diff --git a/marked/Rel-16/25_series/25101/00d7302f6a24d401f2cfe45812dd6ccf_img.jpg b/marked/Rel-16/25_series/25101/00d7302f6a24d401f2cfe45812dd6ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c47d0cb79cc2e26297ad4c6079c55d978679da6 --- /dev/null +++ b/marked/Rel-16/25_series/25101/00d7302f6a24d401f2cfe45812dd6ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01ac175140aa81316a4bac25bafc3df3a01a9731a6f5639409b2fb26f693b9a9 +size 48988 diff --git a/marked/Rel-16/25_series/25101/098c14b0bed86af949bf0a327f252840_img.jpg b/marked/Rel-16/25_series/25101/098c14b0bed86af949bf0a327f252840_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b9257c59fe2c83a4a812cac28a2a78e0c0efc93 --- /dev/null +++ b/marked/Rel-16/25_series/25101/098c14b0bed86af949bf0a327f252840_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36aa1256c914768ab562480f343fd9ffde420b369549560fd933213195560494 +size 64861 diff --git a/marked/Rel-16/25_series/25101/0b13c8043bf78842cd0980770eb9d60b_img.jpg b/marked/Rel-16/25_series/25101/0b13c8043bf78842cd0980770eb9d60b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6f4176c04856f531eb835bff87a8c0cfbe7c22e --- /dev/null +++ b/marked/Rel-16/25_series/25101/0b13c8043bf78842cd0980770eb9d60b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac921384446228688cd9b7510e8654fb5e68c05de54ef6a05c3f6d2c1b9848dd +size 123727 diff --git a/marked/Rel-16/25_series/25101/1322a1154e11aadf811c48774d91ab36_img.jpg b/marked/Rel-16/25_series/25101/1322a1154e11aadf811c48774d91ab36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6afdeed9180284ba7f68a56ea9fc95bef1d1da22 --- /dev/null +++ b/marked/Rel-16/25_series/25101/1322a1154e11aadf811c48774d91ab36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d7d3551d819b46429ebe536641881e083fe88ed2e37e38fa50aa51d8728bc09 +size 135130 diff --git a/marked/Rel-16/25_series/25101/1383c500c5d34fbc2c535226f0f64fa9_img.jpg b/marked/Rel-16/25_series/25101/1383c500c5d34fbc2c535226f0f64fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a13287e3ae53d008f461099207ededcb7b545ddb --- /dev/null +++ b/marked/Rel-16/25_series/25101/1383c500c5d34fbc2c535226f0f64fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5d1b67009535243548d3e9497b988a334897bc4166ee01bbd6201a3e0850ab8 +size 89158 diff --git a/marked/Rel-16/25_series/25101/20b95bcf515b4d9028e98a1d0d68302a_img.jpg b/marked/Rel-16/25_series/25101/20b95bcf515b4d9028e98a1d0d68302a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e0433a007e235bba58ed6fcaa9a2f7779e73928 --- /dev/null +++ b/marked/Rel-16/25_series/25101/20b95bcf515b4d9028e98a1d0d68302a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09a7628a861ea7797ebf6bb7e138d2be58068dce11b7591e8ab9b4fb422ad35e +size 25197 diff --git a/marked/Rel-16/25_series/25101/2686cc35669b140d74b134b0c673adf8_img.jpg b/marked/Rel-16/25_series/25101/2686cc35669b140d74b134b0c673adf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3d05274ebc861f50b4e579ee3ed261392cb3013 --- /dev/null +++ b/marked/Rel-16/25_series/25101/2686cc35669b140d74b134b0c673adf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c19660a7ec8cd6dc853013d25a8b70b206ce6ac539e93cf72872e84c2528463 +size 34250 diff --git a/marked/Rel-16/25_series/25101/2ddba848b8cb2941701e9e123fa7a27d_img.jpg b/marked/Rel-16/25_series/25101/2ddba848b8cb2941701e9e123fa7a27d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ab70d531ea51525dbdc574d87e99c0563aeb6b0 --- /dev/null +++ b/marked/Rel-16/25_series/25101/2ddba848b8cb2941701e9e123fa7a27d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad89597b4e59d3686bf67f8d2e9cd5e9c0823b9f757c43e8e9bc43eb1d757011 +size 126960 diff --git a/marked/Rel-16/25_series/25101/3179e999cb73ab07fad8e9407c88a3b6_img.jpg b/marked/Rel-16/25_series/25101/3179e999cb73ab07fad8e9407c88a3b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c59d815b94734b77a0bb4458e077fe5af61aac35 --- /dev/null +++ b/marked/Rel-16/25_series/25101/3179e999cb73ab07fad8e9407c88a3b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5218ec03c2ed3dcbebddbcaa30894e5957f124511f28739f26484d5fab57e45 +size 23544 diff --git a/marked/Rel-16/25_series/25101/3760416dd8f3568fcc52cd168cac3352_img.jpg b/marked/Rel-16/25_series/25101/3760416dd8f3568fcc52cd168cac3352_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4300e9d36d88fda001a693abe0046d12d0b1bd61 --- /dev/null +++ b/marked/Rel-16/25_series/25101/3760416dd8f3568fcc52cd168cac3352_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c25ddd24d4c83edcaf5a2d6bb895ae7b92ef4f306d68d90ea63c97bd601d441 +size 57605 diff --git a/marked/Rel-16/25_series/25101/3b5dee61a2394578df7e680b9a098fa7_img.jpg b/marked/Rel-16/25_series/25101/3b5dee61a2394578df7e680b9a098fa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b874a773d2609d478e963dd7f719c84259b3536a --- /dev/null +++ b/marked/Rel-16/25_series/25101/3b5dee61a2394578df7e680b9a098fa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b5fe0a3264940592d99df9c34cbdd579e6c3792433c96a74ab73c287366215c +size 45667 diff --git a/marked/Rel-16/25_series/25101/3b7ac0916ffd00e982c6814d71ffe242_img.jpg b/marked/Rel-16/25_series/25101/3b7ac0916ffd00e982c6814d71ffe242_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d29a6532ff2394b834d2b134d6bd5ef07e8652b --- /dev/null +++ b/marked/Rel-16/25_series/25101/3b7ac0916ffd00e982c6814d71ffe242_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68a21d1d126f40a424f3ad5622decd763ef5dc8d3d1300b024124ce753e4441c +size 49399 diff --git a/marked/Rel-16/25_series/25101/3c586c53df312a3694ee1ad0e7fd0960_img.jpg b/marked/Rel-16/25_series/25101/3c586c53df312a3694ee1ad0e7fd0960_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2fafdc1a61728a34da6fb0ccc26069a13d6dc3 --- /dev/null +++ b/marked/Rel-16/25_series/25101/3c586c53df312a3694ee1ad0e7fd0960_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ecd5a8ab5ab4f112ac69c50710673d8e2575723330a1270d5ced489bc2181a +size 136675 diff --git a/marked/Rel-16/25_series/25101/3deb36ec163d8c531f3498b485945091_img.jpg b/marked/Rel-16/25_series/25101/3deb36ec163d8c531f3498b485945091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcb81f906568c6b3ee13aa3530b07610393d7d5 --- /dev/null +++ b/marked/Rel-16/25_series/25101/3deb36ec163d8c531f3498b485945091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f993be7515d701598c98f9d9dd740cc9ba5543b17d1fafe45a402151b19a84d6 +size 109671 diff --git a/marked/Rel-16/25_series/25101/44faa5cb8c5bb66acd22c61811f12b9a_img.jpg b/marked/Rel-16/25_series/25101/44faa5cb8c5bb66acd22c61811f12b9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20067560104f583a55f44ebdcfeae5ff3b0b5404 --- /dev/null +++ b/marked/Rel-16/25_series/25101/44faa5cb8c5bb66acd22c61811f12b9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec3c3b2a7f9edb347d720d457be2d5ecb6cb6a3b368e098b55b0a7b5b4e45bd4 +size 36642 diff --git a/marked/Rel-16/25_series/25101/45b71f54324c8fd8c2830610b367dced_img.jpg b/marked/Rel-16/25_series/25101/45b71f54324c8fd8c2830610b367dced_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d6d679f59b7dd6ec13a33f09ad5c54772fc4d08 --- /dev/null +++ b/marked/Rel-16/25_series/25101/45b71f54324c8fd8c2830610b367dced_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75ba8ed9a44651039b3f4beab92ca46be1162dbb2f30b722696a13b7d75671c7 +size 111831 diff --git a/marked/Rel-16/25_series/25101/47d47f95101a8f543c94a735ad928a65_img.jpg b/marked/Rel-16/25_series/25101/47d47f95101a8f543c94a735ad928a65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e4d802be0c4cb552f5e8e632bfe907c2af3fa9f --- /dev/null +++ b/marked/Rel-16/25_series/25101/47d47f95101a8f543c94a735ad928a65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a774b8e7c411e6b52c8274b56d6972856bde528dfbca0bc842bbdb437f68cc1 +size 11349 diff --git a/marked/Rel-16/25_series/25101/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-16/25_series/25101/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1672a322b3214f1bc91d08e61b85332a8c8caa10 --- /dev/null +++ b/marked/Rel-16/25_series/25101/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdbfecad2233cd271c0a6b5b1097da40b6e109260783caf38ad31bc353c8f395 +size 86213 diff --git a/marked/Rel-16/25_series/25101/5f0934de7d51d5b287f8227e5deca80a_img.jpg b/marked/Rel-16/25_series/25101/5f0934de7d51d5b287f8227e5deca80a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbf7019865ba3b09b6b03fc495aa9f9aff65a82f --- /dev/null +++ b/marked/Rel-16/25_series/25101/5f0934de7d51d5b287f8227e5deca80a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f8d42e0e90bf1e48be63ed0cff4bb192203ef7aec3974339f7e9a42f62af4b7 +size 47789 diff --git a/marked/Rel-16/25_series/25101/630ea28f4495d1f5db09de6182db62c2_img.jpg b/marked/Rel-16/25_series/25101/630ea28f4495d1f5db09de6182db62c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ab3032930bdbf1398f6521fed2c568fec15b7f3 --- /dev/null +++ b/marked/Rel-16/25_series/25101/630ea28f4495d1f5db09de6182db62c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff366fbb3bc4a3bbb437f14f3324d860803d699783bc29854f353e55bba7f4d3 +size 122526 diff --git a/marked/Rel-16/25_series/25101/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/25_series/25101/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07438b3fd874df28e589499fecee9cdf86f96d1d --- /dev/null +++ b/marked/Rel-16/25_series/25101/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bbfa7cf0119cd54588775800c8b8a543062c3baf42c10f74f6350d567818c22 +size 9410 diff --git a/marked/Rel-16/25_series/25101/671a9a08b8506e113012e056945fd8f3_img.jpg b/marked/Rel-16/25_series/25101/671a9a08b8506e113012e056945fd8f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6482a1383d65f43a046689abfe9334ce11c84020 --- /dev/null +++ b/marked/Rel-16/25_series/25101/671a9a08b8506e113012e056945fd8f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc762374196e392c5a04f5cf416138b26b3c08e5798c3ffebf521a806c0eb523 +size 45832 diff --git a/marked/Rel-16/25_series/25101/69be95e218fb058ed062ca975e92a5c8_img.jpg b/marked/Rel-16/25_series/25101/69be95e218fb058ed062ca975e92a5c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..486df89458b117fb4e29a4bcec33e39b6c1e60b6 --- /dev/null +++ b/marked/Rel-16/25_series/25101/69be95e218fb058ed062ca975e92a5c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35eb6a81d721ff18a7e1a782ea5ec15ba534c22751dbbd5cb1d19886d246aaa6 +size 39875 diff --git a/marked/Rel-16/25_series/25101/6de875eb7a49c3352b45075b92e5ea9b_img.jpg b/marked/Rel-16/25_series/25101/6de875eb7a49c3352b45075b92e5ea9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce809de90a8efe629b4280b9c4811e69d714f709 --- /dev/null +++ b/marked/Rel-16/25_series/25101/6de875eb7a49c3352b45075b92e5ea9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf81da1a488e03c353a4646de020dbfd20a3339a0fca154c6e114d795486307 +size 106818 diff --git a/marked/Rel-16/25_series/25101/7a902d790635f608db2476e6340acf8b_img.jpg b/marked/Rel-16/25_series/25101/7a902d790635f608db2476e6340acf8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..510216943e2c724d20008d8d5d541e7a0e47e021 --- /dev/null +++ b/marked/Rel-16/25_series/25101/7a902d790635f608db2476e6340acf8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ece990dd74cc5e0dcf5d669a05cffbab993607237cab92a69c51fa89ba844c9 +size 39594 diff --git a/marked/Rel-16/25_series/25101/7bcf05f70463355ac4550ccb2f963bbd_img.jpg b/marked/Rel-16/25_series/25101/7bcf05f70463355ac4550ccb2f963bbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97dbcb10a4f045396330757302bbb701794162cf --- /dev/null +++ b/marked/Rel-16/25_series/25101/7bcf05f70463355ac4550ccb2f963bbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde94a7430d1eca451219f7f92eea38112f78e1dc46f6ce73b8222e14beb67bc +size 134897 diff --git a/marked/Rel-16/25_series/25101/7f28f27b828d72d06d5d414a6b4a20a7_img.jpg b/marked/Rel-16/25_series/25101/7f28f27b828d72d06d5d414a6b4a20a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb8b7f7a5721b23a5d2b29a366121035093331a --- /dev/null +++ b/marked/Rel-16/25_series/25101/7f28f27b828d72d06d5d414a6b4a20a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d241f6a9e3d9d614c2e7c77078522708da5bf7a75078bc2eb32605874fa97c +size 58433 diff --git a/marked/Rel-16/25_series/25101/835ebc0e9ec15eea8eadc15448249226_img.jpg b/marked/Rel-16/25_series/25101/835ebc0e9ec15eea8eadc15448249226_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0553fde224a172059d2f6708706783ef5045284 --- /dev/null +++ b/marked/Rel-16/25_series/25101/835ebc0e9ec15eea8eadc15448249226_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cfa09f6cef4a49be242abc1209d5f08862a93f2c34e7954f1a2af4ca439afee +size 85554 diff --git a/marked/Rel-16/25_series/25101/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg b/marked/Rel-16/25_series/25101/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f892ca28c21472b85407e1811834d38a10166e58 --- /dev/null +++ b/marked/Rel-16/25_series/25101/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02e17165852142f3ecc974fe6c3f80a7bb71af3889cbc6a84bd6a3c61386cfdf +size 93334 diff --git a/marked/Rel-16/25_series/25101/96bb01315ba42d2185ff70400f09053f_img.jpg b/marked/Rel-16/25_series/25101/96bb01315ba42d2185ff70400f09053f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69cf1e50aa90fb0014f326542bc24d1a3b66d5df --- /dev/null +++ b/marked/Rel-16/25_series/25101/96bb01315ba42d2185ff70400f09053f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbe793d9048700c8f56a1814224c21b25591be994ad23a0aad099efcc0cbc856 +size 58400 diff --git a/marked/Rel-16/25_series/25101/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-16/25_series/25101/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b0b67efde74067e0d42fcbb65ed30d0b7438184 --- /dev/null +++ b/marked/Rel-16/25_series/25101/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8a72c4e8660a123c60b5dd6e2d3aaa5d855f5cb5762a3f6334b9ba422b6823b +size 47387 diff --git a/marked/Rel-16/25_series/25101/99261d7a7ce0fb14086143419ac820ae_img.jpg b/marked/Rel-16/25_series/25101/99261d7a7ce0fb14086143419ac820ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..982114dc44037c9c670ca8453e4d9b054026d63b --- /dev/null +++ b/marked/Rel-16/25_series/25101/99261d7a7ce0fb14086143419ac820ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7be3b61df86ed4bd97af6dc537940a5833422eff509a77258139006b3f9a999b +size 39914 diff --git a/marked/Rel-16/25_series/25101/9c575767fe4409cdd2898df6f70139f5_img.jpg b/marked/Rel-16/25_series/25101/9c575767fe4409cdd2898df6f70139f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec8cf1b78760767aef6a1abcdd87fa6255441286 --- /dev/null +++ b/marked/Rel-16/25_series/25101/9c575767fe4409cdd2898df6f70139f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5446fb118c8e627ada5f442e9abdeda101eeafccc922ca57cbc9e690000da218 +size 40258 diff --git a/marked/Rel-16/25_series/25101/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg b/marked/Rel-16/25_series/25101/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bc5808f687f6fe59546ba2f42820fc30de7600b --- /dev/null +++ b/marked/Rel-16/25_series/25101/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10c64bb93a96fbcc991c0f2f5c6f7c42b7ff548bd18f2fd63ce61ade9420276b +size 35680 diff --git a/marked/Rel-16/25_series/25101/9e23e88f57c8d963f343c29619ebdbf2_img.jpg b/marked/Rel-16/25_series/25101/9e23e88f57c8d963f343c29619ebdbf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aed39b89fb55a76b081e912fac9758a4cbd0e82 --- /dev/null +++ b/marked/Rel-16/25_series/25101/9e23e88f57c8d963f343c29619ebdbf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebd5f7bf9944f99de3492c35578c49462b6aa9c12a090408b078439147d5f3ef +size 111036 diff --git a/marked/Rel-16/25_series/25101/9e2b890eb1af21240ec68d210241d0d5_img.jpg b/marked/Rel-16/25_series/25101/9e2b890eb1af21240ec68d210241d0d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c780ed094dbb737b31ac6e4c599139a83d4885 --- /dev/null +++ b/marked/Rel-16/25_series/25101/9e2b890eb1af21240ec68d210241d0d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adccba44d7827c4d1acb703f0b5a8ecd0b3b08241eb32264d31b7e25545abcb9 +size 40182 diff --git a/marked/Rel-16/25_series/25101/a44678044720601f152e409a473467ce_img.jpg b/marked/Rel-16/25_series/25101/a44678044720601f152e409a473467ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b5f378ed3306dc02f23e51942a271a80471d5f --- /dev/null +++ b/marked/Rel-16/25_series/25101/a44678044720601f152e409a473467ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cfabe80c9d24aa1749683ad57350048e4303f3d615e752be16539abb762aa0f +size 110444 diff --git a/marked/Rel-16/25_series/25101/a6c3e540dd89b417038cfeb0e67516e1_img.jpg b/marked/Rel-16/25_series/25101/a6c3e540dd89b417038cfeb0e67516e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fb5573236fdcdb597dd8752ae1ff6c19b0629f0 --- /dev/null +++ b/marked/Rel-16/25_series/25101/a6c3e540dd89b417038cfeb0e67516e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e901a7091f61e83573a9d8bfe17085ca4a76eda73c076aeab42a3e152f7b0395 +size 25231 diff --git a/marked/Rel-16/25_series/25101/b7321a97441b64ca21fa3647d44cfeb0_img.jpg b/marked/Rel-16/25_series/25101/b7321a97441b64ca21fa3647d44cfeb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ece04b172d5a20f4f00fd9e1f25a8005b415c180 --- /dev/null +++ b/marked/Rel-16/25_series/25101/b7321a97441b64ca21fa3647d44cfeb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1239e9489c7aae3b3a8562696434ef8b72a689c221a0bf81aa2bd2fe096eafb +size 34451 diff --git a/marked/Rel-16/25_series/25101/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-16/25_series/25101/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..041f12a924b0b46ac3f025b95005a83614e4bc2e --- /dev/null +++ b/marked/Rel-16/25_series/25101/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14bf1d4c7095f4ccdc563842948261173b54c064853606c426556c63bfb361c4 +size 125705 diff --git a/marked/Rel-16/25_series/25101/c4af7b16ba093a462fb5f67f369ce743_img.jpg b/marked/Rel-16/25_series/25101/c4af7b16ba093a462fb5f67f369ce743_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1da9cc7cd9b1ff2d18ca2c172cae6d136609fb83 --- /dev/null +++ b/marked/Rel-16/25_series/25101/c4af7b16ba093a462fb5f67f369ce743_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d911c23fec3184afcf8586f5790f3a7360c4d2ac389fc3ba91876f221bf1671 +size 142252 diff --git a/marked/Rel-16/25_series/25101/c4ce20d443c5793503265b1f68fe4536_img.jpg b/marked/Rel-16/25_series/25101/c4ce20d443c5793503265b1f68fe4536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49d17926ad7ebfb0252432809a071d991b106747 --- /dev/null +++ b/marked/Rel-16/25_series/25101/c4ce20d443c5793503265b1f68fe4536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ba3b76c4c494796ddafb02edb625a2bd54f7776ace3d1f96384470936343afe +size 140601 diff --git a/marked/Rel-16/25_series/25101/c52ea16bac02e546d0c5767db5dd4981_img.jpg b/marked/Rel-16/25_series/25101/c52ea16bac02e546d0c5767db5dd4981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19db0319850eb87ae77b08bab3395a36787131c3 --- /dev/null +++ b/marked/Rel-16/25_series/25101/c52ea16bac02e546d0c5767db5dd4981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:073284107bfe9a45cc5a230948d5dfe8fb75fc3ba2e020592245fc9c0f19339f +size 135183 diff --git a/marked/Rel-16/25_series/25101/c8262867e39639276066c34941705aed_img.jpg b/marked/Rel-16/25_series/25101/c8262867e39639276066c34941705aed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14ae2d5c40f86cd9d02feb42061a7ac5593324f1 --- /dev/null +++ b/marked/Rel-16/25_series/25101/c8262867e39639276066c34941705aed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a9baaab775526ae9288b23cacd1ae1c478536a109dfb7c6ee2023fa6fc8f18a +size 39614 diff --git a/marked/Rel-16/25_series/25101/c9a112da345a240257303fe6d2fa36fb_img.jpg b/marked/Rel-16/25_series/25101/c9a112da345a240257303fe6d2fa36fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b20ab9837b63fb530f1de01ea1eb7fe6ef4a0572 --- /dev/null +++ b/marked/Rel-16/25_series/25101/c9a112da345a240257303fe6d2fa36fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6fd9a4cd06733a1e06ca54af4a1c910115dc46cdc899215b1151e62970cf71b +size 108203 diff --git a/marked/Rel-16/25_series/25101/cacf4ea7d22183dc5235f1673ef884e8_img.jpg b/marked/Rel-16/25_series/25101/cacf4ea7d22183dc5235f1673ef884e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ece04b172d5a20f4f00fd9e1f25a8005b415c180 --- /dev/null +++ b/marked/Rel-16/25_series/25101/cacf4ea7d22183dc5235f1673ef884e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1239e9489c7aae3b3a8562696434ef8b72a689c221a0bf81aa2bd2fe096eafb +size 34451 diff --git a/marked/Rel-16/25_series/25101/cc2f9155973f67e9efae011b93249ef5_img.jpg b/marked/Rel-16/25_series/25101/cc2f9155973f67e9efae011b93249ef5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..569d50e6a863bdefe8a7ac45a80e57a9fa510377 --- /dev/null +++ b/marked/Rel-16/25_series/25101/cc2f9155973f67e9efae011b93249ef5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8646b8f52ccf78a0f2bed31c034c184b64e6671d526505786d6c0452e5e66da2 +size 57082 diff --git a/marked/Rel-16/25_series/25101/cf6ca8f1a86c81dccf05cb590811fa7e_img.jpg b/marked/Rel-16/25_series/25101/cf6ca8f1a86c81dccf05cb590811fa7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e61af0c0b32998fecd3b5daf1b8a7c3ca24edaae --- /dev/null +++ b/marked/Rel-16/25_series/25101/cf6ca8f1a86c81dccf05cb590811fa7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8457c6acbed615cdcfa26311479988d9db83cc14be2e34e4cb673be03592b4fb +size 135542 diff --git a/marked/Rel-16/25_series/25101/d86ffa3857b2c16635c09b2768c4e01d_img.jpg b/marked/Rel-16/25_series/25101/d86ffa3857b2c16635c09b2768c4e01d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ea4ec1ca4936e438a760bbf60cf24d79beb08d0 --- /dev/null +++ b/marked/Rel-16/25_series/25101/d86ffa3857b2c16635c09b2768c4e01d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d65ec717a58383fa27aa76e9267a6f3e721638b2b1b196b577aaa980a0e502d4 +size 57377 diff --git a/marked/Rel-16/25_series/25101/df6ce1a71cc187bb1044b2c81fdea7c0_img.jpg b/marked/Rel-16/25_series/25101/df6ce1a71cc187bb1044b2c81fdea7c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..480dfd969070a6f677071b36223a1489ff0b45fc --- /dev/null +++ b/marked/Rel-16/25_series/25101/df6ce1a71cc187bb1044b2c81fdea7c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1514047e072f82ccf914a9167e32f791b7ee549e578eab74a7684082b7cd593 +size 9982 diff --git a/marked/Rel-16/25_series/25101/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-16/25_series/25101/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32df925822ceefa4c42746b9a99bc09f52f0dc54 --- /dev/null +++ b/marked/Rel-16/25_series/25101/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26e4c9f35feed2964f354c2800f3550293802dea86e322c172e58f9c7d5a452f +size 20809 diff --git a/marked/Rel-16/25_series/25101/e3734a615e069a3923c72f1ef4608fa9_img.jpg b/marked/Rel-16/25_series/25101/e3734a615e069a3923c72f1ef4608fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3046f7b9342b05a1baff339c424f3a2acc886adb --- /dev/null +++ b/marked/Rel-16/25_series/25101/e3734a615e069a3923c72f1ef4608fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19523dec708b3b5d0ba1fd8f89cecb5fd04df3eaf75ac7d1466130b189ab92f1 +size 45746 diff --git a/marked/Rel-16/25_series/25101/f064a4f199728c7a51a422a98ecec5f5_img.jpg b/marked/Rel-16/25_series/25101/f064a4f199728c7a51a422a98ecec5f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..934d398dc24332f2b69eb46c35cdd7cf925ac6ee --- /dev/null +++ b/marked/Rel-16/25_series/25101/f064a4f199728c7a51a422a98ecec5f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa1152a1f5001e05452f2b155e2585e2a0db6c9889a78e5d28038bdabf3666ab +size 123167 diff --git a/marked/Rel-16/25_series/25101/f1bbb2dc05f87cc762b8f1f0ff9f3ba3_img.jpg b/marked/Rel-16/25_series/25101/f1bbb2dc05f87cc762b8f1f0ff9f3ba3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f2f578bd1645300d12d1f42de8ceeda9d49fc9 --- /dev/null +++ b/marked/Rel-16/25_series/25101/f1bbb2dc05f87cc762b8f1f0ff9f3ba3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1afe6a0c0f3a14741afc2bd4b850d1fc393f4f06254dc984315d3eaad53b3ef7 +size 47164 diff --git a/marked/Rel-16/25_series/25101/f3ad0d455d96f36b0c1551e022b5a423_img.jpg b/marked/Rel-16/25_series/25101/f3ad0d455d96f36b0c1551e022b5a423_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d30dae2913fc7e88e99cc29be749e573caee43a1 --- /dev/null +++ b/marked/Rel-16/25_series/25101/f3ad0d455d96f36b0c1551e022b5a423_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0c7427fde8d0da02ab4f43f7c8e70a7c285f4c52e7459945ad592c616ca91ca +size 70022 diff --git a/marked/Rel-16/25_series/25101/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-16/25_series/25101/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bdc11cb7876b723cc9c30658d2f116e16782390 --- /dev/null +++ b/marked/Rel-16/25_series/25101/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88ffdc38c074094f1b01552505ea7c5e83fe40978ffb192e1d2dd462e08b0f08 +size 103546 diff --git a/marked/Rel-16/25_series/25101/f83da0638c9b438f282afed053cddb80_img.jpg b/marked/Rel-16/25_series/25101/f83da0638c9b438f282afed053cddb80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecb5c31f6da564abe892b9ccd33f941115f0db31 --- /dev/null +++ b/marked/Rel-16/25_series/25101/f83da0638c9b438f282afed053cddb80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25799a9b6c9799fd4431ac61715f67110a864a598791c440e8d386f1fb70411a +size 59057 diff --git a/marked/Rel-16/25_series/25101/f95e8ef65337ff45839ad3994f66af54_img.jpg b/marked/Rel-16/25_series/25101/f95e8ef65337ff45839ad3994f66af54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82ef4a5e0dcad5c2f40a570f36fd2f2cc4f10d8d --- /dev/null +++ b/marked/Rel-16/25_series/25101/f95e8ef65337ff45839ad3994f66af54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec97f91668f7d9c97f532806d1698160c45fa761c0e7f4f3935880d97045ed8d +size 2995 diff --git a/marked/Rel-16/25_series/25101/fed9090f9aa34eb8f39fb3fd5b781359_img.jpg b/marked/Rel-16/25_series/25101/fed9090f9aa34eb8f39fb3fd5b781359_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03cb25963f54898f8e9c103478babe8c7fc66625 --- /dev/null +++ b/marked/Rel-16/25_series/25101/fed9090f9aa34eb8f39fb3fd5b781359_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:910a52f41d734612cc992d09995c4788f2f6cef7d182633091645a28a5ac55b4 +size 66008 diff --git a/marked/Rel-16/25_series/25101/raw.md b/marked/Rel-16/25_series/25101/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..49305dd7daa6dc8de2b6da96e6e7ebd0fe255617 --- /dev/null +++ b/marked/Rel-16/25_series/25101/raw.md @@ -0,0 +1,14815 @@ + + +# 3GPP TS 25.101 V16.1.0 (2019-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 16)** --- + +![3GPP logo with the text 'A GLOBAL INITIATIVE' below it.](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo features the letters '3GPP' in a stylized, bold font. The '3' is large and curved, the 'G' is a thick, rounded shape, the 'P' is a standard capital letter, and the 'P' is a stylized, overlapping version of the 'P'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, sans-serif font. + +3GPP logo with the text 'A GLOBAL INITIATIVE' below it. + +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 + +| | | | +|-------|----------------------------------------------------------------------|----| +| 1 | Scope..... | 15 | +| 2 | References..... | 15 | +| 3 | Definitions, symbols and abbreviations..... | 15 | +| 3.1 | Definitions..... | 15 | +| 3.2 | Abbreviations..... | 17 | +| 4 | General..... | 19 | +| 4.1 | Relationship between Minimum Requirements and Test Requirements..... | 19 | +| 4.2 | Power Classes..... | 19 | +| 4.3 | Control and monitoring functions..... | 19 | +| 4.3.1 | Minimum requirement..... | 20 | +| 4.4 | RF requirements in later releases..... | 20 | +| 5 | Frequency bands and channel arrangement..... | 20 | +| 5.1 | General..... | 20 | +| 5.2 | Frequency bands..... | 20 | +| 5.3 | TX-RX frequency separation..... | 23 | +| 5.4 | Channel arrangement..... | 24 | +| 5.4.1 | Channel spacing..... | 24 | +| 5.4.2 | Channel raster..... | 24 | +| 5.4.3 | Channel number..... | 24 | +| 5.4.4 | UARFCN..... | 27 | + +## 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. + +© 2019, 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 + +| | | | +|----------|-----------------------------------------------------------------------------------|----| +| 6 | Transmitter characteristics..... | 28 | +| 6.1 | General..... | 28 | +| 6.2 | Transmit power..... | 28 | +| 6.2.1 | UE maximum output power..... | 28 | +| 6.2.1A | UE maximum output power for UL OLTD..... | 30 | +| 6.2.1B | UE maximum output power for UL CLTD..... | 31 | +| 6.2.1C | UE maximum output power for UL MIMO..... | 32 | +| 6.2.1D | UE maximum output power for DB-DC-HSUPA..... | 33 | +| 6.2.2 | UE maximum output power with HS-DPCCH and E-DCH..... | 34 | +| 6.2.2A | UE maximum output power for DC-HSUPA..... | 34 | +| 6.2.2B | UE maximum output power with HS-DPCCH and E-DCH for UL OLTD..... | 35 | +| 6.2.2C | UE maximum output power with HS-DPCCH and E-DCH for UL CLTD..... | 36 | +| 6.2.2D | UE maximum output power with HS-DPCCH and E-DCH for UL MIMO..... | 36 | +| 6.2.2E | UE maximum output power for the band with HS-DPCCH and E-DCH for DB-DC-HSUPA..... | 37 | +| 6.2.3 | UE Relative code domain power accuracy..... | 37 | +| 6.2.3A | UE Relative code domain power accuracy for DC-HSUPA..... | 38 | +| 6.2.3B | UE Relative code domain power accuracy for UL OLTD..... | 39 | +| 6.2.3C | UE Relative code domain power accuracy for UL CLTD..... | 39 | +| 6.2.3D | UE Relative code domain power accuracy for UL MIMO..... | 39 | +| 6.2.3E | UE Relative code domain power accuracy for DB-DC-HSUPA..... | 39 | +| 6.3 | Frequency Error..... | 39 | +| 6.3A | Frequency Error for DC-HSUPA..... | 39 | +| 6.3B | Frequency error for UL OLTD..... | 39 | +| 6.3C | Frequency error for UL CLTD..... | 40 | +| 6.3D | Frequency error for UL MIMO..... | 40 | +| 6.3E | Frequency error for DB-DC-HSUPA..... | 40 | +| 6.4 | Output power dynamics..... | 40 | +| 6.4.1 | Open loop power control..... | 40 | +| 6.4.1.1 | Minimum requirement..... | 40 | +| 6.4.1.1A | Additional requirement for DC-HSUPA..... | 40 | + +| | | | +|------------|------------------------------------------------------|----| +| 6.4.1.1B | Additional requirement for DB-DC-HSUPA..... | 40 | +| 6.4.2 | Inner loop power control in the uplink..... | 41 | +| 6.4.2.1 | Power control steps..... | 41 | +| 6.4.2.1.1 | Minimum requirement..... | 41 | +| 6.4.2.1.1A | Additional requirement for DC-HSUPA..... | 42 | +| 6.4.2.1.1B | Additional requirement for UL OLTD..... | 43 | +| 6.4.2.1.1C | Additional requirement for UL CLTD..... | 43 | +| 6.4.2.1.1D | Additional requirement for UL MIMO..... | 43 | +| 6.4.2.1.1E | Additional requirement for DB-DC-HSUPA..... | 43 | +| 6.4.3 | Minimum output power..... | 43 | +| 6.4.3.1 | Minimum requirement..... | 43 | +| 6.4.3.1A | Additional requirement for DC-HSUPA..... | 43 | +| 6.4.3.1B | Additional requirement for UL OLTD..... | 43 | +| 6.4.3.1C | Additional requirement for UL CLTD..... | 43 | +| 6.4.3.1D | Additional requirement for UL MIMO..... | 43 | +| 6.4.3.1E | Additional requirement for DB-DC-HSUPA..... | 44 | +| 6.4.4 | Out-of-synchronization handling of output power..... | 44 | +| 6.4.4.1 | Minimum requirement..... | 44 | +| 6.4.4.1A | Additional requirement for UL OLTD..... | 44 | +| 6.4.4.1B | Additional requirement for UL CLTD..... | 44 | +| 6.4.4.1C | Additional requirement for UL MIMO..... | 45 | +| 6.4.4.1D | Additional requirement for DB-DC-HSUPA..... | 45 | +| 6.4.4.2 | Test case..... | 45 | +| 6.4A | Output pattern dynamics..... | 47 | +| 6.4A.1 | Out-of-quality handling of TPI applicability..... | 47 | +| 6.4A.1.1 | Minimum requirement..... | 47 | +| 6.4A.1.2 | Test case..... | 47 | +| 6.5 | Transmit ON/OFF power..... | 49 | +| 6.5.1 | Transmit OFF power..... | 49 | +| 6.5.1.1 | Minimum requirement..... | 49 | + +| | | | +|----------|------------------------------------------------------------------------------|----| +| 6.5.1.1A | Additional requirement for DC-HSUPA..... | 49 | +| 6.5.1.1B | Additional requirement for UL OLTD..... | 50 | +| 6.5.1.1C | Additional requirement for UL CLTD..... | 50 | +| 6.5.1.1D | Additional requirement for UL MIMO..... | 50 | +| 6.5.1.1E | Additional requirement for DB-DC-HSUPA..... | 50 | +| 6.5.2 | Transmit ON/OFF Time mask..... | 50 | +| 6.5.2.1 | Minimum requirement..... | 50 | +| 6.5.2.1A | Additional requirement for UL OLTD..... | 53 | +| 6.5.2.1B | Additional requirement for UL CLTD..... | 53 | +| 6.5.2.1C | Additional requirement for UL MIMO..... | 53 | +| 6.5.2.1D | Additional requirement for DB-DC-HSUPA operating simultaneously with CS..... | 53 | +| 6.5.3 | Change of TFC..... | 53 | +| 6.5.3.1 | Minimum requirement..... | 54 | +| 6.5.3.1A | Additional requirement for UL OLTD..... | 55 | +| 6.5.3.1B | Additional requirement for UL CLTD..... | 55 | +| 6.5.3.1C | Additional requirement for DB-DC-HSUPA operating simultaneously with CS..... | 56 | +| 6.5.4 | Power setting in uplink compressed mode..... | 56 | +| 6.5.4.1 | Minimum requirement..... | 56 | +| 6.5.4.1A | Additional requirement for UL OLTD..... | 57 | +| 6.5.4.1B | Additional requirement for UL CLTD..... | 57 | +| 6.5.4.1C | Additional requirement for DB-DC-HSUPA..... | 58 | +| 6.5.5 | HS-DPCCH..... | 58 | +| 6.5.5.1 | Minimum requirement..... | 58 | +| 6.5.5.1A | Additional requirement for UL OLTD..... | 60 | +| 6.5.5.1B | Additional requirement for UL CLTD..... | 60 | +| 6.5.5.1C | Additional requirement for UL MIMO..... | 60 | +| 6.5.5.1D | Additional requirement for DB-DC-HSUPA..... | 60 | +| 6.6 | Output RF spectrum emissions..... | 60 | +| 6.6.1 | Occupied bandwidth..... | 60 | +| 6.6.1A | Occupied bandwidth for DC-HSUPA..... | 61 | + +| | | | +|------------|-----------------------------------------------------------------|----| +| 6.6.1B | Occupied bandwidth for UL OLTD..... | 61 | +| 6.6.1C | Occupied bandwidth for UL CLTD..... | 61 | +| 6.6.1D | Occupied bandwidth for UL MIMO..... | 61 | +| 6.6.1E | Occupied bandwidth for DB-DC-HSUPA..... | 61 | +| 6.6.2 | Out of band emission..... | 61 | +| 6.6.2.1 | Spectrum emission mask..... | 61 | +| 6.6.2.1.1 | Minimum requirement..... | 62 | +| 6.6.2.1A | Additional Spectrum emission mask for DC-HSUPA..... | 63 | +| 6.6.2.1A.1 | Minimum requirement..... | 63 | +| 6.6.2.1A.2 | Additional requirement for band II, IV, V, X, XXV and XXVI..... | 63 | +| 6.6.2.1B | Additional requirement for UL OLTD..... | 64 | +| 6.6.2.1C | Additional requirement for UL CLTD..... | 64 | +| 6.6.2.1D | Additional requirement for UL MIMO..... | 64 | +| 6.6.2.1E | Additional requirement for DB-DC-HSUPA..... | 64 | +| 6.6.2.2 | Adjacent Channel Leakage power Ratio (ACLR)..... | 64 | +| 6.6.2.2.1 | Minimum requirement..... | 64 | +| 6.6.2.2.1A | Additional requirement for DC-HSUPA..... | 64 | +| 6.6.2.2.1B | Additional requirement for UL OLTD..... | 65 | +| 6.6.2.2.1C | Additional requirement for UL CLTD..... | 65 | +| 6.6.2.2.1D | Additional requirement for UL MIMO..... | 65 | +| 6.6.2.2.1E | Additional requirement for DB-DC-HSUPA..... | 65 | +| 6.6.3 | Spurious emissions..... | 65 | +| 6.6.3.1 | Minimum requirement..... | 65 | +| 6.6.3.1.1 | Additional requirement..... | 73 | +| 6.6.3.1A | Additional requirement for DC-HSUPA..... | 74 | +| 6.6.3.1A.1 | Additional requirement for DC-HSUPA..... | 80 | +| 6.6.3.1B | Additional requirement for UL OLTD..... | 80 | +| 6.6.3.1C | Additional requirement for UL CLTD..... | 80 | +| 6.6.3.1D | Additional requirement for UL MIMO..... | 80 | +| 6.6.3.1E | Additional requirement for DB-DC-HSUPA..... | 81 | + +| | | | +|-------------|------------------------------------------------------------------------------|----| +| 6.7 | Transmit intermodulation..... | 82 | +| 6.7.1 | Minimum requirement..... | 82 | +| 6.7.1A | Additional requirement for DC-HSUPA..... | 82 | +| 6.7.1B | Additional requirement for UL OLTD..... | 83 | +| 6.7.1C | Additional requirement for UL CLTD..... | 83 | +| 6.7.1D | Additional requirement for UL MIMO..... | 83 | +| 6.7.1E | Additional requirement for DB-DC-HSUPA..... | 83 | +| 6.8 | Transmit modulation..... | 83 | +| 6.8.1 | Transmit pulse shape filter..... | 83 | +| 6.8.1A | Additional requirement for UL OLTD..... | 83 | +| 6.8.1B | Additional requirement for UL CLTD..... | 83 | +| 6.8.1C | Additional requirement for UL MIMO..... | 84 | +| 6.8.1D | Additional requirement for DB-DC-HSUPA..... | 84 | +| 6.8.2 | Error Vector Magnitude..... | 84 | +| 6.8.2.1 | Minimum requirement..... | 84 | +| 6.8.2.1A | Additional requirement for DC-HSUPA..... | 85 | +| 6.8.2.1B | Additional requirement for UL OLTD..... | 85 | +| 6.8.2.1C | Additional requirement for UL CLTD..... | 85 | +| 6.8.2.1D | Additional requirement for UL MIMO..... | 86 | +| 6.8.2.1E | Additional requirement for DB-DC-HSUPA..... | 86 | +| 6.8.3 | Peak code domain error..... | 86 | +| 6.8.3.1 | Minimum requirement..... | 87 | +| 6.8.3.1A | Additional requirement for UL OLTD..... | 87 | +| 6.8.3.1B | Additional requirement for UL CLTD..... | 87 | +| 6.8.3.1C | Additional requirement for DB-DC-HSUPA operating simultaneously with CS..... | 87 | +| 6.8.3a | Relative code domain error..... | 87 | +| 6.8.3a.1 | Relative Code Domain Error..... | 87 | +| 6.8.3a.1.1 | Minimum requirement..... | 88 | +| 6.8.3a.1.1a | Additional requirement for DC-HSUPA..... | 88 | +| 6.8.3a.1.1b | Additional requirement for UL OLTD..... | 89 | + +| | | | +|-------------|---------------------------------------------|----| +| 6.8.3a.1.1c | Additional requirement for UL CLTD..... | 89 | +| 6.8.3a.1.1d | Additional requirement for UL MIMO..... | 89 | +| 6.8.3a.1.1e | Additional requirement for DB-DC-HSUPA..... | 89 | +| 6.8.3b | In-band emission for DC-HSUPA..... | 89 | +| 6.8.3b.1 | Minimum requirement for DC-HSUPA..... | 89 | +| 6.8.4 | Phase discontinuity for uplink DPCH..... | 89 | +| 6.8.4.1 | Minimum requirement..... | 89 | +| 6.8.4.1A | Additional requirement for UL OLTD..... | 90 | +| 6.8.4.1B | Additional requirement for UL CLTD..... | 90 | +| 6.8.4.1C | Additional requirement for DB-DC-HSUPA..... | 90 | +| 6.8.5 | Phase discontinuity for HS-DPCCH..... | 90 | +| 6.8.5.1 | Minimum requirement..... | 91 | +| 6.8.5.1A | Additional requirement for UL OLTD..... | 91 | +| 6.8.5.1B | Additional requirement for UL CLTD..... | 91 | +| 6.8.6 | Phase discontinuity for E-DCH..... | 91 | +| 6.8.6.1 | Minimum requirement..... | 92 | +| 6.8.6.1A | Additional requirement for UL OLTD..... | 92 | +| 6.8.6.1B | Additional requirement for UL CLTD..... | 93 | +| 6.8.6.1C | Additional requirement for DB-DC-HSUPA..... | 93 | +| 6.8.7 | Time alignment error for DC-HSUPA..... | 93 | +| 6.8.7.1 | Minimum requirement..... | 93 | +| 6.8.7A | Time alignment error for UL OLTD..... | 93 | +| 6.8.7A.1 | Minimum requirement..... | 93 | +| 6.8.7B | Time alignment error for UL CLTD..... | 93 | +| 6.8.7B.1 | Minimum requirement..... | 93 | +| 6.8.7C | Time alignment error for UL MIMO..... | 93 | +| 6.8.7C.1 | Minimum requirement..... | 93 | +| 6.8.7D | Time alignment error for DB-DC-HSUPA..... | 94 | +| 6.8.7D.1 | Minimum requirement..... | 94 | + +| | | | +|---------|--------------------------------------------------------------------------------------------------------------------|-----| +| 7 | Receiver characteristics..... | 94 | +| 7.1 | General..... | 94 | +| 7.2 | Diversity characteristics..... | 95 | +| 7.3 | Reference sensitivity level..... | 95 | +| 7.3.1 | Minimum requirement..... | 95 | +| 7.3.2 | Additional requirement for DC-HSDPA..... | 97 | +| 7.3.3 | Additional requirement for DB-DC-HSDPA..... | 99 | +| 7.3.4 | Additional requirement for single band 4C-HSDPA..... | 100 | +| 7.3.5 | Additional requirement for dual band 4C-HSDPA..... | 101 | +| 7.3.6 | Additional requirement for single band 8C-HSDPA..... | 101 | +| 7.3.7 | Additional requirement for single band NC-4C-HSDPA..... | 102 | +| 7.4 | Maximum input level..... | 103 | +| 7.4.1 | Minimum requirement for DPCH reception..... | 103 | +| 7.4.2 | Minimum requirement for HS-PDSCH reception..... | 103 | +| 7.4.2.1 | Minimum requirement for 16QAM..... | 103 | +| 7.4.2.2 | Minimum requirement for 64QAM..... | 104 | +| 7.4.3 | Additional requirement for DC-HSDPA and DB-DC-HSDPA..... | 105 | +| 7.4.3.1 | Additional requirement for 16QAM..... | 105 | +| 7.4.3.2 | Additional requirement for 64QAM..... | 105 | +| 7.4.4 | Additional requirement for single band/dual band 4C-HSDPA or single band 8C-HSDPA and single band NC-4C-HSDPA..... | 106 | +| 7.4.4.1 | Additional requirement for 16QAM..... | 106 | +| 7.4.4.2 | Additional requirement for 64QAM..... | 107 | +| 7.5 | Adjacent Channel Selectivity (ACS)..... | 107 | +| 7.5.1 | Minimum requirement..... | 107 | +| 7.5.2 | Additional requirement for DC-HSDPA and DB-DC-HSDPA..... | 108 | +| 7.5.3 | Additional requirement for single band/dual band 4C-HSDPA..... | 108 | +| 7.5.4 | Additional requirement for single band 8C-HSDPA..... | 111 | +| 7.5.5 | Additional requirement for single band NC-4C-HSDPA..... | 112 | +| 7.6 | Blocking characteristics..... | 113 | + +| | | | +|----------|---------------------------------------------------------------------------------|-----| +| 7.6.1 | Minimum requirement (In-band blocking)..... | 114 | +| 7.6.1A | Additional requirement for DC-HSDPA and DB-DC-HSDPA (In-band blocking)..... | 115 | +| 7.6.1B | Additional requirement for DC-HSUPA (In-band blocking)..... | 117 | +| 7.6.1C | Additional requirement for single band 4C-HSDPA (In-band blocking)..... | 119 | +| 7.6.1C.1 | Single uplink operation..... | 119 | +| 7.6.1C.2 | Dual uplink operation..... | 120 | +| 7.6.1D | Additional requirement for dual band 4C-HSDPA (In-band blocking)..... | 121 | +| 7.6.1D.1 | Single uplink operation..... | 121 | +| 7.6.1D.2 | Dual uplink operation..... | 122 | +| 7.6.1E | Additional requirement for single band 8C-HSDPA (In-band blocking)..... | 124 | +| 7.6.1E.1 | Single uplink operation..... | 124 | +| 7.6.1E.2 | Dual uplink operation..... | 124 | +| 7.6.1F | Additional requirement for single band NC-4C-HSDPA (In-band blocking)..... | 125 | +| 7.6.1F.1 | Single uplink operation..... | 125 | +| 7.6.1F.2 | Dual uplink operation..... | 126 | +| 7.6.2 | Minimum requirement (Out-of-band blocking)..... | 127 | +| 7.6.2A | Additional requirement for DC-HSDPA (Out-of-band blocking)..... | 129 | +| 7.6.2B | Additional requirement for DB-DC-HSDPA (Out-of-band blocking)..... | 131 | +| 7.6.2C | Additional requirement for single band 4C-HSDPA (Out-of-band blocking)..... | 132 | +| 7.6.2D | Additional requirement for dual band 4C-HSDPA (Out-of-band blocking)..... | 133 | +| 7.6.2E | Additional requirement for single band 8C-HSDPA (Out-of-band blocking)..... | 135 | +| 7.6.2F | Additional requirement for single band NC-4C-HSDPA (Out-of-band blocking)..... | 136 | +| 7.6.3 | Minimum requirement (Narrow band blocking)..... | 137 | +| 7.6.3A | Additional requirement for DC-HSDPA and DB-DC-HSDPA (Narrow band blocking)..... | 137 | +| 7.6.3B | Additional requirement for DC-HSUPA (Narrow band blocking)..... | 138 | +| 7.6.3C | Additional requirement for single band 4C-HSDPA (Narrow band blocking)..... | 138 | +| 7.6.3C.1 | Single uplink operation..... | 138 | +| 7.6.3C.2 | Dual uplink operation..... | 139 | +| 7.6.3D | Additional requirement for dual band 4C-HSDPA (Narrow band blocking)..... | 139 | +| 7.6.3D.1 | Single uplink operation..... | 140 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.6.3D.2 | Dual uplink operation..... | 140 | +| 7.6.3E | Additional requirement for single band NC-4C-HSDPA (Narrow band blocking)..... | 141 | +| 7.6.3E.1 | Single uplink operation..... | 141 | +| 7.6.3E.2 | Dual uplink operation..... | 142 | +| 7.7 | Spurious response..... | 143 | +| 7.7.1 | Minimum requirement..... | 143 | +| 7.7.2 | Additional requirement for DC-HSDPA, DB-DC-HSDPA, single band/dual band 4C-HSDPA and single band 8C-HSDPA and single band NC-4C-HSDPA..... | 144 | +| 7.8 | Intermodulation characteristics..... | 144 | +| 7.8.1 | Minimum requirement..... | 144 | +| 7.8.1A | Additional requirement for DC-HSDPA and DB-DC-HSDPA..... | 145 | +| 7.8.1B | Additional requirement for DC-HSUPA..... | 145 | +| 7.8.1C | Additional requirement for single band 4C-HSDPA..... | 146 | +| 7.8.1C.1 | Single uplink operation..... | 146 | +| 7.8.1C.2 | Dual uplink operation..... | 147 | +| 7.8.1D | Additional requirement for dual band 4C-HSDPA..... | 148 | +| 7.8.1D.1 | Single uplink operation..... | 148 | +| 7.8.1D.2 | Dual uplink operation..... | 149 | +| 7.8.1E | Additional requirement for single band 8C-HSDPA..... | 150 | +| 7.8.1E.1 | Single uplink operation..... | 150 | +| 7.8.1E.2 | Dual uplink operation..... | 151 | +| 7.8.1F | Additional requirement for single band NC-4C-HSDPA..... | 152 | +| 7.8.1F.1 | Single uplink operation..... | 152 | +| 7.8.1F.2 | Dual uplink operation..... | 152 | +| 7.8.2 | Minimum requirement (Narrow band)..... | 153 | +| 7.8.2A | Additional requirement for DC-HSDPA and DB-DC-HSDPA (Narrow band)..... | 154 | +| 7.8.2B | Additional requirement for DC-HSUPA (Narrow band)..... | 154 | +| 7.8.2C | Additional requirement for single band 4C-HSDPA (Narrow band)..... | 155 | +| 7.8.2C.1 | Single uplink operation..... | 155 | +| 7.8.2C.2 | Dual uplink operation..... | 156 | +| 7.8.2D | Additional requirement for dual band 4C-HSDPA (Narrow band)..... | 156 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------------|-----| +| 7.8.2D.1 | Single uplink operation..... | 156 | +| 7.8.2D.2 | Dual uplink operation..... | 157 | +| 7.8.2E | Additional requirement for single band NC-4C-HSDPA (Narrow band)..... | 159 | +| 7.8.2E.1 | Single uplink operation..... | 159 | +| 7.8.2E.2 | Dual uplink operation..... | 159 | +| 7.9 | Spurious emissions..... | 160 | +| 7.9.1 | Minimum requirement..... | 160 | +| 7.9.1A | Minimum requirement..... | 161 | +| 7.10 | Reference input power adjustment for a dual band device..... | 162 | +| 8 | Performance requirement..... | 162 | +| 8.1 | General..... | 162 | +| 8.2 | Demodulation in static propagation conditions..... | 163 | +| 8.2.1 | (void)..... | 163 | +| 8.2.2 | (void)..... | 163 | +| 8.2.3 | Demodulation of Dedicated Channel (DCH)..... | 163 | +| 8.2.3.1 | Minimum requirement..... | 163 | +| 8.2.4 | Demodulation of Dedicated Channel (DCH) when DL_DCH_FET_Config [10] is configured by higher layers..... | 163 | +| 8.2.4.1 | Minimum requirement..... | 164 | +| 8.3 | Demodulation of DCH in multi-path fading propagation conditions..... | 164 | +| 8.3.1 | Single Link Performance..... | 164 | +| 8.3.1.1 | Minimum requirement..... | 164 | +| 8.3.2 | Single Link Performance when DL_DCH_FET_Config [10] is configured by higher layers..... | 167 | +| 8.3.2.1 | Minimum requirement..... | 167 | +| 8.4 | Demodulation of DCH in moving propagation conditions..... | 169 | +| 8.4.1 | Single link performance..... | 169 | +| 8.4.1.1 | Minimum requirement..... | 169 | +| 8.5 | Demodulation of DCH in birth-death propagation conditions..... | 170 | +| 8.5.1 | Single link performance..... | 170 | +| 8.5.1.1 | Minimum requirement..... | 170 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.5A | Demodulation of DCH in high speed train condition..... | 170 | +| 8.5A.1 | General..... | 170 | +| 8.5A.2 | Minimum requirement..... | 170 | +| 8.6 | Demodulation of DCH in downlink Transmit diversity modes..... | 171 | +| 8.6.1 | Demodulation of DCH in open-loop transmit diversity mode..... | 171 | +| 8.6.1.1 | Minimum requirement..... | 171 | +| 8.6.2 | Demodulation of DCH in closed loop transmit diversity mode..... | 172 | +| 8.6.2.1 | Minimum requirement..... | 172 | +| 8.6.3 | (void)..... | 173 | +| 8.7 | Demodulation in Handover conditions..... | 173 | +| 8.7.1 | Demodulation of DCH in Inter-Cell Soft Handover..... | 173 | +| 8.7.1.1 | Minimum requirement..... | 173 | +| 8.7.1A | Demodulation of DCH in Inter-Cell Soft Handover when DL_DCH_FET_Config [10] is configured by higher layers..... | 174 | +| 8.7.1A.1 | Minimum requirement..... | 174 | +| 8.7.2 | Combining of TPC commands from radio links of different radio link sets..... | 175 | +| 8.7.2.1 | Minimum requirement..... | 175 | +| 8.7.2A | Combining of TPC commands from radio links of different radio link sets when DL_DCH_FET_Config [10] is configured by higher layers..... | 175 | +| 8.7.2A.1 | Minimum requirement..... | 175 | +| 8.7.2B | Combining of TPC commands from radio links of different radio link sets when DPCCH2 is configured..... | 176 | +| 8.7.2B.1 | Minimum requirement..... | 176 | +| 8.7.3 | Combining of reliable TPC commands from radio links of different radio link sets..... | 177 | +| 8.7.3.1 | Minimum requirement..... | 177 | +| 8.7.4 | Combining of reliable TPC commands from radio links of different radio link sets when DL_DCH_FET_Config [10] is configured by higher layers..... | 178 | +| 8.7.4.1 | Minimum requirement..... | 178 | +| 8.8 | Power control in downlink..... | 179 | +| 8.8.1 | Power control in the downlink, constant BLER target..... | 179 | +| 8.8.1.1 | Minimum requirements..... | 179 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------------------------|-----| +| 8.8.1A | Power control in the downlink, constant BLER target when DL_DCH_FET_Config [10] is configured by higher layers..... | 181 | +| 8.8.1A.1 | Minimum requirements..... | 181 | +| 8.8.2 | Power control in the downlink, initial convergence..... | 182 | +| 8.8.2.1 | Minimum requirements..... | 182 | +| 8.8.2A | Power control in the downlink, initial convergence when DL_DCH_FET_Config [10] is configured by higher layers..... | 184 | +| 8.8.2A.1 | Minimum requirements..... | 184 | +| 8.8.3 | Power control in downlink, wind up effects..... | 185 | +| 8.8.3.1 | Minimum requirements..... | 185 | +| 8.8.3A | Power control in downlink, wind up effects when DL_DCH_FET_Config [10] is configured by higher layers..... | 186 | +| 8.8.3A.1 | Minimum requirements..... | 186 | +| 8.8.4 | Power control in the downlink, different transport formats..... | 188 | +| 8.8.4.1 | Minimum requirements..... | 188 | +| 8.8.4A | Power control in the downlink, different transport formats..... | 189 | +| 8.8.4A.1 | Minimum requirements..... | 189 | +| 8.8.5 | Power control in the downlink for F-DPCH..... | 191 | +| 8.8.5.1 | Minimum requirements..... | 191 | +| 8.9 | Downlink compressed mode..... | 191 | +| 8.9.1 | Single link performance..... | 191 | +| 8.9.1.1 | Minimum requirements..... | 192 | +| 8.10 | Blind transport format detection..... | 192 | +| 8.10.1 | Minimum requirement..... | 192 | +| 8.11 | Detection of Broadcast channel (BCH)..... | 193 | +| 8.11.1 | Minimum requirement without transmit diversity..... | 193 | +| 8.11.2 | Minimum requirement with open loop transmit diversity..... | 194 | +| 8.11A | Detection of Broadcast channel (BCH) mapped to S-CCPCH..... | 194 | +| 8.11A.1 | Minimum requirement without transmit diversity..... | 194 | +| 8.11.2 | Minimum requirement with open loop transmit diversity..... | 195 | +| 8.12 | Demodulation of Paging Channel (PCH)..... | 195 | + +| | | | +|---------|---------------------------------------------------------------------------------------|-----| +| 8.12.1 | Minimum requirement..... | 195 | +| 8.13 | Detection of Acquisition Indicator (AI)..... | 196 | +| 8.13.1 | Minimum requirement..... | 196 | +| 8.13A | Detection of E-DCH Acquisition Indicator (E-AI)..... | 196 | +| 8.13A.1 | Minimum requirement..... | 196 | +| 8.14 | UE UL power control operation with discontinuous UL DPCCH transmission operation..... | 197 | +| 8.14.1 | Minimum requirement..... | 197 | +| 8.15 | (void)..... | 198 | +| 8.16 | (void)..... | 198 | +| 8.17 | UE UL power control operation with Algorithm 3..... | 198 | +| 8.17.1 | Minimum requirement..... | 198 | +| 9 | Performance requirement (HSDPA)..... | 199 | +| 9.1 | (void)..... | 200 | +| 9.2 | Demodulation of HS-DSCH (Fixed Reference Channel)..... | 200 | +| 9.2.1 | Single Link performance..... | 214 | +| 9.2.1.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E..... | 214 | +| 9.2.1.2 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3..... | 216 | +| 9.2.1.3 | Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5..... | 217 | +| 9.2.1.4 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E..... | 218 | +| 9.2.1.5 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E..... | 220 | +| 9.2.1.6 | Requirement 64QAM, Fixed Reference Channel (FRC) H-Set 8/8A/8B/8C/8E..... | 222 | +| 9.2.1.7 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E..... | 224 | +| 9.2.1.8 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E..... | 225 | +| 9.2.2 | Open Loop Diversity performance..... | 226 | +| 9.2.2.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E..... | 226 | +| 9.2.2.2 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E..... | 227 | +| 9.2.2.3 | Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5..... | 228 | +| 9.2.3 | Closed Loop Diversity Performance..... | 229 | +| 9.2.3.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3..... | 229 | +| 9.2.3.2 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3..... | 231 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| 9.2.3.3 | Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5..... | 232 | +| 9.2.3.4 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 6..... | 233 | +| 9.2.3.5 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 6..... | 233 | +| 9.2.4 | MIMO Performance..... | 234 | +| 9.2.4.1 | Requirement Fixed Reference Channel (FRC) H-Set 9/9A/9B/9C/9E..... | 234 | +| 9.2.4.2 | Requirement Fixed Reference Channel (FRC) H-Set 11/11A/11B/11C/11E..... | 236 | +| 9.2.4A | MIMO only with single-stream restriction Performance..... | 238 | +| 9.2.4A.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E..... | 238 | +| 9.2.4A.2 | Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E..... | 240 | +| 9.2.4B | Four Transmit Antennas MIMO Performance..... | 242 | +| 9.2.4B.1 | Requirement Fixed Reference Channel (FRC) H-Set 13A/13C..... | 242 | +| 9.2.4B.2 | Requirement Fixed Reference Channel (FRC) H-Set 14A/14C..... | 243 | +| 9.2.4C | MIMO Mode with Four Transmit Antennas Only With Dual-stream Restriction Performance..... | 244 | +| 9.2.4C.1 | Requirement Fixed Reference Channel (FRC) H-Set 9A/9C..... | 244 | +| 9.2.4C.2 | Requirement Fixed Reference Channel (FRC) H-Set 11A/11C..... | 245 | +| 9.2.5 | Multiflow HSDPA performance..... | 246 | +| 9.2.5.1 | Requirement Fixed Reference Channel (FRC) H-Set 6 16QAM/QPSK..... | 246 | +| 9.3 | Reporting of Channel Quality Indicator..... | 247 | +| 9.3.1 | Single Link Performance..... | 248 | +| 9.3.1.1 | AWGN propagation conditions..... | 248 | +| 9.3.1.1.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 248 | +| 9.3.1.1.2 | Minimum Requirement – UE HS-DSCH categories 13,14,17,18, 19 and 20..... | 248 | +| 9.3.1.1.3 | Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36..... | 249 | +| 9.3.1.2 | Fading propagation conditions..... | 250 | +| 9.3.1.2.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 250 | +| 9.3.1.2.2 | Minimum Requirement – UE HS-DSCH categories 13,14,17,18, 19 and 20..... | 251 | +| 9.3.1.2.3 | Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36..... | 252 | +| 9.3.1.3 | Periodically varying radio conditions..... | 252 | +| 9.3.1.3.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 253 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| 9.3.2 | Open Loop Diversity Performance..... | 255 | +| 9.3.2.1 | AWGN propagation conditions..... | 255 | +| 9.3.2.1.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 255 | +| 9.3.2.1.2 | Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36..... | 255 | +| 9.3.2.2 | Fading propagation conditions..... | 256 | +| 9.3.2.2.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 256 | +| 9.3.2.2.2 | Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36..... | 257 | +| 9.3.2.3 | Periodically varying radio conditions..... | 257 | +| 9.3.2.3.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 258 | +| 9.3.3 | Closed Loop Diversity Performance..... | 259 | +| 9.3.3.1 | AWGN propagation conditions..... | 259 | +| 9.3.3.1.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 259 | +| 9.3.3.2 | Fading propagation conditions..... | 260 | +| 9.3.3.2.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 260 | +| 9.3.3.3 | Periodically varying radio conditions..... | 261 | +| 9.3.3.3.1 | Minimum Requirement – UE HS-DSCH categories 1-20..... | 261 | +| 9.3.4 | MIMO Performance..... | 263 | +| 9.3.4.1 | MIMO Single Stream Fading Conditions..... | 263 | +| 9.3.4.1.1 | Minimum Requirement - UE HS-DSCH categories 15-20..... | 263 | +| 9.3.4.1.2 | Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36..... | 264 | +| 9.3.4.2 | MIMO Dual Stream Fading Conditions..... | 265 | +| 9.3.4.2.1 | Minimum Requirement – UE HS-DSCH categories 15-20..... | 266 | +| 9.3.4.2.2 | Minimum Requirement – UE HS-DSCH categories 19-20..... | 267 | +| 9.3.4.2.3 | Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36..... | 268 | +| 9.3.4.2.4 | Additional Requirement – UE HS-DSCH categories 27, 28, 30, 32 and 36..... | 270 | +| 9.3.4.3 | MIMO Dual Stream Static Orthogonal Conditions..... | 271 | +| 9.3.4.3.1 | Minimum Requirement –UE HS-DSCH categories 15-20..... | 272 | +| 9.3.4.3.2 | Minimum Requirement –UE HS-DSCH categories 19-20..... | 272 | +| 9.3.4.3.3 | Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36..... | 273 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------|-----| +| 9.3.4.3.4 | Additional Requirement – UE HS-DSCH categories 27, 28, 30, 32 and 36..... | 274 | +| 9.3.5 | MIMO only with single-stream restriction Performance..... | 275 | +| 9.3.5.1 | MIMO only with single-stream restriction Fading Conditions..... | 275 | +| 9.3.5.1.1 | Minimum Requirement..... | 275 | +| 9.3.6 | Multiflow HSDPA performance..... | 276 | +| 9.3.6.1 | Fading propagation conditions..... | 276 | +| 9.3.6.1.1 | Minimum Requirement..... | 277 | +| 9.3.7 | MIMO Performance with four transmit antennas..... | 277 | +| 9.3.7.1 | Four Streams Static Orthogonal Conditions..... | 277 | +| 9.3.7.1.1 | Minimum Requirement – UE HS-DSCH categories 37 and 38..... | 278 | +| 9.3.8 | MIMO with Four Transmit Antennas only with Dual-Stream Restriction Performance..... | 279 | +| 9.3.8.1 | MIMO with four transmit antennas only with dual-stream restriction fading conditions..... | 279 | +| 9.3.8.1.1 | Minimum Requirement..... | 280 | +| 9.4 | HS-SCCH Detection Performance..... | 281 | +| 9.4.1 | HS-SCCH Type 1 Single Link Performance..... | 282 | +| 9.4.2 | HS-SCCH Type 1 Open Loop Diversity Performance..... | 282 | +| 9.4.3 | HS-SCCH Type 3 Performance..... | 283 | +| 9.4.4 | HS-SCCH Type 3 Performance for MIMO only with single-stream restriction..... | 285 | +| 9.4.5 | HS-SCCH Type 4 Performance..... | 287 | +| 9.4.6 | HS-SCCH Type 4 Performance for MIMO mode with Four Transmit Antennas Only with Dual-stream Restriction..... | 288 | +| 9.5 | HS-SCCH-less demodulation of HS-DSCH (Fixed Reference Channel)..... | 289 | +| 9.5.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 7..... | 290 | +| 9.6 | Requirements for HS-DSCH and HS-SCCH reception in CELL_FACH state..... | 290 | +| 9.6.1 | HS-DSCH demodulation requirements (Single Link)..... | 290 | +| 9.6.1.1 | Requirement QPSK, Fixed Reference Channel (FRC) H-Set 3..... | 291 | +| 9.6.2 | HS-SCCH Detection Performance..... | 291 | +| 9.6.2.1 | HS-SCCH Type 1 Single Link Performance..... | 291 | +| 10 | Performance requirement (E-DCH)..... | 292 | +| 10.1 | General..... | 292 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------|-----| +| 10.2 | Detection of E-DCH HARQ ACK Indicator Channel (E-HICH)..... | 292 | +| 10.2.1 | Single link performance..... | 292 | +| 10.2.1.1 | Performance requirement..... | 292 | +| 10.2.2 | Detection in Inter-Cell Handover conditions..... | 293 | +| 10.2.2.1 | Performance requirement for RLS not containing the Serving E-DCH cell..... | 293 | +| 10.2.2.2 | Performance requirement for RLS containing the serving E-DCH cell..... | 295 | +| 10.3 | Detection of E-DCH Relative Grant Channel (E-RGCH)..... | 296 | +| 10.3.1 | Single link performance..... | 296 | +| 10.3.1.1 | Performance requirement..... | 296 | +| 10.3.2 | Detection in Inter-Cell Handover conditions..... | 298 | +| 10.3.2.1 | Performance requirement for Non-serving E-DCH RL..... | 298 | +| 10.3A | Determination of common E-RGCH radio links in CELL_FACH state..... | 299 | +| 10.3A.1 | Introduction..... | 299 | +| 10.3A.2 | Requirements..... | 299 | +| 10.3A.2.1 | Determination when a cell for common E-RGCH RL has been already identified..... | 299 | +| 10.3A.2.2 | Determination when a cell for common E-RGCH RL has not been identified..... | 300 | +| 10.4 | Demodulation of E-DCH Absolute Grant Channel (E-AGCH)..... | 301 | +| 10.4.1 | Single link performance..... | 301 | +| 10.4.1.1 | Performance requirement..... | 302 | +| 10.4A | Demodulation of E-DCH Absolute Grant Channel (E-AGCH) with Time Multiplexed UE grants..... | 302 | +| 10.4A.1 | Single link performance..... | 302 | +| 10.4A.1.1 | Performance requirement..... | 302 | +| 11 | Performance requirement (MBMS)..... | 303 | +| 11.1 | Demodulation of MCCH..... | 304 | +| 11.1.1 | Minimum requirement..... | 304 | +| 11.1.2 | Minimum requirement for MBSFN..... | 304 | +| 11.2 | Demodulation of MTCH..... | 305 | +| 11.2.1 | Minimum requirement..... | 305 | +| 11.2.2 | Minimum requirement for MBSFN..... | 305 | +| 11.3 | Demodulation of MTCH and cell identification..... | 306 | + +| | | | +|-----------------------------|---------------------------------------------------------------------------------|------------| +| 11.3.1 | Minimum requirement..... | 306 | +| Annex A (normative): | Measurement channels..... | 307 | +| A.1 | General..... | 307 | +| A.2 | UL reference measurement channel..... | 307 | +| A.2.1 | UL reference measurement channel (12.2 kbps)..... | 307 | +| A.2.2 | UL reference measurement channel (64 kbps)..... | 308 | +| A.2.3 | UL reference measurement channel (144 kbps)..... | 309 | +| A.2.4 | UL reference measurement channel (384 kbps)..... | 310 | +| A.2.5 | UL reference measurement channel (768 kbps)..... | 311 | +| A.2.5A | UL reference measurement channel (768 kbps)..... | 311 | +| A.2.6 | UL E-DCH reference measurement channel for DC-HSUPA using BPSK modulation..... | 312 | +| A.2.7 | UL E-DCH reference measurement channel for DC-HSUPA using 16QAM modulation..... | 313 | +| A.2.8 | Combinations of UL E-DCH reference measurement channel for DC-HSUPA tests..... | 314 | +| A.3 | DL reference measurement channel..... | 314 | +| A.3.0 | DL reference measurement channel (0 kbps)..... | 314 | +| A.3.1 | DL reference measurement channel (12.2 kbps)..... | 315 | +| A.3.2 | DL reference measurement channel (64 kbps)..... | 316 | +| A.3.3 | DL reference measurement channel (144 kbps)..... | 317 | +| A.3.4 | DL reference measurement channel (384 kbps)..... | 318 | +| A.3.5 | DL reference measurement channel 2 (64 kbps)..... | 319 | +| A.3A | DL reference measurement channel..... | 320 | +| A.3A.0 | DL reference measurement channel (0 kbps without DCCH)..... | 320 | +| A.3A.1 | DL reference measurement channel (0 kbps with DCCH)..... | 321 | +| A.3A.2 | DL reference measurement channel (12.2 kbps without DCCH)..... | 322 | +| A.3A.3 | DL reference measurement channel (12.2 kbps with DCCH)..... | 323 | + +| | | | +|----------|-------------------------------------------------------------------------|-----| +| A.4 | DL reference measurement channel for BTFD performance requirements..... | 325 | +| A.4A | Reference parameters for discontinuous UL DPCCH transmission..... | 327 | +| A.5 | DL reference compressed mode parameters..... | 327 | +| A.6 | DL reference parameters for PCH tests..... | 329 | +| A.7 | DL reference channel parameters for HSDPA tests..... | 330 | +| A.7.1 | Fixed Reference Channel (FRC)..... | 330 | +| A.7.1.1 | Fixed Reference Channel Definition H-Set 1/1A/1B/1C/1E..... | 330 | +| A.7.1.2 | Fixed Reference Channel Definition H-Set 2..... | 331 | +| A.7.1.3 | Fixed Reference Channel Definition H-Set 3/3A/3B/3C/3E..... | 332 | +| A.7.1.4 | Fixed Reference Channel Definition H-Set 4..... | 333 | +| A.7.1.5 | Fixed Reference Channel Definition H-Set 5..... | 334 | +| A.7.1.6 | Fixed Reference Channel Definition H-Set 6/6A/6B/6C/6E..... | 335 | +| A.7.1.7 | Fixed Reference Channel Definition H-Set 7..... | 336 | +| A.7.1.8 | Fixed Reference Channel Definition H-Set 8/8A/8B/8C/8E..... | 337 | +| A.7.1.9 | Fixed Reference Channel Definition H-Set 9/9A/9B/9C/9E..... | 338 | +| A.7.1.10 | Fixed Reference Channel Definition H-Set 10/10A/10B/10C/10E..... | 339 | +| A.7.1.11 | Fixed Reference Channel Definition H-Set 11/11A/11B/11C/11E..... | 341 | +| A.7.1.12 | Fixed Reference Channel Definition H-Set 12..... | 342 | +| A.7.1.13 | Fixed Reference Channel Definition H-Set 13/13A/13C..... | 343 | +| A.7.1.14 | Fixed Reference Channel Definition H-Set 14/14A/14C..... | 344 | +| A.8 | DL reference parameters for MBMS tests..... | 345 | +| A.8.1 | MCCH..... | 345 | +| A.8.1 | MTCH..... | 346 | + +| | | | +|------------------------------|-------------------------------------------------------------------------------------|------------| +| A.9 | DL reference parameters for combined MTCH demodulation and cell identification..... | 346 | +| Annex B (normative) : | Propagation conditions..... | 348 | +| B.1 | (void)..... | 348 | +| B.2 | Propagation Conditions..... | 348 | +| B.2.1 | Static propagation condition..... | 348 | +| B.2.2 | Multi-path fading propagation conditions..... | 348 | +| B.2.3 | Moving propagation conditions..... | 351 | +| B.2.4 | Birth-Death propagation conditions..... | 352 | +| B.2.5 | High speed train condition..... | 352 | +| B.2.6 | MIMO propagation conditions..... | 353 | +| B.2.6.1 | MIMO Single Stream Fading Conditions..... | 354 | +| B.2.6.2 | MIMO Dual Stream Fading Conditions..... | 355 | +| B.2.6.3 | MIMO Dual Stream Static Orthogonal Conditions..... | 356 | +| B.2.7 | Propagation conditions for MIMO with four transmit antennas..... | 356 | +| B.2.7.1 | MIMO with Four Transmit Antennas and Four Streams Static Orthogonal Conditions..... | 357 | +| B.2.7.2 | MIMO with Four Transmit Antennas Only With Dual Stream Fading Conditions..... | 357 | +| Annex C (normative): | Downlink Physical Channels..... | 358 | +| C.1 | General..... | 358 | +| C.2 | Connection Set-up..... | 358 | +| C.3 | During connection..... | 358 | +| C.3.1 | Measurement of Rx Characteristics..... | 358 | +| C.3.2 | Measurement of Performance requirements..... | 359 | +| C.3.3 | Connection with open-loop transmit diversity mode..... | 360 | +| C.3.4 | Connection with closed loop transmit diversity mode..... | 360 | +| C.3.5 | (void)..... | 361 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------|------------| +| C.4 | W-CDMA Modulated Interferer..... | 361 | +| C.5 | HSDPA DL Physical channels..... | 362 | +| C.5.1 | Downlink Physical Channels connection set-up..... | 362 | +| C.5.2 | OCNS Definition..... | 372 | +| C.5.3 | Test Definition for Enhanced Performance Type 3i..... | 373 | +| C.5.3.1 | Transmitted code and power characteristics for serving cell..... | 373 | +| C.5.3.2 | Transmitted code and power characteristics for interfering cells..... | 375 | +| C.5.3.3 | Model for power control sequence generation..... | 376 | +| C.5.4 | Simplified Multi Carrier HSDPA testing method..... | 376 | +| C.5.4A | Simplified Multiflow HSDPA testing method..... | 377 | +| C.5.5 | Test Definition for Multiflow HSDPA..... | 377 | +| C.5.5.1 | Test configuration when 2 cells are configured in Multiflow mode..... | 377 | +| C.5.5.2 | Test configuration when 3 cells are configured in Multiflow mode..... | 379 | +| C.5.5.3 | Test configuration when 4 cells are configured in Multiflow mode..... | 379 | +| C.6 | MBMS DL Physical channels..... | 380 | +| C.6.1 | Downlink Physical Channels connection set-up..... | 380 | +| C.6.2 | Downlink Physical Channels connection set-up for MBSFN..... | 380 | +| Annex D (normative) : | Environmental conditions..... | 381 | +| D.1 | General..... | 381 | +| D.2 | Environmental requirements..... | 381 | +| D.2.1 | Temperature..... | 381 | +| D.2.2 | Voltage..... | 381 | +| D.2.3 | Vibration..... | 382 | +| Annex E (informative): | UARFCN numbers..... | 383 | +| E.1 | General..... | 383 | +| E.2 | List of UARFCN used for UTRA FDD bands..... | 383 | +| Annex F (informative): | Change history..... | 387 | + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document establishes the minimum RF characteristics of the FDD mode of UTRA for the User Equipment (UE). + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] (void) +- [2] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [3] (void) +- [4] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling". +- [5] ETSI ETR 273: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [6] 3GPP TS 45.004: "Modulation". +- [7] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". +- [8] 3GPP TS25.214: "Physical layer procedures (FDD)". +- [9] 3GPP TS 25.307: "Requirements on User Equipments (UEs) supporting a release-independent frequency band". +- [10] 3GPP TS25.212:" Multiplexing and channel coding (FDD)". +- [11] 3GPP TS 36.101: "E-UTRA User Equipment (UE) radio transmission and reception". + +--- + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions apply: + +**Assisting secondary serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the secondary downlink frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Assisting serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the same frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Cell group:** A group of (one, two or three) Multiflow mode cells that have the same CPICH timing. The cells that belong to a cell group are indicated by higher layers. + +**Enhanced performance requirements type 1:** This defines performance requirements which are optional for the UE. The requirements are based on UEs which utilise receiver diversity. + +**Enhanced performance requirements type 2:** This defines performance requirements which are optional for the UE. The requirements are based on UEs which utilise a chip equaliser receiver structure. + +**Enhanced performance requirements type 3:** This defines performance requirements which are optional for the UE. The requirements are based on UEs which utilise a chip equaliser receiver structure with receiver diversity. + +**Enhanced performance requirements type 3i:** This defines performance requirements which are optional for the UE. The requirements are based on UEs which utilise an interference-aware chip equaliser receiver structure with receiver diversity. + +**Power Spectral Density:** The units of Power Spectral Density (PSD) are extensively used in this document. PSD is a function of power versus frequency and when integrated across a given bandwidth, the function represents the mean power in such a bandwidth. When the mean power is normalised to (divided by) the chip-rate it represents the mean energy per chip. Some signals are directly defined in terms of energy per chip, (DPCH\_Ec, Ec, OCNS\_Ec and S-CCPCH\_Ec) and others defined in terms of PSD (Io, Ioc, Ior and $\hat{I}_{or}$ ). There also exist quantities that are a ratio of energy per chip to PSD (DPCH\_Ec/Ior, Ec/Ior etc.). This is the common practice of relating energy magnitudes in communication systems. + +It can be seen that if both energy magnitudes in the ratio are divided by time, the ratio is converted from an energy ratio to a power ratio, which is more useful from a measurement point of view. It follows that an energy per chip of X dBm/3.84 MHz can be expressed as a mean power per chip of X dBm. Similarly, a signal PSD of Y dBm/3.84 MHz can be expressed as a signal power of Y dBm. + +**Maximum Output Power:** This is a measure of the maximum power the UE can transmit (i.e. the actual power as would be measured assuming no measurement error) in a bandwidth of at least $(1 + \alpha)$ times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot. For DC-HSUPA the maximum output power is defined by the sum of the broadband transmit power of each carrier in the UE. + +**Mean power:** When applied to a W-CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least $(1 + \alpha)$ times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot unless otherwise stated. + +**Multiflow mode:** The UE is configured in Multiflow mode when it is configured with assisting serving HS-DSCH cell. + +**Nominal Maximum Output Power:** This is the nominal power defined by the UE power class. + +**Primary uplink frequency:** If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequency is configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**RRC filtered mean power:** The mean power as measured through a root raised cosine filter with roll-off factor $\alpha$ and a bandwidth equal to the chip rate of the radio access mode. + +NOTE 1: The RRC filtered mean power of a perfectly modulated W-CDMA signal is 0.246 dB lower than the mean power of the same signal. + +NOTE 2: The roll-off factor $\alpha$ is defined in section 6.8.1. + +**Secondary serving HS-DSCH cell(s):** In addition to the serving HS-DSCH cell, the set of cells where the UE is configured to simultaneously monitor an HS-SCCH set and receive the HS-DSCH if it is scheduled in that cell. There can be up to 7 secondary serving HS-DSCH cells. + +**Secondary uplink frequency:** A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**Time reference cell:** The (Serving or Assisting Serving, but not Secondary Serving or Assisting Secondary Serving) HS-DSCH cell that carries the HS-PDSCH acting as the time reference for the uplink HS-DPCCH when in Multiflow mode. There is one and only one Time reference cell. + +**Throughput:** Number of information bits per second excluding CRC bits successfully received on HS-DSCH by a HSDPA capable UE. + +**1st secondary serving HS-DSCH cell:** If the UE is configured with two uplink frequencies, the 1st secondary serving HS-DSCH cell is the secondary serving HS-DSCH cell that is associated with the secondary uplink frequency. If the UE is configured with a single uplink frequency, the 1st secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 4C-HSDPA | Four-Carrier HSDPA. HSDPA operation configured on 3 or 4 DL carriers. | +| ACLR | Adjacent Channel Leakage power Ratio | +| ACS | Adjacent Channel Selectivity | +| AICH | Acquisition Indication Channel | +| BER | Bit Error Ratio | +| BLER | Block Error Ratio | +| CQI | Channel Quality Indicator | +| CW | Continuous Wave (un-modulated signal) | +| DB-DC-HSDPA | Dual Band Dual Cell HSDPA | +| DB-DC-HSUPA | Dual Band Dual Cell HSUPA | +| DC-HSUPA | Dual Cell HSUPA | +| DCH | Dedicated Channel, which is mapped into Dedicated Physical Channel. | +| DIP | Dominant Interferer Proportion ratio | +| DL | Down Link (forward link) | +| DTX | Discontinuous Transmission | +| DPCCH | Dedicated Physical Control Channel | +| DPCH | Dedicated Physical Channel | +| DPCH_ $E_c$ | Average energy per PN chip for DPCH. | +| $\frac{DPCH\_E_c}{I_{or}}$ | The ratio of the transmit energy per PN chip of the DPCH to the total transmit power spectral density at the Node B antenna connector. | +| DPDCH | Dedicated Physical Data Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced Dedicated Channel | +| E-DPCCH | E-DCH Dedicated Physical Control Channel | +| E-DPDCH | E-DCH Dedicated Physical Data Channel | +| E-HICH | E-DCH HARQ ACK Indicator Channel | +| E-RGCH | E-DCH Relative Grant Channel | + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EIRP | Effective Isotropic Radiated Power | +| $E_c$ | Average energy per PN chip. | +| $\frac{E_c}{I_{or}}$ | The ratio of the average transmit energy per PN chip for different fields or physical channels to the total transmit power spectral density. | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| FDR | False transmit format Detection Ratio. A false Transport Format detection occurs when the receiver detects a different TF to that which was transmitted, and the decoded transport block(s) for this incorrect TF passes the CRC check(s). | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| $F_{uw}$ | Frequency of unwanted signal. This is specified in bracket in terms of an absolute frequency(s) or a frequency offset from the assigned channel frequency. For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells. | +| HARQ | Hybrid Automatic Repeat Request | +| HSDPA | High Speed Downlink Packet Access | +| HSUPA | High Speed Uplink Packet Access | +| HS-DPCCH | Dedicated Physical Control Channel (uplink) for HS-DSCH | +| HS-DPCCH 2 | Secondary Dedicated Physical Control Channel (uplink) for HS-DSCH, when Secondary_Cell_Enabled is greater than 3 | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | High Speed Shared Control Channel | +| Information Data Rate | Rate of the user information, which must be transmitted over the Air Interface. For example, output rate of the voice codec. | +| $I_o$ | The total received power spectral density, including signal and interference, as measured at the UE antenna connector. | +| $I_{oc}$ | The power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of a band limited white noise source (simulating interference from cells, which are not defined in a test procedure) as measured at the UE antenna connector. For DC-HSDPA and DB-DC-HSDPA, $I_{oc}$ is defined for each of the cells individually and is assumed to be equal for both cells unless explicitly stated per cell. | +| $I_{oc}'$ | The received power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of the summation of the received power spectral densities of the two strongest interfering cells plus $I_{oc}$ as measured at the UE antenna connector. The respective power spectral density of each interfering cell relative to $I_{oc}'$ is defined by its associated DIP value. The power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of a band limited white noise source (simulating Node B transmitter impairments) as measured at the Node B transmit antenna connector(s). For DC-HSDPA and DB-DC-HSDPA, is defined for each of the cells individually and is assumed to be equal for both cells unless explicitly stated per cell. | +| $I_{or}$ | The total transmit power spectral density (integrated in a bandwidth of $(1+\alpha)$ times the chip rate and normalized to the chip rate) of the downlink signal at the Node B antenna connector. For DC-HSDPA and DB-DC-HSDPA, $I_{or}$ is defined for each of the cells individually and is assumed to be equal for both cells unless explicitly stated per cell. | + +| | | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\hat{I}_{or}$ | The received power spectral density (integrated in a bandwidth of $(1+\alpha)$ times the chip rate and normalized to the chip rate) of the downlink signal as measured at the UE antenna connector. For DC-HSDPA and DB-DC-HSDPA, $\hat{I}_{or}$ is defined for each of the cells individually and is assumed to be equal for both cells unless explicitly stated per cell. | +| MBSFN | MBMS over a Single Frequency Network | +| MER | Message Error Ratio | +| MIMO | Multiple Input Multiple Output | +| NC-4C-HSDPA | Non-Contiguous Four-Carrier HSDPA. HSDPA operation configured on 2, 3 or 4 DL carriers with two non contiguous subblocks of adjacent carriers. | +| Node B | A logical node responsible for radio transmission / reception in one or more cells to/from the User Equipment. Terminates the Iub interface towards the RNC | +| OCNS | Orthogonal Channel Noise Simulator, a mechanism used to simulate the users or control signals on the other orthogonal channels of a downlink link. | +| OCNS_E c | Average energy per PN chip for the OCNS. | +| $\frac{OCNS\_E_c}{I_{or}}$ | The ratio of the average transmit energy per PN chip for the OCNS to the total transmit power spectral density. | +| P-CCPCH | Primary Common Control Physical Channel | +| PCH | Paging Channel | +| $P\_CCPCH \frac{E_c}{I_o}$ | The ratio of the received P-CCPCH energy per chip to the total received power spectral density at the UE antenna connector. | +| $\frac{P\_CCPCH\_E_c}{I_{or}}$ | The ratio of the average transmit energy per PN chip for the P-CCPCH to the total transmit power spectral density. | +| P-CPICH | Primary Common Pilot Channel | +| PICH | Paging Indicator Channel | +| PPM | Parts Per Million | +| R | Number of information bits per second excluding CRC bits successfully received on HS-DSCH by a HSDPA capable UE. | +| | Reference sensitivity | +| $\langle REF \hat{I}_{or} \rangle$ | Reference $\hat{I}_{or}$ | +| RACH | Random Access Channel | +| SCH | Synchronization Channel consisting of Primary and Secondary synchronization channels | +| $S\_CCPCH$ | Secondary Common Control Physical Channel. | +| $S\_CCPCH\_E_c$ | Average energy per PN chip for S-CCPCH. | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| S-E-DPCCH | Secondary Dedicated Physical Control Channel for E-DCH | +| S-E-DPDCH | Secondary Dedicated Physical Data Channel for E-DCH | +| SG | Serving Grant | +| SIR | Signal to Interference ratio | +| SML | Soft Metric Location (Soft channel bit) | +| STTD | Space Time Transmit Diversity | +| TDD | Time Division Duplexing | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TPC | Transmit Power Control | +| TPI | Transmitted Precoding Indicator | +| TSTD | Time Switched Transmit Diversity | +| UE | User Equipment | + +| | | +|---------|----------------------------------------| +| UL | Up Link (reverse link) | +| UL CLTD | Up Link Closed-Loop Transmit Diversity | +| UL OLTD | Up Link Open-Loop Transmit Diversity | +| UTRA | UMTS Terrestrial Radio Access | + +--- + +## 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 34.121 Annex F defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. + +The measurement results returned by the test system are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ETR 273 Part 1 sub-part 2 section 6.5. + +### 4.2 Power Classes + +For UE power classes 1 and 2, a number of RF parameter are not specified. It is intended that these are part of a later release. + +### 4.3 Control and monitoring functions + +This requirement verifies that the control and monitoring functions of the UE prevent it from transmitting if no acceptable cell can be found by the UE. + +#### 4.3.1 Minimum requirement + +The power of the UE, as measured with a thermal detector, shall not exceed -30dBm if no acceptable cell can be found by the UE. + +### 4.4 RF requirements in later releases + +The standardisation of new frequency bands may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band of operation that is specified in a later release, it is necessary to specify some extra requirements. TS 25.307 [9] specifies requirements on UEs supporting a frequency band that is independent of release. + +NOTE: For UEs conforming to the 3GPP release of the present document, some RF requirements of later releases may be mandatory independent of whether the UE supports the bands specified in later releases or not. The set of RF requirements of later releases that is also mandatory for UEs conforming to the 3GPP release of the present document is determined by regional regulation. + +## 5 Frequency bands and channel arrangement + +### 5.1 General + +The information presented in this subclause is based on a chip rate of 3.84 Mcps. + +NOTE: Other chip rates may be considered in future releases. + +### 5.2 Frequency bands + +a) UTRA/FDD is designed to operate in the following paired bands: + +**Table 5.0: UTRA FDD frequency bands** + +| Operating Band | UL Frequencies
UE transmit, Node B receive | DL frequencies
UE receive, Node B transmit | +|--------------------|-----------------------------------------------|-----------------------------------------------| +| I | 1920 - 1980 MHz | 2110 - 2170 MHz | +| II | 1850 - 1910 MHz | 1930 - 1990 MHz | +| III | 1710-1785 MHz | 1805-1880 MHz | +| IV | 1710-1755 MHz | 2110-2155 MHz | +| V | 824 - 849 MHz | 869-894 MHz | +| VI | 830-840 MHz | 875-885 MHz | +| VII | 2500-2570 MHz | 2620-2690 MHz | +| VIII | 880 - 915 MHz | 925 - 960 MHz | +| IX | 1749.9-1784.9 MHz | 1844.9-1879.9 MHz | +| X | 1710-1770 MHz | 2110-2170 MHz | +| XI | 1427.9 - 1447.9 MHz | 1475.9 - 1495.9 MHz | +| XII | 699 - 716 MHz | 729 - 746 MHz | +| XIII | 777 - 787 MHz | 746 - 756 MHz | +| XIV | 788 - 798 MHz | 758 - 768 MHz | +| XV | Reserved | Reserved | +| XVI | Reserved | Reserved | +| XVII | Reserved | Reserved | +| XVIII | Reserved | Reserved | +| XIX | 830 - 845 MHz | 875 - 890 MHz | +| XX | 832 - 862 MHz | 791 - 821 MHz | +| XXI | 1447.9 - 1462.9 MHz | 1495.9 - 1510.9 MHz | +| XXII | 3410 - 3490 MHz | 3510 - 3590 MHz | +| XXV | 1850 - 1915 MHz | 1930 - 1995 MHz | +| XXVI | 814 - 849 MHz | 859 - 894 MHz | +| XXXII 1 | N/A | 1452 - 1496 MHz | + +NOTE 1: Restricted to UTRA operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA). The down link frequenc(ies) of this band are paired with the uplink frequenc(ies) of the other FDD band (external) of the dual band configuration. + +b) Deployment in other frequency bands is not precluded + +c) DB-DC-HSDPA is designed to operate in the following configurations: + +**Table 5.0aA DB-DC-HSDPA configurations** + +| DB-DC-HSDPA Configuration | UL Band | DL Band A | DL Band B | +|---------------------------|-----------|-----------|-----------| +| 1 | I or VIII | I | VIII | +| 2 | II or IV | II | IV | +| 3 | I or V | I | V | +| 4 | I or XI | I | XI | +| 5 | II or V | II | V | +| 6 | I | I | XXXII | + +d) Single band 4C-HSDPA is designed to operate in the following configurations: + +**Table 5.0aB Single band 4C-HSDPA configurations** + +| Single band 4C-HSDPA Configuration | Operating Band | Number of DL carriers | +|-------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------| +| I-3 | I | 3 | +| II-3 | II | 3 | +| II-4 | II | 4 | +| NOTE: Single band 4C-HSDPA configuration is numbered as (X-M) where X denotes the operating band and M denotes the number of DL carriers. | | | + +e) Dual band 4C-HSDPA is designed to operate in the following configurations: + +**Table 5.0aC Dual band 4C-HSDPA configurations** + +| Dual band 4C-HSDPA Configuration | UL Band | DL Band A | Number of DL carriers in Band A | DL Band B | Number of DL carriers in Band B | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|---------------------------------|-----------|---------------------------------| +| I-2-VIII-1 | I or VIII | I | 2 | VIII | 1 | +| I-2-VIII-2 | I or VIII | I | 2 | VIII | 2 | +| I-1-VIII-2 | I or VIII | I | 1 | VIII | 2 | +| I-3-VIII-1 | I or VIII | I | 3 | VIII | 1 | +| II-1-IV-2 | II or IV | II | 1 | IV | 2 | +| II-2-IV-1 | II or IV | II | 2 | IV | 1 | +| II-2-IV-2 | II or IV | II | 2 | IV | 2 | +| I-1-V-2 | I or V | I | 1 | V | 2 | +| I-2-V-1 | I or V | I | 2 | V | 1 | +| I-2-V-2 | I or V | I | 2 | V | 2 | +| II-1-V-2 | II or V | II | 1 | V | 2 | +| I-1-XXXII-2 | I | I | 1 | XXXII | 2 | +| I-2-XXXII-1 | I | I | 2 | XXXII | 1 | +| NOTE: Dual band 4C-HSDPA configuration is numbered as (X-M-Y-N) where X denotes the DL Band A, M denotes the number DL carriers in the DL Band A, Y denotes the DL Band B, and N denotes the number of DL carriers in the DL Band B | | | | | | + +f) Single band 8C-HSDPA is designed to operate in the following configurations: + +**Table 5.0aD Single band 8C-HSDPA configurations** + +| Single band 8C-HSDPA Configuration | Operating Band | Number of DL carriers | +|-------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------| +| I-8 | I | 8 | +| NOTE: Single band 8C-HSDPA configuration is numbered as (X-M) where X denotes the operating band and M denotes the number of DL carriers. | | | + +g) Single band NC-4C-HSDPA is designed to operate in the following configurations: + +**Table 5.0aE Single band NC-4C-HSDPA configurations** + +| Single band NC-4C-HSDPA Configuration | Operating Band | Number of DL carriers in one subblock | Gap between subblocks [MHz] | Number of DL carriers in the other subblock | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------------------------------|-----------------------------|---------------------------------------------| +| I-1-5-1 | I | 1 | 5 | 1 | +| I-2-5-1 | I | 2 | 5 | 1 | +| I-3-10-1 | I | 3 | 10 | 1 | +| IV-1-5-1 | IV | 1 | 5 | 1 | +| IV-2-10-1 | IV | 2 | 10 | 1 | +| IV-2-15-2 | IV | 2 | 15 | 2 | +| IV-2-20-1 | IV | 2 | 20 | 1 | +| IV-2-25-2 | IV | 2 | 25 | 2 | +| NOTE: Single band NC-4C-HSDPA configuration is numbered as (X-M-Y-N) where X denotes the operating band, M denotes the number of DL carriers in one subblock, Y denotes the gap between subblocks in MHz and N denotes the number of DL carriers in the other subblock. M and N can be switched | | | | | + +h) DB-DC-HSUPA is designed to operate in the following configurations: + +**Table 5.0aF: Dual Band HSUPA Configurations** + +| Dual band HSUPA Configuration together with DB-DC-HSDPA/D B-4C-HSDPA | UL Band A/B | Number of UL carriers in Band A/B | DL Band A | Number of DL carriers in Band A | DL Band B | Number of DL carriers in Band B | +|----------------------------------------------------------------------|-------------|-----------------------------------|-----------|---------------------------------|-----------|---------------------------------| +| I-1-VIII-1 | I and VIII | 1 | I | 1 | VIII | 1 | +| I-2-VIII-1 | I and VIII | 1 | I | 2 | VIII | 1 | +| I-2-VIII-2 | I and VIII | 1 | I | 2 | VIII | 2 | +| I-1-VIII-2 | I and VIII | 1 | I | 1 | VIII | 2 | +| I-3-VIII-1 | I and VIII | 1 | I | 3 | VIII | 1 | +| I-1-V-1 | I and V | 1 | I | 1 | V | 1 | +| I-1-V-2 | I and V | 1 | I | 1 | V | 2 | +| I-2-V-1 | I and V | 1 | I | 2 | V | 1 | +| I-2-V-2 | I and V | 1 | I | 2 | V | 2 | +| II-1-V-1 | II and V | 1 | II | 1 | V | 1 | +| II-1-V-2 | II and V | 1 | II | 1 | V | 2 | + +## 5.3 TX-RX frequency separation + +a) UTRA/FDD is designed to operate with the following TX-RX frequency separation + +**Table 5.0A: TX-RX frequency separation** + +| Operating Band | TX-RX frequency separation | +|-----------------------|-----------------------------------| +| I | 190 MHz | +| II | 80 MHz. | +| III | 95 MHz. | +| IV | 400 MHz | +| V | 45 MHz | +| VI | 45 MHz | +| VII | 120 MHz | +| VIII | 45 MHz | +| IX | 95 MHz | +| X | 400 MHz | +| XI | 48 MHz | +| XII | 30 MHz | +| XIII | 31 MHz | +| XIV | 30 MHz | +| XIX | 45 MHz | +| XX | 41 MHz | +| XXI | 48 MHz | +| XXII | 100 MHz | +| XXV | 80 MHz | +| XXVI | 45MHz | + +- b) UTRA/FDD can support both fixed and variable transmit to receive frequency separation. +- c) The use of other transmit to receive frequency separations in existing or other frequency bands shall not be precluded. +- d) When configured to operate on dual cells in the DL with a single UL frequency, the TX-RX frequency separation in Table 5.0A shall be applied for the serving HS-DSCH cell. For bands XII, XIII and XIV, the TX-RX frequency separation in Table 5.0A shall be the minimum spacing between the UL and either of the DL carriers. +- e) When configured to operate on dual cells in both the DL and UL, the TX-RX frequency separation in Table 5.0A shall be applied to the primary UL frequency and DL frequency of the serving HS-DSCH cell, and to the secondary UL frequency and the frequency of the secondary serving HS-DSCH cell respectively. +- f) When configured to operate on single/dual band 4C-HSDPA or single band 8C-HSDPA or single band NC-4C-HSDPA with a single UL frequency, the TX-RX frequency separation in Table 5.0A shall be applied for the DL frequency of the serving HS-DSCH cell. When configured to operate on single/dual band 4C-HSDPA or single band 8C-HSDPA or single band NC-4C-HSDPA with dual UL frequencies, the TX-RX frequency separation in Table 5.0A shall be applied to the primary UL frequency and DL frequency of the serving HS-DSCH cell, and to the secondary UL frequency and the frequency of the 1st secondary serving HS-DSCH cell respectively. +- g) For bands XII, XIII and XIV, all the requirements in TS 25.101 are applicable only for a single uplink carrier frequency, however dual cell uplink operation may be considered in future releases. +- f) When configured to operate on dual band dual cell HSDPA or dual band 4C-HSDPA with dual band UL frequencies, the TX-RX frequency separation in Table 5.0A shall be applied to the primary UL frequency and DL frequency of the serving HS-DSCH cell, and to the secondary UL frequency and the frequency of the 1st secondary serving HS-DSCH cell respectively. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. In DC-HSDPA and DB-DC-HSDPA mode, the UE receives two cells simultaneously. In context of DC-HSDPA and DB-DC-HSDPA, a cell is characterized by a combination of scrambling code and a carrier frequency, see [21.905]. + +### 5.4.2 Channel raster + +The channel raster is 200 kHz, for all bands which means that the centre frequency must be an integer multiple of 200 kHz. In addition a number of additional centre frequencies are specified according to table 5.1A, which means that the centre frequencies for these channels are shifted 100 kHz relative to the general raster. + +### 5.4.3 Channel number + +The carrier frequency is designated by the UTRA Absolute Radio Frequency Channel Number (UARFCN). For each operating Band, the UARFCN values are defined as follows: + +Uplink: $N_U = 5 * (F_{UL} - F_{UL\_Offset})$ , for the carrier frequency range $F_{UL\_low} \leq F_{UL} \leq F_{UL\_high}$ + +Downlink: $N_D = 5 * (F_{DL} - F_{DL\_Offset})$ , for the carrier frequency range $F_{DL\_low} \leq F_{DL} \leq F_{DL\_high}$ + +For each operating Band, $F_{UL\_Offset}$ , $F_{UL\_low}$ , $F_{UL\_high}$ , $F_{DL\_Offset}$ , $F_{DL\_low}$ and $F_{DL\_high}$ are defined in Table 5.1 for the general UARFCN. For the additional UARFCN, $F_{UL\_Offset}$ , $F_{DL\_Offset}$ and the specific $F_{UL}$ and $F_{DL}$ are defined in Table 5.1A. + +Table 5.1: UARFCN definition (general) + +| Band | UPLINK (UL) | | | DOWNLINK (DL) | | | +|--------------------|----------------------------------------------------|--------------------------------------------------|----------------------|----------------------------------------------------|--------------------------------------------------|----------------------| +| | UE transmit, Node B receive | | | UE receive, Node B transmit | | | +| | UARFCN formula offset F UL_Offset [MHz] | Carrier frequency (F UL ) range [MHz] | | UARFCN formula offset F DL_Offset [MHz] | Carrier frequency (F DL ) range [MHz] | | +| | | F UL_low | F UL_high | | F DL_low | F DL_high | +| I | 0 | 1922.4 | 1977.6 | 0 | 2112.4 | 2167.6 | +| II | 0 | 1852.4 | 1907.6 | 0 | 1932.4 | 1987.6 | +| III | 1525 | 1712.4 | 1782.6 | 1575 | 1807.4 | 1877.6 | +| IV | 1450 | 1712.4 | 1752.6 | 1805 | 2112.4 | 2152.6 | +| V | 0 | 826.4 | 846.6 | 0 | 871.4 | 891.6 | +| VI | 0 | 832.4 | 837.6 | 0 | 877.4 | 882.6 | +| VII | 2100 | 2502.4 | 2567.6 | 2175 | 2622.4 | 2687.6 | +| VIII | 340 | 882.4 | 912.6 | 340 | 927.4 | 957.6 | +| IX | 0 | 1752.4 | 1782.4 | 0 | 1847.4 | 1877.4 | +| X | 1135 | 1712.4 | 1767.6 | 1490 | 2112.4 | 2167.6 | +| XI | 733 | 1430.4 | 1445.4 | 736 | 1478.4 | 1493.4 | +| XII | -22 | 701.4 | 713.6 | -37 | 731.4 | 743.6 | +| XIII | 21 | 779.4 | 784.6 | -55 | 748.4 | 753.6 | +| XIV | 12 | 790.4 | 795.6 | -63 | 760.4 | 765.6 | +| XIX | 770 | 832.4 | 842.6 | 735 | 877.4 | 887.6 | +| XX | -23 | 834.4 | 859.6 | -109 | 793.4 | 818.6 | +| XXI | 1358 | 1450.4 | 1460.4 | 1326 | 1498.4 | 1508.4 | +| XXII | 2525 | 3412.4 | 3487.6 | 2580 | 3512.4 | 3587.6 | +| XXV | 875 | 1852.4 | 1912.6 | 910 | 1932.4 | 1992.6 | +| XXVI | -291 | 816.4 | 846.6 | -291 | 861.4 | 891.6 | +| XXXII 1 | N/A | | | 131 | 1454.4 | 1493.6 | + +NOTE 1: Restricted to UTRA operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA) + +**Table 5.1A: UARFCN definition (additional channels)** + +| Band | UPLINK (UL) | | DOWNLINK (DL) | | +|--------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| | UE transmit, Node B receive | | UE receive, Node B transmit | | +| | UARFCN formula offset F UL_offset [MHz] | Carrier frequency [MHz] (F UL ) | UARFCN formula offset F DL_offset [MHz] | Carrier frequency [MHz] (F DL ) | +| I | - | - | - | - | +| II | 1850.1 | 1852.5, 1857.5, 1862.5, 1867.5, 1872.5, 1877.5, 1882.5, 1887.5, 1892.5, 1897.5, 1902.5, 1907.5 | 1850.1 | 1932.5, 1937.5, 1942.5, 1947.5, 1952.5, 1957.5, 1962.5, 1967.5, 1972.5, 1977.5, 1982.5, 1987.5 | +| III | - | - | - | - | +| IV | 1380.1 | 1712.5, 1717.5, 1722.5, 1727.5, 1732.5, 1737.5, 1742.5, 1747.5, 1752.5 | 1735.1 | 2112.5, 2117.5, 2122.5, 2127.5, 2132.5, 2137.5, 2142.5, 2147.5, 2152.5 | +| V | 670.1 | 826.5, 827.5, 831.5, 832.5, 837.5, 842.5 | 670.1 | 871.5, 872.5, 876.5, 877.5, 882.5, 887.5 | +| VI | 670.1 | 832.5, 837.5 | 670.1 | 877.5, 882.5 | +| VII | 2030.1 | 2502.5, 2507.5, 2512.5, 2517.5, 2522.5, 2527.5, 2532.5, 2537.5, 2542.5, 2547.5, 2552.5, 2557.5, 2562.5, 2567.5 | 2105.1 | 2622.5, 2627.5, 2632.5, 2637.5, 2642.5, 2647.5, 2652.5, 2657.5, 2662.5, 2667.5, 2672.5, 2677.5, 2682.5, 2687.5 | +| VIII | - | - | - | - | +| IX | - | - | - | - | +| X | 1075.1 | 1712.5, 1717.5, 1722.5, 1727.5, 1732.5, 1737.5, 1742.5, 1747.5, 1752.5, 1757.5, 1762.5, 1767.5 | 1430.1 | 2112.5, 2117.5, 2122.5, 2127.5, 2132.5, 2137.5, 2142.5, 2147.5, 2152.5, 2157.5, 2162.5, 2167.5 | +| XI | - | - | - | - | +| XII | -39.9 | 701.5, 706.5, 707.5, 712.5, 713.5 | -54.9 | 731.5, 736.5, 737.5, 742.5, 743.5 | +| XIII | 11.1 | 779.5, 784.5 | -64.9 | 748.5, 753.5 | +| XIV | 2.1 | 790.5, 795.5 | -72.9 | 760.5, 765.5 | +| XIX | 755.1 | 832.5, 837.5, 842.5 | 720.1 | 877.5, 882.5, 887.5 | +| XX | - | - | - | - | +| XXI | - | - | - | - | +| XXII | - | - | - | - | +| XXV | 639.1 | 1852.5, 1857.5, 1862.5, 1867.5, 1872.5, 1877.5, 1882.5, 1887.5, 1892.5, 1897.5, 1902.5, 1907.5, 1912.5 | 674.1 | 1932.5, 1937.5, 1942.5, 1947.5, 1952.5, 1957.5, 1962.5, 1967.5, 1972.5, 1977.5, 1982.5, 1987.5, 1992.5 | +| XXVI | -325.9 | 816.5, 821.5, 826.5, 827.5, 831.5, 832.5, 836.5, 837.5, 841.5, 842.5, 846.5 | -325.9 | 861.5, 866.5, 871.5, 872.5, 876.5, 877.5, 881.5, 882.5, 886.5, 887.5, 891.5 | +| XXXII 1 | N/A | | 87.1 | 1454.5, 1459.5, 1464.5, 1469.5, 1474.5, 1479.5, 1484.5, 1489.5 | + +NOTE 1: Restricted to UTRA operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA) + +## 5.4.4 UARFCN + +The following UARFCN range shall be supported for each paired band + +**Table 5.2: UTRA Absolute Radio Frequency Channel Number** + +| Band | Uplink (UL) | | Downlink (DL) | | +|--------------------|-----------------------------|------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------------------------------------| +| | UE transmit, Node B receive | | UE receive, Node B transmit | | +| | General | Additional | General | Additional | +| I | 9612 to 9888 | - | 10562 to 10838 | - | +| II | 9262 to 9538 | 12, 37, 62, 87, 112, 137, 162, 187, 212, 237, 262, 287 | 9662 to 9938 | 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687 | +| III | 937 to 1288 | - | 1162 to 1513 | - | +| IV | 1312 to 1513 | 1662, 1687, 1712, 1737, 1762, 1787, 1812, 1837, 1862 | 1537 to 1738 | 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087 | +| V | 4132 to 4233 | 782, 787, 807, 812, 837, 862 | 4357 to 4458 | 1007, 1012, 1032, 1037, 1062, 1087 | +| VI | 4162 to 4188 | 812, 837 | 4387 to 4413 | 1037, 1062 | +| VII | 2012 to 2338 | 2362, 2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562, 2587, 2612, 2637, 2662, 2687 | 2237 to 2563 | 2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912 | +| VIII | 2712 to 2863 | - | 2937 to 3088 | - | +| IX | 8762 to 8912 | - | 9237 to 9387 | - | +| X | 2887 to 3163 | 3187, 3212, 3237, 3262, 3287, 3312, 3337, 3362, 3387, 3412, 3437, 3462 | 3112 to 3388 | 3412, 3437, 3462, 3487, 3512, 3537, 3562, 3587, 3612, 3637, 3662, 3687 | +| XI | 3487 to 3562 | - | 3712 to 3787 | - | +| XII | 3617 to 3678 | 3707, 3732, 3737, 3762, 3767 | 3842 to 3903 | 3932, 3957, 3962, 3987, 3992 | +| XIII | 3792 to 3818 | 3842, 3867 | 4017 to 4043 | 4067, 4092 | +| XIV | 3892 to 3918 | 3942, 3967 | 4117 to 4143 | 4167, 4192 | +| XIX | 312 to 363 | 387, 412, 437 | 712 to 763 | 787, 812, 837 | +| XX | 4287 to 4413 | - | 4512 to 4638 | - | +| XXI | 462 to 512 | - | 862 to 912 | - | +| XXII | 4437 to 4813 | - | 4662 to 5038 | - | +| XXV | 4887 to 5188 | 6067, 6092, 6117, 6142, 6167, 6192, 6217, 6242, 6267, 6292, 6317, 6342, 6367 | 5112 to 5413 | 6292, 6317, 6342, 6367, 6392, 6417, 6442, 6467, 6492, 6517, 6542, 6567, 6592 | +| XXVI | 5537 to 5688 | 5712, 5737, 5762, 5767, 5787, 5792, 5812, 5817, 5837, 5842, 5862 | 5762 to 5913 | 5937, 5962, 5987, 5992, 6012, 6017, 6037, 6042, 6062, 6067, 6087 | +| XXXII 1 | N/A | | 6617 to 6813 | 6837, 6862, 6887, 6912, 6937, 6962, 6987, 7012 | + +NOTE 1: Restricted to UTRA operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA) + +NOTE: If the UE is on a network with Mobile Country Code set to Japan then it may assume that any DL UARFCN sent by the network from the overlapping region of Band V and Band VI is from Band VI. If the UE is on a network with a Mobile Country Code other than Japan then it may assume that any DL UARFCN sent by the network from the overlapping region of Band V and Band VI is from Band V. + +--- + +## 6 Transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the transmitter characteristics are specified at the antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Transmitter characteristics for UE(s) with multiple antennas/antenna connectors are FFS. + +The UE antenna performance has a significant impact on system performance, and minimum requirements on the antenna efficiency are therefore intended to be included in future versions of the present document. It is recognised that different requirements and test methods are likely to be required for the different types of UE. + +UEs supporting DC-HSUPA shall support both minimum requirements, as well as additional requirements for DC-HSUPA. + +Unless otherwise stated, for the additional requirements for DC-HSUPA, all the parameters in clause 6 are defined using the UL E-DCH reference measurement channel, specified in subclause A.2.6. For the additional requirements for DC-HSUPA, the spacing of the carrier frequencies of the two cells shall be 5 MHz. + +Unless otherwise stated, for the additional requirements for DB-DC-HSUPA, all the parameters in clause 6 are defined using the UL E-DCH reference measurement channel, specified in subclause A.2.6. + +UEs supporting Open-Loop uplink Transmitter Diversity shall support both minimum requirements for one of transmit antenna connectors, which one to be tested shall be declared by the manufacturer, and additional requirements for UL OLTD. In addition, the additional requirements for UL OLTD are applicable only in the case when equal power is transmitted from two active antenna ports. + +DC-HSUPA and UL OLTD do not operate simultaneously in the UE. + +DB-DC-HSUPA and UL OLTD do not operate simultaneously in the UE. + +UEs supporting UL CLTD shall support both minimum requirements, as well as additional requirements for UL CLTD. + +The requirements in clause 6 for UEs supporting UL CLTD are specified for UL CLTD activation states 1, 2, 3 which are defined in sub-clause 4.6C.2.2.3 in TS 25.212[10]. + +DC-HSUPA and UL CLTD do not operate simultaneously in the UE. + +DB-DC-HSUPA and UL CLTD do not operate simultaneously in the UE. + +UEs supporting UL MIMO shall support both minimum requirements, as well as additional requirements for UL MIMO. + +The requirements in clause 6 specified for UL MIMO are applicable for UL MIMO rank-2 transmission. The requirements for UL MIMO rank-1 transmission are covered by UL CLTD requirements. UL MIMO rank-1 and rank-2 transmissions are defined in clause 11 of TS25.214 [8]. + +DC-HSUPA and UL MIMO do not operate simultaneously in the UE. + +DB-DC-HSUPA and UL MIMO do not operate simultaneously in the UE. + +## 6.2 Transmit power + +### 6.2.1 UE maximum output power + +The following Power Classes define the nominal maximum output power. The nominal power defined is the broadband transmit power of the UE, i.e. the power in a bandwidth of at least $(1+\alpha)$ times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot. For DC-HSUPA, the nominal transmit power is defined by the sum of the broadband transmit power of each carrier in the UE. + +**Table 6.1: UE Power Classes** + +| Operating Band | Power Class 1 | | Power Class 2 | | Power Class 3 | | Power Class 3bis | | Power Class 4 | | +|--------------------|---------------|----------|---------------|----------|---------------|----------|------------------|----------|---------------|----------| +| | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | +| Band I | +33 | +1/-3 | +27 | +1/-3 | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band II | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band III | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band IV | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band V | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band VI | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band VII | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band VIII | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band IX | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band X | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XI | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XII | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XIII | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band IV | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XIX | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XX | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XXI | - | - | - | - | +24 | +1/-3 | 23 | +2/-2 | +21 | +2/-2 | +| Band XXII | - | - | - | - | +24 | +1/-4.5 | 23 | +2/-3.5 | +21 | +2/-3.5 | +| Band XXV | - | - | - | - | +24 | +1/-4 | 23 | +2/-3 | +21 | +2/-3 | +| Band XXVI (Note 1) | - | - | - | - | +24 | +1/-4 | 23 | +2/-3 | +21 | +2/-3 | + +NOTE 1 For the UE which supports both Band V and Band XXVI operating frequencies, the UE maximum output power of Band V shall apply for Band XXVI when the carrier frequency of the assigned UTRA channel is within 824-845 MHz. + +NOTE: The tolerance allowed for the nominal maximum output power applies even for the multi-code DPDCH transmission mode. + +For the UE which supports DB-DC-HSDPA configuration in Table 6.1aB, the lower side of the tolerance in Table 6.1 is allowed to be adjusted by the amount given in Table 6.1aB for the applicable bands. + +**Table 6.1aB Allowed adjustment in lower side of tolerance for UE which supports DB-DC-HSDPA** + +| DB-DC-HSDPA Configuration | Maximum allowed adjustment in lower side of tolerance (dB) | Applicable bands | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------| +| 1 | -0.3 | I, VIII | +| 2 | -1 | II, IV | +| 3 | -0.3 | I, V | +| 4 | -1 | I, XI | +| 5 | -0.3 | II, V | +| 6 | -0.3 | I | +| NOTE: The requirements reflect what can be achieved with the present state of the art technology. They shall be reconsidered when the state of the art technology progresses. | | | + +For the UE which supports dual band 4C-HSDPA configuration in Table 6.1aC, the lower side of the tolerance in Table 6.1 is allowed to be adjusted by the amount given in Table 6.1aC for the applicable bands. + +**Table 6.1aC Allowed adjustment in lower side of tolerance for UE which supports dual band 4C-HSDPA** + +| Dual Band 4C-HSDPA Configuration | Maximum allowed adjustment in lower side of tolerance (dB) | Applicable bands | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------| +| I-2-VIII-1, I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | -0.3 | I, VIII | +| II-1-IV-2, II-2-IV-1, II-2-IV-2 | -1 | II, IV | +| I-1-V-2, I-2-V-1, I-2-V-2 | -0.3 | I, V | +| II-1-V-2 | -0.3 | II, V | +| I-1-XXXII-2, I-2-XXXII-1 | -0.3 | I | +| NOTE: The requirements reflect what can be achieved with the present state of the art technology. They shall be reconsidered when the state of the art technology progresses. | | | + +For the UE which supports E-UTRA inter-band carrier aggregation, the lower side of the tolerance in Table 6.1 is allowed to be decreased by the amount given in Table 6.2.5A-3 of TS 36.101[11] for those UTRA operating bands corresponding to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. The tolerance in Table 6.2.5A-3 of TS 36.101[11] does not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. + +In case the UE supports DB-DC-HSDPA or dual band 4C-HSDPA configurations and one or more of the E-UTRA inter-band carrier aggregation configurations listed in Table 6.2.5A-3 of TS36.101[11] with a UTRA operating band that belongs to UTRA and E-UTRA carrier aggregation configurations, then + +- When the UTRA operating band frequency range is $\leq 1\text{GHz}$ , the applicable additional tolerance shall be the average of the applicable tolerances, truncated to one decimal place for that operating band among the supported DB-DC-HSDPA, dual band 4C-HSDPA, and E-UTRA CA configurations, with the DB-DC-HSDPA, dual carrier 4C-HSDPA, and E-UTRA CA configurations counted separately. In case there is a harmonic relation between low band UL and high band DL, then the maximum tolerance among the different supported carrier aggregation configurations involving such band shall be applied +- When the UTRA operating band frequency range is $>1\text{GHz}$ , the applicable additional tolerance shall be the maximum tolerance that applies for that operating band among the supported DB-DC-HSDPA, dual band 4C-HSDPA, and E-UTRA CA configurations. + +## 6.2.1A UE maximum output power for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the maximum output power is specified in Table 6.1aD. The nominal transmit power is defined by the sum of transmit power at each UE antenna connector. + +**Table 6.1aD: UE Power Classes for UL OLTD** + +| Operating Band | Power Class 3 | | Power Class 3bis | | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------------------|----------| +| | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | +| Band I | +24 | +1/-4 | 23 | +2/-3 | +| Band II | +24 | +1/-4 | 23 | +2/-3 | +| Band III | +24 | +1/-4 | 23 | +2/-3 | +| Band IV | +24 | +1/-4 | 23 | +2/-3 | +| Band V | +24 | +1/-4 | 23 | +2/-3 | +| Band VI | +24 | +1/-4 | 23 | +2/-3 | +| Band VII | +24 | +1/-4 | 23 | +2/-3 | +| Band VIII | +24 | +1/-4 | 23 | +2/-3 | +| Band IX | +24 | +1/-4 | 23 | +2/-3 | +| Band X | +24 | +1/-4 | 23 | +2/-3 | +| Band XI | +24 | +1/-4 | 23 | +2/-3 | +| Band XII | +24 | +1/-4 | 23 | +2/-3 | +| Band XIII | +24 | +1/-4 | 23 | +2/-3 | +| Band XIV | +24 | +1/-4 | 23 | +2/-3 | +| Band XIX | +24 | +1/-4 | 23 | +2/-3 | +| Band XX | +24 | +1/-4 | 23 | +2/-3 | +| Band XXI | +24 | +1/-4 | 23 | +2/-3 | +| Band XXII | +24 | +1/-5.5 | 23 | +2/-4.5 | +| Band XXV | +24 | +1/-5 | 23 | +2/-4 | +| Band XXVI (Note 1) | +24 | +1/-5 | 23 | +2/-4 | +| Note 1 | For the UE which supports both Band V and Band XXVI operating frequencies, the UE maximum output power of Band V shall apply for Band XXVI when the carrier frequency of the assigned UTRA channel is within 824-845 MHz. | | | | + +## 6.2.1B UE maximum output power for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the nominal maximum output power is specified in Table 6.1aE. The nominal transmit power is defined by the sum of transmit power at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the nominal maximum output power specified in sub-clause 6.2.1 applies at the active transmit antenna connector. + +Table 6.1aE: UE Power Classes for UL CLTD + +| Operating Band | Power Class 3 | | Power Class 3bis | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------------------|----------| +| | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | +| Band I | +24 | +1/-4 | 23 | +2/-3 | +| Band II | +24 | +1/-4 | 23 | +2/-3 | +| Band III | +24 | +1/-4 | 23 | +2/-3 | +| Band IV | +24 | +1/-4 | 23 | +2/-3 | +| Band V | +24 | +1/-4 | 23 | +2/-3 | +| Band VI | +24 | +1/-4 | 23 | +2/-3 | +| Band VII | +24 | +1/-4 | 23 | +2/-3 | +| Band VIII | +24 | +1/-4 | 23 | +2/-3 | +| Band IX | +24 | +1/-4 | 23 | +2/-3 | +| Band X | +24 | +1/-4 | 23 | +2/-3 | +| Band XI | +24 | +1/-4 | 23 | +2/-3 | +| Band XII | +24 | +1/-4 | 23 | +2/-3 | +| Band XIII | +24 | +1/-4 | 23 | +2/-3 | +| Band IV | +24 | +1/-4 | 23 | +2/-3 | +| Band XIX | +24 | +1/-4 | 23 | +2/-3 | +| Band XX | +24 | +1/-4 | 23 | +2/-3 | +| Band XXI | +24 | +1/-4 | 23 | +2/-3 | +| Band XXII | +24 | +1/-5.5 | 23 | +2/-4.5 | +| Band XXV | +24 | +1/-5 | 23 | +2/-4 | +| Band XXVI
(Note 1) | +24 | +1/-5 | 23 | +2/-4 | +| Note 1 | For the UE which supports both Band V and Band XXVI operating frequencies, the UE maximum output power of Band V shall apply for Band XXVI when the carrier frequency of the assigned UTRA channel is within 824-845 MHz. | | | | + +## 6.2.1C UE maximum output power for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the nominal maximum output power is specified in Table 6.1aF. The nominal transmit power is defined by the sum of transmit power at each transmit antenna connector. + +**Table 6.1aF: UE Power Classes for UL MIMO** + +| Operating Band | Power Class 3 | | Power Class 3bis | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------------------|----------| +| | Power (dBm) | Tol (dB) | Power (dBm) | Tol (dB) | +| Band I | +24 | +1/-4 | 23 | +2/-3 | +| Band II | +24 | +1/-4 | 23 | +2/-3 | +| Band III | +24 | +1/-4 | 23 | +2/-3 | +| Band IV | +24 | +1/-4 | 23 | +2/-3 | +| Band V | +24 | +1/-4 | 23 | +2/-3 | +| Band VI | +24 | +1/-4 | 23 | +2/-3 | +| Band VII | +24 | +1/-4 | 23 | +2/-3 | +| Band VIII | +24 | +1/-4 | 23 | +2/-3 | +| Band IX | +24 | +1/-4 | 23 | +2/-3 | +| Band X | +24 | +1/-4 | 23 | +2/-3 | +| Band XI | +24 | +1/-4 | 23 | +2/-3 | +| Band XII | +24 | +1/-4 | 23 | +2/-3 | +| Band XIII | +24 | +1/-4 | 23 | +2/-3 | +| Band XIV | +24 | +1/-4 | 23 | +2/-3 | +| Band XIX | +24 | +1/-4 | 23 | +2/-3 | +| Band XX | +24 | +1/-4 | 23 | +2/-3 | +| Band XXI | +24 | +1/-4 | 23 | +2/-3 | +| Band XXII | +24 | +1/-5.5 | 23 | +2/-4.5 | +| Band XXV | +24 | +1/-5 | 23 | +2/-4 | +| Band XXVI
(Note 1) | +24 | +1/-5 | 23 | +2/-4 | +| Note 1 | For the UE which supports both Band V and Band XXVI operating frequencies, the UE maximum output power of Band V shall apply for Band XXVI when the carrier frequency of the assigned UTRA channel is within 824-845 MHz. | | | | + +## 6.2.1D UE maximum output power for DB-DC-HSUPA + +For UE supporting for DB-DC-HSUPA operation, the nominal maximum output power is specified in Table 6.1aG. The nominal transmit power is defined by the sum of transmit powers of both carriers. + +**Table 6.1aG: UE Power Classes for Dual Band HSUPA** + +| Dual band HSUPA Configuration together with DB-DC-HSDPA/DB-4C-HSDPA | Power Class 3 | | +|---------------------------------------------------------------------|---------------|----------| +| | Power (dBm) | Tol (dB) | +| | | | + +| | | | +|------------|----|-------| +| I-1-VIII-1 | 24 | +1/-3 | +| I-2-VIII-1 | 24 | +1/-3 | +| I-2-VIII-2 | 24 | +1/-3 | +| I-1-VIII-2 | 24 | +1/-3 | +| I-3-VIII-1 | 24 | +1/-3 | +| I-1-V-1 | 24 | +1/-3 | +| I-1-V-2 | 24 | +1/-3 | +| I-2-V-1 | 24 | +1/-3 | +| I-2-V-2 | 24 | +1/-3 | +| II-1-V-1 | 24 | +1/-3 | +| II-1-V-2 | 24 | +1/-3 | + +## 6.2.2 UE maximum output power with HS-DPCCH and E-DCH + +The Maximum Power Reduction (MPR) for the nominal maximum output power defined in 6.2.1 is specified in table 6.1A for the values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ defined in [8] fully or partially transmitted during a DPCCH timeslot + +**Table 6.1A: UE maximum output power with HS-DPCCH and E-DCH** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------| +| When DPCCH2 is not configured:
For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH and E-DPCCH | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| When DPCCH2 is configured:
For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH, E-DPCCH and DPCCH2 | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| Note 1: CM = 1 for $\beta_c/\beta_d = 12/15$ , $\beta_{hs}/\beta_c = 24/15$ . For all other combinations of DPDCH, DPCCH, HS-DPCCH, E-DPDCH and E-DPCCH the MPR is based on the relative CM difference. | | | + +Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by + +$$CM = \text{CEIL} \{ [20 * \log_{10} ((v\_norm^3)_{rms}) - 20 * \log_{10} ((v\_norm\_ref^3)_{rms})] / k, 0.5 \}$$ + +Where + +- CEIL { x, 0.5 } means rounding upwards to closest 0.5dB, i.e. CM $\in$ [0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5] +- k is 1.85 for signals where all channelisations codes meet the following criteria CSF, N where $N < SF/2$ +- k is 1.56 for signals where any channelisations codes meet the following criteria $C_{SF, N}$ where $N \geq SF/2$ +- v\_norm is the normalized voltage waveform of the input signal +- v\_norm\_ref is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech) and +- $20 * \log_{10} ((v\_norm\_ref^3)_{rms}) = 1.52$ dB + +## 6.2.2A UE maximum output power for DC-HSUPA + +The Maximum Power Reduction (MPR) for the nominal maximum output power defined in 6.2.1 is specified for the values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ defined in [8] fully or partially transmitted during a DPCCH timeslot, and defined through calculation of the Raw Cubic Metric (Raw CM) which is based on the UE transmit channel configuration and is given by + +$$\text{Raw CM} = 20 * \log_{10} ((v\_norm^3)_{\text{rms}}) - 20 * \log_{10} ((v\_norm\_ref^3)_{\text{rms}})$$ + +where + +- $v\_norm$ is the normalized voltage waveform of the input signal +- $v\_norm\_ref$ is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech) and +- $20 * \log_{10} ((v\_norm\_ref^3)_{\text{rms}}) = 1.52 \text{ dB}$ + +For any DC-HSUPA signal not employing 16QAM modulation on any of the carriers, the MPR is specified in Table 6.1AA. + +**Table 6.1AA: UE maximum output power for DC-HSUPA signals not employing 16QAM modulation on any of the carriers** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| When DPCCH2 is not configured:
For all combinations of: DPCCH, DPDCH, HS-DPCCH, E-DPDCH and E-DPCCH | $0.22 \leq \text{CM} \leq 3.72$ | $\text{MAX}(\text{CM}-0.72, 0)$ | +| When DPCCH2 is configured:
For all combinations of: DPCCH, DPDCH, HS-DPCCH, E-DPDCH, E-DPCCH and DPCCH2 | $0.22 \leq \text{CM} \leq 3.72$ | $\text{MAX}(\text{CM}-0.72, 0)$ | + +where Cubic Metric (CM) is based on the Raw CM and is given by + +$$\text{CM} = \text{CEIL} \{ \text{Raw CM} / k, 0.22 \}$$ + +where + +- $\text{CEIL} \{ x, 0.22 \}$ means rounding upwards to closest 0.22dB with 0.5 dB granularity, i.e. $\text{CM} = [0.22, 0.72, 1.22, 1.72, 2.22, 2.72, 3.22, 3.72]$ +- $k$ is 1.66 + +For any DC-HSUPA signal employing 16QAM modulation on any of the carriers, the MPR is specified in Table 6.1AB.. + +**Table 6.1AB: UE maximum output power for DC-HSUPA signals employing 16QAM modulation on any of the carriers** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|---------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------| +| When DPCCH2 is not configured:
For all combinations of: DPCCH, DPDCH, HS-DPCCH, E-DPDCH and E-DPCCH | $[0.22 \leq \text{CM} \leq 3.72]$ | $[\text{CM}+0.8]$ | +| When DPCCH2 is configured:
For all combinations of: DPCCH, DPDCH, HS-DPCCH, E-DPDCH and E-DPCCH and DPCCH2 | $[0.22 \leq \text{CM} \leq 3.72]$ | $[\text{CM}+0.8]$ | + +where Cubic Metric (CM) is based on the Raw CM and is given by + +$$[\text{CM} = \text{CEIL} \{ \text{Raw CM} / k, 0.2 \}]$$ + +where + +- CEIL { x, 0.2 } means rounding upwards to closest 0.2dB with 0.5 dB granularity, i.e. CM = [0.2, 0.7, 1.2, 1.7, 2.2, 2.7, 3.2, 3.7] +- k is 1.66. + +The reference measurement channels for the requirements in subclause 6.2.2A are provided in subclause A.2.8. + +## 6.2.2B UE maximum output power with HS-DPCCH and E-DCH for UL OLTD + +For the UE with two active transmit antenna connectors in UL OLTD operation, the allowed Maximum Power Reduction (MPR) for the nominal maximum output power of each antenna is specified in Table 6.1A. The amount of applied power reduction on each antenna shall be the same. + +NOTE: CM is measured at each transmit antenna connector. + +## 6.2.2C UE maximum output power with HS-DPCCH and E-DCH for UL CLTD + +The Maximum Power Reduction (MPR) for the nominal maximum output power defined in 6.2.1 is specified in table 6.1AB for the values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ , $\beta_{ed}$ and $\beta_{sc}$ defined in [8] fully or partially transmitted during a DPCCH timeslot + +**Table 6.1AB: UE maximum output power with HS-DPCCH and E-DCH for UL CLTD** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|---------------------------------------------------------------------------------------|--------------------|---------------| +| For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH, E-DPCCH and S-DPCCH | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH, E-DPCCH, S-DPCCH and DPCCH2 | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | + +Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by + +$$CM = \text{CEIL} \{ [20 * \log_{10} ((v\_norm^3)_{rms}) - 20 * \log_{10} ((v\_norm\_ref^3)_{rms})] / k, 0.5 \}$$ + +Where + +- CEIL { x, 0.5 } means rounding upwards to closest 0.5dB, i.e. CM = [0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5] +- k is 1.85 for signals where all channelisations codes meet the following criteria $C_{SF,N}$ where $N < SF/2$ +- k is 1.56 for signals where any channelisations codes meet the following criteria $C_{SF,N}$ where $N \geq SF/2$ +- $v\_norm$ is the normalized voltage waveform of the input signal +- $v\_norm\_ref$ is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech) and +- $20 * \log_{10} ((v\_norm\_ref^3)_{rms}) = 1.52 \text{ dB}$ + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the allowed Maximum Power Reduction (MPR) for the nominal maximum output power of each antenna is specified in Table 6.1AA. The amount of applied power reduction on each antenna shall be the same. + +NOTE: CM is measured at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the allowed Maximum Power Reduction (MPR) for the nominal maximum output power specified in sub-clause 6.2.2 applies at the active transmit antenna connector. + +## 6.2.2D UE maximum output power with HS-DPCCH and E-DCH for UL MIMO + +The Maximum Power Reduction (MPR) for the nominal maximum output power defined in 6.2.1 is specified in table 6.1AC for the values of $\beta_c$ , $\beta_{hs}$ , $\beta_{ec}$ , $\beta_{sec}$ , $\beta_{ed}$ , $\beta_{sed}$ and $\beta_{sc}$ defined in [8] fully or partially transmitted during a DPCCH timeslot + +**Table 6.1AC: UE maximum output power with HS-DPCCH and E-DCH for UL MIMO** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|-----------------------------------------------------------------------------------------------------|--------------------|---------------| +| For all combinations of: DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH E-DPCCH, S-E-DPCCH and S-DPCCH | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| For all combinations of: DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH E-DPCCH, S-E-DPCCH, S-DPCCH and DPCCH2 | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | + +Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by + +$$CM = CEIL \{ [20 * \log_{10} ((v\_norm^3)_{rms}) - 20 * \log_{10} ((v\_norm\_ref^3)_{rms})] / k, 0.5 \}$$ + +Where + +- $CEIL \{ x, 0.5 \}$ means rounding upwards to closest 0.5dB, i.e. $CM = [0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5]$ +- $k$ is 1.85 for signals where all channelisations codes meet the following criteria $C_{SF,N}$ where $N < SF/2$ +- $k$ is 1.56 for signals where any channelisations codes meet the following criteria $C_{SF,N}$ where $N \geq SF/2$ +- $v\_norm$ is the normalized voltage waveform of the input signal +- $v\_norm\_ref$ is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech) and +- $20 * \log_{10} ((v\_norm\_ref^3)_{rms}) = 1.52$ dB + +For UE with two active transmit antenna connectors in UL MIMO operation, the allowed Maximum Power Reduction (MPR) for the nominal maximum output power of each antenna is specified in Table 6.1AC. The amount of applied power reduction on each antenna shall be the same. + +NOTE: CM is measured at each transmit antenna connector. + +## 6.2.2E UE maximum output power for the band with HS-DPCCH and E-DCH for DB-DC-HSUPA + +The Maximum Power Reduction (MPR) for the nominal maximum output power defined in 6.2.1D is specified in table 6.1AD for the values of $\beta_c$ , $\beta_{hs}$ , $\beta_{ec}$ , $\beta_{sec}$ , $\beta_{ed}$ , $\beta_{sed}$ and $\beta_{sc}$ defined in [8] fully or partially transmitted during a DPCCH timeslot + +**Table 6.1AD: UE maximum output power for the band with HS-DPCCH and E-DCH for DB-DC-HSUPA** + +| UE transmit channel configuration | CM (dB) | MPR (dB) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------| +| When DPCCH2 is not configured:
For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH and E-DPCCH | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| When DPCCH2 is configured:
For all combinations of: DPDCH, DPCCH, HS-DPCCH, E-DPDCH, E-DPCCH and DPCCH2 | $0 \leq CM \leq 4$ | MAX (CM-1, 0) | +| Note 1: CM = 1 for $\beta_d/\beta_c=12/15$ , $\beta_{ns}/\beta_c=24/15$ . For all other combinations of DPDCH, DPCCH, HS-DPCCH, E-DPDCH and E-DPCCH the MPR is based on the relative CM difference. | | | + +Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by + +$$CM = CEIL \{ [20 * \log_{10} ((v\_norm^3)_{rms}) - 20 * \log_{10} ((v\_norm\_ref^3)_{rms})] / k, 0.5 \}$$ + +Where + +- $CEIL \{ x, 0.5 \}$ means rounding upwards to closest 0.5dB, i.e. $CM = [0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5]$ +- $k$ is 1.85 for signals where all channelisations codes meet the following criteria $C_{SF,N}$ where $N < SF/2$ +- $k$ is 1.56 for signals where any channelisations codes meet the following criteria $C_{SF,N}$ where $N \geq SF/2$ +- $v\_norm$ is the normalized voltage waveform of the input signal +- $v\_norm\_ref$ is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech) and +- $20 * \log_{10} ((v\_norm\_ref^3)_{rms}) = 1.52$ dB + +NOTE: CM is measured at each carrier. + +### 6.2.3 UE Relative code domain power accuracy + +The UE Relative code domain power accuracy is a measure of the ability of the UE to correctly set the level of individual code powers relative to the total power of all active codes. When the UE uses 16QAM modulation on any of the uplink code channels the IQ origin offset power shall be removed from the Measured CDP ratio; however, the removed relative IQ origin offset power (relative carrier leakage power) also has to satisfy the applicable requirement. The measure of accuracy is the difference between two dB ratios: + +$$UE\ Relative\ CDP\ accuracy = (Measured\ CDP\ ratio) - (Nominal\ CDP\ ratio)$$ + +where + +$$Measured\ CDP\ ratio = 10 * \log((Measured\ code\ power) / (Measured\ total\ power\ of\ all\ active\ codes))$$ + +$$Nominal\ CDP\ ratio = 10 * \log((Nominal\ CDP) / (Sum\ of\ all\ nominal\ CDPs))$$ + +The nominal CDP of a code is relative to the total of all codes and is derived from beta factors. + +When the UE uses 16QAM modulation a correction factor shall be applied to the $\beta_{cd}$ value used to compute the Nominal CDP equal to $\{A_1*(0.4472)^2 + A_2*(1.3416)^2 + A_3*(-0.4472)^2 + A_4*(-1.3416)^2\}^{1/2}$ where $A_1, A_2, A_3$ and $A_4$ are the fractions of symbols (00, 01, 10, 11 respectively) transmitted during the test. + +The sum of all nominal CDPs will equal 1 by definition. + +NOTE: The above definition of UE relative CDP accuracy is independent of variations in the actual total power of the signal and of noise in the signal that falls on inactive codes. + +The required accuracy of the UE relative CDP is given in table 6.1B. The UE relative CDP accuracy shall be maintained over the period during which the total of all active code powers remains unchanged or one timeslot, whichever is the longer. + +**Table 6.1B: UE Relative CDP accuracy** + +| Nominal CDP ratio | Accuracy (dB) | +|---------------------------|---------------| +| $\geq -10$ dB | $\pm 1.5$ | +| $-10$ dB to $\geq -15$ dB | $\pm 2.0$ | +| $-15$ dB to $\geq -20$ dB | $\pm 2.5$ | +| $-20$ dB to $\geq -30$ dB | $\pm 3.0$ | + +### 6.2.3A UE Relative code domain power accuracy for DC-HSUPA + +The requirement and corresponding measurements apply to each individual carrier when the total power in each of the assigned carriers is equal to each other + +The UE Relative code domain power accuracy is a measure of the ability of the UE to correctly set the level of individual code powers in a carrier relative to the total power of all active codes in that carrier. When the UE uses 16QAM modulation on any of the uplink code channels in a carrier the IQ origin offset power measured in that carrier shall be removed from the Measured CDP ratio in that carrier; however, the removed relative IQ origin offset power (relative carrier leakage power) measured in that carrier also has to satisfy the applicable requirement in that carrier. The measure of accuracy is the difference between two dB ratios measured per carrier configured on the uplink: + +$$\text{UE Relative CDP accuracy} = (\text{Measured CDP ratio}) - (\text{Nominal CDP ratio})$$ + +where + +$$\text{Measured CDP ratio} = 10 * \log((\text{Measured code power}) / (\text{Measured total power of all active codes}))$$ + +$$\text{Nominal CDP ratio} = 10 * \log((\text{Nominal CDP}) / (\text{Sum of all nominal CDPs}))$$ + +The nominal CDP of a code is relative to the total of all codes in each carrier and is derived from beta factors. The sum of all nominal CDPs will equal 1 by definition. + +NOTE: The above definition of UE relative CDP accuracy is independent of variations in the actual total power of the signal in each carrier and of noise in the signal that falls on inactive codes. + +The required accuracy of the UE relative CDP is given in table 6.1B. The UE relative CDP accuracy shall be maintained over the period during which the total of all active code powers remains unchanged or one timeslot, whichever is the longer. + +The reference measurement channels for the requirements in subclause 6.2.3A are provided in subclause A.2.6 and A.2.7. + +### 6.2.3B UE Relative code domain power accuracy for UL OLTD + +For the UE with two active transmit antenna connectors in UL OLTD operation, the relative code domain power accuracy specified in sub-clause 6.2.3 applies at each transmit antenna connector. + +### 6.2.3C UE Relative code domain power accuracy for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the relative code domain power accuracy specified in sub-clause 6.2.3 applies at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the relative code domain power accuracy specified in sub-clause 6.2.3 applies at the active transmit antenna connector. + +### 6.2.3D UE Relative code domain power accuracy for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the relative code domain power accuracy specified in sub-clause 6.2.3 applies at each transmit antenna connector. + +### 6.2.3E UE Relative code domain power accuracy for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the relative code domain power accuracy specified in sub-clause 6.2.3A applies. + +## 6.3 Frequency Error + +The UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the carrier frequency received from the Node B. For the PRACH preambles the measurement interval is lengthened to 3904 chips (being the 4096 chip nominal preamble period less a 25 $\mu\text{s}$ transient period allowance at each end of the burst). These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +### 6.3A Frequency Error for DC-HSUPA + +The UE modulated carrier frequencies shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the average of the carrier frequencies received from the Node B. When the signal from one Node B cell is out-of-sync, the UE modulated carrier frequency shall be compared to the remaining carrier frequency received from the other Node B cell. These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time such that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The frequency error of the carrier frequencies received from the Node B shall be the same in average. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +### 6.3B Frequency error for UL OLTD + +The UE modulated carrier frequency at each transmit antenna connector shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the carrier frequency received from the Node B. These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +### 6.3C Frequency error for UL CLTD + +The UE modulated carrier frequency at each transmit antenna connector shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the carrier frequency received from the Node B. These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +## 6.3D Frequency error for UL MIMO + +For UE supporting UL MIMO, the UE modulated carrier frequency at each transmit antenna connector shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the carrier frequency received from the Node B. These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +## 6.3E Frequency error for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, each UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of one timeslot compared to the associated downlink carrier frequency received from the Node B. These signals will have an apparent error due to Node B frequency error and Doppler shift. The signals from the Node B must be averaged over sufficient time that errors due to noise or interference are within the above $\pm 0.1$ PPM figure. The UE shall use the same frequency source for both RF frequency generation and the chip clock. + +## 6.4 Output power dynamics + +Power control is used to limit the interference level. + +### 6.4.1 Open loop power control + +Open loop power control is the ability of the UE transmitter to sets its output power to a specific value. The open loop power control tolerance is given in Table 6.3 + +#### 6.4.1.1 Minimum requirement + +The UE open loop power is defined as the mean power in a timeslot or ON power duration, whichever is available. + +**Table 6.3: Open loop power control tolerance** + +| Conditions | Tolerance | +|--------------------|-------------| +| Normal conditions | $\pm 9$ dB | +| Extreme conditions | $\pm 12$ dB | + +#### 6.4.1.1A Additional requirement for DC-HSUPA + +The open loop power control tolerance per carrier is given in Table 6.3. + +#### 6.4.1.1B Additional requirement for DB-DC-HSUPA + +The open loop power control tolerance per carrier is given in Table 6.3. + +### 6.4.2 Inner loop power control in the uplink + +Inner loop power control in the Uplink is the ability of the UE transmitter to adjust its output power in accordance with one or more TPC commands received in the downlink. There are two inner loop power control loops defined , one that controls the DPCCH and one that controls the DPCCH2 power when DPCCH2 is configured. + +### 6.4.2.1 Power control steps + +The power control step is the change in the UE transmitter output power in response to a single TPC command, TPC\_cmd, derived at the UE. + +#### 6.4.2.1.1 Minimum requirement + +The UE transmitter shall when DPCCH2 is not configured have the capability of changing the output power with a step size of 1, 2 and 3 dB according to the value of $\Delta_{\text{TPC}}$ or $\Delta_{\text{RP-TPC}}$ , in the slot immediately after the TPC\_cmd as follows + +- The transmitter output power step due to inner loop power control shall be within the range shown in Table 6.4. +- The transmitter average output power step due to inner loop power control shall be within the range shown in Table 6.5. Here a TPC\_cmd group is a set of TPC\_cmd values derived from a corresponding sequence of TPC commands of the same duration. + +The inner loop power step is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot, not including the transient duration. The transient duration is from 25 $\mu\text{s}$ before the slot boundary to 25 $\mu\text{s}$ after the slot boundary. + +**Table 6.4: Transmitter power control range** + +| TPC_cmd | Transmitter power control range | | | | | | +|---------|---------------------------------|---------|----------------|---------|----------------|---------| +| | 1 dB step size | | 2 dB step size | | 3 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | +| + 1 | +0.5 dB | +1.5 dB | +1 dB | +3 dB | +1.5 dB | +4.5 dB | +| 0 | -0.5 dB | +0.5 dB | -0.5 dB | +0.5 dB | -0.5 dB | +0.5 dB | +| -1 | -0.5 dB | -1.5 dB | -1 dB | -3 dB | -1.5 dB | -4.5 dB | + +The UE transmitter shall when DPCCH2 is configured have the capability of changing the power for the DPCCH code as well as the DPCCH2 code with a step size of 1, 2 and 3 dB according to the value of $\Delta_{\text{TPC}}$ or $\Delta_{\text{RP-TPC}}$ in the slot immediately after the TPC\_cmd as follows + +- These requirements are valid as long as the maximum code power difference between DPCCH2 and DPCCH is between -5 and +20 dB. +- The transmitter output power step due to inner loop power control shall be within the range shown in Table 6.4A. +- The transmitter average output power step due to inner loop power control shall be within the range shown in Table 6.5. Here a TPC\_cmd group is a set of TPC\_cmd values derived from a corresponding sequence of TPC commands of the same duration. + +The inner loop power step is defined as the relative power difference between the mean code power of the original (reference) timeslot and the mean code power of the target timeslot, not including the transient duration. The transient duration is from 25 $\mu\text{s}$ before the slot boundary to 25 $\mu\text{s}$ after the slot boundary. + +**Table 6.4A: Transmitter power control range** + +| TPC_cmd | Transmitter power control range | | | | | | +|---------|---------------------------------|---------|----------------|---------|----------------|-------| +| | 1 dB step size | | 2 dB step size | | 3 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | +| + 1 | +1.0 dB | +2.0 dB | +1.5 dB | +3.5 dB | +2 dB | +5 dB | +| 0 | -1 dB | +1 dB | -1 dB | +1 dB | -1 dB | +1 dB | +| -1 | -1 dB | -2 dB | -1.5 dB | -3.5 dB | -2 dB | -5 dB | + +**Table 6.4A: Transmitter power control range for exceptions** + +| TPC_cmd | Transmitter power control range | | | | | | +|---------|---------------------------------|---------|----------------|---------|----------------|---------| +| | 1 dB step size | | 2 dB step size | | 3 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | +| + 1 | -0.5 dB | +2.5 dB | +0.5 dB | +3.5 dB | +1.5 dB | +4.5 dB | +| 0 | -0.5 dB | +0.5 dB | -0.5 dB | +0.5 dB | -0.5 dB | +0.5 dB | +| -1 | 0.5 dB | -2.5 dB | -0.5 dB | -3.5 dB | -1.5 dB | -4.5 dB | + +**Table 6.5: Transmitter aggregate power control range** + +| TPC_cmd group | Transmitter power control range after 10 equal TPC_cmd groups | | | | Transmitter power control range after 7 equal TPC_cmd groups | | +|---------------|---------------------------------------------------------------|--------|----------------|--------|--------------------------------------------------------------|--------| +| | 1 dB step size | | 2 dB step size | | 3 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | +| +1 | +8 dB | +12 dB | +16 dB | +24 dB | +16 dB | +26 dB | +| 0 | -1 dB | +1 dB | -1 dB | +1 dB | -1 dB | +1 dB | +| -1 | -8 dB | -12 dB | -16 dB | -24 dB | -16 dB | -26 dB | +| 0,0,0,0,+1 | +6 dB | +14 dB | N/A | N/A | N/A | N/A | +| 0,0,0,0,-1 | -6 dB | -14 dB | N/A | N/A | N/A | N/A | + +The UE shall meet the above requirements with the exceptions defined below for inner loop power control over the power range bounded by the Minimum output power as defined in subclause 6.4.3, and the Maximum output power supported by the UE (i.e. the actual power as would be measured assuming no measurement error). This power shall be in the range specified for the power class of the UE in subclause 6.2.1. For each direction, up to 2 exceptions to the transmitter power control range defined in table 6.4 shall be allowed. The transmitter power control range for exceptions is defined in table 6.4A. + +#### 6.4.2.1.1A Additional requirement for DC-HSUPA + +The UE transmitter shall have the capability of changing the output power in each assigned carrier in the uplink with a step size of 1, 2 and 3 dB according to the value of $\Delta_{TPC}$ or $\Delta_{RP-TPC}$ , in the slot immediately after the TPC\_cmd for the corresponding carrier as follows + +- a) The transmitter output power step due to inner loop power control in each assigned carrier in the uplink shall be within the range shown in Table 6.4 with the exceptions defined below, when the total transmit power in each of the assigned carriers is equal to each other. +- b) The transmitter average output power step due to inner loop power control in each assigned carrier in the uplink shall be within the range shown in Table 6.5 with the exceptions defined below, when the total transmit power in each of the assigned carriers is equal to each other. Here a TPC\_cmd group is a set of TPC\_cmd values derived from a corresponding sequence of TPC commands of the same duration. +- c) The requirements can be tested by sending the same TPC commands for each of the assigned carriers, assuming that the signal powers for the carriers (in terms of DPCCH code power and total power) have been aligned prior to the beginning of the test procedure. + +The inner loop power step is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot in each carrier, not including the transient duration. The transient duration is from 25μs before the slot boundary to 25μs after the slot boundary. For each direction, up to 2 exceptions to the transmitter power control range defined in table 6.4 shall be allowed. The transmitter power control range for exceptions is defined in table 6.4A. + +#### 6.4.2.1.1B Additional requirement for UL OLTD + +For the UE with two active transmit antenna connectors in UL OLTD operation, the inner loop power control in the uplink specified in sub-clause 6.4.2.1.1 applies at each transmit antenna connector. + +#### 6.4.2.1.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the inner loop power control in the uplink specified in sub-clause 6.4.2.1.1 applies at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the inner loop power control in the uplink specified in sub-clause 6.4.2.1.1 applies at the active transmit antenna connector. + +#### 6.4.2.1.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the inner loop power control in the uplink specified in sub-clause 6.4.2.1.1 applies at each transmit antenna connector. + +#### 6.4.2.1.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the inner loop power control in the uplink specified in sub-clause 6.4.2.1.1A applies. + +### 6.4.3 Minimum output power + +The minimum controlled output power of the UE is when the power is set to a minimum value. + +#### 6.4.3.1 Minimum requirement + +The minimum output power is defined as the mean power in one time slot. The minimum output power shall be less than -50 dBm. + +#### 6.4.3.1A Additional requirement for DC-HSUPA + +The minimum output power is defined as the mean power in one time slot in each carrier. The minimum output power in each carrier shall be less than -50 dBm, when both carriers are set to minimum output power. + +#### 6.4.3.1B Additional requirement for UL OLTD + +For the UE with two active transmit antenna connectors in UL OLTD operation, the minimum output power specified in sub-clause 6.4.3.1 applies at each transmit antenna connector, when the UE power is set to a minimum value. + +#### 6.4.3.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the minimum output power specified in sub-clause 6.4.3.1 applies at each transmit antenna connector, when the UE power is set to a minimum value. + +For UE configured in UL CLTD activation state 2 or activation state 3, the minimum output power specified in sub-clause 6.4.3.1 applies at the active transmit antenna connector, when the UE power is set to a minimum value. + +#### 6.4.3.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the minimum output power specified in sub-clause 6.4.3.1 applies at each transmit antenna connector, when the UE power is set to a minimum value. + +#### 6.4.3.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the minimum output power specified in sub-clause 6.4.3.1A applies. + +### 6.4.4 Out-of-synchronization handling of output power + +The receiver characteristics in this section are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna 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 the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in section 6.4.4.2 below. + +The UE shall monitor the DPCCH quality in order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The thresholds $Q_{out}$ and $Q_{in}$ specify at what DPCCH quality levels the UE shall shut its power off and when it shall turn its power on respectively. The thresholds are not defined explicitly, but are defined by the conditions under which the UE shall shut its transmitter off and turn it on, as stated in this subclause. + +The DPCCH quality shall be monitored in the UE and compared to the thresholds $Q_{out}$ and $Q_{in}$ for the purpose of monitoring synchronization. The threshold $Q_{out}$ should correspond to a level of DPCCH quality where no reliable detection of the TPC commands transmitted on the downlink DPCCH can be made. This can be at a TPC command error ratio level of e.g. 30%. The threshold $Q_{in}$ should correspond to a level of DPCCH quality where detection of the TPC commands transmitted on the downlink DPCCH is significantly more reliable than at $Q_{out}$ . This can be at a TPC command error ratio level of e.g. 20%. + +#### 6.4.4.1 Minimum requirement + +For the minimum requirement specified in this clause, it is assumed the use of either the Algorithm 1 or 2 [8] unless otherwise stated (i.e. Algorithm 3). + +UE shall shut its transmitter off within 40 ms when the UE estimates the following quality to be worse than a threshold $Q_{out}$ : + +- the DPCCH quality or the quality of the TPC fields of the F-DPCH frame received from the serving HS-DSCH cell over the last 160 ms period or, +- the quality of the TPC fields of the F-DPCH from the serving HS-DSCH cell over the previous 240 slots in which the TPC symbols are known to be present when the discontinuous uplink DPCCH transmission operation or the Algorithm 3 [8] is enabled. + +The UE shall not turn its transmitter on again until the DPCCH quality exceeds an acceptable level $Q_{in}$ . The UE shall again turn its transmitter on within 40 ms when the UE estimates the following quality to be better than a threshold $Q_{in}$ : + +- the DPCCH quality or the quality of the TPC fields of the F-DPCH frame received from the serving HS-DSCH cell over the last 160 ms period or, +- the quality of the TPC fields of the F-DPCH from the serving HS-DSCH cell over the previous 240 slots in which the TPC symbols are known to be present when the discontinuous uplink DPCCH transmission operation or the Algorithm 3 [8] is enabled. + +The UE transmitter shall be considered "off" if the transmitted power is below the level defined in subclause 6.5.1 (Transmit off power). Otherwise the transmitter shall be considered as "on". + +#### 6.4.4.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the minimum requirements specified in sub-clause 6.4.4.1 apply at each transmit antenna connector. + +#### 6.4.4.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the minimum requirements specified in sub-clause 6.4.4.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the minimum requirements specified in sub-clause 6.4.4.1 apply at the active transmit antenna connector. + +#### 6.4.4.1C Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the minimum requirements specified in sub-clause 6.4.4.1 apply at each transmit antenna connector. + +#### 6.4.4.1D Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the minimum requirements specified in sub-clause 6.4.4.1 apply per carrier. + +When the primary carrier is determined to be out-of-synchronization, UE shall shut its transmitter off for both primary and secondary carriers regardless of whether the secondary carrier is out-of-synchronization or not. When the secondary carrier is determined to be out-of-synchronization, the UE can continue to transmit on the primary carrier on the other band as long as it is not out-of-synchronization. + +#### 6.4.4.2 Test case + +This subclause specifies a test case, which provides additional information for how the minimum requirement should be interpreted for the purpose of conformance testing. + +The quality levels at the thresholds $Q_{out}$ and $Q_{in}$ correspond to different signal levels depending on the downlink conditions DCH parameters. For the conditions in Table 6.6, a signal with the quality at the level $Q_{out}$ can be generated by a DPCCH\_Ec/Ior ratio of -25 dB, and a signal with $Q_{in}$ by a DPCCH\_Ec/Ior ratio of -21 dB. For a UE which supports the optional enhanced performance requirements type1 for DCH a signal with the quality at the level $Q_{out}$ can be instead generated by a DPCCH\_Ec/Ior ratio of -28 dB, and a signal with $Q_{in}$ by a DPCCH\_Ec/Ior ratio of -24 dB for the conditions in Table 6.6. The DL reference measurement channel (12.2) kbps specified in subclause A.3.1 and with static propagation conditions. The downlink physical channels, other than those specified in Table 6.6, are as specified in Table C.3 of Annex C. + +Figure 6.1 shows an example scenario where the DPCCH\_Ec/Ior ratio varies from a level where the DPCH is demodulated under normal conditions, down to a level below $Q_{out}$ where the UE shall shut its power off and then back up to a level above $Q_{in}$ where the UE shall turn the power back on. Figure 6.1A shows an example scenario for a UE which supports the optional enhanced performance requirements type1 for DCH, where the DPCCH\_Ec/Ior ratio varies from a level where the DPCH is demodulated under normal conditions, down to a level below $Q_{out}$ where the UE shall shut its power off and then back up to a level above $Q_{in}$ where the UE shall turn the power back on. + +**Table 6.6: DCH parameters for the Out-of-synch handling test case** + +| Parameter | Unit | Value | +|-----------------------------|--------------|-------------------------------------------------------------------| +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| $\frac{DPDCH\_E_c}{I_{or}}$ | dB | See figure 6.1: Before point A -16.6
After point A Not defined | +| $\frac{DPCCH\_E_c}{I_{or}}$ | dB | See figure 6.1 | +| Information Data Rate | kbps | 12.2 | + +![Figure 6.1: Test case for out-of-synch handling in the UE. The graph shows the DPCCH_Ec/Ior power level in dB over time. The y-axis has levels at -16.6, -22, -24, -28, and -18. The x-axis has time points A, B, C, D, E, F. The power level starts at -16.6 before point A. At point A, it drops to -22 for 5 seconds until point B. At point B, it drops to -28. After a duration of Toff, at point C, the UE shuts power off. The level stays at -28 for 5 seconds until point D, then rises to -24 for 5 seconds until point E. At point E, it rises to -18. After a duration of Ton, at point F, the UE turns power on. Two horizontal dotted lines represent thresholds Qout and Qin.](671a9a08b8506e113012e056945fd8f3_img.jpg) + +*DPCCH\_Ec/Ior* [dB] + +ABCDEF + +Time [s] + +UE shuts power off + +UE turns power on + +Figure 6.1: Test case for out-of-synch handling in the UE. The graph shows the DPCCH\_Ec/Ior power level in dB over time. The y-axis has levels at -16.6, -22, -24, -28, and -18. The x-axis has time points A, B, C, D, E, F. The power level starts at -16.6 before point A. At point A, it drops to -22 for 5 seconds until point B. At point B, it drops to -28. After a duration of Toff, at point C, the UE shuts power off. The level stays at -28 for 5 seconds until point D, then rises to -24 for 5 seconds until point E. At point E, it rises to -18. After a duration of Ton, at point F, the UE turns power on. Two horizontal dotted lines represent thresholds Qout and Qin. + +**Figure 6.1: Test case for out-of-synch handling in the UE** + +![Figure 6.1A: Test case for out-of-synch handling in the UE supporting the enhanced performance requirements type1. The graph plots DPCCH_Ec/Ior [dB] against Time [s]. The signal level changes at specific points: A (-19.6 dB), B (-25 dB), C (-31 dB), D (-27 dB), E (-21 dB), and F (-21 dB). Horizontal dashed lines represent thresholds Qout and Qin. Time intervals of 5s are marked between A-B, C-D, and D-E. T_off is the interval between B and C, and T_on is the interval between E and F. Arrows indicate 'UE shuts power off' at point C and 'UE turns power' at point F.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +| Point | Time Interval | DPCCH_Ec/Ior [dB] | +|-------|-------------------|-------------------| +| A | Start | -19.6 | +| B | 5s after A | -25 | +| C | $T_{off}$ after B | -31 | +| D | 5s after C | -27 | +| E | 5s after D | -21 | +| F | $T_{on}$ after E | -21 | + +Figure 6.1A: Test case for out-of-synch handling in the UE supporting the enhanced performance requirements type1. The graph plots DPCCH\_Ec/Ior [dB] against Time [s]. The signal level changes at specific points: A (-19.6 dB), B (-25 dB), C (-31 dB), D (-27 dB), E (-21 dB), and F (-21 dB). Horizontal dashed lines represent thresholds Qout and Qin. Time intervals of 5s are marked between A-B, C-D, and D-E. T\_off is the interval between B and C, and T\_on is the interval between E and F. Arrows indicate 'UE shuts power off' at point C and 'UE turns power' at point F. + +**Figure 6.1A: Test case for out-of-synch handling in the UE supporting the enhanced performance requirements type1** + +In this test case, the requirements for the UE are that: + +1. The UE shall not shut its transmitter off before point B. +2. The UE shall shut its transmitter off before point C, which is $T_{off} = 200$ ms after point B. +3. The UE shall not turn its transmitter on between points C and E. +4. The UE shall turn its transmitter on before point F, which is $T_{on} = 200$ ms after point E. + +## 6.4A Output pattern dynamics + +An F-TPICH carries transmitted precoding indicator generated at layer 1 for UL CLTD operation. + +### 6.4A.1 Out-of-quality handling of TPI applicability + +The UE shall measure the reliability of the received TPI bits over the 3 slot period in which the TPI bit pattern corresponding to a precoding weight is received, as specified in TS 25.214 [8]. The received TPI bits are mapped to precoding weights and applied by the UE only if the estimated quality of the TPI bits is determined to be better than a threshold $Q_{tpi}$ . Otherwise, the UE shall apply the precoding weights corresponding to the last reliably received TPI bit pattern. The threshold is not defined explicitly, but is defined by the conditions under which the UE shall apply the precoding weights corresponding to the received TPI bits and apply the precoding weights corresponding to the last reliably received TPI bits, as stated in this subclause. + +The threshold $Q_{tpi}$ should correspond to a level of F-TPICH quality below which no reliable detection of the TPI bits transmitted on the downlink DPCCH can be made. + +### 6.4A.1.1 Minimum requirement + +When the UE estimates the F-TPICH quality received over the 3 slot period to be worse than a threshold $Q_{\text{tpi}}$ , the UE shall apply the precoding weights corresponding to the last reliably received TPI bit pattern. The UE shall not apply the precoding weights corresponding to the received TPI bits again until the F-TPICH quality exceeds a threshold $Q_{\text{tpi}}$ . When the estimated F-TPICH quality is better than a threshold $Q_{\text{tpi}}$ , the UE shall again apply the precoding weights corresponding to the received TPI bits. + +### 6.4A.1.2 Test case + +This subclause specifies a test case, which provides additional information for how the minimum requirement should be interpreted for the purpose of conformance testing. + +The quality level at the threshold $Q_{\text{tpi}}$ corresponds to a signal level depending on the downlink conditions F-TPICH parameters. For the conditions in Table 6.6A, a signal with the quality below the level $Q_{\text{tpi}}$ can be generated by an F-TPICH\_Ec/Ior ratio of -26 dB, and a signal with the quality above the level $Q_{\text{tpi}}$ can be generated by an F-TPICH\_Ec/Ior ratio of -12 dB. For a UE which supports the optional enhanced requirements type1 specified based on receiver diversity for F-TPICH a signal with the quality below the level $Q_{\text{tpi}}$ can be instead generated by an F-TPICH\_Ec/Ior ratio of -29 dB for the conditions in Table 6.6A, and a signal with the quality above the level $Q_{\text{tpi}}$ by an F-TPICH\_Ec/Ior ratio of -15 dB. The downlink physical channels, other than those specified in Table 6.6A, are as specified in Table C.3 of Annex C. + +Figure 6.1B shows an example scenario where the F-TPICH\_Ec/Ior ratio varies from a level where the F-TPICH is demodulated under normal conditions, down to a level below $Q_{\text{tpi}}$ where the UE shall apply the precoding weights corresponding to the last reliably received TPI bit pattern and then back up to a level above $Q_{\text{tpi}}$ where the UE shall apply the precoding weights corresponding to the received TPI bit pattern. Figure 6.1C shows an example scenario for a UE which supports the optional enhanced requirements type1 for F-TPICH, where the F-TPICH\_Ec/Ior ratio varies from a level where the F-TPICH is demodulated under normal conditions, down to a level below $Q_{\text{tpi}}$ where the UE shall apply the precoding weights corresponding to the last reliably received TPI bit pattern and then back up to a level above $Q_{\text{tpi}}$ where the UE shall apply the precoding weights corresponding to the received TPI bit pattern. Point B shall be at least 10 ms after point A, and point D shall be at least 10 ms after point C. + +For a UE which supports the optional enhanced requirements type 1 for F-TPICH, the UE shall not be tested according to the minimum requirements. + +**Table 6.6A: parameters for the out-of-quality handling of F-TPICH test case** + +| Parameter | Unit | Value | +|--------------------------------------------|--------------|--------------------------------| +| Propagation condition | | Static | +| $\hat{I}_{\text{or}}/I_{\text{oc}}$ | dB | -1 | +| $I_{\text{oc}}$ | dBm/3.84 MHz | -60 | +| $\frac{\text{F-TPICH\_Ec}}{I_{\text{or}}}$ | dB | See figure 6.1B or figure 6.1C | + +![Figure 6.1B: Test case for F-TPICH out-of-quality handling in the UE supporting the minimum requirements for F-TPICH. The graph shows a step-like signal with two transitions. The first transition is labeled 'T1' and the second 'T2'. The signal starts at a high level, drops to a low level at T1, and returns to the high level at T2. The y-axis has two tick marks, and the x-axis has two tick marks corresponding to T1 and T2. Arrows point from the labels 'T1' and 'T2' to the transition points on the x-axis.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +Figure 6.1B: Test case for F-TPICH out-of-quality handling in the UE supporting the minimum requirements for F-TPICH. The graph shows a step-like signal with two transitions. The first transition is labeled 'T1' and the second 'T2'. The signal starts at a high level, drops to a low level at T1, and returns to the high level at T2. The y-axis has two tick marks, and the x-axis has two tick marks corresponding to T1 and T2. Arrows point from the labels 'T1' and 'T2' to the transition points on the x-axis. + +Figure 6.1B: Test case for F-TPICH out-of-quality handling in the UE supporting the minimum requirements for F-TPICH + +![Figure 6.1C: Test case for F-TPICH out-of-quality handling in the UE supporting the optional enhanced requirements type1 for F-TPICH. This graph is identical to Figure 6.1B, showing a step-like signal with two transitions labeled 'T1' and 'T2'. The signal starts at a high level, drops to a low level at T1, and returns to the high level at T2. The y-axis has two tick marks, and the x-axis has two tick marks corresponding to T1 and T2. Arrows point from the labels 'T1' and 'T2' to the transition points on the x-axis.](3179e999cb73ab07fad8e9407c88a3b6_img.jpg) + +Figure 6.1C: Test case for F-TPICH out-of-quality handling in the UE supporting the optional enhanced requirements type1 for F-TPICH. This graph is identical to Figure 6.1B, showing a step-like signal with two transitions labeled 'T1' and 'T2'. The signal starts at a high level, drops to a low level at T1, and returns to the high level at T2. The y-axis has two tick marks, and the x-axis has two tick marks corresponding to T1 and T2. Arrows point from the labels 'T1' and 'T2' to the transition points on the x-axis. + +Figure 6.1C: Test case for F-TPICH out-of-quality handling in the UE supporting the optional enhanced requirements type1 for F-TPICH + +In these test cases, the requirements for the UE are that: + +1. The UE shall keep precoding weights with more than 50% of the time between point B and point C. +2. The UE apply precoding weights w.r.t. TPI bits with more than 99% of the time after point D. + +## 6.5 Transmit ON/OFF power + +### 6.5.1 Transmit OFF power + +Transmit OFF power is defined as the RRC filtered mean power when the transmitter is off. The transmitter is considered to be off when the UE is not allowed to transmit or during periods when the UE is not transmitting DPCCH due to discontinuous uplink DPCCH transmission. During UL compressed mode gaps, the UE is not considered to be off. + +#### 6.5.1.1 Minimum requirement + +The transmit OFF power is defined as the RRC filtered mean power in a duration of at least one timeslot excluding any transient periods. The requirement for the transmit OFF power shall be less than -56 dBm. + +##### 6.5.1.1A Additional requirement for DC-HSUPA + +The transmit OFF power is defined per carrier as the RRC filtered mean power in a duration of at least one timeslot excluding any transient periods. The requirement for the transmit OFF power in each carrier shall be less than -56 dBm, when the transmitters in both carriers are turned off. + +##### 6.5.1.1B Additional requirement for UL OLTD + +For the UE with two active transmit antenna connectors in UL OLTD operation, the transmit OFF power specified in sub-clause 6.5.1.1 applies at each transmit antenna connector, when the transmitter is OFF on both transmit connectors. + +##### 6.5.1.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the transmit OFF power specified in sub-clause 6.5.1.1 applies at each transmit antenna connector, when the transmitter is OFF on both transmit antenna connectors. + +For UE configured in UL CLTD activation state 2 or activation state 3, the transmit OFF power specified in sub-clause 6.5.1.1 applies at the active transmit antenna connector, when the transmitter is OFF on both transmit antenna connectors. + +##### 6.5.1.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the transmit OFF power specified in sub-clause 6.5.1.1 applies at each transmit antenna connector, when the transmitter is OFF on both transmit antenna connectors. + +##### 6.5.1.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the transmit OFF power specified in sub-clause 6.5.1.1A applies. + +## 6.5.2 Transmit ON/OFF Time mask + +The time mask for transmit ON/OFF defines the transient period allowed for the UE between transmit OFF power and transmit ON power. During the transient period there are no additional requirements on UE transmit power beyond what is required in subclause 6.2 maximum output power observed over a period of at least one timeslot. ON/OFF scenarios include PRACH preamble bursts, the beginning or end of PRACH message parts, the beginning or end of each discontinuous uplink DPCCH transmission gap and the beginning or end of UL DPCH transmissions. + +### 6.5.2.1 Minimum requirement + +The transmit power levels versus time shall meet the requirements in figure 6.2 for PRACH preambles, the requirements in figure 6.2A for discontinuous uplink DPCCH transmission and the requirements in figure 6.3 for all other cases. The off power observation period is defined as the RRC filtered mean power in a duration of at least one timeslot excluding any transient periods. The on power observation period is defined as the mean power over one timeslot excluding any transient periods. For PRACH preambles, the on power observation period is 3904 chips (4096 chips less the transient periods). + +The off power specification in figures 6.2 and 6.3 is as defined in 6.5.1.1. + +The average on power specification in figures 6.2 and 6.3 depends on each possible case. + +- First preamble of RACH: Open loop accuracy (Table 6.3). +- During preamble ramping of the RACH, and between final RACH preamble and RACH message part: Accuracy depending on size of the required power difference (Table 6.7). The step in total transmitted power between final RACH preamble and RACH message (control part + data part) shall be rounded to the closest integer dB value. A power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. +- Accuracy for the DPCCH power loop: + +After transmission gaps due to discontinuous uplink DPCCH transmission: Accuracy for the DPCCH power loop as defined in Table 6.7A. The uplink transmitter power difference tolerance after a transmission gap of up to 10 sub-frames shall be within the range as defined in Table 6.7A. The TPC\_cmd value shown in Table 6.7A corresponds to the last TPC\_cmd value received before the transmission gap and applied by the UE after the transmission gap when discontinuous uplink DPCCH transmission is activated. + +- After transmission gaps in compressed mode: Accuracy for the DPCCH power loop as in Table 6.9. +- Accuracy for the DPCCH2 power loop: + +The Accuracies are required when the power of DPCCH2 is within the range {DPCCH power + 20dB , DPCCH power – 5dB} + +After transmission gaps due to discontinuous uplink DPCCH transmission: Accuracy for the DPCCH2 power loop has the same requirement from Table 6.7A as the DPCCH power loop + +- After transmission gaps in compressed mode: Accuracy for the DPCCH2 power loop as in Table 6.9. +- Power step to Maximum Power: Maximum power accuracy (Table 6.1). + +![Diagram showing PRACH access slot and preamble durations, and a power envelope with ON/OFF power levels and transient periods.](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +The figure illustrates the transmit ON/OFF template for PRACH preambles. At the top, a horizontal double-headed arrow indicates the 'PRACH access slot' duration of '5120 chips'. Below it, another horizontal double-headed arrow indicates the 'PRACH preamble' duration of '4096 chips'. A green rectangular block represents the active preamble signal. Below this, a power envelope graph shows the transmit power over time. The power rises from a baseline 'OFF power' to an 'Average ON Power' level. The duration of the 'On power requirement' is specified as '3904 chips'. The transition from OFF to ON power is labeled as a 'Transient period ( no offpower requirements )' and is shown to occur within a '25μs' time frame. Similarly, the transition from ON to OFF power is also a 'Transient period ( no offpower requirements )' within a '25μs' time frame. The 'End of off power requirement' is marked at the start of the transient period, and the 'Start of off power requirement' is marked at the end of the transient period. + +Diagram showing PRACH access slot and preamble durations, and a power envelope with ON/OFF power levels and transient periods. + +Figure 6.2: Transmit ON/OFF template for PRACH preambles + +![Figure 6.2A: Transmit ON/OFF template for discontinuous uplink DPCCH transmission. The diagram shows two green rectangular blocks representing 'UL DPCCH 2560 chips' separated by a gap. Above the blocks, 'Slot boundaries' are indicated by vertical dashed lines. Below the blocks, a power curve is shown. The first block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The second block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The power curve transitions between 'Average ON Power' and 'OFF power*'. A 'Transient period ( no offpower requirements )' is indicated between the blocks. A note states: '*The OFF power requirement does not apply for compressed mode gaps'.](835ebc0e9ec15eea8eadc15448249226_img.jpg) + +Slot boundaries + +UL DPCCH +2560 chips + +UL DPCCH +2560 chips + +25μs ↔ 25μs + +25μs ↔ 25μs + +Average +ON Power + +Average +ON Power + +End of off power +requirement + +Start of on power +requirement + +End of on power +requirement + +Start of off power +requirement + +OFF power\* + +OFF power\* + +Transient period +( no offpower requirements ) + +\*The OFF power requirement does +not apply for compressed mode gaps + +Transient period +( no offpower requirements ) + +Figure 6.2A: Transmit ON/OFF template for discontinuous uplink DPCCH transmission. The diagram shows two green rectangular blocks representing 'UL DPCCH 2560 chips' separated by a gap. Above the blocks, 'Slot boundaries' are indicated by vertical dashed lines. Below the blocks, a power curve is shown. The first block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The second block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The power curve transitions between 'Average ON Power' and 'OFF power\*'. A 'Transient period ( no offpower requirements )' is indicated between the blocks. A note states: '\*The OFF power requirement does not apply for compressed mode gaps'. + +**Figure 6.2A: Transmit ON/OFF template for discontinuous uplink DPCCH transmission** + +![Figure 6.3: Transmit ON/OFF template for all other On/Off cases. The diagram shows two green rectangular blocks representing 'UL DPDCH or PRACH message part 2560 chips' separated by a gap. Below the blocks, a power curve is shown. The first block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The second block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The power curve transitions between 'Average ON Power' and 'OFF power*'. A 'Transient period ( no offpower requirements )' is indicated between the blocks. A note states: '*The OFF power requirement does not apply for compressed mode gaps'.](1383c500c5d34fbc2c535226f0f64fa9_img.jpg) + +UL DPDCH or PRACH +message part +2560 chips + +UL DPDCH or PRACH +message part +2560 chips + +25μs ↔ 25μs + +25μs ↔ 25μs + +Average +ON Power + +Average +ON Power + +End of off power +requirement + +Start of on power +requirement + +End of on power +requirement + +Start of off power +requirement + +OFF power\* + +OFF power\* + +Transient period +( no offpower requirements ) + +\*The OFF power requirement does +not apply for compressed mode gaps + +Transient period +( no offpower requirements ) + +Figure 6.3: Transmit ON/OFF template for all other On/Off cases. The diagram shows two green rectangular blocks representing 'UL DPDCH or PRACH message part 2560 chips' separated by a gap. Below the blocks, a power curve is shown. The first block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The second block starts at the 'Start of on power requirement' and ends at the 'End of on power requirement'. The power curve transitions between 'Average ON Power' and 'OFF power\*'. A 'Transient period ( no offpower requirements )' is indicated between the blocks. A note states: '\*The OFF power requirement does not apply for compressed mode gaps'. + +**Figure 6.3: Transmit ON/OFF template for all other On/Off cases** + +**Table 6.7: Transmitter power difference tolerance for RACH preamble ramping, and between final RACH preamble and RACH message part** + +| Power step size (Up or down)*
$\Delta P$ [dB] | Transmitter power difference tolerance [dB] | +|--------------------------------------------------|---------------------------------------------| +| 0 | +/- 1 | +| 1 | +/- 1 | +| 2 | +/- 1.5 | +| 3 | +/- 2 | +| $4 \leq \Delta P \leq 10$ | +/- 2.5 | +| $11 \leq \Delta P \leq 15$ | +/- 3.5 | +| $16 \leq \Delta P \leq 20$ | +/- 4.5 | +| $21 \leq \Delta P$ | +/- 6.5 | + +NOTE: Power step size for RACH preamble ramping is from 1 to 8 dB with 1 dB steps. + +**Table 6.7A: Transmitter power difference tolerance after a gap of up to 10 sub-frames due to discontinuous uplink DPCCH transmission** + +| Last TPC_cmd | Transmitter power step tolerance after discontinuous UL DPCCH transmission gap | | | | | | +|--------------|--------------------------------------------------------------------------------|-------|----------------|-------|----------------|-------| +| | 1 dB step size | | 2 dB step size | | 3 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | +| + 1 | -2 dB | +4 dB | -1 dB | +5 dB | 0 dB | +6 dB | +| 0 | -3 dB | +3 dB | -3 dB | +3 dB | -3 dB | +3 dB | +| -1 | -4 dB | +2 dB | -5 dB | +1 dB | -6 dB | 0 dB | + +#### 6.5.2.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the minimum requirements except the requirement with PRACH specified in sub-clause 6.5.2.1 apply at each transmit antenna connector. + +#### 6.5.2.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the minimum requirements specified in sub-clause 6.5.2.1 except the requirement with PRACH apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the minimum requirements in sub-clause 6.5.2.1 except the requirement with PRACH apply at the active transmit antenna connector. + +#### 6.5.2.1C Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the minimum requirements specified in sub-clause 6.5.2.1, except the requirement with PRACH, apply at each transmit antenna connector. + +#### 6.5.2.1D Additional requirement for DB-DC-HSUPA operating simultaneously with CS + +For UE supporting DB-DC-HSUPA operation simultaneously with CS, the minimum requirements specified in sub-clause 6.5.2.1 apply for the primary carrier. + +### 6.5.3 Change of TFC + +A change of TFC (Transport Format Combination) in uplink means that the power in the uplink varies according to the change in data rate. DTX, where the DPDCH is turned off, is a special case of variable data, which is used to minimise + +the interference between UE(s) by reducing the UE transmit power when voice, user or control information is not present. + +### 6.5.3.1 Minimum requirement + +A change of output power is required when the TFC, and thereby the data rate, is changed. The ratio of the amplitude between the DPDCH codes and the DPCCH code will vary. The power step due to a change in TFC shall be calculated in the UE so that the power transmitted on the DPCCH shall follow the inner loop power control. The step in total transmitted power (DPCCH + DPDCH) shall then be rounded to the closest integer dB value. A power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. The accuracy of the power step, given the step size, is specified in Table 6.8. The power change due to a change in TFC is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot, not including the transient duration. The transient duration is from 25 $\mu$ s before the slot boundary to 25 $\mu$ s after the slot boundary. + +**Table 6.8: Transmitter power step tolerance** + +| Power step size (Up or down)
$\Delta P$ [dB] | Transmitter power step
tolerance [dB] | +|-------------------------------------------------|------------------------------------------| +| 0 | +/- 0.5 | +| 1 | +/- 0.5 | +| 2 | +/- 1.0 | +| 3 | +/- 1.5 | +| $4 \leq \Delta P \leq 10$ | +/- 2.0 | +| $11 \leq \Delta P \leq 15$ | +/- 3.0 | +| $16 \leq \Delta P \leq 20$ | +/- 4.0 | +| $21 \leq \Delta P$ | +/- 6.0 | + +The mean power of successive slots shall be calculated according to Figure 6.4. + +![Figure 6.4: Transmit template during TFC change. The diagram illustrates the timing and power levels for Up-Link DPDCH and DPCCH across slot boundaries. Two slots are shown, each 2560 chips long. The DPDCH power level increases in the second slot. Below the channel bars, a power curve shows the transition. Mean power is measured over 2368 chips in each slot. A transient period of 50μs (25μs before and 25μs after the slot boundary) is marked where no offpower requirements apply. The power curve shows a rise during this transient period between the two mean power levels.](f455955c4bc84005728b4138f19098dc_img.jpg) + +Figure 6.4: Transmit template during TFC change. The diagram illustrates the timing and power levels for Up-Link DPDCH and DPCCH across slot boundaries. Two slots are shown, each 2560 chips long. The DPDCH power level increases in the second slot. Below the channel bars, a power curve shows the transition. Mean power is measured over 2368 chips in each slot. A transient period of 50μs (25μs before and 25μs after the slot boundary) is marked where no offpower requirements apply. The power curve shows a rise during this transient period between the two mean power levels. + +**Figure 6.4: Transmit template during TFC change** + +**6.5.3.1A Additional requirement for UL OLTd** + +For UE with two active transmit antenna connectors in UL OLTd operation, the minimum requirements specified in sub-clause 6.5.3.1 apply at each transmit antenna connector. + +**6.5.3.1B Additional requirement for UL CLTD** + +A change of output power is required when the TFC, and thereby the data rate, is changed. The ratio of the amplitude between the DPDCH codes and the DPCCH code will vary. The power step due to a change in TFC shall be calculated in the UE so that the power transmitted on the DPCCH shall follow the inner loop power control. The step in total transmitted power (DPCCH + S-DPCCH + DPDCH for UE configured in UL CLTD activation state 1, and DPCCH + DPDCH for UE configured in UL CLTD activation state 2 or activation state 3) shall then be rounded to the closest integer dB value. A power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. The accuracy of the power step, given the step size, is specified in Table 6.8 at each transmit antenna connector. The power change at each transmit antenna connector due to a change in TFC is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot, not including the transient duration. The transient duration is from 25μs before the slot boundary to 25μs after the slot boundary. + +### 6.5.3.1C Additional requirement for DB-DC-HSUPA operating simultaneously with CS + +For UE supporting DB-DC-HSUPA operating simultaneously with CS, the minimum requirements specified in sub-clause 6.5.3.1 apply for the primary carrier. + +## 6.5.4 Power setting in uplink compressed mode + +Compressed mode in uplink means that the power in uplink is changed. + +### 6.5.4.1 Minimum requirement + +A change of output power is required during uplink compressed frames since the transmission of data is performed in a shorter interval. The ratio of the amplitude between the DPDCH codes and the DPCCH code will also vary. The power step due to compressed mode shall be calculated in the UE so that the energy transmitted on the pilot bits during each transmitted slot shall follow the inner loop power control. + +Thereby, the power during compressed mode, and immediately afterwards, shall be such that the mean power of the DPCCH follows the steps due to inner loop power control combined with additional steps of $10\text{Log}_{10}(N_{\text{pilot,prev}} / N_{\text{pilot,curr}})$ dB where $N_{\text{pilot,prev}}$ is the number of pilot bits in the previously transmitted slot, and $N_{\text{pilot,curr}}$ is the current number of pilot bits per slot. + +The resulting step in total transmitted power (DPCCH +DPDCH) shall then be rounded to the closest integer dB value. A power step exactly half-way between two integer values shall be rounded to the closest integer of greatest magnitude. The accuracy of the power step, given the step size, is specified in Table 6.8 in subclause 6.5.3.1. The power step is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot, when neither the original timeslot nor the reference timeslot are in a transmission gap. The transient duration is not included, and is from 25 $\mu\text{s}$ before the slot boundary to 25 $\mu\text{s}$ after the slot boundary. + +In addition to any power change due to the ratio $N_{\text{pilot,prev}} / N_{\text{pilot,curr}}$ , the mean power of the DPCCH in the first slot after a compressed mode transmission gap shall differ from the mean power of the DPCCH in the last slot before the transmission gap by an amount $\Delta_{\text{RESUME}}$ , where $\Delta_{\text{RESUME}}$ is calculated as described in clause 5.1.2.3 of TS 25.214. + +The resulting difference in the total transmitted power (DPCCH + DPDCH) shall then be rounded to the closest integer dB value. A power difference exactly half-way between two integer values shall be rounded to the closest integer of greatest magnitude. The accuracy of the resulting difference in the total transmitted power (DPCCH + DPDCH) after a transmission gap of up to 14 slots shall be as specified in Table 6.9. + +**Table 6.9: Transmitter power difference tolerance after a transmission gap of up to 14 slots** + +| Power difference (Up or down)
$\Delta P$ [dB] | Transmitter power step
tolerance after a transmission
gap [dB] | +|--------------------------------------------------|----------------------------------------------------------------------| +| $\Delta P \leq 2$ | +/- 3 | +| 3 | +/- 3 | +| $4 \leq \Delta P \leq 10$ | +/- 3.5 | +| $11 \leq \Delta P \leq 15$ | +/- 4 | +| $16 \leq \Delta P \leq 20$ | +/- 4.5 | +| $21 \leq \Delta P$ | +/- 6.5 | + +The power difference is defined as the difference between the mean power of the original (reference) timeslot before the transmission gap and the mean power of the target timeslot after the transmission gap, not including the transient durations. The transient durations at the start and end of the transmission gaps are each from 25 $\mu\text{s}$ before the slot boundary to 25 $\mu\text{s}$ after the slot boundary. + +The mean power of successive slots shall be calculated according to figure 6.5. + +![Figure 6.5: Transmit template during compressed mode. The diagram shows two horizontal timelines for Up-Link DPDCH and Up-Link DPCCH. Above the timelines, 'Slot boundaries' are indicated by vertical dashed lines. The first slot is labeled 'UL slot 2560 chips' and the second is also labeled 'UL slot 2560 chips'. Below the timelines, a power curve is shown. The curve has a 'Transient period ( no off power requirements )' at the start, followed by a 'Gap period ( no off power requirements )' in the middle, and another 'Transient period ( no off power requirements )' at the end. The 'Mean power 2368 chips' is indicated for the first and second transient periods. Time intervals of 25μs are marked between the start of each slot and the start of the corresponding transient period.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +Figure 6.5: Transmit template during compressed mode. The diagram shows two horizontal timelines for Up-Link DPDCH and Up-Link DPCCH. Above the timelines, 'Slot boundaries' are indicated by vertical dashed lines. The first slot is labeled 'UL slot 2560 chips' and the second is also labeled 'UL slot 2560 chips'. Below the timelines, a power curve is shown. The curve has a 'Transient period ( no off power requirements )' at the start, followed by a 'Gap period ( no off power requirements )' in the middle, and another 'Transient period ( no off power requirements )' at the end. The 'Mean power 2368 chips' is indicated for the first and second transient periods. Time intervals of 25μs are marked between the start of each slot and the start of the corresponding transient period. + +Figure 6.5: Transmit template during compressed mode + +#### 6.5.4.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the minimum requirements specified in sub-clause 6.5.4.1 apply at each UE antenna connector. + +#### 6.5.4.1B Additional requirement for UL CLTD + +A change of output power is required during uplink compressed frames since the transmission of data is performed in a shorter interval. The ratio of the amplitude between the DPDCH codes and the DPCCH code will also vary. The power step due to compressed mode shall be calculated in the UE so that the energy transmitted on the pilot bits during each transmitted slot shall follow the inner loop power control. + +Thereby, the power during compressed mode, and immediately afterwards, shall be such that the mean power of the DPCCH follows the steps due to inner loop power control combined with additional steps of $10\text{Log}_{10}(N_{\text{pilot,prev}} / N_{\text{pilot,curr}})$ dB where $N_{\text{pilot,prev}}$ is the number of pilot bits in the previously transmitted slot, and $N_{\text{pilot,curr}}$ is the current number of pilot bits per slot. + +The resulting step in total transmitted power (DPCCH + S-DPCCH +DPDCH for UE configured in UL CLTD activation state 1, and DPCCH + DPDCH for UE configured in UL CLTD activation state 2 or activation state 3) shall + +then be rounded to the closest integer dB value. A power step exactly half-way between two integer values shall be rounded to the closest integer of greatest magnitude. The accuracy of the power step at each transmit antenna connector, given the step size, is specified in Table 6.8 in subclause 6.5.3.1. The power step is defined as the relative power difference between the mean power of the original (reference) timeslot and the mean power of the target timeslot, when neither the original timeslot nor the reference timeslot are in a transmission gap. The transient duration is not included, and is from 25 $\mu$ s before the slot boundary to 25 $\mu$ s after the slot boundary. + +In addition to any power change due to the ratio $N_{\text{pilot,prev}} / N_{\text{pilot,curr}}$ , the mean power of the DPCCH in the first slot after a compressed mode transmission gap shall differ from the mean power of the DPCCH in the last slot before the transmission gap by an amount $\Delta_{\text{RESUME}}$ , where $\Delta_{\text{RESUME}}$ is calculated as described in clause 5.1.2.3 of TS 25.214. + +The resulting difference in the total transmitted power (DPCCH + S-DPCCH + DPDCH for UE configured in UL CLTD activation state 1, and DPCCH + DPDCH for UE configured in UL CLTD activation state 2 or activation state 3) shall then be rounded to the closest integer dB value. A power difference exactly half-way between two integer values shall be rounded to the closest integer of greatest magnitude. The accuracy of the resulting difference in the total transmitted power (DPCCH + S-DPCCH + DPDCH for UE configured in UL CLTD activation state 1, and DPCCH + DPDCH for UE configured in UL CLTD activation state 2 or activation state 3) after a transmission gap of up to 14 slots shall be as specified in Table 6.9 at each transmit antenna connector. + +The power difference at each transmit antenna connector is defined as the difference between the mean power of the original (reference) timeslot before the transmission gap and the mean power of the target timeslot after the transmission gap, not including the transient durations. The transient durations at the start and end of the transmission gaps are each from 25 $\mu$ s before the slot boundary to 25 $\mu$ s after the slot boundary. The mean power of successive slots shall be calculated according to figure 6.5. + +#### 6.5.4.1C Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the minimum requirements specified in sub-clause 6.5.4.1 apply for the primary carrier. + +### 6.5.5 HS-DPCCH + +The transmission of Ack/Nack or CQI over the HS-DPCCH may cause the transmission power in the uplink to vary. The ratio of the amplitude between the DPCCH and the Ack/Nack and CQI respectively is signalled by higher layers. + +#### 6.5.5.1 Minimum requirement + +The nominal sum power on DPCCH+DPDCH is independent of the transmission of Ack/Nack and CQI unless the UE output power when Ack/Nack or CQI is transmitted would exceed the maximum value specified in Table 6.1A or fall below the value specified in 6.4.3.1, whereupon the UE shall apply additional scaling to the total transmit power as defined in section 5.1.2.6 of TS.25.214 [8]. + +The composite transmitted power (DPCCH + DPDCH+HS-DPCCH) may then also be rounded to the closest integer dB value. If rounding is done a power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. + +The nominal power step due to transmission of Ack/Nack or CQI is defined as the difference between the nominal mean powers of two power evaluation periods either side of an HS-DPCCH boundary. The first evaluation period starts 25 $\mu$ s after a DPCCH slot boundary and ends 25 $\mu$ s before the following HS-DPCCH slot boundary. The second evaluation period starts 25 $\mu$ s after the same HS-DPCCH slot boundary and ends 25 $\mu$ s before the following DPCCH slot boundary. This is described graphically in figure 6.6. + +![Figure 6.6: Transmit power template during HS-DPCCH transmission. The diagram shows three horizontal timelines for Up-Link HS-DPCCH, Up-Link DPDCH, and Up-Link DPCCH. The HS-DPCCH timeline has green rectangular blocks representing slots, with vertical dashed lines marking slot boundaries. The DPDCH and DPCCH timelines show continuous transmission. Below these, a graph plots transmit power over time. The power level is shown as a black line that steps up and down at specific points. Vertical dashed lines from the slot boundaries above align with the power steps. Labels include 'DPCCH 2560 chip Slot boundaries', 'HS-DPCCH 2560 chip Slot boundaries', 'DPCCH to HS-DPCCH timing offset', 'Mean power' (indicated by horizontal double-headed arrows), 'Power step' (indicated by vertical double-headed arrows), and asterisks (*) for steps due to inner loop power control and double asterisks (**) for steps due to CQI transmission.](89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg) + +Figure 6.6: Transmit power template during HS-DPCCH transmission. The diagram shows three horizontal timelines for Up-Link HS-DPCCH, Up-Link DPDCH, and Up-Link DPCCH. The HS-DPCCH timeline has green rectangular blocks representing slots, with vertical dashed lines marking slot boundaries. The DPDCH and DPCCH timelines show continuous transmission. Below these, a graph plots transmit power over time. The power level is shown as a black line that steps up and down at specific points. Vertical dashed lines from the slot boundaries above align with the power steps. Labels include 'DPCCH 2560 chip Slot boundaries', 'HS-DPCCH 2560 chip Slot boundaries', 'DPCCH to HS-DPCCH timing offset', 'Mean power' (indicated by horizontal double-headed arrows), 'Power step' (indicated by vertical double-headed arrows), and asterisks (\*) for steps due to inner loop power control and double asterisks (\*\*) for steps due to CQI transmission. + +The power step due to HS-DPCCH transmission is the difference between the mean powers transmitted before and after an HS-DPCCH slot boundary. The mean power evaluation period excludes a 25μs period before and after any DPCCH or HS-DPCCH slot boundary. + +**Figure 6.6: Transmit power template during HS-DPCCH transmission** + +The tolerance of the power step due to transmission of the HS-DPCCH shall meet the requirements in table 6.9A. For each direction, up to 2 exceptions to the transmitter power step tolerance defined in table 6.9A shall be allowed. The transmitter power control range for exceptions is defined in table 6.9B. Exceptions are applicable only if the change in UL power is measured per 1-dB step size. + +**Table 6.9A: Transmitter power step tolerance** + +| Nominal power step size (Up or down) ΔP [dB] | Transmitter power step tolerance [dB] | +|----------------------------------------------|---------------------------------------| +| 0 | +/- 0.5 | +| 1 | +/- 0.5 | +| 2 | +/- 1.0 | +| 3 | +/- 1.5 | +| $4 \leq \Delta P \leq 10$ | +/- 2.0 | +| $11 \leq \Delta P \leq 15$ | +/- 3.0 | + +**Table 6.9B: Transmitter power step tolerance for exceptions** + +| Nominal power step size (Up or down) ΔP [dB] | Transmitter power step tolerance [dB] | +|----------------------------------------------|---------------------------------------| +| 0 | +/- 0.5 | +| 1 | +/- 1.5 | +| 2 | +/- 1.5 | +| 3 | +/- 1.5 | +| $4 \leq \Delta P \leq 7$ | +/- 2.0 | + +#### 6.5.5.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the minimum requirements specified in sub-clause 6.5.5.1 apply at each transmit antenna connector. + +#### 6.5.5.1B Additional requirement for UL CLTD + +The nominal sum power on DPCCH+S-DPCCH+DPDCH is independent of the transmission of Ack/Nack and CQI unless the UE output power when Ack/Nack or CQI is transmitted would exceed the maximum value specified in Table 6.1A or fall below the value specified in 6.4.3.1, whereupon the UE shall apply additional scaling to the total transmit power as defined in section 5.1.2.6 of TS.25.214 [8]. + +The composite transmitted power (DPCCH + S-DPCCH + DPDCH+HS-DPCCH) may then also be rounded to the closest integer dB value. If rounding is done a power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. + +The nominal power step due to transmission of Ack/Nack or CQI is defined as the difference between the nominal mean powers of two power evaluation periods either side of an HS-DPCCH boundary. The first evaluation period starts 25 $\mu$ s after a DPCCH slot boundary and ends 25 $\mu$ s before the following HS-DPCCH slot boundary. The second evaluation period starts 25 $\mu$ s after the same HS-DPCCH slot boundary and ends 25 $\mu$ s before the following DPCCH slot boundary. + +The tolerance of the power step due to transmission of the HS-DPCCH shall meet the requirements in table 6.9A at each transmit antenna connector. + +#### 6.5.5.1C Additional requirement for UL MIMO + +The nominal sum power on DPCCH+S-DPCCH+E-DPDCH+S-E-DPDCH+E-DPCCH+S-E-DPCCH is independent of the transmission of Ack/Nack and CQI unless the UE output power when Ack/Nack or CQI is transmitted would exceed the maximum value specified in Table 6.1AC or fall below the value specified in 6.4.3.1D, whereupon the UE shall apply additional scaling to the total transmit power as defined in section 5.1.2.6 of TS.25.214 [8]. + +The composite transmitted power (DPCCH + S-DPCCH + E-DPDCH + S-E-DPDCH + E-DPCCH + S-E-DPCCH +HS-DPCCH) may then also be rounded to the closest integer dB value. If rounding is done a power step exactly half-way between two integer values shall be rounded to the closest integer of greater magnitude. + +The nominal power step due to transmission of Ack/Nack or CQI is defined as the difference between the nominal mean powers of two power evaluation periods either side of an HS-DPCCH boundary. The first evaluation period starts 25 $\mu$ s after a DPCCH slot boundary and ends 25 $\mu$ s before the following HS-DPCCH slot boundary. The second evaluation period starts 25 $\mu$ s after the same HS-DPCCH slot boundary and ends 25 $\mu$ s before the following DPCCH slot boundary. + +The tolerance of the power step due to transmission of the HS-DPCCH shall meet the requirements in table 6.9A at each transmit antenna connector. + +#### 6.5.5.1D Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the minimum requirements specified in sub-clause 6.5.5.1 apply to the primary carrier which carries HS-DPCCH. + +## 6.6 Output RF spectrum emissions + +### 6.6.1 Occupied bandwidth + +Occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum, centered on the assigned channel frequency. The occupied channel bandwidth shall be less than 5 MHz based on a chip rate of 3.84 Mcps. + +#### 6.6.1A Occupied bandwidth for DC-HSUPA + +In the case dual adjacent carriers are assigned in the uplink, occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum, centered at the center of the assigned channel frequencies. The occupied channel bandwidth shall be less than 10 MHz on a chip rate of 3.84 Mcps. + +#### 6.6.1B Occupied bandwidth for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, occupied bandwidth requirement is defined per UE. + +The occupied bandwidth of the UL OLTD UE is determined by the occupied bandwidth (defined in 6.6.1) measured at each active antenna port of the UE. The upper boundary of the UE occupied bandwidth is the highest boundary of the two measured occupied bandwidths. The lower boundary of the UE occupied bandwidth is the lowest boundary of the two measured occupied bandwidths. The occupied channel bandwidth for UE shall be less than 5 MHz based on a chip rate of 3.84 Mcps. + +#### 6.6.1C Occupied bandwidth for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, occupied bandwidth requirement is defined per UE. + +The occupied bandwidth of the UL CLTD UE is determined by the occupied bandwidth (defined in 6.6.1) measured at each active antenna port of the UE. The upper boundary of the UE occupied bandwidth is the highest boundary of the two measured occupied bandwidths. The lower boundary of the UE occupied bandwidth is the lowest boundary of the two measured occupied bandwidths. The occupied channel bandwidth for UE shall be less than 5 MHz based on a chip rate of 3.84 Mcps. + +For UE configured in UL CLTD activation state 2 or activation state 3, the requirement in sub-clause 6.6.1 apply at the active transmit antenna connector. + +#### 6.6.1D Occupied bandwidth for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, occupied bandwidth requirement is defined per UE. + +The occupied bandwidth of the UL MIMO UE is determined by the occupied bandwidth (defined in 6.6.1) measured at each active antenna connector of the UE. The upper boundary of the UE occupied bandwidth is the higher upper boundary of the two measured occupied bandwidths. The lower boundary of the UE occupied bandwidth is the lower low boundary of the two measured occupied bandwidths. The occupied channel bandwidth for UE shall be less than 5 MHz based on a chip rate of 3.84 Mcps. + +#### 6.6.1E Occupied bandwidth for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, occupied bandwidth requirement is defined per carrier. + +The occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum, centered on the assigned channel frequency. The occupied channel bandwidth for UE shall be less than 5 MHz based on a chip rate of 3.84 Mcps. + +## 6.6.2 Out of band emission + +Out of band emissions are unwanted emissions immediately outside the nominal channel resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and Adjacent Channel Leakage power Ratio. + +### 6.6.2.1 Spectrum emission mask + +The spectrum emission mask of the UE applies to frequencies, which are between 2.5 MHz and 12.5 MHz away from the UE centre carrier frequency. The out of channel emission is specified relative to the RRC filtered mean power of the UE carrier. + +#### 6.6.2.1.1 Minimum requirement + +The power of any UE emission shall not exceed the levels specified in Table 6.10. The absolute requirement is based on a -50 dBm/3.84 MHz minimum power threshold for the UE. This limit is expressed for the narrower measurement bandwidths as -55.8 dBm/1 MHz and -71.1 dBm/30 kHz. The requirements are applicable for all values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8]. + +**Table 6.10: Spectrum Emission Mask Requirement** + +| \Delta f in MHz
(Note 1) | Minimum requirement (Note 2) | | Measurement
bandwidth | +|--------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| | Relative requirement | Absolute
requirement | | +| 2.5 - 3.5 | $\left\{ - 35 - 15 \cdot \left( \frac{\Delta f}{MHz} - 2.5 \right) \right\} dBc$ | -71.1 dBm | 30 kHz
(Note 3) | +| 3.5 - 7.5 | $\left\{ - 35 - 1 \cdot \left( \frac{\Delta f}{MHz} - 3.5 \right) \right\} dBc$ | -55.8 dBm | 1 MHz
(Note 4) | +| 7.5 - 8.5 | $\left\{ - 39 - 10 \cdot \left( \frac{\Delta f}{MHz} - 7.5 \right) \right\} dBc$ | -55.8 dBm | 1 MHz
(Note 4) | +| 8.5 - 12.5 MHz | -49 dBc | -55.8 dBm | 1 MHz
(Note 4) | + +Note 1: $\Delta f$ is the separation between the carrier frequency and the centre of the measurement bandwidth. + +Note 2: The minimum requirement is calculated from the relative requirement or the absolute requirement, whichever is the higher power. + +Note 3: The first and last measurement position with a 30 kHz filter is at $\Delta f$ equals to 2.515 MHz and 3.485 MHz. + +Note 4: The first and last measurement position with a 1 MHz filter is at $\Delta f$ equals to 4 MHz and 12 MHz. + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI the minimum requirement is calculated from the minimum requirement in table 6.10 or the applicable additional requirement in Tables 6.10A, 6.10B or 6.10C, whichever is the tighter requirement. + +**Table 6.10A: Additional spectrum emission limits for Bands II, IV, X and XXV** + +| \Delta f in MHz
(Note 1) | Frequency offset of
measurement filter centre
frequency, f\_offset | Additional
requirements Band II,
IV, X | Measurement
bandwidth | +|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.485 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq 12.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f\_offset < 12.0 \text{ MHz}$ | -13 dBm | 1 MHz | +| Note 1: $\Delta f$ is the separation between the carrier frequency and the centre of the measurement bandwidth. | | | | + +**Table 6.10B: Additional spectrum emission limits for Band V and XXVI** + +| \Delta f in MHz
(Note 1) | Frequency offset of
measurement filter centre
frequency, f\_offset | Additional
requirements Band V | Measurement
bandwidth | +|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.485 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq 12.5 \text{ MHz}$ | $3.55 \text{ MHz} \leq f\_offset < 12.45 \text{ MHz}$ | -13 dBm | 100 kHz | +| Note 1: $\Delta f$ is the separation between the carrier frequency and the centre of the measurement bandwidth. | | | | + +**Table 6.10C: Additional spectrum emission limits for Bands XII, XIII, XIV** + +| \Delta f in MHz
(Note 1) | Frequency offset of
measurement filter centre
frequency, f\_offset | Additional
requirements Band
XII, XIII, XIV | Measurement
bandwidth | +|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------|----------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.585 \text{ MHz}$ | -13 dBm | 30 kHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 12.45 \text{ MHz}$ | $2.65 \text{ MHz} \leq f\_offset < 12.45 \text{ MHz}$ | -13 dBm | 100 kHz | +| Note 1: $\Delta f$ is the separation between the carrier frequency and the centre of the measurement bandwidth. | | | | + +NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth specified in tables 6.10, 6.10A, 6.10B and 6.10C. 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.2.1A Additional Spectrum emission mask for DC-HSUPA + +The spectrum emission mask of the UE applies to frequencies, which are between 5 MHz and 20 MHz away from the UE centre frequency of the two assigned channel frequencies. The requirements assume that the UE output power shall be maximum level. The reference measurement channels for the requirements in subclause 6.6.2.1A.1 and 6.6.2.1A.2 are provided in subclause A.2.8. + +##### 6.6.2.1A.1 Minimum requirement + +The power of any UE emission shall not exceed the levels specified in Table 6.10D for the specified channel bandwidth. + +**Table 6.10D: Spectrum emission mask for DC-HSUPA** + +| \Delta f
(MHz) | Frequency offset of
measurement filter centre
frequency, f\_offset | Spectrum emission
limit (dBm) | Measurement
bandwidth | +|----------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------|----------------------------------| +| $\pm 5-6$ | $5.015\text{MHz} \leq f\_offset < 5.985\text{MHz}$ | -18 | 30 kHz | +| $\pm 6-10$ | $6.5\text{MHz} \leq f\_offset < 10.0\text{MHz}$ | -10 | 1 MHz | +| $\pm 10-19$ | $10.0\text{MHz} \leq f\_offset < 19.0\text{MHz}$ | -13 | 1 MHz | +| $\pm 19-20$ | $19.0\text{MHz} \leq f\_offset < 19.5\text{MHz}$ | -25 | 1 MHz | + +Note: $\Delta f$ is the separation between the center of two assigned channel frequencies and the centre of the measurement bandwidth. + +#### 6.6.2.1A.2 Additional requirement for band II, IV, V, X, XXV and XXVI + +The UE shall meet an additional requirement specified in Table 6.10E for band II, IV, V, X, XXV and XXVI. + +**Table 6.10E: Additional spectrum emission mask for DC-HSUPA in band II, IV, V, X, XXV and XXVI** + +| \Delta f
(MHz) | Frequency offset of
measurement filter centre
frequency, f\_offset | Spectrum emission
limit (dBm) | Measurement
bandwidth | +|----------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------|----------------------------------| +| $\pm 5-6$ | $5.015\text{MHz} \leq f\_offset < 5.985\text{MHz}$ | -18 | 30 kHz | +| $\pm 6-19$ | $6.5\text{MHz} \leq f\_offset < 19.0\text{MHz}$ | -13 | 1 MHz | +| $\pm 19-20$ | $19.0\text{MHz} \leq f\_offset < 19.5\text{MHz}$ | -25 | 1 MHz | + +Note: $\Delta f$ is the separation between the center of two assigned channel frequencies and the centre of the measurement bandwidth. + +#### 6.6.2.1B Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the spectrum emission mask specified in sub-clause 6.6.2.1 applies at each transmit antenna connector. + +#### 6.6.2.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the spectrum emission mask specified in sub-clause 6.6.2.1 applies at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the requirements in sub-clause 6.6.2.1 apply at the active transmit antenna connector. + +#### 6.6.2.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the spectrum emission mask specified in sub-clause 6.6.2.1 applies at each transmit antenna connector. + +#### 6.6.2.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the spectrum emission mask specified in sub-clause 6.6.2.1 applies at each carrier. + +## 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) + +In the case a single carrier is assigned on the uplink, Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency. + +In the case dual adjacent carriers are assigned on the uplink, ACLR is the ratio of the sum of the RRC filtered mean powers centered on each of the two assigned channel frequencies to the RRC filtered mean power centered on an adjacent channel frequency. + +### 6.6.2.2.1 Minimum requirement + +If the adjacent channel power is greater than -50dBm then the ACLR shall be higher than the value specified in Table 6.11. The requirements are applicable for all values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8]. + +**Table 6.11: UE ACLR** + +| Power Class | Adjacent channel frequency relative to assigned channel frequency | ACLR limit | +|-------------|-------------------------------------------------------------------|------------| +| 3 | + 5 MHz or - 5 MHz | 33 dB | +| 3 | + 10 MHz or - 10 MHz | 43 dB | +| 4 | + 5 MHz or - 5 MHz | 33 dB | +| 4 | + 10 MHz or -10 MHz | 43 dB | + +NOTE 1: The requirement shall still be met in the presence of switching transients. + +NOTE 2: The ACLR requirements reflect what can be achieved with present state of the art technology. + +NOTE 3: Requirement on the UE shall be reconsidered when the state of the art technology progresses. + +### 6.6.2.2.1A Additional requirement for DC-HSUPA + +If the adjacent channel power is greater than -50dBm then the ACLR shall be higher than the value specified in Table 6.11A. The requirements are applicable for all values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8]. The reference measurement channels for the requirements in subclause 6.6.2.2.1A are provided in subclause A.2.8. + +**Table 6.11A: UE ACLR for DC-HSUPA** + +| Power Class | Adjacent channel frequency relative to the center of two assigned channel frequencies | ACLR limit | +|-------------|---------------------------------------------------------------------------------------|------------| +| 3 | + 7.5 MHz or - 7.5 MHz | 33 dB | +| 3 | + 12.5 MHz or - 12.5 MHz | 36 dB | +| 4 | + 7.5 MHz or - 7.5 MHz | 33 dB | +| 4 | + 12.5 MHz or -12.5 MHz | 36 dB | + +NOTE 1: The requirement shall still be met in the presence of switching transients. + +NOTE 2: The ACLR requirements reflect what can be achieved with present state of the art technology. + +NOTE 3: Requirement on the UE shall be reconsidered when the state of the art technology progresses. + +### 6.6.2.2.1B Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the ACLR requirements specified in subclause 6.6.2.2.1 apply at each transmit antenna connector. + +#### 6.6.2.2.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the ACLR requirements specified in sub-clause 6.6.2.2.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the ACLR requirements specified in sub-clause 6.6.2.2.1 apply at the active transmit antenna connector. + +#### 6.6.2.2.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the ACLR requirements specified in sub-clause 6.6.2.2.1 apply at each transmit antenna connector. + +#### 6.6.2.2.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the ACLR requirements specified in sub-clause 6.6.2.2.1 apply to each carrier. + +### 6.6.3 Spurious emissions + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The frequency boundary and the detailed transitions of the limits between the requirement for out band emissions and spectrum emissions are based on ITU-R Recommendations SM.329 [2]. + +#### 6.6.3.1 Minimum requirement + +These requirements are only applicable for frequencies, which are greater than 12.5 MHz away from the UE centre carrier frequency. + +**Table 6.12: General spurious emissions requirements** + +| Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | Note | +|-----------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|--------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | 1 kHz | -36 dBm | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | 10 kHz | -36 dBm | | +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | 100 kHz | -36 dBm | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | 1 MHz | -30 dBm | | +| $12.75 \text{ GHz} \leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the UL operating band in GHz | 1 MHz | -30 dBm | Note 1 | + +NOTE 1: Applies only for Band XXII. + +**Table 6.13: Additional spurious emissions requirements** + +| Operating Band | Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | +|----------------|-------------------------------------|-----------------------|---------------------| +| I | 460 MHz $\leq f \leq 467.5$ MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq 821$ MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f < 925$ MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq 935$ MHz | 100 kHz | -67 dBm * | +| | | 3.84MHz | -60 dBm | +| | 935 MHz $< f \leq 960$ MHz | 100 kHz | -79 dBm * | +| | | 3.84MHz | -60 dBm | +| | 1427 MHz $\leq f \leq 1518$ MHz | 1 MHz | -50 dBm | +| | 1452 MHz $\leq f \leq 1510.9$ MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq 1880$ MHz | 100 kHz | -71 dBm * | +| | | 3.84MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq 1879.9$ MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $< f < 1915.7$ MHz | 300 kHz | -41 dBm | +| | 2010 MHz $< f < 2025$ MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq 2400$ MHz | 3.84 MHz | -60 dBm | +| | 2496 MHz $\leq f \leq 2570$ MHz | 1 MHz | -50 dBm | +| | 2570 MHz $\leq f \leq 2690$ MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq 3590$ MHz | 3.84 MHz | -60 dBm | +| | 3300 MHz $\leq f \leq 3800$ MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq 4200$ MHz | 1 MHz | -50 dBm** | +| | 4400 MHz $\leq f \leq 5000$ MHz | 1 MHz | -50 dBm | +| II | 617 MHz $\leq f \leq 652$ MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq 728$ MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq 746$ MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq 758$ MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq 768$ MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq 1518$ MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq 1559$ MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq 1995$ MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq 2020$ MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq 2360$ MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq 2495$ MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq 2690$ MHz | 1 MHz | -50 dBm | +| | 3510 MHz $\leq f \leq 3590$ MHz | 3.84 MHz | -60 dBm | +| | 3400 MHz $\leq f \leq 3800$ MHz | 1 MHz | -50 dBm** | +| III | 460 MHz $\leq f \leq 467.5$ MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq 821$ MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm ***** | +| | 921 MHz $\leq f < 925$ MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq 935$ MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq 960$ MHz | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | + +| | | | | +|----|-------------------------------------|----------|---------------| +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $\leq f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm ***** | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 3.84 MHz | -60 dBm | +| | 1880 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm ***** | +| | 2010 MHz $< f <$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2496 MHz $\leq f \leq$ 2570 MHz | 1 MHz | -50 dBm | +| | 2570 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm ** | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm ** | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm | +| IV | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm** | +| V | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 859 MHz $\leq f \leq$ 869 MHz | 1 MHz | -27 dBm | +| | 869 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm** | +| | 2570 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm | + +| | | | | +|------|-------------------------------------|----------|--------------| +| | 3300 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm** | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm** | +| VI | 758 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 860 MHz $\leq f <$ 875 MHz | 1 MHz | -37 dBm | +| | 875 MHz $\leq f \leq$ 890 MHz | 3.84 MHz | -60 dBm | +| | 945 MHz $\leq f \leq$ 960 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 2010 MHz $< f <$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq$ 2575 MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq$ 2645 MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq$ 3600 MHz | 1 MHz | -50 dBm | +| VII | 461 MHz $\leq f \leq$ 466 MHz | 1 MHz | -50 dBm | +| | 462.5 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 738 MHz $\leq f \leq$ 758 MHz | 1 MHz | -50 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 791 MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f <$ 925 MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1427 MHz $< f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $< f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 100 kHz | -71 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1900 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 2010 MHz $< f <$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $< f <$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 2595 MHz $\leq f \leq$ 2620 MHz | 1 MHz | -40 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm | +| VIII | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -60 dBm | +| | 860 MHz $\leq f \leq$ 890 MHz | 1 MHz | -37 dBm **** | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $\leq f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | + +| | | | | +|----|-------------------------------------|----------|----------------| +| | 1475.9 MHz $\leq f \leq 1510.9$ MHz | 3.84 MHz | -60 dBm **** | +| | 1805 MHz $< f \leq 1830$ MHz | 100 kHz | -71 dBm ** & * | +| | | 3.84 MHz | -60 dBm ** | +| | 1830 MHz $< f \leq 1880$ MHz | 100 kHz | -71 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1880 MHz $\leq f \leq 1920$ MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq 1915.7$ MHz | 300 kHz | -41 dBm **** | +| | 2010 MHz $\leq f \leq 2025$ MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2300 MHz $< f < 2400$ MHz | 3.84 MHz | -60 dBm | +| | 2496 MHz $\leq f \leq 2570$ MHz | 1 MHz | -50 dBm | +| | 2570 MHz $\leq f \leq 2640$ MHz | 3.84 MHz | -60 dBm | +| | 2640 MHz $< f \leq 2690$ MHz | 3.84 MHz | -60 dBm ** | +| | 3510 MHz $\leq f \leq 3590$ MHz | 3.84 MHz | -60 dBm ** | +| | 3300 MHz $\leq f \leq 4200$ MHz | 1 MHz | -50 dBm ** | +| | 4400 MHz $\leq f \leq 5000$ MHz | 1 MHz | -50 dBm ** | +| IX | 758 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 945 MHz $\leq f \leq 960$ MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq 1510.9$ MHz | 3.84 MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq 1879.9$ MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq 1915.7$ MHz | 300 kHz | -41 dBm | +| | 2010 MHz $\leq f \leq 2025$ MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq 2575$ MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq 2645$ MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq 3600$ MHz | 1 MHz | -50 dBm ** | +| X | 717 MHz $\leq f \leq 728$ MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq 746$ MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq 756$ MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq 768$ MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq 1559$ MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq 1995$ MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq 2020$ MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq 2360$ MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq 2570$ MHz | 1 MHz | -50 dBm | +| | 3510 MHz $\leq f \leq 3590$ MHz | 3.84 MHz | -60 dBm ** | +| | 3400 MHz $\leq f \leq 3800$ MHz | 1 MHz | -50 dBm ** | +| XI | 758 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 860 MHz $\leq f \leq 890$ MHz | 3.84 MHz | -60 dBm | +| | 945 MHz $\leq f \leq 960$ MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq 1510.9$ MHz | 3.84 MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq 1879.9$ MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq 1915.7$ MHz | 300 kHz | -41 dBm | +| | 2010 MHz $\leq f \leq 2025$ MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq 2575$ MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq 2645$ MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq 4200$ MHz | 1 MHz | -50 dBm | + +| | | | | +|------|-------------------------------------|----------|-------------| +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm | +| XII | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| XIII | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 763 MHz $\leq f \leq$ 775 MHz | 6.25 kHz | -35 dBm*** | +| | 793 MHz $\leq f \leq$ 805 MHz | 6.25 kHz | -35 dBm*** | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm** | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm** | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| XIV | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 769 MHz $\leq f \leq$ 775 MHz | 6.25 kHz | -35 dBm *** | +| | 799 MHz $\leq f \leq$ 805 MHz | 6.25 kHz | -35 dBm *** | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| XIX | 758 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 860 MHz $\leq f <$ 875 MHz | 1 MHz | -37 dBm | +| | 875 MHz $\leq f \leq$ 890 MHz | 3.84 MHz | -60 dBm | +| | 945 MHz $\leq f \leq$ 960 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | + +| | | | | +|------|-----------------------------------------------------|---------------------|----------------------| +| | $1884.5 \text{ MHz} \leq f \leq 1915.7 \text{ MHz}$ | 300 kHz | -41 dBm | +| | $2010 \text{ MHz} \leq f \leq 2025 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2545 \text{ MHz} \leq f \leq 2575 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2595 \text{ MHz} \leq f \leq 2645 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $3400 \text{ MHz} \leq f \leq 3600 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $3300 \text{ MHz} \leq f \leq 4200 \text{ MHz}$ | 1 MHz | -50 dBm** | +| | $4400 \text{ MHz} \leq f \leq 5000 \text{ MHz}$ | 1 MHz | -50 dBm | +| XX | $461 \text{ MHz} \leq f \leq 466 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $738 \text{ MHz} \leq f \leq 758 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $758 \text{ MHz} \leq f \leq 788 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $791 \text{ MHz} \leq f \leq 821 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $921 \text{ MHz} \leq f < 925 \text{ MHz}$ | 100 kHz | -60 dBm * | +| | $925 \text{ MHz} \leq f \leq 935 \text{ MHz}$ | 100 kHz
3.84 MHz | -67 dBm *
-60 dBm | +| | $935 \text{ MHz} < f \leq 960 \text{ MHz}$ | 100 kHz
3.84 MHz | -79 dBm *
-60 dBm | +| | $1427 \text{ MHz} < f \leq 1518 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $1452 \text{ MHz} < f \leq 1496 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1805 \text{ MHz} \leq f \leq 1880 \text{ MHz}$ | 100 kHz
3.84 MHz | -71 dBm *
-60 dBm | +| | $2010 \text{ MHz} \leq f \leq 2025 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2170 \text{ MHz} \leq f \leq 2200 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2300 \text{ MHz} \leq f \leq 2400 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2620 \text{ MHz} \leq f \leq 2690 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2570 \text{ MHz} \leq f \leq 2620 \text{ MHz}$ | 3.84 MHz | -60 dBm** | +| | $3510 \text{ MHz} \leq f \leq 3590 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $3300 \text{ MHz} \leq f \leq 4200 \text{ MHz}$ | 1 MHz | -50 dBm ** | +| XXI | $758 \text{ MHz} \leq f \leq 803 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $860 \text{ MHz} \leq f \leq 890 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $945 \text{ MHz} \leq f \leq 960 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1475.9 \text{ MHz} \leq f \leq 1510.9 \text{ MHz}$ | 1 MHz | -35 dBm | +| | $1839.9 \text{ MHz} \leq f \leq 1879.9 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1884.5 \text{ MHz} \leq f \leq 1915.7 \text{ MHz}$ | 300 kHz | -41 dBm | +| | $2010 \text{ MHz} \leq f \leq 2025 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2170 \text{ MHz} \leq f \leq 2200 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2545 \text{ MHz} \leq f \leq 2575 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2595 \text{ MHz} \leq f \leq 2645 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $3300 \text{ MHz} \leq f \leq 4200 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $4400 \text{ MHz} \leq f \leq 5000 \text{ MHz}$ | 1 MHz | -50 dBm | +| XXII | $461 \text{ MHz} \leq f \leq 466 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $738 \text{ MHz} \leq f \leq 758 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $758 \text{ MHz} \leq f \leq 791 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $791 \text{ MHz} \leq f \leq 821 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $852 \text{ MHz} \leq f \leq 859 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $859 \text{ MHz} \leq f \leq 894 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $921 \text{ MHz} \leq f < 925 \text{ MHz}$ | 100 kHz | -60 dBm * | +| | $925 \text{ MHz} \leq f \leq 935 \text{ MHz}$ | 100 kHz
3.84 MHz | -67 dBm *
-60 dBm | +| | $935 \text{ MHz} < f \leq 960 \text{ MHz}$ | 100 kHz
3.84 MHz | -79 dBm *
-60 dBm | +| | $1452 \text{ MHz} < f \leq 1496 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1805 \text{ MHz} \leq f \leq 1880 \text{ MHz}$ | 100 kHz
3.84 MHz | -71 dBm *
-60 dBm | +| | $1880 \text{ MHz} \leq f \leq 1920 \text{ MHz}$ | 3.84 MHz | -60 dBm | + +| | | | | +|------|-------------------------------------|----------|------------| +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 2570 MHz $\leq f \leq$ 2620 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3525 MHz | 1 MHz | -40 dBm | +| | 3525 MHz $\leq f \leq$ 3590 MHz | 1 MHz | -50 dBm | +| | 3600 MHz $\leq f \leq$ 3800 MHz | 3.84 MHz | -50 dBm | +| XXV | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm ** | +| XXVI | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 799 MHz | 1 MHz | -50 dBm | +| | 799 MHz $\leq f \leq$ 803 MHz | 1 MHz | -40 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 945 MHz $\leq f \leq$ 960 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 3.84 MHz | -60 dBm | +| | 1839.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm ** | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm** | + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note * | The transmitter additional spurious emission measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, up to five measurements with a level up to the applicable requirements defined in Table 6.12 are permitted for each UARFCN used in the measurement. | +| Note ** | The transmitter additional spurious emission measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, measurements with a level up to the applicable requirements defined in Table 6.12 are permitted for each UARFCN used in the measurement due to 2 nd , 3 rd and 4 th harmonic spurious emissions. Note *** This requirement is applicable also for frequencies, which are between 2.5 MHz and 12.5 MHz away from the UE transmit centre carrier frequency. | +| Note **** | This requirement is applicable only when UE transmission is allocated within 900MHz to 915MHz. | +| Note ***** | This requirement is applicable only when UE transmission is allocated within 1744.9 MHz to 1784.9 MHz. | + +#### 6.6.3.1.1 Additional requirement + +The UE shall meet the requirements in Table 6.13a for the applicable band. + +**Table 6.13a: Additional spurious emissions requirements** + +| Operating Band | Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-----------------------|---------------------| +| XXVI | $806 \text{ MHz} \leq f \leq 813.5 \text{ MHz}$ | 6.25 kHz | -42 dBm (NOTE 1) | +| | $806 \text{ MHz} \leq f \leq 816 \text{ MHz}$ | 6.25 kHz | -42 dBm (NOTE 2) | +| | $852 \text{ MHz} \leq f \leq 859 \text{ MHz}$ | 1 MHz | -32 dBm (NOTE 3) | +| | $851 \text{ MHz} \leq f \leq 859 \text{ MHz}$ | 6.25 kHz | -53 dBm (NOTE 4) | +| NOTE 1: Applicable for UE center frequencies $\geq 816.4 \text{ MHz}$ . For UE center frequencies $\leq 819.6 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +17 dBm. | | | | +| NOTE 2: Applicable for UE center frequencies $\geq 819.4 \text{ MHz}$ . For UE center frequencies $\leq 822 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +17 dBm. | | | | +| NOTE 3: Applicable for UE center frequencies $\leq 846.6 \text{ MHz}$ . For UE center frequencies $\geq 842.4 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +10 dBm. | | | | +| NOTE 4: Applicable for UE center frequencies $\leq 846.6 \text{ MHz}$ . For UE center frequencies $\geq 842.4 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +10 dBm. | | | | +| NOTE 5: For the 6.25kHz measurement bandwidth, the emissions measurement shall be sufficiently power averaged to ensure standard standard deviation $< 0.5 \text{ dB}$ . | | | | + +#### 6.6.3.1A Additional requirement for DC-HSUPA + +The requirements in Table 6.12A are only applicable for frequencies, which are greater than 20 MHz away from the centre of the assigned carrier frequencies when dual adjacent carriers are assigned on the uplink. + +**Table 6.12A: General spurious emissions requirements for DC-HSUPA** + +| Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | Note | +|--------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|--------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | 1 kHz | -36 dBm | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | 10 kHz | -36 dBm | | +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | 100 kHz | -36 dBm | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | 1 MHz | -30 dBm | | +| $12.75 \text{ GHz} \leq f < 5\text{th harmonic of the upper frequency edge of the UL operating band in GHz}$ | 1 MHz | -30 dBm | Note 1 | + +NOTE 1: Applies only for Band XXII. + +The requirements in Table 6.13A are only applicable for frequencies, which are greater than 25 MHz away from the centre of the assigned frequencies when dual adjacent carriers are assigned on the uplink. + +**Table 6.13A: Additional spurious emissions requirements for DC-HSUPA** + +| Operating Band | Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | +|----------------|-------------------------------------|-----------------------|---------------------| +| I | 460 MHz $\leq f \leq 467.5$ MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq 821$ MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f < 925$ MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq 935$ MHz | 100 kHz | -67 dBm * | +| | | 3.84MHz | -60 dBm | +| | 935 MHz $< f \leq 960$ MHz | 100 kHz | -79 dBm * | +| | | 3.84MHz | -60 dBm | +| | 1427 MHz $\leq f \leq 1518$ MHz | 1 MHz | -50 dBm | +| | 1452 MHz $\leq f \leq 1510.9$ MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq 1880$ MHz | 100 kHz | -71 dBm * | +| | | 3.84MHz | -60 dBm | +| | 1844.9 MHz $\leq f \leq 1879.9$ MHz | 3.84 MHz | -55 dBm | +| | 1884.5 MHz $< f < 1915.7$ MHz | 300 kHz | -41 dBm | +| | 2010 MHz $< f < 2025$ MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2300 MHz $< f < 2400$ MHz | 3.84 MHz | -60 dBm | +| | 2496 MHz $\leq f \leq 2570$ MHz | 1 MHz | -50 dBm | +| | 2570 MHz $\leq f \leq 2690$ MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq 3590$ MHz | 3.84 MHz | -60 dBm | +| | 3300 MHz $\leq f \leq 3800$ MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq 4200$ MHz | 1 MHz | -50 dBm** | +| | 4400 MHz $\leq f \leq 5000$ MHz | 1 MHz | -50 dBm | +| II | 617 MHz $\leq f \leq 652$ MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq 728$ MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq 746$ MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq 758$ MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq 768$ MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq 859$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq 1518$ MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq 1559$ MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq 1995$ MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq 2020$ MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq 2170$ MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq 2200$ MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq 2360$ MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq 2620$ MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq 2620$ MHz | 1 MHz | -50 dBm | +| III | 460 MHz $\leq f \leq 467.5$ MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq 803$ MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq 821$ MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq 869$ MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq 894$ MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f < 925$ MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq 935$ MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq 960$ MHz | 100 kHz | -79 dBm | +| | | 3.84 MHz | -60 dBm * | +| | 1427 MHz $\leq f \leq 1518$ MHz | 1 MHz | -50 dBm | +| | 1452 MHz $< f \leq 1496$ MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq 1880$ MHz | 3.84 MHz | -60 dBm | + +| | | | | +|----|-------------------------------------|----------|------------| +| | 1880 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2496 MHz $\leq f \leq$ 2570 MHz | 1 MHz | -50 dBm | +| | 2570 MHz $\leq f \leq$ 2620 MHz | 3.84 MHz | -60 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm ** | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm ** | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm | +| IV | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| V | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq$ 803 MHz | 3.84 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 859 MHz $\leq f \leq$ 869 MHz | 1 MHz | -27 dBm | +| | 869 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2620 MHz | 1 MHz | -50 dBm ** | +| | 2570 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm ** | +| | 3300 MHz $\leq f \leq$ 3400 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm** | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm** | +| VI | 860 MHz $\leq f <$ 875 MHz | 1 MHz | -37 dBm | +| | 875 MHz $\leq f \leq$ 890 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | + +| | | | | +|------|-------------------------------------|---------------------|------------------------------| +| | 1844.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 2010 MHz $< f <$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq$ 2575 MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq$ 2645 MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq$ 3600 MHz | 1 MHz | -50 dBm | +| VII | 462.5 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 738 MHz $\leq f \leq$ 758 MHz | 1 MHz | -50 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 791 MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq$ 869 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f <$ 925 MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz
3.84 MHz | -67 dBm *
-60 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz | -79 dBm * | +| | 1427 MHz $< f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $< f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 100 kHz | -71 dBm * | +| | 1900 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2010 MHz $< f <$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $< f <$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 2595 MHz $\leq f \leq$ 2620 MHz | 1 MHz | -37 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm | +| VIII | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 703 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -60 dBm | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz
3.84 MHz | -57 dBm *, ***
-50 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz
3.84 MHz | -79 dBm *
-60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $< f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $< f \leq$ 1830 MHz | 100 kHz
3.84 MHz | -71 dBm ** & *
-60 dBm ** | +| | 1830 MHz $< f \leq$ 1880 MHz | 100 kHz
3.84 MHz | -71 dBm *
-60 dBm | +| | 1880 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2570 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2570 MHz $\leq f \leq$ 2620 MHz | 3.84 MHz | -60 dBm | + +| | | | | +|-----|-------------------------------------|----------|------------| +| | 2620 MHz $\leq f \leq$ 2640 MHz | 3.84 MHz | -60 dBm | +| | 2640 MHz $< f \leq$ 2690 MHz | 3.84 MHz | -60 dBm ** | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm ** | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm ** | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm ** | +| IX | 758 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1844.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq$ 2575 MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq$ 2645 MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq$ 3600 MHz | 1 MHz | -50 dBm ** | +| X | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2570 MHz | 1 MHz | -50 dBm | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm ** | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm ** | +| XI | 758 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 860 MHz $\leq f \leq$ 890 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1844.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq$ 2575 MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq$ 2645 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm | +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm | +| XIX | 758 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 860 MHz $\leq f <$ 875 MHz | 1 MHz | -30 dBm | +| | 875 MHz $\leq f \leq$ 890 MHz | 3.84 MHz | -60 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1844.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2545 MHz $\leq f \leq$ 2575 MHz | 1 MHz | -50 dBm | +| | 2595 MHz $\leq f \leq$ 2645 MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq$ 3600 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm** | + +| | | | | +|------|---------------------------------|----------|-------------| +| | 4400 MHz $\leq f \leq$ 5000 MHz | 1 MHz | -50 dBm | +| XX | 738 MHz $\leq f \leq$ 758 MHz | 1 MHz | -50 dBm | +| | 758 MHz $\leq f \leq$ 788 MHz | 1 MHz | -50 dBm | +| | 811 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -50 dBm *** | +| | 791 MHz $\leq f \leq$ 811 MHz | 3.84 MHz | -60 dBm | +| | 921 MHz $\leq f <$ 925 MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1427 MHz $< f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1452 MHz $< f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 100 kHz | -71 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 2570 MHz $\leq f \leq$ 2620 MHz | 3.84 MHz | -60 dBm ** | +| | 3510 MHz $\leq f \leq$ 3590 MHz | 3.84 MHz | -60 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm ** | +| XXII | 738 MHz $\leq f \leq$ 758 MHz | 1 MHz | -50 dBm | +| | 758 MHz $\leq f \leq$ 791 MHz | 1 MHz | -50 dBm | +| | 791 MHz $\leq f \leq$ 821 MHz | 3.84 MHz | -60 dBm | +| | 852 MHz $\leq f \leq$ 869 MHz | 1 MHz | -50 dBm | +| | 921 MHz $\leq f <$ 925 MHz | 100 kHz | -60 dBm * | +| | 925 MHz $\leq f \leq$ 935 MHz | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 935 MHz $< f \leq$ 960 MHz | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1452 MHz $< f \leq$ 1496 MHz | 3.84 MHz | -60 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 100 kHz | -71 dBm * | +| | | 3.84 MHz | -60 dBm | +| | 1880 MHz $\leq f \leq$ 1920 MHz | 3.84 MHz | -60 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2620 MHz $\leq f \leq$ 2690 MHz | 3.84 MHz | -60 dBm | +| | 2570 MHz $\leq f \leq$ 2620 MHz | 3.84 MHz | -60 dBm | +| | 3510 MHz $\leq f \leq$ 3525 MHz | 1 MHz | -40 dBm | +| | 3525 MHz $\leq f \leq$ 3590 MHz | 1 MHz | -50 dBm | +| | 3600 MHz $\leq f \leq$ 3800 MHz | 3.84 MHz | -50 dBm | +| XXV | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 746 MHz | 3.84 MHz | -60 dBm | +| | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | +| | 758 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 803 MHz | 1 MHz | -50 dBm | +| | 852 MHz $\leq f \leq$ 859 MHz | 1 MHz | -50 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 3.84 MHz | -60 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | + +| | | | | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------------| +| | 2350 MHz $\leq f \leq$ 2360 MHz | 1 MHz | -50 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm | +| XXVI | 460 MHz $\leq f \leq$ 467.5 MHz | 1 MHz | -50 dBm | +| | 617 MHz $\leq f \leq$ 652 MHz | 1 MHz | -50 dBm | +| | 717 MHz $\leq f \leq$ 728 MHz | 1 MHz | -50 dBm | +| | 728 MHz $\leq f \leq$ 768 MHz | 3.84 MHz | -60 dBm | +| | 768 MHz $\leq f \leq$ 799 MHz | 1 MHz | -50 dBm | +| | 799 MHz $\leq f \leq$ 803 MHz | 1 MHz | -40 dBm | +| | 859 MHz $\leq f \leq$ 894 MHz | 3.84 MHz | -60 dBm | +| | 1427 MHz $\leq f \leq$ 1518 MHz | 1 MHz | -50 dBm | +| | 1475.9 MHz $\leq f \leq$ 1510.9 MHz | 3.84 MHz | -60 dBm | +| | 1525 MHz $\leq f \leq$ 1559 MHz | 1 MHz | -50 dBm | +| | 1805 MHz $\leq f \leq$ 1880 MHz | 3.84 MHz | -60 dBm | +| | 1844.9 MHz $\leq f \leq$ 1879.9 MHz | 3.84 MHz | -60 dBm | +| | 1884.5 MHz $\leq f \leq$ 1915.7 MHz | 300 kHz | -41 dBm | +| | 1930 MHz $\leq f \leq$ 1995 MHz | 3.84 MHz | -60 dBm | +| | 1995 MHz $\leq f \leq$ 2020 MHz | 1 MHz | -50 dBm | +| | 2010 MHz $\leq f \leq$ 2025 MHz | 3.84 MHz | -60 dBm | +| | 2110 MHz $\leq f \leq$ 2170 MHz | 3.84 MHz | -60 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2170 MHz $\leq f \leq$ 2200 MHz | 1 MHz | -50 dBm | +| | 2300 MHz $\leq f \leq$ 2400 MHz | 3.84 MHz | -60 dBm | +| | 2483.5 MHz $\leq f \leq$ 2495 MHz | 1 MHz | -50 dBm | +| | 2496 MHz $\leq f \leq$ 2690 MHz | 1 MHz | -50 dBm ** | +| | 3400 MHz $\leq f \leq$ 3800 MHz | 1 MHz | -50 dBm | +| | 3300 MHz $\leq f \leq$ 4200 MHz | 1 MHz | -50 dBm** | +| Note * | The measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, up to five measurements with a level up to the applicable requirements defined in Table 6.12 are permitted for each UARFCN used in the measurement | | | +| Note ** | The measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, measurements with a level up to the applicable requirements defined in Table 6.12 are permitted for each UARFCN used in the measurement due to 2 nd , 3 rd and 4 th harmonic spurious emissions | | | +| Note *** | This requirement is applicable also for frequencies, which are between 5 MHz and 25 MHz away from the UE centre carrier frequency. | | | + +#### 6.6.3.1A.1 Additional requirement for DC-HSUPA + +The UE shall meet the requirements in Table 6.13B for the applicable band. + +**Table 6.13B: Additional spurious emissions requirements** + +| Operating Band | Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-----------------------|---------------------| +| XXVI | $806 \text{ MHz} \leq f \leq 813.5 \text{ MHz}$ | 6.25 kHz | -42 dBm (NOTE 1) | +| | $806 \text{ MHz} \leq f \leq 816 \text{ MHz}$ | 6.25 kHz | -42 dBm (NOTE 2) | +| | $852 \text{ MHz} \leq f \leq 859 \text{ MHz}$ | 1 MHz | -32 dBm (NOTE 3) | +| | $851 \text{ MHz} \leq f \leq 859 \text{ MHz}$ | 6.25 kHz | -53 dBm (NOTE 4) | +| NOTE 1: Applicable for a UE center frequency of the two assigned channel frequencies $\geq 819 \text{ MHz}$ . For such UE center frequencies $\leq 826.6 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +17 dBm. | | | | +| NOTE 2: Applicable for UE center frequency of the two assigned channel frequencies $\geq 822 \text{ MHz}$ . For such UE center frequencies $\leq 829 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +17 dBm. | | | | +| NOTE 3: Applicable for UE center frequency of the two assigned channel frequencies $\leq 844 \text{ MHz}$ . For such UE center frequencies $\geq 831 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +10 dBm. | | | | +| NOTE 4: Applicable for UE center frequency of the two assigned channel frequencies $\leq 844 \text{ MHz}$ . For such UE center frequencies $\geq 831 \text{ MHz}$ the IE "Maximum allowed UL TX power" shall be indicated and set to +10 dBm. | | | | +| NOTE 5: For the 6.25kHz measurement bandwidth, the emissions measurement shall be sufficiently power averaged to ensure standard standard deviation $< 0.5 \text{ dB}$ . | | | | + +#### 6.6.3.1B Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the requirements specified in sub-clause 6.6.3.1 apply at each transmit antenna connector. + +#### 6.6.3.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the spectrum emission requirements specified in sub-clause 6.6.3.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the spectrum emission requirements in sub-clause 6.6.3.1 apply at the active transmit antenna connector. + +#### 6.6.3.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the spectrum emission requirements specified in sub-clause 6.6.3.1 apply at each transmit antenna connector. + +#### 6.6.3.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the spurious emission requirements in Table 6.13C and Table 6.13D apply for frequencies, which are greater than 12.5MHz away from the UE centre carrier frequency for each carrier. If for some frequency a spurious emission requirement of individual carrier overlaps with the spectrum emission mask or channel bandwidth of another carrier then it does not apply. + +**Table 6.13C: General spurious emissions requirements for DB-DC-HSUPA** + +| Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | Note | +|--------------------------------------------|-----------------------|---------------------|------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | 1 kHz | -36 dBm | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | 10 kHz | -36 dBm | | +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | 100 kHz | -36 dBm | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | 1 MHz | -30 dBm | | + +**Table 6.13D: Additional spurious emissions requirements for DB-DC-HSUPA** + +| Operating Band combination | Frequency Bandwidth | Measurement Bandwidth | Minimum requirement | +|--------------------------------------------------------------------|-----------------------------------------------------|-----------------------|---------------------| +| I-1-V-1
I-1-V-2
I-2-V-1
I-2-V-2 | $460 \text{ MHz} \leq f \leq 467.5 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $703 \text{ MHz} \leq f \leq 803 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $859 \text{ MHz} \leq f \leq 869 \text{ MHz}$ | 1 MHz | -27 dBm | +| | $869 \text{ MHz} \leq f \leq 894 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1427 \text{ MHz} \leq f \leq 1518 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2496 \text{ MHz} \leq f \leq 2570 \text{ MHz}$ | 1 MHz | -50 dBm** | +| | $3510 \text{ MHz} \leq f \leq 3590 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $3300 \text{ MHz} \leq f \leq 3800 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $3300 \text{ MHz} \leq f \leq 4200 \text{ MHz}$ | 1 MHz | -50 dBm** | +| I-1-VIII-1
I-2-VIII-1
I-2-VIII-2
I-1-VIII-2
I-1-VIII-3 | $4400 \text{ MHz} \leq f \leq 5000 \text{ MHz}$ | 1 MHz | -50 dBm** | +| | $460 \text{ MHz} \leq f \leq 467.5 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $703 \text{ MHz} \leq f \leq 803 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $791 \text{ MHz} \leq f \leq 821 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $859 \text{ MHz} \leq f \leq 894 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $860 \text{ MHz} \leq f \leq 890 \text{ MHz}$ | 1 MHz | -37 dBm *** | +| | $925 \text{ MHz} \leq f \leq 935 \text{ MHz}$ | 100 kHz | -67 dBm * | +| | | 3.84 MHz | -60 dBm | +| | $935 \text{ MHz} < f \leq 960 \text{ MHz}$ | 100 kHz | -79 dBm * | +| | | 3.84 MHz | -60 dBm | +| | $1427 \text{ MHz} \leq f \leq 1518 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $1452 \text{ MHz} \leq f \leq 1496 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $1475.9 \text{ MHz} \leq f \leq 1510.9 \text{ MHz}$ | 3.84 MHz | -60 dBm *** | +| | $1805 \text{ MHz} < f \leq 1830 \text{ MHz}$ | 100 kHz | -71 dBm ** & * | +| | | 3.84 MHz | -60 dBm ** | +| | $1830 \text{ MHz} < f \leq 1880 \text{ MHz}$ | 100 kHz | -71 dBm * | +| | | 3.84 MHz | -60 dBm | +| | $1884.5 \text{ MHz} \leq f \leq 1915.7 \text{ MHz}$ | 300 kHz | -41 dBm *** | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2496 \text{ MHz} \leq f \leq 2570 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2570 \text{ MHz} \leq f \leq 2640 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2640 \text{ MHz} < f \leq 2690 \text{ MHz}$ | 3.84 MHz | -60 dBm ** | +| | $3510 \text{ MHz} \leq f \leq 3590 \text{ MHz}$ | 3.84 MHz | -60 dBm ** | +| | $3300 \text{ MHz} \leq f \leq 4200 \text{ MHz}$ | 1 MHz | -50 dBm ** | +| | $4400 \text{ MHz} \leq f \leq 5000 \text{ MHz}$ | 1 MHz | -50 dBm ** | +| II-1-V-1
II-1-V-2 | $617 \text{ MHz} \leq f \leq 652 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $717 \text{ MHz} \leq f \leq 728 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $728 \text{ MHz} \leq f \leq 746 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $746 \text{ MHz} \leq f \leq 756 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $758 \text{ MHz} \leq f \leq 768 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $859 \text{ MHz} \leq f \leq 869 \text{ MHz}$ | 1 MHz | -27 dBm | +| | $869 \text{ MHz} \leq f \leq 894 \text{ MHz}$ | 3.84 MHz | -60 dBm | + +| | | | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-----------| +| | $1427 \text{ MHz} \leq f \leq 1518 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $1525 \text{ MHz} \leq f \leq 1559 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $1930 \text{ MHz} \leq f \leq 1995 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2110 \text{ MHz} \leq f \leq 2170 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $2180 \text{ MHz} \leq f \leq 2200 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2350 \text{ MHz} \leq f \leq 2360 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2483.5 \text{ MHz} \leq f \leq 2495 \text{ MHz}$ | 1 MHz | -50 dBm | +| | $2496 \text{ MHz} \leq f \leq 2690 \text{ MHz}$ | 1 MHz | -50 dBm** | +| | $3510 \text{ MHz} \leq f \leq 3590 \text{ MHz}$ | 3.84 MHz | -60 dBm | +| | $3400 \text{ MHz} \leq f \leq 3800 \text{ MHz}$ | 1 MHz | -50 dBm | +| Note *: | The measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, up to five measurements with a level up to the applicable requirements defined in Table 6.13C are permitted for each UARFCN used in the measurement | | | +| Note **: | The measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, measurements with a level up to the applicable requirements defined in Table 6.13C are permitted for each UARFCN used in the measurement due to 2nd, 3rd and 4th harmonic spurious emissions | | | +| Note ***: | This requirement is applicable only when transmission is made between 900MHz to 915MHz. | | | + +## 6.7 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. + +### 6.7.1 Minimum requirement + +User Equipment(s) transmitting in close vicinity of each other can produce intermodulation products, which can fall into the UE, or Node B receive band as an unwanted interfering signal. The UE intermodulation attenuation is defined by the ratio of the RRC filtered mean power of the wanted signal to the RRC filtered mean power of the intermodulation product when an interfering CW signal is added at a level below the wanted signal. + +The requirement of transmitting intermodulation for a carrier spacing of 5 MHz is prescribed in Table 6.14. + +**Table 6.14: Transmit Intermodulation** + +| | | | | +|------------------------------|--------------------------------------|--------|--------| +| | Interference Signal Frequency Offset | 5MHz | 10MHz | +| Interference CW Signal Level | -40dBc | | | +| Intermodulation Product | | -31dBc | -41dBc | + +### 6.7.1A Additional requirement for DC-HSUPA + +The UE intermodulation attenuation is defined by the ratio of the sum of the RRC filtered mean powers of the wanted signal on the assigned carriers to the sum of the RRC filtered mean powers of the intermodulation product on two adjacent carriers when an interfering CW signal is added at a level below the wanted signal. + +The requirement of transmitting intermodulation for a carrier spacing of 5 MHz is prescribed in Table 6.14A. + +**Table 6.14A: Transmit Intermodulation requirement for DC-HSUPA** + +| | | | +|--------------------------------------|--------|--------| +| Interference Signal Frequency Offset | 10MHz | 20MHz | +| Interference CW Signal Level | -40dBc | | +| Intermodulation Product | -31dBc | -41dBc | + +### 6.7.1B Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the requirements specified in sub-clause 6.7.1 apply at each transmit antenna connector. + +### 6.7.1C Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the requirements specified in sub-clause 6.7.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the requirements specified in sub-clause 6.7.1 apply at the active transmit antenna connector. + +### 6.7.1D Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the requirements specified in sub-clause 6.7.1 apply at each transmit antenna connector. + +### 6.7.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the requirements specified in sub-clause 6.7.1 apply per carrier. + +## 6.8 Transmit modulation + +Transmit modulation defines the modulation quality for expected in-channel RF transmissions from the UE. The requirements apply to all transmissions including the PRACH pre-amble and message parts and all other expected transmissions. In cases where the mean power of the RF signal is allowed to change versus time e.g. PRACH, DPCH in compressed mode, change of TFC, inner loop power control and for HSDPA transmissions with non-constant HS-DPCCH code power, the EVM, Peak Code Domain Error and E-DCH Code Domain Error requirements do not apply during the 25 us period before and after the nominal time when the mean power is expected to change. + +### 6.8.1 Transmit pulse shape filter + +The transmit pulse shaping filter is a root-raised cosine (RRC) with roll-off $\alpha = 0.22$ in the frequency domain. The impulse response of the chip impulse filter $RC_0(t)$ is: + +$$RC_0(t) = \frac{\sin\left(\pi \frac{t}{T_c} (1 - \alpha)\right) + 4\alpha \frac{t}{T_c} \cos\left(\pi \frac{t}{T_c} (1 + \alpha)\right)}{\pi \frac{t}{T_c} \left(1 - \left(4\alpha \frac{t}{T_c}\right)^2\right)}$$ + +Where the roll-off factor $\alpha = 0.22$ and the chip duration is + +$$T = \frac{1}{chiprate} \approx 0.26042 \mu s$$ + +### 6.8.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the transmit pulse shape filter requirements specified in sub-clause 6.8.1 apply at each transmit antenna connector. + +### 6.8.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the transmit pulse shape filter requirements specified in sub-clause 6.8.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the transmit pulse shape filter requirements specified in sub-clause 6.8.1 apply at the active transmit antenna connector. + +### 6.8.1C Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the transmit pulse shape filter requirements specified in sub-clause 6.8.1 apply at each transmit antenna connector. + +### 6.8.1D Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the transmit pulse shape filter requirements specified in sub-clause 6.8.1 apply per carrier. + +## 6.8.2 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. Both waveforms pass through a matched Root Raised Cosine filter with bandwidth 3,84 MHz and roll-off $\alpha=0,22$ . Both waveforms are then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. The measurement interval is one timeslot except when the mean power between slots is expected to change whereupon the measurement interval is reduced by 25 $\mu s$ at each end of the slot. For the PRACH preamble the measurement interval is 4096 chips less 25 $\mu s$ at each end of the burst (3904 chips). + +When the UE uses 16QAM modulation on any of the uplink code channels in a carrier, the error minimization step also includes selecting an IQ origin offset besides selecting the frequency, absolute phase, absolute amplitude and chip clock timing to minimise the error vector. The IQ origin offset shall be removed from the evaluated signal before calculating the EVM; however, the removed relative IQ origin offset power (relative carrier leakage power) also has to satisfy the applicable requirement. + +For signals containing more than one spreading code in a carrier where the slot alignment of the codes is not the same and the code power is varying, the period over which the nominal mean power in that carrier remains constant can be less than one timeslot. For such time-varying signals it is not possible to define EVM across one timeslot since this interval contains an expected change in mean power, and the exact timing and trajectory of the power change is not defined. For these signals, the EVM minimum requirements apply only for intervals of at least one half timeslot (less any 25 $\mu s$ transient periods) during which the nominal code power of each individual code is constant. + +NOTE: The reason for setting a lower limit for the EVM measurement interval is that for any given impaired signal, the EVM would be expected to improve for measurement intervals less than one timeslot while the frequency error would be expected to degrade. + +### 6.8.2.1 Minimum requirement + +When 16QAM modulation is not used on any of the uplink code channels, the Error Vector Magnitude shall not exceed 17.5 % for the parameters specified in Table 6.15. + +When 16QAM modulation is used on any of the uplink code channels, the modulation accuracy requirement shall meet one or both of the following requirements: + +1. The Error Vector Magnitude does not exceed 14 % for the parameters specified in Table 6.15. +2. The Relative Code Domain Error requirements specified in 6.8.3a are met. + +The requirements are applicable for all values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8]. + +**Table 6.15: Parameters for Error Vector Magnitude/Peak Code Domain Error** + +| Parameter | | Unit | Level | | +|--------------------------------------------------------------------------|----------|-------|----------------------------|--| +| UE Output Power, no 16QAM | | dBm | $\geq -20$ | | +| UE Output Power, 16QAM | | dBm | $\geq -30$ | | +| Operating conditions | | | Normal conditions | | +| Power control step size | | dB | 1 | | +| Measurement period (Note 1) | PRACH | Chips | 3904 | | +| | Any DPCH | | From 1280 to 2560 (Note 2) | | +| Note 1: Less any 25 $\mu$ s transient periods | | | | | +| Note 2: The longest period over which the nominal power remains constant | | | | | + +When 16QAM modulation is used on any of the uplink code channels, the relative carrier leakage power (IQ origin offset power) shall not exceed the values specified in Table 6.15a + +**Table 6.15a: Relative Carrier Leakage Power** + +| UE Transmitted Mean Power | Relative Carrier Leakage Power (dB) | +|---------------------------|-------------------------------------| +| $P \geq -30$ dBm | $< -17$ | + +### 6.8.2.1A Additional requirement for DC-HSUPA + +When 16QAM modulation is not used on any of the uplink code channels in a carrier, the Error Vector Magnitude in that carrier shall not exceed 17.5 % for the parameters specified in Table 6.15AA. + +When 16QAM modulation is used on any of the uplink code channels in a carrier, the modulation accuracy requirement shall meet one or both of the following requirements: + +1. The Error Vector Magnitude does not exceed 14 % for the parameters specified in Table 6.15AA. +2. The Relative Code Domain Error requirements specified in 6.8.3a are met. + +The requirements are applicable for all values of $\beta_c$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8], when the total power in each of the assigned carriers is equal to each other. The reference measurement channels for the requirements in subclause 6.8.2.1A are provided in subclause A.2.6 and A.2.7. + +**Table 6.15AA: Parameters for Error Vector Magnitude for DC-HSUPA** + +| Parameter | Unit | Level | +|---------------------------|------|-------------------| +| UE Output Power, no 16QAM | dBm | $\geq -20$ | +| UE Output Power, 16QAM | dBm | $\geq -30$ | +| Operating conditions | | Normal conditions | +| Power control step size | dB | 1 | + +#### 6.8.2.1B Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the EVM requirements specified in sub-clause 6.8.2.1 except the requirement with PRACH apply at each transmit antenna connector. + +#### 6.8.2.1C Additional requirement for UL CLTD + +When 16QAM modulation is not used on any of the uplink code channels, the Error Vector Magnitude shall not exceed 17.5 % for the parameters specified in Table 6.15AB at each transmit antenna connector. + +When 16QAM modulation is used on any of the uplink code channels, the modulation accuracy requirement shall meet one or both of the following requirements: + +1. The Error Vector Magnitude does not exceed 14 % for the parameters specified in Table 6.15AB at each transmit antenna connector. +2. The Relative Code Domain Error requirements specified in 6.8.3a are met at each transmit antenna connector. + +The requirements are applicable for all values of $\beta_c$ , $\beta_{sc}$ , $\beta_d$ , $\beta_{hs}$ , $\beta_{ec}$ and $\beta_{ed}$ as specified in [8]. + +**Table 6.15AB: Parameters for Error Vector Magnitude for UL CLTD** + +| Parameter | Unit | Level | +|--------------------------------------------------------------------------|----------|----------------------------------| +| UE Output Power, no 16QAM | dBm | $\geq -20$ | +| UE Output Power, 16QAM | dBm | $\geq -30$ | +| Operating conditions | | Normal conditions | +| Power control step size | dB | 1 | +| Measurement period (Note 1) | Any DPCH | Chips From 1280 to 2560 (Note 2) | +| Note 1: Less any 25 $\mu$ s transient periods | | | +| Note 2: The longest period over which the nominal power remains constant | | | + +When 16QAM modulation is used on any of the uplink code channels, the relative carrier leakage power (IQ origin offset power) shall not exceed the values specified in Table 6.15a at each transmit antenna connector + +#### 6.8.2.1D Additional requirement for UL MIMO + +When 16QAM modulation is not used on any of the uplink code channels, the Error Vector Magnitude shall not exceed 17.5 % for the parameters specified in Table 6.15AC at each transmit antenna connector. + +When 16QAM modulation is used on any of the uplink code channels, the modulation accuracy requirement shall meet one or both of the following requirements: + +1. The Error Vector Magnitude does not exceed 14 % for the parameters specified in Table 6.15AC. +2. The Relative Code Domain Error requirements specified in 6.8.3a are met. + +The requirements are applicable for all values of $\beta_c$ , $\beta_{sc}$ , $\beta_{hs}$ , $\beta_{ec}$ , $\beta_{sec}$ , $\beta_{ed}$ and $\beta_{sed}$ as specified in [8]. + +**Table 6.15AC: Parameters for Error Vector Magnitude for UL MIMO** + +| Parameter | Unit | Level | +|---------------------------|------|-------------------| +| UE Output Power, no 16QAM | dBm | $\geq -20$ | +| UE Output Power, 16QAM | dBm | $\geq -30$ | +| Operating conditions | | Normal conditions | +| Power control step size | dB | 1 | + +When 16QAM modulation is used on any of the uplink code channels, the relative carrier leakage power (IQ origin offset power) shall not exceed the values specified in Table 6.15a at each transmit antenna connector. + +#### 6.8.2.1E Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the EVM requirements specified in sub-clause 6.8.2.1 apply at each carrier. + +### 6.8.3 Peak code domain error + +The Peak Code Domain Error is computed by projecting power of the error vector (as defined in 6.8.2) onto the code domain at a specific spreading factor. The Code Domain Error for every code in the domain is defined as the ratio of the mean power of the projection onto that code, to the mean power of the composite reference waveform. This ratio is expressed in dB. The Peak Code Domain Error is defined as the maximum value for the Code Domain Error for all codes. The measurement interval is one timeslot except when the mean power between slots is expected to change whereupon the measurement interval is reduced by 25 $\mu\text{s}$ at each end of the slot. + +The requirement for peak code domain error is only applicable for multi-code DPDCH transmission and therefore does not apply for the PRACH preamble and message parts. + +#### 6.8.3.1 Minimum requirement + +The peak code domain error shall not exceed -15 dB at spreading factor 4 for the parameters specified in Table 6.15. The requirements are defined using the UL reference measurement channel specified in subclause A.2.5. + +#### 6.8.3.1A Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the Peak code domain error requirements specified in sub-clause 6.8.3.1 apply at each transmit antenna connector. + +#### 6.8.3.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the peak code domain error shall not exceed -15 dB at spreading factor 4 for the parameters specified in Table 6.15. The requirements are defined using the UL reference measurement channel specified in subclause A.2.5A. + +For UE configured in UL CLTD activation state 2 or activation state 3, the Peak code domain error requirements specified in sub-clause 6.8.3.1 apply at the active transmit antenna connector. + +#### 6.8.3.1C Additional requirement for DB-DC-HSUPA operating simultaneously with CS + +For UE supporting DB-DC-HSUPA operating simultaneously with CS, the peak code domain error requirements specified in sub-clause 6.8.3.1 apply for the primary carrier. + +## 6.8.3a Relative code domain error + +### 6.8.3a.1 Relative Code Domain Error + +The Relative Code Domain Error is computed by projecting the error vector (as defined in 6.8.2) onto the code domain. Only the code channels with non-zero betas in the composite reference waveform are considered for this requirement. The Relative Code Domain Error for every non-zero beta code in the domain is defined as the ratio of the mean power of the projection onto that non-zero beta code, to the mean power of the non-zero beta code in the composite reference waveform. This ratio is expressed in dB. The measurement interval is one timeslot except when the mean power between slots is expected to change whereupon the measurement interval is reduced by 25 $\mu\text{s}$ at each end of the slot. + +In the mode of DC-HSUPA, the requirement and corresponding measurements apply to each individual carrier when the total power in each of the assigned carriers is equal to each other. + +The Relative Code Domain Error is affected by both the spreading factor and beta value of the various code channels in the domain. The Effective Code Domain Power (ECDP) is defined to capture both considerations into one parameter. It uses the Nominal CDP ratio (as defined in 6.2.3), and is defined as follows for each used code, $k$ , in the domain: + +$$\text{ECDP}_k = (\text{Nominal CDP ratio})_k + 10 \cdot \log_{10}(\text{SF}_k/256)$$ + +When 16QAM is not used on any of the UL code channels in a carrier, the requirements for Relative Code Domain Error are not applicable when either or both the following channel combinations occur: + +- when the ECDP of any code channel is $< -30\text{dB}$ +- when the nominal code domain power of any code channel is $< -20\text{ dB}$ + +When 16QAM is used on any of the UL code channels in a carrier, the requirements for Relative Code Domain Error are not applicable when either or both the following channel combinations occur: + +- when the ECDP of any code channel is $< -30\text{dB}$ +- when the nominal code domain power of any code channel is $< -30\text{ dB}$ + +The requirement for Relative Code Domain Error also does not apply for the PRACH preamble and message parts. + +#### 6.8.3a.1.1 Minimum requirement + +When 16QAM is not used on any of the UL code channels, the Relative Code Domain Error shall meet the requirements in Table 6.15B for the parameters specified in Table 6.15 + +**Table 6.15B: Relative Code Domain Error minimum requirement** + +| ECDP dB | Relative Code Domain Error dB | +|---------------------------------|-------------------------------| +| $-21 < \text{ECDP}$ | $\leq -16$ | +| $-30 \leq \text{ECDP} \leq -21$ | $\leq -37 - \text{ECDP}$ | +| $\text{ECDP} < -30$ | No requirement | + +When 16QAM is used on any of the UL code channels, the Relative Code Domain Error of the codes not using 16QAM shall meet the requirements in Table 6.15C for the parameters specified in Table 6.15. + +**Table 6.15C: Relative Code Domain Error minimum requirement** + +| ECDP dB | Relative Code Domain Error dB | +|---------------------------------|--------------------------------------| +| $-22 < \text{ECDP}$ | $\leq -18$ | +| $-30 \leq \text{ECDP} \leq -22$ | $\leq -40 - \text{ECDP}$ | +| $\text{ECDP} < -30$ | No requirement | + +When 16QAM is used on any of the UL code channels, the Nominal CDP Ratio-weighted average of the Relative Code Domain Errors measured individually on each of the codes using 16QAM shall meet the requirements in Table 6.15D for the parameters specified in Table 6.15. The Nominal CDP Ratio-weighted average of the Relative Code Domain Errors means the sum over all code k that uses 16QAM. + +For the purposes of evaluating the requirements specified in Table 6.15D, the ECDP value is determined as the minimum of the individual ECDP values corresponding to the codes using 16QAM. + +**Table 6.15D: Relative Code Domain Error minimum requirement** + +| ECDP dB | Average Relative Code Domain Error dB | +|-----------------------------------|----------------------------------------------| +| $-25.5 < \text{ECDP}$ | $\leq -18$ | +| $-30 \leq \text{ECDP} \leq -25.5$ | $\leq -43.5 - \text{ECDP}$ | +| $\text{ECDP} < -30$ | No requirement | + +#### 6.8.3a.1.1a Additional requirement for DC-HSUPA + +When 16QAM is not used on any of the UL code channels in a carrier, the Relative Code Domain Error in that carrier shall meet the requirements in Table 6.15B for the parameters specified in Table 6.15AA. + +When 16QAM is used on any of the UL code channels in a carrier, the Relative Code Domain Error of the codes not using 16QAM in that carrier shall meet the requirements in Table 6.15C for the parameters specified in Table 6.15AA. + +When 16QAM is used on any of the UL code channels in a carrier, the Nominal CDP Ratio-weighted average of the Relative Code Domain Errors measured individually on each of the codes using 16QAM in that carrier shall meet the requirements in Table 6.15D for the parameters specified in Table 6.15AA. + +For the purposes of evaluating the requirements specified in Table 6.15D, the ECDP value is determined as the minimum of the individual ECDP values corresponding to the codes using 16QAM. + +The reference measurement channels for the requirements in subclause 6.8.3a.1.1a are provided in subclause A.2.6 and A.2.7. + +#### 6.8.3a.1.1b Additional requirement for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the relative code domain error requirements specified in sub-clause 6.8.3a.1.1 apply at each transmit antenna connector. + +#### 6.8.3a.1.1c Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the relative code domain error requirements specified in sub-clause 6.8.3a.1.1 apply at each transmit antenna connector. + +For UE configured in UL CLTD activation state 2 or activation state 3, the relative code domain error requirements specified in sub-clause 6.8.3a.1.1 apply at the active transmit antenna connector. + +#### 6.8.3a.1.1d Additional requirement for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the relative code domain error requirements specified in sub-clause 6.8.3a.1.1 apply at each transmit antenna connector. + +#### 6.8.3a.1.1e Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, the relative code domain error requirements specified in sub-clause 6.8.3a.1.1a apply. + +### 6.8.3b In-band emission for DC-HSUPA + +The in-band emission is measured as the ratio of the UE output power in one carrier in dual cells to the UE output power in the other carrier, where the power in the former carrier shall be set to the minimum output power and the power in the latter carrier to the maximum output power. The reference measurement channel for the requirements in subclause 6.8.3b.1 is provided in subclause A.2.6 with an adjusted power imbalance to set the power in one carrier to the minimum output power and the power in the other carrier to the maximum output power. The basic in-band emission measurement interval is defined over one slot in the time domain. + +#### 6.8.3b.1 Minimum requirement for DC-HSUPA + +The in-band emission shall not exceed the value specified in Table 6.15E. + +**Table 6.15E: In-band emission minimum requirements for DC-HSUPA** + +| Parameter Description | Unit | Limit | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| In-band emission | dBc | -24 | +| Note : | The measurement bandwidth is 3.84 MHz centered on each carrier frequency and the limit is expressed as a ratio of RRC filtered mean power in one carrier, transmitting at minimum output power, to the RRC filtered mean power in the other carrier, transmitting at maximum output power. | | + +### 6.8.4 Phase discontinuity for uplink DPCH + +Phase discontinuity is the change in phase between any two adjacent timeslots. The EVM for each timeslot (excluding the transient periods of 25 $\mu$ s on either side of the nominal timeslot boundaries), shall be measured according to subclause 6.8.2. The frequency, absolute phase, absolute amplitude and chip clock timing used to minimise the error vector are chosen independently for each timeslot. The phase discontinuity result is defined as the difference between the absolute phase used to calculate EVM for the preceding timeslot, and the absolute phase used to calculate EVM for the succeeding timeslot. + +#### 6.8.4.1 Minimum requirement + +The rate of occurrence of any phase discontinuity on an uplink DPCH for the parameters specified in table 6.16 shall not exceed the values specified in table 6.17. Phase shifts that are caused by changes of the UL transport format combination (TFC), compressed mode and HS-DPCCH are not included. When calculating the phase discontinuity, the requirements for frequency error and EVM in subclauses 6.3 and 6.8.2 for each timeslot shall be met. + +**Table 6.16: Parameters for Phase discontinuity** + +| Parameter | Unit | Level | +|-------------------------|------|-------| +| Power control step size | dB | 1 | + +**Table 6.17: Phase discontinuity minimum requirement** + +| Phase discontinuity $\Delta\theta$ in degrees | Maximum allowed rate of occurrence in Hz | +|-----------------------------------------------|------------------------------------------| +| $\Delta\theta \leq 30$ | 1500 | +| $30 < \Delta\theta \leq 60$ | 300 | +| $\Delta\theta > 60$ | 0 | + +#### 6.8.4.1A Additional requirement for UL OLTD + +For UE with two transmit antenna connectors in UL OLTD operation, the rate of occurrence of any phase discontinuity on an uplink DPCH for the parameters specified in table 6.16 shall not exceed the values specified in table 6.17 for each transmit antenna connector. In addition, the relative phase applied to the two transmit paths shall be fixed during the phase discontinuity test. Phase shifts that are caused by changes of the UL transport format combination (TFC), compressed mode and HS-DPCCH are not included. When calculating the phase discontinuity, the requirements for frequency error and EVM in subclauses 6.3B and 6.8.2 for each timeslot shall be met. + +#### 6.8.4.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the rate of occurrence of any phase discontinuity on an uplink DPCH for the parameters specified in table 6.16 shall not exceed the values specified in table 6.17 for each transmit antenna connector. In addition, TPI applied to the two transmit paths shall be fixed during the phase discontinuity test. Phase shifts that are caused by changes of the UL transport format combination (TFC), compressed mode and HS-DPCCH are not included. When calculating the phase discontinuity, the requirements for frequency error and EVM in subclauses 6.3C and 6.8.2 for each timeslot shall be met. + +For UE configured in UL CLTD activation state 2 or activation state 3, the phase discontinuity for Uplink DPCH specified in sub-clause 6.8.4.1 applies at the active transmit antenna connector. + +#### 6.8.4.1C Additional requirement for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA, the rate of occurrence of any phase discontinuity on an uplink DPCH for the parameters specified in table 6.16 shall not exceed the values specified in table 6.17 for the primary carrier. + +### 6.8.5 Phase discontinuity for HS-DPCCH + +Phase discontinuity for HS-DPCCH is the change in phase due to the transmission of the HS-DPCCH. In the case where the HS-DPCCH timeslot is offset from the DPCH timeslot, the period of evaluation of the phase discontinuity shall be the DPCH timeslot that contains the HS-DPCCH slot boundary. The phase discontinuity for HS-DPCCH result is defined as the difference between the absolute phase used to calculate the EVM for that part of the DPCH timeslot prior to the HS-DPCCH slot boundary, and the absolute phase used to calculate the EVM for remaining part of the DPCH timeslot following the HS-DPCCH slot boundary. In all cases the subslot EVM is measured excluding the transient periods of 25 $\mu\text{s}$ . + +Since subslot EVM is only defined for intervals of at least one half timeslot, the phase discontinuity for HS-DPCCH is only defined for non-aligned timeslots when the offset is 0.5 slots. + +#### 6.8.5.1 Minimum requirement + +The phase discontinuity for HS-DPCCH shall not exceed the value specified in table 6.18 90% of the time. When calculating the phase discontinuity, the requirements for frequency error and EVM in sub clauses 6.3 and 6.8.2, respectively shall be met. + +**Table 6.18: Phase discontinuity minimum requirement for HS-DPCCH at HS-DPCCH slot boundary** + +| | | +|------------------------------------------------------------|------------------------| +| Phase discontinuity for HS-DPCCH $\Delta\theta$ in degrees | $\Delta\theta \leq 30$ | +|------------------------------------------------------------|------------------------| + +#### 6.8.5.1A Additional requirement for UL OLTD + +For UE with two transmit antenna connectors in UL OLTD operation, the phase discontinuity for HS-DPCCH shall not exceed the value specified in table 6.18 90% of the time for each transmit antenna connector. In addition, the relative phase applied to the two transmit paths shall be fixed during the phase discontinuity test. When calculating the phase discontinuity, the requirements for frequency error and EVM in sub clauses 6.3B and 6.8.2, respectively shall be met. + +#### 6.8.5.1B Additional requirement for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the phase discontinuity for HS-DPCCH shall not exceed the value specified in table 6.18 90% of the time for each transmit antenna connector. In addition, TPI applied to the two transmit paths shall be fixed during the phase discontinuity test. When calculating the phase discontinuity, the requirements for frequency error and EVM in sub clauses 6.3C and 6.8.2, respectively shall be met. + +For UE configured in UL CLTD activation state 2 or activation state 3, the phase discontinuity for HS-DPCCH specified in sub-clause 6.8.5.1 applies at the active transmit antenna connector. + +### 6.8.6 Phase discontinuity for E-DCH + +Phase discontinuity for E-DCH is the change in phase due to the transmission of DPCCH, HS-DPCCH, E-DPCCH and E-DCH with the combined transmit power profile as defined in Table 6.19. The phase discontinuity for E-DCH result is defined as the difference between the absolute phase used to calculate the EVM for the preceding timeslot, and the absolute phase used to calculate the EVM for the succeeding timeslot. + +**Table 6.19 Transmit power profile for E-DCH phase discontinuity test** + +| Slot Number | | | | +|-------------|-------|-------|-------| +| 1 | 19/15 | 21/15 | DTX | +| 2 | 19/15 | 21/15 | 24/15 | +| 3 | 19/15 | 21/15 | 24/15 | +| 4 | 19/15 | 42/15 | 30/15 | +| 5 | 19/15 | 42/15 | DTX | +| 6 | 19/15 | 42/15 | DTX | +| 7 | 19/15 | 60/15 | DTX | +| 8 | 19/15 | 60/15 | 24/15 | +| 9 | 19/15 | 60/15 | 24/15 | +| 10 | 19/15 | 30/15 | DTX | +| 11 | 19/15 | 30/15 | DTX | +| 12 | 19/15 | 30/15 | DTX | +| 13 | 19/15 | 21/15 | 30/15 | +| 14 | 19/15 | 21/15 | 24/15 | +| 15 | 19/15 | 21/15 | 24/15 | +| 16 | 19/15 | 30/15 | DTX | +| 17 | 19/15 | 30/15 | DTX | +| 18 | 19/15 | 30/15 | DTX | +| 19 | 19/15 | 21/15 | | +| 20 | 19/15 | 21/15 | | +| 21 | 19/15 | 21/15 | | +| 22 | 19/15 | 42/15 | | +| 23 | 19/15 | 42/15 | | +| 24 | 19/15 | 42/15 | | + +Note 1: E-DCH power profile has a period of 24 slots and will be repeated every 24 slots. +Note 2: HS-DPCCH power profile has a period of 18 slots and will be repeated every 18 slots. +Note 3: The total combined power profile has a period of 72 slots and will be repeated every 72 slots. +Note 4: Power control will be turned off so that DPCCH power is kept constant for a specific run of the test. + +### 6.8.6.1 Minimum requirement + +When transmitting according to the power profile specified in Table 6.19, the phase discontinuity for E-DCH shall not exceed the value specified in table 6.20 for the specified amount of time in table 6.20. The requirement applies for the range of DPCCH powers according to table 6.20. When calculating the phase discontinuity, the requirements for frequency error and EVM in sub clauses 6.3 and 6.8.2, respectively shall be met. + +**Table 6.20: Phase discontinuity minimum requirement for E-DCH** + +| Phase discontinuity $\Delta\theta$ in degrees | Minimum allowed time in percentage | DPCCH power in dBm | +|-----------------------------------------------|------------------------------------|----------------------------------------------------| +| $\Delta\theta \leq 15$ | 80 | $-15 \leq \text{DPCCH power} \leq (P_{\max} - 20)$ | +| $\Delta\theta \leq 35$ | 90 | | +| $\Delta\theta \leq 45$ | 100 | | + +#### 6.8.6.1A Additional requirement for UL OLTD + +For UE with two transmit antenna connectors in UL OLTD operation, when transmitting according to the power profile specified in Table 6.19, the phase discontinuity for E-DCH shall not exceed the value specified in table 6.20 for the specified amount of time in table 6.20 for each transmit antenna connector. The requirement applies for the range of DPCCH powers according to table 6.20. In addition, the relative phase applied to the two transmit paths shall be fixed during the phase discontinuity test. When calculating the phase discontinuity, the requirements for frequency error and EVM in sub clauses 6.3B and 6.8.2, respectively shall be met. + +#### 6.8.6.1B Additional requirement for UL CLTD + +For UE configured in UL CLTD activation state 2 or activation state 3, the phase discontinuity for E-DCH specified in sub-clause 6.8.6.1 applies at the active transmit antenna connector. + +#### 6.8.6.1C Additional requirement for DB-DC-HSUPA + +For UE configured in DB-DC-HSUPA, the phase discontinuity for E-DCH specified in sub-clause 6.8.6.1 applies at the primary UL carrier. + +### 6.8.7 Time alignment error for DC-HSUPA + +In DC-HSUPA transmission, signals are transmitted for dual cells. These signals shall be aligned. The time alignment error in DC-HSUPA transmission is specified as the delay between the signals from primary and secondary uplink frequencies at the antenna port. + +#### 6.8.7.1 Minimum requirement + +The time alignment error shall not exceed $\frac{3}{4} T_c$ . + +### 6.8.7A Time alignment error for UL OLTD + +For UE with two active transmit antenna connectors in UL OLTD operation, the signals transmitted in the two antenna connectors shall be aligned. The time alignment error in UL OLTD operation transmission is specified as the delay between the signals from two antenna connectors. + +#### 6.8.7A.1 Minimum requirement + +The time alignment error shall not exceed $0.4 T_c$ . + +### 6.8.7B Time alignment error for UL CLTD + +For UE with two active transmit antenna connectors in UL CLTD activation state 1, the signals transmitted in the two antenna connectors shall be aligned. The time alignment error in UL CLTD activation state 1 transmission is specified as the delay between the signals from two antenna connectors. + +#### 6.8.7B.1 Minimum requirement + +The time alignment error shall not exceed $0.4 T_c$ . + +## 6.8.7C Time alignment error for UL MIMO + +For UE with two active transmit antenna connectors in UL MIMO operation, the signals transmitted in the two antenna connectors shall be aligned. The time alignment error in UL MIMO transmission is specified as the delay between the signals from two antenna connectors. + +### 6.8.7C.1 Minimum requirement + +The time alignment error shall not exceed $0.4T_c$ . + +## 6.8.7D Time alignment error for DB-DC-HSUPA + +For UE supporting DB-DC-HSUPA operation, signals are transmitted for dual cells. These signals shall be aligned. The time alignment error in DB-DC-HSUPA transmission is specified as the delay between the signals from primary and secondary uplink frequencies. + +### 6.8.7D.1 Minimum requirement + +The time alignment error shall not exceed $\frac{3}{4} T_c$ . + +--- + +# 7 Receiver characteristics + +## 7.1 General + +Unless otherwise stated the receiver characteristics are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna 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 the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. + +The UE antenna performance has a significant impact on system performance, and minimum requirements on the antenna efficiency are therefore intended to be included in future versions of the present document. It is recognised that different requirements and test methods are likely to be required for the different types of UE. + +UEs supporting DC-HSDPA, regardless of MIMO configuration, shall support both minimum requirements, as well as additional requirements for DC-HSDPA. + +UEs supporting DB-DC-HSDPA shall support both minimum requirements as well as additional requirements for DB-DC-HSDPA. + +UEs supporting DC-HSUPA shall support both minimum requirements, as well as additional requirements for DC-HSUPA. + +UEs supporting single band 4C-HSDPA shall support minimum requirements, additional requirements for DC-HSDPA as well as additional requirements for single band 4C-HSDPA. + +UEs supporting dual band 4C-HSDPA shall support minimum requirements, additional requirements for DC-HSDPA, additional requirements for DB-DC-HSDPA as well as additional requirements for dual band 4C-HSDPA. + +UEs supporting single band 8C-HSDPA shall support minimum requirements, additional requirements for DC-HSDPA and single band 4C-HSDPA as well as additional requirements for single band 8C-HSDPA. + +UEs supporting single band NC-4C-HSDPA shall support minimum requirements, additional requirements for DC-HSDPA as well as additional requirements for NC-4C-HSDPA. + +For minimum requirements, all the parameters in clause 7 are defined using the DL reference measurement channel (12.2 kbps) specified in subclause A.3.1 and unless otherwise stated with DL power control OFF. + +For the additional requirements for DC-HSDPA, DB-DC-HSDPA, DC-HSUPA, single band/dual band 4C-HSDPA or single band 8C-HSDPA or single band NC-4C-HSDPA, all the parameters in clause 7 are defined using the DL reference measurement channel H-Set 12, specified in subclause A.7.1.12 and the downlink physical channel setup according to table C.12C. + +For the additional requirements for DC-HSDPA, the spacing of the carrier frequencies of the two cells in downlink shall be 5 MHz, and it is assumed that the UE is configured with a single uplink carrier frequency. + +For the additional requirements for DC-HSUPA, the spacing of the carrier frequencies of the two cells in both downlink and uplink shall be 5 MHz. + +For the additional requirements for single band/dual band 4C-HSDPA or single band NC-4C-HSDPA, the spacing of the adjacent carrier frequencies in downlink and uplink shall be 5 MHz. + +For the additional requirements for single 8C-HSDPA, the spacing of the adjacent carrier frequencies in downlink and uplink shall be 5 MHz. + +For each single band/dual band 4C-HSDPA and single band 8C-HSDPA or single band NC-4C-HSDPA configuration, the UL-DL carrier separation is defined as minimum (maximum) when the UL carrier is placed at minimum (maximum) possible distance in frequency from the closest carrier in the corresponding DL band for which the requirement applies. + +The requirements specified in Section 7 in general could be different for each single band/dual band 4C-HSDPA or single band NC-4C-HSDPA configuration within the same operating band(s). + +For the additional requirements for single band NC-4C-HSDPA, in-gap test refers to the case when the interfering signal is located at a positive offset with respect to the the assigned channel frequency of the highest carrier frequency of the left end subblock; or located at a negative offset with respect to the assigned channel frequency of the lowest carrier frequency of the right end subblock. + +For the additional requirements for single band NC-4C-HSDPA out-of-gap test refers to the case when the interfering signal(s) is (are) located at a positive offset with respect to the assigned channel frequency of the highest carrier frequency, or located at a negative offset with respect to the assigned channel frequency of the lowest carrier frequency. + +For the additional requirements for single band NC-4C-HSDPA, existing blocking characteristics requirements shall be supported for in-gap tests only if the gap length satisfies the following condition so that the interferer position does not change the nature of the core requirement tested: + +$$\text{Gap length} \geq 2 * \text{Interferer frequency offset} - 5\text{MHz}$$ + +## 7.2 Diversity characteristics + +A suitable receiver structure using coherent reception in both channel impulse response estimation and code tracking procedures is assumed. Three forms of diversity are considered to be available in UTRA/FDD. + +**Table 7.1: Diversity characteristics for UTRA/FDD** + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time diversity | Channel coding and interleaving in both up link and down link | +| Multi-path diversity | Rake receiver or other suitable receiver structure with maximum combining. Additional processing elements can increase the delay-spread performance due to increased capture of signal energy. | +| Antenna diversity | Antenna diversity with maximum ratio combining in the Node B and optionally in the UE. Possibility for downlink transmit diversity in the Node B. | + +## 7.3 Reference sensitivity level + +The reference sensitivity level $\langle \text{REFSENS} \rangle$ is the minimum mean power received at the UE antenna port at which the specified minimum requirement shall be met. + +### 7.3.1 Minimum requirement + +The BER shall not exceed 0.001 for the parameters specified in Table 7.2. + +**Table 7.2: Test parameters for reference sensitivity, minimum requirement.** + +| Operating Band | Unit | DPCH_Ec $\langle \text{REFSENS} \rangle$ | $\langle \text{REF}_{\text{Io}} \rangle$ | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------| +| I | dBm/3.84 MHz | -117 | -106.7 | +| II | dBm/3.84 MHz | -115 | -104.7 | +| III | dBm/3.84 MHz | -114 | -103.7 | +| IV | dBm/3.84 MHz | -117 | -106.7 | +| V | dBm/3.84 MHz | -115 | -104.7 | +| VI | dBm/3.84 MHz | -117 | -106.7 | +| VII | dBm/3.84 MHz | -115 | -104.7 | +| VIII | dBm/3.84 MHz | -114 | -103.7 | +| IX | dBm/3.84 MHz | -116 | -105.7 | +| X | dBm/3.84 MHz | -117 | -106.7 | +| XI | dBm/3.84 MHz | -117 | -106.7 | +| XII | dBm/3.84 MHz | -114 | -103.7 | +| XIII | dBm/3.84 MHz | -114 | -103.7 | +| XIV | dBm/3.84 MHz | -114 | -103.7 | +| XIX | dBm/3.84 MHz | -117 | -106.7 | +| XX | dBm/3.84 MHz | -114 | -103.7 | +| XXI | dBm/3.84 MHz | -117 | -106.7 | +| XXII | dBm/3.84 MHz | -114 | -103.7 | +| XXV | dBm/3.84 MHz | -113.5 | -103.2 | +| XXVI | dBm/3.84 MHz | -113.5 | -103.2 | +| NOTE 1 | For Power class 3 and 3bis this shall be at the maximum output power | | | +| NOTE 2 | For Power class 4 this shall be at the maximum output power | | | +| NOTE 3 | For the UE which supports both Band III and Band IX operating frequencies, the reference sensitivity level of -114.5 dBm DPCH_Ec $\langle \text{REFSENS} \rangle$ shall apply for Band IX. The corresponding $\langle \text{REF}_{\text{Io}} \rangle$ is -104.2 dBm | | | +| NOTE 4 | For the UE which supports both Band XI and Band XXI operating frequencies, the reference sensitivity level is FFS. | | | +| NOTE 5 | For the UE which supports both Band V and Band XXVI operating frequencies, the reference sensitivity level of -115 dBm DPCH_Ec $\langle \text{REFSENS} \rangle$ shall apply for Band XXVI when the carrier frequency of the assigned UTRA channel is within 869-894 MHz. The corresponding $\langle \text{REF}_{\text{Io}} \rangle$ is -104.7 dBm. | | | + +For the UE which supports DB-DC-HSDPA configuration in Table 7.2aA, the reference sensitivity level DPCH\_Ec and corresponding in Table 7.2 are allowed to be increased by the amount given in Table 7.2aA for the applicable bands. + +**Table 7.2aA: Allowed de-sensitization relative to reference sensitivity for UE which supports DB-DC-HSDPA.** + +| DB-DC-HSDPA Configuration | Allowed de-sensitization (dB) | Applicable bands | +|----------------------------------|--------------------------------------|-------------------------| +| 2 | 1 | II, IV | +| 4 | 1 | I, XI | + +For the UE which supports dual band 4C-HSDPA configuration in Table 7.2aB, the reference sensitivity level DPCH\_Ec and corresponding in Table 7.2 are allowed to be increased by the amount given in Table 7.2aB for the applicable bands. + +**Table 7.2aB: Allowed de-sensitization relative to reference sensitivity for UE which supports dual band 4C-HSDPA.** + +| Dual Band 4C-HSDPA Configuration | Allowed de-sensitization (dB) | Applicable bands | +|-----------------------------------------|--------------------------------------|-------------------------| +| II-1-IV-2 | 1 | II, IV | +| II-2-IV-1 | | | +| II-2-IV-2 | | | + +For the UE which supports E-UTRA inter-band carrier aggregation the reference sensitivity level DPCH\_Ec and corresponding in Table 7.2 are allowed to be increased by the amount given in Table 7.3.1-1A of TS 36.101[11] for those UTRA operating bands corresponding to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. The tolerance in Table 7.3.1-1A of TS 36.101[11] does not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. + +In case the UE supports DB-DC-HSDPA or dual band 4C-HSDPA configurations and one or more of the E-UTRA inter-band carrier aggregation configurations listed in Table 7.3.1-1A of TS36.101[11] with a UTRA operating band that belongs to UTRA and E-UTRA carrier aggregation configurations, then + +- When the UTRA operating band frequency range is $\leq 1$ GHz, the applicable additional tolerance shall be the average of the applicable tolerances, truncated to one decimal place for that operating band among the supported DB-DC-HSDPA, dual band 4C-HSDPA, and E-UTRA CA configurations, with the DB-DC-HSDPA, dual carrier 4C-HSDPA, and E-UTRA CA configurations counted separately. In case there is a harmonic relation between low band UL and high band DL, then the maximum tolerance among the different supported carrier aggregation configurations involving such band shall be applied +- When the UTRA operating band frequency range is $>1$ GHz, the applicable additional tolerance shall be the maximum tolerance that applies for that operating band among the supported DB-DC-HSDPA, dual band HSDPA, and E-UTRA CA configurations. + +### 7.3.2 Additional requirement for DC-HSDPA + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.2A. + +Note: The reference sensitivity level requirement for DC-HSDPA is not applicable for dual uplink operation. However, there might be a substantial Rx de-sensitization for the UE operating in bands which have less than 80 MHz Tx-Rx frequency separation, transmitting on more than one uplink frequency, at maximum power. + +**Table 7.2A: Test parameters for reference sensitivity, additional requirement for DC-HSDPA.** + +| Operating Band | Unit | HS-PDSCH_Ec
| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------|-----------------------| +| I | dBm/3.84 MHz | -113 | -102.7 | +| II | dBm/3.84 MHz | -111 | -100.7 | +| III | dBm/3.84 MHz | -110 | -99.7 | +| IV | dBm/3.84 MHz | -113 | -102.7 | +| V | dBm/3.84 MHz | -111 | -100.7 | +| VI | dBm/3.84 MHz | -113 | -102.7 | +| VII | dBm/3.84 MHz | -111 | -100.7 | +| VIII | dBm/3.84 MHz | -110 | -99.7 | +| IX | dBm/3.84 MHz | -112 | -101.7 | +| X | dBm/3.84 MHz | -113 | -102.7 | +| XI | dBm/3.84 MHz | -113 | -102.7 | +| XII | dBm/3.84 MHz | -110 | -99.7 | +| XIII | dBm/3.84 MHz | -110 | -99.7 | +| XIV | dBm/3.84 MHz | -110 | -99.7 | +| XIX | dBm/3.84 MHz | -113 | -102.7 | +| XX | dBm/3.84 MHz | -110 | -99.7 | +| XXI | dBm/3.84 MHz | -113 | -102.7 | +| XXII | dBm/3.84 MHz | -110 | -99.7 | +| XXV | dBm/3.84 MHz | -109.5 | -99.2 | +| XXVI | dBm/3.84 MHz | -109.5 | -99.2 | +| NOTE 1 For Power class 3 and 3bis this shall be at the maximum output power | | | | +| NOTE 2 For Power class 4 this shall be at the maximum output power | | | | +| NOTE 3 For the UE which supports both Band III and Band IX operating frequencies, the reference sensitivity level of -110.5 dBm HS-PDSCH_Ec shall apply for Band IX. The corresponding is -100.2 dBm | | | | +| NOTE 4 For the UE which supports both Band XI and Band XXI operating frequencies, the reference sensitivity level is FFS. | | | | +| NOTE 5 For the UE which supports both Band V and Band XXVI operating frequencies, the reference sensitivity level of -111 dBm HS-PDSCH_Ec shall apply for Band XXVI when any of the carrier frequencies of the assigned UTRA channel is within 869-894 MHz. The corresponding is -100.7 dBm. | | | | + +For the UE which supports DB-DC-HSDPA configuration in Table 7.2AA, the reference sensitivity level HS-PDSCH\_Ec and corresponding in Table 7.2A are allowed to be increased by the amount given in Table 7.2AA for the applicable bands. + +**Table 7.2AA: Allowed de-sensitization relative to reference sensitivity for UE which supports DB-DC-HSDPA.** + +| DB-DC-HSDPA
Configuration | Allowed de-sensitization (dB) | Applicable bands | +|------------------------------|-------------------------------|------------------| +| 2 | 1 | II, IV | +| 4 | 1 | I, XI | + +For the UE which supports dual band 4C-HSDPA configuration in Table 7.2AB, the reference sensitivity level HS-PDSCH\_Ec and corresponding in Table 7.2A are allowed to be increased by the amount given in Table 7.2AB for the applicable bands. + +**Table 7.2AB: Allowed de-sensitization relative to reference sensitivity for UE which supports dual band 4C-HSDPA.** + +| Dual Band 4C-HSDPA Configuration n | Allowed de-sensitization (dB) | Applicable bands | +|------------------------------------|-------------------------------|------------------| +| II-1-IV-2 | 1 | II, IV | +| II-2-IV-1 | | | +| II-2-IV-2 | | | + +For the UE which supports E-UTRA inter-band carrier aggregation the reference sensitivity level HS-PDSCH\_Ec and corresponding tot> in Table 7.2A are allowed to be increased by the amount given in Table 7.3.1-1A of TS 36.101[11] for those UTRA operating bands corresponding to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. The tolerance in Table 7.3.1-1A of TS 36.101[11] does not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. + +In case the UE supports DB-DC-HSDPA or dual band 4C-HSDPA configurations and one or more of the E-UTRA inter-band carrier aggregation configurations listed in Table 7.3.1-1A of TS36.101[11] with a UTRA operating band that belongs to UTRA and E-UTRA carrier aggregation configurations, then + +- When the UTRA operating band frequency range is $\leq 1$ GHz, the applicable additional tolerance shall be the average of the applicable tolerances, truncated to one decimal place for that operating band among the supported DB-DC-HSDPA, dual band 4C-HSDPA, and E-UTRA CA configurations, with the DB-DC-HSDPA, dual carrier 4C-HSDPA, and E-UTRA CA configurations counted separately. In case there is a harmonic relation between low band UL and high band DL, then the maximum tolerance among the different supported carrier aggregation configurations involving such band shall be applied +- When the UTRA operating band frequency range is $>1$ GHz, the applicable additional tolerance shall be the maximum tolerance that applies for that operating band among the supported DB-DC-HSDPA, dual band 4C-HSDPA, and E-UTRA CA configurations. + +### 7.3.3 Additional requirement for DB-DC-HSDPA + +For all requirements listed in Table 7.2.B, corresponding to the specific DB-DC-HSDPA configuration(s) supported by the UE, (see Table 5.0aA), the BLER measured on each individual cell shall not exceed 0.1. + +**Table 7.2B: Test parameters for reference sensitivity, additional requirement for DB-DC-HSDPA.** + +| DB-DC-HSDPA configuration | DL Band | UL Band | Unit | HS-PDSCH_Ec | or > | +|---------------------------|---------|---------|--------------|-----------------------|-----------------------| +| 1 | I | I | dBm/3.84 MHz | -113 | -102.7 | +| | VIII | | dBm/3.84 MHz | -110 | -99.7 | +| | I | VIII | dBm/3.84 MHz | -113 | -102.7 | +| | VIII | | dBm/3.84 MHz | -110 | -99.7 | +| 2 | II | II | dBm/3.84 MHz | -110 | -99.7 | +| | IV | | dBm/3.84 MHz | -112 | -101.7 | +| | II | IV | dBm/3.84 MHz | -110 | -99.7 | +| | IV | | dBm/3.84 MHz | -112 | -101.7 | +| 3 | I | I | dBm/3.84 MHz | -113 | -102.7 | +| | V | | dBm/3.84 MHz | -111 | -100.7 | +| | I | V | dBm/3.84 MHz | -113 | -102.7 | +| | V | | dBm/3.84 MHz | -111 | -100.7 | +| 4 | I | I | dBm/3.84 MHz | -112 | -101.7 | +| | XI | | dBm/3.84 MHz | -112 | -101.7 | +| | I | XI | dBm/3.84 MHz | -112 | -101.7 | +| | XI | | dBm/3.84 MHz | -112 | -101.7 | +| 5 | II | II | dBm/3.84 MHz | -111 | -100.7 | +| | V | | dBm/3.84 MHz | -111 | -100.7 | +| | II | V | dBm/3.84 MHz | -111 | -100.7 | +| | V | | dBm/3.84 MHz | -111 | -100.7 | +| 6 | I | I | dBm/3.84 MHz | -113 | -102.7 | +| | XXXII | | dBm/3.84 MHz | -113 | -102.7 | + +NOTE 1 For Power class 3 and 3bis this shall be at the maximum output power + +NOTE 2 For Power class 4 this shall be at the maximum output power + +### 7.3.4 Additional requirement for single band 4C-HSDPA + +For all requirements listed in Table 7.2C, corresponding to the specific single band 4C-HSDPA configuration(s) supported by the UE, (see Table 5.0aB), the BLER measured on each individual cell shall not exceed 0.1. + +Note: The reference sensitivity level requirement for single band 4C-HSDPA is not applicable for dual uplink operation. However, there might be a substantial Rx de-sensitization for the UE operating in bands which have less than 80 MHz Tx-Rx frequency separation, transmitting on more than one uplink frequency, at maximum power. + +**Table 7.2C: Test parameters for reference sensitivity, additional requirement for single band 4C-HSDPA.** + +| Single band 4C-HSDPA configuration | DL Band | Unit | HS-PDSCH_Ec | or > | UL-DL carrier separation | +|---------------------------------------------------------------------------------|---------|--------------|-----------------------|-----------------------|--------------------------| +| I-3 | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| II-3, II-4 | II | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| NOTE 1 For Power class 3, 3bis and 4, this shall be at the maximum output power | | | | | | + +For the UE which supports DB-DC-HSDPA configuration in Table 7.2CA, the reference sensitivity level HS-PDSCH\_Ec and corresponding or> in Table 7.2C are allowed to be increased by the amount given in Table 7.2CA for the applicable bands. + +**Table 7.2CA: Allowed de-sensitization relative to reference sensitivity for UE which supports DB-DC-HSDPA.** + +| DB-DC-HSDPA Configuration | Allowed de-sensitization (dB) | Applicable bands | +|---------------------------|-------------------------------|------------------| +| 2 | 1 | II | +| 4 | 1 | I | + +For the UE which supports dual band 4C-HSDPA configuration in Table 7.2CB, the reference sensitivity level *HS-PDSCH\_Ec* $\text{}$ and corresponding $\text{}$ in Table 7.2C are allowed to be increased by the amount given in Table 7.2CB for the applicable bands. + +**Table 7.2CB: Allowed de-sensitization relative to reference sensitivity for UE which supports dual band 4C-HSDPA.** + +| Dual Band 4C-HSDPA Configuration
n | Allowed de-sensitization (dB) | Applicable bands | +|---------------------------------------|-------------------------------|------------------| +| II-1-IV-2 | 1 | II | +| II-2-IV-1 | | | +| II-2-IV-2 | | | + +For the UE which supports E-UTRA inter-band carrier aggregation the reference sensitivity level *HS-PDSCH\_Ec* $\text{}$ and corresponding $\text{}$ in Table 7.2C are allowed to be increased by the amount given in Table 7.3.1-1A of TS 36.101[11] for those UTRA operating bands corresponding to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. The tolerance in Table 7.3.1-1A of TS 36.101[11] does not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. + +In case the UE supports DB-DC-HSDPA configurations and one or more of the E-UTRA inter-band carrier aggregation configurations listed in Table 7.3.1-1A of TS36.101[11] with a UTRA operating band that belongs to UTRA and E-UTRA carrier aggregation configurations, then + +- When the UTRA operating band frequency range is $\leq 1\text{GHz}$ , the applicable additional tolerance shall be the average of the applicable tolerances, truncated to one decimal place for that operating band among the supported DB-DC-HSDPA and E-UTRA CA configurations, with the DB-DC-HSDPA and E-UTRA CA configurations counted separately. In case there is a harmonic relation between low band UL and high band DL, then the maximum tolerance among the different supported carrier aggregation configurations involving such band shall be applied +- When the UTRA operating band frequency range is $>1\text{GHz}$ , the applicable additional tolerance shall be the maximum tolerance that applies for that operating band among the supported DB-DC-HSDPA and E-UTRA CA configurations. + +### 7.3.5 Additional requirement for dual band 4C-HSDPA + +For all requirements listed in Table 7.2D, corresponding to the specific dual band 4C-HSDPA configuration(s) supported by the UE, (see Table 5.0aC), the BLER measured on each individual cell shall not exceed 0.1. + +Note: The reference sensitivity level requirement for dual band 4C-HSDPA is not applicable for dual uplink operation. However, there might be a substantial Rx de-sensitization for the UE operating in bands which have less than 80 MHz Tx-Rx frequency separation, transmitting on more than one uplink frequency, at maximum power. + +**Table 7.2D: Test parameters for reference sensitivity, additional requirement for dual band 4C-HSDPA.** + +| Dual band 4C-HSDPA configuration | DL Band | UL Band | Unit | HS-PDSCH_Ec | or > | UL-DL carrier separation | +|----------------------------------|---------|---------|--------------|-----------------------|-----------------------|--------------------------| +| I-2-VIII-1 | I | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| I-3-VIII-1 | VIII | | dBm/3.84 MHz | -110 | -99.7 | Minimum | +| I-2-VIII-2 | I | VIII | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| I-1-VIII-2 | VIII | | dBm/3.84 MHz | -110 | -99.7 | Minimum | +| II-1-IV-2 | II | II | dBm/3.84 MHz | -110 | -99.7 | Minimum | +| II-2-IV-1 | IV | | dBm/3.84 MHz | -112 | -101.7 | Minimum | +| II-2-IV-2 | II | IV | dBm/3.84 MHz | -110 | -99.7 | Minimum | +| | IV | | dBm/3.84 MHz | -112 | -101.7 | Minimum | +| I-1-V-2 | I | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| I-2-V-1 | V | | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| I-2-V-2 | I | V | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| | V | | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| II-1-V-2 | II | II | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| | V | | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| | II | V | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| | V | | dBm/3.84 MHz | -111 | -100.7 | Minimum | +| I-1-XXXII-2 | I | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| I-2-XXXII-1 | XXXII | | dBm/3.84 MHz | -113 | -102.7 | Minimum | + +NOTE 1 For Power class 3, 3bis and 4, this shall be at the maximum output power + +### 7.3.6 Additional requirement for single band 8C-HSDPA + +For all requirements listed in Table 7.2E, corresponding to the specific single band 8C-HSDPA configuration(s) supported by the UE, (see Table 5.0aD), the BLER measured on each individual cell shall not exceed 0.1. + +Note: The reference sensitivity level requirement for single band 8C-HSDPA is not applicable for dual uplink operation. However, there might be a substantial Rx de-sensitization for the UE operating in bands which have less than 80 MHz Tx-Rx frequency separation, transmitting on more than one uplink frequency, at maximum power. + +**Table 7.2E: Test parameters for reference sensitivity, additional requirement for single band 8C-HSDPA.** + +| Single band 8C-HSDPA configuration | DL Band | Unit | HS-PDSCH_Ec | or > | UL-DL carrier separation | +|---------------------------------------------------------------------------------|---------|--------------|-----------------------|-----------------------|--------------------------| +| I-8 | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| NOTE 1 For Power class 3, 3bis and 4, this shall be at the maximum output power | | | | | | + +### 7.3.7 Additional requirement for single band NC-4C-HSDPA + +For all requirements listed in Table 7.2E, corresponding to the specific single band NC-4C-HSDPA configuration(s) supported by the UE, (see Table 5.0aE), the BLER measured on each individual cell shall not exceed 0.1. + +Note: The reference sensitivity level requirement for single band NC-4C-HSDPA is not applicable for dual uplink operation. However, there might be a substantial Rx de-sensitization for the UE operating in bands which have less than 80 MHz Tx-Rx frequency separation, transmitting on more than one uplink frequency, at maximum power. + +**Table 7.2E: Test parameters for reference sensitivity, additional requirement for single band NC-4C-HSDPA.** + +| Single band NC-4C-HSDPA configuration | DL Band | Unit | HS-PDSCH_Ec | o > | UL-DL carrier separation | +|---------------------------------------------------------------------------------|---------|--------------|-----------------------|----------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | I | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | IV | dBm/3.84 MHz | -113 | -102.7 | Minimum | +| NOTE 1 For Power class 3, 3bis and 4, this shall be at the maximum output power | | | | | | + +For the UE which supports DB-DC-HSDPA configuration in Table 7.2F, the reference sensitivity level HS-PDSCH\_Ec and corresponding o> in Table 7.2E are allowed to be increased by the amount given in Table 7.2F for the applicable bands. + +**Table 7.2F: Allowed de-sensitization relative to reference sensitivity for UE which supports DB-DC-HSDPA.** + +| DB-DC-HSDPA Configuration | Allowed de-sensitization (dB) | Applicable bands | +|---------------------------|-------------------------------|------------------| +| 2 | 1 | IV | +| 4 | 1 | I | + +For the UE which supports dual band 4C-HSDPA configuration in Table 7.2G, the reference sensitivity level HS-PDSCH\_Ec and corresponding o> in Table 7.2E are allowed to be increased by the amount given in Table 7.2G for the applicable bands. + +**Table 7.2G: Allowed de-sensitization relative to reference sensitivity for UE which supports dual band 4C-HSDPA.** + +| Dual Band 4C-HSDPA Configuration | Allowed de-sensitization (dB) | Applicable bands | +|-------------------------------------|-------------------------------|------------------| +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | 1 | IV | + +For the UE which supports E-UTRA inter-band carrier aggregation the reference sensitivity level HS-PDSCH\_Ec and corresponding o> in Table 7.2E are allowed to be increased by the amount given in Table 7.3.1-1A of TS 36.101[11] for those UTRA operating bands corresponding to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. The tolerance in Table 7.3.1-1A of TS 36.101[11] does not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. + +In case the UE supports DB-DC-HSDPA configurations and one or more of the E-UTRA inter-band carrier aggregation configurations listed in Table 7.3.1-1A of TS36.101[11] with a UTRA operating band that belongs to UTRA and E-UTRA carrier aggregation configurations, then + +- When the UTRA operating band frequency range is $\leq 1\text{GHz}$ , the applicable additional tolerance shall be the average of the applicable tolerances, truncated to one decimal place for that operating band among the supported DB-DC-HSDPA and E-UTRA CA configurations, with the DB-DC-HSDPA and E-UTRA CA configurations counted separately. In case there is a harmonic relation between low band UL and high band DL, then the maximum tolerance among the different supported carrier aggregation configurations involving such band shall be applied +- When the UTRA operating band frequency range is $> 1\text{GHz}$ , the applicable additional tolerance shall be the maximum tolerance that applies for that operating band among the supported DB-DC-HSDPA and E-UTRA CA configurations. + +## 7.4 Maximum input level + +This is defined as the maximum mean power received at the UE antenna port, at which the specified BER performance shall be met. + +### 7.4.1 Minimum requirement for DPCH reception + +The BER shall not exceed 0.001 for the parameters specified in Table 7.3. + +**Table 7.3: Maximum input level** + +| Parameter | Unit | Level | +|--------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------| +| $\frac{DPCH\_Ec}{I_{or}}$ | dB | -19 | +| $\hat{I}_{or}$ | dBm/3.84 MHz | -25 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 1 | +| NOTE 1: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | + +NOTE: Since the spreading factor is large ( $10\log(\text{SF})=21\text{dB}$ ), the majority of the total input signal consists of the OCNS interference. The structure of OCNS signal is defined in Annex C.3.2. + +### 7.4.2 Minimum requirement for HS-PDSCH reception + +#### 7.4.2.1 Minimum requirement for 16QAM + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H-Set 1 (16QAM version) specified in Annex A.7.1.1 with the addition of the parameters in Table 7.3A and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3B. + +**Table 7.3A Test parameters for maximum input level** + +| Parameter | Unit | Value | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------|---------------------------------------------------------------------| +| | Phase reference | | P-CPICH | +| $\hat{I}_{or}$ | | dBm/3.84 MHz | -25 | +| UE transmitted mean power | | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 2 | +| DPCH_Ec/Ior | | dB | -13 | +| HS-SCCH_1_Ec/Ior | | dB | -13 | +| Redundancy and constellation version | | | 6 | +| Maximum number of HARQ transmissions | | | 1 | +| NOTE 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every third TTI | | | | +| NOTE 2: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | + +**Table 7.3B Minimum requirement** + +| HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|-------------------------------|------------------| +| -3 | 700 | + +#### 7.4.2.2 Minimum requirement for 64QAM + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H-Set 8 specified in Annex A.7.1.8. with the addition of the parameters in Table 7.3C and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3D. + +**Table 7.3C Test parameters for maximum input level** + +| Parameter | Unit | Value | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------|---------| +| | Phase reference | | P-CPICH | +| $\hat{I}_{or}$ | | dBm/3.84 MHz | -25 | +| UE transmitted mean power | | dBm | 0 | +| DPCH_Ec/Ior | | dB | -13 | +| HS-SCCH_1_Ec/Ior | | dB | -13 | +| Redundancy and
constellation version | | | 6 | +| Maximum number of
HARQ transmissions | | | 1 | +| NOTE 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every third TTI. | | | | + +**Table 7.3D Minimum requirement** + +| HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|-------------------------------|------------------| +| -2 | 11800 | + +## 7.4.3 Additional requirement for DC-HSDPA and DB-DC-HSDPA + +### 7.4.3.1 Additional requirement for 16QAM + +The additional requirements are specified in terms of a minimum information throughput per cell $R$ with the DL reference channel H-Set 1 (16QAM version) specified in Annex A7.1.1, with the addition of the parameters in Table 7.3E, and the downlink physical channel setup according to table C.8, applied to both cells simultaneously. Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3F. + +**Table 7.3E Test parameters for maximum input level** + +| Parameter | Unit | Value | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------|---------------------------------------------------------------------| +| | Phase reference | | P-CPICH | +| $\hat{I}_{or}$ | | dBm/3.84 MHz | -25 | +| UE transmitted mean power | | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 2 | +| DPCH_Ec/Ior | | dB | -13 | +| HS-SCCH_1_Ec/Ior | | dB | -13 | +| Redundancy and
constellation version | | | 6 | +| Maximum number of
HARQ transmissions | | | 1 | +| NOTE 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every third TTI | | | | +| NOTE 2: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | + +**Table 7.3F Minimum requirement** + +| HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|-------------------------------|------------------| +| -3 | 700 | + +### 7.4.3.2 Additional requirement for 64QAM + +The additional requirements are specified in terms of a minimum information throughput per cell $R$ with the DL reference channel H-Set 8 specified in Annex A7.1.8, with the addition of the parameters in Table 7.3G, and the downlink physical channel setup according to table C.8, applied to both cells simultaneously. Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3H. + +**Table 7.3G Test parameters for maximum input level** + +| Parameter | Unit | Value | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------|---------| +| | Phase reference | | P-CPICH | +| | $\hat{I}_{or}$ | dBm/3.84 MHz | -25 | +| | UE transmitted mean power | dBm | 0 | +| | DPCH_Ec/Ior | dB | -13 | +| | HS-SCCH_1_Ec/Ior | dB | -13 | +| | Redundancy and
constellation version | | 6 | +| | Maximum number of
HARQ transmissions | | 1 | +| NOTE 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every third TTI | | | | + +**Table 7.3H Minimum requirement** + +| HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|-------------------------------|------------------| +| -2 | 11800 | + +## 7.4.4 Additional requirement for single band/dual band 4C-HSDPA or single band 8C-HSDPA and single band NC-4C-HSDPA + +### 7.4.4.1 Additional requirement for 16QAM + +The additional requirements are specified in terms of a minimum information throughput per cell $R$ with the DL reference channel H-Set 1 (16QAM version) specified in Annex A7.1.1, with the addition of the parameters in Table 7.3I, and the downlink physical channel setup according to table C.8, applied to all the cells simultaneously. Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3J. + +**Table 7.3I Test parameters for maximum input level** + +| Parameter | Unit | Value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-----------------------------------------------------------| +| Phase reference | | P-CPICH | +| Wanted signal mean power per band (dBm) | dBm/band | -22 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | +| DPCH_Ec/Ior | dB | -13 | +| HS-SCCH_1_Ec/Ior | dB | -13 | +| Redundancy and constellation version | | 6 | +| Maximum number of HARQ transmissions | | 1 | +| Note 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every thir TTI | | | +| Note 2 : Wanted signal mean power per band is the sum of measured mean power on each carrier in a band over 3.84 MHz. | | | + +**Table 7.3J Minimum requirement** + +| HS-PDSCH $E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|----------------------------|------------------| +| -3 | 700 | + +#### 7.4.4.2 Additional requirement for 64QAM + +The additional requirements are specified in terms of a minimum information throughput per cell $R$ with the DL reference channel H-Set 8 specified in Annex A7.1.8, with the addition of the parameters in Table 7.3K, and the downlink physical channel setup according to table C.8, applied to all the cells simultaneously. Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 7.3L. + +**Table 7.3K Parameters definition** + +| Parameter | Unit | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------| +| Phase reference | | P-CPICH | +| Wanted signal mean power per band (dBm) | dBm/band | -22 | +| UE transmitted mean power | dBm | 0 | +| DPCH_Ec/Ior | dB | -13 | +| HS-SCCH_1_Ec/Ior | dB | -13 | +| Redundancy and constellation version | | 6 | +| Maximum number of HARQ transmissions | | 1 | +| Note 1: The HS-SCCH and corresponding HS-PDSCH shall be transmitted continuously with constant power but the HS-SCCH shall only use the identity of the UE under test every third TTI | | | +| Note 2: Wanted signal mean power per band is the sum of measured mean power on each carrier in a band over 3.84 MHz. | | | + +**Table 7.3L Minimum requirement** + +| HS-PDSCH $E_c/I_{or}$ (dB) | T-put $R$ (kbps) | +|----------------------------|------------------| +| -2 | 11800 | + +## 7.5 Adjacent Channel Selectivity (ACS) + +Adjacent Channel Selectivity (ACS) is a measure of a receiver's ability to receive a W-CDMA 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). + +### 7.5.1 Minimum requirement + +The UE shall fulfill the minimum requirement specified in Table 7.4 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 where the BER shall not exceed 0.001. + +**Table 7.4: Adjacent Channel Selectivity** + +| Unit | ACS | +|------|-----| +| dB | 33 | + +**Table 7.5: Test parameters for Adjacent Channel Selectivity** + +| Parameter | Unit | Case 1 | Case 2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------|---------------------------------------------------------------------| +| DPCH_Ec | dBm/3.84 MHz | + 14 dB | + 41 dB | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 14 dB | REF $\hat{I}_{or}$ + 41 dB | +| $I_{oac}$ mean power (modulated) | dBm | -52 | -25 | +| $F_{uw}$ (offset) | MHz | +5 or -5 | +5 or -5 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | +| NOTE 1: The $I_{oac}$ (modulated) signal consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | +| NOTE 2: and refers to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | | +| NOTE 3: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | + +### 7.5.2 Additional requirement for DC-HSDPA and DB-DC-HSDPA + +The UE shall fulfill the additional requirement specified in Table 7.5A 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.5B, where the HS-PDSCH BLER shall not exceed 0.1. + +**Table 7.5A: Adjacent Channel Selectivity** + +| Unit | ACS | +|------|-----| +| dB | 33 | + +**Table 7.5B: Test parameters for Adjacent Channel Selectivity** + +| Parameter | Unit | Case 1 | Case 2 | +|----------------------------------|--------------|---------------------------------------------------------------------|---------------------------------------------------------------------| +| HS-PDSCH_Ec | dBm/3.84 MHz | + 14 dB | + 41 dB | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 14 dB | + 41 dB | +| $I_{oac}$ mean power (modulated) | dBm | -52 | -25 | +| $F_{uw}$ (offset)
(NOTE 2) | MHz | +5 or -5 | +5 or -5 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 4 | + +NOTE 1: The $I_{oac}$ (modulated) signal consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. + +NOTE 2: For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells. + +NOTE 3: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2A for DC-HSDPA and Table 7.2B for DB-DC-HSDPA. + +NOTE 4: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. + +### 7.5.3 Additional requirement for single band/dual band 4C-HSDPA + +The UE shall fulfill the additional requirement specified in Table 7.5C 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.5D and the requirements are given in Table 7.5E and Table 7.5EA for single band 4C-HSDPA and in 7.5F and 7.5G for dual band 4C-HSDPA, where the HS-PDSCH BLER shall not exceed 0.1. + +The ACS requirement for single band/dual-band 4C-HSDPA is not applicable for dual uplink operation. + +**Table 7.5C: Adjacent Channel Selectivity** + +| Rx Parameter | Unit | Number of adjacent downlink carriers in a band | | | | +|--------------|------|------------------------------------------------|----|----|----| +| | | 1 | 2 | 3 | 4 | +| ACS | dB | 33 | 33 | 33 | 33 | + +**Table 7.5D: Test parameters for Adjacent Channel Selectivity** + +| Parameter | Unit | Case 1 | Case 2 | +|----------------------------------|------|-----------------------------------------------------------|----------| +| $I_{oac}$ mean power (modulated) | dBm | -52 | -25 | +| $F_{uw}$ (offset)
(NOTE 2) | MHz | +5 or -5 | +5 or -5 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | + +NOTE 1: The $I_{oac}$ (modulated) signal consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. + +NOTE 2: Negative offset refers to the assigned channel frequency of the lowest carrier frequency(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequency(ies) in each band. + +**Table 7.5E: Single band 4C-HSDPA requirements for Adjacent Channel Selectivity, Case 1** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| I-3 | I | +14 dB | +14 dB | Minimum | +| II-3, II-4 | II | +14 dB | +14 dB | Minimum | +| NOTE: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +**Table 7.5EA: Single band 4C-HSDPA requirements for Adjacent Channel Selectivity, Case 2** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| I-3 | I | +41 dB | +41 dB | Minimum | +| II-3, II-4 | II | +41 dB | +41 dB | Minimum | +| NOTE: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +Table 7.5F: Dual band 4C-HSDPA requirements for Adjacent Channel Selectivity, Case 1 + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------|---------|---------|---------------------------|------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | I | I | +14 dB | +14 dB | Minimum | +| | VIII | | +14 dB | +14 dB | Minimum | +| | I | VIII | +14 dB | +14 dB | Minimum | +| | VIII | | +14 dB | +14 dB | Minimum | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | II | II | +14 dB | +14 dB | Minimum | +| | IV | | +14 dB | +14 dB | Minimum | +| | II | IV | +14 dB | +14 dB | Minimum | +| | IV | | +14 dB | +14 dB | Minimum | +| I-1-V-2
I-2-V-1
I-2-V-2 | I | I | +14 dB | +14 dB | Minimum | +| | V | | +14 dB | +14 dB | Minimum | +| | I | V | +14 dB | +14 dB | Minimum | +| | V | | +14 dB | +14 dB | Minimum | +| II-1-V-2 | II | II | +14 dB | +14 dB | Minimum | +| | V | | +14 dB | +14 dB | Minimum | +| | II | V | +14 dB | +14 dB | Minimum | +| | V | | +14 dB | +14 dB | Minimum | +| I-1-XXXII-2
I-2-XXXII-1 | I | I | +14 dB | +14 dB | Minimum | +| | XXXII | | +14 dB | +14 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2D for dual band 4C-HSDPA. + +**Table 7.5G: Dual band 4C-HSDPA requirements for Adjacent Channel Selectivity, Case 2** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------|---------|---------|---------------------------|------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | I | I | +41 dB | +41 dB | Minimum | +| | VIII | | +41 dB | +41 dB | Minimum | +| | I | VIII | +41 dB | +41 dB | Minimum | +| | VIII | | +41 dB | +41 dB | Minimum | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | II | II | +41 dB | +41 dB | Minimum | +| | IV | | +41 dB | +41 dB | Minimum | +| | II | IV | +41 dB | +41 dB | Minimum | +| | IV | | +41 dB | +41 dB | Minimum | +| I-1-V-2
I-2-V-1
I-2-V-2 | I | I | +41 dB | +41 dB | Minimum | +| | V | | +41 dB | +41 dB | Minimum | +| | I | V | +41 dB | +41 dB | Minimum | +| | V | | +41 dB | +41 dB | Minimum | +| II-1-V-2 | II | II | +41 dB | +41 dB | Minimum | +| | V | | +41 dB | +41 dB | Minimum | +| | II | V | +41 dB | +41 dB | Minimum | +| | V | | +41 dB | +41 dB | Minimum | +| I-1-XXXII-2
I-2-XXXII-1 | I | I | +41 dB | +41 dB | Minimum | +| | XXXII | | +41 dB | +41 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2D for dual band 4C-HSDPA. + +## 7.5.4 Additional requirement for single band 8C-HSDPA + +The UE shall fulfill the additional requirement specified in Table 7.5H 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.5I and the requirements are given in Table 7.5J and Table 7.5K where the HS-PDSCH BLER shall not exceed 0.1. + +The ACS requirement for single band 8C-HSDPA is not applicable for dual uplink operation. + +**Table 7.5H: Adjacent Channel Selectivity** + +| Rx Parameter | Unit | Number of adjacent downlink carriers in a band | | | | | | | | +|--------------|------|------------------------------------------------|----|----|----|----|----|----|----| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| ACS | dB | 33 | 33 | 33 | 33 | 33 | 33 | 33 | 33 | + +**Table 7.5I: Test parameters for Adjacent Channel Selectivity** + +| Parameter | Unit | Case 1 | Case 2 | +|----------------------------------|------|-----------------------------------------------------------|----------| +| $I_{oac}$ mean power (modulated) | dBm | -52 | -25 | +| $F_{uw}$ (offset)
(NOTE 2) | MHz | +5 or -5 | +5 or -5 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | + +NOTE 1: The $I_{oac}$ (modulated) signal consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. + +NOTE 2: Negative offset refers to the assigned channel frequency of the lowest carrier frequency in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequency in each band. + +**Table 7.5J: Single band 8C-HSDPA requirements for Adjacent Channel Selectivity, Case 1** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| I-8 | I | +14 dB | +14 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band 8C-HSDPA. + +**Table 7.5K: Single band 8C-HSDPA requirements for Adjacent Channel Selectivity, Case 2** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| I-8 | I | +41 dB | +41 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band 8C-HSDPA. + +## 7.5.5 Additional requirement for single band NC-4C-HSDPA + +The UE shall fulfill the additional requirement specified in Table 7.5L 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.5M and the requirements are given in Table 7.5N and Table 7.5P where the HS-PDSCH BLER shall not exceed 0.1. + +The ACS requirement for single band NC-4C-HSDPA is not applicable for dual uplink operation. + +**Table 7.5L: Adjacent Channel Selectivity** + +| Rx Parameter | Unit | Number of adjacent downlink carriers in a band | | | +|--------------|------|------------------------------------------------|----|----| +| | | 1 | 2 | 3 | +| ACS | dB | 33 | 33 | 33 | + +**Table 7.5M: Test parameters for Adjacent Channel Selectivity** + +| Parameter | Unit | Case 1 | Case 2 | +|----------------------------------|------|-----------------------------------------------------------|----------| +| $I_{oac}$ mean power (modulated) | dBm | -52 | -25 | +| $F_{uw}$ (offset)
(NOTE 2,3) | MHz | +5 or -5 | +5 or -5 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | + +NOTE 1: The $I_{oac}$ (modulated) signal consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. + +NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. + +NOTE 3: For single band NC-4C-HSPDA in-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the higher subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the lower subblock of carriers. + +**Table 7.5N: Single band NC-4C-HSDPA requirements for Adjacent Channel Selectivity, Case 1** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------|------------|---------|---------------------------|------------------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | In-gap | I | +14 dB | +14 dB | Minimum | +| I-1-5-1, I-2-5-1, I-3-10-1 | Out-of-gap | I | +14 dB | +14 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | +14 dB | +14 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | +14 dB | +14 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band NC-4C-HSDPA. + +**Table 7.5P: Single band NC-4C-HSDPA requirements for Adjacent Channel Selectivity, Case 2** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------|------------|---------|---------------------------|------------------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | In-gap | I | +41 dB | +41 dB | Minimum | +| I-1-5-1, I-2-5-1, I-3-10-1 | Out-of-gap | I | +41 dB | +41 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | +41 dB | +41 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | +41 dB | +41 dB | Minimum | + +NOTE: and refers to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band NC-4C-HSDPA. + +## 7.6 Blocking characteristics + +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 occur. + +### 7.6.1 Minimum requirement (In-band blocking) + +The BER shall not exceed 0.001 for the parameters specified in Table 7.6. In-band blocking 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. + +**Table 7.6: In-band blocking** + +| Parameter | Unit | Level | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------|-----------------------------------------|--|--| +| DPCH_Ec | dBm/3.84 MHz | +3 dB | | | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 3 dB | | | | +| $I_{blocking}$ mean power (modulated) | dBm | -56 | -44 | | | +| $F_{uw}$ offset | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | | | +| $F_{uw}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{uw}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | | | +| $F_{uw}$ (Band III operation) | MHz | $1797.4 \leq f \leq 1887.6$ | $1790 \leq f \leq 1895$ | | | +| $F_{uw}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | | | +| $F_{uw}$ (Band V operation) | MHz | $861.4 \leq f \leq 901.6$ | $854 \leq f \leq 909$ | | | +| $F_{uw}$ (Band VI operation) | MHz | $867.4 \leq f \leq 892.6$
(NOTE 2) | $860 \leq f \leq 900$
(NOTE 2) | | | +| $F_{uw}$ (Band VII operation) | MHz | $2612.4 \leq f \leq 2697.6$ | $2605 \leq f \leq 2705$ | | | +| $F_{uw}$ (Band VIII operation) | MHz | $917.4 \leq f \leq 967.6$ | $910 \leq f \leq 975$ | | | +| $F_{uw}$ (Band IX operation) | MHz | $1837.4 \leq f \leq 1887.4$ | $1829.9 \leq f \leq 1894.9$ | | | +| $F_{uw}$ (Band X operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{uw}$ (Band XI operation) | MHz | $1468.4 \leq f \leq 1503.4$ | $1460.9 \leq f \leq 1510.9$ | | | +| $F_{uw}$ (Band XII operation) | MHz | $721.4 \leq f \leq 753.6$ | $714 \leq f \leq 761$ | | | +| $F_{uw}$ (Band XIII operation) | MHz | $738.4 \leq f \leq 763.6$ | $731 \leq f \leq 771$ | | | +| $F_{uw}$ (Band XIV operation) | MHz | $750.4 \leq f \leq 775.6$ | $743 \leq f \leq 783$ | | | +| $F_{uw}$ (Band XIX operation) | MHz | $867.4 \leq f \leq 897.6$ | $860 \leq f \leq 905$
(NOTE 2) | | | +| $F_{uw}$ (Band XX operation) | MHz | $783.4 \leq f \leq 828.6$ | $776 \leq f \leq 836$ | | | +| $F_{uw}$ (Band XXI operation) | MHz | $1488.4 \leq f \leq 1518.4$ | $1480.9 \leq f \leq 1525.9$
(NOTE 2) | | | +| $F_{uw}$ (Band XXII operation) | MHz | $3502.4 \leq f \leq 3597.6$ | $3495 \leq f \leq 3605$ | | | +| $F_{uw}$ (Band XXV operation) | MHz | $1922.4 \leq f \leq 2002.6$ | $1915 \leq f \leq 2010$ | | | +| $F_{uw}$ (Band XXVI operation) | MHz | $851.4 \leq f \leq 901.6$ | $844 \leq f \leq 909$ | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 4 | | | | +| NOTE 1: $I_{blocking}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For Band VI, Band XIX and Band XXI, the unwanted interfering signal does not fall inside the UE receive band, but within the first 15 MHz below or above the UE receive band. | | | | | | +| NOTE 3: and refer to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | | | | +| NOTE 4: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | | | + +### 7.6.1A Additional requirement for DC-HSDPA and DB-DC-HSDPA (In-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6A. In-band blocking 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. + +**Table 7.6A: In-band blocking for DC-HSDPA and DB-DC-HSDPA** + +| Parameter | Unit | Level | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------|-----------------------------------------|--|--| +| HS-PDSCH_Ec | dBm/3.84 MHz | +3 dB | | | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 3 dB | | | | +| $I_{blocking}$ mean power (modulated) | dBm | -56 | -44 | | | +| $F_{uw}$ offset (NOTE 3) | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | | | +| $F_{uw}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{uw}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | | | +| $F_{uw}$ (Band III operation) | MHz | $1797.4 \leq f \leq 1887.6$ | $1790 \leq f \leq 1895$ | | | +| $F_{uw}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | | | +| $F_{uw}$ (Band V operation) | MHz | $861.4 \leq f \leq 901.6$ | $854 \leq f \leq 909$ | | | +| $F_{uw}$ (Band VI operation) | MHz | $867.4 \leq f \leq 892.6$
(NOTE 2) | $860 \leq f \leq 900$
(NOTE 2) | | | +| $F_{uw}$ (Band VII operation) | MHz | $2612.4 \leq f \leq 2697.6$ | $2605 \leq f \leq 2705$ | | | +| $F_{uw}$ (Band VIII operation) | MHz | $917.4 \leq f \leq 967.6$ | $910 \leq f \leq 975$ | | | +| $F_{uw}$ (Band IX operation) | MHz | $1837.4 \leq f \leq 1887.4$ | $1829.9 \leq f \leq 1894.9$ | | | +| $F_{uw}$ (Band X operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{uw}$ (Band XI operation) | MHz | $1468.4 \leq f \leq 1503.4$ | $1460.9 \leq f \leq 1510.9$ | | | +| $F_{uw}$ (Band XII operation) | MHz | $721.4 \leq f \leq 753.6$ | $714 \leq f \leq 761$ | | | +| $F_{uw}$ (Band XIII operation) | MHz | $738.4 \leq f \leq 763.6$ | $731 \leq f \leq 771$ | | | +| $F_{uw}$ (Band XIV operation) | MHz | $750.4 \leq f \leq 775.6$ | $743 \leq f \leq 783$ | | | +| $F_{uw}$ (Band XIX operation) | MHz | $867.4 \leq f \leq 897.6$ | $860 \leq f \leq 905$
(NOTE 2) | | | +| $F_{uw}$ (Band XX operation) | MHz | $783.4 \leq f \leq 828.6$ | $776 \leq f \leq 836$ | | | +| $F_{uw}$ (Band XXI operation) | MHz | $1488.4 \leq f \leq 1518.4$ | $1480.9 \leq f \leq 1525.9$
(NOTE 2) | | | +| $F_{uw}$ (Band XXII operation) | MHz | $3502.4 \leq f \leq 3597.6$ | $3495 \leq f \leq 3605$ | | | +| $F_{uw}$ (Band XXV operation) | MHz | $1922.4 \leq f \leq 2002.6$ | $1915 \leq f \leq 2010$ | | | +| $F_{uw}$ (Band XXVI operation) | MHz | $851.4 \leq f \leq 901.6$ | $844 \leq f \leq 909$ | | | +| $F_{uw}$ (Band XXXII operation) (NOTE 6) | MHz | $1444.4 \leq f \leq 1503.6$ | $1437 \leq f \leq 1511$ | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 5 | | | | +| NOTE 1: $I_{blocking}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For Band VI, Band XIX and Band XXI, the unwanted interfering signal does not fall inside the UE receive band, but within the first 15 MHz below or above the UE receive band. | | | | | | + +- | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

NOTE 3: For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells.

NOTE 4: <REFSENS> and <REF\hat{I}_{or}> refer to the HS-PDSCH_Ec<REFSENS> and the HS-PDSCH<REF\hat{I}_{or}> as specified in Table 7.2A for DC-HSDPA and Table 7.2B for DB-DC-HSDPA.

NOTE 5: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII.

NOTE 6: Restricted to UTRA operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA)

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.6.1B Additional requirement for DC-HSUPA (In-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6B and Table 7.6C. In-band blocking 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. + +**Table 7.6B: In-band blocking for DC-HSUPA** + +| Parameter | Unit | Level | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------------------------------------------------------------------|-----------------------------------------|--|--| +| I blocking mean power (modulated) | dBm | -56 | -44 | | | +| F uw offset (NOTE 3) | | = $\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | | | +| F uw (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| F uw (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | | | +| F uw (Band III operation) | MHz | $1797.4 \leq f \leq 1887.6$ | $1790 \leq f \leq 1895$ | | | +| F uw (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | | | +| F uw (Band V operation) | MHz | $861.4 \leq f \leq 901.6$ | $854 \leq f \leq 909$ | | | +| F uw (Band VI operation) | MHz | $867.4 \leq f \leq 892.6$
(NOTE 2) | $860 \leq f \leq 900$
(NOTE 2) | | | +| F uw (Band VII operation) | MHz | $2612.4 \leq f \leq 2697.6$ | $2605 \leq f \leq 2705$ | | | +| F uw (Band VIII operation) | MHz | $917.4 \leq f \leq 967.6$ | $910 \leq f \leq 975$ | | | +| F uw (Band IX operation) | MHz | $1837.4 \leq f \leq 1887.4$ | $1829.9 \leq f \leq 1894.9$ | | | +| F uw (Band X operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| F uw (Band XI operation) | MHz | $1468.4 \leq f \leq 1503.4$ | $1460.9 \leq f \leq 1510.9$ | | | +| F uw (Band XII operation) | MHz | $721.4 \leq f \leq 753.6$ | $714 \leq f \leq 761$ | | | +| F uw (Band XIII operation) | MHz | $738.4 \leq f \leq 763.6$ | $731 \leq f \leq 771$ | | | +| F uw (Band XIV operation) | MHz | $750.4 \leq f \leq 775.6$ | $743 \leq f \leq 783$ | | | +| F uw (Band XIX operation) | MHz | $867.4 \leq f \leq 897.6$ | $860 \leq f \leq 905$
(NOTE 2) | | | +| F uw (Band XX operation) | MHz | $783.4 \leq f \leq 828.6$ | $776 \leq f \leq 836$
(NOTE 2) | | | +| F uw (Band XXI operation) | MHz | $1488.4 \leq f \leq 1518.4$ | $1480.9 \leq f \leq 1525.9$
(NOTE 2) | | | +| F uw (Band XXII operation) | MHz | $3502.4 \leq f \leq 3597.6$ | $3495 \leq f \leq 3605$ | | | +| F uw (Band XXV operation) | MHz | $1922.4 \leq f \leq 2002.6$ | $1915 \leq f \leq 2010$ | | | +| F uw (Band XXVI operation) | MHz | $851.4 \leq f \leq 901.6$ | $844 \leq f \leq 909$ | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 4 | | | | +| NOTE 1: I blocking (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For Band VI, Band XIX and Band XXI, the unwanted interfering signal does not fall inside the UE receive band, but within the first 15 MHz below or above the UE receive band. | | | | | | +| NOTE 3: For DC-HSUPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. | | | | | | +| NOTE 4: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | | | + +**Table 7.6C: Reference input powers for in-band blocking, DC-HSUPA.** + +| Operating Band | Unit | HS-PDSCH_Ec | $\hat{I}_{or}$ | +|----------------|--------------|-------------|----------------| +| I | dBm/3.84 MHz | -110 | -99.7 | +| II | dBm/3.84 MHz | -108 | -97.7 | +| III | dBm/3.84 MHz | -107 | -96.7 | +| IV | dBm/3.84 MHz | -110 | -99.7 | +| V | dBm/3.84 MHz | -104.3 | -94 | +| VI | dBm/3.84 MHz | -104.7 | -94.4 | +| VII | dBm/3.84 MHz | -108 | -97.7 | +| VIII | dBm/3.84 MHz | -101.1 | -90.8 | +| IX | dBm/3.84 MHz | -109 | -98.7 | +| X | dBm/3.84 MHz | -110 | -99.7 | +| XI | dBm/3.84 MHz | -101.4 | -91.1 | +| XII | dBm/3.84 MHz | N/A | N/A | +| XIII | dBm/3.84 MHz | N/A | N/A | +| XIV | dBm/3.84 MHz | N/A | N/A | +| XIX | dBm/3.84 MHz | -104.7 | -94.4 | +| XX | dBm/3.84 MHz | N/A | N/A | +| XXI | dBm/3.84 MHz | -101.4 | -91.1 | +| XXII | dBm/3.84 MHz | -107 | -96.7 | +| XXV | dBm/3.84 MHz | -106.5 | -96.2 | +| XXVI | dBm/3.84 MHz | -101.1 | -90.8 | + +NOTE 1 For the UE which supports both Band III and Band IX operating frequencies, the reference sensitivity level of TBD dBm $\langle \text{REF\_Ec,in-band} \rangle$ shall apply for Band IX. The corresponding $\langle \text{REF\_I}_{or,in-band} \rangle$ is TBD dBm + +NOTE 2 For the UE which supports both Band XI and Band XXI operating frequencies, the reference input power level is FFS. + +NOTE 3 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{or} \rangle$ are allowed to be increased by an amount defined in Table 7.12. + +NOTE 4 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{or} \rangle$ are allowed to be increased by an amount defined in Table 7.13. + +## 7.6.1C Additional requirement for single band 4C-HSDPA (In-band blocking) + +### 7.6.1C.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6D and Table 7.6E. In-band blocking 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. + +**Table 7.6D: Test parameters for in-band blocking, single band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.6E: In-band blocking requirements, single band 4C-HSDPA, single uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|----------------------------------------|--------------------------| +| I-3 | I | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | +| II-3, II-4 | II | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | +| NOTE: $<\text{REFSENS}>$ and $<\text{REF}\hat{I}_{\text{or}}>$ refer to the HS-PDSCH_Ec $<\text{REFSENS}>$ and the HS-PDSCH $<\text{REF}\hat{I}_{\text{or}}>$ as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +### 7.6.1C.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6F and Table 7.6G. In-band blocking 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. + +**Table 7.6F: Test parameters for in-band blocking, single band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.6G: In-band blocking requirements, single band 4C-HSDPA, dual uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|------------------------------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-3 | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-3, II-4 | II | -108 | -97.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{or} \rangle$ are allowed to be increased by an amount defined in Table 7.12. + +NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{or} \rangle$ are allowed to be increased by an amount defined in Table 7.13. + +## 7.6.1D Additional requirement for dual band 4C-HSDPA (In-band blocking) + +### 7.6.1D.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6H and Table 7.6I. In-band blocking 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. + +**Table 7.6H: Test parameters for in-band blocking, dual band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|----------------------------------------------|------|-----------------------------------------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $= \pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| $F_{\text{uw}}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | +| $F_{\text{uw}}$ (Band V operation) | MHz | $861.4 \leq f \leq 901.6$ | $854 \leq f \leq 909$ | +| $F_{\text{uw}}$ (Band VIII operation) | MHz | $917.4 \leq f \leq 967.6$ | $910 \leq f \leq 975$ | +| $F_{\text{uw}}$ (Band XXXII operation) | MHz | $1444.4 \leq f \leq 1503.6$ | $1437 \leq f \leq 1511$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | + +NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. + +NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. + +**Table 7.6I: In-band blocking requirements, dual band 4C-HSDPA, single uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|----------------------------------|---------|---------|---------------------------|------------------------------|--------------------------| +| I-2-VIII-1 | I | I | +3 dB | +3 dB | Minimum | +| I-3-VIII-1 | VIII | | +3 dB | +3 dB | Minimum | +| I-2-VIII-2 | I | VIII | +3 dB | +3 dB | Minimum | +| I-1-VIII-2 | VIII | | +3 dB | +3 dB | Minimum | +| II-1-IV-2 | II | II | +3 dB | +3 dB | Minimum | +| II-2-IV-1 | IV | | +3 dB | +3 dB | Minimum | +| II-2-IV-2 | II | IV | +3 dB | +3 dB | Minimum | +| | IV | | +3 dB | +3 dB | Minimum | +| I-1-V-2 | I | I | +3 dB | +3 dB | Minimum | +| I-2-V-1 | V | | +3 dB | +3 dB | Minimum | +| I-2-V-2 | I | V | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| II-1-V-2 | II | II | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| | II | V | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| I-1-XXXII-2 | I | I | +3 dB | +3 dB | Minimum | +| I-2-XXXII-1 | XXXII | | +3 dB | +3 dB | Minimum | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2D for dual band 4C-HSDPA. + +### 7.6.1D.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6J and Table 7.6K. In-band blocking 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. + +**Table 7.6J: Test parameters for in-band blocking, dual band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $= \pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| $F_{\text{uw}}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | +| $F_{\text{uw}}$ (Band V operation) | MHz | $861.4 \leq f \leq 901.6$ | $854 \leq f \leq 909$ | +| $F_{\text{uw}}$ (Band VIII operation) | MHz | $917.4 \leq f \leq 967.6$ | $910 \leq f \leq 975$ | +| $F_{\text{uw}}$ (Band XXXII operation) | MHz | $1444.4 \leq f \leq 1503.6$ | $1437 \leq f \leq 1511$ | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | +| NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. | | | | + +**Table 7.6K: In-band blocking requirements, dual band 4C-HSDPA, dual uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|----------------------------------|---------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1 | I | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-VIII-2 | I | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | I | VIII | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -99.7 | -89.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-VIII-2 | I | VIII | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -99.7 | -89.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-IV-2 | II | IV | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -109 | -98.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-1 | II | II | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -109 | -98.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-2 | II | II | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -109 | -98.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | II | IV | -107 | -96.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -109 | -98.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-V-2 | I | V | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -103.2 | -92.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-1 | I | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -108 | -97.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-2 | I | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -108 | -97.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | I | V | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -103.2 | -92.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-V-2 | II | V | -108 | -97.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -103.1 | -92.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-XXXII-1 | I | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | XXXII | | -110 | -99.7 | 20 (for Power class 3 and 3bis) | | + +| | | | | | | | +|--|--|--|--|--|------------------------|--| +| | | | | | 18 (for Power class 4) | | +|--|--|--|--|--|------------------------|--| + +## 7.6.1E Additional requirement for single band 8C-HSDPA (In-band blocking) + +### 7.6.1E.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6L and Table 7.6M. In-band blocking 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. + +**Table 7.6L: Test parameters for in-band blocking, single band 8C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 8C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency, and positive offset refers to the assigned channel frequency of the highest carrier frequency. | | | | + +**Table 7.6M: In-band blocking requirements, single band 8C-HSDPA, single uplink operation** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|----------------------------------------|--------------------------| +| I-8 | I | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | +| NOTE: $<\text{REFSENS}>$ and $<\text{REF}\hat{I}_{\text{or}}>$ refer to the HS-PDSCH_Ec $<\text{REFSENS}>$ and the HS-PDSCH $<\text{REF}\hat{I}_{\text{or}}>$ as specified in Table 7.2E for single band 8C-HSDPA. | | | | | + +### 7.6.1E.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6N and Table 7.6O. In-band blocking 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. + +**Table 7.6N: Test parameters for in-band blocking, single band 8C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------|--------------------------------------| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44 | +| $F_{\text{uw}}$ offset (NOTE 2) | | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | +| $F_{\text{uw}}$ (Band II operation) | MHz | $1922.4 \leq f \leq 1997.6$ | $1915 \leq f \leq 2005$ | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 8C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency, and positive offset refers to the assigned channel frequency of the highest carrier frequency. | | | | + +**Table 7.6O: In-band blocking requirements, single band 8C-HSDPA, dual uplink operation** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|-------------------------------------|-----------------------------------------------------------|--------------------------| +| I-8 | I | -110 | -99.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{\text{or}} \rangle$ are allowed to be increased by an amount defined in Table 7.12. | | | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{\text{or}} \rangle$ are allowed to be increased by an amount defined in Table 7.13. | | | | | | + +## 7.6.1F Additional requirement for single band NC-4C-HSDPA (In-band blocking) + +### 7.6.1F.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6P and Table 7.6Q. In-band blocking 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. + +**Table 7.6P: Test parameters for in-band blocking, single band NC-4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|--------------------------------------|--|--| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44
(NOTE 4) | | | +| $F_{\text{uw}}$ offset (NOTE 2,3) | MHz | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | | | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{\text{uw}}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | | | +| NOTE 3: For single band NC-4C-HSPDA in-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the higher subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the lower subblock of carriers. | | | | | | +| NOTE 4: The $I_{\text{blocking}}$ (modulated) interferer with mean power equals to -44dBm is only applicable for scenario with gap length $\geq 25$ MHz. | | | | | | + +**Table 7.6Q: In-band blocking requirements, single band NC-4C-HSDPA, single uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------|------------|---------|---------------------------|----------------------------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | Out-of-gap | I | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | +| IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | $<\text{REFSENS}>+3$ dB | $<\text{REF}\hat{I}_{\text{or}}>+3$ dB | Minimum | + +NOTE: $<\text{REFSENS}>$ and $<\text{REF}\hat{I}_{\text{or}}>$ refer to the HS-PDSCH\_Ec $<\text{REFSENS}>$ and the HS-PDSCH $<\text{REF}\hat{I}_{\text{or}}>$ as specified in Table 7.2E for single band NC-4C-HSDPA. + +### 7.6.1F.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.6R and Table 7.6S. In-band blocking 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. + +**Table 7.6R: Test parameters for in-band blocking, single band NC-4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|--------------------------------------|--|--| +| $I_{\text{blocking}}$ mean power (modulated) | dBm | -56 | -44
(NOTE 4) | | | +| $F_{\text{uw}}$ offset (NOTE 2,3) | MHz | $=\pm 10$ MHz | $\leq -15$ MHz
&
$\geq 15$ MHz | | | +| $F_{\text{uw}}$ (Band I operation) | MHz | $2102.4 \leq f \leq 2177.6$ | $2095 \leq f \leq 2185$ | | | +| $F_{\text{uw}}$ (Band IV operation) | MHz | $2102.4 \leq f \leq 2162.6$ | $2095 \leq f \leq 2170$ | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| NOTE 1: $I_{\text{blocking}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | | | +| NOTE 3: For single band NC-4C-HSPDA in-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the higher subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the lower subblock of carriers. | | | | | | +| NOTE 4: The $I_{\text{blocking}}$ (modulated) interferer with mean power equals to -44dBm is only applicable for scenario with gap length $\geq 25$ MHz. | | | | | | + +**Table 7.6S: In-band blocking requirements, single band NC-4C-HSDPA, dual uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------|---------------------------|-------------------------------------|--------------------------| +| I-2-5-1, I-3-10-1 | Out-of-gap | I | -110 | -99.7 | Minimum | +| IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | -110 | -99.7 | Minimum | +| IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | -110 | -99.7 | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{\text{or}}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{\text{or}}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | | | + +## 7.6.2 Minimum requirement (Out-of-band blocking) + +The BER shall not exceed 0.001 for the parameters specified in Table 7.7. Out-of-band blocking is defined for an unwanted interfering signal falling more than 15 MHz below or above the UE receive band. + +For Table 7.7 in frequency range 1, 2 and 3, up to 24 exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7 in frequency range 4, up to 8 exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable + +**Table 7.7: Out of band blocking** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | | | | | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|--------------------------------------|------------------------------|--|--|--|--| +| DPCH_Ec | dBm / 3.84 MHz | +3 dB | +3 dB | +3 dB | +3 dB | | | | | +| $\hat{I}_{or}$ | dBm / 3.84 MHz | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | | | | +| $I_{blocking}$ (CW) | dBm | -44 | -30 | -15 | -15 | | | | | +| $F_{uw}$ (Band I operation) | MHz | 205021852230 ≤ f <2255 | 1< f ≤ 2025
2255≤f<12750 | - | | | | | +| $F_{uw}$ (Band II operation) | MHz | 187020052050 ≤ f <2075 | 1< f ≤ 1845
2075≤f<12750 | 1850 ≤ f ≤ 1910 | | | | | +| $F_{uw}$ (Band III operation) | MHz | 1745 18951940≤f < 1965 | 1< f ≤ 1720
1965≤f<12750 | - | | | | | +| $F_{uw}$ (Band IV operation) | MHz | 205021702215≤ f < 2240 | 1< f ≤ 2025
2240≤f<12750 | - | | | | | +| $F_{uw}$ (Band V operation) | MHz | 809909954≤ f < 979 | 1< f ≤ 784
979≤f<12750 | 824 ≤ f ≤ 849 | | | | | +| $F_{uw}$ (Band VI operation) | MHz | 815 < f < 860
900 < f < 945 | 790 < f ≤ 815
945 ≤ f < 970 | 1 < f ≤ 790
970 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band VII operation) | MHz | 2570 < f < 2605
2705 < f < 2750 | na
2750 ≤ f < 2775 | 1 < f ≤ 2570
2775 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band VIII operation) | MHz | 865 < f < 910
975 < f < 1020 | 840 < f ≤ 865
1020 ≤ f < 1045 | 1 < f ≤ 840
1045 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band IX operation) | MHz | 1784.9 < f < 1829.9
1894.9 < f < 1939.9 | 1759.9 < f ≤ 1784.9
1939.9 ≤ f < 1964.9 | 1 < f ≤ 1759.9
1964.9 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band X operation) | MHz | 2050 < f < 2095
2185 < f < 2230 | 2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 2025
2255 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band XI operation) | MHz | 1415.9 < f < 1460.9
1510.9 < f < 1555.9 | 1390.9 < f ≤ 1415.9
1555.9 ≤ f < 1580.9 | 1 < f ≤ 1390.9
1580.9 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band XII operation) | MHz | 669 < f < 714
761 < f < 806 | 644 < f ≤ 669
806 ≤ f < 831 | 1 < f ≤ 644
831 ≤ f < 12750 | 699 ≤ f ≤ 716 | | | | | +| $F_{uw}$ (Band XIII operation) | MHz | 686 < f < 731
771 < f < 816 | 61 < f ≤ 686
816 ≤ f < 841 | 1 < f ≤ 661
841 ≤ f < 12750 | 776 ≤ f ≤ 788 | | | | | +| $F_{uw}$ (Band XIV operation) | MHz | 698 < f < 743
783 < f < 828 | 673 < f ≤ 698
828 ≤ f < 853 | 1 < f ≤ 673
853 ≤ f < 12750 | 788 ≤ f ≤ 798 | | | | | +| $F_{uw}$ (Band XIX operation) | MHz | 815 < f < 860
905 < f < 950 | 790 < f ≤ 815
950 ≤ f < 975 | 1 < f ≤ 790
975 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band XX operation) | MHz | 731836881 ≤ f < 906 | 1 < f ≤ 706
906 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band XXI operation) | MHz | 1435.9 < f < 1480.9
1525.9 < f < 1570.9 | 1410.9 < f ≤ 1435.9
1570.9 ≤ f < 1595.9 | 1 < f ≤ 1410.9
1595.9 ≤ f < 12750 | - | | | | | +| $F_{uw}$ (Band XXII operation) | MHz | 3450 < f < 3495
36053650≤f < 3675 | 1< f ≤ 3425
3675≤f<12750 | - | | | | | +| $F_{uw}$ (Band XXV operation) | MHz | 187020102055 ≤ f <2080 | 1< f ≤ 1845
2080≤f<12750 | 1850 ≤ f ≤ 1915 | | | | | +| $F_{uw}$ (Band XXVI operation) | MHz | 799909954≤ f < 979 | 1< f ≤ 774
979 ≤ f < 12750 | 814 ≤ f ≤ 849 | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | | | | | | | | +| Band I operation | For 2095≤f ≤2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | | | | | | | | | +| Band II operation | For 1915≤f ≤2005 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied | | | | | | | | | +| Band III operation | For 1790≤f ≤1895 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | | | | | | | | | +| Band IV operation | For 2095≤f≤2170 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | | | | | | | | | + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Band V operation | For $854 \leq f \leq 909$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band VI operation | For $860 \leq f \leq 900$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band VII operation | For $2605 \leq f \leq 2705$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band VIII operation | For $910 \leq f \leq 975$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band IX operation | For $1829.9 \leq f \leq 1894.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band X operation | For $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XI operation | For $1460.9 \leq f \leq 1510.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XII operation | For $714 \leq f \leq 761$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XIII operation | For $731 \leq f \leq 771$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XIV operation | For $743 \leq f \leq 783$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XIX operation | For $860 \leq f \leq 905$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XX operation | For $776 \leq f \leq 836$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XXI operation | For $1480.9 \leq f \leq 1525.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | +| Band XXII operation | For $3495 \leq f \leq 3605$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. NOTE 3 | +| Band XXV operation | For $1915 \leq f \leq 2010$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied | +| Band XXVI operation | For $844 \leq f \leq 909$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. | + +NOTE 1: and refer to the DPCH\_Ec and the DPCH as specified in Table 7.2. + +NOTE 2: For the UE which supports both Band XI and Band XXI operating frequencies, the Out of band blocking is FFS. + +NOTE 3: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. + +## 7.6.2A Additional requirement for DC-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AA. Out-of-band band blocking is defined for an unwanted interfering signal falling more than 15 MHz below or above the UE receive band. + +For Table 7.7AA in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7AA in frequency range 4, up to 8 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +**Table 7.7AA: Out of band blocking for DC-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|--------------------------------------|------------------------------| +| HS-PDSCH_Ec | dBm /
3.84 MHz | +3 dB | +3 dB | +3 dB | +3 dB | +| $\hat{I}_{or}$ | dBm /
3.84 MHz | + 3 dB | + 3 dB | + 3 dB | + 3 dB | +| I blocking (CW) | dBm | -44 | -30 | -15 | -15 | +| $F_{uw}$
(Band I operation) | MHz | 2050 < f < 2095
2185 < f < 2230 | 2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 2025
2255 ≤ f < 12750 | - | +| $F_{uw}$
(Band II operation) | MHz | 1870 < f < 1915
2005 < f < 2050 | 1845 < f ≤ 1870
2050 ≤ f < 2075 | 1 < f ≤ 1845
2075 ≤ f < 12750 | 1850 ≤ f ≤ 1910 | +| $F_{uw}$
(Band III operation) | MHz | 1745 < f < 1790
1895 < f < 1940 | 1720 < f ≤ 1745
1940 ≤ f < 1965 | 1 < f ≤ 1720
1965 ≤ f < 12750 | - | +| $F_{uw}$
(Band IV operation) | MHz | 2050 < f < 2095
2170 < f < 2215 | 2025 < f ≤ 2050
2215 ≤ f < 2240 | 1 < f ≤ 2025
2240 ≤ f < 12750 | - | +| $F_{uw}$
(Band V operation) | MHz | 809 < f < 854
909 < f < 954 | 784 < f ≤ 809
954 ≤ f < 979 | 1 < f ≤ 784
979 ≤ f < 12750 | 824 ≤ f ≤ 849 | +| $F_{uw}$
(Band VI operation) | MHz | 815 < f < 860
900 < f < 945 | 790 < f ≤ 815
945 ≤ f < 970 | 1 < f ≤ 790
970 ≤ f < 12750 | - | +| $F_{uw}$
(Band VII operation) | MHz | 2570 < f < 2605
2705 < f < 2750 | na
2750 ≤ f < 2775 | 1 < f ≤ 2570
2775 ≤ f < 12750 | - | +| $F_{uw}$
(Band VIII operation) | MHz | 865 < f < 910
975 < f < 1020 | 840 < f ≤ 865
1020 ≤ f < 1045 | 1 < f ≤ 840
1045 ≤ f < 12750 | - | +| $F_{uw}$
(Band IX operation) | MHz | 1784.9 < f < 1829.9
1894.9 < f < 1939.9 | 1759.9 < f ≤ 1784.9
1939.9 ≤ f < 1964.9 | 1 < f ≤ 1759.9
1964.9 ≤ f < 12750 | - | +| $F_{uw}$
(Band X operation) | MHz | 2050 < f < 2095
2185 < f < 2230 | 2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 2025
2255 ≤ f < 12750 | - | +| $F_{uw}$
(Band XI operation) | MHz | 1415.9 < f < 1460.9
1510.9 < f < 1555.9 | 1390.9 < f ≤ 1415.9
1555.9 ≤ f < 1580.9 | 1 < f ≤ 1390.9
1580.9 ≤ f < 12750 | - | +| $F_{uw}$
(Band XII operation) | MHz | 669 < f < 714
761 < f < 806 | 643 < f ≤ 669
806 ≤ f < 831 | 1 < f ≤ 644
831 ≤ f < 12750 | 699 ≤ f ≤ 716 | +| $F_{uw}$
(Band XIII operation) | MHz | 686 < f < 731
771 < f < 816 | 61 < f ≤ 686
816 ≤ f < 841 | 1 < f ≤ 661
841 ≤ f < 12750 | 776 ≤ f ≤ 788 | +| $F_{uw}$
(Band XIV operation) | MHz | 698 < f < 743
783 < f < 828 | 673 < f ≤ 698
828 ≤ f < 853 | 1 < f ≤ 673
853 ≤ f < 12750 | 788 ≤ f ≤ 798 | +| $F_{uw}$
(Band XIX operation) | MHz | 815 < f < 860
905 < f < 950 | 790 < f ≤ 815
950 ≤ f < 975 | 1 < f ≤ 790
975 ≤ f < 12750 | - | +| $F_{uw}$
(Band XX operation) | MHz | 731 < f < 776
836 < f < 881 | 706 < f ≤ 731
881 ≤ f < 906 | 1 < f ≤ 706
906 ≤ f < 12750 | - | +| $F_{uw}$
(Band XXI operation) | MHz | 1435.9 < f < 1480.9
1525.9 < f < 1570.9 | 1410.9 < f ≤ 1435.9
1570.9 ≤ f < 1595.9 | 1 < f ≤ 1410.9
1595.9 ≤ f < 12750 | - | +| $F_{uw}$
(Band XXII operation) | MHz | 3450 < f < 3495
3605 < f < 3650 | 3425 < f ≤ 3450
3650 ≤ f < 3675 | 1 < f ≤ 3425
3675 ≤ f < 12750 | - | +| $F_{uw}$
(Band XXV operation) | MHz | 1870 < f < 1915
2010 < f < 2055 | 1845 < f ≤ 1870
2055 ≤ f < 2080 | 1 < f ≤ 1845
2080 ≤ f < 12750 | 1850 ≤ f ≤ 1915 | +| $F_{uw}$
(Band XXVI operation) | MHz | 799 < f < 844
909 < f < 954 | 774 < f ≤ 799
954 ≤ f < 979 | 1 < f ≤ 774
979 ≤ f < 12750 | 814 ≤ f ≤ 849 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | | | | +| Band I operation | For 2095 ≤ f ≤ 2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | +| Band II operation | For 1915 ≤ f ≤ 2005 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied | | | | | +| Band III operation | For 1790 ≤ f ≤ 1895 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | +| Band IV operation | For 2095 ≤ f ≤ 2170 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | + +| | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Band V operation | For $854 \leq f \leq 909$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band VI operation | For $860 \leq f \leq 900$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band VII operation | For $2605 \leq f \leq 2705$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band VIII operation | For $910 \leq f \leq 975$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band IX operation | For $1829.9 \leq f \leq 1894.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band X operation | For $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XI operation | For $1460.9 \leq f \leq 1510.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XII operation | For $714 \leq f \leq 761$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XIII operation | For $731 \leq f \leq 771$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XIV operation | For $743 \leq f \leq 783$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XIX operation | For $860 \leq f \leq 905$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XX operation | For $776 \leq f \leq 836$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XXI operation | For $1480.9 \leq f \leq 1525.9$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | +| Band XXII operation | For $3495 \leq f \leq 3605$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. NOTE 3 | +| Band XXV operation | For $1915 \leq f \leq 2010$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied | +| Band XXVI operation | For $844 \leq f \leq 909$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | + +NOTE 1: and refer to the DPCH\_Ec and the DPCH as specified in Table 7.2A. + +NOTE 2: For the UE which supports both Band XI and Band XXI operating frequencies, the Out of band blocking is FFS. + +NOTE 3: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. + +## 7.6.2B Additional requirement for DB-DC-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AB. Out-of-band blocking is defined for an unwanted interfering signal falling at frequencies outside of frequency regions defined as the UE receive bands extended by 15 MHz at their lower and upper ends. For Table 7.7AB in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7AB in frequency range 4, up to 8 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +**Table 7.7AB: Out of band blocking for DB-DC-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | | | | | +|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------|--|--|--|--| +| HS-PDSCH_Ec | dBm / 3.84 MHz | +3 dB | +3 dB | +3 dB | +3 dB | | | | | +| $\hat{I}_{or}$ | dBm / 3.84 MHz | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | | | | +| $I_{blocking}$ (CW) | dBm | -44 | -30 | -15 | -15 | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 1) | MHz | 865 < f < 910
975 < f < 1020
2050 < f < 2095
2185 < f < 2230 | 840 < f ≤ 865
1020 ≤ f < 1045
2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 840
1045 ≤ f < 2025
2255 < f ≤ 12750 | - | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 2) | MHz | 1870 < f < 1915
2005 < f < 2095
2170 < f < 2215 | 1845 < f ≤ 1870
2215 ≤ f < 2240 | 1 < f ≤ 1845
2240 ≤ f < 12750 | 1850 ≤ f ≤ 1910 | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 3) | MHz | 809 < f < 854
909 < f < 954
2050 < f < 2095
2185 < f < 2230 | 784 < f ≤ 809
954 ≤ f < 979
2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 784
979 ≤ f < 2025
2255 < f ≤ 12750 | 824 ≤ f ≤ 849 | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 4) | MHz | 1415.9 < f < 1460.9
1510.9 < f < 1555.9
2050 < f < 2095
2185 < f < 2230 | 1390.9 < f ≤ 1415.9
1555.9 ≤ f < 1580.9
2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 1390.9
1580.9 ≤ f < 2025
2255 < f ≤ 12750 | - | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 5) | MHz | 809 < f < 854
909 < f < 954
1870 < f < 1915
2005 < f < 2050 | 784 < f ≤ 809
954 ≤ f < 979
1845 < f ≤ 1870
2050 ≤ f < 2075 | 1 < f ≤ 784
979 < f ≤ 1845
2075 < f ≤ 12750 | 824 ≤ f ≤ 849
1850 ≤ f ≤ 1910 | | | | | +| $F_{uw}$
(DB-DC-HSDPA Configuration 6) | MHz | 1392 < f < 1437
1511 < f < 1556
2050 < f < 2095
2185 < f < 2230 | 1367 < f ≤ 1392
1556 ≤ f < 1581
2025 < f ≤ 2050
2230 ≤ f < 2255 | 1 < f ≤ 1367
1581 ≤ f < 2025
2255 < f ≤ 12750 | - | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | | | | | +| DB-DC-HSDPA Configuration 1 | For 910 ≤ f ≤ 975 MHz and 2095 ≤ f ≤ 2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | +| DB-DC-HSDPA Configuration 2 | For 1915 ≤ f ≤ 2005 MHz and 2095 ≤ f ≤ 2070 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | +| DB-DC-HSDPA Configuration 3 | For 854 ≤ f ≤ 909 MHz and 2095 ≤ f ≤ 2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | +| DB-DC-HSDPA Configuration 4 | For 1460.9 ≤ f ≤ 1510.9 MHz and 2095 ≤ f ≤ 2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | +| DB-DC-HSDPA Configuration 5 | For 854 ≤ f ≤ 909 MHz and 1915 ≤ f ≤ 2005 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | +| DB-DC-HSDPA Configuration 6 | For 1437 ≤ f ≤ 1511 MHz and 2095 ≤ f ≤ 2185 MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1A shall be applied. | | | | | | | | | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2B. + +## 7.6.2C Additional requirement for single band 4C-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AC and Table 7.7AD. Out-of-band band blocking is defined for an unwanted interfering signal falling more than 15 MHz below or above the UE receive band. The requirement is not applicable for dual uplink operation. + +For Table 7.7AC in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7AC in frequency range 4, up to 8 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +**Table 7.7AC: Test parameters for out of band blocking, single band 4C-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | | | | | +|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------|--------------------------------------------|-------------------------|--|--|--|--| +| $I_{\text{blocking}}$ (CW) | dBm | -44 | -30 | -15 | -15 | | | | | +| $F_{\text{uw}}$
(Single band 4C-HSDPA Configuration I-3) | MHz | $2050 < f < 2095$
$2185 < f < 2230$ | $2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 2025$
$2255 \leq f < 12750$ | - | | | | | +| $F_{\text{uw}}$
(Single band 4C-HSDPA Configuration II-3, II-4) | MHz | $1870 < f < 1915$
$2005 < f < 2050$ | $1845 < f \leq 1870$
$2050 \leq f < 2075$ | $1 < f \leq 1845$
$2075 \leq f < 12750$ | $1850 \leq f \leq 1910$ | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | | | | | +| Single band 4C-HSDPA Configuration I-3 | For $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.3 and subclause 7.6.1C.1 shall be applied. | | | | | | | | | +| Single band 4C-HSDPA Configuration II-3, II-4 | For $1915 \leq f \leq 2005$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.3 and subclause 7.6.1C.1 shall be applied. | | | | | | | | | + +**Table 7.7AD: Out of band blocking requirements, single band 4C-HSDPA** + +| Single band 4C-HSDPA Configuration | Parameter | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | UL-DL carrier separation | +|------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|--------------------------| +| I-3 | HS-PDSCH_Ec (dBm/3.84MHz) |
+3 dB |
+3 dB |
+3 dB |
+3 dB | Minimum | +| | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | +| II-3, II-4 | HS-PDSCH_Ec (dBm/3.84MHz) |
+3 dB |
+3 dB |
+3 dB |
+3 dB | Minimum | +| | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2C. + +## 7.6.2D Additional requirement for dual band 4C-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AE and Table 7.7AF. Out-of-band blocking is defined for an unwanted interfering signal falling at frequencies outside of frequency regions defined as the UE receive bands extended by 15 MHz at their lower and upper ends. The requirement is not applicable for dual uplink operation. + +For Table 7.7AF in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7AF in frequency range 4, up to 8 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +**Table 7.7AE: Test parameters for out of band blocking, dual band 4C-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | | | | | +|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------------------------------|--|--|--|--| +| $I_{\text{blocking}}$ (CW) | dBm | -44 | -30 | -15 | -15 | | | | | +| $F_{\text{uw}}$
(Dual band 4C-HSDPA Configuration I-2-VIII-1, I-3-VIII-1, I-2-VIII-2, I-1-VIII-2) | MHz | $865 < f < 910$
$975 < f < 1020$
$2050 < f < 2095$
$2185 < f < 2230$ | $840 < f \leq 865$
$1020 \leq f < 1045$
$2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 840$
$1045 \leq f < 2025$
$2255 < f \leq 12750$ | - | | | | | +| $F_{\text{uw}}$
(Dual band 4C-HSDPA Configuration II-1-IV-2, II-2-IV-1, II-2-IV-2) | MHz | $1870 < f < 1915$
$2005 < f < 2095$
$2170 < f < 2215$ | $1845 < f \leq 1870$
$2215 \leq f < 2240$ | $1 < f \leq 1845$
$2240 \leq f < 12750$ | $1850 \leq f \leq 1910$ | | | | | +| $F_{\text{uw}}$
(Dual band 4C-HSDPA Configuration I-1-V-2, I-2-V-1, I-2-V-2) | MHz | $809 < f < 854$
$909 < f < 954$
$2050 < f < 2095$
$2185 < f < 2230$ | $784 < f \leq 809$
$954 \leq f < 979$
$2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 784$
$979 \leq f < 2025$
$2255 < f \leq 12750$ | $824 \leq f \leq 849$ | | | | | +| $F_{\text{uw}}$
(Dual band 4C-HSDPA Configuration II-1-V-2) | MHz | $809 < f < 854$
$909 < f < 954$
$1870 < f < 1915$
$2005 < f < 2050$ | $784 < f \leq 809$
$954 \leq f < 979$
$1845 < f \leq 1870$
$2050 \leq f < 2075$ | $1 < f \leq 784$
$979 \leq f < 1845$
$2075 < f \leq 12750$ | $824 \leq f \leq 849$ ,
$1850 \leq f \leq 1910$ | | | | | +| $F_{\text{uw}}$
(Dual band 4C-HSDPA Configuration I-1-XXXII-2, I-2-XXXII-1) | MHz | $1392 < f < 1437$
$1511 < f < 1556$
$2050 < f < 2095$
$2185 < f < 2230$ | $1367 < f \leq 1392$
$1556 \leq f < 1581$
$2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 1367$
$1581 \leq f < 2025$
$2255 < f \leq 12750$ | - | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | | | | | +| Dual band 4C-HSDPA Configuration I-2-VIII-1, I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | For $910 \leq f \leq 975$ MHz and $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1D.1 shall be applied. | | | | | | | | | +| Dual band 4C-HSDPA Configuration II-1-IV-2, II-2-IV-1, II-2-IV-2 | For $1915 \leq f \leq 2005$ MHz and $2095 \leq f \leq 2070$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1D.1 shall be applied. | | | | | | | | | +| Dual band 4C-HSDPA Configuration I-1-V-2, I-2-V-1, I-2-V-2 | For $854 \leq f \leq 909$ MHz and $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1D.1 shall be applied. | | | | | | | | | +| Dual band 4C-HSDPA Configuration II-1-V-2 | For $854 \leq f \leq 909$ MHz and $1915 \leq f \leq 2005$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1D.1 shall be applied. | | | | | | | | | +| Dual band 4C-HSDPA Configuration I-1-XXXII-2, I-2-XXXII-1 | For $1437 \leq f \leq 1511$ MHz and $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.2 and subclause 7.6.1D.1 shall be applied. | | | | | | | | | + +**Table 7.7AF: Out of band blocking requirements, dual band 4C-HSDPA** + +| Dual band 4C-HSDPA Configuration n | DL Band | UL Band | Parameter | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | UL-DL carrier separation | +|------------------------------------------------------|---------|---------|------------------------------|------------------------------|------------------------------|------------------------------|------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1
I-2-VIII-2
I-1-VIII-2 | I | I | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | VIII | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| | I | VIII | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | VIII | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | II | II | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | IV | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| | II | IV | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | IV | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| I-1-V-2
I-2-V-1
I-2-V-2 | I | I | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | V | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| | I | V | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | V | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| II-1-V-2 | II | II | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | V | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| | II | V | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | V | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | Minimum | +| I-1-XXXII-2
I-2-XXXII-1 | I | I | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | +3 dB | Minimum | +| | XXXII | | $\hat{I}_{or}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2D. + +## 7.6.2E Additional requirement for single band 8C-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AG and Table 7.7AH. Out-of-band band blocking is defined for an unwanted interfering signal falling more than 15 MHz below or above the UE receive band. The requirement is not applicable for dual uplink operation. + +For Table 7.7AG in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +For Table 7.7AG in frequency range 4, up to 8 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 Spurious response are applicable. + +**Table 7.7AG: Test parameters for out of band blocking, single band 8C-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | +|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------|--------------------------------------------|-------------------| +| $I_{\text{blocking}}$ (CW) | dBm | -44 | -30 | -15 | -15 | +| $F_{\text{uw}}$
(Single band 8C-HSDPA Configuration I-8) | MHz | $2050 < f < 2095$
$2185 < f < 2230$ | $2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 2025$
$2255 \leq f < 12750$ | - | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| Single band 8C-HSDPA Configuration I-8 | For $2095 \leq f \leq 2185$ MHz, the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.4 and subclause 7.6.1E.1 shall be applied. | | | | | + +**Table 7.7AH: Out of band blocking requirements, single band 8C-HSDPA** + +| Singe band 8C-HSDPA Configuration | Parameter | Frequency range 1 | Frequency range 2 | Frequency range 3 | Frequency range 4 | UL-DL carrier separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|--------------------------| +| I-8 | HS-PDSCH_Ec (dBm/3.84MHz) |
+3 dB |
+3 dB |
+3 dB |
+3 dB | Minimum | +| | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | + 3 dB | | +| NOTE: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2E. | | | | | | | + +## 7.6.2F Additional requirement for single band NC-4C-HSDPA (Out-of-band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7AI and Table 7.7AJ. Out-of-band band blocking is defined for an unwanted interfering signal falling more than 15 MHz below or above the UE receive band. The requirement is not applicable for dual uplink operation. + +For Table 7.7AI in frequency range 1, 2 and 3, up to 24 exceptions per received cell are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1 MHz step size. For these exceptions the requirements of clause 7.7 spurious response are applicable. + +**Table 7.7AI: Test parameters for out of band blocking, single band NC-4C-HSDPA** + +| Parameter | Unit | Frequency range 1 | Frequency range 2 | Frequency range 3 | +|-----------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|----------------------------------------------|--------------------------------------------| +| $I_{\text{blocking}}$ (CW) | dBm | -44 | -30 | -15 | +| $F_{\text{uw}}$
(Single band NC-4C-HSDPA Configuration I-1-5-1, I-2-5-1, I-3-10-1) | MHz | $2050 < f < 2095$
$2185 < f < 2230$ | $2025 < f \leq 2050$
$2230 \leq f < 2255$ | $1 < f \leq 2025$
$2255 \leq f < 12750$ | +| $F_{\text{uw}}$
(Single band NC-4C-HSDPA Configuration IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2) | MHz | $2050 < f < 2095$
$2170 < f < 2215$ | $2025 < f \leq 2050$
$2215 \leq f < 2240$ | $1 < f \leq 2025$
$2240 \leq f < 12750$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | + +**Table 7.7AJ: Out of band blocking requirements, single band NC-4C-HSDPA** + +| Single band NC-4C-HSDPA Configuration | Parameter | Frequency range 1 | Frequency range 2 | Frequency range 3 | UL-DL carrier separation | +|------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | Minimum | +| | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | HS-PDSCH_Ec (dBm/3.84MHz) | +3 dB | +3 dB | +3 dB | Minimum | +| | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | + 3 dB | + 3 dB | + 3 dB | | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E. + +### 7.6.3 Minimum requirement (Narrow band blocking) + +The BER shall not exceed 0.001 for the parameters specified in Table 7.7A. This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +**Table 7.7A: Narrow band blocking characteristics** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | Band III, VIII, XII, XIII, XIV | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------|--------------------------------------|--|--| +| DPCH_Ec | dBm/3.84 MHz | + 10 dB | + 10 dB | | | +| $\hat{I}_{\text{or}}$ | dBm/3.84 MHz | + 10 dB | + 10 dB | | | +| $I_{\text{blocking}}$ (GMSK) | dBm | -57 | -56 | | | +| $F_{\text{uw}}$ (offset) | MHz | 2.7 | 2.8 | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| NOTE 1: $I_{\text{blocking}}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. | | | | | | +| NOTE 2: and refer to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | | | | + +### 7.6.3A Additional requirement for DC-HSDPA and DB-DC-HSDPA (Narrow band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7B. This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +**Table 7.7B: Narrow band blocking characteristics for DC-HSDPA** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | Band III, VIII, XII, XIII, XIV | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------|--------------------------------| +| HS-PDSCH_Ec | dBm/3.84 MHz | + 10 dB | + 10 dB | +| $\bar{I}_{or}$ | dBm/3.84 MHz | + 10 dB | + 10 dB | +| $I_{blocking}$ (GMSK) | dBm | -57 | -56 | +| $F_{uw}$ (offset)
(NOTE 2) | MHz | $\pm 2.7$ | $\pm 2.8$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{blocking}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells.
NOTE 3: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2A for DC-HSDPA and Table 7.2B for DB-DC-HSDPA. | | | | + +### 7.6.3B Additional requirement for DC-HSUPA (Narrow band blocking) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7C and Table 7.7D. This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +**Table 7.7C: Narrow band blocking characteristics for DC-HSUPA** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | Band III, VIII, XII, XIII, XIV | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|--------------------------------| +| $I_{blocking}$ (GMSK) | dBm | -57 | -56 | +| $F_{uw}$ (offset)
(NOTE 2) | MHz | $\pm 2.7$ | $\pm 2.8$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{blocking}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For DC-HSUPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. | | | | + +**Table 7.7D: Reference input powers for narrow-band blocking, DC-HSUPA.** + +| Operating Band | Unit | HS-PDSCH_Ec | $\hat{I}_{or}$ | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|----------------| +| II | dBm/3.84 MHz | -101 | -90.7 | +| III | dBm/3.84 MHz | -100 | -89.7 | +| IV | dBm/3.84 MHz | -102.8 | -92.5 | +| V | dBm/3.84 MHz | -100.9 | -90.6 | +| VIII | dBm/3.84 MHz | -98.5 | -88.2 | +| X | dBm/3.84 MHz | -102.8 | -92.5 | +| XII | dBm/3.84 MHz | N/A | N/A | +| XIII | dBm/3.84 MHz | N/A | N/A | +| XIV | dBm/3.84 MHz | N/A | N/A | +| XXV | dBm/3.84 MHz | -99.5 | -89.2 | +| XXVI | dBm/3.84 MHz | -98.5 | -88.2 | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | + +### 7.6.3C Additional requirement for single band 4C-HSDPA (Narrow band blocking) + +This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +#### 7.6.3C.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7DA and Table 7.7DB. + +**Table 7.7DA: Test parameters for narrow band blocking characteristics, single band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band II | +|----------------------------|------|-----------------------------------------------------------| +| $I_{blocking}$ (GMSK) | dBm | -57 | +| $F_{uw}$ (offset) (NOTE 2) | MHz | $\pm 2.7$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | + +NOTE 1: $I_{blocking}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. + +**Table 7.7DB: Narrow band blocking requirements, single band 4C-HSDPA, single uplink operation** + +| Single band 4C-HSDPA Configuration n | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| II-3, II-4 | II | +10 dB | +10 dB | Minimum | +| NOTE: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +### 7.6.3C.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7DC and Table 7.7DD. + +**Table 7.7DC: Test parameters for narrow band blocking characteristics for single band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band II | +|----------------------------|------|-----------| +| $I_{blocking}$ (GMSK) | dBm | -57 | +| $F_{uw}$ (offset) (NOTE 2) | MHz | $\pm 2.7$ | + +NOTE 1: $I_{blocking}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. + +**Table 7.7DD: Narrow band blocking requirements, single band 4C-HSDPA, dual uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz ) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|------------------------------------|---------|----------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| II-3, II-4 | II | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +### 7.6.3D Additional requirement for dual band 4C-HSDPA (Narrow band blocking) + +This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +#### 7.6.3D.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7E and Table 7.7F. + +**Table 7.7E: Test parameters for narrow band blocking characteristics, dual band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band II, IV, V | Band VIII | +|--------------------------------------|------|-----------------------------------------------------------|-----------| +| $I_{\text{blocking}}$ (GMSK) | dBm | -57 | -56 | +| $F_{\text{uw}}$ (offset)
(NOTE 2) | MHz | $\pm 2.7$ | $\pm 2.8$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | + +NOTE 1: $I_{\text{blocking}}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequency(ies) in each band. + +**Table 7.7F: Narrow band blocking requirements, dual band 4C-HSDPA, single uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------|---------|---------|------------------------------------------|---------------------------------------------------------|--------------------------| +| I-2-VIII-1 | VIII | I | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | VIII | VIII | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| II-1-IV-2 | II | II | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| II-2-IV-1 | IV | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| II-2-IV-2 | II | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| | IV | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| I-1-V-2 | V | I | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| I-2-V-1 | V | V | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| I-2-V-2 | | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| II-1-V-2 | II | II | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| | V | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| | II | V | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | +| | V | | $\langle \text{REFSENS} \rangle + 10$ dB | $\langle \text{REF}\hat{I}_{\text{or}} \rangle + 10$ dB | Minimum | + +NOTE: $\langle \text{REFSENS} \rangle$ and $\langle \text{REF}\hat{I}_{\text{or}} \rangle$ refer to the HS-PDSCH\_Ec $\langle \text{REFSENS} \rangle$ and the HS-PDSCH $\langle \text{REF}\hat{I}_{\text{or}} \rangle$ as specified in Table 7.2D for dual band 4C-HSDPA. + +### 7.6.3D.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7G and Table 7.7H. + +**Table 7.7G: Test parameters for narrow band blocking characteristics for dual band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band II, IV, V | Band VIII | +|--------------------------------------|------|----------------|-----------| +| $I_{\text{blocking}}$ (GMSK) | dBm | -57 | -56 | +| $F_{\text{uw}}$ (offset)
(NOTE 2) | MHz | $\pm 2.7$ | $\pm 2.8$ | + +NOTE 1: $I_{\text{blocking}}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. + +**Table 7.7H: Narrow band blocking requirements, dual band 4C-HSDPA, dual uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|----------------------------------|---------|---------|---------------------------|-------------------------------------|-----------------------------------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1 | VIII | I | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-VIII-2 | VIII | I | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | VIII | -97.4 | -87.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-VIII-2 | VIII | VIII | -97.4 | -87.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-IV-2 | II | IV | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-1 | II | II | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-2 | II | II | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | II | IV | -100 | -89.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-V-2 | V | V | -99.8 | -89.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-1 | V | I | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-2 | V | I | -101 | -90.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | V | -99.8 | -89.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-V-2 | II | V | -100.3 | -90 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -99.8 | -89.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +### 7.6.3E Additional requirement for single band NC-4C-HSDPA (Narrow band blocking) + +This requirement is measure of a receiver's ability to receive a W-CDMA signal at its assigned channel frequency in the presence of an unwanted narrow band interferer at a frequency, which is less than the nominal channel spacing. + +#### 7.6.3E.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7I and Table 7.7J. + +**Table 7.7I: Test parameters for narrow band blocking characteristics, single band NC-4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band IV | +|-----------------------------------------|------|-----------------------------------------------------------| +| $I_{\text{blocking}}$ (GMSK) | dBm | -57 | +| $F_{\text{uw}}$ (offset)
(NOTE 2, 3) | MHz | $\pm 2.7$ | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | + +NOTE 1: $I_{\text{blocking}}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. + +NOTE 3: For single band NC-4C-HSPDA in-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the higher subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the lower subblock of carriers. + +**Table 7.7J: Narrow band blocking requirements, single band NC-4C-HSDPA, single uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------|------------|---------|---------------------------|-------------------------------------|--------------------------| +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | +10 dB | +10 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | +10 dB | +10 dB | Minimum | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band NC-4C-HSDPA. + +#### 7.6.3E.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.7K and Table 7.7L. + +**Table 7.7K Test parameters for narrow band blocking characteristics for single band NC-4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band IV | +|-----------------------------------------|------|-----------| +| $I_{\text{blocking}}$ (GMSK) | dBm | -57 | +| $F_{\text{uw}}$ (offset)
(NOTE 2, 3) | MHz | $\pm 2.7$ | + +NOTE 1: $I_{\text{blocking}}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. + +NOTE 3: For single band NC-4C-HSPDA in-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the higher subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the lower subblock of carriers. + +**Table 7.7L: Narrow band blocking requirements, single band NC-4C-HSDPA, dual uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|--------------------------------------------|------------|---------|---------------------------|-------------------------------------|-----------------------------------------------------------|--------------------------| +| IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | In-gap | IV | -102.8 | -92.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | -102.8 | -92.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{\text{or}} \rangle$ are allowed to be increased by an amount defined in Table 7.12. + +NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the $\langle \text{HS-PDSCH\_Ec} \rangle$ and $\langle \hat{I}_{\text{or}} \rangle$ are allowed to be increased by an amount defined in Table 7.13. + +## 7.7 Spurious response + +### 7.7.1 Minimum requirement + +Spurious response is a measure of the receiver's ability to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in subclause 7.6.2 is not met. + +The BER shall not exceed 0.001 for the parameters specified in Table 7.8. + +**Table 7.8: Spurious Response** + +| Parameter | Unit | Level | +|----------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------| +| DPCH_Ec | dBm/3.84 MHz | +3 dB | +| $\hat{I}_{or}$ | dBm/3.84 MHz | +3 dB | +| $I_{blocking}$ (CW) | dBm | -44 | +| $F_{uw}$ | MHz | Spurious response frequencies | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 2 | +| NOTE 1: and refer to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | +| NOTE 2: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | + +### 7.7.2 Additional requirement for DC-HSDPA, DB-DC-HSDPA, single band/dual band 4C-HSDPA and single band 8C-HSDPA and single band NC-4C-HSDPA + +Spurious response is a measure of the receiver's ability to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in subclause 7.6.2A, 7.6.2B, 7.6.2C, 7.6.2D or 7.6.2E or 7.6.2F is not met. + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.8A. The requirement is not applicable for dual uplink operation. + +**Table 7.8A: Spurious Response** + +| Parameter | Unit | Level | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------| +| HS-PDSCH_Ec | dBm/3.84 MHz | +3 dB | +| $\hat{I}_{or}$ | dBm/3.84 MHz | +3 dB | +| $I_{blocking}$ (CW) | dBm | -44 | +| $F_{uw}$ | MHz | Spurious response frequencies | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 2 | +| NOTE 1: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2A for DC-HSDPA, Table 7.2B for DB-DC-HSDPA, Table 7.2C for single band 4C-HSDPA, Table 7.2D for dual band 4C-HSDPA and Table 7.2E for single band 8C-HSDPA and 7.2F for single band NC-4C-HSDPA. | | | +| NOTE 2: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | + +## 7.8 Intermodulation characteristics + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal. + +### 7.8.1 Minimum requirement + +The BER shall not exceed 0.001 for the parameters specified in Table 7.9. + +**Table 7.9: Receive intermodulation characteristics** + +| Parameter | Unit | Level | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------|-----| +| DPCH_Ec | dBm/3.84 MHz | +3 dB | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | +3 dB | | +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | +| NOTE 2: and refer to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | | +| NOTE 3: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | + +### 7.8.1A Additional requirement for DC-HSDPA and DB-DC-HSDPA + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AA. + +**Table 7.9AA: Receive intermodulation characteristics** + +| Parameter | Unit | Level | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------|-----|--|--| +| HS-PDSCH_Ec | dBm/3.84 MHz | +3 dB | | | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | +3 dB | | | | +| $I_{ouw1}$ (CW) | dBm | -46 | | | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | | | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 4 | | | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells. | | | | | | +| NOTE 3: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2A for DC-HSDPA and Table 7.2B for DB-DC-HSDPA. | | | | | | +| NOTE 4: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | | | + +## 7.8.1B Additional requirement for DC-HSUPA + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AB and Table 7.9AC. + +**Table 7.9AB: Receive intermodulation characteristics** + +| Parameter | Unit | Level | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------------------------------------------------------------------|-----|--|--| +| $I_{ouw1}$ (CW) | dBm | -46 | | | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | | | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4)
NOTE 3 | | | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6. | | | | | | +| NOTE 2: For DC-HSUPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. | | | | | | +| NOTE 3: The UE transmitted mean power shall be reduced by 0.5dB for a UE operating in band XXII. | | | | | | + +**Table 7.9AC: Reference input powers for intermod, DC-HSUPA.** + +| Operating Band | Unit | HS-PDSCH_Ec | $\hat{I}_{or}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|----------------| +| I | dBm/3.84 MHz | -105 | -94.7 | +| II | dBm/3.84 MHz | -105.3 | -95 | +| III | dBm/3.84 MHz | -104.1 | -93.8 | +| IV | dBm/3.84 MHz | -105 | -94.7 | +| V | dBm/3.84 MHz | -102 | -91.7 | +| VI | dBm/3.84 MHz | -102.2 | -91.9 | +| VII | dBm/3.84 MHz | -105.3 | -95 | +| VIII | dBm/3.84 MHz | -99.8 | -89.5 | +| IX | dBm/3.84 MHz | -104.6 | -94.3 | +| X | dBm/3.84 MHz | -105 | -94.7 | +| XI | dBm/3.84 MHz | -100 | -89.7 | +| XII | dBm/3.84 MHz | N/A | N/A | +| XIII | dBm/3.84 MHz | N/A | N/A | +| XIV | dBm/3.84 MHz | N/A | N/A | +| XIX | dBm/3.84 MHz | -102.2 | -91.9 | +| XX | dBm/3.84 MHz | TBD | TBD | +| XXI | dBm/3.84 MHz | -100 | -89.7 | +| XXII | dBm/3.84 MHz | -104.1 | -93.8 | +| XXV | dBm/3.84 MHz | -103.5 | -93.2 | +| XXVI | dBm/3.84 MHz | -99.8 | -89.5 | +| NOTE 1 For the UE which supports both Band III and Band IX operating frequencies, the reference sensitivity level of TBD dBm shall apply for Band IX. The corresponding is TBD dBm | | | | +| NOTE 2 For the UE which supports both Band XI and Band XXI operating frequencies, the reference input power level is FFS. | | | | +| NOTE 3 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | +| NOTE 4 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | + +## 7.8.1C Additional requirement for single band 4C-HSDPA + +### 7.8.1C.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AD and Table 7.9AE. + +**Table 7.9AD: Test parameters for receive intermodulation characteristics, single band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|-----| +| $I_{\text{ouw1}}$ (CW) | dBm | -46 | | +| $I_{\text{ouw2}}$ mean power (modulated) | dBm | -46 | | +| $F_{\text{uw1}}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{\text{uw2}}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{\text{ouw2}}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.9AE: Intermodulation requirements, single band 4C-HSDPA, single uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{\text{or}}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|-------------------------------------|--------------------------| +| I-3 | I | +3 dB | +3 dB | Minimum | +| II-3, II-4 | II | +3 dB | +3 dB | Minimum | +| NOTE: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +### 7.8.1C.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AF and Table 7.9AG. + +**Table 7.9AF: Receive intermodulation characteristics for single band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.9AG: Intermodulation requirements, single band 4C-HSDPA, dual uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-3 | I | -105 | -94.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-3, II-4 | II | -105.3 | -95.0 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12.
NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | | | + +## 7.8.1D Additional requirement for dual band 4C-HSDPA + +### 7.8.1D.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AH and Table 7.9AI. + +**Table 7.9AH: Test parameters for receive intermodulation characteristics, dual band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. | | | | + +**Table 7.9AI: Intermodulation requirements, dual band 4C-HSDPA, single uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|--------------------------------------------------|---------|---------|---------------------------|------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1, I-2-VIII-2, I-1-VIII-2 | I | I | +3 dB | +3 dB | Minimum | +| | VIII | | +3 dB | +3 dB | Minimum | +| | I | VIII | +3 dB | +3 dB | Minimum | +| | VIII | | +3 dB | +3 dB | Minimum | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | II | II | +3 dB | +3 dB | Minimum | +| | IV | | +3 dB | +3 dB | Minimum | +| | II | IV | +3 dB | +3 dB | Minimum | +| | IV | | +3 dB | +3 dB | Minimum | +| I-1-V-2
I-2-V-1
I-2-V-2 | I | I | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| | I | V | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| II-1-V-2 | II | I | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| | II | V | +3 dB | +3 dB | Minimum | +| | V | | +3 dB | +3 dB | Minimum | +| I-1-XXXII-2
I-2-XXXII-1 | I | I | +3 dB | +3 dB | Minimum | +| | XXXII | | +3 dB | +3 dB | Minimum | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2D for dual band 4C-HSDPA. + +## 7.8.1D.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AJ and Table 7.9AK. + +**Table 7.9AJ: Receive intermodulation characteristics for dual band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. | | | | + +**Table 7.9AK: Intermodulation requirements, dual band 4C-HSDPA, dual uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|----------------------------------|---------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-2-VIII-1
I-3-VIII-1 | I | I | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -103.6 | -93.3 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-VIII-2 | I | I | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -103.6 | -93.3 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | I | VIII | -104.8 | -94.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -98.7 | -88.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-VIII-2 | I | VIII | -104.8 | -94.5 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | | -98.7 | -88.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-IV-2 | II | IV | -103.1 | -92.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -103.4 | -93.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-1 | II | II | -103.1 | -92.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -103.4 | -93.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-2 | II | II | -103.1 | -92.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -103.4 | -93.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | II | IV | -103.1 | -92.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +| | | | | | | | +|-------------|-------|---|--------|-------|-----------------------------------------------------------|---------| +| | IV | | -103.4 | -93.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-V-2 | I | V | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -101.1 | -90.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-1 | I | I | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -103.9 | -93.6 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-2 | I | I | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -103.9 | -93.6 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | I | V | -104.2 | -93.9 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -101.1 | -90.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-V-2 | II | V | -104.4 | -94.1 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -101.1 | -90.8 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-XXXII-1 | I | I | -104.7 | -94.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | XXXII | | -104.7 | -94.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +## 7.8.1E Additional requirement for single band 8C-HSDPA + +### 7.8.1E.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AL and Table 7.9AM. + +**Table 7.9AL: Test parameters for receive intermodulation characteristics, single band 8C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 8C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency, and positive offset refers to the assigned channel frequency of the highest carrier frequency. | | | | + +**Table 7.9AM: Intermodulation requirements, single band 8C-HSDPA, single uplink operation** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|--------------------------| +| I-8 | I | +3 dB | +3 dB | Minimum | +| NOTE: and refer to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2E for single band 8C-HSDPA. | | | | | + +### 7.8.1E.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AN and Table 7.9AO. + +**Table 7.9AN: Receive intermodulation characteristics for single band 8C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{ouw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{ouw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band 8C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency, and positive offset refers to the assigned channel frequency of the highest carrier frequency. | | | | + +**Table 7.9AO: Intermodulation requirements, single band 8C-HSDPA, dual uplink operation** + +| Single band 8C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-8 | I | -105 | -94.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | | | + +### 7.8.1F Additional requirement for single band NC-4C-HSDPA + +#### 7.8.1F.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AP and Table 7.9AQ. + +**Table 7.9AP: Test parameters for receive intermodulation characteristics, single band NC-4C-HSDPA, single uplink operation** + +| Parameter | Unit | Level | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | + +**Table 7.9AQ: Intermodulation requirements, single band NC-4C-HSDPA, single uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|------------------------------------------------------|------------|---------|---------------------------|------------------------------|--------------------------| +| I-1-5-1, I-2-5-1, I-3-10-1 | Out-of-gap | I | +3 dB | +3 dB | Minimum | +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | +3 dB | +3 dB | Minimum | + +NOTE: and refer to the HS-PDSCH\_Ec and the HS-PDSCH as specified in Table 7.2E for single band NC-4C-HSDPA. + +### 7.8.1F.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9AR and Table 7.9AS. + +**Table 7.9AR: Receive intermodulation characteristics for single band NC-4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Level | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-----| +| $I_{ouw1}$ (CW) | dBm | -46 | | +| $I_{ouw2}$ mean power (modulated) | dBm | -46 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 10 | -10 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 20 | -20 | +| NOTE 1: $I_{ouw2}$ (modulated) consists of the common channels needed for tests as specified in Table C.7 and 16 dedicated data channels as specified in Table C.6.
NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | + +**Table 7.9AS: Intermodulation requirements, single band NC-4C-HSDPA, dual uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| I-2-5-1, I-3-10-1 | Out-of-gap | I | -105 | -94.7 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | -104.7 | -94.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | | | | + +## 7.8.2 Minimum requirement (Narrow band) + +The BER shall not exceed 0.001 for the parameters specified in Table 7.9A. + +**Table 7.9A: Receive intermodulation characteristics** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | | Band III, VIII, XII, XIII, XIV | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------|------|--------------------------------|------|--|--|--|--| +| DPCH_Ec | dBm/3.84 MHz | + 10 dB | | + 10 dB | | | | | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 10 dB | | + 10 dB | | | | | | +| $I_{ouw1}$ (CW) | dBm | -44 | | -43 | | | | | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | -43 | | | | | | +| $F_{uw1}$ (offset) | MHz | 3.5 | -3.5 | 3.6 | -3.6 | | | | | +| $F_{uw2}$ (offset) | MHz | 5.9 | -5.9 | 6.0 | -6.0 | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | | | | | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. | | | | | | | | | | +| NOTE 2: and refer to the DPCH_Ec and the DPCH as specified in Table 7.2. | | | | | | | | | | + +## 7.8.2A Additional requirement for DC-HSDPA and DB-DC-HSDPA (Narrow band) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9B. + +**Table 7.9B: Receive intermodulation characteristics** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | | Band III, VIII, XII, XIII, XIV | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------|------|--------------------------------|------|--|--|--|--| +| HS-PDSCH_Ec | dBm/3.84 MHz | + 10 dB | | + 10 dB | | | | | | +| $\hat{I}_{or}$ | dBm/3.84 MHz | + 10 dB | | + 10 dB | | | | | | +| $I_{ouw1}$ (CW) | dBm | -44 | | -43 | | | | | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | -43 | | | | | | +| $F_{uw1}$ (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | 3.6 | -3.6 | | | | | +| $F_{uw2}$ (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | 6.0 | -6.0 | | | | | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | | | | | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. | | | | | | | | | | +| NOTE 2: For DC-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. For DB-DC-HSDPA, offset refers to the assigned channel frequencies of the individual cells. | | | | | | | | | | +| NOTE3: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2A for DC-HSDPA and Table 7.2B for DB-DC-HSDPA. | | | | | | | | | | + +## 7.8.2B Additional requirement for DC-HSUPA (Narrow band) + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9C and Table 7.9D. + +**Table 7.9C: Receive intermodulation characteristics** + +| Parameter | Unit | Band II, IV, V, X, XXV, XXVI | | Band III, VIII, XII, XIII, XIV | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|------|--------------------------------|------| +| I ouw1 (CW) | dBm | -44 | | -43 | | +| I ouw2 (GMSK) | dBm | -44 | | -43 | | +| F uw1 (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | 3.6 | -3.6 | +| F uw2 (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | 6.0 | -6.0 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| NOTE 1: I ouw2 (GMSK) is an interfering signal as defined in TS 45.004 [6]. | | | | | | +| NOTE 2: For DC-HSUPA, negative offset refers to the assigned channel frequency of the lowest carrier frequency used and positive offset refers to the assigned channel frequency of the highest carrier frequency used. | | | | | | + +**Table 7.9D: Reference input powers for intermodulation, narrow-band, DC-HSUPA.** + +| Operating Band | Unit | HS-PDSCH_Ec | $\hat{I}_{or}$ | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|----------------| +| II | dBm/3.84 MHz | -86.9 | -76.6 | +| III | dBm/3.84 MHz | -85.7 | -75.4 | +| IV | dBm/3.84 MHz | -86.9 | -76.6 | +| V | dBm/3.84 MHz | -86.9 | -76.6 | +| VIII | dBm/3.84 MHz | -85.6 | -75.3 | +| X | dBm/3.84 MHz | -86.9 | -76.6 | +| XII | dBm/3.84 MHz | N/A | N/A | +| XIII | dBm/3.84 MHz | N/A | N/A | +| XIV | dBm/3.84 MHz | N/A | N/A | +| XXV | dBm/3.84 MHz | -84.7 | -74.4 | +| XXVI | dBm/3.84 MHz | -85.6 | -75.3 | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | + +## 7.8.2C Additional requirement for single band 4C-HSDPA (Narrow band) + +### 7.8.2C.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9DA and Table 7.9DB. + +**Table 7.9DA: Test parameters for receive narrow-band intermodulation characteristics, single band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band II | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | +| $F_{uw1}$ (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | +| $F_{uw2}$ (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.9DB: Narrow-band intermodulation requirements, single band 4C-HSDPA, single uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------|-------------------------------|--------------------------| +| II-3, II-4 | II | +15.5 dB | +15.5 dB | Minimum | +| NOTE: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2C for single band 4C-HSDPA. | | | | | + +## 7.8.2C.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9DC and Table 7.9DD. + +**Table 7.9DC: Test parameters for receive narrow-band intermodulation characteristics, single band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band II | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | +| $F_{uw1}$ (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | +| $F_{uw2}$ (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For single band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequencies, and positive offset refers to the assigned channel frequency of the highest carrier frequencies. | | | | + +**Table 7.9DD: Narrow-band intermodulation requirements, single band 4C-HSDPA, dual uplink operation** + +| Single band 4C-HSDPA Configuration | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|------------------------------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| II-3, II-4 | II | -86.9 | -76.6 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +## 7.8.2D Additional requirement for dual band 4C-HSDPA (Narrow band) + +### 7.8.2D.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9E and Table 7.9F. + +**Table 7.9E: Test parameters for receive narrow-band intermodulation characteristics, dual band 4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band II, IV, V | | Band VIII | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|------|-----------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | -43 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | -43 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 3.5 | -3.5 | 3.6 | -3.6 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 5.9 | -5.9 | 6.0 | -6.0 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | | | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. | | | | | | + +**Table 7.9F: Narrow-band intermodulation requirements, dual band 4C-HSDPA, single uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | \hat{I}_{or} (dBm/3.84MHz) | UL-DL carrier separation | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------------------------|------------------------------------------------|---------------------------------| +| I-2-VIII-1
I-3-VIII-1
I-2-VIII-2
I-1-VIII-2 | VIII | I | +16.6 dB | +16.6 dB | Minimum | +| | VIII | VIII | +16.6 dB | +16.6 dB | Minimum | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | II | II | +17 dB | +17 dB | Minimum | +| | IV | | +18.9 dB | +18.9 dB | Minimum | +| | II | IV | +17 dB | +17 dB | Minimum | +| | IV | | +18.9 dB | +18.9 dB | Minimum | +| I-1-V-2
I-2-V-1
I-2-V-2 | V | I | +17 dB | +17 dB | Minimum | +| | V | V | +17 dB | +17 dB | Minimum | +| II-1-V-2 | II | II | +16.5 dB | +16.5 dB | Minimum | +| | V | | +16.5 dB | +16.5 dB | Minimum | +| | II | V | +16.5 dB | +16.5 dB | Minimum | +| | V | | +16.5 dB | +16.5 dB | Minimum | +| NOTE: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2D for dual band 4C-HSDPA. | | | | | | + +### 7.8.2D.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9G and Table 7.9H. + +**Table 7.9G: Test parameters for receive narrow-band intermodulation characteristics, dual band 4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band II, IV, V | | Band VIII | | +|-----------------------------|-------------|-----------------------|------|------------------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | -43 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | -43 | | +| $F_{uw1}$ (offset) (NOTE 2) | MHz | 3.5 | -3.5 | 3.6 | -3.6 | +| $F_{uw2}$ (offset) (NOTE 2) | MHz | 5.9 | -5.9 | 6.0 | -6.0 | + +NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6]. + +NOTE 2: For dual band 4C-HSDPA, negative offset refers to the assigned channel frequency of the lowest carrier frequenc(ies) in each band, and positive offset refers to the assigned channel frequency of the highest carrier frequenc(ies) in each band. + +**Table 7.9H: Narrow-band intermodulation requirements, dual band 4C-HSDPA, dual uplink operation** + +| Dual band 4C-HSDPA Configuration | DL Band | UL Band | HS-PDSCH_Ec (dBm/3.84MHz) | \hat{I}_{or} (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|-----------------------------------------|----------------|----------------|----------------------------------|------------------------------------------------|----------------------------------------|---------------------------------| +|-----------------------------------------|----------------|----------------|----------------------------------|------------------------------------------------|----------------------------------------|---------------------------------| + +| | | | | | | | +|--------------------------|------|------|-------|-------|-----------------------------------------------------------|---------| +| I-2-VIII-1
I-3-VIII-1 | VIII | I | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-VIII-2 | VIII | I | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | VIII | VIII | -84.6 | -74.3 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-VIII-2 | VIII | VIII | -84.6 | -74.3 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-IV-2 | II | IV | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-1 | II | II | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-2-IV-2 | II | II | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | II | IV | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | IV | | -84.7 | -74.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-1-V-2 | V | V | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-1 | V | I | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| I-2-V-2 | V | I | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | V | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| II-1-V-2 | II | V | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| | V | | -85.7 | -75.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | + +## 7.8.2E Additional requirement for single band NC-4C-HSDPA (Narrow band) + +### 7.8.2E.1 Single uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9I and Table 7.9J. + +**Table 7.9I: Test parameters for receive narrow-band intermodulation characteristics, single band NC-4C-HSDPA, single uplink operation** + +| Parameter | Unit | Band IV | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | +| $F_{uw1}$ (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | +| $F_{uw2}$ (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | +| UE transmitted mean power | dBm | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For single band NC-4C-HSDPA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | + +**Table 7.9J: Narrow-band intermodulation requirements, single band NC-4C-HSDPA, single uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UL-DL carrier separation | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------|---------------------------|------------------------------|--------------------------| +| IV-1-5-1, IV-2-10-1, IV-2-15-2, IV-2-20-1, IV-2-25-2 | Out-of-gap | IV | +10 dB | +10 dB | Minimum | +| NOTE: and refers to the HS-PDSCH_Ec and the HS-PDSCH as specified in Table 7.2E for single band NC-4C-HSDPA. | | | | | | + +## 7.8.2E.2 Dual uplink operation + +The BLER measured on each individual cell shall not exceed 0.1 for the parameters specified in Table 7.9K and Table 7.9L. + +**Table 7.9DC: Test parameters for receive narrow-band intermodulation characteristics, single band NC-4C-HSDPA, dual uplink operation** + +| Parameter | Unit | Band IV | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------|------| +| $I_{ouw1}$ (CW) | dBm | -44 | | +| $I_{ouw2}$ (GMSK) | dBm | -44 | | +| $F_{uw1}$ (offset)
(NOTE 2) | MHz | 3.5 | -3.5 | +| $F_{uw2}$ (offset)
(NOTE 2) | MHz | 5.9 | -5.9 | +| NOTE 1: $I_{ouw2}$ (GMSK) is an interfering signal as defined in TS 45.004 [6].
NOTE 2: For single band NC-4C-HSPDA out-of-gap, negative offset refers to the assigned channel frequency of the lowest carrier belonging to the lower subblock of carriers, and positive offset refers to the assigned channel frequency of the highest carrier belonging to the higher subblock of carriers. | | | | + +**Table 7.9L: Narrow-band intermodulation requirements, single band NC-4C-HSDPA, dual uplink operation** + +| Single band NC-4C-HSDPA Configuration | Test type | DL Band | HS-PDSCH_Ec (dBm/3.84MHz) | $\hat{I}_{or}$ (dBm/3.84MHz) | UE transmitted mean power (dBm) | UL-DL carrier separation | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------|---------------------------|------------------------------|-----------------------------------------------------------|--------------------------| +| IV-2-10-1,
IV-2-15-2,
IV-2-20-1,
IV-2-25-2 | Out-of-gap | IV | -86.7 | -76.4 | 20 (for Power class 3 and 3bis)
18 (for Power class 4) | Minimum | +| NOTE 1 For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.12. | | | | | | | +| NOTE 2 For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC the < HS-PDSCH_Ec > and < $\hat{I}_{or}$ > are allowed to be increased by an amount defined in Table 7.13. | | | | | | | + +## 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 spurious emission is verified per antenna connector with the other(s) terminated. + +### 7.9.1 Minimum requirement + +The power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.10, Table 7.11 and Table 6.13. + +**Table 7.10: General receiver spurious emission requirements** + +| Frequency Band | 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 | | +| $12.75\text{GHz} \leq f \leq 5^{\text{th}}$ harmonic of the upper frequency edge of the DL operating band in GHz | 1 MHz | -47 dBm | Note 1 | +| NOTE 1: Applies only for Band XXII. | | | | + +**Table 7.11: Additional receiver spurious emission requirements** + +| Band | Frequency Band | Measurement Bandwidth | Maximum level | Note | +|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------|------------------------------------------------------| +| I | 1920 MHz $\leq f \leq$ 1980 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| II | 1850 MHz $\leq f \leq$ 1915 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| III | 1710 MHz $\leq f \leq$ 1785 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| IV | 1710 MHz $\leq f <$ 1755 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| V | 824 MHz $\leq f \leq$ 849 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| VI | 815 MHz $\leq f \leq$ 830 MHz | 3.84 MHz | -60 dBm | | +| | 830 MHz $\leq f \leq$ 840 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| | 840 MHz $\leq f \leq$ 845 MHz | 3.84 MHz | -60 dBm | | +| | 860 MHz $\leq f \leq$ 875 MHz | 3.84 MHz | -60 dBm | | +| VII | 2500 MHz $\leq f \leq$ 2570 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| VIII | 880 MHz $\leq f \leq$ 915 MHz | 3.84 MHz | -60 dBm | UE in URA_PCH, Cell_PCH and idle state | +| IX | 1749.9 MHz $\leq f \leq$ 1784.9 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| X | 1710 MHz $\leq f <$ 1770 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XI | 1427.9 MHz $\leq f \leq$ 1447.9 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XII | 699 MHz $\leq f \leq$ 716 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XIII | 746 MHz $\leq f \leq$ 756 MHz | 3.84 MHz | -60 dBm | UE receive band | +| | 776 MHz $\leq f \leq$ 788 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XIV | 788 MHz $\leq f \leq$ 798 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XIX | 815 MHz $\leq f \leq$ 830 MHz | 3.84 MHz | -60 dBm | | +| | 830 MHz $\leq f \leq$ 845 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| | 860 MHz $\leq f \leq$ 875 MHz | 3.84 MHz | -60 dBm | | +| XX | 832 MHz $\leq f \leq$ 862 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XXI | 1447.9 MHz $\leq f \leq$ 1462.9 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XXII | 3410 MHz $\leq f \leq$ 3490 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XXV | 1850 MHz $\leq f \leq$ 1915 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| XXVI | 814 MHz $\leq f \leq$ 849 MHz | 3.84 MHz | -60 dBm | UE transmit band in URA_PCH, Cell_PCH and idle state | +| Note * | The receiver additional spurious emission measurements are made on frequencies which are integer multiples of 200 kHz. As exceptions, up to five measurements with a level up to the applicable requirements defined in Table 7.10 are permitted for each UARFCN used in the measurement. This note applies also to receiver additional spurious emission measurements according to Table 6.11. | | | | + +### 7.9.1A Minimum requirement + +For DB-DC-HSDPA and Dual band 4C-HSDPA configurations including an operating band without UL Band, the power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.12. + +**Table 7.12: General receiver spurious emission requirements** + +| Frequency Band | 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 1: The requirements apply when the UE is configured for DL multicarrier operation but is not transmitting. | | | | + +### 7.10 Reference input power adjustment for a dual band device + +For the UE which supports DB-DC-HSDPA configuration in Table 5.0aA, the reference input powers (HS-PDSCH\_Ec and $\hat{I}_{or}$ ) of core requirements specified in subclause 7.6.1B, 7.6.1C.2, 7.6.3B, 7.8.1B, 7.8.1C.2, and 7.8.2B are allowed to be increased by the amount given in Table 7.12 for the applicable bands. + +**Table 7.12: Allowed increase of HS-PDSCH Ec and $\hat{I}_{or}$ for UE which supports DB-DC-HSDPA.** + +| DB-DC-HSDPA Configuration | Allowed increase of HS-PDSCH Ec and $\hat{I}_{or}$ (dB) | Applicable bands | +|---------------------------|---------------------------------------------------------|------------------| +| 1 | 0.5 | I, VIII | +| 2 | 1 | II, IV | +| 3 | 0.5 | I, V | +| 4 | 1 | I, XI | +| 5 | 0.5 | II, V | +| 6 | 0.6 | I | + +For the UE which supports dual band 4C-HSDPA configuration in Table 5.0aC, the reference input powers (HS-PDSCH\_Ec and $\hat{I}_{or}$ ) of core requirements specified in subclause 7.6.1B, 7.6.1C.2, 7.6.3B, 7.8.1B, 7.8.1C.2, and 7.8.2B are allowed to be increased by the amount given in Table 7.13 for the applicable bands. + +**Table 7.13: Allowed increase of HS-PDSCH Ec and $\hat{I}_{or}$ for UE which supports dual band 4C-HSDPA.** + +| Dual Band 4C-HSDPA Configuration n | Allowed increase of HS-PDSCH Ec and $\hat{I}_{or}$ (dB) | Applicable bands | +|------------------------------------------------------|---------------------------------------------------------|------------------| +| I-2-VIII-1
I-3-VIII-1
I-1-VIII-2
I-2-VIII-2 | 0.5 | I, VIII | +| II-1-IV-2
II-2-IV-1
II-2-IV-2 | 1 | II, IV | +| I-1-V-2
I-2-V-1
I-2-V-2 | 0.5 | I, V | + +| | | | +|----------------------------|-----|-------| +| II-1-V-2 | 0.5 | II, V | +| I-1-XXXII-2
I-2-XXXII-1 | 0.6 | I | + +## 8 Performance requirement + +### 8.1 General + +The performance requirements for the UE in this subclause are specified for the measurement channels specified in Annex A, the propagation conditions specified in Annex B and the Down link Physical channels specified in Annex C. Unless stated DL power control is OFF. Unless otherwise stated the performance requirements are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. For UE(s) with more than one receiver antenna connector the fading of the signals and the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. + +For a UE which supports optional enhanced performance requirements type1 for DCH and an alternative requirement is specified, the UE shall meet only the enhanced performance requirement type1. For those cases where the enhanced performance requirements type1 are not specified, the minimum performance requirements shall apply. + +### 8.2 Demodulation in static propagation conditions + +8.2.1 (void) + +8.2.2 (void) + +#### 8.2.3 Demodulation of Dedicated Channel (DCH) + +The receive characteristic of the Dedicated Channel (DCH) in the static environment is determined by the Block Error Ratio (BLER). BLER is specified for each individual data rate of the DCH. DCH is mapped into the Dedicated Physical Channel (DPCH). + +##### 8.2.3.1 Minimum requirement + +For the parameters specified in Table 8.5 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.6. These requirements are applicable for TFCS size 16. + +**Table 8.5: DCH parameters in static propagation conditions** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------|------|--------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | | dB
-1 | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.6: DCH requirements in static propagation conditions** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -16.6 dB | $10^{-2}$ | +| 2 | -13.1 dB | $10^{-1}$ | +| | -12.8 dB | $10^{-2}$ | +| 3 | -9.9 dB | $10^{-1}$ | +| | -9.8 dB | $10^{-2}$ | +| 4 | -5.6 dB | $10^{-1}$ | +| | -5.5 dB | $10^{-2}$ | + +## 8.2.4 Demodulation of Dedicated Channel (DCH) when DL\_DCH\_FET\_Config [10] is configured by higher layers + +The receive characteristic of the Dedicated Channel (DCH) in the static environment is determined by the Block Error Ratio (BLER). BLER is specified for each individual data rate of the DCH. DCH is mapped into the Dedicated Physical Channel (DPCH). + +### 8.2.4.1 Minimum requirement + +For the parameters specified in Table 8.6A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.6B. These requirements are applicable for TFCS size 16. + +**Table 8.6A: DCH parameters in static propagation conditions** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------------------------|------|--------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | | dB
-1 | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | +| Information Data Rate | kbps | 12.2 | 12.2 | 0 | 0 | +| DCCH Presence | - | Yes | No | Yes | No | +| DL_DCH_FET_Config | - | 0 (Note 1) | | | | +| Note 1: UL is in 10ms transmission mode | | | | | | + +**Table 8.6B: DCH requirements in static propagation conditions** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -17.6 dB | $10^{-2}$ | +| 2 | -15.5 dB | $10^{-2}$ | +| 3 | -19.3 dB | $10^{-2}$ | +| 4 | -17.2 dB | $10^{-2}$ | + +## 8.3 Demodulation of DCH in multi-path fading propagation conditions + +### 8.3.1 Single Link Performance + +The receive characteristics of the Dedicated Channel (DCH) in different multi-path fading environments are determined by the Block Error Ratio (BLER) values. BLER is measured for the each of the individual data rate specified for the DPCH. DCH is mapped into in Dedicated Physical Channel (DPCH). + +#### 8.3.1.1 Minimum requirement + +For the parameters specified in Table 8.7, 8.9, 8.11, 8.13 and 8.14A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.8, 8.10, 8.12, 8.14 and 8.14B. If the UE supports optional enhanced performance requirements type1 for DCH then for the parameters specified in Table 8.10A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in 8.10B, and Test 5, Test 6 and Test 8 shall be replaced by Test 5a, Test 6a and Test 8a. These requirements are applicable for TFCS size 16. + +**Table 8.7: Test Parameters for DCH in multi-path fading propagation conditions (Case 1)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------|--------------|---------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.8: Test requirements for DCH in multi-path fading propagation conditions (Case 1)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -15.0 dB | $10^{-2}$ | +| 2 | -13.9 dB | $10^{-1}$ | +| | -10.0 dB | $10^{-2}$ | +| 3 | -10.6 dB | $10^{-1}$ | +| | -6.8 dB | $10^{-2}$ | +| 4 | -6.3 dB | $10^{-1}$ | +| | -2.2 dB | $10^{-2}$ | + +**Table 8.9: DCH parameters in multi-path fading propagation conditions (Case 2)** + +| Parameter | Unit | Test 5 | Test 6 | Test 7 | Test 8 | +|-----------------------|------|--------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | -3 | -3 | 3 | +| | | | | | 6 | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.10: DCH requirements in multi-path fading propagation (Case 2)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 5 | -7.7 dB | $10^{-2}$ | +| 6 | -6.4 dB | $10^{-1}$ | +| | -2.7 dB | $10^{-2}$ | +| 7 | -8.1 dB | $10^{-1}$ | +| | -5.1 dB | $10^{-2}$ | +| 8 | -5.5 dB | $10^{-1}$ | +| | -3.2 dB | $10^{-2}$ | + +**Table 8.10A: DCH parameters in multi-path fading propagation conditions (VA30) for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 5a | Test 6a | Test 8a | +|-----------------------|------|--------------|---------|---------| +| Phase reference | | P-CPICH | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | -3 | -3 | +| | | | | 6 | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | +| Information Data Rate | kbps | 12.2 | 64 | 384 | + +**Table 8.10B: DCH requirements in multi-path fading propagation (VA30) for UE supporting the enhanced performance requirements type1 for DCH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 5a | -14.4 dB | $10^{-2}$ | +| 6a | -11.4 dB | $10^{-1}$ | +| | -10.0 dB | $10^{-2}$ | +| 8a | -9.3 dB | $10^{-1}$ | +| | -8.0 dB | $10^{-2}$ | + +**Table 8.11: DCH parameters in multi-path fading propagation conditions (Case 3)** + +| Parameter | Unit | Test 9 | Test 10 | Test 11 | Test 12 | +|-----------------------|--------------|---------|---------|---------|----------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | -3 | -3 | 3      6 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.12: DCH requirements in multi-path fading propagation conditions (Case 3)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 9 | -11.8 dB | $10^{-2}$ | +| 10 | -8.1 dB | $10^{-1}$ | +| | -7.4 dB | $10^{-2}$ | +| | -6.8 dB | $10^{-3}$ | +| 11 | -9.0 dB | $10^{-1}$ | +| | -8.5 dB | $10^{-2}$ | +| | -8.0 dB | $10^{-3}$ | +| 12 | -5.9 dB | $10^{-1}$ | +| | -5.1 dB | $10^{-2}$ | +| | -4.4 dB | $10^{-3}$ | + +**Table 8.13: DCH parameters in multi-path fading propagation conditions (Case 1) with S-CPICH** + +| Parameter | Unit | Test 13 | Test 14 | Test 15 | Test 16 | +|-----------------------|--------------|---------|---------|---------|---------| +| Phase reference | | S-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.14: DCH requirements in multi-path fading propagation conditions (Case 1) with S-CPICH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 13 | -15.0 dB | $10^{-2}$ | +| 14 | -13.9 dB | $10^{-1}$ | +| | -10.0 dB | $10^{-2}$ | +| 15 | -10.6 dB | $10^{-1}$ | +| | -6.8 dB | $10^{-2}$ | +| 16 | -6.3 dB | $10^{-1}$ | +| | -2.2 dB | $10^{-2}$ | + +**Table 8.14A: DCH parameters in multi-path fading propagation conditions (Case 6)** + +| Parameter | Unit | Test 17 | Test 18 | Test 19 | Test 20 | +|-----------------------|--------------|---------|---------|---------|---------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | -3 | -3 | 3 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Information Data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.14B: DCH requirements in multi-path fading propagation conditions (Case 6)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 17 | -8.8 dB | $10^{-2}$ | +| 18 | -5.1 dB | $10^{-1}$ | +| | -4.4 dB | $10^{-2}$ | +| | -3.8 dB | $10^{-3}$ | +| 19 | -6.0 dB | $10^{-1}$ | +| | -5.5 dB | $10^{-2}$ | +| | -5.0 dB | $10^{-3}$ | +| 20 | -2.9 dB | $10^{-1}$ | +| | -2.1 dB | $10^{-2}$ | +| | -1.4 dB | $10^{-3}$ | + +**Table 8.14C: (void)****Table 8.14D: (void)****Table 8.14E: (void)****Table 8.14F: (void)** + +### 8.3.2 Single Link Performance when DL\_DCH\_FET\_Config [10] is configured by higher layers + +The receive characteristics of the Dedicated Channel (DCH) in different multi-path fading environments are determined by the Block Error Ratio (BLER) values. BLER is measured for the each of the individual data rate specified for the DPCH. DCH is mapped into in Dedicated Physical Channel (DPCH). + +#### 8.3.2.1 Minimum requirement + +For the parameters specified in Table 8.14G, 8.14I, 8.14K, 8.14M and 8.14O, the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.14H, 8.14J, 8.14L, 8.14N and 8.14P. + +**Table 8.14G: Test Parameters for DCH in multi-path fading propagation conditions (Case 1)** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------------------------------------|------|--------------|--------| +| Phase reference | | P-CPICH | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | 0 | +| DCCH Presence | - | No | | +| DL_DCH_FET_Config | - | 0 (Note 1) | | +| Note 1: UL is in 10ms transmission mode | | | | + +**Table 8.14H: Test requirements for DCH in multi-path fading propagation conditions (Case 1)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -13.4 dB | $10^{-2}$ | +| 2 | -16.6 dB | $10^{-2}$ | + +**Table 8.14I: DCH parameters in multi-path fading propagation conditions (Case 2)** + +| Parameter | Unit | Test 3 | Test 4 | +|-----------------------|------|--------------|--------| +| Phase reference | | P-CPICH | | +| $\hat{I}_{or}/I_{oc}$ | dB | -3 | | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | 0 | +| DCCH Presence | - | No | | + +**Table 8.14J: DCH requirements in multi-path fading propagation (Case 2)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 3 | -5.5 dB | $10^{-2}$ | +| 4 | -8.9 dB | $10^{-2}$ | + +**Table 8.14K: DCH parameters in multi-path fading propagation conditions (Case 3)** + +| Parameter | Unit | Test 5 | Test 6 | +|-----------------------|--------------|--------|--------| +| Phase reference | P-CPICH | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -3 | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Information Data Rate | kbps | 12.2 | 0 | +| DCCH Presence | - | No | | + +**Table 8.14L: DCH requirements in multi-path fading propagation conditions (Case 3)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 5 | -10.0 dB | $10^{-2}$ | +| 6 | -12.5 dB | $10^{-2}$ | + +**Table 8.14M: DCH parameters in multi-path fading propagation conditions (Case 1) with S-CPICH** + +| Parameter | Unit | Test 7 | Test 8 | +|-----------------------|--------------|--------|--------| +| Phase reference | S-CPICH | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Information Data Rate | kbps | 12.2 | 0 | +| DCCH Presence | - | No | | + +**Table 8.14N: DCH requirements in multi-path fading propagation conditions (Case 1) with S-CPICH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 7 | -13.4 dB | $10^{-2}$ | +| 8 | -16.6 dB | $10^{-2}$ | + +**Table 8.14O: DCH parameters in multi-path fading propagation conditions (Case 6)** + +| Parameter | Unit | Test 9 | Test 10 | +|-----------------------|--------------|--------|---------| +| Phase reference | P-CPICH | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -3 | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Information Data Rate | Kbps | 12.2 | 0 | +| DCCH Presence | - | No | | + +**Table 8.14P: DCH requirements in multi-path fading propagation conditions (Case 6)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 9 | -9.9 dB | $10^{-2}$ | +| 10 | -12.2 dB | $10^{-2}$ | + +## 8.4 Demodulation of DCH in moving propagation conditions + +### 8.4.1 Single link performance + +The receive single link performance of the Dedicated Channel (DCH) in dynamic moving propagation conditions are determined by the Block Error Ratio (BLER) values. BLER is measured for the each of the individual data rate specified for the DPCH. DCH is mapped into Dedicated Physical Channel (DPCH). + +#### 8.4.1.1 Minimum requirement + +For the parameters specified in Table 8.15 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.16. + +**Table 8.15: DCH parameters in moving propagation conditions** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------------------|--------------|--------|--------| +| Phase reference | P-CPICH | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | -1 | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Information Data Rate | kbps | 12.2 | 64 | + +**Table 8.16: DCH requirements in moving propagation conditions** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -14.5 dB | $10^{-2}$ | +| 2 | -10.9 dB | $10^{-2}$ | + +## 8.5 Demodulation of DCH in birth-death propagation conditions + +### 8.5.1 Single link performance + +The receive single link performance of the Dedicated Channel (DCH) in dynamic birth-death propagation conditions are determined by the Block Error Ratio (BLER) values. BER is measured for the each of the individual data rate specified for the DPCH. DCH is mapped into Dedicated Physical Channel (DPCH). + +### 8.5.1.1 Minimum requirement + +For the parameters specified in Table 8.17 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.18. + +**Table 8.17: DCH parameters in birth-death propagation conditions** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------------------|------|--------------|--------| +| Phase reference | | P-CPICH | | +| $\hat{I}_{or}/I_{oc}$ | | dB | -1 | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | 64 | + +**Table 8.18: DCH requirements in birth-death propagation conditions** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -12.6 dB | $10^{-2}$ | +| 2 | -8.7 dB | $10^{-2}$ | + +## 8.5A Demodulation of DCH in high speed train condition + +### 8.5A.1 General + +The receiver performance of the DCH in high speed train condition is determined by the BLER values. BLER is measured for the individual data rate specified for the DPCH. DCH is mapped into DPCH. + +### 8.5A.2 Minimum requirement + +For the parameters specified in Table 8.18A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.18B. + +**Table 8.18A: DCH parameters in high speed train condition** + +| Parameter | Unit | Test 1 | | +|-----------------------|------|--------------|-----| +| Phase reference | | P-CPICH | | +| $\hat{I}_{or}/I_{oc}$ | | dB | 5 | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | | + +**Table 8.18B: DCH requirements in high speed train condition** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -21.8 | $10^{-2}$ | + +## 8.6 Demodulation of DCH in downlink Transmit diversity modes + +### 8.6.1 Demodulation of DCH in open-loop transmit diversity mode + +The receive characteristic of the Dedicated Channel (DCH) in open loop transmit diversity mode is determined by the Block Error Ratio (BLER). DCH is mapped into in Dedicated Physical Channel (DPCH). + +#### 8.6.1.1 Minimum requirement + +For the parameters specified in Table 8.19 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.20. If the UE supports optional enhanced performance requirements type1 for DCH then for the parameters specified in Table 8.20A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.20B and Test 1 shall be replaced by Test 1a. + +**Table 8.19: Test parameters for DCH reception in an open loop transmit diversity scheme. +(Propagation condition: Case 1)** + +| Parameter | Unit | Test 1 | +|-----------------------|--------------|---------| +| Phase reference | | P-CPICH | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information data rate | kbps | 12.2 | + +**Table 8.20: Test requirements for DCH reception in open loop transmit diversity scheme** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$
(antenna 1/2) | BLER | +|-------------|---------------------------------------------|-----------| +| 1 | -16.8 dB | $10^{-2}$ | + +**Table 8.20A: Test parameters for DCH reception in an open loop transmit diversity scheme for UE supporting the enhanced performance requirements type1 for DCH +(Propagation condition: PA3)** + +| Parameter | Unit | Test 1a | +|-----------------------|--------------|----------------| +| Phase reference | | P-CPICH | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information | data | rate kbps 12.2 | + +**Table 8.20B: Test requirements for DCH reception in open loop transmit diversity scheme for UE supporting the enhanced performance requirements type1 for DCH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$
(antenna 1/2) | BLER | +|-------------|---------------------------------------------|-----------| +| 1a | -22.7 dB | $10^{-2}$ | + +## 8.6.2 Demodulation of DCH in closed loop transmit diversity mode + +The receive characteristic of the dedicated channel (DCH) in closed loop transmit diversity mode is determined by the Block Error Ratio (BLER). DCH is mapped into in Dedicated Physical Channel (DPCH). + +### 8.6.2.1 Minimum requirement + +For the parameters specified in Table 8.21 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.22. If the UE supports optional enhanced performance requirements type1 for + +DCH then for the parameters specified in Table 8.22A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.22B and Test 1 shall be replaced by Test 1a. + +**Table 8.21: Test Parameters for DCH Reception in closed loop transmit diversity mode (Propagation condition: Case 1)** + +| Parameter | Unit | Test 1
(Mode 1) | +|------------------------------------|--------------|--------------------| +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information data rate | kbps | 12.2 | +| Feedback error rate | % | 4 | +| Closed loop timing adjustment mode | - | 1 | + +**Table 8.22: Test requirements for DCH reception in closed loop transmit diversity mode** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$
(see note) | BLER | +|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------| +| 1 | -18.0 dB | $10^{-2}$ | +| NOTE: This is the total power from both antennas. Power sharing between antennas are feedback mode dependent as specified in TS25.214. | | | + +**Table 8.22A: Test Parameters for DCH Reception in closed loop transmit diversity mode for UE supporting the enhanced performance requirements type1 for DCH (Propagation condition: PA3)** + +| Parameter | Unit | Test 1a (Mode 1) | +|------------------------------------|--------------|------------------| +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information data rate | kbps | 12.2 | +| Feedback error rate | % | 4 | +| Closed loop timing adjustment mode | - | 1 | + +**Table 8.22B: Test requirements for DCH reception in closed loop transmit diversity mode for UE supporting the enhanced performance requirements type1 for DCH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ (see note) | BLER | +|---------------------------------------------------|---------------------------------------|-----------| +| 1a | -23.3 dB | $10^{-2}$ | +| NOTE: This is the total power from both antennas. | | | + +8.6.3 (void) + +**Table 8.23: (void)** + +**Table 8.24: (void)** + +## 8.7 Demodulation in Handover conditions + +### 8.7.1 Demodulation of DCH in Inter-Cell Soft Handover + +The bit error rate characteristics of UE is determined during an inter-cell soft handover. During the soft handover a UE receives signals from different cells. A UE has to be able to demodulate two PCCPCH channels and to combine the energy of DCH channels. Delay profiles of signals received from different cells are assumed to be the same but time shifted by 10 chips. + +The receive characteristics of the different channels during inter-cell handover are determined by the average Block Error Ratio (BLER) values. + +#### 8.7.1.1 Minimum requirement + +For the parameters specified in Table 8.25 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.26. If the UE supports optional enhanced performance requirements type1 for + +DCH then for the parameters specified in Table 8.26A the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.26B and Test 1 shall be replaced by Test 1a. + +**Table 8.25: DCH parameters in multi-path propagation conditions during Soft Handoff (Case 3)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|---------------------------------------------------|--------------|---------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ | dB | 0 | 0 | 3 | 6 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Information data Rate | kbps | 12.2 | 64 | 144 | 384 | + +**Table 8.26: DCH requirements in multi-path propagation conditions during Soft Handoff (Case 3)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -15.2 dB | $10^{-2}$ | +| 2 | -11.8 dB | $10^{-1}$ | +| | -11.3 dB | $10^{-2}$ | +| 3 | -9.9 dB | $10^{-1}$ | +| | -9.5 dB | $10^{-2}$ | +| 4 | -6.3 dB | $10^{-1}$ | +| | -5.8 dB | $10^{-2}$ | + +**Table 8.26A: DCH parameters in multi-path propagation conditions during Soft Handoff (VA120) for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 1a | +|---------------------------------------------------|-------------------|---------| +| Phase | reference P-CPICH | Phase | +| $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ | dB | 0 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information data Rate | kbps | 12.2 | + +**Table 8.26B: DCH requirements in multi-path propagation conditions during Soft Handoff (VA120) for UE supporting the enhanced performance requirements type1 for DCH** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1a | -18.5 dB | $10^{-2}$ | + +### 8.7.1A Demodulation of DCH in Inter-Cell Soft Handover when DL\_DCH\_FET\_Config [10] is configured by higher layers + +The bit error rate characteristics of UE is determined during an inter-cell soft handover. During the soft handover a UE receives signals from different cells. A UE has to be able to demodulate two PCCPCH channels and to combine the energy of DCH channels. Delay profiles of signals received from different cells are assumed to be the same but time shifted by 10 chips. + +The receive characteristics of the different channels during inter-cell handover are determined by the average Block Error Ratio (BLER) values. + +### 8.7.1A.1 Minimum requirement + +For the parameters specified in Table 8.26C the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.26D. + +**Table 8.26C: DCH parameters in multi-path propagation conditions during Soft Handoff (Case 3)** + +| Parameter | Unit | Test 1 | +|---------------------------------------------------|--------------|------------| +| Phase reference | | P-CPICH | +| $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ | dB | 0 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | +| DCCH Presence | - | No | +| DL_DCH_FET_Config | - | 0 (Note 1) | + +Note 1: UL is in 10ms transmission mode + +**Table 8.26D: DCH requirements in multi-path propagation conditions during Soft Handoff (Case 3)** + +| Test Number | $\frac{DPCH\_E_c}{I_{or}}$ | BLER | +|-------------|----------------------------|-----------| +| 1 | -14.6 dB | $10^{-2}$ | + +## 8.7.2 Combining of TPC commands from radio links of different radio link sets + +### 8.7.2.1 Minimum requirement + +Test parameters are specified in Table 8.27. The delay profiles of the signals received from the different cells are the same but time-shifted by 10 chips. + +For Test 1, the sequence of uplink power changes between adjacent slots shall be as shown in Table 8.28 over the 4 consecutive slots more than 99% of the time. Note that this case is without an additional noise source $I_{oc}$ . + +For Test 2, the Cell1 and Cell2 TPC patterns are repeated a number of times. If the transmitted power of a given slot is increased compared to the previous slot, then a variable "Transmitted power UP" is increased by one, otherwise a variable "Transmitted power DOWN" is increased by one. The requirements for "Transmitted power UP" and "Transmitted power DOWN" are shown in Table 8.28A. + +**Table 8.27: Parameters for TPC command combining** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------|--------------|-------------------------------------|--------------------------| +| Phase reference | - | | | +| DPCH_Ec/Ior | dB | | -12 | +| $\hat{I}_{or1}$ and $\hat{I}_{or2}$ | dBm/3.84 MHz | | -60 | +| $I_{oc}$ | dBm/3.84 MHz | - | -60 | +| Power-Control-Algorithm | - | Algorithm 1 | | +| Cell 1 TPC commands over 4 slots | - | {0,0,1,1} | | +| Cell 2 TPC commands over 4 slots | - | {0,1,0,1} | | +| Information data Rate | kbps | 12.2 | | +| Propagation condition | - | Static without AWGN source $I_{oc}$ | Multi-path fading case 3 | + +**Table 8.28: Test requirements for Test 1** + +| Test Number | Required power changes over the 4 consecutive slots | +|-------------|-----------------------------------------------------| +| 1 | Down, Down, Down, Up | + +**Table 8.28A: Requirements for Test 2** + +| Test Number | Ratio (Transmitted power UP) / (Total number of slots) | Ratio (Transmitted power DOWN) / (Total number of slots) | +|-------------|--------------------------------------------------------|----------------------------------------------------------| +| 2 | $\geq 0.25$ | $\geq 0.5$ | + +## 8.7.2A Combining of TPC commands from radio links of different radio link sets when DL\_DCH\_FET\_Config [10] is configured by higher layers + +### 8.7.2A.1 Minimum requirement + +Test parameters are specified in Table 8.28AA. The delay profiles of the signals received from the different cells are the same but time-shifted by 10 chips. + +For Test 1, the sequence of uplink power changes between adjacent slots shall be as shown in Table 8.28AB over the 4 consecutive slots more than 99% of the time. Note that this case is without an additional noise source $I_{oc}$ . + +For Test 2, the Cell1 and Cell2 TPC patterns are repeated a number of times. If the transmitted power of a given slot is increased compared to the previous slot, then a variable "Transmitted power UP" is increased by one, otherwise a variable "Transmitted power DOWN" is increased by one. The requirements for "Transmitted power UP" and "Transmitted power DOWN" are shown in Table 8.28AC. + +**Table 8.28AA: Parameters for TPC command combining** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------|--------------|-------------------------------------|--------------------------| +| Phase reference | - | | | +| DPCH_Ec/Ior | dB | | -12 | +| $\hat{I}_{or1}$ and $\hat{I}_{or2}$ | dBm/3.84 MHz | | -60 | +| $I_{oc}$ | dBm/3.84 MHz | - | -60 | +| Power-Control-Algorithm | - | Algorithm 1 | | +| Cell 1 TPC commands over 4 slots | - | {0,0,1,1} | | +| Cell 2 TPC commands over 4 slots | - | {0,1,0,1} | | +| Information data Rate | kbps | 12.2 | | +| DCCH Presence | - | No | | +| Propagation condition | - | Static without AWGN source $I_{oc}$ | Multi-path fading case 3 | +| DL_DCH_FET_Config | - | 0 (Note 1) | | + +Note 1: UL is in 20ms transmission mode + +**Table 8.28AB: Test requirements for Test 1** + +| Test Number | Required power changes over the 4 consecutive slots | +|-------------|-----------------------------------------------------| +| 1 | Down, Down, Down, Up | + +**Table 8.28AC: Requirements for Test 2** + +| Test Number | Ratio (Transmitted power UP) / (Total number of slots) | Ratio (Transmitted power DOWN) / (Total number of slots) | +|-------------|--------------------------------------------------------|----------------------------------------------------------| +| 2 | $\geq 0.25$ | $\geq 0.5$ | + +## 8.7.2B Combining of TPC commands from radio links of different radio link sets when DPCCH2 is configured + +### 8.7.2B.1 Minimum requirement + +This test verifies that UE follows the TPC commands for the DPCCH as well as the TPC commands for the DPCCH2 when DPCCH2 is configured. + +Test parameters are specified in Table 8.28AD. The delay profiles of the signals received from the different cells are the same but time-shifted by 10 chips. Cell1 is the serving HS-DSCH cell on which the DPCCH2 is configured. Two F-DPCH channels are sent from Cell1, where one is associated with DPCCH and one is associated with DPCCH2. + +The sequence of uplink DPCCH and DPCCH2 power changes between adjacent slots shall be as shown in Table 8.28AE over the 4 consecutive slots more than 99% of the time. Note that this case is without an additional noise source $I_{oc}$ . + +**Table 8.28AD: Parameters for TPC command combining** + +| Parameter | Unit | Test | Notes | +|-------------------------------------------------------|--------------|-------------|----------------------------------------------------------------------------------------------------------------------------------| +| Phase reference | - | P-CPICH | | +| F-DPCH $E_c/I_{or}$ Cell 1 associated with UL DPCCH | dB | -12 | This F-DPCH channel is from Cell 1 and is associated with the UL DPCCH channel | +| F-DPCH $E_c/I_{or}$ Cell 1, associated with UL DPCCH2 | dB | -12 | This F-DPCH channel is from Cell1 and is associated with the UL DPCCH2 channel | +| F-DPCH $E_c/I_{or}$ Cell 2 | dB | -12 | This F-DPCH channel is from Cell 2 and is associated with the UL DPCCH channel | +| F-DPCH slot format | - | 0 | Valid for all F-DPCH channels. | +| HS-SCCH_1 $E_c/I_{or}$ (Cell 1) | dB | - | No signalling scheduled, and no power is transmitted on this HS-SCCH, but signalled to the UE as present in HSDPA configuration. | +| HS-PDSCH $E_c/I_{or}$ (Cell 1) | dB | - | No power is transmitted | +| OCNS | | | The power of the OCNS channels that is added shall make the total power from both cells to be equal to $I_{or}$ . | +| $\hat{I}_{or1}$ and $\hat{I}_{or2}$ | dBm/3.84 MHz | -60 | | +| $I_{oc}$ | dBm/3.84 MHz | - | No interference is transmitted | +| Power-Control-Algorithm | - | Algorithm 1 | | +| Cell 1 TPC commands for DPCCH over 4 slots | - | {1,1,1,1} | | +| Cell 1 TPC commands for DPCCH2 over 4 slots | - | {1,1,0,0} | | +| Cell 2 TPC commands for DPCCH over 4 slots | - | {0,0,1,1} | | +| Propagation condition | - | Static | | + +**Table 8.28AE: Test requirements** + +| | Required power changes over the 4 consecutive slots | +|--------|-----------------------------------------------------| +| DPCCH | Down, Down, Up, Up | +| DPCCH2 | Up, Up, Down, Down | + +## 8.7.3 Combining of reliable TPC commands from radio links of different radio link sets + +### 8.7.3.1 Minimum requirement + +Test 1 verifies that the UE follows only the reliable TPC commands in soft handover. Test 2 verifies that the UE follows all the reliable TPC commands in soft handover. + +Test parameters are specified in Table 8.28B. Before the start of the tests, the UE transmit power shall be initialised to -15 dBm. An actual UE transmit power may vary from the target level of -15 dBm due to inaccurate UE output power step. + +During tests 1 and 2 the UE transmit power samples, which are defined as the mean power over one timeslot, shall stay 90% of the time within the range defined in Table 8.28C. + +**Table 8.28B: Parameters for reliable TPC command combining** + +| Parameter | | Unit | Test 1 | Test 2 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------------|-------------------|------------------| +| Phase reference | | - | P-CPICH | | +| DPCH_Ec/Ior1 | | dB | Note 1 | Note 1 & Note 3 | +| DPCH_Ec/Ior2 | | dB | DPCH_Ec/Ior1 - 10 | DPCH_Ec/Ior1 + 6 | +| DPCH_Ec/Ior3 | | dB | DPCH_Ec/Ior1 - 10 | - | +| $\hat{I}_{or1}/I_{oc}$ | | dB | -1 | -1 | +| $\hat{I}_{or2}/I_{oc}$ | | dB | -1 | -1 | +| $\hat{I}_{or3}/I_{oc}$ | | dB | -1 | - | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | +| Power-Control-Algorithm | | - | Algorithm 1 | | +| UL Power Control step size, $\Delta_{TPC}$ | | dB | 1 | | +| Cell 1 TPC commands | | - | Note 2 | Note 2 | +| Cell 2 TPC commands | | - | "1" | "1" | +| Cell 3 TPC commands | | - | "1" | - | +| Information data Rate | | kbps | 12.2 | | +| Propagation condition | | - | Static | | +| Note 1: The DPCH_Ec/Ior1 is set at the level corresponding to 5% TPC error rate.
Note 2: The uplink power control from cell1 shall be such that the UE transmit power would stay at -15 dBm.
Note 3: The maximum DPCH_Ec/Ior1 level in cell1 is -9 dB. | | | | | + +**Table 8.28C: Test requirements for reliable TPC command combining** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------------|------|------------|------------| +| UE output power | dBm | -15 ± 5 dB | -15 ± 3 dB | + +## 8.7.4 Combining of reliable TPC commands from radio links of different radio link sets when DL\_DCH\_FET\_Config [10] is configured by higher layers + +### 8.7.4.1 Minimum requirement + +Test 1 verifies that the UE follows only the reliable TPC commands in soft handover. Test 2 verifies that the UE follows all the reliable TPC commands in soft handover. + +Test parameters are specified in Table 8.28D. Before the start of the tests, the UE transmit power shall be initialised to -15 dBm. An actual UE transmit power may vary from the target level of -15 dBm due to inaccurate UE output power step. + +During tests 1 and 2 the UE transmit power samples, which are defined as the mean power over one timeslot, shall stay 90% of the time within the range defined in Table 8.28E. + +**Table 8.28D: Parameters for reliable TPC command combining** + +| | Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|------------------|--------|--|--| +| | Phase reference | - | P-CPICH | | | | +| DPCH_Ec/Ior1 | dB | Note 1 | Note 1 & Note 3 | | | | +| DPCH_Ec/Ior2 | dB | DPCH_Ec/Ior1 - 10 | DPCH_Ec/Ior1 + 6 | | | | +| DPCH_Ec/Ior3 | dB | DPCH_Ec/Ior1 - 10 | - | | | | +| $\hat{I}_{or1}/I_{oc}$ | dB | -1 | -1 | | | | +| $\hat{I}_{or2}/I_{oc}$ | dB | -1 | -1 | | | | +| $\hat{I}_{or3}/I_{oc}$ | dB | -1 | - | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | | +| Power-Control-Algorithm | - | Algorithm 1 | | | | | +| UL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | | +| Cell 1 TPC commands | - | Note 2 | Note 2 | | | | +| Cell 2 TPC commands | - | "1" | "1" | | | | +| Cell 3 TPC commands | - | "1" | - | | | | +| Information data Rate | Kbps | 12.2 | | | | | +| | Propagation condition | - | Static | | | | +| | DCCH Presence | - | No | | | | +| | DL_DCH_FET_Config | - | 0 (Note 4) | | | | +| Note 1: The DPCH_Ec/Ior1 is set at the level corresponding to 5% TPC error rate.
Note 2: The uplink power control from cell1 shall be such that the UE transmit power would stay at -15 dBm.
Note 3: The maximum DPCH_Ec/Ior1 level in cell1 is -9 dB.
Note 4: UL is in 10ms transmission mode | | | | | | | + +**Table 8.28E: Test requirements for reliable TPC command combining** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------------|------|----------------|----------------| +| UE output power | dBm | $-15 \pm 5$ dB | $-15 \pm 3$ dB | + +## 8.8 Power control in downlink + +Power control in the downlink is the ability of the UE receiver to converge to required link quality set by the network while using as low power as possible in downlink. If a BLER target has been assigned to a DCCH (See Annex A.3), then it has to be such that outer loop is based on DTCH and not on DCCH. + +The requirements in this subclause were derived with the assumption that the UTRAN responds immediately to the uplink TPC commands by adjusting the power of the first pilot field of the DL DPCCH that commences after end of the received TPC command. + +### 8.8.1 Power control in the downlink, constant BLER target + +#### 8.8.1.1 Minimum requirements + +For the parameters specified in Table 8.29 the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.30 more than 90% of the time. BLER shall be as shown in Table 8.30. If the UE supports optional enhanced performance requirements type1 for DCH then for the parameters specified in Table 8.30A the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.30B more than 90% of the time. BLER shall be as shown in Table 8.30B and Test 2 shall be replaced by Test 2a. Power control in downlink is ON during the test. + +**Table 8.29: Test parameter for downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|--------------------------------------------|--------------|------------|--------|--------|--------| +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | -1 | 4 | 9 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | -60 | | +| Information Data Rate | kbps | 12.2 | | 64 | | +| Reference channel in Annex A | | A.3.1 | | A.3.5 | | +| Target quality value on DTCH | BLER | 0.01 | | 0.1 | 0.001 | +| Target quality value on DCCH | BLER | - | | 0.1 | 0.1 | +| Propagation condition | | Case 4 | | | | +| Maximum_DL_Power * | dB | 7 | | | | +| Minimum_DL_Power * | dB | -18 | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | +| Limited Power Increase | - | "Not used" | | | | + +NOTE: Power is compared to P-CPICH as specified in [4]. + +**Table 8.30: Requirements in downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|----------------------------|------|----------|----------|---------|-----------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -16.0 | -9.0 | -9.0 | -10.3 | +| Measured quality on DTCH | BLER | 0.01±30% | 0.01±30% | 0.1±30% | 0.001±30% | + +**Table 8.30A: Test parameter for downlink power control for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 2a | +|--------------------------------------------|--------------|------------| +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Information Data Rate | kbps | 12.2 | +| Reference channel in Annex A | | A.3.1 | +| Target quality value on DTCH | BLER | 0.01 | +| Target quality value on DCCH | BLER | - | +| Propagation condition | | PA3 | +| Maximum_DL_Power * | dB | 7 | +| Minimum_DL_Power * | dB | -18 | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | +| Limited Power Increase | - | "Not used" | + +NOTE: Power is compared to P-CPICH as specified in [4]. + +**Table 8.30B: Requirements in downlink power control for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 2a | +|----------------------------|------|----------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -12.2 | +| Measured quality on DTCH | BLER | 0.01±30% | + +## 8.8.1A Power control in the downlink, constant BLER target when DL\_DCH\_FET\_Config [10] is configured by higher layers + +### 8.8.1A.1 Minimum requirements + +$$\frac{DPCH\_E_c}{I_{or}}$$ + +For the parameters specified in Table 8.30C and Table 8.30D, the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.30E, Table 8.30F, Table 8.30G and Table 8.30H more than 90% of the time. BLER shall be as shown in Table 8.30E, Table 8.30F, Table 8.30G and Table 8.30H. Test requirements in Table 8.30E, Table 8.30F, Table 8.30G and Table 8.30H correspond to DL\_DCH\_FET\_Config is set to 0 with UL in 20ms transmission mode, DL\_DCH\_FET\_Config is set to 0 with UL in 10ms transmission mode, DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and non-Null transmission in the UL, and DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and Null transmission in the UL respectively. + +**Table 8.30C: Test parameter for downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | +|--------------------------------------------|--------------|------------|--------| +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Information Data Rate | kbps | 12.2 | 0 | +| Reference channel in Annex A | | A.3A.2 | A.3A.0 | +| Target quality value on DTCH | BLER | 0.01 | | +| Target quality value on DCCH | BLER | - | | +| Propagation condition | | Case 4 | | +| Maximum_DL_Power * | dB | 7 | | +| Minimum_DL_Power * | dB | -18 | -21 | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | + +**Table 8.30D: Test parameter for downlink power control** + +| Parameter | Unit | Test 3 | Test 4 | +|--------------------------------------------|--------------|------------|--------| +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Information Data Rate | kbps | 12.2 | 0 | +| Reference channel in Annex A | | A.3A.2 | A.3A.0 | +| Target quality value on DTCH | BLER | 0.01 | | +| Target quality value on DCCH | BLER | - | | +| Propagation condition | | Case 4 | | +| Maximum_DL_Power * | dB | 7 | | +| Minimum_DL_Power * | dB | -18 | -21 | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | + +NOTE: Power is compared to P-CPICH as specified in [4]. + +**Table 8.30E: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 0 with 20ms UL transmission mode)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|----------------------------|------|-----------------|-----------------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.7 | -19.8 | -10.2 | -11.7 | +| Measured quality on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +**Table 8.30F: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 0 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|----------------------------|------|--------------|--------------|--------------|--------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -14.4 | -16.5 | -6.0 | -8.7 | +| Measured quality on DTCH | BLER | 0.01±
30% | 0.01±
30% | 0.01±
30% | 0.01±
30% | + +**Table 8.30G: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|----------------------------|------|--------------|--------------|--------------|--------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.5 | -19.8 | -9.6 | -11.6 | +| Measured quality on DTCH | BLER | 0.01±
30% | 0.01±
30% | 0.01±
30% | 0.01±
30% | + +**Table 8.30H: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode and Null transmission in uplink)** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|----------------------------|------|--------------|--------------|--------------|--------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.5 | -19.7 | -9.6 | -11.6 | +| Measured quality on DTCH | BLER | 0.01±
30% | 0.01±
30% | 0.01±
30% | 0.01±
30% | + +## 8.8.2 Power control in the downlink, initial convergence + +This requirement verifies that DL power control works properly during the first seconds after DPCH connection is established + +### 8.8.2.1 Minimum requirements + +For the parameters specified in Table 8.31 the downlink DPCH\_Ec/Ior power ratio measured values, which are averaged over 50 ms, shall be within the range specified in Table 8.32 more than 90% of the time. For UE supporting the enhanced performance requirements type1 for DCH with the parameters specified in Table 8.32A the downlink DPCH\_Ec/Ior power ratio measured values, which are averaged over 50 ms, shall be within the range specified in Table 8.32B more than 90% of the time. T1 equals to 500 ms and it starts 10 ms after the DPDCH physical channel is considered established and the first uplink frame is transmitted. T2 equals to 500 ms and it starts when T1 has expired. Power control is ON during the test. If the UE supports optional enhanced performance requirements type1 for DCH, Test 1, Test 2, Test 3 and Test 4 shall be replaced by Test 1a, Test 2a, Test 3a and Test 4a. + +The first 10 ms shall not be used for averaging, ie the first sample to be input to the averaging filter is at the beginning of T1. The averaging shall be performed with a sliding rectangular window averaging filter. The window size of the averaging filter is linearly increased from 0 up to 50 ms during the first 50 ms of T1, and then kept equal to 50ms. + +**Table 8.31: Test parameters for downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|--------------------------------------------|--------------|------------|--------|--------|--------| +| Target quality value on DTCH | BLER | 0.01 | 0.01 | 0.1 | 0.1 | +| Initial DPCH_Ec/Ior | dB | -5.9 | -25.9 | -3 | -22.8 | +| Information Data Rate | kbps | 12.2 | 12.2 | 64 | 64 | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Propagation condition | | Static | | | | +| Maximum_DL_Power | dB | 7 | | | | +| Minimum_DL_Power | dB | -18 | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | +| Limited Power Increase | - | "Not used" | | | | + +**Table 8.32: Requirements in downlink power control** + +| Parameter | Unit | Test 1 and Test 2 | Test 3 and Test 4 | +|-------------------------------------------------------------------------------------------|------|--------------------------------------|--------------------------------------| +| $\frac{DPCH\_E_c}{I_{or}}$ during T1 | dB | $-18.9 \leq DPCH\_Ec/Ior \leq -11.9$ | $-15.1 \leq DPCH\_Ec/Ior \leq -8.1$ | +| $\frac{DPCH\_E_c}{I_{or}}$ during T2 | dB | $-18.9 \leq DPCH\_Ec/Ior \leq -14.9$ | $-15.1 \leq DPCH\_Ec/Ior \leq -11.1$ | +| Note: The lower limit is decreased by 3 dB for a UE with more than one antenna connector. | | | | + +**Table 8.32A: Test parameters for downlink power control for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 1a | Test 2a | Test 3a | Test 4a | +|--------------------------------------------|--------------|------------|---------|---------|---------| +| Target quality value on DTCH | BLER | 0.01 | 0.01 | 0.1 | 0.1 | +| Initial DPCH_Ec/Ior | dB | -8.9 | -28 | -6 | -25.8 | +| Information Data Rate | kbps | 12.2 | 12.2 | 64 | 64 | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Propagation condition | | Static | | | | +| Maximum_DL_Power | dB | 7 | | | | +| Minimum_DL_Power | dB | -18 | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | +| Limited Power Increase | - | "Not used" | | | | + +**Table 8.32B: Requirements in downlink power control for UE supporting the enhanced performance requirements type1 for DCH** + +| Parameter | Unit | Test 1a and Test 2a | Test 3a and Test 4a | +|--------------------------------------|------|--------------------------------------|--------------------------------------| +| $\frac{DPCH\_E_c}{I_{or}}$ during T1 | dB | $-21.9 \leq DPCH\_Ec/Ior \leq -14.9$ | $-18.1 \leq DPCH\_Ec/Ior \leq -11.1$ | +| $\frac{DPCH\_E_c}{I_{or}}$ during T2 | dB | $-21.9 \leq DPCH\_Ec/Ior \leq -17.9$ | $-18.1 \leq DPCH\_Ec/Ior \leq -14.1$ | + +## 8.8.2A Power control in the downlink, initial convergence when DL\_DCH\_FET\_Config [10] is configured by higher layers + +This requirement verifies that DL power control works properly during the first seconds after DPCH connection is established. + +### 8.8.2A.1 Minimum requirements + +For the parameters specified in Table 8.32C the downlink DPCH\_Ec/Ior power ratio measured values, which are averaged over 50 ms, shall be within the range specified in Table 8.32D, Table 8.32E and Table 8.32F more than 90% of the time. T1 equals to 500 ms and it starts 10 ms after the DPDCH physical channel is considered established and the first uplink frame is transmitted. T2 equals to 500 ms and it starts when T1 has expired. Power control is ON during the test. + +The first 10 ms shall not be used for averaging, ie the first sample to be input to the averaging filter is at the beginning of T1. The averaging shall be performed with a sliding rectangular window averaging filter. The window size of the averaging filter is linearly increased from 0 up to 50 ms during the first 50 ms of T1, and then kept equal to 50ms. Test requirements in Table 8.32D, Table 8.32E and Table 8.32F correspond to DL\_DCH\_FET\_Config is set to 0 with UL in 20ms transmission mode, DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and non-Null transmission in the UL, and DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and Null transmission in the UL respectively. + +**Table 8.32C: Test parameters for downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | | | +|--------------------------------------------|--------------|------------|--------|--------|--------|--|--| +| Target quality value on DTCH | BLER | 0.01 | | 0.01 | | | | +| Initial DPCH_Ec/Ior | dB | -5.9 | -25.9 | -5.9 | -25.9 | | | +| Information Data Rate | kbps | 12.2 | | 0 | | | | +| DCCH Presence | - | No | | | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | | | +| Propagation condition | | Static | | | | | | +| Maximum_DL_Power | dB | 7 | | | | | | +| Minimum_DL_Power | dB | -18 | | -21 | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | | | +| Limited Power Increase | - | "Not used" | | | | | | + +**Table 8.32D: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 0 with 20ms UL transmission mode)** + +| Parameter | Unit | Test 1 & Test 2 | Test 3 & Test 4 | +|--------------------------------------|------|-----------------------------------------|-----------------------------------------| +| $\frac{DPCH\_E_c}{I_{or}}$ during T1 | dB | $-20.6 \leq DPCH\_Ec/I_{or} \leq -12.0$ | $-20.6 \leq DPCH\_Ec/I_{or} \leq -12.0$ | +| $\frac{DPCH\_E_c}{I_{or}}$ during T2 | dB | $-20.6 \leq DPCH\_Ec/I_{or} \leq -15.5$ | $-20.6 \leq DPCH\_Ec/I_{or} \leq -15.6$ | + +**Table 8.32E: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1 & Test 2 | Test 3 & Test 4 | +|--------------------------------------|------|-----------------------------------------|-----------------------------------------| +| $\frac{DPCH\_E_c}{I_{or}}$ during T1 | dB | $-21.0 \leq DPCH\_Ec/I_{or} \leq -11.5$ | $-21.4 \leq DPCH\_Ec/I_{or} \leq -11.6$ | +| $\frac{DPCH\_E_c}{I_{or}}$ during T2 | dB | $-21.0 \leq DPCH\_Ec/I_{or} \leq -15.8$ | $-21.4 \leq DPCH\_Ec/I_{or} \leq -15.2$ | + +**Table 8.32F: Requirements in downlink power control (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode and Null transmission in uplink)** + +| Parameter | Unit | Test 1 & Test 2 | Test 3 & Test 4 | +|--------------------------------------|------|-----------------------------------------|-----------------------------------------| +| $\frac{DPCH\_E_c}{I_{or}}$ during T1 | dB | $-21.3 \leq DPCH\_Ec/I_{or} \leq -10.6$ | $-22.1 \leq DPCH\_Ec/I_{or} \leq -11.2$ | +| $\frac{DPCH\_E_c}{I_{or}}$ during T2 | dB | $-21.3 \leq DPCH\_Ec/I_{or} \leq -15.0$ | $-22.1 \leq DPCH\_Ec/I_{or} \leq -14.9$ | + +### 8.8.3 Power control in downlink, wind up effects + +#### 8.8.3.1 Minimum requirements + +This test is run in three stages where stage 1 is for convergence of the power control loop. In stage two the maximum downlink power for the dedicated channel is limited not to be higher than the value specified in Table 8.33. All + +parameters used in the three stages are specified in Table 8.33. The downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, during stage 3 shall be lower than the value specified in Table 8.34 more than 90% of the time. + +Power control of the UE is ON during the test. + +**Table 8.33: Test parameter for downlink power control, wind-up effects** + +| Parameter | Unit | Test 1 | | | +|--------------------------------------------|--------------|------------|---------------------|---------| +| | | Stage 1 | Stage 2 | Stage 3 | +| Time in each stage | s | 5 | 5 | 0.5 | +| $\hat{I}_{or}/I_{oc}$ | dB | 5 | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | +| Information Data Rate | kbps | 12.2 | | | +| Quality target on DTCH | BLER | 0.01 | | | +| Propagation condition | | Case 4 | | | +| Maximum_DL_Power | dB | 7 | min(-6.2,P). Note 1 | 7 | +| Minimum_DL_Power | dB | -18 | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | +| Limited Power Increase | - | "Not used" | | | + +*Note 1:* $P$ is the level corresponding to the average $\frac{DPCH\_E_c}{I_{or}}$ power ratio - 2 dB compared to the P-CPICH level. The average $\frac{DPCH\_E_c}{I_{or}}$ power ratio is measured during the initialisation stage after the power control loop has converged before the actual test starts. + +**Table 8.34: Requirements in downlink power control, wind-up effects** + +| Parameter | Unit | Test 1, stage 3 | +|----------------------------|------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -13.3 | + +## 8.8.3A Power control in downlink, wind up effects when DL\_DCH\_FET\_Config [10] is configured by higher layers + +### 8.8.3A.1 Minimum requirements + +This test is run in three stages where stage 1 is for convergence of the power control loop. In stage two the maximum downlink power for the dedicated channel is limited not to be higher than the value specified in Table 8.33A and Table 8.33B. + +All parameters used in the three stages are specified in Table 8.33A and Table 8.33B. The downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, during stage 3 shall be lower than the value specified in Table 8.34C, Table 8.34D, Table 8.34E and Table 8.34F more than 90% of the time. Test requirements in Table 8.34C, Table 8.34D, Table 8.34E and Table 8.34F correspond to DL\_DCH\_FET\_Config is set to 0 with UL in 20ms transmission mode, DL\_DCH\_FET\_Config is set to 0 with UL in 10ms transmission mode, DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and non-Null transmission in the UL, and, DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and Null transmission in the UL respectively. + +Power control of the UE is ON during the test. + +**Table 8.34A: Test parameter for downlink power control, wind-up effects (12.2 kbps without DCCH)** + +| Parameter | Unit | Test 1 | | | +|-----------|------|---------|---------|---------| +| | | Stage 1 | Stage 2 | Stage 3 | + +| | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------|---------------------|-----|--|--|--| +| Time in each stage | s | 5 | 5 | 0.5 | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 5 | | | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | | | +| Information Data Rate | kbps | 12.2 | | | | | | +| DCCH Presence | | No | | | | | | +| Quality target on DTCH | BLER | 0.01 | | | | | | +| Propagation condition | | Case 4 | | | | | | +| Maximum_DL_Power | dB | 7 | min(-6.2,P). Note 1 | 7 | | | | +| Minimum_DL_Power | dB | -18 | | | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | | | +| Limited Power Increase | - | "Not used" | | | | | | +| $\frac{DPCH\_E_c}{I_{or}}$ | | | | | | | | +| Note 1: $P$ is the level corresponding to the average $\frac{DPCH\_E_c}{I_{or}}$ power ratio - 2 dB compared to the $P\text{-CPICH}$ level. The average $\frac{DPCH\_E_c}{I_{or}}$ power ratio is measured during the initialisation stage after the power control loop has converged before the actual test starts. | | | | | | | | + +Table 8.34B: Test parameter for downlink power control, wind-up effects (0 kbps without DCCH) + +| Parameter | Unit | Test 1 | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------|---------------------|---------|--|--|--| +| | | Stage 1 | Stage 2 | Stage 3 | | | | +| Time in each stage | s | 5 | 5 | 0.5 | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 5 | | | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | | | +| Information Data Rate | kbps | 0 | | | | | | +| DCCH Presence | | No | | | | | | +| Quality target on DTCH | BLER | 0.01 | | | | | | +| Propagation condition | | Case 4 | | | | | | +| Maximum_DL_Power | dB | 7 | min(-6.2,P). Note 1 | 7 | | | | +| Minimum_DL_Power | dB | -21 | | | | | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | | | | | +| Limited Power Increase | - | "Not used" | | | | | | +| $\frac{DPCH\_E_c}{I_{or}}$ | | | | | | | | +| Note 1: $P$ is the level corresponding to the average $\frac{DPCH\_E_c}{I_{or}}$ power ratio - 2 dB compared to the $P\text{-CPICH}$ level. The average $\frac{DPCH\_E_c}{I_{or}}$ power ratio is measured during the initialisation stage after the power control loop has converged before the actual test starts. | | | | | | | | + +Table 8.34C: Requirements in downlink power control, wind-up effects (DL\_DCH\_FET\_Config is set to 0 with 20ms UL transmission mode) + +| Parameter | Unit | Test 1, stage 3 | Test 1, stage 3 | +|----------------------------|------|----------------------------------------|----------------------------------------| +| | | Reference Measurement Channel (A.3A.2) | Reference Measurement Channel (A.3A.0) | +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -14.6 | -17.3 | + +**Table 8.34D: Requirements in downlink power control, wind-up effects (DL\_DCH\_FET\_Config is set to 0 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1, stage 3 | Test 1, stage 3 | +|----------------------------|------|----------------------------------------|----------------------------------------| +| | | Reference Measurement Channel (A.3A.2) | Reference Measurement Channel (A.3A.0) | +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -13.6 | -15.7 | + +**Table 8.34E: Requirements in downlink power control, wind-up effects (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1, stage 3 | Test 1, stage 3 | +|----------------------------|------|----------------------------------------|----------------------------------------| +| | | Reference Measurement Channel (A.3A.2) | Reference Measurement Channel (A.3A.0) | +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -14.7 | -17.1 | + +**Table 8.34F: Requirements in downlink power control, wind-up effects (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode and Null transmission in Uplink)** + +| Parameter | Unit | Test 1, stage 3 | Test 1, stage 3 | +|----------------------------|------|----------------------------------------|----------------------------------------| +| | | Reference Measurement Channel (A.3A.2) | Reference Measurement Channel (A.3A.0) | +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -14.7 | -16.7 | + +## 8.8.4 Power control in the downlink, different transport formats + +### 8.8.4.1 Minimum requirements + +Test 1 verifies that UE outer loop power control has proper behaviour with different transport formats. + +The downlink reference measurement channel used in this subclause shall have two different transport formats. The different transport formats of the downlink reference measurement channel used shall correspond to the measurement channels specified in Annex A.3.0 and A.3.1. The transport format used in downlink reference measurement channel during different stages of the test shall be set according to the information data rates specified in Table 8.34A. During + +stage 1 a downlink transport format combination using the 12.2kbps information data rate DTCH shall be used, and during stage 2 the downlink transport format combination shall be changed such that a 0kbps information data rate transport format combination is then used. + +For the parameters specified in Table 8.34A the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.34B more than 90% of the time. BLER shall be as shown in Table 8.34B. Power control in downlink is ON during the test. + +**Table 8.34A: Parameters for downlink power control in case of different transport formats** + +| Parameter | Unit | Test 1 | | +|------------------------------------------------------------------------------------|--------------|------------|---------| +| | | Stage 1 | Stage 2 | +| Time in each stage | s | Note 1 | Note 1 | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Information Data Rate | kbps | 12.2 | 0 | +| Quality target on DTCH | BLER | 0.01 | | +| Quality target on DCCH | BLER | 1 | | +| Propagation condition | | Case4 | | +| Maximum_DL_Power | dB | 7 | | +| Minimum_DL_Power | dB | -18 | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | +| Note 1: The stage lasts until the DTCH quality has converged to the quality target | | | | + +NOTE: Power is compared to P-CPICH as specified in [4]. + +**Table 8.34B: Requirements in downlink power control in case of different transport formats** + +| Parameter | Unit | Test 1, stage 1 | Test 1, stage 2 | +|---------------------------------|------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -16.0 | -18.0 | +| Measured quality

on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +## 8.8.4A Power control in the downlink, different transport formats + +### 8.8.4A.1 Minimum requirements + +Test 1 verifies that UE outer loop power control has proper behaviour with different transport formats. + +The downlink reference measurement channel used in this subclause shall have two different transport formats. The different transport formats of the downlink reference measurement channel used shall correspond to the measurement channels specified in Annex A.3A.0 and A.3A.2. The transport format used in downlink reference measurement + +channel during different stages of the test shall be set according to the information data rates specified in Table 8.34BA. During stage 1 a downlink transport format combination using the 12.2kbps information data rate DTCH shall be used, and during stage 2 the downlink transport format combination shall be changed such that a 0kbps information data rate transport format combination is then used. + +For the parameters specified in Table 8.34BA, the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.34BB, Table 8.34BC, Table 8.34BD and Table 8.34BE more than 90% of the time. BLER shall be as shown in Table 8.34BB, Table 8.34BC, Table 8.34BD and Table 8.34BE. Power control in downlink is ON during the test. Test requirements in Table 8.34BB, Table 8.34BC, Table 8.34BD and Table 8.34BE correspond to DL\_DCH\_FET\_Config is set to 0 with UL in 20ms transmission mode, DL\_DCH\_FET\_Config is set to 0 with UL in 10ms transmission mode, DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and non-Null transmission in the UL, and DL\_DCH\_FET\_Config is set to 1 with UL in 10ms transmission mode and Null transmission in the UL respectively. + +**Table 8.34BA: Parameters for downlink power control in case of different transport formats** + +| Parameter | Unit | Test 1 | | +|------------------------------------------------------------------------------------|--------------|------------|---------| +| | | Stage 1 | Stage 2 | +| Time in each stage | s | Note 1 | Note 1 | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Information Data Rate | kbps | 12.2 | 0 | +| DCCH Presence | | No | | +| Quality target on DTCH | BLER | 0.01 | | +| Quality target on DCCH | BLER | 1 | | +| Propagation condition | | Case4 | | +| Maximum_DL_Power | dB | 7 | | +| Minimum_DL_Power | dB | -18 | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | +| Note 1: The stage lasts until the DTCH quality has converged to the quality target | | | | + +NOTE: Power is compared to P-CPICH as specified in [4]. + +**Table 8.34BB: Requirements in downlink power control in case of different transport formats (DL\_DCH\_FET\_Config is set to 0 with 20ms UL transmission mode)** + +| Parameter | Unit | Test 1, stage 1 | Test 1, stage 2 | +|----------------------------|------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.7 | -19.8 | +| Measured quality on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +**Table 8.34BC: Requirements in downlink power control in case of different transport formats (DL\_DCH\_FET\_Config is set to 0 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1, stage 1 | Test 1, stage 2 | +|-----------------------------|------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -14.4 | -16.6 | +| Measured quality
on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +**Table 8.34BD: Requirements in downlink power control in case of different transport formats (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode)** + +| Parameter | Unit | Test 1, stage 1 | Test 1, stage 2 | +|-----------------------------|------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.5 | -19.8 | +| Measured quality
on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +**Table 8.34BE: Requirements in downlink power control in case of different transport formats (DL\_DCH\_FET\_Config is set to 1 with 10ms UL transmission mode and Null transmission in uplink)** + +| Parameter | Unit | Test 1, stage 1 | Test 1, stage 2 | +|-----------------------------|------|-----------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -17.5 | -19.8 | +| Measured quality
on DTCH | BLER | $0.01 \pm 30\%$ | $0.01 \pm 30\%$ | + +## 8.8.5 Power control in the downlink for F-DPCH + +### 8.8.5.1 Minimum requirements + +For the parameters specified in Table 8.34C the downlink power ratio measured values, which are averaged over TPC symbols of the F-DPCH frame, shall be below the specified value in Table 8.34D more than 90% of the time. TPC command error ratio shall be in the limits given by Table 8.34D. Power control in downlink is ON during the tests. + +**Table 8.34C: Test parameters for Fractional downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | +|--------------------------------------------|--------------|-------------|--------| +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | -1 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| SF | | 256 | | +| Target quality value on F DPCH | % | 0.01 | 0.05 | +| Propagation condition | | Case 4 | | +| Maximum_DL_Power * | dB | 7 | | +| Minimum_DL_Power * | dB | -18 | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | +| Power-Control-Algorithm | - | Algorithm 1 | | + +**Table 8.34D: Requirements in Fractional downlink power control** + +| Parameter | Unit | Test 1 | Test 2 | +|------------------------------|------|--------|--------| +| | dB | -15.9 | -12.0 | +| TPC command Error Ratio high | - | 0.015 | 0.065 | +| TPC command Error Ratio low | - | 0.005 | 0.035 | + +## 8.9 Downlink compressed mode + +Downlink compressed mode is used to create gaps in the downlink transmission, to allow the UE to make measurements on other frequencies. + +The requirements in this subclause were derived with the assumption that the UTRAN responds immediately to the uplink TPC commands by adjusting the power of the first pilot field of the DL DPCCH that commences after end of the received TPC command. + +### 8.9.1 Single link performance + +The receiver single link performance of the Dedicated Traffic Channel (DCH) in compressed mode is determined by the Block Error Ratio (BLER) and transmitted DPCH\_Ec/Ior power ratio in the downlink. + +The compressed mode parameters are given in clause A.5. + +#### 8.9.1.1 Minimum requirements + +For the parameters specified in Table 8.35 the downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio measured values, which are averaged over one slot, shall be below the specified value in Table 8.36 more than 90% of the time. The measured quality on DTCH shall be as required in Table 8.36. + +Downlink power control is ON during the test. Uplink TPC commands shall be error free. + +**Table 8.35: Test parameter for downlink compressed mode** + +| Parameter | Unit | Test 1 | Test 2 | +|--------------------------------------------|--------------|------------------------------------------------|------------------------------------------------| +| Delta SIR1 | dB | 0 | 3 | +| Delta SIR after1 | dB | 0 | 3 | +| Delta SIR2 | dB | 0 | 0 | +| Delta SIR after2 | dB | 0 | 0 | +| Compressed mode patterns | - | Set 2 in table A.21 in clause A.5 of TS 25.101 | Set 1 in table A.21 in clause A.5 of TS 25.101 | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Information Data Rate | kbps | 12.2 | | +| Propagation condition | | Case 3 | Case 2 | +| Target quality value on DTCH | BLER | 0.01 | | +| Maximum_DL_Power | dB | 7 | | +| Minimum_DL_Power | dB | -18 | | +| DL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Limited Power Increase | - | "Not used" | | + +**Table 8.36: Requirements in downlink compressed mode** + +| Parameter | Unit | Test 1 | Test 2 | +|----------------------------------------------------|------|------------------|-----------------| +| $\frac{DPCH\_E_c}{I_{or}}$ | dB | -13.7 | No requirements | +| Measured quality of compressed and recovery frames | BLER | No requirements | <0.001 | +| Measured quality on DTCH | BLER | $0.01 \pm 30 \%$ | | + +## 8.10 Blind transport format detection + +Performance of Blind transport format detection is determined by the Block Error Ratio (BLER) values and by the measured average transmitted DPCH\_Ec/Ior value. + +### 8.10.1 Minimum requirement + +For the parameters specified in Table 8.37 the average downlink $\frac{DPCH\_E_c}{I_{or}}$ power ratio shall be below the specified value for the BLER shown in Table 8.38. + +**Table 8.37: Test parameters for Blind transport format detection** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | Test 5 | Test 6 | +|-----------------------|--------------|---------------|---------------|---------------|--------------------------|---------------|---------------| +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | | -3 | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | | | +| Information Data Rate | kbps | 12.2 (rate 1) | 7.95 (rate 2) | 1.95 (rate 3) | 12.2 (rate 1) | 7.95 (rate 2) | 1.95 (rate 3) | +| propagation condition | - | static | | | multi-path fading case 3 | | | +| TFCI | - | off | | | | | | + +**Table 8.38: The Requirements for DCH reception in Blind transport format detection** + +| Test Number | $\frac{DPCH\_Ec}{I_{or}}$ | BLER | FDR | +|-------------|---------------------------|-----------|-----------| +| 1 | -17.7 dB | $10^{-2}$ | $10^{-4}$ | +| 2 | -17.8 dB | $10^{-2}$ | $10^{-4}$ | +| 3 | -18.4 dB | $10^{-2}$ | $10^{-4}$ | +| 4 | -13.0 dB | $10^{-2}$ | $10^{-4}$ | +| 5 | -13.2 dB | $10^{-2}$ | $10^{-4}$ | +| 6 | -13.8 dB | $10^{-2}$ | $10^{-4}$ | + +NOTE 1: The value of DPCH\_Ec/Ior, Ioc, and Ior/Ioc are defined in case of DPCH is transmitted + +NOTE 2: In this test, 9 different Transport Format Combinations (Table 8.39) are sent during the call set up procedure, so that the UE has to detect the correct transport format from these 9 candidates. + +**Table 8.39: Transport format combinations informed during the call set up procedure in the test** + +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | +|------|-------|-------|-------|------|------|------|-------|-------|-------| +| DTCH | 12.2k | 10.2k | 7.95k | 7.4k | 6.7k | 5.9k | 5.15k | 4.75k | 1.95k | +| DCCH | 2.4k | | | | | | | | | + +## 8.11 Detection of Broadcast channel (BCH) + +The receiver characteristics of Broadcast Channel (BCH) are determined by the Block Error Ratio (BLER) values. BCH is mapped into the primary common control physical channel (P-CCPCH). + +### 8.11.1 Minimum requirement without transmit diversity + +For the parameters specified in Table 8.40 the average downlink power P-CCPCH\_Ec/Ior shall be below the specified value for the BLER shown in Table 8.41. (The Down link Physical channels are specified in Annex C). + +This requirement doesn't need to be tested. + +**Table 8.40: Parameters for BCH detection** + +| | Parameter | Unit | Test 1 | Test 2 | +|-----------------------|-----------------|--------|---------|--------| +| | Phase reference | - | P-CPICH | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | -3 | | +| Propagation condition | | Static | Case 3 | | + +**Table 8.41: Test requirements for BCH detection** + +| Test Number | P-CCPCH_Ec/Ior | BLER | +|-------------|----------------|------| +| 1 | -18.5 dB | 0.01 | +| 2 | -12.8 dB | 0.01 | + +## 8.11.2 Minimum requirement with open loop transmit diversity + +For the parameters specified in Table 8.41A the average downlink power P-CCPCH\_Ec/Ior shall be below the specified value for the BLER shown in Table 8.41B. (The Down link Physical channels are specified in Annex C). + +This requirement doesn't need to be tested. + +**Table 8.41A: Test parameters for BCH detection in an open loop transmit diversity scheme (STTD). +(Propagation condition: Case 1)** + +| | Parameter | Unit | Test 3 | +|-----------------------|-----------------|------|---------| +| | Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | + +**Table 8.41B: Test requirements for BCH detection in open loop transmit diversity scheme** + +| Test Number | P-CCPCH_Ec/Ior
(Total power from antenna 1 and 2) | BLER | +|-------------|------------------------------------------------------|------| +| 3 | -18.5 | 0.01 | + +## 8.11A Detection of Broadcast channel (BCH) mapped to S-CCPCH + +The requirements in this section shall apply for UEs that support reception of a broadcast channel mapped to S-CCPCH. + +The receiver characteristics of a Broadcast Channel (BCH) mapped to S-CCPCH are determined by the Block Error Ratio (BLER) values during non DTX TTIs. + +### 8.11A.1 Minimum requirement without transmit diversity + +For the parameters specified in Table 8.41C the average downlink power S-CCPCH\_Ec/Ior during non DTX TTIs shall be below the specified value for the BLER shown in Table 8.41D. (The Downlink Physical channels are specified in Annex C). + +This requirement doesn't need to be tested. + +**Table 8.41C: Parameters for detection of BCH mapped to S-CCPCH** + +| | Parameter | Unit | Test 1 | Test 2 | +|-----------------------|-----------------|--------|---------|--------| +| | Phase reference | - | P-CPICH | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | -3 | | +| Propagation condition | | Static | Case 3 | | + +**Table 8.41D: Test requirements for detection of BCH mapped to S-CCPCH** + +| Test Number | S-CCPCH_Ec/Ior | BLER | +|-------------|----------------|------| +| 1 | -18.5 dB | 0.01 | +| 2 | -12.8 dB | 0.01 | + +## 8.11.2 Minimum requirement with open loop transmit diversity + +For the parameters specified in Table 8.41E the average downlink power S-CCPCH\_Ec/Ior during non DTX TTIs shall be below the specified value for the BLER shown in Table 8.41F. (The Downlink Physical channels are specified in Annex C). + +This requirement doesn't need to be tested. + +**Table 8.41E: Test parameters for detection of BCH mapped to S-CCPCH in an open loop transmit diversity scheme (STTD). (Propagation condition: Case 1)** + +| | Parameter | Unit | Test 3 | +|-----------------------|-----------------|------|---------| +| | Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| $\hat{I}_{or}/I_{oc}$ | dB | 9 | | + +**Table 8.41F: Test requirements for detection of BCH mapped to S-CCPCH in open loop transmit diversity scheme** + +| Test Number | S-CCPCH_Ec/Ior
(Total power from antenna 1 and 2) | BLER | +|-------------|------------------------------------------------------|------| +| 3 | -18.5 | 0.01 | + +## 8.12 Demodulation of Paging Channel (PCH) + +The receiver characteristics of paging channel are determined by the probability of missed paging message (Pm-p). PCH is mapped into the S-CCPCH and it is associated with the transmission of Paging Indicators (PI) to support efficient sleep-mode procedures. + +### 8.12.1 Minimum requirement + +For the parameters specified in Table 8.42 the average probability of missed paging (Pm-p) shall be below the specified value in Table 8.43. Power of downlink channels other than S-CCPCH and PICH are as defined in Table C.3 of Annex C. S-CCPCH structure is as defined in Annex A.6. + +**Table 8.42: Parameters for PCH detection** + +| | Parameter | Unit | Test 1 | Test 2 | | +|-----------------------|--------------------------------------------|--------|---------|--------|--| +| | Number of paging indicators per frame (Np) | - | 72 | | | +| | Phase reference | - | P-CPICH | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | -3 | | | +| Propagation condition | | Static | Case 3 | | | + +**Table 8.43: Test requirements for PCH detection** + +| Test Number | S-CCPCH_Ec/lor | PICH_Ec/lor | Pm-p | +|-------------|----------------|-------------|------| +| 1 | -14.8 | -19 | 0.01 | +| 2 | -9.8 | -12 | 0.01 | + +## 8.13 Detection of Acquisition Indicator (AI) + +The receiver characteristics of Acquisition Indicator (AI) are determined by the probability of false alarm $P_{fa}$ and probability of correct detection $P_d$ . $P_{fa}$ is defined as a conditional probability of detection of AI signature given that a AI signature was not transmitted. $P_d$ is defined as a conditional probability of correct detection of AI signature given that the AI signature is transmitted. + +### 8.13.1 Minimum requirement + +For the parameters specified in Table 8.44 the $P_{fa}$ and $1-P_d$ shall not exceed the specified values in Table 8.45. Power of downlink channels other than AICH is as defined in Table C.3 of Annex C. + +**Table 8.44: Parameters for AI detection** + +| | Parameter | Unit | Test 1 | | +|---------------------------------------------------|-----------------|--------|---------|--| +| | Phase reference | - | P-CPICH | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | +| Number of other transmitted AI signatures on AICH | - | 0 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | | | +| AICH_Ec/lor | dB | -22.0 | | | +| AICH Power Offset | dB | -12.0 | | | +| Propagation condition | - | Static | | | + +Note that AICH\_Ec/lor can not be set. Its value is calculated from other parameters and it is given for information only. + $(AICH\_Ec/lor = AICH\ Power\ Offset + CPICH\_Ec/lor)$ + +**Table 8.45: Test requirements for AI detection** + +| Test Number | Pfa | 1-Pd | +|-------------|------|------| +| 1 | 0.01 | 0.01 | + +## 8.13A Detection of E-DCH Acquisition Indicator (E-AI) + +The receiver characteristics of E-DCH Acquisition Indicator (E-AI) are determined by the probability of correct detection $P_{de}$ . $P_{de}$ is defined as a conditional probability of correct detection of E-AI signature given that the E-AI signature is transmitted and AI signature was correctly received. + +### 8.13A.1 Minimum requirement + +For the parameters specified in Table 8.45C the 1- $P_{de}$ shall not exceed the specified value in Table 8.45D. The power settings for downlink channels other than AICH and E-AICH are set as defined in Table C.3 of Annex C. + +**Table 8.45C: Parameters for E-AI detection** + +| Parameter | Unit | Test 1 | +|-----------------------------------------------------|--------------|---------| +| Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Number of other transmitted AI signatures on AICH | - | 0 | +| Number of resources assumed for E-DCH random access | - | 32 | +| $\hat{I}_{or}/I_{oc}$ | dB | -1 | + + + +| | | | +|-----------------------|----|--------| +| AICH_Ec/Ior | dB | -22.0 | +| AICH Power Offset | dB | -12.0 | +| E-AICH_Ec/Ior | dB | -22.0 | +| E-AICH Power Offset | dB | -12.0 | +| Propagation condition | - | Static | + +Note that AICH\_Ec/Ior and E-AICH\_Ec/Ior can not be set, their values are calculated from other parameters and are given for information only. + +**Table 8.45D: Test requirements for E-AI detection** + +| Test Number | 1- Pde | +|-------------|--------| +| 1 | 0.005 | + +## 8.14 UE UL power control operation with discontinuous UL DPCCH transmission operation + +### 8.14.1 Minimum requirement + +This test verifies that the UE follows only those TPC commands that correspond to the UL DPCCH slots which are transmitted. + +Test parameters are specified in Table 8.45A. The discontinuous UL DPCCH transmission is enabled during the test. The parameters for discontinuous UL DPCCH transmission operation are as specified in Table A.20A. Before the start of the tests, the UE transmit power shall be initialised to -15 dBm. An actual UE transmit power may vary from the target level of -15 dBm due to inaccurate UE output power step. + +After transmission gaps due to discontinuous uplink DPCCH transmission the uplink transmitter power difference shall be within the range as defined in Table 8.45B. The transmit power difference is defined as the difference between the power of the last slot transmitted before the gap and the power of first slot transmitted after the gap. The on power observation period is defined as the mean power over one timeslot excluding any transient periods. + +**Table 8.45A: Parameters for UE UL power control operation with discontinuous UL DPCCH transmission** + +| Parameter | Unit | Test 1 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------| +| Phase reference | - | P-CPICH | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -10 | +| F-DPCH $E_c/I_{or}$ | dB | -10 | +| F-DPCH slot format | - | 0 | +| $\hat{I}_{or1}$ | dBm/3.84 MHz | -60 | +| Power-Control-Algorithm | - | Algorithm 1 | +| UL Power Control step size, $\Delta_{TPC}$ | dB | 1 | +| Uplink TPC commands corresponding to the UL DPCCH slots which are transmitted | - | {0,1,0,1,0,1}
Note 1 | +| Propagation condition | - | Static without AWGN source $I_{oc}$ | +| Note 1: The sequence of uplink TPC commands corresponds to the UL DPCCH slots that are transmitted. During those slots which correspond to UL DPCCH slots that are not transmitted, UP-commands shall be transmitted. | | | + +**Table 8.45B: Test requirements for UE UL power control operation with discontinuous UL DPCCH transmission** + +| Parameter | Unit | Test 1 | | +|--------------------------------------|------|--------|-------| +| | | Lower | Upper | +| UE output power difference tolerance | dB | -2 | +4 | + +8.15 (void) + +8.16 (void) + +**Table 8.46: (void)** + +**Table 8.47: (void)** + +**Table 8.48: (void)** + +**Table 8.49: (void)** + +**Table 8.50: (void)** + +**Table 8.51: (void)** + +**Table 8.52: (void)** + +## 8.17 UE UL power control operation with Algorithm 3 + +### 8.17.1 Minimum requirement + +This test verifies that the UE follows only those TPC commands which are transmitted. + +Test parameters are specified in Table 8.53. The power control Algorithm 3 is enabled during the test. Before the start of the tests, the UE transmit power shall be initialised to -15 dBm. An actual UE transmit power may vary from the target level of -15 dBm due to inaccurate UE output power step. + +After transmission gaps due to discontinuous TPC symbol transmission the uplink transmitter power difference shall be within the range as defined in Table 8.54. The transmit power difference is defined as the difference in power between two transmitted slots corresponding to two consecutive received TPC commands. The on power observation period is defined as the mean power over one timeslot excluding any transient periods. + +**Table 8.53: Parameters for UE UL power control operation with algorithm 3** + +| Parameter | | Unit | Test 1 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------|-------------------------------------| +| | Phase reference | - | P-CPICH | +| | HS-SCCH_1 $E_c/I_{or}$ | dB | -10 | +| F-DPCH $E_c/I_{or}$ | dB | -10 | | +| F-DPCH slot format | - | 0 | | +| $\hat{I}_{or1}$ | dBm/3.84 MHz | -60 | | +| Power-Control-Algorithm | - | Algorithm 3 | | +| Decimation Factor | | 5-slot cycle | | +| UL Power Control step size, $\Delta_{TPC}$ | dB | 1 | | +| Uplink TPC commands corresponding to the UL DPCCH slots which are transmitted | - | {0,1,0,1,0,1,...}
Note 1 | | +| | Propagation condition | - | Static without AWGN source $I_{oc}$ | +| Note 1: The sequence of uplink TPC commands corresponds to the UL DPCCH slots that are transmitted. During those slots which correspond to UL DPCCH slots that are not transmitted, UP-commands shall be transmitted. | | | | + +**Table 8.54: Test requirements for UE UL power control operation with algorithm 3** + +| Parameter | Unit | Test 1 | | +|--------------------------------------|------|--------|-------| +| | | Lower | Upper | +| UE output power difference tolerance | dB | -2 | +4 | + +## 9 Performance requirement (HSDPA) + +The performance requirements for the UE in this clause apply for the reference measurement channels specified in Annex A.7, the propagation conditions specified in Annex B.2.2 and the Down link Physical channels specified in Annex C.5. The specific references are provided separately for each requirement. + +Unless otherwise stated the performance requirements are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna 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 antenna connector testing the fading of the signals and the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. + +## 9.1 (void) + +## 9.2 Demodulation of HS-DSCH (Fixed Reference Channel) + +The minimum performance requirement for a particular UE supporting one of the HS-DSCH categories 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 or 12 are determined according to Table 9.1. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 1, 2, 3, 4, 5, 6, 7, 8, 9 or 10 and supporting the optional enhanced performance requirements type 1 are determined according to Table 9.1AA. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 7, 8, 9 or 10 and supporting the optional enhanced performance requirements type 2 are determined according to Table 9.1AB. + +The minimum performance requirements for a particular UE supporting HS-DSCH category 13 or 14 are determined according to Table 9.1AB. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 7, 8, 9, 10, 13 or 14 and supporting the optional enhanced performance requirements type 3 are determined according to Table 9.1AC. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 15, 16, 17, 18, 19 or 20 are determined according to Table 9.1AC. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19 or 20 and supporting the optional enhanced performance requirements type 3i are determined according to Table 9.1AD. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 21, 22, 23 and 24 are determined according to Table 9.1 AE. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 21, 22, 23, 24, 25, 26, 27 or 28 and supporting the optional enhanced performance requirements type 3 are determined according to Table 9.1 AF. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 21, 22, 23, 24, 25, 26, 27 or 28 and supporting the optional enhanced performance requirements type 3i are determined according to Table 9.1 AG. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 29 and 31 are determined according to Table 9.1AH. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 29, 30, 31 and 32 and supporting the optional enhanced performance requirements type 3 are determined according to Table 9.1AI. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 29, 30, 31 and 32 and supporting the optional enhanced performance requirements type 3i are determined according to Table 9.1AJ. + +The minimum performance requirements for a particular UE supporting HS-DSCH category 35 are determined according to Table 9.1AK. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 35 and 36 and supporting the optional enhanced performance requirements type 3 are determined according to Table 9.1AL. + +The minimum performance requirements for a particular UE supporting one of the HS-DSCH categories 35 and 36 and supporting the optional enhanced performance requirements type 3i are determined according to Table 9.1AM. + +A UE supporting one of categories 21, 22, 23, 24, 29, 31 or 35 shall support either enhanced receiver type 2 requirements, or enhanced receiver type 3 requirements, or enhanced receiver type 3i requirements applicable for the other categories supported by this UE. + +A UE supporting one of categories 21, 22, 23, 24, 29, 31 or 35 supporting enhanced receiver type 3 requirements shall support either enhanced receiver type 3 requirements, or enhanced receiver type 3i requirements applicable for the other categories supported by this UE. + +A UE supporting one of categories 21, 22, 23, 24, 29, 31 or 35 supporting enhanced receiver type 3i requirements shall support enhanced receiver type 3i requirements applicable for the other categories supported by this UE. + +The additional minimum performance requirements for UE supporting one of the HS-DSCH categories 7, 8, 9, 10, 13, 14, 21, 22, 23, 24, 29, 31 or 35 and the MIMO only with single-stream restriction are indicated in Table 9.1AB, Table 9.1AC, 9.1AD, Table 9.1AE, Table 9.1AF, Table 9.1AG, Table 9.1AH, Table 9.1AI, Table 9.1AJ, Table 9.1AK, Table 9.1AL and Table 9.1AM. + +The additional minimum performance requirements for UE supporting one of the HS-DSCH categories 37 or 38 are indicated in Table 9.1AO. + +The additional minimum performance requirements for UE supporting one of the HS-DSCH categories 28, 30, 32, 34 or 36 and the MIMO with four transmit antennas only with dual-stream restriction capability are indicated in Table 9.1AF, Table 9.1AG, Table 9.1AI, Table 9.1AJ, Table 9.1AL and Table 9.1AM. + +The minimum performance requirements for a particular UE supporting the optional non-contiguous multi-cell operation are determined according to Table 9.1AN. + +For the requirements for UEs supporting HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35, 36, 37 or 38, when the carriers are located in the same frequency band or the carriers belong to the same cell group in Multiflow mode, the spacing of the carrier frequencies of the two cells shall be 5 MHz. + +For Multiflow HSDPA requirements in subclause 9.2.5, the serving HS-DSCH cell and the assisting serving HS-DSCH cell shall have the same carrier frequency, and the secondary serving HS-DSCH cell and the assisting secondary serving HS-DSCH cell shall have the same carrier frequency. + +For the requirements for UEs supporting HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 or 32 and supporting NC-4C-HSDPA, the spacing of the carrier frequencies belonging to the same subblock of carriers shall be 5MHz. The spacing of the highest carrier frequency of the lowest subblock of carriers and the lowest carrier frequency of the highest subblock of carriers depends on the configuration as indicated in Table 5.0aE and on the UE capability as indicated in the Information Element "Gap size", [7]. + +For single link performance with a UE supporting one of the categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35, 36, 37 or 38, and supporting enhanced receiver type 3i, the simplified testing method in Annex C.5.4 can be applied. + +For open loop diversity performance with a UE supporting one of the categories 29, 30, 31, 32, 35, 36, 37 or 38, and supporting enhanced receiver type 1, type 3 or type 3i, the simplified testing method in Annex C.5.4 can be applied. + +For MIMO performance with a UE supporting one of the categories 30 or 32, and supporting enhanced receiver type 3 or type 3i, the simplified testing method in Annex C.5.4 can be applied. + +For Multiflow performance with a UE supporting one of the categories 21, 22, 23, 24, 25, 26, 27 or 28, the simplified testing method in Annex C.5.4A can be applied. + +All aforementioned requirements are applicable to the UE when in CELL\_DCH state. Minimum performance requirements for UE being able to receive HS-DSCH and HS-SCCH in CELL\_FACH state are given in Section 9.6. + +The propagation conditions for this subclause are defined in table B.1B. + +**Table 9.1: FRC for minimum performance requirements for different HS-DSCH categories** + +| HS-DSCH category | Corresponding requirement | | | +|---------------------|---------------------------|---------------------|-----------------------| +| | Single Link
(Note 1) | Open Loop Diversity | Closed Loop Diversity | +| Category 1 | H-Set 1 | H-Set 1 | H-Set 1 | +| Category 2 | H-Set 1 | H-Set 1 | H-Set 1 | +| Category 3 | H-Set 2 | H-Set 2 | H-Set 2 | +| Category 4 | H-Set 2 | H-Set 2 | H-Set 2 | +| Category 5 | H-Set 3 | H-Set 3 | H-Set 3 | +| Category 6 | H-Set 3 | H-Set 3 | H-Set 3 | +| Category 7 (Note 1) | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 8 (Note 1) | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 9 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 10 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 11 | H-Set 4 | H-Set 4 | H-Set 4 | +| Category 12 | H-Set 5 | H-Set 5 | H-Set 5 | + +Note 1: Single link minimum performance requirements for Categories 7-10 in Pedestrian A with $\hat{I}_{or}/I_{oc}=10\text{dB}$ are set according to H-Set 6. Requirements in other conditions are according to H-Set 3. + +Note 2: For UE supporting the minimum performance requirements for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51 and for open loop transmit diversity in Table 9.53. + +**Table 9.1AA: FRC for enhanced performance requirements type 1 for different HS-DSCH categories** + +| HS-DSCH category | Corresponding requirement | | | +|---------------------|---------------------------|---------------------|-----------------------| +| | Single Link
(Note 1) | Open Loop Diversity | Closed Loop Diversity | +| Category 1 | H-Set 1 | H-Set 1 | H-Set 1 | +| Category 2 | H-Set 1 | H-Set 1 | H-Set 1 | +| Category 3 | H-Set 2 | H-Set 2 | H-Set 2 | +| Category 4 | H-Set 2 | H-Set 2 | H-Set 2 | +| Category 5 | H-Set 3 | H-Set 3 | H-Set 3 | +| Category 6 | H-Set 3 | H-Set 3 | H-Set 3 | +| Category 7 (Note 1) | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 8 (Note 1) | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 9 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | +| Category 10 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | + +Note 1: Single link enhanced performance requirements type 1 for Categories 7 - 10 in Pedestrian A with $\hat{I}_{or}/I_{oc}=10\text{dB}$ are set according to H-Set 6. Requirements in other conditions are according to H-Set 3. + +Note 2: For UE supporting the enhanced performance requirements type 1 for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. + +**Table 9.1AB: FRC for enhanced performance requirements type 2 for different HS-DSCH categories** + +| HS-DSCH category | Corresponding requirement | | | +|------------------|-------------------------------------|------------------------------|--------------------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity (Note 3) | +| Category 7 | H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | +| Category 8 | H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | +| Category 9 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | +| Category 10 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | +| Category 13 | H-Set-10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | +| Category 14 | H-Set-10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-set 6, H-Set 3 | + +Note 1: Single link enhanced performance requirements type 2 for Categories 9, 10, 13 and 14 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10. Single link enhanced performance requirements type 2 for Categories 13 and 14 with $\hat{I}_{or}/I_{oc} = 15$ and 18 dB are set according to H-Set 8. Single link enhanced performance requirements type 2 for Categories 7, 8, 9, 10, 13 and 14 with $\hat{I}_{or}/I_{oc} = 10$ dB are set according to H-Set 6. Requirements in other conditions are according to H-Set 3 minimum performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 minimum performance requirements. + +Note 3: Closed loop transmit diversity enhanced performance requirements type 2 for Categories 7, 8, 9, 10, 13 and 14 in Pedestrian B 3km/h with $\hat{I}_{or}/I_{oc} = 10$ dB and $E_c/I_{or} = -3$ dB are set according to H-Set 6. Requirements in other conditions are set according to H-Set 3 minimum performance requirements. + +Note 4: For UE supporting the enhanced performance requirements type 2 for HS-DSCH the minimum requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51 and for open loop transmit diversity in Table 9.53. + +Note 5: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G2, 9.22G2A, 9.22H2 and 9.22H2A and for HS-SCCH type 3 in Table 9.57A2, 9.57A4 and 9.57A6. + +**Table 9.1AC: FRC for enhanced performance requirements type 3 for different HS-DSCH categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-------------------------------------|------------------------------|--------------------------------|-------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity (Note 3) | MIMO (Note 4) | +| Category 7 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 8 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 9 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 10 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 13 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 14 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 15 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 16 | H-Set 10, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 17 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 18 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 19 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 11, H-Set 9 | +| Category 20 | H-Set 10, H-Set 8, H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 11, H-Set 9 | + +Note 1: Single link enhanced performance requirements type 3 for Categories 9, 10, 13, 14, 15, 16, 17, 18, 19 and 20 with $\hat{I}_{or} / I_{oc} = 4$ dB and 8 dB are set according to H-Set 10. +Single link enhanced performance requirements type 3 for Categories 13, 14, 17, 18, 19 and 20 with $\hat{I}_{or} / I_{oc} = 15$ dB and 18 dB are set according to H-Set 8. +Single link enhanced performance requirements type 3 for Categories 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19 and 20 with $\hat{I}_{or} / I_{oc} = 10$ dB and $\hat{I}_{or} / I_{oc} = 5$ dB are set according to H-Set 6. +Requirements in other conditions are according to H-Set 3 type1 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 3: Closed loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 4: MIMO requirements for categories 15-20, with $\hat{I}_{or} / I_{oc} = 6$ and 10 dB are set according to H-Set 9. +MIMO requirements for categories 19-20, with $\hat{I}_{or} / I_{oc} = 18$ dB are set according to H-Set 11. + +Note 5: For UE supporting the enhanced performance requirements type 3 for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. + +Note 6: For UEs supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 7: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. + +**Table 9.1AD: FRC for enhanced performance requirements type 3i for different HS-DSCH categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|----------------------------------------|---------------------------------|-----------------------------------|-------------------| +| | Single Link
(Note 1) | Open Loop Diversity
(Note 2) | Closed Loop Diversity
(Note 3) | MIMO
(Note 4) | +| Category 7 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 8 | H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 9 | H-Set10, H-Set 6,
H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 10 | H-Set10, H-Set 6,
H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 13 | H-Set10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 14 | H-Set10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | N/A | +| Category 15 | H-Set10, H-Set 6,
H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 16 | H-Set10, H-Set 6,
H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 17 | H-Set10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 18 | H-Set10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 9 | +| Category 19 | H-Set-10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 11, H-Set 9 | +| Category 20 | H-Set-10, H-Set 8,
H-Set 6, H-Set 3 | H-Set 3 | H-Set 3 | H-Set 11, H-Set 9 | + +Note 1: Single link enhanced performance requirements type 3i for Categories 7-20 with $\hat{I}_{or}/I_{oc}' = 0\text{dB}$ are set according to H-Set 6. Requirements in other conditions are according to type 3 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 3: Closed loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 4: MIMO requirements for categories 15-20, with $\hat{I}_{or}/I_{oc} = 6$ and 10 dB are set according to H-Set 9. +MIMO requirements for categories 19-20, with $\hat{I}_{or}/I_{oc} = 18$ dB are set according to H-Set 11. + +Note 5: For UE supporting the enhanced performance requirements type 3i for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. + +Note 6: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 7: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. + +**Table 9.1AE: FRC for enhanced performance requirements type 2 for different DC-HSDPA and DB-DC-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | +|------------------|-----------------------------------------|------------------------------|-----------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | +| Category 21 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | +| Category 22 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | +| Category 23 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | +| Category 24 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | + +Note 1: Single link enhanced performance requirements type 2 for categories 21, 22, 23 and 24 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10A. +Single link enhanced performance requirements type 2 for categories 23 and 24 with $\hat{I}_{or}/I_{oc} = 15$ and 18 dB are set according to H-Set 8A. +Single link enhanced performance requirements type 2 for categories 21, 22, 23 and 24 with $\hat{I}_{or}/I_{oc} = 10$ dB are set according to H-Set 6A. +Single link requirements for categories 21, 22, 23 and 24 in other conditions are according to H-Set 3A minimum performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3A minimum performance requirements. + +Note 3: For UE supporting the enhanced performance requirements type 2 for HS-DSCH the minimum requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51 and for open loop transmit diversity in Table 9.53. + +Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G2, 9.22G2A, 9.22H2 and 9.22H2A and for HS-SCCH type 3 in Table 9.57A2, 9.57A4 and 9.57A6. + +**Table 9.1AF: FRC for enhanced performance requirements type 3 for different DC-HSDPA and DB-DC-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|------------------------------|-----------------------|---------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | MIMO | +| Category 21 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 22 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 23 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 24 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 25 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 9A | +| Category 26 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 9A | +| Category 27 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 11A, H-Set 9A | +| Category 28 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 11A, H-Set 9A | + +Note 1: Single link enhanced performance requirements type 3 for categories 21, 22, 23, 24, 25, 26, 27 and 28 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10A. +Single link enhanced performance requirements type 3 for categories 23, 24, 27 and 28 with $\hat{I}_{or}/I_{oc} = 15$ dB and 18 dB are set according to H-Set 8A. +Single link enhanced performance requirements type 3 for categories 21, 22, 23, 24, 25, 26, 27 and 28 with $\hat{I}_{or}/I_{oc} = 10$ dB and $\hat{I}_{or}/I_{oc} = 5$ dB are set according to H-Set 6A. +Single link minimum requirements for categories 21, 22, 23, 24, 25, 26, 27 and 28 in other conditions are according to H-Set 3A type 1 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3A type 1 enhanced performance requirements. + +Note 3: MIMO requirements for categories 25-26, with $\hat{I}_{or}/I_{oc} = 6$ and 10 dB are set according to H-Set 9A. +MIMO requirements for categories 27-28, with $\hat{I}_{or}/I_{oc} = 18$ dB are set according to H-Set 11A. + +Note 4: For UE supporting the enhanced performance requirements type 3 for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. + +Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 6: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H1 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5, and 9.57A7. + +Note 7: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AG: FRC for enhanced performance requirements type 3i for different DC-HSDPA and DB-DC-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|------------------------------|-----------------------|---------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | MIMO | +| Category 21 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 22 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 23 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 24 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | N/A | +| Category 25 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 9A | +| Category 26 | H-Set-10A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 9A | +| Category 27 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 11A, H-Set 9A | +| Category 28 | H-Set-10A, H-Set 8A, H-Set 6A, H-Set 3A | H-Set 3A | N/A | H-Set 11A, H-Set 9A | + +Note 1: Single link enhanced performance requirements type 3i for Categories 21, 22, 23, 24, 25, 26, 27 and 28 with $\hat{I}_{or}/I_{oc} = 0\text{dB}$ are set according to H-Set 6A. Requirements in other conditions are according to type 3 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 3: For UE supporting the enhanced performance requirements type 3i for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54 + +Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5, 9.57A7. + +Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 6: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AH: FRC for enhanced performance requirements type 2 for different 4C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | +|------------------|-----------------------------------------|------------------------------|-----------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | +| Category 29 | H-Set-10B, H-Set 8B, H-Set 6B, H-Set 3B | H-Set 3B | N/A | +| Category 31 | H-Set-10C, H-Set 8C, H-Set 6C, H-Set 3C | H-Set 3C | N/A | + +Note 1: Single link enhanced performance requirements type 2 for categories 29 and 31 with $\hat{I}_{or} / I_{oc} = 4$ dB and 8 dB are set according to H-Set 10B and H-Set 10C respectively. + +Single link enhanced performance requirements type 2 for categories 29 and 31 with $\hat{I}_{or} / I_{oc} = 15$ and 18 dB are set according to H-Set 8B and H-Set 8C respectively. + +Single link enhanced performance requirements type 2 for categories 29 and 31 with $\hat{I}_{or} / I_{oc} = 10$ dB are set according to H-Set 6B and H-Set 6C respectively. + +Single link requirements for categories 29 and 31 in other conditions are according to H-Set 3B minimum performance requirements and H-Set 3C minimum performance requirements respectively. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3B minimum performance requirements and H-Set 3C minimum performance requirements. + +Note 3: For UE supporting the enhanced performance requirements type 2 for HS-DSCH the minimum requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51 and for open loop transmit diversity in Table 9.53. + +Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G2, 9.22G2A, 9.22H2 and 9.22H2A and for HS-SCCH type 3 in Table 9.57A2, 9.57A4 and 9.57A6. + +**Table 9.1A1: FRC for enhanced performance requirements type 3 for different 4C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|------------------------------|-----------------------|---------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | MIMO | +| Category 29 | H-Set 10B, H-Set 6B, H-Set 8B, H-Set 3B | H-Set 3B | N/A | N/B | +| Category 30 | H-Set 10B, H-Set 6B, H-Set 8B, H-Set 3B | H-Set 3B | N/A | H-Set 11B, H-Set 9B | +| Category 31 | H-Set 10C, H-Set 8C, H-Set 6C, H-Set 3C | H-Set 3C | N/A | N/A | +| Category 32 | H-Set 10C, H-Set 8C, H-Set 6C, H-Set 3C | H-Set 3C | N/A | H-Set 11C, H-Set 9C | + +- Note 1: Single link enhanced performance requirements type 3 for categories 29, 30 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10B. +Single link enhanced performance requirements type 3 for categories 31, 32 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10C. +Single link enhanced performance requirements type 3 for categories 29, 30 with $\hat{I}_{or}/I_{oc} = 15$ dB and 18 dB are set according to H-Set 8B. +Single link enhanced performance requirements type 3 for categories 31, 32 with $\hat{I}_{or}/I_{oc} = 15$ dB and 18 dB are set according to H-Set 8C. +Single link enhanced performance requirements type 3 for categories 29, 30 with $\hat{I}_{or}/I_{oc} = 10$ dB and $\hat{I}_{or}/I_{oc} = 5$ dB are set according to H-Set 6B. +Single link enhanced performance requirements type 3 for categories 31, 32 with $\hat{I}_{or}/I_{oc} = 10$ dB and $\hat{I}_{or}/I_{oc} = 5$ dB are set according to H-Set 6C. +Single link minimum requirements for categories 29, 30 in other conditions are according to H-Set 3B type 1 enhanced performance requirements. +Single link minimum requirements for categories 31, 32 in other conditions are according to H-Set 3C type 1 enhanced performance requirements. +- Note 2: Open loop transmit diversity requirements are set according to H-Set 3B type 1 enhanced performance requirements and H-Set 3C type 1 enhanced performance requirements. +- Note 3: MIMO requirements for categories 30 and 32, with $\hat{I}_{or}/I_{oc} = 6$ and 10 dB are set according to H-Set 9B and H-Set 9C respectively. MIMO requirements for categories 30 and 32, with $\hat{I}_{or}/I_{oc} = 18$ dB are set according to H-Set 11B and H-set 11C respectively. +- Note 4: For UE supporting the enhanced performance requirements type 3 for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. +- Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d, +- Note 6: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. +- Note 7: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AJ: FRC for enhanced performance requirements type 3i for different 4C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|------------------------------|-----------------------|---------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | MIMO | +| Category 29 | H-Set-10B, H-Set 6B, H-Set 8B, H-Set 3B | H-Set 3B | N/A | N/B | +| Category 30 | H-Set-10B, H-Set 6B, H-Set 8B, H-Set 3B | H-Set 3B | N/A | H-Set 11B, H-Set 9B | +| Category 31 | H-Set 10C, H-Set 8C, H-Set 6C, H-Set 3C | H-Set 3C | N/A | N/A | +| Category 32 | H-Set 10C, H-Set 8C, H-Set 6C, H-Set 3C | H-Set 3C | N/A | H-Set 11C, H-Set 9C | + +Note 1: Single link enhanced performance requirements type 3i for Categories 29, 30 with $\hat{I}_{or}/I_{oc} = 0\text{dB}$ are set according to H-Set 6B. Single link enhanced performance requirements type 3i for Categories 31, 32 with $\hat{I}_{or}/I_{oc} = 0\text{dB}$ are set according to H-Set 6C. Requirements in other conditions are according to type 3 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 3: For UE supporting the enhanced performance requirements type 3i for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54 + +Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. + +Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 6: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AK: FRC for enhanced performance requirements type 2 for the 8C-HSDPA category** + +| HS-DSCH category | Corresponding requirement | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------|-----------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | +| Category 35 | H-Set-10E, H-Set 8E, H-Set 6E, H-Set 3E | H-Set 3E | N/A | +|

Note 1: Single link enhanced performance requirements type 2 for category 35 with \hat{I}_{or} / I_{oc} = 4 dB and 8 dB are set according to H-Set 10E.

Single link enhanced performance requirements type 2 for category 35 with \hat{I}_{or} / I_{oc} = 15 and 18 dB are set according to H-Set 8E.

Single link enhanced performance requirements type 2 for category 35 with \hat{I}_{or} / I_{oc} = 10 dB are set according to H-Set 6E.

Single link requirements for category 35 in other conditions are according to H-Set 3E minimum performance requirements.

Note 2: Open loop transmit diversity requirements are set according to H-Set 3E minimum performance requirements.

Note 3: For UE supporting the enhanced performance requirements type 2 for HS-DSCH the minimum requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51 and for open loop transmit diversity in Table 9.53.

Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G2, 9.22G2A, 9.22H2 and 9.22H2A and for HS-SCCH type 3 in Table 9.57A2, 9.57A4 and 9.57A6.

| | | | + +**Table 9.1AL: FRC for enhanced performance requirements type 3 for different 8C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|------------------------------|-----------------------|---------------------| +| | Single Link (Note 1) | Open Loop Diversity (Note 2) | Closed Loop Diversity | MIMO | +| Category 35 | H-Set 10E, H-Set 6E, H-Set 8E, H-Set 3E | H-Set 3E | N/A | N/B | +| Category 36 | H-Set 10E, H-Set 6E, H-Set 8E, H-Set 3E | H-Set 3E | N/A | H-Set 11E, H-Set 9E | + +Note 1: Single link enhanced performance requirements type 3 for categories 35, 36 with $\hat{I}_{or}/I_{oc} = 4$ dB and 8 dB are set according to H-Set 10E. +Single link enhanced performance requirements type 3 for categories 35, 36 with $\hat{I}_{or}/I_{oc} = 15$ dB and 18 dB are set according to H-Set 8E. +Single link enhanced performance requirements type 3 for categories 35, 36 with $\hat{I}_{or}/I_{oc} = 10$ dB and $\hat{I}_{or}/I_{oc} = 5$ dB are set according to H-Set 6E. +Single link minimum requirements for categories 35, 36 in other conditions are according to H-Set 3E type 1 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3E type 1 enhanced performance requirements. + +Note 3: MIMO requirements for category 36, with $\hat{I}_{or}/I_{oc} = 6$ and 10 dB are set according to H-Set 9E. MIMO requirements for category 36, with $\hat{I}_{or}/I_{oc} = 18$ dB are set according to H-Set 11E. + +Note 4: For UE supporting the enhanced performance requirements type 3 for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54. + +Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 6: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. + +Note 7: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AM: FRC for enhanced performance requirements type 3i for different 8C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|-----------------------------------------|---------------------------------|-----------------------|---------------------| +| | Single Link
(Note 1) | Open Loop Diversity
(Note 2) | Closed Loop Diversity | MIMO | +| Category 35 | H-Set-10E, H-Set 6E, H-Set 8E, H-Set 3E | H-Set 3E | N/A | N/B | +| Category 36 | H-Set-10E, H-Set 6E, H-Set 8E, H-Set 3E | H-Set 3E | N/A | H-Set 11E, H-Set 9E | + +Note 1: Single link enhanced performance requirements type 3i for Categories 35, 36 with $\hat{I}_{or}/I_{oc}' = 0\text{dB}$ are set according to H-Set 6E. Requirements in other conditions are according to type 3 enhanced performance requirements. + +Note 2: Open loop transmit diversity requirements are set according to H-Set 3 type1 enhanced performance requirements. + +Note 3: For UE supporting the enhanced performance requirements type 3i for HS-DSCH the requirements for HS-SCCH Type 1 detection for single link are determined in Table 9.51A and for open loop transmit diversity in Table 9.54 + +Note 4: For UE supporting the MIMO only with single-stream restriction the additional minimum requirements for HS-DSCH are given in Table 9.22G3, 9.22G4, 9.22H3 and 9.22H4 and for HS-SCCH type 3 in Table 9.57A3, 9.57A5 and 9.57A7. + +Note 5: For UE supporting MIMO for HS-DSCH the requirements for HS-SCCH Type 3 detection are determined in Tables 9.56, Table 9.57, 9.57a, 9.57b, 9.57c and 9.57d. + +Note 6: For UE supporting MIMO mode with four transmit antennas only with dual-stream restriction capability the additional minimum requirements for HS-DSCH are given in Table 9.22K2, 9.22K4 and for HS-SCCH type 4 in Table 9.57B5, 9.57B6. + +**Table 9.1AN: Applicability of the requirements for UE supporting NC-4C-HSDPA** + +| HS-DSCH categories supported by the UE | NC-4C-HSDPA configurations | Applicable category for performance requirement | Applicable requirements | | | +|----------------------------------------|--------------------------------|-------------------------------------------------|--------------------------------------------------|--------------------------------------------------|---------------------------------------------------| +| | | | FRC for enhanced performance requirements type 2 | FRC for enhanced performance requirements type 3 | FRC for enhanced performance requirements type 3i | +| 21, 22, 23, 24, | I-1-5-1, IV-1-5-1 | 21, 22, 23, 24, | Table 9.1AE | Table 9.1AF | Table 9.1AG | +| 25, 26, 27, 28 (Note 1) | | 25, 26, 27, 28 | NA | Table 9.1AF | Table 9.1AG | +| 29, 31 | | 24 | Table 9.1AE | Table 9.1AF | Table 9.1AG | +| 30, 32 (Note 1) | | 28 | Table 9.1AE | Table 9.1AF | Table 9.1AG | +| 29, 31 | I-2-5-1, IV-2-10-1, IV-2-20-1 | 29 | Table 9.1AH | Table 9.1AI | Table 9.1AJ | +| 30, 32 (Note 1) | | 30 | NA | Table 9.1AI | Table 9.1AJ | +| 31 | IV-2-15-2, IV-2-25-2, I-3-10-1 | 31 | Table 9.1AH | Table 9.1AI | Table 9.1AJ | +| 32 (Note 1) | | 32 | NA | Table 9.1AI | Table 9.1AJ | + +Note 1. MIMO requirements are applicable for UE supporting NC-4C-HSDPA if UE has signalled support for this combination via IE "Non-contiguous multi-cell with MIMO" in 25.331 [7]. + +**Table 9.1AO: FRC UEs supporting MIMO mode with four transmit antennas for DC-HSDPA/DB-DC-HSDPA and 4C-HSDPA categories** + +| HS-DSCH category | Corresponding requirement | | | | +|------------------|---------------------------|--------------------------|-----------------------|---------------------------------------| +| | Single Link | Open Loop Diversity | Closed Loop Diversity | MIMO mode with four transmit antennas | +| Category 37 | Table 9.1AF, Table 9.1AG | Table 9.1AF, Table 9.1AG | N/A | H-Set 13A, H-Set 14A | +| Category 38 | Table 9.1AI, Table 9.1AJ | Table 9.1AI, Table 9.1AJ | N/A | H-Set 13C, H-Set 14C | + +Note 1: For UE supporting MIMO mode with four transmit antennas for HS-DSCH the requirements for HS-SCCH Type 4 detection are determined in Tables 9.57B2, 9.57B3. + +During the Fixed Reference Channel tests the behaviour of the Node-B emulator in response to the ACK/NACK signalling field of the HS-DPCCH is specified in Table 9.1A: + +**Table 9.1A: Node-B Emulator Behaviour in response to ACK/NACK/DTX** + +| HS-DPCCH ACK/NACK Field State | Node-B Emulator Behaviour | +|-------------------------------|---------------------------------------------------------------------------------------| +| ACK | ACK: new transmission using 1 st redundancy and constellation version (RV) | +| NACK | NACK: retransmission using the next RV (up to the maximum permitted number or RV's) | +| DTX | DTX: retransmission using the RV previously transmitted to the same H-ARQ process | + +NOTE: Performance requirements in this section assume a sufficient power allocation to HS-SCCH\_1 so that probability of reporting DTX is very low. + +## 9.2.1 Single Link performance + +The receiver single link performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) in different multi-path fading environments are determined by the information bit throughput R + +### 9.2.1.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 1/2/3/3A/3B/3C/3E (QPSK version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.2 and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.3. Enhanced performance requirements type 1 specified in Table 9.3A are based on receiver diversity. + +**Table 9.2: Test Parameters for Testing QPSK FRCs H-Set 1/H-Set 2/H-Set 3/H-Set 3A/H-Set 3B/H-Set 3C/3E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Redundancy and constellation version coding sequence | | {0,2,5,6} | | | | +| Maximum number of HARQ transmission | | 4 | | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.3: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 65 | 309 | +| | | -3 | N/A | 423 | +| 2 | PB3 | -6 | 23 | 181 | +| | | -3 | 138 | 287 | +| 3 | VA30 | -6 | 22 | 190 | +| | | -3 | 142 | 295 | +| 4 | VA120 | -6 | 13 | 181 | +| | | -3 | 140 | 275 | + +\* Notes: + +- 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +- 2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +- 3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). +- 4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for $R$ should be scaled (multiplied by 6). +- 5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for $R$ should be scaled (multiplied by 9). +- 6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for $R$ should be scaled (multiplied by 12). +- 7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for $R$ should be scaled (multiplied by 24) . + +**Table 9.3A: Enhanced requirement type 1 QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -12 | N/A | 247 | +| | | -9 | N/A | 379 | +| | | -6 | 195 | N/A | +| | | -3 | 329 | N/A | +| 2 | PB3 | -9 | N/A | 195 | +| | | -6 | 156 | 316 | +| | | -3 | 263 | N/A | +| 3 | VA30 | -9 | N/A | 212 | +| | | -6 | 171 | 329 | +| | | -3 | 273 | N/A | +| 4 | VA120 | -9 | N/A | 191 | +| | | -6 | 168 | 293 | +| | | -3 | 263 | N/A | + +\* Notes: + +- 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +- 2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +- 3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). +- 4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for $R$ should be scaled (multiplied by 6). +- 5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for $R$ should be scaled (multiplied by 9). +- 6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for $R$ should be scaled (multiplied by 12). +- 7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for $R$ should be scaled (multiplied by 24). + +### 9.2.1.2 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3 + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-set 1/2/3 (16QAM version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.4 and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.5. Enhanced performance requirements type 1 specified in Table 9.5A are based on receiver diversity. + +**Table 9.4: Test Parameters for Testing 16QAM FRCs H-Set 1/H-Set 2/H-Set 3** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | | | +| Redundancy and constellation version coding sequence | | {6,2,1,5} | | | | +| Maximum number of HARQ transmission | | 4 | | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.5: Minimum requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 198 | +| | | -3 | 368 | +| 2 | PB3 | -6 | 34 | +| | | -3 | 219 | +| 3 | VA30 | -6 | 47 | +| | | -3 | 214 | +| 4 | VA120 | -6 | 28 | +| | | -3 | 167 | + +\* Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for R should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, i integer). +3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for R should be scaled (multiplied by 3). + +**Table 9.5A: Enhanced requirement type 1 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -9 | 312 | +| | | -6 | 487 | +| 2 | PB3 | -6 | 275 | +| | | -3 | 408 | +| 3 | VA30 | -6 | 296 | +| | | -3 | 430 | +| 4 | VA120 | -6 | 271 | +| | | -3 | 392 | + +\* Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 1. + 2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for R should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, i integer). + 3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for R should be scaled (multiplied by 3). + +### 9.2.1.3 Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5 + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 4/5 specified in Annex A.7.1.4 and A.7.1.5 respectively, with the addition of the parameters in Table 9.6 and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.7 for H-Set 4 and table 9.8 for H-Set 5. + +**Table 9.6: Test Parameters for Testing QPSK FRCs H-Set 4/H-Set 5** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | | | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|--------|--------|--|--| +| Phase reference | | P-CPICH | | | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | | | +| Redundancy and constellation version coding sequence | | {0,2,5,6} | | | | | | +| Maximum number of HARQ transmission | | 4 | | | | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | | | + +**Table 9.7: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|----------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 72 | 340 | +| | | -3 | N/A | 439 | +| 2 | PB3 | -6 | 24 | 186 | +| | | -3 | 142 | 299 | +| 3 | VA30 | -6 | 19 | 183 | +| | | -3 | 148 | 306 | +| 4 | VA120 | -6 | 11 | 170 | +| | | -3 | 144 | 284 | + +**Table 9.8: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 5** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|----------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 98 | 464 | +| | | -3 | N/A | 635 | +| 2 | PB3 | -6 | 35 | 272 | +| | | -3 | 207 | 431 | +| 3 | VA30 | -6 | 33 | 285 | +| | | -3 | 213 | 443 | +| 4 | VA120 | -6 | 20 | 272 | +| | | -3 | 210 | 413 | + +### 9.2.1.4 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H-Set 6/6A/6B/6C/6E specified in Annex A.7.1.6 with the addition of the parameters in Table 9.8A and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.8B. Enhanced performance requirements type 1 as specified in Table 9.8B1 are based on receiver diversity. Enhanced performance requirements type 2 as specified in Table 9.8B2 are based on chip level equaliser. Enhanced performance requirements type 3 as specified in Table 9.8B3 and in Table 9.8B4 are based on receiver diversity and chip level equaliser. Enhanced performance requirements type 3i as specified in Table 9.8B5 are based on receiver diversity and interference-aware chip level equaliser. + +**Table 9.8A: Test Parameters for Testing QPSK FRCs H-Set 6/6A/6B/6C/6E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------|--------|--------|--------|--|--| +| Phase reference | | P-CPICH | | | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | | | +| Redundancy and constellation version coding sequence | | {0,2,5,6} | | | | | | +| Maximum number of HARQ transmission | | 4 | | | | | | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | | | | + +**Table 9.8B: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 1407 | +| | | -3 | 2090 | + +**Table 9.8B1: Enhanced requirements type 1 QPSK, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -12 | 672 | +| | | -9 | 1305 | + +**Table 9.8B2: Enhanced requirement type 2 QPSK, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 1494 | +| | | -3 | 2153 | +| 2 | PB3 | -6 | 1038 | +| | | -3 | 1744 | +| 3 | VA30 | -6 | 1142 | +| | | -3 | 1782 | +| 4 | VA120 | -6 | 909 | +| | | -3 | 1467 | + +\* Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 6. +2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for $R$ should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for $R$ should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.8B3: Enhanced requirement type 3 QPSK at $\hat{I}_{or} / I_{oc} = 10$ dB, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -9 | 1554 | +| | | -6 | 2495 | +| 2 | PB3 | -9 | 1190 | +| | | -6 | 2098 | +| 3 | VA30 | -9 | 1229 | +| | | -6 | 2013 | +| 4 | VA120 | -9 | 1060 | +| | | -6 | 1674 | + +\* Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 6. + 2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2). + 3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3). + 4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4). + 5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8). + +**Table 9.8B4: Enhanced requirement type 3 QPSK at $\hat{I}_{or}/I_{oc} = 5$ dB, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|-------------------------------|----------------------------------------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or}/I_{oc} = 5$ dB | +| 5 | PB3 | -6 | 1248 | +| | | -3 | 2044 | + +\* Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 6. + 2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2.0). + 3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3.0). + 4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4.0). + 5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8.0). + +**Table 9.8B5: Enhanced requirement type 3i QPSK at $\hat{I}_{or}/I_{oc}' = 0$ dB, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or}/I_{oc}' = 0$ dB
DIP1 = -2.75 dB
DIP2 = -7.64 dB
(Note 1) | +| 1 | PB3 | -6 | 691 | +| | | -3 | 1359 | +| 2 | VA30 | -6 | 661 | +| | | -3 | 1327 | + +\*Notes: 1) $I_{oc}/I_{oc}'$ is computed based on the relations shown in C.5.3. (Information only $I_{oc}/I_{oc}' = -5.27$ dB). + 2) The reference value R is for the Fixed Reference Channel (FRC) H-Set 6. + 3) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2). + 4) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3). + 5) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4). + 6) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8). + +### 9.2.1.5 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H Set-6/6A/6B/6C/6E specified in Annex A.7.1.6 with the addition of the parameters in Table 9.8C and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.8D. Enhanced performance requirements type 1 as specified in Table 9.8D1 are based on receiver diversity. Enhanced performance requirements type 2 as specified in Table 9.8D2 are based on chip level equaliser. Enhanced performance requirements type 3 as specified in Table 9.8D3 and in Table 9.8D4 are based on receiver diversity and chip level equaliser. + +**Table 9.8C: Test Parameters for Testing 16-QAM FRCs H-Set 6/6A/6B/6C/6E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | Test 5 | | | | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|--------|--------|--------|--|--|--| +| Phase reference | | P-CPICH | | | | | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | | | | | +| Redundancy and constellation version coding sequence | | {6,2,1,5} | | | | | | | | +| Maximum number of HARQ transmission | | 4 | | | | | | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | | | | | + +**Table 9.8D: Minimum requirement 16QAM, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 887 | +| | | -3 | 1664 | + +**Table 9.8D1: Enhanced requirements type 1 16QAM, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -9 | 912 | +| | | -6 | 1730 | + +**Table 9.8D2: Enhanced requirement type 2 16QAM, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 991 | +| | | -3 | 1808 | +| 2 | PB3 | -6 | 465 | +| | | -3 | 1370 | +| 3 | VA30 | -6 | 587 | +| | | -3 | 1488 | +| 4 | VA120 | -6 | 386 | +| | | -3 | 1291 | + +\* Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 6 +2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2) +3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3) +4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4) +5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8) + +**Table 9.8D3: Enhanced requirement type 3 16QAM at $\hat{I}_{or} / I_{oc} = 10$ dB, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 1979 | +| | | -3 | 3032 | +| 2 | PB3 | -6 | 1619 | +| | | -3 | 2464 | +| 3 | VA30 | -6 | 1710 | +| | | -3 | 2490 | +| 4 | VA120 | -6 | 1437 | +| | | -3 | 2148 | + +\* Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 6 +2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2) +3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3) +4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4) +5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8) + +**Table 9.8D4: Enhanced requirement type 3 16QAM at $\hat{I}_{or}/I_{oc} = 5$ dB, Fixed Reference Channel (FRC) H-Set 6/6A/6B/6C/6E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|-------------------------------|----------------------------------------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or}/I_{oc} = 5$ dB | +| 5 | PB3 | -6 | 779 | +| | | -3 | 1688 | + +\* Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 6 +2) For Fixed Reference Channel (FRC) H-Set 6A the reference values for R should be scaled (multiplied by 2) +3) For Fixed Reference Channel (FRC) H-Set 6B the reference values for R should be scaled (multiplied by 3) +4) For Fixed Reference Channel (FRC) H-Set 6C the reference values for R should be scaled (multiplied by 4) +5) For Fixed Reference Channel (FRC) H-Set 6E the reference values for R should be scaled (multiplied by 8) + +**9.2.1.6 Requirement 64QAM, Fixed Reference Channel (FRC) H-Set 8/8A/8B/8C/8E** + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channel H Set-8/8A/8B/8C/8E specified in Annex A.7.1.7 with the addition of the parameters in Table 9.8E and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.8F2 and 9.8F3. Enhanced performance requirements type 2 as specified in Table 9.8F2 are based on chip level equaliser. Enhanced performance requirements type 3 as specified in Table 9.8F3 are based on receiver diversity and chip level equaliser. + +**Table 9.8F1: Test Parameters for Testing 64QAM FRCs H-Set 8/8A/8B/8C/8E** + +| Parameter | Unit | Test 1 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|--------------|-----------| +| | Phase reference | P-CPICH | | +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | | dB | -24.4 | +| | Redundancy and constellation version coding sequence | | {6,2,1,5} | +| | Maximum number of HARQ transmission | | 4 | +| Note : The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | + +**Table 9.8F2: Enhanced requirement type 2 64QAM, Fixed Reference Channel (FRC) H-Set 8/8A/8B/8C/8E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -2$ dB | +| 1 | PA3 | 15 | 4507 | +| | | 18 | 5736 | +| * Notes: | 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 8.
2) For Fixed Reference Channel (FRC) H-Set 8A the reference values for R should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 8B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 8C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 8E the reference values for R should be scaled (multiplied by 8).
6) When determining $I_{or}/I_{oc}$ , the contribution from is not included. | | | + +**Table 9.8F3: Enhanced requirement type 3 64QAM, Fixed Reference Channel (FRC) H-Set 8/8A/8B/8C/8E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -2$ dB | +| 1 | PA3 | 15 | 6412 | +| | | 18 | 7638 | +| * Notes: | 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 8.
2) For Fixed Reference Channel (FRC) H-Set 8A the reference values for R should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 8B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 8C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 8E the reference values for R should be scaled (multiplied by 8).
6) When determining $I_{or}/I_{oc}$ , the contribution from is not included. | | | + +### 9.2.1.7 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channel H Set-10/10A/10B/10C/10E specified in Annex A.7.1.10 with the addition of the parameters in Table 9.8G and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum performance requirements as specified in table 9.8H and table 9.8H1. Enhanced performance requirements type 2 as specified in Table 9.8H are based on chip level equaliser. Enhanced performance requirements type 3 as specified in Table 9.8H1 are based on receiver diversity and chip level equaliser. + +**Table 9.8G: Test Parameters for Testing QPSK FRCs H-Set 10/10A/10B/10C/10E** + +| Parameter | Unit | Test 1 | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------| +| | Phase reference | | P-CPICH | +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | Redundancy and constellation version coding sequence | | {0, 2, 5, 6} | +| | Maximum number of HARQ transmission | | 4 | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | + +**Table 9.8H: Enhanced requirement type 2 QPSK, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E** + +| Test Number | Propagation Conditions | Reference value | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 4$ dB | +| 1 | VA3 | -2 | 1397 | +| * Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 10.
2) For Fixed Reference Channel (FRC) H-Set 10A the reference values for R should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 10B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 10C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 10E the reference values for R should be scaled (multiplied by 8). | | | | + +**Table 9.8H1: Enhanced requirement type 3 QPSK, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 4$ dB | +| 1 | VA3 | -2 | 2621 | +| * Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 10.
2) For Fixed Reference Channel (FRC) H-Set 10A the reference values for should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 10B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 10C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 10E the reference values for R should be scaled (multiplied by 8). | | | | + +### 9.2.1.8 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H Set-10/10A/10B/10C/10E specified in Annex A.7.1.10 with the addition of the parameters in Table 9.8I and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum performance requirements as specified in table 9.8J and table 9.8J1. Enhanced performance requirements type 2 as specified in Table 9.8J are based on chip level equaliser. Enhanced performance requirements type 3 as specified in Table 9.8J1 are based on receiver diversity and chip level equaliser. + +**Table 9.8I: Test Parameters for Testing 16-QAM FRCs H-Set 10/10A/10B/10C/10E** + +| Parameter | Unit | Test 1 | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----| +| | Phase reference | P-CPICH | | +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | Redundancy and constellation version coding sequence | {6, 2, 1, 5} | | +| | Maximum number of HARQ transmission | 4 | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | + +**Table 9.8J: Enhanced requirement type 2 16QAM, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 8$ dB | +| 1 | VA3 | -2 | 1726 | +| * Notes: | 1)The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 10.
2) For Fixed Reference Channel (FRC) H-Set 10A the reference values for $R$ should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 10B the reference values for $R$ should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 10C the reference values for $R$ should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 10E the reference values for $R$ should be scaled (multiplied by 8). | | | + +**Table 9.8J1: Enhanced requirement type 3 16QAM, Fixed Reference Channel (FRC) H-Set 10/10A/10B/10C/10E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 8$ dB | +| 1 | VA3 | -2 | 3396 | +| * Notes: | 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 10.
2) For Fixed Reference Channel (FRC) H-Set 10A the reference values for R should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 10B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 10C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 10E the reference values for R should be scaled (multiplied by 8). | | | + +## 9.2.2 Open Loop Diversity performance + +The receiver single open loop transmit diversity performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) in multi-path fading environments are determined by the information bit throughput R. + +### 9.2.2.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-Set 1/2/3/3A/3B/3C/3E (QPSK version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.9 and the downlink physical channel setup according to table C.9. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.10. Enhanced performance requirements type 1 specified in Table 9.10A are based on receiver diversity. + +**Table 9.9: Test Parameters for Testing QPSK FRCs H-Set 1/2/3/3A/3B/3C/3E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|--------| +| Phase reference | | P-CPICH | | | +| $I_{oc}$ | | dBm/3.84 MHz | | | +| Redundancy and constellation version | | | | | +| coding sequence | | {0,2,5,6} | | | +| Maximum number of HARQ transmission | | 4 | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | + +**Table 9.10: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 77 | 375 | +| | | -3 | 180 | 475 | +| 2 | PB3 | -6 | 20 | 183 | +| | | -3 | 154 | 274 | +| 3 | VA30 | -6 | 15 | 187 | +| | | -3 | 162 | 284 | + +\* Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for $R$ should be scaled (multiplied by 6). +5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for $R$ should be scaled (multiplied by 9). +6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for $R$ should be scaled (multiplied by 12). +7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for $R$ should be scaled (multiplied by 24). + +**Table 9.10A: Enhanced requirement type 1 QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -12 | N/A | 268 | +| | | -9 | N/A | 407 | +| | | -6 | 197 | N/A | +| | | -3 | 333 | N/A | +| 2 | PB3 | -9 | N/A | 183 | +| | | -6 | 152 | 288 | +| | | -3 | 251 | N/A | +| 3 | VA30 | -9 | N/A | 197 | +| | | -6 | 164 | 307 | +| | | -3 | 261 | N/A | + +\* Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for $R$ should be scaled (multiplied by 6). +5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for $R$ should be scaled (multiplied by 9). +6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for $R$ should be scaled (multiplied by 12). +7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for $R$ should be scaled (multiplied by 24). + +### 9.2.2.2 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-Set 1/2/3/3A/3B/3C/3E (16QAM version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.11 and the downlink physical channel setup according to table C.9. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.12. Enhanced performance requirements type 1 specified in Table 9.12A are based on receiver diversity. + +**Table 9.11: Test Parameters for Testing 16QAM FRCs H-Set 1/2/3/3A/3B/3C/3E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------|--------|--------| +| Phase reference | | P-CPICH | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | +| Redundancy and
constellation version
coding sequence | | {6,2,1,5} | | | +| Maximum number of
HARQ transmission | | 4 | | | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.12: Minimum requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 295 | +| | | -3 | 463 | +| 2 | PB3 | -6 | 24 | +| | | -3 | 243 | +| 3 | VA30 | -6 | 35 | +| | | -3 | 251 | + +\* Notes: + +- 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +- 2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +- 3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). +- 4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for $R$ should be scaled (multiplied by 6). +- 5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for $R$ should be scaled (multiplied by 9). +- 6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for $R$ should be scaled (multiplied by 12). +- 7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for $R$ should be scaled (multiplied by 24). + +**Table 9.12A: Enhanced requirement type 1 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3/3A/3B/3C/3E** + +| Test Number | Propagation Conditions | Reference value | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -9 | 340 | +| | | -6 | 513 | +| 2 | PB3 | -6 | 251 | +| | | -3 | 374 | +| 3 | VA30 | -6 | 280 | +| | | -3 | 398 | +| * Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 1.
2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for R should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, i integer).
3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 3A the reference values for R should be scaled (multiplied by 6).
5) For Fixed Reference Channel (FRC) H-Set 3B the reference values for R should be scaled (multiplied by 9).
6) For Fixed Reference Channel (FRC) H-Set 3C the reference values for R should be scaled (multiplied by 12).
7) For Fixed Reference Channel (FRC) H-Set 3E the reference values for R should be scaled (multiplied by 24). | | | | + +**9.2.2.3 Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5** + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-Set 4/5 specified in Annex A.7.1.4 and A.7.1.5 respectively, with the addition of the parameters in Table 9.13 and the downlink physical channel setup according to table C.9. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.14 for H-Set 4 and table 9.15 for H-Set 5. + +**Table 9.13: Test Parameters for Testing QPSK FRCs H-Set 4/H-Set 5** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | | +| Redundancy and constellation version coding sequence | | {0,2,5,6} | | | | +| Maximum number of HARQ transmission | | 4 | | | | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | | + +**Table 9.14: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 70 | 369 | +| | | -3 | 171 | 471 | +| 2 | PB3 | -6 | 14 | 180 | +| | | -3 | 150 | 276 | +| 3 | VA30 | -6 | 11 | 184 | +| | | -3 | 156 | 285 | + +**Table 9.15: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 5** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 116 | 563 | +| | | -3 | 270 | 713 | +| 2 | PB3 | -6 | 30 | 275 | +| | | -3 | 231 | 411 | +| 3 | VA30 | -6 | 23 | 281 | +| | | -3 | 243 | 426 | + +## 9.2.3 Closed Loop Diversity Performance + +The closed loop transmit diversity (Mode 1) performance of the High Speed Physical Downlink Shared Channel (HS-PDSCH) in multi-path fading environments are determined by the information bit throughput $R$ . + +### 9.2.3.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3 + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-Set 1/2/3 (QPSK version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.16 and the downlink physical channel setup according to table C.10. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.17. Enhanced performance requirements type 1 specified in Table 9.17A are based on receiver diversity. + +**Table 9.16: Test Parameters for Testing QPSK FRCs H-Set 1/H-Set 2/H-Set 3** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--------------|--------|-----------| +| | Phase reference | P-CPICH | | | +| | $I_{oc}$ | dBm/3.84 MHz | | -60 | +| | DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | | 0 | +| | Redundancy and
constellation version
coding sequence | | | {0,2,5,6} | +| | Maximum number of
HARQ transmission | | | 4 | +| | Feedback Error Rate | % | | 4 | +| | Closed loop timing
adjustment mode | | | 1 | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.17: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 118 | 399 | +| | | -3 | 225 | 458 | +| 2 | PB3 | -6 | 50 | 199 | +| | | -3 | 173 | 301 | +| 3 | VA30 | -6 | 47 | 204 | +| | | -3 | 172 | 305 | + +\* Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). + +**Table 9.17A: Enhanced requirement type 1 QPSK, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|------------------------------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -12 | N/A | 297 | +| | | -9 | N/A | 410 | +| | | -6 | 242 | N/A | +| | | -3 | 369 | N/A | +| 2 | PB3 | -9 | N/A | 194 | +| | | -6 | 170 | 308 | +| | | -3 | 272 | N/A | +| 3 | VA30 | -9 | N/A | 204 | +| | | -6 | 172 | 315 | +| | | -3 | 270 | N/A | + +\* Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for $R$ should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of $i+1/2$ are rounded up to $i+1$ , $i$ integer). +3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for $R$ should be scaled (multiplied by 3). + +### 9.2.3.2 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3 + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-set 1/2/3 (16QAM version) specified in Annex A.7.1.1, A.7.1.2 and A.7.1.3 respectively, with the addition of the parameters in Table 9.18 and the downlink physical channel setup according to table C.10. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.19. Enhanced performance requirements type 1 specified in Table 9.19A are based on receiver diversity. + +**Table 9.18: Test Parameters for Testing 16-QAM FRCs H-Set 1/H-Set 2/H-Set 3** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|-----------| +| Phase reference | | P-CPICH | | | +| $I_{oc}$ | | dBm/3.84 MHz | | -60 | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | | | 0 | +| Redundancy and
constellation version
coding sequence | | | | {6,2,1,5} | +| Maximum number of
HARQ transmission | | | | 4 | +| Feedback Error Rate | % | | | 4 | +| Closed loop timing
adjustment mode | | | | 1 | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | + +**Table 9.19: Minimum requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 361 | +| | | -3 | 500 | +| 2 | PB3 | -6 | 74 | +| | | -3 | 255 | +| 3 | VA30 | -6 | 84 | +| | | -3 | 254 | +| * Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 1
2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for R should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, I integer)
3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for R should be scaled (multiplied by 3 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, I integer) | | | | + +**Table 9.19A: Enhanced requirement type 1 16QAM, Fixed Reference Channel (FRC) H-Set 1/2/3** + +| Test Number | Propagation Conditions | Reference value | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps) *
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -9 | 376 | +| | | -6 | 532 | +| 2 | PB3 | -6 | 267 | +| | | -3 | 393 | +| 3 | VA30 | -6 | 279 | +| | | -3 | 404 | +| * Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 1.
2) For Fixed Reference Channel (FRC) H-Set 2 the reference values for R should be scaled (multiplied by 1.5 and rounding to the nearest integer t-put in kbps, where values of i+1/2 are rounded up to i+1, I integer).
3) For Fixed Reference Channel (FRC) H-Set 3 the reference values for R should be scaled (multiplied by 3). | | | | + +### 9.2.3.3 Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4/5 + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 4/5 specified in Annex A.7.1.4 and A.7.1.5 respectively, with the addition of the parameters in Table 9.20 and the downlink physical channel setup according to table C.10. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.21 for H-Set 4 and table 9.22 for H-Set 5. + +**Table 9.20: Test Parameters for Testing QPSK FRCs H-Set 4/H-Set 5** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--------------|--------|-----------| +| | Phase reference | P-CPICH | | | +| | $I_{oc}$ | dBm/3.84 MHz | | -60 | +| | DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | | 0 | +| | Redundancy and
constellation version
coding sequence | | | {0,2,5,6} | +| | Maximum number of
HARQ transmission | | | 4 | +| | Feedback Error Rate | % | | 4 | +| | Closed loop timing
adjustment mode | | | 1 | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.21: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 4** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|----------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 114 | 398 | +| | | -3 | 223 | 457 | +| 2 | PB3 | -6 | 43 | 196 | +| | | -3 | 167 | 292 | +| 3 | VA30 | -6 | 40 | 199 | +| | | -3 | 170 | 305 | + +**Table 9.22: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 5** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|---------------------------------|----------------------------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 0$ dB | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PA3 | -6 | 177 | 599 | +| | | -3 | 338 | 687 | +| 2 | PB3 | -6 | 75 | 299 | +| | | -3 | 260 | 452 | +| 3 | VA30 | -6 | 71 | 306 | +| | | -3 | 258 | 458 | + +### 9.2.3.4 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 6 + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H-Set 6 specified in Annex A.7.1.6 with the addition of the parameters in Table 9.22A and the downlink physical channel setup according to table C.10. + +Using this configuration the throughput shall meet or exceed the requirements specified in table 9.22B. Enhanced performance requirements type 2 as specified in Table 9.22B are based on chip level equaliser. + +**Table 9.22A: Test Parameters for Testing QPSK FRCs H-Set 6** + +| Parameter | Unit | Test 1 | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------| +| | Phase reference | | P-CPICH | +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | +| | Redundancy and
constellation version
coding sequence | | {0,2,5,6} | +| | Maximum number of
HARQ transmission | | 4 | +| | Feedback Error Rate | % | 4 | +| | Closed loop timing
adjustment mode | | 1 | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | + +**Table 9.22B: Enhanced requirement type 2 QPSK, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|---------------------------------|-----------------------------------------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PB3 | -3 | 1536 | + +### 9.2.3.5 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 6 + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channel H Set-6 specified in Annex A.7.1.6 with the addition of the parameters in Table 9.22C and the downlink physical channel setup according to table C.10. + +Using this configuration the throughput shall meet or exceed the requirements specified in table 9.22D. Enhanced performance requirements type 2 specified in Table 9.22D are based on chip level equaliser. + +**Table 9.22C: Test Parameters for Testing 16-QAM FRCs H-Set 6** + +| Parameter | | Unit | Test 1 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------|-----------| +| | Phase reference | | P-CPICH | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| DPCH frame offset ( $\tau_{DPCH,n}$ ) | | Chip | 0 | +| Redundancy and constellation version coding sequence | | | {6,2,1,5} | +| Maximum number of HARQ transmission | | | 4 | +| Feedback Error Rate | | % | 4 | +| Closed loop timing adjustment mode | | | 1 | +| Note: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | + +**Table 9.22D: Enhanced requirement type 2 16QAM, Fixed Reference Channel (FRC) H-Set 6** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|------------------------------|-----------------------------------------------------| +| | | HS-PDSCH $E_c / I_{or}$ (dB) | T-put $R$ (kbps)
$\hat{I}_{or} / I_{oc} = 10$ dB | +| 1 | PB3 | -3 | 1154 | + +## 9.2.4 MIMO Performance + +The MIMO performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) in multi-path fading environments is determined by the information bit throughput $R$ . + +### 9.2.4.1 Requirement Fixed Reference Channel (FRC) H-Set 9/9A/9B/9C/9E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-Set 9/9A/9B/9C/9E specified in Annex A.7.1.9, with the addition of the parameters in Table 9.22E1 and the downlink physical channel setup according to Table C.9 and Table C.12D. Precoding weight set restriction shall not be enabled. + +The primary precoding vector signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred primary precoding vector reported immediately before the start of the HS-SCCH subframe. + +The determination of applied precoding vector for single transport block transmission shall be as follows: the reported preferred primary precoding vector shall be applied to the primary transport block. + +The determination of applied precoding vector for two transport block transmission shall be as follows: If the CQI reported by the UE indicates a preference for a single transport block, the preferred primary precoding vector shall be applied to the primary transport block. If the CQI reported by the UE indicates a preference for two transport blocks, and the preferred primary precoding vector corresponds to the highest reported CQI value, the preferred primary precoding vector shall be applied to the primary transport block. If the CQI reported by the UE indicates a preference + +for two transport blocks, and the preferred primary precoding vector does not correspond to the highest reported CQI value, the preferred primary precoding vector shall be applied to the secondary transport block. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22E2 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22E3 with the downlink physical channel setup in Table C.12D. + +**Table 9.22E1: Test Parameters for Testing MIMO FRC H-Set 9/9A/9B/9C/9E** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------------------------------|--------------|-------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------|--------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | | | | +| Redundancy and
constellation version
coding sequence | | {0,3,2,1} for 16-QAM and QPSK | | | | +| Maximum number of
HARQ transmission | | 4 | | | | +| MIMO
N_cqi_typeA/M_cqi ratio | | 1/1 | | 1/2 | | +| PCI/CQI reporting Error
Rate | % | 0 | | 0 | | +| Number of transport
blocks | | 2 | | 1 | | +| Modulation | | Primary Transport
Block: 16QAM
Secondary Transport
Block: QPSK | | Primary Transport
Block: 16QAM
Secondary Transport
Block is not used. | | + +**Table 9.22E2: Minimum requirement MIMO, Fixed Reference Channel (FRC) H-Set 9/9A/9B/9C/9E with downlink physical channel setup in Table C.9** + +| Test
Number | Propagation
Conditions | Reference value | | +|----------------|---------------------------|------------------------------|----------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -2$ dB | +| 1 | PA3 | 10 | 5563 | +| 2 | VA3 | 10 | 4347 | +| 3 | PA3 | 6 | 3933 | +| 4 | VA3 | 6 | 3011 | + +\* Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 9. +2) For Fixed Reference Channel (FRC) H-Set 9A the reference values for R should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 9B the reference values for R should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 9C the reference values for R should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 9E the reference values for R should be scaled (multiplied by 8). + +**Table 9.22E3: Minimum requirement MIMO, Fixed Reference Channel (FRC) H-Set 9/9A/9B/9C/9E with downlink physical channel setup in Table C.12D** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|------------------------------|----------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -2$ dB | +| 1 | PA3 | 10 | 5394 | +| 2 | VA3 | 10 | 4344 | +| 3 | PA3 | 6 | 3742 | +| 4 | VA3 | 6 | 2926 | + +\* Notes: 1)The reference value R is for the Fixed Reference Channel (FRC) H-Set 9. +2) For Fixed Reference Channel (FRC) H-Set 9A the reference values for R should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 9B the reference values for R should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 9C the reference values for R should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 9E the reference values for R should be scaled (multiplied by 8). + +#### 9.2.4.2 Requirement Fixed Reference Channel (FRC) H-Set 11/11A/11B/11C/11E + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-Set 11/11A/11B/11C/11E specified in Annex A.7.1.11, with the addition of the parameters in Table 9.22F1 and the downlink physical channel setup according to Table C.9 and Table C.12D. Precoding weight set restriction shall not be enabled. + +The primary precoding vector signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred primary precoding vector reported immediately before the start of the HS-SCCH subframe. + +The determination of applied precoding vector for two transport block transmission shall be as follows: If the CQI reported by the UE indicates a preference for a single transport block, the preferred primary precoding vector shall be applied to the primary transport block. If the CQI reported by the UE indicates a preference for two transport blocks, and the preferred primary precoding vector corresponds to the highest reported CQI value, the preferred primary precoding vector shall be applied to the primary transport block. If the CQI reported by the UE indicates a preference for two transport blocks, and the preferred primary precoding vector does not correspond to the highest reported CQI value, the preferred primary precoding vector shall be applied to the secondary transport block. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22F2 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22F3 with the downlink physical channel setup in Table C.12D. + +**Table 9.22F1: Test Parameters for Testing MIMO FRC H-Set 11/11A/11B/11C/11E** + +| Parameter | Unit | Test 1 | +|------------------------------------------------------------|--------------|--------------------------------------------------------------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | +| Redundancy and
constellation version
coding sequence | | {0,3,2,1} for 16QAM
and 64QAM | +| Maximum number of
HARQ transmission | | 4 | +| MIMO
$N_{cqi\_typeA}/M_{cqi}$
ratio | | 1/1 | +| PCI/CQI reporting
Error Rate | % | 0 | +| Number of transport
blocks | | 2 | +| Modulation | | Primary Transport
Block: 64QAM
Secondary Transport
Block: 16QAM | + +**Table 9.22F2: Minimum requirement MIMO, Fixed Reference Channel (FRC) H-Set 11/11A/11B/11C/11E with downlink physical channel setup in Table C.9** + +| Test
Number | Propagation
Conditions | Reference value | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -1.5$ dB | +| 1 | PA3 | 18 | 9980 | +| * Notes: | 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 11.
2) For Fixed Reference Channel (FRC) H-Set 11A the reference values for $R$ should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 11B the reference values for $R$ should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 11C the reference values for $R$ should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 11E the reference values for $R$ should be scaled (multiplied by 8). | | | + +**Table 9.22F3: Minimum requirement MIMO, Fixed Reference Channel (FRC) H-Set 11/11A/11B/11C/11E with downlink physical channel setup in Table C.12D** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -1.5$ dB | +| 1 | PA3 | 18 | 9880 | +| * Notes: | 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 11.
2) For Fixed Reference Channel (FRC) H-Set 11A the reference values for R should be scaled (multiplied by 2).
3) For Fixed Reference Channel (FRC) H-Set 11B the reference values for R should be scaled (multiplied by 3).
4) For Fixed Reference Channel (FRC) H-Set 11C the reference values for R should be scaled (multiplied by 4).
5) For Fixed Reference Channel (FRC) H-Set 11E the reference values for R should be scaled (multiplied by 8). | | | + +## 9.2.4A MIMO only with single-stream restriction Performance + +The MIMO only with single-stream performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) in multi-path fading environments are determined by the information bit throughput R. + +### 9.2.4A.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 1/1A/1B/1C/1E (QPSK version) specified in Annex A.7.1.1, with the addition of the parameters in Table 9.22G1 and the downlink physical channel setup according to Table C.9 and Table C.12D. Precoding weight set restriction shall be enabled for the tests with the downlink physical channel setup according to Table C.12D, defined in Table 9.22G2A and Table 9.22G4. Precoding weight set restriction shall not be enabled for the tests with the downlink physical channel setup according to Table C.9, defined in Table 9.22G2 and Table 9.22G3. + +The primary precoding vector signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred primary precoding vector reported immediately before the start of the HS-SCCH subframe. + +The determination of applied precoding vector for single transport block transmission shall be as follows: the reported preferred primary precoding vector shall be applied to the primary transport block. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22G2 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22G2A with the downlink physical channel setup in Table C.12D. If UE supports enhanced performance requirements type 3, the throughput shall meet or exceed the minimum requirements specified in Table 9.22G3 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22G4 with the downlink physical channel setup in Table C.12D. The performance requirements specified in Table 9.22G2 and Table 9.22G2A are based on chip level equaliser and the performance requirements specified in Table 9.22G3 and Table 9.22G4 are based on chip level equaliser with receiver diversity. + +**Table 9.22G1: Test Parameters for Testing QPSK FRCs H-Set 1/1A/1B/1C/1E** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------| +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | Redundancy and constellation version coding sequence | | {0,3,2,1} | +| | Maximum number of HARQ transmission | | 4 | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | + +**Table 9.22G2: Enhanced requirement type 2 QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.9** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 0 | 305 | +| | 2 | VA3 | 3 | 357 | + +\*Notes: + +- 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +- 2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +- 3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +- 4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +- 5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22G2A: Enhanced requirement type 2 QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.12D** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 0 | 279 | +| | 2 | VA3 | 3 | 345 | + +\*Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22G3: Enhanced requirement type 3 QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.9** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -6$ dB | +| | 1 | PA3 | 0 | 306 | +| | 2 | VA3 | 0 | 236 | + +\*Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22G4: Enhanced requirement type 3 QPSK, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.12D** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -6$ dB | +| | 1 | PA3 | 0 | 285 | +| | 2 | VA3 | 0 | 230 | + +\*Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 1. + 2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for R should be scaled (multiplied by 2). + 3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for R should be scaled (multiplied by 3). + 4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for R should be scaled (multiplied by 4). + 5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for R should be scaled (multiplied by 8). + +## 9.2.4A.2 Requirement 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 1/1A/1B/1C/1E (16QAM version) specified in Annex A.7.1.1, with the addition of the parameters in Table 9.22H1 and the downlink physical channel setup according to Table C.9 and Table C.12D. Precoding weight set restriction shall be enabled for the tests with the downlink physical channel setup according to Table C.12D, defined in Table 9.22H2A and 9.22H4. Precoding weight set restriction shall not be enabled for the tests with the downlink physical channel setup according to Table C.9, defined in Table 9.22H2 and Table 9.22H3. + +The primary precoding vector signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred primary precoding vector reported immediately before the start of the HS-SCCH subframe. + +The determination of applied precoding vector for single transport block transmission shall be as follows: the reported preferred primary precoding vector shall be applied to the primary transport block. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22H2 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22H2A with the downlink physical channel setup in Table C.12D. If UE supports enhanced performance requirements type 3, the throughput shall meet or exceed the minimum requirements specified in Table 9.22H3 with the downlink physical channel setup in Table C.9, and the minimum requirements specified in Table 9.22H4 with the downlink physical channel setup in Table C.12D. The performance requirements specified in Table 9.22H2 and Table 9.22H2A are based on chip level equaliser and the performance requirements specified in Table 9.22H3 and Table 9.22H4 are based on chip level equaliser with receiver diversity. + +**Table 9.22H1: Test Parameters for Testing 16QAM FRCs H-Set 1/1A/1B/1C/1E** + +| Parameter | Unit | Test 1 | Test 2 | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------| +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | Redundancy and constellation version coding sequence | | {0,3,2,1} | +| | Maximum number of HARQ transmission | | 4 | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | + +**Table 9.22H2: Enhanced requirement type 2 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.9** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 3 | 394 | +| | 2 | VA3 | 6 | 388 | + +\*Notes: + +- 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +- 2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +- 3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +- 4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +- 5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22H2A: Enhanced requirement type 2 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.12D** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 3 | 363 | +| | 2 | VA3 | 6 | 380 | + +\*Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22H3: Enhanced requirement type 3 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.9** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 0 | 385 | +| | 2 | VA3 | 3 | 437 | + +\*Notes: 1) The reference value $R$ is for the Fixed Reference Channel (FRC) H-Set 1. +2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for $R$ should be scaled (multiplied by 2). +3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for $R$ should be scaled (multiplied by 3). +4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for $R$ should be scaled (multiplied by 4). +5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for $R$ should be scaled (multiplied by 8). + +**Table 9.22H4: Enhanced requirement type 3 16QAM, Fixed Reference Channel (FRC) H-Set 1/1A/1B/1C/1E with downlink physical channel setup in Table C.12D** + +| | Test Number | Propagation Conditions | Reference value | | +|--|-------------|------------------------|------------------------------|---------------------------------------------------------| +| | | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps)*
HS-PDSCH
$E_c / I_{or} = -3$ dB | +| | 1 | PA3 | 0 | 365 | +| | 2 | VA3 | 3 | 433 | + +\*Notes: 1) The reference value R is for the Fixed Reference Channel (FRC) H-Set 1. + 2) For Fixed Reference Channel (FRC) H-Set 1A the reference values for R should be scaled (multiplied by 2). + 3) For Fixed Reference Channel (FRC) H-Set 1B the reference values for R should be scaled (multiplied by 3). + 4) For Fixed Reference Channel (FRC) H-Set 1C the reference values for R should be scaled (multiplied by 4). + 5) For Fixed Reference Channel (FRC) H-Set 1E the reference values for R should be scaled (multiplied by 8). + +## 9.2.4B Four Transmit Antennas MIMO Performance + +The four transmit antennas MIMO performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) in multi-path fading environments is determined by the information bit throughput R. + +### 9.2.4B.1 Requirement Fixed Reference Channel (FRC) H-Set 13A/13C + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-Set 13A/13C specified in Annex A.7.1.13, with the addition of the parameters in Table 9.22I1 and the downlink physical channel setup according to Table C.12F. + +The precoding weights signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred precoding control index reported immediately before the start of the HS-SCCH subframe. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22I2 with the downlink physical channel setup in Table C.12F. + +**Table 9.22I1: Test Parameters for Testing MIMO mode with Four Transmit Antennas, FRC H-Set 13A/13C** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------------------------------|--------------|--------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------|--------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | | | | +| Redundancy and
constellation version
coding sequence | | {0,3,2,1} for 16-QAM and QPSK | | | | +| Maximum number of
HARQ transmission | | 4 | | | | +| MIMO
N_cqi_typeA/M_cqi ratio | | 1/1 | | 1/1 | | +| PCI/CQI reporting Error
Rate | % | 0 | | 0 | | +| Number of transport
blocks | | Up to 4 | | Up to 2 | | +| Modulation | | First and fourth
Transport Block:
16QAM
Secondary and third
Transport Block:
QPSK | | Primary Transport
Block: 16QAM
Secondary Transport
Block: QPSK. | | + +**Table 9.22I2: Minimum requirement for MIMO mode with four transmit antennas, Fixed Reference Channel (FRC) H-Set 13A/13C with downlink physical channel setup in Table C.12F** + +| Test
Number | Propagation
Conditions | Reference value | | | +|----------------|---------------------------|---------------------------------|------------------------------|--------------------| +| | | HS-PDSCH
$E_c / I_{or}$ (dB) | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) * | +| 1 | PA3 | -1.9 | 15 | 16000 | +| 2 | VA3 | -1.9 | 12 | 8500 | +| 3 | PA3 | -2.26 | 8 | 7000 | +| 4 | VA3 | -1.9 | 10 | 6500 | + +\* Notes: 1) For Fixed Reference Channel (FRC) H-Set 13A the reference values for R should be scaled (multiplied by 2). +2) For Fixed Reference Channel (FRC) H-Set 13C the reference values for R should be scaled (multiplied by 4). + +## 9.2.4B.2 Requirement Fixed Reference Channel (FRC) H-Set 14A/14C + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-Set 14A/14C specified in Annex A.7.1.14, with the addition of the parameters in Table 9.22J1 and the downlink physical channel setup according to Table C.12F. + +The precoding weights signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred precoding control index vector reported immediately before the start of the HS-SCCH subframe. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in Table 9.22J2 with the downlink physical channel setup in Table C.12F. + +**Table 9.22J1: Test Parameters for Testing MIMO mode with four transmit antennas, FRC H-Set 14A/14C** + +| Parameter | Unit | Test 1 | Test 2 | +|------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | | +| Redundancy and
constellation version
coding sequence | | {0,3,2,1} for 64QAM and 16-QAM | | +| Maximum number of
HARQ transmission | | 4 | | +| MIMO
N_cqi_typeA/M_cqi ratio | | 1/1 | 1/1 | +| PCI/CQI reporting Error
Rate | % | 0 | 0 | +| Number of transport
blocks | | Up to 4 | Up to 2 | +| Modulation | | First and fourth
Transport Block:
64QAM
Secondary and third
Transport Block:
16QAM | Primary Transport
Block: 64QAM
Secondary Transport
Block: 16QAM. | + +**Table 9.22J2: Minimum requirement MIMO mode with four transmit antennas, Fixed Reference Channel (FRC) H-Set 14A/14C with downlink physical channel setup in Table C.12F** + +| Test
Number | Propagation
Conditions | Reference value | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------|------------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -1.9$ dB | +| 1 | PA3 | 18 | 17500 | +| 2 | PA3 | 15 | 13500 | +| * Notes: 1) For Fixed Reference Channel (FRC) H-Set 14A the reference values for R should be scaled (multiplied by 2).
2) For Fixed Reference Channel (FRC) H-Set 14C the reference values for R should be scaled (multiplied by 4). | | | | + +## 9.2.4C MIMO Mode with Four Transmit Antennas Only With Dual-stream Restriction Performance + +The performance of MIMO mode with four transmit antennas only with dual stream capability for High Speed Physical Downlink Shared Channel (HS-DSCH) in multi-path fading environments are determined by the information bit throughput R. + +### 9.2.4C.1 Requirement Fixed Reference Channel (FRC) H-Set 9A/9C + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 9A/9C specified in Annex A.7.1.9, with the addition of the parameters in Table 9.22K1 and the downlink physical channel setup according to Table C.12F. Precoding weight set restriction shall be enabled for the tests with the downlink physical channel setup according to Table C.12F, defined in Table 9.22K2. + +The precoding control index signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred precoding control index reported immediately before the start of the HS-SCCH subframe. + +Using this configuration, if UE supports enhanced performance requirements type 3, the throughput shall meet or exceed the minimum requirements specified in Table 9.22K2 with the downlink physical channel setup in Table C.12F. The performance requirements specified in Table 9.22K2 are based on chip level equaliser with receiver diversity. + +**Table 9.22K1: Test Parameters for Testing MIMO mode with four transmit antennas only with dual stream restriction, FRC H-Set 9A/9C** + +| Parameter | Unit | Test 1/Test 2 | +|------------------------------------------------------------|--------------|--------------------------------------------------------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | +| Redundancy and
constellation version
coding sequence | | {0,3,2,1} for 16QAM and QPSK | +| Maximum number of
HARQ transmission | | 4 | +| MIMO
N_cqi_typeA/M_cqi ratio | | 1/1 | +| PCI/CQI reporting Error
Rate | % | 0 | +| Number of transport
blocks | | Up to 2 | +| Modulation | | Primary Transport Block: 16QAM
Secondary Transport Block: QPSK. | + +**Table 9.22K2: Minimum requirement MIMO mode with four transmit antennas only with dual stream restriction capability, Fixed Reference Channel (FRC) H-Set 9A/9C with downlink physical channel setup in Table C.12F** + +| Test
Number | Propagation
Conditions | Reference value | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -1.9$ dB | +| 1 | PA3 | 12 | 8000 | +| 2 | VA3 | 10 | 3000 | +| * Notes: | 1) For Fixed Reference Channel (FRC) H-Set 9A the reference values for R should be scaled (multiplied by 2).
2) For Fixed Reference Channel (FRC) H-Set 9C the reference values for R should be scaled (multiplied by 4). | | | + +## 9.2.4C.2 Requirement Fixed Reference Channel (FRC) H-Set 11A/11C + +The requirements are specified in terms of a minimum information bit throughput $R$ for the DL reference channels H-set 11A/11C specified in Annex A.7.1.11, with the addition of the parameters in Table 9.22K3 and the downlink physical channel setup according to Table C.12F. Precoding weight set restriction shall be enabled for the tests with the downlink physical channel setup according to Table C.12F, defined in Table 9.22K4. + +The precoding control index signalled on the HS-SCCH and applied on the associated HS-DSCH subframe shall correspond to the preferred precoding control index reported immediately before the start of the HS-SCCH subframe. + +Using this configuration, if UE supports enhanced performance requirements type 3, the throughput shall meet or exceed the minimum requirements specified in Table 9.22K4 with the downlink physical channel setup in Table C.12F. The performance requirements specified in Table 9.22K4 are based on chip level equaliser with receiver diversity. + +**Table 9.22K3: Test Parameters for Testing MIMO mode with four transmit antennas only with dual stream restriction capability, FRC H-Set 11A/11C** + +| Parameter | Unit | Test 1 | +|------------------------------------------------------|--------------|---------------------------------------------------------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| DPCH frame offset
( $\tau_{DPCH,n}$ ) | Chip | 0 | +| Redundancy and constellation version coding sequence | | {0,3,2,1} for 64QAM and 16QAM | +| Maximum number of HARQ transmission | | 4 | +| MIMO
N_cqi_typeA/M_cqi ratio | | 1/1 | +| PCI/CQI reporting Error Rate | % | 0 | +| Number of transport blocks | | Up to 2 | +| Modulation | | Primary Transport Block: 64QAM
Secondary Transport Block: 16QAM. | + +**Table 9.22K4: Minimum requirement MIMO mode with four transmit antennas only with dual stream restriction capability, Fixed Reference Channel (FRC) H-Set 11A/11C with downlink physical channel setup in Table C.12F** + +| Test Number | Propagation Conditions | Reference value | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------|------------------------------------------------------------| +| | | $\hat{I}_{or} / I_{oc}$ (dB) | T-put $R$ (kbps) *
HS-PDSCH
$E_c / I_{or} = -1.9$ dB | +| 1 | PA3 | 18 | 12500 | +| * Notes: 1) For Fixed Reference Channel (FRC) H-Set 11A the reference values for R should be scaled (multiplied by 2).
2) For Fixed Reference Channel (FRC) H-Set 11C the reference values for R should be scaled (multiplied by 4). | | | | + +## 9.2.5 Multiflow HSDPA performance + +The Multiflow HSDPA performance in multi-path fading environments is determined by the information bit throughput R. + +### 9.2.5.1 Requirement Fixed Reference Channel (FRC) H-Set 6 16QAM/QPSK + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-Set 6 16QAM (HS-DSCH serving cell) and QPSK (assisting HS-DSCH serving cell) specified in Annex A.7.1.6, with the addition of the parameters in Table 9.22H5 and the test set-up in Annex C.5.5. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.22H6. + +**Table 9.22H5: Test Parameters for Testing FRC H-Set 6 16QAM and QPSK** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|--------|--------|--------| +| Phase reference | | P-CPICH | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Redundancy and constellation version coding sequence | | {6,2,1,5} for H-Set 6 16QAM
{0,2,5,6} for H-Set 6 QPSK | | | | +| Maximum number of HARQ transmission | | 4 | | | | +| Note: | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. | | | | | + +**Table 9.22H6: Minimum requirement QPSK, FRC H-Set 6 16QAM and QPSK** + +| Test Number | Number of additional interfering cell | Propagation Conditions | HS-PDSCH $E_c/I_{or}$ (dB) | Reference value | | +|-------------|---------------------------------------|------------------------|----------------------------|---------------------------------------|------------------------------------------------| +| | | | | Serving HS-DSCH cell (H-Set 6, 16QAM) | Assisting serving HS-DSCH cell (H-Set 6, QPSK) | +| | | | | T-put $R$ (kbps) | T-put $R$ (kbps) | +| | | | | $\hat{I}_{or,1}/I_{oc,1}' = 1.83$ dB | $\hat{I}_{or,2}/I_{oc,2}' = -4.19$ dB | +| 1 | 0 | PA3 | -3 | 1971 | 1408 | +| 2 | 0 | PB3 | -3 | 1706 | 1155 | +| | | | | $\hat{I}_{or,1}/I_{oc,1}' = 0$ dB | $\hat{I}_{or,2}/I_{oc,2}' = -4.42$ dB | +| 3 | 1 | PA3 | -3 | 1324 | 1012 | +| 4 | 1 | PB3 | -3 | 1059 | 769 | + +Notes: 1) When the number of configured cells is 3 in Multiflow mode, the serving HS-DSCH cell requirement is applicable to the secondary serving HS-DSCH cell. +2) When the number of configured cells is 4 in Multiflow mode on 2 frequencies, the serving HS-DSCH cell requirement is applicable to the secondary serving HS-DSCH cell and the assisting serving HS-DSCH cell requirement is applicable to the assisting secondary serving HS-DSCH cell. +3) $I_{oc,1}'$ and $I_{oc,2}'$ are defined in Annex C.5.5.1 +4) When the number of configured cells is 4 in Multiflow mode on 3 frequencies, the serving HS-DSCH cell requirement is applicable to the 1st secondary serving HS-DSCH cell and the 2nd secondary serving HS-DSCH cell. + +### 9.3 Reporting of Channel Quality Indicator + +The propagation conditions for this subclause are defined in table B.1C for non-MIMO operation under fading conditions, in subclause B.2.6.1 for MIMO operation under single stream conditions, and in subclause B.2.6.2 for MIMO operation under dual stream conditions. + +For the cases in this subclause where CQI reporting is evaluated under fading conditions or under MIMO single/dual stream conditions it is expected that the UE will not always detect the HS-SCCH, resulting in a DTX for the uplink ACK/NACK transmission. The downlink configuration for evaluating CQI performance does not use retransmission. Therefore any BLER calculations must exclude any packets where the UE may have attempted to combine data from more than one transmission due to having missed one or more new data indicators or initial transmissions in MIMO operation from lost HS-SCCH transmissions. + +For the requirements for UEs supporting HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36, when the carriers are located in the same frequency band or the carriers belong to the same cell group in Multiflow mode, the spacing of the carrier frequencies of the two cells shall be 5 MHz. + +For Multiflow HSDPA requirements in subclause 9.2.5, the serving HS-DSCH cell and the assisting serving HS-DSCH cell shall have the same carrier frequency, and the secondary serving HS-DSCH cell and the assisting secondary serving HS-DSCH cell shall have the same carrier frequency. + +## 9.3.1 Single Link Performance + +### 9.3.1.1 AWGN propagation conditions + +The reporting accuracy of channel quality indicator (CQI) under AWGN environments is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. + +#### 9.3.1.1.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.23, and using the downlink physical channels specified in table C.8, the reported CQI value shall be in the range of +/-2 of the reported median more than 90% of the time. If the HS-PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI +2) shall be greater than 0.1. If the HS-PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI -1) shall be less than or equal to 0.1. + +**Table 9.23: Test Parameter for CQI test in AWGN – single link** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--| +| $\hat{I}_{or} / I_{oc}$ | | dB | 0 | 5 | | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | | +| Phase reference | | - | P-CPICH | | | +| HS-PDSCH $E_c / I_{or}$ | | dB | -3 | | | +| HS-SCCH_1 $E_c / I_{or}$ | | dB | -10 | | | +| DPCH $E_c / I_{or}$ | | dB | -10 | | | +| Maximum number of H-ARQ transmission | | - | 1 | | | +| Number of HS-SCCH set to be monitored | | - | 1 | | | +| CQI feedback cycle | | ms | 2 | | | +| CQI repetition factor | | - | 1 | | | +| HS-SCCH-1 signalling pattern | | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | UEs from capability categories 13-20 shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +### 9.3.1.1.2 Minimum Requirement – UE HS-DSCH categories 13,14,17,18, 19 and 20 + +For the parameters specified in Table 9.24, and using the downlink physical channels specified in table C.8, the reported CQI value shall be in the range of +/-2 of the reported median more than 90% of the time. If the HS-PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 2) shall be greater than 0.1. If the HS-PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI -1) shall be less than or equal to 0.1. + +**Table 9.24: Test Parameter for CQI test in AWGN – single link** + +| Parameter | Unit | Test 1 | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\hat{I}_{or} / I_{oc}$ | dB | 15 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Phase reference | - | P-CPICH | +| HS-PDSCH $E_c / I_{or}$ | dB | -2 | +| HS-SCCH_1 $E_c / I_{or}$ | dB | -12 | +| DPCH $E_c / I_{or}$ | dB | -12 | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | ms | 2 | +| CQI repetition factor | - | 1 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | +| Note 5: | The UE shall be configured in 64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | + +### 9.3.1.1.3 Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36 + +For the parameters specified in Table 9.25, and using the downlink physical channels specified in table C.8, with a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, for each of the serving cells, the reported CQI value for the cell shall be in the range of $\pm 2$ of the cell-specific reported median more than 90% of the time. If the HS-PDSCH BLER, for any of the cells, using the transport format indicated by cell-specific median CQI is less than or equal to 0.1, the BLER for this cell using the transport format indicated by the (cell-specific median CQI +2) shall be greater than 0.1. If the HS-PDSCH BLER, for any of the cells, using the transport format indicated by the cell-specific median CQI is greater than 0.1, the BLER using transport format indicated by (cell-specific median CQI -1) shall be less than or equal to 0.1. + +**Table 9.25: Test Parameter for CQI test in AWGN – single link** + +| Parameter | Unit | Test 1 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\hat{I}_{or1} / I_{oc}$ | dB | | 0 | +| $\hat{I}_{or2} / I_{oc}$ | dB | | 10 | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Phase reference | - | | P-CPICH | +| HS-PDSCH $E_c / I_{or}$ | dB | | -3 | +| HS-SCCH_1 $E_c / I_{or}$ | dB | | -10 | +| DPCH $E_c / I_{or}$ | dB | | -10 | +| Maximum number of H-ARQ transmission | - | | 1 | +| Number of HS-SCCH set to be monitored | - | | 1 | +| CQI feedback cycle | ms | | 2 | +| CQI repetition factor | - | | 1 | +| HS-SCCH-1 signalling pattern | - | | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | +| Note 5: | The UE shall be configured in non 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +### 9.3.1.2 Fading propagation conditions + +The reporting accuracy of the channel quality indicator (CQI) under fading environments is determined by the BLER performance using the transport format indicated by the reported CQI median. + +The specified requirements may be subject to further simulations to verify assumptions. + +#### 9.3.1.2.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.26, and using the downlink physical channels specified in table C.8, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.27. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +**Table 9.26: Test Parameters for CQI test in fading – single link** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -8 | -4 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 0 | 5 | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH | | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -8.5 | | | | +| DPCH $E_c/I_{or}$ | dB | -6 | | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | Case 8 | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7] . | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.27: Minimum requirement for CQI test in fading – single link** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|-------| +| | Test 1 | Test2 | +| CQI median | 60% | 60% | +| CQI median + 3 | 15% | 15% | + +### 9.3.1.2.2 Minimum Requirement – UE HS-DSCH categories 13, 14, 17, 18, 19 and 20 + +For the parameters specified in Table 9.27A, and using the downlink physical channels specified in table C.8, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.27B. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +**Table 9.27A: Test Parameters for CQI test in fading – single link** + +| Parameter | Unit | Test 1 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-PDSCH $E_c/I_{or}$ | dB | | -2 | +| $\hat{I}_{or}/I_{oc}$ | dB | | 15 | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Phase reference | - | | P-CPICH | +| HS-SCCH_1 $E_c/I_{or}$ | dB | | -12 | +| DPCH $E_c/I_{or}$ | dB | | -12 | +| Maximum number of H-ARQ transmission | - | | 1 | +| Number of HS-SCCH set to be monitored | - | | 1 | +| CQI feedback cycle | ms | | 2 | +| CQI repetition factor | - | | 1 | +| HS-SCCH-1 signalling pattern | - | | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Propagation Channel | | | Case 8 | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7] . | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | +| Note 5: | The UE shall be configured in 64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +**Table 9.27B: Minimum requirement for CQI test in fading - single link** + +| Reported CQI | Maximum BLER | +|----------------|--------------| +| | Test 1 | +| CQI median | 60% | +| CQI median + 3 | 15% | + +### 9.3.1.2.3 Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36 + +For the parameters specified in Table 9.26, and using the downlink physical channels specified in table C.8, with a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, for each of the serving cells, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each serving cell when transmitting with a cell-specific fixed transport format given by the cell-specific CQI median as shown in Table 9.27. The BLER at a particular reported CQI for a specific serving cell is obtained by associating a particular CQI reference + +measurement period with the HS-PDSCH subframe transmitted from this serving cell overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +### 9.3.1.3 Periodically varying radio conditions. + +The reporting accuracy of the channel quality indicator (CQI) when subject to AWGN propagation conditions with periodically varying $\hat{I}_{or}/I_{oc}$ , is determined by the reporting variance as measured during selected parts of a predetermined $\hat{I}_{or}/I_{oc}$ pattern, as depicted in Figure 9.1. + +![Figure 9.1: Test scenario for CQI reporting test under varying interference conditions. The graph shows a square wave pattern of interference power (I_or/I_oc) over time. The y-axis is labeled I_or/I_oc and has two levels, alpha_1 and alpha_2. The x-axis is labeled Time. The square wave transitions between alpha_1 and alpha_2. A pulse is shown with duration T_pulse. The time from the start of the pulse to the start of the measurement period is T_settle. The time from the start of the measurement period to the start of the measurement is T_delay. The duration of the measurement period is T_measure.](20b95bcf515b4d9028e98a1d0d68302a_img.jpg) + +Figure 9.1: Test scenario for CQI reporting test under varying interference conditions. The graph shows a square wave pattern of interference power (I\_or/I\_oc) over time. The y-axis is labeled I\_or/I\_oc and has two levels, alpha\_1 and alpha\_2. The x-axis is labeled Time. The square wave transitions between alpha\_1 and alpha\_2. A pulse is shown with duration T\_pulse. The time from the start of the pulse to the start of the measurement period is T\_settle. The time from the start of the measurement period to the start of the measurement is T\_delay. The duration of the measurement period is T\_measure. + +**Figure 9.1 Test scenario for CQI reporting test under varying interference conditions. $\hat{I}_{or}/I_{oc}$ is varied between $\alpha_1$ and $\alpha_2$ according to a predetermined square wave pattern.** + +#### 9.3.1.3.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.27C, and using the downlink physical channels specified in table C.8, let $M_1$ be defined as the median CQI that the UE reports in static propagation conditions, with $I_{or}/I_{oc}$ set to $\alpha_1$ , and $M_2$ be the median CQI that the UE reports in static propagation conditions, with $\hat{I}_{or}/I_{oc}$ set to $\alpha_2$ . The minimum difference between $M_1$ and $M_2$ is required to be larger than 6. + +For the parameters specified in Table 9.27C, and using the downlink physical channels specified in table C.8, 90% of the reported CQI values, during $T_{measure}$ as depicted in Figure 9.1, shall be in the range of $\pm 3$ of $M_1$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_1$ , and in the range of $\pm 3$ of $M_2$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_2$ . + +The measurement equipment is allowed to start the ramping of $\hat{I}_{or}/I_{oc}$ 13 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +The measurement equipment shall have settled $\hat{I}_{or}/I_{oc}$ to its nominal value 10 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +An illustration of these timing relations is provided in Figure 9.2. + +Table 9.27C: Test Parameter for CQI test in periodically varying radio conditions – single link + +| Parameter | Unit | Test 1 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha^1$ | dB | | 10 | +| $\alpha_2$ | dB | | 0 | +| $I_{oc1}$ | dBm/3.84 MHz | | -60 | +| $I_{oc2}$ | dBm/3.84 MHz | | -50 | +| Phase reference | - | | P-CPICH | +| $T_{measure}$ | TTI | | 8 | +| $T_{delay}$ | TTI | | 3 | +| $T_{settle}$ | TTI | | 1 | +| $T_{pulse}$ | TTI | | 12 | +| HS-PDSCH $E_c/I_{or}$ | dB | | -2 | +| HS-SCCH_1 $E_c/I_{or}$ | dB | | -10 | +| DPCH $E_c/I_{or}$ | dB | | -10 | +| Maximum number of H-ARQ transmission | - | | 1 | +| Number of HS-SCCH set to be monitored | - | | 1 | +| CQI feedback cycle | ms | | 2 | +| CQI repetition factor | - | | 1 | +| HS-SCCH-1 signalling pattern | - | | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +![Timing diagram showing a sequence of subframes. A dashed line at the top indicates the timeline. Below it, a series of boxes represent subframes, with some shaded grey. A double-headed arrow points to a specific subframe, indicating the start of the measurement period.](df6ce1a71cc187bb1044b2c81fdea7c0_img.jpg) + +The diagram illustrates the timing relation between HS-DPCCH, DPCCH/DPDCH, and $\hat{I}_{or}/I_{oc}$ ramping. It shows a sequence of subframes. A dashed line at the top indicates the timeline. Below it, a series of boxes represent subframes, with some shaded grey. A double-headed arrow points to a specific subframe, indicating the start of the measurement period. + +Timing diagram showing a sequence of subframes. A dashed line at the top indicates the timeline. Below it, a series of boxes represent subframes, with some shaded grey. A double-headed arrow points to a specific subframe, indicating the start of the measurement period. + +Figure 9.2 Timing relation between HS-DPCCH, DPCCH/DPDCH and $\hat{I}_{or}/I_{oc}$ ramping. The measurement equipment starts ramping the $\hat{I}_{or}/I_{oc}$ at point 1. The $\hat{I}_{or}/I_{oc}$ should be settled to its nominal value at point 2. The first CQI report that is counted in the statistics of the requirement is transmitted in the uplink at point 3. + +## 9.3.2 Open Loop Diversity Performance + +### 9.3.2.1 AWGN propagation conditions + +The reporting accuracy of channel quality indicator (CQI) under AWGN environments is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. + +#### 9.3.2.1.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.32, and using the downlink physical channels specified in table C.9, the reported CQI value shall be in the range of +/-2 of the reported median more than 90% of the time. If the HS-PDSCH (BLER) using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI +2) shall be greater than 0.1. If the HS-PDSCH (BLER) using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI -1) shall be less than or equal to 0.1. + +**Table 9.32: Test Parameter for CQI test in AWGN – open loop diversity** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|--| +| $\hat{I}_{or} / I_{oc}$ | | dB | 0 | 5 | | | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | | | +| Phase reference | | - | P-CPICH | | | | +| HS-PDSCH $E_c / I_{or}$ | | dB | -3 | | | | +| HS-SCCH_1 $E_c / I_{or}$ | | dB | -10 | | | | +| DPCH $E_c / I_{or}$ | | dB | -10 | | | | +| Maximum number of H-ARQ transmission | | - | 1 | | | | +| Number of HS-SCCH set to be monitored | | - | 1 | | | | +| CQI feedback cycle | | ms | 2 | | | | +| CQI repetition factor | | - | 1 | | | | +| HS-SCCH-1 signalling pattern | | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | | +| Note 5: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | | + +### 9.3.2.1.2 Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36 + +For the parameters specified in Table 9.33, and using the downlink physical channels specified in table C.9, with a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, for each of the serving cells, the reported CQI value for the cell shall be in the range of +/-2 of the cell-specific reported median more than 90% of the time. If the HS-PDSCH BLER, for any of the cells, using the transport format indicated by cell-specific median CQI is less than or equal to 0.1, the BLER for this cell using the transport format indicated by the (cell-specific median CQI +2) shall be greater than 0.1. If the HS-PDSCH BLER, for any of the cells, using the transport format indicated by the cell-specific median CQI is greater than 0.1, the BLER using transport format indicated by (cell-specific median CQI -1) shall be less than or equal to 0.1. + +**Table 9.33: Test Parameter for CQI test in AWGN – open loop diversity** + +| Parameter | Unit | Test 1 | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\hat{I}_{or1} / I_{oc}$ | dB | 0 | +| $\hat{I}_{or2} / I_{oc}$ | dB | 10 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Phase reference | - | P-CPICH | +| HS-PDSCH $E_c / I_{or}$ | dB | -3 | +| HS-SCCH_1 $E_c / I_{or}$ | dB | -10 | +| DPCH $E_c / I_{or}$ | dB | -10 | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | ms | 2 | +| CQI repetition factor | - | 1 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | +| Note 5: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | + +### 9.3.2.2 Fading propagation conditions + +The reporting accuracy of the channel quality indicator (CQI) under fading environments is determined by the BLER performance using the transport format indicated by the reported CQI median. + +The specified requirements may be subject to further simulations to verify assumptions. + +#### 9.3.2.2.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.35, and using the downlink physical channels specified in table C.9, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.36. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +**Table 9.35: Test Parameters for CQI test in fading – open loop diversity** + +| Parameter | Unit | Test 1 | | Test 2 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|--------|--| +| | | HS-PDSCH $E_c/I_{or}$ | dB | -8 | | +| $\hat{I}_{or}/I_{oc}$ | dB | 0 | | 5 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH | | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -8.5 | | | | +| DPCH $E_c/I_{or}$ | dB | -6 | | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | - | Case 8 | | | | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | | | +| Note 3: | HS-PDSCH Ec/Ior is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.36: Minimum requirement for CQI test in fading – open loop diversity** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|-------| +| | Test 1 | Test2 | +| CQI median | 60% | 60% | +| CQI median + 3 | 15% | 15% | + +### 9.3.2.2.2 Additional Requirements – UE HS-DSCH categories 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 35 and 36 + +For the parameters specified in Table 9.35 and using the downlink physical channels specified in table C.9, with a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, for each of the serving cells, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each serving cell when transmitting with a cell-specific fixed transport format given by the cell-specific CQI median as shown in Table 9.36. The BLER at a particular reported CQI for a specific serving cell is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe transmitted from this serving cell overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +### 9.3.2.3 Periodically varying radio conditions. + +The reporting accuracy of the channel quality indicator (CQI) when subject to AWGN propagation conditions with periodically varying $\hat{I}_{or}/I_{oc}$ , is determined by the reporting variance as measured during selected parts of a predetermined $\hat{I}_{or}/I_{oc}$ pattern, as depicted in Figure 9.1. + +#### 9.3.2.3.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.37, and using the downlink physical channels specified in table C.9, let $M_1$ be defined as the median CQI that the UE reports in static propagation conditions, with $I_{or}/I_{oc}$ set to $\alpha_1$ , and $M_2$ be the median CQI that the UE reports in static propagation conditions, with $\hat{I}_{or}/I_{oc}$ set to $\alpha_2$ . The minimum difference between $M_1$ and $M_2$ is required to be larger than 6. + +For the parameters specified in Table 9.37, and using the downlink physical channels specified in table C.9, 90% of the reported CQI values, during $T_{measure}$ as depicted in Figure 9.1, shall be in the range of $\pm 3$ of $M_1$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_1$ , and in the range of $\pm 3$ of $M_2$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_2$ . + +The measurement equipment is allowed to start the ramping of $\hat{I}_{or}/I_{oc}$ 13 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +The measurement equipment shall have settled $\hat{I}_{or}/I_{oc}$ to its nominal value 10 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +An illustration of these timing relations is provided in Figure 9.2. + +**Table 9.37: Test Parameter for CQI test in periodically varying radio conditions – open loop diversity** + +| Parameter | Unit | Test 1 | +|----------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha^1$ | dB | 10 | +| $\alpha_2$ | dB | 0 | +| $I_{oc1}$ | dBm/3.84 MHz | -60 | +| $I_{oc2}$ | dBm/3.84 MHz | -50 | +| Phase reference | - | P-CPICH | +| $T_{measure}$ | TTI | 8 | +| $T_{delay}$ | TTI | 3 | +| $T_{settle}$ | TTI | 1 | +| $T_{pulse}$ | TTI | 12 | +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -10 | +| DPCH $E_c/I_{or}$ | dB | -10 | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | ms | 2 | +| CQI repetition factor | - | 1 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: The UE shall be configured in non 64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +### 9.3.3 Closed Loop Diversity Performance + +#### 9.3.3.1 AWGN propagation conditions + +The reporting accuracy of channel quality indicator (CQI) under AWGN environments is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. + +##### 9.3.3.1.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.41, and using the downlink physical channels specified in table C.10, the reported CQI value shall be in the range of +/-2 of the reported median more than 90% of the time. If the HS-PDSCH (BLER) using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI +2) shall be greater than 0.1. If the HS-PDSCH (BLER) using transport format indicated by the median CQI is greater than 0.1, the BLER using the transport format indicated by (median CQI -1) shall be less than or equal to 0.1. + +**Table 9.41: Test Parameters for CQI in AWGN – closed loop diversity** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--| +| $\hat{I}_{or} / I_{oc}$ | | dB | 0 | 5 | | +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | | +| Phase reference | | - | P-CPICH | | | +| HS-PDSCH $E_c / I_{or}$ | | dB | -3 | | | +| HS-SCCH_1 $E_c / I_{or}$ | | dB | -10 | | | +| DPCH $E_c / I_{or}$ | | dB | -10 | | | +| Maximum number of H-ARQ transmission | | - | 1 | | | +| Number of HS-SCCH set to be monitored | | - | 1 | | | +| CQI feedback cycle | | ms | 2 | | | +| CQI repetition factor | | - | 1 | | | +| Feedback Error Rate | | % | 0 | | | +| Closed loop timing adjustment mode | | | 1 | | | +| HS-SCCH-1 signalling pattern | | - | To incorporate inter-TTI=3 the six subframe HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI, median CQI -1, median CQI+2 are used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non.64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +### 9.3.3.2 Fading propagation conditions + +The reporting accuracy of the channel quality indicator (CQI) under fading environments is determined by the BLER performance using the transport format indicated by the reported CQI median. + +The specified requirements may be subject to further simulations to verify assumptions. + +#### 9.3.3.2.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.44, and using the downlink physical channels specified in table C.10, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.45. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +**Table 9.44: Test Parameters for CQI test in fading- closed loop diversity** + +| Parameter | Unit | Test 1 | Test 2 | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| HS-PDSCH $E_c/I_{or}$ | dB | -8 | -4 | +| $\hat{I}_{or}/I_{oc}$ | dB | 0 | 5 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Phase reference | - | P-CPICH | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -8.5 | | +| DPCH $E_c/I_{or}$ | dB | -6 | | +| Maximum number of H-ARQ transmission | - | 1 | | +| Number of HS-SCCH set to be monitored | - | 1 | | +| CQI feedback cycle | ms | 2 | | +| CQI repetition factor | - | 1 | | +| Feedback Error Rate | % | 0 | | +| Closed loop timing adjustment mode | - | 1 | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | +| Propagation Channel | | Case 8 | | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | +| Note 5: | The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +**Table 9.45: Minimum requirement for CQI test in fading – closed loop diversity** + +| Reported CQI | | Maximum BLER | | +|----------------|--|--------------|--------| +| | | Test 1 | Test 2 | +| CQI median | | 60% | 60% | +| CQI median + 3 | | 15% | 15% | + +### 9.3.3.3 Periodically varying radio conditions. + +The reporting accuracy of the channel quality indicator (CQI) when subject to AWGN propagation conditions with periodically varying $\hat{I}_{or}/I_{oc}$ , is determined by the reporting variance as measured during selected parts of a predetermined $\hat{I}_{or}/I_{oc}$ pattern, as depicted in Figure 9.1. + +#### 9.3.3.3.1 Minimum Requirement – UE HS-DSCH categories 1-20 + +For the parameters specified in Table 9.45A, and using the downlink physical channels specified in table C.10, let $M_1$ be defined as the median CQI that the UE reports in static propagation conditions, with $I_{or}/I_{oc}$ set to $\alpha_1$ , and $M_2$ be the median CQI that the UE reports in static propagation conditions, with $\hat{I}_{or}/I_{oc}$ set to $\alpha_2$ . The minimum difference between $M_1$ and $M_2$ is required to be larger than 6. + +For the parameters specified in Table 9.45A, and using the downlink physical channels specified in table C.10, 90% of the reported CQI values, during $T_{measure}$ as depicted in Figure 9.1, shall be in the range of $\pm 3$ of $M_1$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_1$ , and in the range of $\pm 3$ of $M_2$ , for the cases when $T_{measure}$ occurs during time-periods where $\hat{I}_{or}/I_{oc}$ is set to $\alpha_2$ . + +The measurement equipment is allowed to start the ramping of $\hat{I}_{or}/I_{oc}$ 13 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +The measurement equipment shall have settled $\hat{I}_{or}/I_{oc}$ to its nominal value 10 slots before the start of the HS-DPCCH slot that contains the first CQI report in $T_{measure}$ . + +An illustration of these timing relations is provided in Figure 9.2. + +**Table 9.45A: Test Parameter for CQI test in periodically varying radio conditions – closed loop diversity** + +| Parameter | Unit | Test 1 | +|----------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha^1$ | dB | 10 | +| $\alpha_2$ | dB | 0 | +| $I_{oc1}$ | dBm/3.84 MHz | -60 | +| $I^{oc2}$ | dBm/3.84 MHz | -50 | +| Phase reference | - | P-CPICH | +| $T_{measure}$ | TTI | 8 | +| $T_{delay}$ | TTI | 3 | +| $T_{settle}$ | TTI | 1 | +| $T_{pulse}$ | TTI | 12 | +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -10 | +| DPCH $E_c/I_{or}$ | dB | -10 | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | ms | 2 | +| CQI repetition factor | - | 1 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Note 1: Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: The UE shall be configured in non-64QAM/non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +### 9.3.4 MIMO Performance + +#### 9.3.4.1 MIMO Single Stream Fading Conditions + +The minimum performance requirements of channel quality indicator (CQI) reporting under MIMO single stream conditions are defined based on a CQI Type A versus Type B reporting ratio of 1 / 2, i.e. the parameters $N_{cqi\_typeA}$ and $M_{cqi}$ (see [8]) are assumed to be set to 1 and 2, respectively. The propagation conditions assumed for minimum performance requirements of CQI reporting under MIMO single stream conditions are defined in subclause B.2.6.1. The precoding used at the transmitter is one randomly picked but fixed precoding vector for single transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described for MIMO single stream conditions in subclause B.2.6.1. + +The reporting accuracy of CQI under MIMO single stream conditions is determined by the BLER performance when transmitting with a transport format indicated by the reported CQI median determined over all single transport block + +Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1. + +#### 9.3.4.1.1 Minimum Requirement - UE HS-DSCH categories 15-20 + +For the parameters specified in Table 9.46, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.47. The CQI median shall be determined over all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes to which the same CQI value was associated. + +**Table 9.46: Test Parameters for CQI test in MIMO single stream fading conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 dB | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 6 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| PCI/CQI reporting Error Rate | % | 0 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO single stream fading conditions | | | | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI over all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding vector for single transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described for MIMO single stream conditions in subclause B.2.6.1. | | | | | +| Note 3: | HS-PDSCH Ec/Ior is decreased according to reference power adjustment Δ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non-64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.47: Minimum requirement for CQI test in MIMO single stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 3 | 15% | 15% | + +#### 9.3.4.1.2 Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.47A, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the cell-specific CQI median as shown in Table 9.47B. The requirement is applicable for each cell individually, that is + +the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and independently verified against the requirement in Table 9.47B. The cell-specific CQI median shall be determined over all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1. The cell-specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the cell-specific precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes to which the same CQI value was associated. + +**Table 9.47A: Test Parameters for CQI test in MIMO single stream fading conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or1}/I_{oc}$ | dB | | 6 | | | +| $\hat{I}_{or2}/I_{oc}$ | dB | | 6 | | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | | 1 | | | +| Number of HS-SCCH set to be monitored | - | | 1 | | | +| CQI feedback cycle | ms | | 2 | | | +| CQI repetition factor | - | | 1 | | | +| PCI/CQI reporting Error Rate | % | | 0 | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO single stream fading conditions | | | | +| Note 1: | Measurement power offset "I" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI over all single transport block Type A CQI reports and all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding vector for single transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described for MIMO single stream conditions in subclause B.2.6.1. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non-64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.47B: Minimum requirement for CQI test in MIMO single stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 3 | 15% | 15% | + +### 9.3.4.2 MIMO Dual Stream Fading Conditions + +The minimum performance requirements of channel quality indicator (CQI) reporting under MIMO dual stream conditions are defined based on a Type A reporting fraction of 100%, i.e. the parameters $N\_cqi\_typeA$ and $M\_cqi$ (see [8]) are assumed to be both set to 1. The propagation conditions assumed for minimum performance requirements of CQI reporting under MIMO dual stream conditions are defined in subclause B.2.6.2. The precoding used at the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.6.2. + +The reporting accuracy of CQI under MIMO dual stream conditions is determined by the BLER performance of two streams of transport blocks using the transport formats indicated by the respective stream specific reported CQI median over all dual transport block CQI reports for each stream that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. + +#### 9.3.4.2.1 Minimum Requirement – UE HS-DSCH categories 15-20 + +For the parameters specified in Table 9.48, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each stream when transmitting a fixed transport format per stream given by the stream specific CQI median as shown in Table 9.49. The stream specific CQI median shall be determined over all dual transport block CQI reports that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the first column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used respectively to determine the median CQI values for stream #1 and stream #2 as depicted in Figure B.5 in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the second column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used to determine the median CQI values for stream #2 and stream #1, respectively. The stream specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all dual transport block CQI reports that were reported together with a PCI report that was matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2 with the two transport blocks of the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fractions of erroneous HS-PDSCH subframes to which the same CQI values were associated. + +**Table 9.48: Test Parameters for CQI test in MIMO dual stream fading conditions** + +| Parameter | Unit | Test 1 | Test 2 | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | +| $\hat{I}_{or}/I_{oc}$ | dB | 10 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | +| Precoding weight set restriction | - | Disabled | Enabled | +| Maximum number of H-ARQ transmission | - | 1 | | +| Number of HS-SCCH set to be monitored | - | 1 | | +| CQI feedback cycle | ms | 2 | | +| CQI repetition factor | - | 1 | | +| PCI/CQI reporting Error Rate | % | 0 | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | +| Propagation Channel | - | MIMO dual stream fading conditions | | +| Note 1: | Measurement power offset "I" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: | TF for HS-PDSCH is configured for each stream according to the reported CQI statistics. TF for each stream is based on median CQI over all dual transport block CQI reports that are reported together with a PCI report that is matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.6.2. | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | +| Note 5: | The UE shall be configured in non-64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +**Table 9.49: Minimum requirement for CQI test in MIMO dual stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 2 | 15% | 15% | + +### 9.3.4.2.2 Minimum Requirement – UE HS-DSCH categories 19-20 + +For the parameters specified in Table 9.49A, and using the downlink physical channels specified in table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each stream when transmitting a fixed transport format per stream given by the stream specific CQI median as shown in Table 9.49B. The stream specific CQI median shall be determined over all dual transport block CQI reports that were reported together + +with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the first column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used respectively to determine the median CQI values for stream #1 and stream #2 as depicted in Figure B.5 in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the second column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used to determine the median CQI values for stream #2 and stream #1, respectively. The stream specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all dual transport block CQI reports that were reported together with a PCI report that was matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2 with the two transport blocks of the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fractions of erroneous HS-PDSCH subframes to which the same CQI values were associated. + +**Table 9.49A: Test Parameters for CQI test in MIMO dual stream conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | 15 | | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | | 1 | | | +| Number of HS-SCCH set to be monitored | - | | 1 | | | +| CQI feedback cycle | ms | | 2 | | | +| CQI repetition factor | - | | 1 | | | +| PCI/CQI reporting Error Rate | % | | 0 | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO dual stream conditions | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured for each stream according to the reported CQI statistics. TF for each stream is based on median CQI over all dual transport block CQI reports that are reported together with a PCI report that is matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.6.2. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.49B: Minimum requirement for CQI test in MIMO dual stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 2 | 15% | 15% | + +### 9.3.4.2.3 Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49BA, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each stream when transmitting a fixed transport format per stream given by the stream specific CQI median as shown in Table 9.49BB. The requirement is applicable for each cell and stream individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and stream, and independently verified against the requirement in Table 9.49BB. The stream and cell-specific CQI median shall be determined over all dual transport block CQI reports that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the first column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used respectively to determine the median CQI values for stream #1 and stream #2 as depicted in Figure B.5 in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the second column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used to determine the median CQI values for stream #2 and stream #1, respectively. The stream and cell-specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all dual transport block CQI reports that were reported together with a PCI report that was matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2 with the two transport blocks of the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fractions of erroneous HS-PDSCH subframes to which the same CQI values were associated. + +**Table 9.49BA: Test Parameters for CQI test in MIMO dual stream conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or1}/I_{oc}$ | dB | | 10 | | | +| $\hat{I}_{or2}/I_{oc}$ | dB | | 10 | | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | | 1 | | | +| Number of HS-SCCH set to be monitored | - | | 1 | | | +| CQI feedback cycle | ms | | 2 | | | +| CQI repetition factor | - | | 1 | | | +| PCI/CQI reporting Error Rate | % | | 0 | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO dual stream conditions | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured for each stream according to the reported CQI statistics. TF for each stream is based on median CQI over all dual transport block CQI reports that are reported together with a PCI report that is matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.6.2. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 5: | The UE shall be configured in non-64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +**Table 9.49BB: Minimum requirement for CQI test in MIMO dual stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 2 | 15% | 15% | + +#### 9.3.4.2.4 Additional Requirement – UE HS-DSCH categories 27, 28, 30, 32 and 36 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49BC, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are + +specified in terms of maximum BLERs at particular reported CQIs for each stream when transmitting a fixed transport format per stream given by the stream specific CQI median as shown in Table 9.49BD. The requirement is applicable for each cell and stream individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and stream, and independently verified against the requirement in Table 9.49BB. The stream and cell-specific CQI median shall be determined over all dual transport block CQI reports that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the first column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used respectively to determine the median CQI values for stream #1 and stream #2 as depicted in Figure B.5 in subclause B.2.6.2. When the reported preferred primary precoding vector is matching with the second column of the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2, the reported values $CQI_1$ and $CQI_2$ shall be used to determine the median CQI values for stream #2 and stream #1, respectively. The stream and cell-specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all dual transport block CQI reports that were reported together with a PCI report that was matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2 with the two transport blocks of the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fractions of erroneous HS-PDSCH subframes to which the same CQI values were associated. + +**Table 9.49BC: Test Parameters for CQI test in MIMO dual stream conditions** + +| Parameter | Unit | Test 1 | Test 2 | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | +| $\hat{I}_{or1}/I_{oc}$ | dB | 15 | | +| $\hat{I}_{or2}/I_{oc}$ | dB | 15 | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | +| Precoding weight set restriction | - | Disabled | Enabled | +| Maximum number of H-ARQ transmission | - | 1 | | +| Number of HS-SCCH set to be monitored | - | 1 | | +| CQI feedback cycle | ms | 2 | | +| CQI repetition factor | - | 1 | | +| PCI/CQI reporting Error Rate | % | 0 | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | +| Propagation Channel | - | MIMO dual stream conditions | | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7]. | | | +| Note 2: | TF for HS-PDSCH is configured for each stream according to the reported CQI statistics. TF for each stream is based on median CQI over all dual transport block CQI reports that are reported together with a PCI report that is matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.6.2. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.6.2. | | | +| Note 3: | HS-PDSCH Ec/Ior is decreased according to reference power adjustment Δ described in TS 25.214 | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | +| Note 5: | The UE shall be configured in 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | + +**Table 9.49BD: Minimum requirement for CQI test in MIMO dual stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 2 | 15% | 15% | + +### 9.3.4.3 MIMO Dual Stream Static Orthogonal Conditions + +The minimum performance requirements of channel quality indicator (CQI) reporting under MIMO dual stream conditions are defined based on a Type A reporting fraction of 100%, i.e. the parameters $N\_cqi\_typeA$ and $M\_cqi$ (see + +[8]) are assumed to be both set to 1. The propagation conditions assumed for minimum performance requirements of CQI reporting under MIMO dual stream static orthogonal conditions are defined in subclause B.2.6.3. + +The precoding matrix used in the transmitter shall be one randomly picked but fixed precoding matrix $\mathbf{W}$ out of the set defined in equation EQ.B.2.6.2. + +#### 9.3.4.3.1 Minimum Requirement –UE HS-DSCH categories 15-20 + +For the parameters specified in Table 9.49C, and using the downlink physical channels specified in Table C.9 and Table C.12D, the reported CQI value, for each of the streams, shall be in the range of $\pm 2$ of the reported stream specific CQI median more than 90% of the time. The stream specific CQI median shall be determined over all dual transport block CQI reports. + +For each of the streams, if the HS-PDSCH BLER using the transport format indicated by the stream specific CQI median is less than or equal to 0.1, the BLER using the transport format indicated by the (stream specific CQI median + 2) shall be greater than 0.1. For each of the streams, if the HS-PDSCH BLER using the transport format indicated by the stream specific CQI median is greater than 0.1, the BLER using transport format indicated by (stream specific CQI median -1) shall be less than or equal to 0.1. The requirements are applicable to Test 1 and Test 2. + +**Table 9.49C: Test Parameters for CQI test in MIMO dual stream static orthogonal conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | 10 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| PCI/CQI reporting Error Rate | % | 0 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be “...XOOXOO...”, where “X” indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and “O” indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO dual stream static orthogonal conditions | | | | +| Note 1: | Measurement power offset “T” is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214 | | | | | +| Note 3: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 4: | The UE shall be configured in non-64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +### 9.3.4.3.2 Minimum Requirement –UE HS-DSCH categories 19-20 + +For the parameters specified in Table 9.49D, and using the downlink physical channels specified in Table C.9 and Table C.12D, the reported CQI value, for each of the streams, shall be in the range of $\pm 2$ of the reported stream specific CQI median more than 90% of the time. The stream specific CQI median shall be determined over all dual transport block CQI reports. + +For each of the streams, if the HS-PDSCH BLER using the transport format indicated by the stream specific CQI median is less than or equal to 0.1, the BLER using the transport format indicated by the (stream specific CQI median + 2) shall be greater than 0.1. For each of the streams, if the HS-PDSCH BLER using the transport format indicated by the stream specific CQI median is greater than 0.1, the BLER using transport format indicated by (stream specific CQI median - 1) shall be less than or equal to 0.1. The requirements are applicable to Test 1 and Test 2. + +**Table 9.49D: Test Parameters for CQI test in MIMO dual stream static orthogonal conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | 15 | | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | | 1 | | | +| Number of HS-SCCH set to be monitored | - | | 1 | | | +| CQI feedback cycle | ms | | 2 | | | +| CQI repetition factor | - | | 1 | | | +| PCI/CQI reporting Error Rate | % | | 0 | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO dual stream static orthogonal conditions | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214 | | | | | +| Note 3: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 4: | The UE shall be configured in 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +### 9.3.4.3.3 Additional Requirement – UE HS-DSCH categories 25-28, 30, 32 and 36 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49E, and using the downlink physical channels specified in Table C.9 and Table C.12D, the reported CQI value, for each of the streams, and cells shall be in the range of $\pm 2$ of the reported stream specific CQI median more than 90% of the time. The requirement is applicable for each cell and stream individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and stream, and independently verified to fulfil the requirement. The stream and cell-specific CQI median shall be determined over all dual transport block CQI reports. + +For each of the streams and cells, if the HS-PDSCH BLER using the transport format indicated by the stream and cell-specific CQI median is less than or equal to 0.1, the BLER using the transport format indicated by the (stream and cell-specific CQI median + 2) shall be greater than 0.1. For each of the streams and cells, if the HS-PDSCH BLER using the transport format indicated by the stream and cell-specific CQI median is greater than 0.1, the BLER using transport format indicated by (stream and cell-specific CQI median -1) shall be less than or equal to 0.1. The requirements are applicable to Test 1 and Test 2. + +**Table 9.49E: Test Parameters for CQI test in MIMO dual stream static orthogonal conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or1}/I_{oc}$ | dB | 10 | | | | +| $\hat{I}_{or2}/I_{oc}$ | dB | 10 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| PCI/CQI reporting Error Rate | % | 0 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | - | MIMO dual stream static orthogonal conditions | | | | +| Note 1: | Measurement power offset "Γ" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | Note 3: HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 3: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 4: | UEs from HS-DSCH categories 27-28 shall be configured in non-64QAM/MIMO and use appropriate CQI tables according to TS 25.214. | | | | | + +#### 9.3.4.3.4 Additional Requirement – UE HS-DSCH categories 27, 28, 30, 32 and 36 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49F, and using the downlink physical channels specified in Table C.9 and Table C.12D, the reported CQI value, for each of the streams, and cells shall be in the range of +/-2 of the reported stream specific CQI median more than 90% of the time. The requirement is applicable for each cell and stream individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and stream, and independently verified to fulfil the requirement. The stream and cell-specific CQI median shall be determined over all dual transport block CQI reports. + +For each of the streams and cells, if the HS-PDSCH BLER using the transport format indicated by the stream and cell-specific CQI median is less than or equal to 0.1, the BLER using the transport format indicated by the (stream and cell-specific CQI median + 2) shall be greater than 0.1. + +specific CQI median + 2) shall be greater than 0.1. For each of the streams and cells, if the HS-PDSCH BLER using the transport format indicated by the stream and cell-specific CQI median is greater than 0.1, the BLER using transport format indicated by (stream and cell-specific CQI median -1) shall be less than or equal to 0.1. The requirements are applicable to Test 1 and Test 2. + +**Table 9.49EF: Test Parameters for CQI test in MIMO dual stream static orthogonal conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or1}/I_{oc}$ | dB | 15 | | | | +| $\hat{I}_{or2}/I_{oc}$ | dB | 15 | | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | 1 | | | | +| Number of HS-SCCH set to be monitored | - | 1 | | | | +| CQI feedback cycle | ms | 2 | | | | +| CQI repetition factor | - | 1 | | | | +| PCI/CQI reporting Error Rate | % | 0 | | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | MIMO dual stream static orthogonal conditions | | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | Note 3: HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 3: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | +| Note 4: | The UE shall be configured in 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. | | | | | + +### 9.3.5 MIMO only with single-stream restriction Performance + +#### 9.3.5.1 MIMO only with single-stream restriction Fading Conditions + +The propagation conditions assumed for minimum performance requirements of CQI reporting under MIMO single stream conditions are defined in subclause B.2.6.1. The precoding used at the transmitter is one randomly picked but fixed precoding vector for single transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described for MIMO single stream conditions in subclause B.2.6.1. + +The reporting accuracy of CQI under MIMO with single-stream restriction is determined by the BLER performance when transmitting with a transport format indicated by the reported CQI median determined over all CQI reports that + +were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1. + +### 9.3.5.1.1 Minimum Requirement + +For the parameters specified in Table 9.49E1, and using the downlink physical channels specified in Table C.9 and Table C.12D, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.4E2. The CQI median shall be determined over all CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 with the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes to which the same CQI value was associated. + +**Table 9.49E1: Test Parameters for CQI test in MIMO single stream fading conditions** + +| Parameter | Unit | Test 1 | Test 2 | | | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--|--| +| HS-PDSCH $E_c/I_{or}$ | dB | -2 | -2.23 | | | +| $\hat{I}_{or}/I_{oc}$ | dB | | 6 | | | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | | | +| Phase reference | - | P-CPICH (Table C.9) | P-CPICH/S-CPICH (Table C.12D) | | | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -15 (using STTD) | -15 (without STTD) | | | +| DPCH $E_c/I_{or}$ | dB | -10 (using STTD) | -10 (without STTD) | | | +| Precoding weight set restriction | - | Disabled | Enabled | | | +| Maximum number of H-ARQ transmission | - | | 1 | | | +| Number of HS-SCCH set to be monitored | - | | 1 | | | +| CQI feedback cycle | ms | | 2 | | | +| CQI repetition factor | - | | 1 | | | +| PCI/CQI reporting Error Rate | % | | 0 | | | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | +| Propagation Channel | | MIMO single stream fading conditions | | | | +| Note 1: | Measurement power offset "T" is configured by RRC accordingly and as defined in [7]. | | | | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI over all Type B CQI reports that were reported together with PCI reports matching the precoding vector embedded in the propagation channel as defined in subclause B.2.6.1 is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding vector for single transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described for MIMO single stream conditions in subclause B.2.6.1. | | | | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | | | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | | | | + +**Table 9.49E2: Minimum requirement for CQI test in MIMO single stream conditions** + +| Reported CQI | Maximum BLER | | +|----------------|--------------|--------| +| | Test 1 | Test 2 | +| CQI median | 60% | 60% | +| CQI median + 3 | 15% | 15% | + +### 9.3.6 Multiflow HSDPA performance + +#### 9.3.6.1 Fading propagation conditions + +The reporting accuracy of the channel quality indicator (CQI) under fading environments is determined by the BLER performance using the transport format indicated by the reported CQI median. + +The specified requirements may be subject to further simulations to verify assumptions. + +##### 9.3.6.1.1 Minimum Requirement + +For the parameters specified in Table 9.49E3, and using the the test set-up in Annex C.5.5, the requirements are specified in terms of maximum BLERs at particular reported CQIs when transmitting a fixed transport format given by the CQI median as shown in Table 9.49E4. The BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period with the HS-PDSCH subframe of the time reference cell overlapping with the end of this CQI reference measurement period and calculating the fraction of erroneous HS-PDSCH subframes. + +**Table 9.49E3: Test Parameters for CQI test in fading – Multiflow HSDPA** + +| Parameter | Unit | Test 1 | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-PDSCH $E_c / I_{or}$ | dB | -3 | +| $\hat{I}_{or} / I_{oc}$ | dB | Specified in Annex C.5.5 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Number of additional interfering cell | | 0 | +| Phase reference | - | P-CPICH | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | ms | 2 | +| CQI repetition factor | - | 1 | +| HS-SCCH-1 signalling pattern | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. The HS-SCCH-1 shall be transmitted continuously with constant power. | +| Propagation Channel | | Case 8 | +| Note 1: | Measurement power offset "I" is configured by RRC accordingly and as defined in [7] . | | +| Note 2: | TF for HS-PDSCH is configured according to the reported CQI statistics. TF based on median CQI is used. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. | | +| Note 3: | HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. | | +| Note 4: | For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. | | +| Note 5: | The UE shall be configured in non-MIMO mode and use appropriate CQI tables according to TS 25.214. | | + +**Table 9.49E4: Minimum requirement for CQI test in fading – Multiflow HSDPA** + +| Reported CQI | Maximum BLER | +|----------------|--------------| +| | Test 1 | +| CQI median | 60% | +| CQI median + 3 | 15% | + +### 9.3.7 MIMO Performance with four transmit antennas + +#### 9.3.7.1 Four Streams Static Orthogonal Conditions + +The minimum performance requirements of channel quality indicator (CQI) reporting under MIMO with four transmit antennas and four stream conditions are defined based on a Type A reporting fraction of 100%, i.e. the parameters $N\_cqi\_typeA$ and $M\_cqi$ (see [8]) are assumed to be both set to 1. The propagation conditions assumed for minimum performance requirements of CQI reporting are defined in subclause B.2.7. + +The precoding matrix used in the transmitter shall be one randomly picked but fixed precoding matrix **W** out of the set defined in Annex B.2.7. + +#### 9.3.7.1.1 Minimum Requirement – UE HS-DSCH categories 37 and 38 + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49E5, and using the downlink physical channels specified in C.12F, the reported CQI value, for each of the HARQ process, and cells shall be in the range of $[+/-2]$ of the reported stream specific CQI median more than 90% of the time. The requirement is applicable for each cell and for each HARQ process individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and HARQ process, and independently verified to fulfil the requirement. The HARQ process and cell-specific CQI median shall be determined over all four transport block reports. + +For each HARQ process and cells, if the HS-PDSCH BLER averaged over the streams associated to the same HARQ-process identifier, using the transport format indicated by the HARQ process and cell-specific CQI median is less than or equal to [0.1], the BLER using the transport format indicated by the HARQ process and cell-specific CQI median $[+2]$ shall be greater than [0.1]. For each of the HARQ process and cells, if the HS-PDSCH BLER using the transport format indicated by the stream and cell-specific CQI median is greater than [0.1], the BLER using transport format indicated by the HARQ-process and cell-specific CQI median $[-1]$ shall be less than or equal to [0.1]. + +**Table 9.49E5: Test Parameters for CQI test for MIMO with four transmit antennas with four streams static orthogonal conditions** + +| Parameter | Unit | Test 1 | Test 2 | +|---------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-PDSCH
$E_c / I_{or}$ | dB | -2.3 | -2.3 | +| $\hat{I}_{or1} / I_{oc}$ | dB | 13 | 18 | +| $\hat{I}_{or2} / I_{oc}$ | dB | 13 | 18 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | -60 | +| Phase reference | - | P-CPICH/S-CPICH (Table C.12F) | P-CPICH/S-CPICH (Table C.12F) | +| HS-SCCH_1
$E_c / I_{or}$ | dB | -17.4 (without STTD) | -17.4 (without STTD) | +| DPCH $E_c / I_{or}$ | dB | -10 (without STTD) | -10 (without STTD) | +| Precoding weight set restriction | - | Enabled | Enabled | +| Maximum number of H-ARQ transmission | - | 1 | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | 1 | +| CQI feedback cycle | ms | 2 | 2 | +| CQI repetition factor | - | 1 | 1 | +| PCI/CQI reporting Error Rate | % | 0 | 0 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Propagation Channel | | Four branch MIMO four stream static orthogonal conditions, Annex B.2.7.1 | Four branch MIMO four stream static orthogonal conditions, Annex B.2.7.1 | + +Note 1: Measurement power offset "I" is configured by RRC accordingly and as defined in [7]. +Note 2: HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214. +Note 3: For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. + +### 9.3.8 MIMO with Four Transmit Antennas only with Dual-Stream Restriction Performance + +#### 9.3.8.1 MIMO with four transmit antennas only with dual-stream restriction fading conditions + +The propagation conditions assumed for minimum performance requirements of CQI reporting under MIMO with four transmit antennas with dual stream conditions are defined in subclause B.2.7.2. The precoding used at the transmitter is + +one randomly picked but fixed precoding vector for dual transport block transmission out of the set of possible precoding vectors as defined in [8]. The same precoding vector shall be used to generate the resulting channel coefficients as described in subclause B.2.7.2. + +The reporting accuracy of CQI under MIMO with four transmit antennas with dual-stream restriction is determined by the BLER performance when transmitting with a transport format indicated by the reported CQI median determined over all CQI reports that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.7.2. + +#### 9.3.8.1.1 Minimum Requirement + +With a serving HS-DSCH cell and secondary serving HS-DSCH cell(s) configured, using the parameters specified in Table 9.49E6, and using the downlink physical channels specified in Table C.12F, the requirements are specified in terms of maximum BLERs at particular reported CQIs for each HARQ process when transmitting a fixed transport format per HARQ process given by the HARQ process specific CQI median as shown in Table 9.49E7. The requirement is applicable for each cell and stream individually, that is the median reported CQI, as well as corresponding BLERs, are to be separately determined for each cell and stream, and independently verified against the requirement in Table 9.49E7. The HARQ process and cell-specific CQI median shall be determined over all dual transport block CQI reports that were reported together with PCI reports matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.7.2. The HARQ process and cell-specific BLER at a particular reported CQI is obtained by associating a particular CQI reference measurement period for all dual transport block CQI reports that were reported together with a PCI report that was matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.7.2 with the two transport blocks of the HS-PDSCH subframe overlapping with the end of this CQI reference measurement period and calculating the fractions of erroneous HS-PDSCH subframes to which the same CQI values were associated. + +**Table 9.49E6: Test Parameters for CQI test for MIMO with four transmit antennas only with dual streams conditions** + +| Parameter | Unit | Test 1 | +|---------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-PDSCH $E_c/I_{or}$ | dB | -2.3 | +| $\hat{I}_{or1}/I_{oc}$ | dB | 15 | +| $\hat{I}_{or2}/I_{oc}$ | dB | 15 | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Phase reference | - | P-CPICH/S-CPICH (Table C.12F) | +| HS-SCCH_1 $E_c/I_{or}$ | dB | -17.4 (without STTD) | +| DPCH $E_c/I_{or}$ | dB | -10 (without STTD) | +| Precoding weight set restriction | - | Enabled | +| Maximum number of H-ARQ transmission | - | 1 | +| Number of HS-SCCH set to be monitored | - | 1 | +| CQI feedback cycle | Ms | 2 | +| CQI repetition factor | - | 1 | +| PCI/CQI reporting Error Rate | % | 0 | +| HS-SCCH-1 signalling pattern | - | To incorporate inter-TTI=3 the six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | +| Propagation Channel | | Four branch MIMO dual stream fading conditions, Annex B.2.7.2 | + +Note 1: Measurement power offset " $\Gamma$ " is configured by RRC accordingly and as defined in [7]. + +Note 2: TF for HS-PDSCH is configured for each stream according to the reported CQI statistics. TF for each stream is based on median CQI over all dual transport block CQI reports that are reported together with a PCI report that is matching the precoding matrix embedded in the propagation channel as defined in subclause B.2.7.2. Other physical channel parameters are configured according to the CQI mapping table described in TS25.214. The precoding that shall be used in the transmitter is one randomly picked but fixed precoding matrix for dual transport block transmission out of the set of possible precoding matrices as defined in [8]. The same precoding matrix shall be used to generate the resulting channel coefficients as described for MIMO dual stream conditions in subclause B.2.7.2. + +Note 3: HS-PDSCH $E_c/I_{or}$ is decreased according to reference power adjustment $\Delta$ described in TS 25.214 + +Note 4: For any given transport format the power of the HS-SCCH and HS-PDSCH shall be transmitted continuously with constant power. + +Note 5: The UE shall be configured in 64QAM/MIMO mode and use appropriate CQI tables according to TS 25.214. + +**Table 9.49E7: Minimum requirement for CQI test in MIMO dual stream conditions** + +| Reported CQI | Maximum BLER | +|------------------|--------------| +| | Test 1 | +| CQI median | 60% | +| CQI median [+ 2] | 15% | + +## 9.4 HS-SCCH Detection Performance + +The detection performance of the HS-SCCH is determined by the probability of event $E_m$ , which is declared when the UE is signaled on HS-SCCH-1, but DTX is observed in the corresponding HS-DPCCH ACK/NACK field. The probability of event $E_m$ is denoted $P(E_m)$ . + +### 9.4.1 HS-SCCH Type 1 Single Link Performance + +For the test parameters specified in Table 9.50, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.51 and Table 9.51A the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . Enhanced performance requirements type 1 specified in Table 9.51A are based on receiver diversity. + +**Table 9.50: Test parameters for HS-SCCH detection – single link** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|-------------------------------------------------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------| +| | $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Phase reference | | - | P-CPICH | | +| P-CPICH $E_c/I_{or}$ | dB | -10 | | | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(every third TTI only , UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111110101010 | | | +| HS-DSCH TF of UE1 | | TF corresponding to CQI1 | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power. | | | +| HS-SCCH-1 TTI Signalling Pattern | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | + +**Table 9.51: Minimum requirement for HS-SCCH detection – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -9 | 0 | 0.05 | +| 2 | PA3 | -9.9 | 5 | 0.01 | +| 3 | VA30 | -10 | 0 | 0.01 | + +**Table 9.51A: Enhanced requirement type 1 for HS-SCCH detection – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -12.0 | 0 | 0.01 | +| 2 | VA30 | -15.6 | 0 | 0.01 | + +## 9.4.2 HS-SCCH Type 1 Open Loop Diversity Performance + +For the test parameters specified in Table 9.52, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.53 and Table 9.54 the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . Enhanced performance requirements type 1 specified in Table 9.54 are based on receiver diversity. + +**Table 9.52: Test parameters for HS-SCCH detection – open loop diversity** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | | +|-------------------------------------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--| +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | | +| Phase reference | | - | P-CPICH | | | +| P-CPICH $E_c/I_{or}$ | dB | -10 | | | | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(every third TTI only, UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111101010101 | | | | +| HS-DSCH TF of UE1 | | TF corresponding to CQI1 | | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power. | | | | +| HS-SCCH-1 TTI Signalling Pattern | | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | + +**Table 9.53: Minimum requirement for HS-SCCH detection – open loop diversity** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -11.6 | 0 | 0.05 | +| 2 | PA3 | -13.4 | 5 | 0.01 | +| 3 | VA30 | -11.5 | 0 | 0.01 | + +**Table 9.54: Enhanced requirement type 1 for HS-SCCH detection – open loop diversity** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -15.2 | 0 | 0.01 | +| 2 | VA30 | -16.4 | 0 | 0.01 | + +## 9.4.3 HS-SCCH Type 3 Performance + +For the test parameters specified in Table 9.55 with the downlink physical channel setup in Table C.12, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.56 and Table 9.57 the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.56 and Table 9.57 assume STTD is enabled on + +HS-SCCH and DPCH. The requirements in Table 9.56 assume HS-SCCH Type 3 coding associated with single stream transmission on HS-DSCH. The requirements in Table 9.57 assume HS-SCCH Type 3 coding associated with dual stream transmission on HS-DSCH. + +For the test parameters specified in Table 9.55 with the downlink physical channel setup in Table C.12E, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.57a, Table 9.57b, Table 9.57c and Table 9.57d, the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.57a and Table 9.57b assume STTD is disabled on HS-SCCH and DPCH. The requirements in Table 9.57c and Table 9.57d assume STTD is enabled on HS-SCCH and DPCH. The requirements in Table 9.57a and Table 9.57c assume HS-SCCH Type 3 coding associated with single stream transmission on HS-DSCH. The requirements in Table 9.57b and Table 9.57d assume HS-SCCH Type 3 coding associated with dual stream transmission on HS-DSCH. + +Minimum performance requirements specified in Table 9.56, 9.57, 9.57a, 9.57b, 9.57c and 9.57d are based on receiver diversity. + +**Table 9.55: Test parameters for HS-SCCH Type 3 detection** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-------------------------------------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------| +| | | $I_{oc}$ | | dBm/3.84 MHz | -60 | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(every third TTI only, UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111110101010 | | | | +| HS-DSCH TF of UE1 | | In case one transport block is signalled on HS-SCCH:
One transport block with TF corresponding to CQI1
Precoding vector applied to HS-PDSCH shall cycle through the four possible options.

In case two transport blocks are signalled on HS-SCCH:
Two transport blocks with the same size and same number of OVSF codes as used in the case of transmitting only one transport block.
Precoding matrix applied to HS-PDSCH shall cycle through the four possible options. | | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power. | | | | +| HS-SCCH-1 TTI Signalling Pattern | | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | + +**Table 9.56: Minimum requirement for HS-SCCH Type 3 detection, single transport block case with downlink physical channel setup in Table C.12** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -15.6 | 0 | 0.01 | +| 2 | VA3 | -16.8 | 0 | 0.01 | + +**Table 9.57: Minimum requirement for HS-SCCH Type 3 detection, dual transport block case with downlink physical channel setup in Table C.12** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 3 | PA3 | -14.7 | 0 | 0.01 | +| 4 | VA3 | -16.0 | 0 | 0.01 | + +**Table 9.57a: Minimum requirement for HS-SCCH Type 3 detection, STTD disabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -12.3 | 0 | 0.01 | +| 2 | VA3 | -14.9 | 0 | 0.01 | + +**Table 9.57b: Minimum requirement for HS-SCCH Type 3 detection, STTD disabled, dual transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 3 | PA3 | -11.4 | 0 | 0.01 | +| 4 | VA3 | -14.2 | 0 | 0.01 | + +**Table 9.57c: Minimum requirement for HS-SCCH Type 3 detection, STTD enabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -15.3 | 0 | 0.01 | +| 2 | VA3 | -16.7 | 0 | 0.01 | + +**Table 9.57d: Minimum requirement for HS-SCCH Type 3 detection, STTD enabled, dual transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 3 | PA3 | -14.4 | 0 | 0.01 | +| 4 | VA3 | -15.8 | 0 | 0.01 | + +#### 9.4.4 HS-SCCH Type 3 Performance for MIMO only with single-stream restriction + +For the test parameters specified in Table 9.57A1 with the downlink physical channel setup in Table C.12, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.57A2 and Table 9.57A3 the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.57A2 and Table 9.57A3 assume STTD is enabled on HS-SCCH and DPCH. The requirements in Table 9.57A2 and Table 9.57A3 assume HS-SCCH Type 3 coding associated with single stream transmission on HS-DSCH. Performance requirements specified in Table 9.57A3 are based on receiver diversity. + +For the test parameters specified in Table 9.57A1 with the downlink physical channel setup in Table C.12E, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.57A4, Table 9.57A5, Table 9.57A6 and Table 9.57A7, the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.57A4 and Table 9.57A5 assume STTD is disabled on HS-SCCH and DPCH. The requirements in Table 9.57A6 and Table 9.57A7 assume STTD is enabled on HS-SCCH and DPCH. The requirements in Table 9.57A4, Table 9.57A5, Table 9.57A6 and Table 9.57A7 assume HS-SCCH Type 3 coding associated with single stream transmission on HS-DSCH. Performance requirements specified in Table 9.57A5 and Table 9.57A7 are based on receiver diversity. + +**Table 9.57A1: Test parameters for HS-SCCH Type 3 detection** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------------------------------------|------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $I_{oc}$ | | dBm/3.84 MHz | -60 | +| Phase reference | | - | P-CPICH | +| P-CPICH $E_c/I_{or}$ | dB | | -10 | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | | HS-SCCH-1: 1010101010101010
(every third TTI only, UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111110101010 | +| HS-DSCH TF of UE1 | | | One transport block with TF corresponding to CQI1
Precoding vector applied to HS-PDSCH shall cycle through the four possible options. | +| HS-SCCH-1 transmission pattern | | | The HS-SCCH-1 shall be transmitted continuously with constant power. | +| HS-PDSCH transmission pattern | | | The HS-PDSCH shall be transmitted continuously with constant power. | +| HS-SCCH-1 TTI Signalling Pattern | | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | + +**Table 9.57A2: Minimum requirement for HS-SCCH Type 3 detection, single transport block case with downlink physical channel setup in Table C.12** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -8.9 | 0 | 0.01 | +| 2 | VA3 | -11.0 | 0 | 0.01 | + +**Table 9.57A3: Enhanced requirement type 1 for HS-SCCH Type 3 detection, single transport block case with downlink physical channel setup in Table C.12** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -15.6 | 0 | 0.01 | +| 2 | VA3 | -16.8 | 0 | 0.01 | + +**Table 9.57A4: Minimum requirement for HS-SCCH Type 3 detection, STTD disabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -11.0 | 3 | 0.05 | +| 2 | VA3 | -8.7 | 0 | 0.01 | + +**Table 9.57A5: Enhanced requirement type 1 for HS-SCCH Type 3 detection, STTD disabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -12.3 | 0 | 0.01 | +| 2 | VA3 | -14.9 | 0 | 0.01 | + +**Table 9.57A6: Minimum requirement for HS-SCCH Type 3 detection, STTD enabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -8.4 | 0 | 0.01 | +| 2 | VA3 | -11.1 | 0 | 0.01 | + +**Table 9.57A7: Enhanced requirement type 1 for HS-SCCH Type 3 detection, STTD enabled, single transport block case with downlink physical channel setup in Table C.12E** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -15.3 | 0 | 0.01 | +| 2 | VA3 | -16.7 | 0 | 0.01 | + +## 9.4.5 HS-SCCH Type 4 Performance + +For the test parameters specified in Table 9.57B1 with the downlink physical channel setup in Table C.12G, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.57B2 and Table 9.57B3 the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.57B2 and Table 9.57B3 assume STTD is + +disabled on HS-SCCH and DPCH. The requirements in Table 9.57B2 assume HS-SCCH Type 4 coding associated with single stream transmission on HS-DSCH. The requirements in Table 9.57B3 assume HS-SCCH Type 4 coding associated with four stream transmission on HS-DSCH. + +Minimum performance requirements specified in Table 9.57B1, 9.57B2 are based on receiver diversity. + +**Table 9.57B1: Test parameters for HS-SCCH Type 4 detection** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(every third TTI only, UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111110101010 | | | | +| HS-DSCH TF of UE1 | | In case one transport block is signalled on HS-SCCH:
One transport block with TF corresponding to CQI1
Precoding vector applied to HS-PDSCH shall cycle through all the possible options.

In case four transport blocks are signalled on HS-SCCH:
Three/four transport blocks with the same size and same number of OVSF codes as used in the case of transmitting only one transport block.
Precoding matrix applied to HS-PDSCH shall cycle through all the possible options.
Note that 2, 3 or 4 transport blocks will have the same HS-SCCH structure. | | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power. | | | | +| HS-SCCH-1 TTI Signalling Pattern | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | + +**Table 9.57B2: Minimum requirement for HS-SCCH Type 4 detection, single transport block case with downlink physical channel setup in Table C.12G** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -18 | 0 | 0.01 | +| 2 | VA3 | -19 | 0 | 0.01 | + +**Table 9.57B3: Minimum requirement for HS-SCCH Type 4 detection, four transport block case with downlink physical channel setup in Table C.12G** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 3 | PA3 | -21 | 5 | 0.01 | +| 4 | VA3 | -20 | 5 | 0.01 | + +#### 9.4.6 HS-SCCH Type 4 Performance for MIMO mode with Four Transmit Antennas Only with Dual-stream Restriction + +For the test parameters specified in Table 9.57B4 with the downlink physical channel setup in Table C.12G, for each value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.57B5 and Table 9.57B6 the measured $P(E_m)$ shall be less than or equal to the corresponding specified value of $P(E_m)$ . The requirements in Table 9.57B5 and Table 9.57B6 assume STTD is disabled on HS-SCCH and DPCH. The requirements in Table 9.57B5 and Table 9.57B6 assume HS-SCCH Type 4 coding associated with dual stream transmission on HS-DSCH. Performance requirements specified in Table 9.57B5 and 9.57B6 are based on (dual branches) receiver diversity. + +**Table 9.57B4: Test parameters for HS-SCCH Type 4 detection** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(every third TTI only, UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010
HS-SCCH-3: 0001101010101010
HS-SCCH-4: 0001111110101010 | | | | +| HS-DSCH TF of UE1 | | In case one transport block is signalled on HS-SCCH:
One transport block with TF corresponding to CQI1
Precoding vector applied to HS-PDSCH shall cycle through all the possible options.

Two transport blocks are signalled on HS-SCCH:
Two transport blocks with the same size and same number of OVSF codes as used in the case of transmitting only one transport block.
Precoding matrix applied to HS-PDSCH shall cycle through all the possible options. | | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power. | | | | +| HS-SCCH-1 TTI Signalling Pattern | - | The six sub-frame HS-SCCH-1 signalling pattern shall be "...XOOXOO...", where "X" indicates TTI in which the HS-SCCH-1 uses the identity of the UE under test, and "O" indicates TTI in which the HS-SCCH-1 uses a different UE identity. | | | | + +**Table 9.57B5: Enhanced requirement type 1 for HS-SCCH Type 4 detection, single transport block case with downlink physical channel setup in Table C.12G** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -17 | 5 | 0.01 | +| 2 | VA3 | -17.8 | 5 | 0.01 | + +**Table 9.57B6: Enhanced requirement type 1 for HS-SCCH Type 4 detection, dual transport block case with downlink physical channel setup in Table C.12G** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|----------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | $P(E_m)$ | +| 1 | PA3 | -19 | 10 | 0.01 | +| 2 | VA3 | -18.5 | 10 | 0.01 | + +## 9.5 HS-SCCH-less demodulation of HS-DSCH (Fixed Reference Channel) + +The receiver performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) with HS-SCCH-less operation in multi-path fading environment is determined by the information bit throughput R. + +The propagation conditions for this subclause are defined in table B.1C. + +During the Fixed Reference Channel tests the behaviour of the Node-B emulator in response to the ACK/NACK signalling field of the HS-DPCCH is specified in Table 9.1A. + +Performance requirements in this section assume sufficient power allocation to HS-SCCH\_1, so that the probability of detection failure, when the HS-SCCH-1 uses the identity of the UE under test, is very low. + +### 9.5.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 7 + +The requirements are specified in terms of a minimum information bit throughput R for the DL reference channels H-set 7 specified in Annex A.7.1.7, with the addition of the parameters in Table 9.58 and the downlink physical channel setup according to table C.8. + +Using this configuration the throughput shall meet or exceed the minimum requirements specified in table 9.59. Enhanced performance requirements type 1 specified in Table 9.60 are based on receiver diversity. + +**Table 9.58: Test Parameters for Testing QPSK FRCs H-Set 7** + +| Parameter | Unit | Test 1 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|---------| +| Phase reference | - | | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | | -60 | +| Redundancy and
constellation version
coding sequence | - | | {0,3} | +| Maximum number of
HARQ transmission | - | | 2 | +| NOTE: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for redundancy version 3 transmissions intended for the UE. | | | | + +**Table 9.59: Minimum requirement, Fixed Reference Channel (FRC) H-Set 7** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-------------------------------|----------------------------|------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | T-put $R$ (kbps) | +| 1 | Case 8 | -6 | 0 | 19.9 | + +**Table 9.60: Enhanced requirement type 1, Fixed Reference Channel (FRC) H-Set 7** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-------------------------------|----------------------------|------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | T-put $R$ (kbps) | +| 1 | Case 8 | -9 | 0 | 23.5 | + +## 9.6 Requirements for HS-DSCH and HS-SCCH reception in CELL\_FACH state + +The requirements determined in this section apply for UE being able to receive HS-DSCH and HS-SCCH in CELL\_FACH state. + +### 9.6.1 HS-DSCH demodulation requirements (Single Link) + +The receiver single link performance of the High Speed Physical Downlink Shared Channel (HS-DSCH) is determined by the RLC SDU error rate (RLC SDU ER). + +#### 9.6.1.1 Requirement QPSK, Fixed Reference Channel (FRC) H-Set 3 + +The requirements are specified in terms of a minimum RLC SDU error rate (RLC SDU ER) for the DL reference channel H-Set 3 (QPSK version) specified in A.7.1.3, with the addition of the parameters in Table 9.61 and the downlink physical channel setup according to Table C.12A. For the test parameters specified in Table 9.61, for the + +value of HS-DSCH-1 $E_c/I_{or}$ specified in Table 9.62 the measured RLC SDU ER shall be less than or equal to the corresponding specified value of RLC SDU ER. + +**Table 9.61: Test Parameters for Testing QPSK FRCs H-Set 3** + +| Parameter | Unit | Test 1 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|--------------|-----| +| | Phase reference | P-CPICH | | +| | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | Redundancy and constellation version coding sequence | {0,2,5,6} | | +| | Number of HARQ transmission | 4 | | +| NOTE: The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE.
NOTE: The HS-PDSCH is transmitted using all four HARQ transmissions cycling through the different redundancy and constellation versions. | | | | + +**Table 9.62: Minimum requirement QPSK, Fixed Reference Channel (FRC) H-Set 3** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|-------------------------------|--------------------------------------------| +| | | HS-PDSCH
$E_c/I_{or}$ (dB) | RLC SDU ER
$\hat{I}_{or}/I_{oc} = 0$ dB | +| 1 | VA30 | -6 | 0.82 | + +## 9.6.2 HS-SCCH Detection Performance + +The detection performance of the HS-SCCH is determined by RLC SDU error rate (RLC SDU ER). + +### 9.6.2.1 HS-SCCH Type 1 Single Link Performance + +For the test parameters specified in Table 9.63, for the value of HS-SCCH-1 $E_c/I_{or}$ specified in Table 9.64 the measured RLC SDU ER shall be less than or equal to the corresponding specified value of RLC SDU ER. The downlink physical channel setup according to Table C.12B. + +**Table 9.63: Test parameters for HS-SCCH detection – single link** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|-------------------------------------------------------------------|------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|--------| +| $I_{oc}$ | | dBm/3.84 MHz | -60 | | +| Phase reference | | - | P-CPICH | | +| P-CPICH $E_c/I_{or}$ | dB | -10 | | | +| HS-SCCH UE Identity
( $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ ) | | HS-SCCH-1: 1010101010101010
(UE under test addressed solely via HS-SCCH-1)
HS-SCCH-2: 0001001010101010 | | | +| HS-DSCH TF of UE1 | | TF corresponding to CQI1 | | | +| HS-SCCH-1 transmission pattern | | The HS-SCCH-1 shall be transmitted continuously with constant power. | | | +| HS-PDSCH transmission pattern | | The HS-PDSCH shall be transmitted continuously with constant power, without re-transmissions. | | | +| HS-SCCH-1 TTI Signalling Pattern | | - | The identity of the UE under test shall be used on every fourth TTI. | | + +**Table 9.64: Minimum requirement for HS-SCCH detection – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------------|----------------------------|------------| +| | | HS-SCCH-1
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | RLC SDU ER | +| 3 | VA30 | -10 | 0 | 0.01 | + +## 10 Performance requirement (E-DCH) + +### 10.1 General + +The performance requirements for the UE in this subclause are specified for the propagation conditions specified in Annex B.2.2 and the Downlink Physical channels specified in Annex C.3.2. + +Unless otherwise stated the receiver characteristics are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna 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 the fading of the signals and the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. Enhanced performance requirements Type 1 are based on receiver diversity. + +### 10.2 Detection of E-DCH HARQ ACK Indicator Channel (E-HICH) + +#### 10.2.1 Single link performance + +The receive characteristics of the E-DCH HARQ ACK Indicator Channel (E-HICH) in different multi-path fading environments are determined by the missed ACK and false ACK values. + +### 10.2.1.1 Performance requirement + +For the parameters specified in Table 10.1 the average downlink E-HICH $E_c/I_{or}$ power ratio shall be below the specified value for the missed ACK probabilities in Table 10.2 and 10.3 for minimum performance requirements and Table 10.2A and 10.3A for enhanced performance requirements Type 1. For the parameters specified in Table 10.1 the false ACK probability shall be below the specified value in Table 10.4 and 10.5. + +**Table 10.1: Requirement scenario parameters for E-HICH – RLS containing the Serving E-DCH cell** + +| Parameter | Unit | Missed ACK | False ACK | | +|-----------|------|---------------------------|--------------|------------------------| +| | | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | | Phase reference | - | P-CPICH | +| | | P-CPICH $E_c/I_{or}$ | dB | -10 | +| | | E-HICH signalling pattern | - | 100% ACK      100% DTX | + +**Table 10.2: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -28.3 | 0 | 0.01 | + +**Table 10.2A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -31.7 | 0 | 0.01 | + +**Table 10.3: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed ACK probability | +| 2 | VA30 | -35.1 | 0 | 0.01 | + +**Table 10.3A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed ACK probability | +| 2 | VA30 | -38.3 | 0 | 0.01 | + +**Table 10.4: Minimum requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|----------------------------|-----------------------| +| | | $\hat{I}_{or}/I_{oc}$ (dB) | False ACK probability | +| 3 | VA30 | 0 | 0.5 | + +**Table 10.5: Minimum requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|----------------------------|-----------------------| +| | | $\hat{I}_{or}/I_{oc}$ (dB) | False ACK probability | +| 4 | VA30 | 0 | 0.5 | + +## 10.2.2 Detection in Inter-Cell Handover conditions + +The receive characteristics of the E-DCH HARQ ACK Indicator Channel (E-HICH) is determined during an inter-cell soft handover by the missed ACK and false ACK error probabilities. During the soft handover a UE receives signals from different cells. A UE has to be able to detect E-HICH signalling from different cells belonging to different RLS, containing and not containing the Serving E-DCH cell. + +### 10.2.2.1 Performance requirement for RLS not containing the Serving E-DCH cell + +For the parameters specified in Table 10.6 the average downlink E-HICH $E_c/I_{or}$ power ratio of cell belonging to RLS not containing the Serving E-DCH cell shall be below the specified value for the missed ACK probabilities in Table 10.7 and 10.8 for minimum performance requirements and Table 10.7A and 10.8A for enhanced performance requirements Type 1. For the parameters specified in Table 10.6 the false ACK probability shall be below the specified value in Table 10.9 and 10.10. + +**Table 10.6: Requirement scenario parameters for E-HICH – cell belonging to RLS not containing the Serving E-DCH cell** + +| Parameter | Unit | Missed ACK | False ACK | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------------|-----------------------------| +| | | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | | Phase reference | - | P-CPICH | +| | | P-CPICH $E_c/I_{or}$ | dB | -10 | +| | | E-HICH signalling pattern for the Serving E-DCH cell | - | 100% NACK (-1) 1 | +| | | E-HICH signalling pattern for cell belonging to RLS not containing the Serving E-DCH cell | 100% ACK (+1) | 100% NACK (0) | +| Note 1 | The Serving E-DCH cell E-HICH $E_c/I_{or}$ power level is set to -16 dB when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots and to -23 dB when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots. | | | | + +**Table 10.7: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH
$E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -16.3 | 0 | 0.05 | + +**Table 10.7A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH
$E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -20.6 | 0 | 0.05 | + +**Table 10.8: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH
$E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 2 | VA30 | -23.6 | 0 | 0.05 | + +**Table 10.8A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH
$E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 2 | VA30 | -27.8 | 0 | 0.05 | + +**Table 10.9: Requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|--------------------------------------------------------|-----------------------| +| | | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | False ACK probability | +| 3 | VA30 | 0 | 2E-4 | + +**Table 10.10: Requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – cell belonging to RLS not containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|--------------------------------------------------------|-----------------------| +| | | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | False ACK probability | +| 4 | VA30 | 0 | 2E-4 | + +### 10.2.2.2 Performance requirement for RLS containing the serving E-DCH cell + +For the parameters specified in Table 10.11 the average downlink E-HICH $E_c/I_{or}$ power ratio of cell belonging to RLS containing the serving E-DCH cell shall be below the specified value for the missed ACK probabilities in Table 10.12 and 10.13 for minimum performance requirements and Table 10.12A and 10.13A for enhanced performance requirements Type 1. For the parameters specified in Table 10.11 the false ACK probability shall be below the specified value in Table 10.14 and 10.15. + +**Table 10.11: Requirement scenario parameters for E-HICH – RLS containing the serving cell in SHO** + +| Parameter | Unit | Missed ACK | False ACK | +|-------------------------------------------------------------------------------------------|--------------|---------------|---------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| Phase reference | - | P-CPICH | | +| P-CPICH $E_c/I_{or}$ | dB | -10 | | +| E-HICH signalling pattern for Serving E-DCH cell | - | 100% ACK (+1) | 100% DTX (0) | +| E-HICH signalling pattern for cell belonging to RLS not containing the Serving E-DCH cell | | 100% NACK (0) | 100% NACK (0) | + +**Table 10.12: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-------------------------------------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) for Serving E-DCH cell (ACK) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -23.2 | 0 | 0.05 | + +**Table 10.12A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-------------------------------------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) for Serving E-DCH cell (ACK) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 1 | VA30 | -27.1 | 0 | 0.05 | + +**Table 10.13: Minimum requirement for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-------------------------------------------------------|--------------------------------------------------------|------------------------| +| | | E-HICH $E_c/I_{or}$ (dB) for Serving E-DCH cell (ACK) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK probability | +| 2 | VA30 | -29.7 | 0 | 0.05 | + +**Table 10.13A: Enhanced performance requirement Type 1 for Missed ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|----------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| | | E-HICH
$E_c/I_{or}$ (dB) for
Serving E-DCH cell
(ACK) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed ACK
probability | +| 2 | VA30 | -33.4 | 0 | 0.05 | + +**Table 10.14: Requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 3 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|--------------------------------------------------------|-----------------------| +| | | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | False ACK probability | +| 3 | PA3 | 0 | 0.1 | +| 4 | VA120 | 0 | 0.1 | + +**Table 10.15: Requirement for False ACK when hybrid ARQ acknowledgement indicator is transmitted using 12 consecutive slots – RLS containing the Serving E-DCH cell** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|--------------------------------------------------------|-----------------------| +| | | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | False ACK probability | +| 5 | PA3 | 0 | 0.1 | +| 6 | VA120 | 0 | 0.1 | + +## 10.3 Detection of E-DCH Relative Grant Channel (E-RGCH) + +### 10.3.1 Single link performance + +The receive characteristics of the E-DCH Relative Grant Channel (E-RGCH) in multi-path fading environment is determined by the missed UP/DOWN and missed HOLD. + +#### 10.3.1.1 Performance requirement + +For the parameters specified in Table 10.16 the average downlink E-RGCH $E_c/I_{or}$ power ratio shall be below the specified value for the missed UP/DOWN probabilities in Table 10.17 and 10.18 for minimum performance requirements and Table 10.17A and 10.18A for enhanced performance requirements Type 1. For the parameters specified in Table 10.16 the missed HOLD probability shall be below the specified value in Table 10.19 and 10.20. + +**Table 10.16: Requirement scenario parameters for E-RGCH – Serving E-DCH RLS** + +| Parameter | Unit | Missed UP/DOWN | Missed HOLD | | +|-----------|------|---------------------------|--------------|---------------------------------| +| | | $I_{oc}$ | dBm/3.84 MHz | -60 | +| | | Phase reference | - | P-CPICH | +| | | P-CPICH $E_c/I_{or}$ | dB | -10 | +| | | E-RGCH signalling pattern | - | 50% UP
50% DOWN
100% HOLD | + +**Table 10.17: Minimum requirement for Missed UP/DOWN when relative scheduling grant is transmitted using 3 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|----------------------------| +| | | E-RGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed UP/DOWN probability | +| 1 | VA30 | -24.4 | 0 | 0.05/0.05 | + +**Table 10.17A: Enhanced performance requirement Type 1 for Missed UP/DOWN when relative scheduling grant is transmitted using 3 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|----------------------------| +| | | E-RGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed UP/DOWN probability | +| 1 | VA30 | -28.6 | 0 | 0.05/0.05 | + +**Table 10.18: Minimum requirement for Missed UP/DOWN when relative scheduling grant is transmitted using 12 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|----------------------------| +| | | E-RGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed UP/DOWN probability | +| 2 | VA30 | -31 | 0 | 0.05/0.05 | + +**Table 10.18A: Enhanced performance requirement Type 1 for Missed UP/DOWN when relative scheduling grant is transmitted using 12 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|----------------------------| +| | | E-RGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Missed UP/DOWN probability | +| 2 | VA30 | -35.0 | 0 | 0.05/0.05 | + +**Table 10.19: Requirement for Missed HOLD when relative scheduling grant is transmitted using 3 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|----------------------------|-------------------------| +| | | $\hat{I}_{or}/I_{oc}$ (dB) | Missed HOLD probability | +| 3 | VA30 | 0 | 0.1 | + +**Table 10.20: Requirement for Missed HOLD when relative scheduling grant is transmitted using 12 consecutive slots – Serving E-DCH RLS** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|----------------------------|-------------------------| +| | | $\hat{I}_{or}/I_{oc}$ (dB) | Missed HOLD probability | +| 4 | VA30 | 0 | 0.1 | + +## 10.3.2 Detection in Inter-Cell Handover conditions + +The receive characteristics of the E-DCH Relative Grant Channel (E-RGCH) is determined during an inter-cell soft handover by the missed UP/DOWN and missed HOLD error probabilities. During the soft handover a UE receives signals from different cells. A UE has to be able to detect E-RGCH signalling from different cells, Serving E-DCH cell and Non-serving E-DCH RL. + +### 10.3.2.1 Performance requirement for Non-serving E-DCH RL + +For the parameters specified in Table 10.21 the missed HOLD probability shall be below the specified value in Table 10.22. For the parameters specified in Table 10.21 the average downlink E-RGCH $E_c/I_{or}$ power ratio shall be below the specified value for the missed DOWN probabilities in Table 10.23 for minimum performance requirements and Table 10.23A for enhanced performance requirements Type 1. + +**Table 10.21: Requirement scenario parameters for E-RGCH – Non-serving E-DCH RL** + +| Parameter | Unit | Missed HOLD | Missed DOWN | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------------------------------------|--------------|-----------------------|-----------------------| +| | | $I_{oc}$ | dBm/3.84 MHz | -60 | | +| | | Phase reference | - | P-CPICH | | +| | | P-CPICH $E_c/I_{or}$ | dB | -10 | | +| | | E-RGCH signalling pattern for Serving E-DCH cell | - | 100% UP 1 | 100% UP 1 | +| | | E-AGCH information | | Fixed SG 2 | Fixed SG 2 | +| | | E-RGCH signalling pattern for Non-serving E-DCH RL | | 100% HOLD | 100% DOWN | +| Note 1 Serving E-DCH cell E-RGCH $E_c/I_{or}$ power level is set to -22 dB and relative scheduling grant is transmitted using 12 consecutive slots. | | | | | | +| Note 2 Serving E-DCH cell E-AGCH $E_c/I_{or}$ power level is set to -15 dB and E-AGCH TTI length is 10ms. | | | | | | + +**Table 10.22: Requirement for Missed HOLD when relative scheduling grant is transmitted using 15 consecutive slots – Non-serving E-DCH RL** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|--------------------------------------------------------|-------------------------| +| | | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed HOLD probability | +| 1 | VA30 | 0 | 0.005 | + +**Table 10.23: Minimum requirement for Missed DOWN when relative scheduling grant is transmitted using 15 consecutive slots – Non-serving E-DCH RL** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|--------------------------------------------------------|-------------------------| +| | | E-RGCH $E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed DOWN probability | +| 2 | VA30 | -27.3 | 0 | 0.05 | + +**Table 10.23A: Enhanced performance requirement Type 1 for Missed DOWN when relative scheduling grant is transmitted using 15 consecutive slots – Non-serving E-DCH RL** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|--------------------------------------------------------|-------------------------| +| | | E-RGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or1}/I_{oc}$ and $\hat{I}_{or2}/I_{oc}$ (dB) | Missed DOWN probability | +| 2 | VA30 | -31.2 | 0 | 0.05 | + +## 10.3A Determination of common E-RGCH radio links in CELL\_FACH state + +### 10.3A.1 Introduction + +The requirements defined in this section are applicable to a UE supporting Common E-RGCH based interference control [7]. + +Uplink interference from E-DCH transmission in CELL\_FACH can be controlled based on the UE monitoring an E-RGCH channel from the neighboring cells. The UE determines the set of cells from candidate set for common E-RGCH monitoring by comparing CPICH\_Ec/No of the neighbor cell within a threshold of the serving cell CPICH\_Ec/No according to the procedure specified in [7]. The UE starts monitoring common E-RGCH from common E-RGCH radio link (RL). + +### 10.3A.2 Requirements + +#### 10.3A.2.1 Determination when a cell for common E-RGCH RL has been already identified + +This test case is targeting the scenario where UE has already been in CELL\_FACH state for a long enough time to identify candidate cells for common E-RGCH monitoring. The purpose of this test is to verify the amount of time for UE to determine common E-RGCH RL only without including a cell identification time, and to verify the missed down probability after determination. + +The test parameters are given in Tables 10.23B and 10.23C below. The test consists of three successive time periods, with a time duration of T1, T2 and T3 respectively. During time duration T1, the UE shall not initiate PRACH preamble transmission for common E-DCH transmission. At the beginning of time duration T2, the UE shall initiate PRACH preamble transmission for common E-DCH transmission. During time duration T3, the common E-DCH resource shall be released. + +NOTE: UE may not initiate PRACH preamble transmission for common E-DCH transmission exactly at the beginning of time duration T2. + +Missed DOWN probability from Cell 2 shall be measured after 60 ms from initial PRACH preamble transmission until the end of time duration T2. Test shall be repeated to test common E-RGCH RL determination performance. The overall missed DOWN probability shall not exceed 5%. The overall missed down probability shall be measured over multiple repetitions of T2. If the UE fails to determine to monitor Cell 2 during a certain repetition of T1, T2, and T3, then the missed down probability for that repetition will be 100%. + +**Table 10.23B: General test parameters for test 1** + +| Parameter | Unit | Value | Comment | +|-----------------------------------------------|------|----------------|----------------------------------------------------------------------| +| Phase reference | | P-CPICH | | +| Active cell | | Cell 1 | | +| Candidate cell for Common E-RGCH RL | | Cell 2 | | +| L3 filter coefficient | | 5 1 | Applicable for event 1A | +| Reporting range | dB | 4.5 | Applicable for event 1A | +| Hysteresis | dB | 0 | Applicable for event 1A | +| Reporting deactivation threshold | | 0 | Applicable for event 1A | +| Time to Trigger | Ms | 0 | Applicable for event 1A | +| S intrasearch for Cell 1 | dB | Not sent | | +| Q offset1s,n for Cell 2 | dB | 50 | To prevent reselection to Cell 2 during the test | +| Q offset2s,n for Cell 2 | dB | 50 | To prevent reselection to Cell 2 during the test | +| E-RGCH signalling pattern for Cell 1 | | 100% UP | Relative scheduling grant is transmitted using 12 consecutive slots. | +| E-RGCH signalling pattern for Cell 2 | | 100% DOWN | Relative scheduling grant is transmitted using 12 consecutive slots. | +| E-AGCH information for Cell 1 | | Fixed SG | E-AGCH TTI length is 10 ms. | +| Common E-RGCH channel configuration list | | 24 | | +| T1 | S | 1 | UE shall identify Cell 2 during T1. | +| T2 | S | 3 | | +| T3 | S | 1 | | + +NOTE 1: L3 filter coefficient assumes the default filter input rate as 10 ms. + +**Table 10.23C: Cell specific test parameters for test 1** + +| Parameter | Unit | Cell 1 | | | Cell 2 | | | +|-----------------------|--------------|--------|-------|-------|--------|-------|-------| +| | | T1 | T2 | T3 | T1 | T2 | T3 | +| CPICH_Ec/Ior | dB | -10 | | | -10 | | | +| PCCPCH_Ec/Ior | dB | -12 | | | -12 | | | +| SCH_Ec/Ior | dB | -12 | | | -12 | | | +| PICH_Ec/Ior | dB | -15 | | | -15 | | | +| E-RGCH_Ec/Ior | dB | -20 | | | -35.3 | | | +| E-AGCH_Ec/Ior | dB | -13 | | | N/A | | | +| OCNS | | Note 1 | | | Note 1 | | | +| | dB | 10 | 10 | 10 | 15 | 15 | 15 | +| | dBm/3,84 MHz | -60 | | | | | | +| CPICH_Ec/Io | dB | -16.3 | -16.3 | -16.3 | -11.3 | -11.3 | -11.3 | +| Propagation Condition | | AWGN | | | | | | + +NOTE 1: The power of the OCNS channel that is added shall make the total power from the cell to be equal to Ior. + +NOTE 2: Cell 2 PSC shall be changed from T1 in one test to T1 in the next test among Common E-RGCH channel configuration list. + +## 10.3A.2.2 Determination when a cell for common E-RGCH RL has not been identified + +This test case is targeting the scenario where UE enters into CELL\_FACH and E-DCH resources are allocated immediately, before candidate cells for E-RGCH monitoring have been identified. The purpose of this test is to verify the amount of time for UE to determine common E-RGCH RL including the cell identification time for a candidate cell for common E-RGCH RL. + +The test parameters are given in Tables 10.23D and 10.23E below. The test consists of two successive time periods, with a time duration of T1 and T2 respectively. At the beginning of time duration T1, the UE shall initiate PRACH preamble transmission for common E-DCH transmission. During time duration T2, the common E-DCH resource shall be released. + +NOTE: UE may not initiate PRACH preamble transmission for common E-DCH transmission exactly at the beginning of time duration T1. + +Missed DOWN probability from Cell 2 shall be measured after 120 ms from initial PRACH preamble transmission until the end of time duration T1. Test shall be repeated to test common E-RGCH RL determination performance. The overall missed DOWN probability shall not exceed 24%. The overall missed down probability shall be measured over multiple repetitions of T1. If the UE fails to determine to monitor Cell 2 during a certain repletion of T1 and T2, then the missed down probability for that repetition will be 100%. + +**Table 10.23D: General test parameters for test 2** + +| Parameter | Unit | Value | Comment | +|-------------------------------------------------------------------------------|------|----------------|----------------------------------------------------------------------| +| Phase reference | | P-CPICH | | +| Active cell | | Cell 1 | | +| Candidate cell for Common E-RGCH RL | | Cell 2 | | +| L3 filter coefficient | | 5 1 | Applicable for event 1A | +| Reporting range | dB | 4.5 | Applicable for event 1A | +| Hysteresis | dB | 0 | Applicable for event 1A | +| Reporting deactivation threshold | | 0 | Applicable for event 1A | +| Time to Trigger | ms | 0 | Applicable for event 1A | +| E-RGCH signalling pattern for Cell 1 | | 100% UP | Relative scheduling grant is transmitted using 12 consecutive slots. | +| E-RGCH signalling pattern for Cell 2 | | 100% DOWN | Relative scheduling grant is transmitted using 12 consecutive slots. | +| E-AGCH information for Cell 1 | | Fixed SG | E-AGCH TTI length is 10 ms. | +| Common E-RGCH channel configuration list | | 24 | | +| T1 | s | 3 | | +| T2 | s | 1 | | +| NOTE 1: L3 filter coefficient assumes the default filter input rate as 10 ms. | | | | + +**Table 10.23E: Cell specific test parameters for test 2** + +| Parameter | Unit | Cell 1 | | Cell 2 | | +|--------------------------------------------------------------------------------------------------------------------------------|--------------|--------|-----|--------|-----------| +| | | T1 | T2 | T1 | T2 | +| CPICH_E c /I or | dB | -10 | | -10 | | +| PCCPCH_E c /I or | dB | -12 | | -12 | | +| SCH_E c /I or | dB | -12 | | -12 | | +| PICH_E c /I or | dB | -15 | | -15 | | +| E-RGCH_E c /I or | dB | -22 | | -27.3 | | +| E-AGCH_E c /I or | dB | -15 | | N/A | | +| OCNS | | Note 1 | | Note 1 | | +| | dB | 0 | 0 | 2 | -infinity | +| | dBm/3,84 MHz | -60 | | | | +| CPICH_E c /I o | dB | -15.5 | -13 | -13.5 | -infinity | +| Propagation Condition | | VA30 | | | | +| NOTE 1: The power of the OCNS channel that is added shall make the total power from the cell to be equal to I or . | | | | | | +| NOTE 2: Cell 2 PSC shall be changed from T1 in one test to T1 in the next test among Common E-RGCH channel configuration list. | | | | | | + +## 10.4 Demodulation of E-DCH Absolute Grant Channel (E-AGCH) + +### 10.4.1 Single link performance + +The receive characteristics of the E-DCH Absolute Grant Channel (E-AGCH) in multi-path fading environment is determined by the missed detection probability. + +#### 10.4.1.1 Performance requirement + +For the parameters specified in Table 10.24 the average downlink E-AGCH $E_c/I_{or}$ power ratio shall be below the specified value for the missed detection probability in Table 10.25 for minimum performance requirements and Table 10.25A for enhanced performance requirements Type 1. + +**Table 10.24: Test parameters for E-AGCH detection – single link** + +| Parameter | Unit | Missed detection | +|----------------------|--------------|------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| Phase reference | - | P-CPICH | +| P-CPICH $E_c/I_{or}$ | dB | -10 | +| E-AGCH information | - | Varying SG | +| E-AGCH TTI length | ms | 10 | + +**Table 10.25: Minimum requirement for E-AGCH detection – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|----------------------------| +| | | E-AGCH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Miss detection probability | +| 1 | VA30 | -23.2 | 0 | 0.01 | + +**Table 10.25A: Enhanced performance requirement Type 1 for E-AGCH detection – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|----------------------------| +| | | E-AGCH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Miss detection probability | +| 1 | VA30 | -26.8 | 0 | 0.01 | + +## 10.4A Demodulation of E-DCH Absolute Grant Channel (E-AGCH) with Time Multiplexed UE grants + +This section specifies performance requirements when the UEs in a cell are scheduled grants in a time multiplexed fashion. The performance metric used to evaluate E-AGCH detection performance is the percentage of incorrect decisions by UE as a function of mis-detection rate ( $P_{MD}$ ) based on E-AGCH presence check, false alarm rate ( $P_{FA}$ ) based on E-AGCH presence check, and also the E-AGCH CRC check failure rate ( $P_{CRC}$ ). + +## 10.4A.1 Single link performance + +The receive characteristics of the E-DCH Absolute Grant Channel (E-AGCH) in multi-path fading environment is determined by the missed detection probability. + +### 10.4A.1.1 Performance requirement + +For the parameters specified in Table 10.26 the average downlink E-AGCH $E_c/I_{or}$ power ratio shall be below the specified value for the performance metric in Table 10.27, Table 10.28 and Table 10.30 for minimum performance requirements, and Table 10.29 and Table 10.31 for enhanced performance requirements Type 1. + +**Table 10.26: Test parameters for E-AGCH detection – single link** + +| Parameter | Unit | Test 1 | Test 2 and Test 3 | Test 4 and Test 5 | +|----------------------|--------------|---------|-------------------------------|------------------------------| +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | +| Phase reference | - | P-CPICH | | | +| P-CPICH $E_c/I_{or}$ | dB | -10 | | | +| E-AGCH information | - | - | Varying SG | Varying SG | +| E-RNTI | | NA | Set E-RNTI for a different UE | Set E-RNTI for UE under test | +| E-AGCH TTI length | ms | 2 | | | + +**Table 10.27: Minimum requirement for E-AGCH detection when no E-AGCH is transmitted** + +| Test Number | Propagation Conditions | Reference value | | +|-------------|------------------------|----------------------------|-----------------------------| +| | | $\hat{I}_{or}/I_{oc}$ (dB) | Performance Metric $P_{FA}$ | +| 1 | AWGN | 0 | 0.0015 | + +**Table 10.28: Minimum requirement for E-AGCH detection when E-RNTI is not set for UE under test – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|-----------------------------| +| | | E-AGCH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Performance Metric $P_{MD}$ | +| 2 | AWGN | -21 | 0 | 0.001 | + +**Table 10.29: Enhanced performance requirement Type 1 for E-AGCH detection when E-RNTI is not set for UE under test – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|--------------------------|----------------------------|-----------------------------| +| | | E-AGCH $E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Performance Metric $P_{MD}$ | +| 3 | AWGN | -24 | 0 | 0.001 | + +**Table 10.30: Minimum requirement for E-AGCH detection when E-RNTI is set for UE under test – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|---------------------------------------------------------| +| | | E-AGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Performance Metric
$P_{MD} + (1 - P_{MD}) * P_{CRC}$ | +| 4 | AWGN | -21 | 0 | 0.01 | + +**Table 10.31: Enhanced performance requirement Type 1 for E-AGCH detection when E-AGCH is for UE under test – single link** + +| Test Number | Propagation Conditions | Reference value | | | +|-------------|------------------------|-----------------------------|----------------------------|---------------------------------------------------------| +| | | E-AGCH
$E_c/I_{or}$ (dB) | $\hat{I}_{or}/I_{oc}$ (dB) | Performance Metric
$P_{MD} + (1 - P_{MD}) * P_{CRC}$ | +| 5 | AWGN | -24 | 0 | 0.01 | + +## 11 Performance requirement (MBMS) + +Unless otherwise stated the receiver characteristics are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna 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 the fading of the signals and the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. + +### 11.1 Demodulation of MCCH + +The receive characteristic of the MCCH is determined by the RLC SDU error rate (RLC SDU ER). The requirement is valid for all RRC states for which the UE has capabilities for MBMS. + +#### 11.1.1 Minimum requirement + +For the parameters specified in Table 11.1 the average downlink S-CCPCH $_E_c/I_{or}$ power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.2. + +**Table 11.1: Parameters for MCCH detection** + +| | Parameter | Unit | Test 1 | +|-----------------------|-----------------|----------|---------| +| | Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| $\hat{I}_{or}/I_{oc}$ | dB | -3 | | +| MCCH Data Rate | | 7.6 kbps | | +| Propagation condition | | VA3 | | + +**Table 11.2: Test requirements for MCCH detection** + +| Test Number | S-CCPCH_Ec/Ior (dB) | RLC SDU ER | +|-------------|---------------------|------------| +| 1 | -11.6 | 0.01 | + +## 11.1.2 Minimum requirement for MBSFN + +Requirement in this subclause is applicable to UEs that are capable of receiving MBSFN with at least two receive antenna connectors. + +For the parameters specified in Table 11.1a the average downlink S-CCPCH\_Ec/Ior power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.2a. + +**Table 11.1a: Parameters for MCCH detection** + +| Parameter | Unit | Test 1 | +|-----------------------|--------------|---------------------------------------| +| Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | +| $\hat{I}_{or}/I_{oc}$ | dB | 12 | +| MCCH data rate | kbps | 7.6 | +| Propagation condition | | MBSFN channel model ( see Appendix B) | + +**Table 11.2a: Test requirements for MCCH detection** + +| Test Number | S-CCPCH_Ec/Ior (dB) | RLC SDU ER | +|-------------|---------------------|------------| +| 1 | -24.9 | 0.01 | + +## 11.2 Demodulation of MTCH + +The receive characteristic of the MTCH is determined by RLC SDU error rate (RLC SDU ER). RLC SDU ER is specified for each individual data rate of the MTCH. The requirement is valid for all RRC states for which the UE has capabilities for MBMS. + +### 11.2.1 Minimum requirement + +For the parameters specified in Table 11.3 the average downlink S-CCPCH\_Ec/Ior power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.4. If the UE supports optional enhanced performance requirements type1 for MBMS then for the parameters specified in Table 11.3 the average downlink S-CCPCH\_Ec/Ior power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.4a. + +**Table 11.3: Parameters for MTCH detection** + +| | Parameter | Unit | Test 1 | Test 2 | Test 3 | +|--------------------------------------------------|-----------------|----------|------------------------------|------------------------------|--------| +| | Phase reference | - | P-CPICH | | | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | | | +| $\hat{I}_{or}/I_{oc}$ | dB | -3 | -3 | -3 | | +| MTCH Data Rate | | 128 kbps | 256 kbps | 128 kbps | | +| Transmission Time Interval | | 40 | 40 | 80 | | +| Propagation condition | | VA3 | | | | +| Number of Radio Links p | | 3 | 3 | 3 | | +| Delay of Radio Link 2 compared with Radio Link 1 | | 160ms | 20 ms | 20 ms | | +| Delay of Radio Link 3 compared with Radio Link 1 | | 1240ms | 40.67 ms
(1 TTI + 1 slot) | 80.67 ms
(1 TTI + 1 slot) | | + +**Table 11.4: Test requirements for MTCH detection** + +| Test Number | S-CCPCH_Ec/Ior (dB) | RLC SDU ER | +|-------------|---------------------|------------| +| 1 | -4.9 | 0.1 | +| 2 | -5.6 | 0.1 | +| 3 | -8.5 | 0.1 | + +**Table 11.4a: Test requirements for MTCH detection for UE supporting the enhanced performance requirements type1** + +| Test Number | S-CCPCH_Ec/Ior (dB) | RLC SDU ER | +|-------------|---------------------|------------| +| 1 | -7.7 | 0.1 | +| 2 | -8.7 | 0.1 | +| 3 | -11.5 | 0.1 | + +## 11.2.2 Minimum requirement for MBSFN + +Requirement in this subclause is applicable to UEs that are capable of receiving MBSFN with at least two receive antenna connectors. + +For the parameters specified in Table 11.3a the average downlink S-CCPCH\_Ec/Ior power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.4a. + +**Table 11.3a: Parameters for MTCH detection** + +| | Parameter | Unit | Test 1 | +|----------------------------|-----------------|--------------------------------------|---------| +| | Phase reference | - | P-CPICH | +| $I_{oc}$ | dBm/3.84 MHz | -60 | | +| $\hat{I}_{or}/I_{oc}$ | dB | 12 | | +| MTCH Data Rate | kbps | 512 | | +| Transmission Time Interval | ms | 40 | | +| Propagation condition | | MBSFN channel model (see Appendix B) | | + +**Table 11.4a: Test requirements for MTCH detection** + +| Test Number | S-CCPCH_Ec/Ior (dB) | RLC SDU ER | +|-------------|---------------------|------------| +| 1 | -5.8 | 0.1 | + +## 11.3 Demodulation of MTCH and cell identification + +MBMS combining is not controlled by a network but instead it is autonomously handled by a terminal. UE has to be able to receive MTCH and identify intra-frequency neighbour cells according to the requirements. The receive characteristic of the MTCH combined with cell identification is determined by RLC SDU error rate (RLC SDU ER). + +### 11.3.1 Minimum requirement + +For the parameters specified in Table 11.5 the average downlink S-CCPCH\_Ec/Ior power ratio shall be below the specified value for the RLC SDU error rate shown in Table 11.6. The cell reselection parameters are given in clause A.9 in Table A.34. The different cells are assumed to be time aligned. + +**Table 11.5: Parameters for MTCH demodulation requirements with cell identification** + +| Parameter | Unit | Test 1 | | | +|------------------------------|--------------|-----------|---------|-----------| +| | | Stage 1 | Stage 2 | Stage 2 | +| Time in each stage | S | 2 | 0.8 | 3 | +| Phase reference | - | P-CPICH | | | +| $I_{oc}$ | dBm/3.84 MHz | -70 | -73 | -70 | +| Cell1 $\hat{I}_{or1}/I_{oc}$ | dB | -3 | 0 | -3 | +| Cell2 $\hat{I}_{or2}/I_{oc}$ | dB | -3 | 0 | -infinity | +| Cell3 $\hat{I}_{or3}/I_{oc}$ | dB | -infinity | 0 | -3 | +| Propagation condition | | Case1 | | | +| MTCH Data Rate | Kbps | 128 | | | +| Number of Radio Links | | 2 | 3 | 2 | + +**Table 11.6: Requirements for MTCH detection** + +| Test Number | S-CCPCH_Ec/Ior
(dB) | RLC SDU ER | +|-------------|------------------------|------------| +| 1 | -5.6 | 0.05 | + +## Annex A (normative): Measurement channels + +### A.1 General + +The measurement channels in this annex are defined to derive the requirements in clauses 6, 7 and 8. The measurement channels represent example configuration of radio access bearers for different data rates. + +The measurement channel for 12.2 kbps shall be supported by any UE both in up- and downlink. Support for other measurement channels is depending on the UE Radio Access capabilities. + +### A.2 UL reference measurement channel + +#### A.2.1 UL reference measurement channel (12.2 kbps) + +The parameters for the 12.2 kbps UL reference measurement channel are specified in Table A.1 and Table A.2. The channel coding for information is shown in figure A.1. + +**Table A.1: UL reference measurement channel physical parameters (12.2 kbps)** + +| Parameter | Unit | Level | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Information bit rate | kbps | 12.2 | +| DPDCH | kbps | 60 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #i | - | 0 | +| DPCCH/DPDCH power ratio | dB | -5.46 | +| TFCI | - | On | +| Repetition | % | 23 | +| Note: | Slot Format #2 is used for closed loop tests in subclause 8.6.2.
Slot Format #2 and #5 are used for site selection diversity transmission tests in subclause 8.6.3 | | + +**Table A.2: UL reference measurement channel, transport channel parameters (12.2 kbps)** + +| Parameters | DTCH | DCCH | +|----------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 100 | +| Transport Block Set Size | 244 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +![Figure A.1: Channel coding of UL reference measurement channel (12.2 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 244 information bits, adds CRC16 and Tail8, then applies Conv. Coding R=1/3 to produce 804 bits. After 1st interleaving, it is segmented into two 402-bit blocks. Rate matching produces four SMU blocks (SMU#1 490, SMU#2 490, SMU#1 490, SMU#2 490). 2nd interleaving produces four 600-bit blocks. DCCH starts with 100 information bits, adds CRC12 and Tail8, then applies Conv. Coding R=1/3 to produce 360 bits. After 1st interleaving, it is segmented into four 90-bit blocks. Rate matching produces four SMU blocks (SMU#1 110, SMU#2 110, SMU#3 110, SMU#4 110). The 600-bit blocks from DTCH and the 110-bit blocks from DCCH are combined into 60kpbs DPDCH and 15kpbs DPCCH. The final output is shown across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3).](9e23e88f57c8d963f343c29619ebdbf2_img.jpg) + +Figure A.1: Channel coding of UL reference measurement channel (12.2 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 244 information bits, adds CRC16 and Tail8, then applies Conv. Coding R=1/3 to produce 804 bits. After 1st interleaving, it is segmented into two 402-bit blocks. Rate matching produces four SMU blocks (SMU#1 490, SMU#2 490, SMU#1 490, SMU#2 490). 2nd interleaving produces four 600-bit blocks. DCCH starts with 100 information bits, adds CRC12 and Tail8, then applies Conv. Coding R=1/3 to produce 360 bits. After 1st interleaving, it is segmented into four 90-bit blocks. Rate matching produces four SMU blocks (SMU#1 110, SMU#2 110, SMU#3 110, SMU#4 110). The 600-bit blocks from DTCH and the 110-bit blocks from DCCH are combined into 60kpbs DPDCH and 15kpbs DPCCH. The final output is shown across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). + +Figure A.1 (Informative): Channel coding of UL reference measurement channel (12.2 kbps) + +## A.2.2 UL reference measurement channel (64 kbps) + +The parameters for the 64 kbps UL reference measurement channel are specified in Table A.3 and Table A.4. The channel coding for information is shown in figure A.2. This measurement channel is not currently used in TS 25.101 but can be used for future requirements. + +Table A.3: UL reference measurement channel (64 kbps) + +| Parameter | Unit | Level | +|-------------------------|------|-------| +| Information bit rate | kbps | 64 | +| DPDCH | kbps | 240 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #i | - | 0 | +| DPCCH/DPDCH power ratio | dB | -9.54 | +| TFCI | - | On | +| Repetition | % | 18 | + +Table A.4: UL reference measurement channel, transport channel parameters (64 kbps) + +| Parameter | DTCH | DCCH | +|----------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 1280 | 100 | +| Transport Block Set Size | 1280 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +![Figure A.2: Channel coding of UL reference measurement channel (64 kbps). The diagram shows the processing flow for two transport channels, DTCH and DCCH. DTCH starts with 1280 bits of information data, adds a 16-bit CRC, and then applies Turbo Coding with a rate of 1/3, resulting in 3888 bits. This is followed by 1st interleaving (3900 bits) and radio frame segmentation into two 1950-bit blocks. Rate matching produces four segments (SMU#1 2294, SMU#2 2294, SMU#1 2294, SMU#2 2294). 2nd interleaving results in four 2400-bit blocks. DCCH starts with 100 bits of information data, adds a 12-bit CRC and 8 tail bits, and applies Convolutional Coding with a rate of 1/3, resulting in 360 bits. This is followed by 1st interleaving (360 bits) and rate matching into four 90-bit segments (SMU#1 106, SMU#2 106, SMU#3 106, SMU#4 106). Both channels are then mapped to 240 kbps DPDCH and 15 kbps DPCCH across four radio frames (FN=4N to FN=4N+3).](6de875eb7a49c3352b45075b92e5ea9b_img.jpg) + +Figure A.2: Channel coding of UL reference measurement channel (64 kbps). The diagram shows the processing flow for two transport channels, DTCH and DCCH. DTCH starts with 1280 bits of information data, adds a 16-bit CRC, and then applies Turbo Coding with a rate of 1/3, resulting in 3888 bits. This is followed by 1st interleaving (3900 bits) and radio frame segmentation into two 1950-bit blocks. Rate matching produces four segments (SMU#1 2294, SMU#2 2294, SMU#1 2294, SMU#2 2294). 2nd interleaving results in four 2400-bit blocks. DCCH starts with 100 bits of information data, adds a 12-bit CRC and 8 tail bits, and applies Convolutional Coding with a rate of 1/3, resulting in 360 bits. This is followed by 1st interleaving (360 bits) and rate matching into four 90-bit segments (SMU#1 106, SMU#2 106, SMU#3 106, SMU#4 106). Both channels are then mapped to 240 kbps DPDCH and 15 kbps DPCCH across four radio frames (FN=4N to FN=4N+3). + +Figure A.2 (Informative): Channel coding of UL reference measurement channel (64 kbps) + +### A.2.3 UL reference measurement channel (144 kbps) + +The parameters for the 144 kbps UL reference measurement channel are specified in Table A.5 and Table A.6. The channel coding for information is shown in Figure A.3. This measurement channel is not currently used in the present document but can be used for future requirements. + +Table A.5: UL reference measurement channel (144 kbps) + +| Parameter | Unit | Level | +|-------------------------|------|--------| +| Information bit rate | kbps | 144 | +| DPDCH | kbps | 480 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #i | - | 0 | +| DPCCH/DPDCH power ratio | dB | -11.48 | +| TFCI | - | On | +| Repetition | % | 8 | + +Table A.6: UL reference measurement channel, transport channel parameters (144kbps) + +| Parameters | DTCH | DCCH | +|----------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 2880 | 100 | +| Transport Block Set Size | 2880 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +![Figure A.3: Channel coding of UL reference measurement channel (144 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 2880 information bits, adds a 16-bit CRC, and then applies Turbo Coding with a rate of 1/3 to produce 8688 bits. These are then interleaved and segmented into four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3) for 480 kbps DPDCH and 15 kbps DPCCH. DCCH starts with 100 information bits, adds a 12-bit CRC and 8 tail bits, and then applies Convolutional Coding with a rate of 1/3 to produce 360 bits. These are then rate matched and interleaved into the same four radio frames.](a44678044720601f152e409a473467ce_img.jpg) + +Figure A.3: Channel coding of UL reference measurement channel (144 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 2880 information bits, adds a 16-bit CRC, and then applies Turbo Coding with a rate of 1/3 to produce 8688 bits. These are then interleaved and segmented into four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3) for 480 kbps DPDCH and 15 kbps DPCCH. DCCH starts with 100 information bits, adds a 12-bit CRC and 8 tail bits, and then applies Convolutional Coding with a rate of 1/3 to produce 360 bits. These are then rate matched and interleaved into the same four radio frames. + +Figure A.3 (Informative): Channel coding of UL reference measurement channel (144 kbps) + +## A.2.4 UL reference measurement channel (384 kbps) + +The parameters for the 384 kbps UL reference measurement channel are specified in Table A.7 and Table A.8. The channel coding for information is shown in Figure A.4. This measurement channel is not currently used in TS 25.101 but can be used for future requirements. + +Table A.7: UL reference measurement channel (384 kbps) + +| Parameter | Unit | Level | +|-------------------------|------|--------| +| Information bit rate | kbps | 384 | +| DPDCH | kbps | 960 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #l | - | 0 | +| DPCCH/DPDCH power ratio | dB | -11.48 | +| TFCI | - | On | +| Puncturing | % | 18 | + +Table A.8: UL reference measurement channel, transport channel parameters (384 kbps) + +| Parameter | DTCH | DCCH | +|----------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 3840 | 100 | +| Transport Block Set Size | 3840 | 100 | +| Transmission Time Interval | 10 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +![Diagram showing channel coding for DTCH and DCCH. DTCH: Information data (3840) -> CRC16 (3840) -> Turbo Coding R=1/3 (11568) -> 1st interleaving (11580) -> Radio Frame Segmentation (11580) -> Rate matching (9525) -> 2nd interleaving (9600) -> 960kbps DPDCH / 15kbps DPCCH. DCCH: Information data (100) -> CRC12 (100) -> Tail bit attachment (112) -> Conv. Coding R=1/3 (360) -> 1st interleaving (360) -> Rate matching (90) -> SMU#1-4 (75) -> 2nd interleaving (9600) -> 960kbps DPDCH / 15kbps DPCCH. Arrows show mapping to radio frames FN=4N to FN=4N+3.](45b71f54324c8fd8c2830610b367dced_img.jpg) + +Diagram showing channel coding for DTCH and DCCH. DTCH: Information data (3840) -> CRC16 (3840) -> Turbo Coding R=1/3 (11568) -> 1st interleaving (11580) -> Radio Frame Segmentation (11580) -> Rate matching (9525) -> 2nd interleaving (9600) -> 960kbps DPDCH / 15kbps DPCCH. DCCH: Information data (100) -> CRC12 (100) -> Tail bit attachment (112) -> Conv. Coding R=1/3 (360) -> 1st interleaving (360) -> Rate matching (90) -> SMU#1-4 (75) -> 2nd interleaving (9600) -> 960kbps DPDCH / 15kbps DPCCH. Arrows show mapping to radio frames FN=4N to FN=4N+3. + +Figure A.4 (Informative): Channel coding of UL reference measurement channel (384 kbps) + +### A.2.5 UL reference measurement channel (768 kbps) + +The parameters for the UL measurement channel for 768 kbps are specified in Table A.9 and Table A.10. + +Table A.9: UL reference measurement channel, physical parameters (768 kbps) + +| Parameter | Unit | Level | +|-------------------------|------|--------| +| Information bit rate | kbps | 2*384 | +| DPDCH 1 | kbps | 960 | +| DPDCH 2 | kbps | 960 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #i | - | 0 | +| DPCCH/DPDCH power ratio | dB | -11.48 | +| TFCI | - | On | +| Puncturing | % | 18 | + +Table A.10: UL reference measurement channel, transport channel parameters (768 kbps) + +| Parameter | DTCH | DCCH | +|----------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 3840 | 100 | +| Transport Block Set Size | 7680 | 100 | +| Transmission Time Interval | 10 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +## A.2.5A UL reference measurement channel (768 kbps) + +The parameters for the UL measurement channel for 768 kbps are specified in Table A.9A and Table A.10A. + +**Table A.9A: UL reference measurement channel, physical parameters (768 kbps)** + +| Parameter | Unit | Level | +|-------------------------|------|--------| +| Information bit rate | kbps | 2*384 | +| DPDCH 1 | kbps | 960 | +| DPDCH 2 | kbps | 960 | +| DPCCH | kbps | 15 | +| DPCCH Slot Format #i | - | 0 | +| S-DPCCH | kbps | 15 | +| S-DPCCH Slot Format #i | - | 1 | +| DPCCH/DPDCH power ratio | dB | -11.48 | +| TFCI | - | On | +| Puncturing | % | 18 | + +**Table A.10A: UL reference measurement channel, transport channel parameters (768 kbps)** + +| Parameter | DTCH | DCCH | +|----------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 3840 | 100 | +| Transport Block Set Size | 7680 | 100 | +| Transmission Time Interval | 10 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +## A.2.6 UL E-DCH reference measurement channel for DC-HSUPA using BPSK modulation + +The parameters for the UL measurement channel for UE transmitter characteristics for DC-HSUPA are specified in Table A.10AA and Figure A.4AA. The power imbalance in Table A.10AA refers to the ratio of the DPCCH power of the primary uplink frequency to the DPCCH power of the secondary uplink frequency, expressed in dB. + +**Table A.10AA: Settings for DC-HSUPA reference measurement channel using BPSK modulation** + +| Parameter | Unit | Value | +|---------------------------------------------|-----------|-------| +| Modulation | | BPSK | +| Maximum. Inf. Bit Rate | kbps | 60 | +| TTI | ms | 2 | +| Number of HARQ Processes | Processes | 8 | +| Information Bit Payload (N INF ) | Bits | 120 | + +| | | | +|--------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------| +| Binary Channel Bits per TTI ( $N_{\text{BIN}}$ )
(3840 / SF x TTI sum for all channels) | Bits | 480 | +| Coding Rate ( $N_{\text{INF}}/N_{\text{BIN}}$ ) | | 0.25 | +| Physical Channel Codes | SF for each physical channel | {16} | +| E-DPDCH/DPCCH power ratio | dB | 4.08 | +| E-DPCCH/DPCCH power ratio | dB | -9.54 | +| HS-DPCCH/DPCCH power ratio | dB | -9.54 | +| Power imbalance | dB | 0 | +| Note: | HS-DPCCH is applicable only for the primary uplink frequency. | | + +![](9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg) + +| | | | +|-------------------------------|--------------------------------------|----| +| Information Bit Payload | $N_{\text{INF}} = 120$ | | +| CRC Addition | $N_{\text{INF}} = 120$ | 24 | +| Code Block Segmentation | $120+24 = 144$ | | +| Turbo Encoding ( $R=1/3$ ) | $3 \times (N_{\text{INF}}+24) = 432$ | 12 | +| RV Selection | 480 | | +| Physical Channel Segmentation | 480 | | + +**Figure A.4AA: E-DPDCH coding rate for DC-HSUPA reference measurement channel using BPSK modulation** + +## A.2.7 UL E-DCH reference measurement channel for DC-HSUPA using 16QAM modulation + +The parameters for the UL measurement channel for UE transmitter characteristics for DC-HSUPA using 16QAM modulation are specified in Table A.10AB and Figure A.4AB. The power imbalance in Table A.11 refers to the ratio of the DPCCH power of the primary uplink frequency to the DPCCH power of the secondary uplink frequency, expressed in dB. + +**Table A.10AB: Settings for DC-HSUPA reference measurement channel using 16QAM modulation** + +| Parameter | Unit | Value | +|-------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------| +| Modulation | | 16QAM | +| Maximum. Inf. Bit Rate | Kbps | 4227.0 | +| TTI | ms | 2 | +| Number of HARQ Processes | Processes | 8 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 8454 | +| Binary Channel Bits per TTI ( $N_{BIN}$ )
(3840 / SF x TTI sum for all channels) | Bits | 23040 | +| Coding Rate ( $N_{INF}/ N_{BIN}$ ) | | 0.367 | +| Physical Channel Codes | SF for each physical channel | {2,2,4,4} | +| E-DPDCH/DPCCH power ratio, SF4 codes | dB | 16.03 | +| E-DPDCH/DPCCH power ratio, SF2 codes | dB | 19.02 | +| E-DPCCH/DPCCH power ratio | dB | 8.07 | +| HS-DPCCH/DPCCH power ratio | dB | 2.05 | +| Power imbalance | dB | 0 | +| Note: | HS-DPCCH is applicable only for the primary uplink frequency. | | + +![](3b7ac0916ffd00e982c6814d71ffe242_img.jpg) + +| | | | +|-------------------------------|-----------------------|----------------------| +| Information Bit Payload | $N_{INF} = 8454$ | | +| CRC Addition | $N_{INF} = 8454$ | 24 | +| Code Block Segmentation | $(8454+24)/2 = 4239$ | $(8454+24)/2 = 4239$ | +| Turbo Encoding ( $R=1/3$ ) | $3 \times 4239=12717$ | 12 | +| RV Selection | 23040 | | +| Physical Channel Segmentation | 7680 | 7680 | +| | 3840 | 3840 | + +**Figure A.4AB: E-DPDCH coding rate for DC-HSUPA reference measurement channel using 16QAM modulation** + +## A.2.8 Combinations of UL E-DCH reference measurement channel for DC-HSUPA tests + +The combinations of BPSK and 16QAM reference measurement channels in Table A.10AC shall be used for verifying the UE maximum output power for DC-HSUPA, additional Spectrum emission mask for DC-HSUPA, and additional ACLR requirement for DC-HSUPA. The entry BPSK in Table A.10AC refers to the UL E-DCH reference measurement channel for DC-HSUPA using BPSK modulation, specified in subclause A.2.6, and the entry 16QAM refers to the UL E-DCH reference measurement channel for DC-HSUPA using 16QAM modulation, specified in subclause A.2.7. The power imbalance in subclause A.2.6 and A.2.7 have been adjusted as shown in Table A.10AC. + +**Table A.10AC: Settings for DC-HSUPA reference measurement channels for UE maximum output power, spectrum emission mask and ACLR requirements** + +| Config # | Primary carrier | Secondary carrier | Power imbalance [dB] | Allowed MPR [dB] | +|----------|-----------------|-------------------|----------------------|------------------| +| 1 | BPSK | BPSK | -10 | [0.5] | +| 2 | BPSK | BPSK | 8 | [1.0] | +| 3 | BPSK | BPSK | 0 | [1.5] | +| 4 | 16QAM | 16QAM | 0 | [TBD] | + +## A.3 DL reference measurement channel + +### A.3.0 DL reference measurement channel (0 kbps) + +The parameters for the 0 kbps DL reference measurement channel are specified in Table A.10A and Table A.10B. The channel coding is shown for information in figure A.4A. + +**Table A.10A: DL reference measurement channel physical parameters (0 kbps)** + +| Parameter | Unit | Level | +|--------------------------------|------|-------| +| Information bit rate | kbps | 0 | +| DPCH | kspc | 30 | +| Slot Format #l | - | 11 | +| TFCI | - | On | +| Power offsets PO1, PO2 and PO3 | dB | 0 | +| Puncturing | % | 13.9 | + +**Table A.10B: DL reference measurement channel, transport channel parameters (0 kbps)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 0 | 100 | +| Transport Block Set Size | 0 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | fixed | + +![Figure A.4A: Channel coding of DL reference measurement channel (0 kbps). The diagram shows the processing flow for DTCH and DCCH channels. For DTCH, information data (0 bits) is processed through CRC detection (0 bits), tail bit discard (16 bits), Viterbi decoding R=1/3 (72 bits), rate matching (61 bits), and 1st interleaving (61 bits). The data is then segmented into radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3) and further processed through 2nd interleaving and slot segmentation to produce 30ksps DPCH (including TFCI bits). For DCCH, information data (100 bits) is processed through CRC detection (100 bits), tail bit discard (112 bits), Viterbi decoding R=1/3 (360 bits), rate matching (308 bits), and 1st interleaving (308 bits). The data is then segmented into radio frames and further processed through 2nd interleaving and slot segmentation to produce 30ksps DPCH (including TFCI bits).](7bcf05f70463355ac4550ccb2f963bbd_img.jpg) + +Figure A.4A: Channel coding of DL reference measurement channel (0 kbps). The diagram shows the processing flow for DTCH and DCCH channels. For DTCH, information data (0 bits) is processed through CRC detection (0 bits), tail bit discard (16 bits), Viterbi decoding R=1/3 (72 bits), rate matching (61 bits), and 1st interleaving (61 bits). The data is then segmented into radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3) and further processed through 2nd interleaving and slot segmentation to produce 30ksps DPCH (including TFCI bits). For DCCH, information data (100 bits) is processed through CRC detection (100 bits), tail bit discard (112 bits), Viterbi decoding R=1/3 (360 bits), rate matching (308 bits), and 1st interleaving (308 bits). The data is then segmented into radio frames and further processed through 2nd interleaving and slot segmentation to produce 30ksps DPCH (including TFCI bits). + +Figure A.4A (Informative): Channel coding of DL reference measurement channel (0 kbps) + +### A.3.1 DL reference measurement channel (12.2 kbps) + +The parameters for the 12.2 Kbps DL reference measurement channel are specified in Table A.11 and Table A.12. The channel coding is shown for information in figure A.5. + +Table A.11: DL reference measurement channel physical parameters (12.2 kbps) + +| Parameter | Unit | Level | +|--------------------------------|------|-------| +| Information bit rate | kbps | 12.2 | +| DPCH | ksps | 30 | +| Slot Format #i | - | 11 | +| TFCI | - | On | +| Power offsets PO1, PO2 and PO3 | dB | 0 | +| Puncturing | % | 14.7 | + +Table A.12: DL reference measurement channel, transport channel parameters (12.2 kbps) + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 100 | +| Transport Block Set Size | 244 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | fixed | + +![Figure A.5: Channel coding of DL reference measurement channel (12.2 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 244 information bits, adds a 16-bit CRC, discards 8 tail bits, and then applies Viterbi decoding (R=1/3) to produce 804 bits. This is followed by rate matching to 686 bits and 1st interleaving. The data is then segmented into two transport blocks of 343 bits each. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 8 tail bits, and applies Viterbi decoding (R=1/3) to produce 360 bits. This is followed by rate matching to 308 bits and 1st interleaving. The data is then segmented into four transport blocks of 77 bits each. Both channels undergo 2nd interleaving and slot segmentation. The final output is a 30ksps DPCH (including TFCI bits) stream, which is further segmented into four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). Each radio frame contains 420 slots, with each slot containing 28 chips. The DPCH stream is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across the four radio frames.](cf6ca8f1a86c81dccf05cb590811fa7e_img.jpg) + +Figure A.5: Channel coding of DL reference measurement channel (12.2 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 244 information bits, adds a 16-bit CRC, discards 8 tail bits, and then applies Viterbi decoding (R=1/3) to produce 804 bits. This is followed by rate matching to 686 bits and 1st interleaving. The data is then segmented into two transport blocks of 343 bits each. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 8 tail bits, and applies Viterbi decoding (R=1/3) to produce 360 bits. This is followed by rate matching to 308 bits and 1st interleaving. The data is then segmented into four transport blocks of 77 bits each. Both channels undergo 2nd interleaving and slot segmentation. The final output is a 30ksps DPCH (including TFCI bits) stream, which is further segmented into four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). Each radio frame contains 420 slots, with each slot containing 28 chips. The DPCH stream is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across the four radio frames. + +Figure A.5 (Informative): Channel coding of DL reference measurement channel (12.2 kbps) + +### A.3.2 DL reference measurement channel (64 kbps) + +The parameters for the DL reference measurement channel for 64 kbps are specified in Table A.13 and Table A.14. The channel coding is shown for information in Figure A.6. + +Table A.13: DL reference measurement channel physical parameters (64 kbps) + +| Parameter | Unit | Level | +|--------------------------------|------|-------| +| Information bit rate | kbps | 64 | +| DPCH | ksps | 120 | +| Slot Format #i | - | 13 | +| TFCI | - | On | +| Power offsets PO1, PO2 and PO3 | dB | 0 | +| Repetition | % | 2.9 | + +Table A.14: DL reference measurement channel, transport channel parameters (64 kbps) + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 1280 | 100 | +| Transport Block Set Size | 1280 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | fixed | + +![Figure A.6: Channel coding of DL reference measurement channel (64 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 1280 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) with 12 tail bits, resulting in 3888 bits. After rate matching to 4014 bits and 1st interleaving, it is segmented into four radio frames (FN=4N to 4N+3), each containing two transport blocks of 2007 bits. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 8 tail bits, resulting in 112 bits. After Viterbi decoding (R=1/3) to 360 bits, rate matching to 372 bits, and 1st interleaving, it is segmented into four radio frames, each containing four transport blocks of 93 bits. Both channels undergo 2nd interleaving and slot segmentation into 140-bit slots. The final output is a 120ksps DPCH stream including TFCI bits, with slots 0, 1, and 14 identified in each frame.](c4ce20d443c5793503265b1f68fe4536_img.jpg) + +Figure A.6: Channel coding of DL reference measurement channel (64 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 1280 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) with 12 tail bits, resulting in 3888 bits. After rate matching to 4014 bits and 1st interleaving, it is segmented into four radio frames (FN=4N to 4N+3), each containing two transport blocks of 2007 bits. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 8 tail bits, resulting in 112 bits. After Viterbi decoding (R=1/3) to 360 bits, rate matching to 372 bits, and 1st interleaving, it is segmented into four radio frames, each containing four transport blocks of 93 bits. Both channels undergo 2nd interleaving and slot segmentation into 140-bit slots. The final output is a 120ksps DPCH stream including TFCI bits, with slots 0, 1, and 14 identified in each frame. + +Figure A.6 (Informative): Channel coding of DL reference measurement channel (64 kbps) + +### A.3.3 DL reference measurement channel (144 kbps) + +The parameters for the DL measurement channel for 144 kbps are specified in Table A.15 and Table A.16. The channel coding is shown for information in Figure A.7. + +Table A.15: DL reference measurement channel physical parameters (144 kbps) + +| Parameter | Unit | Level | +|--------------------------------|------|-------| +| Information bit rate | kbps | 144 | +| DPCH | ksps | 240 | +| Slot Format #i | - | 14 | +| TFCI | - | On | +| Power offsets PO1, PO2 and PO3 | dB | 0 | +| Puncturing | % | 2.7 | + +Table A.16: DL reference measurement channel, transport channel parameters (144 kbps) + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 2880 | 100 | +| Transport Block Set Size | 2880 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | fixed | + +![Figure A.7: Channel coding of DL reference measurement channel (144 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 2880 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) with 12 tail bits, rate matching to 8464 bits, and 1st interleaving. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 12 tail bits, applies Viterbi decoding (R=1/3), rate matching to 352 bits, and 1st interleaving. Both channels are then segmented into radio frames (FN=4N to 4N+3) and further interleaved. Slot segmentation and 240ksps DPCH (including TFCI bits) are also shown.](c4af7b16ba093a462fb5f67f369ce743_img.jpg) + +Figure A.7: Channel coding of DL reference measurement channel (144 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 2880 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) with 12 tail bits, rate matching to 8464 bits, and 1st interleaving. DCCH starts with 100 information bits, adds a 12-bit CRC, discards 12 tail bits, applies Viterbi decoding (R=1/3), rate matching to 352 bits, and 1st interleaving. Both channels are then segmented into radio frames (FN=4N to 4N+3) and further interleaved. Slot segmentation and 240ksps DPCH (including TFCI bits) are also shown. + +Figure A.7 (Informative): Channel coding of DL reference measurement channel (144 kbps) + +### A.3.4 DL reference measurement channel (384 kbps) + +The parameters for the DL measurement channel for 384 kbps are specified in Table A.17 and Table A.18. The channel coding is shown for information in Figure A.8 + +Table A.17: DL reference measurement channel, physical parameters (384 kbps) + +| Parameter | Unit | Level | +|--------------------------------|------|-------| +| Information bit rate | kbps | 384 | +| DPCH | ksps | 480 | +| Slot Format # i | - | 15 | +| TFCI | | On | +| Power offsets PO1, PO2 and PO3 | dB | 0 | +| Puncturing | % | 22 | + +Table A.18: DL reference measurement channel, transport channel parameters (384 kbps) + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 3840 | 100 | +| Transport Block Set Size | 3840 | 100 | +| Transmission Time Interval | 10 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | Fixed | + +![Figure A.8: Channel coding of DL reference measurement channel (384 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 3840 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) resulting in 11568 bits, then rate matching to 9049 bits. DCCH starts with 100 information bits, adds a 12-bit CRC, discards tail bits, applies Viterbi decoding (R=1/3) resulting in 360 bits, then rate matching to 284 bits. Both channels undergo 1st and 2nd interleaving. The final data is segmented into radio frames (FN=4N to FN=4N+3) and slot segments. Each slot segment contains 608 bits of data and 14 bits of TFCI (Transport Format Combination Indicator).](3c586c53df312a3694ee1ad0e7fd0960_img.jpg) + +Figure A.8: Channel coding of DL reference measurement channel (384 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 3840 information bits, adds a 16-bit CRC, applies Turbo coding (R=1/3) resulting in 11568 bits, then rate matching to 9049 bits. DCCH starts with 100 information bits, adds a 12-bit CRC, discards tail bits, applies Viterbi decoding (R=1/3) resulting in 360 bits, then rate matching to 284 bits. Both channels undergo 1st and 2nd interleaving. The final data is segmented into radio frames (FN=4N to FN=4N+3) and slot segments. Each slot segment contains 608 bits of data and 14 bits of TFCI (Transport Format Combination Indicator). + +Figure A.8 (Informative): Channel coding of DL reference measurement channel (384 kbps) + +### A.3.5 DL reference measurement channel 2 (64 kbps) + +The parameters for the DL reference measurement channel for 64 kbps are specified in Table A.18A and Table A.18B. The channel coding is shown for information in Figure A.8A. + +Table A.18A: DL reference measurement channel physical parameters (64 kbps) + +| Parameter | Unit | Level | +|-----------------------------|------|-------| +| Information bit rate (DTCH) | kbps | 64 | +| Information bit rate (DCCH) | kbps | 3.4 | +| DPCH | ksp | 120 | +| Slot Format #i | - | 13 | +| TFCI | - | On | +| Puncturing (DTCH) | % | 8.6 | +| Repetition (DCCH) | % | 27.9 | + +Table A.18B: DL reference measurement channel, transport channel parameters (64 kbps) + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 336 | 148 | +| Transport Block Set Size | 1344 | 148 | +| Transport blocks per TTI | 4 | 1 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Turbo Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 143 | 200 | +| Size of CRC | 16 | 16 | +| Position of TrCH in radio frame | fixed | fixed | + +![Figure A.8A: Channel coding of DL reference measurement channel 2 (64 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 336 information bits, followed by CRC16, Turbo code R=1/3 (1056 bits), termination bits, rate matching (3870 bits), and 1st interleaving. DCCH starts with 148 information bits, followed by CRC16, tail bit discard, Viterbi decoding R=1/3 (516 bits), rate matching (660 bits), and 1st interleaving. Both channels are then segmented into radio frames (FN=4N, 4N+1, 4N+2, 4N+3) and further processed through 2nd interleaving and slot segmentation to produce 120ksps DPCH (including TFCI bits).](1322a1154e11aadf811c48774d91ab36_img.jpg) + +Figure A.8A: Channel coding of DL reference measurement channel 2 (64 kbps). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 336 information bits, followed by CRC16, Turbo code R=1/3 (1056 bits), termination bits, rate matching (3870 bits), and 1st interleaving. DCCH starts with 148 information bits, followed by CRC16, tail bit discard, Viterbi decoding R=1/3 (516 bits), rate matching (660 bits), and 1st interleaving. Both channels are then segmented into radio frames (FN=4N, 4N+1, 4N+2, 4N+3) and further processed through 2nd interleaving and slot segmentation to produce 120ksps DPCH (including TFCI bits). + +Figure A.8A (Informative): Channel coding of DL reference measurement channel 2 (64 kbps) + +### A.3A DL reference measurement channel + +#### A.3A.0 DL reference measurement channel (0 kbps without DCCH) + +The parameters for the 0 kbps DL reference measurement channel without DCCH are specified in Table A.10AA and Table A.10BA. The channel coding is shown for information in figure A.4AA. + +Table A.18C: DL reference measurement channel physical parameters (0 kbps without DCCH) + +| Parameter | Unit | Level | +|---------------------------------------------------|------|-------| +| Information bit rate | Kbps | 0 | +| DPCH | Ksps | 30 | +| Slot Format #1 | - | 18 | +| TFCI | - | Off | +| Power offsets PO1, PO2, PO3 and PO SRB | dB | 0 | +| Repetition | % | 43.1 | + +**Table A.18D: DL reference measurement channel, transport channel parameters (0 kbps without DCCH)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 0 | 0 | +| Transport Block Set Size | 0 | 0 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 0 | +| Size of CRC | 16 | 16 | +| Position of TrCH in radio frame | Pseudo-flexible | Pseudo-flexible | + +![Figure A.8B: Channel coding of DL reference measurement channel (0 kbps without DCCH). The diagram illustrates the processing flow for DTCH and DCCH channels. For DTCH, the process starts with Information data (C), followed by CRC detection (C), Tail bit discard (16), Viterbi decoding R=1/3 (72), Rate matching (103), and 1st interleaving (103). The data is then segmented into two parts: #1 52 and #2 51. These are further processed through Radio Frame Segmentation, 2nd interleaving, and slot segmentation. The final output is a sequence of bits (0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14) mapped to 30ksps DPCH (including TFCI bits) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). The DCCH channel follows a similar process but with a 40 ms TTI.](3deb36ec163d8c531f3498b485945091_img.jpg) + +Figure A.8B: Channel coding of DL reference measurement channel (0 kbps without DCCH). The diagram illustrates the processing flow for DTCH and DCCH channels. For DTCH, the process starts with Information data (C), followed by CRC detection (C), Tail bit discard (16), Viterbi decoding R=1/3 (72), Rate matching (103), and 1st interleaving (103). The data is then segmented into two parts: #1 52 and #2 51. These are further processed through Radio Frame Segmentation, 2nd interleaving, and slot segmentation. The final output is a sequence of bits (0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14) mapped to 30ksps DPCH (including TFCI bits) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). The DCCH channel follows a similar process but with a 40 ms TTI. + +**Figure A.8B (Informative): Channel coding of DL reference measurement channel (0 kbps without DCCH)** + +### A.3A.1 DL reference measurement channel (0 kbps with DCCH) + +The parameters for the 0 kbps DL reference measurement channel with DCCH are specified in Table A.11AA and Table A.11BA. The channel coding is shown for information in figure A.5AA. + +**Table A.18E: DL reference measurement channel physical parameters (0 kbps with DCCH)** + +| Parameter | Unit | Level | +|---------------------------------------------------|------|-------| +| Information bit rate | kbps | 0 | +| DPCH | ksps | 30 | +| Slot Format #1 | - | 18 | +| TFCI | - | Off | +| Power offsets PO1, PO2, PO3 and PO SRB | dB | 0 | +| Repetition | % | 8.3 | + +**Table A.18F: DL reference measurement channel, transport channel parameters (0 kbps with DCCH)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 0 | 148 | +| Transport Block Set Size | 0 | 148 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 16 | +| Position of TrCH in radio frame | Pseudo-flexible | Pseudo-flexible | + +![Figure A.8C: Channel coding of DL reference measurement channel (0 kbps with DCCH). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with information data 'C', followed by CRC16, Tail8, Viterbi decoding R=1/3 (72 bits), Rate matching (78 bits), and 1st interleaving (78 bits). It then undergoes Radio Frame Segmentation into four segments (#1 39, #2 39, #1 39, #2 39), 2nd interleaving (39, 139), and slot segmentation (178 bits). The final output is 30ksps DPCH (including TFCI bits) with a sequence of 0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14. DCCH starts with information data '148', followed by CRC16, Tail8, Viterbi decoding R=1/3 (516 bits), Rate matching (556 bits), and 1st interleaving (556 bits). It then undergoes Radio Frame Segmentation into four segments (#1 139, #2 139, #3 139, #4 139), 2nd interleaving (39, 139), and slot segmentation (178 bits). The final output is 30ksps DPCH (including TFCI bits) with a sequence of 0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14. The diagram also indicates radio frame numbering: FN=4N, FN=4N+1, FN=4N+2, FN=4N+3.](630ea28f4495d1f5db09de6182db62c2_img.jpg) + +Figure A.8C: Channel coding of DL reference measurement channel (0 kbps with DCCH). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with information data 'C', followed by CRC16, Tail8, Viterbi decoding R=1/3 (72 bits), Rate matching (78 bits), and 1st interleaving (78 bits). It then undergoes Radio Frame Segmentation into four segments (#1 39, #2 39, #1 39, #2 39), 2nd interleaving (39, 139), and slot segmentation (178 bits). The final output is 30ksps DPCH (including TFCI bits) with a sequence of 0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14. DCCH starts with information data '148', followed by CRC16, Tail8, Viterbi decoding R=1/3 (516 bits), Rate matching (556 bits), and 1st interleaving (556 bits). It then undergoes Radio Frame Segmentation into four segments (#1 139, #2 139, #3 139, #4 139), 2nd interleaving (39, 139), and slot segmentation (178 bits). The final output is 30ksps DPCH (including TFCI bits) with a sequence of 0, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14, C, 1, ..., 14. The diagram also indicates radio frame numbering: FN=4N, FN=4N+1, FN=4N+2, FN=4N+3. + +**Figure A.8C (Informative): Channel coding of DL reference measurement channel (0 kbps with DCCH)** + +### A.3A.2 DL reference measurement channel (12.2 kbps without DCCH) + +The parameters for the 12.2 kbps DL reference measurement channel without DCCH are specified in Table A.12AA and Table A.12BA. The channel coding is shown for information in figure A.6AA. + +**Table A.18G: DL reference measurement channel physical parameters (12.2 kbps without DCCH)** + +| Parameter | Unit | Level | +|---------------------------------------------------|------|-------| +| Information bit rate | kbps | 12.2 | +| DPCH | ksps | 30 | +| Slot Format #i | - | 18 | +| TFCI | - | Off | +| Power offsets PO1, PO2, PO3 and PO SRB | dB | 0 | +| Repetition | % | 41.8 | + +**Table A.18H: DL reference measurement channel, transport channel parameters (12.2 kbps without DCCH)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 0 | +| Transport Block Set Size | 244 | 0 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 0 | +| Size of CRC | 16 | 16 | +| Position of TrCH in radio frame | Pseudo-flexible | Pseudo-flexible | + +![Figure A.8D: Channel coding of DL reference measurement channel (12.2 kbps without DCCH). The diagram shows the processing flow for DTCH and DCCH channels. For DTCH, the process starts with 244 information bits, followed by CRC16 (244 bits), Tail bit discard (260 bits), Viterbi decoding R=1/3 (804 bits), Rate matching (1140 bits), and 1st interleaving (1140 bits). The data is then segmented into two 570-bit blocks (#1 570, #2 570). These are further processed through 2nd interleaving and slot segmentation into 30ksps DPCH (including TFCI bits). The final output is shown across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). The DCCH channel follows a similar process but with 0 information bits.](c9a112da345a240257303fe6d2fa36fb_img.jpg) + +Figure A.8D: Channel coding of DL reference measurement channel (12.2 kbps without DCCH). The diagram shows the processing flow for DTCH and DCCH channels. For DTCH, the process starts with 244 information bits, followed by CRC16 (244 bits), Tail bit discard (260 bits), Viterbi decoding R=1/3 (804 bits), Rate matching (1140 bits), and 1st interleaving (1140 bits). The data is then segmented into two 570-bit blocks (#1 570, #2 570). These are further processed through 2nd interleaving and slot segmentation into 30ksps DPCH (including TFCI bits). The final output is shown across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). The DCCH channel follows a similar process but with 0 information bits. + +**Figure A.8D (Informative): Channel coding of DL reference measurement channel (12.2 kbps without DCCH)** + +### A.3A.3 DL reference measurement channel (12.2 kbps with DCCH) + +The parameters for the 12.2 Kbps DL reference measurement channel with DCCH are specified in Table A.13AA and Table A.13BA. The channel coding is shown for information in figure A.7AA. + +**Table A.18I: DL reference measurement channel physical parameters (12.2 kbps with DCCH)** + +| Parameter | Unit | Level | +|---------------------------------------------------|------|-------| +| Information bit rate | kbps | 12.2 | +| DPCH | ksp | 30 | +| Slot Format #i | - | 18 | +| TFCI | - | Off | +| Power offsets PO1, PO2, PO3 and PO SRB | dB | 0 | +| Repetition | % | 7.2 | + +**Table A.18J: DL reference measurement channel, transport channel parameters (12.2 kbps with DCCH)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 148 | +| Transport Block Set Size | 244 | 148 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution Coding | Convolution Coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 16 | +| Position of TrCH in radio frame | Pseudo-flexible | Pseudo-flexible | + +![Diagram showing the channel coding process for DTCH and DCCH transport channels. It illustrates the flow from information data through CRC, tail bits, Viterbi decoding, rate matching, and interleaving to the final DPCH slots across four radio frames.](f064a4f199728c7a51a422a98ecec5f5_img.jpg) + +**DTCH** + +Information data: 244 + +CRC detection: 244 (CRC16) + +Tail bit discard: 260 (Tail8) + +Viterbi decoding R=1/3: 804 + +Rate matching: 862 + +1st interleaving: 862 + +Radio Frame Segmentation: #1 431, #2 431 + +2nd interleaving: 431, 139, 431, 139, 431, 139, 431, 139 + +slot segmentation: 570, 570, 570, 570 + +38 38 ... 38 38 38 ... 38 38 38 ... 38 38 38 ... 38 + +0 1 ... 14 0 1 ... 14 0 1 ... 14 0 1 ... 14 + +38kps DPCH (including TPC bits) + +Radio frame FN=4N, Radio frame FN=4N+1, Radio frame FN=4N+2, Radio frame FN=4N+3 + +**DCCH** + +Information data: 148 + +CRC detection: 148 (CRC16) + +Tail bit discard: 164 (Tail8) + +Viterbi decoding R=1/3: 516 + +Rate matching: 556 + +1st interleaving: 556 + +Radio Frame Segmentation: #1 139, #2 139, #3 139, #4 139 + +2nd interleaving: 431, 139, 431, 139, 431, 139, 431, 139 + +slot segmentation: 570, 570, 570, 570 + +38 38 ... 38 38 38 ... 38 38 38 ... 38 + +0 1 ... 14 0 1 ... 14 0 1 ... 14 0 1 ... 14 + +38kps DPCH (including TPC bits) + +Radio frame FN=4N, Radio frame FN=4N+1, Radio frame FN=4N+2, Radio frame FN=4N+3 + +Diagram showing the channel coding process for DTCH and DCCH transport channels. It illustrates the flow from information data through CRC, tail bits, Viterbi decoding, rate matching, and interleaving to the final DPCH slots across four radio frames. + +**Figure A.8E (Informative): Channel coding of DL reference measurement channel (12.2 kbps with DCCH)** + +## A.4 DL reference measurement channel for BTFD performance requirements + +The parameters for DL reference measurement channel for BTFD are specified in Table A.19 and Table A.20. The channel coding for information is shown in figures A.9, A.10, and A.11. + +**Table A.19: DL reference measurement channel physical parameters for BTFD** + +| Parameter | Unit | Rate 1 | Rate 2 | Rate 3 | +|--------------------------------|------|--------|--------|--------| +| Information bit rate | kbps | 12.2 | 7.95 | 1.95 | +| DPCH | ksps | 30 | | | +| Slot Format # i | - | 8 | | | +| TFCI | - | Off | | | +| Power offsets PO1, PO2 and PO3 | dB | 0 | | | +| Repetition | % | 5 | | | + +**Table A.20: DL reference measurement channel, transport channel parameters for BTFD** + +| Parameter | DTCH | | | DCCH | +|---------------------------------|--------------------|--------|--------|--------------------| +| | Rate 1 | Rate 2 | Rate 3 | | +| Transport Channel Number | 1 | | | 2 | +| Transport Block Size | 244 | 159 | 39 | 100 | +| Transport Block Set Size | 244 | 159 | 39 | 100 | +| Transmission Time Interval | 20 ms | | | 40 ms | +| Type of Error Protection | Convolution Coding | | | Convolution Coding | +| Coding Rate | 1/3 | | | 1/3 | +| Rate Matching attribute | 256 | | | 256 | +| Size of CRC | 12 | | | 12 | +| Position of TrCH in radio frame | fixed | | | fixed | + +![Figure A.9: Channel coding of DL reference measurement channel for BTFD (Rate 1).](c52ea16bac02e546d0c5767db5dd4981_img.jpg) + +This diagram illustrates the channel coding process for the DL reference measurement channel for BTFD (Rate 1). It is divided into two main sections: DTCH and DCCH. + +**DTCH (Traffic Channel):** + +- Information data:** 244 bits (yellow bar). +- CRC detection:** 244 bits (purple bar) with CRC12 added. +- Tail bit discard:** 256 bits (purple bar) with Tail8 added. +- Viterbi decoding R=1/3:** 792 bits (purple bar). +- Rate matching:** 830 bits (purple bar). +- 1st interleaving:** 830 bits (purple bar). +- Radio Frame Segmentation:** The data is segmented into two frames: #1 415 and #2 415. +- 2nd interleaving:** Each frame is interleaved into 415 bits and 95 bits. +- slot segmentation:** The data is further segmented into slots of 510 bits. +- 30ksps DPCH:** The final output is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). + +**DCCH (Control Channel):** + +- Information data:** 100 bits (yellow bar). +- CRC detection:** 100 bits (green bar) with CRC12 added. +- Tail bit discard:** 112 bits (green bar) with Tail8 added. +- Viterbi decoding R=1/3:** 360 bits (green bar). +- Rate matching:** 380 bits (green bar). +- 1st interleaving:** 380 bits (green bar). +- Radio Frame Segmentation:** The data is segmented into four frames: #1 95, #2 95, #3 95, and #4 95. +- 2nd interleaving:** Each frame is interleaved into 415 bits and 95 bits. +- slot segmentation:** The data is further segmented into slots of 510 bits. +- 30ksps DPCH:** The final output is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). + +Figure A.9: Channel coding of DL reference measurement channel for BTFD (Rate 1). + +Figure A.9 (Informative): Channel coding of DL reference measurement channel for BTFD (Rate 1) + +![Figure A.10: Channel coding of DL reference measurement channel for BTFD (Rate 2).](2ddba848b8cb2941701e9e123fa7a27d_img.jpg) + +This diagram illustrates the channel coding process for the DL reference measurement channel for BTFD (Rate 2). It is divided into two main sections: DTCH and DCCH. + +**DTCH (Traffic Channel):** + +- Information data:** 159 bits (yellow bar). +- CRC detection:** 159 bits (purple bar) with CRC12 added. +- Tail bit discard:** 171 bits (purple bar) with Tail8 added. +- Viterbi decoding R=1/3:** 537 bits (purple bar). +- Rate matching:** 563 bits (purple bar), with DTX 267 added. +- 1st interleaving:** 563 (+ DTX 267) bits (purple bar). +- Radio Frame Segmentation:** The data is segmented into two frames: #1 282 (+133) and #2 281 (+134). +- 2nd interleaving:** Each frame is interleaved into 282 (+133) bits and 95 bits. +- slot segmentation:** The data is further segmented into slots of 377 (+133) and 376 (+134) bits. +- 30ksps DPCH:** The final output is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). + +**DCCH (Control Channel):** + +- Information data:** 100 bits (yellow bar). +- CRC detection:** 100 bits (green bar) with CRC12 added. +- Tail bit discard:** 112 bits (green bar) with Tail8 added. +- Viterbi decoding R=1/3:** 360 bits (green bar). +- Rate matching:** 380 bits (green bar). +- 1st interleaving:** 380 bits (green bar). +- Radio Frame Segmentation:** The data is segmented into four frames: #1 95, #2 95, #3 95, and #4 95. +- 2nd interleaving:** Each frame is interleaved into 282 (+133) bits and 95 bits. +- slot segmentation:** The data is further segmented into slots of 377 (+133) and 376 (+134) bits. +- 30ksps DPCH:** The final output is shown as a sequence of bits (0, 1, ..., 14, 0, 1, ..., 14, 0, 1, ..., 14) across four radio frames (FN=4N, FN=4N+1, FN=4N+2, FN=4N+3). + +Figure A.10: Channel coding of DL reference measurement channel for BTFD (Rate 2). + +Figure A.10 (Informative): Channel coding of DL reference measurement channel for BTFD (Rate 2) + +![Figure A.11: Channel coding of DL reference measurement channel for BTFD (Rate 3). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 39 bits of information data, followed by CRC12, Tail8, and Viterbi decoding (R=1/3) resulting in 177 bits. Rate matching produces 186 bits, which are then interleaved with DTX 644 to produce 186 (+ DTX 644) bits. These are segmented into two radio frames, #1 93 (+322) and #2 93 (+322). DCCH starts with 100 bits of information data, followed by CRC12, Tail8, and Viterbi decoding (R=1/3) resulting in 360 bits. Rate matching produces 380 bits, which are then interleaved to produce 380 bits. These are segmented into four radio frames, #1 95, #2 95, #3 95, and #4 95. The segmented data is then 2nd interleaved and slot segmented into 30ksps DPCCH (NOT including TFCI bits, 2symbol pilot) across four radio frames: FN=4N, FN=4N+1, FN=4N+2, and FN=4N+3.](0b13c8043bf78842cd0980770eb9d60b_img.jpg) + +Figure A.11: Channel coding of DL reference measurement channel for BTFD (Rate 3). The diagram shows the processing flow for DTCH and DCCH channels. DTCH starts with 39 bits of information data, followed by CRC12, Tail8, and Viterbi decoding (R=1/3) resulting in 177 bits. Rate matching produces 186 bits, which are then interleaved with DTX 644 to produce 186 (+ DTX 644) bits. These are segmented into two radio frames, #1 93 (+322) and #2 93 (+322). DCCH starts with 100 bits of information data, followed by CRC12, Tail8, and Viterbi decoding (R=1/3) resulting in 360 bits. Rate matching produces 380 bits, which are then interleaved to produce 380 bits. These are segmented into four radio frames, #1 95, #2 95, #3 95, and #4 95. The segmented data is then 2nd interleaved and slot segmented into 30ksps DPCCH (NOT including TFCI bits, 2symbol pilot) across four radio frames: FN=4N, FN=4N+1, FN=4N+2, and FN=4N+3. + +Figure A.11 (Informative): Channel coding of DL reference measurement channel for BTFD (Rate 3) + +## A.4A Reference parameters for discontinuous UL DPCCH transmission + +The parameters for the UE UL power control operation with discontinuous UL DPCCH transmission test is specified in Table A.20A. Same parameter values are used for 2ms and 10ms E-DCH TTI. + +Table A.20A: Parameters for the discontinuous UL DPCCH transmission + +| Parameter | Unit | Level | +|----------------------------------------|--------------|-------| +| Enabling_Delay | Radio frames | 0 | +| UE_DTX_cycle_1 | Subframes | 10 | +| UE_DTX_cycle_2 | Subframes | 10 | +| UE_DTX_DRX_offset | Subframes | 0 | +| Inactivity_threshold_for_UE_DTX_cycle2 | E-DCH TTI | 1 | +| UE_DPCCH_burst_1 | Subframes | 1 | +| UE_DPCCH_burst_2 | Subframes | 1 | +| UE_DTX_long_preamble_length | Slots | 2 | +| CQI Feedback cycle, k | Milliseconds | 0 | +| CQI_DTX_TIMER | Subframes | 0 | + +Table A.20B: (void) + +Figure A.11A (void) + +## A.5 DL reference compressed mode parameters + +Parameters described in Table A.21 are used in some test specified in TS 25.101 while parameters described in Table A.22 and Table A.22A are used in some tests specified in TS 25.133. + +Parameters in Table A.21 are applicable when compressed mode by spreading factor reduction is used in downlink. + +Table A.21: Compressed mode reference pattern 1 parameters + +| Parameter | Set 1 | Set 2 | Note | +|---------------------------------------------------|---------|---------|-------------------------------------------| +| TGSN (Transmission Gap Starting Slot Number) | 11 | 4 | | +| TGL1 (Transmission Gap Length 1) | 7 | 7 | | +| TGL2 (Transmission Gap Length 2) | - | 7 | Only one gap in use. | +| TGD (Transmission Gap Distance) | 0 | 15 | Only one gap in use. | +| TGPL1 (Transmission Gap Pattern Length) | 4 | 4 | | +| TGPRC (Transmission Gap Pattern Repetition Count) | NA | NA | Defined by higher layers | +| TGCFN (Transmission Gap Connection Frame Number): | NA | 0 | Defined by higher layers | +| UL/DL compressed mode selection | DL & UL | DL & UL | 2 configurations possible
DL & UL / DL | +| UL compressed mode method | SF/2 | SF/2 | | +| DL compressed mode method | SF/2 | SF/2 | | +| Downlink frame type and Slot format | 11B | 11B | | +| Scrambling code change | No | No | | +| RPP ( Recovery period power control mode) | 0 | 0 | | +| ITP ( Initial transmission power control mode) | 0 | 0 | | + +**Table A.22: Compressed mode reference pattern 2 parameters** + +| Parameter | Set 1 | Set 2 | Set 4 | Set 5 | Note | +|---------------------------------------------------|---------|---------|---------|---------|-----------------------------------------| +| TGSN (Transmission Gap Starting Slot Number) | 4 | 4 | 8 | 10 | | +| TGL1 (Transmission Gap Length 1) | 7 | 7 | 14 | 10 | | +| TGL2 (Transmission Gap Length 2) | - | - | - | - | Only one gap in use. | +| TGD (Transmission Gap Distance) | 0 | 0 | 0 | 0 | | +| TGPL1 (Transmission Gap Pattern Length) | 3 | 12 | 4 | 8 | | +| TGPRC (Transmission Gap Pattern Repetition Count) | NA | NA | NA | NA | Defined by higher layers | +| TGCFN (Transmission Gap Connection Frame Number): | NA | NA | NA | NA | Defined by higher layers | +| UL/DL compressed mode selection | DL & UL | DL & UL | DL & UL | DL & UL | 2 configurations possible. DL & UL / DL | +| UL compressed mode method | SF/2 | SF/2 | SF/2 | SF/2 | | +| DL compressed mode method | SF/2 | SF/2 | SF/2 | SF/2 | | +| Downlink frame type and Slot format | 11B | 11B | 11B | 11B | | +| Scrambling code change | No | No | No | No | | +| RPP (Recovery period power control mode) | 0 | 0 | 0 | 0 | | +| ITP (Initial transmission power control mode) | 0 | 0 | 0 | 0 | | + +**Table A.22A: Compressed mode reference pattern 3 parameters** + +| Parameter | Set 1 | Set 2 | Set 3 | Set 4 | Note | +|---------------------------------------------------|---------|---------|---------|---------|-----------------------------------------| +| TGSN (Transmission Gap Starting Slot Number) | 8 | 8 | 8 | 8 | | +| TGL1 (Transmission Gap Length 1) | 14 | 14 | 14 | 14 | | +| TGL2 (Transmission Gap Length 2) | - | - | - | - | Only one gap in use. | +| TGD (Transmission Gap Distance) | 0 | 0 | 0 | 0 | | +| TGPL1 (Transmission Gap Pattern Length) | 8 | 24 | 24 | 24 | | +| TGPRC (Transmission Gap Pattern Repetition Count) | NA | NA | NA | NA | Defined by higher layers | +| TGCFN (Transmission Gap Connection Frame Number): | 0 | 4 | 12 | 20 | | +| UL/DL compressed mode selection | DL & UL | DL & UL | DL & UL | DL & UL | 2 configurations possible. DL & UL / DL | +| UL compressed mode method | SF/2 | SF/2 | SF/2 | SF/2 | | +| DL compressed mode method | SF/2 | SF/2 | SF/2 | SF/2 | | +| Downlink frame type and Slot format | 11B | 11B | 11B | 11B | | +| Scrambling code change | No | No | No | No | | +| RPP (Recovery period power control mode) | 0 | 0 | 0 | 0 | | +| ITP (Initial transmission power control mode) | 0 | 0 | 0 | 0 | | + +## A.6 DL reference parameters for PCH tests + +The parameters for the PCH demodulation tests are specified in Table A.23 and Table A.24. + +**Table A.23: Physical channel parameters for S-CCPCH** + +| Parameter | Unit | Level | +|---------------------------------------------------------------|------|-------| +| Channel bit rate | kbps | 60 | +| Channel symbol rate | ksps | 30 | +| Slot Format #i | - | 4 | +| TFCI | - | OFF | +| Power offsets of TFCI and Pilot fields relative to data field | dB | 0 | + +**Table A.24: Transport channel parameters for S-CCPCH** + +| Parameter | PCH | +|---------------------------------|--------------------| +| Transport Channel Number | 1 | +| Transport Block Size | 240 | +| Transport Block Set Size | 240 | +| Transmission Time Interval | 10 ms | +| Type of Error Protection | Convolution Coding | +| Coding Rate | $\frac{1}{2}$ | +| Rate Matching attribute | 256 | +| Size of CRC | 16 | +| Position of TrCH in radio frame | fixed | + +## A.7 DL reference channel parameters for HSDPA tests + +### A.7.1 Fixed Reference Channel (FRC) + +#### A.7.1.1 Fixed Reference Channel Definition H-Set 1/1A/1B/1C/1E + +**Table A.25: Fixed Reference Channel H-Set 1/1A/1B/1C/1E** + +| Parameter | Unit | Value | | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 534 | 777 | +| Inter-TTI Distance | TTI's | 3 | 3 | +| Number of HARQ Processes | Processes | 2 | 2 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 3202 | 4664 | +| Number Code Blocks | Blocks | 1 | 1 | +| Binary Channel Bits Per TTI | Bits | 4800 | 7680 | +| Total Available SML's in UE | SML's | 19200 | 19200 | +| Number of SML's per HARQ Proc. | SML's | 9600 | 9600 | +| Coding Rate | | 0.67 | 0.61 | +| Number of Physical Channel Codes | Codes | 5 | 4 | +| Modulation | | QPSK | 16QAM | +| Note: | The HS-DSCH shall be transmitted continuously with constant power but only every third TTI shall be allocated to the UE under test. The values in the table defines H-Set 1. H-Set 1A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 1 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 1B and H-Set 1C for 4C-HSDPA are formed by applying H-Set 1 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 1B and 4 carriers for H-Set 1C). H-Set 1E for 8C-HSDPA is formed by applying H-Set 1 to each of the carriers available in 8C-HSDPA mode. | | | + +![Diagram illustrating the coding rate for Fixed reference Channel H-Set 1 (QPSK).](99261d7a7ce0fb14086143419ac820ae_img.jpg) + +The diagram shows the flow of bits through various processing stages: + +- Inf. Bit Payload:** 3202 bits +- CRC Addition:** 3202 bits + 24 CRC bits +- Code Block Segmentation:** 3226 bits +- Turbo-Encoding (R=1/3):** 9678 bits + 12 Tail Bits +- 1st Rate Matching:** 9600 bits +- RV Selection:** 4800 bits +- Physical Channel Segmentation:** 960 bits (represented by a stack of boxes) + +Diagram illustrating the coding rate for Fixed reference Channel H-Set 1 (QPSK). + +**Figure A.12: Coding rate for Fixed reference Channel H-Set 1 (QPSK)** + +![Figure A.13: Coding rate for Fixed reference Channel H-Set 1 (16 QAM). This diagram shows the bit flow through various processing stages. The stages and their bit counts are: Inf. Bit Payload (4664), CRC Addition (4664 + 24 CRC), Code Block Segmentation (4688), Turbo-Encoding (R=1/3) (14064 + 12 Tail Bits), 1st Rate Matching (9600), RV Selection (7680), and Physical Channel Segmentation (1920).](b7321a97441b64ca21fa3647d44cfeb0_img.jpg) + +Inf. Bit Payload: 4664 + +CRC Addition: 4664 + 24 CRC + +Code Block Segmentation: 4688 + +Turbo-Encoding (R=1/3): 14064 + 12 Tail Bits + +1st Rate Matching: 9600 + +RV Selection: 7680 + +Physical Channel Segmentation: 1920 + +Figure A.13: Coding rate for Fixed reference Channel H-Set 1 (16 QAM). This diagram shows the bit flow through various processing stages. The stages and their bit counts are: Inf. Bit Payload (4664), CRC Addition (4664 + 24 CRC), Code Block Segmentation (4688), Turbo-Encoding (R=1/3) (14064 + 12 Tail Bits), 1st Rate Matching (9600), RV Selection (7680), and Physical Channel Segmentation (1920). + +Figure A.13: Coding rate for Fixed reference Channel H-Set 1 (16 QAM) + +### A.7.1.2 Fixed Reference Channel Definition H-Set 2 + +Table A.26: Fixed Reference Channel H-Set 2 + +| Parameter | Unit | Value | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 801 | 1166 | +| Inter-TTI Distance | TTI's | 2 | 2 | +| Number of HARQ Processes | Processes | 3 | 3 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 3202 | 4664 | +| Number Code Blocks | Blocks | 1 | 1 | +| Binary Channel Bits Per TTI | Bits | 4800 | 7680 | +| Total Available SML's in UE | SML's | 28800 | 28800 | +| Number of SML's per HARQ Proc. | SML's | 9600 | 9600 | +| Coding Rate | | 0.67 | 0.61 | +| Number of Physical Channel Codes | Codes | 5 | 4 | +| Modulation | | QPSK | 16QAM | +| Note: | The HS-DSCH shall be transmitted continuously with constant power but only every second TTI shall be allocated to the UE under test. | | | + +![Figure A.14: Coding rate for Fixed Reference Channel H-Set 2 (QPSK). This diagram shows the bit flow through various processing stages. The stages and their bit counts are: Inf. Bit Payload (3202), CRC Addition (3202 + 24 CRC), Code Block Segmentation (3226), Turbo-Encoding (R=1/3) (9678 + 12 Tail Bits), 1st Rate Matching (9600), RV Selection (4800), and Physical Channel Segmentation (960).](7a902d790635f608db2476e6340acf8b_img.jpg) + +Inf. Bit Payload: 3202 + +CRC Addition: 3202 + 24 CRC + +Code Block Segmentation: 3226 + +Turbo-Encoding (R=1/3): 9678 + 12 Tail Bits + +1st Rate Matching: 9600 + +RV Selection: 4800 + +Physical Channel Segmentation: 960 + +Figure A.14: Coding rate for Fixed Reference Channel H-Set 2 (QPSK). This diagram shows the bit flow through various processing stages. The stages and their bit counts are: Inf. Bit Payload (3202), CRC Addition (3202 + 24 CRC), Code Block Segmentation (3226), Turbo-Encoding (R=1/3) (9678 + 12 Tail Bits), 1st Rate Matching (9600), RV Selection (4800), and Physical Channel Segmentation (960). + +Figure A.14: Coding rate for Fixed Reference Channel H-Set 2 (QPSK) + +![Figure A.15: Coding rate for Fixed Reference Channel H-Set 2 (16QAM). This diagram shows the bit flow through various processing stages. It starts with an 'Inf. Bit Payload' of 4664 bits. After 'CRC Addition', 24 CRC bits are added, resulting in 4688 bits. This is followed by 'Code Block Segmentation' which maintains the 4688 bits. 'Turbo-Encoding (R=1/3)' then produces 14064 bits, including 12 'Tail Bits'. '1st Rate Matching' reduces this to 9600 bits. 'RV Selection' then results in 7680 bits. Finally, 'Physical Channel Segmentation' divides these into 1920 segments.](2686cc35669b140d74b134b0c673adf8_img.jpg) + +Figure A.15: Coding rate for Fixed Reference Channel H-Set 2 (16QAM). This diagram shows the bit flow through various processing stages. It starts with an 'Inf. Bit Payload' of 4664 bits. After 'CRC Addition', 24 CRC bits are added, resulting in 4688 bits. This is followed by 'Code Block Segmentation' which maintains the 4688 bits. 'Turbo-Encoding (R=1/3)' then produces 14064 bits, including 12 'Tail Bits'. '1st Rate Matching' reduces this to 9600 bits. 'RV Selection' then results in 7680 bits. Finally, 'Physical Channel Segmentation' divides these into 1920 segments. + +Figure A.15: Coding rate for Fixed Reference Channel H-Set 2 (16QAM) + +### A.7.1.3 Fixed Reference Channel Definition H-Set 3/3A/3B/3C/3E + +Table A.27: Fixed Reference Channel H-Set 3/3A/3B/3C/3E + +| Parameter | Unit | Value | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 1601 | 2332 | +| Inter-TTI Distance | TTI's | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 3202 | 4664 | +| Number Code Blocks | Blocks | 1 | 1 | +| Binary Channel Bits Per TTI | Bits | 4800 | 7680 | +| Total Available SML's,in UE | SML's | 57600 | 57600 | +| Number of SML's per HARQ Proc. | SML's | 9600 | 9600 | +| Coding Rate | | 0.67 | 0.61 | +| Number of Physical Channel Codes | Codes | 5 | 4 | +| Modulation | | QPSK | 16QAM | +| Note: | The values in the table define H-Set 3. H-Set 3A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 3 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 3B and H-Set 3C for 4C-HSDPA are formed by applying H-Set 3 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 3B and 4 carriers for H-Set 3C). H-Set 3E for 8C-HSDPA is formed by applying H-Set 3 to each of the carriers available in 8C-HSDPA mode. | | | + +![Figure A.16: Coding rate for Fixed reference Channel H-Set 3 (QPSK). This diagram shows the bit flow for H-Set 3. It starts with an 'Inf. Bit Payload' of 3202 bits. After 'CRC Addition', 24 CRC bits are added, resulting in 3226 bits. This is followed by 'Code Block Segmentation' which maintains the 3226 bits. 'Turbo-Encoding (R=1/3)' then produces 9678 bits, including 12 'Tail Bits'. '1st Rate Matching' reduces this to 9600 bits. 'RV Selection' then results in 4800 bits. Finally, 'Physical Channel Segmentation' divides these into 960 segments.](9e2b890eb1af21240ec68d210241d0d5_img.jpg) + +Figure A.16: Coding rate for Fixed reference Channel H-Set 3 (QPSK). This diagram shows the bit flow for H-Set 3. It starts with an 'Inf. Bit Payload' of 3202 bits. After 'CRC Addition', 24 CRC bits are added, resulting in 3226 bits. This is followed by 'Code Block Segmentation' which maintains the 3226 bits. 'Turbo-Encoding (R=1/3)' then produces 9678 bits, including 12 'Tail Bits'. '1st Rate Matching' reduces this to 9600 bits. 'RV Selection' then results in 4800 bits. Finally, 'Physical Channel Segmentation' divides these into 960 segments. + +Figure A.16: Coding rate for Fixed reference Channel H-Set 3 (QPSK) + +![Figure A.17: Coding rate for Fixed reference Channel H-Set 3 (16QAM). This diagram shows the bit flow through various processing stages. It starts with 'Inf. Bit Payload' (4664), followed by 'CRC Addition' (4664 + 24 CRC), 'Code Block Segmentation' (4688), 'Turbo-Encoding (R=1/3)' (14064 + 12 Tail Bits), '1st Rate Matching' (9600), 'RV Selection' (7680), and finally 'Physical Channel Segmentation' (1920).](cacf4ea7d22183dc5235f1673ef884e8_img.jpg) + +| | | | +|-------------------------------|-------|--------------| +| Inf. Bit Payload | 4664 | | +| CRC Addition | 4664 | 24 CRC | +| Code Block Segmentation | 4688 | | +| Turbo-Encoding (R=1/3) | 14064 | 12 Tail Bits | +| 1st Rate Matching | 9600 | | +| RV Selection | 7680 | | +| Physical Channel Segmentation | 1920 | | + +Figure A.17: Coding rate for Fixed reference Channel H-Set 3 (16QAM). This diagram shows the bit flow through various processing stages. It starts with 'Inf. Bit Payload' (4664), followed by 'CRC Addition' (4664 + 24 CRC), 'Code Block Segmentation' (4688), 'Turbo-Encoding (R=1/3)' (14064 + 12 Tail Bits), '1st Rate Matching' (9600), 'RV Selection' (7680), and finally 'Physical Channel Segmentation' (1920). + +Figure A.17: Coding rate for Fixed reference Channel H-Set 3 (16QAM) + +#### A.7.1.4 Fixed Reference Channel Definition H-Set 4 + +Table A.28: Fixed Reference Channel H-Set 4 + +| Parameter | Unit | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 534 | +| Inter-TTI Distance | TTI's | 2 | +| Number of HARQ Processes | Processes | 2 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 3202 | +| Number Code Blocks | Blocks | 1 | +| Binary Channel Bits Per TTI | Bits | 4800 | +| Total Available SML's in UE | SML's | 14400 | +| Number of SML's per HARQ Proc. | SML's | 7200 | +| Coding Rate | | 0.67 | +| Number of Physical Channel Codes | Codes | 5 | +| Modulation | | QPSK | +| Note: This FRC is used to verify the minimum inter-TTI distance for UE category 11. The HS-PDSCH shall be transmitted continuously with constant power. The six sub-frame HS-SCCH signalling pattern shall repeat as follows:
...O O X O X O O O X O X O...,
where 'X' marks TTI in which HS-SCCH uses the identity of the UE under test and 'O' marks TTI, in which HS-SCCH uses a different identity. | | | + +![Figure A.18: Coding rate for Fixed Reference Channel H-Set 4. This diagram shows the bit flow through various processing stages. It starts with 'Inf. Bit Payload' (3202), followed by 'CRC Addition' (3202 + 24 CRC), 'Code Block Segmentation' (3226), 'Turbo-Encoding (R=1/3)' (9678 + 12 Tail Bits), '1st Rate Matching' (7200), 'RV Selection' (4800), and finally 'Physical Channel Segmentation' (960).](c8262867e39639276066c34941705aed_img.jpg) + +| | | | +|-------------------------------|------|--------------| +| Inf. Bit Payload | 3202 | | +| CRC Addition | 3202 | 24 CRC | +| Code Block Segmentation | 3226 | | +| Turbo-Encoding (R=1/3) | 9678 | 12 Tail Bits | +| 1st Rate Matching | 7200 | | +| RV Selection | 4800 | | +| Physical Channel Segmentation | 960 | | + +Figure A.18: Coding rate for Fixed Reference Channel H-Set 4. This diagram shows the bit flow through various processing stages. It starts with 'Inf. Bit Payload' (3202), followed by 'CRC Addition' (3202 + 24 CRC), 'Code Block Segmentation' (3226), 'Turbo-Encoding (R=1/3)' (9678 + 12 Tail Bits), '1st Rate Matching' (7200), 'RV Selection' (4800), and finally 'Physical Channel Segmentation' (960). + +Figure A.18: Coding rate for Fixed Reference Channel H-Set 4 + +### A.7.1.5 Fixed Reference Channel Definition H-Set 5 + +Table A.29: Fixed Reference Channel H-Set 5 + +| Parameter | Unit | Value | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 801 | +| Inter-TTI Distance | TTI's | 1 | +| Number of HARQ Processes | Processes | 3 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 3202 | +| Number Code Blocks | Blocks | 1 | +| Binary Channel Bits Per TTI | Bits | 4800 | +| Total Available SML's in UE | SML's | 28800 | +| Number of SML's per HARQ Proc. | SML's | 9600 | +| Coding Rate | | 0.67 | +| Number of Physical Channel Codes | Codes | 5 | +| Modulation | | QPSK | +| Note: |

This FRC is used to verify the minimum inter-TTI distance for UE category 12. The HS-PDSCH shall be transmitted continuously with constant power. The six sub-frame HS-SCCH signalling pattern shall repeat as follows:
...OOXXXOOOXXXO...,
where 'X' marks TTI in which HS-SCCH uses the identity of the UE under test and 'O' marks TTI, in which HS-SCCH uses a different identity.

| | + +![Figure A.19: Coding rate for Fixed Reference Channel H-Set 5. This diagram shows the flow of bits through various processing stages. It starts with 'Inf. Bit Payload' (3202), followed by 'CRC Addition' (3202 + 24 CRC), 'Code Block Segmentation' (3226), 'Turbo-Encoding (R=1/3)' (9678 + 12 Tail Bits), '1st Rate Matching' (9600), 'RV Selection' (4800), and finally 'Physical Channel Segmentation' (960).](9c575767fe4409cdd2898df6f70139f5_img.jpg) + +Inf. Bit Payload 3202 + +CRC Addition 3202 24 CRC + +Code Block Segmentation 3226 + +Turbo-Encoding (R=1/3) 9678 12 Tail Bits + +1st Rate Matching 9600 + +RV Selection 4800 + +Physical Channel Segmentation 960 + +Figure A.19: Coding rate for Fixed Reference Channel H-Set 5. This diagram shows the flow of bits through various processing stages. It starts with 'Inf. Bit Payload' (3202), followed by 'CRC Addition' (3202 + 24 CRC), 'Code Block Segmentation' (3226), 'Turbo-Encoding (R=1/3)' (9678 + 12 Tail Bits), '1st Rate Matching' (9600), 'RV Selection' (4800), and finally 'Physical Channel Segmentation' (960). + +**Figure A.19: Coding rate for Fixed Reference Channel H-Set 5** + +### A.7.1.6 Fixed Reference Channel Definition H-Set 6/6A/6B/6C/6E + +**Table A.29A: Fixed Reference Channel H-Set 6/6A/6B/6C/6E** + +| Parameter | Unit | Value | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Nominal Avg. Inf. Bit Rate | kbps | 3219 | 4689 | +| Inter-TTI Distance | TTI's | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 6438 | 9377 | +| Number Code Blocks | Blocks | 2 | 2 | +| Binary Channel Bits Per TTI | Bits | 9600 | 15360 | +| Total Available SML's in UE | SML's | 115200 | 115200 | +| Number of SML's per HARQ Proc. | SML's | 19200 | 19200 | +| Coding Rate | | 0.67 | 0.61 | +| Number of Physical Channel Codes | Codes | 10 | 8 | +| Modulation | | QPSK | 16QAM | +| Note: | The values in the table define H-Set 6. H-Set 6A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 6 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 6B and H-Set 6C for 4C-HSDPA are formed by applying H-Set 6 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 6B and 4 carriers for H-Set 6C). H-Set 6E for 8C-HSDPA is formed by applying H-Set 6 to each of the carriers available in 8C-HSDPA mode. | | | + +![Figure A.20: Coding rate for Fixed reference Channel H-Set 6 (QPSK). This diagram shows the bit processing flow for QPSK modulation. It starts with an Information Bit Payload of 6438 bits. A 24-bit CRC is added, resulting in 6438 bits plus 24 CRC bits. This is then segmented into 3231 code blocks. Turbo-encoding with a rate of R=1/3 produces 9693 bits, including 12 tail bits. The first rate matching step reduces this to 9600 bits. RV selection then results in 4800 bits. Finally, physical channel segmentation divides these into 960 bits per TTI, represented by a stack of 10 bars.](e3734a615e069a3923c72f1ef4608fa9_img.jpg) + +Figure A.20: Coding rate for Fixed reference Channel H-Set 6 (QPSK). This diagram shows the bit processing flow for QPSK modulation. It starts with an Information Bit Payload of 6438 bits. A 24-bit CRC is added, resulting in 6438 bits plus 24 CRC bits. This is then segmented into 3231 code blocks. Turbo-encoding with a rate of R=1/3 produces 9693 bits, including 12 tail bits. The first rate matching step reduces this to 9600 bits. RV selection then results in 4800 bits. Finally, physical channel segmentation divides these into 960 bits per TTI, represented by a stack of 10 bars. + +Figure A.20: Coding rate for Fixed reference Channel H-Set 6 (QPSK) + +![Figure A.21: Coding rate for Fixed reference Channel H-Set 6 (16 QAM). This diagram shows the bit processing flow for 16 QAM modulation. It starts with an Information Bit Payload of 9377 bits. A 24-bit CRC is added, resulting in 9377 bits plus 24 CRC bits. This is then segmented into 4701 code blocks. Turbo-encoding with a rate of R=1/3 produces 14103 bits, including 12 tail bits. The first rate matching step reduces this to 9600 bits. RV selection then results in 7680 bits. Finally, physical channel segmentation divides these into 1920 bits per TTI, represented by a stack of 10 bars.](00d7302f6a24d401f2cfe45812dd6ccf_img.jpg) + +Figure A.21: Coding rate for Fixed reference Channel H-Set 6 (16 QAM). This diagram shows the bit processing flow for 16 QAM modulation. It starts with an Information Bit Payload of 9377 bits. A 24-bit CRC is added, resulting in 9377 bits plus 24 CRC bits. This is then segmented into 4701 code blocks. Turbo-encoding with a rate of R=1/3 produces 14103 bits, including 12 tail bits. The first rate matching step reduces this to 9600 bits. RV selection then results in 7680 bits. Finally, physical channel segmentation divides these into 1920 bits per TTI, represented by a stack of 10 bars. + +Figure A.21: Coding rate for Fixed reference Channel H-Set 6 (16 QAM) + +### A.7.1.7 Fixed Reference Channel Definition H-Set 7 + +Table A.29B: Fixed Reference Channel H-Set 7 + +| Parameter | Unit | Value | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 37.8 | +| Inter-TTI Distance | TTI's | 8 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 605 | +| Number Code Blocks | Blocks | 1 | +| Binary Channel Bits Per TTI | Bits | 960 | +| Coding Rate | | 0.66 | +| Number of Physical Channel Codes | Codes | 1 | +| Modulation | | QPSK | +| Note: | This FRC is used to verify CPC operation. The HS-DSCH shall be transmitted continuously with constant power but only every 8 th TTI shall be allocated to the UE under test. | | + +![Figure A.22: Coding rate for Fixed Reference Channel H-Set 7 (QPSK). This diagram shows the bit flow through various processing stages. It starts with an 'Inf. Bit Payload' of 605 bits. A 'CRC Addition' of 24 bits is added to the 605 bits, resulting in 629 bits. This is followed by 'Code Block Segmentation' which outputs 629 bits. 'Turbo-Encoding (R=1/3)' then processes these bits into 1887 bits, with 12 'Tail Bits' added at the end. The output of Turbo-Encoding is then processed by '1st Rate Matching' to produce 1899 bits. This is followed by 'RV Selection' which outputs 960 bits. Finally, 'Physical Channel Segmentation' outputs 960 bits.](3b5dee61a2394578df7e680b9a098fa7_img.jpg) + +| | | | +|-------------------------------|------|--------------| +| Inf. Bit Payload | 605 | | +| CRC Addition | 605 | 24 CRC | +| Code Block Segmentation | 629 | | +| Turbo-Encoding (R=1/3) | 1887 | 12 Tail Bits | +| 1st Rate Matching | 1899 | | +| RV Selection | 960 | | +| Physical Channel Segmentation | 960 | | + +Figure A.22: Coding rate for Fixed Reference Channel H-Set 7 (QPSK). This diagram shows the bit flow through various processing stages. It starts with an 'Inf. Bit Payload' of 605 bits. A 'CRC Addition' of 24 bits is added to the 605 bits, resulting in 629 bits. This is followed by 'Code Block Segmentation' which outputs 629 bits. 'Turbo-Encoding (R=1/3)' then processes these bits into 1887 bits, with 12 'Tail Bits' added at the end. The output of Turbo-Encoding is then processed by '1st Rate Matching' to produce 1899 bits. This is followed by 'RV Selection' which outputs 960 bits. Finally, 'Physical Channel Segmentation' outputs 960 bits. + +Figure A.22: Coding rate for Fixed Reference Channel H-Set 7 (QPSK) + +### A.7.1.8 Fixed Reference Channel Definition H-Set 8/8A/8B/8C/8E + +Table A.29C: Fixed Reference Channel H-Set 8/8A/8B/8C/8E + +| Parameter | Unit | Value | | | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--|--| +| Nominal Avg. Inf. Bit Rate | kbps | 13252 | | | | +| Inter-TTI Distance | TTI's | 1 | | | | +| Number of HARQ Processes | Processes | 6 | | | | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 26504 | | | | +| Number Code Blocks | Blocks | 6 | | | | +| Binary Channel Bits Per TTI | Bits | 43200 | | | | +| Total Available SML's in UE | SML's | 259200 | 264000 | | | +| Number of SML's per HARQ Proc. | SML's | 43200 | 44000 | | | +| Coding Rate | | 0.61 | 0.60 | | | +| Number of Physical Channel Codes | Codes | 15 | | | | +| Modulation | | 64QAM | | | | +| Note 1: | The values in the table define H-Set 8. H-Set 8A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 8 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 8B and H-Set 8C for 4C-HSDPA are formed by applying H-Set 8 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 8B and 4 carriers for H-Set 8C). H-Set 8E for 8C-HSDPA is formed by applying H-Set 8 to each of the carriers available in 8C-HSDPA mode. | | | | | +| Note 2: | For H-Set 8, if "Total number of soft channel bits" as per HS-DSCH categories is equal to 259200, set "Number of SML's per HARQ Proc." as 43200 using an implicit UE IR Buffer Size Allocation.
For H-Set 8, if "Total number of soft channel bits" is larger than or equal to 264000, set "Number of SML's per HARQ Proc." as 44000 using an explicit UE IR Buffer Size Allocation. | | | | | +| Note 3: | For H-Set 8A/8B/8C/8E, set "Number of SML's per HARQ Proc." as 43200 using an implicit UE IR Buffer Size Allocation. | | | | | + +![Figure A.23: Coding rate for Fixed reference Channel H-Set 8 (64 QAM). The diagram shows a stack of layers representing the data flow through various processing stages. From top to bottom: Inf. Bit Payload (26504), CRC Addition (26504 + 24 CRC), Code Block Segmentation (4422), Turbo - Encoding (R=1/3) (13266 + 12 Tail Bits), 1st Rate Matching (7200), RV Selection (7200), and Physical Channel Segmentation (2880).](098c14b0bed86af949bf0a327f252840_img.jpg) + +Figure A.23: Coding rate for Fixed reference Channel H-Set 8 (64 QAM). The diagram shows a stack of layers representing the data flow through various processing stages. From top to bottom: Inf. Bit Payload (26504), CRC Addition (26504 + 24 CRC), Code Block Segmentation (4422), Turbo - Encoding (R=1/3) (13266 + 12 Tail Bits), 1st Rate Matching (7200), RV Selection (7200), and Physical Channel Segmentation (2880). + +Figure A.23: Coding rate for Fixed reference Channel H-Set 8 (64 QAM) + +### A.7.1.9 Fixed Reference Channel Definition H-Set 9/9A/9B/9C/9E + +Table A.29D: Fixed Reference Channel H-Set 9/9A/9B/9C/9E + +| Parameter | Unit | Value | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------| +| | | Primary | Secondary | +| Transport block | | | | +| Combined Nominal Avg. Inf. Bit Rate | | 13652 | | +| Nominal Avg. Inf. Bit Rate | kbps | 8784 | 4868 | +| Inter-TTI Distance | TTI's | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 17568 | 9736 | +| Number Code Blocks | Blocks | 4 | 2 | +| Binary Channel Bits Per TTI | Bits | 28800 | 14400 | +| Total available SML's in UE | Bits | 345600 | | +| Number of SML's per HARQ Proc. | SML's | 28800 | 28800 | +| Coding Rate | | 0.61 | 0.68 | +| Number of Physical Channel Codes | Codes | 15 | 15 | +| Modulation | | 16QAM | QPSK | +| Note: | The values in the table define H-Set 9. H-Set 9A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 9 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 9B and H-Set 9C for 4C-HSDPA are formed by applying H-Set 9 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 9B and 4 carriers for H-Set 9C). H-Set 9E for 8C-HSDPA is formed by applying H-Set 9 to each of the carriers available in 8C-HSDPA mode. | | | + +![Diagram showing the coding rate for Fixed Reference Channel H-Set 9 Primary Transport Block. It illustrates the flow from Inf. Bit Payload (17568) through CRC addition, code block segmentation, turbo encoding, rate matching, and physical channel segmentation.](7f28f27b828d72d06d5d414a6b4a20a7_img.jpg) + +The diagram illustrates the processing of a primary transport block for Fixed Reference Channel H-Set 9. The data flows through several stages: starting with an information bit payload of 17568, followed by the addition of 24 CRC bits. This is then segmented into code blocks of 4398 bits. Turbo encoding with a rate of $R = 1/3$ produces 13194 bits plus 12 tail bits. This is followed by the first rate matching stage resulting in 7200 bits. After RV selection, the data undergoes physical channel segmentation into 1920 bits. + +| Stage | Value | +|--------------------------------|----------------------| +| Inf. Bit Payload | 17568 | +| CRC Addition | 17568 + 24 CRC | +| Code Block Segmentation | 4398 | +| Turbo - Encoding ( $R = 1/3$ ) | 13194 + 12 Tail Bits | +| 1 st Rate Matching | 7200 | +| RV Selection | 7200 | +| Physical Channel Segmentation | 1920 | + +Diagram showing the coding rate for Fixed Reference Channel H-Set 9 Primary Transport Block. It illustrates the flow from Inf. Bit Payload (17568) through CRC addition, code block segmentation, turbo encoding, rate matching, and physical channel segmentation. + +Figure A.24: Coding rate for Fixed Reference Channel H-Set 9 Primary Transport Block + +![Diagram showing the coding rate for Fixed Reference Channel H-Set 9 Secondary Transport Block. It illustrates the flow from Inf. Bit Payload (9736) through CRC addition, code block segmentation, turbo encoding, rate matching, and physical channel segmentation.](cc2f9155973f67e9efae011b93249ef5_img.jpg) + +The diagram illustrates the processing of a secondary transport block for Fixed Reference Channel H-Set 9. The data flows through several stages: starting with an information bit payload of 9736, followed by the addition of 24 CRC bits. This is then segmented into code blocks of 4880 bits. Turbo encoding with a rate of $R = 1/3$ produces 14640 bits plus 12 tail bits. This is followed by the first rate matching stage resulting in 14400 bits. After RV selection of 7200 bits, the data undergoes physical channel segmentation into 960 bits. + +| Stage | Value | +|-------------------------------|----------------------| +| Inf. Bit Payload | 9736 | +| CRC Addition | 9736 + 24 CRC | +| Code Block Segmentation | 4880 | +| Turbo- Encoding ( $R=1/3$ ) | 14640 + 12 Tail Bits | +| 1 st Rate Matching | 14400 | +| RV Selection | 7200 | +| Physical Channel Segmentation | 960 | + +Diagram showing the coding rate for Fixed Reference Channel H-Set 9 Secondary Transport Block. It illustrates the flow from Inf. Bit Payload (9736) through CRC addition, code block segmentation, turbo encoding, rate matching, and physical channel segmentation. + +Figure A.25: Coding rate for Fixed Reference Channel H-Set 9 Secondary Transport Block + +### A.7.1.10 Fixed Reference Channel Definition H-Set 10/10A/10B/10C/10E + +Table A.29E: Fixed Reference Channel H-Set 10/10A/10B/10C/10E + +| Parameter | Unit | Value | | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Nominal Avg. Inf. Bit Rate | Kbps | 8774 | 4860 | +| Inter-TTI Distance | TTI's | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | +| Information Bit Payload | Bits | 17548 | 9719 | +| Number Code Blocks | Blocks | 4 | 2 | +| Binary Channel Bits Per TTI | Bits | 28800 | 14400 | +| Number of SML's per HARQ Proc. | SML's | 28800 | 28800 | +| Coding Rate | | 0.6 | 0.67 | +| Number of Physical Channel Codes | Codes | 15 | 15 | +| Modulation | | 16QAM | QPSK | +| Note: | The values in the table define H-Set 10. H-Set 10A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 10 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 10B and H-Set 10C for 4C-HSDPA are formed by applying H-Set 10 to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 10B and 4 carriers for H-Set 10C). H-Set 10E for 8C-HSDPA is formed by applying H-Set 10 to each of the carriers available in 8C-HSDPA mode. | | | + +![Diagram illustrating the coding rate for Fixed Reference Channel H-Set 10 (16QAM). The diagram shows a series of horizontal bars of varying lengths, stacked vertically, representing the distribution of coded bits across different transport blocks. The bars are arranged in a way that suggests a 3D perspective, with the longest bars at the top and shorter bars appearing in the foreground at the bottom.](f1bbb2dc05f87cc762b8f1f0ff9f3ba3_img.jpg) + +Diagram illustrating the coding rate for Fixed Reference Channel H-Set 10 (16QAM). The diagram shows a series of horizontal bars of varying lengths, stacked vertically, representing the distribution of coded bits across different transport blocks. The bars are arranged in a way that suggests a 3D perspective, with the longest bars at the top and shorter bars appearing in the foreground at the bottom. + +Figure A.24: Coding rate for Fixed Reference Channel H-Set 10 (16QAM) + +![Figure A.25: Coding rate for Fixed Reference Channel H-Set 10 (QPSK). The diagram shows a stack of transport blocks. At the top, a black bar spans the width, with a white rectangle inside it. Below this, a white rectangle is shown. Further down, a stack of several white rectangles is depicted, representing multiple transport blocks. The rectangles are of varying widths, with some being wider than others, illustrating the coding rate for different transport block sizes.](69be95e218fb058ed062ca975e92a5c8_img.jpg) + +Figure A.25: Coding rate for Fixed Reference Channel H-Set 10 (QPSK). The diagram shows a stack of transport blocks. At the top, a black bar spans the width, with a white rectangle inside it. Below this, a white rectangle is shown. Further down, a stack of several white rectangles is depicted, representing multiple transport blocks. The rectangles are of varying widths, with some being wider than others, illustrating the coding rate for different transport block sizes. + +Figure A.25: Coding rate for Fixed Reference Channel H-Set 10 (QPSK) + +#### A.7.1.11 Fixed Reference Channel Definition H-Set 11/11A/11B/11C/11E + +Table A.29F: Fixed Reference Channel H-Set 11/11A/11B/11C/11E + +| Parameter | Unit | Value | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------| +| | | Primary | Secondary | +| Transport block | | | | +| Combined Nominal Avg. Inf. Bit Rate | | 22074 | | +| Nominal Avg. Inf. Bit Rate | kbps | 13300 | 8774 | +| Inter-TTI Distance | TTI's | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 26504 | 17568 | +| Number Code Blocks | Blocks | 6 | 4 | +| Binary Channel Bits Per TTI | Bits | 43200 | 28800 | +| Total available SML's in UE | Bits | 518400 | | +| Number of SML's per HARQ Proc. | SML's | 43200 | 43200 | +| Coding Rate | | 0.61 | 0.6 | +| Number of Physical Channel Codes | Codes | 15 | 15 | +| Modulation | | 64QAM | 16QAM | +| Note: | The values in the table define H-Set 11. H-Set 11A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 11 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 11B and H-Set 11C for 4C-HSDPA are formed by applying H-Set 11 and H-Set 11C to each of the carriers available in 4C-HSDPA mode (3 carriers for H-Set 11B and 4 carriers for H-Set 11C). H-Set 11E for 8C-HSDPA is formed by applying H-Set 11 to each of the carriers available in 8C-HSDPA mode. | | | + +![Diagram showing the coding rate for Fixed Reference Channel H-Set 11 Primary Transport Block. It illustrates the flow from Inf. Bit Payload (26504) through CRC addition (24 bits), code block segmentation (4422), turbo encoding (R=1/3) with 13266 bits and 12 tail bits, 1st rate matching (7200), RV selection (7200), and physical channel segmentation (2880).](f3ad0d455d96f36b0c1551e022b5a423_img.jpg) + +Inf . Bit Payload: 26504 + +CRC Addition: 26504 + 24 CRC + +Code Block Segmentation: 4422 + +Turbo - Encoding ( $R = 1/3$ ): 13266 + 12 Tail Bits + +1st Rate Matching: 7200 + +RV Selection: 7200 + +Physical Channel Segmentation: 2880 + +Diagram showing the coding rate for Fixed Reference Channel H-Set 11 Primary Transport Block. It illustrates the flow from Inf. Bit Payload (26504) through CRC addition (24 bits), code block segmentation (4422), turbo encoding (R=1/3) with 13266 bits and 12 tail bits, 1st rate matching (7200), RV selection (7200), and physical channel segmentation (2880). + +Figure A.26: Coding rate for Fixed Reference Channel H-Set 11 Primary Transport Block + +![Diagram showing the coding rate for Fixed Reference Channel H-Set 11 Secondary Transport Block. It illustrates the flow from Inf. Bit Payload (17568) through CRC addition (24 bits), code block segmentation (4398), turbo encoding (R=1/3) with 13194 bits and 12 tail bits, 1st rate matching (7200), RV selection (7200), and physical channel segmentation (1920).](96bb01315ba42d2185ff70400f09053f_img.jpg) + +Inf . Bit Payload: 17568 + +CRC Addition: 17568 + 24 CRC + +Code Block Segmentation: 4398 + +Turbo - Encoding ( $R = 1/3$ ): 13194 + 12 Tail Bits + +1st Rate Matching: 7200 + +RV Selection: 7200 + +Physical Channel Segmentation: 1920 + +Diagram showing the coding rate for Fixed Reference Channel H-Set 11 Secondary Transport Block. It illustrates the flow from Inf. Bit Payload (17568) through CRC addition (24 bits), code block segmentation (4398), turbo encoding (R=1/3) with 13194 bits and 12 tail bits, 1st rate matching (7200), RV selection (7200), and physical channel segmentation (1920). + +Figure A.27: Coding rate for Fixed Reference Channel H-Set 11 Secondary Transport Block + +### A.7.1.12 Fixed Reference Channel Definition H-Set 12 + +**Table A.29G: Fixed Reference Channel H-Set 12** + +| Parameter | Unit | Value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------| +| Nominal Avg. Inf. Bit Rate | kbps | 60 | +| Inter-TTI Distance | TTI's | 1 | +| Number of HARQ Processes | Processes | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 120 | +| Number Code Blocks | Blocks | 1 | +| Binary Channel Bits Per TTI | Bits | 960 | +| Total Available SML's in UE | SML's | 19200 | +| Number of SML's per HARQ Proc. | SML's | 3200 | +| Coding Rate | | 0.15 | +| Number of Physical Channel Codes | Codes | 1 | +| Modulation | | QPSK | +| Note 1: The RMC is intended to be used for DC-HSDPA mode and both cells shall transmit with identical parameters as listed in the table. | | | +| Note 2: Maximum number of transmission is limited to 1, i.e., retransmission is not allowed. The redundancy and constellation version 0 shall be used. | | | + +![Diagram showing the coding rate for Fixed reference Channel H-Set 12 (QPSK). It illustrates the flow of bits through various processing stages: Inf. Bit Payload (120), CRC Addition (120 + 24 CRC), Code Block Segmentation (144), Turbo-Encoding (R=1/3) resulting in 432 bits plus 12 Tail Bits, 1st Rate Matching (432), RV Selection (960), and Physical Channel Segmentation (960).](5f0934de7d51d5b287f8227e5deca80a_img.jpg) + +The diagram illustrates the bit flow and processing stages for the Fixed reference Channel H-Set 12 (QPSK): + +- Inf. Bit Payload:** 120 bits +- CRC Addition:** 120 bits + 24 CRC bits +- Code Block Segmentation:** 144 bits +- Turbo-Encoding (R=1/3):** 432 bits + 12 Tail Bits +- 1st Rate Matching:** 432 bits +- RV Selection:** 960 bits +- Physical Channel Segmentation:** 960 bits + +Diagram showing the coding rate for Fixed reference Channel H-Set 12 (QPSK). It illustrates the flow of bits through various processing stages: Inf. Bit Payload (120), CRC Addition (120 + 24 CRC), Code Block Segmentation (144), Turbo-Encoding (R=1/3) resulting in 432 bits plus 12 Tail Bits, 1st Rate Matching (432), RV Selection (960), and Physical Channel Segmentation (960). + +**Figure A.28: Coding rate for Fixed reference Channel H-Set 12 (QPSK)** + +### A.7.1.13 Fixed Reference Channel Definition H-Set 13/13A/13C + +**Table A.29H: Fixed Reference Channel H-Set 13/13A/13C** + +| Parameter | Unit | Value | | | | +|---------------------------------------|-----------|---------|--------|-------|--------| +| | | Primary | Second | Third | Fourth | +| Transport block | | | | | | +| Combined Nominal Avg. Inf. Bit Rate | | 27304 | | | | +| Nominal Avg. Inf. Bit Rate | Kbps | 8784 | 4868 | 4868 | 8784 | +| Inter-TTI Distance | TTI's | 1 | 1 | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 17568 | 9736 | 9736 | 17568 | + +| | | | | | | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------|-------|-------| +| Number Code Blocks | Blocks | 4 | 2 | 2 | 4 | +| Binary Channel Bits Per TTI | Bits | 28800 | 14400 | 14400 | 28800 | +| Total available SML's in UE | Bits | 1036800 | | | | +| Number of SML's per HARQ Proc. | SML's | 43200 | 43200 | 43200 | 43200 | +| Coding Rate | | 0.61 | 0.68 | 0.68 | 0.61 | +| Number of Physical Channel Codes | Codes | 15 | 15 | 15 | 15 | +| Modulation | | 16QAM | QPSK | QPSK | 16QAM | +| Note: | The values in the table define H-Set 13. H-Set 13A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 13 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 13C for 4C-HSDPA are formed by applying H-Set 13 to each of the carriers available in 4C-HSDPA mode. | | | | | + +![Figure A.29: Coding rate for Fixed Reference Channel H-Set 13 Primary and Fourth Transport Block. This diagram illustrates the bit processing flow for the primary and fourth transport blocks. It starts with an information bit payload of 17568. After CRC addition (24 bits), the total is 17592 bits. This is then segmented into 4 code blocks of 4398 bits each. Turbo encoding with a rate of R=1/3 produces 13194 bits plus 12 tail bits. The first rate matching step reduces this to 7200 bits. After RV selection, the data remains at 7200 bits. Finally, physical channel segmentation divides this into 1920 segments.](f83da0638c9b438f282afed053cddb80_img.jpg) + +Inf. Bit-Payload: 17568 + +CRC-Addition: 17568 + 24 CRC + +Code Block Segmentation: 4398 + +Turbo - Encoding (R = 1/3): 13194 + 12 Tail-Bits + +1st Rate-Matching: 7200 + +RV-Selection: 7200 + +Physical-Channel Segmentation: 1920 + +Figure A.29: Coding rate for Fixed Reference Channel H-Set 13 Primary and Fourth Transport Block. This diagram illustrates the bit processing flow for the primary and fourth transport blocks. It starts with an information bit payload of 17568. After CRC addition (24 bits), the total is 17592 bits. This is then segmented into 4 code blocks of 4398 bits each. Turbo encoding with a rate of R=1/3 produces 13194 bits plus 12 tail bits. The first rate matching step reduces this to 7200 bits. After RV selection, the data remains at 7200 bits. Finally, physical channel segmentation divides this into 1920 segments. + +Figure A.29: Coding rate for Fixed Reference Channel H-Set 13 Primary and Fourth Transport Block + +![Figure A.30: Coding rate for Fixed Reference Channel H-Set 13 Secondary and Third Transport Block. This diagram illustrates the bit processing flow for the secondary and third transport blocks. It starts with an information bit payload of 9736. After CRC addition (24 bits), the total is 9760 bits. This is then segmented into 4880 code blocks. Turbo encoding with a rate of R=1/3 produces 14640 bits plus 12 tail bits. The first rate matching step reduces this to 14400 bits. After RV selection, the data is reduced to 7200 bits. Finally, physical channel segmentation divides this into 960 segments.](d86ffa3857b2c16635c09b2768c4e01d_img.jpg) + +Inf. Bit Payload: 9736 + +CRC Addition: 9736 + 24 CRC + +Code Block Segmentation: 4880 + +Turbo- Encoding (R=1/3): 14640 + 12 Tail Bits + +1st Rate Matching: 14400 + +RV Selection: 7200 + +Physical Channel Segmentation: 960 + +Figure A.30: Coding rate for Fixed Reference Channel H-Set 13 Secondary and Third Transport Block. This diagram illustrates the bit processing flow for the secondary and third transport blocks. It starts with an information bit payload of 9736. After CRC addition (24 bits), the total is 9760 bits. This is then segmented into 4880 code blocks. Turbo encoding with a rate of R=1/3 produces 14640 bits plus 12 tail bits. The first rate matching step reduces this to 14400 bits. After RV selection, the data is reduced to 7200 bits. Finally, physical channel segmentation divides this into 960 segments. + +Figure A.30: Coding rate for Fixed Reference Channel H-Set 13 Secondary and Third Transport Block + +## A.7.1.14 Fixed Reference Channel Definition H-Set 14/14A/14C + +Table A.29I: Fixed Reference Channel H-Set 14/14A/14C + +| Parameter | Unit | Value | | | | +|---------------------------------------|-----------|---------|--------|-------|--------| +| | | Primary | Second | Third | Fourth | +| Transport block | | | | | | +| Combined Nominal Avg. Inf. Bit Rate | | 44148 | | | | +| Nominal Avg. Inf. Bit Rate | Kbps | 13300 | 8774 | 8774 | 13300 | +| Inter-TTI Distance | TTI's | 1 | 1 | 1 | 1 | +| Number of HARQ Processes | Processes | 6 | 6 | 6 | 6 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 26504 | 17568 | 17568 | 26504 | +| Number Code Blocks | Blocks | 6 | 4 | 4 | 6 | +| Binary Channel Bits Per TTI | Bits | 43200 | 28800 | 28800 | 43200 | +| Total available SML's in UE | Bits | 1036800 | | | | +| Number of SML's per HARQ Proc. | SML's | 43200 | 43200 | 43200 | 43200 | +| Coding Rate | | 0.61 | 0.6 | 0.6 | 0.61 | +| Number of Physical Channel Codes | Codes | 15 | 15 | 15 | 15 | +| Modulation | | 64QAM | 16QAM | 16QAM | 64QAM | + +Note: The values in the table define H-Set 14. H-Set 14A for DC-HSDPA and DB-DC-HSDPA is formed by applying H-Set 14 to each of the carriers available in DC-HSDPA and DB-DC-HSDPA mode. H-Set 14C for 4C-HSDPA are formed by applying H-Set 14 to each of the carriers available in 4C-HSDPA mode. + +![Diagram illustrating the coding process for Fixed Reference Channel H-Set 14 Primary and Fourth Transport Block. The process starts with an Information Bit Payload of 26504 bits. A CRC of 24 bits is added, resulting in 26528 bits. This is followed by Code-Block Segmentation into 4422 blocks. Turbo Encoding (R=1/3) produces 13266 bits plus 12 Tail-Bits. 1st Rate Matching results in 7200 bits. RV Selection results in 7200 bits. Finally, Physical Channel Segmentation results in 2880 blocks.](fed9090f9aa34eb8f39fb3fd5b781359_img.jpg) + +The diagram illustrates the coding process for Fixed Reference Channel H-Set 14 Primary and Fourth Transport Block. The process starts with an Information Bit Payload of 26504 bits. A CRC of 24 bits is added, resulting in 26528 bits. This is followed by Code-Block Segmentation into 4422 blocks. Turbo Encoding (R=1/3) produces 13266 bits plus 12 Tail-Bits. 1st Rate Matching results in 7200 bits. RV Selection results in 7200 bits. Finally, Physical Channel Segmentation results in 2880 blocks. + +Diagram illustrating the coding process for Fixed Reference Channel H-Set 14 Primary and Fourth Transport Block. The process starts with an Information Bit Payload of 26504 bits. A CRC of 24 bits is added, resulting in 26528 bits. This is followed by Code-Block Segmentation into 4422 blocks. Turbo Encoding (R=1/3) produces 13266 bits plus 12 Tail-Bits. 1st Rate Matching results in 7200 bits. RV Selection results in 7200 bits. Finally, Physical Channel Segmentation results in 2880 blocks. + +Figure A.31: Coding rate for Fixed Reference Channel H-Set 14 Primary and Fourth Transport Block + +![Figure A.32: Coding rate for Fixed Reference Channel H-Set 14 Secondary and Third Transport Block. The diagram shows the flow of data through various processing stages: Inf. Bit-Payload (17568), CRC-Addition (17568 + 24 CRC), Code-Block Segmentation (4398), Turbo-Encoding (R=1/3) resulting in 13194 bits plus 12 Tail-Bits, 1st-Rate-Matching (7200), RV-Selection (7200), and Physical-Channel Segmentation (1920).](3760416dd8f3568fcc52cd168cac3352_img.jpg) + +The diagram illustrates the data flow and bit counts at various stages of the coding process for a Fixed Reference Channel H-Set 14 Secondary and Third Transport Block: + +- Inf. Bit-Payload:** 17568 bits +- CRC-Addition:** 17568 bits + 24 CRC bits +- Code-Block Segmentation:** 4398 bits +- Turbo-Encoding ( $R=1/3$ ):** 13194 bits + 12 Tail-Bits +- 1st-Rate-Matching:** 7200 bits +- RV-Selection:** 7200 bits +- Physical-Channel Segmentation:** 1920 bits + +Figure A.32: Coding rate for Fixed Reference Channel H-Set 14 Secondary and Third Transport Block. The diagram shows the flow of data through various processing stages: Inf. Bit-Payload (17568), CRC-Addition (17568 + 24 CRC), Code-Block Segmentation (4398), Turbo-Encoding (R=1/3) resulting in 13194 bits plus 12 Tail-Bits, 1st-Rate-Matching (7200), RV-Selection (7200), and Physical-Channel Segmentation (1920). + +Figure A.32: Coding rate for Fixed Reference Channel H-Set 14 Secondary and Third Transport Block + +## A.8 DL reference parameters for MBMS tests + +### A.8.1 MCCH + +The parameters for the MCCH demodulation tests are specified in Table A.30 and Table A.31. + +Table A.30: Physical channel parameters for S-CCPCH + +| Parameter | Unit | Level | +|---------------------------------------------------------------|------|-------| +| Channel bit rate | kbps | 30 | +| Channel symbol rate | ksps | 15 | +| Slot Format #i | - | 2 | +| TFCI | - | ON | +| Power offsets of TFCI and Pilot fields relative to data field | dB | 0 | + +Table A.31: Transport channel parameters for S-CCPCH + +| Parameter | MCCH | +|---------------------------------|--------------------| +| User Data Rate | 7.6 kbps | +| Transport Channel Number | 1 | +| Transport Block Size | 72 | +| Transport Block Set Size | 72 | +| RLC SDU block size | 4088 | +| Transmission Time Interval | 10 ms | +| Repetition period | 640 ms | +| Modification period | 1280 ms | +| Type of Error Protection | Convolution Coding | +| Coding Rate | 1/3 | +| Rate Matching attribute | 256 | +| Size of CRC | 16 | +| Position of TrCH in radio frame | Flexible | + +## A.8.1 MTCH + +The parameters for the MTCH demodulation tests are specified in Table A.32 and Table A.33. + +**Table A.32: Physical channel parameters for S-CCPCH** + +| Parameter | Unit | Level | Level | Level | +|---------------------------------------------------------------|-------------|------------|------------|------------| +| User Data Rate | kbps | 512 | 256 | 128 | +| Channel bit rate | kbps | 1920 | 960 | 480 | +| Channel symbol rate | ksps | 480 | 480 | 240 | +| Slot Format #i | - | 23 | 14 | 12 | +| TFCI | - | ON | ON | ON | +| Power offsets of TFCI and Pilot fields relative to data field | dB | 0 | 0 | 0 | + +**Table A.33: Transport channel parameters for S-CCPCH** + +| Parameter | MTCH | | | | +|---------------------------------|-------------------|----------|-----------------------|------------------------| +| | 512 kbps
MBSFN | 256 kbps | 128 kbps
40 ms TTI | 128 kbps,
80 ms TTI | +| User Data Rate | | | | | +| Transport Channel Number | 1 | 1 | 1 | 1 | +| Transport Block Size | 2560 | 2536 | 2536 | 2536 | +| Transport Block Set Size | 20480 | 10144 | 5072 | 10144 | +| Nr of transport blocks/TTI | 8 | 4 | 2 | 4 | +| RLC SDU block size | 20336 | 10080 | 5024 | 10080 | +| Transmission Time Interval | 40 ms | 40 ms | 40 ms | 80 ms | +| Minimum inter-TTI interval | 1 | 1 | 1 | 1 | +| Type of Error Protection | Turbo | Turbo | Turbo | Turbo | +| Rate Matching attribute | 256 | 256 | 256 | 256 | +| Size of CRC | 16 | 16 | 16 | 16 | +| Position of TrCH in radio frame | Flexible | Flexible | Flexible | Flexible | + +## A.9 DL reference parameters for combined MTCH demodulation and cell identification + +Parameters for combined MTCH demodulation and cell identification requirements are defined in Table A.34. + +**Table A.34: Cell reselection parameters** + +| Parameter | Unit | Value | +|------------------------------------------------|---------|----------------------------------------------------------------------------| +| Serving cell in the initial condition | | Cell1 | +| Neighbour cells | | 32 intra-frequency neighbour cells are indicated including Cell2 and Cell3 | +| Cell_selection_and_reselection_quality_measure | | CPICH E b /N 0 | +| Qqualmin | dB | -20 | +| Qrxlevmin | dBm | -115 | +| UE_TXPWR_MAX_RACH | dB | 21 | +| Qhyst2 | dB | 20 dB | +| Treselection | seconds | 4 | +| Sintrasearch | dB | not sent | +| IE "FACH Measurement occasion info" | | not sent | + +## Annex B (normative) : Propagation conditions + +### B.1 (void) + +### B.2 Propagation Conditions + +#### B.2.1 Static propagation condition + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. + +#### B.2.2 Multi-path fading propagation conditions + +Table B.1 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum. + +**Table B.1: Propagation Conditions for Multi path Fading Environments (Cases 1 to 6)** + +| Case 1 | | Case 2 | | Case 3 | | Case 4 | | Case 5 (Note 1) | | Case 6 | | +|---------------------------------------------------------|--------------------------|---------------------------------------------------------|--------------------------|-----------------------------------------------------------------------|--------------------------|---------------------------------------------------------|--------------------------|-----------------------------------------------------------|--------------------------|-----------------------------------------------------------------------|--------------------------| +| Speed for Band I, II, III, IV, IX, X and XXV:
3 km/h | | Speed for Band I, II, III, IV, IX, X and XXV:
3 km/h | | Speed for Band I, II, III, IV, IX, X and XXV:
120 km/h | | Speed for Band I, II, III, IV, IX, X and XXV:
3 km/h | | Speed for Band I, II, III, IV, IX, X and XXV:
50 km/h | | Speed for Band I, II, III, IV, IX, X and XXV:
250 km/h | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI:
7 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI:
7 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI:
282 km/h
(Note 2) | | Speed for Band V, VI, VIII, XIX, XX and XXVI:
7 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI:
118 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI:
583 km/h
(Note 2) | | +| Speed for Band VII:
2.3 km/h | | Speed for Band VII:
2.3 km/h | | Speed for Band VII:
92 km/h | | Speed for Band VII:
2.3 km/h | | Speed for Band VII:
38 km/h | | Speed for Band VII:
192 km/h | | +| Speed for Band XI, XXI:
4.1 km/h | | Speed for Band XI, XXI:
4.1 km/h | | Speed for Band XI, XXI:
166 km/h | | Speed for Band XI, XXI:
4.1 km/h | | Speed for Band XI, XXI:
69 km/h | | Speed for Band XI, XXI:
345 km/h
(Note 2) | | +| Speed for Band XII, XIII, XIV:
8 km/h | | Speed for Band XII, XIII, XIV:
8 km/h | | Speed for Band XII, XIII, XIV:
320 km/h | | Speed for Band XII, XIII, XIV:
8 km/h | | Speed for Band XII, XIII, XIV:
133 km/h | | Speed for Band XII, XIII, XIV:
668 km/h | | +| Speed for Band XXII:
1.7 km/h | | Speed for Band XXII:
1.7 km/h | | Speed for Band XXII:
69 km/h | | Speed for Band XXII:
1.7 km/h | | Speed for Band XXII:
29 km/h | | Speed for Band XXII:
143 km/h | | +| Relative Delay [ns] | Relative mean Power [dB] | Relative Delay [ns] | Relative mean Power [dB] | Relative Delay [ns] | Relative mean Power [dB] | Relative Delay [ns] | Relative mean Power [dB] | Relative Delay [ns] | Relative mean Power [dB] | Relative Delay [ns] | Relative mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 976 | -10 | 976 | 0 | 260 | -3 | 976 | 0 | 976 | -10 | 260 | -3 | +| | | 20000 | 0 | 521 | -6 | | | | | 521 | -6 | +| | | | | 781 | -9 | | | | | 781 | -9 | + +NOTE 1: Case 5 is only used in TS25.133. + +NOTE 2: Speed above 250km/h is applicable to demodulation performance requirements only. + +**Table B.1A (void)** + +Table B.1B shows propagation conditions that are used for HSDPA performance measurements in multi-path fading environment. For HSDPA and DCH enhanced performance requirements, the fading of the signals and the AWGN signals provided in each receiver antenna port shall be independent. For DC-HSDPA requirements, the fading of the signals for each cell shall be independent. + +**Table B.1B: Propagation Conditions for Multi-Path Fading Environments for HSDPA Performance Requirements** + +| ITU Pedestrian A
Speed 3km/h
(PA3) | | ITU Pedestrian B
Speed 3km/h
(PB3) | | ITU vehicular A
Speed 30km/h
(VA30) | | ITU vehicular A
Speed 120km/h
(VA120) | | +|--------------------------------------------------------|---------------------------------|--------------------------------------------------------|---------------------------------|---------------------------------------------------------|---------------------------------|-------------------------------------------------------------------|---------------------------------| +| Speed for Band I, II, III, IV, IX, X and XXV
3 km/h | | Speed for Band I, II, III, IV, IX, X and XXV
3 km/h | | Speed for Band I, II, III, IV, IX, X and XXV
30 km/h | | Speed for Band I, II, III, IV, IX, X and XXV
120 km/h | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI
7 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI
7 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI
71 km/h | | Speed for Band V, VI, VIII, XIX, XX and XXVI
282 km/h (Note 1) | | +| Speed for Band VII
2.3 km/h | | Speed for Band VII
2.3 km/h | | Speed for Band VII
23 km/h | | Speed for Band VII
92 km/h | | +| Speed for Band XI, XXI, XXXII:
4.1 km/h | | Speed for Band XI, XXI, XXXII:
4.1 km/h | | Speed for Band XI, XXI, XXXII:
41 km/h | | Speed for Band XI, XXI, XXXII:
166 km/h (Note 1) | | +| Speed for Band XII, XIII, XIV
8 km/h | | Speed for Band XII, XIII, XIV
8 km/h | | Speed for Band XII, XIII, XIV
80 km/h | | Speed for Band XII, XIII, XIV
320 km/h | | +| Speed for Band XXII:
1.7 km/h | | Speed for Band XXII:
1.7 km/h | | Speed for Band XXII:
17 km/h | | Speed for Band XXII:
69 km/h | | +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 110 | -9.7 | 200 | -0.9 | 310 | -1.0 | 310 | -1.0 | +| 190 | -19.2 | 800 | -4.9 | 710 | -9.0 | 710 | -9.0 | +| 410 | -22.8 | 1200 | -8.0 | 1090 | -10.0 | 1090 | -10.0 | +| | | 2300 | -7.8 | 1730 | -15.0 | 1730 | -15.0 | +| | | 3700 | -23.9 | 2510 | -20.0 | 2510 | -20.0 | + +NOTE 1: Speed above 120km/h is applicable to demodulation performance requirements only. + +Table B.1C shows propagation conditions that are used for CQI test in multi-path fading and HS-SCCH-less demodulation of HS-DSCH. For HSDPA enhanced performance requirements, the fading of the signals and the AWGN signals provided in each receiver antenna port shall be independent. For DC-HSDPA requirements, the fading of the signals for each cell shall be independent. + +**Table B.1C: Propagation Conditions for CQI test in multi-path fading and HS-SCCH-less demodulation of HS-DSCH** + +| Case 8,
Speed for Band I, II, III, IV, IX, X and XXV: 30km/h
Speed for Band V, VI, VIII, XIX, XX and XXVI: 71km/h
Speed for Band VII: 23km/h
Speed for Band XI, XXI, XXXII: 41km/h
Speed for Band XII, XIII, XIV: 80 km/h
Speed for Band XXII: 17 km/h | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Relative Delay [ns] | Relative mean Power [dB] | +| 0 | 0 | +| 976 | -10 | + +Table B.1D shows propagation conditions that are used for MBMS demodulation performance measurements in multi-path fading environment. + +**Table B.1D: Propagation Conditions for Multi-Path Fading Environments for MBMS Performance Requirements** + +| ITU vehicular A
Speed 3km/h
(VA 3) | | +|---------------------------------------------------------|--| +| Speed for Band I, II, III, IV, IX, X and XXV
3 km/h | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI:
7 km/h | | +| Speed for Band VII:
2.3 km/h | | +| Speed for Band XI, XXI:
4.1 km/h | | +| Speed for Band XII, XIII, XIV:
8 km/h | | +| Speed for Band XXII:
1.7 km/h | | + + + +| Relative Delay [ns] | Relative Mean Power [dB] | +|----------------------------|---------------------------------| +| 0 | 0 | +| 310 | -1.0 | +| 710 | -9.0 | +| 1090 | -10.0 | +| 1730 | -15.0 | +| 2510 | -20.0 | + +Table B.1E shows propagation conditions that are used for MBSFN demodulation performance measurements in multi-path fading environment. All taps have classical Doppler spectrum. + +The fading of the signals and the AWGN signals provided in each receiver antenna port shall be independent. + +**Table B.1E: Propagation Conditions for Multi-Path Fading Environments for MBSFN Demodulation Performance Requirements** + +| MBSFN channel model | | +|---------------------------------------------------------|---------------------------------| +| Speed for Band I, II, III, IV, IX, X and XXV
3 km/h | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI:
7 km/h | | +| Speed for Band VII:
2.3 km/h | | +| Speed for Band XI, XXI:
4.1 km/h | | +| Speed for Band XII, XIII and XIV
8 km/h | | +| Speed for Band XXII:
1.7 km/h | | +| Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | +| 310 | -1 | +| 710 | -9 | +| 1090 | -10 | +| 1730 | -15 | +| 2510 | -20 | +| 12490 | -10 | +| 12800 | -11 | +| 13200 | -19 | +| 13580 | -20 | +| 14220 | -25 | +| 15000 | -30 | +| 27490 | -20 | +| 27800 | -21 | +| 28200 | -29 | +| 28580 | -30 | +| 29220 | -35 | +| 30000 | -40 | + +### B.2.3 Moving propagation conditions + +The dynamic propagation conditions for the test of the baseband performance are non fading channel models with two taps. The moving propagation condition has two tap, one static, Path0, and one moving, Path1. The time difference between the two paths is according Equation (B.1). The taps have equal strengths and equal phases. + +![Figure B.1: The moving propagation conditions. A graph showing two vertical arrows, P0 and P1, at time points t0 and t1 respectively. A horizontal double-headed arrow between them is labeled Δτ.](47d47f95101a8f543c94a735ad928a65_img.jpg) + +Figure B.1: The moving propagation conditions. A graph showing two vertical arrows, P0 and P1, at time points t0 and t1 respectively. A horizontal double-headed arrow between them is labeled Δτ. + +Figure B.1: The moving propagation conditions + +$$\Delta\tau = B + \frac{A}{2}(1 + \sin(\Delta\omega \cdot t)) \quad (\text{B.1})$$ + +The parameters in the equation are shown in the following table. + +Table B.2 + +| Parameter | Value | +|----------------|-----------------------------------| +| A | 5 $\mu\text{s}$ | +| B | 1 $\mu\text{s}$ | +| $\Delta\omega$ | $40 \cdot 10^{-3} \text{ s}^{-1}$ | + +## B.2.4 Birth-Death propagation conditions + +The dynamic propagation conditions for the test of the base band performance is a non fading propagation channel with two taps. The moving propagation condition has two taps, Path1 and Path2 which alternate between 'birth' and 'death'. The positions the paths appear are randomly selected with an equal probability rate and is shown in Figure B.2. + +![Figure B.2: Birth death propagation sequence. A sequence of three diagrams showing the appearance and disappearance of two paths, P1 and P2, over time. The first diagram shows P1 and P2 at specific positions. The second diagram shows P1 at a new position and P2 at its original position. The third diagram shows P2 at a new position and P1 at its original position. Blue rectangular blocks represent the channel response at different time intervals.](a6c3e540dd89b417038cfeb0e67516e1_img.jpg) + +Figure B.2: Birth death propagation sequence. A sequence of three diagrams showing the appearance and disappearance of two paths, P1 and P2, over time. The first diagram shows P1 and P2 at specific positions. The second diagram shows P1 at a new position and P2 at its original position. The third diagram shows P2 at a new position and P1 at its original position. Blue rectangular blocks represent the channel response at different time intervals. + +Figure B.2: Birth death propagation sequence + +1. Two paths, Path1 and Path2 are randomly selected from the group $[-5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5] \mu\text{s}$ . The paths have equal magnitudes and equal phases. +2. After 191 ms, Path1 vanishes and reappears immediately at a new location randomly selected from the group $[-5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5] \mu\text{s}$ but excludes the point Path 2. The magnitudes and the phases of the tap coefficients of Path 1 and Path 2 shall remain unaltered. +3. After an additional 191 ms, Path2 vanishes and reappears immediately at a new location randomly selected from the group $[-5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5] \mu\text{s}$ but excludes the point Path 1. The magnitudes and the phases of the tap coefficients of Path 1 and Path 2 shall remain unaltered. + +The sequence in 2) and 3) is repeated. + +## B.2.5 High speed train condition + +The high speed train condition for the test of the baseband performance is a non fading propagation channel with one tap. Doppler shift is given by + +$$(B.2)$$ + +where $f_d$ is the Doppler shift and $f_{max}$ is the maximum Doppler frequency. The cosine of angle is given by + +$$(B.3)$$ + +$$(B.4)$$ + +$$(B.5)$$ + +where $d_0$ is the initial distance of the train from BS, and $d$ is BS-Railway track distance, both in meters; $v$ is the velocity of the train in m/s, $t$ is time in seconds. + +Doppler shift and cosine angle is given by equation B.2 and B.3-B.5 respectively, where the required input parameters listed in table B.3 and the resulting Doppler shift shown in Figure B.3 are applied for all frequency bands. + +**Table B.3** + +| Parameter | Value | +|-----------|----------| +| $d_0$ | 300 m | +| $d$ | 2 m | +| $v$ | 300 km/h | +| $f_{max}$ | 600 Hz | + +NOTE1: Parameters for HST conditions in table B.3 including $f_d$ and Doppler shift trajectories presented on figure B.3 were derived for Band1. + +![Figure B.3: Doppler shift trajectory. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 20). The plot shows a periodic square wave-like signal. The signal starts at approximately 600 Hz, drops to -600 Hz at 2 seconds, returns to 600 Hz at 5 seconds, drops to -600 Hz at 9 seconds, returns to 600 Hz at 12 seconds, drops to -600 Hz at 16 seconds, and returns to 600 Hz at 20 seconds.](44faa5cb8c5bb66acd22c61811f12b9a_img.jpg) + +Figure B.3: Doppler shift trajectory. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 20). The plot shows a periodic square wave-like signal. The signal starts at approximately 600 Hz, drops to -600 Hz at 2 seconds, returns to 600 Hz at 5 seconds, drops to -600 Hz at 9 seconds, returns to 600 Hz at 12 seconds, drops to -600 Hz at 16 seconds, and returns to 600 Hz at 20 seconds. + +**Figure B.3: Doppler shift trajectory** + +## B.2.6 MIMO propagation conditions + +MIMO propagation conditions are defined for a 2x2 antenna configuration. The resulting propagation channel shall be characterized by a complex 2x2 matrix termed + +The channel coefficients of **H** shall be defined as a function of the possible precoding vectors or matrices. The possible precoding vectors for MIMO operation according to [8] shall be termed + +$$(EQ.B.2.6.1)$$ + +In what follows. Furthermore the following possible precoding matrices shall be defined: + +$$(EQ.B.2.6.2)$$ + +### B.2.6.1 MIMO Single Stream Fading Conditions + +For MIMO single stream conditions, the resulting propagation channel shall be generated using two independent fading processes with classical Doppler and one randomly picked but fixed precoding vector out of the set defined in equation EQ.B.2.6.1. The two fading processes shall be generated according to the parameters in Table B.4 + +**Table B.4** + +| MIMO Single Stream Conditions, | | | +|-------------------------------------------------------|--------------------------|----------------------------| +| Speed for Band I, II, III, IV, IX, X and XXV: 3km/h | | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI: 7.1km/h | | | +| Speed for Band VII: 2.3km/h | | | +| Speed for Band XI, XXI: 4.1km/h | | | +| Speed for Band XII, XIII and XIV: 8 km/h | | | +| Speed for Band XXII: 1.7 km/h | | | +| Relative Delay [ns] | Relative Mean Power [dB] | (Amplitude, phase) symbols | +| 0 | 0 | | +| 0 | 0 | | + +NOTE: The amplitude is not used in tests under MIMO single stream conditions, only the phase will be used. + +The channel coefficients of the resulting propagation channel under MIMO single stream conditions shall be given by + +The generation of the resulting channel coefficients for MIMO single stream conditions and the association with the transmitter and receiver ports are depicted Figure B.4. Figure B.4 does not restrict test system implementation. + +**Figure B.4: Test setup under MIMO Single Stream Fading Conditions** + +## B.2.6.2 MIMO Dual Stream Fading Conditions + +For MIMO dual stream conditions, the resulting propagation channel shall be generated using two independent fading processes with classical Doppler and one randomly picked but fixed precoding matrix $\mathbf{W}$ out of the set defined in equation EQ.B.2.6.2. The two fading processes shall be generated according to the parameters in Table B.5 + +**Table B.5** + +| MIMO Dual Stream Conditions, | | | +|-------------------------------------------------------|--------------------------|----------------------------| +| Speed for Band I, II, III, IV, IX, X and XXV: 3km/h | | | +| Speed for Band V, VI, VIII, XIX, XX and XXVI: 7.1km/h | | | +| Speed for Band VII: 2.3km/h | | | +| Speed for Band XI, XXI: 4.1km/h | | | +| Speed for Band XII, XIII and XIV: 8 km/h | | | +| Speed for Band XXII: 1.7 km/h | | | +| Relative Delay [ns] | Relative Mean Power [dB] | (Amplitude, phase) symbols | +| 0 | 0 | | +| 0 | -3 | | + +The channel coefficients of the resulting propagation channel under MIMO dual stream conditions shall be given by + +The generation of the resulting channel coefficients for MIMO dual stream conditions and the association with the transmitter and receiver ports are depicted Figure B.5. Figure B.5 does not restrict test system implementation. + +**Figure B.5: Test setup under MIMO Dual Stream Fading Conditions** + +### B.2.6.3 MIMO Dual Stream Static Orthogonal Conditions + +The channel coefficients of the resulting propagation channel under MIMO dual stream conditions shall be given by + +The generation of the resulting channel coefficients for MIMO dual stream conditions and the association with the transmitter and receiver ports are depicted Figure B.6. Figure B.6 does not restrict test system implementation. + +![A light blue rectangular box, likely representing a test setup diagram.](f95e8ef65337ff45839ad3994f66af54_img.jpg) + +A light blue rectangular box, likely representing a test setup diagram. It is a simple rectangle with a light blue fill and a thin black border, positioned on the right side of the page. + +A light blue rectangular box, likely representing a test setup diagram. + +**Figure B.6: Test setup under MIMO Dual Stream Static Orthogonal Conditions** + +### B.2.7 Propagation conditions for MIMO with four transmit antennas + +The propagation conditions for MIMO with four transmit antennas are defined for a 4x4 antenna configuration. The resulting propagation channel shall be characterized by a complex 4x4 matrix termed + +The channel coefficients of **H** shall be defined as a function of the possible precoding matrices. The possible precoding matrices for MIMO operation with four transmit antennas according to [8] are obtained by the quantity **W** = which denotes the matrix defined by the columns given by the set from the expression where **I** is the identity matrix and the vector is given in [8], Table 14B.7. + +### B.2.7.1 MIMO with Four Transmit Antennas and Four Streams Static Orthogonal Conditions + +The channel coefficients of the resulting propagation channel under MIMO with four transmit antennas and four stream conditions shall be given by + +The generation of the resulting channel coefficients for MIMO with four transmit antennas and four stream conditions and the association with the transmitter and receiver ports can be derived from Figure B.4 with the application of the above mentioned coefficients. Figure B.4 does not restrict test system implementation. + +### B.2.7.2 MIMO with Four Transmit Antennas Only With Dual Stream Fading Conditions + +For MIMO with four transmit antennas and dual stream conditions, the resulting propagation channel shall be generated using two independent fading processes with classical Doppler and one randomly picked but fixed precoding matrix **W** out of the set defined in Section B.2.7 with two transport blocks. The two fading processes shall be generated according to the parameters in Table B.8 + +**Table B.8** + +| MIMO Dual Stream Conditions,
Speed for Band I, II, III, IV, IX, X and XXV: 3km/h
Speed for Band V, VI, VIII, XIX, XX and XXVI: 7.1km/h
Speed for Band VII: 2.3km/h
Speed for Band XI, XXI: 4.1km/h
Speed for Band XII, XIII and XIV: 8 km/h
Speed for Band XXII: 1.7 km/h | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------| +| Relative Delay [ns] | Relative Mean Power [dB] | (Amplitude, phase) symbols | +| 0 | 0 | | +| 0 | -3 | | + +The channel coefficients of the resulting propagation channel under MIMO with four transmit antennas and dual stream conditions shall be given by + +Where **WH** is a 2x4 matrix. The generation of the resulting channel coefficients for MIMO with four transmit antennas and dual stream conditions and the association with the transmitter and receiver ports can be derived from Figure B.5 with the appropriate changes to the matrix dimensions (**W**). Figure B.5 does not restrict test system implementation. + +## 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 Connection Set-up + +Table C.1 describes the downlink Physical Channels that are required for connection set up. + +**Table C.1: Downlink Physical Channels required +for connection set-up** + +| Physical Channel | +|------------------| +| P-CPICH | +| P-CCPCH | +| SCH | +| S-CCPCH | +| PICH | +| AICH | +| DPCH | + +### C.3 During connection + +The following clauses, describes the downlink Physical Channels that are transmitted during a connection i.e., when measurements are done. For these measurements the offset between DPCH and SCH shall be zero chips at Node B meaning that SCH is overlapping with the first symbols in DPCH in the beginning of DPCH slot structure. + +#### C.3.1 Measurement of Rx Characteristics + +Table C.2 is applicable for measurements on the Receiver Characteristics (clause 7) with the exception of subclause 7.4 (Maximum input level). + +**Table C.2: Downlink Physical Channels transmitted during a connection** + +| Physical Channel | Power ratio | +|------------------|-------------------------------------------------------| +| P-CPICH | $\text{P-CPICH\_Ec} / \text{DPCH\_Ec} = 7 \text{ dB}$ | +| P-CCPCH | $\text{P-CCPCH\_Ec} / \text{DPCH\_Ec} = 5 \text{ dB}$ | +| SCH | $\text{SCH\_Ec} / \text{DPCH\_Ec} = 5 \text{ dB}$ | +| PICH | $\text{PICH\_Ec} / \text{DPCH\_Ec} = 2 \text{ dB}$ | +| DPCH | Test dependent power | + +## C.3.2 Measurement of Performance requirements + +Table C.3 is applicable for measurements on the Performance requirements (clause 8), including subclause 7.4 (Maximum input level) and subclause 6.4.4 (Out-of-synchronization handling of output power). + +**Table C.3: Downlink Physical Channels transmitted during a connection1** + +| Physical Channel | Power ratio | NOTE | +|------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH | $P\text{-CPICH\_Ec/lor} = -10 \text{ dB}$ | Use of P-CPICH or S-CPICH as phase reference is specified for each requirement and is also set by higher layer signalling. | +| S-CPICH | $S\text{-CPICH\_Ec/lor} = -10 \text{ dB}$ | When S-CPICH is the phase reference in a test condition, the phase of S-CPICH shall be 180 degrees offset from the phase of P-CPICH. When S-CPICH is not the phase reference, it is not transmitted. | +| P-CCPCH | $P\text{-CCPCH\_Ec/lor} = -12 \text{ dB}$ | When BCH performance is tested the $P\text{-CCPCH\_Ec/lor}$ is test dependent | +| SCH | $SCH\text{-Ec/lor} = -12 \text{ dB}$ | This power shall be divided equally between Primary and Secondary Synchronous channels | +| PICH | $PICH\text{-Ec/lor} = -15 \text{ dB}$ | | +| DPCH | Test dependent power | When S-CPICH is the phase reference in a test condition, the phase of DPCH shall be 180 degrees offset from the phase of P-CPICH.
When BCH performance is tested the DPCH is not transmitted. | +| OCNS | Necessary power so that total transmit power spectral density of Node B (lor) adds to one 1 | OCNS interference consists of 16 dedicated data channels as specified in table C.6. | + +NOTE 1 For dynamic power correction required to compensate for the presence of transient channels, e.g. control channels, a subset of the DPCH channels may be used. + +### C.3.3 Connection with open-loop transmit diversity mode + +Table C.4 is applicable for measurements for subclause 8.6.1 (Demodulation of DCH in open loop transmit diversity mode). + +**Table C.4: Downlink Physical Channels transmitted during a connection1** + +| Physical Channel | Power ratio | NOTE | +|---------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec1/lor = -13 dB | 1. Total P-CPICH_Ec/lor = -10 dB | +| P-CPICH (antenna 2) | P-CPICH_Ec2/lor = -13 dB | | +| P-CCPCH (antenna 1) | P-CCPCH_Ec1/lor = -15 dB | 1. STTD applied
2. Total P-CCPCH_Ec/lor = -12 dB | +| P-CCPCH (antenna 2) | P-CCPCH_Ec2/lor = -15 dB | | +| SCH (antenna 1 / 2) | SCH_Ec/lor = -12 dB | 1. TSTD applied.
2. This power shall be divided equally between Primary and Secondary Synchronous channels
3. When BCH performance is tested the P-CCPCH_Ec/lor is test dependent | +| PICH (antenna 1) | PICH_Ec1/lor = -18 dB | 1. STTD applied
2. Total PICH_Ec/lor = -15 dB | +| PICH (antenna 2) | PICH_Ec2/lor = -18 dB | | +| DPCH | Test dependent power | 1. STTD applied
2. Total power from both antennas | +| OCNS | Necessary power so that total transmit power spectral density of Node B (lor) adds to one 1 | 1. This power shall be divided equally between antennas
2. OCNS interference consists of 16 dedicated data channels as specified in Table C.6. | + +Note 1: For dynamic power correction required to compensate for the presence of transient channels, e.g. control channels, a subset of the DPCH channels may be used. + +### C.3.4 Connection with closed loop transmit diversity mode + +Table C.5 is applicable for measurements for subclause 8.6.2 (Demodulation of DCH in closed loop transmit diversity mode). + +**Table C.5: Downlink Physical Channels transmitted during a connection1** + +| Physical Channel | Power ratio | NOTE | +|---------------------|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec1/Ior = -13 dB | 1. Total P-CPICH_Ec/Ior = -10 dB | +| P-CPICH (antenna 2) | P-CPICH_Ec2/Ior = -13 dB | | +| P-CCPCH (antenna 1) | P-CCPCH_Ec1/Ior = -15 dB | 1. STTD applied | +| P-CCPCH (antenna 2) | P-CCPCH_Ec2/Ior = -15 dB | 1. STTD applied,
2. total P-CCPCH_Ec/Ior = -12 dB | +| SCH (antenna 1 / 2) | SCH_Ec/Ior = -12 dB | | +| PICH (antenna 1) | PICH_Ec1/Ior = -18 dB | 1. STTD applied | +| PICH (antenna 2) | PICH_Ec2/Ior = -18 dB | 2. STTD applied, total PICH_Ec/Ior = -15 dB | +| DPCH | Test dependent power | 1. Total power from both antennas | +| OCNS | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one (Notes 1 & 2) | 1. This power shall be divided equally between antennas
2. OCNS interference consists of 16 dedicated data channels. As specified in Table C.6. | + +Note 1: For dynamic power correction required to compensate for the presence of transient channels, e.g. control channels, a subset of the DPCH channels may be used. + +Note 2: For the case of DPCH with transmit diversity, the OCNS power calculation shall be based on the addition of the power from Antenna 1 and Antenna 2, i.e. disregarding any phase relationship between the antennas. + +**Table C.6: DPCH Channelization Code and relative level settings for OCONS signal** + +| Channelization Code at SF=128 | Relative Level setting (dB) (Note 1) | DPCH Data (see NOTE 3) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2 | -1 | The DPCH data for each channelization code shall be uncorrelated with each other and with any wanted signal over the period of any measurement. For OCONS with transmit diversity the DPCH data sent to each antenna shall be either STTD encoded or generated from uncorrelated sources. | +| 11 | -3 | | +| 17 | -3 | | +| 23 | -5 | | +| 31 | -2 | | +| 38 | -4 | | +| 47 | -8 | | +| 55 | -7 | | +| 62 | -4 | | +| 69 | -6 | | +| 78 | -5 | | +| 85 | -9 | | +| 94 | -10 | | +| 125 | -8 | | +| 113 | -6 | | +| 119 | 0 | | +|

Note 1: The relative level setting specified in dB refers only to the relationship between the OCONS channels. The level of the OCONS channels relative to the Ior of the complete signal is a function of the power of the other channels in the signal with the intention that the power of the group of OCONS channels is used to make the total signal add up to 1.

Note 2: The DPCH Channelization Codes and relative level settings are chosen to simulate a signal with realistic Peak to Average Ratio.

Note 3: For MBSFN, the group of OCONS channels represent orthogonal S-CCPCH channels instead of DPCH. Transmit diversity is not applicable to MBSFN which excludes STTD.

| | | + +### C.3.5 (void) + +Table C.6A: (void) + +## C.4 W-CDMA Modulated Interferer + +Table C.7 describes the downlink Channels that are transmitted as part of the W-CDMA modulated interferer. + +Table C.7: Spreading Code, Timing offsets and relative level settings for W-CDMA Modulated Interferer signal channels + +| Channel Type | Spreading Factor | Channelization Code | Timing offset (x256T chip ) | Power | NOTE | +|--------------|------------------|---------------------|----------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| P-CCPCH | 256 | 1 | 0 | P-CCPCH_Ec/Ior = -10 dB | | +| SCH | 256 | - | 0 | SCH_Ec/Ior = -10 dB | The SCH power shall be divided equally between Primary and Secondary Synchronous channels | +| P-CPICH | 256 | 0 | 0 | P-CPICH_Ec/Ior = -10 dB | | +| PICH | 256 | 16 | 16 | PICH_Ec/Ior = -15 dB | | +| OCNS | See table C.6 | | | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | OCNS interference consists of the dedicated data channels. As specified in Table C.6. | + +## C.5 HSDPA DL Physical channels + +### C.5.1 Downlink Physical Channels connection set-up + +Table C.8 is applicable for the measurements for tests in subclause 7.4.2, 9.2.1 and 9.3. Table C.9 is applicable for the measurements for tests in subclause 9.2.2 and 9.2.4. Table C.10 is applicable for the measurements for tests in subclause 9.2.3. Table C.11 is applicable for the measurements for tests in subclause 9.4.1. Table C.12 is applicable for the measurements in subclause 9.4.2. Table C.12A and C.12B are applicable to requirements in subclause 9.6. Table C.12D is applicable for the measurements in subclause 9.2.4 and 9.2.4A when explicitly mentioned. Table C.12E is applicable for the measurements in subclause 9.4.3 and 9.4.4 when explicitly mentioned. Table C.12F is applicable for the measurements in subclauses 9.2.4B and 9.2.4C. Table C.12G is applicable for the measurements in subclauses 9.4.5 and 9.4.6. + +**Table C.8: Downlink physical channels for HSDPA/DC-HSDPA/DB-DC-HSDPA/4C-HSDPA receiver testing for Single Link performance.** + +| Physical Channel | Parameter | Value | Note | +|------------------|-----------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/lor | -10dB | | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | Mean power level is shared with SCH. | +| SCH | SCH_Ec/lor | -12dB | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
P-SCH code is S_dl,0 as per TS25.213
S-SCH pattern is scrambling code group 0 | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | Test-specific only for serving HS-DSCH cell, omitted otherwise | 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present in HSDPA configuration. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | . | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one | OCNS interference consists of a number of dedicated data channels as specified in table C.13 and C. 13A. Table C.13 specifies the OCNS setup for H-Set 1 to H-Set 6. Table C.13A specifies the OCNS setup for H-Set 8 and H-set 10. | + +**Table C.9: Downlink physical channels for HSDPA/DC-HSDPA/DB-DC-HSDPA/4C-HSDPA receiver testing for Open Loop Transmit Diversity and MIMO performance.** + +| Physical Channel | Parameter | Value | Note | +|---------------------|-----------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec1/lor | -13dB | 1. Total P-CPICH_Ec/lor = -10dB | +| P-CPICH (antenna 2) | P-CPICH_Ec2/lor | -13dB | | +| P-CCPCH (antenna 1) | P-CCPCH_Ec1/lor | -15dB | 1. STTD applied.
2. Total P-CCPCH Ec/lor is -12dB. | +| P-CCPCH (antenna 2) | P-CCPCH_Ec2/lor | -15dB | | +| SCH (antenna 1/2) | SCH_Ec/lor | -12dB | 1. TSTD applied.
2. Power divided equally between primary and secondary SCH. | +| PICH (antenna 1) | PICH_Ec1/lor | -18dB | 1. STTD applied.
2. Total PICH Ec/lor is -15dB. | +| PICH (antenna 2) | PICH_Ec2/lor | -18dB | | +| DPCH | DPCH_Ec/lor | Test-specific only for serving HS-DSCH cell, omitted otherwise | 1. STTD applied. | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | 1. STTD applied.
2. Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | 1. UE assumes STTD applied.
2. No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | 1. As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/lor | DTX'd | 1. UE assumes STTD applied.
2. No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present in HSDPA configuration. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | 1. STTD applied for open loop transmit diversity tests, precoding used for MIMO tests | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one (Note 1) | 1. Balance of power $I_{or}$ of the Node-B is assigned to OCNS.
2. Power divided equally between antennas.
3. OCNS interference consists of a number of dedicated data channels as specified in table C.13 and C.13A. Table C.13 specifies the OCNS setup for H-Set 1 to H-set 6. Table C.13A specifies the OCNS setup for H-Set 9 and H-Set 11. | + +Note 1: For the case of DPCH with transmit diversity, the OCNS power calculation shall be based on the addition of the power from Antenna 1 and Antenna 2, i.e. disregarding any phase relationship between the antennas. + +**Table C.10: Downlink physical channels for HSDPA receiver testing for Closed Loop. Transmit Diversity (Mode-1) performance.** + +| Physical Channel | Parameter | Value | Note | +|---------------------|-----------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec1/Ior | -13dB | 1. Total P-CPICH_Ec/Ior = -10dB | +| P-CPICH (antenna 2) | P-CPICH_Ec2/Ior | -13dB | | +| P-CCPCH (antenna 1) | P-CCPCH_Ec1/Ior | -15dB | 1. STTD applied.
2. Total P-CCPCH Ec/Ior is -12dB. | +| P-CCPCH (antenna 2) | P-CCPCH_Ec2/Ior | -15dB | | +| SCH (antenna 1/2) | SCH_Ec/Ior | -12dB | 1. TSTD applied.
2. Power divided equally between primary and secondary SCH. | +| PICH (antenna 1) | PICH_Ec1/Ior | -18dB | 1. STTD applied.
2. Total PICH Ec/Ior is -15dB. | +| PICH (antenna 2) | PICH_Ec2/Ior | -18dB | | +| DPCH | DPCH_Ec/Ior | Test-specific | 1. CL1 applied. | +| HS-SCCH-1 | HS-SCCH_Ec/Ior | Test-specific | 1. STTD applied.
2. Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/Ior | DTX'd | 1. UE assumes STTD applied.
2. No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/Ior | DTX'd | 1. As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/Ior | DTX'd | 2. As HS-SCCH-2. | +| HS-PDSCH | HS-PDSCH_Ec/Ior | Test-specific | 1. CL1 applied. | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one (Note 1) | 1. Balance of power $I_{or}$ of the Node-B is assigned to OCNS.
2. Power divided equally between antennas.
3. OCNS interference consists of 6 dedicated data channels as specified in table C.13. | + +Note 1: For the case of DPCH with transmit diversity, the OCNS power calculation shall be based on the addition of the power from Antenna 1 and Antenna 2, i.e. disregarding any phase relationship between the antennas. + +**Table C.11: Downlink physical channels for HSDPA receiver testing for HS-SCCH detection performance** + +| Parameter | Units | Value | Comment | +|-------------------------|-------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CPICH $E_c/I_{or}$ | dB | -10 | | +| P-CCPCH $E_c/I_{or}$ | dB | -12 | Mean power level is shared with SCH. | +| SCH $E_c/I_{or}$ | dB | -12 | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
P-SCH code is $S\_dl,0$ as per TS25.213
S-SCH pattern is scrambling code group 0 | +| PICH $E_c/I_{or}$ | dB | -15 | | +| HS-PDSCH-1 $E_c/I_{or}$ | dB | -10 | HS-PDSCH associated with HS-SCCH-1. The HS-PDSCH shall be transmitted continuously with constant power. | +| HS-PDSCH-2 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-2 | +| HS-PDSCH-3 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-3 | +| HS-PDSCH-4 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-4 | +| DPCH $E_c/I_{or}$ | dB | -8 | 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 $E_c/I_{or}$ | dB | Test Specific | All HS-SCCH's allocated equal $E_c/I_{or}$ .
Specifies $E_c/I_{or}$ when TTI is active. | +| HS-SCCH-2 $E_c/I_{or}$ | dB | | | +| HS-SCCH-3 $E_c/I_{or}$ | dB | | | +| HS-SCCH-4 $E_c/I_{or}$ | dB | | | +| OCNS $E_c/I_{or}$ | dB | Necessary power so that total transmit power spectral density of Node B ( $I_{or}$ ) adds to one (Note 1) | 1. Balance of power $I_{or}$ of the Node-B is assigned to OCNS.
2. OCNS interference consists of 6 dedicated data channels as specified in table C.13. | + +Note 1: For the case of DPCH with transmit diversity, the OCNS power calculation shall be based on the addition of the power from Antenna 1 and Antenna 2, i.e. disregarding any phase relationship between the antennas. + +**Table C.12: Downlink physical channels for HSDPA receiver testing for HS-SCCH detection performance in Open Loop Diversity** + +| Parameter | Units | Value | Comment | +|----------------------------------|-------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH $E_c/I_{or}$ (antenna 1) | dB | -13 | 1. Total P-CPICH $E_c/I_{or} = -10\text{dB}$ | +| P-CPICH $E_c/I_{or}$ (antenna 2) | dB | -13 | | +| P-CCPCH $E_c/I_{or}$ (antenna 1) | dB | -15 | 1. STTD applied
2. Total P-CCPCH $E_c/I_{or} = -12\text{dB}$ | +| P-CCPCH $E_c/I_{or}$ (antenna 2) | dB | -15 | | +| SCH $E_c/I_{or}$ (antenna ½) | dB | -12 | 1. TSTD applied
2. Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
3. P-SCH code is S_dl,0 as per TS25.213
4. S-SCH pattern is scrambling code group 0 | +| PICH $E_c/I_{or}$ (antenna 1) | dB | -15 | 1. STTD applied
2. Total PICH $E_c/I_{or} = -12\text{dB}$ | +| PICH $E_c/I_{or}$ (antenna 2) | dB | -15 | | +| HS-PDSCH-1 $E_c/I_{or}$ | dB | -10 | 1. STTD applied
2. HS-PDSCH assoc. with HS-SCCH-1 | +| HS-PDSCH-2 $E_c/I_{or}$ | dB | DTX | 1. STTD applied
2. HS-PDSCH assoc. with HS-SCCH-2 | +| HS-PDSCH-3 $E_c/I_{or}$ | dB | DTX | 1. STTD applied
2. HS-PDSCH assoc. with HS-SCCH-3 | +| HS-PDSCH-4 $E_c/I_{or}$ | dB | DTX | 1. STTD applied
2. HS-PDSCH assoc. with HS-SCCH-4 | +| DPCH $E_c/I_{or}$ | dB | -8 | 1. STTD applied
2. 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 $E_c/I_{or}$ | dB | Test Specific | 1. STTD applied
2. All HS-SCCH's allocated equal $E_c/I_{or}$ .
3. Specifies $E_c/I_{or}$ when TTI is active. | +| HS-SCCH-2 $E_c/I_{or}$ | dB | | | +| HS-SCCH-3 $E_c/I_{or}$ | dB | | | +| HS-SCCH-4 $E_c/I_{or}$ | dB | | | +| OCNS $E_c/I_{or}$ | dB | Remaining power at Node-B (including HS-SCCH power allocation when HS-SCCH's inactive). | 1. STTD applied
2. OCNS interference consists of 6 dedicated data channels as specified in table C.13.
3. Power divided equally between antennas | + +**Table C.12A: Downlink physical channels for HSDPA receiver testing for HS-DSCH reception in CELL\_FACH state.** + +| Physical Channel | Parameter | Value | Note | +|------------------|-----------------|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/lor | -10dB | | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | Mean power level is shared with SCH. | +| SCH | SCH_Ec/lor | -12dB | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
P-SCH code is S_dl,0 as per TS25.213
S-SCH pattern is scrambling code group 0 | +| PICH | PICH_Ec/lor | -15dB | | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | . | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one | OCNS interference consists of a number of dedicated data channels as specified in table C.13. | + +**Table C.12B: Downlink physical channels for HSDPA receiver testing for HS-SCCH reception in CELL\_FACH state.** + +| Parameter | Units | Value | Comment | +|-------------------------|-------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CPICH $E_c/I_{or}$ | dB | -10 | | +| P-CCPCH $E_c/I_{or}$ | dB | -12 | Mean power level is shared with SCH. | +| SCH $E_c/I_{or}$ | dB | -12 | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
P-SCH code is $S\_dl,0$ as per TS25.213
S-SCH pattern is scrambling code group 0 | +| PICH $E_c/I_{or}$ | dB | -15 | | +| HS-PDSCH-1 $E_c/I_{or}$ | dB | -3 | HS-PDSCH associated with HS-SCCH-1. The HS-PDSCH shall be transmitted continuously with constant power. | +| HS-PDSCH-2 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-2 | +| HS-PDSCH-3 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-3 | +| HS-PDSCH-4 $E_c/I_{or}$ | dB | DTX | HS-PDSCH associated with HS-SCCH-4 | +| HS-SCCH-1 $E_c/I_{or}$ | dB | Test Specific | All HS-SCCH's allocated equal $E_c/I_{or}$ .
Specifies $E_c/I_{or}$ when TTI is active. | +| HS-SCCH-2 $E_c/I_{or}$ | dB | | | +| HS-SCCH-3 $E_c/I_{or}$ | dB | DTX | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-4 $E_c/I_{or}$ | dB | | | +| OCNS $E_c/I_{or}$ | dB | Necessary power so that total transmit power spectral density of Node B ( $I_{or}$ ) adds to one (Note 1) | 1. Balance of power $I_{or}$ of the Node-B is assigned to OCNS.
2. OCNS interference consists of 6 dedicated data channels as specified in table C.13. | + +**Table C.12C: Downlink physical channels for DC-HSDPA/DB-DC-HSDPA/4C-HSDPA Reference Measurement Channel testing** + +| Physical Channel | Parameter | Value | Note | +|------------------|-----------------|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/lor | -10dB | | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | Mean power level is shared with SCH. | +| SCH | SCH_Ec/lor | -12dB | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both.
P-SCH code is S_dl,0 as per TS25.213
S-SCH pattern is scrambling code group 0 | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | - 5 dB unless test-specific value is specified,

only for serving HS-DSCH cell, omitted otherwise | 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 | HS-SCCH_Ec/lor | -9dB unless test-specific value is specified | Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | . | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one | OCNS interference consists of a number of dedicated data channels as specified in table C.13 and C. 13A. Table C.13 specifies the OCNS setup for H-Set 1 to H-Set 6 and H-Set 12. Table C.13A specifies the OCNS setup for H-Set 8 and H-set 10. | + +**Table C.12D: Downlink physical channels for HSDPA/DC-HSDPA/DB-DC-HSDPA/4C-HSDPA receiver testing for MIMO performance with asymmetric P-CPICH/S-CPICH power settings.** + +| Physical Channel | Parameter | Value | Note | +|---------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec/lor | -10dB | Phase reference | +| S-CPICH (antenna 2) | S-CPICH Ec/lor | -13dB | Phase reference | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | | +| SCH | SCH_Ec/lor | -12dB | | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | Test-specific | | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present in HSDPA configuration. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | Precoding used. | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one |
  1. Balance of power I_{or} of the Node-B is assigned to OCNS.
  2. OCNS interference consists of a number of dedicated data channels as specified in Table C.13 and C.13A. Table C.13 specifies the OCNS setup for H-Set 1 to H-set 6. Table C.13A specifies the OCNS setup for H-Set 9 and H-Set 11.
  3. OCNS transmitted only on antenna 1.
| +| Note: | Transmit diversity (STTD or TSTD) is disabled on the associated physical channels (P-CPICH, PICH, SCH, HS-SCCH, DPCH). | | | + +**Table C.12E: Downlink physical channels for HSDPA receiver testing for HS-SCCH detection performance with asymmetric P-CPICH/S-CPICH power settings.** + +| Physical Channel | Parameter | Value | Note | +|---------------------------|-----------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec/Ior | -10dB | Phase reference | +| S-CPICH (antenna 2) | S-CPICH Ec/Ior | -13dB | Phase reference | +| P-CCPCH | P-CCPCH_Ec/Ior | -12dB | | +| SCH | SCH_Ec/Ior | -12dB | | +| PICH | PICH_Ec/Ior | -15dB | | +| DPCH | DPCH_Ec/Ior | -8dB | 1. STTD applicability is test-specific.
2. 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 | HS-SCCH_Ec/Ior | Test-specific | 1. STTD applicability is test specific.
2. Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval).
2. All HS-SCCH's allocated equal $E_c / I_{or}$ .
3. Specifies $E_c / I_{or}$ when TTI is active. | +| HS-SCCH-2 | HS-SCCH_Ec/Ior | | | +| HS-SCCH-3 | HS-SCCH_Ec/Ior | | | +| HS-SCCH-4 | HS-SCCH_Ec/Ior | | | +| HS-PDSCH-1 $E_c / I_{or}$ | HS-PDSCH_Ec/Ior | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | 1. Precoding used.
2. Balance of power $I_{or}$ of the Node-B is assigned to HS-PDSCH. | +| HS-PDSCH-2 $E_c / I_{or}$ | HS-PDSCH_Ec/Ior | DTX | | +| HS-PDSCH-3 $E_c / I_{or}$ | HS-PDSCH_Ec/Ior | DTX | | +| HS-PDSCH-4 $E_c / I_{or}$ | HS-PDSCH_Ec/Ior | DTX | | +| OCNS | | DTX | | + +Note 1: Transmit diversity (STTD or TSTD) is disabled on P-CCPCH, PICH and SCH. + +Note 2: OCNS is not present for this test. HS-PDSCH is used in order to model other UE MIMO traffic. + +**Table C.12F: Downlink physical channels for HSDPA/DC-HSDPA/DB-DC-HSDPA/4C-HSDPA receiver testing for MIMO mode with four transmit antennas performance with asymmetric P-CPICH/S-CPICH power settings.** + +| Physical Channel | Parameter | Value | Note | +|---------------------|-----------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec/lor | -10dB | Phase reference | +| S-CPICH (antenna 2) | S-CPICH Ec/lor | -13dB | Phase reference | +| S-CPICH (antenna 3) | S-CPICH Ec/lor | -19dB | Phase reference | +| S-CPICH (antenna 4) | S-CPICH Ec/lor | -19dB | Phase reference | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | | +| SCH | SCH_Ec/lor | -12dB | | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | Test-specific | | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval). | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-SCCH-4 | HS-SCCH_Ec/lor | | Not configured | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | Precoding used. | +| OCNS | | Necessary power so that total transmit power spectral density of Node B (lor) adds to one |
  1. Balance of power I_{or} of the Node-B is assigned to OCNS.
  2. OCNS interference consists of a number of dedicated data channels as specified in Table C.13B.
  3. OCNS transmitted only on antenna 1.
| + +Note 1: Transmit diversity (STTD or TSTD) is disabled on the associated physical channels (P-CPICH, PICH, SCH, HS-SCCH, DPCH). + +**Table C.12G: Downlink physical channels for HSDPA receiver testing for HS-SCCH type 4 detection performance with asymmetric P-CPICH/S-CPICH power settings.** + +| Physical Channel | Parameter | Value | Note | +|---------------------------|-----------------|-------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-CPICH (antenna 1) | P-CPICH_Ec/lor | -10dB | Phase reference | +| S-CPICH (antenna 2) | S-CPICH Ec/lor | -13dB | Phase reference | +| S-CPICH (antenna 3) | S-CPICH Ec/lor | -19dB | Phase reference | +| S-CPICH (antenna 4) | S-CPICH Ec/lor | -19dB | Phase reference | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | | +| SCH | SCH_Ec/lor | -12dB | | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | -8dB | 1. STTD disabled
2. 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 | HS-SCCH_Ec/lor | Test-specific | 1. Specifies fraction of Node-B radiated power transmitted when TTI is active (i.e. due to minimum inter-TTI interval).
2. All HS-SCCH's allocated equal $E_c / I_{or}$ .
3. Specifies $E_c / I_{or}$ when TTI is active. | +| HS-SCCH-2 | HS-SCCH_Ec/lor | | | +| HS-SCCH-3 | HS-SCCH_Ec/lor | | | +| HS-SCCH-4 | HS-SCCH_Ec/lor | | | +| HS-PDSCH-1 $E_c / I_{or}$ | HS-PDSCH_Ec/lor | Necessary power so that total transmit power spectral density of Node B (lor) adds to one | 1. Precoding used.
2. Balance of power $I_{or}$ of the Node-B is assigned to HS-PDSCH. | +| HS-PDSCH-2 $E_c / I_{or}$ | HS-PDSCH_Ec/lor | DTX | | +| HS-PDSCH-3 $E_c / I_{or}$ | HS-PDSCH_Ec/lor | DTX | | +| HS-PDSCH-4 $E_c / I_{or}$ | HS-PDSCH_Ec/lor | DTX | | +| OCNS | | DTX | | + +Note 1: Transmit diversity (STTD or TSTD) is disabled on P-CCPCH, PICH and SCH. + +Note 2: OCNS is not present for this test. HS-PDSCH is used in order to model other UE MIMO traffic. + +## C.5.2 OCNS Definition + +The selected channelization codes and relative power levels for OCNS transmission during for HSDPA performance assessment for other than enhanced performance type 3i are defined in Table C.13. The selected codes are designed to have a single length-16 parent code. The test definition for the enhanced performance type 3i is defined in section C.5.3. + +**Table C.13: OCNS definition for HSDPA receiver testing.** + +| Channelization Code at SF=128 | Relative Level setting (dB) (Note 1) | DPCH Data | +|-------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 122 | 0 | The DPCH data for each channelization code shall be uncorrelated with each other and with any wanted signal over the period of any measurement. For OCNS with transmit diversity the DPCH data sent to each antenna shall be either STTD encoded or generated from uncorrelated sources. | +| 123 | -2 | | +| 124 | -2 | | +| 125 | -4 | | +| 126 | -1 | | +| 127 | -3 | | + +**Table C.13A: OCNS definition for HSDPA receiver testing, FRC H-Set 8, H-Set 9, H-Set 10 and H-Set 11.** + +| Channelization Code at SF=128 | Relative Level setting (dB) (Note 1) | DPCH Data | +|-------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 | 0 | The DPCH data for each channelization code shall be uncorrelated with each other and with any wanted signal over the period of any measurement. For OCNS with transmit diversity the DPCH data sent to each antenna shall be either STTD encoded or generated from uncorrelated sources. | +| 5 | -2 | | +| 6 | -4 | | +| 7 | -1 | | + +**Table C.13B: OCNS definition for HSDPA receiver testing, FRC H-Set 13 and H-Set 14.** + +| Channelization Code at SF=128 | DPCH Data | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | For OCNS with transmit diversity the DPCH data sent to each antenna shall be either STTD encoded or generated from uncorrelated sources. | + +Note 1: The relative level setting specified in dB refers only to the relationship between the OCNS channels. The level of the OCNS channels relative to the Ior of the complete signal is a function of the power of the other channels in the signal with the intention that the power of the group of OCNS channels is used to make the total signal add up to 1. + +### C.5.3 Test Definition for Enhanced Performance Type 3i + +This section defines additional test definition for enhanced performance type 3i including: number of interfering cells and their respective powers; transmitted code and power characteristics (OCNS) for serving and interfering cells; and frame offsets for interfering cells. For DC-HSDPA, DB-DC-HSDPA and 4C-HSDPA requirements, the number of interfering cells and their respective powers; transmitted code and power characteristics (OCNS) for serving and interfering cells; and frame offsets for interfering cells shall be the same for each carrier frequency. The transmitted OCNS and data signals shall be independent for each cell. + +DIPi = where $\hat{I}_{orj}$ is the average received power spectral density from the *j*-th strongest interfering cell ( $\hat{I}_{or1}$ is assumed to be the power spectral density associated with the serving cell), and Ioc' is given by where Ioc' is the average power spectral density of a band limited white noise source consistent with the definition provided in section 3.2. + +### C.5.3.1 Transmitted code and power characteristics for serving cell + +The downlink physical channel code allocations for the serving cell are specified in Table C.14. Ten HS-PDSCH codes have been reserved for the user of interest, based upon the use of QPSK with FRC H-Set 6. The other user codes are selected from 46 possible SF = 128 codes. Note not all 46 of these codes are used, and in addition only 16 codes are used at a given instance in time. Table C.15 summarizes the power allocations of different channels for the serving cell for 50% and 25% HS-PDSCH power allocation. Note the power allocations in the last row of Table C.15 are to be split between the HS-SCCH and the other users' channels in order to ensure proper operation of the HS-SCCH during testing. + +Table C.16 summarizes the channelization codes to be used for the other users channels (OCNS) along with their respective relative power allocations in dB when HS-PDSCH is allocated 25% or 50% of the total power. As shown in Table C.16, there are two groups of 16 codes, which are randomly selected with equal probability on a symbol-by-symbol basis. This random selection is done per code pair, where a code pair occupies the same row, as opposed to selecting all of the codes within group 1 or group 2. This random selection between these two groups is for purposes of modelling a simplified form of DTX. Note that the switching time for the symbols with SF = 64 would be the symbol timing associated with an SF 64 channel, and the switching time for the symbols with SF = 128 would be the symbol timing for SF = 128 channel. Thus, there would be two different symbol times dependent upon the SF. For SF = 64, symbol time ~ 16.67 microseconds, and for SF = 128, symbol time ~ 33.33 microseconds. Each of these users is also power controlled as described in section C.5.3.3. + +The scrambling code of the serving cell is set to 0. + +**Table C.14. Downlink physical channel code allocation.** + +| Channelization Code at SF=128 | Note | +|-------------------------------|-------------------------------------| +| 0 | P-CPICH, P-CCPCH and PICH on SF=256 | +| 1 | | +| 2...7 | 6 SF=128 codes free for OCNS | +| 8...87 | 10 HS-PDSCH codes at SF=16 | +| 88...127 | 40 SF=128 codes free for OCNS | + +**Table C.15. Summary of modelling approach for the serving cell.** + +| | Serving cell | | +|--------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------| +| Common channels | 0.195 (-7.1dB)
As specified in Table C.8 | | +| HS-PDSCH transport format | H-Set 6 | | +| HS-PDSCH power allocation [ $E_c/I_{or}$ ] | 0.5
(-3 dB) | 0.25
(-6 dB) | +| HS-SCCH + Other users' channels (OCNS) | 0.3049
(-5.16 dB)
Other users' channels set according to Table C.16 | 0.5551
(-2.56 dB)
Other users' channels set according to Table C.16 | + +Note: The values given in decibel are only for information. + +**Table C.16. Channelization codes and relative power levels for 25% and 50% HS-PDSCH power allocations.** + +| Group 1
Channelization Code,
Cch, SF.k | Group 2
Channelization Code,
Cch, SF. k | Relative level
setting for 25%
and 50% | +|------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------| +| C ch,128,2 | C ch,128,108 | -1.7 | +| C ch,128,3 | C ch,128,103 | -2.7 | +| C ch,128,5 | C ch,128,109 | -3.5 | +| C ch,128,6 | C ch,128,118 | -0.8 | +| C ch,128,90 | C ch,128,4 | -6.2 | +| C ch,128,94 | C ch,128,123 | -4.6 | +| C ch,128,96 | C ch,128,111 | -2.3 | +| C ch,128,98 | C ch,128,106 | -4.1 | +| C ch,128,99 | C ch,128,100 | -3.1 | +| C ch,128,101 | C ch,128,113 | -5.1 | +| C ch,64,52 | C ch,64,44 | 0.0 | +| C ch,128,110 | C ch,128,124 | -4.6 | +| C ch,128,114 | C ch,128,115 | -4.8 | +| C ch,128,116 | C ch,128,126 | -4.8 | +| C ch,64,60 | C ch,64,46 | -1.1 | +| C ch,128,125 | C ch,128,95 | -4.1 | + +Note: The relative level settings specified in dB refer only to the relationship between the OCNS channels. For the serving cell, the sum of the powers of the OCNS channels plus the power allocated to the HS-SCCH must add up to the values specified in the last row of Table C.15. For the interfering cells, the sum of the powers of the OCNS channels must add up to the value shown in the last row of Table C.17. + +### C.5.3.2 Transmitted code and power characteristics for interfering cells + +The downlink physical channel code allocations for the interfering cells are same as for the serving cell as given in Table C.14. The modelling approach for the interfering cells is summarized in Table C.17. The modelling of the other users' dedicated channels is done in the same way as in the case of the serving cell except that the HSDPA power allocation is fixed at 50% and the total power allocated is not shared with the HS-SCCH. Thus, the two groups of channelization codes defined in Table C.16 apply, along with the specified relative power levels. + +**Table C.17. Summary of modelling approach for the interfering cells.** + +| | Interfering cell(s) | +|--------------------------------------------|------------------------------------------------------------------------------------------| +| Common channels | 0.195 (-7.1dB)
As specified in Table C.8 | +| HS-PDSCH transport format | Selected randomly from Table C.18
Independent for each interferer. | +| HS-PDSCH power allocation [ $E_c/I_{or}$ ] | 0.5
(-3 dB) | +| Other users' channels | 0.3049
(-5.16 dB)
Set according to Table C.16 for 50%
HS-PDSCH power allocation | + +Note: The values given in decibel are only for information. + +The HS-PDSCH transmission for interfering cells is modelled to have randomly varying modulation and number of codes. The predefined modulation and number of codes are given in Table C.18, with the actual codes selected per the code allocation given in Table C.14. The transmission from each interfering cell is randomly and independently selected every HSDPA TTI among the four options given in Table C.18. + +The scrambling codes of the interfering cells are set to 16 and 32, respectively. The frame offsets for the interfering cells are set to 1296 and 2576 chips relative to the serving cell. The scrambling code value of 16 and the frame offset value of 2576 corresponds to the first interfering cell. + +**Table C.18. Predefined interferer transmission.** + +| # | Used modulation and number of HS-PDSCH codes | +|---|----------------------------------------------| +| 1 | QPSK with 5 codes | +| 2 | 16QAM with 5 codes | +| 3 | QPSK with 10 codes | +| 4 | 16QAM, with 10 codes | + +### C.5.3.3 Model for power control sequence generation + +In this section the modelling of power control for the other users' channels is described. There are two powers that are calculated for each user, $I$ at each slot, $n$ . The first is an interim power calculation, which develops a power in dB. The second is the actual applied transmit power, in the linear domain, which is normalized such that the total power for all users remains the same as that originally allocated. The interim power calculation is described first followed by the applied, normalized power calculation. + +The interim power is varied randomly, either by increasing or decreasing it by 1 dB steps in each slot, i.e. + +$$P_{lin,n}^i = P_{lin,n-1}^i + \Delta, \text{ where } \Delta \in \{-1, +1\} \quad (\text{EQ.C.5.3.3.1})$$ + +The probability of $\Delta$ having a value of +1 for the $i^{\text{th}}$ user at time instant $n$ can be determined as + +$$P(\Delta = +1) = \frac{1}{2} \quad (\text{EQ.C.5.3.3.2})$$ + +where, $P_{lin,n-1}^i$ is the interim power at time instant $n-1$ and $P_{lin,0}^i$ is the initial value given in Table C.16 after conversion to dB for each of the two possible HS-PDSCH power allocations. $L$ is a scaling factor which can be used to determine the range to which the variation of power is confined. The value of $L$ is set to 10, leading to a variance of $\sim 5$ dB. + +The applied, normalized power is given by + +$$P_{lin,n}^i = \frac{P_{lin,n}^i}{\sum_{i=1}^{16} P_{lin,n}^i} \quad (\text{EQ.C.5.3.3.3})$$ + +where $P_{lin,n}^i$ is the interim power of the user $I$ at time instant $n$ in the linear domain, and $P_{lin,0}^i$ is the initial value of the $i^{\text{th}}$ user's power also in the linear domain. Each summation is over all 16 possible values for $P_{lin,n}^i$ and $P_{lin,0}^i$ where the latter summation is equal to either 0.5551 or 0.3049 for HS-PDSCH allocations of 25% and 50%, respectively, see Table C.16. The total instantaneous output power of the OCNS is now always equal to its allocated power. One other subtle point to note is that at each iteration of interim power generation using (EQ.C.5.3.3.1) that the value of $P_{lin,n}^i$ is set to of the previous iteration as opposed to of the previous iteration. In summary, two sets of power control sequences are developed using (EQ.C.5.3.3.1) and (EQ.C.5.3.3.3), respectively, where the interim outputs developed by (C.1) are used to develop the applied, normalized values described by (EQ.C.5.3.3.3) and to which the actual channel powers are set. + +## C.5.4 Simplified Multi Carrier HSDPA testing method + +For DC-HSDPA, DB-DC-HSDPA or 4C-HSDPA tests which require more than 8 independent faders, the resulting propagation channel(s) shall be generated by considering a number of independent faders needed for one carrier and connecting them to the signal of randomly chosen carrier(s). The maximum number of channel faders on the test will be less than or equal to 8. The remaining carrier(s) shall be connected without a channel fader but with AWGN. The throughput shall be collected only for the carrier(s) connected to channel faders. + +The test shall be repeated by choosing carrier(s) excluding already chosen carrier(s) until all the carrier(s) are tested under fading conditions. The sum of all the collected throughputs from each carrier shall be compared against the reference value in the requirements. + +All supported carriers shall be configured and activated during the test. + +### C.5.4A Simplified Multiflow HSDPA testing method + +For Multiflow HSDPA tests which require more than 8 independent faders, the resulting propagation channel(s) shall be generated by considering a number of independent faders needed for one carrier frequency and connecting them to the signal of randomly chosen carrier(s). The maximum number of channel faders on the test will be less than or equal to 8. The remaining carrier(s) shall be connected without a channel fader but with AWGN. The throughput shall be collected only for the carrier(s) connected to channel faders. + +The test shall be repeated by choosing carrier(s) excluding already chosen carrier(s) until all the carrier(s) are tested under fading conditions. + +All supported carriers shall be configured and activated during the test. + +## C.5.5 Test Definition for Multiflow HSDPA + +This section defines additional test configuration for Multiflow HSDPA including: number of cells and their respective powers; transmitted code and power characteristics (OCNS) for the interfering cell; and frame offsets for assisting serving HS-DSCH cell and interfering cell. + +### C.5.5.1 Test configuration when 2 cells are configured in Multiflow mode + +The relative powers for the serving HS-DSCH cell (Cell 1), the assisting serving HS-DSCH cell (Cell 2) and additional interfering cell (Cell 3, if present) are shown in Table C.19. The scrambling code of the serving HS-DSCH cell is set to 0, that of the assisting serving HS-DSCH cell is set to 16, and that of the interfering cell is set to 32. The frame offsets of the assisting serving HS-DSCH cell is set to 2560 chips and that of the interfering cell is set to 1296 chips relative to the serving HS-DSCH cell. The downlink physical channel setup for the serving HS-DSCH cell and assisting serving HS-DSCH cell is shown in Table C.20 and Table C.21 respectively. The downlink physical channel setup for the additional interfering cell is shown in Table C.22. + +**Table C.19: Relative power of the cells in Multiflow HSDPA test** + +| Number of additional interfering cell | $\hat{I}_{or1}/I_{loc}$ | $\hat{I}_{or2}/I_{loc}$ | $\hat{I}_{or3}/I_{loc}$ | Cell 1 Geometry | Cell 2 Geometry | +|---------------------------------------|-------------------------|-------------------------|-------------------------|-----------------|-----------------| +| 0 | 7.01 | 3.61 | -inf | 1.83 | -4.19 | +| 1 | 5.27 | 2.52 | -2.37 | 0.00 | -4.42 | + +Notes: 1) Cell 1 corresponds to the serving HS-DSCH cell, Cell 2 corresponds to the assisting serving HS-DSCH cell, and Cell 3 is the additional interfering cell. + +2) Cell 1 Geometry is defined by $\hat{I}_{or1}/I_{loc,1}'$ , where $I_{loc,1}' = (I_{loc} + \hat{I}_{or2} + \hat{I}_{or3})$ . + +3) Cell 2 Geometry is defined by $\hat{I}_{or2}/I_{loc,2}'$ , where $I_{loc,2}' = (I_{loc} + \hat{I}_{or1} + \hat{I}_{or3})$ . + +**Table C.20: Downlink physical channels for the serving/secondary serving HS-DSCH cell in HSDPA receiver testing of Multiflow HSDPA** + +| Physical Channel | Parameter | Value | Note | +|------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/lor | -10dB | | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | Mean power level is shared with SCH. | +| SCH | SCH_Ec/lor | -12dB | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both. | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | Necessary power so that total transmit power spectral density of Node B (lor) adds to one

Only for serving HS-DSCH cell, omitted otherwise | 12.2 kbps DL reference measurement channel as defined in Annex A.3.1 | +| HS-SCCH-1 | HS-SCCH_Ec/lor | -8 dB for serving HS-DSCH cell, otherwise necessary power so that total transmit power spectral density of Node B (lor) adds to one | | +| HS-SCCH-2 | HS-SCCH_Ec/lor | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/lor | DTX'd | As HS-SCCH-2. | +| HS-PDSCH | HS-PDSCH_Ec/lor | Test-specific | | + +**Table C.21: Downlink physical channels for the assisting serving/secondary serving HS-DSCH cell in HSDPA receiver testing of Multiflow HSDPA** + +| Physical Channel | Parameter | Value | Note | +|------------------|----------------|-------|-----------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/lor | -10dB | | +| P-CCPCH | P-CCPCH_Ec/lor | -12dB | Mean power level is shared with SCH. | +| SCH | SCH_Ec/lor | -12dB | Mean power level is shared with P-CCPCH – SCH includes P- and S-SCH, with power split between both. | +| PICH | PICH_Ec/lor | -15dB | | +| DPCH | DPCH_Ec/lor | DTX'd | Omitted | + +| | | | | +|-----------|-----------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| HS-SCCH-1 | HS-SCCH_Ec/Ior | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | | +| HS-SCCH-2 | HS-SCCH_Ec/Ior | DTX'd | No signalling scheduled, or power radiated, on this HS-SCCH, but signalled to the UE as present. | +| HS-SCCH-3 | HS-SCCH_Ec/Ior | DTX'd | As HS-SCCH-2. | +| HS-PDSCH | HS-PDSCH_Ec/Ior | Test-specific | | + +**Table C.22: Downlink physical channels for the additional interfering cell in Multiflow HSDPA testing** + +| | Interfering cell | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Common channels | 0.195 (-7.1dB)
Same as Table C.20 | +| HS-SCCH_Ec/Ior | -12 dB | +| HS-PDSCH transport format | Selected randomly from Table C.18 | +| HS-PDSCH power allocation
[E c /I or ] | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | + +### C.5.5.2 Test configuration when 3 cells are configured in Multiflow mode + +When 3 cells are configured in Multiflow mode, the test configuration in C.5.5.1 shall be duplicated for each frequency according to Table C.20 and Table C.21. The downlink physical channel setup for the serving HS-DSCH cell, assisting serving HS-DSCH cell and the secondary serving HS-DSCH cell is shown in Table C.23. Cell 2 on the carrier of the secondary serving HS-DSCH cell becomes an interfering cell and does not participate in Multiflow mode. The downlink physical channel setup of Cell 2 on the carrier of the secondary serving HS-DSCH cell shall follow Table C.21. + +**Table C.23: Test configuration when 3 cells are configured in Multiflow mode** + +| | Setting | +|--------------------------------|-------------------------| +| Serving HS-DSCH cell | According to Table C.20 | +| Assisting serving HS-DSCH cell | According to Table C.21 | +| Secondary serving HS-DSCH cell | According to Table C.20 | + +### C.5.5.3 Test configuration when 4 cells are configured in Multiflow mode + +When 4 cells are configured in Multiflow mode on 2 frequencies, the test configuration in C.5.5.1 shall be duplicated for each frequency according to Table C.20 and Table C.21. The downlink physical channel setup for the serving HS- + +DSCH cell, assisting serving HS-DSCH cell, the secondary serving HS-DSCH cell and the assisting secondary serving HS-DSCH cell is shown in Table C.24. + +**Table C.24: Test configuration when 4 cells are configured in Multiflow mode** + +| | Setting | +|------------------------------------------|-------------------------| +| Serving HS-DSCH cell | According to Table C.20 | +| Assisting serving HS-DSCH cell | According to Table C.21 | +| Secondary serving HS-DSCH cell | According to Table C.20 | +| Assisting secondary serving HS-DSCH cell | According to Table C.21 | + +When 4 cells are configured in Multiflow mode on 3 frequencies, the test configuration in C.5.5.1 shall be duplicated for each frequency according to Table C.20 and Table C.21. The downlink physical channel setup for the serving HS-DSCH cell, assisting serving HS-DSCH cell, the 1st secondary serving HS-DSCH cell and the 2nd secondary serving HS-DSCH cell is shown in Table C.24a. + +**Table C.24a: Test configuration when 4 cells are configured in Multiflow mode** + +| | Setting | +|------------------------------------|-------------------------| +| Serving HS-DSCH cell | According to Table C.20 | +| Assisting serving HS-DSCH cell | According to Table C.21 | +| 1st secondary serving HS-DSCH cell | According to Table C.20 | +| 2nd secondary serving HS-DSCH cell | According to Table C.20 | + +## C.6 MBMS DL Physical channels + +### C.6.1 Downlink Physical Channels connection set-up + +Table C.14 is applicable for measurements on the Performance requirements in Clause 11. + +**Table C.14: Downlink Physical Channels on each radiolink** + +| Physical Channel | Power ratio | NOTE | +|------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH_Ec/Ior = -10 dB | Only P-CPICH is used as phase reference for S-CCPCH carrying MCCH or MTCH. | +| P-CCPCH | P-CCPCH_Ec/Ior = -12 dB | | +| SCH | SCH_Ec/Ior = -12 dB | This power shall be divided equally between Primary and Secondary Synchronous channels | +| PICH | PICH_Ec/Ior = -15 dB | | +| S-CCPCH | S-CCPCH_Ec/Ior = test dependent | | +| DPCH | TBD | DPCH is enable only when UE has capability to receive MBMS in CELL_DCH state | +| OCNS | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | OCNS interference consists of 16 dedicated data channels as specified in table C.6. | + +## C.6.2 Downlink Physical Channels connection set-up for MBSFN + +**Table C.14a: Downlink Physical Channels for performance requirements** + +| Physical Channel | Power ratio | NOTE | +|------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| P-CPICH | $P\text{-CPICH\_Ec/Ior} = -10 \text{ dB}$ | Only P-CPICH is used as phase reference for S-CCPCH carrying MCCH or MTCH. | +| P-CCPCH | $P\text{-CCPCH\_Ec/Ior} = -12 \text{ dB}$ | | +| SCH | $SCH\_Ec/Ior = -12 \text{ dB}$ | This power shall be divided equally between Primary and Secondary Synchronous channels | +| S-CCPCH | $S\text{-CCPCH\_Ec/Ior} = \text{test dependent}$ | | +| OCNS | Necessary power so that total transmit power spectral density of Node B (Ior) adds to one | Same code channels as used for DPCH, see table C.6 | + +## Annex D (normative) : Environmental conditions + +### D.1 General + +This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled. + +### D.2 Environmental requirements + +The requirements in this clause apply to all types of UE(s). + +#### D.2.1 Temperature + +The UE shall fulfil all the requirements in the full temperature range of: + +**Table D.1** + +| | | +|----------------|-----------------------------------------------------------------| +| +15°C to +35°C | for normal conditions (with relative humidity of 25 % to 75 %) | +| -10°C to +55°C | for extreme conditions (see IEC publications 68-2-1 and 68-2-2) | + +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 TS 25.101 for extreme operation. + +#### D.2.2 Voltage + +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 D.2** + +| 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 | +| Non regulated batteries: | | | | +| Leclanché | 0,85 * nominal | Nominal | Nominal | +| Lithium | 0,95 * nominal | 1,1 * nominal | 1,1 * nominal | +| Mercury/nickel & cadmium | 0,90 * nominal | 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 25.101 for extreme operation. In particular, the UE shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shutdown voltage. + +## D.2.3 Vibration + +The UE shall fulfil all the requirements when vibrated at the following frequency/amplitudes. + +**Table D.3** + +| 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 25.101 for extreme operation + +--- + +## Annex E (informative): UARFCN numbers + +### E.1 General + +This Annex lists the UARFCN numbers used for the frequency bands implemented in the current specification. + +--- + +### E.2 List of UARFCN used for UTRA FDD bands + +The UARFCN numbering scheme detailed in clauses 5.4.3 and 5.4.4 of this specification is summarized for information in Table E.1. The table shows the UARFCN assigned to all UTRA FDD operating bands, starting with the lowest UARFCN and continuing up to the highest one assigned. + +Each band may have two table entries, one for the “general” numbers and one for the “additional” ones, as specified in Table 5.2. The entries in Table E.1 are explained as follows: + +**Band range:** The size of the frequency range for the UTRA FDD band specified in Table 5.0. + +**Range res.:** The size of the frequency range corresponding to the UARFCN range that has been “reserved” in 3GPP for possible future extensions of the band. + +**Formula offset:** The offset parameter ( $F_{UL\_Offset}$ or $F_{DL\_Offset}$ ) in the formula, used to calculate the UARFCN as specified in Clause 5.4.3. + +**Assigned/reserved:** Indicates the significance of the UARFCN and corresponding frequencies listed as follows: + +- | | | +|-------------------|--------------------------------------------------| +| Start res. | Start of the UARFCN range reserved for the band. | +| Min. | The lowest UARFCN assigned to the band. | +| Max. | The highest UARFCN assigned to the band. | +| End res. | End of the UARFCN range reserved for the band. | + +$N_U, N_D$ : Uplink and downlink UARFCN. + +$F_{UL}, F_{DL}$ : Corresponding uplink and downlink frequencies. + +**(Add.):** Refers to the additional UARFCN (on the 100 kHz raster) as specified in Table 5.1A. + +Note that bands V and VI are shown with common entries in Table E.1, since their UARFCN ranges are completely overlapping. + +**Table E.1: UARFCN used for the UTRA FDD bands** + +| UTRA FDD Band | Band range [MHz] | Range res. [MHz] | Uplink UARFCN | | | | Downlink UARFCN | | | | +|-----------------|-----------------------|------------------|---------------------------------------|-------------------|-------|----------------|---------------------------------------|-------------------|-------|----------------| +| | | | Formula offset $F_{UL\_Offset}$ [MHz] | Assigned/Reserved | $N_U$ | $F_{UL}$ [MHz] | Formula offset $F_{DL\_Offset}$ [MHz] | Assigned/Reserved | $N_D$ | $F_{DL}$ [MHz] | +| II (Add.) | 2x60 | 2x60 | 1850.1 | Start res. | 0 | 1850.1 | 1850.1 | Start res. | 400 | 1930.1 | +| | | | | Min. | 12 | 1852.5 | | Min. | 412 | 1932.5 | +| | | | | Max. | 287 | 1907.5 | | Max. | 687 | 1987.5 | +| | | | | End res. | 299 | 1909.9 | | End res. | 699 | 1989.9 | +| XIX | 2x15 | 2x15 | 770 | Start res. | 300 | 830.0 | 735 | Start res. | 700 | 875.0 | +| | | | | Min. | 312 | 832.4 | | Min. | 712 | 877.4 | +| | | | | Max. | 363 | 842.6 | | Max. | 763 | 887.6 | +| | | | | End res. | 374 | 844.8 | | End res. | 774 | 889.8 | +| XIX (Add.) | 2x15 | 2x15 | 755.1 | Start res. | 375 | 830.1 | 720.1 | Start res. | 775 | 875.1 | +| | | | | Min. | 387 | 832.5 | | Min. | 787 | 877.5 | +| | | | | Max. | 437 | 842.5 | | Max. | 837 | 887.5 | +| | | | | End res. | 449 | 844.9 | | End res. | 849 | 889.9 | +| XXI | 2x15 | 2x15 | 1358 | Start res. | 450 | 1448.0 | 1326 | Start res. | 850 | 1496.0 | +| | | | | Min. | 462 | 1450.4 | | Min. | 862 | 1498.4 | +| | | | | Max. | 512 | 1460.4 | | Max. | 912 | 1508.4 | +| | | | | End res. | 524 | 1462.8 | | End res. | 924 | 1510.8 | +| V and VI (Add.) | 2x25 (V)
2x10 (VI) | 2x25 | 670.1 | Start res. | 770 | 824.1 | 670.1 | Start res. | 995 | 869.1 | +| | | | | Min. (V) | 782 | 826.5 | | Min. (V) | 1007 | 871.5 | +| | | | | Min. (VI) | 812 | 832.5 | | Min. (VI) | 1037 | 877.5 | +| | | | | Max. (VI) | 837 | 837.5 | | Max. (VI) | 1062 | 882.5 | +| | | | | Max. (V) | 862 | 842.5 | | Max. (V) | 1087 | 887.5 | +| | | | | End res. | 894 | 848.9 | | End res. | 1119 | 893.9 | +| III | 2x75 | 2x75 | 1525 | Start res. | 925 | 1710.0 | 1575 | Start res. | 1150 | 1805.0 | +| | | | | Min. | 937 | 1712.4 | | Min. | 1162 | 1807.4 | +| | | | | Max. | 1288 | 1782.6 | | Max. | 1513 | 1877.6 | +| | | | | End res. | 1299 | 1784.8 | | End res. | 1524 | 1879.8 | +| IV | 2x45 | 2x45 | 1450 | Start res. | 1300 | 1710.0 | 1805 | Start res. | 1525 | 2110.0 | +| | | | | Min. | 1312 | 1712.4 | | Min. | 1537 | 2112.4 | +| | | | | Max. | 1513 | 1752.6 | | Max. | 1738 | 2152.6 | +| | | | | End res. | 1524 | 1754.8 | | End res. | 1749 | 2154.8 | +| IV (Add.) | 2x45 | 2x45 | 1380.1 | Start res. | 1650 | 1710.1 | 1735.1 | Start res. | 1875 | 2110.1 | +| | | | | Min. | 1662 | 1712.5 | | Min. | 1887 | 2112.5 | +| | | | | Max. | 1862 | 1752.5 | | Max. | 2087 | 2152.5 | +| | | | | End res. | 1874 | 1754.9 | | End res. | 2099 | 2154.9 | +| VII | 2x70 | 2x70 | 2100 | Start res. | 2000 | 2500.0 | 2175 | Start res. | 2225 | 2620.0 | +| | | | | Min. | 2012 | 2502.4 | | Min. | 2237 | 2622.4 | +| | | | | Max. | 2338 | 2567.6 | | Max. | 2563 | 2687.6 | +| | | | | End res. | 2349 | 2569.8 | | End res. | 2574 | 2689.8 | +| VII (Add.) | 2x70 | 2x70 | 2030.1 | Start res. | 2350 | 2500.1 | 2105.1 | Start res. | 2575 | 2620.1 | +| | | | | Min. | 2362 | 2502.5 | | Min. | 2587 | 2622.5 | +| | | | | Max. | 2687 | 2567.5 | | Max. | 2912 | 2687.5 | +| | | | | End res. | 2699 | 2569.9 | | End res. | 2924 | 2689.9 | +| VIII | 2x35 | 2x35 | 340 | Start res. | 2700 | 880.0 | 340 | Start res. | 2925 | 925.0 | +| | | | | Min. | 2712 | 882.4 | | Min. | 2937 | 927.4 | +| | | | | Max. | 2863 | 912.6 | | Max. | 3088 | 957.6 | +| | | | | End res. | 2874 | 914.8 | | End res. | 3099 | 959.8 | +| X | 2x60 | 2x60 | 1135 | Start res. | 2875 | 1710.0 | 1490 | Start res. | 3100 | 2110.0 | +| | | | | Min. | 2887 | 1712.4 | | Min. | 3112 | 2112.4 | +| | | | | Max. | 3163 | 1767.6 | | Max. | 3388 | 2167.6 | +| | | | | End res. | 3174 | 1769.8 | | End res. | 3399 | 2169.8 | +| X | 2x60 | 2x60 | 1075.1 | Start res. | 3175 | 1710.1 | 1430.1 | Start res. | 3400 | 2110.1 | + +| | | | | | | | | | | | +|----------------|-----------------------------|------|-------|------------|------|--------|-------|------------|------|--------| +| (Add.) | | | | Min. | 3187 | 1712.5 | | Min. | 3412 | 2112.5 | +| | | | | Max. | 3462 | 1767.5 | | Max. | 3687 | 2167.5 | +| | | | | End res. | 3474 | 1769.9 | | End res. | 3699 | 2169.9 | +| XI | 2x20 | 2x20 | 733 | Start res. | 3475 | 1428.0 | 736 | Start res. | 3700 | 1476.0 | +| | | | | Min. | 3487 | 1430.4 | | Min. | 3712 | 1478.4 | +| | | | | Max. | 3562 | 1445.4 | | Max. | 3787 | 1493.4 | +| | | | | End res. | 3574 | 1447.8 | | End res. | 3799 | 1495.8 | +| XII | 2x17 | 2x17 | -22 | Start res. | 3605 | 699.0 | -37 | Start res. | 3830 | 729.0 | +| | | | | Min. | 3617 | 701.4 | | Min. | 3842 | 731.4 | +| | | | | Max. | 3678 | 713.6 | | Max. | 3903 | 743.6 | +| | | | | End res. | 3689 | 715.8 | | End res. | 3914 | 745.8 | +| XII
(Add.) | 2x17 | 2x17 | -39.9 | Start res. | 3695 | 699.1 | -54.9 | Start res. | 3920 | 729.1 | +| | | | | Min. | 3707 | 701.5 | | Min. | 3932 | 731.5 | +| | | | | Max. | 3767 | 713.5 | | Max. | 3992 | 743.5 | +| | | | | End res. | 3779 | 715.9 | | End res. | 4004 | 745.9 | +| XIII | 2x10 | 2x10 | 21 | Start res. | 3780 | 777.0 | -55 | Start res. | 4005 | 746.0 | +| | | | | Min. | 3792 | 779.4 | | Min. | 4017 | 748.4 | +| | | | | Max. | 3818 | 784.6 | | Max. | 4043 | 753.6 | +| | | | | End res. | 3829 | 786.8 | | End res. | 4054 | 755.8 | +| XIII
(Add.) | 2x10 | 2x10 | 11.1 | Start res. | 3830 | 777.1 | -64.9 | Start res. | 4055 | 746.1 | +| | | | | Min. | 3842 | 779.5 | | Min. | 4067 | 748.5 | +| | | | | Max. | 3867 | 784.5 | | Max. | 4092 | 753.5 | +| | | | | End res. | 3879 | 786.9 | | End res. | 4104 | 755.9 | +| XIV | 2x10 | 2x10 | 12 | Start res. | 3880 | 788.0 | -63 | Start res. | 4105 | 758.0 | +| | | | | Min. | 3892 | 790.4 | | Min. | 4117 | 760.4 | +| | | | | Max. | 3918 | 795.6 | | Max. | 4143 | 765.6 | +| | | | | End res. | 3929 | 797.8 | | End res. | 4154 | 767.8 | +| XIV
(Add.) | 2x10 | 2x10 | 2.1 | Start res. | 3930 | 788.1 | -72.9 | Start res. | 4155 | 758.1 | +| | | | | Min. | 3942 | 790.5 | | Min. | 4167 | 760.5 | +| | | | | Max. | 3967 | 795.5 | | Max. | 4192 | 765.5 | +| | | | | End res. | 3979 | 797.9 | | End res. | 4204 | 767.9 | +| V
and
VI | 2x25
(V)
2x10
(VI) | 2x25 | 0 | Start res. | 4120 | 824.0 | 0 | Start res. | 4345 | 869.0 | +| | | | | Min. (V) | 4132 | 826.4 | | Min. (V) | 4357 | 871.4 | +| | | | | Min. (VI) | 4162 | 832.4 | | Min. (VI) | 4387 | 877.4 | +| | | | | Max. (VI) | 4188 | 837.6 | | Max. (VI) | 4413 | 882.6 | +| | | | | Max. (V) | 4233 | 846.6 | | Max. (V) | 4458 | 891.6 | +| | | | | End res. | 4244 | 848.8 | | End res. | 4469 | 893.8 | +| XX | 2x30 | 2x30 | -23 | Start res. | 4275 | 832.0 | -109 | Start res. | 4500 | 791.0 | +| | | | | Min. | 4287 | 834.4 | | Min. | 4512 | 793.4 | +| | | | | Max. | 4413 | 859.6 | | Max. | 4638 | 818.6 | +| | | | | End res. | 4424 | 861.8 | | End res. | 4649 | 820.8 | +| XXII | 80 | 80 | 2525 | Start res. | 4425 | 3410.0 | 2580 | Start res. | 4650 | 3510.0 | +| | | | | Min. | 4437 | 3412.4 | | Min. | 4662 | 3512.4 | +| | | | | Max. | 4813 | 3487.6 | | Max. | 5038 | 3587.6 | +| | | | | Stop res. | 4824 | 3489.8 | | Stop res. | 5049 | 3589.8 | +| XXV | 2x65 | 2x65 | 875 | Start res. | 4875 | 1850 | 910 | Start res. | 5100 | 1930 | +| | | | | Min. | 4887 | 1852.4 | | Min. | 5112 | 1932.4 | +| | | | | Max. | 5188 | 1912.6 | | Max. | 5413 | 1992.6 | +| | | | | End res. | 5199 | 1914.8 | | End res. | 5424 | 1994.8 | +| XXV
(Add.) | 2x65 | 2x65 | 639.1 | Start res. | 6055 | 1850.1 | 674.1 | Start res. | 6280 | 1930.1 | +| | | | | Min. | 6067 | 1852.5 | | Min. | 6292 | 1932.5 | +| | | | | Max. | 6367 | 1912.5 | | Max. | 6592 | 1992.5 | +| XXVI | 2x35 | 2x35 | -291 | End res. | 6379 | 1914.9 | -291 | End res. | 6604 | 1994.9 | +| | | | | Start res. | 5525 | 814.0 | | Start res. | 5750 | 859.0 | + +| | | | | | | | | | | | +|-------------------------|------|------|--------|-------------|-------------|---------------|--------|-------------|--------------|---------------| +| | | | | Min. | 5537 | 816.4 | | Min. | 5762 | 861.4 | +| | | | | Max. | 5688 | 846.6 | | Max. | 5913 | 891.6 | +| | | | | End res. | 5699 | 848.8 | | End res. | 5924 | 893.8 | +| XXVI
(Add.) | 2x35 | 2x35 | -325.9 | Start res. | 5700 | 814.1 | -325.9 | Start res. | 5925 | 859.1 | +| | | | | Min. | 5712 | 816.5 | | Min. | 5937 | 861.5 | +| | | | | Max. | 5862 | 846.5 | | Max. | 6087 | 891.5 | +| | | | | End res. | 5874 | 848.9 | | End res. | 6099 | 893.9 | +| XXXII | 44 | 44 | | N/A | | | 131 | Start res. | 6605 | 1452.0 | +| | | | | | | | | Min. | 6617 | 1454.4 | +| | | | | | | | | Max. | 6813 | 1493.6 | +| | | | | | | | | End res. | 6824 | 1495.8 | +| XXXII
(Add.) | 44 | 44 | | N/A | | | 87.1 | Start res. | 6825 | 1452.1 | +| | | | | | | | | Min. | 6637 | 1454.5 | +| | | | | | | | | Max. | 7012 | 1489.5 | +| | | | | | | | | End res. | 7024 | 1491.9 | +| IX | 2x35 | 2x35 | 0 | Start res. | 8750 | 1750.0 | 0 | Start res. | 9225 | 1845.0 | +| | | | | Min. | 8762 | 1752.4 | | Min. | 9237 | 1847.4 | +| | | | | Max. | 8912 | 1782.4 | | Max. | 9387 | 1877.4 | +| | | | | End res. | 8924 | 1784.8 | | End res. | 9399 | 1879.8 | +| II | 2x60 | 2x60 | 0 | Start res. | 9250 | 1850.0 | 0 | Start res. | 9650 | 1930.0 | +| | | | | Min. | 9262 | 1852.4 | | Min. | 9662 | 1932.4 | +| | | | | Max. | 9538 | 1907.6 | | Max. | 9938 | 1987.6 | +| | | | | End res. | 9549 | 1909.8 | | End res. | 9949 | 1989.8 | +| I | 2x60 | 2x60 | 0 | Start res. | 9600 | 1920.0 | 0 | Start res. | 10550 | 2110.0 | +| | | | | Min. | 9612 | 1922.4 | | Min. | 10562 | 2112.4 | +| | | | | Max. | 9888 | 1977.6 | | Max. | 10838 | 2167.6 | +| | | | | End res. | 9899 | 1979.8 | | End res. | 10849 | 2169.8 | +| | | | | | | | | | | | + +--- + +## Annex F (informative): Change history + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| | RP-37 | | | | | Rel-7 version created based on v7.9.0 | 8.0.0 | +| | RP-37 | RP-070658 | 0567 | | B | Introduction of UMTS1500 requirements (Rel-8) | 8.0.0 | +| | RP-37 | RP-070654 | 0571 | 1 | B | MBSFN FDD UE dem req | 8.0.0 | +| | RP-38 | RP-070934 | 0578 | | A | Correction to UE Relative code domain power accuracy | 8.1.0 | +| | RP-38 | RP-070934 | 0580 | 1 | A | Introduction of requirements for UE capable of receiving HS-DSCH and HS-SCCH in CELL_FACH state | 8.1.0 | +| | RP-38 | RP-070936 | 0576 | | A | Editorial correction to the RV sequence of the MIMO FRC | 8.1.0 | +| | RP-38 | RP-070937 | 0575 | | A | Correction to extreme condition voltages for Lithium batteries in table D.2.2 | 8.1.0 | +| | RP-39 | RP-080121 | 0593 | | A | Correct reference to MIMO dual-stream channel model for MIMO CQI dual-stream requirements | 8.2.0 | +| | RP-39 | RP-080121 | 0594 | | A | HS-SCCH Type nominator | 8.2.0 | +| | RP-39 | RP-080121 | 0592 | 1 | A | Nominal Peak Data Rate and redundancy versions in MIMO FRC Tests | 8.2.0 | +| | RP-39 | RP-080124 | 0583 | 2 | B | Introduction of UMTS700EMC requirements | 8.2.0 | +| | RP-39 | RP-080165 | 0598 | | B | Addition of 15 code HSDPA demodulation requirements for 16QAM and QPSK | 8.2.0 | +| | RP-39 | RP-080166 | 0582 | 1 | B | Specification of enhanced performance requirements type 3i for HSDPA based on receiver diversity and interference-aware chip level equaliser | 8.2.0 | +| | RP-39 | RP-080167 | 0595 | | A | Correct reference to H-Set for 64-QAM max input test | 8.2.0 | +| | RP-40 | RP-080326 | 0606 | | F | Correction of UMTS700 UE blocking and intermodulation values | 8.3.0 | +| | RP-40 | RP-080328 | 0608 | 2 | B | Introduction of Cat 19-20 demodulation requirement and cleanup of HS-DSCH requirement applicability. | 8.3.0 | +| | RP-40 | RP-080323 | 0600 | | A | Correction to MIMO propagation conditions | 8.3.0 | +| | RP-40 | RP-080323 | 0611 | | A | HS-DSCH transport Format used for HS-SCCH type 3 requirements | 8.3.0 | +| | RP-40 | RP-080321 | 0603 | | A | Correction to Rx Spurious Emissions | 8.3.0 | +| | RP-40 | RP-080321 | 0601 | | A | Correction to Annex A.8.1 | 8.3.0 | +| | RP-41 | RP-080629 | 0618 | | A | Correction to F-DPCH TPC error rate requirement | 8.4.0 | +| | RP-41 | RP-080629 | 0621 | 1 | A | TS25.101: UTRA UE Power Class | 8.4.0 | +| | RP-41 | RP-080631 | 0614 | 1 | F | CQI reporting test for single link with varying lor/loc | 8.4.0 | +| | RP-41 | RP-080631 | 0626 | 1 | F | MIMO CQI reporting bias tests | 8.4.0 | +| | RP-41 | RP-080631 | 0627 | | F | Clarification of HSDPA performance requirement applicability | 8.4.0 | +| | RP-41 | RP-080625 | 624 | 1 | F | CQI reporting test in fading conditions for 64QAM+MIMO | 8.4.0 | +| | RP-42 | RP-080898 | 635 | 1 | A | Introduction of fading CQI requirement at higher geometry for 64QAM operation | 8.5.0 | +| | RP-42 | RP-080927 | 631 | 1 | A | Clarification of HST propagation conditions | 8.5.0 | +| | RP-42 | RP-080947 | 640 | 1 | B | Introduction of E-AI requirements | 8.5.0 | + +| | | | | | | | | +|--|--------|-----------|-----|---|---|----------------------------------------------------------------------------------------------------------------|-------| +| | RP-42 | RP-080948 | 641 | | B | Introduction of CQI reporting test requirements for DC-HSDPA | 8.5.0 | +| | RP-42 | RP-080948 | 639 | 3 | B | Introduction of DC-HSDPA requirements | 8.5.0 | +| | RP-42 | RP-080948 | 638 | 4 | B | Introduction of FRC requirements for Dual cell HSDPA operation | 8.5.0 | +| | RP-42 | RP-080942 | 636 | | F | CQI reporting test for STTD and CL1 with varying Ior/Ioc | 8.5.0 | +| | | | | | | Correction to version number shown in title line | 8.5.1 | +| | RP-043 | RP-090168 | 644 | 1 | A | Correction to requirement tables for 9.2.1 and 9.2.4. | 8.6.0 | +| | RP-043 | RP-090168 | 648 | 1 | F | Dual Cell HSDPA CQI Requirements in AWGN | 8.6.0 | +| | RP-043 | RP-090168 | 658 | | A | Correction of HS-SCCH power in CQI tests | 8.6.0 | +| | RP-043 | RP-090168 | 649 | 1 | F | Correction to FRC requirements for DC HSDPA | 8.6.0 | +| | RP-043 | RP-090168 | 651 | | F | 25.101 CR Tx-Rx frequency separation for DC-HSDPA | 8.6.0 | +| | RP-043 | RP-090168 | 653 | | F | 25.101 CR clarification of CQI reporting requirement for DC-HSDPA | 8.6.0 | +| | RP-043 | RP-090196 | 650 | 1 | F | 25.101 CR E-DCH phase discontinuity test requirement | 8.6.0 | +| | RP-043 | RP-090196 | 654 | 1 | F | Corrections of out of band blocking | 8.6.0 | +| | RP-044 | RP-090539 | 660 | | A | Clarifications for CQI Reporting Requirements of HSDPA. (Technically Endorsed CR in R4-50bis - R4-091235) | 8.7.0 | +| | RP-044 | RP-090539 | 662 | | F | Correction to MIMO Propagation Conditions. (Technically Endorsed CR in R4-50bis - R4-091433) | 8.7.0 | +| | RP-044 | RP-090539 | 666 | 1 | A | Correction to FRC H-Set 8 definition | 8.7.0 | +| | RP-044 | RP-090546 | 667 | | F | Introduction of a new Compressed Mode pattern for E-UTRAN measurements | 8.7.0 | +| | RP-044 | RP-090555 | 669 | | F | Removal of square brackets for DC-HSDPA Type 3i demodulation tests | 8.7.0 | +| | RP-044 | RP-090559 | 661 | | B | Introduction of Extended UMTS800 requirements | 9.0.0 | +| | RP-45 | RP-090820 | 673 | 1 | A | Update of DC HSDPA CQI requirements | 9.1.0 | +| | RP-46 | RP-091286 | 676 | 1 | B | Introduction of Extended UMTS1500 requirements for TS25.101 (Technically endorsed at RAN 4 52bis in R4-093624) | 9.2.0 | +| | RP-46 | RP-091290 | 679 | 1 | B | Combination of DC-HSDPA and MIMO, CQI requirements (Technically endorsed at RAN 4 52bis in R4-093831) | 9.2.0 | +| | RP-46 | RP-091290 | 680 | 2 | B | Combination of DC-HSDPA and MIMO, FRC requirements (Technically endorsed at RAN 4 52bis in R4-093832) | 9.2.0 | +| | RP-46 | RP-091290 | 681 | 1 | B | Combination of DC-HSDPA and MIMO, RF requirements (Technically endorsed at RAN 4 52bis in R4-093833) | 9.2.0 | +| | RP-46 | RP-091288 | 682 | 1 | B | RF transmitter requirements for DC-HSUPA (Technically endorsed at RAN 4 52bis in R4-094072) | 9.2.0 | +| | RP-46 | RP-091289 | 683 | | B | 25.101 CR introduction of Dual Band DC-HSDPA (Technically Endorsed in R4-52, R4-093464) | 9.2.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|--------| +| | RP-46 | RP-091291 | 689 | 2 | B | Introduction of requirements for TxA A fallback mode | 9.2.0 | +| | RP-46 | RP-091296 | 690 | | A | Clarification of CQI reporting requirement applicability | 9.2.0 | +| | RP-46 | RP-091372 | 694 | | A | RAN5 related changes to enhanced CELL_FACH test case | 9.2.0 | +| | RP-47 | RP-100248 | 702 | | A | Correction of H-Set 11 requirement for type 3 and type 3i receivers | 9.3.0 | +| | RP-47 | RP-100270 | 697 | | F | Correction of CQI requirements for DC_MIMO | 9.3.0 | +| | RP-47 | RP-100271 | 703 | 1 | F | HS-SCCH requirements for TxA A fallback extension | 9.3.0 | +| | RP-47 | RP-100263 | 696 | | B | Introduction of UMTS in 800 MHz for Europe requirements in TS 25.101 | 9.3.0 | +| | RP-47 | RP-100267 | 699 | 1 | B | Tx-Rx frequency separation for DC-HSUPA | 9.3.0 | +| | RP-47 | RP-100267 | 698 | 2 | B | Introduction of Rx core requirements for DC-HSUPA | 9.3.0 | +| | RP-48 | RP-100624 | 712 | | A | Editorial correction of note in varying geometry testcases | 9.4.0 | +| | RP-48 | RP-100626 | 704 | 1 | F | 25.101 CR spurious emission requirements for DC-HSUPA in band XX | 9.4.0 | +| | RP-48 | RP-100631 | 714 | 1 | F | Small correction to parameters for testing MIMO FRC H-Set11/11A | 9.4.0 | +| | RP-48 | RP-100631 | 713 | | F | DC-MIMO-HSDPA; Removal of brackets from CQI Requirements | 9.4.0 | +| | RP-49 | RP-100918 | 725 | | A | Corrections to CQI reporting requirements | 9.5.0 | +| | RP-49 | RP-100921 | 728 | | F | Correction to Rx core requirements for DC-HSUPA | 9.5.0 | +| | RP-49 | RP-100921 | 722 | | F | Clarification of primary uplink frequency and secondary uplink frequency | 9.5.0 | +| | RP-50 | RP-101334 | 745 | | A | Correction to Band XII frequency range | 9.6.0 | +| | RP-50 | RP-101339 | 742 | 1 | A | Correction to Downlink Physical Channels in DC-HSDPA Tests | 9.6.0 | +| | RP-50 | RP-101348 | 751 | 1 | F | Correction to core requirements for DB-DC-HSDPA with bands II/IV combination | 9.6.0 | +| | RP-50 | RP-101348 | 747 | 2 | F | Clarification on carrier spacing for DC-HSDPA with MIMO | 9.6.0 | +| | RP-50 | RP-101353 | 733 | 2 | B | Introduction of frequency bands for 4C-HSDPA | 10.0.0 | +| | RP-50 | RP-101353 | 750 | 1 | B | 25.101 CR Introduction of Tx Core Requirements for DB-DC-HSDPA and dual band 4C-HSDPA with bands II/IV combination | 10.0.0 | +| | RP-50 | RP-101353 | 737 | 1 | B | 25.101 CR introduction of Rx core requirements for 4C-HSDPA | 10.0.0 | +| | RP-50 | RP-101361 | 748 | | B | Protection of E-UTRA Band 24 | 10.0.0 | +| | | | | | | Correction of reference to table 7.1aB in section 7.3.1 | 10.0.1 | +| | RP-51 | RP-110354 | 0754 | 1 | F | Introduction of Rx core requirements for DB-DC-HSDPA and dual band 4C-HSDPA | 10.1.0 | +| | RP-51 | RP-110345 | 0765 | 1 | A | Correction to Downlink Physical Channels in DC-HSDPA receiver sensitivity | 10.1.0 | +| | RP-51 | RP-110354 | 0766 | 1 | F | Introduction of Tx core requirements for DB-DC-HSDPA and dual band 4C-HSDPA for I/VIII and I/V band combinations | 10.1.0 | +| | RP-51 | RP-110407 | 0768 | 1 | B | HSDPA MIMO demodulation performance requirements due to asymmetric P-CPICH/S-CPICH power settings | 10.1.0 | +| | RP-51 | RP-110345 | 0771 | - | A | DC-HSUPA Rx core requirements for band XI and band XXI | 10.1.0 | +| | RP-51 | RP-110341 | 0776 | - | A | Correction of UARFCN range for Band XII | 10.1.0 | +| | RP-51 | RP-110336 | 0779 | - | A | Correction of OOB interferer frequency ranges for Band XII | 10.1.0 | +| | RP-51 | RP-110355 | 0783 | - | A | 25.101 CR: Correction of out of band blocking for DB-DC-HSDPA configuration 3 (Rel-10) | 10.1.0 | +| | RP-51 | RP-110346 | 0785 | 2 | F | 25.101 CR Introduction of demodulation performance for DB-DC-HSDPA (rel-10) | 10.1.0 | +| | RP-51 | RP-110355 | 0788 | 3 | B | CR for the addition of the new band combinations and the TX core requirements for band I-XI and II-V | 10.1.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| | RP-51 | RP-110355 | 0789 | 3 | B | CR for RX core requirements for band I-XI and II-V | 10.1.0 | +| | RP-51 | RP-110341 | 0793 | 1 | A | CR for the modification of the UE relative code domain power accuracy | 10.1.0 | +| | RP-52 | RP-110798 | 797 | | B | CR for the introduction of TX core requirements for band I-XI and II-V | 10.2.0 | +| | RP-52 | RP-110798 | 798 | | B | 25.101 CR Introduction of Rx core requirements for Band combinations II-V and I-XI | 10.2.0 | +| | RP-52 | RP-110801 | 799 | | B | HSDPA MIMO CQI reporting requirements due to asymmetric P-CPICH/S-CPICH power settings | 10.2.0 | +| | RP-52 | RP-110801 | 811 | | B | HSDPA MIMO CQI reporting requirements due to asymmetric P-CPICH/S-CPICH power settings | 10.2.0 | +| | RP-52 | RP-110812 | 812 | | B | UTRAN UE spurious emission requirements to protect E-UTRA band 23 | 10.2.0 | +| | RP-52 | RP-110795 | 813 | | F | UTRAN UE spurious emission requirements to protect E-UTRA band 24 | 10.2.0 | +| | RP-52 | RP-110796 | 816 | | F | Additional Spurious requirement extension due to EN spec change | 10.2.0 | +| | RP-52 | RP-110801 | 807 | 1 | B | Clarification on retransmission for MIMO workaround | 10.2.0 | +| | RP-52 | RP-110804 | 805 | 3 | B | Expanded 1900 MHz addition to 25.101 | 10.2.0 | +| | RP-53 | RP-111252 | 846 | | A | Correction of UE Relative code domain power accuracy requirements for TS 25.101 REL-10 | 10.3.0 | +| | RP-53 | RP-111253 | 843 | | A | Clarification of spectrum emission mask requirements | 10.3.0 | +| | RP-53 | RP-111254 | 829 | | A | Clarification of ACLR requirements for DC-HSUPA | 10.3.0 | +| | RP-53 | RP-111255 | 838 | 1 | B | Add Band XXII for LTE/UMTS 3500 (FDD) to TS 25.101 | 10.3.0 | +| | RP-53 | RP-111262 | 837 | 1 | F | Fixing UARFCN numbers in 25.101 | 10.3.0 | +| | RP-53 | RP-111264 | 830 | 1 | F | UE core requirements for Band XXV | 10.3.0 | +| | RP-53 | RP-111270 | 818 | | B | Completion of UE demodulation performance requirements for 4C-HSDPA | 10.3.0 | +| | RP-53 | RP-111270 | 819 | 1 | B | Introduction of UE CQI reporting requirements for 4C-HSDPA | 10.3.0 | +| | RP-54 | RP-111690 | 848 | | F | Non applicable UARFCN numbers | 10.4.0 | +| | RP-54 | RP-111735 | 850 | | F | Alignment with TS 36.101 on 3500MHz | 10.4.0 | +| | RP-54 | RP-111686 | 851 | | F | Introduction of missing ACS case 2 requirement for single band 4C-HSDPA | 10.4.0 | +| | RP-54 | RP-111696 | 849 | | B | Introduction of single band 4C-HSDPA II-4 | 11.0.0 | +| | RP-55 | RP-120306 | 860 | 1 | B | Introduction of Band 26/XXVI to TS 25.101 | 11.1.0 | +| | RP-55 | RP-120297 | 862 | | A | Correction of frequency range for spurious emission requirements | 11.1.0 | +| | RP-56 | RP-120775 | 866 | - | A | Correction to H-Set 8 | 11.2.0 | +| | RP-56 | RP-120771 | 874 | 1 | A | Introduction of Japanese Regulatory Requirements to W-CDMA Band VIII (R11) | 11.2.0 | +| | RP-56 | RP-120786 | 876 | 2 | B | Introduction of 8C-HSDPA operation in 25.101 and rx core requirements | 11.2.0 | +| | RP-56 | RP-120793 | 881 | - | B | Introduction of Band 28 | 11.2.0 | +| | RP-56 | RP-120779 | 883 | - | A | Correction of TX power step size tolerance for HS-DPCCH | 11.2.0 | +| | RP-56 | RP-120793 | 884 | 1 | B | Introduction of Band 44 | 11.2.0 | +| | RP-56 | RP-120763 | 888 | - | A | Correction to numbers of HS-SCCH for DC-HSDPA | 11.2.0 | +| | RP-56 | RP-120791 | 889 | 2 | B | Introduction of E850_LB (Band 27) to TS 25.101 | 11.2.0 | +| | RP-56 | RP-120766 | 895 | - | A | Correction of PHS protection requirements for TS 25.101 | 11.2.0 | +| | RP-56 | RP-120610 | 899 | 2 | B | Introduction of non contiguous 4C-HSDPA core requirements definition | 11.2.0 | +| | RP-57 | RP-121300 | 892a | - | A | Corrections of spurious emission band UE co-existence applicable in Japan | 11.3.0 | +| | RP-57 | RP-121309 | 899a | 1 | F | Missing allowed de-sensitization for single band 4C-HSDPA | 11.3.0 | +| | RP-57 | RP-121299 | 905 | 1 | A | Correction of DC-HSUPA core requirements | 11.3.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-57 | RP-121314 | 906 | 1 | F | Removal of [] in NC-4C-HSDPA core requirements | 11.3.0 | +| | RP-57 | RP-121318 | 907 | 1 | B | Performance requirements for 8C-HSDPA | 11.3.0 | +| | RP-57 | RP-121312 | 909 | - | A | DC-HSUPA for Band XXII | 11.3.0 | +| | RP-57 | RP-121317 | 910 | - | B | Modification of the MPR/CM for 8C-HSDPA | 11.3.0 | +| | RP-57 | RP-121340 | 911 | - | F | Correction of the HS-DPCCH power step range | 11.3.0 | +| | RP-57 | RP-121320 | 912 | - | B | Tx requirements for I-2-VIII-2 and II-1-V-2 | 11.3.0 | +| | RP-57 | RP-121320 | 913 | 1 | B | Missing requirements for I-2-VIII-2 and II-1-V-2 | 11.3.0 | +| | RP-58 | RP-121867 | 927 | | A | Japanese regulatory requirements for DC-HSUPA spurious emissions | 11.4.0 | +| | RP-58 | RP-121856 | 931 | | A | Alignment of inconsistent Rx core requirements with dual uplinks | 11.4.0 | +| | RP-58 | RP-121908 | 933 | 1 | B | Introduction of UL MIMO to TS 25.101 | 11.4.0 | +| | RP-58 | RP-121876 | 934 | 1 | B | CR to TS 25.101 due to introduction of CLTD | 11.4.0 | +| | RP-58 | RP-121901 | 935 | | B | Introduction of Band 29 | 11.4.0 | +| | RP-58 | RP-121876 | 937 | | B | F-TPICH out of quality handling for UL CLTD and UL MIMO | 11.4.0 | +| | RP-58 | RP-121877 | 918 | 1 | B | CR to TS 25.101 due to introduction of OLTD | 11.4.0 | +| | RP-58 | RP-121848 | 923 | | A | Introducing the additional frequency bands of 5 MHz x 2 in 1.7 GHz in Japan to Band III | 11.4.0 | +| | RP-58 | RP-121867 | 925 | | A | Cleaning of 25.101 Performance sections Rel-11
The CR was not implemented as it was not based on the latest version of the spec | 11.4.0 | +| | RP-59 | RP-130287 | 941 | 1 | F | CR for Cleaning of 25.101 Rel-11 | 11.5.0 | +| | RP-59 | RP-130287 | 942 | 1 | F | Band 41 requirements for operation in China and Japan | 11.5.0 | +| | RP-59 | RP-130281 | 940 | 1 | B | CR for Non contiguous Carrier aggregation UE demodulation performance | 11.5.0 | +| | RP-59 | RP-130271 | 939 | | F | Some corrections on requirements of ULTD for TS 25.101 | 11.5.0 | +| | RP-59 | RP-130270 | 938 | 1 | F | Removal of bracket from CR F-TPICH out of quality handling for UL CLTD and UL MIMO | 11.5.0 | +| | RP-60 | RP-130762 | 948 | | A | Adding definition of UE maximum output power for DC-HSUPA | 11.6.0 | +| | RP-60 | RP-130762 | 951 | | A | Correction to center frequency offset for additional spectrum emissions mask | 11.6.0 | +| | RP-60 | RP-130768 | 952 | | F | Correction to Definitions list | 11.6.0 | +| | RP-60 | RP-130768 | 955 | 1 | F | Co-existence with 2.6GHz bands | 11.6.0 | +| | RP-60 | RP-130768 | 964 | | F | Introduction of F-TPICH demodulation performance requirements in F-TPICH out-of-quality handling requirements | 11.6.0 | +| | RP-60 | RP-130766 | 967 | | A | Carrier aggregation in multi-RAT UTRA and E-UTRA terminals | 11.6.0 | +| | RP-60 | RP-130764 | 973 | | A | Editorial CR for 25.101 rel-11 | 11.6.0 | +| | RP-60 | RP-130791 | 960 | | B | Introduction of Band 30 | 12.0.0 | +| | RP-60 | RP-130790 | 971 | | B | Protection of LTE 450 band | 12.0.0 | +| | RP-61 | RP-131280 | 988 | | A | CM and MPR for DC-HSUPA with 16QAM | 12.1.0 | +| | RP-61 | RP-131304 | 989 | | A | Introduction of UE demodulation performance requirements for Multiflow HSDPA | 12.1.0 | +| | RP-61 | RP-131304 | 990 | | A | Introduction of UE CQI reporting performance requirements for Multiflow HSDPA | 12.1.0 | +| | RP-62 | RP-131925 | 1004 | | A | Missing update on reference input power adjustment for a dual band device | 12.2.0 | +| | RP-62 | RP-131933 | 1010 | | A | CSI testing for MIMO mode with 4 transmit antennas | 12.2.0 | +| | RP-62 | RP-131932 | 1015 | | A | Introduction of UE requirements for determination of Common E-RGCH Radio Link(s) in Cell_FACH | 12.2.0 | +| | RP-62 | RP-131967 | 1016 | | F | Band 41 deployment in Japan | 12.2.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-62 | RP-131933 | 992 | | A | HS-PDSCH performance requirements for MIMO mode with 4 transmit antennas | 12.2.0 | +| | RP-62 | RP-131929 | 996 | | A | Clarification on the applicability of MIMO performance for a UE supporting NC-MC-HSDPA | 12.2.0 | +| | RP-63 | RP-140375 | 1028 | | A | Editorial corrections to UE RF core requirements in TS 25.101 | 12.3.0 | +| | RP-63 | RP-140369 | 1018 | | A | Removing [] in 25.101 in the context of Four transmit antennas for HSDPA | 12.3.0 | +| | RP-64 | RP-140926 | 1034 | 2 | B | Introduction of Band XXXII and Band I+XXXII | 12.4.0 | +| | RP-64 | RP-140945 | 1033 | | D | Editorial correction of note in clause 4.4 | 12.4.0 | +| | RP-65 | RP-141543 | 1040 | | B | Addition of demodulation requirement for BCH mapped to S-CCPCH | 12.5.0 | +| | RP-65 | RP-141529 | 1042 | | A | Maximum allowed UL TX power for Band XXVI coexistence with Public Safety | 12.5.0 | +| | RP-65 | RP-141238 | 1043 | | B | CR on UMTS HetNet Enhancements | 12.5.0 | +| | RP-66 | RP-142168 | 1054 | | B | UMTS HetNet Enhancements requirements for power control | 12.6.0 | +| | RP-66 | RP-142167 | 1049 | 1 | B | 25.101 CR on performance requirements for UE DCH demodulation during handover due to introduction of DCH enhancements | 12.6.0 | +| | RP-66 | RP-142167 | 1051 | 1 | B | 25.101 CR on performance requirements for UE DCH demodulation in static and multipath fading conditions due to introduction of DCH enhancements | 12.6.0 | +| | RP-66 | RP-142170 | 1053 | 1 | B | 25.101 CR on E-AGCH performance requirements with TDM granting | 12.6.0 | +| | RP-66 | RP-142188 | 1059 | 1 | F | TS25.101 removal of brackets (RF) | 12.6.0 | +| | RP-66 | RP-142153 | 1055 | 1 | F | UMTS HetNet Enhancements impact on cubic metric (MPR) | 12.6.0 | +| | RP-66 | RP-142167 | 1048 | 2 | B | 25.101 CR on new reference measurement channels due to introduction of DCH enhancements | 12.6.0 | +| | RP-66 | RP-142167 | 1050 | 2 | B | 25.101 CR on performance requirements for downlink power control due to introduction of DCH enhancements | 12.6.0 | +| | RP-67 | RP-150385 | 1060 | | F | TX UE spurious emissions alignment with 36.101 | 12.7.0 | +| | RP-67 | RP-150385 | 1061 | | F | RX UE spurious emissions simplification | 12.7.0 | +| | RP-67 | RP-150385 | 1062 | | F | Removal of square brackets of cubic metric (MPR) for UMTS HetNet Enhancements | 12.7.0 | +| | RP-68 | RP-150957 | 1067 | | F | Receiver spurious emissions requirements for downlink-only bands (Band XXXII) | 12.8.0 | +| | RP-69 | RP-151483 | 1070 | 1 | F | Correction on RX spurious emissions of Band VI and XIX | 12.9.0 | +| | RP-69 | RP-151483 | 1071 | 1 | F | UMTS UE co-existence requirements from the Japanese bands to the frequency range of 3400-3600 MHz | 12.9.0 | +| | RP-69 | RP-151492 | 1073 | | A | Correction to table C.24 title | 12.9.0 | +| | RP-69 | RP-151477 | 1075 | | F | Correction in the available channel list when DPCCH2 is configured | 12.9.0 | +| | RP-69 | RP-151483 | 1076 | | F | Correction of notes for UE additional TX/RX spurious emissions requirements | 12.9.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------|--------| +| | RP-69 | RP-151492 | 1074 | | B | Introduction of the Multiflow 3F-4C configuration | 13.0.0 | +| | RP-70 | RP-152171 | 1084 | - | B | Introduction of Band 65 to TS 25.101 | 13.1.0 | +| | RP-70 | RP-152157 | 1086 | - | B | Introduction of Band 67 | 13.1.0 | +| | RP-70 | RP-152172 | 1087 | - | B | Introduction of Band 66 | 13.1.0 | +| | RP-70 | RP-152140 | 1088 | 1 | B | 25.101CR to introduce DB-DC-HSUPA | 13.1.0 | +| | RP-70 | RP-152142 | 1089 | 1 | B | Out-of-synchronization requirement for UTRA TPC algorithm 3 | 13.1.0 | +| | RP-70 | RP-152175 | 1090 | - | B | Introduction of Region 3 requirement in Band 65 | 13.1.0 | +| | RP-70 | RP-152144 | 1091 | 1 | B | Introduction of Dual Carrier HSUPA enhancements for UTRAN CS in TS 25.101 | 13.1.0 | +| | RP-70 | RP-152173 | 1092 | - | B | Introduction of 1447-1467MHz Band into 25.101 | 13.1.0 | +| 03/2016 | RP-71 | RP-160484 | 1093 | 1 | B | Introduction of TPC decoding requirement due to TPC algorithm 3 | 13.2.0 | +| 03/2016 | RP-71 | RP-160487 | 1099 | 1 | A | CR on ILPC Exceptions | 13.2.0 | +| 2016-05 | | | | | | Correction to RP-71 entries in change history table above | 13.2.1 | +| 2016/06 | RP-72 | RP-161125 | 1101 | - | B | Introduction of Band 70 to 25.101 | 14.0.0 | +| 2017/09 | RP-77 | RP-171952 | 1102 | | B | Introduction of Band 71 to TS25.101 | 15.0.0 | +| 2017/09 | RP-77 | RP-171948 | 1103 | | B | Introduction of the FDD L-band (Band 74) into TS 25.101 | 15.0.0 | +| 2017/09 | RP-77 | RP-171946 | 1104 | 1 | B | Addition of band 72 protection TS 25.101 | 15.0.0 | +| 2017/09 | RP-77 | RP-171949 | 1105 | 1 | B | Introduction of L-band for SDL, TDD and FDD for TS 25.101 | 15.0.0 | +| 2017/09 | RP-77 | RP-171950 | 1106 | | B | Protection of E-UTRA Extended 1.5 GHz SDL bands 75 and 76 | 15.0.0 | +| 2017/12 | RP-78 | RP-172593 | 1107 | 1 | B | Introduction of Band 73 into TS 25.101 | 15.1.0 | +| 2018-03 | RAN#79 | RP-180279 | 1109 | | B | CR to 25.101: Introduction of Band 85 (B12-extended) | 15.2.0 | +| 2018-03 | RAN#79 | RP-180278 | 1110 | | B | Introduction of TDD 3.3-3.4GHz band (band 52) | 15.2.0 | +| 2018-12 | RAN#82 | RP-182376 | 1112 | 1 | B | Introduction of band 53 into TS 25.101 | 16.0.0 | +| 2019-03 | RAN#83 | RP-190401 | 1115 | | A | Introduction of NR protection in TS25.101 | 16.1.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25106/89dcb02be40d2949bb93de93bbf213d5_img.jpg b/marked/Rel-16/25_series/25106/89dcb02be40d2949bb93de93bbf213d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1e6a47957d927987a34ef2dfa0050990ec4c475 --- /dev/null +++ b/marked/Rel-16/25_series/25106/89dcb02be40d2949bb93de93bbf213d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58874e7397301f8a147102f608fb07651d106d7fe8f1444f740bda91d9d99e23 +size 50602 diff --git a/marked/Rel-16/25_series/25106/raw.md b/marked/Rel-16/25_series/25106/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0030a26e883b6fa11035d17ad1c0a52c2fe1e410 --- /dev/null +++ b/marked/Rel-16/25_series/25106/raw.md @@ -0,0 +1,1269 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Relationship between Minimum Requirements and Test Requirements ..... | 7 | +| 4.2 Regional requirements..... | 8 | +| 5 Frequency bands and channel arrangement ..... | 9 | +| 5.1 Frequency bands..... | 9 | +| 5.2 TX - RX frequency separation ..... | 9 | +| 5.3 Channel arrangement..... | 10 | +| 5.3.1 Channel spacing..... | 10 | +| 5.3.2 Channel raster..... | 10 | +| 5.3.3 Channel number..... | 10 | +| 6 Output power..... | 12 | +| 6.1 Maximum output power..... | 13 | +| 6.1.1 Minimum Requirements..... | 13 | +| 7 Frequency stability..... | 13 | +| 7.1 Minimum requirement..... | 13 | +| 8 Out of band gain..... | 13 | +| 8.1 Minimum requirement..... | 13 | +| 9 Unwanted emission ..... | 14 | +| 9.1 Out of band emission..... | 14 | +| 9.1.1 Void ..... | 14 | +| 9.1.2 Operating band unwanted emissions ..... | 14 | +| 9.1.3 Protection of the BS receiver in the operating band..... | 19 | +| 9.1.3.1 Minimum Requirement..... | 19 | +| 9.1.4 Co-existence with services in adjacent frequency bands..... | 19 | +| 9.1.4.1 Minimum requirement ..... | 19 | +| 9.2 Spurious emissions..... | 19 | +| 9.2.1 General Requirements ..... | 20 | +| 9.2.1.1 Minimum Requirement (Category A)..... | 20 | +| 9.2.1.2 Minimum Requirement (Category B)..... | 20 | +| 9.2.2 Void ..... | 21 | +| 9.2.3 Co-existence with other systems in the same geographical area..... | 21 | +| 9.2.3.1 Minimum Requirements ..... | 22 | +| 9.2.4 Co-existence with co-located and co-sited Base Stations ..... | 25 | +| 9.2.4.1 Minimum Requirements ..... | 26 | +| 9.2.5 Co-existence with PHS..... | 28 | +| 9.2.5.1 Minimum Requirement..... | 28 | +| 9.2.6 Co-existence with UTRA-TDD and/or E-UTRA TDD..... | 29 | +| 9.2.6.1 Operation in the same geographic area..... | 29 | +| 9.2.6.1.1 Minimum Requirement ..... | 29 | +| 9.2.6.2 Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations..... | 31 | +| 9.2.6.2.1 Minimum Requirement ..... | 31 | +| 9.2.7 Void ..... | 33 | +| 9.2.8 Protection of public safety operations ..... | 33 | +| 9.2.8.1 Minimum Requirement..... | 33 | + +| | | | +|------------------------|----------------------------------------------------------------------------------------|----| +| 10 | Modulation accuracy..... | 33 | +| 10.1 | Error Vector Magnitude ..... | 33 | +| 10.1.1 | Minimum requirement..... | 34 | +| 10.2 | Peak code domain error..... | 34 | +| 10.2.1 | Minimum requirement..... | 34 | +| 10.3 | Relative Code Domain Error (RCDE) for 64QAM modulation ..... | 34 | +| 10.3.1 | Minimum requirement..... | 34 | +| 11 | Input Intermodulation ..... | 34 | +| 11.1 | General Requirement..... | 34 | +| 11.1.1 | Minimum requirement..... | 34 | +| 11.2 | Co-location with BS in other systems ..... | 35 | +| 11.2.1 | Minimum requirements - Co-location with GSM, DCS, PCS, UTRA FDD and/or E-UTRA FDD..... | 35 | +| 11.2.2 | Minimum Requirement - Co-location with UTRA-TDD and/or E-UTRA TDD..... | 38 | +| 11.3 | Co-existence with other systems..... | 39 | +| 11.3.1 | Minimum requirements ..... | 39 | +| 12 | Output intermodulation ..... | 42 | +| 12.1 | Minimum requirement..... | 42 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 43 | +| 13.1 | Definitions and applicability ..... | 43 | +| 13.2 | Minimum Requirements..... | 43 | +| Annex A (informative): | Change History..... | 44 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document.. + +# --- 1 Scope + +The present document establishes the minimum radio frequency performance of UTRA FDD repeaters. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [2] 3GPP TS 25.143: "UTRA Repeater Conformance Testing". +- [3] 3GPP TS 25.113: "Base Station and Repeater Electromagnetic Compatibility". +- [4] ETSI ETR 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [5] 3GPP TR 25.942: "RF System Scenarios". +- [6] 3GPP TS 25.104: "UTRA(BS) FDD; Radio transmission and Reception". +- [7] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL) ". +- [8] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Donor coupling loss:** is the coupling loss between the repeater and the donor base station. + +**Down-link:** Signal path where base station transmits and mobile receives. + +**Operating band:** the frequency range in which UTRA FDD operates, that is defined with a specific set of technical requirements. + +NOTE 1: The operating band(s) for an UTRA Repeater is declared by the manufacturer according to the designations in clause 5.1, Table 5.1. + +NOTE 2: Unless specified, operating band refers to the uplink operating band and downlink operating band. + +**Pass band:** The frequency range in which the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal 5 MHz channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. A repeater can have one or several pass bands. + +**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). In operating bands specified with only down-link or up-link, only the up-link or down-link as specified for the operating band is repeated. + +**Up-link:** Signal path where mobile transmits and base station receives. + +## 3.2 Symbols + +(void) + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------| +| BS | Base Transceiver Station | +| DL | Down Link (forward link) | +| DTT | Digital Terrestrial Television | +| EVM | Error Vector Magnitude | +| EIRP | Effective Isotropic Radiated Power | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| IMT2000 | International Mobile Telecommunication-2000 | +| ITU | International Telecommunication Union | +| RCDE | Relative Code Domain Error. | +| RF | Radio Frequency | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UL | Up Link (reverse link) | +| UMTS | Universal Mobile Telecommunication System | +| UTRA | Universal Terrestrial Radio Access | +| WCDMA | Wide band Code Division Multiple Access | + +# --- 4 General + +This specification applies only to UTRA-FDD repeaters. + +Unless otherwise stated, all requirements in this specification apply to both the up-link and down-link directions, where applicable. + +## 4.1 Relationship between Minimum Requirements and Test Requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The repeater test specification 25.143 section 5 [2] defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ETR 273 Part 1 sub-part 2 section 6.5 [4]. + +## 4.2 Regional requirements + +Some requirements in TS 25.106 may only apply in certain regions. Table 4.1 lists all requirements that may be applied differently in different regions. + +**Table 4.1: List of regional requirements.** + +| Clause number | Requirement | Comments | +|---------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.1 | Frequency bands | Some bands may be applied regionally. | +| 5.2 | TX – RX frequency separation | The requirement is applied according to which frequency bands in Clause 5.1 that are supported by the Repeater. | +| 5.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 5.1 that are supported by the Repeater. | +| 6.1 | Maximum output power | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. | +| 9.1.2 | Operating band unwanted emissions | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. Additional spectrum protection may apply regionally. | +| 9.2.1.1 | Spurious emissions (Category A) | These requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. | +| 9.2.1.2 | Spurious emissions (Category B) | These requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. | +| 9.2.3 | Spurious emissions: Co-existence with other systems in the same geographical area | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900 DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | +| 9.2.4 | Spurious emissions: Co-existence with co-located and co-sited base stations | These requirements may be applied for the protection of other BS receivers when GSM900 DCS1800, PCS1900, GSM850 and/or FDD BS operating in another frequency band are co-located with a UTRA FDD Repeater. | +| 9.2.5 | Spurious emissions: Co-existence with PHS | This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA FDD Repeaters are deployed. | +| 9.2.6.1 | Spurious emissions: Co-existence with UTRA-TDD and/or E-UTRA TDD - Operation in the same geographic area | This requirement may be applied for the protection of UTRA UE in geographic areas in which both UTRA TDD BS and UTRA FDD Repeaters are deployed. | +| 9.2.6.2 | Spurious emissions: Co-existence with UTRA-TDD and/or E-UTRA TDD - Co-location | This requirement may be applied for the protection of UTRA TDD BS receivers when UTRA TDD BS and UTRA FDD Repeaters are co-located. | +| 9.2.8 | Spurious emissions: Protection of public safety operations | This requirement may be applied for the protection of public safety systems in geographic areas in which both UTRA FDD Repeater and public safety systems are deployed. | +| 11.2 | Input Intermodulation: Co-location with BS in other systems | The requirement may be applied when GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band and UTRA-FDD Repeaters are co-located. | +| 11.3 | Input Intermodulation: Co-existence with other systems | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | + +# 5 Frequency bands and channel arrangement + +## 5.1 Frequency bands + +- A UTRA/FDD Repeater is designed to operate in one or several pass bands within either of the following operating bands; + +**Table 5.1: Frequency bands** + +| Operating Band | UL Frequencies
UE transmit, Node B receive | DL frequencies
UE receive, Node B transmit | +|-----------------------|-------------------------------------------------------|-------------------------------------------------------| +| I | 1920 - 1980 MHz | 2110 - 2170 MHz | +| II | 1850 - 1910 MHz | 1930 - 1990 MHz | +| III | 1710 - 1785 MHz | 1805 - 1880 MHz | +| IV | 1710 - 1755 MHz | 2110 - 2155 MHz | +| V | 824 - 849 MHz | 869 - 894 MHz | +| VI | 830 - 840 MHz | 875 - 885 MHz | +| VII | 2500 - 2570 MHz | 2620 - 2690 MHz | +| VIII | 880 - 915 MHz | 925 - 960 MHz | +| IX | 1749.9 - 1784.9 MHz | 1844.9 - 1879.9 MHz | +| X | 1710 - 1770 MHz | 2110 - 2170 MHz | +| XI | 1427.9 - 1447.9 MHz | 1475.9 - 1495.9 MHz | +| XII | 698 - 716 MHz | 728 - 746 MHz | +| XIII | 777 - 787 MHz | 746 - 756 MHz | +| XIV | 788 - 798 MHz | 758 - 768 MHz | +| XV | Reserved | Reserved | +| XVI | Reserved | Reserved | +| XVII | Reserved | Reserved | +| XVIII | Reserved | Reserved | +| XIX | 830 - 845 MHz | 875 - 890 MHz | +| XX | 832 - 862 MHz | 791 - 821 MHz | +| XXI | 1447.9 - 1462.9 MHz | 1495.9 - 1510.9 MHz | +| XXII | 3410 - 3490 MHz | 3510 - 3590 MHz | +| XXV | 1850 - 1915 MHz | 1930 - 1995 MHz | +| XXVI | 814 - 849 MHz | 859 - 894 MHz | +| XXXII | N/A | 1452 - 1496 MHz | + +b) Deployment in other frequency bands is not precluded. + +## 5.2 TX - RX frequency separation + +a) A UTRA/FDD repeater is designed to operate with the following TX to RX frequency separation + +**Table 5.2: TX-RX frequency separation** + +| Operating Band | TX-RX frequency separation | +|-----------------------|-----------------------------------| +| I | 190 MHz | +| II | 80 MHz | +| III | 95 MHz | +| IV | 400 MHz | +| V | 45 MHz | +| VI | 45 MHz | +| VII | 120 MHz | +| VIII | 45 MHz | +| IX | 95 MHz | +| X | 400 MHz | +| XI | 48 MHz | +| XII | 30 MHz | +| XIII | 31 MHz | +| XIV | 30 MHz | +| XIX | 45 MHz | +| XX | 41 MHz | +| XXI | 48 MHz | +| XXII | 100 MHz | +| XXV | 80 MHz | +| XXVI | 45 MHz | + +b) A UTRA/FDD repeater can support both fixed and variable up-link to down-link frequency separation. + +- c) The use of other up-link to down-link frequency separations in existing or other frequency bands shall not be precluded. + +## 5.3 Channel arrangement + +### 5.3.1 Channel spacing + +The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 5.3.2 Channel raster + +The channel raster is 200 kHz for all bands, which means that the centre frequency must be an integer multiple of 200 kHz. In addition, a number of additional centre frequencies are specified according to the table 5.3, which means that and the centre frequencies for these channels are shifted 100 kHz relative to the general raster. + +### 5.3.3 Channel number + +The carrier frequency is designated by the UTRA Absolute Radio Frequency Channel Number (UARFCN). + +For each operating band, the UARFCN values are defined as follows. + +Uplink: $N_U = 5 * (F_{UL} - F_{UL\_offset})$ , for the carrier frequency range $F_{UL\_low} \leq F_{UL} \leq F_{UL\_high}$ + +Downlink: $N_D = 5 * (F_{DL} - F_{DL\_offset})$ , for the carrier frequency range $F_{DL\_low} \leq F_{DL} \leq F_{DL\_high}$ + +For each operating Band, $F_{UL\_offset}$ , $F_{UL\_low}$ , $F_{UL\_high}$ , $F_{DL\_offset}$ , $F_{DL\_low}$ and $F_{DL\_high}$ are defined in Table 5.3 for the general UARFCN. For the additional UARFCN, $F_{UL\_offset}$ , $F_{DL\_offset}$ and the specific $F_{UL}$ and $F_{DL}$ are defined in Table 5.4. + +**Table 5.3: UARFCN definition (general)** + +| Band | UPLINK (UL) | | | DOWNLINK (DL) | | | +|-------|----------------------------------------------|--------------------------------------------|----------------|----------------------------------------------|--------------------------------------------|----------------| +| | UE transmit, Node B receive | | | UE receive, Node B transmit | | | +| | UARFCN formula offset $F_{UL\_Offset}$ [MHz] | Carrier frequency ( $F_{UL}$ ) range [MHz] | | UARFCN formula offset $F_{DL\_Offset}$ [MHz] | Carrier frequency ( $F_{DL}$ ) range [MHz] | | +| | | $F_{UL\_low}$ | $F_{UL\_high}$ | | $F_{DL\_low}$ | $F_{DL\_high}$ | +| I | 0 | 1922.4 | 1977.6 | 0 | 2112.4 | 2167.6 | +| II | 0 | 1852.4 | 1907.6 | 0 | 1932.4 | 1987.6 | +| III | 1525 | 1712.4 | 1782.6 | 1575 | 1807.4 | 1877.6 | +| IV | 1450 | 1712.4 | 1752.6 | 1805 | 2112.4 | 2152.6 | +| V | 0 | 826.4 | 846.6 | 0 | 871.4 | 891.6 | +| VI | 0 | 832.4 | 837.6 | 0 | 877.4 | 882.6 | +| VII | 2100 | 2502.4 | 2567.6 | 2175 | 2622.4 | 2687.6 | +| VIII | 340 | 882.4 | 912.6 | 340 | 927.4 | 957.6 | +| IX | 0 | 1752.4 | 1782.4 | 0 | 1847.4 | 1877.4 | +| X | 1135 | 1712.4 | 1767.6 | 1490 | 2112.4 | 2167.6 | +| XI | 733 | 1430.4 | 1450.4 | 736 | 1478.4 | 1498.4 | +| XII | -22 | 700.4 | 713.6 | -37 | 730.4 | 743.6 | +| XIII | 21 | 779.4 | 784.6 | -55 | 748.4 | 753.6 | +| XIV | 12 | 790.4 | 795.6 | -63 | 760.4 | 765.6 | +| XIX | 770 | 832.4 | 842.6 | 735 | 877.4 | 887.6 | +| XX | -23 | 834.4 | 859.6 | -109 | 793.4 | 818.6 | +| XXI | 1358 | 1450.4 | 1460.4 | 1326 | 1498.4 | 1508.4 | +| XXII | 2525 | 3412.4 | 3487.6 | 2580 | 3512.4 | 3587.6 | +| XXV | 875 | 1852.4 | 1912.6 | 910 | 1932.4 | 1992.6 | +| XXVI | -291 | 816.4 | 846.6 | -291 | 861.4 | 891.6 | +| XXXII | - | N/A | N/A | 131 | 1454.4 | 1493.6 | + +**Table 5.4: UARFCN definition (additional channels)** + +| Band | UPLINK (UL)
UE transmit, Node B receive | | DOWNLINK (DL)
UE receive, Node B transmit | | +|-------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| | UARFCN
formula offset
$F_{UL\_Offset}$ [MHz] | Carrier frequency [MHz]
( $F_{UL}$ ) | UARFCN
formula offset
$F_{DL\_Offset}$ [MHz] | Carrier frequency [MHz]
( $F_{DL}$ ) | +| I | - | - | - | - | +| II | 1850.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5 | 1850.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5 | +| III | - | - | - | - | +| IV | 1380.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5 | 1735.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5 | +| V | 670.1 | 826.5, 827.5, 831.5,
832.5, 837.5, 842.5 | 670.1 | 871.5, 872.5, 876.5,
877.5, 882.5, 887.5 | +| VI | 670.1 | 832.5, 837.5 | 670.1 | 877.5, 882.5 | +| VII | 2030.1 | 2502.5, 2507.5, 2512.5,
2517.5, 2522.5, 2527.5,
2532.5, 2537.5, 2542.5,
2547.5, 2552.5, 2557.5,
2562.5, 2567.5 | 2105.1 | 2622.5, 2627.5, 2632.5,
2637.5, 2642.5, 2647.5,
2652.5, 2657.5, 2662.5,
2667.5, 2672.5, 2677.5,
2682.5, 2687.5 | +| VIII | - | - | - | - | +| IX | - | - | - | - | +| X | 1075.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5,
1757.5, 1762.5, 1767.5 | 1430.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5,
2157.5, 2162.5, 2167.5 | +| XI | - | - | - | - | +| XII | -39.9 | 700.5, 701.5, 706.5,
707.5, 712.5, 713.5 | -54.9 | 730.5, 731.5, 736.5, 737.5,
742.5, 743.5 | +| XIII | 11.1 | 779.5, 784.5 | -64.9 | 748.5, 753.5 | +| XIV | 2.1 | 790.5, 795.5 | -72.9 | 760.5, 765.5 | +| XIX | 755.1 | 832.5, 837.5, 842.5 | 720.1 | 877.5, 882.5, 887.5 | +| XX | - | - | - | - | +| XXI | - | - | - | - | +| XXII | - | - | - | - | +| XXV | 810.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5,
1912.5 | 845.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5,
1992.5 | +| XXVI | -325.9 | 816.5, 821.5, 826.5,
827.5, 831.5, 832.5,
836.5, 837.5, 841.5,
842.5, 846.5 | -325.9 | 861.5, 866.5, 871.5, 872.5,
876.5, 877.5, 881.5, 882.5,
886.5, 887.5, 891.5 | +| XXXII | - | - | 87.1 | 1454.5, 1459.5, 1464.5,
1469.5, 1474.5, 1479.5,
1484.5, 1489.5 | + +# 6 Output power + +Output power, $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +Rated output power, $P_{RAT}$ , of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 Maximum output power + +Maximum output power, $P_{max}$ , of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition. + +### 6.1.1 Minimum Requirements + +The requirements shall apply at maximum gain, with WCDMA signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. + +When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met. + +In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +**Table 6.1: Repeater output power; normal conditions** + +| Rated output power | Limit | +|----------------------|-----------------| +| $P \geq 43$ dBm | +2 dB and -2 dB | +| $39 \leq P < 43$ dBm | +2 dB and -2 dB | +| $31 \leq P < 39$ dBm | +2 dB and -2 dB | +| $P < 31$ dBm | +3 dB and -3 dB | + +In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|----------------------|---------------------| +| $P \geq 43$ dBm | +2,5 dB and -2,5 dB | +| $39 \leq P < 43$ dBm | +2,5 dB and -2,5 dB | +| $31 \leq P < 39$ dBm | +2,5 dB and -2,5 dB | +| $P < 31$ dBm | +4 dB and -4 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. + +# 7 Frequency stability + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +## 7.1 Minimum requirement + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ ppm. + +# 8 Out of band gain + +Out of band gain refers to the gain of the repeater outside the pass band. + +## 8.1 Minimum requirement + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is this the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last 5 MHz channel within the pass band. + +**Table 8.1: Out of band gain limits 1** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $2,7 \leq f\_offset < 3,5$ MHz | 60 dB | +| $3,5 \leq f\_offset < 7,5$ MHz | 45 dB | +| $7,5 \leq f\_offset < 12,5$ MHz | 45 dB | +| $12,5$ MHz $\leq f\_offset$ | 35 dB | + +For $12,5$ MHz $\leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) | +| NOTE 1: The out of band gain is considered with $12,5$ MHz $\leq f\_offset$ | | + +# 9 Unwanted emission + +Unwanted emissions consist of out-of-band emissions and spurious emissions [1]. Out of band emissions are unwanted emissions immediately outside the pass band bandwidth resulting from the modulation process and non-linearity in the transmitter, but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The out-of-band emissions requirement for repeater is specified both in terms operating band unwanted emissions and protection of the BS receiver in the operating band. The Operating band unwanted emissions define all unwanted emissions in the repeater operating band plus the frequency ranges 10 MHz above and 10 MHz below that band. Unwanted emissions outside of this frequency range are limited by a spurious emissions requirement. + +## 9.1 Out of band emission + +### 9.1.1 Void + +### 9.1.2 Operating band unwanted emissions + +Operating band unwanted emissions comprise an emission mask applied outside the repeater passband and a general requirement applied outside the mask but inside the frequency range of the operating band unwanted emissions. + +The general operating band unwanted emissions limits are given in table 9.0. + +**Table 9.0: General operating band unwanted emissions requirements** + +| Frequency range of operating band | Category A | Category B | Measurement bandwidth | Notes | +|-----------------------------------|------------|------------|-----------------------|-------| +| $\leq 1$ GHz | -13 dBm | -16 dBm | 100 kHz | 1,2 | +| $\geq 1$ GHz | -13 dBm | -15 dBm | 1 MHz | 2,3 | + +NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1. + +NOTE 2: Limit based on ITU-R Recommendation SM.329 [1], s4.3 and Annex 7. + +NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1. + +The mask defined in tables 9.1 to 9.4 below may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions where this clause applies, the requirement shall be met by a repeater's RF-signal output at maximum gain with WCDMA signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +Emissions shall not exceed the maximum level specified in tables 9.1 to 9.4 for the appropriate repeater maximum output power, in the frequency range from $\Delta f = 2,5$ MHz to $\Delta f_{max}$ from the 5 MHz channel, where: + +- $\Delta f$ is the separation between the centre frequency of first or last 5 MHz channel used in the pass band and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the centre frequency of first or last 5 MHz channel in the pass band and the centre of the measuring filter. +- $f\_offset_{max}$ is 12,5 MHz. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measurement filter. + +![Figure 9.1: Illustrative diagram of emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 2.5, 2.7, 3.5, and 7.5. The mask is defined by three power levels: P = 43 dBm (0 dBm on the right axis), P = 39 dBm (-4 dBm on the right axis), and P = 31 dBm (-12 dBm on the right axis). The mask starts at -15 dBm for Δf < 2.7 MHz, then decreases linearly to -35 dBm at Δf = 3.5 MHz, and then steps down to -40 dBm for Δf > 3.5 MHz. Arrows indicate the corresponding power levels on the right y-axis.](89dcb02be40d2949bb93de93bbf213d5_img.jpg) + +Figure 9.1: Illustrative diagram of emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 2.5, 2.7, 3.5, and 7.5. The mask is defined by three power levels: P = 43 dBm (0 dBm on the right axis), P = 39 dBm (-4 dBm on the right axis), and P = 31 dBm (-12 dBm on the right axis). The mask starts at -15 dBm for Δf < 2.7 MHz, then decreases linearly to -35 dBm at Δf = 3.5 MHz, and then steps down to -40 dBm for Δf > 3.5 MHz. Arrows indicate the corresponding power levels on the right y-axis. + +Figure 9.1: Illustrative diagram of emission mask + +Table 9.1: Emission mask values, maximum output power $P \geq 43$ dBm + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------| +| $2,5$ MHz $\leq \Delta f < 2,7$ MHz | $2,515$ MHz $\leq f\_offset < 2,715$ MHz | -14 dBm | 30 kHz | +| $2,7$ MHz $\leq \Delta f < 3,5$ MHz | $2,715$ MHz $\leq f\_offset < 3,515$ MHz | $-14$ dBm $- 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right)$ dB | 30 kHz | +| (Note 1) | $3,515$ MHz $\leq f\_offset < 4,0$ MHz | -26 dBm | 30 kHz | +| $3,5$ MHz $\leq \Delta f \leq f_{max}$ | $4,0$ MHz $\leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | + +**Table 9.2: Emission mask values, maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -26 dBm | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -13 dBm | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +**Table 9.3: Emission mask values, maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 53 \text{ dB}$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $P - 53 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 65 \text{ dB}$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 52 \text{ dB}$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +**Table 9.4: Emission mask values, maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -22 dBm | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -34 dBm | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -21 dBm | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -25 dBm | 1 MHz | + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the applicable additional requirement in Tables 9.4A, 9.4B or 9.4C apply in addition to the minimum requirements in Tables 9.1 to 9.4. + +**Table 9.4A: Additional emission mask values for Bands II, IV, X, XXV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $4.0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | + +**Table 9.4B: Additional emission mask values for Band V and XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3.55 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 100 kHz | + +**Table 9.4C: Additional emission mask values for Bands XII, XIII, XIV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.615 \text{ MHz}$ | -13 dBm | 30 kHz | +| $2.6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $2.65 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 100 kHz | + +In certain regions the following requirement may apply for protection of DTT. For UTRA Repeater operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{filter}$ according to Table 9.4.D, shall not exceed the maximum emission level $P_{EM,N}$ declared by the manufacturer. + +**Table 9.4.D: Declared emissions levels for protection of DTT** + +| Filter centre frequency, $F_{filter}$ | Measurement bandwidth | Declared emission level [dBm] | +|-----------------------------------------------------------------------|-----------------------|-------------------------------| +| $F_{filter} = 8 \cdot N + 306 \text{ (MHz)}$ ;
$21 \leq N \leq 60$ | 8 MHz | $P_{EM,N}$ | + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the repeater needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in TS 25.104 [6] Annex D. + +Note for Tables 9.1, 9.2, 9.3, 9.4, 9.4A, 9.4B and 9.4C: + +NOTE 1: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +In certain regions, the following requirements may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to Table 9.4E shall neither exceed the maximum emission level $P_{EM,B32,a}$ , $P_{EM,B32,b}$ nor $P_{EM,B32,c}$ declared by the manufacturer. + +**Table 9.4E: Declared operating band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission level [dBm] | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------------| +| 5 MHz | $P_{EM,B32,a}$ | 5 MHz | +| 10 MHz | $P_{EM,B32,b}$ | 5 MHz | +| $15\text{ MHz} \leq f\_offset \leq f\_offset_{max,B32}$ | $P_{EM,B32,c}$ | 5 MHz | +| NOTE: $f\_offset_{max,B32}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE: The regional requirement, included in [7], is defined in terms of EIRP per antenna, which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [8]. + +In certain regions, the following requirement may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to Table 9.4F shall neither exceed the maximum emission level $P_{EM,B32,d}$ nor $P_{EM,B32,e}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 9.4F: Operating band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared emission level [dBm] | Measurement bandwidth | +|------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5\text{ MHz} \leq F_{filter} \leq 1448.5\text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | +| $F_{filter} = 1450.5\text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $F_{filter} = 1493.5\text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $1495.5\text{ MHz} \leq F_{filter} \leq 1517.5\text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | + +NOTE: The regional requirement, included in [7], is defined in terms of EIRP, which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [8]. + +### 9.1.3. Protection of the BS receiver in the operating band + +This requirement shall be applied for the protection of UTRA FDD BS receiver in geographic areas in which UTRA-FDD Repeater and UTRA-FDD BS are deployed. + +The requirement applies outside the emission mask. + +#### 9.1.3.1 Minimum Requirement + +This requirement applies to the uplink of the repeater, at maximum gain. + +The power of any operating band unwanted emission shall not exceed the limits in Table 9.7A. + +**Table 9.7A: Uplink operating band unwanted emissions limits for protection of the BS receiver** + +| Maximum Level | Measurement Bandwidth | Note | +|---------------|-----------------------|------| +| -53 dBm | 100 kHz | | + +NOTE 1: These requirements in Table 9.7A: for the uplink direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA FDD BS receiver. + +NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses. + +NOTE 3: The protection of R-GSM is for further study. + +### 9.1.4 Co-existence with services in adjacent frequency bands + +This requirement may be applied for the protection in bands adjacent to bands I, or VII, as defined in clause 5.1 in geographic areas in which both an adjacent band service and UTRA are deployed. + +The requirement applies only to the down-link direction of the repeater. + +#### 9.1.4.1 Minimum requirement + +The power of any spurious emission shall not exceed: + +**Table 9.16: UTRA Repeater down-link spurious emissions limits for protection of adjacent band services** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|------------------------------------------------|-----------------------|------| +| I | 2100-2105 MHz | $-30 + 3.4 (f - 2100 \text{ MHz}) \text{ dBm}$ | 1 MHz | | +| | 2175-2180 MHz | $-30 + 3.4 (2180 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | | +| VII | 2610-2615 MHz | $-30 + 3.4 (f - 2610 \text{ MHz}) \text{ dBm}$ | 1 MHz | | +| | 2695-2700 MHz | $-30 + 3.4 (2700 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | | + +## 9.2 Spurious emissions + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the repeaters RF output port. + +The spurious emission limits apply from 9 kHz to 12.75 GHz (or above, as indicated in Table 9.5 and 9.5A), excluding the frequency range from 10 MHz below the lowest frequency of the repeaters operating band up to 10 MHz above the highest frequency of the repeaters operating band. Exceptions are the requirement in Table 9.13 and 9.16 that apply also closer than 10 MHz from repeaters operating band. + +Unless otherwise stated, all requirements are measured as mean power. + +### 9.2.1 General Requirements + +The requirements of either subclause 9.2.1.1 or subclause 9.2.1.2 shall apply whatever the type of repeater considered (one or several pass bands). It applies for all configurations foreseen by the manufacturer's specification. + +#### 9.2.1.1 Minimum Requirement (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. + +At maximum repeater gain, with WCDMA signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel, the power of any spurious emission shall not exceed the limits specified in table 9.5. The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +When the power in all channels is increased by 10 dB, compared to the input level producing the maximum rated output power, the requirement shall still be met. + +**Table 9.5: Up-link and down-link: General spurious emissions limits, Category A** + +| Band | Maximum level | Measurement Bandwidth | Note | | +|----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------|--| +| 9kHz - 150kHz | -13 dBm | 1 kHz | Note 1 | | +| 150kHz - 30MHz | | 10 kHz | Note 1 | | +| 30MHz - 1GHz | | 100 kHz | Note 1 | | +| 1GHz - 12,75 GHz | | 1 MHz | Note 2 | | +| 12,75GHz – 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | | 1 MHz | Note 2, Note 3 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [1], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [1], s2.5 table 1 | | | | | +| NOTE 3: Applies only for Band XXII | | | | | + +#### 9.2.1.2 Minimum Requirement (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. + +At maximum repeater gain, with WCDMA signals in the pass band of the repeater, at levels that produce the maximum rated power output per channel, the power of any spurious emission shall not exceed the limits specified in table 9.5A for the down- and up-link. + +The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +When the power in all channels is increased by 10 dB, compared to the input level producing the maximum rated output power, the requirement shall still be met. + +**Table 9.5A: General spurious emissions limits (Category B)** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------| +| 9 kHz ↔ 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz ↔ 30 MHz | -36 dBm | 10 kHz | Note 1 | +| 30 MHz ↔ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz ↔ 12.75 GHz | -30 dBm | 1 MHz | Note 2 | +| 12.75 GHz ↔ 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | -30 dBm | 1 MHz | Note 2, Note 3 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1 | | | | +| NOTE 2: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1 | | | | +| NOTE 3: Applies only for Band XXII | | | | + +**Table 9.6: (Void)****Table 9.6A: (Void)****Table 9.6B: (Void)****Table 9.6C: (Void)****Table 9.6D: (Void)****Table 9.6E: (Void)****Table 9.6F: (Void)** + +### 9.2.2 Void + +### 9.2.3 Co-existence with other systems in the same geographical area + +These requirements may be applied for the protection of UE, MS and/or BS operating in other frequency bands in the same geographical area. The requirements may apply in geographic areas in which both UTRA FDD Repeater and a system operating in another frequency band than the FDD operating band are deployed. The system operating in the other frequency band may be GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD. + +#### 9.2.3.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.9 for a UTRA FDD Repeater where requirements for co-existence with the system listed in the first column apply. + +**Table 9.9: UTRA Repeater up-link and down-link spurious emissions limits in geographic coverage area of systems operating in other frequency bands** + +| System type operating in the same geographic area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|---------------------------------------------------|-----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII | +| | 876 - 915 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3 | +| DCS1800 | 1805 - 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band III. | +| | 1710 - 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3. | +| PCS1900 | 1930 - 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band II or band XXV. | +| | 1850 - 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. | +| GSM850 or CDMA850 | 869 - 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band V or XXVI. | +| | 824 - 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band V or XXVI, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band I or E-UTRA Band 1 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I. | +| | 1920 - 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band II or E-UTRA Band 2 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| | 1850 - 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band III or E-UTRA Band 3 | 1805 - 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. | +| | 1710 - 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency Range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in clause 9.1.3. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. | +| | 1710 - 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band V or E-UTRA Band 5 | 869 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI. | +| | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V or XXVI, since it is already covered by the requirement in sub-clause 9.1.3. | +| | 860 - 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | +| | 815 - 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | + +| | | | | | +|----------------------------------------------------|---------------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 830 – 845 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V, XX or XXVI. | +| UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| | 2500 - 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band VIII or E-UTRA Band 8 | 925 - 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII. | +| | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. | +| | 1749.9 - 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. | +| | 1710 - 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band X, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IV in the frequency Range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in clause 9.1.3. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, band XXI or XXXII. | +| | 1427.9 - 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 9.1.3. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| | 1447.9 - 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 9.1.3. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| UTRA FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII. | +| | 777 - 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV. | +| | 788 - 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 9.1.3. | +| E-UTRA Band 17 | 734 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. | +| | 704 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. | +| | 791 - 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX. | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIII, since it is already covered by the band XX requirement in sub-clause 9.1.3. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band XXII. | +| | 3410 - 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to the uplink of the UTRA FDD repeater operating in band XXII, since it is already covered by the requirement in sub-clause 9.1.3. | +| E-UTRA Band 23 | 2180 - 2200 MHz | -52 dBm | 1 MHz | | +| | 2000 - 2020 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, where the limits are defined separately. | +| | 2000 – 2010 MHz | -30 dBm | 1 MHz | This requirement only applies to UTRA FDD Repeater operating in band II or band XXV. This requirement applies starting 5 MHz above the band XXV DL operating band. | +| | 2010 – 2020 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band II or band XXV. | +| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD repeater operating in band XXV since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD repeater operating in band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in sub-clause 9.1.3. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band V or band XXVI. | +| | 814 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD repeater operating in band XXVI since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD repeater operating in band V, it applies for 814 MHz to 824 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 27 | 852 - 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band V or band XXVI. | +| | 807 - 824 MHz | -49 dBm | 1 MHz | For UTRA FDD repeater operating in band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 28 | 758 - 803 MHz | -52 dBm | 1 MHz | | +| | 703 - 748 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 29 | 717 – 728 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA repeater operating in Band XI, XXI, or XXXII | +| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 5.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +### 9.2.4 Co-existence with co-located and co-sited Base Stations + +These requirements may be applied for the protection of other BS receivers when GSM900 and/or DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater. + +#### 9.2.4.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.10 for a UTRA FDD Repeater where requirements for co-location with the Base Station listed in the first column apply. + +**Table 9.10: UTRA Repeater up-link and down-link spurious emissions limits for Repeater co-located with Base Stations** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 - 915 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| DCS1800 | 1710 - 1785 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| PCS1900 | 1850 - 1910 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band I. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band II or E-UTRA Band 2 | 1850 - 1910 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency Range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band IV or band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 - 830 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | +| | 830 – 845 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, XX or XXVI. | + +| | | | | | +|-------------------------------------------------|---------------------|---------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band VIII or E-UTRA Band 8 | 880 - 915 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III or band IX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement does not apply to the uplink of E-UTRA FDD Repeater operating in band IV in the frequency range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1427.9 - 1447.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| | 1447.9 - 1462.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| UTRA FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 17 | 704 - 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XX or E-UTRA Band 20 | 832 – 862 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 23 | 2000 - 2020 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 24 | 1626.5 - 1660.5 MHz | -96 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 | 1850 - 1915 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. For UTRA FDD Repeater operating in band 2, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 814 – 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. For UTRA FDD Repeater operating in band V, it applies from 814 MHz to 824MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 27 | 807 – 824 MHz | -96 dBm | 100 kHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807 MHz to 814MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 28 | 703 – 748 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 30 | 2305 – 2315 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 31 | 452.5 – 457.5 MHz | -96 dBm | 100 kHz | | +| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeater operating band (see Table 5.1). The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB UTRA Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +### 9.2.5 Co-existence with PHS + +This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA-FDD Repeaters are deployed. This requirement is also applicable at specified frequencies falling between 12,5 MHz below the centre frequency of the first 5 MHz channel or more than 12,5 MHz above the centre frequency of the last 5 MHz channel in the pass band. + +#### 9.2.5.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.13: UTRA Repeater up-link and down-link spurious emissions limits for in geographic coverage area of PHS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|------| +| 1884,5 - 1915,7 MHz | -41 dBm | 300 kHz | | + +### 9.2.6 Co-existence with UTRA-TDD and/or E-UTRA TDD + +#### 9.2.6.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and/or E-UTRA TDD and UTRA-FDD Repeaters are deployed. + +##### 9.2.6.1.1 Minimum Requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.14: UTRA Repeater down-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD** + +| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | | +| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +In the up-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.14A: UTRA Repeater up-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD** + +| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. | +| | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. | +| | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. | +| | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | | +| NOTE 3: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 4: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +NOTE 1: The requirements of -53dBm/100kHz in Table 9.14 and Table 9.14A, which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses. + +#### 9.2.6.2 Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations + +This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD BS and UTRA-FDD Repeater are co-located. + +##### 9.2.6.2.1 Minimum Requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.15: UTRA Repeater down-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|-------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -86 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -86 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -86 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920 MHz | -86 dBm | 1 MHz | Applicable in China | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| E-UTRA Band 42 | 3400 - 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -86 dBm | 1 MHz | | +| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +In the up-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.15A: UTRA Repeater up-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. | +| | 1900 - 1920 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -83 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I. | +| | 2010 - 2025 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. | +| | 2570 - 2620 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. | +| | 1880 – 1920 MHz | -86 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -86 dBm | 1 MHz | | +| NOTE 4: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 5: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | | + +NOTE 1: The requirements of -53dBm/100kHz in Table 9.15 and Table 9.15A , which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 2: The requirements of -83dBm/100kHz in Table 9.15A for the up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 43 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 3: The requirements shall be reconsidered when the state of the art technology progresses. + +### 9.2.7 Void + +### 9.2.8 Protection of public safety operations + +This requirement shall be applied to Repeater operating in Bands XIII and XIV to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at specified frequencies falling between 12.5 MHz below the first carrier frequency used and 12.5 MHz above the last carrier frequency used. + +#### 9.2.8.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.16: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 700 MHz public safety operations** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|---------------|-----------------------|------| +| XIII | 763 - 775 MHz | -46 dBm | 6.25 kHz | | +| XIII | 793 - 805 MHz | -46 dBm | 6.25 kHz | | +| XIV | 769 - 775 MHz | -46 dBm | 6.25 kHz | | +| XIV | 799 - 805 MHz | -46 dBm | 6.25 kHz | | + +This requirement shall be applied to repeaters operating in Band XXVI to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at specified frequencies falling between 12.5 MHz below the first carrier frequency used and 12.5 MHz above the last carrier frequency used. + +The power of any spurious emission shall not exceed: + +**Table 6.16A: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 800 MHz public safety operations** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|---------------|-----------------------|--------------------------------------------------------| +| XXVI | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +# 10 Modulation accuracy + +## 10.1 Error Vector Magnitude + +The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 3.84 MHz and roll-off $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %. + +The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal WCDMA signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer. + +### 10.1.1 Minimum requirement + +The Error Vector Magnitude shall not be worse than 12,5 %. + +## 10.2 Peak code domain error + +The peak code domain error is computed by projecting the power of the error vector (as defined in subclause 10.1) onto the code domain at a specified spreading factor. The code domain error for every code in the domain is defined as the ratio of the mean power of the projection onto that code, to the mean power of the composite reference waveform. This ratio is expressed in dB. The peak code domain error is defined as the maximum value for the code domain error for all codes. The measurement interval is one power control group (timeslot). + +### 10.2.1 Minimum requirement + +The peak code domain error shall not exceed -35 dB at spreading factor 256. + +## 10.3 Relative Code Domain Error (RCDE) for 64QAM modulation + +The Relative Code Domain Error is computed by projecting the error vector (as defined in 10.1) onto the code domain at a specified spreading factor. Only the active code channels in the composite reference waveform are considered for this requirement. The Relative Code Domain Error for every active code is defined as the ratio of the mean power of the error projection onto that code, to the mean power of the active code in the composite reference waveform. This ratio is expressed in dB. The measurement interval is one frame. + +The requirement for Relative Code Domain Error is only applicable for Repeater supporting 64QAM modulated codes. + +### 10.3.1 Minimum requirement + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -21 dB at spreading factor 16. + +# --- 11 Input Intermodulation + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 General Requirement + +The following requirement applies for interfering signals in the frequency bands defined in sub-clause 5.1, depending on the repeaters pass band. The requirement shall be met with the repeater operating at maximum gain. + +### 11.1.1 Minimum requirement + +For the parameters specified in table 11.1, the power in the pass band, shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the 3rd order intermodulation product is positioned in the centre of the pass band. + +Table 11.1 specifies the parameters for two interfering signals, where: + +- $f\_offset$ is the separation between the centre frequency of first or last 5 MHz channel in the pass band and one the interfering signals. + +**Table 11.1: Input intermodulation requirement** + +| f_offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|-----------------|----------------------------------|------------------------|------------------------------| +| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +## 11.2 Co-location with BS in other systems + +The requirement shall be met with the repeater operating at maximum gain. + +### 11.2.1 Minimum requirements - Co-location with GSM, DCS, PCS, UTRA FDD and/or E-UTRA FDD + +This additional input intermodulation requirement may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater. + +For the parameters specified in table 11.2, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation product corresponds to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.2: Input intermodulation requirements for interfering signals in other systems** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| DCS1800 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| PCS1900 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| GSM850 or CDMA850 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band I or E-UTRA Band 1 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band V or E-UTRA Band 5 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 - 890 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI, XIX or XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|-------------------------------------------------|---------------------|---------|---------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 - 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. This requirement does not apply to UTRA FDD Repeater operating in band XXXII, between 1475.9 MHz and 1496 MHz, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 17 | 734 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|---------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 23 | 2180 - 2200 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1525 – 1559 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band II, it applies from 1990MHz to 1995MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band V, it applies from 859 MHz to 869 MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 27 | 852 - 869 MHz | +16 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies from 852 MHz to 859 MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 28 | 758 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 29 | 717 - 728 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, XXI or XXXII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| NOTE 1: The co-location requirements in the table 11.2 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the table 11.2. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]. | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +### 11.2.2 Minimum Requirement - Co-location with UTRA-TDD and/or E-UTRA TDD + +An additional input intermodulation requirement may be applied for the protection of FDD BS receivers when UTRA TDD and/or E-UTRA TDD is co-located with a UTRA FDD Repeater. + +The requirements in this chapter assume a 30 dB coupling loss between transmitter and receiver. + +The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-Repeater minimum coupling loss. + +However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]. + +**Table 11.2A: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-located other system | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|----------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA-TDD Band d) or E-UTRA TDD Band 38 | 2570 - 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 41 | 2496 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 42 | 3400 - 3600 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 43 | 3600 - 3800 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 44 | 703 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | + +NOTE 1: The co-location requirements in Table 11.2A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.2A. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5] + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +## 11.3 Co-existence with other systems + +The following requirement may be applied when GSM 900, DCS 1800, PCS1900, GSM850, E-UTRA FDD, E-UTRA TDD BS and/or UTRA FDD, UTRA TDD BS operating in another frequency band and UTRA-FDD Repeaters co-exist. The requirement shall be met with the repeater operating at maximum gain. + +### 11.3.1 Minimum requirements + +For the parameters specified in table 11.3 and table 11.3A, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation product corresponds to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.3: Input intermodulation requirements for interfering signals in other systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 - 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.1. | +| DCS1800 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.1. | +| PCS1900 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.1. | +| GSM850 or CDMA850 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 - 8845 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.1. This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V or XX. | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 880 - 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1749,9 - 1784,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1427.9 - 1447.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 11.1. | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1447.9 - 1462.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 11.1. For UTRA FDD Repeater operating in band XXXII, it applies from 1447.9 MHz to 1452 MHz, while the rest is covered in sub-clause 11.1. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.1. | +| E-UTRA Band 17 | 704 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.1. | +| E-UTRA Band 23 | 2000 - 2020 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1626.5 - 1660.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1850 - 1915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.1. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 11.1. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 814 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.1. For UTRA FDD Repeater operating in band V, it applies from 814MHz to 824 MHz, while the rest is covered in sub-clause 11.1. | +| E-UTRA Band 27 | 807 - 824 MHz | -15 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807MHz to 814 MHz, while the rest is covered in sub-clause 11.1. | +| E-UTRA Band 28 | 703 - 748 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2305 - 2315 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 452.5 - 457.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| NOTE 1: The co-existence requirements in Table 11.3 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 11.3. The current state-of-the-art technology does not allow a single generic solution for co-existence. | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +**Table 11.3A: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|--------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-TDD Band d) and or E-UTRA TDD Band 38 | 2570 – 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -15 dBm | 2 CW carriers | 1 MHz | Applicable in China.
This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 42 | 3400 - 3600 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 44 | 703 - 803 MHz | -15 dBm | 2 CW carriers | 1 MHz | | + +NOTE 1: The co-existence requirements in Table 11.3A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.3A. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5] + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +# 12 Output intermodulation + +The output intermodulation requirement is a measure of the ability of the repeater to inhibit the generation of intermodulation products signals created by the presence of an interfering signal reaching the repeater via the output port. + +The output intermodulation level is the power of the intermodulation products when a WCDMA modulated interference signal is injected into the output port at a level of 30 dB lower than that of the wanted signal. The frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the wanted signal, but within the frequency band allocated for UTRA FDD downlink as specified in subclause 4.1. + +The requirement is applicable for downlink signals. + +## 12.1 Minimum requirement + +The output intermodulation level shall not exceed the out of band emission or the spurious emission requirements of section 9.1 and 9.2. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. + +The requirement shall apply to the Uplink and Downlink of Repeater where the donor link is maintained via antennas (over the air Repeater). + +## 13.2 Minimum Requirements + +In normal conditions the ACRR shall be higher than the value specified in the Table 13.1. + +**Table 13.1: Repeater ACRR** + +| Repeater maximum output power as in 9.1.1 | Channel offset from the centre frequency of the first or last 5 MHz channel within the pass band. | ACRR limit | +|-------------------------------------------|---------------------------------------------------------------------------------------------------|------------| +| $P \geq 31$ dBm | 5 MHz | 33dB | +| $P \geq 31$ dBm | 10 MHz | 33dB | +| $P < 31$ dBm | 5 MHz | 20dB | +| $P < 31$ dBm | 10 MHz | 20dB | + +# --- Annex A (informative): Change History + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|------------------------------------------------------------------------------------------------------------------------------------------| +| RP-31 | | | | Rel-7 version created; based on v6.4.0 | | | 7.0.0 | | +| RP-31 | RP-060100 | 0042 | 2 | Introduction of operating band III to IX requirements in 25.106 | B | 6.3.0 | 7.0.0 | TEI7 | +| RP-31 | RP-060110 | 0043 | | Correction of spurious emissions for coexistence with GSM900 in same geographic area | F | 6.3.0 | 7.0.0 | RlnImp-UMTS900 | +| RP-33 | RP-060520 | 0046 | 1 | Clean up of Spurious emissions | A | 7.0.0 | 7.1.0 | TEI5 | +| RP-33 | RP-060521 | 0049 | 1 | New UTRA Repeater up-link spurious emissions limits for co-existence/co-location with TDD | A | 7.0.0 | 7.1.0 | TEI5 | +| RP-34 | RP-060811 | 0052 | 1 | Corrections to input intermodulation | A | 7.1.0 | 7.2.0 | TEI5 | +| RP-36 | RP-070370 | 0056 | | Category B spurious emission limits for UTRA Repeater | A | 7.2.0 | 7.3.0 | TEI4 | +| RP-36 | RP-070373 | 0057 | | Introduction of operating band X into the repeater specification | B | 7.2.0 | 7.3.0 | TEI7 | +| RP-39 | RP-080126 | 0058 | | Introduction of UMTS1500 requirements | B | 7.3.0 | 8.0.0 | RlnImp8-UMTS1500 | +| | | | | Minor correction to CR implementation | | 8.0.0 | 8.0.1 | | +| | | | | Update of history table | | 8.0.1 | 8.0.2 | | +| RP-42 | RP-080943 | 60 | 1 | Introduction of operating band unwanted emission | F | 8.0.2 | 8.1.0 | TEI8 | +| RP-45 | RP-080819 | 61 | | Introduction of band XII, XIII, XIV | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-45 | RP-080819 | 62 | | CR to limit the scope to FDD only to 25.106 | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-46 | RP-091277 | 063 | | Corrections on additional spectrum emission limits for Bands XII, XIII, XIV | F | 8.2.0 | | TEI8 | +| | | | | Automatic upgrade from previous Release | | 8.3.0 | 9.0.0 | TEI9 | +| RP-49 | RP-100925 | 064 | | Introduction of operating band XIX, XX and XXI and correction of band XI | F | 9.0.0 | 9.1.0 | TEI9 | +| RP-49 | RP-100913 | 067 | 1 | RCDE for 64QAM modulated codes for FDD Repeater | A | 9.0.0 | 9.1.0 | TEI7 | +| RP-50 | RP-101336 | 072 | | Protection of cdma and E-UTRA bands | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101337 | 074 | | Removal of brackets | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101347 | 068 | | Remove test settings for unwanted emissions from core spec | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 069 | | Corrections to the symbols and abbreviations clause related to DTT requirement | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 070 | | Co-existence with services in adjacent frequency bands | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-51 | RP-110352 | 0075 | - | Inclusion of E-UTRA TDD text to co-location on 25.106 | F | 9.2.0 | 10.0.0 | TEI10 | +| RP-55 | RP-120303 | 078 | 1 | Correction on the table of Regional requirements | F | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 079 | 1 | Introduction of operating frequency band XXII | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 080 | 1 | Introduction of operating frequency band XXV and protection limits towards E-UTRA Band 23 | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-56 | RP-120783 | 082 | 2 | Update of the Definition clause with repeaters operating band definition and introduction of minor editorial changes for better alignment with BS core specification | F | 10.1.0 | 10.2.0 | TEI10 | +| RP-56 | RP-120765 | 085 | | Additional spurious emissions requirements for PHS | A | 10.1.0 | 10.2.0 | TEI8 | +| RP-57 | RP-121313 | 088 | 2 | Introduction of missing Spurious Emission limits and Input Intermodulation requirements towards E-UTRA FDD Band 24 | F | 10.2.0 | 10.3.0 | TEI10 | +| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.3.0 | 11.0.0 | - | +| RP-58 | RP-121867 | 095 | | Introduction of Spurious Emission limits and Input Intermodulation requirements towards missing UTRA and E-UTRA TDD frequency bands | A | 11.0.0 | 11.1.0 | TEI10 | +| RP-58 | RP-121867 | 096 | | Introduction of a Note on non deployment of operating bands with overlapping frequency ranges for the tables for Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | TEI10 | +| RP-58 | RP-121858 | 097 | | Modifications of frequency ranges for E-UTRA Band 6, 18, 19 in the Tables for Spurious Emission limits and Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | RlnImp9-UMTSLTE800 | +| RP-58 | RP-121867 | 100 | | The special cases for protection of UTRA Band III and Band X in co-existence and co-location with UTRA Repeaters | A | 11.0.0 | 11.1.0 | TEI10 | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.1.0 | 12.0.0 | | +| RP-66 | RP-142154 | 103 | | Update with regard to operating bands of TS25.106 | F | 12.0.0 | 12.1.0 | LTE_UTRA_SDL_BandL-Core, LTE450_Brazil-Core, LTE_WCS_b and-Core, LTE_DL_FD D700-Core, LTE_APAC7 00-Core, LTE_e850_L B-Core, E850_UB-Core | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.1.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | - | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25141/107cbeda15ddd53da92c2f677b441c93_img.jpg b/marked/Rel-16/25_series/25141/107cbeda15ddd53da92c2f677b441c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67be74325a95159a2dd3c32c4a96094f7c61c62f --- /dev/null +++ b/marked/Rel-16/25_series/25141/107cbeda15ddd53da92c2f677b441c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a1b42451f6b84ea191958f4a7f0227588217d89cd710798958361ceb35432dc +size 66687 diff --git a/marked/Rel-16/25_series/25141/20e1585db1a707a774877194c689de82_img.jpg b/marked/Rel-16/25_series/25141/20e1585db1a707a774877194c689de82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daeac2330e0bc3a2c506a8137e21a1f2c4623c6d --- /dev/null +++ b/marked/Rel-16/25_series/25141/20e1585db1a707a774877194c689de82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e38a7e103a40db17571c396972e7761741453ee2c7a19f1b4b5d620cc9a9321e +size 32522 diff --git a/marked/Rel-16/25_series/25141/236f674770a03c918c0375a74fe950db_img.jpg b/marked/Rel-16/25_series/25141/236f674770a03c918c0375a74fe950db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79f2c16e1a374096ba5ec165eac4113ec11cc66b --- /dev/null +++ b/marked/Rel-16/25_series/25141/236f674770a03c918c0375a74fe950db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf88da91bbf900a626f1f1726b358bb3a73ab69d747fe4cfdae10fd7c019cf4a +size 31033 diff --git a/marked/Rel-16/25_series/25141/2e8dd34433bac31ce3d0d503abd0210e_img.jpg b/marked/Rel-16/25_series/25141/2e8dd34433bac31ce3d0d503abd0210e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f3d8d606cc6a570d3d2af7ddfe8a05833ec59a2 --- /dev/null +++ b/marked/Rel-16/25_series/25141/2e8dd34433bac31ce3d0d503abd0210e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2dacdc8e6c826cf6c7f1fe6f8fa1cb0ef1e4a9437688ca71a5b10cf12ed02e6 +size 40797 diff --git a/marked/Rel-16/25_series/25141/4b8c5ecb492fd759c766fe8950fafe67_img.jpg b/marked/Rel-16/25_series/25141/4b8c5ecb492fd759c766fe8950fafe67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e39d810aa9c611685b7c9fa69b72ab616893554 --- /dev/null +++ b/marked/Rel-16/25_series/25141/4b8c5ecb492fd759c766fe8950fafe67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cb5eba86070478b47f0b2012b0cc4e235a86a3e1a2d6bf62f594ec64b26e3ce +size 4796 diff --git a/marked/Rel-16/25_series/25141/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/25_series/25141/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd8224dbd713679df1490fabe1201cad58cfeb7b --- /dev/null +++ b/marked/Rel-16/25_series/25141/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c15a63f20ec7fdc40e04d572ab4c59aa9148c40a7c4667ddbfd4f5ffe91094c +size 59516 diff --git a/marked/Rel-16/25_series/25141/a70e0adcabc973b01b413b6a141884f3_img.jpg b/marked/Rel-16/25_series/25141/a70e0adcabc973b01b413b6a141884f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b0e82574edae50f948e7a3905073d3c5fbdad2f --- /dev/null +++ b/marked/Rel-16/25_series/25141/a70e0adcabc973b01b413b6a141884f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:129a643f39a3c5188dbec30050c6f186264129d266a95d8fa0fd167854d93907 +size 151034 diff --git a/marked/Rel-16/25_series/25141/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-16/25_series/25141/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde8ed3e9f6523ed7efcbec299ec2ec296a3a205 --- /dev/null +++ b/marked/Rel-16/25_series/25141/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb4be5e38d4a807139f0a1da843b4ccd7d707c6705ff23bbdb040b247116b3d7 +size 134835 diff --git a/marked/Rel-16/25_series/25141/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg b/marked/Rel-16/25_series/25141/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d506e64f0f0526c7a61435eb5bfa0b03bc583f52 --- /dev/null +++ b/marked/Rel-16/25_series/25141/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e84c434ad56b917fd011b1d1f2c2736708601d9117184d2dc9f3ab460287e96 +size 33806 diff --git a/marked/Rel-16/25_series/25141/c5c767928d086da5347036f88309fc7a_img.jpg b/marked/Rel-16/25_series/25141/c5c767928d086da5347036f88309fc7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0965f5fd974a3cf190bf74155748b6ffc49fe4 --- /dev/null +++ b/marked/Rel-16/25_series/25141/c5c767928d086da5347036f88309fc7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8bdb3e7604456a038da9281ef39ee61325c8751bdab23b986a1739371b02d77 +size 10189 diff --git a/marked/Rel-16/25_series/25141/cf018d13814389b0bd7f94a2f9bb812a_img.jpg b/marked/Rel-16/25_series/25141/cf018d13814389b0bd7f94a2f9bb812a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0737ab0f6bd8a3cefbc405dfa6e7e28eb5019d74 --- /dev/null +++ b/marked/Rel-16/25_series/25141/cf018d13814389b0bd7f94a2f9bb812a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d0ae3d41208fafa46320a2eba0b4d686dedfdae8276fae062f7a0c4e828f9ac +size 145044 diff --git a/marked/Rel-16/25_series/25141/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-16/25_series/25141/d197b6ded14ea918198a280ff07122b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d24a52766a2d6d437853d3b12ec96ae14a4cd61f --- /dev/null +++ b/marked/Rel-16/25_series/25141/d197b6ded14ea918198a280ff07122b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c12916b78f3b7ad9df1328c7c77309a5a618a1a3c2d3ce6c64f0f87d5ea67456 +size 35947 diff --git a/marked/Rel-16/25_series/25141/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg b/marked/Rel-16/25_series/25141/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87a64a4779ac53beae14f8cfb11fe565922483ac --- /dev/null +++ b/marked/Rel-16/25_series/25141/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c7e0cab9c5e4817cc1eba08b692bd5449d4c38ed4c376786f10d4fbc72168eb +size 25537 diff --git a/marked/Rel-16/25_series/25141/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/25_series/25141/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ef3b596a8d19d2176de43fee13ec609cf3728be --- /dev/null +++ b/marked/Rel-16/25_series/25141/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db2abac545cc81f7f4c4b0d7ad325ecd2e78c95b2436dfc1983547dfe4387db0 +size 14068 diff --git a/marked/Rel-16/25_series/25141/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-16/25_series/25141/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..435434ec72d1dcc556a3706a24d85b0d662dbdee --- /dev/null +++ b/marked/Rel-16/25_series/25141/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a2890f6fc33b3d2ac85eea9f83ebb0fdbe5531865436653b3f1f2071a2814e6 +size 4815 diff --git a/marked/Rel-16/25_series/25153/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg b/marked/Rel-16/25_series/25153/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2660a8c0f900ac213f8c14d9b01648b3da53f5b --- /dev/null +++ b/marked/Rel-16/25_series/25153/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b2053a75ffeb1560211317be5df43c0bc9aeace9186554053129f90b212817 +size 22053 diff --git a/marked/Rel-16/25_series/25153/252210dd01a9d2f476bfb1c284c59ccf_img.jpg b/marked/Rel-16/25_series/25153/252210dd01a9d2f476bfb1c284c59ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22a889698801ef6e8425f405768f797a2b5c6e36 --- /dev/null +++ b/marked/Rel-16/25_series/25153/252210dd01a9d2f476bfb1c284c59ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ff6bf96ea5fac250e9dac804b31bb3f0a769ffe799b69cf3dbc4593f533cbb1 +size 16357 diff --git a/marked/Rel-16/25_series/25153/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/25_series/25153/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b915f074b0b5774b83a73efc12fe6a3d768f31c --- /dev/null +++ b/marked/Rel-16/25_series/25153/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f7bb7111f09ffde947a79a9853d82230adda64f591146a56eeeb5b033c2d4ce +size 28202 diff --git a/marked/Rel-16/25_series/25153/4ee6ee5ce67694dbc95537938e09a917_img.jpg b/marked/Rel-16/25_series/25153/4ee6ee5ce67694dbc95537938e09a917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5f69871ee13d5082b310f54ac31df95d37d67c2 --- /dev/null +++ b/marked/Rel-16/25_series/25153/4ee6ee5ce67694dbc95537938e09a917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c831976d4960bc6cd20f02a953f0f6ea69d24224daddf13c03fc5aef05e7942 +size 29695 diff --git a/marked/Rel-16/25_series/25153/5837d4aa3bb1d08bbebcd757248f5515_img.jpg b/marked/Rel-16/25_series/25153/5837d4aa3bb1d08bbebcd757248f5515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41e268945204f7eada91480abb8a43a413b92373 --- /dev/null +++ b/marked/Rel-16/25_series/25153/5837d4aa3bb1d08bbebcd757248f5515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8fc0d05d4a368866361c209d8868cbacb19d2e9d65bf6e4c806102dd0cf049c +size 19646 diff --git a/marked/Rel-16/25_series/25153/59fdf9faef450c0a4236031fb44d9faa_img.jpg b/marked/Rel-16/25_series/25153/59fdf9faef450c0a4236031fb44d9faa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f30acbd7fde72a7833a0dba9b57274d29623d16 --- /dev/null +++ b/marked/Rel-16/25_series/25153/59fdf9faef450c0a4236031fb44d9faa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837409659410631bbf2b5d3b13385c7cfc7b63a7fe2f625082d3634568e48f17 +size 29991 diff --git a/marked/Rel-16/25_series/25153/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Rel-16/25_series/25153/8d8c758885b4f754ff071bf3b572ab3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce600255736091344e876e2d92398ca2491e682e --- /dev/null +++ b/marked/Rel-16/25_series/25153/8d8c758885b4f754ff071bf3b572ab3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3e7e5321593e7769a6cf7b63db0f704cf8cb628c5db529c2bd684dc9209d146 +size 17370 diff --git a/marked/Rel-16/25_series/25153/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/25_series/25153/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26fdc097c304debfd9f1b936403bcb0ec5a7e024 --- /dev/null +++ b/marked/Rel-16/25_series/25153/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc6844b08d7a88b710d88159838f91a6e5ed7728d7c7a4e5b52c6c88ea8e9e0 +size 37080 diff --git a/marked/Rel-16/25_series/25153/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/25_series/25153/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3038fabdd6b0953669a12be0af71c998eb13bd --- /dev/null +++ b/marked/Rel-16/25_series/25153/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce745ff13e37ba319571ba0dc0b464393cbafcae3d690fe20b6f4e5de44b24ae +size 19900 diff --git a/marked/Rel-16/25_series/25153/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/25_series/25153/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29657116335049aee847237cc0ebadacd622d2b9 --- /dev/null +++ b/marked/Rel-16/25_series/25153/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c72a1f1dd61b9590e3b095dc0bad44dbaff277d2b9e0127e4baae46fb337da83 +size 16994 diff --git a/marked/Rel-16/25_series/25153/bd4c85f71b8f5e06d935a6240b6dab56_img.jpg b/marked/Rel-16/25_series/25153/bd4c85f71b8f5e06d935a6240b6dab56_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f4cceb34f7e5f7a8228dc7808d2b854a8698053 --- /dev/null +++ b/marked/Rel-16/25_series/25153/bd4c85f71b8f5e06d935a6240b6dab56_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf288f02d65b036e4819418055f567c60a884b4724700cf61066f60c33ac4ccb +size 18340 diff --git a/marked/Rel-16/25_series/25153/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/marked/Rel-16/25_series/25153/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f0db61198c577f9819e4dc2f449c01204a9981 --- /dev/null +++ b/marked/Rel-16/25_series/25153/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:245d460da3fbd8bad49274fe313846d08226a9e8dfb0de268e20d6fdcf764d75 +size 22745 diff --git a/marked/Rel-16/25_series/25153/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-16/25_series/25153/f142b022cfc716cd967297f027efe647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a2a0820b4eb8cf548272f2eada32bc82236b537 --- /dev/null +++ b/marked/Rel-16/25_series/25153/f142b022cfc716cd967297f027efe647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c73f362edb536b7205b174568523dca1c74a6d9c14fff99f24b544f31ccbf10 +size 20759 diff --git a/marked/Rel-16/25_series/25153/raw.md b/marked/Rel-16/25_series/25153/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f730ebcecbdbc94a9251c81ec1d8de2388c6d83 --- /dev/null +++ b/marked/Rel-16/25_series/25153/raw.md @@ -0,0 +1,1786 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Frequency bands and channel arrangement ..... | 8 | +| 4.1 Frequency bands..... | 8 | +| 4.2 TX-RX frequency separation ..... | 9 | +| 4.3 Channel arrangement..... | 9 | +| 4.3.1 Channel spacing..... | 9 | +| 4.3.2 Channel raster ..... | 9 | +| 4.3.3 Channel number..... | 9 | +| 5 General test conditions and declarations..... | 9 | +| 5.1 Acceptable uncertainty of Test System..... | 10 | +| 5.1.1 Measurements of test environments ..... | 10 | +| 5.1.2 Measurements of Repeater ..... | 11 | +| 5.2 Repeater test tolerances (informative)..... | 11 | +| 5.3 Interpretation of measurement results ..... | 12 | +| 5.4 Test Environment..... | 12 | +| 5.4.1 Normal test environment ..... | 12 | +| 5.4.2 Extreme test environment..... | 13 | +| 5.4.2.1 Extreme temperature..... | 13 | +| 5.4.3 Vibration..... | 13 | +| 5.4.4 Power supply ..... | 14 | +| 5.5 Selection of configurations for testing ..... | 14 | +| 5.6 Regional requirements..... | 15 | +| 5.7 Format and interpretation of tests..... | 15 | +| 5.8 Repeater configurations..... | 16 | +| 5.8.1 Power supply options ..... | 16 | +| 5.8.2 Combining of Repeaters..... | 16 | +| 6 Output power..... | 17 | +| 6.1 Definition and applicability..... | 17 | +| 6.2 Minimum Requirements..... | 17 | +| 6.3 Test purpose ..... | 17 | +| 6.4 Method of test..... | 17 | +| 6.4.1 Initial conditions ..... | 17 | +| 6.4.2 Procedure..... | 18 | +| 6.5 Test Requirements..... | 18 | +| 7 Frequency stability..... | 18 | +| 7.1 Definition and applicability..... | 19 | +| 7.2 Minimum Requirement ..... | 19 | +| 7.3 Test purpose ..... | 19 | +| 7.4 Method of test..... | 19 | +| 7.4.1 Initial conditions ..... | 19 | +| 7.4.2 Procedure..... | 19 | +| 7.5 Test requirements ..... | 19 | +| 8 Out of band gain..... | 19 | +| 8.1 Definitions and applicability ..... | 19 | +| 8.2 Minimum requirement..... | 20 | +| 8.3 Test purpose ..... | 20 | +| 8.4 Method of test..... | 20 | +| 8.4.1 Initial conditions ..... | 20 | + +| | | | +|-----------|---------------------------------------------|----| +| 8.4.2 | Procedure ..... | 20 | +| 8.5 | Test requirements ..... | 21 | +| 9 | Unwanted emission ..... | 21 | +| 9.1 | Spectrum emission mask..... | 21 | +| 9.1.1 | Definition and applicability ..... | 21 | +| 9.1.2 | Minimum Requirements ..... | 21 | +| 9.1.3 | Test purpose..... | 22 | +| 9.1.4 | Method of test..... | 22 | +| 9.1.4.1 | Initial conditions ..... | 22 | +| 9.1.4.2 | Procedure..... | 22 | +| 9.1.5 | Test Requirements ..... | 23 | +| 9.2 | Spurious emissions..... | 24 | +| 9.2.1 | Definition and applicability ..... | 24 | +| 9.2.2 | Minimum Requirements..... | 24 | +| 9.2.2.1 | Mandatory Requirements..... | 24 | +| 9.2.2.1.1 | Spurious emissions (Category A)..... | 24 | +| 9.2.2.1.2 | Spurious emissions (Category B)..... | 24 | +| 9.2.2.2 | Co-existence with GSM 900..... | 25 | +| 9.2.2.2.1 | Operation in the same geographic area ..... | 25 | +| 9.2.2.2.2 | Co-located base stations..... | 25 | +| 9.2.2.3 | Co-existence with DCS 1800..... | 26 | +| 9.2.2.3.1 | Operation in the same geographic area ..... | 26 | +| 9.2.2.3.2 | Co-located base stations..... | 26 | +| 9.2.2.4 | Co-existence with UTRA-FDD ..... | 26 | +| 9.2.2.4.1 | Operation in the same geographic area ..... | 26 | +| 9.2.2.4.2 | Co-located base stations..... | 27 | +| 9.2.2.5 | Co-existence with unsynchronised TDD ..... | 27 | +| 9.2.2.5.1 | Operation in the same geographic area ..... | 27 | +| 9.2.2.5.2 | Co-located base stations..... | 28 | +| 9.2.3 | Test purpose..... | 28 | +| 9.2.4 | Method of test..... | 29 | +| 9.2.4.1 | Initial conditions ..... | 29 | +| 9.2.4.2 | Procedure..... | 29 | +| 9.2.5 | Test Requirements ..... | 29 | +| 10 | Modulation accuracy..... | 29 | +| 10.1 | Error Vector Magnitude ..... | 29 | +| 10.1.1 | Definition and applicability ..... | 29 | +| 10.1.2 | Minimum requirements ..... | 29 | +| 10.1.3 | Test purpose..... | 29 | +| 10.1.4 | Method of test..... | 30 | +| 10.1.4.1 | Initial conditions ..... | 30 | +| 10.1.4.2 | Procedure ..... | 30 | +| 10.1.5 | Test requirements ..... | 30 | +| 10.2 | Peak code domain error..... | 30 | +| 10.2.1 | Definition and applicability ..... | 30 | +| 10.2.2 | Minimum requirement..... | 30 | +| 10.2.3 | Test purpose..... | 30 | +| 10.2.4 | Method of test..... | 30 | +| 10.2.4.1 | Initial conditions ..... | 30 | +| 10.2.4.2 | Procedure ..... | 31 | +| 10.2.5 | Test requirements ..... | 31 | +| 11 | Input Intermodulation ..... | 31 | +| 11.1 | Definition and applicability..... | 31 | +| 11.2 | Minimum requirement..... | 31 | +| 11.2.1 | General requirement ..... | 31 | +| 11.2.2 | Co-location with BS in other systems ..... | 33 | +| 11.2.3 | Co-existence with other systems ..... | 36 | +| 11.3 | Test purpose ..... | 37 | +| 11.4 | Method of test..... | 38 | +| 11.4.1 | Initial conditions ..... | 38 | + +| | | | +|-------------------------------|-------------------------------------------------------|-----------| +| 11.4.2 | Procedure ..... | 38 | +| 11.5 | Test requirements ..... | 38 | +| 12 | Output Intermodulation ..... | 38 | +| 12.1 | Definition and applicability ..... | 38 | +| 12.2 | Minimum requirements ..... | 38 | +| 12.3 | Test purpose ..... | 38 | +| 12.4 | Method of test ..... | 39 | +| 12.4.1 | Initial conditions ..... | 39 | +| 12.4.2 | Procedures ..... | 39 | +| 12.5 | Test requirements ..... | 39 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 40 | +| 13.1 | Definitions and applicability ..... | 40 | +| 13.2 | Minimum Requirements ..... | 40 | +| 13.3 | Test purpose ..... | 40 | +| 13.4 | Method of test ..... | 40 | +| 13.4.1 | Initial conditions ..... | 40 | +| 13.4.2 | Procedure ..... | 41 | +| 13.5 | Test Requirements ..... | 41 | +| 14 | Timing Accuracy ..... | 41 | +| 14.1 | Definition and applicability ..... | 41 | +| 14.2 | Minimum requirements ..... | 41 | +| 14.3 | Test purpose ..... | 42 | +| 14.4 | Method of test ..... | 42 | +| 14.4.1 | Initial conditions ..... | 42 | +| 14.4.2 | Procedure ..... | 43 | +| 14.5 | Test Requirements ..... | 43 | +| Annex A (normative): | Repeater measurement system set-up ..... | 45 | +| A.1 | Maximum output power ..... | 45 | +| A.2 | Frequency stability ..... | 45 | +| A.3 | Out of band gain ..... | 45 | +| A.4 | Unwanted emission: Spectrum emission mask ..... | 45 | +| A.5 | Unwanted emission: Spurious emission ..... | 46 | +| A.6 | Modulation Accuracy: Error Vector Magnitude ..... | 46 | +| A.7 | Modulation Accuracy: Peak Code Domain Error ..... | 46 | +| A.8 | Input inter modulation ..... | 46 | +| A.9 | Output Intermodulation ..... | 47 | +| A.10 | Timing Accuracy ..... | 47 | +| Annex B (informative): | Derivation of Test Requirements ..... | 48 | +| Annex C (informative): | Acceptable uncertainty of Test Equipment ..... | 49 | +| Annex D (informative): | Change history ..... | 50 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Radio Frequency (RF) test methods and Minimum Requirements for LCR TDD Repeaters. These have been derived from, and are consistent with the LCR TDD Repeater specifications defined in TS 25.116. + +This document establishes the minimum RF characteristics of the LCR TDD Repeater. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.105: “Base Station (BS) radio transmission and reception (TDD)”. +- [2] 3GPP TS 25.942: “RF system scenarios”. +- [3] 3GPP TS 25.113 : “ Base station EMC ”. +- [4] ITU-R recommendation SM.329: “Unwanted emissions in the spurious domain “. +- [5] ITU-T recommendation O.153: “Basic parameters for the measurement of error performance at bit rates below the primary rate”. +- [6] IEC 60721-3-3 (1994): “Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 3: Stationary use at weather protected locations”. +- [7] IEC 60721-3-4 (1995): “Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 4: Stationary use at non-weather protected locations”. +- [8] IEC 60068-2-1 (1990): “Environmental testing – Part 2: Tests. Tests A: Cold”. +- [9] IEC 60068-2-2 (1974): “Environmental testing – Part 2: Tests. Tests B: Dry heat”. +- [10] IEC 60068-2-6 (1995): “Environmental testing – Part 2: Tests – Test Fc: Vibration (sinusoidal)”. +- [11] 3GPP TS 25.142: “Base station conformance testing (TDD)”. +- [12] 3GPP TS 25.106: “UTRA Repeater; Radio transmission and reception”. +- [13] 3GPP TS 25.116: “LCR TDD Repeater; Radio transmission and reception” + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Donor coupling loss:** is the coupling loss between the repeater and the donor base station. + +**Down-link:** signal path where base station transmits and mobile receives + +**Maximum output power, Pmax:** This is the mean power level per carrier measured at the antenna connector of the Repeater in specified reference condition. + +**Pass band:** the Repeater can have one or several pass bands. The pass band is the frequency range that the Repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal 5 MHz channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. + +**Repeater:** a device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). + +**Up-link:** signal path where mobile transmits and base station receives. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------------------|----------------------------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| BW Config | Transmission bandwidth configuration, expressed in MHz. | +| BW Meas | Measurement bandwidth | +| BW Signal | Bandwidth of the repeater input signal filling the repeater pass band | +| F DL_low | The lowest frequency of the downlink operating band | +| F DL_high | The highest frequency of the downlink operating band | +| F UL_low | The lowest frequency of the uplink operating band | +| F UL_high | The highest frequency of the uplink operating band | +| f offset_PB | Distance from the channel edge frequency of the first or last channel in the pass band | +| N DL | Downlink LARFCN | +| N offs-DL | Offset used for calculating downlink LARFCN | +| N offs-UL | Offset used for calculating uplink LARFCN | +| N RB | Transmission bandwidth configuration, expressed in units of resource blocks | +| N UL | Uplink LARFCN | +| P max | Maximum output power | +| P out | Output power | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-------------------------------------------------| +| BTS | Base Transceiver Station | +| CW | Continuous Wave (unmodulated signal) | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| IMT2000 | International Mobile Telecommunication-2000 | +| ITU | International Telecommunication Union | +| MS | Mobile Station | +| RF | Radio Frequency | +| TDD | Time Division Duplex | +| LARFCN | LCR TDD Absolute Radio Frequency Channel Number | +| UMTS | Universal Mobile Telecommunication System | +| UTRA | Universal Terrestrial Radio Access | + +# --- 4 Frequency bands and channel arrangement + +## 4.1 Frequency bands + +UTRA/TDD is designed to operate in the following bands; + +- a) 1900 - 1920 MHz: Uplink and downlink transmission +2010 - 2025 MHz Uplink and downlink transmission +- b) 1850 - 1910 MHz Uplink and downlink transmission + +- 1930 - 1990 MHz Uplink and downlink transmission +- c) 1910 - 1930 MHz Uplink and downlink transmission + - d) 2570 - 2620 MHz Uplink and downlink transmission + - e) 2300 - 2400 MHz Uplink and downlink transmission + - f) 1880 - 1920 MHz: Uplink and downlink transmission + +Note: Deployment in existing and other frequency bands is not precluded. + +## 4.2 TX-RX frequency separation + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL. + +## 4.3 Channel arrangement + +### 4.3.1 Channel spacing + +The channel spacing is 1.6MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 4.3.2 Channel raster + +The channel raster is 200 kHz for all bands, which means that the carrier frequency must be a multiple of 200 kHz. + +### 4.3.3 Channel number + +The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows: + +$$N_t = 5 * F \qquad 0.0 \leq F \leq 3276.6 \text{ MHz}$$ + +where F is the carrier frequency in MHz. + +# 5 General test conditions and declarations + +This specification applies only to LCR TDD Repeater. + +The requirements of this clause apply to all applicable tests in this specification. Many of the tests in this specification measure a parameter relative to a value, that is not fully specified in the LCR TDD specifications. For these tests, the Minimum Requirement is determined relative to a nominal value specified by the manufacturer. + +Some requirements for the Repeater may be regional as listed in subClause 5.6. + +When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported. + +Schematic drawings for the individual measurement set-up can be found in the Annex A. + +## 5.1 Acceptable uncertainty of Test System + +The maximum acceptable uncertainty of the Test System is specified below for each test, where appropriate. The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance, and the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +For RF test it should be noted that the uncertainties in subClause 5.1 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System. + +### 5.1.1 Measurements of test environments + +The measurement accuracy of the Repeater test environments defined in SubClause 5.4, Test environments shall be. + +| | | +|----------------------|------------------| +| Pressure: | $\pm 5$ kPa. | +| Temperature: | $\pm 2$ degrees. | +| Relative Humidity: | $\pm 5$ %. | +| DC Voltage: | $\pm 1,0$ %. | +| AC Voltage: | $\pm 1,5$ %. | +| Vibration: | 10 %. | +| Vibration frequency: | 0,1 Hz. | + +The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter. + +### 5.1.2 Measurements of Repeater + +**Table 5.1: Maximum Test System Uncertainty** + +| Subclause | Maximum Test System Uncertainty | Range over which Test System Uncertainty applies | +|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| 6 Maximum output power | ±0,7 dB | | +| 7 Frequency error | ±12 Hz | Measurement results of ± 500 Hz | +| 8 Out of band gain | ±0,5 dB
Calibration of test set-up shall be made without D.U.T. in order to achieve the accuracy | | +| 9.1 Spectrum emission mask | ±1,5 dB | | +| 9.2 Spurious emissions | ± 2,0 dB for BS and coexistence bands for results > -60 dBm
± 3,0 dB for results < -60 dBm

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

(±2,5 % measurement error for single code).

5,0 % EVM in the stimulus signal (single code) will shift the EVM maximum value 0,7% to 18,2%.
(RSS repeater EVM and Stimulus EVM.) | Measurement results from 12,5% to 22,5% at signal power = P_max – 3dB to P_max – 18 dB | +| 10.2 Peak code domain error | ±1,1dB

Formula: RSS measurement error and impedance mismatch error

(using ±1,0 dB measurement error and ±0,5 dB impedance mismatch error (stimulus side) assuming 14 dB return loss) | Measurement results from – 36 dB to – 30 dB, at signal power = P_max – 3 dB to P_max – 18 dB | +| 11 Input intermodulation Characteristics | ±1,2 dB

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

± 1 dB | The uncertainty of the interferer has double the effect on the result due to the frequency offset. | +| 13 Adjacent Channel Rejection Ratio | ±0,7 dB | | + +## 5.2 Repeater test tolerances (informative) + +The Test Tolerances defined in this subclause have been used to relax the Minimum Requirements in this specification to derive the Test Requirements. + +The Test Tolerances are derived from Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the Test Tolerances may sometimes be set to zero. + +The test tolerances should not be modified for any reason e.g. to take account of commonly known test system errors (such as mismatch, cable loss, etc.) + +**Table 5.2: Test Tolerance** + +| Subclause | Test Tolerance (Note 1) | Notes | +|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------| +| 6 Maximum output power | 0,7 dB | | +| 9.1 Spectrum emission mask | 1,5 dB | 0 dB test tolerance for the additional Band II, IV and V requirements | +| 9.2 Spurious emissions | 0 dB | | +| 7 Frequency error | 12 Hz | | +| 10.1 Error vector magnitude | 0 % | Target value is shifted due to stimulus EVM | +| 10.2 Peak code domain error | 1,1 dB | | +| 8 Out of band gain | 0,5dB | | +| 11 Input intermodulation Characteristics | 1,2dB | | +| 12 Output intermodulation | 1,5 dB for spectrum emission
0 dB for spurious emission | | +| 13 Adjacent Channel Rejection Ratio | 0,7 dB | | +| NOTE 1: Unless otherwise stated, The Test Tolerances are applied to the DUT Minimum Requirement. See Annex B. | | | + +## 5.3 Interpretation of measurement results + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ETR 273 Part 1 sub-part 2 section 6.5. + +The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report. + +The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in subClause 5.1 of this specification. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in subClause 5.1, it is still permitted to use this equipment provided that an adjustment is made as follows: + +Any additional uncertainty in the Test System over and above that specified in subClause 5.1 shall be used to tighten the Test Requirement - making the test harder to pass. + +This procedure will ensure that a Test System not compliant with subClause 4.1 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with subClause 4.1 had been used. + +## 5.4 Test Environment + +For each test in the present document, the environmental conditions under which the Repeater is to be tested are defined. + +### 5.4.1 Normal test environment + +When a normal test environment is specified for a test, the test should be performed under any combination of conditions between the minimum and maximum limits stated in table 5.3. + +**Table 5.3: Limits of conditions for Normal Test Environment** + +| Condition | Minimum | Maximum | +|---------------------|------------------------------------------|---------| +| Barometric pressure | 86 kPa | 106 kPa | +| Temperature | 15°C | 30°C | +| Relative Humidity | 20 % | 85 % | +| Power supply | Nominal, as declared by the manufacturer | | +| Vibration | Negligible | | + +The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +### 5.4.2 Extreme test environment + +The manufacturer shall declare one of the following: + +- a) The equipment class for the equipment under test, as defined in IEC 60721-3-3 [2]. +- b) The equipment class for the equipment under test, as defined in IEC 60721-3-4 [3]. +- c) For equipment that does not comply to the mentioned classes, the relevant classes from IEC 60 721 documentation for Temperature, Humidity and Vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall out side of the standard operational conditions are not tested in this TS. These may be stated and tested separately. + +#### 5.4.2.1 Extreme temperature + +When an extreme temperature test environment is specified for a test, the test shall be performed at the standard minimum and maximum operating temperatures defined by the manufacturer's declaration for the equipment under test. + +##### Minimum temperature: + +- The test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-1 [4], Environmental Testing, Part 2: Tests - Tests A: Cold. The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +##### Maximum temperature: + +- The test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-2 [5] (Environmental Testing, Part 2: Tests - Tests Bd Dry heat). The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +### 5.4.3 Vibration + +When vibration conditions are specified for a test, the test shall be performed while the equipment is subjected to a vibration sequence as defined by the manufacturers declaration for the equipment under test. This shall use the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-6 [8], Environmental Testing, Part 2: Tests - Test Fc and guidance: Vibration (Sinusoidal). Other environmental conditions shall be within the ranges specified in subClause 4.4.1, Normal test environment. + +NOTE: The higher levels of vibration may induce undue physical stress in to equipment after a prolonged series of tests. The testing body should only vibrate the equipment during the RF measurement process. + +### 5.4.4 Power supply + +When extreme power supply conditions are specified for a test, the test shall be performed at the standard upper and lower limits of operating voltage defined by the manufacturer's declaration for the equipment under test. + +#### Upper voltage limit + +- The equipment shall be supplied with a voltage equal to the upper limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at a steady state minimum and + +maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] Test Bb/Bd: Dry Heat. + +#### Lower voltage limit + +- The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at a steady state minimum and maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] Test Bb/Bd: Dry Heat. + +## 5.5 Selection of configurations for testing + +Measurements shall be performed within the time slots under test as specified individually for each test within the subclause " Procedure ". + +Most tests in this TS are only performed for a subset of the possible combinations of test conditions. For instance: + +- Only one RF channel may be specified to be tested. +- Only one timeslot may be specified to be tested. + +When a test is performed by a test laboratory, the choice of which combinations are to be tested shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +When a test is performed by a manufacturer, the choice of which combinations are to be tested may be specified by an operator. + +## 5.6 Regional requirements + +Some requirements in TS 25.153 may only apply in certain regions. Table 5.4 lists all requirements that may be applied differently in different regions. + +**Table 5.4: List of regional requirements** + +| Sub-clause number | Requirement | Comments | +|-------------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.1 | Frequency bands | Some bands may be applied regionally. | +| 4.2 | Up-link to down-link frequency separation | The requirement is applied according to what frequency bands in clause 5.1 that are supported by the Repeater. | +| 4.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 5.1 that are supported by the Repeater. | +| 6 | Maximum output power | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. | +| 9.1 | Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. | +| 9.2.2.1.1 | Spurious emissions (Category A) | These requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. | +| 9.2.2.1.2 | Spurious emissions (Category B) | These requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. | +| 9.2.2.2.1 | Co-existence with GSM900 - Operation in the same geographic area | This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS in geographic areas in which both GSM 900 and UTRA are deployed. | +| 9.2.2.2.2 | Co-existence with GSM900 - Co-located base stations | This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. | +| 9.2.2.3.1 | Co-existence with DCS1800 - Operation in the same geographic area | This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS in geographic areas in which both DCS 1800 and UTRA are deployed. | +| 9.2.2.3.2 | Co-existence with DCS1800 - Co-located base stations | This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. | +| 9.2.2.4.1 | Co-existence with UTRA FDD - Operation in the same geographic area | This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. | +| 9.2.2.4.2 | Co-existence with UTRA FDD - Co-located base stations | This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. | +| 9.2.2.5.1 | Co-existence with unsynchronised TDD - Operation in the same geographic area | This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised TDD is deployed. | +| 9.2.2.5.2 | Co-existence with unsynchronised TDD - Co-located base stations | This requirement may be applied for the protection of TDD BS receivers when unsynchronised TDD BS are co-located. | +| 11.2.2 | Input intermodulation: Co-location with other systems | The requirement may be applied when GSM 900, DCS 1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band and LCR TDD Repeaters are co-located. | +| 11.2.3 | Input Intermodulation: Co-existence with other systems | These requirements may apply in geographic areas in which both LCR TDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | + +## 5.7 Format and interpretation of tests + +Each test in the following clauses has a standard format: + +**X                      Title** + +All tests are applicable to all equipment within the scope of the present document, unless otherwise stated. + +## X.1 Definition and applicability + +This subclause gives the general definition of the parameter under consideration and specifies whether the test is applicable to all equipment or only to a certain subset. + +## X.2 Minimum Requirements + +This subclause is an informative copy of the Minimum Requirement defined by the core specification. + +In addition, this subclause contains the reference to the subclause to the 3GPP reference (or core) specification which defines the Minimum Requirement. + +## X.3 Test purpose + +This subclause defines the purpose of the test. + +## X.4 Method of test + +### X.4.1 Initial conditions + +This subclause defines the initial conditions for each test, including the basic measurement set-up. + +### X.4.2 Procedure + +This subclause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. antenna port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). + +## X.5 Test Requirements + +This subclause defines the pass/fail criteria for the equipment under test. See subClause 4.3 Interpretation of measurement results. + +## 5.8 Repeater configurations + +### 5.8.1 Power supply options + +If the repeater is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations. + +### 5.8.2 Combining of Repeaters + +If the repeater is intended for combination with additional apparatus connected to a repeater port and this combination is supplied as a system, the combination of repeater together with the additional apparatus shall also fulfil the repeater requirements. E.g. if the repeater is intended for combination such that multiple repeaters amplify the same signals into the same ports the combination shall also fulfil the repeater requirements. + +An example of such a configuration is shown in figure 5.1 + +![Diagram of a repeater configuration showing two repeaters connected in parallel between two combiner/splitter units.](bd4c85f71b8f5e06d935a6240b6dab56_img.jpg) + +The diagram illustrates a repeater configuration. On the left, a 'Test port' is connected to a 'Combiner / Splitter' block. The output of this block splits into two 'Repeater' blocks. The outputs of these two repeaters are then combined by another 'Combiner / Splitter' block, which is connected to a 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are positioned between the combiner/splitter blocks and the repeater blocks, indicating the connection points. + +Diagram of a repeater configuration showing two repeaters connected in parallel between two combiner/splitter units. + +Figure 5.1: Example of repeater configuration + +# 6 Output power + +Output power, $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +Rated output power, $PRAT$ , of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 Definition and applicability + +Maximum output power, $P_{max}$ , of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition. + +## 6.2 Minimum Requirements + +The requirements shall apply at maximum gain, with LCR TDD signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. + +When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met. + +In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +**Table 6.1: Repeater output power; normal conditions** + +| Rated output power | Limit | +|---------------------------|-----------------| +| $P \geq 31$ dBm | +2 dB and -2 dB | +| $P < 31$ dBm | +3 dB and -3 dB | + +In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|---------------------------|---------------------| +| $P \geq 31$ dBm | +2,5 dB and -2,5 dB | +| $P < 31$ dBm | +4 dB and -4 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. + +## 6.3 Test purpose + +To verify that the Repeater maximum output power is within the limit specified in 6.1.2. + +## 6.4 Method of test + +### 6.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. + +### 6.4.2 Procedure + +- 1) Set the signal generator to transmit a signal according to table 6.3. + +**Table 6.3: Parameters of the transmitted signal for output power test** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| output power setting | PRAT | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the mean power at the RF output port over a certain slot. +- 4) Increase the power with 10 dB compare to the level obtained in step 2. +- 5) Measure the mean power at the RF output port over a certain slot. + +In addition, on one UARFCN only, the test shall be performed under extreme power supply as defined in subclause 5.4.4 + +NOTE: Tests under extreme power supply also test extreme temperature. + +## 6.5 Test Requirements + +In normal conditions as specified in section 5.4.1, the Repeater maximum output power shall remain within limits specified in Table 6.3 relative to the manufacturer's rated output power. + +**Table 6.4: Repeater output power; normal conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +2,7 dB and -2,7 dB | +| $P < 31$ dBm | +3,7 dB and -3,7 dB | + +In extreme conditions as specified in section 5.4.2 and 5.4.4, the Repeater maximum output power shall remain within limits specified in Table 6.4 relative to the manufacturer's rated output power. + +**Table 6.5: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +3,2 dB and -3,2 dB | +| $P < 31$ dBm | +4,7 dB and -4,7 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.4.1. + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non zero. The Test Tolerance for this test is defined in subclause 5.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex B. + +# --- 7 Frequency stability + +Frequency error is the measure of the difference between the frequency of the received signal and the frequency of the re-transmitted signal. + +## 7.1 Definition and applicability + +The frequency stability is a measure of the frequency deviation of the output signal with respect to the input signal. The test shall address the uplink and the downlink path of the Repeater. + +## 7.2 Minimum Requirement + +In normal conditions as specified in section 5.4.1 the frequency deviation shall be within $\pm 0,01$ ppm. + +## 7.3 Test purpose + +To verify that the Frequency Error is within the limit specified in 7.2. + +## 7.4 Method of test + +### 7.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +### 7.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 7.1. + +**Table 7.1: Parameters of the transmitted signal for Frequency stability test** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i is 0, 4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the frequency error for both paths uplink and downlink of the Repeater. + +## 7.5 Test requirements + +The measurement result of 7.4.2 shall not exceed: + +$$| f_{IN} - f_{out} | \leq (f_{out} * 0,01 \text{ ppm}) + 12 \text{ Hz}$$ + +# 8 Out of band gain + +## 8.1 Definitions and applicability + +Out of band gain refers to the gain of the Repeater immediately outside the pass band. The measurements shall apply to both paths uplink and downlink of the Repeater. + +## 8.2 Minimum requirement + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last channel within the pass band. + +**Table 8.1: Out of band gain limits 1** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $1,0 \leq f\_offset < 1,8$ MHz | 60 dB | +| $1,8 \leq f\_offset < 5,8$ MHz | 45 dB | +| $5,8 \leq f\_offset < 10,8$ MHz | 45 dB | +| $10,8$ MHz $\leq f\_offset$ | 35 dB | + +For $10,8$ MHz $\leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) | +| NOTE 1: The out of band gain is considered with $10,8$ MHz $\leq f\_offset$ | | + +## 8.3 Test purpose + +The purpose of this test is to verify that the Repeater meets the out of band gain requirements as specified by the minimum requirements. + +## 8.4 Method of test + +### 8.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) $f\_offset\_CW$ is the offset between the outer channel edge frequency of the outer channel in the pass band and a CW-signal. +- 3) The test shall be performed with an $f\_offset\_CW$ of 1 MHz, 1.8 MHz, 5.8 MHz, 10.8 MHz, 15 MHz and 20 MHz, excluding other pass bands. In addition the test shall also be performed for all harmonic frequencies of the repeaters pass band up to 12,75 GHz. + +### 8.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator to generate a CW-signal, applied to the input port of the Repeater. The power level of the RF input signal shall be at least 5 dB below the power level which, when applied within the pass band, would produce the maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range. +- 3) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded compared to table 8.3 or table 8.4 whichever is lower. +- 4) With the same input power as in step 1) set the repeater gain to the minimum specified by the manufacturer. +- 5) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded and compared to table 8.3 or table 8.4 whichever is lower. + +## 8.5 Test requirements + +**Table 8.3: Out of band gain limits** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $1,0 \leq f\_offset < 1,8$ MHz | 60,5 dB | +| $1,8 \leq f\_offset < 5,8$ MHz | 45,5 dB | +| $5,8 \leq f\_offset < 10,8$ MHz | 45,5 dB | +| $10,8$ MHz $\leq f\_offset$ | 35,5 dB | + +**Table 8.4: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,5 dB | +| NOTE: The donor coupling loss is considered with $10,8$ MHz $\leq f\_offset$ | | + +# 9 Unwanted emission + +## 9.1 Spectrum emission mask + +### 9.1.1 Definition and applicability + +The spectrum emission mask specifies the limit of the transmitter out of band emissions at frequency offsets from the assigned channel frequency of the wanted signal between 0,8 MHz and 4 MHz. + +The mask defined in Table 9.1 to 9.3 may be mandatory in certain regions. In other regions this mask may not be applied. + +### 9.1.2 Minimum Requirements + +For regions where this subclause applies, the requirement shall be met by LCR TDD repeater transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 9.1 to 9.3 in the frequency range of $f\_offset$ from 0.815 MHz to $f\_offset_{max}$ from the carrier frequency, where: + +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter +- $f\_offset_{max}$ is either 4 MHz or the offset to the UMTS Tx band edge as defined in subclause 4.2, whichever is the greater. + +**Table 9.1: Spectrum emission mask values, maximum output power $P \geq 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------| +| $0.815$ MHz $\leq f\_offset < 1.015$ MHz | -20 dBm | 30 kHz | +| $1.015$ MHz $\leq f\_offset < 1.815$ MHz | $-20\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right)$ dB | 30 kHz | +| $1.815$ MHz $\leq f\_offset < 2.3$ MHz | -28 dBm | 30 kHz | +| $2.3$ MHz $\leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | + +**Table 9.2: Spectrum emission mask values, maximum output power $26 \leq P < 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | $P-54$ dB | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $P - 54\text{dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{ MHz} \leq f\_offset < 2.3\text{ MHz}$ | $P-62$ dB | 30 kHz | +| $2.3\text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 47$ dB | 1 MHz | + +**Table 9.3: Spectrum emission mask values, maximum output power $P < 26$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -28 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-28\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -36 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -21 dBm | 1 MHz | + +NOTE: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +### 9.1.3 Test purpose + +The purpose of this test is to verify that the Repeater meet the spectrum emission requirements as specified in TS 25.116. + +### 9.1.4 Method of test + +#### 9.1.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. + +#### 9.1.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to table 9.4, at level(s) which produce the manufacturer specified maximum output power at maximum gain. + +**Table 9.4: Parameters of the transmitted signal for spectrum emission mask testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +- 3) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 4) Increase the power with 10 dB compare to the level obtained in step 2. + +- 5) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. + +### 9.1.5 Test Requirements + +The spectrum emissions measured according to subclause 9.1.4.2 shall be within the mask defined in the table 9.5 to 9.7. + +**Table 9.5: Spectrum emission mask values, maximum output power $P \geq 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -18.5 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-18.5\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -26.5 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -11.5 dBm | 1 MHz | + +**Table 9.6: Spectrum emission mask values, maximum output power $26 \leq P < 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | $P - 52.5 \text{ dB}$ | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $P - 52.5\text{dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | $P - 60.5 \text{ dB}$ | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 45.5 \text{ dB}$ | 1 MHz | + +**Table 9.7: Spectrum emission mask values, maximum output power $P < 26$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -26.5 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-26.5\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -34.5 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -19.5 dBm | 1 MHz | + +## 9.2 Spurious emissions + +### 9.2.1 Definition and applicability + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer's. + +For 1.28 Mcps TDD option, either requirement applies at frequencies within the specified frequency ranges which are more than 4 MHz under the first carrier frequency used or more than 4 MHz above the last carrier frequency used. + +Unless otherwise stated, all requirements are measured as mean power. + +### 9.2.2 Minimum Requirements + +#### 9.2.2.1 Mandatory Requirements + +The requirements of either subclause 9.2.2.1.1 or subclause 9.2.2.1.2 shall apply. + +##### 9.2.2.1.1 Spurious emissions (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [6], are applied. + +The power of any spurious emission shall not exceed the maximum level given in Table 9.8. + +**Table 9.8: LCR TDD repeater Mandatory spurious emissions limits, Category A** + +| Band | Minimum requirement | Measurement Bandwidth | Notes | | +|------------------------------------------------------------|---------------------|-----------------------|--------|--| +| 9kHz - 150kHz | -13 dBm | 1 kHz | Note 1 | | +| 150kHz - 30MHz | | 10 kHz | Note 1 | | +| 30MHz - 1GHz | | 100 kHz | Note 1 | | +| 1GHz - 12.75 GHz | | 1 MHz | Note 2 | | +| NOTE 1: Bandwidth as in ITU SM.329 [6], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU SM.329 [6], s2.5 table 1 | | | | | + +NOTE: only the measurement bands are different according to the occupied bandwidth. + +##### 9.2.2.1.2 Spurious emissions (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [6], are applied. + +The power of any spurious emission shall not exceed the maximum levels given in Table 9.9. + +**Table 9.9: LCR TDD repeater Mandatory spurious emissions limits, Category B** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|---------------|-----------------------|--------| +| 9kHz - 150kHz | -36 dBm | 1 kHz | Note 1 | +| 150kHz - 30MHz | -36 dBm | 10 kHz | Note 1 | +| 30MHz - 1GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz
↔
Fl -10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl -10MHz
↔
Fu +10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu +10 MHz
↔
12.5 GHz | -30 dBm | 1 MHz | Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | +| NOTE 2: Specification in accordance with ITU-R SM.329 [6], s4.1 | | | | +| NOTE 3: Bandwidth as in ITU-R SM.329-9, s4.1. Upper frequency as in ITU-R SM.329-9, s2.5 table 1 | | | | + +Fl: Lower frequency of the band in which TDD operates + +Fu: Upper frequency of the band in which TDD operates + +#### 9.2.2.2 Co-existence with GSM 900 + +##### 9.2.2.2.1 Operation in the same geographic area + +This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS receivers in geographic areas in which both GSM 900 and UTRA are deployed. + +The power of any spurious emission shall not exceed the maximum level given in Table 9.10. + +**Table 9.10: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of GSM 900 MS and GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -61 dBm | 100 kHz | | +| 921 - 960MHz | -57 dBm | 100 kHz | | + +##### 9.2.2.2.2 Co-located base stations + +This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. + +The power of any spurious emission shall not exceed the maximum level given in table 9.11. + +**Table 9.11: LCR TDD repeater Spurious emissions limits for protection of the GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -98 dBm | 100 kHz | | + +#### 9.2.2.3 Co-existence with DCS 1800 + +##### 9.2.2.3.1 Operation in the same geographic area + +This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS receivers in geographic areas in which both DCS 1800 and UTRA are deployed. + +The power of any spurious emission shall not exceed the maximum level given in table 9.12. + +**Table 9.12: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -61 dBm | 100 kHz | | +| 1805 - 1880MHz | -47 dBm | 100 kHz | | + +**Table 9.12a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver operating in 1710-1755 MHz/1805-1850 MHz** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -61 dBm | 100 kHz | | +| 1805 - 1850MHz | -47 dBm | 100 kHz | | + +##### 9.2.2.3.2 Co-located base stations + +This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. + +The power of any spurious emission shall not exceed the maximum level given in table 9.13. + +**Table 9.13: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when co-located with DCS 1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -98 dBm | 100 kHz | | + +**Table 9.13a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when co-located with DCS1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -98 dBm | 100 kHz | | + +#### 9.2.2.4 Co-existence with UTRA-FDD + +##### 9.2.2.4.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD operating in bands specified in Table 9.11 are deployed. + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.11. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed the maximum level given in table 9.14. + +**Table 9.14: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------| +| 1920 - 1980 MHz | -43 dBm (*) | 3.84 MHz | | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | | +| 2500 - 2570 MHz | -43 dBm(**) | 3.84 MHz | | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | | +| NOTE* | For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | +| NOTE ** | For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6 MHz below the lowest TDD carrier used, whichever is lower. | | | + +NOTE: The requirements in Table 9.14 are based on a coupling loss of 70 dB between LCR TDD repeater and FDD Wide Area base stations. + +##### 9.2.2.4.2 Co-located base stations + +This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.12. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed the maximum level given in table 9.15. + +**Table 9.15: LCR TDD repeater Spurious emissions limits for BS co-located with UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1920 - 1980 MHz | -80 dBm (*) | 3,84 MHz | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | +| 2500 - 2570 MHz | - 80 dBm(**) | 3.84 MHz | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | +| NOTE * For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | +| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6MHz below the lowest TDD carrier used, whichever is lower. | | | + +NOTE: The requirements in Table 9.15 are based on a minimum coupling loss of 30 dB between LCR TDD repeater and UTRA-FDD base stations. + +#### 9.2.2.5 Co-existence with unsynchronised TDD + +##### 9.2.2.5.1 Operation in the same geographic area + +This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised TDD is deployed. + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the limits specified in table 9.16, otherwise the limits in table 9.17 shall apply. + +**Table 9.16: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -39 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -39 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -39 dBm | 1,28 MHz | +| 1880 – 1920 MHz | -39 dBm | 1,28 MHz | + +**Table 9.17: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -39 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -39 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.16 and 9.17 for the LCR TDD repeater are based on a minimum coupling loss of 67 dB between LCR TDD repeater and unsynchronised TDD base stations. + +##### 9.2.2.5.2 Co-located base stations + +This requirement may be applied for the protection of TDD BS receivers when unsynchronised TDD BS are co-located. + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the limits specified in table 9.18, otherwise the limits in table 9.19 shall apply. + +**Table 9.18: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -76 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -76 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -76 dBm | 1,28 MHz | +| 1880 - 1920 MHz | -76 dBm | 1,28 MHz | +| NOTE: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. | | | + +**Table 9.19: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -76 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -76 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.18 and 9.19 for the LCR TDD repeater are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. + +### 9.2.3 Test purpose + +The test purpose is to verify the ability of the LCR TDD repeater to limit the interference caused by unwanted transmitter effects to other systems operating at frequencies which are more than 4 MHz away from of the UTRA band used. + +### 9.2.4 Method of test + +#### 9.2.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. + +#### 9.2.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to table 9.4, at level(s) which produce the manufacturer specified maximum output power at maximum gain. +- 3) The detecting device shall be configured with a measurement bandwidth as stated in the tables. +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 5) Increase the input power with 10 dB compare to the level obtained in step 2. +- 6) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. + +### 9.2.5 Test Requirements + +The spurious emissions measured according to subclause 9.2.4.2 shall not exceed the limits specified in the relevant tables of 9.2.2. + +# 10 Modulation accuracy + +## 10.1 Error Vector Magnitude + +### 10.1.1 Definition and applicability + +The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 1.28MHz and roll-off $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %. + +The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal LCR TDD signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer. + +### 10.1.2 Minimum requirements + +The Error Vector Magnitude shall not be worse than 8 %. + +### 10.1.3 Test purpose + +To verify that the EVM is within the limit specified in 10.1.2 after the signal passed through the Repeater.. + +### 10.1.4 Method of test + +#### 10.1.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +#### 10.1.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 10.1. + +**Table 10.1: Parameters of the transmitted signal for Error Vector Magnitude testing** + +| Parameter | Value/description | +|---------------------------------------------|-------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
Transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Base station power | PRAT | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the Error Vector Magnitude for both paths uplink and downlink of the Repeater. + +### 10.1.5 Test requirements + +The error vector magnitude (EVM) measured according to subclause 10.1.4.2 shall not exceed 8 %. + +## 10.2 Peak code domain error + +### 10.2.1 Definition and applicability + +The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot. + +### 10.2.2 Minimum requirement + +The peak code domain error shall not exceed -30 dB at spreading factor 16. + +### 10.2.3 Test purpose + +To verify that the peak code domain error is within the limit specified in 10.2.2 after the signal passed through the Repeater. + +### 10.2.4 Method of test + +#### 10.2.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +#### 10.2.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 10.2. + +**Table 10.2: Parameters of the transmitted signal for Peak Code Domain Error testing** + +| Parameter | Value/description | +|---------------------------------------------|-------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the Peak Code Domain Error for both paths uplink and downlink of the Repeater. + +### 10.2.5 Test requirements + +The peak code domain error measured according to subclause 10.2.4.2 shall not exceed -30 dB at spreading factor 16. + +# --- 11 Input Intermodulation + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 Definition and applicability + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the Repeater to maintain the wanted frequency free of internally created interference. + +This test applies to uplink and downlink path of the Repeater. + +## 11.2 Minimum requirement + +### 11.2.1 General requirement + +For the parameters specified in table 11.1, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the 3rd order intermodulation product is positioned in the centre of the pass band. + +Table 11.1 specifies the parameters for two interfering signals, where: + +- $f_1$ offset is the offset from the channel edge frequency of the first or last channel in the pass band of the closer carrier. + +**Table 11.1: Input intermodulation requirement** + +| f_1 offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|--------------------------------|----------------------------------|------------------------|------------------------------| +| 1,0 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +### 11.2.2 Co-location with BS in other systems + +This additional input intermodulation requirement may be applied for the protection of TDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an LCR TDD Repeater. + +Unless otherwise stated this requirement applies to the uplink and downlink of the repeater, at maximum gain. + +For the parameters specified in table 11.2, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation products correspond to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.2: Input intermodulation requirements for interfering signals in co-located other systems** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|--------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|------| +| GSM900 | 921 - 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| DCS1800 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| PCS1900 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| GSM850 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band I or E-UTRA Band 1 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band II or E-UTRA Band 2 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band III or E-UTRA Band 3 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band V or E-UTRA Band 5 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VI or E-UTRA Band 6 | 875 - 885 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 - 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XI or E-UTRA Band 11 | 1475.9 - 1500.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | | + +| | | | | | | +|---------------------------------------|-----------------|---------|---------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD in Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band c), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band d), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band e), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band f), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | + +NOTE 1: The co-location requirements in Table 11.2 do not apply when the repeaters pass band frequency range is adjacent to the band for the co-location requirement in the Table 11.2. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [13]. + +NOTE 2: The Table 11.2 assumes that two operating bands, where the corresponding transmit and receive frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. + +### 11.2.3 Co-existence with other systems + +This additional input intermodulation requirement may be applied when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS operating in another frequency band co-exist with an E-UTRA FDD Repeater. + +Unless otherwise stated this requirement applies to the uplink and downlink of the repeater, at maximum gain. + +For the parameters specified in table 11.3, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation products correspond to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.3: Input intermodulation requirements for interfering signals in co-existing other systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|---------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 - 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| DCS1800 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| PCS1900 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| GSM850 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band II or E-UTRA Band 2 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VI or E-UTRA Band 6 | 815 - 850 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 | 880 - 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1452.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA TDD in Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1. | + +| | | | | | | +|---------------------------------------|-----------------|---------|---------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD in Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band c), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band d), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band e), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band f), since it is already covered by the requirement in sub-clause 11.1. | + +NOTE 1: The co-existence requirements in Table 11.3 do not apply when the repeaters pass band frequency range is adjacent to the band for the co-existence requirement in the Table 11.3. The current state-of-the-art technology does not allow a single generic solution for co-existence. + +NOTE 2: The Table 11.3 assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +## 11.3 Test purpose + +The purpose of this test is to verify that the Repeater meets the intermodulation characteristics requirements as specified by the minimum requirements. + +## 11.4 Method of test + +### 11.4.1 Initial conditions + +- 1) A measurement system set-up is shown in annex A. +- 2) Set the Repeater to maximum gain. +- 3) Connect two signal generators with a combining circuit or one signal generator with the ability to generate several CW carriers to the input. +- 4) Connect a spectrum analyser to the output of the Repeater. Set the resolution bandwidth to 1 MHz in the centre of the pass band. Set averaging to 1 second or more. + +### 11.4.2 Procedure + +- 1) Adjust the frequency of the input signals, either below or above the pass band, so that one carrier, $f_1$ , is 1 MHz outside the channel edge frequency of the first or last channel in the pass band, and the lowest order intermodulation product from the two carriers is positioned in the centre of the pass band, according to subclause 11.2. +- 2) Take the measurement of the rise of the output signal. +- 3) Repeat the measurement for the opposite path of the Repeater. + +## 11.5 Test requirements + +The Input intermodulation measured according to subclause 11.4.2 shall not exceed the limits specified in the relevant tables of 11.2. + +# --- 12 Output Intermodulation + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +## 12.1 Definition and applicability + +The transmit intermodulation level is the power of the intermodulation products when a LCR TDD modulated interference signal is injected into the antenna connector at a mean power level of 30 dB lower than that of the mean power of the subject signal. + +The requirement is applicable for downlink signals. + +## 12.2 Minimum requirements + +The frequency of the interference signal shall be $\pm 1.6$ MHz, $\pm 3.2$ MHz and $\pm 4.8$ MHz offset from the subject signal. The Transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of section 9.1 and 9.2. + +## 12.3 Test purpose + +The test purpose is to verify the ability of the repeater to restrict the generation of intermodulation products in the presence of a subject signal on the repeater input and output ports, and an interfering signal applied at the repeater output port. + +## 12.4 Method of test + +### 12.4.1 Initial conditions + +- 1) A measurement system set-up is shown in annex A. +- 2) Connect a signal generator to the input port of the Repeater (wanted signal). Connect a signal generator to the circulator on the output port (interfering signal) and make sure the signal generator power is directed to the repeater output port. +- 3) Detection mode: True RMS. + +### 12.4.2 Procedures + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator at the repeater input port (subject signal) to generate a signal in accordance to table 12.1, at the level which produce the manufacturer specified maximum output power at maximum gain. + +**Table 12.1: Parameters of the transmitted signal for transmit intermodulation testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +- 3) Set the signal generator at the repeater output port (interference signal) to generate a signal in accordance to table 12.1, at the level producing signal power corresponding to 30 dB below the manufacturer specified maximum output power at the repeater output port with the specified frequency offset from the wanted signal. +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. Measurements in the band of the interfering signal shall be excluded. The measurements can be limited to the power of all third and fifth order intermodulation products. +- 5) Repeat from clause 3 until interference signals $\pm 1,6\text{MHz}$ , $\pm 3,2\text{MHz}$ and $\pm 4,8\text{MHz}$ frequency offset from the wanted signal has been tested. Note that interfering signals outside the UTRA-FDD allocated frequency band, as specifies in section 4.1. need not be tested. + +## 12.5 Test requirements + +The mean power level of the interference signal shall be 30 dB below the mean power level of the wanted signal. + +At the frequencies of all third and fifth order intermodulation products, the Test Requirements for out of band and spurious emissions as specified in subclauses 9.1.5 (Spectrum emission mask), and 9.2.5 (Spurious emissions) shall be met. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. The carrier in the pass band and in the adjacent channel shall be of the same type (reference carrier). + +The requirement shall apply to the uplink and downlink of Repeater, at maximum gain, where the donor link is maintained via antennas (over the air Repeater). + +## 13.2 Minimum Requirements + +In normal conditions the ACRR shall be higher than the value specified in the Table 13.1. + +**Table 13.1: Repeater ACRR** + +| Repeater maximum output Pmax | Channel offset from the channel edge from the first or last channel within the pass band. | ACRR limit | +|------------------------------|-------------------------------------------------------------------------------------------|------------| +| $P \geq 31\text{ dBm}$ | 1,6 MHz | 33dB | +| $P \geq 31\text{ dBm}$ | 3,2 MHz | 33dB | +| $P < 31\text{ dBm}$ | 1,6 MHz | 20dB | +| $P < 31\text{ dBm}$ | 3,2 MHz | 20dB | + +Note: For co-existence with TDD, a narrow band requirement is for further study. + +## 13.3 Test purpose + +To verify that the Repeater ACRR requirement shall be met as specified in subclause 13.1. + +## 13.4 Method of test + +### 13.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. +- 4) The measurement device characteristics shall be: + - measurement filter bandwidth: defined in subclause 13.1; + - detection mode: true RMS voltage or true average power. + +### 13.4.2 Procedure + +- 1) Set the signal generator to transmit a signal according to table 13.2. + +**Table 13.2: Parameters of the transmitted signal for ACRR test** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| output power setting | PRAT | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain +- 3) Measure the RRC filtered mean power at the RF output port over a certain slot. +- 4) Set the signal generator to transmit the same signal and the same input power at one of the channel offsets according to Table 13.1. +- 5) Measure the RRC filtered mean power at the RF output port over a certain slot. +- 6) Calculate the ratio of the measured power in the pass band to the measured power at the channel offset. +- 7) Repeat step 4) to 6) until all channel offsets in Table 13.1 are measured. + +## 13.5 Test Requirements + +In normal conditions as specified in section 5.4.1, the ACRR shall be higher than the value specified in the Table 13.3. + +**Table 13.3: Repeater ACRR** + +| Repeater maximum output power as in 9.1.1.1 | Channel offset from the centre frequency of the first or last channel within the pass band. | ACRR limit | +|---------------------------------------------|---------------------------------------------------------------------------------------------|------------| +| $P \geq 31$ dBm | 1,6 MHz | 32,3dB | +| $P \geq 31$ dBm | 3,2 MHz | 32,3dB | +| $P < 31$ dBm | 1,6 MHz | 19,3dB | +| $P < 31$ dBm | 3,2 MHz | 19,3dB | + +# 14 Timing Accuracy + +## 14.1 Definition and applicability + +Timing Accuracy is the repeater synchronization accuracy with NodeB, it includes the downlink ramp on/off time and uplink ramp on/off time. + +## 14.2 Minimum requirements + +The downlink gain versus time should meet the mask specified in figure 14.1. The beginning and end point of downlink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing the downlink gain over time. The vertical axis is labeled 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Downlink burst without GP'.](4ee6ee5ce67694dbc95537938e09a917_img.jpg) + +The diagram illustrates the downlink gain template. It features a rectangular pulse representing the gain over time. The vertical axis is marked with 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis shows two '8 chips' intervals, indicated by double-headed arrows, at the leading and trailing edges of the pulse. The central portion of the pulse is labeled 'Downlink burst without GP'. + +Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing the downlink gain over time. The vertical axis is labeled 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Downlink burst without GP'. + +**Figure 14.1: Downlink gain ON/OFF template** + +The uplink gain versus time should meet the mask specified in figure 14.2. The beginning and end point of uplink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.2: Uplink gain ON/OFF template. The diagram shows a rectangular pulse representing the uplink gain over time. The vertical axis is labeled 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Uplink burst without GP'.](59fdf9faef450c0a4236031fb44d9faa_img.jpg) + +The diagram illustrates the uplink gain template. It features a rectangular pulse representing the gain over time. The vertical axis is marked with 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis shows two '8 chips' intervals, indicated by double-headed arrows, at the leading and trailing edges of the pulse. The central portion of the pulse is labeled 'Uplink burst without GP'. + +Figure 14.2: Uplink gain ON/OFF template. The diagram shows a rectangular pulse representing the uplink gain over time. The vertical axis is labeled 'Zero Gain' at the baseline and 'Rated Gain' at the peak. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Uplink burst without GP'. + +**Figure 14.2: Uplink gain ON/OFF template** + +## 14.3 Test purpose + +This test verifies the ability of the LCR TDD repeater to reduce its transmit power outside of the active part of the Tx time slot (burst without guard period) to values below specified limits. This ability is needed to minimize the interference for other users receiving on the same frequency. + +## 14.4 Method of test + +### 14.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +### 14.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 14.1. + +**Table 14.1: Parameters of the transmitted signal for Timing Accuracy testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is UpPCH,1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | + +- 2) Measure the RRC filtered mean power of the LCR TDD repeater output signal chipwise (i.e. averaged over time intervals of one chip duration) over the transmit off power period starting 8 chips before the beginning point of uplink/downlink burst, and ending 8 chips after the end point of uplink/downlink burst. + +## 14.5 Test Requirements + +The Timing Accuracy measured according to subclause 14.4.2 shall not exceed the limits specified in the relevant figures of 14.1 and 14.2. + + + +# Annex A (normative): Repeater measurement system set-up + +Example of measurement system set-ups are attached below as an informative annex. + +## A.1 Maximum output power + +![Block diagram for maximum output power measurement](a5184899f915014fa38608754efcc9c7_img.jpg) + +``` +graph LR; A[Power meter or equivalent] <--> B[Repeater under test] <--> C[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of three blocks. From left to right, they are: 'Power meter or equivalent', 'Repeater under test', and 'LCR TDD Signal Generator'. Double-headed arrows connect the 'Power meter or equivalent' to the 'Repeater under test', and the 'Repeater under test' to the 'LCR TDD Signal Generator'. + +Block diagram for maximum output power measurement + +**Figure A.1: Measuring system set-up for maximum output power.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.2 Frequency stability + +![Block diagram for RF frequency stability measurement](8d8c758885b4f754ff071bf3b572ab3c_img.jpg) + +``` +graph LR; A[Spectrum analyzer] <--> B[Repeater under test] <--> C[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of three blocks. From left to right, they are: 'Spectrum analyzer', 'Repeater under test', and 'LCR TDD Signal Generator'. Double-headed arrows connect the 'Spectrum analyzer' to the 'Repeater under test', and the 'Repeater under test' to the 'LCR TDD Signal Generator'. + +Block diagram for RF frequency stability measurement + +**Figure A.2: Measurement system set-up for RF frequency stability.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.3 Out of band gain + +![Block diagram for out of band gain measurement](c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg) + +``` +graph LR; A[Spectrum analyser] <--> B[-30 dB precision attenuator] <--> C[Repeater under test] <--> D[-30 dB precision attenuator] <--> E[CW Signal Generator] +``` + +The diagram shows a linear arrangement of five blocks. From left to right, they are: 'Spectrum analyser', '-30 dB precision attenuator', 'Repeater under test', '-30 dB precision attenuator', and 'CW Signal Generator'. Double-headed arrows connect each adjacent pair of blocks. + +Block diagram for out of band gain measurement + +**Figure A.3: Measuring system set-up for out of band gain.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.4 Unwanted emission: Spectrum emission mask + +![Block diagram for unwanted emission: spectrum emission mask measurement](5837d4aa3bb1d08bbebcd757248f5515_img.jpg) + +``` +graph LR; A[Spectrum analyzer] <--> B[Repeater under test] <--> C[Channel filter] <--> D[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of four blocks. From left to right, they are: 'Spectrum analyzer', 'Repeater under test', 'Channel filter', and 'LCR TDD Signal Generator'. Double-headed arrows connect each adjacent pair of blocks. + +Block diagram for unwanted emission: spectrum emission mask measurement + +**Figure A.4: Measuring system Set-up for unwanted emission: spectrum emission mask.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.5 Unwanted emission: Spurious emission + +![Block diagram for Figure A.5: Measuring system set-up for unwanted emission: spurious emission. The diagram shows four blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Channel filter', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer.](f142b022cfc716cd967297f027efe647_img.jpg) + +``` +graph RL; A[LCR TDD Signal Generator] --> B[Channel filter]; B --> C[Repeater under test]; C --> D[Spectrum analyzer]; +``` + +Block diagram for Figure A.5: Measuring system set-up for unwanted emission: spurious emission. The diagram shows four blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Channel filter', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer. + +Figure A.5: Measuring system set-up for unwanted emission: spurious emission. + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.6 Modulation Accuracy: Error Vector Magnitude + +![Block diagram for Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows three blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer.](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` +graph RL; A[LCR TDD Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyzer]; +``` + +Block diagram for Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows three blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer. + +Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude. + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.7 Modulation Accuracy: Peak Code Domain Error + +![Block diagram for Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error. The diagram shows three blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer.](18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg) + +``` +graph RL; A[LCR TDD Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyzer]; +``` + +Block diagram for Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error. The diagram shows three blocks connected in a line from right to left: 'LCR TDD Signal Generator', 'Repeater under test', and 'Spectrum analyzer'. Arrows indicate the signal flow from the generator to the analyzer. + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.8 Input inter modulation + +![Block diagram for Figure A.8: Measuring system set-up for input intermodulation. The diagram shows three blocks connected in a line from right to left: 'CW Signal Generator', 'Repeater under test', and 'Spectrum analyser'. Arrows indicate the signal flow from the generator to the analyser.](252210dd01a9d2f476bfb1c284c59ccf_img.jpg) + +``` +graph RL; A[CW Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyser]; +``` + +Block diagram for Figure A.8: Measuring system set-up for input intermodulation. The diagram shows three blocks connected in a line from right to left: 'CW Signal Generator', 'Repeater under test', and 'Spectrum analyser'. Arrows indicate the signal flow from the generator to the analyser. + +Figure A.8: Measuring system set-up for input intermodulation. + +## A.9 Output Intermodulation + +![Block diagram for Output Intermodulation measurement setup.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +The diagram shows a measurement setup for Output Intermodulation. It features a 'Spectrum analyser' on the left connected to a 'circulator' (represented by a circle with a clockwise arrow). The 'circulator' has three ports: one connected to the 'Spectrum analyser', one connected to the 'Repeater under test', and one connected to an 'attenuator'. The 'attenuator' is connected to a 'Channel filter', which is in turn connected to an 'LCR TDD Signal Generator'. The 'Repeater under test' is connected to another 'Channel filter', which is connected to a second 'LCR TDD Signal Generator'. + +Block diagram for Output Intermodulation measurement setup. + +**Figure A.9: Measuring system set-up for Output Intermodulation.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.10 Timing Accuracy + +![Block diagram for Timing Accuracy measurement setup.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +The diagram shows a measurement setup for Timing Accuracy. It features a 'Spectrum analyzer' on the left connected to a 'Repeater under test', which is connected to an 'LCR TDD Signal Generator' on the right. Above the 'Repeater under test' and 'LCR TDD Signal Generator', there are two lines labeled 'Frequency reference' and 'Frame Trigger'. The 'Frequency reference' line connects to the 'Spectrum analyzer', the 'Repeater under test', and the 'LCR TDD Signal Generator'. The 'Frame Trigger' line connects to the 'Spectrum analyzer', the 'Repeater under test', and the 'LCR TDD Signal Generator'. + +Block diagram for Timing Accuracy measurement setup. + +**Figure A.10: Measuring system set-up for Timing Accuracy.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +# Annex B (informative): Derivation of Test Requirements + +The Test Requirements in this specification have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in subclause 4.2. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test Requirements will differ from the Minimum Requirements, and the formula used for this relaxation is given in table B.1. + +| Clause number | Title | Minimum Requirement in TS 25.116 | Test Tolerance (TT) | Test Requirement in TS 25.153 | +|---------------|------------------------|-----------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 6 | Maximum output power | In normal conditions
Table 6.1 | 0,7 dB | Formula:
Upper limit + TT
Lower limit – TT
In normal conditions refer to
Table 6.4 | +| | | In extreme conditions
Table 6.2 | 0,7dB | In extreme conditions refer to
Table 6.5 | +| 9.1 | Spectrum emission mask | Tables 9.1, 9.2 and 9.3:
“Maximum level” = X dB | 1,5 dB | Formula:
Maximum level + TT
Refer to tables 9.5, 9.6 and
9.7 | +| 7 | Frequency stability | 7.1 minimum requirement | 12 Hz | Formula:
Relative error + TT
Refer to 7.5 Test requirements | +| 8 | Out of Band Gain | Table 8.1: Out of band gain
limits | 0,5 dB | Formula:
Maximum level + TT
Refer to table 8.2 | +| 9.2 | Spurious emissions | Tables 9.8, to 9.19 | 0 dB | | +| 10.1 | Error Vector Magnitude | 10.1.2 Minimum requirement | 0 % | Formula:
RSS Stimulus EVM and
Repeater EVM to get target
EVM
Refer to 10.1.5 Test
requirements | +| 10.2 | Peak code domain error | 10.2.2 Minimum requirement | 1,1 dB | Formula:
Maximum error + TT
Refer to 10.2.5 Test
requirements | +| 11 | Input intermodulation | 11.2 Minimum requirements,
and Tables 11.1 ,11.2 and
11.3 | 1,2 dB | Maximum in-band power
increase + TT
Refer to 11.5 Test
requirements. | +| 12 | Output intermodulation | 12.2 Minimum requirements | 1,5 dB for
spectrum emission
mask.
0 dB for spurious
emissions | Maximum level + TT
Refer to tables 9.5 to 9.19 | + +Table B.1: Derivation of Test Requirements + +# Annex C (informative): Acceptable uncertainty of Test Equipment + +This informative annex specifies the critical parameters of the components of an overall Test System (e.g. signal generators, signal analysers etc.) which are necessary when assembling a Test System which complies with subclause 5.1 Acceptable uncertainty of Test System. These Test Equipment parameters are fundamental to the accuracy of the overall Test System and are unlikely to be improved upon through System Calibration. + +**Table C.1: Equipment accuracy** + +| Test | Equipment accuracy | Test condition | +|---------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------| +| 6 Output power | Not critical | Not critical | +| 9.1 Spectrum emission mask | Not critical | Not critical | +| 9.2 Spurious emissions | Not critical | Not critical | +| 11 Input intermodulation (interferer requirement) | Not critical | Not critical | +| 7 Frequency error | $\pm 10$ Hz + timebase = 12 Hz | Range 0 to 500 Hz. (This is to allow for UE range that at 0,1 PPM is larger than BTS). | +| 10.1 Error vector magnitude | $\pm 2,5$ % (for single code) | $P\_Max-3$ to $P\_Max - 18$ dB
Applies for reading from 10% to 25%. | +| 10.2 Peak code domain error | $\pm 1$ dB | Measurements in the range -25 dB to -30 dB at signal power = $P_{max}$ | +| 8 Out of band gain | | | +| 11 Input intermodulation | Not critical | Not critical | +| 12 Output intermodulation | Not critical | Not critical | +| 13 ACRR | | | +| 14 Timing Accuracy | Not critical | Not critical | + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2009-10 | RAN4#52 bis | R4-093748 | | | TS skeleton created from 3GPP TS template. | | 0.0.1 | +| 2010-02 | RAN4#54 | R4-100999 | | | TS with the TP approved at RAN4#52bis and RAN4#53
R4-093756 Text proposal for TS25.153: Output Power
R4-094018 Text proposal for TS25.153: Frequency Error
R4-093752 Text proposal for TS25.153: EVM
R4-093757 Text proposal for TS25.153: PCDE
R4-093755 Text proposal for TS25.153: Output Intermodulation
R4-094017 Text proposal for TS25.153: Frequency bands and channel arrangements
R4-093753 Text proposal for TS25.153: Input Intermodulation
R4-093754 Text proposal for TS25.153: Out of Band Gain
R4-093751 Text proposal for TS25.153: ACRR
R4-094019 Text proposal for TS25.153: Timing Accuracy
R4-093759 Text proposal for TS25.153: Unwanted Emissions
R4-093760 Text proposal for 25.153: Clause 1 to Clause 3
R4-094638 Text proposal for 25.153: Clause 4
R4-094768 Text proposal for 25.153: Annex A to Annex D
R4-100998 Correction of the Figure A.10 of TS 25.153 | 0.0.1 | 1.0.0 | +| 2010-03 | RAN#47 | RP-100111 | | | Presentation to TSG for approval | 1.0.0 | 1.0.0 | +| 2010-03 | RAN#47 | RP-100111 | | | Approved by TSG RAN | 1.0.0 | 10.0.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | RAN#75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-09 | RAN#81 | | | | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25201/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-16/25_series/25201/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..570da1eff07c9e17fbc89b91c21c300c68e2a392 --- /dev/null +++ b/marked/Rel-16/25_series/25201/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da072d365abc411d9812ce96300c604d6a679f35e0fcf95cc40dd26643911e25 +size 38878 diff --git a/marked/Rel-16/25_series/25201/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-16/25_series/25201/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..145b66bbe9c292e4483acf4bcb1cb700431d0dad --- /dev/null +++ b/marked/Rel-16/25_series/25201/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fba1b5efcd68e6c122fd11826f670499255d265becb90d73d64408be8c50863f +size 17231 diff --git a/marked/Rel-16/25_series/25201/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/Rel-16/25_series/25201/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d5e47abe97ebb3b235352434fa219f17546eebb --- /dev/null +++ b/marked/Rel-16/25_series/25201/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:475f6da81a2594c949cacc76c33469b82138180ff9e99db1a85d50f14297f9c5 +size 17906 diff --git a/marked/Rel-16/25_series/25201/raw.md b/marked/Rel-16/25_series/25201/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..54330c762a07b7abe12dab586924b9c93013ee11 --- /dev/null +++ b/marked/Rel-16/25_series/25201/raw.md @@ -0,0 +1,476 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 6 | +| 4 General description of Layer 1 ..... | 7 | +| 4.1 Relation to other layers ..... | 7 | +| 4.1.1 General Protocol Architecture ..... | 7 | +| 4.1.2 Service provided to higher layers ..... | 7 | +| 4.2 General description of Layer 1 ..... | 8 | +| 4.2.1 Multiple Access ..... | 8 | +| 4.2.2 Channel coding and interleaving..... | 9 | +| 4.2.3 Modulation and spreading ..... | 9 | +| 4.2.4 Physical layer procedures ..... | 9 | +| 4.2.5 Physical layer measurements..... | 10 | +| 4.2.6 Relationship of the physical layer functions ..... | 10 | +| 5 Document structure of physical layer specification..... | 11 | +| 5.1 Overview ..... | 11 | +| 5.2 TS 25.201: Physical layer – General description ..... | 11 | +| 5.3 TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD) ..... | 11 | +| 5.4 TS 25.212: Multiplexing and channel coding (FDD) ..... | 11 | +| 5.5 TS 25.213: Spreading and modulation (FDD) ..... | 12 | +| 5.6 TS 25.214: Physical layer procedures (FDD) ..... | 12 | +| 5.7 TS 25.215: Physical layer – Measurements (FDD)..... | 12 | +| 5.8 TS 25.221: Physical channels and mapping of transport channels onto physical channels (TDD) ..... | 12 | +| 5.9 TS 25.222: Multiplexing and channel coding (TDD) ..... | 13 | +| 5.10 TS 25.223: Spreading and modulation (TDD)..... | 13 | +| 5.11 TS 25.224: Physical layer procedures (TDD) ..... | 13 | +| 5.12 TS 25.225: Physical layer – Measurements (TDD) ..... | 13 | +| 5.13 TR 25.833: Physical layer items not for inclusion in Release '99..... | 13 | +| 5.14 TR 25.944: Channel coding and multiplexing examples ..... | 13 | +| Annex A (informative): Preferred mathematical notations ..... | 14 | +| Annex B (informative): Change history..... | 15 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes a general description of the physical layer of the UTRA radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 25.200 series. The TS 25.200 series specifies the Uu point for the 3G mobile system, and defines the minimum level of specifications required for basic connections in terms of mutual connectivity and compatibility. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.225: "Physical layer – Measurements (TDD)". +- [11] 3GPP TR 25.833: "Physical layer items not for inclusion in Release '99". +- [12] 3GPP TR 25.944: "Channel coding and multiplexing examples". +- [13] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [14] 3GPP TS 25.302: "Services provided by the physical layer". +- [15] 3GPP TS 25.101: "UE Radio transmission and reception (FDD)". +- [16] 3GPP TS 25.102: "UE Radio transmission and reception (TDD)". +- [17] 3GPP TS 25.104: "BTS Radio transmission and reception (FDD)". +- [18] 3GPP TS 25.105: "BTS Radio transmission and reception (TDD)". + +# 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-----------------------------------------------| +| 16QAM | 16 Quadrature Amplitude Modulation | +| 64QAM | 64 Quadrature Amplitude Modulation | +| ARQ | Automatic Repeat Request | +| BER | Bit Error Rate | +| CCTrCH | Coded Composite Transport Channel | +| DCA | Dynamic channel allocation | +| DCH | Dedicated Channel | +| DS-CDMA | Direct-Sequence Code Division Multiple Access | +| DSCH | Downlink Shared Channel | +| DwPCH | Downlink Pilot Channel | +| DwPTS | Downlink Pilot Time Slot | +| E-DCH | Enhanced Dedicated Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-RGCH | E-DCH Relative Grant Channel | +| FDD | Frequency Division Duplex | +| FEC | Forward Error Correction | +| FER | Frame Error Rate | +| GSM | Global System for Mobile Communication | +| HS-DSCH | High Speed Downlink Shared channel | +| HS-SCCH | HS-DSCH Shared Control Channel | +| L1 | Layer 1 (physical layer) | +| L2 | Layer 2 (data link layer) | +| L3 | Layer 3 (network layer) | +| LAC | Link Access Control | +| MAC | Medium Access Control | +| MBSFN | MBMS over a Single Frequency Network | +| Mcps | Mega Chip Per Second | +| MIMO | Multiple Input Multiple Output | +| QPSK | Quaternary Phase Shift Keying | +| RACH | Random Access Channel | +| RF | Radio Frequency | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| SCH | Synchronisation Channel | +| SIR | Signal-to-Interference Ratio | +| TDD | Time Division Duplex | +| TDMA | Time Division Multiple Access | +| TFCI | Transport-Format Combination Indicator | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UpPTS | Uplink Pilot Time Slot | +| UpPCH | Uplink Pilot Channel | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | +| WCDMA | Wide-band Code Division Multiple Access | + +# 4 General description of Layer 1 + +## 4.1 Relation to other layers + +### 4.1.1 General Protocol Architecture + +Radio interface which is prescribed by this specification means the Uu point between User Equipment (UE) and network. The radio interface is composed of Layers 1, 2 and 3. Layer 1 is based on WCDMA/TD-SCDMA technology + +and the TS 25.200 series describes the Layer-1 specification. Layers 2 and 3 of the radio interface are described in the TS 25.300 series. + +![Figure 1: Radio interface protocol architecture around the physical layer. The diagram shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). Layer 3 is connected to Layer 2 via a Service Access Point (SAP). Layer 2 is connected to Layer 1 via another SAP. Layer 2 also has a SAP on its upper side. A vertical line on the left, labeled 'Control / Measurements', connects Layer 3 and Layer 1 to the Physical layer. On the right, 'Logical channels' are shown above Layer 2, and 'Transport channels' are shown between Layer 2 and Layer 1.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +Figure 1: Radio interface protocol architecture around the physical layer. The diagram shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). Layer 3 is connected to Layer 2 via a Service Access Point (SAP). Layer 2 is connected to Layer 1 via another SAP. Layer 2 also has a SAP on its upper side. A vertical line on the left, labeled 'Control / Measurements', connects Layer 3 and Layer 1 to the Physical layer. On the right, 'Logical channels' are shown above Layer 2, and 'Transport channels' are shown between Layer 2 and Layer 1. + +**Figure 1: Radio interface protocol architecture around the physical layer** + +Figure 1 shows the UTRA radio interface protocol architecture around the physical layer (Layer 1). The physical layer interfaces the Medium Access Control (MAC) sub-layer of Layer 2 and the Radio Resource Control (RRC) Layer of Layer 3. The circles between different layer/sub-layers indicate Service Access Points (SAPs). The physical layer offers different Transport channels to MAC. A transport channel is characterized by how the information is transferred over the radio interface. MAC offers different Logical channels to the Radio Link Control (RLC) sub-layer of Layer 2. A logical channel is characterized by the type of information transferred. Physical channels are defined in the physical layer. There are two duplex modes: Frequency Division Duplex (FDD) and Time Division Duplex (TDD). In the FDD mode a physical channel is characterized by the code, frequency and in the uplink the relative phase (I/Q); in addition E-HICH and E-RGCH are also defined by a specific orthogonal signature sequence. In the TDD mode the physical channels are also characterized by the timeslot and additionally, the E-HICH is further defined by a specific orthogonal signature sequence. For 1.28Mcps TDD, the E-HICH can be also further defined by a group of orthogonal signature sequences. The physical layer is controlled by RRC. + +### 4.1.2 Service provided to higher layers + +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. The physical layer is expected to perform the following functions in order to provide the data transport service. See also TS 25.302: + +- Macrodiversity distribution/combining and soft handover execution. +- Error detection on transport channels and indication to higher layers. +- FEC encoding/decoding of transport channels. +- Multiplexing of transport channels and demultiplexing of coded composite transport channels (CCTrCHs). +- Rate matching of coded transport channels to physical channels. +- Mapping of coded composite transport channels on physical channels. +- Power weighting and combining of physical channels. +- Modulation and spreading/demodulation and despreading of physical channels. +- Frequency and time (chip, bit, slot, frame) synchronisation. +- Radio characteristics measurements including FER, SIR, Interference Power, etc., and indication to higher layers. +- Inner - loop power control. +- RF processing. (Note: RF processing is defined in TS 25.100 series). +- synchronization shift control + +- Beamforming +- MIMO transmission +- Hybrid ARQ soft-combining for HS-DSCH and E-DCH + +When network elements (UEs and network) provide compatible service bearers (for example support a speech bearer) they should be assured of successful interworking. Moreover, different implementation options of the same (optional) feature would lead to incompatibility between UE and network. Therefore, this shall be avoided. + +## 4.2 General description of Layer 1 + +### 4.2.1 Multiple Access + +The access scheme is Direct-Sequence Code Division Multiple Access (DS-CDMA) with information either spread over approximately 5 MHz (FDD and 3.84 Mcps TDD) bandwidth, thus also often denoted as Wideband CDMA (WCDMA) due that nature, 10MHz (7.68 Mcps TDD) bandwidth, or 1.6MHz (1.28Mcps TDD), thus also often denoted as Narrowband CDMA. UTRA has two modes, FDD (Frequency Division Duplex) & TDD (Time Division Duplex), for operating with paired and unpaired bands respectively. The possibility to operate in either FDD or TDD mode allows for efficient utilisation of the available spectrum according to the frequency allocation in different regions. FDD and TDD modes are defined as follows: + +FDD: A duplex method whereby uplink and downlink transmissions use two separated radio frequencies. In the FDD, each uplink and downlink uses the different frequency band. A pair of frequency bands which have specified separation shall be assigned for the system. + +TDD: A duplex method whereby uplink and downlink transmissions are carried over same radio frequency by using synchronised time intervals. In the TDD, time slots in a physical channel are divided into transmission and reception part. Information on uplink and downlink are transmitted reciprocally. + +UTRA TDD has three options, the 3.84Mcps option and the 1.28Mcps option, the 7.68Mcps TDD option. In UTRA TDD there is TDMA component in the multiple access in addition to DS-CDMA. Thus the multiple access has been also often denoted as TDMA/CDMA due to the added TDMA nature. + +A 10 ms radio frame is divided into 15 slots (2560 chip/slot at the chip rate 3.84 Mcps). A physical channel is therefore defined as a code (or number of codes) and additionally in TDD mode the sequence of time slots completes the definition of a physical channel. In FDD, for HS-DSCH, E-DCH and associated signalling channels, 2ms sub-frames consisting of 3 slots are defined. + +The information rate of the channel varies with the symbol rate being derived from the 3.84 Mcps chip rate and the spreading factor. Spreading factors are from 256 to 2 with FDD uplink, from 512 to 4 with FDD downlink, and from 16 to 1 for TDD uplink and downlink. Thus the respective modulation symbol rates vary from 1920 k symbols/s to 15 k symbols/s (7.5 k symbols/s) for FDD uplink (downlink), and for TDD the momentary modulation symbol rates shall vary from 3.84 M symbols/s to 240 k symbols/s. + +For the 7.68Mcps TDD option, a 10 ms radio frame is divided into 15 slots (5120 chip/slot). A physical channel is therefore defined as a code (or number of codes) and the sequence of time slots. + +The information rate of the channel varies with the symbol rate being derived from the 7.68 Mcps chip rate and the spreading factor. Spreading factors are from 32 to 1 for both uplink and downlink. Thus the respective modulation symbol rates vary from 7.68 M symbols/s to 240 k symbols/s. + +For 1.28Mcps TDD option, a 10 ms radio frame is divided into two 5ms sub-frames. In each sub-frame, there are 7 normal time slots and 3 special time slots. Note that in case of entire carrier dedicated to MBSFN there are 7 normal MBSFN Traffic time slots and 1 short MBSFN Special time slot in each sub-frame. A basic physical channel is therefore characterised by the frequency, code and time slot. + +The information rate of the channel varies with the symbol rate being derived from the 1.28 Mcps chiprate and the spreading factor. Spreading factors is from 16 to 1 for both uplink and downlink. Thus the respective modulation symbol rates shall vary from 80.0K symbols/s to 1.28M symbols/s. + +### 4.2.2 Channel coding and interleaving + +For the channel coding in UTRA two options are supported for FDD and three options are supported for TDD: + +- Convolutional coding. +- Turbo coding. +- No coding (only TDD). + +Channel coding selection is indicated by higher layers. In order to randomise transmission errors, bit interleaving is performed further. + +### 4.2.3 Modulation and spreading + +The UTRA modulation scheme is QPSK (8PSK is also used for 1.28Mcps TDD option). For HS-DSCH transmission, 16QAM and 64QAM can also be used. 16QAM and 64QAM are further supported for E-DCH transmission, and 16QAM is supported for MBSFN1 FACH transmissions. Pulse shaping is specified in the TS 25.100 series. + +With CDMA nature the spreading (& scrambling) process is closely associated with modulation. In UTRA different families of spreading codes are used to spread the signal: + +- For separating channels from same source, channelisation codes derived with the code tree structure as given in TS 25.213 and 25.223 are used. +- For separating different cells the following solutions are supported. +- FDD mode: Gold codes with 10 ms period (38400 chips at 3.84 Mcps) used, with the actual code itself length $2^{18}-1$ chips, as defined in TS 25.213. +- TDD mode: for the 3.84Mcps and 1.28Mcps TDD options, scrambling codes with the length 16 are used as defined in TS 25.223; for the 7.68Mcps TDD option, scrambling codes with length 32 are used. +- For separating different UEs the following code families are defined. +- FDD mode: Gold codes with 10 ms period, or alternatively S(2) codes 256 chip period. +- TDD mode: for the 3.84Mcps and 1.28Mcps TDD options, codes with period of 16 chips and midamble sequences of different length depending on the environment; for the 7.68Mcps TDD option, codes with period of 32 chips and midamble sequences of different length depending on the environment. + +### 4.2.4 Physical layer procedures + +There are several physical layer procedures involved with UTRA operation. Such procedures covered by physical layer description are: + +- 1) The power control, inner loop for FDD mode, and for the 3.84Mcps TDD and 7.68Mcps TDD options open loop in uplink and inner loop in downlink, for 1.28Mcps TDD option, open loop in uplink and inner loop in both uplink and downlink. +- 2) Cell search operation. +- 3) Uplink synchronization control with open and closed loop. +- 4) Random access +- 5) Procedures related to HS-DSCH transmission, including HS-SCCH less operation and MIMO transmission. +- 6) Procedures related to E-DCH transmission, including MIMO transmission. +- 7) Procedures related to discontinuous transmission and reception. + +--- + +1 MBSFN transmission is characterised by a group of synchronised base stations transmitting the same wave form by using a common scrambling code + +### 4.2.5 Physical layer measurements + +Radio characteristics including FER, SIR, Interference power, etc., are measured and reported to higher layers and network. Such measurements are: + +- 1) Handover measurements for handover within UTRA. Specific features being determined in addition to the relative strength of the cell, for the FDD mode the timing relation between for cells for support of asynchronous soft handover. +- 2) The measurement procedures for preparation for handover to GSM900/GSM1800. +- 3) The measurement procedures for UE before random access process. +- 4) The measurement procedures for Dynamic Channel Allocation (DCA) of TDD mode. +- 5) UTRAN measurements. + +### 4.2.6 Relationship of the physical layer functions + +The functionality of the layer 1 is split over several specifications each for FDD and TDD. The following figures, although not categorical, show as an introduction the relationship of layer 1 functions by specification in terms of users plane information flow. + +![Diagram of FDD layer 1 functions relationships by specification](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +This diagram illustrates the functional relationships for FDD Layer 1. It features five rectangular blocks. At the top left is '25.214 procedures', which has a dashed downward arrow to '25.211' and a dashed rightward arrow to '25.213', both labeled 'control'. To the right of '25.214' is '25.215 measurements'. Below '25.211' is '25.212', which receives 'traffic' from the left and has solid arrows pointing to '25.213'. '25.213' is a central block with a solid arrow pointing to the right. + +Diagram of FDD layer 1 functions relationships by specification + +Figure 2 - FDD layer 1 functions relationships by specification + +![Diagram of TDD layer 1 functions relationships by specification](b0211cee4b20034939d883ac0d70f696_img.jpg) + +This diagram illustrates the functional relationships for TDD Layer 1. It features five rectangular blocks. At the top left is '25.224 procedures', which has a dashed downward arrow to '25.221' and a dashed rightward arrow to '25.223', both labeled 'control'. To the right of '25.224' is '25.225 measurements'. Below '25.221' is '25.222', which receives 'traffic' from the left and has solid arrows pointing to '25.223'. '25.223' is a central block with a solid arrow pointing to the right. + +Diagram of TDD layer 1 functions relationships by specification + +Figure 3 - TDD layer 1 functions relationships by specification + +# --- 5 Document structure of physical layer specification + +## 5.1 Overview + +The physical layer specification consists of a general document (TS 25.201), five FDD mode documents (TS 25.211 through 25.215), five TDD mode documents (TS 25.221 through 25.225). In addition, there are two technical reports (TR 25.833 and 25.944). + +## 5.2 TS 25.201: Physical layer – General description + +The scope is to describe: + +- the contents of the Layer 1 documents (TS 25.200 series); +- where to find information; +- a general description of Layer 1. + +## 5.3 TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD) + +The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the FDD mode, and to specify: + +- the different transport channels that exist; +- which physical channels exist; +- what is the structure of each physical channel, slot format etc.; +- relative timing between different physical channels in the same link, and relative timing between uplink and downlink; +- mapping of transport channels onto the physical channels. + +## 5.4 TS 25.212: Multiplexing and channel coding (FDD) + +The scope is to describe multiplexing, channel coding and interleaving in the FDD mode, and to specify: + +- coding and multiplexing of transport channels into CCTrCHs; +- channel coding alternatives; +- coding for Layer 1 control information, such as TFCI; +- the different interleavers; +- how is rate matching done; +- physical channel segmentation and mapping. + +## 5.5 TS 25.213: Spreading and modulation (FDD) + +The scope is to establish the characteristics of the spreading and modulation in the FDD mode, and to specify: + +- the spreading (channelisation plus scrambling); +- generation of channelisation and scrambling codes; +- generation of RACH preamble codes; +- generation of SCH synchronisation codes; + +- modulation. + +RF channel arrangements and Pulse shaping are specified in TS 25.101 for UE and in TS 25.104 for Node-B. + +## 5.6 TS 25.214: Physical layer procedures (FDD) + +The scope is to establish the characteristics of the physical layer procedures in the FDD mode, and to specify: + +- cell search procedures; +- power control procedures; +- random access procedure. + +## 5.7 TS 25.215: Physical layer – Measurements (FDD) + +The scope is to establish the characteristics of the physical layer measurements in the FDD mode, and to specify: + +- the measurements that Layer 1 is to perform; +- reporting of measurements to higher layers and network; +- handover measurements, idle-mode measurements etc. + +## 5.8 TS 25.221: Physical channels and mapping of transport channels onto physical channels (TDD) + +The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the TDD mode, and to specify: + +- transport channels; +- physical channels, structure and contents; +- mapping of transport channels onto the physical channels. + +## 5.9 TS 25.222: Multiplexing and channel coding (TDD) + +The scope is to describe multiplexing, channel coding and interleaving in the TDD mode, and to specify: + +- channel coding and multiplexing of transport channels into CCTrCHs; +- channel coding alternatives; +- coding for Layer 1 control information, such as TFCI; +- interleaving; +- rate matching; +- physical channel segmentation and mapping. + +## 5.10 TS 25.223: Spreading and modulation (TDD) + +The scope is to establish the characteristics of the spreading and modulation in the TDD mode, and to specify: + +- data modulation; +- spreading; +- generation of synchronisation codes. + +RF channel arrangements and Pulse shaping are specified in TS 25.102 for UE and in TS 25.105 for Node-B. + +## 5.11 TS 25.224: Physical layer procedures (TDD) + +The scope is to establish the characteristics of the physical layer procedures in the TDD mode, and to specify: + +- cell synchronisation; +- timing advance; +- power control procedures; +- idle mode tasks. + +## 5.12 TS 25.225: Physical layer – Measurements (TDD) + +The scope is to establish the characteristics of the physical layer measurements in the TDD mode, and to specify: + +- the measurements that Layer 1 is to perform; +- reporting of measurements to higher layers and network; +- handover measurements, idle-mode measurements etc. + +## 5.13 TR 25.833: Physical layer items not for inclusion in Release '99 + +The scope is to collect materials on UTRA physical layer items not included in the Release '99 specification documents, such as DSCH control channel, FAUSCH, Hybrid ARQ, 4-state SCCC turbo coding and ODMA. + +## 5.14 TR 25.944: Channel coding and multiplexing examples + +The scope is to describe examples of channel coding and multiplexing for transport channels of various types and cases. + +# Annex A (informative): Preferred mathematical notations + +The following table contains the preferred mathematical notations used in L1 documentation. + +| Item | Notation | +|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| multiply product | cross sign, e.g. $a \times b$ | +| matrix product | dot sign, e.g. $a \cdot b$ | +| scalar product (product of a matrix by a scalar) | dot sign, scalar should precede matrix
$(1 + j) \cdot \begin{bmatrix} u \\ v \end{bmatrix}$ e.g. | +| matrix dimensioning | number of rows $\times$ number of column, e.g.:
$R \times C$ | +| Kronecker product | $a \otimes b$ | +| bracketing of sets (all elements of same type, not ordered elements) | curly brackets $\{ \}$ , e.g.
$\{a_i\}_{i \in \{1, 2, \dots, p\}}$ $\{a_1, a_2, \dots, a_p\}$ , or | +| bracketing of lists (all elements not necessary of same type, ordered elements) | round brackets (), e.g. $(A, u, x)$ | +| bracketing of sequences (all elements of same type, ordered elements) | angle brackets, e.g. $\langle a_1, a_2, \dots, a_p \rangle$ or
$\langle a_i \rangle_{i \in \{1, 2, \dots, p\}}$ | +| bracketing of function argument | round brackets, e.g. $f(x)$ | +| bracketing of array index | square brackets, e.g. $a[x]$ | +| bracketing of matrix or vector | square brackets [], e.g. $\begin{bmatrix} x \\ y \end{bmatrix}$ , $\begin{bmatrix} x & y \end{bmatrix}$ , or $\begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix}$ | +| Separation of indexes | use a comma : e.g. $N_{i,j}$ | +| use of italic for symbols | a symbol should be either in italic or in normal font, but mixing up should be avoided. | +| bracketing of arithmetic expression to force precedence of operations | round brackets : e.g. $(a + b) \times c$ | +| necessity of bracketing arithmetic expressions | When only + and $\times$ bracketing is not necessary. When the mod operator is used explicit bracketing of mod operands and possibly result should be done. | +| number type | in a context of non negative integer numbers, some notes should stress when a number is signed, or possibly fractional. | +| binary xor and and | respectively use + or $\cdot$ . If no "mod 2" is explicitly in the expression some text should stress that the operation is modulo 2. | +| matrix or vector transpose | $v^T$ | +| $1 \times 1$ matrices | implicitly cast to its unique element. | +| vector dot product | $u^T \cdot v$ for column vectors, and $u \cdot v^T$ for line vectors | +| complex conjugate | $v^*$ | +| matrix or vector Hermitian transpose | $v^H$ | +| real part and imaginary part of complex numbers. | $\text{Re}(x)$ and $\text{Im}(x)$ | + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | RAN_05 | RP-99586 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | - | - | - | | Modified in terms of formality. The contents were not changed. | 3.0.0 | 3.0.1 | +| 31/03/00 | RAN_07 | RP-000059 | 001 | - | Editorial revision | 3.0.1 | 3.0.2 | +| 26/06/00 | RAN_08 | RP-000264 | 002 | - | Corrections to align with TS 25.212 and TR 25.944 | 3.0.2 | 3.1.0 | +| 26/06/00 | RAN_08 | RP-000264 | 003 | 1 | Editorial corrections | 3.0.2 | 3.1.0 | +| 26/06/00 | RAN_08 | RP-000264 | 004 | - | Physical layer information flow | 3.0.2 | 3.1.0 | +| 26/06/00 | RAN_08 | RP-000264 | 005 | 1 | Preferred mathematical notation for editorial unity of L1 documentation | 3.0.2 | 3.1.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.1.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 006 | 1 | Inclusion of 1.28Mcps TDD in TS 25.201 | 3.1.0 | 4.0.0 | +| 14/12/01 | RAN_14 | RP-010735 | 008 | - | Removal of slow power control and ODMA from TS 25.201 | 4.0.0 | 4.1.0 | +| 08/03/02 | RAN_15 | RP-020231 | 010 | 1 | Removal of channel coding option "no coding" for FDD | 4.1.0 | 4.2.0 | +| 08/03/02 | RAN_15 | RP-020058 | 013 | - | Specification of HS-DSCH for Release 5 in 25.201 | 4.1.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020306 | 017 | - | Downlink bit mapping | 5.0.0 | 5.1.0 | +| 10/09/02 | RAN_17 | RP-020580 | 018 | - | Correction on the description of TS and layer | 5.1.0 | 5.2.0 | +| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.2.0 | 6.0.0 | +| 13/12/04 | RAN_26 | RP-040449 | 019 | - | Introduction of E-DCH | 6.0.0 | 6.1.0 | +| 16/06/05 | RAN_28 | RP-050250 | 021 | - | Feature Clean Up: Removal of "CPCH" | 6.1.0 | 6.2.0 | +| 20/03/06 | RAN_31 | RP-060079 | 023 | - | Introduction of 7.68Mcps TDD option | 6.2.0 | 7.0.0 | +| 29/09/06 | RAN_33 | RP-060492 | 025 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.0.0 | 7.1.0 | +| 07/03/07 | RAN_35 | RP-070115 | 031 | - | Introduction of CPC related functionality | 7.1.0 | 7.2.0 | +| 07/03/07 | RAN_35 | RP-070114 | 032 | - | Introduction of MIMO | 7.1.0 | 7.2.0 | +| 07/03/07 | RAN_35 | RP-070118 | 028 | - | Introduction of E-DCH for 1.28Mcps TDD | 7.1.0 | 7.2.0 | +| 07/03/07 | RAN_35 | RP-070116 | 026 | 2 | Introduction of 64QAM for HSDPA | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070388 | 027 | 2 | Introduction of 16QAM for HSUPA | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070385 | 029 | 1 | Support for MBSFN operation | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070384 | 030 | 1 | Support for DL only SFN operation for MBMS FDD | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070386 | 034 | - | Support for 1.28Mcps TDD MBSFN operation | 7.2.0 | 7.3.0 | +| 11/09/07 | RAN_37 | RP-070640 | 0035 | 1 | Minor modification related to EDCH in 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 27/11/07 | RAN_38 | RP-070943 | 0037 | 1 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.4.0 | 7.5.0 | +| 04/03/08 | RAN_39 | - | - | - | Release 8 version created further to RAN_39 decision | 7.5.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080356 | 0039 | - | Introduction 64QAM for 1.28Mcps TDD HSDPA | 8.0.0 | 8.1.0 | +| 18/09/09 | RAN_45 | - | - | - | Release 9 version created further to RAN_45 decision | 8.1.0 | 9.0.0 | +| 21/03/11 | SP-51 | - | - | - | Release 10 version created further to SP-51 decision | 9.0.0 | 10.0.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 04/12/12 | RAN_58 | RP-121845 | 0040 | - | Introduction of uplink MIMO and 64QAM | 11.0.0 | 11.1.0 | +| 2014-09 | SP_65 | - | - | - | Update to Rel-12 version (MCC) | 11.1.0 | 12.0.0 | +| 2015-12 | SP_70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e- | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25212/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-16/25_series/25212/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9da7d5e2127ad4fe87ac04f6b976237a3e44be4e --- /dev/null +++ b/marked/Rel-16/25_series/25212/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3cb9fe2d413fdca4f0492bb77b62e8ea1a1708511d5c41f303afd4c011441d1 +size 52887 diff --git a/marked/Rel-16/25_series/25212/08eda25d46345f5d500bdfbe2d64bc7e_img.jpg b/marked/Rel-16/25_series/25212/08eda25d46345f5d500bdfbe2d64bc7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75c378d4f17bc8a6a02543afff26ebad598b4202 --- /dev/null +++ b/marked/Rel-16/25_series/25212/08eda25d46345f5d500bdfbe2d64bc7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2511e8c9ada8fd1d8928990f5fbab367049736c37c959e0066f747f1b4fcc463 +size 38122 diff --git a/marked/Rel-16/25_series/25212/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/Rel-16/25_series/25212/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d89a30412f963139fb876db5c8c96c97e246adf --- /dev/null +++ b/marked/Rel-16/25_series/25212/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b091d58a2543f5dbc64e18fb69158f0492af28ba5d4a5605d4707ef89543f32d +size 48829 diff --git a/marked/Rel-16/25_series/25212/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25212/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6135e3c7483578aa7ebbc3ae9f7d7c6e49bb0b06 --- /dev/null +++ b/marked/Rel-16/25_series/25212/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cbbae89537c306c37833cb0805298ff4fd8c60b32694fb54ef8904647f234c3 +size 103363 diff --git a/marked/Rel-16/25_series/25212/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/25_series/25212/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5b47b2c8d098433ac73be0e308ecc07ab4644dd --- /dev/null +++ b/marked/Rel-16/25_series/25212/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:289b152dcca8ba60c9cf8b6d8e1286a3e2afc99382ee11ce70c83665c9782d17 +size 34668 diff --git a/marked/Rel-16/25_series/25212/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/25_series/25212/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec2ea86c4426fed6d535dcf19b24eb0db45be32 --- /dev/null +++ b/marked/Rel-16/25_series/25212/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fa9e30215874f91549ba33b4607ee24f6851b91618dc4ba073de117ce5b8934 +size 46902 diff --git a/marked/Rel-16/25_series/25212/305c3b31c7d60405cf039fd098ba4669_img.jpg b/marked/Rel-16/25_series/25212/305c3b31c7d60405cf039fd098ba4669_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89d56c980e0dc4a8a77782dc16d36ef6e1113d21 --- /dev/null +++ b/marked/Rel-16/25_series/25212/305c3b31c7d60405cf039fd098ba4669_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3fe4a27501e1b50149aed1b88442932522882927c76ed1af4912df2120f982a +size 31457 diff --git a/marked/Rel-16/25_series/25212/30fe9e9487585118063341332e802e98_img.jpg b/marked/Rel-16/25_series/25212/30fe9e9487585118063341332e802e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a574dc938e4e50a1d1f88e45ca18d40cebe63a7 --- /dev/null +++ b/marked/Rel-16/25_series/25212/30fe9e9487585118063341332e802e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ed35b4ec9b94f4e6bf4868df803f04e689a63b1efaf0120fea3ad332d9fb12 +size 27088 diff --git a/marked/Rel-16/25_series/25212/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/25_series/25212/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4686e0db0a17842d6cc30b8f14098e61f05f3f85 --- /dev/null +++ b/marked/Rel-16/25_series/25212/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe941fa2985c48042b53d08a62bd85df5be320ebdaefea70ced3ce4c15705598 +size 62310 diff --git a/marked/Rel-16/25_series/25212/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25212/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba37d44bac21f0311738cfdb026a8ed48207e32e --- /dev/null +++ b/marked/Rel-16/25_series/25212/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f4722d10f158e3e9c1dd2fc4743c5ce742d8a739bcb9ab2bc46c0afba25df73 +size 152738 diff --git a/marked/Rel-16/25_series/25212/46b47a38697e3aedb09cccd7eba47192_img.jpg b/marked/Rel-16/25_series/25212/46b47a38697e3aedb09cccd7eba47192_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6312532b7dff1879774fafc2ddfd916f5ff530aa --- /dev/null +++ b/marked/Rel-16/25_series/25212/46b47a38697e3aedb09cccd7eba47192_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:673e9b9699590d5582130fa222ea95b17f1442d45e6d7158eb5053a420717fb2 +size 26291 diff --git a/marked/Rel-16/25_series/25212/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-16/25_series/25212/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f99a6fcae5ad19cced8f46ea5a2663526904ab74 --- /dev/null +++ b/marked/Rel-16/25_series/25212/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec7a28073605773962a54cdaa42006657e3ff1aaee6e894a9a10c0ebf916ce0b +size 28400 diff --git a/marked/Rel-16/25_series/25212/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/25_series/25212/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1306c09138ff420da0837f8c4604c4ef10b02b0 --- /dev/null +++ b/marked/Rel-16/25_series/25212/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3f8b7d3cefda36f70ec4e00200d3c75dc1270f8630e566a7576640fa4aa5465 +size 99949 diff --git a/marked/Rel-16/25_series/25212/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/25_series/25212/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba61352d7d0baa9acdeaadfe7d35d5b475e653f --- /dev/null +++ b/marked/Rel-16/25_series/25212/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:095adac401fe10a118655f99e870fb62d89fa9a9c0559aca378812e5f8dc2c93 +size 59934 diff --git a/marked/Rel-16/25_series/25212/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/marked/Rel-16/25_series/25212/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a0a72eca7366fa83a036764a11d89de5a72b055 --- /dev/null +++ b/marked/Rel-16/25_series/25212/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddfa28361da56da95e908fc332856586f932c3bdd9892232a73b626b8c10760c +size 24558 diff --git a/marked/Rel-16/25_series/25212/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/25_series/25212/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8464d3329c45158f94ef8dc1230f2d80fb61e3a5 --- /dev/null +++ b/marked/Rel-16/25_series/25212/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:129d096ed7f462a2e3277537919ff01e972360a1cb2006da6f79b3dbfd2393b0 +size 54933 diff --git a/marked/Rel-16/25_series/25212/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/marked/Rel-16/25_series/25212/6059b0a3a051cc20b414d51a4e412f3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..836a529f458ef6fa3fbc4baccb27501a852beab3 --- /dev/null +++ b/marked/Rel-16/25_series/25212/6059b0a3a051cc20b414d51a4e412f3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c7074a5bbfe9df0aea9932d8a90029a8e4456fcf7b8756d2c4f3d4b7cf6f587 +size 30294 diff --git a/marked/Rel-16/25_series/25212/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Rel-16/25_series/25212/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1836872cf6da659e1fc1c2b72f51a0b9c72cee79 --- /dev/null +++ b/marked/Rel-16/25_series/25212/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b08000712ab9a41d8eb807571ef0634bd3e15a8c4197b177763ed9bedffdb6c +size 55532 diff --git a/marked/Rel-16/25_series/25212/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/marked/Rel-16/25_series/25212/67a1dd734d3de6e31754caf85d6fe77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2502f1e0f6d6fd2eeb02b93b9f2b65617dfda8a6 --- /dev/null +++ b/marked/Rel-16/25_series/25212/67a1dd734d3de6e31754caf85d6fe77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbe9002bd9c086617e0ea814fa5cbfa9a5d8da875267138898743afa5960d056 +size 24133 diff --git a/marked/Rel-16/25_series/25212/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-16/25_series/25212/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3925dd4e18a312d2ef52bf1244b3379a3c469910 --- /dev/null +++ b/marked/Rel-16/25_series/25212/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85aefeb86f1f4799084b72971564961e8cebc3008089d97442a1397dda3f4586 +size 12547 diff --git a/marked/Rel-16/25_series/25212/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-16/25_series/25212/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1eb411c213b2668d2e914e5faac057afdfb44fb --- /dev/null +++ b/marked/Rel-16/25_series/25212/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fed1f4bcc27963db1a106bf8216fc119851c3e8b0ff205da46c38a64776c60e +size 32149 diff --git a/marked/Rel-16/25_series/25212/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25212/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..090305243984fd7253268575a94ed6ee5aa9a74a --- /dev/null +++ b/marked/Rel-16/25_series/25212/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0aaab5bc5b75b3fa70a8e9de567a647d739a289934bf3b7989401051cdf8197 +size 103088 diff --git a/marked/Rel-16/25_series/25212/819f1d00e68b342a246b64fa888a97f9_img.jpg b/marked/Rel-16/25_series/25212/819f1d00e68b342a246b64fa888a97f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a8fe7483652cb95ff28ce37bde17fee6c404899 --- /dev/null +++ b/marked/Rel-16/25_series/25212/819f1d00e68b342a246b64fa888a97f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a918e600e6eae7058273788bcfafdd262e4c916191030e4bace720ef5bfa4172 +size 19040 diff --git a/marked/Rel-16/25_series/25212/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/25_series/25212/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca57b2eba97bc2b7684a7a147e66a91901f5410 --- /dev/null +++ b/marked/Rel-16/25_series/25212/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5428ac35f423a5e59356fb54e45836fe4440237448a03c10a34377a79cfdd880 +size 53934 diff --git a/marked/Rel-16/25_series/25212/91aa519060714a3ebba978bb68cbf648_img.jpg b/marked/Rel-16/25_series/25212/91aa519060714a3ebba978bb68cbf648_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911a0a3d34ac2270d659c0cd7d98a83114a950ad --- /dev/null +++ b/marked/Rel-16/25_series/25212/91aa519060714a3ebba978bb68cbf648_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38d9c83ac2dd1907a682d8f63544dd45818cb5582e0e1d5c5a8ab46d344361c0 +size 19234 diff --git a/marked/Rel-16/25_series/25212/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-16/25_series/25212/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb846b00c5e3aab209557572588623d87c292c7c --- /dev/null +++ b/marked/Rel-16/25_series/25212/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5801fd0b3a787cef4ec68100fed3526bee2e27260030d416c89410e58cd5ff31 +size 50593 diff --git a/marked/Rel-16/25_series/25212/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/25_series/25212/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0afae3df94eb27d38ac58962630bcf90c74c3b9 --- /dev/null +++ b/marked/Rel-16/25_series/25212/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b11217c3ad267e5c8273ffa68d998b15db19c4b763ddc70c17d500194bee9f1f +size 45929 diff --git a/marked/Rel-16/25_series/25212/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/25_series/25212/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2ae98797df6aac38b84308dfe0378799746dd29 --- /dev/null +++ b/marked/Rel-16/25_series/25212/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73aa3e87f045f1bc7770ce66010fa0dc9974a066de43d57c6220f7820b3d4fb4 +size 23204 diff --git a/marked/Rel-16/25_series/25212/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Rel-16/25_series/25212/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecff0b26ea3b62ae729327f7c69b8a621ae0e621 --- /dev/null +++ b/marked/Rel-16/25_series/25212/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e807accd00af1b220fa6af7ae884e3da91f3d85ada258bc8ef53a80946a3329f +size 30434 diff --git a/marked/Rel-16/25_series/25212/b11b654648249b38a82129a35555b481_img.jpg b/marked/Rel-16/25_series/25212/b11b654648249b38a82129a35555b481_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af7fe713110c385cf518b4143759807208e5f47 --- /dev/null +++ b/marked/Rel-16/25_series/25212/b11b654648249b38a82129a35555b481_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f45808e972e1eb5b5a6529afe810185b37f768adae03633e816fc836fc39468 +size 51949 diff --git a/marked/Rel-16/25_series/25212/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/25_series/25212/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..833beeb5ecf901fc5ae30fa698190d2aa2c1335c --- /dev/null +++ b/marked/Rel-16/25_series/25212/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d30c3631617f784a65bdec37591951409e873027e097a326d1be6a474d7b138 +size 56410 diff --git a/marked/Rel-16/25_series/25212/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-16/25_series/25212/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6914cadc97cd9a6b03bc2010dd939eb54a03e9e --- /dev/null +++ b/marked/Rel-16/25_series/25212/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31bef7edbc334eb6962e0595013ab1329267f28ba83999f14638276d16adba4e +size 20621 diff --git a/marked/Rel-16/25_series/25212/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/25_series/25212/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a5bafef8c7fe50990b9d9844b0c89653cbe8c8 --- /dev/null +++ b/marked/Rel-16/25_series/25212/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74b12572d809dbbd44deb8676faf2149e16586c9cc47109e8f6f1b28839f2c16 +size 27453 diff --git a/marked/Rel-16/25_series/25212/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/marked/Rel-16/25_series/25212/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c035ac6bca179deb8ecad75bec19c4c3bf7cc83c --- /dev/null +++ b/marked/Rel-16/25_series/25212/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a295d3af18c73ad7493faccd36dae507cf3cd40b29a3226a9ffd29b0bff35c5a +size 37280 diff --git a/marked/Rel-16/25_series/25212/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg b/marked/Rel-16/25_series/25212/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6b160c92be3187502b5261c5de1a68e1ae6aea5 --- /dev/null +++ b/marked/Rel-16/25_series/25212/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:848a3c1b4f6badcbf41bf473f534865c7730a65775d5269700b4379b68103544 +size 106609 diff --git a/marked/Rel-16/25_series/25212/c2e2b17d61aecbead88a6278e4ba3605_img.jpg b/marked/Rel-16/25_series/25212/c2e2b17d61aecbead88a6278e4ba3605_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a920770e4ea28f14ad2f2bfe33bb22d7812bae61 --- /dev/null +++ b/marked/Rel-16/25_series/25212/c2e2b17d61aecbead88a6278e4ba3605_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:839133b4f1a3d7b25178bcb01c9edf9d6bd9f4285122951a0c5ef7d63453b28c +size 45220 diff --git a/marked/Rel-16/25_series/25212/ceb9a4217df4b6e301712b3b88b09c69_img.jpg b/marked/Rel-16/25_series/25212/ceb9a4217df4b6e301712b3b88b09c69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c9679554e4d30bcf2cfdb70f0080e63cbb12016 --- /dev/null +++ b/marked/Rel-16/25_series/25212/ceb9a4217df4b6e301712b3b88b09c69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c40669f77b1dc5be441d5d46636f089711a5f32575024515d40a89cc47e22c77 +size 17424 diff --git a/marked/Rel-16/25_series/25212/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/25_series/25212/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26ddcae93e587289b0633d7d6b7af1e631f1fdf4 --- /dev/null +++ b/marked/Rel-16/25_series/25212/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fb391caf51aecb47efac17cfe8a05304ab64f257a2cfc86b1d1e0a4009f5a0f +size 29273 diff --git a/marked/Rel-16/25_series/25212/d8bc70513c482a0b8bb6d99e43de623e_img.jpg b/marked/Rel-16/25_series/25212/d8bc70513c482a0b8bb6d99e43de623e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8909d9ed99e3ca8e2133f0321c2b7826c32a8ac1 --- /dev/null +++ b/marked/Rel-16/25_series/25212/d8bc70513c482a0b8bb6d99e43de623e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cce25906f5caf86c7286fd74e38499d4fadb5ff2427c3fa776987973e1c9e634 +size 24762 diff --git a/marked/Rel-16/25_series/25212/db7cb51aac8519daab50e2171cecae82_img.jpg b/marked/Rel-16/25_series/25212/db7cb51aac8519daab50e2171cecae82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0637e8c4f0403079fb77a8d7741c71bb4dd626b8 --- /dev/null +++ b/marked/Rel-16/25_series/25212/db7cb51aac8519daab50e2171cecae82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82fd89624927049189cdef1a22d9a88bf34fafccd5d17c0dd74648c1681b8197 +size 83362 diff --git a/marked/Rel-16/25_series/25212/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/25_series/25212/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8527508acc5a8d1673dac602abc3cb538564fdc6 --- /dev/null +++ b/marked/Rel-16/25_series/25212/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08e191e6cd3160c075f00d8a27cdbba1603fd686d304895e667de0723facd391 +size 32068 diff --git a/marked/Rel-16/25_series/25212/e20792fef9de6560b2d6c5441da7614a_img.jpg b/marked/Rel-16/25_series/25212/e20792fef9de6560b2d6c5441da7614a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e2e265c149ee6da593c9113196bf36cd5594529 --- /dev/null +++ b/marked/Rel-16/25_series/25212/e20792fef9de6560b2d6c5441da7614a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:173b0f05aa4c75517c5360e09fffd6c887e57e8be35196c951eef7e562392075 +size 31131 diff --git a/marked/Rel-16/25_series/25212/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/marked/Rel-16/25_series/25212/f1ba1e68228ebd4c3109371574a723e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aeca86dc5e0eaea99fda904014702ed8515a7b4 --- /dev/null +++ b/marked/Rel-16/25_series/25212/f1ba1e68228ebd4c3109371574a723e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a08a0b4a56cb9bcd3212e18a15579dd7bae2c367e5c5b24d1f1af9c5be68c381 +size 32519 diff --git a/marked/Rel-16/25_series/25212/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-16/25_series/25212/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a78e99a9c21bc6afe6babd67c329b3226e5dcd3f --- /dev/null +++ b/marked/Rel-16/25_series/25212/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb53a1500ccd4006ef694e421f662d2471ebb0734711f1b257e74669e0596e54 +size 56561 diff --git a/marked/Rel-16/25_series/25212/raw.md b/marked/Rel-16/25_series/25212/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d91e4ce26275e41b9bf7f7c6faa5aa17769b35a3 --- /dev/null +++ b/marked/Rel-16/25_series/25212/raw.md @@ -0,0 +1,6704 @@ + + + + +Error: + +2 + +Error: Reference source not + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations..... | 13 | +| 4 Multiplexing, channel coding and interleaving..... | 14 | +| 4.1 General..... | 14 | +| 4.2 General coding/multiplexing of TrCHs..... | 14 | +| 4.2.0 Transport channel concatenation..... | 19 | +| 4.2.1 CRC attachment..... | 19 | +| 4.2.1.1 CRC Calculation..... | 19 | +| 4.2.1.2 Relation between input and output of the CRC attachment block..... | 20 | +| 4.2.2 Transport block concatenation and code block segmentation..... | 20 | +| 4.2.2.1 Concatenation of transport blocks..... | 20 | +| 4.2.2.2 Code block segmentation..... | 20 | +| 4.2.3 Channel coding..... | 21 | +| 4.2.3.1 Convolutional coding..... | 22 | +| 4.2.3.2 Turbo coding..... | 23 | +| 4.2.3.2.1 Turbo coder..... | 23 | +| 4.2.3.2.2 Trellis termination for Turbo coder..... | 23 | +| 4.2.3.2.3 Turbo code internal interleaver..... | 24 | +| 4.2.3.3 Concatenation of encoded blocks..... | 27 | +| 4.2.4 Radio frame size equalisation..... | 27 | +| 4.2.5 1 st interleaving..... | 28 | +| 4.2.5.1 Void..... | 28 | +| 4.2.5.2 1 st interleaver operation..... | 28 | +| 4.2.5.3 Relation between input and output of 1 st interleaving in uplink..... | 29 | +| 4.2.5.4 Relation between input and output of 1 st interleaving in downlink..... | 29 | +| 4.2.6 Radio frame segmentation..... | 29 | +| 4.2.6.1 Relation between input and output of the radio frame segmentation block in uplink..... | 30 | +| 4.2.6.2 Relation between input and output of the radio frame segmentation block in downlink..... | 30 | +| 4.2.7 Rate matching..... | 30 | +| 4.2.7.1 Determination of rate matching parameters in uplink..... | 32 | +| 4.2.7.1.1 Determination of SF and number of PhCHs needed..... | 32 | +| 4.2.7.2 Determination of rate matching parameters in downlink..... | 35 | +| 4.2.7.2.1 Determination of rate matching parameters for fixed positions of TrCHs..... | 35 | +| 4.2.7.2.1A Determination of rate matching parameters for pseudo-flexible positions of TrCHs..... | 37 | +| 4.2.7.2.2 Determination of rate matching parameters for flexible positions of TrCHs..... | 37 | +| 4.2.7.3 Bit separation and collection in uplink..... | 39 | +| 4.2.7.3.1 Bit separation..... | 41 | +| 4.2.7.3.2 Bit collection..... | 41 | +| 4.2.7.4 Bit separation and collection in downlink..... | 42 | +| 4.2.7.4.1 Bit separation..... | 43 | +| 4.2.7.4.2 Bit collection..... | 43 | +| 4.2.7.5 Rate matching pattern determination..... | 44 | +| 4.2.8 TrCH multiplexing..... | 45 | +| 4.2.9 Insertion of discontinuous transmission (DTX) indication bits..... | 45 | +| 4.2.9.1 1 st insertion of DTX indication bits..... | 45 | +| 4.2.9.2 2 nd insertion of DTX indication bits..... | 46 | +| 4.2.10 Physical channel segmentation..... | 47 | +| 4.2.10.1 Relation between input and output of the physical segmentation block in uplink..... | 47 | +| 4.2.10.2 Relation between input and output of the physical segmentation block in downlink..... | 47 | +| 4.2.11 2 nd interleaving..... | 47 | +| 4.2.11.1 2 nd interleaving for Secondary CCPCH with 16QAM..... | 48 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 4.2.12 | Physical channel mapping..... | 49 | +| 4.2.12.1 | Uplink..... | 49 | +| 4.2.12.1.1 | UL_DPCH_10ms_Mode is not configured by higher layers, or, no compressed-mode transmission gap overlaps with the first radio frame in the 20ms CI..... | 49 | +| 4.2.12.1.2 | UL_DPCH_10ms_Mode is configured by higher layers, and, a compressed-mode transmission gap overlaps with the first radio frame in 20ms CI..... | 49 | +| 4.2.12.2 | Downlink..... | 50 | +| 4.2.13 | Restrictions on different types of CCTrCHs..... | 50 | +| 4.2.13.1 | Uplink Dedicated channel (DCH)..... | 50 | +| 4.2.13.2 | Random Access Channel (RACH)..... | 51 | +| 4.2.13.3 | Void..... | 51 | +| 4.2.13.4 | Downlink Dedicated Channel (DCH)..... | 51 | +| 4.2.13.5 | Void..... | 51 | +| 4.2.13.6 | Broadcast channel (BCH)..... | 51 | +| 4.2.13.7 | Forward access and paging channels (FACH and PCH)..... | 51 | +| 4.2.13.8 | High Speed Downlink Shared Channel (HS-DSCH) associated with a DCH..... | 51 | +| 4.2.13.9 | Enhanced Dedicated Channel (E-DCH)..... | 52 | +| 4.2.14 | Multiplexing of different transport channels into one CCTrCH, and mapping of one CCTrCH onto physical channels..... | 52 | +| 4.2.14.1 | Allowed CCTrCH combinations for one UE..... | 53 | +| 4.2.14.1.1 | Allowed CCTrCH combinations on the uplink..... | 53 | +| 4.2.14.1.2 | Allowed CCTrCH combinations on the downlink..... | 53 | +| 4.3 | Transport format detection..... | 53 | +| 4.3.1 | Blind transport format detection..... | 54 | +| 4.3.1A | Single transport format detection..... | 54 | +| 4.3.2 | Transport format detection based on TFCI..... | 54 | +| 4.3.3 | Coding of Transport-Format-Combination Indicator (TFCI)..... | 55 | +| 4.3.4 | Void..... | 56 | +| 4.3.5 | Mapping of TFCI words..... | 56 | +| 4.3.5.1 | Mapping of TFCI word in normal mode in downlink, and in uplink when uplink DPCCH slot format is not 5..... | 56 | +| 4.3.5.1A | Mapping of TFCI word in normal mode in uplink when uplink DPCCH slot format is 5..... | 56 | +| 4.3.5.1.1 | Mapping of TFCI bits for Secondary CCPCH with 16QAM..... | 56 | +| 4.3.5.2 | Mapping of TFCI word in compressed mode..... | 56 | +| 4.3.5.2.1 | Uplink compressed mode..... | 57 | +| 4.3.5.2.2 | Downlink compressed mode..... | 57 | +| 4.3A | Mapping of DL FET ACK/NACK bits..... | 58 | +| 4.4 | Compressed mode..... | 59 | +| 4.4.1 | Frame structure in the uplink..... | 59 | +| 4.4.2 | Frame structure types in the downlink..... | 59 | +| 4.4.2A | Frame structure in the downlink for F-DPCH..... | 60 | +| 4.4.2B | Frame structure in the downlink for F-TPICH..... | 60 | +| 4.4.3 | Transmission time reduction method..... | 60 | +| 4.4.3.1 | Void..... | 60 | +| 4.4.3.2 | Compressed mode by reducing the spreading factor by 2..... | 60 | +| 4.4.3.3 | Compressed mode by higher layer scheduling..... | 60 | +| 4.4.4 | Transmission gap position..... | 61 | +| 4.4.5 | Transmission gap position for E-DCH..... | 62 | +| 4.4.5.1 | E-DPDCH Transmission Gap Position during Initial Transmissions..... | 62 | +| 4.4.5.2 | E-DPDCH Transmission Gap Position during Retransmissions..... | 63 | +| 4.4.5.3 | E-DPCCH Transmission Gap Position..... | 63 | +| 4.5 | Coding for HS-DSCH..... | 63 | +| 4.5.1 | CRC attachment for HS-DSCH..... | 64 | +| 4.5.1.1 | CRC attachment method 1 for HS-DSCH..... | 64 | +| 4.5.1.2 | CRC attachment method 2 for HS-DSCH..... | 65 | +| 4.5.1A | Bit scrambling for HS-DSCH..... | 65 | +| 4.5.2 | Code block segmentation for HS-DSCH..... | 65 | +| 4.5.3 | Channel coding for HS-DSCH..... | 66 | +| 4.5.4 | Hybrid ARQ for HS-DSCH..... | 66 | +| 4.5.4.1 | HARQ bit separation..... | 66 | +| 4.5.4.2 | HARQ First Rate Matching Stage..... | 66 | + +| | | | +|--------------|--------------------------------------------------------------------|----| +| 4.5.4.3 | HARQ Second Rate Matching Stage..... | 67 | +| 4.5.4.4 | HARQ bit collection..... | 68 | +| 4.5.5 | Physical channel segmentation for HS-DSCH..... | 68 | +| 4.5.6 | Interleaving for HS-DSCH..... | 69 | +| 4.5.7 | Constellation re-arrangement for 16 QAM and 64QAM..... | 69 | +| 4.5.8 | Physical channel mapping for HS-DSCH..... | 70 | +| 4.6 | Coding for HS-SCCH type 1..... | 70 | +| 4.6.1 | Overview..... | 70 | +| 4.6.2 | HS-SCCH information field mapping..... | 72 | +| 4.6.2.1 | Redundancy and constellation version coding..... | 72 | +| 4.6.2.2 | Modulation scheme mapping..... | 73 | +| 4.6.2.3 | Channelization code-set mapping..... | 73 | +| 4.6.2.4 | UE identity mapping..... | 74 | +| 4.6.2.5 | HARQ process identifier mapping..... | 74 | +| 4.6.2.6 | Transport block size index mapping..... | 74 | +| 4.6.3 | Multiplexing of HS-SCCH information..... | 74 | +| 4.6.4 | CRC attachment for HS-SCCH..... | 74 | +| 4.6.5 | Channel coding for HS-SCCH..... | 75 | +| 4.6.6 | Rate matching for HS-SCCH..... | 75 | +| 4.6.7 | UE specific masking for HS-SCCH..... | 75 | +| 4.6.8 | Physical channel mapping for HS-SCCH..... | 75 | +| 4.6A | Coding for HS-SCCH type 2..... | 75 | +| 4.6A.1 | Overview..... | 75 | +| 4.6A.2 | HS-SCCH Type 2 information field mapping..... | 76 | +| 4.6A.2.1 | The first transmission..... | 76 | +| 4.6A.2.2 | The second and the third transmissions..... | 77 | +| 4.6A.2.2.1 | Special Information mapping..... | 77 | +| 4.6A.2.2.1.1 | Transport-block size information mapping..... | 77 | +| 4.6A.2.2.1.2 | Pointer to the previous transmission mapping..... | 77 | +| 4.6A.2.2.1.3 | Second or third transmission mapping..... | 77 | +| 4.6A.2.2.2 | Redundancy and Constellation Version mapping..... | 78 | +| 4.6A.2.2.3 | Modulation scheme mapping..... | 78 | +| 4.6A.2.2.4 | Channelization code-set mapping..... | 78 | +| 4.6A.2.2.5 | UE identity mapping..... | 78 | +| 4.6A.3 | Multiplexing of HS-SCCH Type 2 information..... | 78 | +| 4.6A.4 | CRC attachment for HS-SCCH Type 2..... | 78 | +| 4.6A.5 | Channel coding for HS-SCCH Type 2..... | 78 | +| 4.6A.6 | Rate matching for HS-SCCH Type 2..... | 78 | +| 4.6A.7 | UE specific masking for HS-SCCH Type 2..... | 78 | +| 4.6A.8 | Physical channel mapping for HS-SCCH Type 2..... | 78 | +| 4.6B | Coding for HS-SCCH type 3..... | 79 | +| 4.6B.1 | Overview..... | 79 | +| 4.6B.2 | HS-SCCH type 3 information field mapping..... | 80 | +| 4.6B.2.1 | Redundancy and constellation version coding..... | 80 | +| 4.6B.2.2 | Modulation scheme and number of transport blocks mapping..... | 81 | +| 4.6B.2.3 | Channelization code-set mapping..... | 81 | +| 4.6B.2.4 | UE identity mapping..... | 82 | +| 4.6B.2.5 | HARQ process identifier mapping..... | 82 | +| 4.6B.2.6 | Transport block size index mapping..... | 82 | +| 4.6B.2.7 | Precoding Weight Information mapping..... | 82 | +| 4.6B.3 | Multiplexing of HS-SCCH type 3 information..... | 83 | +| 4.6B.4 | CRC attachment for HS-SCCH type 3..... | 83 | +| 4.6B.5 | Channel coding for HS-SCCH type 3..... | 84 | +| 4.6B.6 | Rate matching for HS-SCCH type 3..... | 84 | +| 4.6B.7 | UE specific masking for HS-SCCH type 3..... | 84 | +| 4.6B.8 | Physical channel mapping for HS-SCCH type 3..... | 84 | +| 4.6C | Coding for HS-SCCH orders..... | 85 | +| 4.6C.1 | Overview..... | 85 | +| 4.6C.2 | HS-SCCH Order information field mapping in the CELL_DCH state..... | 85 | +| 4.6C.2.1 | Order type mapping..... | 85 | +| 4.6C.2.2 | Order mapping..... | 85 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 4.6C.2.2.1 | Orders for activation and deactivation of DTX, DRX and HS-SCCH-less operation and for HS-DSCH serving cell change..... | 85 | +| 4.6C.2.2.2 | Orders for activation and deactivation of Secondary serving HS-DSCH cells and Secondary uplink frequency..... | 86 | +| 4.6C.2.2.3 | Orders for Switching between Uplink Closed Loop Transmit Diversity Activation states..... | 93 | +| 4.6C.2.2.4 | Orders for activating and de-activating demodulation common pilots (D-CPICH) when the UE is configured in MIMO mode with four transmit antennas..... | 93 | +| 4.6C.2.2.5 | Orders for switching the E-DCH TTI, and for start/stop a simplified HS-SCCH type 1 transmission interval..... | 94 | +| 4.6C.2.3 | UE identity mapping..... | 95 | +| 4.6C.3 | HS-SCCH order information field mapping in the CELL_FACH and CELL_PCH states..... | 95 | +| 4.6C.3.1 | Order type mapping..... | 95 | +| 4.6C.3.2 | Order mapping..... | 95 | +| 4.6C.3.2.1 | Orders for network triggered HS-DPCCH transmission..... | 95 | +| 4.6C.3.2.2 | Orders for HS-DSCH reception during CELL_FACH HS-SCCH DRX operation..... | 95 | +| 4.6D | Coding for HS-SCCH type 4..... | 95 | +| 4.6D.1 | Overview..... | 95 | +| 4.6D.2 | HS-SCCH type 4 information field mapping..... | 96 | +| 4.6D.2.1 | Redundancy and constellation version coding..... | 96 | +| 4.6D.2.2 | Modulation scheme and number of transport blocks mapping..... | 97 | +| 4.6D.2.3 | Channelization code-set mapping..... | 98 | +| 4.6D.2.4 | UE identity mapping..... | 99 | +| 4.6D.2.5 | HARQ process identifier mapping..... | 99 | +| 4.6D.2.6 | Transport block size index mapping..... | 99 | +| 4.6D.2.7 | Precoding Weight Information mapping..... | 100 | +| 4.6D.3 | Multiplexing of HS-SCCH type 4 information..... | 101 | +| 4.6D.4 | CRC attachment for HS-SCCH type 4..... | 102 | +| 4.6D.5 | Channel coding for HS-SCCH type 4..... | 102 | +| 4.6D.6 | Rate matching for HS-SCCH type 4..... | 102 | +| 4.6D.7 | UE specific masking for HS-SCCH type 4..... | 103 | +| 4.6D.8 | Physical channel mapping for HS-SCCH type 4..... | 103 | +| 4.7 | Coding for HS-DPCCH..... | 103 | +| 4.7.1 | Overview..... | 103 | +| 4.7.2 | Channel coding for HS-DPCCH when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in the serving HS-DSCH cell and Secondary_Cell_Enabled is 0 or 1 and Secondary_Cell_Active is 0..... | 108 | +| 4.7.2.1 | Channel coding for HS-DPCCH HARQ-ACK..... | 108 | +| 4.7.2.2 | Channel coding for HS-DPCCH channel quality indication..... | 108 | +| 4.7.3 | Channel coding for HS-DPCCH when the UE is configured in MIMO mode in the serving HS-DSCH cell and Secondary_Cell_Enabled is 0..... | 109 | +| 4.7.3.1 | Channel coding for HS-DPCCH HARQ-ACK..... | 109 | +| 4.7.3.2 | Channel coding for HS-DPCCH composite precoding control indication and channel quality indication..... | 110 | +| 4.7.3.2.1 | Bit mapping of Type A channel quality indication..... | 110 | +| 4.7.3.2.2 | Bit mapping of Type B channel quality indication..... | 110 | +| 4.7.3.2.3 | Bit mapping of precoding control indication..... | 110 | +| 4.7.3.2.4 | Composite precoding control indication and channel quality indication bits..... | 110 | +| 4.7.3.2.5 | Block encoding of composite precoding control indication and channel quality indication bits..... | 111 | +| 4.7.3A | Channel coding for HS-DPCCH when the UE is not configured in MIMO mode in any cell and Secondary_Cell_Enabled is 1 and Secondary_Cell_Active is 1..... | 112 | +| 4.7.3A.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 112 | +| 4.7.3A.2 | Channel coding for HS-DPCCH composite channel quality indication..... | 113 | +| 4.7.3A.2.1 | Composite channel quality indication bits..... | 113 | +| 4.7.3A.2.2 | Block encoding of composite channel quality indication bits..... | 114 | +| 4.7.3B | Channel coding for HS-DPCCH when Secondary_Cell_Enabled is at least 3 or when the UE is configured in MIMO mode in at least one cell and Secondary_Cell_Enabled is greater than 0..... | 114 | +| 4.7.3B.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 114 | +| 4.7.3B.2 | Channel coding for HS-DPCCH composite precoding control indication and channel quality indication..... | 116 | +| 4.7.3C | Channel coding for HS-DPCCH when the UE is not configured in MIMO mode in any cell and Secondary_Cell_Enabled is 2..... | 116 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 4.7.3C.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 116 | +| 4.7.3C.2 | Channel coding for HS-DPCCH channel quality indication..... | 117 | +| 4.7.3D | Channel coding for HS-DPCCH when the UE is configured in Multiflow mode..... | 117 | +| 4.7.3D.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 117 | +| 4.7.3D.2 | Channel coding for HS-DPCCH channel quality indication..... | 118 | +| 4.7.3E | Channel coding for HS-DPCCH when the UE is configured in MIMO mode with 4 transmit antennas..... | 118 | +| 4.7.3E.1 | Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas and Secondary_Cell_Enabled is 0..... | 118 | +| 4.7.3E.1.1 | Channel coding for HS-DPCCH HARQ-ACK..... | 118 | +| 4.7.3E.1.2 | Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication..... | 120 | +| 4.7.3E.2 | Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary_Cell_Enabled is 1..... | 122 | +| 4.7.3E.2.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 122 | +| 4.7.3E.2.2 | Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication..... | 123 | +| 4.7.3E.3 | Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary_Cell_Enabled is 2..... | 123 | +| 4.7.3E.3.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 123 | +| 4.7.3E.3.2 | Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication..... | 123 | +| 4.7.3E.4 | Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary_Cell_Enabled is 3..... | 123 | +| 4.7.3E.4.1 | Channel coding for the composite HS-DPCCH HARQ-ACK..... | 124 | +| 4.7.3E.4.2 | Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication..... | 124 | +| 4.7.4 | Physical channel mapping for HS-DPCCH..... | 124 | +| 4.7.4.1 | Physical Channel mapping for HS-DPCCH HARQ-ACK..... | 124 | +| 4.7.4.2 | Physical Channel mapping for HS-DPCCH PCI/CQI..... | 127 | +| 4.7.4.3 | Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured in Multiflow mode..... | 132 | +| 4.7.4.3.1 | Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with one serving and one assisting serving HS-DSCH cell..... | 132 | +| 4.7.4.3.2 | Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with two serving and one assisting serving or one serving and two assisting serving HS-DSCH cells..... | 133 | +| 4.7.4.3.3 | Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with two serving and two assisting serving HS-DSCH cells..... | 135 | +| 4.7.4.3.4 | Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with three serving and one assisting serving HS-DSCH cells or one serving and three assisting serving HS-DSCH cells..... | 135 | +| 4.7.4.4 | Physical Channel mapping for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in at least one cell..... | 137 | +| 4.7.4.4.1 | Physical Channel mapping for HS-DPCCH HARQ-ACK..... | 137 | +| 4.7.4.4.2 | Physical Channel mapping for HS-DPCCH NTBP/PCI/CQI..... | 138 | +| 4.8 | Coding for E-DCH..... | 140 | +| 4.8.1 | CRC attachment for E-DCH..... | 142 | +| 4.8.2 | Code block segmentation for E-DCH..... | 142 | +| 4.8.3 | Channel coding for E-DCH..... | 142 | +| 4.8.4 | Physical layer HARQ functionality and rate matching for E-DCH..... | 142 | +| 4.8.4.1 | Determination of SF, modulation scheme and number of E-DPDCH PhCHs needed..... | 142 | +| 4.8.4.1A | Determination of SF, modulation scheme and number of S-E-DPDCH PhCHs needed..... | 144 | +| 4.8.4.2 | HARQ bit separation..... | 145 | +| 4.8.4.3 | HARQ Rate Matching Stage..... | 145 | +| 4.8.4.4 | HARQ bit collection..... | 146 | +| 4.8.5 | Physical channel segmentation for E-DCH..... | 146 | +| 4.8.6 | Interleaving for E-DCH..... | 146 | +| 4.8.7 | Physical channel mapping for E-DCH..... | 147 | +| 4.9 | Coding for E-DPCCH..... | 147 | +| 4.9.1 | Overview..... | 148 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------|------------| +| 4.9.2 | E-DPCCH information field mapping..... | 148 | +| 4.9.2.1 | Information field mapping of E-TFCI..... | 148 | +| 4.9.2.2 | Information field mapping of retransmission sequence number..... | 148 | +| 4.9.2.3 | Information field mapping of the "Happy" bit..... | 149 | +| 4.9.3 | Multiplexing of E-DPCCH information..... | 149 | +| 4.9.4 | Channel coding for E-DPCCH..... | 149 | +| 4.9.5 | Physical channel mapping for E-DPCCH..... | 149 | +| 4.9A | Coding for S-E-DPCCH..... | 150 | +| 4.9A.1 | Overview..... | 150 | +| 4.9A.2 | S-E-DPCCH information field mapping..... | 150 | +| 4.9A.2.1 | Information field mapping of E-TFCI..... | 150 | +| 4.9A.2.2 | Information field mapping of retransmission sequence number..... | 150 | +| 4.9A.2.3 | Information field mapping of the Spare bit..... | 150 | +| 4.9A.3 | Multiplexing of S-E-DPCCH information..... | 150 | +| 4.9A.4 | Channel coding for S-E-DPCCH..... | 150 | +| 4.9A.5 | Physical channel mapping for S-E-DPCCH..... | 150 | +| 4.10 | Coding for E-AGCH..... | 150 | +| 4.10.1 | Overview..... | 150 | +| 4.10.1A | E-AGCH information field mapping..... | 151 | +| 4.10.1A.1 | Information field mapping of the Absolute Grant Value..... | 151 | +| 4.10.1A.2 | Information field mapping of the Absolute Grant Scope..... | 153 | +| 4.10.1B | Multiplexing of E-AGCH information..... | 153 | +| 4.10.2 | CRC attachment for E-AGCH..... | 154 | +| 4.10.3 | Channel coding for E-AGCH..... | 154 | +| 4.10.4 | Rate matching for E-AGCH..... | 154 | +| 4.10.5 | Physical channel mapping for E-AGCH..... | 154 | +| 4.10A | Coding for E-ROCH..... | 154 | +| 4.10A.1 | Overview..... | 154 | +| 4.10A.2 | E-ROCH information field mapping..... | 155 | +| 4.10A.2.1 | Information field mapping of the S-ETFC Offset..... | 155 | +| 4.10A.2.2 | Information field mapping of the Rank Indication..... | 156 | +| 4.10A.3 | Multiplexing of E-ROCH information..... | 156 | +| 4.10A.4 | CRC attachment for E-ROCH..... | 156 | +| 4.10A.5 | Channel coding for E-ROCH..... | 157 | +| 4.10A.6 | Rate matching for E-ROCH..... | 157 | +| 4.10A.7 | Physical channel mapping for E-ROCH..... | 157 | +| 4.11 | Mapping for E-RGCH Relative Grant..... | 157 | +| 4.11.1 | Overview..... | 157 | +| 4.11.2 | Relative Grant mapping..... | 157 | +| 4.12 | Mapping for E-HICH ACK/NACK..... | 157 | +| 4.12.1 | Overview..... | 157 | +| 4.12.2 | ACK/NACK mapping..... | 157 | +| Annex A (informative): | Blind transport format detection..... | 159 | +| A.1 | Blind transport format detection using fixed positions..... | 159 | +| A.1.1 | Blind transport format detection using received power ratio..... | 159 | +| A.1.2 | Blind transport format detection using CRC..... | 159 | +| A.2 | Blind transport format detection using pseudo-flexible positions..... | 161 | +| Annex B (informative): | Compressed mode idle lengths..... | 162 | +| B.1 | Idle lengths for DL, UL and DL+UL compressed mode for DPCH..... | 162 | +| Annex C (informative): | Change history..... | 164 | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document describes the characteristics of the Layer 1 multiplexing and channel coding in the FDD mode of UTRA. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. +- [1] 3GPP TS 25.201: "Physical layer - General Description". +- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.225: "Physical layer – Measurements (TDD)". +- [11] 3GPP TS 25.302: "Services Provided by the Physical Layer". +- [12] 3GPP TS 25.402: "Synchronization in UTRAN, Stage 2". +- [13] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". +- [14] ITU-T Recommendation X.691 (12/97) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)" +- [15] 3GPP TS 25.306: "UE Radio Access capabilities". +- [16] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". + +--- + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Assisting secondary serving HS-DSCH Cell(s):** In addition to the serving HS-DSCH cell, a cell in the secondary downlink frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. There can be up to two assisting secondary serving HS-DSCH cells. + +**Assisting serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the same frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Cell group:** A group of (one, two, or three) Multiflow mode cells that have the same CPICH timing. The cells that belong to a cell group are indicated by higher layers. + +**DL FET:** DL FET refers to early termination of DL DPCH transmission upon receiving an acknowledgement message. In this context, a DL FET ACK/NACK message represents an acknowledge message sent on UL DPCCH for DL FET. + +**DL\_DCH\_FET\_Config:** Higher layers signal this configuration parameter to indicate enhanced DCH physical layer configuration. The possible values are 0 and 1. The value 0 indicates Mode 0 configuration where DL transport channels concatenation and DL FET ACK/NACK signalling on UL are not configured. The value 1 indicates Mode 1 where DL transport channel concatenation and DL FET ACK/NACK signalling on UL are configured. + +**MIMO mode:** This term refers to the downlink MIMO configuration with two transmit antennas + +**MIMO mode with four transmit antennas:** This term refers to the downlink MIMO configuration with four transmit antennas + +**Multiflow mode:** The UE is configured in Multiflow mode when it is configured with assisting serving HS-DSCH cell. + +**Primary uplink frequency:** If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequency is configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**Secondary uplink frequency:** A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**TG:** Transmission Gap is consecutive empty slots that have been obtained with a transmission time reduction method. The transmission gap can be contained in one or two consecutive radio frames. + +**TGL:** Transmission Gap Length is the number of consecutive empty slots that have been obtained with a transmission time reduction method. $0 \leq TGL \leq 14$ . The CFNs of the radio frames containing the first empty slot of the transmission gaps, the CFNs of the radio frames containing the last empty slot, the respective positions $N_{\text{first}}$ and $N_{\text{last}}$ within these frames of the first and last empty slots of the transmission gaps, and the transmission gap lengths can be calculated with the compressed mode parameters described in [5]. + +**TrCH number:** The transport channel number identifies a TrCH in the context of L1. The L3 transport channel identity (TrCH ID) maps onto the L1 transport channel number. The mapping between the transport channel number and the TrCH ID is as follows: TrCH 1 corresponds to the TrCH with the lowest TrCH ID, TrCH 2 corresponds to the TrCH with the next lowest TrCH ID and so on. + +**UL DPCH 10ms Mode:** When configured by higher layers for the TTI to be transmitted [16], UL DPCH follows physical channel procedures specific to this mode. UL DPCH 10ms Mode can only happen when DL\_DCH\_FET\_Config is configured. + +**UL 20ms Compression Interval (CI):** A time interval of 20ms duration aligned to a 20ms TTI defined for UL DPCH physical layer procedures when DL\_DCH\_FET\_Config is configured by higher layers. + +**1st secondary serving HS-DSCH cell:** If the UE is configured with two uplink frequencies, the 1st secondary serving HS-DSCH cell is the secondary serving HS-DSCH cell that is associated with the secondary uplink frequency. If the UE is configured with a single uplink frequency, the 1st secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**2nd secondary serving HS-DSCH cell:** If the UE is configured with more than two serving HS-DSCH cells, the 2nd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**3rd secondary serving HS-DSCH cell:** If the UE is configured with more than three serving HS-DSCH cells, the 3rd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**4th secondary serving HS-DSCH cell:** If the UE is configured with more than four serving HS-DSCH cells, the 4th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**5th secondary serving HS-DSCH cell:** If the UE is configured with more than five serving HS-DSCH cells, the 5th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**6th secondary serving HS-DSCH cell:** If the UE is configured with more than six serving HS-DSCH cells, the 6th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**7th secondary serving HS-DSCH cell:** If the UE is configured with eight serving HS-DSCH cells, the 7th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------|---------------------------------------------------------------------------------------------------| +| $\lceil x \rceil$ | round towards $\infty$ , i.e. integer such that $x \leq \lceil x \rceil < x+1$ | +| $\lfloor x \rfloor$ | round towards $-\infty$ , i.e. integer such that $x-1 < \lfloor x \rfloor \leq x$ | +| $ x $ | absolute value of $x$ | +| $\text{sgn}(x)$ | signum function, i.e. $\text{sgn}(x) = \begin{cases} 1; & x \geq 0 \\ -1; & x < 0 \end{cases}$ | +| $N_{\text{first}}$ | The first slot in the TG, located in the first compressed radio frame if the TG spans two frames. | +| $N_{\text{last}}$ | The last slot in the TG, located in the second compressed radio frame if the TG spans two frames. | +| $N_{\text{tr}}$ | Number of transmitted slots in a radio frame. | + +Unless otherwise is explicitly stated when the symbol is used, the meaning of the following symbols is: + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $A$ | List of transport channels numbers $i_1, i_2, \dots, i_B$ , corresponding to downlink transport channels to be concatenated when DL_DCH_FET_Config = 1. | +| $i$ | TrCH number | +| $j$ | TFC number | +| $k$ | Bit number | +| $l$ | TF number | +| $m$ | Transport block number | +| $n_i$ | Radio frame number of TrCH $i$ . | +| $p$ | PhCH number | +| $r$ | Code block number | +| $I$ | Number of TrCHs in a CCTrCH. | +| $C_i$ | Number of code blocks in one TTI of TrCH $i$ . | +| $F_i$ | Number of radio frames in one TTI of TrCH $i$ , except for uplink when UL_DPCH_10ms_Mode is configured. In uplink, when UL_DPCH_10ms_Mode is configured, $F_i$ is the number of radio frames in the transmission time interval of TrCH $i$ divided by 2. | +| $M_i$ | Number of transport blocks in one TTI of TrCH $i$ . | +| $N_{\text{data},j}$ | Number of data bits that are available for the CCTrCH in a radio frame with TFC $j$ . | +| $N_{\text{data},j}^{\text{cm}}$ | Number of data bits that are available for the CCTrCH in a compressed radio frame with TFC $j$ . | +| $P$ | Number of PhCHs used for one CCTrCH. | +| $PL$ | Puncturing Limit for the uplink. Signalled from higher layers | +| $RM_i$ | Rate Matching attribute for TrCH $i$ . Signalled from higher layers, or determined as specified in clause 4.2.0. | + +Temporary variables, i.e. variables used in several (sub)clauses with different meaning. + +$x, X$ + $y, Y$ + $z, Z$ + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|--------------------------| +| ARQ | Automatic Repeat Request | +| BCH | Broadcast Channel | +| BER | Bit Error Rate | +| BLER | Block Error Rate | + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------| +| BS | Base Station | +| CCPCH | Common Control Physical Channel | +| CCTrCH | Coded Composite Transport Channel | +| CFN | Connection Frame Number | +| CLTD | Closed Loop Transmit Diversity | +| CRC | Cyclic Redundancy Check | +| DCH | Dedicated Channel | +| DL | Downlink (Forward link) | +| DPCCH | Dedicated Physical Control Channel | +| DPCCH2 | Dedicated Physical Control Channel 2 | +| DPCH | Dedicated Physical Channel | +| DPDCH | Dedicated Physical Data Channel | +| DS-CDMA | Direct-Sequence Code Division Multiple Access | +| DTX | Discontinuous Transmission | +| FACH | Forward Access Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced Dedicated Channel | +| E-DPCCH | E-DCH Dedicated Physical Control Channel | +| E-DPDCH | E-DCH Dedicated Physical Data Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-RGCH | E-DCH Relative Grant Channel | +| E-RNTI | E-DCH Radio Network Temporary Identifier | +| E-ROCH | E-DCH Rank and Offset Channel | +| FDD | Frequency Division Duplex | +| F-DPCH | Fractional Dedicated Physical Channel | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| FER | Frame Error Rate | +| GF | Galois Field | +| HARQ | Hybrid Automatic Repeat reQuest | +| HS-DPCCH | Dedicated Physical Control Channel (uplink) for HS-DSCH | +| HS-DPCCH 2 | Secondary Dedicated Physical Control Channel (uplink) for HS-DSCH, when Secondary_Cell_Enabled is greater than 3 | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Channel for HS-DSCH | +| MAC | Medium Access Control | +| MBSFN | MBMS over a Single Frequency Network | +| Mcps | Mega Chip Per Second | +| MIMO | Multiple Input Multiple Output | +| MS | Mobile Station | +| OVSF | Orthogonal Variable Spreading Factor (codes) | +| PCCC | Parallel Concatenated Convolutional Code | +| PCH | Paging Channel | +| PhCH | Physical Channel | +| PRACH | Physical Random Access Channel | +| RACH | Random Access Channel | +| RSC | Recursive Systematic Convolutional Coder | +| RV | Redundancy Version | +| RX | Receive | +| SCH | Synchronization Channel | +| SF | Spreading Factor | +| SFN | System Frame Number | +| SIR | Signal-to-Interference Ratio | +| SNR | Signal to Noise Ratio | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| S-E-DPCCH | Secondary Dedicated Physical Control Channel for E-DCH | +| S-E-DPDCH | Secondary Dedicated Physical Data Channel for E-DCH | +| S-E-RNTI | Secondary E-RNTI | +| TF | Transport Format | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | + +| | | +|------|---------------------------------| +| TPC | Transmit Power Control | +| TPI | Transmitted Precoding Indicator | +| TrCH | Transport Channel | +| TTI | Transmission Time Interval | +| TX | Transmit | +| UL | Uplink (Reverse link) | + +--- + +## 4 Multiplexing, channel coding and interleaving + +### 4.1 General + +Data stream from/to MAC and higher layers (Transport block / Transport block set) is encoded/decoded to offer transport services over the radio transmission link. Channel coding scheme is a combination of error detection, error correcting, rate matching, interleaving and transport channels mapping onto/splitting from physical channels. + +### 4.2 General coding/multiplexing of TrCHs + +This section only applies to the transport channels: DCH, RACH, BCH, FACH and PCH. Other transport channels which do not use the general method are described separately below. + +Data arrives to the coding/multiplexing unit in form of transport block sets once every transmission time interval. The transmission time interval is transport-channel specific from the set {10 ms, 20 ms, 40 ms, 80 ms}, where 80 ms TTI for DCH shall not be used unless SF=512. + +The following coding/multiplexing steps can be identified: + +- add CRC to each transport block (see subclause 4.2.1); +- transport block concatenation and code block segmentation (see subclause 4.2.2); +- channel coding (see subclause 4.2.3); +- radio frame equalisation (see subclause 4.2.4); +- rate matching (see subclause 4.2.7); +- insertion of discontinuous transmission (DTX) indication bits (see subclause 4.2.9); +- interleaving (two steps, see subclauses 4.2.5 and 4.2.11); +- radio frame segmentation (see subclause 4.2.6); +- multiplexing of transport channels (see subclause 4.2.8); +- physical channel segmentation (see subclause 4.2.10); +- mapping to physical channels (see subclause 4.2.12). + +The coding/multiplexing steps for uplink and downlink are shown in figure 1 and figure 2 respectively. + +![Flowchart of transport channel multiplexing structure for uplink. It shows a sequence of processing blocks: CRC attachment, Turbo concatenation / Code block segmentation, Channel coding, Data flow equalization, 1st interleaving, Data flow segmentation, and Rate matching. These are followed by a 'Data splitting' block. The next stage is 'Turbo Multiplexing', which includes a 'CRC' block. This is followed by 'Physical channel segmentation', '1st interleaving', and 'Physical channel mapping'. The final output consists of multiple parallel streams labeled 'Physical channel'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +graph TD + subgraph TC [Transport Channel] + direction TB + T1[CRC attachment] --> T2[Turbo concatenation / Code block segmentation] + T2 --> T3[Channel coding] + T3 --> T4[Data flow equalization] + T4 --> T5[1st interleaving] + T5 --> T6[Data flow segmentation] + T6 --> T7[Rate matching] + end + T7 --> DS[Data splitting] + DS --> TM[Turbo Multiplexing] + subgraph PC [Physical Channel] + direction TB + TM --> P1[Physical channel segmentation] + P1 --> P2[1st interleaving] + P2 --> P3[Physical channel mapping] + end + P3 --> Out1[Physical channel] + P3 --> Out2[Physical channel] + P3 --> Out3[Physical channel] + P3 --> Out4[Physical channel] + P3 --> Out5[Physical channel] + P3 --> Out6[Physical channel] + P3 --> Out7[Physical channel] + P3 --> Out8[Physical channel] + P3 --> Out9[Physical channel] + P3 --> Out10[Physical channel] + P3 --> Out11[Physical channel] + P3 --> Out12[Physical channel] + P3 --> Out13[Physical channel] + P3 --> Out14[Physical channel] + P3 --> Out15[Physical channel] + P3 --> Out16[Physical channel] + P3 --> Out17[Physical channel] + P3 --> Out18[Physical channel] + P3 --> Out19[Physical channel] + P3 --> Out20[Physical channel] + P3 --> Out21[Physical channel] + P3 --> Out22[Physical channel] + P3 --> Out23[Physical channel] + P3 --> Out24[Physical channel] + P3 --> Out25[Physical channel] + P3 --> Out26[Physical channel] + P3 --> Out27[Physical channel] + P3 --> Out28[Physical channel] + P3 --> Out29[Physical channel] + P3 --> Out30[Physical channel] + P3 --> Out31[Physical channel] + P3 --> Out32[Physical channel] + P3 --> Out33[Physical channel] + P3 --> Out34[Physical channel] + P3 --> Out35[Physical channel] + P3 --> Out36[Physical channel] + P3 --> Out37[Physical channel] + P3 --> Out38[Physical channel] + P3 --> Out39[Physical channel] + P3 --> Out40[Physical channel] + P3 --> Out41[Physical channel] + P3 --> Out42[Physical channel] + P3 --> Out43[Physical channel] + P3 --> Out44[Physical channel] + P3 --> Out45[Physical channel] + P3 --> Out46[Physical channel] + P3 --> Out47[Physical channel] + P3 --> Out48[Physical channel] + P3 --> Out49[Physical channel] + P3 --> Out50[Physical channel] + P3 --> Out51[Physical channel] + P3 --> Out52[Physical channel] + P3 --> Out53[Physical channel] + P3 --> Out54[Physical channel] + P3 --> Out55[Physical channel] + P3 --> Out56[Physical channel] + P3 --> Out57[Physical channel] + P3 --> Out58[Physical channel] + P3 --> Out59[Physical channel] + P3 --> Out60[Physical channel] + P3 --> Out61[Physical channel] + P3 --> Out62[Physical channel] + P3 --> Out63[Physical channel] + P3 --> Out64[Physical channel] + P3 --> Out65[Physical channel] + P3 --> Out66[Physical channel] + P3 --> Out67[Physical channel] + P3 --> Out68[Physical channel] + P3 --> Out69[Physical channel] + P3 --> Out70[Physical channel] + P3 --> Out71[Physical channel] + P3 --> Out72[Physical channel] + P3 --> Out73[Physical channel] + P3 --> Out74[Physical channel] + P3 --> Out75[Physical channel] + P3 --> Out76[Physical channel] + P3 --> Out77[Physical channel] + P3 --> Out78[Physical channel] + P3 --> Out79[Physical channel] + P3 --> Out80[Physical channel] + P3 --> Out81[Physical channel] + P3 --> Out82[Physical channel] + P3 --> Out83[Physical channel] + P3 --> Out84[Physical channel] + P3 --> Out85[Physical channel] + P3 --> Out86[Physical channel] + P3 --> Out87[Physical channel] + P3 --> Out88[Physical channel] + P3 --> Out89[Physical channel] + P3 --> Out90[Physical channel] + P3 --> Out91[Physical channel] + P3 --> Out92[Physical channel] + P3 --> Out93[Physical channel] + P3 --> Out94[Physical channel] + P3 --> Out95[Physical channel] + P3 --> Out96[Physical channel] + P3 --> Out97[Physical channel] + P3 --> Out98[Physical channel] + P3 --> Out99[Physical channel] + P3 --> Out100[Physical channel] + +``` + +Flowchart of transport channel multiplexing structure for uplink. It shows a sequence of processing blocks: CRC attachment, Turbo concatenation / Code block segmentation, Channel coding, Data flow equalization, 1st interleaving, Data flow segmentation, and Rate matching. These are followed by a 'Data splitting' block. The next stage is 'Turbo Multiplexing', which includes a 'CRC' block. This is followed by 'Physical channel segmentation', '1st interleaving', and 'Physical channel mapping'. The final output consists of multiple parallel streams labeled 'Physical channel'. + +Figure 1: Transport channel multiplexing structure for uplink + +![Flowchart of downlink transport channel multiplexing structure. The process starts with multiple transport channels entering a dashed box. Inside, they pass through CRC attachment, CRC concatenation / cyclic block repetition, channel coding, rate matching, 1st interleaving of TTI information, 1st interleaving, and data frame segmentation. Outside the box, the data goes through TTI multiplexing, 1st interleaving of TTI information, physical channel segmentation, 2nd interleaving, and physical channel mapping. Vertical ellipses on the left indicate multiple parallel transport channels. Horizontal ellipses indicate additional steps or channels in the process.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Flowchart of downlink transport channel multiplexing structure. The process starts with multiple transport channels entering a dashed box. Inside, they pass through CRC attachment, CRC concatenation / cyclic block repetition, channel coding, rate matching, 1st interleaving of TTI information, 1st interleaving, and data frame segmentation. Outside the box, the data goes through TTI multiplexing, 1st interleaving of TTI information, physical channel segmentation, 2nd interleaving, and physical channel mapping. Vertical ellipses on the left indicate multiple parallel transport channels. Horizontal ellipses indicate additional steps or channels in the process. + +Figure 2: Downlink transport channel multiplexing structure for transport channels that are not concatenated. + + + +![Flowchart of downlink transport channel processing for concatenated transport channels. The process starts with multiple transport channels (i1, i2, ..., iB) being concatenated, followed by CRC attachment, code block segmentation, channel coding, rate matching, DTX indication insertion, interleaving, and radio frame segmentation. The output is then multiplexed with other transport channels and processed through a second DTX indication insertion, physical channel segmentation, second interleaving, and physical channel mapping to produce the final physical channels (PICH#1, PICH#2).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the downlink transport channel processing flow for concatenated transport channels. It begins with three transport channels, $i_1 \in A$ , $i_2 \in A$ , and $i_B \in A$ , each containing data blocks $a_{i_1 m1}, a_{i_1 m2}, \dots, a_{i_1 m_{A_{i_1}}}$ , $a_{i_2 m1}, a_{i_2 m2}, \dots, a_{i_2 m_{A_{i_2}}}$ , and $a_{i_B m1}, a_{i_B m2}, \dots, a_{i_B m_{A_{i_B}}}$ respectively. These are input to a 'TrCh Concatenation' block. + +The output of 'TrCh Concatenation' is a 'Concatenated Transport Channel' containing data blocks $a_{i_{DM}1}, a_{i_{DM}2}, a_{i_{DM}3}, \dots, a_{i_{DM}A_{i_{DM}}}$ . This channel undergoes a series of processing steps: 'CRC attachment' resulting in $b_{i_{DM}1}, b_{i_{DM}2}, b_{i_{DM}3}, \dots, b_{i_{DM}B_{i_{DM}}}$ ; 'TrBk concatenation / Code block segmentation' resulting in $o_{i_{DM}1}, o_{i_{DM}2}, o_{i_{DM}3}, \dots, o_{i_{DM}K_{i_{DM}}}$ ; 'Channel coding' resulting in $c_{i_{DM}1}, c_{i_{DM}2}, c_{i_{DM}3}, \dots, c_{i_{DM}E_{i_{DM}}}$ ; 'Rate matching' resulting in $g_{i_{DM}1}, g_{i_{DM}2}, g_{i_{DM}3}, \dots, g_{i_{DM}G_{i_{DM}}}$ ; '1st insertion of DTX indication' resulting in $r_{i_{DM}1}, r_{i_{DM}2}, r_{i_{DM}3}, \dots, r_{i_{DM}D_{i_{DM}}}$ ; '1st interleaving' resulting in $q_{i_{DM}1}, q_{i_{DM}2}, q_{i_{DM}3}, \dots, q_{i_{DM}Q_{i_{DM}}}$ ; and 'Radio frame segmentation' resulting in $f_{i_{DM}1}, f_{i_{DM}2}, f_{i_{DM}3}, \dots, f_{i_{DM}F_{i_{DM}}}$ . + +Simultaneously, 'Other Transport Channels' are processed through their own 'Rate matching' block. The segmented data from the concatenated channel and the rate-matched data from other channels are combined in a 'TrCH Multiplexing' block, producing $s_1, s_2, s_3, \dots, s_S$ . + +This multiplexed data then undergoes '2nd insertion of DTX indication' resulting in $w_1, w_2, w_3, \dots, w_R$ , which are labeled as 'CCTrCH'. This is followed by 'Physical channel segmentation' resulting in $u_{p1}, u_{p2}, u_{p3}, \dots, u_{pU}$ ; '2nd interleaving' resulting in $v_{p1}, v_{p2}, v_{p3}, \dots, v_{pU}$ ; and 'Physical channel mapping' which finally produces the physical channels 'PICH#1' and 'PICH#2'. + +Flowchart of downlink transport channel processing for concatenated transport channels. The process starts with multiple transport channels (i1, i2, ..., iB) being concatenated, followed by CRC attachment, code block segmentation, channel coding, rate matching, DTX indication insertion, interleaving, and radio frame segmentation. The output is then multiplexed with other transport channels and processed through a second DTX indication insertion, physical channel segmentation, second interleaving, and physical channel mapping to produce the final physical channels (PICH#1, PICH#2). + +Figure 2A: Downlink transport channel processing for transport channels that are concatenated. The concatenated transport channel inherits the parameters of the transport channel $i_1$ . + +The single output data stream from the TrCH multiplexing, including DTX indication bits in downlink, is denoted *Coded Composite Transport Channel (CCTrCH)*. A CCTrCH can be mapped to one or several physical channels. + +#### 4.2.0 Transport channel concatenation + +When DL\_DCH\_FET\_Config is configured with value 1, downlink transport blocks of transport channels with a transport channel number $i_t \in \Lambda$ are concatenated to form a concatenated transport channel. In this case, higher layers ensure that TTI values of transport channels that are concatenated are the same. + +Let $i_1, i_2, i_3, \dots, i_B$ denote in ascending order the transport channel numbers in $\Lambda$ , $i_1 < i_2 < i_3 < \dots < i_B$ . The concatenated transport channel is treated as a regular transport channel in layer 1, inheriting the parameters of transport channel number $i_t$ , e.g., the transport channel number, and the rate matching attribute of the concatenated transport channel are $i_t$ and $RM_{i_t}$ respectively. All transport blocks of all the transport channels to be concatenated are serially concatenated into a single transport block, in ascending order. The bits input to the transport channel concatenation are denoted by + +$w_{i_k m 1}, w_{i_k m 2}, w_{i_k m 3}, \dots, w_{i_k m B_{i_k}}$ for $i_k \in \Lambda$ , and $m = 1, \dots, M_{i_k}$ , where $i_k$ denotes the TrCH number, $m$ denotes the transport block number for the transport channel $i_k$ , and $B_{i_k}$ is the number of bits in each transport block of transport channel $i_k$ . + +The bits after transport channel concatenation are denoted by $a_1, a_2, a_3, \dots, a_A$ , where $A = \sum_{i_k \in \Lambda} B_{i_k} \times M_{i_k}$ denotes the total number of bits in the single transport block of the concatenated transport channel. + +The $a_1, a_2, a_3, \dots, a_A$ bits are defined by the following set of relations: + +$$a_{1+\sum_{k=1}^{t-1} M_{i_k} B_{i_k} + (m-1) B_{i_t}}, a_{2+\sum_{k=1}^{t-1} M_{i_k} B_{i_k} + (m-1) B_{i_t}}, \dots, a_{B_{i_t} + \sum_{k=1}^{t-1} M_{i_k} B_{i_k} + (m-1) B_{i_t}} = w_{i_t m 1}, w_{i_t m 2}, w_{i_t m 3}, \dots, w_{i_t m B_{i_t}},$$ + +for $m = 1, \dots, M_{i_t}$ , and $i_t \in \Lambda$ . + +#### 4.2.1 CRC attachment + +Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC). The size of the CRC is 24, 16, 12, 8 or 0 bits and it is signalled from higher layers what CRC size that should be used for each TrCH. + +##### 4.2.1.1 CRC Calculation + +The entire transport block is used to calculate the CRC parity bits for each transport block. The parity bits are generated by one of the following cyclic generator polynomials: + +- $g_{CRC24}(D) = D^{24} + D^{23} + D^6 + D^5 + D + 1$ ; +- $g_{CRC16}(D) = D^{16} + D^{12} + D^5 + 1$ ; +- $g_{CRC12}(D) = D^{12} + D^{11} + D^3 + D^2 + D + 1$ ; +- $g_{CRC8}(D) = D^8 + D^7 + D^4 + D^3 + D + 1$ . + +Denote the bits in a transport block delivered to layer 1 by $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA_i}$ , and the parity bits by + +$p_{im1}, p_{im2}, p_{im3}, \dots, p_{imL_i}$ . $A_i$ is the size of a transport block of TrCH $i$ , $m$ is the transport block number, and $L_i$ is the number of parity bits. $L_i$ can take the values 24, 16, 12, 8, or 0 depending on what is signalled from higher layers, except for a concatenated transport channel (Subclause 4.2.0) where the number of parity bits is always 16. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial: + +$$a_{im1} D^{A_i+23} + a_{im2} D^{A_i+22} + \dots + a_{imA_i} D^{24} + p_{im1} D^{23} + p_{im2} D^{22} + \dots + p_{im23} D^1 + p_{im24}$$ + +yields a remainder equal to 0 when divided by $g_{CRC24}(D)$ , polynomial: + +$$a_{im1} D^{A_i+15} + a_{im2} D^{A_i+14} + \dots + a_{imA_i} D^{16} + p_{im1} D^{15} + p_{im2} D^{14} + \dots + p_{im15} D^1 + p_{im16}$$ + +yields a remainder equal to 0 when divided by $g_{CRC16}(D)$ , polynomial: + +$$a_{im1}D^{A_i+11} + a_{im2}D^{A_i+10} + \dots + a_{imA_i}D^{12} + p_{im1}D^{11} + p_{im2}D^{10} + \dots + p_{im11}D^1 + p_{im12}$$ + +yields a remainder equal to 0 when divided by $g_{CRC12}(D)$ and polynomial: + +$$a_{im1}D^{A_i+7} + a_{im2}D^{A_i+6} + \dots + a_{imA_i}D^8 + p_{im1}D^7 + p_{im2}D^6 + \dots + p_{im7}D^1 + p_{im8}$$ + +yields a remainder equal to 0 when divided by $g_{CRC8}(D)$ . + +If no transport blocks are input to the CRC calculation ( $M_i = 0$ ), no CRC attachment shall be done. If transport blocks are input to the CRC calculation ( $M_i \neq 0$ ) and the size of a transport block is zero ( $A_i = 0$ ), CRC shall be attached, i.e. all parity bits equal to zero. + +#### 4.2.1.2 Relation between input and output of the CRC attachment block + +The bits after CRC attachment are denoted by $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ , where $B_i = A_i + L_i$ . The relation between $a_{imk}$ and $b_{imk}$ is: + +$$b_{imk} = a_{imk} \quad k = 1, 2, 3, \dots, A_i$$ + +$$b_{imk} = p_{im(L_i+1-(k-A_i))} \quad k = A_i + 1, A_i + 2, A_i + 3, \dots, A_i + L_i$$ + +#### 4.2.2 Transport block concatenation and code block segmentation + +All transport blocks in a TTI are serially concatenated. If the number of bits in a TTI is larger than $Z$ , the maximum size of a code block in question, then code block segmentation is performed after the concatenation of the transport blocks. The maximum size of the code blocks depends on whether convolutional coding or turbo coding is used for the TrCH. + +##### 4.2.2.1 Concatenation of transport blocks + +The bits input to the transport block concatenation are denoted by $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ where $i$ is the TrCH number, $m$ is the transport block number, and $B_i$ is the number of bits in each block (including CRC). The number of transport blocks on TrCH $i$ is denoted by $M_i$ . The bits after concatenation are denoted by $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ , where $i$ is the TrCH number and $X_i = M_i B_i$ . They are defined by the following relations: + +$$x_{ik} = b_{i1k} \quad k = 1, 2, \dots, B_i$$ + +$$x_{ik} = b_{i2,(k-B_i)} \quad k = B_i + 1, B_i + 2, \dots, 2B_i$$ + +$$x_{ik} = b_{i3,(k-2B_i)} \quad k = 2B_i + 1, 2B_i + 2, \dots, 3B_i$$ + +... + +$$x_{ik} = b_{iM_i,(k-(M_i-1)B_i)} \quad k = (M_i - 1)B_i + 1, (M_i - 1)B_i + 2, \dots, M_i B_i$$ + +##### 4.2.2.2 Code block segmentation + +Segmentation of the bit sequence from transport block concatenation is performed if $X_i > Z$ . The code blocks after segmentation are of the same size. The number of code blocks on TrCH $i$ is denoted by $C_i$ . If the number of bits input to the segmentation, $X_i$ , is not a multiple of $C_i$ , filler bits are added to the beginning of the first block. If turbo coding is selected and $X_i < 40$ , filler bits are added to the beginning of the code block. The filler bits are transmitted and they are always set to 0. The maximum code block sizes are: + +- convolutional coding: $Z = 504$ ; + +- turbo coding: $Z = 5114$ . + +The bits output from code block segmentation, for $C_i \neq 0$ , are denoted by $O_{ir1}, O_{ir2}, O_{ir3}, \dots, O_{irK_i}$ , where $i$ is the TrCH number, $r$ is the code block number, and $K_i$ is the number of bits per code block. + +Number of code blocks: + +$$C_i = \lceil X_i / Z \rceil$$ + +Number of bits in each code block (applicable for $C_i \neq 0$ only): + +if $X_i < 40$ and Turbo coding is used, then + +$$K_i = 40$$ + +else + +$$K_i = \lceil X_i / C_i \rceil$$ + +end if + +Number of filler bits: $Y_i = C_i K_i - X_i$ + +for $k = 1$ to $Y_i$ -- Insertion of filler bits + +$$o_{ilk} = 0$$ + +end for + +for $k = Y_i + 1$ to $K_i$ + +$$o_{ilk} = x_{i, (k - Y_i)}$$ + +end for + +$r = 2$ -- Segmentation + +while $r \leq C_i$ + +for $k = 1$ to $K_i$ + +$$o_{irk} = x_{i, (k + (r-1)K_i - Y_i)}$$ + +end for + +$$r = r + 1$$ + +end while + +### 4.2.3 Channel coding + +Code blocks are delivered to the channel coding block. They are denoted by $O_{ir1}, O_{ir2}, O_{ir3}, \dots, O_{irK_i}$ , where $i$ is the TrCH number, $r$ is the code block number, and $K_i$ is the number of bits in each code block. The number of code blocks on TrCH $i$ is denoted by $C_i$ . After encoding the bits are denoted by $Y_{ir1}, Y_{ir2}, Y_{ir3}, \dots, Y_{irY_i}$ , where $Y_i$ is the number of encoded bits. The relation between $O_{irk}$ and $Y_{irk}$ and between $K_i$ and $Y_i$ is dependent on the channel coding scheme. + +The following channel coding schemes can be applied to TrCHs: + +- convolutional coding; +- turbo coding. + +Usage of coding scheme and coding rate for the different types of TrCH is shown in table 1. + +The values of $Y_i$ in connection with each coding scheme: + +- convolutional coding with rate 1/2: $Y_i = 2 * K_i + 16$ ; rate 1/3: $Y_i = 3 * K_i + 24$ ; +- turbo coding with rate 1/3: $Y_i = 3 * K_i + 12$ . + +**Table 1: Usage of channel coding scheme and coding rate** + +| Type of TrCH | Coding scheme | Coding rate | +|--------------|----------------------|-------------| +| BCH | Convolutional coding | 1/2 | +| PCH | | | +| RACH | | | +| DCH, FACH | Turbo coding* | 1/3, 1/2 | +| | | 1/3 | + +\* For DCH, turbo coding is not allowed when DL\_DCH\_FET\_Config is configured by higher layers. + +#### 4.2.3.1 Convolutional coding + +Convolutional codes with constraint length 9 and coding rates 1/3 and 1/2 are defined. + +The configuration of the convolutional coder is presented in figure 3. + +Output from the rate 1/3 convolutional coder shall be done in the order output0, output1, output2, output0, output1, output2, output0, ..., output2. Output from the rate 1/2 convolutional coder shall be done in the order output 0, output 1, output 0, output 1, output 0, ..., output 1. + +8 tail bits with binary value 0 shall be added to the end of the code block before encoding. + +The initial value of the shift register of the coder shall be "all 0" when starting to encode the input bits. + +![Figure 3: Rate 1/2 and rate 1/3 convolutional coders. (a) Rate 1/2 convolutional coder: Input enters a chain of 8 delay elements (D). Taps from each delay element are combined via XOR gates to produce Output 0 (G0 = 561 octal) and Output 1 (G1 = 753 octal). (b) Rate 1/3 convolutional coder: Input enters a chain of 8 delay elements (D). Taps from each delay element are combined via XOR gates to produce Output 0 (G0 = 557 octal), Output 1 (G1 = 663 octal), and Output 2 (G2 = 711 octal).](db7cb51aac8519daab50e2171cecae82_img.jpg) + +(a) Rate 1/2 convolutional coder + +(b) Rate 1/3 convolutional coder + +Figure 3: Rate 1/2 and rate 1/3 convolutional coders. (a) Rate 1/2 convolutional coder: Input enters a chain of 8 delay elements (D). Taps from each delay element are combined via XOR gates to produce Output 0 (G0 = 561 octal) and Output 1 (G1 = 753 octal). (b) Rate 1/3 convolutional coder: Input enters a chain of 8 delay elements (D). Taps from each delay element are combined via XOR gates to produce Output 0 (G0 = 557 octal), Output 1 (G1 = 663 octal), and Output 2 (G2 = 711 octal). + +**Figure 3: Rate 1/2 and rate 1/3 convolutional coders** + +#### 4.2.3.2 Turbo coding + +##### 4.2.3.2.1 Turbo coder + +The scheme of Turbo coder is a Parallel Concatenated Convolutional Code (PCCC) with two 8-state constituent encoders and one Turbo code internal interleaver. The coding rate of Turbo coder is 1/3. The structure of Turbo coder is illustrated in figure 4. + +The transfer function of the 8-state constituent code for PCCC is: + +$$G(D) = \begin{bmatrix} 1, & \frac{g_1(D)}{g_0(D)} \end{bmatrix},$$ + +where + +$$g_0(D) = 1 + D^2 + D^3,$$ + +$$g_1(D) = 1 + D + D^3.$$ + +The initial value of the shift registers of the 8-state constituent encoders shall be all zeros when starting to encode the input bits. + +Output from the Turbo coder is + +$$x_1, z_1, z'_1, x_2, z_2, z'_2, \dots, x_K, z_K, z'_K,$$ + +where $x_1, x_2, \dots, x_K$ are the bits input to the Turbo coder i.e. both first 8-state constituent encoder and Turbo code internal interleaver, and $K$ is the number of bits, and $z_1, z_2, \dots, z_K$ and $z'_1, z'_2, \dots, z'_K$ are the bits output from first and second 8-state constituent encoders, respectively. + +The bits output from Turbo code internal interleaver are denoted by $x'_1, x'_2, \dots, x'_K$ , and these bits are to be input to the second 8-state constituent encoder. + +![Figure 4: Structure of rate 1/3 Turbo coder. The diagram shows an input bit stream entering a switch. One path goes to the '1st constituent encoder' which produces output z_k. The other path goes to an 'Input Turbo code internal interleaver Output' block, which produces x'_k. Both x'_k and the original input x_k enter the '2nd constituent encoder', which produces output z'_k. The final output is a combination of x_k, z_k, and z'_k. Dotted lines represent trellis termination paths for the encoders.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +Figure 4: Structure of rate 1/3 Turbo coder. The diagram shows an input bit stream entering a switch. One path goes to the '1st constituent encoder' which produces output z\_k. The other path goes to an 'Input Turbo code internal interleaver Output' block, which produces x'\_k. Both x'\_k and the original input x\_k enter the '2nd constituent encoder', which produces output z'\_k. The final output is a combination of x\_k, z\_k, and z'\_k. Dotted lines represent trellis termination paths for the encoders. + +Figure 4: Structure of rate 1/3 Turbo coder (dotted lines apply for trellis termination only) + +#### 4.2.3.2.2 Trellis termination for Turbo coder + +Trellis termination is performed by taking the tail bits from the shift register feedback after all information bits are encoded. Tail bits are padded after the encoding of information bits. + +The first three tail bits shall be used to terminate the first constituent encoder (upper switch of figure 4 in lower position) while the second constituent encoder is disabled. The last three tail bits shall be used to terminate the second constituent encoder (lower switch of figure 4 in lower position) while the first constituent encoder is disabled. + +The transmitted bits for trellis termination shall then be: + +$$x_{K+1}, z_{K+1}, x_{K+2}, z_{K+2}, x_{K+3}, z_{K+3}, x'_{K+1}, z'_{K+1}, x'_{K+2}, z'_{K+2}, x'_{K+3}, z'_{K+3}.$$ + +#### 4.2.3.2.3 Turbo code internal interleaver + +The Turbo code internal interleaver consists of bits-input to a rectangular matrix with padding, intra-row and inter-row permutations of the rectangular matrix, and bits-output from the rectangular matrix with pruning. The bits input to the Turbo code internal interleaver are denoted by $x_1, x_2, x_3, \dots, x_K$ , where $K$ is the integer number of the bits and takes one value of $40 \leq K \leq 5114$ . The relation between the bits input to the Turbo code internal interleaver and the bits input to the channel coding is defined by $x_k = o_{irk}$ and $K = K_i$ . + +The following subclause specific symbols are used in subclauses 4.2.3.2.3.1 to 4.2.3.2.3.3: + +$K$ Number of bits input to Turbo code internal interleaver + +$R$ Number of rows of rectangular matrix + +$C$ Number of columns of rectangular matrix + +$p$ Prime number + +$v$ Primitive root + +$\langle s(j) \rangle_{j \in \{0, 1, \dots, p-2\}}$ Base sequence for intra-row permutation + +$q_i$ Minimum prime integers + +$r_i$ Permuted prime integers + +$\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ Inter-row permutation pattern + +$\langle U_i(j) \rangle_{j \in \{0, 1, \dots, C-1\}}$ Intra-row permutation pattern of $i$ -th row + +$i$ Index of row number of rectangular matrix + +$j$ Index of column number of rectangular matrix + +$k$ Index of bit sequence + +##### 4.2.3.2.3.1 Bits-input to rectangular matrix with padding + +The bit sequence $x_1, x_2, x_3, \dots, x_K$ input to the Turbo code internal interleaver is written into the rectangular matrix as follows. + +(1) Determine the number of rows of the rectangular matrix, $R$ , such that: + +$$R = \begin{cases} 5, \text{ if } (40 \leq K \leq 159) \\ 10, \text{ if } ((160 \leq K \leq 200) \text{ or } (481 \leq K \leq 530)) \\ 20, \text{ if } (K = \text{any other value}) \end{cases}$$ + +The rows of rectangular matrix are numbered 0, 1, ..., $R - 1$ from top to bottom. + +(2) Determine the prime number to be used in the intra-permutation, $p$ , and the number of columns of rectangular matrix, $C$ , such that: + +if $(481 \leq K \leq 530)$ then + +$$p = 53 \text{ and } C = p.$$ + +else + +Find minimum prime number $p$ from table 2 such that + +$$K \leq R \times (p+1),$$ + +and determine $C$ such that + +$$C = \begin{cases} p-1 & \text{if } K \leq R \times (p-1) \\ p & \text{if } R \times (p-1) < K \leq R \times p \\ p+1 & \text{if } R \times p < K \end{cases}.$$ + +end if + +The columns of rectangular matrix are numbered 0, 1, ..., $C-1$ from left to right. + +**Table 2: List of prime number $p$ and associated primitive root $v$** + +| $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 7 | 3 | 47 | 5 | 101 | 2 | 157 | 5 | 223 | 3 | +| 11 | 2 | 53 | 2 | 103 | 5 | 163 | 2 | 227 | 2 | +| 13 | 2 | 59 | 2 | 107 | 2 | 167 | 5 | 229 | 6 | +| 17 | 3 | 61 | 2 | 109 | 6 | 173 | 2 | 233 | 3 | +| 19 | 2 | 67 | 2 | 113 | 3 | 179 | 2 | 239 | 7 | +| 23 | 5 | 71 | 7 | 127 | 3 | 181 | 2 | 241 | 7 | +| 29 | 2 | 73 | 5 | 131 | 2 | 191 | 19 | 251 | 6 | +| 31 | 3 | 79 | 3 | 137 | 3 | 193 | 5 | 257 | 3 | +| 37 | 2 | 83 | 2 | 139 | 2 | 197 | 2 | | | +| 41 | 6 | 89 | 3 | 149 | 2 | 199 | 3 | | | +| 43 | 3 | 97 | 5 | 151 | 6 | 211 | 2 | | | + +- (3) Write the input bit sequence $x_1, x_2, x_3, \dots, x_K$ into the $R \times C$ rectangular matrix row by row starting with bit $y_1$ in column 0 of row 0: + +$$\begin{bmatrix} y_1 & y_2 & y_3 & \dots & y_C \\ y_{(C+1)} & y_{(C+2)} & y_{(C+3)} & \dots & y_{2C} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{((R-1)C+1)} & y_{((R-1)C+2)} & y_{((R-1)C+3)} & \dots & y_{R \times C} \end{bmatrix}$$ + +where $y_k = x_k$ for $k = 1, 2, \dots, K$ and if $R \times C > K$ , the dummy bits are padded such that $y_k = 0$ or $1$ for $k = K+1, K+2, \dots, R \times C$ . These dummy bits are pruned away from the output of the rectangular matrix after intra-row and inter-row permutations. + +#### 4.2.3.2.3.2 Intra-row and inter-row permutations + +After the bits-input to the $R \times C$ rectangular matrix, the intra-row and inter-row permutations for the $R \times C$ rectangular matrix are performed stepwise by using the following algorithm with steps (1) – (6): + +- (1) Select a primitive root $v$ from table 2 in clause 4.2.3.2.3.1, which is indicated on the right side of the prime number $p$ . + +- (2) Construct the base sequence $\langle s(j) \rangle_{j \in \{0, 1, \dots, p-2\}}$ for intra-row permutation as: + +$$s(j) = (v \times s(j-1)) \bmod p, \quad j = 1, 2, \dots, (p-2), \text{ and } s(0) = 1.$$ + +- (3) Assign $q_0 = 1$ to be the first prime integer in the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ , and determine the prime integer $q_i$ in the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ to be a least prime integer such that $\text{g.c.d}(q_i, p-1) = 1$ , $q_i > 6$ , and $q_i > q_{(i-1)}$ for each $i = 1, 2, \dots, R-1$ . Here $\text{g.c.d.}$ is greatest common divisor. + +(4) Permute the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ to make the sequence $\langle r_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ such that + +$$r_{T(i)} = q_i, \quad i = 0, 1, \dots, R-1,$$ + +where $\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ is the inter-row permutation pattern defined as the one of the four kind of patterns, which are shown in table 3, depending on the number of input bits $K$ . + +**Table 3: Inter-row permutation patterns for Turbo code internal interleaver** + +| Number of input bits
$K$ | Number of rows
$R$ | Inter-row permutation patterns
$\langle T(0), T(1), \dots, T(R-1) \rangle$ | +|--------------------------------------------------------|-----------------------|----------------------------------------------------------------------------------------| +| $(40 \leq K \leq 159)$ | 5 | $\langle 4, 3, 2, 1, 0 \rangle$ | +| $(160 \leq K \leq 200)$ or $(481 \leq K \leq 530)$ | 10 | $\langle 9, 8, 7, 6, 5, 4, 3, 2, 1, 0 \rangle$ | +| $(2281 \leq K \leq 2480)$ or $(3161 \leq K \leq 3210)$ | 20 | $\langle 19, 9, 14, 4, 0, 2, 5, 7, 12, 18, 16, 13, 17, 15, 3, 1, 6, 11, 8, 10 \rangle$ | +| $K = \text{any other value}$ | 20 | $\langle 19, 9, 14, 4, 0, 2, 5, 7, 12, 18, 10, 8, 13, 17, 3, 1, 16, 6, 15, 11 \rangle$ | + +(5) Perform the $i$ -th ( $i = 0, 1, \dots, R-1$ ) intra-row permutation as: + +if ( $C = p$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p-1)), \quad j = 0, 1, \dots, (p-2), \text{ and } U_i(p-1) = 0,$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row. + +end if + +if ( $C = p+1$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p-1)), \quad j = 0, 1, \dots, (p-2). \quad U_i(p-1) = 0, \text{ and } U_i(p) = p,$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row, and + +if ( $K = R \times C$ ) then + +Exchange $U_{R-1}(p)$ with $U_{R-1}(0)$ . + +end if + +end if + +if ( $C = p-1$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p-1)) - 1, \quad j = 0, 1, \dots, (p-2),$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row. + +end if + +(6) Perform the inter-row permutation for the rectangular matrix based on the pattern $\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ , + +where $T(i)$ is the original row position of the $i$ -th permuted row. + +#### 4.2.3.2.3.3 Bits-output from rectangular matrix with pruning + +After intra-row and inter-row permutations, the bits of the permuted rectangular matrix are denoted by $y'_k$ : + +$$\begin{bmatrix} y'^1_1 & y'^1_{(R+1)} & y'^1_{(2R+1)} & \dots & y'^1_{((C-1)R+1)} \\ y'^2_1 & y'^2_{(R+2)} & y'^2_{(2R+2)} & \dots & y'^2_{((C-1)R+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y'^R_1 & y'^R_{2R} & y'^R_{3R} & \dots & y'^R_{C \times R} \end{bmatrix}$$ + +The output of the Turbo code internal interleaver is the bit sequence read out column by column from the intra-row and inter-row permuted $R \times C$ rectangular matrix starting with bit $y'^1_1$ in row 0 of column 0 and ending with bit $y'^R_{CR}$ in row $R - 1$ of column $C - 1$ . The output is pruned by deleting dummy bits that were padded to the input of the rectangular matrix before intra-row and inter row permutations, i.e. bits $y'^k_j$ that corresponds to bits $y_k$ with $k > K$ are removed from the output. The bits output from Turbo code internal interleaver are denoted by $x'^1_1, x'^2_2, \dots, x'^K_K$ , where $x'^1_1$ corresponds to the bit $y'^k_j$ with smallest index $k$ after pruning, $x'^2_2$ to the bit $y'^k_j$ with second smallest index $k$ after pruning, and so on. The number of bits output from Turbo code internal interleaver is $K$ and the total number of pruned bits is: + +$$R \times C - K.$$ + +#### 4.2.3.3 Concatenation of encoded blocks + +After the channel coding for each code block, if $C_i$ is greater than 1, the encoded blocks are serially concatenated so that the block with lowest index $r$ is output first from the channel coding block, otherwise the encoded block is output from channel coding block as it is. The bits output are denoted by $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ , where $i$ is the TrCH number and $E_i = C_i Y_i$ . The output bits are defined by the following relations: + +$$c_{ik} = y_{i1k} \quad k = 1, 2, \dots, Y_i$$ + +$$c_{ik} = y_{i2, (k-Y_i)} \quad k = Y_i + 1, Y_i + 2, \dots, 2Y_i$$ + +$$c_{ik} = y_{i3, (k-2Y_i)} \quad k = 2Y_i + 1, 2Y_i + 2, \dots, 3Y_i$$ + +... + +$$c_{ik} = y_{iC_i, (k-(C_i-1)Y_i)} \quad k = (C_i - 1)Y_i + 1, (C_i - 1)Y_i + 2, \dots, C_i Y_i$$ + +If no code blocks are input to the channel coding ( $C_i = 0$ ), no bits shall be output from the channel coding, i.e. $E_i = 0$ . + +#### 4.2.4 Radio frame size equalisation + +Radio frame size equalisation is padding the input bit sequence in order to ensure that the output can be segmented in $F_i$ data segments of same size as described in subclause 4.2.7. Radio frame size equalisation is only performed in the UL. + +The input bit sequence to the radio frame size equalisation is denoted by $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ , where $i$ is TrCH number and $E_i$ the number of bits. The output bit sequence is denoted by $t_{i1}, t_{i2}, t_{i3}, \dots, t_{iT_i}$ , where $T_i$ is the number of bits. The output bit sequence is derived as follows: + +- $t_{ik} = c_{ik}$ , for $k = 1 \dots E_i$ ; and +- $t_{ik} = \{0, 1\}$ for $k = E_i + 1 \dots T_i$ if $E_i < T_i$ ; + +where + +- $T_i = F_i * N_i$ ; and +- $N_i = \lceil E_i / F_i \rceil$ is the number of bits per segment after size equalisation. + +## 4.2.5 1st interleaving + +### 4.2.5.1 Void + +### 4.2.5.2 1st interleaver operation + +The 1st interleaving is a block interleaver with inter-column permutations. The input bit sequence to the block + +interleaver is denoted by $x_{i,1}, x_{i,2}, x_{i,3}, \dots, x_{i,X_i}$ , where $i$ is TrCH number and $X_i$ the number of bits. Here $X_i$ is guaranteed to be an integer multiple of $F_i$ . The output bit sequence from the block interleaver is derived as follows: + +- (1) Select the number of columns $C1$ from Table 4 or 4A depending on the TTI. The columns are numbered 0, 1, ..., $C1 - 1$ from left to right. Table 4A is used in uplink when UL\_DPCH\_10ms\_Mode is configured by higher layers, and Table 4 is used in all other cases. + +- (2) Determine the number of rows of the matrix, $R1$ defined as + +$$R1 = X_i / C1.$$ + +The rows of the matrix are numbered 0, 1, ..., $R1 - 1$ from top to bottom. + +- (3) Write the input bit sequence into the $R1 \times C1$ matrix row by row starting with bit $x_{i,1}$ in column 0 of row 0 and ending with bit $x_{i,(R1 \times C1)}$ in column $C1 - 1$ of row $R1 - 1$ : + +$$\begin{bmatrix} x_{i,1} & x_{i,2} & x_{i,3} & \dots & x_{i,C1} \\ x_{i,(C1+1)} & x_{i,(C1+2)} & x_{i,(C1+3)} & \dots & x_{i,(2 \times C1)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ x_{i,((R1-1) \times C1+1)} & x_{i,((R1-1) \times C1+2)} & x_{i,((R1-1) \times C1+3)} & \dots & x_{i,(R1 \times C1)} \end{bmatrix}$$ + +- (4) Perform the inter-column permutation for the matrix based on the pattern $\langle P1_{C1}(j) \rangle_{j \in \{0,1,\dots,C1-1\}}$ shown in table 4, where $P1_{C1}(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y_{ik}$ : + +$$\begin{bmatrix} y_{i,1} & y_{i,(R1+1)} & y_{i,(2 \times R1+1)} & \dots & y_{i,((C1-1) \times R1+1)} \\ y_{i,2} & y_{i,(R1+2)} & y_{i,(2 \times R1+2)} & \dots & y_{i,((C1-1) \times R1+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{i,R1} & y_{i,(2 \times R1)} & y_{i,(3 \times R1)} & \dots & y_{i,(C1 \times R1)} \end{bmatrix}$$ + +- (5) Read the output bit sequence $y_{i,1}, y_{i,2}, y_{i,3}, \dots, y_{i,(C1 \times R1)}$ of the block interleaver column by column from the inter-column permuted $R1 \times C1$ matrix. Bit $y_{i,1}$ corresponds to row 0 of column 0 and bit $y_{i,(R1 \times C1)}$ corresponds to row $R1 - 1$ of column $C1 - 1$ . + +**Table 4: Inter-column permutation patterns for 1st interleaving for downlink, and for uplink when UL\_DPCH\_10ms\_Mode is not configured by higher layers** + +| TTI | Number of columns C1 | Inter-column permutation patterns
$\langle P1_{C1}(0), P1_{C1}(1), \dots, P1_{C1}(C1-1) \rangle$ | +|-------|----------------------|-----------------------------------------------------------------------------------------------------| +| 10 ms | 1 | $\langle 0 \rangle$ | +| 20 ms | 2 | $\langle 0, 1 \rangle$ | +| 40 ms | 4 | $\langle 0, 2, 1, 3 \rangle$ | +| 80 ms | 8 | $\langle 0, 4, 2, 6, 1, 5, 3, 7 \rangle$ | + +**Table 4A: Inter-column permutation patterns for 1st interleaving for uplink when UL\_DPCH\_10ms\_Mode is configured by higher layers** + +| TTI | Number of columns C1 | Inter-column permutation patterns
c1 (0), P1 c1 (1), ..., P1 c1 (C1-1)> | +|-------|----------------------|-----------------------------------------------------------------------------------------------------------------| +| 20 ms | 1 | <0> | +| 40 ms | 2 | <0,1> | +| 80 ms | 4 | <0,2,1,3> | + +#### 4.2.5.3 Relation between input and output of 1st interleaving in uplink + +The bits input to the 1st interleaving are denoted by $t_{i,1}, t_{i,2}, t_{i,3}, \dots, t_{i,T_i}$ , where $i$ is the TrCH number and $T_i$ the number of bits. Hence, $x_{i,k} = t_{i,k}$ and $X_i = T_i$ . + +The bits output from the 1st interleaving are denoted by $d_{i,1}, d_{i,2}, d_{i,3}, \dots, d_{i,T_i}$ , and $d_{i,k} = y_{i,k}$ . + +#### 4.2.5.4 Relation between input and output of 1st interleaving in downlink + +If fixed positions of the TrCHs in a radio frame is used then the bits input to the 1st interleaving are denoted by $h_{i1}, h_{i2}, h_{i3}, \dots, h_{iD_i}$ , where $i$ is the TrCH number. Hence, $x_{i,k} = h_{i,k}$ and $X_i = D_i$ . + +If flexible positions of the TrCHs in a radio frame is used then the bits input to the 1st interleaving are denoted by $g_{i1}, g_{i2}, g_{i3}, \dots, g_{iG_i}$ , where $i$ is the TrCH number. Hence, $x_{i,k} = g_{i,k}$ and $X_i = G_i$ . + +The bits output from the 1st interleaving are denoted by $q_{i1}, q_{i2}, q_{i3}, \dots, q_{iQ_i}$ , where $i$ is the TrCH number and $Q_i$ is the number of bits. Hence, $q_{i,k} = y_{i,k}$ , $Q_i = F_i H_i$ if fixed positions are used, and $Q_i = G_i$ if flexible positions are used. $H_i$ is defined in subclause 4.2.9.1. + +### 4.2.6 Radio frame segmentation + +When the transmission time interval is longer than 10 ms, the input bit sequence is segmented and mapped onto $F_i$ segments. Following rate matching in the DL and radio frame size equalisation in the UL the input bit sequence length is guaranteed to be an integer multiple of $F_i$ . + +The input bit sequence is denoted by $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ where $i$ is the TrCH number and $X_i$ is the number bits. The $F_i$ output bit sequences per TTI are denoted by $y_{i,n_1}, y_{i,n_2}, y_{i,n_3}, \dots, y_{i,n_{Y_i}}$ where $n_i$ is the segment number and $Y_i$ is the number of bits per radio frame for TrCH $i$ . The output sequences are defined as follows: + +$$y_{i,n_k} = x_{i,((n_i-1)Y_i)+k}, \quad n_i = 1 \dots F_i, \quad k = 1 \dots Y_i$$ + +where + +$Y_i = (X_i / F_i)$ is the number of bits per segment. + +In downlink, the $n_i$ -th segment is mapped to the radio frame $n_i - 1$ of the transmission time interval. + +In uplink when UL\_DPCH\_10ms\_Mode is not configured by higher layers, the $n_i$ -th segment, $1 \leq n_i \leq F_i$ is mapped to radio frame $n_i - 1$ of the transmission time interval. + +In uplink when UL\_DPCH\_10ms\_Mode is configured by higher layers, the $n_i$ -th segment, $1 \leq n_i \leq F_i$ , is mapped to the radio frame $2n_i - 2$ of the transmission time interval. No bits are input to the radio frame $2n_i - 1$ . + +#### 4.2.6.1 Relation between input and output of the radio frame segmentation block in uplink + +The input bit sequence to the radio frame segmentation is denoted by $d_{i1}, d_{i2}, d_{i3}, \dots, d_{iT_i}$ , where $i$ is the TrCH number and $T_i$ the number of bits. Hence, $x_{ik} = d_{ik}$ and $X_i = T_i$ . + +The output bit sequence corresponding to radio frame $n_i$ is denoted by $e_{i1}, e_{i2}, e_{i3}, \dots, e_{iN_i}$ , where $i$ is the TrCH number and $N_i$ is the number of bits. Hence, $e_{i,k} = y_{i,n,k}$ and $N_i = Y_i$ . + +#### 4.2.6.2 Relation between input and output of the radio frame segmentation block in downlink + +The bits input to the radio frame segmentation are denoted by $q_{i1}, q_{i2}, q_{i3}, \dots, q_{iQ_i}$ , where $i$ is the TrCH number and $Q_i$ the number of bits. Hence, $x_{ik} = q_{ik}$ and $X_i = Q_i$ . + +The output bit sequence corresponding to radio frame $n_i$ is denoted by $f_{i1}, f_{i2}, f_{i3}, \dots, f_{iV_i}$ , where $i$ is the TrCH number and $V_i$ is the number of bits. Hence, $f_{i,k} = y_{i,n,k}$ and $V_i = Y_i$ . + +### 4.2.7 Rate matching + +Rate matching means that bits on a transport channel are repeated or punctured. Higher layers assign a rate-matching attribute for each transport channel. This attribute is semi-static and can only be changed through higher layer signalling. The rate-matching attribute is used when the number of bits to be repeated or punctured is calculated. + +The number of bits on a transport channel can vary between different transmission time intervals. In the downlink the transmission is interrupted if the number of bits is lower than maximum. When the number of bits between different transmission time intervals in uplink is changed, bits are repeated or punctured to ensure that the total bit rate after TrCH multiplexing is identical to the total channel bit rate of the allocated dedicated physical channels. + +If no bits are input to the rate matching for all TrCHs within a CCTrCH, the rate matching shall output no bits for all TrCHs within the CCTrCH and no uplink DPDCH will be selected in the case of uplink rate matching. + +#### Notation used in subclause 4.2.7 and subclauses: + +$N_{ij}$ : For uplink: Number of bits in a radio frame before rate matching on TrCH $i$ with transport format combination $j$ . When UL\_DPCH\_10ms Mode is configured by higher layers, the derivation of $N_{ij}$ is described in detail in subclauses 4.2.6 and 4.2.6.1. + +For downlink: An intermediate calculation variable (not an integer but a multiple of 1/8). + +$N_{i,l}^{TTI}$ : Number of bits in a transmission time interval before rate matching on TrCH $i$ with transport format $l$ . Used in downlink only. + +$\Delta N_{i,j}$ : For uplink: If positive - number of bits that should be repeated in each radio frame on TrCH $i$ with transport format combination $j$ . + +If negative - number of bits that should be punctured in each radio frame on TrCH $i$ with transport format combination $j$ . + +For downlink : An intermediate calculation variable (not an integer but a multiple of 1/8). + +$\Delta N_{i,l}^{TTI}$ : If positive - number of bits to be repeated in each transmission time interval on TrCH $i$ with transport format $l$ . + +If negative - number of bits to be punctured in each transmission time interval on TrCH $i$ with transport format $l$ . + +- Used in downlink only. +- $N_{TGL}$ : Positive or null: number of bits in the radio frame corresponding to the gap for compressed mode for the CCTrCH. +- $RM_i$ : Semi-static rate matching attribute for transport channel $i$ . $RM_i$ is provided by higher layers or takes a value as indicated in subclause 4.2.13 or subclause 4.2.0. +- $PL$ : Puncturing limit for uplink. This value limits the amount of puncturing that can be applied in order to avoid multicode or to enable the use of a higher spreading factor. Signalled from higher layers. The allowed puncturing in % is actually equal to $(1-PL)*100$ . +- $N_{data,j}$ : Total number of bits that are available for the CCTrCH in a radio frame with transport format combination $j$ . +- $I$ : Number of TrCHs in the CCTrCH. +- $Z_{ij}$ : Intermediate calculation variable. +- $F_i$ : Number of radio frames in the transmission time interval of TrCH $i$ , except for uplink when UL\_DPCH\_10ms\_Mode is configured. In uplink, when UL\_DPCH\_10ms\_Mode is configured, $F_i$ is the number of radio frames in the transmission time interval of TrCH $i$ divided by 2. +- $n_i$ : Radio frame number in the transmission time interval of TrCH $i$ . In downlink, and in uplink when UL\_DPCH\_10ms\_Mode is not configured by higher layers, $0 \leq n_i < F_i$ . In uplink when UL\_DPCH\_10ms\_Mode is configured by higher layers, $0 \leq n_i < 2F_i$ . +- $q$ : Average puncturing or repetition distance (normalised to only show the remaining rate matching on top of an integer number of repetitions). Used in uplink only. +- $P1_F(n_i)$ : The column permutation function of the 1st interleaver, $P1_F(x)$ is the original position of column with number $x$ after permutation. $P1$ is defined on table 4 of clause 4.2.5.2 (note that the $P1_F$ is self-inverse). Used for rate matching in uplink only. +- $S[n]$ : The shift of the puncturing or repetition pattern for radio frame $n_i$ when $n = P1_F(n_i)$ . Used in uplink only. +- $TF(i)$ : Transport format of TrCH $i$ for the transport format combination $j$ . +- $TFS(i)$ : The set of transport format indexes $l$ for TrCH $i$ . +- $TFCS$ : The set of transport format combination indexes $j$ . +- $e_{ini}$ : Initial value of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.5. +- $e_{plus}$ : Increment of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.5. +- $e_{minus}$ : Decrement of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.5. +- $b$ : Indicates systematic and parity bits +- $b=1$ : Systematic bit. $x_k$ in subclause 4.2.3.2.1. +- $b=2$ : 1st parity bit (from the upper Turbo constituent encoder). $z_k$ in subclause 4.2.3.2.1. +- $b=3$ : 2nd parity bit (from the lower Turbo constituent encoder). $z'_k$ in subclause 4.2.3.2.1. + +The \* (star) notation is used to replace an index $x$ when the indexed variable $X_x$ does not depend on the index $x$ . In the left wing of an assignment the meaning is that " $X_* = Y$ " is equivalent to "for all $x$ do $X_x = Y$ ". In the right wing of an assignment, the meaning is that " $Y = X_*$ " is equivalent to "take any $x$ and do $Y = X_x$ ". + +The following relations, defined for all TFC $j$ , are used when calculating the rate matching parameters: + +$$Z_{0,j} = 0$$ + +$$Z_{i,j} = \left[ \frac{\left( \sum_{m=1}^i RM_m \times N_{m,j} \right) \times N_{data,j}}{\sum_{m=1}^I RM_m \times N_{m,j}} \right] \text{ for all } i = 1 \dots I \quad (1)$$ + +$$\Delta N_{i,j} = Z_{i,j} - Z_{i-1,j} - N_{i,j} \text{ for all } i = 1 \dots I$$ + +#### 4.2.7.1 Determination of rate matching parameters in uplink + +##### 4.2.7.1.1 Determination of SF and number of PhCHs needed + +In uplink, puncturing can be applied to match the CCTrCH bit rate to the PhCH bit rate. The bit rate of the PhCH(s) is limited by the UE capability and restrictions imposed by UTRAN, through limitations on the PhCH spreading factor. The maximum amount of puncturing that can be applied is 1-PL, PL is signalled from higher layers. The number of available bits in the radio frames of one PhCH for all possible spreading factors is given in [2]. Denote these values by $N_{256}$ , $N_{128}$ , $N_{64}$ , $N_{32}$ , $N_{16}$ , $N_8$ , and $N_4$ , where the index refers to the spreading factor. The possible number of bits available to the CCTrCH on all PhCHs, $N_{data}$ , then are $\{ N_{256}, N_{128}, N_{64}, N_{32}, N_{16}, N_8, N_4, 2 \times N_4, 3 \times N_4, 4 \times N_4, 5 \times N_4, 6 \times N_4 \}$ . + +For a RACH CCTrCH SET0 represents the set of $N_{data}$ values allowed by the UTRAN, as set by the minimum SF provided by higher layers. SET0 may be a sub-set of $\{ N_{256}, N_{128}, N_{64}, N_{32} \}$ . SET0 does not take into account the UE's capability. + +For other CCTrCHs, SET0 denotes the set of $N_{data}$ values allowed by the UTRAN and supported by the UE, as part of the UE's capability. SET0 can be a subset of $\{ N_{256}, N_{128}, N_{64}, N_{32}, N_{16}, N_8, N_4, 2 \times N_4, 3 \times N_4, 4 \times N_4, 5 \times N_4, 6 \times N_4 \}$ . When UL DPCH 10ms Mode is configured, SET0 shall include $N_{data}$ values associated with spreading factors larger than or equal to the minimum SF provided by higher layers divided by 2. $N_{data,j}$ for the transport format combination $j$ is determined by executing the following algorithm: + +$$\text{SET1} = \{ N_{data} \text{ in SET0 such that } \left( \min_{1 \leq y \leq I} \{ RM_y \} \right) \times N_{data} - \sum_{x=1}^I RM_x \times N_{x,j} \text{ is non negative} \}$$ + +If SET1 is not empty and the smallest element of SET1 requires just one PhCH then + +$$N_{data,j} = \min \text{ SET1}$$ + +else + +$$\text{SET2} = \{ N_{data} \text{ in SET0 such that } \left( \min_{1 \leq y \leq I} \{ RM_y \} \right) \times N_{data} - PL \times \sum_{x=1}^I RM_x \times N_{x,j} \text{ is non negative} \}$$ + +Sort SET2 in ascending order + +$$N_{data} = \min \text{ SET2}$$ + +While $N_{data}$ is not the max of SET2 and the follower of $N_{data}$ requires no additional PhCH do + +$$N_{data} = \text{follower of } N_{data} \text{ in SET2}$$ + +End while + +$$N_{data,j} = N_{data}$$ + +End if + +For a RACH CCTrCH, if $N_{data,j}$ is not part of the UE's capability then the TFC $j$ cannot be used. + +#### 4.2.7.1.2 Determination of parameters needed for calculating the rate matching pattern + +The number of bits to be repeated or punctured, $\Delta N_{i,j}$ , within one radio frame for each TrCH $i$ is calculated with equation 1 for all possible transport format combinations $j$ and selected every radio frame. $N_{data,j}$ is given from subclause 4.2.7.1.1. + +In a compressed radio frame when UL\_DPCH\_10ms\_Mode is not configured by higher layers, $N_{data,j}$ is replaced by $N_{data,j}^{cm}$ in Equation 1. $N_{data,j}^{cm}$ is given as follows: + +In a radio frame compressed by higher layer scheduling, $N_{data,j}^{cm}$ is obtained by executing the algorithm in subclause 4.2.7.1.1 but with the number of bits in one radio frame of one PhCH reduced to $\frac{N_{tr}}{15}$ of the value in normal mode. + +$N_{tr}$ is the number of transmitted slots in a compressed radio frame and is defined by the following relation: + +$$N_{tr} = \begin{cases} 15 - TGL, & \text{if } N_{first} + TGL \leq 15 \\ N_{first}, & \text{in first frame if } N_{first} + TGL > 15 \\ 30 - TGL - N_{first}, & \text{in second frame if } N_{first} + TGL > 15 \end{cases}$$ + +$N_{first}$ and $TGL$ are defined in subclause 4.4. + +In a radio frame compressed by spreading factor reduction, $N_{data,j}^{cm} = 2 \times (N_{data,j} - N_{TGL})$ , where + +$$N_{TGL} = \frac{15 - N_{tr}}{15} \times N_{data,j}$$ + +If $\Delta N_{i,j} = 0$ then the output data of the rate matching is the same as the input data and the rate matching algorithm of subclause 4.2.7.5 does not need to be executed. + +If $\Delta N_{i,j} \neq 0$ the parameters listed in subclauses 4.2.7.1.2.1 and 4.2.7.1.2.2 shall be used for determining $e_{ini}$ , $e_{plus}$ , and $e_{minus}$ (regardless if the radio frame is compressed or not). + +#### 4.2.7.1.2.1 Convolutionally encoded TrCHs + +$R = \Delta N_{i,j} \bmod N_{i,j}$ -- note: in this context $\Delta N_{i,j} \bmod N_{i,j}$ is in the range of 0 to $N_{i,j}-1$ i.e. $-1 \bmod 10 = 9$ . + +if $R \neq 0$ and $2 \times R \leq N_{i,j}$ + +then $q = \lceil N_{i,j} / R \rceil$ + +else + +$q = \lceil N_{i,j} / (R - N_{i,j}) \rceil$ + +endif + +-- note: $q$ is a signed quantity. + +if $q$ is even + +then $q' = q + \gcd(|q|, F_i) / F_i$ -- where $\gcd(|q|, F_i)$ means greatest common divisor of $|q|$ and $F_i$ + +-- note that $q'$ is not an integer, but a multiple of $1/8$ + +else + +$q' = q$ + +endif + +for $x = 0$ to $F_i - 1$ + +$$S[\lfloor x \times q' \rfloor \bmod F_i] = (\lfloor x \times q' \rfloor \bmod F_i)$$ + +end for + +$$\Delta N_i = \Delta N_{ij}$$ + +$$a = 2$$ + +For each radio frame, the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5, where : + +$$X_i = N_{ij}, \text{ and}$$ + +$$e_{ini} = (a \times S[PI_{Fi}(n_i)] \times |\Delta N_i| + 1) \bmod (a \cdot N_{ij}).$$ + +$$e_{plus} = a \times N_{ij}$$ + +$$e_{minus} = a \times |\Delta N_i|$$ + +puncturing for $\Delta N < 0$ , repetition otherwise. + +#### 4.2.7.1.2.2 Turbo encoded TrCHs + +If repetition is to be performed on turbo encoded TrCHs, i.e. $\Delta N_{ij} > 0$ , the parameters in subclause 4.2.7.1.2.1 are used. + +If puncturing is to be performed, the parameters below shall be used. Index $b$ is used to indicate systematic ( $b=1$ ), 1st parity ( $b=2$ ), and 2nd parity bit ( $b=3$ ). + +$$a=2 \text{ when } b=2$$ + +$$a=1 \text{ when } b=3$$ + +$$\Delta N_i = \begin{cases} \lfloor \Delta N_{i,j} / 2 \rfloor, & b = 2 \\ \lfloor \Delta N_{i,j} / 2 \rfloor, & b = 3 \end{cases}$$ + +If $\Delta N_i$ is calculated as 0 for $b=2$ or $b=3$ , then the following procedure and the rate matching algorithm of subclause 4.2.7.5 don't need to be performed for the corresponding parity bit stream. + +$$X_i = \lfloor N_{ij} / 3 \rfloor,$$ + +$$q = \lfloor X_i / |\Delta N_i| \rfloor$$ + +if( $q \leq 2$ ) + +for $r=0$ to $F_i-1$ + +$$S[(3 \times r + b - 1) \bmod F_i] = r \bmod 2;$$ + +end for + +else + +if $q$ is even + +then $q' = q - \gcd(q, F_i) / F_i$ -- where $\gcd(q, F_i)$ means greatest common divisor of $q$ and $F_i$ +-- note that $q'$ is not an integer, but a multiple of $1/8$ + +else $q' = q$ + +endif + +for $x=0$ to $F_i - 1$ + +$$r = [x \times q'] \bmod F_i;$$ + +$$S[(3 \times r + b - 1) \bmod F_i] = [x \times q'] \bmod F_i;$$ + +endfor + +endif + +For each radio frame, the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5, where: + +$X_i$ is as above: + +$$e_{ini} = (a \times S[PI_{F_i}(n_i)] \times |\Delta N_i| + X_i) \bmod (a \times X_i), \text{ if } e_{ini} = 0 \text{ then } e_{ini} = a \times X_i$$ + +$$e_{plus} = a \times X_i$$ + +$$e_{minus} = a \times |\Delta N_i|$$ + +#### 4.2.7.2 Determination of rate matching parameters in downlink + +For downlink channels, $N_{data,j}$ does not depend on the transport format combination $j$ . $N_{data,*}$ is given by the channelization code(s) assigned by higher layers. + +Denote the number of physical channels used for the CCTrCH by $P$ . $N_{data,*}$ is the number of bits available to the CCTrCH in one radio frame and defined as $N_{data,*} = P \times 15 \times (N_{data1} + N_{data2})$ , where $N_{data1}$ and $N_{data2}$ are defined in [2]. Note that contrary to the uplink, the same rate matching patterns are used in TTIs containing no compressed radio frames and in TTIs containing radio frames compressed by spreading factor reduction or higher layer scheduling. + +##### 4.2.7.2.1 Determination of rate matching parameters for fixed positions of TrCHs + +###### 4.2.7.2.1.1 Calculation of $\Delta N_{i,max}$ for normal mode and compressed mode by spreading factor reduction + +First an intermediate calculation variable $N_{i,*}$ is calculated for all transport channels $i$ by the following formula: + +$$N_{i,*} = \frac{1}{F_i} \times \left( \max_{l \in TFS(i)} N_{i,l}^{TTI} \right)$$ + +In order to compute the $\Delta N_{i,l}^{TTI}$ parameters for all TrCH $i$ and all TF $l$ , we first compute an intermediate parameter $\Delta N_{i,max}$ by the following formula, where $\Delta N_{i,*}$ is derived from $N_{i,*}$ by the formula given at subclause 4.2.7: + +$$\Delta N_{i,max} = F_i \times \Delta N_{i,*}$$ + +If $\Delta N_{i,max} = 0$ then, for TrCH $i$ , the output data of the rate matching is the same as the input data and the rate matching algorithm of subclause 4.2.7.5 does not need to be executed. In this case we have : + +$$\forall l \in TFS(i) \Delta N_{i,l}^{TTI} = 0$$ + +If $\Delta N_{i,max} \neq 0$ the parameters listed in subclauses 4.2.7.2.1.3 and 4.2.7.2.1.4 shall be used for determining $e_{ini}$ , $e_{plus}$ , and $e_{minus}$ , and $\Delta N_{i,l}^{TTI}$ . + +###### 4.2.7.2.1.2 Void + +###### 4.2.7.2.1.3 Determination of rate matching parameters for convolutionally encoded TrCHs + +$$\Delta N_i = \Delta N_{i,max}$$ + +$$a=2$$ + +$$N_{max} = \max_{l \in TFS(l)} N_{il}^{TTI}$$ + +For each transmission time interval of TrCH $i$ with TF $l$ , the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5. The following parameters are used as input: + +$$X_i = N_{il}^{TTI}$$ + +$$e_{ini} = 1$$ + +$$e_{plus} = a \times N_{max}$$ + +$$e_{minus} = a \times |\Delta N_i|$$ + +Puncturing if $\Delta N_i < 0$ , repetition otherwise. The values of $\Delta N_{i,l}^{TTI}$ may be computed by counting repetitions or puncturing when the algorithm of subclause 4.2.7.5 is run. The resulting values of $\Delta N_{i,l}^{TTI}$ can be represented with following expression. + +$$\Delta N_{i,l}^{TTI} = \left\lceil \frac{|\Delta N_i| \times X_i}{N_{max}} \right\rceil \times \text{sgn}(\Delta N_i)$$ + +#### 4.2.7.2.1.4 Determination of rate matching parameters for Turbo encoded TrCHs + +If repetition is to be performed on turbo encoded TrCHs, i.e. $\Delta N_{i,max} > 0$ , the parameters in subclause 4.2.7.2.1.3 are used. + +If puncturing is to be performed, the parameters below shall be used. Index $b$ is used to indicate systematic ( $b=1$ ), 1st parity ( $b=2$ ), and 2nd parity bit ( $b=3$ ). + +$$a=2 \text{ when } b=2$$ + +$$a=1 \text{ when } b=3$$ + +The bits indicated by $b=1$ shall not be punctured. + +$$\Delta N_i^b = \begin{cases} \lceil \Delta N_{i,max} / 2 \rceil, & \text{for } b = 2 \\ \lceil \Delta N_{i,max} / 2 \rceil, & \text{for } b = 3 \end{cases}$$ + +$$N_{max} = \max_{l \in TFS(l)} (N_{il}^{TTI} / 3)$$ + +For each transmission time interval of TrCH $i$ with TF $l$ , the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5. The following parameters are used as input: + +$$X_i = N_{il}^{TTI} / 3$$ + +$$e_{ini} = N_{max}$$ + +$$e_{plus} = a \times N_{max}$$ + +$$e_{minus} = a \times |\Delta N_i^b|$$ + +The values of $\Delta N_{i,l}^{TTI}$ may be computed by counting puncturing when the algorithm of subclause 4.2.7.5 is run. The resulting values of $\Delta N_{i,l}^{TTI}$ can be represented with following expression. + +$$\Delta N_{i,l}^{TTI} = - \left\lceil \frac{|\Delta N_i^2| \times X_i}{N_{max}} + 0.5 \right\rceil - \left\lceil \frac{|\Delta N_i^3| \times X_i}{N_{max}} \right\rceil$$ + +In the above equation, the first term of the right hand side represents the amount of puncturing for $b=2$ and the second term represents the amount of puncturing for $b=3$ . + +#### 4.2.7.2.1A Determination of rate matching parameters for pseudo-flexible positions of TrCHs + +Pseudo-flexible rate matching is identical to fixed-position rate matching, with a difference that in pseudo-flexible rate matching, rate matching parameters are re-evaluated for each maximum TTI, and the value of $RM_i$ is set to 0 in Equation (1) of subclause 4.2.7 if $M_i=0$ (i.e., no transport blocks are sent in the TTI) for each transport channel $i$ with the maximum TTI value among all the transport channels multiplexed into the CCTrCH. + +When there is a configuration with more than one transport channel having the maximum TTI and more than one of those transport channels having a transport format with no transport blocks multiplexed into a CCTrCH, the UE behaviour is unspecified. + +As a consequence of re-evaluating rate-matching parameters per maximum TTI in pseudo-flexible rate matching, derived parameters dependent on rate matching, for example the parameters corresponding to DTX indication bits in Section 4.2.9.1, can change from one maximum TTI to another in pseudo-flexible rate matching, unlike in fixed position rate matching. + +#### 4.2.7.2.2 Determination of rate matching parameters for flexible positions of TrCHs + +##### 4.2.7.2.2.1 Calculations for normal mode, compressed mode by higher layer scheduling, and compressed mode by spreading factor reduction + +First an intermediate calculation variable $N_{ij}$ is calculated for all transport channels $i$ and all transport format combinations $j$ by the following formula: + +$$N_{i,j} = \frac{1}{F_i} \times N_{i,TF_i(j)}^{TTI}$$ + +Then rate matching ratios $RF_i$ are calculated for each the transport channel $i$ in order to minimise the number of DTX bits when the bit rate of the CCTrCH is maximum. The $RF_i$ ratios are defined by the following formula: + +$$RF_i = \frac{N_{data,*}}{\max_{j \in TFCS} \sum_{i=1}^{i=l} (RM_i \times N_{i,j})} \times RM_i$$ + +The computation of $\Delta N_{i,l}^{TTI}$ parameters is then performed in two phases. In a first phase, tentative temporary values of $\Delta N_{i,l}^{TTI}$ are computed, and in the second phase they are checked and corrected. The first phase, by use of the $RF_i$ ratios, ensures that the number of DTX indication bits inserted is minimum when the CCTrCH bit rate is maximum, but it does not ensure that the maximum CCTrCH bit rate is not greater than $N_{data,*}$ per 10ms. The latter condition is ensured through the checking and possible corrections carried out in the second phase. + +At the end of the second phase, the latest value of $\Delta N_{i,l}^{TTI}$ is the definitive value. + +The first phase defines the tentative temporary $\Delta N_{i,l}^{TTT}$ for all transport channel $i$ and any of its transport format $l$ by use of the following formula: + +$$\Delta N_{i,l}^{TTT} = F_i \times \left| \frac{RF_i \times N_{i,l}^{TTT}}{F_i} \right| - N_{i,l}^{TTT} = F_i \times \left| \frac{N_{data,*} \times RM_i \times N_{i,l}^{TTT}}{F_i \times \max_{j \in TFCS} \sum_{l=1}^L (RM_i \times N_{i,j})} \right| - N_{i,l}^{TTT}$$ + +The second phase is defined by the following algorithm: + +for all $j$ in *TFCS* in ascending order of TFCI do -- for all TFC + +$$D = \sum_{i=1}^{i=I} \frac{N_{i,TF_i(j)}^{TTT} + \Delta N_{i,TF_i(j)}^{TTT}}{F_i} \quad \text{-- CCTrCH bit rate (bits per 10ms) for TFC } j$$ + +if $D > N_{data,*}$ then + +for $i = 1$ to $I$ do -- for all TrCH + +$$\Delta N = F_i \times \Delta N_{i,j} \quad \text{-- } \Delta N_{i,j} \text{ is derived from } N_{i,j} \text{ by the formula given at subclause 4.2.7.}$$ + +if $\Delta N_{i,TF_i(j)}^{TTT} > \Delta N$ then + +$$\Delta N_{i,TF_i(j)}^{TTT} = \Delta N$$ + +end-if + +end-for + +end-if + +end-for + +If $\Delta N_{i,l}^{TTT} = 0$ then, for TrCH $i$ at TF $l$ , the output data of the rate matching is the same as the input data and the rate matching algorithm of subclause 4.2.7.5 does not need to be executed. + +If $\Delta N_{i,l}^{TTT} \neq 0$ the parameters listed in subclauses 4.2.7.2.2.2 and 4.2.7.2.2.3 shall be used for determining $e_{mis}$ , $e_{plus}$ , and $e_{minus}$ . + +4.2.7.2.2.2 Determination of rate matching parameters for convolutionally encoded TrCHs + +$$\Delta N_i = \Delta N_{i,l}^{TTT}$$ + +$$a = 2$$ + +For each transmission time interval of TrCH $i$ with TF $l$ , the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5. The following parameters are used as input: + +$$X_i = N_{i,l}^{TTT}$$ + +$$e_{ini} = 1$$ + +$$e_{plus} = a \times N_{i,l}^{TTT}$$ + +$$e_{minus} = a \times |\Delta N_i|$$ + +puncturing for $\Delta N_i < 0$ , repetition otherwise. + +#### 4.2.7.2.2.3 Determination of rate matching parameters for Turbo encoded TrCHs + +If repetition is to be performed on turbo encoded TrCHs, i.e. $\Delta N_{il}^{TTT} > 0$ , the parameters in subclause 4.2.7.2.2.2 are used. + +If puncturing is to be performed, the parameters below shall be used. Index $b$ is used to indicate systematic ( $b=1$ ), 1st parity ( $b=2$ ), and 2nd parity bit ( $b=3$ ). + +$a=2$ when $b=2$ + +$a=1$ when $b=3$ + +The bits indicated by $b=1$ shall not be punctured. + +$$\Delta N_i = \begin{cases} \lfloor \Delta N_{il}^{TTT} / 2 \rfloor, & b = 2 \\ \lfloor \Delta N_{il}^{TTT} / 2 \rfloor, & b = 3 \end{cases}$$ + +For each transmission time interval of TrCH $i$ with TF $l$ , the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.5. The following parameters are used as input: + +$$X_i = N_{il}^{TTT} / 3,$$ + +$$e_{ini} = X_i,$$ + +$$e_{plus} = a \times X_i$$ + +$$e_{minus} = a \times |\Delta N_i|$$ + +#### 4.2.7.3 Bit separation and collection in uplink + +The systematic bits of turbo encoded TrCHs shall not be punctured, the other bits may be punctured. The systematic bits, first parity bits, and second parity bits in the bit sequence input to the rate matching block are therefore separated into three sequences. + +The first sequence contains: + +- All of the systematic bits that are from turbo encoded TrCHs. +- From 0 to 2 first and/or second parity bits that are from turbo encoded TrCHs. These bits come into the first sequence when the total number of bits in a block after radio frame segmentation is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The second sequence contains: + +- All of the first parity bits that are from turbo encoded TrCHs, except those that go into the first sequence when the total number of bits is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The third sequence contains: + +- All of the second parity bits that are from turbo encoded TrCHs, except those that go into the first sequence when the total number of bits is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The second and third sequences shall be of equal length, whereas the first sequence can contain from 0 to 2 more bits. Puncturing is applied only to the second and third sequences. The bit separation function is transparent for + +convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition. The bit separation and bit collection are illustrated in figures 5 and 6. + +![Figure 5: Puncturing of turbo encoded TrCHs in uplink. The diagram shows a block diagram of the uplink processing chain. It starts with 'Radio frame segmentation' which outputs e_{ik}. This signal enters a dashed box labeled 'Rate matching'. Inside, 'Bit separation' splits the signal into three parallel paths: x_{1ik}, x_{2ik}, and x_{3ik}. Each path goes through a 'Rate matching algorithm' block, which outputs y_{1ik}, y_{2ik}, and y_{3ik} respectively. These three signals are then combined in a 'Bit collection' block, which outputs f_{ik}. The signal f_{ik} then enters a 'TrCH Multiplexing' block, which produces the final output. Dotted lines extend from the 'TrCH Multiplexing' block downwards.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +Figure 5: Puncturing of turbo encoded TrCHs in uplink. The diagram shows a block diagram of the uplink processing chain. It starts with 'Radio frame segmentation' which outputs $e_{ik}$ . This signal enters a dashed box labeled 'Rate matching'. Inside, 'Bit separation' splits the signal into three parallel paths: $x_{1ik}$ , $x_{2ik}$ , and $x_{3ik}$ . Each path goes through a 'Rate matching algorithm' block, which outputs $y_{1ik}$ , $y_{2ik}$ , and $y_{3ik}$ respectively. These three signals are then combined in a 'Bit collection' block, which outputs $f_{ik}$ . The signal $f_{ik}$ then enters a 'TrCH Multiplexing' block, which produces the final output. Dotted lines extend from the 'TrCH Multiplexing' block downwards. + +Figure 5: Puncturing of turbo encoded TrCHs in uplink + +![Figure 6: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in uplink. The diagram shows a block diagram of the uplink processing chain. It starts with 'Radio frame segmentation' which outputs e_{ik}. This signal enters a dashed box labeled 'Rate matching'. Inside, 'Bit separation' outputs x_{1ik}, which goes through a 'Rate matching algorithm' block, which outputs y_{1ik}. This signal then enters a 'Bit collection' block, which outputs f_{ik}. The signal f_{ik} then enters a 'TrCH Multiplexing' block, which produces the final output. Dotted lines extend from the 'TrCH Multiplexing' block downwards.](107da2e3495b2f24352c9e3b26ec4841_img.jpg) + +Figure 6: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in uplink. The diagram shows a block diagram of the uplink processing chain. It starts with 'Radio frame segmentation' which outputs $e_{ik}$ . This signal enters a dashed box labeled 'Rate matching'. Inside, 'Bit separation' outputs $x_{1ik}$ , which goes through a 'Rate matching algorithm' block, which outputs $y_{1ik}$ . This signal then enters a 'Bit collection' block, which outputs $f_{ik}$ . The signal $f_{ik}$ then enters a 'TrCH Multiplexing' block, which produces the final output. Dotted lines extend from the 'TrCH Multiplexing' block downwards. + +Figure 6: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in uplink + +The bit separation is dependent on the 1st interleaving and offsets are used to define the separation for different TTIs. $b$ indicates the three sequences defined in this section, with $b=1$ indicating the first sequence, $b=2$ the second one, and $b=3$ the third one. The offsets $\alpha_b$ for these sequences are listed in table 5. + +Table 5: TTI dependent offset needed for bit separation + +| TTI (ms) | $\alpha_1$ | $\alpha_2$ | $\alpha_3$ | +|----------|------------|------------|------------| +| 10, 40 | 0 | 1 | 2 | +| 20, 80 | 0 | 2 | 1 | + +The bit separation is different for different radio frames in the TTI. A second offset is therefore needed. The radio frame number for TrCH $i$ is denoted by $n_i$ , and the offset by $\beta_{n_i}$ . + +**Table 6: Radio frame dependent offset needed for bit separation** + +| TTI (ms) | $\beta_0$ | $\beta_1$ | $\beta_2$ | $\beta_3$ | $\beta_4$ | $\beta_5$ | $\beta_6$ | $\beta_7$ | +|----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------| +| 10 | 0 | NA | NA | NA | NA | NA | NA | NA | +| 20 | 0 | 1 | NA | NA | NA | NA | NA | NA | +| 40 | 0 | 1 | 2 | 0 | NA | NA | NA | NA | +| 80 | 0 | 1 | 2 | 0 | 1 | 2 | 0 | 1 | + +#### 4.2.7.3.1 Bit separation + +The bits input to the rate matching are denoted by $e_{i1}, e_{i2}, e_{i3}, \dots, e_{iN_i}$ , where $i$ is the TrCH number and $N_i$ is the number of bits input to the rate matching block. Note that the transport format combination number $j$ for simplicity has been left out in the bit numbering, i.e. $N_i=N_{ij}$ . The bits after separation are denoted by $x_{bi1}, x_{bi2}, x_{bi3}, \dots, x_{biX_i}$ . For turbo encoded TrCHs with puncturing, $b$ indicates the three sequences defined in clause 4.2.7.3, with $b=1$ indicating the first sequence, and so forth. For all other cases $b$ is defined to be 1. $X_i$ is the number of bits in each separated bit sequence. The relation between $e_{ik}$ and $x_{bik}$ is given below. + +For turbo encoded TrCHs with puncturing: + +$$x_{1,i,k} = e_{i,3(k-1)+1+(\alpha_1+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +$$x_{1,i,\lfloor N_i/3 \rfloor+k} = e_{i,3\lfloor N_i/3 \rfloor+k} \quad k = 1, \dots, N_i \bmod 3 \quad \text{Note: When } (N_i \bmod 3) = 0 \text{ this row is not needed.}$$ + +$$x_{2,i,k} = e_{i,3(k-1)+1+(\alpha_2+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +$$x_{3,i,k} = e_{i,3(k-1)+1+(\alpha_3+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +For convolutionally encoded TrCHs and turbo encoded TrCHs with repetition: + +$$x_{1,i,k} = e_{i,k} \quad k = 1, 2, 3, \dots, X_i \quad X_i = N_i$$ + +#### 4.2.7.3.2 Bit collection + +The bits $x_{bik}$ are input to the rate matching algorithm described in subclause 4.2.7.5. The bits output from the rate matching algorithm are denoted $y_{bi1}, y_{bi2}, y_{bi3}, \dots, y_{biY_i}$ . + +Bit collection is the inverse function of the separation. The bits after collection are denoted by $z_{bi1}, z_{bi2}, z_{bi3}, \dots, z_{biY_i}$ . + +After bit collection, the bits indicated as punctured are removed and the bits are then denoted by $f_{i1}, f_{i2}, f_{i3}, \dots, f_{iV_i}$ , where $i$ is the TrCH number and $V_i = N_{ij} + \Delta N_{ij}$ . The relations between $y_{bik}$ , $z_{bik}$ , and $f_{ik}$ are given below. + +For turbo encoded TrCHs with puncturing ( $Y_i=X_i$ ): + +$$z_{i,3(k-1)+1+(\alpha_1+\beta_{n_i}) \bmod 3} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3\lfloor N_i/3 \rfloor+k} = y_{1,i,\lfloor N_i/3 \rfloor+k} \quad k = 1, \dots, N_i \bmod 3 \quad \text{Note: When } (N_i \bmod 3) = 0 \text{ this row is not needed.}$$ + +$$z_{i,3(k-1)+1+(\alpha_2+\beta_{n_i}) \bmod 3} = y_{2,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3(k-1)+1+(\alpha_3+\beta_{n_i}) \bmod 3} = y_{3,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +After the bit collection, bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $f_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $f_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +For convolutionally encoded TrCHs and turbo encoded TrCHs with repetition: + +$$z_{i,k} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +When repetition is used, $f_{i,k}=z_{i,k}$ and $Y_i=V_i$ . + +When puncturing is used, $Y_i=X_i$ and bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $f_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $f_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +#### 4.2.7.4 Bit separation and collection in downlink + +The systematic bits of turbo encoded TrCHs shall not be punctured, the other bits may be punctured. + +The systematic bits, first parity bits and second parity bits in the bit sequence input to the rate matching block are therefore separated into three sequences of equal lengths. + +The first sequence contains : + +- All of the systematic bits that are from turbo encoded TrCHs. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The second sequence contains: + +- All of the first parity bits that are from turbo encoded TrCHs. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The third sequence contains: + +- All of the second parity bits that are from turbo encoded TrCHs. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +Puncturing is applied only to the second and third sequences. + +The bit separation function is transparent for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition. The bit separation and bit collection are illustrated in figures 7 and 8. + +![Figure 7: Puncturing of turbo encoded TrCHs in downlink. The diagram shows a block diagram of the rate matching process. An input bit sequence c_ik enters a 'Channel coding' block. The output of the channel coding block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs three sequences: x_1ik, x_2ik, and x_3ik. These three sequences enter two 'Rate matching algorithm' blocks. The first algorithm takes x_1ik and produces y_1ik. The second algorithm takes x_2ik and x_3ik and produces y_2ik and y_3ik. These three output sequences (y_1ik, y_2ik, y_3ik) then enter a 'Bit collection' block, which outputs a single sequence g_ik. Finally, the sequence g_ik enters a block labeled '1st insertion of DTX indication'.](8269648391c59363ea61243864a2adf7_img.jpg) + +Figure 7: Puncturing of turbo encoded TrCHs in downlink. The diagram shows a block diagram of the rate matching process. An input bit sequence c\_ik enters a 'Channel coding' block. The output of the channel coding block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs three sequences: x\_1ik, x\_2ik, and x\_3ik. These three sequences enter two 'Rate matching algorithm' blocks. The first algorithm takes x\_1ik and produces y\_1ik. The second algorithm takes x\_2ik and x\_3ik and produces y\_2ik and y\_3ik. These three output sequences (y\_1ik, y\_2ik, y\_3ik) then enter a 'Bit collection' block, which outputs a single sequence g\_ik. Finally, the sequence g\_ik enters a block labeled '1st insertion of DTX indication'. + +Figure 7: Puncturing of turbo encoded TrCHs in downlink + +![Figure 8: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in downlink. The diagram shows a block diagram of the rate matching process. An input bit sequence c_ik enters a 'Channel coding' block. The output of the channel coding block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs a single sequence x_1ik. This sequence enters a 'Rate matching algorithm' block, which produces y_1ik. This output sequence y_1ik then enters a 'Bit collection' block, which outputs a single sequence g_ik. Finally, the sequence g_ik enters a block labeled '1st insertion of DTX indication'.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +Figure 8: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in downlink. The diagram shows a block diagram of the rate matching process. An input bit sequence c\_ik enters a 'Channel coding' block. The output of the channel coding block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs a single sequence x\_1ik. This sequence enters a 'Rate matching algorithm' block, which produces y\_1ik. This output sequence y\_1ik then enters a 'Bit collection' block, which outputs a single sequence g\_ik. Finally, the sequence g\_ik enters a block labeled '1st insertion of DTX indication'. + +Figure 8: Rate matching for convolutionally encoded TrCHs and for turbo encoded TrCHs with repetition in downlink + +#### 4.2.7.4.1 Bit separation + +The bits input to the rate matching are denoted by $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ , where $i$ is the TrCH number and $E_i$ is the number of bits input to the rate matching block. Note that $E_i$ is a multiple of 3 for turbo encoded TrCHs and that the transport format $l$ for simplicity has been left out in the bit numbering, i.e. $E_i = N_{il}^{TTI}$ . The bits after separation are denoted by $x_{bi1}, x_{bi2}, x_{bi3}, \dots, x_{biX_i}$ . For turbo encoded TrCHs with puncturing, $b$ indicates the three sequences defined in clause 4.2.7.4, with $b=1$ indicating the first sequence, and so forth. For all other cases $b$ is defined to be 1. $X_i$ is the number of bits in each separated bit sequence. The relation between $c_{ik}$ and $x_{bik}$ is given below. + +For turbo encoded TrCHs with puncturing: + +$$x_{1,i,k} = c_{i,3(k-1)+1} \quad k = 1, 2, 3, \dots, X_i \quad X_i = E_i/3$$ + +$$x_{2,i,k} = c_{i,3(k-1)+2} \quad k = 1, 2, 3, \dots, X_i \quad X_i = E_i/3$$ + +$$x_{3,i,k} = c_{i,3(k-1)+3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = E_i/3$$ + +For convolutionally encoded TrCHs and turbo encoded TrCHs with repetition: + +$$x_{1,i,k} = c_{i,k} \quad k = 1, 2, 3, \dots, X_i \quad X_i = E_i$$ + +#### 4.2.7.4.2 Bit collection + +The bits $x_{bik}$ are input to the rate matching algorithm described in subclause 4.2.7.5. The bits output from the rate matching algorithm are denoted $y_{bi1}, y_{bi2}, y_{bi3}, \dots, y_{biY_i}$ . + +Bit collection is the inverse function of the separation. The bits after collection are denoted by $z_{bi1}, z_{bi2}, z_{bi3}, \dots, z_{biY_i}$ . + +After bit collection, the bits indicated as punctured are removed and the bits are then denoted by $g_{i1}, g_{i2}, g_{i3}, \dots, g_{iG_i}$ , where $i$ is the TrCH number and $G_i = N_{ii}^{TTI} + \Delta N_{ii}^{TTI}$ . The relations between $y_{bik}$ , $z_{bik}$ , and $g_{ik}$ are given below. + +For turbo encoded TrCHs with puncturing ( $Y_i = X_i$ ): + +$$z_{i,3(k-1)+1} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3(k-1)+2} = y_{2,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3(k-1)+3} = y_{3,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +After the bit collection, bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $g_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $g_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +For convolutionally encoded TrCHs and turbo encoded TrCHs with repetition: + +$$z_{i,k} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +When repetition is used, $g_{i,k} = z_{i,k}$ and $Y_i = G_i$ . + +When puncturing is used, $Y_i = X_i$ and bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $g_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $g_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +#### 4.2.7.5 Rate matching pattern determination + +Denote the bits before rate matching by: + +$x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ , where $i$ is the TrCH number and the sequence is defined in 4.2.7.3 for uplink or in 4.2.7.4 for downlink. Parameters $X_i$ , $e_{ini}$ , $e_{plus}$ , and $e_{minus}$ are given in 4.2.7.1 for uplink or in 4.2.7.2 for downlink. + +The rate matching rule is as follows: + +if puncturing is to be performed + +$e = e_{ini}$ -- initial error between current and desired puncturing ratio + +$m = 1$ -- index of current bit + +do while $m \leq X_i$ + +$e = e - e_{minus}$ -- update error + +if $e \leq 0$ then -- check if bit number $m$ should be punctured + +set bit $x_{i,m}$ to $\delta$ where $\delta \notin \{0, 1\}$ + +$e = e + e_{plus}$ -- update error + +``` + +end if +m = m + 1 -- next bit +end do +else +e = eini -- initial error between current and desired puncturing ratio +m = 1 -- index of current bit +do while m <= Xi + e = e - eminus -- update error + do while e <= 0 -- check if bit number m should be repeated + repeat bit xi,m + e = e + eplus -- update error + end do + m = m + 1 -- next bit +end do +end if + +``` + +A repeated bit is placed directly after the original one. + +#### 4.2.8 TrCH multiplexing + +Every 10 ms, one radio frame from each TrCH is delivered to the TrCH multiplexing. These radio frames are serially multiplexed into a coded composite transport channel (CCTrCH). + +The bits input to the TrCH multiplexing are denoted by $f_{i1}, f_{i2}, f_{i3}, \dots, f_{iV_i}$ , where $i$ is the TrCH number and $V_i$ is the number of bits in the radio frame of TrCH $i$ . The number of TrCHs is denoted by $I$ . The bits output from TrCH + +multiplexing are denoted by $s_1, s_2, s_3, \dots, s_S$ , where $S$ is the number of bits, i.e. $S = \sum_i V_i$ . The TrCH multiplexing is defined by the following relations: + +$$s_k = f_{1k} \quad k = 1, 2, \dots, V_1$$ + +$$s_k = f_{2(k-V_1)} \quad k = V_1+1, V_1+2, \dots, V_1+V_2$$ + +$$s_k = f_{3(k-(V_1+V_2))} \quad k = (V_1+V_2)+1, (V_1+V_2)+2, \dots, (V_1+V_2)+V_3$$ + +... + +$$s_k = f_{I(k-(V_1+V_2+\dots+V_{I-1}))} \quad k = (V_1+V_2+\dots+V_{I-1})+1, (V_1+V_2+\dots+V_{I-1})+2, \dots, (V_1+V_2+\dots+V_{I-1})+V_I$$ + +#### 4.2.9 Insertion of discontinuous transmission (DTX) indication bits + +In the downlink, DTX is used to fill up the radio frame with bits. The insertion point of DTX indication bits depends on whether fixed or flexible positions of the TrCHs in the radio frame are used. It is up to the UTRAN to decide for each CCTrCH whether fixed, pseudo-flexible (Subclause 4.2.7.2.1A), or flexible positions are used during the connection. DTX indication bits only indicate when the transmission should be turned off, they are not transmitted. Pseudo-flexible rate matching is always used when DL\_DCH\_FET\_Config is configured by higher layers. Otherwise pseudo-flexible rate matching is not used. + +#### 4.2.9.1 1st insertion of DTX indication bits + +This step of inserting DTX indication bits is used only if the positions of the TrCHs in the radio frame are fixed. With fixed position scheme a fixed number of bits is reserved for each TrCH in the radio frame. + +The bits from rate matching are denoted by $g_{i1}, g_{i2}, g_{i3}, \dots, g_{iG_i}$ , where $G_i$ is the number of bits in one TTI of TrCH $i$ . Denote the number of bits in one radio frame of TrCH $i$ by $H_i$ . Denote $D_i$ the number of bits output of the first DTX insertion block. + +In TTIs containing no compressed frames or frames compressed by spreading factor reduction, $H_i$ is constant and corresponds to the maximum number of bits from TrCH $i$ in one radio frame for any transport format of TrCH $i$ and $D_i = F_i \times H_i$ . + +The bits output from the DTX insertion are denoted by $h_{i1}, h_{i2}, h_{i3}, \dots, h_{iD_i}$ . Note that these bits are three valued. They are defined by the following relations: + +$$h_{ik} = g_{ik} \quad k = 1, 2, 3, \dots, G_i$$ + +$$h_{ik} = \delta \quad k = G_i+1, G_i+2, G_i+3, \dots, D_i$$ + +where DTX indication bits are denoted by $\delta$ . Here $g_{ik} \in \{0, 1\}$ and $\delta \notin \{0, 1\}$ . + +In pseudo-flexible rate matching, the 1st insertion of DTX indication bits is the same as the above for fixed position rate matching, with a difference that the above procedure is applied to each TTI independently of others. + +#### 4.2.9.2 2nd insertion of DTX indication bits + +The DTX indication bits inserted in this step shall be placed at the end of the radio frame. Note that the DTX will be distributed over all slots after 2nd interleaving. + +The bits input to the DTX insertion block are denoted by $s_1, s_2, s_3, \dots, s_S$ , where $S$ is the number of bits from TrCH multiplexing. The number of PhCHs is denoted by $P$ and the number of bits in one radio frame, including DTX indication bits, for each PhCH by $R$ . + +$$R = \frac{N_{data,*}}{P} = 15 \times (N_{data1} + N_{data2})$$ + +In non-compressed frames, $N_{data1}$ and $N_{data2}$ are defined in [2]. + +For compressed frames, $N'_{data,*}$ is defined as $N'_{data,*} = P \times 15 \times (N'_{data1} + N'_{data2})$ . $N'_{data1}$ and $N'_{data2}$ are the number of bits in the data fields of the slot format used for the current compressed frame, i.e. slot format A or B as defined in [2] corresponding to the spreading factor and the number of transmitted slots in use. + +In frames compressed by higher layer scheduling, additional DTX with respect to normal mode shall be inserted if the transmission time reduction does not exactly create a transmission gap of the desired $TGL$ . + +The number of bits available to the CCTrCH in one radio frame compressed by spreading factor reduction or by higher + +layer scheduling is denoted by $N_{data,*}^{cm}$ and $R = \frac{N_{data,*}^{cm}}{P}$ . + +$$N_{data,*}^{cm} = \frac{N'_{data,*}}{2}$$ + +For frames compressed by spreading factor reduction + +For frames compressed by higher layer scheduling the exact value of $N_{data,*}^{cm}$ is dependent on the $TGL$ which is signalled from higher layers. It can be calculated as $N_{data,*}^{cm} = N'_{data,*} - N_{TGL}$ . + +$N_{TGL}$ is the number of bits that are located within the transmission gap and defined as: + +$$N_{\text{II}} = \begin{cases} \frac{TGL}{15} \times N'_{\text{data},*} & , \text{ if } N_{\text{first}} + TGL \leq 15 \\ \frac{15 - N_{\text{first}}}{15} \times N'_{\text{data},*} & , \text{ in first frame if } N_{\text{first}} + TGL > 15 \\ \frac{TGL - (15 - N_{\text{first}})}{15} \times N'_{\text{data},*} & , \text{ in second frame if } N_{\text{first}} + TGL > 15 \end{cases}$$ + +$N_{\text{first}}$ and $TGL$ are defined in subclause 4.4. + +The bits output from the DTX insertion block are denoted by $w_1, w_2, w_3, \dots, w_{(PR)}$ . Note that these bits are three valued. They are defined by the following relations: + +$$w_k = s_k \quad k = 1, 2, 3, \dots, S$$ + +$$w_k = \delta \quad k = S+1, S+2, S+3, \dots, P \cdot R$$ + +where DTX indication bits are denoted by $\delta$ . Here $s_k \in \{0, 1, p\}$ and $\delta \notin \{0, 1\}$ . + +## 4.2.10 Physical channel segmentation + +When more than one PhCH is used, physical channel segmentation divides the bits among the different PhCHs. The bits input to the physical channel segmentation are denoted by $x_1, x_2, x_3, \dots, x_X$ , where $X$ is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by $P$ . + +The bits after physical channel segmentation are denoted $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U}$ , where $p$ is PhCH number and $U$ is the number of bits in one radio frame for each PhCH, i.e. $U = \frac{X}{P}$ . The relation between $x_k$ and $u_{p,k}$ is given below. + +For all modes, some bits of the input flow are mapped to each code until the number of bits on the code is $U$ . All bits of the input flow are taken to be mapped to the codes. + +Bits on first PhCH after physical channel segmentation: + +$$u_{1,k} = x_k \quad k = 1, 2, \dots, U$$ + +Bits on second PhCH after physical channel segmentation: + +$$u_{2,k} = x_{k+U} \quad k = 1, 2, \dots, U$$ + +... + +Bits on the $P^{\text{th}}$ PhCH after physical channel segmentation: + +$$u_{P,k} = x_{k+(P-1) \times U} \quad k = 1, 2, \dots, U$$ + +### 4.2.10.1 Relation between input and output of the physical segmentation block in uplink + +The bits input to the physical segmentation are denoted by $s_1, s_2, s_3, \dots, s_S$ . Hence, $x_k = s_k$ and $Y = S$ . + +#### 4.2.10.2 Relation between input and output of the physical segmentation block in downlink + +The bits input to the physical segmentation are denoted by $w_1, w_2, w_3, \dots, w_{(PU)}$ . Hence, $x_k = w_k$ and $Y = PU$ . + +#### 4.2.11 2nd interleaving + +The 2nd interleaving is a block interleaver and consists of bits input to a matrix with padding, the inter-column permutation for the matrix and bits output from the matrix with pruning. The bits input to the block interleaver are + +denoted by $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U}$ , where $p$ is PhCH number and $U$ is the number of bits in one radio frame for one PhCH. The output bit sequence from the block interleaver is derived as follows: + +- (1) Assign $C2 = 30$ to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1, 2, ..., $C2 - 1$ from left to right. +- (2) Determine the number of rows of the matrix, $R2$ , by finding minimum integer $R2$ such that: + +$$U \leq R2 \times C2.$$ + +The rows of rectangular matrix are numbered 0, 1, 2, ..., $R2 - 1$ from top to bottom. + +- (3) Write the input bit sequence $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U}$ into the $R2 \times C2$ matrix row by row starting with bit $u_{p,1}$ in column 0 of row 0: + +$$\begin{bmatrix} y_{p,1} & y_{p,2} & y_{p,3} & \dots & y_{p,C2} \\ y_{p,(C2+1)} & y_{p,(C2+2)} & y_{p,(C2+3)} & \dots & y_{p,(2 \times C2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{p,((R2-1) \times C2+1)} & y_{p,((R2-1) \times C2+2)} & y_{p,((R2-1) \times C2+3)} & \dots & y_{p,(R2 \times C2)} \end{bmatrix}$$ + +where $y_{p,k} = u_{p,k}$ for $k = 1, 2, \dots, U$ and if $R2 \times C2 > U$ , the dummy bits are padded such that $y_{p,k} = 0$ or 1 for $k = U + 1, U + 2, \dots, R2 \times C2$ . These dummy bits are pruned away from the output of the matrix after the inter-column permutation. + +- (4) Perform the inter-column permutation for the matrix based on the pattern $\langle P2(j) \rangle_{j \in \{0, 1, \dots, C2-1\}}$ that is shown in table 7, where $P2(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y'_{p,k}$ . + +$$\begin{bmatrix} y'_{p,1} & y'_{p,(R2+1)} & y'_{p,(2 \times R2+1)} & \dots & y'_{p,((C2-1) \times R2+1)} \\ y'_{p,2} & y'_{p,(R2+2)} & y'_{p,(2 \times R2+2)} & \dots & y'_{p,((C2-1) \times R2+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y'_{p,R2} & y'_{p,(2 \times R2)} & y'_{p,(3 \times R2)} & \dots & y'_{p,(C2 \times R2)} \end{bmatrix}$$ + +- (5) The output of the block interleaver is the bit sequence read out column by column from the inter-column permuted $R2 \times C2$ matrix. The output is pruned by deleting dummy bits that were padded to the input of the matrix before the inter-column permutation, i.e. bits $y'_{p,k}$ that corresponds to bits $y_{p,k}$ with $k > U$ are removed from the output. The bits after 2nd interleaving are denoted by $v_{p,1}, v_{p,2}, \dots, v_{p,U}$ , where $v_{p,1}$ corresponds to the bit $y'_{p,k}$ with smallest index $k$ after pruning, $v_{p,2}$ to the bit $y'_{p,k}$ with second smallest index $k$ after pruning, and so on. + +**Table 7 Inter-column permutation pattern for 2nd interleaving** + +| Number of columns C2 | Inter-column permutation pattern
< P2(0), P2(1), ..., P2(C2-1) > | +|----------------------|----------------------------------------------------------------------------------------------------------------| +| 30 | <0, 20, 10, 5, 15, 25, 3, 13, 23, 8, 18, 28, 1, 11, 21, 6, 16, 26, 4, 14, 24, 19, 9, 29, 12, 2, 7, 22, 27, 17> | + +#### 4.2.11.1 2nd interleaving for Secondary CCPCH with 16QAM + +For MBSFN transmissions with 16QAM, the 2nd interleaving for Secondary CCPCH is done as illustrated in figure 8a below. The basic block interleaver is as described in Clause 4.2.11. For 16QAM modulated bits, there are two identical basic block interleavers of size $R2 \times 30$ , where $R2$ is the minimum integer fulfilling + +, + +The output bits from the physical channel segmentation are divided two by two between the interleavers: bits $u_{p,k}$ and $u_{p,k+1}$ go to the first interleaver and bits $u_{p,k+2}$ and $u_{p,k+3}$ go to the second interleaver. Bits are collected two by two from the interleavers: bits $v_{p,k}$ and $v_{p,k+1}$ are obtained from the first interleaver and bits $v_{p,k+2}$ and $v_{p,k+3}$ are obtained from the second interleaver, where $k \bmod 4=1$ . + +![Figure 8a: Interleaver structure for Secondary CCPCH. The diagram shows two interleavers, each labeled 'Interleaver (R2 x 30)'. The top interleaver receives inputs u_{p,k} (QPSK) and u_{p,k} u_{p,k+1} (16QAM) and produces outputs v_{p,k} (QPSK) and v_{p,k} v_{p,k+1} (16QAM). The bottom interleaver receives inputs u_{p,k+2} u_{p,k+3} (16QAM) and produces outputs v_{p,k+2} v_{p,k+3} (16QAM). Dashed lines indicate the flow of bits between the two interleavers.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +Figure 8a: Interleaver structure for Secondary CCPCH. The diagram shows two interleavers, each labeled 'Interleaver (R2 x 30)'. The top interleaver receives inputs u\_{p,k} (QPSK) and u\_{p,k} u\_{p,k+1} (16QAM) and produces outputs v\_{p,k} (QPSK) and v\_{p,k} v\_{p,k+1} (16QAM). The bottom interleaver receives inputs u\_{p,k+2} u\_{p,k+3} (16QAM) and produces outputs v\_{p,k+2} v\_{p,k+3} (16QAM). Dashed lines indicate the flow of bits between the two interleavers. + +**Figure 8a: Interleaver structure for Secondary CCPCH** + +#### 4.2.12 Physical channel mapping + +The PhCH for both uplink and downlink is defined in [2]. The bits input to the physical channel mapping are denoted by $v_{p,1}, v_{p,2}, \dots, v_{p,U}$ , where $p$ is the PhCH number and $U$ is the number of bits in one radio frame for one PhCH. The bits $v_{p,k}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +In compressed mode, no bits are mapped to certain slots of the PhCH(s). If $N_{first} + TGL \leq 15$ , no bits are mapped to slots $N_{first}$ to $N_{last}$ . If $N_{first} + TGL > 15$ , i.e. the transmission gap spans two consecutive radio frames, the mapping is as follows: + +- In the first radio frame, no bits are mapped to slots $N_{first}, N_{first}+1, N_{first}+2, \dots, 14$ . +- In the second radio frame, no bits are mapped to the slots $0, 1, 2, \dots, N_{last}$ . + +$TGL$ , $N_{first}$ , and $N_{last}$ are defined in subclause 4.4. + +#### 4.2.12.1 Uplink + +When UL\_DPCH\_10ms\_Mode is configured, uplink physical channel mapping depends on whether a compressed-mode transmission gap overlaps with the first radio frame in 20ms CI. A distinction is made between the following cases: + +4.2.12.1.1 UL\_DPCH\_10ms\_Mode is not configured by higher layers, or, no compressed-mode transmission gap overlaps with the first radio frame in the 20ms CI + +In uplink, the PhCHs used during a radio frame are either completely filled with bits that are transmitted over the air or not used at all. The only exception is when the UE is in compressed mode. The transmission can then be turned off during consecutive slots of the radio frame. + +4.2.12.1.2 UL\_DPCH\_10ms\_Mode is configured by higher layers, and, a compressed-mode transmission gap overlaps with the first radio frame in 20ms CI + +In this case, physical channel mapping is performed over 20ms Compression Intervals (20ms CI). Note that as a consequence of radio frame segmentation procedure in Subclause 4.2.6, there are no bit inputs to the second radio frame in one 20ms CI. Denote the bit inputs to the physical channel mapping in a 20ms CI by $v_{p,1}, v_{p,2}, v_{p,3}, \dots, v_{p,U}$ , where $p$ is the PhCH number and $U$ is the number of bits in one radio frame for one PhCH. Then, the 15 slots used to map the bits $v_{p,1}, v_{p,2}, v_{p,3}, \dots, v_{p,U}$ are the first 15 slots in the 20ms CI excluding slots in the compressed-mode transmission gap. In other words, + +if $N_{first} + TGL \leq 15$ , i.e., the transmission gap spans only one radio frame, and the mapping is as follows + +The 15 slots used for mapping are slots 0 to $N_{first} - 1$ in the first 10ms radio frame in the 20ms CI, slots $N_{last} + 1$ to slot 14 in the first 10ms radio frame in the 20ms CI, and slots 0 to $TGL - 1$ in the second radio frame of the 20ms CI. + +Else if $N_{first} + TGL > 15$ , i.e., the transmission gap spans two consecutive radio frames, the mapping is as follows: + +If the transmission gap occurs at the beginning of the first radio frame of the 20ms CI, then the 15 slots used for mapping are slots $N_{last} + 1$ to slot 14 of the first radio frame of the 20ms CI and slots 0 to $N_{last}$ of the second radio frame of the 20ms CI; + +Else, if the transmission gap occurs at the end of the first radio frame of the 20ms CI, then the 15 slots used for mapping are slots 0 to $N_{first} - 1$ of the first radio frame of the 20ms CI and slots $N_{last} + 1$ to $N_{last} + 15 - N_{first}$ of the second radio frame of the 20ms CI. + +#### 4.2.12.2 Downlink + +In downlink, the PhCHs do not need to be completely filled with bits that are transmitted over the air. Values $v_{p,k} \notin \{0, 1\}$ correspond to DTX indicators, which are mapped to the DPCCH/DPDCH fields but are not transmitted over the air. + +In compressed mode when DL\_DCH\_FET\_Config is configured by higher layers, the mapping of data bits onto the slots of the PhCH is the same as normal mode, with a difference that the data bits that are mapped to slots in a transmission gap are not transmitted over the air. + +During compressed mode by reducing the spreading factor by 2, the data bits are always mapped into 7.5 slots within a compressed frame. No bits are mapped to the DPDCH field as follows: + +If $N_{first} + TGL \leq 15$ , i.e. the transmission gap spans one radio frame, + +if $N_{first} + 7 \leq 14$ + +no bits are mapped to slots $N_{first}, N_{first} + 1, N_{first} + 2, \dots, N_{first} + 6$ + +no bits are mapped to the first $(N_{Data1} + N_{Data2})/2$ bit positions of slot $N_{first} + 7$ + +else + +no bits are mapped to slots $N_{first}, N_{first} + 1, N_{first} + 2, \dots, 14$ + +no bits are mapped to slots $N_{first} - 1, N_{first} - 2, N_{first} - 3, \dots, 8$ + +no bits are mapped to the last $(N_{Data1} + N_{Data2})/2$ bit positions of slot 7 + +end if + +If $N_{first} + TGL > 15$ , i.e. the transmission gap spans two consecutive radio frames, + +In the first radio frame, no bits are mapped to last $(N_{\text{Data1}} + N_{\text{Data2}})/2$ bit positions in slot 7 as well as to slots 8, 9, 10, ..., 14. + +In the second radio frame, no bits are mapped to slots 0, 1, 2, ..., 6 as well as to first $(N_{\text{Data1}} + N_{\text{Data2}})/2$ bit positions in slot 7. + +$N_{\text{Data1}}$ and $N_{\text{Data2}}$ are defined in [2]. + +## 4.2.13 Restrictions on different types of CCTrCHs + +Restrictions on the different types of CCTrCHs are described in general terms in TS 25.302[11]. In this subclause those restrictions are given with layer 1 notation. + +### 4.2.13.1 Uplink Dedicated channel (DCH) + +The maximum value of the number of TrCHs $I$ in a CCTrCH, the maximum value of the number of transport blocks $M_i$ on each transport channel, and the maximum value of the number of DPDCHs $P$ are given from the UE capability class. + +### 4.2.13.2 Random Access Channel (RACH) + +- There can only be one TrCH in each RACH CCTrCH, i.e. $I=1$ , $s_k = f_{1k}$ and $S = V_1$ . +- The maximum value of the number of transport blocks $M_i$ on the transport channel is given from the UE capability class. +- The transmission time interval is either 10 ms or 20 ms. +- Only one PRACH is used, i.e. $P=1$ , $u_{1k} = s_k$ , and $U = S$ . +- The Static rate matching parameter $RM_i$ is not provided by higher layer signalling on the System information as the other transport channel parameters. Any value may be used as there is one transport channel in the CCTrCH, hence one transport channel per Transport Format Combination and no need to do any balancing between multiple transport channels. + +### 4.2.13.3 Void + +### 4.2.13.4 Downlink Dedicated Channel (DCH) + +The maximum value of the number of TrCHs $I$ in a CCTrCH, the maximum value of the number of transport blocks $M_i$ on each transport channel, and the maximum value of the number of DPDCHs $P$ are given from the UE capability class. + +### 4.2.13.5 Void + +### 4.2.13.6 Broadcast channel (BCH) + +- There can only be one TrCH in a BCH CCTrCH, i.e. $I=1$ , $s_k = f_{1k}$ , and $S = V_1$ . +- There can only be one transport block in each transmission time interval, i.e. $M_i = 1$ . +- All transport format attributes have predefined values which are provided in [11] apart from the rate matching $RM_i$ . +- The Static rate matching parameter $RM_i$ is not provided by higher layer signalling neither fixed. Any value may be used as there is one transport channel in the CCTrCH, hence one transport channel per Transport Format Combination and no need to do any balancing between multiple transport channels. +- Only one primary or secondary CCPCH is used per CCTrCH, i.e. $P=1$ . + +### 4.2.13.7 Forward access and paging channels (FACH and PCH) + +- The maximum value of the number of TrCHs $I$ in a CCTrCH and the maximum value of the number of transport blocks $M_i$ on each transport channel are given from the UE capability class. +- The transmission time interval for TrCHs of PCH type is always 10 ms. + +- Only one secondary CCPCH is used per CCTrCH, i.e. $P=1$ . + +#### 4.2.13.8 High Speed Downlink Shared Channel (HS-DSCH) associated with a DCH + +- There can be only one TrCH in an HS-DSCH CCTrCH, i.e. $I = 1$ , +- In case the UE is not configured in MIMO mode and not in MIMO mode with four transmit antennas or the UE is configured in MIMO mode and single-stream restriction is configured, there can only be one transport block in each transmission time interval, i.e. $M_i = 1$ . In case the UE is configured in MIMO mode, there can be one or two transport blocks in each transmission time interval and in case the UE is configured in MIMO mode with four transmit antennas, there can be up to four transport blocks in each transmission time interval. +- The transmission time interval for TrCHs of HS-DSCH type is always 2 ms. +- The maximum value of the number of HS-PDSCHs $P$ are given from the UE capability class. + +#### 4.2.13.9 Enhanced Dedicated Channel (E-DCH) + +- There can be only one TrCH in the E-DCH CCTrCH, i.e. $I = 1$ . +- If the UL\_MIMO\_Enabled is not set to TRUE, there can only be one transport block in each transmission time interval, i.e. $M_i = 1$ . If the UL\_MIMO\_Enabled is set to TRUE, there can be one or two transport blocks in each transmission time interval.. +- The transmission time interval for TrCHs of E-DCH type is 2 ms or 10 ms. If the UL\_MIMO\_Enabled is set to TRUE, the transmission time interval for TrCHs of E-DCH type is always set to 2 ms. +- The maximum value of the number of E-DPDCHs $P$ are given from the UE capabilities. + +### 4.2.14 Multiplexing of different transport channels into one CCTrCH, and mapping of one CCTrCH onto physical channels + +The following rules shall apply to the different transport channels which are part of the same CCTrCH: + +- 1) Transport channels multiplexed into one CCTrCH shall have co-ordinated timings. When the TFCS of a CCTrCH is changed because one or more transport channels are added to the CCTrCH or reconfigured within the CCTrCH, or removed from the CCTrCH, the change may only be made at the start of a radio frame with CFN fulfilling the relation + +$$\text{CFN mod } F_{\max} = 0,$$ + +where $F_{\max}$ denotes the maximum number of radio frames within the transmission time intervals of all transport channels which are multiplexed into the same CCTrCH, including any transport channels $i$ which are added, reconfigured or have been removed, and CFN denotes the connection frame number of the first radio frame of the changed CCTrCH. + +After addition or reconfiguration of a transport channel $i$ within a CCTrCH, the TTI of transport channel $i$ may only start in radio frames with CFN fulfilling the relation: + +$$\text{CFN mod } F_i = 0.$$ + +- 2) Only transport channels with the same active set can be mapped onto the same CCTrCH. +- 3) Different CCTrCHs cannot be mapped onto the same PhCH. +- 4) One CCTrCH shall be mapped onto one or several PhCHs. These physical channels shall all have the same SF, except for the case of four E-DPDCHs, where two E-DPDCHs have spreading factor 2 and the other two E-DPDCHs have spreading factor 4, and for the case of four S-E-DPDCHs, where two S-E-DPDCHs have spreading factor 2 and the other two S-E-DPDCHs have spreading factor 4. + +All physical channels belonging to the same CCTrCH shall use the same modulation scheme with the exception that, when transmitted, the modulation scheme used by the four S-E-DPDCHs may be different from that used by the four E-DPDCHs. + +The 4PAM modulation shall only be used for orthogonal PhCH pairs which are orthogonal in phase and use the same OVSF code. + +The 8PAM modulation shall only be used for orthogonal PhCH pairs which are orthogonal in phase and use the same OVSF code. + +- 5) Dedicated Transport channels and common transport channels cannot be multiplexed into the same CCTrCH. +- 6) For the common transport channels, only the FACH and PCH may belong to the same CCTrCH. + +There are hence two types of CCTrCH: + +- 1) CCTrCH of dedicated type, corresponding to the result of coding and multiplexing of one or several DCHs or one E-DCH. +- 2) CCTrCH of common type, corresponding to the result of the coding and multiplexing of a common channel, RACH in the uplink, HS-DSCH, BCH, or FACH/PCH for the downlink. + +#### 4.2.14.1 Allowed CCTrCH combinations for one UE + +##### 4.2.14.1.1 Allowed CCTrCH combinations on the uplink + +The following CCTrCH combinations for one UE are allowed: + +- 1) one CCTrCH of dedicated type or + - 1a) two CCTrCHs of dedicated type, one being of DCH type and the other one of E-DCH type or +- 2) one CCTrCH of common type. + +##### 4.2.14.1.2 Allowed CCTrCH combinations on the downlink + +The following CCTrCH combinations for one UE are allowed: + +- $x$ CCTrCH of dedicated type + $y$ CCTrCH of common type. The allowed combination of CCTrCHs of dedicated and common type are given from UE radio access capabilities. There can be a maximum of one CCTrCH of common type for HS-DSCH. The maximum number of CCTrCHs of common type for FACH is determined from UE capabilities. With one CCTrCH of common type for HS-DSCH, there shall be only one CCTrCH of dedicated type. + +NOTE 1: There is only one DPCCH in the uplink, hence one TPC bits flow on the uplink to control possibly the different DPDCHs on the downlink, part of the same or several CCTrCHs. + +NOTE 2: There is only one DPCCH in the downlink, even with multiple CCTrCHs. With multiple CCTrCHs, the DPCCH is transmitted on one of the physical channels of that CCTrCH which has the smallest SF among the multiple CCTrCHs. Thus there is only one TPC command flow and only one TFCI word in downlink even with multiple CCTrCHs. + +NOTE 3: in the current release, only 1 CCTrCH of dedicated type is supported. + +## 4.3 Transport format detection + +If the transport format set of a TrCH $i$ contains more than one transport format, the transport format can be detected according to one of the following methods: + +- TFCI based detection: This method is applicable when the transport format combination is signalled using the TFCI field; +- explicit blind detection: This method typically consists of detecting the TF of TrCH $i$ by use of channel decoding and CRC check; +- guided detection: This method is applicable when there is at least one other TrCH $i'$ , hereafter called guiding TrCH, such that: + - the guiding TrCH has the same TTI duration as the TrCH under consideration, i.e. $F_{i'} = F_i$ ; + +- different TFs of the TrCH under consideration correspond to different TFs of the guiding TrCH; +- explicit blind detection is used on the guiding TrCH. + +If the transport format set for a TrCH *i* does not contain more than one transport format with more than zero transport blocks, no explicit blind transport format detection needs to be performed for this TrCH. The UE can use guided detection for this TrCH or single transport format detection, where the UE always assumes the transport format corresponding to more than zero transport blocks for decoding. + +For uplink, blind transport format detection is a network controlled option. For downlink, the UE shall be capable of performing blind transport format detection, if certain restrictions on the configured transport channels are fulfilled. + +#### 4.3.1 Blind transport format detection + +When no TFCI is available then explicit blind detection or guided detection shall be performed on all TrCHs within the CCTrCH that have more than one transport format and that do not use single transport format detection. The UE shall only be required to support blind transport format detection if all of the following restrictions are fulfilled: + +1. either only one CCTrCH is received, or one CCTrCH of dedicated type and one CCTrCH of common type for HS-DSCH are received by the UE; + +If only one CCTrCH is received by the UE, the following conditions apply to that CCTrCH and those TrCHs that are multiplexed on the CCTrCH. If one CCTrCH of dedicated type and one CCTrCH of common type for HS-DSCH are received by the UE, the following conditions apply to the dedicated type CCTrCH and the TrCHs that are multiplexed on the dedicated type CCTrCH. + +2. the number of CCTrCH bits received per radio frame is 600 or less; +3. the number of transport format combinations of the CCTrCH is 64 or less; +4. fixed positions of the transport channels is used on the CCTrCH to be detectable; +5. convolutional coding is used on all explicitly detectable TrCHs; +6. CRC with non-zero length is appended to all transport blocks on all explicitly detectable TrCHs; +7. at least one transport block shall be transmitted per TTI on each explicitly detectable TrCH; +8. the number of explicitly detectable TrCHs is 3 or less; +9. for all explicitly detectable TrCHs *i*, the number of code blocks in one TTI ( $C_i$ ) shall not exceed 1; +10. the sum of the transport format set sizes of all explicitly detectable TrCHs, is 16 or less. The transport format set size is defined as the number of transport formats within the transport format set; +11. there is at least one TrCH that can be used as the guiding transport channel for all transport channels using guided detection. + +Examples of blind transport format detection methods are given in annex A. + +#### 4.3.1A Single transport format detection + +When no TFCI is available, then single transport format detection shall be applied on all TrCHs within the CCTrCH that have a transport format set not containing more than one transport format with more than zero transport blocks and that do not use guided detection. The UE shall only be required to support single transport format detection if the following restrictions are fulfilled: + +1. For each transport channel that is single transport format detected, CRC with non-zero length is appended to all transport blocks within the non-zero transport block transport format; +2. fixed positions of the transport channels is used on the CCTrCH to be detectable. + +### 4.3.2 Transport format detection based on TFCI + +If a TFCI is available, then TFCI based detection shall be applicable to all TrCHs within the CCTrCH. The TFCI informs the receiver about the transport format combination of the CCTrCHs. As soon as the TFCI is detected, the transport format combination, and hence the transport formats of the individual transport channels are known. + +If higher layers indicate that S-CCPCHs can be soft combined during a period of consecutive TTIs, then the same TFCI is used on those S-CCPCHs for each combinable TTI. The UE may therefore detect TFCI on one S-CCPCH to determine the TFCI on all S-CCPCHs that can be soft combined. (S-CCPCH soft combining is further specified in [4]). + +### 4.3.3 Coding of Transport-Format-Combination Indicator (TFCI) + +The TFCI is encoded using a (32, 10) sub-code of the second order Reed-Muller code. The coding procedure is as shown in figure 9. + +![Figure 9: Channel coding of TFCI information bits. The diagram shows a flow from left to right: 'TFCI (10 bits) a9...a0' points to a box labeled '(32,10) sub-code of second order Reed-Muller code', which points to 'TFCI code word b0...b31'.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` + +graph LR + A["TFCI +(10 bits) +a9...a0"] --> B["(32,10) sub-code of +second order +Reed-Muller code"] + B --> C["TFCI code +word +b0...b31"] + +``` + +Figure 9: Channel coding of TFCI information bits. The diagram shows a flow from left to right: 'TFCI (10 bits) a9...a0' points to a box labeled '(32,10) sub-code of second order Reed-Muller code', which points to 'TFCI code word b0...b31'. + +Figure 9: Channel coding of TFCI information bits + +If the TFCI consists of less than 10 bits, it is padded with zeros to 10 bits, by setting the most significant bits to zero. The length of the TFCI code word is 32 bits. + +The code words of the (32,10) sub-code of second order Reed-Muller code are linear combination of 10 basis sequences. The basis sequences are as in the following table 8. + +Table 8: Basis sequences for (32,10) TFCI code + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | M i,6 | M i,7 | M i,8 | M i,9 | +|----|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 2 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| 4 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 5 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| 6 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | +| 7 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| 8 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 9 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | +| 10 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | +| 11 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| 12 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| 13 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 14 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | +| 15 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | +| 16 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| 17 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | +| 18 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | +| 19 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | +| 20 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| 21 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | +| 22 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | +| 23 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | +| 24 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| 25 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 26 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| 27 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| 28 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | +| 29 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 30 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 31 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | + +When UL\_DPCH\_10ms\_Mode is not configured by higher layers, the TFCI information bits $a_0, a_1, a_2, a_3, a_4, a_5, a_6, a_7, a_8, a_9$ (where $a_0$ is LSB and $a_9$ is MSB) shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated DPCH radio frame. + +When UL\_DPCH\_10ms\_Mode is configured by higher layers, the TFCI information bits $a_0, a_1, a_2, a_3, a_4, a_5, a_6, a_7, a_8, a_9$ (where $a_0$ is LSB and $a_9$ is MSB) shall correspond to unsigned binary expression of the sum of the TFC index and the size of TFCS. + +The output code word bits $b_i$ are given by: + +$$b_i = \sum_{n=0}^9 (a_n \times M_{i,n}) \bmod 2$$ + +where $i = 0, \dots, 31$ . + +The output bits are denoted by $b_k, k = 0, 1, 2, \dots, 31$ . + +In downlink, when the SF < 128 the encoded TFCI code words are repeated yielding 8 encoded TFCI bits per slot in normal mode and 16 encoded TFCI bits per slot in compressed mode. Mapping of repeated bits to slots is explained in subclause 4.3.5. + +#### 4.3.4 Void + +#### 4.3.5 Mapping of TFCI words + +##### 4.3.5.1 Mapping of TFCI word in normal mode in downlink, and in uplink when uplink DPCCH slot format is not 5 + +The bits of the code word are directly mapped to the slots of the radio frame. Within a slot the bit with lower index is transmitted before the bit with higher index. The coded bits $b_k$ , are mapped to the transmitted TFCI bits $d_k$ , according to the following formula: + +$$d_k = b_{k \bmod 32}$$ + +For uplink physical channels regardless of the SF and downlink physical channels, if $SF \geq 128, k = 0, 1, 2, \dots, 29$ . Note that this means that bits $b_{30}$ and $b_{31}$ are not transmitted. + +For downlink physical channels whose $SF < 128, k = 0, 1, 2, \dots, 119$ . Note that this means that bits $b_0$ to $b_{23}$ are transmitted four times and bits $b_{24}$ to $b_{31}$ are transmitted three times. + +##### 4.3.5.1A Mapping of TFCI word in normal mode in uplink when uplink DPCCH slot format is 5 + +In each 20ms CI, the first 10 slots of uplink DPCCH contain TFCI bits. The bits of the codeword are directly mapped to the slots of the radio frame. Within a slot, the bit with lower index is transmitted before the bit with higher index. The coded bits $b_k$ , are mapped to the transmitted TFCI bits $d_k$ , according to the following formula: + +$$d_k = b_k, \text{ for } k = 0, \dots, 19.$$ + +##### 4.3.5.1.1 Mapping of TFCI bits for Secondary CCPCH with 16QAM + +For MBSFN transmissions with 16QAM, the coded bits $b_k$ , are mapped to the transmitted TFCI bits according to the following formulas: + +$$d_{4k} = b_{2k \bmod 32},$$ + +$$d_{4k+1} = b_{2k+1 \bmod 32},$$ + +$$d_{4k+2} = (d_{4k} + d_{4k+1}) \bmod 2,$$ + +$$d_{4k+3} = (1 + d_{4k} + d_{4k+1}) \bmod 2,$$ + +where $k = 0, 1, 2, \dots, 59$ for $SF < 128$ and $k = 0, 1, 2, \dots, 14$ for $SF \geq 128$ . + +#### 4.3.5.2 Mapping of TFCI word in compressed mode + +The mapping of the TFCI bits in compressed mode is different for uplink, downlink with $SF \geq 128$ and downlink with $SF < 128$ . + +##### 4.3.5.2.1 Uplink compressed mode + +###### 4.3.5.2.1.1 Uplink DPCCH slot formats other than 5 + +For uplink compressed mode, the slot format is changed so that no TFCI coded bits are lost. The different slot formats in compressed mode do not match the exact number of TFCI coded bits for all possible TGLs. Repetition of the TFCI bits is therefore used. + +Denote the number of bits available in the TFCI fields of one compressed radio frame by $D$ and the number of bits in the TFCI field in a slot by $N_{\text{TFCI}}$ . The parameter $E$ is used to determine the number of the first TFCI bit to be repeated. + +$E = N_{\text{first}} N_{\text{TFCI}}$ , if the start of the transmission gap is allocated to the current frame. + +$E = 0$ , if the start of the transmission gap is allocated to the previous frame and the end of the transmission gap is allocated to the current frame. + +The TFCI coded bits $b_k$ are mapped to the bits in the TFCI fields $d_k$ . The following relations define the mapping for each compressed frame. + +$$d_k = b_k$$ + +where $k = 0, 1, 2, \dots, \min(31, D-1)$ . + +If $D > 32$ , the remaining positions are filled by repetition (in reversed order): + +$$d_{D-k-1} = b_{(E+k) \bmod 32}$$ + +where $k = 0, \dots, D-33$ . + +###### 4.3.5.2.1.2 Uplink DPCCH slot format 5 + +In each 20ms CI, the first 10 UL DPCCH slots that are not in a compressed mode transmission gap contain TFCI information. The bits of the codeword are directly mapped to these slots. Within a slot, the bit with lower index is transmitted before the bit with higher index. The coded bits $b_k$ , are mapped to the transmitted TFCI bits $d_k$ , according to the following formula: + +$$d_k = b_k, \text{ for } k = 0, \dots, 19.$$ + +##### 4.3.5.2.2 Downlink compressed mode + +For downlink compressed mode, the slot format is changed so that no TFCI coded bits are lost. The different slot formats in compressed mode do not match the exact number of TFCI bits for all possible TGLs. DTX is therefore used if the number of bits available in the TFCI fields in one compressed frame exceeds the number of TFCI bits given from the slot format. The block of bits in the TFCI fields where DTX is used starts on the first TFCI field after the transmission gap. If there are more bits available in the TFCI fields before the transmission gap than TFCI bits, DTX is also used on the bits in the last TFCI fields before the transmission gap. + +Denote the number of bits available in the TFCI fields of one compressed radio frame by $D$ and the number of bits in the TFCI field in a slot by $N_{\text{TFCI}}$ . The parameter $E$ is used to determine the position of the first bit in the TFCI field on which DTX is used. + +$E = N_{\text{first}} N_{\text{TFCI}}$ , if the start of the transmission gap is allocated to the current frame. + +$E = 0$ , if the start of the transmission gap is allocated to the previous frame and the end of the transmission gap is allocated to the current frame. + +Denote the total number of TFCI bits to be transmitted by $F$ . $F = 32$ for slot formats $nA$ or $nB$ , where $n = 0, 1, \dots, 11$ (see table 11 in [2]). Otherwise, $F = 128$ . The TFCI coded bits $b_k$ are mapped to the bits in the TFCI fields $d_k$ . The following relations define the mapping for each compressed frame. + +If $E > 0$ , + +$$d_k = b_{k \bmod 32}$$ + +where $k = 0, 1, 2, \dots, \min(E, F)-1$ . + +If $E < F$ , + +$$d_{k+D-F} = b_{k \bmod 32}$$ + +where $k = E, \dots, F-1$ . + +DTX is used on $d_k$ where $k = \min(E, F), \dots, \min(E, F) + D - F - 1$ . + +## 4.3A Mapping of DL FET ACK/NACK bits + +When slot format 5 is used for uplink DPCCH, TFCI fields in each 20ms TTI contain DL FET ACK/NACK indicators in all transmitted slots that do not contain TFCI bits (see subclauses 4.3.5.1A and 4.3.5.2.1.2). Each DL FET ACK/NACK indicator is encoded as specified in Table 9. When $DL\_DCH\_FET\_Config = 0$ , the bits that replace DL FET ACK/NACK indicators are unspecified. + +**Table 9: ACK/NACK transmission on uplink DPCCH** + +| DL FET ACK/NACK indicator | bits in slot $i$ | +|---------------------------|------------------| +| ACK | 1 | +| NACK | 0 | + +Let the slots in a 20ms CI be numbered $0, 1, \dots, 29$ . For each $i = 0, 1, \dots, 29$ , if slot $i$ is not in a compressed-mode gap and does not contain TFCI bits, then a DL FET NACK indicator is transmitted in slot $i$ if at least one of the following conditions holds: + +- At least one of the transport blocks transmitted on downlink DPDCH with a TTI that includes slot $i$ has not been successfully decoded by the UE. +- $i$ belongs in the set $S = \{11, 13, 15, 17, 19, 21, 23, 25, 27, 29\}$ , and a DL FET ACK indication has not been sent in any prior slot $j, 0 \leq j < i$ , in this 20ms TTI. +- A downlink slot containing bits of a non-zero transport block of a maximum TTI TrCH overlaps with slot $i$ . + +A DL FET ACK indicator is sent in all transmitted UL DPCCH slots that do not fall in a compressed mode gap and do not contain a DL FET NACK indicator or TFCI bit. If a 20ms CI contains a DL FET ACK indication, it always contains at least two slots carrying a DL FET ACK indication. + +## 4.4 Compressed mode + +In compressed frames, TGL slots from $N_{first}$ to $N_{last}$ are not used for transmission of data. As illustrated in figure 11, the instantaneous transmit power is increased in the compressed frame in order to keep the quality (BER, FER, etc.) unaffected by the reduced processing gain. The amount of power increase depends on the transmission time reduction method (see subclause 4.4.3). What frames are compressed, are decided by the network. When in compressed mode, compressed frames can occur periodically, as illustrated in figure 11, or requested on demand. The rate and type of compressed frames is variable and depends on the environment and the measurement requirements. + +![Figure 11: Compressed mode transmission diagram showing a sequence of frames with transmission gaps.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +The diagram illustrates a sequence of frames over time. A horizontal line represents the timeline, with several rectangular blocks representing frames. One frame is highlighted with a double-headed arrow below it, labeled "One frame (10 ms)". Between this frame and the next, there is a gap. Two vertical bars represent the transmission power levels. The first bar is shorter, and the second bar, corresponding to the gap, is taller, indicating increased power. An arrow points to the gap with the text "Transmission gap available for inter-frequency measurements". + +Figure 11: Compressed mode transmission diagram showing a sequence of frames with transmission gaps. + +Figure 11: Compressed mode transmission + +### 4.4.1 Frame structure in the uplink + +The frame structure for uplink compressed frames is illustrated in figure 12. + +![Figure 12: Frame structure in uplink compressed transmission diagram showing slot details.](30fe9e9487585118063341332e802e98_img.jpg) + +The diagram shows the structure of uplink compressed frames. It consists of two rows of slots. The top row shows "Slot # ( $N_{first} - 1$ )" on the left, a "transmission gap" in the middle (indicated by five dots), and "Slot # ( $N_{last} + 1$ )" on the right. The bottom row shows the internal structure of the slots. The slot on the left is divided into four fields: "Pilot", "TFCI", "FBI", and "TPC". The slot on the right is also divided into four fields: "Pilot", "TFCI", "FBI", and "TPC". The "Data" field is shown above the Pilot, TFCI, FBI, and TPC fields in both slots. The transmission gap is indicated by five dots between the two slots. + +Figure 12: Frame structure in uplink compressed transmission diagram showing slot details. + +Figure 12: Frame structure in uplink compressed transmission + +### 4.4.2 Frame structure types in the downlink + +There are two different types of frame structures defined for downlink compressed frames. Type A maximises the transmission gap length and type B is optimised for power control. The frame structure type A or B is set by higher layers independent from the downlink slot format type A or B. + +- With frame structure of type A, the pilot field of the last slot in the transmission gap is transmitted. Transmission is turned off during the rest of the transmission gap (figure 13(a)). In case the length of the pilot field is 2 bits and STTD is used on the radio link, the pilot bits in the last slot of the transmission gap shall be STTD encoded assuming DTX indicators as the two last bits in the Data2 field. +- With frame structure of type B, the TPC field of the first slot in the transmission gap and the pilot field of the last slot in the transmission gap is transmitted. Transmission is turned off during the rest of the transmission gap (figure 13(b)). In case the length of the pilot field is 2 bits and STTD is used on the radio link, the pilot bits in the last slot of the transmission gap shall be STTD encoded assuming DTX indicators as the two last bits of the Data2 field. Similarly, the TPC bits in the first slot of the transmission gap shall be STTD encoded assuming DTX indicators as the two last bits in the Data1 field. + +![Figure 13: Frame structure types in downlink compressed transmission. (a) Frame structure type A shows a sequence of slots. Slot # (N_first - 1) contains Data1, TPC, TFCI, Data2, and PL. This is followed by a transmission gap indicated by dots. Slot # (N_last + 1) contains PL, Data1, TPC, TFCI, Data2, and PL. (b) Frame structure type B shows a similar sequence, but includes a TPC field immediately before the transmission gap dots.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +**(a) Frame structure type A** + +**(b) Frame structure type B** + +Figure 13: Frame structure types in downlink compressed transmission. (a) Frame structure type A shows a sequence of slots. Slot # (N\_first - 1) contains Data1, TPC, TFCI, Data2, and PL. This is followed by a transmission gap indicated by dots. Slot # (N\_last + 1) contains PL, Data1, TPC, TFCI, Data2, and PL. (b) Frame structure type B shows a similar sequence, but includes a TPC field immediately before the transmission gap dots. + +**Figure 13: Frame structure types in downlink compressed transmission** + +#### 4.4.2A Frame structure in the downlink for F-DPCH + +There is only one type of frame structure defined for downlink F-DPCH compressed frames: transmission is turned off during the whole transmission gap i.e. in slots $N_{\text{first}}$ to $N_{\text{last}}$ . + +#### 4.4.2B Frame structure in the downlink for F-TPICH + +There is only one type of frame structure defined for downlink F-TPICH compressed frames: transmission is turned off during the whole transmission gap i.e. in slots $N_{\text{first}}$ to $N_{\text{last}}$ . TPI will not be transmitted in either of the both slots in the case where only one of the two slots carrying the TPI information overlaps with the transmission gap. + +### 4.4.3 Transmission time reduction method + +When in compressed mode, the information normally transmitted during a 10 ms frame is compressed in time. The mechanisms provided for achieving this are reduction of the spreading factor by a factor of two, and higher layer scheduling. In the downlink and the uplink, all methods are supported. The maximum idle length is defined to be 7 slots per one 10 ms frame. The slot formats that are used in compressed frames are listed in [2]. + +In downlink when DL\_DCH\_FET\_Config is configured by higher layers, and in uplink when UL\_DPCH\_10ms\_Mode is configured by higher layers, the same slot format is used in compressed frames and normal frames. + +In case F-DPCH is configured in the downlink, no transmission time reduction method is needed during compressed frames. The same slot format is used in compressed frames and normal frames. + +#### 4.4.3.1 Void + +#### 4.4.3.2 Compressed mode by reducing the spreading factor by 2 + +The spreading factor (SF) can be reduced by 2 during one compressed radio frame to enable the transmission of the information bits in the remaining time slots of the compressed frame. This method is not supported for SF=4. + +On the downlink, UTRAN can also order the UE to use a different scrambling code in a compressed frame than in a non-compressed frame. If the UE is ordered to use a different scrambling code in a compressed frame, then there is a one-to-one mapping between the scrambling code used in the non-compressed frame and the one used in the compressed frame, as described in [3] subclause 5.2.1. + +#### 4.4.3.3 Compressed mode by higher layer scheduling + +Compressed frames can be obtained by higher layer scheduling. Higher layers then set restrictions so that only a subset of the allowed TFCs are used in a compressed frame. The maximum number of bits that will be delivered to the physical layer during the compressed radio frame is then known and a transmission gap can be generated. Note that in the downlink, the TFCI field is expanded on the expense of the data fields and this shall be taken into account by higher layers when setting the restrictions on the TFCs. Compressed mode by higher layer scheduling shall not be used with + +fixed starting positions of the TrCHs in the radio frame. Compressed mode by higher layer scheduling shall not be used when DL\_DCH\_FET\_Config is configured by higher layers. + +#### 4.4.4 Transmission gap position + +Transmission gaps can be placed at different positions as shown in figures 14 and 15 for each purpose such as interfrequency power measurement, acquisition of control channel of other system/carrier, and actual handover operation. + +The restrictions listed below apply to DPCCH/DPCCH2/S-DPCCH/DPDCH in the uplink and DPCH or F-DPCH in the downlink. + +When using single frame method, the transmission gap is located within the compressed frame depending on the transmission gap length (TGL) as shown in figure 14 (1). When using double frame method, the transmission gap is located on the center of two connected frames as shown in figure 14 (2). + +![Figure 14: Transmission gap position. (1) Single-frame method: A diagram showing a single radio frame with 15 slots. A transmission gap is indicated by a double-headed arrow above a set of idle slots. The first slot of the gap is labeled #N_first-1 and the last slot is labeled #N_last+1. The gap length is TGL. The frame starts at slot #0 and ends at slot #14. (2) Double-frame method: A diagram showing two consecutive radio frames. A transmission gap is indicated by a double-headed arrow above the gap between the two frames. The last slot of the first frame is labeled #N_first-1 and the first slot of the second frame is labeled #N_last+1. The gap length is TGL. The first frame starts at slot #0 and ends at slot #14. The second frame also starts at slot #0 and ends at slot #14.](077f85b82901283b4657fd2b45fc0294_img.jpg) + +Figure 14: Transmission gap position. (1) Single-frame method: A diagram showing a single radio frame with 15 slots. A transmission gap is indicated by a double-headed arrow above a set of idle slots. The first slot of the gap is labeled #N\_first-1 and the last slot is labeled #N\_last+1. The gap length is TGL. The frame starts at slot #0 and ends at slot #14. (2) Double-frame method: A diagram showing two consecutive radio frames. A transmission gap is indicated by a double-headed arrow above the gap between the two frames. The last slot of the first frame is labeled #N\_first-1 and the first slot of the second frame is labeled #N\_last+1. The gap length is TGL. The first frame starts at slot #0 and ends at slot #14. The second frame also starts at slot #0 and ends at slot #14. + +**Figure 14: Transmission gap position** + +Parameters of the transmission gap positions are calculated as follows. + +TGL is the number of consecutive idle slots during the compressed mode transmission gap: + +$$\text{TGL} = 3, 4, 5, 7, 10, 14$$ + +$N_{\text{first}}$ specifies the starting slot of the consecutive idle slots, + +$$N_{\text{first}} = 0, 1, 2, 3, \dots, 14.$$ + +$N_{\text{last}}$ shows the number of the final idle slot and is calculated as follows; + +$$\text{If } N_{\text{first}} + \text{TGL} \leq 15, \text{ then } N_{\text{last}} = N_{\text{first}} + \text{TGL} - 1 \text{ ( in the same frame ),}$$ + +$$\text{If } N_{\text{first}} + \text{TGL} > 15, \text{ then } N_{\text{last}} = (N_{\text{first}} + \text{TGL} - 1) \bmod 15 \text{ ( in the next frame ).}$$ + +When the transmission gap spans two consecutive radio frames, $N_{\text{first}}$ and TGL must be chosen so that at least 8 slots in each radio frame are transmitted. + +![Figure 15: Transmission gap positions with different Nfirst. The figure shows two methods for determining the transmission gap position within a radio frame. (1) Single-frame method: Three diagrams show a radio frame (14 slots) with a transmission gap of 2 slots. In the first, the gap is at slots 1-2. In the second, it's at slots 5-6. In the third, it's at slots 10-11. (2) Double-frame method: Three diagrams show two consecutive radio frames. The transmission gap (2 slots) is shown starting at the boundary between the first and second frames, then shifting one slot to the right in the second frame, and then one slot further right in the third frame, illustrating how the gap position changes relative to the frame boundary.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +(1) Single-frame method + +(2) Double-frame method + +Figure 15: Transmission gap positions with different Nfirst. The figure shows two methods for determining the transmission gap position within a radio frame. (1) Single-frame method: Three diagrams show a radio frame (14 slots) with a transmission gap of 2 slots. In the first, the gap is at slots 1-2. In the second, it's at slots 5-6. In the third, it's at slots 10-11. (2) Double-frame method: Three diagrams show two consecutive radio frames. The transmission gap (2 slots) is shown starting at the boundary between the first and second frames, then shifting one slot to the right in the second frame, and then one slot further right in the third frame, illustrating how the gap position changes relative to the frame boundary. + +**Figure 15: Transmission gap positions with different Nfirst** + +#### 4.4.5 Transmission gap position for E-DCH + +In the following, the transmission gap position for E-DCH during compressed frames is specified for the case when E-DCH TTI length is 10 ms. Slots that are not idle due to uplink compressed mode are termed "available". + +The parameter $n_{first}$ and $n_{last}$ are used to determine the transmission gap position due to uplink compressed mode in the current radio frame. If the start of the transmission gap is allocated in the current frame $n_{first}=N_{first}$ else $n_{first}=0$ . If the end of a transmission gap is allocated in the current frame $n_{last}=N_{last}$ else $n_{last}=14$ . + +##### 4.4.5.1 E-DPDCH Transmission Gap Position during Initial Transmissions + +If an initial transmission overlaps with a compressed frame the starting slot of the consecutive E-DPDCH idle slots within the E-DCH TTI is $n_{first}$ , and $n_{last}$ is the final idle slot within the 10 ms E-DCH TTI. The number of transmitted slots $n_{txl}$ is given by $n_{txl}=14+n_{first}-n_{last}$ . + +If the initial transmission occurs in a non-compressed uplink frame, $n_{txl}=15$ . + +#### 4.4.5.2 E-DPDCH Transmission Gap Position during Retransmissions + +If the current retransmission occurs in a compressed frame the maximum number of slots available for the retransmission is given by $n_{max}=14+n_{first}-n_{last}$ . Else the maximum number of slots available for the retransmission $n_{max}$ is 15. + +If the initial transmission was compressed and in the retransmission more than $n_{txl}$ slots are available for transmission ( $n_{max}>n_{txl}$ ), the last $n_{dtx}=n_{max}-n_{txl}$ available slots of the E-DPDCH frame are E-DPDCH idle slots. The parameter $n_{txl}$ refers to the number of transmitted slots calculated as defined in 4.4.5.1 for the corresponding initial transmission. + +The E-DPDCH transmission gap in case a retransmission occurs in a compressed frame or a retransmission occurs in a non-compressed frame for which initial transmission was compressed is defined as follows: + +If $n_{max} \leq n_{txl}$ + +E-DPDCH idle slots are slots $n_{first}, n_{first}+1, \dots, n_{last}$ + +Else + +If a retransmission occurs in a compressed frame and $n_{first} < n_{txl}$ + +E-DPDCH idle slots are the slots $n_{first}, n_{first}+1, \dots, n_{last}$ and $15-n_{dtx}, 15-n_{dtx}+1, \dots, 14$ + +Else + +E-DPDCH idle slots are the slots $n_{txl}, n_{txl}+1, \dots, 14$ + +#### 4.4.5.3 E-DPCCH Transmission Gap Position + +If a transmission overlaps with an uplink compressed frame the starting slot of the compressed mode gap within the E-DCH TTI is $n_{first}$ , and $n_{last}$ is the final E-DPCCH idle slot within the 10 ms E-DCH TTI. + +### 4.5 Coding for HS-DSCH + +Data arrives to the coding unit in form of a maximum of one transport block once every transmission time interval. The transmission time interval is 2 ms which is mapped to a radio sub-frame of 3 slots. + +The following coding steps can be identified: + +- add CRC to each transport block (see subclause 4.5.1); +- bit scrambling (see subclause 4.5.1A); +- code block segmentation (see subclause 4.5.2); +- channel coding (see subclause 4.5.3); +- hybrid ARQ (see subclause 4.5.4); +- physical channel segmentation (see subclause 4.5.5); +- interleaving for HS-DSCH (see subclause 4.5.6); +- constellation re-arrangement for 16QAM and 64QAM (see subclause 4.5.7); +- mapping to physical channels (see subclause 4.5.8). + +The coding steps for HS-DSCH are shown in the figure below. + +![Flowchart of the coding chain for HS-DSCH. The process starts with input bits a_im1, a_im2, a_im3, ..., a_imA. It proceeds through CRC attachment, Bit Scrambling, Code block segmentation, Channel Coding, Physical Layer Hybrid-ARQ functionality, Physical channel segmentation, HS-DSCH Interleaving, Constellation re-arrangement for 16QAM and 64QAM, and finally Physical channel mapping to PhCH#1 and PhCH#P.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + + graph TD + In[" $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA}$ "] --> CRC[CRC attachment] + CRC --> B1[" $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB}$ "] + B1 --> BS[Bit Scrambling] + BS --> D1[" $d_{im1}, d_{im2}, d_{im3}, \dots, d_{imB}$ "] + D1 --> CBS[Code block segmentation] + CBS --> O1[" $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK}$ "] + O1 --> CC[Channel Coding] + CC --> C1[" $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE}$ "] + C1 --> PHAF[Physical Layer Hybrid-ARQ functionality] + PHAF --> W1[" $w_1, w_2, w_3, \dots, w_R$ "] + W1 --> PCS[Physical channel segmentation] + PCS --> U1[" $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U}$ "] + U1 --> HI[HS-DSCH Interleaving] + HI --> V1[" $v_{p,1}, v_{p,2}, v_{p,3}, \dots, v_{p,U}$ "] + V1 --> CR[Constellation re-arrangement for 16QAM and 64QAM] + CR --> R1[" $r_{p,1}, r_{p,2}, r_{p,3}, \dots, r_{p,U}$ "] + R1 --> PCM[Physical channel mapping] + PCM --> PhCH1["PhCH#1"] + PCM --> PhCHP["PhCH#P"] + +``` + +Flowchart of the coding chain for HS-DSCH. The process starts with input bits a\_im1, a\_im2, a\_im3, ..., a\_imA. It proceeds through CRC attachment, Bit Scrambling, Code block segmentation, Channel Coding, Physical Layer Hybrid-ARQ functionality, Physical channel segmentation, HS-DSCH Interleaving, Constellation re-arrangement for 16QAM and 64QAM, and finally Physical channel mapping to PhCH#1 and PhCH#P. + +**Figure 16: Coding chain for HS-DSCH** + +In the following the number of transport blocks and the number of transport channels is always one i.e. $m=1$ , $i=1$ . When referencing non HS-DSCH formulae which are used in correspondence with HS-DSCH formulae the convention is used that transport block subscripts may be omitted (e.g. $X_1$ may be written $X$ ). + +#### 4.5.1 CRC attachment for HS-DSCH + +##### 4.5.1.1 CRC attachment method 1 for HS-DSCH + +CRC attachment method 1 for the HS-DSCH transport channel shall be done using the general method described in 4.2.1 above with the following specific parameters. + +The CRC length shall always be $L_1 = 24$ bits. + +#### 4.5.1.2 CRC attachment method 2 for HS-DSCH + +CRC attachment method 2 for the HS-DSCH transport channel shall be done according to the following method. + +From the sequence of bits $a_1, a_2, a_3, \dots, a_A$ , where $A$ is the size of the HS-DSCH transport block, a CRC of length $L_1 = 24$ bits is calculated according to Clause 4.2.1.1 above. This gives a sequence of bits $c_{im1}, c_{im2}, c_{im3}, \dots, c_{im24}$ where + +$$k=1,2,\dots,24$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $a_1, a_2, a_3, \dots, a_A$ to form the sequence of bits $b_1, b_2, b_3, \dots, b_B$ , where $B = A + 24$ , and + +$$b_k = a_k \quad k=1,2,\dots,A$$ + +$$b_k = c_{k-A} \quad k=A+1,\dots,A+8$$ + +$$b_k = (c_{k-A} + x_{ue,k-A-8}) \bmod 2 \quad k=A+9, \dots, A+24$$ + +#### 4.5.1A Bit scrambling for HS-DSCH + +The bits output from the HS-DSCH CRC attachment are scrambled in the bit scrambler. The bits input to the bit scrambler are denoted by $x$ , where $B$ is the number of bits input to the HS-DSCH bit scrambler. The bits after bit scrambling are denoted by $y$ . + +Bit scrambling is defined by the following relation: + +$$k = 1,2,\dots,B$$ + +and results from the following operation: + +$$-15 < \gamma < 1$$ + +$$\gamma = 1$$ + +, + +where , + +$$k = 1,2,\dots,B.$$ + +#### 4.5.2 Code block segmentation for HS-DSCH + +Code block segmentation for the HS-DSCH transport channel shall be done with the general method described in 4.2.2.2 above with the following specific parameters. + +There will be a maximum of one transport block, $i=1$ . The bits $d_{im1}, d_{im2}, d_{im3}, \dots, d_{imB}$ input to the block are mapped to the bits $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iB}$ directly. It follows that $X_1 = B$ . Note that the bits $x$ referenced here refer only to the internals of the code block segmentation function. The output bits from the code block segmentation function are $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK}$ . + +The value of $Z = 5114$ for turbo coding shall be used. + +#### 4.5.3 Channel coding for HS-DSCH + +Channel coding for the HS-DSCH transport channel shall be done with the general method described in 4.2.3 above with the following specific parameters. + +There will be a maximum of one transport block, $i=1$ . The rate 1/3 turbo coding shall be used. + +#### 4.5.4 Hybrid ARQ for HS-DSCH + +The hybrid ARQ functionality matches the number of bits at the output of the channel coder to the total number of bits of the HS-PDSCH set to which the HS-DSCH is mapped. The hybrid ARQ functionality is controlled by the redundancy version (RV) parameters. The exact set of bits at the output of the hybrid ARQ functionality depends on the number of input bits, the number of output bits, and the RV parameters. + +The hybrid ARQ functionality consists of two rate-matching stages and a virtual buffer as shown in the figure below. + +The first rate matching stage matches the number of input bits to the virtual IR buffer, information about which is provided by higher layers. Note that, if the number of input bits does not exceed the virtual IR buffering capability, the first rate-matching stage is transparent. + +The second rate matching stage matches the number of bits after first rate matching stage to the number of physical channel bits available in the HS-PDSCH set in the TTI. + +![Figure 17: HS-DSCH hybrid ARQ functionality diagram. The diagram shows the flow of data from input C (N^TTI) through bit separation into systematic bits, Parity 1 bits, and Parity 2 bits. These bits then pass through the First Rate Matching stage (RM_S, RM_P1_1, RM_P2_1) into the Virtual IR Buffer (N_sys, N_p1, N_p2). From the buffer, they pass through the Second Rate Matching stage (RM_S, RM_P1_2, RM_P2_2) and finally through bit collection to produce the output W (N_data).](677bcb564410628b8b966ad87b394888_img.jpg) + +The diagram illustrates the HS-DSCH hybrid ARQ functionality. It starts with an input $C$ of size $N^{TTI}$ entering a 'bit separation' block. This block outputs three streams: 'Systematic bits', 'Parity 1 bits', and 'Parity 2 bits'. The 'Systematic bits' stream goes directly to the 'Second Rate Matching' stage. The 'Parity 1 bits' and 'Parity 2 bits' streams first pass through the 'First Rate Matching' stage, specifically through blocks $RM\_P1\_1$ and $RM\_P2\_1$ respectively. All three streams then enter the 'Virtual IR Buffer', which stores them as $N_{sys}$ , $N_{p1}$ , and $N_{p2}$ . From the buffer, the streams pass through the 'Second Rate Matching' stage, specifically through blocks $RM\_S$ , $RM\_P1\_2$ , and $RM\_P2\_2$ , resulting in intermediate bit counts $N_{t,sys}$ , $N_{t,p1}$ , and $N_{t,p2}$ . Finally, these streams are combined in a 'bit collection' block to produce the output $W$ with a total size of $N_{data}$ . + +Figure 17: HS-DSCH hybrid ARQ functionality diagram. The diagram shows the flow of data from input C (N^TTI) through bit separation into systematic bits, Parity 1 bits, and Parity 2 bits. These bits then pass through the First Rate Matching stage (RM\_S, RM\_P1\_1, RM\_P2\_1) into the Virtual IR Buffer (N\_sys, N\_p1, N\_p2). From the buffer, they pass through the Second Rate Matching stage (RM\_S, RM\_P1\_2, RM\_P2\_2) and finally through bit collection to produce the output W (N\_data). + +Figure 17: HS-DSCH hybrid ARQ functionality + +#### 4.5.4.1 HARQ bit separation + +The HARQ bit separation function shall be performed in the same way as bit separation for turbo encoded TrCHs with puncturing in 4.2.7.4.1 above. + +#### 4.5.4.2 HARQ First Rate Matching Stage + +HARQ first stage rate matching for the HS-DSCH transport channel shall be done with the general method described in 4.2.7.2.2.3 above with the following specific parameters. + +The maximum number of soft channel bits available in the virtual IR buffer is $N_{IR}$ which is signalled from higher layers for each HARQ process. The number of coded bits in a TTI before rate matching is $N^{TTI}$ this is deduced from information signalled from higher layers and parameters signalled on the HS-SCCH for each TTI. Note that HARQ processing and physical layer storage occurs independently for each HARQ process currently active. + +If $N_{IR}$ is greater than or equal to $N^{TTI}$ (i.e. all coded bits of the corresponding TTI can be stored) the first rate matching stage shall be transparent. This can, for example, be achieved by setting $e_{minus} = 0$ . Note that no repetition is performed. + +If $N_{IR}$ is smaller than $N^{TTI}$ the parity bit streams are punctured as in 4.2.7.2.2.3 above by setting the rate matching parameter where the subscripts $i$ and $l$ refer to transport channel and transport format in the referenced sub-clause. Note the negative value is expected when the rate matching implements puncturing. Bits selected for puncturing which appear as $\delta$ in the algorithm in 4.2.7 above shall be discarded and not counted in the totals for the streams through the virtual IR buffer. + +#### 4.5.4.3 HARQ Second Rate Matching Stage + +HARQ second stage rate matching for the HS-DSCH transport channel shall be done with the general method described in 4.2.7.5 above with the following specific parameters. Bits selected for puncturing which appear as $\delta$ in the algorithm in 4.2.7.5 above shall be discarded and are not counted in the streams towards the bit collection. + +The parameters of the second rate matching stage depend on the value of the RV parameters $s$ and $r$ . The parameter $s$ can take the value 0 or 1 to distinguish between transmissions that prioritise systematic bits ( $s = 1$ ) and non systematic bits ( $s = 0$ ). The parameter $r$ (range 0 to $r_{max}-1$ ) changes the initial error variable $e_{ini}$ in the case of puncturing. In case of repetition both parameters $r$ and $s$ change the initial error variable $e_{ini}$ . The parameters $X_i$ , $e_{plus}$ and $e_{minus}$ are calculated as per table 10 below. + +Denote the number of bits before second rate matching as $N_{sys}$ for the systematic bits, $N_{p1}$ for the parity 1 bits, and $N_{p2}$ for the parity 2 bits, respectively. Denote the number of physical channels used for the HS-DSCH by $P$ . $N_{data}$ is the number of bits available to the HS-DSCH in one TTI and defined as $N_{data}=P \times 3 \times N_{data1}$ , where $N_{data1}$ is defined in [2]. The rate matching parameters are determined as follows. + +For , puncturing is performed in the second rate matching stage. The number of transmitted systematic bits in a transmission is for a transmission that prioritises systematic bits and for a transmission that prioritises non systematic bits. + +For repetition is performed in the second rate matching stage. A similar repetition rate in all bit streams is achieved by setting the number of transmitted systematic bits to . + +The number of parity bits in a transmission is: and for the parity 1 and parity 2 bits, respectively. + +Table 10 below summarizes the resulting parameter choice for the second rate matching stage. + +**Table 10: Parameters for HARQ second rate matching** + +| | $X_i$ | $e_{plus}$ | $e_{minus}$ | +|---------------------|-------|------------|-------------| +| Systematic
RM S | | | | +| Parity 1
RM P1_2 | | | | +| Parity 2
RM P2_2 | | | | + +The rate matching parameter $e_{ini}$ is calculated for each bit stream according to the RV parameters $r$ and $s$ using +in the case of puncturing , i.e., and + +for repetition, i.e., . Where $r \in \{0, 1, \dots, r_{max} - 1\}$ and $r_{max}$ is the total number of redundancy versions allowed by varying $r$ as defined in 4.6.2. Note that $r_{max}$ varies depending on the modulation mode, i.e. for 16QAM and 64QAM, $r_{max} = 2$ and for QPSK $r_{max} = 4$ . + +Note: For the modulo operation the following clarification is used: the value of $(x \bmod y)$ is strictly in the range of 0 to $y-1$ (i.e. $-1 \bmod 10 = 9$ ). + +#### 4.5.4.4 HARQ bit collection + +The HARQ bit collection is achieved using a rectangular interleaver of size $N_{row} \times N_{col}$ . + +The number of rows and columns are determined from: + +for 64QAM, for 16QAM and for QPSK + +where $N_{data}$ is used as defined in 4.5.4.3. + +Data is written into the interleaver column by column, and read out of the interleaver column by column starting from the first column. + +$N_{t,sys}$ is the number of transmitted systematic bits. Intermediate values $N_r$ and $N_c$ are calculated using: + +and . + +If $N_c=0$ and $N_r > 0$ , the systematic bits are written into rows $1 \dots N_r$ . + +Otherwise systematic bits are written into rows $1 \dots N_r+1$ in the first $N_c$ columns and, if $N_r > 0$ , also into rows $1 \dots N_r$ in the remaining $N_{col}-N_c$ columns. + +The remaining space is filled with parity bits. The parity bits are written column wise into the remaining rows of the respective columns. Parity 1 and 2 bits are written in alternating order, starting with a parity 2 bit in the first available column with the lowest index number. + +In the case of 64QAM for each column the bits are read out of the interleaver in the order row 1, row 2, row 3, row 4, row 5, row 6. In the case of 16QAM for each column the bits are read out of the interleaver in the order row 1, row 2, row 3, row 4. In the case of QPSK for each column the bits are read out of the interleaver in the order row 1, row 2. + +#### 4.5.5 Physical channel segmentation for HS-DSCH + +When more than one HS-PDSCH is used, physical channel segmentation divides the bits among the different physical channels. The bits input to the physical channel segmentation are denoted by $w_1, w_2, w_3, \dots, w_R$ , where $R$ is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by $P$ . + +The bits after physical channel segmentation are denoted $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U}$ , where $p$ is PhCH number and $U$ is the number of bits in one radio sub-frame for each HS-PDSCH, i.e. $U = \frac{R}{P}$ . The relation between $w_k$ and $u_{p,k}$ is given below. + +For all modes, some bits of the input flow are mapped to each code until the number of bits on the code is $U$ . + +Bits on first PhCH after physical channel segmentation: + +$$u_{1,k} = w_k \quad k = 1, 2, \dots, U$$ + +Bits on second PhCH after physical channel segmentation: + +$$u_{2,k} = w_{k+U} \quad k = 1, 2, \dots, U$$ + +... + +Bits on the $P^{\text{th}}$ PhCH after physical channel segmentation: + +$$u_{P,k} = w_{k+(P-1) \times U} \quad k = 1, 2, \dots, U$$ + +#### 4.5.6 Interleaving for HS-DSCH + +The interleaving for FDD is done as shown in figure 18 below, separately for each physical channel. The bits input to the block interleaver are denoted by $u_{p,k}$ , where $p$ is PhCH number and $U$ is the number of bits in one TTI for one PhCH. For QPSK $U = 960$ , for 16QAM $U = 1920$ and for 64QAM $U = 2880$ . The basic interleaver is as the 2nd interleaver described in Clause 4.2.11. The interleaver is of fixed size: $R2=32$ rows and $C2=30$ columns. + +![Figure 18: Interleaver structure for HS-DSCH. The diagram shows three parallel interleaver blocks, each labeled 'Interleaver (32x 30)'. The first block takes inputs u_{p,k} (QPSK), u_{p,k}, u_{p,k+1} (16QAM), and u_{p,k}, u_{p,k+1} (64QAM) and produces outputs v_{p,k} (QPSK), v_{p,k}, v_{p,k+1} (16QAM), and v_{p,k}, v_{p,k+1} (64QAM). The second block takes inputs u_{p,k+2}, u_{p,k+3} (16QAM) and u_{p,k+2}, u_{p,k+3} (64QAM) and produces outputs v_{p,k+2}, v_{p,k+3} (16QAM) and v_{p,k+2}, v_{p,k+3} (64QAM). The third block takes inputs u_{p,k+4}, u_{p,k+5} (64QAM) and produces outputs v_{p,k+4}, v_{p,k+5} (64QAM). All three blocks are connected to a common dashed vertical line on the left, indicating they receive data from the same source.](08eda25d46345f5d500bdfbe2d64bc7e_img.jpg) + +Figure 18: Interleaver structure for HS-DSCH. The diagram shows three parallel interleaver blocks, each labeled 'Interleaver (32x 30)'. The first block takes inputs u\_{p,k} (QPSK), u\_{p,k}, u\_{p,k+1} (16QAM), and u\_{p,k}, u\_{p,k+1} (64QAM) and produces outputs v\_{p,k} (QPSK), v\_{p,k}, v\_{p,k+1} (16QAM), and v\_{p,k}, v\_{p,k+1} (64QAM). The second block takes inputs u\_{p,k+2}, u\_{p,k+3} (16QAM) and u\_{p,k+2}, u\_{p,k+3} (64QAM) and produces outputs v\_{p,k+2}, v\_{p,k+3} (16QAM) and v\_{p,k+2}, v\_{p,k+3} (64QAM). The third block takes inputs u\_{p,k+4}, u\_{p,k+5} (64QAM) and produces outputs v\_{p,k+4}, v\_{p,k+5} (64QAM). All three blocks are connected to a common dashed vertical line on the left, indicating they receive data from the same source. + +Figure 18: Interleaver structure for HS-DSCH + +For 16QAM, there are two identical interleavers of the same fixed size $R2 \times C2 = 32 \times 30$ . The output bits from the physical channel segmentation are divided two by two between the interleavers: bits $u_{p,k}$ and $u_{p,k+1}$ go to the first interleaver and bits $u_{p,k+2}$ and $u_{p,k+3}$ go to the second interleaver. Bits are collected two by two from the interleavers: bits $v_{p,k}$ and $v_{p,k+1}$ are obtained from the first interleaver and bits $v_{p,k+2}$ and $v_{p,k+3}$ are obtained from the second interleaver, where $k \bmod 4 = 1$ . + +For 64QAM, there are three identical interleavers of the same fixed size $R2 \times C2 = 32 \times 30$ . The output bits from the physical channel segmentation are divided two by two between the interleavers: bits $u_{p,k}$ and $u_{p,k+1}$ go to the first interleaver, bits $u_{p,k+2}$ and $u_{p,k+3}$ go to the second interleaver and bits $u_{p,k+4}$ and $u_{p,k+5}$ go to the third interleaver. Bits are collected two by two from the interleavers: bits $v_{p,k}$ and $v_{p,k+1}$ are obtained from the first interleaver, bits $v_{p,k+2}$ and $v_{p,k+3}$ are obtained from the second interleaver and bits $v_{p,k+4}$ and $v_{p,k+5}$ are obtained from the third interleaver, where $k \bmod 6 = 1$ . + +#### 4.5.7 Constellation re-arrangement for 16 QAM and 64QAM + +This function only applies to 16QAM and 64QAM modulated bits. In case of QPSK it is transparent. + +Table 11 describes the operations that produce the different rearrangements for 16QAM. The bits of the input sequence are mapped in groups of 4 so that $v_{p,k}$ , $v_{p,k+1}$ , $v_{p,k+2}$ , $v_{p,k+3}$ are used, where $k \bmod 4 = 1$ . The output bit sequences map to the output bits in groups of 4, i.e. $r_{p,k}$ , $r_{p,k+1}$ , $r_{p,k+2}$ , $r_{p,k+3}$ , where $k \bmod 4 = 1$ . + +**Table 11: Constellation re-arrangement for 16QAM** + +| constellation version parameter $b$ | Output bit sequence | Operation | +|-------------------------------------|---------------------|-----------------------------------------------------------------| +| 0 | | None | +| 1 | | Swapping MSBs with LSBs | +| 2 | | Inversion of the logical values of LSBs | +| 3 | | Swapping MSBs with LSBs and inversion of logical values of LSBs | + +Table 11A describes the operations that produce the different rearrangements for 64QAM. The bits of the input sequence are mapped in groups of 6 so that $v_{p,k}$ , $v_{p,k+1}$ , $v_{p,k+2}$ , $v_{p,k+3}$ , $v_{p,k+4}$ , $v_{p,k+5}$ are used, where $k \bmod 6 = 1$ . The output bit sequences map to the output bits in groups of 6, i.e. $r_{p,k}$ , $r_{p,k+1}$ , $r_{p,k+2}$ , $r_{p,k+3}$ , $r_{p,k+4}$ , $r_{p,k+5}$ , where $k \bmod 6 = 1$ . + +**Table 11A: Constellation re-arrangement for 64QAM** + +| constellation version parameter $b$ | Output bit sequence | Operation | +|-------------------------------------|---------------------|-------------------------------------------------------------| +| 0 | | None | +| 1 | | Swapping MSBs and LSBs. Inversion of Middle SBs | +| 2 | | Left circular shift of pair of SBs. Inversion of Middle SBs | +| 3 | | Inversion of Middle SBs | + +#### 4.5.8 Physical channel mapping for HS-DSCH + +The HS-PDSCH is defined in [2]. The bits input to the physical channel mapping are denoted by $r_{p,1}, r_{p,2}, \dots, r_{p,U}$ , where $p$ is the physical channel number and $U$ is the number of bits in one radio sub-frame for one HS-PDSCH. The bits $r_{p,k}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +### 4.6 Coding for HS-SCCH type 1 + +#### 4.6.1 Overview + +HS-SCCH shall be of type 1 when the following two conditions are both true: + +- the UE is not configured in MIMO mode and not in MIMO mode with four transmit antennas, and + +- the conditions for usage of HS-SCCH type 2 are not met. + +In this section, the terms “HS-SCCH” and “HS-SCCH type 1” are used interchangeably. + +The following information is transmitted by means of the HS-SCCH type 1 physical channel. + +- Channelization-code-set information (7 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Transport-block size information (6 bits): $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ +- Hybrid-ARQ process information (3 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}$ +- Redundancy and constellation version (3 bits): $x_{rv,1}, x_{rv,2}, x_{rv,3}$ +- New data indicator (1 bit): $x_{nd,1}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +For an HS-SCCH order, + +- $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}, x_{ms,1}$ shall be set to "11100000" +- $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,4}$ shall be set to "1111" +- $x_{tbs,5}, x_{tbs,6}$ shall be set to $x_{eodt,1}, x_{eodt,2}$ +- $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{rv,1}, x_{rv,2}, x_{rv,3}$ shall be set to $x_{odt,1}, x_{odt,2}, x_{odt,3}, x_{ord,1}, x_{ord,2}, x_{ord,3}$ +- $x_{nd,1}$ is reserved + +where $x_{eodt,1}, x_{eodt,2}, x_{odt,1}, x_{odt,2}, x_{odt,3}, x_{ord,1}, x_{ord,2}, x_{ord,3}$ are defined in subclause 4.6C. + +Figure 19 below illustrates the overall coding chain for HS-SCCH type 1. + +![Figure 19: Coding chain for HS-SCCH type 1. The diagram shows two parallel processing paths for HS-SCCH type 1. Path 1 (left) takes inputs X_ccs and X_ms through a 'mux' block to produce X_1. X_1 is then processed by 'Channel Coding 1' to produce Z_1, which is then processed by 'Rate matching 1' to produce R_1. R_1 is then processed by 'UE specific masking' (which also takes X_ue as input) to produce S_1. Path 2 (right) takes inputs X_tbs, X_hap, X_rv, and X_nd through a 'mux' block to produce X_2. X_2 is then processed by 'UE specific CRC attachment' (which also takes X_ue as input) to produce Y. Y is then processed by 'Channel Coding 2' to produce Z_2, which is then processed by 'Rate matching 2' to produce R_2. Both S_1 and R_2 are then processed by 'Physical channel mapping' to produce the final output HS-SCCH. Additionally, inputs r, s, and b are processed by 'RV coding' to produce X_rv, which is an input to the 'mux' block in Path 2.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +graph TD + X_ccs[X_ccs] --> mux1[mux] + X_ms[X_ms] --> mux1 + mux1 --> X1[X_1] + X1 --> CC1[Channel Coding 1] + CC1 --> Z1[Z_1] + Z1 --> RM1[Rate matching 1] + RM1 --> R1[R_1] + R1 --> USM[UE specific masking] + X_ue1[X_ue] --> USM + USM --> S1[S_1] + r[r] --> RV[RV coding] + s[s] --> RV + b[b] --> RV + RV --> X_rv[X_rv] + X_tbs[X_tbs] --> mux2[mux] + X_hap[X_hap] --> mux2 + X_rv --> mux2 + X_nd[X_nd] --> mux2 + mux2 --> X2[X_2] + X2 --> USCA[UE specific CRC attachment] + X_ue2[X_ue] --> USCA + USCA --> Y[Y] + Y --> CC2[Channel Coding 2] + CC2 --> Z2[Z_2] + Z2 --> RM2[Rate matching 2] + RM2 --> R2[R_2] + S1 --> PCM[Physical channel mapping] + R2 --> PCM + PCM --> HS_SCCH[HS-SCCH] + +``` + +Figure 19: Coding chain for HS-SCCH type 1. The diagram shows two parallel processing paths for HS-SCCH type 1. Path 1 (left) takes inputs X\_ccs and X\_ms through a 'mux' block to produce X\_1. X\_1 is then processed by 'Channel Coding 1' to produce Z\_1, which is then processed by 'Rate matching 1' to produce R\_1. R\_1 is then processed by 'UE specific masking' (which also takes X\_ue as input) to produce S\_1. Path 2 (right) takes inputs X\_tbs, X\_hap, X\_rv, and X\_nd through a 'mux' block to produce X\_2. X\_2 is then processed by 'UE specific CRC attachment' (which also takes X\_ue as input) to produce Y. Y is then processed by 'Channel Coding 2' to produce Z\_2, which is then processed by 'Rate matching 2' to produce R\_2. Both S\_1 and R\_2 are then processed by 'Physical channel mapping' to produce the final output HS-SCCH. Additionally, inputs r, s, and b are processed by 'RV coding' to produce X\_rv, which is an input to the 'mux' block in Path 2. + +Figure 19: Coding chain for HS-SCCH type 1 + +## 4.6.2 HS-SCCH information field mapping + +### 4.6.2.1 Redundancy and constellation version coding + +The redundancy version (RV) parameters $r$ , $s$ and constellation version parameter $b$ are coded jointly to produce the value $X_{rv}$ . $X_{rv}$ is alternatively represented as the sequence $x_{rv,1}, x_{rv,2}, x_{rv,3}$ where $x_{rv,1}$ is the MSB. This is done according to tables 12 and 13 according to the modulation mode used: + +**Table 12: RV coding for 16QAM and 64QAM** + +| Xrv (value) | s | R | b | +|-------------------------------|----------|----------|----------| +| 0 | 1 | 0 | 0 | +| 1 | 0 | 0 | 0 | +| 2 | 1 | 1 | 1 | +| 3 | 0 | 1 | 1 | +| 4 | 1 | 0 | 1 | +| 5 | 1 | 0 | 2 | +| 6 | 1 | 0 | 3 | +| 7 | 1 | 1 | 0 | + +**Table 13: RV coding for QPSK** + +| Xrv (value) | s | r | +|-------------------------------|----------|----------| +| 0 | 1 | 0 | +| 1 | 0 | 0 | +| 2 | 1 | 1 | +| 3 | 0 | 1 | +| 4 | 1 | 2 | +| 5 | 0 | 2 | +| 6 | 1 | 3 | +| 7 | 0 | 3 | + +#### 4.6.2.2 Modulation scheme mapping + +The value of $x_{ms,l}$ is derived from the modulation and given by the following: + +#### 4.6.2.3 Channelization code-set mapping + +The channelization code-set bits $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ are coded according to the following: + +Given P (multi-)codes starting at code O, and given the HS-SCCH number if 64QAM is configured for the UE and $x_{ms,1}=1$ , calculate the information-field using the unsigned binary representation of integers calculated by the expressions, + +for the first three bits (code group indicator) of which $x_{ccs,1}$ is the MSB: + +$$x_{ccs,1}, x_{ccs,2}, x_{ccs,3} = \min(P-1, 15-P)$$ + +If 64QAM is not configured for the UE, or if 64QAM is configured and $x_{ms,1}=0$ , then + +for the last four bits (code offset indicator) of which $x_{ccs,4}$ is the MSB: + +$$x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,7} = |O-1-\lfloor P/8 \rfloor * 15|$$ + +Otherwise (i.e. if 64QAM is configured for the UE and $x_{ms,1}=1$ ), + +P and O shall fulfil $|O-1-\lfloor P/8 \rfloor * 15| \bmod 2 = (\text{HS-SCCH number}) \bmod 2$ , and then + +$$x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,dummy} = |O-1-\lfloor P/8 \rfloor * 15|, \text{ where } x_{ccs,dummy} \text{ is a dummy bit that is not transmitted on HS-SCCH.}$$ + +Furthermore, + +The definitions of P and O are given in [3]. The HS-SCCH number is given by the position in the list of HS-SCCH Channelisation Code Informations signalled by higher layers. The HS-SCCH number is associated with the code offset indicator and code group indicator as described above if 64QAM is configured for the UE and $x_{ms,1}=1$ . + +#### 4.6.2.4 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [13]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +#### 4.6.2.5 HARQ process identifier mapping + +Hybrid-ARQ process information (3 bits) $x_{hap,1}, x_{hap,2}, x_{hap,3}$ is the unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6.2.6 Transport block size index mapping + +Transport-block size information (6 bits) $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ is unsigned binary representation of the transport block size index where $x_{tbs,1}$ is MSB. + +### 4.6.3 Multiplexing of HS-SCCH information + +The channelization-code-set information $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ and modulation-scheme information $x_{ms,1}$ are multiplexed together. This gives a sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,8}$ where + +$$x_{1,i} = x_{ccs,i} \quad i=1,2,\dots,7$$ + +$$x_{1,i} = x_{ms,i-7} \quad i=8$$ + +The transport-block-size information $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, x_{hap,3}$ , redundancy-version information $x_{rv,1}, x_{rv,2}, x_{rv,3}$ and new-data indicator $x_{nd,1}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,13}$ where + +$$x_{2,i} = x_{tbs,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{hap,i-6} \quad i=7,8,9$$ + +$$x_{2,i} = x_{rv,i-9} \quad i=10,11,12$$ + +$$x_{2,i} = x_{nd,i-12} \quad i=13$$ + +### 4.6.4 CRC attachment for HS-SCCH + +From the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,8}, x_{2,1}, x_{2,2}, \dots, x_{2,13}$ a 16 bits CRC is calculated according to Clause 4.2.1.1. This gives a sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,13}$ to form the sequence of bits $y_1, y_2, \dots, y_{29}$ , where + +$$y_i = x_{2,i} \quad i=1,2,\dots,13$$ + +$$y_i = (c_{i-13} + x_{ue,i-13}) \bmod 2 \quad i=14,15,\dots,29$$ + +### 4.6.5 Channel coding for HS-SCCH + +Rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,8}$ . This gives a sequence of bits $z_{1,1}, z_{1,2}, \dots, z_{1,48}$ . + +Rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $y_1, y_2, \dots, y_{29}$ . This gives a sequence of bits $z_{2,1}, z_{2,2}, \dots, z_{2,111}$ . + +Note that the coded sequence lengths result from the termination of K=9 convolutional coding being fully applied. + +## 4.6.6 Rate matching for HS-SCCH + +From the input sequence $z_{1,1}, z_{1,2}, \dots, z_{1,48}$ the bits $z_{1,1}, z_{1,2}, z_{1,4}, z_{1,8}, z_{1,12}, z_{1,16}, z_{1,20}, z_{1,24}, z_{1,28}, z_{1,32}, z_{1,36}, z_{1,40}, z_{1,44}, z_{1,48}$ are punctured to obtain the output sequence $r_{1,1}, r_{1,2}, \dots, r_{1,40}$ . + +From the input sequence $z_{2,1}, z_{2,2}, \dots, z_{2,111}$ the bits $z_{2,1}, z_{2,2}, z_{2,3}, z_{2,4}, z_{2,5}, z_{2,6}, z_{2,7}, z_{2,8}, z_{2,12}, z_{2,14}, z_{2,15}, z_{2,24}, z_{2,42}, z_{2,48}, z_{2,54}, z_{2,57}, z_{2,60}, z_{2,66}, z_{2,69}, z_{2,96}, z_{2,99}, z_{2,101}, z_{2,102}, z_{2,104}, z_{2,105}, z_{2,106}, z_{2,107}, z_{2,108}, z_{2,109}, z_{2,110}, z_{2,111}$ are punctured to obtain the output sequence $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ . + +## 4.6.7 UE specific masking for HS-SCCH + +The rate matched bits $r_{1,1}, r_{1,2}, \dots, r_{1,40}$ shall be masked in an UE specific way using the UE identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ to produce the bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ . + +Intermediate code word bits $b_i, i=1,2,\dots,48$ , are defined by encoding the UE identity bits using the rate $\frac{1}{2}$ convolutional coding described in Clause 4.2.3.1. Eight bits out of the resulting 48 convolutionally encoded bits are punctured using the rate matching rule of Clause 4.6.6 for the HS-SCCH part 1 sequence, that is, the intermediate code word bits $b_1, b_2, b_4, b_8, b_{12}, b_{16}, b_{20}, b_{24}$ are punctured to obtain the 40 bit UE specific scrambling sequence $c_1, c_2, \dots, c_{40}$ . + +The mask output bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ are calculated as follows: + +$$s_{1,k} = (r_{1,k} + c_k) \bmod 2 \quad \text{for } k = 1, 2, \dots, 40$$ + +## 4.6.8 Physical channel mapping for HS-SCCH + +The HS-SCCH sub-frame is described in [2]. + +The sequence of bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ is mapped to the first slot of the HS-SCCH sub frame. The bits $s_{1,k}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +The sequence of bits $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ is mapped to the second and third slot of the HS-SCCH sub frame. The bits $r_{2,k}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +## 4.6A Coding for HS-SCCH type 2 + +### 4.6A.1 Overview + +HS-SCCH type 2 is used for HS-SCCH-less operation. HS-SCCH type 2 is not used when the UE is configured in MIMO mode or in MIMO mode with four transmit antennas. During second and third transmission, the following information is transmitted by means of the HS-SCCH type 2 physical channel. + +- Channelization-code-set information (7 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Special Information type (6 bits): $x_{type,1}, x_{type,2}, \dots, x_{type,6}$ +- Special Information (7 bits): $x_{info,1}, x_{info,2}, x_{info,3}, x_{info,4}, x_{info,5}, x_{info,6}, x_{info,7}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +Figure 19A below illustrates the overall coding chain for HS-SCCH type 2. + +![Figure 19A: Coding chain for HS-SCCH type 2. The diagram shows two parallel processing paths. Path 1: Inputs X_ccs and X_mts are multiplexed (mux) to produce X_1. X_1 is then processed by Channel Coding 1 to produce Z_1, which is then processed by Rate matching 1 to produce R_1. R_1 is then processed by UE specific masking (with input X_ue) to produce S_1. Path 2: Inputs X_type and X_info are multiplexed (mux) to produce X_2. X_2 is then processed by UE specific CRC attachment (with input X_ue) to produce Y. Y is then processed by Channel Coding 2 to produce Z_2, which is then processed by Rate matching 2 to produce R_2. Both S_1 and R_2 are then processed by Physical channel mapping to produce the final output HS-SCCH.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +graph TD + X_ccs[X_ccs] --> mux1[mux] + X_mts[X_mts] --> mux1 + mux1 -- X_1 --> CC1[Channel Coding 1] + CC1 -- Z_1 --> RM1[Rate matching 1] + RM1 -- R_1 --> UM[UE specific masking] + X_ue1[X_ue] --> UM + UM -- S_1 --> PCM[Physical channel mapping] + X_type[X_type] --> mux2[mux] + X_info[X_info] --> mux2 + mux2 -- X_2 --> UCA[UE specific CRC attachment] + X_ue2[X_ue] --> UCA + UCA -- Y --> CC2[Channel Coding 2] + CC2 -- Z_2 --> RM2[Rate matching 2] + RM2 -- R_2 --> PCM + PCM --> HS_SCCH[HS-SCCH] + +``` + +Figure 19A: Coding chain for HS-SCCH type 2. The diagram shows two parallel processing paths. Path 1: Inputs X\_ccs and X\_mts are multiplexed (mux) to produce X\_1. X\_1 is then processed by Channel Coding 1 to produce Z\_1, which is then processed by Rate matching 1 to produce R\_1. R\_1 is then processed by UE specific masking (with input X\_ue) to produce S\_1. Path 2: Inputs X\_type and X\_info are multiplexed (mux) to produce X\_2. X\_2 is then processed by UE specific CRC attachment (with input X\_ue) to produce Y. Y is then processed by Channel Coding 2 to produce Z\_2, which is then processed by Rate matching 2 to produce R\_2. Both S\_1 and R\_2 are then processed by Physical channel mapping to produce the final output HS-SCCH. + +Figure 19A: Coding chain for HS-SCCH type 2 + +## 4.6A.2 HS-SCCH Type 2 information field mapping + +### 4.6A.2.1 The first transmission + +When HS-SCCH\_less\_mode=1 for a UE (as defined in [4]), the first transmission of an HS-DSCH transport block using CRC attachment method 2 shall be sent without an associated HS-SCCH. In this case, the UE shall use the following signalling values in order to attempt to decode the transport block: + +- | | | +|----------------------------------------|----------------------------------------------------------------| +| - Channelization-code-set information: | Configured by higher layers | +| - Modulation scheme information: | QPSK | +| - Transport-block size information: | Each of four possible sizes configured by higher layers | + +- Redundancy and constellation version: $X_{rv} = 0$ (see 4.6.2.1) +- UE identity: *Configured by higher layers* + +#### 4.6A.2.2 The second and the third transmissions + +For HS-SCCH\_less\_mode=1 there are at maximum 3 transmissions for a HS-DSCH transport block using CRC attachment method 2. The 2nd and 3rd transmissions of a transport block that was sent without an associated HS-SCCH in the first transmission, as described in subclause 4.6A.2.1.1, are associated with an HS-SCCH of type 2. + +##### 4.6A.2.2.1 Special Information mapping + +The Special Information type $x_{type,1}, x_{type,2}, \dots, x_{type,6}$ shall be set to "111110" to indicate HS-SCCH less operation. + +The Special Information bits $x_{info,1}, x_{info,2}, \dots, x_{info,7}$ are comprised of: + +- Transport-block size information (2 bits): $x_{info,1}, x_{info,2} = x_{tbs,1}, x_{tbs,2}$ +- Pointer to the previous transmission (3 bits): $x_{info,3}, x_{info,4}, x_{info,5} = x_{ptr,1}, x_{ptr,2}, x_{ptr,3}$ +- Second or third transmission (1 bit): $x_{info,6} = x_{sec,1}$ +- Reserved (1 bit): $x_{info,7} = x_{res,1}$ + +###### 4.6A.2.2.1.1 Transport-block size information mapping + +The Transport-block size information (2 bits) $x_{tbs,1}, x_{tbs,2}$ is the unsigned binary representation of a reference to one of the four Transport-block sizes and the associated number of HS-PDSCH codes for the first transmission configured by higher layers. + +| $X_{tbs,1}, X_{tbs,2}$ | Entry in "Transport Block size list" as signalled in the HS-SCCH-less Information of HS_SCCH_LESS_PARAMS [13] | +|------------------------|---------------------------------------------------------------------------------------------------------------| +| "00" | 1 st entry | +| "01" | 2 nd entry | +| "10" | 3 rd entry | +| "11" | 4 th entry | + +###### 4.6A.2.2.1.2 Pointer to the previous transmission mapping + +Pointer to the previous transmission (3 bits) $x_{ptr,1}, x_{ptr,2}, x_{ptr,3}$ is the unsigned binary representation of $s$ , such that the previous transmission of the same transport block started (6+s) subframes before the start of this transmission. + +###### 4.6A.2.2.1.3 Second or third transmission mapping + +Second or Third transmission (1 bit) indicates whether this is the second or third transmission. + +If $x_{sec,1} = "0"$ , this is a second transmission. + +If $x_{sec,1} = "1"$ , this is a third transmission. + +##### 4.6A.2.2.2 Redundancy and Constellation Version mapping + +The redundancy version $X_{rv}$ for the second and third transmissions shall be equal to 3 and 4 respectively, as defined in Table 13. + +#### 4.6A.2.2.3 Modulation scheme mapping + +The value of $x_{ms,1}$ shall be set to "0" (QPSK). + +#### 4.6A.2.2.4 Channelization code-set mapping + +The channelization code-set bits $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ are coded as per clause 4.6.2.3 where the value of P shall be set to either 1 or 2. + +#### 4.6A.2.2.5 UE identity mapping + +The UE identity is encoded as per clause 4.6.2.4. + +### 4.6A.3 Multiplexing of HS-SCCH Type 2 information + +The channelization-code-set information $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ and modulation-scheme information $x_{ms,1}$ are multiplexed together. This gives a sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,8}$ where + +$$x_{1,i} = x_{ccs,i} \quad i=1,2,\dots,7$$ + +$$x_{1,i} = x_{ms,i-7} \quad i=8$$ + +The Special Information type $x_{type,1}, x_{type,2}, \dots, x_{type,6}$ , and Special Information $x_{info,1}, x_{info,2}, x_{info,3}, x_{info,4}, x_{info,5}, x_{info,6}, x_{info,7}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,13}$ where + +$$x_{2,i} = x_{type,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{info,i-6} \quad i=7,8,\dots,13$$ + +### 4.6A.4 CRC attachment for HS-SCCH Type 2 + +The sequence of bits $y_1, y_2, \dots, y_{29}$ , is calculated according to Clause 4.6.4. + +### 4.6A.5 Channel coding for HS-SCCH Type 2 + +Channel coding is performed according to Clause 4.6.5. + +### 4.6A.6 Rate matching for HS-SCCH Type 2 + +Rate matching is performed according to Clause 4.6.6. + +### 4.6A.7 UE specific masking for HS-SCCH Type 2 + +The mask output bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ are calculated according to Clause 4.6.7. + +### 4.6A.8 Physical channel mapping for HS-SCCH Type 2 + +Physical channel mapping is performed according to Clause 4.6.8. + +## 4.6B Coding for HS-SCCH type 3 + +### 4.6B.1 Overview + +HS-SCCH type 3 is used when the UE is configured in MIMO mode. If one transport block is transmitted on the associated HS-PDSCH(s) or an HS-SCCH order is transmitted, the following information is transmitted by means of the HS-SCCH type 3 physical channel: + +- | | | +|--------------------------------------------------------------------------|------------------------------------------------| +| - Channelization-code-set information (7 bits): | $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ | +| - Modulation scheme and number of transport blocks information (3 bits): | $x_{ms,1}, x_{ms,2}, x_{ms,3}$ | +| - Precoding weight information (2 bits): | $x_{pwipb,1}, x_{pwipb,2}$ | +| - Transport-block size information (6 bits): | $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ | + +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ +- Redundancy and constellation version (2 bits): $x_{rvpb,1}, x_{rvpb,2}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +For an HS-SCCH order, + +- $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}, x_{ms,1}, x_{ms,2}, x_{ms,3}, x_{pwipb,1}, x_{pwipb,2}$ shall be set to "111000000000" +- $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,4}$ shall be set to "1111" +- $x_{tbspb,5}, x_{tbspb,6}$ shall be set to $x_{eodt,1}, x_{eodt,2}$ +- $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}, x_{rvpb,1}, x_{rvpb,2}$ shall be set to $x_{odt,1}, x_{odt,2}, x_{odt,3}, x_{ord,1}, x_{ord,2}, x_{ord,3}$ + +where $x_{eodt,1}, x_{eodt,2}, x_{odt,1}, x_{odt,2}, x_{odt,3}, x_{ord,1}, x_{ord,2}, x_{ord,3}$ are defined in subclause 4.6C. + +If two transport blocks are transmitted on the associated HS-PDSCHs (not applicable when single-stream restriction is configured), the following information is transmitted by means of the HS-SCCH type 3 physical channel: + +- Channelization-code-set information (7 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ +- Modulation scheme and number of transport blocks information (3 bits): $x_{ms,1}, x_{ms,2}, x_{ms,3}$ +- Precoding weight information for the primary transport block (2 bits): $x_{pwipb,1}, x_{pwipb,2}$ +- Transport-block size information for the primary transport block (6 bits): $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ +- Transport-block size information for the secondary transport block (6 bits): $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ +- Redundancy and constellation version for the primary transport block (2 bits): $x_{rvpb,1}, x_{rvpb,2}$ +- Redundancy and constellation version for the secondary transport block (2 bits): $x_{rvsb,1}, x_{rvsb,2}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +Figure 19B below illustrates the overall coding chain for HS-SCCH type 3. Note that some information shown is not present if only one transport block is transmitted on the associated HS-PDSCH(s). + +![Figure 19B: Coding chain for HS-SCCH type 3. The diagram shows two parallel processing paths for transport blocks. Path 1 (left) takes inputs X_ocs, X_ms, and X_pwipb through a 'mux' block to produce X_1. X_1 is then processed by 'Channel Coding 1' to produce Z_1, which is then processed by 'Rate matching 1' to produce R_1. R_1 is then processed by 'UE specific masking' (with input X_ue) to produce S_1. Path 2 (right) takes inputs X_tbspb, X_tbsb, X_hap, X_rvpb, and X_rvsb through a 'mux' block to produce X_2. X_2 is then processed by 'UE specific CRC attachment' (with input X_ue) to produce Y. Y is then processed by 'Channel Coding 2' to produce Z_2, which is then processed by 'Rate matching 2' to produce R_2. Both S_1 and R_2 are then processed by 'Physical channel mapping' to produce the final output HS-SCCH. Additionally, RV parameters r, s, and b are input to two 'RV coding' blocks. The first 'RV coding' block produces X_rvpb, which is an input to the second 'mux' block. The second 'RV coding' block produces X_rvsb, which is also an input to the second 'mux' block.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Figure 19B: Coding chain for HS-SCCH type 3. The diagram shows two parallel processing paths for transport blocks. Path 1 (left) takes inputs X\_ocs, X\_ms, and X\_pwipb through a 'mux' block to produce X\_1. X\_1 is then processed by 'Channel Coding 1' to produce Z\_1, which is then processed by 'Rate matching 1' to produce R\_1. R\_1 is then processed by 'UE specific masking' (with input X\_ue) to produce S\_1. Path 2 (right) takes inputs X\_tbspb, X\_tbsb, X\_hap, X\_rvpb, and X\_rvsb through a 'mux' block to produce X\_2. X\_2 is then processed by 'UE specific CRC attachment' (with input X\_ue) to produce Y. Y is then processed by 'Channel Coding 2' to produce Z\_2, which is then processed by 'Rate matching 2' to produce R\_2. Both S\_1 and R\_2 are then processed by 'Physical channel mapping' to produce the final output HS-SCCH. Additionally, RV parameters r, s, and b are input to two 'RV coding' blocks. The first 'RV coding' block produces X\_rvpb, which is an input to the second 'mux' block. The second 'RV coding' block produces X\_rvsb, which is also an input to the second 'mux' block. + +Figure 19B: Coding chain for HS-SCCH type 3 + +## 4.6B.2 HS-SCCH type 3 information field mapping + +### 4.6B.2.1 Redundancy and constellation version coding + +For each of the primary transport block and a secondary transport block if two transport blocks are transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r$ , $s$ and constellation version parameter $b$ are coded jointly to produce the values $X_{rvpb}$ and $X_{rvsb}$ respectively. The transmitted sequences $x_{rvpb,1}$ , $x_{rvpb,2}$ and $x_{rvsb,1}$ , $x_{rvsb,2}$ are the binary representations of $X_{rvpb}$ and $X_{rvsb}$ , respectively, where $x_{rvpb,1}$ and $x_{rvsb,1}$ are the MSBs. + +For the primary transport block if only one transport block is transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r$ , $s$ and constellation version parameter $b$ are coded jointly to produce the value $X_{rvpb}$ . The transmitted sequence $x_{rvpb,1}$ , $x_{rvpb,2}$ is the binary representation of $X_{rvpb}$ , where $x_{rvpb,1}$ is the MSB. + +Joint coding of parameters $r$ , $s$ and constellation version parameter $b$ is done according to tables 13A and 13B according to the modulation mode used. If $X_{rvpb} = 0$ or $X_{rvsb} = 0$ , the UE shall treat the corresponding transport block as an initial transmission. + +**Table 13A: RV coding for 16QAM and 64QAM for HS-SCCH type 3** + +| $X_{rvpb}$ or
$X_{rvsb}$
(value) | $N_{sys} / N_{data} < 1/2$ | | | $N_{sys} / N_{data} \geq 1/2$ | | | +|----------------------------------------|----------------------------|-----|-----|-------------------------------|-----|-----| +| | $s$ | $r$ | $b$ | $s$ | $r$ | $b$ | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | +| 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 2 | 1 | 0 | 2 | 0 | 0 | 0 | +| 3 | 1 | 0 | 3 | 1 | 0 | 2 | + +**Table 13B: RV coding for QPSK for HS-SCCH type 3** + +| $X_{rvpb}$ or
$X_{rvsb}$
(value) | $N_{sys} / N_{data} < 1/2$ | | $N_{sys} / N_{data} \geq 1/2$ | | +|----------------------------------------|----------------------------|-----|-------------------------------|-----| +| | $s$ | $r$ | $s$ | $r$ | +| 0 | 1 | 0 | 1 | 0 | +| 1 | 1 | 1 | 0 | 1 | +| 2 | 1 | 2 | 0 | 3 | +| 3 | 1 | 3 | 1 | 2 | + +#### 4.6B.2.2 Modulation scheme and number of transport blocks mapping + +The number of transport blocks transmitted on the associated HS-PDSCH(s) and the modulation scheme information are jointly coded as shown in Table 14: + +**Table 14: Mapping of $x_{ms}$** + +| $x_{ms,1}$ , $x_{ms,2}$ ,
$x_{ms,3}$ | Modulation for
primary
transport block | Modulation for
secondary
transport block | Number of transport
blocks | +|-----------------------------------------|----------------------------------------------|------------------------------------------------|-------------------------------| +| 111 | 16QAM | 16QAM | 2 | +| 110 | 16QAM | QPSK | 2 | +| 101 | 64QAM | Indicated by
$x_{ccs,7}$ | Indicated by $x_{ccs,7}$ | +| 100 | 16QAM | n/a | 1 | +| 011 | QPSK | QPSK | 2 | +| 010 | 64QAM | 64QAM | 2 | +| 001 | 64QAM | 16QAM | 2 | +| 000 | QPSK | n/a | 1 | + +In case $x_{ms,1}$ , $x_{ms,2}$ , $x_{ms,3}$ equals “101” $x_{ccs,7}$ is used as an extra bit in modulation scheme information. + +#### 4.6B.2.3 Channelization code-set mapping + +The channelization code-set bits $x_{ccs,1}$ , $x_{ccs,2}$ , ..., $x_{ccs,7}$ are coded according to the following: + +Given $P$ (multi-)codes starting at code $O$ , and given the HS-SCCH number if 64QAM is configured for the UE and $x_{ms,1}$ , $x_{ms,2}$ , $x_{ms,3}$ is equal to “101”, calculate the information-field using the unsigned binary representation of integers calculated by the expressions, + +for the first three bits (code group indicator) of which $x_{ccs,1}$ is the MSB: + +$$x_{ccs,1}, x_{ccs,2}, x_{ccs,3} = \min(P-1, 15-P)$$ + +If 64QAM is not configured for the UE, or if 64QAM is configured and $x_{ms,1}$ , $x_{ms,2}$ , $x_{ms,3}$ is not equal to “101”, then + +for the last four bits (code offset indicator) of which $x_{ccs,4}$ is the MSB: + +$$x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,7} = |O-1-\lfloor P/8 \rfloor * 15|$$ + +Otherwise (i.e. if 64QAM is configured for the UE and $x_{ms,1}, x_{ms,2}, x_{ms,3}$ is equal to “101”), + +$P$ and $O$ shall fulfil $|O-1-\lfloor P/8 \rfloor * 15| \bmod 2 = (\text{HS-SCCH number}) \bmod 2$ , and then + +$$x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,dummy} = |O-1-\lfloor P/8 \rfloor * 15|, \text{ where } x_{ccs,dummy} \text{ is a dummy bit that is not transmitted on HS-SCCH.}$$ + +Furthermore, + +$$x_{ccs,7} = 0 \text{ if the modulation for the secondary transport block is QPSK, and}$$ + +$$x_{ccs,7} = 1 \text{ if the number of transport blocks} = 1.$$ + +The definitions of $P$ and $O$ are given in [3]. The HS-SCCH number is given by the position in the list of HS-SCCH Channelisation Code Informations signalled by higher layers. The HS-SCCH number is associated with the code offset indicator and code group indicator as described above if 64QAM is configured for the UE and $x_{ms,1}, x_{ms,2}, x_{ms,3}$ is equal to “101”. + +If two transport blocks are transmitted on the associated HS-PDSCH(s), the same set of channelization codes shall be used for both transport blocks. + +#### 4.6B.2.4 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [13]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +#### 4.6B.2.5 HARQ process identifier mapping + +If two transport blocks are transmitted on the associated HS-PDSCH(s), the mapping relationship between the hybrid-ARQ processes and the transport blocks is such that when the HARQ-process with identifier $HAP_{pb}$ is mapped to the primary transport block, the HARQ-process with the identifier given by $HAP_{pb} \oplus N_{proc}$ shall be mapped to the secondary transport block, where $N_{proc}$ is the number of HARQ processes configured by higher layers. The combination of HARQ-processes is indicated by the hybrid-ARQ process information (4 bits) $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ which are the unsigned binary representation of $HAP_{pb}$ where $x_{hap,1}$ is MSB. + +If only one transport block is transmitted on the associated HS-PDSCH(s), the above mapping is ignored and the hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ is the unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6B.2.6 Transport block size index mapping + +The transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is the unsigned binary representation of the transport block size index for the primary transport block, where $x_{tbspb,1}$ is the MSB. + +If two transport blocks are transmitted on the associated HS-PDSCH(s), the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is the unsigned binary representation of the transport block size index for the secondary transport block, where $x_{tbssb,1}$ is the MSB. + +#### 4.6B.2.7 Precoding Weight Information mapping + +The precoding weight information for the primary transport block $x_{pwipb,1}, x_{pwipb,2}$ is derived from the precoding weight factor $w_2$ as defined in [4], according to Table 14A. + +**Table 14A: Mapping of precoding weight information for primary transport block** + +| $w_2$ | $x_{pwipb,1}, x_{pwipb,2}$ | +|-------|----------------------------| +| | 00 | +| | 01 | +| | 10 | +| | 11 | + +### 4.6B.3 Multiplexing of HS-SCCH type 3 information + +The channelization-code-set information $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ , modulation-scheme and number of transport blocks information $x_{ms,1}, x_{ms,2}, x_{ms,3}$ and precoding weight information $x_{pwipb,1}, x_{pwipb,2}$ are multiplexed together. This gives a sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,12}$ , where + +$$x_{1,i} = x_{ccs,i} \quad i=1,2,\dots,7$$ + +$$x_{1,i} = x_{ms,i-7} \quad i=8,9,10$$ + +$$x_{1,i} = x_{pwipb,i-10} \quad i=11,12$$ + +If one transport block is transmitted on the associated HS-PDSCH(s), the transport-block-size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ and redundancy-version information $x_{rvpb,1}, x_{rvpb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,12}$ where + +$$x_{2,i} = x_{tbs,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{hap,i-6} \quad i=7,8,\dots,10$$ + +$$x_{2,i} = x_{rv,i-10} \quad i=11,12$$ + +If two transport blocks are transmitted on the associated HS-PDSCHs, the transport-block-size information for the primary transport block $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , transport-block-size information for the secondary transport block $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ , redundancy-version information for the primary transport block $x_{rvpb,1}, x_{rvpb,2}$ , and redundancy-version information for the secondary transport block $x_{rvsb,1}, x_{rvsb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ where + +$$x_{2,i} = x_{tbspb,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{tbssb,i-6} \quad i=7,8,\dots,12$$ + +$$x_{2,i} = x_{hap,i-12} \quad i=13,14,\dots,16$$ + +$$x_{2,i} = x_{rvpb,i-16} \quad i=17,18$$ + +$$x_{2,i} = x_{rvsb,i-18} \quad i=19,20$$ + +### 4.6B.4 CRC attachment for HS-SCCH type 3 + +If one transport block is transmitted on the associated HS-PDSCH(s), from the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,12}, x_{2,1}, x_{2,2}, \dots, x_{2,12}$ a 16-bit CRC is calculated according to Clause 4.2.1.1. This gives a sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,12}$ to form the sequence of bits $y_1, y_2, \dots, y_{28}$ , where + +$$y_i = x_{2,i} \quad i=1,2,\dots,12$$ + +$$y_i = (c_{i-12} + x_{ue,i-12}) \bmod 2 \quad i=13,14,\dots,28$$ + +If two transport blocks are transmitted on the associated HS-PDSCHs, from the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,12}, x_{2,1}, x_{2,2}, \dots, x_{2,20}$ a 16-bit CRC is calculated according to Clause 4.2.1.1. This gives a sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ to form the sequence of bits $y_1, y_2, \dots, y_{36}$ , where + +$$y_i = x_{2,i} \quad i=1,2,\dots,20$$ + +$$y_i = (c_{i-20} + x_{ue,i-20}) \bmod 2 \quad i=21,22,\dots,36$$ + +#### 4.6B.5 Channel coding for HS-SCCH type 3 + +Rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,12}$ . This gives a sequence of bits $z_{1,1}, z_{1,2}, \dots, z_{1,60}$ . + +If one transport block is transmitted on the associated HS-PDSCH(s), rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $y_1, y_2, \dots, y_{28}$ . This gives a sequence of bits $z_{2,1}, z_{2,2}, \dots, z_{2,108}$ . + +If two transport blocks are transmitted on the associated HS-PDSCHs, rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $y_1, y_2, \dots, y_{36}$ . This gives a sequence of bits $z_{2,1}, z_{2,2}, \dots, z_{2,132}$ . + +Note that the coded sequence lengths result from the termination of K=9 convolutional coding being fully applied. + +#### 4.6B.6 Rate matching for HS-SCCH type 3 + +From the input sequence $z_{1,1}, z_{1,2}, \dots, z_{1,60}$ the bits $z_{1,1}, z_{1,2}, z_{1,4}, z_{1,6}, z_{1,8}, z_{1,12}, z_{1,15}, z_{1,18}, z_{1,21}, z_{1,24}, z_{1,37}, z_{1,40}, z_{1,43}, z_{1,46}, z_{1,49}, z_{1,53}, z_{1,55}, z_{1,57}, z_{1,59}, z_{1,60}$ are punctured to obtain the output sequence $r_{1,1}, r_{1,2}, \dots, r_{1,40}$ . + +If one transport block is transmitted on the associated HS-PDSCH(s), from the input sequence $z_{2,1}, z_{2,2}, \dots, z_{2,108}$ the bits $z_{2,1}, z_{2,2}, z_{2,3}, z_{2,4}, z_{2,5}, z_{2,6}, z_{2,7}, z_{2,8}, z_{2,12}, z_{2,14}, z_{2,15}, z_{2,24}, z_{2,42}, z_{2,48}, z_{2,63}, z_{2,66}, z_{2,93}, z_{2,96}, z_{2,98}, z_{2,99}, z_{2,101}, z_{2,102}, z_{2,103}, z_{2,104}, z_{2,105}, z_{2,106}, z_{2,107}, z_{2,108}$ are punctured to obtain the output sequence $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ . + +If two transport blocks are transmitted on the associated HS-PDSCHs, from the input sequence $z_{2,1}, z_{2,2}, \dots, z_{2,132}$ the bits $z_{2,1}, z_{2,2}, z_{2,3}, z_{2,4}, z_{2,5}, z_{2,6}, z_{2,7}, z_{2,8}, z_{2,10}, z_{2,11}, z_{2,13}, z_{2,14}, z_{2,16}, z_{2,19}, z_{2,22}, z_{2,25}, z_{2,28}, z_{2,31}, z_{2,34}, z_{2,37}, z_{2,40}, z_{2,43}, z_{2,46}, z_{2,49}, z_{2,55}, z_{2,61}, z_{2,72}, z_{2,78}, z_{2,84}, z_{2,87}, z_{2,90}, z_{2,93}, z_{2,96}, z_{2,99}, z_{2,102}, z_{2,105}, z_{2,108}, z_{2,111}, z_{2,114}, z_{2,117}, z_{2,119}, z_{2,120}, z_{2,122}, z_{2,123}, z_{2,125}, z_{2,126}, z_{2,127}, z_{2,128}, z_{2,129}, z_{2,130}, z_{2,131}, z_{2,132}$ are punctured to obtain the output sequence $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ . + +#### 4.6B.7 UE specific masking for HS-SCCH type 3 + +The output bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ are calculated as described in subclause 4.6.7. + +#### 4.6B.8 Physical channel mapping for HS-SCCH type 3 + +The HS-SCCH sub-frame is described in [2]. The physical channel mapping is carried out as described in subclause 4.6.8. + +### 4.6C Coding for HS-SCCH orders + +#### 4.6C.1 Overview + +HS-SCCH orders are commands sent to the UE using HS-SCCH. No HS-PDSCH is associated with HS-SCCH orders. + +The following information is transmitted by means of the HS-SCCH order physical channel. + +- | | | +|-------------------------------|----------------------------------------| +| - Extended order type (2bits) | $x_{eodt,1}, x_{eodt,2}$ | +| - Order type (3 bits): | $x_{odt,1}, x_{odt,2}, x_{odt,3}$ | +| - Order (3 bits): | $x_{ord,1}, x_{ord,2}, x_{ord,3}$ | +| - UE identity (16 bits): | $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ | + +The coding for HS-SCCH orders is specified in subclause 4.6.1 for a cell where the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas or if the UE is in CELL\_FACH state and in subclause 4.6B.1 for a cell where the UE is configured in MIMO mode, in subclause 4.6D.1 for a cell where the UE is configured in MIMO mode with four transmit antennas with the exception of HS-DSCH serving cell change order, which is always transmitted using HS-SCCH type 1 specified in subclause 4.6.1. + +## 4.6C.2 HS-SCCH Order information field mapping in the CELL\_DCH state + +### 4.6C.2.1 Order type mapping + +If the extended Order type $x_{eodt,1}, x_{eodt,2} = '01'$ and the Order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = "000"$ , then the mapping for $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.2.2.1. + +If the extended Order type $x_{eodt,1}, x_{eodt,2} = '01'$ and the Order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = "011"$ , then the mapping for $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.2.2.3. + +If the extended Order type $x_{eodt,1}, x_{eodt,2} = '11'$ and the Order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = "010"$ , then the mapping for $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.2.2.4. + +If the extended Order type $x_{eodt,1}, x_{eodt,2} = "11"$ and the Order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = "011"$ , then the mapping for $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.2.2.5. + +Otherwise the mapping for $x_{eodt,1}, x_{eodt,2}, x_{odt,1}, x_{odt,2}, x_{odt,3}, x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.2.2.2. + +### 4.6C.2.2 Order mapping + +#### 4.6C.2.2.1 Orders for activation and deactivation of DTX, DRX and HS-SCCH-less operation and for HS-DSCH serving cell change + +If the order is transmitted from the serving HS-DSCH cell or a secondary serving HS-DSCH cell, for this Order type, $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is comprised of: + +- DRX activation (1 bit): $x_{ord,1} = x_{drx,1}$ +- DTX activation (1 bit): $x_{ord,2} = x_{dtx,1}$ +- HS-SCCH-less operation activation (1 bit): $x_{ord,3} = x_{hs-sech-less,1}$ + +If $x_{drx,1} = "0"$ , then the HS-SCCH order is a DRX De-activation order. + +If $x_{drx,1} = "1"$ , then the HS-SCCH order is a DRX Activation order. + +If $x_{dtx,1} = "0"$ , then the HS-SCCH order is a DTX De-activation order. + +If $x_{dtx,1} = "1"$ , then the HS-SCCH order is a DTX Activation order. + +If $x_{hs-sech-less,1} = "0"$ , then the HS-SCCH order is a HS-SCCH-less operation De-activation order. + +If $x_{hs-sech-less,1} = "1"$ , then the HS-SCCH order is a HS-SCCH-less operation Activation order. + +If the order is transmitted from a non-serving cell using HS-SCCH type 1 specified in subclause 4.6.1 and $x_{ord,1}, x_{ord,2}, x_{ord,3} = "000"$ , then it is an HS-DSCH serving cell change order. + +$x_{drx,1}, x_{dtx,1} = "10"$ is a reserved combination (not used in this release). + +#### 4.6C.2.2.2 Orders for activation and deactivation of Secondary serving HS-DSCH cells and Secondary uplink frequency + +For these Extended Order types and Order types, the meaning of the orders is listed in Table 14B for the case where Secondary\_Cell\_Enabled is less than 4. For the case where Secondary\_Cell\_Enabled is greater than 3 the meaning of the orders is listed in Table 14B.1. + +When Secondary\_Cell\_Enabled is 1, + +- the order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = '010'$ is unused; +- regardless of the signaled value of $x_{ord,1}$ the UE shall assume $x_{ord,1} = '0'$ ; +- $x_{ord,2}, x_{ord,3} = "10"$ is an unused combination. + +When the UE is configured in Multiflow mode the following exceptions to the definitions in table 14B apply: + +- For the orders received from the Serving or the Secondary Serving HS-DSCH cell, the UE shall consider the 1st Secondary Serving cell to refer to the Secondary Serving HS-DSCH cell and apply the received order to that cell. The activation status of all other cells shall remain unchanged. +- For the orders received from the Assisting Serving or Assisting Secondary Serving HS-DSCH cell the UE shall consider the 1st Secondary Serving cell to refer to the Assisting Secondary Serving HS-DSCH cell and apply the received order to that cell. The activation status of all other cells shall remain unchanged. +- For the orders received from the Assisting Serving or Assisting Secondary Serving HS-DSCH cell the UE shall ignore activation status related to the Secondary Uplink Frequency and maintain the activation status of the Secondary Uplink Frequency unchanged. +- The order contents related to the 2nd and 3rd Secondary Serving HS-DSCH cells shall be ignored. + +**Table 14B: Orders for activation and deactivation of Secondary serving HS-DSCH cells and Secondary uplink frequency when Secondary\_Cell\_Enabled is less than 4, or when the UE is configured in Multiflow mode.** + +| Extended Order Type | Order Type | Order Mapping | | | Activation Status of Secondary Serving HS-DSCH cells and Secondary Uplink Frequency
A= Activate; D = De-activate | | | | +|--------------------------|-----------------------------------|---------------|-------------|-------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|----------------------------| +| | | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | 1 st Secondary Serving HS-DSCH cell | 2 nd Secondary Serving HS-DSCH cell | 3 rd Secondary Serving HS-DSCH cell | Secondary Uplink Frequency | +| $X_{eodt,1}, X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | | | | | +| 01 | 001 | 0 | 0 | 0 | D | D | D | D | +| | | 0 | 0 | 1 | A | D | D | D | +| | | 0 | 1 | 1 | A | D | D | A | +| | | 0 | 1 | 0 | D | A | D | D | +| | | 1 | 0 | 0 | A | A | D | D | +| | | 1 | 0 | 1 | A | A | D | A | +| | | 1 | 1 | 0 | D | D | A | D | +| | | 1 | 1 | 1 | A | D | A | D | +| | 010 | 0 | 0 | 0 | A | D | A | A | +| | | 0 | 0 | 1 | D | A | A | D | +| | | 0 | 1 | 0 | A | A | A | D | +| | | 0 | 1 | 1 | A | A | A | A | +| | | 1 | 0 | 0 | Unused (Reserved) | | | | +| | | 1 | 0 | 1 | Unused (Reserved) | | | | +| | | 1 | 1 | 0 | Unused (Reserved) | | | | +| | | 1 | 1 | 1 | Unused (Reserved) | | | | + +**Table 14B.1: Orders for activation and deactivation of Secondary serving HS-DSCH cells and Secondary uplink frequency when Secondary\_Cell\_Enabled is greater than 3.** + +| Extended Order Type | | Order Type | Order Mapping | | | Activation Status of Secondary Serving HS-DSCH cells and Secondary Uplink Frequency
A= Activate; D = De-activate | | | | | | | | +|---------------------|--------------|-----------------------------------|---------------|-------------|-------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|-----------------| +| $X_{eodt,1}$ | $X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | 1 st Sec Serving HS-DSCH cell | 2 nd Sec Serving HS-DSCH cell | 3 rd Sec Serving HS-DSCH cell | 4 th Sec Serving HS-DSCH cell | 5 th Sec Serving HS-DSCH cell | 6 th Sec Serving HS-DSCH cell | 7 th Sec Serving HS-DSCH cell | Sec Uplink Freq | +| 00 | | 000 | 0 | 0 | 0 | A | D | A | D | A | D | A | A | +| | | | 0 | 0 | 1 | D | A | A | D | A | D | A | D | +| | | | 0 | 1 | 1 | A | A | A | D | A | D | A | A | +| | | | 0 | 1 | 0 | A | A | A | D | A | D | A | D | +| | | | 1 | 0 | 0 | D | D | D | A | A | D | A | D | +| | | | 1 | 0 | 1 | A | D | D | A | A | D | A | D | +| | | | 1 | 1 | 0 | D | A | D | A | A | D | A | D | +| | | | 1 | 1 | 1 | A | D | D | A | A | D | A | A | +| 00 | | 001 | 0 | 0 | 0 | A | A | D | A | A | D | A | D | +| | | | 0 | 0 | 1 | A | A | D | A | A | D | A | A | +| | | | 0 | 1 | 1 | A | D | A | A | A | D | A | D | +| | | | 0 | 1 | 0 | D | D | A | A | A | D | A | D | +| | | | 1 | 0 | 0 | A | D | A | A | A | D | A | A | +| | | | 1 | 0 | 1 | D | A | A | A | A | D | A | D | +| | | | 1 | 1 | 0 | A | A | A | A | A | D | A | D | +| | | | 1 | 1 | 1 | A | A | A | A | A | D | A | A | +| 00 | | 010 | 0 | 0 | 0 | D | D | D | D | D | A | A | D | +| | | | 0 | 0 | 1 | A | D | D | D | D | A | A | D | +| | | | 0 | 1 | 1 | A | D | D | D | D | A | A | A | +| | | | 0 | 1 | 0 | D | A | D | D | D | A | A | D | +| | | | 1 | 0 | 0 | A | A | D | D | D | A | A | D | +| | | | 1 | 0 | 1 | A | A | D | D | D | A | A | A | +| | | | 1 | 1 | 0 | D | D | A | D | D | A | A | D | +| | | | 1 | 1 | 1 | A | D | A | D | D | A | A | D | +| 00 | | 011 | 0 | 0 | 0 | A | D | A | D | D | A | A | A | +| | | | 0 | 0 | 1 | D | A | A | D | D | A | A | D | +| | | | 0 | 1 | 1 | A | A | A | D | D | A | A | A | +| | | | 0 | 1 | 0 | A | A | A | D | D | A | A | D | + +| | | | | | | | | | | | | | +|----|-----|---|---|---|---|---|---|---|---|---|---|---| +| | | 1 | 0 | 0 | D | D | D | A | D | A | A | D | +| | | 1 | 0 | 1 | A | D | D | A | D | A | A | D | +| | | 1 | 1 | 0 | D | A | D | A | D | A | A | D | +| | | 1 | 1 | 1 | A | D | D | A | D | A | A | A | +| 00 | 100 | 0 | 0 | 0 | A | A | D | A | D | A | A | D | +| | | 0 | 0 | 1 | A | A | D | A | D | A | A | A | +| | | 0 | 1 | 1 | A | D | A | A | D | A | A | D | +| | | 0 | 1 | 0 | D | D | A | A | D | A | A | D | +| | | 1 | 0 | 0 | A | D | A | A | D | A | A | A | +| | | 1 | 0 | 1 | D | A | A | A | D | A | A | D | +| | | 1 | 1 | 0 | A | A | A | A | D | A | A | D | +| | | 1 | 1 | 1 | A | A | A | A | D | A | A | A | +| 00 | 101 | 0 | 0 | 0 | D | D | D | D | A | A | A | D | +| | | 0 | 0 | 1 | A | D | D | D | A | A | A | D | +| | | 0 | 1 | 1 | A | D | D | D | A | A | A | A | +| | | 0 | 1 | 0 | D | A | D | D | A | A | A | D | +| | | 1 | 0 | 0 | A | A | D | D | A | A | A | D | +| | | 1 | 0 | 1 | A | A | D | D | A | A | A | A | +| | | 1 | 1 | 0 | D | D | A | D | A | A | A | D | +| | | 1 | 1 | 1 | A | D | A | D | A | A | A | D | +| 00 | 110 | 0 | 0 | 0 | A | D | A | D | A | A | A | A | +| | | 0 | 0 | 1 | D | A | A | D | A | A | A | D | +| | | 0 | 1 | 1 | A | A | A | D | A | A | A | A | +| | | 0 | 1 | 0 | A | A | A | D | A | A | A | D | +| | | 1 | 0 | 0 | D | D | D | A | A | A | A | D | +| | | 1 | 0 | 1 | A | D | D | A | A | A | A | D | +| | | 1 | 1 | 0 | D | A | D | A | A | A | A | D | +| | | 1 | 1 | 1 | A | D | D | A | A | A | A | A | +| 00 | 111 | 0 | 0 | 0 | A | A | D | A | A | A | A | D | +| | | 0 | 0 | 1 | A | A | D | A | A | A | A | A | +| | | 0 | 1 | 1 | A | D | A | A | A | A | A | D | +| | | 0 | 1 | 0 | D | D | A | A | A | A | A | D | +| | | 1 | 0 | 0 | A | D | A | A | A | A | A | A | +| | | 1 | 0 | 1 | D | A | A | A | A | A | A | D | + +| | | | | | | | | | | | | | +|----|-----|---|---|---|---|---|---|---|---|---|---|---| +| | | 1 | 1 | 0 | A | A | A | A | A | A | A | D | +| | | 1 | 1 | 1 | A | A | A | A | A | A | A | A | +| 01 | 001 | 0 | 0 | 0 | D | D | D | D | D | D | D | D | +| | | 0 | 0 | 1 | A | D | D | D | D | D | D | D | +| | | 0 | 1 | 1 | A | D | D | D | D | D | D | A | +| | | 0 | 1 | 0 | D | A | D | D | D | D | D | D | +| | | 1 | 0 | 0 | A | A | D | D | D | D | D | D | +| | | 1 | 0 | 1 | A | A | D | D | D | D | D | A | +| | | 1 | 1 | 0 | D | D | A | D | D | D | D | D | +| | | 1 | 1 | 1 | A | D | A | D | D | D | D | D | +| 01 | 010 | 0 | 0 | 0 | A | D | A | D | D | D | D | A | +| | | 0 | 0 | 1 | D | A | A | D | D | D | D | D | +| | | 0 | 1 | 1 | A | A | A | D | D | D | D | A | +| | | 0 | 1 | 0 | A | A | A | D | D | D | D | D | +| | | 1 | 0 | 0 | D | D | D | A | D | D | D | D | +| | | 1 | 0 | 1 | A | D | D | A | D | D | D | D | +| | | 1 | 1 | 0 | D | A | D | A | D | D | D | D | +| | | 1 | 1 | 1 | A | D | D | A | D | D | D | A | +| 01 | 100 | 0 | 0 | 0 | D | D | D | D | A | D | D | D | +| | | 0 | 0 | 1 | A | D | D | D | A | D | D | D | +| | | 0 | 1 | 1 | A | D | D | D | A | D | D | A | +| | | 0 | 1 | 0 | D | A | D | D | A | D | D | D | +| | | 1 | 0 | 0 | A | A | D | D | A | D | D | D | +| | | 1 | 0 | 1 | A | A | D | D | A | D | D | A | +| | | 1 | 1 | 0 | D | D | A | D | A | D | D | D | +| | | 1 | 1 | 1 | A | D | A | D | A | D | D | D | +| 01 | 101 | 0 | 0 | 0 | A | D | A | D | A | D | D | A | +| | | 0 | 0 | 1 | D | A | A | D | A | D | D | D | +| | | 0 | 1 | 1 | A | A | A | D | A | D | D | A | +| | | 0 | 1 | 0 | A | A | A | D | A | D | D | D | +| | | 1 | 0 | 0 | D | D | D | A | A | D | D | D | +| | | 1 | 0 | 1 | A | D | D | A | A | D | D | D | +| | | 1 | 1 | 0 | D | A | D | A | A | D | D | D | + +| | | | | | | | | | | | | | +|----|-----|---|---|---|---|---|---|---|---|---|---|---| +| | | 1 | 1 | 1 | A | D | D | A | A | D | D | A | +| 01 | 110 | 0 | 0 | 0 | A | A | D | A | A | D | D | D | +| | | 0 | 0 | 1 | A | A | D | A | A | D | D | A | +| | | 0 | 1 | 1 | A | D | A | A | A | D | D | D | +| | | 0 | 1 | 0 | D | D | A | A | A | D | D | D | +| | | 1 | 0 | 0 | A | D | A | A | A | D | D | A | +| | | 1 | 0 | 1 | D | A | A | A | A | D | D | D | +| | | 1 | 1 | 0 | A | A | A | A | A | D | D | D | +| | | 1 | 1 | 1 | A | A | A | A | A | D | D | A | +| 01 | 111 | 0 | 0 | 0 | D | D | D | D | D | A | D | D | +| | | 0 | 0 | 1 | A | D | D | D | D | A | D | D | +| | | 0 | 1 | 1 | A | D | D | D | D | A | D | A | +| | | 0 | 1 | 0 | D | A | D | D | D | A | D | D | +| | | 1 | 0 | 0 | A | A | D | D | D | A | D | D | +| | | 1 | 0 | 1 | A | A | D | D | D | A | D | A | +| | | 1 | 1 | 0 | D | D | A | D | D | A | D | D | +| | | 1 | 1 | 1 | A | D | A | D | D | A | D | D | +| 10 | 000 | 0 | 0 | 0 | A | D | A | D | D | A | D | A | +| | | 0 | 0 | 1 | D | A | A | D | D | A | D | D | +| | | 0 | 1 | 1 | A | A | A | D | D | A | D | A | +| | | 0 | 1 | 0 | A | A | A | D | D | A | D | D | +| | | 1 | 0 | 0 | D | D | D | A | D | A | D | D | +| | | 1 | 0 | 1 | A | D | D | A | D | A | D | D | +| | | 1 | 1 | 0 | D | A | D | A | D | A | D | D | +| | | 1 | 1 | 1 | A | D | D | A | D | A | D | A | +| 10 | 001 | 0 | 0 | 0 | A | A | D | A | D | A | D | D | +| | | 0 | 0 | 1 | A | A | D | A | D | A | D | A | +| | | 0 | 1 | 1 | A | D | A | A | D | A | D | D | +| | | 0 | 1 | 0 | D | D | A | A | D | A | D | D | +| | | 1 | 0 | 0 | A | D | A | A | D | A | D | A | +| | | 1 | 0 | 1 | D | A | A | A | D | A | D | D | +| | | 1 | 1 | 0 | A | A | A | A | D | A | D | D | +| | | 1 | 1 | 1 | A | A | A | A | D | A | D | A | + +| | | | | | | | | | | | | | +|----|-----|---|---|---|---|---|---|---|---|---|---|---| +| 10 | 010 | 0 | 0 | 0 | D | D | D | D | A | A | D | D | +| | | 0 | 0 | 1 | A | D | D | D | A | A | D | D | +| | | 0 | 1 | 1 | A | D | D | D | A | A | D | A | +| | | 0 | 1 | 0 | D | A | D | D | A | A | D | D | +| | | 1 | 0 | 0 | A | A | D | D | A | A | D | D | +| | | 1 | 0 | 1 | A | A | D | D | A | A | D | A | +| | | 1 | 1 | 0 | D | D | A | D | A | A | D | D | +| | | 1 | 1 | 1 | A | D | A | D | A | A | D | D | +| 10 | 011 | 0 | 0 | 0 | A | D | A | D | A | A | D | A | +| | | 0 | 0 | 1 | D | A | A | D | A | A | D | D | +| | | 0 | 1 | 1 | A | A | A | D | A | A | D | A | +| | | 0 | 1 | 0 | A | A | A | D | A | A | D | D | +| | | 1 | 0 | 0 | D | D | D | A | A | A | D | D | +| | | 1 | 0 | 1 | A | D | D | A | A | A | D | D | +| | | 1 | 1 | 0 | D | A | D | A | A | A | D | D | +| | | 1 | 1 | 1 | A | D | D | A | A | A | D | A | +| 10 | 100 | 0 | 0 | 0 | A | A | D | A | A | A | D | D | +| | | 0 | 0 | 1 | A | A | D | A | A | A | D | A | +| | | 0 | 1 | 1 | A | D | A | A | A | A | D | D | +| | | 0 | 1 | 0 | D | D | A | A | A | A | D | D | +| | | 1 | 0 | 0 | A | D | A | A | A | A | D | A | +| | | 1 | 0 | 1 | D | A | A | A | A | A | D | D | +| | | 1 | 1 | 0 | A | A | A | A | A | A | D | D | +| | | 1 | 1 | 1 | A | A | A | A | A | A | D | A | +| 10 | 101 | 0 | 0 | 0 | D | D | D | D | D | D | A | D | +| | | 0 | 0 | 1 | A | D | D | D | D | D | A | D | +| | | 0 | 1 | 1 | A | D | D | D | D | D | A | A | +| | | 0 | 1 | 0 | D | A | D | D | D | D | A | D | +| | | 1 | 0 | 0 | A | A | D | D | D | D | A | D | +| | | 1 | 0 | 1 | A | A | D | D | D | D | A | A | +| | | 1 | 1 | 0 | D | D | A | D | D | D | A | D | +| | | 1 | 1 | 1 | A | D | A | D | D | D | A | D | +| 10 | 110 | 0 | 0 | 0 | A | D | A | D | D | D | A | A | +| | | 0 | 0 | 1 | D | A | A | D | D | D | A | D | + +| | | | | | | | | | | | | | +|----|-----|---|---|---|---|---|---|---|---|---|---|---| +| | | 0 | 1 | 1 | A | A | A | D | D | D | A | A | +| | | 0 | 1 | 0 | A | A | A | D | D | D | A | D | +| | | 1 | 0 | 0 | D | D | D | A | D | D | A | D | +| | | 1 | 0 | 1 | A | D | D | A | D | D | A | D | +| | | 1 | 1 | 0 | D | A | D | A | D | D | A | D | +| | | 1 | 1 | 1 | A | D | D | A | D | D | A | A | +| 10 | 111 | 0 | 0 | 0 | A | A | D | A | D | D | A | D | +| | | 0 | 0 | 1 | A | A | D | A | D | D | A | A | +| | | 0 | 1 | 1 | A | D | A | A | D | D | A | D | +| | | 0 | 1 | 0 | D | D | A | A | D | D | A | D | +| | | 1 | 0 | 0 | A | D | A | A | D | D | A | A | +| | | 1 | 0 | 1 | D | A | A | A | D | D | A | D | +| | | 1 | 1 | 0 | A | A | A | A | D | D | A | D | +| | | 1 | 1 | 1 | A | A | A | A | D | D | A | A | +| 11 | 000 | 0 | 0 | 0 | D | D | D | D | A | D | A | D | +| | | 0 | 0 | 1 | A | D | D | D | A | D | A | D | +| | | 0 | 1 | 1 | A | D | D | D | A | D | A | A | +| | | 0 | 1 | 0 | D | A | D | D | A | D | A | D | +| | | 1 | 0 | 0 | A | A | D | D | A | D | A | D | +| | | 1 | 0 | 1 | A | A | D | D | A | D | A | A | +| | | 1 | 1 | 0 | D | D | A | D | A | D | A | D | +| | | 1 | 1 | 1 | A | D | A | D | A | D | A | D | +| 11 | 001 | 0 | 0 | 0 | A | A | D | A | D | D | D | D | +| | | 0 | 0 | 1 | A | A | D | A | D | D | D | A | +| | | 0 | 1 | 1 | A | D | A | A | D | D | D | D | +| | | 0 | 1 | 0 | D | D | A | A | D | D | D | D | +| | | 1 | 0 | 0 | A | D | A | A | D | D | D | A | +| | | 1 | 0 | 1 | D | A | A | A | D | D | D | D | +| | | 1 | 1 | 0 | A | A | A | A | D | D | D | D | +| | | 1 | 1 | 1 | A | A | A | A | D | D | D | A | + +#### 4.6C.2.2.3 Orders for Switching between Uplink Closed Loop Transmit Diversity Activation states + +For this Order type, the meaning of the orders is listed in Table 14B.2. + +When the UE is configured in Multiflow mode, if any of the orders related to uplink CLTD activation states as defined in Table 14B.2 are received from the Assisting Serving or Assisting Secondary Serving HS-DSCH cell, then the UE shall ignore the orders and maintain the uplink CLTD activation state unchanged. + +**Table 14B.2: Orders for UE when UL\_CLTD\_Enabled is TRUE** + +| Extended Order Type | Order Type | Order Mapping | | | Activation States
A= Activate; D = De-activate | | | +|--------------------------|-----------------------------------|---------------|-------------|-------------|---------------------------------------------------------|----------------------------------------|----------------------------------------| +| | | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | 1 | 2 | 3 | +| $X_{eodt,1}, X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | | | | Tx on Antenna 1 and Antenna 2 with Beamforming (Note 1) | Single Tx on Antenna 1 with no S-DPCCH | Single Tx on Antenna 2 with no S-DPCCH | +| 01 | 011 | 1 | 1 | 1 | A | D | D | +| | | 0 | 0 | 1 | D | A | D | +| | | 0 | 1 | 0 | D | D | A | +| | | 1 | 0 | 1 | Unused (Reserved) | | | +| | | 1 | 1 | 0 | Unused (Reserved) | | | +| | | 0 | 0 | 0 | Unused (Reserved) | | | +| | | 0 | 1 | 1 | Unused (Reserved) | | | +| | | 1 | 0 | 0 | Unused (Reserved) | | | + +Note 1: The precoding weights for beamforming are defined in [4]. + +#### 4.6C.2.2.4 Orders for activating and de-activating demodulation common pilots (D-CPICH) when the UE is configured in MIMO mode with four transmit antennas + +For this Order type, the meaning of the orders is listed in Table 14B.3. + +**Table 14B.3: Orders when the UE is configured in MIMO mode with four transmit antennas** + +| Extended Order Type | Order Type | Order Mapping | | | D-CPICH Activation States
A= Activate; D = De-activate | +|--------------------------|-----------------------------------|---------------|-------------|-------------|-----------------------------------------------------------| +| | | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | | +| $X_{eodt,1}, X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | | | | | +| 11 | 010 | 1 | 1 | 1 | A | +| | | 0 | 0 | 0 | D | +| | | 0 | 0 | 1 | Unused (Reserved) | +| | | 0 | 1 | 0 | Unused (Reserved) | +| | | 0 | 1 | 1 | Unused (Reserved) | +| | | 1 | 0 | 0 | Unused (Reserved) | +| | | 1 | 0 | 1 | Unused (Reserved) | +| | | 1 | 1 | 0 | Unused (Reserved) | + +Note 1: The activation and de-activation status corresponds to individual HS-DSCH cell. + +Note 2: Activation and de-activation indication applies for all the demodulation common pilots configured in the cell. + +#### 4.6C.2.2.5 Orders for switching the E-DCH TTI, and for start/stop a simplified HS-SCCH type 1 transmission interval + +If the order is transmitted from the serving HS-DSCH cell or a secondary serving HS-DSCH cell, for this Order type, the meaning of the orders for single cell E-DCH is listed in Table 14B.3A and the meaning of the orders for dual cell E-DCH is listed in Table 14B.3B. + +**Table 14B.3A: Orders for switching the E-DCH TTI for single cell E-DCH and for start/stop a simplified HS-SCCH type 1 transmission interval** + +| Extended Order Type | Order Type | Order Mapping | | | Interpretation | +|--------------------------|-----------------------------------|---------------|-------------|-------------|-------------------------------------------------------------| +| | | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | | +| $X_{eodt,1}, X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | | | | | +| 11 | 011 | 0 | 0 | 0 | TTI switch order from 2ms to 10ms | +| | | 0 | 0 | 1 | TTI switch order from 10ms to 2ms | +| | | 0 | 1 | 0 | Start simplified HS-SCCH type 1 transmission interval order | +| | | 0 | 1 | 1 | Stop simplified HS-SCCH type 1 transmission interval order | +| | | 1 | 0 | 0 | Unused (Reserved) for single cell E-DCH | +| | | 1 | 0 | 1 | Unused (Reserved) for single cell E-DCH | +| | | 1 | 1 | 0 | Unused (Reserved) for single cell E-DCH | +| | | 1 | 1 | 1 | Unused (Reserved) for single cell E-DCH | + +**Table 14B.3B: Orders for switching the E-DCH TTI for dual cell E-DCH** + +| Extended Order Type | Order Type | Order Mapping | | | Interpretation | +|--------------------------|-----------------------------------|---------------|-------------|-------------|---------------------------------------| +| | | $X_{ord,1}$ | $X_{ord,2}$ | $X_{ord,3}$ | | +| $X_{eodt,1}, X_{eodt,2}$ | $X_{odt,1}, X_{odt,2}, X_{odt,3}$ | | | | | +| 11 | 011 | 0 | 0 | 0 | Unused (Reserved for dual cell E-DCH) | +| | | 0 | 0 | 1 | Unused (Reserved for dual cell E-DCH) | +| | | 0 | 1 | 0 | TTI switch order to 2ms+10ms | +| | | 0 | 1 | 1 | TTI switch order to 10ms+2ms | +| | | 1 | 0 | 0 | TTI switch order to 2ms+2ms | +| | | 1 | 0 | 1 | TTI switch order to 10ms+10ms | +| | | 1 | 1 | 0 | Unused (Reserved for dual cell E-DCH) | +| | | 1 | 1 | 1 | Unused (Reserved for dual cell E-DCH) | + +NOTE 1: (Table 14B.3B): For the TTI switch orders the TTI length displayed on the left hand side applies to the primary uplink frequency, while the TTI length displayed on the right hand side applies to the secondary uplink frequency. + +NOTE 2: (Table 14B.3B): The TTI switch orders also apply if the secondary uplink frequency is deactivated, but it becomes effective on the secondary uplink frequency upon its re-activation. + +#### 4.6C.2.3 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [13]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6C.3 HS-SCCH order information field mapping in the CELL\_FACH and CELL\_PCH states + +#### 4.6C.3.1 Order type mapping + +If the extended Order type $x_{eodt,1}, x_{eodt,2} = '01'$ and the Order type $x_{odt,1}, x_{odt,2}, x_{odt,3} = '000'$ , then the mapping for $x_{ord,1}, x_{ord,2}, x_{ord,3}$ is according to subclause 4.6C.3.2. + +#### 4.6C.3.2 Order mapping + +##### 4.6C.3.2.1 Orders for network triggered HS-DPCCH transmission + +For this Order type, the Order mapping $x_{ord,1}, x_{ord,2}, x_{ord,3}$ and the associated meaning is as follows: + +If $x_{ord,1}, x_{ord,2}, x_{ord,3} = '001'$ , then the HS-SCCH order is an order for triggering the random access procedure in CELL\_FACH as specified in subclause 6.1A in [4]. + +##### 4.6C.3.2.2 Orders for HS-DSCH reception during CELL\_FACH HS-SCCH DRX operation + +For this Order type, the Order mapping $x_{ord,1}, x_{ord,2}, x_{ord,3}$ and the associated meaning is as follows: + +If $x_{ord,1}, x_{ord,2}, x_{ord,3} = '110'$ then the HS-SCCH order is an order for notifying about an HS-DSCH transmission during CELL\_FACH HS-SCCH DRX operation as specified in [4] subclause 6A.1.3.2. + +## 4.6D Coding for HS-SCCH type 4 + +### 4.6D.1 Overview + +HS-SCCH type 4 is used when the UE is configured in MIMO mode with four transmit antennas. If one transport block is transmitted on the associated HS-PDSCH(s) or an HS-SCCH order is transmitted, the following information is transmitted by means of the HS-SCCH type 4 physical channel: + +- Channelization-code-set information (7 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ +- Modulation scheme and number of transport blocks information (5 bits): $x_{ms,1}, x_{ms,2}, x_{ms,3}, x_{ms,4}, x_{ms,5}$ +- Precoding weight information (4 bits): $x_{pwipb,1}, x_{pwipb,2}, x_{pwipb,3}, x_{pwipb,4}$ +- Transport-block size information (6 bits): $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ +- Redundancy and constellation version (2 bits): $x_{rvpb,1}, x_{rvpb,2}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +For an HS-SCCH order, + +- $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}, x_{ms,1}, x_{ms,2}, x_{ms,3}, x_{ms,4}, x_{ms,5}, x_{pwipb,1}, x_{pwipb,2}, x_{pwipb,3}, x_{pwipb,4}$ shall be set to "1110000000000000" +- $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,4}$ shall be set to "1111" +- $x_{tbspb,5}, x_{tbspb,6}$ shall be set to $x_{eodt,1}, x_{eodt,2}$ + +- $X_{hap,1}, X_{hap,2}, X_{hap,3}, X_{hap,4}, X_{rvpb,1}, X_{rvpb,2}$ shall be set to $X_{odt,1}, X_{odt,2}, X_{odt,3}, X_{ord,1}, X_{ord,2}, X_{ord,3}$ + +where $X_{eodt,1}, X_{eodt,2}, X_{odt,1}, X_{odt,2}, X_{odt,3}, X_{ord,1}, X_{ord,2}, X_{ord,3}$ are defined in subclause 4.6C. + +If more than one transport block is transmitted on the associated HS-PDSCHs, the following information is transmitted by means of the HS-SCCH type 4 physical channel: + +- Channelization-code-set information (7 bits): $X_{ccs,1}, X_{ccs,2}, \dots, X_{ccs,7}$ +- Modulation scheme and number of transport blocks information (5 bits): $X_{ms,1}, X_{ms,2}, X_{ms,3}, X_{ms,4}, X_{ms,5}$ +- Precoding weight information (4 bits): $X_{pwipb,1}, X_{pwipb,2}, X_{pwipb,3}, X_{pwipb,4}$ +- Transport-block size information for the primary or/and fourth transport block (6 bits): $X_{tbspb,1}, X_{tbspb,2}, \dots, X_{tbspb,6}$ +- Transport-block size information for the second or/and third transport block (6 bits): $X_{tbssb,1}, X_{tbssb,2}, \dots, X_{tbssb,6}$ +- Hybrid-ARQ process information (4 bits): $X_{hap,1}, X_{hap,2}, \dots, X_{hap,4}$ +- Redundancy and constellation version for the primary or/and fourth transport block (2 bits): $X_{rvpb,1}, X_{rvpb,2}$ +- Redundancy and constellation version for the second or/and third transport block (2 bits): $X_{rvsb,1}, X_{rvsb,2}$ +- UE identity (16 bits): $X_{ue,1}, X_{ue,2}, \dots, X_{ue,16}$ + +The overall coding chain for HS-SCCH type 4 is same as that of HS-SCCH type 3 as shown in Figure 19 B. + +## 4.6D.2 HS-SCCH type 4 information field mapping + +### 4.6D.2.1 Redundancy and constellation version coding + +If four transport blocks are transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are coded jointly to produce the values $X_{rvpb}$ for the primary and the fourth transport blocks and $X_{rvsb}$ for the second and the third transport blocks respectively. The transmitted sequences $x_{rvpb,1}, x_{rvpb,2}$ and $x_{rvsb,1}, x_{rvsb,2}$ are the binary representations of $X_{rvpb}$ and $X_{rvsb}$ , respectively, where $x_{rvpb,1}$ and $x_{rvsb,1}$ are the MSBs. + +If three transport blocks are transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are coded jointly to produce the values $X_{rvpb}$ for the primary transport block and $X_{rvsb}$ for the second and the third transport blocks respectively. The transmitted sequences $x_{rvpb,1}, x_{rvpb,2}$ and $x_{rvsb,1}, x_{rvsb,2}$ are the binary representations of $X_{rvpb}$ and $X_{rvsb}$ , respectively, where $x_{rvpb,1}$ and $x_{rvsb,1}$ are the MSBs. + +For each of the primary transport block and a second transport block if two transport blocks are transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are coded jointly to produce the values $X_{rvpb}$ and $X_{rvsb}$ respectively. The transmitted sequences $x_{rvpb,1}, x_{rvpb,2}$ and $x_{rvsb,1}, x_{rvsb,2}$ are the binary representations of $X_{rvpb}$ and $X_{rvsb}$ , respectively, where $x_{rvpb,1}$ and $x_{rvsb,1}$ are the MSBs. + +For the primary transport block if only one transport block is transmitted on the associated HS-PDSCH(s), the redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are coded jointly to produce the value $X_{rvpb}$ . The transmitted sequence $x_{rvpb,1}, x_{rvpb,2}$ is the binary representation of $X_{rvpb}$ , where $x_{rvpb,1}$ is the MSB. + +Joint coding of parameters $r, s$ and constellation version parameter $b$ is done according to tables 14B.4 and 14B.5 according to the modulation mode used. If $X_{rvpb} = 0$ or $X_{rvsb} = 0$ , the UE shall treat the corresponding transport block as an initial transmission. + +**Table 14B.4: RV coding for 16QAM and 64QAM for HS-SCCH type 4** + +| $X_{rvpb}$ or
$X_{rvsb}$
(value) | $N_{sys} / N_{data} < 1/2$ | | | $N_{sys} / N_{data} \geq 1/2$ | | | +|----------------------------------------|----------------------------|---|---|-------------------------------|---|---| +| | s | r | b | s | r | b | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | +| 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 2 | 1 | 0 | 2 | 0 | 0 | 0 | +| 3 | 1 | 0 | 3 | 1 | 0 | 2 | + +**Table 14B.5: RV coding for QPSK for HS-SCCH type 4** + +| $X_{rvpb}$ or
$X_{rvsb}$
(value) | $N_{sys} / N_{data} < 1/2$ | | $N_{sys} / N_{data} \geq 1/2$ | | +|----------------------------------------|----------------------------|---|-------------------------------|---| +| | s | r | s | r | +| 0 | 1 | 0 | 1 | 0 | +| 1 | 1 | 1 | 0 | 1 | +| 2 | 1 | 2 | 0 | 3 | +| 3 | 1 | 3 | 1 | 2 | + +#### 4.6D.2.2 Modulation scheme and number of transport blocks mapping + +The number of transport blocks transmitted on the associated HS-PDSCH(s) and the modulation scheme information are jointly coded as shown in Table 14B.6: + +**Table 14B.6: Mapping of $x_{ms}$** + +| $x_{ms,1}$ ,
$x_{ms,2}$ ,
$x_{ms,3}$ ,
$x_{ms,4}$ ,
$x_{ms,5}$ | Modulation
for
primary
transport
block | Modulation
for second
transport
block | Modulation
for
third
transport
block | Modulation
for
fourth
transport
block | Number
of
transport
blocks | +|----------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------|--------------------------------------------------|---------------------------------------------------|-------------------------------------| +| 00000 | QPSK | Unused | Unused | Unused | 1 | +| 00001 | 16QAM | Unused | Unused | Unused | 1 | +| 00010 | 64 QAM | Unused | Unused | Unused | 1 | +| 00011 | QPSK | QPSK | Unused | Unused | 2 | +| 00100 | QPSK | 16QAM | Unused | Unused | 2 | +| 00101 | QPSK | 64QAM | Unused | Unused | 2 | +| 00110 | 16QAM | QPSK | Unused | Unused | 2 | +| 00111 | 16QAM | 16QAM | Unused | Unused | 2 | +| 1000 | 16QAM | 64QAM | Unused | Unused | 2 | +| 01001 | 64QAM | QPSK | Unused | Unused | 2 | +| 01010 | 64QAM | 16QAM | Unused | Unused | 2 | +| 01011 | 64QAM | 64QAM | Unused | Unused | 2 | +| 01100 | QPSK | QPSK | QPSK | Unused | 3 | +| 01101 | QPSK | 16QAM | 16QAM | Unused | 3 | +| 01110 | QPSK | 64QAM | 64QAM | Unused | 3 | +| 01111 | 16QAM | QPSK | QPSK | Unused | 3 | +| 10000 | 16QAM | 16QAM | 16QAM | Unused | 3 | +| 10001 | 16QAM | 64QAM | 64QAM | Unused | 3 | +| 10010 | 64QAM | QPSK | QPSK | Unused | 3 | +| 10011 | 64QAM | 16QAM | 16QAM | Unused | 3 | +| 10100 | 64QAM | 64QAM | 64QAM | Unused | 3 | +| 10101 | QPSK | QPSK | QPSK | QPSK | 4 | +| 10110 | QPSK | 16QAM | 16QAM | QPSK | 4 | + +| | | | | | | +|-------|-------------------|-------|-------|--------|---| +| 10111 | QPSK | 64QAM | 64QAM | QPSK | 4 | +| 11000 | 16QAM | QPSK | QPSK | 16QAM | 4 | +| 11001 | 16QAM | 16QAM | 16QAM | 16QAM | 4 | +| 11010 | 16QAM | 64QAM | 64QAM | 16QAM | 4 | +| 11011 | 64QAM | QPSK | QPSK | 64QAM | 4 | +| 11100 | 64QAM | 16QAM | 16QAM | 64QAM | 4 | +| 11101 | 64 QAM | 64QAM | 64QAM | 64 QAM | 4 | +| 11110 | Unused (Reserved) | | | | | +| 11111 | Unused (Reserved) | | | | | + +#### 4.6D.2.3 Channelization code-set mapping + +The channelization code-set bits $x_{ces,1}, x_{ces,2}, \dots, x_{ces,7}$ are coded according to the following: + +Given P (multi-)codes starting at code O calculate the information-field using the unsigned binary representation of integers calculated by the expressions, + +for the first three bits (code group indicator) of which $x_{ces,1}$ is the MSB: + +$$x_{ces,1}, x_{ces,2}, x_{ces,3} = \min(P-1, 15-P)$$ + +for the last four bits (code offset indicator) of which $x_{ces,4}$ is the MSB: + +$$x_{ces,4}, x_{ces,5}, x_{ces,6}, x_{ces,7} = |O-1-\lfloor P/8 \rfloor| * 15$$ + +The definitions of P and O are given in [3]. + +If more than one transport blocks are transmitted on the associated HS-PDSCH(s), the same set of channelization codes shall be used for all transport blocks. + +#### 4.6D.2.4 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [13]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +#### 4.6D.2.5 HARQ process identifier mapping + +If four transport blocks are transmitted on the associated HS-PDSCH(s), the mapping relationship between the hybrid-ARQ processes and the transport blocks is such that when the HARQ-process with identifier $HAP_{pb}$ is mapped to the primary and the fourth transport block, the HARQ-process with the identifier given by $(HAP_{pb} + N_{proc}) \bmod N_{proc}$ shall be mapped to the second and the third transport block, where $N_{proc}$ is the number of HARQ processes configured by higher layers. The combination of HARQ-processes is indicated by the hybrid-ARQ process information (4 bits) $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ which are the unsigned binary representation of $HAP_{pb}$ where $x_{hap,1}$ is MSB. + +If three transport blocks are transmitted on the associated HS-PDSCH(s), the mapping relationship between the hybrid-ARQ processes and the transport blocks is such that when the HARQ-process with identifier $HAP_{pb}$ is mapped to the primary transport block, the HARQ-process with the identifier given by $(HAP_{pb} + N_{proc}) \bmod N_{proc}$ shall be mapped to the second and the third transport block, where $N_{proc}$ is the number of HARQ processes configured by higher layers. The combination of HARQ-processes is indicated by the hybrid-ARQ process information (4 bits) $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ which are the unsigned binary representation of $HAP_{pb}$ where $x_{hap,1}$ is MSB. + +If two transport blocks are transmitted on the associated HS-PDSCH(s), the mapping relationship between the hybrid-ARQ processes and the transport blocks is such that when the HARQ-process with identifier $HAP_{pb}$ is mapped to the primary transport block, the HARQ-process with the identifier given by $(HAP_{pb} + N_{proc}) \bmod N_{proc}$ shall be mapped to the second transport block, where $N_{proc}$ is the number of HARQ processes configured by higher layers. The combination of HARQ-processes is indicated by the hybrid-ARQ process information (4 bits) $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ which are the unsigned binary representation of $HAP_{pb}$ where $x_{hap,1}$ is MSB. + +If only one transport block is transmitted on the associated HS-PDSCH(s), the above mapping is ignored and the hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ is the unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6D.2.6 Transport block size index mapping + +The transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is the unsigned binary representation of the transport block size index for the primary transport block, where $x_{tbspb,1}$ is the MSB. + +If two transport blocks are transmitted on the associated HS-PDSCH(s), the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is the unsigned binary representation of the transport block size index for the second transport block, where $x_{tbssb,1}$ is the MSB. If the number of transport blocks indicated is equal to 2, if $X_{rvpb} = 0$ and if the transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is set to "111111", then the primary transport block is not transmitted. If the number of transport blocks indicated is equal to 2, if $X_{rvsb} = 0$ and if the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is set to "111111", then the second transport block is not transmitted. + +If three transport blocks are transmitted on the associated HS-PDSCH(s), the transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is the unsigned binary representation of the transport block size index for the primary transport block, where $x_{tbspb,1}$ is the MSB and the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is the unsigned binary representation of the transport block size index for the second and the third transport blocks, where $x_{tbssb,1}$ is the MSB. If the number of transport blocks indicated is equal to 3, if $X_{rvpb} = 0$ and if the transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is set to "111111", then the primary transport block is not transmitted. If the number of transport blocks indicated is equal to 3, if $X_{rvsb} = 0$ and if the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is set to "111111", then the second and the third transport blocks are not transmitted. + +If four transport blocks are transmitted on the associated HS-PDSCH(s), the transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is the unsigned binary representation of the transport block size index for the primary and the fourth transport blocks, where $x_{tbspb,1}$ is the MSB and the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is the unsigned binary representation of the transport block size index for the second and the third transport blocks, where $x_{tbssb,1}$ is the MSB. If the number of transport blocks indicated is equal to 4 if $X_{rvpb} = 0$ and if the transport-block size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ is set to "111111", then the primary and fourth transport blocks are not transmitted. If the number of transport blocks indicated is equal to 4 if $X_{rvsb} = 0$ and if the transport-block size information $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ is set to "111111", then the second and the third transport blocks are not transmitted. + +#### 4.6D.2.7 Precoding Weight Information mapping + +The precoding weight information $x_{pwipb,1}, x_{pwipb,2}, x_{pwipb,3}, x_{pwipb,4}$ is mapped according to Table 14B.7. The quantity denotes the matrix defined by the columns given by the set from the expression where $I$ is the identity matrix and the vector is given by Table 14B.7. + +**Table 14B.7: precoding weight information** + +| $x_{pwipb,1},$
$x_{pwipb,2},$
$x_{pwipb,3},$
$x_{pwipb,4},$ | Number of transport blocks | | | | +|----------------------------------------------------------------------|----------------------------|---|---|---| +| | 1 | 2 | 3 | 4 | +| 0000 | | | | | +| 0001 | | | | | +| 0010 | | | | | +| 0011 | | | | | +| 0100 | | | | | +| 0101 | | | | | +| 0110 | | | | | +| 0111 | | | | | +| 1000 | | | | | +| 1001 | | | | | +| 1010 | | | | | +| 1011 | | | | | +| 1100 | | | | | +| 1101 | | | | | +| 1110 | | | | | +| 1111 | | | | | + +#### 4.6D.3 Multiplexing of HS-SCCH type 4 information + +The channelization-code-set information $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,7}$ , modulation-scheme and number of transport blocks information $x_{ms,1}, x_{ms,2}, x_{ms,3}, x_{ms,4}, x_{ms,5}$ and precoding weight information $x_{pwipb,1}, x_{pwipb,2}, x_{pwipb,3}, x_{pwipb,4}$ are multiplexed together. This gives a sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,16}$ , where + +$$x_{1,i} = x_{ccs,i} \quad i=1,2,\dots,7$$ + +$$x_{1,i} = x_{ms,i-7} \quad i=8,9,10,11,12$$ + +$$x_{1,i} = x_{pwipb,i-12} \quad i=13,14,15,16$$ + +If one transport block is transmitted on the associated HS-PDSCH(s), the transport-block-size information $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ and redundancy-version information $x_{rvpb,1}, x_{rvpb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,12}$ where + +$$x_{2,i} = x_{tbs,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{hap,i-6} \quad i=7,8,\dots,10$$ + +$$x_{2,i} = x_{rv,i-10} \quad i=11,12$$ + +If two transport blocks are transmitted on the associated HS-PDSCHs, the transport-block-size information for the primary transport block $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , transport-block-size information for the second transport block $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ , redundancy-version information for the primary transport block $x_{rvpb,1}, x_{rvpb,2}$ , and redundancy-version information for the second transport block $x_{rvsb,1}, x_{rvsb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ where + +$$x_{2,i} = x_{tbspb,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{tbssb,i-6} \quad i=7,8,\dots,12$$ + +$$x_{2,i} = x_{hap,i-12} \quad i=13,14,\dots,16$$ + +$$x_{2,i} = x_{rvpb,i-16} \quad i=17,18$$ + +$$x_{2,i} = x_{rvsb,i-18} \quad i=19,20$$ + +If three transport blocks are transmitted on the associated HS-PDSCHs, the transport-block-size information for the primary transport block $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , transport-block-size information for the second and the third transport blocks $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ , redundancy-version information for the primary transport block $x_{rvpb,1}, x_{rvpb,2}$ , and redundancy-version information for the second and the third transport blocks $x_{rvsb,1}, x_{rvsb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ where + +$$x_{2,i} = x_{tbspb,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{tbssb,i-6} \quad i=7,8,\dots,12$$ + +$$x_{2,i} = x_{hap,i-12} \quad i=13,14,\dots,16$$ + +$$x_{2,i} = x_{rvpb,i-16} \quad i=17,18$$ + +$$x_{2,i} = x_{rvsb,i-18} \quad i=19,20$$ + +If four transport blocks are transmitted on the associated HS-PDSCHs, the transport-block-size information for the primary and the fourth transport blocks $x_{tbspb,1}, x_{tbspb,2}, \dots, x_{tbspb,6}$ , transport-block-size information for the second and the third transport blocks $x_{tbssb,1}, x_{tbssb,2}, \dots, x_{tbssb,6}$ , Hybrid-ARQ-process information $x_{hap,1}, x_{hap,2}, \dots, x_{hap,4}$ , redundancy-version information for the primary and the fourth transport blocks $x_{rvpb,1}, x_{rvpb,2}$ , and redundancy-version information for the second and the third transport blocks $x_{rvsb,1}, x_{rvsb,2}$ are multiplexed together. This gives a sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ where + +$$x_{2,i} = x_{tbspb,i} \quad i=1,2,\dots,6$$ + +$$x_{2,i} = x_{tbssb,i-6} \quad i=7,8,\dots,12$$ + +$$x_{2,i} = x_{hap,i-12} \quad i=13,14,\dots,16$$ + +$$x_{2,i} = x_{\text{rpb},i-16} \quad i=17,18$$ + +$$x_{2,i} = x_{\text{rsb},i-18} \quad i=19,20$$ + +#### 4.6D.4 CRC attachment for HS-SCCH type 4 + +If one transport block is transmitted on the associated HS-PDSCH(s), from the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,16}, x_{2,1}, x_{2,2}, \dots, x_{2,12}$ a 16-bit CRC is calculated according to Clause 4.2.1.1. This gives a sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,12}$ to form the sequence of bits $y_1, y_2, \dots, y_{28}$ , where + +$$y_i = x_{2,i} \quad i=1,2,\dots,12$$ + +$$y_i = (c_{i-12} + x_{ues,i-12}) \bmod 2 \quad i=13,14,\dots,28$$ + +If more than one transport blocks are transmitted on the associated HS-PDSCHs, from the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,16}, x_{2,1}, x_{2,2}, \dots, x_{2,20}$ a 16-bit CRC is calculated according to Clause 4.2.1.1. This gives a sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with the UE Identity $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ and then appended to the sequence of bits $x_{2,1}, x_{2,2}, \dots, x_{2,20}$ to form the sequence of bits $y_1, y_2, \dots, y_{36}$ , where + +$$y_i = x_{2,i} \quad i=1,2,\dots,20$$ + +$$y_i = (c_{i-20} + x_{ues,i-20}) \bmod 2 \quad i=21,22,\dots,36$$ + +#### 4.6D.5 Channel coding for HS-SCCH type 4 + +Rate 1/2 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $x_{1,1}, x_{1,2}, \dots, x_{1,16}$ . This gives a sequence of bits $z_{1,1}, z_{1,2}, \dots, z_{1,48}$ . + +If one transport block is transmitted on the associated HS-PDSCH(s), rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $y_1, y_2, \dots, y_{28}$ . This gives a sequence of bits $z_{2,1}, z_{2,2}, \dots, z_{2,108}$ . + +If more than one transport blocks are transmitted on the associated HS-PDSCHs, rate 1/3 convolutional coding, as described in Clause 4.2.3.1, is applied to the sequence of bits $y_1, y_2, \dots, y_{36}$ . This gives a sequence of bits $z_{2,1}, z_{2,2}, \dots, z_{2,132}$ . + +Note that the coded sequence lengths result from the termination of K=9 convolutional coding being fully applied. + +#### 4.6D.6 Rate matching for HS-SCCH type 4 + +From the input sequence $z_{1,1}, z_{1,2}, \dots, z_{1,48}$ the bits $z_{1,1}, z_{1,2}, z_{1,4}, z_{1,8}, z_{1,42}, z_{1,45}, z_{1,47}, z_{1,48}$ are punctured to obtain the output sequence $r_{1,1}, r_{1,2}, \dots, r_{1,40}$ . + +If one transport block is transmitted on the associated HS-PDSCH(s), from the input sequence $z_{2,1}, z_{2,2}, \dots, z_{2,108}$ the bits $z_{2,1}, z_{2,2}, z_{2,3}, z_{2,4}, z_{2,5}, z_{2,6}, z_{2,7}, z_{2,8}, z_{2,12}, z_{2,14}, z_{2,15}, z_{2,24}, z_{2,42}, z_{2,48}, z_{2,63}, z_{2,66}, z_{2,93}, z_{2,96}, z_{2,98}, z_{2,99}, z_{2,101}, z_{2,102}, z_{2,103}, z_{2,104}, z_{2,105}, z_{2,106}, z_{2,107}, z_{2,108}$ are punctured to obtain the output sequence $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ . + +If more than one transport blocks are transmitted on the associated HS-PDSCHs, from the input sequence $z_{2,1}, z_{2,2}, \dots, z_{2,132}$ the bits $z_{2,1}, z_{2,2}, z_{2,3}, z_{2,4}, z_{2,5}, z_{2,6}, z_{2,7}, z_{2,8}, z_{2,10}, z_{2,11}, z_{2,13}, z_{2,14}, z_{2,16}, z_{2,19}, z_{2,22}, z_{2,25}, z_{2,28}, z_{2,31}, z_{2,34}, z_{2,37}, z_{2,40}, z_{2,43}, z_{2,46}, z_{2,49}, z_{2,55}, z_{2,61}, z_{2,72}, z_{2,78}, z_{2,84}, z_{2,87}, z_{2,90}, z_{2,93}, z_{2,96}, z_{2,99}, z_{2,102}, z_{2,105}, z_{2,108}, z_{2,111}, z_{2,114}, z_{2,117}, z_{2,119}, z_{2,120}, z_{2,122}, z_{2,123}, z_{2,125}, z_{2,126}, z_{2,127}, z_{2,128}, z_{2,129}, z_{2,130}, z_{2,131}, z_{2,132}$ are punctured to obtain the output sequence $r_{2,1}, r_{2,2}, \dots, r_{2,80}$ . + +#### 4.6D.7 UE specific masking for HS-SCCH type 4 + +The output bits $s_{1,1}, s_{1,2}, \dots, s_{1,40}$ are calculated as described in subclause 4.6.7. + +## 4.6D.8 Physical channel mapping for HS-SCCH type 4 + +The HS-SCCH sub-frame is described in [2]. The physical channel mapping is carried out as described in subclause 4.6.8. + +## 4.7 Coding for HS-DPCCH + +### 4.7.1 Overview + +Data arrives to the coding unit in form of indicators for measurement indication and HARQ acknowledgement. + +The following coding/multiplexing steps can be identified: + +- channel coding (see subclauses 4.7.2, 4.7.3, 4.7.3A, 4.7.3B, 4.7.3C, 4.7.3D and 4.7.3E); +- mapping to physical channels (see subclause 4.7.4). + +The coding/multiplexing for HS-DPCCH is defined separately for the following cases: + +- when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in the serving HS-DSCH cell, and Secondary\_Cell\_Enabled is 0 or 1 and Secondary\_Cell\_Active is 0 (see subclause 4.7.2); +- when the UE is configured in MIMO mode in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0 (see subclause 4.7.3); +- when the UE is configured in MIMO mode in at least the serving HS-DSCH cell, and Secondary\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is 0 (see subclause 4.7.3B); +- when the UE is not configured in MIMO mode in any cell and Secondary\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is 1 (see subclause 4.7.3A); +- when the UE is configured in MIMO mode in at least one cell and Secondary\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is 1 (see subclause 4.7.3B); +- when Secondary\_Cell\_Enabled is equal to 2 or 3 (see applicable subclauses in Table 14C and 14D) +- when Secondary\_Cell\_Enabled is more than 3 (see applicable subclauses in Table 14C.1 and 14D.1) +- when the UE is configured in Multiflow mode, see subclause 4.7.3D +- when the UE is configured in MIMO mode with four transmit antennas at least in one cell, see subclause 4.7.3E + +where Secondary\_Cell\_Enabled and Secondary\_Cell\_Active are defined in [4]. + +**Table 14C: Coding for HARQ-ACK when Secondary\_Cell\_Enabled is 2 or 3** + +| Secondary_Cell_Active | Condition | Secondary Cell Enabled is 2
UE is configured with two secondary serving HS-DSCH cells | | | | +|-----------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|------------------------------------------------| +| | | Serving HS-DSCH cell | 1 st Secondary Serving HS-DSCH cell | 2 nd Secondary Serving HS-DSCH cell | 3 rd Secondary Serving HS-DSCH cell | +| 0, 1, 2 | MIMO mode and MIMO mode with four transmit antennas is not configured in any cell | 4.7.3C.1 (Note 1) | | | N/A | +| 0 | MIMO mode is configured in at least one cell | 4.7.3B.1 (Note 3) | | | N/A | +| 1 | MIMO mode is configured in at least one cell | 4.7.3B.1 (Note 2) | | | N/A | + +| | | | | | | +|------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------| +| 2 | MIMO mode is configured in at least one cell | 4.7.3B.1 | | 4.7.3B.1 (Note 4) | N/A | +| | Secondary Cell Enabled is 3
UE is configured with three secondary serving HS-DSCH cells | | | | | +| Secondary_Cell_Active | Condition | Serving HS-DSCH cell | 1st Secondary Serving HS-DSCH cell | 2nd Secondary Serving HS-DSCH cell | 3rd Secondary Serving HS-DSCH cell | +| 0 | - | 4.7.3B.1 (Note 3) | | | | +| 1 | - | 4.7.3B.1 (Note 2) | | | | +| 2, 3 | - | 4.7.3B.1 (Note 1) | | 4.7.3B.1 (Note 1) | | + +Note 1: When a cell is deactivated, DTX message is indicated for that cell. + +Note 2: HARQ-ACK information is jointly encoded for the pair of serving HS-DSCH cell and the active secondary serving HS-DSCH cell and repeated to fill the whole HARQ-ACK slot in the HS-DPCCH sub-frame as described in subclause 4.7.4.1. + +Note 3: HARQ-ACK information for the serving HS-DSCH cell is repeated to fill the whole HARQ-ACK slot in the HS-DPCCH sub-frame as described in subclause 4.7.4.1. + +Note 4: HARQ-ACK information for the 2nd secondary serving HS-DSCH cell is jointly encoded with a DTX message in place of the 3rd secondary serving HS-DSCH cell as described in subclause 4.7.3B.1. + +**Table 14C.1: Coding for HARQ-ACK of HS-DPCCH when Secondary\_Cell\_Enabled is more than 3** + +| | | | | | +|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------| +| | Secondary Cell Enabled is more than 3
UE is configured with more than 3 secondary serving HS-DSCH cells | | | | +| Number of active cells mapped to the HS-DPCCH | Serving HS-DSCH cell | 1st Secondary Serving HS-DSCH cell | 2nd Secondary Serving HS-DSCH cell | 3rd Secondary Serving HS-DSCH cell | +| 1 | 4.7.3B.1 (Note 1) | | | | +| 2 | 4.7.3B.1 (Note 2) | | | | +| 3 | 4.7.3B.1 (Note 3) | | 4.7.3B.1 (Note 3) | | +| 4 | 4.7.3B.1 | | 4.7.3B.1 | | + +Note 1: The HARQ-ACK information is repeated to fill the whole HARQ-ACK slot of HS-DPCCH sub-frame as described in subclause 4.7.4.1. + +Note 2: HARQ-ACK information is jointly encoded for the pair of serving HS-DSCH cell and the active secondary serving HS-DSCH cell and repeated to fill the whole HARQ-ACK slot in the HS-DPCCH sub-frame as described in subclause 4.7.4.1. + +Note 3: If one of the 1st, 2nd, or 3rd secondary serving HS-DSCH cells is deactivated a DTX message is indicated for the deactivated cell. + +**Table 14C.2: Coding for HARQ-ACK transmitted on HS-DPCCH2 when Secondary\_Cell\_Enabled is more than 3** + +| Number of active cells mapped to the HS-DPCCH 2 | Secondary Cell Enabled is more than 3
UE is configured with more than 3 secondary serving HS-DSCH cells | | | | +|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|------------------------------------------------| +| | 4 th secondary serving HS-DSCH cell | 5 th Secondary Serving HS-DSCH cell | 6 th Secondary Serving HS-DSCH cell | 7 th Secondary Serving HS-DSCH cell | +| 1 | 4.7.3B.1 (Note 1) | | | | +| 2 | 4.7.3B.1 (Note 2) | | | | +| 3 | 4.7.3B.1 (Note 3) | | 4.7.3B.1 (Note 3) | | +| 4 | 4.7.3B.1 | | 4.7.3B.1 | | + +Note 1: The HARQ-ACK information is repeated to fill the whole HARQ-ACK slot of HS-DPCCH2 sub-frame as described in subclause 4.7.4.1. + +Note 2: The HARQ-ACK information for the two activated secondary serving HS-DSCH cells are jointly encoded and repeated to fill the whole HARQ-ACK slot in the HS-DPCCH2 sub-frame as described in subclause 4.7.4.1. + +Note 3: If one of the 4th, 5th, 6th, and 7th secondary serving HS-DSCH cells is deactivated a DTX message is indicated for the deactivated cell. + +The order of the cells in HARQ-ACK joint encoding is specified in detail in subclause 4.7.4.1. + +**Table 14D: Coding for PCI/CQI when Secondary\_Cell\_Enabled is 2 or 3** + +| Secondary_Cell_Active | Secondary Cell Enabled is 2
UE is configured with two secondary serving HS-DSCH cells | | | | | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|--|--| +| | Serving HS-DSCH cell | 1 st Secondary Serving HS-DSCH cell | 2 nd Secondary Serving HS-DSCH cell | 3 rd Secondary Serving HS-DSCH cell | | | +| 0, 1 | The CQI information for a cell not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is encoded according to subclause 4.7.2.2(Note 1)The composite PCI/CQI information for a cell configured with MIMO mode is encoded according to subclause 4.7.3.2 (Note 3) | | | N/A | | | +| 2
MIMO is not configured in any cell | The CQI information for the serving HS-DSCH cell is encoded using subclause 4.7.2.2 | The CQI information for the 1 st secondary serving HS-DSCH cell and the 2 nd secondary serving HS-DSCH cell is encoded according to subclause 4.7.3A.2 | | N/A | | | +| 2 (Otherwise)
Note 4 | The CQI information for a cell not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is encoded according to subclause 4.7.2.2.
The composite PCI/CQI information for a cell configured with MIMO mode is encoded according to subclause 4.7.3.2 | | | N/A | | | +| Secondary_Cell_Active | Secondary Cell Enabled is 3
UE is configured with three secondary serving HS-DSCH cells | | | | | | +| | Serving HS-DSCH cell | 1 st Secondary Serving HS- | 2 nd Secondary Serving HS-DSCH | 3 rd Secondary Serving HS-DSCH | | | + +| | | DSCH cell | cell | cell | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------|------| +| 0, 1
Note 3 | The CQI information for a cell not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is encoded according to subclause 4.7.2.2.
The composite PCI/CQI information for a cell configured with MIMO mode is encoded according to subclause 4.7.3.2 | | | | +| 2, 3
Note 2 | | | | | + +Note 1: If the UE is configured with MIMO mode in at least one cell, the CQI field for each active cell is repeated to fill the two slot CQI field in the HS-DPCCH sub-frame as described in subclause 4.7.4.2. + +Note 2: In the deactivated cell, the PCI/CQI field is DTXed. + +Note 3: The CQI or PCI/CQI for each active cell is repeated to fill the two slot CQI or PCI/CQI field in the HS-DPCCH sub-frame as described in subclause 4.7.4.2. + +Note 4: The PCI/CQI field for the 3rd secondary serving HS-DSCH cell is DTXed. + +**Table 14D.1: Coding for PCI/CQI transmitted on HS-DPCCH when Secondary\_Cell\_Enabled is more than 3** + +| Number of active cells mapped to the HS-DPCCH | Secondary Cell Enabled more than 3
UE is configured with more than 3 secondary serving HS-DSCH cells | | | | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|------------------------------------------------| +| | Serving HS-DSCH cell | 1 st Secondary Serving HS-DSCH cell | 2 nd Secondary Serving HS-DSCH cell | 3 rd Secondary Serving HS-DSCH cell | +| 1, 2
Note 1 | The CQI information for a cell not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is encoded according to subclause 4.7.2.2.
The composite PCI/CQI information for a cell configured with MIMO mode is encoded according to subclause 4.7.3.2 | | | | +| 3, 4
Note 2 | | | | | + +Note 1: The CQI or PCI/CQI for each active cell is repeated to fill the two slot CQI or PCI/CQI field in the corresponding HS-DPCCH sub-frame as described in subclause 4.7.4.2. + +Note 2: In the deactivated cell, the PCI/CQI field is DTXed. + +**Table 14D.2: Coding for PCI/CQI transmitted on HS-DPCCH2 when Secondary\_Cell\_Enabled is more than 3** + +| Number of active cells mapped to the HS-DPCCH 2 | Secondary Cell Enabled more than 3
UE is configured with more than 3 secondary serving HS-DSCH cells | | | | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|------------------------------------------------| +| | 4 th Secondary serving HS-DSCH cell | 5 th Secondary Serving HS-DSCH cell | 6 th Secondary Serving HS-DSCH cell | 7 th Secondary Serving HS-DSCH cell | +| 1, 2
Note 1 | The CQI information for a cell not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is encoded according to subclause 4.7.2.2.
The composite PCI/CQI information for a cell configured with MIMO mode is encoded according to subclause 4.7.3.2 | | | | +| 3, 4
Note 2 | | | | | + +Note 1: The CQI or PCI/CQI for each active cell is repeated to fill the two slot CQI or PCI/CQI field in the corresponding HS-DPCCH sub-frame as described in subclause 4.7.4.2. + +Note 2: In the deactivated cell, the PCI/CQI field is DTXed. + +For each HS-DPCCH the general coding flow when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas is shown in the figure 20. This is done in parallel for the HARQ-ACK and CQI as the flows are not directly multiplexed but are transmitted at different times. + +![Figure 20: Coding for each HS-DPCCH when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas. The diagram shows two parallel processing flows. The left flow starts with HARQ-ACK, followed by a 'Channel coding' block, then an intermediate signal w0, w1, w2, ..., w9, then a 'Physical channel mapping' block, and finally PhCH. The right flow starts with CQI (a0, a1, ..., a4 OR a0, a1, ..., a9), followed by a 'Channel Coding' block, then an intermediate signal b0, b1, ..., b19, then a 'Physical channel mapping' block, and finally PhCH.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + + graph TD + subgraph LeftFlow [ ] + HARQ-ACK --> CC1[Channel coding] + CC1 --> W["w0, w1, w2, ..., w9"] + W --> PCM1[Physical channel mapping] + PCM1 --> PhCH1[PhCH] + end + subgraph RightFlow [ ] + CQI["CQI +a0, a1, ..., a4 OR a0, a1, ..., a9"] --> CC2[Channel Coding] + CC2 --> B["b0, b1, ..., b19"] + B --> PCM2[Physical channel mapping] + PCM2 --> PhCH2[PhCH] + end + style LeftFlow fill:none,stroke:none + style RightFlow fill:none,stroke:none + +``` + +Figure 20: Coding for each HS-DPCCH when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas. The diagram shows two parallel processing flows. The left flow starts with HARQ-ACK, followed by a 'Channel coding' block, then an intermediate signal w0, w1, w2, ..., w9, then a 'Physical channel mapping' block, and finally PhCH. The right flow starts with CQI (a0, a1, ..., a4 OR a0, a1, ..., a9), followed by a 'Channel Coding' block, then an intermediate signal b0, b1, ..., b19, then a 'Physical channel mapping' block, and finally PhCH. + +**Figure 20: Coding for each HS-DPCCH when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas** + +In case the UE is configured in MIMO mode, the measurement indication consists of precoding control indication (PCI) and channel quality indication (CQI). For each HS-DPCCH the general coding flow when the UE is configured in MIMO mode is shown in the figure 20A. This is done in parallel for the flow of HARQ-ACK and for the flow of composite PCI/CQI reports as the two flows are not directly multiplexed but are transmitted at different times + +![Figure 20A: Coding for each HS-DPCCH when the UE is configured in MIMO mode. The diagram shows two parallel processing flows. The left flow starts with HARQ-ACK, followed by a 'Channel coding' block, then an intermediate signal w0, w1, w2, ..., w9, then a 'Physical channel mapping' block, and finally PhCH. The right flow starts with Type A (PCI, CQI) (a0, a1, ..., a9) OR Type B (PCI, CQI) (a0, a1, ..., a6), followed by a 'Channel Coding' block, then an intermediate signal b0, b1, ..., b19, then a 'Physical channel mapping' block, and finally PhCH.](e20792fef9de6560b2d6c5441da7614a_img.jpg) + +``` + + graph TD + subgraph LeftFlow [ ] + HARQ-ACK --> CC1[Channel coding] + CC1 --> W["w0, w1, w2, ..., w9"] + W --> PCM1[Physical channel mapping] + PCM1 --> PhCH1[PhCH] + end + subgraph RightFlow [ ] + TypeA["Type A (PCI, CQI) +a0, a1, ..., a9"] --> CC2[Channel Coding] + TypeB["Type B (PCI, CQI) +a0, a1, ..., a6"] --> CC2 + CC2 --> B["b0, b1, ..., b19"] + B --> PCM2[Physical channel mapping] + PCM2 --> PhCH2[PhCH] + end + style LeftFlow fill:none,stroke:none + style RightFlow fill:none,stroke:none + +``` + +Figure 20A: Coding for each HS-DPCCH when the UE is configured in MIMO mode. The diagram shows two parallel processing flows. The left flow starts with HARQ-ACK, followed by a 'Channel coding' block, then an intermediate signal w0, w1, w2, ..., w9, then a 'Physical channel mapping' block, and finally PhCH. The right flow starts with Type A (PCI, CQI) (a0, a1, ..., a9) OR Type B (PCI, CQI) (a0, a1, ..., a6), followed by a 'Channel Coding' block, then an intermediate signal b0, b1, ..., b19, then a 'Physical channel mapping' block, and finally PhCH. + +**Figure 20A: Coding for each HS-DPCCH when the UE is configured in MIMO mode** + +In case the UE is configured in MIMO mode with four transmit antennas, the measurement indication consists of number of transport blocks preferred (NTBP), precoding control indication (PCI) and channel quality indication (CQI). For each HS-DPCCH the general coding flow when the UE is configured in MIMO mode with four transmit antennas is shown in the figure 20A.1. This is done in parallel for the flow of HARQ-ACK and for the flow of composite NTBP/PCI/CQI reports as the two flows are not directly multiplexed but are transmitted at different times + +![Figure 20A.1: Coding for each HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas. The diagram shows two parallel processing paths. The left path starts with HARQ-ACK input, followed by a 'Channel coding' block, then an intermediate output w0, w1, w2, ..., w19, then a 'Physical channel mapping' block, and finally the output PhCH. The right path starts with Type A (NTBP, PCI, CQI) input a0, a1, ..., a14 OR Type B (PCI, CQI) input a0, a1, ..., a9, followed by a 'Channel Coding' block, then an intermediate output b0, b1, ..., b39, then a 'Physical channel mapping' block, and finally the output PhCH.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +Figure 20A.1: Coding for each HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas. The diagram shows two parallel processing paths. The left path starts with HARQ-ACK input, followed by a 'Channel coding' block, then an intermediate output w0, w1, w2, ..., w19, then a 'Physical channel mapping' block, and finally the output PhCH. The right path starts with Type A (NTBP, PCI, CQI) input a0, a1, ..., a14 OR Type B (PCI, CQI) input a0, a1, ..., a9, followed by a 'Channel Coding' block, then an intermediate output b0, b1, ..., b39, then a 'Physical channel mapping' block, and finally the output PhCH. + +Figure 20A.1: Coding for each HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas + +4.7.2 Channel coding for HS-DPCCH when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0 or 1 and Secondary\_Cell\_Active is 0 + +Two forms of channel coding are used, one for the channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +#### 4.7.2.1 Channel coding for HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message to be transmitted, as defined in [4], shall be coded to 10 bits as shown in Table 15. The output is denoted $w_0, w_1, \dots, w_9$ . + +Table 15: Channel coding of HARQ-ACK when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0 or 1 and Secondary\_Cell\_Active is 0 + +| HARQ-ACK message to be transmitted | $w_0$ | $w_1$ | $w_2$ | $w_3$ | $w_4$ | $w_5$ | $w_6$ | $w_7$ | $w_8$ | $w_9$ | +|------------------------------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| ACK | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| NACK | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| PRE | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| POST | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +#### 4.7.2.2 Channel coding for HS-DPCCH channel quality indication + +The channel quality indication is coded using a (20,5) code. The code words of the (20,5) code are a linear combination of the 5 basis sequences denoted $M_{i,n}$ defined in the table below. + +**Table 15A: Basis sequences for (20,5) code** + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | +|----|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 1 | +| 1 | 0 | 1 | 0 | 0 | 1 | +| 2 | 1 | 1 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 1 | +| 4 | 1 | 0 | 1 | 0 | 1 | +| 5 | 0 | 1 | 1 | 0 | 1 | +| 6 | 1 | 1 | 1 | 0 | 1 | +| 7 | 0 | 0 | 0 | 1 | 1 | +| 8 | 1 | 0 | 0 | 1 | 1 | +| 9 | 0 | 1 | 0 | 1 | 1 | +| 10 | 1 | 1 | 0 | 1 | 1 | +| 11 | 0 | 0 | 1 | 1 | 1 | +| 12 | 1 | 0 | 1 | 1 | 1 | +| 13 | 0 | 1 | 1 | 1 | 1 | +| 14 | 1 | 1 | 1 | 1 | 1 | +| 15 | 0 | 0 | 0 | 0 | 1 | +| 16 | 0 | 0 | 0 | 0 | 1 | +| 17 | 0 | 0 | 0 | 0 | 1 | +| 18 | 0 | 0 | 0 | 0 | 1 | +| 19 | 0 | 0 | 0 | 0 | 1 | + +The CQI values 0 ... 30 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (1 0 0 0 0) to (1 1 1 1 1) respectively. The information bit pattern (0 0 0 0 0) shall not be used in this release. The channel quality indication bits are a0, a1, a2, a3, a4 (where a0 is LSB and a4 is MSB). The output code word bits bi are given by: + +where i = 0, ..., 19. + +#### 4.7.3 Channel coding for HS-DPCCH when the UE is configured in MIMO mode in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0 + +Two forms of channel coding are used, one for the composite precoding control indication (PCI) and channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +##### 4.7.3.1 Channel coding for HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message to be transmitted, as defined in [4], shall be coded to 10 bits as shown in Table 15B. The output is denoted w0, w1, ..., w9. + +**Table 15B: Channel coding of HARQ-ACK when the UE is configured in MIMO mode in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0** + +| HARQ-ACK message to be transmitted | | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | +|------------------------------------------------------------|---------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| HARQ-ACK in response to a single scheduled transport block | | | | | | | | | | | | +| ACK | | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| NACK | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| HARQ-ACK in response to two scheduled transport blocks | | | | | | | | | | | | +| Response to primary transport block | Response to secondary transport block | | | | | | | | | | | +| ACK | ACK | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| ACK | NACK | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | + +| | | | | | | | | | | | | +|---------------------|------|---|---|---|---|---|---|---|---|---|---| +| | | | | | | | | | | | | +| NACK | ACK | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | +| NACK | NACK | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| PRE/POST indication | | | | | | | | | | | | +| PRE | | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| POST | | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +#### 4.7.3.2 Channel coding for HS-DPCCH composite precoding control indication and channel quality indication + +When the UE is configured in MIMO mode and single-stream restriction is not configured, two types of CQI reports shall be supported by the UE. According to the definition of the CQI reporting procedure in [4], type A CQI reports use values 0 ... 255 and type B CQI reports use values 0 ... 30, respectively. When the UE is configured in MIMO mode and single-stream restriction is configured, only type B shall be supported by the UE. + +##### 4.7.3.2.1 Bit mapping of Type A channel quality indication + +In case a type A CQI shall be reported, the CQI values 0 ... 255 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (0 0 0 0 0 0 0 0) to (1 1 1 1 1 1 1 1), respectively. The channel quality indication bits are $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4, cqi_5, cqi_6, cqi_7$ (where $cqi_0$ is LSB and $cqi_7$ is MSB). + +##### 4.7.3.2.2 Bit mapping of Type B channel quality indication + +In case a type B CQI shall be reported, the CQI values 0 ... 30 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (1 0 0 0 0) to (1 1 1 1 1), respectively. The information bit pattern (0 0 0 0 0) shall not be used in this release. The channel quality indication bits are $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4$ (where $cqi_0$ is LSB and $cqi_4$ is MSB). + +##### 4.7.3.2.3 Bit mapping of precoding control indication + +According to the PCI definition in [4], the range of possible PCI values is 0 ... 3. The PCI values 0 ... 3 as defined in [4] are converted from decimal to binary to map them to the precoding control indication bits (0 0) to (1 1) respectively. The precoding control indication bits are $pci_0, pci_1$ (where $pci_0$ is LSB and $pci_1$ is MSB). + +##### 4.7.3.2.4 Composite precoding control indication and channel quality indication bits + +Two formats for composite PCI/CQI information words are possible depending on the type of the reported CQI value. The two formats shall be constructed according to the scheme depicted in Figure 20B. + +![Figure 20B: Construction of composite PCI/CQI report. The diagram shows two parallel processing paths. The left path takes PCI as input to a 'Binary mapping' block, which outputs bits pci0, pci1. The right path takes either Type A CQI or Type B CQI as input to a 'Binary mapping' block. Type A CQI outputs bits cqi0, cqi1, ..., cqi7. Type B CQI outputs bits cqi0, cqi1, ..., cqi4. Both outputs from the binary mapping blocks are fed into a 'concatenation' block. The final output of the concatenation block is either a0, a1, ..., a9 (for Type A CQI) or a0, a1, ..., a6 (for Type B CQI).](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +``` + +graph TD + PCI[PCI] --> BM1[Binary mapping] + BM1 --> pci[pci0, pci1] + TCQI[Type A CQI OR Type B CQI] --> BM2[Binary mapping] + BM2 --> cqiA[cqi0, cqi1, ..., cqi7] + BM2 --> cqiB[cqi0, cqi1, ..., cqi4] + pci --> CONCAT[concatenation] + cqiA --> CONCAT + cqiB --> CONCAT + CONCAT --> aA[a0, a1, ..., a9] + CONCAT --> aB[a0, a1, ..., a6] + +``` + +Figure 20B: Construction of composite PCI/CQI report. The diagram shows two parallel processing paths. The left path takes PCI as input to a 'Binary mapping' block, which outputs bits pci0, pci1. The right path takes either Type A CQI or Type B CQI as input to a 'Binary mapping' block. Type A CQI outputs bits cqi0, cqi1, ..., cqi7. Type B CQI outputs bits cqi0, cqi1, ..., cqi4. Both outputs from the binary mapping blocks are fed into a 'concatenation' block. The final output of the concatenation block is either a0, a1, ..., a9 (for Type A CQI) or a0, a1, ..., a6 (for Type B CQI). + +**Figure 20B: Construction of composite PCI/CQI report** + +In case a type A CQI shall be reported, the precoding control indication bits $pci_0, pci_1$ , and the channel quality indication bits $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4, cqi_5, cqi_6, cqi_7$ are concatenated to the composite precoding control indication and channel quality indication bits according to the relation + +In case a type B CQI shall be reported, the precoding control indication bits $pci_0, pci_1$ , and the channel quality indication bits $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4$ are concatenated to the composite precoding control indication and channel quality indication bits according to the relation + +#### 4.7.3.2.5 Block encoding of composite precoding control indication and channel quality indication bits + +In case a type A CQI needs to be reported, the composite precoding control indication and channel quality indication is coded using a (20,10) code. The code words of the (20,10) code are a linear combination of the 10 basis sequences denoted $M_{i,n}$ defined in the table 15C below. + +**Table 15C: Basis sequences for channel encoding of composite PCI/CQI reports** + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | M i,6 | M i,7 | M i,8 | M i,9 | M i,10 | +|----|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------| +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 3 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | +| 4 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| 5 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | +| 6 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | +| 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| 8 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | +| 9 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | +| 10 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | +| 11 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | +| 12 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | +| 13 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | +| 14 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | +| 15 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | +| 16 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| 17 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | +| 18 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | +| 19 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | + +The output code word bits $b_i$ are given by: + +where $i = 0, \dots, 19$ . + +In case a type B CQI needs to be reported, the composite precoding control indication and channel quality indication is coded using a (20,7) code. The code words of the (20,7) code are a linear combination of the basis sequences denoted $M_{i,n}$ defined in the table 15C for. + +The output code word bits $b_i$ are given by: + +where $i = 0, \dots, 19$ . + +#### 4.7.3A Channel coding for HS-DPCCH when the UE is not configured in MIMO mode in any cell and Secondary\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is 1 + +Two forms of channel coding are used, one for the composite channel quality indication (CQI) and another for the composite HARQ-ACK (acknowledgement). + +##### 4.7.3A.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +The composite HARQ acknowledgement message to be transmitted, as defined in [4], shall be coded to 10 bits as shown in Table 15C.1. The output is denoted $w_0, w_1, \dots, w_9$ . + +**Table 15C.1: Channel coding of HARQ-ACK when the UE is not configured in MIMO mode in a pair of serving HS-DSCH cells and Secondary\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is 1** + +| HARQ-ACK message to be transmitted | $w_0$ | $w_1$ | $w_2$ | $w_3$ | $w_4$ | $w_5$ | $w_6$ | $w_7$ | $w_8$ | $w_9$ | +|-----------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| HARQ-ACK when UE detects a single scheduled transport block on the serving HS-DSCH cell | | | | | | | | | | | +| ACK | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | + +| | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|---|---|---|---|---|---|---|---|---|---| +| NACK | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| HARQ-ACK when UE detects a single scheduled transport block on the secondary serving HS-DSCH cell | | | | | | | | | | | | +| ACK | | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | +| NACK | | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | +| HARQ-ACK when UE detects a single scheduled transport block on each of the serving and secondary serving HS-DSCH cells | | | | | | | | | | | | +| Response to transport block from serving HS-DSCH cell | Response to transport block from secondary serving HS-DSCH cell | | | | | | | | | | | +| ACK | ACK | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | +| ACK | NACK | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| NACK | ACK | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | +| NACK | NACK | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| PRE/POST indication | | | | | | | | | | | | +| PRE | | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| POST | | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +#### 4.7.3A.2 Channel coding for HS-DPCCH composite channel quality indication + +##### 4.7.3A.2.1 Composite channel quality indication bits + +The composite CQI report is constructed from two individual CQI reports that are represented by CQI1 and CQI2. CQI1 corresponds to the serving HS-DSCH cell and CQI2 corresponds to the secondary serving HS-DSCH cell. + +Each constituent CQI report uses values 0 ... 30 in accordance with the definition of the CQI reporting procedure in [4]. The individual CQI values are converted from decimal to binary to map them to the channel quality indication bits (1 0 0 0 0) to (1 1 1 1 1) respectively. The information bit pattern (0 0 0 0 0) shall not be used in this release. + +The channel quality indication bits corresponding to CQI1 are $cqi1_0, cqi1_1, cqi1_2, cqi1_3, cqi1_4$ (where $cqi1_0$ is LSB and $cqi1_4$ is MSB) and those corresponding to CQI2 are $cqi2_0, cqi2_1, cqi2_2, cqi2_3, cqi2_4$ (where $cqi2_0$ is LSB and $cqi2_4$ is MSB). + +The composite CQI report is constructed according to the scheme depicted in Figure 20C + +![Figure 20C: Construction of composite CQI report. The diagram shows two input CQI reports, CQI1 and CQI2, each passing through a 'Binary mapping' block. The output of the first block is a sequence cqi1_0, cqi1_1, ..., cqi1_4. The output of the second block is a sequence cqi2_0, cqi2_1, ..., cqi2_4. These two sequences are then concatenated in a 'concatenation' block to produce the final composite CQI report a_0, a_1, ..., a_9.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +graph TD + CQI1[CQI1] --> BM1[Binary mapping] + CQI2[CQI2] --> BM2[Binary mapping] + BM1 --> C1["cqi10, cqi11, ..., cqi14"] + BM2 --> C2["cqi20, cqi21, ..., cqi24"] + C1 --> CONCAT[concatenation] + C2 --> CONCAT + CONCAT --> AC["a0, a1, ..., a9"] + +``` + +Figure 20C: Construction of composite CQI report. The diagram shows two input CQI reports, CQI1 and CQI2, each passing through a 'Binary mapping' block. The output of the first block is a sequence cqi1\_0, cqi1\_1, ..., cqi1\_4. The output of the second block is a sequence cqi2\_0, cqi2\_1, ..., cqi2\_4. These two sequences are then concatenated in a 'concatenation' block to produce the final composite CQI report a\_0, a\_1, ..., a\_9. + +**Figure 20C: Construction of composite CQI report** + +The two individual CQI reports are concatenated to form the composite channel quality indication according to the relation + +#### 4.7.3A.2.2 Block encoding of composite channel quality indication bits + +The composite channel quality indication is coded using a (20,10) code. The code words of the (20,10) code are a linear combination of the 10 basis sequences denoted $M_{i,n}$ defined in Table 15C. + +The output code word bits $b_i$ are given by: + +where $i = 0, \dots, 19$ and $a_0, \dots, a_9$ are defined in the previous subclause. + +### 4.7.3B Channel coding for HS-DPCCH when Secondary\_Cell\_Enabled is at least 3 or when the UE is configured in MIMO mode in at least one cell and Secondary\_Cell\_Enabled is greater than 0 + +Two forms of channel coding are used, one for the composite precoding control indication (PCI) and channel quality indication (CQI) and another for the composite HARQ-ACK (acknowledgement). + +#### 4.7.3B.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +The composite HARQ acknowledgement message to be transmitted, as defined in [4], shall be coded to 10 bits as shown in Table 15C.2. The feedback related to the first cell is given before the divider sign and the feedback related to the second cell is given after the divider sign. 'A' means 'ACK', 'N' means 'NACK' and 'D' means 'no transmission' ('DTX'). 'AA', 'AN', 'NA' and 'NN' refer to feedback for dual-stream transmission in a cell. For example, 'AN' means ACK on the primary stream and NACK on the secondary stream. The output is denoted $w_0, w_1, \dots, w_9$ . + +When Secondary\_Cell\_Enabled is 2, and when Secondary\_Cell\_Active is 2, HARQ-ACK information for the 2nd secondary serving HS-DSCH cell is jointly encoded with a DTX message in place of the 3rd secondary serving HS-DSCH cell. + +When Secondary\_Cell\_Enabled is 4, and when Secondary\_Cell\_Active is 4, HARQ-ACK information for the 4th secondary serving HS-DSCH cell is jointly encoded with a DTX message in place of the 5th secondary serving HS-DSCH cell. + +When Secondary\_Cell\_Enabled is 6, and when Secondary\_Cell\_Active is 6, HARQ-ACK information for the 6th secondary serving HS-DSCH cell is jointly encoded with a DTX message in place of the 7th secondary serving HS-DSCH cell. + +**Table 15C.2: Channel coding of HARQ-ACK when Secondary\_Cell\_Enabled is at least 3 or the UE is configured in MIMO mode in at least one cell and Secondary\_Cell\_Enabled is greater than 0** + +| HARQ-ACK message to be transmitted | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | HARQ-ACK message to be transmitted | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | +|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| A/D | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | AA/A | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | +| N/D | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | AA/N | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | +| AA/D | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | AN/A | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | +| AN/D | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | AN/N | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | +| NA/D | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | NA/A | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| NN/D | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | NA/N | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | +| D/A | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | NN/A | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | +| D/N | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | NN/N | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | +| D/AA | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | AA/AA | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | +| D/AN | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | AA/AN | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| D/NA | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | AA/NA | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| D/NN | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | AA/NN | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | +| A/A | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | AN/AA | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | +| A/N | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | AN/AN | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | +| N/A | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | AN/NA | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | +| N/N | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | AN/NN | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | +| A/AA | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | NA/AA | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| A/AN | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | NA/AN | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | +| A/NA | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | NA/NA | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| A/NN | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | NA/NN | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | +| N/AA | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | NN/AA | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | +| N/AN | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | NN/AN | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | +| N/NA | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | NN/NA | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| N/NN | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | NN/NN | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| PRE/POST | | | | | | | | | | | | | | | | | | | | | | +| PRE | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | POST | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +When Secondary\_Cell\_Active is 2 or 3, and when DTX message is indicated for a cell pair, whose HARQ-ACK information is jointly encoded, the specific DTX code word as defined in Table 15C.2A is transmitted for that cell pair except for the case when DTX message is indicated for all active cells, in which case the HARQ-ACK slot is DTXed. The slot containing HARQ-ACK information is either transmitted or DTXed. If Secondary\_Cell\_Active is larger than 3 and when DTX message is indicated for both cell pairs transmitted on one of the two HS-DPCCHs and there is at least one HARQ-ACK message associated with the other HS-DPCCH that does not correspond to DTX message, then the specific DTX code word as defined in Table 15C.2A is transmitted for all cell pairs for which a DTX message is indicated. If the DTX message is indicated for all active cell pairs then the slot on each respective HS-DPCCH containing the HARQ-ACK information is DTXed. + +**Table 15C.2A: Channel coding of HARQ-ACK for a pair of DTX messages when Secondary\_Cell\_Active is greater than 2** + +| HARQ-ACK message to be transmitted | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | +|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| D/D | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | + +#### 4.7.3B.2 Channel coding for HS-DPCCH composite precoding control indication and channel quality indication + +The channel coding for CQI associated with a cell for which the UE is not configured in MIMO mode is specified in subclause 4.7.2.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. + +#### 4.7.3C Channel coding for HS-DPCCH when the UE is not configured in MIMO mode in any cell and Secondary\_Cell\_Enabled is 2 + +Two forms of channel coding are used, one for the composite channel quality indication (CQI) and another for the composite HARQ-ACK (acknowledgement). + +##### 4.7.3C.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +**Table 15C.3: Channel coding of HARQ-ACK when the UE is not configured in MIMO mode in any cell and Secondary\_Cell\_Enabled is 2** + +| HARQ-ACK message to be transmitted | W 0 | W 1 | W 2 | W 3 | W 4 | W 5 | W 6 | W 7 | W 8 | W 9 | +|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| A/D/D | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| N/D/D | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| D/A/D | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | +| D/N/D | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | +| D/D/A | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | +| D/D/N | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | +| A/A/D | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | +| A/N/D | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| N/A/D | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | +| N/N/D | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| A/D/A | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| A/D/N | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | +| N/D/A | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| N/D/N | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | +| D/A/A | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | +| D/A/N | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | +| D/N/A | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | +| D/N/N | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| A/A/A | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | +| A/A/N | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | +| A/N/A | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | +| A/N/N | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | +| N/A/A | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | +| N/A/N | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | +| N/N/A | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | +| N/N/N | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | +| PRE/POST | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----|---|---|---|---|---|---|---|---|---|---|------|---|---|---|---|---|---|---|---|---|---| +| PRE | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | POST | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | +|-----|---|---|---|---|---|---|---|---|---|---|------|---|---|---|---|---|---|---|---|---|---| + +#### 4.7.3C.2 Channel coding for HS-DPCCH channel quality indication + +The channel coding for CQI is specified in subclause 4.7.2.2 for the serving HS-DSCH cell, and in subclause 4.7.3A.2 for the 1st and 2nd secondary serving HS-DSCH cells. + +#### 4.7.3D Channel coding for HS-DPCCH when the UE is configured in Multiflow mode + +##### 4.7.3D.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +Subclause 4.7.4.3 defines the applicable HARQ-ACK encoding to be used with the following exception + +- When the UE is configured with one serving and one assisting HS-DSCH cell and at least one of the two cells is configured in MIMO mode the HARQ-ACK encoding is defined in Table 15C.3A. + +**Table 15C.3A: Channel coding of HARQ-ACK when the UE is configured with one serving and one assisting HS-DSCH cell and at least one cell is configured in MIMO mode** + +| HARQ-ACK message to be transmitted | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | HARQ-ACK message to be transmitted | w 0 | w 1 | w 2 | w 3 | w 4 | w 5 | w 6 | w 7 | w 8 | w 9 | +|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| A/D | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | AA/A | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| N/D | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | AA/N | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | +| AA/D | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | AN/A | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | +| AN/D | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | AN/N | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | +| NA/D | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | NA/A | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| NN/D | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | NA/N | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| D/A | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | NN/A | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| D/N | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | NN/N | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | +| D/AA | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | AA/AA | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| D/AN | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | AA/AN | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| D/NA | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | AA/NA | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | +| D/NN | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | AA/NN | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | +| A/A | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | AN/AA | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | +| A/N | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | AN/AN | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | +| N/A | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | AN/NA | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | +| N/N | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | AN/NN | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | +| A/AA | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | NA/AA | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| A/AN | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | NA/AN | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| A/NA | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | NA/NA | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | +| A/NN | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | NA/NN | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| N/AA | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | NN/AA | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| N/AN | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | NN/AN | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | +| N/NA | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | NN/NA | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | +| N/NN | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | NN/NN | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | +| PRE/POST | | | | | | | | | | | | | | | | | | | | | | +| PRE | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | POST | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +#### 4.7.3D.2 Channel coding for HS-DPCCH channel quality indication + +Subclause 4.7.4.3 defines the applicable CQI encoding to be used with different Multiflow configurations. + +#### 4.7.3E Channel coding for HS-DPCCH when the UE is configured in MIMO mode with 4 transmit antennas + +The coding for HS-DPCCH is defined separately for the following cases: + +- when the UE is configured in MIMO mode with four transmit antennas and Secondary\_Cell\_Enabled is 0 (see subclause 4.7.3E.1); +- when the UE is configured in MIMO mode with four transmit antennas in any cell, and Secondary\_Cell\_Enabled is 1 (see subclause 4.7.3E.2); +- when the UE is configured in MIMO mode with four transmit antennas in any cell, and Secondary\_Cell\_Enabled is 2 (see subclause 4.7.3E.3); +- when the UE is configured in MIMO mode with four transmit antennas in any cell, and Secondary\_Cell\_Enabled is 3 (see subclause 4.7.3E.4); + +##### 4.7.3E.1 Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas and Secondary\_Cell\_Enabled is 0 + +Two forms of channel coding are used, one for the composite number of transport blocks preferred (NTBP), precoding control indication (PCI) and channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +###### 4.7.3E.1.1 Channel coding for HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message to be transmitted, as defined in [4], shall be coded to 10 bits as shown in Table 15C.3B. The output is denoted $g_0, g_1, \dots, g_9$ . + +When three or four transport blocks are received, the second and the third transport blocks are positively acknowledged (ACK) only if both transport blocks are received correctly. Otherwise both the second and the third transport blocks are negatively acknowledged (NACK). + +When four transport blocks are received, the first and the fourth transport blocks are positively acknowledged (ACK) only if both transport blocks are received correctly. Otherwise both the first and the fourth transport blocks are negatively acknowledged (NACK). + +**Table 15C.3B: Channel coding of HARQ-ACK when the UE is configured in MIMO mode with four transmit antennas in the serving HS-DSCH cell and Secondary\_Cell\_Enabled is 0** + +| HARQ-ACK message to be transmitted | | $g_0$ | $g_1$ | $g_2$ | $g_3$ | $g_4$ | $g_5$ | $g_6$ | $g_7$ | $g_8$ | $g_9$ | +|------------------------------------------------------------|------------------------------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| HARQ-ACK in response to a single scheduled transport block | | | | | | | | | | | | +| ACK | | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| NACK | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| HARQ-ACK in response to two scheduled transport blocks | | | | | | | | | | | | +| Response to primary transport block | Response to second transport block | | | | | | | | | | | +| ACK | ACK | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| ACK | NACK | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | +| NACK | ACK | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | + +| | | | | | | | | | | | | +|----------------------------------------------------------|-----------------------------------------------|---|---|---|---|---|---|---|---|---|---| +| NACK | NACK | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| HARQ-ACK in response to three scheduled transport blocks | | | | | | | | | | | | +| Response to primary transport block | Response to second and third transport blocks | | | | | | | | | | | +| ACK | ACK | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| ACK | NACK | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | +| NACK | ACK | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | +| NACK | NACK | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| HARQ-ACK in response to four scheduled transport blocks | | | | | | | | | | | | +| Response to primary and fourth transport blocks | Response to second and third transport blocks | | | | | | | | | | | +| ACK | ACK | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| ACK | NACK | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | +| NACK | ACK | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | +| NACK | NACK | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| PRE/POST indication | | | | | | | | | | | | +| PRE | | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| POST | | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | + +The output bits $g_0, g_1, \dots, g_9$ are repeated as shown in Figure 20C.0 + +![Flowchart of HARQ-ACK message processing: HARQ-ACK -> Channel coding -> Repetition -> Physical channel mapping -> PhCH. Output bits g_0, g_1, ..., g_9 are shown after Channel coding, and input bits w_0, w_1, w_2, ..., w_19 are shown before Physical channel mapping.](ceb9a4217df4b6e301712b3b88b09c69_img.jpg) + +``` + +graph TD + HARQ_ACK[HARQ-ACK] --> CC[Channel coding] + CC -- "g_0, g_1, ..., g_9" --> R[Repetition] + R -- "w_0, w_1, w_2, ..., w_19" --> PCM[Physical channel mapping] + PCM --> PhCH[PhCH] + +``` + +Flowchart of HARQ-ACK message processing: HARQ-ACK -> Channel coding -> Repetition -> Physical channel mapping -> PhCH. Output bits g\_0, g\_1, ..., g\_9 are shown after Channel coding, and input bits w\_0, w\_1, w\_2, ..., w\_19 are shown before Physical channel mapping. + +**Figure 20C.0: Repetition of HARQ-ACK message** + +In Figure 20C.0, the repetition is according to the relation: + +#### 4.7.3E.1.2 Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication + +When the UE is configured in MIMO mode with four transmit antennas two types of CQI reports shall be supported by the UE. According to the definition of the CQI reporting procedure in [4], in type A CQI reporting the number of transport blocks preferred is up to four and in type B CQI reporting the number of transport blocks preferred is one. + +##### 4.7.3E.1.2.1 Bit mapping of Type A channel quality indication + +In case a type A CQI shall be reported, the CQI values 0 ... 255 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (0 0 0 0 0 0 0 0) to (1 1 1 1 1 1 1 1), respectively. The channel quality indication bits are $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4, cqi_5, cqi_6, cqi_7$ (where $cqi_0$ is LSB and $cqi_7$ is MSB). + +In case the number of transport blocks preferred is one, the CQI values 0 ... 30 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (1 0 0 0 0) to (1 1 1 1 1), respectively. The information bit pattern (0 0 0 0 0) shall not be used in this release. The channel quality indication bits are $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4$ (where $cqi_0$ is LSB and $cqi_4$ is MSB) and (0 0 0) is used for indicating $cqi_5, cqi_6, cqi_7$ (where $cqi_5$ is LSB and $cqi_7$ is MSB). + +##### 4.7.3E.1.2.2 Bit mapping of Type B channel quality indication + +In case a type B CQI shall be reported, the CQI values 0 ... 30 as defined in [4] are converted from decimal to binary to map them to the channel quality indication bits (1 0 0 0 0) to (1 1 1 1 1), respectively. The information bit pattern (0 0 0 0 0) shall not be used in this release. The channel quality indication bits are $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4$ (where $cqi_0$ is LSB and $cqi_4$ is MSB). + +##### 4.7.3E.1.2.3 Bit mapping of number of transport blocks preferred + +According to the number of transport blocks preferred definition in [4], the range of possible values is 0 ... 3. The number of transport blocks preferred values 0 ... 3 as defined in [4] are converted from decimal to binary to map them to the number of transport blocks preferred bits (0 0) to (1 1) respectively. The number of transport blocks preferred bits are $ri_0, ri_1$ (where $ri_0$ is LSB and $ri_1$ is MSB). + +##### 4.7.3E.1.2.4 Bit mapping of precoding control indication + +According to the PCI definition in [4], the range of possible PCI values is 0 ... 15. The PCI values 0 ... 15 as defined in [4] are converted from decimal to binary to map them to the precoding control indication bits (0 0,0,0) to (1 1,1,1) respectively. The precoding control indication bits are $pci_0, pci_1, pci_2, pci_3$ (where $pci_0$ is LSB and $pci_3$ is MSB). + +##### 4.7.3E.1.2.5 Composite number of transport blocks preferred, precoding control indication and channel quality indication bits + +For type A CQI report the composite NTBP/PCI/CQI shall be constructed according to the scheme depicted in Figure 20C.1. + +![Figure 20C.1: Construction of composite NTBP/PCI/CQI for Type A CQI report. The diagram shows three input signals: NTBP, PCI, and Type A CQI. NTBP and PCI are each processed through a 'Binary mapping' block. The output of the NTBP mapping is labeled ri_0, ri_1. The output of the PCI mapping is labeled pci_0, ..., pci_3. The Type A CQI is processed through a 'Binary mapping' block, with the output labeled cqi_0, cqi_1, ..., cqi_7. All three outputs are then concatenated in a 'concatenation' block. The final output of the concatenation is labeled a_0, a_1, ..., a_13.](d8bc70513c482a0b8bb6d99e43de623e_img.jpg) + +``` + +graph TD + NTBP --> BM1[Binary mapping] + PCI --> BM2[Binary mapping] + TCQI[Type A CQI] --> BM3[Binary mapping] + BM1 --> ri["ri_0, ri_1"] + BM2 --> pci["pci_0, ..., pci_3"] + BM3 --> cqi["cqi_0, cqi_1, ..., cqi_7"] + ri --> C[concatenation] + pci --> C + cqi --> C + C --> a["a_0, a_1, ..., a_13"] + +``` + +Figure 20C.1: Construction of composite NTBP/PCI/CQI for Type A CQI report. The diagram shows three input signals: NTBP, PCI, and Type A CQI. NTBP and PCI are each processed through a 'Binary mapping' block. The output of the NTBP mapping is labeled ri\_0, ri\_1. The output of the PCI mapping is labeled pci\_0, ..., pci\_3. The Type A CQI is processed through a 'Binary mapping' block, with the output labeled cqi\_0, cqi\_1, ..., cqi\_7. All three outputs are then concatenated in a 'concatenation' block. The final output of the concatenation is labeled a\_0, a\_1, ..., a\_13. + +Figure 20C.1: Construction of composite NTBP/PCI/CQI for Type A CQI report + +In case a type A CQI shall be reported, the number of transport blocks preferred bits $ri_0, ri_1$ , precoding control indication bits $pci_0, pci_1, pci_2, pci_3$ , and the channel quality indication bits $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4, cqi_5, cqi_6, cqi_7$ are concatenated to the composite number of transport blocks preferred, precoding control indication and channel quality indication bits according to the relation + +For type B CQI report the composite PCI/CQI shall be constructed according to the scheme depicted in Figure 20C.2. + +![Figure 20C.2: Construction of composite NTBP/PCI/CQI for Type B CQI report. The diagram shows two input streams, PCI and Type B CQI, each entering a 'Binary mapping' block. The output of the PCI mapping is labeled pci_0...pci_3, and the output of the Type B CQI mapping is labeled cqi_0, cqi_1, ...cqi_4. Both outputs are then fed into a 'concatenation' block, which produces the final output sequence a_0, a_1, ..., a_8.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) + +``` + +graph TD + PCI[PCI] --> BM1[Binary mapping] + TBCQI[Type B CQI] --> BM2[Binary mapping] + BM1 --> pci_bits[pci_0...pci_3] + BM2 --> cqi_bits[cqi_0, cqi_1, ...cqi_4] + pci_bits --> CONCAT[concatenation] + cqi_bits --> CONCAT + CONCAT --> output[a_0, a_1, ..., a_8] + +``` + +Figure 20C.2: Construction of composite NTBP/PCI/CQI for Type B CQI report. The diagram shows two input streams, PCI and Type B CQI, each entering a 'Binary mapping' block. The output of the PCI mapping is labeled pci\_0...pci\_3, and the output of the Type B CQI mapping is labeled cqi\_0, cqi\_1, ...cqi\_4. Both outputs are then fed into a 'concatenation' block, which produces the final output sequence a\_0, a\_1, ..., a\_8. + +**Figure 20C.2: Construction of composite NTBP/PCI/CQI for Type B CQI report** + +In case a type B CQI shall be reported, the precoding control indication bits $pci_0, pci_1, pci_2, pci_3$ , and the channel quality indication bits $cqi_0, cqi_1, cqi_2, cqi_3, cqi_4$ are concatenated to the composite precoding control indication and channel quality indication bits according to the relation + +#### 4.7.3E.1.2.6 Channel coding for composite number of transport blocks preferred, precoding control indication and channel quality indication bits + +In case a type A CQI needs to be reported, rate 1/2 convolutional coding, as described in Clause 4.2.3.1 is applied to the sequence of bits $a_0, a_1, \dots, a_{13}$ , resulting in the sequence of bits $d_0, d_1, \dots, d_{43}$ . + +Note that the coded sequence lengths result from the termination of K=9 convolutional coding being fully applied. + +In case a type B CQI needs to be reported, rate 1/3 convolutional coding, as described in Clause 4.2.3.1 is applied to the sequence of bits $a_0, a_1, \dots, a_8$ , resulting in the sequence of bits $d_0, d_1, \dots, d_{50}$ . + +Note that the coded sequence lengths result from the termination of K=9 convolutional coding being fully applied. + +#### 4.7.3E.1.2.7 Rate matching for composite number of transport blocks preferred, precoding control indication and channel quality indication bits + +In case a type A CQI needs to be reported, from the input sequence $d_0, d_1, \dots, d_{43}$ the bits $d_0, d_2, d_{41}, d_{43}$ are punctured to obtain the output sequence $b_0, b_1, \dots, b_{39}$ . + +In case a type B CQI needs to be reported, from the input sequence $d_0, d_1, \dots, d_{50}$ the bits $d_0, d_2, d_3, d_4, d_6, d_{44}, d_{45}, d_{46}, d_{47}, d_{48}, d_{50}$ are punctured to obtain the output sequence $b_0, b_1, \dots, b_{39}$ . + +#### 4.7.3E.2 Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary\_Cell\_Enabled is 1 + +Two forms of channel coding are used, one for the composite number of transport blocks preferred (NTBP), precoding control indication (PCI) and channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +#### 4.7.3E.2.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode with four transmit antennas shall be coded to 10 bits as in Table 15C.3B in subclause 4.7.3E.1.1. + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode shall be coded to 10 bits as in Table 15B in subclause 4.7.3.1. + +The HARQ acknowledgement message associated with a cell for which the UE is configured not in MIMO mode and not in MIMO mode with four transmit antennas shall be coded to 10 bits as specified in Table 15 in subclause 4.7.2. + +The HARQ acknowledgement messages corresponding to the serving HS-DSCH cell and secondary serving HS-DSCH cell in that order are encoded and concatenated into the same slot according to Figure 20D in clause 4.7.4.1. + +#### 4.7.3E.2.2 Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication + +The channel coding for NTBP, PCI and CQI associated with a cell for which the UE is configured in MIMO mode with four transmit antennas is specified in subclause 4.7.3E.1.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. + +The channel coding for CQI associated with a cell for which the UE is configured not in MIMO mode and not in MIMO mode with four transmit antennas is specified in subclause 4.7.2.2. + +#### 4.7.3E.3 Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary\_Cell\_Enabled is 2 + +Two forms of channel coding are used, one for the composite number of transport blocks preferred (NTBP), precoding control indication (PCI) and channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +##### 4.7.3E.3.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode with four transmit antennas shall be coded to 10 bits as in Table 15C.3B in subclause 4.7.3E.1.1. + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode shall be coded to 10 bits as in Table 15B in subclause 4.7.3.1. + +The HARQ acknowledgement message associated with a cell for which the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas shall be coded to 10 bits as specified in Table 15 in subclause 4.7.2. + +The HARQ acknowledgement messages corresponding to the serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order are encoded and concatenated into the same slot according to Figure 20D in clause 4.7.4.1. + +#### 4.7.3E.3.2 Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication + +The channel coding for NTBP, PCI and CQI associated with a cell for which the UE is configured in MIMO mode with four transmit antennas is specified in subclause 4.7.3E.1.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured not in MIMO mode and not in MIMO mode with four transmit antennas is specified in subclause 4.7.2.2. + +#### 4.7.3E.4 Channel coding for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in any cell and Secondary\_Cell\_Enabled is 3 + +Two forms of channel coding are used, one for the composite number of transport blocks preferred (NTBP), precoding control indication (PCI) and channel quality indication (CQI) and another for HARQ-ACK (acknowledgement). + +#### 4.7.3E.4.1 Channel coding for the composite HS-DPCCH HARQ-ACK + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode with four transmit antennas shall be coded to 10 bits as in Table 15C.3B in subclause 4.7.3E.1.1. + +The HARQ acknowledgement message associated with a cell for which the UE is configured in MIMO mode shall be coded to 10 bits as in Table 15B in subclause 4.7.3.1. + +The HARQ acknowledgement message associated with a cell for which the UE is configured not in MIMO mode and not in MIMO mode with four transmit antennas shall be coded to 10 bits as specified in Table 15 in subclause 4.7.2. + +The HARQ acknowledgement messages corresponding to the serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order are encoded and concatenated into the same slot according to Figure 20D in clause 4.7.4.1. + +The HARQ acknowledgement messages corresponding to the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order are encoded and concatenated into the same slot according to Figure 20D.1 in clause 4.7.4.1. + +#### 4.7.3E.4.2 Channel coding for HS-DPCCH composite number of transport blocks preferred, precoding control indication and channel quality indication + +The channel coding for NTBP, PCI and CQI associated with a cell for which the UE is configured in MIMO mode with four transmit antennas is specified in subclause 4.7.3E.1.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. + +The channel coding for PCI and CQI associated with a cell for which the UE is configured not in MIMO mode and not in MIMO mode with four transmit antennas is specified in subclause 4.7.2.2. + +### 4.7.4 Physical channel mapping for HS-DPCCH + +#### 4.7.4.1 Physical Channel mapping for HS-DPCCH HARQ-ACK + +This section is not applicable when the UE is configured in MIMO mode with four transmit antennas in at least one cell. + +If the HS-DPCCH slot format 0 as defined in [2] is used, the HS-DPCCH physical channel mapping function shall map the input bits $w_k$ directly to physical channel so that bits are transmitted over the air in ascending order with respect to $k$ . + +If the HS-DPCCH slot format 1 as defined in [2], is used, the HS-DPCCH physical channel mapping function shall map the input bits $w_k$ to the physical channel so that bits are transmitted over the air in ascending order with respect to $k$ as follows: + +- If Secondary\_Cell\_Enabled is equal to 7 and Secondary\_Cell\_Active is equal to 7 + - The following two HARQ-ACK messages are transmitted on HS-DPCCH according to Figure 20D: + - HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and + - HARQ-ACK2 comprising the HARQ acknowledgement messages for the pair of the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order + - The following two HARQ-ACK messages are transmitted on HS-DPCCH2 according to Figure 20D.1: + - HARQ-ACK3 comprising the HARQ acknowledgement messages for the pair of the 4th secondary serving HS-DSCH cell and the 5th secondary serving HS-DSCH cell in that order + - HARQ-ACK4 comprising the HARQ acknowledgement messages for the pair of the 6th secondary serving HS-DSCH cell and the 7th secondary serving HS-DSCH cell in that order +- If Secondary\_Cell\_Enabled is equal to 6 and Secondary\_Cell\_Active is equal to 6 + - The following two HARQ-ACK messages are transmitted on HS-DPCCH according to Figure 20D: + +- HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and +- HARQ-ACK2 comprising the HARQ acknowledgement messages for the pair of the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order +- The following two HARQ-ACK messages are transmitted on HS-DPCCH2 according to Figure 20D.1: + - HARQ-ACK3 comprising the HARQ acknowledgement messages for the pair of the 4th secondary serving HS-DSCH cell and the 5th secondary serving HS-DSCH cell in that order + - HARQ-ACK4 comprising the HARQ acknowledgement messages for the 6th secondary serving HS-DSCH cell and a DTX message in that order +- If Secondary\_Cell\_Enabled is equal to 5 and Secondary\_Cell\_Active is equal to 5 + - The following two HARQ-ACK messages are transmitted on HS-DPCCH according to Figure 20D: + - HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and + - HARQ-ACK2 comprising the HARQ acknowledgement messages for the pair of the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order + - The following HARQ-ACK message is transmitted on HS-DPCCH2: + - The HARQ acknowledgement messages for the pair of the 4th secondary serving HS-DSCH cell and the 5th secondary serving HS-DSCH cell are repeated according to Figure 20E. +- If Secondary\_Cell\_Enabled is equal to 4 and Secondary\_Cell\_Active is equal to 4 + - The following two HARQ-ACK messages are transmitted on HS-DPCCH according to Figure 20D: + - HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and + - HARQ-ACK2 comprising the HARQ acknowledgement messages for the pair of the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order + - The following two HARQ-ACK messages are transmitted on HS-DPCCH2: + - The HARQ-ACK comprising the HARQ acknowledgement the 4th secondary serving HS-DSCH cell and a DTX message in that order and it is repeated according to Figure 20E. +- If Secondary\_Cell\_Enabled is greater than 3 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - If none of the 4th, 5th, 6th, or 7th secondary serving HS-DSCH cell is activated the HARQ-ACK transmissions on HS-DPCCH2 are DTXed + - If at most one of the 1st, 2nd, or 3rd secondary serving HS-DSCH cell is activated the HARQ-ACK message is repeated according to Figure 20E + - If one of the 4th, 5th, 6th, and 7th secondary serving HS-DSCH cell is activated the HARQ-ACK message is repeated according to Figure 20E. + - If two of the 4th, 5th, 6th and 7th secondary serving HS-DSCH cell are active the HARQ-ACK comprises the HARQ acknowledgement messages for the pair of the secondary serving HS-DSCH cell with lowest index as indicated by higher layers and the other activated secondary serving HS-DSCH cell in that order. The HARQ-ACK message is repeated according to Figure 20E. + - Otherwise the transmissions of the HARQ-ACK messages is the same as if Secondary\_Cell\_Active was equal to Secondary\_Cell\_Enabled but where DTX message(s) is transmitted in place of deactivated secondary serving HS-DSCH cells. +- If Secondary\_Cell\_Enabled is 3 and Secondary\_Cell\_Active is 2 or 3 then the following two HARQ-ACK messages are encoded and concatenated into the same slot according to Figure 20D : + +- HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and +- HARQ-ACK2 comprising the HARQ acknowledgement messages for the pair of 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order +- If Secondary\_Cell\_Enabled is 2 with MIMO configured in at least one of the cells and Secondary\_Cell\_Active is 2 then the following two HARQ-ACK messages, are encoded and concatenated into the same slot according to Figure 20D: + - HARQ-ACK1 comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order and + - HARQ-ACK2 comprising the HARQ acknowledgement messages for the 2nd secondary serving HS-DSCH cell and a DTX message in that order +- If Secondary\_Cell\_Enabled is more than 1 and Secondary\_Cell\_Active is 0 or 1 then the transmission of the HARQ-ACK message is repeated according to Figure 20E. + +![Flowchart of HARQ-ACK message concatenation process](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +``` +graph TD; HARQ-ACK1[HARQ-ACK1] --> CC1[Channel Coding]; HARQ-ACK2[HARQ-ACK2] --> CC2[Channel Coding]; CC1 --> ack1["ack1_0, ack1_1, ..., ack1_9"]; CC2 --> ack2["ack2_0, ack2_1, ..., ack2_9"]; ack1 --> Concat[Concatenation]; ack2 --> Concat; Concat --> w["w_0, w_1, w_2, ..., w_9, w_10, w_11, ..., w_19"]; w --> PCM[Physical Channel Mapping]; PCM --> PhCh[PhCh]; +``` + +The diagram illustrates the processing flow for two HARQ-ACK messages. HARQ-ACK1 and HARQ-ACK2 are each processed through a 'Channel Coding' block. The output of the first channel coding block is a sequence of acknowledgements: ack10, ack11, ..., ack19. The output of the second channel coding block is: ack20, ack21, ..., ack29. These two sequences are then combined in a 'Concatenation' block. The resulting concatenated sequence is: w0, w1, w2, ..., w9, w10, w11, ..., w19. This sequence is then processed through 'Physical Channel Mapping' to produce the final output, PhCh. + +Flowchart of HARQ-ACK message concatenation process + +**Figure 20D: Concatenation of 2 HARQ-ACK messages** + +In Figure 20D, the concatenation of the 2 HARQ-ACK messages is according to the relation: + +![Flowchart showing the concatenation of two HARQ-ACK messages (HARQ-ACK3 and HARQ-ACK4) on HS-DPCCH2. Both messages are first processed through Channel Coding to produce ack3_0, ack3_1, ..., ack3_9 and ack4_0, ack4_1, ..., ack4_9. These are then concatenated to form a combined sequence w_0, w_1, w_2, ..., w_9, w_10, w_11, ..., w_19, which is then mapped to the Physical Channel (PhCh).](72d448a65347c51989171748789c7d4b_img.jpg) + +``` + +graph TD + HARQ-ACK3[HARQ-ACK3] --> CC3[Channel Coding] + HARQ-ACK4[HARQ-ACK4] --> CC4[Channel Coding] + CC3 --> ack3["ack30, ack31, ..., ack39"] + CC4 --> ack4["ack40, ack41, ..., ack49"] + ack3 --> Concat[Concatenation] + ack4 --> Concat + Concat --> w["w0, w1, w2, ..., w9, w10, w11, ..., w19"] + w --> PCM[Physical Channel Mapping] + PCM --> PhCh[PhCh] + +``` + +Flowchart showing the concatenation of two HARQ-ACK messages (HARQ-ACK3 and HARQ-ACK4) on HS-DPCCH2. Both messages are first processed through Channel Coding to produce ack3\_0, ack3\_1, ..., ack3\_9 and ack4\_0, ack4\_1, ..., ack4\_9. These are then concatenated to form a combined sequence w\_0, w\_1, w\_2, ..., w\_9, w\_10, w\_11, ..., w\_19, which is then mapped to the Physical Channel (PhCh). + +**Figure 20D.1: Concatenation of 2 HARQ-ACK messages on HS-DPCCH2** + +![Flowchart showing the repetition of a HARQ-ACK message. The HARQ-ACK message is first processed through Channel Coding to produce ack_0, ack_1, ..., ack_9. This is then processed through Repetition to form a combined sequence w_0, w_1, w_2, ..., w_9, w_10, w_11, ..., w_19, which is then mapped to the Physical Channel (PhCh).](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +``` + +graph TD + HARQ-ACK[HARQ-ACK] --> CC[Channel Coding] + CC --> ack["ack0, ack1, ..., ack9"] + ack --> Rep[Repetition] + Rep --> w["w0, w1, w2, ..., w9, w10, w11, ..., w19"] + w --> PCM[Physical Channel Mapping] + PCM --> PhCh[PhCh] + +``` + +Flowchart showing the repetition of a HARQ-ACK message. The HARQ-ACK message is first processed through Channel Coding to produce ack\_0, ack\_1, ..., ack\_9. This is then processed through Repetition to form a combined sequence w\_0, w\_1, w\_2, ..., w\_9, w\_10, w\_11, ..., w\_19, which is then mapped to the Physical Channel (PhCh). + +**Figure 20E: Repetition of HARQ-ACK message** + +In Figure 20E, the repetition of the HARQ-ACK message is according to the relation: + +#### 4.7.4.2 Physical Channel mapping for HS-DPCCH PCI/CQI + +Table 15C.4 lists the CQI and PCI/CQI report mapping scenarios when Secondary\_Cell\_Enabled is less than 4. Tables 15C.5 and 15C.6 list the CQI and PCI/CQI report mapping scenarios when Secondary\_Cell\_Enabled is greater than 3. The transmission timing and repetition of the 1st and the 2nd CQI and PCI/CQI report is defined in [4]. + +**Table 15C.4: The CQI and PCI/CQI report mapping scenarios when Secondary\_Cell\_Enabled is less than 4** + +| Case | Secondary_Cell_Enabled | MIMO configured in any cell | HS-DPCCH slot format | Secondary_Cell_Active | 1 st CQI or PCI/CQI report | | 2 nd CQI or PCI/CQI report | | | +|------|------------------------|-----------------------------|----------------------|-----------------------|-----------------------------------------------|-----------------------------|-----------------------------------------------|--------------------------------|--| +| | | | | | CQI or PCI/CQI Type A/B | | CQI or PCI/CQI Type A/B | | | +| 1 | 0 | No | 0 | 0 | CQI | | Not applicable | | | +| 2 | | Yes | 0 | 0 | PCI/CQI | | Not applicable | | | +| 3 | 1
Note 2 | No | 0 | 1 | CQI 0 & CQI 1
Note 5 | | Not applicable | | | +| 4 | | | | 0 | CQI 0 | | Not applicable | | | +| 5 | | Yes
Note 1 | | 1 | PCI/CQI 0 | | PCI/CQI 1 | | | +| 6 | | | | 0 | PCI/CQI 0 | | DTX | | | +| 7 | 2
Note 2 | No | 0 | 2 | CQI 0 | | CQI 1 & CQI 2
Note 5 | | | +| 8 | | | | 1 | CQI 0 | | CQI n
Note 4 | | | +| 9 | | | | 0 | CQI 0 | | DTX | | | +| | | | | | CQI 1 or PCI/CQI 1 Type A/B | CQI 2 or PCI/CQI 2 Type A/B | CQI 1 or PCI/CQI 1 Type A/B | CQI 2 or PCI/CQI 2 Type A/B | | +| 10 | 2
Note 2 | Yes
Note 1 | 1 | 2 | PCI/CQI 0 | PCI/CQI 2 | PCI/CQI 1 | DTX | | +| 11 | | | | 1 | PCI/CQI 0 | PCI/CQI 0 | PCI/CQI n
Note 4 | PCI/CQI n
Note 4 | | +| 12 | | | | 0 | PCI/CQI 0 | PCI/CQI 0 | DTX | | | +| 13 | 3
Note 2 | No | 1 | 3 | CQI 0 | CQI 2 | CQI 1 | CQI 3 | | +| 14 | | | | 2 | CQI 0 | CQI 2
Note 3 | CQI 1
Note 3 | CQI 3
Note 3 | | +| 15 | | | | 1 | CQI 0 | CQI 0 | CQI n
Note 4 | CQI n
Note 4 | | +| 16 | | | | 0 | CQI 0 | CQI 0 | DTX | | | +| 17 | | Yes | 1 | 3 | PCI/CQI 0 | PCI/CQI 2 | PCI/CQI 1 | PCI/CQI 3 | | + +| | | | | | | | | | +|----|--|--------|--|---|----------------------|--------------------------------|--------------------------------|--------------------------------| +| 18 | | Note 1 | | 2 | PCI/CQI 0 | PCI/CQI 2
Note 3 | PCI/CQI 1
Note 3 | PCI/CQI 3
Note 3 | +| 19 | | | | 1 | PCI/CQI 0 | PCI/CQI 0 | PCI/CQI n
Note 4 | PCI/CQI n
Note 4 | +| 20 | | | | 0 | PCI/CQI 0 | PCI/CQI 0 | | DTX | + +Note 1: If the UE is configured in MIMO mode in at least one cell, but not in all cells, a CQI value is reported instead of PCI/CQI value for the non-MIMO cell(s). + +Note 2: The CQI0 and PCI/CQI0 refer to the serving HS-DSCH cell's CQI and PCI/CQI reports respectively, the CQIn and PCI/CQIn refer to the nth secondary serving HS-DSCH cell's reports. + +Note 3: The deactivated secondary cell's CQI or PCI/CQI is not transmitted (DTX'd). + +Note 4: The CQI or the PCI/CQI of the single active secondary cell is transmitted. + +Note 5: The two CQI values are jointly encoded. + +**Table 15C.5: The CQI and PCI/CQI report mapping for HS-DPCCH when Secondary\_Cell\_Enabled is greater than 3.** + +| Case | Secondary_Cell_Enabled | MIMO configured in any cell | HS-DPCCH slot format | Active secondary cells out of 1 st , 2 nd , 3 rd secondary cell | 1 st CQI or PCI/CQI report | | 2 nd CQI or PCI/CQI report | | +|------|------------------------|-----------------------------|----------------------|--------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------|---------------------------------------|--------------------------------| +| | | | | | CQI 1 or PCI/CQI 1 Type A/B | CQI 2 or PCI/CQI 2 Type A/B | CQI 1 or PCI/CQI 1 Type A/B | CQI 2 or PCI/CQI 2 Type A/B | +| 21a | 4-7
Note 2 | No | 1 | 3 | CQI 0 | CQI 2 | CQI 1 | CQI 3 | +| 22a | | | | 2 | CQI 0 | CQI 2
Note 3 | CQI 1
Note 3 | CQI 3
Note 3 | +| 23a | | | | 1 | CQI 0 | CQI 0 | CQI n
Note 4 | CQI n
Note 4 | +| 24a | | | | 0 | CQI 0 | CQI 0 | DTX | | +| 25a | | Yes
Note 1 | 1 | 3 | PCI/CQI 0 | PCI/CQI 2 | PCI/CQI 1 | PCI/CQI 3 | +| 26a | | | | 2 | PCI/CQI 0 | PCI/CQI 2
Note 3 | PCI/CQI 1
Note 3 | PCI/CQI 3
Note 3 | +| 27a | | | | 1 | PCI/CQI 0 | PCI/CQI 0 | PCI/CQI n
Note 4 | PCI/CQI n
Note 4 | +| 28a | | | | 0 | PCI/CQI 0 | PCI/CQI 0 | DTX | | + +Note 1: If the UE is configured in MIMO mode in at least one cell, but not in all cells, a CQI value is reported instead of PCI/CQI value for the non-MIMO cell(s). + +Note 2: The CQI0 and PCI/CQI0 refer to the serving HS-DSCH cell's CQI and PCI/CQI reports respectively, the CQIn and PCI/CQIn refer to the nth secondary serving HS-DSCH cell's reports, and $n \in \{1,2,3\}$ . + +Note 3: The deactivated secondary cell's CQI or PCI/CQI is not transmitted (DTX'd). + +Note 4: The CQI or the PCI/CQI of the single active secondary cell is transmitted. + +**Table 15C.6: The CQI and PCI/CQI report mapping for HS-DPCCH2 when Secondary\_Cell\_Enabled is greater than 3.** + +| Case | Secondary_Cell_Enabled | MIMO configured in any cell | HS-DPCCH slot format | Active secondary cells out of 4 th , 5 th , 6 th and 7 th secondary cell | 3 rd CQI or PCI/CQI report | | 4 th CQI or PCI/CQI report | | +|------|------------------------|-----------------------------|----------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------|---------------------------------------|--------------------------------| +| | | | | | CQI 3 or PCI/CQI 3 Type A/B | CQI 4 or PCI/CQI 4 Type A/B | CQI 3 or PCI/CQI 3 Type A/B | CQI 4 or PCI/CQI 4 Type A/B | +| 21b | 4-7
Note 2 | No | 1 | 4 | CQI 4 | CQI 6 | CQI 5 | CQI 7 | +| 22b | | | | 3 | CQI 4
Note 3 | CQI 6
Note 3 | CQI 5
Note 3 | CQI 7
Note 3 | +| 23b | | | | 2 | CQI n
Note 2 | CQI n
Note 2 | CQI m
Note 2 | CQI m
Note 2 | +| 24b | | | | 1 | CQI n
Note 4 | CQI n
Note 4 | DTX | | +| 25b | | | | 0 | DTX | | DTX | | +| 26b | | Yes
Note 1 | 1 | 4 | PCI/CQI 4 | PCI/CQI 6 | PCI/CQI 5 | PCI/CQI 7 | +| 27b | | | | 3 | PCI/CQI 4
Note 3 | PCI/CQI 6
Note 3 | PCI/CQI 5
Note 3 | PCI/CQI 7
Note 3 | +| 28b | | | | 2 | PCI/CQI n
Note 2 | PCI/CQI n
Note 2 | PCI/CQI m
Note 2 | PCI/CQI m
Note 2 | +| 29b | | | | 1 | PCI/CQI n
Note 4 | PCI/CQI n
Note 4 | DTX | | +| 30b | | | | 0 | DTX | | DTX | | + +Note 1: If the UE is configured in MIMO mode in at least one cell, but not in all cells, a CQI value is reported instead of PCI/CQI value for the non-MIMO cell(s). + +Note 2: The CQIn and PCI/CQIn refer to the *n*th secondary serving HS-DSCH cell's reports, and the CQIm and PCI/CQIm refer to the *m*th secondary serving HS-DSCH cell's reports, where $n < m$ and $\{n, m\} \subset \{4,5,6,7\}$ . + +Note 3: The deactivated secondary cells' CQI or PCI/CQI is not transmitted (DTX'd). + +Note 4: The CQI or the PCI/CQI of the single active secondary cell out of the 4th, 5th, 6th and 7th secondary cells is transmitted. + +If the HS-DPCCH slot format 0 as defined in [2] is used, the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to physical channel so that bits are transmitted over the air in ascending order with respect to k. When Secondary\_Cell\_Active is 2, the CQI reports for each of the following groups are mapped to separate subframes as specified in [4]: + +- The report for the serving HS-DSCH cell (CQI) is mapped according to the physical channel mapping of CQI in Figure 20. +- The report for the 1st secondary serving HS-DSCH cell (CQI 1) and the 2nd secondary serving HS-DSCH cell (CQI 2) are mapped according to Figure 20C and according to the physical channel mapping of CQI in Figure 20. + +If the HS-DPCCH slot format 1 as defined in [2] is used and Secondary\_Cell\_Enabled is less than 4, the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ to the physical channel so that bits are transmitted over the air in ascending order with respect to k as follows: + +- When Secondary\_Cell\_Active is 3, the CQI or PCI/CQI reports for each of the following pairs are mapped to separate subframes as specified in [4]: + - The report for the serving HS-DSCH cell (CQI 1 or PCI/CQI 1) and the 2nd secondary serving HS-DSCH cell (CQI 2 or PCI/CQI 2) are mapped according to Figure 20F. + - The report for the 1st secondary serving HS-DSCH cell (CQI 1 or PCI/CQI 1) and the 3rd secondary serving HS-DSCH cell (CQI 2 or PCI/CQI 2) are mapped according to Figure 20F. +- When Secondary\_Cell\_Active is 2, the mapping of the CQI or PCI/CQI reports is the same as the case when Secondary\_Cell\_Active is 3 with the following exception: In the subframe in which only one active cell is mapped, the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to the physical + +channel in the corresponding slot of the CQI (or PCI/CQI) field of that subframe while the other slot of the CQI (or PCI/CQI) field is DTXed. + +- When Secondary\_Cell\_Active is 0 or 1, the CQI or PCI/CQI report for each active cell is mapped to a separate subframe as specified in [4]. In each subframe, the HS-DPCCH physical channel mapping function shall map the input bits to the physical channel according to Figure 20G. + +If the HS-DPCCH slot format 1 as defined in [2] is used and Secondary\_Cell\_Enabled is greater than 3, the HS-PDCCH physical channel mapping function shall map the input bits $b_k$ to the physical channel so that bits are transmitted over the air in ascending order with respect to $k$ as follows: + +- When Secondary\_Cell\_Active is 7, the CQI or PCI/CQI reports for each of the following pairs are mapped to separate subframes as specified in [4]: + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1) and the 2nd secondary serving HS-DSCH cell (CQI2 or PCI/CQI2) are mapped according to Figure 20F. + - The report for the 1st secondary serving HS-DSCH cell (CQI1 or PCI/CQI1) and the 3rd secondary serving HS-DSCH cell (CQI2 or PCI/CQI2) are mapped according to Figure 20F. + - The following is transmitted on HS-DPCCH2: + - The report for the 4th secondary serving HS-DSCH cell (CQI3 or PCI/CQI3) and the 6th secondary serving HS-DSCH cell (CQI4 or PCI/CQI4) are mapped according to Figure 20F.1. + - The report for the 5th secondary serving HS-DSCH cell (CQI3 or PCI/CQI3) and the 7th secondary serving HS-DSCH cell (CQI4 or PCI/CQI4) are mapped according to Figure 20F.1. +- When Secondary\_Cell\_Active is less than 7 the mapping of the CQI or PCI/CQI reports is the same as the case when Secondary\_Cell\_Active is 7 with the following exceptions: + - When one of the 1st, 2nd or 3rd secondary serving HS-DSCH cell is deactivated the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to the physical channel in the corresponding slot of the CQI (or PCI/CQI) field of that subframe while the other slot of the CQI (or PCI/CQI) field is DTXed in the subframe in which only one active cell is mapped. + - When one of the 4th, 5th, 6th or 7th secondary serving HS-DSCH cell is deactivated the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to the physical channel in the corresponding slot of the CQI (or PCI/CQI) field of that subframe while the other slot of the CQI (or PCI/CQI) field is DTXed in the subframe in which only one active cell is mapped. + - If at most one of the 1st, 2nd, or 3rd secondary serving HS-DSCH cell is activated the CQI or PCI/CQI report for each active cell is mapped to a separate subframe as specified in [4]. In each subframe, the HS-DPCCH physical channel mapping function shall map the input bits to the physical channel according to Figure 20G. + - If at most two of the 4th, 5th, 6th or 7th secondary serving HS-DSCH cell is activated the CQI or PCI/CQI report for each active cell is mapped to a separate subframe as specified in [4]. In each subframe, the HS-DPCCH physical channel mapping function shall map the input bits to the physical channel according to Figure 20G. + +![Flowchart showing the concatenation of CQI (or PCI/CQI) reports for two sub-frames. Inputs include CQI 1, PCI/CQI 1 Type A, and PCI/CQI 1 Type B (ORed) entering a Channel Coding block to produce cqi1_0 to cqi1_19. Similarly, CQI 2, PCI/CQI 2 Type A, and PCI/CQI 2 Type B (ORed) enter another Channel Coding block to produce cqi2_0 to cqi2_19. These are then concatenated to form b_0 to b_39, which are mapped via Physical Channel Mapping to PhCh.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` +graph TD; subgraph Group1 [ ]; CQI1[CQI 1] --> OR1[OR]; PC1A[PCI/CQI 1 Type A] --> OR1; PC1B[PCI/CQI 1 Type B] --> OR1; OR1 --> CC1[Channel Coding]; end; subgraph Group2 [ ]; CQI2[CQI 2] --> OR2[OR]; PC2A[PCI/CQI 2 Type A] --> OR2; PC2B[PCI/CQI 2 Type B] --> OR2; OR2 --> CC2[Channel Coding]; end; CC1 --> Cqi1["cqi1_0, cqi1_1, ..., cqi1_19"]; CC2 --> Cqi2["cqi2_0, cqi2_1, ..., cqi2_19"]; Cqi1 --> Concat[Concatenation]; Cqi2 --> Concat; Concat --> B["b_0, b_1, ..., b_39"]; B --> PCM[Physical Channel Mapping]; PCM --> PhCh[PhCh]; +``` + +Flowchart showing the concatenation of CQI (or PCI/CQI) reports for two sub-frames. Inputs include CQI 1, PCI/CQI 1 Type A, and PCI/CQI 1 Type B (ORed) entering a Channel Coding block to produce cqi1\_0 to cqi1\_19. Similarly, CQI 2, PCI/CQI 2 Type A, and PCI/CQI 2 Type B (ORed) enter another Channel Coding block to produce cqi2\_0 to cqi2\_19. These are then concatenated to form b\_0 to b\_39, which are mapped via Physical Channel Mapping to PhCh. + +**Figure 20F: Concatenation of CQI (or PCI/CQI) reports in the CQI (or PCI/CQI) field of a sub-frame** + +In Figure 20F, the two individual CQI (or PCI/CQI) reports are concatenated to form the composite channel quality indication according to the relation + +![Flowchart showing the concatenation of CQI (or PCI/CQI) reports for two sub-frames (3 and 4). Inputs include CQI 3, PCI/CQI 3 Type A, and PCI/CQI 3 Type B (ORed) entering a Channel Coding block to produce cqi3_0 to cqi3_19. Similarly, CQI 4, PCI/CQI 4 Type A, and PCI/CQI 4 Type B (ORed) enter another Channel Coding block to produce cqi4_0 to cqi4_19. These are then concatenated to form b_0 to b_39, which are mapped via Physical Channel Mapping to PhCh.](b11b654648249b38a82129a35555b481_img.jpg) + +``` +graph TD; subgraph Group3 [ ]; CQI3[CQI 3] --> OR3[OR]; PC3A[PCI/CQI 3 Type A] --> OR3; PC3B[PCI/CQI 3 Type B] --> OR3; OR3 --> CC3[Channel Coding]; end; subgraph Group4 [ ]; CQI4[CQI 4] --> OR4[OR]; PC4A[PCI/CQI 4 Type A] --> OR4; PC4B[PCI/CQI 4 Type B] --> OR4; OR4 --> CC4[Channel Coding]; end; CC3 --> Cqi3["cqi3_0, cqi3_1, ..., cqi3_19"]; CC4 --> Cqi4["cqi4_0, cqi4_1, ..., cqi4_19"]; Cqi3 --> Concat[Concatenation]; Cqi4 --> Concat; Concat --> B["b_0, b_1, ..., b_39"]; B --> PCM[Physical Channel Mapping]; PCM --> PhCh[PhCh]; +``` + +Flowchart showing the concatenation of CQI (or PCI/CQI) reports for two sub-frames (3 and 4). Inputs include CQI 3, PCI/CQI 3 Type A, and PCI/CQI 3 Type B (ORed) entering a Channel Coding block to produce cqi3\_0 to cqi3\_19. Similarly, CQI 4, PCI/CQI 4 Type A, and PCI/CQI 4 Type B (ORed) enter another Channel Coding block to produce cqi4\_0 to cqi4\_19. These are then concatenated to form b\_0 to b\_39, which are mapped via Physical Channel Mapping to PhCh. + +**Figure 20F.1: Concatenation of CQI (or PCI/CQI) reports in the CQI (or PCI/CQI) field of a sub-frame on HS-DPCCH2.** + +![Flowchart of CQI or PCI/CQI report processing. Inputs: CQI 1, PCI/CQI 1 Type A, and PCI/CQI 1 Type B. CQI 1 and PCI/CQI 1 Type A are combined via an OR operation. The result and PCI/CQI 1 Type B are then processed by Channel Coding. The output of Channel Coding is a sequence of 20 bits (cqi0, cqi1, ..., cqi19). This sequence is then processed by Repetition, resulting in 40 bits (b0, b1, ..., b39). Finally, these bits are processed by Physical Channel Mapping to produce the Physical Channel (PhCh).](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +``` + +graph TD + CQI1[CQI 1] -- OR --> CC[Channel Coding] + PCICQI1A[PCI/CQI 1 Type A] -- OR --> CC + PCICQI1B[PCI/CQI 1 Type B] --> CC + CC -- "cqi0, cqi1, ..., cqi19" --> R[Repetition] + R -- "b0, b1, ..., b39" --> PCM[Physical Channel Mapping] + PCM --> PhCh[PhCh] + +``` + +Flowchart of CQI or PCI/CQI report processing. Inputs: CQI 1, PCI/CQI 1 Type A, and PCI/CQI 1 Type B. CQI 1 and PCI/CQI 1 Type A are combined via an OR operation. The result and PCI/CQI 1 Type B are then processed by Channel Coding. The output of Channel Coding is a sequence of 20 bits (cqi0, cqi1, ..., cqi19). This sequence is then processed by Repetition, resulting in 40 bits (b0, b1, ..., b39). Finally, these bits are processed by Physical Channel Mapping to produce the Physical Channel (PhCh). + +**Figure 20G: Repetition of CQI or PCI/CQI reports** + +In Figure 20G, the CQI (or PCI/CQI) report is repeated according to the relation + +#### 4.7.4.3 Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured in Multiflow mode + +The notation used in the following subclauses is as defined below: + +| | | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell activation status "A": | Indicates a cell that is active (not deactivated by an HS-SCCH order). | +| Cell activation status "-": | Indicates a cell that is inactive (deactivated by an HS-SCCH order). | +| Cell group n: | A group of (one, two, or three) Multiflow mode cells that have the same CPICH timing. The cells that belong to a cell group are indicated by higher layers. | +| Ai & Aj: | HARQ-ACK field for jointly encoded HARQ-ACK information of cell i and cell j. | +| Ai & Aj & Ak: | HARQ-ACK field for jointly encoded HARQ-ACK information of cell i, cell j and cell k. | +| Ai & D: | HARQ-ACK field for jointly encoded HARQ-ACK information of cell i and DTX indication. | +| Ai & Aj & D: | HARQ-ACK field for jointly encoded HARQ-ACK information of cell i, cell j and DTX indication. | +| Ai & D & Aj: | HARQ-ACK field for jointly encoded HARQ-ACK information of cell i, DTX indication, and HARQ-ACK information of cell j. | +| CQIi: | CQI field for CQI information of cell i. | +| PCI/CQIi: | PCI/CQI field for jointly encoded PCI and CQI information of cell i. | +| CQIi & CQIj: | Jointly encoded CQI field for CQI information of cell i and cell j. | + +##### 4.7.4.3.1 Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with one serving and one assisting serving HS-DSCH cell + +When MIMO is not configured in any cell; + +- The HS-DPCCH mapping follows the table 15C.8. +- The HARQ-ACK and CQI encoding follow the definition in subclause 4.7.3A. +- HS-DPCCH is transmitted using slot format #0. + +**Table 15C.8: The UE is configured with one serving and one assisting serving HS-DSCH cell and no cells are in MIMO mode** + +| MF case | Cell activation status | | HS-DPCCH subframe | | | +|---------|------------------------|--------------|-------------------|--------|-------------| +| | Cell group 1 | Cell group 2 | Slot 0 | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | | | | +| 1 | A | A | A0 & A1 | | CQI0 & CQI1 | + +In this table cell 0 refers to the serving HS-DSCH cell, and cell 1 refers to the assisting serving HS-DSCH cell. + +When MIMO is configured in at least one cell; + +- The HS-DPCCH mapping follows the table 15C.9. +- The HARQ-ACK encoding follows the subclause 4.7.3D.1. +- The channel coding for CQI associated with a cell for which the UE is not configured in MIMO mode is specified in subclause 4.7.2.2. +- The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. +- HS-DPCCH is transmitted using slot format #0. + +**Table 15C.9: The UE is configured with one serving and one assisting serving HS-DSCH cell and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | HS-DPCCH subframe #1 | | | HS-DPCCH subframe #2 | | | +|---------|------------------------|--------------|----------------------|--------|----------|----------------------|--------|----------| +| | Cell group 1 | Cell group 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | | | | | | | +| 2 | A | A | A0 & A1 | | PCI/CQI0 | A0 & A1 | | PCI/CQI1 | + +In this table cell 0 refers to the serving HS-DSCH cell, and cell 1 refers to the assisting serving HS-DSCH cell. + +#### 4.7.4.3.2 Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with two serving and one assisting serving or one serving and two assisting serving HS-DSCH cells + +When MIMO is not configured in any cell; + +- If the UE is configured with two serving and one assisting serving HS-DSCH cells the HS-DPCCH mapping follows the table 15C.10 +- If the UE is configured with one serving and two assisting serving HS-DSCH cells the HS-DPCCH mapping follows the table 15C.11. +- The HARQ-ACK encoding follow the definition in subclause 4.7.3C.1. +- The CQI encoding for composite CQI reports containing channel quality indication for two cells follows the definition in subclause 4.7.3A.2 +- The CQI encoding for the separately encoded CQI reports follows the definition in subclause 4.7.2.2. +- HS-DPCCH is transmitted using slot format #0. + +**Table 15C.10: The UE is configured with two serving and one assisting serving HS-DSCH cells and no cells are in MIMO mode** + +| MF case | Cell activation status | | | HS-DPCCH subframe #1 | | | HS-DPCCH subframe #2 | | | +|---------|------------------------|--------------|--------------|----------------------|--------|-------------|----------------------|--------|--------| +| | Cell group 1 | Cell group 2 | Cell group 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | | | | | | | | +| 3 | A | A | A | A0&A1&A2 | | CQI0 & CQI1 | A0&A1&A2 | | CQI2 | +| 4 | A | - | A | A0&D&A2 | | CQI0 | A0&D&A2 | | CQI2 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the secondary serving HS-DSCH cell and cell 2 refers to the assisting serving HS-DSCH cell. + +**Table 15C.11: The UE is configured with one serving and two assisting serving HS-DSCH cells and no cells are in MIMO mode** + +| MF case | Cell activation status | | | HS-DPCCH subframe #1 | | | HS-DPCCH subframe #2 | | | | | +|---------|------------------------|--------------|-------|----------------------|--------|--------|----------------------|-------------|--------|--|--| +| | Cell group 1 | Cell group 2 | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | | | +| | Cell0 | Cell1 | Cell2 | | | | | | | | | +| 5 | A | A | | A0&A1&A2 | CQI0 | | A0&A1&A2 | CQI1 & CQI2 | | | | +| 6 | A | A | | A0&A1&D | CQI0 | | A0&A1&D | CQI1 | | | | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the assisting serving HS-DSCH cell and cell 2 refers to the assisting secondary serving HS-DSCH cell. + +When MIMO is configured in at least one cell; + +- If the UE is configured with two serving and one assisting serving HS-DSCH cells the HS-DPCCH mapping follows the table 15C.12 +- If the UE is configured with one serving and two assisting serving HS-DSCH cells the HS-DPCCH mapping follows the table 15C.13. +- The channel coding for HARQ-ACK for all cells is specified in subclause 4.7.3B.1. +- The channel coding for CQI associated with a cell for which the UE is not configured in MIMO mode is specified in subclause 4.7.2.2. +- The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. +- HS-DPCCH is transmitted using slot format #1. + +**Table 15C.12: The UE is configured with two serving and one assisting serving HS-DSCH cells and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | +|---------|------------------------|--------------|-------|----------------------|--------|----------|----------|----------------------|--------|----------|----------| +| | Cell group 1 | Cell group 2 | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | +| | Cell0 | Cell1 | Cell2 | | | | | | | | | +| 7 | A | A | A | A0&A1 | A2&D | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&D | PCI/CQI2 | PCI/CQI2 | +| 8 | A | - | A | A0&D | A2&D | PCI/CQI0 | PCI/CQI0 | A0&D | A2&D | PCI/CQI2 | PCI/CQI2 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the secondary serving HS-DSCH cell and cell 2 refers to the assisting serving HS-DSCH cell. + +**Table 15C.13: The UE is configured with one serving and two assisting serving HS-DSCH cells and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | +|---------|------------------------|--------------|-------|----------------------|--------|----------|----------|----------------------|--------|----------|----------| +| | Cell group 1 | Cell group 2 | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | +| | Cell0 | Cell1 | Cell2 | | | | | | | | | +| 9 | A | A | A | A0&D | A1&A2 | PCI/CQI0 | PCI/CQI0 | A0&D | A1&A2 | PCI/CQI1 | PCI/CQI2 | +| 10 | A | A | - | A0&D | A1&D | PCI/CQI0 | PCI/CQI0 | A0&D | A1&D | PCI/CQI1 | PCI/CQI1 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the assisting serving HS-DSCH cell and cell 2 refers to the assisting secondary serving HS-DSCH cell. + +#### 4.7.4.3.3 Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with two serving and two assisting serving HS-DSCH cells + +When MIMO is not configured in any cell; + +- The HS-DPCCH mapping follows the table 15C.14 +- The channel coding for HARQ-ACK is specified in subclause 4.7.3B.1. +- The channel coding for CQI is specified in subclause 4.7.2.2. +- HS-DPCCH is transmitted using slot format #1. + +**Table 15C.14: The UE is configured with two serving and two assisting serving HS-DSCH cells and no cells are in MIMO mode** + +| MF case | Cell activation status | | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | +|---------|------------------------|-------|--------------|-------|----------------------|-------|--------|--------|----------------------|-------|--------|--------| +| | Cell group 1 | | Cell group 2 | | Slot 0 | | Slot 1 | Slot 2 | Slot 0 | | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | +| 11 | A | A | A | A | A0&A1 | A2&A3 | CQI0 | CQI1 | A0&A1 | A2&A3 | CQI2 | CQI3 | +| 12 | A | A | A | - | A0&A1 | A2&D | CQI0 | CQI1 | A0&A1 | A2&D | CQI2 | CQI2 | +| 13 | A | - | A | A | A0&D | A2&A3 | CQI0 | CQI0 | A0&D | A2&A3 | CQI2 | CQI3 | +| 14 | A | - | A | - | A0&D | A2&D | CQI0 | CQI0 | A0&D | A2&D | CQI2 | CQI2 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the secondary serving HS-DSCH cell, cell 2 refers to the assisting serving HS-DSCH cell and cell 3 refers to the assisting secondary serving HS-DSCH cell. + +When MIMO is configured in at least one cell; + +- The HS-DPCCH mapping follows the table 15C.15 +- The channel coding for HARQ-ACK for all cells is specified in subclause 4.7.3B.1. +- The channel coding for CQI associated with a cell for which the UE is not configured in MIMO mode is specified in subclause 4.7.2.2. +- The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. +- HS-DPCCH is transmitted using slot format #1. + +**Table 15C.15: The UE is configured with two serving and two assisting serving HS-DSCH cells and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | +|---------|------------------------|-------|--------------|-------|----------------------|-------|----------|----------|----------------------|-------|----------|----------| +| | Cell group 1 | | Cell group 2 | | Slot 0 | | Slot 1 | Slot 2 | Slot 0 | | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | +| 15 | A | A | A | A | A0&A1 | A2&A3 | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&A3 | PCI/CQI2 | PCI/CQI3 | +| 16 | A | A | A | - | A0&A1 | A2&D | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&D | PCI/CQI2 | PCI/CQI2 | +| 17 | A | - | A | A | A0&D | A2&A3 | PCI/CQI0 | PCI/CQI0 | A0&D | A2&A3 | PCI/CQI2 | PCI/CQI3 | +| 18 | A | - | A | - | A0&D | A2&D | PCI/CQI0 | PCI/CQI0 | A0&D | A2&D | PCI/CQI2 | PCI/CQI2 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the secondary serving HS-DSCH cell, cell 2 refers to the assisting serving HS-DSCH cell and cell 3 refers to the assisting secondary serving HS-DSCH cell. + +#### 4.7.4.3.4 Physical Channel mapping for HS-DPCCH HARQ-ACK and PCI/CQI when the UE is configured with three serving and one assisting serving HS-DSCH cells or one serving and three assisting serving HS-DSCH cells + +When MIMO is not configured in any cell; + +- If the UE is configured with three serving and one assisting serving HS-DSCH cells, the HS-DPCCH mapping follows the table 15C.16. +- If the UE is configured with one serving and three assisting serving HS-DSCH cells, the HS-DPCCH mapping follows the table 15C.17. +- The channel coding for HARQ-ACK is specified in subclause 4.7.3B.1. +- The channel coding for CQI is specified in subclause 4.7.2.2. +- HS-DPCCH is transmitted using slot format #1. + +**Table 15C.16: The UE is configured with three serving and one assisting serving HS-DSCH cells and no cells are in MIMO mode** + +| MF case | Cell activation status | | HS-DPCCH subframe #1 | | | HS-DPCCH subframe #2 | | | +|---------|------------------------|-----|----------------------|--------|--------|----------------------|--------|--------| +| | Cell group 1 | CG2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | + +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | +|----|-------|-------|-------|-------|-------|-------|------|------|-------|-------|------|------| +| 19 | A | A | A | A | A0&A1 | A2&A3 | CQI0 | CQI1 | A0&A1 | A2&A3 | CQI2 | CQI3 | +| 20 | A | - | A | A | A0&D | A2&A3 | CQI0 | CQI0 | A0&D | A2&A3 | CQI2 | CQI3 | +| 21 | A | A | - | A | A0&A1 | D&A3 | CQI0 | CQI1 | A0&A1 | D&A3 | DTX | CQI3 | +| 22 | A | - | - | A | A0&D | D&A3 | CQI0 | CQI0 | A0&D | D&A3 | DTX | CQI3 | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the 1st secondary serving HS-DSCH cell, cell 2 refers to the 2nd secondary serving HS-DSCH cell and cell 3 refers to the assisting serving HS-DSCH cell. + +**Table 15C.17: The UE is configured with one serving and three assisting serving HS-DSCH cells and no cells are in MIMO mode** + +| MF case | Cell activation status | | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | | +|---------|------------------------|--------------|-------|-------|----------------------|--------|--------|--------|----------------------|--------|--------|--------|--------| +| | CG1 | Cell group 2 | | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | | +| 23 | A | A | A | A | A0&A1 | A2&A3 | CQI0 | CQI1 | A0&A1 | A2&A3 | CQI2 | CQI3 | | +| 24 | A | A | - | A | A0&A1 | D&A3 | CQI0 | CQI1 | A0&A1 | D&A3 | DTX | CQI3 | | +| 25 | A | A | A | - | A0&A1 | A2&D | CQI0 | CQI1 | A0&A1 | A2&D | CQI2 | DTX | | +| 26 | A | A | - | - | A0&A1 | D | CQI0 | CQI1 | A0&A1 | D | DTX | DTX | | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the assisting serving HS-DSCH cell, cell 2 refers to the 1st assisting secondary serving HS-DSCH cell and cell 3 refers to the 2nd assisting secondary serving HS-DSCH cell. + +When MIMO is configured in at least one cell; + +- If the UE is configured with three serving and one assisting serving HS-DSCH cells, the HS-DPCCH mapping follows the table 15C.18. +- If the UE is configured with one serving and three assisting serving HS-DSCH cells, the HS-DPCCH mapping follows the table 15C.19. +- The channel coding for HARQ-ACK for all cells is specified in subclause 4.7.3B.1, with the following exceptions: + - The second half (last 10 bits) of the Slot0 in Table 15C.18, where the channel coding is specified in subclause 4.7.3D.1. + - The first half (first 10 bits) of the Slot0 in Table 15C.19, where the channel coding is specified in subclause 4.7.3D.1 +- The channel coding for CQI associated with a cell for which the UE is not configured in MIMO mode is specified in subclause 4.7.2.2. +- The channel coding for PCI and CQI associated with a cell for which the UE is configured in MIMO mode is specified in subclause 4.7.3.2. +- HS-DPCCH is transmitted using slot format #1. + +**Table 15C.18: The UE is configured with three serving and one assisting serving HS-DSCH cells and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | | | HS-DPCCH subframe #1 | | | | HS-DPCCH subframe #2 | | | | | +|---------|------------------------|-------|-------|-------|----------------------|--------|----------|----------|----------------------|--------|----------|----------|--------| +| | Cell group 1 | | CG2 | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | | +| 27 | A | A | A | A | A0&A1 | A2&A3 | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&A3 | PCI/CQI2 | PCI/CQI3 | | +| 28 | A | - | A | A | A0&D | A2&A3 | PCI/CQI0 | PCI/CQI0 | A0&D | A2&A3 | PCI/CQI2 | PCI/CQI3 | | +| 29 | A | A | - | A | A0&A1 | D&A3 | PCI/CQI0 | PCI/CQI1 | A0&A1 | D&A3 | DTX | PCI/CQI3 | | +| 30 | A | - | - | A | A0&D | D&A3 | PCI/CQI0 | PCI/CQI0 | A0&D | D&A3 | DTX | PCI/CQI3 | | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the 1st secondary serving HS-DSCH cell, cell 2 refers to the 2nd secondary serving HS-DSCH cell and cell 3 refers to the assisting serving HS-DSCH cell. + +**Table 15C.19: The UE is configured with one serving and three assisting serving HS-DSCH cells and at least one cell is configured in MIMO mode** + +| MF case | Cell activation status | | | | HS-DPCCH subframe #1 | | | HS-DPCCH subframe #2 | | | | | +|---------|------------------------|--------------|-------|-------|----------------------|--------|----------|----------------------|--------|--------|----------|----------| +| | CG1 | Cell group 2 | | | Slot 0 | Slot 1 | Slot 2 | Slot 0 | Slot 1 | Slot 2 | Slot 2 | | +| | Cell0 | Cell1 | Cell2 | Cell3 | | | | | | | | | +| 31 | A | A | A | A | A0&A1 | A2&A3 | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&A3 | PCI/CQI2 | PCI/CQI3 | +| 32 | A | A | - | A | A0&A1 | A2&D | PCI/CQI0 | PCI/CQI1 | A0&A1 | D&A3 | DTX | PCI/CQI3 | +| 33 | A | A | A | - | A0&A1 | D&A3 | PCI/CQI0 | PCI/CQI1 | A0&A1 | A2&D | PCI/CQI2 | DTX | +| 34 | A | A | - | - | A0&A1 | D | PCI/CQI0 | PCI/CQI1 | A0&A1 | D | DTX | DTX | + +In this table cell 0 refers to the serving HS-DSCH cell, cell 1 refers to the assisting serving HS-DSCH cell, cell 2 refers to the 1st assisting secondary serving HS-DSCH cell and cell 3 refers to the 2nd assisting secondary serving HS-DSCH cell. + +#### 4.7.4.4 Physical Channel mapping for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in at least one cell + +##### 4.7.4.4.1 Physical Channel mapping for HS-DPCCH HARQ-ACK + +If the HS-DPCCH slot format 0 as defined in [2], is used, the HS-DPCCH physical channel mapping function shall map the input bits $w_k$ directly to physical channel so that bits are transmitted over the air in ascending order with respect to $k$ . + +If the HS-DPCCH slot format 1 as defined in [2], is used, the HS-DPCCH physical channel mapping function shall map the input bits $w_k$ to the physical channel so that bits are transmitted over the air in ascending order with respect to $k$ as follows: + +- If Secondary\_Cell\_Enabled is equal to 3 and Secondary\_Cell\_Active is equal to 3 + - The following HARQ-ACK messages are transmitted on HS-DPCCH: + - HARQ-ACK comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order + - The following HARQ-ACK messages are transmitted on HS-DPCCH2: + - HARQ-ACK comprising the HARQ acknowledgement messages for the pair of the 2nd secondary serving HS-DSCH cell and the 3rd secondary serving HS-DSCH cell in that order +- If Secondary\_Cell\_Enabled is equal to 2 and Secondary\_Cell\_Active is equal to 2 + - The following HARQ-ACK messages are transmitted on HS-DPCCH: + - HARQ-ACK comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order + - The following HARQ-ACK messages are transmitted on HS-DPCCH2: + - HARQ-ACK comprising the HARQ acknowledgement message for the 2nd secondary serving HS-DSCH cell +- If Secondary\_Cell\_Enabled is equal to 1 and Secondary\_Cell\_Active is equal to 1 + - The following two HARQ-ACK messages are transmitted on HS-DPCCH + - HARQ-ACK comprising the HARQ acknowledgement messages for the pair of serving HS-DSCH cell and 1st secondary serving HS-DSCH cell in that order +- If Secondary\_Cell\_Enabled is equal to 3 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - If none of the 2nd or 3rd secondary serving HS-DSCH cell is activated HS-DPCCH2 is not transmitted + - If only one of the 2nd or 3rd secondary serving HS-DSCH cell is activated the HARQ-ACK is repeated according to the Figure 20E + +- If the 1st secondary serving HS-DSCH cell is not activated the HARQ-ACK is repeated according to the Figure 20E +- Otherwise the transmissions of the HARQ-ACK messages are the same as if Secondary\_Cell\_Active was equal to Secondary\_Cell\_Enabled. +- If Secondary\_Cell\_Enabled is equal to 2 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - If the 2nd secondary serving HS-DSCH cell is not activated the HARQ-ACK transmissions on HS-DPCCH2 are DTXed + - If the 1st secondary serving HS-DSCH cell is not activated the HARQ-ACK is repeated according to the Figure 20E + - Otherwise the transmissions of the HARQ-ACK messages are the same as if Secondary\_Cell\_Active was equal to Secondary\_Cell\_Enabled. +- If Secondary\_Cell\_Enabled is equal to 1 and Secondary\_Cell\_Active is 0 then the transmission of the HARQ-ACK message is repeated according to Figure 20E. + +#### 4.7.4.4.2 Physical Channel mapping for HS-DPCCH NTBP/PCI/CQI + +If the HS-DPCCH slot format 0 as defined in [2] is used, the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to physical channel so that bits are transmitted over the air in ascending order with respect to $k$ . + +If the HS-DPCCH slot format 1 as defined in [2] is used, the HS-DPCCH physical channel mapping function shall map the input bits $b_k$ directly to physical channel so that bits are transmitted over the air in ascending order with respect to $k$ . + +- If Secondary\_Cell\_Enabled is equal to 3 and Secondary\_Cell\_Active is equal to 3 + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. + - If the serving cell is configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is not configured in MIMO mode with four transmit antennas, the CQI2 or PCI/CQI2 of the 1st secondary serving cell is repeated. + - If the serving cell is not configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is configured in MIMO mode with four transmit antennas, the CQI1 or PCI/CQI1 of the serving cell is repeated. + - If both the serving cell and 1st secondary serving cell are not configured in MIMO mode with four transmit antennas the CQI1 or PCI/CQI1 and CQI2 or PCI/CQI2 are mapped to a separate subframe as specified in [4]. + - The following is transmitted on HS-DPCCH2: + - The report for the 2nd secondary HS-DSCH cell (CQI3 or PCI/CQI3 or NTBP/PCI/CQI3) and the 3rd secondary HS-DSCH cell (CQI4 or PCI/CQI4 or NTBP/PCI/CQI4) are mapped to a separate subframe as specified in [4]. + - If the 2nd serving cell is configured in MIMO mode with four transmit antennas and the 3rd secondary serving cell is not configured in MIMO mode with four transmit antennas, the CQI4 or PCI/CQI4 of the 3rd secondary serving cell is repeated. + - If the 2nd serving cell is not configured in MIMO mode with four transmit antennas and the 3rd secondary serving cell is configured in MIMO mode with four transmit antennas, the CQI3 or PCI/CQI3 of the 2nd serving cell is repeated. + - If both the 2nd serving cell and 3rd secondary serving cell are not configured in MIMO mode with four transmit antennas the CQI3 or PCI/CQI3 and CQI4 or PCI/CQI4 are mapped to a separate subframe as specified in [4]. + +- If Secondary\_Cell\_Enabled is equal to 2 and Secondary\_Cell\_Active is equal to 2 + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. + - If the serving cell is configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is not configured in MIMO mode with four transmit antennas, the CQI2 or PCI/CQI2 of the 1st secondary serving cell is repeated. + - If the serving cell is not configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is configured in MIMO mode with four transmit antennas, the CQI1 or PCI/CQI1 of the serving cell is repeated. + - If both the serving cell and 1st secondary serving cell are not configured in MIMO mode with four transmit antennas the CQI1 or PCI/CQI1 and CQI2 or PCI/CQI2 are mapped to a separate subframe as specified in [4]. + - The following is transmitted on HS-DPCCH2: + - If the 2nd serving cell is configured in MIMO mode with four transmit antennas the HS-DPCCH2 physical channel mapping function shall map NTBP/ PCI/CQI3 to the physical channel. + - If the 2nd serving cell is not configured in MIMO mode with four transmit antennas the HS-DPCCH2 physical channel mapping function shall map CQI3 or PCI/CQI3 to the physical channel. +- If Secondary\_Cell\_Enabled is equal to 1 and Secondary\_Cell\_Active is equal to 1 + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. + - If the serving cell is configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is not configured in MIMO mode with four transmit antennas, the CQI2 or PCI/CQI2 of the 1st secondary serving cell is repeated. + - If the serving cell is not configured in MIMO mode with four transmit antennas and the 1st secondary serving cell is configured in MIMO mode with four transmit antennas, the CQI1 or PCI/CQI1 of the serving cell is repeated. +- If Secondary\_Cell\_Enabled is equal to 1 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. The slots corresponding to the (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are DTXed. +- If Secondary\_Cell\_Enabled is equal to 2 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - If the 2nd serving cell is not activated HS-DPCCH2 is not transmitted. + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. The slots corresponding to the (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are DTXed. + - The following is transmitted on HS-DPCCH2: + +- If the 2nd serving cell is configured in MIMO mode with four transmit antennas the HS-DPCCH2 physical channel mapping function shall map NTBP/ PCI/CQI3 to the physical channel +- If the 2nd serving cell is not configured in MIMO mode with four transmit antennas the HS-DPCCH2 physical channel mapping function shall map CQI3 or PCI/CQI3 to the physical channel. +- If Secondary\_Cell\_Enabled is equal to 3 and Secondary\_Cell\_Active is less than Secondary\_Cell\_Enabled: + - If none of the 2nd or 3rd secondary serving HS-DSCH cell is activated HS-DPCCH2 is not transmitted and the rules in case Secondary\_Cell\_Enabled is equal to 1 and Secondary\_Cell\_Active is equal to 1 are followed for HS-DPCCH + - The following is transmitted on HS-DPCCH: + - The report for the serving HS-DSCH cell (CQI1 or PCI/CQI1 or NTBP/PCI/CQI1) and the 1st secondary serving HS-DSCH cell (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are mapped to a separate subframe as specified in [4]. The slots corresponding to the (CQI2 or PCI/CQI2 or NTBP/PCI/CQI2) are DTXed. + - The following is transmitted on HS-DPCCH2: + - If the 3rd secondary serving HS-DSCH cell is not activated, the report for the 2nd secondary HS-DSCH cell (CQI3 or PCI/CQI3 or NTBP/PCI/CQI3) and the 3rd secondary serving HS-DSCH cell (CQI4 or PCI/CQI4 or NTBP/PCI/CQI4) are mapped to a separate subframe as specified in [4]. The slots corresponding to the (CQI4 or PCI/CQI4 or NTBP/PCI/CQI4) are DTXed. + - If the 2nd secondary serving HS-DSCH cell is not activated, the report for the 3rd secondary HS-DSCH cell (CQI4 or PCI/CQI4 or NTBP/PCI/CQI4) and the 2nd secondary serving HS-DSCH cell (CQI3 or PCI/CQI3 or NTBP/PCI/CQI3) are mapped to a separate subframe as specified in [4]. The slots corresponding to the (CQI3 or PCI/CQI3 or NTBP/PCI/CQI3) are DTXed. +- If Secondary\_Cell\_Enabled is equal to 0 + - The following is transmitted on HS-DPCCH: + - The physical channel mapping function shall map NTBP/ PCI/CQI1 to the physical channel. + +## 4.8 Coding for E-DCH + +Figure 21 shows the processing structure for the E-DCH transport channel mapped onto a separate CCTrCH. + +If UL\_MIMO\_Enabled is not set to TRUE, or UL\_MIMO\_Enabled is set to TRUE and UL\_CLTD\_Active is not 1, data arrives to the coding unit in form of a maximum of one transport block once every transmission time interval (TTI). + +If UL\_MIMO\_Enabled is set to TRUE and UL\_CLTD\_Active = 1, data arrives to the coding unit in form of a maximum of two transport blocks once every TTI. + +- If a single transport block arrives to the coding unit in a TTI, the transport block is processed as when UL\_MIMO\_Enabled is not set to TRUE. +- If two transport blocks arrive to the coding unit in a TTI, each transport block is separately processed as when UL\_MIMO\_Enabled is not set to TRUE, with the exception of the rank-dependent determinations of SF, modulation, number of E-DPDCHs and S-E-DPDCHs, and the physical channel mapping. + +The following coding steps can be identified: + +- Add CRC to the transport block +- Code block segmentation +- Channel coding +- Physical layer hybrid ARQ and rate matching +- Physical channel segmentation + +- Interleaving +- Physical channel mapping + +The coding steps for E-DCH transport channel are shown in the figure below. + +![Flowchart of transport channel processing for E-DCH. The process starts with input bits a_im1, a_im2, a_im3, ..., a_imA. These pass through 'CRC attachment' to produce b_im1, b_im2, b_im3, ..., b_imB. Next is 'Code block segmentation' resulting in o_ir1, o_ir2, o_ir3, ..., o_irK. Then 'Channel Coding' produces c_i1, c_i2, c_i3, ..., c_iE. This is followed by 'Physical Layer Hybrid-ARQ functionality/Rate matching' resulting in s_1, s_2, s_3, ..., s_R. Next is 'Physical Channel Segmentation' resulting in u_p,1, u_p,2, u_p,3, ..., u_p,U(p). Finally, 'Interleaving & Physical channel mapping' produces the output 'Physical channel(s)'.](c2e2b17d61aecbead88a6278e4ba3605_img.jpg) + +``` + +graph TD + Input["a_im1, a_im2, a_im3, ..., a_imA"] --> CRC["CRC attachment"] + CRC --> B["b_im1, b_im2, b_im3, ..., b_imB"] + B --> Seg["Code block segmentation"] + Seg --> O["o_ir1, o_ir2, o_ir3, ..., o_irK"] + O --> CC["Channel Coding"] + CC --> C["c_i1, c_i2, c_i3, ..., c_iE"] + C --> PHARQ["Physical Layer Hybrid-ARQ functionality/Rate matching"] + PHARQ --> S["s_1, s_2, s_3, ..., s_R"] + S --> PCS["Physical Channel Segmentation"] + PCS --> U["u_p,1, u_p,2, u_p,3, ..., u_p,U(p)"] + U --> IP["Interleaving & Physical channel mapping"] + IP --> Output["Physical channel(s)"] + +``` + +Flowchart of transport channel processing for E-DCH. The process starts with input bits a\_im1, a\_im2, a\_im3, ..., a\_imA. These pass through 'CRC attachment' to produce b\_im1, b\_im2, b\_im3, ..., b\_imB. Next is 'Code block segmentation' resulting in o\_ir1, o\_ir2, o\_ir3, ..., o\_irK. Then 'Channel Coding' produces c\_i1, c\_i2, c\_i3, ..., c\_iE. This is followed by 'Physical Layer Hybrid-ARQ functionality/Rate matching' resulting in s\_1, s\_2, s\_3, ..., s\_R. Next is 'Physical Channel Segmentation' resulting in u\_p,1, u\_p,2, u\_p,3, ..., u\_p,U(p). Finally, 'Interleaving & Physical channel mapping' produces the output 'Physical channel(s)'. + +**Figure 21: Transport channel processing for E-DCH** + +In the following the number of transport blocks per TTI and the number of transport channels is always one i.e. $m=1$ and $i=1$ . When referencing non E-DCH formulae which are used in correspondence with E-DCH formulae the convention is used that transport block subscripts may be omitted (e.g. $X_i$ may be written $X$ ). + +#### 4.8.1 CRC attachment for E-DCH + +CRC attachment for the E-DCH transport channel shall be performed according to the general method described in 4.2.1 above with the following specific parameters. + +The CRC length shall always be $L_i=24$ bits. + +#### 4.8.2 Code block segmentation for E-DCH + +Code block segmentation for the E-DCH transport channel shall be performed according to the general method described in 4.2.2.2 with the following specific parameters. + +There is a maximum of one transport block. The bits input to the block are mapped to the bits directly. It follows that $X_i = B_i$ . Note that the bits $x$ referenced here refer only to the internals of the code block segmentation function. The output bits from the code block segmentation function are $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK}$ . + +The value of $Z = 5114$ for turbo coding shall be used. + +### 4.8.3 Channel coding for E-DCH + +Channel coding for the E-DCH transport channel shall be performed according to the general method described in clause 4.2.3 above with the following specific parameters. + +There is a maximum of one transport block, $i=1$ . The rate 1/3 turbo coding shall be used. + +### 4.8.4 Physical layer HARQ functionality and rate matching for E-DCH + +The hybrid ARQ functionality matches the number of bits at the output of the channel coder to the total number of bits of the E-DPDCH or S-E-DPDCH set to which the E-DCH transport channel is mapped. The hybrid ARQ functionality is controlled by the redundancy version (RV) parameters. + +![Figure 22: E-DCH hybrid ARQ functionality block diagram. The input N_e,j enters a 'bit separation' block. The output is split into three parallel paths: 'Systematic bits' (N_sys), 'Parity 1 bits' (N_p1), and 'Parity 2 bits' (N_p2). Each path goes through a 'Rate Matching' block (RM_S, RM_P1_2, RM_P2_2) to produce N_t,sys, N_t,p1, and N_t,p2 respectively. These three outputs then enter a 'bit collection' block, which produces the final output N_e,data,j. The 'Rate Matching' label is placed above the RM blocks.](46b47a38697e3aedb09cccd7eba47192_img.jpg) + +Figure 22: E-DCH hybrid ARQ functionality block diagram. The input N\_e,j enters a 'bit separation' block. The output is split into three parallel paths: 'Systematic bits' (N\_sys), 'Parity 1 bits' (N\_p1), and 'Parity 2 bits' (N\_p2). Each path goes through a 'Rate Matching' block (RM\_S, RM\_P1\_2, RM\_P2\_2) to produce N\_t,sys, N\_t,p1, and N\_t,p2 respectively. These three outputs then enter a 'bit collection' block, which produces the final output N\_e,data,j. The 'Rate Matching' label is placed above the RM blocks. + +Figure 22: E-DCH hybrid ARQ functionality + +#### 4.8.4.1 Determination of SF, modulation scheme and number of E-DPDCH PhCHs needed + +The maximum amount of puncturing that can be applied is + +- $1-PL_{non-max}$ if the modulation scheme or the number of code channels is less than the maximum allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{mod\_switch}$ if the modulation scheme is BPSK, the number of E-DPDCH code channels equals to 4 and the usage of 4PAM is allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{mod\_switch\_2}$ if the modulation scheme is 4PAM, the number of E-DPDCH code channels equals to 4 and the usage of 8PAM is allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{max}$ if the modulation scheme and the number of code channels equals to the maximum allowed by the UE capability and restrictions imposed by UTRAN. + +The number of available bits per TTI of one E-DPDCH for all possible spreading factors and modulation schemes is denoted by $N_{256}$ , $N_{128}$ , $N_{64}$ , $N_{32}$ , $N_{16}$ , $N_8$ , $N_4$ , $N_2$ , $M_4$ , $M_2$ , $L_4$ and $L_2$ where the index refers to the spreading factor. $N$ refers to BPSK modulation, $M$ to 4PAM modulation and $L$ to 8PAM modulation. + +The possible number of bits available to the CCTrCH of E-DCH type on all E-DPDCHs, $N_{e,data}$ , then are $\{N_{256}$ , $N_{128}$ , $N_{64}$ , $N_{32}$ , $N_{16}$ , $N_8$ , $N_4$ , $2 \times N_4$ , $2 \times N_2$ , $2 \times N_2 + 2 \times N_4$ , $2 \times M_2 + 2 \times M_4$ , $2 \times L_2 + 2 \times L_4\}$ . + +SET0 denotes the set of $N_{e,data}$ values allowed by the UTRAN and supported by the UE, as part of the UE's capability. SET0 can be a subset of $\{N_{256}$ , $N_{128}$ , $N_{64}$ , $N_{32}$ , $N_{16}$ , $N_8$ , $N_4$ , $2 \times N_4$ , $2 \times N_2$ , $2 \times N_2 + 2 \times N_4$ , $2 \times M_2 + 2 \times M_4$ , $2 \times L_2 + 2 \times L_4\}$ . + +The total number of bits in a TTI on all E-DPDCHs before rate matching with transport format j is $N_{ej}$ . The total number of bits available for the E-DCH transmission per TTI on all E-DPDCHs with transport format j, $N_{e,data,j}$ , is determined by executing the following algorithm, where + +- $PL_{non-max}$ is signalled from higher layers, +- $PL_{mod\_switch}$ is equal to 0.468, +- $PL_{mod\_switch\_2}$ is equal to 0.4, +- $PL_{max}$ is equal to 0.44 , except when the $N_{e,data} = 2 \times N_2 + 2 \times N_4$ , $2 \times M_2 + 2 \times M_4$ or $2 \times L_2 + 2 \times L_4$ is allowed by the UTRAN and supported by the UE, in which case $PL_{max}$ is equal to 0.33: + +If the UE transmits only one transport block: + +SET1 = { $N_{e,data}$ in SET0 such that $N_{e,data} - N_{ej}$ is non negative } + +If SET1 is not empty and the smallest element of SET1 requires just one E-DPDCH then + +$N_{e,data,j} = \min \text{ SET1}$ + +Else + +SET2 = { $N_{e,data}$ in SET0 without $2 \times N_2 + 2 \times N_4$ , $2 \times M_2 + 2 \times M_4$ and $2 \times L_2 + 2 \times L_4$ such that $N_{e,data} - PL_{non-max} \times N_{ej}$ is non negative } + +If SET2 is not empty then + +Sort SET2 in ascending order + +$N_{e,data} = \min \text{ SET2}$ + +While $N_{e,data}$ is not the max of SET2 and the follower of $N_{e,data}$ requires only one E-DPDCH do + +$N_{e,data} = \text{follower of } N_{e,data} \text{ in SET2}$ + +End while + +$N_{e,data,j} = N_{e,data}$ + +Else + +If SET0 includes $2 \times N_2 + 2 \times N_4$ + +$N_{e,data} = 2 \times N_2 + 2 \times N_4$ + +If $N_{e,data} / N_{ej} < PL_{mod\_switch}$ and SET0 includes $2 \times M_2 + 2 \times M_4$ + +$N_{e,data} = 2 \times M_2 + 2 \times M_4$ + +End if + +If $N_{e,data}$ is equal to $2 \times M_2 + 2 \times M_4$ and $N_{e,data} / N_{ej} < PL_{mod\_switch\_2}$ and SET0 includes $2 \times L_2 + 2 \times L_4$ + +$N_{e,data} = 2 \times L_2 + 2 \times L_4$ + +End if + +$N_{e,data,j} = N_{e,data}$ provided that $N_{e,data,j} - PL_{max} \times N_{ej}$ is non negative + +Else + +$N_{e,data,j} = \max \text{ SET0}$ provided that $N_{e,data,j} - PL_{max} \times N_{ej}$ is non negative + +End if + +End if + +End if + +Else (when UE transmits two transport blocks) + +$$N_{e,data} = 2 \times N_2 + 2 \times N_4$$ + +If $N_{e,data} / N_{ej} < PL_{mod\_switch}$ and SET0 includes $2 \times M_2 + 2 \times M_4$ + +$$N_{e,data} = 2 \times M_2 + 2 \times M_4$$ + +End if + +If $N_{e,data}$ is equal to $2 \times M_2 + 2 \times M_4$ , $N_{e,data} / N_{ej} < PL_{mod\_switch\_2}$ and SET0 includes $2 \times L_2 + 2 \times L_4$ + +$$N_{e,data} = 2 \times L_2 + 2 \times L_4$$ + +End if + +$N_{e,data,j} = N_{e,data}$ provided that $N_{e,data} - PL_{max} \times N_{ej}$ is non negative + +End if + +While E-DCH TTI length is 10 ms, if an initial transmission occurs in a compressed frame, or a retransmission occurs in a compressed frame, or a retransmission occurs in a non-compressed frame for which initial transmission was compressed, the number of available bits per TTI of one E-DPDCH for all possible spreading factors denoted by $N_{256}$ , $N_{128}$ , $N_{64}$ , $N_{32}$ , $N_{16}$ , $N_8$ , $N_4$ and $N_2$ used in the algorithm above is replaced by $k \times N_{256}$ , $k \times N_{128}$ , $k \times N_{64}$ , $k \times N_{32}$ , $k \times N_{16}$ , $k \times N_8$ , $k \times N_4$ and $k \times N_2$ . The parameter $k$ is equal to $n_{txl}/15$ and $n_{txl}$ is defined in 4.4.5.1. + +#### 4.8.4.1A Determination of SF, modulation scheme and number of S-E-DPDCH PhCHs needed + +S-E-DPDCHs are only present when the UE transmits two transport blocks. When present, the number of S-E-DPDCHs is always 4. + +The maximum amount of puncturing that can be applied is + +- $1-PL_{non-max}$ if the modulation scheme is less than the maximum allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{mod\_switch}$ if the modulation scheme is BPSK and the usage of 4PAM is allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{mod\_switch\_2}$ if the modulation scheme is 4PAM and the usage of 8PAM is allowed by the UE capability and restrictions imposed by UTRAN. +- $1-PL_{max}$ if the modulation scheme equals to the maximum allowed by the UE capability and restrictions imposed by UTRAN. + +The number of available bits per TTI of one S-E-DPDCH for all possible spreading factors and modulation schemes is denoted by $N_4$ , $N_2$ , $M_4$ , $M_2$ , $L_4$ and $L_2$ , where the index refers to the spreading factor. $N$ refers to BPSK modulation, $M$ to 4PAM modulation and $L$ to 8PAM modulation. + +The possible number of bits available to the CCTrCH of E-DCH type on all S-E-DPDCHs, $N_{e,data}$ , then are $\{2 \times N_2 + 2 \times N_4, 2 \times M_2 + 2 \times M_4, 2 \times L_2 + 2 \times L_4\}$ . + +SET0 denotes the set of $N_{e,data}$ values allowed by the UTRAN and supported by the UE, as part of the UE's capability. SET0 can be a subset of $\{2 \times N_2 + 2 \times N_4, 2 \times M_2 + 2 \times M_4, 2 \times L_2 + 2 \times L_4\}$ . + +The total number of bits in a TTI on all S-E-DPDCHs before rate matching with transport format $j$ is $N_{ej}$ . The total number of bits available for the E-DCH transmission per TTI on all S-E-DPDCHs with transport format $j$ , $N_{e,data,j}$ , is determined by executing the following algorithm, where + +- $PL_{mod\_switch}$ is equal to 0.468, +- $PL_{mod\_switch\_2}$ is equal to 0.4, +- $PL_{max}$ is equal to 0.33: + +$$N_{e,data} = 2 \times N_2 + 2 \times N_4$$ + +If $N_{e,data} / N_{ej} < PL_{mod\_switch}$ and SET0 includes $2 \times M_2 + 2 \times M_4$ + +$$N_{e,data} = 2 \times M_2 + 2 \times M_4$$ + +End if + +If $N_{e,data}$ is equal to $2 \times M_2 + 2 \times M_4$ , $N_{e,data} / N_{ej} < PL_{mod\_switch\_2}$ and SET0 includes $2 \times L_2 + 2 \times L_4$ + +$$N_{e,data} = 2 \times L_2 + 2 \times L_4$$ + +End if + +$N_{e,data,j} = N_{e,data}$ provided that $N_{e,data} - PL_{max} \times N_{ej}$ is non negative + +#### 4.8.4.2 HARQ bit separation + +The HARQ bit separation function shall be performed in the same way as bit separation for turbo encoded TrCHs with puncturing in 4.2.7.4.1 above. + +#### 4.8.4.3 HARQ Rate Matching Stage + +The hybrid ARQ rate matching for the E-DCH transport channel shall be done with the general method described in 4.2.7.5 with the following specific parameters. + +The parameters of the rate matching stage depend on the value of the RV parameters $s$ and $r$ . The $s$ and $r$ combinations corresponding to each RV allowed for the E-DCH are listed in the table below. + +**Table 15D: RV for E-DCH** + +| E-DCH RV Index | $s$ | $r$ | +|----------------|-----|-----| +| 0 | 1 | 0 | +| 1 | 0 | 0 | +| 2 | 1 | 1 | +| 3 | 0 | 1 | + +The parameter $e_{plus}$ , $e_{minus}$ and $e_{ini}$ are calculated with the general method for QPSK as described in 4.5.4.3 above. The following parameters are used as input: + +$$N_{sys} = N_{p1} = N_{p2} = N_{ej}/3$$ + +$$N_{data} = N_{e,data,j}$$ + +$$r_{max} = 2$$ + +During uplink compressed frames while E-DCH TTI length is 10 ms and if $N_{data} > N_{ej}$ : + +- If $N_{data} \bmod 3 = 1$ , one $\delta$ bit is added to the $N_{t,sys}$ bits as the last systematic bit and another $\delta$ bit is added to the $N_{t,p1}$ bits as the last $N_{t,p1}$ bit. +- If $N_{data} \bmod 3 = 2$ , one $\delta$ bit is added to the $N_{t,sys}$ bits as the last systematic bit. + +#### 4.8.4.4 HARQ bit collection + +The HARQ bit collection shall be performed according to the general method for bit collection for turbo encoded TrCHs with puncturing as specified in 4.2.7.4.2 including the removal of the bits with value $\delta$ . + +#### 4.8.5 Physical channel segmentation for E-DCH + +When more than one E-DPDCH or S-E-DPDCH is used, physical channel segmentation distributes the bits among the different physical channels. The bits input to the physical channel segmentation are denoted by $s_1, s_2, s_3, \dots, s_R$ , where $R$ is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by $P$ . + +The bits after physical channel segmentation are denoted $u_{p,k}$ where $p$ is the PhCH number. $U(p)$ is the number of physical channel bits in one E-DCH TTI for the $p^{\text{th}}$ E-DPDCH or S-E-DPDCH. The relation between $s_k$ and $u_{p,k}$ is given below. + +Bits on first PhCH after physical channel segmentation: + +$$k = 1, 2, \dots, U(1)$$ + +Bits on $p^{\text{th}}$ PhCH after physical channel segmentation: + +$$k = 1, 2, \dots, U(p)$$ + +#### 4.8.6 Interleaving for E-DCH + +The interleaving is done as shown in figure 22A below, separately for each physical channel. The bits input to the block interleaver are denoted by $u_{p,k}$ , where $p$ is PhCH number and $U=U(p)$ is the number of bits in one TTI for one PhCH. + +![Figure 22A: Interleaver structure for E-DCH. The diagram shows three interleaver blocks, each labeled 'Interleaver (R2 x 30)'. The first block takes u_{p,k} (BPSK) as input and produces v_{p,k} (BPSK) as output. The second block takes u_{p,k+1} (4PAM) and u_{p,k+1} (8PAM) as input and produces v_{p,k+1} (4PAM) and v_{p,k+1} (8PAM) as output. The third block takes u_{p,k+2} (8PAM) as input and produces v_{p,k+2} (8PAM) as output. Dashed lines connect the input bits to the interleaver blocks, showing the distribution of bits from the physical channel segmentation.](305c3b31c7d60405cf039fd098ba4669_img.jpg) + +Figure 22A: Interleaver structure for E-DCH. The diagram shows three interleaver blocks, each labeled 'Interleaver (R2 x 30)'. The first block takes u\_{p,k} (BPSK) as input and produces v\_{p,k} (BPSK) as output. The second block takes u\_{p,k+1} (4PAM) and u\_{p,k+1} (8PAM) as input and produces v\_{p,k+1} (4PAM) and v\_{p,k+1} (8PAM) as output. The third block takes u\_{p,k+2} (8PAM) as input and produces v\_{p,k+2} (8PAM) as output. Dashed lines connect the input bits to the interleaver blocks, showing the distribution of bits from the physical channel segmentation. + +**Figure 22A: Interleaver structure for E-DCH** + +The basic interleaver is as the 2nd interleaver described in Clause 4.2.11. + +For 4PAM, there are two identical interleavers of the same size $R2 \times 30$ , where $R2$ is the minimum integer fulfilling . The output bits from the physical channel segmentation are divided one by one between the interleavers: bit $u_{p,k}$ goes to the first interleaver and bit $u_{p,k+1}$ goes to the second interleaver. Bits are collected one by one from the interleavers: bit $v_{p,k}$ is obtained from the first interleaver and bit $v_{p,k+1}$ is obtained from the second interleaver, where $k \bmod 2=1$ . + +For 8PAM, there are three identical interleavers of the same size $R2 \times 30$ , where $R2$ is the minimum integer fulfilling . The output bits from the physical channel segmentation are divided one by one between the interleavers: bit $u_{p,k}$ goes to the first interleaver, bit $u_{p,k+1}$ goes to the second interleaver and bit $u_{p,k+2}$ goes to the third interleaver. Bits are collected one by one from the interleavers: bit $v_{p,k}$ is obtained from the first interleaver, bit $v_{p,k+1}$ is obtained from the second interleaver and bit $v_{p,k+2}$ is obtained from the third interleaver, where $k \bmod 3=1$ . + +#### 4.8.7 Physical channel mapping for E-DCH + +The E-DCH structure is described in [2]. The bits input to the physical channel mapping are denoted $v_{p,1}, v_{p,2}, \dots, v_{p,U(p)}$ . The bits $v_{p,k}$ are mapped to the PhCHs such that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +During compressed frames in the uplink and when E-DCH TTI is 10 ms: + +- For the initial transmission the bits shall be consecutively mapped to the non-idle slots. The UE shall not map any bit to the E-DPDCH idle slots specified in 4.4.5.1. +- In case a retransmission occurs in a compressed frame or a retransmission occurs in a non-compressed frame for which initial transmission was compressed: + - If $n_{txl} > n_{max}$ : The bits shall be consecutively mapped to the $n_{max}$ available slots. The remaining bits are not transmitted. + - If $n_{txl} \leq n_{max}$ : The bits shall be consecutively mapped to the $n_{txl}$ non-idle slots, whilst no bits are mapped to the idle slots. +- The transmission gap position and the parameters $n_{txl}$ and $n_{max}$ are specified in 4.4.5.2. + +## 4.9 Coding for E-DPCCH + +The following information is transmitted by means of the E-DPCCH: + +- Retransmission sequence number (RSN): $x_{rsn,1}, x_{rsn,2}$ +- E-TFCI: $x_{tfci,1}, x_{tfci,2}, \dots, x_{tfci,7}$ +- "Happy" bit: $x_{h,1}$ + +### 4.9.1 Overview + +The figure below illustrates the overall coding chain for E-DPCCH. + +![Figure 23: Coding chain for E-DPCCH. The diagram shows a vertical flow of data through three processing blocks. At the top, three input data streams are shown: x_{h,1}, x_{rsn,2}, x_{rsn,1}, and x_{tfci,7}, ..., x_{tfci,2}, x_{tfci,1}. These inputs enter a 'Multiplexing' block. The output of the Multiplexing block is a sequence of bits x_1, x_2, ..., x_{10}. This sequence enters a 'Channel Coding' block. The output of the Channel Coding block is a sequence of bits z_0, z_1, ..., z_{29}. This sequence enters a 'Physical channel mapping' block. The final output of the Physical channel mapping block is the E-DPCCH signal.](91aa519060714a3ebba978bb68cbf648_img.jpg) + +``` + +graph TD + Inputs["x_{h,1}, x_{rsn,2}, x_{rsn,1}, x_{tfci,7}, ..., x_{tfci,2}, x_{tfci,1}"] --> Multiplexing[Multiplexing] + Multiplexing --> X["x_1, x_2, ..., x_{10}"] + X --> ChannelCoding[Channel Coding] + ChannelCoding --> Z["z_0, z_1, ..., z_{29}"] + Z --> PhysicalMapping[Physical channel mapping] + PhysicalMapping --> E_DPCCH[E-DPCCH] + +``` + +Figure 23: Coding chain for E-DPCCH. The diagram shows a vertical flow of data through three processing blocks. At the top, three input data streams are shown: x\_{h,1}, x\_{rsn,2}, x\_{rsn,1}, and x\_{tfci,7}, ..., x\_{tfci,2}, x\_{tfci,1}. These inputs enter a 'Multiplexing' block. The output of the Multiplexing block is a sequence of bits x\_1, x\_2, ..., x\_{10}. This sequence enters a 'Channel Coding' block. The output of the Channel Coding block is a sequence of bits z\_0, z\_1, ..., z\_{29}. This sequence enters a 'Physical channel mapping' block. The final output of the Physical channel mapping block is the E-DPCCH signal. + +Figure 23: Coding chain for E-DPCCH + +### 4.9.2 E-DPCCH information field mapping + +#### 4.9.2.1 Information field mapping of E-TFCI + +The E-TFCI is mapped such that $x_{tfci,1}$ corresponds to the MSB. + +#### 4.9.2.2 Information field mapping of retransmission sequence number + +To indicate the redundancy version (RV) of each HARQ transmission and to assist the Node B soft buffer management a two bit retransmission sequence number (RSN) is signalled from the UE to the Node B. The Node B can avoid soft + +buffer corruption by flushing the soft buffer associated to one HARQ process in case more than 3 consecutive E-DPCCH transmissions on that HARQ process can not be decoded or the last received RSN is incompatible with the current one. + +The RSN is set by higher layers as described in [16]. The RSN is mapped such that $x_{rsn,1}$ corresponds to the MSB. + +The applied E-DCH RV index specifying the used RV ( $s$ and $r$ parameter) depends on the RSN, on $N_{sys} / N_{e,data,j}$ , and if RSN=3 also on the TTIN (TTI number). For 10 ms TTI the TTI number is equal to the CFN, for 2 ms TTI + +$$TTIN = 5 * CFN + \text{subframe number}$$ + +where the subframe number counts the five TTIs which are within a given CFN, starting from 0 for the first TTI to 4 for the last TTI. $N_{ARQ}$ is the number of Hybrid ARQ processes. + +**Table 16: Relation between RSN value and E-DCH RV Index** + +| RSN Value | $N_{sys} / N_{e,data,j} < 1/2$ | $1/2 \leq N_{sys} / N_{e,data,j}$ | +|-----------|-------------------------------------|-----------------------------------| +| | E-DCH RV Index | E-DCH RV Index | +| 0 | 0 | 0 | +| 1 | 2 | 3 | +| 2 | 0 | 2 | +| 3 | $[(TTIN/N_{ARQ}) \bmod 2] \times 2$ | $(TTIN/N_{ARQ}) \bmod 4$ | + +The UE shall use either + +- an RV index as indicated in Table 16 and according to the RSN +- or, if signalled by higher layers only E-DCH RV index 0 independently of the RSN. + +#### 4.9.2.3 Information field mapping of the "Happy" bit + +The UE shall set $x_{h,1}$ as specified in Table 16A. + +**Table 16A: Mapping of "Happy" bit** + +| "Happy" bit | $x_{h,1}$ | +|-------------|-----------| +| Happy | 1 | +| Not happy | 0 | + +#### 4.9.3 Multiplexing of E-DPCCH information + +The E-TFCI $x_{tfc,1}, x_{tfc,2}, \dots, x_{tfc,7}$ , the retransmission sequence number $x_{rsn,1}, x_{rsn,2}$ and the "happy" bit $x_{h,1}$ are multiplexed together. This gives a sequence of bits $x_1, x_2, \dots, x_{10}$ where + +$$x_k = x_{h,1} \quad k=1$$ + +$$x_k = x_{rsn,4-k} \quad k=2,3$$ + +$$x_k = x_{tfc,11-k} \quad k=4,5,\dots,10$$ + +#### 4.9.4 Channel coding for E-DPCCH + +Channel coding of the E-DPCCH is done using a sub-code of the second order Reed-Muller code. Coding is applied to the output $x_1, x_2, \dots, x_{10}$ from the E-DPCCH multiplexing, resulting in: + +$$i=0, 1, \dots, 29$$ + +The basis sequences are as described in 4.3.3 for $i=0, 1, \dots, 29$ . + +## 4.9.5 Physical channel mapping for E-DPCCH + +The E-DPCCH is described in [2]. The sequence of bits $z_0, z_1, \dots, z_{29}$ output from the E-DPCCH channel coding is mapped to the corresponding E-DPCCH sub frame. The bits are mapped so that they are transmitted over the air in ascending order with respect to $i$ . If the E-DCH TTI is equal to 10 ms the sequence of bits is transmitted in all the E-DPCCH sub frames of the E-DPCCH radio frame. + +For compressed frames in the uplink and the case when E-DCH TTI length is 10 ms, the bits mapped to the E-DPCCH idle slots specified in 4.4.5.3 shall not be transmitted. + +## 4.9A Coding for S-E-DPCCH + +The following information related to the transport block transmitted on the secondary stream is transmitted by means of the S-E-DPCCH: + +- Retransmission sequence number (RSN): $x_{rsn,1}, x_{rsn,2}$ +- E-TFCI: $x_{tfci,1}, x_{tfci,2}, \dots, x_{tfci,7}$ +- Spare: $x_{h,1}$ + +### 4.9A.1 Overview + +Overall coding chain for S-E-DPCCH follows that of the E-DPCCH described in clause 4.9.1. + +### 4.9A.2 S-E-DPCCH information field mapping + +#### 4.9A.2.1 Information field mapping of E-TFCI + +The E-TFCI mapping for S-E-DPCCH follows that of the E-DPCCH described in clause 4.9.2.1. + +#### 4.9A.2.2 Information field mapping of retransmission sequence number + +The RSN mapping for S-E-DPCCH follows that of the E-DPCCH described in clause 4.9.2.2. + +#### 4.9A.2.3 Information field mapping of the Spare bit + +This bit is fixed to "0" in this release of the specifications. + +### 4.9A.3 Multiplexing of S-E-DPCCH information + +The S-E-DPCCH multiplexing follows that of the E-DPCCH multiplexing described in clause 4.9.3. + +### 4.9A.4 Channel coding for S-E-DPCCH + +Channel coding for S-E-DPCCH follows the channel coding for E-DPCCH described in clause 4.9.4. + +### 4.9A.5 Physical channel mapping for S-E-DPCCH + +Physical channel mapping for S-E-DPCCH follows the physical channel mapping for E-DPCCH described in clause 4.9.5. + +## 4.10 Coding for E-AGCH + +The following information is transmitted by means of the absolute grant channel (E-AGCH): + +- Absolute Grant Value: $x_{agv,1}, x_{agv,2}, \dots, x_{agv,5}$ +- Absolute Grant Scope: $x_{ags,1}$ + +### 4.10.1 Overview + +Figure 24 below illustrates the overall coding chain for the E-AGCH. + +![Flowchart of the coding process for E-AGCH. The process starts with two input sequences: x_agv,1, x_agv,2, ..., x_agv,5 and xags,1. These are combined in a 'Multiplexing' block. The output of this block is x_ag,1, x_ag,2, ..., x_ag,6. This sequence is then processed by an 'ID specific CRC attachment' block, resulting in y_1, y_2, ..., y_22. This is followed by a 'Channel coding' block, which produces z_1, z_2, ..., z_90. The next step is 'Rate matching', which results in r_1, r_2, ..., r_60. Finally, a 'Physical channel mapping' block maps these values to the 'E-AGCH'.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) + +``` +graph TD; Input1["x_agv,1, x_agv,2, ..., x_agv,5"] --> Multiplexing[Multiplexing]; Input2["xags,1"] --> Multiplexing; Multiplexing --> Output1["x_ag,1, x_ag,2, ..., x_ag,6"]; Output1 --> CRC["ID specific CRC attachment"]; CRC --> Output2["y_1, y_2, ..., y_22"]; Output2 --> ChannelCoding["Channel coding"]; ChannelCoding --> Output3["z_1, z_2, ..., z_90"]; Output3 --> RateMatching["Rate matching"]; RateMatching --> Output4["r_1, r_2, ..., r_60"]; Output4 --> PhysicalMapping["Physical channel mapping"]; PhysicalMapping --> EAGCH["E-AGCH"]; +``` + +Flowchart of the coding process for E-AGCH. The process starts with two input sequences: x\_agv,1, x\_agv,2, ..., x\_agv,5 and xags,1. These are combined in a 'Multiplexing' block. The output of this block is x\_ag,1, x\_ag,2, ..., x\_ag,6. This sequence is then processed by an 'ID specific CRC attachment' block, resulting in y\_1, y\_2, ..., y\_22. This is followed by a 'Channel coding' block, which produces z\_1, z\_2, ..., z\_90. The next step is 'Rate matching', which results in r\_1, r\_2, ..., r\_60. Finally, a 'Physical channel mapping' block maps these values to the 'E-AGCH'. + +**Figure 24: Coding for E-AGCH** + +## 4.10.1A E-AGCH information field mapping + +### 4.10.1A.1 Information field mapping of the Absolute Grant Value + +The Absolute Grant Value information is specified in Table 16B and Table 16.B.1. The values are mapped such that $x_{agv,i}$ corresponds to the MSB of the index. + +Based on higher layer signalling, either Table 16B or Table 16.B.1 is selected. + +**Table 16B: Mapping of Absolute Grant Value** + +| Absolute Grant Value | Index | +|-----------------------|-------| +| $(168/15)^2 \times 6$ | 31 | +| $(150/15)^2 \times 6$ | 30 | +| $(168/15)^2 \times 4$ | 29 | +| $(150/15)^2 \times 4$ | 28 | +| $(134/15)^2 \times 4$ | 27 | +| $(119/15)^2 \times 4$ | 26 | +| $(150/15)^2 \times 2$ | 25 | +| $(95/15)^2 \times 4$ | 24 | +| $(168/15)^2$ | 23 | +| $(150/15)^2$ | 22 | +| $(134/15)^2$ | 21 | +| $(119/15)^2$ | 20 | +| $(106/15)^2$ | 19 | +| $(95/15)^2$ | 18 | +| $(84/15)^2$ | 17 | +| $(75/15)^2$ | 16 | +| $(67/15)^2$ | 15 | +| $(60/15)^2$ | 14 | +| $(53/15)^2$ | 13 | +| $(47/15)^2$ | 12 | +| $(42/15)^2$ | 11 | +| $(38/15)^2$ | 10 | +| $(34/15)^2$ | 9 | +| $(30/15)^2$ | 8 | +| $(27/15)^2$ | 7 | +| $(24/15)^2$ | 6 | +| $(19/15)^2$ | 5 | +| $(15/15)^2$ | 4 | +| $(11/15)^2$ | 3 | +| $(7/15)^2$ | 2 | +| ZERO_GRANT* | 1 | +| INACTIVE* | 0 | + +NOTE \*: These values are specified in [16]. + +**Table 16B.1: Alternative Mapping of Absolute Grant Value** + +| Absolute Grant Value | Index | +|-----------------------|-------| +| $(377/15)^2 \times 4$ | 31 | +| $(237/15)^2 \times 6$ | 30 | +| $(168/15)^2 \times 6$ | 29 | +| $(150/15)^2 \times 6$ | 28 | +| $(168/15)^2 \times 4$ | 27 | +| $(150/15)^2 \times 4$ | 26 | +| $(134/15)^2 \times 4$ | 25 | +| $(119/15)^2 \times 4$ | 24 | +| $(150/15)^2 \times 2$ | 23 | +| $(95/15)^2 \times 4$ | 22 | +| $(168/15)^2$ | 21 | +| $(150/15)^2$ | 20 | +| $(134/15)^2$ | 19 | +| $(119/15)^2$ | 18 | +| $(106/15)^2$ | 17 | +| $(95/15)^2$ | 16 | +| $(84/15)^2$ | 15 | +| $(75/15)^2$ | 14 | +| $(67/15)^2$ | 13 | +| $(60/15)^2$ | 12 | +| $(53/15)^2$ | 11 | +| $(47/15)^2$ | 10 | +| $(42/15)^2$ | 9 | +| $(38/15)^2$ | 8 | +| $(34/15)^2$ | 7 | +| $(30/15)^2$ | 6 | +| $(27/15)^2$ | 5 | +| $(24/15)^2$ | 4 | +| $(19/15)^2$ | 3 | +| $(15/15)^2$ | 2 | +| ZERO_GRANT* | 1 | +| INACTIVE* | 0 | + +NOTE \*: These values are specified in [16]. + +#### 4.10.1A.2 Information field mapping of the Absolute Grant Scope + +The value of $x_{ags,1}$ is set as specified in Table 16C. + +**Table 16C: Mapping of Absolute Grant Scope** + +| Absolute Grant Scope | $x_{ags,1}$ | +|----------------------|-------------| +| "Per HARQ process" | 1 | +| "All HARQ processes" | 0 | + +#### 4.10.1B Multiplexing of E-AGCH information + +The Absolute Grant Value information $x_{agv,1}, x_{agv,2}, \dots, x_{agv,5}$ and the Absolute Grant Scope information $x_{ags,1}$ are multiplexed together. This gives a sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,6}$ where + +$$x_{ag,k} = x_{agv,k} \quad k=1,2,\dots,5$$ + +$$x_{ag,k} = x_{ags,7-k} \quad k=6$$ + +## 4.10.2 CRC attachment for E-AGCH + +The E-RNTI is the E-DCH Radio Network Identifier defined in [13]. It is mapped such that $x_{id,1}$ corresponds to the MSB. + +From the sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,6}$ a 16 bit CRC is calculated according to clause 4.2.1.1. That gives the sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ and appended to the sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,6}$ to form the sequence of bits $y_1, y_2, \dots, y_{22}$ where + +$$y_i = x_{ag,i} \quad i=1,2,\dots,6$$ + +$$y_i = (c_{i-6} + x_{id,i-6}) \bmod 2 \quad i=7,\dots,22$$ + +## 4.10.3 Channel coding for E-AGCH + +Rate 1/3 convolutional coding, as described in Clause 4.2.3.1 is applied to the sequence of bits $y_1, y_2, \dots, y_{22}$ , resulting in the sequence of bits $z_1, z_2, \dots, z_{90}$ . + +## 4.10.4 Rate matching for E-AGCH + +From the input sequence $z_1, z_2, \dots, z_{90}$ the bits $z_1, z_2, z_5, z_6, z_7, z_{11}, z_{12}, z_{14}, z_{15}, z_{17}, z_{23}, z_{24}, z_{31}, z_{37}, z_{44}, z_{47}, z_{61}, z_{63}, z_{64}, z_{71}, z_{72}, z_{75}, z_{77}, z_{80}, z_{83}, z_{84}, z_{85}, z_{87}, z_{88}, z_{90}$ are punctured to obtain the output sequence $r_1, r_2, \dots, r_{60}$ . + +## 4.10.5 Physical channel mapping for E-AGCH + +The E-AGCH sub frame is described in [2]. The sequence of bits $r_1, r_2, \dots, r_{60}$ is mapped to the corresponding E-AGCH sub frame. The bits $r_k$ are mapped so that they are transmitted over the air in ascending order with respect to k. If the E-DCH TTI is equal to 10 ms the same sequence of bits is transmitted in all the E-AGCH sub frames of the E-AGCH radio frame. + +## 4.10A Coding for E-ROCH + +The following information is transmitted by means of the E-DCH rank and offset channel (E-ROCH): + +- S-ETFC Offset: $x_{seo,1}, x_{seo,2}, \dots, x_{seo,5}$ + +- Rank Indication: $x_{ri,1}$ + +### 4.10A.1 Overview + +The E-ROCH coding chain uses the same coding chain as the E-AGCH. Figure 24B below illustrates the overall coding chain for the E-ROCH. + +![Flowchart of the coding process for E-ROCH. The process starts with two input sequences: x_{seo,1}, x_{seo,2}, ..., x_{seo,5} and x_{r,1}. These are fed into a 'Multiplexing' block. The output of the multiplexing block is a sequence x_{r0,1}, x_{r0,2}, ..., x_{r0,6}, which is then processed by an 'ID specific CRC attachment' block. The output of this block is y_1, y_2, ..., y_{22}, which is then processed by a 'Channel coding' block. The output of the channel coding block is z_1, z_2, ..., z_{90}, which is then processed by a 'Rate matching' block. The output of the rate matching block is r_1, r_2, ..., r_{60}, which is then processed by a 'Physical channel mapping' block. The final output of the process is E-ROCH.](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) + +``` +graph TD; Input1["x_{seo,1}, x_{seo,2}, ..., x_{seo,5}"] --> Multiplexing[Multiplexing]; Input2["x_{r,1}"] --> Multiplexing; Multiplexing --> Output1["x_{r0,1}, x_{r0,2}, ..., x_{r0,6}"]; Output1 --> CRC["ID specific CRC attachment"]; CRC --> Output2["y_1, y_2, ..., y_{22}"]; Output2 --> ChannelCoding["Channel coding"]; ChannelCoding --> Output3["z_1, z_2, ..., z_{90}"]; Output3 --> RateMatching["Rate matching"]; RateMatching --> Output4["r_1, r_2, ..., r_{60}"]; Output4 --> PhysicalMapping["Physical channel mapping"]; PhysicalMapping --> EROCH["E-ROCH"]; +``` + +Flowchart of the coding process for E-ROCH. The process starts with two input sequences: x\_{seo,1}, x\_{seo,2}, ..., x\_{seo,5} and x\_{r,1}. These are fed into a 'Multiplexing' block. The output of the multiplexing block is a sequence x\_{r0,1}, x\_{r0,2}, ..., x\_{r0,6}, which is then processed by an 'ID specific CRC attachment' block. The output of this block is y\_1, y\_2, ..., y\_{22}, which is then processed by a 'Channel coding' block. The output of the channel coding block is z\_1, z\_2, ..., z\_{90}, which is then processed by a 'Rate matching' block. The output of the rate matching block is r\_1, r\_2, ..., r\_{60}, which is then processed by a 'Physical channel mapping' block. The final output of the process is E-ROCH. + +**Figure 24B: Coding for E-ROCH** + +## 4.10A.2 E-ROCH information field mapping + +### 4.10A.2.1 Information field mapping of the S-ETFC Offset + +The S-ETFC Offset information is specified in Table 16D. The values are mapped such that $x_{seo,i}$ corresponds to the MSB of the index. + +**Table 16D: Mapping of S-ETFC Offset value** + +| S-ETFC Offset Value | Index | +|---------------------|-------| +| 60/30 | 31 | +| 55/30 | 30 | +| 50/30 | 29 | +| 45/30 | 28 | +| 40/30 | 27 | +| 35/30 | 26 | +| 30/30 | 25 | +| 28/30 | 24 | +| 26/30 | 23 | +| 24/30 | 22 | +| 22/30 | 21 | +| 21/30 | 20 | +| 20/30 | 19 | +| 19/30 | 18 | +| 18/30 | 17 | +| 17/30 | 16 | +| 16/30 | 15 | +| 15/30 | 14 | +| 14/30 | 13 | +| 13/30 | 12 | +| 12/30 | 11 | +| 11/30 | 10 | +| 10/30 | 9 | +| 9/30 | 8 | +| 8/30 | 7 | +| 7/30 | 6 | +| 6/30 | 5 | +| 5/30 | 4 | +| 4/30 | 3 | +| 3/30 | 2 | +| 2/30 | 1 | +| 1/30 | 0 | + +#### 4.10A.2.2 Information field mapping of the Rank Indication + +The value of $x_{ri,1}$ is set as specified in Table 16E. + +**Table 16E: Mapping of Rank Indication** + +| Rank Indication | $x_{ri,1}$ | +|----------------------|------------| +| "Rank 2 allowed" | 1 | +| "Rank 2 not allowed" | 0 | + +#### 4.10A.3 Multiplexing of E-ROCH information + +The S-ETFC Offset information $x_{seo,1}, x_{seo,2}, \dots, x_{seo,5}$ and the Rank Indication information $x_{ri,1}$ are multiplexed together. This gives a sequence of bits $x_{ro,1}, x_{ro,2}, \dots, x_{ro,6}$ where + +$$x_{ro,k} = x_{seo,k} \quad k=1,2,\dots,5$$ + +$$x_{ro,6} = x_{ri,1}$$ + +#### 4.10A.4 CRC attachment for E-ROCH + +The S-E-RNTI is the E-DCH Radio Network Identifier specific to E-ROCH defined in [13]. It is mapped such that $x_{id,1}$ corresponds to the MSB. + +From the sequence of bits $x_{ro,1}, x_{ro,2}, \dots, x_{ro,6}$ a 16 bit CRC is calculated according to clause 4.2.1.1. That gives the sequence of bits $c_1, c_2, \dots, c_{16}$ where + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ and appended to the sequence of bits $x_{ro,1}, x_{ro,2}, \dots, x_{ro,6}$ to form the sequence of bits $y_1, y_2, \dots, y_{22}$ where + +$$y_i = x_{ro,i} \quad i=1,2,\dots,6$$ + +$$y_i = (c_{i-6} + x_{id,i-6}) \bmod 2 \quad i=7,\dots,22$$ + +#### 4.10A.5 Channel coding for E-ROCH + +Rate 1/3 convolutional coding, as described in Clause 4.2.3.1 is applied to the sequence of bits $y_1, y_2, \dots, y_{22}$ , resulting in the sequence of bits $z_1, z_2, \dots, z_{90}$ . + +#### 4.10A.6 Rate matching for E-ROCH + +From the input sequence $z_1, z_2, \dots, z_{90}$ the bits $z_1, z_2, z_5, z_6, z_7, z_{11}, z_{12}, z_{14}, z_{15}, z_{17}, z_{23}, z_{24}, z_{31}, z_{37}, z_{44}, z_{47}, z_{61}, z_{63}, z_{64}, z_{71}, z_{72}, z_{75}, z_{77}, z_{80}, z_{83}, z_{84}, z_{85}, z_{87}, z_{88}, z_{90}$ are punctured to obtain the output sequence $r_1, r_2, \dots, r_{60}$ . + +#### 4.10A.7 Physical channel mapping for E-ROCH + +The E-ROCH sub frame is described in [2]. The sequence of bits $r_1, r_2, \dots, r_{60}$ is mapped to the corresponding E-ROCH sub frame. The bits $r_k$ are mapped so that they are transmitted over the air in ascending order with respect to k. + +### 4.11 Mapping for E-RGCH Relative Grant + +#### 4.11.1 Overview + +The relative grant is transmitted on the E-RGCH as described in [2]. + +#### 4.11.2 Relative Grant mapping + +The relative grant (RG) command is mapped to the relative grant value as described in the table below. + +**Table 17: Mapping of RG value** + +| Command | RG Value (serving E-DCH RLS) | RG Value (other radio links) | +|---------|------------------------------|------------------------------| +| UP | +1 | not allowed | +| HOLD | 0 | 0 | +| DOWN | -1 | -1 | + +### 4.12 Mapping for E-HICH ACK/NACK + +#### 4.12.1 Overview + +The ACK/NACK is transmitted on the E-HICH as described in [2]. + +#### 4.12.2 ACK/NACK mapping + +The ACK/NACK command is mapped to the HARQ acknowledgement indicator as described in the table below. + +**Table 18: Mapping of HARQ Acknowledgement** + +| Command | HARQ acknowledgement indicator | +|---------------------------------------------------|--------------------------------| +| ACK | +1 | +| NACK (RLSs not containing the serving E-DCH cell) | 0 | +| NACK (RLS containing the serving E-DCH cell) | -1 | + +## Annex A (informative): Blind transport format detection + +### A.1 Blind transport format detection using fixed positions + +#### A.1.1 Blind transport format detection using received power ratio + +For the dual transport format case (the possible data rates are 0 and full rate, and CRC is only transmitted for full rate), blind transport format detection using received power ratio can be used. + +The transport format detection is then done using average received power ratio of DPDCH to DPCCH. Define the following: + +- $P_c$ : Received power per bit of DPCCH calculated from all pilot and TPC bits per slot over a radio frame; +- $P_d$ : Received power per bit of DPDCH calculated from $X$ bits per slot over a radio frame; +- $X$ : the number of DPDCH bits per slot when transport format corresponds to full rate; +- $T$ : Threshold of average received power ratio of DPDCH to DPCCH for transport format detection. + +The decision rule can then be formulated as: + +If $P_d/P_c > T$ then: + +- full rate transport format detected; + +else + +- zero rate transport format detected. + +#### A.1.2 Blind transport format detection using CRC + +For the multiple transport format case (the possible data rates are 0, ..., (full rate)/ $r$ , ..., full rate, and CRC is transmitted for all transport formats), blind transport format detection using CRC can be used. + +At the transmitter, the data stream with variable number of bits from higher layers is block-encoded using a cyclic redundancy check (CRC) and then convolutionally encoded. CRC parity bits are attached just after the data stream with variable number of bits as shown in figure A.1. + +The receiver knows only the possible transport formats (or the possible end bit position $\{n_{\text{end}}\}$ ) by Layer-3 negotiation. The receiver performs Viterbi-decoding on the soft decision sample sequence. The correct trellis path of the Viterbi-decoder ends at the zero state at the correct end bit position. + +The blind transport format detection method using CRC traces back the surviving trellis path ending at the zero state (hypothetical trellis path) at each possible end bit position to recover the data sequence. For each recovered data sequence error-detection is performed by checking the CRC, and if there is no error, the recovered sequence is declared to be correct. + +The following variable is defined: + +$$s(n_{\text{end}}) = -10 \log ( (a_0(n_{\text{end}}) - a_{\min}(n_{\text{end}})) / (a_{\max}(n_{\text{end}}) - a_{\min}(n_{\text{end}})) ) \text{ [dB]} \text{ (Eq. 1)}$$ + +where $a_{\max}(n_{\text{end}})$ and $a_{\min}(n_{\text{end}})$ are the maximum and minimum path-metric values among all survivors at end bit position $n_{\text{end}}$ , and $a_0(n_{\text{end}})$ is the path-metric value at zero state. + +In order to reduce the probability of false detection (this happens if the selected path is wrong but the CRC misses the error detection), a path selection threshold $D$ is introduced. The threshold $D$ determines whether the hypothetical trellis path connected to the zero state should be traced back or not at each end bit position $n_{\text{end}}$ . If the hypothetical trellis path connected to the zero state that satisfies: + +$$s(n_{\text{end}}) \leq D \quad (\text{Eq. 2})$$ + +is found, the path is traced back to recover the frame data, where $D$ is the path selection threshold and a design parameter. + +If more than one end bit positions satisfying Eq. 2 is found, the end bit position which has minimum value of $s(n_{\text{end}})$ is declared to be correct. If no path satisfying Eq. 2 is found even after all possible end bit positions have been exhausted, the received frame data is declared to be in error. + +Figure A-2 shows the procedure of blind transport format detection using CRC. + +![Diagram illustrating four possible transport formats with end bit positions n_end = 1, 2, 3, and 4. The formats consist of 'Data with variable number of bits', 'CRC', and 'Empty' fields.](819f1d00e68b342a246b64fa888a97f9_img.jpg) + +The diagram shows a horizontal sequence of three boxes representing different transport formats. Above the first box, the label $n_{\text{end}} = 1$ has a downward arrow pointing to it. Above the second box, the label $n_{\text{end}} = 2$ has a downward arrow pointing to it. Above the third box, the label $n_{\text{end}} = 3$ has a downward arrow pointing to it. Above the fourth box, the label $n_{\text{end}} = 4$ has a downward arrow pointing to it. The first box is labeled 'Data with variable number of bits'. The second box is labeled 'CRC'. The third box is labeled 'Empty'. The fourth box is empty. To the left of the first box, the text 'Possible end bit positions $n_{\text{end}}$ ' is present. + +Diagram illustrating four possible transport formats with end bit positions n\_end = 1, 2, 3, and 4. The formats consist of 'Data with variable number of bits', 'CRC', and 'Empty' fields. + +**Figure A.1: An example of data with variable number of bits. +Four possible transport formats, and transmitted end bit position $n_{\text{end}} = 3$** + +![Flowchart of the basic processing flow of blind transport format detection.](c15cb6383bc35906e6b3c7c3aac621ed_img.jpg) + +``` + + graph TD + START([START]) --> Init["nend = 1 +Smin = D +nend' = 0"] + Init --> Decode["Viterbi decoding (ACS operation) +to end bit position nend"] + Decode --> CalcS["Calculation of S(nend)"] + CalcS --> PathSel{Path selection} + PathSel -- "S(nend) > D" --> IsMax{Is nend the +maximum value?} + PathSel -- "S(nend) ≤ D" --> TraceBack["Tracing back +from end bit position nend"] + TraceBack --> CalcCRC["Calculation of CRC parity +for recovered data"] + CalcCRC --> CRC{CRC} + CRC -- NG --> IsMax + CRC -- OK --> CompareS{"Comparison +of S(nend)"} + CompareS -- "Smin ≤ S(nend)" --> IsMax + CompareS -- "Smin > S(nend)" --> Update["Smin = S(nend) +nend' = nend"] + Update --> IsMax + IsMax -- No --> IncNend["nend = nend + 1"] + IncNend --> Decode + IsMax -- Yes --> Output["Output detected +end bit position nend' *"] + Output --> END([END]) + +``` + +\* If the value of detected $n_{end}'$ is "0", the received frame data is declared to be in error. + +Flowchart of the basic processing flow of blind transport format detection. + +Figure A.2: Basic processing flow of blind transport format detection + +## A.2 Blind transport format detection using pseudo-flexible positions + +The blind detection procedure for each TTI begins by assuming a hypothesis for all values of $RM_i$ of Equation (1) of subclause 4.2.7, based on a corresponding hypothesis regarding whether certain TrCHs are delivering a transport block during that TTI. Based on this hypothesis, the blind detection then proceeds similar to blind transport format detection with fixed positions. If this hypothesis results in a successful detection of at least one transport format based on a passing CRC, the assumed hypothesis is considered to be validated to be correct. If there is no passing CRC, this process is repeated with another hypothesis, until all hypotheses are exhausted. + +## Annex B (informative): Compressed mode idle lengths + +The tables B.1-B.3 show the resulting idle lengths for different transmission gap lengths, UL/DL modes and DL frame types when DPCCH/DPDCH are used in the uplink and DPCH in the downlink. The idle lengths given are calculated purely from the slot and frame structures and the UL/DL offset. They do not contain margins for e.g. synthesizer switching. + +### B.1 Idle lengths for DL, UL and DL+UL compressed mode for DPCH + +**Table B.1: Parameters for DL compressed mode** + +| TGL | DL Frame Type | Spreading Factor | Idle length [ms] | Transmission time Reduction method | Idle frame Combining | +|-----|---------------|------------------|------------------|-----------------------------------------------------------|--------------------------------------------------| +| 3 | A | 512 – 4 | 1.73 – 1.99 | Spreading factor division by 2 or Higher layer scheduling | (S) | +| | B | | 1.60 – 1.86 | | (D) = (1,2) or (2,1) | +| 4 | A | | 2.40 – 2.66 | | (S) | +| | B | | 2.27 – 2.53 | | (D) = (1,3), (2,2) or (3,1) | +| 5 | A | | 3.07 – 3.33 | | (S) | +| | B | | 2.93 – 3.19 | | (D) = (1,4), (2,3), (3, 2) or (4,1) | +| 7 | A | | 4.40 – 4.66 | | (S) | +| | B | | 4.27 – 4.53 | | (D) = (1,6), (2,5), (3,4), (4,3), (5,2) or (6,1) | +| 10 | A | | 6.40 – 6.66 | | (D) = (3,7), (4,6), (5,5), (6,4) or (7,3) | +| | B | | 6.27 – 6.53 | | | +| 14 | A | | 9.07 – 9.33 | | (D) = (7,7) | +| | B | | 8.93 – 9.19 | | | + +**Table B.2: Parameters for UL compressed mode** + +| TGL | Spreading Factor | Idle length [ms] | Transmission time Reduction method | Idle frame Combining | +|-----|------------------|------------------|-----------------------------------------------------------|--------------------------------------------------| +| 3 | 256 – 4 | 2.00 | Spreading factor division by 2 or Higher layer scheduling | (S) | +| 4 | | 2.67 | | (D) = (1,2) or (2,1) | +| 5 | | 3.33 | | (S) | +| 7 | | 4.67 | | (D) = (1,3), (2,2) or (3,1) | +| 10 | | 6.67 | | (S) | +| 14 | | 9.33 | | (D) = (1,4), (2,3), (3, 2) or (4,1) | +| | | | | (S) | +| | | | | (D) = (1,6), (2,5), (3,4), (4,3), (5,2) or (6,1) | +| | | | | (D) = (3,7), (4,6), (5,5), (6,4) or (7,3) | +| | | | | (D) = (7,7) | + +**Table B.3: Parameters for combined UL/DL compressed mode** + +| TGL | DL Frame Type | Spreading Factor | Idle length [ms] | Transmission time Reduction method | Idle frame Combining | +|-----|---------------|--------------------------------------|------------------|-----------------------------------------------------------|-------------------------------------------------------| +| 3 | A or B | DL:
512 – 4

UL:
256 – 4 | 1.47 – 1.73 | Spreading factor division by 2 or Higher layer scheduling | (S)
(D) =(1,2) or (2,1) | +| 4 | | | 2.13 – 2.39 | | (S)
(D) =(1,3), (2,2) or (3,1) | +| 5 | | | 2.80 – 3.06 | | (S)
(D) = (1,4), (2,3), (3, 2) or (4,1) | +| 7 | | | 4.13 – 4.39 | | (S)
(D)=(1,6), (2,5), (3,4), (4,3), (5,2) or (6,1) | +| 10 | | | 6.13 – 6.39 | | (D)=(3,7), (4,6), (5,5), (6,4) or (7,3) | +| 14 | | | 8.80 – 9.06 | | (D) =(7,7) | + +(S): Single-frame method as shown in figure 14 (1). + +(D): Double-frame method as shown in figure 14 (2). (x,y) indicates x: the number of idle slots in the first frame, y: the number of idle slots in the second frame. + +NOTE: Compressed mode by spreading factor reduction is not supported when SF=4 is used in normal mode + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | RP_05 | RP-99588 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RP_06 | RP-99680 | 001 | 3 | Correction of rate matching parameters for repetition after 1st unterleaving in 25.212 | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 004 | - | Changing the initial offset value for convolutional code rate matching | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99681 | 005 | 1 | Introduction of compressed mode by higher layer scheduling | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99679 | 008 | - | Editorial corrections to TS 25.212 | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 009 | - | Removal of SFN multiplexing | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 010 | 1 | Clarification of bit separation and collection | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 011 | 2 | Connection between TTI and CFN | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 012 | 2 | Zero length transport blocks | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99679 | 014 | - | Update of channel coding sections | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 016 | - | Removal of TrCH restriction in DSCH CCTrCH | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99681 | 017 | - | 20 ms RACH message length | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 018 | - | Minimum SF in UL | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 024 | - | Rate matching parameter determination in DL and fixed positions | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99680 | 026 | 1 | Corrections to TS 25.212 | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99679 | 027 | - | Modification of BTFD description in 25.212 Annex | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99681 | 028 | - | TFCI coding and mapping including compressed mode | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RP_07 | RP-000061 | 025 | 2 | CR for parity bit attachment to 0 bit transport block | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 029 | 1 | Limitations of blind transport format detection | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 034 | 1 | Clarification of fixed position rate matching | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 035 | 1 | Clarification of DL compressed mode | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 036 | - | Reconfiguration of TFCS | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 037 | 1 | Removal of fixed gap position in 25.212 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 038 | 2 | Definition clarification for TS 25.212 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 039 | 1 | Clarification on TFCI coding input | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 041 | 2 | Correction of UL compressed mode by higher layer scheduling | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 042 | 5 | Downlink Compressed Mode by puncturing | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 044 | - | Modification of Turbo code internal interleaver | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 045 | - | Editorial corrections | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 046 | - | SF/2 method: DTX insertion after 2nd interleaver | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 047 | 1 | TFCI coding for FDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 048 | - | Mapping of TFCI in downlink compressed mode | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 049 | - | Editorial changes to Annex A | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 050 | - | Removal of rate matching attribute setting for RACH | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 052 | - | Padding Function for Turbo coding of small blocks | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 055 | 2 | Clarifications relating to DSCH | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000061 | 056 | - | Editorial modification of uplink shifting parameter calculation for turbo code puncturing | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000062 | 059 | 1 | Revision: Editorial correction to the calculation of Rate Matching parameters | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000062 | 060 | 1 | Editorial changes of channel coding section | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000062 | 061 | - | Removal of DL compressed mode by higher layer scheduling with fixed positions | 3.1.1 | 3.2.0 | +| 26/06/00 | RP_08 | RP-000266 | 066 | 1 | Clause 4.4.5 and table 9 is moved to informative annex | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 068 | - | Editorial modifications of 25.212 | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 069 | - | Removal of BTFD for flexible positions in Release 99 | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 070 | 1 | Editorial modifications | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 071 | 1 | Corrections and editorial modifications of 25.212 for 2nd insertion of DTX bits for CM | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 072 | 4 | Corrections to 25.212 (Rate Matching, p-bit insertion, PhCH segmentation) | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 073 | - | Editorial correction in 25.212 coding/multiplexing | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 074 | 2 | Bit separation of the Turbo encoded data | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 076 | 1 | Revision of code block segmentation description | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 077 | - | Clarifications for TFCI coding | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 078 | 2 | Clarifying the rate matching parameter setting for the RACH and BCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 080 | - | Clarification on BTFD utilisation (single CCTrCH) | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 081 | - | Correction of order of checking TFC during flexible position RM parameter determination | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 082 | - | Editorial corrections in channel coding section | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 083 | - | Correction for bit separation and bit collection | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000266 | 084 | 1 | Correction on the spreading factor selection for the RACH | 3.2.0 | 3.3.0 | +| 23/09/00 | RP_09 | RP-000341 | 079 | - | Clarification of compressed mode terminology | 3.3.0 | 3.4.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 23/09/00 | RP_09 | RP-000341 | 085 | 1 | Editorial corrections in Turbo code internal interleaver section | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 086 | 1 | Clarification on DL slot format for compressed mode by SF/2 | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 087 | - | Corrections | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 088 | 1 | Clarifications to TS 25.212 | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 089 | - | Correction regarding DSCH | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 090 | - | Correction regarding CPCH | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 092 | 1 | Bit separation and collection for rate matching | 3.3.0 | 3.4.0 | +| 23/09/00 | RP_09 | RP-000341 | 093 | - | Puncturing Limit definition in WG1 specification | 3.3.0 | 3.4.0 | +| 15/12/00 | RP_10 | RP-000538 | 094 | 2 | Correction of BTFD limitations | 3.4.0 | 3.5.0 | +| 15/12/00 | RP_10 | RP-000538 | 096 | - | Compressed mode by puncturing | 3.4.0 | 3.5.0 | +| 15/12/00 | RP_10 | RP-000538 | 097 | - | Clarification on the Ci formula | 3.4.0 | 3.5.0 | +| 15/12/00 | RP_10 | RP-000538 | 099 | - | Editorial modification in RM section | 3.4.0 | 3.5.0 | +| 15/12/00 | RP_10 | RP-000538 | 100 | 1 | Editorial corrections in TS 25.212 | 3.4.0 | 3.5.0 | +| 15/12/00 | RP_10 | RP-000538 | 101 | - | Correction to code block segmentation | 3.4.0 | 3.5.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 16/03/01 | RP_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 15/06/01 | RP_12 | RP-010332 | 106 | - | Correction of compressed mode by puncturing | 4.0.0 | 4.1.0 | +| 15/06/01 | RP_12 | RP-010332 | 108 | 1 | Dual transport format detection | 4.0.0 | 4.1.0 | +| 15/06/01 | RP_12 | RP-010332 | 112 | 1 | Correction for downlink rate matching for the DSCH | 4.0.0 | 4.1.0 | +| 21/09/01 | RP_13 | RP-010519 | 115 | - | Correction of PDSCH spreading factor signalling | 4.1.0 | 4.2.0 | +| 14/12/01 | RP_14 | RP-010737 | 118 | - | Clarification of compressed mode | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010737 | 122 | - | Support of multiple CCTrChs of dedicated type | 4.2.0 | 4.3.0 | +| 08/03/02 | RP_15 | RP-020231 | 128 | 2 | Removal of channel coding option "no coding" for FDD | 4.3.0 | 4.4.0 | +| 08/03/02 | RP_15 | RP-020054 | 123 | 4 | Inclusion of flexible hard split mode TFCI operation | 4.3.0 | 5.0.0 | +| 08/03/02 | RP_15 | RP-020058 | 126 | 1 | Changes to 25.212 for HSDPA work item | 4.3.0 | 5.0.0 | +| 07/06/02 | RP_16 | RP-020308 | 136 | - | Downlink bit mapping | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 130 | 5 | Correction of Errata noted by RAN1 delegates | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 131 | 2 | Removal of inconsistencies and ambiguities in the HARQ description | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 132 | - | Rate Matching and Channel Coding for HS-SCCH | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 137 | - | Basis sequences for HS-DPCCH Channel Quality information code | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 145 | 5 | UE specific masking for HS-SCCH part1 | 5.0.0 | 5.1.0 | +| 14/09/02 | RP_17 | RP-020582 | 141 | 1 | Bit scrambling for HS-DSCH | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020582 | 148 | - | Physical channel mapping for HS-DPCCH | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020582 | 149 | - | HARQ bit collection | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020582 | 150 | 1 | Coding for HS-SCCH | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020582 | 151 | - | Correction to UE specific masking for HS-SCCH part1 | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020568 | 155 | 2 | Clarification of the definition of layer 1 transport channel numbers | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020573 | 157 | - | Numbering Corrections | 5.1.0 | 5.2.0 | +| 15/09/02 | RP_17 | RP-020645 | 158 | 1 | Specification of H-RNTI to UE identity mapping | 5.1.0 | 5.2.0 | +| 20/12/02 | RP_18 | RP-020846 | 163 | - | Correction of CQI index to bit mapping | 5.2.0 | 5.3.0 | +| 20/12/02 | RP_18 | RP-020846 | 164 | - | Correction of mapping of HARQ-ACK | 5.2.0 | 5.3.0 | +| 26/03/03 | RP_19 | RP-030134 | 165 | 1 | Correction of CQI index to bit mapping | 5.3.0 | 5.4.0 | +| 26/03/03 | RP_19 | RP-030134 | 166 | 3 | Correction of bit scrambling of HS-DSCH | 5.3.0 | 5.4.0 | +| 26/03/03 | RP_19 | RP-030134 | - | - | Correction of subscript for modulation scheme information | 5.3.0 | 5.4.0 | +| 23/06/03 | RP_20 | RP-030272 | 172 | 1 | Clarification of TPC and Pilot transmission with STTD in compressed mode | 5.4.0 | 5.5.0 | +| 23/06/03 | RP_20 | RP-030272 | 173 | 2 | Correction on the flexible TFCI coding in the DSCH hard split mode for Rel5 | 5.4.0 | 5.5.0 | +| 21/09/03 | RP_21 | RP-030456 | 178 | 4 | Clarification on Single Transport Format Detection | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030456 | 179 | - | Correction on table number in first interleave description | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030456 | 180 | 3 | Broadening the conditions that require UEs to perform BTFD for the case of HS-DSCH reception | 5.5.0 | 5.6.0 | +| 06/01/04 | RP_22 | RP-030647 | 183 | - | Clarification of the CRC attachment procedure for HS-SCCH | 5.6.0 | 5.7.0 | +| 06/01/04 | RP_22 | RP-030647 | 184 | 1 | Correction of UE identity notation | 5.6.0 | 5.7.0 | +| 06/01/04 | RP_22 | RP-030644 | 185 | - | HARQ process identifier mapping | 5.6.0 | 5.7.0 | +| 06/01/04 | RP_22 | RP-030712 | 186 | - | Alignment of terminology across 3GPP documentation | 5.6.0 | 5.7.0 | +| 13/01/04 | RP_22 | - | - | - | Created for M.1457 update | 5.7.0 | 6.0.0 | +| 23/03/04 | RP_23 | RP-040085 | 187 | 1 | CCTrCH definition extension to HS-DSCH | 6.0.0 | 6.1.0 | +| 09/06/04 | RP_24 | RP-040230 | 191 | 1 | Clarification of Channelization Code-Set Mapping | 6.1.0 | 6.2.0 | +| 13/12/04 | RP_26 | RP-040446 | 192 | 2 | Introduction of MBMS Soft Combining | 6.2.0 | 6.3.0 | +| 13/12/04 | RP_26 | RP-040527 | 195 | - | Preamble and Postamble to reduce HS-DPCCH transmit power | 6.2.0 | 6.3.0 | +| 13/12/04 | RP_26 | RP-040449 | 196 | 2 | Introduction of E-DCH | 6.2.0 | 6.3.0 | +| 14/03/05 | RP_27 | RP-050088 | 193 | 1 | Introduction of F-DPCH | 6.3.0 | 6.4.0 | +| 14/03/05 | RP_27 | RP-050044 | 198 | 1 | PLnon-max and PLmax | 6.3.0 | 6.4.0 | +| 14/03/05 | RP_27 | RP-050045 | 199 | - | HARQ bit collection for E-DCH | 6.3.0 | 6.4.0 | +| 16/06/05 | RP_28 | RP-050241 | 203 | - | Correction of HSDPA Bit Separation | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 204 | 2 | E-DCH Corrections | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 205 | 1 | Compressed mode operation for the Enhanced Uplink | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050357 | 206 | 1 | E-HICH and E-RGCH serving/non-serving definition clarification | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050250 | 208 | 1 | Feature Clean Up: Removal of "CPCH" | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050248 | 210 | - | Feature Clean Up: Removal of DSCH (FDD mode) | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050243 | 212 | 1 | Feature Clean-Up: Removal of 80 ms TTI for DCH for all other cases but when the UE supports SF512 | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 215 | - | Clarification on E-AGCH bit mapping | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 216 | - | Determination of SF and number of PhCHs considering SF2 | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050251 | 217 | 1 | MBMS related corrections | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050249 | 218 | 1 | Feature clean up: Removal of the 'compressed mode by puncturing' | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 219 | - | Re-ordering of the E-DPCCH bit mapping | 6.4.0 | 6.5.0 | +| 16/06/05 | RP_28 | RP-050252 | 220 | - | Coding for E-AGCH | 6.4.0 | 6.5.0 | +| 26/09/05 | RP_29 | RP-050450 | 0222 | - | SF max for E-DPDCH | 6.5.0 | 6.6.0 | +| 26/09/05 | RP_29 | RP-050450 | 0223 | 1 | Compressed mode operation for the Enhanced Uplink | 6.5.0 | 6.6.0 | +| 26/09/05 | RP_29 | RP-050450 | 0225 | 1 | Absolute grant values | 6.5.0 | 6.6.0 | +| 26/09/05 | RP_29 | RP-050450 | 0227 | - | Removal of description on RSN setting | 6.5.0 | 6.6.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12/12/05 | RP_30 | RP-050727 | 0228 | - | PLmax alignment over all UE categories | 6.6.0 | 6.7.0 | +| 12/12/05 | RP_30 | RP-050727 | 0229 | - | Correction of SF when a CCTRCH is mapped onto four E-DPDCHs | 6.6.0 | 6.7.0 | +| 12/12/05 | RP_30 | RP-050727 | 0231 | 1 | Usage of 2xSF4 with puncturing | 6.6.0 | 6.7.0 | +| 20/03/06 | RP_31 | - | - | - | Creation of Release 7 specification (v.7.0.0) at RAN#31 | 6.7.0 | 7.0.0 | +| 12/06/06 | RP_32 | RP-060370 | 0236 | - | Clarification of E-TFCI terminology | 7.0.0 | 7.1.0 | +| 29/09/06 | RP_33 | RP-060490 | 0240 | - | Correction to the E-DCH HARQ rate matching for compressed mode | 7.1.0 | 7.2.0 | +| 11/12/06 | RP_34 | RP-060727 | 0244 | 1 | Clarification on the number of physical channels, transmission gap positioning and physical channel mapping for E-DCH in relation to compressed mode | 7.2.0 | 7.3.0 | +| 07/03/07 | RP_35 | RP-070115 | 0238 | 5 | Support of CPC feature | 7.3.0 | 7.4.0 | +| 07/03/07 | RP_35 | RP-070114 | 0241 | 4 | Coding of HS-SCCH to support FDD MIMO | 7.3.0 | 7.4.0 | +| 07/03/07 | RP_35 | RP-070114 | 0242 | 7 | Coding of HS-DPCCH to support operation of FDD MIMO | 7.3.0 | 7.4.0 | +| 07/03/07 | RP_35 | RP-070116 | 0245 | 4 | Introduction of 64QAM for HSDPA | 7.3.0 | 7.4.0 | +| 30/05/07 | RP_36 | RP-070387 | 0249 | - | MIMO HS-SCCH rate matching | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070387 | 0248 | 1 | Correction to coding of HS-SCCH to support FDD MIMO | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070387 | 0251 | 1 | HS-SCCH orders in MIMO mode | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070388 | 0246 | 5 | Introduction of 16QAM for HSUPA | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070384 | 0247 | 1 | Support for DL only SFN operation for MBMS FDD | 7.4.0 | 7.5.0 | +| 11/09/07 | RP_37 | RP-070644 | 0252 | - | 16QAM modulation selection for HSUPA | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070642 | 0253 | - | Clarifications of MIMO | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070641 | 0254 | - | Clarifications of CPC and MIMO | 7.5.0 | 7.6.0 | +| 27/11/07 | RP_38 | RP-070941 | 0257 | - | Correction of decimal to binary mapping in case of type B CQI | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070941 | 0259 | - | Correction of number of TBs in a TTI in case of MIMO | 7.6.0 | 7.7.0 | +| 28/11/07 | RP_38 | RP-070950 | 0256 | - | HS-SCCH information field mapping for 64QAM MIMO | 7.7.0 | 8.0.0 | +| 05/04/08 | RP_39 | RP-080146 | 0261 | - | Correction to RV-coding in case of simultaneous usage of 64QAM and MIMO | 8.0.0 | 8.1.0 | +| 28/05/08 | RP_40 | RP-080440 | 0262 | 1 | HS-SCCH orders for HS-SCCH-less operation | 8.1.0 | 8.2.0 | +| 28/05/08 | RP_40 | RP-080349 | 0264 | 2 | Clarification to number of HS-PDSCH codes in HS-SCCH less operations | 8.1.0 | 8.2.0 | +| 09/09/08 | RP_41 | RP-080673 | 270 | 2 | Introduction of HS-PDSCH Serving Cell Change Enhancements | 8.2.0 | 8.3.0 | +| 09/09/08 | RP_41 | RP-080665 | 272 | - | Correction to the table name and the quoted name | 8.2.0 | 8.3.0 | +| 03/12/08 | RP_42 | RP-080989 | 267 | 5 | Introduction of Dual-Cell HSDPA Operation on Adjacent Carriers | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080988 | 270 | 3 | Introduction of HS-PDSCH Serving Cell Change Enhancements | 8.3.0 | 8.4.0 | +| 03/03/09 | RP_43 | RP-090228 | 274 | 1 | Correction to the puncturing limit allowed when UL 4PAM modulation is allowed | 8.4.0 | 8.5.0 | +| 15/09/09 | RP_45 | RP-090885 | 278 | 1 | Reservation of HS-SCCH order combination not used by CPC | 8.5.0 | 8.6.0 | +| 15/09/09 | RP_45 | RP-090889 | 280 | 1 | Alignment with RAN2 decisions on HS-SCCH orders for activation and deactivation of DTX and DRX operation | 8.5.0 | 8.6.0 | +| 18/09/09 | RP_45 | RP-090975 | 276 | 4 | Introduction of TxAA extension for non-MIMO UEs | 8.6.0 | 9.0.0 | +| 18/09/09 | RP_45 | RP-090974 | 282 | 1 | Combination of DC-HSDPA with MIMO | 8.6.0 | 9.0.0 | +| 01/12/09 | RP_46 | RP-091170 | 281 | 2 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091171 | 283 | 3 | MIMO configuration per downlink frequency in DC-MIMO operation | 9.0.0 | 9.1.0 | +| 16/03/10 | RP_47 | RP-100206 | 286 | 1 | Clarification of MIMO configuration per downlink frequency in DC-MIMO operation | 9.1.0 | 9.2.0 | +| 14/09/10 | RP_49 | RP-100897 | 287 | 1 | Clarification of uplink frequencies | 9.2.0 | 9.3.0 | +| 16/09/10 | RP_49 | RP-100902 | 288 | 3 | Release 10 created with the introduction of 4C-HSDPA | 9.3.0 | 10.0.0 | +| 07/12/10 | RP_50 | RP-101318 | 290 | 3 | Clarification of 4C-HSDPA | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101318 | 295 | - | 4C-HSDPA summary of CQI reporting configurations | 10.0.0 | 10.1.0 | +| 05/12/11 | RP_54 | RP-111671 | 296 | 8 | Introduction of 8C-HSDPA | 10.1.0 | 11.0.0 | +| 05/12/11 | RP_54 | RP-111672 | 297 | 1 | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.1.0 | 11.0.0 | +| 28/02/12 | RP_55 | RP-120280 | 301 | - | Clarification to Target cell HS-SCCH order type | 11.0.0 | 11.1.0 | +| 28/02/12 | RP_55 | RP-120284 | 303 | - | Correction to 4C-HSDPA CQI report mapping scenarios table | 11.0.0 | 11.1.0 | +| 28/02/12 | RP_55 | RP-120287 | 304 | 1 | Introduction of 8C-HSDPA CQI report mapping scenarios table | 11.0.0 | 11.1.0 | +| 28/02/12 | RP_55 | RP-120288 | 305 | - | Corrections to Uplink Closed Loop Transmit Diversity | 11.0.0 | 11.1.0 | +| 13/06/12 | RP_56 | RP-120740 | 307 | 1 | Addition of missing 8C-HSDPA CQI reporting case indices | 11.1.0 | 11.2.0 | +| 13/06/12 | RP_56 | RP-120741 | 306 | - | Clarification of CLTD Features | 11.1.0 | 11.2.0 | +| 04/09/12 | RP_57 | RP-121271 | 308 | 2 | Introduction of Multiflow | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121267 | 310 | 1 | Correction of the number of CQI information bits for MC-HSDPA | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121268 | 311 | - | Correction of HS-SCCH order information | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121270 | 314 | - | Introduction of Further Enhancements to CELL_FACH | 11.2.0 | 11.3.0 | +| 04/12/12 | RP_58 | RP-121845 | 312 | 5 | Introduction of uplink MIMO and 64QAM | 11.3.0 | 11.4.0 | +| 04/12/12 | RP_58 | RP-121843 | 313 | 5 | Introduction of 4Tx_HSDPA in 25.212 | 11.3.0 | 11.4.0 | +| 04/12/12 | RP_58 | RP-121840 | 316 | 1 | Clarification of HS-SCCH order for MC-HSPA | 11.3.0 | 11.4.0 | +| 04/12/12 | RP_58 | RP-121844 | 317 | 1 | Clarifications and corrections to HSDPA Multiflow | 11.3.0 | 11.4.0 | +| 04/12/12 | RP_58 | RP-121842 | 318 | 1 | Clarification of HS-SCCH order information | 11.3.0 | 11.4.0 | +| 11/06/13 | RP_60 | RP-130745 | 319 | 2 | Correction to the HS-SCCH Type 4 Structure | 11.4.0 | 11.5.0 | +| 11/06/13 | RP_60 | RP-130748 | 320 | 1 | Clarification of HS-SCCH orders with the UE is configured in Multiflow and CLTD | 11.4.0 | 11.5.0 | +| 03/09/13 | RP_61 | RP-131245 | 321 | - | Correction of HS-SCCH type 4 order | 11.5.0 | 11.6.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03/03/14 | RP_63 | RP-140285 | 326 | - | Correction of HS-SCCH type 4 orderCorrection to HS-SCCH special information mapping for HS-SCCH less HSDPA | 11.6.0 | 11.7.0 | +| 10/09/14 | RP_65 | RP-141483 | 327 | 2 | Introduction of Further EUL Enhancements | 11.7.0 | 12.0.0 | +| 10/09/14 | RP_65 | RP-141482 | 328 | 2 | Introduction of Enhanced Broadcast of System Information | 11.7.0 | 12.0.0 | +| 10/09/14 | RP_65 | RP-141480 | 329 | 4 | Introduction of DCH Enhancements | 11.7.0 | 12.0.0 | +| 10/09/14 | RP_65 | RP-141481 | 330 | 1 | Introduction of UMTS Heterogeneous Networks enhancements | 11.7.0 | 12.0.0 | +| 08/12/14 | RP_66 | RP-142101 | 332 | 1 | Correction of DL FET | 12.0.0 | 12.1.0 | +| 08/12/14 | RP_66 | RP-142101 | 333 | - | Correction to TFCI bit mapping index in Rel-12 DCH Enhancements | 12.0.0 | 12.1.0 | +| 14/09/15 | RP_69 | RP-151469 | 334 | 6 | Introduction of the Multiflow 3F-4C configuration | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-06 | RP-72 | RP-161144 | 0340 | | F | Clarifications on DCH enhancements feature | 13.1.0 | +| 2016-06 | RP-72 | RP-161283 | 0338 | 2 | F | Clarification on UL DPCH 10ms Mode | 13.1.0 | +| 2016-12 | RP-74 | RP-162354 | 0344 | - | B | Introduction of HS-SCCH Order for HS-SCCH DRx feature in enhanced Cell Fach | 14.0.0 | +| 2016-12 | RP-74 | RP-162363 | 0345 | 1 | B | Introduction of multi-carrier enhancements for UMTS | 14.0.0 | +| 2017-09 | RP-77 | RP-171592 | 0347 | - | B | Introduction of the HS-SCCH orders for the additional triggering mechanism based on HS-SCCH orders | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25213/0fa26005ab105a07af4fda20b2554987_img.jpg b/marked/Rel-16/25_series/25213/0fa26005ab105a07af4fda20b2554987_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9985fa42245b1d0d24a7e13dfde8e2eb4c7b060a --- /dev/null +++ b/marked/Rel-16/25_series/25213/0fa26005ab105a07af4fda20b2554987_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed14944947deff969a893c2448a903f447a1bbb40e86527c56edc2530388cfc0 +size 24377 diff --git a/marked/Rel-16/25_series/25213/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-16/25_series/25213/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..922dfbd20218f4ba3076adbab1e27d95c896d5f8 --- /dev/null +++ b/marked/Rel-16/25_series/25213/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c7bf6869265bb978170e5159bf9b364400a9b2e4603599a47c8fc1102f5064a +size 75224 diff --git a/marked/Rel-16/25_series/25213/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/25_series/25213/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed50d858596a7af622bdf8243fd46f928f3f4ba6 --- /dev/null +++ b/marked/Rel-16/25_series/25213/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:166fd83b95b894a0741c1a91d65cad34bfcf4e414ae549a45669f9c719330d46 +size 8042 diff --git a/marked/Rel-16/25_series/25213/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/25_series/25213/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4193f0270a54487c9f328c8691fbcbe50a58999d --- /dev/null +++ b/marked/Rel-16/25_series/25213/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0282e9d134cb505138f5c9e5b0cd92c5adef5e0486307f9a7c368add3a0cd1db +size 26869 diff --git a/marked/Rel-16/25_series/25213/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25213/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db80628833ea5028ec932d917430d208fb5f36df --- /dev/null +++ b/marked/Rel-16/25_series/25213/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c94ff509a1c5b76139f6dd8a5ff8693ce91e4fc96cb1027c703ee673bed4c496 +size 64922 diff --git a/marked/Rel-16/25_series/25213/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/25_series/25213/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00615e373d9ec4d91ab5786bf5ea74e8ac7af872 --- /dev/null +++ b/marked/Rel-16/25_series/25213/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41bf69a8c0ac4e36de2e659087a591dada1ddfb365a08ba9c34288049e309c13 +size 50746 diff --git a/marked/Rel-16/25_series/25213/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Rel-16/25_series/25213/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cdcba35b7884c536641a079af8433cd59bc552b --- /dev/null +++ b/marked/Rel-16/25_series/25213/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c9d6a25059b57ac0ea2df27a1df80054460de0b3427e82e43010b1bf849a39c +size 66134 diff --git a/marked/Rel-16/25_series/25213/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/25_series/25213/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ddd4cab4bae6d7a0efa13d719f79bf380618f59 --- /dev/null +++ b/marked/Rel-16/25_series/25213/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0904a32bc5a4c84a1d76eb715dc01556c361168c7c7acd25ef8a4c4b52b24579 +size 24328 diff --git a/marked/Rel-16/25_series/25213/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/marked/Rel-16/25_series/25213/7ede87328f6b696dcffa65ebc4570cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bee7a91bfa256dadc8ea0e8d5c7ad6b88d3d3207 --- /dev/null +++ b/marked/Rel-16/25_series/25213/7ede87328f6b696dcffa65ebc4570cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c346ce44f3026c00c51873a7fa3461d6fe26f9c3b3df38c4d04c7a6449ac939 +size 11448 diff --git a/marked/Rel-16/25_series/25213/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/25_series/25213/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f59d39598ba659c6f751cf23586a76cffdd340b2 --- /dev/null +++ b/marked/Rel-16/25_series/25213/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c2895c60fa985e2e11c9f39b277e74f8987ff9ca8571d9ee0d921bf6f6e35a9 +size 25506 diff --git a/marked/Rel-16/25_series/25213/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/25_series/25213/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbbf885087ffe2f48128d6104ca4aa63f972cab5 --- /dev/null +++ b/marked/Rel-16/25_series/25213/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3114ad5f1361595f74cb5de457a269af8c3267c32ac24cf05fa1840a542a82db +size 8769 diff --git a/marked/Rel-16/25_series/25213/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/Rel-16/25_series/25213/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1be5dc03d0cc3109d1cf562daa5412bf16c5dbf --- /dev/null +++ b/marked/Rel-16/25_series/25213/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfbe006a83ed0bcb2691c50f16187ce8a5fcdba8417f06366c08258d65163262 +size 31152 diff --git a/marked/Rel-16/25_series/25213/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/25_series/25213/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3bdb37cc9116b6d17eaa62941b5e1671a8cdf00 --- /dev/null +++ b/marked/Rel-16/25_series/25213/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79cd9ea49aca7476999b60d000991d81f80a7fd1e0bd095b2f9dfd776a5b3f79 +size 28008 diff --git a/marked/Rel-16/25_series/25213/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/25_series/25213/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..553ef413ce65d8f8e53a4b3b850fbf88417df6dc --- /dev/null +++ b/marked/Rel-16/25_series/25213/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:122fe70860447d9c3e8fb03c93e7d0e0a2105ec072e3eacaa7965d3a8c719e1d +size 47430 diff --git a/marked/Rel-16/25_series/25213/b068dd12a75c78795832651369caecac_img.jpg b/marked/Rel-16/25_series/25213/b068dd12a75c78795832651369caecac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea2ca957e5e1146c39de5ccb72d52585cf964690 --- /dev/null +++ b/marked/Rel-16/25_series/25213/b068dd12a75c78795832651369caecac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ca7883d6e5cb4a8e1ff44f42ac880fd3fce5df2277cf9893483cdcc1b97fe12 +size 60221 diff --git a/marked/Rel-16/25_series/25213/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/25_series/25213/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c1fd4261b09235e9aa2ab5367d1a784da965c13 --- /dev/null +++ b/marked/Rel-16/25_series/25213/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f460180309592fc06a97a4b3347a1746cc390e1be68a5bbbe7e18ca63dded27 +size 44385 diff --git a/marked/Rel-16/25_series/25213/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/25_series/25213/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9060b4161863f2bcde293332cb40b665c7cf4ca9 --- /dev/null +++ b/marked/Rel-16/25_series/25213/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfb4bc3c98845b8ad83d8b52b39905ebc11be8638252d9e3a5192fc8960f4641 +size 11547 diff --git a/marked/Rel-16/25_series/25213/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-16/25_series/25213/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7020565e97b1bfa93296abce7c4ad3b70fbef5a3 --- /dev/null +++ b/marked/Rel-16/25_series/25213/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bb1b9f60405072076c16f7559795944e95d0a7e43640e8a73b1b2a43e399c8f +size 39037 diff --git a/marked/Rel-16/25_series/25213/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/25_series/25213/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fc9bffd78275908756250f18770c6f6033643e5 --- /dev/null +++ b/marked/Rel-16/25_series/25213/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e724b6962d26596bb12023837a64451c04561b20f9f9671bfedfba9577b8e15 +size 43703 diff --git a/marked/Rel-16/25_series/25213/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/marked/Rel-16/25_series/25213/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74bde5d9cbce043aebec5f894c846fcf65871eb9 --- /dev/null +++ b/marked/Rel-16/25_series/25213/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1868f5493a364cf24a1ea452a191a681fb115bf328274d865539f7cce688f3a8 +size 31404 diff --git a/marked/Rel-16/25_series/25213/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/25_series/25213/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6035549266a7d1aae7b9204817dc484e436abd60 --- /dev/null +++ b/marked/Rel-16/25_series/25213/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fecf31a3401e36217370a923f6c524f23e13ca65a97e94ca36b47c5c00c9e946 +size 36454 diff --git a/marked/Rel-16/25_series/25213/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/25_series/25213/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8c800b5537ffa1f5f6afcb5cc394de51e09c02c --- /dev/null +++ b/marked/Rel-16/25_series/25213/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:483cf142a8afaac7455bde8aeca36fdcb5bc6acc97d52e1abb15e93c0433d739 +size 22409 diff --git a/marked/Rel-16/25_series/25213/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-16/25_series/25213/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404d2de8e26a1f4d51a3ea65e039926179456126 --- /dev/null +++ b/marked/Rel-16/25_series/25213/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:593776556303be67ff8e99d38247ae8159fc4a74a351e6c24242354dff0c6907 +size 34581 diff --git a/marked/Rel-16/25_series/25213/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25213/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2689fa462ad5bcfb54c820d4e09478344523f3b1 --- /dev/null +++ b/marked/Rel-16/25_series/25213/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e1a84144001e981a321a3e0cb232573768d14e009d45b0a2b1bdbec3d5102c6 +size 49254 diff --git a/marked/Rel-16/25_series/25213/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/25_series/25213/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4e7ca807009f247ff4b07817aaf18101d910346 --- /dev/null +++ b/marked/Rel-16/25_series/25213/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e0ee66f280015b609b56139df347d94ffb942341970ad89b50793d3a3bbde5d +size 22658 diff --git a/marked/Rel-16/25_series/25213/raw.md b/marked/Rel-16/25_series/25213/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..68688688099fbef8b1cecb1730128e15670e8d33 --- /dev/null +++ b/marked/Rel-16/25_series/25213/raw.md @@ -0,0 +1,1909 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Symbols, abbreviations and definitions ..... | 6 | +| 3.1 Symbols..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 3.3 Definitions..... | 7 | +| 4 Uplink spreading and modulation..... | 8 | +| 4.1 Overview ..... | 8 | +| 4.2 Spreading..... | 8 | +| 4.2.1 Dedicated physical channels..... | 8 | +| 4.2.1.1 DPCCH/DPDCH ..... | 10 | +| 4.2.1.2 HS-DPCCH..... | 12 | +| 4.2.1.3 E-DPDCH/E-DPCCH..... | 13 | +| 4.2.1.4 S-DPCCH..... | 21 | +| 4.2.1.4.1 S-DPCCH gain factor setting while not transmitting rank-2 ..... | 21 | +| 4.2.1.4.2 S-DPCCH gain factor setting while transmitting rank-2 ..... | 22 | +| 4.2.1.5 S-E-DPCCH..... | 22 | +| 4.2.1.6 S-E-DPDCH..... | 23 | +| 4.2.1.7 DPCCH2 ..... | 24 | +| 4.2.2 PRACH..... | 25 | +| 4.2.2.1 PRACH preamble part..... | 25 | +| 4.2.2.2 PRACH message part ..... | 25 | +| 4.2.3 Void..... | 25 | +| 4.2.4 Channel combining for UL CLTD and UL MIMO..... | 25 | +| 4.3 Code generation and allocation..... | 26 | +| 4.3.1 Channelisation codes ..... | 26 | +| 4.3.1.1 Code definition ..... | 26 | +| 4.3.1.2 Code allocation for dedicated physical channels ..... | 27 | +| 4.3.1.2.1 Code allocation for DPCCH/ S-DPCCH/DPDCH/DPCCH2..... | 27 | +| 4.3.1.2.2 Code allocation for HS-DPCCH when the UE is not configured in MIMO mode with four transmit antennas in any cell..... | 28 | +| 4.3.1.2.2A Code allocation for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in at least one cell..... | 29 | +| 4.3.1.2.3 Code allocation for E-DPCCH/E-DPDCH ..... | 30 | +| 4.3.1.2.4 Code allocation for S-E-DPCCH/S-E-DPDCH ..... | 31 | +| 4.3.1.3 Code allocation for PRACH message part ..... | 31 | +| 4.3.1.4 Void ..... | 31 | +| 4.3.1.5 Void ..... | 31 | +| 4.3.2 Scrambling codes..... | 31 | +| 4.3.2.1 General..... | 31 | +| 4.3.2.2 Long scrambling sequence..... | 32 | +| 4.3.2.3 Short scrambling sequence ..... | 33 | +| 4.3.2.4 Dedicated physical channels scrambling code..... | 34 | +| 4.3.2.5 PRACH message part scrambling code ..... | 34 | +| 4.3.2.6 Void ..... | 35 | +| 4.3.2.7 Void ..... | 35 | +| 4.3.3 PRACH preamble codes..... | 35 | +| 4.3.3.1 Preamble code construction..... | 35 | +| 4.3.3.2 Preamble scrambling code..... | 35 | +| 4.3.3.3 Preamble signature..... | 35 | +| 4.3.4 Void..... | 36 | +| 4.4 Modulation ..... | 36 | +| 4.4.1 Modulating chip rate..... | 36 | +| 4.4.2 Modulation ..... | 36 | + +| | | | +|--------------------------------|-----------------------------------------------------------------------|-----------| +| 5 | Downlink spreading and modulation ..... | 37 | +| 5.1 | Spreading..... | 37 | +| 5.1.1 | Modulation mapper ..... | 37 | +| 5.1.1.1 | QPSK ..... | 37 | +| 5.1.1.2 | 16QAM ..... | 38 | +| 5.1.1.3 | 64QAM ..... | 38 | +| 5.1.2 | Channelisation ..... | 39 | +| 5.1.3 | IQ combining..... | 39 | +| 5.1.4 | Scrambling..... | 39 | +| 5.1.5 | Channel combining..... | 39 | +| 5.2 | Code generation and allocation ..... | 40 | +| 5.2.1 | Channelisation codes ..... | 40 | +| 5.2.2 | Scrambling code ..... | 41 | +| 5.2.3 | Synchronisation codes ..... | 43 | +| 5.2.3.1 | Code generation ..... | 43 | +| 5.2.3.2 | Code allocation of SSC..... | 43 | +| 5.3 | Modulation ..... | 45 | +| 5.3.1 | Modulating chip rate..... | 45 | +| 5.3.2 | Modulation ..... | 45 | +| Annex A (informative): | Generalised Hierarchical Golay Sequences ..... | 46 | +| A.1 | Alternative generation..... | 46 | +| Annex B (informative): | Uplink modulation for operation on adjacent frequencies..... | 47 | +| Annex B1 (informative): | Uplink modulation for UL CLTD..... | 48 | +| Annex B2 (informative): | Uplink modulation for operation on dual band frequencies ..... | 49 | +| Annex C (informative): | Change history..... | 50 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes spreading and modulation for UTRA Physical Layer FDD mode. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.201: "Physical layer - general description". +- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)." +- [3] 3GPP TS 25.101: "UE Radio transmission and Reception (FDD)". +- [4] 3GPP TS 25.104: "UTRA (BS) FDD; Radio transmission and Reception". +- [5] 3GPP TS 25.308: "UTRA High Speed Downlink Packet Access (HSDPA); Overall description". +- [6] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [7] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". + +# --- 3 Symbols, abbreviations and definitions + +## 3.1 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----------------|----------------------------------------------------------------------------| +| $C_{ch,SF,n}$ : | $n$ :th channelisation code with spreading factor $SF$ | +| $C_{pre,n,s}$ : | PRACH preamble code for $n$ :th preamble scrambling code and signature $s$ | +| $C_{sig,s}$ : | PRACH signature code for signature $s$ | +| $S_{dpch,n}$ : | $n$ :th DPCCH/DPDCH uplink scrambling code | +| $S_{r-pre,n}$ : | $n$ :th PRACH preamble scrambling code | +| $S_{r-msg,n}$ : | $n$ :th PRACH message scrambling code | +| $S_{dl,n}$ : | DL scrambling code | +| $C_{psc}$ : | PSC code | +| $C_{ssc,n}$ : | $n$ :th SSC code | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|------------------------------------| +| 16QAM | 16 Quadrature Amplitude Modulation | +| 4PAM | 4 Pulse Amplitude Modulation | +| 64QAM | 64 Quadrature Amplitude Modulation | +| 8PAM | 8 Pulse Amplitude Modulation | +| AICH | Acquisition Indicator Channel | +| BCH | Broadcast Channel | +| CCPCH | Common Control Physical Channel | + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------| +| CLTD | Closed Loop Transmit Diversity | +| CPICH | Common Pilot Channel | +| DCH | Dedicated Channel | +| DPCH | Dedicated Physical Channel | +| DPCCH | Dedicated Physical Control Channel | +| DPCCH2 | Dedicated Physical Control Channel 2 | +| DPDCH | Dedicated Physical Data Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DPCCH | E-DCH Dedicated Physical Control Channel | +| E-DPDCH | E-DCH Dedicated Physical Data Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-RGCH | E-DCH Relative Grant Channel | +| E-ROCH | E-DCH Rank and Offset Channel | +| FDD | Frequency Division Duplex | +| F-DPCH | Fractional Dedicated Physical Channel | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| HS-DPCCH | Dedicated Physical Control Channel (uplink) for HS-DSCH | +| HS-DPCCH 2 | Secondary Dedicated Physical Control Channel (uplink) for HS-DSCH, when Secondary_Cell_Enabled is greater than 3 | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Physical Channel for HS-DSCH | +| MBSFN | MBMS over a Single Frequency Network | +| Mcps | Mega Chip Per Second | +| MICH | MBMS Indication Channel | +| OVSF | Orthogonal Variable Spreading Factor (codes) | +| TPI | Transmitted Precoding Indicator | +| PICH | Page Indication Channel | +| PRACH | Physical Random Access Channel | +| PSC | Primary Synchronisation Code | +| RACH | Random Access Channel | +| SCH | Synchronisation Channel | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| S-E-DPCCH | Secondary Dedicated Physical Control Channel for E-DCH | +| S-E-DPDCH | Secondary Dedicated Physical Data Channel for E-DCH | +| SSC | Secondary Synchronisation Code | +| SF | Spreading Factor | +| UE | User Equipment | + +## 3.3 Definitions + +**Activated uplink frequency:** For a specific UE, an uplink frequency is said to be activated if the UE is allowed to transmit on that frequency. The primary uplink frequency is always activated when configured while a secondary uplink frequency has to be activated by means of an HS-SCCH order in order to become activated. Similarly, for a specific UE, an uplink frequency is said to be deactivated if it is configured but disallowed by the NodeB to transmit on that frequency. + +**Configured uplink frequency:** For a specific UE, an uplink frequency is said to be configured if the UE has received all relevant information from higher layers in order to perform transmission on that frequency. + +**Primary uplink frequency:** If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequency is configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**Secondary uplink frequency:** A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +# 4 Uplink spreading and modulation + +## 4.1 Overview + +Spreading is applied to the physical channels. It consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. + +With the channelisation, data symbols on so-called I- and Q-branches are independently multiplied with an OVSF code. With the scrambling operation, the resultant signals on the I- and Q-branches are further multiplied by complex-valued scrambling code, where I and Q denote real and imaginary parts, respectively. + +## 4.2 Spreading + +### 4.2.1 Dedicated physical channels + +The possible combinations of the maximum number of respective dedicated physical channels which may be configured simultaneously for a UE in addition to the DPCCH are specified in table 0. The actual UE capability may be lower than the values specified in table 0; the actual dedicated physical channel configuration is indicated by higher layer signalling. The actual number of configured DPDCHs, denoted $N_{\max\text{-dpdch}}$ , is equal to the largest number of DPDCHs from all the TFCs in the TFCS. $N_{\max\text{-dpdch}}$ is not changed by frame-by-frame TFCI change or temporary TFC restrictions. + +**Table 0: Maximum number of simultaneously-configured uplink dedicated channels** + +| | DPDCH | HS-DPCCH | E-DPDCH | E-DPCCH | S-E-DPDCH | S-E-DPCCH | +|--------|-----------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------|------------------------|-----------|-----------| +| Case 1 | 6 | 1 | - | - | - | - | +| Case 2 | 1 | 1 | 2 | 1 | - | - | +| Case 3 | - | 1 on the primary uplink frequency, 0 on any secondary uplink frequency | 4 per uplink frequency | 1 per uplink frequency | - | - | +| Case 4 | 1 | 2 | 2 | 1 | - | - | +| Case 5 | - | 2 on the primary uplink frequency, 0 on any secondary uplink frequency | 4 per uplink frequency | 1 per uplink frequency | - | - | +| Case 6 | - | 2 | 4 | 1 | 4 | 1 | +| Case X | 1 on the primary uplink frequency | 2 on the primary uplink frequency, 0 on any secondary uplink frequency | 2 on the primary uplink frequency, 4 on the secondary uplink frequency | 1 per uplink frequency | - | - | + +Figure 1 illustrates the principle of the spreading of uplink dedicated physical channels (DPCCH, DPDCHs, HS-DPCCH, DPCCH2, E-DPCCH, E-DPDCHs, S-E-DPCCH). Figure 1.1 illustrates the principle of the spreading of uplink S-DPCCH and S-E-DPDCHs. + +In case of BPSK modulation, the binary input sequences of all physical channels are converted to real valued sequences, i.e. the binary value "0" is mapped to the real value +1, the binary value "1" is mapped to the real value -1, and the value "DTX" (HS-DPCCH only) is mapped to the real value 0. + +In case of 4PAM modulation, the binary input sequences of all E-DPDCH and S-E-DPDCH physical channels are converted to real valued sequences, i.e. a set of two consecutive binary symbols $n_k, n_{k+1}$ (with $k \bmod 2 = 0$ ) in each binary sequence is converted to a real valued sequence following the mapping described in Table 0A. + +In case of 8PAM modulation, the binary input sequences of all E-DPDCH and S-E-DPDCH physical channels are converted to real valued sequences, i.e. a set of three consecutive binary symbols $n_k, n_{k+1}, n_{k+2}$ (with $k \bmod 3 = 0$ ) in each binary sequence is converted to a real valued sequence following the mapping described in Table 0B. + +**Table 0A: Mapping of E-DPDCH and S-E-DPDCH with 4PAM modulation** + +| $n_k, n_{k+1}$ | Mapped real value | +|----------------|-------------------| +| 00 | 0.4472 | +| 01 | 1.3416 | +| 10 | -0.4472 | +| 11 | -1.3416 | + +**Table 0B: Mapping of E-DPDCH and S-E-DPDCH with 8PAM modulation** + +| $n_k, n_{k+1}, n_{k+2}$ | Mapped real value | +|-------------------------|-------------------| +| 000 | 0.6547 | +| 001 | 0.2182 | +| 010 | 1.0911 | +| 011 | 1.5275 | +| 100 | -0.6547 | +| 101 | -0.2182 | +| 110 | -1.0911 | +| 111 | -1.5275 | + +![Block diagram of spreading for uplink dedicated channels. Five input channels (DPCCH/DPDCHs, DPCCH2, HS-DPCCH, E-DPDCHs/E-DPCCH, and S-E-DPCCH) are each processed by a 'Spreading' block. The outputs are labeled S_dpch, S_dpch2, S_hs-dpch, S_e-dpch, and S_s-e-dpch respectively. These five signals are summed together in a block labeled with the summation symbol Σ. The output of the summation block is labeled I+jQ. This complex signal is then multiplied by a spreading code S_dpch,n in a block labeled with a circle containing an 'X'. The final output is labeled S.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +Block diagram of spreading for uplink dedicated channels. Five input channels (DPCCH/DPDCHs, DPCCH2, HS-DPCCH, E-DPDCHs/E-DPCCH, and S-E-DPCCH) are each processed by a 'Spreading' block. The outputs are labeled S\_dpch, S\_dpch2, S\_hs-dpch, S\_e-dpch, and S\_s-e-dpch respectively. These five signals are summed together in a block labeled with the summation symbol Σ. The output of the summation block is labeled I+jQ. This complex signal is then multiplied by a spreading code S\_dpch,n in a block labeled with a circle containing an 'X'. The final output is labeled S. + +**Figure 1: Spreading for uplink dedicated channels** + +![Figure 1.1: Spreading for uplink S-DPCCH and S-E-DPDCHs. Block diagram showing S-DPCCH and S-E-DPDCHs inputs entering individual 'Spreading' blocks. The outputs, S_s-dpcch and S_s-e-dpdch respectively, enter a summation block (Σ). The output of the summation is labeled I+jQ, which is then multiplied (×) by a scrambling code S_dpcch,n to produce the final output S'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 1.1: Spreading for uplink S-DPCCH and S-E-DPDCHs. Block diagram showing S-DPCCH and S-E-DPDCHs inputs entering individual 'Spreading' blocks. The outputs, S\_s-dpcch and S\_s-e-dpdch respectively, enter a summation block (Σ). The output of the summation is labeled I+jQ, which is then multiplied (×) by a scrambling code S\_dpcch,n to produce the final output S'. + +**Figure 1.1: Spreading for uplink S-DPCCH and S-E-DPDCHs** + +The spreading operation is specified in subclauses 4.2.1.1 to 4.2.1.4 for each of the dedicated physical channels; it includes a spreading stage, a weighting stage, and an IQ mapping stage. In the process, the streams of real-valued chips on the I and Q branches are summed; this results in a complex-valued stream of chips for each set of channels. + +As described in figure 1, the resulting complex-valued streams $S_{\text{dpch}}$ , $S_{\text{dpcch2}}$ , $S_{\text{hs-dpcch}}$ , $S_{\text{e-dpch}}$ and $S_{\text{s-e-dpcch}}$ are summed into a single complex-valued stream which is then scrambled by the complex-valued scrambling code $S_{\text{dpch,n}}$ resulting in the complex-valued signal $S$ . As described in Figure 1.1, the resulting complex-valued streams $S_{\text{s-dpcch}}$ and $S_{\text{s-e-dpdch}}$ are summed into a single complex-valued stream which is scrambled by the same complex-valued scrambling code $S_{\text{dpch,n}}$ resulting in the complex-valued signal $S'$ . The scrambling code shall be applied aligned with the radio frames, i.e. the first scrambling chip corresponds to the beginning of a radio frame. + +NOTE: Although subclause 4.2.1 has been reorganized in this release, the spreading operation for the DPCCH, DPDCH remains unchanged as compared to the previous release. + +#### 4.2.1.1 DPCCH/DPDCH + +Figure 1a illustrates the spreading operation for the uplink DPCCH and DPDCHs. + +![Block diagram of spreading for uplink DPCCH/DPDCHs. The diagram shows two parallel processing paths for the in-phase (I) and quadrature (Q) components of the signal S_dpch. The I-path consists of three DPDCH signals (DPDCH1, DPDCH3, DPDCH5) each multiplied by a channelisation code (c_d,1, c_d,3, c_d,5) and a gain factor (beta_d), then summed. The Q-path consists of four signals (DPDCH2, DPDCH4, DPDCH6, DPCCH) each multiplied by a channelisation code (c_d,2, c_d,4, c_d,6, c_c) and a gain factor (beta_d for DPDCHs, beta_c for DPCCH), then summed. The output of the Q-path sum is multiplied by the imaginary unit j. Finally, the I-path output and the j-multiplied Q-path output are summed to produce the final signal S_dpch.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Block diagram of spreading for uplink DPCCH/DPDCHs. The diagram shows two parallel processing paths for the in-phase (I) and quadrature (Q) components of the signal S\_dpch. The I-path consists of three DPDCH signals (DPDCH1, DPDCH3, DPDCH5) each multiplied by a channelisation code (c\_d,1, c\_d,3, c\_d,5) and a gain factor (beta\_d), then summed. The Q-path consists of four signals (DPDCH2, DPDCH4, DPDCH6, DPCCH) each multiplied by a channelisation code (c\_d,2, c\_d,4, c\_d,6, c\_c) and a gain factor (beta\_d for DPDCHs, beta\_c for DPCCH), then summed. The output of the Q-path sum is multiplied by the imaginary unit j. Finally, the I-path output and the j-multiplied Q-path output are summed to produce the final signal S\_dpch. + +**Figure 1A: Spreading for uplink DPCCH/DPDCHs** + +The DPCCH is spread to the chip rate by the channelisation code $c_c$ . The $n$ :th DPDCH called $DPDCH_n$ is spread to the chip rate by the channelisation code $c_{d,n}$ . + +After channelisation, the real-valued spread signals are weighted by gain factors, $\beta_c$ for DPCCH, $\beta_d$ for all DPDCHs. + +The $\beta_c$ and $\beta_d$ values are signalled by higher layers or derived as described in [6] 5.1.2.5 and 5.1.2.5C. At every instant in time, at least one of the values $\beta_c$ and $\beta_d$ has the amplitude 1.0. The $\beta_c$ and $\beta_d$ values are quantized into 4 bit words. The quantization steps are given in table 1. + +**Table 1: The quantization of the gain parameters** + +| Signalled values for $\beta_c$ and $\beta_d$ | Quantized amplitude ratios $\beta_c$ and $\beta_d$ | +|----------------------------------------------|----------------------------------------------------| +| 15 | 1.0 | +| 14 | 14/15 | +| 13 | 13/15 | +| 12 | 12/15 | +| 11 | 11/15 | +| 10 | 10/15 | +| 9 | 9/15 | +| 8 | 8/15 | +| 7 | 7/15 | +| 6 | 6/15 | +| 5 | 5/15 | +| 4 | 4/15 | +| 3 | 3/15 | +| 2 | 2/15 | +| 1 | 1/15 | +| 0 | Switch off | + +#### 4.2.1.2 HS-DPCCH + +Figure 1B illustrates the spreading operation for the HS-DPCCH when Secondary\_Cell\_Enabled is less than 4 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or less than 2 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell. Figure 1B.1 illustrates the spreading operation for the HS-DPCCHs when Secondary\_Cell\_Enabled is greater than 3 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or greater than 1 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell.. + +![Figure 1B: Spreading for uplink HS-DPCCH. The diagram shows two parallel processing paths for the HS-DPCCH signal. The top path is for the In-phase (I) component, where the input signal is multiplied by c_hs and then beta_hs to produce the I component. The bottom path is for the Quadrature (Q) component, where the input signal is multiplied by c_hs and then beta_hs to produce the Q component, which is then multiplied by j. The I and Q components are summed to produce the final signal S_hs-dpch.](853f59c89931a666c07903b31d098277_img.jpg) + +The diagram illustrates the spreading operation for the HS-DPCCH. It consists of two main processing paths: + + +- I Component Path:** The input HS-DPCCH signal (labeled "If $N_{max-dpch} = 2, 4 \text{ or } 6$ ") is first multiplied by $c_{hs}$ and then by $\beta_{hs}$ to produce the In-phase (I) component. +- Q Component Path:** The input HS-DPCCH signal (labeled "If $N_{max-dpch} = 0, 1, 3, 5$ ") is first multiplied by $c_{hs}$ and then by $\beta_{hs}$ to produce the Quadrature (Q) component. This Q component is then multiplied by $j$ . +- Summation:** The I component and the $j \cdot Q$ component are summed together to produce the final output signal $S_{hs-dpch}$ . + +Figure 1B: Spreading for uplink HS-DPCCH. The diagram shows two parallel processing paths for the HS-DPCCH signal. The top path is for the In-phase (I) component, where the input signal is multiplied by c\_hs and then beta\_hs to produce the I component. The bottom path is for the Quadrature (Q) component, where the input signal is multiplied by c\_hs and then beta\_hs to produce the Q component, which is then multiplied by j. The I and Q components are summed to produce the final signal S\_hs-dpch. + +**Figure 1B: Spreading for uplink HS-DPCCH when Secondary\_Cell\_Enabled is less than 4 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or less than 2 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell** + +![Figure 1B.1: Spreading for uplink HS-DPCCHs. The diagram shows two input signals, HS-DPCCH2 and HS-DPCCH, being processed through channelisation codes (c_hs) and gain factors (beta_hs) to produce in-phase (I) and quadrature (Q) components. These components are then combined to form the final signal S_hs-dpch.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the spreading process for uplink HS-DPCCHs. + - The top path for HS-DPCCH2 involves multiplying the input by a channelisation code $c_{hs}$ and then by a gain factor $\beta_{hs}$ to produce the in-phase component $I$ . + - The bottom path for HS-DPCCH involves multiplying the input by a channelisation code $c_{hs}$ and then by a gain factor $\beta_{hs}$ to produce a signal that is further multiplied by $j$ to produce the quadrature component $Q$ . + - The components $I$ and $Q$ are then summed at a block labeled $I+jQ$ to produce the final output signal $S_{hs-dpch}$ . + +Figure 1B.1: Spreading for uplink HS-DPCCHs. The diagram shows two input signals, HS-DPCCH2 and HS-DPCCH, being processed through channelisation codes (c\_hs) and gain factors (beta\_hs) to produce in-phase (I) and quadrature (Q) components. These components are then combined to form the final signal S\_hs-dpch. + +**Figure 1B.1: Spreading for uplink HS-DPCCHs when Secondary\_Cell\_Enabled is greater than 3 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or greater than 1 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell** + +Each HS-DPCCH shall be spread to the chip rate by the channelisation code $c_{hs}$ . + +After channelisation, the real-valued spread signals are weighted by gain factor $\beta_{hs}$ + +The $\beta_{hs}$ values are derived from the quantized amplitude ratios $A_{hs}$ which are translated from $\Delta_{ACK}$ , $\Delta_{NACK}$ and $\Delta_{CQI}$ signalled by higher layers as described in [6] 5.1.2.5A. + +The translation of $\Delta_{ACK}$ , $\Delta_{NACK}$ and $\Delta_{CQI}$ into quantized amplitude ratios $A_{hs} = \beta_{hs}/\beta_c$ in the case that DPCCH2 is not configured, and $A_{hs} = \beta_{hs}/\beta_{c2}$ in the case that DPCCH2 is configured is shown in Table 1A. + +**Table 1A: The quantization of the power offset** + +| Signalled values for $\Delta_{ACK}$ , $\Delta_{NACK}$ and $\Delta_{CQI}$ | Quantized amplitude ratios $A_{hs} = \beta_{hs}/\beta_c$ or $\beta_{hs}/\beta_{c2}$ | +|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| 12 | 76/15 | +| 11 | 60/15 | +| 10 | 48/15 | +| 9 | 38/15 | +| 8 | 30/15 | +| 7 | 24/15 | +| 6 | 19/15 | +| 5 | 15/15 | +| 4 | 12/15 | +| 3 | 9/15 | +| 2 | 8/15 | +| 1 | 6/15 | +| 0 | 5/15 | + +If Secondary\_Cell\_Enabled is less than 4 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or less than 2 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell, HS-DPCCH shall be mapped to the I branch in case $N_{max-dpch}$ is 2, 4 or 6, and to the Q branch otherwise ( $N_{max-dpch} = 0, 1, 3$ or 5). If Secondary\_Cell\_Enabled is greater than 3 in case the UE is not configured in MIMO mode with four transmit antennas in any cell, or greater than 1 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell, HS-DPCCH shall be mapped to the Q branch and HS-DPCCH2 shall be mapped to the I branch. + +#### 4.2.1.3 E-DPDCH/E-DPCCH + +Figure 1C illustrates the spreading operation for the E-DPDCHs and the E-DPCCH. + +![Figure 1C: Spreading for E-DPDCH/E-DPCCH. The diagram shows multiple signal paths (E-DPDCH1, ..., E-DPDCHk, E-DPCCH) entering a summation block. Each path consists of a series of three multipliers. The first multiplier takes the channel signal and a channelisation code (ced,1 to ced,k or cec). The second multiplier takes the output and a gain factor (bed,1 to bed,k or bec). The third multiplier takes the output and an in-phase component (iqed,1 to iqed,k or iqec). The outputs of all multipliers are summed in a block labeled with a large sigma symbol. The output of the summation block is labeled I+jQ and Se-dpch.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 1C: Spreading for E-DPDCH/E-DPCCH. The diagram shows multiple signal paths (E-DPDCH1, ..., E-DPDCHk, E-DPCCH) entering a summation block. Each path consists of a series of three multipliers. The first multiplier takes the channel signal and a channelisation code (ced,1 to ced,k or cec). The second multiplier takes the output and a gain factor (bed,1 to bed,k or bec). The third multiplier takes the output and an in-phase component (iqed,1 to iqed,k or iqec). The outputs of all multipliers are summed in a block labeled with a large sigma symbol. The output of the summation block is labeled I+jQ and Se-dpch. + +**Figure 1C: Spreading for E-DPDCH/E-DPCCH** + +The E-DPCCH shall be spread to the chip rate by the channelisation code $c_{ec}$ . The $k$ :th E-DPDCH, denominated E-DPDCH $_k$ , shall be spread to the chip rate using channelisation code $c_{ed,k}$ . + +After channelisation, the real-valued spread E-DPCCH and E-DPDCH $_k$ signals shall respectively be weighted by gain factor $\beta_{ec}$ and $\beta_{ed,k}$ . + +$E-TFCI_{ec,boost}$ may be signalled by higher layers. If $E-TFCI_{ec,boost}$ is not signalled by higher layers a default value 127 shall be used. When UL\_MIMO\_Enabled is TRUE the UE shall assume $E-TFCI_{ec,boost} = -1$ for rank-2 transmissions. + +When $E-TFCI \leq E-TFCI_{ec,boost}$ the value of $\beta_{ec}$ shall be derived as specified in [6] based on the quantized amplitude ratio $A_{ec}$ which is translated from $\Delta_{E-DPCCH}$ signalled by higher layers. The translation of $\Delta_{E-DPCCH}$ into quantized amplitude ratios $A_{ec} = \beta_{ec}/\beta_c$ is specified in Table 1B. + +**Table 1B: Quantization for $\Delta_{E-DPCCH}$ for $E-TFCI \leq E-TFCI_{ec,boost}$** + +| Signalled values for $\Delta_{E-DPCCH}$ | Quantized amplitude ratios $A_{ec} = \beta_{ec}/\beta_c$ | +|-----------------------------------------|----------------------------------------------------------| +| 15 | 151/15 | +| 14 | 120/15 | +| 13 | 95/15 | +| 12 | 76/15 | +| 11 | 60/15 | +| 10 | 48/15 | +| 9 | 38/15 | +| 8 | 30/15 | +| 7 | 24/15 | +| 6 | 19/15 | +| 5 | 15/15 | +| 4 | 12/15 | +| 3 | 9/15 | +| 2 | 8/15 | +| 1 | 6/15 | +| 0 | 5/15 | + +When $E\text{-TFCI} > E\text{-TFCI}_{ec,boost}$ , in order to provide an enhanced phase reference, the value of $\beta_{ec}$ shall be derived as specified in [6] based on a traffic to total pilot power offset $\Delta_{T2TP}$ , configured by higher layers as specified in Table 1B.0 and the quantization of the ratio $\beta_{ed}/\beta_c$ as specified in Table 1B.0A. + +**Table 1B.0: $\Delta_{T2TP}$** + +| Signalled values for $\Delta_{T2TP}$ | Power offset values $\Delta_{T2TP}$ [dB] | +|--------------------------------------|------------------------------------------| +| 6 | 16 | +| 5 | 15 | +| 4 | 14 | +| 3 | 13 | +| 2 | 12 | +| 1 | 11 | +| 0 | 10 | + +Table 1B.0A: Quantization for $\beta_{ed}/\beta_c$ for $E\text{-TFCI} > E\text{-TFCI}_{ec,boost}$ + +| Quantized amplitude ratios $\beta_{ed}/\beta_c$ | E-DPDCH modulation schemes which may be used in the same subframe | +|-------------------------------------------------|-------------------------------------------------------------------| +| 239/15 | 4PAM, 8PAM | +| 190/15 | 4PAM, 8PAM | +| 151/15 | 4PAM, 8PAM | +| 120/15 | BPSK, 4PAM, 8PAM | +| 95/15 | BPSK, 4PAM, 8PAM | +| 76/15 | BPSK, 4PAM, 8PAM | +| 60/15 | BPSK, 4PAM, 8PAM | +| 48/15 | BPSK, 4PAM, 8PAM | +| 38/15 | BPSK, 4PAM, 8PAM | +| 30/15 | BPSK, 4PAM, 8PAM | +| 24/15 | BPSK, 4PAM, 8PAM | +| 19/15 | BPSK, 4PAM, 8PAM | +| 15/15 | BPSK, 4PAM, 8PAM | +| 12/15 | BPSK, 4PAM, 8PAM | +| 9/15 | BPSK | +| 8/15 | BPSK, 4PAM, 8PAM | +| 6/15 | BPSK, 4PAM, 8PAM | +| 5/15 | BPSK | + +The value of $\beta_{ed,k}$ shall be computed as specified in [6] subclause 5.1.2.5B.2, based on the reference gain factors, the spreading factor for E-DPDCHk, the HARQ offsets, and the quantization of the ratio $\beta_{ed,k}/\beta_c$ into amplitude ratios specified in Table 1B.2 for the case when $E\text{-TFCI} \leq E\text{-TFCI}_{ec,boost}$ and Table 1B.2B, for the case when $E\text{-TFCI} > E\text{-TFCI}_{ec,boost}$ . + +The reference gain factors are derived from the quantised amplitude ratios $A_{ed}$ which is translated from $\Delta_{E\text{-DPDCH}}$ signalled by higher layers. The translation of $\Delta_{E\text{-DPDCH}}$ into quantized amplitude ratios $A_{ed} = \beta_{ed}/\beta_c$ is specified in Table 1B.1 for the case when $E\text{-TFCI} \leq E\text{-TFCI}_{ec,boost}$ and Table 1B.2A for the case when $E\text{-TFCI} > E\text{-TFCI}_{ec,boost}$ . + +When the UE is configured in MIMO mode and transmitting two transport blocks, one with a set of E-DPDCHs and another with a set of S-E-DPDCHs, the amplitude ratios $A_{ed}$ for the primary stream are modified to take the inter-stream interference into account. Note that the amplitude ratios for the secondary stream are not modified. The amplitude ratios $A_{ed}$ for the primary stream are then given by + +$$A_{ed} = A_{ed,ISI} \times A_{ISI}$$ + +$A_{ed,ISI}$ is translated from $\Delta_{E\text{-DPDCH}}$ signalled by higher layers. The translation of $\Delta_{E\text{-DPDCH}}$ into quantized amplitude ratios $A_{ed,ISI}$ is specified in Table 1B.2A. $A_{ISI}$ is an inter-stream interference compensation factor that is translated from $\Delta_{ISI}$ signalled by higher layers according to Table 1B.0B. Note that this procedure does not affect the power used for the + +transmission of the primary stream E-TFC, but rather lowers the size of the primary stream transport block in order to compensate for the inter-stream interference. + +**Table 1B.0B: Quantization of $\Delta_{ISI}$** + +| Signalled values for
$\Delta_{ISI}$ | Quantized amplitude ratios
$A_{ISI}$ | +|-----------------------------------------------|------------------------------------------------| +| 15 | 30/15 | +| 14 | 29/15 | +| 13 | 28/15 | +| 12 | 27/15 | +| 11 | 26/15 | +| 10 | 25/15 | +| 9 | 24/15 | +| 8 | 23/15 | +| 7 | 22/15 | +| 6 | 21/15 | +| 5 | 20/15 | +| 4 | 19/15 | +| 3 | 18/15 | +| 2 | 17/15 | +| 1 | 16/15 | +| 0 | 15/15 | + +**Table 1B.1: Quantization for $\Delta_{E-DPDCH}$ for $E-TFCI \leq E-TFCI_{ec,boost}$** + +| Signalled values for $\Delta_{E-DPDCH}$ | Quantized amplitude ratios $A_{ed} = \beta_{ed}/\beta_c$ | E-DPDCH modulation schemes which may be used in the same subframe | +|-----------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------| +| 29 | 168/15 | BPSK | +| 28 | 150/15 | BPSK | +| 27 | 134/15 | BPSK | +| 26 | 119/15 | BPSK | +| 25 | 106/15 | BPSK | +| 24 | 95/15 | BPSK | +| 23 | 84/15 | BPSK | +| 22 | 75/15 | BPSK | +| 21 | 67/15 | BPSK | +| 20 | 60/15 | BPSK | +| 19 | 53/15 | BPSK, 4PAM | +| 18 | 47/15 | BPSK, 4PAM | +| 17 | 42/15 | BPSK, 4PAM | +| 16 | 38/15 | BPSK, 4PAM | +| 15 | 34/15 | BPSK, 4PAM | +| 14 | 30/15 | BPSK, 4PAM | +| 13 | 27/15 | BPSK, 4PAM | +| 12 | 24/15 | BPSK, 4PAM | +| 11 | 21/15 | BPSK, 4PAM | +| 10 | 19/15 | BPSK, 4PAM | +| 9 | 17/15 | BPSK | +| 8 | 15/15 | BPSK | +| 7 | 13/15 | BPSK | +| 6 | 12/15 | BPSK | +| 5 | 11/15 | BPSK | +| 4 | 9/15 | BPSK | +| 3 | 8/15 | BPSK | +| 2 | 7/15 | BPSK | +| 1 | 6/15 | BPSK | +| 0 | 5/15 | BPSK | + +**Table 1B.2: Quantization for $\beta_{ed,kl}\beta_c$ for $E-TFCI \leq E-TFCI_{ec,boost}$** + +| Quantized amplitude ratios
$\beta_{ed,kl}\beta_c$ | E-DPDCH modulation schemes
which may be used in the
same subframe | +|------------------------------------------------------|-------------------------------------------------------------------------| +| 168/15 | BPSK | +| 150/15 | BPSK | +| 134/15 | BPSK | +| 119/15 | BPSK | +| 106/15 | BPSK | +| 95/15 | BPSK | +| 84/15 | BPSK | +| 75/15 | BPSK | +| 67/15 | BPSK | +| 60/15 | BPSK | +| 53/15 | BPSK, 4PAM | +| 47/15 | BPSK, 4PAM | +| 42/15 | BPSK, 4PAM | +| 38/15 | BPSK, 4PAM | +| 34/15 | BPSK, 4PAM | +| 30/15 | BPSK, 4PAM | +| 27/15 | BPSK, 4PAM | +| 24/15 | BPSK, 4PAM | +| 21/15 | BPSK, 4PAM | +| 19/15 | BPSK, 4PAM | +| 17/15 | BPSK | +| 15/15 | BPSK | +| 13/15 | BPSK | +| 12/15 | BPSK | +| 11/15 | BPSK | +| 9/15 | BPSK | +| 8/15 | BPSK | +| 7/15 | BPSK | +| 6/15 | BPSK | +| 5/15 | BPSK | + +**Table 1B.2A: Quantization for $\Delta_{E-DPDCH}$ for $E-TFCI > E-TFCI_{ec,boost}$** + +| Signalled values for $\Delta_{E-DPDCH}$ | Quantized amplitude ratios $A_{ed} = \beta_{ed}/\beta_c$ | E-DPDCH modulation schemes which may be used in the same subframe | +|-----------------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------| +| 31 | 377/15 | 4PAM, 8PAM (applicable only for SF2 code in a 2xSF2+2xSF4 configuration) | +| 30 | 336/15 | 4PAM, 8PAM (applicable only for SF2 code in a 2xSF2+2xSF4 configuration) | +| 29 | 299/15 | 4PAM, 8PAM | +| 28 | 267/15 | BPSK (applicable only for SF2 code in a 2xSF2+2xSF4 configuration), 4PAM, 8PAM | +| 27 | 237/15 | BPSK (applicable only for SF2 code in a 2xSF2+2xSF4 configuration), 4PAM, 8PAM | +| 26 | 212/15 | BPSK, 4PAM, 8PAM | +| 25 | 189/15 | BPSK, 4PAM, 8PAM | +| 24 | 168/15 | BPSK, 4PAM, 8PAM | +| 23 | 150/15 | BPSK, 4PAM, 8PAM | +| 22 | 134/15 | BPSK, 4PAM, 8PAM | +| 21 | 119/15 | BPSK, 4PAM, 8PAM | +| 20 | 106/15 | BPSK, 4PAM, 8PAM | +| 19 | 95/15 | BPSK, 4PAM, 8PAM | +| 18 | 84/15 | BPSK, 4PAM, 8PAM | +| 17 | 75/15 | BPSK, 4PAM, 8PAM | +| 16 | 67/15 | BPSK, 4PAM, 8PAM | +| 15 | 60/15 | BPSK, 4PAM, 8PAM | +| 14 | 53/15 | BPSK, 4PAM, 8PAM | +| 13 | 47/15 | BPSK, 4PAM, 8PAM | +| 12 | 42/15 | BPSK, 4PAM, 8PAM | +| 11 | 38/15 | BPSK | +| 10 | 34/15 | BPSK | +| 9 | 30/15 | BPSK | +| 8 | 27/15 | BPSK | +| 7 | 24/15 | BPSK | +| 6 | 21/15 | BPSK | +| 5 | 19/15 | BPSK | +| 4 | 17/15 | BPSK | +| 3 | 15/15 | BPSK | +| 2 | 13/15 | BPSK | +| 1 | 11/15 | BPSK | +| 0 | 8/15 | BPSK | + +Table 1B.2B: Quantization for $\beta_{ed,k}/\beta_c$ for $E-TFCI > E-TFCI_{ec,boost}$ + +| Quantized amplitude ratios
$\beta_{ed,k}/\beta_c$ | E-DPDCH modulation schemes which
may be used in the same subframe | +|------------------------------------------------------|--------------------------------------------------------------------------------| +| 377/15 | 4PAM, 8PAM (applicable only for SF2 code in a 2xSF2+2xSF4 configuration) | +| 336/15 | 4PAM, 8PAM (applicable only for SF2 code in a 2xSF2+2xSF4 configuration) | +| 299/15 | 4PAM, 8PAM | +| 267/15 | BPSK (applicable only for SF2 code in a 2xSF2+2xSF4 configuration), 4PAM, 8PAM | +| 237/15 | BPSK (applicable only for SF2 code in a 2xSF2+2xSF4 configuration), 4PAM, 8PAM | +| 212/15 | BPSK, 4PAM, 8PAM | +| 189/15 | BPSK, 4PAM, 8PAM | +| 168/15 | BPSK, 4PAM, 8PAM | +| 150/15 | BPSK, 4PAM, 8PAM | +| 134/15 | BPSK, 4PAM, 8PAM | +| 119/15 | BPSK, 4PAM, 8PAM | +| 106/15 | BPSK, 4PAM, 8PAM | +| 95/15 | BPSK, 4PAM, 8PAM | +| 84/15 | BPSK, 4PAM, 8PAM | +| 75/15 | BPSK, 4PAM, 8PAM | +| 67/15 | BPSK, 4PAM, 8PAM | +| 60/15 | BPSK, 4PAM, 8PAM | +| 53/15 | BPSK, 4PAM, 8PAM | +| 47/15 | BPSK, 4PAM, 8PAM | +| 42/15 | BPSK, 4PAM, 8PAM | +| 38/15 | BPSK | +| 34/15 | BPSK | +| 30/15 | BPSK | +| 27/15 | BPSK | +| 24/15 | BPSK | +| 21/15 | BPSK | +| 19/15 | BPSK | +| 17/15 | BPSK | +| 15/15 | BPSK | +| 13/15 | BPSK | +| 11/15 | BPSK | +| 8/15 | BPSK | + +The HARQ offsets $\Delta_{harq}$ to be used for support of different HARQ profile are configured by higher layers as specified in Table 1B.3. + +Table 1B.3: HARQ offset $\Delta_{harq}$ + +| Signalled values for
$\Delta_{harq}$ | Power offset values
$\Delta_{harq}$ [dB] | +|-----------------------------------------|---------------------------------------------| +| 6 | 6 | +| 5 | 5 | +| 4 | 4 | +| 3 | 3 | +| 2 | 2 | +| 1 | 1 | +| 0 | 0 | + +After weighting, the real-valued spread signals shall be mapped to the I branch or the Q branch according to the $i_{q_{ec}}$ value for the E-DPCCH and to $i_{q_{ed,k}}$ for E-DPDCHk and summed together. + +The E-DPCCH shall always be mapped to the I branch, i.e. $i_{q,ec} = 1$ . + +The IQ branch mapping for the E-DPDCHs depends on $N_{max-dpdch}$ and on whether an HS-DSCH is configured for the UE; the IQ branch mapping shall be as specified in table 1C. + +**Table 1C: IQ branch mapping for E-DPDCH** + +| $N_{max-dpdch}$ | HS-DSCH configured | E-DPDCH $_k$ | $i_{q,ed,k}$ | +|-----------------|--------------------|--------------|--------------| +| 0 | No/Yes | E-DPDCH $_1$ | 1 | +| | | E-DPDCH $_2$ | j | +| | | E-DPDCH $_3$ | 1 | +| | | E-DPDCH $_4$ | j | +| 1 | No | E-DPDCH $_1$ | j | +| | | E-DPDCH $_2$ | 1 | +| 1 | Yes | E-DPDCH $_1$ | 1 | +| | | E-DPDCH $_2$ | j | + +NOTE: In case the UE transmits more than 2 E-DPDCHs, the UE then always transmits E-DPDCH $_3$ and E-DPDCH $_4$ simultaneously. + +#### 4.2.1.4 S-DPCCH + +Figure 1D illustrates the spreading operation for the uplink S-DPCCH. + +![Figure 1D: Spreading for uplink S-DPCCH. The diagram shows a signal flow from left to right. It starts with 'S-DPCCH' entering a multiplier (circle with X). Above the multiplier is 'c_sc' with a downward arrow. The output of the first multiplier enters a second multiplier. Above this multiplier is 'beta_sc' with a downward arrow. The output of the second multiplier is labeled 'Q'. This 'Q' signal enters a third multiplier. Below this multiplier is 'j' with an upward arrow. The final output is labeled 'S_s-dpch'.](7ede87328f6b696dcffa65ebc4570cc8_img.jpg) + +Figure 1D: Spreading for uplink S-DPCCH. The diagram shows a signal flow from left to right. It starts with 'S-DPCCH' entering a multiplier (circle with X). Above the multiplier is 'c\_sc' with a downward arrow. The output of the first multiplier enters a second multiplier. Above this multiplier is 'beta\_sc' with a downward arrow. The output of the second multiplier is labeled 'Q'. This 'Q' signal enters a third multiplier. Below this multiplier is 'j' with an upward arrow. The final output is labeled 'S\_s-dpch'. + +**Figure 1D: Spreading for uplink S-DPCCH** + +The S-DPCCH is spread to the chip rate by the channelisation code $c_{sc}$ . + +After channelisation, the real-valued spread signal is weighted by the gain factor $\beta_{sc}$ for S-DPCCH. + +##### 4.2.1.4.1 S-DPCCH gain factor setting while not transmitting rank-2 + +When no transmission on E-DCH is taking place, or when E-DCH transmission is taking place and $E-TFCI \leq E-TFCI_{ec,boost}$ the $\beta_{sc}$ shall be derived based on the quantized amplitude ratios $A_{sc}$ which is translated from $\Delta_{S-DPCCH}$ signalled by higher layers as described in [6] subclause 5.1.2.5D. The translation of $\Delta_{S-DPCCH}$ into quantized amplitude ratios $A_{sc} = \beta_{sc}/\beta_c$ is specified in Table 1C.1. + +**Table 1C.1: The quantization for $\Delta_{S-DPCCH}$ when no transmission on E-DCH is taking place, and when E-DCH transmission is taking place and $E-TFCI \leq E-TFCI_{ec,boost}$** + +| Signalled values for $\Delta_{S-DPCCH}$ | Quantized amplitude ratios $A_{sc}$ | +|-----------------------------------------|-------------------------------------| +| 6 | 1.0 | +| 5 | 12/15 | +| 4 | 11/15 | +| 3 | 10/15 | +| 2 | 9/15 | +| 1 | 8/15 | +| 0 | Switch off | + +When $E\text{-TFCI} > E\text{-TFCI}_{ec,boost}$ , in order to provide an enhanced phase reference, the value of $\beta_{sc}$ shall be derived as specified in [6] based on the traffic to secondary pilot power offset $\Delta_{T2SP}$ , configured by higher layers, and following the definition of $\Delta_{T2TP}$ as specified in Table 1B.0 and the quantization of the ratio $\beta_{sc}/\beta_c$ following the quantization of $\beta_{ec}/\beta_c$ as specified in Table 1B.0A. + +##### 4.2.1.4.2 S-DPCCH gain factor setting while transmitting rank-2 + +When a set of S-E-DPDCHs are present in a TTI, the S-DPCCH gain factor $\beta_{sc}$ is set equal to $\beta_{ec}$ for that TTI as defined in sub-clause 4.2.1.3. + +#### 4.2.1.5 S-E-DPCCH + +Figure 1E illustrates the spreading operation for the S-E-DPCCH. + +![Figure 1E: Spreading for S-E-DPCCH. The diagram shows a signal flow from left to right. It starts with 'S-E-DPCCH' entering a multiplier (circle with X). An arrow labeled 'c_sec' points down to this multiplier. The output of this multiplier enters another multiplier (circle with X). An arrow labeled 'beta_sec' points down to this second multiplier. The output of the second multiplier is labeled 'Q'. This 'Q' signal enters a third multiplier (circle with X). An arrow labeled 'j' points up to this third multiplier. The final output is labeled 'S_s-e-dpch'.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Figure 1E: Spreading for S-E-DPCCH. The diagram shows a signal flow from left to right. It starts with 'S-E-DPCCH' entering a multiplier (circle with X). An arrow labeled 'c\_sec' points down to this multiplier. The output of this multiplier enters another multiplier (circle with X). An arrow labeled 'beta\_sec' points down to this second multiplier. The output of the second multiplier is labeled 'Q'. This 'Q' signal enters a third multiplier (circle with X). An arrow labeled 'j' points up to this third multiplier. The final output is labeled 'S\_s-e-dpch'. + +Figure 1E: Spreading for S-E-DPCCH + +The S-E-DPCCH shall be spread to the chip rate by the channelisation code $c_{sec}$ . + +After channelisation, the real-valued spread S-E-DPCCH shall be weighted by gain factor $\beta_{sec}$ . + +The $\Delta_{S\text{-E-DPCCH}}$ value is signalled by higher layers and the gain factor $\beta_{sec}$ shall be derived based on the quantized amplitude ratios. The translation of $\Delta_{S\text{-E-DPCCH}}$ into quantized amplitude ratios $\beta_{sec}/\beta_c$ is specified in Table 1C.2. + +The S-E-DPCCH shall always be mapped to the Q branch. + +Table 1C.2: Quantization gain factors for S-E-DPCCH + +| Signaled values for $\Delta_{S\text{-E-DPCCH}}$ | Quantized amplitude ratios $\beta_{sec}/\beta_c$ | +|-------------------------------------------------|--------------------------------------------------| +| 17 | 239/15 | +| 16 | 190/15 | +| 15 | 151/15 | +| 14 | 120/15 | +| 13 | 95/15 | +| 12 | 76/15 | +| 11 | 60/15 | +| 10 | 48/15 | +| 9 | 38/15 | +| 8 | 30/15 | +| 7 | 24/15 | +| 6 | 19/15 | +| 5 | 15/15 | +| 4 | 12/15 | +| 3 | 9/15 | +| 2 | 8/15 | +| 1 | 6/15 | +| 0 | 5/15 | + +#### 4.2.1.6 S-E-DPDCH + +Figure 1F illustrates the spreading operation for the S-E-DPDCHs. + +![Figure 1F: Spreading for S-E-DPDCH. The diagram shows four parallel processing paths for S-E-DPDCH1 through S-E-DPDCH4. Each path consists of three sequential multiplication blocks (circles with 'X'). The first block takes the channel input and a channelisation code c_sed,k. The second block takes the output and a gain factor beta_sed,k. The third block takes the output and an IQ mapping factor iq_sed,k. The outputs of these four paths are then summed together in a large summation block (Sigma). The final output is labeled I+jQ and S_s-e-dpdch.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 1F: Spreading for S-E-DPDCH. The diagram shows four parallel processing paths for S-E-DPDCH1 through S-E-DPDCH4. Each path consists of three sequential multiplication blocks (circles with 'X'). The first block takes the channel input and a channelisation code c\_sed,k. The second block takes the output and a gain factor beta\_sed,k. The third block takes the output and an IQ mapping factor iq\_sed,k. The outputs of these four paths are then summed together in a large summation block (Sigma). The final output is labeled I+jQ and S\_s-e-dpdch. + +**Figure 1F: Spreading for S-E-DPDCH** + +The $k$ :th S-E-DPDCH, denominated S-E-DPDCH $_k$ , shall be spread to the chip rate using channelisation code $c_{sed,k}$ . + +After channelisation, the real-valued spread S-E-DPDCH $_k$ signals shall respectively be weighted by gain factor $\beta_{sed,k}$ . The value of $\beta_{sed,k}$ for S-E-DPDCH $_k$ shall follow that of the corresponding $\beta_{ed,k}$ for E-DPDCH $_k$ transmitted in the same TTI as defined in table 1C.3. + +**Table 1C.3: Gain factor setting for S-E-DPDCHs** + +| S-E-DPDCH $_k$ | Quantized amplitude ratios
$\beta_{sed,k}/\beta_c$ | +|----------------|-------------------------------------------------------| +| S-E-DPDCH $_1$ | $\beta_{sed,1}/\beta_c = \beta_{ed,1}/\beta_c$ | +| S-E-DPDCH $_2$ | $\beta_{sed,2}/\beta_c = \beta_{ed,2}/\beta_c$ | +| S-E-DPDCH $_3$ | $\beta_{sed,3}/\beta_c = \beta_{ed,3}/\beta_c$ | +| S-E-DPDCH $_4$ | $\beta_{sed,4}/\beta_c = \beta_{ed,4}/\beta_c$ | + +NOTE: Either no S-E-DPDCHs are transmitted, or all four S-E-DPDCHs are transmitted together and simultaneously with four E-DPDCHs. + +After weighting, the real-valued spread signals shall be mapped to the I branch or the Q branch according to the $iq_{sed,k}$ for S-E-DPDCH $_k$ and summed together. The IQ branch mapping for the S-E-DPDCHs shall be as specified in table 1C.4. + +**Table 1C.4: IQ branch mapping for S-E-DPDCHs** + +| S-E-DPDCH $_k$ | $iq_{sed,k}$ | +|----------------|--------------| +| S-E-DPDCH $_1$ | 1 | +| S-E-DPDCH $_2$ | j | +| S-E-DPDCH $_3$ | 1 | +| S-E-DPDCH $_4$ | j | + +#### 4.2.1.7 DPCCH2 + +Figure 1G illustrates the spreading operation for the uplink DPCCH2. + +![Figure 1G: Spreading for uplink DPCCH2. The diagram shows two parallel processing paths for DPCCH2. The top path is for the case where N_max-dpch = 0. It takes a DPCCH2 input, multiplies it by a channelisation code c_c2, then by a gain factor beta_c2 to produce an in-phase (I) signal. The bottom path is for the case where N_max-dpch > 0. It takes a DPCCH2 input, multiplies it by c_c2, then by beta_c2 to produce a quadrature (Q) signal. This Q signal is then multiplied by the imaginary unit j. Finally, the I signal and the j*Q signal are summed together to produce the final spread signal S_dpch2.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +Figure 1G: Spreading for uplink DPCCH2. The diagram shows two parallel processing paths for DPCCH2. The top path is for the case where N\_max-dpch = 0. It takes a DPCCH2 input, multiplies it by a channelisation code c\_c2, then by a gain factor beta\_c2 to produce an in-phase (I) signal. The bottom path is for the case where N\_max-dpch > 0. It takes a DPCCH2 input, multiplies it by c\_c2, then by beta\_c2 to produce a quadrature (Q) signal. This Q signal is then multiplied by the imaginary unit j. Finally, the I signal and the j\*Q signal are summed together to produce the final spread signal S\_dpch2. + +Figure 1G: Spreading for uplink DPCCH2 + +The DPCCH2 is spread to the chip rate by the channelisation code $c_{c2}$ . + +After channelisation, the real-valued spread signal is weighted by the gain factor $\beta_{c2}$ for DPCCH2. + +At every instant in time, the value of $\beta_{c2}$ is set to 1.0. + +### 4.2.2 PRACH + +#### 4.2.2.1 PRACH preamble part + +The PRACH preamble part consists of a complex-valued code, described in subclause 4.3.3. + +#### 4.2.2.2 PRACH message part + +Figure 2 illustrates the principle of the spreading and scrambling of the PRACH message part, consisting of data and control parts. The binary control and data parts to be spread are represented by real-valued sequences, i.e. the binary value "0" is mapped to the real value +1, while the binary value "1" is mapped to the real value -1. The control part is spread to the chip rate by the channelisation code $c_c$ , while the data part is spread to the chip rate by the channelisation code $c_d$ . + +![Figure 2: Spreading of PRACH message part. The diagram shows two parallel processing paths for the PRACH message part. The top path processes the 'PRACH message data part' by multiplying it with a channelisation code c_d and a gain factor beta_d to produce an in-phase (I) signal. The bottom path processes the 'PRACH message control part' by multiplying it with a channelisation code c_c, a gain factor beta_c, and the imaginary unit j to produce a quadrature (Q) signal. The I and Q signals are summed to form a complex signal I+jQ. This complex signal is then multiplied by a scrambling code S_r-msg,n to produce the final spread signal S.](0fa26005ab105a07af4fda20b2554987_img.jpg) + +Figure 2: Spreading of PRACH message part. The diagram shows two parallel processing paths for the PRACH message part. The top path processes the 'PRACH message data part' by multiplying it with a channelisation code c\_d and a gain factor beta\_d to produce an in-phase (I) signal. The bottom path processes the 'PRACH message control part' by multiplying it with a channelisation code c\_c, a gain factor beta\_c, and the imaginary unit j to produce a quadrature (Q) signal. The I and Q signals are summed to form a complex signal I+jQ. This complex signal is then multiplied by a scrambling code S\_r-msg,n to produce the final spread signal S. + +Figure 2: Spreading of PRACH message part + +After channelisation, the real-valued spread signals are weighted by gain factors, $\beta_c$ for the control part and $\beta_d$ for the data part. At every instant in time, at least one of the values $\beta_c$ and $\beta_d$ has the amplitude 1.0. The $\beta$ -values are quantized into 4 bit words. The quantization steps are given in subclause 4.2.1. + +After the weighting, the stream of real-valued chips on the I- and Q-branches are treated as a complex-valued stream of chips. This complex-valued signal is then scrambled by the complex-valued scrambling code $S_{r\text{-msg},n}$ . The 10 ms scrambling code is applied aligned with the 10 ms message part radio frames, i.e. the first scrambling chip corresponds to the beginning of a message part radio frame. + +### 4.2.3 Void + +### 4.2.4 Channel combining for UL CLTD and UL MIMO + +Figure 3, 3A, and 3B illustrate how different uplink channels are combined if UL\_CLTD\_Enabled is TRUE. + +- For the case that UL\_CLTD\_Active is 1, + - Each complex-valued spread channel, corresponding to point S in Figure 1, and point S' in Figure 1.1, shall be separately pre-coded by a precoding vector $\{w_1, w_2\}$ and $\{w_3, w_4\}$ as described in [6]. After precoding, the complex-valued signals T and T' are obtained; see Figure 3. +- For the case that UL\_CLTD\_Active is 2, + - Complex-valued spread channel, corresponding to point S in Figure 1, shall be mapped to T, as shown in Figure 3A. +- For the case that UL\_CLTD\_Active is 3, + - Complex-valued spread channel, corresponding to point S in Figure 1, shall be mapped to T', as shown in Figure 3B. + +![Figure 3: Combining of uplink physical channels when UL_CLTD_Enabled is TRUE and UL_CLTD_Active is 1. The diagram shows two input signals, '(Point S in Figure 1)' (blue) and '(Point S' in Figure 1.1)' (red), being processed through precoding vectors. The blue signal is multiplied by w1 and w2. The red signal is multiplied by w3 and w4. The outputs are then summed: the top sum (Σ) combines the w1 path and the w4 path to produce T; the bottom sum (Σ) combines the w2 path and the w3 path to produce T'.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +Figure 3: Combining of uplink physical channels when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 1. The diagram shows two input signals, '(Point S in Figure 1)' (blue) and '(Point S' in Figure 1.1)' (red), being processed through precoding vectors. The blue signal is multiplied by w1 and w2. The red signal is multiplied by w3 and w4. The outputs are then summed: the top sum (Σ) combines the w1 path and the w4 path to produce T; the bottom sum (Σ) combines the w2 path and the w3 path to produce T'. + +**Figure 3: Combining of uplink physical channels when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 1** + +![Figure 3A: Combining of uplink physical channels when UL_CLTD_Enabled is TRUE and UL_CLTD_Active is 2. The diagram shows two input signals, '(Point S in Figure 1)' and '(Point S' in Figure 1.1)', being mapped directly to outputs T and T' respectively, without precoding.](303fadfb9def251d1575d6221199b158_img.jpg) + +Figure 3A: Combining of uplink physical channels when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 2. The diagram shows two input signals, '(Point S in Figure 1)' and '(Point S' in Figure 1.1)', being mapped directly to outputs T and T' respectively, without precoding. + +**Figure 3A: Combining of uplink physical channels when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 2** + +![Diagram showing two boxes labeled '(Point S in Figure 1)' and '(Point S' in Figure 1.1)' with arrows pointing to 'T' and 'T'' respectively.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + + graph LR + A["(Point S in Figure 1)"] --> T + B["(Point S' in Figure 1.1)"] --> T' + +``` + +Diagram showing two boxes labeled '(Point S in Figure 1)' and '(Point S' in Figure 1.1)' with arrows pointing to 'T' and 'T'' respectively. + +**Figure 3B: Combining of uplink physical channels when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 3** + +## 4.3 Code generation and allocation + +### 4.3.1 Channelisation codes + +#### 4.3.1.1 Code definition + +The channelisation codes of figure 1 are Orthogonal Variable Spreading Factor (OVSF) codes that preserve the orthogonality between a user's different physical channels. The OVSF codes can be defined using the code tree of figure 4. + +![Code-tree diagram for generation of OVSF codes. The tree starts with C_ch,1,0 = (1) at SF=1, branches to C_ch,2,0 = (1,1) and C_ch,2,1 = (1,-1) at SF=2, and further branches to C_ch,4,0 = (1,1,1,1), C_ch,4,1 = (1,1,-1,-1), C_ch,4,2 = (1,-1,1,-1), and C_ch,4,3 = (1,-1,-1,1) at SF=4.](bb3354f497635d15bef873577125c48d_img.jpg) + +``` + + graph LR + SF1["SF = 1"] --- C10["Cch,1,0 = (1)"] + C10 --- C20["Cch,2,0 = (1,1)"] + C10 --- C21["Cch,2,1 = (1,-1)"] + C20 --- C40["Cch,4,0 = (1,1,1,1)"] + C20 --- C41["Cch,4,1 = (1,1,-1,-1)"] + C21 --- C42["Cch,4,2 = (1,-1,1,-1)"] + C21 --- C43["Cch,4,3 = (1,-1,-1,1)"] + SF2["SF = 2"] + SF4["SF = 4"] + +``` + +Code-tree diagram for generation of OVSF codes. The tree starts with C\_ch,1,0 = (1) at SF=1, branches to C\_ch,2,0 = (1,1) and C\_ch,2,1 = (1,-1) at SF=2, and further branches to C\_ch,4,0 = (1,1,1,1), C\_ch,4,1 = (1,1,-1,-1), C\_ch,4,2 = (1,-1,1,-1), and C\_ch,4,3 = (1,-1,-1,1) at SF=4. + +**Figure 4: Code-tree for generation of Orthogonal Variable Spreading Factor (OVSF) codes** + +In figure 4, the channelisation codes are uniquely described as $C_{ch,SF,k}$ , where SF is the spreading factor of the code and $k$ is the code number, $0 \leq k \leq SF-1$ . + +Each level in the code tree defines channelisation codes of length SF, corresponding to a spreading factor of SF in figure 4. + +The generation method for the channelisation code is defined as: + +$$C_{ch,1,0} = 1,$$ + +$$[C_{ch,2,0}]$$ + +$$\begin{bmatrix} C_{(n+1),0} \\ C_{(n+1),1} \\ C_{(n+1),2} \\ C_{(n+1),3} \\ \vdots \\ C_{(n+1)(n+1)-2} \\ C_{(n+1)(n+1)-1} \end{bmatrix} = \begin{bmatrix} C_{ch,2^n,0} & C_{ch,2^n,0} \\ C_{ch,2^n,0} & -C_{ch,2^n,0} \\ C_{ch,2^n,1} & C_{ch,2^n,1} \\ C_{ch,2^n,1} & -C_{ch,2^n,1} \\ \vdots & \vdots \\ C_{ch,2^n,2^n-1} & C_{ch,2^n,2^n-1} \\ C_{ch,2^n,2^n-1} & -C_{ch,2^n,2^n-1} \end{bmatrix}$$ + +The leftmost value in each channelisation code word corresponds to the chip transmitted first in time. + +#### 4.3.1.2 Code allocation for dedicated physical channels + +NOTE: Although subclause 4.3.1.2 has been reorganized in this release, the spreading operation for DPCCH and DPDCH remains unchanged as compared to the previous release. + +##### 4.3.1.2.1 Code allocation for DPCCH/ S-DPCCH/DPDCH/DPCCH2 + +For the DPCCH, S-DPCCH and DPDCHs the following applies: + +- The DPCCH shall always be spread by code $c_c = C_{ch,256,0}$ . +- The S-DPCCH shall always be spread by code $c_{sc} = C_{ch,256,31}$ . +- The DPCCH2 shall be spread with code $c_{c2}$ as specified in table 1C.5. +- When only one DPDCH is to be transmitted, DPDCH1 shall be spread by code $c_{d,1} = C_{ch,SF,k}$ where SF is the spreading factor of DPDCH1 and $k = SF / 4$ . +- When more than one DPDCH is to be transmitted, all DPDCHs have spreading factors equal to 4. DPDCHn shall be spread by the the code $c_{d,n} = C_{ch,4,k}$ , where $k = 1$ if $n \in \{1, 2\}$ , $k = 3$ if $n \in \{3, 4\}$ , and $k = 2$ if $n \in \{5, 6\}$ . + +**Table 1C.5: Channelisation code of DPCCH2** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{c2}$ | +|--------------------------------------------------|------------------------------| +| 0 | $C_{ch,256,34}$ | +| $\geq 1$ | $C_{ch,256,3}$ | + +If a power control preamble is used to initialise a DCH, the channelisation code for the DPCCH during the power control preamble shall be the same as that to be used afterwards. + +##### 4.3.1.2.2 Code allocation for HS-DPCCH when the UE is not configured in MIMO mode with four transmit antennas in any cell + +The HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D. If Secondary\_Cell\_Enabled is greater than 3 HS-DPCCH2 shall be spread with code $c_{hs}$ as specified in table 1D.1. + +If Secondary\_Cell\_Enabled as defined in [6] is 0 or 1 or if Secondary\_Cell\_Enabled is 2 and MIMO is not configured in any cell, HS-DPCCH slot format #0 as defined in [2] is used. + +If Secondary\_Cell\_Enabled is 2 and MIMO is configured in at least one cell or if Secondary\_Cell\_Enabled is 3, HS-DPCCH slot format #1 as defined in [2] is used. + +If Secondary\_Cell\_Enabled is greater than 3, HS-DPCCH slot format #1 as defined in [2] is used. + +**Table 1D: channelisation code of HS-DPCCH** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ | | | +|----------------------------------------------------------------------|----------------------------------------|--------------------------------|---------------------------------------------| +| | Secondary_Cell_Enabled is 0, 1, 2 or 3 | | Secondary_Cell_Enabled is
greater than 3 | +| | HS-DPCCH slot format #0
[2] | HS-DPCCH slot format #1
[2] | HS-DPCCH slot format #1
[2] | +| 0 | $C_{ch,256,33}$ | $C_{ch,128,16}$ | $C_{ch,128,16}$ | +| 1 | $C_{ch,256,64}$ | $C_{ch,128,32}$ | $C_{ch,128,16}$ | +| 2,4,6 | $C_{ch,256,1}$ | N/A | N/A | +| 3,5 | $C_{ch,256,32}$ | N/A | N/A | + +**Table 1D.1: channelisation code of HS-DPCCH2 if Secondary\_Cell\_Enabled is greater than 3.** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ | +|----------------------------------------------------------------------|---------------------------------------------| +| | Secondary_Cell_Enabled is
greater than 3 | +| | HS-DPCCH slot format #1 [2] | +| 0 | $C_{ch,128,16}$ | +| 1 | $C_{ch,128,16}$ | + +##### 4.3.1.2.2A Code allocation for HS-DPCCH when the UE is configured in MIMO mode with four transmit antennas in at least one cell + +If Secondary\_Cell\_Enabled as defined in [6] is 0 or 1, HS-DPCCH slot format #1 as defined in [2] is used. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.2. + +If Secondary\_Cell\_Enabled is 2: + +- If the UE is configured in MIMO mode with four transmit antennas in all cells, HS-DPCCH slot format #1 as defined in [2] is used for both HS-DPCCH and HS-DPCCH2. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.2 and HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.3. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is configured in MIMO mode with four transmit antennas either in the primary or in the 1st secondary serving cell or both, then HS-DPCCH slot format #1 as defined in [2] is used for HS-DPCCH. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.2. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is not configured in MIMO mode with four transmit antennas in the primary and the 1st secondary serving cell then HS-DPCCH slot format #0 as defined in [2] is used for HS-DPCCH. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.4. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is configured in MIMO mode with four transmit antennas in the 2nd secondary serving cell then HS-DPCCH slot format #1 as defined in [2] is used for HS-DPCCH2. HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.3. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is not configured in MIMO mode with four transmit antennas in the 2nd secondary serving cell then HS-DPCCH slot format #0 as defined in [2] is used for HS-DPCCH2. HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.5. + +If Secondary\_Cell\_Enabled is 3: + +- If the UE is configured in MIMO mode with four transmit antennas in more than 2 cells HS-DPCCH slot format #1 as defined in [2] is used for both HS-DPCCH and HS-DPCCH2. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.2 and HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.3. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is configured in MIMO mode with four transmit antennas either in the primary or in the 1st secondary serving cell or + +both, then HS-DPCCH slot format #1 as defined in [2] is used for HS-DPCCH. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.2. + +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is not configured in MIMO mode with four transmit antennas in the primary and the 1st secondary serving cell then HS-DPCCH slot format #0 as defined in [2] is used for HS-DPCCH. HS-DPCCH shall be spread with code $c_{hs}$ as specified in table 1D.4. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is configured in MIMO mode with four transmit antennas in the 2nd serving or in the 3rd serving secondary cell or both then HS-DPCCH slot format #1 as defined in [2] is used for HS-DPCCH2. HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.3. +- If the number of cells configured in MIMO mode with four transmit antennas is less than 3 and if the UE is not configured in MIMO mode with four transmit antennas in the 2nd and the 3rd secondary serving cell then HS-DPCCH slot format #0 as defined in [2] is used for HS-DPCCH2. HS-DPCCH2 spread with code $c_{hs}$ as specified in table 1D.5. + +**Table 1D.2: channelisation code of HS-DPCCH if Secondary\_Cell\_Enabled is 0 or 1 or 2 or 3 and the UE is configured in MIMO mode with four transmit antennas in any cell** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ ,
Secondary_Cell_Enabled is 0, 1 | Channelisation code $c_{hs}$ ,
Secondary_Cell_Enabled is 2, 3 | +|----------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------| +| | HS-DPCCH slot format #1 [2] | HS-DPCCH slot format #1 [2] | +| 0 | $C_{ch,128,16}$ | $C_{ch,128,16}$ | +| 1 | $C_{ch,128,32}$ | $C_{ch,128,16}$ | + +**Table 1D.3: channelisation code of HS-DPCCH2 if Secondary\_Cell\_Enabled is 2 or 3 and the UE is configured in MIMO mode with four transmit antennas in any cell** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ | Channelisation code $c_{hs}$ | +|----------------------------------------------------------------------|------------------------------|------------------------------| +| | HS-DPCCH slot format #0 [2] | HS-DPCCH slot format #1 [2] | +| 0 | $C_{ch,256,32}$ | $C_{ch,128,16}$ | +| 1 | $C_{ch,256,32}$ | $C_{ch,128,16}$ | + +**Table 1D.4: channelisation code of HS-DPCCH if Secondary\_Cell\_Enabled is greater than 1 and the UE is not configured in MIMO mode with four transmit antennas in the primary and the 1st secondary serving cell.** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ | +|----------------------------------------------------------------------|---------------------------------------------| +| | Secondary_Cell_Enabled is
greater than 1 | +| | HS-DPCCH slot format #0 [2] | +| 0 | $C_{ch,256,33}$ | +| 1 | $C_{ch,256,64}$ | + +**Table 1D.5: channelisation code of HS-DPCCH2 if Secondary\_Cell\_Enabled is equal to 3 and the UE is not configured in MIMO mode with four transmit antennas in the 2nd and the 3rd secondary serving cell or if Secondary\_Cell\_Enabled is equal to 2 and the UE is not configured in MIMO mode with four transmit antennas in the 2nd secondary serving cell.** + +| Nmax-dpdch
(as defined in
subclause 4.2.1) | Channelisation code $c_{hs}$ | +|----------------------------------------------------------------------|---------------------------------------------| +| | Secondary_Cell_Enabled is
greater than 1 | +| | HS-DPCCH slot format #0 [2] | +| 0 | $C_{ch,256,33}$ | +| 1 | $C_{ch,256,64}$ | + +##### 4.3.1.2.3 Code allocation for E-DPCCH/E-DPDCH + +The E-DPCCH shall be spread with channelisation code $c_{ec} = C_{ch,256,1}$ . + +E-DPDCHk shall be spread with channelisation code $c_{ed,k}$ . The sequence $c_{ed,k}$ depends on $N_{max-dpdch}$ and the spreading factor selected for the corresponding frame or sub-frame as specified in [7]; it shall be selected according to table 1E. + +**Table 1E: Channelisation code for E-DPDCH** + +| $N_{max-dpdch}$ | E-DPDCH k | Channelisation code $C_{ed,k}$ | +|-----------------|----------------------------------------------|-------------------------------------------------------------| +| 0 | E-DPDCH 1 | $C_{ch,SF,SF/4}$ if $SF \geq 4$
$C_{ch,2,1}$ if $SF = 2$ | +| | E-DPDCH 2 | $C_{ch,4,1}$ if $SF = 4$
$C_{ch,2,1}$ if $SF = 2$ | +| | E-DPDCH 3
E-DPDCH 4 | $C_{ch,4,1}$ | +| 1 | E-DPDCH 1 | $C_{ch,SF,SF/2}$ | +| | E-DPDCH 2 | $C_{ch,4,2}$ if $SF = 4$
$C_{ch,2,1}$ if $SF = 2$ | + +NOTE: When more than one E-DPDCH is transmitted, the respective channelisation codes used for E-DPDCH1 and E-DPDCH2 are always the same. + +##### 4.3.1.2.4 Code allocation for S-E-DPCCH/S-E-DPDCH + +The S-E-DPCCH shall be spread with channelisation code $c_{sec} = C_{ch,256,1}$ . + +S-E-DPDCHk shall be spread with channelisation code $c_{sed,k}$ . The sequence $c_{sed,k}$ shall be selected according to table 1F. + +**Table 1F: Channelisation code for S-E-DPDCH** + +| $N_{max-dpdch}$ | S-E-DPDCH k | Channelisation code $C_{sed,k}$ | +|-----------------|--------------------------------------------------|---------------------------------| +| 0 | S-E-DPDCH 1
S-E-DPDCH 2 | $C_{ch,2,1}$ | +| | S-E-DPDCH 3
S-E-DPDCH 4 | $C_{ch,4,1}$ | + +NOTE: Either none or all four S-E-DPDCHs are transmitted. + +#### 4.3.1.3 Code allocation for PRACH message part + +The preamble signature $s$ , $0 \leq s \leq 15$ , points to one of the 16 nodes in the code-tree that corresponds to channelisation codes of length 16. The sub-tree below the specified node is used for spreading of the message part. The control part is spread with the channelisation code $c_c$ (as shown in subclause 4.2.2.2) of spreading factor 256 in the lowest branch of the sub-tree, i.e. $c_c = C_{ch,256,m}$ where $m = 16 \times s + 15$ . The data part uses any of the channelisation codes from spreading factor 32 to 256 in the upper-most branch of the sub-tree. To be exact, the data part is spread by channelisation code $c_d = C_{ch,SF,m}$ and $SF$ is the spreading factor used for the data part and $m = SF \times s / 16$ . + +4.3.1.4 Void + +4.3.1.5 Void + +### 4.3.2 Scrambling codes + +4.3.2.1 General + +All uplink physical channels on an activated uplink frequency shall be scrambled with a complex-valued scrambling code. The dedicated physical channels may be scrambled by either a long or a short scrambling code, defined in subclause 4.3.2.4. The PRACH message part shall be scrambled with a long scrambling code, defined in subclause 4.3.2.5. There are $2^{24}$ long and $2^{24}$ short uplink scrambling codes. Uplink scrambling codes are assigned by higher layers. + +The long scrambling code is built from constituent long sequences defined in subclause 4.3.2.2, while the constituent short sequences used to build the short scrambling code are defined in subclause 4.3.2.3. + +4.3.2.2 Long scrambling sequence + +The long scrambling sequences $c_{\text{long},1,n}$ and $c_{\text{long},2,n}$ are constructed from position wise modulo 2 sum of 38400 chip segments of two binary $m$ -sequences generated by means of two generator polynomials of degree 25. Let $x$ , and $y$ be the two $m$ -sequences respectively. The $x$ sequence is constructed using the primitive (over GF(2)) polynomial $X^{25}+X^3+1$ . The $y$ sequence is constructed using the polynomial $X^{25}+X^3+X^2+X+1$ . The resulting sequences thus constitute segments of a set of Gold sequences. + +The sequence $c_{\text{long},2,n}$ is a 16777232 chip shifted version of the sequence $c_{\text{long},1,n}$ . + +Let $n_{23} \dots n_0$ be the 24 bit binary representation of the scrambling sequence number $n$ with $n_0$ being the least significant bit. The $x$ sequence depends on the chosen scrambling sequence number $n$ and is denoted $x_n$ , in the sequel. Furthermore, let $x_n(i)$ and $y(i)$ denote the $i$ :th symbol of the sequence $x_n$ and $y$ , respectively. + +The $m$ -sequences $x_n$ and $y$ are constructed as: + +Initial conditions: + +- $x_n(0)=n_0, x_n(1)=n_1, \dots, x_n(22)=n_{22}, x_n(23)=n_{23}, x_n(24)=1$ . +- $y(0)=y(1)=\dots=y(23)=y(24)=1$ . + +Recursive definition of subsequent symbols: + +- $x_n(i+25)=x_n(i+3)+x_n(i)$ modulo 2, $i=0, \dots, 2^{25}-27$ . +- $y(i+25)=y(i+3)+y(i+2)+y(i+1)+y(i)$ modulo 2, $i=0, \dots, 2^{25}-27$ . + +Define the binary Gold sequence $z_n$ by: + +- $z_n(i)=x_n(i)+y(i)$ modulo 2, $i=0, 1, 2, \dots, 2^{25}-2$ . + +The real valued Gold sequence $Z_n$ is defined by: + +$$Z_n(i) = \begin{cases} +1 & \text{if } z_n(i) = 0 \\ -1 & \text{if } z_n(i) = 1 \end{cases} \text{ for } i = 0, 1, \dots, 2^{25} - 2.$$ + +Now, the real-valued long scrambling sequences $c_{\text{long},1,n}$ and $c_{\text{long},2,n}$ are defined as follows: + +$$c_{\text{long},1,n}(i) = Z_n(i), \quad i = 0, 1, 2, \dots, 2^{25} - 2 \text{ and}$$ + +$$c_{\text{long},2,n}(i) = Z_n((i + 16777232) \bmod (2^{25} - 1)), \quad i = 0, 1, 2, \dots, 2^{25} - 2.$$ + +Finally, the complex-valued long scrambling sequence $C_{\text{long},n}$ , is defined as: + +$$C_{\text{long},n}(i) = c_{\text{long},1,n}(i) \left( 1 + j(-1)^i c_{\text{long},2,n}(2\lfloor i/2 \rfloor) \right)$$ + +where $i = 0, 1, \dots, 2^{25} - 2$ and $\lfloor \cdot \rfloor$ denotes rounding to nearest lower integer. + +![Figure 5: Configuration of uplink scrambling sequence generator. The diagram shows two parallel scrambling sequence generators. The top generator takes a 24-bit input sequence (labeled MSB at the left and LSB at the right) and produces an output sequence c_long,1,n. The bottom generator takes a 24-bit input sequence and produces an output sequence c_long,2,n. Both generators use a series of XOR gates and feedback loops to generate the scrambling sequences.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 5: Configuration of uplink scrambling sequence generator. The diagram shows two parallel scrambling sequence generators. The top generator takes a 24-bit input sequence (labeled MSB at the left and LSB at the right) and produces an output sequence c\_long,1,n. The bottom generator takes a 24-bit input sequence and produces an output sequence c\_long,2,n. Both generators use a series of XOR gates and feedback loops to generate the scrambling sequences. + +**Figure 5: Configuration of uplink scrambling sequence generator** + +#### 4.3.2.3 Short scrambling sequence + +The short scrambling sequences $c_{\text{short},1,n}(i)$ and $c_{\text{short},2,n}(i)$ are defined from a sequence from the family of periodically extended S(2) codes. + +Let $n_{23}n_{22}\dots n_0$ be the 24 bit binary representation of the code number $n$ . + +The $n$ :th quaternary S(2) sequence $z_n(i)$ , $0 \leq n \leq 16777215$ , is obtained by modulo 4 addition of three sequences, a quaternary sequence $a(i)$ and two binary sequences $b(i)$ and $d(i)$ , where the initial loading of the three sequences is determined from the code number $n$ . The sequence $z_n(i)$ of length 255 is generated according to the following relation: + +- $z_n(i) = a(i) + 2b(i) + 2d(i)$ modulo 4, $i = 0, 1, \dots, 254$ ; + +where the quaternary sequence $a(i)$ is generated recursively by the polynomial $g_0(x) = x^8 + 3x^5 + x^3 + 3x^2 + 2x + 3$ as: + +- $a(0) = 2n_0 + 1$ modulo 4; +- $a(i) = 2n_i$ modulo 4, $i = 1, 2, \dots, 7$ ; +- $a(i) = 3a(i-3) + a(i-5) + 3a(i-6) + 2a(i-7) + 3a(i-8)$ modulo 4, $i = 8, 9, \dots, 254$ ; + +and the binary sequence $b(i)$ is generated recursively by the polynomial $g_1(x) = x^8 + x^7 + x^5 + x + 1$ as + +$$b(i) = n_{8+i} \text{ modulo } 2, i = 0, 1, \dots, 7,$$ + +$$b(i) = b(i-1) + b(i-3) + b(i-7) + b(i-8) \text{ modulo } 2, i = 8, 9, \dots, 254,$$ + +and the binary sequence $d(i)$ is generated recursively by the polynomial $g_2(x) = x^8 + x^7 + x^5 + x^4 + 1$ as: + +$$d(i) = n_{16+i} \text{ modulo } 2, i = 0, 1, \dots, 7,$$ + +$$d(i) = d(i-1) + d(i-3) + d(i-4) + d(i-8) \text{ modulo } 2, i = 8, 9, \dots, 254.$$ + +The sequence $z_n(i)$ is extended to length 256 chips by setting $z_n(255) = z_n(0)$ . + +The mapping from $z_n(i)$ to the real-valued binary sequences $c_{\text{short},1,n}(i)$ and $c_{\text{short},2,n}(i)$ , $i = 0, 1, \dots, 255$ is defined in Table 2. + +**Table 2: Mapping from $z_n(i)$ to $c_{\text{short},1,n}(i)$ and $c_{\text{short},2,n}(i)$ , $i = 0, 1, \dots, 255$** + +| $z_n(i)$ | $c_{\text{short},1,n}(i)$ | $c_{\text{short},2,n}(i)$ | +|----------|---------------------------|---------------------------| +| 0 | +1 | +1 | +| 1 | -1 | +1 | +| 2 | -1 | -1 | +| 3 | +1 | -1 | + +Finally, the complex-valued short scrambling sequence $C_{\text{short},n}$ is defined as: + +$$c_{\text{short},n}(i) = c_{\text{short},1,n}(i \bmod 256) \left( 1 + j(-1)^i c_{\text{short},2,n}(2 \lfloor (i \bmod 256)/2 \rfloor) \right)$$ + +where $i = 0, 1, 2, \dots$ and $\lfloor \cdot \rfloor$ denotes rounding to nearest lower integer. + +An implementation of the short scrambling sequence generator for the 255 chip sequence to be extended by one chip is shown in Figure 6. + +![Figure 6: Uplink short scrambling sequence generator for 255 chip sequence. The diagram shows three parallel processing paths for sequences a(i), b(i), and d(i), each 8 chips long (indices 0-7). Path a(i) uses mod 4 addition and multiplication by 3. Path b(i) uses mod 2 addition. Path d(i) uses mod 2 addition. The outputs are combined via mod 4 addition and multiplication by 2 to produce z_n(i), which is then mapped to c_short,1,n(i) and c_short,2,n(i). A legend defines the symbols for mod n addition and multiplication.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +The diagram illustrates the uplink short scrambling sequence generator. It consists of three parallel processing paths for sequences $a(i)$ , $b(i)$ , and $d(i)$ , each 8 chips long (indices 0-7). + - Path $a(i)$ : The sequence is processed through a series of mod 4 additions and multiplications by 3. The output is then multiplied by 2 and added to the output of path $b(i)$ via mod 4 addition. + - Path $b(i)$ : The sequence is processed through a series of mod 2 additions. The output is then multiplied by 2 and added to the output of path $d(i)$ via mod 4 addition. + - Path $d(i)$ : The sequence is processed through a series of mod 2 additions. The output is then multiplied by 2 and added to the output of path $b(i)$ via mod 4 addition. + The final combined output $z_n(i)$ is then mapped to the short scrambling sequences $c_{\text{short},1,n}(i)$ and $c_{\text{short},2,n}(i)$ . + Legend: + - $\oplus$ mod n addition + - $\otimes$ multiplication + +Figure 6: Uplink short scrambling sequence generator for 255 chip sequence. The diagram shows three parallel processing paths for sequences a(i), b(i), and d(i), each 8 chips long (indices 0-7). Path a(i) uses mod 4 addition and multiplication by 3. Path b(i) uses mod 2 addition. Path d(i) uses mod 2 addition. The outputs are combined via mod 4 addition and multiplication by 2 to produce z\_n(i), which is then mapped to c\_short,1,n(i) and c\_short,2,n(i). A legend defines the symbols for mod n addition and multiplication. + +Figure 6: Uplink short scrambling sequence generator for 255 chip sequence + +#### 4.3.2.4 Dedicated physical channels scrambling code + +The code used for scrambling of the uplink dedicated physical channels may be of either long or short type. The $n$ :th uplink scrambling code, denoted $S_{\text{dpch},n}$ , is defined as: + +$$S_{\text{dpch},n}(i) = C_{\text{long},n}(i), \quad i = 0, 1, \dots, 38399, \text{ when using long scrambling codes;}$$ + +where the lowest index corresponds to the chip transmitted first in time and $C_{\text{long},n}$ is defined in subclause 4.3.2.2. + +The $n$ :th uplink scrambling code, denoted $S_{\text{dpch},n}$ , is defined as: + +$$S_{\text{dpch},n}(i) = C_{\text{short},n}(i), \quad i = 0, 1, \dots, 38399, \text{ when using short scrambling codes;}$$ + +where the lowest index corresponds to the chip transmitted first in time and $C_{\text{short},n}$ is defined in subclause 4.3.2.3. + +#### 4.3.2.5 PRACH message part scrambling code + +The scrambling code used for the PRACH message part is 10 ms long, and there are 8192 different PRACH scrambling codes defined. + +The $n$ :th PRACH message part scrambling code, denoted $S_{\text{r-msg},n}$ , where $n = 0, 1, \dots, 8191$ , is based on the long scrambling sequence and is defined as: + +$$S_{\text{r-msg},n}(i) = C_{\text{long},n}(i + 4096), \quad i = 0, 1, \dots, 38399$$ + +where the lowest index corresponds to the chip transmitted first in time and $C_{\text{long},n}$ is defined in subclause 4.3.2.2. + +The message part scrambling code has a one-to-one correspondence to the scrambling code used for the preamble part. For one PRACH, the same code number is used for both scrambling codes, i.e. if the PRACH preamble scrambling code used is $S_{r-pre,m}$ then the PRACH message part scrambling code is $S_{r-msg,m}$ , where the number $m$ is the same for both codes. + +4.3.2.6 Void + +4.3.2.7 Void + +### 4.3.3 PRACH preamble codes + +#### 4.3.3.1 Preamble code construction + +The random access preamble code $C_{pre,n}$ is a complex valued sequence. It is built from a preamble scrambling code $S_{r-pre,n}$ and a preamble signature $C_{sig,s}$ as follows: + +$$- C_{pre,n,s}(k) = S_{r-pre,n}(k) \times C_{sig,s}(k) \times e^{j(\frac{\pi}{4} + \frac{\pi}{2}k)}, k = 0, 1, 2, 3, \dots, 4095;$$ + +where $k=0$ corresponds to the chip transmitted first in time and $S_{r-pre,n}$ and $C_{sig,s}$ are defined in 4.3.3.2 and 4.3.3.3 below respectively. + +#### 4.3.3.2 Preamble scrambling code + +The scrambling code for the PRACH preamble part is constructed from the long scrambling sequences. There are 8192 PRACH preamble scrambling codes in total. + +The $n$ :th preamble scrambling code, $n = 0, 1, \dots, 8191$ , is defined as: + +$$S_{r-pre,n}(i) = c_{long,1,n}(i), i = 0, 1, \dots, 4095;$$ + +where the sequence $c_{long,1,n}$ is defined in subclause 4.3.2.2. + +The 8192 PRACH preamble scrambling codes are divided into 512 groups with 16 codes in each group. There is a one-to-one correspondence between the group of PRACH preamble scrambling codes in a cell and the primary scrambling code used in the downlink of the cell. The $k$ :th PRACH preamble scrambling code within the cell with downlink primary scrambling code $m$ , $k = 0, 1, 2, \dots, 15$ and $m = 0, 1, 2, \dots, 511$ , is $S_{r-pre,n}(i)$ as defined above with $n = 16 \times m + k$ . + +#### 4.3.3.3 Preamble signature + +The preamble signature corresponding to a signature $s$ consists of 256 repetitions of a length 16 signature $P_s(n)$ , $n=0\dots15$ . This is defined as follows: + +$$- C_{sig,s}(i) = P_s(i \bmod 16), i = 0, 1, \dots, 4095.$$ + +The signature $P_s(n)$ is from the set of 16 Hadamard codes of length 16. These are listed in table 3. + +Table 3: Preamble signatures + +| Preamble signature | Value of $n$ | | | | | | | | | | | | | | | | +|--------------------|--------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| $P_0(n)$ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| $P_1(n)$ | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | +| $P_2(n)$ | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | +| $P_3(n)$ | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | +| $P_4(n)$ | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | +| $P_5(n)$ | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | +| $P_6(n)$ | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | +| $P_7(n)$ | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | +| $P_8(n)$ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| $P_9(n)$ | 1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | +| $P_{10}(n)$ | 1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | +| $P_{11}(n)$ | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | +| $P_{12}(n)$ | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | +| $P_{13}(n)$ | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | +| $P_{14}(n)$ | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | +| $P_{15}(n)$ | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | + +### 4.3.4 Void + +## 4.4 Modulation + +### 4.4.1 Modulating chip rate + +The modulating chip rate is 3.84 Mcps. + +### 4.4.2 Modulation + +Modulation of the complex-valued chip sequence generated by the spreading process is shown below in Figure 7 for a UE with a single configured uplink frequency when UL\_CLTD\_Enabled is FALSE: + +![Block diagram of uplink modulation. A complex-valued chip sequence S is input to a 'Split real & imag. parts' block. The real part Re{S} is output to a 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by cos(ot). The imaginary part Im{S} is output to another 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by -sin(ot). The outputs of the two multipliers are summed (+) to produce the final modulated signal.](df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg) + +``` + +graph LR + S[Complex-valued chip sequence S] --> Split[Split real & imag. parts] + Split -- Re{S} --> PS1[Pulse-shaping] + PS1 --> M1((X)) + cos_ot[cos(ot)] --> M1 + Split -- Im{S} --> PS2[Pulse-shaping] + PS2 --> M2((X)) + -sin_ot[-sin(ot)] --> M2 + M1 --> Sum((+)) + M2 --> Sum + Sum --> Output[ ] + +``` + +Block diagram of uplink modulation. A complex-valued chip sequence S is input to a 'Split real & imag. parts' block. The real part Re{S} is output to a 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by cos(ot). The imaginary part Im{S} is output to another 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by -sin(ot). The outputs of the two multipliers are summed (+) to produce the final modulated signal. + +Figure 7: Uplink modulation when a single uplink frequency is configured and UL\_CLTD\_Enabled is FALSE + +An example of uplink modulation for a UE with adjacent primary and secondary uplink frequencies is given in Annex B. An example of uplink modulation for a UE with primary and secondary uplink frequencies in two different bands is given in Annex B2. The pulse-shaping characteristics are described in [3]. + +An example of uplink modulation for a UE when a single uplink frequency is configured and UL\_CLTD\_Enabled is TRUE is given in Annex B1. The pulse-shaping characteristics are described in [3]. + +# 5 Downlink spreading and modulation + +## 5.1 Spreading + +Figure 8 illustrates the spreading operation for all physical channel except SCH. The spreading operation includes a modulation mapper stage successively followed by a channelisation stage, an IQ combining stage and a scrambling stage. All the downlink physical channels are then combined as specified in sub subclause 5.1.5. + +The non-spread downlink physical channels, except SCH, AICH, E-HICH and E-RGCH consist of a sequence of 3-valued digits taking the values 0, 1 and "DTX". Note that "DTX" is only applicable to those downlink physical channels that support DTX transmission. + +![Figure 8: Spreading for all downlink physical channels except SCH. The diagram shows a block diagram of the spreading process. A 'downlink physical channel' input enters a block labeled 'S' over 'P'. The output of this block goes to a 'Modulation Mapper' block. The output of the Modulation Mapper is split into two branches. The upper branch is multiplied by 'I' and the lower branch is multiplied by 'Q'. The outputs of these multipliers are then multiplied by 'Cch,SF,m' and 'j' respectively. The outputs of these two branches are then summed together to form 'I+jQ'. This complex symbol is then multiplied by 'Sdl,n' to produce the final output 'S'.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +Figure 8: Spreading for all downlink physical channels except SCH. The diagram shows a block diagram of the spreading process. A 'downlink physical channel' input enters a block labeled 'S' over 'P'. The output of this block goes to a 'Modulation Mapper' block. The output of the Modulation Mapper is split into two branches. The upper branch is multiplied by 'I' and the lower branch is multiplied by 'Q'. The outputs of these multipliers are then multiplied by 'Cch,SF,m' and 'j' respectively. The outputs of these two branches are then summed together to form 'I+jQ'. This complex symbol is then multiplied by 'Sdl,n' to produce the final output 'S'. + +**Figure 8: Spreading for all downlink physical channels except SCH** + +NOTE: Although subclause 5.1 has been reorganized in this release, the spreading operation as specified for the DL channels in the previous release remains unchanged. + +### 5.1.1 Modulation mapper + +Table 3A defines which of the IQ mapping specified in subclauses 5.1.1.1 and 5.1.1.2 may be used for the physical channel being processed. + +**Table 3A: IQ mapping** + +| Physical channel | IQ mapping | +|-------------------------------------|----------------------| +| HS-PDSCH | QPSK, 16QAM or 64QAM | +| S-CCPCH used for MBSFN | QPSK or 16QAM | +| All other channels (except the SCH) | QPSK | + +#### 5.1.1.1 QPSK + +For all channels, except AICH, E-HICH and E-RGCH, the input digits shall be mapped to real-valued symbols as follows: the binary value "0" is mapped to the real value +1, the binary value "1" is mapped to the real value -1 and "DTX" is mapped to the real value 0. + +For the indicator channels using signatures (AICH), the real-valued input symbols depend on the exact combination of the indicators to be transmitted as specified in [2] subclauses 5.3.3.7, 5.3.3.8 and 5.3.3.9. For the E-HICH and the E-RGCH the input is a real valued symbol sequence as specified in [2] + +Each pair of two consecutive real-valued symbols is first converted from serial to parallel and mapped to an I and Q branch. The definition of the modulation mapper is such that even and odd numbered symbols are mapped to the I and Q branch respectively. For all QPSK channels except the indicator channels using signatures, symbol number zero is defined as the first symbol in each frame or sub-frame. For the indicator channels using signatures, symbol number zero is defined as the first symbol in each access slot. + +#### 5.1.1.2 16QAM + +In case of 16QAM, a set of four consecutive binary symbols $n_k, n_{k+1}, n_{k+2}, n_{k+3}$ (with $k \bmod 4 = 0$ ) is serial-to-parallel converted to two consecutive binary symbols ( $i_1 = n_k, i_2 = n_{k+2}$ ) on the I branch and two consecutive binary symbols ( $q_1 = n_{k+1}, q_2 = n_{k+3}$ ) on the Q branch and then mapped to 16QAM by the modulation mapper as defined in table 3B. + +The I and Q branches are then both spread to the chip rate by the same real-valued channelisation code $C_{ch,16,m}$ . The channelisation code sequence shall be aligned in time with the symbol boundary. The sequences of real-valued chips on the I and Q branch are then treated as a single complex-valued sequence of chips. This sequence of chips from all multi-codes is summed and then scrambled (complex chip-wise multiplication) by a complex-valued scrambling code $S_{dl,n}$ . The scrambling code is applied aligned with the scrambling code applied to the P-CCPCH. + +**Table 3B: 16QAM modulation mapping** + +| $i_1 q_1 i_2 q_2$ | I branch | Q branch | +|-------------------|----------|----------| +| 0000 | 0.4472 | 0.4472 | +| 0001 | 0.4472 | 1.3416 | +| 0010 | 1.3416 | 0.4472 | +| 0011 | 1.3416 | 1.3416 | +| 0100 | 0.4472 | -0.4472 | +| 0101 | 0.4472 | -1.3416 | +| 0110 | 1.3416 | -0.4472 | +| 0111 | 1.3416 | -1.3416 | +| 1000 | -0.4472 | 0.4472 | +| 1001 | -0.4472 | 1.3416 | +| 1010 | -1.3416 | 0.4472 | +| 1011 | -1.3416 | 1.3416 | +| 1100 | -0.4472 | -0.4472 | +| 1101 | -0.4472 | -1.3416 | +| 1110 | -1.3416 | -0.4472 | +| 1111 | -1.3416 | -1.3416 | + +In the case of 16-QAM on S-CCPCH, a sequence of four consecutive symbols $n_k, n_{k+1}, n_{k+2}, n_{k+3}$ (with $k \bmod 4 = 0$ ) at the input to the modulation mapper may contain values from the set 0, 1, and "DTX". In the event that all 4 bits of the quadruple are DTX bits, the output from the modulation mapping on both the I and Q branches is equal to the real value 0. + +For all other cases, all DTX bits in the quadruple are replaced with other non-DTX bits from the quadruple according to the following: + +The quadruple consists of two bit pairs, $\{n_k, n_{k+2}\}$ on the I branch, and $\{n_{k+1}, n_{k+3}\}$ on the Q branch. For any bit pair, if a non-DTX bit is available in the same pair, the DTX bit shall be replaced with the non-DTX bit value. If a non-DTX bit is not available in the same pair, the two DTX bits in that pair shall be replaced by the non-DTX bits in the other pair (using the same bit ordering when the other pair contains two non-DTX bits). + +The bit positions and values of non-DTX bits in the quadruple are not affected. + +#### 5.1.1.3 64QAM + +In case of 64QAM, a set of six consecutive binary symbols $n_k, n_{k+1}, n_{k+2}, n_{k+3}, n_{k+4}, n_{k+5}$ (with $k \bmod 6 = 0$ ) is serial-to-parallel converted to three consecutive binary symbols ( $i_1 = n_k, i_2 = n_{k+2}, i_3 = n_{k+4}$ ) on the I branch and three consecutive binary symbols ( $q_1 = n_{k+1}, q_2 = n_{k+3}, q_3 = n_{k+5}$ ) on the Q branch and then mapped to 64QAM by the modulation mapper as defined in table 3C. + +The I and Q branches are then both spread to the chip rate by the same real-valued channelisation code $C_{ch,16,m}$ . The channelisation code sequence shall be aligned in time with the symbol boundary. The sequences of real-valued chips on the I and Q branch are then treated as a single complex-valued sequence of chips. This sequence of chips from all multi-codes is summed and then scrambled (complex chip-wise multiplication) by a complex-valued scrambling code $S_{dl,n}$ . The scrambling code is applied aligned with the scrambling code applied to the P-CCPCH. + +**Table 3C: 64QAM modulation mapping** + +| $i_1 q_1 i_2 q_2 i_3 q_3$ | I branch | Q branch | $i_1 q_1 i_2 q_2 i_3 q_3$ | I branch | Q branch | +|---------------------------|----------|----------|---------------------------|----------|----------| +| 000000 | 0.6547 | 0.6547 | 100000 | -0.6547 | 0.6547 | +| 000001 | 0.6547 | 0.2182 | 100001 | -0.6547 | 0.2182 | +| 000010 | 0.2182 | 0.6547 | 100010 | -0.2182 | 0.6547 | +| 000011 | 0.2182 | 0.2182 | 100011 | -0.2182 | 0.2182 | +| 000100 | 0.6547 | 1.0911 | 100100 | -0.6547 | 1.0911 | +| 000101 | 0.6547 | 1.5275 | 100101 | -0.6547 | 1.5275 | +| 000110 | 0.2182 | 1.0911 | 100110 | -0.2182 | 1.0911 | +| 000111 | 0.2182 | 1.5275 | 100111 | -0.2182 | 1.5275 | +| 001000 | 1.0911 | 0.6547 | 101000 | -1.0911 | 0.6547 | +| 001001 | 1.0911 | 0.2182 | 101001 | -1.0911 | 0.2182 | +| 001010 | 1.5275 | 0.6547 | 101010 | -1.5275 | 0.6547 | +| 001011 | 1.5275 | 0.2182 | 101011 | -1.5275 | 0.2182 | +| 001100 | 1.0911 | 1.0911 | 101100 | -1.0911 | 1.0911 | +| 001101 | 1.0911 | 1.5275 | 101101 | -1.0911 | 1.5275 | +| 001110 | 1.5275 | 1.0911 | 101110 | -1.5275 | 1.0911 | +| 001111 | 1.5275 | 1.5275 | 101111 | -1.5275 | 1.5275 | +| 010000 | 0.6547 | -0.6547 | 110000 | -0.6547 | -0.6547 | +| 010001 | 0.6547 | -0.2182 | 110001 | -0.6547 | -0.2182 | +| 010010 | 0.2182 | -0.6547 | 110010 | -0.2182 | -0.6547 | +| 010011 | 0.2182 | -0.2182 | 110011 | -0.2182 | -0.2182 | +| 010100 | 0.6547 | -1.0911 | 110100 | -0.6547 | -1.0911 | +| 010101 | 0.6547 | -1.5275 | 110101 | -0.6547 | -1.5275 | +| 010110 | 0.2182 | -1.0911 | 110110 | -0.2182 | -1.0911 | +| 010111 | 0.2182 | -1.5275 | 110111 | -0.2182 | -1.5275 | +| 011000 | 1.0911 | -0.6547 | 111000 | -1.0911 | -0.6547 | +| 011001 | 1.0911 | -0.2182 | 111001 | -1.0911 | -0.2182 | +| 011010 | 1.5275 | -0.6547 | 111010 | -1.5275 | -0.6547 | +| 011011 | 1.5275 | -0.2182 | 111011 | -1.5275 | -0.2182 | +| 011100 | 1.0911 | -1.0911 | 111100 | -1.0911 | -1.0911 | +| 011101 | 1.0911 | -1.5275 | 111101 | -1.0911 | -1.5275 | +| 011110 | 1.5275 | -1.0911 | 111110 | -1.5275 | -1.0911 | +| 011111 | 1.5275 | -1.5275 | 111111 | -1.5275 | -1.5275 | + +### 5.1.2 Channelisation + +For all physical channels (except SCH) the I and Q branches shall be spread to the chip rate by the same real-valued channelisation code $C_{ch,SF,m}$ , i.e. the output for each input symbol on the I and the Q branches shall be a sequence of SF chips corresponding to the channelisation code chip sequence multiplied by the real-valued symbol. The channelisation code sequence shall be aligned in time with the symbol boundary. + +### 5.1.3 IQ combining + +The real valued chip sequence on the Q branch shall be complex multiplied with $j$ and summed with the corresponding real valued chip sequence on the I branch, thus resulting in a single complex valued chip sequence. + +### 5.1.4 Scrambling + +The sequence of complex valued chips shall be scrambled (complex chip-wise multiplication) by a complex-valued scrambling code $S_{dl,n}$ . In case of P-CCPCH, the scrambling code shall be applied aligned with the P-CCPCH frame boundary, i.e. the first complex chip of the spread P-CCPCH frame is multiplied with chip number zero of the scrambling code. In case of other downlink channels, the scrambling code shall be applied aligned with the scrambling code applied to the P-CCPCH. In this case, the scrambling code is thus not necessarily applied aligned with the frame boundary of the physical channel to be scrambled. + +### 5.1.5 Channel combining + +Figure 9 illustrates how different downlink channels are combined. Each complex-valued spread channel, corresponding to point S in Figure 8, may be separately weighted by a weight factor $G_i$ . The complex-valued P-SCH and S-SCH, as described in [2], subclause 5.3.3.5, may be separately weighted by weight factors $G_p$ and $G_s$ . All downlink physical channels shall then be combined using complex addition. + +![Figure 9: Combining of downlink physical channels. The diagram shows two stages of channel combining. In the first stage, multiple 'Different downlink Physical channels (point S in Figures 8)' are each multiplied by a spreading code (G1, G2, ...) and then summed (Σ). The output of this stage is then split into two paths: one for 'P-SCH' multiplied by Gp and another for 'S-SCH' multiplied by Gs. These two are then summed (Σ) again to produce the final output at 'point T in Figure 11'.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Figure 9: Combining of downlink physical channels. The diagram shows two stages of channel combining. In the first stage, multiple 'Different downlink Physical channels (point S in Figures 8)' are each multiplied by a spreading code (G1, G2, ...) and then summed (Σ). The output of this stage is then split into two paths: one for 'P-SCH' multiplied by Gp and another for 'S-SCH' multiplied by Gs. These two are then summed (Σ) again to produce the final output at 'point T in Figure 11'. + +**Figure 9: Combining of downlink physical channels** + +## 5.2 Code generation and allocation + +### 5.2.1 Channelisation codes + +The channelisation codes of figure 8 are the same codes as used in the uplink, namely Orthogonal Variable Spreading Factor (OVSF) codes that preserve the orthogonality between downlink channels of different rates and spreading factors. The OVSF codes are defined in figure 4 in subclause 4.3.1. + +The channelisation code for the Primary CPICH is fixed to $C_{ch,256,0}$ and the channelisation code for the Primary CCPCH is fixed to $C_{ch,256,1}$ . The channelisation codes for all other physical channels are assigned by UTRAN. + +With the spreading factor 512 a specific restriction is applied. When the code word $C_{ch,512,n}$ , with $n=0,2,4,\dots,510$ , is used in soft handover, then the code word $C_{ch,512,n+1}$ is not allocated in the cells where timing adjustment is to be used. Respectively if $C_{ch,512,n}$ , with $n=1,3,5,\dots,511$ is used, then the code word $C_{ch,512,n-1}$ is not allocated in the cells where timing adjustment is to be used. This restriction shall not apply in cases where timing adjustments in soft handover are not used with spreading factor 512. + +When compressed mode is implemented by reducing the spreading factor by 2, the OVSF code used for compressed frames is: + +- $C_{ch,SF/2,n/2}$ if ordinary scrambling code is used. +- $C_{ch,SF/2,n \bmod SF/2}$ if alternative scrambling code is used (see subclause 5.2.2); + +where $C_{ch,SF,n}$ is the channelisation code used for non-compressed frames. + +For F-DPCH, the spreading factor is always 256. + +For HS-PDSCH, the spreading factor is always 16. + +For HS-SCCH, the spreading factor is always 128. + +Channelisation-code-set information over HS-SCCH is mapped in following manner: the OVSF codes shall be allocated in such a way that they are positioned in sequence in the code tree. That is, for P multicodes at offset O the following codes are allocated: + +$$C_{ch,16,O} \dots C_{ch,16,O+P-1}$$ + +The number of multicodes and the corresponding offset for HS-PDSCHs mapped from a given HS-DSCH is signalled by HS-SCCH. + +For E-HICH and for E-RGCH, the spreading factor shall always be 128. In each cell, the E-RGCH and E-HICH assigned to a UE shall be configured with the same channelisation code. + +For E-AGCH, the spreading factor shall always be 256. + +For F-TPICH, the spreading factor shall always be 256. + +For E-ROCH, the spreading factor shall always be 256. + +### 5.2.2 Scrambling code + +A total of $2^{18}-1 = 262,143$ scrambling codes, numbered 0...262,142 can be generated. However not all the scrambling codes are used. The scrambling codes are divided into 512 sets each of a primary scrambling code and 15 secondary scrambling codes. + +The primary scrambling codes consist of scrambling codes $n=16*i$ where $i=0...511$ . The $i$ :th set of secondary scrambling codes consists of scrambling codes $16*i+k$ , where $k=1...15$ . + +There is a one-to-one mapping between each primary scrambling code and 15 secondary scrambling codes in a set such that $i$ :th primary scrambling code corresponds to $i$ :th set of secondary scrambling codes. + +Hence, according to the above, scrambling codes $k = 0, 1, \dots, 8191$ are used. Each of these codes are associated with a left alternative scrambling code and a right alternative scrambling code, that may be used for compressed frames. The left alternative scrambling code corresponding to scrambling code $k$ is scrambling code number $k + 8192$ , while the right alternative scrambling code corresponding to scrambling code $k$ is scrambling code number $k + 16384$ . The alternative scrambling codes can be used for compressed frames. In this case, the left alternative scrambling code is used if $n < SF/2$ and the right alternative scrambling code is used if $n \geq SF/2$ , where $c_{ch,SF,n}$ is the channelisation code used for non-compressed frames. The usage of alternative scrambling code for compressed frames is signalled by higher layers for each physical channel respectively. + +In case F-DPCH is configured in the downlink, the same scrambling code and OVSF code shall be used in F-DPCH compressed frames and normal frames. + +In the case that F-TPICH is configured in the downlink, the same scrambling code and OVSF code shall be used in F-TPICH compressed frames and normal frames. + +The set of primary scrambling codes is further divided into 64 scrambling code groups, each consisting of 8 primary scrambling codes. The $j$ :th scrambling code group consists of primary scrambling codes $16*8*j+16*k$ , where $j=0..63$ and $k=0..7$ . + +Each cell is allocated one and only one primary scrambling code. The primary CCPCH, primary CPICH, PICH, MICH, AICH and S-CCPCH carrying PCH or BCH shall always be transmitted using the primary scrambling code. The other downlink physical channels may be transmitted with either the primary scrambling code or a secondary scrambling code from the set associated with the primary scrambling code of the cell. + +In MBSFN operations, the S-CCPCH carries FACH only and shall always be transmitted using the primary scrambling code. The same primary CCPCH, primary CPICH, MICH and S-CCPCH may be transmitted from multiple cells using the same primary scrambling code when part of MBSFN operations. + +The mixture of primary scrambling code and no more than one secondary scrambling code for one CCTrCH is allowable. In compressed mode during compressed frames, these can be changed to the associated left or right scrambling codes as described above, i.e. in these frames, the total number of different scrambling codes may exceed two. + +In the case of CCTrCH of type of HS-DSCH then all the HS-PDSCH channelisation codes and HS-SCCH that a single UE may receive from a single cell shall be under a single scrambling code (either the primary or a secondary scrambling code). + +In each cell, the F-DPCH, E-RGCH, E-HICH, E-AGCH, E-ROCH and F-TPICH assigned to a UE shall be configured with same scrambling code as the assigned phase reference (primary or secondary CPICH). + +In each cell the UE may be configured simultaneously with at most two scrambling codes. + +The scrambling code sequences are constructed by combining two real sequences into a complex sequence. Each of the two real sequences are constructed as the position wise modulo 2 sum of 38400 chip segments of two binary $m$ -sequences generated by means of two generator polynomials of degree 18. The resulting sequences thus constitute segments of a set of Gold sequences. The scrambling codes are repeated for every 10 ms radio frame. Let $x$ and $y$ be the two sequences respectively. The $x$ sequence is constructed using the primitive (over GF(2)) polynomial $1+X^7+X^{18}$ . The $y$ sequence is constructed using the polynomial $1+X^5+X^7+X^{10}+X^{18}$ . + +The sequence depending on the chosen scrambling code number $n$ is denoted $z_n$ , in the sequel. Furthermore, let $x(i)$ , $y(i)$ and $z_n(i)$ denote the $i$ :th symbol of the sequence $x$ , $y$ , and $z_n$ , respectively. + +The $m$ -sequences $x$ and $y$ are constructed as: + +Initial conditions: + +- $x$ is constructed with $x(0)=1$ , $x(1)=x(2)=\dots=x(16)=x(17)=0$ . +- $y(0)=y(1)=\dots=y(16)=y(17)=1$ . + +Recursive definition of subsequent symbols: + +- $x(i+18)=x(i+7)+x(i)$ modulo 2, $i=0,\dots,2^{18}-20$ . +- $y(i+18)=y(i+10)+y(i+7)+y(i+5)+y(i)$ modulo 2, $i=0,\dots,2^{18}-20$ . + +The $n$ :th Gold code sequence $z_n$ , $n=0,1,2,\dots,2^{18}-2$ , is then defined as: + +- $z_n(i)=x((i+n)$ modulo $(2^{18}-1)) + y(i)$ modulo 2, $i=0,\dots,2^{18}-2$ . + +These binary sequences are converted to real valued sequences $Z_n$ by the following transformation: + +$$Z_n(i) = \begin{cases} +1 & \text{if } z_n(i) = 0 \\ -1 & \text{if } z_n(i) = 1 \end{cases} \text{ for } i = 0,1,\dots,2^{18}-2.$$ + +Finally, the $n$ :th complex scrambling code sequence $S_{dl,n}$ is defined as: + +- $S_{dl,n}(i)=Z_n(i) + j Z_n((i+131072)$ modulo $(2^{18}-1))$ , $i=0,1,\dots,38399$ . + +Note that the pattern from phase 0 up to the phase of 38399 is repeated. + +![Block diagram of a downlink scrambling code generator. It shows two parallel processing paths for generating the In-phase (I) and Quadrature (Q) components. Each path consists of a 18-bit shift register (labeled 17 down to 0), a series of taps and adders (circles with a cross) to implement the Gold code sequence generation, and a final adder to combine the real and imaginary parts. The top path generates the I component, and the bottom path generates the Q component.](b068dd12a75c78795832651369caecac_img.jpg) + +Block diagram of a downlink scrambling code generator. It shows two parallel processing paths for generating the In-phase (I) and Quadrature (Q) components. Each path consists of a 18-bit shift register (labeled 17 down to 0), a series of taps and adders (circles with a cross) to implement the Gold code sequence generation, and a final adder to combine the real and imaginary parts. The top path generates the I component, and the bottom path generates the Q component. + +Figure 10: Configuration of downlink scrambling code generator + +### 5.2.3 Synchronisation codes + +#### 5.2.3.1 Code generation + +The primary synchronisation code (PSC), $C_{psc}$ is constructed as a so-called generalised hierarchical Golay sequence. The PSC is furthermore chosen to have good aperiodic auto correlation properties. + +Define: + +- $a = \langle x_1, x_2, x_3, \dots, x_{16} \rangle = \langle 1, 1, 1, 1, 1, 1, -1, -1, 1, -1, 1, -1, 1, -1, -1, 1 \rangle$ + +The PSC is generated by repeating the sequence $a$ modulated by a Golay complementary sequence, and creating a complex-valued sequence with identical real and imaginary components. The PSC $C_{psc}$ is defined as: + +- $C_{psc} = (1 + j) \times \langle a, a, a, -a, -a, a, -a, -a, a, a, a, -a, a, -a, a, a \rangle;$ + +where the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +The 16 secondary synchronization codes (SSCs), $\{C_{ssc,1}, \dots, C_{ssc,16}\}$ , are complex-valued with identical real and imaginary components, and are constructed from position wise multiplication of a Hadamard sequence and a sequence $z$ , defined as: + +- $z = \langle b, b, b, -b, b, b, -b, -b, b, -b, b, -b, -b, -b, -b, -b \rangle$ , where +- $b = \langle x_1, x_2, x_3, x_4, x_5, x_6, x_7, x_8, -x_9, -x_{10}, -x_{11}, -x_{12}, -x_{13}, -x_{14}, -x_{15}, -x_{16} \rangle$ and $x_1, x_2, \dots, x_{15}, x_{16}$ , are same as in the definition of the sequence $a$ above. + +The Hadamard sequences are obtained as the rows in a matrix $H_8$ constructed recursively by: + +$$\begin{aligned} H_0 &= (1) \\ H_k &= \begin{pmatrix} H_{k-1} & H_{k-1} \\ H_{k-1} & -H_{k-1} \end{pmatrix}, k \geq 1 \end{aligned}$$ + +The rows are numbered from the top starting with row 0 (the all ones sequence). + +Denote the $n$ :th Hadamard sequence as a row of $H_8$ numbered from the top, $n = 0, 1, 2, \dots, 255$ , in the sequel. + +Furthermore, let $h_n(i)$ and $z(i)$ denote the $i$ :th symbol of the sequence $h_n$ and $z$ , respectively where $i = 0, 1, 2, \dots, 255$ and $i = 0$ corresponds to the leftmost symbol. + +The $k$ :th SSC, $C_{ssc,k}$ , $k = 1, 2, 3, \dots, 16$ is then defined as: + +- $C_{ssc,k} = (1 + j) \times \langle h_m(0) \times z(0), h_m(1) \times z(1), h_m(2) \times z(2), \dots, h_m(255) \times z(255) \rangle;$ + +where $m = 16 \times (k - 1)$ and the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +#### 5.2.3.2 Code allocation of SSC + +The 64 secondary SCH sequences are constructed such that their cyclic-shifts are unique, i.e., a non-zero cyclic shift less than 15 of any of the 64 sequences is not equivalent to some cyclic shift of any other of the 64 sequences. Also, a non-zero cyclic shift less than 15 of any of the sequences is not equivalent to itself with any other cyclic shift less than 15. Table 4 describes the sequences of SSCs used to encode the 64 different scrambling code groups. The entries in table 4 denote what SSC to use in the different slots for the different scrambling code groups, e.g. the entry "7" means that SSC $C_{ssc,7}$ shall be used for the corresponding scrambling code group and slot. + +**Table 4: Allocation of SSCs for secondary SCH** + +| Scrambling Code Group | slot number | | | | | | | | | | | | | | | +|-----------------------|-------------|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----| +| | #0 | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | #12 | #13 | #14 | +| Group 0 | 1 | 1 | 2 | 8 | 9 | 10 | 15 | 8 | 10 | 16 | 2 | 7 | 15 | 7 | 16 | +| Group 1 | 1 | 1 | 5 | 16 | 7 | 3 | 14 | 16 | 3 | 10 | 5 | 12 | 14 | 12 | 10 | +| Group 2 | 1 | 2 | 1 | 15 | 5 | 5 | 12 | 16 | 6 | 11 | 2 | 16 | 11 | 15 | 12 | +| Group 3 | 1 | 2 | 3 | 1 | 8 | 6 | 5 | 2 | 5 | 8 | 4 | 4 | 6 | 3 | 7 | +| Group 4 | 1 | 2 | 16 | 6 | 6 | 11 | 15 | 5 | 12 | 1 | 15 | 12 | 16 | 11 | 2 | +| Group 5 | 1 | 3 | 4 | 7 | 4 | 1 | 5 | 5 | 3 | 6 | 2 | 8 | 7 | 6 | 8 | +| Group 6 | 1 | 4 | 11 | 3 | 4 | 10 | 9 | 2 | 11 | 2 | 10 | 12 | 12 | 9 | 3 | +| Group 7 | 1 | 5 | 6 | 6 | 14 | 9 | 10 | 2 | 13 | 9 | 2 | 5 | 14 | 1 | 13 | +| Group 8 | 1 | 6 | 10 | 10 | 4 | 11 | 7 | 13 | 16 | 11 | 13 | 6 | 4 | 1 | 16 | +| Group 9 | 1 | 6 | 13 | 2 | 14 | 2 | 6 | 5 | 5 | 13 | 10 | 9 | 1 | 14 | 10 | +| Group 10 | 1 | 7 | 8 | 5 | 7 | 2 | 4 | 3 | 8 | 3 | 2 | 6 | 6 | 4 | 5 | +| Group 11 | 1 | 7 | 10 | 9 | 16 | 7 | 9 | 15 | 1 | 8 | 16 | 8 | 15 | 2 | 2 | +| Group 12 | 1 | 8 | 12 | 9 | 9 | 4 | 13 | 16 | 5 | 1 | 13 | 5 | 12 | 4 | 8 | +| Group 13 | 1 | 8 | 14 | 10 | 14 | 1 | 15 | 15 | 8 | 5 | 11 | 4 | 10 | 5 | 4 | +| Group 14 | 1 | 9 | 2 | 15 | 15 | 16 | 10 | 7 | 8 | 1 | 10 | 8 | 2 | 16 | 9 | +| Group 15 | 1 | 9 | 15 | 6 | 16 | 2 | 13 | 14 | 10 | 11 | 7 | 4 | 5 | 12 | 3 | +| Group 16 | 1 | 10 | 9 | 11 | 15 | 7 | 6 | 4 | 16 | 5 | 2 | 12 | 13 | 3 | 14 | +| Group 17 | 1 | 11 | 14 | 4 | 13 | 2 | 9 | 10 | 12 | 16 | 8 | 5 | 3 | 15 | 6 | +| Group 18 | 1 | 12 | 12 | 13 | 14 | 7 | 2 | 8 | 14 | 2 | 1 | 13 | 11 | 8 | 11 | +| Group 19 | 1 | 12 | 15 | 5 | 4 | 14 | 3 | 16 | 7 | 8 | 6 | 2 | 10 | 11 | 13 | +| Group 20 | 1 | 15 | 4 | 3 | 7 | 6 | 10 | 13 | 12 | 5 | 14 | 16 | 8 | 2 | 11 | +| Group 21 | 1 | 16 | 3 | 12 | 11 | 9 | 13 | 5 | 8 | 2 | 14 | 7 | 4 | 10 | 15 | +| Group 22 | 2 | 2 | 5 | 10 | 16 | 11 | 3 | 10 | 11 | 8 | 5 | 13 | 3 | 13 | 8 | +| Group 23 | 2 | 2 | 12 | 3 | 15 | 5 | 8 | 3 | 5 | 14 | 12 | 9 | 8 | 9 | 14 | +| Group 24 | 2 | 3 | 6 | 16 | 12 | 16 | 3 | 13 | 13 | 6 | 7 | 9 | 2 | 12 | 7 | +| Group 25 | 2 | 3 | 8 | 2 | 9 | 15 | 14 | 3 | 14 | 9 | 5 | 5 | 15 | 8 | 12 | +| Group 26 | 2 | 4 | 7 | 9 | 5 | 4 | 9 | 11 | 2 | 14 | 5 | 14 | 11 | 16 | 16 | +| Group 27 | 2 | 4 | 13 | 12 | 12 | 7 | 15 | 10 | 5 | 2 | 15 | 5 | 13 | 7 | 4 | +| Group 28 | 2 | 5 | 9 | 9 | 3 | 12 | 8 | 14 | 15 | 12 | 14 | 5 | 3 | 2 | 15 | +| Group 29 | 2 | 5 | 11 | 7 | 2 | 11 | 9 | 4 | 16 | 7 | 16 | 9 | 14 | 14 | 4 | +| Group 30 | 2 | 6 | 2 | 13 | 3 | 3 | 12 | 9 | 7 | 16 | 6 | 9 | 16 | 13 | 12 | +| Group 31 | 2 | 6 | 9 | 7 | 7 | 16 | 13 | 3 | 12 | 2 | 13 | 12 | 9 | 16 | 6 | +| Group 32 | 2 | 7 | 12 | 15 | 2 | 12 | 4 | 10 | 13 | 15 | 13 | 4 | 5 | 5 | 10 | +| Group 33 | 2 | 7 | 14 | 16 | 5 | 9 | 2 | 9 | 16 | 11 | 11 | 5 | 7 | 4 | 14 | +| Group 34 | 2 | 8 | 5 | 12 | 5 | 2 | 14 | 14 | 8 | 15 | 3 | 9 | 12 | 15 | 9 | +| Group 35 | 2 | 9 | 13 | 4 | 2 | 13 | 8 | 11 | 6 | 4 | 6 | 8 | 15 | 15 | 11 | +| Group 36 | 2 | 10 | 3 | 2 | 13 | 16 | 8 | 10 | 8 | 13 | 11 | 11 | 16 | 3 | 5 | +| Group 37 | 2 | 11 | 15 | 3 | 11 | 6 | 14 | 10 | 15 | 10 | 6 | 7 | 7 | 14 | 3 | +| Group 38 | 2 | 16 | 4 | 5 | 16 | 14 | 7 | 11 | 4 | 11 | 14 | 9 | 9 | 7 | 5 | +| Group 39 | 3 | 3 | 4 | 6 | 11 | 12 | 13 | 6 | 12 | 14 | 4 | 5 | 13 | 5 | 14 | +| Group 40 | 3 | 3 | 6 | 5 | 16 | 9 | 15 | 5 | 9 | 10 | 6 | 4 | 15 | 4 | 10 | +| Group 41 | 3 | 4 | 5 | 14 | 4 | 6 | 12 | 13 | 5 | 13 | 6 | 11 | 11 | 12 | 14 | +| Group 42 | 3 | 4 | 9 | 16 | 10 | 4 | 16 | 15 | 3 | 5 | 10 | 5 | 15 | 6 | 6 | +| Group 43 | 3 | 4 | 16 | 10 | 5 | 10 | 4 | 9 | 9 | 16 | 15 | 6 | 3 | 5 | 15 | +| Group 44 | 3 | 5 | 12 | 11 | 14 | 5 | 11 | 13 | 3 | 6 | 14 | 6 | 13 | 4 | 4 | +| Group 45 | 3 | 6 | 4 | 10 | 6 | 5 | 9 | 15 | 4 | 15 | 5 | 16 | 16 | 9 | 10 | +| Group 46 | 3 | 7 | 8 | 8 | 16 | 11 | 12 | 4 | 15 | 11 | 4 | 7 | 16 | 3 | 15 | +| Group 47 | 3 | 7 | 16 | 11 | 4 | 15 | 3 | 15 | 11 | 12 | 12 | 4 | 7 | 8 | 16 | +| Group 48 | 3 | 8 | 7 | 15 | 4 | 8 | 15 | 12 | 3 | 16 | 4 | 16 | 12 | 11 | 11 | +| Group 49 | 3 | 8 | 15 | 4 | 16 | 4 | 8 | 7 | 7 | 15 | 12 | 11 | 3 | 16 | 12 | +| Group 50 | 3 | 10 | 10 | 15 | 16 | 5 | 4 | 6 | 16 | 4 | 3 | 15 | 9 | 6 | 9 | + +| Scrambling Code Group | slot number | | | | | | | | | | | | | | | +|-----------------------|-------------|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----| +| | #0 | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | #12 | #13 | #14 | +| Group 51 | 3 | 13 | 11 | 5 | 4 | 12 | 4 | 11 | 6 | 6 | 5 | 3 | 14 | 13 | 12 | +| Group 52 | 3 | 14 | 7 | 9 | 14 | 10 | 13 | 8 | 7 | 8 | 10 | 4 | 4 | 13 | 9 | +| Group 53 | 5 | 5 | 8 | 14 | 16 | 13 | 6 | 14 | 13 | 7 | 8 | 15 | 6 | 15 | 7 | +| Group 54 | 5 | 6 | 11 | 7 | 10 | 8 | 5 | 8 | 7 | 12 | 12 | 10 | 6 | 9 | 11 | +| Group 55 | 5 | 6 | 13 | 8 | 13 | 5 | 7 | 7 | 6 | 16 | 14 | 15 | 8 | 16 | 15 | +| Group 56 | 5 | 7 | 9 | 10 | 7 | 11 | 6 | 12 | 9 | 12 | 11 | 8 | 8 | 6 | 10 | +| Group 57 | 5 | 9 | 6 | 8 | 10 | 9 | 8 | 12 | 5 | 11 | 10 | 11 | 12 | 7 | 7 | +| Group 58 | 5 | 10 | 10 | 12 | 8 | 11 | 9 | 7 | 8 | 9 | 5 | 12 | 6 | 7 | 6 | +| Group 59 | 5 | 10 | 12 | 6 | 5 | 12 | 8 | 9 | 7 | 6 | 7 | 8 | 11 | 11 | 9 | +| Group 60 | 5 | 13 | 15 | 15 | 14 | 8 | 6 | 7 | 16 | 8 | 7 | 13 | 14 | 5 | 16 | +| Group 61 | 9 | 10 | 13 | 10 | 11 | 15 | 15 | 9 | 16 | 12 | 14 | 13 | 16 | 14 | 11 | +| Group 62 | 9 | 11 | 12 | 15 | 12 | 9 | 13 | 13 | 11 | 14 | 10 | 16 | 15 | 14 | 16 | +| Group 63 | 9 | 12 | 10 | 15 | 13 | 14 | 9 | 14 | 15 | 11 | 11 | 13 | 12 | 16 | 10 | + +## 5.3 Modulation + +### 5.3.1 Modulating chip rate + +The modulating chip rate is 3.84 Mcps. + +### 5.3.2 Modulation + +Modulation of the complex-valued chip sequence generated by the spreading process is shown in Figure 11 below. + +![Block diagram of downlink modulation. A complex-valued chip sequence T is input to a 'Split real & imag. parts' block. The real part Re{T} is output to a 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by cos(ot). The imaginary part Im{T} is output to another 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by -sin(ot). The outputs of the two multipliers are summed (+) to produce the final modulated signal.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +``` + +graph LR + T[Complex-valued chip sequence T] --> Split[Split real & imag. parts] + Split -- Re{T} --> PS1[Pulse-shaping] + PS1 --> M1((X)) + cos_ot[cos(ot)] --> M1 + Split -- Im{T} --> PS2[Pulse-shaping] + PS2 --> M2((X)) + -sin_ot[-sin(ot)] --> M2 + M1 --> Sum((+)) + M2 --> Sum + Sum --> Output[ ] + +``` + +Block diagram of downlink modulation. A complex-valued chip sequence T is input to a 'Split real & imag. parts' block. The real part Re{T} is output to a 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by cos(ot). The imaginary part Im{T} is output to another 'Pulse-shaping' block, which then outputs to a multiplier (X) where it is multiplied by -sin(ot). The outputs of the two multipliers are summed (+) to produce the final modulated signal. + +Figure 11: Downlink modulation + +The pulse-shaping characteristics are described in [4]. + +# Annex A (informative): Generalised Hierarchical Golay Sequences + +## A.1 Alternative generation + +The generalised hierarchical Golay sequences for the PSC described in 5.2.3.1 may be also viewed as generated (in real valued representation) by the following methods: + +### Method 1. + +The sequence $y$ is constructed from two constituent sequences $x_1$ and $x_2$ of length $n_1$ and $n_2$ respectively using the following formula: + +$$- y(i) = x_2(i \bmod n_2) * x_1(i \bmod n_1), i = 0 \dots (n_1 * n_2) - 1.$$ + +The constituent sequences $x_1$ and $x_2$ are chosen to be the following length 16 (i.e. $n_1 = n_2 = 16$ ) sequences: + +- $x_1$ is defined to be the length 16 ( $N^{(1)}=4$ ) Golay complementary sequence obtained by the delay matrix $D^{(1)} = [8, 4, 1, 2]$ and weight matrix $W^{(1)} = [1, -1, 1, 1]$ . +- $x_2$ is a generalised hierarchical sequence using the following formula, selecting $s=2$ and using the two Golay complementary sequences $x_3$ and $x_4$ as constituent sequences. The length of the sequence $x_3$ and $x_4$ is called $n_3$ respectively $n_4$ . +- $x_2(i) = x_4(i \bmod s + s * (i \bmod n_3)) * x_3((i \bmod s) \bmod n_3), i = 0 \dots (n_3 * n_4) - 1.$ +- $x_3$ and $x_4$ are defined to be identical and the length 4 ( $N^{(3)}=N^{(4)}=2$ ) Golay complementary sequence obtained by the delay matrix $D^{(3)} = D^{(4)} = [1, 2]$ and weight matrix $W^{(3)} = W^{(4)} = [1, 1]$ . + +The Golay complementary sequences $x_1, x_3$ and $x_4$ are defined using the following recursive relation: + +$$a_0(k) = \delta(k) \text{ and } b_0(k) = \delta(k);$$ + +$$a_n(k) = a_{n-1}(k) + W_n^{(j)} \cdot b_{n-1}(k - D_n^{(j)});$$ + +$$b_n(k) = a_{n-1}(k) - W_n^{(j)} \cdot b_{n-1}(k - D_n^{(j)});$$ + +$$k = 0, 1, 2, \dots, 2^{N^{(j)}} - 1;$$ + +$$n = 1, 2, \dots, N^{(j)}.$$ + +The wanted Golay complementary sequence $x_j$ is defined by $a_n$ assuming $n=N^{(j)}$ . The Kronecker delta function is described by $\delta$ , $k, j$ and $n$ are integers. + +### Method 2 + +The sequence $y$ can be viewed as a pruned Golay complementary sequence and generated using the following parameters which apply to the generator equations for $a$ and $b$ above: + +- (a) Let $j = 0, N^{(0)} = 8$ . +- (b) $[D_1^0, D_2^0, D_3^0, D_4^0, D_5^0, D_6^0, D_7^0, D_8^0] = [128, 64, 16, 32, 8, 1, 4, 2]$ . +- (c) $[W_1^0, W_2^0, W_3^0, W_4^0, W_5^0, W_6^0, W_7^0, W_8^0] = [1, -1, 1, 1, 1, 1, 1, 1]$ . +- (d) For $n = 4, 6$ , set $b_4(k) = a_4(k), b_6(k) = a_6(k)$ . + +# Annex B (informative): Uplink modulation for operation on adjacent frequencies + +An example of modulation of the complex-valued chip sequence generated by the spreading process is shown below in Figure B-1. In Figure B-1, $\omega_L$ and $\omega_H$ are the lower and higher assigned channel frequencies. + +![Block diagram of uplink modulation for adjacent frequencies.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +The diagram illustrates the uplink modulation process for a UE with adjacent primary and secondary uplink frequencies. It consists of two parallel processing paths that are combined at the end. + +**Path 1 (Top):** A complex-valued chip sequence from spreading operations on carrier 1 ( $\omega_L$ ) is input to a "Pulse-shaping" block. The output of this block is multiplied (X) by a complex exponential $e^{-j((\omega_H-\omega_L)/2)t}$ . The result is then added (+) to the output of Path 2. + +**Path 2 (Bottom):** A complex-valued chip sequence from spreading operations on carrier 2 ( $\omega_H$ ) is input to a "Pulse-shaping" block. The output of this block is multiplied (X) by a complex exponential $e^{+j((\omega_H-\omega_L)/2)t}$ . The result is then added (+) to the output of Path 1. + +The combined signal from the addition (+) is then processed by a "Split real & imag parts" block, which separates the real part ( $Re\{S\}$ ) and the imaginary part ( $Im\{S\}$ ). + +**Final Modulation:** + +- The real part $Re\{S\}$ is multiplied (X) by $\cos((\omega_L+\omega_H)/2)t$ . +- The imaginary part $Im\{S\}$ is multiplied (X) by $-\sin((\omega_L+\omega_H)/2)t$ . +- The outputs of these two multiplications are then added (+) to produce the final modulated signal. + +Block diagram of uplink modulation for adjacent frequencies. + +Figure B-1: Uplink modulation for a UE with adjacent primary and secondary uplink frequencies + +# Annex B1 (informative): Uplink modulation for UL CLTD + +In the case that UL\_CLTD\_Enabled is TRUE, modulation of the complex-valued chip sequence T and T', obtained from channel combining operation for UL CLTD in section 4.2.4, is shown in Figure B1-1. + +![Block diagram of uplink modulation for UL CLTD showing two parallel paths for chip sequences T and T'.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +The diagram illustrates the uplink modulation process for two chip sequences, T and T', when UL\_CLTD\_Enabled is TRUE. Both sequences are processed through identical parallel paths. + +**Path for chip sequence T:** + +- The input "Complex-valued chip sequence from channel combining operations" (T) is fed into a block labeled "Split real & imag. parts". +- This block outputs the real part, $Re\{T\}$ , and the imaginary part, $Im\{T\}$ . +- Both $Re\{T\}$ and $Im\{T\}$ are fed into separate "Pulse-shaping" blocks. +- The outputs of these blocks are then multiplied by $\cos(\omega t)$ and $-\sin(\omega t)$ respectively. +- The results of these multiplications are summed at a block labeled "Antenna 1" (indicated by a circle with a plus sign). + +**Path for chip sequence T':** + +- The input "Complex-valued chip sequence from channel combining operations" (T') is fed into a block labeled "Split real & imag. parts". +- This block outputs the real part, $Re\{T'\}$ , and the imaginary part, $Im\{T'\}$ . +- Both $Re\{T'\}$ and $Im\{T'\}$ are fed into separate "Pulse-shaping" blocks. +- The outputs of these blocks are then multiplied by $\cos(\omega t)$ and $-\sin(\omega t)$ respectively. +- The results of these multiplications are summed at a block labeled "Antenna 2" (indicated by a circle with a plus sign). + +Block diagram of uplink modulation for UL CLTD showing two parallel paths for chip sequences T and T'. + +Figure B1-1: Uplink modulation when UL\_CLTD\_Enabled is TRUE + +# Annex B2 (informative): Uplink modulation for operation on dual band frequencies + +An example of modulation of the complex-valued chip sequence generated by the spreading process is shown below in Figure B2-1 for two uplink frequencies in two distinct bands. In Figure B2-1, $\omega_{B1}$ and $\omega_{B2}$ are the assigned primary and secondary uplink channel frequencies in two distinct bands. + +![Figure B2-1: Uplink modulation for a UE with primary and secondary uplink frequencies on two different bands. The diagram shows two parallel processing paths for carriers in the First Band (omega_B1) and Second Band (omega_B2). Each path consists of a complex-valued chip sequence input, a pulse-shaping block, a split real and imaginary parts block, two multipliers (one for the real part with cos(omega_Bi t) and one for the imaginary part with -sin(omega_Bi t)), and an adder to produce the final modulated signal.](1ce027dfd26183da52137cf990213724_img.jpg) + +The diagram illustrates the uplink modulation process for two distinct bands. The top path is for the First Band ( $\omega_{B1}$ ) and the bottom path is for the Second Band ( $\omega_{B2}$ ). + +**Top Path (First Band $\omega_{B1}$ ):** + +- Input: Complex-valued chip sequence from spreading operations on carrier 1 in First Band ( $\omega_{B1}$ ) +- Block: Pulse-shaping +- Block: Split real & imag parts +- Output: $Re\{S\}$ (Real part) +- Multiplier: $\cos(\omega_{B1}t)$ +- Output: $Im\{S\}$ (Imaginary part) +- Multiplier: $-\sin(\omega_{B1}t)$ +- Adder: $+$ +- Output: Modulated signal + +**Bottom Path (Second Band $\omega_{B2}$ ):** + +- Input: Complex-valued chip sequence from spreading operations on carrier 2 in Second Band ( $\omega_{B2}$ ) +- Block: Pulse-shaping +- Block: Split real & imag parts +- Output: $Re\{S\}$ (Real part) +- Multiplier: $\cos(\omega_{B2}t)$ +- Output: $Im\{S\}$ (Imaginary part) +- Multiplier: $-\sin(\omega_{B2}t)$ +- Adder: $+$ +- Output: Modulated signal + +Figure B2-1: Uplink modulation for a UE with primary and secondary uplink frequencies on two different bands. The diagram shows two parallel processing paths for carriers in the First Band (omega\_B1) and Second Band (omega\_B2). Each path consists of a complex-valued chip sequence input, a pulse-shaping block, a split real and imaginary parts block, two multipliers (one for the real part with cos(omega\_Bi t) and one for the imaginary part with -sin(omega\_Bi t)), and an adder to produce the final modulated signal. + +**Figure B2-1: Uplink modulation for a UE with primary and secondary uplink frequencies on two different bands** + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|-----------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99589 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99682 | 005 | 1 | Harmonization of notations for downlink scrambling codes | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 006 | - | Update of downlink spreading description | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99682 | 007 | 1 | Update of TS 25.213 uplink parts | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 008 | - | Updated modulation description | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 009 | - | Restriction for spreading factor 512 allocation in the UTRA FDD Downlink | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 011 | 1 | CPCH codes in power control preamble | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 012 | 2 | Support of short codes for CPCH | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99682 | 014 | 1 | Editorial Change | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 016 | - | Channelization Code Allocation for USTS | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 017 | 1 | Correction (Editorial Change) | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99683 | 019 | - | Correction to code allocation for compressed mode | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000063 | 020 | 1 | Consistent numbering of scrambling code groups | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 021 | - | Downlink signal flow corrections | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 022 | - | Uplink signal flow corrections | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 023 | 1 | Number of RACH scrambling codes | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 024 | 1 | Editorial changes to 25.213 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 025 | 3 | Number of PCPCH scrambling codes per cell | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 027 | - | A typo correction for 5.2.2 and clarification for 5.2.3.1 of TS 25.213V3.1.1 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 028 | 2 | Channelization code allocation method for PCPCH message part | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 029 | - | Clarifications to DSCH scrambling and modulation in 25.213 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000063 | 032 | - | Clean up of USTS related specifications | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000267 | 033 | - | Clarifications to power control preamble sections | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000267 | 034 | 2 | Numbering of the PCPCH access preamble and collision detection preamble scrambling codes | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000267 | 035 | - | DPDCH/DPCCCH gain factors | 3.2.0 | 3.3.0 | +| 16/12/00 | RAN_10 | RP-000539 | 037 | 1 | Proposed removal of the option of secondary scrambling code for some downlink common channels | 3.3.0 | 3.4.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.4.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010059 | 038 | - | Clarification of channelization codes when SF=512 | 3.4.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010059 | 039 | 1 | Clarification of the scrambling code of a power control preamble | 3.4.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010333 | 041 | 1 | Clarification of DL channelization code alignment | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010333 | 043 | 1 | Clarification of PDSCH root channelisation code definition | 4.0.0 | 4.1.0 | +| 14/12/01 | RAN_14 | RP-010738 | 047 | - | Correction of section number reference | 4.1.0 | 4.2.0 | +| 08/03/02 | RAN_15 | RP-020058 | 049 | - | The inclusion of HSDPA into 25.213 | 4.2.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020309 | 053 | 1 | Downlink bit mapping | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020316 | 050 | - | Consistency of Signal Point Constellation for QPSK and 16QAM | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020316 | 054 | - | Clarification of uplink DTX handling and modulation | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020316 | 055 | - | Removal of code mapping description over HS-SCCH | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020316 | 056 | 3 | I/Q mapping of HS-DPCCH | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020316 | 057 | - | Definition of the amplitude gain factor for HS-DPCCH | 5.0.0 | 5.1.0 | +| 16/09/02 | RAN_17 | RP-020583 | 058 | 1 | Numbering corrections | 5.1.0 | 5.2.0 | +| 16/09/02 | RAN_17 | RP-020583 | 059 | - | Correction on the maximum DPDCH in Figure 1 | 5.1.0 | 5.2.0 | +| 16/09/02 | RAN_17 | RP-020592 | 060 | - | Power offset values for HS-DPCCH | 5.1.0 | 5.2.0 | +| 26/03/03 | RAN_19 | RP-030135 | 061 | 1 | Removal of the tiny text in Figure 1 and minor corrections to 4.2.1 | 5.2.0 | 5.3.0 | +| 21/09/03 | RAN_21 | RP-030457 | 062 | - | Clarification of 16QAM modulation description | 5.3.0 | 5.4.0 | +| 06/01/04 | RAN_22 | RP-030648 | 064 | 1 | Correction of figure in combining of downlink physical channels | 5.4.0 | 5.5.0 | +| 06/01/04 | RAN_22 | RP-030648 | 065 | 1 | Correction of reference to calculation of HS-DPCCH gain factor | 5.4.0 | 5.5.0 | +| 06/01/04 | RAN_22 | RP-030727 | 067 | 2 | Restriction of DL secondary scrambling codes per CCTrCH | 5.4.0 | 5.5.0 | +| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.5.0 | 6.0.0 | +| 13/12/04 | RAN_26 | RP-040539 | 071 | 3 | Introduction of E-DCH | 6.0.0 | 6.1.0 | +| 13/12/04 | RAN_26 | RP-040450 | 069 | - | Introduction of MICH | 6.0.0 | 6.1.0 | +| 14/03/05 | RAN_27 | RP-050088 | 070 | 1 | Introduction of F-DPCH | 6.1.0 | 6.2.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/03/05 | RAN_27 | RP-050046 | 072 | - | Correction on E-DPCCH power offset | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN_27 | RP-050047 | 073 | 1 | Defining E-DPDCH power offset | 6.1.0 | 6.2.0 | +| 16/06/05 | RAN_28 | RP-050252 | 074 | 2 | Power offset values for E-DPDCH/E-DPCCH | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050252 | 075 | 3 | Support of different HARQ profiles | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050250 | 077 | 2 | Feature Clean Up: Removal of "CPCH" | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050248 | 079 | - | Feature Clean Up: Removal of DSCH (FDD mode) | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050256 | 080 | - | Correction to short scrambling code polynomial | 6.2.0 | 6.3.0 | +| 26/09/05 | RAN_29 | RP-050450 | 0081 | - | Clarification on derivation of $\beta_c$ and $\beta_d$ | 6.3.0 | 6.4.0 | +| 26/09/05 | RAN_29 | RP-050450 | 0082 | 1 | DL Scrambling Code and Phase Reference Combinations | 6.3.0 | 6.4.0 | +| 26/09/05 | RAN_29 | RP-050450 | 0083 | 1 | Clarification on power offset quantization | 6.3.0 | 6.4.0 | +| 20/03/06 | RAN_31 | RP-060076 | 0084 | 1 | Correction to number of configured DPDCHs when E-DPDCH is configured | 6.4.0 | 6.5.0 | +| 20/03/06 | RAN_31 | - | - | - | Creation of Release 7 specification (v7.0.0) at RAN#31 | 6.5.0 | 7.0.0 | +| 07/03/07 | RAN_35 | RP-070116 | 0085 | 2 | Introduction of 64QAM for HSDPA | 7.0.0 | 7.1.0 | +| 30/05/07 | RAN_36 | RP-070388 | 0086 | 4 | Introduction of 16-QAM for HSUPA | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070384 | 0087 | 1 | Support for DL only SFN operation for MBMS FDD | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070387 | 0089 | - | CQI and ACK/NACK power setting for MIMO | 7.1.0 | 7.2.0 | +| 11/09/07 | RAN_37 | RP-070644 | 0090 | - | Editorial changes in 25.213 for 16QAM specification | 7.2.0 | 7.3.0 | +| 27/11/07 | RAN_38 | RP-070944 | 0091 | 1 | Editorial changes in 25.213 for 16QAM specification | 7.3.0 | 7.4.0 | +| 04/03/08 | RAN_39 | - | - | - | Release 8 version further to RAN_39 decision | 7.4.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080439 | 0093 | 1 | Range of E-DCH amplitude ratios | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080709 | 0098 | - | Restricted Beta Factor Combinations for EUL | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-080989 | 0099 | - | Clarification to scrambling codes in dual cell HSDPA operation | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090238 | 0101 | 2 | Correction to DTX bit insertion for MBSFN 16-QAM | 8.3.0 | 8.4.0 | +| 18/09/09 | RAN_45 | - | - | - | Release 9 created further to RAN_45 decision | 8.4.0 | 9.0.0 | +| 01/12/09 | RAN_46 | RP-091170 | 0103 | 2 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 | +| 01/12/09 | RAN_46 | RP-091161 | 0106 | - | Clarification of the quantization of E-DPDCH power offset without E-DPCCH boosting | 9.0.0 | 9.1.0 | +| 14/09/10 | RAN_49 | RP-100897 | 0107 | 1 | Clarification of uplink frequencies | 9.1.0 | 9.2.0 | +| 16/09/10 | RAN_49 | RP-100902 | 0108 | 2 | Release 10 created with the introduction of 4C HSDPA | 9.2.0 | 10.0.0 | +| 05/12/11 | RAN_54 | RP-111671 | 0109 | 7 | Introduction of 8C-HSDPA | 10.0.0 | 11.0.0 | +| 05/12/11 | RAN_54 | RP-111672 | 0110 | 1 | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.0.0 | 11.0.0 | +| 28/02/12 | RAN_55 | RP-120288 | 0111 | - | Corrections to Uplink Closed Loop Transmit Diversity | 11.0.0 | 11.1.0 | +| 13/06/12 | RAN_56 | RP-120741 | 0112 | 1 | Clarification of CLTD Features | 11.1.0 | 11.2.0 | +| 04/09/12 | RAN_57 | RP-121271 | 0113 | 2 | Introduction of Multiflow | 11.2.0 | 11.3.0 | +| 04/09/12 | RAN_57 | RP-121384 | 0114 | 1 | Correction to the gain factor definition for S-DPCCH | 11.2.0 | 11.3.0 | +| 04/12/12 | RAN_58 | RP-121845 | 0115 | 6 | Introduction of uplink MIMO and 64QAM | 11.3.0 | 11.4.0 | +| 04/12/12 | RAN_58 | RP-121843 | 0116 | 6 | Introduction of 4Tx HSDPA in 25.213 | 11.3.0 | 11.4.0 | +| 10/09/14 | RAN_65 | RP-141482 | 0117 | 2 | Introduction of Enhanced Broadcast of System Information | 11.4.0 | 12.0.0 | +| 10/09/14 | RAN_65 | RP-141481 | 0118 | 1 | Introduction of UMTS Heterogeneous Networks enhancements | 11.4.0 | 12.0.0 | +| 07/12/15 | RAN_70 | RP-152023 | 0119 | 4 | Introduction of Dual Carrier HSUPA enhancements for UTRAN CS in TS 25.213 | 12.0.0 | 13.0.0 | +| 07/12/15 | RAN_70 | RP-152030 | 0121 | 1 | Introduction of HSPA Dual-Band UL carrier aggregation | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25214/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25214/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd159f150a5871918ee7e7573fd3c49d60ba56dc --- /dev/null +++ b/marked/Rel-16/25_series/25214/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00bc80b43be1fc27e118f6a61278218eedfdd46264fd9264b21ce29095748fca +size 63933 diff --git a/marked/Rel-16/25_series/25214/08ff9a984e4ab22be72c62ad9f39a4f3_img.jpg b/marked/Rel-16/25_series/25214/08ff9a984e4ab22be72c62ad9f39a4f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02bafd6496ba8ae170cc8be7374f7aae4ad5388d --- /dev/null +++ b/marked/Rel-16/25_series/25214/08ff9a984e4ab22be72c62ad9f39a4f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb528417c0251e306b7ea8a7d08ca0b87f22ff5ba6bf6b507077d318b3dec0b +size 1092 diff --git a/marked/Rel-16/25_series/25214/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/25_series/25214/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46e9147d9163554ae751501b9c8c138cb613d920 --- /dev/null +++ b/marked/Rel-16/25_series/25214/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60142d1ccc75c14f8b9e275e465227ec92debd8f54822c0d05e535d382af8d7e +size 108154 diff --git a/marked/Rel-16/25_series/25214/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/25_series/25214/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f1185dc3d0172d9ccad1dbe6b1606b0e14916b --- /dev/null +++ b/marked/Rel-16/25_series/25214/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daed3820d623be509bd379f00c443f68d72fa94e2fb10cf98a3cce9d6332119b +size 56110 diff --git a/marked/Rel-16/25_series/25214/2ff238be5d86662d1213fe4dadd67c96_img.jpg b/marked/Rel-16/25_series/25214/2ff238be5d86662d1213fe4dadd67c96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80f975d97c0b78d0feb85ca983441cf9c4bcbed --- /dev/null +++ b/marked/Rel-16/25_series/25214/2ff238be5d86662d1213fe4dadd67c96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b46148ab5b248eb29ed15113ad18c69767ffbc055c05eedb0830b6be3659ed56 +size 1159 diff --git a/marked/Rel-16/25_series/25214/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25214/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84d847d8ff77ecb1781ba1e0dc0e79c1e92ccc0 --- /dev/null +++ b/marked/Rel-16/25_series/25214/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1eda222f2013603b718baf8e8398a3edd11ec8700ae5348adb86425cfb5688d8 +size 11980 diff --git a/marked/Rel-16/25_series/25214/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/25_series/25214/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9a17d9511df1d1f43f3e8b05ade5f92cfebdc23 --- /dev/null +++ b/marked/Rel-16/25_series/25214/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af500466782a4073224442a321b13924423056e52092a503114016d7986a8981 +size 76605 diff --git a/marked/Rel-16/25_series/25214/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-16/25_series/25214/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e12b83c6ce17d4eab44f337cb56da8584aa8a22b --- /dev/null +++ b/marked/Rel-16/25_series/25214/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2254a322250a75c7290cb7cd1c2dfddca2056441a69bee59b46d4e87e2ceca97 +size 41019 diff --git a/marked/Rel-16/25_series/25214/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/25_series/25214/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..637e06da20b42ad54d37486381f0f8db2ad36a9f --- /dev/null +++ b/marked/Rel-16/25_series/25214/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13f03ea1b7ab3a3a458f801e2a053bc70d68e3650599782c7e7106b7ae4f2c77 +size 113452 diff --git a/marked/Rel-16/25_series/25214/7cb2bb7f9f6fd8be2dc5679e7053ae04_img.jpg b/marked/Rel-16/25_series/25214/7cb2bb7f9f6fd8be2dc5679e7053ae04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b99135f4168f3344c539ef5c3a55c21ae8f27dd6 --- /dev/null +++ b/marked/Rel-16/25_series/25214/7cb2bb7f9f6fd8be2dc5679e7053ae04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab03e46159b4e46d77fbbe3427f907229b23ec76810e4a8feba2a281af06ee3f +size 107444 diff --git a/marked/Rel-16/25_series/25214/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/25_series/25214/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abf91f88f18d0a20852cb7612bae0b1637b60ee9 --- /dev/null +++ b/marked/Rel-16/25_series/25214/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7df410ef952b39cfdc116559af38047e05d768ae5adeb47073a0774482d05971 +size 56516 diff --git a/marked/Rel-16/25_series/25214/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/25_series/25214/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40c749379c799033a1033ca45eb422796970e40b --- /dev/null +++ b/marked/Rel-16/25_series/25214/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:094279bb322d346642e4d4f73ef815b3100fbaf38e898d3206baae5e7627dddf +size 50370 diff --git a/marked/Rel-16/25_series/25214/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/25_series/25214/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bae458e56dcb4846a922dd8be5775dd9fe1d4f2 --- /dev/null +++ b/marked/Rel-16/25_series/25214/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d511d4d87f664cebe1cef091e7ac5b75690e6f44d62119918d93ffb8fd6a721 +size 110298 diff --git a/marked/Rel-16/25_series/25214/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-16/25_series/25214/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82c6ed2b56e4ebdec3d4f81480d9bda0ca6a2998 --- /dev/null +++ b/marked/Rel-16/25_series/25214/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fc4999843ccf9d48c055adbf53d61f49335b56e8d2422476379be0ac4c495cc +size 128621 diff --git a/marked/Rel-16/25_series/25214/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/25_series/25214/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73eb1d3fe9ea7748066f7e6200ac836db9b19150 --- /dev/null +++ b/marked/Rel-16/25_series/25214/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:162cf475c91b6a25b464e8b9c55d6b5e15f1878eb0451d27514ef43c87d81a66 +size 344693 diff --git a/marked/Rel-16/25_series/25214/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/25_series/25214/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5923e14559e906f4077a1bdc1e803c755a91b482 --- /dev/null +++ b/marked/Rel-16/25_series/25214/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5a7da5f0ad863b84868c9e08af897acb185bb63d97039f2f89b489f39ad8b00 +size 45601 diff --git a/marked/Rel-16/25_series/25214/a190fc2966c8406e81e2dfa7fbdd232d_img.jpg b/marked/Rel-16/25_series/25214/a190fc2966c8406e81e2dfa7fbdd232d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51019383faf554697909ea9ceef39446103ae924 --- /dev/null +++ b/marked/Rel-16/25_series/25214/a190fc2966c8406e81e2dfa7fbdd232d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd0e607ff18d6dfcbd853a95af6065afbfa853c23cce9b3327394964ddd9187d +size 2342 diff --git a/marked/Rel-16/25_series/25214/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/25_series/25214/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80171262debe8a3e019c1e77af5832444b6e7b37 --- /dev/null +++ b/marked/Rel-16/25_series/25214/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a104781cf375bc8ee361c07b6eee27838ede3dd148c8293e5b75fe81e1ccce3d +size 82211 diff --git a/marked/Rel-16/25_series/25214/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-16/25_series/25214/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e90747a87e6537b741fa12e400b0fa8574b8b9d --- /dev/null +++ b/marked/Rel-16/25_series/25214/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e5c28d7a23e66ca9a8ea7e3f2f245e177d2f6c53e79e42efe92b427eba43c1f +size 80908 diff --git a/marked/Rel-16/25_series/25214/b88b618bb8863766bd545c6bfb31f850_img.jpg b/marked/Rel-16/25_series/25214/b88b618bb8863766bd545c6bfb31f850_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..566451c2a012f6317ce2ff80a281070b5c92e71e --- /dev/null +++ b/marked/Rel-16/25_series/25214/b88b618bb8863766bd545c6bfb31f850_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de531eb3d45a73a1d563e2fb95729699885870e1b304205d54bbb80e2a6f66f4 +size 108381 diff --git a/marked/Rel-16/25_series/25214/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-16/25_series/25214/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb28c7a8cf3a66752dd8f7dbc36282c6607ea29a --- /dev/null +++ b/marked/Rel-16/25_series/25214/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88608a0876cc9ae5dee5fd1a6c3099d7424bf32e8695b5a35384d5b8a0d047b6 +size 87257 diff --git a/marked/Rel-16/25_series/25214/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/25_series/25214/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..206068fd9e0826b19c6360dc4465fedfa16b9a6d --- /dev/null +++ b/marked/Rel-16/25_series/25214/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e55ea8145e42ff9857d9012757641ecd95ae0141ea1357a1a863a2d990bc3c74 +size 78953 diff --git a/marked/Rel-16/25_series/25214/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Rel-16/25_series/25214/f5d2a88925807080157c7cfb1d41cf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ce043547b47cc1afad1b1fe550fec5034823e35 --- /dev/null +++ b/marked/Rel-16/25_series/25214/f5d2a88925807080157c7cfb1d41cf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c79e6fcbbe83898113d4e52cacbacc644dc65c3cb650fe60dfc7e9ef3b718009 +size 53480 diff --git a/marked/Rel-16/25_series/25214/raw.md b/marked/Rel-16/25_series/25214/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..42ec5a32406cbf85dd64b6f4c7b6e581b8b4630f --- /dev/null +++ b/marked/Rel-16/25_series/25214/raw.md @@ -0,0 +1,4543 @@ +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 10 | +| 4 Synchronization procedures..... | 11 | +| 4.1 Cell search..... | 11 | +| 4.2 Common physical channel synchronization..... | 11 | +| 4.2.1 P-CCPCH radio frame timing ..... | 11 | +| 4.2.2 S-CCPCH soft combining timing..... | 11 | +| 4.2.3 Radio frame timing on the MBSFN layer ..... | 12 | +| 4.2.4 Secondary serving HS-DSCH cell timing..... | 12 | +| 4.2.5 HS-DSCH cell timing when Multiflow is configured..... | 12 | +| 4.3 DPCCH/DPDCH/F-DPCH synchronization..... | 12 | +| 4.3.1 Synchronization primitives..... | 12 | +| 4.3.1.1 General..... | 12 | +| 4.3.1.2 Downlink synchronization primitives..... | 12 | +| 4.3.1.3 Uplink synchronization primitives..... | 14 | +| 4.3.2 Radio link establishment and physical layer reconfiguration for dedicated channels..... | 14 | +| 4.3.2.1 General..... | 14 | +| 4.3.2.2 Node B radio link set state machine ..... | 15 | +| 4.3.2.3 Synchronization procedure A ..... | 15 | +| 4.3.2.3A Synchronization procedure AA ..... | 17 | +| 4.3.2.4 Synchronization procedure B..... | 17 | +| 4.3.3 Radio link monitoring..... | 18 | +| 4.3.3.1 Downlink radio link failure..... | 18 | +| 4.3.3.2 Uplink radio link failure/restore in CELL_DCH state..... | 18 | +| 4.3.3.2A Uplink radio link failure/restore in CELL_FACH state and IDLE mode..... | 18 | +| 4.3.4 Transmission timing adjustments..... | 18 | +| 5 Power control..... | 19 | +| 5.1 Uplink power control ..... | 19 | +| 5.1.1 PRACH..... | 19 | +| 5.1.1.1 General..... | 19 | +| 5.1.1.2 Setting of PRACH control and data part power difference ..... | 19 | +| 5.1.2 DPCCH/DPDCH/DPCCH2..... | 19 | +| 5.1.2.1 General..... | 19 | +| 5.1.2.2 Ordinary transmit power control..... | 20 | +| 5.1.2.2.1 General ..... | 20 | +| 5.1.2.2.2 Algorithm 1 for processing TPC commands..... | 22 | +| 5.1.2.2.3 Algorithm 2 for processing TPC commands..... | 23 | +| 5.1.2.2.4 Algorithm 3 for processing TPC commands..... | 24 | +| 5.1.2.2A Ordinary transmit power control for DPCCH2..... | 25 | +| 5.1.2.3 Transmit power control in compressed mode..... | 26 | +| 5.1.2.3A Transmit power control in compressed mode for DPCCH2..... | 28 | +| 5.1.2.4 Transmit power control in the uplink DPCCH power control preamble..... | 29 | +| 5.1.2.5 Setting of the uplink DPCCH/DPDCH relative powers ..... | 29 | +| 5.1.2.5.1 General ..... | 29 | +| 5.1.2.5.2 Signalled gain factors..... | 30 | +| 5.1.2.5.3 Computed gain factors ..... | 30 | +| 5.1.2.5.4 Setting of the uplink DPCCH/DPDCH relative powers in compressed mode..... | 30 | +| 5.1.2.5A Setting of the uplink HS-DPCCH power relative to DPCCH or DPCCH2 power..... | 31 | +| 5.1.2.5B Setting of the uplink E-DPCCH and E-DPDCH powers relative to DPCCH power..... | 34 | +| 5.1.2.5B.1 E-DPCCH/DPCCH when one transport block is transmitted on E-DCH..... | 34 | +| 5.1.2.5B.1A E-DPCCH/DPCCH when two transport blocks are transmitted on E-DCH (rank-2)..... | 35 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 5.1.2.5B.2 | E-DPDCH/DPCCH ..... | 36 | +| 5.1.2.5C | Setting of the uplink DPCCH gain factor when no DPDCH is configured ..... | 40 | +| 5.1.2.5D | Setting of the uplink S-DPCCH power relative to DPCCH power ..... | 40 | +| 5.1.2.5D.1 | Setting of the uplink S-DPCCH/DPCCH power ratio when less than two transport blocks are transmitted on E-DCH ..... | 40 | +| 5.1.2.5D.2 | Setting of the uplink S-DPCCH/DPCCH power ratio when two transport blocks are transmitted on E-DCH (rank-2) ..... | 41 | +| 5.1.2.5E | Setting of the uplink S-E-DPCCH power relative to DPCCH power ..... | 41 | +| 5.1.2.5F | Setting of the uplink S-E-DPDCH power relative to E-DPDCH power ..... | 41 | +| 5.1.2.6 | Maximum and minimum power limits ..... | 42 | +| 5.1.3 | Void ..... | 45 | +| 5.2 | Downlink power control ..... | 45 | +| 5.2.1 | DPCCH/DPDCH/F-DPCH ..... | 45 | +| 5.2.1.1 | General ..... | 45 | +| 5.2.1.2 | Ordinary transmit power control ..... | 45 | +| 5.2.1.2.1 | UE behaviour ..... | 45 | +| 5.2.1.2.2 | UTRAN behaviour ..... | 47 | +| 5.2.1.3 | Power control in compressed mode ..... | 48 | +| 5.2.1.4 | Power scaling of DPDCH with PO SRB ..... | 49 | +| 5.2.2 | Void ..... | 50 | +| 5.2.3 | Void ..... | 50 | +| 5.2.4 | AICH ..... | 50 | +| 5.2.5 | PICH ..... | 50 | +| 5.2.6 | S-CCPCH ..... | 50 | +| 5.2.7 | Void ..... | 50 | +| 5.2.8 | Void ..... | 50 | +| 5.2.9 | Void ..... | 50 | +| 5.2.10 | HS-SCCH ..... | 50 | +| 5.2.11 | HS-PDSCH ..... | 51 | +| 5.2.12 | E-AGCH ..... | 51 | +| 5.2.13 | E-HICH ..... | 51 | +| 5.2.14 | E-RGCH ..... | 51 | +| 5.2.15 | MICH ..... | 51 | +| 5.2.16 | S-CPICH ..... | 51 | +| 5.2.17 | F-TPICH ..... | 51 | +| 5.2.18 | D-CPICH ..... | 51 | +| 5.2.19 | E-ROCH ..... | 52 | +| 6 | Random access procedure ..... | 52 | +| 6.1 | Physical random access procedure ..... | 52 | +| 6.1.1 | RACH sub-channels ..... | 53 | +| 6.1.2 | RACH access slot sets ..... | 54 | +| 6.1A | Physical random access procedure for Enhanced Uplink in CELL_FACH state and IDLE mode ..... | 54 | +| 6.2 | Void ..... | 56 | +| 6A | HS-DSCH-related procedures ..... | 56 | +| 6A.1 | General procedure ..... | 56 | +| 6A.1.1 | UE procedure for receiving HS-DSCH and HS-SCCH in the CELL_DCH state ..... | 58 | +| 6A.1.1A | UE procedure for receiving HS-DSCH and HS-SCCH in CELL_FACH state ..... | 63 | +| 6A.1.1B | UE procedure for receiving HS-DSCH and HS-SCCH in the URA_PCH and CELL_PCH states ..... | 63 | +| 6A.1.2 | UE procedure for reporting channel quality indication (CQI) and precoding control indication (PCI) ..... | 64 | +| 6A.1.2.1 | CQI reporting procedure in case the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in any cell ..... | 65 | +| 6A.1.2.2 | Composite PCI/CQI reporting procedure in case the UE is configured in MIMO mode ..... | 67 | +| 6A.1.2.3 | Composite NTBP/PCI/CQI reporting procedure in case the UE is configured in MIMO mode with four transmit antennas ..... | 69 | +| 6A.1.3 | Node B procedure for transmitting the HS-DSCH and HS-SCCH ..... | 71 | +| 6A.1.3.1 | Node B procedure for transmitting the HS-DSCH and HS-SCCH in the CELL_DCH state ..... | 71 | +| 6A.1.3.2 | Node B procedure for transmitting the HS-DSCH and HS-SCCH in the CELL_FACH state ..... | 72 | +| 6A.1.3.3 | Node B procedure for transmitting the HS-DSCH and HS-SCCH in the URA_PCH or CELL_PCH state ..... | 72 | +| 6A.2 | Channel quality indicator (CQI) definition ..... | 73 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------|-----| +| 6A.2.1 | CQI definition when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas ..... | 73 | +| 6A.2.2 | CQI definition when the UE is configured in MIMO mode ..... | 73 | +| 6A.2.2A | CQI definition when the UE is configured in MIMO mode with four transmit antennas..... | 75 | +| 6A.2.3 | CQI tables..... | 76 | +| 6A.3 | Operation during compressed mode on the associated DPCH or F-DPCH ..... | 87 | +| 6A.4 | Precoding control indication (PCI) definition..... | 87 | +| 6A.4.1 | PCI definition when the UE is configured in MIMO mode ..... | 87 | +| 6A.4.2 | PCI definition when the UE is configured in MIMO mode with four transmit antennas ..... | 88 | +| 6B | E-DCH related procedures ..... | 89 | +| 6B.1 | ACK/NACK detection ..... | 89 | +| 6B.2 | Relative grants detection ..... | 90 | +| 6B.2A | Absolute Grant Detection when the UE is configured with Implicit Grant Handling ..... | 90 | +| 6B.3 | E-DCH control timing..... | 90 | +| 6B.3.0 | UE procedure for switching the E-DCH TTI length due to an HS-SCCH order ..... | 91 | +| 6B.3.1 | 10 ms E-DCH TTI..... | 91 | +| 6B.3.2 | 2 ms E-DCH TTI..... | 91 | +| 6B.4 | Operation during compressed mode..... | 92 | +| 6B.4.1 | Uplink compressed mode ..... | 92 | +| 6B.4.2 | Downlink compressed mode ..... | 92 | +| 6C | Discontinuous transmission and reception procedures ..... | 92 | +| 6C.0 | Discontinuous transmission/reception of DCH..... | 93 | +| 6C.0.1 | DL_DPCH_DYN_DRX and UL_DPCH_DYN_DTX ..... | 93 | +| 6C.0.1.1 | DL_DCH_FET_Config = 0 ..... | 93 | +| 6C.0.1.2 | DL_DCH_FET_Config = 1 ..... | 94 | +| 6C.1 | Uplink CQI transmission..... | 94 | +| 6C.2 | Discontinuous uplink DPCCH/DPCCH2 transmission operation ..... | 95 | +| 6C.2.1 | Uplink DPCCH burst pattern..... | 95 | +| 6C.2.2 | Uplink DPCCH preamble and postamble..... | 97 | +| 6C.2.2.1 | Uplink DPCCH preamble and postamble for the DPCCH only transmission..... | 97 | +| 6C.2.2.2 | Uplink DPCCH preamble and postamble for the E-DCH transmission..... | 97 | +| 6C.2.2.3 | Uplink DPCCH preamble and postamble for the HS-DPCCH transmission ..... | 97 | +| 6C.3 | Discontinuous downlink reception..... | 98 | +| 6C.3.1 | Discontinuous downlink reception when the UE is in Multiflow mode..... | 100 | +| 6C.4 | HS-SCCH orders ..... | 101 | +| 6C.5 | Operation during compressed mode..... | 101 | +| 7 | Closed loop mode 1 transmit diversity ..... | 102 | +| 7.1 | General procedure ..... | 103 | +| 7.2 | Determination of feedback information ..... | 104 | +| 7.2.1 | End of frame adjustment ..... | 104 | +| 7.2.2 | Normal initialisation..... | 105 | +| 7.2.3 | Operation during compressed mode..... | 105 | +| 7.2.3.1 | Downlink in compressed mode and uplink in normal mode ..... | 105 | +| 7.2.3.2 | Both downlink and uplink in compressed mode..... | 105 | +| 7.2.3.3 | Uplink in compressed mode and downlink in normal mode ..... | 106 | +| 7.2.4 | Initialisation during compressed mode..... | 106 | +| 7.2.4.1 | Downlink in compressed mode..... | 106 | +| 7.2.4.2 | Uplink in compressed mode ..... | 107 | +| 7.3 | Void..... | 107 | +| 8 | Idle periods for IPDL location method ..... | 107 | +| 8.1 | General ..... | 107 | +| 8.2 | Parameters of IPDL..... | 107 | +| 8.3 | Calculation of idle period position ..... | 108 | +| 9 | MIMO operation of HS-DSCH..... | 110 | +| 9.1 | General procedure ..... | 112 | +| 10 | Uplink Closed Loop Transmit Diversity operation..... | 112 | +| 10.1 | General procedure ..... | 112 | +| 10.2 | Downlink TPI transmission and control timing ..... | 114 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------|------------| +| 10.3 | Combining TPI bits from multiple radio links ..... | 115 | +| 10.4 | Operation during discontinuous uplink DPCCH operation..... | 115 | +| 10.5 | Operation during compressed mode..... | 115 | +| 10.5.1 | Uplink compressed mode ..... | 115 | +| 10.5.2 | Downlink compressed mode ..... | 115 | +| 10.6 | HS-SCCH orders ..... | 115 | +| 11 | Uplink MIMO ..... | 116 | +| 11.1 | General procedure ..... | 118 | +| 11.2 | Downlink TPI transmission and control timing ..... | 118 | +| 11.3 | Combining TPI bits from radio links of the serving radio link set ..... | 119 | +| 11.4 | Operation during discontinuous uplink DPCCH operation..... | 119 | +| 11.5 | Operation during compressed mode..... | 119 | +| 11.6 | HS-SCCH orders ..... | 119 | +| 11.7 | Uplink power control ..... | 119 | +| 12 | MIMO operation of HS-DSCH with four transmit antennas ..... | 119 | +| 12.1 | General procedure ..... | 121 | +| 12.2 | Symbol level interleaving..... | 121 | +| 12.3 | Retransmission Procedures ..... | 122 | +| 12.4 | Precoding weight restriction..... | 123 | +| 12.5 | HS-SCCH Orders ..... | 123 | +| Annex A (informative): | (no title) ..... | 124 | +| A.1 | Antenna verification..... | 124 | +| A.2 | Computation of feedback information for closed loop mode 1 transmit diversity ..... | 125 | +| Annex B (Informative): | Power control..... | 126 | +| B.1 | Downlink power control timing..... | 126 | +| B.2 | Example of implementation in the UE..... | 131 | +| B.3 | UL power control when losing UL synchronization..... | 131 | +| Annex C (Informative): | Cell search procedure ..... | 132 | +| Annex D (Informative): | F-TPICH Transmission ..... | 133 | +| Annex E (informative): | Change history..... | 134 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD mode of UTRA. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [5] 3GPP TS 25.331: "RRC Protocol Specification". +- [6] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling". +- [7] 3GPP TS 25.101: "UE Radio transmission and Reception (FDD)". +- [8] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)". +- [9] 3GPP TS 25.321: "MAC protocol specification". +- [10] 3GPP TS 25.306: "UE Radio Access Capabilities". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Activated uplink frequency:** For a specific UE, an uplink frequency is said to be activated if the UE is allowed to transmit on that frequency. The primary uplink frequency is always activated when configured while a secondary uplink frequency has to be activated by means of an HS-SCCH order in order to become activated. Similarly, for a specific UE, an uplink frequency is said to be deactivated if it is configured but disallowed by the NodeB to transmit on that frequency. + +**Assisting secondary serving HS-DSCH Cell(s):** In addition to the serving HS-DSCH cell, a cell in the secondary downlink frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. There can be up to two assisting secondary serving HS-DSCH cells. + +**Assisting serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the same frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Cell group:** A group of (one, two or three) Multiflow mode cells that have the same CPICH timing. The cells that belong to a cell group are indicated by higher layers. + +**Configured uplink frequency:** For a specific UE, an uplink frequency is said to be configured if the UE has received all relevant information from higher layers in order to perform transmission on that frequency. + +**Designated non-serving HS-DSCH cell:** The non-serving HS-DSCH cell transmitting the F-DPCH that is used to estimate the F-DPCH quality for TPC command derivation, when the UE is configured with DPCCH2 in the uplink or E-DCH decoupling is configured. + +**DL FET:** DL FET refers to early termination of DL DPCH transmission upon receiving an acknowledgement message. In this context, a DL FET ACK/NACK message represents an acknowledge message sent on UL DPCCH for DL FET. + +**DL\_DCH\_FET\_Config:** Higher layers signal this configuration parameter to indicate enhanced DCH physical layer configuration. The possible values are 0 and 1. The value 0 indicates Mode 0 configuration where DL transport channels concatenation and UL ACK/NACK signalling are not configured. The value 1 indicates Mode 1 where DL transport channel concatenation and UL ACK/NACK signalling for DL FET are configured. + +**E-DCH decoupling:** An E-DCH operation mode in which the Serving HS-DSCH cell and the Serving E-DCH cell are different. + +**L1 combining period:** An interval of contiguous TTIs when S-CCPCHs, each on different RLs, may be soft combined. + +**MIMO mode:** This term refers to the downlink MIMO configuration with two transmit antennas. + +**MIMO mode with four transmit antennas:** This term refers to the downlink MIMO configuration with four transmit antennas. + +**Multiflow mode:** The UE is configured in Multiflow mode when it is configured with an assisting serving HS-DSCH cell. + +**Non-time reference cell:** An HS-DSCH cell configured for a UE in Multiflow mode that has a different timing than the time reference cell. If the time reference cell is the Assisting Serving HS-DSCH cell then the non-time reference cell is the Serving HS-DSCH cell. If the time reference cell is the Serving HS-DSCH Cell, then the non-time reference cell is the Assisting Serving HS-DSCH cell. + +**Primary uplink frequency:** If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequency is configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**Secondary uplink frequency:** A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**SRB:** Signalling Radio Bearers as defined in [5]. + +**40ms Compression Interval (40ms CI):** A time interval of 40ms duration aligned in time with a 40ms TTI, defined for DPCH physical layer procedures when DCH channel is configured with a single transport channel of 40ms TTI carrying SRB data only. + +**Time reference cell:** The (Serving or Assisting Serving, but not Secondary Serving or Assisting Secondary Serving) HS-DSCH cell that carries the HS-PDSCH acting as the time reference for the uplink HS-DPCH when in Multiflow mode. There is one and only one Time reference cell. + +**UL DPCH 10ms Mode:** When configured by higher layers for the TTI to be transmitted [9], UL DPCH follows physical channel procedures specific to this mode. UL DPCH 10ms Mode can only happen when DL\_DCH\_FET\_Config is configured. + +**UL DPCH 20ms Mode:** When configured by higher layers for the TTI to be transmitted [9], UL DPCH is transmitted continuously over a Compression Interval of 20ms, and follows the physical channel procedures specific to this mode. UL DPCH 20ms Mode can only happen when DL\_DCH\_FET\_Config is configured. + +**UL 20ms Compression Interval (20ms CI):** A time interval of 20ms duration aligned in time with a 20ms TTI, defined for UL DPCH physical layer procedures when DL\_DCH\_FET\_Config is configured by higher layers. + +**1st secondary serving HS-DSCH cell:** If the UE is configured with two uplink frequencies, the 1st secondary serving HS-DSCH cell is the secondary serving HS-DSCH cell that is associated with the secondary uplink frequency. If the + +UE is configured with a single uplink frequency, the 1st secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**2nd secondary serving HS-DSCH cell:** If the UE is configured with more than two serving HS-DSCH cells, the 2nd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**3rd secondary serving HS-DSCH cell:** If the UE is configured with more than three serving HS-DSCH cells, the 3rd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**4th secondary serving HS-DSCH cell:** If the UE is configured with more than four serving HS-DSCH cells, the 4th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**5th secondary serving HS-DSCH cell:** If the UE is configured with more than five serving HS-DSCH cells, the 5th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**6th secondary serving HS-DSCH cell:** If the UE is configured with more than six serving HS-DSCH cells, the 6th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**7th secondary serving HS-DSCH cell:** If the UE is configured with eight serving HS-DSCH cells, the 7th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACK | Acknowledgement | +| AICH | Acquisition Indicator Channel | +| ASC | Access Service Class | +| BCH | Broadcast Channel | +| CCPCH | Common Control Physical Channel | +| CCTrCH | Coded Composite Transport Channel | +| CLTD | Closed Loop Transmit Diversity | +| CPICH | Common Pilot Channel | +| CQI | Channel Quality Indicator | +| CRC | Cyclic Redundancy Check | +| DCH | Dedicated Channel | +| DL | Downlink | +| DPCCH | Dedicated Physical Control Channel | +| DPCCH2 | Dedicated Physical Control Channel 2 | +| DPCH | Dedicated Physical Channel | +| DPDCH | Dedicated Physical Data Channel | +| DTX | Discontinuous Transmission | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced Dedicated Channel | +| E-DPCCH | E-DCH Dedicated Physical Control Channel | +| E-DPDCH | E-DCH Dedicated Physical Data Channel | +| E-HICH | E-DCH HARQ Acknowledgement Indicator Channel | +| E-RGCH | E-DCH Relative Grant Channel | +| E-ROCH | E-DCH Rank and Offset Channel | +| F-DPCH | Fractional Dedicated Physical Channel | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| HSDPA | High Speed Downlink Packet Access | +| HS-DPCCH | Dedicated Physical Control Channel (uplink) for HS-DSCH | +| HS-DPCCH 2 | Secondary Dedicated Physical Control Channel (uplink) for HS-DSCH, when Secondary_Cell_Enabled is greater than 3 when the UE is not configured in MIMO mode with four transmit antennas and is greater than 1 when the UE is configured in MIMO mode with four transmit antennas | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | High Speed Physical Downlink Shared Control Channel | +| MBSFN | MBMS over a Single Frequency Network | +| MICH | MBMS Indicator Channel | +| MIMO | Multiple Input Multiple Output | + +| | | +|-------------|--------------------------------------------------------| +| NACK | Negative Acknowledgement | +| NT-HS-DPCCH | NodeB Triggered HS-DPCCH | +| P-CCPCH | Primary Common Control Physical Channel | +| PCA | Power Control Algorithm | +| PICH | Paging Indicator Channel | +| PRACH | Physical Random Access Channel | +| RACH | Random Access Channel | +| RL | Radio Link | +| RPL | Recovery Period Length | +| RSCP | Received Signal Code Power | +| S-CCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronization Channel | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| S-E-DPCCH | Secondary Dedicated Physical Control Channel for E-DCH | +| S-E-DPDCH | Secondary Dedicated Physical Data Channel for E-DCH | +| SFN | System Frame Number | +| SIR | Signal-to-Interference Ratio | +| SNIR | Signal to Noise Interference Ratio | +| TFC | Transport Format Combination | +| TFRI | Transport Format and Resource Indicator | +| TPC | Transmit Power Control | +| TPI | Transmitted Precoding Indicator | +| TrCH | Transport Channel | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Synchronization procedures + +## 4.1 Cell search + +During the cell search, the UE searches for a cell and determines the downlink scrambling code and common channel frame synchronization of that cell. How cell search is typically done is described in Annex C. + +## 4.2 Common physical channel synchronization + +The radio frame timing of all common physical channels can be determined after cell search. + +### 4.2.1 P-CCPCH radio frame timing + +The P-CCPCH radio frame timing is found during cell search and the radio frame timing of all common physical channel are related to that timing as described in [1]. + +### 4.2.2 S-CCPCH soft combining timing + +Higher layers will provide timing information when S-CCPCHs, each on different RLs, can be soft combined. The timing information allows the UE to determine the L1 combining period that applies to each S-CCPCH. The information also identifies the S-CCPCHs and the RLs that can be soft combined. The set of S-CCPCHs that can be combined does not change during an L1 combining period. When S-CCPCHs can be soft combined, all S-CCPCHs shall contain identical bits in their data fields, although the TFCI fields of the S-CCPCHs may be different. (TFC detection when S-CCPCHs may be soft combined is discussed in [2].) The maximum delay between S-CCPCHs that the UE may combine is set by UE performance requirements. The maximum number of S-CCPCHs that UE may simultaneously combine is defined by the UE capability in [10]. + +### 4.2.3 Radio frame timing on the MBSFN layer + +MBSFN cluster search and radio frame synchronization on the MBSFN layer can be performed via SCH and follow the same principles as described in Annex C. After the primary scrambling code has been identified, the P-CCPCH can be detected and MBSFN system information can be read. + +### 4.2.4 Secondary serving HS-DSCH cell timing + +When the UE is configured with one or more secondary serving HS-DSCH cells, it shall not assume the presence of any common physical channel from these cells other than CPICH. The radio frame timing and timing reference for each of the secondary serving HS-DSCH cells are defined in [1]. + +### 4.2.5 HS-DSCH cell timing when Multiflow is configured + +When the UE is configured in Multiflow mode, the UE shall not assume any timing relation between the serving HS-DSCH cell and the assisting serving HS-DSCH cell. The UE can only be configured with an assisting serving HS-DSCH cell if that cell is contained in the UE's active set. If the UE is also configured with multiple uplink frequencies, then the UE can only be configured with an assisting secondary serving HS-DSCH cell if that cell is contained in the UE's active set on the secondary uplink frequency. + +The UE may assume that the serving HS-DSCH cell and the secondary serving HS-DSCH cell, if present, have the same radio frame timing. + +The UE may assume that the assisting serving HS-DSCH cell and the assisting secondary serving HS-DSCH cell, if present, have the same radio frame timing. + +## 4.3 DPCCH/DPDCH/F-DPCH synchronization + +### 4.3.1 Synchronization primitives + +#### 4.3.1.1 General + +For the dedicated channels, synchronization primitives are used to indicate the synchronization status of radio links, both in uplink and downlink. The definition of the primitives is given in the following subclauses. + +#### 4.3.1.2 Downlink synchronization primitives + +If UL\_DTX\_Active is FALSE (see clause 6C), layer 1 in the UE shall every radio frame check synchronization status of either the DPCH or the F-DPCH depending on which is configured. If UL\_DTX\_Active is TRUE (see clause 6C), the layer 1 in the UE shall check synchronization status of the F-DPCH for each radio frame in which the F-DPCH transmission is known to be present in at least one slot, and for the other radio frames, the layer 1 will not indicate any synchronization status to the higher layers. Synchronization status is indicated to higher layers using the CPHY-Sync-IND and CPHY-Out-of-Sync-IND primitives. + +The criteria for reporting synchronization status are defined in two different phases. Each phase is performed by the UE for each individual downlink frequency associated with the activated uplink frequencies. The downlink synchronization primitives are also reported to higher layers for each individual downlink frequency associated with the activated uplink frequencies. + +The first phase starts when higher layers initiate physical dedicated channel establishment (as described in [5]) or whenever the UE initiates synchronization procedure A or synchronization procedure AA (as described in subclauses 4.3.2.1 and 4.3.2.3A) and lasts until 160 ms after the downlink dedicated channel is considered established by higher layers (physical channel establishment is defined in [5]). During this time out-of-sync shall not be reported and in-sync shall be reported using the CPHY-Sync-IND primitive if the following criterion is fulfilled: + +- The UE estimates the DPCCH quality or the quality of the TPC fields of the F-DPCH frame received from the associated serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH frame received from the serving E-DCH cell (or secondary serving E-DCH cell) when E-DCH decoupling is configured and DPCCH2 is not configured over the previous 40 ms period to be better than a threshold $Q_{in}$ , or over the previous 120ms or 200ms to be better than a threshold $Q_{in}$ if the Algorithm 3 is configured, when the length of the slot cycle is 3 or 5 respectively. This criterion shall be assumed not to be fulfilled before 40 ms of DPCCH or F-DPCH quality measurements have been collected when either the Algorithm 1 or 2 is configured, or before 120 ms or 200 ms of F-DPCH quality measurements have been collected if the Algorithm 3 is configured, when the length of the slot cycle is 3 or 5 respectively. $Q_{in}$ is defined implicitly by the relevant tests in [7]. +- If both DPCCH and F-DPCH are transmitted when DPCCH2 is configured, then the UE shall use the DPCCH for the estimation of the quality of the TPC fields. + +When DL\_DCH\_FET\_Config is configured, the UE shall indicate UL\_DPCH\_20ms\_Mode through the TFCI information carried on the UL DPCCH while both the UE and network transmit as per UL\_DPCH\_20ms\_Mode lasting for 160 ms after the downlink dedicated channel is considered established by higher layers. + +The second phase starts 160 ms after the downlink dedicated channel is considered established by higher layers. During this phase both out-of-sync and in-sync are reported as follows. + +Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive if any of the following criteria is fulfilled: + +- UL\_DTX\_Active is FALSE (see clause 6C) and the UE estimates the DPCCH quality or the quality of the TPC fields of the F-DPCH frame received from the associated serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH frame received from the serving E-DCH cell (or secondary serving E-DCH cell) when E-DCH decoupling is configured and DPCCH2 is not configured over the previous 160 ms period to be worse than a threshold $Q_{out}$ . $Q_{out}$ is defined implicitly by the relevant tests in [7]. If both DPCCH and F-DPCH are transmitted when DPCCH2 is configured, then the UE shall use the DPCCH for the estimation of the quality of the TPC fields. +- If PCA has the value 3 or UL\_DTX\_Active is TRUE (see clause 6C) and the UE estimates the quality of the TPC fields of the F-DPCH from the associated serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH frame received from the serving E-DCH cell (or secondary serving E-DCH cell) when E-DCH decoupling is configured and DPCCH2 is not configured over the previous 240 slots in which the TPC symbols are known to be present to be worse than a threshold $Q_{out}$ . $Q_{out}$ is defined implicitly by the relevant tests in [7]. If both DPCCH and F-DPCH are transmitted when DPCCH2 is configured, then the UE shall use the DPCCH for the estimation of the quality of the TPC fields. +- The 20 most recently received transport blocks with a non-zero length CRC attached, as observed on all TrCHs using non-zero length CRC mapped to the DPDCH, have been received with incorrect CRC. In addition, over the previous 160 ms, all transport blocks with a non-zero length CRC attached have been received with incorrect CRC. In case no TFCI is used this criterion shall not be considered for the TrCH(s) not using guided detection if they do not use a non-zero length CRC in all transport formats. If no transport blocks with a non-zero length CRC attached are received over the previous 160 ms this criterion shall not be assumed to be fulfilled. + +For a DPCH, in-sync shall be reported using the CPHY-Sync-IND primitive if both of the following criteria are fulfilled: + +- The UE estimates the DPCCH quality over the previous 160 ms period to be better than a threshold $Q_{in}$ . $Q_{in}$ is defined implicitly by the relevant tests in [7]. +- At least one transport block with a non-zero length CRC attached, as observed on all TrCHs using non-zero length CRC mapped to the DPDCH, is received in a TTI ending in the current frame with correct CRC. If no transport blocks are received, or no transport block has a non-zero length CRC attached in a TTI ending in the current frame and in addition over the previous 160 ms at least one transport block with a non-zero length CRC attached has been received with a correct CRC, this criterion shall be assumed to be fulfilled. If no transport blocks with a non-zero length CRC attached are received over the previous 160 ms this criterion shall also be assumed to be fulfilled. In case no TFCI is used this criterion shall not be considered for the TrCH(s) not using guided detection if they do not use a non-zero length CRC in all transport formats. + +For a F-DPCH, in-sync shall be reported using the CPHY-Sync-IND primitive if any of the following criteria is fulfilled: + +- UL\_DTX\_Active is FALSE (see clause 6C) and the UE estimates the quality of the TPC fields of the F-DPCH frame received from the associated serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH frame received from the serving E-DCH cell (or secondary serving E-DCH cell) when E-DCH decoupling is configured and DPCCH2 is not configured over the previous 160 ms period to be better than a threshold $Q_{in}$ . $Q_{in}$ is defined implicitly by the relevant tests in [7]. +- If PCA has the value 3 or UL\_DTX\_Active is TRUE (see clause 6C) and the UE estimates the quality of the TPC fields of the F-DPCH from the associated serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH frame received from the serving E-DCH cell (or secondary serving E-DCH cell) when E-DCH decoupling is configured and DPCCH2 is not configured over the previous 240 slots in which the TPC symbols are known to be present to be better than a threshold $Q_{in}$ . $Q_{in}$ is defined implicitly by the relevant tests in [7]. + +- If both DPCH and F-DPCH are transmitted when DPCCH2 is configured, then the UE shall use the DPCH in-sync reporting procedure. + +How the primitives are used by higher layers is described in [5]. The above definitions may lead to radio frames where neither the in-sync nor the out-of-sync primitives are reported. + +#### 4.3.1.3 Uplink synchronization primitives + +Layer 1 in the Node B shall every radio frame check synchronization status of all radio link sets. Synchronization status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitive. Hence, only one synchronization status indication shall be given per radio link set. + +The exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received DPCCH or DPCCH2 quality or CRC checks. One example would be to have the same criteria as for the downlink synchronization status primitives. + +### 4.3.2 Radio link establishment and physical layer reconfiguration for dedicated channels + +#### 4.3.2.1 General + +Three synchronization procedures are defined in order to obtain physical layer synchronization of dedicated channels between UE and UTRAN: + +- Synchronization procedure A: This procedure shall be used when at least one downlink dedicated physical channel (i.e. a DPCH or F-DPCH) and one uplink dedicated physical channel are to be set up on a frequency and none of the radio links after the establishment/reconfiguration existed on that frequency prior to the establishment/reconfiguration which also includes the following cases : + - the UE was previously on another RAT i.e. inter-RAT handover + - the UE was previously on another frequency i.e. inter-frequency hard handover + - the UE has all its previous radio links removed and replaced by other radio links i.e. intra-frequency hard-handover + - after it fails to complete an inter-RAT, intra- or inter-frequency hard-handover [8], the UE attempts to re-establish [5] all the dedicated physical channels which were already established immediately before the hard-handover attempt. In this case only steps c) and d) of synchronization procedure A are applicable. + - the UE receives an HS-SCCH order to activate the secondary uplink frequency as specified in [2] and the UE is configured with multiple frequencies on the uplink. + +For transitions from the CELL\_FACH state of a cell to the CELL\_DCH state of the same cell,, when synchronization has already been achieved by a synchronization procedure AA and the UE has not already released its uplink common E-DCH resource before the time of transition to CELL\_DCH, the synchronization procedure A shall not be executed. Else, the synchronization procedure A shall be executed. + +- Synchronization procedure AA: This procedure shall be used when one downlink F-DPCH and uplink dedicated physical channels are to be set up on a frequency as a consequence of an Enhanced Uplink in CELL\_FACH procedure. +- Synchronization procedure B: This procedure shall be used when one or several radio links are added to the active set on a frequency and at least one of the radio links prior to the establishment/reconfiguration still exists on that frequency after the establishment/reconfiguration. +- If higher layers indicate that the UE shall not perform any synchronization procedure for timing maintained intra- and inter-frequency hard handover, the UE shall not perform any of the synchronization procedures A or B. If higher layers indicate to the Node B timing maintained intra- or inter-frequency hard handover where the UE does not perform any of the synchronization procedures A, AA or B, the Node B shall perform steps a) and b) of synchronization procedure B. + +For all physical layer reconfigurations not listed above, the UE and UTRAN shall not perform any of the synchronization procedures listed above. + +The three synchronization procedures are described in subclauses 4.3.2.3, 4.3.2.3A and 4.3.2.4 respectively. + +#### 4.3.2.2 Node B radio link set state machine + +In Node B, each radio link set can be in three different states: initial state, out-of-sync state and in-sync state. Transitions between the different states are shown in figure 1 below. The state of the Node B at the start of radio link establishment is described in the following subclauses. Transitions between initial state and in-sync state are described in subclauses 4.3.2.3, 4.3.2.3A and 4.3.2.4 and transitions between the in-sync and out-of-sync states are described in subclause 4.3.3.2. + +$$y^{(0)}(i) = x^{(0)}(i)$$ + +**Figure 1: Node B radio link set states and transitions** + +#### 4.3.2.3 Synchronization procedure A + +For each configured uplink frequency, the synchronization establishment procedure, which begins at the time indicated by higher layers (either immediately at receipt of upper layer signalling, or at an indicated activation time), or by an HS-SCCH order to activate the secondary uplink frequency (in the case multiple frequencies are configured on the uplink) is as follows: + +- a) Each Node B involved in the procedure sets all the radio link sets which are to be set-up for this UE in the initial state. +- b) UTRAN shall start the transmission of the downlink DPCCH or F-DPCH corresponding to the activated uplink frequency and may start the transmission of DPDCH if any data is to be transmitted. The initial downlink DPCCH or F-DPCH transmit power is set by higher layers [6]. Downlink TPC commands are generated as described in 5.1.2.2.1.2. +- c) The UE establishes downlink chip and frame synchronization of DPCCH or F-DPCH corresponding to the activated uplink frequency, using the P-CCPCH timing and timing offset information notified from UTRAN. For DPCH, frame synchronization can be confirmed using the frame synchronization word. Downlink synchronization status is reported to higher layers every radio frame according to subclause 4.3.1.2. +- d) If higher layers indicate the usage of a post-verification period for the primary uplink frequency the UE shall start transmission on the primary uplink frequency immediately when the physical dedicated channel establishment is initiated by the UE. When DL\_DCH\_FET\_Config is configured, the UE shall continue to indicate and transmit as per UL\_DPCH\_20ms\_Mode. Post-verification period shall not be used if the Algorithm 3 is configured. Post-verification period is always used for the secondary uplink frequency, except when Algorithm 3 is configured, or when DTX enhancements is configured, in which case upon successfully receiving an HS-SCCH order to activate the secondary uplink frequency, in-sync shall be reported, and the UE shall start transmission on the secondary uplink frequency immediately according to the DTX settings if configured. In this case, the synchronization status evaluation shall be performed immediately according to the second phase of the downlink synchronization status evaluation. +- e) If higher layers do not indicate the usage of a post-verification period for the primary uplink frequency, or if higher layers do indicate the usage of a post-verification period (as specified in 5.1.2.2.1.1) and the post-verification has failed, the UE shall not transmit on the activated uplink frequency until higher layers consider the downlink physical channel established; + - If no activation time for uplink DPCCH has been signalled to the UE or if the UE attempts to re-establish the DPCH after an inter-RAT, intra- or inter-frequency hard-handover failure [5], uplink DPCCH transmission + +shall start on the activated uplink frequency when higher layers consider the downlink physical channel established; + +- If an activation time has been given, uplink DPCCH transmission shall not start on the activated uplink frequency before the downlink physical channel has been established and the activation time has been reached. Physical channel establishment and activation time are defined in [5]. + +The initial uplink DPCCH transmit power is set by higher layers [5]. In case the synchronization procedure A is executed because the UE receives an HS-SCCH order to activate the secondary uplink frequency, then the initial DPCCH transmit power on the secondary uplink frequency is computed (in dB) as + +$$\text{Uplink DPCCH transmit power} = P_{\text{DPCCH},1} - \text{UE\_Sec\_Tx\_Power\_Backoff}$$ + +where $P_{\text{DPCCH},1}$ is the DPCCH transmit power on the primary uplink frequency at the start of the transmission on the secondary uplink frequency and $\text{UE\_Sec\_Tx\_Power\_Backoff}$ is set by higher layers. + +In case the UE attempts to re-establish the DPCH after an inter-RAT, intra- or inter-frequency hard-handover failure [5] the initial uplink DPCCH power shall be the same as the one used immediately preceding the inter-RAT, intra- or inter-frequency hard-handover attempt. In case of physical layer reconfiguration the uplink DPCCH power is kept unchanged between before and after the reconfiguration except for inner loop power control adjustments. + +A power control preamble shall be applied on the activated uplink frequency as indicated by higher layers. The transmission of the uplink DPCCH power control preamble shall start $N_{\text{pcp}}$ radio frames prior to the radio frame where the uplink DPDCH/E-DPCCH/E-DPDCH transmission starts, where $N_{\text{pcp}}$ is a higher layer parameter set by UTRAN [5]; in case the UE attempts to re-establish the DPCH after an inter-RAT, intra- or inter-frequency hard-handover failure [5] the UE shall use the value of $N_{\text{pcp}}$ as specified in [5] for this case. Note that the transmission start delay between DPCCH and DPDCH/E-DPCCH/E-DPDCH may be cancelled using a power control preamble of 0 length. If higher layers indicate the usage of a post-verification period, and the start of the uplink DPCCH power control preamble with a length of $N_{\text{pcp}}$ radio frames would be in a radio frame later than the first uplink radio frame after physical dedicated channel establishment is initiated by the UE, then the duration of the uplink DPCCH power control preamble shall be equal to or longer than $N_{\text{pcp}}$ radio frames such that the uplink DPCCH power control preamble is transmitted from the first uplink radio frame after physical dedicated channel establishment is initiated by the UE. + +The starting time for transmission of DPDCHs/E-DPCCH/E-DPDCHs shall also satisfy the constraints on adding transport channels to a CCTrCH, as defined in [2] subclause 4.2.14, independently of whether there are any bits mapped to the DPDCHs/E-DPCCH/E-DPDCHs. During the uplink DPCCH power control preamble, independently of the selected TFC, no transmission is done on the DPDCH/E-DPCCH/E-DPDCH. + +- e) UTRAN establishes uplink chip and frame synchronization on the activated uplink frequency. Frame synchronization can be confirmed using the frame synchronization word. Radio link sets remain in the initial state until $N_{\text{INSYNC\_IND}}$ successive in-sync indications are received from layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has obtained synchronization. When RL Restore has been triggered the radio link set shall be considered to be in the in-sync state. The parameter value of $N_{\text{INSYNC\_IND}}$ is configurable, see [6]. The RL Restore procedure may be triggered several times, indicating when synchronization is obtained for different radio link sets. + +Note: The total signalling response delay for the establishment of a new DPCH shall not exceed the requirements given in [5] subclause 13.5. + +#### 4.3.2.3A Synchronization procedure AA + +The synchronization establishment procedure, which begins at the time defined in [1] for the Enhanced Uplink in CELL\_FACH state and IDLE mode, is as follows: + +- a) The Node B involved in the procedure sets the radio link which is to be set-up for this UE in the initial state. +- b) UTRAN shall start the transmission of the downlink F-DPCH at the time defined for the Enhanced Uplink in CELL\_FACH state and IDLE mode in [1]. +- c) The UE establishes downlink chip and frame synchronization of F-DPCH, using the P-CCPCH timing and timing offset information notified from UTRAN and based on the timing definition for the Enhanced Uplink in + +CELL\_FACH state and IDLE mode as defined in [1]. Downlink synchronization status is reported to higher layers every radio frame according to subclause 4.3.1.2. + +- d) The UE shall start transmission on uplink at the time defined for the Enhanced Uplink in CELL\_FACH state and IDLE mode in [1] and shall use a post-verification period for confirming the establishment of the downlink physical channel as follows: During the first 40 ms period of the first phase of the downlink synchronization procedure the UE shall control its transmitter according to a downlink F-DPCH quality criterion as follows: + - When the UE estimates the F-DPCH quality over the first 40 ms period of the first phase of the downlink synchronization status evaluation to be worse than a threshold $Q_{in}$ , the UE shall shut its transmitter off and consider post-verification failed. $Q_{in}$ is defined implicitly by the relevant tests in [7]. + +If the post-verification has failed, the UE shall not transmit on uplink and await higher layer orders. + +- e) UTRAN establishes uplink chip and frame synchronization. Frame synchronization can be confirmed using the frame synchronization word. + +#### 4.3.2.4 Synchronization procedure B + +For each configured uplink frequency, the synchronization procedure B, which begins at the time indicated by higher layers (either immediately at receipt of upper layer signalling, or at an indicated activation time) is as follows: + +- a) The following applies to each Node B involved in the procedure: + - New radio link sets are set up to be in initial state. + - If one or several radio links are added to an existing radio link set, this radio link set shall be considered to be in the state the radio link set was prior to the addition of the radio link, i.e. if the radio link set was in the in-sync state before the addition of the radio link it shall remain in that state. +- b) UTRAN starts the transmission of the downlink DPCCH/DPDCH or F-DPCH for each new radio link for which the DPCH or F-DPCH is to be transmitted corresponding to the activated uplink frequency at a frame timing such that the frame timing received at the UE will be within $T_0 \pm 148$ chips prior to the frame timing of the uplink DPCCH/DPDCH at the UE. Simultaneously, UTRAN establishes uplink chip and frame synchronization of each new radio link. Frame synchronization can be confirmed using the frame synchronization word. Radio link sets considered to be in the initial state shall remain in the initial state until N\_INSYNC\_IND successive in-sync indications are received from layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has obtained synchronization. When RL Restore is triggered the radio link set shall be considered to be in the in-sync state. The parameter value of N\_INSYNC\_IND is configurable, see [6]. The RL Restore procedure may be triggered several times, indicating when synchronization is obtained for different radio link sets. +- c) The UE establishes chip and frame synchronization of each new radio link. Layer 1 in the UE keeps reporting downlink synchronization status to higher layers every radio frame according to the second phase of subclause 4.3.1.2. For DPCH, frame synchronization can be confirmed using the frame synchronization word for the radio link where the DPCH is transmitted. + +### 4.3.3 Radio link monitoring + +#### 4.3.3.1 Downlink radio link failure + +The downlink radio links where F-DPCH and/or DPCH is transmitted shall be monitored by the UE, to trigger radio link failure procedures. The downlink radio link failure criteria is specified in [5], and is based on the synchronization status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. + +#### 4.3.3.2 Uplink radio link failure/restore in CELL\_DCH state + +The uplink radio link sets are monitored by the Node B, to trigger radio link failure/restore procedures. Once the radio link sets have been established, they will be in the in-sync or out-of-sync states as shown in figure 1 in subclause 4.3.2.2. Transitions between those two states are described below. + +The uplink radio link failure/restore criteria is based on the synchronization status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. Note that only one synchronization status indication shall be given per radio link set. + +When the radio link set is in the in-sync state, Node B shall start timer T\_RLFAILURE after receiving N\_OUTSYNC\_IND consecutive out-of-sync indications. Node B shall stop and reset timer T\_RLFAILURE upon receiving successive N\_INSYNC\_IND in-sync indications. If T\_RLFAILURE expires, Node B shall trigger the RL Failure procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is triggered, the state of the radio link set change to the out-of-sync state. + +When the radio link set is in the out-of-sync state, after receiving N\_INSYNC\_IND successive in-sync indications Node B shall trigger the RL Restore procedure and indicate which radio link set has re-established synchronization. When the RL Restore procedure is triggered, the state of the radio link set change to the in-sync state. + +The specific parameter settings (values of T\_RLFAILURE, N\_OUTSYNC\_IND, and N\_INSYNC\_IND) are configurable, see [6]. + +#### 4.3.3.2A Uplink radio link failure/restore in CELL\_FACH state and IDLE mode + +The uplink radio link failure/restore is under the control of the Node B. + +### 4.3.4 Transmission timing adjustments + +During a connection the UE may adjust its DPDCH/DPCCH transmission time instant. + +When the UE autonomously adjusts its DPDCH/DPCCH transmission time instant, it shall simultaneously adjust the HS-DPCCH, DPCCH2, E-DPCCH, E-DPDCH, S-DPCCH, S-E-DPCCH and S-E-DPDCH transmission time instant by the same amount so that the relative timing between DPCCH/DPDCH/DPCCH2 and HS-DPCCH is kept constant and that DPCCH/DPDCH and DPCCH2 and E-DPCCH/E-DPDCH and S-DPCCH and S-E-DPCCH/S-E-DPDCH remain time aligned. + +If the receive timing for any downlink DPCCH/DPDCH or F-DPCH in the current active set has drifted, so the time between reception of the downlink DPCCH/DPDCH in question and transmission of uplink DPCCH/DPDCH lies outside the valid range, L1 shall inform higher layers of this, so that the network can be informed of this and downlink timing can be adjusted by the network. + +The maximum rate of uplink TX time adjustment, and the valid range for the time between downlink DPCCH/DPDCH or F-DPCH reception and uplink DPCCH/DPDCH transmission in the UE are defined by the requirements specified in [8]. + +When the UE's time reference cell for HSDPA Multiflow is changed, the UE shall adjust its HS-DPCCH transmission timing to comply with the definitions in [1]. + +# 5 Power control + +## 5.1 Uplink power control + +### 5.1.1 PRACH + +#### 5.1.1.1 General + +The power control during the physical random access procedure is described in clause 6. The setting of power of the message control and data parts is described in the next subclause. + +#### 5.1.1.2 Setting of PRACH control and data part power difference + +The message part of the uplink PRACH channel shall employ gain factors to control the control/data part relative power similar to the uplink dedicated physical channels. Hence, subclause 5.1.2.5 applies also for the RACH message part, with the differences that: + +- $\beta_c$ is the gain factor for the control part (similar to DPCCH); +- $\beta_d$ is the gain factor for the data part (similar to DPDCH); +- no inner loop power control is performed. + +### 5.1.2 DPCCH/DPDCH/DPCCH2 + +#### 5.1.2.1 General + +The initial uplink DPCCH transmit power is set by higher layers. Subsequently the uplink transmit power control procedure simultaneously and independently controls the power of a DPCCH on each activated uplink frequency and its corresponding DPDCHs (if present). The relative transmit power offset between DPCCH and DPDCHs is determined by the network and is computed according to subclause 5.1.2.5 using the gain factors signalled to the UE using higher layer signalling. + +The operation of the inner power control loop, described in sub clause 5.1.2.2, adjusts the power of the DPCCH and DPDCHs by the same amount, provided there are no changes in gain factors. Additional adjustments to the power of the DPCCH associated with the use of compressed mode are described in sub clause 5.1.2.3. + +Any change in the uplink DPCCH transmit power shall take place immediately before the start of the pilot field on the DPCCH. The change in DPCCH power with respect to its previous value is derived by the UE and is denoted by $\Delta_{\text{DPCCH}}$ (in dB). The previous value of DPCCH power shall be that used in the previous slot, except in the event of an interruption in transmission due to the use of compressed mode or discontinuous uplink DPCCH transmission operation, when the previous value shall be that used in the last slot before the transmission gap. If the DTX enhancements is configured, the initial UL DPCCH transmit power value after a transmission gap on the secondary uplink carrier if configured, shall be calculated according to subclause 5.1.2.2.1.3. + +During the operation of the uplink power control procedure the UE transmit power shall not exceed a maximum allowed value which is the lower out of the maximum output power of the terminal power class and a value which may be set by higher layer signalling. + +Uplink power control shall be performed while the UE transmit power is below the maximum allowed output power. + +The provisions for power control at the maximum allowed value and below the required minimum output power (as defined in [7]) are described in subclause 5.1.2.6. + +If DPCCH2 is configured, the initial uplink DPCCH2 transmit power is computed (in dB) as + +$$\text{Uplink DPCCH2 transmit power} = P_{\text{DPCCH}} + \text{UE\_DPCCH2\_Tx\_Power\_Offset}$$ + +where $P_{\text{DPCCH}}$ is the DPCCH transmit power on the primary uplink frequency at the start of the transmission of DPCCH2 and $\text{UE\_DPCCH2\_Tx\_Power\_Offset}$ is set by higher layers. + +The power control procedure for DPCCH2 is described in sub clause 5.1.2.2A. + +#### 5.1.2.2 Ordinary transmit power control + +##### 5.1.2.2.1 General + +For each activated uplink frequency, the uplink inner-loop power control adjusts the UE transmit power in order to keep the received uplink signal-to-interference ratio (SIR) on that frequency at a given SIR target, $\text{SIR}_{\text{target}}$ . + +The cells in the active set should estimate signal-to-interference ratio $\text{SIR}_{\text{est}}$ of the received uplink DPCH. The cells in the active set should then generate TPC commands and transmit the commands once per slot or once per slot cycle if Algorithm 3 is configured according to the following rule: if $\text{SIR}_{\text{est}} > \text{SIR}_{\text{target}}$ then the TPC command to transmit is "0", while if $\text{SIR}_{\text{est}} < \text{SIR}_{\text{target}}$ then the TPC command to transmit is "1". When $\text{UL\_DTX\_Active}$ is TRUE (see clause 6C) or $\text{DL\_DCH\_FET\_Config}$ is configured, a TPC command is not required to be transmitted in any downlink slot starting during an uplink DPCCH slot which is in an uplink DPCCH transmission gap as defined in subclause 6C.2, in which case it is not known to be present. When $\text{DL\_DCH\_FET\_Config}$ is configured, a TPC command is also required to be transmitted on the first slot of a downlink radio frame, when the corresponding uplink radio frame is transmitted after a transmission gap. + +Upon reception of one or more TPC commands in a TPC command combining period, the UE shall derive a single TPC command, $\text{TPC\_cmd}$ , for each TPC command combining period in which a TPC command is known to be present, combining multiple TPC commands if more than one is received in a TPC command combining period. The TPC command combining period has a length of one slot, beginning at the downlink slot boundary for DPCH, and 512 chips after the downlink slot boundary for F-DPCH. + +The UE shall ignore any TPC commands received in an F-DPCH or DPCH slot starting during an uplink DPCCH slot which is in an uplink DPCCH transmission gap as defined in subclause 6C.2. When DL\_DCH\_FET\_Config is configured, the UE shall not ignore the TPC command received in the first DPCH slot of a downlink radio frame, when the corresponding uplink radio frame is transmitted after an uplink transmission gap. + +Further, in case of an uplink DPCCH transmission gap as defined in subclause 6C.2, the UE shall add together the values of TPC\_cmd derived from each TPC command combining period in which a TPC command is known to be present and is not ignored as described above and which cannot be applied before the uplink DPCCH transmission gap, and apply the resulting sum of TPC\_cmd values when the uplink DPCCH transmission resumes. + +Three algorithms shall be supported by the UE for deriving a TPC\_cmd. Which of these three algorithms is used is determined by a UE-specific higher-layer parameter, "PowerControlAlgorithm", and is under the control of the UTRAN. If "PowerControlAlgorithm" indicates "algorithm1", then the layer 1 parameter PCA shall take the value 1, if "PowerControlAlgorithm" indicates "algorithm2" then PCA shall take the value 2 and if "PowerControlAlgorithm" indicates "algorithm3" then PCA shall take the value 3. + +If PCA has the value 1, Algorithm 1, described in subclause 5.1.2.2.2, shall be used for processing TPC commands. + +If PCA has the value 2, Algorithm 2, described in subclause 5.1.2.2.3, shall be used for processing TPC commands unless UE\_DTX\_DRX\_Enabled is TRUE or DL\_DCH\_FET\_Config is configured, in which case Algorithm 1 shall be used for processing TPC commands. + +If PCA has the value 3, Algorithm 3, described in subclause 5.1.2.2.4, shall be used for processing TPC commands unless UE\_DTX\_DRX\_Enabled is TRUE, in which case Algorithm 1 shall be used for processing TPC commands. The Algorithm 3 can only be configured with the F-DPCH. + +The step size $\Delta_{\text{TPC}}$ is a layer 1 parameter which is derived from the UE-specific higher-layer parameter "TPC-StepSize" which is under the control of the UTRAN. If "TPC-StepSize" has the value "dB1", then the layer 1 parameter $\Delta_{\text{TPC}}$ shall take the value 1 dB and if "TPC-StepSize" has the value "dB2", then $\Delta_{\text{TPC}}$ shall take the value 2 dB. The parameter "TPC-StepSize" only applies to Algorithm 1 and Algorithm 3 as stated in [5]. For Algorithm 2 $\Delta_{\text{TPC}}$ shall always take the value 1 dB. + +The length of slot cycle $X$ in Algorithm 3 is a layer 1 parameter which is derived from higher layer parameter "Decimation Factor" which is under the control of the UTRAN. If "Decimation Factor" has the value "3-slot cycle", then the layer 1 parameter $X$ shall take the value 3 and if "Decimation Factor" has the value "5-slot cycle", then $X$ shall take the value 5. The parameter "Decimation Factor" only applies to Algorithm 3 as stated in [5]. If Algorithm 3 is configured, the TPC command is not known to be present in $X-1$ slots where the TPC command is not received. + +After deriving of the combined TPC command TPC\_cmd using one of the three supported algorithms, the UE shall adjust the transmit power of the uplink DPCCH with a step of $\Delta_{\text{DPCCH}}$ (in dB) which is given by: + +$$\Delta_{\text{DPCCH}} = \Delta_{\text{TPC}} \times \text{TPC\_cmd}.$$ + +###### 5.1.2.2.1.1 + +###### Out of synchronization handling + +After 160 ms after physical channel establishment (defined in [5]) or immediately on the secondary uplink frequency if DTX enhancements is configured, the UE shall independently control its transmitter on each activated uplink frequency according to a downlink DPCCH or F-DPCH quality criterion on the associated downlink frequency as follows: + +- If UL\_DTX\_Active is FALSE (see clause 6C), the UE shall stop transmitting on the associated uplink frequency when the UE estimates the DPCCH or F-DPCH quality over the last 160 ms period to be worse than a threshold $Q_{\text{out}}$ . If UL\_DTX\_Active is TRUE (see clause 6C) or if PCA has the value 3, the UE shall stop transmitting on the associated uplink frequency when the UE estimates the quality of the TPC fields of the F-DPCH from the serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH from the serving E-DCH cell (or secondary serving E-DCH cell) in case of E-DCH decoupling is configured and DPCCH2 is not configured over the last 240 slots in which the TPC symbols are known to be present to be worse than a threshold $Q_{\text{out}}$ . $Q_{\text{out}}$ is defined implicitly by the relevant tests in [7]. +- If UL\_DTX\_Active is FALSE (see clause 6C), the UE can start transmitting on the associated uplink frequency again when the UE estimates the DPCCH or F-DPCH quality over the last 160 ms period to be better than a threshold $Q_{\text{in}}$ . If UL\_DTX\_Active is TRUE (see clause 6C) or if PCA has the value 3, the UE can start transmitting on the associated uplink frequency again when the UE estimates the quality of the TPC fields of the F-DPCH from the serving HS-DSCH cell (or secondary serving HS-DSCH cell) or the quality of the TPC fields of the F-DPCH from the serving E-DCH cell (or secondary serving E-DCH cell) in case of E-DCH decoupling is + +configured and DPCCH2 is not configured over the last 240 slots in which the TPC symbols are known to be present to be better than a threshold $Q_{in}$ . $Q_{in}$ is defined implicitly by the relevant tests in [7]. When transmission is resumed, the power of the DPCCH shall be the same as when the UE transmitter was shut off. + +- If both DPCCH and F-DPCH are transmitted when DPCCH2 is configured, then the UE shall use the DPCCH for determination of the quality criterion. + +If higher layers indicate the usage of a post-verification period, the UE shall independently control its transmitter on each activated uplink frequency according to a downlink DPCCH or F-DPCH quality criterion on the associated downlink frequency as follows: + +- When the UE estimates the DPCCH or F-DPCH quality over the first 40 ms period of the first phase of the downlink synchronization status evaluation to be worse than a threshold $Q_{in}$ , the UE shall stop transmitting on the associated uplink frequency and consider post-verification failed. $Q_{in}$ is defined implicitly by the relevant tests in [7]. When the UE transmission is resumed, the transmission of the uplink DPCCH power control preamble shall start $N_{pcp}$ radio frames prior to the start of uplink DPDCH transmission, where $N_{pcp}$ is a higher layer parameter set by UTRAN [5]. + +In case F-DPCH is configured in the downlink, the F-DPCH quality criterion shall be estimated as explained in subclause 4.3.1.2. + +###### 5.1.2.2.1.2 TPC command generation on downlink during RL initialisation + +When commanded by higher layers the TPC commands sent on a downlink radio link from Node Bs that have not yet achieved uplink synchronization shall follow a pattern as follows: + +If higher layers indicate by "First RLS indicator" that the radio link is part of the first radio link set sent to the UE or if the radio link initialisation is caused by an HS-SCCH order to activate the secondary uplink frequency and the value 'n' obtained from the parameter "DL TPC pattern 01 count" passed by higher layers is different from 0 then : + +- the TPC pattern shall consist of n instances of the pair of TPC commands ("0", "1"), followed by one instance of TPC command "1", where ("0", "1") indicates the TPC commands to be transmitted in 2 consecutive slots in which the TPC symbols are known to be present, +- the TPC pattern continuously repeat but shall be forcibly re-started at the beginning of each frame where $CFN \bmod 4 = 0$ . + +else + +- The TPC pattern shall consist only of TPC commands "1". + +The TPC pattern shall terminate once uplink synchronization is achieved. + +###### 5.1.2.2.1.3 Initial uplink DPCCH power handling after discontinuous transmission for the activated secondary uplink frequency + +If the UE is configured with DTX enhancements, when a secondary uplink frequency is activated, the UE shall set the initial DPCCH power after a transmission gap for the secondary uplink frequency as follows: + +- If the DPCCH transmission gap on the secondary uplink frequency is greater than the *Inactivity\_Threshold\_for\_Reset\_DPCCH\_Power*, then the initial DPCCH transmit power after transmission gap on the secondary uplink frequency is computed (in dB) as: + +$$P_{DPCCH,2} = P_{DPCCH,1,filtered} + Secondary\_Power\_Offset\_After\_Gap$$ + +where the $P_{DPCCH,1,filtered}$ is the most recent filtered DPCCH power on the primary uplink frequency, which shall be updated on a per-slot basis according to the following: + +$$P_{DPCCH,1,filtered}(i) = (1 - \alpha) \cdot P_{DPCCH,1,filtered}(i - 1) + \alpha \cdot P_{DPCCH,1}(i)$$ + +where $P_{DPCCH,1}(i)$ denotes the primary uplink frequency DPCCH power in slot i. When there is no uplink DPCCH transmission on the primary frequency as defined in subclause 6C.2, the UE shall not update $P_{DPCCH,1,filtered}$ . The filter coefficient $\alpha$ is defined as $\alpha = 1/4^k$ , where k is an integer number which is set by higher layer. The parameters of *Inactivity\_Threshold\_for\_Reset\_DPCCH\_Power* and *Secondary\_Power\_Offset\_After\_Gap* are parameters signalled by the network as defined in [5]. The filtering on the primary frequency shall be started when the secondary uplink frequency is activated. + +- Otherwise, the initial DPCCH transmit power after the gap shall be set to the previous DPCCH power value used in the last slot before the transmission gap. + +##### 5.1.2.2.2 Algorithm 1 for processing TPC commands + +###### 5.1.2.2.2.1 Derivation of TPC\_cmd when only one TPC command is received in each slot + +When a UE is not in soft handover, only one TPC command will be received in each slot in which a TPC command is known to be present. In this case, the value of TPC\_cmd shall be derived as follows: + +- If the received TPC command is equal to 0 then TPC\_cmd for that slot is -1. +- If the received TPC command is equal to 1, then TPC\_cmd for that slot is 1. + +###### 5.1.2.2.2.2 Combining of TPC commands from radio links of the same radio link set + +When a UE is in soft handover, multiple TPC commands may be received in each slot in which a TPC command is known to be present from different cells in the active set. In some cases, the UE has the knowledge that some of the transmitted TPC commands in a TPC command combining period are the same. This is the case when the radio links are in the same radio link set. For these cases, the TPC commands from the same radio link set in the same TPC command combining period shall be combined into one TPC command, to be further combined with other TPC commands as described in subclause 5.1.2.2.2.3. + +###### 5.1.2.2.2.3 Combining of TPC commands from radio links of different radio link sets + +This subclause describes the general scheme for combination of the TPC commands associated with the uplink DPCCH from radio links of different radio link sets and for which the TPC command is transmitted. + +First, the UE shall for each TPC command combining period conduct a soft symbol decision $W_i$ on each of the power control commands $TPC_i$ , where $i = 1, 2, \dots, N$ , where $N$ is greater than 1 and is the number of TPC commands from radio links of different radio link sets, that may be the result of a first phase of combination according to subclause 5.1.2.2.2.2. + +Finally, the UE derives a combined TPC command, TPC\_cmd, as a function $\gamma$ of all the $N$ soft symbol decisions $W_i$ : + +- $TPC\_cmd = \gamma(W_1, W_2, \dots, W_N)$ , where TPC\_cmd can take the values 1 or -1. + +The function $\gamma$ shall fulfil the following criteria: + +If the $N$ $TPC_i$ commands are random and uncorrelated, with equal probability of being transmitted as "0" or "1", the probability that the output of $\gamma$ is equal to 1 shall be greater than or equal to $1/(2^N)$ , and the probability that the output of $\gamma$ is equal to -1 shall be greater than or equal to 0.5. Further, the output of $\gamma$ shall equal 1 if the TPC commands from all the radio link sets, that are not ignored according to subclause 5.1.2.2.1 or 5.1.2.3 are reliably "1", and the output of $\gamma$ shall equal -1 if a TPC command from any of the radio link sets, that are not ignored according to subclause 5.1.2.2.1 or 5.1.2.3 is reliably "0". + +##### 5.1.2.2.3 Algorithm 2 for processing TPC commands + +NOTE: Algorithm 2 makes it possible to emulate smaller step sizes than the minimum power control step specified in subclause 5.1.2.2.1, or to turn off uplink power control by transmitting an alternating series of TPC commands. + +###### 5.1.2.2.3.1 Derivation of TPC\_cmd when only one TPC command is received in each slot + +When a UE is not in soft handover, only one TPC command will be received in each slot. In this case, the UE shall process received TPC commands on a 5-slot cycle, where the sets of 5 slots shall be aligned to the frame boundaries and there shall be no overlap between each set of 5 slots. + +The value of TPC\_cmd shall be derived as follows: + +- For the first 4 slots of a set, TPC\_cmd = 0. +- For the fifth slot of a set, the UE uses hard decisions on each of the 5 received TPC commands as follows: + - If all 5 hard decisions within a set are 1 then TPC\_cmd = 1 in the 5th slot. + +- If all 5 hard decisions within a set are 0 then $TPC\_cmd = -1$ in the 5th slot. +- Otherwise, $TPC\_cmd = 0$ in the 5th slot. + +###### 5.1.2.2.3.2 Combining of TPC commands from radio links of the same radio link set + +When a UE is in soft handover, multiple TPC commands may be received in each slot from different cells in the active set. In some cases, the UE has the knowledge that some of the transmitted TPC commands in a TPC command combining period are the same. This is the case when the radio links are in the same radio link set. For these cases, the TPC commands from radio links of the same radio link set in the same TPC command combining period shall be combined into one TPC command, to be processed and further combined with any other TPC commands as described in subclause 5.1.2.2.3.3. + +###### 5.1.2.2.3.3 Combining of TPC commands from radio links of different radio link sets + +This subclause describes the general scheme for combination of the TPC commands from radio links of different radio link sets. + +The UE shall make a hard decision on the value of each $TPC_i$ , where $i = 1, 2, \dots, N$ and $N$ is the number of TPC commands from radio links of different radio link sets, that may be the result of a first phase of combination according to subclause 5.1.2.2.3.2. + +The UE shall follow this procedure for 5 consecutive TPC command combining periods, resulting in $N$ hard decisions for each of the 5 TPC command combining periods. + +The sets of 5 TPC command combining periods shall for DPCH be aligned to the frame boundaries and for F-DPCH be aligned to 512 chips offset from the frame boundaries, and there shall be no overlap between each set of 5 TPC command combining periods. + +The value of $TPC\_cmd$ is zero for the first 4 TPC command combining periods. After 5 TPC command combining periods have elapsed, the UE shall determine the value of $TPC\_cmd$ for the fifth TPC command combining period in the following way: + +The UE first determines one temporary TPC command, $TPC\_temp_i$ , for each of the $N$ sets of 5 TPC commands as follows: + +- If all 5 hard decisions within a set are "1", $TPC\_temp_i = 1$ . +- If all 5 hard decisions within a set are "0", $TPC\_temp_i = -1$ . +- Otherwise, $TPC\_temp_i = 0$ . + +Finally, the UE derives a combined TPC command for the fifth TPC command combining period, $TPC\_cmd$ , as a function $\gamma$ of all the $N$ temporary power control commands $TPC\_temp_i$ : + +$TPC\_cmd(5^{\text{th}} \text{ TPC command combining period}) = \gamma (TPC\_temp_1, TPC\_temp_2, \dots, TPC\_temp_N)$ , where $TPC\_cmd(5^{\text{th}} \text{ TPC command combining period})$ can take the values 1, 0 or -1, and $\gamma$ is given by the following definition: + +- $TPC\_cmd$ is set to -1 if any of $TPC\_temp_1$ to $TPC\_temp_N$ are equal to -1. +- Otherwise, $TPC\_cmd$ is set to 1 if $\frac{1}{N} \sum_{i=1}^N TPC\_temp_i > 0.5$ . +- Otherwise, $TPC\_cmd$ is set to 0. + +##### 5.1.2.2.4 Algorithm 3 for processing TPC commands + +###### 5.1.2.2.4.1 Derivation of $TPC\_cmd$ when only one TPC command is received in each slot cycle + +When a UE is not in soft handover, only one TPC command will be received in each slot cycle, where the sets of $X$ slots shall be aligned to the frame boundaries and there shall be no overlap between each set of $X$ slots. + +In the initial radio link configuration, within each slot cycle, the UE receives one TPC command in the first F-DPCH slot with one of the slot formats from #1 to #8 or in the second F-DPCH slot with one of the slot formats #9 and #0. + +If it is not the initial radio link configuration, within each slot cycle, if the slot position or the slot format is not indicated by higher layers, there is no change in the F-DPCH slot position or slot format where the UE receives the TPC command. Otherwise the UE receives one TPC command in the F-DPCH slot position and slot format which is indicated by higher layers. + +In this case, the value of TPC\_cmd shall be derived as follows: + +- If the received TPC command is equal to 0 then TPC\_cmd for that slot is -1. +- If the received TPC command is equal to 1, then TPC\_cmd for that slot is 1. +- In the slots when no TPC command is received, TPC\_cmd = 0. + +###### 5.1.2.2.4.2 Combining of TPC commands from radio links of the same radio link set + +When a UE is in soft handover, multiple TPC commands may be received in each slot cycle in which a TPC command is known to be present from different cells in the active set. In some cases, the UE has the knowledge that some of the transmitted TPC commands in a TPC command combining period are the same. This is the case when the radio links are in the same radio link set. + +Within each slot cycle, the UE receives one TPC command in the F-DPCH slot which may be indicated by higher layers with any slot formats. + +There is only one TPC combining period associated to Algorithm 3 in each slot cycle. The TPC combining period is determined by the TPC symbol position of the existing radio link configured with Algorithm 3. + +When a new radio link configured with Algorithm 3 is added, the UE receives the TPC command of the new radio link in the existing TPC combining period. The existing TPC combining period is determined by the TPC symbol position of the existing radio link configured with Algorithm 3. + +For these cases, the TPC commands from the same radio link set in the same TPC command combining period shall be combined into one TPC command, to be further combined with other TPC commands as described in subclause 5.1.2.2.4.3. + +###### 5.1.2.2.4.3 Combining of TPC commands from radio links of different radio link sets + +This subclause describes the general scheme for combination of the TPC commands associated with the uplink DPCCH from radio links of different radio link sets where at least one radio link is configured with Algorithm 3 and for which the TPC command is transmitted. For the radio link configured with Algorithm 3, within each slot cycle, the UE receives one TPC command in the F-DPCH slot which may be indicated by higher layers with any slot format. + +There is only one TPC combining period associated to Algorithm 3 in each slot cycle. The TPC combining period is determined by the TPC symbol position of the existing radio link configured with Algorithm 3. + +When a new radio link configured with Algorithm 3 is added, the UE receives the TPC command of the new radio link in the existing TPC combining period. The existing TPC combining period is determined by the TPC symbol position of the existing radio link configured with Algorithm 3. + +First, in the TPC command combining period associated to Algorithm 3, the UE shall conduct a soft symbol decision $W_i$ on each of the power control commands $TPC_i$ , where $i = 1, 2, \dots, N$ , where $N$ is greater than 1 and is the number of TPC commands from radio links of different radio link sets, that may be the result of a first phase of combination according to subclause 5.1.2.2.4.2. + +Finally, the value of TPC\_cmd is 0 for the TPC command combining period not associated to Algorithm 3, while for the TPC command combining period associated to Algorithm 3, the UE derives a combined TPC command, TPC\_cmd, as a function $\gamma$ of all the $N$ soft symbol decisions $W_i$ : + +- $TPC\_cmd = \gamma(W_1, W_2, \dots, W_N)$ , where TPC\_cmd can take the values 1 or -1. + +The function $\gamma$ shall fulfil the following criteria: + +If the $N$ $TPC_i$ commands are random and uncorrelated, with equal probability of being transmitted as "0" or "1", the probability that the output of $\gamma$ is equal to 1 shall be greater than or equal to $1/(2^N)$ , and the probability that the output of $\gamma$ is equal to -1 shall be greater than or equal to 0.5. Further, the output of $\gamma$ shall equal 1 if the TPC commands from all + +the radio link sets, that are not ignored according to subclause 5.1.2.2.1 or 5.1.2.3 are reliably "1", and the output of $\gamma$ shall equal $-1$ if a TPC command from any of the radio link sets, that are not ignored according to subclause 5.1.2.2.1 or 5.1.2.3 is reliably "0". + +#### 5.1.2.2A Ordinary transmit power control for DPCCH2 + +For the primary uplink frequency, the uplink inner-loop power control for DPCCH2 adjusts the uplink DPCCH2 transmit power in order to maintain reliable reception of DPCCH2. + +The HS-DSCH serving cell in the active set monitors the DPCCH2 quality and provides TPC commands to adjust the uplink DPCCH2 transmit power. To increase the UE transmit power of DPCCH2 the TPC command to transmit is "1", and to decrease the power the TPC command to transmit is "0". + +The TPC command associated with DPCCH2 is not required to be transmitted in any downlink slot starting during an uplink DPCCH2 slot in which the DPCCH2 is not transmitted. + +Algorithm 1 as described in subclause 5.1.2.2.2.1, shall be used for processing TPC commands associated with DPCCH2, i.e. only one TPC command is received in each slot from the HS-DSCH serving cell. + +After deriving the TPC command $TPC\_cmd$ associated with DPCCH2, the UE shall adjust the transmit power of the uplink DPCCH2 with a step of $\Delta_{DPCCH2}$ (in dB) which is given by: + +$$\Delta_{DPCCH2} = \Delta_{TPC} \times TPC\_cmd,$$ + +where $\Delta_{TPC}$ is 1 dB. + +#### 5.1.2.3 Transmit power control in compressed mode + +NOTE: "Transmission gaps" correspond to transmission gaps created as a result of compressed mode. Another type of transmission gap may exist if DPCCH discontinuous transmission is applied (as described in clause 6C), however these gaps are named "uplink DPCCH transmission gaps". + +In compressed mode, one or more transmission gap pattern sequences are active. Therefore some frames are compressed and contain transmission gaps. The uplink power control procedure is as specified in subclause 5.1.2.2, using the same UTRAN supplied parameters for Power Control Algorithm and step size ( $\Delta_{TPC}$ ), but with additional features which aim to recover as rapidly as possible a signal-to-interference ratio (SIR) close to the target SIR after each transmission gap. + +The cells in the active set should estimate signal-to-interference ratio $SIR_{est}$ of the received uplink DPCH. The cells in the active set should then generate TPC commands and transmit the commands once per slot, except during downlink transmission gaps, according to the following rule: if $SIR_{est} > SIR_{cm\_target}$ then the TPC command to transmit is "0", while if $SIR_{est} < SIR_{cm\_target}$ then the TPC command to transmit is "1". + +$SIR_{cm\_target}$ is the target SIR during compressed mode and fulfils + +$$SIR_{cm\_target} = SIR_{target} + \Delta SIR_{PILOT} + \Delta SIR1\_coding + \Delta SIR2\_coding,$$ + +where $\Delta SIR1\_coding$ and $\Delta SIR2\_coding$ are computed from uplink parameters $\Delta SIR1$ , $\Delta SIR2$ , $\Delta SIRafter1$ , $\Delta SIRafter2$ signalled by higher layers as: + +- $\Delta SIR1\_coding = \Delta SIR1$ if the start of the first transmission gap in the transmission gap pattern is within the current uplink frame and $UE\_DTX\_DRX\_Enabled$ is FALSE for the UE. +- $\Delta SIR1\_coding = \Delta SIRafter1$ if the current uplink frame just follows a frame containing the start of the first transmission gap in the transmission gap pattern and $UE\_DTX\_DRX\_Enabled$ is FALSE for the UE. +- $\Delta SIR2\_coding = \Delta SIR2$ if the start of the second transmission gap in the transmission gap pattern is within the current uplink frame and $UE\_DTX\_DRX\_Enabled$ is FALSE for the UE. +- $\Delta SIR2\_coding = \Delta SIRafter2$ if the current uplink frame just follows a frame containing the start of the second transmission gap in the transmission gap pattern and $UE\_DTX\_DRX\_Enabled$ is FALSE for the UE. +- $\Delta SIR1\_coding = 0$ dB and $\Delta SIR2\_coding = 0$ dB in all other cases. + +$\Delta SIR_{PILOT}$ is defined as: $\Delta SIR_{PILOT} = 10 \log_{10} (N_{pilot,N} / N_{pilot,curr\_frame})$ , + +where $N_{pilot,curr\_frame}$ is the number of pilot bits per slot in the current uplink frame, and $N_{pilot,N}$ is the number of pilot bits per slot in a normal uplink frame without a transmission gap. + +In the case of several compressed mode pattern sequences being used simultaneously, $\Delta SIR1\_coding$ and $\Delta SIR2\_coding$ offsets are computed for each compressed mode pattern and all $\Delta SIR1\_coding$ and $\Delta SIR2\_coding$ offsets are summed together. + +In compressed mode, compressed frames may occur in either the uplink or the downlink or both. In uplink compressed frames, the transmission of uplink DPDCH(s), DPCCH and DPCH2 shall both be stopped during transmission gaps. + +Due to the transmission gaps in compressed frames, there may be missing TPC commands in the downlink. If no downlink TPC command is transmitted, the corresponding TPC\_cmd derived by the UE shall be set to zero. + +Compressed and non-compressed frames in the uplink DPCCH may have a different number of pilot bits per slot. A change in the transmit power of the uplink DPCCH would be needed in order to compensate for the change in the total pilot energy. Therefore at the start of each slot the UE shall derive the value of a power offset $\Delta PILOT$ . If the number of pilot bits per slot in the uplink DPCCH is different from its value in the most recently transmitted slot, $\Delta PILOT$ (in dB) shall be given by: + +$$\Delta PILOT = 10 \log_{10} (N_{pilot,prev}/N_{pilot,curr});$$ + +where $N_{pilot,prev}$ is the number of pilot bits in the most recently transmitted slot, and $N_{pilot,curr}$ is the number of pilot bits in the current slot. Otherwise, including during transmission gaps in the downlink, $\Delta PILOT$ shall be zero. + +Unless otherwise specified, in every slot during compressed mode the UE shall adjust the transmit power of the uplink DPCCH with a step of $\Delta DPCCH$ (in dB) which is given by: + +$$\Delta DPCCH = \Delta TPC \times TPC\_cmd + \Delta PILOT.$$ + +At the start of the first slot after an uplink or downlink transmission gap the UE shall apply a change in the transmit power of the uplink DPCCH by an amount $\Delta DPCCH$ (in dB), with respect to the uplink DPCCH power in the most recently transmitted uplink slot, where: + +$$\Delta DPCCH = \Delta RESUME + \Delta PILOT.$$ + +The value of $\Delta RESUME$ (in dB) shall be determined by the UE according to the Initial Transmit Power mode (ITP). The ITP is a UE specific parameter, which is signalled by the network with the other compressed mode parameters (see [4]). The different modes are summarised in table 1. + +**Table 1: Initial Transmit Power modes during compressed mode** + +| Initial Transmit Power mode | Description | +|-----------------------------|----------------------------------------------------| +| 0 | $\Delta RESUME = \Delta TPC \times TPC\_cmd_{gap}$ | +| 1 | $\Delta RESUME = \delta_{last}$ | + +If UE\_DTX\_DRX\_Enabled is TRUE, the UE shall behave as if the ITP mode is 0. + +In the case of a transmission gap in the uplink, TPC\_cmdgap shall be derived as follows: + +- If DPCH is configured in the downlink then TPC\_cmdgap shall be the value of TPC\_cmd derived in the first slot of the uplink transmission gap, if a downlink TPC\_command is transmitted in that slot. Otherwise TPC\_cmdgap shall be zero if no downlink TPC\_command is transmitted in that slot. +- If F-DPCH is configured in the downlink then TPC\_cmdgap shall be equal to the sum of the values of TPC\_cmd derived from each TPC command combining period in which a TPC command is known to be present and is not ignored as described below and which cannot be applied before the uplink transmission gap. The UE shall ignore any TPC commands received in an F-DPCH slot starting during an uplink DPCCH slot which is in an uplink transmission gap. In case there are no TPC commands to be summed TPC\_cmdgap shall be zero. + +$\delta_{last}$ shall be equal to the most recently computed value of $\delta_i$ . $\delta_i$ shall be updated according to the following recursive relations, which shall be executed in all slots in which both the uplink DPCCH and a downlink TPC command are transmitted, and in the first slot of an uplink transmission gap if a downlink TPC command is transmitted in that slot: + +$$\delta_i = 0.9375\delta_{i-1} - 0.96875\text{TPC}_{\text{cmd}_i}\Delta_{\text{TPC}}k_{\text{sc}}$$ + +$$\delta_{i-1} = \delta_i$$ + +where: $\text{TPC}_{\text{cmd}_i}$ is the power control command derived by the UE in that slot; + +$k_{\text{sc}} = 0$ if additional scaling is applied in the current slot and the previous slot as described in subclause 5.1.2.6, and $k_{\text{sc}} = 1$ otherwise. + +$\delta_{i-1}$ is the value of $\delta_i$ computed for the previous slot. The value of $\delta_{i-1}$ shall be initialised to zero when the uplink DPCCH is activated, and also at the end of the first slot after each uplink transmission gap, and also at the end of the first slot after each downlink transmission gap. The value of $\delta_i$ shall be set to zero at the end of the first slot after each uplink transmission gap. + +After a transmission gap in either the uplink or the downlink, the period following resumption of simultaneous uplink and downlink DPCCH or F-DPCH transmission is called a recovery period. RPL is the recovery period length and is expressed as a number of slots. RPL is equal to the minimum value out of the transmission gap length and 7 slots. If a transmission gap or an Uplink DPCCH burst pattern gap as defined in subclause 6C.2 is scheduled to start before RPL slots have elapsed, then the recovery period shall end at the start of the gap, and the value of RPL shall be reduced accordingly. + +During the recovery period, 2 modes are possible for the power control algorithm. The Recovery Period Power control mode (RPP) is signalled with the other compressed mode parameters (see [4]). The different modes are summarised in the table 2: + +**Table 2: Recovery Period Power control modes during compressed mode** + +| Recovery Period power control mode | Description | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Transmit power control is applied using the algorithm determined by the value of PCA, as in subclause 5.1.2.2 with step size $\Delta_{\text{TPC}}$ . | +| 1 | Transmit power control is applied using algorithm 1 (see subclause 5.1.2.2.2) with step size $\Delta_{\text{RP-TPC}}$ during RPL slots after each transmission gap. | + +If $\text{UE\_DTX\_DRX\_Enabled}$ is TRUE or if PCA has the value 3, the UE shall behave as if the RPP mode is 0. + +For RPP mode 0, the step size is not changed during the recovery period and ordinary transmit power control is applied (see subclause 5.1.2.2), using the algorithm for processing TPC commands determined by the value of PCA (see sub clauses 5.1.2.2.2, 5.1.2.2.3 and 5.1.2.2.4). + +For RPP mode 1, during RPL slots after each transmission gap, power control algorithm 1 is applied with a step size $\Delta_{\text{RP-TPC}}$ instead of $\Delta_{\text{TPC}}$ , regardless of the value of PCA. Therefore, the change in uplink DPCCH transmit power at the start of each of the RPL+1 slots immediately following the transmission gap (except for the first slot after the transmission gap) is given by: + +$$\Delta_{\text{DPCCH}} = \Delta_{\text{RP-TPC}} \times \text{TPC}_{\text{cmd}} + \Delta_{\text{PILOT}}$$ + +$\Delta_{\text{RP-TPC}}$ is called the recovery power control step size and is expressed in dB. If PCA has the value 1, $\Delta_{\text{RP-TPC}}$ is equal to the minimum value of 3 dB and $2\Delta_{\text{TPC}}$ . If PCA has the value 2, $\Delta_{\text{RP-TPC}}$ is equal to 1 dB. + +After the recovery period, ordinary transmit power control resumes using the algorithm specified by the value of PCA and with step size $\Delta_{\text{TPC}}$ . + +If PCA has the value 2, the sets of slots over which the TPC commands are processed shall remain aligned to the frame boundaries in the compressed frame. For both RPP mode 0 and RPP mode 1, if the transmission gap or the recovery period results in any incomplete sets of TPC commands, $\text{TPC}_{\text{cmd}}$ shall be zero for those sets of slots which are incomplete. + +#### 5.1.2.3A Transmit power control in compressed mode for DPCCH2 + +In compressed mode, one or more transmission gap pattern sequences are active. Therefore some frames are compressed and contain transmission gaps. The uplink power control procedure is as specified in subclause 5.1.2.2A, using the Algorithm 1 as described in subclause 5.1.2.2.2 and step size ( $\Delta_{\text{TPC}}$ ), but with additional features after each transmission gap. + +Due to the transmission gaps in compressed frames, there may be missing TPC commands in the downlink. If no downlink TPC command is transmitted, the corresponding TPC\_cmd derived by the UE shall be set to zero. + +At the start of the first slot after an uplink or downlink transmission gap the UE shall apply a change in the transmit power of the uplink DPCCH2 by an amount $\Delta_{\text{DPCCH2}}$ (in dB), with respect to the uplink DPCCH2 power in the most recently transmitted uplink slot, where: + +$$\Delta_{\text{DPCCH2}} = \Delta_{\text{RESUME2}}$$ + +The value of $\Delta_{\text{RESUME2}}$ (in dB) shall be determined by the UE according to the Initial Transmit Power mode (ITP) as described in 5.1.2.3. + +During the recovery period which is described in subclause 5.1.2.3, two modes are possible for the power control algorithm. + +For RPP mode 0, during RPL slots after each transmission gap, power control algorithm 1 is applied with a step size $\Delta_{\text{TPC}}$ (see subclause 5.1.2.2A). + +For RPP mode 1, during RPL slots after each transmission gap, power control algorithm 1 is applied with a step size $\Delta_{\text{RP-TPC}}$ instead of $\Delta_{\text{TPC}}$ . Therefore, the change in uplink DPCCH2 transmit power at the start of each of the RPL+1 slots immediately following the transmission gap (except for the first slot after the transmission gap) is given by: + +$$\Delta_{\text{DPCCH2}} = \Delta_{\text{RP-TPC}} \times \text{TPC\_cmd}$$ + +$\Delta_{\text{RP-TPC}}$ is called the recovery power control step size and is expressed in dB. $\Delta_{\text{RP-TPC}}$ is equal to $2\Delta_{\text{TPC}}$ . + +After the recovery period, transmit power control for DPCCH2 resumes using algorithm 1 and with step size $\Delta_{\text{TPC}}$ (see subclause 5.1.2.2A). + +#### 5.1.2.4 Transmit power control in the uplink DPCCH power control preamble + +An uplink DPCCH power control preamble is a period of uplink DPCCH transmission prior to the start of the uplink DPDCH transmission. The downlink DPCCH or F-DPCH shall also be transmitted during an uplink DPCCH power control preamble. + +The length of the uplink DPCCH power control preamble is a higher layer parameter signalled by the network as defined in [5]. The uplink DPDCH transmission shall commence after the end of the uplink DPCCH power control preamble. + +During the uplink DPCCH power control preamble the change in uplink DPCCH transmit power shall be given by: + +$$\Delta_{\text{DPCCH}} = \Delta_{\text{TPC}} \times \text{TPC\_cmd}$$ + +During the uplink DPCCH power control preamble TPC\_cmd is derived according to algorithm 1 as described in sub clause 5.1.2.2.1, if the value of PCA is 1 or 2. If the value of PCA is 3, TPC\_cmd is derived according to algorithm 3 as described in sub clause 5.1.2.2.4. + +Ordinary power control (see subclause 5.1.2.2), with the power control algorithm determined by the value of PCA and step size $\Delta_{\text{TPC}}$ , shall be used after the end of the uplink DPCCH power control preamble. + +#### 5.1.2.5 Setting of the uplink DPCCH/DPDCH relative powers + +##### 5.1.2.5.1 General + +The uplink DPCCH and DPDCH(s) are transmitted on different codes as defined in subclause 4.2.1 of [3]. In the case that at least one DPDCH is configured, the gain factors $\beta_c$ and $\beta_d$ may vary for each TFC. When UL DPCH\_10ms\_Mode is configured by higher layers for a given TFC, alternative $\beta_c$ and $\beta_d$ values determine the gain factors for DPDCH and DPCCH. There are two ways of controlling the gain factors of the DPCCH code and the DPDCH codes for different TFCs in normal (non-compressed) frames: + +- $\beta_c$ and $\beta_d$ are signalled for the TFC, or +- $\beta_c$ and $\beta_d$ is computed for the TFC, based on the signalled settings for a reference TFC. + +Combinations of the two above methods may be used to associate $\beta_c$ and $\beta_d$ values to all TFCs in the TFCS. The two methods are described in subclauses 5.1.2.5.2 and 5.1.2.5.3 respectively. Several reference TFCs may be signalled from higher layers. + +The gain factors may vary on radio frame basis depending on the current TFC used. Further, the setting of gain factors is independent of the inner loop power control. + +After applying the gain factors, the UE shall scale the total transmit power of the DPCCH and DPDCH(s), such that the DPCCH output power follows the changes required by the power control procedure with power adjustments of $\Delta_{\text{DPCCH}}$ dB, subject to the provisions of subclause 5.1.2.6. + +The gain factors during compressed frames are based on the nominal power relation defined in normal frames, as specified in subclause 5.1.2.5.4. + +##### 5.1.2.5.2 Signalled gain factors + +When the gain factors $\beta_c$ and $\beta_d$ are signalled by higher layers for a certain TFC, the signalled values are used directly for weighting of DPCCH and DPDCH(s). The variable $A_j$ , called the nominal power relation is then computed as: + +$$A_j = \frac{\beta_d}{\beta_c}.$$ + +##### 5.1.2.5.3 Computed gain factors + +The gain factors $\beta_c$ and $\beta_d$ may also be computed for certain TFCs, based on the signalled settings for a reference TFC. + +Let $\beta_{c,\text{ref}}$ and $\beta_{d,\text{ref}}$ denote the signalled gain factors for the reference TFC. Further, let $\beta_{c,j}$ and $\beta_{d,j}$ denote the gain factors used for the $j$ :th TFC. Also let $L_{\text{ref}}$ denote the number of DPDCHs used for the reference TFC and $L_j$ denote the number of DPDCHs used for the $j$ :th TFC. + +Define the variable + +$$K_{\text{ref}} = \sum_i \text{RM}_i \cdot N_i;$$ + +where $\text{RM}_i$ is the semi-static rate matching attribute for transport channel $i$ (defined in [2] subclause 4.2.7), $N_i$ is the number of bits output from the radio frame segmentation block for transport channel $i$ (defined in [2] subclause 4.2.6.1), and the sum is taken over all the transport channels $i$ in the reference TFC. + +Similarly, define the variable + +$$K_j = \sum_i \text{RM}_i \cdot N_i;$$ + +where the sum is taken over all the transport channels $i$ in the $j$ :th TFC. + +The variable $A_j$ , called the nominal power relation is then computed as: + +$$A_j = \frac{\beta_{d,\text{ref}}}{\beta_{c,\text{ref}}} \cdot \sqrt{\frac{L_{\text{ref}}}{L_j}} \sqrt{\frac{K_j}{K_{\text{ref}}}}.$$ + +The gain factors for the $j$ :th TFC are then computed as follows: + +- If $A_j > 1$ , then $\beta_{d,j} = 1.0$ and $\beta_{c,j}$ is the largest quantized $\beta$ -value, for which the condition $\beta_{c,j} \leq 1 / A_j$ holds. Since $\beta_{c,j}$ may not be set to zero, if the above rounding results in a zero value, $\beta_{c,j}$ shall be set to the lowest quantized amplitude ratio of 1/15 as specified in [3]. +- If $A_j \leq 1$ , then $\beta_{d,j}$ is the smallest quantized $\beta$ -value, for which the condition $\beta_{d,j} \geq A_j$ holds and $\beta_{c,j} = 1.0$ . + +The quantized $\beta$ -values are defined in [3] subclause 4.2.1, table 1. + +##### 5.1.2.5.4 Setting of the uplink DPCCH/DPDCH relative powers in compressed mode + +When UL\_DPCH\_10ms\_Mode is configured, the gain factors used during a compressed mode frame are the same as those used in a normal frame. For all other cases, the following procedure calculates the gain factors to be used in compressed mode frames. + +The gain factors used during a compressed frame for a certain TFC are calculated from the nominal power relation used in normal (non-compressed) frames for that TFC. Let $A_j$ denote the nominal power relation for the $j$ :th TFC in a normal frame. Further, let $\beta_{c,c,j}$ and $\beta_{d,c,j}$ denote the gain factors used for the $j$ :th TFC when the frame is compressed. The variable $A_{c,j}$ is computed as: + +$$A_{c,j} = A_j \cdot \sqrt{\frac{15 \cdot N_{pilot,C}}{N_{slots,C} \cdot N_{pilot,N}}};$$ + +where $N_{pilot,C}$ is the number of pilot bits per slot when in compressed mode, and $N_{pilot,N}$ is the number of pilot bits per slot in normal mode. $N_{slots,C}$ is the number of slots in the compressed frame used for transmitting the data. + +The gain factors for the $j$ :th TFC in a compressed frame are computed as follows: + +If $A_{c,j} > 1$ , then $\beta_{d,c,j} = 1.0$ and $\beta_{c,c,j}$ is the largest quantized $\beta$ -value, for which the condition $\beta_{c,c,j} \leq 1 / A_{c,j}$ holds. Since $\beta_{c,c,j}$ may not be set to zero, if the above rounding results in a zero value, $\beta_{c,c,j}$ shall be set to the lowest quantized amplitude ratio of 1/15 as specified in [3]. + +If $A_{c,j} \leq 1$ , then $\beta_{d,c,j}$ is the smallest quantized $\beta$ -value, for which the condition $\beta_{d,c,j} \geq A_{c,j}$ holds and $\beta_{c,c,j} = 1.0$ . + +The quantized $\beta$ -values are defined in [3] subclause 4.2.1, table 1. + +#### 5.1.2.5A Setting of the uplink HS-DPCCH power relative to DPCCH or DPCCH2 power + +When one or two HS-DPCCH are active, the values for $\Delta_{ACK}$ , $\Delta_{NACK}$ and $\Delta_{CQI}$ set by higher layers are translated to the quantized amplitude ratios $A_{hs}$ as specified in [3] subclause 4.2.1.2, and shall be set for each HS-DPCCH slot as follows. + +When only one activated cell's HARQ-ACK information is mapped to a HS-DPCCH, for each HS-DPCCH and each slot carrying HARQ Acknowledgement, the HS-DPCCH power settings are described in Table 2a. When more than one activated cell whose HARQ-ACK information are mapped to a specific HS-DPCCH, the HS-DPCCH power settings are described in Table 2b. When the UE is configured in Multiflow mode, the HARQ-ACK slot power settings of the HS-DPCCH are described in table 2b.1. + +**Table 2a: HARQ-ACK power offset setting when Secondary\_Cell\_Active is 0 or when Secondary\_Cell\_Enabled is more than 3 in case UE is not configured in MIMO mode with four transmit antennas in any cell, is more than 1 in case the UE is configured in MIMO mode with four transmit antennas in at least one cell and only HARQ-ACK information of one active downlink cell is mapped to either HS-DPCCH or HS-DPCCH2** + +| HARQ-ACK message sent in one time slot | $A_{hs}$ equals the quantized amplitude ratio translated from | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| ACK | $\Delta_{ACK}$ | +| NACK | $\Delta_{NACK}$ | +| PRE before single transport block or POST after a single transport block | $MAX(\Delta_{ACK}, \Delta_{NACK})$ | +| ACK/ACK | $\Delta_{ACK} + 1$ | +| NACK/NACK | $\Delta_{NACK} + 1$ | +| ACK/NACK or NACK/ACK or PRE before a dual transport block or POST after a dual transport block | $MAX(\Delta_{ACK} + 1, \Delta_{NACK} + 1)$ | + +**Table 2b: HARQ-ACK power offset setting when the HARQ-ACK information of more than one active downlink cell is mapped to either HS-DPCCH or HS-DPCCH2** + +| | Condition | $A_{hs}$ equals the quantized amplitude ratio translated from | +|--|-----------|---------------------------------------------------------------| +|--|-----------|---------------------------------------------------------------| + +| Number of active cells mapped to the HS-DPCCH or HS-DPCCH 2 | | Composite HARQ-ACK message(s) sent in one time slot | | | +|------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|---------------------------------------|-----------------------------------------------------| +| | | contains at least one ACK but no NACK | contains at least one NACK but no ACK | contains both ACK and NACK or is a PRE or is a POST | +| 2 | MIMO mode with four transmit antennas is not configured in any cell | $\Delta_{ACK} + 1$ | $\Delta_{NACK} + 1$ | $MAX(\Delta_{ACK} + 1, \Delta_{NACK} + 1)$ | +| 2 | MIMO mode with four transmit antennas is configured in at least one cell | $\Delta_{ACK} + 2$ | $\Delta_{NACK} + 2$ | $MAX(\Delta_{ACK} + 2, \Delta_{NACK} + 2)$ | +| 3 | Secondary_Cell_Enabled is 2 and MIMO or MIMO mode with four transmit antennas is not configured in any cell | $\Delta_{ACK} + 1$ | $\Delta_{NACK} + 1$ | $MAX(\Delta_{ACK} + 1, \Delta_{NACK} + 1)$ | +| 3 | Otherwise | $\Delta_{ACK} + 2$ | $\Delta_{NACK} + 2$ | $MAX(\Delta_{ACK} + 2, \Delta_{NACK} + 2)$ | +| 4 | | $\Delta_{ACK} + 2$ | $\Delta_{NACK} + 2$ | $MAX(\Delta_{ACK} + 2, \Delta_{NACK} + 2)$ | + +**Table 2b.1: HARQ-ACK power offset setting when the UE is configured in Multiflow mode** + +| Number of cells configured to the UE (Note 1) | Condition | A hs equals the quantized amplitude ratio translated from | | | +|-----------------------------------------------|--------------------------------------|----------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------| +| | | Composite HARQ-ACK message(s) sent in one time slot | | | +| | | contains at least one ACK but no NACK | contains at least one NACK but no ACK | contains both ACK and NACK or is a PRE or is a POST | +| 2 | | $\Delta_{ACK} + 1$ | $\Delta_{NACK} + 1$ | $MAX(\Delta_{ACK} + 1, \Delta_{NACK} + 1)$ | +| 3 | MIMO not configured in any cell | $\Delta_{ACK} + 1$ | $\Delta_{NACK} + 1$ | $MAX(\Delta_{ACK} + 1, \Delta_{NACK} + 1)$ | +| 3 | MIMO configured in at least one cell | $\Delta_{ACK} + 2$ | $\Delta_{NACK} + 2$ | $MAX(\Delta_{ACK} + 2, \Delta_{NACK} + 2)$ | +| 4 | | $\Delta_{ACK} + 2$ | $\Delta_{NACK} + 2$ | $MAX(\Delta_{ACK} + 2, \Delta_{NACK} + 2)$ | + +Note 1: When the UE is configured in the Multiflow mode, the cell deactivation with HS-SCCH orders do not impact the HARQ-ACK power offset used. + +For each HS-DPCCH and each slot carrying CQI, the HS-DPCCH power setting is described in Tables 2c and 2d: + +**Table 2c: CQI power offset setting when the UE is not in Multiflow mode** + +| Number of active cells mapped to HS-DPCCH or HS-DPCCH 2 | Condition | A hs equals the quantized amplitude ratio translated from | | +|--------------------------------------------------------------------|-----------|----------------------------------------------------------------------|------------------------------------------------------------------| +| | | MIMO or MIMO with four transmit antennas is not | MIMO or MIMO with four transmit antennas is configured in a cell | +| | | | | + +| | | configured in a cell | CQI of Type A | CQI of Type B | +|---------------|---------------------------------------------------------------------------------------------------------|----------------------|--------------------|--------------------| +| 1 | - | $\Delta_{CQI}$ | $\Delta_{CQI} + 1$ | $\Delta_{CQI}$ | +| 2 | Secondary_Cell_Enabled is 1, and MIMO or MIMO with four transmit antennas is not configured in any cell | $\Delta_{CQI} + 1$ | N/A | N/A | +| 2 | Otherwise | $\Delta_{CQI}$ | $\Delta_{CQI} + 1$ | $\Delta_{CQI}$ | +| 3
(Note 1) | Secondary_Cell_Enabled is 2 and MIMO is not configured in any cell | $\Delta_{CQI}$ | N/A | N/A | +| 3
(Note 2) | | $\Delta_{CQI} + 1$ | N/A | N/A | +| 3 | Otherwise | $\Delta_{CQI} + 1$ | $\Delta_{CQI} + 2$ | $\Delta_{CQI} + 1$ | +| 4 | | $\Delta_{CQI} + 1$ | $\Delta_{CQI} + 2$ | $\Delta_{CQI} + 1$ | + +Note 1: When the UE transmits a CQI report for the serving HS-DSCH cell in a subframe +Note 2: When the UE transmits a composite CQI report for 1st and 2nd secondary serving HS-DSCH cells in a subframe. + +**Table 2d: CQI power offset setting when the UE is in Multiflow mode** + +| Number of cells configured to the UE (Note 1) | MIMO configured in at least one cell | $A_{hs}$ equals the quantized amplitude ratio translated from | | | +|-----------------------------------------------|--------------------------------------|---------------------------------------------------------------|------------------------------|--------------------| +| | | MIMO is not configured in a cell | MIMO is configured in a cell | | +| | | | CQI of Type A | CQI of Type B | +| 2 | No | $\Delta_{CQI} + 1$ | N/A | | +| 2 | Yes | $\Delta_{CQI}$ | $\Delta_{CQI} + 1$ | $\Delta_{CQI}$ | +| 3
(Note 2) | No | $\Delta_{CQI}$ | N/A | | +| 3
(Note 3) | | $\Delta_{CQI} + 1$ | | | +| 3 | Yes | $\Delta_{CQI} + 1$ | $\Delta_{CQI} + 2$ | $\Delta_{CQI} + 1$ | +| 4 | No | $\Delta_{CQI} + 1$ | N/A | | +| 4 | Yes | $\Delta_{CQI} + 1$ | $\Delta_{CQI} + 2$ | $\Delta_{CQI} + 1$ | + +Note 1: When the UE is configured in the Multiflow mode, the cell activations and deactivations with HS-SCCH orders do not impact the CQI power offsets used. +Note 2: When the UE transmits a CQI report for the cell group consisting of one cell only +Note 3: When the UE transmits a composite CQI report of the cell group consisting of two cells, or a CQI report of the remaining active cell if the secondary cell of this cell group was deactivated by a HS-SCCH order. + +When DPCCH2 is not configured the following applies: + +In non-compressed frames $\beta_{hs}$ , which is the gain factor defined in [3] subclause 4.2.1.2, is calculated according to + +$$\beta_{hs} = \beta_c \cdot A_{hs},$$ + +where $\beta_c$ value is signalled by higher-layer or calculated as described in subclause 5.1.2.5.2 or 5.1.2.5.3 if at least one DPDCH is configured. In case no DPDCH is configured, $\beta_c$ value is set as described in subclause 5.1.2.5C. + +With the exception of the start and end of compressed frames, any DPCCH power change shall not modify the power ratio between the DPCCH and the HS-DPCCH. The power ratio between the DPCCH and the HS-DPCCH during compressed DPCCH frames is described below. + +During the period between the start and end of a compressed DPCCH frame, when HS-DPCCH is transmitted, $\beta_{hs}$ is calculated according to + +$$\beta_{hs} = \beta_{c,C,j} \cdot A_{hs} \cdot \sqrt{\frac{N_{pilot,C}}{N_{pilot,N}}},$$ + +where $\beta_{c,C,j}$ is calculated as described in subclause 5.1.2.5.4 if at least one DPDCH is configured. In case no DPDCH is configured, $\beta_{c,C,j}$ value is set as described in subclause 5.1.2.5C. $N_{pilot,C}$ is the number of pilot bits per slot on the DPCCH in compressed frames, and $N_{pilot,N}$ is the number of pilot bits per slot in non-compressed frames. + +Thus the gain factor $\beta_{hs}$ varies depending on the current quantized amplitude ratio $A_{hs}$ and on whether the UL DPCCH is currently in a compressed frame. + +##### When DPCCH2 is configured the following applies: + +In both non-compressed and compressed frames $\beta_{hs}$ , which is the gain factor defined in [3] subclause 4.2.1.2, is calculated according to + +$$y^{(0)}(i) = x^{(0)}(i),$$ + +where $\beta_{e2}$ value is the gain factor of DPCCH2 defined in [3] subclause 4.2.1.7. + +#### 5.1.2.5B Setting of the uplink E-DPCCH and E-DPDCH powers relative to DPCCH power + +##### 5.1.2.5B.1 E-DPCCH/DPCCH when one transport block is transmitted on E-DCH + +The E-DPCCH gain factor computation depends on the transmitted E-TFC at a given TTI. + +In non compressed frames, if $E-TFCI_i$ is smaller than or equal to $E-TFCI_{ec,boost}$ , where $E-TFCI_i$ denotes the E-TFCI of the $i$ :th E-TFC, the E-DPCCH gain factor, $\beta_{ec}$ , which is defined in [3] subclause 4.2.1.3, is calculated according to + +$$\beta_{ec} = \beta_c \cdot A_{ec}$$ + +where $\beta_c$ value is signalled by higher-layers or calculated as described in subclause 5.1.2.5.2 or 5.1.2.5.3 if at least one DPDCH is configured. In case no DPDCH is configured, $\beta_c$ value is set as described in subclause 5.1.2.5C. $A_{ec}$ is defined in [3] subclause 4.2.1.3. The $E-TFCI_{ec,boost}$ value is signalled by higher layers. + +In non compressed frames if $E-TFCI_i$ is greater than $E-TFCI_{ec,boost}$ , the unquantized E-DPCCH gain factor for the $i$ :th E-TFC, $\beta_{ec,i,uq}$ , is calculated according to + +$$\beta_{ec,i,uq} = \beta_c \cdot \sqrt{\max \left( A_{ec}^2, \frac{\sum_{k=1}^{k_{max,i}} \left( \frac{\beta_{ed,i,k}}{\beta_c} \right)^2}{\frac{\Delta T_{2TP}}{10} \cdot 10} - 1 \right)}$$ + +where $\Delta T_{2TP}$ is signalled by higher layers and is defined in [3] subclause 4.2.1.3, $\beta_{ed,i,k}$ is the E-DPDCH gain factor for the $i$ :th E-TFC on the $k$ :th physical channel and $k_{max,i}$ is the number of physical channels used for the $i$ :th E-TFC. + +If $\beta_{ec,i,uq}$ is less than the smallest quantized value of Table 1B.0A in [3] subclause 4.2.1.3, then the E-DPCCH gain factor of $E-TFCI_i$ , $\beta_{ec,i}$ is set such that $\beta_{ec,i}/\beta_c$ is the smallest quantized value of Table 1B.0A in [3] subclause 4.2.1.3. Otherwise, $\beta_{ec,i}$ is selected from Table 1B.0A in [3] subclause 4.2.1.3, such that $20 \cdot \log_{10}(\beta_{ec,i}/\beta_c)$ is the nearest quantized value to $20 \cdot \log_{10}(\beta_{ec,i,uq}/\beta_c)$ . + +During compressed frames where the E-DCH TTI is 2msec, the E-DPCCH gain factor, $\beta_{ec}$ , which is defined in [3] subclause 4.2.1.3, is calculated according to: + +$$\beta_{ec} = \beta_{c,c,j} \cdot A_{ec} \cdot \sqrt{\frac{N_{pilot,C}}{N_{pilot,N}}} \text{ if } E-TFCI_i \text{ is smaller than or equal to } E-TFCI_{ec,boost}.$$ + +and according to + +$$\beta_{ec,i,uq} = \beta_{c,c,j} \cdot \sqrt{\max\left(A_{ec}^2, \frac{\sum_{k=1}^{k_{max,i}} \left(\frac{\beta_{ed,i,k}}{\beta_c}\right)^2}{10^{\frac{\Delta T2TP}{10}}} - 1}\right)} \cdot \sqrt{\frac{N_{pilot,C}}{N_{pilot,N}}} \text{ if } E-TFCI_i \text{ is greater than } E-TFCI_{ec,boost}.$$ + +where $\beta_{c,c,j}$ is calculated as described in subclause 5.1.2.5.4 if at least one DPDCH is configured. In case no DPDCH is configured, the $\beta_{c,c,j}$ value is set as described in subclause 5.1.2.5C. $\beta_{ed,i,k}$ is the E-DPDCH gain factor for the $i$ :th E-TFC on the $k$ :th physical channel in non-compressed frames. $N_{pilot,C}$ is the number of pilot bits per slot on the DPCCH in compressed frames, and $N_{pilot,N}$ is the number of pilot bits per slot in non-compressed frames. $N_{slots,C}$ is the number of non DTX slots in the compressed frame. + +During compressed frames and where the E-DCH TTI is 10msec, the E-DPCCH gain factor, $\beta_{ec}$ , which is defined in [3] subclause 4.2.1.3, is calculated according to: + +$$\beta_{ec} = \beta_{c,c,j} \cdot A_{ec} \cdot \sqrt{\frac{15 \cdot N_{pilot,C}}{N_{slots,C} \cdot N_{pilot,N}}} \text{ if } E-TFCI_i \text{ is smaller than or equal to } E-TFCI_{ec,boost}$$ + +and according to + +$$\beta_{ec,i,uq} = \beta_{c,c,j} \cdot \sqrt{\max\left(A_{ec}^2, \frac{\sum_{k=1}^{k_{max,i}} \left(\frac{\beta_{ed,i,k}}{\beta_c}\right)^2}{10^{\frac{\Delta T2TP}{10}}} - 1}\right)} \cdot \sqrt{\frac{15 \cdot N_{pilot,C}}{N_{slots,C} \cdot N_{pilot,N}}} \text{ if } E-TFCI_i \text{ is greater than } E-TFCI_{ec,boost}.$$ + +where, $N_{slots,C}$ is the number of non DTX slots in the compressed frame. + +##### 5.1.2.5B.1A E-DPCCH/DPCCH when two transport blocks are transmitted on E-DCH (rank-2) + +When UL\_MIMO\_Enabled is TRUE, and the UE is transmitting two transport blocks, the E-DPCCH/DPCCH power ratio is calculated according to the definitions in subclause 5.1.2.5B.1 assuming $E-TFCI_{ec,boost} = -1$ . + +##### 5.1.2.5B.2 E-DPDCH/DPCCH + +###### 5.1.2.5B.2.1 General + +The E-DPDCH gain factor, $\beta_{ed}$ , which is defined in [3] subclause 4.2.1.3, may take a different value for each E-TFC and HARQ offset. The gain factors for different E-TFCs and HARQ offsets are computed as described in subclause 5.1.2.5B.2.3 based on reference gain factor(s) $\beta_{ed,ref}$ of E-TFC(s) signalled as reference E-TFC(s). The $\beta_{ed,ref}$ are computed as described in subclause 5.1.2.5B.2.2. At least one E-TFC of the set of E-TFCs configured by the network shall be signalled as a reference E-TFC. + +The gain factors may vary on radio frame basis or sub-frame basis depending on the E-DCH TTI used. Further, the setting of gain factors is independent of the inner loop power control. + +###### 5.1.2.5B.2.2 Computation of reference gain factors + +Let $E-TFCI_{ref,m}$ denote the E-TFCI of the $m$ :th reference E-TFC, where $m=1,2,\dots,M$ and $M$ is the number of signalled reference E-TFCs and $E-TFCI_{ref,1} < E-TFCI_{ref,2} < \dots < E-TFCI_{ref,M}$ . + +For each reference E-TFC, a reference gain factor $\beta_{ed,ref}$ is calculated according to + +$$\beta_{ed,ref} = \beta_c \cdot A_{ed}$$ + +where $\beta_c$ value is signalled by higher-layer or calculated as described in subclause 5.1.2.5.2 or 5.1.2.5.3 if at least one DPDCH is configured. In case no DPDCH is configured, $\beta_c$ value is set as described in subclause 5.1.2.5C. $A_{ed}$ is defined in [3] subclause 4.2.1.3 table 1B.1 when the reference $E-TFCI_{ref,m}$ is smaller than or equal to $E-TFCI_{ec,boost}$ ; otherwise, $A_{ed}$ is defined in [3] subclause 4.2.1.3 table 1B.2A when reference $E-TFCI_{ref,m}$ is greater than $E-TFCI_{ec,boost}$ . + +###### 5.1.2.5B.2.3 Computation of gain factors + +The gain factor $\beta_{ed}$ of an E-TFC is computed based on the signalled settings for its corresponding reference E-TFC. + +Whether E-DPDCH power extrapolation formula or E-DPDCH power interpolation formula is used to compute the gain factor $\beta_{ed}$ is signalled by higher layers. + +Let $E-TFCI_i$ denote the E-TFCI of the $i$ :th E-TFC. + +For the $i$ :th E-TFC: + +If E-DPDCH power extrapolation formula is configured + +if $E-TFCI_i \geq E-TFCI_{ref,M}$ , the reference E-TFC is the $M$ :th reference E-TFC. + +if $E-TFCI_i < E-TFCI_{ref,1}$ , the reference E-TFC is the 1st reference E-TFC. + +if $E-TFCI_{ref,1} \leq E-TFCI_i < E-TFCI_{ref,M}$ , the reference E-TFC is the $m$ :th reference E-TFC such that $E-TFCI_{ref,m} \leq E-TFCI_i < E-TFCI_{ref,m+1}$ . + +Else If E-DPDCH power interpolation formula is configured + +if $E-TFCI_i \geq E-TFCI_{ref,M}$ , the primary and secondary reference E-TFCs are the $(M-1)$ :th and $M$ :th reference E-TFCs respectively. + +if $E-TFCI_i < E-TFCI_{ref,1}$ , the primary and secondary reference E-TFCs are the 1st and 2nd reference E-TFCs respectively. + +if $E-TFCI_{ref,1} \leq E-TFCI_i < E-TFCI_{ref,M}$ , the primary and secondary reference E-TFCs are the $m$ :th and $(m+1)$ :th reference E-TFCs respectively, such that $E-TFCI_{ref,m} \leq E-TFCI_i < E-TFCI_{ref,m+1}$ . + +When E-DPDCH power extrapolation formula is configured, let $\beta_{ed,ref}$ denote the reference gain factor of the reference E-TFC. Let $L_{e,ref}$ denote the number of E-DPDCHs used for the reference E-TFC and $L_{e,i}$ denote the number of E-DPDCHs used for the $i$ :th E-TFC. If SF2 is used, $L_{e,ref}$ and $L_{e,i}$ are the equivalent number of physical channels assuming SF4. Let $K_{e,ref}$ denote the transport block size of the reference E-TFC and $K_{e,i}$ denote the transport block size of the $i$ :th E-TFC, where the mapping between the E-TFCI and the E-DCH transport block size is defined in [9]. For the $i$ :th E-TFC, the temporary variable $\beta_{ed,i,harq}$ is then computed as: + +$$\beta_{ed,i,harq} = \beta_{ed,ref} \sqrt{\frac{L_{e,ref}}{L_{e,i}}} \sqrt{\frac{K_{e,i}}{K_{e,ref}}} \cdot 10^{\left(\frac{\Delta_{harq}}{20}\right)}$$ + +where the HARQ offset $\Delta_{harq}$ is defined in [3] subclause 4.2.1.3. + +When E-DPDCH power interpolation formula is configured, let $\beta_{ed,ref,1}$ and $\beta_{ed,ref,2}$ denote the reference gain factors of the primary and secondary reference E-TFCs respectively. Let $L_{e,ref,1}$ and $L_{e,ref,2}$ denote the number of E-DPDCHs used for the primary and secondary reference E-TFCs respectively. Let $L_{e,i}$ denotes the number of E-DPDCHs used for the $i$ :th E-TFC. If SF2 is used, $L_{e,ref,1}$ , $L_{e,ref,2}$ and $L_{e,i}$ are the equivalent number of physical channels assuming SF4. Let $K_{e,ref,1}$ and $K_{e,ref,2}$ denote the transport block sizes of the primary and secondary reference E-TFCs respectively. Let $K_{e,i}$ denotes the transport block size of the $i$ :th E-TFC, where the mapping between the E-TFCI and the E-DCH transport block size is defined in [9]. For the $i$ :th E-TFC, the temporary variable $\beta_{ed,i,harq}$ is computed as: + +$$\beta_{ed,i,harq} = \sqrt{\frac{L_{e,ref,1}}{L_{e,i}}} \cdot \sqrt{\left( \left( \frac{\frac{L_{e,ref,2}}{L_{e,ref,1}} \beta_{ed,ref,2}^2 - \beta_{ed,ref,1}^2}{K_{e,ref,2} - K_{e,ref,1}} \right) (K_{e,i} - K_{e,ref,1}) + \beta_{ed,ref,1}^2 \right)} \cdot 10^{\left(\frac{\Delta_{harq}}{20}\right)} \text{ with the exception that } \beta_{ed,i,harq} \text{ is set to 0 if } \left( \frac{\frac{L_{e,ref,2}}{L_{e,ref,1}} \beta_{ed,ref,2}^2 - \beta_{ed,ref,1}^2}{K_{e,ref,2} - K_{e,ref,1}} \right) (K_{e,i} - K_{e,ref,1}) + \beta_{ed,ref,1}^2 \leq 0.$$ + +For the $i$ :th E-TFC, the unquantized gain factor $\beta_{ed,k,i,uq}$ for the $k$ :th E-DPDCH (denoted E-DPDCH $_k$ in [3] subclause 4.2.1.3) shall be set to $\sqrt{2} \times \beta_{ed,i,harq}$ if the spreading factor for E-DPDCH $_k$ is 2 and to $\beta_{ed,i,harq}$ otherwise. + +The following applies: + +- For E-TFCI smaller than or equal to $E-TFCI_{ec,boost}$ , + - If $\beta_{ed,k,i,uq}/\beta_c$ is less than the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the largest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, for which the condition $\beta_{ed,k} \leq \beta_{ed,k,i,uq}$ holds. +- For E-TFCI greater than $E-TFCI_{ec,boost}$ , + - If $\beta_{ed,k,i,uq}/\beta_c$ is less than the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the largest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, for which the condition $\beta_{ed,k} \leq \beta_{ed,k,i,uq}$ holds. + +###### 5.1.2.5B.2.4 E-DPDCH/DPCCH adjustments relating to compressed mode + +The gain factor applied to E-DPDCH is adjusted as a result of compressed mode operation in the following cases: + +- E-DCH transmissions that overlap a compressed frame +- For 10msec E-DCH TTI case, retransmissions that do not themselves overlap a compressed frame, but for which the corresponding initial transmission overlapped a compressed frame. + +The gain factors used during a compressed frame for a certain E-TFC are calculated from the nominal power relation used in normal (non-compressed) frames for that E-TFC. When the frame is compressed, the gain factor used for the $i$ :th E-TFC is derived from $\beta_{ed,C,i}$ as described below. + +When the E-DCH TTI is 2msec, $\beta_{ed,C,i}$ shall be calculated as follows: + +If E-DPDCH power extrapolation formula is configured, + +$$\beta_{ed,C,i} = \beta_{c,C,j} \cdot A_{ed} \cdot \sqrt{\frac{L_{e,ref}}{L_{e,i}}} \cdot \sqrt{\frac{K_{e,i}}{K_{e,ref}}} \cdot 10^{\left(\frac{\Delta_{harq}}{20}\right)} \cdot \sqrt{\frac{N_{pilot,C}}{N_{pilot,N}}}$$ + +Else if E-DPDCH power interpolation formula is configured, + +$$\beta_{ed,C,i} = \beta_{c,C,j} \cdot \sqrt{\frac{L_{e,ref,1}}{L_{e,i}}} \cdot \sqrt{\left( \left( \frac{\frac{L_{e,ref,2}}{L_{e,ref,1}} A_{ed,2}^2 - A_{ed,1}^2}{K_{e,ref,2} - K_{e,ref,1}} \right) (K_{e,i} - K_{e,ref,1}) + A_{ed,1}^2 \right)} \cdot 10^{\left(\frac{\Delta_{harq}}{20}\right)} \cdot \sqrt{\frac{N_{pilot,C}}{N_{pilot,N}}}$$ + +with the exception that $\beta_{ed,C,i}$ is set to 0 if $\left( \frac{\frac{L_{e,ref,2}}{L_{e,ref,1}} A_{ed,2}^2 - A_{ed,1}^2}{K_{e,ref,2} - K_{e,ref,1}} \right) (K_{e,i} - K_{e,ref,1}) + A_{ed,1}^2 \leq 0$ + +where $\beta_{c,C,j}$ is calculated for the $j$ :th TFC as described in subclause 5.1.2.5.4 if at least one DPDCH is configured. In case no DPDCH is configured, the $\beta_{c,C,j}$ value is set as described in subclause 5.1.2.5C. $A_{ed}$ , $A_{ed,1}$ and $A_{ed,2}$ are as defined in [3] subclause 4.2.1.3. $A_{ed,1}$ and $A_{ed,2}$ denote the quantized amplitude ratios assigned to the primary and secondary reference E-TFCs respectively. + +$L_{e,ref}$ , $L_{e,i}$ , $K_{e,ref}$ , $K_{e,i}$ , $L_{e,ref,1}$ , $L_{e,ref,2}$ , $K_{e,ref,1}$ and $K_{e,ref,2}$ are as defined in subclause 5.1.2.5B.2.3, $\Delta_{harq}$ is as defined in [3] subclause 4.2.1.3, $N_{pilot,C}$ is the number of pilot bits per slot on the DPCCH in compressed frames, and $N_{pilot,N}$ is the number of pilot bits per slot in non-compressed frames. + +When the E-DCH TTI is 10msec and the current frame is compressed, $\beta_{ed,C,i}$ shall be calculated as follows: + +If E-DPDCH power extrapolation formula is configured + +$$\beta_{\text{ed},C,i} = \beta_{c,C,j} \cdot A_{\text{ed}} \cdot \sqrt{\frac{L_{e,\text{ref}}}{L_{e,I,i}}} \cdot \sqrt{\frac{K_{e,i}}{K_{e,\text{ref}}}} \cdot 10^{\left(\frac{\Delta_{\text{harq}}}{20}\right)} \cdot \sqrt{\frac{15 \cdot N_{\text{pilot},C}}{N_{\text{slots},I} \cdot N_{\text{pilot},N}}},$$ + +Else if E-DPDCH power interpolation formula is configured + +$$\beta_{\text{ed},C,i} = \beta_{c,C,j} \cdot \sqrt{\frac{L_{e,\text{ref},1}}{L_{e,I,i}}} \cdot \sqrt{\left( \left( \frac{\frac{L_{e,\text{ref},2}}{L_{e,\text{ref},1}} A_{\text{ed},2}^2 - A_{\text{ed},1}^2}{K_{e,\text{ref},2} - K_{e,\text{ref},1}} \right) (K_{e,i} - K_{e,\text{ref},1}) + A_{\text{ed},1}^2 \right)} \cdot 10^{\left(\frac{\Delta_{\text{harq}}}{20}\right)} \cdot \sqrt{\frac{15 \cdot N_{\text{pilot},C}}{N_{\text{slots},I} \cdot N_{\text{pilot},N}}}$$ + +with the exception that $\beta_{\text{ed},C,i}$ is set to 0 if $\left( \frac{\frac{L_{e,\text{ref},2}}{L_{e,\text{ref},1}} A_{\text{ed},2}^2 - A_{\text{ed},1}^2}{K_{e,\text{ref},2} - K_{e,\text{ref},1}} \right) (K_{e,i} - K_{e,\text{ref},1}) + A_{\text{ed},1}^2 \leq 0$ + +where $L_{e,I,i}$ denotes the number of E-DPDCHs used for the $i$ :th E-TFC in the first frame used for transmitting the data and $N_{\text{slots},I}$ is the number of non DTX slots in the first frame used for transmitting the data. + +For the $i$ :th E-TFC, the unquantized gain factor $\beta_{\text{ed},k,i,uq}$ for the $k$ :th E-DPDCH (denoted E-DPDCH $_k$ in [3] subclause 4.2.1.3) shall be set to $\sqrt{2} \times \beta_{\text{ed},C,i}$ if the spreading factor for E-DPDCH $_k$ is 2 and to $\beta_{\text{ed},C,i}$ otherwise. + +Quantization may be applied as follows: + +- For E-TFCI smaller than or equal to $E\text{-TFCI}_{\text{ec,boost}}$ , + - If $\beta_{\text{ed},k,i,uq}/\beta_{c,C,j}$ is less than the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{\text{ed},k}$ is set such that $\beta_{\text{ed},k}/\beta_{c,C,j}$ is the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{\text{ed},k}$ is set such that $\beta_{\text{ed},k}/\beta_{c,C,j}$ is the largest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, for which the condition $\beta_{\text{ed},k} \leq \beta_{\text{ed},k,i,uq}$ holds. +- For E-TFCI greater than $E\text{-TFCI}_{\text{ec,boost}}$ , + - If $\beta_{\text{ed},k,i,uq}/\beta_{c,C,j}$ is less than the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{\text{ed},k}$ is set such that $\beta_{\text{ed},k}/\beta_{c,C,j}$ is the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{\text{ed},k}$ is set such that $\beta_{\text{ed},k}/\beta_{c,C,j}$ is the largest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, for which the condition $\beta_{\text{ed},k} \leq \beta_{\text{ed},k,i,uq}$ holds. + +If quantization is not applied, $\beta_{\text{ed},k}$ shall be set to $\beta_{\text{ed},k,i,uq}$ . + +When the E-DCH TTI is 10msec and the current frame is not compressed, but is a retransmission for which the corresponding first transmission was compressed, the gain factor used for the $k$ :th E-DPDCH for the $i$ :th E-TFC is derived from $\beta_{\text{ed},R,i}$ as follows: + +If E-DPDCH power extrapolation formula is configured + +$$\beta_{\text{ed},R,i} = \beta_{\text{ed},\text{ref}} \sqrt{\frac{L_{e,\text{ref}}}{L_{e,I,i}}} \sqrt{\frac{K_{e,i}}{K_{e,\text{ref}}}} \sqrt{\frac{15}{N_{\text{slots},I}}} \cdot 10^{\left(\frac{\Delta_{\text{harq}}}{20}\right)}$$ + +Else if E-DPDCH power interpolation formula is configured + +$$\beta_{\text{ed},R,i} = \sqrt{\frac{L_{e,\text{ref},1}}{L_{e,I,i}}} \cdot \sqrt{\left( \left( \frac{\frac{L_{e,\text{ref},2}}{L_{e,\text{ref},1}} \beta_{\text{ed},\text{ref},2}^2 - \beta_{\text{ed},\text{ref},1}^2}{K_{e,\text{ref},2} - K_{e,\text{ref},1}} \right) (K_{e,i} - K_{e,\text{ref},1}) + \beta_{\text{ed},\text{ref},1}^2 \right)} \cdot \sqrt{\frac{15}{N_{\text{slots},I}}} \cdot 10^{\left(\frac{\Delta_{\text{harq}}}{20}\right)}$$ + +with the exception that $\beta_{ed,R,i}$ is set to 0 if $\left( \frac{\frac{L_{e,ref,2}}{L_{e,ref,1}} \beta_{ed,ref,2}^2 - \beta_{ed,ref,1}^2}{K_{e,ref,2} - K_{e,ref,1}} \right) (K_{e,i} - K_{e,ref,1}) + \beta_{ed,ref,1}^2 \leq 0$ + +where $\beta_{ed,ref}, \beta_{ed,ref,1}, \beta_{ed,ref,2}, L_{e,ref}, K_{e,ref}, K_{e,i}, L_{e,ref,1}, L_{e,ref,2}, K_{e,ref,1}$ and $K_{e,ref,2}$ are as defined in subclause 5.1.2.5B.2.3, $\Delta_{harq}$ is as defined in [3] subclause 4.2.1.3, and $L_{e,i}$ and $N_{slots,i}$ are as defined above. + +For the $i$ :th E-TFC, the unquantized gain factor $\beta_{ed,k,i,uq}$ for the $k$ :th E-DPDCH (denoted E-DPDCH $_k$ in [3] subclause 4.2.1.3) shall be set to $\sqrt{2} \times \beta_{ed,R,i}$ if the spreading factor for E-DPDCH $_k$ is 2 and to $\beta_{ed,R,i}$ otherwise. + +Quantization may be applied as follows: + +- For E-TFCI smaller than or equal to $E-TFCI_{ec,boost}$ , + - If $\beta_{ed,k,i,uq}/\beta_c$ is less than the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the largest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, for which the condition $\beta_{ed,k} \leq \beta_{ed,k,i,uq}$ holds. +- For E-TFCI greater than $E-TFCI_{ec,boost}$ , + - If $\beta_{ed,k,i,uq}/\beta_c$ is less than the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, then the gain factor of E-DPDCH $_k$ , $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the smallest quantized value of Table 1B.2B in [3] subclause 4.2.1.3. + - Otherwise, $\beta_{ed,k}$ is set such that $\beta_{ed,k}/\beta_c$ is the largest quantized value of Table 1B.2B in [3] subclause 4.2.1.3, for which the condition $\beta_{ed,k} \leq \beta_{ed,k,i,uq}$ holds. + +If quantization is not applied, $\beta_{ed,k}$ shall be set to $\beta_{ed,k,i,uq}$ . + +#### 5.1.2.5C Setting of the uplink DPCCH gain factor when no DPDCH is configured + +In the case that no DPDCH is configured, the gain factor $\beta_c$ is equal to 1. During a compressed frame, the gain factor $\beta_{c,C,j}$ is also equal to 1. + +#### 5.1.2.5D Setting of the uplink S-DPCCH power relative to DPCCH power + +##### 5.1.2.5D.1 Setting of the uplink S-DPCCH/DPCCH power ratio when less than two transport blocks are transmitted on E-DCH + +If UL\_CLTD\_Enabled is set to TRUE and UL\_CLTD\_Active is 1, or if UL\_MIMO\_Enabled is set to TRUE and UL\_CLTD\_Active is 1 and the UE is transmitting either one or zero transport blocks on E-DCH, the S-DPCCH gain factor, $\beta_{sc}$ , which is defined in [3] subclause 4.2.1.4, is calculated depending on the transmitted E-TFC at a given TTI. + +In non compressed frames, if no transmission on E-DCH is taking place, or if E-DCH transmission is taking place and E-TFCI $_i$ is smaller than or equal to $E-TFCI_{ec,boost}$ , where $E-TFCI_i$ denotes the E-TFCI of the $i$ :th E-TFC, $\beta_{sc}$ is calculated according to + +$$\beta_{sc} = \beta_c \cdot A_{sc}$$ + +Where the $\beta_c$ value is signalled by higher layers or calculated as described in subclause 5.1.2.5.2 or 5.1.2.5.3 if at least one DPDCH is configured. In the case that no DPDCH is configured, the $\beta_c$ value is set as described in subclause 5.1.2.5C. $A_{sc}$ is defined in [3] subclause 4.2.1.4 Table 1C.1. The $E-TFCI_{ec,boost}$ value is signalled by higher layers. + +In non compressed frames if $E-TFCI_i$ is greater than $E-TFCI_{ec,boost}$ , the unquantized S-DPCCH gain factor for the $i$ :th E-TFC, $\beta_{sc}$ is calculated according to + +$$y^{(1)}(i) = x^{(1)}(i)$$ + +where $\Delta_{TSP}$ is signalled by higher layers and is defined in [3] subclause 4.2.1.4, $\beta_{ed,i,k}$ is the E-DPDCH gain factor for the $i$ :th E-TFC on the $k$ :th physical channel and $k_{max,i}$ is the number of physical channels used for the $i$ :th E-TFC, and the quantization of $\beta_{sc,i,uq}$ follows the quantization according to the definition of $\beta_{ec}$ quantization in table 1B.0A of [3]. + +If $\beta_{sc,i,uq}$ is less than the smallest quantized value of Table 1B.0A in [3], then the S-DPCCH gain factor of $E-TFC_i$ , $\beta_{sc,i}$ is set such that $\beta_{sc,i}/\beta_c$ is the smallest quantized value of Table 1B.0A in [3]. Otherwise, $\beta_{sc,i}$ is selected from that table such that $20 \cdot \log_{10}(\beta_{sc,i}/\beta_c)$ is the nearest quantized value to $20 \cdot \log_{10}(\beta_{sc,i,uq}/\beta_c)$ . + +During the period between the start and end of a compressed DPCCH frame, when S-DPCCH is transmitted, $\beta_{sc}$ is calculated according to + +$$y^{(0)}(i) = x^{(0)}(i)$$ + +if no transmission on E-DCH is taking place, or $E-TFC_i$ is smaller than or equal to $E-TFC_{ec,boost}$ , + +and according to + +$$y^{(1)}(i) = \begin{cases} x^{(1)}(i), & i \text{ is odd} \\ x^{(2)}(i), & i \text{ is even} \end{cases}, \text{ if } E-TFC_i \text{ is greater than } E-TFC_{ec,boost}$$ + +where $\beta_{c,C,j}$ is calculated as described in subclause 5.1.2.5.4 if at least one DPDCH is configured. In case no DPDCH is configured, $\beta_{c,C,j}$ value is set as described in subclause 5.1.2.5C. $N_{pilot,C}$ is the number of pilot bits per slot on the DPCCH in compressed frames, and $N_{pilot,N}$ is the number of pilot bits per slot in non-compressed frames. + +##### 5.1.2.5D.2 Setting of the uplink S-DPCCH/DPCCH power ratio when two transport blocks are transmitted on E-DCH (rank-2) + +When two transport blocks are transmitted on uplink E-DCH, the S-DPCCH gain factor setting, $\beta_{sc}$ , is defined in [3] subclause 4.2.1.4.2. + +#### 5.1.2.5E Setting of the uplink S-E-DPCCH power relative to DPCCH power + +When two transport blocks are transmitted on uplink E-DCH, the S-E-DPCCH gain factor setting, $\beta_{sec}$ , is defined in [3] subclause 4.2.1.5. When one or zero transport blocks are transmitted on uplink E-DCH, the S-E-DPCCH is not transmitted. + +#### 5.1.2.5F Setting of the uplink S-E-DPDCH power relative to E-DPDCH power + +When two transport blocks are transmitted on uplink E-DCH, the S-E-DPDCH gain factor setting, $\beta_{sed}$ , is defined in [3] subclause 4.2.1.6. + +When only one or zero transport blocks are transmitted on uplink E-DCH, the S-E-DPDCH is not transmitted. + +#### 5.1.2.6 Maximum and minimum power limits + +When E-DCH is not configured, in the case that the total UE transmit power (after applying DPCCH and DPCCH2 power adjustments and gain factors) would exceed the maximum allowed value, the UE shall apply additional scaling to + +the total transmit power so that it is equal to the maximum allowed power. This additional scaling shall be such that the power ratio between DPCCH and DPDCH, between DPCCH and HS-DPCCH, or between DPCCH2 and HS-DPCCH if DPCCH2 is configured, and between DPCCH and S-DPCCH remains as required by subclause 5.1.2.5, 5.1.2.5A, and 5.1.2.5D. In addition, scaling to the transmit power shall be such that the power ratio between DPCCH and DPCCH2 remains fixed if DPCCH2 is configured. + +##### Single uplink frequency configured for E-DCH + +When E-DCH is configured on a single frequency or E-DCH is configured on multiple frequencies but Secondary\_EDCH\_Cell\_Active is 0, + +##### Single transport block transmission (no MIMO) + +- If the total UE transmit power (after applying DPCCH and DPCCH2 power adjustments and gain factors) would exceed the maximum allowed value, the UE shall firstly reduce all the E-DPDCH gain factors $\beta_{ed,k}$ by an equal scaling factor to respective values $\beta_{ed,k,reduced}$ so that the total transmit power would be equal to the maximum allowed power. +- Also if $E-TFCI_i$ is greater than $E-TFCI_{ec,boosts}$ , UE shall reduce only E-DPDCH gain factors to respective values $\beta_{ed,k,reduced}$ and E-DPCCH is transmitted using original $\beta_{ec}$ which is not recalculated according to the reduced E-DPDCH gain factors. +- After calculating the reduced E-DPDCH gain factors, if $E-TFCI_i$ is smaller than or equal to $E-TFCI_{ec,boosts}$ quantization according to table 1B.2 in [3] subclause 4.2.1.3 may be applied, or if $E-TFCI_i$ is greater than $E-TFCI_{ec,boosts}$ , quantization according to table 1B.2B in [3] subclause 4.2.1.3 may be applied, where each $\beta_{ed,k,reduced}$ is quantized such that $\beta_{ed,k}/\beta_c$ is the largest quantized value for which the condition $\beta_{ed,k} \leq \beta_{ed,k,reduced}$ holds. +- In case a DPDCH is transmitted, + - if any $\beta_{ed,k,reduced}/\beta_c$ is less than the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, DTX may be used on that E-DPDCH. If DTX is used on all E-DPDCHs then DTX is also used on E-DPCCH, else E-DPCCH is still transmitted using $\beta_{ec}$ . + - When the UE is configured with HS-DPCCH overhead reduction Type 1, if DTX is used on all the E-DPDCHs and on the E-DPCCH and the total UE transmit power still exceeds the maximum allowed value, UE shall reduce HS-DPCCH gain factors $\beta_{hs}$ to $\beta_{hs,reduced}$ in a slot in which CQI is transmitted so that the total transmit power would be equal to the maximum allowed power. If this slot contains the start of a CQI transmission, then CQI value 0 shall be transmitted instead of the computed CQI report. After calculating the reduced HS-DPCCH gain factors, quantization according to table 1A in [3] subclause 4.2.1.2 may be applied, where $\beta_{hs,reduced}$ is quantized such that $\beta_{hs}/\beta_c$ if DPCCH2 is not configured, or $\beta_{hs}/\beta_{c2}$ if DPCCH2 is configured, is the largest quantized value for which the condition $\beta_{hs} \leq \beta_{hs,reduced}$ holds. If any $\beta_{hs,reduced}/\beta_c$ when DPCCH2 is not configured, or any $\beta_{hs,reduced}/\beta_{c2}$ when DPCCH2 is configured, is less than the smallest quantized value of Table 1A in [3] subclause 4.2.1.2, DTX may be used on that CQI field of HS-DPCCH. +- In case no DPDCH is transmitted and regardless of the applied uplink modulation, if any $\beta_{ed,k,reduced}/\beta_c$ is less than $\beta_{ed,k,reduced,min}/\beta_c$ , that $\beta_{ed,k}$ shall be set to $\beta_{ed,k,min}$ such that $\beta_{ed,k,min}/\beta_c = \min(\beta_{ed,k,reduced,min}/\beta_c, \beta_{ed,k,original}/\beta_c)$ , where $\beta_{ed,k,original}$ denotes the E-DPDCH gain factor before reduction. + +##### Dual transport block transmission (MIMO) + +- Also if the UE is transmitting both a set of E-DPDCHs and a set of S-E-DPDCHs, the UE shall reduce all the E-DPDCH and S-E-DPDCH gain factors $\beta_{ed,k}$ and $\beta_{sed,k}$ by an equal scaling factor to respective values $\beta_{ed,k,reduced}$ and $\beta_{sed,k,reduced}$ so that the total transmit power would be equal to the maximum allowed power. +- After calculating the reduced E-DPDCH and S-E-DPDCH gain factors, quantization according to table 1B.2B in [3] subclause 4.2.1.3 may be applied, where each $\beta_{ed,k,reduced}$ is quantized such that $\beta_{ed,k}/\beta_c$ is the largest quantized value for which the condition $\beta_{ed,k} \leq \beta_{ed,k,reduced}$ holds, and $\beta_{sed,k,reduced}$ is set to the same value as the quantized $\beta_{ed,k,reduced}$ . +- if any $\beta_{ed,k,reduced}/\beta_c$ is less than $\beta_{ed,k,reduced,min}/\beta_c$ , that $\beta_{ed,k}$ shall be set to $\beta_{ed,k,min}$ such that $\beta_{ed,k,min}/\beta_c = \min(\beta_{ed,k,reduced,min}/\beta_c, \beta_{ed,k,original}/\beta_c)$ , where $\beta_{ed,k,original}$ denotes the E-DPDCH gain factor before reduction, + +- if any $\beta_{sed,k,reduced}/\beta_c$ is less than $\beta_{sed,k,reduced,min}/\beta_c$ , that $\beta_{sed,k}$ shall be set to $\beta_{sed,k,min}$ such that $\beta_{sed,k,min}/\beta_c = \min(\beta_{sed,k,reduced,min}/\beta_c, \beta_{sed,k,original}/\beta_c)$ , where $\beta_{sed,k,original}$ denotes the S-E-DPDCH gain factor before reduction, +- $\beta_{sed,k,reduced,min}$ is configurable by higher layers. + +##### Additional scaling rules applicable to both non-MIMO and MIMO transmissions + +- In the following cases, the UE shall then apply additional scaling to the total transmit power so that it is equal to the maximum allowed power: + - if a DPDCH is transmitted and the total UE transmit power would still exceed the maximum allowed value even though DTX is used on all E-DPDCHs and the E-DPCCH, and on the CQI field of HS-DPCCH if the UE is configured with HS-DPCCH overhead reduction Type 1. + - if no DPDCH is transmitted and the total UE transmit power would still exceed the maximum allowed value even though $\beta_{ed,k}$ is equal to $\beta_{ed,k,min}$ for all $k$ . +- Any additional scaling of the total transmit power as described above shall be such that the power ratio between DPCCH and DPDCH, on the CQI field between DPCCH and HS-DPCCH (if DTX is not used on CQI field of HS-DPCCH) or between DPCCH2 and HS-DPCCH (if DTX is not used on CQI field of HS-DPCCH and DPCCH2 is configured), on HARQ-ACK field between DPCCH and HS-DPCCH (if HARQ-ACK field is transmitted) or between DPCCH2 and HS-DPCCH (if HARQ-ACK field is transmitted and DPCCH2 is configured), between DPCCH and E-DPCCH if DTX is not used on E-DPCCH, and between DPCCH and S-DPCCH, remains as required by subclauses 5.1.2.5, 5.1.2.5A, 5.1.2.5B.1, and 5.1.2.5D, and such that the power ratio between each E-DPDCH and DPCCH remains as required by $\beta_{ed,k,min}/\beta_c$ if DTX is not used on E-DPDCH, and such that the power ratio between DPCCH and DPCCH2 remains fixed if DPCCH2 is configured. Any slot-level scaling of $\beta_{ed}$ , DTX of E-DPDCH, DTX of E-DPCCH or DTX of the CQI field of HS-DPCCH as described above is applied at layer 1 only and is transparent to higher layers. +- If the UE is transmitting both a set of E-DPDCHs and a set of S-E-DPDCHs, the UE shall reduce all the E-DPDCH and S-E-DPDCH gain factors $\beta_{ed,k}$ and $\beta_{sed,k}$ by an equal scaling factor to respective values $\beta_{ed,k,reduced}$ and $\beta_{sed,k,reduced}$ so that the total transmit power would be equal to the maximum allowed power and the rule that $\beta_{sed,k,reduced}$ is equal to $\beta_{sed,k,reduced}$ is always kept. + +##### Two uplink frequencies configured for E-DCH + +When Secondary\_EDCH\_Cell\_Active is 1, + +- If the total UE transmit power (after applying DPCCH and DPCCH2 power adjustments and gain factors) would exceed the maximum allowed value, the UE shall start by reducing all the E-DPDCH gain factors $\beta_{ed,k}$ on the frequency with highest DPCCH power by an equal scaling factor to respective values $\beta_{ed,k,reduced}$ so that the total transmit power would be equal to the maximum allowed power. +- Also if $E-TFCI_i$ is greater than $E-TFCI_{ec,boost}$ , UE shall reduce only E-DPDCH gain factors to respective values $\beta_{ed,k,reduced}$ and E-DPCCH is transmitted using original $\beta_{ec}$ which is not recalculated according to the reduced E-DPDCH gain factors. After calculating the reduced E-DPDCH gain factors, if $E-TFCI_i$ is smaller than or equal to $E-TFCI_{ec,boost}$ , quantization according to table 1B.2 in [3] subclause 4.2.1.3 may be applied, or if $E-TFCI_i$ is greater than $E-TFCI_{ec,boost}$ , quantization according to table 1B.2B in [3] subclause 4.2.1.3 may be applied, where each $\beta_{ed,k,reduced}$ is quantized such that $\beta_{ed,k}/\beta_c$ is the largest quantized value for which the condition $\beta_{ed,k} \leq \beta_{ed,k,reduced}$ holds. +- If $\beta_{ed,k,reduced}/\beta_c$ is less than $\beta_{ed,k,reduced,min}/\beta_c$ then $\beta_{ed,k}$ shall be set to $\beta_{ed,k,min}$ such that $\beta_{ed,k,min}/\beta_c = \min(\beta_{ed,k,reduced,min}/\beta_c, \beta_{ed,k,original}/\beta_c)$ , where $\beta_{ed,k,original}$ denotes the E-DPDCH gain factor before reduction and $\beta_{ed,k,reduced,min}$ is individually configured by higher layers for each frequency. +- The UE shall then apply the same procedure on the uplink frequency with second highest DPCCH power. +- If $\beta_{ed,k,min}/\beta_c = \min(\beta_{ed,k,reduced,min}/\beta_c, \beta_{ed,k,original}/\beta_c)$ for all activated uplink frequencies, then + - In case a DPDCH is transmitted, + +- if any $\beta_{ed,k,reduced}/\beta_c$ is less than the smallest quantized value of Table 1B.2 in [3] subclause 4.2.1.3, DTX may be used on that E-DPDCH on the frequency with highest DPCCH power. If DTX is used on all E-DPDCHs on the frequency with highest DPCCH power then DTX is also used on E-DPCCH on the frequency with highest DPCCH power, else E-DPCCH is still transmitted using $\beta_{ec}$ . +- The UE shall then apply the same procedure on the uplink frequency with second highest DPCCH power. +- When the UE is configured with HS-DPCCH overhead reduction Type 1, if DTX is used on all the E-DPDCHs and on the E-DPCCH and the total UE transmit power still exceeds the maximum allowed value, UE shall reduce HS-DPCCH gain factors $\beta_{hs}$ to $\beta_{hs,reduced}$ in a slot in which CQI is transmitted so that the total transmit power would be equal to the maximum allowed power. If this slot contains the start of a CQI transmission, then CQI value 0 shall be transmitted instead of the computed CQI report. After calculating the reduced HS-DPCCH gain factors, quantization according to table 1A in [3] subclause 4.2.1.2 may be applied, where $\beta_{hs,reduced}$ is quantized such that $\beta_{hs}/\beta_c$ if DPCCH2 is not configured, or $\beta_{hs}/\beta_{c2}$ if DPCCH2 is configured, is the largest quantized value for which the condition $\beta_{hs} \leq \beta_{hs,reduced}$ holds. If any $\beta_{hs,reduced}/\beta_c$ when DPCCH2 is not configured, or any $\beta_{hs,reduced}/\beta_{c2}$ when DPCCH2 is configured, is less than the smallest quantized value of Table 1A in [3] subclause 4.2.1.2, DTX may be used on that CQI field of HS-DPCCH. +- Any additional scaling of the total transmit power shall be such that: + - if the total UE transmit power would still exceed the maximum allowed value even though DTX is used on all E-DPDCHs and the E-DPCCH, and on the CQI field of HS-DPCCH if the UE is configured with HS-DPCCH overhead reduction Type 1. + - Any additional scaling of the total transmit power as described above shall be such that the power ratio between DPCCH and DPDCH, on the CQI field between DPCCH and HS-DPCCH (if DTX is not used on CQI field of HS-DPCCH) or between DPCCH2 and HS-DPCCH (if DTX is not used on CQI field of HS-DPCCH and DPCCH2 is configured), on HARQ-ACK field between DPCCH and HS-DPCCH (if HARQ-ACK field is transmitted) or between DPCCH2 and HS-DPCCH (if HARQ-ACK field is transmitted and DPCCH2 is configured), between DPCCH and E-DPCCH if DTX is not used on E-DPCCH, and between DPCCH and S-DPCCH, remains as required by subclauses 5.1.2.5, 5.1.2.5A, 5.1.2.5B.1, and 5.1.2.5D, and such that the power ratio between each E-DPDCH and DPCCH remains as required by $\beta_{ed,k,min}/\beta_c$ if DTX is not used on E-DPDCH, and such that the power ratio between DPCCH and DPCCH2 remains fixed if DPCCH2 is configured. Any slot-level scaling of $\beta_{ed}$ , DTX of E-DPDCH, DTX of E-DPCCH or DTX of the CQI field of HS-DPCCH as described above is applied at layer 1 only and is transparent to higher layers. +- In case no DPDCH is transmitted, any additional scaling of the total transmit power shall be such that + - the power ratio between DPCCH and HS-DPCCH or between DPCCH2 and HS-DPCCH if DPCCH2 is configured, and between DPCCH and E-DPCCH, for each activated uplink frequency remains as required by subclauses 5.1.2.5, 5.1.2.5A and 5.1.2.5B.1, and such that the power ratio between each E-DPDCH and DPCCH remains as required by $\beta_{ed,k,min}/\beta_c$ and + - the power ratio between DPCCH on the activated frequencies remains unchanged. + +##### Additional generic power scaling rules + +Any scaling, and any reduction in the E-DPDCH gain factor as described above, shall only be applied or changed at a DPCCH slot boundary. In order that the total UE transmit power does not exceed the maximum allowed value the scaling or E-DPDCH gain factor reduction shall be computed using the maximum HS-DPCCH power transmitted in the next DPCCH slot. In the case that either an ACK or a NACK transmission will start during the next DPCCH slot, the maximum HS-DPCCH power shall be computed using one of the following: + +- a) whichever of $\Delta_{ACK}$ and $\Delta_{NACK}$ will be used according to whether the transmission will be ACK or NACK, or +- b) whichever of $\Delta_{ACK}$ and $\Delta_{NACK}$ is the largest. + +When transmitting on a DPCH the UE is not required to be capable of reducing its total transmit power below the minimum level required in [7]. However, it may do so, provided that the power ratio between DPCCH and DPDCH, between DPCCH and HS-DPCCH or between DPCCH2 and HS-DPCCH if DPCCH2 is configured, and between + +DPCCH and S-DPCCH remains as specified in sub clause 5.1.2.5, 5.1.2.5A, and 5.1.2.5D. Some further regulations also apply as follows: In the case that the total UE transmit power (after applying DPCCH power adjustments and gain factors) would be at or below the total transmit power in the previously transmitted slot and also at or below the required minimum power specified in [7], the UE may apply additional scaling to the total transmit power, subject to the following restrictions: + +- The total transmit power after applying any additional scaling shall not exceed the required minimum power, nor the total transmit power in the previously transmitted slot; +- The magnitude of any reduction in total transmit power between slots after applying any additional scaling shall not exceed the magnitude of the calculated power reduction before the additional scaling. + +In the case that the total UE transmit power in the previously transmitted slot is at or below the required minimum power specified in [7] and the DPCCH power adjustment and gain factors for the current slot would result in an increase in total power, then no additional scaling shall be used (i.e. power control shall operate as normal). + +If the UE applies any additional scaling to the total transmit power as described above, this scaling shall be included in the computation of any DPCCH power adjustments to be applied in the next transmitted slot. + +### 5.1.3 Void + +## 5.2 Downlink power control + +The transmit power of the downlink channels is determined by the network. In general the ratio of the transmit power between different downlink channels is not specified and may change with time. However, regulations exist as described in the following subclauses. + +Higher layer power settings shall be interpreted as setting of the total power, i.e. the sum of the power from the two antennas in case of transmit diversity. + +### 5.2.1 DPCCH/DPDCH/F-DPCH + +#### 5.2.1.1 General + +The downlink transmit power control procedure controls simultaneously the power of a DPCCH and its corresponding DPDCHs. The power control loop adjusts the power of the DPCCH and DPDCHs with the same amount, i.e. the relative power difference between the DPCCH and DPDCHs is not changed. In case of F-DPCH, the power control loop adjusts the F-DPCH power. If DPCCH2 is configured, the power control loop associated with DPCCH2 adjusts the F-DPCH power at the serving HS-DSCH cell, and the power control loop associated with DPCCH adjusts the F-DPCH power at the designated non-serving HS-DSCH cell. If multiple frequencies are activated in the uplink, then the downlink transmit power control procedure shall be followed independently for each associated downlink frequency. + +For DPCH, the relative transmit power offset between DPCCH fields and DPDCHs is determined by the network. The TFCI and pilot fields of the DPCCH are offset relative to the DPDCHs power by PO1 and PO3 dB respectively. When DL\_DCH\_FET\_Config is not configured by higher layers, or, when DL\_DCH\_FET\_Config is configured and no SRBs are transmitted in the radio frame, the TPC fields of the DPCCH are offset relative to the DPDCHs power by PO2; otherwise, when DL\_DCH\_FET\_Config is configured by higher layers, and, SRB is transmitted in the radio frame, the TPC fields of the DPCCH are offset relative to the DPDCHs power by PO2 – POSRB. The power offsets may vary in time. The method for controlling the power offsets within UTRAN is specified in [6]. The power offsets PO1, PO2, PO3 and POSRB do not apply to F-DPCH. + +#### 5.2.1.2 Ordinary transmit power control + +##### 5.2.1.2.1 UE behaviour + +If Algorithm 3 is not configured for the serving radio link, the UE behaviour is as follows. + +If DPCCH2 is not configured, the UE shall generate TPC commands to control the network transmit power and send them in the TPC field of the uplink DPCCH. An example on how to derive the TPC commands is given in Annex B.2. + +If DPCCH2 is configured, the UE shall generate TPC commands to control the network transmit power from the serving HS-DSCH cell and send them in the TPC field of the uplink DPCCH2, and in addition, if E-DCH decoupling is + +not configured, the UE shall generate TPC commands to control the network transmit power from the designated non-serving HS-DSCH cell signalled by the network and send them in the TPC field of the uplink DPCCH. + +If E-DCH decoupling is configured, the UE shall generate TPC commands to control the network transmit power from the serving E-DCH cell and send them in the TPC field of the uplink DPCCH. + +The UE shall check the downlink power control mode (DPC\_MODE) before generating the TPC command: + +- if DPC\_MODE = 0 : the UE sends a unique TPC command in each slot and the TPC command generated is transmitted in the first available TPC field in the uplink DPCCH/DPCCH2. In case uplink DPCCH slot format #4 is used then UE may delay transmitting generated TPC command to the next available TPC field +- if DPC\_MODE = 1 : the UE repeats the same TPC command over 3 slots and the new TPC command is transmitted such that there is a new command at the beginning of the frame, unless UE\_DTX\_DRX\_Enabled is TRUE, in which case the UE shall behave as for DPC\_MODE=0. If DPC\_MODE=1 when uplink DPCCH slot format #4 is configured, the UE behaviour is undefined. + +The DPC\_MODE parameter is a UE specific parameter controlled by the UTRAN. + +The UE shall not make any assumptions on how the downlink power is set by UTRAN, in order to not prohibit usage of other UTRAN power control algorithms than what is defined in subclause 5.2.1.2.2. + +If the serving radio link is configured with Algorithm 3, the UE generates the TPC commands in the uplink DPCCH as follows: + +- The UE shall generate one uplink TPC command in the slot where the downlink TPC command is known to be present. + - If the length of the slot cycle is 3, the uplink TPC commands generated in the subsequent slots where the downlink TPC command is not known to be present shall take the value of 0 and 1, respectively. + - If the length of the slot cycle is 5, the uplink TPC commands generated in the subsequent slots where the downlink TPC command is not known to be present shall take the value of 0, 1, 0 and 1, respectively. + +###### 5.2.1.2.1.1 F-DPCH quality target control + +When DPCCH2 is not configured, the UTRAN sets a quality target for the F-DPCH. The UE autonomously sets a SIR target value and adjusts it in order to achieve the same quality as the quality target set by UTRAN. The quality target is set as a downlink TPC command error rate target value for the F-DPCH belonging to the radio link from the HS-DSCH serving cell as signalled by the UTRAN for the case where E-DCH decoupling is not configured. If E-DCH decoupling is configured, the quality target is set as a downlink TPC command error rate target value for the F-DPCH belonging to the radio link from the serving E-DCH cell as signalled by the UTRAN. The UE shall set the SIR target when the F-DPCH has been setup or reconfigured. It shall not increase the SIR target value before the power control has converged on the current value. The UE may estimate whether the power control has converged on the current value, by comparing the averaged measured SIR to the SIR target value. When UL\_DTX\_Active is TRUE, the UE shall ignore in the SIR target value adjustment any TPC commands received in F-DPCH slot starting during an uplink DPCCH slot which is in an uplink DPCCH transmission gap. + +When DPCCH2 is configured, the UE monitors two independent F-DPCH qualities, one for the F-DPCH associated with the uplink DPCCH2 belonging to the HS-DSCH serving cell, and one for F-DPCH belonging to the designated non-serving HS-DSCH cell. If E-DCH decoupling is configured, the designated non-serving HS-DSCH cell is the serving E-DCH cell. The UTRAN sets a single quality target which is set as a downlink TPC command error rate target value for the F-DPCHs. The UE autonomously sets a SIR target value and adjusts it in order to achieve the same quality as the quality target set by UTRAN. It shall not increase the SIR target value before the power control has converged on the current value. The UE may estimate whether the power control has converged on the current value, by comparing the averaged measured SIR to the SIR target value. When UL\_DTX\_Active is TRUE, the UE shall ignore in the SIR target value adjustment any TPC commands received in F-DPCH slot starting during an uplink DPCCH slot which is in an uplink DPCCH transmission gap. + +##### 5.2.1.2.2 UTRAN behaviour + +If DPCCH2 is not configured, upon receiving the TPC commands from DPCCH, UTRAN shall adjust its downlink DPCCH/DPDCH or F-DPCH power accordingly. + +If DPCCH2 is configured and DPCH is not configured, upon receiving the TPC commands from DPCCH2, UTRAN shall adjust its downlink power of F-DPCH associated with DPCCH2 for the serving HS-DSCH cell accordingly, and upon receiving the TPC commands from DPCCH, UTRAN shall adjust its downlink power of F-DPCH associated with DPCCH for the designated non-serving HS-DSCH cell. For the serving HS-DSCH cell, both the F-DPCH associated with DPCCH2 and the F-DPCH associated with DPCCH are transmitted at the same power. + +If DPCCH2 is configured and DPCH is configured, upon receiving the TPC commands from DPCCH2, UTRAN shall adjust its downlink power of F-DPCH associated with DPCCH2 for the serving HS-DSCH cell accordingly, and upon receiving the TPC commands from DPCCH, UTRAN shall adjust its downlink power of DPCCH/DPDCH accordingly. + +For DPC\_MODE = 0, and for DPC\_MODE=1 if UE\_DTX\_DRX\_Enabled is TRUE, UTRAN shall estimate the transmitted TPC command $TPC_{est}$ to be 0 or 1, and shall update the power every transmitted slot. If DPC\_MODE = 1 and UE\_DTX\_DRX\_Enabled is FALSE, UTRAN shall estimate the transmitted TPC command $TPC_{est}$ over three slots to be 0 or 1, and shall update the power every three slots. + +After estimating the $k$ :th TPC command, UTRAN shall adjust the current downlink power $P(k-1)$ [dB] to a new power $P(k)$ [dB] according to the following formula: + +$$P(k) = P(k-1) + P_{TPC}(k) + P_{bal}(k),$$ + +where $P_{TPC}(k)$ is the $k$ :th power adjustment due to the inner loop power control, and $P_{bal}(k)$ [dB] is a correction according to the downlink power control procedure for balancing radio link powers towards a common reference power. The power balancing procedure and control of the procedure is described in [6]. + +$P_{TPC}(k)$ is calculated according to the following. + +If the value of *Limited Power Increase Used* parameter is 'Not used', then + +$$P_{TPC}(k) = \begin{cases} +\Delta_{TPC} & \text{if } TPC_{est}(k) = 1 \\ -\Delta_{TPC} & \text{if } TPC_{est}(k) = 0 \end{cases} \text{ [dB].} \quad (1)$$ + +If the value of *Limited Power Increase Used* parameter is 'Used', then the $k$ :th inner loop power adjustment shall be calculated as: + +$$P_{TPC}(k) = \begin{cases} +\Delta_{TPC} & \text{if } TPC_{est}(k) = 1 \text{ and } \Delta_{sum}(k) + \Delta_{TPC} < \text{Power\_Raise\_Limit} \\ 0 & \text{if } TPC_{est}(k) = 1 \text{ and } \Delta_{sum}(k) + \Delta_{TPC} \geq \text{Power\_Raise\_Limit}, \text{ [dB]} \\ -\Delta_{TPC} & \text{if } TPC_{est}(k) = 0 \end{cases} \quad (2)$$ + +where + +$$\Delta_{sum}(k) = \sum_{i=k-DL\_Power\_Averaging\_Window\_Size}^{k-1} P_{TPC}(i)$$ + +is the temporary sum of the last *DL\_Power\_Averaging\_Window\_Size* inner loop power adjustments (in dB). + +For the first (*DL\_Power\_Averaging\_Window\_Size* – 1) adjustments after the activation of the limited power increase method, formula (1) shall be used instead of formula (2). *Power\_Raise\_Limit* and *DL\_Power\_Averaging\_Window\_Size* are parameters configured in the UTRAN. + +The power control step size $\Delta_{TPC}$ can take four values: 0.5, 1, 1.5 or 2 dB. It is mandatory for UTRAN to support $\Delta_{TPC}$ of 1 dB, while support of other step sizes is optional. + +In addition to the above described formulas on how the downlink power is updated, the restrictions below apply. + +In case of congestion (commanded power not available), UTRAN may disregard the TPC commands from the UE. + +The average power of transmitted DPDCH symbols over one timeslot shall not exceed *Maximum\_DL\_Power* (dB), nor shall it be below *Minimum\_DL\_Power* (dB). Transmitted DPDCH symbol means here a complex QPSK symbol before spreading which does not contain DTX. *Maximum\_DL\_Power* (dB) and *Minimum\_DL\_Power* (dB) are power limits for one channelisation code, relative to the primary CPICH power [6]. + +In case of F-DPCH, the power of the transmitted symbol over one timeslot for a given UE shall not exceed *Maximum\_DL\_Power* (dB), nor shall it be below *Minimum\_DL\_Power* (dB). Transmitted symbol means here a complex QPSK symbol before spreading which does not contain DTX. + +In the case that UL\_DTX\_Active is TRUE (see clause 6C), if no uplink TPC command is received due to Uplink DPCCH burst pattern gap as defined in subclause 6C.2.1, $P_{TPC}(k)$ derived by the Node B shall be set to zero. + +#### 5.2.1.3 Power control in compressed mode + +The aim of downlink power control in uplink or/and downlink compressed mode is to recover as fast as possible a signal-to-interference ratio (SIR) close to the target SIR after each transmission gap. + +The UE behaviour is the same in compressed mode as in normal mode, described in subclause 5.2.1.2, except that the target SIR for a DPCH is offset by higher layer signalling. However due to transmission gaps in uplink compressed frames there may be incomplete sets of TPC commands when DPC\_MODE=1. + +UTRAN behaviour is as stated in subclause 5.2.1.2.2 except for DPC\_MODE = 1 where missing TPC commands in the UL may lead the UTRAN to changing its power more frequently than every 3 slots. + +In compressed mode, compressed frames may occur in either the uplink or the downlink or both. In downlink compressed frames, the transmission of downlink DPDCH(s), DPCCH and F-DPCH shall be stopped during transmission gaps. + +The power of the DPCCH and DPDCH in the first slot after the transmission gap, or the power of the F-DPCH in the first slot after the transmission gap, should be set to the same value as in the slot just before the transmission gap. + +During compressed mode except during downlink transmission gaps, UTRAN shall estimate the $k$ :th TPC command and adjust the current downlink power $P(k-1)$ [dB] to a new power $P(k)$ [dB] according to the following formula: + +$$P(k) = P(k-1) + P_{TPC}(k) + P_{SIR}(k) + P_{bal}(k),$$ + +where $P_{TPC}(k)$ is the $k$ :th power adjustment due to the inner loop power control, $P_{SIR}(k)$ is the $k$ -th power adjustment due to the downlink target SIR variation, and $P_{bal}(k)$ [dB] is a correction according to the downlink power control procedure for balancing radio link powers towards a common reference power. The power balancing procedure and control of the procedure is described in [6]. + +Due to transmission gaps in uplink compressed frames, there may be missing TPC commands in the uplink. + +For DPC\_MODE = 0, and for DPC\_MODE=1 if UE\_DTX\_DRX\_Enabled is TRUE, if no uplink TPC command is received, $P_{TPC}(k)$ derived by the Node B shall be set to zero. Otherwise, $P_{TPC}(k)$ is calculated the same way as in normal mode (see subclause 5.2.1.2.2) but with a step size $\Delta_{STEP}$ instead of $\Delta_{TPC}$ . + +For DPC\_MODE = 1 if UE\_DTX\_DRX\_Enabled is FALSE, the sets of slots over which the TPC commands are processed shall remain aligned to the frame boundaries in the compressed frame. If this results in an incomplete set of TPC commands, the UE shall transmit the same TPC commands in all slots of the incomplete set. + +The power control step size $\Delta_{STEP} = \Delta_{RP-TPC}$ during RPL slots after each transmission gap and $\Delta_{STEP} = \Delta_{TPC}$ otherwise, where: + +- RPL is the recovery period length and is expressed as a number of slots. RPL is equal to the minimum value out of the transmission gap length and 7 slots. If a transmission gap or an Uplink DPCCH burst pattern gap as defined in subclause 6C.2 is scheduled to start before RPL slots have elapsed, then the recovery period shall end at the start of the gap, and the value of RPL shall be reduced accordingly. +- $\Delta_{RP-TPC}$ is called the recovery power control step size and is expressed in dB. $\Delta_{RP-TPC}$ is equal to the minimum value of 3 dB and $2\Delta_{TPC}$ . + +For F-DPCH, $P_{SIR}(k) = 0$ . + +For DPCH, the power offset $P_{SIR}(k) = \delta P_{curr} - \delta P_{prev}$ , where $\delta P_{curr}$ and $\delta P_{prev}$ are respectively the value of $\delta P$ in the current slot and the most recently transmitted slot and $\delta P$ is computed as follows: + +$$\delta P = \max(\Delta P1\_compression, \dots, \Delta Pn\_compression) + \Delta P1\_coding + \Delta P2\_coding$$ + +where $n$ is the number of different TTI lengths amongst TTIs of all TrChs of the CCTrCh, where $\Delta P1\_coding$ and $\Delta P2\_coding$ are computed from uplink parameters DeltaSIR1, DeltaSIR2, DeltaSIRafter1, DeltaSIRafter2 signaled by higher layers as: + +- $\Delta P1\_coding = \text{DeltaSIR1}$ if the start of the first transmission gap in the transmission gap pattern is within the current frame and $\text{UE\_DTX\_DRX\_Enabled}$ is FALSE. +- $\Delta P1\_coding = \text{DeltaSIRafter1}$ if the current frame just follows a frame containing the start of the first transmission gap in the transmission gap pattern and $\text{UE\_DTX\_DRX\_Enabled}$ is FALSE. +- $\Delta P2\_coding = \text{DeltaSIR2}$ if the start of the second transmission gap in the transmission gap pattern is within the current frame and $\text{UE\_DTX\_DRX\_Enabled}$ is FALSE. +- $\Delta P2\_coding = \text{DeltaSIRafter2}$ if the current frame just follows a frame containing the start of the second transmission gap in the transmission gap pattern and $\text{UE\_DTX\_DRX\_Enabled}$ is FALSE. +- $\Delta P1\_coding = 0 \text{ dB}$ and $\Delta P2\_coding = 0 \text{ dB}$ in all other cases. + +and $\Delta P_i\_compression$ is defined by : + +- $\Delta P_i\_compression = 3 \text{ dB}$ for downlink frames compressed by reducing the spreading factor by 2. +- $\Delta P_i\_compression = 0 \text{ dB}$ in all other cases. + +In case several compressed mode patterns are used simultaneously, a $\delta P$ offset is computed for each compressed mode pattern and the sum of all $\delta P$ offsets is applied to the frame. + +For all time slots except those in transmissions gaps, the average power of transmitted DPDCH symbols over one timeslot shall not exceed $\text{Maximum\_DL\_Power (dB)}$ by more than $\delta P_{curr}$ , nor shall it be below $\text{Minimum\_DL\_Power (dB)}$ . Transmitted DPDCH symbol means here a complex QPSK symbol before spreading which does not contain DTX. $\text{Maximum\_DL\_Power (dB)}$ and $\text{Minimum\_DL\_Power (dB)}$ are power limits for one channelisation code, relative to the primary CPICH power [6]. + +For F-DPCH, for all time slots except those in transmissions gaps the power of the transmitted symbol over one timeslot for a given UE shall not exceed $\text{Maximum\_DL\_Power (dB)}$ , nor shall it be below $\text{Minimum\_DL\_Power (dB)}$ . Transmitted symbol means here a complex QPSK symbol before spreading which does not contain DTX. + +#### 5.2.1.4 Power scaling of DPDCH with $PO_{SRB}$ + +When $\text{DL\_DCH\_FET\_Config}$ is configured by higher layers, and SRB is transmitted in the radio frame, the TPC fields of the DPCCH are offset relative to the DPDCHs power by $PO2 - PO_{SRB}$ . The change in TPC/DPDCH offset between $PO2$ and $PO2 - PO_{SRB}$ happens by adjusting the power of DPCH (both TPC and DPDCH fields) according to power control rules of Subclause 5.2.1.2.2 or 5.2.1.3, and then, scaling the DPDCH fields by a factor of $PO_{SRB}$ (in dB). Figure 1A describes the scaling procedure. + +$$y^{(2)}(i) = \begin{cases} x^{(2)}(i), & i \text{ is odd} \\ x^{(1)}(i), & i \text{ is even} \end{cases}$$ + +**Figure 1A: Power scaling of DPDCH with $PO_{SRB}$ . Here, $\alpha$ denotes the power adjustment due to power control procedure in Subclause 5.2.1.2.2 or 5.2.1.3.** + +### 5.2.2 Void + +### 5.2.3 Void + +### 5.2.4 AICH + +The UE is informed about the relative transmit power of the AIs (measured as the power per transmitted acquisition indicator) and the relative transmit power of the EAIs (measured as the power per transmitted extended acquisition indicator), both compared to the primary CPICH transmit power by the higher layers. + +### 5.2.5 PICH + +The UE is informed about the relative transmit power of the PICH (measured as the power over the paging indicators) compared to the primary CPICH transmit power by the higher layers. + +### 5.2.6 S-CCPCH + +The TFCI and pilot fields may be offset relative to the power of the data field. The power offsets may vary in time. + +For MBSFN FACH transmission with 16QAM, the UE is informed about the relative transmit power of the S-CCPCH (measured as the power of the transmitted data of S-CCPCH) compared to the primary CPICH transmit power by the higher layers. + +### 5.2.7 Void + +### 5.2.8 Void + +### 5.2.9 Void + +### 5.2.10 HS-SCCH + +The HS-SCCH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. + +### 5.2.11 HS-PDSCH + +The HS-PDSCH power control is under the control of the node B. When the HS-PDSCH is transmitted using 16QAM or 64QAM, the UE may assume that the power is kept constant during the corresponding HS-PDSCH subframe. + +In case of multiple HS-PDSCH transmission to one UE, all the HS-PDSCHs intended for that UE shall be transmitted with equal power. + +The sum of the powers used by all HS-PDSCHs, HS-SCCHs, E-AGCHs, E-RGCHs and E-HICHs in a cell shall not exceed the value of *HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power* if signaled by higher layers [6]. + +### 5.2.12 E-AGCH + +The E-AGCH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. If Implicit Grant Handling is configured, when the E-AGCH message is targeted to one UE for decoding and to another UE for detection, the Node B may e.g. power control the E-AGCH appropriately to satisfy the reception performance requirements for the two UEs. + +### 5.2.13 E-HICH + +The E-HICH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. + +### 5.2.14 E-RGCH + +The E-RGCH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. + +### 5.2.15 MICH + +The UE is informed about the relative transmit power of the MICH (measured as the power over the notification indicators) compared to the primary CPICH transmit power by the higher layers. + +### 5.2.16 S-CPICH + +In case the UE is configured in MIMO mode, and S-CPICH is used as a phase reference for a second transmit antenna, the UE is informed about the relative transmit power of the S-CPICH compared to the primary CPICH transmit power by the higher layers. + +In case the UE is configured in MIMO mode with four transmit antennas, the S-CPICHs are used as a phase reference for the second, third and fourth transmit antennas and, the UE is informed about the relative transmit power of each S-CPICH compared to the primary CPICH transmit power by the higher layers. The S-CPICHs transmitted on the third and fourth transmit antennas are transmitted with equal power. + +### 5.2.17 F-TPICH + +F-TPICH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. + +### 5.2.18 D-CPICH + +In case the UE is configured in MIMO mode with four transmit antennas, D-CPICHs are configured for the third and fourth transmit antenna, the UE is informed about the relative transmit power of each D-CPICH compared to the primary CPICH transmit power by the higher layers. The two D-CPICHs are transmitted with equal power. + +### 5.2.19 E-ROCH + +The E-ROCH power control is under the control of the node B. It may e.g. follow the power control commands sent by the UE to the node B or any other power control procedure applied by the node B. + +# --- 6 Random access procedure + +## 6.1 Physical random access procedure + +The physical random access procedure described in this subclause is initiated upon request from the MAC sublayer (cf. [9]). This procedure can also be initiated if indicated by higher layers and Fallback\_R99\_Enabled is TRUE. + +Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information from the higher layers (RRC): + +- The preamble scrambling code. +- The message length in time, either 10 or 20 ms. +- The AICH\_Transmission\_Timing parameter [0 or 1]. +- The set of available signatures and the set of available RACH sub-channels for each Access Service Class (ASC). Sub-channels are defined in subclause 6.1.1. +- The power-ramping factor Power Ramp Step [integer > 0]. +- The parameter Preamble Retrans Max [integer > 0]. + +- The initial preamble power Preamble\_Initial\_Power. +- The Power offset $P_{p-m} = P_{\text{message-control}} - P_{\text{preamble}}$ , measured in dB, between the power of the last transmitted preamble and the control part of the random-access message. +- The set of Transport Format parameters. This includes the power offset between the data part and the control part of the random-access message for each Transport Format. + +Note that the above parameters may be updated from higher layers before each physical random access procedure is initiated. + +At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the higher layers (MAC): + +- The Transport Format to be used for the PRACH message part. +- The ASC of the PRACH transmission. +- The data to be transmitted (Transport Block Set). + +The physical random-access procedure shall be performed as follows: + +- 1 Derive the available uplink access slots, in the next full access slot set or in the next 8 access slots, for the set of available RACH sub-channels within the given ASC with the help of subclauses 6.1.1. and 6.1.2. Randomly select one access slot among the ones previously determined. If there is no access slot available in the selected set, randomly select one uplink access slot corresponding to the set of available RACH sub-channels within the given ASC from the next access slot set or in the next 7 access slots. The random function shall be such that each of the allowed selections is chosen with equal probability. +- 2 Randomly select a signature from the set of available signatures within the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability. +- 3 Set the Preamble Retransmission Counter to Preamble Retrans Max. +- 4 If the Preamble\_Initial\_Power is below the minimum level required in [7], set the Commanded Preamble Power to a value, which shall be at or above the Preamble\_Initial\_Power and at or below the required minimum power specified in [7]. Otherwise set the parameter Commanded Preamble Power to Preamble\_Initial\_Power. +- 5 In the case that the Commanded Preamble Power exceeds the maximum allowed value, set the preamble transmission power to the maximum allowed power. In the case that the Commanded Preamble Power is below the minimum level required in [7], set the preamble transmission power to a value, which shall be at or above the Commanded Preamble Power and at or below the required minimum power specified in [7]. Otherwise set the preamble transmission power to the Commanded Preamble Power. Transmit a preamble using the selected uplink access slot, signature, and preamble transmission power. +- 6 If no positive or negative acquisition indicator ( $AI \neq +1$ nor $-1$ ) corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot: + - 6.1 Select the next available access slot in the set of available RACH sub-channels within the given ASC. + - 6.2 Randomly select a new signature from the set of available signatures within the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability. + - 6.3 Increase the Commanded Preamble Power by $\Delta P_0 = \text{Power Ramp Step [dB]}$ . If the Commanded Preamble Power exceeds the maximum allowed power by 6dB, the UE may pass L1 status ("No ack on AICH") to the higher layers (MAC) and exit the physical random access procedure. + - 6.4 Decrease the Preamble Retransmission Counter by one. + - 6.5 If the Preamble Retransmission Counter $> 0$ then repeat from step 5. Otherwise pass L1 status ("No ack on AICH") to the higher layers (MAC) and exit the physical random access procedure. +- 7 If a negative acquisition indicator corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot, pass L1 status ("Nack on AICH received") to the higher layers (MAC) and exit the physical random access procedure. + +- 8 Transmit the random access message three or four uplink access slots after the uplink access slot of the last transmitted preamble depending on the AICH transmission timing parameter. Transmission power of the control part of the random access message should be $P_{p-m}$ [dB] higher than the power of the last transmitted preamble. Transmission power of the data part of the random access message is set according to subclause 5.1.1.2. +- 9 Pass L1 status "RACH message transmitted" to the higher layers and exit the physical random access procedure. + +### 6.1.1 RACH sub-channels + +A RACH sub-channel defines a sub-set of the total set of uplink access slots. There are a total of 12 RACH sub-channels. RACH sub-channel # $i$ ( $i = 0, \dots, 11$ ) consists of the following uplink access slots: + +- Uplink access slot # $i$ leading by $\tau_{p-a}$ chips the downlink access slot # $i$ contained within the 10 ms interval that is time aligned with P-CCPCH frames for which $SFN \bmod 8 = 0$ or $SFN \bmod 8 = 1$ . +- Every 12th access slot relative to this access slot. + +The access slots of different RACH sub-channels are also illustrated in Table 7. + +**Table 7: The available uplink access slots for different RACH sub-channels** + +| SFN modulo 8 of corresponding P-CCPCH frame | Sub-channel number | | | | | | | | | | | | +|---------------------------------------------|--------------------|----|----|----|----|----|----|----|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | +| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | | | +| 1 | 12 | 13 | 14 | | | | | | 8 | 9 | 10 | 11 | +| 2 | | | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| 3 | 9 | 10 | 11 | 12 | 13 | 14 | | | | | | 8 | +| 4 | 6 | 7 | | | | | 0 | 1 | 2 | 3 | 4 | 5 | +| 5 | | | 8 | 9 | 10 | 11 | 12 | 13 | 14 | | | | +| 6 | 3 | 4 | 5 | 6 | 7 | | | | | 0 | 1 | 2 | +| 7 | | | | | | 8 | 9 | 10 | 11 | 12 | 13 | 14 | + +### 6.1.2 RACH access slot sets + +The PRACH contains two sets of access slots as shown in Figure 2. Access slot set 1 contains PRACH slots 0 – 7 and starts $\tau_{p-a}$ chips before the downlink P-CCPCH frame for which $SFN \bmod 2 = 0$ . Access slot set 2 contains PRACH slots 8 - 14 and starts $(\tau_{p-a} - 2560)$ chips before the downlink P-CCPCH frame for which $SFN \bmod 2 = 1$ . + +$$y^{(0)}(i) = \begin{cases} x^{(0)}(i), & i \text{ is odd} \\ x^{(3)}(i), & i \text{ is even} \end{cases}$$ + +**Figure 2: PRACH access slot and downlink AICH relation ( $\tau_{p-a} = 7680$ chips)** + +## 6.1A Physical random access procedure for Enhanced Uplink in CELL\_FACH state and IDLE mode + +The physical random access procedure described in this subclause is initiated upon request from the MAC sublayer (cf. [9]). + +Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information from the higher layers (RRC): + +- Preamble scrambling code(s) for 2 and 10ms TTI. +- The AICH\_Transmission\_Timing parameter [0 or 1]. +- The set of available signatures and the set of available RACH sub-channels corresponding to E-DCH resources for each Access Service Class (ASC). Sub-channels are defined in subclause 6.1.1. +- The total number of E-DCH resources configured in the cell. +- The power-ramping factor Power Ramp Step [integer > 0]. +- The parameter Preamble Retrans Max [integer > 0]. +- The initial preamble power Preamble\_Initial\_Power. +- The Power offset $P_{p-e} = P_{dpch} - P_{preamble}$ , measured in dB, between the power of the last transmitted preamble and the initial DPCCH transmission power. +- The number of TTIs in which only the uplink DPCCH is sent before the E-DCH transmission may start for 2 and 10ms TTI. + +Note that the above parameters may be updated from higher layers before each physical random access procedure is initiated. + +At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the higher layers (MAC): + +- The ASC of the PRACH transmission. + +If Concurrent\_TTI\_Deployment\_Enabled is TRUE, Layer 1 shall also receive the following additional parameters from the higher layers (MAC): + +- TTI length, either 2 or 10ms. + +The procedure for the selection of the TTI length is defined in subclause 8.5.b1 in [5]. The TTI length may be updated by higher layers before each preamble retransmission. + +The physical random-access procedure shall be performed as follows: + +- 1 If NT-HS-DPCCH\_Enabled is FALSE, or if NT-HS-DPCCH\_Enabled is TRUE and the physical random-access procedure is not triggered by an HS-SCCH order, then derive the available uplink access slots, in the next full access slot set or in the next 8 access slots, for the set of available RACH sub-channels within the given ASC with the help of subclauses 6.1.1. and 6.1.2. Randomly select one access slot among the ones previously determined. If there is no access slot available in the selected set, randomly select one uplink access slot corresponding to the set of available RACH sub-channels within the given ASC from the next access slot set or in the next 7 access slots. The random function shall be such that each of the allowed selections is chosen with equal probability. If NT-HS-DPCCH\_Enabled is TRUE and the physical random-access procedure is triggered by an HS-SCCH order, then the next available access slot is chosen. +- 2 If Concurrent\_TTI\_Deployment\_Enabled is TRUE, the scrambling code corresponding to the indicated TTI length is chosen. +- 2a Randomly select a signature from the set of available signatures within the given ASC and indicated scrambling code. The random function shall be such that each of the allowed selections is chosen with equal probability. If Concurrent\_TTI\_Deployment\_Enabled is TRUE, the set of available signatures corresponds to the indicated TTI length. +- 3 Set the Preamble Retransmission Counter to Preamble Retrans Max. +- 4 If the Preamble\_Initial\_Power is below the minimum level required in [7], set the Commanded Preamble Power to a value, which shall be at or above the Preamble\_Initial\_Power and at or below the required minimum power specified in [7]. Otherwise set the parameter Commanded Preamble Power to Preamble\_Initial\_Power. + +- 5 In the case that the Commanded Preamble Power exceeds the maximum allowed value, set the preamble transmission power to the maximum allowed power. In the case that the Commanded Preamble Power is below the minimum level required in [7], set the preamble transmission power to a value, which shall be at or above the Commanded Preamble Power and at or below the required minimum power specified in [7]. Otherwise set the preamble transmission power to the Commanded Preamble Power. Transmit a preamble using the selected uplink access slot, signature, and preamble transmission power. +- 6 If no positive or negative acquisition indicator (AI $\neq +1$ nor $-1$ ) corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot: + - 6.1 Select the next available access slot in the set of available RACH sub-channels within the given ASC. + - 6.2 Randomly select a new signature from the set of available signatures within the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability. If an update to the TTI length is indicated by higher layers, then the set of available signatures and the preamble scrambling code are also updated correspondingly. + - 6.3 Increase the Commanded Preamble Power by $\Delta P_0 = \text{Power Ramp Step [dB]}$ . If the **Commanded Preamble Power** exceeds the maximum allowed power by 6dB, the UE may pass L1 status ("No ack on AICH") to the higher layers (MAC) and exit the physical random access procedure. + - 6.4 Decrease the Preamble Retransmission Counter by one. + - 6.5 If the Preamble Retransmission Counter $> 0$ then repeat from step 5. Otherwise pass L1 status ("No ack on AICH") to the higher layers (MAC) and exit the physical random access procedure. +- 7 If a negative acquisition indicator on AICH corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot. + - 7.1 If no Extended Acquisition Indicator signature set is configured in the cell, pass L1 status ("Nack on AICH received") to the higher layers (MAC) and exit the physical random access procedure. + - 7.2 If an Extended Acquisition Indicator signature set is configured in the cell, detect which one of the defined Extended Acquisition Indicator signatures is present. + - 7.2.1 If the detected Extended Acquisition Indicator signature and modulation symbol corresponds to 'NACK' as defined in [1], pass L1 status ("Nack on AICH received") to the higher layers (MAC) and exit the physical random access procedure. + - 7.2.2 If the detected Extended Acquisition Indicator signature and modulation symbol do not correspond to 'NACK', pass L1 status ("Ack on AICH received") with the corresponding E-DCH resource index as defined in [1] to higher layers (MAC) and skip step 8. +- 8 If a positive acquisition indicator on AICH corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot, pass L1 status ("Ack on AICH received") with the default E-DCH resource index corresponding to the selected signature as defined in [1] to higher layers (MAC), +- 9 Start transmitting DPCCH (timing as specified in [1] and synchronization according to synchronization procedure AA). The initial transmission power of DPCCH prior to starting the E-DCH transmission should be $P_{p-e}$ [dB] higher than the power of the last transmitted preamble. +- 10 Proceed to transmitting E-DPCCH and E-DPDCH, and transmit HS-DPCCH if so instructed by MAC layer after the defined number of TTIs of DPCCH only transmission has passed. + +## 6.2 Void + +# 6A HS-DSCH-related procedures + +## 6A.1 General procedure + +Scheduling and transport format selection is controlled by the MAC-hs or MAC-ehs sublayer in the Node B [9]. + +The following parameters are signalled to the physical layer in the UE and the Node B from higher layers: + +- 1) HS-SCCH set to be monitored in the serving HS-DSCH cell +- 2) Repetition factors of ACK/NACK: $N\_acknack\_transmit$ and $N\_acknack\_transmit\_2$ . The parameter $N\_acknack\_transmit\_2$ is signaled when the UE is configured in Multiflow mode as specified in [5] +- 3) Channel Quality Indicator (CQI) feedback cycles: CQI feedback cycle $k$ and CQI feedback cycle2 $k$ if HS-DPCCH overhead reduction Type 2 is configured. At any given moment in time, the used CQI feedback cycle, denoted $k$ in the subclause 6A.1.2, is set to be one of the two feedback cycles. +- 4) Repetition factors of CQI: $N\_cqi\_transmit$ and $N\_cqi\_transmit\_2$ . The parameter $N\_cqi\_transmit\_2$ is signalled when the UE is configured in Multiflow mode as specified in [5] +- 5) Measurement power offset $\Gamma$ and $\Gamma_1$ +- 6) Status of preamble/postamble transmission: HARQ\_preamble\_mode +- 7) Status of 64QAM configuration +- 8) Set of P-CPICH and/or S-CPICH (which shall be transmitted on the same scrambling code) that shall be used for HS-PDSCH demodulation in case the UE is configured in MIMO mode and in MIMO mode with four transmit antennas. Set of D-CPICH (which shall be transmitted on the same scrambling code as that of P-CPICH) in case the UE is configured in MIMO mode with four transmit antennas. +- 9) The number $N$ of dynamic single/dual CQI reports out of a sequence of $M$ CQI reports in case the UE is configured in MIMO mode (not applicable when single-stream restriction is configured) and in MIMO mode with four transmit antennas: $N\_cqi\_typeA$ , $M\_cqi$ , respectively +- 10) Set of transport block sizes configured for HS-SCCH-less operation +- 11) Set of HS-PDSCHs configured for HS-SCCH-less operation +- 12) Status variables HS\_SCCH\_LESS\_STATUS and DTX\_DRX\_STATUS +- 13) Enabling\_Delay +- 14) RRC protocol state (CELL\_DCH, CELL\_FACH, CELL\_PCH or URA\_PCH) +- 15) H-RNTI values (dedicated H-RNTI, common H-RNTI, BCCH specific H-RNTI) to be monitored when the UE is configured to receive HS-DSCH in CELL\_FACH or CELL\_PCH state +- 16) HS-DSCH paging system information, which includes the following information when the UE is configured to receive HS-DSCH in URA\_PCH state or in CELL\_PCH state: + - a) Number of PCCH transmissions: The number of subframes used to transmit PAGING TYPE 1 as defined in [5]. + - b) HS-PDSCH Channelisation Code configured for HS-SCCH less paging operation + - c) Transport Block Size: List of Transport Block Sizes +- 17) Status of MIMO configuration and MIMO configuration with four transmit antennas +- 18) HS-SCCH set to be monitored in each secondary serving HS-DSCH cell +- 19) HS-SCCH set to be monitored in one non-serving cell +- 20) Status of 'Support for different HS-SCCHs in contiguous TTIs' +- 21) HS-SCCH set to be monitored in the assisting serving HS-DSCH cell +- 22) HS-SCCH set to be monitored in the assisting secondary serving HS-DSCH cell +- 23) CQI\_CYCLE\_SWITCH\_TIMER, which specifies the number of subframes without HS-PDSCH transmissions to the UE for the purpose of switching CQI feedback cycle to CQI feedback cycle2. This is the initial value of "CQI cycle switch timer". + +If HS\_SCCH\_LESS\_STATUS is TRUE then HS-SCCH\_less\_mode=1. Otherwise HS-SCCH\_less\_mode=0. + +HS-SCCH-less\_Active shall be set to TRUE while HS-SCCH\_less\_mode=1 and HS-SCCH-less operation is activated. Otherwise HS-SCCH\_less\_Active shall be set to FALSE. HS-SCCH-less operation shall be activated at the time when HS-SCCH\_less\_mode is set to 1, and may be further deactivated or activated by HS-SCCH orders as specified in [2]. This ordered deactivation or activation of the HS-SCCH-less operation is applied by the UE 12 slots after the end of the HS-SCCH subframe delivering the order. + +If the higher layers set DTX\_DRX\_STATUS to TRUE (as described in [5]) then UE\_DTX\_DRX\_Enabled is FALSE until Enabling\_Delay radio frames have passed. After the higher layers have set DTX\_DRX\_STATUS to TRUE (as described in [5]) and Enabling\_Delay radio frames have passed then UE\_DTX\_DRX\_Enabled is TRUE. Otherwise UE\_DTX\_DRX\_Enabled is FALSE. + +If the UE is not configured in Multiflow mode; + +- If the UE is configured with at least one secondary serving HS-DSCH cell, then Secondary\_Cell\_Enabled is equal to the number of the configured secondary serving HS-DSCH cells, otherwise Secondary\_Cell\_Enabled is 0 and Secondary\_Cell\_Active is 0. +- Configured secondary serving HS-DSCH cells shall be activated at the time when Secondary\_Cell\_Enabled is changed from 0 to a value not equal to 0, or +- The activation status for configured secondary HS-DSCH cell(s) shall be set as specified in [5] when Secondary\_Cell\_Enabled is changed from a value n (where n is greater than 0) to a value m (where m is a value greater than 0). Configured secondary serving HS-DSCH cells may further be deactivated or activated by HS-SCCH orders as specified in [2]. +- Secondary\_Cell\_Active shall be set to 1, 2, 3, 4, 5, 6, or 7 while Secondary\_Cell\_Enabled is set to a value not equal to 0, and 1, 2, 3, 4, 5, 6, or 7 secondary serving HS-DSCH cells are activated respectively; otherwise Secondary\_Cell\_Active shall be set to 0. +- If the UE receives an HS-SCCH order for activation of a secondary serving HS-DSCH cell that is already activated as specified in [2], then the UE shall not change the activation status of that secondary serving HS-DSCH cell, but shall transmit the HARQ-ACK acknowledging the HS-SCCH order. + +If the UE is configured in Multiflow mode and with a secondary serving cell or an assisting secondary serving cell, all the configured cell(s) are initially activated, and may further be deactivated or activated using HS-SCCH orders. + +- The Secondary Serving HS-DSCH cell can be deactivated with an order transmitted only by the Serving or the Secondary Serving HS-DSCH cell and reactivated with an order transmitted only by the serving HS-DSCH cell. +- The Assisting Secondary Serving HS-DSCH cell can be deactivated with an order transmitted only by the Assisting Serving or Assisting Secondary Serving HS-DSCH cell and reactivated with an order transmitted only by the Assisting Serving HS-DSCH cell. +- If the UE receives an HS-SCCH order for activation of a Secondary Serving HS-DSCH or Assisting Secondary Serving cell that is already activated as specified in [2], then the UE shall not change the activation status of that secondary serving HS-DSCH cell, but shall transmit the HARQ-ACK acknowledging the HS-SCCH order. +- If the higher layers indicate a change in the HS-DSCH cells, + - if the new configuration contains a Secondary Serving HS-DSCH cell that was either the Secondary Serving or Assisting Secondary Serving HS-DSCH cell in the earlier configuration and the cell was deactivated with HS-SCCH orders, it shall remain deactivated. Otherwise after the change the Secondary Serving HS-DSCH cell shall be active. + - if the new configuration contains an Assisting Secondary Serving HS-DSCH cell that was either the Secondary Serving or Assisting Secondary Serving HS-DSCH cell in the earlier configuration and the cell was deactivated with HS-SCCH orders, it shall remain deactivated. Otherwise after the change the Assisting Secondary Serving HS-DSCH cell shall be active. + +If the UE is not configured with multiple uplink frequencies, HS-SCCH ordered deactivation or activation of the secondary serving HS-DSCH cell(s) or the Assisting Secondary Serving HS-DSCH cell is applied by the UE 12 slots after the end of the HS-SCCH subframe delivering the order, and any transient behaviour related to this change should take place before this point in time. If the activation statuses of all secondary serving HS-DSCH cells in a frequency band (as defined in [7]) remain unaffected by an HS-SCCH ordered deactivation or activation the maximum allowed interruption time for the cells in this band is 1 slot and the interrupt shall take place during the next downlink HS-SCCH + +slot after the end of the HS-DPCCH slot that contains the HARQ-ACK information acknowledging the HS-SCCH order. The corresponding change of the HS-DPCCH channel coding scheme as specified in [2] is applied by the UE at the first HS-DPCCH subframe boundary after the activation or deactivation has been applied. + +If the UE is configured with multiple uplink frequencies, HS-SCCH ordered deactivation or activation of the secondary serving HS-DSCH cell(s) or the Assisting Secondary Serving HS-DSCH cell is applied by the UE 18 slots after the end of the HS-SCCH subframe delivering the order, and any transient behaviour related to this change should take place before this point in time. If: + +- the activation statuses of all secondary serving HS-DSCH cells in a frequency band (as defined in [7]) remain unaffected by the HS-SCCH ordered deactivation or activation and the serving HS-DSCH cell is not configured in this band or +- the activation statuses of all secondary serving HS-DSCH cells and the secondary uplink frequency in a frequency band remain unaffected by the HS-SCCH ordered deactivation or activation and the serving HS-DSCH cell is configured in this band + +The maximum allowed interruption time for the downlink cells and uplink frequencies configured in this frequency band is 1 slot. The interrupt shall take place during the next downlink HS-SCCH slot after the end of the HS-DPCCH slot that contains the HARQ-ACK information acknowledging the HS-SCCH order. The corresponding change of the HS-DPCCH channel coding scheme as specified in [2] is applied by the UE at the first HS-DPCCH subframe boundary after the activation or deactivation has been applied. + +### 6A.1.1 UE procedure for receiving HS-DSCH and HS-SCCH in the CELL\_DCH state + +NOTE: The Node B procedure for transmitting the HS-DSCH and the HS-SCCH is specified in subclause 6A.1.3. + +In this subclause, sub-frame $n$ on the HS-SCCHs refers to the sub-frame which is associated with sub-frame $n$ on the HS-PDSCH as defined in [1], and sub-frame $n$ on the HS-DPCCH refers to the sub-frame which is related to sub-frame $n$ on the HS-PDSCH as defined in [1]. + +If the UE did not detect consistent control information intended for this UE on any of the HS-SCCHs in the HS-SCCH set in the immediately preceding subframe $n - 1$ , the UE shall in sub-frame $n$ monitor all HS-SCCHs in the HS-SCCH set. The maximum size of the HS-SCCH set in the serving HS-DSCH cell is 4. + +If 64QAM is not configured for the UE and 'Support for different HS-SCCHs in contiguous TTIs' is false, then if the UE did detect consistent control information intended for this UE in the immediately preceding subframe $n - 1$ , it is sufficient in sub-frame $n$ to only monitor the same HS-SCCH used in the immediately preceding subframe $n - 1$ . If 64QAM is configured for the UE or 'Support for different HS-SCCHs in contiguous TTIs' is true, then if the UE did detect consistent control information intended for this UE in the immediately preceding subframe $n - 1$ , the UE shall in sub-frame $n$ monitor all HS-SCCHs in the HS-SCCH set. These rules apply regardless of the value of HS-SCCH\_less\_mode. + +If Secondary\_Cell\_Active is not 0 and the UE is not configured in Multiflow mode, + +- The UE shall simultaneously monitor an HS-SCCH set in each of the activated secondary serving HS-DSCH cells, and receive HS-DSCH if it is scheduled in that cell. The maximum size of the HS-SCCH set in a secondary serving HS-DSCH cell is 4 and the maximum number of HS-SCCHs monitored by the UE across + - both the serving HS-DSCH cell and the secondary serving HS-DSCH cell is 6 if the UE is capable of HS-DSCH reception in a maximum of 2 cells. + - the serving HS-DSCH cell, the 1st and 2nd secondary serving HS-DSCH cells is 9 if the UE is capable of HS-DSCH reception in a maximum of 3 cells. + - the serving HS-DSCH cell, the 1st, 2nd and 3rd secondary serving HS-DSCH cells is 12 if the UE is capable of HS-DSCH reception in 4 cells. + - the serving HS-DSCH cell, the 1st, 2nd, 3rd and 4th secondary serving HS-DSCH cells is 15 if the UE is capable of HS-DSCH reception in 5 cells. + - the serving HS-DSCH cell, the 1st, 2nd, 3rd, 4th and 5th secondary serving HS-DSCH cells is 18 if the UE is capable of HS-DSCH reception in 6 cells. + +- the serving HS-DSCH cell, the 1st, 2nd, 3rd, 4th, 5th and 6th secondary serving HS-DSCH cells is 21 if the UE is capable of HS-DSCH reception in 7 cells. +- the serving HS-DSCH cell, the 1st, 2nd, 3rd, 4th, 5th, 6th and 7th secondary serving HS-DSCH cells is 24 if the UE is capable of HS-DSCH reception in 8 cells. +- From the serving HS-DSCH cell, the UE shall be able to receive up to one HS-DSCH if MIMO mode and MIMO mode with four transmit antennas is not configured or two HS-DSCHs if MIMO mode is configured or four HS-DSCHs if MIMO mode with four transmit antennas is configured or one HS-SCCH order. +- In addition, from each of the activated secondary serving HS-DSCH cells, the UE shall be able to simultaneously receive up to one HS-DSCH if MIMO mode and MIMO mode with four transmit antennas is not configured or two HS-DSCHs if MIMO mode is configured or four HS-DSCHs if MIMO mode with four transmit antennas is configured or one HS-SCCH order. + +- The maximum number of HS-SCCH orders simultaneously received by the UE across the serving HS-DSCH cell and all the activated secondary serving HS-DSCH cells is 2. +- HS-SCCH-less HS-DSCH transmission shall not be used in a secondary serving HS-DSCH cell. +- The UE behaviour is unspecified in case more than two HS-SCCH orders are received simultaneously or contradictory HS-SCCH orders (i.e. orders for activation and deactivation of the same functionality) are received from the serving HS-DSCH cell and/or any of the secondary serving HS-DSCH cells during the same subframe. + +If the UE is configured in Multiflow mode + +- The UE shall simultaneously monitor an HS-SCCH set in each of the activated serving, assisting serving, secondary serving and assisting secondary serving HS-DSCH cells, and receive HS-DSCH if it is scheduled in that cell. The maximum size of the HS-SCCH set in any cell is 4 and the maximum number of HS-SCCHs monitored by the UE across + - both the serving HS-DSCH cell and the assisting serving HS-DSCH cell is 6 if the UE is capable of HS-DSCH reception in a maximum of 2 cells in Multiflow mode. + - the (secondary) serving HS-DSCH cell(s) and the assisting (secondary) serving HS-DSCH cell(s) is 9 if the UE is capable of HS-DSCH reception in a maximum of 3 cells in Multiflow mode. + - the (secondary) serving HS-DSCH cell(s) and the assisting (secondary) serving HS-DSCH cell(s) is 12 if the UE is capable of HS-DSCH reception in a maximum of 4 cells in Multiflow mode. +- From the serving HS-DSCH cell, the UE shall be able to receive up to one HS-DSCH if MIMO mode is not configured or two HS-DSCHs if MIMO mode is configured or one HS-SCCH order. +- In addition, from each of the assisting serving and the activated (assisting) secondary serving HS-DSCH cell(s), the UE shall be able to simultaneously receive up to one HS-DSCH if MIMO mode is not configured or two HS-DSCHs if MIMO mode is configured or one HS-SCCH order. +- HS-SCCH-less HS-DSCH transmission shall not be used in any cell other than the serving HS-DSCH cell. +- The UE behaviour is unspecified in case more than two HS-SCCH orders are received simultaneously or contradictory HS-SCCH orders (i.e. orders for activation and deactivation of the same functionality) are received simultaneously. + +The UE can be configured to simultaneously monitor a maximum of 1 HS-SCCH in one non-serving cell. This HS-SCCH is only used for HS-SCCH orders that indicate HS-DSCH serving cell change as defined in subclause 4.6C.2.2.1 in [2]. Upon successfully receiving an HS-SCCH order that indicates HS-DSCH serving cell change from this non-serving cell, the UE shall be able to start listening to the full configured HS-SCCH set from this new serving cell and from the new secondary serving HS-DSCH cells if configured by higher layers, at the activation time configured by higher layers if the activation time is not equal to “now”, or otherwise within 40 ms from the end of the subframe in which the HS-SCCH order is received. + +When the UE monitors HS-SCCHs, the UE shall only consider the control information to be consistent if either: + +- the decoded 'channelization-code-set information' is lower than or equal to 'maximum number of HS-DSCH codes received' in its UE capability and the decoded 'modulation scheme information' is valid in terms of its UE capability, + +or + +- the decoded 'channelization-code-set information' and decoded 'modulation scheme information' correspond to an indication of an HS-SCCH order as defined in [2] subclause 4.6C.2. + +Control information for one UE shall not be transmitted from the serving cell on more than one HS-SCCH in a single sub-frame. + +If a UE detects that one of the monitored HS-SCCHs in sub-frame $n$ carries consistent control information intended for this UE, the UE shall perform the following: + +- If the decoded 'channelization-code-set information' and decoded 'modulation scheme information' do not correspond to an indication of an HS-SCCH order, start receiving the HS-PDSCHs indicated by this consistent control information + +- If HS-DPCCH overhead reduction Type 2 and DPDCH are configured, the used\_CQI\_feedback\_cycle is set to CQI feedback cycle, and the “CQI cycle switch timer” is reset to CQI\_CYCLE\_SWITCH\_TIMER. +- If the CRC of the HS-SCCH is OK: + - If HS-SCCH\_less\_mode=1 and the TFRI value corresponds to the retransmissions of HS-SCCH-less operation, the transport block size information shall be derived from the signalled transport block size indicator as defined in [5] and [9]. + - Else if UE\_DTX\_DRX\_Enabled is TRUE or HS-SCCH\_less\_mode=1 or Secondary\_Cell\_Enabled is not 0 or UL\_CLTD\_Enabled is TRUE or UE is configured in MIMO mode with four transmit antennas or UE is configured in Multiflow mode or UE is configured in Enhanced TTI switching, and the ‘channelization-code-set information’ and ‘modulation scheme information’ correspond to an HS-SCCH order, the UE shall: + - if the TFRI value corresponds to an HS-SCCH order as defined in [2] subclause 4.6C.2, + - If the HS-SCCH order was sent by the serving HS-DSCH cell or by one of the secondary serving HS-DSCH cells, transmit ACK information in the slot allocated to the HARQ-ACK in the corresponding HS-DPCCH sub-frame as defined in [1] and [2]; + - Process the HS-SCCH orders as described in subclauses 6A.1, 6B, 6B.3.0, 6C.4, 10.6, 11.6 and 12.5. + - else, discard the information received on this HS-SCCH. + - Else, the transport block size information shall be derived from the signalled TFRI value as defined in [9]. + - If the 'Hybrid-ARQ process information' is not included in the set configured by upper layers, the UE shall discard the information received on this HS-SCCH and on the HS-PDSCHs. +- Else, if HS-SCCH\_less\_Active is TRUE, the UE may start receiving the HS-PDSCHs configured for HS-SCCH-less operation and attempt to decode the HS-DSCH bits based on the set of possible HS-DSCH transport block sizes configured for HS-SCCH-less operation. Otherwise, the UE shall discard the information received on this HS-SCCH and HS-PDSCH. + +Otherwise, if the UE does not detect consistent control information intended for this UE on any of the HS-SCCHs in its HS-SCCH sets, the UE shall perform the following: + +- the UE shall discard the information received on this HS-SCCH. +- if HS-SCCH\_less\_Active is TRUE, the UE shall start receiving the HS-PDSCHs configured for HS-SCCH-less operation and attempt to decode the HS-DSCH bits based on the set of possible HS-DSCH transport block sizes configured for HS-SCCH-less operation. +- otherwise, the UE shall discard the information received on the HS-PDSCHs. +- if HS-DPCCH overhead reduction Type 2 and DPDCH are configured, the “CQI cycle switch timer” is decremented by one. If the “CQI cycle switch timer” has expired, then the UE shall set the used\_CQI\_feedback\_cycle to CQI feedback cycle2. + +If UL\_DTX\_Active is TRUE (see clause 6C) and either of the following is true: + +- the UE detects consistent control information intended for this UE and the TFRI value does not correspond to an HS-SCCH order, or +- the UE has successfully decoded HS-PDSCHs intended for this UE; + +then, at the HS-DPCCH sub frame that contains or would contain the HARQ-ACK corresponding to the HS-SCCH or to the HS-PDSCHs that generated the priority change, the UE shall perform the following: + +- set CQI\_DTX\_Priority to 1 and, +- reset the CQI nominal reporting timer to CQI\_DTX\_TIMER. + +If HARQ\_preamble\_mode = 1 and the information received on HS-SCCH is not discarded, the UE shall: + +- transmit a HARQ Preamble (PRE for HS-DPCCH slot format 0 or PRE/PRE for HS-DPCCH slot format 1) in the slot allocated to HARQ-ACK in HS-DPCCH sub-frame $n - 1$ (if two HS-DPCCHs are active then a HARQ preamble is sent on each of HS-DPCCH and HS-DPCCH2), unless an ACK or NACK or any combination of ACK and NACK is to be transmitted in sub-frame $n - 1$ as a result of an HS-DSCH transmission earlier than sub-frame $n$ on the HS-PDSCH, and +- if $N\_acknack\_transmit > 1$ , the UE shall transmit a HARQ Preamble in the slot allocated to HARQ-ACK in HS-DPCCH sub-frame $n - 2$ (if two HS-DPCCHs are active then a HARQ preamble is sent on each of HS-DPCCH and HS-DPCCH2), unless an ACK or NACK or any combination of ACK and NACK is to be transmitted in sub-frame $n - 2$ as a result of an HS-DSCH transmission earlier than sub-frame $n$ on the HS-PDSCH. +- if $N\_acknack\_transmit\_2 > 1$ , the UE is configured in Multiflow mode and the HS-SCCH corresponds to an assisting serving or assisting secondary serving cell, then the UE shall transmit a HARQ Preamble in the slot allocated to HARQ-ACK in HS-DPCCH sub-frame $n - 2$ , unless an ACK or NACK or any combination of ACK and NACK is to be transmitted in sub-frame $n - 2$ as a result of an HS-DSCH transmission earlier than sub-frame $n$ on the HS-PDSCH. + +The UE shall transmit the ACK/NACK information received from MAC-hs or MAC-ehs in the slot allocated to the HARQ-ACK in the corresponding HS-DPCCH sub-frame as defined in [1] and [2]. + +When $N\_acknack\_transmit$ is greater than one, the UE shall: + +- repeat the transmission of the ACK/NACK information over the next ( $N\_acknack\_transmit - 1$ ) consecutive HS-DPCCH sub-frames, in the slots allocated to the HARQ-ACK as defined in [1] and +- not attempt to receive any HS-SCCH in HS-SCCH subframes corresponding to HS-DPCCH sub-frames in which the ACK/NACK information transmission is repeated, nor to receive or decode transport blocks from the HS-PDSCH in HS-DSCH sub-frames corresponding to HS-DPCCH sub-frames in which the ACK/NACK information transmission is repeated. + +When $N\_acknack\_transmit\_2 > 1$ and the UE is configured in Multiflow mode, the UE shall: + +- repeat the transmission of the ACK/NACK information for the assisting serving cell and if configured the assisting secondary serving cell over the next ( $N\_acknack\_transmit\_2 - 1$ ) consecutive HS-DPCCH sub-frames, in the slots allocated to the HARQ-ACK as defined in [1] and +- not attempt to receive any HS-SCCH in HS-SCCH subframes corresponding to HS-DPCCH sub-frames in which the ACK/NACK information transmission is repeated, nor to receive or decode transport blocks from the HS-PDSCH in HS-DSCH sub-frames corresponding to HS-DPCCH sub-frames in which the ACK/NACK information transmission is repeated. + +If ACK or NACK or any combination of ACK and NACK is transmitted in HS-DPCCH sub-frame $n$ , and $HARQ\_preamble\_mode = 1$ and $UE\ InterTTI \leq N\_acknack\_transmit$ , then the UE shall: + +- transmit a HARQ Postamble (POST for HS-DPCCH slot format 0 or POST/POST for HS-DPCCH slot format 1) in the slot allocated to HARQ-ACK in HS-DPCCH subframe $n + 2 * N\_acknack\_transmit - 1$ (if two HS-DPCCHs are active then a HARQ preamble is sent on each of HS-DPCCH and HS-DPCCH2), unless ACK or NACK or PRE or PRE/PRE or any combination of ACK and NACK is to be transmitted in this subframe, and +- if $N\_acknack\_transmit > 1$ , transmit a HARQ Postamble in the slot allocated to HARQ-ACK in HS-DPCCH subframe $n + 2 * N\_acknack\_transmit - 2$ (if two HS-DPCCHs are active then a HARQ preamble is sent on each of HS-DPCCH and HS-DPCCH2), unless an ACK or NACK or PRE or PRE/PRE or any combination of ACK and NACK is to be transmitted in this subframe. + +If the UE is configured in Multiflow mode and ACK or NACK or any combination of ACK and NACK is transmitted in HS-DPCCH sub-frame $n$ corresponding to an assisting serving or assisting secondary serving cell, and $HARQ\_preamble\_mode = 1$ and $UE\ InterTTI \leq N\_acknack\_transmit\_2$ , then the UE shall: + +- transmit a HARQ Postamble (POST/POST for HS-DPCCH slot format 1) in the slot allocated to HARQ-ACK in HS-DPCCH subframe $n + 2 * N\_acknack\_transmit\_2 - 1$ , unless ACK or NACK or PRE or PRE/PRE or any combination of ACK and NACK is to be transmitted in this subframe, and +- if $N\_acknack\_transmit\_2 > 1$ , transmit a HARQ Postamble in the slot allocated to HARQ-ACK in HS-DPCCH subframe $n + 2 * N\_acknack\_transmit\_2 - 2$ , unless an ACK or NACK or PRE or PRE/PRE or any combination of ACK and NACK is to be transmitted in this subframe. + +For the case where Secondary\_Cell\_Active is less than 4 when the UE is not configured in MIMO mode with four transmit antennas in any cell or is less than 2 when the UE is configured in MIMO mode with four transmit antennas in at least one cell DTX shall be used on the HS-DPCCH in the slot allocated to HARQ-ACK in the corresponding HS-DPCCH subframe unless a HARQ-ACK message is to be transmitted as described above. + +For the case where Secondary\_Cell\_Active is greater than 3 when the UE is not configured in MIMO mode with four transmit antennas in any cell or is greater than 1 when the UE is configured in MIMO mode with four transmit antennas in at least one cell DTX shall be used on HS-DPCCH and HS-DPCCH2 in the slot allocated to HARQ-ACK in each of the corresponding HS-DPCCH subframes unless a HARQ-ACK message is to be transmitted as described above on either of the HS-DPCCHs. If a HARQ-ACK message is to be transmitted on only one of the active HS-DPCCHs, the DTX codeword should be repeated in the HARQ-ACK field on the other HS-DPCCH in the corresponding HS-DPCCH subframe. + +#### 6A.1.1A UE procedure for receiving HS-DSCH and HS-SCCH in CELL\_FACH state + +The HS-SCCH reception procedure is as defined in subclause 6A.1.1. + +The UE shall perform these actions in the following order: + +- The UE shall monitor the first indexed HS-SCCH of the configured HS-SCCH set with the BCCH specific H-RNTI. +- If the UE is configured with a dedicated H-RNTI, the UE shall monitor the HS-SCCHs of the configured HS-SCCH set with the dedicated H-RNTI. If the UE is not configured with a dedicated H-RNTI, the UE shall monitor the HS-SCCHs of the configured HS-SCCH set with the common H-RNTI as defined in [5]. + +If the higher layers configure NodeB triggered HS-DPCCH transmission (as described in [5]) then NT-HS-DPCCH\_Enabled is set to TRUE. Otherwise, NT-HS-DPCCH\_Enabled is set to FALSE. + +If the UE detects that one HS-SCCH carries consistent control information intended for this UE, the UE shall perform the following: + +- If the decoded 'channelization-code-set information' and decoded 'modulation scheme information' do not correspond to an indication of an HS-SCCH order, start receiving the HS-PDSCHs indicated by this consistent control information. +- If the CRC of the HS-SCCH is OK: + - If the 'channelization-code-set information' and 'modulation scheme information' correspond to an HS-SCCH order as defined in [2] subclause 4.6C.3, + - if the TFRI value corresponds to an HS-SCCH order and the order mapping is as per subclause 4.6C.3.2.1, the UE shall process the HS-SCCH orders as described in subclause 6B. If NT-HS-DPCCH\_Enabled is TRUE, the UE shall not transmit the associated HARQ-ACK information acknowledging the HS-SCCH order. + - if the TFRI value corresponds to an HS-SCCH order and the order mapping is as per subclause 4.6C.3.2.2, the UE shall process the HS-SCCH order as described in [5]. + - else, discard the information received on this HS-SCCH + - Else, the transport block size information shall be derived from the signalled TFRI value as defined in [9]. If the 'Hybrid-ARQ process information' is not included in the set configured by upper layers, the UE shall discard the information received on this HS-SCCH and on the HS-PDSCHs. + +Otherwise, if the UE does not detect consistent control information intended for this UE on any of the HS-SCCHs, the UE shall discard the information received on this HS-SCCH and on the HS-PDSCHs. + +If HS-DPCCH transmission is indicated by higher layers, the HS-DPCCH transmission procedure as defined in subclauses 6A.1.1 and 6A.1.2 are followed. Otherwise, the UE shall not transmit any HARQ-ACK or CQI information and DTX shall be used on all the HS-DPCCH subframes. + +### 6A.1.1B UE procedure for receiving HS-DSCH and HS-SCCH in the URA\_PCH and CELL\_PCH states + +The HS-SCCH reception procedure is as defined in subclause 6A.1.1. + +If the UE has detected a paging indication intended for this UE, the UE shall perform the actions below: + +In CELL\_PCH state, if the UE is configured with a dedicated H-RNTI, the UE shall perform these actions in the following order: + +- The UE shall monitor the first indexed HS-SCCH of the configured HS-SCCH set with the BCCH specific H-RNTI. +- The UE shall monitor the HS-SCCHs of the configured HS-SCCH set with the dedicated H-RNTI. + +In CELL\_PCH state, if the higher layers configure NodeB triggered HS-DPCCH transmission (as described in [5]) then NT-HS-DPCCH\_Enabled is set to TRUE. Otherwise, NT-HS-DPCCH\_Enabled is set to FALSE. + +If the UE is configured with a dedicated H-RNTI, and if the UE detects that one HS-SCCH in a set of 5 associated HS-SCCH subframes (as defined in [1]) carries consistent control information intended for this UE, the UE shall perform the following: + +- If the decoded 'channelization-code-set information' and decoded 'modulation scheme information' do not correspond to an indication of an HS-SCCH order, start receiving the HS-PDSCHs indicated by this consistent control information. +- If the CRC of the HS-SCCH is OK, + - If the 'channelization-code-set information' and 'modulation scheme information' correspond to an HS-SCCH order as defined in [2] subclause 4.6C.3, + - if the TFRI value corresponds to an HS-SCCH order, the UE shall process the HS-SCCH orders as described in subclause 6B. If NT-HS-DPCCH\_Enabled is TRUE, the UE shall not transmit the associated HARQ-ACK information acknowledging the HS-SCCH order. + - else, discard the information received on this HS-SCCH +- Else, the transport block size information shall be derived from the signalled TFRI value as defined in [9]. If the 'Hybrid-ARQ process information' is not included in the set configured by upper layers, the UE shall discard the information received on this HS-SCCH and on the HS-PDSCHs. + +If the UE is configured with a dedicated H-RNTI and the UE does not detect consistent control information intended for this UE on any of the HS-SCCHs, the UE shall discard the information received on this HS-SCCH and on the HS-PDSCHs. + +In CELL\_PCH state, when the UE is configured to receive HS-DSCH without a dedicated H-RNTI, or in URA\_PCH state, the UE shall perform the following: + +- the UE shall start receiving the HS-PDSCH configured for HS-SCCH-less operation and attempt to decode the HS-DSCH bits of the first associated HS-DSCH sub-frame (as defined in [1]) and the subsequent repetitions in the (Number of PCCH transmissions-1) next contiguous HS-DSCH subframes based on the set of possible HS-DSCH Transport Block Sizes configured by higher layers. + +The UE shall not transmit any HARQ-ACK or CQI information and DTX shall be used on all the HS-DPCCH subframes. + +### 6A.1.2 UE procedure for reporting channel quality indication (CQI) and precoding control indication (PCI) + +The UE procedure for reporting PCI/CQI is given in subclause 6A.1.2.1 for the case when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in any cell, in subclause 6A.1.2.2 for the case when the UE is configured in MIMO mode in all cells, and in subclause 6A.1.2.3 for the case when the UE is configured in MIMO mode with four transmit antennas in all cells. + +If the UE is configured in MIMO mode in at least one cell, but not in all cells and is not configured in MIMO mode with four transmit antennas in any cell, then the overall PCI/CQI reporting procedure shall be the same as if the UE was configured in MIMO mode in all cells as specified in subclause 6A.1.2.2 except that a CQI value as defined in subclause 6A.2.1 is derived and reported for the non-MIMO cells. + +In the following subclauses, symbol $k$ represents the used CQI feedback cycle. The used CQI feedback cycle is always set to CQI feedback cycle, except when the HS-DPCCH overhead reduction Type 2 is configured, in which case the used CQI feedback cycle may change from the set value according to the rules defined in subclause 6A.1.1. When the UE is provided with a HS-DSCH configuration the used CQI feedback cycle is reset to CQI feedback cycle. + +#### 6A.1.2.1 CQI reporting procedure in case the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in any cell + +With the exception of the provisions of subclause 6A.3, the following shall apply when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas in any cell: + +- 1) The UE derives the CQI value for the serving HS-DSCH cell as defined in subclause 6A.2.1. + +If the UE is not configured in Multiflow mode and Secondary\_Cell\_Active is not 0, the UE also derives a CQI value for the activated secondary serving HS-DSCH cells as defined in subclause 6A.2.1. + +If the UE is configured in the Multiflow mode, the UE also derives the CQI values for the assisting serving and any activated secondary serving and assisting secondary serving HS-DSCH cells as defined in subclause 6A.2.1. + +The CQI report(s) are constructed from the CQI value(s) as specified in [2]. + +- 2) For $k = 0$ , the UE shall not transmit the CQI report(s). + +For $k > 0$ when DTX\_DRX\_STATUS is not TRUE, the UE shall transmit the CQI report containing the CQI value for the serving HS-DSCH cell in each subframe that starts $m \times 256$ chips after the start of the associated uplink DPCCH frame with $m$ fulfilling: + +$$(5 \times \text{CFN} + [m \times 256\text{chip}/7680\text{chip}]) \bmod \{k' = 0 \text{ with } k' = k/(2\text{ms})\},$$ + +where CFN denotes the connection frame number for the associated DPCH and the set of five possible values of $m$ is calculated as described in subclause 7.7 in [1]. + +For $k > 0$ when DTX\_DRX\_STATUS is TRUE, the UE shall transmit the CQI report containing the CQI value for the serving HS-DSCH cell as specified in 6C.2 based on the CQI transmission pattern. The CQI transmission pattern is the set of HS-DPCCH subframes whose HS-DPCCH discontinuous transmission radio frame number CFN\_DRX and subframe number S\_DRX, both defined in 6C.3, verify: + +$$((5 * \text{CFN\_DRX} - \text{UE\_DTX\_DRX\_Offset} + \text{S\_DRX}) \bmod k') = 0, \text{ with } k' = k/(2\text{ms}).$$ + +- 3) The UE shall repeat the transmission of the CQI report containing the CQI value for the serving HS-DSCH cell derived in 1) over the next $(N_{\text{cqi\_transmit}} - 1)$ consecutive HS-DPCCH sub frames in the slots respectively allocated to the CQI as defined in [1]. UE does not support the case of $k' < N_{\text{cqi\_transmit}}$ . + +- 4a) If Secondary\_Cell\_Enabled is less than 4, the UE is not in Multiflow mode, and if an additional CQI report is derived in 1), the UE shall transmit this CQI report over the next $N_{\text{cqi\_transmit}}$ consecutive HS-DPCCH sub frames immediately following the transmission of the CQI report in 2) and 3). UE does not support the case of $k' < 2 \cdot N_{\text{cqi\_transmit}}$ . + +- 4b) If Secondary\_Cell\_Enabled is 7 and Secondary\_Cell\_Active is 7 the UE shall for the activated cells + +- Transmit the CQI report containing the CQI value of the 4th secondary serving HS-DSCH cell simultaneously as the CQI report containing the CQI value of the serving HS-DSCH cell. +- Transmit the CQI report containing the CQI value of the 6th secondary serving HS-DSCH cell simultaneously as the CQI report containing the CQI value of the 2nd secondary serving HS-DSCH cell +- Transmit the CQI report containing the CQI value of the 5th secondary serving HS-DSCH cell simultaneously as the CQI report containing the CQI value of the 1st secondary serving HS-DSCH cell +- Transmit the CQI report containing the CQI value of the 7th secondary serving HS-DSCH cell simultaneously as the CQI report containing the CQI value of the 3rd secondary serving HS-DSCH cell + +The CQI report is transmitted over $(N\_cqi\_transmit - 1)$ consecutive HS-DPCCH sub frames. The UE does not support the case of $k' < 2 \cdot N_{cqi\_transmit}$ . + +4c) If Secondary\_Cell\_Enabled is greater than 3 and Secondary\_Cell\_Active is less than 7 the UE shall + +- For HS-DPCCH + - Transmit the CQI reports in the same slots as it would transmit the CQI reports if Secondary\_Cell\_Enabled is equal to 4 and the 1st, 2nd and 3rd secondary serving HS-DSCH cell were active. +- For HS-DPCCH2 + - Transmit the CQI report of the 4th secondary serving HS-DSCH cell (if present) so that it starts in the same slot as the transmissions of CQI report of the serving HS-DSCH starts. + - If at most one of the 4th, 5th, 6th or 7th secondary serving HS-DSCH cell is deactivated the transmissions of the CQI reports for the active secondary serving HS-DSCH cells occurs in the same slots as if Secondary\_Cell\_Active is equal to 7. + - If at most two of 4th, 5th, 6th and 7th secondary serving HS-DSCH cell are active the transmissions of the CQI reports associated with the active secondary serving HS-DSCH cell with lowest index as indicated by higher layers is transmitted in the CQI field of the subframe where the 4th and 6th secondary serving HS-DSCH cell would be transmitted if Secondary\_Cell\_Active is 7. The CQI report associated with the other secondary serving HS-DSCH cell (if present) is always transmitted in the subframe(s) immediately following the transmissions of the first CQI report. + +The CQI reports transmitted on HS-DPCCH2 are always over $(N\_cqi\_transmit - 1)$ consecutive HS-DPCCH sub frames. + +4d) If the UE is configured in the Multiflow mode + +- 4d.1) If the UE is configured with the Serving HS-DSCH and Assisting Serving HS-DSCH only, and neither of the cells is in MIMO mode, the combined CQI report is transmitted and repeated as defined in steps 2) and 3) and no other CQI reports are sent. The CQI reports are constructed from the CQI value(s) as specified in subclause 4.7.4.3.1, MF case 1 in table 15C.8 of [2] +- 4d.2) For all other non-MIMO Multiflow configurations, + - The UE shall transmit the CQI report(s) associated with the serving HS-DSCH cells as defined in step 2). + - If a MF case from 19 to 26 [2] is not configured, the UE shall transmit the CQI report(s) associated with the assisting serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the CQI report(s) for the serving HS-DSCH cells. + - If a MF case from 19 to 22 [2] is configured, the UE shall transmit the CQI reports associated with the 2nd secondary serving and assisting serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the CQI reports for the serving and 1st secondary serving HS-DSCH cells. + - If a MF case from 23 to 26 [2] is configured, the UE shall transmit the CQI reports associated with the 1st assisting secondary serving and 2nd assisting secondary serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the CQI reports for the serving and assisting serving HS-DSCH cells. + - The UE shall repeat the transmission of the CQI report(s) associated with the serving HS-DSCH cells $(N\_cqi\_transmit - 1)$ times in every other HS-DPCCH sub frame in the slots allocated to the CQI in accordance with the composite CQI report constructed in subclause 4.7.4.3 of [2]. + - The UE shall repeat the transmission of the CQI report(s) associated with the assisting serving HS-DSCH cells $(N\_cqi\_transmit - 2 - 1)$ times in every other HS-DPCCH sub frame in the slots allocated to the CQI in accordance with the composite CQI report constructed in subclause 4.7.4.3 of [2]. + - UE does not support the case of $k' < (N\_cqi\_transmit + N\_cqi\_transmit\_2)$ . + +- The CQI reports are constructed from the CQI value(s) as specified in subclause 4.7.4.3, MF cases 3 to 6, 11 to 14, 19 to 22 and 23 to 26 in tables 15C.10, 15C.11, 15C.14, 15C.16 and 15C.17 of [2]. +- 5) The UE shall not transmit CQI reports in other subframes than those described in 2), 3), 4a), 4b), 4c) and 4d). + +#### 6A.1.2.2 Composite PCI/CQI reporting procedure in case the UE is configured in MIMO mode + +The following types of CQI reports have to be supported by the UE when the UE is configured in MIMO mode and single-stream restriction is not configured: + +- Type A CQI reports that indicate the supported transport format(s) for the number of simultaneously transmitted transport blocks that the UE prefers according to the current channel conditions assuming that the preferred primary precoding vector as indicated by the PCI value signalled in the same HS-DPCCH sub-frame would be applied at the Node-B for the primary transport block and in case two transport blocks are preferred the precoding vector orthogonal to the preferred primary precoding vector would be applied for the secondary transport block. This type of CQI report contains information on either one transport format or a combination of two transport formats depending on what is currently the preferred number of transport blocks (either 1 or 2). +- Type B CQI reports that indicate the supported transport format for a single transmitted transport block according to the current channel conditions assuming that the preferred primary precoding vector as indicated by the PCI value signalled in the same HS-DPCCH sub-frame would be applied at the Node-B for the primary transport block and that no secondary transport block is transmitted. + +When UE is configured in MIMO mode and single-stream restriction is configured only type B CQI report have to be supported by the UE. + +With the exception of the provisions of subclause 6A.3, the following shall apply when the UE is configured in MIMO mode: + +- 1) The UE derives the PCI value for the serving HS-DSCH cell as defined in subclause 6A.4.1 and when single-stream restriction is not configured either a type A or a type B CQI value and when single-stream restriction is configured type B CQI value for the serving HS-DSCH cell as defined in subclause 6A.2.2 depending on which type of CQI shall be reported as defined below. + +If UE is not configured in Multiflow mode and Secondary\_Cell\_Active is not 0, the UE also derives a PCI value for the activated secondary serving HS-DSCH cell(s) as defined in subclause 6A.4 and when single-stream restriction is not configured either a type A or a type B CQI value and when single-stream restriction is configured type B CQI value for the secondary serving HS-DSCH cell as defined in subclause 6A.2.2 depending on which type of CQI shall be reported as defined below. + +If the UE is configured in the Multiflow mode, + +- the UE also derives a PCI value for the assisting serving and any activated secondary serving and assisting secondary serving HS-DSCH cells as defined in subclause 6A.4 if the UE is configured in MIMO mode in that cell, +- and when single-stream restriction is not configured, either type A or type B CQI value, and when single-stream restriction is configured, type B CQI value for the assisting serving and any activated secondary serving and assisting secondary serving HS-DSCH cells as defined in subclause 6A.2.2 depending on which type of CQI shall be reported. + +The PCI/CQI report(s) in each subframe are constructed from the composite PCI/CQI value(s) as specified in [2]. + +2) + +- a) For $k = 0$ , the UE shall not transmit a composite PCI/CQI value. +- b) For $k > 0$ when DTX\_DRX\_STATUS is not TRUE (see subclause 6A.1), the UE shall transmit the composite PCI/CQI value(s) for the cells in the PCI/CQI report containing the composite PCI/CQI value for the serving HS-DSCH cell in each subframe that starts $m \times 256$ chips after the start of the associated uplink DPCCH frame with $m$ fulfilling + +$$(5 \times \text{CFN} + [m \times 256\text{chip}/7680\text{chip}]) \bmod \{k' = 0 \text{ with } k' = k/(2\text{ms})\}, \quad (\text{x1})$$ + +where CFN denotes the connection frame number for the associated DPCH and the set of five possible values of $m$ is calculated as described in subclause 7.7 in [1]. + +When single-stream restriction is not configured and the relation + +$$\left\lfloor \frac{5 \times \text{CFN} + \lfloor m \times 256 \text{ chip} / 7680 \text{ chip} \rfloor}{k'} \right\rfloor \bmod M\_cqi < N\_cqi\_typeA$$ + +holds, the UE shall report a type A CQI value. Otherwise the UE shall report a type B CQI value. + +- c) For $k > 0$ when DTX\_DRX\_STATUS is TRUE (see subclause 6A.1), the UE shall transmit the CQI value for the cells in the PCI/CQI report containing the composite PCI/CQI value for the serving HS-DSCH cell as specified in 6C.2 based on the CQI transmission pattern. The CQI transmission pattern is the set of HS-DPCCH subframes whose HS-DPCCH discontinuous transmission radio frame number CFN\_DRX and subframe number S\_DRX, both defined in 6C.3, verify: + +$$((5 * \text{CFN\_DRX} - \text{UE\_DTX\_DRX\_Offset} + \text{S\_DRX}) \bmod k') = 0, \text{ with } k' = k / (2 \text{ ms}).$$ + +When single-stream restriction is not configured and the relation + +$$\left\lfloor \frac{5 \times \text{CFN\_DRX} - \text{UE\_DTX\_DRX\_Offset} + \text{S\_DRX}}{k'} \right\rfloor \bmod M\_cqi < N\_cqi\_typeA$$ + +holds, the UE shall report a type A CQI value. Otherwise the UE shall report a type B CQI value. + +- d) For $k > 0$ , each PCI value derived in 1) shall be transmitted together with the corresponding CQI value as a composite PCI/CQI value. It should be noted that in case that 2560 is not an integer multiple of $M\_cqi$ , the sequence of type A and type B CQI reports might not always be periodic due to CFN roll-over. +- 3) The UE shall repeat the transmission of the CQI report containing the composite PCI/CQI value for the serving HS-DSCH cell derived above over the next $(N\_cqi\_transmit - 1)$ consecutive HS-DPCCH sub frames in the slots respectively allocated to CQI as defined in [1]. The UE does not support the case of $k' < N\_cqi\_transmit$ . +- 4a) If Secondary\_Cell\_Enabled is less than 4, the UE is not in Multiflow mode, and if an additional PCI/CQI report is derived in 1), the UE shall transmit this PCI/CQI report over the next $N\_cqi\_transmit$ consecutive HS-DPCCH sub frames immediately following the transmission of the CQI report in 2) and 3). UE does not support the case of $k' < 2 \cdot N\_cqi\_transmit$ . +- 4b) If Secondary\_Cell\_Enabled is 7 and Secondary\_Cell\_Active is 7 the UE shall: +- Transmit the PCI/CQI report containing the PCI/CQI value of the 4th secondary serving HS-DSCH cell simultaneously as the PCI/CQI report containing the PCI/CQI value of the serving HS-DSCH cell. + - Transmit the PCI/CQI report containing the PCI/CQI value of the 6th secondary serving HS-DSCH cell simultaneously as the PCI/CQI report containing the PCI/CQI value of the 2nd secondary serving HS-DSCH cell + - Transmit the PCI/CQI report containing the PCI/CQI value of the 5th secondary serving HS-DSCH cell simultaneously as the PCI/CQI report containing the PCI/CQI value of the 1st secondary serving HS-DSCH cell + - Transmit the PCI/CQI report containing the PCI/CQI value of the 7th secondary serving HS-DSCH cell simultaneously as the PCI/CQI report containing the PCI/CQI value of the 3rd secondary serving HS-DSCH cell + +The PCI/CQI report is transmitted over $(N\_cqi\_transmit - 1)$ consecutive HS-DPCCH sub frames. The UE does not support the case of $k' < 2 \cdot N\_cqi\_transmit$ . + +- 4c) If Secondary\_Cell\_Enabled is greater than 3 and Secondary\_Cell\_Active is less than 7 the UE shall: + +- For HS-DPCCH + - Transmit the PCQ/CQI reports in the same slots as it would transmit the PCI/CQI reports if Secondary\_Cell\_Enabled is equal to 4 and the same of the 1st, 2nd and 3rd secondary serving HS-DSCH cell were active. +- For HS-DPCCH2 + +- Transmit the PCI/CQI report of the 4th secondary serving HS-DSCH cell (if present) so that it starts in the same slot as the transmissions of PCI/CQI report of the serving HS-DSCH cell starts. +- If at most one of the 4th, 5th, 6th or 7th secondary serving HS-DSCH cell is deactivated the transmissions of the PCI/CQI reports for the active secondary serving HS-DSCH cells occurs in the same slots as if Secondary\_Cell\_Active is equal to 7. +- If at most two of 4th, 5th, 6th and 7th secondary serving HS-DSCH cell are active the transmissions of the PCI/CQI reports associated with the active secondary serving HS-DSCH cell with lowest index as indicated by higher layers is transmitted in the PCI/CQI field of the subframe where the 4th and 6th secondary serving HS-DSCH cell would be transmitted if Secondary\_Cell\_Active is 7. The PCI/CQI report associated with the other secondary serving HS-DSCH cell (if present) is always transmitted in the subframe(s) immediately following the transmissions of the first PCI/CQI report. + +The PCI/CQI reports transmitted on HS-DPCCH2 are always over ( $N\_cqi\_transmit-1$ ) consecutive HS-DPCCH sub frames. + +4d) If the UE is configured in the Multiflow mode, + +- The UE shall transmit the PCI/CQI report(s) associated with the serving HS-DSCH cells as defined in step 2). + - If a MF case from 27 to 34 [2] is not configured, the UE shall transmit the PCI/CQI report(s) associated with the assisting serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the PCI/CQI report(s) for the serving HS-DSCH cells. + - If a MF case from 27 to 30 [2] is configured, the UE shall transmit the PCI/CQI reports associated with the 2nd secondary serving and assisting serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the PCI/CQI reports for the serving and 1st secondary serving HS-DSCH cells. + - If a MF case from 31 to 34 [2] is configured, the UE shall transmit the PCI/CQI reports associated with the 1st assisting secondary serving and 2nd assisting secondary serving HS-DSCH cells in the next HS-DPCCH subframe immediately following the PCI/CQI reports for the serving and assisting serving HS-DSCH cells. + - The UE shall repeat the transmission of the PCI/CQI report(s) associated with the serving HS-DSCH cells ( $N\_cqi\_transmit - 1$ ) times in every other HS-DPCCH sub frame in the slots allocated to the PCI/CQI in accordance with the composite PCI/CQI report constructed in subclause 4.7.4.3 of [2]. + - The UE shall repeat the transmission of the PCI/CQI report(s) associated with the assisting serving HS-DSCH cells ( $N\_cqi\_transmit\_2 - 1$ ) times in every other HS-DPCCH sub frame in the slots allocated to the PCI/CQI in accordance with the composite PCI/CQI report constructed in subclause 4.7.4.3 of [2]. + - UE does not support the case of $k' < (N\_cqi\_transmit + N\_cqi\_transmit\_2)$ . + - The PCI/CQI reports are constructed from the PCI/CQI value(s) as specified in subclause 4.7.4.3, MF cases 2, 7...10, 15...18, 27...30 and 31...34 in tables 15C.9, 15C.12, 15C.13, 15C.15, 15C.18 and 15C.19 of [2]. +- 5) The UE shall not transmit PCI/CQI reports in other subframes than those described in 2), 3) , 4a), 4b), 4c) and 4d). + +#### 6A.1.2.3 Composite NTBP/PCI/CQI reporting procedure in case the UE is configured in MIMO mode with four transmit antennas + +The following types of CQI reports have to be supported by the UE when the UE is configured in MIMO mode with four transmit antennas: + +Type A: + +CQI reports that indicate the supported transport format(s) for the number of simultaneously transmitted transport blocks that the UE prefers according to the current channel conditions assuming that the preferred precoding + +matrix as indicated by the PCI value signalled in the same HS-DPCCH sub-frame would be applied at the Node-B. + +##### Type B: + +CQI reports that indicate the supported transport format for a single transmitted transport block according to the current channel conditions assuming that the preferred precoding vector as indicated by the PCI value signalled in the same HS-DPCCH sub-frame would be applied at the Node-B for the primary transport block and that no second, third, and fourth transport blocks are transmitted. + +With the exception of the provisions of subclause 6A.3, the following shall apply when the UE is configured in MIMO mode with four transmit antennas: + +- 1) The UE derives the NTBP, PCI value for the serving HS-DSCH cell as defined in subclause 6A.4.2 and either a type A or a type B CQI value for the serving HS-DSCH cell depending on which type of CQI shall be reported as defined below. + +If Secondary\_Cell\_Active is not 0, the UE also derives NTBP, PCI value for the activated secondary serving HS-DSCH cell(s) as defined in subclause 6A.4.1 and 6A.4.2 and either a type A or a type B CQI value for the secondary serving HS-DSCH cell depending on which type of CQI shall be reported as defined below. + +The NTBP/PCI/CQI report(s) in each subframe are constructed from the composite NTBP/PCI/CQI value(s) as specified in [2]. + +- 2) + +- a) For $k = 0$ , the UE shall not transmit a composite NTBP/PCI/CQI value. +- b) For $k > 0$ when DTX\_DRX\_STATUS is not TRUE (see subclause 6A.1), the UE shall transmit the composite NTBP/PCI/CQI value(s) for the cells in the NTBP/PCI/CQI report containing the composite NTBP/PCI/CQI value for the serving HS-DSCH cell in each subframe that starts $m \times 256$ chips after the start of the associated uplink DPCCH frame with $m$ fulfilling + +$$(5 \times \text{CFN} + [m \times 256\text{chip}/7680\text{chip}]) \bmod \{k' = 0 \text{ with } k' = k/(2\text{ms})\}, \quad (\text{x1})$$ + +where CFN denotes the connection frame number for the associated DPCH and the set of five possible values of $m$ is calculated as described in subclause 7.7 in [1]. + +- c) For $k > 0$ when DTX\_DRX\_STATUS is TRUE (see subclause 6A.1), the UE shall transmit the CQI value for the cells in the NTBP/PCI/CQI report containing the composite NTBP/PCI/CQI value for the serving HS-DSCH cell as specified in 6C.2 based on the CQI transmission pattern. The CQI transmission pattern is the set of HS-DPCCH subframes whose HS-DPCCH discontinuous transmission radio frame number CFN\_DRX and subframe number S\_DRX, both defined in 6C.3, verify: + +$$((5 * \text{CFN\_DRX} - \text{UE\_DTX\_DRX\_Offset} + \text{S\_DRX}) \bmod k') = 0, \text{ with } k' = k/(2\text{ms}).$$ + +- d) For $k > 0$ , each NTBP/PCI value derived in 1) shall be transmitted together with the corresponding CQI value as a composite PCI/CQI value. It should be noted that in case that 2560 is not an integer multiple of $M_{\text{cqi}}$ , the sequence of type A and type B CQI reports might not always be periodic due to CFN roll-over. + +- 3) The UE shall repeat the transmission of the CQI report containing the composite NTBP/PCI/CQI value for the serving HS-DSCH cell derived above over the next $(N_{\text{cqi\_transmit}} - 1)$ consecutive HS-DPCCH sub frames in the slots respectively allocated to CQI as defined in [1]. The UE does not support the case of $k' < N_{\text{cqi\_transmit}}$ . + +- 4a) If Secondary\_Cell\_Enabled is less than 2, and if an additional NTBP/PCI/CQI report is derived in 1), the UE shall transmit this NTBP/PCI/CQI report over the next $N_{\text{cqi\_transmit}}$ consecutive HS-DPCCH sub frames immediately following the transmission of the CQI report in 2) and 3). UE does not support the case of $k' < 2 \cdot N_{\text{cqi\_transmit}}$ . + +- 4b) If Secondary\_Cell\_Enabled is 3 and Secondary\_Cell\_Active is 3 the UE shall: + +- Transmit the NTBP/PCI/CQI report containing the NTBP/PCI/CQI value of the 2nd secondary serving HS-DSCH cell simultaneously as the NTBP/PCI/CQI report containing the NTBP/PCI/CQI value of the serving HS-DSCH cell. + +- Transmit the NTBP/PCI/CQI report containing the NTBP/PCI/CQI value of the 3rd secondary serving HS-DSCH cell simultaneously as the NTBP/PCI/CQI report containing the NTBP/PCI/CQI value of the 1st secondary serving HS-DSCH cell. + +The NTBP/PCI/CQI report is transmitted over ( $N_{cqitransmit}$ ) consecutive HS-DPCCH sub frames. The UE does not support the case of $k' < 2 \cdot N_{cqitransmit}$ . + +- 5) The UE shall not transmit NTBP/PCI/CQI reports in other subframes than those described in 2), 3) , 4a) and 4b). + +### 6A.1.3 Node B procedure for transmitting the HS-DSCH and HS-SCCH + +#### 6A.1.3.1 Node B procedure for transmitting the HS-DSCH and HS-SCCH in the CELL\_DCH state + +When transmitting to a UE for which the HS-SCCH\_less\_mode=1, the Node B shall use the following procedures: + +- The Node B can always transmit an HS-DSCH transport block using CRC attachment method 1 and HS-SCCH type 1. +- If HS-SCCH\_less\_Active is TRUE, the Node B may transmit an HS-DSCH transport block using CRC attachment method 2 and HS-SCCH type 2 according to [2] provided that the size of the transport block belongs to the set of transport block sizes configured for HS-SCCH less operation by higher layers. In this case, a maximum of two retransmissions may be used for each HS-DSCH transport block. + +Otherwise, + +- The Node B should always transmit an HS-DSCH transport block using CRC attachment method 1 and + - HS-SCCH type 1 in a cell where the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas, or + - HS-SCCH type 3 in a cell where the UE is configured in MIMO mode, or + - HS-SCCH type 4 in a cell where the UE is configured in MIMO mode with four transmit antennas. + +If Node B uses CRC attachment method 1 or CRC attachment method 2 for the first transmission of a transport block, Node B shall use CRC attachment method 1 or CRC attachment method 2 respectively for any retransmission of the transport block. + +When transmitting/retransmitting, in a cell where the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas, a transport block using CRC attachment method 1 or retransmitting a transport block to a UE using CRC attachment method 2, the Node B shall transmit the corresponding control information using HS-SCCH type 1 or HS-SCCH type 2 respectively on one of the HS-SCCHs in the UE's HS-SCCH set. + +When transmitting/retransmitting, in a cell where the UE is configured in MIMO mode, a transport block the Node B shall use CRC attachment method 1 and transmit the corresponding control information using HS-SCCH type 3 on one of the HS-SCCHs in the UE's HS-SCCH set. + +When transmitting/retransmitting, in a cell where the UE is configured in MIMO mode with four transmit antennas, the Node B shall use CRC attachment method 1 and transmit the corresponding control information using HS-SCCH type 4 on one of the HS-SCCHs in the UE's HS-SCCH set. + +If the Simplified HS-SCCH type 1 operation is configured, once a UE has reported a low CQI value over the HS-DPCCH (i.e., CQI values from 1 to 6), the UE may assume that a HS-SCCH Type 1 transmission carrying control information corresponding to 1 code and QPSK would be transmitted in the first available HS-SCCH subframe once four sub-frames have passed after the end of the sub-frame where the HS-DPCCH was transmitted. + +- The HS-SCCH orders described in [2] subclause 4.6C.2.2.5, which upon their successful reception shall be acknowledged by the UE, can be used to start and stop a transmission interval within which any scheduled HS-SCCH Type 1 transmission will carry control information corresponding to 1 code and QPSK. While the UE is within such a transmission interval, once the UE has reported a CQI value over the HS-DPCCH (i.e. any value), the UE may assume that a HS-SCCH Type 1 transmission carrying control information corresponding to 1 code and QPSK would be transmitted in the first available HS-SCCH subframe once four sub-frames have passed after the end of the sub-frame where the HS-DPCCH was transmitted. When the network has transmitted a HS- + +SCCH order for stopping the transmission interval created by the HS-SCCH orders, a fall back to the CQI based triggering mechanism occurs. + +#### 6A.1.3.2 Node B procedure for transmitting the HS-DSCH and HS-SCCH in the CELL\_FACH state + +When transmitting to a UE the Node B shall use the following procedures: + +- The Node B shall always transmit an HS-DSCH transport block using CRC attachment method 1 and HS-SCCH type 1. +- When transmitting/retransmitting a transport block the Node B shall transmit the corresponding control information using HS-SCCH type 1 on one of the HS-SCCHs in the configured HS-SCCH set. When transmitting/retransmitting a transport block with the BCCH specific H-RNTI, the Node B shall use the first indexed HS-SCCH of the configured HS-SCCH set. +- When the NodeB transmits an HS-SCCH order as defined in [2] subclause 4.6C.3.2.2, the NodeB shall start transmitting the HS-SCCH associated with the HS-DSCH four sub-frames after the end of the sub-frame where the HS-SCCH order was transmitted. The UE monitors the reception of the HS-SCCH order as specified in [5]. + +#### 6A.1.3.3 Node B procedure for transmitting the HS-DSCH and HS-SCCH in the URA\_PCH or CELL\_PCH state + +The timing relation of the PICH frame to the first associated HS-SCCH subframe and its associated HS-DSCH subframe is described in 7.2A of [1]. + +In CELL\_PCH state, when transmitting with a dedicated H-RNTI or BCCH specific H-RNTI, the Node B shall use the following procedures: + +- The Node B may transmit HS-SCCH type 1 in any of the 5 HS-SCCH subframes associated with the PICH frame (as defined in [1]), and the corresponding HS-DSCH transport block using CRC attachment method 1 in the associated HS-DSCH subframe. When transmitting with the BCCH specific H-RNTI, the Node B shall use the first indexed HS-SCCH of the configured HS-SCCH set. +- The Node B may retransmit the HS-DSCH in any of the subsequent sub-frames associated with the PICH (as defined in [1]). All retransmissions shall be sent with HS-SCCH type 1. +- The Node B may also transmit an HS-SCCH order, as defined in [2] subclause 4.6C.3, in any of the 5 HS-SCCH subframes associated with the PICH frame (as defined in [1]). + +In CELL\_PCH state, when transmitting to a UE not configured with a dedicated H-RNTI, or in URA\_PCH state, the Node B shall use the following procedures: + +- The Node B shall not transmit an HS-SCCH. +- The Node B shall transmit an HS-DSCH transport block in the HS-DSCH subframe associated with the first associated HS-SCCH subframe, with the following parameters: + - QPSK modulation + - HS-PDSCH channelisation code configured for HS-SCCH less paging operation by higher layers + - CRC attachment method 1 for the HS-DSCH + - the size of the transport block belongs to the set of transport block sizes configured for HS-SCCH less paging operation by higher layers. +- The Node B shall retransmit the HS-DSCH transport block (Number of PCCH transmissions-1) times in the next contiguous subframes without transmitting HS-SCCH. +- For the first, second, third, fourth and fifth transmissions, the redundancy and constellation version of the HS-DSCH transport block are 0, 2, 5, 6, and 1, respectively. + +## 6A.2 Channel quality indicator (CQI) definition + +Any overlap between the 3-slot reference period (as defined in either 6A.2.1 or 6A.2.2 or 6A.2.2A) and a DRX period (as defined in subclause 6C.3) shall not prevent the UE transmitting a CQI report. + +### 6A.2.1 CQI definition when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas + +This definition of CQI applies only when the UE is not configured in MIMO mode and not configured in MIMO mode with four transmit antennas. + +Based on an unrestricted observation interval, the UE shall report the highest tabulated CQI value for which a single HS-DSCH sub-frame formatted with the transport block size, number of HS-PDSCH codes and modulation corresponding to the reported or lower CQI value could be received with a transport block error probability not exceeding 0.1 in a 3-slot reference period ending 1 slot before the start of the first slot in which the reported CQI value is transmitted. Depending on the UE category as derived by higher layers in [5], either Table 7A, 7B, 7C, 7D, 7E, 7F or 7G should be used. + +For the purpose of CQI reporting, the UE shall assume a total received HS-PDSCH power of $P_{HSPDSCH} = P_{CPICH} + \Gamma + \Delta$ in dB, + +where the total received power is evenly distributed among the HS-PDSCH codes of the reported CQI value, the measurement power offset $P_{offset}$ is signalled by higher layers and the reference power adjustment $\Delta$ is given by Table 7A, 7B, 7C, 7D, 7E, 7F or 7G depending on the UE category. + +Further, for the purpose of CQI reporting, the UE shall assume the number of soft channel bits available in the virtual IR buffer ( $N_{IR}$ ), and redundancy and constellation version parameter ( $X_{RV}$ ) as given by Table 7A, 7B, 7C, 7D, 7E, 7F or 7G depending on the UE category irrespective of the actual number of HARQ processes that are configured. The indicated HSDPA category applies independent of whether the UE is configured in Multiflow mode or not. + +If higher layer signalling informs the UE that for the relevant radio link (i.e. the radio link from the serving HS-DSCH cell in the case of a CQI value for the serving HS-DSCH cell, or the radio link from a secondary serving HS-DSCH cell in the case of a CQI value for a secondary serving HS-DSCH cell) it may use a S-CPICH as a phase reference and the + +P-CPICH is not a valid phase reference, $\sum_{i=0}^{N-1} |x^{(i)}|^2$ is the received power of the S-CPICH used by the UE, otherwise + +$\sum_{i=0}^{N-1} |x^{(i)}|^2$ is the received power of the P-CPICH. In the case of a CQI value for the serving HS-DSCH cell, if closed loop + +transmit diversity is used for the radio link from the serving HS-DSCH cell, $\sum_{i=0}^{N-1} |x^{(i)}|^2$ denotes the power of the combined received CPICH from both transmit antennas, determined as if error-free transmitter weights had been applied to the + +CPICH, where those weights are determined as described in subclause 7.2. If STTD is used, $\sum_{i=0}^{N-1} |x^{(i)}|^2$ denotes the + +combined CPICH power received from each transmit antenna and if no transmit diversity is used $\sum_{i=0}^{N-1} |x^{(i)}|^2$ denotes the power received from the non diversity antenna. + +For the purpose of CQI reporting the UE shall assume that all HS-PDSCH channelisation codes it may receive from the relevant radio link are under the same scrambling code as the Common Pilot Channel used to determine $\sum_{i=0}^{N-1} |x^{(i)}|^2$ . + +### 6A.2.2 CQI definition when the UE is configured in MIMO mode + +This definition of CQI applies only when the UE is configured in MIMO mode. + +Based on an unrestricted observation interval, the UE shall report the highest tabulated CQI value(s) for which a single HS-DSCH sub-frame formatted with the set of transport block size(s), number of HS-PDSCH codes and set of modulation(s) corresponding to the reported CQI value(s) could be received with individual transport block error probabilities not exceeding 0.1 in a 3-slot reference period ending 1 slot before the start of the first slot in which the reported CQI value(s) is/are transmitted if the preferred primary precoding vector as indicated by the PCI value reported in the same HS-DPCCH sub-frame would be applied at the Node B for the primary transport block and in case two transport blocks are preferred the precoding vector orthogonal to the preferred primary precoding vector would be applied for the secondary transport block. When single-stream restriction is not configured and depending on the UE category as derived by higher layers [5], either Table 7H, 7I, 7Ia or 7Ib shall be used for dual transport block type A CQI reports, and either Table 7C, 7D, 7F or 7G shall be used for single transport block type A or type B CQI reports. + +Type A CQI reports are constructed using a CQI value that is computed according to + +$$\text{CQI} = \begin{cases} 15 \times \text{CQI}_1 + \text{CQI}_2 + 31 & \text{when 2 transport blocks are preferred by the UE} \\ \text{CQI}_S & \text{when 1 transport block is preferred by the UE} \end{cases},$$ + +where $\text{CQI}_1$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the transport block that could be received with the specified block error probability if it was transmitted with the preferred primary precoding vector and $\text{CQI}_2$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the transport block that could be received with the specified block error probability if it was transmitted with the precoding vector orthogonal to the preferred primary precoding vector. $\text{CQI}_S$ indicates the supported transport format according to Table 7C, 7D, 7F or 7G for the transport block that could be received with the specified block error probability if it was transmitted with the preferred primary precoding vector. + +When single-stream restriction is not configured type B CQI reports are constructed using the CQI value of the supported transport format according to Table 7C, 7D, 7F or 7G for the transport block that could be received with the specified block error probability if it was transmitted with the preferred primary precoding vector. + +When single-stream restriction is configured type B CQI reports are constructed using the CQI value of the supported transport format according to Table 7A, 7B, 7C, 7D, 7F or 7G for the transport block that could be received with the specified block error probability if it was transmitted with the preferred primary precoding vector. + +For the purpose of CQI reporting, the UE shall assume a total transmit power of HS-PDSCH + +$$P_{\text{HSPDSCH}} = P_{\text{CPICH}} + \Gamma \text{ in dB},$$ + +where the total transmit power is assumed to be evenly distributed among the HS-PDSCH codes corresponding to the reported CQI value, and the measurement power offset ![power offset icon](2ff238be5d86662d1213fe4dadd67c96_img.jpg) is signaled by higher layers. ![combined transmit power icon](a190fc2966c8406e81e2dfa7fbdd232d_img.jpg) denotes the combined transmit power of the set of CPICH(s) used for MIMO operation of HS-DSCH. + +When single-stream restriction is not configured and if a CQI for a single transport block is reported, the parameter $\Delta$ that is given by Table 7C, 7D, 7F or 7G depending on the UE category and configuration indicates a reference power adjustment for the Node B transmit power on the indicated HS-PDSCH(s). If a CQI for two transport blocks is reported, the parameter $\Delta$ that is given by Table 7H, 7I, 7Ia or 7Ib depending on the UE category and configuration indicates by how much the equivalent AWGN symbol SINR for a specific transport block would be different from the one required to meet the predicted BLER performance. + +When single-stream restriction is configured, the parameter $\Delta$ that is given by Table 7A, 7B, 7C, 7D, 7F or 7G depending on the UE category and configuration indicates a reference power adjustment for the Node B transmit power on the indicated HS-PDSCH(s). + +When deriving the CQI value, the UE assumes that the Node B would be using a uniform power allocation across the number of HS-PDSCH codes corresponding to the CQI value to be reported. In case the UE reports a CQI for two transport blocks, it is assumed by the UE that the Node B uses an equal power per HS-PDSCH code for both of the two transport blocks. + +When the Node B schedules the UE with two transport blocks, if the Node B does not transmit with equal power per used HS-PDSCH code or use different power per code than indicated by the measurement power offset ![power offset icon](08ff9a984e4ab22be72c62ad9f39a4f3_img.jpg), it should not assume that the reported transport block sizes can be received with the specified block error probabilities or that transmission of two transport blocks is preferred by the UE. + +Further, for the purpose of CQI reporting, the UE shall assume the number of soft channel bits available in the virtual IR buffer ( $N_{\text{IR}}$ ), and redundancy and constellation version parameter ( $X_{\text{rv}}$ , $X_{\text{rvpb}}$ , or $X_{\text{rvsb}}$ ) as given by Table 7A, 7B, 7C, 7D, 7F, 7G, 7H, 7I, 7Ia or 7Ib depending on the UE category and on the CQI report type irrespective of the actual number of HARQ processes that are configured. + +For the purpose of CQI reporting the UE shall assume that all HS-PDSCH channelisation codes it may receive are under the same scrambling code as the set of CPICH(s) used to determine $P_{\text{CPICH}}$ . + +#### 6A.2.2A CQI definition when the UE is configured in MIMO mode with four transmit antennas + +This definition of CQI applies only when the UE is configured in MIMO mode with four transmit antennas. + +Based on an unrestricted observation interval, the UE shall report the highest tabulated CQI value(s) for which a single HS-DSCH sub-frame formatted with the set of transport block size(s), number of HS-PDSCH codes and set of modulation(s) corresponding to the reported CQI value(s) could be received with individual transport block error probabilities not exceeding 0.1 in a 3-slot reference period ending 1 slot before the start of the first slot in which the reported CQI value(s) is/are transmitted if the preferred precoding matrix as indicated by the PCI value reported in the same HS-DPCCH sub-frame that would be applied at the Node B on transport blocks as indicated by the UE. Either Table 7H, 7I, 7Ia or 7Ib shall be used for two, three or four transport block type A CQI reports, and either Table 7C, 7D, 7F or 7G shall be used for single transport block type A or type B CQI reports. + +Type A CQI reports are constructed using a CQI value that is computed according to + +$$\text{CQI} = \begin{cases} 15 \times \text{CQI}_1 + \text{CQI}_2 & \text{when 2, 3, 4 transport blocks are preferred by the UE} \\ \text{CQI}_S & \text{when 1 transport block is preferred by the UE} \end{cases}$$ + +When the number of transport blocks preferred by the UE is equal to four, $\text{CQI}_1$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the primary and fourth transport blocks that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix and $\text{CQI}_2$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the second and third transport blocks that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix. + +When the number of transport blocks preferred by the UE is equal to three, $\text{CQI}_1$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the primary transport block that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix and $\text{CQI}_2$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the second and third transport blocks that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix. + +When the number of transport blocks preferred by the UE is equal to two, $\text{CQI}_1$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the primary transport block that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix and $\text{CQI}_2$ indicates the supported transport format according to Table 7H, 7I, 7Ia or 7Ib for the second transport block that could be received with the specified block error probability if it was transmitted with the preferred precoding matrix. + +When the number of transport blocks preferred by the UE is equal to one, $\text{CQI}_S$ indicates the supported transport format according to Table 7C, 7D, 7F or 7G for the transport block that could be received with the specified block error probability if it was transmitted with the preferred precoding vector. + +Type B CQI reports are constructed using the CQI value of the supported transport format according to Table 7C, 7D, 7F or 7G for the transport block that could be received with the specified block error probability if it was transmitted with the preferred precoding vector. + +When D-CPICH(s) are not activated for data demodulation by Node B, for the purpose of CQI reporting, the UE shall assume a total transmit power of HS-PDSCH + +$$P_{\text{HSPDSCH}} = P_{\text{CPICH}} + \Gamma \text{ in dB,}$$ + +where the total transmit power is assumed to be evenly distributed among the HS-PDSCH codes corresponding to the reported CQI value, and the measurement power offset $\Gamma$ is signaled by higher layers. $P_{\text{CPICH}}$ denotes the combined transmit power of the set of primary and three secondary CPICHs used for MIMO operation of HS-DSCH. + +When D-CPICH(s) are activated for data demodulation by Node B, for the purpose of CQI reporting, the UE shall assume a total transmit power of HS-PDSCH + +$$P_{\text{HSPDSCH}} = P_{\text{CPICH}} + \Gamma_1 \text{ in dB,}$$ + +where the total transmit power is assumed to be evenly distributed among the HS-PDSCH codes corresponding to the reported CQI value, and the measurement power offset $\Gamma_1$ are signaled by higher layers. $P_{\text{CPICH}}$ denotes the combined transmit power of the set of primary and three secondary CPICHs used for MIMO operation of HS-DSCH. + +If a CQI for a single transport block is reported, the parameter $\Delta$ that is given by Table 7C, 7D, 7F or 7G depending on the UE category and configuration indicates a reference power adjustment for the Node B transmit power on the indicated HS-PDSCH(s). If a CQI for two or three or four transport blocks are reported, the parameter $\Delta$ that is given by Table 7H, 7I, 7Ia or 7Ib depending on the UE category and configuration indicates by how much the equivalent AWGN + +symbol SINR for a specific transport block would be different from the one required to meet the predicted BLER performance. + +When deriving the CQI value, the UE assumes that the Node B would be using a uniform power allocation across the number of HS-PDSCH codes corresponding to the CQI value to be reported. In case the UE reports a CQI for more than one transport block, it is assumed by the UE that the Node B uses an equal power per HS-PDSCH code for all the transport blocks. + +When the Node B schedules the UE with more than one transport block, if the Node B does not transmit each transport block with equal power per used HS-PDSCH code or use different power per code than indicated by the measurement power offset $\Gamma$ , it should not assume that the reported transport block sizes can be received with the specified block error probabilities or that transmission of more than one transport block is preferred by the UE. + +Further, for the purpose of CQI reporting, the UE shall assume the number of soft channel bits available in the virtual IR buffer ( $N_{IR}$ ), and redundancy and constellation version parameter ( $X_{rv}$ , $X_{rvpb}$ , or $X_{rvsb}$ ) as given by Table 7A, 7B, 7C, 7D, 7F, 7G, 7H, 7I, 7Ia or 7Ib depending on the UE category and on the CQI report type irrespective of the actual number of HARQ processes that are configured. + +For the purpose of CQI reporting the UE shall assume that all HS-PDSCH channelisation codes it may receive are under the same scrambling code as the set of CPICH(s) used to determine $P_{CPICH}$ . + +### 6A.2.3 CQI tables + +The CQI mapping table for each UE category and configured mode of operation is described in Table 7a. + +Table 7a: Applicability of CQI mapping tables. + +| Category | Used CQI mapping table | | | | | | | | +|-----------|------------------------|------------------|----------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------|-----------------------------------------------|------------------| +| | MIMO not configured | | MIMO configured and single-stream restriction not configured | | | | MIMO and single-stream restriction configured | | +| | 64QAM not configured | 64QAM configured | 64QAM not configured | | 64QAM configured | | 64QAM not configured | 64QAM configured | +| | | | In case of type B or single transport block type A CQI reports | In case of dual transport block type A CQI reports | In case of type B or single transport block type A CQI reports | In case of dual transport block type A CQI reports | | | +| 1-6 | A | | N/A | | | | A | N/A | +| 7 and 8 | B | | N/A | | | | B | N/A | +| 9 | C | | N/A | | | | C | N/A | +| 10 | D | | N/A | | | | D | N/A | +| 11 and 12 | E | | N/A | | | | | | +| 13 | C | F | N/A | | | | C | F | +| 14 | D | G | N/A | | | | D | G | +| 15 | C | N/A | C | H | N/A | | | | +| 16 | D | N/A | D | I | N/A | | | | +| 17 | C | F | C | H | N/A | | N/A | F | +| 18 | D | G | D | I | N/A | | N/A | G | +| 19 | C | F | C | H | F | J | N/A | | +| 20 | D | G | D | I | G | K | N/A | | +| 21 | C | | N/A | | | | C | N/A | +| 22 | D | | N/A | | | | D | N/A | +| 23 | C | F | N/A | | | | C | F | +| 24 | D | G | N/A | | | | D | G | +| 25 | C | N/A | C | H | N/A | | N/A | | +| 26 | D | N/A | D | I | N/A | | N/A | | +| 27 | C | F | C | H | F | J | N/A | | +| 28 | D | G | D | I | G | K | N/A | | +| 29 and 31 | D | G | N/A | | | | D | G | +| 30 and 32 | D | G | D | I | G | K | N/A | | +| 33 and 35 | D | G | N/A | | | | D | G | +| 34 and 36 | D | G | D | I | G | K | N/A | | +| 37 and 38 | D | G | D | I | G | K | N/A | | + +Table 7A: CQI mapping table A. + +| CQI value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | $N_{IR}$ | $X_{rv}$ | +|-----------|----------------------|--------------------|------------|-------------------------------------|----------|----------| +| 0 | N/A | Out of range | | | | | +| 1 | 137 | 1 | QPSK | 0 | 9600 | 0 | +| 2 | 173 | 1 | QPSK | 0 | | | +| 3 | 233 | 1 | QPSK | 0 | | | +| 4 | 317 | 1 | QPSK | 0 | | | +| 5 | 377 | 1 | QPSK | 0 | | | +| 6 | 461 | 1 | QPSK | 0 | | | +| 7 | 650 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 931 | 2 | QPSK | 0 | | | +| 10 | 1262 | 3 | QPSK | 0 | | | +| 11 | 1483 | 3 | QPSK | 0 | | | +| 12 | 1742 | 3 | QPSK | 0 | | | +| 13 | 2279 | 4 | QPSK | 0 | | | +| 14 | 2583 | 4 | QPSK | 0 | | | +| 15 | 3319 | 5 | QPSK | 0 | | | +| 16 | 3565 | 5 | 16-QAM | 0 | | | +| 17 | 4189 | 5 | 16-QAM | 0 | | | +| 18 | 4664 | 5 | 16-QAM | 0 | | | +| 19 | 5287 | 5 | 16-QAM | 0 | | | +| 20 | 5887 | 5 | 16-QAM | 0 | | | +| 21 | 6554 | 5 | 16-QAM | 0 | | | +| 22 | 7168 | 5 | 16-QAM | 0 | | | +| 23 | 7168 | 5 | 16-QAM | -1 | | | +| 24 | 7168 | 5 | 16-QAM | -2 | | | +| 25 | 7168 | 5 | 16-QAM | -3 | | | +| 26 | 7168 | 5 | 16-QAM | -4 | | | +| 27 | 7168 | 5 | 16-QAM | -5 | | | +| 28 | 7168 | 5 | 16-QAM | -6 | | | +| 29 | 7168 | 5 | 16-QAM | -7 | | | +| 30 | 7168 | 5 | 16-QAM | -8 | | | + +Table 7B: CQI mapping table B. + +| CQI value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | $N_{IR}$ | $X_{rv}$ | +|-----------|----------------------|--------------------|------------|-------------------------------------|----------|----------| +| 0 | N/A | Out of range | | | | | +| 1 | 137 | 1 | QPSK | 0 | 19200 | 0 | +| 2 | 173 | 1 | QPSK | 0 | | | +| 3 | 233 | 1 | QPSK | 0 | | | +| 4 | 317 | 1 | QPSK | 0 | | | +| 5 | 377 | 1 | QPSK | 0 | | | +| 6 | 461 | 1 | QPSK | 0 | | | +| 7 | 650 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 931 | 2 | QPSK | 0 | | | +| 10 | 1262 | 3 | QPSK | 0 | | | +| 11 | 1483 | 3 | QPSK | 0 | | | +| 12 | 1742 | 3 | QPSK | 0 | | | +| 13 | 2279 | 4 | QPSK | 0 | | | +| 14 | 2583 | 4 | QPSK | 0 | | | +| 15 | 3319 | 5 | QPSK | 0 | | | +| 16 | 3565 | 5 | 16-QAM | 0 | | | +| 17 | 4189 | 5 | 16-QAM | 0 | | | +| 18 | 4664 | 5 | 16-QAM | 0 | | | +| 19 | 5287 | 5 | 16-QAM | 0 | | | +| 20 | 5887 | 5 | 16-QAM | 0 | | | +| 21 | 6554 | 5 | 16-QAM | 0 | | | +| 22 | 7168 | 5 | 16-QAM | 0 | | | +| 23 | 9719 | 7 | 16-QAM | 0 | | | +| 24 | 11418 | 8 | 16-QAM | 0 | | | +| 25 | 14411 | 10 | 16-QAM | 0 | | | +| 26 | 14411 | 10 | 16-QAM | -1 | | | +| 27 | 14411 | 10 | 16-QAM | -2 | | | +| 28 | 14411 | 10 | 16-QAM | -3 | | | +| 29 | 14411 | 10 | 16-QAM | -4 | | | +| 30 | 14411 | 10 | 16-QAM | -5 | | | + +Table 7C: CQI mapping table C. + +| CQI or CQI s value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | N IR | X rv or X rvpb | +|-------------------------------|----------------------|--------------------|------------|-------------------------------------|-----------------|--------------------------------------| +| 0 | N/A | Out of range | | | | | +| 1 | 137 | 1 | QPSK | 0 | 28800 | 0 | +| 2 | 173 | 1 | QPSK | 0 | | | +| 3 | 233 | 1 | QPSK | 0 | | | +| 4 | 317 | 1 | QPSK | 0 | | | +| 5 | 377 | 1 | QPSK | 0 | | | +| 6 | 461 | 1 | QPSK | 0 | | | +| 7 | 650 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 931 | 2 | QPSK | 0 | | | +| 10 | 1262 | 3 | QPSK | 0 | | | +| 11 | 1483 | 3 | QPSK | 0 | | | +| 12 | 1742 | 3 | QPSK | 0 | | | +| 13 | 2279 | 4 | QPSK | 0 | | | +| 14 | 2583 | 4 | QPSK | 0 | | | +| 15 | 3319 | 5 | QPSK | 0 | | | +| 16 | 3565 | 5 | 16-QAM | 0 | | | +| 17 | 4189 | 5 | 16-QAM | 0 | | | +| 18 | 4664 | 5 | 16-QAM | 0 | | | +| 19 | 5287 | 5 | 16-QAM | 0 | | | +| 20 | 5887 | 5 | 16-QAM | 0 | | | +| 21 | 6554 | 5 | 16-QAM | 0 | | | +| 22 | 7168 | 5 | 16-QAM | 0 | | | +| 23 | 9719 | 7 | 16-QAM | 0 | | | +| 24 | 11418 | 8 | 16-QAM | 0 | | | +| 25 | 14411 | 10 | 16-QAM | 0 | | | +| 26 | 17237 | 12 | 16-QAM | 0 | | | +| 27 | 17237 | 12 | 16-QAM | -1 | | | +| 28 | 17237 | 12 | 16-QAM | -2 | | | +| 29 | 17237 | 12 | 16-QAM | -3 | | | +| 30 | 17237 | 12 | 16-QAM | -4 | | | + +**Table 7D: CQI mapping table D.** + +| CQI or CQI s value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | N IR | X rv or X rvpb | +|-------------------------------|----------------------|--------------------|------------|-------------------------------------|-----------------|--------------------------------------| +| 0 | N/A | Out of range | | | | | +| 1 | 137 | 1 | QPSK | 0 | 28800 | 0 | +| 2 | 173 | 1 | QPSK | 0 | | | +| 3 | 233 | 1 | QPSK | 0 | | | +| 4 | 317 | 1 | QPSK | 0 | | | +| 5 | 377 | 1 | QPSK | 0 | | | +| 6 | 461 | 1 | QPSK | 0 | | | +| 7 | 650 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 931 | 2 | QPSK | 0 | | | +| 10 | 1262 | 3 | QPSK | 0 | | | +| 11 | 1483 | 3 | QPSK | 0 | | | +| 12 | 1742 | 3 | QPSK | 0 | | | +| 13 | 2279 | 4 | QPSK | 0 | | | +| 14 | 2583 | 4 | QPSK | 0 | | | +| 15 | 3319 | 5 | QPSK | 0 | | | +| 16 | 3565 | 5 | 16-QAM | 0 | | | +| 17 | 4189 | 5 | 16-QAM | 0 | | | +| 18 | 4664 | 5 | 16-QAM | 0 | | | +| 19 | 5287 | 5 | 16-QAM | 0 | | | +| 20 | 5887 | 5 | 16-QAM | 0 | | | +| 21 | 6554 | 5 | 16-QAM | 0 | | | +| 22 | 7168 | 5 | 16-QAM | 0 | | | +| 23 | 9719 | 7 | 16-QAM | 0 | | | +| 24 | 11418 | 8 | 16-QAM | 0 | | | +| 25 | 14411 | 10 | 16-QAM | 0 | | | +| 26 | 17237 | 12 | 16-QAM | 0 | | | +| 27 | 21754 | 15 | 16-QAM | 0 | | | +| 28 | 23370 | 15 | 16-QAM | 0 | | | +| 29 | 24222 | 15 | 16-QAM | 0 | | | +| 30 | 25558 | 15 | 16-QAM | 0 | | | + +Table 7E: CQI mapping table E. + +| CQI value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | $N_{IR}$ | $X_{rv}$ | +|-----------|----------------------|--------------------|------------|-------------------------------------|----------|----------| +| 0 | N/A | Out of range | | | | | +| 1 | 137 | 1 | QPSK | 0 | 4800 | 0 | +| 2 | 173 | 1 | QPSK | 0 | | | +| 3 | 233 | 1 | QPSK | 0 | | | +| 4 | 317 | 1 | QPSK | 0 | | | +| 5 | 377 | 1 | QPSK | 0 | | | +| 6 | 461 | 1 | QPSK | 0 | | | +| 7 | 650 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 931 | 2 | QPSK | 0 | | | +| 10 | 1262 | 3 | QPSK | 0 | | | +| 11 | 1483 | 3 | QPSK | 0 | | | +| 12 | 1742 | 3 | QPSK | 0 | | | +| 13 | 2279 | 4 | QPSK | 0 | | | +| 14 | 2583 | 4 | QPSK | 0 | | | +| 15 | 3319 | 5 | QPSK | 0 | | | +| 16 | 3319 | 5 | QPSK | -1 | | | +| 17 | 3319 | 5 | QPSK | -2 | | | +| 18 | 3319 | 5 | QPSK | -3 | | | +| 19 | 3319 | 5 | QPSK | -4 | | | +| 20 | 3319 | 5 | QPSK | -5 | | | +| 21 | 3319 | 5 | QPSK | -6 | | | +| 22 | 3319 | 5 | QPSK | -7 | | | +| 23 | 3319 | 5 | QPSK | -8 | | | +| 24 | 3319 | 5 | QPSK | -9 | | | +| 25 | 3319 | 5 | QPSK | -10 | | | +| 26 | 3319 | 5 | QPSK | -11 | | | +| 27 | 3319 | 5 | QPSK | -12 | | | +| 28 | 3319 | 5 | QPSK | -13 | | | +| 29 | 3319 | 5 | QPSK | -14 | | | +| 30 | 3319 | 5 | QPSK | -15 | | | + +Table 7F: CQI mapping table F. + +| CQI value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | N IR | X RV | +|-----------|----------------------|--------------------|------------|-------------------------------------|-----------------|-----------------| +| 0 | N/A | Out of range | | | | | +| 1 | 136 | 1 | QPSK | 0 | 43200 | 0 | +| 2 | 176 | 1 | QPSK | 0 | | | +| 3 | 232 | 1 | QPSK | 0 | | | +| 4 | 320 | 1 | QPSK | 0 | | | +| 5 | 376 | 1 | QPSK | 0 | | | +| 6 | 464 | 1 | QPSK | 0 | | | +| 7 | 648 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 928 | 2 | QPSK | 0 | | | +| 10 | 1264 | 3 | QPSK | 0 | | | +| 11 | 1488 | 3 | QPSK | 0 | | | +| 12 | 1744 | 3 | QPSK | 0 | | | +| 13 | 2288 | 4 | QPSK | 0 | | | +| 14 | 2592 | 4 | QPSK | 0 | | | +| 15 | 3328 | 5 | QPSK | 0 | | | +| 16 | 3576 | 5 | 16-QAM | 0 | | | +| 17 | 4200 | 5 | 16-QAM | 0 | | | +| 18 | 4672 | 5 | 16-QAM | 0 | | | +| 19 | 5296 | 5 | 16-QAM | 0 | | | +| 20 | 5896 | 5 | 16-QAM | 0 | | | +| 21 | 6568 | 5 | 16-QAM | 0 | | | +| 22 | 7184 | 5 | 16-QAM | 0 | | | +| 23 | 9736 | 7 | 16-QAM | 0 | | | +| 24 | 11432 | 8 | 16-QAM | 0 | | | +| 25 | 14424 | 10 | 16-QAM | 0 | | | +| 26 | 15776 | 10 | 64-QAM | 0 | | | +| 27 | 21768 | 12 | 64-QAM | 0 | | | +| 28 | 26504 | 13 | 64-QAM | 0 | | | +| 29 | 32264 | 14 | 64-QAM | 0 | | | +| 30 | 32264 | 14 | 64-QAM | -2 | | | + +Table 7G: CQI mapping table G. + +| CQI value | Transport Block Size | Number of HS-PDSCH | Modulation | Reference power adjustment $\Delta$ | N IR | X RV | +|-----------|----------------------|--------------------|------------|-------------------------------------|-----------------|-----------------| +| 0 | N/A | Out of range | | | | | +| 1 | 136 | 1 | QPSK | 0 | 43200 | 0 | +| 2 | 176 | 1 | QPSK | 0 | | | +| 3 | 232 | 1 | QPSK | 0 | | | +| 4 | 320 | 1 | QPSK | 0 | | | +| 5 | 376 | 1 | QPSK | 0 | | | +| 6 | 464 | 1 | QPSK | 0 | | | +| 7 | 648 | 2 | QPSK | 0 | | | +| 8 | 792 | 2 | QPSK | 0 | | | +| 9 | 928 | 2 | QPSK | 0 | | | +| 10 | 1264 | 3 | QPSK | 0 | | | +| 11 | 1488 | 3 | QPSK | 0 | | | +| 12 | 1744 | 3 | QPSK | 0 | | | +| 13 | 2288 | 4 | QPSK | 0 | | | +| 14 | 2592 | 4 | QPSK | 0 | | | +| 15 | 3328 | 5 | QPSK | 0 | | | +| 16 | 3576 | 5 | 16-QAM | 0 | | | +| 17 | 4200 | 5 | 16-QAM | 0 | | | +| 18 | 4672 | 5 | 16-QAM | 0 | | | +| 19 | 5296 | 5 | 16-QAM | 0 | | | +| 20 | 5896 | 5 | 16-QAM | 0 | | | +| 21 | 6568 | 5 | 16-QAM | 0 | | | +| 22 | 7184 | 5 | 16-QAM | 0 | | | +| 23 | 9736 | 7 | 16-QAM | 0 | | | +| 24 | 11432 | 8 | 16-QAM | 0 | | | +| 25 | 14424 | 10 | 16-QAM | 0 | | | +| 26 | 15776 | 10 | 64-QAM | 0 | | | +| 27 | 21768 | 12 | 64-QAM | 0 | | | +| 28 | 26504 | 13 | 64-QAM | 0 | | | +| 29 | 32264 | 14 | 64-QAM | 0 | | | +| 30 | 38576 | 15 | 64-QAM | 0 | | | + +Table 7H: CQI mapping table H. + +| CQI 1 or CQI 2 | Transport Block Size | Number of HS-PDSCH | Modulation | Equivalent AWGN SINR difference $\Delta$ | N IR | X rvpb or X rvsb | +|--------------------------------------|----------------------|--------------------|------------|------------------------------------------|-----------------|----------------------------------------| +| 0 | 4581 | 15 | QPSK | -3.00 | 28800 | 0 | +| 1 | 4581 | 15 | QPSK | -1.00 | | | +| 2 | 5101 | 15 | QPSK | 0 | | | +| 3 | 6673 | 15 | QPSK | 0 | | | +| 4 | 8574 | 15 | QPSK | 0 | | | +| 5 | 10255 | 15 | QPSK | 0 | | | +| 6 | 11835 | 15 | QPSK | 0 | | | +| 7 | 14936 | 15 | 16QAM | 0 | | | +| 8 | 17548 | 15 | 16QAM | 0 | | | +| 9 | 20617 | 15 | 16QAM | 0 | | | +| 10 | 23370 | 15 | 16QAM | 0 | | | +| 11 | 23370 | 15 | 16QAM | 1.50 | | | +| 12 | 23370 | 15 | 16QAM | 2.50 | | | +| 13 | 23370 | 15 | 16QAM | 4.00 | | | +| 14 | 23370 | 15 | 16QAM | 5.00 | | | + +Table 7I: CQI mapping table I. + +| CQI 1 or CQI 2 | Transport Block Size | Number of HS-PDSCH | Modulation | Equivalent AWGN SINR difference $\Delta$ | N IR | X rvpb or X rvsb | +|--------------------------------------|----------------------|--------------------|------------|------------------------------------------|-----------------|----------------------------------------| +| 0 | 4581 | 15 | QPSK | -3.00 | 28800 | 0 | +| 1 | 4581 | 15 | QPSK | -1.00 | | | +| 2 | 5101 | 15 | QPSK | 0 | | | +| 3 | 6673 | 15 | QPSK | 0 | | | +| 4 | 8574 | 15 | QPSK | 0 | | | +| 5 | 10255 | 15 | QPSK | 0 | | | +| 6 | 11835 | 15 | QPSK | 0 | | | +| 7 | 14936 | 15 | 16QAM | 0 | | | +| 8 | 17548 | 15 | 16QAM | 0 | | | +| 9 | 20617 | 15 | 16QAM | 0 | | | +| 10 | 23370 | 15 | 16QAM | 0 | | | +| 11 | 25558 | 15 | 16QAM | 0 | | | +| 12 | 26969 | 15 | 16QAM | 0 | | | +| 13 | 27456 | 15 | 16QAM | 0 | | | +| 14 | 27952 | 15 | 16QAM | 0 | | | + +Table 71a: CQI mapping table J. + +| CQI 1 or CQI 2 | Transport Block Size | Number of HS-PDSCH | Modulation | Equivalent AWGN SINR difference $\Delta$ | N IR | X rvpb or X rvsb | +|--------------------------------------|----------------------|--------------------|------------|------------------------------------------|-----------------|----------------------------------------| +| 0 | 4592 | 15 | QPSK | -3.00 | 43200 | 0 | +| 1 | 4592 | 15 | QPSK | -1.00 | | | +| 2 | 5296 | 15 | QPSK | 0 | | | +| 3 | 7312 | 15 | QPSK | 0 | | | +| 4 | 9392 | 15 | QPSK | 0 | | | +| 5 | 11032 | 15 | QPSK | 0 | | | +| 6 | 14952 | 15 | 16QAM | 0 | | | +| 7 | 17880 | 15 | 16QAM | 0 | | | +| 8 | 21384 | 15 | 16QAM | 0 | | | +| 9 | 24232 | 15 | 16QAM | 0 | | | +| 10 | 27960 | 15 | 64QAM | 0 | | | +| 11 | 32264 | 15 | 64QAM | 0 | | | +| 12 | 32264 | 15 | 64QAM | 2 | | | +| 13 | 32264 | 15 | 64QAM | 4 | | | +| 14 | 32264 | 15 | 64QAM | 6 | | | + +Table 71b: CQI mapping table K. + +| CQI 1 or CQI 2 | Transport Block Size | Number of HS-PDSCH | Modulation | Equivalent AWGN SINR difference $\Delta$ | N IR | X rvpb or X rvsb | +|--------------------------------------|----------------------|--------------------|------------|------------------------------------------|-----------------|----------------------------------------| +| 0 | 4592 | 15 | QPSK | -3.00 | 43200 | 0 | +| 1 | 4592 | 15 | QPSK | -1.00 | | | +| 2 | 5296 | 15 | QPSK | 0 | | | +| 3 | 7312 | 15 | QPSK | 0 | | | +| 4 | 9392 | 15 | QPSK | 0 | | | +| 5 | 11032 | 15 | QPSK | 0 | | | +| 6 | 14952 | 15 | 16QAM | 0 | | | +| 7 | 17880 | 15 | 16QAM | 0 | | | +| 8 | 21384 | 15 | 16QAM | 0 | | | +| 9 | 24232 | 15 | 16QAM | 0 | | | +| 10 | 27960 | 15 | 64QAM | 0 | | | +| 11 | 32264 | 15 | 64QAM | 0 | | | +| 12 | 36568 | 15 | 64QAM | 0 | | | +| 13 | 39984 | 15 | 64QAM | 0 | | | +| 14 | 42192 | 15 | 64QAM | 0 | | | + +## 6A.3 Operation during compressed mode on the associated DPCH or F-DPCH + +During compressed mode on the associated DPCH or F-DPCH, and the Secondary Cell Active is 0, or the Secondary Cell Active is not 0 and the compressed mode is applied to the serving HS-DSCH cell and all the secondary serving HS-DSCH cells, the following applies for the UE for transmission of HS-DPCCH and reception of HS-SCCH and HS-PDSCH: + +- The UE shall neglect a HS-SCCH or HS-PDSCH transmission, if a part of the HS-SCCH or a part of the corresponding HS-PDSCH overlaps with a downlink transmission gap on the associated DPCH or F-DPCH. In this case, neither ACK, nor NACK shall be transmitted by the UE to respond to the corresponding downlink transmission. +- If a part of a HS-DPCCH slot allocated to HARQ-ACK overlaps with an uplink transmission gap on the associated DPCH, the UE shall use DTX on the HS-DPCCH in that HS-DPCCH slot. +- If in a HS-DPCCH sub-frame a part of a slot allocated for CQI information overlaps with an uplink transmission gap on the associated DPCH, the UE shall not transmit that CQI or composite PCI/CQI information in that sub-frame (if HS-DPCCH slot format 0 is used) or in that slot (if HS-DPCCH slot format 1 is used). +- If a CQI report or a composite PCI/CQI report is scheduled in the current CQI field according to subclause 6A.1.2.1 paragraph (2) or subclause 6A.1.2.2 paragraph (2), and the corresponding 3-slot reference period (as defined in subclause 6A.2.1 or subclause 6A.2.2) wholly or partly overlaps a downlink transmission gap, then the UE shall use DTX in the current CQI field and in the CQI fields in the next $(N\_cqi\_transmit-1)$ subframes. + +During compressed mode, when Secondary Cell Active is not 0 and the compressed mode is not applied to all the active cells, the following applies for the UE for transmission of HS-DPCCH and reception of HS-SCCH and HS-PDSCH on the cell(s) in which the compressed mode is applied: + +- The UE shall neglect a HS-SCCH or HS-PDSCH transmission on a cell, if a part of the HS-SCCH or a part of the corresponding HS-PDSCH overlaps with a downlink transmission gap on that cell. In this case, neither ACK, nor NACK shall be transmitted by the UE to respond to the corresponding downlink transmission. +- If a CQI report or a composite PCI/CQI report for a cell is scheduled in the current CQI field according to subclause 6A.1.2.1 paragraph (2) or subclause 6A.1.2.2 paragraph (2), and the corresponding 3-slot reference period (as defined in subclause 6A.2.1 or subclause 6A.2.2) wholly or partly overlaps a downlink transmission gap on that cell, then the UE shall use DTX in the current CQI field and in the CQI fields in the next $(N\_cqi\_transmit-1)$ subframes if using DTX in the CQI field is possible. In the case that using DTX in the CQI field is not possible due to the need to transmit a CQI or a composite PCI/CQI report of another cell not experiencing a compressed mode gap, the UE shall transmit a CQI or a composite PCI/CQI report based on measurements prior to the start of the compressed mode gap for the cell experiencing the compressed mode gap. + +During compressed mode, when the UE is configured in Multiflow mode, + +- For the assisting serving HS-DSCH cell: The UE shall follow the same compressed mode rules that are defined for the serving HS-DSCH cell. +- For the assisting secondary serving cell, if present: The UE shall follow the same compressed mode rules that are defined for the secondary serving HS-DSCH cell. + +## 6A.4 Precoding control indication (PCI) definition + +### 6A.4.1 PCI definition when the UE is configured in MIMO mode + +The UE uses the CPICH(s) transmitted from antenna 1 and antenna 2 to calculate the preferred precoding vectors to be applied at Node B to maximise the aggregate transport block size that could be supported under current channel conditions. No matter whether one or two transport blocks are preferred, it is sufficient to signal from the UE to the Node B only the preferred primary precoding vector $(w_1^{pref}, w_2^{pref})$ , since the optional secondary precoding vector will be a unique function of the primary one. When single-stream restriction is not configured the information on whether one or two transport blocks are preferred is part of the CQI reporting as defined in subclause 6A.2.2. Since the first precoding weight $w_1^{pref}$ of the preferred primary precoding vector $(w_1^{pref}, w_2^{pref})$ is constant, it is sufficient to determine + +the precoding weight for antenna 2. In each TTI during which the UE derives a composite PCI/CQI report, the UE shall calculate the optimum precoding weight $w_2^{\text{pref}}$ for antenna 2. + +If the UE is not configured with precoding weight set restriction by the higher layers, the optimum precoding weight $w_2^{\text{pref}}$ for antenna 2 is taken from the set: + +$$w_2^{\text{pref}} \in \left\{ \frac{1+j}{2}, \frac{1-j}{2}, \frac{-1+j}{2}, \frac{-1-j}{2} \right\}.$$ + +If the UE is configured with precoding weight set restriction by the higher layers, the optimum precoding vector weight $w_2^{\text{pref}}$ for antenna 2 is taken from the set as defined in table 7J0. + +**Table 7J0 : Selection of the precoding weight set when the precoding weight set restriction is configured by higher layers** + +| Number of Transport Blocks preferred in the composite PCI/CQI report | Precoding weight set from which the optimum precoding weight $w_2^{\text{pref}}$ for antenna 2 is taken. | +|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| 1 (always the case when single-stream restriction is configured to the UE) | $w_2^{\text{pref}} \in \left\{ \frac{1+j}{2}, \frac{-1-j}{2} \right\}$ | +| 2 | $w_2^{\text{pref}} \in \left\{ \frac{1+j}{2}, \frac{1-j}{2}, \frac{-1+j}{2}, \frac{-1-j}{2} \right\}$ | + +The precoding weight $w_2^{\text{pref}}$ is mapped to PCI values as defined in table 7J. + +**Table 7J : Mapping of preferred precoding weight $w_2^{\text{pref}}$ to PCI values.** + +| $w_2^{\text{pref}}$ | PCI value | +|---------------------|-----------| +| $\frac{1+j}{2}$ | 0 | +| $\frac{1-j}{2}$ | 1 | +| $\frac{-1+j}{2}$ | 2 | +| $\frac{-1-j}{2}$ | 3 | + +### 6A.4.2 PCI definition when the UE is configured in MIMO mode with four transmit antennas + +This section applies only when the UE is configured in MIMO mode with four transmit antennas. + +The UE uses the CPICHs transmitted from antenna 1, antenna 2, antennas 3 and antenna 4 to calculate the preferred precoding matrix to be applied at Node B to maximise the aggregate transport block sizes that could be supported under current channel conditions. + +The preferred precoding information PCI ( $pci_0, pci_1, pci_2, pci_3$ ) is defined as the precoding weight information in subclause 4.6D.2.7 of [2] with the following PCI mapping to table 14B.7: + +$$pci_0, pci_1, pci_2, pci_3 = x_{\text{pwibp},1}, x_{\text{pwibp},2}, x_{\text{pwibp},3}, x_{\text{pwibp},4}.$$ + +The number of transport blocks corresponding corresponding to table 14B.7 used in the PCI derivation corresponds to the number of transport blocks preferred (NTBP) reported in the composite NTBP/PCI/CQI report carrying the corresponding NTBP. + +# 6B E-DCH related procedures + +The following physical layer parameters are signalled to the UE from higher layers: + +- 1) E-HICH set to be monitored for each uplink frequency for which E-DCH is configured +- 2) E-RGCH set to be monitored for each uplink frequency for which E-DCH is configured + +If the UE is configured with multiple uplink frequencies, then the Secondary\_EDCH\_Cell\_Enabled is 1, otherwise Secondary\_EDCH\_Cell\_Enabled is 0 and Secondary\_EDCH\_Cell\_Active is 0. + +The Secondary\_EDCH\_Cell\_Active shall be set according to the following rules: + +- Secondary\_EDCH\_Cell\_Active is set to 0 when Secondary\_EDCH\_Cell\_Enabled is 0 or Secondary\_Cell\_Active is 0 (as described in subclause 6A.1). +- Secondary\_EDCH\_Cell\_Active shall remain set to 0, when Secondary\_EDCH\_Cell\_Enabled is changed from 0 to 1. +- Secondary\_EDCH\_Cell\_Active shall be set to 0 or 1, upon the reception of HS-SCCH orders to deactivate or activate the secondary uplink carrier respectively as specified in [2] when Secondary\_EDCH\_Cell\_Enabled is 1 and Secondary\_Cell\_Active is not 0 (as described in subclause 6A.1) and the 1st secondary serving HS-DSCH cell is activated. +- Secondary\_EDCH\_Cell\_Active shall be set to 0 or 1, upon the reception of HS-SCCH orders to deactivate or activate both the secondary uplink carrier and the 1st secondary serving HS-DSCH cell as specified in [2] when Secondary\_EDCH\_Cell\_Enabled is 1 (as described in subclause 6A.1). +- Secondary\_EDCH\_Cell\_Active can be set to 0 by higher layers (as described in [5]). + +Secondary\_EDCH\_Cell\_Active shall be set to 1 while Secondary\_EDCH\_Cell\_Enabled is 1, Secondary\_Cell\_Active is not 0, 1st secondary serving HS-DSCH cell is activated, and the secondary uplink frequency is activated, otherwise Secondary\_EDCH\_Cell\_Active shall be set to 0. If the Secondary\_EDCH\_Cell\_Active is already equal to 1 when the UE receives an HS-SCCH order for activation of the secondary uplink frequency as specified in [2], then the UE shall not change the status of Secondary\_EDCH\_Cell\_Active regarding the contents of the order, but shall transmit the HARQ-ACK acknowledging the HS-SCCH order. + +HS-SCCH ordered deactivation or activation of the secondary uplink frequency is applied by the UE at the same point in time as in the case of HS-SCCH ordered deactivation and activation of the secondary serving HS-DSCH cell for a UE configured with multiple uplink frequencies (see subclause 6A.1). + +If higher layers set READY\_FOR\_COMMON\_ERGCH to TRUE (as described in [5]) then Common\_RGCH\_Enabled is TRUE. Otherwise, Common\_RGCH\_Enabled is FALSE. + +If higher layers configure concurrent deployment of 2ms and 10ms TTI in a cell (as described in [5]) then Concurrent\_TTI\_Deployment\_Enabled is TRUE. Otherwise, Concurrent\_TTI\_Deployment\_Enabled is FALSE. + +If higher layers set READY\_FOR\_FALLBACK\_R99\_PRACH to TRUE (as described in [5]) then Fallback\_R99\_Enabled is TRUE. Otherwise, Fallback\_R99\_Enabled is FALSE. + +If NT-HS-DPCCH\_Enabled is TRUE, the UE shall inform higher layers about the reception of an HS-SCCH order and the order type. + +## 6B.1 ACK/NACK detection + +For each activated uplink frequency, the physical layer in the UE shall detect ACK or NACK within the E-HICH set that is monitored by the UE in the subframes where ACK/NACK is transmitted by the UTRAN and deliver the ACK/NACK to the higher layers as follows: + +- When a UE is not in soft handover, an ACK shall be delivered to the higher layers if a reliable ACK is detected by the physical layer in the UE, else a NACK shall be delivered to the higher layers. +- When a UE is in soft handover, multiple ACK/NACKs may be received in an E-DCH TTI from different cells in the active set. In some cases, the UE has the knowledge that some of the transmitted ACK/NACKs are the same. This is the case when the radio links are in the same radio link set. For these cases, ACK/NACKs from the same radio link set shall be soft combined into one ACK/NACK information and delivered to higher layers. If a radio link set contains only one radio link, the detection shall be done as specified above for the case where the UE is not in soft handover. For each radio link set containing multiple radio links, an ACK shall be delivered to the + +higher layers if a reliable ACK is detected by the physical layer in the UE after soft combining, else a NACK shall be delivered to the higher layers. + +## 6B.2 Relative grants detection + +In CELL\_DCH state, for each activated uplink frequency, the physical layer in the UE shall detect relative grants within the E-RGCH set that is monitored by the UE and deliver the relative grants to the higher layers as follows: + +- When a UE is not in soft handover, an UP shall be delivered to the higher layers if a reliable UP is detected by the physical layer in the UE, else a DOWN shall be delivered to the higher layers if a reliable DOWN is detected by the UE, else a HOLD shall be delivered to the higher layers. +- When a UE is in soft handover, multiple relative grants may be received in an E-DCH TTI from different cells in the E-DCH active set. The UE shall handle the E-RGCH received from these cells as follows: + - If the E-DCH serving radio link set contains only one radio link, the detection shall be done as specified above for the case where the UE is not in soft handover. If the E-DCH serving radio link set contains more than one radio link, the relative grants from the E-DCH serving radio link set are the same and shall be soft combined into one single relative grant information; an UP shall be delivered to the higher layers if a reliable UP is detected by the physical layer in the UE after soft combining, else a DOWN shall be delivered to the higher layers if a reliable DOWN is detected by the UE after soft combining, else a HOLD shall be delivered to the higher layers. +- Furthermore, for each relative grant received from a radio link which does not belong to the E-DCH serving radio link set, a DOWN shall be delivered to the higher layers if a reliable DOWN is detected by the UE, else a HOLD shall be delivered to the higher layers. The UE shall not soft combine relative grants received from radio links which do not belong to the E-DCH serving radio link set. + +In CELL\_FACH state, if Common\_RGCH\_Enabled is TRUE, the physical layer in the UE shall detect relative grants within the E-RGCH set that is monitored by the UE and deliver the relative grants to the higher layers as follows: + +- Multiple relative grants may be received in an E-DCH TTI from different cells that do not belong to the E-DCH serving radio link set. For each relative grant received from a cell, a DOWN shall be delivered to the higher layers if a reliable DOWN is detected by the physical layer in the UE, else a HOLD shall be delivered to the higher layers. The UE shall not soft combine relative grants received from any of the cells. + +### 6B.2A Absolute Grant Detection when the UE is configured with Implicit Grant Handling + +In CELL\_DCH state, when Implicit Grant Handling is configured, the UE shall determine the presence of an E-AGCH transmission. If the presence of the E-AGCH transmission in an E-AGCH sub-frame is detected, then the Serving Grant Update procedure as described in subclause 11.8.1.3.1 of [9] shall be applied. Otherwise, the UE shall assume that it has not received an E-AGCH transmission in that TTI. + +## 6B.3 E-DCH control timing + +In subclauses 6B.3.1 and 6B.3.2 the word "first" refers to the earliest point in time. + +### 6B.3.0 UE procedure for switching the E-DCH TTI length due to an HS-SCCH order + +When Enhanced TTI switching is configured, upon successfully receiving an HS-SCCH order that depending on the UE's configuration indicates single cell E-DCH TTI switching (i.e. from 2ms E-DCH TTI to 10ms E-DCH TTI or vice versa) or dual cell E-DCH TTI switching (see Table 14B.3B in [2]), the UE shall be able to start transmitting E-DCH data using the new E-DCH TTI length according to the activation time configured by higher layers and the time taken for E-DCH TTI reconfiguration. The activation time is measured from the beginning of the first E-DCH radio frame after the end of the HS-SCCH sub-frame containing the order. The UE E-DCH TTI reconfiguration process begins after the activation time and lasts for 20 ms, after which the UE shall be able to start transmitting E-DCH data using the new E-DCH TTI length. + +#### 6B.3.1 10 ms E-DCH TTI + +For each cell in the E-DCH active set, the UE shall associate the control data received in the E-HICH frame associated with SFN $i$ to the data transmitted in the E-DPDCH frame associated with SFN $i-3$ . + +For each cell which belongs to the serving E-DCH radio link set, the UE shall first take into account E-DCH control data received in the E-RGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in the E-DPDCH frame associated with SFN $i+1$ . + +For each cell which does not belong to the serving E-DCH radio link set the UE shall first take into account E-DCH control data received in the E-RGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in the E-DPDCH frame associated with SFN $i+1+s$ where: + +$$s = \left\lceil \frac{160 - (\tau_{\text{DPCH},n}/256)}{150} \right\rceil$$ + +The UE shall first take into account E-DCH control data received in the E-AGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in the E-DPDCH frame associated with SFN $i+1+s$ where: + +$$s = \left\lceil \frac{100 - (\tau_{\text{DPCH},n}/256)}{150} \right\rceil$$ + +When a downlink F-DPCH is configured, $\tau_{\text{DPCH},n} = \tau_{F\text{-DPCH},n}$ . + +#### 6B.3.2 2 ms E-DCH TTI + +For each cell in the E-DCH active set, the UE shall associate the E-DCH control data received in sub-frame $j$ of the E-HICH frame associated with SFN $i$ to sub-frame $t$ of the E-DPDCH frame associated with SFN $i-s$ where: + +$$s = 1 - \lfloor j/3 \rfloor, \text{ and } t = (j + 2) \bmod 5$$ + +For each cell which belongs to the serving E-DCH radio link set, the UE shall first take into account E-DCH control data received in sub-frame $j$ of the E-RGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in sub-frame $j$ of the E-DPDCH frame associated with SFN $i+1$ . + +For each cell which does not belong to the serving E-DCH radio link set the UE shall first take into account E-DCH control data received in the E-RGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in sub-frame $t$ of the E-DPDCH frame associated with SFN $i+1+s$ where: + +$$s = \left\lceil \frac{\left\lceil \frac{160 - (\tau_{\text{DPCH},n}/256)}{30} \right\rceil}{5} \right\rceil, \text{ and } t = \left\lceil \frac{160 - (\tau_{\text{DPCH},n}/256) - 150s}{30} \right\rceil$$ + +The UE shall first take into account E-DCH control data received in sub-frame $j$ of the E-AGCH frame associated with SFN $i$ in the higher layer procedures which correspond to E-DCH transmission in sub-frame $t$ of the E-DPDCH frame associated with SFN $i+s$ where: + +$$s = \left\lceil \frac{\left\lceil \frac{30j + 100 - (\tau_{\text{DPCH},n}/256)}{30} \right\rceil}{5} \right\rceil, \text{ and } t = \left\lceil \frac{30j + 100 - (\tau_{\text{DPCH},n}/256) - 150s}{30} \right\rceil$$ + +The same relationship applies for E-ROCH to S-E-DPDCH timing relationship as is defined above for the E-AGCH to E-DPDCH timing relationship. + +When a downlink F-DPCH is configured, $\tau_{\text{DPCH},n} = \tau_{F\text{-DPCH},n}$ . + +## 6B.4 Operation during compressed mode + +### 6B.4.1 Uplink compressed mode + +When E-DCH TTI length is 2 ms, the UE shall not transmit E-DCH data in a TTI which fully or partly overlaps with an uplink transmission gap. + +Handling of uplink compressed mode when the E-DCH TTI is 10msec is described in [2]. + +### 6B.4.2 Downlink compressed mode + +The following applies for the UE for reception of E-HICH, E-RGCH and E-AGCH, during compressed mode on the DPCH or F-DPCH: + +- A UE shall decode E-HICH, E-RGCH, E-ROCH or E-AGCH transmissions to the UE using all the slots which do not overlap a downlink transmission gap. +- The UE may discard E-HICH, E-RGCH, E-ROCH or E-AGCH slots which overlap a downlink transmission gap. + +# --- 6C Discontinuous transmission and reception procedures + +Whether discontinuous uplink DPCCH transmission operation or discontinuous downlink reception operation are applied is determined by the settings of UL\_DTX\_Active and DL\_DRX\_Active as follows: + +UL\_DTX\_Active shall be set to TRUE while UE\_DTX\_DRX\_Enabled is TRUE and discontinuous uplink DPCCH transmission is activated. Otherwise, UL\_DTX\_Active shall be set to FALSE. + +Discontinuous uplink DPCCH transmission shall be activated at the time when UE\_DTX\_DRX\_Enabled is set to TRUE, and may be further deactivated or activated by layer 1 HS-SCCH orders (see subclause 6C.4). + +DL\_DRX\_Active shall be set to TRUE while UE\_DTX\_DRX\_Enabled is TRUE and UL\_DTX\_Active is TRUE and discontinuous downlink reception is activated. Otherwise, DL\_DRX\_Active shall be set to FALSE. + +Discontinuous downlink reception shall be activated at the time when UE\_DTX\_DRX\_Enabled is set to TRUE, and may be further deactivated or activated by layer 1 HS-SCCH orders (see subclause 6C.4). + +The higher layers define the discontinuous transmission and reception procedures using the following parameters: + +For discontinuous UL DPCCH transmission: + +**CQI\_DTX\_TIMER:** Specifies the number of subframes during which the CQI reports have higher priority than the DTX pattern. This is the initial value of CQI nominal reporting timer. + +**UE\_DTX\_cycle\_1:** Uplink DPCCH burst pattern length in subframes. + +**UE\_DTX\_cycle\_2:** Uplink DPCCH burst pattern length in subframes. + +**Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2:** Defines a number of consecutive E-DCH TTIs without an E-DCH transmission, after which the UE shall immediately move from UE\_DTX\_cycle\_1 to using UE\_DTX\_cycle\_2. + +**UE\_DPCCH\_burst\_1:** Determines the Uplink DPCCH burst length in subframes, when UE\_DTX\_cycle\_1 is applied. + +**UE\_DPCCH\_burst\_2:** Determines the Uplink DPCCH burst length in subframes, when UE\_DTX\_cycle\_2 is applied. + +**UE\_DTX\_long\_preamble\_length:** Determines in slots the length of the preamble associated with the UE\_DTX\_cycle\_2. + +For both discontinuous UL DPCCH transmission and discontinuous downlink reception: + +**UE\_DTX\_DRX\_Offset:** Uplink DPCCH burst pattern and HS-SCCH reception pattern offset in subframes. + +**Enabling\_Delay:** defined in [5], ensures that the uplink DPCCH, the downlink F-DPCH and, if configured, the downlink F-TPICH are transmitted continuously for Enabling\_Delay radio frames after DTX\_DRX\_STATUS is set to TRUE or ensures that, with DTX\_DRX\_STATUS set to TRUE, the uplink DPCCH on the secondary uplink frequency is transmitted continuously for Enabling\_Delay radio frames after application of secondary uplink frequency activation. + +For discontinuous downlink reception: + +**UE\_DRX\_cycle:** HS-SCCH reception pattern length in subframes. + +**Inactivity\_Threshold\_for\_UE\_DRX\_cycle:** Defines the number of subframes after an HS-SCCH reception or after the first slot of an HS-PDSCH reception (as defined in 6C.3) during which the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set continuously with the exceptions of $N\_acknack\_transmit > 1$ or $N\_acknack\_transmit\_2 > 1$ when the UE is configured in multiflow mode or $InterTTI > 1$ . + +**UE\_DRX\_Grant\_Monitoring:** A Boolean which determines whether the UE is required to monitor the E-AGCH and E-ROCH transmissions from the serving E-DCH cell and the E-RGCH from cells in the serving E-DCH radio link set when the conditions in subclause 6C.3 are met. + +When DRX enhancements is configured, the following definitions also apply: + +**UE\_DRX\_cycle\_2:** HS-SCCH reception pattern length in subframes. + +**Inactivity\_Threshold\_for\_UE\_DRX\_cycle\_2:** Defines a number of consecutive subframes without an HS-SCCH reception or after the first slot of an HS-PDSCH reception (as defined in 6C.3), after which the UE shall immediately move from UE\_DRX\_cycle to using UE\_DRX\_cycle\_2. + +## 6C.0 Discontinuous transmission/reception of DCH + +When DL\_DCH\_FET\_Config is configured by higher layers, DL\_DPCH\_DYN\_DRX and UL\_DPCH\_DYN\_DTX control DTX and DRX operations for DPCH transmission and reception. UE shall DRX DL DPDCH if DL\_DPCH\_DYN\_DRX is TRUE. UE shall DTX UL DPDCH if UL\_DPCH\_DYN\_DTX is TRUE. + +In each slot, the values of the Boolean flags DL\_DPCH\_DYN\_DRX and UL\_DPCH\_DYN\_DTX are determined in Subclause 6C.0.1 and 6C.0.2. + +### 6C.0.1 DL\_DPCH\_DYN\_DRX and UL\_DPCH\_DYN\_DTX + +#### 6C.0.1.1 DL\_DCH\_FET\_Config = 0 + +In each UL slot, the UL\_DPCH\_DYN\_DTX is set to TRUE if all of the following conditions are satisfied: + +- This slot is in the second radio frame of 20ms CI. +- UL\_DPCH\_10ms\_Mode is configured by higher layers. + +Or, if all of the following conditions are satisfied: + +- Only a single transport channel is configured with 40ms TTI by higher layers over UL DCH. +- This slot is not in the first radio frame of 40ms CI. +- This slot contains no UL DPDCH bits, i.e., no UL DCH transport blocks are sent in this radio frame. + +Otherwise UL\_DPCH\_DYN\_DTX is set to FALSE. + +In each DL slot, the DL\_DPCH\_DYN\_DRX is set to TRUE if all of the following conditions are satisfied: + +- This slot is in the second radio frame of 20ms CI. +- DL DCH contains no SRBs in this radio frame. +- UL\_DPCH\_10ms\_Mode is configured by higher layers. + +Or, if all of the following conditions are satisfied: + +- Only a single transport channel is configured with 40ms TTI by higher layers over DL DCH. + +- This slot is not in the first radio frame of 40ms CI. +- DL DCH contains no SRBs in this radio frame. + +Otherwise DL\_DPCH\_DYN\_DRX is set to FALSE. + +#### 6C.0.1.2 DL\_DCH\_FET\_Config = 1 + +In each UL slot, the UL\_DPCH\_DYN\_DTX is set to TRUE if all of the following conditions are satisfied, otherwise UL\_DPCH\_DYN\_DTX is set to FALSE: + +- In this 20ms CI, excluding this slot, at least two UL DPCCH slots that contain DL FET ACK bits (Subclause 4.3A of [2]) have been transmitted. +- UL\_DPCH\_10ms\_Mode is configured by higher layers and this slot is in the second radio frame of 20ms CI. + +In each DL slot, the DL\_DPCH\_DYN\_DRX is set to TRUE if all of the following conditions are satisfied, otherwise DL\_DPCH\_DYN\_DRX is set to FALSE + +- In this 20ms CI, at least two UL DPCCH slots that contain DL FET ACK bits (Subclause 4.3A of [2]) have been transmitted before the end of this DL slot. +- UL\_DPCH\_DYN\_DTX in the UL slot started during this DL slot is TRUE. + +## 6C.1 Uplink CQI transmission + +When UL\_DTX\_Active is FALSE (see clause 6C), the UE shall always transmit the Channel-Quality Indication (CQI) in the CQI transmission pattern defined in 6A.1.2. + +When UL\_DTX\_Active is TRUE (see clause 6C), the UE shall perform the following procedures: + +- The UE shall set the initial value of the variable CQI\_DTX\_Priority to 1. +- Reset the "CQI nominal reporting timer" to CQI\_DTX\_TIMER at the first HS-DPCCH subframe boundary. + +Afterwards, when UL\_DTX\_Active is TRUE, the UE sets the CQI\_DTX\_Priority based on the status of a "CQI nominal reporting timer" which is counting down to zero in HS-DPCCH subframes from the value CQI\_DTX\_TIMER which is configured by higher layers. + +The setting of CQI\_DTX\_Priority to 1 is described in subclause 6A.1.1. + +Upon the expiration of the CQI nominal reporting timer, the UE shall set CQI\_DTX\_Priority to 0. + +CQI\_DTX\_Priority=0 indicates that CQI reports have lower priority than the Uplink DPCCH burst pattern. If CQI\_DTX\_Priority is set to 0, the UE shall transmit the Channel-Quality Indication (CQI), and all repeated CQI transmissions (corresponding to the serving HS-DSCH cell and the secondary serving HS-DSCH cell) according to the value of N\_cqi\_transmit, only if the start of the CQI field corresponding to the serving HS-DSCH cell in the CQI transmission pattern as defined in 6A.1.2 overlaps with a DPCCH transmission burst of the Uplink DPCCH burst pattern as indicated in 6C.2.1. + +CQI\_DTX\_Priority=1 indicates that CQI reports have higher priority than the Uplink DPCCH burst pattern. If CQI\_DTX\_Priority is set to 1, + +- the UE shall always transmit the Channel-Quality Indication (CQI), in the CQI transmission pattern defined in 6A.1.2. +- The repeated CQI transmissions according to the value of N\_cqi\_transmit are transmitted only if the start of the CQI field in the CQI transmission pattern, as defined in 6A.1.2, is transmitted. + +## 6C.2 Discontinuous uplink DPCCH/DPCCH2 transmission operation + +When UL\_DTX\_Active is FALSE (see clause 6C) the UE shall transmit the uplink DPCCH in each slot except in the following cases: + +- In the slots overlapping a compressed mode transmission gap. +- If DL\_DCH\_FET\_Config is configured by higher layers, neither HS-DSCH nor E-DCH is configured, and UL\_DPCH\_DYN\_DTX is TRUE (Subclause 6C.0). + +When UL\_DTX\_Active is TRUE (see clause 6C), in addition to the conditions defined in 6C.5 the UE shall not transmit the uplink DPCCH in a slot on an activated uplink frequency when all of the following conditions are met for that uplink frequency: + +1. There is no HARQ-ACK transmission on HS-DPCCH as indicated in 6A.1 overlapping with the UL DPCCH slot, +2. There is no CQI transmission on HS-DPCCH as indicated in 6C.1 overlapping with the UL DPCCH slot, +3. There is no E-DCH transmission during the UL DPCCH slot, +4. The slot is in a gap in the Uplink DPCCH burst pattern defined in 6C.2.1, +5. The UL DPCCH preamble or postamble defined in 6C.2.2 is not transmitted in the slot. +6. Either the uplink frequency is a secondary uplink frequency where at least Enabling\_Delay radio frames have passed since the activation of the secondary uplink frequency was applied, or it is a primary uplink frequency. +7. If DL\_DCH\_FET\_Config is configured by higher layers, UL\_DPCH\_DYN\_DTX is TRUE (subclause 6C.0). + +The procedures for the F-DPCH transmission and reception in case of discontinuous uplink DPCCH operation are defined in subclause 5.1. + +The procedures for the F-TPICH transmission and reception in case of discontinuous uplink DPCCH operation are defined in subclause 10.4. + +When DPCCH2 is configured, DPCCH2 is transmitted only in the slots in which DPCCH is transmitted. + +### 6C.2.1 Uplink DPCCH burst pattern + +The Uplink DPCCH burst pattern and the uplink DPCCH preamble and postamble (6C.2.2) together define the discontinuous uplink DPCCH operation. + +NOTE: When the secondary uplink frequency is active and DTX enhancements is configured, some of the parameters related to the discontinuous UL DPCCH transmission as defined in [5] can be independently configured for the two uplink frequencies. + +The Uplink DPCCH burst pattern is illustrated in Figure 2A for 2ms E-DCH TTI and Figure 2B for 10ms E-DCH TTI. The Uplink DPCCH burst pattern defines the minimum set of slots where the UE shall transmit the UL-DPCCH. + +The Uplink DPCCH burst pattern shall be derived as follows. + +If there has not been any E-DCH transmission for the last Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2 E-DCH TTIs, and at least this many TTIs have passed since the end of the Enabling\_Delay, then: + +- The transmission length in the Uplink DPCCH burst pattern shall be UE\_DPCCH\_burst\_2 subframes. +- The gap length following the DPCCH transmission burst in the Uplink DPCCH burst pattern shall be + - (UE\_DTX\_cycle\_2 – UE\_DPCCH\_burst\_2) subframes, +- The first subframe in each Uplink DPCCH burst pattern shall be such that + - the CFN and DPCCH subframe number S verify + +$$((5 \cdot \text{CFN} - \text{UE\_DTX\_DRX\_Offset} + S) \bmod \text{UE\_DTX\_cycle\_2}) = 0$$ + +Otherwise: + +- The transmission length in the Uplink DPCCH burst pattern shall be UE\_DPCCH\_burst\_1 subframes. +- The gap length following the DPCCH transmission burst in the Uplink DPCCH burst pattern shall be + +- (UE\_DTX\_cycle\_1 – UE\_DPCCH\_burst\_1) subframes. +- The first subframe in each Uplink DPCCH burst pattern shall be such that + - the CFN and DPCCH subframe number S verify + +$$((5*CFN - UE_DTX_DRX_Offset + S) \text{ MOD } UE\_DTX\_cycle\_1) = 0$$ + +In case the DTX cycle pattern changes during a transmission of an Uplink DPCCH burst, the following shall apply: + +- the previously derived length of the Uplink DPCCH burst which has already been started shall not be affected by the change of the DTX cycle pattern. +- if the UL DPCCH burst, which is derived according to the new DTX cycle pattern, overlaps with the ongoing UL DPCCH burst, the non-overlapping portion of the burst, if any, shall be transmitted. +- the change in the DTX cycle pattern from UE\_DTX\_cycle\_2 to UE\_DTX\_cycle\_1 shall occur only at the end of an E-DCH transmission. + +NOTE: The E-DCH transmission start time after data transmission inactivity may be restricted as described in [9] to allow discontinuous reception at Node B. + +![Figure 2A: Example for Uplink DPCCH burst pattern for 2ms E-DCH TTI beginning at CFN=1 (with UE_DTX_DRX_Offset = 6).](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +This diagram illustrates the Uplink DPCCH burst pattern for a 2ms E-DCH TTI. The horizontal axis represents the Connection Frame Number (CFN). A 10ms radio frame is shown at the top, containing five 2ms sub-frames. The E-DCH transmission starts at CFN=1 and continues for several sub-frames. The Uplink DPCCH burst pattern is shown below the E-DCH transmission, with bursts occurring in specific sub-frames. The diagram is divided into two DTX cycles: UE\_DTX\_cycle\_1 and UE\_DTX\_cycle\_2. An 'Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2' is indicated. The pattern shows bursts in the first sub-frame of each 10ms frame during the first cycle, and then changes to a different pattern during the second cycle. + +Figure 2A: Example for Uplink DPCCH burst pattern for 2ms E-DCH TTI beginning at CFN=1 (with UE\_DTX\_DRX\_Offset = 6). + +Figure 2A: Example for Uplink DPCCH burst pattern for 2ms E-DCH TTI beginning at CFN=1 (with UE\_DTX\_DRX\_Offset = 6) + +![Figure 2B: Example for Uplink DPCCH burst pattern for 10ms E-DCH TTI beginning at CFN=1 (with UE_DTX_DRX_Offset = 5).](9ff1b32449ea068bba9647d71904bd59_img.jpg) + +This diagram illustrates the Uplink DPCCH burst pattern for a 10ms E-DCH TTI. The horizontal axis represents the Connection Frame Number (CFN). A 10ms radio frame is shown at the top, containing one 10ms sub-frame. The E-DCH transmission starts at CFN=1 and continues for several sub-frames. The Uplink DPCCH burst pattern is shown below the E-DCH transmission, with bursts occurring in specific sub-frames. The diagram is divided into two DTX cycles: UE\_DTX\_cycle\_1 and UE\_DTX\_cycle\_2. An 'Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2' is indicated. The pattern shows bursts in the first sub-frame of each 10ms frame during the first cycle, and then changes to a different pattern during the second cycle. + +Figure 2B: Example for Uplink DPCCH burst pattern for 10ms E-DCH TTI beginning at CFN=1 (with UE\_DTX\_DRX\_Offset = 5). + +Figure 2B: Example for Uplink DPCCH burst pattern for 10ms E-DCH TTI beginning at CFN=1 (with UE\_DTX\_DRX\_Offset = 5) + +Note: Figures 2A and 2B do not show the application of preambles and postambles as described in subclause 6C.2.2. + +### 6C.2.2 Uplink DPCCH preamble and postamble + +NOTE: The “uplink DPCCH preamble” specified in this subclause is not the same as the “uplink DPCCH power control preamble” specified in clauses 4 and 5. + +#### 6C.2.2.1 Uplink DPCCH preamble and postamble for the DPCCH only transmission + +If a UE will start a transmission of DPCCH based on the Uplink DPCCH burst pattern at the start of slot $s$ and finish its DPCCH transmission at the end of slot $t$ , the UE shall start the DPCCH transmission at the start of slot $s-2$ and continue the DPCCH transmission till the end of slot $t+1$ . + +#### 6C.2.2.2 Uplink DPCCH preamble and postamble for the E-DCH transmission + +If a UE will start a transmission of E-DPCCH and E-DPDCH on a E-DCH TTI, the UE shall start the DPCCH transmission 2 slots prior to the E-DCH TTI and continue the DPCCH transmission during the E-DCH TTI and consecutive E-DCH TTIs and 1 slot after the last consecutive E-DCH TTI. + +In addition, if there has not been any E-DCH transmission for the last $\text{Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2}$ E-DCH TTIs, and if a UE will start a transmission of E-DPCCH and E-DPDCH on a E-DCH TTI, the UE shall start the DPCCH transmission $\text{UE\_DTX\_long\_preamble\_length}$ slots prior to the E-DCH TTI and continue the DPCCH transmission during the E-DCH TTI and consecutive E-DCH TTIs and 1 slot after the last consecutive E-DCH TTI. + +#### 6C.2.2.3 Uplink DPCCH preamble and postamble for the HS-DPCCH transmission + +If a UE will start a transmission of HARQ-ACK, the UE shall start the DPCCH transmission 2 slots prior to the DPCCH slot that coincides with or overlaps the start of the HARQ-ACK field, unless the HARQ-ACK transmission is an HARQ Preamble (PRE) in an HS-DPCCH sub-frame $n - 2$ as defined in subclause 6A.1.1. The UE shall continue the DPCCH transmission during the HARQ-ACK field and until the end of the first full DPCCH slot after the end of the HARQ-ACK field. + +If a UE will start a transmission of CQI, the UE shall start the DPCCH transmission 3 slots prior to the DPCCH slot that coincides with or overlaps the start of the CQI field, and continue the DPCCH transmission during the CQI field and until the end of the first full DPCCH slot after the end of the CQI field. + +In addition, if there has not been any E-DCH transmission for the last $\text{Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2}$ E-DCH TTIs, and if a UE will start a transmission of CQI, the UE shall start the DPCCH transmission $(\text{UE\_DTX\_long\_preamble\_length} + 1)$ slots prior to the DPCCH slot that coincides with or overlaps the start of the CQI field, and continue the DPCCH transmission during the CQI field and until the end of the first full DPCCH slot after the end of the CQI field. If the transmission of the CQI is not known to the UE in advance due to the change of $\text{CQI\_DTX\_Priority}$ from 0 to 1, or due to the change from $\text{UE\_DTX\_cycle\_1}$ to $\text{UE\_DTX\_cycle\_2}$ , the preamble for the first CQI after the change may start late resulting in a shorter preamble. + +## 6C.3 Discontinuous downlink reception + +The HS-SCCH reception pattern is derived from a discontinuous reception subframe numbering as follows. + +The discontinuous HS-SCCH reception subframe numbering is such that: + +- A HS-SCCH discontinuous reception radio frame is 10 ms long and is indexed using $\text{CFN\_DRX}$ . +- The start of the HS-SCCH discontinuous reception radio frame of $\text{CFN\_DRX } n$ is aligned with the start of the HS-SCCH subframe that starts $\tau_{\text{DRX}}$ chips after the start of the associated downlink F-DPCH of $\text{CFN } n$ where $-3840\text{chips} \leq \tau_{\text{DRX}} - T_0 < 3840\text{chips}$ . +- The HS-SCCH subframe $\text{S\_DRX}=0$ is aligned with the start of the HS-SCCH discontinuous reception radio frame. The HS-SCCH subframes are numbered $\text{S\_DRX}=0$ to $\text{S\_DRX}=4$ . +- The HS-PDSCH discontinuous reception radio frame of $\text{CFN\_DRX } n$ starts $\tau_{\text{HS-PDSCH}}$ chips after the start of the HS-SCCH discontinuous reception radio frame of $\text{CFN\_DRX } n$ . The HS-PDSCH subframe $\text{S\_DRX}=0$ is aligned with the start of the HS-PDSCH discontinuous reception radio frame. The HS-PDSCH subframes are numbered $\text{S\_DRX}=0$ to $\text{S\_DRX}=4$ . +- The HS-DPCCH discontinuous transmission radio frame of $\text{CFN\_DRX } n$ starts at the HS-DPCCH subframe boundary closest in time to 1280 chips after the start of the HS-SCCH discontinuous reception radio frame of $\text{CFN\_DRX } n$ as received at the UE. The HS-DPCCH subframe $\text{S\_DRX}=0$ is aligned with the start of the HS-DPCCH discontinuous transmission radio frame. The HS-DPCCH subframes are numbered $\text{S\_DRX}=0$ to $\text{S\_DRX}=4$ . + +If the UE has not detected consistent control information on HS-SCCH nor received data on HS-PDSCH for the last Inactivity\_Threshold\_for\_UE\_DRX\_cycle\_2 subframes, and at least this many subframes have passed since the end of the Enabling\_Delay, then: + +- The HS-SCCH reception pattern is the set of subframes whose HS-SCCH discontinuous reception radio frame number CFN\_DRX and subframe number S\_DRX verify: + +$$((5*CFN\_DRX - UE\_DTX\_DRX\_Offset + S\_DRX) \bmod UE\_DRX\_cycle\_2) = 0$$ + +Otherwise: + +- The HS-SCCH reception pattern is the set of subframes whose HS-SCCH discontinuous reception radio frame number CFN\_DRX and subframe number S\_DRX verify: + +$$((5*CFN\_DRX - UE\_DTX\_DRX\_Offset + S\_DRX) \bmod UE\_DRX\_cycle) = 0$$ + +When the UE is configured with one or more secondary serving HS-DSCH cells and if the UE has not detected consistent control information on HS-SCCH nor received data on HS-PDSCH for the last Inactivity\_Threshold\_for\_UE\_DRX\_cycle\_2 subframes, and at least this many subframes have passed since the end of the Enabling\_Delay, the UE shall perform the following procedures: + +- The secondary serving HS-DSCH cells shall be deactivated, and the UE shall receive HS-SCCHs and HS-PDSCHs only from the serving HS-DSCH cell in the HS-SCCH reception pattern according to the UE\_DRX\_cycle\_2. HS-SCCH orders shall be used to reactivate the secondary serving HS-DSCH cells as needed. +- In case the secondary uplink frequency is activated, the associated secondary serving HS-DSCH cell shall remain activated. + +When DL\_DRX\_Active is FALSE (see clause 6C), the UE shall monitor and receive all downlink physical channels continuously. + +When DL\_DRX\_Active is TRUE (see clause 6C), the UE shall continue to receive F-DPCH as described in subclause 5.1 and the UE need not receive physical downlink channels other than the F-DPCH except for the following cases: + +1. The UE shall receive E-HICH (sub-)frame corresponding to an E-DCH transmission as specified in subclause 6B. +2. The UE shall monitor the HS-SCCH subframes in the HS-SCCH reception pattern. +3. The UE shall receive an HS-PDSCH subframe as specified in subclause 6A. +4. The UE has received an HS-SCCH or an HS-PDSCH subframe during the last Inactivity\_Threshold\_for\_UE\_DRX\_cycle subframes which was not an HS-SCCH order. +5. The UE shall monitor E-AGCH and E-ROCH transmission from the serving E-DCH cell in the following cases: + - If UE\_DRX\_Grant\_Monitoring is TRUE and the E-AGCH/E-ROCH subframe (in case of a 2ms TTI) or E-AGCH frame (in case of a 10ms TTI) overlaps with the start of an HS-SCCH reception subframe as defined in the HS-SCCH reception pattern, + - When conditions defined in subclause 11.8.1.8 of [9] are fulfilled. +6. The UE shall monitor E-RGCH transmission from a cell in the serving E-DCH radio link set in the following cases: + - If UE\_DRX\_Grant\_Monitoring is TRUE and the corresponding subframe (in case of a 2ms TTI) or frame (in case of a 10ms TTI) of the serving cell E-RGCH overlaps with the start of an HS-SCCH reception subframe as defined in the HS-SCCH reception pattern. + - When conditions defined in subclause 11.8.1.8 of [9] are fulfilled. +7. The UE shall monitor the E-RGCH(s) from all the other cells in the E-DCH active set, except from the cells in the serving E-DCH radio link set, in the following case: + - When conditions defined as determined in subclause 11.8.1.8 of [9] are fulfilled. + +The HS-SCCH reception pattern is illustrated by Figure 2C for a 2ms E-DCH TTI. The grey subframes correspond to the HS-SCCH reception pattern *UE\_DRX\_cycle*=4. + +![Figure 2C: Example for HS-SCCH reception pattern, 2ms E-DCH TTI. This diagram shows the timing relationship between various channels (P-CCPCH, F-DPCH, Uplink DPCCH, HS-SCCH, HS-PDSCH, HS-DPCCH) across two radio frames (SFN mod 2 = 0 and SFN mod 2 = 1). It details subframe numbering, slot allocation, and the UE_DRX_cycle of 4. Key timing parameters like T_DPCH,n, T_0 chips, and T_DRX are indicated. A '1280 chips' duration is marked at the bottom.](7cb2bb7f9f6fd8be2dc5679e7053ae04_img.jpg) + +Figure 2C: Example for HS-SCCH reception pattern, 2ms E-DCH TTI. This diagram shows the timing relationship between various channels (P-CCPCH, F-DPCH, Uplink DPCCH, HS-SCCH, HS-PDSCH, HS-DPCCH) across two radio frames (SFN mod 2 = 0 and SFN mod 2 = 1). It details subframe numbering, slot allocation, and the UE\_DRX\_cycle of 4. Key timing parameters like T\_DPCH,n, T\_0 chips, and T\_DRX are indicated. A '1280 chips' duration is marked at the bottom. + +**Figure 2C: Example for HS-SCCH reception pattern, 2ms E-DCH TTI** + +The HS-SCCH reception pattern is illustrated by Figure 2D for a 10 ms TTI E-DCH. The grey subframes correspond to the HS-SCCH reception pattern *UE\_DRX\_cycle*=5. + +![Figure 2D: Example for HS-SCCH reception pattern, 10ms E-DCH TTI. This diagram is similar to Figure 2C but for a 10ms TTI. It shows the same channels and timing parameters but with a different subframe arrangement corresponding to a 10ms TTI. The UE_DRX_cycle is indicated as 5. A '1280 chips' duration is also marked at the bottom.](b88b618bb8863766bd545c6bfb31f850_img.jpg) + +Figure 2D: Example for HS-SCCH reception pattern, 10ms E-DCH TTI. This diagram is similar to Figure 2C but for a 10ms TTI. It shows the same channels and timing parameters but with a different subframe arrangement corresponding to a 10ms TTI. The UE\_DRX\_cycle is indicated as 5. A '1280 chips' duration is also marked at the bottom. + +**Figure 2D: Example for HS-SCCH reception pattern, 10ms E-DCH TTI** + +### 6C.3.1 Discontinuous downlink reception when the UE is in Multiflow mode + +When the UE is in Multiflow mode the discontinuous downlink reception for the time reference cell operates as defined in subclause 6C.3 for the case when the UE is not in Multiflow mode. + +The discontinuous HS-SCCH reception subframe numbering in the non-time reference cell at the UE is such that: + +- The HS-SCCH discontinuous transmission radio frame of CFN\_DRX n in the non-time reference cell is derived from the HS-SCCH discontinuous transmission radio frame of CFN\_DRX n in the time reference cell, with the related HS-PDSCH subframes are paired subframes, i.e. the corresponding HARQ-ACK fields in the same HS-DPCCH sub-frame. + +- The HS-DPCCH discontinuous transmission radio frame of CFN\_DRX n in the non-time reference cell is identical to the HS-DPCCH discontinuous transmission radio frame of CFN\_DRX n in the time reference cell. + +The discontinuous HS-SCCH reception subframe numbering in the non-time reference cell at the NodeB is such that: + +- A HS-SCCH discontinuous reception radio frame is 10 ms long and is indexed using CFN\_DRX. +- The start of the HS-SCCH discontinuous reception radio frame of CFN\_DRX n is aligned with the start of the HS-SCCH subframe that starts $\tau_{\text{DRX}}$ chips after the start of the associated downlink F-DPCH of CFN n where $-3840\text{chips} \leq \tau_{\text{DRX}} - T_0 - 7680 * \text{DRX\_OFFSET} < 3840\text{chips}$ , and $\text{DRX\_OFFSET}$ is defined as $\text{DRX\_OFFSET} = \left\lfloor \frac{\frac{T_{\text{TX\_diff2}}}{2560} - 0.9}{3} \right\rfloor - \left\lfloor \frac{\frac{T_{\text{TX\_diff1}}}{2560} - 0.9}{3} \right\rfloor$ , where $T_{\text{TX\_diff1}}$ and $T_{\text{TX\_diff2}}$ are as defined in [1]. +- The HS-SCCH subframe S\_DRX=0 is aligned with the start of the HS-SCCH discontinuous reception radio frame. The HS-SCCH subframes are numbered S\_DRX=0 to S\_DRX=4. +- The HS-PDSCH discontinuous reception radio frame of CFN\_DRX n starts $\tau_{\text{HS-PDSCH}}$ chips after the start of the HS-SCCH discontinuous reception radio frame of CFN\_DRX n. The HS-PDSCH subframe S\_DRX=0 is aligned with the start of the HS-PDSCH discontinuous reception radio frame. The HS-PDSCH subframes are numbered S\_DRX=0 to S\_DRX=4. +- The HS-DPCCH discontinuous transmission radio frame of CFN\_DRX n starts at the HS-DPCCH subframe boundary closest in time to $1280 + T_{\text{TX\_diff1}} - T_{\text{TX\_diff2}}$ after the start of the HS-SCCH discontinuous reception radio frame of CFN\_DRX n as received at the UE. The HS-DPCCH subframe S\_DRX=0 is aligned with the start of the HS-DPCCH discontinuous transmission radio frame. The HS-DPCCH subframes are numbered S\_DRX=0 to S\_DRX=4. + +## 6C.4 HS-SCCH orders + +When the UE is not configured in Multiflow mode, the Node B may activate and deactivate the discontinuous downlink reception operation and discontinuous uplink DPCCH transmission operation through physical layer commands transmitted on one of the HS-SCCH in the HS-SCCH set as specified in [2] and in subclause 6A.1.1. + +When E-DCH\_decoupling is configured, discontinuous uplink DPCCH transmission cannot be deactivated or activated through HS-SCCH orders. + +- The activation and deactivation of the discontinuous uplink DPCCH transmission operation is applied by the UE at the earliest E-DCH TTI boundary coinciding with or following the beginning of the HS-DPCCH subframe containing the HARQ-ACK corresponding to the order. +- The activation and deactivation of the discontinuous downlink reception operation is applied by the UE 12 slots after the ending of the HS-SCCH subframe delivering the order. +- The activation and deactivation shall affect all frequencies configured to the UE. + +## 6C.5 Operation during compressed mode + +When in compressed mode, the UE shall behave according to subclauses 6A.3 and 6B.4 including the following rules. + +The uplink discontinuous transmission operation is not impacted by the compressed mode in the radio frames that do not overlap an uplink compressed mode transmission gap as defined in subclause 6.1.1 of [4]. + +In radio frames that overlap an uplink compressed mode transmission gap as defined in subclause 6.1.1 of [4], the uplink DPCCH shall be transmitted in all slots in the radio frame that do not overlap the uplink compressed mode transmission gap if either of the following is true: + +- an uplink DPCCH transmission defined by the Uplink DPCCH burst pattern according to subclause 6C.2.1 overlaps an uplink compressed mode transmission gap, or +- an uplink DPCCH preamble or postamble according to subclause 6C.2.2 corresponding to an uplink DPCCH transmission defined by the Uplink DPCCH burst pattern overlaps an uplink compressed mode transmission gap. + +If the 2 bullets above are not true, the following are not affected by compressed mode: + +- uplink DPCCH transmission according to Uplink DPCCH burst patterns defined in subclause 6C.2.1, +- uplink DPCCH preamble transmission corresponding to an uplink DPCCH transmission defined by the Uplink DPCCH burst pattern, +- uplink DPCCH postamble transmission corresponding to an uplink DPCCH transmission defined by the Uplink DPCCH burst pattern. + +If part of an uplink DPCCH preamble or postamble corresponding to an E-DCH or HS-DPCCH transmission overlaps an uplink compressed mode transmission gap, then that part of the preamble or postamble shall not be transmitted. + +If an HS-SCCH subframe in the HS-SCCH reception pattern for downlink discontinuous reception according to subclause 6C.3 overlaps with a downlink compressed mode transmission gap, the following is true: + +- the reception of an HS-SCCH subframe is postponed to the first full HS-SCCH subframe after the downlink compressed mode transmission gap. +- if UE\_DRX\_Grant\_Monitoring is TRUE and the conditions defined in subclause 11.8.1.8 of [9] are not fulfilled, the UE may discard the E-AGCH/E-ROCH and E-RGCH subframe (in case of 2ms TTI) or frame (in case of 10ms TTI) that overlaps with the start of the postponed HS-SCCH subframe. + +Note that the compressed mode parameters (see [5]) ‘‘UL compressed mode method’’, ‘‘DL compressed mode method’’ and ‘‘scrambling code change’’ have no effect on the UE behaviour while DTX\_DRX\_STATUS is TRUE. + +# --- 7 Closed loop mode 1 transmit diversity + +The general transmitter structure to support closed loop mode transmit diversity for DPCH transmission is shown in figure 3. Channel coding, interleaving and spreading are done as in non-diversity mode. The spread complex valued signal is fed to both TX antenna branches, and weighted with antenna specific weight factors $w_1$ and $w_2$ . The weight factor $w_1$ is a constant scalar and the weight factor $w_2$ is complex valued signal. + +The weight factor $w_2$ (actually the corresponding phase adjustment) is determined by the UE, and signalled to the UTRAN access point (i.e. cell transceiver) using the FBI field of uplink DPCCH. + +For the closed loop mode 1 different orthogonal dedicated pilot symbols in the DPCCH are sent on the 2 different antennas. Closed-loop transmit diversity for DPCH is not supported with downlink slot formats 17 and 18 in [1]. + +![Figure 3: The generic downlink transmitter structure to support closed loop mode transmit diversity for DPCH transmission. The diagram shows two input channels, DPCCH and DPDCH, entering a 'DPCH' block. The output of this block goes to a 'Spread/scramble' block. The output of 'Spread/scramble' is split into two branches. Each branch contains a multiplier (represented by a circle with an 'X') where the signal is multiplied by a weight, w1 and w2 respectively. The outputs of these multipliers are then summed (represented by a circle with a 'Σ') with CPICH1 and CPICH2 signals. The final outputs are transmitted via antennas Ant1 and Ant2. Below the main transmitter, a 'Determine FBI message from Uplink DPCCH' block feeds into a 'Weight Generation' block, which outputs the weights w1 and w2.](8269648391c59363ea61243864a2adf7_img.jpg) + +Figure 3: The generic downlink transmitter structure to support closed loop mode transmit diversity for DPCH transmission. The diagram shows two input channels, DPCCH and DPDCH, entering a 'DPCH' block. The output of this block goes to a 'Spread/scramble' block. The output of 'Spread/scramble' is split into two branches. Each branch contains a multiplier (represented by a circle with an 'X') where the signal is multiplied by a weight, w1 and w2 respectively. The outputs of these multipliers are then summed (represented by a circle with a 'Σ') with CPICH1 and CPICH2 signals. The final outputs are transmitted via antennas Ant1 and Ant2. Below the main transmitter, a 'Determine FBI message from Uplink DPCCH' block feeds into a 'Weight Generation' block, which outputs the weights w1 and w2. + +**Figure 3: The generic downlink transmitter structure to support closed loop mode transmit diversity for DPCH transmission.** + +Closed loop mode 1 characteristics are summarised in the Table 8. The use of the closed loop mode 1 is controlled via higher layer signalling. + +**Table 8: Summary of number of feedback information bits per slot, $N_{FBD}$ , feedback command length in slots, $N_w$ , feedback command rate, feedback bit rate, number of phase bits, $N_{ph}$ , per signalling word, number of amplitude bits, $N_{po}$ , per signalling word and amount of constellation rotation at UE for the closed loop mode 1.** + +| $N_{FBD}$ | $N_w$ | Update rate | Feedback bit rate | $N_{po}$ | $N_{ph}$ | Constellation rotation | +|-----------|-------|-------------|-------------------|----------|----------|------------------------| +| 1 | 1 | 1500 Hz | 1500 bps | 0 | 1 | $\pi/2$ | + +## 7.1 General procedure + +The UE uses the CPICH to separately estimate the channels seen from each antenna. + +Once every slot, the UE computes the phase adjustment, $\phi$ , that should be applied at the UTRAN access point to maximise the UE received power. During soft handover, the UE computes the phase adjustment to maximise the total UE received power from the cells in the active set. In the case that a HS-PDSCH is associated with a DPCH for which closed loop mode 1 is applied, the antenna weights applied to the HS-PDSCH, are the same as the antenna weights applied to the associated DPCH. In case a HS-PDSCH is associated with a DPCH during soft handover, the UE may emphasize the radio link transmitted from HS-PDSCH serving cell, respectively, when calculating the antenna weights. An example of how the computations can be accomplished is given in Annex A.2. + +The UE feeds back to the UTRAN access point the information on which phase/power settings to use. Feedback Signalling Message (FSM) bits are transmitted in the FBI field of uplink DPCCH slot(s) (see [1]). Each message is of length $N_W = N_{po} + N_{ph}$ bits and its format is shown in the figure 4. The transmission order of bits is from MSB to LSB, i.e. MSB is transmitted first. $FSM_{po}$ and $FSM_{ph}$ subfields are used to transmit the power and phase settings, respectively. + +![Diagram of feedback signalling message format showing MSB and LSB fields, FSM_ph and FSM_po, with lengths N_ph and N_po.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram shows a horizontal rectangle representing a feedback signalling message. Above the left half is the label 'MSB' and above the right half is 'LSB'. The left half is labeled 'FSMph' and has a double-headed arrow below it labeled 'Nph'. The right half is labeled 'FSMpo' and has a double-headed arrow below it labeled 'Npo'. A vertical line in the center separates the two halves. + +Diagram of feedback signalling message format showing MSB and LSB fields, FSM\_ph and FSM\_po, with lengths N\_ph and N\_po. + +**Figure 4: Format of feedback signalling message. FSMpo transmits the power setting and FSMph the phase setting.** + +The adjustments are made by the UTRAN Access Point at the beginning of the downlink DPCCH pilot field. The downlink slot in which the adjustment is done is signalled to L1 of UE by higher layers. Two possibilities exist: + +- 1) When feedback command is transmitted in uplink slot *i*, which is transmitted approximately 1024 chips in offset from the received downlink slot *j*, the adjustment is done at the beginning of the pilot field of the downlink slot *(i+1) mod 15*. +- 2) When feedback command is transmitted in uplink slot *i*, which is transmitted approximately 1024 chips in offset from the received downlink slot *j*, the adjustment is done at the beginning of the pilot field of the downlink slot *(i+2) mod 15*. + +Thus, adjustment timing at UTRAN Access Point is either according to 1) or 2) as controlled by the higher layers. + +In case of soft handover, Layer 1 shall support different adjustment timing values for different radio links in the same active set. + +The timing of the weight adjustment of the HS-PDSCH is such that the HS-PDSCH weight adjustment is done at the HS-PDSCH slot border, respectively, *M* chips after the adjustment of the associated DPCH, where $0 \leq M < 2560$ . + +## 7.2 Determination of feedback information + +The UE uses the CPICH transmitted both from antenna 1 and antenna 2 to calculate the phase adjustment to be applied at UTRAN access point to maximise the UE received power. In each slot, UE calculates the optimum phase adjustment, $\phi$ , for antenna 2, which is then quantized into $\varphi_Q$ having two possible values as follows: + +$$\varphi_Q = \begin{cases} \pi, & \text{if } \pi/2 < \phi - \phi_r(i) \leq 3\pi/2 \\ 0, & \text{otherwise} \end{cases} \quad (1)$$ + +where: + +$$\phi_r(i) = \{0, i = 0, 2, 4, 6, 8, 10, 12, 14\} \quad (2)$$ + +If $\varphi_Q = 0$ , a command '0' is sent to UTRAN using the FSMph field. Correspondingly, if $\varphi_Q = \pi$ , command '1' is sent to UTRAN using the FSMph field. + +Due to rotation of the constellation at UE the UTRAN interprets the received commands according to table 9 which shows the mapping between phase adjustment, $\phi_i$ , and received feedback command for each uplink slot. + +**Table 9: Phase adjustments, $\phi_i$ , corresponding to feedback commands for the slots *i* of the UL radio frame** + +| Slot # | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|---|-------|----------|-------|----------|-------|----------|-------|----------|-------|----------|-------|----------|-------|----------| +| FSM | 0 | 0 | $\pi/2$ | 0 | $\pi/2$ | 0 | $\pi/2$ | 0 | $\pi/2$ | 0 | $\pi/2$ | 0 | $\pi/2$ | 0 | $\pi/2$ | +| | 1 | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | $\pi$ | $-\pi/2$ | + +The weight $w_2$ is then calculated by averaging the received phases over 2 consecutive slots. Algorithmically, $w_2$ is calculated as follows: + +$$w_2 = \frac{\sum_{i=n-1}^n \cos(\phi_i)}{2} + j \frac{\sum_{i=n-1}^n \sin(\phi_i)}{2} \quad (3)$$ + +where: + +$$\varphi_i \in \{0, \pi, \pi/2, -\pi/2\} \quad (4)$$ + +For antenna 1, $w_1$ is constant: + +$$w_1 = 1/\sqrt{2} \quad (5)$$ + +### 7.2.1 End of frame adjustment + +In closed loop mode 1 at frame borders the averaging operation is slightly modified. Upon reception of the FB command for slot 0 of a frame, the average is calculated based on the command for slot 13 of the previous frame and the command for slot 0 of the current frame, i.e. $\phi_i$ from slot 14 is not used: + +$$w_2 = \frac{\cos(\varphi_{13}^{j-1}) + \cos(\varphi_0^j)}{2} + j \frac{\sin(\varphi_{13}^{j-1}) + \sin(\varphi_0^j)}{2} \quad (6)$$ + +where: + +- $\varphi_{13}^{j-1}$ = phase adjustment from frame j-1, slot 13. +- $\varphi_0^j$ = phase adjustment from frame j, slot 0. + +### 7.2.2 Normal initialisation + +For the first frame of transmission UE determines the feedback commands in a normal way and sends them to UTRAN. + +Before the first FB command is received, the UTRAN shall use the initial weight $w_2 = \frac{1}{2}(1 + j)$ . + +Having received the first FB command the UTRAN calculates $w_2$ as follows: + +$$w_2 = \frac{\cos(\pi/2) + \cos(\varphi_0)}{2} + j \frac{\sin(\pi/2) + \sin(\varphi_0)}{2} \quad (7)$$ + +where: + +$\varphi_0$ = phase adjustment from slot 0 of the first frame. + +### 7.2.3 Operation during compressed mode + +#### 7.2.3.1 Downlink in compressed mode and uplink in normal mode + +When downlink is in compressed mode but uplink is operating normally (i.e. not compressed) the UTRAN continues its Tx diversity related functions in the same way as in non-compressed downlink mode. + +In downlink transmission gaps there are uplink slots for which no new estimate of the phase adjustment is calculated. During these slots the following rules are applied in UE when determining the feedback command: + +- 1) If no new estimate of phase adjustment $\phi_i$ exists corresponding to the feedback command to be sent in uplink slot $i$ : + - If $1 < i < 15$ : + - the feedback command sent in uplink slot $i-2$ is used; + - else if $i = 0$ : + - the feedback command sent in uplink slot 14 of previous frame is used; + - else if $i = 1$ : + - the feedback command sent in uplink slot 13 of previous frame is used; + - end if. +- 2) When transmission in downlink is started again in downlink slot $N_{\text{last}}+1$ (if $N_{\text{last}}+1 = 15$ , then slot 0 in the next frame) the UE must resume calculating new estimates of the phase adjustment. The feedback command + +corresponding to the first new estimate of $\phi_i$ must be sent in the uplink slot which is transmitted approximately 1024 chips in offset from the downlink slot $N_{\text{last}}+1$ . + +#### 7.2.3.2 Both downlink and uplink in compressed mode + +During the uplink transmission gaps no FB commands are sent from UE to UTRAN. When transmission in downlink is started again in downlink slot $N_{\text{last}}+1$ (if $N_{\text{last}}+1 = 15$ , then slot 0 in the next frame) the UE must resume calculating new estimates of the phase adjustment. The feedback command corresponding to the first new estimate of $\phi_i$ must be sent in the uplink slot which is transmitted approximately 1024 chips in offset from the downlink slot $N_{\text{last}}+1$ . + +The UTRAN continues to update the weight $w_2$ until the uplink transmission gap starts and no more FB commands are received. When the transmission in downlink resumes in slot $N_{\text{last}}+1$ , the value of $w_2$ , calculated after receiving the last FB command before the start of the uplink transmission gap, is applied to antenna 2 signal. + +After the UE resumes transmission in uplink and sends the first FB command, the new value of $w_2$ is calculated as follows: + +- $S_1 = \{0, 2, 4, 6, 8, 10, 12, 14\}$ . +- $S_2 = \{1, 3, 5, 7, 9, 11, 13\}$ . +- $i$ = number of uplink slot at which the transmission resumes. +- $j$ = number of uplink slot at which the last FB command was sent before the start of the uplink transmission gap. +- Do while ( $i \in S_1$ and $j \in S_1$ ) or ( $i \in S_2$ and $j \in S_2$ ): + - $j = j-1$ ; + - if $j < 0$ ; + - $j = 14$ ; + - end if; + - end do; + - calculate $w_2$ based on FB commands received in uplink slots $i$ and $j$ . + +Note that for $N_{\text{last}} = 13$ the end of frame adjustment procedure shall be based on the FB commands for the last odd slot prior to the uplink transmission gap and slot 0. + +#### 7.2.3.3 Uplink in compressed mode and downlink in normal mode + +The UTRAN continues to update the value of $w_2$ until the uplink transmission gap starts and no more FB commands are received. Then, the value of $w_2$ calculated after receiving the last FB command before the uplink transmission gap is applied to the antenna 2 signal. When the UE resumes transmission in uplink, it shall send FB commands according to subclause 7.2 equations 2 and 3 (normal operation) and the UTRAN Access Point shall interpret the FB commands according to Table 9. + +The calculation of $w_2$ by the UTRAN following the uplink transmission gap, and before the first two FB commands following the gap are received is not specified. + +### 7.2.4 Initialisation during compressed mode + +#### 7.2.4.1 Downlink in compressed mode + +When closed loop mode 1 is initialised during the downlink transmission gap of compressed mode there are slots for which no estimate of the phase adjustment is calculated and no previous feedback command is available. + +In this case, if the UE is required to send feedback in the uplink, the FB command to the UTRAN shall be '0'. + +When transmission in downlink is started again in slot $N_{\text{last}}+1$ (if $N_{\text{last}}+1 = 15$ , then slot 0 in the next frame), the UTRAN shall use the initial weight $w_2 = \frac{1}{2}(1 + j)$ . The UE must start calculating estimates of the phase adjustment. The feedback command corresponding to the first estimate of $\phi_i$ must be sent in the uplink slot which is transmitted + +approximately 1024 chips in offset from the downlink slot $N_{\text{last}}+1$ . Having received this feedback command the UTRAN calculates $w_2$ as follows: + +$$w_2 = \frac{\cos(\varphi_i) + \cos(\varphi_j)}{2} + j \frac{\sin(\varphi_i) + \sin(\varphi_j)}{2} \quad (8)$$ + +where: + +$\varphi_i$ = phase adjustment in uplink slot $i$ , which is transmitted approximately 1024 chips in offset from the downlink slot $N_{\text{last}}+1$ . + +$\varphi_j = \frac{\pi}{2}$ , if slot $i$ is even ( $i \in \{0, 2, 4, 6, 8, 10, 12, 14\}$ ) and + +$\varphi_j = 0$ , if slot $i$ is odd ( $i \in \{1, 3, 5, 7, 9, 11, 13\}$ ) + +#### 7.2.4.2 Uplink in compressed mode + +Initialisation of closed loop mode 1 operation during uplink compressed mode only is not specified. + +## 7.3 Void + +# 8 Idle periods for IPDL location method + +## 8.1 General + +To support time difference measurements for location services, idle periods can be created in the downlink (hence the name IPDL) during which time transmission of all channels from a Node B is temporarily seized. During these idle periods the visibility of neighbour cells from the UE is improved. + +The idle periods are arranged in a predetermined pseudo random fashion according to higher layer parameters. Idle periods differ from compressed mode in that they are shorter in duration, all channels are silent simultaneously, and no attempt is made to prevent data loss. + +In general there are two modes for these idle periods: + +- Continuous mode, and +- Burst mode. + +In continuous mode the idle periods are active all the time. In burst mode the idle periods are arranged in bursts where each burst contains enough idle periods to allow a UE to make sufficient measurements for its location to be calculated. The bursts are separated by a period where no idle periods occur. + +## 8.2 Parameters of IPDL + +The following parameters are signalled to the UE via higher layers: + +**IP\_Status:** This is a logic value that indicates if the idle periods are arranged in continuous or burst mode. + +**IP\_Spacing:** The number of 10 ms radio frames between the start of a radio frame that contains an idle period and the next radio frame that contains an idle period. Note that there is at most one idle period in a radio frame. + +**IP\_Length:** The length of the idle periods, expressed in symbols of the CPICH. + +**IP\_Offset:** A cell specific offset that can be used to synchronise idle periods from different sectors within a Node B. + +**Seed:** Seed for the pseudo random number generator. + +Additionally in the case of burst mode operation the following parameters are also communicated to the UE. + +**Burst\_Start:** Specifies the start of the first burst of idle periods. $256 \times \text{Burst\_Start}$ is the SFN where the first burst of idle periods starts. + +**Burst\_Length:** The number of idle periods in a burst of idle periods. + +**Burst\_Freq:** Specifies the time between the start of a burst and the start of the next burst. $256 \times \text{Burst\_Freq}$ is the number of radio frames of the primary CPICH between the start of a burst and the start of the next burst. + +## 8.3 Calculation of idle period position + +In burst mode, burst #0 starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start}$ . Burst # $k$ starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start} + k \times 256 \times \text{Burst\_Freq}$ ( $k = 0, 1, 2, \dots$ ). The sequence of bursts according to this formula continues up to and including the radio frame with $\text{SFN} = 4095$ . At the start of the radio frame with $\text{SFN} = 0$ , the burst sequence is terminated (no idle periods are generated) and at $\text{SFN} = 256 \times \text{Burst\_Start}$ the burst sequence is restarted with burst #0 followed by burst #1 etc., as described above. + +Continuous mode is equivalent to burst mode, with only one burst spanning the whole SFN cycle of 4096 radio frames, this burst starting in the radio frame with $\text{SFN} = 0$ . + +Assume that $\text{IP\_Position}(x)$ is the position of idle period number $x$ within a burst, where $x = 1, 2, \dots$ , and $\text{IP\_Position}(x)$ is measured in number of CPICH symbols from the start of the first radio frame of the burst. + +The positions of the idle periods within each burst are then given by the following equation: + +$$\text{IP\_Position}(x) = (x \times \text{IP\_Spacing} \times 150) + (\text{rand}(x \bmod 64) \bmod (150 - \text{IP\_Length})) + \text{IP\_Offset};$$ + +where $\text{rand}(m)$ is a pseudo random generator defined as follows: + +$$\text{rand}(0) = \text{Seed};$$ + +$$\text{rand}(m) = (106 \times \text{rand}(m - 1) + 1283) \bmod 6075, m = 1, 2, 3, \dots$$ + +Note that $x$ is reset to $x = 1$ for the first idle period in every burst. + +Figure 6 below illustrates the idle periods for the burst mode case. + +![Diagram illustrating Idle Period placement in burst mode operation across four levels: Slot, Frame, Burst, and SFN.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +The diagram illustrates the placement of Idle Periods (IP) in burst mode operation across four hierarchical levels: + +- Slot Level:** Shows Slot #n and Slot #n+1. An idle period of length $IP\_Length$ is shown at the end of Slot #n. +- Frame Level:** Shows a frame containing multiple slots, including Slot #0, Slot #1, and Slot #14. The $x^{th}$ idle period in the burst is located within a slot. The formula for its position is $rand(x \bmod 64) \bmod (150 - IP\_Length) + IP\_Offset$ . +- Burst Level:** Shows a sequence of frames starting from Frame #i. Idle periods are placed every $IP\_Spacing$ frames. The $x^{th}$ idle period is at $IP\_Position(x)$ . The first idle period is at $IP\_Position(1)$ . The $(Burst\_Length)^{th}$ idle period is also indicated. The total duration of $x$ idle periods is $x \times IP\_Spacing$ frames. +- SFN Level:** Shows the start of Burst #0 at $SFN = 0$ . The start of Burst #1 is at $SFN = 256 \times Burst\_Start + 256 \times Burst\_Freq$ . The start of Burst #0 is at $SFN = 256 \times Burst\_Start$ . The duration between the start of Burst #0 and Burst #1 is $256 \times Burst\_Freq$ frames. The duration from $SFN = 0$ to the start of Burst #0 is $256 \times Burst\_Start$ frames. + +Diagram illustrating Idle Period placement in burst mode operation across four levels: Slot, Frame, Burst, and SFN. + +Figure 6: Idle Period placement in the case of burst mode operation + +# 9 MIMO operation of HS-DSCH + +There are two possibilities for operating MIMO: MIMO mode when single-stream restriction is not configured, in which both single and dual stream transmission can be applied, and MIMO mode when single-stream restriction is configured, which is restricted only to single stream transmission. This section applies only when a UE is configured in MIMO mode. + +The general transmitter structure to support MIMO operation of HS-PDSCH transmission is shown in figure 7. Channel coding, interleaving and spreading are done as in non-MIMO mode. When single-stream restriction is not configured the Node B scheduler can decide to transmit one or two transport blocks to a UE in one TTI in the serving HS-DSCH cell, and one or two transport blocks in a secondary serving HS-DSCH cell if the UE is configured with a secondary serving HS-DSCH cell in which MIMO is configured, whereas when single-stream restriction is configured only transmission of single transport block is allowed in any of the cells. The spread complex valued signals are fed to both TX antenna branches, and weighted with precoding weights $w_1$ , $w_2$ , $w_3$ and $w_4$ . The precoding weights $w_1$ and $w_3$ are constant real valued scalars and the precoding weights $w_2$ and $w_4$ are variable complex valued scalars. The precoding weights $w_1$ , $w_2$ , $w_3$ and $w_4$ are defined as follows: + +$$w_3 = w_1 = 1/\sqrt{2},$$ + +$$w_4 = -w_2,$$ + +$$w_2 \in \left\{ \frac{1+j}{2}, \frac{1-j}{2}, \frac{-1+j}{2}, \frac{-1-j}{2} \right\}.$$ + +If single-stream restriction is configured, or single-stream restriction is not configured and the Node B schedules a single transport block in a cell to a UE in one TTI, it uses the precoding vector $(w_1, w_2)$ for transmission of that transport block on the HS-PDSCH sub-frame. If single-stream restriction is not configured and the UTRAN schedules two transport blocks in a cell to a UE in one TTI, it uses two orthogonal precoding vectors to transmit the two transport blocks. The precoding vector $(w_1, w_2)$ is called the primary precoding vector which is used for transmitting the primary transport block and the precoding vector $(w_3, w_4)$ is called secondary precoding vector which is used for transmitting the secondary transport block, respectively. + +If single-stream restriction is configured (Figure 7a) the secondary transport block is never present. If single-stream restriction is not configured (figure 7) the Node B can dynamically schedule the UE with one or two transport blocks. + +![Figure 7: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is not configured.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +This diagram illustrates the downlink transmitter structure for MIMO operation. It features two transport blocks: a Primary transport block (HS-DSCH) and a Secondary transport block (HS-DSCH). Both blocks undergo TrCH processing and are then spread/scrambled. The spread/scrambled signals are multiplied by weights $w_1, w_2, w_3, w_4$ generated by a Weight Generation block. The Weight Generation block receives input from a 'Determine weight info message from the uplink'. The weighted signals are then summed and transmitted via two antennas, Ant1 and Ant2. CPICH1 and CPICH2 signals are also transmitted via the antennas. A legend indicates that the Primary transport block is always present for scheduled UE, and the Secondary transport block is optionally present for scheduled UE. + +Figure 7: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is not configured. + +Figure 7: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is not configured. + +![Figure 7a: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is configured.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +This diagram shows the downlink transmitter structure when a single-stream restriction is configured. Only the Primary transport block (HS-DSCH) is processed through TrCH and spread/scrambling. It is then multiplied by weights $w_1$ and $w_2$ from the Weight Generation block, which is informed by an uplink message. The weighted signals are summed and transmitted via Ant1 and Ant2 along with CPICH1 and CPICH2 signals. A legend indicates that the Primary transport block is always present for scheduled UE. + +Figure 7a: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is configured. + +Figure 7a: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission when single-stream restriction is configured. + +## 9.1 General procedure + +The UE uses the CPICH to separately estimate the channels seen from each antenna. One of the antennas will transmit the Antenna 1 modulation pattern of the P-CPICH as defined in subclause 5.3.3.1 of [1]. The other antenna will transmit + +either the Antenna 2 modulation pattern of the P-CPICH or the Antenna 1 modulation pattern of a S-CPICH. The Pilot configuration in support of MIMO operation of HS-DSCH in the cell is signalled by higher layers. + +The UE determines a preferred primary precoding vector $(w_1^{\text{pref}}, w_2^{\text{pref}})$ and signals it to the Node B. The signalled information about the preferred primary precoding vector is termed precoding control indication (PCI) and is defined in subclause 6A.4. The PCI is signalled to the Node B together with channel quality indication (CQI) as a composite PCI/CQI report according to the procedure defined in subclause 6A.1.2.2. The UE transmits the composite PCI/CQI report to the Node B using the CQI field on the HS-DPCCH as defined in [1]. Based on the composite PCI/CQI reports, the Node B scheduler decides when single-stream restriction is not configured whether to schedule one or two transport blocks in a cell to a UE in one TTI and what transport block size(s) and modulation scheme(s) to use for each of them. + +The Node B signals to the UE the precoding weight $w_2$ applied on the HS-PDSCH sub-frame using the precoding weight indication bits of part 1 of the corresponding HS-SCCH sub-frame. The precoding weight adjustment of each HS-PDSCH is done at the HS-PDSCH sub-frame border. + +# 10 Uplink Closed Loop Transmit Diversity operation + +The use of uplink CLTD is controlled by higher layer signalling. If the UE is configured with UL CLTD, then UL\_CLTD\_Enabled is set to TRUE, otherwise UL\_CLTD\_Enabled is set to FALSE and UL\_CLTD\_Active is 0. UL\_CLTD\_Active shall be set to 1, 2 or 3 while UL\_CLTD\_Enabled is TRUE and CLTD activation state 1, 2 or 3 is activated through HS-SCCH orders respectively. + +At the time when UL\_CLTD\_Enabled is set to TRUE, UL\_CLTD\_Active shall be set to 1 or 2 as indicated by higher layer signaling. If activation state 1 is configured, or a transition from a different activation state to activation state 1 occurs through an HS-SCCH order, the TPI is initially set to the fixed precoder weight corresponding to the bit pattern "1100" in Table 10. The parameter UL\_CLTD\_Active may be further switched to other CLTD activation states through HS-SCCH orders, as described in [2]. + +Upon higher layer signaling that does not result in a serving cell change, the UE shall remember its current UL CLTD activation state and use the last received pre-coding vector after the RRC reconfiguration. Upon higher layer signaling that results in serving cell change, CLTD activation state is either reset or maintained in the RRC reconfiguration message. If activation state 1 is configured, the TPI is initially set to the fixed precoder weight corresponding to the bit pattern "1100" in Table 10. + +The secondary dedicated pilot channel, S-DPCCH, is transmitted as long as UL DPCCH is transmitted when UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is set to 1. + +## 10.1 General procedure + +The general transmitter structure to support uplink CLTD activation state 1 is shown in Figure 8. Channel coding, interleaving and spreading are done as in the case where uplink CLTD is not configured. If UL\_CLTD\_Active is 1, the complex-valued signal after spreading is fed to both TX antenna branches and weighted with precoding weights $w_1$ , $w_2$ , $w_3$ and $w_4$ . The same precoding weights, $w_1$ and $w_2$ , are always applied to DPCCH, DPCCH2 and DPDCH if present, E-DPCCH, E-DPDCH and the HS-DPCCH. The S-DPCCH is pre-coded with precoding weights $w_3$ and $w_4$ . + +The beamforming weight matrix is given by + +$$\begin{bmatrix} w_1 & w_3 \\ w_2 & w_4 \end{bmatrix} = \begin{bmatrix} ae^{-j\frac{\theta}{2}} & ae^{-j\frac{\theta}{2}} \\ ae^{j\frac{\theta}{2}} & -ae^{j\frac{\theta}{2}} \end{bmatrix}$$ + +where normalized amplitude $a = \frac{1}{\sqrt{2}}$ and $\theta = \theta^{(n+1)}$ is the phase to be applied in the current TPI update period, which is determined as follows. + +Let $\theta^{(n+1)}$ be the currently received TPI phase calculated by the NodeB and signalled to the UE via the F-TPICH bit pattern, and $\theta^{(n)}$ the phase applied in the previous TPI update period. + +Then the final beamforming phase applied $\theta^{(n+1)}$ for the current TPI update period is calculated as: + +$$\text{if } |\varphi_1 - \theta^{(n)}| \leq \pi$$ + +$$\theta^{(n+1)} = \varphi_1$$ + +$$\text{else}$$ + +$$\theta^{(n+1)} = \varphi_2$$ + +where + +$$\varphi_1 = \begin{cases} \theta^{(n+1)} - 2\pi, & \text{if } \theta^{(n)} < 0 \\ \theta^{(n+1)}, & \text{else} \end{cases}$$ + +and + +$$\varphi_2 = \begin{cases} \theta^{(n+1)} - 2\pi, & \text{if } \theta^{(n)} \geq 0 \\ \theta^{(n+1)}, & \text{else} \end{cases}$$ + +The mapping between the F-TPICH bit pattern and the TPI phase $\theta^{(n+1)}$ is given by Table 10. + +**Table 10: Mapping of precoding weight information** + +| $\theta^{(n+1)}$ | Bit pattern | | +|------------------|-------------|-------| +| | $i$ | $i+1$ | +| 0 | 00 | 00 | +| $\pi/2$ | 00 | 11 | +| $\pi$ | 11 | 11 | +| $3\pi/2$ | 11 | 00 | + +![Figure 8: The generic uplink transmitter structure to support UL CLTD activation state 1. The diagram shows a block diagram of the transmitter. On the left, multiple input channels (DPCCH, DPDCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH) are summed and then scrambled. The scrambled signal is split into four parallel paths, each multiplied by a weight (w1, w2, w3, w4). The outputs are then summed and transmitted via two antennas (Ant1, Ant2). Below the diagram, a 'Weight Generation' block is shown, which receives input from 'Determine TPI message from Downlink' and outputs the weights w1, w2, w3, w4.](f5d2a88925807080157c7cfb1d41cf0b_img.jpg) + +The diagram illustrates the generic uplink transmitter structure for UL CLTD activation state 1. It consists of the following components and signal flow: + +- Input Channels:** DPCCH, DPDCH, DPCCH2, E-DPCCH, E-DPDCH, and HS-DPCCH are shown as inputs on the left. +- Summation:** The first six channels (DPCCH through HS-DPCCH) are summed together in a block labeled with the summation symbol $\Sigma$ . +- Scrambling:** The summed signal is then processed by a 'Scramble' block, represented by a circle with an 'X'. +- Weight Generation:** At the bottom, a block labeled 'Determine TPI message from Downlink' feeds into a 'Weight Generation' block. This block outputs four weights: $w_1, w_2, w_3, w_4$ . +- Multiplication:** The scrambled signal is split into four parallel paths. Each path is multiplied by one of the weights: $w_1, w_2, w_3, w_4$ . These multiplications are represented by circles with an 'X'. +- Final Summation:** The outputs of the four multiplication paths are summed in two stages. First, the outputs for $w_1$ and $w_2$ are summed, and the outputs for $w_3$ and $w_4$ are summed. These two intermediate sums are then summed together. +- Antennas:** The final summed signal is transmitted to two antennas, labeled $Ant_1$ and $Ant_2$ . + +Figure 8: The generic uplink transmitter structure to support UL CLTD activation state 1. The diagram shows a block diagram of the transmitter. On the left, multiple input channels (DPCCH, DPDCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH) are summed and then scrambled. The scrambled signal is split into four parallel paths, each multiplied by a weight (w1, w2, w3, w4). The outputs are then summed and transmitted via two antennas (Ant1, Ant2). Below the diagram, a 'Weight Generation' block is shown, which receives input from 'Determine TPI message from Downlink' and outputs the weights w1, w2, w3, w4. + +**Figure 8: The generic uplink transmitter structure to support UL CLTD activation state 1** + +The channel combining for UL CLTD when UL\_CLTD\_Enabled is set to TRUE is described in [3] subclause 4.2.4. When UL\_CLTD\_Active is not equal to 1, no UL closed loop beamforming is performed for uplink transmission. + +In the case that UL\_CLTD\_Active is 2, the DPCCH/DPCCH2/DPDCH/E-DPCCH/E-DPDCH/HS-DPCCH are transmitted on antenna 1, and S-DPCCH is switched off. + +In the case that UL\_CLTD\_Active is 3, the DPCCH/DPCCH2/DPDCH/E-DPCCH/E-DPDCH/HS-DPCCH are transmitted on antenna 2, and S-DPCCH is switched off. + +## 10.2 Downlink TPI transmission and control timing + +If UL\_CLTD\_Enabled is TRUE and UL\_CLTD\_Active is 1, the Node B determines a precoding phase which is signalled to the UE using the allocated TPI field on the F-TPICH as defined in [1]; see also Table 10. The following applies: + +- if the UE is configured with an HS-DPCCH, higher layers indicate to the UE which cells in the active set transmit the F-TPICH, with the restriction that either only the HS-DSCH serving cell transmits the F-TPICH or all cells from the serving radio link set transmit the F-TPICH. +- if the UE is not configured with an HS-DPCCH, higher layers indicate to the UE which cells in the active set transmit the F-TPICH, with the restriction that either only one cell transmits the F-TPICH or all cells from one radio link set transmit the F-TPICH. +- When E-DCH\_decoupling is configured, higher layers indicate to the UE which cells in the active set transmit the F-TPICH, with the restriction that either only the E-DCH serving cell transmits the F-TPICH, or only HS-DSCH serving cell transmits the F-TPICH or all cells from the serving radio link set transmit the F-TPICH. + +The TPI information update rate is 3 slots. However, the uplink channel measurement periods are not specified for Node B. The UE shall apply the precoding weight indicated by the TPI on the first DPCCH slot boundary, after 512 chips after + +- the end of the TPI field carrying the second of the two bits in the TPI bit pattern, if the F-TPICH is configured to be transmitted from one radio link only. +- the end of the last TPI field carrying the second of the two bits in a TPI bit pattern received during a TPI combining period, if the F-TPICH is configured to be transmitted from multiple radio links. + +The UE shall measure the reliability of the received TPI bits over the 3 slot period in which the TPI bit pattern corresponding to a precoding weight is received. The received TPI bits are mapped to precoding weights and applied by the UE only if the estimated quality of the TPI bits is determined to be better than a threshold $Q_{\text{tpi}}$ . Otherwise, the UE shall apply the precoding weights corresponding to the last reliably received TPI bit pattern. $Q_{\text{tpi}}$ is defined implicitly by the relevant tests in [7]. + +## 10.3 Combining TPI bits from multiple radio links + +When a UE is in softer handover and if F-TPICH is configured to be transmitted from multiple radio links as defined in subclause 10.2, the UE may assume that the transmitted TPI bits from those radio links in a TPI combining period are the same. The TPI combining period has the length of one slot, beginning at the downlink slot boundary of the F-TPICH. Upon reception of one or more TPI bits in a TPI combining period, the UE combines all the TPI bits received in that TPI combining period into a single TPI bit. + +## 10.4 Operation during discontinuous uplink DPCCH operation + +When UL\_DTX\_Active is TRUE (see clause 6C), the UE shall not transmit the uplink S-DPCCH in a slot where UE does not transmit uplink DPCCH according to subclause 6C.2. + +The UE shall ignore any TPI commands received in an F-TPICH subframe starting during an uplink DPCCH slot which is in an uplink DPCCH transmission gap as defined in subclause 6C.2. When uplink transmission resumes after a transmission gap, the UE shall apply the precoding weights corresponding to the last applied TPI before the uplink DPCCH transmission gap until a new reliable TPI is received. + +## 10.5 Operation during compressed mode + +### 10.5.1 Uplink compressed mode + +In the case that UL\_CLTD\_Active is 1, the UE shall keep the last applied TPI before an uplink transmission gap until a new reliable TPI is received. + +### 10.5.2 Downlink compressed mode + +The following applies for the UE for reception of F-TPICH, during compressed mode on the DPCH or F-DPCH: + +The UE shall decode F-TPICH transmissions in all slots that do not overlap with a downlink transmission gap. The UE shall ignore the other TPI bit if one of the two slots carrying the TPI bits overlaps a downlink transmission gap. + +## 10.6 HS-SCCH orders + +The Node B may switch uplink CLTD activation state to one of three CLTD activation states through HS-SCCH orders as described in [2]. HS-SCCH ordered transitions between any CLTD activation states are applied at the first E-DCH slot boundary after the end of the HS-DPCCH subframe in which the ACK is sent. The maximum allowed interruption time is 2 slots, ending at the end of the HS-DPCCH subframe in which the ACK is sent. If the UE receives an HS-SCCH order for transitioning to an activation state that is already being applied, then the UE shall not change its activation state, but shall transmit the HARQ-ACK acknowledging the HS-SCCH order. + +When E-DCH\_decoupling is configured, CLTD activation state cannot be changed through HS-SCCH orders. + +## --- 11 Uplink MIMO + +If the UE is configured with UL MIMO, then UL\_MIMO\_Enabled is set to TRUE, otherwise UL\_MIMO\_Enabled is set to FALSE. When UL\_MIMO\_Enabled is set to TRUE, UL\_CLTD\_Enabled is also set to TRUE. UL\_CLTD\_Active can be set to 1, 2 or 3 while UL\_MIMO\_Enabled is TRUE and CLTD activation state can be changed through HS-SCCH orders. The initial state of the UL\_CLTD\_Active follows the definition in clause 10. + +Two separate transport blocks are transmitted via two independent spatial streams when rank-2 transmission is used. The data rates on each stream can be independently adapted. The number of HARQ processes in dual stream operation is double of that in single stream operation, and two E-HICH signature sequences are allocated, providing HARQ-ACK feedback for each stream independently. + +Rank-2 transmissions are only possible when the UL\_CLTD\_Active = 1. + +The pre-coded physical channels structure for UL MIMO rank-2 transmission is depicted in Figure 9. When UL\_MIMO\_Enabled is TRUE either single or dual-stream transmissions can take place. In case of single stream (rank-1) transmission, the transport block is carried over E-DPDCH(s) as in UL CLTD. In case of dual stream (rank-2) transmission, the primary transport block is carried over 4 E-DPDCHs and the secondary transport block is carried over 4 S-E-DPDCHs. S-E-DPCCH is used to indicate the transport block size and retransmission sequence number of the secondary transport block on S-E-DPDCH. S-E-DPCCH is I/Q multiplexed with E-DPCCH and transmitted on primary pre-coding vector. S-E-DPCCH is only sent with rank-2 transmissions. Both the E-DPDCHs and the S-E-DPDCHs are always sent with 2xSF2 + 2xSF4 code combination for rank-2 transmission. The UE can be configured with uplink MIMO only with 2 ms TTI on E-DCH. + +For dual stream transmissions the following applies on setting the relative transmit powers of the uplink physical channels: + +- For the calculation of the E-DPCCH gain factors, E-DPCCH boosting is always applied regardless of the selected E-TFC to be transmitted, +- The S-DPCCH gain factor equals the E-DPCCH gain factor, +- The S-E-DPCCH gain factor is configured by higher layers. + +UL MIMO rank-1 transmission and the setting of the channel transmit powers function as defined for UL CLTD. The pre-coded physical channels structure for UL MIMO rank-1 transmission is depicted in Figure 10. + +![Block diagram of pre-coded physical channel structure for UL MIMO with rank-2 transmission. It shows two groups of channels (DPCCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH, S-E-DPCCH and S-DPCCH, S-E-DPDCH) being summed, scrambled, and then weighted (w1, w2, w3, w4) before being summed again for transmission on Ant1 and Ant2. A 'Determine TPI message from Downlink' block feeds into a 'Weight Generation' block which provides the weights.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The diagram illustrates the pre-coded physical channel structure for UL MIMO with rank-2 transmission. It consists of the following components and signal flow: + +- Input Channels:** DPCCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH, S-E-DPCCH, S-DPCCH, and S-E-DPDCH. +- Summation ( $\Sigma$ ):** The first six channels (DPCCH to S-E-DPCCH) are summed together. The last two channels (S-DPCCH and S-E-DPDCH) are also summed together. +- Scramble:** Both summed signals are then processed by a 'Scramble' block. +- Weighting ( $w_1, w_2, w_3, w_4$ ):** The scrambled signals are then weighted by four weights: $w_1$ , $w_2$ , $w_3$ , and $w_4$ . These weights are generated by a 'Weight Generation' block. +- Final Summation ( $\Sigma$ ):** The weighted signals are then summed again. The first two weighted signals ( $w_1$ and $w_3$ ) are summed for $Ant_1$ , and the other two weighted signals ( $w_2$ and $w_4$ ) are summed for $Ant_2$ . +- Output:** The final summed signals are transmitted on $Ant_1$ and $Ant_2$ . +- Control Logic:** A block labeled 'Determine TPI message from Downlink' feeds into a 'Weight Generation' block, which provides the weights $w_1, w_2, w_3,$ and $w_4$ . + +Block diagram of pre-coded physical channel structure for UL MIMO with rank-2 transmission. It shows two groups of channels (DPCCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH, S-E-DPCCH and S-DPCCH, S-E-DPDCH) being summed, scrambled, and then weighted (w1, w2, w3, w4) before being summed again for transmission on Ant1 and Ant2. A 'Determine TPI message from Downlink' block feeds into a 'Weight Generation' block which provides the weights. + +Figure 9: Pre-coded physical channel structure of UL MIMO with rank-2 transmission + +![Figure 10: Pre-coded physical channel structure of UL MIMO with rank-1 transmission. The diagram shows two groups of input channels being summed, scrambled, and then weighted by pre-coding weights w1, w2, w3, and w4 before being summed again for transmission on two antennas, Ant1 and Ant2. A 'Weight Generation' block at the bottom determines the TPI message from the Downlink to provide the weights.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The diagram illustrates the pre-coding process for UL MIMO with rank-1 transmission. On the left, there are two groups of input channels. The top group includes DPCCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH, and S-E-DPCCH, which are summed together. The bottom group includes S-DPCCH and S-E-DPDCH, which are also summed. Both summed signals are then passed through a 'Scramble' block. The output of the top scramble block is multiplied by pre-coding weights $w_1$ and $w_2$ . The output of the bottom scramble block is multiplied by pre-coding weights $w_3$ and $w_4$ . The weighted signals are then summed again: the signals weighted by $w_1$ and $w_3$ are summed for Antenna 1 (Ant1), and the signals weighted by $w_2$ and $w_4$ are summed for Antenna 2 (Ant2). At the bottom, a 'Determine TPI message from Downlink' block feeds into a 'Weight Generation' block, which outputs the pre-coding weights $w_1, w_2, w_3, w_4$ . + +Figure 10: Pre-coded physical channel structure of UL MIMO with rank-1 transmission. The diagram shows two groups of input channels being summed, scrambled, and then weighted by pre-coding weights w1, w2, w3, and w4 before being summed again for transmission on two antennas, Ant1 and Ant2. A 'Weight Generation' block at the bottom determines the TPI message from the Downlink to provide the weights. + +Figure 10: Pre-coded physical channel structure of UL MIMO with rank-1 transmission + +## 11.1 General procedure + +The UE transmits two orthogonal pilot signals on DPCCH and S-DPCCH. Node B estimates the preferred rank, precoding vector and S-ETFC Offset of the two streams from the received pilot signals. The Node B transmits the preferred precoding vector to the UE in the form of TPI bits using the F-TPICH as in UL CLTD. The UE applies TPI as with UL CLTD. The preferred rank and S-ETFC Offset to be applied by the UE E-TFC selection are signalled to the UE using the E-ROCH channel. + +Rank-1 transmissions occur if the maximum rank signalled over the E-ROCH is 1, or if the UE does not have sufficient data or power headroom to transmit at least the *Minimum E-TFCI for Rank 2 transmission* sized transport blocks on both streams. *Minimum E-TFCI for Rank 2 transmission* is configured by higher layers. + +The signal after spreading is fed to both TX antenna branches and weighted with pre-coding weights $w_1, w_2, w_3$ and $w_4$ . The same pre-coding weights, $w_1$ and $w_2$ are always applied to DPCCH, DPCCH2, E-DPCCH, E-DPDCH, HS-DPCCH and S-E-DPCCH. The S-DPCCH and S-E-DPDCH are pre-coded with pre-coding weights $w_3$ and $w_4$ . + +## 11.2 Downlink TPI transmission and control timing + +When uplink MIMO is configured, downlink TPI transmission and control timing follows that defined for UL CLTD as defined in subclause 10.2. + +## 11.3 Combining TPI bits from radio links of the serving radio link set + +When uplink MIMO is configured, combining TPI bits follows that defined for UL CLTD as defined in subclause 10.3. + +## 11.4 Operation during discontinuous uplink DPCCH operation + +When uplink MIMO is configured, operation during discontinuous uplink DPCCH operation follows that defined for UL CLTD as defined in subclause 10.4. + +## 11.5 Operation during compressed mode + +When uplink MIMO is configured, operation during compressed mode follows that defined for UL CLTD as defined in subclause 10.5. + +## 11.6 HS-SCCH orders + +When uplink MIMO is configured, the HS-SCCH orders as defined for UL CLTD operation in subclause 10.6 apply. + +## 11.7 Uplink power control + +When uplink MIMO is configured, the inner loop power control operates without modifications as defined for non-MIMO operation. + +# --- 12 MIMO operation of HS-DSCH with four transmit antennas + +This section applies only when a UE is configured in MIMO mode with four transmit antennas. + +The general transmitter structure to support MIMO operation of HS-PDSCH transmission with four transmit antennas is shown in Figure 11. For each transport block channel coding, interleaving, spreading and scrambling are done as in non-MIMO mode. Symbol level interleaving between symbols modulated from the primary and the fourth transport blocks is applied. Similarly, symbol level interleaving between symbols modulated from the second and the third transport block. The detailed operation for symbol level interleaving is described in subclause 12.2. The Node B scheduler can decide to transmit one or two or three or four transport blocks to a UE in one TTI in the serving HS-DSCH cell. The spread complex valued signals are fed to all TX antenna branches, and weighted with precoding weights $w_{mn}$ , where $m = 0, 1, 2, 3$ , and $n = 0$ to number of transport blocks decided. The precoding weights $w_{mn}$ is the $m^{\text{th}}$ row and $n^{\text{th}}$ column of the precoding matrix $W_n^{\{s\}}$ defined in Table 14B.7 of [2]. The Node B can dynamically schedule the UE with one or two or three or four transport blocks. + +![A detailed block diagram of a generic downlink transmitter structure for MIMO mode with four transmit antennas. It shows four transport blocks (Primary, Fourth, Second, Third) being processed through TrCH processing, Modulation Mapping, Symbol Interleaving, and Spreading/Scrambling. Each block's output is then multiplied by a set of weights (W) and summed before being transmitted via one of four antennas (Ant1 to Ant4). Pilot signals (P-CPICH, S-CPICH, D-CPICH) are also shown being transmitted. A 'Weight Generation' block at the bottom determines the PCI from the uplink to provide the weights.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The diagram illustrates the downlink transmitter architecture for HS-PDSCH transmission in a MIMO mode with four antennas. The transmitter processes four transport blocks, each following a similar path: + + +- Primary Transport Block (HS-DSCH):** Processed by TrCH processing, then Modulation Mapper to produce $x^{(0)}(i)$ , followed by Symbol Interleaver to produce $y^{(0)}(i)$ , and finally Spreading/Scrambling. The output is multiplied by weights $W_{0,0}, W_{1,0}, W_{2,0}, W_{3,0}$ and summed to form the P-CPICH signal for Ant1. +- Fourth Transport Block (HS-DSCH):** Processed similarly to produce $x^{(3)}(i)$ , $y^{(3)}(i)$ , and then spread/scrambled. The output is multiplied by weights $W_{0,3}, W_{1,3}, W_{2,3}, W_{3,3}$ and summed to form the S-CPICH1 signal for Ant2. +- Second Transport Block (HS-DSCH):** Processed to produce $x^{(1)}(i)$ , $y^{(1)}(i)$ , and then spread/scrambled. The output is multiplied by weights $W_{0,1}, W_{1,1}, W_{2,1}, W_{3,1}$ and summed to form the S-CPICH2 and D-CPICH1 signals for Ant3. +- Third Transport Block (HS-DSCH):** Processed to produce $x^{(2)}(i)$ , $y^{(2)}(i)$ , and then spread/scrambled. The output is multiplied by weights $W_{0,2}, W_{1,2}, W_{2,2}, W_{3,2}$ and summed to form the S-CPICH3 and D-CPICH2 signals for Ant4. + + All four transport blocks share a common Symbol Interleaver and Spreading/Scrambling stage. The weights $W_{i,j}$ are generated by a 'Weight Generation' block which determines the PCI from the uplink. The final signals are summed and transmitted via four antennas (Ant1 to Ant4). + +**Legend:** + +- Primary:** Always present for scheduled UE +- Second:** Optionally present for scheduled UE +- Third:** Optionally present for scheduled UE +- Fourth:** Optionally present for scheduled UE + +A detailed block diagram of a generic downlink transmitter structure for MIMO mode with four transmit antennas. It shows four transport blocks (Primary, Fourth, Second, Third) being processed through TrCH processing, Modulation Mapping, Symbol Interleaving, and Spreading/Scrambling. Each block's output is then multiplied by a set of weights (W) and summed before being transmitted via one of four antennas (Ant1 to Ant4). Pilot signals (P-CPICH, S-CPICH, D-CPICH) are also shown being transmitted. A 'Weight Generation' block at the bottom determines the PCI from the uplink to provide the weights. + +Figure 11: The generic downlink transmitter structure to support MIMO mode with four transmit antennas operation for HS-PDSCH transmission. + +## 12.1 General procedure + +The UE uses the CPICH to separately estimate the channels seen from each antenna. One of the antennas will transmit the Antenna 1 modulation pattern of the P-CPICH as defined in subclause 5.3.3.1 of [1]. The other antennas will transmit the Antenna 1 modulation pattern of a S-CPICH. If D-CPICHs are activated, the Antenna 3 and Antenna 4 will transmit the Antenna 1 modulation pattern of a D-CPICH within TTIs in which the HS-PDSCH is scheduled for a UE configured for MIMO mode with 4 transmit antennas. If D-CPICHs are activated, in addition to P-CPICH and S-CPICHs, the UE uses the D-CPICHs as additional phase references on antenna 3 and antenna 4 to estimate the channels for the HS-PDSCH demodulation. The Pilot configuration in support of MIMO mode with four transmit antennas operation of HS-PDSCH in the cell is signalled by higher layers. + +The UE determines number of transport block preferred a preferred precoding matrix and signals it to the Node B. The signalled information about the number of transport block preferred (NTBP) also called rank information (RI), preferred precoding matrix is termed precoding control indication (PCI) and is defined in subclause 6A.4.2. The PCI is signalled to the Node B together with channel quality indication (CQI) and number of transport block preferred (NTBP) as a composite NTBP/ PCI/CQI report according to the procedure defined in subclause 6A.1.2.3. The UE transmits the composite NTBP/PCI/CQI report to the Node B using the CQI field on the HS-DPCCH as defined in [1]. Based on the composite NTBP/PCI/CQI reports, the Node B scheduler decides whether to schedule one, two, three or four transport blocks in a cell to a UE in one TTI and what transport block size(s) and modulation scheme(s) to use for each of them. + +The Node B signals to the UE the transport blocks scheduled, the precoding weights applied on the HS-PDSCH sub-frame using the precoding weight indication bits of part 1 of the corresponding HS-SCCH sub-frame. The precoding weight adjustment of each HS-PDSCH is done at the HS-PDSCH sub-frame border. For an UE with dual stream capability the Node B should not schedule more than two transport blocks. + +## 12.2 Symbol level interleaving + +Symbol level interleaving is applied between symbols modulated from the second and the third transport block when the Node B schedules three transport blocks. Symbol level interleaving is applied between symbols modulated from the primary and the fourth transport blocks, similarly between symbols modulated from the second and the third transport block when the Node B schedules four transport blocks. Table 11 shows the operation of symbol level interleaving, where $x^{(p)}(i)$ and $y^{(p)}(i)$ , $p = 0, 1, 2$ and 3 are the symbol interleaver input and output symbols respectively. + +**Table 11: Operation of symbol level interleaving** + +| Number of transport blocks | Symbol level interleaving output | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | $y^{(0)}(i) = x^{(0)}(i)$ | +| 2 | $y^{(0)}(i) = x^{(0)}(i)$
$y^{(1)}(i) = x^{(1)}(i)$ | +| 3 | $y^{(0)}(i) = x^{(0)}(i)$
$y^{(1)}(i) = \begin{cases} x^{(1)}(i), & i \text{ is odd} \\ x^{(2)}(i), & i \text{ is even} \end{cases}$
$y^{(2)}(i) = \begin{cases} x^{(2)}(i), & i \text{ is odd} \\ x^{(1)}(i), & i \text{ is even} \end{cases}$ | +| 4 | $y^{(0)}(i) = \begin{cases} x^{(0)}(i), & i \text{ is odd} \\ x^{(3)}(i), & i \text{ is even} \end{cases}$ | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | $y^{(3)}(i) = \begin{cases} x^{(3)}(i), & i \text{ is odd} \\ x^{(0)}(i), & i \text{ is even} \end{cases}$ $y^{(1)}(i) = \begin{cases} x^{(1)}(i), & i \text{ is odd} \\ x^{(2)}(i), & i \text{ is even} \end{cases}$ $y^{(2)}(i) = \begin{cases} x^{(2)}(i), & i \text{ is odd} \\ x^{(1)}(i), & i \text{ is even} \end{cases}$ | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 12.3 Retransmission Procedures + +If the Node B schedules three transport blocks in any transmission, for retransmissions the second transport block and the third transport block are re-transmitted with the same HARQ process identifier as defined in [2]. If the Node B schedules four transport blocks in any transmission, for retransmissions the primary transport block and the fourth transport block are re-transmitted with the same HARQ process identifier as defined in [2], retransmissions the second transport block and the third transport block are re-transmitted with the same HARQ process identifier as defined in [2]. + +- If the Node B schedules two or three transport blocks, the transport block size information of the primary transport block is set to '111111' and if $X_{\text{rvpb}}$ is set to 0, then the primary transport block is not transmitted. +- If the Node B schedules two transport blocks, the transport block size information of the second transport block is set to '111111' and if $X_{\text{rvsb}}$ is set to 0, then the second transport block is not transmitted. +- If the Node B schedules three or four transport blocks, the transport block size information of the second and the third transport block is set to '111111' and if $X_{\text{rvsb}}$ is set to 0, then the second and the third transport block are not transmitted. +- If the Node B schedules four transport blocks, the transport block size information of the primary transport block and fourth transport block is set to '111111' and if $X_{\text{rvpb}}$ is set to 0, then the primary and the fourth transport block are not transmitted. +- When the number of transport blocks is equal to 2 or 3, $X_{\text{rvpb}} = 0$ and if the transport block size information of the primary transport block is equal to '111111' the UE shall discard the received data on the primary transport block, should assume that the primary transport block had been successfully decoded and generate a positive acknowledgement for the primary transport block in this HARQ process. Node B should assume positive acknowledgement has been received for this HARQ process. +- When the number of transport blocks is equal to 2, $X_{\text{rvsb}} = 0$ and if the transport block size information of the second transport block is equal to '111111' the UE shall discard the received data on the second transport block, should assume that the second transport block had been successfully decoded and generate a positive acknowledgement for the second transport block in this HARQ process. Node B should assume positive acknowledgement has been received for this HARQ process. +- When the number of transport blocks is equal to 3 or 4, $X_{\text{rvsb}} = 0$ and if the transport block size information of the second and the third transport block is equal to '111111' the UE shall discard the received data on the second and the third transport blocks, should assume that the second and the third transport blocks had been successfully decoded and generate a positive acknowledgement for the second and the third transport blocks in this HARQ process. Node B should assume positive acknowledgement has been received for this HARQ process. +- When the number of transport blocks is equal to 4, $X_{\text{rvpb}} = 0$ and if the transport block size information of the primary and the fourth transport block is equal to '111111' the UE shall discard the received data on the primary and the fourth transport blocks, should assume that the primary and the fourth transport blocks had been successfully decoded and generate a positive acknowledgement for the primary and the fourth transport blocks in this HARQ process. Node B should assume positive acknowledgement has been received for this HARQ process. + +## 12.4 Precoding weight restriction + +A UE is restricted to report PCI, and NTBP within a precoder codebook subset specified by a bitmap parameter *PrecodingWeightRestriction* configured by higher layer signalling. The bitmap can specify all possible precoder codebook subsets from which the UE can assume the Node B may be using when the UE is configured in MIMO mode with four transmit antennas. The bitmap forms the bit sequence $a_{63}, \dots, a_3, a_2, a_1, a_0$ where $a_0$ is the LSB and $a_{63}$ is the MSB and where a bit value of zero indicates that the precoding indices reporting is not allowed in the NTBP/PCI/CQI report. + +## 12.5 HS-SCCH Orders + +The Node B may activate or deactivate D-CPICH on 3rd and 4th antennas through HS-SCCH orders as described in [2]. The UE may assume that D-CPICHs are present 12 slots after the end of the HS-SCCH subframe containing the order for activation of D-CPICHs. The UE is not required to perform any operations based on the D-CPICHs 12 slots after the end of the HS-SCCH subframe containing the order for deactivation. The HS-SCCH order for activation or deactivation of D-CPICHs is UE-specific. + +The UE can assume the initial activation status of D-CPICH as set by the network through RRC signalling. + +# Annex A (informative): (no title) + +## A.1 Antenna verification + +In closed loop mode 1, if channel estimates are taken from the Primary CPICH, the performance will also suffer if the UE cannot detect errors since the channel estimates will be taken for the incorrect phase settings. To mitigate this problem, antenna verification can be done, which can make use of antenna specific pilot patterns of the dedicated physical channel. The antenna verification can be implemented with several different algorithms. A straightforward algorithm can use a 4-hypothesis test per slot. Alternatively, a simplified beam former verification (SBV) requiring only a 2-hypothesis test per slot can be used. + +Consider + +$$2 \sum_{i=1}^{N_{\text{path}}} \frac{1}{\sigma_i^2} \left\{ \sqrt{2} \operatorname{Re}(\gamma h_{2,i}^{(d)} h_{2,i}^{(p)}) \right\} > \ln \left( \frac{\bar{p}(\varphi_{\text{Rx}}=\pi)}{\bar{p}(\varphi_{\text{Rx}}=0)} \right)$$ + +Then define the variable $x_0$ as 0 if the above inequality holds good and $x_0 = \pi$ otherwise. + +Similarly consider + +$$-2 \sum_{i=1}^{N_{\text{path}}} \frac{1}{\sigma_i^2} \left\{ \sqrt{2} \operatorname{Im}(\gamma h_{2,i}^{(d)} h_{2,i}^{(p)}) \right\} > \ln \left( \frac{\bar{p}(\varphi_{\text{Rx}}=\pi/2)}{\bar{p}(\varphi_{\text{Rx}}=-\pi/2)} \right)$$ + +then define the variable $x_1$ as $-\pi/2$ if the above inequality holds good and $x_1 = \pi/2$ otherwise. + +Whether $x_0$ or $x_1$ is to be calculated for each slot is given by the following table, where the first row contains the UL slot index of the feedback bit to be verified. + +| UL | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|----|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | $x_1$ | $x_0$ | + +The estimate for the transmitted phase is now obtained from + +$$\sin(\varphi_{\text{Tx}}) + j\cos(\varphi_{\text{Tx}}) = \frac{\sum_{i=0}^1 \sin(x_i)}{\sqrt{2}} + j \frac{\sum_{i=0}^1 \cos(x_i)}{\sqrt{2}}$$ + +where: + +- the $x_i$ values are used corresponding to the current slot and the previous slot taking into account the end-of-frame adjustment and the used CL timing adjustment delay +- $h_{2,i}^{(p)}$ is the $i$ 'th estimated channel tap of antenna 2 using the CPICH; +- $h_{2,i}^{(d)}$ is the $i$ 'th estimated channel tap of antenna 2 using the DPCCH; +- $\gamma^2$ is the DPCH Pilot SNIR/ CPICH SNIR; +- $\sigma_i^2$ is the noise plus interference power on the $i$ 'th path. + +In normal operation the *a priori* probability for selected pilot pattern is assumed to be 96% (assuming there are 4% of errors in the feedback channel for power control and antenna selection). + +## A.2 Computation of feedback information for closed loop mode 1 transmit diversity + +In non-soft handover case, the computation of feedback information can be accomplished by e.g. solving for weight vector, $\underline{w}$ , that maximises. + +$$P = \underline{w}^H H^H H \underline{w} \quad (1)$$ + +where + +$$H = [\underline{h}_1 \ \underline{h}_2] \text{ and } \underline{w} = [w_1, w_2]^T$$ + +and where the column vectors $\underline{h}_1$ and $\underline{h}_2$ represent the estimated channel impulse responses for the transmission antennas 1 and 2, of length equal to the length of the channel impulse response. The elements of $\underline{w}$ correspond to the adjustments computed by the UE. + +During soft handover, the antenna weight vector, $\underline{w}$ can be, for example, determined so as to maximise the criteria function: + +$$P = \underline{w}^H (H_1^H H_1 + H_2^H H_2 + \dots) \underline{w} \quad (2)$$ + +where $H_i$ is an estimated channel impulse response for BS#i. In regular SHO, the set of BS#i corresponds to the active set. + +If HS-PDSCH is present, the UE may emphasize the HS-PDSCH serving cell. In this case the antenna weight vector, $\underline{w}$ can be, for example, determined so as to maximise the criteria function: + +$$P = \underline{w}^H (\alpha(H_1^H H_1) + (1-\alpha)(H_2^H H_2 + \dots)) \underline{w}$$ + +where BS#1 is the HS-PDSCH serving cell and coefficient $\alpha$ is less than or equal to 1. For example $\alpha = 0.7$ enhances HS-PDSCH performance while ensuring that there is only a small degradation on the DPCH. + +# Annex B (Informative): Power control + +## B.1 Downlink power control timing + +The power control timing described in this annex should be seen as an example on how the control bits have to be placed in order to permit a short TPC delay. + +In order to maximise the cell radius distance within which one-slot control delay is achieved, the frame timing of an uplink DPCH is delayed by 1024 chips from that of the corresponding downlink DPCH measured at the UE antenna. + +Responding to a downlink TPC command, the UE shall change its uplink DPCH output power at the beginning of the first uplink pilot field after the TPC command reception. Responding to an uplink TPC command, the UTRAN access point shall change its DPCH output power at the beginning of the next downlink pilot field after the reception of the whole TPC command. Note that in soft handover, the TPC command is sent over one slot when DPC\_MODE is 0 and over three slots when DPC\_MODE is 1. Note also that the delay from the uplink TPC command reception to the power change timing is not specified for UTRAN. The UE shall decide and send TPC commands on the uplink based on the downlink SIR measurement. For the DPCH, the TPC command field on the uplink starts, when measured at the UE antenna, 512 chips after the end of the downlink pilot field. The UTRAN access point shall decide and send TPC commands based on the uplink SIR measurement. However, the SIR measurement periods are not specified either for UE nor UTRAN. + +Figure B.1 illustrates an example of transmitter power control timings when a DPCH is configured on the downlink, with a slot format that contains pilot bits. + +![Figure B.1: Transmitter power control timing for DPCH when downlink DPCH slot format contains pilot bits. The diagram shows four horizontal timelines representing signal slots for DL and UL DPCH at UTRAN and UE. The top timeline (DL DPCH at UTRAN) shows a slot of 2560 chips with fields: PILOT, Data1, TPC (T), TF CI, Data2, PILOT, Data1, TPC (T), C. The second timeline (DL DPCH at UE) shows the same slot structure but with a propagation delay and a DL-UL timing offset of 1024 chips. The third timeline (UL DPCH at UE) shows a slot of 2560 chips with fields: PILOT, TF CI, TPC, PILOT. The bottom timeline (UL DPCH at UTRAN) shows the same slot structure but with a propagation delay. Arrows indicate timing relationships: 'DL SIR measurement (*1)' from the UE's DL DPCH to its UL DPCH; 'Response To TPC (*3)' from the UE's DL DPCH to the UTRAN's DL DPCH; 'Response to TPC' from the UE's UL DPCH to the UTRAN's UL DPCH; and 'UL SIR measurement (*2)' from the UTRAN's UL DPCH to its DL DPCH.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +Figure B.1: Transmitter power control timing for DPCH when downlink DPCH slot format contains pilot bits. The diagram shows four horizontal timelines representing signal slots for DL and UL DPCH at UTRAN and UE. The top timeline (DL DPCH at UTRAN) shows a slot of 2560 chips with fields: PILOT, Data1, TPC (T), TF CI, Data2, PILOT, Data1, TPC (T), C. The second timeline (DL DPCH at UE) shows the same slot structure but with a propagation delay and a DL-UL timing offset of 1024 chips. The third timeline (UL DPCH at UE) shows a slot of 2560 chips with fields: PILOT, TF CI, TPC, PILOT. The bottom timeline (UL DPCH at UTRAN) shows the same slot structure but with a propagation delay. Arrows indicate timing relationships: 'DL SIR measurement (\*1)' from the UE's DL DPCH to its UL DPCH; 'Response To TPC (\*3)' from the UE's DL DPCH to the UTRAN's DL DPCH; 'Response to TPC' from the UE's UL DPCH to the UTRAN's UL DPCH; and 'UL SIR measurement (\*2)' from the UTRAN's UL DPCH to its DL DPCH. + +\*1,2 The SIR measurement periods illustrated here are examples. Other ways of measurement are allowed to achieve accurate SIR estimation. + +\*3 If there is not enough time for UTRAN to respond to the TPC, the action can be delayed until the next slot. + +**Figure B.1: Transmitter power control timing for DPCH when downlink DPCH slot format contains pilot bits** + +Figure B.1A illustrates an example of transmitter power control timings when a DPCH is configured on the downlink, with a slot format that does not contain pilot bits. + +![Figure B.1A: Transmitter power control timing for DPCH when downlink DPCH slot format does not contain pilot bits. The diagram shows four horizontal timelines representing radio links: DL DPCCH at UTRAN, DL DPCCH at UE, UL DPCCH at UE, and UL DPCCH at UTRAN. The DL DPCCH at UTRAN and DL DPCCH at UE show slots with TPC and Data1 fields. The UL DPCCH at UE and UL DPCCH at UTRAN show slots with PILOT, TFCI, and TPC fields. Arrows indicate propagation delays, DL-UL timing offsets (1024 chips), DL SIR measurement (*1), UL SIR measurement (*2), and responses to TPC (*3).](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +The diagram illustrates the timing relationships for transmitter power control (TPC) across four radio links: + +- DL DPCCH at UTRAN:** Shows a slot (2560 chips) containing TPC and Data1 fields. +- DL DPCCH at UE:** Shows a slot (2560 chips) containing TPC and Data1 fields. A propagation delay is indicated from the UTRAN TPC to the UE TPC. A DL-UL timing offset (1024 chips) is shown between the UTRAN TPC and the UE TPC. A DL SIR measurement (\*1) is indicated. A response to the TPC is shown. +- UL DPCCH at UE:** Shows a slot (2560 chips) containing PILOT, TFCI, and TPC fields. A propagation delay is indicated from the UE TPC to the UTRAN TPC. A UL SIR measurement (\*2) is indicated. A response to the TPC is shown. +- UL DPCCH at UTRAN:** Shows a slot (2560 chips) containing PILOT, TFCI, and TPC fields. + +Key timing parameters and measurements shown: + +- Slot (2560 chips) +- Propagation delay +- DL-UL timing offset (1024 chips) +- 512 chips +- DL SIR measurement (\*1) +- UL SIR measurement (\*2) +- Response To TPC (\*3) + +Figure B.1A: Transmitter power control timing for DPCH when downlink DPCH slot format does not contain pilot bits. The diagram shows four horizontal timelines representing radio links: DL DPCCH at UTRAN, DL DPCCH at UE, UL DPCCH at UE, and UL DPCCH at UTRAN. The DL DPCCH at UTRAN and DL DPCCH at UE show slots with TPC and Data1 fields. The UL DPCCH at UE and UL DPCCH at UTRAN show slots with PILOT, TFCI, and TPC fields. Arrows indicate propagation delays, DL-UL timing offsets (1024 chips), DL SIR measurement (\*1), UL SIR measurement (\*2), and responses to TPC (\*3). + +\*1,2 The SIR measurement periods illustrated here are examples. Other ways of measurement are allowed to achieve accurate SIR estimation. + +\*3 If there is not enough time for UTRAN to respond to the TPC, the action can be delayed until the next slot. + +**Figure B.1A: Transmitter power control timing for DPCH when downlink DPCH slot format does not contain pilot bits** + +Figure B.2 illustrates an example of transmitter power control timings when the F-DPCH is configured on the downlink and the F-DPCH TPC offset $N_{OFF1}$ of all the radio links in the RLS is 0 or 2 (see Table 16C of [1]). Figure B.2a illustrates an example of transmitter power control timings for the radio link whose F-DPCH TPC offset $N_{OFF1} = 0$ or 2, when the F-DPCH is configured on the downlink, and the F-DPCH TPC offset $N_{OFF1}$ of at least one other radio link in the RLS is $> 2$ . Figure B.3 illustrates an example of transmitter power control timings when the F-DPCH is configured on the downlink and the F-DPCH TPC offset $N_{OFF1}$ of the radio link is larger than 2. Figure B.4 illustrates an example of transmitter power control timings when the F-DPCH is configured on the downlink and the F-DPCH TPC offset $N_{OFF1}$ of the radio link is larger than 14 when uplink DPCH slot format #4 is used. + +![Timing diagram Figure B.2 showing DL F-DPCH and UL DPCCH timing relationships between UTRAN and UE. It details slot structures, propagation delays, and TPC response timing for N_OFF1 values of 0 or 2.](5801c19431e76330430e92a598cc7a16_img.jpg) + +The diagram shows the timing relationship between Downlink (DL) and Uplink (UL) channels for power control. Key elements include: + +- DL F-DPCH at UTRAN:** Shows slots of 2560 chips starting at $\tau_0$ , with TPC fields (T, P, C). +- DL F-DPCH at UE:** Delayed by propagation delay $\tau_p$ . Shows DL-UL timing offset (1024 chips) and TPC offset $N_{OFF1}$ . A DL SIR measurement is taken, leading to a TPC response. +- UL DPCCH at UE:** Contains PILOT, TFCI, and TPC fields. The TPC response is sent in the UL TPC field. +- UL DPCCH at UTRAN:** Received after another propagation delay. An UL SIR measurement is performed here. + +A timing constraint of "512 chips or more" is indicated between the end of the DL TPC field and the start of the UL TPC field. + +Timing diagram Figure B.2 showing DL F-DPCH and UL DPCCH timing relationships between UTRAN and UE. It details slot structures, propagation delays, and TPC response timing for N\_OFF1 values of 0 or 2. + +Figure B.2: Transmitter power control timing for F-DPCH with TPC offsets $N_{OFF1}$ of 0 or 2 when F-DPCH TPC offset $N_{OFF1}$ of all the radio links in the RLS is 0 or 2 + +![Timing diagram Figure B.2a, similar to B.2 but showing different measurement and response timing when at least one radio link has N_OFF1 > 2.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +This diagram illustrates a variation of the power control timing. While the channel structures (DL F-DPCH and UL DPCCH) remain the same as in Figure B.2, the timing of the DL SIR measurement and the TPC response is different. In this case, the DL SIR measurement spans a different portion of the DL slot, and the response to the TPC command is mapped to a later UL TPC field, reflecting the condition where at least one radio link in the RLS has a larger TPC offset. + +Timing diagram Figure B.2a, similar to B.2 but showing different measurement and response timing when at least one radio link has N\_OFF1 > 2. + +Figure B.2a: Transmitter power control timing for F-DPCH with TPC offsets $N_{OFF1}$ of 0 or 2 when the F-DPCH TPC offset $N_{OFF1}$ of at least one other radio link in the RLS is $> 2$ + +![Timing diagram for F-DPCH transmitter power control with TPC offset N_OFF1 > 2. It shows four horizontal timelines: DL F-DPCH at UTRAN, DL F-DPCH at UE, UL DPCCH at UE, and UL DPCCH at UTRAN. The DL F-DPCH at UTRAN has TPC fields every 2560 chips. The DL F-DPCH at UE shows a propagation delay \tau_p and a DL-UL timing offset of 1024 chips. The UL DPCCH at UE has slots with PILOT, TFCI, and TPC fields. The UL DPCCH at UTRAN shows a propagation delay and a UL SIR measurement. Arrows indicate 'Response To TPC' from the UE's UL DPCCH to the UTRAN's DL F-DPCH and from the UTRAN's UL DPCCH to the UE's DL F-DPCH.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +Timing diagram for F-DPCH transmitter power control with TPC offset N\_OFF1 > 2. It shows four horizontal timelines: DL F-DPCH at UTRAN, DL F-DPCH at UE, UL DPCCH at UE, and UL DPCCH at UTRAN. The DL F-DPCH at UTRAN has TPC fields every 2560 chips. The DL F-DPCH at UE shows a propagation delay $\tau_p$ and a DL-UL timing offset of 1024 chips. The UL DPCCH at UE has slots with PILOT, TFCI, and TPC fields. The UL DPCCH at UTRAN shows a propagation delay and a UL SIR measurement. Arrows indicate 'Response To TPC' from the UE's UL DPCCH to the UTRAN's DL F-DPCH and from the UTRAN's UL DPCCH to the UE's DL F-DPCH. + +Figure B.3: Transmitter power control timing for F-DPCH with a TPC offset $N_{OFF1}$ larger than 2 + +![Timing diagram for F-DPCH transmitter power control with TPC offset N_OFF1 > 14 and uplink DPCCH slot format #4. It follows the same four-timeline structure as Figure B.3. The main difference is in the UL DPCCH slot format at the UE and UTRAN, which now consists of alternating PILOT and TPC fields without TFCI. The timing relationships, propagation delays, and response arrows remain consistent with the previous figure.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +Timing diagram for F-DPCH transmitter power control with TPC offset N\_OFF1 > 14 and uplink DPCCH slot format #4. It follows the same four-timeline structure as Figure B.3. The main difference is in the UL DPCCH slot format at the UE and UTRAN, which now consists of alternating PILOT and TPC fields without TFCI. The timing relationships, propagation delays, and response arrows remain consistent with the previous figure. + +Figure B.4: Transmitter power control timing for F-DPCH with a TPC offset $N_{OFF1}$ larger than 14 with uplink DPCCH slot format #4 + +## --- B.2 Example of implementation in the UE + +The downlink inner-loop power control adjusts the network transmit power in order to keep the received downlink SIR at a given SIR target, $SIR_{target}$ . A higher layer outer loop adjusts $SIR_{target}$ independently for each connection. + +The UE should estimate the received downlink DPCCH/DPDCH power of the connection to be power controlled. Simultaneously, the UE should estimate the received interference and calculate the signal-to-interference ratio, $SIR_{est}$ . $SIR_{est}$ can be calculated as RSCP/ISCP, where RSCP refers to the received signal code power on one code and ISCP refers to the non-orthogonal interference signal code power of the received signal on one code. Note that due to the specific SIR target offsets described in [5] that can be applied during compressed frames, the spreading factor shall not be considered in the calculation of $SIR_{est}$ . + +The obtained SIR estimate $SIR_{est}$ is then used by the UE to generate TPC commands according to the following rule: if $SIR_{est} > SIR_{target}$ then the TPC command to transmit is "0", requesting a transmit power decrease, while if $SIR_{est} < SIR_{target}$ then the TPC command to transmit is "1", requesting a transmit power increase. + +When the UE is in soft handover, the UE should estimate $SIR_{est}$ from the downlink signals of all cells in the active set. + +## --- B.3 UL power control when losing UL synchronization + +Each Node B operates the uplink power control independently of the other Node Bs that may be providing RLS to the same UE. In case of multiple RLS the UE derives the decision on power adjustment based on all the commands received according the rules specified in subclause 5.1.2. In this scenario, transmission of a down command by one or more of the involved Node Bs will likely result in the UE decreasing its transmit power. + +Consequently, if and when, after successful initial RL synchronization, the Node B loses UL synchronization for a UE and if the current number of RLS configured for that UE is greater than one and if the Node B reverts to a TPC pattern in such situation (i.e. generates DL TPC commands independently of actual RL measurements), the Node B should not use TPC commands "0" in the TPC pattern. + +# --- Annex C (Informative):Cell search procedure + +During the cell search, the UE searches for a cell and determines the downlink scrambling code and frame synchronization of that cell. The cell search is typically carried out in three steps: + +## Step 1: Slot synchronization + +During the first step of the cell search procedure the UE uses the SCH's primary synchronization code to acquire slot synchronization to a cell. This is typically done with a single matched filter (or any similar device) matched to the primary synchronization code which is common to all cells. The slot timing of the cell can be obtained by detecting peaks in the matched filter output. + +## Step 2: Frame synchronization and code-group identification + +During the second step of the cell search procedure, the UE uses the SCH's secondary synchronization code to find frame synchronization and identify the code group of the cell found in the first step. This is done by correlating the received signal with all possible secondary synchronization code sequences, and identifying the maximum correlation value. Since the cyclic shifts of the sequences are unique the code group as well as the frame synchronization is determined. + +## Step 3: Scrambling-code identification + +During the third and last step of the cell search procedure, the UE determines the exact primary scrambling code used by the found cell. The primary scrambling code is typically identified through symbol-by-symbol correlation over the CPICH with all codes within the code group identified in the second step. After the primary scrambling code has been identified, the Primary CCPCH can be detected. And the system- and cell specific BCH information can be read. + +If the UE has received information about which scrambling codes to search for, steps 2 and 3 above can be simplified. + +# Annex D (Informative): F-TPICH Transmission + +The F-TPICH transmission timing described in this annex should be seen as an example on how the TPI bits have to be placed in order to ensure a short TPI delay. + +In response to the reception of the TPI bits on the F-TPICH channel, the UE shall apply the precoding weights indicated by the TPI bits at the first UL DPCCH slot that is transmitted at least 512 chips after the reception of the last of the two TPI symbols. The reliability of the received TPI bit is determined by the UE based on the downlink SIR measurement on the F-TPICH channel. + +Figure D.1 illustrates an example of F-TPICH timing for UL CLTD operation when the F-TPICH frame starts 512 chips after the start of the DPCH/F-DPCH frame. + +![Figure D.1: F-TPICH Transmission timing for UL CLTD when F-TPICH frame starts 512 chips after the start of DPCH/F-DPCH frame. The diagram shows the timing relationship between DL F-TPICH, DL F-DPCH, and UL DPCCH channels at the UTRAN and UE. It illustrates the propagation delays, slot durations (2560 chips), and the application of TPI bits.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +The diagram illustrates the timing for F-TPICH transmission in UL CLTD. It consists of five horizontal timelines representing different channels and locations: + +- DL F-TPICH at UTRAN:** Shows a frame starting at $\tau_0$ . The first slot (2560 chips) contains two TPI symbols, $T_P$ , separated by 512 chips. The second slot also contains two $T_P$ symbols. +- DL F-TPICH at UE:** Shows the reception of the TPI symbols with a propagation delay $N_{OFF1}$ from the UTRAN. +- DL F-DPCH at UTRAN:** Shows a frame starting at $\tau_0$ . The first slot (2560 chips) contains two TPC symbols, $T_P$ , separated by 512 chips. The second slot also contains two $T_P$ symbols. +- DL F-DPCH at UE:** Shows the reception of the TPC symbols with a propagation delay $\tau_p$ from the UTRAN. +- UL DPCCH at UE:** Shows a frame structure with slots of 2560 chips. Each slot contains PILOT, TFCI, and TPC fields. The application of TPI bits is indicated by an arrow pointing to the first slot that is transmitted at least 512 chips after the reception of the last TPI symbol from the DL F-TPICH at UE. +- UL DPCCH at UTRAN:** Shows the reception of the UL DPCCH frame with a propagation delay from the UE. A 'UL channel measurement' is indicated at the start of the frame. + +Key timing parameters shown include: + +- $\tau_0$ : Start of the DL F-TPICH and DL F-DPCH frames at the UTRAN. +- 512 chips: Time interval between TPI symbols in the DL F-TPICH frame. +- Slot (2560 chips): Duration of one slot in the DL F-TPICH and DL F-DPCH frames. +- $N_{OFF1}$ : Propagation delay for the DL F-TPICH channel. +- $\tau_p$ : Propagation delay for the DL F-DPCH channel. +- DL-UL timing offset (1024 chips): Time offset between the start of the DL F-DPCH frame at the UE and the start of the UL DPCCH frame at the UE. +- 512 chips or more: Time interval from the reception of the last TPI symbol to the application of TPI bits in the UL DPCCH frame. + +Figure D.1: F-TPICH Transmission timing for UL CLTD when F-TPICH frame starts 512 chips after the start of DPCH/F-DPCH frame. The diagram shows the timing relationship between DL F-TPICH, DL F-DPCH, and UL DPCCH channels at the UTRAN and UE. It illustrates the propagation delays, slot durations (2560 chips), and the application of TPI bits. + +**Figure D.1: F-TPICH Transmission timing for UL CLTD when F-TPICH frame starts 512 chips after the start of DPCH/F-DPCH frame** + +# --- Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | RP 05 | RP-99531 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RP_06 | RP-99686 | 003 | 2 | Flexible timing of UTRAN response to uplink closed loop Tx diversity feedback commands | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 006 | 2 | CPCH power control preamble length | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 007 | - | Removal of open loop power control | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 008 | - | Power offset of AICH and PICH | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 009 | 1 | Update of Random Access Procedure | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 010 | 1 | oft symbol combining for uplink power control | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99685 | 011 | - | Clarification of closed loop transmit diversity figure in clause 8 and closed loop operation in compressed mode for mode 2 in subclause 8.3 of TS 25.214 | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 012 | - | Uplink power control maximum TX power | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99686 | 013 | 1 | Setting of beta values for multi-code | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 014 | - | Consolidation of CPCH Power Control Preamble Information | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 015 | 1 | Consolidation of Power Control Information for DCH Initialisation | 3.0.0 | 3.1.0 | +| 14/01/00 | RP_06 | RP-99686 | 016 | - | Uplink power control in compressed mode | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 018 | 1 | Timing for initialisation procedures | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 021 | - | 20 ms RACH message length | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99684 | 023 | 1 | Maximum Tx Power at uplink compressed Mode | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 024 | 2 | Setting of power in uplink compressed mode | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 025 | - | Cleanup of synchronization procedures | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 026 | 2 | Downlink power control | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 029 | - | Out-of-synch handling | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 030 | 2 | State update rule addition to SSDT specification | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 033 | - | Uplink TX timing adjustment | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 036 | - | Inclusion of idle periods for the IPDL LCS | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99686 | 041 | - | Revision of power control timing text | 3.0.0 | 3.1.0 | +| 14/01/00 | RP 06 | RP-99687 | 042 | 1 | Inclusion of adjustment loop in downlink power control | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RP 07 | RP-000064 | 043 | 1 | Optimum ID Codes for SSDT Power Control | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 044 | - | Editorial clarification to subclause 5.1.2.2.2 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 047 | 1 | Additional description of TX diversity for PDSCH | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 048 | - | Power offset on S-CCPCH | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 050 | 2 | Corrections to uplink power control | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 055 | - | Correction of Adjustment loop description | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 056 | 1 | Clarification of TPC command combining for Algorithm 1 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 057 | - | Clarification of TPC command combining for Algorithm 2 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 059 | 2 | CPCH:CD subslot-related additions to 6.2 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 061 | 1 | CPCH: editorial changes and clarifications of 6.2 | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 062 | - | Editorial corrections | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 064 | 1 | Editorial improvement of the IPDL section | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 065 | 1 | PRACH power offset definition | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 066 | 1 | Radio link synchronization in UTRA/FDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 068 | - | Definition for maximum and minimum DL power | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000064 | 069 | 4 | Channel assignment and UE channel selection methods of CPCH | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 071 | - | Channelization code allocation method for PCPCH message part | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 072 | 1 | Limited power raise used -parameter in DL PC | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 080 | - | Downlink power control | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000064 | 081 | - | Editorial improvement on SSDT power control section | 3.1.1 | 3.2.0 | +| 31/03/00 | RP_07 | RP-000065 | 082 | 2 | Emergency Stop of CPCH transmission and Start of Message Indicator | 3.1.1 | 3.2.0 | +| 31/03/00 | RP 07 | RP-000065 | 083 | - | Clean up of USTS related specifications | 3.1.1 | 3.2.0 | +| 26/06/00 | RP 08 | RP-000268 | 084 | - | Addition of CSICH power parameter | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 085 | - | Correction to power control in compressed mode recovery period | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000268 | 086 | 1 | Revisions to power control for CPCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 087 | - | Corrections to uplink DCH power control sections | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 090 | 3 | Level of specification of downlink power control | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 091 | 1 | Clarification of TX diversity power setting | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 092 | - | PICH undefined bits | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 095 | 1 | DPDCH/DPCCH gain factors | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 096 | 3 | Correction to RACH subchannel definition | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 097 | 1 | The power setting of the CCC field of DL DPCCH for CPCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 098 | 4 | Procedure for end of transmission indicator in CPCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 099 | - | Downlink inner-loop power control in compressed mode | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 100 | - | Definition of vector transmission weight entity | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 101 | 1 | Number of slots for DPCCH power control preamble | 3.2.0 | 3.3.0 | +| 26/06/00 | RP_08 | RP-000268 | 102 | - | Clarification of UTRAN Tx diversity response timing description in 25.214 | 3.2.0 | 3.3.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 26/06/00 | RP 08 | RP-000268 | 103 | 2 | Corrections to transmit diversity section | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 104 | 1 | Corrections to uplink power control in compressed mode | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 105 | - | Clarification of downlink power control mode | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 106 | - | Clarification of radio link set | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000268 | 107 | 1 | Clarification of radio link synchronization procedure | 3.2.0 | 3.3.0 | +| 26/06/00 | RP 08 | RP-000269 | 108 | - | Correctly quantized gain factors for uplink compressed mode | 3.2.0 | 3.3.0 | +| 23/09/00 | RP 09 | RP-000342 | 110 | 4 | Downlink inner-loop power control in compressed mode | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 112 | - | Adding reference for power offset variation text in TS 25.214 | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 113 | - | Combining TPC commands in soft handover | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 115 | 1 | Corrections to power control | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 116 | - | Corrections to 25.214 | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 117 | - | Clarification to downlink power control | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 118 | 3 | Clarification of power control at maximum and minimum power | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 119 | - | Clarification of SSDT text | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 120 | - | Corrections to CL transmit diversity mode 1 | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 121 | 1 | Clarification of SSDT ID code bit transmission order | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 122 | 1 | Clarification on RACH and CPCH subchannel definition | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 123 | 1 | DPCH initialisation procedure | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 124 | - | Clarification of closed loop mode TX diversity initialisation | 3.3.0 | 3.4.0 | +| 23/09/00 | RP 09 | RP-000342 | 127 | 2 | Uplink power control in compressed mode | 3.3.0 | 3.4.0 | +| 15/12/00 | RP 10 | RP-000540 | 128 | 1 | Clarification of downlink quality measurement in SSDT | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 129 | - | Formula typography and reference corrections | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 130 | 1 | Radio link establishment and sync status reporting | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 133 | - | Correction of RACH/CPCH physical random access procedure | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 134 | - | Correction of uplink power control algorithm 2 | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 135 | 1 | TPC command generation on downlink during RLS initialization | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 136 | 1 | Clarification of RACH behavior at maximum and minimum power | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 137 | - | Clarifications on the description of the radio link establishment procedure (when no radio link exists) | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 138 | 1 | Corrections on power control preambles | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 139 | 1 | Clarification of RACH procedure | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 140 | - | Uplink power control in compressed mode | 3.4.0 | 3.5.0 | +| 15/12/00 | RP 10 | RP-000540 | 141 | 1 | Revision of the abbreviation list | 3.4.0 | 3.5.0 | +| 16/03/01 | RP 11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 142 | 1 | Uplink power control in compressed mode | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 144 | - | Removal of the power balancing algorithm from TS 25.214 | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010254 | 145 | 2 | Clarification of Nid parameter – when SSDT and uplink compressed mode are in operation | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 146 | - | Clarification of closed loop transmit diversity mode 1 and mode 2 operation during compressed mode | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 148 | 1 | Clarification of UE SIR estimation | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 150 | 1 | Clarification of the order of SSDT signalling in 2 bit FBI | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010244 | 154 | 2 | Uplink power control preamble | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 155 | - | Correction of limited power raise | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 156 | - | Clarification of initialization procedure | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 158 | - | Definition of power control step size for algorithm 2 | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 161 | 1 | Correction of the UE behavior in SSDT mode | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010060 | 163 | - | Correction on downlink synchronization primitives | 3.5.0 | 4.0.0 | +| 16/03/01 | RP 11 | RP-010074 | 149 | 1 | DSCH Power Control Improvement in soft handover | 3.5.0 | 4.0.0 | +| 15/06/01 | RP 12 | RP-010334 | 166 | 1 | Limited power raise: aligning of terminology with TS25.433 | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010334 | 167 | 1 | Correction of IPDL burst parameters | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010334 | 169 | 1 | Correction of synchronization primitives | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010334 | 177 | 1 | Clarification on TPC command generation on downlink during RL initialisation | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010482 | 181 | 4 | Clarification of synchronization procedures | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010334 | 183 | - | Clarification of initialisation of closed loop mode 1 and 2 during compressed mode | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010334 | 186 | - | DL maximum power level in compressed mode | 4.0.0 | 4.1.0 | +| 15/06/01 | RP 12 | RP-010341 | 164 | 1 | Clarification on the usage of SSDT signaling in uplink | 4.0.0 | 4.1.0 | +| 21/09/01 | RP 13 | RP-010520 | 192 | - | Corrections and Clarifications for calculation of idle period position in subclause 8.3 in 25.214 | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010520 | 194 | 1 | Minor modifications to the CPCH access procedure | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010520 | 197 | - | Downlink power control in compressed mode | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010520 | 199 | 1 | Improvements of closed loop TX diversity description | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010520 | 201 | 1 | Correction to Random access procedure (Primitive from MAC) | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010677 | 205 | 1 | Proposed CR to TS25.214: Clarification of the SSDT behaviour with beam forming | 4.1.0 | 4.2.0 | +| 21/09/01 | RP 13 | RP-010527 | 195 | 1 | Enhanced PDSCH power control clarification | 4.1.0 | 4.2.0 | +| 14/12/01 | RP 14 | RP-010739 | 207 | 1 | Power control in compressed mode when DPC_MODE=1 | 4.2.0 | 4.3.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/12/01 | RP_14 | RP-010739 | 209 | - | Clarification of closed loop mode 1 and 2 Tx diversity operation during compressed mode | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010739 | 211 | - | Downlink phase reference reconfiguration | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010739 | 219 | 1 | Downlink power control for channels supporting CPCH | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010739 | 223 | - | Removal of slow power control from TS 25.214 | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010775 | 216 | - | Uplink TPC command processing in SHO with SSDT | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010744 | 217 | 2 | DSCH power control clarification | 4.2.0 | 4.3.0 | +| 14/12/01 | RP_14 | RP-010933 | 229 | - | Restriction to SSDT and closed loop mode transmit diversity combination | 4.2.0 | 4.3.0 | +| 08/03/02 | RP_15 | RP-020047 | 227 | - | Clarification on DPCCH dedicated pilot bits with closed loop mode1 | 4.3.0 | 4.4.0 | +| 08/03/02 | RP_15 | RP-020261 | 231 | 3 | Qth threshold parameter in SSDT | 4.3.0 | 4.4.0 | +| 08/03/02 | RP_15 | RP-020047 | 240 | 1 | TPC procedure in UE when SSDT is activated | 4.3.0 | 4.4.0 | +| 08/03/02 | RP_15 | RP-020053 | 236 | 1 | Clarification of closed loop transmit diversity during soft handover | 4.3.0 | 4.4.0 | +| 08/03/02 | RP_15 | RP-020054 | 250 | 1 | Description of SSDT operation for TFCI power control in hard split mode | 4.3.0 | 5.0.0 | +| 08/03/02 | RP_15 | RP-020058 | 237 | 2 | Introduction of HSDPA feature to TS25.214 | 4.3.0 | 5.0.0 | +| 08/03/02 | RP_15 | RP-020058 | 251 | - | Introduction of power control aspects for HSDPA feature in TS25.214 | 4.3.0 | 5.0.0 | +| 07/06/02 | RP_16 | RP-020316 | 255 | 2 | Correction on the operation of HSDPA during compressed mode | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 259 | 1 | Clarification of UE transmission timing adjustment with HS-DPCCH | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 260 | 4 | Definition of CQI reporting | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 266 | - | Correction to the setting of DPCCH/HS-DPCCH power difference | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020316 | 267 | - | Inclusion of CQI table | 5.0.0 | 5.1.0 | +| 07/06/02 | RP_16 | RP-020318 | 265 | 1 | Definition of Qth threshold parameter in SSDT | 5.0.0 | 5.1.0 | +| 17/09/02 | RP_17 | RP-020584 | 263 | - | Clarification of total HS-SCCH/HS-PDSCH power | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020571 | 272 | - | Reversal of unwanted corrections resulting from CR 25.211-122 & CR 25.214-226 | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 273 | 2 | Clarification of total HS-PDSCH power in CQI reporting procedure | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 274 | 1 | Closed loop transmit diversity mode 2 with antenna verification | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020589 | 279 | - | Correction of maximum power adjustment in case of compressed mode | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020574 | 282 | 1 | Enhanced DSCH power control parameter name change | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 287 | 2 | Correction of CQI definition | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020587 | 288 | - | Inclusion of closed loop transmit diversity for HSDPA | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020588 | 289 | - | Correction of timing of CQI reporting | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020529 | 294 | - | Correction of reference linked to approval of CR 25.133-471 | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 296 | - | The clarification of CQI feedback parameter k value | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 298 | - | Clarification of CQI definition and reference period | 5.1.0 | 5.2.0 | +| 17/09/02 | RP_17 | RP-020584 | 286 | 1 | Numbering corrections | 5.1.0 | 5.2.0 | +| 20/12/02 | RP_18 | RP-020847 | 300 | 1 | Corrections and clarifications to FDD CQI description | 5.2.0 | 5.3.0 | +| 20/12/02 | RP_18 | RP-020847 | 301 | 1 | Criterion to determine primary cell for DSCH power control improvement | 5.2.0 | 5.3.0 | +| 20/12/02 | RP_18 | RP-020851 | 304 | 2 | Introduction of Transport Block Size signaling procedure reference. | 5.2.0 | 5.3.0 | +| 20/12/02 | RP_18 | RP-020841 | 307 | - | Clarification of closed loop timing adjustment mode | 5.2.0 | 5.3.0 | +| 26/03/03 | RP_19 | RP-030136 | 299 | 5 | CQI reporting with TxD | 5.3.0 | 5.4.0 | +| 26/03/03 | RP_19 | RP-030136 | 313 | 1 | On closed loop transmit diversity mode 1 verification algorithm | 5.3.0 | 5.4.0 | +| 26/03/03 | RP_19 | RP-030136 | 315 | 2 | Clarification of SSDT and HSDPA | 5.3.0 | 5.4.0 | +| 26/03/03 | RP_19 | RP-030132 | 318 | - | Correction on verification algorithm in Annex 1 | 5.3.0 | 5.4.0 | +| 23/06/03 | RP_20 | RP-030273 | 314 | 1 | Correction of TPC command combining in SHO | 5.4.0 | 5.5.0 | +| 23/06/03 | RP_20 | RP-030273 | 319 | - | Correction for HS-DPCCH gain factor in compressed frame | 5.4.0 | 5.5.0 | +| 23/06/03 | RP_20 | RP-030273 | 320 | 1 | Clarification of HS-SCCH reception in case of minimum interTTI interval is not 1 | 5.4.0 | 5.5.0 | +| 23/06/03 | RP_20 | RP-030273 | 321 | - | Correction of description of CQI transmission timing calculation | 5.4.0 | 5.5.0 | +| 23/06/03 | RP_20 | RP-030273 | 322 | 1 | Clarification of the reference power for HS-DPCCH | 5.4.0 | 5.5.0 | +| 21/09/03 | RP_21 | RP-030458 | 325 | - | Correction of CQI definition table | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030462 | 326 | - | Removal of the combination of TxAA Mode 1 with HS-SCCH | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030458 | 328 | 2 | Clarification of power scaling with HS-DPCCH | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030458 | 329 | 3 | Correction of CQI reporting in DL compressed mode | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030458 | 330 | 1 | Clarification of HS-SCCH reception | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030458 | 333 | 1 | Clarification on CQI repetition behaviour | 5.5.0 | 5.6.0 | +| 21/09/03 | RP_21 | RP-030547 | 335 | 3 | TPC pattern during loss of RL synchronization | 5.5.0 | 5.6.0 | +| 06/01/04 | RP_22 | RP-030649 | 335 | 1 | Clarification of HS-SCCH reception | 5.6.0 | 5.7.0 | +| 06/01/04 | RP_22 | RP-030649 | 336 | 1 | Clarification of CQI definition | 5.6.0 | 5.7.0 | +| 06/01/04 | RP_22 | RP-030649 | 337 | 1 | Clarification of the HS-SCCH detection | 5.6.0 | 5.7.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 06/01/04 | RP_22 | RP-030661 | 338 | - | Remove inconsistency among specifications on signalling support for power control during loss of RL synchronization | 5.6.0 | 5.7.0 | +| 06/01/04 | RP 22 | RP-030712 | 339 | - | Alignment of "Soft channel bits" terminology with 25.306 | 5.6.0 | 5.7.0 | +| 13/01/04 | RP 22 | - | - | - | Created for M.1457 update | 5.7.0 | 6.0.0 | +| 23/03/04 | RP 23 | RP-040086 | 341 | - | Beta values for HS-DPCCH in compressed mode | 6.0.0 | 6.1.0 | +| 23/03/04 | RP 23 | RP-040086 | 346 | 1 | ACK/NACK repetition factor | 6.0.0 | 6.1.0 | +| 09/06/04 | RP 24 | RP-040257 | 350 | 3 | Clarification of UE procedure in case of HHO failure | 6.1.0 | 6.2.0 | +| 28/09/04 | RP 25 | RP-040318 | 352 | 1 | Clarification of SSDT uplink only signalling | 6.2.0 | 6.3.0 | +| 13/12/04 | RP 26 | RP-040449 | 361 | 1 | Introduction of E-DCH | 6.3.0 | 6.4.0 | +| 13/12/04 | RP 26 | RP-040450 | 351 | - | Introduction of MICH | 6.3.0 | 6.4.0 | +| 13/12/04 | RP 26 | RP-040448 | 356 | 1 | Introduction of MBMS Soft Combining | 6.3.0 | 6.4.0 | +| 13/12/04 | RP_26 | RP-040447 | 360 | - | Correction of downlink transmit power control in compressed mode | 6.3.0 | 6.4.0 | +| 13/12/04 | RP 26 | RP-040527 | 358 | 1 | Preamble and Postamble to reduce HS-DPCCH transmit power | 6.3.0 | 6.4.0 | +| 14/03/05 | RP 27 | RP-050048 | 362 | 2 | Gain factor setting for E-DCH | 6.4.0 | 6.5.0 | +| 14/03/05 | RP 27 | RP-050049 | 364 | 1 | Reliable E-RGCH/E-HICH Detection | 6.4.0 | 6.5.0 | +| 14/03/05 | RP 27 | RP-050088 | 368 | 1 | Introduction of F-DPCH without pilot field | 6.4.0 | 6.5.0 | +| 14/03/05 | RP 27 | RP-050140 | 369 | 3 | DL/UL timing association of E-DCH operation | 6.4.0 | 6.5.0 | +| 16/06/05 | RP 28 | RP-050254 | 354 | 4 | Timing Maintained Hard Handover | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050253 | 355 | 4 | Faster L1 DCH synchronization | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 363 | 4 | Power control at the maximum power limit | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 372 | 4 | Support of different HARQ profiles | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 373 | - | Lowest reference E-TFC for the gain factor setting for E-DCH | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050250 | 375 | 1 | Feature Clean Up: Removal of "CPCH" | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050248 | 377 | 1 | Feature Clean Up: Removal of DSCH (FDD mode) | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050333 | 378 | 1 | F-DPCH Downlink Power Control Behaviour in SHO | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050256 | 379 | - | Correction to DL synchronization | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 380 | 3 | Clarification on E-DCH timing | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 381 | 1 | DPCCH gain factor with no DPDCH configured | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050252 | 382 | 2 | Compressed mode operation for the Enhanced Uplink | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050244 | 384 | - | Feature Clean Up: Removal of "SSDT" | 6.5.0 | 6.6.0 | +| 16/06/05 | RP_28 | RP-050247 | 387 | 1 | Feature clean up: Removal of the 'TX diversity closed loop mode 2' | 6.5.0 | 6.6.0 | +| 16/06/05 | RP_28 | RP-050249 | 389 | 1 | Feature clean up: Removal of the 'compressed mode by puncturing' | 6.5.0 | 6.6.0 | +| 16/06/05 | RP_28 | RP-050246 | 391 | 1 | Feature Clean Up: Removal of dedicated pilot as sole phase reference | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050251 | 392 | 1 | Removal of MBMS Rake Combining | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050242 | 394 | 1 | HS-DPCCH transmissions on discarding HS-SCCH | 6.5.0 | 6.6.0 | +| 16/06/05 | RP 28 | RP-050345 | 395 | - | Removal of E-RGCH non-serving radio link set | 6.5.0 | 6.6.0 | +| 26/09/05 | RP 29 | RP-050449 | 0398 | - | Power control annex for F-DPCH | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050447 | 0399 | 2 | Faster L1 DCH Synchronization | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050449 | 0400 | 1 | F-DPCH Quality Estimate | 6.6.0 | 6.7.0 | +| 26/09/05 | RP_29 | RP-050450 | 0401 | 2 | Downlink compressed mode and E-HICH, E-RGCH and E-AGCH | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050440 | 0403 | - | Downlink HS total power limitation | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050450 | 0404 | 1 | Clarification on power offset quantization | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050450 | 0405 | - | Clarification on computation of gain factors | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050450 | 0406 | 1 | E-DPDCH power scaling at the maximum power limit | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050547 | 0407 | 2 | Clarification on E-RGCH detection | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050645 | 0408 | 4 | PRACH preamble power at minimum power transmission | 6.6.0 | 6.7.0 | +| 26/09/05 | RP 29 | RP-050450 | 0412 | - | Clarification on E-AGCH, EHICH, E-RGCH power control | 6.6.0 | 6.7.0 | +| 12/12/05 | RP_30 | - | - | - | Editorial revision to the header format change of the chapter 6B.3 | 6.7.0 | 6.7.1 | +| 20/03/06 | RP_31 | RP-060076 | 0416 | - | Correction to number of configured DPDCHs in relation to E-DPDCH power scaling | 6.7.1 | 6.8.0 | +| 20/03/06 | RP 31 | - | - | - | Creation of Release 7 specification (v7.0.0) at RAN#31 | 6.8.0 | 7.0.0 | +| 12/06/06 | RP 32 | RP-060293 | 0418 | 1 | Correction of synchronization procedure | 7.0.0 | 7.1.0 | +| 12/06/06 | RP 32 | RP-060370 | 0420 | - | Clarification of E-TFCI terminology | 7.0.0 | 7.1.0 | +| 29/09/06 | RP 33 | RP-060490 | 0423 | 1 | Clarification of E-DPDCH gain factor quantization | 7.1.0 | 7.2.0 | +| 11/12/06 | RP_34 | RP-060727 | 0432 | 3 | Correction to E-DCH gain factor calculation in relation to compressed mode | 7.2.0 | 7.3.0 | +| 08/03/07 | RP_35 | RP-070114 | 0430 | 10 | Definition of MIMO operation on HS-PDSCH, preferred precoding and CQI reporting procedures, modified CQI tables | 7.3.0 | 7.4.0 | +| 08/03/07 | RP 35 | RP-070115 | 0421 | 13 | Support of CPC feature | 7.3.0 | 7.4.0 | +| 08/03/07 | RP 35 | RP-070116 | 0434 | 2 | Introduction of 64QAM for HSDPA | 7.3.0 | 7.4.0 | +| 30/05/07 | RP 36 | RP-070388 | 0435 | 5 | Introduction of 16-QAM for HSUPA | 7.4.0 | 7.5.0 | +| 30/05/07 | RP 36 | RP-070392 | 0437 | 2 | Enhanced F-DPCH | 7.4.0 | 7.5.0 | +| 30/05/07 | RP 36 | RP-070389 | 0438 | 6 | Clarification to the CPC feature | 7.4.0 | 7.5.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|----------------------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 30/05/07 | RP_36 | RP-070387 | 0440 | - | Setting of the uplink HS-DPCCH power relative to DPCCH power for MIMO | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070392 | 0446 | 1 | Enhanced F-DPCH and CPC DL PC timing | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070384 | 0449 | - | Support for DL only SFN operation for MBMS FDD | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070392 | 0450 | - | Clarification on power control operation for F-DPCH enhancement | 7.4.0 | 7.5.0 | +| 30/05/07 | RP_36 | RP-070390 | 0451 | 1 | Enhanced CELL_FACH Procedure | 7.4.0 | 7.5.0 | +| 11/09/07 | RP_37 | RP-070641 | 0452 | 2 | CPC preamble and postamble clarification for CQI transmission | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070641 | 0453 | - | Removal of Inactivity_Threshold_for_UE_Grant_Monitoring definition | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070643 | 0454 | 2 | Corrections to HS-DSCH procedures for CELL_FACH and MIMO | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070644 | 0456 | 3 | Correction to Rel-7 E-DPDCH gain factor calculation | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070645 | 0458 | 1 | Correction of 64QAM CQI tables | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070641 | 0459 | - | Clarification of CPC | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070644 | 0460 | 2 | E-DPDCH scaling when UE is at max power | 7.5.0 | 7.6.0 | +| 11/09/07 | RP_37 | RP-070642 | 0462 | 1 | Correction of MIMO CQI tables | 7.5.0 | 7.6.0 | +| 27/11/07 | RP_38 | RP-070945 | 0463 | - | Timing of CQI vs DTX priority change | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070945 | 0465 | - | Grant Monitoring clarification | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070947 | 0467 | 1 | Clarification on CQI tables in Rel-7 | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070945 | 0469 | 2 | Addition of TFRI to list of abbreviations | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070944 | 0470 | - | Correction to Rel-7 E-DPDCH gain factor calculation | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070941 | 0471 | 2 | Clarification of CQI definition | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070947 | 0473 | 2 | Clarification on HSDPA UE category in Rel-7 | 7.6.0 | 7.7.0 | +| 27/11/07 | RP_38 | RP-070911 | 0474 | - | Clarification on E-DPDCH power extrapolation/interpolation | 7.6.0 | 7.7.0 | +| 28/11/07 | RP_38 | RP-070948 | 0476 | - | Removing the constraint that the same HS-SCCH should be used in contiguous TTIs | 7.7.0 | 8.0.0 | +| 28/11/07 | RP_38 | RP-070950 | 0477 | - | Inclusion of CQI tables for the combination of 64QAM and MIMO | 7.7.0 | 8.0.0 | +| 04/03/08 | RP_39 | RP-080143 | 0480 | 1 | Correction to UE grant monitoring | 8.0.0 | 8.1.0 | +| 28/05/08 | RP_40 | RP-080350 | 0482 | 2 | CPC DTX cycle change clarification | 8.1.0 | 8.2.0 | +| 28/05/08 | RP_40 | RP-080440 | 0483 | 3 | HS-SCCH orders for HS-SCCH-less operation | 8.1.0 | 8.2.0 | +| 28/05/08 | RP_40 | RP-080439 | 0485 | - | Correction to E-DPCCH gain factor calculation | 8.1.0 | 8.2.0 | +| 28/05/08 | RP_40 | RP-080351 | 0492 | 1 | Correction to E-DCH control channel timing | 8.1.0 | 8.2.0 | +| 09/09/08 | RP_41 | RP-080672 | 0490 | 1 | Introduction of the Enhanced Uplink for CELL_FACH state | 8.2.0 | 8.3.0 | +| 09/09/08 | RP_41 | RP-080673 | 0498 | 3 | Introduction of HS-PDSCH Serving Cell Change Enhancements | 8.2.0 | 8.3.0 | +| 03/12/08 | RP_42 | RP-080989 | 0497 | 4 | Introduction of Dual-Cell HSDPA Operation on Adjacent Carriers | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080974 | 0502 | 1 | Clarification of F-DPCH TPC Combining Rule of cells in the same RLS | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080988 | 0503 | 1 | Introduction of HS-PDSCH Serving Cell Change Enhancements | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080986 | 0504 | 1 | Corrections in the physical random access procedure for Enhanced Uplink in CELL_FACH State and Idle mode | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080974 | 0506 | 2 | Correction to the description of CPC procedures | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080990 | 0508 | 2 | Improved EUL power control at UE power limitation | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080979 | 0509 | 1 | Typographical error correction in a parameter name in HS-PDSCH reception | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080986 | 0513 | - | Support of HS-DPCCH for Enhanced uplink in CELL_FACH state | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080978 | 0515 | - | Clarification of NIR setting in CQI mapping tables | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080975 | 0517 | 3 | Correction to E-DPDCH gain factor interpolation in compressed mode | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080989 | 0519 | - | References to CQI tables for DC-HSDPA | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080975 | 0523 | - | Correction to E-DPDCH gain factor calculation | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080974 | 0524 | - | Clarification of CQI repetition in case of UE DTX | 8.3.0 | 8.4.0 | +| 03/12/08 | RP_42 | RP-080989 | 0528 | - | Clarifications to Dual-Cell HSDPA Operation | 8.3.0 | 8.4.0 | +| 03/03/09 | RP_43 | RP-090227 | 0531 | - | Editorial correction to UE transmit power control behaviour in case of DTX/DRX | 8.4.0 | 8.5.0 | +| 03/03/09 | RP_43 | RP-090242 | 0534 | 2 | Corrections of HS-SCCH orders for DC-HSDPA | 8.4.0 | 8.5.0 | +| 03/03/09 | RP_43 | RP-090227 | 0535 | - | Clarification of CQI preamble length when switching UE DTX cycle | 8.4.0 | 8.5.0 | +| 03/03/09 | RP_43 | RP-090229 | 0538 | 1 | Clarification of the source of parameters to HS-DSCH physical layer | 8.4.0 | 8.5.0 | +| 26/05/09 | RP_44 | RP-090525 | 0545 | 1 | Clarification to the transmission of a combination of ACK and NACK | 8.5.0 | 8.6.0 | +| 26/05/09 | RP_44 | RP-090532 | 0546 | - | HS-DSCH serving cell change enhancements with preconfigured secondary cell | 8.5.0 | 8.6.0 | +| 15/09/09 | RP_45 | RP-090885 | 0550 | 1 | Clarification of CQI transmission when CQI priority changes | 8.6.0 | 8.7.0 | +| 15/09/09 | RP_45 | RP-090886 | 0553 | 1 | Clarification to support of HS-DSCH related procedures according to MAC-ehs | 8.6.0 | 8.7.0 | +| 15/09/09 | RP_45 | RP-090885 | 0557 | 1 | Clarification of CPC Enabling Delay | 8.6.0 | 8.7.0 | +| 15/09/09 | RP_45 | RP-090885 | 0559 | 1 | Clarification of DTX Cycle transitions and UL DPCCH burst transmissions | 8.6.0 | 8.7.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 15/09/09 | RP_45 | RP-090885 | 0561 | 1 | Clarification of the start of the CQI DTX Timer | 8.6.0 | 8.7.0 | +| 15/09/09 | RP_45 | RP-090883 | 0563 | 1 | Unequal Power Setting of P-CPICH and S-CPICH | 8.6.0 | 8.7.0 | +| 15/09/09 | RP_45 | RP-090889 | 0568 | 1 | HS-DPCCH ACK/NACK Power Offset setting for DC-HSDPA | 8.6.0 | 8.7.0 | +| 18/09/09 | RP_45 | RP-090975 | 0548 | 4 | Introduction of TxAA extension for non-MIMO UEs | 8.7.0 | 9.0.0 | +| 18/09/09 | RP_45 | RP-090974 | 0569 | - | Combination of DC-HSDPA with MIMO | 8.7.0 | 9.0.0 | +| 01/12/09 | RP_46 | RP-091170 | 0570 | 5 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091171 | 0574 | 3 | MIMO configuration per downlink frequency in DC-MIMO operation | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091174 | 0578 | 1 | Clarification to TxAA extension in dual cell | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091164 | 0580 | - | Clarification of HS-SCCH monitoring | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091163 | 0582 | - | Clarification of CQI nominal timer and CQI DTX TIMER | 9.0.0 | 9.1.0 | +| 01/12/09 | RP_46 | RP-091165 | 0589 | - | Table Index Correction | 9.0.0 | 9.1.0 | +| 16/03/10 | RP_47 | RP-100199 | 0592 | 3 | HSDPA MIMO codebook restriction | 9.1.0 | 9.2.0 | +| 16/03/10 | RP_47 | RP-100200 | 0594 | - | Correction to HS-DSCH and HS-SCCH reception in the URA_PCH and CELL_PCH states | 9.1.0 | 9.2.0 | +| 16/03/10 | RP_47 | RP-100206 | 0596 | 1 | Clarification of MIMO configuration per downlink frequency in DC-MIMO operation | 9.1.0 | 9.2.0 | +| 16/03/10 | RP_47 | RP-100207 | 0597 | - | Correction to Applicability of CQI Mapping Table | 9.1.0 | 9.2.0 | +| 16/03/10 | RP_47 | RP-100208 | 0599 | 1 | Decrease DC-HSPA carrier activation application time to 18 slots | 9.1.0 | 9.2.0 | +| 14/09/10 | RP_49 | RP-100893 | 0604 | 5 | Clarification of the CQI definition when the UE is configured in MIMO mode | 9.2.0 | 9.3.0 | +| 14/09/10 | RP_49 | RP-100883 | 0607 | 3 | Clarification of HS-DSCH and HS-SCCH reception in CELL_FACH, CELL_PCH and URA_PCH states | 9.2.0 | 9.3.0 | +| 14/09/10 | RP_49 | RP-100894 | 0614 | - | Clarification of E-AGCH/E-RGCH monitoring in a CM gap when DL_DRX_Active is TRUE | 9.2.0 | 9.3.0 | +| 14/09/10 | RP_49 | RP-100898 | 0615 | 2 | Clarification on the interruption time for DB-HSDPA due to HS-SCCH order (de)activation | 9.2.0 | 9.3.0 | +| 14/09/10 | RP_49 | RP-100897 | 0616 | - | Clarification on Secondary_EDCH_Cell_Active upon reception of redundant HS-SCCH order | 9.2.0 | 9.3.0 | +| 16/09/10 | RP_49 | RP-100902 | 0611 | 3 | Release 10 created with the introduction of 4C HSDPA | 9.3.0 | 10.0.0 | +| 07/12/10 | RP_50 | RP-101318 | 621 | 1 | Correction of number of received HS-DSCH and HS-SCCH in DC-HSDPA-MIMO and 4C-HSDPA | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101318 | 622 | 1 | Clarification on the interruption time for 4C-HSDPA due to HS-SCCH ordered (de)activation | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101312 | 627 | - | Further clarification of E-AGCH/E-RGCH monitoring in CM gap when DL_DRX_Active is TRUE | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101313 | 631 | 2 | Clarification of E-DPCCH gain factor calculation in compressed mode | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101312 | 637 | 1 | Clarification of discontinuous uplink DPCCH transmission and compressed mode | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101311 | 641 | 2 | Correction to the single stream CQI reporting in MIMO mode | 10.0.0 | 10.1.0 | +| 07/12/10 | RP_50 | RP-101310 | 650 | - | Clarification of the applicability of the IE Number of PCCH transmissions in CELL_PCH state | 10.0.0 | 10.1.0 | +| 15/03/11 | RP_51 | RP-110251 | 633 | 5 | Correction to CPC procedure for DC-HSUPA | 10.1.0 | 10.2.0 | +| 01/06/11 | RP_52 | RP-110816 | 653 | - | Clarification of activation status when Secondary_Cell_Enabled is changed from 0 to a value not equal to 0 | 10.2.0 | 10.3.0 | +| 15/09/11 | RP_53 | RP-111224 | 656 | - | Clarification of when to use Sync A procedure when UE transitions from CELL_FACH to CELL_DCH | 10.3.0 | 10.4.0 | +| 05/12/11 | RP_54 | RP-111670 | 658 | 2 | CQI reporting for frequency specific compressed mode | 10.4.0 | 10.5.0 | +| 05/12/11 | RP_54 | RP-111671 | 652 | 8 | Introduction of 8C-HSDPA | 10.5.0 | 11.0.0 | +| 05/12/11 | RP_54 | RP-111672 | 663 | - | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.5.0 | 11.0.0 | +| 28/02/12 | RP_55 | RP-120282 | 669 | - | Clarification of UL DPCCH Slot Format when DPC_MODE is 1 and CPC is not Enabled | 11.0.0 | 11.1.0 | +| 28/02/12 | RP_55 | RP-120288 | 670 | - | Corrections to Uplink Closed Loop Transmit Diversity | 11.0.0 | 11.1.0 | +| 28/02/12 | RP_55 | RP-120281 | 671 | - | Further Clarification of when to use Sync A procedure when UE transitions from CELL_FACH to CELL_DCH | 11.0.0 | 11.1.0 | +| 13/06/12 | RP_56 | RP-120741 | 677 | 1 | Clarification of CLTD Features | 11.1.0 | 11.2.0 | +| 13/06/12 | RP_56 | RP-120741 | 678 | 5 | Introduction of Timing Diagrams for F-TPICH Operation in UL CLTD | 11.1.0 | 11.2.0 | +| 13/06/12 | RP_56 | RP-120741 | 679 | 2 | Clarification of TPI timing and F-TPICH transmission for UL CLTD | 11.1.0 | 11.2.0 | +| 04/09/12 | RP_57 | RP-121271 | 685 | 2 | Introduction of Multiflow | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121384 | 686 | 1 | Correction of F-TPICH transmission | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121384 | 687 | 1 | Correction to the gain factor definition for S-DPCCH | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121270 | 690 | - | Introduction of Further Enhancements to CELL_FACH | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_57 | RP-121384 | 691 | - | Clarification to F-TPICH transmission | 11.2.0 | 11.3.0 | +| 04/09/12 | RP_58 | RP-121845 | 688 | 5 | Introduction of uplink MIMO and 64QAM | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121843 | 689 | 5 | Introduction of 4Tx_HSDPA in 25.214 | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121841 | 692 | - | Clarification of UE procedure for receiving HS-SCCH orders in the CELL_DCH state | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121841 | 695 | - | Clarification of F-TPICH configuration | 11.3.0 | 11.4.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|---------------------------------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 04/09/12 | RP_58 | RP-121842 | 697 | 2 | Clarification to the procedure of NodeB Triggered HS-DPCCH | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121844 | 699 | 2 | Clarifications and corrections to HSDPA Multiflow | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121842 | 700 | 1 | Clarification of the some aspects of Further Enhancements to CELL_FACH | 11.3.0 | 11.4.0 | +| 04/09/12 | RP_58 | RP-121836 | 701 | - | Power scaling handling for Multi-RAB | 11.3.0 | 11.4.0 | +| 26/02/13 | RP_59 | RP-130250 | 702 | 1 | Correction of HS-DPCCH power offset for four-branch MIMO | 11.4.0 | 11.5.0 | +| 26/02/13 | RP_59 | RP-130359 | 703 | 2 | Correction to the referenced variable for CELL-FACH enhancement | 11.4.0 | 11.5.0 | +| 11/06/13 | RP_60 | RP-130744 | 707 | 1 | Correction of HARQ PRE/POST transmission | 11.5.0 | 11.6.0 | +| 03/09/13 | | | | | MCC clean-up | 11.6.0 | 11.7.0 | +| 03/09/13 | RP_61 | RP-131247 | 709 | - | Corrections to Discontinuous downlink reception when the UE is in Multiflow mode | 11.6.0 | 11.7.0 | +| 03/09/13 | RP_61 | RP-131246 | 710 | - | Random Access Procedure | 11.6.0 | 11.7.0 | +| 03/03/14 | RP_63 | RP-140409 | 712 | 1 | Clarification on (de-)activation status of secondary carriers when higher layer indicates a change of HS-DSCH cells | 11.7.0 | 11.8.0 | +| 10/06/14 | RP_64 | RP-140860 | 716 | 2 | Clarifications to Multiflow Operation | 11.8.0 | 11.9.0 | +| 10/06/14 | RP_64 | RP-140860 | 717 | 1 | Compressed mode in Multiflow assisting (secondary) serving cell | 11.8.0 | 11.9.0 | +| 10/06/14 | RP_64 | RP-140860 | 718 | 1 | Correction of DRX operation for Multiflow | 11.8.0 | 11.9.0 | +| 10/06/14 | RP_64 | RP-140861 | 719 | 1 | Clarification of the power scaling for MIMO dual transport block transmission | 11.8.0 | 11.9.0 | +| 10/09/14 | RP_65 | RP-141475 | 721 | 2 | Clarifications to Multiflow Operation | 11.9.0 | 11.10.0 | +| 10/09/14 | RP_65 | RP-141476 | 722 | 1 | Correction to the Four Branch MIMO | 11.9.0 | 11.10.0 | +| 10/09/14 | RP_65 | RP-141480 | 715 | 2 | Introduction of DCH Enhancements | 11.10.0 | 12.0.0 | +| 10/09/14 | RP_65 | RP-141483 | 720 | 2 | Introduction of Further EUL Enhancements | 11.10.0 | 12.0.0 | +| 10/09/14 | RP_65 | RP-141481 | 723 | 1 | Introduction of UMTS Heterogeneous Networks enhancements | 11.10.0 | 12.0.0 | +| 08/12/14 | RP_66 | RP-142102 | 727 | 1 | Correction to UMTS Hetnet features | 12.0.0 | 12.1.0 | +| 08/12/14 | RP_66 | RP-142103 | 730 | 1 | Clarification of HS-SCCH orders for Rel-12 features | 12.0.0 | 12.1.0 | +| 08/12/14 | RP_66 | RP-142101 | 731 | 1 | Correction on DCH Enhancement | 12.0.0 | 12.1.0 | +| 08/12/14 | RP_66 | RP-142103 | 732 | 2 | Clarifications to Further EUL Enhancements | 12.0.0 | 12.1.0 | +| 08/12/14 | RP_66 | RP-142103 | 734 | - | Clarification on the CQI feedback cycle switching procedure | 12.0.0 | 12.1.0 | +| 09/03/15 | RP_67 | RP-150360 | 735 | 1 | Clarifications to UMTS Heterogeneous Network Enhancements | 12.1.0 | 12.2.0 | +| 15/06/15 | RP_68 | RP-150934 | 738 | - | Clarifications to Multiflow | 12.2.0 | 12.3.0 | +| 14/09/15 | RP_69 | RP-151469 | 739 | - | Introduction of 3F-4C Multiflow 3F-4C configuration | 12.3.0 | 13.0.0 | +| 07/12/15 | RP_70 | RP-152029 | 741 | 1 | Clarifications on definitions and CQI reporting in Multiflow 3F-4C configuration | 13.0.0 | 13.1.0 | +| 07/12/15 | RP_70 | RP-152039 | 743 | 1 | Introduction of downlink TPC enhancements for UMTS | 13.0.0 | 13.1.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-03 | RP-71 | RP-160368 | 0746 | 1 | F | Clarification on the availability of the F-DPCH for Algorithm1 and 2, within the first phase of the downlink synchronization status evaluation | 13.2.0 | +| 2016-03 | RP-71 | RP-160366 | 0745 | 1 | F | Correction of Rel-13 Downlink TPC Enhancements | 13.2.0 | +| 2016-06 | RP-72 | RP-161144 | 0748 | | F | Clarifications on DCH enhancements feature | 13.3.0 | +| 2016-07 | | | | | | MCC clean-up by removing unnecessary comments left in sections 5.1.2.2.4.2 and 5.1.2.2.4.3 | 13.3.1 | +| 2016-09 | RP-73 | RP-161568 | 0750 | - | A | Clarifications on UL Discontinuous Transmission with DCH enhancements (Rel. 13) | 13.4.0 | +| 2016-09 | RP-73 | RP-161568 | 0751 | 1 | A | Correction of DCH enhancements | 13.4.0 | +| 2016-09 | RP-73 | RP-161564 | 0753 | 1 | F | Correction of DCH enhancements | 13.4.0 | +| 2016-09 | RP-73 | RP-161568 | 0755 | - | A | Editorial clarification on the definitions of "UL DPCH 10ms Mode" and "UL DPCH 20ms Mode" of DCH enhancements for UMTS | 13.4.0 | +| 2016-12 | RP-74 | RP-162354 | 0758 | - | B | UE Procedures for HS-SCCH DRx feature in enhanced Cell Fach | 14.0.0 | +| 2017-03 | RP-75 | RP-170614 | 0759 | - | F | Clarification on the TTI switching for single cell E-DCH and dual cell E-DCH | 14.1.0 | +| 2017-09 | RP-77 | RP-171592 | 0760 | 2 | B | Introduction of the triggering mechanisms for the simplified HS-SCCH type 1 operation | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25215/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/25_series/25215/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8738d7a4c3edf872214e775c756c7b045bc0af17 --- /dev/null +++ b/marked/Rel-16/25_series/25215/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:065887938e5ffa81718c8dd6dee206056cd4ab2af47a31c634db99d11bb2fa27 +size 48222 diff --git a/marked/Rel-16/25_series/25215/raw.md b/marked/Rel-16/25_series/25215/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a229eacab8615303e56b0da8b855da2a7617feeb --- /dev/null +++ b/marked/Rel-16/25_series/25215/raw.md @@ -0,0 +1,662 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and Abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Control of UE/UTRAN measurements ..... | 7 | +| 5 Measurement abilities for UTRA FDD..... | 8 | +| 5.1 UE measurement abilities..... | 8 | +| 5.1.1 CPICH RSCP..... | 9 | +| 5.1.2 CCPCH RSCP ..... | 9 | +| 5.1.3 UTRA carrier RSSI ..... | 9 | +| 5.1.4 GSM carrier RSSI..... | 9 | +| 5.1.5 CPICH Ec/No ..... | 10 | +| 5.1.6 Transport channel BLER..... | 10 | +| 5.1.7 UE transmitted power ..... | 10 | +| 5.1.8 SFN-CFN observed time difference ..... | 11 | +| 5.1.9 SFN-SFN observed time difference ..... | 11 | +| 5.1.10 UE Rx-Tx time difference ..... | 12 | +| 5.1.11 Void ..... | 12 | +| 5.1.12 UE GPS Timing of Cell Frames for UE positioning ..... | 12 | +| 5.1.13 UE GPS code phase..... | 12 | +| 5.1.14 UE transmission power headroom..... | 12 | +| 5.1.15 UE GANSS Timing of Cell Frames for UE positioning ..... | 13 | +| 5.1.16 UE GANSS code measurements ..... | 13 | +| 5.1.17 E-UTRA RSRP..... | 13 | +| 5.1.18 Void ..... | 13 | +| 5.1.19 E-UTRA RSRQ ..... | 14 | +| 5.1.20 IEEE 802.11 Beacon RSSI ..... | 14 | +| 5.2 UTRAN measurement abilities ..... | 14 | +| 5.2.1 Received total wide band power..... | 15 | +| 5.2.2 SIR ..... | 15 | +| 5.2.3 $SIR_{error}$ ..... | 15 | +| 5.2.4 Transmitted carrier power ..... | 16 | +| 5.2.5 Transmitted code power ..... | 16 | +| 5.2.6 Transport channel BER ..... | 16 | +| 5.2.7 Physical channel BER ..... | 16 | +| 5.2.8 Round trip time..... | 17 | +| 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning ..... | 17 | +| 5.2.10 PRACH Propagation delay..... | 17 | +| 5.2.11 Acknowledged PRACH preambles ..... | 17 | +| 5.2.12 Void ..... | 18 | +| 5.2.13 Void ..... | 18 | +| 5.2.14 SFN-SFN observed time difference ..... | 18 | +| 5.2.15 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission ..... | 18 | +| 5.2.16 DL Transmission Branch Load ..... | 18 | +| 5.2.17 Received scheduled E-DCH power share (RSEPS) ..... | 19 | +| 5.2.18 UTRAN GANSS Timing of Cell Frames for UE positioning..... | 19 | +| 6 Measurements for UTRA FDD..... | 19 | +| 6.1 UE measurements..... | 19 | +| 6.1.1 Compressed mode ..... | 19 | +| 6.1.1.1 Use of compressed mode for monitoring..... | 19 | +| 6.1.1.2 Parameterisation of the compressed mode..... | 20 | + +Annex A (informative): Change history................................................................................................ 23 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the description and definition of the measurements for FDD done at the UE and network in order to support operation in idle mode and connected mode. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer - Measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [11] 3GPP TS 25.302: "Services provided by the Physical layer". +- [12] 3GPP TS 25.303: "UE functions and interlayer procedures in connected mode". +- [13] 3GPP TS 25.304: "UE procedures in idle mode". +- [14] 3GPP TS 25.331: "RRC Protocol Specification". +- [15] 3GPP TR 25.922: "Radio Resource Management Strategies". +- [16] 3GPP TR 25.923: "Report on Location Services (LCS)". +- [17] 3GPP TR 25.401: "UTRAN Overall Description". +- [18] 3GPP TS 25.101: "UE Radio transmission and Reception (FDD)". +- [19] 3GPP TS 25.104: "UTRA (BS) FDD; Radio transmission and Reception". +- [20] 3GPP TS 25.133: " Requirements for Support of Radio Resource Management (FDD)" +- [21] 3GPP TS 25.225: " Physical layer – Measurements (TDD)". +- [22] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification" + +- [23] 3GPP TS 36.211: "E-UTRA; Physical Channels and Modulation" +- [24] 3GPP TS 36.214: "E-UTRA; Physical layer – Measurements" +- [25] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std." + +# --- 3 Definitions and Abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**cell portion:** A geographical part of a cell for which a Node B measurement can be reported to the RNC. A cell portion is semi-static, and identical for both the UL and the DL. Within a cell, a cell portion is uniquely identified by a cell portion ID. + +Note 1: a cell portion is not necessarily analogous to actual beams used for transmission and/or reception of e.g. a DPCH at the Node B. + +Note 2: RNC may associate physical channels with cell portions. + +**DL\_DCH\_FET\_Config:** Higher layers signal this configuration parameter to indicate enhanced DCH physical layer configuration. The possible values are 0 and 1. The value 0 indicates Mode 0 configuration where DL transport channels concatenation and UL ACK/NACK signalling are not configured. The value 1 indicates Mode 1 where DL transport channel concatenation and UL ACK/NACK signalling for DL FET are configured. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------------------------------| +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| Ec/No | Received energy per chip divided by the power density in the band | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| F-DPCH | Fractional Dedicated Physical Channel | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| ISCP | Interference Signal Code Power | +| RL | Radio Link | +| RSCP | Received Signal Code Power | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| SIR | Signal to Interference Ratio | + +# --- 4 Control of UE/UTRAN measurements + +In this chapter the general measurement control concept of the higher layers is briefly described to provide an understanding on how L1 measurements are initiated and controlled by higher layers. + +L1 provides with the measurement specifications a toolbox of measurement abilities for the UE and the UTRAN. These measurements can be differentiated in different reported measurement types: intra-frequency, inter-frequency, inter-system, traffic volume, quality and UE internal measurements (see [14]). + +In the L1 measurement specifications the measurements, see chapter 5, are distinguished between measurements in the UE (the messages will be described in the RRC Protocol or MAC Protocol [22]) and measurements in the UTRAN (the messages will be described in the NBAP and the Frame Protocol). + +To initiate a specific measurement the UTRAN transmits a 'measurement control message' to the UE including a measurement ID and type, a command (setup, modify, release), the measurement objects and quantity, the reporting quantities, criteria (periodical/event-triggered) and mode (acknowledged/unacknowledged), see [14]. + +When the reporting criteria is fulfilled the UE shall answer with a 'measurement report message' to the UTRAN including the measurement ID and the results. + +In idle mode the measurement control message is broadcast in a System Information. + +Intra-frequency reporting events, traffic volume reporting events and UE internal measurement reporting events described in [14] define events which trigger the UE to send a report to the UTRAN. This defines a toolbox from which the UTRAN can choose the needed reporting events. + +# 5 Measurement abilities for UTRA FDD + +In this chapter the physical layer measurements reported to higher layers are defined. The GSM measurements are required only from the GSM capable terminals. The TDD measurements are required only from the terminals that are capable to operate in TDD mode. + +## 5.1 UE measurement abilities + +The structure of the table defining a UE measurement quantity is shown below. + +| Column field | Comment | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Contains the definition of the measurement. | +| Applicable for | States in which RRC state according to [14] a measurement shall be possible to perform. For RRC connected mode states information is also given on the possibility to perform the measurement on intra-frequency and/or inter-frequency.
The following terms are used in the tables:
Idle = Shall be possible to perform in idle mode;
URA_PCH = Shall be possible to perform in URA_PCH;
CELL_PCH = Shall be possible to perform in CELL_PCH;
CELL_FACH = Shall be possible to perform in CELL_FACH;
CELL_DCH = Shall be possible to perform in CELL_DCH;

For all RRC connected mode states i.e. URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH
Intra appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an intra-frequency cell;
Inter appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-frequency cell.
Inter-RAT appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-RAT cell. | + +The term "antenna connector of the UE" used in this sub-clause to define the reference point for the UE measurements is defined in [18]. Performance and reporting requirements for the UE measurements are defined in [20]. + +### 5.1.1 CPICH RSCP + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one code measured on the Primary CPICH. The reference point for the RSCP shall be the antenna connector of the UE. If Tx diversity is applied on the Primary CPICH the received code power from each antenna shall be separately measured and summed together in [W] to a total received code power on the Primary CPICH. If receiver diversity is in use by the UE, the measured CPICH RSCP value shall not be lower than the corresponding CPICH RSCP of any of the individual receive antenna branches. | +| Applicable for | Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter | + +### 5.1.2 PCCPCH RSCP + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one code measured on the PCCPCH from a TDD cell. The reference point for the RSCP shall be the antenna connector of the UE.
See [21] for further details on this measurement. | +| Applicable for | Idle,
URA_PCH inter,
CELL_PCH inter,
CELL_FACH inter,
CELL_DCH inter | + +### 5.1.3 UTRA carrier RSSI + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter. The reference point for the measurement shall be the antenna connector of the UE. If receiver diversity is in use by the UE, the measured UTRA carrier RSSI value shall not be lower than the corresponding UTRA carrier RSSI of any of the individual receive antenna branches. | +| Applicable for | CELL_DCH intra, CELL_DCH inter | + +### 5.1.4 GSM carrier RSSI + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Strength Indicator, the wide-band received power within the relevant channel bandwidth. Measurement shall be performed on a GSM BCCH carrier. The reference point for the RSSI shall be the antenna connector of the UE. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_FACH inter-RAT
CELL_DCH inter-RAT | + +### 5.1.5 CPICH Ec/No + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received energy per chip divided by the power density in the band. If receiver diversity is not in use by the UE, the CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI. Measurement shall be performed on the Primary CPICH. The reference point for the CPICH Ec/No shall be the antenna connector of the UE. If Tx diversity is applied on the Primary CPICH the received energy per chip (Ec) from each antenna shall be separately measured and summed together in [Ws] to a total received chip energy per chip on the Primary CPICH, before calculating the Ec/No. If receiver diversity is in use by the UE the measured CPICH Ec/No value shall not be lower than the corresponding CPICH RSCP/UTRA Carrier RSSI of receive antenna branch i. | +| Applicable for | Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter | + +### 5.1.6 Transport channel BLER + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

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

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

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

| +| Applicable for | CELL_DCH intra | + +### 5.1.7 UE transmitted power + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The sum of the total UE transmitted power on all configured uplink carriers. The reference point for the UE transmitted power shall be the antenna connector of the UE. In the case where transmissions from multiple branches take place the transmitted power for each branch shall be measured and summed together in [W]. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.8 SFN-CFN observed time difference + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

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

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

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

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

| +| Applicable for |

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

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

| + +### 5.1.10 UE Rx-Tx time difference + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The difference in time between the UE uplink DPCCH frame transmission and the first detected path (in time), of the downlink DPCH or F-DPCH frame from the measured radio link. Type 1 and Type 2 are defined. For Type 1, the reference Rx path shall be the first detected path (in time) amongst the paths (from the measured radio link) used in the demodulation process. For Type 2, the reference Rx path shall be the first detected path (in time) amongst all paths (from the measured radio link) detected by the UE. The reference path used for the measurement may therefore be different for Type 1 and Type 2. The reference point for the UE Rx-Tx time difference shall be the antenna connector of the UE. Measurement shall be made for each cell included in the active set.

| +| Applicable for | CELL_DCH intra | + +### 5.1.11 Void + +### 5.1.12 UE GPS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The timing between cell j and GPS Time Of Week. T_{UE-GPSj} is defined as the time of occurrence of a specified UTRAN event according to GPS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for T_{UE-GPSj} shall be the antenna connector of the UE.

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

For each uplink DPCCH, UE transmission power headroom (UPH) is the ratio of the maximum UE transmission power and the DPCCH code power, and shall be calculated as following:
UPH = P_{max,tx} / P_{DPCCH} where:
P_{max,tx} = \min \{Maximum\ allowed\ UL\ TX\ Power, P_{max}\} is the UE maximum transmission power;
Maximum allowed UL TX Power is set by UTRAN and defined in [14];
P_{max} is the UE nominal maximum output power according to the UE power class and specified in [18] table 6.1;
P_{DPCCH} is the transmitted code power on the DPCCH.

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

| +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.15 UE GANSS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The timing between cell j and GANSS Time Of Day for a given GANSS system. $T_{UE-GANSS}$ is defined as the time of occurrence of a specified UTRAN event according to GANSS time for a given GANSS Id. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for $T_{UE-GANSS}$ shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.16 UE GANSS code measurements + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The GANSS code phase and GANSS Integer code phase of the spreading code of the $i^{\text{th}}$ GANSS satellite signal. The reference point for the GANSS code phase shall be the antenna connector of the UE. | +| Applicable for | Void (this measurement is not related to UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state) | + +### 5.1.17 E-UTRA RSRP + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

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

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

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

| +| Applicable for |

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

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

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

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

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

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

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

| +| Applicable for |

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

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

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

where:

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

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

where:

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

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

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

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

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

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

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

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

Round trip time (RTT), is defined as
RTT = T_{RX} - T_{TX}, where
T_{TX} = The time of transmission of the beginning of a downlink DPCH or F-DPCH frame to a UE. The reference point for T_{TX} shall be the Tx antenna connector.
T_{RX} = The time of reception of the beginning (the first detected path, in time) of the corresponding uplink DPCCH frame from the UE. The reference point for T_{RX} shall be the Rx antenna connector.
Measurement shall be possible on DPCH or F-DPCH for each RL transmitted from an UTRAN access point and DPDCH for each RL received in the same UTRAN access point.

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | T UTRAN-GPS is defined as the time of the occurrence of a specified UTRAN event according to GPS Time Of Week. The specified UTRAN event is the beginning of the transmission of a particular frame in the cell. The reference point for T UTRAN-GPS shall be the Tx antenna connector. | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.10 PRACH Propagation delay + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

PRACH :

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

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

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

| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.11 Acknowledged PRACH preambles + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The Acknowledged PRACH preambles measurement is defined as the total number of acknowledged PRACH preambles per access frame per PRACH. This is equivalent to the number of positive acquisition indicators transmitted per access frame per AICH. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.12 Void + +### 5.2.13 Void + +### 5.2.14 SFN-SFN observed time difference + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

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

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

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

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

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

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

The 'DL transmission branch load' is the maximum of the transmission branch loads calculated for each branch.
A 'transmission branch load' is the ratio between the total transmitted power [W] on the considered branch and the 'maximum DL branch capability' on this branch.
The 'maximum DL branch capability' defines the maximum transmission power possible to use on that branch.
The reference point for the transmission branch load measurement shall be the TX antenna connector.

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

The 'Received scheduled E-DCH power share' is defined as a report of 2 values for a considered cell:
1. RSEPS: defined as a quotient:
sum of all scheduled E-DPCCH and E-DPDCH power contributions determined in the RSEPS measurement period T=t2-t1>0 for all UEs for which this cell is the serving E-DCH cell
divided by
the corresponding received total wideband power value determined for this cell during T.
2. RTWP*: This is the received total wideband power (RTWP) measured for this cell as defined in section 5.2.1 but determined for the same time period T starting at t1 and ending at t2 during which RSEPS is determined.
The reference point for the RSEPS and RTWP* measurements shall be the Rx antenna connector.
When cell portions are defined in the cell, RSEPS (and RTWP*) shall be measured for each cell portion.

The sum in the numerator of RSEPS is determined under the following conditions:
- The contributions are summed up TTI wise and only TTIs which are ending between the time instants t1 and t2 are considered.
- In case a UE has not only a radio link to the considered cell but also other radio links to the same Node B ('softer handover'): It is allowed to take into account the power value combined for these radio links of the same Node B and divided by the number of combined radio links.
Note: For improved measurement performance it is possible to consider only the power contribution determined for the considered cell.

| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.18 UTRAN GANSS Timing of Cell Frames for UE positioning + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | T UTRAN-GANSS is defined as the time of the occurrence of a specified UTRAN event according to GANSS Time Of Day. The specified UTRAN event is the beginning of the transmission of a particular frame in the cell. The reference point for T UTRAN-GANSS shall be the Tx antenna connector. | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# --- 6 Measurements for UTRA FDD + +## 6.1 UE measurements + +### 6.1.1 Compressed mode + +#### 6.1.1.1 Use of compressed mode for monitoring + +On command from the UTRAN, a UE shall monitor cells on other FDD frequencies and on other modes and radio access technologies that are supported by the UE (i.e. TDD, GSM, E-UTRA). To allow the UE to perform measurements, UTRAN shall command that the UE enters in compressed mode, depending on the UE capabilities. + +The UE capabilities define whether a UE requires compressed mode in order to monitor cells on other FDD frequencies and on other modes and radio access technologies. UE capabilities indicate the need for compressed mode separately for the uplink and downlink and for each mode, radio access technology and frequency band. + +A UE shall support compressed mode for all cases for which the UE indicates that compressed mode is required. + +A UE does not need to support compressed mode for cases for which the UE indicates that compressed mode is not required. For these cases, the UE shall support an alternative means of making the measurements. + +The UE shall support one single measurement purpose for one transmission gap pattern sequence. The measurement purpose of the transmission gap pattern sequence is signalled by higher layers. + +The following subclause provides rules to parameterise the compressed mode. + +#### 6.1.1.2 Parameterisation of the compressed mode + +In response to a request from higher layers, the UTRAN shall signal to the UE the compressed mode parameters. + +A transmission gap pattern sequence consists of consecutive occurrences of transmission gap pattern 1, where transmission gap pattern 1 consists of one or two transmission gaps. See figure 1. + +The following parameters characterise a transmission gap pattern: + +- TGSN (Transmission Gap Starting Slot Number): A transmission gap pattern begins in a radio frame, henceforward called first radio frame of the transmission gap pattern, containing at least one transmission gap slot. TGSN is the slot number of the first transmission gap slot within the first radio frame of the transmission gap pattern; +- TGL1 (Transmission Gap Length 1): This is the duration of the first transmission gap within the transmission gap pattern, expressed in number of slots; +- TGL2 (Transmission Gap Length 2): This is the duration of the second transmission gap within the transmission gap pattern, expressed in number of slots. If this parameter is not explicitly set by higher layers, then $TGL2 = TGL1$ ; +- TGD (Transmission Gap start Distance): This is the duration between the starting slots of two consecutive transmission gaps within a transmission gap pattern, expressed in number of slots. The resulting position of the second transmission gap within its radio frame(s) shall comply with the limitations of [2]. If this parameter is not set by higher layers, then there is only one transmission gap in the transmission gap pattern; + +- TGPL1 (Transmission Gap Pattern Length): This is the duration of transmission gap pattern 1, expressed in number of frames; + +The following parameters control the transmission gap pattern sequence start and repetition: + +- TGPRC (Transmission Gap Pattern Repetition Count): This is the number of transmission gap patterns within the transmission gap pattern sequence; +- TGCFN (Transmission Gap Connection Frame Number): This is the CFN of the first radio frame of the first pattern 1 within the transmission gap pattern sequence. + +In addition to the parameters defining the positions of transmission gaps, each transmission gap pattern sequence is characterised by: + +- UL/DL compressed mode selection: This parameter specifies whether compressed mode is used in UL only, DL only or both UL and DL; +- UL compressed mode method: The methods for generating the uplink compressed mode gap are spreading factor division by two or higher layer scheduling and are described in [2]. This parameter does not impact the compressed mode method used when DL\_DCH\_FET\_Config is configured by higher layers; +- DL compressed mode method: The methods for generating the downlink compressed mode gap are spreading factor division by two or higher layer scheduling and are described in [2]. This parameter does not impact the compressed mode method used when DL\_DCH\_FET\_Config is configured by higher layers; +- downlink frame type: This parameter defines if frame structure type 'A' or 'B' shall be used in downlink compressed mode. The frame structures are defined in [2]; +- scrambling code change: This parameter indicates whether the alternative scrambling code is used for compressed mode method 'SF/2'. Alternative scrambling codes are described in [3]; +- RPP: Recovery Period Power control mode specifies the uplink power control algorithm applied during recovery period after each transmission gap in compressed mode. RPP can take 2 values (0 or 1). The different power control modes are described in [4]; +- ITP: Initial Transmit Power mode selects the uplink power control method to calculate the initial transmit power after the gap. ITP can take two values (0 or 1) and is described in [4]. + +The UE shall support simultaneous compressed mode pattern sequences which can be used for different measurements. The following measurement purposes can be signalled from higher layers: + +- FDD +- TDD +- GSM carrier RSSI measurement +- Initial BSIC identification +- BSIC re-confirmation +- E-UTRA. + +The UE shall support one compressed mode pattern sequence for each measurement purpose while operating in FDD mode, assuming the UE needs compressed mode to perform the respective measurement. In case the UE supports several of the measurement purposes, it shall support in parallel one compressed mode pattern sequence for each supported measurement purpose where the UE needs compressed mode to perform the measurement. The capability of the UE to operate in compressed mode in uplink and downlink is given from the UE capabilities. + +The GSM measurements Initial BSIC identification and BSIC re-confirmation are defined in [20]. + +Higher layers will ensure that the compressed mode gaps do not overlap and are not scheduled to overlap the same frame. The behaviour when an overlap occurs is described in [11]. UE is not required to support two compressed mode gaps in a frame. + +In all cases, higher layers have control of individual UE parameters. Any pattern sequence can be stopped on higher layers' command. + +The parameters TGSN, TGL1, TGL2, TGD, TGPL1, TGPRC and TGCFN shall all be integers. + +![Figure 1: Illustration of compressed mode pattern parameters. The diagram shows a sequence of 'TG pattern 1' blocks labeled #1 through #5 and #TGPRC. Below this, a detailed view shows two 'Transmission' blocks separated by 'gap 1' and 'gap 2'. Various timing parameters are indicated: TGSN (start of the first transmission), TGL1 (length of the first transmission), TGL2 (length of the second transmission), TGD (gap duration between transmissions), and TGPL1 (total period of the pattern).](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 1: Illustration of compressed mode pattern parameters. The diagram shows a sequence of 'TG pattern 1' blocks labeled #1 through #5 and #TGPRC. Below this, a detailed view shows two 'Transmission' blocks separated by 'gap 1' and 'gap 2'. Various timing parameters are indicated: TGSN (start of the first transmission), TGL1 (length of the first transmission), TGL2 (length of the second transmission), TGD (gap duration between transmissions), and TGPL1 (total period of the pattern). + +Figure 1: Illustration of compressed mode pattern parameters + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99590 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99688 | 001 | 3 | Clarifications for compressed mode parameters | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 002 | - | Definition of PCCPCH RSCP | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 003 | - | Definition of observed time difference to GSM cell | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 004 | - | Measurements are done on Primary CPICH | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 005 | 1 | Physical channel BER on DPCCH | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 006 | - | Definition of SIR measurement | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 007 | 2 | Ranges and resolution of timing measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 009 | 2 | Range and resolution for RF related measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 010 | 2 | New subclauses: 5.1.15 - UE GPS Timing of Cell Frames for LCS; 5.2.8 UTRAN GPS Timing of Cell Frames for LCS | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 011 | - | Removal of Annex A from TS 25.215 | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 013 | - | Definition of Transmitted code power | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 014 | 2 | Range and resolution of BLER measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 015 | 2 | Range and resolution of BER measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 020 | - | Correction of SFN-SFN observed time difference | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 021 | 1 | CFN-SFN measurement with compressed mode | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000066 | 024 | 1 | Definition of Transmitted carrier power | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 025 | - | Clarification of Observed time difference to GSM cell | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 027 | - | Naming of BER/BLER mapping | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 028 | - | Minor corrections in TS 25.215 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 029 | - | Re-definition of timing measurements | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 030 | 2 | Mapping of timing measurements | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 031 | - | Removal of note in Round trip time measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 033 | - | Removal of fixed gap position in 25.215 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 036 | 4 | Corrections to 25.215 compressed mode parameter list | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 037 | 3 | Definition and range of physical channel BER | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 040 | - | Clarification of CPICH measurements in Tx diversity | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 042 | 1 | UTRAN RSSI measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 043 | 1 | UTRAN Propagation delay | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 044 | 2 | Correction to subclauses: 5.1.15 UE GPS Timing of Cell Frames for LCS; 5.2.8 UTRAN GPS Timing of Cell Frames for LCS, including timing mapping | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 047 | - | Removal of RSCP measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 048 | - | UE BER measurement removal and clarification for use of uplink compressed mode | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000270 | 049 | 1 | Propagation delay for PCPCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 050 | 1 | Maximum number of simultaneous compressed mode pattern sequences | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 051 | 1 | Clarification of Physical channel BER | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 052 | - | Clarification of transmitted code power | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 053 | - | Editorial correction in TS 25.215 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 055 | - | Proposed CR for Measurements of RACH in FDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 056 | - | Proposed CR for Measurements of CPCH in FDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 057 | - | Transfer of information from TS 25.212 table 9 to TS 25.215 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 058 | - | Correction to CM parameter list | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 062 | - | Clarification of radio link measurements in compressed mode | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 063 | - | Clarification of the Transmitted code power measurement in Tx diversity | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 064 | 1 | Removal of Range/mapping | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 066 | - | Removal of UTRAN TrCH BLER measurement | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000343 | 067 | - | Insertion of UTRAN SIRerro measurement in 25.215 | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 068 | - | Reporting of UTRAN Transmitted carrier power | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 070 | - | Clarification of UTRAN SIR measurement | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 071 | - | Clarification of first significant path | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 072 | - | Clarification of radio link set as the measured object | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000541 | 069 | 3 | Support of parallel compressed mode patterns | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 074 | 1 | Clarification of SIRerror measurement during compressed mode | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 075 | 2 | Definition of UTRAN RSSI | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 076 | 1 | Clarification of GPS timing measurements | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 077 | 2 | Clarification of reference point for UE/UTRAN measurements | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 078 | 1 | Correction to measurement "Rx-Tx time difference" | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 080 | 1 | Clarifications to compressed mode usage | 3.4.0 | 3.5.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010061 | 079 | 2 | Correction of the observed time difference to GSM measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN_11 | RP-010061 | 081 | - | Removal of UE SIR measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN_11 | RP-010061 | 082 | 1 | Correction of GSM reference | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN_11 | RP-010061 | 083 | - | Correction of GPS Timing measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN_11 | RP-010061 | 086 | - | Correction on transport channel BLER | 3.5.0 | 3.6.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 16/03/01 | RAN_11 | RP-010072 | 085 | - | RTD measurement in UTRAN for FDD | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010335 | 088 | - | Renaming of LCS measurements | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010456 | 090 | 2 | Correction the TrCH BLER measurement | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010521 | 096 | - | Removal of the BLER measurement of the BCH | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010740 | 098 | - | Clarification of internal measurements | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010740 | 103 | - | Clarification of P-CCPCH RSCP in 25.215 | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010740 | 105 | - | Revised definitions of CPICH Ec/No and UTRA carrier RSSI | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010745 | 099 | 2 | UE GPS code phase measurement | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010745 | 106 | 1 | UTRAN SFN-SFN observed time difference measurement | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020245 | 114 | 3 | Clarification of UE measurements Applicability | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020048 | 116 | - | Correction to the definition of UTRAN GPS timing of cell frames for UE positioning | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020048 | 117 | - | Correction to the definition of UE GPS timing of cell frames for UE positioning | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020231 | 111 | 1 | Removal of channel coding option "no coding" for FDD | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | - | - | - | Raised up to v5.0.0 together with other specs. | 4.4.0 | 5.0.0 | +| 18/09/02 | RAN_17 | RP-020530 | 119 | 4 | Transmitted carrier power measurement correction | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN_17 | RP-020575 | 121 | - | Measurements for observed time difference to GSM cell | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN_17 | RP-020575 | 130 | - | Compressed mode limitation | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN_17 | RP-020558 | 128 | - | Correction of UE SFN-SFN type 1 measurement | 5.0.0 | 5.1.0 | +| 21/12/02 | RAN_18 | RP-020842 | 131 | 1 | Received Total Wide Band Power Measurement Definition | 5.1.0 | 5.2.0 | +| 26/03/03 | RAN_19 | RP-030017 | 133 | 3 | Correction of UTRAN SIR measurement definition | 5.2.0 | 5.3.0 | +| 26/03/03 | RAN_19 | RP-030081 | 134 | 1 | Non-HSDPA power measurement | 5.2.0 | 5.3.0 | +| 23/06/03 | RAN_20 | RP-030270 | 142 | - | Correction of transmitted carrier power definition in case of Tx diversity | 5.3.0 | 5.4.0 | +| 23/06/03 | RAN_20 | RP-030274 | 143 | - | Correction of transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission definition in case of Tx diversity | 5.3.0 | 5.4.0 | +| 22/09/03 | RAN_21 | RP-030452 | 144 | 1 | Beamforming Enhancement related measurements | 5.4.0 | 5.5.0 | +| 07/01/04 | RAN_22 | - | - | - | Approved to promote to a Release 6 TS and created for M.1457 update | 5.5.0 | 6.0.0 | +| 07/01/04 | RAN_22 | RP-030726 | 145 | 2 | Beamforming Enhancement related measurements | 5.5.0 | 6.0.0 | +| 13/12/04 | RAN_26 | RP-040449 | 149 | 1 | Introduction of E-DCH | 6.0.0 | 6.1.0 | +| 14/03/05 | RAN_27 | RP-050050 | 147 | 4 | Introduction of 'DL Transmission Branch Load' measurement | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN_27 | RP-050038 | 153 | 1 | Removal of TGPL2 | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN_27 | RP-050092 | 154 | - | Clarification of the cell on SFN-SFN observed time difference | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN_27 | RP-050088 | 155 | - | Introduction of F-DPCH without pilot field | 6.1.0 | 6.2.0 | +| 16/06/05 | RAN_28 | RP-050250 | 161 | - | Feature Clean Up: Removal of "CPCH" | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050245 | 163 | - | Feature Clean Up: Removal of observed time difference to GSM cell measurement | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050249 | 165 | - | Feature clean up: Removal of the 'compressed mode by puncturing' | 6.2.0 | 6.3.0 | +| 26/09/05 | RAN_29 | RP-050453 | 0166 | 1 | UE power headroom measurement | 6.3.0 | 6.4.0 | +| 26/09/05 | RAN_29 | RP-050440 | 0167 | - | Non-HS power measurement | 6.3.0 | 6.4.0 | +| 20/03/06 | RAN_31 | - | - | - | Creation of Release 7 specification (v.7.0.0) at RAN#31 | 6.4.0 | 7.0.0 | +| 29/09/06 | RAN_33 | RP-060495 | 0170 | 3 | Introduction of a Node B measurement for E-DCH RRM | 7.0.0 | 7.1.0 | +| 30/05/07 | RAN_36 | RP-070391 | 0172 | 5 | Clarification of UE measurement definitions for RX diversity | 7.1.0 | 7.2.0 | +| 11/09/07 | RAN_37 | RP-070648 | 0176 | 1 | Adding GANSS related measurements in the FDD physical layer measurements | 7.2.0 | 7.3.0 | +| 27/11/07 | RAN_38 | RP-070946 | 0177 | - | Clarification of UE measurement definitions for RX diversity | 7.3.0 | 7.4.0 | +| 04/03/08 | RAN_39 | - | - | - | Release 8 version further to RAN_39 decision | 7.4.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080436 | 188 | - | E-UTRA measurements for UTRA – E-UTRA interworking | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080672 | 189 | - | UPH measurement support for Enhanced Uplink for CELL_FACH state | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080666 | 190 | - | Modification of RSRQ and removal of RSSI | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080666 | 192 | - | Modification of RSRP definition | 8.1.0 | 8.2.0 | +| 03/03/09 | RAN_43 | RP-090232 | 194 | 1 | RSRP and RSRQ Measurement Definitions | 8.2.0 | 8.3.0 | +| 15/09/09 | RAN_45 | RP-090888 | 195 | 1 | Clarification on reference point of RSRP and RSRQ for EUTRA | 8.3.0 | 8.4.0 | +| 18/09/09 | RAN_45 | - | - | - | Release 9 created further to RAN_45 decision | 8.4.0 | 9.0.0 | +| 01/12/09 | RAN_46 | RP-091170 | 196 | 2 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 | +| 16/03/10 | RAN_47 | RP-100205 | 197 | 2 | Modification of RSRQ definition | 9.1.0 | 9.2.0 | +| 21/03/11 | SP_51 | - | - | - | Release 10 created further to SP_51 decision | 9.2.0 | 10.0.0 | +| 05/12/11 | RAN_54 | RP-111672 | 199 | - | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.0.0 | 11.0.0 | +| 10/09/14 | RAN_65 | RP-141480 | 201 | 1 | Introduction of DCH Enhancements | 11.0.0 | 12.0.0 | +| 10/09/14 | RAN_65 | RP-141484 | 202 | 2 | Inclusion of definition of WLAN Beacon RSSI in UMTS specifications | 11.0.0 | 12.0.0 | +| 09/03/15 | RAN_67 | RP-150361 | 200 | 2 | New E-UTRA RSRQ measurement definition | 12.0.0 | 12.1.0 | +| 07/12/15 | SP_70 | - | - | - | Release 13 created further to SP_70 decision | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|------------------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-06 | RP-72 | RP-161144 | 0206 | | F | Clarification on measuring the transmitted code power for the downlink DPCH slot formats #17 and #18 | 13.1.0 | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25222/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25222/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ff92067e9391fc0e438d25ec5ff157ca962b764 --- /dev/null +++ b/marked/Rel-16/25_series/25222/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f21c5d24cc93de756c78e9cbbde38ddf88e20788fb9b9c608c0ad62d3cc03f5 +size 14301 diff --git a/marked/Rel-16/25_series/25222/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/25_series/25222/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00d5abf36f0a7205ec18d00e915e227f3b4a58e5 --- /dev/null +++ b/marked/Rel-16/25_series/25222/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c61767f306401bbd05effef8ca842df22aad82a74deceb4553fec6e7927b0ec +size 46946 diff --git a/marked/Rel-16/25_series/25222/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/25_series/25222/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a2e7306d42902d4a9a2e82ddd7ca816a5997997 --- /dev/null +++ b/marked/Rel-16/25_series/25222/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6818a971c365b07993b1536dfe61acb63eb72bd96490575003cf5d8c3ab0baa +size 13878 diff --git a/marked/Rel-16/25_series/25222/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-16/25_series/25222/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc307367e6b40e2a02bc98ca2ff2973bbaab281e --- /dev/null +++ b/marked/Rel-16/25_series/25222/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51418dac6f8bc11a21ec9d1471ecb0b3d57d4e40f00cae64aa376e6865ec397c +size 17071 diff --git a/marked/Rel-16/25_series/25222/0fa3b4af7842aaed476a9a6bab544b28_img.jpg b/marked/Rel-16/25_series/25222/0fa3b4af7842aaed476a9a6bab544b28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7699dae1f8be38e6bf6ebb09feb67672c45fd791 --- /dev/null +++ b/marked/Rel-16/25_series/25222/0fa3b4af7842aaed476a9a6bab544b28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f77f0ab88b3a3f4246fb8435870415e0d1bb74e0b5588493d3cf646eb3b08c7 +size 26236 diff --git a/marked/Rel-16/25_series/25222/19f90331494ba1e143d915d8d0061942_img.jpg b/marked/Rel-16/25_series/25222/19f90331494ba1e143d915d8d0061942_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dddea197aaa4edc439314efd5ae21b360c7554a5 --- /dev/null +++ b/marked/Rel-16/25_series/25222/19f90331494ba1e143d915d8d0061942_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad08805631dda1ead2a612e82b947f14cefa6d5f1308022c43510f56a6f505a1 +size 32047 diff --git a/marked/Rel-16/25_series/25222/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25222/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9a1030e6de2446e77a8460410fc0686d5960770 --- /dev/null +++ b/marked/Rel-16/25_series/25222/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e49cafc4e7bec243e8a2c810c881e5949692d9b82f9b799e3ea62156706d3240 +size 140591 diff --git a/marked/Rel-16/25_series/25222/1dd5414c93117a86043e7ae8d3ac1c0b_img.jpg b/marked/Rel-16/25_series/25222/1dd5414c93117a86043e7ae8d3ac1c0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1600ff1ed94b5a3336e37ee720e7dd513a22b32f --- /dev/null +++ b/marked/Rel-16/25_series/25222/1dd5414c93117a86043e7ae8d3ac1c0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00d35f7417dc267d2cf0bbad8a07d6cf905992d6005c3534342424b1983f076d +size 2997 diff --git a/marked/Rel-16/25_series/25222/1dda1ccbaddcb163f7b69e9726bbaff1_img.jpg b/marked/Rel-16/25_series/25222/1dda1ccbaddcb163f7b69e9726bbaff1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23b6e8d7783fc7e3c68ed4c5481737d106dbdde6 --- /dev/null +++ b/marked/Rel-16/25_series/25222/1dda1ccbaddcb163f7b69e9726bbaff1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b4c804eb014502fa1702b061f9b923df8e01718cd62cb83a2249c1c76f6133d +size 4010 diff --git a/marked/Rel-16/25_series/25222/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/25_series/25222/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9abf9618230278faf4a8ebfcb9309f2195d77915 --- /dev/null +++ b/marked/Rel-16/25_series/25222/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c810a9ec6e9f9cdb150df16fa4d9525d5045227d16939d9f288127afbd1f6814 +size 65137 diff --git a/marked/Rel-16/25_series/25222/2e41f0ad7219c40ed9c9f440509165ae_img.jpg b/marked/Rel-16/25_series/25222/2e41f0ad7219c40ed9c9f440509165ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..895fe458b38b562b0d6e9fef7ec9e19e6bb0659c --- /dev/null +++ b/marked/Rel-16/25_series/25222/2e41f0ad7219c40ed9c9f440509165ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e9b2d9a9fa4905af0c1fc5e16ee0087b517b09acd5f548039f39f44ba613cdc +size 4101 diff --git a/marked/Rel-16/25_series/25222/346324c08906e6d9320f632ab916f73e_img.jpg b/marked/Rel-16/25_series/25222/346324c08906e6d9320f632ab916f73e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5924303f042130c4c02096808e3a8185ee9d63fe --- /dev/null +++ b/marked/Rel-16/25_series/25222/346324c08906e6d9320f632ab916f73e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18aab5aa5b9ca49907e7d5e21fb4fd55486b74b28405e817776d4784aaf24542 +size 14172 diff --git a/marked/Rel-16/25_series/25222/4c5f1aeea1c3fa1db11cc4ae0663c832_img.jpg b/marked/Rel-16/25_series/25222/4c5f1aeea1c3fa1db11cc4ae0663c832_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5340057c806ac904dd83b05a88305f4600624b0c --- /dev/null +++ b/marked/Rel-16/25_series/25222/4c5f1aeea1c3fa1db11cc4ae0663c832_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aca88e86332de740a2f1e98c2f05e2f5f24cd4195ba0bde3970fc2d458ddce9e +size 4889 diff --git a/marked/Rel-16/25_series/25222/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-16/25_series/25222/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..189b86227c62d3e055b3b600d3da156f8c3be938 --- /dev/null +++ b/marked/Rel-16/25_series/25222/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:360d52cd3b68285ddf0f03c3135475873dbd142be4a80ef8c34ea1b2056209f4 +size 17001 diff --git a/marked/Rel-16/25_series/25222/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/marked/Rel-16/25_series/25222/5c3dd31372f59e15250f0ab1613ca485_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bea86d38c3de59147cc3402adcb791736fd71f4d --- /dev/null +++ b/marked/Rel-16/25_series/25222/5c3dd31372f59e15250f0ab1613ca485_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6075f39b2a84421c3cbb32235e98591c4cea38d00bdeaf36ea2f3599f5054c96 +size 27533 diff --git a/marked/Rel-16/25_series/25222/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/Rel-16/25_series/25222/5ec3284657e4df0df3653dd61d0ecd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5e1fb88b4d473bc8f43284d3a42fab016ab5fe1 --- /dev/null +++ b/marked/Rel-16/25_series/25222/5ec3284657e4df0df3653dd61d0ecd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bf686d1c9d9f1cfad6dbc8fe34d52d7158437bfb2b0baba10360bd7d5ec7f39 +size 53201 diff --git a/marked/Rel-16/25_series/25222/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/marked/Rel-16/25_series/25222/659a041a7997f9eea79f4e2f3ba265a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbbf09580336f1bf2bbd9c116825a5ced8ef4890 --- /dev/null +++ b/marked/Rel-16/25_series/25222/659a041a7997f9eea79f4e2f3ba265a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1900eb12ea2ec134ccbccf2a083be29be06b09a4b83767a642f2116e7037d55e +size 11277 diff --git a/marked/Rel-16/25_series/25222/69959d0c3f45f3c08c4d85efdd0bf815_img.jpg b/marked/Rel-16/25_series/25222/69959d0c3f45f3c08c4d85efdd0bf815_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43eb88567f7342ca70cf53c99bc5fd329db436a7 --- /dev/null +++ b/marked/Rel-16/25_series/25222/69959d0c3f45f3c08c4d85efdd0bf815_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:940c63538dea1f5c85509b95d09e52d55da03b6c44f0aa28b1589c5328bb6874 +size 6959 diff --git a/marked/Rel-16/25_series/25222/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25222/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ff77c728e6bd5bda38ab9cc0a0263181d3cf0a7 --- /dev/null +++ b/marked/Rel-16/25_series/25222/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d851c550c20792a1e02700d6d5374f68867ff4d544a276904eeffd838c61d57a +size 146040 diff --git a/marked/Rel-16/25_series/25222/86692d82da6655813b5acf58a767a38c_img.jpg b/marked/Rel-16/25_series/25222/86692d82da6655813b5acf58a767a38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3a62b24013b686d0e7203bfc30f9f58cfb355d8 --- /dev/null +++ b/marked/Rel-16/25_series/25222/86692d82da6655813b5acf58a767a38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ebc3dc163bf2ad6a52284bb02793105269304eeb9194dfd231ee81358e530a5 +size 39478 diff --git a/marked/Rel-16/25_series/25222/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-16/25_series/25222/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d09fc54c52c7bc695e1f12e485668d841dae10b --- /dev/null +++ b/marked/Rel-16/25_series/25222/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af67f259719a9c5da083870f6ee8e76b25bf8b1cbe38ed26a11ccc28ace020ba +size 6346 diff --git a/marked/Rel-16/25_series/25222/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/25_series/25222/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b662de5b17ae365b47d7af343b483dbb218b5f0 --- /dev/null +++ b/marked/Rel-16/25_series/25222/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:090ebea2122e21c2b714112238e209e04b6f24e07696add17d056641d779aa6c +size 53627 diff --git a/marked/Rel-16/25_series/25222/9bafc60bf378685e5e246c3ffad7b792_img.jpg b/marked/Rel-16/25_series/25222/9bafc60bf378685e5e246c3ffad7b792_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3732f5e932333af47892c09f5e68f89c223613a6 --- /dev/null +++ b/marked/Rel-16/25_series/25222/9bafc60bf378685e5e246c3ffad7b792_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b70b7af3116102688796c335e5dc896b6ca37bca2ab605229ab03a556ffb00df +size 12153 diff --git a/marked/Rel-16/25_series/25222/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg b/marked/Rel-16/25_series/25222/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adeb4c650adad86008c22666fe872ac23ba31e91 --- /dev/null +++ b/marked/Rel-16/25_series/25222/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a21480d802315f4c269809c9b1c482cc4048e83cf5bfd771e3783ffe9422846a +size 20797 diff --git a/marked/Rel-16/25_series/25222/9dd03da031e134bfc9ecc730dd5f6583_img.jpg b/marked/Rel-16/25_series/25222/9dd03da031e134bfc9ecc730dd5f6583_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983fcd591be4f2f278ef2209878f661d6e530140 --- /dev/null +++ b/marked/Rel-16/25_series/25222/9dd03da031e134bfc9ecc730dd5f6583_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1264f065225b98c5f28772b18d7192a9ece6a9b6dcee8f6c4b0f7b28c3b8b569 +size 56629 diff --git a/marked/Rel-16/25_series/25222/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-16/25_series/25222/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..075033facb556b2ecd684d5579516206734b145b --- /dev/null +++ b/marked/Rel-16/25_series/25222/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f908eeef62892b399d54d36bad00212b094741fb8c5e463237294c8a5e5dcd +size 36633 diff --git a/marked/Rel-16/25_series/25222/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/25_series/25222/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d656cf4f4e2cfc2d97b456d054269f34a95c4d0 --- /dev/null +++ b/marked/Rel-16/25_series/25222/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffb4433ae64f6fdfb5e88609a34e58cbc758daeef9361f13aa8ff94de86326da +size 82959 diff --git a/marked/Rel-16/25_series/25222/a97f7c055c1fd8d79037d02b3fc38496_img.jpg b/marked/Rel-16/25_series/25222/a97f7c055c1fd8d79037d02b3fc38496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e374c353a73e15255023bb824d221a425d3c90b --- /dev/null +++ b/marked/Rel-16/25_series/25222/a97f7c055c1fd8d79037d02b3fc38496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f35f0a61acfbd1a5538014c5c5a3aa25c0025a006cc5bcaa2db710cb88efa8d +size 30285 diff --git a/marked/Rel-16/25_series/25222/aa5b4fe5ea9a65d15789baa3e8dc1565_img.jpg b/marked/Rel-16/25_series/25222/aa5b4fe5ea9a65d15789baa3e8dc1565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfa6ae8f5f494a7a82592cbe7c17b409d4571928 --- /dev/null +++ b/marked/Rel-16/25_series/25222/aa5b4fe5ea9a65d15789baa3e8dc1565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:235797f36c9190730230d4c38577b4519b111ec2b00968e7f4ae09e0162a8f44 +size 4502 diff --git a/marked/Rel-16/25_series/25222/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-16/25_series/25222/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f5a25e6ecebfd1f9c5c185ed3ed838e1cf3d76c --- /dev/null +++ b/marked/Rel-16/25_series/25222/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b30ed72f5f146e9e1768c69ccca6b3c75e4e77a2af30f7f6a0ce0e452674b5 +size 13736 diff --git a/marked/Rel-16/25_series/25222/bc3d1c04d342094c893d5064974c9ee7_img.jpg b/marked/Rel-16/25_series/25222/bc3d1c04d342094c893d5064974c9ee7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dff2a6fbbb49e0817f6b63c0e08b309e79408c5e --- /dev/null +++ b/marked/Rel-16/25_series/25222/bc3d1c04d342094c893d5064974c9ee7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bc811e094047e142e58b072257816a674405cbe2ae17b9150e2da99ac9fc037 +size 9878 diff --git a/marked/Rel-16/25_series/25222/c32236ab37ba84aaaefca890cf6deab6_img.jpg b/marked/Rel-16/25_series/25222/c32236ab37ba84aaaefca890cf6deab6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a209d977a51d268de061da8f92e254c329beb06 --- /dev/null +++ b/marked/Rel-16/25_series/25222/c32236ab37ba84aaaefca890cf6deab6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9bd1cf1028a4054091d8adc6d9a736e86f9e4dfc9667d35f8be0ffc1b950bcb +size 6595 diff --git a/marked/Rel-16/25_series/25222/c701a84b904fedcdb0316835eafbd39f_img.jpg b/marked/Rel-16/25_series/25222/c701a84b904fedcdb0316835eafbd39f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f066a4e53c3e4e2862de498dabb9fccb1e4352dc --- /dev/null +++ b/marked/Rel-16/25_series/25222/c701a84b904fedcdb0316835eafbd39f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a10d60ceb4fe6d1d65412e98f4ee26f295e4c5e4a30e3a70ab7eada46f88faf +size 24349 diff --git a/marked/Rel-16/25_series/25222/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg b/marked/Rel-16/25_series/25222/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75c97d77888624283f60a302fb9bdfe550079aa5 --- /dev/null +++ b/marked/Rel-16/25_series/25222/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e1cb2668b86e5de061daca1c65f79dd3ce7f175bdda25540669eae2caa9b93c +size 30672 diff --git a/marked/Rel-16/25_series/25222/d62cac468ea25bcb00a23015ede34537_img.jpg b/marked/Rel-16/25_series/25222/d62cac468ea25bcb00a23015ede34537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efae68253b3c966af1dbd36b67b6b7acd75f61e4 --- /dev/null +++ b/marked/Rel-16/25_series/25222/d62cac468ea25bcb00a23015ede34537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1d1c288b094dedda576ac1ec4b3897c4383ac71e829f9d8291c5b8e639cc466 +size 4516 diff --git a/marked/Rel-16/25_series/25222/da434ee158d8bd56122f990b91dc17ba_img.jpg b/marked/Rel-16/25_series/25222/da434ee158d8bd56122f990b91dc17ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb42520d9936caa5840f6363cdfeecf44a079ec6 --- /dev/null +++ b/marked/Rel-16/25_series/25222/da434ee158d8bd56122f990b91dc17ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee2de8e21c37cff002a14898a20cdce4fe4be9a7ffab9fddbc5fa1abf15b8a53 +size 38798 diff --git a/marked/Rel-16/25_series/25222/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/25_series/25222/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a08fa787e1d60a3582797a0cf0cbf88dd55e93c --- /dev/null +++ b/marked/Rel-16/25_series/25222/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00af5d42c22882571e237761d5ec3fc42cb4b025a3780c18fb3f13cc32c4e13 +size 85858 diff --git a/marked/Rel-16/25_series/25222/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/marked/Rel-16/25_series/25222/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac170ae4b8cb6d8e8fd494ddae0b914df902d17d --- /dev/null +++ b/marked/Rel-16/25_series/25222/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d08ab9356fbd653f2515d6a31f03c673277c79aa257d0d4a933877d2cdea2a62 +size 55031 diff --git a/marked/Rel-16/25_series/25222/e694eeb983c07b3dd631358292db6af1_img.jpg b/marked/Rel-16/25_series/25222/e694eeb983c07b3dd631358292db6af1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66875b9b7da67f61a3622a9580abc3731588d379 --- /dev/null +++ b/marked/Rel-16/25_series/25222/e694eeb983c07b3dd631358292db6af1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa27e4f3f29d9b8e52bdebe9ae78f3152eb2095821b73aa457e67b9384fd5ee +size 26451 diff --git a/marked/Rel-16/25_series/25222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d69bcee8405bb3e12487da3df70567494cf10a1 --- /dev/null +++ b/marked/Rel-16/25_series/25222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b6995076b062692486f774fdff7d2350758ed2c4b45a94a2b1fd098738f65ae +size 36780 diff --git a/marked/Rel-16/25_series/25222/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg b/marked/Rel-16/25_series/25222/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c94a70f8e5999c710cf5249491cc508b0701bf02 --- /dev/null +++ b/marked/Rel-16/25_series/25222/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d91e71b4bc9e72d95d5afd4921035550351c76a0468f0a2f738ff1f66786ac89 +size 13090 diff --git a/marked/Rel-16/25_series/25222/f85901c04910147b1057081deab67741_img.jpg b/marked/Rel-16/25_series/25222/f85901c04910147b1057081deab67741_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01f28cd28dd7a332b57371d3bbd75e9dc90e7bce --- /dev/null +++ b/marked/Rel-16/25_series/25222/f85901c04910147b1057081deab67741_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e55553bac87031d7c1a04732fabf619d8df423bac29eda5e0c214d44c09d351d +size 6928 diff --git a/marked/Rel-16/25_series/25222/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/25_series/25222/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e29d38c7c2e15d6bf546f7ac4e7242b93b860648 --- /dev/null +++ b/marked/Rel-16/25_series/25222/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04c2e5578b1f37c2c8e2936964c79505e4939ff583c0d85b73812d3ee7a16f0e +size 29295 diff --git a/marked/Rel-16/25_series/25222/raw.md b/marked/Rel-16/25_series/25222/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00c5e02fc1af62082215bbcb4a54f00531a2985f --- /dev/null +++ b/marked/Rel-16/25_series/25222/raw.md @@ -0,0 +1,5922 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 10 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions, symbols and abbreviations..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations..... | 12 | +| 4 Multiplexing, channel coding and interleaving for the 1.28 Mcps, 3.84 Mcps and 7.68 Mcps options..... | 14 | +| 4.1 General..... | 14 | +| 4.2 General coding/multiplexing of TrCHs..... | 14 | +| 4.2.1 CRC attachment..... | 18 | +| 4.2.1.1 CRC calculation..... | 18 | +| 4.2.1.2 Relation between input and output of the CRC attachment block..... | 18 | +| 4.2.2 Transport block concatenation and code block segmentation..... | 19 | +| 4.2.2.1 Concatenation of transport blocks..... | 19 | +| 4.2.2.2 Code block segmentation..... | 19 | +| 4.2.3 Channel coding..... | 20 | +| 4.2.3.1 Convolutional coding..... | 21 | +| 4.2.3.2 Turbo coding..... | 22 | +| 4.2.3.2.1 Turbo coder..... | 22 | +| 4.2.3.2.2 Trellis termination for Turbo coder..... | 23 | +| 4.2.3.2.3 Turbo code internal interleaver..... | 23 | +| 4.2.3.2.3.1 Bits-input to rectangular matrix with padding..... | 24 | +| 4.2.3.3 Concatenation of encoded blocks..... | 27 | +| 4.2.4 Radio frame size equalisation..... | 27 | +| 4.2.5 1st interleaving..... | 27 | +| 4.2.5.1 Relation between input and output of 1 st interleaving..... | 28 | +| 4.2.6 Radio frame segmentation..... | 28 | +| 4.2.7 Rate matching..... | 29 | +| 4.2.7.1 Determination of rate matching parameters..... | 30 | +| 4.2.7.1.1 Uncoded and convolutionally encoded TrCHs..... | 31 | +| 4.2.7.1.2 Turbo encoded TrCHs..... | 31 | +| 4.2.7.2 Bit separation and collection for rate matching..... | 32 | +| 4.2.7.2.1 Bit separation..... | 34 | +| 4.2.7.2.2 Bit collection..... | 35 | +| 4.2.7.3 Rate matching pattern determination..... | 35 | +| 4.2.8 TrCH multiplexing..... | 36 | +| 4.2.9 Bit Scrambling..... | 37 | +| 4.2.10 Physical channel segmentation..... | 37 | +| 4.2.11 2nd interleaving..... | 37 | +| 4.2.11.1 Frame related 2nd interleaving..... | 38 | +| 4.2.11.2 Timeslot related 2 nd interleaving..... | 39 | +| 4.2.11A Sub-frame segmentation for the 1.28 Mcps option..... | 41 | +| 4.2.12 Physical channel mapping..... | 41 | +| 4.2.12.1 Physical channel mapping for the 3.84 Mcps and 7.68 Mcps options..... | 41 | +| 4.2.12.1.1 Mapping scheme..... | 42 | +| 4.2.12.2 Physical channel mapping for the 1.28 Mcps option..... | 43 | +| 4.2.12.2.1 Mapping scheme..... | 43 | +| 4.2.13 Multiplexing of different transport channels onto one CCTrCH, and mapping of one CCTrCH onto physical channels..... | 44 | +| 4.2.13.1 Allowed CCTrCH combinations for one UE..... | 45 | +| 4.2.13.1.1 Allowed CCTrCH combinations on the uplink..... | 45 | +| 4.2.13.1.2 Allowed CCTrCH combinations on the downlink..... | 45 | +| 4.2.14 Transport format detection..... | 45 | +| 4.2.14.1 Blind transport format detection..... | 45 | + +| | | | +|------------|---------------------------------------------------------------------------------|----| +| 4.2.14.2 | Explicit transport format detection based on TFCI..... | 45 | +| 4.2.14.2.1 | Transport Format Combination Indicator (TFCI)..... | 45 | +| 4.3 | Coding for layer 1 control for the 3.84 Mcps and 7.68Mcps TDD options..... | 46 | +| 4.3.1 | Coding of transport format combination indicator (TFCI)..... | 46 | +| 4.3.1.1 | Coding of long TFCI lengths..... | 46 | +| 4.3.1.2 | Coding of short TFCI lengths..... | 47 | +| 4.3.1.2.1 | Coding very short TFCIs by repetition..... | 47 | +| 4.3.1.2.2 | Coding short TFCIs using bi-orthogonal codes..... | 47 | +| 4.3.1.3 | Mapping of TFCI code word..... | 48 | +| 4.3.2 | Coding and Bit Scrambling of the Paging Indicator..... | 48 | +| 4.3.3 | Coding and Bit Scrambling of the MBMS Notification Indicator..... | 49 | +| 4.4 | Coding for layer 1 control for the 1.28 Mcps option..... | 49 | +| 4.4.1 | Coding of transport format combination indicator (TFCI) for QPSK and 16QAM..... | 49 | +| 4.4.1.1 | Mapping of TFCI code word..... | 49 | +| 4.4.2 | Coding of transport format combination indicator (TFCI) for 8PSK..... | 51 | +| 4.4.2.1 | Coding of long TFCI lengths..... | 51 | +| 4.4.2.2 | Coding of short TFCI lengths..... | 53 | +| 4.4.2.2.1 | Coding very short TFCIs by repetition..... | 53 | +| 4.4.2.2.2 | Coding short TFCIs using bi-orthogonal codes..... | 53 | +| 4.4.2.3 | Mapping of TFCI code word..... | 54 | +| 4.4.3 | Coding and Bit Scrambling of the Paging Indicator..... | 55 | +| 4.4.4 | Coding of the Fast Physical Access Channel (FPACH) information bits..... | 55 | +| 4.4.5 | Coding and Bit Scrambling of the MBMS Notification Indicator..... | 56 | +| 4.4.6 | Coding of PLCCH..... | 56 | +| 4.5 | Coding for HS-DSCH..... | 57 | +| 4.5.1 | CRC attachment for HS-DSCH..... | 59 | +| 4.5.2 | Code block segmentation for HS-DSCH..... | 59 | +| 4.5.3 | Channel coding for HS-DSCH..... | 60 | +| 4.5.4 | Hybrid ARQ for HS-DSCH..... | 60 | +| 4.5.4.1 | HARQ bit separation..... | 60 | +| 4.5.4.2 | HARQ First Rate Matching Stage..... | 60 | +| 4.5.4.3 | HARQ Second Rate Matching Stage..... | 61 | +| 4.5.4.4 | HARQ bit collection..... | 62 | +| 4.5.5 | Bit scrambling..... | 63 | +| 4.5.6 | Interleaving for HS-DSCH..... | 63 | +| 4.5.7 | Constellation re-arrangement for 16 QAM and 64 QAM..... | 64 | +| 4.5.8 | Physical channel mapping for HS-DSCH..... | 65 | +| 4.6 | Coding/Multiplexing for HS-SCCH..... | 67 | +| 4.6.1 | HS-SCCH information field mapping..... | 69 | +| 4.6.1.1 | Channelisation code set information mapping..... | 69 | +| 4.6.1.1.1 | 1.28Mcps TDD and 3.84Mcps TDD..... | 69 | +| 4.6.1.1.2 | 7.68Mcps TDD..... | 70 | +| 4.6.1.2 | Timeslot information mapping..... | 71 | +| 4.6.1.2.1 | 1.28 Mcps TDD..... | 71 | +| 4.6.1.2.2 | 3.84 Mcps TDD and 7.68Mcps TDD..... | 71 | +| 4.6.1.3 | Modulation scheme information mapping..... | 72 | +| 4.6.1.4 | Redundancy and constellation version information mapping..... | 73 | +| 4.6.1.5 | HS-SCCH cyclic sequence number..... | 73 | +| 4.6.1.6 | UE identity..... | 73 | +| 4.6.1.7 | HARQ process identifier mapping..... | 73 | +| 4.6.1.8 | Transport block size index mapping..... | 73 | +| 4.6.2 | Multiplexing of HS-SCCH information..... | 73 | +| 4.6.3 | CRC attachment for HS-SCCH..... | 74 | +| 4.6.4 | Channel coding for HS-SCCH..... | 74 | +| 4.6.5 | Rate matching for HS-SCCH..... | 74 | +| 4.6.6 | Interleaving for HS-SCCH..... | 74 | +| 4.6.7 | Physical Channel Segmentation for HS-SCCH..... | 74 | +| 4.6.8 | Physical channel mapping for HS-SCCH..... | 74 | +| 4.6A | Coding/Multiplexing for HS-SCCH orders type A..... | 75 | +| 4.6A.1 | HS-SCCH orders type A information field mapping..... | 75 | +| 4.6A.1.1 | Order type mapping..... | 75 | + +| | | | +|-----------|------------------------------------------------------------------|----| +| 4.6A.1.2 | UE identity mapping..... | 75 | +| 4.6B | Coding/Multiplexing for HS-SCCH type 2 (1.28 Mcps TDD only)..... | 75 | +| 4.6B.1 | HS-SCCH type 2 information field mapping..... | 77 | +| 4.6B.1.1 | Type flag 1 mapping..... | 77 | +| 4.6B.1.2 | Resource repetition pattern index mapping..... | 77 | +| 4.6B.1.3 | Type flag 2 mapping..... | 78 | +| 4.6B.1.4 | Transport block size index mapping..... | 78 | +| 4.6B.1.5 | Timeslot information mapping..... | 78 | +| 4.6B.1.6 | Channelisation code set information mapping..... | 78 | +| 4.6B.1.7 | Modulation scheme information mapping..... | 79 | +| 4.6B.1.8 | HS-SICH indicator mapping..... | 79 | +| 4.6B.1.9 | HS-SCCH cyclic sequence number..... | 79 | +| 4.6B.1.10 | UE identity..... | 79 | +| 4.6B.2 | Multiplexing of HS-SCCH type 2 information..... | 79 | +| 4.6B.3 | CRC attachment for HS-SCCH type 2..... | 80 | +| 4.6B.4 | Channel coding for HS-SCCH type 2..... | 80 | +| 4.6B.5 | Rate matching for HS-SCCH type 2..... | 80 | +| 4.6B.6 | Interleaving for HS-SCCH type 2..... | 80 | +| 4.6B.7 | Physical Channel Segmentation for HS-SCCH type 2..... | 80 | +| 4.6B.8 | Physical channel mapping for HS-SCCH type 2..... | 80 | +| 4.6C | Coding/Multiplexing for HS-SCCH type 3 (1.28 Mcps TDD only)..... | 80 | +| 4.6C.1 | HS-SCCH type 3 information field mapping..... | 82 | +| 4.6C.1.1 | Type flag 1 mapping..... | 82 | +| 4.6C.1.2 | Resource repetition pattern index mapping..... | 82 | +| 4.6C.1.3 | Type flag 2 mapping..... | 82 | +| 4.6C.1.4 | Transport block size index mapping..... | 82 | +| 4.6C.1.5 | Timeslot information mapping..... | 83 | +| 4.6C.1.6 | Channelisation code set information mapping..... | 83 | +| 4.6C.1.7 | Modulation scheme information mapping..... | 83 | +| 4.6C.1.8 | Redundancy version information mapping..... | 83 | +| 4.6C.1.9 | Pointer to the previous transmission mapping..... | 83 | +| 4.6C.1.10 | HS-SCCH cyclic sequence number..... | 83 | +| 4.6C.1.11 | UE identity..... | 83 | +| 4.6C.2 | Multiplexing of HS-SCCH type 3 information..... | 83 | +| 4.6C.3 | CRC attachment for HS-SCCH type 3..... | 84 | +| 4.6C.4 | Channel coding for HS-SCCH type 3..... | 84 | +| 4.6C.5 | Rate matching for HS-SCCH type 3..... | 84 | +| 4.6C.6 | Interleaving for HS-SCCH type 3..... | 84 | +| 4.6C.7 | Physical Channel Segmentation for HS-SCCH type 3..... | 84 | +| 4.6C.8 | Physical channel mapping for HS-SCCH type 3..... | 84 | +| 4.6D | Coding/Multiplexing for HS-SCCH type 4 (1.28 Mcps TDD only)..... | 85 | +| 4.6D.1 | HS-SCCH type 4 information field mapping..... | 86 | +| 4.6D.1.1 | Type flag 1 mapping..... | 86 | +| 4.6D.1.2 | Type flag 2 mapping..... | 86 | +| 4.6D.1.3 | Channelisation code set information mapping..... | 86 | +| 4.6D.1.4 | Timeslot information mapping..... | 87 | +| 4.6D.1.5 | Modulation scheme information mapping..... | 87 | +| 4.6D.1.6 | Transport block size index mapping..... | 87 | +| 4.6D.1.7 | HARQ process identifier mapping..... | 87 | +| 4.6D.1.8 | Redundancy version information mapping..... | 87 | +| 4.6D.1.9 | HS-SCCH cyclic sequence number..... | 87 | +| 4.6D.1.10 | UE identity..... | 88 | +| 4.6D.1.11 | Midamble allocation scheme flag..... | 88 | +| 4.6D.2 | Multiplexing of HS-SCCH type 4 information..... | 88 | +| 4.6D.3 | CRC attachment for HS-SCCH type 4..... | 88 | +| 4.6D.4 | Channel coding for HS-SCCH type 4..... | 88 | +| 4.6D.5 | Rate matching for HS-SCCH type 4..... | 88 | +| 4.6D.6 | Interleaving for HS-SCCH type 4..... | 89 | +| 4.6D.7 | Physical Channel Segmentation for HS-SCCH type 4..... | 89 | +| 4.6D.8 | Physical channel mapping for HS-SCCH type 4..... | 89 | +| 4.6E | Coding/Multiplexing for HS-SCCH type 5 (1.28 Mcps TDD only)..... | 89 | + +| | | | +|-----------|------------------------------------------------------------------|-----| +| 4.6E.1 | HS-SCCH type 5 information field mapping..... | 90 | +| 4.6E.1.1 | Type flag 1 mapping..... | 90 | +| 4.6E.1.2 | Type flag 2 mapping..... | 90 | +| 4.6E.1.3 | Timeslot information mapping..... | 90 | +| 4.6E.1.4 | Modulation scheme information mapping..... | 90 | +| 4.6E.1.5 | Transport block size offset information mapping..... | 91 | +| 4.6E.1.6 | Transport block size index mapping..... | 91 | +| 4.6E.1.7 | HARQ process identifier mapping..... | 91 | +| 4.6E.1.8 | Redundancy version information mapping..... | 91 | +| 4.6E.1.9 | HS-SCCH cyclic sequence number..... | 91 | +| 4.6E.1.10 | UE identity..... | 91 | +| 4.6E.2 | Multiplexing of HS-SCCH type 5 information..... | 91 | +| 4.6E.3 | CRC attachment for HS-SCCH type 5..... | 92 | +| 4.6E.4 | Channel coding for HS-SCCH type 5..... | 92 | +| 4.6E.5 | Rate matching for HS-SCCH type 5..... | 92 | +| 4.6E.6 | Interleaving for HS-SCCH type 5..... | 92 | +| 4.6E.7 | Physical Channel Segmentation for HS-SCCH type 5..... | 92 | +| 4.6E.8 | Physical channel mapping for HS-SCCH type 5..... | 92 | +| 4.6F | Coding/Multiplexing for HS-SCCH type 6 (1.28 Mcps TDD only)..... | 92 | +| 4.6F.1 | HS-SCCH type 6 information field mapping..... | 94 | +| 4.6F.1.1 | Type flag mapping..... | 94 | +| 4.6F.1.2 | Channelisation code set information mapping..... | 94 | +| 4.6F.1.3 | Timeslot information mapping..... | 94 | +| 4.6F.1.4 | Modulation scheme information mapping..... | 94 | +| 4.6F.1.5 | Resource repetition pattern index mapping..... | 94 | +| 4.6F.1.6 | Transport block size index mapping..... | 95 | +| 4.6F.1.7 | HS-SICH indicator mapping..... | 95 | +| 4.6F.1.8 | HS-SCCH cyclic sequence number..... | 95 | +| 4.6F.1.9 | UE identity..... | 95 | +| 4.6F.2 | Multiplexing of HS-SCCH type 6 information..... | 95 | +| 4.6F.3 | CRC attachment for HS-SCCH type 6..... | 95 | +| 4.6F.4 | Channel coding for HS-SCCH type 6..... | 95 | +| 4.6F.5 | Rate matching for HS-SCCH type 6..... | 96 | +| 4.6F.6 | Interleaving for HS-SCCH type 6..... | 96 | +| 4.6F.7 | Physical Channel Segmentation for HS-SCCH type 6..... | 96 | +| 4.6F.8 | Physical channel mapping for HS-SCCH type 6..... | 96 | +| 4.6G | Coding/Multiplexing for HS-SCCH type 7 (1.28 Mcps TDD only)..... | 96 | +| 4.6G.1 | HS-SCCH type 7 information field mapping..... | 97 | +| 4.6G.1.1 | Type flag mapping..... | 97 | +| 4.6G.1.2 | Channelisation code set information mapping..... | 97 | +| 4.6G.1.3 | Timeslot information mapping..... | 97 | +| 4.6G.1.4 | Modulation scheme information mapping..... | 97 | +| 4.6G.1.5 | Resource repetition pattern index mapping..... | 98 | +| 4.6G.1.6 | Transport block size index mapping..... | 98 | +| 4.6G.1.7 | Redundancy version information mapping..... | 98 | +| 4.6G.1.8 | Pointer to the previous transmission mapping..... | 98 | +| 4.6G.1.9 | HS-SCCH cyclic sequence number..... | 98 | +| 4.6G.1.10 | UE identity..... | 98 | +| 4.6G.2 | Multiplexing of HS-SCCH type 7 information..... | 98 | +| 4.6G.3 | CRC attachment for HS-SCCH type 7..... | 98 | +| 4.6G.4 | Channel coding for HS-SCCH type 7..... | 99 | +| 4.6G.5 | Rate matching for HS-SCCH type 7..... | 99 | +| 4.6G.6 | Interleaving for HS-SCCH type 7..... | 99 | +| 4.6G.7 | Physical Channel Segmentation for HS-SCCH type 7..... | 99 | +| 4.6G.8 | Physical channel mapping for HS-SCCH type 7..... | 99 | +| 4.6H | Coding/Multiplexing for HS-SCCH type 8 (1.28 Mcps TDD only)..... | 99 | +| 4.6H.1 | HS-SCCH type 8 information field mapping..... | 100 | +| 4.6H.1.1 | Channelisation code set information mapping..... | 100 | +| 4.6H.1.2 | Transport block size index mapping..... | 101 | +| 4.6H.1.3 | Modulation scheme information mapping..... | 102 | +| 4.6H.1.4 | Timeslot information mapping..... | 102 | + +| | | | +|-----------|------------------------------------------------------------------------|-----| +| 4.6H.1.5 | Redundancy version information mapping..... | 102 | +| 4.6H.1.6 | Type flag mapping..... | 102 | +| 4.6H.1.7 | Field flag mapping..... | 102 | +| 4.6H.1.8 | Special Information mapping..... | 102 | +| 4.6H.1.9 | HARQ process identifier mapping..... | 102 | +| 4.6H.1.10 | HS-SCCH cyclic sequence number..... | 102 | +| 4.6H.1.11 | UE identity..... | 102 | +| 4.6H.2 | Multiplexing of HS-SCCH type 8 information..... | 102 | +| 4.6H.3 | CRC attachment for HS-SCCH type 8..... | 103 | +| 4.6H.4 | Channel coding for HS-SCCH type 8..... | 103 | +| 4.6H.5 | Rate matching for HS-SCCH type 8..... | 103 | +| 4.6H.6 | Interleaving for HS-SCCH type 8..... | 103 | +| 4.6H.7 | Physical Channel Segmentation for HS-SCCH type 8..... | 103 | +| 4.6H.8 | Physical channel mapping for HS-SCCH type 8..... | 103 | +| 4.6I | Coding/Multiplexing for HS-SCCH type 9 (1.28 Mcps TDD only)..... | 104 | +| 4.6I.1 | HS-SCCH type 9 information field mapping..... | 105 | +| 4.6I.1.1 | Channelisation code set information mapping..... | 105 | +| 4.6I.1.2 | Transport block size offset information mapping..... | 106 | +| 4.6I.1.3 | Modulation scheme information mapping..... | 106 | +| 4.6I.1.4 | Timeslot information mapping..... | 106 | +| 4.6I.1.5 | Redundancy version information mapping..... | 106 | +| 4.6I.1.6 | HARQ process identifier mapping..... | 106 | +| 4.6I.1.9 | HS-SCCH cyclic sequence number..... | 106 | +| 4.6I.1.10 | UE identity..... | 106 | +| 4.6I.2 | Multiplexing of HS-SCCH type 9 information..... | 106 | +| 4.6I.3 | CRC attachment for HS-SCCH type 9..... | 107 | +| 4.6I.4 | Channel coding for HS-SCCH type 9..... | 107 | +| 4.6I.5 | Rate matching for HS-SCCH type 9..... | 107 | +| 4.6I.6 | Interleaving for HS-SCCH type 9..... | 107 | +| 4.6I.7 | Physical Channel Segmentation for HS-SCCH type 9..... | 107 | +| 4.6I.8 | Physical channel mapping for HS-SCCH type 9..... | 107 | +| 4.6J | Coding/Multiplexing for HS-SCCH orders type B (1.28Mcps TDD only)..... | 107 | +| 4.6J.1 | HS-SCCH orders type B information field mapping..... | 108 | +| 4.6J.1.1 | Order type mapping..... | 108 | +| 4.6J.1.2 | UE identity mapping..... | 108 | +| 4.7 | Coding for HS-SICH..... | 108 | +| 4.7.1 | HS-SICH information field mapping..... | 109 | +| 4.7.1.1 | RMF information mapping..... | 109 | +| 4.7.1.2 | RTBS information mapping..... | 109 | +| 4.7.1.3 | ACK/NACK information mapping..... | 109 | +| 4.7.2 | Coding for HS-SICH..... | 110 | +| 4.7.2.1 | Field Coding of ACK/NACK..... | 110 | +| 4.7.2.2 | Field Coding of CQI..... | 110 | +| 4.7.2.2.1 | Field Coding of CQI for 1.28 Mcps TDD..... | 110 | +| 4.7.2.2.2 | Field Coding of CQI for 3.84 Mcps TDD and 7.68Mcps TDD..... | 111 | +| 4.7.3 | Multiplexing of HS-SICH information fields..... | 111 | +| 4.7.4 | Interleaver for HS-SICH..... | 111 | +| 4.7.5 | Physical channel mapping for HS-SICH..... | 111 | +| 4.7A | Coding for HS-SICH type 2 (1.28 Mcps TDD only)..... | 111 | +| 4.7A.1 | HS-SICH type 2 information field mapping..... | 112 | +| 4.7A.1.1 | RMF information mapping..... | 112 | +| 4.7A.1.2 | RTBS information mapping..... | 112 | +| 4.7A.1.3 | ACK/NACK information mapping..... | 113 | +| 4.7A.2 | Coding for HS-SICH type 2..... | 113 | +| 4.7A.2.1 | Field Coding of ACK/NACK..... | 113 | +| 4.7A.2.2 | Field Coding of CQI..... | 113 | +| 4.7A.3 | Multiplexing of HS-SICH type 2 information fields..... | 113 | +| 4.7A.4 | Interleaver for HS-SICH type 2..... | 114 | +| 4.7A.5 | Physical channel mapping for HS-SICH type 2..... | 114 | +| 4.8 | Coding for E-DCH..... | 114 | +| 4.8.1 | CRC attachment for E-DCH..... | 115 | + +| | | | +|-----------|----------------------------------------------------------------------|-----| +| 4.8.2 | Code block segmentation for E-DCH..... | 115 | +| 4.8.3 | Channel coding for E-DCH..... | 116 | +| 4.8.4 | Physical layer HARQ functionality and rate matching for E-DCH..... | 116 | +| 4.8.4.1 | Determination of SF, modulation and number of physical channels..... | 116 | +| 4.8.4.2 | HARQ bit separation..... | 116 | +| 4.8.4.3 | HARQ Rate Matching Stage..... | 116 | +| 4.8.4.4 | HARQ bit collection..... | 117 | +| 4.8.5 | Bit scrambling..... | 117 | +| 4.8.6 | Interleaving for E-DCH..... | 117 | +| 4.8.7 | Constellation re-arrangement for 16 QAM..... | 117 | +| 4.8.8 | Physical channel mapping for E-DCH..... | 117 | +| 4.9 | Coding for E-UCCH..... | 118 | +| 4.9.1 | Coding for E-UCCH for the 3.84Mcps and 7.68Mcps TDD options..... | 118 | +| 4.9.1.1 | Overview..... | 118 | +| 4.9.1.2 | E-UCCH part 1..... | 119 | +| 4.9.1.2.1 | Information field mapping of E-TFCI..... | 119 | +| 4.9.1.2.2 | Channel coding for E-UCCH part 1..... | 119 | +| 4.9.1.2.3 | Physical channel mapping for E-UCCH part 1..... | 119 | +| 4.9.1.3 | E-UCCH part 2..... | 119 | +| 4.9.1.3.1 | Information field mapping of retransmission sequence number..... | 119 | +| 4.9.1.3.2 | Information field mapping of HARQ process ID..... | 119 | +| 4.9.1.3.3 | Multiplexing of E-UCCH part 2 information..... | 120 | +| 4.9.1.3.4 | Channel coding for E-UCCH part 2..... | 120 | +| 4.9.1.3.5 | Physical channel mapping for E-UCCH part 2..... | 120 | +| 4.9.2 | Coding for E-UCCH for the 1.28Mcps TDD option..... | 120 | +| 4.9.2.1 | E-UCCH information field mapping..... | 121 | +| 4.9.2.1.1 | Information field mapping of E-TFCI..... | 121 | +| 4.9.2.1.2 | RSN information mapping..... | 121 | +| 4.9.2.1.3 | HARQ information mapping..... | 122 | +| 4.9.2.2 | Multiplexing for E-UCCH..... | 122 | +| 4.9.2.3 | Coding for E-UCCH..... | 122 | +| 4.9.2.4 | Physical channel mapping for E-UCCH..... | 123 | +| 4.10 | Coding for E-AGCH..... | 123 | +| 4.10.1 | Information Field Mapping..... | 124 | +| 4.10.1.1 | Mapping of the Absolute Grant (Power) Value..... | 124 | +| 4.10.1.2 | Mapping of the Code Resource Related Information..... | 126 | +| 4.10.1.3 | Mapping of the Timeslot Resource Related Information..... | 127 | +| 4.10.1.4 | Mapping of the E-AGCH Cyclic Sequence Number (ECSN)..... | 127 | +| 4.10.1.5 | Mapping of the Resource Duration Indicator..... | 127 | +| 4.10.1.6 | Mapping of the E-HICH Indicator (1.28Mcps option only)..... | 128 | +| 4.10.1.7 | Mapping of the E-UCCH Number Indicator (1.28Mcps option only)..... | 128 | +| 4.10.2 | Field Multiplexing..... | 128 | +| 4.10.3 | CRC attachment..... | 129 | +| 4.10.4 | Channel Coding..... | 129 | +| 4.10.5 | Rate Matching..... | 129 | +| 4.10.6 | Interleaving..... | 129 | +| 4.10.7 | Physical Channel Segmentation..... | 129 | +| 4.10.8 | Physical Channel Mapping..... | 129 | +| 4.10A | Coding for E-AGCH type 2 (1.28Mcps TDD only)..... | 129 | +| 4.10A.1 | E-AGCH type 2 Information Field Mapping..... | 131 | +| 4.10A.1.1 | Mapping of the Absolute Grant (Power) Value..... | 131 | +| 4.10A.1.2 | Mapping of the Code Resource Related Information..... | 131 | +| 4.10A.1.3 | Mapping of the Timeslot Resource Related Information..... | 131 | +| 4.10A.1.4 | Mapping of the E-AGCH Cyclic Sequence Number (ECSN)..... | 131 | +| 4.10A.1.5 | Mapping of the Field Flag..... | 131 | +| 4.10A.1.6 | Mapping of the Special Information 1..... | 131 | +| 4.10A.1.7 | Mapping of the Special Information 2..... | 132 | +| 4.10A.1.8 | Mapping of the E-UCCH Number Indicator..... | 132 | +| 4.10A.2 | Field Multiplexing of E-AGCH type 2..... | 132 | +| 4.10A.3 | CRC attachment for E-AGCH type 2..... | 133 | +| 4.10A.4 | Channel Coding for E-AGCH type 2..... | 133 | + +| | | | +|------------------------|--------------------------------------------------------------------------------------------------------|-----| +| 4.10A.5 | Rate Matching for E-AGCH type 2..... | 133 | +| 4.10A.6 | Interleaving for E-AGCH type 2..... | 133 | +| 4.10A.7 | Physical Channel Segmentation for E-AGCH type 2..... | 133 | +| 4.10A.8 | Physical Channel Mapping for E-AGCH type 2..... | 133 | +| 4.10B | Coding for E-AGCH orders..... | 133 | +| 4.10B.1 | E-AGCH orders information field mapping..... | 133 | +| 4.10B.1.1 | Order type mapping..... | 133 | +| 4.10B.1.2 | UE identity mapping..... | 134 | +| 4.11 | Coding for E-HICH ACK/NACK..... | 134 | +| 4.11.1 | Coding for E-HICH ACK/NACK for the 3.84Mcps and 7.68Mcps options..... | 134 | +| 4.11.1.1 | Overview..... | 134 | +| 4.11.1.2 | Coding of the HARQ acknowledgement indicator..... | 134 | +| 4.11.1.3 | Bit scrambling of the E-HICH..... | 136 | +| 4.11.1.4 | Physical channel mapping of the E-HICH..... | 136 | +| 4.11.2 | Coding for E-HICH for the 1.28Mcps option only..... | 136 | +| 4.11.2.1 | Overview..... | 136 | +| 4.11.2.2 | Coding of the HARQ acknowledgement indicator and TPC/SS..... | 137 | +| 4.11.2.3 | Bit scrambling and Physical channel mapping of the E-HICH..... | 139 | +| 4.12 | Coding for E-RUCCH..... | 139 | +| 4.12.1 | CRC attachment for E-RUCCH..... | 140 | +| 4.12.2 | Channel coding for E-RUCCH..... | 140 | +| 4.12.3 | Rate matching for E-RUCCH..... | 140 | +| 4.12.4 | Bit scrambling for E-RUCCH..... | 140 | +| 4.12.5 | Interleaving for E-RUCCH..... | 140 | +| 4.12.6 | Physical channel mapping for E-RUCCH..... | 140 | +| 5 | Multiplexing, channel coding and interleaving for the 3.84 Mcps MBSFN IMB option..... | 140 | +| 5.1 | General..... | 140 | +| 5.2 | General coding/multiplexing of TrCHs..... | 141 | +| 5.2.1 | CRC attachment..... | 141 | +| 5.2.2 | Transport block concatenation and code block segmentation..... | 141 | +| 5.2.3 | Channel coding..... | 141 | +| 5.2.4 | 1 st Interleaving..... | 141 | +| 5.2.5 | Radio frame segmentation..... | 141 | +| 5.2.6 | Rate matching..... | 141 | +| 5.2.7 | TrCH multiplexing..... | 141 | +| 5.2.8 | Insertion of discontinuous transmission (DTX) indication bits..... | 142 | +| 5.2.9 | Physical channel segmentation..... | 142 | +| 5.2.10 | 2 nd Interleaving..... | 142 | +| 5.2.11 | Physical channel mapping..... | 142 | +| 5.2.12 | Restrictions on different types of CCTrCHs..... | 143 | +| 5.2.12.1 | Broadcast channel (BCH)..... | 143 | +| 5.2.12.2 | Forward access channel (FACH)..... | 143 | +| 5.2.13 | Multiplexing of different TrCHs into one CCTrCH, and mapping of one CCTrCH onto physical channels..... | 143 | +| 5.3 | Transport format detection..... | 143 | +| 5.3.1 | Transport format detection based on TFCI..... | 143 | +| 5.3.2 | Coding of Transport-Format-Combination Indicator (TFCI)..... | 143 | +| 5.3.3 | Mapping of TFCI words..... | 143 | +| 5.3.3.1 | Mapping of TFCI bits for Secondary CCPCH..... | 143 | +| Annex A (informative): | Change history..... | 144 | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +[Version x.y.z](#) + +[where:](#) + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document describes multiplexing, channel coding and interleaving for UTRA Physical Layer TDD mode. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.202: "UE capabilities". +- [2] 3GPP TS 25.211: "Transport channels and physical channels (FDD)". +- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [4] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [6] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [7] 3GPP TS 25.221: "Transport channels and physical channels (TDD)". +- [9] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [10] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [11] 3GPP TS 25.225: "Measurements". +- [12] 3GPP TS 25.331: "RRC Protocol Specification". +- [13] 3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA): Overall description (stage 2)". +- [14] ITU-T Recommendation X.691 (12/97) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [15] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification" +- [16] 3GPP TS 25.302: "Services provided by the physical layer" +- [17] 3GPP TS 25.306: "UE Radio Access Capabilities" + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**TrCH number:** The transport channel number identifies a TrCH in the context of L1. The L3 transport channel identity (TrCH ID) maps onto the L1 transport channel number. The mapping between the transport channel number and the TrCH ID is as follows: TrCH 1 corresponds to the TrCH with the lowest TrCH ID, TrCH 2 corresponds to the TrCH with the next lowest TrCH ID and so on. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------|----------------------------------------------------------------------------------| +| $\lfloor x \rfloor$ | round towards $\infty$ , i.e. integer such that $x \leq \lfloor x \rfloor < x+1$ | +| $\lceil x \rceil$ | round towards $-\infty$ , i.e. integer such that $x-1 < \lceil x \rceil \leq x$ | +| $ x $ | absolute value of $x$ | + +Unless otherwise is explicitly stated when the symbol is used, the meaning of the following symbols are: + +| | | +|------------------------------|----------------------------------------------------------------------| +| $i$ | TrCH number | +| $j$ | TFC number | +| $k$ | Bit number | +| $l$ | TF number | +| $m$ | Transport block number | +| $n$ | Radio frame number | +| $p$ | PhCH number | +| $r$ | Code block number | +| $I$ | Number of TrCHs in a CCTrCH. | +| $C_i$ | Number of code blocks in one TTI of TrCH $i$ . | +| $F_i$ | Number of radio frames in one TTI of TrCH $i$ . | +| $M_i$ | Number of transport blocks in one TTI of TrCH $i$ . | +| $N_{TFCI \text{ code word}}$ | Number of TFCI code word bits after TFCI encoding | +| $P$ | Number of PhCHs used for one CCTrCH. | +| $PL$ | Puncturing Limit. Signalled from higher layers | +| $RM_i$ | Rate Matching attribute for TrCH $i$ . Signalled from higher layers. | + +Temporary variables, i.e. variables used in several (sub)clauses with different meaning. + +| | +|--------| +| $x, X$ | +| $y, Y$ | +| $z, Z$ | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----------|------------------------------------| +| ARQ | Automatic Repeat on Request | +| BCH | Broadcast Channel | +| BER | Bit Error Rate | +| BS | Base Station | +| BSS | Base Station Subsystem | +| CBR | Constant Bit Rate | +| CCCH | Common Control Channel | +| CCTrCH | Coded Composite Transport Channel | +| CDMA | Code Division Multiple Access | +| CFN | Connection Frame Number | +| CQI | Channel Quality Indicator | +| CRC | Cyclic Redundancy Check | +| DCA | Dynamic Channel Allocation | +| DCCH | Dedicated Control Channel | +| DCH | Dedicated Channel | +| DL | Downlink | +| DRX | Discontinuous Reception | +| DSCH | Downlink Shared Channel | +| DTX | Discontinuous Transmission | +| E-AGCH | E-DCH Absolute Grant Channel | +| ECSN | E-AGCH Cyclic Sequence Number | +| E-DCH | Enhanced Dedicated Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-PUCH | E-DCH Physical Uplink Channel | + +| | | +|----------------|------------------------------------------------------| +| E-RUCCH | E-DCH Random Access Uplink Control Channel | +| E-TFCI | E-DCH Transport Format Combination Indicator | +| E-UCCH | E-DCH Uplink Control Channel | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| FDMA | Frequency Division Multiple Access | +| FEC | Forward Error Control | +| FER | Frame Error Rate | +| GF | Galois Field | +| HARQ | Hybrid Automatic Repeat reQuest | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Channel for HS-DSCH | +| HS-SICH | Shared Information Channel for HS-DSCH | +| IMB | Integrated Mobile Broadcast | +| JD | Joint Detection | +| L1 | Layer 1 | +| L2 | Layer 2 | +| LLC | Logical Link Control | +| MA | Multiple Access | +| MAC | Medium Access Control | +| MBSFN | MBMS over a Single Frequency Network | +| MICH | MBMS Indicator Channel | +| MIMO | single user Multiple Input Multiple Output | +| MS | Mobile Station | +| MT | Mobile Terminated | +| MU-MIMO | Multi-User Multiple Input Multiple Output | +| NRT | Non-Real Time | +| OVSF | Orthogonal Variable Spreading Factor | +| PC | Power Control | +| PCCC | Parallel Concatenated Convolutional Code | +| PICH | Paging Indicator Channel | +| PCH | Paging Channel | +| PhCH | Physical Channel | +| PI | Paging Indicator (value calculated by higher layers) | +| PLCCH | Physical Layer Common Control Channel | +| P q | Paging Indicator (indicator set by physical layer) | +| QoS | Quality of Service | +| QPSK | Quaternary Phase Shift Keying | +| RACH | Random Access Channel | +| RF | Radio Frequency | +| RLC | Radio Link Control | +| RMF | Recommended Modulation Format | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RSC | Recursive Systematic Convolutional Coder | +| RSN | Retransmission Sequence Number | +| RT | Real Time | +| RTBS | Recommended Transport Block Size | +| RU | Resource Unit | +| RV | Redundancy Version | +| SCCC | Serial Concatenated Convolutional Code | +| SCH | Synchronization Channel | +| SNR | Signal to Noise Ratio | +| TCH | Traffic channel | +| TDD | Time Division Duplex | +| TDMA | Time Division Multiple Access | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TFRI | Transport Format Resource Indicator | +| TPC | Transmit Power Control | + +| | | +|------|--------------------------------------------| +| TrBk | Transport Block | +| TrCH | Transport Channel | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| USCH | Uplink Shared Channel | +| UTRA | UMTS Terrestrial Radio Access | +| VBR | Variable Bit Rate | + +## 4 Multiplexing, channel coding and interleaving for the 1.28 Mcps, 3.84 Mcps and 7.68 Mcps options + +In the case of the 3.84 Mcps option, clause 4 applies only for non-MBSFN-IMB operation. Multiplexing, channel coding and interleaving for 3.84 Mcps MBSFN IMB operation is described in sub-clause 5. + +### 4.1 General + +Data stream from/to MAC and higher layers (Transport block / Transport block set) is encoded/decoded to offer transport services over the radio transmission link. Channel coding scheme is a combination of error detection, error correcting (including rate matching), and interleaving and transport channels mapping onto/splitting from physical channels. + +In the UTRA-TDD mode for the 1.28 Mcps, 3.84 Mcps and 7.68 Mcps options, the total number of basic physical channels (a certain time slot one spreading code on a certain carrier frequency) per frame is given by the maximum number of time slots and the maximum number of CDMA codes per time slot. + +### 4.2 General coding/multiplexing of TrCHs + +This section only applies to the transport channels: DCH, RACH, DSCH, USCH, BCH, FACH and PCH. Other transport channels which do not use the general method are described separately below. + +Figure 1 illustrates the overall concept of transport-channel coding and multiplexing. Data arrives to the coding/multiplexing unit in form of transport block sets, once every transmission time interval. The transmission time interval is transport-channel specific from the set {5 ms(\*), 10 ms, 20 ms, 40 ms, 80 ms}. + +Note: (\*) may be applied for PRACH for 1.28 Mcps TDD + +The following coding/multiplexing steps can be identified: + +- add CRC to each transport block (see subclause 4.2.1); +- TrBk concatenation / Code block segmentation (see subclause 4.2.2); +- channel coding (see subclause 4.2.3) ; +- radio frame size equalization (see subclause 4.2.4); +- interleaving (two steps, see subclauses 4.2.5 and 4.2.11 ); +- radio frame segmentation (see subclause 4.2.6); +- rate matching (see subclause 4.2.7); +- multiplexing of transport channels (see subclause 4.2.8); +- bit scrambling (see subclause 4.2.9); +- physical channel segmentation (see subclause 4.2.10); +- sub-frame segmentation(see subclause 4.2.11A only for 1.28Mcps TDD) + +- mapping to physical channels (see subclause 4.2.12). + +The coding/multiplexing steps for uplink and downlink are shown in figures 1 and 1A. + +![Flowchart of transport channel multiplexing structure showing steps from input data to PHCH mapping.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The flowchart illustrates the transport channel multiplexing process. It begins with input data $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA_i}$ entering a 'CRC attachment' block. The output is $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ , which then enters 'TrBk concatenation / Code block segmentation'. The output is $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK_i}$ , followed by 'Channel coding' to produce $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ . This is followed by 'Radio frame equalisation' to produce $t_{i1}, t_{i2}, t_{i3}, \dots, t_{iT_i}$ , then '1st interleaving' to produce $d_{i1}, d_{i2}, d_{i3}, \dots, d_{iT_i}$ , and 'Radio frame segmentation' to produce $e_{i1}, e_{i2}, e_{i3}, \dots, e_{iN_i}$ . These segments enter 'Rate matching' blocks. The outputs of the rate matching blocks, $f_{i1}, f_{i2}, f_{i3}, \dots, f_{iV_i}$ , enter 'TrCH Multiplexing'. The output is $h_1, h_2, h_3, \dots, h_S$ , which enters 'Bit Scrambling' to produce $s_1, s_2, s_3, \dots, s_S$ . This is followed by 'Physical channel segmentation' to produce $u_{p1}, u_{p2}, u_{p3}, \dots, u_{pU_p}$ , then '2nd interleaving' to produce $v_{t,1}, v_{t,2}, v_{t,3}, \dots, v_{t,U_t}$ , and finally 'Physical channel mapping' to produce $w_{p1}, w_{p2}, w_{p3}, \dots, w_{pU_p}$ . The final outputs are labeled PHCH#1 and PHCH#2. Dashed boxes group the first eight steps and the rate matching stage. Ellipses indicate additional steps or parallel processing. + +Flowchart of transport channel multiplexing structure showing steps from input data to PHCH mapping. + +Figure 1: Transport channel multiplexing structure for uplink and downlink for 3.84Mcps and 7.68 Mcps TDD + +![Flowchart of transport channel multiplexing structure for 1.28Mcps TDD.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The flowchart illustrates the transport channel multiplexing structure for uplink and downlink of 1.28Mcps TDD. The process begins with multiple input data streams ( $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA_i}$ ) entering a 'CRC attachment' block. The output ( $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ ) is then processed by 'TrBk concatenation / Code block segmentation', resulting in ( $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK_i}$ ). This is followed by 'Channel coding', producing ( $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ ). The next step is 'Radio frame equalisation', which outputs ( $t_{i1}, t_{i2}, t_{i3}, \dots, t_{iT_i}$ ). This is followed by '1st interleaving', resulting in ( $d_{i1}, d_{i2}, d_{i3}, \dots, d_{iT_i}$ ). The next step is 'Radio frame segmentation', which outputs ( $e_{i1}, e_{i2}, e_{i3}, \dots, e_{iN_i}$ ). This is followed by 'Rate matching', which outputs ( $f_{i1}, f_{i2}, f_{i3}, \dots, f_{iV_i}$ ). The output is then processed by 'TrCH Multiplexing', resulting in ( $h_1, h_2, h_3, \dots, h_S$ ). This is followed by 'Bit Scrambling', which outputs ( $s_1, s_2, s_3, \dots, s_S$ ). The next step is 'Physical channel segmentation', which outputs ( $u_{p1}, u_{p2}, u_{p3}, \dots, u_{pU_p}$ ). This is followed by '2nd interleaving', resulting in ( $v_{t,1}, v_{t,2}, v_{t,3}, \dots, v_{t,U_t}$ ). The next step is 'Subframe segmentation', which outputs ( $g_{p1}, g_{p2}, g_{p3}, \dots, g_{pU_p}$ ). The final step is 'Physical channel mapping', which outputs ( $w_{p1}, w_{p2}, w_{p3}, \dots, w_{pU_p}$ ). The output is then split into 'PHCH#1' and 'PHCH#2'. + +Flowchart of transport channel multiplexing structure for 1.28Mcps TDD. + +**Figure 1A: Transport channel multiplexing structure for uplink and downlink of 1.28Mcps TDD** + +Primarily, transport channels are multiplexed as described above, i.e. into one data stream mapped on one or several physical channels. However, an alternative way of multiplexing services is to use multiple CCTrCHs (Coded Composite Transport Channels), which corresponds to having several parallel multiplexing chains as in figures 1 and 1A, resulting in several data streams, each mapped to one or several physical channels. + +#### 4.2.1 CRC attachment + +Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC). The size of the CRC is 24, 16, 12, 8 or 0 bits and it is signalled from higher layers what CRC size that should be used for each transport channel. + +##### 4.2.1.1 CRC calculation + +The entire transport block is used to calculate the CRC parity bits for each transport block. The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{\text{CRC24}}(D) = D^{24} + D^{23} + D^6 + D^5 + D + 1$$ + +$$g_{\text{CRC16}}(D) = D^{16} + D^{12} + D^5 + 1$$ + +$$g_{\text{CRC12}}(D) = D^{12} + D^{11} + D^3 + D^2 + D + 1$$ + +$$g_{\text{CRC8}}(D) = D^8 + D^7 + D^4 + D^3 + D + 1$$ + +Denote the bits in a transport block delivered to layer 1 by $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA_i}$ , and the parity bits by + +$p_{im1}, p_{im2}, p_{im3}, \dots, p_{imL_i}$ . $A_i$ is the size of a transport block of TrCH $i$ , $m$ is the transport block number, and $L_i$ is the number of parity bits. $L_i$ can take the values 24, 16, 12, 8, or 0 depending on what is signalled from higher layers. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial: + +$$a_{im1}D^{A_i+23} + a_{im2}D^{A_i+22} + \dots + a_{imA_i}D^{24} + p_{im1}D^{23} + p_{im2}D^{22} + \dots + p_{im23}D^1 + p_{im24}$$ + +yields a remainder equal to 0 when divided by $g_{\text{CRC24}}(D)$ , polynomial: + +$$a_{im1}D^{A_i+15} + a_{im2}D^{A_i+14} + \dots + a_{imA_i}D^{16} + p_{im1}D^{15} + p_{im2}D^{14} + \dots + p_{im15}D^1 + p_{im16}$$ + +yields a remainder equal to 0 when divided by $g_{\text{CRC16}}(D)$ , polynomial: + +$$a_{im1}D^{A_i+11} + a_{im2}D^{A_i+10} + \dots + a_{imA_i}D^{12} + p_{im1}D^{11} + p_{im2}D^{10} + \dots + p_{im11}D^1 + p_{im12}$$ + +yields a remainder equal to 0 when divided by $g_{\text{CRC12}}(D)$ and the polynomial: + +$$a_{im1}D^{A_i+7} + a_{im2}D^{A_i+6} + \dots + a_{imA_i}D^8 + p_{im1}D^7 + p_{im2}D^6 + \dots + p_{im7}D^1 + p_{im8}$$ + +yields a remainder equal to 0 when divided by $g_{\text{CRC8}}(D)$ . + +If no transport blocks are input to the CRC calculation ( $M_i = 0$ ), no CRC attachment shall be done. If transport blocks are input to the CRC calculation ( $M_i \neq 0$ ) and the size of a transport block is zero ( $A_i = 0$ ), CRC shall be attached, i.e. all parity bits equal to zero. + +##### 4.2.1.2 Relation between input and output of the CRC attachment block + +The bits after CRC attachment are denoted by $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ , where $B_i = A_i + L_i$ . The relation between $a_{imk}$ and $b_{imk}$ is: + +$$b_{imk} = a_{imk} \quad k = 1, 2, 3, \dots, A_i$$ + +$$b_{imk} = p_{im(L_i+1-(k-A_i))} \quad k = A_i + 1, A_i + 2, A_i + 3, \dots, A_i + L_i$$ + +## 4.2.2 Transport block concatenation and code block segmentation + +All transport blocks in a TTI are serially concatenated. If the number of bits in a TTI is larger than the maximum size of a code block, then code block segmentation is performed after the concatenation of the transport blocks. The maximum size of the code blocks depends on whether convolutional, turbo coding or no coding is used for the TrCH. + +### 4.2.2.1 Concatenation of transport blocks + +The bits input to the transport block concatenation are denoted by $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB_i}$ where $i$ is the TrCH number, $m$ is the transport block number, and $B_i$ is the number of bits in each block (including CRC). The number of transport blocks on TrCH $i$ is denoted by $M_i$ . The bits after concatenation are denoted by $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ , where $i$ is the TrCH number and $X_i = M_i B_i$ . They are defined by the following relations: + +$$x_{ik} = b_{i1k} \quad k = 1, 2, \dots, B_i$$ + +$$x_{ik} = b_{i2, (k - B_i)} \quad k = B_i + 1, B_i + 2, \dots, 2B_i$$ + +$$x_{ik} = b_{i3, (k - 2B_i)} \quad k = 2B_i + 1, 2B_i + 2, \dots, 3B_i$$ + +... + +$$x_{ik} = b_{iM_i, (k - (M_i - 1)B_i)} \quad k = (M_i - 1)B_i + 1, (M_i - 1)B_i + 2, \dots, M_i B_i$$ + +### 4.2.2.2 Code block segmentation + +Segmentation of the bit sequence from transport block concatenation is performed if $X_i > Z$ . The code blocks after segmentation are of the same size. The number of code blocks on TrCH $i$ is denoted by $C_i$ . If the number of bits input to the segmentation, $X_i$ , is not a multiple of $C_i$ , filler bits are added to the beginning of the first block. If turbo coding is selected and $X_i < 40$ , filler bits are added to the beginning of the code block. The filler bits are transmitted and they are always set to 0. The maximum code block sizes are: + +- convolutional coding: $Z = 504$ ; +- turbo coding: $Z = 5114$ ; +- no channel coding: $Z = \text{unlimited}$ . + +The bits output from code block segmentation, for $C_i \neq 0$ , are denoted by $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK_i}$ , where $i$ is the TrCH number, $r$ is the code block number, and $K_i$ is the number of bits per code block. + +Number of code blocks: + +$$C_i = \begin{cases} \lceil X_i / Z \rceil & \text{when } Z \neq \text{unlimited} \\ 0 & \text{when } Z = \text{unlimited and } X_i = 0 \\ 1 & \text{when } Z = \text{unlimited and } X_i \neq 0 \end{cases}$$ + +Number of bits in each code block (applicable for $C_i \neq 0$ only): + +if $X_i < 40$ and Turbo coding is used, then + +$$K_i = 40$$ + +else + +$$K_i = \lceil X_i / C_i \rceil$$ + +end if + +Number of filler bits: $Y_i = C_i K_i - X_i$ + +for $k = 1$ to $Y_i$ -- Insertion of filler bits + +$$o_{i1k} = 0$$ + +end for + +for $k = Y_i + 1$ to $K_i$ + +$$o_{i1k} = x_{i,(k-Y_i)}$$ + +end for + +$r = 2$ -- Segmentation + +while $r \leq C_i$ + +for $k = 1$ to $K_i$ + +$$o_{irk} = x_{i,(k+(r-1)K_i-Y_i)}$$ + +end for + +$r = r + 1$ + +end while + +### 4.2.3 Channel coding + +Code blocks are delivered to the channel coding block. They are denoted by $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK_i}$ , where $i$ is the TrCH number, $r$ is the code block number, and $K_i$ is the number of bits in each code block. The number of code blocks on TrCH $i$ is denoted by $C_i$ . After encoding the bits are denoted by $y_{ir1}, y_{ir2}, y_{ir3}, \dots, y_{irY_i}$ , where $Y_i$ is the number of encoded bits. The relation between $o_{irk}$ and $y_{irk}$ and between $K_i$ and $Y_i$ is dependent on the channel coding scheme. + +The following channel coding schemes can be applied to transport channels: + +- convolutional coding; +- turbo coding; +- no coding. + +Usage of coding scheme and coding rate for the different types of TrCH is shown in tables 1 and 1A. The values of $Y_i$ in connection with each coding scheme: + +- convolutional coding with rate 1/2: $Y_i = 2 * K_i + 16$ ; rate 1/3: $Y_i = 3 * K_i + 24$ ; +- turbo coding with rate 1/3: $Y_i = 3 * K_i + 12$ ; +- no coding: $Y_i = K_i$ . + +**Table 1: Usage of channel coding scheme and coding rate for 3.84Mcps TDD** + +| Type of TrCH | Coding scheme | Coding rate | +|-----------------------|----------------------|-------------| +| BCH | Turbo coding | 1/3 | +| PCH | Convolutional coding | 1/2 | +| RACH | | 1/3, 1/2 | +| DCH, DSCH, FACH, USCH | Turbo coding | 1/3 | +| | No coding | | + +Note: Rate 1/3 Turbo coding is only applied to BCH when the beacon timeslot uses burst type 4; rate 1/2 convolutional coding is only applied to BCH when the beacon timeslot uses burst type 1. For the MBSFN FACH, only rate 1/3 Turbo coding shall be applied. + +**Table 1A: Usage of channel coding scheme and coding rate for 1.28Mcps TDD** + +| Type of TrCH | Coding scheme | Coding rate | +|-----------------------|----------------------|-------------| +| BCH | | 1/3 | +| PCH | Convolutional coding | 1/3, 1/2 | +| RACH | | 1/2 | +| DCH, DSCH, FACH, USCH | | 1/3, 1/2 | +| | Turbo coding | 1/3 | +| | No coding | | + +Note: For the MBSFN FACH, only rate 1/3 Turbo coding shall be applied. + +#### 4.2.3.1 Convolutional coding + +Convolutional codes with constraint length 9 and coding rates 1/3 and 1/2 are defined. + +The configuration of the convolutional coder is presented in figure 2. + +Output from the rate 1/3 convolutional coder shall be done in the order output 0, output 1, output 2, output 0, output 1, output 2, output 0, ..., output 2. Output from the rate 1/2 convolutional coder shall be done in the order output 0, output 1, output 0, output 1, output 0, ..., output 1. + +8 tail bits with binary value 0 shall be added to the end of the code block before encoding. + +The initial value of the shift register of the coder shall be "all 0" when starting to encode the input bits. + +![Figure 2: Rate 1/2 and rate 1/3 convolutional coders. (a) Rate 1/2 convolutional coder: Input enters a series of 8 delay elements (D). The output of each delay is summed with the input to produce Output 0 (G0 = 561 octal). The output of each delay is also summed with the output of the previous delay to produce Output 1 (G1 = 753 octal). (b) Rate 1/3 convolutional coder: Input enters a series of 8 delay elements (D). The output of each delay is summed with the input to produce Output 0 (G0 = 557 octal). The output of each delay is also summed with the output of the previous delay to produce Output 1 (G1 = 663 octal). The output of each delay is also summed with the output of the previous two delays to produce Output 2 (G2 = 711 octal).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +(a) Rate 1/2 convolutional coder + +(b) Rate 1/3 convolutional coder + +Figure 2: Rate 1/2 and rate 1/3 convolutional coders. (a) Rate 1/2 convolutional coder: Input enters a series of 8 delay elements (D). The output of each delay is summed with the input to produce Output 0 (G0 = 561 octal). The output of each delay is also summed with the output of the previous delay to produce Output 1 (G1 = 753 octal). (b) Rate 1/3 convolutional coder: Input enters a series of 8 delay elements (D). The output of each delay is summed with the input to produce Output 0 (G0 = 557 octal). The output of each delay is also summed with the output of the previous delay to produce Output 1 (G1 = 663 octal). The output of each delay is also summed with the output of the previous two delays to produce Output 2 (G2 = 711 octal). + +**Figure 2: Rate 1/2 and rate 1/3 convolutional coders** + +#### 4.2.3.2 Turbo coding + +##### 4.2.3.2.1 Turbo coder + +The scheme of Turbo coder is a Parallel Concatenated Convolutional Code (PCCC) with two 8-state constituent encoders and one Turbo code internal interleaver. The coding rate of Turbo coder is 1/3. The structure of Turbo coder is illustrated in figure 3. + +The transfer function of the 8-state constituent code for PCCC is: + +$$G(D) = \left[ 1, \frac{g_1(D)}{g_0(D)} \right],$$ + +where + +$$g_0(D) = 1 + D^2 + D^3,$$ + +$$g_1(D) = 1 + D + D^3.$$ + +The initial value of the shift registers of the 8-state constituent encoders shall be all zeros when starting to encode the input bits. + +Output from the Turbo coder is , $Y'(0), X(1), Y(1), Y'(1)$ , etc: + +$$x_1, z_1, z'_1, x_2, z_2, z'_2, \dots, x_K, z_K, z'_K,$$ + +where $x_1, x_2, \dots, x_K$ are the bits input to the Turbo coder i.e. both first 8-state constituent encoder and Turbo code internal interleaver, and $K$ is the number of bits, and $z_1, z_2, \dots, z_K$ and $z'_1, z'_2, \dots, z'_K$ are the bits output from first and second 8-state constituent encoders, respectively. + +The bits output from Turbo code internal interleaver are denoted by $x'_1, x'_2, \dots, x'_K$ , and these bits are to be input to the second 8-state constituent encoder. + +![Figure 3: Structure of rate 1/3 Turbo coder. The diagram shows an input X_k entering a switch. One path goes to the '1st constituent encoder' which produces outputs X_k and Z_k. The other path goes to an 'Input Turbo code internal interleaver Output' block, which produces X'_k. X'_k then enters the '2nd constituent encoder' which produces outputs Z'_k and X'_k. Both encoders have feedback loops with delay elements (D) and adders. Dotted lines represent trellis termination paths.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 3: Structure of rate 1/3 Turbo coder. The diagram shows an input X\_k entering a switch. One path goes to the '1st constituent encoder' which produces outputs X\_k and Z\_k. The other path goes to an 'Input Turbo code internal interleaver Output' block, which produces X'\_k. X'\_k then enters the '2nd constituent encoder' which produces outputs Z'\_k and X'\_k. Both encoders have feedback loops with delay elements (D) and adders. Dotted lines represent trellis termination paths. + +Figure 3: Structure of rate 1/3 Turbo coder (dotted lines apply for trellis termination only) + +#### 4.2.3.2.2 Trellis termination for Turbo coder + +Trellis termination is performed by taking the tail bits from the shift register feedback after all information bits are encoded. Tail bits are padded after the encoding of information bits. + +The first three tail bits shall be used to terminate the first constituent encoder (upper switch of figure 3 in lower position) while the second constituent encoder is disabled. The last three tail bits shall be used to terminate the second constituent encoder (lower switch of figure 3 in lower position) while the first constituent encoder is disabled. + +The transmitted bits for trellis termination shall then be: + +$$x_{K+1}, z_{K+1}, x_{K+2}, z_{K+2}, x_{K+3}, z_{K+3}, x'_{K+1}, z'_{K+1}, x'_{K+2}, z'_{K+2}, x'_{K+3}, z'_{K+3}.$$ + +#### 4.2.3.2.3 Turbo code internal interleaver + +The Turbo code internal interleaver consists of bits-input to a rectangular matrix with padding, intra-row and inter-row permutations of the rectangular matrix, and bits-output from the rectangular matrix with pruning. The bits input to the Turbo code internal interleaver are denoted by $x_1, x_2, x_3, \dots, x_K$ , where $K$ is the integer number of the bits and takes one value of $40 \leq K \leq 5114$ . The relation between the bits input to the Turbo code internal interleaver and the bits input to the channel coding is defined by $x_k = o_{irk}$ and $K = K_i$ . + +The following subclause specific symbols are used in subclauses 4.2.3.2.3.1 to 4.2.3.2.3.3 : + +$K$ Number of bits input to Turbo code internal interleaver + +$R$ Number of rows of rectangular matrix + +$C$ Number of columns of rectangular matrix + +$p$ Prime number + +$v$ Primitive root + +$\langle s(j) \rangle_{j \in \{0, 1, \dots, p-2\}}$ Base sequence for intra-row permutation + +$q_i$ Minimum prime integers + +$r_i$ Permuted prime integers + +$\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ Inter-row permutation pattern + +$\langle U_i(j) \rangle_{j \in \{0, 1, \dots, C-1\}}$ Intra-row permutation pattern of $i$ -th row + +$i$ Index of row number of rectangular matrix + +$j$ Index of column number of rectangular matrix + +$k$ Index of bit sequence + +#### 4.2.3.2.3.1 Bits-input to rectangular matrix with padding + +The bit sequence $x_1, x_2, x_3, \dots, x_K$ input to the Turbo code internal interleaver is written into the rectangular matrix as follows. + +(1) Determine the number of rows of the rectangular matrix, $R$ , such that: + +$$R = \begin{cases} 5, & \text{if } (40 \leq K \leq 159) \\ 10, & \text{if } ((160 \leq K \leq 200) \text{ or } (481 \leq K \leq 530)) \\ 20, & \text{if } (K = \text{any other value}) \end{cases}$$ + +The rows of rectangular matrix are numbered 0, 1, ..., $R - 1$ from top to bottom. + +(2) Determine the prime number to be used in the intra-permutation, $p$ , and the number of columns of rectangular matrix, $C$ , such that: + +if $(481 \leq K \leq 530)$ then + +$$p = 53 \text{ and } C = p.$$ + +else + +Find minimum prime number $p$ from table 2 such that + +$$K \leq R \times (p + 1),$$ + +and determine $C$ such that + +$$C = \begin{cases} p - 1 & \text{if } K \leq R \times (p - 1) \\ p & \text{if } R \times (p - 1) < K \leq R \times p \\ p + 1 & \text{if } R \times p < K \end{cases}$$ + +end if + +The columns of rectangular matrix are numbered 0, 1, ..., $C - 1$ from left to right. + +**Table 2: List of prime number $p$ and associated primitive root $v$** + +| $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | $p$ | $v$ | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 7 | 3 | 47 | 5 | 101 | 2 | 157 | 5 | 223 | 3 | +| 11 | 2 | 53 | 2 | 103 | 5 | 163 | 2 | 227 | 2 | +| 13 | 2 | 59 | 2 | 107 | 2 | 167 | 5 | 229 | 6 | +| 17 | 3 | 61 | 2 | 109 | 6 | 173 | 2 | 233 | 3 | +| 19 | 2 | 67 | 2 | 113 | 3 | 179 | 2 | 239 | 7 | +| 23 | 5 | 71 | 7 | 127 | 3 | 181 | 2 | 241 | 7 | +| 29 | 2 | 73 | 5 | 131 | 2 | 191 | 19 | 251 | 6 | +| 31 | 3 | 79 | 3 | 137 | 3 | 193 | 5 | 257 | 3 | +| 37 | 2 | 83 | 2 | 139 | 2 | 197 | 2 | | | +| 41 | 6 | 89 | 3 | 149 | 2 | 199 | 3 | | | +| 43 | 3 | 97 | 5 | 151 | 6 | 211 | 2 | | | + +- (3) Write the input bit sequence $x_1, x_2, x_3, \dots, x_K$ into the $R \times C$ rectangular matrix row by row starting with bit $y_1$ in column 0 of row 0: + +$$\begin{bmatrix} y_1 & y_2 & y_3 & \dots & y_C \\ y_{(C+1)} & y_{(C+2)} & y_{(C+3)} & \dots & y_{2C} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{((R-1)C+1)} & y_{((R-1)C+2)} & y_{((R-1)C+3)} & \dots & y_{R \times C} \end{bmatrix}$$ + +where $y_k = x_k$ for $k = 1, 2, \dots, K$ and if $R \times C > K$ , the dummy bits are padded such that $y_k = 0$ or $1$ for $k = K + 1, K + 2, \dots, R \times C$ . These dummy bits are pruned away from the output of the rectangular matrix after intra-row and inter-row permutations. + +#### 4.2.3.2.3.2 Intra-row and inter-row permutations + +After the bits-input to the $R \times C$ rectangular matrix, the intra-row and inter-row permutations for the $R \times C$ rectangular matrix are performed stepwise by using the following algorithm with steps (1) – (6). + +- (1) Select a primitive root $v$ from table 2 in section 4.2.3.2.3.1, which is indicated on the right side of the prime number $p$ . + +- (2) Construct the base sequence $\langle s(j) \rangle_{j \in \{0, 1, \dots, p-2\}}$ for intra-row permutation as: + +$$s(j) = (v \times s(j-1)) \bmod p, \quad j = 1, 2, \dots, (p-2), \text{ and } s(0) = 1.$$ + +- (3) Assign $q_0 = 1$ to be the first prime integer in the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ , and determine the prime integer $q_i$ in the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ to be a least prime integer such that $\text{g.c.d}(q_i, p-1) = 1$ , $q_i > 6$ , and $q_i > q_{(i-1)}$ for each $i = 1, 2, \dots, R-1$ . Here $\text{g.c.d.}$ is greatest common divisor. + +- (4) Permute the sequence $\langle q_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ to make the sequence $\langle r_i \rangle_{i \in \{0, 1, \dots, R-1\}}$ such that + +$$r_{T(i)} = q_i, \quad i = 0, 1, \dots, R-1,$$ + +where $\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ is the inter-row permutation pattern defined as the one of the four kind of patterns, which are shown in table 3, depending on the number of input bits $K$ . + +**Table 3: Inter-row permutation patterns for Turbo code internal interleaver** + +| Number of input bits
$K$ | Number of rows
$R$ | Inter-row permutation patterns
$\langle T(0), T(1), \dots, T(R-1) \rangle$ | +|-----------------------------|-----------------------|-------------------------------------------------------------------------------| +|-----------------------------|-----------------------|-------------------------------------------------------------------------------| + +| | | | +|--------------------------------------------------------|----|----------------------------------------------------------------------------------------| +| $(40 \leq K \leq 159)$ | 5 | $\langle 4, 3, 2, 1, 0 \rangle$ | +| $(160 \leq K \leq 200)$ or $(481 \leq K \leq 530)$ | 10 | $\langle 9, 8, 7, 6, 5, 4, 3, 2, 1, 0 \rangle$ | +| $(2281 \leq K \leq 2480)$ or $(3161 \leq K \leq 3210)$ | 20 | $\langle 19, 9, 14, 4, 0, 2, 5, 7, 12, 18, 16, 13, 17, 15, 3, 1, 6, 11, 8, 10 \rangle$ | +| $K = \text{any other value}$ | 20 | $\langle 19, 9, 14, 4, 0, 2, 5, 7, 12, 18, 10, 8, 13, 17, 3, 1, 16, 6, 15, 11 \rangle$ | + +(5) Perform the $i$ -th ( $i = 0, 1, \dots, R - 1$ ) intra-row permutation as: + +if ( $C = p$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p - 1)), \quad j = 0, 1, \dots, (p - 2), \text{ and } U_i(p - 1) = 0,$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row. + +end if + +if ( $C = p + 1$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p - 1)), \quad j = 0, 1, \dots, (p - 2). \quad U_i(p - 1) = 0, \text{ and } U_i(p) = p,$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row, and + +if ( $K = R \times C$ ) then + +Exchange $U_{R-1}(p)$ with $U_{R-1}(0)$ . + +end if + +end if + +if ( $C = p - 1$ ) then + +$$U_i(j) = s((j \times r_i) \bmod (p - 1)) - 1, \quad j = 0, 1, \dots, (p - 2),$$ + +where $U_i(j)$ is the original bit position of $j$ -th permuted bit of $i$ -th row. + +end if + +(6) Perform the inter-row permutation for the rectangular matrix based on the pattern $\langle T(i) \rangle_{i \in \{0, 1, \dots, R-1\}}$ , + +where $T(i)$ is the original row position of the $i$ -th permuted row. + +#### 4.2.3.2.3.3 Bits-output from rectangular matrix with pruning + +After intra-row and inter-row permutations, the bits of the permuted rectangular matrix are denoted by $y'_k$ : + +$$\begin{bmatrix} y'_1 & y'_{(R+1)} & y'_{(2R+1)} & \dots & y'_{((C-1)R+1)} \\ y'_2 & y'_{(R+2)} & y'_{(2R+2)} & \dots & y'_{((C-1)R+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y'_R & y'_{2R} & y'_{3R} & \dots & y'_{C \times R} \end{bmatrix}$$ + +The output of the Turbo code internal interleaver is the bit sequence read out column by column from the intra-row and inter-row permuted $R \times C$ rectangular matrix starting with bit $y'_1$ in row 0 of column 0 and ending with bit $y'_{CR}$ in row $R - 1$ of column $C - 1$ . The output is pruned by deleting dummy bits that were padded to the input of the rectangular matrix before intra-row and inter row permutations, i.e. bits $y'_k$ that corresponds to bits $y_k$ with $k > K$ are removed from the output. The bits output from Turbo code internal interleaver are denoted by $x'_1, x'_2, \dots, x'_K$ , where $x'_1$ corresponds to the bit $y'_k$ with smallest index $k$ after pruning, $x'_2$ to the bit $y'_k$ with second smallest index $k$ after pruning, and so on. The number of bits output from Turbo code internal interleaver is $K$ and the total number of pruned bits is: + +$$R \times C - K.$$ + +#### 4.2.3.3 Concatenation of encoded blocks + +After the channel coding for each code block, if $C_i$ is greater than 1, the encoded blocks are serially concatenated so that the block with lowest index $r$ is output first from the channel coding block, otherwise the encoded block is output from + +channel coding block as it is. The bits output are denoted by $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ , where $i$ is the TrCH number and $E_i = C_i Y_i$ . The output bits are defined by the following relations: + +$$c_{ik} = y_{i1k} \quad k = 1, 2, \dots, Y_i$$ + +$$c_{ik} = y_{i,2,(k-Y_i)} \quad k = Y_i + 1, Y_i + 2, \dots, 2Y_i$$ + +$$c_{ik} = y_{i,3,(k-2Y_i)} \quad k = 2Y_i + 1, 2Y_i + 2, \dots, 3Y_i$$ + +... + +$$c_{ik} = y_{i,C_i,(k-(C_i-1)Y_i)} \quad k = (C_i - 1)Y_i + 1, (C_i - 1)Y_i + 2, \dots, C_i Y_i$$ + +If no code blocks are input to the channel coding ( $C_i = 0$ ), no bits shall be output from the channel coding, i.e. $E_i = 0$ . + +#### 4.2.4 Radio frame size equalisation + +Radio frame size equalisation is padding the input bit sequence in order to ensure that the output can be segmented in $F_i$ data segments of same size as described in the subclause 4.2.6. + +The input bit sequence to the radio frame size equalisation is denoted by $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE_i}$ , where $i$ is TrCH number and $E_i$ the number of bits. The output bit sequence is denoted by $t_{i1}, t_{i2}, t_{i3}, \dots, t_{iT_i}$ , where $T_i$ is the number of bits. The output bit sequence is derived as follows: + +$$t_{ik} = c_{ik}, \text{ for } k = 1 \dots E_i \text{ and}$$ + +$$t_{ik} = \{0, 1\} \text{ for } k = E_i + 1 \dots T_i, \text{ if } E_i < T_i$$ + +where + +$$T_i = F_i * N_i \text{ and}$$ + +$$N_i = \lceil E_i / F_i \rceil \text{ is the number of bits per segment after size equalisation.}$$ + +#### 4.2.5 1st interleaving + +The 1st interleaving is a block interleaver with inter-column permutations. The input bit sequence to the block + +interleaver is denoted by $x_{i,1}, x_{i,2}, x_{i,3}, \dots, x_{i,X_i}$ , where $i$ is TrCH number and $X_i$ the number of bits. Here $X_i$ is guaranteed to be an integer multiple of the number of radio frames in the TTI. The output bit sequence from the block interleaver is derived as follows: + +- 1) select the number of columns $C1$ from table 4 depending on the TTI. The columns are numbered 0, 1, ..., $C1 - 1$ from left to right. +- 2) determine the number of rows of the matrix, $R1$ defined as + +$$R1 = X_i / C1.$$ + +The rows of the matrix are numbered 0, 1, ..., $R1 - 1$ from top to bottom. + +- 3) write the input bit sequence into the $R1 \times C1$ matrix row by row starting with bit $x_{i,1}$ in column 0 of row 0 and ending with bit $x_{i,(R1 \times C1)}$ in column $C1 - 1$ of row $R1 - 1$ : + +$$\begin{bmatrix} x_{i,1} & x_{i,2} & x_{i,3} & \dots & x_{i,C1} \\ x_{i,(C1+1)} & x_{i,(C1+2)} & x_{i,(C1+3)} & \dots & x_{i,(2 \times C1)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ x_{i,((R1-1) \times C1+1)} & x_{i,((R1-1) \times C1+2)} & x_{i,((R1-1) \times C1+3)} & \dots & x_{i,(R1 \times C1)} \end{bmatrix}$$ + +- 4) Perform the inter-column permutation for the matrix based on the pattern $\langle P1_{C1}(j) \rangle_{j \in [0,1,\dots,C1-1]}$ shown in table 4, where $P1_{C1}(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y_{i,k}$ : + +$$\begin{bmatrix} y_{i,1} & y_{i,(R1+1)} & y_{i,(2 \times R1+1)} & \dots & y_{i,((C1-1) \times R1+1)} \\ y_{i,2} & y_{i,(R1+2)} & y_{i,(2 \times R1+2)} & \dots & y_{i,((C1-1) \times R1+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{i,R1} & y_{i,(2 \times R1)} & y_{i,(3 \times R1)} & \dots & y_{i,(C1 \times R1)} \end{bmatrix}$$ + +- 5) Read the output bit sequence $y_{i,1}, y_{i,2}, y_{i,3}, \dots, y_{i,(C1 \times R1)}$ of the block interleaver column by column from the inter-column permuted $R1 \times C1$ matrix. Bit $y_{i,1}$ corresponds to row 0 of column 0 and bit $y_{i,(R1 \times C1)}$ corresponds to row $R1 - 1$ of column $C1 - 1$ . + +**Table 4 Inter-column permutation patterns for 1st interleaving** + +| TTI | Number of columns C1 | Inter-column permutation patterns
$\langle P1_{C1}(0), P1_{C1}(1), \dots, P1_{C1}(C1-1) \rangle$ | +|----------------------------|----------------------|-----------------------------------------------------------------------------------------------------| +| 5ms (*) , 10 ms | 1 | $\langle 0 \rangle$ | +| 20 ms | 2 | $\langle 0, 1 \rangle$ | +| 40 ms | 4 | $\langle 0, 2, 1, 3 \rangle$ | +| 80 ms | 8 | $\langle 0, 4, 2, 6, 1, 5, 3, 7 \rangle$ | + +(\*) can be used for PRACH for 1.28 Mcps TDD + +#### 4.2.5.1 Relation between input and output of 1st interleaving + +The bits input to the 1st interleaving are denoted by $t_{i,1}, t_{i,2}, t_{i,3}, \dots, t_{i,T_i}$ , where $i$ is the TrCH number and $T_i$ the number of bits. Hence, $x_{i,k} = t_{i,k}$ and $X_i = T_i$ . + +The bits output from the 1st interleaving are denoted by $d_{i,1}, d_{i,2}, d_{i,3}, \dots, d_{i,T_i}$ , and $d_{i,k} = y_{i,k}$ . + +#### 4.2.6 Radio frame segmentation + +When the transmission time interval is longer than 10 ms, the input bit sequence is segmented and mapped onto consecutive $F_i$ radio frames. Following radio frame size equalisation the input bit sequence length is guaranteed to be an integer multiple of $F_i$ . + +The input bit sequence is denoted by $x_{i,1}, x_{i,2}, x_{i,3}, \dots, x_{i,X_i}$ where $i$ is the TrCH number and $X_i$ is the number bits. The $F_i$ output bit sequences per TTI are denoted by $y_{i,n_1}, y_{i,n_2}, y_{i,n_3}, \dots, y_{i,n_{Y_i}}$ where $n_i$ is the radio frame number in current TTI and $Y_i$ is the number of bits per radio frame for TrCH $i$ . The output sequences are defined as follows: + +$$y_{i,n_k} = x_{i,((n_i-1)Y_i)+k}, n_i = 1 \dots F_i, k = 1 \dots Y_i$$ + +where + +$Y_i = (X_i / F_i)$ is the number of bits per segment. + +The $n_i$ -th segment is mapped to the $n_i$ -th radio frame of the transmission time interval. + +The input bit sequence to the radio frame segmentation is denoted by $d_{i1}, d_{i2}, d_{i3}, \dots, d_{iT_i}$ , where $i$ is the TrCH number and $T_i$ the number of bits. Hence, $x_{ik} = d_{ik}$ and $X_i = T_i$ . + +The output bit sequence corresponding to radio frame $n_i$ is denoted by $e_{i1}, e_{i2}, e_{i3}, \dots, e_{iN_i}$ , where $i$ is the TrCH number and $N_i$ is the number of bits. Hence, $e_{i,k} = y_{i,n_i,k}$ and $N_i = Y_i$ . + +#### 4.2.7 Rate matching + +Rate matching means that bits on a TrCH are repeated or punctured. Higher layers assign a rate-matching attribute for each TrCH. This attribute is semi-static and can only be changed through higher layer signalling. The rate-matching attribute is used when the number of bits to be repeated or punctured is calculated. + +The number of bits on a TrCH can vary between different transmission time intervals. When the number of bits between different transmission time intervals is changed, bits are repeated to ensure that the total bit rate after TrCH multiplexing is identical to the total channel bit rate of the allocated physical channels. + +If no bits are input to the rate matching for all TrCHs within a CCTrCH, the rate matching shall output no bits for all TrCHs within the CCTrCH. + +##### Notation used in subclause 4.2.7 and subclauses: + +$N_{ij}$ : Number of bits in a radio frame before rate matching on TrCH $i$ with transport format combination $j$ . + +$\Delta N_{i,j}$ : If positive – number of bits to be repeated in each radio frame on TrCH $i$ with transport format combination $j$ . + +If negative – number of bits to be punctured in each radio frame on TrCH $i$ with transport format combination $j$ . + +$RM_i$ : Semi-static rate matching attribute for TrCH $i$ . Signalled from higher layers. + +$PL$ : Puncturing limit. This value limits the amount of puncturing that can be applied in order to minimise the number of physical channels. Signalled from higher layers. The allowed puncturing in % is actually equal to $(1-PL)*100$ . + +$N_{data,j}$ : Total number of bits that are available for a CCTrCH in a radio frame with transport format combination $j$ . + +$P$ : number of physical channels used in the current frame. + +$P_{max}$ : maximum number of physical channels allocated for a CCTrCH. + +$U_p$ : Number of data bits in the physical channel $p$ with $p = 1 \dots P$ during a radio frame. + +$I$ : Number of TrCHs in a CCTrCH. + +$Z_{ij}$ : Intermediate calculation variable. + +$F_i$ : Number of radio frames in the transmission time interval of TrCH $i$ . + +$n_i$ : Radio frame number in the transmission time interval of TrCH $i$ ( $0 \leq n_i < F_i$ ). + +$q$ : Average puncturing or repetition distance(normalised to only show the remaining rate matching on top of an integer number of repetitions). + +$PI_F(n_i)$ : The column permutation function of the 1st interleaver, $PI_F(x)$ is the original position of column with number $x$ after permutation. $PI$ is defined on table 4 of section 4.2.5 (note that $PI_F$ self-inverse). + +$S[n_i]$ : The shift of the puncturing or repetition pattern for radio frame $n_i$ when $n = PI_F(n_i)$ . + +$TF_i(j)$ : Transport format of TrCH $i$ for the transport format combination $j$ . + +$TFS(i)$ : The set of transport format indexes $l$ for TrCH $i$ . + +$e_{ini}$ : Initial value of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.3. + +$e_{plus}$ : Increment of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.3. + +$e_{minus}$ : Decrement of variable $e$ in the rate matching pattern determination algorithm of subclause 4.2.7.3. + +$b$ : Indicates systematic and parity bits. + +$b=1$ : Systematic bit. $X(t)$ in subclause 4.2.3.2.1. + +$b=2$ : 1st parity bit (from the upper Turbo constituent encoder). $Y(t)$ in subclause 4.2.3.2.1. + +$b=3$ : 2nd parity bit (from the lower Turbo constituent encoder). $Y'(t)$ in subclause 4.2.3.2.1. + +Note: when the TTI is 5msec for 1.28Mcps, the above notation refers to a sub-frame rather than a radio frame. In this case, $F_i = 1$ and $n_i = 0$ . + +#### 4.2.7.1 Determination of rate matching parameters + +The following relations, defined for all TFC $j$ , are used when calculating the rate matching pattern: + +$$Z_{0,j} = 0$$ + +$$Z_{i,j} = \left[ \frac{\left( \sum_{m=1}^i RM_m \times N_{m,j} \right) \times N_{data,j}}{\sum_{m=1}^I RM_m \times N_{m,j}} \right] \text{ for all } i = 1 \dots I \quad (1)$$ + +$$\Delta N_{i,j} = Z_{i,j} - Z_{i-1,j} - N_{i,j} \text{ for all } i = 1 \dots I$$ + +Puncturing can be used to minimise the required transmission capacity. The maximum amount of puncturing that can be applied is 1-PL, PL is signalled from higher layers. The possible values for $N_{data}$ depend on the number of physical channels $P_{max}$ , allocated to the respective CCTrCH, and on their characteristics (spreading factor, length of midamble and TFCI code word, usage of TPC and multiframe structure), which is given in [7]. + +For each physical channel an individual minimum spreading factor $Sp_{min}$ is transmitted by means of the higher layers. Denote the number of data bits in each physical channel by $U_{p,Sp}$ , where $p$ indicates the sequence number $1 \leq p \leq P_{max}$ and $Sp$ indicates the spreading factor of this physical channel: $Sp$ takes the possible values {16, 8, 4, 2, 1} for 1.28Mcps TDD and 3.84Mcps TDD, $Sp$ takes the possible values {32, 16, 8, 4, 2, 1} for 7.68Mcps TDD. The index $p$ is described in section 4.2.12 with the following modifications: spreading factor ( $Q$ ) is replaced by the minimum spreading factor $Sp_{min}$ and $k$ is replaced by the channelization code index at $Q = Sp_{min}$ . Then, for $N_{data}$ one of the following values in ascending order can be chosen: + +$$\left\{ U_{1,Sp_{min}}, U_{1,Sp_{min}} + U_{2,Sp_{min}}, U_{1,Sp_{min}} + U_{2,Sp_{min}} + \dots + U_{P_{max},(Sp_{max})_{min}} \right\}$$ + +Optionally, if indicated by higher layers for the UL the UE shall vary the spreading factor autonomously, so that $N_{data}$ is one of the following values in ascending order: + +$$\left\{ U_{1,16}, \dots, U_{1,S1_{\min}}, U_{1,S1_{\min}} + U_{2,16}, \dots, U_{1,S1_{\min}} + U_{2,S2_{\min}}, \dots, U_{1,S1_{\min}} + U_{2,S2_{\min}} + \dots + U_{P_{\max},16}, \dots, U_{1,S1_{\min}} + U_{2,S2_{\min}} + \dots + U_{P_{\max},(SP_{\max})_{\min}} \right\}$$ + +$N_{\text{data},j}$ for the transport format combination $j$ is determined by executing the following algorithm: + +$$\text{SET1} = \{ N_{\text{data}} \text{ such that } \left( \min_{1 \leq y \leq J} \{ RM_y \} \right) \times N_{\text{data}} - PL \times \sum_{x=1}^J RM_x \times N_{x,j} \text{ is non negative} \}$$ + +$$N_{\text{data},j} = \min \text{ SET1}$$ + +The number of bits to be repeated or punctured, $\Delta N_{ij}$ , within one radio frame (one sub-frame when the TTI is 5msec) for each TrCH $i$ is calculated with the relations given at the beginning of this subclause for all possible transport format combinations $j$ and selected every radio frame (sub-frame). The number of physical channels corresponding to $N_{\text{data},j}$ shall be denoted by $P$ . + +If $\Delta N_{ij} = 0$ then the output data of the rate matching is the same as the input data and the rate matching algorithm of subclause 4.2.7.3 does not need to be executed. + +Otherwise, the rate matching pattern is calculated with the algorithm described in subclause 4.2.7.3. For this algorithm the parameters $e_{\min}$ , $e_{\text{plus}}$ , $e_{\text{minus}}$ , and $X_i$ are needed, which are calculated according to the equations in subclauses 4.2.7.1.1 and 4.2.7.1.2. + +#### 4.2.7.1.1 Uncoded and convolutionally encoded TrCHs + +$$a = 2$$ + +$$\Delta N_i = \Delta N_{ij}$$ + +$$X_i = N_{ij}$$ + +$$R = \Delta N_{ij} \bmod N_{ij} \text{ -- note: in this context } \Delta N_{ij} \bmod N_{ij} \text{ is in the range of } 0 \text{ to } N_{ij}-1 \text{ i.e. } -1 \bmod 10 = 9.$$ + +$$\text{if } R \neq 0 \text{ and } 2 \times R \leq N_{ij}$$ + +$$\text{then } q = \lceil N_{ij} / R \rceil$$ + +else + +$$q = \lceil N_{ij} / (R - N_{ij}) \rceil$$ + +endif + +NOTE 1: $q$ is a signed quantity. + +If $q$ is even + +$$\text{then } q' = q + \gcd(|q|, F_i) / F_i \text{ -- where } \gcd(|q|, F_i) \text{ means greatest common divisor of } |q| \text{ and } F_i$$ + +NOTE 2: $q'$ is not an integer, but a multiple of 1/8. + +else + +$$q' = q$$ + +endif + +for $x = 0$ to $F_i - 1$ + +$$S[\lfloor x \times q' \rfloor \bmod F_i] = (\lfloor x \times q' \rfloor \bmod F_i)$$ + +end for + +$$e_{\min} = (a \times S[P1_F(n_i)] \times |\Delta N_i| + 1) \bmod (a \times N_{ij})$$ + +$$e_{\text{plus}} = a \times X_i$$ + +$$e_{\text{minus}} = a \times |\Delta N_i|$$ + +puncturing for $\Delta N_i < 0$ , repetition otherwise. + +#### 4.2.7.1.2 Turbo encoded TrCHs + +If repetition is to be performed on turbo encoded TrCHs, i.e. $\Delta N_i > 0$ , the parameters in subclause 4.2.7.1.1 are used. + +If puncturing is to be performed, the parameters below shall be used. Index $b$ is used to indicate systematic ( $b=1$ ), 1st parity ( $b=2$ ), and 2nd parity bit ( $b=3$ ). + +$a = 2$ when $b=2$ + +$a = 1$ when $b=3$ + +$$\Delta N_i = \begin{cases} \lceil \Delta N_{i,j} / 2 \rceil, & b = 2 \\ \lceil \Delta N_{i,j} / 2 \rceil, & b = 3 \end{cases}$$ + +If $\Delta N_i$ is calculated as 0 for $b=2$ or $b=3$ , then the following procedure and the rate matching algorithm of subclause 4.2.7.3 don't need to be performed for the corresponding parity bit stream. + +$X_i = \lceil N_{i,j} / 3 \rceil$ , + +$q = \lceil X_i / |\Delta N_i| \rceil$ + +if( $q \leq 2$ ) + +for $r=0$ to $F_i-1$ + +$S[(3 \times r + b - 1) \bmod F_i] = r \bmod 2$ ; + +end for + +else + +if $q$ is even + +then $q' = q - \gcd(q, F_i) / F_i$ -- where $\gcd(q, F_i)$ means greatest common divisor of $q$ and $F_i$ + +NOTE: $q'$ is not an integer, but a multiple of $1/8$ . + +else $q' = q$ + +endif + +for $x=0$ to $F_i-1$ + +$r = \lceil x \times q' \rceil \bmod F_i$ ; + +$S[(3 \times r + b - 1) \bmod F_i] = \lceil x \times q' \rceil \bmod F_i$ ; + +endfor + +endif + +For each radio frame, the rate-matching pattern is calculated with the algorithm in subclause 4.2.7.3, where: + +$X_i$ is as above, + +$e_{\text{ini}} = (a \times S[P1 \ F_i(n_i)] \times \lceil |\Delta N_i| \rceil + X_i) \bmod (a \times X_i)$ , if $e_{\text{ini}} = 0$ then $e_{\text{ini}} = a \times X_i$ + +$e_{\text{plus}} = a \times X_i$ + +$e_{\text{minus}} = a \times |\Delta N_i|$ + +#### 4.2.7.2 Bit separation and collection for rate matching + +The systematic bits of turbo encoded TrCHs shall not be punctured, the other bits may be punctured. The systematic bits, first parity bits, and second parity bits in the bit sequence input to the rate matching block are therefore separated into three sequences. + +The first sequence contains: + +- All of the systematic bits that are from turbo encoded TrCHs. +- From 0 to 2 first and/or second parity bits that are from turbo encoded TrCHs. These bits come into the first sequence when the total number of bits in a block after radio frame segmentation is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The second sequence contains: + +- All of the first parity bits that are from turbo encoded TrCHs, except those that go into the first sequence when the total number of bits is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The third sequence contains: + +- All of the second parity bits that are from turbo encoded TrCHs, except those that go into the first sequence when the total number of bits is not a multiple of three. +- Some of the systematic, first parity and second parity bits that are for trellis termination. + +The second and third sequences shall be of equal length, whereas the first sequence can contain from 0 to 2 more bits. Puncturing is applied only to the second and third sequences. + +The bit separation function is transparent for uncoded TrCHs, convolutionally encoded TrCHs, and for turbo encoded TrCHs with repetition. The bit separation and bit collection are illustrated in figures 4 and 5. + +![Figure 4: Puncturing of turbo encoded TrCHs. The diagram shows a block diagram of the rate matching process. An input bit sequence e_ik enters a 'Radio frame segmentation' block. The output of this block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs three sequences: x_1ik, x_2ik, and x_3ik. The x_1ik sequence bypasses a 'Rate matching algorithm' block. The x_2ik and x_3ik sequences enter separate 'Rate matching algorithm' blocks. The outputs of these algorithms, y_2ik and y_3ik, and the bypassed x_1ik sequence, then enter a 'Bit collection' block. The output of the 'Bit collection' block, f_ik, exits the 'Rate matching' block and enters a 'TrCH Multiplexing' block, which produces the final output.](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +Figure 4: Puncturing of turbo encoded TrCHs. The diagram shows a block diagram of the rate matching process. An input bit sequence e\_ik enters a 'Radio frame segmentation' block. The output of this block enters a 'Rate matching' block (indicated by a dashed box). Inside the 'Rate matching' block, the bits first pass through 'Bit separation', which outputs three sequences: x\_1ik, x\_2ik, and x\_3ik. The x\_1ik sequence bypasses a 'Rate matching algorithm' block. The x\_2ik and x\_3ik sequences enter separate 'Rate matching algorithm' blocks. The outputs of these algorithms, y\_2ik and y\_3ik, and the bypassed x\_1ik sequence, then enter a 'Bit collection' block. The output of the 'Bit collection' block, f\_ik, exits the 'Rate matching' block and enters a 'TrCH Multiplexing' block, which produces the final output. + +Figure 4: Puncturing of turbo encoded TrCHs + +![Block diagram of the rate matching process. It shows a flow from 'Radio frame segmentation' (input e_ik) to 'Bit separation' (output x_1ik), which then enters a 'Rate matching algorithm' block. The output of the algorithm is y_1ik, which goes to 'Bit collection' (output f_ik). These four blocks are enclosed in a dashed box labeled 'Rate matching'. The output f_ik then goes to 'TrCH Multiplexing'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +Block diagram of the rate matching process. It shows a flow from 'Radio frame segmentation' (input e\_ik) to 'Bit separation' (output x\_1ik), which then enters a 'Rate matching algorithm' block. The output of the algorithm is y\_1ik, which goes to 'Bit collection' (output f\_ik). These four blocks are enclosed in a dashed box labeled 'Rate matching'. The output f\_ik then goes to 'TrCH Multiplexing'. + +**Figure 5: Rate matching for uncoded TrCHs, convolutionally encoded TrCHs, and for turbo encoded TrCHs with repetition** + +The bit separation is dependent on the 1st interleaving and offsets are used to define the separation for different TTIs. $b$ indicates the three sequences defined in this section, with $b=1$ indicating the first sequence, $b = 2$ the second one, and $b = 3$ the third one. + +The offsets $\alpha_b$ for these sequences are listed in table 5. + +**Table 5: TTI dependent offset needed for bit separation** + +| TTI (ms) | $\alpha_1$ | $\alpha_2$ | $\alpha_3$ | +|-----------|------------|------------|------------| +| 5, 10, 40 | 0 | 1 | 2 | +| 20, 80 | 0 | 2 | 1 | + +The bit separation is different for different radio frames in the TTI. A second offset is therefore needed. The radio frame number for TrCH $i$ is denoted by $n_i$ and the offset by $\beta_{n_i}$ . + +**Table 6: Radio frame dependent offset needed for bit separation** + +| TTI (ms) | $\beta_0$ | $\beta_1$ | $\beta_2$ | $\beta_3$ | $\beta_4$ | $\beta_5$ | $\beta_6$ | $\beta_7$ | +|----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------| +| 5, 10 | 0 | NA | NA | NA | NA | NA | NA | NA | +| 20 | 0 | 1 | NA | NA | NA | NA | NA | NA | +| 40 | 0 | 1 | 2 | 0 | NA | NA | NA | NA | +| 80 | 0 | 1 | 2 | 0 | 1 | 2 | 0 | 1 | + +#### 4.2.7.2.1 Bit separation + +The bits input to the rate matching are denoted by $e_{i,1}, e_{i,2}, e_{i,3}, \dots, e_{i,N_i}$ , where $i$ is the TrCH number and $N_i$ is the number of bits input to the rate matching block. Note that the transport format combination number $j$ for simplicity has been left out in the bit numbering, i.e. $N_j=N_i$ . The bits after separation are denoted by $x_{b,i,1}, x_{b,i,2}, x_{b,i,3}, \dots, x_{b,i,X_i}$ . For turbo encoded TrCHs with puncturing, $b$ indicates the three sequences defined in section 4.2.7.2, with $b=1$ indicating the first sequence, and so forth. For all other cases $b$ is defined to be 1. $X_i$ is the number of bits in each separated bit sequence. The relation between $e_{i,k}$ and $x_{b,i,k}$ is given below. + +For turbo encoded TrCHs with puncturing: + +$$x_{1,i,k} = e_{i,3(k-1)+1+(\alpha_1+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +$$x_{1,i,\lfloor N_i/3 \rfloor+k} = e_{i,3\lfloor N_i/3 \rfloor+k} \quad k = 1, \dots, N_i \bmod 3 \text{ Note: When } (N_i \bmod 3) = 0 \text{ this row is not needed.}$$ + +$$x_{2,i,k} = e_{i,3(k-1)+1+(\alpha_2+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +$$x_{3,i,k} = e_{i,3(k-1)+1+(\alpha_3+\beta_{n_i}) \bmod 3} \quad k = 1, 2, 3, \dots, X_i \quad X_i = \lfloor N_i/3 \rfloor$$ + +For uncoded TrCHs, convolutionally encoded TrCHs, and turbo encoded TrCHs with repetition: + +$$x_{1,i,k} = e_{i,k} \quad k = 1, 2, 3, \dots, X_i \quad X_i = N_i$$ + +#### 4.2.7.2.2 Bit collection + +The bits $x_{b,i,k}$ are input to the rate matching algorithm described in subclause 4.2.7.3. The bits output from the rate matching algorithm are denoted $y_{b,i,1}, y_{b,i,2}, y_{b,i,3}, \dots, y_{b,i,Y_i}$ . + +Bit collection is the inverse function of the separation. The bits after collection are denoted by + +$z_{b,i,1}, z_{b,i,2}, z_{b,i,3}, \dots, z_{b,i,Y_i}$ . After bit collection, the bits indicated as punctured are removed and the bits are then denoted by $f_{i,1}, f_{i,2}, f_{i,3}, \dots, f_{i,V_i}$ , where $i$ is the TrCH number and $V_i = N_{ij} + \Delta N_{ij}$ . The relations between $y_{b,i,k}$ , $z_{b,i,k}$ , and $f_{i,k}$ are given below. + +For turbo encoded TrCHs with puncturing ( $Y_i=X_i$ ): + +$$z_{i,3(k-1)+1+(\alpha_1+\beta_{n_i}) \bmod 3} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3\lfloor N_i/3 \rfloor+k} = y_{1,i,\lfloor N_i/3 \rfloor+k} \quad k = 1, \dots, N_i \bmod 3 \text{ Note: When } (N_i \bmod 3) = 0 \text{ this row is not needed.}$$ + +$$z_{i,3(k-1)+1+(\alpha_2+\beta_{n_i}) \bmod 3} = y_{2,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +$$z_{i,3(k-1)+1+(\alpha_3+\beta_{n_i}) \bmod 3} = y_{3,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +After the bit collection, bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $f_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $f_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +For uncoded TrCHs, convolutionally encoded TrCHs, and turbo encoded TrCHs with repetition: + +$$z_{i,k} = y_{1,i,k} \quad k = 1, 2, 3, \dots, Y_i$$ + +When repetition is used, $f_{i,k}=z_{i,k}$ and $Y_i=V_i$ . + +When puncturing is used, $Y_i=X_i$ and bits $z_{i,k}$ with value $\delta$ , where $\delta \notin \{0, 1\}$ , are removed from the bit sequence. Bit $f_{i,1}$ corresponds to the bit $z_{i,k}$ with smallest index $k$ after puncturing, bit $f_{i,2}$ corresponds to the bit $z_{i,k}$ with second smallest index $k$ after puncturing, and so on. + +#### 4.2.7.3 Rate matching pattern determination + +The bits input to the rate matching are denoted by $x_{i,1}, x_{i,2}, x_{i,3}, \dots, x_{i,X_i}$ , where $i$ is the TrCH and $X_i$ is the parameter given in subclauses 4.2.7.1.1 and 4.2.7.1.2. + +NOTE: The transport format combination number $j$ for simplicity has been left out in the bit numbering. + +The rate matching rule is as follows: + +if puncturing is to be performed + +$e = e_{ini}$ -- initial error between current and desired puncturing ratio + +$m = 1$ -- index of current bit + +do while $m \leq X_i$ + +$e = e - e_{minus}$ -- update error + +if $e \leq 0$ then -- check if bit number $m$ should be punctured + +set bit $x_{i,m}$ to $\delta$ where $\delta \notin \{0, 1\}$ + +$e = e + e_{plus}$ -- update error + +end if + +$m = m + 1$ -- next bit + +end do + +else + +$e = e_{ini}$ -- initial error between current and desired puncturing ratio + +$m = 1$ -- index of current bit + +do while $m \leq X_i$ + +$e = e - e_{minus}$ -- update error + +do while $e \leq 0$ -- check if bit number $m$ should be repeated + +repeat bit $x_{i,m}$ + +$e = e + e_{plus}$ -- update error + +end do + +$m = m + 1$ -- next bit + +end do + +end if + +A repeated bit is placed directly after the original one. + +#### 4.2.8 TrCH multiplexing + +Every 10 ms, one radio frame from each TrCH is delivered to the TrCH multiplexing. These radio frames are serially multiplexed into a coded composite transport channel (CCTrCH). If the TTI is smaller than 10ms, then no TrCH multiplexing is performed. + +The bits input to the TrCH multiplexing are denoted by $f_{i,1}, f_{i,2}, f_{i,3}, \dots, f_{i,V_i}$ , where $i$ is the TrCH id number and $V_i$ is the number of bits in the radio frame of TrCH $i$ . The number of TrCHs is denoted by $I$ . The bits output from TrCH + +multiplexing are denoted by $h_1, h_2, h_3, \dots, h_S$ , where $S$ is the number of bits, i.e. $S = \sum_i V_i$ . The TrCH multiplexing is defined by the following relations: + +$$h_k = f_{1,k} \quad k = 1, 2, \dots, V_1$$ + +$$h_k = f_{2,(k-V_1)} \quad k = V_1+1, V_1+2, \dots, V_1+V_2$$ + +$$h_k = f_{3,(k-(V_1+V_2))} \quad k = (V_1+V_2)+1, (V_1+V_2)+2, \dots, (V_1+V_2)+V_3$$ + +$$\dots$$ + +$$h_k = f_{1,(k-(V_1+V_2+\dots+V_{l-1}))} \quad k = (V_1+V_2+\dots+V_{l-1})+1, (V_1+V_2+\dots+V_{l-1})+2, \dots, (V_1+V_2+\dots+V_{l-1})+V_l$$ + +#### 4.2.9 Bit Scrambling + +The bits output from the TrCH multiplexer are scrambled in the bit scrambler. The bits input to the bit scrambler are denoted by $h_1, h_2, h_3, \dots, h_S$ , where $S$ is the number of bits input to the bit scrambling block equal to the total number of bits on the CCTrCH. The bits after bit scrambling are denoted $s_1, s_2, s_3, \dots, s_S$ . + +Bit scrambling is defined by the following relation: + +$$s_k = h_k \oplus p_k \quad k = 1, 2, \dots, S$$ + +and $p_k$ results from the following operation: + +$$p_k = \left( \sum_{i=1}^{16} g_i \cdot p_{k-i} \right) \bmod 2 \quad ; \quad p_k = 0; k < 1 \quad ; \quad p_1 = 1 \quad ; \quad g = \{0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 1, 1, 0, 1\}$$ + +#### 4.2.10 Physical channel segmentation + +When more than one PhCH is used, physical channel segmentation divides the bits among the different PhCHs. The bits input to the physical channel segmentation are denoted by $s_1, s_2, s_3, \dots, s_S$ , where $S$ is the number of bits input to the physical channel segmentation block. The number of PhCHs after rate matching is denoted by $P$ , as defined in subclause 4.2.7.1. + +The bits after physical channel segmentation are denoted $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U_p}$ , where $p$ is PhCH number and $U_p$ is the in general variable number of bits in the respective radio frame for each PhCH. The relation between $s_k$ and $u_{p,k}$ is given below. + +Bits on first PhCH after physical channel segmentation: + +$$u_{1,k} = s_k \quad k = 1, 2, \dots, U_1$$ + +Bits on second PhCH after physical channel segmentation: + +$$u_{2,k} = s_{(k+U_1)} \quad k = 1, 2, \dots, U_2$$ + +$\dots$ + +Bits on the $P^{\text{th}}$ PhCH after physical channel segmentation: + +$$u_{p,k} = s_{(k+U_1+\dots+U_{p-1})} \quad k = 1, 2, \dots, U_p$$ + +#### 4.2.11 2nd interleaving + +The 2nd interleaving is a block interleaver and consists of bits input to a matrix with padding, the inter-column permutation for the matrix and bits output from the matrix with pruning. The 2nd interleaving can be applied jointly to all data bits transmitted during one frame, or separately within each timeslot, on which the CCTrCH is mapped. The selection of the 2nd interleaving scheme is controlled by higher layer. + +#### 4.2.11.1 Frame related 2nd interleaving + +In case of frame related 2nd interleaving, the bits input to the block interleaver are denoted by $x_1, x_2, x_3, \dots, x_U$ , where $U$ is the total number of bits after TrCH multiplexing transmitted during the respective radio frame with $S = U = \sum_p U_p$ . + +The relation between $x_k$ and the bits $u_{p,k}$ in the respective physical channels is given below: + +$$x_k = u_{1,k} \quad k = 1, 2, \dots, U_1$$ + +$$x_{(k+U_1)} = u_{2,k} \quad k = 1, 2, \dots, U_2$$ + +... + +$$x_{(k+U_1+\dots+U_{p-1})} = u_{p,k} \quad k = 1, 2, \dots, U_p$$ + +The following steps have to be performed once for each CCTrCH: + +(1) Assign $C2 = 30$ to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1, 2, ..., $C2 - 1$ from left to right. + +(2) Determine the number of rows of the matrix, $R2$ , by finding minimum integer $R2$ such that: + +$$U \leq R2 \times C2.$$ + +The rows of rectangular matrix are numbered 0, 1, 2, ..., $R2 - 1$ from top to bottom. + +(3) Write the input bit sequence $x_1, x_2, x_3, \dots, x_U$ into the $R2 \times C2$ matrix row by row starting with bit $y_1$ in column 0 of row 0: + +$$\begin{bmatrix} y_1 & y_2 & y_3 & \dots & y_{C2} \\ y_{(C2+1)} & y_{(C2+2)} & y_{(C2+3)} & \dots & y_{(2 \times C2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{((R2-1) \times C2+1)} & y_{((R2-1) \times C2+2)} & y_{((R2-1) \times C2+3)} & \dots & y_{(R2 \times C2)} \end{bmatrix}$$ + +where $y_k = x_k$ for $k = 1, 2, \dots, U$ and if $R2 \times C2 > U$ , the dummy bits are padded such that $y_k = 0$ or 1 for $k = U + 1, U + 2, \dots, R2 \times C2$ . These dummy bits are pruned away from the output of the matrix after the inter-column permutation. + +(4) Perform the inter-column permutation for the matrix based on the pattern $\langle P_2(j) \rangle_{j \in \{0, 1, \dots, C2-1\}}$ that is shown in table 7, where $P_2(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y'_k$ . + +$$\begin{bmatrix} y'_1 & y'_{(R2+1)} & y'_{(2 \times R2+1)} & \dots & y'_{((C2-1) \times R2+1)} \\ y'_2 & y'_{(R2+2)} & y'_{(2 \times R2+2)} & \dots & y'_{((C2-1) \times R2+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y'_{R2} & y'_{(2 \times R2)} & y'_{(3 \times R2)} & \dots & y'_{(C2 \times R2)} \end{bmatrix}$$ + +(5) The output of the block interleaver is the bit sequence read out column by column from the inter-column permuted $R2 \times C2$ matrix. The output is pruned by deleting dummy bits that were padded to + +the input of the matrix before the inter-column permutation, i.e. bits $y'_k$ that corresponds to bits $y_k$ with $k > U$ are removed from the output. The bits at the output of the block interleaver are denoted by $z$ , where $z_1$ corresponds to the bit $y'_k$ with smallest index $k$ after pruning, $z_2$ to the bit $y'_k$ with second smallest index $k$ after pruning, and so on. + +The bits shall be segmented as follows: + +$$k = 1, 2, \dots, U_1$$ + +$$k = 1, 2, \dots, U_2$$ + +... + +$$k = 1, 2, \dots, U_p$$ + +The bits after frame related 2nd interleaving are denoted by $v$ , where $t$ refers to the timeslot sequence number and $U_t$ is the number of bits transmitted in this timeslot during the respective radio frame. + +Let $T$ be the number of time slots in a CCTrCH during the respective radio frame (where for 1.28Mcps TDD, the respective radio frame includes subframes 1 and 2), and $t$ . The physical layer shall assign the time slot sequence number $t$ in ascending order of the allocated time slots in the CCTrCH in the respective radio frame. In time slot $t$ , $R_t$ refers to the number of physical channels within the respective time slot and $p$ . The relation between $r$ and $t$ and the physical channel sequence number $p$ as detailed in 4.2.12.1 is given by: + +Defining the relation $u_{t,r,k} = u_{p,k}$ and denoting $u_{t,r,k}$ as the number of bits for physical channel $r$ in time slot $t$ , the relation between $v_{t,k}$ and $u_{t,r,k}$ is given below: + +$$k = 1, 2, \dots,$$ + +$$k = 1, 2, \dots,$$ + +... + +$$k = 1, 2, \dots,$$ + +#### 4.2.11.2 Timeslot related 2nd interleaving + +In case of timeslot related 2nd interleaving, the bits input to the block interleaver are denoted by $x_{t,1}, x_{t,2}, x_{t,3}, \dots, x_{t,U_t}$ , where $t$ is the timeslot sequence number, and $U_t$ is the number of bits transmitted in this timeslot during the respective radio frame. + +Let $T$ be the number of time slots in a CCTrCH during the respective radio frame (where for 1.28Mcps TDD, the respective radio frame includes subframes 1 and 2), and $t$ . The physical layer shall assign the time slot sequence number $t$ in ascending order of the allocated time slots in the CCTrCH in the respective radio frame. In timeslot $t$ , $R_t$ refers to the number of physical channels within the respective timeslot and $p$ . The relation between $r$ and $t$ and the physical channel sequence number $p$ as detailed in 4.2.12.1 is given by: + +Defining the relation $u_{t,r,k} = u_{p,k}$ and denoting $u_{t,r,k}$ as the number of bits for physical channel $r$ in time slot $t$ , the relation between $x_{t,k}$ and $u_{t,r,k}$ is given below: + +$$x_{t,k} = u_{t,1,k} \quad k = 1, 2, \dots, U_{t1}$$ + +$$x_{t,(k+U_{t1})} = u_{t,2,k} \quad k = 1, 2, \dots, U_{t2}$$ + +... + +$$k = 1, 2, \dots,$$ + +The following steps have to be performed for each timeslot $t$ , on which the respective CCTrCH is mapped: + +- (1) Assign $C2 = 30$ to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1, 2, ..., $C2 - 1$ from left to right. +- (2) Determine the number of rows of the matrix, $R2$ , by finding minimum integer $R2$ such that: + +$$U_t \leq R2 \times C2.$$ + +The rows of rectangular matrix are numbered 0, 1, 2, ..., $R2 - 1$ from top to bottom. + +- (3) Write the input bit sequence $x_{t,1}, x_{t,2}, x_{t,3}, \dots, x_{t,U_t}$ into the $R2 \times C2$ matrix row by row starting with bit $y_{t,1}$ in column 0 of row 0: + +$$\begin{bmatrix} y_{t,1} & y_{t,2} & y_{t,3} & \dots & y_{t,C2} \\ y_{t,(C2+1)} & y_{t,(C2+2)} & y_{t,(C2+3)} & \dots & y_{t,(2 \times C2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y_{t,((R2-1) \times C2+1)} & y_{t,((R2-1) \times C2+2)} & y_{t,((R2-1) \times C2+3)} & \dots & y_{t,(R2 \times C2)} \end{bmatrix}$$ + +where $y_{t,k} = x_{t,k}$ for $k = 1, 2, \dots, U_t$ and if $R2 \times C2 > U_t$ , the dummy bits are padded such that $y_{t,k} = 0$ or 1 for $k = U_t + 1, U_t + 2, \dots, R2 \times C2$ . These dummy bits are pruned away from the output of the matrix after the inter-column permutation. + +- (4) Perform the inter-column permutation for the matrix based on the pattern $\langle P2(j) \rangle_{j \in \{0, 1, \dots, C2-1\}}$ that is shown in table 7, where $P2(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y'_{t,k}$ . + +$$\begin{bmatrix} y'_{t,1} & y'_{t,(R2+1)} & y'_{t,(2 \times R2+1)} & \dots & y'_{t,((C2-1) \times R2+1)} \\ y'_{t,2} & y'_{t,(R2+2)} & y'_{t,(2 \times R2+2)} & \dots & y'_{t,((C2-1) \times R2+2)} \\ \vdots & \vdots & \vdots & \dots & \vdots \\ y'_{t,R2} & y'_{t,(2 \times R2)} & y'_{t,(3 \times R2)} & \dots & y'_{t,(C2 \times R2)} \end{bmatrix}$$ + +- (5) The output of the block interleaver is the bit sequence read out column by column from the inter-column permuted $R2 \times C2$ matrix. The output is pruned by deleting dummy bits that were padded to the input of the matrix before the inter-column permutation, i.e. bits $y'_{t,k}$ that corresponds to bits $y_{t,k}$ with $k > U_t$ are removed from the output. The bits after time slot 2nd interleaving are denoted by $v_{t,1}, v_{t,2}, \dots, v_{t,U_t}$ , where $v_{t,1}$ corresponds to the bit $y'_{t,k}$ with smallest index $k$ after pruning, $v_{t,2}$ to the bit $y'_{t,k}$ with second smallest index $k$ after pruning, and so on. + +**Table 7 Inter-column permutation pattern for 2nd interleaving** + +| Number of Columns C2 | Inter-column permutation pattern
< P2(0), P2(1), ..., P2(C2-1) > | +|----------------------|----------------------------------------------------------------------------------------------------------------| +| 30 | <0, 20, 10, 5, 15, 25, 3, 13, 23, 8, 18, 28, 1, 11, 21, 6, 16, 26, 4, 14, 24, 19, 9, 29, 12, 2, 7, 22, 27, 17> | + +## 4.2.11A Sub-frame segmentation for the 1.28 Mcps option + +In the 1.28Mcps TDD, it is needed to add a sub-frame segmentation unit between 2nd interleaving unit and physical channel mapping unit when the TTI of the CCTrCh is greater than 5msec. In this case, the operation of rate-matching guarantees that the size of bit streams is an even number and can be subdivided into 2 sub-frames. The transport channel multiplexing structure for uplink and downlink is shown in figure 1A. + +The input to the sub-frame segmentation unit is segmented into timeslot chunks, where each timeslot chunk contains all of the bits that are to be transmitted in a given timeslot position in both of the sub-frames. + +The input bit sequence is denoted by $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ where $i$ is the timeslot number and $X_i$ is the number of bits transmitted in timeslot $i$ in a radio frame. The two output bit sequences per radio frame are denoted by $y_{i,n,1}, y_{i,n,2}, y_{i,n,3}, \dots, y_{i,n,Y_i}$ where $n$ is the sub-frame number in current radio frame and $Y_i$ is the number of bits per sub-frame for timeslot $i$ . The output sequences are defined as follows: + +$$n = 1 \text{ or } 2, k = 1 \dots Y_i$$ + +where + +$Y_i = (X_i / 2)$ is the number of bits in timeslot $i$ per sub-frame, + +$x_{ik}$ is the $k^{\text{th}}$ bit of the input bit sequence and + +$y_{i,n,k}$ is the $k^{\text{th}}$ bit of the output bit sequence corresponding to the $n^{\text{th}}$ sub-frame + +## 4.2.12 Physical channel mapping + +### 4.2.12.1 Physical channel mapping for the 3.84 Mcps and 7.68Mcps options + +The PhCH for both uplink and downlink is defined in [7]. The bits after physical channel mapping are denoted by + +$w_{p,1}, w_{p,2}, \dots, w_{p,U_p}$ , where $p$ is the PhCH number corresponding to the sequence number $1 \leq p \leq P$ of this physical channel as detailed below, $U_p$ is the number of bits in one radio frame for the respective PhCH, and $P \leq P_{max}$ . The bits $w_{p,k}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +The physical layer shall assign the physical channel sequence number $p$ to the physical channels of the CCTrCH in the respective radio frame, treating each allocated timeslot in ascending order. If within a timeslot there are multiple physical channels they shall first be ordered in ascending order of the spreading factor ( $Q$ ) and subsequently by channelisation code index ( $k$ ), as shown in [9]. + +The mapping of the bits is performed like block interleaving, writing the bits into columns, but a PhCH with an odd number is filled in forward order, whereas a PhCH with an even number is filled in reverse order. + +The mapping scheme, as described in the following subclause, shall be applied individually for each timeslot $t$ used in the current frame. Therefore, the bits $v_{t,1}, v_{t,2}, \dots, v_{t,U_t}$ are assigned to the bits of the physical channels + +$w_{t,1,1 \dots U_{t,1}}, w_{t,2,1 \dots U_{t,2}}, \dots, w_{t,P_t,1 \dots U_{t,P_t}}$ in each timeslot. + +In uplink there are at most two codes allocated ( $P \leq 2$ ). If there is only one code, the same mapping as for downlink is applied. Denote SF1 and SF2 the spreading factors used for code 1 and 2, respectively. For the number of consecutive bits to assign per code $bs_k$ the following rule is applied: + +if + +SF1 $\geq$ SF2 then $bs_1 = 1$ ; $bs_2 = \text{SF1/SF2}$ ; + +else + +SF2 > SF1 then $bs_1 = SF2/SF1$ ; $bs_2 = 1$ ; + +end if + +In the downlink case $bs_p$ is 1 for all physical channels. + +#### 4.2.12.1.1 Mapping scheme + +Notation used in this subclause: + +$P_t$ : number of physical channels for timeslot $t$ , $P_t = 1..2$ for uplink ; $P_t = 1..16$ for downlink for 1.28Mcps TDD and 3.84Mcps TDD, $P_t = 1..32$ for 7.68Mcps TDD + +$U_{t,p}$ : capacity in bits for the physical channel $p$ in timeslot $t$ + +$U_t$ : total number of bits to be assigned for timeslot $t$ + +$bs_p$ : number of consecutive bits to assign per code + +for downlink all $bs_p = 1$ + +for uplink if SF1 >= SF2 then $bs_1 = 1$ ; $bs_2 = SF1/SF2$ ; + +a) if SF2 > SF1 then $bs_1 = SF2/SF1$ ; $bs_2 = 1$ ; + +$fb_p$ : number of already written bits for each code + +$pos$ : intermediate calculation variable + +for $p=1$ to $P_t$ -- reset number of already written bits for every physical channel + +$fb_p = 0$ + +end for + +$p = 1$ -- start with PhCH #1 + +for $k=1$ to $U_t$ + +do while ( $fb_p == U_{t,p}$ ) -- physical channel filled up already ? + +$p = (p \bmod P_t) + 1$ ; + +end do + +if ( $p \bmod 2 == 0$ ) + +$pos = U_{t,p} - fb_p$ -- reverse order + +else + +$pos = fb_p + 1$ -- forward order + +endif + +$w_{t,p,pos} = v_{t,k}$ -- assignment + +$fb_p = fb_p + 1$ -- Increment number of already written bits + +if ( $fb_p \bmod bs_p == 0$ ) -- Conditional change to the next physical channel + +$p = (p \bmod P_t) + 1$ ; + +end if + +end for + +#### 4.2.12.2 Physical channel mapping for the 1.28 Mcps option + +The bit streams from the sub-frame segmentation unit are mapped onto code channels of time slots in sub-frames. + +The bits after physical channel mapping are denoted by $W_{p1}, W_{p2}, \dots, W_{pU_p}$ , where $p$ is the PhCH number and $U_p$ is the number of bits in one sub-frame for the respective PhCH. The bits $w_{pk}$ are mapped to the PhCHs so that the bits for each PhCH are transmitted over the air in ascending order with respect to $k$ . + +The mapping of the bits $y_{t,n,1}, y_{t,n,2}, y_{t,n,3}, \dots, y_{t,n,U_t}$ is performed like block interleaving, writing the bits into columns, but a PhCH with an odd number is filled in forward order, while a PhCH with an even number is filled in reverse order. + +The mapping scheme, as described in the following subclause, shall be applied individually for each timeslot $t$ used in the current subframe. Therefore, the bits $y_{t,n,1}, y_{t,n,2}, y_{t,n,3}, \dots, y_{t,n,U_t}$ are assigned to the bits of the physical channels $W_{t,1,1 \dots U_{t,1}}, W_{t,2,1 \dots U_{t,2}}, \dots, W_{t,P_t,1 \dots U_{t,P_t}}$ in each timeslot. + +In uplink there are at most two codes allocated ( $P \leq 2$ ). If there is only one code, the same mapping as for downlink is applied. Denote SF1 and SF2 the spreading factors used for code 1 and 2, respectively. For the number of consecutive bits to assign per code $b_{sk}$ the following rule is applied: + +if + +SF1 $\geq$ SF2 then $b_{s1} = 1$ ; $b_{s2} = \text{SF1/SF2}$ ; + +else + +SF2 $>$ SF1 then $b_{s1} = \text{SF2/SF1}$ ; $b_{s2} = 1$ ; + +end if + +In the downlink case $b_{sp} = 1$ for all physical channels. + +##### 4.2.12.2.1 Mapping scheme + +Notation used in this subclause: + +$P_t$ : number of physical channels for timeslot $t$ , $P_t = 1..2$ for uplink ; $P_t = 1..16$ for downlink + +$U_p$ : capacity in bits for the physical channel $p$ in timeslot $t$ in the current sub-frame + +$U_t$ : total number of bits to be assigned for timeslot $t$ in the current sub-frame + +$n$ = index of the current sub-frame (1 or 2) + +$b_{sp}$ : number of consecutive bits to assign per code + +for downlink all $b_{sp} = 1$ + +for uplink if SF1 $\geq$ SF2 then $b_{s1} = 1$ ; $b_{s2} = \text{SF1/SF2}$ ; + +if SF2 $>$ SF1 then $b_{s1} = \text{SF2/SF1}$ ; $b_{s2} = 1$ ; + +$fb_p$ : number of already written bits for each code + +$pos$ : intermediate calculation variable + +for $p=1$ to $P_t$ -- reset number of already written bits for every physical channel + +$fb_p = 0$ + +end for + +$p = 1$ -- start with PhCH #1 + +for $k=1$ to $U_t$ . + +do while ( $fb_p == U_{t,p}$ ) -- physical channel filled up already ? + +``` + +p = (p mod Pt) + 1 ; +end do +if (p mod 2) == 0 +pos = Ut,p - fbp -- reverse order +else +pos = fbp + 1 -- forward order +end if +Wt,p,pos = Yt,n,k -- assignment +fbp = fbp + 1 -- Increment number of already written bits +If (fbp mod bsp) == 0 -- Conditional change to the next physical channel +p = (p mod Pt) + 1 ; +end if +end for + +``` + +#### 4.2.13 Multiplexing of different transport channels onto one CCTrCH, and mapping of one CCTrCH onto physical channels + +Different transport channels can be encoded and multiplexed together into one Coded Composite Transport Channel (CCTrCH). The following rules shall apply to the different transport channels which are part of the same CCTrCH: + +- 1) Transport channels multiplexed into one CCTrCH shall have co-ordinated timings. When the TFCS of a CCTrCH is changed because one or more transport channels are added to the CCTrCH or reconfigured within the CCTrCH, or removed from the CCTrCH, the change may only be made at the start of a radio frame with CFN fulfilling the relation + +$$\text{CFN mod } F_{\max} = 0,$$ + +where $F_{\max}$ denotes the maximum number of radio frames within the transmission time intervals of all transport channels which are multiplexed into the same CCTrCH, including any transport channels $i$ which are added reconfigured or have been removed, and CFN denotes the connection frame number of the first radio frame of the changed CCTrCH. + +After addition or reconfiguration of a transport channel $i$ within a CCTrCH, the TTI of transport channel $i$ may only start in radio frames with CFN fulfilling the relation + +$$\text{CFN}_i \bmod F_i = 0.$$ + +- 2) Different CCTrCHs cannot be mapped onto the same physical channel. +- 3) One CCTrCH shall be mapped onto one or several physical channels. +- 4) Dedicated Transport channels and common transport channels cannot be multiplexed into the same CCTrCH. +- 5) For the common transport channels, only the FACH and PCH may belong to the same CCTrCH. +- 6) Each CCTrCH carrying a BCH shall carry only one BCH and shall not carry any other Transport Channel. +- 7) Each CCTrCH carrying a RACH shall carry only one RACH and shall not carry any other Transport Channel. + +Hence, there are two types of CCTrCH. + +CCTrCH of dedicated type, corresponding to the result of coding and multiplexing of one or several DCH. + +CCTrCH of common type, corresponding to the result of the coding and multiplexing of a common channel, i.e. RACH and USCH in the uplink and DSCH, BCH, FACH or PCH in the downlink, respectively. + +Transmission of TFCI is possible for CCTrCH containing Transport Channels of: + +- [dedicated type](#); +- [USCH type](#); +- [DSCH type](#); +- [FACH and/or PCH type](#). + +#### 4.2.13.1 Allowed CCTrCH combinations for one UE + +##### 4.2.13.1.1 Allowed CCTrCH combinations on the uplink + +The following CCTrCH combinations for one UE are allowed, also simultaneously: + +- 1) [several CCTrCH of dedicated type](#); +- 2) [several CCTrCH of common type](#). + +##### 4.2.13.1.2 Allowed CCTrCH combinations on the downlink + +The following CCTrCH combinations for one UE are allowed, also simultaneously: + +- 3) [several CCTrCH of dedicated type](#); +- 4) [several CCTrCH of common type](#). + +#### 4.2.14 Transport format detection + +Transport format detection can be performed both with and without Transport Format Combination Indicator (TFCI). If a TFCI is transmitted, the receiver detects the transport format combination from the TFCI. When no TFCI is transmitted, so called blind transport format detection may be used, i.e. the receiver side uses the possible transport format combinations as a priori information. + +##### 4.2.14.1 Blind transport format detection + +Blind Transport Format Detection is optional both in the UE and the UTRAN. Therefore, for all CCTrCH a TFCI shall be transmitted, including the possibility of a TFCI code word length zero, if only one TFC is defined. + +##### 4.2.14.2 Explicit transport format detection based on TFCI + +###### 4.2.14.2.1 Transport Format Combination Indicator (TFCI) + +The Transport Format Combination Indicator (TFCI) informs the receiver of the transport format combination of the CCTrCHs. As soon as the TFCI is detected, the transport format combination, and hence the individual transport channels' transport formats are known, and decoding of the transport channels can be performed. + +### 4.3 Coding for layer 1 control for the 3.84 Mcps and 7.68 Mcps TDD options + +#### 4.3.1 Coding of transport format combination indicator (TFCI) + +Encoding of the TFCI depends on its length. If there are 6-10 bits of TFCI the channel encoding is done as described in subclause 4.3.1.1. Also specific coding of less than 6 bits is possible as explained in subclause 4.3.1.2. + +#### 4.3.1.1 Coding of long TFCI lengths + +The TFCI is encoded using a (32, 10) sub-code of the second order Reed-Muller code. The coding procedure is as shown in figure 6. + +![Figure 6: Channel coding of the TFCI bits. A block diagram showing the input TFCI (10 bits) a9...a0 entering a block labeled '(32, 10) sub-code of the second order Reed-Muller code', which outputs the TFCI code word b0...b31.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +``` + +graph LR + Input["TFCI (10 bits) +a9...a0"] --> Block["(32, 10) sub-code of +the second order +Reed-Muller code"] + Block --> Output["TFCI code word +b0...b31"] + +``` + +Figure 6: Channel coding of the TFCI bits. A block diagram showing the input TFCI (10 bits) a9...a0 entering a block labeled '(32, 10) sub-code of the second order Reed-Muller code', which outputs the TFCI code word b0...b31. + +Figure 6: Channel coding of the TFCI bits + +If the TFCI consists of less than 10 bits, it is padded with zeros to 10 bits, by setting the most significant bits to zero. TFCI is encoded by the (32,10) sub-code of second order Reed-Muller code. The code words of the (32,10) sub-code of second order Reed-Muller code are linear combination of some among 10 basis sequences. The basis sequences are as follows in table 8. + +Table 8: Basis sequences for (32,10) TFCI code + +| I | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | M i,6 | M i,7 | M i,8 | M i,9 | +|----|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | +| 2 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| 4 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 5 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| 6 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | +| 7 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 8 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 9 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | +| 10 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | +| 11 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| 12 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| 13 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 14 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | +| 15 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | +| 16 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| 17 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | +| 18 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | +| 19 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | +| 20 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| 21 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | +| 22 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | +| 23 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | +| 24 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| 25 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 26 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| 27 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| 28 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | +| 29 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 30 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 31 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | + +The TFCI bits $a_0, a_1, a_2, a_3, a_4, a_5, a_6, a_7, a_8, a_9$ (where $a_0$ is LSB and $a_9$ is MSB) shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +The output TFCI code word bits $b_i$ are given by: + +$$b_i = \sum_{n=0}^9 (a_n \times M_{i,n}) \bmod 2$$ + +where $i = 0, \dots, 31$ . $N_{\text{TFCI code word}} = 32$ . + +#### 4.3.1.2 Coding of short TFCI lengths + +##### 4.3.1.2.1 Coding very short TFCIs by repetition + +If the number of TFCI bits is 1 or 2, then repetition will be used for coding. In this case each bit is repeated to a total of 4 times giving 4-bit transmission ( $N_{\text{TFCI code word}}=4$ ) for a single TFCI bit and 8-bit transmission ( $N_{\text{TFCI code word}}=8$ ) for 2 TFCI bits. The TFCI bit(s) $a_0$ (or $a_0$ and $a_1$ where $a_0$ is the LSB) shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +In the case of $N_{\text{TFCI code word}}=4$ , the TFCI codeword $\{b_0, b_1, b_2, b_3\}$ is equal to the sequence $\{a_0, a_0, a_0, a_0\}$ . + +In the case of $N_{\text{TFCI code word}}=8$ , the TFCI codeword $\{b_0, b_1, \dots, b_7\}$ is equal to the sequence $\{a_0, a_1, a_0, a_1, a_0, a_1, a_0, a_1\}$ . + +##### 4.3.1.2.2 Coding short TFCIs using bi-orthogonal codes + +If the number of TFCI bits is in the range 3 to 5 the TFCI is encoded using a (16, 5) bi-orthogonal (or first order Reed-Muller) code. The coding procedure is as shown in figure 7. + +![Figure 7: Channel coding of short length TFCI bits. A block diagram showing the input 'TFCI (5 bits) a4...a0' entering a block labeled '(16,5) bi-orthogonal code', which outputs the 'TFCI code word b0...b15'.](659a041a7997f9eea79f4e2f3ba265a5_img.jpg) + +``` + +graph LR + Input["TFCI (5 bits) +a4...a0"] --> Block["(16,5) bi-orthogonal code"] + Block --> Output["TFCI code word +b0...b15"] + +``` + +Figure 7: Channel coding of short length TFCI bits. A block diagram showing the input 'TFCI (5 bits) a4...a0' entering a block labeled '(16,5) bi-orthogonal code', which outputs the 'TFCI code word b0...b15'. + +Figure 7: Channel coding of short length TFCI bits + +If the TFCI consists of less than 5 bits, it is padded with zeros to 5 bits, by setting the most significant bits to zero. The code words of the (16,5) bi-orthogonal code are linear combinations of 5 basis sequences as defined in table 9. + +Table 9: Basis sequences for (16,5) TFCI code + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | +|----|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 1 | +| 1 | 0 | 1 | 0 | 0 | 1 | +| 2 | 1 | 1 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 1 | +| 4 | 1 | 0 | 1 | 0 | 1 | +| 5 | 0 | 1 | 1 | 0 | 1 | +| 6 | 1 | 1 | 1 | 0 | 1 | +| 7 | 0 | 0 | 0 | 1 | 1 | +| 8 | 1 | 0 | 0 | 1 | 1 | +| 9 | 0 | 1 | 0 | 1 | 1 | +| 10 | 1 | 1 | 0 | 1 | 1 | +| 11 | 0 | 0 | 1 | 1 | 1 | +| 12 | 1 | 0 | 1 | 1 | 1 | +| 13 | 0 | 1 | 1 | 1 | 1 | +| 14 | 1 | 1 | 1 | 1 | 1 | +| 15 | 0 | 0 | 0 | 0 | 1 | + +The TFCI bits $a_0, a_1, a_2, a_3, a_4$ (where $a_0$ is LSB and $a_4$ is MSB) shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +The output code word bits $b_j$ are given by: + +$$b_i = \sum_{n=0}^4 (a_n \times M_{i,n}) \bmod 2$$ + +where $i = 0, \dots, 15$ . $N_{\text{TFCI code word}} = 16$ . + +#### 4.3.1.3 Mapping of TFCI code word + +The mapping of the TFCI code word to the TFCI bit positions in a timeslot shall be as follows. + +Denote the number of bits in the TFCI code word by $N_{\text{TFCI code word}}$ , denote the TFCI code word bits by $b_k$ where $k=0 \dots N_{\text{TFCI code word}}-1$ . + +![Diagram showing the mapping of TFCI code word bits to timeslot. A horizontal bar represents the timeslot, divided into two main parts. The left part contains bits b_0, ..., b_{N/2-1} and is labeled 'first part of TFCI code word'. The right part contains bits b_{N/2}, ..., b_{N-1} and is labeled 'second part of TFCI code word'. Arrows point from each part of the bar to its respective label.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +Diagram showing the mapping of TFCI code word bits to timeslot. A horizontal bar represents the timeslot, divided into two main parts. The left part contains bits b\_0, ..., b\_{N/2-1} and is labeled 'first part of TFCI code word'. The right part contains bits b\_{N/2}, ..., b\_{N-1} and is labeled 'second part of TFCI code word'. Arrows point from each part of the bar to its respective label. + +**Figure 8: Mapping of TFCI code word bits to timeslot** + +The locations of the first and second parts of the TFCI code word in the timeslot is defined in [7]. + +If the shortest transmission time interval of any constituent TrCH is at least 20 ms the successive TFCI code words in the frames in the TTI shall be identical. If TFCI is transmitted on multiple timeslots in a frame each timeslot shall have the same TFCI code word. + +#### 4.3.2 Coding and Bit Scrambling of the Paging Indicator + +The paging indicator $P_q$ , $q = 0, \dots, N_{\text{PI}}-1$ , $P_q \in \{0, 1\}$ is an identifier to instruct the UE whether there is a paging message for the groups of mobiles that are associated to the PI, calculated by higher layers, and the associated paging indicator $P_q$ . The length $L_{\text{PI}}$ of the paging indicator is $L_{\text{PI}}=2$ , $L_{\text{PI}}=4$ or $L_{\text{PI}}=8$ symbols. $N_{\text{PIB}} = 2 * N_{\text{PI}} * L_{\text{PI}}$ bits are used for the paging indicator transmission in one radio frame. The mapping of the paging indicators to the bits $e_i$ , $i = 1, \dots, N_{\text{PIB}}$ is shown in table 10. + +**Table 10: Mapping of the paging indicator** + +| $P_q$ | Bits $\{e_{2L_{\text{PI}}*q+1}, e_{2L_{\text{PI}}*q+2}, \dots, e_{2L_{\text{PI}}*(q+1)}\}$ | Meaning | +|-------|--------------------------------------------------------------------------------------------|-------------------------------------------| +| 0 | $\{0, 0, \dots, 0\}$ | There is no necessity to receive the PCH | +| 1 | $\{1, 1, \dots, 1\}$ | There is the necessity to receive the PCH | + +If the number $S$ of bits in one radio frame available for the PICH is bigger than the number $N_{\text{PIB}}$ of bits used for the transmission of paging indicators, the sequence $e = \{e_1, e_2, \dots, e_{N_{\text{PIB}}}\}$ is extended by $S - N_{\text{PIB}}$ bits that are set to zero, resulting in a sequence $h = \{h_1, h_2, \dots, h_S\}$ : + +The bits $h_k$ , $k = 1, \dots, S$ on the PICH then undergo bit scrambling as defined in section 4.2.9. + +The bits $s_k$ , $k = 1, \dots, S$ output from the bit scrambler are then transmitted over the air as shown in [7]. + +#### 4.3.3 Coding and Bit Scrambling of the MBMS Notification Indicator + +The MBMS notification indicator $N_q$ , $q = 0, \dots, N_n-1$ , $N_q \in \{0, 1\}$ , is an identifier to instruct UEs whether there is an MBMS notification indication for the groups of MBMS services that are associated to the NI, calculated by higher layers, and the associated MBMS notification indicator $N_q$ . The length $L_{\text{NI}}$ of the MBMS notification indicator is $L_{\text{NI}}=2$ , $L_{\text{NI}}=4$ or $L_{\text{NI}}=8$ symbols. $N_{\text{NIB}} = 2 * N_n * L_{\text{NI}}$ bits are used for the MBMS notification indicator transmission in one MICH. The mapping of the MBMS notification indicators to the bits $e_i$ , $i = 1, \dots, N_{\text{NIB}}$ is shown in table 10A. + +**Table 10A: Mapping of the MBMS notification indicator** + +| $N_q$ | Bits $\{e_{2L_{\text{NI}}*q+1}, e_{2L_{\text{NI}}*q+2}, \dots, e_{2L_{\text{NI}}*(q+1)}\}$ | +|-------|--------------------------------------------------------------------------------------------| +| 0 | $\{0, 0, \dots, 0\}$ | +| 1 | $\{1, 1, \dots, 1\}$ | + +If the number $S$ of bits available for the MICH is bigger than the number $N_{\text{NIB}}$ of bits used for the transmission of MBMS notification indicators, the sequence $e = \{e_1, e_2, \dots, e_{N_{\text{NIB}}}\}$ is extended by $S - N_{\text{NIB}}$ bits that are set to zero, resulting in a sequence $h = \{h_1, h_2, \dots, h_S\}$ : + +The bits $h_k, k = 1, \dots, S$ on the MICH then undergo bit scrambling as defined in section 4.2.9. + +The bits $s_k, k = 1, \dots, S$ output from the bit scrambler are then transmitted over the air as shown in [7]. + +## 4.4 Coding for layer 1 control for the 1.28 Mcps option + +### 4.4.1 Coding of transport format combination indicator (TFCI) for QPSK and 16QAM + +The coding of TFCI for 1.28 Mcps TDD is same as that of 3.84 Mcps TDD cf.[4.3.1 'Coding of transport format combination indicator']. + +#### 4.4.1.1 Mapping of TFCI code word + +Denote the number of bits in the TFCI code word by $N_{\text{TFCI code word}}$ , and denote the TFCI code word bits by $b_k$ , where $k = 0, \dots, N_{\text{TFCI code word}} - 1$ + +When the number of bits in the TFCI code word is 8, 16, 32, the mapping of the TFCI code word to the TFCI bit positions shall be as follows: + +![Diagram showing the mapping of TFCI code word bits to TFCI positions. The diagram illustrates a sequence of bits b_0, b_{N/4-1}, b_{N/4}, b_{N/2-1}, b_{N/2}, b_{3N/4-1}, b_{3N/4}, and b_{N-1} being mapped into four parts of the TFCI code word. The mapping is as follows: b_0 and b_{N/4-1} map to the 1st part; b_{N/4} and b_{N/2-1} map to the 2nd part; b_{N/2} and b_{3N/4-1} map to the 3rd part; and b_{3N/4} and b_{N-1} map to the 4th part. Each part contains a sequence of bits with ellipses indicating intermediate bits.](da434ee158d8bd56122f990b91dc17ba_img.jpg) + +Diagram showing the mapping of TFCI code word bits to TFCI positions. The diagram illustrates a sequence of bits b\_0, b\_{N/4-1}, b\_{N/4}, b\_{N/2-1}, b\_{N/2}, b\_{3N/4-1}, b\_{3N/4}, and b\_{N-1} being mapped into four parts of the TFCI code word. The mapping is as follows: b\_0 and b\_{N/4-1} map to the 1st part; b\_{N/4} and b\_{N/2-1} map to the 2nd part; b\_{N/2} and b\_{3N/4-1} map to the 3rd part; and b\_{3N/4} and b\_{N-1} map to the 4th part. Each part contains a sequence of bits with ellipses indicating intermediate bits. + +**Figure 9: Mapping of TFCI code word bits to TFCI position in 1.28 Mcps TDD option, where $N = N_{\text{TFCI code word}}$ .** + +For MBSFN transmissions with 16QAM, the coded bits $b_k$ , are mapped to the transmitted TFCI bits according to the following two group formulas: + +Formula a, mapping onto the outer-corners of the 16QAM constellation + +$$d_{4k} = b_{2k},$$ + +$$d_{4k+1} = b_{2k+1},$$ + +$$d_{4k+2} = 1,$$ + +$$d_{4k+3} = 1,$$ + +Formula b, mapping onto the inner-corners of the 16QAM constellation + +$$d_{4k} = b_{2k},$$ + +$$d_{4k+1} = b_{2k+1},$$ + +$$d_{4k+2} = 0,$$ + +$$d_{4k+3} = 0,$$ + +The 1st, the 3rd, the 5th and the 7th part of TFCI code word will use the Mapping Formula a, and the 2nd, the 4th, the 6th and the 8th part of TFCI code word will use the Mapping Formula b. As the TTI of S-CCPCH is 40ms or 80ms, the TFCI bits will be repeated with a period of 20ms frame. In the second 20ms frame, the 1st, the 3rd, the 5th and the 7th part of TFCI code word will use the Mapping Formula b, and the 2nd, the 4th, the 6th and 8th part of TFCI code word will use the Mapping Formula a, and so on for the consecutive frames. The mapping of the TFCI code word to the TFCI bit positions shall be as follows: + +![Figure 9A: A simple diagram showing a rectangle with a diagonal line extending from its top-left corner upwards and to the left.](1dd5414c93117a86043e7ae8d3ac1c0b_img.jpg) + +Figure 9A: A simple diagram showing a rectangle with a diagonal line extending from its top-left corner upwards and to the left. + +**Figure 9A: Mapping of TFCI code word bits to TFCI position in 1.28 Mcps TDD option for downlink MBSFN, where $N = N_{\text{TFCI code word}}$ .** + +When the number of bits of the TFCI code word is 4, then the TFCI code word is equally divided into two parts for the consecutive two subframe and mapped onto the end of the first data field in each of the consecutive subframes. The mapping for $N_{\text{TFCI code word}}=4$ is shown in figure 10: + +![Figure 10: A diagram showing the mapping of 4 TFCI code word bits (b0, b1, b2, b3) to four parts of a TFCI field. The bits b0 and b1 are mapped to the 1st and 2nd parts, while b2 and b3 are mapped to the 3rd and 4th parts. Each part is shown as a box with an arrow pointing to it from the corresponding bit label above.](5c3dd31372f59e15250f0ab1613ca485_img.jpg) + +Figure 10: A diagram showing the mapping of 4 TFCI code word bits (b0, b1, b2, b3) to four parts of a TFCI field. The bits b0 and b1 are mapped to the 1st and 2nd parts, while b2 and b3 are mapped to the 3rd and 4th parts. Each part is shown as a box with an arrow pointing to it from the corresponding bit label above. + +**Figure 10: Mapping of TFCI code word bits to TFCI position in 1.28 Mcps TDD option, when $N_{\text{TFCI code word}}=4$** + +The location of the 1st to 4th parts of the TFCI code word in the timeslot is defined in [7]. + +If the shortest transmission time interval of any constituent TrCH is at least 20 ms, then successive TFCI code words in the frames within the TTI shall be identical. If a TFCI is transmitted on multiple timeslots in a frame each timeslot shall have the same TFCI code word. + +#### 4.4.2 Coding of transport format combination indicator (TFCI) for 8PSK + +Encoding of TFCI bits depends on the number of them and the modulation in use. When 2 Mcps service is transmitted, 8PSK modulation is applied in 1.28 Mcps TDD option. The encoding scheme for TFCI when the number of bits are 6 – 10, and less than 6 bits is described in section 4.4.2.1 and 4.4.2.2, respectively. + +#### 4.4.2.1 Coding of long TFCI lengths + +When the number of TFCI bits is 6 – 10, the TFCI bits are encoded by using a (64,10) sub-code of the second order Reed-Muller code, then 16 bits out of 64 bits are punctured (Puncturing positions are 0, 4, 8, 13, 16, 20, 27, 31, 34, 38, 41, 44, 50, 54, 57, 61st bits). The coding procedure is shown in Figure 11. + +![Figure 11: Channel coding of long TFCI bits for 8PSK. The diagram shows a flow from left to right: TFCI (10 bits) a9 ... a0 enters a block labeled '(64,10) sub-code of second order Reed Muller code', which then enters a block labeled 'Puncturing', resulting in a TFCI code word b0 ... b47.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` + +graph LR + A["TFCI +(10 bits) +a9 ..., a0"] --> B["(64,10) sub-code +of second order +Reed Muller code"] + B --> C["Puncturing"] + C --> D["TFCI code word +b0 ..., b47"] + +``` + +Figure 11: Channel coding of long TFCI bits for 8PSK. The diagram shows a flow from left to right: TFCI (10 bits) a9 ... a0 enters a block labeled '(64,10) sub-code of second order Reed Muller code', which then enters a block labeled 'Puncturing', resulting in a TFCI code word b0 ... b47. + +**Figure 11: Channel coding of long TFCI bits for 8PSK** + +If the TFCI consists of less than 10 bits, it is padded with zeros to 10 bits, by setting the most significant bits to zero. The code words of the punctured (48,10) sub-code of the second order Reed-Muller codes are linear combination of 10 basis sequences. The basis sequences are shown in Table 11. + +**Table 11: Basis sequences for (48,10) TFCI code** + +| I | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | M i,6 | M i,7 | M i,8 | M i,9 | +|----|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | +| 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | +| 2 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | +| 3 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | +| 4 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | +| 5 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | +| 6 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| 7 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | +| 8 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | +| 9 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | +| 10 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | +| 11 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| 12 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| 13 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| 14 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | +| 15 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| 16 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | +| 17 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| 18 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | +| 19 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | +| 20 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | +| 21 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | +| 22 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| 23 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | +| 24 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | +| 25 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | +| 26 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | +| 27 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| 28 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | +| 29 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| 30 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 31 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 32 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | +| 33 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 34 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 35 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | +| 36 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | +| 37 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | +| 38 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | +| 39 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | +| 40 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | +| 41 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | +| 42 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 43 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| 44 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| 45 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 46 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 47 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | + +Let's define the TFCI bits as $a_0, a_1, a_2, a_3, a_4, a_5, a_6, a_7, a_8, a_9$ , where $a_0$ is the LSB and $a_9$ is the MSB. The TFCI bits shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +The output TFCI code word bits $b_i$ are given by: + +$$b_i = \sum_{n=0}^9 (a_n \times M_{i,n}) \bmod 2$$ + +where $i=0 \dots 47$ . $N_{\text{TFCI code word}}=48$ . + +#### 4.4.2.2 Coding of short TFCI lengths + +##### 4.4.2.2.1 Coding very short TFCIs by repetition + +When the number of TFCI bits is 1 or 2, then repetition will be used for the coding. In this case, each bit is repeated to a total of 6 times giving 6-bit transmission ( $N_{\text{TFCI code word}} = 6$ ) for a single TFCI bit and 12-bit transmission ( $N_{\text{TFCI code word}} = 12$ ) for 2 TFCI bits. The TFCI bit(s) $a_0$ (or $a_0$ and $a_1$ where $a_0$ is the LSB) shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +In the case of $N_{\text{TFCI code word}}=6$ , the TFCI codeword $\{b_0, b_1, b_2, b_3, b_4, b_5\}$ is equal to the sequence $\{a_0, a_0, a_0, a_0, a_0, a_0\}$ . + +In the case of $N_{\text{TFCI code word}}=12$ , the TFCI codeword $\{b_0, b_1, \dots, b_{11}\}$ is equal to the sequence $\{a_0, a_1, a_0, a_1, a_0, a_1, a_0, a_1, a_0, a_1, a_0, a_1\}$ . + +##### 4.4.2.2.2 Coding short TFCIs using bi-orthogonal codes + +If the number of TFCI bits is in the range of 3 to 5, the TFCI bits are encoded using a (32,5) first order Reed-Muller code, then 8 bits out of 32 bits are punctured (Puncturing positions are 0, 1, 2, 3, 4, 5, 6, 7th bits). The coding procedure is shown in Figure 12. + +![Figure 12: Channel coding of short TFCI bits for 8PSK. The diagram shows a flow from left to right: 'TFCI (5 bits) a4 ... a0' enters a box labeled '(32,5) First order Reed-Muller code', which then enters a box labeled 'Puncturing', resulting in 'TFCI code word b0 ... b23'.](f0eaca8e167a863864b4ad9adb7ef16f_img.jpg) + +``` + +graph LR + A["TFCI (5 bits) +a4 ... a0"] --> B["(32,5) First order +Reed-Muller code"] + B --> C["Puncturing"] + C --> D["TFCI code word +b0 ... b23"] + +``` + +Figure 12: Channel coding of short TFCI bits for 8PSK. The diagram shows a flow from left to right: 'TFCI (5 bits) a4 ... a0' enters a box labeled '(32,5) First order Reed-Muller code', which then enters a box labeled 'Puncturing', resulting in 'TFCI code word b0 ... b23'. + +**Figure 12: Channel coding of short TFCI bits for 8PSK** + +If the TFCI consists of less than 5 bits, it is padded with zeros to 5 bits, by setting the most significant bits to zero. The code words of the punctured (32,5) first order Reed-Muller codes are linear combination of 5 basis sequences shown in Table 12. + +**Table 12: Basis sequences for (24,5) TFCI code** + +| I | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | +|----|------------------|------------------|------------------|------------------|------------------| +| 0 | 0 | 0 | 0 | 1 | 0 | +| 1 | 1 | 0 | 0 | 1 | 0 | +| 2 | 0 | 1 | 0 | 1 | 0 | +| 3 | 1 | 1 | 0 | 1 | 0 | +| 4 | 0 | 0 | 1 | 1 | 0 | +| 5 | 1 | 0 | 1 | 1 | 0 | +| 6 | 0 | 1 | 1 | 1 | 0 | +| 7 | 1 | 1 | 1 | 1 | 0 | +| 8 | 0 | 0 | 0 | 0 | 1 | +| 9 | 1 | 0 | 0 | 0 | 1 | +| 10 | 0 | 1 | 0 | 0 | 1 | +| 11 | 1 | 1 | 0 | 0 | 1 | +| 12 | 0 | 0 | 1 | 0 | 1 | +| 13 | 1 | 0 | 1 | 0 | 1 | +| 14 | 0 | 1 | 1 | 0 | 1 | +| 15 | 1 | 1 | 1 | 0 | 1 | +| 16 | 0 | 0 | 0 | 1 | 1 | +| 17 | 1 | 0 | 0 | 1 | 1 | +| 18 | 0 | 1 | 0 | 1 | 1 | +| 19 | 1 | 1 | 0 | 1 | 1 | +| 20 | 0 | 0 | 1 | 1 | 1 | +| 21 | 1 | 0 | 1 | 1 | 1 | +| 22 | 0 | 1 | 1 | 1 | 1 | +| 23 | 1 | 1 | 1 | 1 | 1 | + +Let's define the TFCI bits as $a_0, a_1, a_2, a_3, a_4$ , where $a_0$ is the LSB and $a_4$ is the MSB. The TFCI bits shall correspond to the TFC index (expressed in unsigned binary form) defined by the RRC layer to reference the TFC of the CCTrCH in the associated radio frame. + +The output code word bits $b_i$ are given by: + +$$b_i = \sum_{n=0}^4 (a_n \times M_{i,n}) \bmod 2$$ + +where $i=0 \dots 23$ . $N_{\text{TFCI code word}}=24$ . + +#### 4.4.2.3 Mapping of TFCI code word + +Denote the number of bits in the TFCI code word by $N_{\text{TFCI code word}}$ , and denote the TFCI code word bits by $b_k$ , where $k = 0, \dots, N_{\text{TFCI code word}} - 1$ . + +When the number of bits in the TFCI code word is 12, 24 or 48, the mapping of the TFCI code word to the TFCI bit positions in a time slot shall be as follows. + +![Diagram showing the mapping of TFCI code word bits to timeslot positions. The diagram illustrates a sequence of bits b_0, b_{N/4-1}, b_{N/4}, b_{N/2-1}, b_{N/2}, b_{3N/4-1}, b_{3N/4}, and b_{N-1} being mapped into a timeslot. The bits are grouped into four parts: 1st part (b_0 to b_{N/4-1}), 2nd part (b_{N/4} to b_{N/2-1}), 3rd part (b_{N/2} to b_{3N/4-1}), and 4th part (b_{3N/4} to b_{N-1}). Each part is shown as a block of bits with ellipses indicating intermediate bits. Arrows point from each part to its corresponding position in the timeslot.](86692d82da6655813b5acf58a767a38c_img.jpg) + +Diagram showing the mapping of TFCI code word bits to timeslot positions. The diagram illustrates a sequence of bits b\_0, b\_{N/4-1}, b\_{N/4}, b\_{N/2-1}, b\_{N/2}, b\_{3N/4-1}, b\_{3N/4}, and b\_{N-1} being mapped into a timeslot. The bits are grouped into four parts: 1st part (b\_0 to b\_{N/4-1}), 2nd part (b\_{N/4} to b\_{N/2-1}), 3rd part (b\_{N/2} to b\_{3N/4-1}), and 4th part (b\_{3N/4} to b\_{N-1}). Each part is shown as a block of bits with ellipses indicating intermediate bits. Arrows point from each part to its corresponding position in the timeslot. + +**Figure 13: Mapping of TFCI code word bits to timeslot in 1.28 Mcps TDD option, where $N = N_{\text{TFCI code word}}$ .** + +When the number of bits in the TFCI code word is 6, the TFCI code word is equally divided into two parts for the consecutive two sub-frames and mapped onto the first data field in each of the consecutive sub-frames. The mapping of the TFCI code word to the TFCI bit positions in a time slot shall be as shown in figure 14. + +![Figure 14: Mapping of TFCI code word bits to timeslot in 1.28 Mcps TDD option when N_TFCI code word = 6. The diagram shows a horizontal bar representing a timeslot, divided into four parts: '1st part of TFCI code word', '2nd part of TFCI code word', '3rd part of TFCI code word', and '4th part of TFCI code word'. Above the first part, bits b0, b1, b2 are shown with an arrow pointing down to it. Above the third part, bits b3, b4, b5 are shown with an arrow pointing down to it.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +Figure 14: Mapping of TFCI code word bits to timeslot in 1.28 Mcps TDD option when N\_TFCI code word = 6. The diagram shows a horizontal bar representing a timeslot, divided into four parts: '1st part of TFCI code word', '2nd part of TFCI code word', '3rd part of TFCI code word', and '4th part of TFCI code word'. Above the first part, bits b0, b1, b2 are shown with an arrow pointing down to it. Above the third part, bits b3, b4, b5 are shown with an arrow pointing down to it. + +**Figure 14: Mapping of TFCI code word bits to timeslot in 1.28 Mcps TDD option when $N_{\text{TFCI code word}} = 6$** + +The location of the 1st to 4th parts of the TFCI code word in the timeslot is defined in [7]. + +#### 4.4.3 Coding and Bit Scrambling of the Paging Indicator + +The paging indicator $P_q$ , $q = 0, \dots, N_{\text{PI}}-1$ , $P_q \in \{0, 1\}$ is an identifier to instruct the UE whether there is a paging message for the groups of mobiles that are associated to the PI, calculated by higher layers, and the associated paging indicator $P_q$ . The length $L_{\text{PI}}$ of the paging indicator is $L_{\text{PI}}=2$ , $L_{\text{PI}}=4$ or $L_{\text{PI}}=8$ symbols. $N_{\text{PIB}} = 2 * N_{\text{PI}} * L_{\text{PI}}$ bits are used for the paging indicator transmission in one radio frame. The mapping of the paging indicators to the bits $e_i$ , $i = 1, \dots, N_{\text{PIB}}$ is shown in table 13. + +**Table 13: Mapping of the paging indicator** + +| $P_q$ | Bits $\{e_{2L_{\text{PI}}q+1}, e_{2L_{\text{PI}}q+2}, \dots, e_{2L_{\text{PI}}(q+1)}\}$ | Meaning | +|-------|-----------------------------------------------------------------------------------------|-------------------------------------------| +| 0 | $\{0, 0, \dots, 0\}$ | There is no necessity to receive the PCH | +| 1 | $\{1, 1, \dots, 1\}$ | There is the necessity to receive the PCH | + +If the number $S$ of bits in one radio frame available for the PICH is bigger than the number $N_{\text{PIB}}$ of bits used for the transmission of paging indicators, the sequence $e = \{e_1, e_2, \dots, e_{N_{\text{PIB}}}\}$ is extended by $S - N_{\text{PIB}}$ bits that are set to zero, resulting in a sequence $h = \{h_1, h_2, \dots, h_S\}$ : + +$$\begin{aligned} h_k &= e_k, \quad k = 1, \dots, N_{\text{PIB}} \\ h_k &= 0, \quad k = N_{\text{PIB}} + 1, \dots, S \end{aligned}$$ + +The bits $h_k$ , $k = 1, \dots, S$ on the PICH then undergo bit scrambling as defined in section 4.2.9. + +The bits $s_k$ , $k = 1, \dots, S$ output from the bit scrambler are then transmitted over the air as shown in [7]. + +#### 4.4.4 Coding of the Fast Physical Access Channel (FPACH) information bits + +The FPACH burst is composed by 32 information bits which are block coded and convolutional coded, and then delivered in one sub-frame as follows: + +1. The 32 information bits are protected by 8 parity bits for error detection as described in sub-clause 4.2.1.1. +2. Convolutional code with constraint length 9 and coding rate $\frac{1}{2}$ is applied as described in sub-clause 4.2.3.1. The size of data block $c(k)$ after convolutional encoder is 96 bits. +3. To adjust the size of the data block $c(k)$ to the size of the FPACH burst, 8 bits are punctured as described in sub-clause 4.2.7 with the following clarifications: + - $N_{ij}=96$ is the number of bits in a radio sub-frame before rate matching + +- $\Delta N_{i,j} = -8$ is the number of bits to punctured in a radio sub-frame +- $e_{mi} = a \times N_{ij}$ + +The 88 bits after rate matching are then delivered to the intra-frame interleaving. + +4. The bits in input to the interleaving unit are denoted as $\{x(0), \dots, x(87)\}$ . The coded bits are block rectangular interleaved according to the following rule: the input is written row by row, the output is read column by column. + +$$\begin{bmatrix} x(0) & x(1) & x(2) & \dots & x(7) \\ x(8) & x(9) & x(10) & \dots & x(15) \\ \vdots & \vdots & \vdots & \dots & \vdots \\ x(80) & x(81) & x(82) & \dots & x(87) \end{bmatrix}$$ + +Hence, the interleaved sequence is denoted by $y(i)$ and are given by: + +$$y(0), y(1), \dots, y(87) = x(0), x(8), \dots, x(80), x(1), \dots, x(87).$$ + +#### 4.4.5 Coding and Bit Scrambling of the MBMS Notification Indicator + +The MBMS notification indicator $N_q$ , $q = 0, \dots, N_n-1$ , $N_q \in \{0, 1\}$ is an identifier to instruct the UE whether there is an MBMS notification indication for the groups of MBMS services that are associated to the NI, calculated by higher layers, and the associated MBMS notification indicator $N_q$ . The length $L_{NI}$ of the MBMS notification indicator is $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols. $N_{NIB} = 2 * N_n * L_{NI}$ bits are used for the MBMS notification indicator transmission in one MICH. The mapping of the MBMS notification indicators to the bits $e_i$ , $i = 1, \dots, N_{NIB}$ is shown in table 13A. + +**Table 13A: Mapping of the MBMS notification indicator** + +| $N_q$ | Bits $\{e_{2L_{NI}q+1}, e_{2L_{NI}q+2}, \dots, e_{2L_{NI}(q+1)}\}$ | +|-------|--------------------------------------------------------------------| +| 0 | $\{0, 0, \dots, 0\}$ | +| 1 | $\{1, 1, \dots, 1\}$ | + +If the number $S$ of bits available for the MICH is bigger than the number $N_{NIB}$ of bits used for the transmission of MBMS notification indicators, the sequence $e = \{e_1, e_2, \dots, e_{N_{NIB}}\}$ is extended by $S - N_{NIB}$ bits that are set to zero, resulting in a sequence $h = \{h_1, h_2, \dots, h_S\}$ : + +$$\begin{aligned} h_k &= e_k, \quad k = 1, \dots, N_{NIB} \\ h_k &= 0, \quad k = N_{NIB} + 1, \dots, S \end{aligned}$$ + +The bits $h_k$ , $k = 1, \dots, S$ on the MICH then undergo bit scrambling as defined in section 4.2.9. + +The bits $s_k$ , $k = 1, \dots, S$ output from the bit scrambler are then transmitted over the air as shown in [7]. + +#### 4.4.6 Coding of PLCCH + +The PLCCH is a Node-B terminated channel used to carry dedicated (UE-specific) TPC and SS information to multiple UEs. Each TPC/SS command pair for a given UE is mapped to 3 bits as shown in table 13B. + +**Table 13B: Mapping of the TPC/SS pair** + +| 3-bit TPC/SS command
(MSB on left) | TPC command | SS command | +|---------------------------------------|-------------|--------------| +| 000 | 'DOWN' | 'DOWN' | +| 100 | 'UP' | 'DOWN' | +| 011 | 'DOWN' | 'UP' | +| 111 | 'UP' | 'UP' | +| 001 | 'DOWN' | 'Do Nothing' | +| 101 | 'UP' | 'Do Nothing' | + +Let $I=14$ be the number of TPC/SS command pairs that can be carried by a single PLCCH. The 3 bits corresponding to the $i^{\text{th}}$ TPC/SS command pair ( $i=1 \dots I$ ), are denoted $\{c_{i,0}, c_{i,1}, c_{i,2}\}$ where $c_{i,0}$ is the MSB. + +The bit sequence corresponding to the $I=14$ TPC/SS command pairs is denoted $(k=0,1,2,\dots,41)$ . $(n=0,1,2)$ is mapped to $c_{i,n}$ such that: + +The PLCCH burst is composed of 44 information bits $\{b_{\text{plcch}}(0), b_{\text{plcch}}(1), \dots, b_{\text{plcch}}(43)\}$ which are repetition coded, and then delivered in one sub-frame as follows: + +1. $b_{\text{plcch}}(m) = 1$ (for $m=0,1,\dots,41$ ) and $b_{\text{plcch}}(m) = 0$ (for $m=42,43$ ) +2. Repetition coding with code rate $1/2$ is applied to the sequence $\{b_{\text{plcch}}(0), \dots, b_{\text{plcch}}(43)\}$ in order to form the sequence $\{x(0), x(1), x(2), x(3), \dots, x(86), x(87)\}$ . The size of the data block after the repetition encoder is 88 bits. The encoded codeword $\{x(0), x(1), x(2), x(3), \dots, x(86), x(87)\}$ is equal to $\{b_{\text{plcch}}(0), b_{\text{plcch}}(0), b_{\text{plcch}}(1), b_{\text{plcch}}(1), \dots, b_{\text{plcch}}(43), b_{\text{plcch}}(43)\}$ . +3. The bits output from the repetition encoder $\{x(0), \dots, x(87)\}$ are input to an interleaving unit. The coded bits are block rectangular interleaved according to the following rule: the input is written row by row, the output is read column by column. + +$$\begin{bmatrix} x(0) & x(1) & x(2) & \dots & x(7) \\ x(8) & x(9) & x(10) & \dots & x(15) \\ \vdots & \vdots & \vdots & \dots & \vdots \\ x(80) & x(81) & x(82) & \dots & x(87) \end{bmatrix}$$ + +Hence, the interleaved sequence is denoted by $y(i)$ and is given by: + +$$y(0), y(1), \dots, y(87) = x(0), x(8), \dots, x(80), x(1), \dots, x(87).$$ + +The bit sequence $y(0), y(1), \dots, y(87)$ is mapped to the PLCCH burst in order of bit index, with the lowest bit index being the first bit (in time) to be transmitted. + +## 4.5 Coding for HS-DSCH + +Figure 15 illustrates the overall concept of transport-channel coding for HS-DSCH. Data arrives at the coding unit in the form of one transport block once every TTI. The TTI is 5 ms for 1.28 Mcps TDD and 10 ms for 3.84 Mcps TDD / 7.68 Mcps TDD. + +For 1.28 Mcps TDD, in the case of multiple-frequency transmission in one TTI, a number of transport blocks arrive at the coding unit, in which the number of transport blocks equals the number of frequencies used. Each transport block for each frequency shall be coded separately as the following coding step. + +For 1.28 Mcps TDD, in the case of MIMO dual stream transmission in one TTI, two transport blocks arrive at the coding unit. Each transport block for each data stream shall be coded separately as the following coding step. + +The following coding steps for HS-DSCH can be identified: + +- add CRC to each transport block (see subclause 4.5.1); +- code block segmentation (see subclause 4.5.2); +- channel coding (see subclause 4.5.3); +- hybrid ARQ (see subclause 4.5.4); +- bit scrambling (see subclause 4.5.5); +- interleaving for HS-DSCH (see subclause 4.5.6); +- constellation re-arrangement for 16QAM and 64QAM (see subclause 4.5.7); + +- mapping to physical channels (see subclause 4.5.8). + +The coding steps for HS-DSCH are shown in figure 15. + +![Flowchart of the coding chain for HS-DSCH. The process starts with input bits a_im1, a_im2, a_im3, ..., a_imA. It proceeds through CRC attachment, resulting in bits b_im1, b_im2, b_im3, ..., b_imB. This is followed by code block segmentation, resulting in bits o_ir1, o_ir2, o_ir3, ..., o_irK. The next step is Channel Coding, resulting in bits c_i1, c_i2, c_i3, ..., c_iE. This is followed by Physical Layer Hybrid-ARQ functionality, resulting in bits w_1, w_2, w_3, ..., w_R. The next step is Bit Scrambling, resulting in bits s_1, s_2, s_3, ..., s_R. This is followed by HS-DSCH Interleaving, resulting in bits v_1, v_2, v_3, ..., v_R. The next step is Constellation re-arrangement for 16 QAM, resulting in bits r_1, r_2, r_3, ..., r_R. The final step is Physical channel mapping, resulting in bits w_t,p,1, w_t,p,2, ..., w_t,p,Up. The output is then split into two channels: PhCH#1 and PhCH#P.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + + graph TD + Input[" $a_{im1}, a_{im2}, a_{im3}, \dots, a_{imA}$ "] --> CRC[CRC attachment] + CRC --> BitsB[" $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB}$ "] + BitsB --> Segmentation[Code block segmentation] + Segmentation --> BitsK[" $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK}$ "] + BitsK --> ChannelCoding[Channel Coding] + ChannelCoding --> BitsE[" $c_{i1}, c_{i2}, c_{i3}, \dots, c_{iE}$ "] + BitsE --> HybridARQ[Physical Layer Hybrid-ARQ functionality] + HybridARQ --> BitsR[" $w_1, w_2, w_3, \dots, w_R$ "] + BitsR --> BitScrambling[Bit Scrambling] + BitScrambling --> BitsSR[" $s_1, s_2, s_3, \dots, s_R$ "] + BitsSR --> HSDSCHInterleaving[HS-DSCH Interleaving] + HSDSCHInterleaving --> BitsVR[" $v_1, v_2, v_3, \dots, v_R$ "] + BitsVR --> Constellation[Constellation re-arrangement for 16 QAM] + Constellation --> BitsrR[" $r_1, r_2, r_3, \dots, r_R$ "] + BitsrR --> PhysicalMapping[Physical channel mapping] + PhysicalMapping --> BitsUp[" $w_{t,p,1}, w_{t,p,2}, \dots, w_{t,p,Up}$ "] + BitsUp --> PhCH1[PhCH#1] + BitsUp --> PhCHP[PhCH#P] + +``` + +Flowchart of the coding chain for HS-DSCH. The process starts with input bits a\_im1, a\_im2, a\_im3, ..., a\_imA. It proceeds through CRC attachment, resulting in bits b\_im1, b\_im2, b\_im3, ..., b\_imB. This is followed by code block segmentation, resulting in bits o\_ir1, o\_ir2, o\_ir3, ..., o\_irK. The next step is Channel Coding, resulting in bits c\_i1, c\_i2, c\_i3, ..., c\_iE. This is followed by Physical Layer Hybrid-ARQ functionality, resulting in bits w\_1, w\_2, w\_3, ..., w\_R. The next step is Bit Scrambling, resulting in bits s\_1, s\_2, s\_3, ..., s\_R. This is followed by HS-DSCH Interleaving, resulting in bits v\_1, v\_2, v\_3, ..., v\_R. The next step is Constellation re-arrangement for 16 QAM, resulting in bits r\_1, r\_2, r\_3, ..., r\_R. The final step is Physical channel mapping, resulting in bits w\_t,p,1, w\_t,p,2, ..., w\_t,p,Up. The output is then split into two channels: PhCH#1 and PhCH#P. + +**Figure 15: Coding chain for HS-DSCH** + +In the following the number of transport blocks is always one. When referencing non HS-DSCH formulae which are used in correspondence with HS-DSCH formulae the convention is used that transport block subscripts may be omitted (e.g. $X_i$ when $i$ is always 1 may be written $X$ ). + +### 4.5.1 CRC attachment for HS-DSCH + +A CRC of size 24 bits is calculated and added per HS-DSCH TTI. The CRC polynomial is defined in 4.2.1.1 with the following specific parameters: $i = 1$ , $L_i = 24$ bits. + +### 4.5.2 Code block segmentation for HS-DSCH + +Code block segmentation for the HS-DSCH transport channel shall be done with the general method described in 4.2.2.2 above with the following specific parameters. + +There will only be one transport block, $i = 1$ . The bits $b_{im1}, b_{im2}, b_{im3}, \dots, b_{imB}$ input to the block are mapped to the bits $x_{i1}, x_{i2}, x_{i3}, \dots, x_{iX_i}$ directly. It follows that $X_i = B$ . Note that the bits $x$ referenced here refer only to the internals of the code block segmentation function. The output bits from the code block segmentation function are $o_{ir1}, o_{ir2}, o_{ir3}, \dots, o_{irK}$ . + +The value of $Z = 5114$ for turbo coding shall be used. + +### 4.5.3 Channel coding for HS-DSCH + +Channel coding for the HS-DSCH transport channel shall be done with the general method described in 4.2.3 above with the following specific parameters. + +There will be a maximum of one transport block, $i = 1$ . The rate 1/3 turbo coding shall be used. + +### 4.5.4 Hybrid ARQ for HS-DSCH + +The hybrid ARQ functionality matches the number of bits at the output of the channel coder to the total number of bits of the HS-PDSCH set to which the HS-DSCH is mapped. The hybrid ARQ functionality is controlled by the redundancy version (RV) parameters. The exact set of bits at the output of the hybrid ARQ functionality depends on the number of input bits, the number of output bits, and the RV parameters. + +The hybrid ARQ functionality consists of two rate-matching stages and a virtual buffer as shown in the figure below. + +The first rate matching stage matches the number of input bits to the virtual IR buffer, information about which is provided by higher layers. Note that, if the number of input bits does not exceed the virtual IR buffering capability, the first rate-matching stage is transparent. + +The second rate matching stage matches the number of bits after first rate matching stage to the number of physical channel bits available in the HS-PDSCH set in the TTI. + +![Figure 16: HS-DSCH hybrid ARQ functionality diagram. The diagram shows the flow of bits through three main stages: First Rate Matching, Virtual IR Buffer, and Second Rate Matching. Input bits (C) are separated into Systematic bits, Parity 1 bits, and Parity 2 bits. Systematic bits pass through the First Rate Matching stage (RM_S) to the Virtual IR Buffer (N_sys). Parity 1 bits pass through RM_P1_1 to the Virtual IR Buffer (N_p1). Parity 2 bits pass through RM_P2_1 to the Virtual IR Buffer (N_p2). The Virtual IR Buffer outputs bits to the Second Rate Matching stage: Systematic bits (N_tsys) through RM_S, Parity 1 bits (N_tp1) through RM_P1_2, and Parity 2 bits (N_tp2) through RM_P2_2. The outputs of the Second Rate Matching stage are then collected by a bit collection block to produce the final output (W).](9dd03da031e134bfc9ecc730dd5f6583_img.jpg) + +Figure 16: HS-DSCH hybrid ARQ functionality diagram. The diagram shows the flow of bits through three main stages: First Rate Matching, Virtual IR Buffer, and Second Rate Matching. Input bits (C) are separated into Systematic bits, Parity 1 bits, and Parity 2 bits. Systematic bits pass through the First Rate Matching stage (RM\_S) to the Virtual IR Buffer (N\_sys). Parity 1 bits pass through RM\_P1\_1 to the Virtual IR Buffer (N\_p1). Parity 2 bits pass through RM\_P2\_1 to the Virtual IR Buffer (N\_p2). The Virtual IR Buffer outputs bits to the Second Rate Matching stage: Systematic bits (N\_tsys) through RM\_S, Parity 1 bits (N\_tp1) through RM\_P1\_2, and Parity 2 bits (N\_tp2) through RM\_P2\_2. The outputs of the Second Rate Matching stage are then collected by a bit collection block to produce the final output (W). + +Figure 16: HS-DSCH hybrid ARQ functionality + +#### 4.5.4.1 HARQ bit separation + +The HARQ bit separation function shall be performed in the same way as bit separation for turbo encoded TrCHs in 4.2.7.2 above. + +#### 4.5.4.2 HARQ First Rate Matching Stage + +HARQ first stage rate matching for the HS-DSCH transport channel shall be done with the general method described in 4.2.7.1.2 above with the following specific parameters. + +The maximum number of soft channel bits available in the virtual IR buffer is $N_{IR}$ which is signalled from higher layers for each HARQ process. The number of coded bits in a TTI before rate matching is $N^{TTI}$ this is deduced from information signalled from higher layers and parameters signalled on the HS-SCCH for each TTI. Note that HARQ processing and physical layer storage occurs independently for each HARQ process currently active. + +If $N_{IR}$ is greater than or equal to $N^{TTI}$ (i.e. all coded bits of the corresponding TTI can be stored) the first rate matching stage shall be transparent. This can, for example, be achieved by setting $e_{minus} = 0$ . Note that no repetition is performed. + +If $N_{IR}$ is smaller than $N^{TTI}$ the parity bit streams are punctured as in 4.2.7.1.2 above by setting the rate matching parameter where the subscripts i and l refer to transport channel and transport format in the referenced sub-clause. Note the negative value is expected when the rate matching implements puncturing. Bits selected for puncturing which appear as $\delta$ in the algorithm in 4.2.7 above shall be discarded and not counted in the totals for the streams through the virtual IR buffer. + +#### 4.5.4.3 HARQ Second Rate Matching Stage + +HARQ second stage rate matching for the HS-DSCH transport channel shall be done with the general method described in 4.2.7.3 above with the following specific parameters. Bits selected for puncturing which appear as $\delta$ in the algorithm in 4.2.7.3 above shall be discarded and are not counted in the streams towards the bit collection. + +The parameters of the second rate matching stage depend on the value of the RV parameters s and r. The parameter s can take the value 0 or 1 to distinguish between transmissions that prioritise systematic bits ( $s = 1$ ) and non systematic bits ( $s = 0$ ). The parameter r (range 0 to $r_{max}-1$ ) changes the initial error variable $e_{ini}$ in the case of puncturing. In case of repetition both parameters r and s change the initial error variable $e_{ini}$ . The parameters $X_i$ , $e_{plus}$ and $e_{minus}$ are calculated as per table 14 below. + +Denote the number of bits before second rate matching as $N_{sys}$ for the systematic bits, $N_{p1}$ for the parity 1 bits, and $N_{p2}$ for the parity 2 bits, respectively. For the HS-DSCH, denote the number of timeslots used as $T$ , the number of codes per timeslot as $C$ and the number of bits available in timeslot $t$ as $U_t$ , where $U_t$ is the number of bits available in physical channel of timeslot $t$ as defined in [7]. $N_{data}$ is the number of bits available to the HS-DSCH in one TTI and is defined as . The rate matching parameters are determined as follows. + +For , puncturing is performed in the second rate matching stage. The number of transmitted systematic bits in a transmission is for a transmission that prioritises systematic bits and for a transmission that prioritises non systematic bits. + +For repetition is performed in the second rate matching stage. A similar repetition rate in all bit streams is achieved by setting the number of transmitted systematic bits to . + +The number of parity bits in a transmission is: and for the parity 1 and parity 2 bits, respectively. + +Table 14 below summarizes the resulting parameter choice for the second rate matching stage. + +**Table 14: Parameters for HARQ second rate matching** + +| | $X_i$ | $e_{plus}$ | $e_{minus}$ | +|---------------------|-------|------------|-------------| +| Systematic
RM S | | | | +| Parity 1
RM P1_2 | | | | +| Parity 2
RM P2_2 | | | | + +The rate matching parameter $e_{ini}$ is calculated for each bit stream according to the RV parameters r and s using in the case of puncturing, i.e., and + +for repetition, i.e.,. + +Where $r \in \{0, 1, \dots, r_{max} - 1\}$ and $r_{max}$ is the total number of redundancy versions allowed by varying $r$ as defined in 4.6.1.4. + +Note that $r_{max}$ varies depending on the modulation mode, i.e. for 16QAM and 64QAM $r_{max} = 2$ and for QPSK $r_{max} = 4$ . + +Note: For the modulo operation the following clarification is used: the value of $(x \bmod y)$ is strictly in the range of 0 to $y-1$ (i.e. $-1 \bmod 10 = 9$ ). + +#### 4.5.4.4 HARQ bit collection + +The HARQ bit collection is achieved using a rectangular interleaver of size $N_{row} \times N_{col}$ . + +The number of rows and columns are determined from: + +for 64QAM + +for 16QAM + +for QPSK + +where $N_{data}$ is used as defined in 4.5.4.3 above. + +Data is written into the interleaver column by column, and read out of the interleaver column by column, starting from the first column. + +$N_{t,sys}$ is the number of transmitted systematic bits. Intermediate values $N_r$ and $N_c$ are calculated using: + +and . + +If $N_c = 0$ and $N_r > 0$ , the systematic bits are written into rows $1 \dots N_r$ . + +Otherwise systematic bits are written into rows $1 \dots N_r + 1$ in the first $N_c$ columns and, if $N_r > 0$ , also into rows $1 \dots N_r$ in the remaining $N_{col} - N_c$ columns. + +The remaining space is filled with parity bits. The parity bits are written column wise into the remaining rows of the respective columns. Parity 1 and 2 bits are written in alternating order, starting with a parity 2 bit in the first available column with the lowest index number. + +In the case of 64QAM for each column the bits are read out of the interleaver in the order row1, row2, row3, row4, row5, row6. In the case of 16QAM for each column the bits are read out of the interleaver in the order row 1, row 2, row 3, row 4. In the case of QPSK for each column the bits are read out of the interleaver in the order row1, row2. + +#### 4.5.5 Bit scrambling + +The bit scrambling for HS-DSCH shall be done with the general method described in subclause 4.2.9. + +#### 4.5.6 Interleaving for HS-DSCH + +The interleaving for TDD is done over all bits in the TTI, as shown in figure 17 when QPSK modulation is being used for the HS-DSCH, and figure 18 when 16-QAM modulation is being used, and figure 18a when 64QAM modulation is being used. The bits input to the block interleaver are denoted by $s_1, s_2, s_3, \dots, s_R$ , where $R$ is the number of bits in one TTI. + +![Diagram of the interleaver structure for HS-DSCH with QPSK modulation. It shows a block interleaver labeled 'Block Interleaver (R2 x 30)'. The input sequence is s1, s2, ..., sR, and the output sequence is v1, v2, ..., vR.](c32236ab37ba84aaaefca890cf6deab6_img.jpg) + +``` + +graph LR + Input["s1, s2, ..., sR"] --> Interleaver["Block Interleaver (R2 x 30)"] + Interleaver --> Output["v1, v2, ..., vR"] + +``` + +Diagram of the interleaver structure for HS-DSCH with QPSK modulation. It shows a block interleaver labeled 'Block Interleaver (R2 x 30)'. The input sequence is s1, s2, ..., sR, and the output sequence is v1, v2, ..., vR. + +**Figure 17: Interleaver structure for HS-DSCH with QPSK modulation** + +For QPSK, the interleaver is a block interleaver and consists of bits input to a matrix with padding, the inter-column permutation for the matrix and bits output from the matrix with pruning. The output bit sequence from the block interleaver is derived as follows: + +- (1) The number of columns of the matrix is 30. The columns of the matrix are numbered 0, 1, 2, ..., 29 from left to right. +- (2) Determine the number of rows of the matrix, $R2$ , by finding minimum integer $R2$ such that $R \leq 30 \times R2$ . The rows of rectangular matrix are numbered 0, 1, 2, ..., $R2 - 1$ from top to bottom. + +- (3) Write the input bit sequence $s_1, s_2, s_3, \dots, s_R$ into the $R2 \times 30$ matrix row by row starting with bit $y_1$ in column 0 of row 0: + +where $y_k = s_k$ for $k = 1, 2, \dots, R$ and, if $R < 30 \times R2$ , dummy bits are inserted for $k = R+1, R+2, \dots, 30 \times R2$ . These dummy bits are pruned away from the output of the matrix after the inter-column permutation. + +- (4) Perform the inter-column permutation for the matrix based on the pattern that is shown in Table 7, where $P2(j)$ is the original column position of the $j$ -th permuted column. After permutation of the columns, the bits are denoted by $y'_k$ . + +- (5) The output of the block interleaver is the bit sequence read out column by column from the inter-column permuted $R2 \times 30$ matrix. The output is pruned by deleting dummy bits that were padded to the input of the matrix before the inter-column permutation, i.e. bits $y'_k$ that corresponds to bits $y_k$ with $k > R$ are removed from the output. The bits after interleaving are denoted by $v_1, v_2, v_3, \dots, v_R$ , where $v_1$ corresponds to the bit $y'_k$ with smallest index $k$ after pruning, $v_2$ to the bit $y'_k$ with second smallest index $k$ after pruning, and so on. + +![Figure 18: Interleaver structure for HS-DSCH with 16-QAM modulation. The diagram shows two parallel Block Interleaver (R2 x 30) units. The top interleaver takes an input sequence s1, s2, s5, s6, ..., sR-3, sR-2 and produces an output sequence v1, v2, v5, v6, ..., vR-3, vR-2. The bottom interleaver takes an input sequence s3, s4, s7, s8, ..., sR-1, sR and produces an output sequence v3, v4, v7, v8, ..., vR-1, vR. The final output is a combination of these two sequences: v1, v2, ..., vR.](9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg) + +Figure 18: Interleaver structure for HS-DSCH with 16-QAM modulation. The diagram shows two parallel Block Interleaver (R2 x 30) units. The top interleaver takes an input sequence s1, s2, s5, s6, ..., sR-3, sR-2 and produces an output sequence v1, v2, v5, v6, ..., vR-3, vR-2. The bottom interleaver takes an input sequence s3, s4, s7, s8, ..., sR-1, sR and produces an output sequence v3, v4, v7, v8, ..., vR-1, vR. The final output is a combination of these two sequences: v1, v2, ..., vR. + +Figure 18: Interleaver structure for HS-DSCH with 16-QAM modulation + +For 16QAM, a second identical interleaver operates in parallel to the first. For both interleavers, $R2$ is chosen to be the minimum integer that satisfies $R \leq 60 \times R2$ . The output bits from the bit scrambling operation are divided pairwise between the interleavers: bits $s_k$ and $s_{k+1}$ go to the first interleaver and bits $s_{k+2}$ and $s_{k+3}$ go to the second interleaver, where $k \bmod 4 = 1$ . Bits are collected pairwise from the interleavers: bits $v_k$ and $v_{k+1}$ are obtained from the first interleaver and bits $v_{k+2}$ and $v_{k+3}$ are obtained from the second interleaver, where again $k \bmod 4 = 1$ . + +![Figure 18a: Interleaver structure for HS-DSCH with 64-QAM modulation. The diagram shows three parallel Block Interleaver (R2 x 30) units. The top interleaver takes an input sequence s1, s2, s7, s8, ..., sR-5, sR-4 and produces an output sequence v1, v2, v7, v8, ..., vR-5, vR-4. The middle interleaver takes an input sequence s3, s4, s9, s10, ..., sR-3, sR-2 and produces an output sequence v3, v4, v9, v10, ..., vR-3, vR-2. The bottom interleaver takes an input sequence s5, s6, s11, s12, ..., sR-1, sR and produces an output sequence v5, v6, v11, v12, ..., vR-1, vR. The final output is a combination of these three sequences: v1, v2, ..., vR.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg) + +Figure 18a: Interleaver structure for HS-DSCH with 64-QAM modulation. The diagram shows three parallel Block Interleaver (R2 x 30) units. The top interleaver takes an input sequence s1, s2, s7, s8, ..., sR-5, sR-4 and produces an output sequence v1, v2, v7, v8, ..., vR-5, vR-4. The middle interleaver takes an input sequence s3, s4, s9, s10, ..., sR-3, sR-2 and produces an output sequence v3, v4, v9, v10, ..., vR-3, vR-2. The bottom interleaver takes an input sequence s5, s6, s11, s12, ..., sR-1, sR and produces an output sequence v5, v6, v11, v12, ..., vR-1, vR. The final output is a combination of these three sequences: v1, v2, ..., vR. + +Figure 18a: Interleaver structure for HS-DSCH with 64-QAM modulation + +The interleaving for TDD is done over all bits in the TTI, as shown in figure 18a when 64QAM modulation is being used for the HS-DSCH. The bits input to the block interleaver are denoted by $s_1, s_2, s_3, \dots, s_R$ , where $R$ is the number of bits in one TTI. + +For 64QAM, two identical interleavers operate in parallel to the first. For all interleavers, $R2$ is chosen to be the minimum integer that satisfies $R \leq 90 \times R2$ . The output bits from the bit scrambling operation are divided into three parts of different interleavers: bits $s_k$ and $s_{k+1}$ go to the first interleaver, bits $s_{k+2}$ and $s_{k+3}$ go to the second interleaver and bits $s_{k+4}$ and $s_{k+5}$ go to the third interleaver, where $k \bmod 6 = 1$ . Bits are collected accordingly from the interleavers: bits $v_k$ and $v_{k+1}$ are obtained from the first interleaver, bits $v_{k+2}$ and $v_{k+3}$ are obtained from the second interleaver and bits $v_{k+4}$ and $v_{k+5}$ are obtained from the third interleaver, where again $k \bmod 6 = 1$ . + +#### 4.5.7 Constellation re-arrangement for 16 QAM and 64 QAM + +This function only applies to 16 QAM modulated bits. In case of QPSK it is transparent. + +The following table 15 describes the operations that produce the different rearrangements. + +The bits of the input sequence are mapped in groups of 4 so that $v_k, v_{k+1}, v_{k+2}, v_{k+3}$ are used, where $k \bmod 4 = 1$ . + +**Table 15: Constellation re-arrangement for 16 QAM** + +| Constellation version parameter $b$ | Output bit sequence | Operation | +|-------------------------------------|---------------------|----------------------------------------------------------------------| +| 0 | | None | +| 1 | | Swapping MSBs with LSBs | +| 2 | | Inversion of the logical values of LSBs | +| 3 | | Swapping MSBs with LSBs, and inversion of the logical values of LSBs | + +The output bit sequences from the table above map to the output bits in groups of 4, i.e. $r_k, r_{k+1}, r_{k+2}, r_{k+3}$ , where $k \bmod 4 = 1$ . + +The following table 15a describes the operations that produce the different rearrangements of 64 QAM. + +The bits of the input sequence are mapped in groups of 6 so that $v_k, v_{k+1}, v_{k+2}, v_{k+3}, v_{k+4}, v_{k+5}$ are used, where $k \bmod 6 = 1$ . + +**Table 15a: Constellation re-arrangement for 64 QAM** + +| Constellation version parameter $b$ | Output bit sequence | Operation | +|-------------------------------------|---------------------|-------------------------------------------------------------| +| 0 | | None | +| 1 | | Swapping MSBs and LSBs. Inversion of Middle SBs | +| 2 | | Left circular shift of pair of SBs. Inversion of Middle SBs | +| 3 | | Inversion of Middle SBs | + +The output bit sequences from the table above map to the output bits in groups of 6, i.e. $r_k, r_{k+1}, r_{k+2}, r_{k+3}, r_{k+4}, r_{k+5}$ , where $k \bmod 6 = 1$ . + +#### 4.5.8 Physical channel mapping for HS-DSCH + +The HS-PDSCH is defined in [7]. The bits input to the physical channel mapping are denoted by $r_1, r_2, \dots, r_R$ , where $R$ is the number of physical channel bits in the allocation for the current TTI. These bits are mapped to the physical channel bits, $\{w_{t,p,j} : t = 1, 2, \dots, T; p = 1, 2, \dots, C; j = 1, 2, \dots, U_{t,p}\}$ , where $t$ is the timeslot index, $T$ is the number of timeslots in the allocation message, $p$ is the physical channel index, $C$ is the number of codes per timeslot in the allocation message, $j$ is the physical channel bit index and $U_{t,p}$ is the number of bits for the physical channel $p$ in timeslot $t$ . The timeslot index, $t$ , increases with increasing timeslot number; the physical channel index, $p$ , increases with increasing channelisation code index, and the physical channel bit index, $j$ , increases with increasing physical channel bit position in time. If TS0 is included in the allocation message, TS0 has the maximum timeslot index while the timeslot index of any other timeslot increases with increasing timeslot number. + +The bits $r_k$ shall be mapped to the PhCHs according to the following rule : + +Define $\{y_{t,k} : k = 1, 2, \dots\}$ to be the set of bits to be transmitted in timeslot $t$ as follows : + +for $k = 1, 2, \dots$ , + +for $k = 1, 2, \dots,$ + +... + +for $k = 1, 2, \dots,$ + +When the modulation level applied to the physical channels is 16- QAM : + +The physical channel $p$ used to transmit the $k^{\text{th}}$ bit in the sequence $y_{i,k}$ is : + +if ( $k \leq U_{i,r} C$ ) + +If $p$ is odd then : + +where + +If $p$ is even then : + +where + +else + +If $p$ is odd then : + +where + +If $p$ is even then : + +where + +Otherwise, when the modulation level applied to the physical channels is QPSK : + +The physical channel $p$ used to transmit the $k^{\text{th}}$ bit in the sequence $y_{i,k}$ is : + +if ( $k \leq U_{i,r} C$ ) + +If $p$ is odd then : + +where + +If $p$ is even then : + +where + +else + +If $p$ is odd then : + +where + +If $p$ is even then : + +where + +When the modulation level applied to the physical channels is 64-QAM: + +The physical channel $p$ used to transmit the $k^{\text{th}}$ bit in the sequence $y_{i,k}$ is: + +If $p$ is odd then : + +where + +If $p$ is even then : + +where + +## 4.6 Coding/Multiplexing for HS-SCCH + +For 1.28 Mcps TDD, HS-SCCH shall be of type 1 when the following two conditions are both true: + +- the UE is not configured in MIMO mode, and +- the variable HS\_DSCH\_SPS\_STATUS is FALSE. + +HS-SCCH type 1 may be used when the following two conditions are both true: + +- the UE is not configured in MIMO mode, and +- the variable HS\_DSCH\_SPS\_STATUS is TRUE. + +In this section, the terms "HS-SCCH" and "HS-SCCH type 1" are used interchangeably. + +The following information, provided by higher layers, is transmitted by means of the HS-SCCH physical channel. + +For 1.28 Mcps TDD, in the case of multi-frequency HS-DSCH transmission in one TTI, HS-PDSCH on each frequency shall be configured with associated HS-SCCH(s) which is coded and multiplexed as following. + +- Channelisation-code-set information ( $q$ bits where $q = 8$ for 1.28 Mcps TDD / 3.84 Mcps TDD and $q = 10$ for 7.68 Mcps TDD): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,q}$ +- Time slot information ( $n$ bits where $n = 5$ for 1.28 Mcps TDD and $n = 13$ for 3.84 Mcps TDD / 7.68 Mcps TDD): + $x_{ts,1}, x_{ts,2}, \dots, x_{ts,n}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Transport-block size information ( $m$ bits where $m = 6$ for 1.28 Mcps TDD and $m = 9$ for 3.84 Mcps TDD / 7.68 Mcps TDD): + $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,m}$ +- Hybrid-ARQ process information (3 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}$ +- Redundancy version information (3 bits): $x_{rv,1}, x_{rv,2}, x_{rv,3}$ +- New data indicator (1 bit): $x_{nd,1}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +For an HS-SCCH order type A for 1.28 Mcps TDD, + +- $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,q}$ are reserved +- $x_{ts,1}, x_{ts,2}, \dots, x_{ts,n}$ shall be set to '00000' +- $x_{ms,1}, x_{tbs,1}, x_{tbs,2}$ shall be set to $x_{odt,1}, x_{odt,2}, x_{odt,3}$ +- $x_{tbs,3}, x_{tbs,4}, \dots, x_{tbs,m}, x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{rv,1}, x_{rv,2}, x_{rv,3}, x_{nd,1}, x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ are reserved + +where $x_{odt,1}, x_{odt,2}, x_{odt,3}$ are defined in subclause 4.6A. + +The following coding/multiplexing steps can be identified: + +- multiplexing of HS-SCCH information (see subclause 4.6.2) +- CRC attachment (see subclause 4.6.3); +- channel coding (see subclause 4.6.4); + +- rate matching (see subclause 4.6.5); +- interleaving for HS-SCCH (see subclause 4.6.6); +- mapping to physical channels (see subclauses 4.6.7 and 4.6.8). + +The general coding/multiplexing flow is shown in Figure 19. + +![Figure 19: Coding and Multiplexing for HS-SCCH flowchart. The process starts with multiple input bit sequences: x_{ccs,1}...x_{ccs,7}, x_{ms,1}, x_{tfas}, x_{tfm}, x_{hapha}, x_{r1}...x_{r3}, x_{nd,1}, x_{has}, and x_{hc}. These are first multiplexed. The output of the multiplexing block (bits q) is then processed through a series of steps: CRC attachment (with input x_{ue,1}...x_{ue,16}), Channel Coding (output bits b), Rate Matching (output bits g), Interleaving (output bits f), Physical Channel Segmentation (output bits v), and finally Physical Channel Mapping (output bits u). The final output is split into multiple physical channels, labeled PhCH#1 and PhCH#n.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` + + graph TD + In1[x_ccs,1...x_ccs,7] --> Mux[multiplexing] + In2[x_ms,1] --> Mux + In3[x_tfas, x_tfm] --> Mux + In4[x_hapha] --> Mux + In5[x_r1...x_r3] --> Mux + In6[x_nd,1] --> Mux + In7[x_has, x_hc] --> Mux + Mux --> |q1, q2, q3| CRC[CRC attachment] + UE[x_ue,1...x_ue,16] --> CRC + CRC --> |b1, b2, b3| CC[Channel Coding] + CC --> |g1, g2, g3| RM[Rate Matching] + RM --> |f1, f2, f3| Int[Interleaving] + Int --> |v1, v2, v3| PCS[Physical Channel Segmentation] + PCS --> |u1, u2, u3| PCM[Physical Channel Mapping] + PCM --> PhCH1[PhCH#1] + PCM --> PhCHn[PhCH#n] + +``` + +Figure 19: Coding and Multiplexing for HS-SCCH flowchart. The process starts with multiple input bit sequences: x\_{ccs,1}...x\_{ccs,7}, x\_{ms,1}, x\_{tfas}, x\_{tfm}, x\_{hapha}, x\_{r1}...x\_{r3}, x\_{nd,1}, x\_{has}, and x\_{hc}. These are first multiplexed. The output of the multiplexing block (bits q) is then processed through a series of steps: CRC attachment (with input x\_{ue,1}...x\_{ue,16}), Channel Coding (output bits b), Rate Matching (output bits g), Interleaving (output bits f), Physical Channel Segmentation (output bits v), and finally Physical Channel Mapping (output bits u). The final output is split into multiple physical channels, labeled PhCH#1 and PhCH#n. + +**Figure 19 Coding and Multiplexing for HS-SCCH** + +#### 4.6.1 HS-SCCH information field mapping + +##### 4.6.1.1 Channelisation code set information mapping + +###### 4.6.1.1.1 1.28Mcps TDD and 3.84Mcps TDD + +HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code. The start code $k_{start}$ is signalled by the bits $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}$ and the stop code $k_{stop}$ by the bits $x_{ccs,5}, x_{ccs,6}, x_{ccs,7}, x_{ccs,8}$ . The mapping in Table 16 below applies. + +Table 16: Channelisation code set information mapping for 1.28Mcps and 3.84Mcps TDD + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | $k_{stop}$ | $x_{ccs,5}$ | $x_{ccs,6}$ | $x_{ccs,7}$ | $x_{ccs,8}$ | +|-------------|-------------|-------------|-------------|-------------|------------|-------------|-------------|-------------|-------------| +| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | 1 | 2 | 0 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 3 | 0 | 0 | 1 | 0 | +| 4 | 0 | 0 | 1 | 1 | 4 | 0 | 0 | 1 | 1 | +| 5 | 0 | 1 | 0 | 0 | 5 | 0 | 1 | 0 | 0 | +| 6 | 0 | 1 | 0 | 1 | 6 | 0 | 1 | 0 | 1 | +| 7 | 0 | 1 | 1 | 0 | 7 | 0 | 1 | 1 | 0 | +| 8 | 0 | 1 | 1 | 1 | 8 | 0 | 1 | 1 | 1 | +| 9 | 1 | 0 | 0 | 0 | 9 | 1 | 0 | 0 | 0 | +| 10 | 1 | 0 | 0 | 1 | 10 | 1 | 0 | 0 | 1 | +| 11 | 1 | 0 | 1 | 0 | 11 | 1 | 0 | 1 | 0 | +| 12 | 1 | 0 | 1 | 1 | 12 | 1 | 0 | 1 | 1 | +| 13 | 1 | 1 | 0 | 0 | 13 | 1 | 1 | 0 | 0 | +| 14 | 1 | 1 | 0 | 1 | 14 | 1 | 1 | 0 | 1 | +| 15 | 1 | 1 | 1 | 0 | 15 | 1 | 1 | 1 | 0 | +| 16 | 1 | 1 | 1 | 1 | 16 | 1 | 1 | 1 | 1 | + +If a value of $k_{start} = 16$ and $k_{stop} = 1$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ shall be treated as an error by the UE. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1. + +#### 4.6.1.1.2 7.68Mcps TDD + +HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code. The start code $k_{start}$ is signalled by the bits $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}, x_{ccs,5}$ and the stop code $k_{stop}$ by the bits $x_{ccs,6}, x_{ccs,7}, x_{ccs,8}, x_{ccs,9}, x_{ccs,10}$ . The mapping in Table 16A below applies. + +**Table 16A: Channelisation code set information mapping for 7.68Mcps TDD** + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | $x_{ccs,5}$ | $k_{stop}$ | $x_{ccs,6}$ | $x_{ccs,7}$ | $x_{ccs,8}$ | $x_{ccs,9}$ | $x_{ccs,10}$ | +|-------------|-------------|-------------|-------------|-------------|-------------|------------|-------------|-------------|-------------|-------------|--------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | 0 | 1 | 2 | 0 | 0 | 0 | 0 | 1 | +| 3 | 0 | 0 | 0 | 1 | 0 | 3 | 0 | 0 | 0 | 1 | 0 | +| 4 | 0 | 0 | 0 | 1 | 1 | 4 | 0 | 0 | 0 | 1 | 1 | +| 5 | 0 | 0 | 1 | 0 | 0 | 5 | 0 | 0 | 1 | 0 | 0 | +| 6 | 0 | 0 | 1 | 0 | 1 | 6 | 0 | 0 | 1 | 0 | 1 | +| 7 | 0 | 0 | 1 | 1 | 0 | 7 | 0 | 0 | 1 | 1 | 0 | +| 8 | 0 | 0 | 1 | 1 | 1 | 8 | 0 | 0 | 1 | 1 | 1 | +| 9 | 0 | 1 | 0 | 0 | 0 | 9 | 0 | 1 | 0 | 0 | 0 | +| 10 | 0 | 1 | 0 | 0 | 1 | 10 | 0 | 1 | 0 | 0 | 1 | +| 11 | 0 | 1 | 0 | 1 | 0 | 11 | 0 | 1 | 0 | 1 | 0 | +| 12 | 0 | 1 | 0 | 1 | 1 | 12 | 0 | 1 | 0 | 1 | 1 | +| 13 | 0 | 1 | 1 | 0 | 0 | 13 | 0 | 1 | 1 | 0 | 0 | +| 14 | 0 | 1 | 1 | 0 | 1 | 14 | 0 | 1 | 1 | 0 | 1 | +| 15 | 0 | 1 | 1 | 1 | 0 | 15 | 0 | 1 | 1 | 1 | 0 | +| 16 | 0 | 1 | 1 | 1 | 1 | 16 | 0 | 1 | 1 | 1 | 1 | +| 17 | 1 | 0 | 0 | 0 | 0 | 17 | 1 | 0 | 0 | 0 | 0 | +| 18 | 1 | 0 | 0 | 0 | 1 | 18 | 1 | 0 | 0 | 0 | 1 | +| 19 | 1 | 0 | 0 | 1 | 0 | 19 | 1 | 0 | 0 | 1 | 0 | +| 20 | 1 | 0 | 0 | 1 | 1 | 20 | 1 | 0 | 0 | 1 | 1 | +| 21 | 1 | 0 | 1 | 0 | 0 | 21 | 1 | 0 | 1 | 0 | 0 | +| 22 | 1 | 0 | 1 | 0 | 1 | 22 | 1 | 0 | 1 | 0 | 1 | +| 23 | 1 | 0 | 1 | 1 | 0 | 23 | 1 | 0 | 1 | 1 | 0 | +| 24 | 1 | 0 | 1 | 1 | 1 | 24 | 1 | 0 | 1 | 1 | 1 | +| 25 | 1 | 1 | 0 | 0 | 0 | 25 | 1 | 1 | 0 | 0 | 0 | +| 26 | 1 | 1 | 0 | 0 | 1 | 26 | 1 | 1 | 0 | 0 | 1 | +| 27 | 1 | 1 | 0 | 1 | 0 | 27 | 1 | 1 | 0 | 1 | 0 | +| 28 | 1 | 1 | 0 | 1 | 1 | 28 | 1 | 1 | 0 | 1 | 1 | +| 29 | 1 | 1 | 1 | 0 | 0 | 29 | 1 | 1 | 1 | 0 | 0 | +| 30 | 1 | 1 | 1 | 0 | 1 | 30 | 1 | 1 | 1 | 0 | 1 | +| 31 | 1 | 1 | 1 | 1 | 0 | 31 | 1 | 1 | 1 | 1 | 0 | +| 32 | 1 | 1 | 1 | 1 | 1 | 32 | 1 | 1 | 1 | 1 | 1 | + +If a value of $k_{start} = 32$ and $k_{stop} = 1$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ shall be treated as an error by the UE. + +#### 4.6.1.2 Timeslot information mapping + +##### 4.6.1.2.1 1.28 Mcps TDD + +For 1.28 Mcps, the timeslots to be used for HS-PDSCH resources are signalled by the bits $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ , where bit $x_{ts,n}$ carries the information for timeslot n+1. Timeslot 1 cannot be used for HS-PDSCH resources. If the signalling bit is set (i.e. equal to 1), then the corresponding timeslot shall be used for HS-PDSCH resources. Otherwise, the timeslot shall not be used. If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, all used timeslots shall use the same channelisation code set, as signalled by the channelisation code set information bits. Otherwise, the used timeslots may use different channelization code sets as described in 4.6.1.1.1. + +When indicated by the higher layer that Timeslot 0 can be used for HS-PDSCH, bit $x_{ts,1}$ carries the information for timeslot 0. If $x_{ts,1}$ is set (i.e. equal to 1), Timeslot 0 shall be used for HS-PDSCH resource. Otherwise, Timeslot 0 shall not be used. + +##### 4.6.1.2.2 3.84 Mcps TDD and 7.68Mcps TDD + +For 3.84 Mcps, the timeslots to be used for HS-PDSCH resources are signalled by the bits $x_{ts,1}, x_{ts,2}, \dots, x_{ts,13}$ , where bit $x_{ts,n}$ carries the information for the nth available timeslot for HS-PDSCH resources, where the order of the timeslots available for HS-PDSCH resources shall be the same as the order of the 15 time slots within each frame with the following two slots removed: + +- The slot containing the P-CCPCH +- The first slot in a frame containing the PRACH + +If the P-CCPCH and/or PRACH are assigned to some, but not all frames, then the corresponding time slots shall remain unavailable for these frames as well.. + +If the bit is set (i.e. equal to 1), then the corresponding timeslot shall be used for HS-PDSCH resources. Otherwise, the timeslot shall not be used. All used timeslots shall use the same channelisation code set, as signalled by the channelisation code set information bits. + +#### 4.6.1.3 Modulation scheme information mapping + +The modulation scheme to be used by the HS-PDSCH resources shall be signalled by bit $x_{ms,1}$ . If 64QAM is not supported by the UE, the mapping scheme in Table 17 shall apply. + +**Table 17: Modulation scheme information mapping** + +| $x_{ms,1}$ | Modulation Scheme | +|------------|-------------------| +| 0 | QPSK | +| 1 | 16-QAM | + +If 64QAM is supported by the UE, the mapping scheme in Table 17a shall apply. + +**Table 17a: Modulation scheme information mapping** + +| $x_{ms,1}$ | Modulation Scheme | +|------------|-------------------| +| 0 | QPSK or 64QAM | +| 1 | 16-QAM | + +The method of determining the modulation scheme by UE with 64QAM capability is as following: + +If $x_{ms,1} = 1$ , then modulation scheme is 16QAM; + +Else if $x_{ms,1} = 0$ , then + +Step 1, UE first calculates the physical resource bearer capability and the transmission bit rate. The physical resource bearer capability is the maximum bit rate at which RAN can transmit with the physical resources assigned in HS-SCCH and the QPSK modulation. The physical resource bearer capability can be calculated by the channelization-code-set information and time slot information of HS-SCCH. + +The transmission bit rate is the bit rate to which the transport-block size indicated in HS-SCCH corresponds. + +Step 2, if the physical resource bearer capability multiplied by R is less than the transmission bit rate, and R belongs to [0, 1], + +then modulation scheme is 64QAM; + +else modulation scheme is QPSK. + +Note: According to the simulation results the value of the transmission bit rate divided by the physical resource bearer capability according to 64QAM should be more than 1/3, where the value of R is equal to 1. + +If 64QAM is configured by UE, the method of determining recommended modulation scheme by NodeB can be similar to 64QAM indication in HS-SCCH. The details are: + +If $x_{ms,1} = 1$ , NodeB should determine the recommended modulation scheme as 16QAM, + +Else if $x_{ms,1} = 0$ , NodeB calculates the physical resource bearer capability assigned in HS-SCCH corresponding to RMF and RTBS in HS-SICH, and calculates the transmission bit rate according to the RTBS in HS-SICH, and then determines whether the recommended modulation scheme is 64QAM or QPSK. + +#### 4.6.1.4 Redundancy and constellation version information mapping + +The redundancy version (RV) parameters $r$ , $s$ and constellation version parameter $b$ are mapped jointly to produce the value $X_{rv}$ . $X_{rv}$ is alternatively represented as the sequence $x_{rv,1}$ , $x_{rv,2}$ , $x_{rv,3}$ where $x_{rv,1}$ is the MSB. This is done according to the following tables according to the modulation mode used: + +**Table 18: RV mapping for 16 QAM and 64 QAM** + +| Xrv (value) | s | r | b | +|-------------------------------|----------|----------|----------| +| 0 | 1 | 0 | 0 | +| 1 | 0 | 0 | 0 | +| 2 | 1 | 1 | 1 | +| 3 | 0 | 1 | 1 | +| 4 | 1 | 0 | 1 | +| 5 | 1 | 0 | 2 | +| 6 | 1 | 0 | 3 | +| 7 | 1 | 1 | 0 | + +**Table 19: RV mapping for QPSK** + +| Xrv (value) | s | r | +|-------------------------------|----------|----------| +| 0 | 1 | 0 | +| 1 | 0 | 0 | +| 2 | 1 | 1 | +| 3 | 0 | 1 | +| 4 | 1 | 2 | +| 5 | 0 | 2 | +| 6 | 1 | 3 | +| 7 | 0 | 3 | + +#### 4.6.1.5 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6.1.6 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +#### 4.6.1.7 HARQ process identifier mapping + +The hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}$ is unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6.1.8 Transport block size index mapping + +The transport-block size information $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,m}$ is unsigned binary representation of the transport block size index where $x_{tbs,1}$ is MSB. + +### 4.6.2 Multiplexing of HS-SCCH information + +The information carried on the HS-SCCH is multiplexed onto the bits according to the following rule : + +### 4.6.3 CRC attachment for HS-SCCH + +From the sequence of bits a 16 bit CRC is calculated according to Section 4.2.1.1. This gives a sequence of bits where + +$$k = 1, 2, \dots, 16$$ + +This latter sequence of bits is then masked with the UE identity and appended to the sequence of bits. The bits at the output of the CRC attachment block is the sequence of bits, where + +$$i = 1, 2, \dots, A$$ + +$$i = A + 1 \dots B$$ + +### 4.6.4 Channel coding for HS-SCCH + +Channel coding for the HS-SCCH shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH. + +### 4.6.5 Rate matching for HS-SCCH + +Rate matching for HS-SCCH shall be done with the general method described in 4.2.7. + +### 4.6.6 Interleaving for HS-SCCH + +Interleaving for HS-SCCH shall be done with the general method described in 4.2.11.1. + +### 4.6.7 Physical Channel Segmentation for HS-SCCH + +Physical channel segmentation for HS-SCCH shall be done with the general method described in 4.2.10. For 1.28 Mcps TDD, the HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2; for 3.84 Mcps TDD and 7.68 Mcps TDD the HS-SCCH only uses one physical channel, see [7]. + +### 4.6.8 Physical channel mapping for HS-SCCH + +Physical channel mapping for the HS-SCCH shall be done with the general method described in subclause 4.2.12. + +## 4.6A Coding/Multiplexing for HS-SCCH orders type A + +HS-SCCH orders type A are commands sent to the UE using HS-SCCH. No HS-PDSCH is associated with HS-SCCH orders. + +For 1.28 Mcps TDD, HS-SCCH order type A may be used when any of the following conditions is true: + +- [HS\\_DSCH\\_RECEPTION\\_CELL\\_FACH\\_STATE](#) is TRUE; +- [CONTROL\\_CHANNEL\\_DRX\\_STATUS](#) is TRUE, and UE is not configured in MIMO mode; +- [CONTROL\\_CHANNEL\\_DRX\\_STATUS](#) is TRUE, and UE is configured in MIMO mode while the variable [MIMO SF mode for HS-PDSCH dual stream](#) is SF1 +- the variable [HS\\_DSCH\\_SPS\\_STATUS](#) is TRUE, and UE is not configured in MIMO mode; +- the variable [HS\\_DSCH\\_SPS\\_STATUS](#) is TRUE, and UE is configured in MIMO mode while the variable [MIMO SF mode for HS-PDSCH dual stream](#) is SF1. + +The following information is transmitted by means of the HS-SCCH order type A physical channel. + +- Order type (3 bits): $x_{odt,1}, x_{odt,2}, x_{odt,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The coding for HS-SCCH orders type A is specified in subclause 4.6. + +## 4.6A.1 HS-SCCH orders type A information field mapping + +### 4.6A.1.1 Order type mapping + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '000'$ , then the HS-SCCH order is an uplink synchronization establishment order when UE is in CELL\_FACH or CELL\_PCH state. + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '001'$ , then the HS-SCCH order is an order to release the allocated semi-persistent HS-PDSCH resources when UE is in CELL\_DCH state. + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '010'$ , then the HS-SCCH order is DRX Activation order when UE is in CELL\_DCH state. + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '011'$ , then the HS-SCCH order is DRX De-activation order when UE is in CELL\_DCH state. + +### 4.6A.1.2 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +## 4.6B Coding/Multiplexing for HS-SCCH type 2 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 2 when any of the following conditions is met: + +- the variable HS\_DSCH\_SPS\_STATUS is TRUE, and UE is not configured in MIMO mode; +- the variable HS\_DSCH\_SPS\_STATUS is TRUE, and UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1. + +HS-SCCH type 2 is used to allocate semi-persistent HS-PDSCH resources for the initial transmissions. The following information is transmitted by means of the HS-SCCH type 2 physical channels. + +- Type flag 1 (2 bits): $x_{flag1,1}, x_{flag1,2}$ +- Resource repetition pattern index (2bits): $x_{rrpi,1}, x_{rrpi,2}$ +- Type flag 2 (2 bits): $x_{flag2,1}, x_{flag2,2}$ +- Transport-block size information (2 bits): $x_{tbs,1}, x_{tbs,2}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Channelisation-code-set information (6 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,6}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- HS-SICH indicator (2bits): $x_{HI,1}, x_{HI,2}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ +- Redundancy and constellation version (0 bit): $X_{rv} = 0$ (see subclause 4.6.1.4) +- Reserved (5 bits): $x_{res,1}, x_{res,2}, \dots, x_{res,5}$ + +For an HS-SCCH order type A, + +- $X_{flag1,1}, X_{flag1,2}, X_{rrpi,1}, X_{rrpi,2}, X_{flag2,1}, X_{flag2,2}, X_{tbs,1}, X_{tbs,2}$ are reserved +- $X_{ts,1}, X_{ts,2}, \dots, X_{ts,5}$ shall be set to '00000' + +- $X_{ccs,1}, X_{ccs,2}, X_{ccs,3}$ shall be set to $X_{odt,1}, X_{odt,2}, X_{odt,3}$ +- $X_{ccs,4}, X_{ccs,5}, X_{ccs,6}, X_{ms,1}, X_{HI,1}, X_{HI,2}, X_{hcsn,1}, X_{hcsn,2}, X_{hcsn,3}, X_{res,1}, X_{res,2}, X_{res,3}, X_{res,4}, X_{res,5}$ are reserved + +where $X_{odt,1}, X_{odt,2}, X_{odt,3}$ are defined in subclause 4.6A. + +The following coding/multiplexing steps for HS-SCCH type 2 can be identified: + +- multiplexing of HS-SCCH type 2 information (see subclause 4.6B.2) +- CRC attachment for HS-SCCH type 2 (see subclause 4.6B.3); +- channel coding for HS-SCCH type 2 (see subclause 4.6B.4); +- rate matching for HS-SCCH type 2 (see subclause 4.6B.5); +- interleaving for HS-SCCH type 2 (see subclause 4.6B.6); +- mapping to physical channels for HS-SCCH type 2 (see subclauses 4.6B.7 and 4.6B.8). + +The general coding/multiplexing flow for HS-SCCH type 2 is shown in Figure 19A. + +![A large empty rectangular box, likely a placeholder for Figure 19A.](2e41f0ad7219c40ed9c9f440509165ae_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 19A. + +**Figure 19A: Coding and Multiplexing for HS-SCCH type 2** + +#### 4.6B.1 HS-SCCH type 2 information field mapping + +##### 4.6B.1.1 Type flag 1 mapping + +The type flag 1 $X_{flag1,1}, X_{flag1,2}$ are mapped such that $X_{flag1,1} = '1'$ corresponds to the MSB and $X_{flag1,2} = '1'$ to the LSB. The type flag 1 is used to distinguish HS-SCCH type 2 from other types. + +#### 4.6B.1.2 Resource repetition pattern index mapping + +The resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ is the unsigned binary representation of a reference to one of repetition patterns of the assigned semi-persistent HS-PDSCH resources configured by higher layers. The resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ are mapped such that $x_{rrpi,1}$ corresponds to the MSB and $x_{rrpi,2}$ to the LSB. The mapping of $x_{rrpi,1}, x_{rrpi,2} = '00'$ is not used. + +| $x_{rrpi,1}, x_{rrpi,2}$ | Resource repetition pattern index as signalled in the variable HS_DSCH_SPS_PARAMS[12] | +|--------------------------|---------------------------------------------------------------------------------------| +| '01' | 1 st entry | +| '10' | 2 nd entry | +| '11' | 3 rd entry | + +#### 4.6B.1.3 Type flag 2 mapping + +The type flag 2 $x_{flag2,1}, x_{flag2,2}$ are mapped such that $x_{flag2,1} = '1'$ corresponds to the MSB and $x_{flag2,2} = '0'$ to the LSB. The type flag 2 is used to distinguish HS-SCCH type 2 from other types. + +#### 4.6B.1.4 Transport block size index mapping + +The transport-block size information $x_{tbs,1}, x_{tbs,2}$ is the unsigned binary representation of a reference to one of the four Transport-block sizes configured by higher layers. + +| $x_{tbs,1}, x_{tbs,2}$ | Transport Block size as signalled in the variable HS_DSCH_SPS_PARAMS[12] | +|------------------------|--------------------------------------------------------------------------| +| '00' | 1 st entry | +| '01' | 2 nd entry | +| '10' | 3 rd entry | +| '11' | 4 th entry | + +#### 4.6B.1.5 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ is performed according to section 4.6.1.2.1. + +#### 4.6B.1.6 Channelisation code set information mapping + +HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code. The start code $k_{start}$ is signalled by the bits $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}$ and the stop code $k_{stop}$ by the bits $x_{ccs,4}, x_{ccs,5}, x_{ccs,6}$ . The mapping in Table 16B below applies. + +If a value of $k_{start} = 9$ and $k_{stop} = 6$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ are not used. + +**Table 16B: Channelisation code set information mapping** + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $x_{ccs,3}$ | $k_{stop}$ | $x_{ccs,4}$ | $x_{ccs,5}$ | $x_{ccs,6}$ | +|-------------|-------------|-------------|-------------|------------|-------------|-------------|-------------| +| 1 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | +| 3 | 0 | 0 | 1 | 4 | 0 | 0 | 1 | +| 5 | 0 | 1 | 0 | 6 | 0 | 1 | 0 | +| 7 | 0 | 1 | 1 | 8 | 0 | 1 | 1 | +| 9 | 1 | 0 | 0 | 10 | 1 | 0 | 0 | +| 11 | 1 | 0 | 1 | 12 | 1 | 0 | 1 | +| 13 | 1 | 1 | 0 | 14 | 1 | 1 | 0 | +| 15 | 1 | 1 | 1 | 16 | 1 | 1 | 1 | + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1. + +#### 4.6B.1.7 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,1}$ is performed according to table 17 in section 4.6.1.3. + +#### 4.6B.1.8 HS-SICH indicator mapping + +The HS-SICH indicator consists of 2 bits used to indicate the UE which HS-SICH will be used to convey the CQI and the acknowledgement indicator for the received data on the semi-persistent HS-PDSCH resources. The bits $x_{HI,1}$ , $x_{HI,2}$ are mapped such that $x_{HI,1}$ corresponds to the MSB and $x_{HI,2}$ to the LSB. + +| $x_{HI,1}$ , $x_{HI,2}$ | HS-SICH indicator as signalled in the variable HS_DSCH_SPS_PARAMS[12] | +|-------------------------|-----------------------------------------------------------------------| +| '00' | 1 st entry | +| '01' | 2 nd entry | +| '10' | 3 rd entry | +| '11' | 4 th entry | + +#### 4.6B.1.9 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}$ , $x_{hcsn,2}$ , $x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6B.1.10 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +## 4.6B.2 Multiplexing of HS-SCCH type 2 information + +The information carried on the HS-SCCH type 2 is multiplexed onto the bits according to the following rule : + +## 4.6B.3 CRC attachment for HS-SCCH type 2 + +The sequence of bits , is calculated according to subclause 4.6.3. + +## 4.6B.4 Channel coding for HS-SCCH type 2 + +Channel coding for the HS-SCCH type 2 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 2. + +## 4.6B.5 Rate matching for HS-SCCH type 2 + +Rate matching for HS-SCCH type 2 shall be done with the general method described in 4.6.5. + +## 4.6B.6 Interleaving for HS-SCCH type 2 + +Interleaving for HS-SCCH type 2 shall be done with the general method described in 4.2.11.1. + +## 4.6B.7 Physical Channel Segmentation for HS-SCCH type 2 + +Physical channel segmentation for HS-SCCH type 2 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +## 4.6B.8 Physical channel mapping for HS-SCCH type 2 + +Physical channel mapping for the HS-SCCH type 2 shall be done with the general method described in subclause 4.2.12. + +## 4.6C Coding/Multiplexing for HS-SCCH type 3 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 3 when any of the following conditions is met: + +- the variable HS\_DSCH\_SPS\_STATUS is TRUE, and UE is not configured in MIMO mode; +- the variable HS\_DSCH\_SPS\_STATUS is TRUE, and UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1. + +HS-SCCH type 3 is used to allocate one subframe HS-PDSCH resources for retransmissions of HS-DSCH semi-persistent scheduling operation. The following information is transmitted by means of the HS-SCCH type 3 physical channels. + +- Type flag 1 (2 bits): $x_{flag1,1}, x_{flag1,2}$ +- Resource repetition pattern index (2bits): $x_{rrpi,1}, x_{rrpi,2}$ +- Type flag 2 (2 bits): $x_{flag2,1}, x_{flag2,2}$ +- Transport-block size information (2 bits): $x_{tbs,1}, x_{tbs,2}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Channelisation-code-set information (6 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,6}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Redundancy version information (2 bits): $x_{rv,1}, x_{rv,2}$ +- Pointer to the previous transmission (4 bits): $x_{ptr,1}, x_{ptr,2}, x_{ptr,3}, x_{ptr,4}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hesn,1}, x_{hesn,2}, x_{hesn,3}$ +- Reserved (1 bit): $x_{res,1}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 3 can be identified: + +- multiplexing of HS-SCCH type 3 information (see subclause 4.6C.2) +- CRC attachment for HS-SCCH type 3 (see subclause 4.6C.3); +- channel coding for HS-SCCH type 3 (see subclause 4.6C.4); +- rate matching for HS-SCCH type 3 (see subclause 4.6C.5); +- interleaving for HS-SCCH type 3 (see subclause 4.6C.6); +- mapping to physical channels for HS-SCCH type 3 (see subclauses 4.6C.7 and 4.6C.8). + +The general coding/multiplexing flow for HS-SCCH type 3 is shown in Figure 19B. + +![A large empty rectangular box, likely a placeholder for a diagram or figure.](69959d0c3f45f3c08c4d85efdd0bf815_img.jpg) + +A large empty rectangular box, likely a placeholder for a diagram or figure. + +**Figure 19B: Coding and Multiplexing for HS-SCCH type 3** + +## 4.6C.1 HS-SCCH type 3 information field mapping + +### 4.6C.1.1 Type flag 1 mapping + +The type flag 1 $x_{flag1,1}, x_{flag1,2}$ are mapped such that $x_{flag1,1} = '1'$ corresponds to the MSB and $x_{flag1,2} = '1'$ to the LSB. The type flag 1 is used to distinguish HS-SCCH type 3 from other types. + +### 4.6C.1.2 Resource repetition pattern index mapping + +The resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ are mapped such that $x_{rrpi,1}$ corresponds to the MSB and $x_{rrpi,2}$ to the LSB. The mapping $x_{rrpi,1}, x_{rrpi,2} = '00'$ is used to indicate one subframe HS-PDSCH resources assigned for retransmissions of semi-persistent scheduling operation. + +### 4.6C.1.3 Type flag 2 mapping + +The type flag 2 $x_{flag2,1}, x_{flag2,2}$ are mapped such that $x_{flag2,1} = '1'$ corresponds to the MSB and $x_{flag2,2} = '0'$ to the LSB. The type flag 2 is used to distinguish HS-SCCH type 3 from other types. + +### 4.6C.1.4 Transport block size index mapping + +The transport-block size information $x_{tbs,1}, x_{tbs,2}$ is the unsigned binary representation of a reference to one of the four Transport-block sizes configured by higher layers. The mapping is performed according to section 4.6B.1.4. + +### 4.6C.1.5 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ is performed according to section 4.6.1.2.1. + +#### 4.6C.1.6 Channelisation code set information mapping + +The mapping of the channelisation code set information $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}, x_{ccs,5}, x_{ccs,6}$ is performed according to section 4.6B.1.6. + +#### 4.6C.1.7 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,i}$ is performed according to table 17 in section 4.6.1.3. + +#### 4.6C.1.8 Redundancy version information mapping + +The redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are mapped jointly to produce the value $X_{rv}$ . $X_{rv}$ is alternatively represented as the sequence $x_{rv,1}, x_{rv,2}$ where $x_{rv,1}$ is the MSB. This is done according to the following tables according to the modulation mode used. + +**Table 18A: RV mapping for 16QAM and 64QAM** + +| $X_{rv}$ (value) | $N_{sys} / N_{data} < 1/2$ | | | $N_{sys} / N_{data} \geq 1/2$ | | | +|------------------|----------------------------|-----|-----|-------------------------------|-----|-----| +| | $s$ | $r$ | $b$ | $s$ | $r$ | $b$ | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | +| 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 2 | 1 | 0 | 2 | 0 | 0 | 0 | +| 3 | 1 | 0 | 3 | 1 | 0 | 2 | + +**Table 19A: RV mapping for QPSK** + +| $X_{rv}$ (value) | $N_{sys} / N_{data} < 1/2$ | | $N_{sys} / N_{data} \geq 1/2$ | | +|------------------|----------------------------|-----|-------------------------------|-----| +| | $s$ | $r$ | $s$ | $r$ | +| 0 | 1 | 0 | 1 | 0 | +| 1 | 1 | 1 | 0 | 1 | +| 2 | 1 | 2 | 0 | 3 | +| 3 | 1 | 3 | 1 | 2 | + +#### 4.6C.1.9 Pointer to the previous transmission mapping + +Pointer to the previous transmission $x_{ptr,1}, x_{ptr,2}, x_{ptr,3}, x_{ptr,4}$ is the unsigned binary representation of $s$ , such that the previous transmission of the same transport block started $(4+s)$ subframes before the start of this transmission. And $x_{ptr,1}$ corresponds to the MSB and $x_{ptr,4}$ to the LSB. + +#### 4.6C.1.10 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6C.1.11 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6C.2 Multiplexing of HS-SCCH type 3 information + +The information carried on the HS-SCCH type 3 is multiplexed onto the bits according to the following rule : + +#### 4.6C.3 CRC attachment for HS-SCCH type 3 + +The sequence of bits , is calculated according to subclause 4.6.3. + +#### 4.6C.4 Channel coding for HS-SCCH type 3 + +Channel coding for the HS-SCCH type 3 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 3. + +#### 4.6C.5 Rate matching for HS-SCCH type 3 + +Rate matching for HS-SCCH type 3 shall be done with the general method described in 4.6.5. + +#### 4.6C.6 Interleaving for HS-SCCH type 3 + +Interleaving for HS-SCCH type 3 shall be done with the general method described in 4.2.11.1. + +#### 4.6C.7 Physical Channel Segmentation for HS-SCCH type 3 + +Physical channel segmentation for HS-SCCH type 3 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +#### 4.6C.8 Physical channel mapping for HS-SCCH type 3 + +Physical channel mapping for the HS-SCCH type 3 shall be done with the general method described in subclause 4.2.12. + +### 4.6D Coding/Multiplexing for HS-SCCH type 4 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 4 when any of the following conditions is met: + +- The UE is configured in MIMO mode, and the variable MIMO SF mode for HS-PDSCH dual stream is SF1. +- The UE is configured in MU-MIMO mode, and UE is not configured in MIMO mode. +- The UE is configured in MU-MIMO mode, and the UE is configured in MIMO mode with the variable MIMO SF mode for HS-PDSCH dual stream being SF1. + +Note : For the UEs configured in MU-MIMO mode staying in CELL-FACH state, HS-SCCH shall be of type 1 for BCCH transmission [10]. + +HS-SCCH type 4 is used for single stream transmission in MIMO mode or in MU-MIMO mode. The following information is transmitted by means of the HS-SCCH type 4 physical channels. + +- Type flag 1 (1 bit): $x_{flag1,1}$ +- Channelisation-code-set information (6 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,6}$ +- Type flag 2 (1 bit): $x_{flag2,1}$ + +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Transport-block size information (6 bits): $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ +- Redundancy version information (2 bits): $x_{rv,1}, x_{rv,2}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- Midamble allocation scheme flag (1 bit): $x_{flag,1}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 4 can be identified: + +- multiplexing of HS-SCCH type 4 information (see subclause 4.6D.2) +- CRC attachment for HS-SCCH type 4 (see subclause 4.6D.3); +- channel coding for HS-SCCH type 4 (see subclause 4.6D.4); +- rate matching for HS-SCCH type 4 (see subclause 4.6D.5); +- interleaving for HS-SCCH type 4 (see subclause 4.6D.6); +- mapping to physical channels for HS-SCCH type 4 (see subclauses 4.6D.7 and 4.6D.8). + +The general coding/multiplexing flow for HS-SCCH type 4 is shown in Figure 19C. + +![A rectangular box representing the flow diagram for Figure 19C.](1dda1ccbaddcb163f7b69e9726bbaff1_img.jpg) + +A large, empty rectangular box with a thin black border, positioned horizontally in the center of the page. It is intended to represent the flow diagram for Figure 19C, which is missing from this version of the document. + +A rectangular box representing the flow diagram for Figure 19C. + +**Figure 19C: Coding and Multiplexing for HS-SCCH type 4** + +## 4.6D.1 HS-SCCH type 4 information field mapping + +### 4.6D.1.1 Type flag 1 mapping + +The type flag 1 bit $x_{flag,1}$ is mapped as $x_{flag,1} = '0'$ . The type flag 1 is used to distinguish HS-SCCH type 4 from other types. + +### 4.6D.1.2 Type flag 2 mapping + +The type flag 2 $x_{flag,2}$ is mapped as $x_{flag,2} = '1'$ . The type flag 2 is used to distinguish HS-SCCH type 4 from other types. + +### 4.6D.1.3 Channelisation code set information mapping + +When the midamble allocation scheme flag bit $x_{flag,1} = '0'$ , the mapping of the channelisation code set information $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}, x_{ccs,5}, x_{ccs,6}$ is performed according to section 4.6B.1.6. + +When the midamble allocation scheme flag bit $x_{flag,1} = '1'$ , the bits $x_{ccs,1}, x_{ccs,2}$ are comprised of the special default midamble pattern indicator ( $x_{mpi,1}, x_{mpi,2}$ ) and $x_{ccs,1} = x_{mpi,1}$ and $x_{ccs,2} = x_{mpi,2}$ . The mapping is shown in Table 24A below. + +The start code $k_{start}$ is signalled by the bits $x_{ccs,3}, x_{ccs,4}$ and the stop code $k_{stop}$ by the bits $x_{ccs,5}, x_{ccs,6}$ . The mapping in Table 24B below applies. If a value of $k_{start} = 13$ and $k_{stop} = 4$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ are not used. + +**Table 24A: Special default midamble pattern mapping** + +| Special default Midamble pattern | $x_{mpi,1}$ | $x_{mpi,2}$ | +|----------------------------------|-------------|-------------| +| pattern 1A | 0 | 0 | +| pattern 1B | 0 | 1 | +| pattern 2A | 1 | 0 | +| pattern 2B | 1 | 1 | + +**Table 24B: Channelisation code set information mapping** + +| $k_{start}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | $k_{stop}$ | $x_{ccs,5}$ | $x_{ccs,6}$ | +|-------------|-------------|-------------|------------|-------------|-------------| +| 1 | 0 | 0 | 4 | 0 | 0 | +| 5 | 0 | 1 | 8 | 0 | 1 | +| 9 | 1 | 0 | 12 | 1 | 0 | +| 13 | 1 | 1 | 16 | 1 | 1 | + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1. + +### 4.6D.1.4 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ is performed according to section 4.6.1.2.1. + +### 4.6D.1.5 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,1}$ is performed according to section 4.6.1.3. + +#### 4.6D.1.6 Transport block size index mapping + +The transport-block size information $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ is the unsigned binary representation of the transport block size index where $x_{tbs,1}$ is MSB. The mapping is performed according to section 4.6.1.8. + +#### 4.6D.1.7 HARQ process identifier mapping + +The hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ is unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6D.1.8 Redundancy version information mapping + +The redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are mapped jointly to produce the value $X_{rv}$ . $X_{rv}$ is alternatively represented as the sequence $x_{rv,1}, x_{rv,2}$ where $x_{rv,1}$ is the MSB. The mapping is performed according to section 4.6C.1.8. If $X_{rv} = 0$ , the UE shall treat the corresponding transport block as an initial transmission. + +#### 4.6D.1.9 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6D.1.10 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +#### 4.6D.1.11 Midamble allocation scheme flag + +When the midamble allocation scheme flag bit $x_{flag,1} = '0'$ , the default midamble allocation scheme is used. Otherwise when the midamble allocation scheme flag bit $x_{flag,1} = '1'$ , the special default midamble allocation scheme with four patterns is used. + +### 4.6D.2 Multiplexing of HS-SCCH type 4 information + +The information carried on the HS-SCCH type 4 is multiplexed onto the bits according to the following rule : + +### 4.6D.3 CRC attachment for HS-SCCH type 4 + +The sequence of bits , is calculated according to subclause 4.6.3. + +#### 4.6D.4 Channel coding for HS-SCCH type 4 + +Channel coding for the HS-SCCH type 4 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 4. + +#### 4.6D.5 Rate matching for HS-SCCH type 4 + +Rate matching for HS-SCCH type 4 shall be done with the general method described in 4.6.5. + +#### 4.6D.6 Interleaving for HS-SCCH type 4 + +Interleaving for HS-SCCH type 4 shall be done with the general method described in 4.2.11.1. + +#### 4.6D.7 Physical Channel Segmentation for HS-SCCH type 4 + +Physical channel segmentation for HS-SCCH type 4 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +#### 4.6D.8 Physical channel mapping for HS-SCCH type 4 + +Physical channel mapping for the HS-SCCH type 4 shall be done with the general method described in subclause 4.2.12. + +### 4.6E Coding/Multiplexing for HS-SCCH type 5 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 5 when the following two conditions are both true: + +- the UE is configured in MIMO mode, and +- the variable MIMO SF mode for HS-PDSCH dual stream is SF1. + +HS-SCCH type 5 is used for dual stream transmission in MIMO mode. The following information is transmitted by means of the HS-SCCH type 5 physical channels. + +- Type flag 1 (1 bit): $x_{flag1,1}$ +- Modulation scheme information for stream 2 (1 bit): $x_{ms2,1}$ +- Transport-block size offset information for stream 2 (5 bits): $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,5}$ +- Type flag 2 (1 bit): $x_{flag2,1}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Transport-block size information for stream 1 (6 bits): $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,6}$ +- Modulation scheme information for stream 1 (1 bit): $x_{ms1,1}$ +- Hybrid-ARQ process information (3 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}$ +- Redundancy version information for stream 1 (2 bits): $x_{rv1,1}, x_{rv1,2}$ +- Redundancy version information for stream 2 (2 bits): $x_{rv2,1}, x_{rv2,2}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 5 can be identified: + +- multiplexing of HS-SCCH type 5 information (see subclause 4.6E.2) +- CRC attachment for HS-SCCH type 5 (see subclause 4.6E.3); +- channel coding for HS-SCCH type 5 (see subclause 4.6E.4); +- rate matching for HS-SCCH type 5 (see subclause 4.6E.5); +- interleaving for HS-SCCH type 5 (see subclause 4.6E.6); +- mapping to physical channels for HS-SCCH type 5 (see subclauses 4.6E.7 and 4.6E.8). + +The general coding/multiplexing flow for HS-SCCH type 5 is shown in Figure 19D. + +![A large empty rectangular box, likely a placeholder for Figure 19D.](d62cac468ea25bcb00a23015ede34537_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 19D. + +**Figure 19D: Coding and Multiplexing for HS-SCCH type 5** + +#### 4.6E.1 HS-SCCH type 5 information field mapping + +##### 4.6E.1.1 Type flag 1 mapping + +The type flag 1 bit $x_{flag1,1}$ is mapped as $x_{flag1,1} = '1'$ . The type flag 1 is used to distinguish HS-SCCH type 5 from other types. + +##### 4.6E.1.2 Type flag 2 mapping + +The type flag 2 bits $x_{flag2,1}$ is mapped as $x_{flag2,1} = '0'$ . The type flag 2 is used to distinguish HS-SCCH type 5 from other types. + +##### 4.6E.1.3 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ is performed according to section 4.6.1.2.1. + +#### 4.6E.1.4 Modulation scheme information mapping + +The mapping of the modulation scheme information for each stream ( $x_{ms1,1}$ for stream 1 or $x_{ms2,1}$ for stream 2) is performed according to section 4.6.1.3. + +#### 4.6E.1.5 Transport block size offset information mapping + +The transport-block size offset information for stream 2 $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,5}$ is the unsigned binary representation of the transport block size index offset for the stream 2 where $x_{tbs2,1}$ is MSB. The transport-block size offset for the stream 2 subtracted from the transport-block size for the stream 1 gives the transport-block size for stream 2. + +#### 4.6E.1.6 Transport block size index mapping + +The transport-block size information for stream 1 $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,6}$ is the unsigned binary representation of the transport block size index where $x_{tbs1,1}$ is MSB. The mapping is performed according to section 4.6.1.8. + +#### 4.6E.1.7 HARQ process identifier mapping + +The hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}$ is unsigned binary representation of the HARQ process identifier for stream 1 where $x_{hap,1}$ is MSB. The HARQ process identifier for stream 2 is , where $N_{proc}$ is the number of HARQ processes configured by higher layers. + +#### 4.6E.1.8 Redundancy version information mapping + +The redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are mapped jointly to produce the value $X_{rv}$ . $X_{rv1}$ is alternatively represented as the sequence for stream 1 $x_{rv1,1}, x_{rv1,2}$ where $x_{rv1,1}$ is the MSB. $X_{rv2}$ is alternatively represented as the sequence for stream 2 $x_{rv2,1}, x_{rv2,2}$ where $x_{rv2,1}$ is the MSB. The mapping of the redundancy version for each stream is performed according to section 4.6C.1.8. If $X_{rv1} = 0$ or $X_{rv2} = 0$ , the UE shall treat the corresponding transport block as an initial transmission. + +#### 4.6E.1.9 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6E.1.10 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6E.2 Multiplexing of HS-SCCH type 5 information + +The information carried on the HS-SCCH type 5 is multiplexed onto the bits according to the following rule : + +#### 4.6E.3 CRC attachment for HS-SCCH type 5 + +The sequence of bits $c$ , is calculated according to subclause 4.6.3. + +#### 4.6E.4 Channel coding for HS-SCCH type 5 + +Channel coding for the HS-SCCH type 5 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 5. + +#### 4.6E.5 Rate matching for HS-SCCH type 5 + +Rate matching for HS-SCCH type 5 shall be done with the general method described in 4.6.5. + +#### 4.6E.6 Interleaving for HS-SCCH type 5 + +Interleaving for HS-SCCH type 5 shall be done with the general method described in 4.2.11.1. + +#### 4.6E.7 Physical Channel Segmentation for HS-SCCH type 5 + +Physical channel segmentation for HS-SCCH type 5 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +#### 4.6E.8 Physical channel mapping for HS-SCCH type 5 + +Physical channel mapping for the HS-SCCH type 5 shall be done with the general method described in subclause 4.2.12. + +### 4.6F Coding/Multiplexing for HS-SCCH type 6 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 6 when the following two conditions are both met: + +- the variable **HS\_DSCH\_SPS\_STATUS** is TRUE, and +- UE is configured in MIMO mode while the variable **MIMO SF mode for HS-PDSCH dual stream** is SF1/SF16. + +HS-SCCH type 6 is used to allocate semi-persistent HS-PDSCH resources for the initial transmissions. The following information is transmitted by means of the HS-SCCH type 6 physical channels. + +- Type flag (3 bits): $x_{flag,1}, x_{flag,2}, x_{flag,3}$ +- Channelisation-code-set information (8 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,8}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Resource repetition pattern index (2bits): $x_{rrpi,1}, x_{rrpi,2}$ +- Transport-block size information (2 bits): $x_{tbs,1}, x_{tbs,2}$ +- HS-SICH indicator (2bits): $x_{HI,1}, x_{HI,2}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- Reserved (8 bits): $x_{res,1}, x_{res,2}, \dots, x_{res,8}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +- Redundancy and constellation version (0 bit ): $X_{rv} = 0$ (see 4.6.1.4) + +For an HS-SCCH order type B, + +- $X_{flag,1}, X_{flag,2}, X_{flag,3}, X_{ccs,1}, X_{ccs,2}, X_{ccs,3}, X_{ccs,4}, X_{ccs,5}, X_{ccs,6}, X_{ccs,7}, X_{ccs,8}$ are reserved +- $X_{ts,1}, X_{ts,2}, \dots, X_{ts,5}$ shall be set to '00000' +- $X_{ms,1}, X_{rrpi,1}, X_{rrpi,2}$ shall be set to $X_{odt,1}, X_{odt,2}, X_{odt,3}$ +- $X_{tbs,1}, X_{tbs,2}, X_{hi,1}, X_{hi,2}, X_{hcsn,1}, X_{hcsn,2}, X_{hcsn,3}, X_{res,1}, X_{res,2}, X_{res,3}, X_{res,4}, X_{res,5}, X_{res,6}, X_{res,7}, X_{res,8}$ are reserved + +where $X_{odt,1}, X_{odt,2}, X_{odt,3}$ are defined in subclause 4.6J. + +The following coding/multiplexing steps for HS-SCCH type 6 can be identified: + +- multiplexing of HS-SCCH type 6 information (see subclause 4.6F.2) +- CRC attachment for HS-SCCH type 6 (see subclause 4.6F.3); +- channel coding for HS-SCCH type 6 (see subclause 4.6F.4); +- rate matching for HS-SCCH type 6 (see subclause 4.6F.5); +- interleaving for HS-SCCH type 6 (see subclause 4.6F.6); +- mapping to physical channels for HS-SCCH type 6 (see subclauses 4.6F.7 and 4.6F.8). + +The general coding/multiplexing flow for HS-SCCH type 6 is shown in Figure 19E. + +![A large empty rectangular box, likely a placeholder for Figure 19E.](f85901c04910147b1057081deab67741_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 19E. + +**Figure 19E: Coding and Multiplexing for HS-SCCH type 6** + +## 4.6F.1 HS-SCCH type 6 information field mapping + +### 4.6F.1.1 Type flag mapping + +The type flag $x_{flag,1}, x_{flag,2}, x_{flag,3}$ are mapped such that $x_{flag,1} = '1'$ corresponds to the MSB and $x_{flag,3} = '0'$ to the LSB. The bit $x_{flag,2}$ is reserved. The type flag is used to distinguish HS-SCCH type 6 from other types. + +### 4.6F.1.2 Channelisation code set information mapping + +The mapping of the channelisation code set information $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,7}, x_{ccs,8}$ is performed according to section 4.6.1.1.1. + +### 4.6F.1.3 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ is performed according to section 4.6.1.2.1. + +### 4.6F.1.4 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,1}$ is performed according to table 17 in section 4.6.1.3. + +### 4.6F.1.5 Resource repetition pattern index mapping + +The mapping of the resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ is performed according to section 4.6B.1.2. + +### 4.6F.1.6 Transport block size index mapping + +The mapping of the transport-block size information $x_{tbs,1}, x_{tbs,2}$ is performed according to section 4.6B.1.4. + +### 4.6F.1.7 HS-SICH indicator mapping + +The mapping of the HS-SICH indicator $x_{HI,1}, x_{HI,2}$ is performed according to section 4.6B.1.9. + +### 4.6F.1.8 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +### 4.6F.1.9 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +## 4.6F.2 Multiplexing of HS-SCCH type 6 information + +The information carried on the HS-SCCH type 6 is multiplexed onto the bits according to the following rule : + +### 4.6F.3 CRC attachment for HS-SCCH type 6 + +The sequence of bits $c$ , is calculated according to subclause 4.6.3. + +### 4.6F.4 Channel coding for HS-SCCH type 6 + +Channel coding for the HS-SCCH type 6 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 6. + +### 4.6F.5 Rate matching for HS-SCCH type 6 + +Rate matching for HS-SCCH type 6 shall be done with the general method described in 4.6.5. + +### 4.6F.6 Interleaving for HS-SCCH type 6 + +Interleaving for HS-SCCH type 6 shall be done with the general method described in 4.2.11.1. + +### 4.6F.7 Physical Channel Segmentation for HS-SCCH type 6 + +Physical channel segmentation for HS-SCCH type 6 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +### 4.6F.8 Physical channel mapping for HS-SCCH type 6 + +Physical channel mapping for the HS-SCCH type 6 shall be done with the general method described in subclause 4.2.12. + +## 4.6G Coding/Multiplexing for HS-SCCH type 7 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 7 when the following two conditions are both met: + +- the variable HS\_DSCH\_SPS\_STATUS is TRUE, and +- UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16. + +HS-SCCH type 7 is used to allocate one subframe HS-PDSCH resources for retransmissions of HS-DSCH semi-persistent scheduling operation. The following information is transmitted by means of the HS-SCCH type 7 physical channels. + +- Type flag (3 bits): $x_{flag,1}, x_{flag,2}, x_{flag,3}$ +- Channelisation-code-set information (8 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,8}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Resource repetition pattern index (2bits): $x_{rrpi,1}, x_{rrpi,2}$ +- Transport-block size information (2 bits): $x_{tbs,1}, x_{tbs,2}$ +- Redundancy version information (2 bits): $x_{rv,1}, x_{rv,2}$ +- Pointer to the previous transmission (4 bits): $x_{ptr,1}, x_{ptr,2}, x_{ptr,3}, x_{ptr,4}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- Reserved (4 bits): $x_{res,1}, x_{res,2}, x_{res,3}, x_{res,4}$ + +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 7 can be identified: + +- multiplexing of HS-SCCH type 7 information (see subclause 4.6G.2) +- CRC attachment for HS-SCCH type 7 (see subclause 4.6G.3); +- channel coding for HS-SCCH type 7 (see subclause 4.6G.4); +- rate matching for HS-SCCH type 7 (see subclause 4.6G.5); +- interleaving for HS-SCCH type 7 (see subclause 4.6G.6); +- mapping to physical channels for HS-SCCH type 7 (see subclauses 4.6G.7 and 4.6G.8). + +The general coding/multiplexing flow for HS-SCCH type 7 is shown in Figure 19F. + +![A large empty rectangular box, likely a placeholder for Figure 19F.](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 19F. + +**Figure 19F: Coding and Multiplexing for HS-SCCH type 7** + +#### 4.6G.1 HS-SCCH type 7 information field mapping + +##### 4.6G.1.1 Type flag mapping + +The type flag $x_{flag,1}, x_{flag,2}, x_{flag,3}$ are mapped such that $x_{flag,1} = '1'$ corresponds to the MSB and $x_{flag,3} = '0'$ to the LSB. The bit $x_{flag,2}$ is reserved. The type flag is used to distinguish HS-SCCH type 7 from other types. + +##### 4.6G.1.2 Channelisation code set information mapping + +The mapping of the channelisation code set information $x_{ccs,1}, x_{ccs,2}, x_{ccs,3}, x_{ccs,4}, x_{ccs,5}, x_{ccs,6}, x_{ccs,7}, x_{ccs,8}$ is performed according to section 4.6.1.1.1. + +#### 4.6G.1.3 Timeslot information mapping + +The mapping of the time slot information $x_{is,1}, x_{is,2}, \dots, x_{is,5}$ is performed according to section 4.6.1.2.1. + +#### 4.6G.1.4 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,1}$ is performed according to table 17 in section 4.6.1.3. + +#### 4.6G.1.5 Resource repetition pattern index mapping + +The mapping of the resource repetition pattern index bits $x_{rppi,1}, x_{rppi,2}$ is performed according to section 4.6C.1.2. + +#### 4.6G.1.6 Transport block size index mapping + +The mapping of the transport-block size information $x_{tbs,1}, x_{tbs,2}$ is performed according to section 4.6B.1.4. + +#### 4.6G.1.7 Redundancy version information mapping + +The mapping of the redundancy version $x_{rv,1}, x_{rv,2}$ is performed according to section 4.6C.1.8. + +#### 4.6G.1.8 Pointer to the previous transmission mapping + +The mapping of the pointer to the previous transmission $x_{ptr,1}, x_{ptr,2}, x_{ptr,3}$ is performed according to section 4.6C.1.9. + +#### 4.6G.1.9 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6G.1.10 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6G.2 Multiplexing of HS-SCCH type 7 information + +The information carried on the HS-SCCH type 7 is multiplexed onto the bits according to the following rule : + +### 4.6G.3 CRC attachment for HS-SCCH type 7 + +The sequence of bits , is calculated according to subclause 4.6.3. + +## 4.6G.4 Channel coding for HS-SCCH type 7 + +Channel coding for the HS-SCCH type 7 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 7. + +## 4.6G.5 Rate matching for HS-SCCH type 7 + +Rate matching for HS-SCCH type 7 shall be done with the general method described in 4.6.5. + +## 4.6G.6 Interleaving for HS-SCCH type 7 + +Interleaving for HS-SCCH type 7 shall be done with the general method described in 4.2.11.1. + +## 4.6G.7 Physical Channel Segmentation for HS-SCCH type 7 + +Physical channel segmentation for HS-SCCH type 7 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +## 4.6G.8 Physical channel mapping for HS-SCCH type 7 + +Physical channel mapping for the HS-SCCH type 7 shall be done with the general method described in subclause 4.2.12. + +## 4.6H Coding/Multiplexing for HS-SCCH type 8 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 8 when any of the following conditions is met: + +- The UE is configured in MIMO mode, and the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16. +- The UE is configured in MU-MIMO mode, and the UE is configured in MIMO mode with the variable MIMO SF mode for HS-PDSCH dual stream being SF1/SF16. + +HS-SCCH type 8 is used for single stream transmission in MIMO mode or in MU-MIMO mode. The following information is transmitted by means of the HS-SCCH type 8 physical channels. + +- Channelisation-code-set information (4 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,4}$ +- Transport-block size information (6 bits): $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,6}$ +- Modulation scheme information (1 bit): $x_{ms,1}$ +- Time slot information (5 bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Redundancy version information (2 bits): $x_{rv,1}, x_{rv,2}$ +- Type flag 1 (6 bits): $x_{flag1,1}, x_{flag1,2}, x_{flag1,3}, x_{flag1,4}, x_{flag1,5}, x_{flag1,6}$ +- Field flag 2 (1 bit): $x_{flag2,1}$ +- Special Information (2 bits): $x_{info,1}, x_{info,2}$ +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ +- HS-SCCH cyclic sequence number (3 bits): $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 8 can be identified: + +- multiplexing of HS-SCCH type 8 information (see subclause 4.6H.2) +- CRC attachment for HS-SCCH type 8 (see subclause 4.6H.3); +- channel coding for HS-SCCH type 8 (see subclause 4.6H.4); +- rate matching for HS-SCCH type 8 (see subclause 4.6H.5); +- interleaving for HS-SCCH type 8 (see subclause 4.6H.6); +- mapping to physical channels for HS-SCCH type 8 (see subclauses 4.6H.7 and 4.6H.8). + +The general coding/multiplexing flow for HS-SCCH type 8 is shown in Figure 19G. + +![A large empty rectangular box, likely a placeholder for Figure 19G.](4c5f1aeea1c3fa1db11cc4ae0663c832_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 19G. + +**Figure 19G: Coding and Multiplexing for HS-SCCH type 8** + +## 4.6H.1 HS-SCCH type 8 information field mapping + +### 4.6H.1.1 Channelisation code set information mapping + +HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code. + +If the field flag $x_{flag,2,l} = '0'$ , the special information $x_{info,1}, x_{info,2}$ are comprised of the channelisation code set extended information $x_{ccs,5}, x_{ccs,6}$ and $x_{info,1} = x_{ccs,5}, x_{info,2} = x_{ccs,6}$ . The start code $k_{start}$ is signalled by the bits $x_{ccs,1}, x_{ccs,2}, x_{ccs,5}$ and the stop code $k_{stop}$ by the bits $x_{ccs,3}, x_{ccs,4}, x_{ccs,6}$ . The mapping in Table 16Ba below applies. + +If a value of $k_{start} = 5$ and $k_{stop} = 2$ is signalled, a spreading factor of $SF=1$ shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ are not used. + +If the field flag $x_{flag,2,1}=1$ , the bits $x_{info,1}$ , $x_{info,2}$ are comprised of the special default midamble pattern indicator ( $x_{mpi,1}$ , $x_{mpi,2}$ ) and $x_{info,1}=x_{mpi,1}$ and $x_{info,2}=x_{mpi,2}$ . The mapping in Table 16Bb below applies. The start code $k_{start}$ is signalled by the bits $x_{ccs,1}$ , $x_{ccs,2}$ and the stop code $k_{stop}$ by the bits $x_{ccs,3}$ , $x_{ccs,4}$ . The mapping in Table 16Bc below applies. + +If a value of $k_{start}=13$ and $k_{stop}=4$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ are not used + +**Table 16Ba: Channelisation code set information mapping** + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $x_{ccs,5}$ | $k_{stop}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | $x_{ccs,6}$ | +|-------------|-------------|-------------|-------------|------------|-------------|-------------|-------------| +| 1 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | +| 3 | 0 | 0 | 1 | 4 | 0 | 0 | 1 | +| 5 | 0 | 1 | 0 | 6 | 0 | 1 | 0 | +| 7 | 0 | 1 | 1 | 8 | 0 | 1 | 1 | +| 9 | 1 | 0 | 0 | 10 | 1 | 0 | 0 | +| 11 | 1 | 0 | 1 | 12 | 1 | 0 | 1 | +| 13 | 1 | 1 | 0 | 14 | 1 | 1 | 0 | +| 15 | 1 | 1 | 1 | 16 | 1 | 1 | 1 | + +**Table 16Bb: Special default midamble pattern mapping** + +| Special default Midamble pattern | $x_{mpi,1}$ | $x_{mpi,2}$ | +|----------------------------------|-------------|-------------| +| pattern 1A | 0 | 0 | +| pattern 1B | 0 | 1 | +| pattern 2A | 1 | 0 | +| pattern 2B | 1 | 1 | + +**Table 16Bc: Channelisation code set information mapping** + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $k_{stop}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | +|-------------|-------------|-------------|------------|-------------|-------------| +| 1 | 0 | 0 | 4 | 0 | 0 | +| 5 | 0 | 1 | 8 | 0 | 1 | +| 9 | 1 | 0 | 12 | 1 | 0 | +| 13 | 1 | 1 | 16 | 1 | 1 | + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1. + +#### 4.6H.1.2 Transport block size index mapping + +The transport-block size information $x_{tbs,1}$ , $x_{tbs,2}$ , ..., $x_{tbs,6}$ is the unsigned binary representation of the transport block size index where $x_{tbs,1}$ is MSB. The mapping is performed according to section 4.6.1.8. + +#### 4.6H.1.3 Modulation scheme information mapping + +The mapping of the modulation scheme information $x_{ms,1}$ is performed according to section 4.6.1.3. + +#### 4.6H.1.4 Timeslot information mapping + +The mapping of the time slot information $x_{is,1}, x_{is,2}, \dots, x_{is,5}$ is performed according to section 4.6.1.2.1. + +#### 4.6H.1.5 Redundancy version information mapping + +The redundancy version (RV) parameters $r, s$ and constellation version parameter $b$ are mapped jointly to produce the value $X_{rv}$ . $X_{rv}$ is alternatively represented as the sequence $x_{rv,1}, x_{rv,2}$ where $x_{rv,1}$ is the MSB. The mapping is performed according to section 4.6C.1.8. If $X_{rv} = 0$ , the UE shall treat the corresponding transport block as an initial transmission. + +#### 4.6H.1.6 Type flag mapping + +The type flag $x_{flag1,1}, x_{flag1,2}, x_{flag1,3}, x_{flag1,4}, x_{flag1,5}, x_{flag1,6}$ is mapped as '000000'. The type flag is used to distinguish HS-SCCH type 8 from other types. + +#### 4.6H.1.7 Field flag mapping + +The field flag is used to distinguish the mapping of special information $x_{info,1}, x_{info,2}$ . + +If $x_{flag2,1} = '0'$ , the special information $x_{info,1}, x_{info,2}$ are comprised of the channelisation code set extended information $x_{ccs,5}, x_{ccs,6}$ and $x_{info,1} = x_{ccs,5}, x_{info,2} = x_{ccs,6}$ . + +If $x_{flag2,1} = '1'$ , the special information $x_{info,1}, x_{info,2}$ are comprised of the special default midamble pattern indicator ( $x_{mpi,1}, x_{mpi,2}$ ). + +#### 4.6H.1.8 Special Information mapping + +The special information $x_{info,1}, x_{info,2}$ is mapped such that $x_{info,1}$ corresponds to the MSB and $x_{info,2}$ to the LSB. + +If $x_{flag2,1} = '0'$ , the special information $x_{info,1}, x_{info,2}$ are comprised of the channelisation code set extended information $x_{ccs,5}, x_{ccs,6}$ and $x_{info,1} = x_{ccs,5}, x_{info,2} = x_{ccs,6}$ . + +If $x_{flag2,1} = '1'$ , the special information $x_{info,1}, x_{info,2}$ are comprised of the special default midamble pattern indicator ( $x_{mpi,1}, x_{mpi,2}$ ). + +#### 4.6H.1.9 HARQ process identifier mapping + +The hybrid-ARQ process information $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ is unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +#### 4.6H.1.10 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6H.1.11 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6H.2 Multiplexing of HS-SCCH type 8 information + +The information carried on the HS-SCCH type 8 is multiplexed onto the bits according to the following rule: + +#### 4.6H.3 CRC attachment for HS-SCCH type 8 + +The sequence of bits $c$ , is calculated according to subclause 4.6.3. + +#### 4.6H.4 Channel coding for HS-SCCH type 8 + +Channel coding for the HS-SCCH type 8 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 8. + +#### 4.6H.5 Rate matching for HS-SCCH type 8 + +Rate matching for HS-SCCH type 8 shall be done with the general method described in 4.6.5. + +#### 4.6H.6 Interleaving for HS-SCCH type 8 + +Interleaving for HS-SCCH type 8 shall be done with the general method described in 4.2.11.1. + +#### 4.6H.7 Physical Channel Segmentation for HS-SCCH type 8 + +Physical channel segmentation for HS-SCCH type 8 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +#### 4.6H.8 Physical channel mapping for HS-SCCH type 8 + +Physical channel mapping for the HS-SCCH type 8 shall be done with the general method described in subclause 4.2.12. + +### 4.6I Coding/Multiplexing for HS-SCCH type 9 (1.28 Mcps TDD only) + +HS-SCCH shall be of type 9 when the following conditions are true: + +- the UE is configured in MIMO mode, and +- the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16. + +HS-SCCH type 9 is used for dual stream transmission in MIMO mode. The following information is transmitted by means of the HS-SCCH type 9 physical channels. + +- Channelisation-code-set information (4 bits): $x_{ccs,1}, x_{ccs,2}, \dots, x_{ccs,4}$ +- Transport-block size information for stream 1 (6 bits): $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,6}$ +- Modulation scheme information for stream 1 (1 bit): $x_{ms1,1}$ +- Time slot information (5bits): $x_{ts,1}, x_{ts,2}, \dots, x_{ts,5}$ +- Redundancy version information for stream 1 (2 bits): $x_{rv1,1}, x_{rv1,2}$ +- Transport-block size information for stream 2 (6 bits): $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,6}$ +- Modulation scheme information for stream 2 (1 bit): $x_{ms2,1}$ +- Redundancy version information for stream 2 (2 bits): $x_{rv2,1}, x_{rv2,2}$ + +- Hybrid-ARQ process information (4 bits): $x_{hap,1}, x_{hap,2}, x_{hap,3}, x_{hap,4}$ , +- HS-SCCH cyclic sequence number (3 bits): $x_{hesn,1}, x_{hesn,2}, x_{hesn,3}$ +- UE identity (16 bits): $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The following coding/multiplexing steps for HS-SCCH type 9 can be identified: + +- multiplexing of HS-SCCH type 9 information (see subclause 4.6I.2) +- CRC attachment for HS-SCCH type 9 (see subclause 4.6I.3); +- channel coding for HS-SCCH type 9 (see subclause 4.6I.4); +- rate matching for HS-SCCH type 9 (see subclause 4.6I.5); +- interleaving for HS-SCCH type 9 (see subclause 4.6I.6); +- mapping to physical channels for HS-SCCH type 9 (see subclauses 4.6I.7 and 4.6I.8). + +The general coding/multiplexing flow for HS-SCCH type 9 is shown in Figure 19H. + +![A large black rectangular area, likely a placeholder for Figure 19H.](0fa3b4af7842aaed476a9a6bab544b28_img.jpg) + +A large black rectangular area, likely a placeholder for Figure 19H. The image is a solid black rectangle with no visible content or text. + +A large black rectangular area, likely a placeholder for Figure 19H. + +Figure 19H: Coding and Multiplexing for HS-SCCH type 9 + +## 4.6I.1 HS-SCCH type 9 information field mapping + +### 4.6I.1.1 Channelisation code set information mapping + +HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code. The start code $k_{start}$ is signalled by the bits $x_{ccs,1}$ , $x_{ccs,2}$ and the stop code $k_{stop}$ by the bits $x_{ccs,3}$ , $x_{ccs,4}$ . The mapping in Table 16 C below applies. + +If a value of $k_{start} = 5$ and $k_{stop} = 4$ is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, $k_{start} > k_{stop}$ are not used. + +**Table 16C: Channelisation code set information mapping** + +| $k_{start}$ | $x_{ccs,1}$ | $x_{ccs,2}$ | $k_{stop}$ | $x_{ccs,3}$ | $x_{ccs,4}$ | +|-------------|-------------|-------------|------------|-------------|-------------| +| 1 | 0 | 0 | 4 | 0 | 0 | +| 5 | 0 | 1 | 8 | 0 | 1 | +| 9 | 1 | 0 | 12 | 1 | 0 | +| 13 | 1 | 1 | 16 | 1 | 1 | + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1. + +### 4.6I.1.2 Transport block size offset information mapping + +The transport-block size information for stream 1 $x_{tbs1,1}$ , $x_{tbs1,2}$ , ..., $x_{tbs1,6}$ is the unsigned binary representation of the transport block size index where $x_{tbs1,1}$ is MSB. The mapping is performed according to section 4.6.1.8. + +The transport-block size information for stream 2 $x_{tbs2,1}$ , $x_{tbs2,2}$ , ..., $x_{tbs2,6}$ is the unsigned binary representation of the transport block size index where $x_{tbs2,1}$ is MSB. The mapping is performed according to section 4.6.1.8. + +### 4.6I.1.3 Modulation scheme information mapping + +The mapping of the modulation scheme information for each stream ( $x_{ms1,1}$ for stream 1 or $x_{ms2,1}$ for stream 2) is performed according to section 4.6.1.3. + +### 4.6I.1.4 Timeslot information mapping + +The mapping of the time slot information $x_{ts,1}$ , $x_{ts,2}$ , ..., $x_{ts,5}$ is performed according to section 4.6.1.2.1. + +### 4.6I.1.5 Redundancy version information mapping + +The mapping of the redundancy version for each stream ( $x_{rv1,1}$ , $x_{rv1,2}$ for stream 1 and $x_{rv2,1}$ , $x_{rv2,2}$ for stream 2) is performed according to section 4.6E.1.8. + +### 4.6I.1.6 HARQ process identifier mapping + +The hybrid-ARQ process information $x_{hap,1}$ , $x_{hap,2}$ , $x_{hap,3}$ , $x_{hap,4}$ is unsigned binary representation of the HARQ process identifier where $x_{hap,1}$ is MSB. + +For dual stream transmission, two transport blocks are transmitted on the associated HS-PDSCH(s), and the mapping relationship between the hybrid-ARQ processes and the transport blocks is such that when the HARQ-process with + +identifier is mapped to the transport block on stream 1, the HARQ-process with the identifier given by shall be mapped to the transport block on stream 2, where $N_{proc}$ is the number of HARQ processes configured by higher layers. + +#### 4.6I.1.9 HS-SCCH cyclic sequence number + +The HS-SCCH cyclic sequence number $x_{hcsn,1}, x_{hcsn,2}, x_{hcsn,3}$ is mapped such that $x_{hcsn,1}$ corresponds to the MSB and $x_{hcsn,3}$ to the LSB. + +#### 4.6I.1.10 UE identity + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +### 4.6I.2 Multiplexing of HS-SCCH type 9 information + +The information carried on the HS-SCCH type 9 is multiplexed onto the bits according to the following rule : + +#### 4.6I.3 CRC attachment for HS-SCCH type 9 + +The sequence of bits , is calculated according to subclause 4.6.3. + +#### 4.6I.4 Channel coding for HS-SCCH type 9 + +Channel coding for the HS-SCCH type 9 shall be done with the general method described in 4.2.3 with the following specific parameters: + +The rate 1/3 convolutional coding shall be used for HS-SCCH type 9. + +#### 4.6I.5 Rate matching for HS-SCCH type 9 + +Rate matching for HS-SCCH type 9 shall be done with the general method described in 4.6.5. + +#### 4.6I.6 Interleaving for HS-SCCH type 9 + +Interleaving for HS-SCCH type 9 shall be done with the general method described in 4.2.11.1. + +#### 4.6I.7 Physical Channel Segmentation for HS-SCCH type 9 + +Physical channel segmentation for HS-SCCH type 9 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2. + +#### 4.6I.8 Physical channel mapping for HS-SCCH type 9 + +Physical channel mapping for the HS-SCCH type 9 shall be done with the general method described in subclause 4.2.12. + +## 4.6J Coding/Multiplexing for HS-SCCH orders type B (1.28Mcps TDD only) + +HS-SCCH orders type B are commands sent to the UE using HS-SCCH. No HS-PDSCH is associated with HS-SCCH orders. + +HS-SCCH order type B may be used when any of the following two conditions is met: + +- **CONTROL\_CHANNEL\_DRX\_STATUS** is TRUE and UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16; +- The variable **HS\_DSCH\_SPS\_STATUS** is TRUE, and UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16. + +The following information is transmitted by means of the HS-SCCH order type B physical channel. + +- **Order type (3 bits)**: $x_{odt,1}, x_{odt,2}, x_{odt,3}$ +- **UE identity (16 bits)**: $x_{ue,1}, x_{ue,2}, \dots, x_{ue,16}$ + +The coding for HS-SCCH orders type B is specified in subclause 4.6F. + +### 4.6J.1 HS-SCCH orders type B information field mapping + +#### 4.6J.1.1 Order type mapping + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '001'$ , then the HS-SCCH order is an order to release the allocated semi-persistent HS-PDSCH resources when UE is in CELL\_DCH state. + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '010'$ , then the HS-SCCH order is DRX Activation order when UE is in CELL\_DCH state. + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '011'$ , then the HS-SCCH order is DRX De-activation order when UE is in CELL\_DCH state. + +#### 4.6J.1.2 UE identity mapping + +The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that $x_{ue,1}$ corresponds to the MSB and $x_{ue,16}$ to the LSB, cf. [14]. + +## 4.7 Coding for HS-SICH + +The following information, provided by higher layers, is transmitted by means of the HS-SICH physical channel. + +For 1.28 Mcps TDD, HS-SICH type 1 is not used for dual stream transmission when UE is configured in MIMO mode. + +In this section, the terms "HS-SICH" and "HS-SICH type 1" are used interchangeably. + +For 1.28 Mcps TDD, in the case of multi-frequency HS-DSCH transmission in one TTI, HS-PDSCH on each frequency shall be configured with associated HS-SICH(s) which is coded as following. + +- **Recommended Modulation Format (RMF) (1 bit)**: $x_{rmf,1}$ +- **Recommended Transport-block size (RTBS) (n bits where n = 6 for 1.28 Mcps TDD and n = 9 for 3.84 Mcps TDD and 7.68Mcps TDD)**: $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,n}$ +- **Hybrid-ARQ information ACK/NACK (1 bit)**: $x_{an,1}$ + +The following coding/multiplexing steps can be identified: + +- separate coding of RMF, RTBS and ACK/NACK (see subclause 4.7.2); +- multiplexing of HS-SICH information (see subclause 4.7.3); + +- interleaving for HS-SICH (see subclause 4.7.4); +- mapping to physical channels (see subclause 4.7.5). + +The general coding/multiplexing flow is shown in the figure 20. + +![Figure 20: Coding and multiplexing for HS-SICH. A block diagram showing the flow from input bits to physical channel mapping. Inputs are x_rmf,1 and x_tbs,1...x_tbs,n into 'Field Coding of CQI', and x_an,1 into 'Field Coding of ACK/NACK'. Outputs are z_1, z_2...z_n_cqi and c_1, c_2...c_36 respectively. These enter 'HS-SICH Multiplexing' to produce d_1, d_2...d_U, followed by 'HS-SICH interleaving' to produce v_1, v_2...v_U, and finally 'Physical Channel Mapping' to output PhCH.](a320e67b369bfde4a5fa360b100da55c_img.jpg) + +``` + +graph TD + subgraph Inputs + I1[" $x_{rmf,1}, x_{tbs,1}, \dots, x_{tbs,n}$ "] + I2[" $x_{an,1}$ "] + end + I1 --> FC1[Field Coding of CQI] + I2 --> FC2[Field Coding of ACK/NACK] + FC1 --> Z[" $z_1, z_2, \dots, z_{n_{cqi}}$ "] + FC2 --> C[" $c_1, c_2, \dots, c_{36}$ "] + Z --> HM[HS-SICH Multiplexing] + C --> HM + HM --> D[" $d_1, d_2, \dots, d_U$ "] + D --> HI[HS-SICH interleaving] + HI --> V[" $v_1, v_2, \dots, v_U$ "] + V --> PCM[Physical Channel Mapping] + PCM --> PHCH[PhCH] + +``` + +Figure 20: Coding and multiplexing for HS-SICH. A block diagram showing the flow from input bits to physical channel mapping. Inputs are x\_rmf,1 and x\_tbs,1...x\_tbs,n into 'Field Coding of CQI', and x\_an,1 into 'Field Coding of ACK/NACK'. Outputs are z\_1, z\_2...z\_n\_cqi and c\_1, c\_2...c\_36 respectively. These enter 'HS-SICH Multiplexing' to produce d\_1, d\_2...d\_U, followed by 'HS-SICH interleaving' to produce v\_1, v\_2...v\_U, and finally 'Physical Channel Mapping' to output PhCH. + +**Figure 20: Coding and multiplexing for HS-SICH** + +### 4.7.1 HS-SICH information field mapping + +#### 4.7.1.1 RMF information mapping + +The RMF information bit, $x_{rmf,1}$ , shall be mapped according to the mapping specified in subclause 4.6.1.3. + +#### 4.7.1.2 RTBS information mapping + +The RTBS information bits, $x_{tbs,1}, x_{tbs,2}, \dots, x_{tbs,n}$ , shall be mapped according to the same mapping as is used for the transport block size information bits in subclause 4.6. This mapping is defined by higher layers [12]. + +#### 4.7.1.3 ACK/NACK information mapping + +The ACK/NACK information bit $x_{an,1}$ shall be mapped according to the mapping given in Table 20 below. + +**Table 20: ACK/NACK information mapping** + +| ACK/NACK | $x_{an,1}$ | +|-----------------|------------| +| ACK | 1 | +| NACK | 0 | + +## 4.7.2 Coding for HS-SICH + +### 4.7.2.1 Field Coding of ACK/NACK + +The ACK/NACK bit $x_{an,i}$ shall be repetition coded to 36 bits. The coded bits are defined as . + +### 4.7.2.2 Field Coding of CQI + +#### 4.7.2.2.1 Field Coding of CQI for 1.28 Mcps TDD + +The quality information consists of Recommended Transport Block Size (RTBS) and Recommended Modulation Format (RMF) fields. The 6 bits of the RTBS field are coded to 32 bits using a (32, 6) 1st order Reed-Muller code. The coding procedure is as shown in figure 21. + +![Figure 21: Field coding of RTBS information bits. A block diagram showing the input bits x_tbs,1, x_tbs,2, ..., x_tbs,6 entering a block labeled '(32,6) 1st order Reed-Muller Code', which outputs the coded bits z_1, z_2, ..., z_32.](bc3d1c04d342094c893d5064974c9ee7_img.jpg) + +Figure 21: Field coding of RTBS information bits. A block diagram showing the input bits x\_tbs,1, x\_tbs,2, ..., x\_tbs,6 entering a block labeled '(32,6) 1st order Reed-Muller Code', which outputs the coded bits z\_1, z\_2, ..., z\_32. + +**Figure 21: Field coding of RTBS information bits** + +The coding uses a subset basis sequences as the TFCI coder as described in subclause 4.3.1.1. The basis sequences that are used for RTBS coding are as follows in table 21. + +**Table 21: Basis sequences for (32,6) RTBS code** + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | +|----|------------------|------------------|------------------|------------------|------------------|------------------| +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | +| 1 | 0 | 1 | 0 | 0 | 0 | 1 | +| 2 | 1 | 1 | 0 | 0 | 0 | 1 | +| 3 | 0 | 0 | 1 | 0 | 0 | 1 | +| 4 | 1 | 0 | 1 | 0 | 0 | 1 | +| 5 | 0 | 1 | 1 | 0 | 0 | 1 | +| 6 | 1 | 1 | 1 | 0 | 0 | 1 | +| 7 | 0 | 0 | 0 | 1 | 0 | 1 | +| 8 | 1 | 0 | 0 | 1 | 0 | 1 | +| 9 | 0 | 1 | 0 | 1 | 0 | 1 | +| 10 | 1 | 1 | 0 | 1 | 0 | 1 | +| 11 | 0 | 0 | 1 | 1 | 0 | 1 | +| 12 | 1 | 0 | 1 | 1 | 0 | 1 | +| 13 | 0 | 1 | 1 | 1 | 0 | 1 | +| 14 | 1 | 1 | 1 | 1 | 0 | 1 | +| 15 | 1 | 0 | 0 | 0 | 1 | 1 | +| 16 | 0 | 1 | 0 | 0 | 1 | 1 | +| 17 | 1 | 1 | 0 | 0 | 1 | 1 | +| 18 | 0 | 0 | 1 | 0 | 1 | 1 | +| 19 | 1 | 0 | 1 | 0 | 1 | 1 | +| 20 | 0 | 1 | 1 | 0 | 1 | 1 | +| 21 | 1 | 1 | 1 | 0 | 1 | 1 | +| 22 | 0 | 0 | 0 | 1 | 1 | 1 | +| 23 | 1 | 0 | 0 | 1 | 1 | 1 | +| 24 | 0 | 1 | 0 | 1 | 1 | 1 | +| 25 | 1 | 1 | 0 | 1 | 1 | 1 | +| 26 | 0 | 0 | 1 | 1 | 1 | 1 | +| 27 | 1 | 0 | 1 | 1 | 1 | 1 | +| 28 | 0 | 1 | 1 | 1 | 1 | 1 | +| 29 | 1 | 1 | 1 | 1 | 1 | 1 | +| 30 | 0 | 0 | 0 | 0 | 0 | 1 | +| 31 | 0 | 0 | 0 | 0 | 1 | 1 | + +The output RTBS code word bits $\{z_i : i = 1, \dots, 32\}$ are given by: + +The RMF bit $x_{rmf,1}$ is repetition coded to 16 bits to produce the bits $w_1, w_2, \dots, w_{16}$ where $n_{CQI} = 48$ . + +#### 4.7.2.2.2 Field Coding of CQI for 3.84 Mcps TDD and 7.68 Mcps TDD + +RTBS and RMF bits are multiplexed onto the bits according to the following rule : + +The bits are coded to produce the bits $w_1, w_2, \dots, w_{32}$ using a (32,10) sub-code of the second order Reed-Muller code as defined in subclause 4.3.1.1.. + +The bits $w_1, w_2, \dots, w_{32}$ are used to produce the CQI bits using a (4,1) repetition code, where $n_{CQI} = 128$ , such that: + +$$z_n, z_{n+32}, z_{n+64}, z_{n+96} = w_n \quad n=1 \dots 32$$ + +### 4.7.3 Multiplexing of HS-SICH information fields + +The CQI bits are multiplexed with the repetition coded ACK/NACK bits to produce the bits where $n$ is the number of physical channel bits carried by HS-SICH, according to the following rule.: + +### 4.7.4 Interleaver for HS-SICH + +Interleaver for HS-SICH shall be done with the general method described in 4.2.11.1. + +### 4.7.5 Physical channel mapping for HS-SICH + +Physical channel mapping for HS-SICH shall be done with the general method described in 4.2.12. + +## 4.7A Coding for HS-SICH type 2 (1.28 Mcps TDD only) + +HS-SICH type 2 is used for dual stream transmission when UE is configured in MIMO mode. + +The following information, provided by higher layers, is transmitted by means of the HS-SICH type 2 physical channels. + +- Recommended Modulation Format (RMF) for stream 1 (1 bit): $x_{rmf1,1}$ +- Recommended Modulation Format (RMF) for stream 2 (1 bit): $x_{rmf2,1}$ +- Recommended Transport-block size (RTBS) for stream 1 (n=6 bits): $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,n}$ +- Recommended Transport-block size (RTBS) for stream 2 (n=6 bits): $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,n}$ +- Hybrid-ARQ information ACK/NACK for stream 1 (1 bit): $x_{an1,1}$ +- Hybrid-ARQ information ACK/NACK for stream 2 (1 bit): $x_{an2,1}$ + +The following coding/multiplexing steps can be identified: + +- separate coding of RMF, RTBS and ACK/NACK (see subclause 4.7A.2); + +- multiplexing of HS-SICH information (see subclause 4.7A.3); +- interleaving for HS-SICH (see subclause 4.7A.4); +- mapping to physical channels (see subclause 4.7A.5). + +The general coding/multiplexing flow for HS-SICH type 2 is shown in the figure 20A. + +![Figure 20A: Coding and multiplexing for HS-SICH type 2. The diagram shows a large black rectangle at the top, representing the input data. Below it, four small white rectangles are arranged horizontally, representing the output channels or streams.](9bafc60bf378685e5e246c3ffad7b792_img.jpg) + +Figure 20A: Coding and multiplexing for HS-SICH type 2. The diagram shows a large black rectangle at the top, representing the input data. Below it, four small white rectangles are arranged horizontally, representing the output channels or streams. + +**Figure 20A: Coding and multiplexing for HS-SICH type 2** + +## 4.7A.1 HS-SICH type 2 information field mapping + +### 4.7A.1.1 RMF information mapping + +The RMF information bit for each stream, $x_{rmf1,1}$ for stream 1 or $x_{rmf2,1}$ for stream 2, shall be mapped according to the mapping given in subclause 4.7.1.1 respectively. + +### 4.7A.1.2 RTBS information mapping + +The RTBS information bits for each stream, $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,n}$ for stream 1 or $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,n}$ for stream 2, shall be mapped according to the mapping given in subclause 4.7.1.2 respectively. + +### 4.7A.1.3 ACK/NACK information mapping + +The ACK/NACK information bit for each stream, $x_{an1,1}$ for stream 1 or $x_{an2,1}$ for stream 2, shall be mapped according to the mapping given in subclause 4.7.1.3 respectively. + +## 4.7A.2 Coding for HS-SICH type 2 + +### 4.7A.2.1 Field Coding of ACK/NACK + +The ACK/NACK bit for stream 1, $x_{an1,1}$ , shall be repetition coded to 36 bits. The coded bits are defined as . + +The ACK/NACK bit for stream 2, $x_{an2,1}$ , shall be repetition coded to 36 bits. The coded bits are defined as . + +### 4.7A.2.2 Field Coding of CQI + +The quality information for each stream consists of Recommended Transport Block Size (RTBS) and Recommended Modulation Format (RMF) fields. The 6 bits of the RTBS field for each stream are coded to 32 bits using a (32, 6) 1st order Reed-Muller code respectively. The coding procedure for each stream is performed according to section 4.7.2.2 shown in figure 21A and figure 21B. + +![Figure 21A: Field coding of RTBS information bits for stream 1. A block diagram showing input bits x_tbs1,1 through x_tbs1,6 entering a (32,6) 1st order Reed-Muller Code block, resulting in output bits z_1,1 through z_1,32.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + + graph LR + In(" $x_{tbs1,1}, x_{tbs1,2}, \dots, x_{tbs1,6}$ ") --> RM["(32,6) 1st order +Reed-Muller +Code"] + RM --> Out(" $z_{1,1}, z_{1,2}, \dots, z_{1,32}$ ") + +``` + +Figure 21A: Field coding of RTBS information bits for stream 1. A block diagram showing input bits x\_tbs1,1 through x\_tbs1,6 entering a (32,6) 1st order Reed-Muller Code block, resulting in output bits z\_1,1 through z\_1,32. + +**Figure 21A: Field coding of RTBS information bits for stream 1** + +![Figure 21B: Field coding of RTBS information bits for stream 2. A block diagram showing input bits x_tbs2,1 through x_tbs2,6 entering a (32,6) 1st order Reed-Muller Code block, resulting in output bits z_2,1 through z_2,32.](346324c08906e6d9320f632ab916f73e_img.jpg) + +``` + + graph LR + In(" $x_{tbs2,1}, x_{tbs2,2}, \dots, x_{tbs2,6}$ ") --> RM["(32,6) 1st order +Reed-Muller +Code"] + RM --> Out(" $z_{2,1}, z_{2,2}, \dots, z_{2,32}$ ") + +``` + +Figure 21B: Field coding of RTBS information bits for stream 2. A block diagram showing input bits x\_tbs2,1 through x\_tbs2,6 entering a (32,6) 1st order Reed-Muller Code block, resulting in output bits z\_2,1 through z\_2,32. + +**Figure 21B: Field coding of RTBS information bits for stream 2** + +The RMF bit for stream 1, $x_{rmf1,1}$ , is repetition coded to 16 bits to produce the bits $z_{1,33}, z_{1,34}, \dots, z_{1,48}$ where $n_{CQI} = 48$ . + +The RMF bit for stream 2, $x_{rmf2,1}$ , is repetition coded to 16 bits to produce the bits $z_{2,33}, z_{2,34}, \dots, z_{2,48}$ where $n_{CQI} = 48$ . + +#### 4.7A.3 Multiplexing of HS-SICH type 2 information fields + +The CQI bits for each stream, $z_{i,1}, z_{i,2}, \dots, z_{i,32}$ , are multiplexed with the repetition coded ACK/NACK bits for each stream, $z_{i,33}, z_{i,34}, \dots, z_{i,48}$ , to produce the bits $z_{i,1}, z_{i,2}, \dots, z_{i,n_{HS-SICH}}$ where $n_{HS-SICH}$ is the number of physical channel bits carried by HS-SICH, according to the following rule: + +#### 4.7A.4 Interleaver for HS-SICH type 2 + +Interleaver for HS-SICH shall be done with the general method described in [4.2.11.1](#). + +#### 4.7A.5 Physical channel mapping for HS-SICH type 2 + +Physical channel mapping for HS-SICH shall be done with the general method described in [4.2.12](#). + +### 4.8 Coding for E-DCH + +Figure 22 shows the processing structure for the E-DCH transport channel mapped onto a separate CCTrCH. Data arrives to the coding unit in form of a maximum of one transport block once every transmission time interval (TTI). A 10ms TTI is used for E-DCH for 3.84Mcps and 7.68Mcps TDD whilst for 1.28Mcps TDD, a TTI of 5ms will be used. + +For 1.28Mcps TDD multi-carrier E-DCH transmission, a number of transport blocks may arrive at the coding unit in one TTI, where the number of the transport blocks equals to the number of the scheduled E-DCH carriers. Each transport block for each scheduled E-DCH carrier shall be coded separately. The following coding steps for E-DCH on one carrier can be identified: + +- add CRC to each transport block ([see subclause 4.8.1](#)); +- code block segmentation ([see subclause 4.8.2](#)); +- channel coding ([see subclause 4.8.3](#)); +- hybrid ARQ ([see subclause 4.8.4](#)); +- bit scrambling ([see subclause 4.8.5](#)); + +- interleaving for E-DCH (see subclause 4.8.6); +- constellation re-arrangement for 16QAM (see subclause 4.8.7); +- mapping to physical channels (see subclause 4.8.8). + +![Flowchart of the coding chain for E-DCH. The process starts with input bits a_im1, a_im2, a_im3, ..., a_imA. It proceeds through CRC attachment, resulting in bits b_im1, b_im2, b_im3, ..., b_imB. This is followed by code block segmentation, resulting in bits o_ir1, o_ir2, o_ir3, ..., o_irK. The next step is channel coding, resulting in bits c_i1, c_i2, c_i3, ..., c_iE. This is followed by Physical Layer Hybrid-ARQ functionality, resulting in bits w_1, w_2, w_3, ..., w_R. The next step is bit scrambling, resulting in bits s_1, s_2, s_3, ..., s_R. This is followed by E-DCH interleaving, resulting in bits v_1, v_2, v_3, ..., v_R. The next step is constellation re-arrangement for 16 QAM, resulting in bits r_1, r_2, r_3, ..., r_R. The final step is physical channel mapping, resulting in bits w_t,1, w_t,2, ..., w_t,Ut. The output is then split into two physical channels: PhCH#1 and PhCH#P.](5ec3284657e4df0df3653dd61d0ecd13_img.jpg) + +``` + +graph TD + Input["a_im1, a_im2, a_im3, ..., a_imA"] --> CRC["CRC attachment"] + CRC --> BitsB["b_im1, b_im2, b_im3, ..., b_imB"] + BitsB --> Segmentation["Code block segmentation"] + Segmentation --> BitsK["o_ir1, o_ir2, o_ir3, ..., o_irK"] + BitsK --> Coding["Channel Coding"] + Coding --> BitsE["c_i1, c_i2, c_i3, ..., c_iE"] + BitsE --> HARQ["Physical Layer Hybrid-ARQ functionality"] + HARQ --> BitsR["w_1, w_2, w_3, ..., w_R"] + BitsR --> Scrambling["Bit Scrambling"] + Scrambling --> BitsS["s_1, s_2, s_3, ..., s_R"] + BitsS --> Interleaving["E-DCH Interleaving"] + Interleaving --> BitsV["v_1, v_2, v_3, ..., v_R"] + BitsV --> Constellation["Constellation re-arrangement for 16 QAM"] + Constellation --> BitsR2["r_1, r_2, r_3, ..., r_R"] + BitsR2 --> Mapping["Physical channel mapping"] + Mapping --> BitsUt["w_t,1, w_t,2, ..., w_t,Ut"] + BitsUt --> PhCH1["PhCH#1"] + BitsUt --> PhCHP["PhCH#P"] + +``` + +Flowchart of the coding chain for E-DCH. The process starts with input bits a\_im1, a\_im2, a\_im3, ..., a\_imA. It proceeds through CRC attachment, resulting in bits b\_im1, b\_im2, b\_im3, ..., b\_imB. This is followed by code block segmentation, resulting in bits o\_ir1, o\_ir2, o\_ir3, ..., o\_irK. The next step is channel coding, resulting in bits c\_i1, c\_i2, c\_i3, ..., c\_iE. This is followed by Physical Layer Hybrid-ARQ functionality, resulting in bits w\_1, w\_2, w\_3, ..., w\_R. The next step is bit scrambling, resulting in bits s\_1, s\_2, s\_3, ..., s\_R. This is followed by E-DCH interleaving, resulting in bits v\_1, v\_2, v\_3, ..., v\_R. The next step is constellation re-arrangement for 16 QAM, resulting in bits r\_1, r\_2, r\_3, ..., r\_R. The final step is physical channel mapping, resulting in bits w\_t,1, w\_t,2, ..., w\_t,Ut. The output is then split into two physical channels: PhCH#1 and PhCH#P. + +**Figure 22. Coding chain for E-DCH** + +In the following the number of transport blocks is always one. When referencing non E-DCH formulae which are used in correspondence with E-DCH formulae the convention is used that transport block subscripts may be omitted (e.g. $X_i$ when $i$ is always 1 may be written $X$ ). + +#### 4.8.1 CRC attachment for E-DCH + +CRC attachment for the E-DCH transport channel shall be performed according to the general method described in 4.2.1 above with the following specific parameters. + +The CRC length shall always be $L_f=24$ bits. + +## 4.8.2 Code block segmentation for E-DCH + +Code block segmentation for the E-DCH transport channel shall be performed according to the general method described in 4.2.2.2 with the following specific parameters. + +There is a maximum of one transport block. The bits input to the block are mapped to the bits directly. It follows that $X_i = B_i$ . Note that the bits $x$ referenced here refer only to the internals of the code block segmentation function. The output bits from the code block segmentation function are $O_{ir1}, O_{ir2}, O_{ir3}, \dots, O_{irK}$ . + +The value of $Z = 5114$ for turbo coding shall be used. + +## 4.8.3 Channel coding for E-DCH + +Channel coding for the E-DCH transport channel shall be performed according to the general method described in section 4.2.3 above with the following specific parameters. + +There is a maximum of one transport block, $i=1$ . The rate 1/3 turbo coding shall be used. + +## 4.8.4 Physical layer HARQ functionality and rate matching for E-DCH + +The hybrid ARQ functionality matches the number of bits at the output of the channel coder to the total number of bits of the E-PUCH set to which the E-DCH transport channel is mapped. The hybrid ARQ functionality is controlled by the redundancy version (RV) parameters. + +![Diagram of E-DCH hybrid ARQ functionality showing bit separation, rate matching, and bit collection stages.](e694eeb983c07b3dd631358292db6af1_img.jpg) + +The diagram illustrates the E-DCH hybrid ARQ functionality. It starts with an input $N_{e,j}$ entering a 'bit separation' block. This block outputs three streams: 'Systematic bits' ( $N_{sys}$ ), 'Parity 1 bits' ( $N_{p1}$ ), and 'Parity 2 bits' ( $N_{p2}$ ). These streams enter a 'Rate Matching' section containing three blocks: 'RM\_S', 'RM\_P1\_2', and 'RM\_P2\_2'. The outputs of these blocks are $N_{L,sys}$ , $N_{tp1}$ , and $N_{tp2}$ respectively. These three streams then enter a 'bit collection' block, which outputs the final result $N_{e,data,j}$ . + +Diagram of E-DCH hybrid ARQ functionality showing bit separation, rate matching, and bit collection stages. + +Figure 23: E-DCH hybrid ARQ functionality + +### 4.8.4.1 Determination of SF, modulation and number of physical channels + +The SF, modulation type and number of E-PUCHs in the E-PUCH set is determined by higher layers (see [15]). These correspond to a value of $N_{e,data,j}$ . + +### 4.8.4.2 HARQ bit separation + +The HARQ bit separation function shall be performed in the same way as bit separation for turbo encoded TrCHs with puncturing in 4.2.7.2.1 above. + +### 4.8.4.3 HARQ Rate Matching Stage + +The hybrid ARQ rate matching for the E-DCH transport channel shall be done with the general method described in 4.2.7.3 with the following specific parameters. + +The parameters of the rate matching stage depend on the value of the RV parameters $s$ and $r$ . The $s$ and $r$ combinations corresponding to each RV allowed for the E-DCH are listed in table 22 below. + +**Table 22: RV for E-DCH** + +| E-DCH RV Index | s | r | +|----------------|---|---| +| 0 | 1 | 0 | +| 1 | 0 | 0 | +| 2 | 1 | 1 | +| 3 | 0 | 1 | + +The parameter $e_{plus}$ , $e_{minus}$ and $e_{ini}$ are calculated with the general method described in 4.5.4.3 above. The following parameters are used as input: + +$$N_{sys} = N_{p1} = N_{p2} = N_{e,j}/3$$ + +$$N_{data} = N_{e,data,j}$$ + +$$r_{max} = 2 \text{ (for both QPSK and 16-QAM)}$$ + +#### 4.8.4.4 HARQ bit collection + +HARQ bit collection for E-DCH shall be performed according to the general method described for HS-DSCH in subclause 4.5.4.4. + +#### 4.8.5 Bit scrambling + +The bit scrambling for E-DCH shall be performed in accordance with the general method described in subclause 4.2.9. + +#### 4.8.6 Interleaving for E-DCH + +Interleaving for E-DCH shall be performed in accordance with the general method described for HS-DSCH in subclause 4.5.6. + +#### 4.8.7 Constellation re-arrangement for 16 QAM + +Constellation rearrangement shall be performed in the case of 16-QAM in accordance with the general method described for HS-DSCH in subclause 4.5.7. For QPSK this function is transparent. + +For 3.84Mcps and 7.68Mcps, the constellation version parameter $b$ is associated with the E-DCH RV index as shown in table 23 below. + +**Table 23: Mapping of RV to constellation rearrangement parameter $b$ for E-DCH (3.84Mcps and 7.68Mcps options)** + +| E-DCH RV Index | $b$ | +|----------------|-----| +| 0 | 0 | +| 1 | 1 | +| 2 | 2 | +| 3 | 3 | + +For 1.28Mcps option, the constellation version parameter $b$ is associated with the retransmission sequence number (RSN). The mapping between RSN and $b$ parameters for constellation re-arrangement is listed in table 25A in subclause 4.9.2.1.2. + +#### 4.8.8 Physical channel mapping for E-DCH + +The E-PUCH is defined in [7]. The bits input to the physical channel mapping are denoted by $r_1, r_2, \dots, r_R$ , where $R = N_{e,data,j}$ and is the number of physical channel data bits to be transmitted in the current TTI. These bits are mapped to the physical channel bits, $\{w_{t,k} : t = 1, 2, \dots, T; \text{ and } k = 1, 2, \dots, U_t\}$ , where $t$ is the timeslot index, $T$ is the number of timeslots in the allocation message, $k$ is the physical channel bit index and $U_t$ is the number of bits in the E-PUCH physical channel in timeslot $t$ . The timeslot index, $t$ , increases with increasing timeslot number and the physical channel bit index, $k$ , increases with increasing physical channel bit position in time. + +The bits $r_1, r_2, \dots, r_R$ shall be mapped to the physical channel bits $w_{t,k}$ according to the following rule : + +for $k = 1, 2, \dots, U_1$ + +for $k = 1, 2, \dots, U_2$ + +... + +for $k = 1, 2, \dots, U_T$ + +## 4.9 Coding for E-UCCH + +### 4.9.1 Coding for E-UCCH for the 3.84Mcps and 7.68Mcps TDD options + +E-UCCH is coded in two parts, E-UCCH part 1 and E-UCCH part 2. Both parts of the E-UCCH are transmitted on the E-PUCH (see [7]). + +The following information is transmitted by means of E-UCCH part 1: + +- E-TFCI information: $x_{tfci,1}, x_{tfci,2}, \dots, x_{tfci,7}$ + +The following information is transmitted by means of E-UCCH part 2: + +- Retransmission sequence number (RSN): $x_{rsn,1}, x_{rsn,2}$ +- HARQ process ID (HARQ\_ID): $x_{harq,1}, x_{harq,2}$ + +#### 4.9.1.1 Overview + +Figure 24 below illustrates the overall coding chain for E-UCCH. + +![Figure 24: Coding chain for E-UCCH parts 1 and 2. The diagram shows two parallel processing paths. Path 1 (left) takes E-TFCI information (x_tfci,1, x_tfci,2, ..., x_tfci,7) as input, passes it through a 'Channel Coding' block to produce bits y_0, y_1, ..., y_31, then through a 'Physical channel mapping' block to produce E-UCCH part 1. Path 2 (right) takes RSN (x_rsn,1, x_rsn,2) and HARQ_ID (x_harq,1, x_harq,2) as input, passes them through a 'Multiplexing' block to produce bits x_1, x_2, ..., x_4, then through a 'Channel Coding' block to produce bits z_0, z_1, ..., z_31, then through a 'Physical channel mapping' block to produce E-UCCH part 2.](19f90331494ba1e143d915d8d0061942_img.jpg) + +``` + +graph TD + subgraph Path1 [E-UCCH part 1] + Input1[" $x_{tfci,1}, x_{tfci,2}, \dots, x_{tfci,7}$ "] --> CC1[Channel Coding] + CC1 --> Y[" $y_0, y_1, \dots, y_{31}$ "] + Y --> PCM1[Physical channel mapping] + PCM1 --> Output1[E-UCCH part 1] + end + subgraph Path2 [E-UCCH part 2] + Input2a[" $x_{rsn,1}, x_{rsn,2}$ "] --> M[Multiplexing] + Input2b[" $x_{harq,1}, x_{harq,2}$ "] --> M + M --> X[" $x_1, x_2, \dots, x_4$ "] + X --> CC2[Channel Coding] + CC2 --> Z[" $z_0, z_1, \dots, z_{31}$ "] + Z --> PCM2[Physical channel mapping] + PCM2 --> Output2[E-UCCH part 2] + end + +``` + +Figure 24: Coding chain for E-UCCH parts 1 and 2. The diagram shows two parallel processing paths. Path 1 (left) takes E-TFCI information (x\_tfci,1, x\_tfci,2, ..., x\_tfci,7) as input, passes it through a 'Channel Coding' block to produce bits y\_0, y\_1, ..., y\_31, then through a 'Physical channel mapping' block to produce E-UCCH part 1. Path 2 (right) takes RSN (x\_rsn,1, x\_rsn,2) and HARQ\_ID (x\_harq,1, x\_harq,2) as input, passes them through a 'Multiplexing' block to produce bits x\_1, x\_2, ..., x\_4, then through a 'Channel Coding' block to produce bits z\_0, z\_1, ..., z\_31, then through a 'Physical channel mapping' block to produce E-UCCH part 2. + +Figure 24: Coding chain for E-UCCH parts 1 and 2 + +#### 4.9.1.2 E-UCCH part 1 + +##### 4.9.1.2.1 Information field mapping of E-TFCI + +The E-TFCI is mapped such that $x_{tfci,1}$ corresponds to the MSB. + +##### 4.9.1.2.2 Channel coding for E-UCCH part 1 + +The E-TFCI bits are zero-padded and coded to produce the bits $y_0, y_1, \dots, y_{31}$ using a (32,10) sub-code of the second order Reed-Muller code as defined in subclause 4.3.1.1. Bits $y_0, y_1, \dots, y_9$ correspond to bits of subclause 4.3.1.1, and bits $y_{10}, y_{11}, \dots, y_{31}$ are set to zero. + +#### 4.9.1.2.3 Physical channel mapping for E-UCCH part 1 + +E-UCCH part 1 is described in [7]. The sequence of bits $y_0, y_1, \dots, y_{31}$ output from the E-UCCH part 1 channel coding is mapped to the E-UCCH part 1 indicator field of each E-PUCH of the E-DCH TTI configured to carry E-UCCH. The bits $y_i$ $\{i=0, 1, \dots, 31\}$ are mapped in an identical manner to that described for TFCI in subclause 4.3.1.3 such that they are transmitted over the air in ascending order with respect to $i$ . + +#### 4.9.1.3 E-UCCH part 2 + +##### 4.9.1.3.1 Information field mapping of retransmission sequence number + +To indicate the redundancy version (RV) of each HARQ transmission and to assist the Node B soft buffer management a two bit retransmission sequence number (RSN) is signalled from the UE to the Node B. The Node B can avoid soft buffer corruption by flushing the soft buffer associated to one HARQ process in case the last received RSN for that HARQ process is incompatible with the current one. + +The RSN is set by higher layers as described in [15]. For a given HARQ process, once the maximum RSN value of 3 is reached, the RSN alternates between the values of 2 and 3 for any further retransmissions. The RSN thus follows the pattern 0, 1, 2, 3, 2, 3, 2, 3, 2, 3, ... The RSN is transmitted by the physical layer in E-UCCH part 2. + +The bits $(x_{rsn,1}, x_{rsn,2})$ of the RSN field of E-UCCH part 2 are mapped such that $x_{rsn,1}$ corresponds to the MSB of the RSN and $x_{rsn,2}$ corresponds to the LSB of the RSN. + +The applied E-DCH RV index specifying the used RV ( $s$ and $r$ parameter) and in the case of 16-QAM, also the used constellation rearrangement parameter ( $b$ ) both depend only on the values of RSN, and on $N_{sys} / N_{e,data,j}$ as shown in table 25 below. + +**Table 25: Relation between RSN value and E-DCH RV Index** + +| RSN Value | $N_{sys} / N_{e,data,j} < 1/2$ | $1/2 \leq N_{sys} / N_{e,data,j}$ | +|-----------|--------------------------------|-----------------------------------| +| | E-DCH RV Index | E-DCH RV Index | +| 0 | 0 | 0 | +| 1 | 2 | 3 | +| 2 | 0 | 2 | +| 3 | 2 | 1 | + +The UE shall use either: + +- an RV index as indicated in Table 25 and according to the value of RSN +- or, if signalled by higher layers only E-DCH RV index 0 independently of the value of RSN. + +##### 4.9.1.3.2 Information field mapping of HARQ process ID + +The HARQ process ID bits $(x_{harq,1}, x_{harq,2})$ transmitted on E-UCCH part 2 correspond to the two LSBs of the 3-bit HARQ ID indicated by higher layers (the MSB of the higher layer HARQ ID is not transmitted). Thus, with the higher layer HARQ ID represented as $h_1, h_2, h_3$ (with $h_1$ as the MSB), bits $x_{harq,1}, x_{harq,2}$ correspond to bits $h_2, h_3$ . + +##### 4.9.1.3.3 Multiplexing of E-UCCH part 2 information + +The retransmission sequence number information $(x_{rsn,1}, x_{rsn,2})$ and the HARQ process ID information $(x_{harq,1}, x_{harq,2})$ are multiplexed together to give a sequence of bits $x_1, x_2, \dots, x_4$ where: + +$$x_k = x_{rsn,k} \quad k=1,2$$ + +$$x_k = x_{harq,k-2} \quad k=3,4$$ + +##### 4.9.1.3.4 Channel coding for E-UCCH part 2 + +The bits are zero-padded and coded to produce the bits $z_0, z_1, \dots, z_{31}$ using a (32,10) sub-code of the second order Reed-Muller code as defined in subclause 4.3.1.1. Bits correspond to bits of subclause 4.3.1.1, and bits of subclause 4.3.1.1 are set to zero. + +#### 4.9.1.3.5 Physical channel mapping for E-UCCH part 2 + +E-UCCH part 2 is described in [7]. The sequence of bits $z_0, z_1, \dots, z_{31}$ output from the E-UCCH part 2 channel coding is mapped to the E-UCCH part 2 indicator field of each E-PUCH of the E-DCH TTI configured to carry E-UCCH. The bits $z_i \{i=0,1,\dots,31\}$ are mapped such that they are transmitted over the air in ascending order with respect to $i$ . + +### 4.9.2 Coding for E-UCCH for the 1.28Mcps TDD option + +The E-UCCH on one carrier is used to convey the following information for the E-DCH on the same carrier: + +- The modulation type of the selected E-TFC – 0 bits (see note 1) +- The transport block size of the selected E-TFC – 6 bits +- The retransmission sequence number (RSN) – 2 bits +- The HARQ process ID – 2 bits + +Note 1: The occupied modulation type is not explicitly signaled, which is inferred from the transport block size. + +The E-UCCHs on the different carriers are coded independently. The E-UCCH on one carrier is transmitted on the E-PUCH on the same carrier and is coded using a (32, 10) sub code of the second order Reed Muller code as defined in subclause 4.3.1.1 + +Figure 24A below illustrates the overall coding chain for E-UCCH on one carrier. + +![Figure 24A: Coding chain for E-UCCH. The diagram shows a vertical flow of data through three processing blocks: Multiplexing, Channel Coding, and Physical Channel mapping. Inputs to the Multiplexing block are three groups of bits: X_tfc,1, ..., X_tfc,6; X_rsn,1, X_rsn,2; and X_harq,1, X_harq,2. The output of the Multiplexing block is a sequence of 10 bits, X_1, X_2, ..., X_10. This sequence is then processed by the Channel Coding block, which outputs a sequence of 32 bits, Z_0, Z_1, ..., Z_31. Finally, the Channel Coding block outputs are processed by the Physical Channel mapping block, which outputs the final result, PhCH.](ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg) + +``` + +graph TD + subgraph Inputs + direction TB + I1["X_tfc,1, ..., X_tfc,6"] + I2["X_rsn,1, X_rsn,2"] + I3["X_harq,1, X_harq,2"] + end + I1 --> M[Multiplexing] + I2 --> M + I3 --> M + M --> O1["X_1, X_2, ..., X_10"] + O1 --> CC[Channel Coding] + CC --> O2["Z_0, Z_1, ..., Z_31"] + O2 --> PCM[Physical Channel mapping] + PCM --> PhCH + +``` + +Figure 24A: Coding chain for E-UCCH. The diagram shows a vertical flow of data through three processing blocks: Multiplexing, Channel Coding, and Physical Channel mapping. Inputs to the Multiplexing block are three groups of bits: X\_tfc,1, ..., X\_tfc,6; X\_rsn,1, X\_rsn,2; and X\_harq,1, X\_harq,2. The output of the Multiplexing block is a sequence of 10 bits, X\_1, X\_2, ..., X\_10. This sequence is then processed by the Channel Coding block, which outputs a sequence of 32 bits, Z\_0, Z\_1, ..., Z\_31. Finally, the Channel Coding block outputs are processed by the Physical Channel mapping block, which outputs the final result, PhCH. + +Figure 24A: Coding chain for E-UCCH + +#### 4.9.2.1 E-UCCH information field mapping + +##### 4.9.2.1.1 Information field mapping of E-TFCI + +The E-TFCI is mapped such that $x_{tfc,1}$ corresponds to the MSB. + +#### 4.9.2.1.2 RSN information mapping + +To indicate the redundancy version (RV) of each HARQ transmission and to assist the Node B soft buffer management a two bit retransmission sequence number (RSN) is signalled from the UE to the Node B. The Node B can avoid soft buffer corruption by flushing the soft buffer associated to one HARQ process in case the last received RSN for that HARQ process is incompatible with the current one. + +The RSN is set by higher layers as described in [15]. For a given HARQ process, once the maximum RSN value of 3 is reached, the RSN alternates between the values of 2 and 3 for any further retransmissions. The RSN thus follows the pattern 0,1,2,3,2,3,2,3,2,3,.... + +The bits ( $x_{rsn,1}$ , $x_{rsn,2}$ ) of the RSN field are mapped such that $x_{rsn,1}$ corresponds to the MSB of the RSN and $x_{rsn,2}$ corresponds to the LSB of the RSN. + +The used RV is implicitly linked to the transmitted RSN, as such the Node-B is always able to determine the correct RV if the RSN information is correctly obtained. + +The constellation rearrangement parameter linkage with RSN is shown in Table 25A below + +**Table 25A: mapping between RSN and b parameters for CoRe** + +| RSN | $N_{sys} / N_{e,data,j} < 1/2$ | $1/2 \leq N_{sys} / N_{e,data,j}$ | +|-----|--------------------------------|-----------------------------------| +| | b | b | +| 0 | 0 | 0 | +| 1 | 2 | 3 | +| 2 | 3 | 0 | +| 3 | 1 | 1 | + +In addition to being associated with the value of RSN, the redundancy version (RV) of the E-DCH transmission is also associated with the coding rate of the E-DCH transmission according to Table 25B and Table 25C below. + +**Table 25B: Relation between RSN and E-DCH RV index for QPSK** + +| RSN | $N_{sys} / N_{e,data,j} < 1/2$ | $1/2 \leq N_{sys} / N_{e,data,j}$ | +|-----|--------------------------------|-----------------------------------| +| | E-DCH RV Index | E-DCH RV Index | +| 0 | 0 | 0 | +| 1 | 2 | 3 | +| 2 | 0 | 2 | +| 3 | 2 | 1 | + +**Table 25C: Relation between RSN and E-DCH RV index for 16QAM** + +| RSN | $N_{sys} / N_{e,data,j} < 1/2$ | $1/2 \leq N_{sys} / N_{e,data,j}$ | +|-----|--------------------------------|-----------------------------------| +| | E-DCH RV Index | E-DCH RV Index | +| 0 | 0 | 0 | +| 1 | 0 | 3 | +| 2 | 2 | 1 | +| 3 | 2 | 2 | + +The UE shall use either: + +- an RV index as indicated in Table 25A, 25B, 25C and according to the value of RSN +- or, if signalled by higher layers only E-DCH RV index 0 independently of the value of RSN. + +#### 4.9.2.1.3 HARQ information mapping + +The bits ( $x_{harq,1}$ , $x_{harq,2}$ ) of the HARQ field are mapped such that $x_{harq,1}$ corresponds to the MSB of the HARQ process ID and $x_{harq,2}$ corresponds to the LSB of the HARQ process ID. + +#### 4.9.2.2 Multiplexing for E-UCCH + +The transport block size information ( $x_{tbs,1}, \dots, x_{tbs,6}$ ), retransmission sequence number information ( $x_{rsn,1}, x_{rsn,2}$ ) and the HARQ process ID information ( $x_{harq,1}, x_{harq,2}$ ) are multiplexed together to give a sequence of bits $x_1, x_2, \dots, x_{10}$ where: + +$$x_k = x_{tbs,k} \quad k=1,2,3,4,5,6$$ + +$$x_k = x_{rsn,k-6} \quad k=7,8$$ + +$$x_k = x_{harq,k-8} \quad k=9,10$$ + +#### 4.9.2.3 Coding for E-UCCH + +The bits $x_1, x_2, \dots, x_{10}$ are coded to produce the bits $z_0, z_1, \dots, z_{31}$ using a (32,10) sub-code of the second order Reed-Muller code as defined in subclause 4.3.1.1. + +#### 4.9.2.4 Physical channel mapping for E-UCCH + +The E-UCCH is described in [7]. The sequence of bits $z_0, z_1, \dots, z_{31}$ output from the E-UCCH channel coding is mapped with E-DCH to E-PUCH of the E-DCH TTI configured to carry E-UCCH. + +### 4.10 Coding for E-AGCH + +The E-AGCHs on the different carriers are coded independently. + +For the 1.28 Mcps TDD, E-AGCH type 1 is used when the variable E\_DCH\_SPS\_STATUS=FALSE and the UE is not configured in MU-MIMO mode by higher layers for a UE (as defined in [12]). + +In this section, the terms "E-AGCH" and "E-AGCH type 1" are used interchangeably. + +The E-AGCH carries the following fields multiplexed into $w$ bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ . $w$ is within the range 14 to 28 bits (for the 3.84Mcps option) and 15 to 29 bits (for the 7.68Mcps option) and 23 to 26 bits (for the 1.28Mcps option) + +- Absolute grant (power) value ( $x_{pg,1}, x_{pg,2}, \dots, x_{pg,5}$ ) {5 bits}, +- Code resource related information ( $x_{c,1}, x_{c,2}, \dots, x_{c,N_c}$ ), { $N_c=5$ bits for the 1.28Mcps and 3.84Mcps options, $N_c=6$ bits for the 7.68Mcps option} +- Timeslot resource related information ( $x_{t,1}, x_{t,2}, \dots, x_{t,n_{TRRI}}$ ), { $n_{TRRI}$ bits} [ $n_{TRRI}=5$ for 1.28Mcps, and is configured by higher layers for 3.84Mcps and 7.68Mcps options] +- E-AGCH Cyclic Sequence Number (ECSN) ( $x_{e,1}, x_{e,2}, x_{e,3}$ ) (3 bits) +- Resource duration indicator (3 bits if present) ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) – [the presence of this field is configured by higher layers] +- E-HICH Indicator ( $x_{EI,1}, x_{EI,2}$ ) (2 bits) (for 1.28Mcps TDD only) +- E-UCCH Number Indicator ( $x_{ENI,1}, x_{ENI,2}, x_{ENI,3}$ ) (3 bits) (for 1.28Mcps TDD only) + +Figure 25 illustrates the overall coding chain for the E-AGCH on one carrier. + +![Flowchart of TrCH processing of E-AGCH. The process starts with five input data streams: x_{pg,1}, x_{pg,2}, x_{pg,3}, x_{pg,4}, and x_{pg,5} entering a 'Multiplexing' block. The output of 'Multiplexing' is a single stream entering a 'CRC attachment' block. An external input x_{id,1}...x_{id,16} is also added at this stage. The output of 'CRC attachment' enters a 'Channel Coding' block. The output of 'Channel Coding' enters a 'Rate Matching' block. The output of 'Rate Matching' enters an 'Interleaving' block. The output of 'Interleaving' enters a 'Physical Channel Segmentation' block. The output of 'Physical Channel Segmentation' enters a 'Physical Channel Mapping' block. The final output of the process is E-AGCH.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +graph TD + subgraph Inputs + direction LR + x1["x_{pg,1}"] + x2["x_{pg,2}"] + x3["x_{pg,3}"] + x4["x_{pg,4}"] + x5["x_{pg,5}"] + end + x1 --> M[Multiplexing] + x2 --> M + x3 --> M + x4 --> M + x5 --> M + M --> x_p["x_{p,1}...x_{p,5}"] + x_p --> CA[CRC attachment] + x_id["x_{id,1}...x_{id,16}"] --> CA + CA --> x_a["x_{a,1}...x_{a,21}"] + x_a --> CC[Channel Coding] + CC --> x_c["x_{c,1}...x_{c,63}"] + x_c --> RM[Rate Matching] + RM --> x_r["x_{r,1}...x_{r,R}"] + x_r --> I[Interleaving] + I --> x_i["x_{i,1}...x_{i,R}"] + x_i --> PCS[Physical Channel Segmentation] + PCS --> x_s["x_{s,1}...x_{s,R}"] + x_s --> PCM[Physical Channel Mapping] + PCM --> EAGCH[E-AGCH] + +``` + +Flowchart of TrCH processing of E-AGCH. The process starts with five input data streams: x\_{pg,1}, x\_{pg,2}, x\_{pg,3}, x\_{pg,4}, and x\_{pg,5} entering a 'Multiplexing' block. The output of 'Multiplexing' is a single stream entering a 'CRC attachment' block. An external input x\_{id,1}...x\_{id,16} is also added at this stage. The output of 'CRC attachment' enters a 'Channel Coding' block. The output of 'Channel Coding' enters a 'Rate Matching' block. The output of 'Rate Matching' enters an 'Interleaving' block. The output of 'Interleaving' enters a 'Physical Channel Segmentation' block. The output of 'Physical Channel Segmentation' enters a 'Physical Channel Mapping' block. The final output of the process is E-AGCH. + +Figure 25 – TrCH processing of E-AGCH + +## 4.10.1 Information Field Mapping + +### 4.10.1.1 Mapping of the Absolute Grant (Power) Value + +The absolute grant (power) value ( $x_{pg,1}, x_{pg,2}, \dots, x_{pg,5}$ ) is represented by 5 bits and corresponds to a dB value as specified in table 26 for 3.84Mcps and 7.68 Mcps TDD and in table 26A for 1.28Mcps TDD below. The values are mapped such that $x_{pg,1}$ corresponds to the MSB of the index. + +**Table 26: Mapping of Absolute Grant Value (for 3.84Mcps and 7.68 Mcps TDD)** + +| Absolute Grant Value | Index | +|----------------------|-------| +| 31 dB | 31 | +| 30 dB | 30 | +| 29 dB | 29 | +| 28 dB | 28 | +| 27 dB | 27 | +| 26 dB | 26 | +| 25 dB | 25 | +| 24 dB | 24 | +| 23 dB | 23 | +| 22 dB | 22 | +| 21 dB | 21 | +| 20 dB | 20 | +| 19 dB | 19 | +| 18 dB | 18 | +| 17 dB | 17 | +| 16 dB | 16 | +| 15 dB | 15 | +| 14 dB | 14 | +| 13 dB | 13 | +| 12 dB | 12 | +| 11 dB | 11 | +| 10 dB | 10 | +| 9 dB | 9 | +| 8 dB | 8 | +| 7 dB | 7 | +| 6 dB | 6 | +| 5 dB | 5 | +| 4 dB | 4 | +| 3 dB | 3 | +| 2 dB | 2 | +| 1 dB | 1 | +| 0 dB | 0 | + +**Table 26A: Mapping of Absolute Grant Value (for 1.28Mcps TDD)** + +| Absolute Grant Value | Index | +|----------------------|-------| +| 19 dB | 31 | +| 18 dB | 30 | +| 17 dB | 29 | +| 16 dB | 28 | +| 15 dB | 27 | +| 14 dB | 26 | +| 13 dB | 25 | +| 12 dB | 24 | +| 11 dB | 23 | +| 10 dB | 22 | +| 9 dB | 21 | +| 8 dB | 20 | +| 7 dB | 19 | +| 6 dB | 18 | +| 5 dB | 17 | +| 4 dB | 16 | +| 3 dB | 15 | +| 2 dB | 14 | +| 1 dB | 13 | +| 0 dB | 12 | +| -1 dB | 11 | +| -2 dB | 10 | +| -3 dB | 9 | +| -4 dB | 8 | +| -5 dB | 7 | +| -6 dB | 6 | +| -7 dB | 5 | +| -8 dB | 4 | +| -9 dB | 3 | +| -10 dB | 2 | +| -11 dB | 1 | +| -12 dB | 0 | + +#### 4.10.1.2 Mapping of the Code Resource Related Information + +The code resource related information ( $x_{c,1}, x_{c,2}, \dots, x_{c,N_c}$ ) indicates which node on the OVSF code tree has been allocated and is represented by $N_c$ bits where $N_c=5$ for 1.28Mcps and 3.84Mcps and $N_c=6$ for 7.68Mcps. The mapping between the allocated OVSF and the enumerated node 0...30 (for 1.28Mcps and 3.84Mcps) and 0...62 (for 7.68Mcps) on the OVSF code tree is as given in table 27 below, in which channelisation code "i" with spreading factor "Q" is denoted as $C_i^{(Q)}$ . $x_{c,1}$ corresponds to the MSB of the enumerated node. The right-most column of table 27 is only applicable for the 7.68Mcps option. + +**Table 27 – Channelisation code mapping** + +| | | | | | | +|-----------------|-----------------|-----------------|------------------|-------------------|----------------------| +| $C_1^{(1)}$ [0] | $C_1^{(2)}$ [1] | $C_1^{(4)}$ [3] | $C_1^{(8)}$ [7] | $C_1^{(16)}$ [15] | $C_1^{(32)}$ [31] | +| | | | | $C_2^{(16)}$ [16] | $C_2^{(32)}$ [32] | +| | | | $C_2^{(8)}$ [8] | $C_3^{(16)}$ [17] | $C_3^{(32)}$ [33] | +| | | | | $C_4^{(16)}$ [18] | $C_4^{(32)}$ [34] | +| | | $C_2^{(4)}$ [4] | $C_3^{(8)}$ [9] | $C_5^{(16)}$ [19] | $C_5^{(32)}$ [35] | +| | | | | $C_6^{(16)}$ [20] | $C_6^{(32)}$ [36] | +| | | | $C_4^{(8)}$ [10] | $C_7^{(16)}$ [21] | $C_7^{(32)}$ [37] | +| | | | | | $C_8^{(32)}$ [38] | +| | | | | | $C_9^{(32)}$ [39] | +| | | | | | $C_{10}^{(32)}$ [40] | +| | | | | | $C_{11}^{(32)}$ [41] | +| | | | | | $C_{12}^{(32)}$ [42] | +| | | | | | $C_{13}^{(32)}$ [43] | +| | | | | | $C_{14}^{(32)}$ [44] | + +| | | | | | +|--|-----------------|------------------|----------------------|----------------------| +| | | | $C_8^{(16)}$ [22] | $C_{15}^{(32)}$ [45] | +| | | | | $C_{16}^{(32)}$ [46] | +| | | $C_5^{(8)}$ [11] | $C_9^{(16)}$ [23] | $C_{17}^{(32)}$ [47] | +| | | | | $C_{18}^{(32)}$ [48] | +| | | $C_3^{(4)}$ [5] | $C_{10}^{(16)}$ [24] | $C_{19}^{(32)}$ [49] | +| | | | | $C_{20}^{(32)}$ [50] | +| | | $C_6^{(8)}$ [12] | $C_{11}^{(16)}$ [25] | $C_{21}^{(32)}$ [51] | +| | | | | $C_{22}^{(32)}$ [52] | +| | $C_2^{(2)}$ [2] | | $C_{12}^{(16)}$ [26] | $C_{23}^{(32)}$ [53] | +| | | | | $C_{24}^{(32)}$ [54] | +| | | $C_7^{(8)}$ [13] | $C_{13}^{(16)}$ [27] | $C_{25}^{(32)}$ [55] | +| | | | | $C_{26}^{(32)}$ [56] | +| | | $C_4^{(4)}$ [6] | $C_{14}^{(16)}$ [28] | $C_{27}^{(32)}$ [57] | +| | | | | $C_{28}^{(32)}$ [58] | +| | | $C_8^{(8)}$ [14] | $C_{15}^{(16)}$ [29] | $C_{29}^{(32)}$ [59] | +| | | | | $C_{30}^{(32)}$ [60] | +| | | | $C_{16}^{(16)}$ [30] | $C_{31}^{(32)}$ [61] | +| | | | | $C_{32}^{(32)}$ [62] | + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, the OVSF code of all the allocated timeslots is indicated by Code Resource Related Information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot closest to the timeslot in which HS-SICH and/or UL DPCH is allocated among all the uplink timeslot scheduled to the UE. The OVSF code of the specific timeslot is indicated by Code Resource Related Information field. The OVSF code of other scheduled timeslots is predefined, i.e. node 0. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, the OVSF code in the specific timeslot is indicated by Code Resource Related Information field. The OVSF code of other scheduled timeslots is predefined, i.e. node 0. + +#### 4.10.1.3 Mapping of the Timeslot Resource Related Information + +For 3.84Mcps and 7.68Mcps options, the timeslot resource related information ( $x_{t,1}, x_{t,2}, \dots, x_{t,n_{TRRI}}$ ) is a bitmap of length $n_{TRRI}$ indicating which of the timeslots configured for E-DCH use by higher layers have been allocated. The length of the field ( $n_{TRRI}$ ) is configured by higher layers up to a maximum of 12 bits. The bitmap is arranged such that the corresponding timeslots are in ascending numerical order, with $x_{t,1}$ corresponding to LSB and lowest-numbered timeslot configured for E-DCH use. + +For 1.28Mcps option, the timeslot resource related information ( $x_{t,1}, x_{t,2}, \dots, x_{t,n_{TRRI}}$ ) is also a bitmap of length 5 indicating the allocation for E-DCH resources from TS1 to TS5. If the bit is set (i.e. equal to 1), then the corresponding timeslot shall be used for E-DCH resources. The bitmap is arranged such that the corresponding timeslots are in ascending numerical order, with $x_{t,1}$ corresponding to MSB. + +#### 4.10.1.4 Mapping of the E-AGCH Cyclic Sequence Number (ECSN) + +The E-AGCH cyclic sequence number is mapped such that $x_{e,1}$ corresponds to the MSB and $x_{e,3}$ to the LSB. + +#### 4.10.1.5 Mapping of the Resource Duration Indicator + +The resource duration indicator ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) is mapped such that $x_{r,1}$ corresponds to the MSB of the resource duration index described in [15]. + +#### 4.10.1.6 Mapping of the E-HICH Indicator (1.28Mcps option only) + +The E-HICH indicator consists of 2 bits used to indicate the UE which E-HICH will be used to convey the acknowledgement indicator in the following schedule period for 1.28Mcps TDD only. The bits ( $x_{EI,1}, x_{EI,2}$ ) are mapped such that $x_{EI,1}$ corresponds to the MSB and $x_{EI,2}$ to the LSB. + +#### 4.10.1.7 Mapping of the E-UCCH Number Indicator (1.28Mcps option only) + +The E-UCCH number indicator is composed of 3bits which is used to calculate the number of E-UCCH for 1.28Mcps TDD only. The bits ( $x_{ENI,1}, x_{ENI,2}, x_{ENI,3}$ ) are mapped such that $x_{ENI,1}$ corresponds to the MSB and $x_{ENI,3}$ to the LSB. The number of the used E-UCCH is equal to ENI+1. + +#### 4.10.2 Field Multiplexing + +The absolute grant (power) value, code resource related information, timeslot resource related information, resource duration indicator (if present), ECSN, E-HICH indicator (for 1.28Mcps TDD only) and E-UCCH number indicator (for 1.28Mcps TDD only) are multiplexed together to give a sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ where: + +For the 1.28Mcps option: + +$$x_{ag,k} = x_{pg,k} \quad k=1, 2, \dots, 5$$ + +$$x_{ag,k} = x_{c,k-5} \quad k=6, 7, \dots, 10$$ + +$$x_{ag,k} = x_{t,k-10} \quad k=11, \dots, 15$$ + +$$x_{ag,k} = x_{e,k-15} \quad k=16, 17, 18$$ + +if resource duration indicator (RDI) present: + +$$x_{ag,k} = x_{r,k-18} \quad k=19, 20, 21$$ + +$$x_{ag,k} = x_{EI,k-21} \quad k=22, 23$$ + +$$x_{ag,k} = x_{ENI,k-23} \quad k=24, 25, 26$$ + +or if resource duration indicator (RDI) does not present: + +$$x_{ag,k} = x_{EI,k-18} \quad k=19, 20$$ + +$$x_{ag,k} = x_{ENI,k-20} \quad k=21, 22, 23$$ + +For the 3.84Mcps option: + +$$x_{ag,k} = x_{pg,k} \quad k=1, 2, \dots, 5$$ + +$$x_{ag,k} = x_{c,k-5} \quad k=6, 7, \dots, 10$$ + +$$x_{ag,k} = x_{t,k-10} \quad k=11, \dots, 10+n_{TRRI}$$ + +$$x_{ag,k} = x_{e,k-10-n_{TRRI}} \quad k=11+n_{TRRI}, \dots, 13+n_{TRRI}$$ + +$$x_{ag,k} = x_{r,k-13-n_{TRRI}} \quad k=14+n_{TRRI}, \dots, 16+n_{TRRI} \text{ \{if resource duration indicator present\}}$$ + +and for the 7.68Mcps option: + +$$x_{ag,k} = x_{pg,k} \quad k=1, 2, \dots, 5$$ + +$$x_{ag,k} = x_{c,k-5} \quad k=6, 7, \dots, 11$$ + +$$x_{ag,k} = x_{t,k-11} \quad k=12, \dots, 11+n_{TRRI}$$ + +$$x_{ag,k} = x_{e,k-11-n_{TRRI}} \quad k=12+n_{TRRI}, \dots, 14+n_{TRRI}$$ + +$$x_{ag,k} = x_{r,k-14-n_{TRRI}} \quad k=15+n_{TRRI}, \dots, 17+n_{TRRI} \text{ \{if resource duration indicator present\}}$$ + +#### 4.10.3 CRC attachment + +The E-RNTI ( $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ ) is the E-DCH Radio Network Identifier defined in [12]. It is mapped such that $x_{id,1}$ corresponds to the MSB. + +From the sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ a 16 bit CRC is calculated according to section 4.2.1.1. This gives the sequence of bits $c_1, c_2, \dots, c_{16}$ where: + +$$k=1,2,\dots,16$$ + +This sequence of bits is then masked with $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ and appended to the sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ to form the sequence of bits $y_1, y_2, \dots, y_{w+16}$ where + +$$y_i = x_{ag,i} \quad i=1,2,\dots,w$$ + +$$y_i = (c_{i-w} + x_{id,i-w}) \bmod 2 \quad i=w+1, \dots, w+16$$ + +#### 4.10.4 Channel Coding + +1/3 rate convolutional channel coding is applied to the sequence $y_1, y_2, \dots, y_{w+16}$ in accordance with section 4.2.3.1, resulting in the sequence of bits $z_1, z_2, \dots, z_{3(w+24)}$ . + +#### 4.10.5 Rate Matching + +Rate matching is applied to the input sequence $z_1, z_2, \dots, z_{3(w+24)}$ to obtain the output sequence $r_1, r_2, \dots, r_U$ , where $U = 242$ for burst type 1 and $U = 274$ for burst type 2 for 3.84Mcps and 7.68Mcps options while $U=172$ for 1.28Mcps option. + +#### 4.10.6 Interleaving + +Interleaving is performed as per section 4.2.11.1 (frame-related 2nd interleaving). + +#### 4.10.7 Physical Channel Segmentation + +Physical channel segmentation is performed as per section 4.2.10. For 1.28Mcps TDD, the E-AGCH consists of two physical channels E-AGCH1 and E-AGCH2, whereas for 3.84Mcps and 7.68Mcps TDD the E-AGCH only uses one physical channel, see[7].Note that physical channel segmentation is transparent when only one physical channel exists + +#### 4.10.8 Physical Channel Mapping + +Physical channel mapping is performed as per section 4.2.12. + +#### 4.10A Coding for E-AGCH type 2 (1.28Mcps TDD only) + +For the 1.28 Mcps TDD, E-AGCH type 2 is used when any of the following conditions is met: + +- the variable E\_DCH\_SPS\_STATUS =TRUE for a UE (as defined in [12]). +- the UE is configured in MU-MIMO mode. + +The E-AGCH type 2 carries the following fields multiplexed into $w$ bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ and $w$ is 30 bits. + +- Absolute grant (power) value $(x_{pg,1}, x_{pg,2}, \dots, x_{pg,5})$ {5 bits} +- Code resource related information $(x_{c,1}, x_{c,2}, \dots, x_{c,N_c})$ , { $N_c=4$ bits } +- Timeslot resource related information $(x_{t,1}, x_{t,2}, \dots, x_{t,n_{TRRI}})$ , { $n_{TRRI}=5$ bits} +- E-AGCH Cyclic Sequence Number (ECSN) $(x_{e,1}, x_{e,2}, x_{e,3})$ (3 bits) +- Field flag $(x_{flag,1}, x_{flag,2})$ {2 bits} +- Special information 1 $(x_{info1,1}, x_{info1,2})$ {2 bits} +- Special information 2 $(x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5})$ {5 bits} +- E-UCCH Number Indicator $(x_{ENI,1}, x_{ENI,2}, x_{ENI,3})$ {3 bits} +- Reserved $(x_{res,1})$ {1 bit} + +For an E-AGCH order, + +- $X_{pg,1}, X_{pg,2}, X_{pg,3}, X_{pg,4}, X_{pg,5}, X_{c,1}, X_{c,2}, X_{c,3}, X_{c,N_c}$ are reserved +- $X_{t,1}, X_{t,2}, \dots, X_{t,n_{TRRI}}$ shall be set to '00000' +- $X_{e,1}, X_{e,2}, X_{e,3}$ shall be set to $X_{odt,1}, X_{odt,2}, X_{odt,3}$ +- $X_{flag,1}, X_{flag,2}, X_{info1,1}, X_{info1,2}, X_{info2,1}, X_{info2,2}, X_{info2,3}, X_{info2,4}, X_{info2,5}, X_{ENL1}, X_{ENL2}, X_{ENL3}, X_{res,1}$ are reserved + +where $X_{odt,1}, X_{odt,2}, X_{odt,3}$ are defined in subclause 4.10B. + +Figure 25A illustrates the overall coding chain for the E-AGCH type 2. + +![A large empty rectangular box, likely a placeholder for Figure 25A.](aa5b4fe5ea9a65d15789baa3e8dc1565_img.jpg) + +A large empty rectangular box, likely a placeholder for Figure 25A. + +**Figure 25A– TrCH processing of E-AGCH type2** + +#### 4.10A.1 E-AGCH type 2 Information Field Mapping + +##### 4.10A.1.1 Mapping of the Absolute Grant (Power) Value + +The mapping of the absolute grant (power) value ( $x_{pg,1}, x_{pg,2}, \dots, x_{pg,5}$ ) is performed as per section 4.10.1.1. + +##### 4.10A.1.2 Mapping of the Code Resource Related Information + +The code resource related information ( $x_{c,1}, x_{c,2}, \dots, x_{c,N_c}$ ) indicates which node on the OVSF code tree has been allocated and is represented by $N_c$ bits where $N_c=4$ . The mapping between the allocated OVSF and the enumerated node 0...14 on the OVSF code tree is as given in table 27, in which channelisation code " $i$ " with spreading factor " $Q$ " is denoted as $C_i^{(Q)}$ . $x_{c,1}$ corresponds to the MSB of the enumerated node. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is FALSE, the OVSF code of all the allocated timeslots is indicated by Code Resource Related Information field. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot closest to the timeslot in which HS-SICH and/or UL DPCH is allocated among all the uplink timeslot scheduled to the UE. The OVSF code of the specific timeslot is indicated by Code Resource Related Information field. The OVSF code of other scheduled timeslots is predefined, i.e. node 0. + +If NON\_RECTANGULAR\_RESOURCE\_ALLOCATION\_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, the OVSF code in the specific timeslot is indicated by Code Resource Related Information field. The OVSF code of other scheduled timeslots is predefined, i.e. node 0. + +#### 4.10A.1.3 Mapping of the Timeslot Resource Related Information + +The mapping of the timeslot resource related information ( $x_{t,1}, x_{t,2}, \dots, x_{t,n_{TRR1}}$ ) is performed as per section 4.10.1.3. + +#### 4.10A.1.4 Mapping of the E-AGCH Cyclic Sequence Number (ECSN) + +The mapping of E-AGCH cyclic sequence number ( $x_{e,1}, x_{e,2}, x_{e,3}$ ) is performed as per section 4.10.1.4. + +#### 4.10A.1.5 Mapping of the Field Flag + +The field flag is used to distinguish the mapping of special information 1 and special information 2. The bits ( $x_{flag,1}, x_{flag,2}$ ) are mapped such that $x_{flag,1}$ corresponds to the MSB and $x_{flag,2}$ to the LSB. + +If $x_{flag,1}, x_{flag,2} = '00'$ , the special information 1 ( $x_{info1,1}, x_{info1,2}$ ) are comprised of the E-HICH indicator ( $x_{EI,1}, x_{EI,2}$ ) and the special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) are comprised of the resource duration indicator ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) and $x_{info2,4}, x_{info2,5}$ are reserved. + +If $x_{flag,1}, x_{flag,2} = '01'$ , the special information 1 ( $x_{info1,1}, x_{info1,2}$ ) are comprised of the resource repetition pattern index ( $x_{rrpi,1}, x_{rrpi,2}$ ) and the special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) are reserved. + +If $x_{flag,1}, x_{flag,2} = '10'$ , the special default midamble allocation is used. The special information 1 ( $x_{info1,1}, x_{info1,2}$ ) are comprised of the E-HICH indicator ( $x_{EI,1}, x_{EI,2}$ ) and the special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) are comprised of the resource duration indicator ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) and the special default midamble pattern indicator ( $x_{mpi,1}, x_{mpi,2}$ ). + +$x_{flag,1}, x_{flag,2} = '11'$ is reserved. + +#### 4.10A.1.6 Mapping of the Special Information 1 + +The special information 1 ( $x_{info1,1}, x_{info1,2}$ ) is mapped such that $x_{info1,1}$ corresponds to the MSB and $x_{info1,2}$ to the LSB. + +If the special information 1 are comprised of the E-HICH indicator ( $x_{EI,1}, x_{EI,2}$ ), then $x_{info1,1} = x_{EI,1}$ and $x_{info1,2} = x_{EI,2}$ . And the mapping of the E-HICH indicator is performed as per section 4.10.1.6. + +If the special information 1 are comprised of the resource repetition pattern index ( $x_{rrpi,1}, x_{rrpi,2}$ ), then $x_{info1,1} = x_{rrpi,1}$ and $x_{info1,2} = x_{rrpi,2}$ . The resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ is the unsigned binary representation of a reference to one of repetition patterns of the assigned semi-persistent E-PUCH resources configured by higher layers. The resource repetition pattern index $x_{rrpi,1}, x_{rrpi,2}$ are mapped such that $x_{rrpi,1}$ corresponds to the MSB and $x_{rrpi,2}$ to the LSB. And if $x_{rrpi,1}, x_{rrpi,2} = '00'$ , one subframe E-PUCH resource is assigned. + +| $x_{rrpi,1}, x_{rrpi,2}$ | Resource repetition pattern index as signalled in the variable E_DCH_SPS_PARAMS[12] | +|--------------------------|-------------------------------------------------------------------------------------| +| '01' | 1 st entry | +| '10' | 2 nd entry | +| '11' | 3 rd entry | + +#### 4.10A.1.7 Mapping of the Special Information 2 + +The special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) is mapped such that $x_{info2,1}$ corresponds to the MSB and $x_{info2,5}$ to the LSB. + +If the special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) are comprised of the resource duration indicator ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) and $x_{info2,4}, x_{info2,5}$ are reserved. Then $x_{info2,1} = x_{r,1}, x_{info2,2} = x_{r,2}$ and $x_{info2,3} = x_{r,3}$ . + +The mapping of the resource duration indicator is performed as per section 4.10.1.5. + +If the special information 2 ( $x_{info2,1}, x_{info2,2}, x_{info2,3}, x_{info2,4}, x_{info2,5}$ ) are comprised of the resource duration indicator ( $x_{r,1}, x_{r,2}, x_{r,3}$ ) and the special default midamble pattern indicator ( $x_{mpi,1}, x_{mpi,2}$ ), then $x_{info2,1} = x_{r,1}, x_{info2,2} = x_{r,2}, x_{info2,3} = x_{r,3}, x_{info2,4} = x_{mpi,1}$ and $x_{info2,5} = x_{mpi,2}$ . The mapping in Table 25A below applies. + +**Table 25A: Special default midamble pattern mapping** + +| Special default
Midamble
pattern | $x_{mpi,1}$ | $x_{mpi,2}$ | +|-------------------------------------------------|-------------|-------------| +| pattern 1A | 0 | 0 | +| pattern 1B | 0 | 1 | +| pattern 2A | 1 | 0 | +| pattern 2B | 1 | 1 | + +#### 4.10A.1.8 Mapping of the E-UCCH Number Indicator + +The mapping of E-UCCH number indicator ( $x_{ENI,1}, x_{ENI,2}, x_{ENI,3}$ ) is performed as per section of 4.10.1.7. + +### 4.10A.2 Field Multiplexing of E-AGCH type 2 + +The absolute grant (power) value, code resource related information, timeslot resource related information, ECSN, field flag, special information 1, special information 2 and E-UCCH number indicator are multiplexed together to give a sequence of bits $x_{ag,1}, x_{ag,2}, \dots, x_{ag,w}$ where: + +$$x_{ag,k} = x_{pg,k} \quad k=1, 2, \dots, 5$$ + +$$x_{ag,k} = x_{c,k-5} \quad k=6, 7, \dots, 9$$ + +$$x_{ag,k} = x_{t,k-9} \quad k=10, 11, \dots, 14$$ + +$$x_{ag,k} = x_{e,k-14} \quad k=15, 16, 17$$ + +$$x_{ag,k} = x_{flag,k-17} \quad k=18, 19$$ + +$$x_{ag,k} = x_{info1,k-19} \quad k=20, 21$$ + +$$x_{ag,k} = x_{info2,k-21} \quad k=22, 23, \dots, 26$$ + +$$x_{ag,k} = x_{ENI,k-26} \quad k=27, 28, 29$$ + +$$x_{ag,k} = x_{res,k-29} \quad k=30$$ + +### 4.10A.3 CRC attachment for E-AGCH type 2 + +The E-RNTI ( $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ ) is the E-DCH Radio Network Identifier defined in [12]. It is mapped such that $x_{id,1}$ corresponds to the MSB. + +The sequence of bits $y_1, y_2, \dots, y_{w+16}$ , is calculated according to section 4.10.3. + +### 4.10A.4 Channel Coding for E-AGCH type 2 + +Channel coding is performed as per section 4.10.4. + +## 4.10A.5 Rate Matching for E-AGCH type 2 + +Rate matching is performed as per section 4.10.5. + +## 4.10A.6 Interleaving for E-AGCH type 2 + +Interleaving is performed as per section 4.10.6. + +## 4.10A.7 Physical Channel Segmentation for E-AGCH type 2 + +Physical channel segmentation is performed as per section 4.10.7. + +## 4.10A.8 Physical Channel Mapping for E-AGCH type 2 + +Physical channel mapping is performed as per section 4.10.8. + +## 4.10B Coding for E-AGCH orders + +E-AGCH orders are commands sent to the UE using E-AGCH. No E-PUCH resources grants are associated with E-AGCH orders. + +The following information is transmitted by means of the E-AGCH order physical channel. + +- **Order type (3 bits):** $x_{odt,1}, x_{odt,2}, x_{odt,3}$ +- **UE identity (16 bits):** $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ + +The coding for E-AGCH orders is specified in subclause 4.10A. + +### 4.10B.1 E-AGCH orders information field mapping + +#### 4.10B.1.1 Order type mapping + +If $x_{odt,1}, x_{odt,2}, x_{odt,3} = '000'$ , then the E-AGCH order is an order to release the allocated semi-persistent E-PUCH resources when UE is in CELL\_DCH state. + +#### 4.10B.1.2 UE identity mapping + +The E-RNTI ( $x_{id,1}, x_{id,2}, \dots, x_{id,16}$ ) is the E-DCH Radio Network Identifier defined in [12]. It is mapped such that $x_{id,1}$ corresponds to the MSB. + +## 4.11 Coding for E-HICH ACK/NACK + +### 4.11.1 Coding for E-HICH ACK/NACK for the 3.84Mcps and 7.68Mcps options + +#### 4.11.1.1 Overview + +The ACK/NACK is transmitted on the E-HICH as described in [7]. + +The value of a binary HARQ acknowledgement indicator for user $h$ is denoted " $a_h$ " and may assume the value 0 or 1. The value of the indicator is mapped as shown in table 28. + +**Table 28 – Mapping of HARQ acknowledgement indicator** + +| Command | HARQ acknowledgement indicator value
( $a_h$ ) | +|---------|---------------------------------------------------| +| NACK | 0 | +| ACK | 1 | + +A HARQ acknowledgement indicator is mapped to one of 240 signature sequences of length 240 bits and represented by the bit sequence $b_{h,0}, b_{h,1}, \dots, b_{h,239}$ for the $h^{th}$ acknowledgement indicator. The signature sequence number "r" is selected as described in [7]. + +The signature sequence $b_{h,0}, b_{h,1}, \dots, b_{h,239}$ is constructed via coding of $a_h$ followed by bit scrambling. Spare bits are inserted during the physical channel mapping stage to produce the output sequence $d_{h,0}, d_{h,1}, \dots, d_{h,U}$ . + +#### 4.11.1.2 Coding of the HARQ acknowledgement indicator + +Bit $a_h$ is used to form the sequence $s_{2,v}$ ( $v=0,1,\dots,239$ ) via a two-stage serialised binary spreading process as shown in figure 26. + +![Figure 26: Block diagram of the two-stage serialised binary spreading process. An HARQ Acknowledgement Indicator (1 bit) is input to the 1st Spreading stage (x20), which also receives a primary code C1,i,k (length 20). The output of the 1st stage (20 bits) is input to the 2nd Spreading stage (x12), which also receives a secondary code C2,j,m (length 12). The final output is 240 bits.](c701a84b904fedcdb0316835eafbd39f_img.jpg) + +``` + +graph LR + Input[HARQ Acknowledgement Indicator] -- "1 bit" --> S1[1st Spreading x20] + C1["primary code C1,i,k (length 20)"] --> S1 + S1 -- "20 bits" --> S2[2nd Spreading x12] + C2["secondary code C2,j,m (length 12)"] --> S2 + S2 -- "240 bits" --> Output[ ] + style Output fill:none,stroke:none + +``` + +Figure 26: Block diagram of the two-stage serialised binary spreading process. An HARQ Acknowledgement Indicator (1 bit) is input to the 1st Spreading stage (x20), which also receives a primary code C1,i,k (length 20). The output of the 1st stage (20 bits) is input to the 2nd Spreading stage (x12), which also receives a secondary code C2,j,m (length 12). The final output is 240 bits. + +Figure 26 + +The output of the first spreading stage is $s_{1,k}$ , where $k=0, 1, 2, \dots, 19$ . + +The output of the second spreading stage is $s_{2,v}$ , where $v=0, 1, \dots, 239$ and where $s_{2,v} = s_{1,k} \cdot c_{2,j,m}$ . + +The binary sequences selected for the first ( $C_{1,i,k}$ ) and second ( $C_{2,j,m}$ ) spreading operations are derived as a function of the HARQ acknowledgement sequence number $r$ (see [7]) such that: + +The first orthogonal sequence set ( $C_{1,i,k}$ ) is given by table 29 and the second orthogonal sequence set ( $C_{2,j,m}$ ) is given by table 30. + +Table 29 – Primary code sequences for HARQ acknowledgement indicator + +| k | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | +|--------------|---|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----| +| $C_{1,0,k}$ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| $C_{1,1,k}$ | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| $C_{1,2,k}$ | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| $C_{1,3,k}$ | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | +| $C_{1,4,k}$ | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | +| $C_{1,5,k}$ | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | +| $C_{1,6,k}$ | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | +| $C_{1,7,k}$ | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | +| $C_{1,8,k}$ | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | +| $C_{1,9,k}$ | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| $C_{1,10,k}$ | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | +| $C_{1,11,k}$ | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | +| $C_{1,12,k}$ | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | +| $C_{1,13,k}$ | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | +| $C_{1,14,k}$ | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | + +| | | | | | | | | | | | | | | | | | | | | | +|---------------------------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| C1,15,k | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| C1,16,k | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | +| C1,17,k | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | +| C1,18,k | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| C1,19,k | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | + +**Table 30 – Secondary code sequences for HARQ acknowledgement indicator** + +| m | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | +|---------------------------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------|-----------| +| C2,0,m | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| C2,1,m | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | +| C2,2,m | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | +| C2,3,m | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | +| C2,4,m | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | +| C2,5,m | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | +| C2,6,m | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | +| C2,7,m | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | +| C2,8,m | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | +| C2,9,m | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| C2,10,m | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | +| C2,11,m | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | + +#### 4.11.1.3 Bit scrambling of the E-HICH + +The bit sequence $b_{h,0}, b_{h,1}, \dots, b_{h,239}$ is formed by applying bit scrambling (as defined in subclause 4.2.9) to the sequence $s_{2,v}$ . + +#### 4.11.1.4 Physical channel mapping of the E-HICH + +The bit sequence $b_{h,0}, b_{h,1}, \dots, b_{h,239}$ is segmented into two halves, $b_{h,0}, \dots, b_{h,119}$ , and $b_{h,120}, \dots, b_{h,239}$ . A sequence of U spare bits $z_u$ ( $u=0 \dots U-1$ ) are inserted between the first and second half of the sequence to form: + +$$d_h = \{b_{h,0}, b_{h,1}, \dots, b_{h,119}, z_0, z_1, \dots, z_{U-1}, b_{h,120}, b_{h,121}, \dots, b_{h,239}\}$$ + +U is equal to 4 or 36 dependant on the burst type (see [7]). The spare bit sequence $z_u$ is not defined. + +### 4.11.2 Coding for E-HICH for the 1.28Mcps option only + +#### 4.11.2.1 Overview + +The scheduled and non-Scheduled transmissions on different E-HICHs are described in [7]. The acknowledgement indicators for the E-DCH semi-persistent scheduling operation can be transmitted on the same E-HICH carrying indicators for scheduled traffic or the E-HICH carrying indicators for non-scheduled traffic as described in [7]. + +For 1.28Mcps TDD multi-carrier E-DCH transmission, the acknowledgement indicators for the E-PUCH on one carrier is associated with the E-HICHs on the same carrier. The E-HICHs on the different carriers are coded independently. + +The value of a binary HARQ acknowledgement indicator for user $h$ is denoted " $a_h$ " and may assume the value 0 or 1. The value of the indicator is mapped as same as that of 3.84Mcps shown in subclause 4.11.1.1. + +Construction of the bit sequence for the $h^{\text{th}}$ acknowledgement indicator is achieved via a spreading process using an orthogonal sequence which is the row of an orthogonal matrix of order 80. This orthogonal matrix ( $C_{80}$ ) is Kronecker tensor product of one Hadamard matrix of order 20 ( $C_{20}$ ) and another Hadamard matrix of order 4 ( $C_4$ ), + +$$C_{80} = C_{20} \otimes C_4$$ + +$\otimes$ is Kronecker tensor product. (note: Kronecker product is not commutative, i.e. $A \otimes B \neq B \otimes A$ ). The element "0" in Hadamard $C_{20}$ and $C_4$ shall be replaced by "-1" before the Kronecker tensor product operation. And after the operation the elements "-1" in $C_{80}$ should be converted back into "0". + +These two Hadamard matrices are given by table 31 and table 32. + +**Table 31: Hadamard matrix of order 4** + +| | | | | | +|-------------|---|---|---|---| +| m | 0 | 1 | 2 | 3 | +| $C_{4,0,m}$ | 1 | 1 | 1 | 1 | +| $C_{4,1,m}$ | 1 | 0 | 1 | 0 | +| $C_{4,2,m}$ | 1 | 1 | 0 | 0 | +| $C_{4,3,m}$ | 0 | 1 | 1 | 0 | + +**Table 32: Hadamard matrix of order 20** + +| k | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | +|---------------|---|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----| +| $C_{20,0,k}$ | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | +| $C_{20,1,k}$ | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | +| $C_{20,2,k}$ | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| $C_{20,3,k}$ | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| $C_{20,4,k}$ | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | +| $C_{20,5,k}$ | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | +| $C_{20,6,k}$ | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | +| $C_{20,7,k}$ | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | +| $C_{20,8,k}$ | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | +| $C_{20,9,k}$ | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | +| $C_{20,10,k}$ | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | +| $C_{20,11,k}$ | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | +| $C_{20,12,k}$ | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| $C_{20,13,k}$ | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | +| $C_{20,14,k}$ | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | +| $C_{20,15,k}$ | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| $C_{20,16,k}$ | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | +| $C_{20,17,k}$ | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | +| $C_{20,18,k}$ | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | +| $C_{20,19,k}$ | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | + +The binary orthogonal sequence ( $C_{80,r,n}$ ) used for spreading operation is selected from the $r^{\text{th}}$ row of the orthogonal matrix of order 80 ( $C_{80}$ ). A HARQ acknowledgement indicator is synchronously linked with the E-DCH TTI transmission to which it relates. There is thus a one-to-one association between an E-DCH TTI transmission and its respective HARQ acknowledgement indicator. + +#### 4.11.2.2 Coding of the HARQ acknowledgement indicator and TPC/SS + +For scheduled transmissions, E-HICHs carry HARQ acknowledgement indicators only. + +When the special default midamble allocation scheme is not used for E-PUCH, a logical allocation resource tag ID "r" ( $r=0, 1, 2, \dots, 79$ ) is calculated first for the E-DCH resource allocation associated with the HARQ acknowledgement indicator. + +where: + +$t_0$ is the last (highest-numbered) allocated timeslot (1,2,...,5) + +$q_0$ is the lowest-numbered channelisation code index allocated in timeslot $t_0$ (1,2,..., $Q_0$ ) + +$Q_0$ is the spreading factor of the lowest-numbered channelisation code index allocated in timeslot $t_0$ + +When the special default midamble allocation scheme is used for E-PUCH, a logical allocation resource tag ID "r" ( $r=0, 1, 2, \dots, 79$ ) is calculated first associated with the HARQ acknowledgement indicator. + +$$r = 16(t_0 - 1) + (q_0 - 1) \frac{16}{Q_0} + offset$$ + +where: + +$t_0$ , $q_0$ and $Q_0$ have the same definition as above . + +Offset is decided by the special default midamble pattern indicator on E-AGCH and the mapping in Table 33 below applies. + +**Table 33: Offset mapping table** + +| offset | $x_{mpi,1}$ | $x_{mpi,2}$ | +|---------------|-------------|-------------| +| 0 | 0 | 0 | +| 1 | 0 | 1 | +| 2 | 1 | 0 | +| 3 | 1 | 1 | + +The logical resource tag ID $r$ is then mapped to a physical allocation resource tag ID $r'$ , + +where $P$ is a permutation function depends on the logical signature index $r$ , system sub-frame number SFN' of E-HICH and the cell specific basic midamble code sequence. A 7-tap linear feedback shift register (LFSR) is used to generate pseudo-random numbers which are then used to generate the pseudo-random permutation $P$ . The generator polynomial of the 7-tap LFSR is , as shown in Figure 27. + +![Figure 27: Structure of PN register. The diagram shows a sequence of 8 rectangular blocks connected in a chain by arrows. Above the first three blocks is a long, empty rectangular box. Below the third block, an arrow points down to a circular node. From this circular node, an arrow points left and then up to the input of the first block, indicating a feedback loop.](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +Figure 27: Structure of PN register. The diagram shows a sequence of 8 rectangular blocks connected in a chain by arrows. Above the first three blocks is a long, empty rectangular box. Below the third block, an arrow points down to a circular node. From this circular node, an arrow points left and then up to the input of the first block, indicating a feedback loop. + +**Figure 27: Structure of PN register** + +The pseudo-random permutation is generated according to the following procedures: + +1. Initialization + +(a) Initialize $M = 80$ , initialize $P$ as $P(m) = m$ , $m = 0, 1, \dots, M-1$ ; + +(b) Initialize $N = 7$ ; + +(c) Initialize PN register with seed $s$ , where $s = \text{LSB}(\text{SFN}, N) \oplus \text{LSB}(\text{MidambleCode}, N)$ and $s_6, s_5, \dots, s_0$ are put into the register in the order as shown in figure 27; + +(d) Initialize $i = 0$ . + +2. Repeat the following steps while $i \leq M - 3$ . + +(a) Find the smallest $p$ such that $M - i - 1 < 2^p$ ; + +(b) Clock the PN register $N$ times to obtain an $N$ -bit pseudorandom number $x$ . Set $k = \text{LSB}(x, p)$ ; + +(c) If $k > M - i - 1$ , set $k = k - (M - i)$ ; + +(d) Swap the $i$ -th and the $(k+i)$ -th element of $P$ , i.e., $\text{tmp} = P(i)$ , $P(i) = P(k+i)$ , $P(k+i) = \text{tmp}$ ; + +(e) Increment $i$ by 1. + +where " $\text{LSB}(x, n)$ " means the right most $n$ bits of $x$ , " $\oplus$ " means modulo 2 addition, and the first output bit from the PN register is the MSB, while the final output bit is the LSB. The resulting $P$ is the output permutation and the physical signature sequence index is given by . + +The output of the spreading stage is equal to , where $n=0,1,\dots,79$ and is the Xor operation. + +For Non-Scheduled transmissions and E-DCH semi-persistent scheduling operation,, E-HICHs carry HARQ acknowledgement indicators and TPC/SS commands. The 80 orthogonal sequences are divided into 20 groups while each group includes 4 sequences of contiguous logical resource tag ID. The mapping between the logical resource tag ID and the physical tag ID is same as scheduled transmissions. Each non-scheduled user is assigned one group by higher layer to indicate the HARQ acknowledgement indicator and TPC/SS command. The first one of the four sequences is used for the acknowledgement indicator's spreading operation and one of the other three is used to indicate TPC/SS command implicitly. The mapping relations between them are described in [7]. + +The HARQ acknowledgement indicator is spread by the assigned orthogonal sequence $(C_{80,s',n})$ , where $s'$ is the physical resource tag ID. The output of the spreading stage is equal to, where $n=0,1,\dots,79$ . The sequence chosen to indicate TPC/SS command is denoted as " $e_{h,n}$ ", , where is the same as the parameter B defined in [7]. + +#### 4.11.2.3 Bit scrambling and Physical channel mapping of the E-HICH + +For scheduled transmission, the bit sequence $b_{h,0}, b_{h,1}, \dots, b_{h,79}$ is segmented into two halves, $b_{h,0}, \dots, b_{h,39}$ , and $b_{h,40}, \dots, b_{h,79}$ . 8 spare bits $z_u$ ( $u=0\dots 7$ ) are inserted between the first and second half of the sequence to form: + +$$d_h = \{b_{h,0}, b_{h,1}, \dots, b_{h,39}, z_0, z_1, \dots, z_7, b_{h,40}, b_{h,41}, \dots, b_{h,79}\}$$ + +The spare bit sequence $z_u$ is not defined. For Non-Scheduled transmission, the corresponding output bit sequences are: + +$$d_{h1} = \{c_{h,0}, c_{h,1}, \dots, c_{h,39}, z_0, z_1, \dots, z_7, c_{h,40}, c_{h,41}, \dots, c_{h,79}\}$$ + +$$d_{h2} = \{e_{h,0}, e_{h,1}, \dots, e_{h,39}, z_0, z_1, \dots, z_7, e_{h,40}, e_{h,41}, \dots, e_{h,79}\}$$ + +Then the corresponding bit sequence $d_h$ or $d_{h1}/d_{h2}$ is formed by applying bit scrambling (as defined in subclause 4.2.9) to the sequence $s_{h,n}$ or $s_{h1,n}/s_{h2,n}$ , $n=0,1,\dots,87$ . + +## 4.12 Coding for E-RUCCH + +For 1.28Mcps TDD, E-RUCCH supports both a 5ms and a 10ms TTI. For 3.84Mcps and 7.68Mcps TDD, E-RUCCH supports a TTI of 10ms only. The sequence of 39 information bits to be transmitted on one E-RUCCH as supplied by higher layers is defined as bits . + +The following processing steps (in sequential order) are defined for E-RUCCH: + +- CRC attachment +- Channel coding +- Rate matching +- Bit scrambling +- Frame related 2nd interleaving +- Mapping to physical channels + +### 4.12.1 CRC attachment for E-RUCCH + +From the sequence of $A_i=39$ bits () a CRC of length $L_i=16$ is appended according to Section 4.2.1.1. The bits output from CRC attachment are denoted $b_{im,k}$ , where $k=1,2,3, \dots, A_i+L_i$ and $A_i=39$ + +For 3.84Mcps and 7.68Mcps TDD, each parity bit $b_{im,k}$ , (where $k=A_i+1, A_i+2, \dots, A_i+L_i$ ) is then XOR'd with 1 such that its polarity is reversed. + +### 4.12.2 Channel coding for E-RUCCH + +1/3 rate convolutional channel coding is applied to the sequence $b_1, b_2, \dots, b_{im,k}$ in accordance with section 4.2.3.1, resulting in the sequence of bits $z_1, z_2, \dots, z_{3(k+8)}$ . + +### 4.12.3 Rate matching for E-RUCCH + +Rate matching for E-RUCCH shall be applied to the input sequence $z_1, z_2, \dots, z_{3(k+8)}$ to obtain the output sequence $r_1, r_2, \dots, r_U$ , where $U=176$ for 1.28Mcps and $U=232$ for 3.84Mcps and 7.68Mcps TDD, according to the general method described in subclause 4.2.7. + +### 4.12.4 Bit scrambling for E-RUCCH + +Bit scrambling for E-RUCCH shall be performed in accordance with the general method described in subclause 4.2.9. + +### 4.12.5 Interleaving for E-RUCCH + +Frame-related 2nd interleaving for E-RUCCH shall be performed in accordance with the general method described in subclause 4.2.11.1. + +### 4.12.6 Physical channel mapping for E-RUCCH + +Physical channel mapping for the E-RUCCH shall be performed in accordance with the general method described in subclause 4.2.12.1. + +## 5 Multiplexing, channel coding and interleaving for the 3.84 Mcps MBSFN IMB option + +### 5.1 General + +Data streams from/to MAC and higher layers (Transport block / Transport block set) are encoded/decoded to offer transport services over the radio transmission link. The channel coding scheme is a combination of error detection, error correcting, rate matching, interleaving and the mapping of transport channels onto physical channels. + +### 5.2 General coding/multiplexing of TrCHs + +This section only applies to the transport channels BCH and FACH. + +Data arrives to the coding/multiplexing unit in form of transport block sets once every transmission time interval. The transmission time interval is transport-channel specific from the set {10 ms, 20 ms, 40 ms, 80 ms}. An overview of the coding/multiplexing steps applicable to MBSFN IMB is shown in figure 2 of subclause 4.2 in [3]. + +#### 5.2.1 CRC attachment + +Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC). CRC attachment shall be performed in accordance with the general method described in subclause 4.2.1 of [3]. + +#### 5.2.2 Transport block concatenation and code block segmentation + +Transport blocks, with attached CRCs, are concatenated and segmented into code blocks. Transport block concatenation and code block segmentation shall be performed in accordance with the general method described in subclause 4.2.2 of [3]. + +#### 5.2.3 Channel coding + +Code blocks are delivered to the channel coding. Channel coding shall be performed in accordance with the general method described in subclause 4.2.3 of [3]. The following restrictions apply: + +- Convolutional coding shall be applied to FACH transport channel mapped on S-CCPCH frame type 1 only. +- Turbo coding shall be applied to FACH transport channels mapped on S-CCPCH frame type 2 only. + +#### 5.2.4 1st Interleaving + +First interleaving shall be performed in accordance with the general methods described in subclause 4.2.5 of [3]. + +#### 5.2.5 Radio frame segmentation + +Radio frame segmentation shall be performed in accordance with the general method described in subclause 4.2.6 of [3]. + +#### 5.2.6 Rate matching + +Rate matching shall be performed in accordance with the general method described in subclause 4.2.7 of [3], in which the downlink description is only relevant. Only flexible positions of TrCHs are supported for the MBSFN IMB option. + +For S-CCPCH frame type 2, the number of bits available to the CCTrCH in one radio frame using $P$ physical channels is defined as $N_{data,*} = 3 \times N_{data1} + (P-1) \times 3 \times N'_{data1}$ , where $N_{data1}$ is defined in [2] and $N'_{data1}$ is the data size of the corresponding slot format with zero TFCI bits. + +## 5.2.7 TrCH multiplexing + +Transport channel multiplexing shall be performed in accordance with the general method described in subclause 4.2.8 of [3]. + +## 5.2.8 Insertion of discontinuous transmission (DTX) indication bits + +DTX is used to fill up the radio frame with bits. The DTX indication bits inserted in this step shall be placed at the end of the radio frame, corresponding to flexible positions of TrCHs in the radio frame [3]. Note that the DTX indication bits will be distributed over all slots after 2nd interleaving. + +The bits input to the DTX insertion block are denoted by $s_1, s_2, s_3, \dots, s_S$ , where $S$ is the number of bits from TrCH multiplexing. The bits output from the DTX insertion block are denoted by and defined by the following relations: + +$$w_k = s_k \quad k = 1, 2, 3, \dots, S$$ + +$$w_k = \delta \quad k = S+1, S+2, S+3, \dots, W$$ + +where DTX indication bits are denoted by $\delta$ . Note that bits $w_k$ are three valued and that $W = N_{data,*}$ . + +## 5.2.9 Physical channel segmentation + +For the 3.84 Mcps MBSFN IMB option, physical channel segmentation is applicable to S-CCPCH frame type 2 only. + +When more than one PhCH is used, physical channel segmentation divides the bits among the different PhCHs. The bits input to the physical channel segmentation are denoted by, where $W$ is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by $P$ . + +The bits after physical channel segmentation are denoted $u_{p,1}, u_{p,2}, u_{p,3}, \dots, u_{p,U_p}$ , where $p$ is PhCH number and $U_p$ is the number of bits in one radio frame of the $p^{th}$ PhCH. The relation between $w_k$ and $u_{p,k}$ is given below. + +Bits on first PhCH after physical channel segmentation: + +$$k = 1, 2, \dots, U_1$$ + +Bits on second PhCH after physical channel segmentation: + +$$k = 1, 2, \dots, U_2$$ + +... + +Bits on the $P^{th}$ PhCH after physical channel segmentation: + +$$k = 1, 2, \dots, U_P$$ + +The number of bits $U_p$ in one radio frame of the $p^{th}$ PhCH is $3 \times N_{data1}$ for $p=1$ and $3 \times N'_{data1}$ for $p = 2, 3, \dots, P$ , where $N_{data1}$ is defined in [2] and $N'_{data1}$ is the data size of the corresponding slot format with zero TFCI bits. + +## 5.2.10 2nd Interleaving + +Second interleaving is performed in accordance with the general method described in section 4.2.11 of [3]. For S-CCPCH frame type 2, 2nd interleaving is performed per physical channel of the CCTrCH. + +## 5.2.11 Physical channel mapping + +Physical channel mapping shall be performed in accordance with the general method described in subclause 4.2.12 in [3], in which the downlink description is only relevant. + +## 5.2.12 Restrictions on different types of CCTrCHs + +Restrictions on the different types of CCTrCHs are described in general terms in [16]. In this subclause those restrictions are given with layer 1 notation. + +### 5.2.12.1 Broadcast channel (BCH) + +The restrictions of subclause 4.2.13.6 of [3] apply. + +### 5.2.12.2 Forward access channel (FACH) + +- The maximum value of the number of TrCHs $I$ in a CCTrCH and the maximum value of the number of transport blocks $M_i$ on each transport channel are given from the UE capability class. +- Only one Secondary CCPCH frame type 1 is used per CCTrCH. +- The maximum number of Secondary CCPCHs of frame type 2 used per CCTrCH is defined in [17]. + +## 5.2.13 Multiplexing of different TrCHs into one CCTrCH, and mapping of one CCTrCH onto physical channels + +Multiplexing of different transport channels into one coded composite transport channel shall be performed in accordance with the general method described in 4.2.14 of [3]. + +## 5.3 Transport format detection + +For MBSFN IMB operations, the transport format combination is signalled using the TFCI field of an S-CCPCH slot and only TFCI based detection shall be used. + +### 5.3.1 Transport format detection based on TFCI + +When a TFCI is available, then TFCI based detection shall be applicable to all TrCHs within the CCTrCH. The TFCI informs the receiver about the transport format combination of the CCTrCHs. As soon as the TFCI is detected, the transport format combination, and hence the transport formats of the individual transport channels are known. + +### 5.3.2 Coding of Transport-Format-Combination Indicator (TFCI) + +The number of TFCI bits to be encoded per CCTrCH shall always be within the range 1 to 5. These bits shall be encoded according to the general method of subclause 4.3.1.2.2 to produce 16 encoded bits b0 to b15. This procedure is valid also for the case where the number of TFCI bits to be encoded is less than 3. + +### 5.3.3 Mapping of TFCI words + +#### 5.3.3.1 Mapping of TFCI bits for Secondary CCPCH + +The 16 encoded TFCI bits are directly mapped to the S-CCPCH slots of the radio frame. Within a slot the bit with lower index is transmitted before the bit with higher index. The coded bits $b_k$ , are mapped to the transmitted TFCI bits $d_k$ , according to the following formula: + +$$d_k = b_{k \bmod 16}$$ + +For S-CCPCH frame type 1, $k = 0, 1, 2, \dots, 29$ . For S-CCPCH frame type 2 using QPSK data modulation, $k = 0, 1, 2, \dots, 47$ whilst for S-CCPCH frame type 2 using 16-QAM data modulation, $k = 0, 1, 2, \dots, 23$ . + +The set of TFCI bits $d_k$ shall be modulated as defined in [9] and mapped to slots of the radio frame such that they are transmitted in ascending order of $k$ . + +--- + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|----------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RAN_05 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99694 | 001 | 3 | Correction of rate matching parameters for repetition after 1st Interleaving in 25.222 | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 002 | 1 | Clarification of bit separation and collection | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 003 | - | Changing the initial offset value for convolutional code rate matching | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99693 | 004 | 1 | Editorial corrections to TS 25.222 | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 007 | - | Update of rate matching rule for TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 009 | 1 | Modified physical channel mapping scheme | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 013 | - | Introduction of TFCI for S-CCPCH in TDD mode | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99694 | 015 | - | TFCI coding and mapping in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000068 | 017 | - | Corrections to TS 25.222 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 018 | - | Refinements of Physical Channel Mapping | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 019 | 1 | TFCI coding specification in TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 021 | - | Modification of Turbo code internal interleaver | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 023 | - | Update of TS 25.222 - clarification of BTFD for TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 025 | - | Change of TFCI basis for TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 026 | - | Padding Function for Turbo coding of small blocks | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 027 | - | Editorial modification of shifting parameter calculation for turbo code puncturing | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000068 | 029 | 1 | Editorial changes of channel coding section | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000272 | 030 | - | Parity bit attachment to 0 size transport block | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000272 | 031 | - | Correction of the mapping formula | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000272 | 034 | - | Alignment of Multiplexing for TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000272 | 036 | 2 | Bit separation of the Turbo encoded data | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000272 | 038 | 2 | Revision of code block segmentation description | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000272 | 039 | - | Editorial corrections in channel coding section | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000345 | 040 | 1 | Update of TS 25.222 | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000345 | 041 | 1 | Editorial corrections in Turbo code internal interleaver section | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000345 | 042 | - | Paging Indicator Terminology | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000345 | 043 | 1 | Bit separation and collection for rate matching | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000345 | 048 | - | Puncturing Limit definition in WG1 specification | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000543 | 049 | - | Clarification on the Ci formula | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000543 | 050 | - | Correction on TFCI & TPC Transmission | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000543 | 053 | 1 | Editorial corrections in TS 25.222 | 3.4.0 | 3.5.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010063 | 051 | 1 | Bit Scrambling for TDD | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010063 | 054 | 1 | Corrections & Clarifications for TS25.222 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 055 | 1 | Inclusion of 1.28Mcps TDD in TS 25.222 | 3.5.0 | 4.0.0 | +| 21/09/01 | RAN_13 | RP-010523 | 057 | - | TFCI Terminology | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010529 | 058 | - | 5ms TTI for PRACH for 1.28 Mcps TDD | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010529 | 060 | - | A correction on the meaning of FPACH in TS 25.222 | 4.0.0 | 4.1.0 | +| 14/12/01 | RAN_14 | RP-010747 | 059 | - | Bit Scrambling for TDD | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010747 | 061 | - | Corrections in clause 4.1 and 4.2 of TS 25.222 | 4.1.0 | 4.2.0 | +| 08/03/02 | RAN_15 | RP-020050 | 063 | 1 | Correction to addition of padding zeros to PICH in TDD | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020050 | 065 | 3 | Clarification of the requirement for the determination of the rate matching parameters and editorial corrections to 25.222 | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020058 | 066 | 2 | Inclusion of HSDPA in 25.222 | 4.2.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020311 | 077 | - | Second Stage Interleaving and Physical Channel Mapping | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020311 | 076 | 1 | Zero padding for TFCI (3.84Mcps TDD) | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020314 | 073 | - | Correction to addition of padding zeros to PICH in 1.28 Mcps TDD | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020314 | 086 | - | Zero padding for TFCI (1.28Mcps TDD) | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 078 | 2 | Removal of inconsistencies and ambiguities in the HARQ description | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 079 | 4 | Corrections to HS-DSCH coding | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 082 | 1 | Corrections to HSDPA Multiplexing and Coding | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 084 | - | Introduction of HS-SCCH Cyclic Sequence Counter for TDD | 5.0.0 | 5.1.0 | +| 19/09/02 | RAN_17 | RP-020570 | 097 | 1 | Clarification of the definition of layer 1 transport channel numbers | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020585 | 093 | - | HS-DSCH Interleaving for TDD | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020585 | 091 | 1 | HS-SCCH corrections for TDD | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020585 | 089 | 1 | Clarification of TFRI bits for 3.84Mcps HSDPA TDD | 5.1.0 | 5.2.0 | +| 15/10/02 | - | - | - | - | Moving of misplaced sections 4.6.1.5 and 4.6.1.6 | 5.2.0 | 5.2.1 | +| 22/12/02 | RAN_18 | RP-020843 | 100 | - | Corrections to TFCI encoding of very short TFCI lengths | 5.2.1 | 5.3.0 | +| 22/12/02 | RAN_18 | RP-020843 | 102 | - | Corrections to TFCI encoding of very short TFCI lengths | 5.2.1 | 5.3.0 | +| 22/12/02 | RAN_18 | RP-020849 | 103 | - | Correction of editorial Error | 5.2.1 | 5.3.0 | +| 22/12/02 | RAN_18 | RP-020849 | 104 | - | Miscellaneous Minor HSDPA Corrections | 5.2.1 | 5.3.0 | +| 22/12/02 | RAN_18 | RP-020852 | 107 | - | Editorial modification to the section numberings | 5.2.1 | 5.3.0 | +| 25/03/03 | RAN_19 | RP-030139 | 108 | 1 | HSDPA corrections | 5.3.0 | 5.4.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 25/03/03 | RAN_19 | RP-030139 | 109 | 3 | Miscellaneous Corrections | 5.3.0 | 5.4.0 | +| 24/06/03 | RAN_20 | RP-030276 | 111 | - | Corrections to field coding of CQI for HS-SICH (3.84Mcps TDD) | 5.4.0 | 5.5.0 | +| 24/06/03 | RAN_20 | RP-030276 | 112 | - | Correction to definition of number of bits available to HS-DSCH in one TTI. | 5.4.0 | 5.5.0 | +| 06/01/04 | RAN_22 | RP-030646 | 118 | 1 | Correction of subframe segmentation, physical channel mapping & rate matching for 1.28Mcps TDD | 5.5.0 | 5.6.0 | +| 06/01/04 | RAN_22 | RP-030650 | 119 | - | Clarification of the CRC attachment procedure for HS-SCCH (TDD) | 5.5.0 | 5.6.0 | +| 06/01/04 | RAN_22 | RP-030660 | 120 | - | HARQ process identifier mapping | 5.5.0 | 5.6.0 | +| 06/01/04 | RAN_22 | RP-030712 | 121 | - | Alignment of "Soft channel bits" terminology with 25.306 | 5.5.0 | 5.6.0 | +| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.6.0 | 6.0.0 | +| 07/09/04 | RAN_25 | RP-040315 | 124 | 1 | Correction of symbol Xi defined in sub-frame segmentation step | 6.0.0 | 6.1.0 | +| 13/12/04 | RAN_26 | RP-040451 | 125 | - | Introduction of MICH | 6.1.0 | 6.2.0 | +| 20/03/06 | RAN_31 | RP-060078 | 0126 | - | Introduction of the Physical Layer Common Control Channel (PLCCH) | 6.2.0 | 7.0.0 | +| 20/03/06 | RAN_31 | RP-060079 | 0127 | - | Introduction of 7.68Mcps TDD option | 6.2.0 | 7.0.0 | +| 29/09/06 | RAN_33 | RP-060492 | 0129 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | RP-060491 | 0130 | - | Correction to coding of PLCCH for 1.28Mcps TDD | 7.0.0 | 7.1.0 | +| 13/03/07 | RAN_35 | RP-070118 | 0131 | 2 | Introduction of E-DCH for 1.28Mcps TDD | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070385 | 0132 | 1 | Support for MBSFN operation | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070383 | 0133 | 1 | Modification on HARQ process ID signalling for 1.28Mcps TDD | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070385 | 0135 | - | Support for 1.28Mcps TDD MBSFN operation | 7.2.0 | 7.3.0 | +| 11/09/07 | RAN_37 | RP-070650 | 0136 | - | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 11/09/07 | RAN_37 | RP-070647 | 0137 | - | TFCI mapping for S-CCPCH and 16QAM for 1.28Mcps TDD MBSFN | 7.3.0 | 7.4.0 | +| 11/09/07 | RAN_37 | RP-070640 | 0138 | 1 | Improved E-HICH signature sequence allocation for LCR TDD | 7.3.0 | 7.4.0 | +| 27/11/07 | RAN_38 | RP-070943 | 0141 | 1 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.4.0 | 7.5.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0144 | 1 | Some corrections for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080141 | 0145 | 1 | Clarification on TFCI mapping for 1.28Mcps TDD MBMS | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.6.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080356 | 0150 | 1 | Introduction 64QAM for 1.28Mcps TDD HSDPA | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 151 | 1 | Clarification on E-HICH coding for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080661 | 153 | 1 | Clarification of E-UCCH Number indicator on E-AGCH for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080661 | 154 | - | Clarification of TRRI on E-AGCH for 1.28Mcps TDD EUL | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080661 | 155 | - | Correction of E-HICH coding for 1.28Mcps TDD EUL | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-080976 | 159 | - | Clarification of E-DCH RV index selection for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-080980 | 161 | 1 | Correction of description about 64QAM for LCR TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-080987 | 162 | - | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-081118 | 163 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090230 | 165 | - | Correction of the absolute grant (power) value mapping for 1.28Mcps TDD EUL | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090240 | 166 | 1 | Introducing of CPC for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090241 | 167 | 1 | Introducing of MIMO for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090239 | 168 | - | Corrections to 25.222 for 3.84Mcps MBSFN IMB | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090239 | 169 | - | TFCI for Secondary CCPCH frame type 2 with 16QAM | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090231 | 173 | - | Editorial correction for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090533 | 174 | - | Modification of CCS information mapping tables for LCR TDD | 8.4.0 | 8.5.0 | +| 26/05/09 | RAN_44 | RP-090526 | 175 | 1 | Corrections to the coding of E-RUCCH for 1.28 Mcps TDD | 8.4.0 | 8.5.0 | +| 26/05/09 | RAN_44 | RP-090530 | 177 | - | Clarification of HS-DSCH coding for MIMO dual stream transmission for 1.28Mcps TDD | 8.4.0 | 8.5.0 | +| 15/09/09 | RAN_45 | RP-090893 | 178 | 2 | Correction to the channel mapping and rate matching for HS-DSCH in CPC for 1.28Mcs TDD | 8.5.0 | 8.6.0 | +| 15/09/09 | RAN_45 | RP-090893 | 180 | - | Modification of HS-SCCH types for CPC in 1.28Mcps TDD | 8.5.0 | 8.6.0 | +| 15/09/09 | RAN_45 | RP-090893 | 182 | 1 | Correction to Xptr field definition for LCR TDD | 8.5.0 | 8.6.0 | +| 15/09/09 | RAN_45 | RP-090893 | 183 | 1 | Correction to HS-SCCH Type 2 definition for LCR TDD | 8.5.0 | 8.6.0 | +| 15/09/09 | RAN_45 | RP-090893 | 184 | - | Clarification of HS-SCCH Order types against HS-SCCH types | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | RP-091166 | 185 | 1 | Correction to the Resource repetition period of SPS operation for 1.28Mcps TDD | 8.6.0 | 8.7.0 | +| 01/12/09 | RAN_46 | RP-091176 | 192 | 1 | Modification to HS-SCCH for TS0 for 1.28Mcps TDD | 8.7.0 | 9.0.0 | +| 16/03/10 | RAN_47 | RP-100202 | 195 | - | Correction to the resource repetition period index for 1.28Mcps TDD | 9.0.0 | 9.1.0 | +| 16/03/10 | RAN_47 | RP-100202 | 201 | - | Corrections to the Physical channel mapping for HS-DSCH for 1.28Mcps TDD | 9.0.0 | 9.1.0 | +| 01/06/10 | RAN_48 | RP-100585 | 205 | - | Corrections to the Physical channel mapping of 64QAM for HS-DSCH for 1.28Mcps TDD | 9.1.0 | 9.2.0 | +| 07/12/10 | RAN_50 | RP-101319 | 208 | - | Introduction of MU-MIMO for 1.28Mcps TDD | 9.2.0 | 10.0.0 | +| 15/03/11 | RAN_51 | RP-110253 | 209 | 1 | Correction to TS 25.222 for MC HSUPA for 1.28Mcps TDD | 10.0.0 | 10.1.0 | +| 05/12/11 | RAN_54 | RP-111665 | 211 | 1 | Physical channel mapping for HS-DSCH for secondary carrier TS0 for LCR TDD | 10.1.0 | 10.2.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 2013-12 | RP_62 | RP-131895 | 213 | 1 | Introduction of HSPA signalling enhancements for more efficient resource usage for LCR TDD | 11.0.0 | 12.0.0 | +| 2015-12 | SP_70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25223/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/25_series/25223/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e194f06f83516e5b58c8438209f940d2fbc5fe78 --- /dev/null +++ b/marked/Rel-16/25_series/25223/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1501930acfe685daecd120b550fe7a3b461ab2256b9b9ad5a07b3fdbdcfdf73 +size 38911 diff --git a/marked/Rel-16/25_series/25223/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-16/25_series/25223/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..685b9d81ad99fe0f1b3db979d3ea7c9bd8833303 --- /dev/null +++ b/marked/Rel-16/25_series/25223/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:976559a8bc892527b5e330ea42cf9cdd5a5fe9f75ca3aa8526ee8786121c372a +size 26540 diff --git a/marked/Rel-16/25_series/25223/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/25_series/25223/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc060b19f23968c091d618c286e91c4ef6432cd9 --- /dev/null +++ b/marked/Rel-16/25_series/25223/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06d1b62cf8a378437f2f76bde8ec4dd20c6685046cb15c2657023445b3baec0 +size 8911 diff --git a/marked/Rel-16/25_series/25223/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/25_series/25223/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b25dacd1e3ab6c7a40dcca6ca5d8941a3f859ee --- /dev/null +++ b/marked/Rel-16/25_series/25223/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68592f30fe300364bcf96cce795618cd79cd67bc75029aea2fc60dec6185fc02 +size 28697 diff --git a/marked/Rel-16/25_series/25223/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/25_series/25223/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ab49a54264101bc1d3f68132d34c9fca48b2a9d --- /dev/null +++ b/marked/Rel-16/25_series/25223/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff498f0980dead94b07d6fd874b910a0da3bc6530fd0fb1bf979889d54b5de7b +size 26283 diff --git a/marked/Rel-16/25_series/25223/7b8b192e2853ef28d28eff0241ebe86b_img.jpg b/marked/Rel-16/25_series/25223/7b8b192e2853ef28d28eff0241ebe86b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d38cfa20e1d83112d4baa1bd7677e9cdfe4014e --- /dev/null +++ b/marked/Rel-16/25_series/25223/7b8b192e2853ef28d28eff0241ebe86b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1784fd4887020f215becbe4b10cb010ba5e60f48dfd1da3d7edb4a4e3eb72f4a +size 29667 diff --git a/marked/Rel-16/25_series/25223/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25223/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..551b33fbffcecce6fc9dec1cc63f2c0db472ad9d --- /dev/null +++ b/marked/Rel-16/25_series/25223/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026b2b40a1ea2e12987bb0639912c0280d8b7461f63950fa9b5026594e0d848f +size 21554 diff --git a/marked/Rel-16/25_series/25223/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/25_series/25223/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de784dec70affe41aa1d88dd79e464f61643b3dc --- /dev/null +++ b/marked/Rel-16/25_series/25223/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6859238a9e3ef275f99d20b1febb8d64355fb32c788953ae85b1e044112c89a +size 27231 diff --git a/marked/Rel-16/25_series/25223/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/25_series/25223/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e838982d040b616e7856b70868752afb9722749c --- /dev/null +++ b/marked/Rel-16/25_series/25223/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29c0fc75bcf14a53c737689be45ed105ebdbc16a75f21277b9b1a17ae68df96f +size 33099 diff --git a/marked/Rel-16/25_series/25223/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/25_series/25223/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bb95ee0860ab82e8a85690367b47a06301bc384 --- /dev/null +++ b/marked/Rel-16/25_series/25223/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb9b4f1b7a177d34c8b94300bf62d7ccde9e45844fd58029e5dbe6a6de56cd5 +size 84996 diff --git a/marked/Rel-16/25_series/25223/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/25_series/25223/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0457ba4582a7709d68e7d3dc5e9210192dc5e11a --- /dev/null +++ b/marked/Rel-16/25_series/25223/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95e17c85680bc637c2ef49899543340cad231abdb53c488f6499c50a7e7bfddc +size 9368 diff --git a/marked/Rel-16/25_series/25223/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25223/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b8ddbd190bb30086dff488def86f95a0dccba3a --- /dev/null +++ b/marked/Rel-16/25_series/25223/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a3d90b963df14fadd34b2c2e1b3eda45c401e4ad0592ead0424dfcbccaeaed2 +size 19056 diff --git a/marked/Rel-16/25_series/25223/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/Rel-16/25_series/25223/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d789b8db67754b5ad186ca3dbfaaaa35ebe3afbd --- /dev/null +++ b/marked/Rel-16/25_series/25223/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87d09e174ab3791e845dbe89340762f7b2327f8f6a68207afb4cdd8a07e8c298 +size 20953 diff --git a/marked/Rel-16/25_series/25223/raw.md b/marked/Rel-16/25_series/25223/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d03888f14d18c4476733f3e1943dbd88f952d400 --- /dev/null +++ b/marked/Rel-16/25_series/25223/raw.md @@ -0,0 +1,1989 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Symbols and abbreviations ..... | 6 | +| 3.1 Symbols..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 5 Data modulation for the 3.84 Mcps and 7.68Mcps options..... | 8 | +| 5.1 Symbol rate ..... | 8 | +| 5.2 Mapping of bits onto signal point constellation..... | 8 | +| 5.2.1 Mapping for burst type 1 and 2 ..... | 8 | +| 5.2.1.1 QPSK modulation..... | 8 | +| 5.2.1.2 16QAM modulation..... | 8 | +| 5.2.2 Mapping for burst type 3 ..... | 11 | +| 5.2.3 Mapping for 3.84 Mcps MBSFN IMB..... | 11 | +| 5.2.3.1 Modulation mapping for data ..... | 11 | +| 5.2.3.2 Modulation mapping for TFCI ..... | 11 | +| 5A Data modulation for the 1.28 Mcps option ..... | 11 | +| 5A.1 Symbol rate ..... | 11 | +| 5A.2 Mapping of bits onto signal point constellation..... | 11 | +| 5A.2.1 QPSK modulation..... | 11 | +| 5A.2.2 8PSK modulation..... | 12 | +| 5A.2.3 16QAM modulation..... | 12 | +| 5A.2.4 64QAM modulation..... | 12 | +| 6 Spreading modulation ..... | 15 | +| 6.1 Basic spreading parameters..... | 15 | +| 6.2 Channelisation codes..... | 16 | +| 6.3 Channelisation Code Specific Multiplier ..... | 16 | +| 6.4 Scrambling codes for the 3.84Mcps and 1.28Mcps options ..... | 17 | +| 6.4a Scrambling codes for the 7.68Mcps option..... | 18 | +| 6.4a.1 Generation of binary scrambling codes..... | 18 | +| 6.5 Spread signal of data symbols and data blocks..... | 19 | +| 6.6 Modulation for the 3.84Mcps and 7.68Mcps options ..... | 19 | +| 6.6.1 Combination of physical channels in uplink ..... | 19 | +| 6.6.1a Physical channel transmission for E-PUCH..... | 21 | +| 6.6.2 Combination of physical channels in downlink ..... | 21 | +| 6.6.3 Combination of signature sequences for E-HICH..... | 21 | +| 6.7 Modulation for the 1.28 Mcps option..... | 22 | +| 6.7.1 Combination of physical channels in uplink ..... | 23 | +| 6.7.1a Physical channel transmission for E-PUCH..... | 23 | +| 6.7.2 Combination of physical channels in downlink ..... | 23 | +| 6.7.3 Combination of signature sequences for Scheduled E-HICH..... | 24 | +| 6.7.3a Combination of signature sequences for Non-Scheduled E-HICH..... | 25 | +| 6.8 Spreading modulation for the 3.84 Mcps MBSFN IMB option..... | 26 | +| 6.8.1 Spreading..... | 26 | +| 6.8.2 Code generation and allocation ..... | 27 | +| 6.8.2.1 Channelisation codes ..... | 27 | +| 6.8.2.2 Scrambling codes..... | 27 | +| 6.8.3 Modulation ..... | 27 | +| 7 Synchronisation codes for the 3.84 Mcps option..... | 28 | +| 7.1 Code Generation..... | 28 | +| 7.2 Code Allocation..... | 28 | +| 7.2.1 Code allocation for Case 1 ..... | 30 | +| 7.2.2 Code allocation for Case 2 ..... | 31 | + +| | | | +|-------------------------------|-------------------------------------------------------|-----------| +| 7.3 | Evaluation of synchronisation codes..... | 32 | +| 7.4 | Synchronisation codes for 3.84 Mcps MBSFN IMB ..... | 33 | +| 7.4.1 | Code generation..... | 33 | +| 7.4.2 | Code allocation of SSC ..... | 33 | +| 7A | Synchronisation codes for the 7.68 Mcps option..... | 33 | +| 7A.1 | Code Generation..... | 33 | +| 7A.2 | Code Allocation..... | 34 | +| 7A.2.1 | Code allocation for Case 1 ..... | 36 | +| 7A.2.2 | Code allocation for Case 2 ..... | 37 | +| 7A.3 | Evaluation of synchronisation codes..... | 38 | +| 8 | Synchronisation codes for the 1.28 Mcps option..... | 39 | +| 8.1 | The downlink pilot channel (DwPCH)..... | 39 | +| 8.1.1 | Modulation of the SYNC-DL..... | 39 | +| 8.2 | The uplink pilot channel (UpPCH) ..... | 39 | +| 8.3 | Code Allocation..... | 40 | +| 8.3Aa | Code Allocation..... | 40 | +| 9 | Cell synchronisation codes..... | 41 | +| Annex A (normative): | Scrambling Codes..... | 43 | +| Annex AA (normative): | Synchronisation sequence..... | 46 | +| AA.1 | Basic SYNC-DL sequence ..... | 46 | +| AA.2 | Basic SYNC-UL Codes..... | 47 | +| Annex B (informative): | Generalised Hierarchical Golay Sequences ..... | 53 | +| B.1 | Alternative generation..... | 53 | +| Annex C (informative): | Change history..... | 54 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes spreading and modulation for UTRA Physical Layer TDD mode. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.201: "Physical layer - general description". +- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [4] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [6] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [7] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [8] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [9] 3GPP TS 25.102: "UTRA (UE) TDD; Radio Transmission and Reception". +- [10] 3GPP TS 25.105: "UTRA (BS) TDD; Radio Transmission and Reception". +- [11] 3GPP TS25.308: "High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2". +- [12] 3GPP TS25.224: "Physical Layer Procedures (TDD)" +- [13] 3GPP TS25.321: "Medium Access Control (MAC) protocol specification" + +# --- 3 Symbols and abbreviations + +## 3.1 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------|----------------------------------------------------------------------------------------------------| +| $C_p$ : | PSC | +| $C_i$ : | i:th secondary SCH code | +| $C_{CSC, m}^{(k)}$ : | CSC derived as $k$ :th offset version from $m$ :th applicable constituent Golay complementary pair | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------------| +| 16QAM | 16 Quadrature Amplitude Modulation | +| CCTrCH | Coded Composite Transport Channel | + +| | | +|----------|---------------------------------------------| +| CDMA | Code Division Multiple Access | +| CSC | Cell Synchronisation Code | +| DPCH | Dedicated Physical Channel | +| FDD | Frequency Division Duplex | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| IMB | Integrated Mobile Broadcast | +| MBSFN | MBSM over a Single Frequency Network | +| MIB | Master Information Block | +| MU-MIMO | Multi-User Multiple Input Multiple Output | +| OVSF | Orthogonal Variable Spreading Factor | +| P-CCPCH | Primary Common Control Physical Channel | +| PN | Pseudo Noise | +| PRACH | Physical Random Access Channel | +| PSC | Primary Synchronisation Code | +| QPSK | Quadrature Phase Shift Keying | +| RACH | Random Access Channel | +| SCH | Synchronisation Channel | +| SF | Spreading Factor | +| SFN | System Frame Number | +| TDD | Time Division Duplex | +| TFC | Transport Format Combination | +| UE | User Equipment | +| UL | Uplink | + +# 4 General + +In the following, a separation between the data modulation and the spreading modulation has been made. The data modulation for 3.84Mcps TDD (including 3.84 Mcps MBSFN IMB) and 7.68Mcps TDD is defined in clause 5 'Data modulation for the 3.84 Mcps and 7.68Mcps options', the data modulation for 1.28Mcps TDD is defined in clause 5A 'Data modulation for the 1.28 Mcps option' and the spreading modulation in clause 6 'Spreading modulation'. + +Table 1 shows the basic modulation parameters for the 7.68Mcps, 3.84Mcps (including 3.84 Mcps MBSFN IMB) and 1.28Mcps TDD options. + +**Table 1: Basic modulation parameters** + +| | | | | +|---------------------------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| Chip rate | 7.68 Mchip/s | same as FDD basic chiprate: 3.84 Mchip/s and 3.84 Mcps MBSFN IMB | Low chiprate: 1.28 Mchip/s | +| Data modulation | QPSK, 16QAM (HS-PDSCH, MBSFN S-CCPCH and E-PUCH only) | QPSK, 16QAM (HS-PDSCH, MBSFN S-CCPCH and E-PUCH only) | QPSK, 8PSK, 16QAM (HS-PDSCH, E-PUCH, MBSFN S-CCPCH only), 64QAM (HS-PDSCH only) | +| Spreading characteristics | Orthogonal Q chips/symbol, where $Q = 2^p$ , $0 \leq p \leq 5$ | Orthogonal Q chips/symbol, where $Q = 2^p$ , $0 \leq p \leq 4$ (For 3.84 Mcps MBSFN IMB $Q = 2^p$ , where $p = 4$ or $8$ only) | Orthogonal Q chips/symbol, where $Q = 2^p$ , $0 \leq p \leq 4$ | + +# 5 Data modulation for the 3.84 Mcps and 7.68Mcps options + +## 5.1 Symbol rate + +The symbol duration $T_s$ depends on the spreading factor $Q$ and the chip duration $T_c$ : $T_s = Q \times T_c$ , where $T_c = \frac{1}{chiprate}$ . + +## 5.2 Mapping of bits onto signal point constellation + +### 5.2.1 Mapping for burst type 1 and 2 + +#### 5.2.1.1 QPSK modulation + +The data modulation is performed to the bits from the output of the physical channel mapping procedure in [8] and combines always 2 consecutive binary bits to a complex valued data symbol. Each user burst has two data carrying parts, termed data blocks: + +$$\underline{d}^{(k,i)} = \left( \underline{d}_1^{(k,i)}, \underline{d}_2^{(k,i)}, \dots, \underline{d}_{N_k}^{(k,i)} \right)^T, \quad i = 1, 2; k = 1, \dots, K_{Code} \quad (1)$$ + +$K_{Code}$ is the number of used codes in a time slot: for 3.84Mcps, max $K_{Code} = 16$ ; for 7.68Mcps, max $K_{Code} = 32$ . $N_k$ is the number of symbols per data field for the code $k$ . This number is linked to the spreading factor $Q_k$ [7]. + +Data block $\underline{d}^{(k,1)}$ is transmitted before the midamble and data block $\underline{d}^{(k,2)}$ after the midamble. Each of the $N_k$ data symbols $\underline{d}_n^{(k,i)}$ ; $i=1, 2; k=1, \dots, K_{Code}; n=1, \dots, N_k$ ; of equation 1 has the symbol duration $T_s^{(k)} = Q_k \cdot T_c$ as already given. + +The data modulation is QPSK, thus the data symbols $\underline{d}_n^{(k,i)}$ are generated from two consecutive data bits from the output of the physical channel mapping procedure in [8]: + +$$b_{l,n}^{(k,i)} \in \{0, 1\}, \quad l = 1, 2; k = 1, \dots, K_{Code}; n = 1, \dots, N_k; i = 1, 2 \quad (2)$$ + +using the following mapping to complex symbols: + +| consecutive binary bit pattern | complex symbol | +|----------------------------------|---------------------------| +| $b_{l,n}^{(k,i)} b_{2n}^{(k,i)}$ | $\underline{d}_n^{(k,i)}$ | +| 00 | +j | +| 01 | +1 | +| 10 | -1 | +| 11 | -j | + +The mapping corresponds to a QPSK modulation of the interleaved and encoded data bits $b_{l,n}^{(k,i)}$ of equation 2. + +#### 5.2.1.2 16QAM modulation + +The data modulation is performed to the bits from the output of the physical channel mapping procedure. In case of 16QAM, modulation 4 consecutive binary bits are represented by one complex valued data symbol. Each user burst has two data carrying parts, termed data blocks: + +$$\underline{d}^{(k,i)} = \left( \underline{d}_1^{(k,i)}, \underline{d}_2^{(k,i)}, \dots, \underline{d}_{N_k}^{(k,i)} \right)^T \quad i = 1, 2; k = 1, \dots, K. \quad (2b)$$ + +$N_k$ is the number of symbols per data field for the user $k$ . This number is linked to the spreading factor $Q_k$ . + +Data block $\underline{d}^{(k,1)}$ is transmitted before the midamble and data block $\underline{d}^{(k,2)}$ after the midamble. Each of the $N_k$ data symbols $\underline{d}_n^{(k,i)}$ ; $i=1, 2; k=1, \dots, K; n=1, \dots, N_k$ ; of equation 2b has the symbol duration $T_s^{(k)} = Q_k \cdot T_c$ as already given. + +The data modulation is 16QAM, thus the data symbols $\underline{d}_n^{(k,i)}$ are generated from 4 consecutive data bits from the output of the physical channel mapping procedure in [8]: + +$$b_{l,n}^{(k,i)} \in \{0, 1\}, \quad l = 1, 2, 3, 4; k = 1, \dots, K_{code}; n = 1, \dots, N_k; i = 1, 2 \quad (2c)$$ + +using the following mapping to complex symbols: + +| Consecutive binary bit pattern | complex symbol | +|-------------------------------------------------------------------|----------------------------------------------| +| $b_{1,n}^{(k,i)} b_{2,n}^{(k,i)} b_{3,n}^{(k,i)} b_{4,n}^{(k,i)}$ | $\underline{d}_n^{(k,i)}$ | +| 0000 | $j \frac{1}{\sqrt{5}}$ | +| 0001 | $-\frac{1}{\sqrt{5}} + j \frac{2}{\sqrt{5}}$ | +| 0010 | $\frac{1}{\sqrt{5}} + j \frac{2}{\sqrt{5}}$ | +| 0011 | $j \frac{3}{\sqrt{5}}$ | +| 0100 | $\sqrt{\frac{1}{5}}$ | +| 0101 | $\frac{2}{\sqrt{5}} - j \frac{1}{\sqrt{5}}$ | +| 0110 | $\frac{2}{\sqrt{5}} + j \frac{1}{\sqrt{5}}$ | +| 0111 | $\frac{3}{\sqrt{5}}$ | +| 1000 | $-\frac{1}{\sqrt{5}}$ | +| 1001 | $-\frac{2}{\sqrt{5}} + j \frac{1}{\sqrt{5}}$ | +| 1010 | $-\frac{2}{\sqrt{5}} - j \frac{1}{\sqrt{5}}$ | +| 1011 | $-\frac{3}{\sqrt{5}}$ | +| 1100 | $-j \frac{1}{\sqrt{5}}$ | +| 1101 | $\frac{1}{\sqrt{5}} - j \frac{2}{\sqrt{5}}$ | +| 1110 | $-\frac{1}{\sqrt{5}} - j \frac{2}{\sqrt{5}}$ | +| 1111 | $-j \frac{3}{\sqrt{5}}$ | + +The mapping corresponds to a 16QAM modulation of the interleaved and encoded data bits $b_{1,n}^{(k,i)}$ of the table above and $\underline{d}_n^{(k,i)}$ of equation 2b. + +### 5.2.2 Mapping for burst type 3 + +In case of burst type 3, the definitions in subclause 5.2.1.1 and subclause 5.2.1.2 apply with a modified number of symbols in the second data block. For the burst type 3, the number of symbols in the second data block $\underline{d}^{(k,2)}$ is decreased by $\frac{96}{Q_k}$ symbols for 3.84Mcps TDD and is decreased by $\frac{192}{Q_k}$ symbols for 7.68Mcps TDD. + +### 5.2.3 Mapping for 3.84 Mcps MBSFN IMB + +#### 5.2.3.1 Modulation mapping for data + +Mapping of data bits onto a QPSK or 16-QAM signal point constellation shall be accomplished as described in subclause 5.1.1.1 or 5.1.1.2 of [4] respectively. + +#### 5.2.3.2 Modulation mapping for TFCI + +In the case of S-CCPCH frame type 1 and S-CCPCH frame type 2 using QPSK modulation for data, TFCI bits shall be QPSK modulated according to subclause 5.1.1.1 of [4]. + +In the case of S-CCPCH frame type 2 using 16-QAM modulation for data, each consecutive pair of binary-valued TFCI bits $\{b_{2q}, b_{2q+1}\}$ , with $q = \{0, 1, 2, \dots\}$ shall be mapped according to the rotated QPSK constellation given by the following table. + +| $\{b_{2q}, b_{2q+1}\}$ | I branch | Q branch | +|------------------------|----------|----------| +| {0,0} | 0.4472 | 1.3416 | +| {0,1} | 1.3416 | -0.4472 | +| {1,0} | -1.3416 | 0.4472 | +| {1,1} | -0.4472 | -1.3416 | + +# 5A Data modulation for the 1.28 Mcps option + +## 5A.1 Symbol rate + +The symbol duration $T_s$ depends on the spreading factor $Q$ and the chip duration $T_c$ : $T_s = Q \times T_c$ , where $T_c = \frac{1}{chiprate}$ . + +## 5A.2 Mapping of bits onto signal point constellation + +### 5A.2.1 QPSK modulation + +The mapping of bits onto the signal point constellation for QPSK modulation is the same as in the 3.84Mcps TDD cf. [5.2.1.1 QPSK modulation]. + +### 5A.2.2 8PSK modulation + +The data modulation is performed to the bits from the output of the physical channel mapping procedure. In case of 8PSK modulation 3 consecutive binary bits are represented by one complex valued data symbol. Each user burst has two data carrying parts, termed data blocks: + +$$\mathbf{d}^{(k,i)} = (d_1^{(k,i)}, d_2^{(k,i)}, \dots, d_{N_k}^{(k,i)})^T, \quad i = 1, 2; k = 1, \dots, K_{Code} \quad (1a)$$ + +$N_k$ is the number of symbols per data field for the code $k$ . This number is linked to the spreading factor $Q_k$ . + +Data block $\mathbf{d}^{(k,1)}$ is transmitted before the midamble and data block $\mathbf{d}^{(k,2)}$ after the midamble. Each of the $N_k$ data symbols $d_n^{(k,i)}$ ; $i=1, 2$ ; $k=1, \dots, K_{Code}$ ; $n=1, \dots, N_k$ ; of equation 1 has the symbol duration $T_s^{(k)} = Q_k T_c$ as already given. + +The data modulation is 8PSK, thus the data symbols $d_n^{(k,i)}$ are generated from 3 consecutive data bits from the output of the physical channel mapping procedure in [8]: + +$$b_{l,n}^{(k,i)} \in \{0,1\} \quad l = 1, 2, 3; k = 1, \dots, K_{Code}; n = 1, \dots, N_k; i = 1, 2 \quad (2a)$$ + +using the following mapping to complex symbols: + +| Consecutive binary bit pattern | complex symbol | +|---------------------------------------------------|----------------------------------| +| $b_{1,n}^{(k,i)} b_{2,n}^{(k,i)} b_{3,n}^{(k,i)}$ | $\underline{d}_n^{(k,i)}$ | +| 000 | $\cos(11\pi/8) + j\sin(11\pi/8)$ | +| 001 | $\cos(9\pi/8) + j\sin(9\pi/8)$ | +| 010 | $\cos(5\pi/8) + j\sin(5\pi/8)$ | +| 011 | $\cos(7\pi/8) + j\sin(7\pi/8)$ | +| 100 | $\cos(13\pi/8) + j\sin(13\pi/8)$ | +| 101 | $\cos(15\pi/8) + j\sin(15\pi/8)$ | +| 110 | $\cos(3\pi/8) + j\sin(3\pi/8)$ | +| 111 | $\cos(\pi/8) + j\sin(\pi/8)$ | + +The mapping corresponds to a 8PSK modulation of the interleaved and encoded data bits $b_{l,n}^{(k,i)}$ of the table above and $\underline{d}_n^{(k,i)}$ of equation 1a. + +### 5A.2.3 16QAM modulation + +The mapping of bits onto the signal point constellation for 16QAM modulation is the same as in the 3.84Mcps TDD cf. [5.2.1.2 16QAM modulation]. + +### 5A.2.4 64QAM modulation + +The data modulation is performed to the bits from the output of the physical channel mapping procedure. In case of 64QAM, modulation 6 consecutive binary bits are represented by one complex valued data symbol. Each user burst has two data carrying parts, termed data blocks: + +$$\underline{\mathbf{d}}^{(k,i)} = (\underline{d}_1^{(k,i)}, \underline{d}_2^{(k,i)}, \dots, \underline{d}_{N_k}^{(k,i)})^T \quad i = 1, 2; k = 1, \dots, K. \quad (1c)$$ + +$N_k$ is the number of symbols per data field for the user k. This number is linked to the spreading factor $Q_k$ . + +Data block $\underline{\mathbf{d}}^{(k,1)}$ is transmitted before the midamble and data block $\underline{\mathbf{d}}^{(k,2)}$ after the midamble. Each of the $N_k$ data symbols $\underline{d}_n^{(k,i)}$ ; $i=1, 2; k=1, \dots, K; n=1, \dots, N_k$ ; of equation 1c has the symbol duration $T_s^{(k)} = Q_k \cdot T_c$ as already given. + +The data modulation is 64QAM, thus the data symbols $\underline{d}_n^{(k,i)}$ are generated from 6 consecutive data bits from the output of the physical channel mapping procedure in [8]: + +$$b_{l,n}^{(k,i)} \in \{0, 1\}, \quad l = 1, 2, 3, 4, 5, 6; \quad k = 1, \dots, K_{code}; \quad n = 1, \dots, N_k; \quad i = 1, 2 \quad (2c)$$ + +using the following mapping to complex symbols: + + + +| Consecutive binary bit pattern | complex symbol | Consecutive binary bit pattern | complex symbol | +|---------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------------------------------------| +| $b_{1,n}^{(k,i)} b_{2,n}^{(k,i)} b_{3,n}^{(k,i)} b_{4,n}^{(k,i)} b_{5,n}^{(k,i)} b_{6,n}^{(k,i)}$ | $\underline{d}_n^{(k,i)}$ | $b_{1,n}^{(k,i)} b_{2,n}^{(k,i)} b_{3,n}^{(k,i)} b_{4,n}^{(k,i)} b_{5,n}^{(k,i)} b_{6,n}^{(k,i)}$ | $\underline{d}_n^{(k,i)}$ | +| 000000 | $j \frac{3}{\sqrt{21}}$ | 100000 | $-\frac{3}{\sqrt{21}}$ | +| 000001 | $\frac{1}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | 100001 | $-\frac{2}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | +| 000010 | $-\frac{1}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | 100010 | $-\frac{2}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | +| 000011 | $j \frac{1}{\sqrt{21}}$ | 100011 | $-\frac{1}{\sqrt{21}}$ | +| 000100 | $-\frac{1}{\sqrt{21}} + j \frac{4}{\sqrt{21}}$ | 100100 | $-\frac{4}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | +| 000101 | $-\frac{2}{\sqrt{21}} + j \frac{5}{\sqrt{21}}$ | 100101 | $-\frac{5}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | +| 000110 | $-\frac{2}{\sqrt{21}} + j \frac{3}{\sqrt{21}}$ | 100110 | $-\frac{3}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | +| 000111 | $-\frac{3}{\sqrt{21}} + j \frac{4}{\sqrt{21}}$ | 100111 | $-\frac{4}{\sqrt{21}} + j \frac{3}{\sqrt{21}}$ | +| 001000 | $\frac{1}{\sqrt{21}} + j \frac{4}{\sqrt{21}}$ | 101000 | $-\frac{4}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | +| 001001 | $\frac{2}{\sqrt{21}} + j \frac{3}{\sqrt{21}}$ | 101001 | $-\frac{3}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | +| 001010 | $\frac{2}{\sqrt{21}} + j \frac{5}{\sqrt{21}}$ | 101010 | $-\frac{5}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | +| 001011 | $\frac{3}{\sqrt{21}} + j \frac{4}{\sqrt{21}}$ | 101011 | $-\frac{4}{\sqrt{21}} - j \frac{3}{\sqrt{21}}$ | +| 001100 | $j \frac{5}{\sqrt{21}}$ | 101100 | $-\frac{5}{\sqrt{21}}$ | +| 001101 | $-\frac{1}{\sqrt{21}} + j \frac{6}{\sqrt{21}}$ | 101101 | $-\frac{6}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | +| 001110 | $\frac{1}{\sqrt{21}} + j \frac{6}{\sqrt{21}}$ | 101110 | $-\frac{6}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | +| 001111 | $j \frac{7}{\sqrt{21}}$ | 101111 | $-\frac{7}{\sqrt{21}}$ | +| 010000 | $\frac{3}{\sqrt{21}}$ | 110000 | $-j \frac{3}{\sqrt{21}}$ | +| 010001 | $\frac{2}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | 110001 | $-\frac{1}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | +| 010010 | $\frac{2}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | 110010 | $\frac{1}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | +| 010011 | $\frac{1}{\sqrt{21}}$ | 110011 | $-j \frac{1}{\sqrt{21}}$ | + +| | | | | +|--------|-----------------------------------------------|--------|------------------------------------------------| +| 010100 | $\frac{4}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | 110100 | $\frac{1}{\sqrt{21}} - j \frac{4}{\sqrt{21}}$ | +| 010101 | $\frac{5}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | 110101 | $\frac{2}{\sqrt{21}} - j \frac{5}{\sqrt{21}}$ | +| 010110 | $\frac{3}{\sqrt{21}} - j \frac{2}{\sqrt{21}}$ | 110110 | $\frac{2}{\sqrt{21}} - j \frac{3}{\sqrt{21}}$ | +| 010111 | $\frac{4}{\sqrt{21}} - j \frac{3}{\sqrt{21}}$ | 110111 | $\frac{3}{\sqrt{21}} - j \frac{4}{\sqrt{21}}$ | +| 011000 | $\frac{4}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | 111000 | $-\frac{1}{\sqrt{21}} - j \frac{4}{\sqrt{21}}$ | +| 011001 | $\frac{3}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | 111001 | $-\frac{2}{\sqrt{21}} - j \frac{3}{\sqrt{21}}$ | +| 011010 | $\frac{5}{\sqrt{21}} + j \frac{2}{\sqrt{21}}$ | 111010 | $-\frac{2}{\sqrt{21}} - j \frac{5}{\sqrt{21}}$ | +| 011011 | $\frac{4}{\sqrt{21}} + j \frac{3}{\sqrt{21}}$ | 111011 | $-\frac{3}{\sqrt{21}} - j \frac{4}{\sqrt{21}}$ | +| 011100 | $\frac{5}{\sqrt{21}}$ | 111100 | $-j \frac{5}{\sqrt{21}}$ | +| 011101 | $\frac{6}{\sqrt{21}} - j \frac{1}{\sqrt{21}}$ | 111101 | $\frac{1}{\sqrt{21}} - j \frac{6}{\sqrt{21}}$ | +| 011110 | $\frac{6}{\sqrt{21}} + j \frac{1}{\sqrt{21}}$ | 111110 | $-\frac{1}{\sqrt{21}} - j \frac{6}{\sqrt{21}}$ | +| 011111 | $\frac{7}{\sqrt{21}}$ | 111111 | $-j \frac{7}{\sqrt{21}}$ | + +The mapping corresponds to a 64QAM modulation of the interleaved and encoded data bits $b_{l,n}^{(k,i)}$ of the table above and $\underline{d}_n^{(k,i)}$ of equation 2c. + +# 6 Spreading modulation + +Sub-clauses 6.1 to 6.7 do not apply to 3.84 Mcps MBSFN IMB. Spreading modulation for 3.84 Mcps MBSFN IMB is described in clause 6.8. + +## 6.1 Basic spreading parameters + +Spreading of data consists of two operations: Channelisation and Scrambling. Firstly, each complex valued data symbol $\underline{d}_n^{(k,i)}$ of equation 1 (or $e_n^{(k,i)}$ of equation 8 in the case of E-HICH) is spread with a real valued channelisation code $c^{(k)}$ of length $Q_k$ : for 3.84Mcps TDD and 1.28Mcps TDD, $Q_k \in \{1,2,4,8,16\}$ ; for 7.68Mcps TDD, $Q_k \in \{1,2,4,8,16,32\}$ . + +The resulting sequence is then scrambled by a complex sequence $\mathbf{v}$ : the sequence is $\mathbf{v}$ of length 16 for the 3.84Mcps and 1.28Mcps options; it is of length 32 for the 7.68Mcps option. + +## 6.2 Channelisation codes + +The elements $c_q^{(k)}$ ; $k=1,\dots,K_{\text{Code}}$ ; $q=1,\dots,Q_k$ ; of the real valued channelisation codes + +$$c^{(k)} = (c_1^{(k)}, c_2^{(k)}, \dots, c_{Q_k}^{(k)}) ; k=1, \dots, K_{Code};$$ + +shall be taken from the set + +$$V_c = \{1, -1\} \tag{3}$$ + +The $c_{Q_k}^{(k)}$ are Orthogonal Variable Spreading Factor (OVSF) codes, allowing to mix in the same timeslot channels with different spreading factors while preserving the orthogonality. The OVSF codes can be defined using the code tree of figure 1. + +![Code-tree for generation of Orthogonal Variable Spreading Factor (OVSF) codes for Channelisation Operation. The tree starts at Q=1 with c^{(k=1)}_{Q=1} = (1). It branches at Q=2 into c^{(k=1)}_{Q=2} = (1,1) and c^{(k=2)}_{Q=2} = (1,-1). The tree further branches at Q=4: c^{(k=1)}_{Q=2} branches into c^{(k=1)}_{Q=4} = (1,1,1,1) and c^{(k=2)}_{Q=4} = (1,1,-1,-1); c^{(k=2)}_{Q=2} branches into c^{(k=3)}_{Q=4} = (1,-1,1,-1) and c^{(k=4)}_{Q=4} = (1,-1,-1,1).](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +Code-tree for generation of Orthogonal Variable Spreading Factor (OVSF) codes for Channelisation Operation. The tree starts at Q=1 with c^{(k=1)}\_{Q=1} = (1). It branches at Q=2 into c^{(k=1)}\_{Q=2} = (1,1) and c^{(k=2)}\_{Q=2} = (1,-1). The tree further branches at Q=4: c^{(k=1)}\_{Q=2} branches into c^{(k=1)}\_{Q=4} = (1,1,1,1) and c^{(k=2)}\_{Q=4} = (1,1,-1,-1); c^{(k=2)}\_{Q=2} branches into c^{(k=3)}\_{Q=4} = (1,-1,1,-1) and c^{(k=4)}\_{Q=4} = (1,-1,-1,1). + +**Figure 1: Code-tree for generation of Orthogonal Variable Spreading Factor (OVSF) codes for Channelisation Operation** + +Each level in the code tree defines a spreading factor indicated by the value of Q in the figure. All codes within the code tree cannot be used simultaneously in a given timeslot. A code can be used in a timeslot if and only if no other code on the path from the specific code to the root of the tree or in the sub-tree below the specific code is used in this timeslot. This means that the number of available codes in a slot is not fixed but depends on the rate and spreading factor of each physical channel. + +For the 3.84Mcps and 1.28Mcps TDD options, the spreading factor goes up to $Q_{MAX}=16$ ; for the 7.68Mcps TDD option, the spreading factor goes up to $Q_{MAX}=32$ . + +## 6.3 Channelisation Code Specific Multiplier + +Associated with each channelisation code is a multiplier $w_{Q_k}^{(k)}$ taking values from the set $\{e^{j\pi/2 \cdot p_k}\}$ , where $P_k$ is a permutation of the integer set $\{0, \dots, Q_k - 1\}$ and $Q_k$ denotes the spreading factor. The multiplier is applied to the data sequence modulating each channelisation code. The values of the multiplier for each channelisation code are given in the table below: + +| k | $w_{Q=1}^{(k)}$ | $w_{Q=2}^{(k)}$ | $w_{Q=4}^{(k)}$ | $w_{Q=8}^{(k)}$ | $w_{Q=16}^{(k)}$ | $w_{Q=32}^{(k)}$ | +|----------|-----------------|-----------------|-----------------|-----------------|------------------|------------------| +| 1 | 1 | 1 | -j | 1 | -1 | -j | +| 2 | | +j | 1 | +j | -j | -1 | +| 3 | | | +j | +j | 1 | -1 | +| 4 | | | -1 | -1 | 1 | 1 | +| 5 | | | | -j | +j | -1 | +| 6 | | | | -1 | -1 | -j | +| 7 | | | | -j | -1 | j | +| 8 | | | | 1 | 1 | 1 | +| 9 | | | | | -j | -1 | +| 10 | | | | | +j | 1 | +| 11 | | | | | 1 | 1 | +| 12 | | | | | +j | -j | +| 13 | | | | | -j | j | +| 14 | | | | | -j | -1 | +| 15 | | | | | +j | j | +| 16 | | | | | -1 | -j | +| 17 | | | | | | -j | +| 18 | | | | | | -j | +| 19 | | | | | | 1 | +| 20 | | | | | | j | +| 21 | | | | | | -1 | +| 22 | | | | | | -j | +| 23 | | | | | | -j | +| 24 | | | | | | -j | +| 25 | | | | | | -1 | +| 26 | | | | | | -1 | +| 27 | | | | | | j | +| 28 | | | | | | -1 | +| 29 | | | | | | -j | +| 30 | | | | | | 1 | +| 31 | | | | | | -1 | +| 32 | | | | | | -1 | + +NOTE: the multiplier $w_{Q=32}^{(k)}$ may only be applied in the 7.68Mcps TDD option. + +If the UE autonomously changes the SF, as described in [7], it shall always use the multiplier associated with the channelisation code allocated by higher layers. + +## 6.4 Scrambling codes for the 3.84Mcps and 1.28Mcps options + +The spreading of data by a real valued channelisation code $c^{(k)}$ of length $Q_k$ is followed by a cell specific complex scrambling sequence $\underline{v} = (\underline{v}_1, \underline{v}_2, \dots, \underline{v}_{16})$ . The elements $\underline{v}_i; i = 1, \dots, 16$ of the complex valued scrambling codes shall be taken from the complex set + +$$\underline{V}_v = \{1, j, -1, -j\} \tag{4}$$ + +In equation 4 the letter j denotes the imaginary unit. A complex scrambling code $\underline{v}$ is generated from the binary scrambling codes $\mathbf{v} = (v_1, v_2, \dots, v_{16})$ of length 16 shown in Annex A. The relation between the elements $\underline{v}$ and $\mathbf{v}$ is given by: + +$$\underline{v}_i = (j)^i \cdot v_i \quad v_i \in \{1, -1\}, i = 1, \dots, 16 \tag{5}$$ + +Hence, the elements $\underline{v}_i$ of the complex scrambling code $\underline{v}$ are alternating real and imaginary. + +The length matching is obtained by concatenating $Q_{MAX}/Q_k$ spread words before the scrambling. The scheme is illustrated in figure 2 and is described in more detail in subclause 6.5. + +![Flowchart illustrating the spreading of data symbols. The process starts with data symbols d_1^{(k,i)}, d_2^{(k,i)}, ..., d_{Q_{MAX}/Q_k}^{(k,i)}. These are followed by 'Weighting of each data symbol by multiplier w_Q^{(k)}'. Then 'Spreading of each weighted data symbol by channelisation code c^{(k)}'. The result is a sequence of spread symbols: w_Q^{(k)} \cdot d_1^{(k,i)} \cdot (c_1^{(k,i)}, c_2^{(k,i)}, ..., c_{Q_k}^{(k,i)}), w_Q^{(k)} \cdot d_2^{(k,i)} \cdot (c_1^{(k,i)}, c_2^{(k,i)}, ..., c_{Q_k}^{(k,i)}), ..., w_Q^{(k)} \cdot d_{Q_{MAX}/Q_k}^{(k,i)} \cdot (c_1^{(k,i)}, c_2^{(k,i)}, ..., c_{Q_k}^{(k,i)}). This is followed by 'Chip by chip multiplication by scrambling code \underline{v}'. The final output is 'Spread and scrambled data' with elements \underline{V}_1, \underline{V}_2, ..., \underline{V}_{Q_k}, \underline{V}_{Q_k+1}, ..., \underline{V}_{2Q_k}, ..., \underline{V}_{Q_{MAX}-Q_k+1}, ..., \underline{V}_{Q_{MAX}}.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +Flowchart illustrating the spreading of data symbols. The process starts with data symbols d\_1^{(k,i)}, d\_2^{(k,i)}, ..., d\_{Q\_{MAX}/Q\_k}^{(k,i)}. These are followed by 'Weighting of each data symbol by multiplier w\_Q^{(k)}'. Then 'Spreading of each weighted data symbol by channelisation code c^{(k)}'. The result is a sequence of spread symbols: w\_Q^{(k)} \cdot d\_1^{(k,i)} \cdot (c\_1^{(k,i)}, c\_2^{(k,i)}, ..., c\_{Q\_k}^{(k,i)}), w\_Q^{(k)} \cdot d\_2^{(k,i)} \cdot (c\_1^{(k,i)}, c\_2^{(k,i)}, ..., c\_{Q\_k}^{(k,i)}), ..., w\_Q^{(k)} \cdot d\_{Q\_{MAX}/Q\_k}^{(k,i)} \cdot (c\_1^{(k,i)}, c\_2^{(k,i)}, ..., c\_{Q\_k}^{(k,i)}). This is followed by 'Chip by chip multiplication by scrambling code \underline{v}'. The final output is 'Spread and scrambled data' with elements \underline{V}\_1, \underline{V}\_2, ..., \underline{V}\_{Q\_k}, \underline{V}\_{Q\_k+1}, ..., \underline{V}\_{2Q\_k}, ..., \underline{V}\_{Q\_{MAX}-Q\_k+1}, ..., \underline{V}\_{Q\_{MAX}}. + +Figure 2: Spreading of data symbols + +## 6.4a Scrambling codes for the 7.68Mcps option + +The spreading of data by a real valued channelisation code $\mathbf{c}^{(k)}$ of length $Q_k$ is followed by a cell specific complex scrambling sequence $\underline{v} = (\underline{v}_1, \underline{v}_2, \dots, \underline{v}_{32})$ . The elements $\underline{v}_i; i = 1, \dots, 32$ of the complex valued scrambling codes shall be taken from the complex set + +$$\underline{V}_v = \{1, j, -1, -j\} \quad (4a)$$ + +In equation 4a the letter $j$ denotes the imaginary unit. A complex scrambling code $\underline{V}$ is generated from the binary scrambling codes $v = (v_1, v_2, \dots, v_{32})$ of length 32 that are generated according to the method described in section 6.4a.1. + +The relation between the elements $\underline{V}$ and $v$ is given by: + +$$\underline{v}_i = (j)^i \cdot v_i \quad v_i \in \{1, -1\}, \quad i = 1, \dots, 32 \quad (5a)$$ + +Hence, the elements $\underline{V}_i$ of the complex scrambling code $\underline{V}$ are alternating real and imaginary. + +The length matching is obtained by concatenating $Q_{MAX}/Q_k$ spread words before the scrambling. The scheme is illustrated in figure 2 and is described in more detail in subclause 6.5. + +### 6.4a.1 Generation of binary scrambling codes + +The binary scrambling code, $c_{7.68}^n$ , for cell parameter $n$ in the 7.68Mcps TDD option is formed from the concatenation of the binary scrambling codes $c_{3.84}^n$ and $c_{3.84}^{(n+2) \bmod 128}$ shown in Annex A: + +$$v = (v_1, v_2, \dots, v_{32}) = c_{7.68}^n = \{c_{3.84}^n, c_{3.84}^{(n+2) \bmod 128}\}$$ + +## 6.5 Spread signal of data symbols and data blocks + +The combination of the user specific channelisation and cell specific scrambling codes can be seen as a user and cell specific spreading code $\mathbf{s}^{(k)} = (s_p^{(k)})$ with + +$$s_p^{(k)} = c_{1+[(p-1) \bmod Q_k]}^{(k)} \cdot \mathcal{V}_{1+[(p-1) \bmod Q_{MAX}]} , k=1, \dots, K_{Code}, p=1, \dots, N_k Q_k.$$ + +With the root raised cosine chip impulse filter $Cr_0(t)$ the transmitted signal belonging to the data block $\mathbf{d}^{(k,1)}$ of equation 1 transmitted before the midamble is + +$$d^{(k,1)}(t) = \sum_{n=1}^{N_k} d_n^{(k,1)} w_{Q_k}^{(k)} \sum_{q=1}^{Q_k} s_{(n-1)Q_k+q}^{(k)} \cdot Cr_0(t - (q-1)T_c - (n-1)Q_k T_c) \quad (6)$$ + +and for the data block $\mathbf{d}^{(k,2)}$ of equation 1 transmitted after the midamble + +$$d^{(k,2)}(t) = \sum_{n=1}^{N_k} d_n^{(k,2)} w_{Q_k}^{(k)} \sum_{q=1}^{Q_k} s_{(n-1)Q_k+q}^{(k)} \cdot Cr_0(t - (q-1)T_c - (n-1)Q_k T_c - N_k Q_k T_c - L_m T_c) \quad (7)$$ + +where $L_m$ is the number of midamble chips. + +## 6.6 Modulation for the 3.84Mcps and 7.68Mcps options + +The complex-valued chip sequence is modulated as shown in figure 3. + +![Block diagram of modulation for complex valued chip sequences. A complex-valued chip sequence S is split into its real part Re{S} and imaginary part Im{S}. Re{S} is pulse-shaped and then multiplied by cos(ωt). Im{S} is pulse-shaped and then multiplied by -sin(ωt). The results are summed to produce the final output.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg) + +``` + +graph LR + S[Complex-valued chip sequence S] --> Split[Split real & imag. parts] + Split -- Re{S} --> Pulse1[Pulse-shaping] + Split -- Im{S} --> Pulse2[Pulse-shaping] + Pulse1 --> Mult1((x)) + cos_omega_t[cos(ωt)] --> Mult1 + Pulse2 --> Mult2((x)) + minus_sin_omega_t[-sin(ωt)] --> Mult2 + Mult1 --> Add((+)) + Mult2 --> Add + Add --> Output[ ] + +``` + +Block diagram of modulation for complex valued chip sequences. A complex-valued chip sequence S is split into its real part Re{S} and imaginary part Im{S}. Re{S} is pulse-shaped and then multiplied by cos(ωt). Im{S} is pulse-shaped and then multiplied by -sin(ωt). The results are summed to produce the final output. + +Figure 3: Modulation of complex valued chip sequences + +The pulse-shaping characteristics are described in [9] and [10]. + +### 6.6.1 Combination of physical channels in uplink + +Figure 4 illustrates the principle of combination of two different physical uplink channels within one timeslot. In the case of E-PUCH, only a single uplink physical channel is transmitted per timeslot and the procedures of subclause 6.6.1a shall instead apply). + +The DPCHs to be combined belong to same CCTrCH, did undergo spreading as described in sections before and are thus represented by complex-valued sequences. First, the amplitude of all DPCHs is adjusted according to UL open loop power control as described in [10]. Each DPCH is then separately weighted by a weight factor $\gamma_i$ and combined using complex addition. After combination of Physical Channels the gain factor $\beta_j$ is applied, depending on the actual TFC as described in [10]. + +In case of different CCTrCH, principle shown in Figure 4 applies to each CCTrCH separately. + +![Figure 4: Combination of different physical channels in uplink. The diagram shows two input channels labeled 'Different UL DPCH'. Each input passes through a multiplier (circle with X) labeled 'Power Setting'. The outputs of these multipliers then pass through another multiplier (circle with X) labeled with weight factors gamma_1 and gamma_2 respectively. The outputs of these second multipliers are then summed in a block labeled with the summation symbol Sigma. The output of the summation block is then multiplied (circle with X) by a factor beta_j. The final output is labeled '(point S in Figure 3)'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4: Combination of different physical channels in uplink. The diagram shows two input channels labeled 'Different UL DPCH'. Each input passes through a multiplier (circle with X) labeled 'Power Setting'. The outputs of these multipliers then pass through another multiplier (circle with X) labeled with weight factors gamma\_1 and gamma\_2 respectively. The outputs of these second multipliers are then summed in a block labeled with the summation symbol Sigma. The output of the summation block is then multiplied (circle with X) by a factor beta\_j. The final output is labeled '(point S in Figure 3)'. + +**Figure 4: Combination of different physical channels in uplink** + +The values of weight factors $\gamma_i$ are depending on the spreading factor SF of the corresponding DPCH: + +| SF of DPCH i | $\gamma_i$ | +|-------------------------|--------------| +| 32 | $\sqrt{2}/8$ | +| 16 | $1/4$ | +| 8 | $\sqrt{2}/4$ | +| 4 | $1/2$ | +| 2 | $\sqrt{2}/2$ | +| 1 | 1 | + +NOTE: in the above table, SF = 32 is only supported in the 7.68Mcps TDD option. + +In the case that $\beta_j$ (corresponding to the $j$ -th TFC) has been explicitly signalled to the UE, the possible values that $\beta_j$ can assume are listed in the table below. In the case that $\beta_j$ has been calculated by the UE from a reference TFC, $\beta_j$ shall not be restricted to the quantised values. + +| Signalling value for $\beta_j$ | Quantized value $\beta_j$ | +|--------------------------------|---------------------------| +| 15 | $16/8$ | +| 14 | $15/8$ | +| 13 | $14/8$ | +| 12 | $13/8$ | +| 11 | $12/8$ | +| 10 | $11/8$ | +| 9 | $10/8$ | +| 8 | $9/8$ | +| 7 | $8/8$ | +| 6 | $7/8$ | +| 5 | $6/8$ | +| 4 | $5/8$ | +| 3 | $4/8$ | +| 2 | $3/8$ | +| 1 | $2/8$ | +| 0 | $1/8$ | + +#### 6.6.1a Physical channel transmission for E-PUCH + +Figure 4a illustrates the principle of E-PUCH transmission. In a timeslot in which an E-PUCH is transmitted by a UE, no other physical channels may be transmitted by the same UE. + +The amplitude of the E-PUCH is adjusted in accordance with the E-PUCH UL power control procedure described in [12]. The power setting procedure of [12] includes appropriate power adjustment factors for the E-PUCH spreading factor and for the E-TFC selected by higher layers [13].□□ Quantisation of the gain factor used to set the E-PUCH power is not specified. + +![Figure 4a: Combination of different physical channels in uplink. The diagram shows an E-PUCH signal entering a multiplier (circle with an X). A 'power setting' signal is input to the multiplier from below. The output of the multiplier is labeled '(point S in Figure 3)'.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +Figure 4a: Combination of different physical channels in uplink. The diagram shows an E-PUCH signal entering a multiplier (circle with an X). A 'power setting' signal is input to the multiplier from below. The output of the multiplier is labeled '(point S in Figure 3)'. + +**Figure 4a: Combination of different physical channels in uplink** + +### 6.6.2 Combination of physical channels in downlink + +Figure 5 illustrates how different physical downlink channels are combined within one timeslot. Each complex-valued spread channel is separately weighted by a weight factor $G_i$ . If a timeslot contains the SCH, the complex-valued SCH, as described in [7] is separately weighted by a weight factor $G_{SCH}$ . All downlink physical channels are then combined using complex addition. + +![Figure 5: Combination of different physical channels in downlink in case of SCH timeslot. The diagram shows multiple 'Different downlink Physical channels' entering multipliers. The first two are labeled with weight factors G1 and G2. The outputs of these multipliers are summed in a block labeled with the Greek letter Sigma (Σ). The output of this summation block is then combined with an SCH signal. The SCH signal enters a multiplier with weight factor GSCH. The outputs of the SCH multiplier and the previous summation block are summed in another block labeled with the Greek letter Sigma (Σ). The final output is labeled '(point S in Figure 3)'.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure 5: Combination of different physical channels in downlink in case of SCH timeslot. The diagram shows multiple 'Different downlink Physical channels' entering multipliers. The first two are labeled with weight factors G1 and G2. The outputs of these multipliers are summed in a block labeled with the Greek letter Sigma (Σ). The output of this summation block is then combined with an SCH signal. The SCH signal enters a multiplier with weight factor GSCH. The outputs of the SCH multiplier and the previous summation block are summed in another block labeled with the Greek letter Sigma (Σ). The final output is labeled '(point S in Figure 3)'. + +**Figure 5: Combination of different physical channels in downlink in case of SCH timeslot** + +### 6.6.3 Combination of signature sequences for E-HICH + +Multiple HARQ acknowledgement indicator signature sequences may be mapped onto the same channelisation code. Each signature sequence (described in [8]) is first subjected to QPSK modulation as described in subclause 5.2.1.1 to form the output sequence $d_{n,h}^{(k,i)}$ for the $h^{th}$ indicator sequence, where $n=1,2,\dots,N_k$ and $i=1,2$ . Code $k$ is the same value for all signature sequences mapped to the same channelisation code. + +When multiple signature sequences are to be transmitted on the same channelisation code, the following procedure shall be applied prior to spreading. + +Each QPSK-modulated stream $d_{n,h}^{(k,i)}$ is amplitude-weighted by a factor $g_h$ according to the desired signature sequence power. A summation is then performed across all $H$ signature sequences mapped to the same channelisation code as shown in figure 5a. The output of the summation block is the sequence: + +$$e_n^{(k,i)} = \sum_{h=1}^H g_h d_{n,h}^{(k,i)} \quad (n = 1, 2, \dots, N_k) \text{ and } (i=1,2) \quad (8)$$ + +![Figure 5a: Combination of HARQ acknowledgement indicator sequences prior to spreading. The diagram shows multiple input sequences d_{n,1}^{(k,i)}, d_{n,2}^{(k,i)}, ..., d_{n,H}^{(k,i)} being multiplied by gain factors g_1, g_2, ..., g_H respectively. The results are then summed together in a block labeled with the summation symbol Σ. The output is a sequence e_n^{(k,i)} for n = 1...N_k and i = 1,2.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Detailed description: A block diagram showing the combination of HARQ indicator sequences. On the left, there are three horizontal paths shown (with vertical dots indicating more in between). The first path has input $d_{n,1}^{(k,i)}$ entering a multiplier with gain $g_1$ . The second path has input $d_{n,2}^{(k,i)}$ entering a multiplier with gain $g_2$ . The bottom path has input $d_{n,H}^{(k,i)}$ entering a multiplier with gain $g_H$ . All multiplier outputs feed into a large vertical rectangular block containing a summation symbol $\Sigma$ . A single output arrow emerges from the right of the summation block, labeled $e_n^{(k,i)} \{n = 1...N_k \quad i = 1,2\}$ . + +Figure 5a: Combination of HARQ acknowledgement indicator sequences prior to spreading. The diagram shows multiple input sequences d\_{n,1}^{(k,i)}, d\_{n,2}^{(k,i)}, ..., d\_{n,H}^{(k,i)} being multiplied by gain factors g\_1, g\_2, ..., g\_H respectively. The results are then summed together in a block labeled with the summation symbol Σ. The output is a sequence e\_n^{(k,i)} for n = 1...N\_k and i = 1,2. + +**Figure 5a: Combination of HARQ acknowledgement indicator sequences prior to spreading** + +The sequence $e_n^{(k,i)}$ is mapped to a single channelisation code and subject to spreading at SF=16 (for 3.84Mcps) and at SF=32 (for 7.68Mcps) in accordance with the general method of subclause 6. + +## 6.7 Modulation for the 1.28 Mcps option + +The complex-valued chip sequence in uplink or downlink on one carrier within one timeslot is modulated as shown in figure 6. + +![Figure 6: Modulation of complex valued chip sequences. The diagram shows a complex-valued chip sequence S being split into its real part Re{S} and imaginary part Im{S}. Each part is then processed by a 'Pulse-shaping' block. The output of the real part is multiplied by cos(ωt), and the output of the imaginary part is multiplied by -sin(ωt). The results are then summed together to produce the final modulated signal.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +Detailed description: A block diagram for modulation. It starts with an input 'Complex-valued chip sequence' labeled $S$ . This enters a block labeled 'Split real & imag. parts'. Two outputs emerge: the top one is $Re\{S\}$ and the bottom one is $Im\{S\}$ . Each signal enters its own 'Pulse-shaping' block. The output of the top pulse-shaping block enters a multiplier with $\cos(\omega t)$ . The output of the bottom pulse-shaping block enters a multiplier with $-\sin(\omega t)$ . The outputs of these two multipliers are combined in a summation block (circle with a $+$ sign) to produce the final output signal. + +Figure 6: Modulation of complex valued chip sequences. The diagram shows a complex-valued chip sequence S being split into its real part Re{S} and imaginary part Im{S}. Each part is then processed by a 'Pulse-shaping' block. The output of the real part is multiplied by cos(ωt), and the output of the imaginary part is multiplied by -sin(ωt). The results are then summed together to produce the final modulated signal. + +**Figure 6: Modulation of complex valued chip sequences** + +The pulse-shaping characteristics are described in [9] and [10]. + +### 6.7.1 Combination of physical channels in uplink + +The principle of combination of two different physical uplink channels within one timeslot is the same as in the 3.84 Mcps TDD cf. [6.6.1 Combination of physical channels in uplink] In the case of E-PUCH, the procedures of subclause 6.7.1a shall instead apply). + +#### 6.7.1a Physical channel transmission for E-PUCH + +Figure 6a illustrates the principle of E-PUCH transmission when one uplink physical channel is transmitted. + +The amplitude of the E-PUCH is adjusted in accordance with the E-PUCH UL power control procedure described in [12]. The power setting procedure of [12] includes appropriate power adjustment factors for the E-PUCH spreading factor and for the E-TFC selected by higher layers [13]. □ □ Quantisation of the gain factor used to set the E-PUCH power is not specified. + +![Diagram of uplink channel combination](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the combination of physical channels in the uplink. An input signal labeled 'E-PUCH' enters a circular node with an 'X' from the left. A vertical arrow labeled 'power setting' points upwards into this node. An output signal exits the node to the right, with a label above it reading '(point S in Figure 3)'. + +Diagram of uplink channel combination + +Figure 6a: Combination of different physical channels in uplink + +### 6.7.2 Combination of physical channels in downlink + +Figure 7 illustrates how different physical downlink channels are combined within one timeslot. Each spread channel is separately weighted by a weight factor $G_i$ . All downlink physical channels are then combined using complex addition. + +![Figure 7: Combination of different physical channels in downlink. The diagram shows multiple input streams labeled 'Different downlink Physical channels' entering a summation block (Σ). Each input stream is first multiplied by a gain factor G1, G2, etc. The output of the summation block is labeled '(point S in Figure 6)'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 7: Combination of different physical channels in downlink. The diagram shows multiple input streams labeled 'Different downlink Physical channels' entering a summation block (Σ). Each input stream is first multiplied by a gain factor G1, G2, etc. The output of the summation block is labeled '(point S in Figure 6)'. + +**Figure 7: Combination of different physical channels in downlink** + +### 6.7.3 Combination of signature sequences for Scheduled E-HICH + +For Scheduled E-HICH, every scheduled user is assigned one signature sequence which is related to the E-DCH resources allocated by Node-B to indicate ACK/NACK. But for the user configured in MU-MIMO mode by higher layers, in case the special default midamble allocation scheme is taken, the signature sequence allocated to the user is related to both the E-DCH resources allocated by Node-B and the variable "offset" which is determined by the special default midamble pattern indicator [7] signalled on E-AGCH. Multiple users' HARQ acknowledgement indicator signature sequences may be mapped onto the same channelisation code. Each signature sequence (described in [8]) is first subjected to QPSK modulation as described in subclause 5.2.1.1 to form the output sequence $d_{n,h}^{(k,i)}$ for the $h^{th}$ indicator sequence, where $n=1,2,\dots,N_k$ and $i=1,2$ . Code $k$ is the same value for all signature sequences mapped to the same channelisation code. + +When multiple signature sequences are to be transmitted on the same channelisation code, the following procedure shall be applied prior to spreading. + +Each QPSK-modulated stream $d_{n,h}^{(k,i)}$ is amplitude-weighted by a factor $g_h$ according to the desired signature sequence power. Each E-HICH physical channel may carry ACK/NACK signature sequence(s) for one UE or multiple UEs decided by Node-B. A summation is then performed across $M$ signature sequences mapped to the same channelisation code as shown in figure 8. The output of the summation block is the sequence: + +$$e_n^{(k,i)} = \sum_{h=1}^M g_h d_{n,h}^{(k,i)} \quad (n = 1, 2, \dots, N_k) \text{ and } (i=1, 2) \quad (9)$$ + +![Figure 8: Combination of HARQ acknowledgement indicator sequences prior to spreading for Scheduled E-HICH. The diagram shows multiple input streams labeled d_{n,1}^{(k,i)}, d_{n,2}^{(k,i)}, ..., d_{n,M}^{(k,i)} entering a summation block (Σ). Each input stream is first multiplied by a gain factor g1, g2, ..., gM. The output of the summation block is labeled e_n^{(k,i)} {n = 1...N_k, i = 1,2}.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +Figure 8: Combination of HARQ acknowledgement indicator sequences prior to spreading for Scheduled E-HICH. The diagram shows multiple input streams labeled d\_{n,1}^{(k,i)}, d\_{n,2}^{(k,i)}, ..., d\_{n,M}^{(k,i)} entering a summation block (Σ). Each input stream is first multiplied by a gain factor g1, g2, ..., gM. The output of the summation block is labeled e\_n^{(k,i)} {n = 1...N\_k, i = 1,2}. + +**Figure 8: Combination of HARQ acknowledgement indicator sequences prior to spreading for Scheduled E-HICH** + +The sequence $e_n^{(k,i)}$ is mapped to a single channelisation code and subject to spreading at SF=16 in accordance with the general method of subclause 6. + +#### 6.7.3a Combination of signature sequences for Non-Scheduled E-HICH + +For Non-Scheduled E-HICH, the 80 signature sequences are divided into 20 groups while each group includes 4 sequences. Every non-scheduled user is assigned one group by higher layer, from that two sequences are selected to indicate ACK/NACK and TPC/SS command. Multiple users' signature sequences may be mapped onto the same channelisation code. Each user's two signature sequences (described in [8]) are first subjected to QPSK modulation as described in subclause 5.2.1.1 to form the two output sequences $d_{n,h_1}^{(k,i)}$ and $d_{n,h_2}^{(k,i)}$ for the $h^{\text{th}}$ user, where $n=1,2,\dots,N_k$ and $i=1,2$ . Code $k$ is the same value for all signature sequences mapped to the same channelisation code. + +When multiple users' signature sequences are to be transmitted on the same channelisation code, the following procedure shall be applied prior to spreading. + +Firstly, each user's QPSK-modulated stream $d_{n,h_2}^{(k,i)}$ corresponding to TPC/SS signature sequence is amplitude-weighted by a factor $f_h$ and added to the QPSK-modulated stream $d_{n,h_1}^{(k,i)}$ corresponding to ACK/NACK signature sequence; Secondly, each user's combined stream $d_{n,h}^{(k,i)}$ is amplitude-weighted by a factor $g_h$ according to the desired user power. A summation is then performed across $M$ users' signature sequences mapped to the same channelisation code as shown in figure 8a. The output of the summation block is the sequence: + +$$e_n^{(k,i)} = \sum_{h=1}^M g_h d_{n,h}^{(k,i)} \quad (n = 1, 2, \dots, N_k) \text{ and } (i=1, 2) \quad (9a)$$ + +![Figure 8a: Combination of ACK/NACK and TPC/SS sequences prior to spreading for Non-Scheduled E-HICH. The diagram shows M parallel processing paths for users h=1 to M. Each path takes two input sequences, d_{n,h_1}^{(k,i)} and d_{n,h_2}^{(k,i)}, where d_{n,h_2}^{(k,i)} is first multiplied by a factor f_h and then added to d_{n,h_1}^{(k,i)}. The result is then multiplied by a factor g_h. All M resulting sequences are then summed together in a summation block (Σ) to produce the final output sequence e_n^{(k,i)} for n = 1, 2, ..., N_k and i = 1, 2.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +Figure 8a: Combination of ACK/NACK and TPC/SS sequences prior to spreading for Non-Scheduled E-HICH. The diagram shows M parallel processing paths for users h=1 to M. Each path takes two input sequences, d\_{n,h\_1}^{(k,i)} and d\_{n,h\_2}^{(k,i)}, where d\_{n,h\_2}^{(k,i)} is first multiplied by a factor f\_h and then added to d\_{n,h\_1}^{(k,i)}. The result is then multiplied by a factor g\_h. All M resulting sequences are then summed together in a summation block (Σ) to produce the final output sequence e\_n^{(k,i)} for n = 1, 2, ..., N\_k and i = 1, 2. + +**Figure 8a: Combination of ACK/NACK and TPC/SS sequences prior to spreading for Non-Scheduled E-HICH** + +The sequence $e_n^{(k,i)}$ is mapped to a single channelisation code and subject to spreading at SF=16 in accordance with the general method of subclause 6. + +## 6.8 Spreading modulation for the 3.84 Mcps MBSFN IMB option + +### 6.8.1 Spreading + +The spreading operation includes a modulation mapper stage successively followed by a channelisation stage, an IQ combining stage and a scrambling stage as illustrated by figure 9. + +Modulation mapping is described in subclause 5.2.3. + +For all physical channels, except for the Synchronisation Channel (SCH), the I and Q branches shall be spread to the chip rate by the same real-valued channelisation code $C_{ch,SF,m}$ , i.e. the output for each input symbol on the I and the Q + +branches shall be a sequence of SF chips corresponding to the channelisation code chip sequence multiplied by the real-valued symbol. The channelisation code sequence shall be aligned in time with the symbol boundary. The real-valued chip sequence on the Q-branch shall be complex multiplied with $j$ and summed with the corresponding real-valued chip sequence on the I-branch, resulting in a single complex-valued chip sequence $I+jQ$ . + +The sequence of complex-valued chips output from the spreading stage shall be scrambled (complex chip-wise multiplication) by a complex-valued scrambling code $S_{dl,n}$ . + +![Figure 9: Spreading for all downlink physical channels except SCH. The diagram shows a signal flow from left to right. It starts with 'downlink physical channel' entering a block labeled 'S' over 'P'. The output goes to a 'Modulation Mapper' block. From the mapper, the signal splits into two branches: an I-branch and a Q-branch. In the I-branch, the signal is multiplied by a chip sequence C_ch,SF,m. In the Q-branch, the signal is multiplied by a chip sequence, and then the result is multiplied by j. The outputs of these two branches are summed at a block labeled '+', resulting in I+jQ. This combined signal is then multiplied by a scrambling code S_dl,n to produce the final output S.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +Figure 9: Spreading for all downlink physical channels except SCH. The diagram shows a signal flow from left to right. It starts with 'downlink physical channel' entering a block labeled 'S' over 'P'. The output goes to a 'Modulation Mapper' block. From the mapper, the signal splits into two branches: an I-branch and a Q-branch. In the I-branch, the signal is multiplied by a chip sequence C\_ch,SF,m. In the Q-branch, the signal is multiplied by a chip sequence, and then the result is multiplied by j. The outputs of these two branches are summed at a block labeled '+', resulting in I+jQ. This combined signal is then multiplied by a scrambling code S\_dl,n to produce the final output S. + +**Figure 9: Spreading for all downlink physical channels except SCH** + +All complex-valued spread channels are separately weighted and then combined, together with separately weighted Primary SCH and Secondary SCH, into one complex-valued chip sequence by using complex addition, as illustrated by figure 9 in subclause 5.1.5 of [4]. The resulting signal is modulated prior to transmission as described in subclause 6A.3. + +### 6.8.2 Code generation and allocation + +#### 6.8.2.1 Channelisation codes + +The channelisation codes are OVFS codes that preserve the orthogonality between downlink channels of different rates and spreading factors. The channelisation codes are defined in figure 4 of subclause 4.3.1.1 of [3] and are uniquely described as $C_{ch,SF,m}$ , where SF is the spreading factor of the code and $m$ is the code number, $0 \leq m \leq SF-1$ . + +The following applies to the MBSFN IMB physical channels: + +- The channelisation code for the Primary CPICH is fixed to $C_{ch,256,0}$ ; +- The channelisation code for the Primary CCPCH is fixed to $C_{ch,256,1}$ ; +- The channelisation codes for the Secondary CCPCH frame type 1 and MICH are assigned by UTRAN from the codes $C_{ch,256,m}$ $m \in \{2,3, \dots, 15\}$ ; +- The channelisation codes for the Secondary CCPCH frame type 2 are assigned by UTRAN from the codes $C_{ch,16,m}$ $m \in \{1,2, \dots, 15\}$ ; +- The channelisation codes for the T-CPICH are $C_{ch,16,1}, C_{ch,16,2}, \dots, C_{ch,16,15}$ . + +#### 6.8.2.2 Scrambling codes + +The scrambling codes shall be generated as described in subclause 5.2.2 in [4]. For MBSFN IMB operation, only primary scrambling codes shall be used. Out of all possible primary scrambling codes with index $n=16*i$ where $i=0\dots511$ as defined in [4] the following subset shall be supported for the MBSFN option: $n \in \{0, 128, 256, 384, 512, 640, 768, 896\}$ . No two members of set $n$ belong to the same scrambling code group. + +Cells that belong to a certain MBSFN IMB cluster shall use the same primary scrambling code. + +The primary scrambling code for all physical channels shall be applied aligned with the start of the Primary CCPCH frame. This also applies in the case of a Secondary CCPCH frame type 2 associated with the $k^{\text{th}}$ sub-frame of a radio frame ( $k = 0,1,\dots,4$ ) [7], such that the start of the scrambling code is always aligned with the start of sub-frame $k = 0$ . + +### 6.8.3 Modulation + +Modulation of the complex-valued chip sequence generated by the spreading process is performed according to sub-clause 6.6. The modulation chip rate is 3.84 Mcps. + +# 7 Synchronisation codes for the 3.84 Mcps option + +Sub-clauses 7.1, 7.2 and 7.3 do not apply for 3.84 Mcps MBSFN IMB operation. Synchronisation codes for 3.84 Mcps MBSFN IMB are described in sub-clause 7.4. + +## 7.1 Code Generation + +The primary synchronisation code (PSC), $C_p$ , is constructed as a so-called generalised hierarchical Golay sequence. The PSC is furthermore chosen to have good aperiodic auto correlation properties. + +Define $a = \langle x_1, x_2, x_3, \dots, x_{16} \rangle = \langle 1, 1, 1, 1, 1, 1, -1, -1, 1, -1, 1, -1, 1, -1, -1, 1 \rangle$ + +The PSC is generated by repeating the sequence 'a' modulated by a Golay complementary sequence and creating a complex-valued sequence with identical real and imaginary components. + +The PSC, $C_p$ , is defined as $C_p = \langle y(0), y(1), y(2), \dots, y(255) \rangle$ + +where $y = (1 + j) \times \langle a, a, a, -a, -a, a, -a, -a, a, a, a, -a, a, -a, a, a \rangle$ + +and the left most index corresponds to the chip transmitted first in time. + +The 12 secondary synchronization codes, $\{C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15}\}$ are complex valued with identical real and imaginary components, and are constructed from the position wise multiplication of a Hadamard sequence and a sequence $z$ , defined as + +$$z = \langle b, b, b, -b, b, b, -b, -b, b, -b, b, -b, -b, -b, -b, -b \rangle, \text{ where}$$ + +$$b = \langle x_1, x_2, x_3, x_4, x_5, x_6, x_7, x_8, -x_9, -x_{10}, -x_{11}, -x_{12}, -x_{13}, -x_{14}, -x_{15}, -x_{16} \rangle$$ + +and $x_1, x_2, x_3, \dots, x_{16}$ are the same as in the definition of the sequence 'a' above. + +The Hadamard sequences are obtained as the rows in a matrix $H_8$ constructed recursively by: + +$$H_0 = (1)$$ + +$$H_k = \begin{pmatrix} H_{k-1} & H_{k-1} \\ H_{k-1} & -H_{k-1} \end{pmatrix}, \quad k \geq 1$$ + +The rows are numbered from the top starting with row 0 (the all ones sequence). + +Denote the $n$ :th Hadamard sequence $h_n$ as a row of $H_8$ numbered from the top, $n = 0, 1, 2, \dots, 255$ , in the sequel. + +Furthermore, let $h_m(l)$ and $z(l)$ denote the $l$ th symbol of the sequence $h_m$ and $z$ , respectively where $l = 0, 1, 2, \dots, 255$ and $l = 0$ corresponds to the leftmost symbol. + +The $i$ :th secondary SCH code word, $C_i$ , $i = 0, 1, 3, 4, 5, 6, 8, 10, 12, 13, 14, 15$ is then defined as + +$$C_i = (1 + j) \times \langle h_m(0) \times z(0), h_m(1) \times z(1), h_m(2) \times z(2), \dots, h_m(255) \times z(255) \rangle,$$ + +where $m = (16 \times i)$ and the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +## 7.2 Code Allocation + +Three secondary SCH codes are QPSK modulated and transmitted in parallel with the primary synchronization code. The QPSK modulation carries the following information: + +- the code group that the base station belongs to (32 code groups:5 bits; Cases 1, 2); +- the position of the frame within an interleaving period of 20 msec (2 frames:1 bit, Cases 1, 2); +- the position of the SCH slot(s) within the frame (2 SCH slots:1 bit, Case 2). + +The modulated secondary SCH codes are also constructed such that their cyclic-shifts are unique, i.e. a non-zero cyclic shift less than 2 (Case 1) and 4 (Case 2) of any of the sequences is not equivalent to some cyclic shift of any other of the sequences. Also, a non-zero cyclic shift less than 2 (Case 1) and 4 (Case 2) of any of the sequences is not equivalent to itself with any other cyclic shift less than 8. The secondary synchronization codes are partitioned into two code sets for Case 1 and four code sets for Case 2. The set is used to provide the following information: + +### Case 1: + +**Table 2: Code Set Allocation for Case 1** + +| Code Set | Code Group | +|----------|------------| +| 1 | 0-15 | +| 2 | 16-31 | + +The code group and frame position information is provided by modulating the secondary codes in the code set. + +### Case 2: + +**Table 3: Code Set Allocation for Case 2** + +| Code Set | Code Group | +|----------|------------| +| 1 | 0-7 | +| 2 | 8-15 | +| 3 | 16-23 | +| 4 | 24-31 | + +The slot timing and frame position information is provided by the comma free property of the code word and the Code group is provided by modulating some of the secondary codes in the code set. + +The following SCH codes are allocated for each code set: + +#### Case 1 + +Code set 1: $C_1, C_3, C_5$ . + +Code set 2: $C_{10}, C_{13}, C_{14}$ . + +#### Case 2 + +Code set 1: $C_1, C_3, C_5$ . + +Code set 2: $C_{10}, C_{13}, C_{14}$ . + +Code set 3: $C_0, C_6, C_{12}$ . + +Code set 4: $C_4, C_8, C_{15}$ . + +The following subclauses 7.2.1 to 7.2.2 refer to the two cases of SCH/P-CCPCH usage as described in [7]. + +Note that in the tables 4 and 5 corresponding to Cases 1 and 2, respectively, Frame 1 implies the frame with an odd SFN and Frame 2 implies the frame with an even SFN. + +### 7.2.1 Code allocation for Case 1 + +**Table 4: Code Allocation for Case 1** + +| Code Group | Code Set | Frame 1 | | | Frame 2 | | | Associated t offset | +|------------|----------|-------------------|-------------------|-----------------|-------------------|-------------------|------------------|--------------------------------| +| 0 | 1 | C 1 | C 3 | C 5 | C 1 | C 3 | -C 5 | t 0 | +| 1 | 1 | C 1 | -C 3 | C 5 | C 1 | -C 3 | -C 5 | t 1 | +| 2 | 1 | -C 1 | C 3 | C 5 | -C 1 | C 3 | -C 5 | t 2 | +| 3 | 1 | -C 1 | -C 3 | C 5 | -C 1 | -C 3 | -C 5 | t 3 | +| 4 | 1 | jC 1 | jC 3 | C 5 | jC 1 | jC 3 | -C 5 | t 4 | +| 5 | 1 | jC 1 | -jC 3 | C 5 | jC 1 | -jC 3 | -C 5 | t 5 | +| 6 | 1 | -jC 1 | jC 3 | C 5 | -jC 1 | jC 3 | -C 5 | t 6 | +| 7 | 1 | -jC 1 | -jC 3 | C 5 | -jC 1 | -jC 3 | -C 5 | t 7 | +| 8 | 1 | jC 1 | jC 5 | C 3 | jC 1 | jC 5 | -C 3 | t 8 | +| 9 | 1 | jC 1 | -jC 5 | C 3 | jC 1 | -jC 5 | -C 3 | t 9 | +| 10 | 1 | -jC 1 | jC 5 | C 3 | -jC 1 | jC 5 | -C 3 | t 10 | +| 11 | 1 | -jC 1 | -jC 5 | C 3 | -jC 1 | -jC 5 | -C 3 | t 11 | +| 12 | 1 | jC 3 | jC 5 | C 1 | jC 3 | jC 5 | -C 1 | t 12 | +| 13 | 1 | jC 3 | -jC 5 | C 1 | jC 3 | -jC 5 | -C 1 | t 13 | +| 14 | 1 | -jC 3 | jC 5 | C 1 | -jC 3 | jC 5 | -C 1 | t 14 | +| 15 | 1 | -jC 3 | -jC 5 | C 1 | -jC 3 | -jC 5 | -C 1 | t 15 | +| 16 | 2 | C 10 | C 13 | C 14 | C 10 | C 13 | -C 14 | t 16 | +| 17 | 2 | C 10 | -C 13 | C 14 | C 10 | -C 13 | -C 14 | t 17 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 20 | 2 | jC 10 | jC 13 | C 14 | jC 10 | jC 13 | -C 14 | t 20 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 24 | 2 | jC 10 | jC 14 | C 13 | jC 10 | jC 14 | -C 13 | t 24 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 2 | -jC 13 | -jC 14 | C 10 | -jC 13 | -jC 14 | -C 10 | t 31 | + +NOTE: The code construction for code groups 0 to 15 using only the SCH codes from code set 1 is shown. The construction for code groups 16 to 31 using the SCH codes from code set 2 is done in the same way. + +### 7.2.2 Code allocation for Case 2 + +Table 5: Code Allocation for Case 2 + +| Code Group | Code Set | Frame 1 | | | | | | Frame 2 | | | | | | Associated $t_{offset}$ | | +|------------|----------|------------------|-------------------|-----------------|------------------|-------------------|------------------|-------------------|-------------------|-----------------|-------------------|-------------------|------------------|-------------------------|--| +| | | Slot k | | | Slot k+8 | | | Slot k | | | Slot k+8 | | | | | +| | | | | | | | | | | | | | | | | +| 0 | 1 | C 1 | C 3 | C 5 | C 1 | C 3 | -C 5 | -C 1 | -C 3 | C 5 | -C 1 | -C 3 | -C 5 | t 0 | | +| 1 | 1 | C 1 | -C 3 | C 5 | C 1 | -C 3 | -C 5 | -C 1 | C 3 | C 5 | -C 1 | C 3 | -C 5 | t 1 | | +| 2 | 1 | jC 1 | jC 3 | C 5 | jC 1 | jC 3 | -C 5 | -jC 1 | -jC 3 | C 5 | -jC 1 | -jC 3 | -C 5 | t 2 | | +| 3 | 1 | jC 1 | -jC 3 | C 5 | jC 1 | -jC 3 | -C 5 | -jC 1 | jC 3 | C 5 | -jC 1 | jC 3 | -C 5 | t 3 | | +| 4 | 1 | jC 1 | jC 5 | C 3 | jC 1 | jC 5 | -C 3 | -jC 1 | -jC 5 | C 3 | -jC 1 | -jC 5 | -C 3 | t 4 | | +| 5 | 1 | jC 1 | -jC 5 | C 3 | jC 1 | -jC 5 | -C 3 | -jC 1 | jC 5 | C 3 | -jC 1 | jC 5 | -C 3 | t 5 | | +| 6 | 1 | jC 3 | jC 5 | C 1 | jC 3 | jC 5 | -C 1 | -jC 3 | -jC 5 | C 1 | -jC 3 | -jC 5 | -C 1 | t 6 | | +| 7 | 1 | jC 3 | -jC 5 | C 1 | jC 3 | -jC 5 | -C 1 | -jC 3 | jC 5 | C 1 | -jC 3 | jC 5 | -C 1 | t 7 | | +| 8 | 2 | C 10 | C 13 | C 14 | C 10 | C 13 | -C 14 | -C 10 | -C 13 | C 14 | -C 10 | -C 13 | -C 14 | t 8 | | +| 9 | 2 | C 10 | -C 13 | C 14 | C 10 | -C 13 | -C 14 | -C 10 | C 13 | C 14 | -C 10 | C 13 | -C 14 | t 9 | | +| 10 | 2 | jC 10 | jC 13 | C 14 | jC 10 | jC 13 | -C 14 | -jC 10 | -jC 13 | C 14 | -jC 10 | -jC 13 | -C 14 | t 10 | | +| 11 | 2 | jC 10 | -jC 13 | C 14 | jC 10 | -jC 13 | -C 14 | -jC 10 | jC 13 | C 14 | -jC 10 | jC 13 | -C 14 | t 11 | | +| 12 | 2 | jC 10 | jC 14 | C 13 | jC 10 | jC 14 | -C 13 | -jC 10 | -jC 14 | C 13 | -jC 10 | -jC 14 | -C 13 | t 12 | | +| 13 | 2 | jC 10 | -jC 14 | C 13 | jC 10 | -jC 14 | -C 13 | -jC 10 | jC 14 | C 13 | -jC 10 | jC 14 | -C 13 | t 13 | | +| 14 | 2 | jC 13 | jC 14 | C 10 | jC 13 | jC 14 | -C 10 | -jC 13 | -jC 14 | C 10 | -jC 13 | -jC 14 | -C 10 | t 14 | | +| 15 | 2 | jC 13 | -jC 14 | C 10 | jC 13 | -jC 14 | -C 10 | -jC 13 | jC 14 | C 10 | -jC 13 | jC 14 | -C 10 | t 15 | | +| 16 | 3 | C 0 | C 6 | C 12 | C 0 | C 6 | -C 12 | -C 0 | -C 6 | C 12 | -C 0 | -C 6 | -C 12 | t 16 | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | | +| 23 | 3 | jC 6 | -jC 12 | C 0 | jC 6 | -jC 12 | -C 0 | -jC 6 | jC 12 | C 0 | -jC 6 | jC 12 | -C 0 | t 20 | | +| 24 | 4 | C 4 | C 8 | C 15 | C 4 | C 8 | -C 15 | -C 4 | -C 8 | C 15 | -C 4 | -C 8 | -C 15 | t 24 | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | | +| 31 | 4 | jC 8 | -jC 15 | C 4 | jC 8 | -jC 15 | -C 4 | -jC 8 | jC 15 | C 4 | -jC 8 | jC 15 | -C 4 | t 31 | | + +NOTE: The code construction for code groups 0 to 15 using the SCH codes from code sets 1 and 2 is shown. The construction for code groups 16 to 31 using the SCH codes from code sets 3 and 4 is done in the same way. + +## 7.3 Evaluation of synchronisation codes + +The evaluation of information transmitted in SCH on code group and frame timing is shown in table 6, where the 32 code groups are listed. Each code group is containing 4 specific scrambling codes (cf. subclause 6.4), each scrambling code associated with a specific short and long basic midamble code. + +Each code group is additionally linked to a specific $t_{\text{offset}}$ , thus to a specific frame timing. By using this scheme, the UE can derive the position of the frame border due to the position of the SCH sequence and the knowledge of $t_{\text{offset}}$ . The complete mapping of Code Group to Scrambling Code, Midamble Codes and $t_{\text{offset}}$ is depicted in table 6. + +**Table 6: Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles and $t_{\text{offset}}$** + +| CELL
PARAMETER | Code
Group | Associated Codes | | | Associated $t_{\text{offset}}$ | | | +|-------------------|---------------|--------------------|--------------------------------|---------------------------------|--------------------------------|--|--| +| | | Scrambling
Code | Long Basic
Midamble
Code | Short Basic
Midamble
Code | | | | +| 0 | Group 0 | Code 0 | m PL0 | m SL0 | $t_0$ | | | +| 1 | | Code 1 | m PL1 | m SL1 | | | | +| 2 | | Code 2 | m PL2 | m SL2 | | | | +| 3 | | Code 3 | m PL3 | m SL3 | | | | +| 4 | Group 1 | Code 4 | m PL4 | m SL4 | $t_1$ | | | +| 5 | | Code 5 | m PL5 | m SL5 | | | | +| 6 | | Code 6 | m PL6 | m SL6 | | | | +| 7 | | Code 7 | m PL7 | m SL7 | | | | +| ⋮ | | | | | | | | +| ⋮ | | | | | | | | +| ⋮ | | | | | | | | +| 124 | Group 31 | Code 124 | m PL124 | m SL124 | $t_{31}$ | | | +| 125 | | Code 125 | m PL125 | m SL125 | | | | +| 126 | | Code 126 | m PL126 | m SL126 | | | | +| 127 | | Code 127 | m PL127 | m SL127 | | | | + +For basic midamble codes mP cf. [7], annex A 'Basic Midamble Codes'. + +Each cell shall cycle through two sets of cell parameters in a code group with the cell parameters changing each frame. Table 7 shows how the cell parameters are cycled according to the SFN. + +**Table 7: Alignment of cell parameter cycling and SFN** + +| Initial Cell
Parameter
Assignment | Code Group | Cell Parameter
used when
SFN mod 2 = 0 | Cell Parameter
used when
SFN mod 2 = 1 | | +|-----------------------------------------|------------|----------------------------------------------|----------------------------------------------|--| +| 0 | Group 0 | 0 | 1 | | +| 1 | | 1 | 0 | | +| 2 | | 2 | 3 | | +| 3 | | 3 | 2 | | +| 4 | Group 1 | 4 | 5 | | +| 5 | | 5 | 4 | | +| 6 | | 6 | 7 | | +| 7 | | 7 | 6 | | +| ⋮ | | | | | +| ⋮ | | | | | +| ⋮ | | | | | +| 124 | Group 31 | 124 | 125 | | +| 125 | | 125 | 124 | | +| 126 | | 126 | 127 | | +| 127 | | 127 | 126 | | + +## 7.4 Synchronisation codes for 3.84 Mcps MBSFN IMB + +### 7.4.1 Code generation + +The primary synchronisation code (PSC), $C_{psc}$ , is constructed to be orthogonal to both the primary and secondary SCH codes defined in subclause 7.1. The PSC is furthermore chosen to have good aperiodic auto correlation properties and low aperiodic cross correlations with the primary SCH defined in sub-clause 7.1. + +Define: + +- $a = \langle 1, -1, -1, 1, 1, -1, 1, -1, 1, 1, -1, -1, 1, 1, 1, 1 \rangle$ + +The PSC is generated by repeating the sequence $a$ modulated by a Golay complementary sequence, and creating a complex-valued sequence with identical real and imaginary components. The PSC $C_{psc}$ is defined as: + +- $C_{psc} = (1 + j) \times \langle a, a, -a, a, -a, a, a, a, a, a, -a, a, a, -a, -a, -a \rangle$ ; + +where the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +The 16 secondary synchronization codes, $\{C_{ssc,1}, \dots, C_{ssc,16}\}$ , are complex-valued with identical real and imaginary components, and are constructed from position wise multiplication of a Hadamard sequence and a sequence $z$ , defined as: + +- $z = \langle b, b, b, -b, b, b, -b, -b, b, -b, b, -b, -b, -b, -b, -b \rangle$ , where +- $b = \langle 1, 1, 1, 1, 1, 1, -1, -1, -1, 1, -1, 1, -1, 1, 1, -1 \rangle$ . + +The Hadamard sequences are obtained as the rows in a matrix $H_8$ constructed recursively by: + +$$\begin{aligned} H_0 &= (1) \\ H_k &= \begin{pmatrix} H_{k-1} & H_{k-1} \\ H_{k-1} & -H_{k-1} \end{pmatrix}, k \geq 1 \end{aligned}$$ + +The rows are numbered from the top starting with row 0 (the all ones sequence). + +Denote the $n$ :th Hadamard sequence as a row of $H_8$ numbered from the top, $n = 0, 1, 2, \dots, 255$ , in the sequel. + +Furthermore, let $h_n(i)$ and $z(i)$ denote the $i$ :th symbol of the sequence $h_n$ and $z$ , respectively where $i = 0, 1, 2, \dots, 255$ and $i = 0$ corresponds to the leftmost symbol. + +The $k$ :th secondary synchronization code, $C_{ssc,k}$ , $k = 1, 2, 3, \dots, 16$ is then defined as: + +- $C_{ssc,k} = (1 + j) \times \langle h_m(0) \times z(0), h_m(1) \times z(1), h_m(2) \times z(2), \dots, h_m(255) \times z(255) \rangle$ ; + +where $m = 16 \times (k - 1)$ and the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +### 7.4.2 Code allocation of SSC + +The secondary synchronisation code sequences shall be constructed as described in subclause 5.2.3.2 in [4]. For MBSFN IMB operation, only the first 8 scrambling code groups are utilised. + +# 7A Synchronisation codes for the 7.68 Mcps option + +## 7A.1 Code Generation + +The primary synchronisation code (PSC), $C_p$ , is constructed as a so-called generalised hierarchical Golay sequence. The PSC is furthermore chosen to have good aperiodic auto correlation properties. + +Define $a = \langle x_1, x_2, x_3, \dots, x_{16} \rangle = \langle 1, 1, 1, 1, 1, 1, -1, -1, 1, -1, 1, -1, 1, -1, -1, 1 \rangle$ + +The PSC of length 512 chips is generated by repetition coding and repeating the sequence 'a' modulated by a Golay complementary sequence and creating a complex-valued sequence with identical real and imaginary components. + +The PSC, $C_p$ , is defined as $C_p = \langle y(0), y(0), y(1), y(1), y(2), y(2), \dots, y(255), y(255) \rangle$ + +where $y = (1 + j) \times \langle a, a, a, -a, -a, a, -a, -a, a, a, a, -a, a, -a, a, a \rangle$ + +and the left most index corresponds to the chip transmitted first in time. + +The 12 secondary synchronization codes, $\{C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15}\}$ are complex valued with identical real and imaginary components, and are constructed from repetition coding of the position wise multiplication of a Hadamard sequence and a sequence $z$ , defined as + +$$z = \langle b, b, b, -b, b, b, -b, -b, b, -b, b, -b, -b, -b, -b, -b \rangle, \text{ where}$$ + +$$b = \langle x_1, x_2, x_3, x_4, x_5, x_6, x_7, x_8, -x_9, -x_{10}, -x_{11}, -x_{12}, -x_{13}, -x_{14}, -x_{15}, -x_{16} \rangle$$ + +and $x_1, x_2, x_3, \dots, x_{16}$ are the same as in the definition of the sequence 'a' above. + +The Hadamard sequences are obtained as the rows in a matrix $H_8$ constructed recursively by: + +$$H_0 = (1)$$ + +$$H_k = \begin{pmatrix} H_{k-1} & H_{k-1} \\ H_{k-1} & -H_{k-1} \end{pmatrix}, \quad k \geq 1$$ + +The rows are numbered from the top starting with row 0 (the all ones sequence). + +Denote the $n$ :th Hadamard sequence $h_n$ as a row of $H_8$ numbered from the top, $n = 0, 1, 2, \dots, 255$ , in the sequel. + +Furthermore, let $h_m(l)$ and $z(l)$ denote the $l$ th symbol of the sequence $h_m$ and $z$ , respectively where $l = 0, 1, 2, \dots, 255$ and $l = 0$ corresponds to the leftmost symbol. + +The $i$ :th secondary SCH code word, $C_i$ , $i = 0, 1, 3, 4, 5, 6, 8, 10, 12, 13, 14, 15$ is of length 512 chips and is then defined as + +$$C_i = (1 + j) \times \langle h_m(0) \times z(0), h_m(0) \times z(0), h_m(1) \times z(1), h_m(1) \times z(1), \dots, h_m(255) \times z(255), h_m(255) \times z(255) \rangle,$$ + +where $m = (16 \times i)$ and the leftmost chip in the sequence corresponds to the chip transmitted first in time. + +## 7A.2 Code Allocation + +Three secondary SCH codes are QPSK modulated and transmitted in parallel with the primary synchronization code. The QPSK modulation carries the following information: + +- the code group that the base station belongs to (32 code groups: 5 bits; Cases 1, 2); +- the position of the frame within an interleaving period of 20 msec (2 frames: 1 bit, Cases 1, 2); +- the position of the SCH slot(s) within the frame (2 SCH slots: 1 bit, Case 2). + +The QPSK modulation sequences for the 7.68Mcps TDD option are unique to the modulation sequences for the 3.84Mcps TDD option. + +The modulated secondary SCH codes are also constructed such that their cyclic-shifts are unique, i.e. a non-zero cyclic shift less than 2 (Case 1) and 4 (Case 2) of any of the sequences is not equivalent to some cyclic shift of any other of the sequences. Also, a non-zero cyclic shift less than 2 (Case 1) and 4 (Case 2) of any of the sequences is not equivalent to itself with any other cyclic shift less than 8. The secondary synchronization codes are partitioned into two code sets for Case 1 and four code sets for Case 2. The set is used to provide the following information: + +Case 1: + +**Table 7A: Code Set Allocation for Case 1** + +| Code Set | Code Group | +|-----------------|-------------------| +| 1 | 0-15 | +| 2 | 16-31 | + +The code group and frame position information is provided by modulating the secondary codes in the code set. + +### Case 2: + +**Table 7B: Code Set Allocation for Case 2** + +| Code Set | Code Group | +|-----------------|-------------------| +| 1 | 0-7 | +| 2 | 8-15 | +| 3 | 16-23 | +| 4 | 24-31 | + +The slot timing and frame position information is provided by the comma free property of the code word and the Code group is provided by modulating some of the secondary codes in the code set. + +The following SCH codes are allocated for each code set: + +#### Case 1 + +Code set 1: $C_1, C_3, C_5$ . + +Code set 2: $C_{10}, C_{13}, C_{14}$ . + +#### Case 2 + +Code set 1: $C_1, C_3, C_5$ . + +Code set 2: $C_{10}, C_{13}, C_{14}$ . + +Code set 3: $C_0, C_6, C_{12}$ . + +Code set 4: $C_4, C_8, C_{15}$ . + +The following subclauses 7A.2.1 to 7A.2.2 refer to the two cases of SCH/P-CCPCH usage as described in [7]. + +Note that in the tables 7C and 7D corresponding to Cases 1 and 2, respectively, Frame 1 implies the frame with an odd SFN and Frame 2 implies the frame with an even SFN. + +### 7A.2.1 Code allocation for Case 1 + +**Table 7D: Code Allocation for Case 1** + +| Code Group | Code Set | Frame 1 | | | Frame 2 | | | Associated t offset | +|------------|----------|-------------------|------------------|------------------|-------------------|------------------|-------------------|--------------------------------| +| 0 | 1 | C 1 | C 3 | jC 5 | C 1 | C 3 | -jC 5 | t 0 | +| 1 | 1 | C 1 | -C 3 | jC 5 | C 1 | -C 3 | -jC 5 | t 1 | +| 2 | 1 | -C 1 | C 3 | jC 5 | -C 1 | C 3 | -jC 5 | t 2 | +| 3 | 1 | -C 1 | -C 3 | jC 5 | -C 1 | -C 3 | -jC 5 | t 3 | +| 4 | 1 | jC 1 | jC 3 | jC 5 | jC 1 | jC 3 | -jC 5 | t 4 | +| 5 | 1 | jC 1 | -jC 3 | jC 5 | jC 1 | -jC 3 | -jC 5 | t 5 | +| 6 | 1 | -jC 1 | jC 3 | jC 5 | -jC 1 | jC 3 | -jC 5 | t 6 | +| 7 | 1 | -jC 1 | -jC 3 | jC 5 | -jC 1 | -jC 3 | -jC 5 | t 7 | +| 8 | 1 | jC 1 | C 5 | C 3 | jC 1 | C 5 | -C 3 | t 8 | +| 9 | 1 | jC 1 | -C 5 | C 3 | jC 1 | -C 5 | -C 3 | t 9 | +| 10 | 1 | -jC 1 | C 5 | C 3 | -jC 1 | C 5 | -C 3 | t 10 | +| 11 | 1 | -jC 1 | -C 5 | C 3 | -jC 1 | -C 5 | -C 3 | t 11 | +| 12 | 1 | jC 3 | C 5 | C 1 | jC 3 | C 5 | -C 1 | t 12 | +| 13 | 1 | jC 3 | -C 5 | C 1 | jC 3 | -C 5 | -C 1 | t 13 | +| 14 | 1 | -jC 3 | C 5 | C 1 | -jC 3 | C 5 | -C 1 | t 14 | +| 15 | 1 | -jC 3 | -C 5 | C 1 | -jC 3 | -C 5 | -C 1 | t 15 | +| 16 | 2 | C 10 | C 13 | jC 14 | C 10 | C 13 | -jC 14 | t 16 | +| 17 | 2 | C 10 | -C 13 | jC 14 | C 10 | -C 13 | -jC 14 | t 17 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 20 | 2 | jC 10 | jC 13 | jC 14 | jC 10 | jC 13 | -jC 14 | t 20 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 24 | 2 | jC 10 | C 14 | C 13 | jC 10 | C 14 | -C 13 | t 24 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 2 | -jC 13 | -C 14 | C 10 | -jC 13 | -C 14 | -C 10 | t 31 | + +NOTE: The code construction for code groups 0 to 15 using only the SCH codes from code set 1 is shown. The construction for code groups 16 to 31 using the SCH codes from code set 2 is done in the same way. + +### 7A.2.2 Code allocation for Case 2 + +Table 7C: Code Allocation for Case 2 + +| Code Group | Code Set | Frame 1 | | | | | | Frame 2 | | | | | | Associated $t_{offset}$ | | +|------------|----------|-----------|------------|-----------|-----------|------------|------------|------------|------------|-----------|------------|------------|------------|-------------------------|--| +| | | Slot k | | | Slot k+8 | | | Slot k | | | Slot k+8 | | | | | +| | | | | | | | | | | | | | | | | +| 0 | 1 | $C_1$ | $C_3$ | $jC_5$ | $C_1$ | $C_3$ | $-jC_5$ | $-C_1$ | $-C_3$ | $jC_5$ | $-C_1$ | $-C_3$ | $-jC_5$ | $t_0$ | | +| 1 | 1 | $C_1$ | $-C_3$ | $jC_5$ | $C_1$ | $-C_3$ | $-jC_5$ | $-C_1$ | $C_3$ | $jC_5$ | $-C_1$ | $C_3$ | $-jC_5$ | $t_1$ | | +| 2 | 1 | $jC_1$ | $jC_3$ | $jC_5$ | $jC_1$ | $jC_3$ | $-jC_5$ | $-jC_1$ | $-jC_3$ | $jC_5$ | $-jC_1$ | $-jC_3$ | $-jC_5$ | $t_2$ | | +| 3 | 1 | $jC_1$ | $-jC_3$ | $jC_5$ | $jC_1$ | $-jC_3$ | $-jC_5$ | $-jC_1$ | $jC_3$ | $jC_5$ | $-jC_1$ | $jC_3$ | $-jC_5$ | $t_3$ | | +| 4 | 1 | $jC_1$ | $C_5$ | $C_3$ | $jC_1$ | $C_5$ | $-C_3$ | $-jC_1$ | $-C_5$ | $C_3$ | $-jC_1$ | $-C_5$ | $-C_3$ | $t_4$ | | +| 5 | 1 | $jC_1$ | $-C_5$ | $C_3$ | $jC_1$ | $-C_5$ | $-C_3$ | $-jC_1$ | $C_5$ | $C_3$ | $-jC_1$ | $C_5$ | $-C_3$ | $t_5$ | | +| 6 | 1 | $jC_3$ | $C_5$ | $C_1$ | $jC_3$ | $C_5$ | $-C_1$ | $-jC_3$ | $-C_5$ | $C_1$ | $-jC_3$ | $-C_5$ | $-C_1$ | $t_6$ | | +| 7 | 1 | $jC_3$ | $-C_5$ | $C_1$ | $jC_3$ | $-C_5$ | $-C_1$ | $-jC_3$ | $C_5$ | $C_1$ | $-jC_3$ | $C_5$ | $-C_1$ | $t_7$ | | +| 8 | 2 | $C_{10}$ | $C_{13}$ | $jC_{14}$ | $C_{10}$ | $C_{13}$ | $-jC_{14}$ | $-C_{10}$ | $-C_{13}$ | $jC_{14}$ | $-C_{10}$ | $-C_{13}$ | $-jC_{14}$ | $t_8$ | | +| 9 | 2 | $C_{10}$ | $-C_{13}$ | $jC_{14}$ | $C_{10}$ | $-C_{13}$ | $-jC_{14}$ | $-C_{10}$ | $C_{13}$ | $jC_{14}$ | $-C_{10}$ | $C_{13}$ | $-jC_{14}$ | $t_9$ | | +| 10 | 2 | $jC_{10}$ | $jC_{13}$ | $jC_{14}$ | $jC_{10}$ | $jC_{13}$ | $-jC_{14}$ | $-jC_{10}$ | $-jC_{13}$ | $jC_{14}$ | $-jC_{10}$ | $-jC_{13}$ | $-jC_{14}$ | $t_{10}$ | | +| 11 | 2 | $jC_{10}$ | $-jC_{13}$ | $jC_{14}$ | $jC_{10}$ | $-jC_{13}$ | $-jC_{14}$ | $-jC_{10}$ | $jC_{13}$ | $jC_{14}$ | $-jC_{10}$ | $jC_{13}$ | $-jC_{14}$ | $t_{11}$ | | +| 12 | 2 | $jC_{10}$ | $C_{14}$ | $C_{13}$ | $jC_{10}$ | $C_{14}$ | $-C_{13}$ | $-jC_{10}$ | $-C_{14}$ | $C_{13}$ | $-jC_{10}$ | $-C_{14}$ | $-C_{13}$ | $t_{12}$ | | +| 13 | 2 | $jC_{10}$ | $-C_{14}$ | $C_{13}$ | $jC_{10}$ | $-C_{14}$ | $-C_{13}$ | $-jC_{10}$ | $C_{14}$ | $C_{13}$ | $-jC_{10}$ | $C_{14}$ | $-C_{13}$ | $t_{13}$ | | +| 14 | 2 | $jC_{13}$ | $C_{14}$ | $C_{10}$ | $jC_{13}$ | $C_{14}$ | $-C_{10}$ | $-jC_{13}$ | $-C_{14}$ | $C_{10}$ | $-jC_{13}$ | $-C_{14}$ | $-C_{10}$ | $t_{14}$ | | +| 15 | 2 | $jC_{13}$ | $-C_{14}$ | $C_{10}$ | $jC_{13}$ | $-C_{14}$ | $-C_{10}$ | $-jC_{13}$ | $C_{14}$ | $C_{10}$ | $-jC_{13}$ | $C_{14}$ | $-C_{10}$ | $t_{15}$ | | +| 16 | 3 | $C_0$ | $C_6$ | $jC_{12}$ | $C_0$ | $C_6$ | $-jC_{12}$ | $-C_0$ | $-C_6$ | $jC_{12}$ | $-C_0$ | $-C_6$ | $-jC_{12}$ | $t_{16}$ | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | | +| 23 | 3 | $jC_6$ | $-C_{12}$ | $C_0$ | $jC_6$ | $-C_{12}$ | $-C_0$ | $-jC_6$ | $C_{12}$ | $C_0$ | $-jC_6$ | $C_{12}$ | $-C_0$ | $t_{20}$ | | +| 24 | 4 | $C_4$ | $C_8$ | $jC_{15}$ | $C_4$ | $C_8$ | $-jC_{15}$ | $-C_4$ | $-C_8$ | $jC_{15}$ | $-C_4$ | $-C_8$ | $-jC_{15}$ | $t_{24}$ | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | | +| 31 | 4 | $jC_8$ | $-C_{15}$ | $C_4$ | $jC_8$ | $-C_{15}$ | $-C_4$ | $-jC_8$ | $C_{15}$ | $C_4$ | $-jC_8$ | $C_{15}$ | $-C_4$ | $t_{31}$ | | + +NOTE: The code construction for code groups 0 to 15 using the SCH codes from code sets 1 and 2 is shown. The construction for code groups 16 to 31 using the SCH codes from code sets 3 and 4 is done in the same way. + +## 7A.3 Evaluation of synchronisation codes + +The evaluation of information transmitted in SCH on code group and frame timing is shown in table 7E, where the 32 code groups are listed. Each code group contains 4 specific scrambling codes, each scrambling code associated with a specific short and long basic midamble code. + +Each code group is additionally linked to a specific $t_{offset}$ , thus to a specific frame timing. By using this scheme, the UE can derive the position of the frame border due to the position of the SCH sequence and the knowledge of $t_{offset}$ . The complete mapping of Code Group to Scrambling Code, Midamble Codes and $t_{offset}$ is depicted in table 7E. + +**Table 7E: Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles and $t_{offset}$** + +| CELL
PARAMETER | Code
Group | Associated Codes | | | Associated $t_{offset}$ | | | +|-------------------|---------------|--------------------|--------------------------------|---------------------------------|-------------------------|--|--| +| | | Scrambling
Code | Long Basic
Midamble
Code | Short Basic
Midamble
Code | | | | +| 0 | Group 0 | Code 0 | m PL0 | m SL0 | $t_0$ | | | +| 1 | | Code 1 | m PL1 | m SL1 | | | | +| 2 | | Code 2 | m PL2 | m SL2 | | | | +| 3 | | Code 3 | m PL3 | m SL3 | | | | +| 4 | Group 1 | Code 4 | m PL4 | m SL4 | $t_1$ | | | +| 5 | | Code 5 | m PL5 | m SL5 | | | | +| 6 | | Code 6 | m PL6 | m SL6 | | | | +| 7 | | Code 7 | m PL7 | m SL7 | | | | +| ⋮ | | | | | | | | +| ⋮ | | | | | | | | +| ⋮ | | | | | | | | +| 124 | Group 31 | Code 124 | m PL124 | m SL124 | $t_{31}$ | | | +| 125 | | Code 125 | m PL125 | m SL125 | | | | +| 126 | | Code 126 | m PL126 | m SL126 | | | | +| 127 | | Code 127 | m PL127 | m SL127 | | | | + +Each cell shall cycle through two sets of cell parameters in a code group with the cell parameters changing each frame. Table 7F shows how the cell parameters are cycled according to the SFN. + +**Table 7F: Alignment of cell parameter cycling and SFN** + +| Initial Cell
Parameter
Assignment | Code Group | Cell Parameter
used when
SFN mod 2 = 0 | Cell Parameter
used when
SFN mod 2 = 1 | | +|-----------------------------------------|------------|----------------------------------------------|----------------------------------------------|--| +| 0 | Group 0 | 0 | 1 | | +| 1 | | 1 | 0 | | +| 2 | | 2 | 3 | | +| 3 | | 3 | 2 | | +| 4 | Group 1 | 4 | 5 | | +| 5 | | 5 | 4 | | +| 6 | | 6 | 7 | | +| 7 | | 7 | 6 | | +| ⋮ | | | | | +| ⋮ | | | | | +| ⋮ | | | | | +| 124 | Group 31 | 124 | 125 | | +| 125 | | 125 | 124 | | +| 126 | | 126 | 127 | | +| 127 | | 127 | 126 | | + +# 8 Synchronisation codes for the 1.28 Mcps option + +## 8.1 The downlink pilot channel (DwPCH) + +The contents of DwPCH is composed of 64 chips of a SYNC-DL sequence, cf.[AA.1 Basic SYNC-DL sequence] and 32 chips of guard period (GP). The SYNC-DL code is not scrambled + +There should be 32 different basic SYNC-DL codes for the whole system. + +For the generation of the complex valued SYNC-DL codes of length 64, the basic binary SYNC-DL codes + +$\underline{s} = (s_1, s_2, \dots, s_{64})$ of length 64 shown in Table AA.1 are used. The relation between the elements $\underline{s}$ and $\underline{s}$ is given by: + +$$\underline{s}_i = (j)^i \cdot s_i \quad s_i \in \{1, -1\} \quad i=1, \dots, 64 \quad (1)$$ + +Hence, the elements $\underline{s}_i$ of the complex SYNC-DL code $\underline{s}$ are alternating real and imaginary. + +The SYNC-DL is QPSK modulated and the phase of the SYNC-DL is used to signal the presence of the P-CCPCH in the multi-frame of the resource units of code $c_{Q=16}^{(k=1)}$ and $c_{Q=16}^{(k=2)}$ in time slot #0. + +### 8.1.1 Modulation of the SYNC-DL + +The SYNC-DL sequences are modulated with respect to the midamble ( $m^{(1)}$ ) in time slot #0. + +Four consecutive phases (phase quadruple) of the SYNC-DL are used to indicate the presence of the P-CCPCH in the following 4 sub-frames. In case the presence of a P-CCPCH is indicated, the next following sub-frame is the first sub-frame of the interleaving period. As QPSK is used for the modulation of the SYNC-DL, the phases 45, 135, 225, and 315° are used. + +The total number of different phase quadruples is 2 (S1 and S2). A quadruple always starts with an even system frame number ((SFN mod 2) =0). Table 8 is showing the quadruples and their meaning. + +**Table 8: Sequences for the phase modulation for the SYNC-DL** + +| Name | Phase quadruple | Meaning | +|------|-------------------|----------------------------------------------| +| S1 | 135, 45, 225, 135 | There is a P-CCPCH in the next 4 sub-frames | +| S2 | 315, 225, 315, 45 | There is no P-CCPCH in the next 4 sub-frames | + +## 8.2 The uplink pilot channel (UpPCH) + +The contents in UpPCH is composed of 128 chips of a SYNC-UL sequence, cf. [AA.2 Basic SYNC-UL sequence] and 32chips of guard period (GP) .The SYNC-UL code is not scrambled. + +There should be 256 different basic SYNC-UL codes (see Table AA.2) for the whole system. + +For the generation of the complex valued SYNC-UL codes of length 128, the basic binary SYNC-UL codes + +$\underline{s} = (s_1, s_2, \dots, s_{128})$ of length 128 shown in Table AA.2 are used. The relation between the elements $\underline{s}$ and $\underline{s}$ is given by: + +$$\underline{s}_i = (j)^i \cdot s_i \quad s_i \in \{1, -1\} \quad i=1, \dots, 128 \quad (2)$$ + +Hence, the elements $\underline{s}_i$ of the complex SYNC-UL code $\underline{s}$ are alternating real and imaginary. + +## 8.3 Code Allocation + +Relationship between the SYNC-DL and SYNC-UL sequences, the scrambling codes and the midamble codes + +| Code Group | Associated Codes | | | | +|------------|------------------|------------|--------------------|------------------------| +| | SYNC-DL ID | SYNC-UL ID | Scrambling Code ID | Basic Midamble Code ID | +| Group 1 | 0 | 0...7 | 0 | 0 | +| | | | 1 | 1 | +| | | | 2 | 2 | +| | | | 3 | 3 | +| Group 2 | 1 | 8...15 | 4 | 4 | +| | | | 5 | 5 | +| | | | 6 | 6 | +| | | | 7 | 7 | +| | | | . | | +| | | | . | | +| | | | . | | +| Group 32 | 31 | 248...255 | 124 | 124 | +| | | | 125 | 125 | +| | | | 126 | 126 | +| | | | 127 | 127 | + +Note: In a multi-frequency cell, primary frequency and secondary frequency use the same scrambling code and basic midamble code. + +## 8.3Aa Code Allocation + +For the dedicated carrier MBSFN, the basic preamble codes are segmented into two groups, even group and odd group, and the Basic preamble Code is described in [7]. + +**Relationship between the scrambling codes and the preamble codes** + +| Code subgroup | Associated Codes | | | | +|---------------|--------------------|------------------------|--------------------|------------------------| +| | $P_{p,even}$ group | | $P_{p,odd}$ group | | +| | Scrambling Code ID | Basic preamble Code ID | Scrambling Code ID | Basic preamble Code ID | +| Sub-g1 | 0 | 0 | 4 | 1 | +| Sub-g2 | 8 | 2 | 12 | 3 | +| Sub-g3 | 16 | 4 | 20 | 5 | +| Sub-g4 | 24 | 6 | 28 | 7 | + +| | | | | | +|---------|-----|----|-----|----| +| | | | | | +| Sub-g15 | 112 | 28 | 116 | 29 | +| Sub-g16 | 120 | 30 | 124 | 31 | + +# 9 Cell synchronisation codes + +The cell synchronisation codes (CSCs) are constructed as so-called CEC sequences, i.e. concatenated and periodically extended complementary sequences. They are complex-valued sequences that are derived as cyclically offset versions from a set of possible constituent Golay complementary pairs. + +The CSCs are chosen to have good aperiodic auto correlation properties. The aperiodic auto correlations of the applicable constituent Golay complementary pairs and every pair of their derived cyclically offset versions are complementary. Furthermore, orthogonality is preserved for all CSCs which are derived from the same constituent Golay complementary pair due to this complementary property. + +The delay and weight matrices for the set of $M = 8$ possible constituent Golay complementary pairs are listed in the table below: + +| Code ID $m$ | Delay matrices $D_m$ and weight matrices $W_m$ of constituent Golay complementary pairs | +|-------------|--------------------------------------------------------------------------------------------------------------------------| +| 0 | $D_0 = \langle 512, 64, 128, 1, 16, 4, 256, 32, 8, 2 \rangle, W_0 = \langle 1, 1, 1, 1, -1, -1, 1, 1, 1, 1 \rangle$ | +| 1 | $D_1 = \langle 2, 16, 32, 256, 1, 8, 128, 4, 512, 64 \rangle, W_1 = \langle 1, -1, 1, 1, -1, 1, -1, 1, -1, -1 \rangle$ | +| 2 | $D_2 = \langle 16, 512, 32, 256, 4, 1, 64, 8, 2, 128 \rangle, W_2 = \langle -1, 1, 1, 1, -1, 1, -1, 1, -1, -1 \rangle$ | +| 3 | $D_3 = \langle 512, 16, 8, 4, 2, 256, 128, 64, 32, 1 \rangle, W_3 = \langle -1, -1, -1, -1, -1, 1, -1, 1, 1, 1 \rangle$ | +| 4 | $D_4 = \langle 512, 128, 256, 32, 2, 4, 64, 1, 16, 8 \rangle, W_4 = \langle 1, -1, 1, 1, -1, -1, -1, -1, -1, 1 \rangle$ | +| 5 | $D_5 = \langle 1, 2, 4, 64, 512, 16, 32, 256, 128, 8 \rangle, W_5 = \langle -1, 1, 1, 1, 1, -1, -1, 1, -1, 1 \rangle$ | +| 6 | $D_6 = \langle 8, 16, 128, 2, 32, 1, 256, 512, 4, 64 \rangle, W_6 = \langle -1, -1, 1, 1, 1, 1, -1, -1, -1, 1 \rangle$ | +| 7 | $D_7 = \langle 1, 2, 128, 16, 256, 32, 8, 512, 64, 4 \rangle, W_7 = \langle 1, 1, -1, -1, -1, -1, 1, -1, -1, -1 \rangle$ | + +A constituent Golay complementary pair of length $N = 1024$ , defined as: + +$$s_m = \langle s_m(0), s_m(1), s_m(2), \dots, s_m(1023) \rangle \text{ and } g_m = \langle g_m(0), g_m(1), g_m(2), \dots, g_m(1023) \rangle$$ + +shall be derived from the selected delay and weight matrices: + +$$D_m = \langle D_m(0), D_m(1), D_m(2), \dots, D_m(9) \rangle \text{ and } W_m = \langle W_m(0), W_m(1), W_m(2), \dots, W_m(9) \rangle$$ + +as follows. + +Define: + +$$a^{(0)} = \langle a^{(0)}(0), a^{(0)}(1), a^{(0)}(2), \dots, a^{(0)}(1023) \rangle = \langle 1, 0, 0, \dots, 0 \rangle \text{ and}$$ + +$$b^{(0)} = \langle b^{(0)}(0), b^{(0)}(1), b^{(0)}(2), \dots, b^{(0)}(1023) \rangle = \langle 1, 0, 0, \dots, 0 \rangle.$$ + +Then, the elements of the set of auxiliary sequences: + +$$a^{(n)} = \langle a^{(n)}(0), a^{(n)}(1), a^{(n)}(2), \dots, a^{(n)}(1023) \rangle \text{ and } b^{(n)} = \langle b^{(n)}(0), b^{(n)}(1), b^{(n)}(2), \dots, b^{(n)}(1023) \rangle$$ + +are given by the recursive relations: + +$$a^{(n+1)}(i) = a^{(n)}(i) + W_m(n) \times b^{(n)}(i - D_m(n)) \text{ and}$$ + +$$b^{(n+1)}(i) = a^{(n)}(i) - W_m(n) \times b^{(n)}(i - D_m(n))$$ + +with element index $i = 0, 1, 2, \dots, 1023$ and iteration index $n = 0, 1, 2, \dots, 9$ . Operations on the element index shall be performed modulo 1024. + +The elements of the constituent Golay complementary pairs $s_m$ and $g_m$ are then obtained from the output of the last iteration step using: + +$$s_m(i) = a^{(10)}(i) \text{ and } g_m(i) = b^{(10)}(i) \text{ for } i = 0, 1, 2, \dots, 1023$$ + +From each applicable constituent Golay complementary pair $s_m$ and $g_m$ , up to $K = 8$ different cyclically offset pairs $s_m^{(k)}$ and $g_m^{(k)}$ , with offset index $k = 0, 1, 2, \dots, K-1$ , of length 1152 chips can be derived. The complementary property of the respective aperiodic auto correlation is preserved for each particular pair of sequences $s_m^{(k)}$ and $g_m^{(k)}$ . The generation of the $K$ cyclically offset pairs from $s_m$ and $g_m$ is done in a similar way as the generation of the user midambles from a periodic basic midamble sequence as described in [7]. + +With $N = 1024$ , $K = 8$ , $W = 128$ , the elements of a cyclically offset pair: + +$$s_m^{(k)} = \langle s_m^{(k)}(0), s_m^{(k)}(1), s_m^{(k)}(2), \dots, s_m^{(k)}(1151) \rangle \text{ and } g_m^{(k)} = \langle g_m^{(k)}(0), g_m^{(k)}(1), g_m^{(k)}(2), \dots, g_m^{(k)}(1151) \rangle$$ + +for a particular offset $k$ , with $k = 0, 1, 2, \dots, K-1$ , shall be derived from the elements of the constituent Golay complementary pairs $s_m$ and $g_m$ using: + +$$s_m^{(k)}(i) = (j)^i \times s_m(i + k \times W) \text{ and } g_m^{(k)}(i) = (j)^i \times g_m(i + k \times W) \text{ for } i = 0, 1, 2, \dots, N - k \times W - 1,$$ + +$$s_m^{(k)}(i) = (j)^i \times s_m(i - N + k \times W) \text{ and } g_m^{(k)}(i) = (j)^i \times g_m(i - N + k \times W) \text{ for } i = N - k \times W, N - k \times W + 1, \dots, 1151.$$ + +Hence, the elements of $s_m^{(k)}$ and $g_m^{(k)}$ are alternating real and imaginary. + +Note that both $s_m^{(0)}$ and $g_m^{(0)}$ simply correspond to $s_m$ and $g_m$ respectively, followed by its first $W$ elements as post extension and that both $s_m^{(7)}$ and $g_m^{(7)}$ simply correspond to the last $W$ elements of $s_m$ and $g_m$ in form of a pre extension, followed by $s_m$ and $g_m$ respectively. + +Finally, the CSC $C_{CSC, m}^{(k)}$ derived from the $m$ :th applicable constituent Golay complementary pair $s_m$ and $g_m$ , and for the $k$ :th offset is then defined as a concatenation of $s_m^{(k)}$ and $g_m^{(k)}$ by: + +$$C_{CSC, m}^{(k)} = \langle s_m^{(k)}(0), s_m^{(k)}(1), s_m^{(k)}(2), \dots, s_m^{(k)}(1151), g_m^{(k)}(0), g_m^{(k)}(1), g_m^{(k)}(2), \dots, g_m^{(k)}(1151) \rangle$$ + +where the leftmost element $s_m^{(k)}(0)$ in the sequence corresponds to the chip to be first transmitted in time. An CSC has therefore length 2304 chips. + +Note that due to this construction method, the auto correlations for all CSCs derived from one particular constituent Golay complementary pair $s_m$ and $g_m$ can be obtained simultaneously and in sequential order from the sum of partial correlations with $s_m$ and $g_m$ , these CSCs remaining orthogonal. + +CSCs derived according to above have complex values and shall not be subject to the channelisation or scrambling process, i.e. its elements represent complex chips for usage in the pulse shaping process at modulation. + +# --- Annex A (normative): Scrambling Codes + +The applicable scrambling codes are listed below. Code numbers are referring to table 6 'Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles, Preambles and $t_{\text{offset}}$ ' in subclause 6.3 'Evaluation of synchronisation codes'. + +Code{0, 4, 8, 12, ..., 120, 124} are used for downlink MBSFN operation. + +| Scrambling Code | V 1 | V 2 | V 3 | V 4 | V 5 | V 6 | V 7 | V 8 | V 9 | V 10 | V 11 | V 12 | V 13 | V 14 | V 15 | V 16 | +|-----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Code 0 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | +| Code 2 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 3 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 4 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 5 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | +| Code 6 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 7 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | +| Code 8 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | +| Code 9 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 10 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 11 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 12 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | +| Code 13 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 14 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 15 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | +| Code 16 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | +| Code 17 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 18 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 19 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 20 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 21 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | +| Code 22 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 23 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 24 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 25 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 26 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 27 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 28 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | +| Code 29 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 30 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | +| Code 31 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | +| Code 32 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 33 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 34 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 35 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 36 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | +| Code 37 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 38 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 39 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 40 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 41 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 42 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | +| Code 43 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | +| Code 44 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 45 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 46 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | +| Code 47 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | +| Code 48 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 49 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | +| Code 50 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 51 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | +| Code 52 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | + +| Scrambling Code | V 1 | V 2 | V 3 | V 4 | V 5 | V 6 | V 7 | V 8 | V 9 | V 10 | V 11 | V 12 | V 13 | V 14 | V 15 | V 16 | +|-----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Code 53 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | +| Code 54 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 55 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 56 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 57 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | +| Code 58 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 59 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | +| Code 60 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | +| Code 61 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | +| Code 62 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | +| Code 63 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | +| Code 64 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | +| Code 65 | -1 | -1 | -1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 66 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | +| Code 67 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | +| Code 68 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | +| Code 69 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | +| Code 70 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 71 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | +| Code 72 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | +| Code 73 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | +| Code 74 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | +| Code 75 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | +| Code 76 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | +| Code 77 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 78 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | +| Code 79 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | +| Code 80 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | +| Code 81 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 82 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | +| Code 83 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | +| Code 84 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | +| Code 85 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | +| Code 86 | -1 | -1 | -1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | +| Code 87 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 88 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | +| Code 89 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | 1 | -1 | -1 | +| Code 90 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | +| Code 91 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | +| Code 92 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | +| Code 93 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | +| Code 94 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | +| Code 95 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | +| Code 96 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | +| Code 97 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | +| Code 98 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | +| Code 99 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | -1 | +| Code 100 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | +| Code 101 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | +| Code 102 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 103 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | -1 | +| Code 104 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | +| Code 105 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | + +| Scrambling Code | v 1 | v 2 | v 3 | v 4 | v 5 | v 6 | v 7 | v 8 | v 9 | v 10 | v 11 | v 12 | v 13 | v 14 | v 15 | v 16 | +|-----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Code 106 | 1 | 1 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | +| Code 107 | -1 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | +| Code 108 | -1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | -1 | +| Code 109 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | +| Code 110 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 111 | 1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | +| Code 112 | -1 | -1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 113 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | +| Code 114 | -1 | -1 | -1 | 1 | 1 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | -1 | +| Code 115 | 1 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 116 | -1 | 1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | +| Code 117 | 1 | 1 | 1 | -1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | +| Code 118 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | +| Code 119 | -1 | -1 | -1 | 1 | -1 | 1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | +| Code 120 | -1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | +| Code 121 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | +| Code 122 | -1 | -1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | 1 | -1 | -1 | -1 | +| Code 123 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | -1 | 1 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | +| Code 124 | -1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | +| Code 125 | 1 | -1 | -1 | 1 | 1 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 1 | 1 | -1 | -1 | +| Code 126 | 1 | 1 | 1 | 1 | -1 | 1 | -1 | 1 | -1 | 1 | 1 | -1 | 1 | 1 | -1 | -1 | +| Code 127 | 1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | 1 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | + +# Annex AA (normative): Synchronisation sequence + +## AA.1 Basic SYNC-DL sequence + +**Table AA.1: Basic SYNC-DL Codes** + +| Code ID | SYNC-DL Codes of length 64 | +|----------------|-----------------------------------| +| 0 | B3A7CC05A98688E4 | +| 1 | 9D559BD290606791 | +| 2 | 2CE7BA12A017C3A2 | +| 3 | 34511D20672F4712 | +| 4 | 9A772841474603F2 | +| 5 | 9109B1A5CE01F228 | +| 6 | 8FD429B3594501C0 | +| 7 | 25251354AA3F8C19 | +| 8 | C9A3B8E0C043EA56 | +| 9 | BA04B888E5BC1802 | +| 10 | A735354299370207 | +| 11 | 74C3C8DA4415AE51 | +| 12 | F4FD0458A0124663 | +| 13 | A011D4E16C3D6064 | +| 14 | BDA0661B0CAA8C68 | +| 15 | 8E31123F28928698 | +| 16 | F095C1632E2906AB | +| 17 | B60B4A8A664071CF | +| 18 | AA094DCCE91E041A | +| 19 | C0C31CDA8A256807 | +| 20 | D516964FB18C1890 | +| 21 | 30DE01834F4AACCE | +| 22 | 8F700323BA5CAD34 | +| 23 | 1B50F4DEE0C1380C | +| 24 | 443382164F56F2D1 | +| 25 | E1E4005D49B846B4 | +| 26 | 040A97165330BFAA | +| 27 | C48E26881693AD78 | +| 28 | D4354B2FE02361CC | +| 29 | 5383AB6C8A10CE84 | +| 30 | D417A730F2F12244 | +| 31 | ABF0A0D905A939C4 | + +## AA.2 Basic SYNC-UL Codes + +**Table AA.2: Basic SYNC-UL Codes** + +| Code ID | SYNC-UL Codes of length 128 | +|---------|----------------------------------| +| 0 | C11C20F0D1807DB8859175B798EC094A | +| 1 | 91278068081EC8E74543DBC1C9AD4235 | +| 2 | 38F5AEE2E513DB12A663BA04160103E5 | +| 3 | 7AA8A0A210F12A1E4332F2EDD33011FC | +| 4 | C180EA3B9BA1774EB9611BD249C4A508 | +| 5 | B072A2C839489D496B98CE9D0132FBC9 | +| 6 | B2723EAC6EB01667F2B33961C8074234 | +| 7 | C4144AD060F0EC095E227B92CF7C8280 | +| 8 | 653036A10D3054146FCF815986C63A14 | +| 9 | F899CA61435D64DC07FDF04C4A0C053A | +| 10 | B56F2D6893A8051407F4C341D88DC7DC | +| 11 | DC0BE838242142EDE6413A72C88D74AA | +| 12 | 22A2FD86E4086C70A4860B13C76E579F | +| 13 | A3CBC21322C97D2A02728E7875F39588 | +| 14 | D4EC4F694A082CB38E3B1558A0FCC89F | +| 15 | CC891141C4E216D235C15CF5D3F9B002 | +| 16 | A1993114C50B77CB0C0725D1E22FD016 | +| 17 | 24F73A979DE52F82E8800CCB93842A59 | +| 18 | 8F878FA04659842E294D8DEAB20BA2FD | +| 19 | AC90B0442D70662B028CF76A6BECD09 | +| 20 | D94A284DF64D7B0102F0E084C29C88C8 | +| 21 | 8603200C7596F24E865FD3815693358D | +| 22 | B466B12CF433642BD8B08F1F452E0550 | +| 23 | 86A3A1772C1C99FCA7DBBA0C312E34A0 | +| 24 | 622A1889F72A9A2C042D46F08EFEE1AC | +| 25 | BF220A362BC0D3B0D7CE400954C6CFAE | +| 26 | D28D73C52E89CF57905C502244F63616 | +| 27 | AD4E1C2103697D64D8B9D4C035D90548 | +| 28 | 8F081A9BA12B6C6BD024531AA984D21C | +| 29 | E4092429BE82988E1E3585BF6A6AE550 | +| 30 | 08BD36E0A9C061782CB38B35B335CA56 | +| 31 | 1CDFF3CC2685D1C44F4A1059AB03F40A | +| 32 | 506ED4E88FB1CECE3243F2A27A0221A4 | +| 33 | 846CF58A7AB613C83A24130B5778C0E2 | +| 34 | A2711A99E26A0C75AC026F4CFAECE893 | +| 35 | D846EEEBA2432AC05A01043C62579DCF | +| 36 | 6B16B4E851CAF2121FC4CF88820C89E7 | +| 37 | AA4889A78207674A74E10C6F2BE11D48 | +| 38 | 8534CF8145BC991052814ED5C72709EE | +| 39 | 01AEF15D2290A84A607425746D9963C7 | +| 40 | 999188F758245D5164FE16D852942C71 | +| 41 | CF71C008599287E446E30745BD56E2D2 | +| 42 | 248414BA0DF8CDC4711FE7C8707ED0AD | + +| | | +|----|----------------------------------| +| 43 | EB2E263EC016191C81AB714BFE4D2B30 | +| 44 | 862082A7482FAC1C499793A0D8CED670 | +| 45 | DE2C22B2783AB75A7342608DE413840A | +| 46 | E31AA60B727F2CA2A78DAAC10665011D | +| 47 | CEF6CD06509870AC9E0177ACD550921D | +| 48 | E52C84D499FFCDC287581691471540F2 | +| 49 | B33BF6551A4322504BEE0930BCA1EC68 | +| 50 | 555BE6886D0FC43D72315E6C6D384148 | +| 51 | 8444F67451EE23CE1240C90F0B52A492 | +| 52 | 5C290D28E84060E69D09788A261B10FF | +| 53 | 337E0C35E83CD38CCC5D45804241F952 | +| 54 | A7879F0D31A8982A01EE6AC4952984DC | +| 55 | A37F506508928C70A83D69A2373781B9 | +| 56 | 42F55208EE12909803A7CBEB19B5419E | +| 57 | 57E5E268A328FCC9ED04B9E5420AC702 | +| 58 | EB033AD1222F84D8642C4E3FAAD28206 | +| 59 | 98EE1415F026AC0E862C520451697DD0 | +| 60 | 6A0528AEA4B7CD6702660D81F8821E19 | +| 61 | 763D626A87C603BCB09E1A4C800A378F | +| 62 | EEA61897879289340C23F669D6A03762 | +| 63 | A6571B3CC2D0E04F017ACC808B92DCE7 | +| 64 | DDF88B52EA1831D293A803CF23C8C471 | +| 65 | 6CA4D333A2684140475DAB491F61C17A | +| 66 | A7D2AD23043989A13289F7C3E135580A | +| 67 | B1C752FA66B41C81904EDE27EA000E2E | +| 68 | 8694BE3CC1CB36BE2A095F89CC619080 | +| 69 | 9C20334E1BBC596B25E151180BF99940 | +| 70 | 484256214F81070DD9C49A2B05A43DCE | +| 71 | 401A20BCBE29B7438A7AEE44635A9E23 | +| 72 | 8858585C3239CBF628033FA0DF189378 | +| 73 | EFA36404C1BA5118CC5F9052FD28D9C3 | +| 74 | 155609873D8A042D496E6477B747C4F8 | +| 75 | 8446077883A6D7D2549CC9742E3FD023 | +| 76 | E630142B189AA209371A6F0FFDBC30A7 | +| 77 | C46060535AC6DBB2095F1D7826D0CD5C | +| 78 | E00D19E48797148B28DEDA9D429362E2 | +| 79 | 645DE447E938485489416CAFCC1C571F | +| 80 | DA10AFBF2AE61C593A1D88584DE30598 | +| 81 | BB248AEA5FD3FE210CD48FC401E1A686 | +| 82 | A89F146BD9191F445301C081CB6F5625 | +| 83 | 15BBF04F247C59150208949EB6B9CC58 | +| 84 | 08F48BFA7804B5B2CC2E96510232E062 | +| 85 | 9AA2BE74005A3679C626B209580B8D03 | +| 86 | 9D40664A2C808F2F293E255398B37E6A | + +| | | +|-----|----------------------------------| +| 87 | 6869C98A8AAD81CAE41A23C83FF9EEA0 | +| 88 | 576E8948E61BD0927C4140C3C04C4CF3 | +| 89 | 0F942C67A1137B6EAA058C2A74872C73 | +| 90 | 9D058E27ED546C10632684BBC84E5BC1 | +| 91 | 79D4B840E20148B134F90B51164BCBD0 | +| 92 | 0E35E1D8D1214C05FAC790B69B239150 | +| 93 | FFA1BB0232CD71480BE5CA1C2A269F89 | +| 94 | B2956F5F4E270446F9211584792628DB | +| 95 | F56CCA23421C8EC8F8A41F7DA4A41EA2 | +| 96 | 0B5ECA04F1789A7148C80C39D57D05F6 | +| 97 | A10B538E8A8CFC8F8925C485F2A88660 | +| 98 | 9925C2C715001D9FC78ACCC51DA1AF34 | +| 99 | 0DAC9CFDEA40429A8B12C7D320D60F70 | +| 100 | 377FC9A097017958440914E83118E39D | +| 101 | 8421096FA8B47E4E943B6473671955CC | +| 102 | 574086183477C4F68540CB7E858263B1 | +| 103 | 895B6A8980C6703C779F49F40C5CFC19 | +| 104 | D0D253E157BC19262150CEA668679E71 | +| 105 | B8889C60EBA812BD7F0B6498823296D2 | +| 106 | A13FB9F3A08528E44B13C12CF0D461AA | +| 107 | 8D4DCFBE43D6E2024B1F8470224AA330 | +| 108 | 536D159E119E0893838657B12A074E64 | +| 109 | DCFD49C504AD3A2F049A0CB70238EC8A | +| 110 | D363DB4C46C11757FA8FB18139789102 | +| 111 | 424A1E8A1D4DA256E4CA3BC8C2201BE3 | +| 112 | 417B619ED30FEB0A847CC3A191A20398 | +| 113 | 843FBBC95453C61786D1332612B45B4D | +| 114 | F26CACC0732CF8ED0C5BC1462B1620B4 | +| 115 | 88E0FE440C70E9249A92A7AF94638880 | +| 116 | 99A52B7D8C950308057E0661D7459960 | +| 117 | A5C28218BF5D16E63E42698A0A6B0896 | +| 118 | B2763BEEC784A12E8C50778536921806 | +| 119 | 987B2B6A3A77A059B30A082457AB84E0 | +| 120 | 820DB500F1B206358D7A7F210AB85AA8 | +| 121 | 97760A5CFC5E03EB439C914590045938 | +| 122 | 896A720E8857C8708A59F8C94DE0841E | +| 123 | 2D101F0CF95263843412577340DEBB11 | +| 124 | E8E5214B4DCF5D11A245B0149D49C87C | +| 125 | 51224EAA10099ACDE384834A5ADF03D8 | +| 126 | 64E51253554A230C186FDE4E8781BC09 | +| 127 | A499E391E69ED08890AC1A82A6115BEC | +| 128 | EE54C6E1834210D3EC1B07A456B92AA8 | +| 129 | 949DB5CA82420B54C1E0BCC111E704D9 | +| 130 | 9439EE9A9E4C447D1AA350926495047F | + +| | | +|-----|-----------------------------------| +| 131 | AD095CC0E7438AECE38D60980B3F2D00 | +| 132 | 83089C254C5EE9788072BC3D9282F798 | +| 133 | A27DC1A457BC5A56563D8A9B11203615 | +| 134 | 713053A9C0B1B08B14705FF5A7244DB4 | +| 135 | D36D4B9F4007354E0EC1B0CA8C8C7124 | +| 136 | 82E7C990612114F1CCE1BD9509FD4386 | +| 137 | C8D83FF0B48B14830D2015D53F8C0672 | +| 138 | 08AF223C869A36B169148FDDABB7D120 | +| 139 | B6C284C600AD0A99F86C449F8F4C53A6 | +| 140 | DC741B320C07682AF92AC4DBDE0C28C2 | +| 141 | 89B8D84FA902265850C0FA6FF0EB2C4F | +| 142 | A69445B3A52201DB984BC03D1956D7F3 | +| 143 | 0FE0F7224B7AD72E4D4530D0223F590C | +| 144 | 1B8C06F051434048EB925133AD3BD3F9 | +| 145 | E133D4C3C942726A351300C37E55D0DF | +| 146 | 9E09481D1881A66F562D8B453BC83AB2 | +| 147 | 2397B04B60A3C5700907BDBBA4E818C8 | +| 148 | 8F81F7A08CC6C8DA3D692AD34F50C012 | +| 149 | 9AB325352981BCCFA072F8FDE3009221 | +| 150 | 4FA88B7F1F8A620C31B0D486C52AC2F6 | +| 151 | 097AF0ADD16D7D39851049F0130EE444 | +| 152 | A5027732DACFF11C388D5820A4A9BA49 | +| 153 | 1CD981EA2EDB46218A407C7E20D4BE84 | +| 154 | D0FD94279FA67EC61A3904C0AD8ACA04 | +| 155 | EA73A9415EC2004D49E9D0F645961C75 | +| 156 | 005AF0614A7552041194DEECBF8DD016 | +| 157 | B514481533DA0A731705B93CF634E40D | +| 158 | 983054521841A6E4FF34B2C07B5684FE | +| 159 | C46D927D0FD2B2F509550025677C6871 | +| 160 | 2AD85C08127487C87ECE014D65169102 | +| 161 | 0F617852FA3930AA7EE74B400B2CC831 | +| 162 | AE9D395004C6E27540C378625D36E0D6 | +| 163 | DC4FA55750F10B0636248F12C212FFE4 | +| 164 | D3602B8D6CBF1809C88B827185631ECF | +| 165 | A94825850708E7723EA8F22C44BF78B2 | +| 166 | A62D231C16AEFEFE0B0026B306662945A | +| 167 | 9C7BE810A86465A50551F89125D93B12 | +| 168 | 9712D9338B9CC60485C10172F50F121F | +| 169 | A3902CE0E0B9912591FF28C695728257 | +| 170 | 4167057891AB29473A9E0F67F3658921 | +| 171 | B3368B91EC12A284BC414C8F0D7F8D20 | +| 172 | EE21888101ABF06C1175828CB58B598D | +| 173 | E43923A00ECC32CCC2D162A4A44BD7F4 | +| 174 | CC9E30B8538AD51703EEB6F70801AB22 | + +| | | +|-----|----------------------------------| +| 175 | B908AD2F1501DA1C156811736CD798CD | +| 176 | 2B46302ACCC2F808797FC648A614326D | +| 177 | 8A54494F1BE27235B8764023AA0FBCFA | +| 178 | BC1041E6F636421E89277DC154439103 | +| 179 | 275B39A63029B974E3561AE0A8FC8032 | +| 180 | 9283F6FE819B80492A22B85CE5CE5DC4 | +| 181 | 4CCB52C0CE058A78022C22DF5788CBCC | +| 182 | B0DF9608DE549A6F6C581516919A81E6 | +| 183 | 2CA185163CC36060D1E85BB0A7FBB988 | +| 184 | 66101D2846155CAC986FC790D2124EFC | +| 185 | 8016E3904644D2093579B83BD7AB5071 | +| 186 | 531CAB7085BEC14257439658023647CF | +| 187 | DF2910165AA5051E41F6EB198E4D491C | +| 188 | BA32052042B0FB2188DE7857DA1B6788 | +| 189 | 9E6D075AFF0EA4153615E140BF380666 | +| 190 | 9ACC5A037902534642A3BE391AA40F9B | +| 191 | 4D741A3B4499843010D7E5FA8988DC80 | +| 192 | FA1421C96EDC6092726154560B1C2FC8 | +| 193 | 882946076223CAE0B0BFE3EDA59826D5 | +| 194 | CEBB288C28B7472A0D3917012276C034 | +| 195 | BD35A6E00C9528DB38289CF823C34F30 | +| 196 | E2C93618B6B2800D51171A5F85746A55 | +| 197 | B43EF39A1A64F0E220AF740F9494291B | +| 198 | AC537817C2612744A58132A8AFBC44A3 | +| 199 | 98A321249A821DDBF81C38235A371A14 | +| 200 | AE1D46069090D81BB6B08FED9E687285 | +| 201 | 7EAE2415DC2CD60AE083249A33B56E05 | +| 202 | 3D942AAA9BC9F27289421CE0B301FB98 | +| 203 | 1548BA6D08530727AC6D059C005C6C42 | +| 204 | FF47C21142C65B502DA70647BAE831D1 | +| 205 | C83AA7FEAC5E51A08091E10DB0C233D9 | +| 206 | E86EDD2EC2DAA3104229EDC43471A16A | +| 207 | 22FAFB9C184B78B56EE91B6602C03244 | +| 208 | E45631DC509B1290C08D2C1A1F15DBFE | +| 209 | D203C51207092B56568FDAD9E2D44473 | +| 210 | 2AA87F31A7D1AB1C90024F936006C4A5 | +| 211 | 913136153593DEABC7305BF0C5A62180 | +| 212 | D8DA5FE401F2758642A082C53A6A5CB8 | +| 213 | 23C2295213147F324DE8EC1C103BAE88 | +| 214 | 883AF097FCDE82B366A1844245E0D727 | +| 215 | 79E5E9F8C933159ACADC22A06F900A70 | +| 216 | FE40502B44A9E44B2C336250D47538CC | +| 217 | 670452E19172C843176F1278FE41D584 | +| 218 | B7EAA436078E6886A3024F593AD57580 | + +| | | +|-----|----------------------------------| +| 219 | 1044D4CDD7230E7B1953AD1232DF07E2 | +| 220 | 4D821ECAC3D845A2E1011695624576FF | +| 221 | 96622ED2FBD44D1B859D70601999F438 | +| 222 | CCC31C3D6D5B41B8D82FF4522A4C0146 | +| 223 | 4A84F7CD62E0C712980E6A0C89BF394F | +| 224 | 10E56751F000927284DBE174E68ECC4C | +| 225 | A3DE70921356F026E084CFE302A210A9 | +| 226 | B12DA0621B343A8C3FE941A32EA5D571 | +| 227 | D653135DE825A74B743E275C19020C71 | +| 228 | 5CAD301BF846B2EE921D33A3D4BB1220 | +| 229 | 1292445ACBB548C668FC3853578474E6 | +| 230 | B94B4B89C0654688C9E007D9061DF5FE | +| 231 | 75A2C91E76061A8680884E8BFD14A64A | +| 232 | 83726F3070B47ECE21504A5065D74A36 | +| 233 | 964A471444A270840919F7FE07382D14 | +| 234 | A582701EBFCA899B8497088C3560F300 | +| 235 | 64FCB63E21CAC63002D1E09FD1543274 | +| 236 | B1E1C83F689ADF422C865F98D288838A | +| 237 | A06A0D822165D3F3416B47419ECCB547 | +| 238 | 1D2068039A32B7EF728914ECE07CB416 | +| 239 | 64C0CF81F78E8823ECC8661A5295422A | +| 240 | 902A7243F593F2180E5A306A8438E6A9 | +| 241 | A4CCED356D56BF1B41C28E1504301FE8 | +| 242 | 82AE90E2F76B3055A2E3A966025CC01A | +| 243 | 8B90D5A62364E18574145C5895CEFF60 | +| 244 | 43F7EA1AB0D19032551AD9DE21307353 | +| 245 | DD5D8424AC60360B1C14E65815C9B15E | +| 246 | C632A67382ECB2681DFB8525140E2878 | +| 247 | 3A6ACF212B6F8B9C53FF224C2E00C16C | +| 248 | 86A90C267B1171093F362FE5CB14E3A0 | +| 249 | EA262EC36E6589C3BB005426AF2590F4 | +| 250 | 200F03126C5B0D7B901128E7757C5F70 | +| 251 | 68FC090C2221AA98BF0D24E85066EFC2 | +| 252 | 9E26CEC67832FC42A87E92FA1015212E | +| 253 | ACD889634F79506F2582EA03240F2A07 | +| 254 | AA65407E1F4A33BF9A62860A3D6A4CC0 | +| 255 | B1B950AC76A608AA32D04B03C7FF24D3 | + +# Annex B (informative): Generalised Hierarchical Golay Sequences + +## B.1 Alternative generation + +The generalised hierarchical Golay sequences for the PSC described in 7.1 may be also viewed as generated (in real valued representation) by the following methods: + +### Method 1. + +The sequence $y$ is constructed from two constituent sequences $x_1$ and $x_2$ of length $n_1$ and $n_2$ respectively using the following formula: + +$$- y(i) = x_2(i \bmod n_2) * x_1(i \bmod n_1), i = 0 \dots (n_1 * n_2) - 1.$$ + +The constituent sequences $x_1$ and $x_2$ are chosen to be the following length 16 (i.e. $n_1 = n_2 = 16$ ) sequences: + +- $x_1$ is defined to be the length 16 ( $N^{(1)}=4$ ) Golay complementary sequence obtained by the delay matrix $D^{(1)} = [8, 4, 1, 2]$ and weight matrix $W^{(1)} = [1, -1, 1, 1]$ . +- $x_2$ is a generalised hierarchical sequence using the following formula, selecting $s=2$ and using the two Golay complementary sequences $x_3$ and $x_4$ as constituent sequences. The length of the sequence $x_3$ and $x_4$ is called $n_3$ respectively $n_4$ . +- $x_2(i) = x_4(i \bmod s + s * (i \bmod n_3)) * x_3((i \bmod s) \bmod n_3), i = 0 \dots (n_3 * n_4) - 1.$ +- $x_3$ and $x_4$ are defined to be identical and the length 4 ( $N^{(3)}=N^{(4)}=2$ ) Golay complementary sequence obtained by the delay matrix $D^{(3)} = D^{(4)} = [1, 2]$ and weight matrix $W^{(3)} = W^{(4)} = [1, 1]$ . + +The Golay complementary sequences $x_1, x_3$ and $x_4$ are defined using the following recursive relation: + +$$a_0(k) = \delta(k) \text{ and } b_0(k) = \delta(k);$$ + +$$a_n(k) = a_{n-1}(k) + W_n^{(j)} \cdot b_{n-1}(k - D_n^{(j)});$$ + +$$b_n(k) = a_{n-1}(k) - W_n^{(j)} \cdot b_{n-1}(k - D_n^{(j)});$$ + +$$k = 0, 1, 2, \dots, 2^{N^{(j)}} - 1;$$ + +$$n = 1, 2, \dots, N^{(j)}.$$ + +The wanted Golay complementary sequence $x_j$ is defined by $a_n$ assuming $n=N^{(j)}$ . The Kronecker delta function is described by $\delta$ , $k, j$ and $n$ are integers. + +### Method 2 + +The sequence $y$ can be viewed as a pruned Golay complementary sequence and generated using the following parameters which apply to the generator equations for $a$ and $b$ above: + +- (a) Let $j = 0, N^{(0)} = 8$ . +- (b) $[D_1^0, D_2^0, D_3^0, D_4^0, D_5^0, D_6^0, D_7^0, D_8^0] = [128, 64, 16, 32, 8, 1, 4, 2]$ . +- (c) $[W_1^0, W_2^0, W_3^0, W_4^0, W_5^0, W_6^0, W_7^0, W_8^0] = [1, -1, 1, 1, 1, 1, 1, 1]$ . +- (d) For $n = 4, 6$ , set $b_4(k) = a_4(k), b_6(k) = a_6(k)$ . + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|--------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99593 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99696 | 001 | 01 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99695 | 003 | 1 | Alignment of Terminology Regarding Spreading for TDD Mode | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99696 | 004 | - | Code allocation for Case 3 | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000069 | 002 | 3 | Cycling of cell parameters | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000069 | 005 | - | Removal of Synchronisation Case 3 in TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000069 | 006 | 1 | Signal Point Constellation | 3.1.1 | 3.2.0 | +| 03/05/00 | - | - | - | | Revision marks accepted to create clean version | 3.2.0 | 3.2.1 | +| 26/06/00 | RAN_08 | RP-000273 | 008 | - | Editorial Modifications for 25.223 | 3.2.1 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000273 | 009 | - | Editorial modification of 25.223 | 3.2.1 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000273 | 010 | - | Editorial modification of 25.223 | 3.2.1 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000273 | 011 | 2 | Editorial modification of 25.223 | 3.2.1 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000273 | 012 | 2 | Modified code sets on SCH for cell search in UTRA TDD | 3.2.1 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000273 | 013 | 1 | Editorial update of TS25.223 | 3.2.1 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000346 | 007 | 1 | Gain Factors for TDD Mode | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000346 | 014 | - | Synchronisation codes | 3.3.0 | 3.4.0 | +| 16/03/01 | RAN_11 | - | - | | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.4.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010064 | 015 | 1 | Code specific phase offsets for TDD | 3.4.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010073 | 016 | - | Cell synchronisation codes for R'4 Node B sync over air interface in UTRA TDD | 3.4.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 017 | 1 | Inclusion of 1.28Mcps TDD in TS 25.223 | 3.4.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010337 | 019 | - | Addition to the abbreviation list and definition of a constant | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010524 | 021 | 1 | Clarification of notations in TS25.221 and TS25.223 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010530 | 022 | 1 | Clarification of notations in TS25.221 and TS25.223 | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010748 | 023 | - | A correction of Figure 7 in subclause 7.7.2 of TS 25.223 | 4.2.0 | 4.3.0 | +| 08/03/03 | RAN_15 | RP-020051 | 025 | 1 | Removal of quantisation of bj gain factor when calculated from a reference TFC | 4.3.0 | 4.4.0 | +| 08/03/03 | RAN_15 | RP-020051 | 028 | - | Channelisation code-specific multiplier operation under autonomous SF change | 4.3.0 | 4.4.0 | +| 08/03/03 | RAN_15 | RP-020051 | 030 | - | Alignment of gamma(i) gains of 25.223 with SIR target of WG2 25.331 | 4.3.0 | 4.4.0 | +| 08/03/03 | RAN_15 | RP-020058 | 026 | 1 | CR to include HSDPA in TS25.223 | 4.4.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020317 | 031 | - | Correction of SPC for 16QAM in TDD | 5.0.0 | 5.1.0 | +| 22/12/02 | RAN_18 | RP-020852 | 033 | - | Editorial modification to the section numberings | 5.1.0 | 5.2.0 | +| 25/03/03 | RAN_19 | RP-030140 | 034 | 3 | Miscellaneous Corrections | 5.2.0 | 5.3.0 | +| 13/01/04 | RAN_22 | - | - | | Created for M.1457 update | 5.3.0 | 6.0.0 | +| 12/12/05 | RAN_30 | RP-050728 | 0037 | - | Correction to 16QAM modulation function | 6.0.0 | 6.1.0 | +| 20/03/06 | RAN_31 | RP-060079 | 0038 | - | Introduction of 7.68Mcps TDD option | 6.1.0 | 7.0.0 | +| 12/06/06 | RAN_32 | RP-060295 | 0040 | - | Correction of the values of weight factors | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | RP-060492 | 0041 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.1.0 | 7.2.0 | +| 13/03/07 | RAN_35 | RP-070118 | 0042 | 1 | Introduction of E-DCH for 1.28Mcps TDD | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070385 | 0043 | 1 | Support for MBSFN operation | 7.3.0 | 7.4.0 | +| 30/05/07 | RAN_36 | RP-070386 | 0045 | - | Support for 1.28Mcps TDD MBSFN operation | 7.3.0 | 7.4.0 | +| 11/09/07 | RAN_37 | RP-070650 | 0046 | 1 | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.4.0 | 7.5.0 | +| 27/11/07 | RAN_38 | RP-070943 | 0049 | 1 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | - | - | | Creation of Release 8 further to RAN_39 decision | 7.6.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080356 | 0052 | - | Introduction the 64QAM constellation for 1.28 Mcps TDD HSDPA | 8.0.0 | 8.1.0 | +| 28/05/08 | RAN_40 | RP-080347 | 0054 | - | Correction of uplink multicode capability for 1.28 Mcps TDD EUL | 8.0.0 | 8.1.0 | +| 03/12/08 | RAN_42 | RP-081118 | 0056 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.1.0 | 8.2.0 | +| 03/03/09 | RAN_43 | RP-090239 | 0057 | - | TFCI for Secondary CCPCH frame type 2 with 16QAM | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090239 | 0058 | - | Specification of scrambling codes and code groups for MBSFN IMB | 8.2.0 | 8.3.0 | +| 26/05/09 | RAN_44 | RP-090531 | 0059 | - | Minor correction for MBSFN IMB | 8.3.0 | 8.4.0 | +| 01/12/09 | RAN_46 | - | - | | Creation of Release 9 (v9.0.0) at RAN#46 | 8.4.0 | 9.0.0 | +| 07/12/10 | RAN_50 | RP-101317 | 0062 | 2 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.0.0 | 10.0.0 | +| 07/12/10 | RAN_50 | RP-101319 | 0063 | 1 | Introduction of MU-MIMO for 1.28Mcps TDD | 9.0.0 | 10.0.0 | +| 15/09/11 | RAN_53 | RP-111225 | 0066 | 2 | Clarification of 64QAM for LCR TDD | 10.0.0 | 10.1.0 | +| 2012-09 | SP_57 | - | - | | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | +| 2014-09 | SP_65 | - | - | | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | SP_70 | - | - | | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25224/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-16/25_series/25224/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0fd05ebf2af65b43f8d79431a343c1b00c24046 --- /dev/null +++ b/marked/Rel-16/25_series/25224/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ff04ef6425a13f3e9b79efb3297e54baf0103e62eb9d82766c56e2133cdccf8 +size 14940 diff --git a/marked/Rel-16/25_series/25224/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-16/25_series/25224/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d538969c783aad314ad35263fb68c7053b6debc6 --- /dev/null +++ b/marked/Rel-16/25_series/25224/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5593504c73384e4e8ee020534103ce1cf8ffe0a0ef102f38deaacc620de5dab +size 60687 diff --git a/marked/Rel-16/25_series/25224/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-16/25_series/25224/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01de32eaabc6dfe6a40a66009150925cabc6babc --- /dev/null +++ b/marked/Rel-16/25_series/25224/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65576596cf3f3f81ea74d69005e5ae0e9439e0286a291bb0a2dc2bbcf6e42312 +size 93310 diff --git a/marked/Rel-16/25_series/25224/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-16/25_series/25224/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cbd883775d573ac788e37f96df7948350e6de7f --- /dev/null +++ b/marked/Rel-16/25_series/25224/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78227f3c5fc92803af70750a30a76410f51fb53e827210b72efe91e4f72285d0 +size 28602 diff --git a/marked/Rel-16/25_series/25224/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/25_series/25224/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9faa154a401c8532ec21c421c7b1c64afdbaeaef --- /dev/null +++ b/marked/Rel-16/25_series/25224/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dab5d92d33f11d39b261a92f1b7edadfb4aef0afccda5f28507d311c06f51f4a +size 23756 diff --git a/marked/Rel-16/25_series/25224/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg b/marked/Rel-16/25_series/25224/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98003175de96df8e17ae5966bb5e786e034a3912 --- /dev/null +++ b/marked/Rel-16/25_series/25224/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bf385e62443677dedc8dd42b9cc01e0bf08641d06005bea0a019765d5fb48ee +size 8976 diff --git a/marked/Rel-16/25_series/25224/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/25_series/25224/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c54a5ecd86bf2d47a5f8d71bece955c08049fb7f --- /dev/null +++ b/marked/Rel-16/25_series/25224/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b67f9d94a80be818d75b7ed2af6abfaa7ee0850551ed940758d511336f074fe +size 25284 diff --git a/marked/Rel-16/25_series/25224/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-16/25_series/25224/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da90295c6cd15b75dfdd63da705541adaa4ebfd --- /dev/null +++ b/marked/Rel-16/25_series/25224/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30fc6ed43c40e60f8ecf5ec32752c22729a1593cf27663329d18b566d5ee95e7 +size 17367 diff --git a/marked/Rel-16/25_series/25224/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25224/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..688dc7e013130df86dddc59dce6a02fa1bca0720 --- /dev/null +++ b/marked/Rel-16/25_series/25224/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7866d5a12f9ec12ad8174d8fe10ee5d754a1f95353f5eb3b49eb731e50438cc0 +size 88271 diff --git a/marked/Rel-16/25_series/25224/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/25_series/25224/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3beac2c5c987acd32e56c646db784f4ffda97754 --- /dev/null +++ b/marked/Rel-16/25_series/25224/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07f0d3c60f835e6a87e3c7269288406d6492924f2d4d1994c5fd77b8f0e8f6bc +size 24913 diff --git a/marked/Rel-16/25_series/25224/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/25_series/25224/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..162f5b10805d48d6b3f2d73c9876906c2b642f40 --- /dev/null +++ b/marked/Rel-16/25_series/25224/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56d10f588bb2615b059445f7b9c2d174bb4a6899fb421ee2f22502494afe9ffa +size 38148 diff --git a/marked/Rel-16/25_series/25224/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-16/25_series/25224/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ca185933826878b852029067e047646418c71d0 --- /dev/null +++ b/marked/Rel-16/25_series/25224/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd8531e548036e83fa4607a2b094a6e8dc3d25e027ef4c9af6a8b9faae2b1ce2 +size 53668 diff --git a/marked/Rel-16/25_series/25224/daae5239bb53d468ea958aedfc2e6070_img.jpg b/marked/Rel-16/25_series/25224/daae5239bb53d468ea958aedfc2e6070_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6bd0dbbc315621178e4ee93ffe307ce6f8ad057 --- /dev/null +++ b/marked/Rel-16/25_series/25224/daae5239bb53d468ea958aedfc2e6070_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa9051d96ee694ae6ac64309b3a2a537a2fc718b3851f2d3070cffd773a0ab4f +size 24762 diff --git a/marked/Rel-16/25_series/25224/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/25_series/25224/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c82962d9bc0f84af1dc6bb9e0d56049545eca94 --- /dev/null +++ b/marked/Rel-16/25_series/25224/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:938c40dd4510b032acdcbffb30bab059705c38f83b2891c870106db5c6c4be1a +size 25980 diff --git a/marked/Rel-16/25_series/25224/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/25_series/25224/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e01df88498aacfd5ee85938be6a444c784e1aeea --- /dev/null +++ b/marked/Rel-16/25_series/25224/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c863c853119c969c3d08b3b50c0ff86b0e80981a889d8d86d532a10ccb69be1 +size 39764 diff --git a/marked/Rel-16/25_series/25224/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25224/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1390b46e1055174d9adf7ec14f9287ed1204a7f3 --- /dev/null +++ b/marked/Rel-16/25_series/25224/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc9b2455c305f718e752050797173b222306db01446a0dc6f741ffe3bf664e3e +size 14430 diff --git a/marked/Rel-16/25_series/25224/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/25_series/25224/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d08ed4f3c32aa00f9ceca184e1545634b9349c4 --- /dev/null +++ b/marked/Rel-16/25_series/25224/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb2547e5baf7d6d8b24b3b4aa4fe25c1e373d7fb790ee2f33ba66063194e4eea +size 17825 diff --git a/marked/Rel-16/25_series/25224/raw.md b/marked/Rel-16/25_series/25224/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fb22ca628f9b57f95d803a15360d1c9b4e9f7be0 --- /dev/null +++ b/marked/Rel-16/25_series/25224/raw.md @@ -0,0 +1,3155 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Abbreviations..... | 10 | +| 4 Physical layer procedures for the 3.84 Mcps option..... | 11 | +| 4.1 General..... | 11 | +| 4.2 Transmitter power control..... | 11 | +| 4.2.1 General parameters..... | 11 | +| 4.2.2 Uplink control..... | 11 | +| 4.2.2.1 General limits..... | 11 | +| 4.2.2.2 PRACH..... | 12 | +| 4.2.2.3 DPCH, PUSCH and HS-SICH..... | 12 | +| 4.2.2.3.1 Gain factors..... | 12 | +| 4.2.2.3.2 Out of synchronisation handling..... | 13 | +| 4.2.2.4 E-PUCH..... | 13 | +| 4.2.2.4.1 Gain factors for E-PUCH..... | 14 | +| 4.2.2.5 E-RUCCH..... | 15 | +| 4.2.3 Downlink control..... | 15 | +| 4.2.3.1 P-CCPCH..... | 15 | +| 4.2.3.2 S-CCPCH, PICH..... | 15 | +| 4.2.3.2A MICH..... | 15 | +| 4.2.3.3 SCH..... | 16 | +| 4.2.3.3A PNBSCH..... | 16 | +| 4.2.3.4 DPCH, PDSCH..... | 16 | +| 4.2.3.4.1 Out of synchronisation handling..... | 17 | +| 4.2.3.5 HS-PDSCH..... | 17 | +| 4.2.3.6 HS-SCCH..... | 17 | +| 4.2.3.7 E-AGCH..... | 17 | +| 4.2.3.8 E-HICH..... | 17 | +| 4.3 Timing advance..... | 17 | +| 4.4 Synchronisation procedures..... | 18 | +| 4.4.1 Cell search..... | 18 | +| 4.4.2 Dedicated channel synchronisation..... | 18 | +| 4.4.2.1 Synchronisation primitives..... | 18 | +| 4.4.2.1.1 General..... | 18 | +| 4.4.2.1.2 Downlink synchronisation primitives..... | 18 | +| 4.4.2.1.2A Downlink synchronisation primitives for HS-channels..... | 19 | +| 4.4.2.1.3 Uplink synchronisation primitives..... | 19 | +| 4.4.2.2 Radio link monitoring..... | 20 | +| 4.4.2.2.1 Downlink radio link failure..... | 20 | +| 4.4.2.2.2 Uplink radio link failure/restore..... | 20 | +| 4.5 Discontinuous transmission (DTX) procedure..... | 20 | +| 4.5.1 Description of special bursts..... | 20 | +| 4.5.2 Use of special bursts during DTX..... | 21 | +| 4.5.3 Use of special bursts for initial establishment / reconfiguration..... | 21 | +| 4.5.4 Use of special bursts for DTX on beacon channels..... | 21 | +| 4.6 Downlink transmit diversity..... | 21 | +| 4.6.1 Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH..... | 21 | +| 4.6.2 Transmit diversity for SCH and S-CCPCH..... | 22 | +| 4.6.2.1 SCH transmission scheme..... | 22 | +| 4.6.2.2 S-CCPCH transmission scheme..... | 23 | +| 4.6.3 Transmit diversity for beacon channels..... | 23 | +| 4.6.3.1 SCTD transmission scheme..... | 23 | +| 4.7 Random access procedure..... | 24 | +| 4.7.1 Physical random access procedure..... | 24 | +| 4.7A E-RUCCH transmission procedure..... | 25 | + +| | | | +|-----------|-----------------------------------------------------------------------|----| +| 4.8 | DSCH procedure..... | 25 | +| 4.8.1 | DSCH procedure with TFCI indication..... | 25 | +| 4.8.2 | DSCH procedure with midamble indication..... | 26 | +| 4.9 | Node B synchronisation procedure over the air..... | 26 | +| 4.9.1 | Frequency acquisition phase..... | 26 | +| 4.9.2 | Initial synchronisation..... | 26 | +| 4.9.3 | Steady-state phase..... | 26 | +| 4.9.4 | Late entrant cells..... | 26 | +| 4.10 | Idle periods for IPDL location method..... | 27 | +| 4.10.1 | General..... | 27 | +| 4.10.2 | Parameters of IPDL..... | 27 | +| 4.10.3 | Calculation of idle period position..... | 27 | +| 4.11 | HS-DSCH procedure..... | 28 | +| 4.11.1 | Link adaptation procedure..... | 28 | +| 4.11.2 | HS-DSCH channel quality indication procedure..... | 29 | +| 4.12 | Macro-diversity procedure..... | 30 | +| 4.13 | E-DCH related procedures..... | 30 | +| 4.13.1 | ACK/NACK detection..... | 30 | +| 4.13.2 | Serving and neighbour cell pathloss metric derivation..... | 30 | +| 4.13.3 | Channelisation code hopping procedure for E-PUCH..... | 31 | +| 4.14 | Physical layer procedures for 3.84 Mcps MBSFN IMB..... | 33 | +| 4.14.1 | Radio frame timing on the MBSFN layer..... | 33 | +| 4.14.2 | Downlink power control..... | 33 | +| 4.14.2.1 | S-CCPCH..... | 33 | +| 4.14.2.2 | MICH..... | 33 | +| 4.14.2.3 | P-CPICH..... | 34 | +| 4.14.2.4 | T-CPICH..... | 34 | +| 5 | Physical layer procedures for the 1.28 Mcps option..... | 34 | +| 5.1 | Transmitter power control..... | 34 | +| 5.1.1 | Uplink control..... | 34 | +| 5.1.1.1 | General limits..... | 34 | +| 5.1.1.2 | UpPCH..... | 34 | +| 5.1.1.3 | PRACH..... | 35 | +| 5.1.1.4 | DPCH and PUSCH..... | 35 | +| 5.1.1.4.1 | Gain factors..... | 35 | +| 5.1.1.4.2 | Out of synchronization handling..... | 35 | +| 5.1.1.5 | HS-SICH..... | 36 | +| 5.1.1.6 | E-PUCH..... | 36 | +| 5.1.1.6.1 | Gain factors for E-PUCH..... | 37 | +| 5.1.1.7 | E-RUCCH..... | 39 | +| 5.1.1.8 | Standalone midamble channel..... | 39 | +| 5.1.2 | Downlink control..... | 39 | +| 5.1.2.1 | P-CCPCH..... | 39 | +| 5.1.2.2 | The power of the FPACH..... | 39 | +| 5.1.2.3 | S-CCPCH, PICH..... | 39 | +| 5.1.2.3A | MICH..... | 39 | +| 5.1.2.4 | DPCH, PDSCH..... | 39 | +| 5.1.2.4.1 | Out of synchronisation handling..... | 40 | +| 5.1.2.5 | HS-PDSCH..... | 40 | +| 5.1.2.6 | HS-SCCH..... | 40 | +| 5.1.2.7 | PLCCH..... | 40 | +| 5.1.2.8 | E-AGCH..... | 40 | +| 5.1.2.9 | E-HICH..... | 41 | +| 5.2 | UL synchronisation..... | 41 | +| 5.2.1 | General description..... | 41 | +| 5.2.1.1 | Preparation of uplink synchronization (downlink synchronization)..... | 41 | +| 5.2.1.2 | Establishment of uplink synchronization..... | 41 | +| 5.2.1.3 | Maintenance of uplink synchronisation..... | 41 | +| 5.2.2 | UpPCH..... | 42 | +| 5.2.3 | PRACH..... | 42 | +| 5.2.4 | DPCH and PUSCH..... | 42 | + +| | | | +|------------|--------------------------------------------------------------------------------|----| +| 5.2.4.1 | Out of synchronization handling..... | 43 | +| 5.2.5 | HS-SICH..... | 43 | +| 5.2.6 | E-PUCH..... | 43 | +| 5.2.7 | E-RUCCH..... | 43 | +| 5.2.8 | Standalone midamble channel..... | 44 | +| 5.3 | Synchronisation procedures..... | 44 | +| 5.3.1 | Cell search..... | 44 | +| 5.3.2 | DCH synchronization..... | 44 | +| 5.3.2A | Shared physical channel synchronization..... | 44 | +| 5.3.2A.1 | Synchronisation primitives..... | 44 | +| 5.3.2A.1.1 | General..... | 44 | +| 5.3.2A.1.2 | Downlink synchronisation primitives..... | 44 | +| 5.3.2A.1.3 | Uplink synchronisation primitives..... | 45 | +| 5.3.2A.2 | Radio link monitoring..... | 45 | +| 5.3.2A.2.1 | Downlink radio link failure..... | 45 | +| 5.3.2A.2.2 | Uplink radio link failure/restore..... | 45 | +| 5.3.3 | Synchronization procedure in CELL_FACH state..... | 45 | +| 5.3.3.1 | Uplink synchronization status detection..... | 45 | +| 5.3.3.2 | Establishment of uplink synchronization..... | 46 | +| 5.4 | Discontinuous transmission (DTX) procedure..... | 46 | +| 5.4.1 | Description of special bursts..... | 46 | +| 5.4.2 | Use of special bursts during DTX..... | 46 | +| 5.4.3 | Use of special bursts for initial establishment / reconfiguration..... | 47 | +| 5.5 | Downlink transmit diversity..... | 47 | +| 5.5.1 | Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH..... | 47 | +| 5.5.1.1 | TSTD for PDSCH and DPCH..... | 47 | +| 5.5.1.2 | Closed loop Tx diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH..... | 48 | +| 5.5.2 | Transmit diversity for DwPCH..... | 48 | +| 5.5.3 | Transmit diversity for P-CCPCH..... | 49 | +| 5.5.3.1 | TSTD transmission scheme for P-CCPCH..... | 49 | +| 5.5.4 | SCTD transmission scheme for beacon channels..... | 49 | +| 5.6 | Random access procedure..... | 50 | +| 5.6.1 | Definitions..... | 50 | +| 5.6.1A | UpPCH sub-channel..... | 50 | +| 5.6.2 | Preparation of random access..... | 51 | +| 5.6.3 | Random access procedure..... | 52 | +| 5.6.3.1 | The use and generation of the information fields transmitted in the FPACH..... | 53 | +| 5.6.3.1.1 | Signature reference number..... | 53 | +| 5.6.3.1.2 | Relative sub-frame number..... | 53 | +| 5.6.3.1.3 | Received starting position of the UpPCH (UpPCH pos )..... | 54 | +| 5.6.3.1.4 | Transmit power level command for the RACH message..... | 54 | +| 5.6.3A | E-RUCCH procedure..... | 54 | +| 5.6.4 | Random access collision..... | 55 | +| 5.7 | Node B synchronisation procedure over the air..... | 55 | +| 5.7.1 | Initial synchronisation..... | 55 | +| 5.7.2 | Steady-state phase..... | 55 | +| 5.7.3 | Late entrant cells..... | 55 | +| 5.8 | Idle periods for IPDL location method..... | 56 | +| 5.8.1 | General..... | 56 | +| 5.8.2 | Parameters of IPDL..... | 56 | +| 5.8.3 | Calculation of idle period position..... | 56 | +| 5.9 | HS-DSCH procedure in CELL_DCH state..... | 57 | +| 5.9.1 | Link adaptation procedure..... | 57 | +| 5.9.2 | HS-DSCH channel quality indication procedure..... | 58 | +| 5.9.3 | HS-SCCH monitoring procedure..... | 59 | +| 5.9A | HS-DSCH procedure in CELL_FACH state..... | 59 | +| 5.9A.1 | Link adaptation procedure..... | 59 | +| 5.9A.2 | HS-DSCH channel quality indication procedure..... | 60 | +| 5.9A.3 | HS-SCCH monitoring procedure..... | 60 | +| 5.9B | HS-DSCH procedure in CELL_PCH or URA_PCH state..... | 60 | +| 5.9B.1 | Link adaptation procedure..... | 60 | + +| | | | +|---------|-----------------------------------------------------------------------|----| +| 5.9B.2 | HS-DSCH channel quality indication procedure..... | 61 | +| 5.9B.3 | HS-SCCH monitoring procedure..... | 61 | +| 5.10 | Macro-diversity procedure..... | 61 | +| 5.11 | E-DCH Procedure..... | 61 | +| 5.11.1 | ACK/NACK detection..... | 61 | +| 5.11.2 | Serving and neighbour cell pathloss metric derivation..... | 62 | +| 5.11.3 | E-AGCH monitoring in CELL_DCH state..... | 63 | +| 5.11.3A | E-AGCH monitoring in CELL_FACH state..... | 63 | +| 5.12 | MIMO operation of HS-DSCH..... | 63 | +| 5.12.1 | General procedure..... | 63 | +| 5.12.2 | Identification of MIMO dual stream..... | 64 | +| 5.12.3 | UE antennas time switched transmission..... | 64 | +| 5.12A | MU-MIMO operation of HS-DSCH and E-DCH..... | 65 | +| 5.13 | Control channel discontinuous reception procedures..... | 65 | +| 5.13.1 | Discontinuous downlink reception..... | 66 | +| 5.13.2 | HS-SCCH orders..... | 67 | +| 6 | Physical layer procedures for the 7.68 Mcps option..... | 67 | +| 6.1 | Transmitter power control..... | 67 | +| 6.2 | Timing advance..... | 68 | +| 6.3 | Synchronisation procedures..... | 68 | +| 6.4 | Discontinuous transmission (DTX) procedure..... | 68 | +| 6.5 | Downlink transmit diversity..... | 68 | +| 6.5.1 | Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH..... | 68 | +| 6.5.2 | Transmit diversity for SCH and S-CCPCH..... | 68 | +| 6.5.3 | Transmit diversity for Beacon Channels..... | 69 | +| 6.5.3.1 | SCTD transmission scheme..... | 69 | +| 6.6 | Random access procedure..... | 69 | +| 6.6.1 | Physical random access procedure..... | 69 | +| 6.6A | E-RUCCH transmission procedure..... | 69 | +| 6.7 | DSCH procedure..... | 70 | +| 6.8 | Idle periods for IPDL location method..... | 70 | +| 6.9 | HS-DSCH procedure..... | 70 | +| 6.9.1 | Link adaptation procedure..... | 70 | +| 6.9.2 | HS-DSCH channel quality indication procedure..... | 71 | +| 6.10 | Macro-diversity procedure..... | 71 | +| 6.11 | E-DCH related procedures..... | 71 | +| 6.11.1 | ACK/NACK detection..... | 71 | +| 6.11.2 | Serving and neighbour cell pathloss metric derivation..... | 71 | +| 6.11.3 | Channelisation code hopping procedure for E-PUCH..... | 71 | + +**Annex A (informative): Power Control.....73** + +A.1 Example implementation of downlink power control in the UE..... 73 + +A.2 Example implementation of closed loop uplink power control in Node B for 1.28Mcps TDD.....73 + +A.3 Example implementation of downlink power control in UE for 1.28Mcps TDD when TSTD is used..... 73 + +A.4 Example implementation of open loop power control for access procedure for 1.28Mcps TDD.....74 + +A.5 Example implementation of closed loop uplink HS-SICH power control in Node B for 1.28Mcps TDD..... 74 + +**Annex B (informative): Determination of weight information..... 75** + +B.1 STD weights..... 75 + +B.2 TxAA weights..... 75 + +**Annex C (informative): Cell search procedure for 3.84Mcps TDD..... 76** + +**Annex CA (informative): Cell search procedure for 1.28Mcps TDD..... 77** + +**Annex CB (informative): Examples random access procedure for 1.28Mcps TDD.....79** + +Annex D (informative): Change history.....81 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the Physical Layer Procedures in the TDD mode of UTRA. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.201: "Physical layer - general description". +- [2] 3GPP TS 25.102: "UE physical layer capabilities". +- [3] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [4] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [5] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [6] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [7] 3GPP TS 25.215: "Physical Layer - Measurements (FDD)". +- [8] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [9] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [10] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [11] 3GPP TS 25.225: "Physical Layer - Measurements (TDD)". +- [12] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [13] 3GPP TS 25.302: "Services Provided by the Physical Layer". +- [14] 3GPP TS 25.401: "UTRAN Overall Description". +- [15] 3GPP TS 25.331: "RRC Protocol Specification" +- [16] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling" +- [17] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and Reception" +- [18] 3GPP TS 25.321: "MAC protocol specification" +- [19] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode" +- [20] 3GPP TS 25.402: "Synchronisation in UTRAN Stage 2" + +# 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|---------------------------------------------| +| ACK | Acknowledgement | +| ASC | Access Service Class | +| BCCH | Broadcast Control Channel | +| BCH | Broadcast Channel | +| CCTrCH | Coded Composite Transport Channel | +| CDMA | Code Division Multiple Access | +| CQI | Channel Quality Information | +| CRC | Cyclic Redundancy Check | +| DCA | Dynamic Channel Allocation | +| DL | Downlink | +| DPCH | Dedicated Physical Channel | +| DTX | Discontinuous Transmission | +| E-AGCH | E-DCH Absolute Grant Channel | +| ECSN | E-AGCH Cyclic Sequence Number | +| E-DCH | Enhanced Dedicated Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| ENI | E-UCCH Number Indicator | +| E-PUCH | E-DCH Physical Uplink Channel | +| E-RUCCH | E-DCH Random Access Uplink Control Channel | +| E-UCCH | E-DCH Uplink Control Channel | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Channel for HS-DSCH | +| HS-SICH | Shared Information Channel for HS-DSCH | +| IMB | Integrated Mobile Broadcast | +| ISCP | Interference Signal Code Power | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast/Multicast Service | +| MBSFN | MBMS over a Single Frequency Network | +| MICH | MBMS Indicator Channel | +| MIMO | single user Multiple Input Multiple Output | +| MS burst | MBSFN Special burst | +| MT burst | MBSFN Traffic burst | +| MU-MIMO | Multi-user Multiple Input Multiple Output | +| NACK | Negative Acknowledgement | +| NRT | Non-Real Time | +| P-CCPCH | Primary Common Control Physical Channel | +| PC | Power Control | +| PDSCH | Physical Downlink Shared Channel | +| PICH | Paging Indicator Channel | +| PLCC | Physical Layer Common Control Channel | +| PRACH | Physical Random Access Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RL | Radio Link | +| RRC | Radio Resource Control | +| RSCP | Received Signal Code Power | +| RT | Real Time | +| RU | Resource Unit | +| SBGP | Special Burst Generation Gap | +| SBP | Special Burst Period | +| SBSP | Special Burst Scheduling Period | +| S-CCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronisation Channel | +| SCTD | Space Code Transmit Diversity | + +| | | +|-------|--------------------------------------------| +| SFN | System Frame Number | +| SIR | Signal-to-Interference Ratio | +| SNPL | Serving and Neighbour cell Pathloss | +| SSCH | Secondary Synchronisation Channel | +| STD | Selective Transmit Diversity | +| TA | Timing Advance | +| TDD | Time Division Duplex | +| TF | Transport Format | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TFCS | Transport Format Combination Set | +| TFRI | Transport Format Resource Indicator | +| TPC | Transmit Power Control | +| TSTD | Time Switched Transmit Diversity | +| TTI | Transmission Time Interval | +| TxAA | Transmit Adaptive Antennas | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| UTRAN | UMTS Radio Access Network | +| VBR | Variable Bit Rate | + +# 4 Physical layer procedures for the 3.84 Mcps option + +## 4.1 General + +Sub-clauses 4.2 to 4.13 do not apply to 3.84 Mcps MBSFN IMB operation. Physical layer procedures for 3.84 Mcps MBSFN IMB operation are described in sub-clause 4.14. + +## 4.2 Transmitter power control + +### 4.2.1 General parameters + +Power control is applied for the TDD mode to limit the interference level within the system thus reducing the intercell interference level and to reduce the power consumption in the UE. + +All codes within one timeslot allocated to the same CCTrCH use the same transmission power, in case they have the same spreading factor. + +**Table 1: Transmit Power Control characteristics** + +| | Uplink | Downlink | +|---------------------------|---------------------------------------------------------------------------|-------------------------------------------------------| +| Power control rate | Variable
1-7 slots delay (2 slot SCH)
1-14 slots delay (1 slot SCH) | Variable, with rate depending on the slot allocation. | +| TPC Step size | -- | 1dB or 2 dB or 3 dB | +| Remarks | All figures are without processing and measurement times | | + +### 4.2.2 Uplink control + +#### 4.2.2.1 General limits + +During the operation of the uplink power control procedure the UE transmit power shall not exceed a maximum allowed value which is the lower out of the maximum output power of the terminal power class and a value which may be set by higher layer signalling. + +Uplink power control shall be performed while the total UE transmit power is below the maximum allowed output power. In some cases the total UE transmit power in a timeslot after uplink power control calculation might exceed the maximum allowed output power. In these cases the calculated transmit power of all uplink physical channels in this + +timeslot shall be scaled by the same amount in dB before transmission. The total UE transmission power used shall be the maximum allowed output power. + +The UTRAN may not expect the UE to be capable of reducing its total transmit power below the minimum level specified in [2]. + +#### 4.2.2.2 PRACH + +The transmit power for the PRACH is set by higher layers based on open loop power control as described in [15]. + +#### 4.2.2.3 DPCH, PUSCH and HS-SICH + +The transmit power for DPCH, PUSCH and HS-SICH is set by higher layers based on open loop power control as described in [15]. + +In the case that an ACK is being transmitted on the HS-SICH, the UE shall apply a power offset to the transmit power of the entire HS-SICH. This power offset shall be signalled by higher layers. + +##### 4.2.2.3.1 Gain factors + +Two or more transport channels may be multiplexed onto a CCTrCH as described in [9]. These transport channels undergo rate matching which involves repetition or puncturing. This rate matching affects the transmit power required to obtain a particular $E_b/N_0$ . Thus, the transmission power of the CCTrCH shall be weighted by a gain factor $\beta$ . + +There are two ways of controlling the gain factors for different TFC's within a CCTrCH transmitted in a radio frame: + +- $\beta$ is signalled for the TFC, or +- $\beta$ is computed for the TFC, based upon the signalled settings for a reference TFC. + +Combinations of the two above methods may be used to associate $\beta$ values to all TFC's in the TFCs for a CCTrCH. The two methods are described in sections 4.2.2.3.1.1 and 4.2.2.3.1.2 respectively. Several reference TFC's for several different CCTrCH's may be signalled from higher layers. + +The weight and gain factors may vary on a radio frame basis depending upon the current SF and TFC used. The setting of weight and gain factors is independent of any other form of power control. That means that the transmit power $P_{UL}$ is calculated according to the formula given in [15] and then the weight and gain factors are applied on top of that, cf. [10]. + +###### 4.2.2.3.1.1 Signalled gain factors + +When the gain factor $\beta_j$ is signalled by higher layers for a certain TFC, the signalled values are used directly for weighting DPCH or PUSCH within a CCTrCH. Exact values are given in [10]. + +###### 4.2.2.3.1.2 Computed gain factors + +The gain factor $\beta_j$ may also be computed for certain TFCs, based on the signalled settings for a reference TFC: + +Let $\beta_{ref}$ denote the signalled gain factor for the reference TFC. Further, let $\beta_j$ denote the gain factor used for the $j$ -th TFC. + +$$K_{ref} = \sum_i RM_i \cdot N_i$$ + +Define the variable: + +where $RM_i$ is the semi-static rate matching attribute for transport channel $i$ , $N_i$ is the number of bits output from the radio frame segmentation block for transport channel $i$ and the sum is taken over all the transport channels $i$ in the reference TFC. + +$$K_j = \sum_i RM_i \cdot N_i$$ + +Similarly, define the variable + +where the sum is taken over all the transport channels $i$ in the $j$ -th TFC. + +$$L_{ref} = \sum_i \frac{1}{SF_i}$$ + +Moreover, define the variable + +where $SF_i$ is the spreading factor of DPCH or PUSCH $i$ and the sum is taken over all DPCH or PUSCH $i$ used in the reference TFC. + +$$L_j = \sum_i \frac{1}{SF_i}$$ + +Similarly, define the variable + +where the sum is taken over all DPCH or PUSCH $i$ used in the $j$ -th TFC. + +The gain factors $\beta_j$ for the $j$ -th TFC are then computed as follows: + +No quantisation of $\beta_j$ is performed and as such, values other than the quantised $\beta_j$ given in [10] may be used. + +##### 4.2.2.3.2 Out of synchronisation handling + +As stated in 4.2.3.4, the association between TPC commands sent on uplink DPCH and PUSCH, with the power controlled downlink DPCH and PDSCH is signaled by higher layers. In the case of multiple DL CCTrCHs it is possible that an UL CCTrCH will provide TPC commands to more than one DL CCTrCH. + +In the second phase of synchronisation evaluation, as defined in 4.4.2.1.2, the UE shall shut off the transmission of an UL CCTrCH if the following criteria are fulfilled for any one of the DL CCTrCHs commanded by its TPC: + +- The UE estimates the received dedicated channel burst quality over the last 160 ms period to be worse than a threshold $Q_{out}$ , and in addition, no special burst, as defined in 4.5, is detected with quality above a threshold, $Q_{sbout}$ . $Q_{out}$ and $Q_{sbout}$ are defined implicitly by the relevant tests in [2]. If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation period for the burst quality evaluation and for the Special Burst detection window. + +UE shall subsequently resume the uplink transmission of the CCTrCH if the following criteria are fulfilled: + +- The UE estimates the received dedicated CCTrCH burst reception quality over the last 160 ms period to be better than a threshold $Q_{in}$ or the UE detects a burst with quality above threshold $Q_{sbin}$ and TFCI decoded to be that of the Special Burst. $Q_{in}$ and $Q_{sbin}$ are defined implicitly by the relevant tests in [2]. If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation period for the burst quality evaluation and for the Special Burst detection window. + +#### 4.2.2.4 E-PUCH + +The power of E-PUCH is set based upon the sum of: + +1. An open loop component based upon beacon channel pathloss and on the E-PUCH constant value signalled by higher layers ( $K_{E-PUCH}$ ). +2. A closed-loop TPC component. One TPC bit is signalled to the UE within each E-AGCH. The TPC command is derived by Node-B. +3. An adjustment factor ( $\beta_e$ ) accounting for the E-TFC selected by the UE and the HARQ offset. + +The transmit power of the E-PUCH is calculated in the UE as follows: + +... where: + +- $P_{e-base}$ is a closed-loop quantity maintained by the UE and which is incremented or decremented by a value $\Delta_{e-base}$ upon each receipt of a TPC command on E-AGCH. On receipt of a TPC "up" command, $P_{e-base}$ is incremented by $\Delta_{e-base}$ . On receipt of a TPC "down" command, $P_{e-base}$ is decremented by $\Delta_{e-base}$ . The TPC step size $\Delta_{e-base}$ is configured by higher layers [15]. + +- $L$ is a pathloss term derived by higher layers from beacon function physical channel measurements. It may comprise a weighted sum of the instantaneous ( $L_{PCCPCH}$ ) and filtered ( $L_0$ ) pathloss measurements (as described in [15]) +- $\beta_e$ is the gain factor derived for the selected E-TFC transport block size, E-PUCH physical resource size, E-PUCH modulation type and HARQ offset according to subclause 4.2.2.4.1. +- $K_{E-PUCH}$ is the E-PUCH constant value signalled by higher layers [15]. + +Higher layers in the UE shall use the current calculated E-PUCH power in conjunction with the current absolute grant (power) value in order to determine the set of E-TFC's available (see [18]). + +When setting the initial transmit power for E-PUCH or following an extended pause in the reception of TPC commands on E-AGCH, the UE shall set $P_{e-base}$ equal to the average of the $I_{BTS}$ values (see [15]) over the timeslots configured for E-DCH use. When receipt of TPC commands on E-AGCH recommences, the TPC commands shall be used to modify $P_{e-base}$ from its previously set value. + +##### 4.2.2.4.1 Gain factors for E-PUCH + +A beta factor $\beta_e$ shall be derived by the UE as a function of: + +- the selected E-TFC transport block size +- the E-PUCH resource occupation in the E-DCH TTI +- the modulation type (QPSK/16-QAM) +- the HARQ power offset (see [18]) + +Higher layers shall provide a set of reference points defining the relationship between the coderate of E-DCH transmission ( $\lambda_e$ ) and the relative reference power per resource unit ( $\beta_\lambda$ dB). A set of reference points is provided separately for each of QPSK and 16-QAM modulation. + +The coderate of E-DCH transmission $\lambda_e$ for the selected E-TFC, physical resource allocation and modulation type is defined as: + +... in which $S_e$ is the transport block size of the selected E-TFC and $R_e$ is the number of physical channel bits output from the physical channel mapping stage of E-DCH transport channel processing as described in [9]. + +The maximum and minimum values of $\lambda$ signalled by higher layers for the appropriate modulation type are denoted $\lambda_{max}$ and $\lambda_{min}$ respectively. For a given $\lambda_e$ there exists a $\lambda_0$ and a $\lambda_1$ such that: + +- If $\lambda_{min} \leq \lambda_e < \lambda_{max}$ + - $\lambda_0$ is the largest $\lambda$ signalled by higher layers for the appropriate modulation type and for which $\lambda \leq \lambda_e$ + - $\lambda_1$ is the smallest $\lambda$ signalled by higher layers for the appropriate modulation type and for which $\lambda > \lambda_e$ +- Else + - If $\lambda_e < \lambda_{min}$ then $\lambda_0 = \lambda_{min}$ and $\lambda_1$ is the smallest signalled $\lambda$ for which $\lambda > \lambda_{min}$ . + - If $\lambda_e \geq \lambda_{max}$ then $\lambda_0$ is the largest signalled $\lambda$ for which $\lambda < \lambda_{max}$ and $\lambda_1 = \lambda_{max}$ + +Associated with $\lambda_0$ and $\lambda_1$ are the corresponding $\beta_{\lambda_0}$ and $\beta_{\lambda_1}$ which define the reference points signalled by higher layers. The normalised (per-resource-unit) beta value for the selected E-TFC and E-PUCH resource set is denoted $\beta_{0,e}$ and is: + +is a logarithmic value set as a function of the E-PUCH spreading factor ( $SF_{E-PUCH}$ ) according to table 1a. + +**Table 1a: Tabulated $\alpha_e$ values** + +| $SF_{E-PUCH}$ | (dB) | +|---------------|------| +|---------------|------| + +| | | +|----|----| +| 1 | 12 | +| 2 | 9 | +| 4 | 6 | +| 8 | 3 | +| 16 | 0 | + +$\beta_e$ is then derived as + +$\Delta_{harq}$ is set by higher layers (see [18]). + +#### 4.2.2.5 E-RUCCH + +The transmit power for the E-RUCCH is set by higher layers based on open loop power control as described in [15]. + +### 4.2.3 Downlink control + +#### 4.2.3.1 P-CCPCH + +The Primary CCPCH transmit power is set by higher layer signalling and can be changed based on network conditions on a slow basis. The reference transmit power of the P-CCPCH is broadcast on BCH or individually signalled to each UE. + +#### 4.2.3.2 S-CCPCH, PICH + +The relative transmit power of the Secondary CCPCH and the PICH compared to the P-CCPCH transmit power are set by higher layer signalling. The PICH power offset relative to the P-CCPCH reference power is signalled on the BCH. + +#### 4.2.3.2A MICH + +The relative transmit power of the MICH compared to the P-CCPCH transmit power is set by higher layer signalling. + +#### 4.2.3.3 SCH + +The SCH transmit power is set by higher layer signalling [16]. The value is given relative to the power of the P-CCPCH. + +#### 4.2.3.3A PNB SCH + +The PNB SCH transmit power is set by higher layer signalling [16]. The value given is relative to the power of the P-CCPCH + +#### 4.2.3.4 DPCH, PDSCH + +The initial transmission power of the downlink DPCH and the PDSCH shall be set by higher layer signalling. If associated uplink CCTrCHs for TPC commands are signalled to the UE by higher layers (mandatory for a DPCH), the network shall transit into inner loop power control after the initial transmission. The UE shall then generate TPC commands to control the network transmit power and send them in the TPC field of the associated uplink CCTrCHs. If the physical channel power should be increased, the TPC command is set to "up" whereas if the power should be reduced the TPC command is set to "down". An example on how to derive the TPC commands and the definition of the inner loop power control are given in Annex A.1. A TPC command sent in an uplink CCTrCH controls all downlink DPCHs or PDSCHs to which the associated downlink CCTrCH is mapped to. + +If a PDSCH does not have associated uplink CCTrCHs configured for TPC power control, its power shall be controlled by higher layer signalling. + +In the case that no associated downlink data is scheduled within 15 timeslots before the transmission of a TPC command then this is regarded as a transmission pause. The TPC commands in this case shall be derived from measurements on beacon function physical channels. An example solution for the generation of the TPC command for this case is given in Annex A.1. + +When not in a transmission pause each TPC command shall always be based on all associated downlink transmissions received since the previous related TPC command. Related TPC commands are defined as TPC commands associated with the same downlink CCTrCHs. If there are no associated downlink transmissions (or equivalently no beacon transmissions when in a transmission pause) between two or more uplink transmissions carrying related TPC commands, then these TPC commands shall be identical and they shall be regarded by the UTRAN as a single TPC command. + +UTRAN may decide how to adjust the transmit power in response to the received TPC command. + +The UTRAN may apply an individual offset to the transmission power in each timeslot according to the downlink interference level at the UE. + +The transmission power of one DPCH or PDSCH shall not exceed the limits set by higher layer signalling by means of Maximum\_DL\_Power (dB) and Minimum\_DL\_Power (dB). The transmission power is defined as the average power over one timeslot of the complex QPSK symbols of a single DPCH or PDSCH before spreading relative to the power of the P-CCPCH. + +During a downlink transmission pause, both UE and Node B shall use the same TPC step size which is signalled by higher layers. The UTRAN may accumulate the TPC commands received during the pause. TPC commands that shall be regarded as identical may only be counted once. The initial UTRAN transmission power for the first data transmission after the pause may then be set to the sum of transmission power before the pause and a power offset according to the accumulated TPC commands. Additionally this sum may include a constant set by the operator and a correction term due to uncertainties in the reception of the TPC bits. The total downlink transmission power at the Node B within one timeslot shall not exceed Maximum Transmission Power set by higher layer signalling. If the total transmit power of all channels in a timeslot exceeds this limit, then the transmission power of all downlink DPCHs and PDSCHs shall be reduced by the same amount in dB. The value for this power reduction is determined, so that the total transmit power of all channels in this timeslot is equal to the maximum transmission power. + +##### 4.2.3.4.1 Out of synchronisation handling + +When the dedicated physical channel out of sync criteria based on the received burst quality is as given in the subclause 4.4.2 then the UE shall set the uplink TPC command = "up". The CRC based criteria shall not be taken into account in TPC bit value setting. + +#### 4.2.3.5 HS-PDSCH + +The HS-PDSCH power control is under the control of the NodeB. + +#### 4.2.3.6 HS-SCCH + +Higher layers shall indicate the maximum transmit power of the HS-SCCH. The Node-B shall not exceed this maximum power when setting the HS-SCCH power. + +The initial power of the HS-SCCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may optionally power control the HS-SCCH. This may be done using TPC commands sent by the UE in the HS-SICH. + +The UE shall set the TPC commands in the HS-SICH in order to control the transmit power of the HS-SCCH. The TPC commands shall be set in order to meet the HS-SCCH target BLER. + +The accuracy of the received HS-SCCH BLER estimate made by the UE may be enhanced by a suitable use of the HCSN field received within the HS-SCCH itself [9]. This field shall initially be set to zero and shall be incremented by the NodeB each time an HS-SCCH is transmitted to the UE. + +#### 4.2.3.7 E-AGCH + +Higher layers shall indicate the maximum transmit power of the E-AGCH. The Node-B shall not exceed this maximum power when setting the E-AGCH power. + +The initial power of the E-AGCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may optionally power control the E-AGCH. This may be done using TPC commands sent by the UE in the E-PUCH. + +The UE shall set the TPC commands in the E-PUCH in order to control the transmit power of the E-AGCH. The TPC commands shall be set in order to meet the E-AGCH target BLER. + +The accuracy of the received E-AGCH BLER estimate made by the UE shall be enhanced by a suitable use of the ECSN field received within the E-AGCH itself [9]. This field shall initially be set to zero and shall be incremented by the Node-B each time an E-AGCH is transmitted to the UE. + +#### 4.2.3.8 E-HICH + +The power of the E- HICH is under the control of the Node B. + +## 4.3 Timing advance + +UTRAN may adjust the UE transmission timing with timing advance. The initial value for timing advance ( $TA_{phys}$ ) will be determined in the UTRAN by measurement of the timing of the PRACH or E-RUCCH. The required timing advance will be represented as an 8 bit number (0-255) 'UL Timing Advance' $TA_{ul}$ , being the multiplier of 4 chips which is nearest to the required timing advance (i.e. $TA_{phys} = TA_{ul} \times 4$ chips). + +When Timing Advance is used the UTRAN will continuously measure the timing of a transmission from the UE and send the necessary timing advance value. On receipt of this value the UE shall adjust the timing of its transmissions accordingly in steps of $\pm 4$ chips. The transmission of TA values is done by means of higher layer messages. Upon receiving the TA command the UE shall adjust its transmission timing according to the timing advance command at the frame number specified by higher layer signaling. The UE is signaled the TA value in advance of the specified frame activation time to allow for local processing of the command and application of the TA adjustment on the specified frame. Node-B is also signaled the TA value and radio frame number that the TA adjustment is expected to take place. + +If TA is enabled by higher layers, after handover the UE shall transmit in the new cell with timing advance TA adjusted by the relative timing difference $\Delta t$ between the new and the old cell: + +$$TA_{new} = TA_{old} + 2\Delta t.$$ + +## 4.4 Synchronisation procedures + +### 4.4.1 Cell search + +During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code and frame synchronisation of that cell. How cell search is typically done is described in Annex C. + +For MBSFN FACH, the downlink scrambling codes and basic midamble codes to be used for non-beacon timeslots are signalled by higher layers. + +### 4.4.2 Dedicated channel synchronisation + +#### 4.4.2.1 Synchronisation primitives + +##### 4.4.2.1.1 General + +For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of radio links, both in uplink and downlink. The definition of the primitives is given in the following subclauses. + +When operating HS-DSCH, the configuration of a downlink DPCH by UTRAN is optional. Subclause 4.4.2.1.2 relates to downlink synchronisation in the case that an uplink and downlink DPCH have been configured by higher layers. Subclause 4.4.2.1.2A relates to downlink synchronisation in the case that only an uplink DPCH has been configured by higher layers. + +##### 4.4.2.1.2 Downlink synchronisation primitives + +Layer 1 in the UE shall check the synchronization status of each DL CCTrCH individually in every radio frame All bursts and transport channels of a CCTrCH shall be taken into account. Synchronisation status is indicated to higher layers, using the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitives. For dedicated physical channels configured with Repetition Periods [15] only the configured active periods shall be taken into account in the estimation. The status check shall also include detection of the Special Bursts defined in 4.5 for DTX. + +The criteria for reporting synchronization status are defined in two different phases. + +The first phase lasts until 160 ms after the downlink CCTrCH is considered to be established by higher layers. During this time, Out-of-sync shall not be reported. In-sync shall be reported using the CPHY-Sync-IND primitive if any one of the following three criteria is fulfilled. + +- a) The UE estimates the burst reception quality over the previous 40 ms period to be better than a threshold $Q_{in}$ . This criterion shall be assumed not to be fulfilled before 40 ms of burst reception quality measurement have been collected. +- b) At least one transport block with a CRC attached is received in a TTI ending in the current frame with correct CRC. +- c) The UE detects at least one Special Burst. Special Burst detection shall be successful if the burst is detected with quality above a threshold, $Q_{sbin}$ , and the TFCI is decoded to be that of the Special Burst. + +The second phase starts 160 ms after the downlink dedicated channel is considered established by higher layers. During this phase both Out-of-Sync and In-Sync are reported as follows. + +Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive if all three of the following criteria are fulfilled: + +- the UE estimates the received dedicated channel burst quality over the last 160 ms period to be worse than a threshold $Q_{out}$ . The value, $Q_{out}$ is defined implicitly by the relevant tests in [2]; +- no Special Burst is detected with quality above a threshold $Q_{sbout}$ within the last 160 ms period. The value $Q_{sbout}$ is defined implicitly by the relevant tests in [2]; +- over the previous 160 ms, no transport block has been received with a correct CRC + +If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, the UE shall use 320 ms estimation period for the burst quality evaluation and for the Special Burst and CRC detection window. + +In-sync shall be reported using the CPHY-Sync-IND primitive if any of the following criteria is fulfilled: + +- the UE estimates the received burst reception quality over the last 160 ms period to be better than a threshold $Q_{in}$ . The value, $Q_{in}$ is defined implicitly by the relevant tests in [2]. +- the UE detects at least one Special Burst with quality above a threshold $Q_{sbin}$ within the last 160 ms period. The value, $Q_{sbin}$ , is defined implicitly by the relevant tests in [2]. +- at least one transport block with a CRC attached is received in a TTI ending in the current frame with correct CRC. + +If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, the UE uses 320 ms estimation period for the burst quality evaluation and for the Special Burst detection window. + +If no data are provided by higher layers for transmission during the second phase on the downlink dedicated channel then DTX shall be applied as defined in section 4.5. + +How the primitives are used by higher layers is described in [15]. The above definitions may lead to radio frames where neither the In-Sync nor Out-of-Sync primitives are reported. + +##### 4.4.2.1.2A Downlink synchronisation primitives for HS-channels + +In the case that an uplink DPCH has been configured by higher layers but a downlink DPCH has not been configured, the UE shall report downlink synchronisation status based upon other downlink physical channels. + +The UE shall monitor the received beacon signal level within the cell and shall average the received beacon power over a period of 160ms. This averaged value is denoted $P_b$ dBm. The UE shall also monitor and average over the same period, the ISCP on the assigned HS-SCCH resources. This value is denoted $I_{HS-SCCH}$ dBm. A quality value $Q_{hs}$ is formed as follows: + +$$Q_{hs} = P_b - I_{HS-SCCH} + D_{hs-sync}$$ + +- where $D_{hs-sync}$ is signalled by higher layers. + +In-sync shall be reported using the CPHY-Sync-IND primitive each time an HS-DSCH CRC pass is detected. On this event, an indicator maintained by the UE termed "HS-DSCH\_failure" shall be set to 'false'. In-sync shall also be reported if the HS-DSCH\_failure indicator is set to 'false' and during the last 160ms period, $Q_{hs} > Q_{hsin}$ , where $Q_{hsin}$ is a quality threshold defined implicitly by the relevant tests in [2]. + +Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive. "Out-of-sync" is generated in the event that, during the last 160ms period, $Q_{hs} < Q_{hsout}$ , where $Q_{hsout}$ is a quality threshold defined implicitly by the relevant tests in [2]. CPHY-Out-of-Sync-IND shall also be generated in the event of 16 successive HS-DSCH CRC failures. On occurrence of this event, the HS-DSCH\_failure indicator shall be set to 'true'. + +How the primitives are used by higher layers is described in [15]. The above definitions may lead to radio frames where neither the In-Sync nor Out-of-Sync primitives are reported. They may also, under some circumstances, lead to radio frames in which both In-Sync and Out-of-Sync primitives are generated. In this instance, In-sync shall override Out-of-Sync and the Out-of-Sync primitive shall not be reported. + +##### 4.4.2.1.3 Uplink synchronisation primitives + +Layer 1 in the Node B shall every radio frame check synchronisation status, individually for each UL CCTrCH of the radio link. Synchronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitive. + +The exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received burst quality or CRC checks. One example would be to have the same criteria as for the downlink synchronisation status primitives. + +#### 4.4.2.2 Radio link monitoring + +##### 4.4.2.2.1 Downlink radio link failure + +The downlink CCTrCHs are monitored by the UE, to trigger radio link failure procedures. The downlink CCTrCH failure status is specified in [15], and is based on the synchronisation status primitives CPHY-Sync-IND and CPHY- + +Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. These primitives shall provide status for each DL CCTrCH separately. + +##### 4.4.2.2.2 Uplink radio link failure/restore + +The uplink CCTrCHs are monitored by the Node B in order to trigger CCTrCH failure/restore procedures. The uplink CCTrCH failure/restore status is reported using the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. + +When the CCTrCH is in the in-sync state, Node B shall start timer T\_RLFAILURE after receiving N\_OUTSYNC\_IND consecutive out-of-sync indications. Node B shall stop and reset timer T\_RLFAILURE upon receiving successive N\_INSYNC\_IND in-sync indications. If T\_RLFAILURE expires, Node B shall indicate to higher layers which CCTrCHs are out-of-sync using the synchronization status primitives. Furthermore, the CCTrCH state shall be changed to the out-of-sync state. + +When a CCTrCH is in the out-of-sync state, after receiving N\_INSYNC\_IND successive in-sync indications Node B shall indicate that the CCTrCH has re-established synchronisation and the CCTrCH's state shall be changed to the in-sync-state. The specific parameter settings (values of T\_RLFAILURE, N\_OUTSYNC\_IND, and N\_INSYNC\_IND) are configurable, see [16]. + +## 4.5 Discontinuous transmission (DTX) procedure + +The DTX procedure shall be applied for CCTrCHs mapped to S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, if the total bit rate of the CCTrCH differs from the total channel bit rate of the physical channels allocated to this CCTrCH. DTX shall not be applied to E-DCH mapped to E-PUCH. + +The DTX procedure shall also be applied to HS-PDSCHs, HS-SCCHs, E-AGCHs and E-HICHs if no data is to be transmitted on these physical channels in a given TTI. + +Rate matching is used in order to fill resource units completely, that are only partially filled with data. In the case that after rate matching and multiplexing no data at all is to be transmitted in a resource unit the complete resource unit shall be discarded from transmission (DTX), unless a Special Burst is transmitted in the RU. This applies also to the case where only one resource unit is allocated and no data has to be transmitted. + +### 4.5.1 Description of special bursts + +For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the Special Burst has the same timeslot format as the burst used for data provided by higher layers. If the timeslot format contains a TFCI field, then the TFCI field shall be filled with "0" bits. The Special Burst may also carry layer 1 control symbols such as TPC bits for the purposes of inner-loop power control. The data portions of the Special Burst are filled with an arbitrary bit pattern. + +For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the transmission power of the special burst shall be the same as that of the substituted physical channel of the CCTrCH. In the case of uplink physical channels where autonomous spreading factor change by the UE is permitted by higher layers, the substituted physical channel is considered to be that which would have been employed for the lowest non-zero rate TFC within the set of allowed TFC's and the transmission power of the Special Burst shall again correspond to that of the physical channel substituted. + +For HS-PDSCH, the Special Burst shall use the timeslot format #0 from table 7a, see section 5.3.9.5 in [8]. For HS-SCCH, the Special Burst shall use timeslot format #0 from table 5a, see section 5.2.2.6.1 in [8]. The Special Burst is filled with an arbitrary bit pattern. The transmission power of the Special Burst shall be the same as that of the substituted Beacon channel. + +### 4.5.2 Use of special bursts during DTX + +In the case that after link establishment there are no transport blocks provided for transmission by higher layers for a given CCTrCH mapped to UL DPCH, DL DPCH, PUSCH or PDSCH physical channels, then a Special Burst shall be transmitted in the first allocated frame of the transmission pause. If, including the first frame, there is a consecutive period of Special Burst Period (SBP) frames without transport blocks provided by higher layers, then another special burst shall be generated and transmitted at the next possible frame. This pattern shall be continued until transport blocks are provided for the CCTrCH by the higher layers. SBP shall be provided by higher layers. The value of SBP shall be independently specified for uplink and for downlink and shall be designated as + +SBGP (special burst generation period) for uplink transmissions + +SBSP (special burst scheduling parameter) for downlink transmissions + +The default value for both SBGP and SBSP shall be 8. + +The Special Burst shall be transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) as defined by the rate matching function in [9]. + +Special Bursts shall not be transmitted for HS-SCCH and for CCTrCHs mapped to S-CCPCH or HS-PDSCH in non-Beacon locations, i.e. only DTX shall be applied to these physical channels. + +### 4.5.3 Use of special bursts for initial establishment / reconfiguration + +Upon initial establishment or reconfiguration for either 160 ms following detection of in-sync, or until the first transport block is received from higher layers, both the UE and the Node B shall transmit the special burst for each CCTrCH mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels. + +The Special Burst shall be transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) as defined by the rate matching function in [9]. + +### 4.5.4 Use of special bursts for DTX on beacon channels + +In the case that a beacon-function physical channel (S-CCPCH or PDSCH) would be DTX'd, then a Special Burst shall be transmitted on the Beacon Channel in that frame instead in order to maintain the beacon functionality. + +## 4.6 Downlink transmit diversity + +Downlink transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-AGCH, E-HICH and SCH is optional in UTRAN. Its support is mandatory at the UE. + +### 4.6.1 Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH + +The transmitter structure to support transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH transmission is shown in figure 1. Channel coding, interleaving and spreading are done as in non-diversity mode. The spread complex valued signal is fed to both TX antenna branches, and weighted with antenna specific weight factors $w_1$ and $w_2$ . The weight factors are complex valued signals (i.e., $w_i = a_i + jb_i$ ), in general. These weight factors are calculated on a per slot and per user basis. + +The weight factors are determined by the UTRAN. Examples of transmit diversity schemes are given in annex B. + +![Figure 1: Downlink transmitter structure to support Transmit Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point).](daae5239bb53d468ea958aedfc2e6070_img.jpg) + +The diagram illustrates the downlink transmitter structure for transmit diversity. On the left, 'Data' is processed through a series of blocks: 'ENC' (Encoder), 'INT' (Interleaver), and 'SPR+SCR' (Spreading and Scrambling). The output of 'SPR+SCR' is fed into a 'MUX' (Multiplexer). The 'MUX' also receives a 'Midamble' signal. The output of the 'MUX' is split into two parallel branches. Each branch consists of a complex multiplier (represented by a circle with an 'X'), followed by an 'FIR' (Finite Impulse Response) filter, and then an 'RF' (Radio Frequency) block. The first branch is labeled with weight factor $w_1$ and the second with $w_2$ . The outputs of the 'RF' blocks are connected to antennas 'ANT1' and 'ANT2'. Below the antennas, a block labeled 'Uplink channel estimate' receives feedback from both antennas and provides the weight factors $w_1$ and $w_2$ to the complex multipliers. + +Figure 1: Downlink transmitter structure to support Transmit Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point). + +**Figure 1: Downlink transmitter structure to support Transmit Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point)** + +### 4.6.2 Transmit diversity for SCH and S-CCPCH + +Time Switched Transmit Diversity (TSTD) can be employed as a transmit diversity scheme for the synchronisation channel and/or S-CCPCH. + +#### 4.6.2.1 SCH transmission scheme + +The transmitter structure to support transmit diversity for SCH transmission is shown in figure 2. P-SCH and S-SCH are transmitted from antenna 1 and antenna 2 alternatively. An example for the antenna switching pattern is shown in figure 3. + +![Figure 2: Downlink transmitter structure to support Transmit Diversity for SCH transmission (UTRAN Access Point).](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +graph LR + PSCH[P-SCH] --> Sum((+)) + SSCH[S-SCH] --> Sum + Sum --> Switch{Switch} + Switch -- Switching Control --> Path1[FIR] --> RF1[RF] --> Ant1[Ant 1] + Switch -- Switching Control --> Path2[FIR] --> RF2[RF] --> Ant2[Ant 2] + +``` + +The diagram shows the transmitter structure for SCH transmission. P-SCH and S-SCH signals are combined at a summing node (+). The output is then routed through a switch controlled by 'Switching Control'. The switch toggles between two paths: the top path leads through an FIR filter and an RF block to Antenna 1, and the bottom path leads through an FIR filter and an RF block to Antenna 2. + +Figure 2: Downlink transmitter structure to support Transmit Diversity for SCH transmission (UTRAN Access Point). + +**Figure 2: Downlink transmitter structure to support Transmit Diversity for SCH transmission (UTRAN Access Point)** + +![Figure 3: Antenna Switching Pattern (Case 2).](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +The diagram illustrates the antenna switching pattern over two frames, each containing 15 timeslots. Shaded slots in the frame structure indicate when a burst is transmitted. The bursts alternate between Antenna #1 and Antenna #2. Each burst contains the primary synchronization code $C_P$ and the secondary synchronization code $b_i c_1$ . + +| Antenna | Active Slots (per 15-slot frame) | Burst Content | +|---------|----------------------------------|-------------------| +| Ant #1 | Slot 1, Slot 9 | $C_P$ , $b_i c_1$ | +| Ant #2 | Slot 5, Slot 13 | $C_P$ , $b_i c_1$ | + +Figure 3: Antenna Switching Pattern (Case 2). + +**Figure 3: Antenna Switching Pattern (Case 2)** + +#### 4.6.2.2 S-CCPCH transmission scheme + +The transmitter structure to support TSTD for S-CCPCH is shown in figure 3a. The antenna switching pattern is under the control of the Node-B and is not explicitly known to the UE. Switching may only be performed during the guard periods between timeslots. + +![Figure 3a: Downlink transmitter structure to support TSTD for S-CCPCH transmission (UTRAN Access Point).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram shows a downlink transmitter structure. An input labeled 'S-CCPCH' enters a switching control unit. This unit has two output paths. The top path consists of a block labeled 'FIR' followed by a block labeled 'RF', which then connects to an antenna labeled 'Ant 1'. The bottom path also consists of a block labeled 'FIR' followed by a block labeled 'RF', which then connects to an antenna labeled 'Ant 2'. The switching control unit is indicated by an upward-pointing arrow. + +Figure 3a: Downlink transmitter structure to support TSTD for S-CCPCH transmission (UTRAN Access Point). + +**Figure 3a: Downlink transmitter structure to support TSTD for S-CCPCH transmission (UTRAN Access Point)** + +### 4.6.3 Transmit diversity for beacon channels + +When beacon channels use burst type 4, SCTD shall not be applied. + +When beacon channels use burst type 1, Space Code Transmit Diversity (SCTD) for beacon channels may be employed optionally in the UTRAN. The support is mandatory in the UE except for the case where the UE only supports burst type 4. The use of SCTD will be indicated by higher layers. If SCTD is active within a cell: + +- SCTD shall be applied to any beacon channel, and +- the maximum number $K_{\text{Cell}}$ of midambles for burst type 1 that are supported in this cell may be 8 or 16, see [8]. The case of $K_{\text{Cell}} = 4$ midambles is not allowed for this burst type. + +#### 4.6.3.1 SCTD transmission scheme + +The open loop downlink transmit diversity scheme for beacon channels is shown in figure 4. Channel coding, rate matching, interleaving and bit-to-symbol mapping are performed as in the non-diversity mode. In Space Code Transmit Diversity mode the data sequence is spread with the channelisation codes $c_{16}^{(k=1)}$ and $c_{16}^{(k=2)}$ and scrambled with the cell specific scrambling code. The spread sequence on code $c_{16}^{(k=2)}$ is then transmitted on the diversity antenna. The power applied to each antenna shall be equal. + +![Figure 4: Block Diagram of the transmitter SCTD.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +The block diagram shows the transmitter SCTD. An input labeled 'Encoded and Interleaved Data Symbols, 2 data fields' enters a split. The top path goes through a block labeled 'SPR-SCR c(1)' to a 'MUX' block. The bottom path goes through a block labeled 'SPR-SCR c(2)' to another 'MUX' block. The top 'MUX' block also receives an input labeled 'Midamble 1' and its output is labeled 'Tx. Antenna 1' with an antenna symbol. The bottom 'MUX' block also receives an input labeled 'Midamble 2' and its output is labeled 'Tx. Antenna 2' with an antenna symbol. + +Figure 4: Block Diagram of the transmitter SCTD. + +**Figure 4: Block Diagram of the transmitter SCTD** + +## 4.7 Random access procedure + +The physical random access procedure described below is invoked whenever a higher layer requests transmission of a message on the RACH. The physical random access procedure is controlled by primitives from RRC and MAC. Retransmission on the RACH in case of failed transmission (e.g. due to a collision) is controlled by higher layers. Thus, + +the backoff algorithm and associated handling of timers is not described here. The definition of the RACH in terms of PRACH Access Service Classes is broadcast on the BCH in each cell. Parameters for common physical channel uplink outer loop power control are also broadcast on the BCH in each cell. The UE needs to decode this information prior to transmission on the RACH. Higher layer signalling may indicate, that in some frames a timeslot shall be blocked for RACH uplink transmission. + +### 4.7.1 Physical random access procedure + +The physical random access procedure described in this subclause is initiated upon request from the MAC sublayer (see [18] and [19]). + +Note: The selection of a PRACH is done by the RRC Layer. + +Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information from the RRC layer using the primitives CPHY-TrCH-Config-REQ and CPHY-RL-Setup/Modify-REQ. + +- the available PRACH channelization codes (There is a 1-1 mapping between the channelization code and the midamble shift as defined by RRC) for each Access Service Class (ASC) of the selected PRACH (the selection of a PRACH is done by the RRC ). CPHY-RL-Setup/Modify-REQ; +- the timeslot, spreading factor, and midamble type(direct or inverted) for the selected PRACH (CPHY-RL-Setup/Modify-REQ); +- the RACH Transport Format (CPHY-TrCH-Config-REQ); +- the RACH transport channel identity (CPHY-TrCH-Config-REQ) +- the set of parameters for common physical channel uplink outer loop power control(CPHY-RL-Setup/Modify-REQ). + +NOTE: The above parameters may be updated from higher layers before each physical random access procedure is initiated. + +At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the MAC: + +- the ASC of the PRACH transmission; +- the data to be transmitted (Transport Block Set). + +the selected ASC sub-channel. The ASC subchannel is defined in reference [18]. The value is passed in the PHY-Data-REQ is the CFNCELL. + +In addition, Layer 1 may receive information from higher layers, that a timeslot in certain frames shall be blocked for PRACH uplink transmission. + +The physical random-access procedure shall be performed as follows: + +- 1 Randomly select one channelization code from the set of available codes for the selected ASC. The random function shall be such that each code is chosen with equal probability. +- 2 Determine the midamble shift to use, based on the selected channelization code. +- 3 Set the PRACH message transmission power level according to the specification for common physical channels in uplink (see subclause 4.2.2.2). +- 4 Transmit the RACH Transport Block Set (the random access message) with no timing advance in the selected sub-channel using the selected channelization code. + +## 4.7A E-RUCCH transmission procedure + +Requests for the transmission of an E-RUCCH are controlled by higher layers [18]. + +The E-RUCCH random access procedure shall be performed as follows: + +- 1 Randomly select one channelization code from the set of available codes for E-RUCCH. The random function shall be such that each code is chosen with equal probability. +- 2 Determine the midamble shift to use, based on the selected channelization code. +- 3 Set the E-RUCCH message transmission power level according to subclause 4.2.2.5. +- 4 Transmit the E-RUCCH with no timing advance using the selected channelization code. + +## 4.8 DSCH procedure + +The physical downlink shared channel procedure described below shall be applied by the UE when the physical layer signalling either with the midamble based signalling or TFCI based signalling is used to indicate for the UE the need for PDSCH detection. There is also a third alternative to indicate to the UE the need for the PDSCH detection and this is done by means of higher layer signalling, already described in [8]. + +### 4.8.1 DSCH procedure with TFCI indication + +When the UE has been allocated by higher layers to receive data on DSCH using the TFCI, the UE shall decode the PDSCH in the following cases: + +- In case of a standalone PDSCH the TFCI is located on the PDSCH itself, then the UE shall decode the TFCI and based on which data rate was indicated by the TFCI, the decoding shall be performed. The UE shall decode PDSCH only if the TFCI word decode corresponds to the TFC part of the TFCS given to the UE by higher layers. +- In case that the TFCI is located on the DCH, the UE shall decode the PDSCH frame or frames if the TFCI on the DCH indicates the need for PDSCH reception. Upon reception of the DCH time slot or time slots, the PDSCH slot (or first PDSCH slot) shall start $SFN\ n+2$ after the DCH frame containing the TFCI, where $n$ indicates the SFN on which the DCH is received. In the case that the TFCI is repeated over several frames, the PDSCH slot shall start $SFN\ n+2$ after the frame having the DCH slot which contains the last part of the repeated TFCI. + +### 4.8.2 DSCH procedure with midamble indication + +When the UE has been allocated by higher layers to receive PDSCH based on the midamble used on the PDSCH (midamble based signalling described in [8]), the UE shall operate as follows: + +- The UE shall test the midamble it received and if the midamble received was the same as indicated by higher layers to correspond to PDSCH reception, the UE shall detect the PDSCH data according to the TF given by the higher layers for the UE. +- In case of multiple time slot allocation for the DSCH indicated to be part of the TF for the UE, the UE shall receive all timeslots if the midamble of the first timeslot of PDSCH was the midamble indicated to the UE by higher layers. +- In case the standalone PDSCH (no associated DCH) contains the TFCI the UE shall detect the TF indicated by the TFCI on PDSCH. + +## 4.9 Node B synchronisation procedure over the air + +An option exists to use cell sync bursts to achieve and maintain Node B synchronisation [20]. This optional procedure is based on transmissions of cell synchronisation bursts [10] in predetermined timeslots normally assigned to contain PRACH, according to an RNC schedule. Such soundings between neighbouring cells facilitate timing offset measurements by the cells. The timing offset measurements are reported back to the RNC for processing. The RNC generates cell timing updates that are transmitted to the Node Bs and cells for implementation. + +When Cell Sync Bursts are used to achieve and maintain intercell Synchronisation there are three distinct phases, with a potential additional sub-phase involving late entrant cells. + +### 4.9.1 Frequency acquisition phase + +The frequency acquisition phase is used to bring cells of an RNS area to within frequency limits prior to initial synchronisation. No traffic is supported during this phase. In this phase cell(s) identified as master time reference shall + +transmit cell sync bursts [10] specified by higher layers continuously, i. e. one in every timeslot. All other cells shall listen for transmissions and shall perform frequency locking to the transmissions received. They shall signal completion of frequency acquisition to the RNC and begin continuous transmission of cell sync bursts specified by higher layers. + +### 4.9.2 Initial synchronisation + +For Initial Phase, where no traffic is supported, the following procedure for initial synchronisation may be used to bring cells of an RNS area into synchronisation at network start up. In this phase each cell shall transmit cell sync bursts [10] according to the higher layer command. All cells use the same cell sync burst code and code offset. Each cell shall listen for transmissions from other cells. Each cell shall report the timing and received SIR of successfully detected cell sync bursts to the RNC. The RNC uses these measurements to adjust the timing of each cell to achieve the required synchronisation accuracy. + +### 4.9.3 Steady-state phase + +The steady-state phase is used to maintain the required synchronisation accuracy. With the start of the steady-state phase, traffic is supported in a cell. A procedure that may be used for the steady-state phase involves cell sync bursts [10] that are transmitted and received without effect on existing traffic. Higher layers signal the transmit parameters, i.e., when to transmit which code and code offset, and which transmit power to use. The higher layers also signal to appropriate cells the receive parameters i. e. which codes and code offsets to measure in a certain timeslot. Upon determination of errors in timing, the RNC may adjust the timing of a cell or cells. + +### 4.9.4 Late entrant cells + +A procedure that may be used for introducing new cells into an already synchronised RNS involves the one time transmission of a single cell sync burst [10] (scheduled by higher layers) by all neighbour cells of the late entrant cell, and received by the late entrant cell. The RNC may use this information to adjust the late entrant cell sufficiently to allow the cell to enter steady state phase. + +## 4.10 Idle periods for IPDL location method + +### 4.10.1 General + +To support time difference measurements for location services, idle periods can be created in the downlink (hence the name IPDL) during which time transmission of all channels from a Node B is temporarily ceased, except for the SCH transmission. During these idle periods the visibility of neighbour cells from the UE is improved. + +The idle periods are arranged in a determined pattern according to higher layer parameters. An idle period has a duration of one time slot. During idle periods only the SCH is transmitted. No attempt is made to prevent data loss. + +In general there are two modes for these idle periods: + +- Continuous mode, and +- Burst mode. + +In continuous mode the idle periods are active all the time. In burst mode the idle periods are arranged in bursts where each burst contains enough idle periods to allow a UE to make sufficient measurements for its location to be calculated. The bursts are separated by a period where no idle periods occur. + +The time difference measurements can be performed on any channel. If the P-CCPCH falls in an idle slot, UTRAN may decide not to transmit the P-CCPCH in two consecutive frames, the first of these two frames containing the idle slot. This option is signalled by higher layers. + +### 4.10.2 Parameters of IPDL + +The following parameters are signalled to the UE via higher layers: + +**IP\_Status:** This is a logic value that indicates if the idle periods are arranged in continuous or burst mode. + +**IP\_Spacing:** The number of 10 ms radio frames between the start of a radio frame that contains an idle period and the next radio frame that contains the next idle period. Note that there is at most one idle period in a radio frame. + +**IP\_Start:** The number of the first frame with idle periods. In case of continuous mode IP\_Start is the SFN of the first frame with idle periods and in case of burst mode IP\_Start defines the number of frames after Burst\_Start with the first frame with idle periods. + +**IP\_Slot:** The number of the slot that has to be idle [0..14]. + +**IP\_PCCPCH:** This logic value indicates, if the P-CCPCH is switched off in two consecutive frames. The first of these two frames contains the idle period. + +Additionally in the case of burst mode operation the following parameters are also communicated to the UE. + +**Burst\_Start:** Specifies the start of the first burst of idle periods. $256 \times \text{Burst\_Start}$ is the SFN where the first burst of idle periods starts. + +**Burst\_Length:** The number of idle periods in a burst of idle periods. + +**Burst\_Freq:** Specifies the time between the start of a burst and the start of the next burst. $256 \times \text{Burst\_Freq}$ is the number of radio frames between the start of a burst and the start of the next burst. + +### 4.10.3 Calculation of idle period position + +In burst mode, burst #0 starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start}$ . Burst #n starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start} + n \times 256 \times \text{Burst\_Freq}$ ( $n = 0, 1, 2, \dots$ ). The sequence of bursts according to this formula continues up to and including the radio frame with $\text{SFN} = 4095$ . At the start of the radio frame with $\text{SFN} = 0$ , the burst sequence is terminated (no idle periods are generated) and at $\text{SFN} = 256 \times \text{Burst\_Start}$ the burst sequence is restarted with burst #0 followed by burst #1 etc., as described above. + +Continuous mode is equivalent to burst mode, with only one burst spanning the whole SFN cycle of 4096 radio frames, this burst starts in the radio frame with $\text{SFN} = 0$ . In case of continuous mode the parameter IP\_Start defines the first frame with idle periods. + +The position of an idle period is defined by two values: IP\_Frame(x) and IP\_Slot. IP\_Frame(x) defines the $x^{\text{th}}$ frame within a burst that contains the idle period. IP\_Slot defines the slot in that frame during which no transmission takes place except for the SCH. + +The actual frame with idle periods within a burst is calculated as follows: + +$$\text{IP\_Frame}(x) = \text{IP\_Start} + (x-1) \times \text{IP\_Spacing} \text{ with } x = 1, 2, 3, \dots$$ + +If the parameter IP\_PCCPCH is set to 1, then the P-CCPCH will not be transmitted in the frame IP\_Frame(x) +1 within a burst. + +Figure 5 below illustrates the idle periods for the burst mode case, if the IP\_P-CCPCH parameter is set to 0. + +![Figure 5: Idle Period placement in the case of burst mode operation with IP_P-CCPCH parameter set to 0. The diagram illustrates the hierarchy of idle periods: IP_Slot (Slots 0, 1, ..., 14), IP_Frame(x) (Frame #i, IP_Start frames, IP_Spacing frames), and Burst #0 and #1 of idle periods (SFN = 0, SFN = 256 * Burst_Start, SFN = 256 * Burst_Start + 256 * Burst_Freq).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram shows the placement of idle periods in burst mode operation. It is structured as follows: + +- IP\_Slot:** A horizontal timeline showing Slot #0, Slot #1, a pink box representing the $x^{\text{th}}$ idle period in a burst, and Slot #14. +- IP\_Frame(x):** A horizontal timeline showing Frame #i, 'IP\_Start' frames, 'IP\_Spacing' frames, and multiple pink boxes representing idle periods. A bracket labeled $\text{IP\_Frame}(1)$ spans the first frame. Another bracket labeled $(\text{Burst\_Length})^{\text{th}}$ idle period spans one of the pink boxes. +- Burst #0 of idle periods:** A horizontal timeline starting at SFN = 0. It shows a gap of $256 \times \text{Burst\_Start}$ frames, followed by a pink box (idle period), and then a gap of $256 \times \text{Burst\_Freq}$ frames. The start of the first idle period is marked with SFN = $256 \times \text{Burst\_Start}$ . +- Burst #1 of idle periods:** A horizontal timeline starting at SFN = $256 \times \text{Burst\_Start} + 256 \times \text{Burst\_Freq}$ , showing the start of the second burst. + +Lines connect the pink boxes in the IP\_Frame(x) timeline to the corresponding idle periods in the Burst #0 and Burst #1 timelines, showing their relative timing. + +Figure 5: Idle Period placement in the case of burst mode operation with IP\_P-CCPCH parameter set to 0. The diagram illustrates the hierarchy of idle periods: IP\_Slot (Slots 0, 1, ..., 14), IP\_Frame(x) (Frame #i, IP\_Start frames, IP\_Spacing frames), and Burst #0 and #1 of idle periods (SFN = 0, SFN = 256 \* Burst\_Start, SFN = 256 \* Burst\_Start + 256 \* Burst\_Freq). + +**Figure 5: Idle Period placement in the case of burst mode operation with IP\_P-CCPCH parameter set to 0** + +## 4.11 HS-DSCH procedure + +### 4.11.1 Link adaptation procedure + +For HS-DSCH, the modulation scheme and effective code rate shall be selected by higher layers located within the NodeB. This shall be achieved by appropriate selection of an HS-DSCH transport block size, modulation format and resources by higher layers. Selection of these parameters may be based on CQI reports from the UE. + +The overall HS-DSCH link adaptation procedure consists of *two parts*: + +*Node B procedure:* + +- 1) The NodeB shall transmit HS-SCCH carrying a UE identity identifying the UE for which HS-DSCH TTI allocation has been given. In the case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same HS-SCCH shall be used for associated signalling. +- 2) The NodeB transmits HS-DSCH to the UE using the resources indicated in the HS-SCCH. +- 3) Upon receiving the HS-SICH from the respective UE, the status report (ACK/NACK and CQI) shall be passed to higher layers. + +*UE procedure:* + +- 1) When indicated by higher layers, the UE shall start monitoring all HS-SCCHs that are in its HS-SCCH set as signalled to it by higher layers. The information carried on the HS-SCCH is described in [8]. +- 2) In the case that a HS-SCCH is identified to be correct by its CRC, the UE shall read the HS-PDSCHs indicated by the HS-SCCH. In the case that a HS-SCCH is identified to be incorrect, the UE shall discard the data on the HS-SCCH and return to monitoring. +- 3) After reading the HS-PDSCHs, the UE shall generate an ACK/NACK message and transmit this to the NodeB in the associated HS-SICH, along with the most recently derived CQI. + +The mapping of HS-PDSCH channelisation code set and timeslot information carried by the HS-SCCH for a given HS-DSCH TTI is described in [9]. + +For a given allocation of HS-PDSCH resources to a UE for a specific HS-DSCH TTI, the following shall apply: + +- If timeslot information on HS-SCCH indicates two or more timeslots, none of these timeslots shall comprise a beacon channel. +- If timeslot information on HS-SCCH indicates a single timeslot and this timeslot comprises a beacon channel then: + - The Node-B shall not indicate SF=1 for any HS-PDSCH resource. + - The set of HS-PDSCH resources allocated by the Node-B to a UE shall exclusively comprise either beacon function or non-beacon function physical channels. The Node B shall therefore not allocate both beacon function and non-beacon function physical channels within the beacon timeslot to the UE. If the HS-DSCH for a specific HS-DSCH TTI is mapped to the beacon channel, this shall be signalled using $k_{start} = 1$ and $k_{stop} = 1$ . For a definition of the first and last allocated channelisation code indices $k_{start}$ and $k_{stop}$ on HS-SCCH refer to [9]. + - When SCTD antenna diversity is applied to the beacon channel, then the presence of channelisation code within the channelisation code set information on HS-SCCH shall implicitly indicate the presence of channelisation code . + +### 4.11.2 HS-DSCH channel quality indication procedure + +The channel quality indicator (CQI) provides the NodeB with an estimate of the code rate that would have maximised the single-transmission throughput of the previous HS-DSCH transmission if decoded in isolation. The CQI report requires to be referenced to a given set of HS-PDSCH resources by the NodeB, but note that the UE is not restricted to making measurements only on these reference resources when deriving a given CQI. The reference resources for a CQI report shall be a set of HS-PDSCH resources that were received by the UE in a single TTI, and contain a complete transport block. These resources will be known to the NodeB from the relative timings of the HS-SICH carrying the CQI and previous HS-DSCH transmissions to the UE. + +The CQI consists of two fields; a Recommended Transport Block Size (RTBS) and a Recommended Modulation Format (RMF). The UE shall use the same mapping table for these fields as is being used for the time slot information and modulation scheme information fields respectively of the HS-SCCH [18]. + +The reporting procedure is as follows: + +1. The UE receives a message on an HS-SCCH telling it which resources have been allocated to it for the next associated HS-DSCH transmission. +2. The UE reads the associated HS-DSCH transmission, and makes the necessary measurements to derive a CQI that it estimates would have given it the highest single-transmission throughput for the allocated resources whilst achieving a BLER of no more than 10 %. + +BLER, in this context, is defined as the probability that a transport block transmitted using the RTBS and RMF is received in error if decoded in isolation. For the purposes of this calculation, it shall be assumed that the transport block that would be transmitted with these parameters would use redundancy version parameters $s = 1$ and $r = 0$ . Note that, by this definition, a UE shall never report a CQI that corresponds to a code rate greater than unity. + +Using this definition of BLER, single-transmission throughput shall be defined as follows : + +$$\text{single-transmission throughput} = (1 - \text{BLER}) \times \text{RTBS}$$ + +3. The CQI report derived from a given HS-DSCH transmission shall be reported to the NodeB in the next HS-SICH available to the UE following that HS-DSCH transmission, unless that HS-SICH immediately follows the last allocated HS-DSCH timeslot, in which case the subsequent available HS-SICH shall be used by the UE. This HS-SICH may not necessarily be the same HS-SICH that carries the ACK/NACK information for that HS-DSCH transmission. The UE shall always transmit the most recently derived CQI in any given HS-SICH, which may mean that some CQI reports are discarded without being transmitted to the NodeB. + +## 4.12 Macro-diversity procedure + +When signalled by higher layers, the UE shall combine transmissions on signalled transport channels from multiple radio links. UTRAN shall only indicate that a transport channel on a radio link may be combined with a transport channel on another radio link when those transport channels do not occupy the same time slot. UTRAN shall transmit identical transport blocks on the multiple radio links on the transport channels that may be combined. UTRAN may multiplex onto a CCTrCH other transport channels with transport channels that can be combined. The TTIs of transmissions that may be combined shall start at the same SFN on each of the multiple radio links. + +## 4.13 E-DCH related procedures + +### 4.13.1 ACK/NACK detection + +The physical layer in the UE shall detect ACK or NACK contained within the E-HICH. Which E-HICH is associated with the corresponding E-DCH transmission is defined in [8]. + +### 4.13.2 Serving and neighbour cell pathloss metric derivation + +The UE shall be capable of measuring the P-CCPCH RSCP of the serving cell and of intra-frequency neighbour cells in accordance with [11]. The P-CCPCH transmit power ( $P_{ref}$ ) of the serving cell and of each intra-frequency neighbour cell in the monitored neighbour cell list shall be signalled by higher layers to the UE in order that the UE may estimate the mean pathloss to the serving cell ( $L_{serv}$ ) and to each of the N neighbour cells in the monitored neighbour cell list ( $L_1, L_2, \dots, L_N$ ). + +Higher layers shall configure the UE to use SNPL reporting type 1 or SNPL reporting type 2. In accordance with the SNPL reporting type, the UE shall be capable of forming a metric corresponding to: + +{for SNPL reporting type 1} + +{for SNPL reporting type 2} + +The metric $\phi$ shall be converted into a logarithmic (dB) value $Q$ and shall be mapped to a Serving and Neighbour Cell Pathloss (SNPL) index according to table 1b. The SNPL index is supplied to and used by higher layers (see [18]). + +**Table 1b: SNPL mapping** + +| Q = 10 \cdot \log_{10}(\phi) | SNPL index | +|--------------------------------------------------|-------------------| +| $Q < -6$ | 0 | +| $-6 \leq Q < -5$ | 1 | +| $-5 \leq Q < -4$ | 2 | +| $-4 \leq Q < -3$ | 3 | +| $-3 \leq Q < -2$ | 4 | +| $-2 \leq Q < -1$ | 5 | +| $-1 \leq Q < 0$ | 6 | +| $0 \leq Q < 1$ | 7 | +| $1 \leq Q < 2$ | 8 | +| $2 \leq Q < 3$ | 9 | +| $3 \leq Q < 4$ | 10 | +| $4 \leq Q < 5$ | 11 | +| $5 \leq Q < 6$ | 12 | +| $6 \leq Q < 7$ | 13 | +| $7 \leq Q < 8$ | 14 | +| $8 \leq Q < 9$ | 15 | +| $9 \leq Q < 10$ | 16 | +| $10 \leq Q < 11$ | 17 | +| $11 \leq Q < 12$ | 18 | +| $12 \leq Q < 13$ | 19 | +| $13 \leq Q < 14$ | 20 | +| $14 \leq Q < 15$ | 21 | +| $15 \leq Q < 16$ | 22 | +| $16 \leq Q < 17$ | 23 | +| $17 \leq Q < 18$ | 24 | +| $18 \leq Q < 19$ | 25 | +| $19 \leq Q < 20$ | 26 | +| $20 \leq Q < 21$ | 27 | +| $21 \leq Q < 22$ | 28 | +| $22 \leq Q < 23$ | 29 | +| $23 \leq Q < 24$ | 30 | +| $24 \leq Q < 25$ | 31 | + +If the higher layer signalling information regarding the required P-CCPCH reference powers is not available, the UE shall return an SNPL index value of 7. + +### 4.13.3 Channelisation code hopping procedure for E-PUCH + +Channelisation code hopping may be applied to E-PUCH transmissions. + +When channelisation code hopping is configured by higher layers, the allocated OVSF code (determined by the code resource related information (CRRI) on E-AGCH – see [9]) is first transformed by the physical layer into a sequence of "effective" allocated OVSF codes (one for each active timeslot of the resource allocation) before further physical layer processing is performed (see figure 5a). The mapping of the allocated code to the sequence of effective codes is a function of the allocated timeslots and of the current CFN. + +![Figure 5a: physical layer interpretation of OVSF code allocation in the case that channelisation code hopping is applied.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +graph TD + A[E-AGCH carrying CRRI field (OVSF code allocation)] --> B[Mapping to effective OVSF code allocation for each allocated timeslot] + B --> C[actual physical resource allocation] + C --> D[Physical Layer Spreading and Modulation] + E[timeslot index] --> B + F[CFN] --> B + subgraph physical_layer [physical layer] + B + C + D + end + style A fill:none,stroke:black + style B fill:none,stroke:black + style C fill:none,stroke:none + style D fill:none,stroke:black + style E fill:none,stroke:none + style F fill:none,stroke:none + +``` + +Figure 5a: physical layer interpretation of OVSF code allocation in the case that channelisation code hopping is applied. + +**Figure 5a - physical layer interpretation of OVSF code allocation in the case that channelisation code hopping is applied** + +The allocated OVSF code (indicated by E-AGCH) is denoted $c$ . The sequence of "effective" allocated OVSF codes is denoted $c_i$ , one for each allocated timeslot index value $t_i$ . $n_{\text{TRRI}}$ is configured by higher layers [15]. + +The set of $n_{\text{TRRI}}$ timeslots configured for E-DCH use is denoted $t_{\text{E-DCH}}$ (where each element of $t_{\text{E-DCH}}$ may assume a value between 0 and 14). The first element of $t_{\text{E-DCH}}$ is associated with $t_i = 0$ , the second element with $t_i = 1$ and so on. $t_i = 0$ therefore corresponds to the lowest numbered timeslot configured for E-DCH use and to the first element (LSB) of the timeslot resource related information bitmap [9]. + +A hopping index parameter $h_i$ is calculated for each timeslot of the E-DCH TTI in which the UE has been allocated as follows: + +The effective allocated OVSF code for timeslot index $t_i$ is then derived from $h_i$ and the channelisation code indicated by the corresponding E-AGCH ( $c$ ) as according to table 1c. + +**Table 1c: Hopping index parameter sequences** + +| CRRI | Hop index $h_i$ | | | | | | | | | | | | | | | | | +|-------------|-----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| SF16 | | | | | | | | | | | | | | | | | | +| 1 | 15 | 1 | 9 | 5 | 13 | 3 | 11 | 7 | 15 | 2 | 10 | 6 | 14 | 4 | 12 | 8 | 16 | +| 2 | 16 | 2 | 10 | 6 | 14 | 4 | 12 | 8 | 16 | 1 | 9 | 5 | 13 | 3 | 11 | 7 | 15 | +| 3 | 17 | 3 | 11 | 7 | 15 | 1 | 9 | 5 | 13 | 4 | 12 | 8 | 16 | 2 | 10 | 6 | 14 | +| 4 | 18 | 4 | 12 | 8 | 16 | 2 | 10 | 6 | 14 | 3 | 11 | 7 | 15 | 1 | 9 | 5 | 13 | +| 5 | 19 | 5 | 13 | 1 | 9 | 7 | 15 | 3 | 11 | 6 | 14 | 2 | 10 | 8 | 16 | 4 | 12 | +| 6 | 20 | 6 | 14 | 2 | 10 | 8 | 16 | 4 | 12 | 5 | 13 | 1 | 9 | 7 | 15 | 3 | 11 | +| 7 | 21 | 7 | 15 | 3 | 11 | 5 | 13 | 1 | 9 | 8 | 16 | 4 | 12 | 6 | 14 | 2 | 10 | +| 8 | 22 | 8 | 16 | 4 | 12 | 6 | 14 | 2 | 10 | 7 | 15 | 3 | 11 | 5 | 13 | 1 | 9 | +| 9 | 23 | 9 | 1 | 13 | 5 | 11 | 3 | 15 | 7 | 10 | 2 | 14 | 6 | 12 | 4 | 16 | 8 | +| 10 | 24 | 10 | 2 | 14 | 6 | 12 | 4 | 16 | 8 | 9 | 1 | 13 | 5 | 11 | 3 | 15 | 7 | +| 11 | 25 | 11 | 3 | 15 | 7 | 9 | 1 | 13 | 5 | 12 | 4 | 16 | 8 | 10 | 2 | 14 | 6 | +| 12 | 26 | 12 | 4 | 16 | 8 | 10 | 2 | 14 | 6 | 11 | 3 | 15 | 7 | 9 | 1 | 13 | 5 | +| 13 | 27 | 13 | 5 | 9 | 1 | 15 | 7 | 11 | 3 | 14 | 6 | 10 | 2 | 16 | 8 | 12 | 4 | +| 14 | 28 | 14 | 6 | 10 | 2 | 16 | 8 | 12 | 4 | 13 | 5 | 9 | 1 | 15 | 7 | 11 | 3 | +| 15 | 29 | 15 | 7 | 11 | 3 | 13 | 5 | 9 | 1 | 16 | 8 | 12 | 4 | 14 | 6 | 10 | 2 | + +16 30 16 8 12 4 14 6 10 2 15 7 11 3 13 5 9 1 + +#### SF8 + +| | | | | | | | | | | | | | | | | | | +|---|----|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 7 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | +| 2 | 8 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | +| 3 | 9 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | +| 4 | 10 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | +| 5 | 11 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | +| 6 | 12 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | +| 7 | 13 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | +| 8 | 14 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | + +#### SF4 + +| | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 3 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | +| 2 | 4 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | +| 3 | 5 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | +| 4 | 6 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | + +#### SF2 + +| | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 1 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | +| 2 | 2 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | + +#### SF1 + +| | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| + +For all subsequent operations, the physical layer shall assume the allocated E-PUCH physical resources to be described by the effective allocated code derived for that timeslot. + +## 4.14 Physical layer procedures for 3.84 Mcps MBSFN IMB + +### 4.14.1 Radio frame timing on the MBSFN layer + +MBSFN cluster search and radio frame synchronisation on the MBSFN layer can be performed via SCH, e.g. by following the steps described in Annex C of [6]. After the primary scrambling code has been identified, the P-CCPCH can be detected and MBSFN system information can be read. + +### 4.14.2 Downlink power control + +The transmit powers of all downlink physical channels is determined by the network. + +#### 4.14.2.1 S-CCPCH + +The TFCI field shall be transmitted at the same constellation power as the data field of the associated physical channel. + +For MBSFN FACH transmission with 16QAM, the UE is informed about the relative transmit power of the S-CCPCH (measured as the power of the transmitted data of S-CCPCH) compared to the primary CPICH transmit power by the higher layers. + +#### 4.14.2.2 MICH + +The UE is informed about the relative transmit power of the MICH (measured as the power over the notification indicators) compared to the primary CPICH transmit power by the higher layers. + +#### 4.14.2.3 P-CPICH + +The UE may assume that the P-CPICH is transmitted with constant power. + +#### 4.14.2.4 T-CPICH + +The UE may assume that each constituent OVSF code of the T-CPICH is transmitted with equal power. The UE may also assume the ratio of power allocated to the T-CPICH and P-CPICH is constant. + +# 5 Physical layer procedures for the 1.28 Mcps option + +## 5.1 Transmitter power control + +The basic purpose of power control is to limit the interference level within the system thus reducing the intercell interference level and to reduce the power consumption in the UE. + +The main characteristics of power control are summarized in the following table. + +**Table 2: Transmit Power Control characteristics** + +| | Uplink | Downlink | +|--------------------|----------------------------------------------------------------------------------------|--------------------------------------------| +| Power control rate | Variable
Closed loop: 0-200 cycles/sec.
Open loop: (about 200us – 3575us delay ) | Variable
Closed loop: 0-200 cycles/sec. | +| Step size | 1,2,3 dB (closed loop) | 1,2,3 dB (closed loop) | +| Remarks | All figures are without processing and measurement times | | + +Note: All codes within one timeslot allocated to the same CCTrCH use the same transmission power in case they have the same Spreading Factor. + +### 5.1.1 Uplink control + +#### 5.1.1.1 General limits + +By means of higher layer signalling, the Maximum\_Allowed\_UL\_TX\_ power for uplink may be set to a value lower than what the terminal power class is capable of. Uplink power control shall be performed while the total UE transmit power is below the maximum allowed output TX power. In some cases the total requested UE transmit power in a timeslot after uplink power control calculation might exceed the maximum allowed output power. In these cases the calculated transmit power of all uplink physical channels in this timeslot shall be scaled by the same amount in dB before transmission in order that the total UE transmission power used shall be the maximum allowed output power. + +The UTRAN may not expect the UE to be capable of reducing its total transmit power below the minimum level specified in [2]. + +#### 5.1.1.2 UpPCH + +The transmit power for the UpPCH is set by higher layers based on open loop power control as described in [15] + +#### 5.1.1.3 PRACH + +The transmit power for the PRACH is set by higher layers based on open loop power control as described in [15]. + +#### 5.1.1.4 DPCH and PUSCH + +The initial transmission power for uplink DPCH and PUSCH is set by higher layers based on open loop power control as described in [15]. The UE then transits into closed loop power control. The node B shall generate TPC commands + +according to a quality target set by higher layers in order to instruct an increase or decrease in the level of transmission power from the UE and send them either in the TPC field of associated downlink CCTrCHs (see [8] for a description of the mapping between DL associated TPC symbols and UL controlled CCTrCH/timeslots) or on PLCCH (see [8] 5A.3.13). If the physical channel power should be increased, the TPC command is set to "up", whereas if the power should be reduced the command is set to "down". A TPC command sent in a downlink CCTrCH or via PLCCH controls all uplink DPCHs and PUSCHs in the associated uplink CCTrCH and timeslot. An example of SIR based UL power control is given in annex A2 + +If signalled by higher layers, the UE must follow the received TPC commands only. In this case, at the UE when the TPC command is judged as 'down', the mobile transmit power shall be reduced by one power control step, whereas if it is judged as 'up', the mobile transmit power shall be raised by one power control step. + +If indicated as allowed by higher layers, the UE may optionally take into account pathloss estimated from beacon function physical channels in addition to the TPC commands when calculating the transmit power. In this case, the mobile transmit power is first modified as described above by the received TPC command and is then further modified based upon the pathloss estimated on recent beacon transmissions. Modifications based upon pathloss shall only be applied when the UE estimates that the pathloss on the uplink transmission timeslot and the pathloss on the beacon timeslots used to derive the modification value are likely to be similar. + +The closed loop power control procedure for UL DPCH and PUSCH is not affected by the use of TSTD. + +In the event of no associated uplink data being transmitted between two related downlink TPC commands, the UE shall ignore the resulting TPC command. The transmit power for the next instance of the timeslot/CCTrCH pair shall then be set: + +- i) to the power level of the previous uplink transmission, optionally modified to compensate for the change in pathloss observed during the uplink transmission pause or, +- ii) using the open loop procedure as for initial transmissions. + +The UE shall select which of the above methods to apply. For short transmission pauses method (i) should be used. + +##### 5.1.1.4.1 Gain factors + +Same as that of 3.84 Mcps TDD, cf. [4.2.2.3.1 Gain factors]. + +##### 5.1.1.4.2 Out of synchronization handling + +In the case that uplink DPCH is controlled by TPC commands carried on downlink DPCH, out of synchronisation handling is the same as that of 3.84 Mcps TDD, cf. [4.2.2.3.2 Out of synchronisation handling]. + +In the case that uplink DPCH is controlled by TPC commands carried on PLCCH, the UE shall shut off the transmission of an UL CCTrCH if the following criteria are fulfilled for the PLCCH carrying its TPC commands: + +- The UE estimates the received PLCCH quality over the last 160 ms period to be worse than a threshold $Q_{out}$ . $Q_{out}$ is defined implicitly by the relevant tests in [2]. + +The UE shall subsequently resume the uplink transmission of the CCTrCH if the following criteria are fulfilled: + +- The UE estimates the received PLCCH reception quality over the last 160 ms period to be better than a threshold $Q_{in}$ . $Q_{in}$ is defined implicitly by the relevant tests in [2]. + +#### 5.1.1.5 HS-SICH + +If the UE is not configured in MIMO mode, the transmit power of the HS-SICH shall be set by the UE according to the procedures described below. In the case that an ACK is being transmitted on the HS-SICH, the UE shall apply a power offset to the transmit power of the entire HS-SICH. This power offset shall be signalled by higher layers. + +For the transmissions on the semi-persistent HS-PDSCH resources without an HS-SCCH, the TPC command for HS-SICH can be conveyed in HS-PDSCH. + +On receipt of a TPC command in the HS-SCCH or HS-PDSCH, the UE shall adjust the HS-SICH transmit power according to the power control step size specified by higher layers. The UE shall ignore the TPC command transmitted + +on an HS-SCCH order which is an uplink synchronization establishment command. An example of SIR based UL power control is given in annex A5. + +- i) However, for the first HS-SICH transmission following the first detected HS-SCCH transmission, the UE shall use open loop power control to set the HS-SICH transmit power for that transmission. In this case, the transmission power for HS-SICH is set by higher layers based on open loop power control as described in [15]. +- ii) When the transmission interval of HS-SICHs, which are in the same time slot, is less than a certain threshold, which is signalled by higher layers, UE shall adjust the transmit power according to received TPC command in HS-SCCH or HS-PDSCH during HS-SICH transmission pause based on transmission power of last instance. When receipt of TPC commands in HS-PDSCH and in HS-SCCH is in the same sub-frame, UE shall treat one single TPC command if they are identical and discard them if they are different. If indicated by higher layers, UE should take into account the pathloss compensation by means of beacon channel estimation in addition to the TPC command when calculating HS-SICH transmit power. +- iii) When the transmission interval of HS-SICHs, which are in the same time slot, is equal or larger than a certain threshold, for the next instance of HS-SICH, UE shall use open loop power control described above for the initial transmission. + +If the UE is configured in MIMO mode, the transmit power of the HS-SICH shall be set by the UE according to the procedures described below. + +The procedure for MIMO single stream transmission is the same as that the UE is not configured in MIMO mode. + +For MIMO dual stream transmission, in the case that two ACKs are being transmitted on the HS-SICH, the UE shall apply a power offset to the transmit power of the entire HS-SICH. This power offset shall be signalled by higher layers. + +On receipt of a TPC command in the HS-SCCH or HS-PDSCH, the UE shall adjust the HS-SICH transmit power according to the power control step size specified by higher layers. An example of SIR based UL power control is given in annex A5. + +- i) However, for the first HS-SICH transmission following the first detected HS-SCCH transmission, the UE shall use open loop power control to set the HS-SICH transmit power for that transmission. In the case of dual stream transmission, a delta is applied to the HS-SICH transmission power. The delta implies the required power offset of the HS-SICH transmission for the different number of the data streams under the limit of SIR target. This transmission power is set by higher layers based on open loop power control as described in [15]. +- ii) When the transmission interval of HS-SICHs, which are in the same time slot, is less than a certain threshold, which is signalled by higher layers, UE shall adjust the transmit power according to received TPC command during HS-SICH transmission pause based on transmission power of last instance. In the case of dual stream transmission, a delta is applied to the HS-SICH transmission power. If indicated by higher layers, UE should take into account the pathloss compensation by means of beacon channel estimation in addition to the TPC command when calculating HS-SICH transmit power. +- iii) When the transmission interval of HS-SICHs, which are in the same time slot, is equal or larger than a certain threshold, for the next instance of HS-SICH, UE shall use open loop power control described above for the initial transmission. + +#### 5.1.1.6 E-PUCH + +For multi-carrier E-DCH transmission, the open-loop and closed-loop power control of E-PUCH on each carrier is independent from each other. The power of E-PUCH in each timeslot on each carrier is set as follows. Note that the power of E-PUCH in the timeslots with same spreading factor is the same. + +The power of E-PUCH in each timeslot is set following the same principle used for DPCH/PUSCH in R4/5/6[15] and in 5.1.1.4, i.e., the combination of open-loop power control and traditional closed-loop power control: + +- the initial transmit power of E-PUCH is set based on an open-loop power control scheme, then +- the transmission power control transits into closed-loop power control using TPC commands carried on E-AGCH or on E-HICH on the same carrier. For non-scheduled transmission, the TPC commands are carried on E-HICH only. Both TPC commands carried on E-AGCH and E-HICH are used on E-PUCH + +The transmit power for E-PUCH set in each timeslot is calculated as follows: + +... where: + +- $P_{E-PUCH}$ is the transmit power of the E-DCH physical channel E-PUCH in each timeslot. +- $P_{e-base}$ is a closed-loop quantity maintained by the UE and NodeB for each carrier, and which is incremented or decremented by a value $\Delta_{e-base}$ upon each receipt of a TPC command on E-AGCH for scheduled transmission or on E-HICH for non-scheduled transmission on the same carrier. On receipt of a TPC "up" command, $P_{e-base}$ is incremented by $\Delta_{e-base}$ . On receipt of a TPC "down" command, $P_{e-base}$ is decremented by $\Delta_{e-base}$ . The TPC step size $\Delta_{e-base}$ is configured by higher layers [15]. + +$$P_{e-base} = PRX_{des\_base} + step * \sum_i TPC_i = PRX_{des\_base} + P_{TPC}$$ + +where, $PRX_{des\_base}$ is the *reference Desired E-PUCH RX power* signalled by RRC signalling for each carrier according to [15], which is set to the average value of the interference signal power level over the timeslots configured for E-DCH use. + +$step$ is the power control step size $\Delta_{e-base}$ configured by higher layers, and $TPC_i$ is a closed-loop control command. + +- $L$ is a pathloss term derived from beacon function physical channels. The same as that in 5.1.1.4, if indicated as allowed by higher layers, the UE may optionally take into account pathloss modification which is estimated from the most recently received beacon function physical channel transmission, in addition to the TPC commands when calculating the transmit power. +- $\beta_e$ is the gain factor for the selected E-TFC transport block size, the allocated E-PUCH physical resources, and the Modulation type and HARQ power offset according to subclause 5.1.1.6.1. If the smallest E-TFC is selected, $\beta_e$ equals to the sum of absolute grant value and $\alpha_e$ . + +Higher layers in the UE shall use the current calculated E-PUCH power in conjunction with the current absolute grant (power) value in order to determine the set of E-TFC's available. + +UE maintains a closed-loop quantity $P_{e-base}$ for both scheduled transmission and non-scheduled transmission. $P_{e-base}$ is incremented or decremented by a value $\Delta_{e-base}$ upon each receipt of a TPC command on E-AGCH and on E-HICH on the same carrier. When receipt of TPC commands on E-AGCH and on E-HICH is in the same sub-frame, UE shall treat one single TPC command if they are identical and discard them if they are different. + +When following an extended pause, which is signalled by higher layers, in the reception of TPC commands on E-AGCH and on E-HICH, the UE shall set $P_{e-base}$ equal to the *reference Desired E-PUCH RX power*. When receipt of TPC commands on E-AGCH or on E-HICH recommences, the TPC commands shall be used to modify $P_{e-base}$ from its previously set value. + +##### 5.1.1.6.1 Gain factors for E-PUCH + +A beta factor shall be derived by the UE as a function of: + +- the selected E-TFC transport block size +- the E-PUCH resource occupation in the E-DCH TTI +- the modulation type (QPSK/16-QAM) +- the HARQ power offset + +Higher layers shall provide a mapping table containing a set of reference points, which defines the relationship between the coderate of E-DCH transmission ( $\lambda_e$ ) and the relative reference power per resource unit ( $\beta_\lambda$ dB). The mapping table is provided separately for each of QPSK and 16-QAM modulation. + +The coderate of E-DCH transmission $\lambda_e$ for the selected E-TFC, physical resource allocation and modulation type is defined as: + +... in which $S_e$ is the transport block size of the selected E-TFC and $R_e$ is the number of physical channel bits output from the physical channel mapping stage of E-DCH transport channel processing as described in [9]. The precision requirement for $\lambda_e$ is $1 \times 10^{-4}$ and the quantization mode is truncation. + +The maximum and minimum values of $\lambda$ are the maximum and minimum values of Reference Code Rate respectively, which are signalled by higher layers for the appropriate modulation type [15], and are denoted $\lambda_{\max}$ and $\lambda_{\min}$ respectively. For a given $\lambda_e$ there exist a $\lambda_0$ and a $\lambda_1$ such that: + +- If $\lambda_{\min} \leq \lambda_e < \lambda_{\max}$ + - $\lambda_0$ is the largest $\lambda$ signalled by higher layers for the appropriate modulation type and for which $\lambda \leq \lambda_e$ + - $\lambda_1$ is the smallest $\lambda$ signalled by higher layers for the appropriate modulation type and for which $\lambda > \lambda_e$ +- Else + - If $\lambda_e < \lambda_{\min}$ then $\lambda_0 = \lambda_{\min}$ and $\lambda_1$ is the smallest signalled $\lambda$ for which $\lambda > \lambda_{\min}$ . + - If $\lambda_e \geq \lambda_{\max}$ then $\lambda_0$ is the largest signalled $\lambda$ for which $\lambda < \lambda_{\max}$ and $\lambda_1 = \lambda_{\max}$ + +Associated with $\lambda_0$ and $\lambda_1$ are the corresponding $\beta_{\lambda_0}$ and $\beta_{\lambda_1}$ which define the reference points signalled by higher layers. The normalised (per-resource-unit) beta value for the selected E-TFC and E-PUCH resource set is denoted $\beta_{0,e}$ and is: + +The precision requirement for $\beta_{0,e}$ is $1 \times 10^{-3}$ and the quantization mode is truncation. + +is a logarithmic value set as a function of the E-PUCH spreading factor ( $SF_{E-PUCH}$ ) according to table 2a. + +**Table 2a: Tabulated $\alpha_e$ values** + +| $SF_{E-PUCH}$ | (dB) | +|---------------|------| +| 1 | 12 | +| 2 | 9 | +| 4 | 6 | +| 8 | 3 | +| 16 | 0 | + +$\beta_e$ is then derived as + +$\Delta_{harq}$ is set by higher layers ( see [18] ). + +#### 5.1.1.7 E-RUCCH + +The transmit power for the E-RUCCH is set following the same formula used for PRACH based on open loop power control as described in [15]. + +#### 5.1.1.8 Standalone midamble channel + +If the UE is configured in MIMO mode, the transmit power for the standalone midamble channel shall be the same as that used for the associated HS-SICH in the same subframe. + +If the UE is configured in MU-MIMO mode, the transmit power for the standalone midamble channel shall make reference to the last transmitted HS-SICH or E-PUCH. When the last transmitted uplink channel is HS-SICH, the transmit power of the standalone midamble channel shall be the same as the last transmitted HS-SICH. When the last + +transmitted uplink channel is E-PUCH, the transmit power of the standalone midamble channel shall be calculated as follows: + +... where: + +- $P_{desired}$ is the desired receiving power of E-PUCH. +- $G$ is the gain factor for standalone midamble channel, and should be configured by high layer. +- $L$ is a pathloss term derived from beacon function physical channels. + +### 5.1.2 Downlink control + +The total downlink transmission power at the Node B within one timeslot shall not exceed the Maximum Transmission Power set by higher layer signalling. + +#### 5.1.2.1 P-CCPCH + +Same as that of 3.84 Mcps TDD, cf.[4.2.3.1 P-CCPCH]. + +#### 5.1.2.2 The power of the FPACH + +The transmit power for the FPACH is set by the higher layer signalling [16]. + +#### 5.1.2.3 S-CCPCH, PICH + +Same as that of 3.84 Mcps TDD, cf.[4.2.3.2 S-CCPCH , PICH]. + +#### 5.1.2.3A MICH + +Same as that of 3.84 Mcps TDD, cf.[4.2.3.2A MICH]. + +#### 5.1.2.4 DPCH, PDSCH + +The initial transmission power of the downlink Dedicated Physical Channel is signalled by higher layers. After the initial transmission, the node B transits into closed-loop TPC. The UE shall generate TPC commands according to a quality target set by higher layers in order to control the level of transmission power from the node B and send them in the TPC field of associated uplink CCTrCHs (see [8] for a description of the mapping between UL associated TPC symbols and DL controlled CCTrCH/timeslots) or in the Non-scheduled E-PUCH when the associated uplink CCTrCHs do not exist. If the physical channel power should be increased, the TPC command is set to "up", whereas if the power should be reduced the command is set to "down". A TPC command sent in an uplink CCTrCH or in the Non-scheduled E-PUCH when the associated uplink CCTrCH does not exist controls all downlink DPCHs or PDSCHs in the associated downlink CCTrCH and timeslot. + +UTRAN may decide how to adjust the transmit power in response to the received TPC command + +When TSTD is applied, the UE can use two consecutive measurements of the received SIR in two consecutive sub-frames to generate the power control command. An example implementation of DL power control procedure for 1.28 Mcps TDD when TSTD is applied is given in Annex A.3. + +The transmission power of one DPCH or PDSCH shall not exceed the limits set by higher layer signalling by means of Maximum\_DL\_Power (dB) and Minimum\_DL\_Power (dB). The transmission power is defined as the average power over one timeslot of the complex QPSK (or 8PSK respectively) symbols of a single DPCH or PDSCH before spreading relative to the power of the P-CCPCH. + +Each TPC command shall be based on all associated downlink transmissions since the previous related TPC command. + +In the event of no associated downlink data being transmitted between two related TPC commands, the UTRAN should ignore the resulting TPC command. + +##### 5.1.2.4.1 Out of synchronisation handling + +Same as that of 3.84 Mcps TDD, cf.[4.2.3.4.1 Out of synchronisation handling]. + +#### 5.1.2.5 HS-PDSCH + +The power control for HS-PDSCH for 1.28 Mcps TDD is the same as for 3.84 Mcps, see section 4.2.3.5 + +#### 5.1.2.6 HS-SCCH + +Higher layers shall indicate the maximum transmit power of the HS-SCCH. The Node-B shall not exceed this maximum power when setting the HS-SCCH power. + +The initial power of the HS-SCCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may optionally power control the HS-SCCH. This may be done using TPC commands sent by the UE in the HS-SICH. When the transmission interval of HS-SCCHs, which are in the same time slot, is more than or equal to a certain threshold, which is signalled by higher layers, NodeB shall use initial transmit power for the next HS-SCCH transmission. + +The UE shall set the TPC commands in the HS-SICH in order to control the transmit power of the HS-SCCH. The TPC commands shall be set in order to meet the HS-SCCH target BLER. + +The accuracy of the received HS-SCCH BLER estimate made by the UE may be enhanced by a suitable use of the HCSN field received within the HS-SCCH itself [9]. This field shall initially be set to zero and shall be incremented by the NodeB each time an HS-SCCH is transmitted to the UE. UE without a dedicated UE identity in CELL\_FACH state and UE in CELL\_PCH state shall ignore the value of HCSN. + +#### 5.1.2.7 PLCCH + +The initial transmission power of the downlink PLCCH is signalled by higher layers. After the initial transmission, the transmission power of PLCCH is under the control of Node-B. The Node-B may optionally adjust the transmission power of PLCCH according to the received TPC commands which are carried by the PLCCH-controlled UL CCTrCH(s). The UE shall generate TPC commands according to a PLCCH quality target set by higher layers. If the PLCCH power should be increased, the TPC command is set to "up", whereas if the power should be reduced the command is set to "down". UTRAN may decide how to adjust the transmit power in response to the received TPC commands. The average power of transmitted PLCCH symbols over one timeslot shall not exceed the limits set by higher layers. The transmission power is defined as the average power over one timeslot of the complex QPSK symbols of a single PLCCH before spreading relative to the power of the P-CCPCH. + +#### 5.1.2.8 E-AGCH + +For multi-carrier E-DCH transmission, the power control of E-AGCH on each carrier is independent from each other and described as follows. + +Higher layers shall indicate the maximum transmit power of the E-AGCH. The Node-B shall not exceed this maximum power when setting the E-AGCH power. + +The initial power of the E-AGCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may optionally power control the E-AGCH. This may be done using TPC commands sent by the UE in the scheduled E-PUCH on the same carrier. + +The UE shall set the TPC commands in the Scheduled E-PUCH on the same carrier in order to control the transmit power of the E-AGCH. The TPC commands shall be set in order to meet the E-AGCH target BLER. + +The accuracy of the received E-AGCH BLER estimate made by the UE shall be enhanced by a suitable use of the ECSN field received within the E-AGCH itself [9]. This field shall initially be set to zero and shall be incremented by the Node-B each time an E-AGCH is transmitted to the UE. For each carrier in multi-carrier E-DCH transmission, the ECSN shall initially be set to zero and shall be incremented by the Node-B each time an E-AGCH is transmitted on the carrier to the UE. + +#### 5.1.2.9 E-HICH + +The power of the E- HICH is under the control of the Node B. + +## 5.2 UL synchronisation + +### 5.2.1 General description + +Support of UL synchronization is mandatory for the UE. + +#### 5.2.1.1 Preparation of uplink synchronization (downlink synchronization) + +When a UE is powered on, it first needs to establish the downlink synchronisation with the cell. Only after the UE has established the downlink synchronisation, it shall start the uplink synchronisation procedure. + +#### 5.2.1.2 Establishment of uplink synchronization + +The establishment of uplink synchronization is done during the random access procedure and involves the UpPCH and the PRACH or the E-RUCCH. + +Although the UE can receive the downlink signal from the Node B, the distance to Node B is still uncertain. This would lead to unsynchronised uplink transmission. Therefore, the first transmission in the uplink direction is performed in a special time-slot UpPTS or other uplink access position indicated by UTRAN to reduce interference in the traffic time-slots. + +After the detection of the SYNC-UL sequence in the searching window, the Node B will evaluate the timing, and reply by sending the adjustment information to the UE to modify its timing for next transmission. This is done with the FPACH within the following 4 sub-frames. After sending the PRACH or the E-RUCCH, the uplink synchronization is established. The uplink synchronisation procedure shall also be used for the re-establishment of the uplink synchronisation when uplink is out of synchronisation. + +#### 5.2.1.3 Maintenance of uplink synchronisation + +Uplink synchronization is maintained in 1.28 Mcps TDD by sending the uplink advanced in time with respect to the timing of the received downlink. + +For the maintenance of the uplink synchronization, the midamble field of each uplink burst can be used. + +In each uplink time slot the midamble for each UE is different. The Node B may estimate the timing by evaluating the channel impulse response of each UE in the same time slot. Then, in the next available downlink time slot, the Node B will signal Synchronisation Shift (SS) commands to enable the UE to properly adjust its Tx timing. + +### 5.2.2 UpPCH + +Open loop uplink synchronisation control is used for UpPCH. + +The UE may estimate the propagation delay $\Delta t_p$ based upon the path loss using the received P-CCPCH and/or DwPCH power. + +The UpPCH is sent to the Node B advanced in time according to the timing of the received DwPCH. The time of the beginning of the UpPCH $T_{TX-UpPCH}$ is given by: + +$$T_{TX-UpPCH} = T_{RX-DwPCH} - 2\Delta t_p + 12 * 16 T_c + n_{UpPCHShift} * 16 T_c$$ + +$n_{UpPCHShift} = 0..127$ , $n_{UpPCHShift}$ is indicated by higher layers + +in multiple of 1/8 chips, where + +$T_{TX-UpPCH}$ is the beginning time of UpPCH transmission with the UE's timing, + +$T_{RX-DwPCH}$ is the received beginning time of DwPCH with the UE's timing, + +$2\Delta t_p$ is the timing advance of the UpPCH default value is $48T_c$ . + +### 5.2.3 PRACH + +The Node B shall measure the received SYNC-UL timing deviation $UpPCH_{POS}$ . $UpPCH_{POS}$ is sent in the FPACH and is represented as a 13 bit number (0-8191) being the multiple of 1/8 chips which is nearest to received position of the $UpPCH$ . + +Time of the beginning of the PRACH $T_{TX-PRACH}$ is given by: + +$$T_{TX-PRACH} = T_{RX-PRACH} - (UpPCH_{ADV} + UpPCH_{POS} - 8 * 16 T_c)$$ + +in multiple of 1/8 chips, where + +$T_{TX-PRACH}$ is the beginning time of PRACH transmission with the UE's timing, + +$T_{RX-PRACH}$ is the beginning time of PRACH reception with the UE's timing if the PRACH was a DL channel. + +### 5.2.4 DPCH and PUSCH + +The closed loop uplink synchronisation control uses layer 1 symbols (SS commands) for DPCH and PUSCH. After establishment of the uplink synchronisation, NodeB and UE start to use the closed loop UL synchronisation control procedure. This procedure is continuous during connected mode. + +The Node B will continuously measure the timing of the UE and send the necessary synchronisation shift commands in each sub-frame. The UE shall derive a single SS command separately for each controlled uplink timeslot by combining all received SS commands that are related to the controlled time slot (cf. [8]) and that are received within the last up to M sub-frames. The value of the "Uplink synchronisation frequency" M (1..8) is configured by higher layers. + +When the combined SS command is judged as 'down', the UE transmit timing for the controlled UL timeslot shall be delayed by one timing adjustment step of k/8 chips. When the command is judged as 'up', the UE transmit timing for the controlled UL timeslot shall be advanced by one timing adjustment step of k/8 chips. When the command is judged as 'do nothing', the timing shall not be changed. The value of the "Uplink synchronisation step size" k (1..8) is configured by higher layers. + +The timing adjustment shall take place in each sub-frame satisfying the following equation: + +where + +SFN' is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from SFN' by + +$SFN = SFN' \text{ div } 2$ , where div is the remainder free division operation. + +During a 1.28 Mcps TDD to 1.28 Mcps TDD hand-over the UE shall transmit in the new cell with timing advance TA adjusted by the relative timing difference $\Delta t$ between the new and the old cell if indicated by higher layers: + +$$TA_{new} = TA_{old} + 2\Delta t.$$ + +#### 5.2.4.1 Out of synchronization handling + +Same as that of 3,84 Mcps TDD, cf.[ 4.2.2.3.2 Out of synchronisation handling.] + +### 5.2.5 HS-SICH + +If there is associated uplink DPCH or non-scheduled E-PUCH, the initial transmit timing for the HS-SICH shall be taken from that of the associated uplink DPCH or non-scheduled E-PUCH. Otherwise, the initial transmit timing for the HS-SICH shall be taken from that of the last uplink transmission except $UpPCH$ transmission. The UE shall then adjust the timing of the HS-SICH according to SS commands transmitted to it on the HS-SCCH or HS-PDSCH. The step size for these commands shall be signalled to the UE by higher layers. The UE shall ignore the SS command transmitted on an HS-SCCH order which is an uplink synchronization establishment command. In the case that there is a gap of one or more subframes during which no SS commands are received by the UE, the UE shall adjust the timing of the HS-SICH + +according to the associated uplink DPCH or non-scheduled E-PUCH or other uplink channel except UpPCH until such time as another HS-SCCH transmission or HS-PDSCH with SS command is received. + +### 5.2.6 E-PUCH + +Uplink synchronization control procedure for E-PUCH remains the same as that used for DPCH, cf. 5.2.4 DPCH and PUSCH, using SS commands carried on E-AGCH or on E-HICH. When receipt of SS commands on E-AGCH and on E-HICH is in the same sub-frame, UE shall treat one single SS command if they are identical and discard them if they are different. + +If configured with DPCH, the timing of E-PUCH can be directly set to the timing of the DPCH. If configured with non-scheduled transmission, the timing of scheduled E-PUCH can be set to the timing of the non-scheduled E-PUCH. If neither DPCH nor non-scheduled transmission is configured, the timing of E-PUCH can be set to the timing of other uplink channels except UpPCH. + +For multi-carrier E-DCH transmission, in one TTI, the timing advance of the E-PUCHs of all carriers of one UE is the same. The UE shall combine all the SS commands on each E-AGCH and E-HICH in the same TTI into one UL timing advance value. + +### 5.2.7 E-RUCCH + +The Node B shall measure the received SYNC-UL timing deviation $UpPCH_{POS}$ . $UpPCH_{POS}$ is sent in the FPACH and is represented as an 13 bit number (0-8191) being the multiple of 1/8 chips which is nearest to received position of the UpPCH. + +Time of the beginning of the E-RUCCH $T_{TX-E-RUCCH}$ is given by: + +$$T_{TX-E-RUCCH} = T_{RX-E-RUCCH} - (UpPCH_{ADV} + UpPCH_{POS} - 8 * 16 T_c)$$ + +in multiple of 1/8 chips, where + +$T_{TX-E-RUCCH}$ is the beginning time of E-RUCCH transmission with the UE's timing, + +$T_{RX-E-RUCCH}$ is the beginning time of E-RUCCH reception with the UE's timing if the E-RUCCH was a DL channel, + +$UpPCH_{ADV}$ is the timing advance of the UpPCH. + +### 5.2.8 Standalone midamble channel + +The transmit timing for the standalone midamble channel shall be taken from that of the last uplink transmission. + +## 5.3 Synchronisation procedures + +### 5.3.1 Cell search + +During the initial cell search, the UE searches for a cell. It then determines the DwPTS synchronisation, scrambling code and basic midamble code, control multi-frame synchronisation and then reads the BCH. How cell search is typically done is described in Annex CA. + +For MBSFN FACH, the downlink scrambling codes and basic midamble codes to be used for non-beacon timeslots are signalled by higher layers. + +### 5.3.2 DCH synchronization + +The DPCH synchronisation is the same as that of 3.84 Mcps TDD, cf. [4.4.2 Dedicated channel synchronisation]. + +### 5.3.2A Shared physical channel synchronization + +For HS-DSCH and E-PUCH operation without DPCH, the synchronisation procedure is defined in the subclause. + +### 5.3.2A.1 Synchronisation primitives + +#### 5.3.2A.1.1 General + +For the shared physical channels, synchronisation primitives are used to indicate the synchronisation status of radio links, both in uplink and downlink. The definition of the primitives is given in the following subclauses. + +#### 5.3.2A.1.2 Downlink synchronisation primitives + +The UE shall measure any of the following downlink physical channels on any carrier to estimate downlink quality. + +- a) HS-PDSCH +- b) HS-SCCH +- c) E-AGCH + +Layer 1 in the UE shall check the synchronization status of downlink physical channels on all carriers. Synchronisation status is indicated to higher layers, using the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitives. + +The criteria for reporting synchronization status are defined in two different phases. + +The first phase lasts until the downlink shared channel is considered to be established by higher layers. During this phase, out-of-sync shall not be reported. in-sync shall be reported using the CPHY-Sync-IND primitive if the following criterion is fulfilled. + +- At least one downlink physical channel with a CRC attached is received in the current subframe with correct CRC. + +The second phase starts after the downlink shared channel is considered established by higher layers. During this phase, both out-of-sync and in-sync are reported as follows. + +Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive based on the synchronization status in an out-of-sync detection window if the following criterion is fulfilled. The out-of-sync detection window (out-of-sync window) is configured by higher layers. + +- No downlink physical channel has been received with a correct CRC in the out-of-sync detection window period. + +In the second phase, the first out-of-sync detection window starts when the second phase starts; after this, the next out-of-sync detection window starts right after the previous out-of-sync detection window. + +In-sync shall be reported using the CPHY-Sync-IND primitive if the following criteria is fulfilled: + +- At least one downlink physical channel with a CRC attached is received in the current subframe with correct CRC. + +#### 5.3.2A.1.3 Uplink synchronisation primitives + +Layer 1 in the Node B shall check synchronisation status of uplink physical channels. Synchronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitive. The exact criteria for indicating in-sync/out-of-sync is not subject to specification. + +### 5.3.2A.2 Radio link monitoring + +#### 5.3.2A.2.1 Downlink radio link failure + +The downlink shared physical channels are monitored by the UE, to trigger radio link failure procedures. The downlink radio link failure status is specified in [15], and is based on the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. + +#### 5.3.2A.2.2 Uplink radio link failure/restore + +The uplink shared physical channels are monitored by the Node B in order to trigger uplink radio link failure/restore procedures. The uplink radio link failure/restore status is reported using the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. + +When the uplink shared physical channel is in the in-sync state, Node B shall start timer T\_RLFAILURE after receiving N\_OUTSYNC\_IND consecutive out-of-sync indications. Node B shall stop and reset timer T\_RLFAILURE upon receiving successive N\_INSYNC\_IND in-sync indications. If T\_RLFAILURE expires, Node B shall indicate to higher layers the uplink shared physical channel is out-of-sync using the synchronization status primitives. Furthermore, the uplink shared physical channel state shall be changed to the out-of-sync state. + +When the uplink shared physical channel is in the out-of-sync state, after receiving N\_INSYNC\_IND successive in-sync indications Node B shall indicate that the uplink shared physical channel has re-established synchronisation and the uplink shared physical channel's state shall be changed to the in-sync-state. The specific parameter settings (values of T\_RLFAILURE, N\_OUTSYNC\_IND, and N\_INSYNC\_IND) are configurable, see [16]. + +### 5.3.3 Synchronization procedure in CELL\_FACH state + +#### 5.3.3.1 Uplink synchronization status detection + +Maintaining of uplink synchronization is not needed in CELL\_FACH state, UE could be out of synchronization after a period of transmission pause. + +The uplink synchronization status detection is under control of Node B, which determines UE's synchronization status according to a timer T-sync. The timer is UE specific and the parameter is configured by higher layers. Node B determines the UE out of synchronization when the T-sync timer expires and in synchronization otherwise. The details of the timer T-sync operation are shown as below: + +- Initially starting the timer + +When Node B receives the UE's uplink E-RUCCH transmission correctly, it will initially start the timer. + +- Restarting the timer + +When Node B receives the UE's any uplink transmission (e.g. E-RUCCH, E-DCH or HS-SICH) correctly, it will restart the timer. + +#### 5.3.3.2 Establishment of uplink synchronization + +Node B shall order UE to establish the uplink synchronization via HS-SCCH order in case that it detects the UE is out of uplink synchronization. Response to this synchronization establishment command, UE then initiates the random access procedure, cf [subclause 5.6 Random Access Procedure], which only involves the UpPCH and the E-RUCCH. + +Node B will limit the synchronization delay based on a timer T-protect. If Node B doesn't receive the E-RUCCH in the synchronization procedure before T-protect expires, Node B will restart another uplink synchronization procedure via HS-SCCH order. After N-protect successive uplink synchronization attempts, Node B shall terminate the synchronization procedure and indicate an uplink synchronization failure to higher layers. The specific parameter settings (values of T-protect and N-protect) are configured by higher layers. + +## 5.4 Discontinuous transmission (DTX) procedure + +The DTX procedure shall be applied for CCTrCHs mapped to S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, if the total bit rate of the CCTrCH differs from the total channel bit rate of the physical channels allocated to this CCTrCH. + +Rate matching is used in order to fill resource units completely, that are only partially filled with data. In the case that after rate matching and multiplexing no data at all is to be transmitted in a resource unit the complete resource unit shall be discarded from transmission (DTX), unless a Special Burst is transmitted in the RU. This applies also to the case where only one resource unit is allocated and no data has to be transmitted. + +The special burst is transmitted in both consecutive subframes (subframe#1 and #2). SS Bits may be transmitted in Special Bursts for each CCTrCH mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels. + +### 5.4.1 Description of special bursts + +For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the Special Burst has the same timeslot format as the burst used for data provided by higher layers. If the timeslot format contains a TFCI field, then the TFCI field shall be filled with "0" bits. The Special Burst may also carry layer 1 control symbols such as TPC bits for the purposes of inner-loop power control. The data portions of the Special Burst are filled with an arbitrary bit pattern. + +For S-CCPCH, DL DPCH, PUSCH and PDSCH, the transmission power of the special burst shall be the same as that of the substituted physical channel of the CCTrCH. For UL DPCH, if the gain factor of the zero rate TFC is explicitly signalled by high layer, the transmission power of the special burst shall be weighted by the gain factor $\beta$ of the zero rate TFC [refer 5.1.1.4.1], otherwise the transmission power of the special burst shall be the same as that of the substituted physical channel of the CCTrCH. In the case of uplink physical channels where autonomous spreading factor change by the UE is permitted by higher layers, the substituted physical channel is considered to be that which would have been employed for the lowest non-zero rate TFC within the set of allowed TFC's and the transmission power of the Special Burst shall again correspond to that of the physical channel substituted. + +## 5.4.2 Use of special bursts during DTX + +In the case that after link establishment there are no transport blocks provided for transmission by higher layers for a given CCTrCH mapped to UL DPCH, DL DPCH, PUSCH or PDSCH physical channels, then a Special Burst shall be transmitted in the first allocated frame of the transmission pause. If, including the first frame, there is a consecutive period of Special Burst Period (SBP) frames without transport blocks provided by higher layers, then another special burst shall be generated and transmitted at the next possible frame. This pattern shall be continued until transport blocks are provided for the CCTrCH by the higher layers. SBP shall be provided by higher layers. The value of SBP shall be independently specified for uplink and for downlink and shall be designated as + +SBGP (special burst generation period) for uplink transmissions + +SBSP (special burst scheduling parameter) for downlink transmissions + +The default value for both SBGP and SBSP shall be 8. + +If DTX is applied on S-CCPCH carrying MBSFN FACH, special burst shall be sent in the first radio frame of each associated TTI. + +The Special Burst shall be transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) as defined by the rate matching function in [9]. + +## 5.4.3 Use of special bursts for initial establishment / reconfiguration + +Upon initial establishment or reconfiguration for either 160 ms following detection of in-sync, or until the first transport block is received from higher layers, both the UE and the Node B shall transmit the special burst for each CCTrCH mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels. + +The Special Burst shall be transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) as defined by the rate matching function in [9]. + +## 5.5 Downlink transmit diversity + +Downlink Transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-AGCH, E-HICH and DwPCH is optional in UTRAN. Its support is mandatory at the UE. + +### 5.5.1 Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH + +Time Switched Transmit Diversity (TSTD) may be employed as transmit diversity scheme for downlink DPCH and PDSCH. Closed loop Transmit Diversity may be employed as transmit diversity scheme for downlink DPCH, HS-SCCH, HS-PDSCH and E-AGCH. + +#### 5.5.1.1 TSTD for PDSCH and DPCH + +TSTD can be employed as transmit diversity scheme for PDSCH and downlink DPCH. An example for the transmitter structure of the TSTD transmitter is shown in figure 6. Channel coding, rate matching, interleaving, bit-to-symbol mapping, spreading, and scrambling are performed as in the non-diversity mode. Then the data is time multiplexed with the midamble sequence. Then, after pulse shaping, modulation and amplification, DPCH and/or PDSCH is transmitted from antenna 1 and antenna 2 alternately every sub-frame. Not all DPCHs and/or PDSCHs in the sub-frame need to be transmitted on the same antenna and not all DPCHs and/or PDSCHs within a sub-frame have to use TSTD. Figure 7 shows an example for the antenna switching pattern for the transmission of DPCH/PDSCH for the case that all physical channels are transmitted with TSTD and are using the same antenna in the sub-frame. + +![Figure 6: Example for TSTD Transmitter structure for DPCH/PDSCH and P-CCPCH.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The diagram illustrates the transmitter structure for Time Switched Transmit Diversity (TSTD). The process begins with 'Data' entering an 'ENC' (Encoder) block, followed by an 'INT' (Interleaver) block. The signal then enters a 'DEMUX' (Demultiplexer) which splits it into 'I' and 'Q' branches. Each branch passes through an 'SPR' (Spreading) block and an 'SCR' (Scrambling) block. These branches, along with a 'Midamble' input (also split into I and Q), enter a 'TDM' (Time Division Multiplexing) block. The TDM outputs separate I and Q signals, each passing through an 'FIR' (Finite Impulse Response) filter. The I-branch is multiplied by $\cos \omega_c t$ and the Q-branch by $-\sin \omega_c t$ . The signals are then summed. A 'Switching control' unit manages a switch that toggles the final output between 'ANT 1' and 'ANT 2'. + +Figure 6: Example for TSTD Transmitter structure for DPCH/PDSCH and P-CCPCH. + +**Figure 6: Example for TSTD Transmitter structure for DPCH/PDSCH and P-CCPCH.** + +![Figure 7: Example for the antenna switching pattern for TSTD transmission of DPCH/PDSCH and P-CCPCH.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +This timing diagram shows the antenna switching pattern. Two antennas, ANT 1 and ANT 2, alternate transmission over consecutive 5ms sub-frames. In the first sub-frame, ANT 1 is active, transmitting a burst followed by a 12.5 micro sec gap. In the second sub-frame, ANT 2 becomes active, starting its transmission after the 12.5 micro sec gap from the previous sub-frame's end. This alternating pattern continues for subsequent sub-frames. + +Figure 7: Example for the antenna switching pattern for TSTD transmission of DPCH/PDSCH and P-CCPCH. + +**Figure 7: Example for the antenna switching pattern for TSTD transmission of DPCH/PDSCH and P-CCPCH: all physical channels are transmitted with TSTD and are using the same antenna in the sub-frame.** + +### 5.5.1.2 Closed loop Tx diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH + +The transmitter structure to support transmit diversity for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH transmission is shown in figure 8. Channel coding, interleaving and spreading are done as in non-diversity mode. The spread complex valued signal is fed to both TX antenna branches, and weighted with antenna specific weight factors $w_1$ and $w_2$ . The weight factors are complex valued signals (i.e., $w_i = a_i + jb_i$ ), in general. These weight factors are calculated on a per slot and per user basis. + +The weight factors are determined by the UTRAN. + +![Figure 8: Downlink transmitter structure to support Transmit Diversity for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point) in 1.28 Mcps TDD. The diagram shows a 'Midamble' input and a 'Data' path (ENC -> INT -> SPR+SCR) entering a 'MUX'. The MUX output is split into two parallel processing branches. Each branch consists of a multiplier (receiving a weight w1 or w2), an FIR filter, and an RF block, leading to antennas ANT1 and ANT2 respectively. A feedback loop from the antennas through an 'Uplink channel estimate' block provides the weights w1 and w2 to the multipliers.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +Figure 8: Downlink transmitter structure to support Transmit Diversity for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point) in 1.28 Mcps TDD. The diagram shows a 'Midamble' input and a 'Data' path (ENC -> INT -> SPR+SCR) entering a 'MUX'. The MUX output is split into two parallel processing branches. Each branch consists of a multiplier (receiving a weight w1 or w2), an FIR filter, and an RF block, leading to antennas ANT1 and ANT2 respectively. A feedback loop from the antennas through an 'Uplink channel estimate' block provides the weights w1 and w2 to the multipliers. + +**Figure 8: Downlink transmitter structure to support Transmit Diversity for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point) in 1.28 Mcps TDD** + +## 5.5.2 Transmit diversity for DwPCH + +The transmitter structure to support transmit diversity for DwPCH transmission is shown in figure 9. DwPCH is transmitted from antenna 1 and antenna 2 alternatively. + +![Figure 9: Downlink transmitter structure to support Transmit Diversity for DwPCH transmission (UTRAN Access Point) in 1.28 Mcps TDD. The diagram shows a 'DwPCH' input connected to a switch. The switch is controlled by a 'Switching Control' signal and alternates between two parallel processing branches. Each branch consists of an FIR filter and an RF block, leading to antennas Ant 1 and Ant 2 respectively.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +Figure 9: Downlink transmitter structure to support Transmit Diversity for DwPCH transmission (UTRAN Access Point) in 1.28 Mcps TDD. The diagram shows a 'DwPCH' input connected to a switch. The switch is controlled by a 'Switching Control' signal and alternates between two parallel processing branches. Each branch consists of an FIR filter and an RF block, leading to antennas Ant 1 and Ant 2 respectively. + +**Figure 9: Downlink transmitter structure to support Transmit Diversity for DwPCH transmission (UTRAN Access Point) in 1.28 Mcps TDD** + +## 5.5.3 Transmit diversity for P-CCPCH + +TSTD or Space Code Transmit Diversity (SCTD) can be employed as transmit diversity scheme for the Primary Common Control Physical Channel (P-CCPCH) + +### 5.5.3.1 TSTD transmission scheme for P-CCPCH + +A block diagram of an example of a TSTD transmitter is shown in figure 6. Channel coding, rate matching, interleaving, bit-to-symbol mapping, spreading, and scrambling are performed as in the non-diversity mode. Then the data is time multiplexed with the midamble sequence. Then, after pulse shaping and modulation and amplification, P-CCPCH is transmitted from antenna 1 and antenna 2 alternately every sub-frame. If there is a DPCH that uses TSTD, TSTD is also applied to P-CCPCH. An example of the antenna-switching pattern is shown in figure 7. If TSTD is applied to P-CCPCH, it shall also be applied to other beacon channels. + +## 5.5.4 SCTD transmission scheme for beacon channels + +The use of SCTD will be indicated by higher layers. If SCTD is active within a cell, SCTD shall be applied to any beacon channel. When beacon channel is used on dedicated MBSFN frequency, SCTD shall not be applied. + +The SCTD open loop downlink transmit diversity scheme for beacon channels is shown in figure 10, exemplary for the P-CCPCH. Channel coding, rate matching, interleaving and bit-to-symbol mapping are performed as in the non-diversity mode. In TxDiversity mode the beacon channel that is allocated to code $c_{16}^{(k=1)}$ is spread with the channelisation codes $c_{16}^{(k=1)}$ and $c_{16}^{(k=3)}$ and scrambled with the cell specific scrambling code. The beacon channel that is allocated to code $c_{16}^{(k=2)}$ is spread with the channelisation codes $c_{16}^{(k=2)}$ and $c_{16}^{(k=4)}$ and scrambled with the cell specific scrambling code. The spread sequences on code $c_{16}^{(k=3)}$ and code $c_{16}^{(k=4)}$ are then transmitted on the diversity antenna. The power applied to each antenna shall be equal. + +The use of SCTD will be indicated by higher layers. + +![Block diagram of the transmitter (SCTD) in 1.28 Mcps TDD, exemplary for the P-CCPCH.](1ce027dfd26183da52137cf990213724_img.jpg) + +The diagram illustrates the SCTD transmitter structure for P-CCPCH. It features two main signal paths for P-CCPCH1 and P-CCPCH2. Each signal is split and processed through multipliers (X) where they are combined with spreading codes \$s^{(1)}, s^{(2)}, s^{(3)},\$ and \$s^{(4)}\$. These processed signals are then fed into Multiplexer (MUX) blocks along with midambles \$m^{(1)}\$ and \$m^{(2)}\$. Specifically, for Tx Antenna 1, P-CCPCH1 is combined with \$s^{(1)}\$ and \$m^{(1)}\$, and P-CCPCH2 is combined with \$s^{(2)}\$ and \$m^{(1)}\$; their outputs are summed (+). For Tx Antenna 2, P-CCPCH1 is combined with \$s^{(3)}\$ and \$m^{(2)}\$, and P-CCPCH2 is combined with \$s^{(4)}\$ and \$m^{(2)}\$; their outputs are also summed (+). A legend at the bottom clarifies: "\* Spreading by \$s^{(k)}\$ means channelisation by \$c^{(k)}\$ and cell specific scrambling". + +Block diagram of the transmitter (SCTD) in 1.28 Mcps TDD, exemplary for the P-CCPCH. + +Figure 10: Block diagram of the transmitter (SCTD) in 1.28 Mcps TDD, exemplary for the P-CCPCH + +## 5.6 Random access procedure + +The physical random access procedure described below is invoked whenever a higher layer requests transmission of a message on the RACH. The physical random access procedure is controlled by primitives from RRC and MAC. + +### 5.6.1 Definitions + +FPACHi : The $i^{th}$ FPACH number parameter i indicates the position of the FPACH, the first position is corresponding to the first instance defined in IE "PRACH system information list" (see [15]). + +$L_i$ : Length of RACH transport blocks associated to FPACHi in sub-frames + +$N_{RACH_i}$ : The number of PRACHs associated to the $i^{th}$ FPACH + +$n_{RACH_i}$ : The number of a PRACH associated to the $i^{th}$ FPACH ranging from 0 to $N_{RACH_i}-1$ + +M : Maximum number transmissions in the UpPCH + +WT : Maximum number of sub-frames to wait for the network acknowledgement to a sent signature + +SFN' : The sub-frame number counting the sub-frames. At the beginning of the frame with the system frame number SFN=0 the sub-frame number is set to zero. + +### 5.6.1A UpPCH sub-channel + +In order to separate different ASCs, UpPCH has N sub-channels associated with it (numbered from 0 to N-1). N may be assigned the value 1,2,4, or 8 by higher layer signaling. + +- Sub-channel i for UpPCH is defined as the UpPTS timeslot in the sub\_frame where $SFN' \bmod N = i$ . + +Where SFN': the sub-frame number counting the sub-frames. At the beginning of the frame with the system frame number SFN=0 the sub-frame number is set to zero. + +The following figure illustrates the eight possible sub channels for the case, N=8. + +![Figure 10A : Example of UpPCH subchannels. The diagram shows four rows of sub-channels. Each row represents two sub-frames, each containing 7 slots (TS0 to TS6). The first row shows sub-channels 0 and 1, corresponding to SFN' mod 8 = 0 and SFN' mod 8 = 1. The second row shows sub-channels 2 and 3, corresponding to SFN' mod 8 = 2 and SFN' mod 8 = 3. The third row shows sub-channels 4 and 5, corresponding to SFN' mod 8 = 4 and SFN' mod 8 = 5. The fourth row shows sub-channels 6 and 7, corresponding to SFN' mod 8 = 6 and SFN' mod 8 = 7. In each sub-frame, the UpPTS (Uplink Pilot Time Slot) is indicated by a red bar in slot TS0. The sub-channel number is indicated below the slots.](215165a27ad7d72bd39fdf55a3cb7486_img.jpg) + +Figure 10A : Example of UpPCH subchannels. The diagram shows four rows of sub-channels. Each row represents two sub-frames, each containing 7 slots (TS0 to TS6). The first row shows sub-channels 0 and 1, corresponding to SFN' mod 8 = 0 and SFN' mod 8 = 1. The second row shows sub-channels 2 and 3, corresponding to SFN' mod 8 = 2 and SFN' mod 8 = 3. The third row shows sub-channels 4 and 5, corresponding to SFN' mod 8 = 4 and SFN' mod 8 = 5. The fourth row shows sub-channels 6 and 7, corresponding to SFN' mod 8 = 6 and SFN' mod 8 = 7. In each sub-frame, the UpPTS (Uplink Pilot Time Slot) is indicated by a red bar in slot TS0. The sub-channel number is indicated below the slots. + +Figure 10A : Example of UpPCH subchannels + +### 5.6.2 Preparation of random access + +When the UE is in idle mode, it will keep the downlink synchronisation and read the system information. From the used SYNC-DL code in DwPCH, the UE will get the code set of 8 SYNC-UL codes (signatures) assigned to UpPCH for random access. + +The description (codes, spreading factor, midambles, time slots) of the P-RACH, FPACH, S-CCPCH (carrying the FACH transport channel) channel; mapping relation of RACH and FPACH; ASC (available SYNC-UL sequences and available sub-channels) sets for each RACH are broadcast on the BCH. + +Thus, when sending a SYNC-UL sequence, the UE knows which FPACH resource, P-RACH resources and S-CCPCH resources will be used for the access. + +The physical random access procedure described in this sub-clause is initiated upon request from the MAC sub-layer (see [18] and [19]). + +Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information by a CPHY-TrCH-Config-REQ from the RRC layer: + +- The uplink access position by higher layers. +- The association between which signatures and which FPACHs; which FPACHs and which PRACHs; including the parameter values for each listed physical channel. +- The length $L_i$ of a RACH message associated to $FPACH_i$ can be configured to be either 1 or 2 or 4 sub-frames corresponding to a length in time of either 5 ms or 10 ms or 20 ms. + +NOTE 1: $N_{RACH_i}$ PRACHs can be associated with $FPACH_i$ . The maximum allowed + +$N_{RACH_i}$ is $L_i$ . + +- The available UpPCH sub-channels for each Access Service Class (ASC); +- The set of Transport Format parameters for the PRACH message; +- The "M" maximum number transmissions in the UpPCH; +- The "WT" maximum number of sub-frames to wait for the network acknowledgement to a sent signature; (1..4) the maximum value supported by Layer 1 is 4 sub-frames. +- The initial signature power "Signature\_Initial\_Power"; +- The power-ramping factor Power Ramp Step [Integer]; + +The above parameters may be updated from higher layers before each physical random access procedure is initiated. + +At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the higher layers (MAC): + +- The Transport Format to be used for the specific PRACH message; +- The ASC for the specific Random Access procedure; +- The data to be transmitted (Transport Block Set). +- The type of random access + +### 5.6.3 Random access procedure + +The physical random-access procedure shall be performed as follows: + +UE side: + +- 1 Set the Signature Re-Transmission Counter to M. +- 2 Set the Signature transmission power to $Signature\_Initial\_Power$ . +- 3 Based on the type of random access and the transport format indicated by MAC layer, an E-RUCCH or unique RACH used for the radio access is chosen, and then randomly select one UpPCH sub-channel and one signature respectively from the available ones for the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability. +- 4 Transmit the signature at UpPCH or other uplink access position indicated by higher layers using the selected UpPCH sub-channel at the signature transmission power. In the case that the Commanded Signature transmission Power exceeds the maximum allowed value, set the Signature transmission Power to the maximum allowed power. +- 5 After sending a signature, listen to the relevant FPACH for the next WT sub-frames to get the network acknowledgement. The UE will read the $FPACH_i$ associated to the transmitted UpPCH only in the sub-frames fulfilling the following relation: + +$(SFN' \bmod L_i) = n_{RACHi}$ ; $n_{RACHi} = 0, \dots, N_{RACHi} - 1$ , Here, FPACH to which UE should listen is decided according to the following formula: + +$$FPACH_i = N \bmod M,$$ + +Where, N denotes the signature number (0..7) and M denotes the maximum number of FPACHs that defined in the cell. + +- 6 In case no valid answer is detected in the due time: Increase the Signature transmission power by $\Delta P_0 = \text{Power Ramp Step [dB]}$ , decrease the Signature Re-transmission counter by one and if it is still greater than 0, then repeat from step 3; else report a random access failure to the MAC sub-layer. +- 7 In case a valid answer is detected in the due time + - a) set the timing and power level values according to the indication received by the network in the $FPACH_i$ + - b) send at the sub-frame coming 2 sub-frames after the one carrying the signature acknowledgement, the RACH message on the relevant PRACH. In case $L_i$ is bigger than one and the sub-frame number of the acknowledgement is odd the UE will wait one more sub-frame. The relevant PRACH is the $n_{RACHi}^{\text{th}}$ PRACH associated to the $FPACH_i$ if the following equation is fulfilled: + +$$(SFN' \bmod L_i) = n_{RACHi};$$ + +Here $SFN'$ is the sub-frame number of the arrival of the acknowledgement. + +Both on the UpPCH and on the PRACH, the transmit power level shall never exceed the indicated value signalled by the network. + +Network side: + +- The node B will transmit the $FPACH_i$ associated with the received UpPCH only in the sub-frames fulfilling the following relation: + +$$(SFN' \bmod L) = n_{RACHi}; n_{RACHi} = 0, \dots, N_{RACHi} - 1,$$ + +Here, FPACH number i is selected according to the following formula based on acknowledged signature: + +$$FPACH_i = N \bmod M,$$ + +Where, N denotes the signature number (0..7) and M denotes the maximum number of FPACH that defined in the cell. + +- The Node B will not acknowledge UpPCHs transmitted more than WT sub-frames ago + +At the reception of a valid signature: + +- Measure the timing deviation with respect to the reference time $T_{\text{ref}}$ of the received first path in time from the UpPCH and acknowledge the detected signature sending the FPACH burst on the relevant FPACH. + +For examples on the random access procedure refer to Annex CB. + +### 5.6.3.1 The use and generation of the information fields transmitted in the FPACH + +The Fast Physical Access CHannel (FPACH) is used by the Node B to carry, in a single burst, the acknowledgement of a detected signature with timing and power level adjustment indication to a user equipment. + +The length and coding of the information fields is explained in TS25.221 sub-clause 5A.3.3.1 . + +#### 5.6.3.1.1 Signature reference number + +The Signature Reference Number field contains the number of the acknowledged signature. The user equipment shall use this information to verify whether it is the recipient of the FPACH message. + +#### 5.6.3.1.2 Relative sub-frame number + +The Relative Sub-Frame Number field indicates the current sub-frame number with respect to the sub-frame at which the acknowledged signature has been detected. + +The user equipment shall use this information to verify whether it is the recipient of the FPACH message. + +#### 5.6.3.1.3 Received starting position of the UpPCH (UpPCHPOS) + +The *received starting position of the UpPCH (UpPCHPOS)* field indirectly indicates to the user equipment the timing adjustment it has to implement for the following transmission to the network. The node B computes the proper value for this parameter according to the following rules: $\text{UpPCH}_{\text{POS}} = \text{UpPCH}_{\text{Rxpath}} - \text{UpPCH}_{\text{TS}}$ + +where + +UpPCHRxpath: time of the reception in the Node B of the SYNC-UL to be used in the uplink synchronization process + +UpPCHTS: time instance 128 chips prior to the start of the UpPCH according to the Node B internal timing + +This information shall be used by the UE to adjust its timing when accessing the network, as described in section [5.2 'Uplink Synchronisation'] . + +#### 5.6.3.1.4 Transmit power level command for the RACH message + +This field indicates to the user equipment the power level to use for the RACH message transmission on the FPACH associated P-RACH. + +The network may set this value based on the measured interference level (I) (in dBm) on the specific PRACH and on the desired signal to interference ratio (SIR) (in dB) on this channel as follows: + +*Transmit Power Level Command for the PRACH(PRXPRACH,des)* + +PRXPRACH,des is the desired receive power level on the PRACH. + +The UE shall add to this value the estimated path-loss to compute the power level to transmit for the PRACH. + +### 5.6.3A E-RUCCH procedure + +Requests for the transmission of an E-RUCCH are controlled by higher layers [18]. + +The available eight SYNC\_UL signatures on the primary carrier in a cell is divided into two subsets, one for the access of RACH information and the other for the access of E-RUCCH information. The available eight SYNC-UL signature on the secondary frequencies in cell are all for the access of E-RUCCH information. + +When a Node B detects a SYNC\_UL signature and acknowledges it on the related FPACH, it should do some recordings, including the FPACH channel number, the sub-frame on which the acknowledgement is sent and the SYNC\_UL signature number. When a PRACH or E-RUCCH comes from a UE, the Node B should derive the related FPACH and the sub-frame on which the acknowledgement was sent for the UE and find the right record. The signature number in the record can help the Node B know the access type. + +Random access procedure for enhanced uplink is basically same as random access procedure in subclause 5.6.3, only adding some new definitions. + +LiE is the Length of E-RUCCH information transport blocks associated to FPACHi in sub-frames. + +NRACHi is the number of PRACHs associated to the ith FPACH. + +NE-RUCCHi is the number of E-RUCCHs associated to the ith FPACH and NE-RUCCHi equals to . + +When SF of PRACH code equals to 16, LiE will be 2, otherwise LiE will be 1. + +When SF of PRACH code equals to 4, SF of E-RUCCH will be 8, otherwise E-RUCCHs has the same SF with PRACH. + +When nE-RUCCHi equals to nRACHi, E-RUCCH will share the same code resource with PRACH. And when SF of PRACH code equals to 4, the code resource assigned to PRACH including two codes (code i and code i+1) of SF 8, E-RUCCH can use the ith code of SF 8. + +If FPACHi sent an acknowledgement for E-RUCCH information, the sub-frames on which an acknowledgement is sent on FPACHi is fulfilling the following relation: + +$$(SFN' \bmod L_{iE}) = n_{E-RUCCHi}; n_{E-RUCCHi} = 0, \dots, N_{E-RUCCHi} - 1,$$ + +Where, SFN' is the sub-frame number of the acknowledgement on FPACH + +Accordingly, the code resource assigned to PRACH may be used by PRACH or E-RUCCH, we should make two prescriptions avoiding the collision between PRACH and E-RUCCH. + +When Node B sent a FPACHi for in sub frame K, Node B could not send a FPACHi for before sub frame $K + L_i$ ; + +When Node B sent a FPACHi for in sub frame K, Node B could not send a FPACHi for before sub frame $K + L_{iE}$ . + +The interval between the acknowledgement on FPACH and transmission of E-RUCCH is fixed for a UE. The UE will send at the sub-frame coming 2 sub-frames after the one carrying the signature acknowledgement. In case $L_{iE}$ is bigger than one and the sub-frame number of the acknowledgement is odd the UE will wait one more sub-frame. + +The transmission power and the transmission timing are set according to subclause 5.1.1.7 and 5.2.7 respectively. + +## 5.6.4 Random access collision + +When a collision is very likely or in bad propagation environment, the Node B does not transmit the FPACH or cannot receive the SYNC-UL. In this case, the UE will not get any response from the Node B. Thus the UE will have to adjust its Tx time and Tx power level based on a new measurement and send a SYNC-UL again after a random delay. + +Note that at each (re-)transmission, the SYNC-UL sequence and the UpPCH sub-channel will be randomly selected again by the UE. + +Note: Due to the two-step approach a collision most likely happens on the UpPCH. The resources allocated to PRACH and E-RUCCH are virtually collision free. This two-step approach will guarantee that the RACH resources can be handled with conventional traffic on the same UL time slots. + +## 5.7 Node B synchronisation procedure over the air + +An option exists to use the regular DwPCH transmissions to achieve and maintain Node B synchronisation [20]. This optional procedure is based on measurements of DwPCHs from neighbouring cells according to an RNC schedule. The timing offset measurements are reported back to the RNC for processing. The RNC generates cell timing updates that are transmitted to the Node Bs and cells for implementation (common with the 3.84 Mcps TDD option). Alternatively the RNC may indicate that the NodeB shall autonomously adjust the cell timings. Two distinct phases can be distinguished for Node B synchronisation over the air, with a potential additional sub-phase involving late entrant cells. + +### 5.7.1 Initial synchronisation + +Common with 3.84 Mcps TDD, see [4.9.2 Initial Synchronisation], however, the regular DwPCHs are used as cell sync bursts. + +### 5.7.2 Steady-state phase + +Common with 3.84 Mcps TDD, see [4.9.3 Steady-State Phase], however, the regular DwPCHs are used as cell sync bursts. If the NodeB adjusts the cell timings autonomously, it shall take into account the propagation delay, signaled by the RNC. + +### 5.7.3 Late entrant cells + +A procedure that may be used for introducing new cells into an already synchronised RNS involves the continuous measurement of the DwPCHs of the neighbouring cells by the late entrant cell. The RNC may use this information to adjust the late entrant cell sufficiently to allow the cell to enter steady state phase. + +## 5.8 Idle periods for IPDL location method + +### 5.8.1 General + +To support time difference measurements for location services, idle periods can be created in the downlink (hence the name IPDL) during which time transmission of the DwPCH from a Node B is temporarily ceased. During these idle periods the visibility of neighbour cells from the UE is improved. + +The idle periods are arranged in a determined pattern according to higher layer parameters. An idle period has a duration of one DwPTS. + +In general there are two modes for these idle periods: + +- Continuous mode, and +- Burst mode + +In continuous mode, the idle periods are active all the time. In burst mode the idle periods are arranged in bursts where each burst contains enough idle periods to allow a UE to make sufficient measurements for its location to be calculated. The bursts are separated by a period where no idle periods occur. The time difference measurements can be performed on any channel. + +### 5.8.2 Parameters of IPDL + +The following parameters are signalled to the UE via higher layers: + +- IP\_Status:** This is a logic value that indicates if the idle periods are arranged in continuous or burst mode. +- IP\_Spacing:** The number of 10 ms radio frames between the start of a radio frame that contains an idle period and the next radio frame that contains the next idle period. +- IP\_Start:** The number of the first frame with idle periods. In case of continuous mode IP\_Start is the SFN of the first frame with idle periods and in case of burst mode IP\_Start defines the number of frames after Burst\_Start with the first frame with idle periods. +- IP\_Sub:** Indicates whether the idle period is to occur in the odd, the even or both the odd and even 5 ms sub-frames of the 10 ms idle frame. + +Additionally in the case of burst mode operation the following parameters are also communicated to the UE. + +- Burst\_Start:** Specifies the start of the first burst of idle periods. $256 \times \text{Burst\_Start}$ is the SFN where the first burst of idle periods starts. +- Burst\_Length:** The number of idle periods in a burst of idle periods. +- Burst\_Freq:** Specifies the time between the start of a burst and the start of the next burst. $256 \times \text{Burst\_Freq}$ is the number of radio frames between the start of a burst and the start of the next burst. + +### 5.8.3 Calculation of idle period position + +In burst mode, burst #0 starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start}$ . Burst #n starts in the radio frame with $\text{SFN} = 256 \times \text{Burst\_Start} + n \times 256 \times \text{Burst\_Freq}$ ( $n = 0, 1, 2, \dots$ ). The sequence of bursts according to this formula continues up to and including the radio frame with $\text{SFN} = 4095$ . At the start of the radio frame with $\text{SFN} = 0$ , the burst sequence is terminated (no idle periods are generated) and at $\text{SFN} = 256 \times \text{Burst\_Start}$ the burst sequence is restarted with burst #0 followed by burst #1 etc., as described above. + +Continuous mode is equivalent to burst mode, with only one burst spanning the whole SFN cycle of 4096 radio frames, this burst starts in the radio frame with $\text{SFN} = 0$ . In case of continuous mode the parameter IP\_Start defines the first frame with idle periods. + +The DwPCH, that has to be idle, is defined by two values: IP\_Frame(x) and IP\_Sub. IP\_Frame(x) defines the $x^{\text{th}}$ frame within a burst in which subframe with the number IP\_Sub has to be switched off. + +The actual frame with idle periods within a burst is calculated as follows: + +$$IP\_Frame(x) = IP\_Start + (x-1) \times IP\_Spacing \text{ with } x = 1, 2, 3, \dots$$ + +Figure 11 below illustrates the idle periods for the burst mode which shows the case that both subframes within each frame have DwPTS as an idle period. + +![Figure 11: Idle periods of burst mode for 1.28Mcps TDD. The diagram shows a sequence of frames and subframes. At the top, a frame is divided into slots, with Slot 0 and Slot 6 highlighted. Below this, Subframe#1 and Subframe#2 are shown, each containing a DwPTS (Dedicated Physical Control Channel) period. The 'IP_Start' frames are indicated by a double-headed arrow. The 'IP_Spacing' frames are also indicated by a double-headed arrow. The bottom part of the diagram shows a sequence of frames starting from SFN=0. The first part is labeled '256×Burst_Start' frames, and the second part is labeled '256×Burst_Freq' frames. Two bursts of idle periods are shown: burst#0 and burst#1.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +Figure 11: Idle periods of burst mode for 1.28Mcps TDD. The diagram shows a sequence of frames and subframes. At the top, a frame is divided into slots, with Slot 0 and Slot 6 highlighted. Below this, Subframe#1 and Subframe#2 are shown, each containing a DwPTS (Dedicated Physical Control Channel) period. The 'IP\_Start' frames are indicated by a double-headed arrow. The 'IP\_Spacing' frames are also indicated by a double-headed arrow. The bottom part of the diagram shows a sequence of frames starting from SFN=0. The first part is labeled '256×Burst\_Start' frames, and the second part is labeled '256×Burst\_Freq' frames. Two bursts of idle periods are shown: burst#0 and burst#1. + +Figure 11: Idle periods of burst mode for 1.28Mcps TDD + +## 5.9 HS-DSCH procedure in CELL\_DCH state + +### 5.9.1 Link adaptation procedure + +For HS-DSCH, the modulation scheme and effective code rate shall be selected by higher layers located within the Node B. This shall be achieved by appropriate selection of an HS-DSCH transport block size, modulation format and resources by higher layers. If the UE is configured in MIMO mode, higher layers may select the number of data streams, i.e. single or dual stream HS-DSCH transmission, and the transport block size, modulation format and resources for each stream. The Node B shall decide the number of data streams based on the uplink channel estimation and CQI reports from the UE. If UE supports multi-carrier HS-DSCH reception, higher layers may select multiple carriers to transfer data. Carriers selection may be based on CQI reports from the UE. If UE supports multi-carrier HS-DSCH transmission, UE shall report the CQI information of every carrier via HS-SICH. + +The overall HS-DSCH link adaptation procedure consists of *two parts*: + +*Node B procedure:* + +- 1) The NodeB transmits HS-SCCH carrying a UE identity identifying the UE to which HS-DSCH TTI is to be granted. In case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same HS-SCCH shall be used for associated signalling. If the UE is configured in MIMO mode, the Node B shall determine appropriate HS-SCCH type for single or dual stream HS-DSCH transmission. If UE supports multi-carrier HS-DSCH reception, above HS-SCCH detection procedure applied on each independent carriers. +- 2) The NodeB transmits HS-DSCH to the UE using the grant indicated in the HS-SCCH. If UE supports multi-carrier HS-DSCH reception, the mapping relation between HS-SCCH and its associated HS-DSCH is set by higher layers. +- 3) Upon receiving the HS-SICH from the respective UE, the status report (ACK/NACK and CQI) shall be passed to higher layers. If UE supports multi-carrier HS-DSCH reception, the mapping relation between HS-SICH and its associated HS-DSCH is set by higher layers. + +*UE procedure:* + +- 1) When indicated by higher layers, the UE shall start monitoring all HS-SCCHs that are in its HS-SCCH set as signalled to it by higher layers. The information carried on the HS-SCCH is described in [8]. If UE supports multi-carrier HS-DSCH reception, the monitoring HS-SCCH set is signalled by higher layers. + +- 2) In the case that a HS-SCCH is identified to be correct by its CRC, the UE shall read the HS-PDSCHs indicated by the HS-SCCH. If the UE is configured in MIMO mode, UE may acquire HS-PDSCH resource allocation information of each stream according to the associated HS-SCCH. If UE supports multi-carrier HS-DSCH reception, UE may acquire HS-PDSCH resource allocation information of each carrier according to the associated HS-SCCHs, the mapping relation between every HS-SCCH and its associated HS-PDSCH is signalled by higher layers. In the case that a HS-SCCH is identified to be incorrect, the UE shall discard the data on the HS-SCCH and return to monitoring. +- 3) After reading the HS-PDSCHs, the UE shall generate an ACK/NACK message and transmit this to the NodeB in the associated HS-SICH, along with the most recently derived CQI. If the UE is configured in MIMO mode, the CQI and ACK/NACK of each stream are transferred via the associated HS-SICH. If UE supports multi-carrier HS-DSCH reception, the CQI and ACK/NACK of every carrier are transferred via individual HS-SICH. + +The mapping of HS-PDSCH channelisation code set and timeslot information carried by the HS-SCCH for a given HS-DSCH TTI is described in [9]. + +For a given allocation of HS-PDSCH resources to a UE for a specific HS-DSCH TTI, the following shall apply: + +- If timeslot information on HS-SCCH indicates two or more timeslots, none of these timeslots shall comprise a beacon channel. +- If timeslot information on HS-SCCH indicates a single timeslot and this timeslot comprises a beacon channel then: + - The Node-B shall not indicate SF=1 for any HS-PDSCH resource. + - The set of HS-PDSCH resources allocated by the Node-B to a UE shall exclusively comprise either beacon function or non-beacon function physical channels. The Node B shall therefore not allocate both beacon function and non-beacon function physical channels within the beacon timeslot to the UE. If the HS-DSCH for a specific HS-DSCH TTI is mapped to the beacon channel, this shall be signalled using $k_{start} = 1$ and $k_{stop} = 1$ . For a definition of the first and last allocated channelisation code indices $k_{start}$ and $k_{stop}$ on HS-SCCH refer to [9]. + - When SCTD antenna diversity is applied to the beacon channel, then the presence of channelisation code within the channelisation code set information on HS-SCCH shall implicitly indicate the presence of channelisation code . + +## 5.9.2 HS-DSCH channel quality indication procedure + +For the HS-SICH associated to the HS-SCCH command for allocation or release of the semi-persistent HS-PDSCH resources and HS-SCCH command for activation or deactivation of DRX and the HS-SICH associated to HS-SCCH type1 or HS-SCCH type 4 or HS-SCCH type 8 with transport block size information set to all zeros, UE shall feedback ACK and CQI on HS-SICH with RTBS equals to zero. + +The channel quality indicator (CQI) provides the Node B with an estimate of the code rate that would have maximized the single-transmission throughput of the previous HS-DSCH transmission if decoded in isolation. The CQI report requires to be referenced to a given set of HS-PDSCH resources by the Node B, but note that the UE is not restricted to making measurements only on these reference resources when deriving a given CQI. The reference resources for a CQI report shall be a set of HS-PDSCH resources that were received by the UE in a single TTI, and contain a complete transport block. These resources will be known to the Node B from the relative timings of the HS-SICH carrying the CQI and previous HS-DSCH transmissions to the UE. + +The CQI consists of two fields; a Recommended Transport Block Size (RTBS) and a Recommended Modulation Format (RMF). The UE shall use the same mapping table for these fields as is being used for the time slot information and modulation scheme information fields respectively of the HS-SCCH [18]. If the UE is configured in MIMO mode, the HS-SICH shall consists of the CQI reports of each stream, i.e. the RTBS and RMF of each stream. + +The reporting procedure is as follows: + +1. The UE receives a message on an HS-SCCH telling it which resources have been allocated to it for the next associated HS-DSCH transmission. +2. The UE reads the associated HS-DSCH transmission, and makes the necessary measurements to derive a CQI that it estimates would have given it the highest single-transmission throughput for the allocated resources whilst + +achieving a BLER of no more than 10 %. If the UE is configured in MIMO mode, the CQI would have given the highest single-transmission throughput for each stream respectively in the allocated resources whilst achieving BLER of each stream of no more than 10%. + +BLER, in this context, is defined as the probability that a transport block transmitted using the RTBS and RMF is received in error if decoded in isolation. For the purposes of this calculation, it shall be assumed that the transport block that would be transmitted with these parameters would use redundancy version parameters $s = 1$ and $r = 0$ . Note that, by this definition, a UE shall never report a CQI that corresponds to a code rate greater than unity. + +Using this definition of BLER, single-transmission throughput shall be defined as follows : + +$$\text{single-transmission throughput} = (1 - \text{BLER}) \times \text{RTBS}$$ + +If the UE is configured in MIMO mode, the single-transmission throughput shall be defined as the sum of each stream throughput. + +3. The CQI report derived from a given HS-DSCH transmission shall be reported to the Node B in the next HS-SICH available to the UE following that HS-DSCH transmission, unless that HS-SICH immediately follows the last allocated HS-DSCH timeslot, in which case the subsequent available HS-SICH shall be used by the UE. This HS-SICH may not necessarily be the same HS-SICH that carries the ACK/NACK information for that HS-DSCH transmission. The UE shall always transmit the most recently derived CQI in any given HS-SICH, which may mean that some CQI reports are discarded without being transmitted to the Node B. + +### 5.9.3 HS-SCCH monitoring procedure + +If HS\_SCCH\_DRX\_Active is FALSE, UE shall monitor a set of HS-SCCHs as follows. + +For 1.28Mcps TDD, in a multi-frequency HS-DSCH cell, a UE divides its HS-SCCH set into one or more HS-SCCH subsets; in each HS-SCCH subset all HS-SCCHs are associated with the same frequency's HS-PDSCH. When indicated by higher layers, the UE shall start monitoring all HS-SCCHs in all HS-SCCH subsets to acquire the configuration information of HS-PDSCHs. In the case that one HS-SCCH is detected carrying its UE identity, the UE shall skip monitoring the remaining HS-SCCHs in this HS-SCCH subset, and restrict its monitoring only to previously detected HS-SCCH in the following TTIs. The UE shall set all HS-SCCHs carrying its UE identity in all HS-SCCH subsets into an active set, and set all HS-SCCH subsets in which no HS-SCCH carries its UE identity into a remaining set. + +In the case that the multi-carrier number (as described in [15]) is not configured by high layers, a UE shall always monitor all HS-SCCH subsets. Otherwise, the UE may skip monitoring remaining HS-SCCH subsets when the number of HS-SCCHs carrying its UE identity, i.e. the number of HS-SCCHs in the active set, is equal to the configured value. + +During the following TTIs, the UE shall update and maintain the active set and the remaining set. If one or more HS-SCCHs in the active set do not carry its UE identity, the UE shall remove them from the active set and set their corresponding HS-SCCH subsets into remaining set. Meanwhile, if one or more HS-SCCHs in remaining sets are detected carrying its UE identity, the UE shall set these founded HS-SCCHs into the active set and remove their corresponding HS-SCCH subsets from the remaining set. + +If HS\_SCCH\_DRX\_Active is TRUE, UE shall monitor a set of HS-SCCHs in the subframes according to rules defined in the subclause 5.13. + +## 5.9A HS-DSCH procedure in CELL\_FACH state + +### 5.9A.1 Link adaptation procedure + +In HS-DSCH reception in CELL\_FACH state, the measurement result on RACH can be used for initial link adaptation. Only when UE is allocated a dedicated UE identity, the ACK/NACK feedback is provided and a measurement report is associated with each HS-DSCH link adaptation procedure. When downlink transmission is recommenced following a transmission pause, Node B shall order UE to perform the uplink synchronization procedure cf [subclause 5.3.3.2 Establishment of uplink synchronization] in case it detects the UE is out of synchronization. If Node B receives E-RUCCH from the UE, the Node B can then resume the HS-DSCH transmission for the UE, and the link adaptation procedure is the same as that in CELL\_DCH state, cf.5.9.1. + +The Node B shall always use HS-SCCH type 1 for BCCH transmission. For the UEs in CELL\_FACH state which are configured in MU-MIMO mode, the UE shall detect the HS-SCCH type of the HS-SCCHs carry consistent control + +information via UE ID, i.e., the HS-SCCH shall be HS-SCCH type 1 if the UE ID is BCCH specific H-RNTI while the HS-SCCH shall be HS-SCCH type 4 if the UE ID is its dedicated H-RNTI. + +## 5.9A.2 HS-DSCH channel quality indication procedure + +If the UE is configured without dedicated UE identity, the UE shall not transmit an HS-SICH. If the UE is configured with a dedicated UE identity, but the HS-SCCH is an uplink synchronization establishment order, then its associated HS-SICH shall not be transmitted. Otherwise, the channel quality indication shall be transmitted on HS-SICH, and the HS-DSCH channel quality indication procedure is the same as that in CELL\_DCH state of 1.28Mcps TDD, cf. 5.9.2. + +## 5.9A.3 HS-SCCH monitoring procedure + +When HS\_DSCH\_DRX\_CELL\_FACH\_STATUS is FALSE (as described in [15]), UE shall monitor HS-SCCHs continuously as in CELL\_DCH state cf. 5.9.3. + +When HS\_DSCH\_DRX\_CELL\_FACH\_STATUS is TRUE (as described in [15]), UE shall monitor HS-SCCHs according to the following rules: + +- Once the UE receives HS-SCCH carrying its dedicated identity and feeds back on HS-SICH, the UE shall monitor HS-SCCHs continuously for a period of inactivity time (T321) configured by higher layer. +- Once the UE receives HS-SCCH order carrying synchronization establishment command and accomplishes the uplink synchronization establishment, the UE shall monitor HS-SCCHs continuously for a period of inactivity time (T321) configured by higher layer. +- Whenever the UE monitors E-AGCH continuously as described in 5.11.3A, the UE shall always monitor HS-SCCHs. +- The UE shall monitor HS-SCCHs for the RX burst length of the DRX Cycle and may choose not to monitor HS-SCCHs for the rest of the time of the DRX Cycle (as described in [15]). + +## 5.9B HS-DSCH procedure in CELL\_PCH or URA\_PCH state + +### 5.9B.1 Link adaptation procedure + +In HS-DSCH reception in CELL\_PCH and URA\_PCH state, after receiving a paging indication on PICH for its specific PI, the UE with a stored dedicated UE identity shall start monitoring HS-SCCH while the UE without a dedicated UE identity shall start monitoring the HS-PDSCH(s). The HS-PDSCH physical resource and associated signalling are broadcasted in the system information. + +In a multi-frequency cell, HS-DSCH reception in CELL\_PCH and URA\_PCH is only on primary frequency. + +*Node B procedure:* + +The timing relation of the PICH frame to the associated HS-SCCH subframe or the HS-DSCH is described in 7.2.7.3 and 7.2.7.4 of [8]. + +If the UE is configured with a dedicated UE identity, the Node B shall use the following procedures: + +- The Node B shall transmit the HS-SCCH order associated with the PICH frame using the dedicated UE identity. +- If the Node B has received E-RUCCH, the Node B considers that the UE has transitted to CELL\_FACH state. + +If the UE is configured without dedicated UE identity, the Node B shall use the following procedures: + +- The Node B shall not transmit an HS-SCCH. +- The Node B shall transmit an HS-DSCH transport block in the HS-DSCH subframe with parameters configured by RRC layer. +- The Node B shall retransmit the HS-DSCH transport block $(2^m-1)$ times in the next contiguous subframes without transmitting HS-SCCH. +- The Node B shall use QPSK modulation for each transmission of HS-PDSCH. + +- For the first transmission and retransmission, the redundancy and constellation version of the HS-DSCH transport block are 0, 3, 4, 7, 0, 3... + +*UE procedure:* + +If the UE has detected a paging indication intended for this UE, the UE shall perform the following actions: + +If the UE is configured with a dedicated UE identity, UE shall receive the corresponding HS-SCCH subframes: + +- if the UE detects that one of the monitored HS-SCCHs in a set of associated HS-SCCH subframes carries consistent control information (HS-SCCH order) intended for this UE, the UE shall initiate the uplink synchronization procedure on primary frequency and transit to CELL\_FACH state. +- if the UE detects that one of the monitored HS-SCCHs in a set of associated HS-SCCH subframes carries consistent control information (HS-SCCH type 1 carrying BCCH specific H-RNTI), the UE shall receive the corresponding HS-DSCH based on the association and timing between HS-SCCH and HS-DSCH. +- if the UE does not detect any HS-SCCH carries consistent control information intended for this UE in the M subframes, the UE shall resume the DRX operation. + +If the UE is configured without dedicated UE identity and there is no legacy PCH channel, UE shall receive the corresponding HS-DSCH TTIs and: + +- consider that paging message is retransmitted in $2*m$ subframes, the parameter $m$ is the number of frame that a paging sub-channel occupies. +- combine retransmissions to the same HARQ buffer. +- pass the data to higher layers if the CRC is correct after decoding the data. +- resume the DRX operation if the CRC fails after receiving $2*m$ subframes. + +## 5.9B.2 HS-DSCH channel quality indication procedure + +The UE in CELL\_PCH or URA\_PCH state does not report CQI via HS-SICH. + +## 5.9B.3 HS-SCCH monitoring procedure + +The UE with a stored dedicated UE identity shall monitor HS-SCCH in M sub-frames after receiving its specific paging indication on PICH (as described in [8]). + +The UE without a dedicated UE identity shall not monitor any HS-SCCH. + +## 5.10 Macro-diversity procedure + +The macro-diversity procedure is the same as that of 3.84 Mcps TDD, cf. 4.12 Macro-diversity procedure. + +## 5.11 E-DCH Procedure + +### 5.11.1 ACK/NACK detection + +The physical layer in the UE shall detect ACK or NACK contained within the E-HICH. Which E-HICH is associated with the corresponding E-DCH transmission is defined in [8]. + +### 5.11.2 Serving and neighbour cell pathloss metric derivation + +The UE shall be capable of measuring the P-CCPCH RSCP of the serving cell and of intra-frequency and inter-frequency neighbour cells in accordance with [11]. The P-CCPCH transmit power ( $P_{ref}$ ) of the serving cell and of each neighbour cell (with a primary or a secondary frequency being the same as UE's current working frequency) in the monitored neighbour cell list shall be signalled by higher layers to the UE in order that the UE may estimate the mean pathloss to the serving cell ( $L_{serv}$ ) and to each of the N neighbour cells in the monitored neighbour cell list ( $L_1, L_2, \dots, L_N$ ). The pathloss used in the following formulas is a linear value, but not a logarithmic (dB) value. + +Higher layers shall configure the UE to use SNPL reporting type 1 or SNPL reporting type 2. In accordance with the SNPL reporting type, the UE shall be capable of forming a metric corresponding to: + +{for SNPL reporting type 1} + +{for SNPL reporting type 2} + +The metric $\phi$ shall be converted into a logarithmic (dB) value $Q$ and shall be mapped to a Serving and Neighbour Cell Pathloss (SNPL) index according to table 2b. The SNPL index is supplied to and used by higher layers (see [18]). + +**Table 2b: SNPL mapping** + +| $Q = 10 \cdot \log_{10}(\phi)$ | SNPL index | +|--------------------------------|------------| +| $Q < -10$ | 0 | +| $-10 \leq Q < -8$ | 1 | +| $-8 \leq Q < -6$ | 2 | +| $-6 \leq Q < -5$ | 3 | +| $-5 \leq Q < -4$ | 4 | +| $-4 \leq Q < -3$ | 5 | +| $-3 \leq Q < -2$ | 6 | +| $-2 \leq Q < -1$ | 7 | +| $-1 \leq Q < 0$ | 8 | +| $0 \leq Q < 1$ | 9 | +| $1 \leq Q < 2$ | 10 | +| $2 \leq Q < 3$ | 11 | +| $3 \leq Q < 4$ | 12 | +| $4 \leq Q < 5$ | 13 | +| $5 \leq Q < 6$ | 14 | +| $6 \leq Q < 7$ | 15 | +| $7 \leq Q < 8$ | 16 | +| $8 \leq Q < 9$ | 17 | +| $9 \leq Q < 10$ | 18 | +| $10 \leq Q < 11$ | 19 | +| $11 \leq Q < 12$ | 20 | +| $12 \leq Q < 13$ | 21 | +| $13 \leq Q < 14$ | 22 | +| $14 \leq Q < 15$ | 23 | +| $15 \leq Q < 16$ | 24 | +| $16 \leq Q < 17$ | 25 | +| $17 \leq Q < 18$ | 26 | +| $18 \leq Q < 20$ | 27 | +| $20 \leq Q < 22$ | 28 | +| $22 \leq Q < 24$ | 29 | +| $24 \leq Q < 26$ | 30 | +| $26 \leq Q$ | 31 | + +If the higher layer signalling information regarding the required P-CCPCH reference power of all the neighbour cells or the serving cell is not available for the UEs staying in CELL\_DCH state, e.g. when the serving cell changes or the working frequency changes within the serving cell, but the intra-frequency cell list and/or the inter-frequency cell list has not been updated, the UE shall return an SNPL index value of 9. + +For the UEs staying in CELL\_DCH state, if the intra-frequency cell list and/or the inter-frequency cell list have been updated, before the pathloss of all of the cells that SNPL calculation involves is derived, the UE shall return an SNPL index value of 9. + +After receiving the related cell information, if neighbour cell indicated for SNPL reporting in the monitored neighbour cell list mentioned above is null, the UE shall return an SNPL index value of 9. + +For the UE configured with multi-carrier E-DCH transmission, all the uplink E-DCH carriers of the UE can be divided into one or more carrier group(s). The neighbour cells which are used for SNPL calculation for each carrier in one carrier group are the same. For physical layer of UE, the carrier group information shall be indicated by higher layer to make it know that which uplink E-DCH carriers are in the same carrier group. For each carrier group, the SNPL is + +calculated in reference to one carrier of the carrier group and is shared by all the carriers which are in the same carrier group. Higher layers shall configure the UE to use SNPL reporting type 1 or SNPL reporting type 2 for all carrier groups. In accordance with the SNPL reporting type, the UE shall be capable of selecting the corresponding formula from the above two formulas to calculate the SNPL for one carrier group, where $L_{\text{serv}}$ is the mean pathloss to the serving cell ( $L_{\text{serv}}$ ) and $L_n$ is the mean pathloss to the n-th cell of the N neighbour cells (with a primary or a secondary frequency being the same as one of the frequencies in the current carrier group) in the monitored neighbour cell list. + +For multi-carrier E-DCH transmission, the UE shall return an SNPL index value of 9 for one carrier when the UE is under the same scenarios as listed above for UE's returning an SNPL index value of 9. + +### 5.11.3 E-AGCH monitoring in CELL\_DCH state + +If E-AGCH DRX information is not configured by higher layers, + +if the UE has semi-persistent E-PUCH resources, the UE shall keep monitoring a set of E-AGCHs continuously; + +otherwise, when the latest scheduling information UE sent indicates the TEBS equals zero and the UE has received the corresponding ACK on E-HICH, after continuing monitoring E-AGCH for a period of time configured by higher layers, the UE may stop monitoring E-AGCH if the UE has no E-DCH data (including retransmission data) to transmit. When the TEBS becomes larger than zero, the UE shall start monitoring E-AGCH after sending scheduling information indicating that the TEBS is larger than zero. + +If the E-AGCH DRX information is configured by higher layers, the UE shall monitor E-AGCHs according to rules defined in the subclause 5.13. + +### 5.11.3A E-AGCH monitoring in CELL\_FACH state + +For the UE with a stored dedicated UE identity in CELL\_FACH state, when the latest scheduling information UE sent indicates the TEBS equals zero and the UE has received the corresponding ACK on E-HICH, after continuing monitoring E-AGCH for a period of time (T321) configured by higher layers (as described in [15]), UE may stop monitoring E-AGCH if the UE has no E-DCH data (including retransmission data) to transmit. The TEBS is described in [18]. + +If the TEBS becomes larger than zero, UE shall start monitoring E-AGCH after sending scheduling information indicating that the TEBS is larger than zero. + +For the UE without a dedicated UE identity in CELL\_FACH state or in IDLE mode, UE shall stop monitoring E-AGCH outside the common E-RNTI Scheduling Window (as described in [18]). + +## 5.12 MIMO operation of HS-DSCH + +### 5.12.1 General procedure + +This section applies only when a UE is configured in MIMO mode. + +The general transmitter structure to support MIMO operation of HS-PDSCH transmission is shown in figure 11A. Channel coding, interleaving and spreading are done the same as in non-MIMO mode. The Node B scheduler can decide to transmit one or two transport blocks to a UE in one TTI. The spread complex valued signals are fed to both TX antenna branches, and weighted with precoding weights. + +If the UTRAN schedules a single transport block to a UE in one TTI, it uses EBB (Eigenvector Based Beam-forming) or antenna selection for transmission of that transport block on the HS-PDSCH sub-frame. If the UTRAN schedules two transport blocks to a UE in one TTI, it uses two orthogonal precoding vectors to transmit the two transport blocks. The precoding vectors are generated by SVD (Singular Value Decomposition) of the channel matrix or grouped beam-forming to form the two beams. The PARC with two transmit antennas can be viewed as a special case, where the stream per antenna is transmitted independently. + +![Figure 11A: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission. The diagram shows two parallel processing paths. Each path starts with an input signal entering a block labeled with an 'X' (representing scrambling or spreading). The output of this block enters a large rectangular block (representing channel coding and modulation). The output of this block then enters another large rectangular block (representing precoding). Finally, the output of the precoding block is transmitted via an antenna. The two paths represent two separate data streams (stream1 and stream2) being processed independently before being transmitted from two different antennas.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +Figure 11A: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission. The diagram shows two parallel processing paths. Each path starts with an input signal entering a block labeled with an 'X' (representing scrambling or spreading). The output of this block enters a large rectangular block (representing channel coding and modulation). The output of this block then enters another large rectangular block (representing precoding). Finally, the output of the precoding block is transmitted via an antenna. The two paths represent two separate data streams (stream1 and stream2) being processed independently before being transmitted from two different antennas. + +**Figure 11A: The generic downlink transmitter structure to support MIMO operation for HS-PDSCH transmission.** + +The Node B estimates the uplink channels seen from each antenna by uplink physical channels or standalone midamble channel. The Node B scheduler decides whether to schedule one or two transport blocks to a UE in one TTI and what transport block size(s) and modulation scheme(s) to use for each of them. The Node B determines the precoding vectors applied on the HS-PDSCH sub-frame and forms the beams to the UE. The associated HS-SCCH type for single or dual stream HS-PDSCH transmission is signaled to the UE. The UE transmits the CQI report and ACK/NACK of each stream to the Node B via the associated HS-SICH. + +## 5.12.2 Identification of MIMO dual stream + +When the UE is configured in MIMO mode and the dual stream transmission is adopted, the two streams are called stream1 and stream2 respectively. According to the special default midamble allocation scheme, the Node B shall allocate the pattern1 to stream1, and the pattern2 to stream2. The UE identifies and detects two transport blocks in one TTI according to the different patterns. + +## 5.12.3 UE antennas time switched transmission + +When the UE is configured in MIMO mode, uplink time switched transmission at the UE with two antennas for uplink physical channels, i.e. HS-SICH, E-PUCH, DPCH and standalone midamble channel if configured by higher layers, is used for uplink channel estimation. + +The UE switches the two antennas to transmit the uplink physical channels HS-SICH, E-PUCH, and DPCH and standalone midamble channel among the uplink timeslots which may belong to one TTI or multiple TTIs allocated by UTRAN. The downlink signaling HCSN and ECSN are used to guarantee the identification of the two UE antennas and the exact update of the two channel estimation vectors at Node B. Note that time switched transmission is not applied to the random access uplink physical channel. + +If the standalone midamble channel is not configured, the UE antennas time switched transmission procedures for uplink physical channels are described below. + +- If the allocated resource for the UE includes multiple uplink timeslots in one TTI, the UE shall transmit the uplink physical channels in every timeslot by using the antenna selected according to the received downlink signaling value and the predefined relationship between UE and Node B. The details are as follows: + - If there is an HS-SICH in this TTI, the Node B implicitly informs the UE by HCSN on HS-SCCH which antenna shall be used to transmit HS-SICH. The UE shall use the antenna indicated by the parity of HCSN decimal value to transmit HS-SICH. Based on the reference antenna carrying HS-SICH, the UE switches the transmit antennas in turn for the consequent uplink transmission in this TTI; + - Else if there is no HS-SICH but scheduled E-PUCH in this TTI, the Node B implicitly informs UE by ECSN on E-AGCH which antenna shall be used to transmit the first timeslot of E-PUCH. UE shall use the antenna indicated by the parity of ECSN decimal value to transmit first timeslot of E-PUCH. And based on the reference antenna carrying the first timeslot of E-PUCH, the UE switches the transmit antennas in turn for the consequent uplink transmission in this TTI; + +- Else, the UE shall take the antenna used to transmit the uplink channel in the first timeslot of this TTI as reference and switch the transmit antennas in turn in the consequent uplink timeslots in this TTI. The reference antenna is the other antenna different from the one used last time for this transmission type which may be non-scheduled transmission, semi-persistent transmission and RDI E-PUCH transmission. +- Else, the allocated resource for the UE just include one uplink timeslot in one TTI, the UE shall select the antenna according to the different uplink channel. +- If there is an HS-SICH in this uplink timeslot, the UE shall select the antenna indicated by the parity of HCSN decimal value on the associated HS-SCCH; +- Else if there is no HS-SICH but scheduled E-PUCH in this uplink timeslot, the UE shall select the antenna indicated by the parity of ECSN decimal value on E-AGCH; +- Else, the UE shall select the other antenna different from the one used last time for this transmission type which may be non-scheduled transmission, semi-persistent transmission and RDI E-PUCH transmission. + +If the standalone midamble channel is configured, the UE antennas time switched transmission procedures for uplink physical channels are described below. + +If the UE needs to transmit an HS-SICH, the UE shall use a different antenna from the one used for HS-SICH to transmit the associated standalone midamble channel in the other uplink timeslot of the same subframe configured by higher layers. + +If there is other uplink physical channel(s) besides HS-SICH in subframe for the UE to transmit, the standalone midamble channel shall be omitted. + +## 5.12 AMU-MIMO operation of HS-DSCH and E-DCH + +If the UE is configured in MU-MIMO mode, the Node B should estimate the uplink channels seen from each antenna by uplink physical channels or standalone midamble channel. The Node B scheduler decides whether to schedule multiple UE using the same physical resource in one TTI according to uplink channel estimation. + +For the MU-MIMO operation of HS-DSCH, the special default midamble pattern is signaled on HS-SCCH to inform the UE which special default midamble pattern is used. The UE transmits the CQI report and ACK/NACK to the Node B via the associated HS-SICH. + +For the MU-MIMO operation of E-DCH, the special default midamble pattern is signaled on E-AGCH to inform the UE which special midamble pattern is used. The Node B transmits ACK/NACK to the each user via the associated E-HICH signature sequence. + +## 5.13 Control channel discontinuous reception procedures + +If the higher layers set CONTROL\_CHANNEL\_DRX\_STATUS to TRUE (as described in [15]) and Enabling\_Delay is configured to be finite value, after Enabling\_Delay radio frames have passed, UE\_DRX\_Enabled is TRUE. Or if the higher layers set CONTROL\_CHANNEL\_DRX\_STATUS to TRUE and Enabling\_Delay is configured to be infinity, after the UE has received DRX activation order via HS-SCCH order, UE\_DRX\_Enabled is TRUE. Otherwise UE\_DRX\_Enabled is FALSE. + +Whether discontinuous downlink HS-SCCH reception operation or discontinuous downlink E-AGCH reception operation is applied is determined by the setting of HS\_SCCH\_DRX\_Active and E\_AGCH\_DRX\_Active as follows: + +**HS\_SCCH\_DRX\_Active** shall be set to TRUE while UE\_DRX\_Enabled is TRUE and discontinuous downlink HS-SCCH reception is activated. Otherwise, HS\_SCCH\_DRX\_Active shall be set to FALSE. + +Discontinuous downlink HS-SCCH reception shall be activated at the time when UE\_DRX\_Enabled is set to TRUE, and may be further deactivated or activated by layer 1 HS-SCCH orders (see section 5.13.2). + +**E\_AGCH\_DRX\_Active** shall be set to TRUE while UE\_DRX\_Enabled is TRUE, E-AGCH DRX information is configured and discontinuous downlink E-AGCH reception is activated. Otherwise, E\_AGCH\_DRX\_Active shall be set to FALSE. + +Discontinuous downlink E-AGCH reception shall be activated at the time when UE\_DRX\_Enabled is set to TRUE and E-AGCH DRX information is configured and may be further deactivated or activated by layer 1 HS-SCCH orders. + +The higher layers define the discontinuous reception procedures using the following parameters (defined in [15]): + +**HS\_SCCH\_DRX Offset:** HS-SCCH reception pattern offset in subframes. + +**E\_AGCH\_DRX Offset:** E-AGCH reception pattern offset in subframes. + +**Enabling\_Delay:** ensures that the HS-SCCHs and E-AGCHs are received continuously for Enabling\_Delay radio frames after CONTROL\_CHANNEL\_DRX\_STATUS is set to TRUE. + +**HS\_SCCH\_DRX cycle:** HS-SCCH reception pattern length in subframes. + +**E\_AGCH\_DRX cycle:** E-AGCH reception pattern length in subframes. + +**Inactivity\_Threshold\_for\_HS\_SCCH\_DRX\_cycle:** For single carrier HS-DSCH reception, when HS\_SCCH\_DRX\_Active is TRUE, this timer shall be started or restarted in the same subframe as the HS-SICH corresponding to an HS-PDSCH reception. + +For multi-carrier HS-DSCH reception, this timer should be maintained per UE. When HS\_SCCH\_DRX\_Active is TRUE, this timer shall be started or restarted in the same subframe as the HS-SICH on any configured carrier corresponding to an HS-PDSCH reception. + +**E\_AGCH\_Inactivity\_Monitor\_Threshold:** For single carrier E-DCH transmission, when E\_AGCH\_DRX\_Active is TRUE, this timer shall be started or restarted in the same subframe as the E-HICH which contains the HARQ-ACK corresponding to the latest scheduling information indicating the TEBS equals zero. If the UE is transmitting SI only MAC-e PDU with TEBS equals zero and the UE is monitoring E-AGCHs only in the E-AGCH reception pattern, this timer shall not be started or restarted. + +For multi-carrier E-DCH transmission, this timer should be maintained per UE. When E\_AGCH\_DRX\_Active is TRUE, this timer shall be started or restarted in the same subframe as the E-HICH on any configured carrier which contains the HARQ-ACK corresponding to the latest scheduling information indicating the TEBS equals zero. If the UE is transmitting SI only MAC-i PDU with TEBS equals zero and the UE is monitoring E-AGCHs only in the E-AGCH reception pattern on all configured carriers, this timer shall not be started or restarted. + +### 5.13.1 Discontinuous downlink reception + +The HS-SCCH reception pattern is the same for all the configured carriers of the UE and is derived from a discontinuous reception subframe numbering as follows. + +The HS-SCCH reception pattern is the set of subframes whose HS-SCCH discontinuous reception radio frame number CFN and subframe number subframe number verify: + +$$((2*CFN - HS\_SCCH\_DRX\_Offset + subframe number) \text{ MOD } HS\_SCCH\_DRX\_cycle) = 0$$ + +For the first subframe within each radio frame, the subframe number shall be set to 0. For the second subframe within each radio frame, the subframe number shall be set to 1. + +When HS\_SCCH\_DRX\_Active is FALSE, the UE shall monitor HS-SCCHs continuously according to rules defined in the subclause 5.9.3. + +When HS\_SCCH\_DRX\_Active is TRUE and the timer Inactivity Threshold for HS-SCCH DRX cycle is not configured by higher layers, the UE shall monitor the HS-SCCH subframes in the HS-SCCH reception pattern on all configured carriers. + +When HS\_SCCH\_DRX\_Active is TRUE and the timer Inactivity Threshold for HS-SCCH DRX cycle is configured by higher layers, the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set on all configured carriers continuously when the timer is running. The UE shall only monitor the HS-SCCH subframes in the HS-SCCH reception pattern on all configured carriers when the timer is expired. + +The E-AGCH reception pattern is the same for all the configured carriers of the UE and is the set of subframes whose E-AGCH discontinuous reception radio frame number CFN and subframe number verify: + +$$((2*CFN - E\_AGCH\_DRX\_Offset + subframe number) \text{ MOD } E\_AGCH\_DRX\_cycle) = 0$$ + +When E\_AGCH\_DRX\_Active is FALSE and E-AGCH DRX information is configured, UE shall monitor E-AGCHs continuously. + +When E\_AGCH\_DRX\_Active is FALSE and the E-AGCH DRX information is not configured, UE shall monitor E-AGCHs according to rules defined in the subclause 5.11.3. + +When E\_AGCH\_DRX\_Active is TRUE and TEBS is larger than zero, the UE shall monitor the E-AGCHs on all configured carriers continuously. + +When E\_AGCH\_DRX\_Active is TRUE and TEBS is equal to zero, the UE is required to monitor the E-AGCHs in the UE's E-AGCH set on all configured carriers continuously until the subframe when the timer E\_AGCH\_Inactivity\_Monitor\_Threshold is expired. The UE shall start to monitor the E-AGCH subframes in the E-AGCH reception pattern on all configured carriers from the next subframe when the timer is expired. + +The HS-SCCH reception pattern is illustrated by Figure 11B. The grey subframes correspond to the HS-SCCH reception pattern HS\_SCCH\_DRX cycle = 4. + +![Figure 11B: Example for HS-SCCH reception pattern. The diagram shows a horizontal timeline with four subframes. The first and fourth subframes are shaded grey, representing active reception periods. Above the timeline, two double-headed arrows indicate the start and end of the reception cycle. The first arrow starts at the beginning of the first subframe and ends at the start of the second. The second arrow starts at the beginning of the third subframe and ends at the start of the fourth (grey) subframe.](83c2ebae8819e9cdca7eb157a13ee26a_img.jpg) + +Figure 11B: Example for HS-SCCH reception pattern. The diagram shows a horizontal timeline with four subframes. The first and fourth subframes are shaded grey, representing active reception periods. Above the timeline, two double-headed arrows indicate the start and end of the reception cycle. The first arrow starts at the beginning of the first subframe and ends at the start of the second. The second arrow starts at the beginning of the third subframe and ends at the start of the fourth (grey) subframe. + +Figure 11B: Example for HS-SCCH reception pattern + +### 5.13.2 HS-SCCH orders + +The Node B may activate and deactivate the discontinuous downlink reception operation through physical layer commands transmitted on one of the HS-SCCHs in the HS-SCCH set as specified in [9]. The activation and deactivation of the discontinuous downlink reception operation is applied by the UE in the same subframe as the HS-SICH subframe which contains the HARQ-ACK corresponding to the order. For multi-carrier E-DCH transmission and multi-carrier HS-DSCH reception, the activation and deactivation of the discontinuous downlink reception operation applies to HS-SCCH and E-AGCH on all carriers, namely, when receiving a DRX activation order on HS-SCCH, the UE shall activate the DRX of HS-SCCH and E-AGCH on all carriers; when receiving a DRX deactivation order on HS-SCCH, the UE shall deactivate the DRX of HS-SCCH and E-AGCH on all carriers. + +## 6 Physical layer procedures for the 7.68 Mcps option + +### 6.1 Transmitter power control + +The transmit power control procedure is identical to that of the 3.84 Mcps TDD option [clause 4.2] with the exception that the tabulated $\alpha_e$ values of subclause 4.2.2.4.1 for uplink power control of E-PUCH are substituted with the following values of table 3. + +Table 3: Tabulated $\alpha_e$ values for the 7.68 Mcps option + +| SF E-PUCH | (dB) | +|----------------------|------| +| 1 | 15 | +| 2 | 12 | +| 4 | 9 | +| 8 | 6 | +| 16 | 3 | +| 32 | 0 | + +### 6.2 Timing advance + +UTRAN may adjust the UE transmission timing with timing advance. The initial value for timing advance (TAphys) will be determined in the UTRAN by measurement of the timing of the PRACH or E-RUCCH. The required timing advance will be represented as a 9 bit number (0-511) 'UL Timing Advance' TAul, being the multiplier of 4 chips which is nearest to the required timing advance (i.e. TAphys = TAul × 4 chips). + +When Timing Advance is used the UTRAN will continuously measure the timing of a transmission from the UE and send the necessary timing advance value. On receipt of this value the UE shall adjust the timing of its transmissions accordingly in steps of $\pm 4$ chips. The transmission of TA values is done by means of higher layer messages. Upon receiving the TA command the UE shall adjust its transmission timing according to the timing advance command at the frame number specified by higher layer signaling. The UE is signaled the TA value in advance of the specified frame activation time to allow for local processing of the command and application of the TA adjustment on the specified frame. Node-B is also signaled the TA value and radio frame number that the TA adjustment is expected to take place. + +If TA is enabled by higher layers, after handover the UE shall transmit in the new cell with timing advance TA adjusted by the relative timing difference $\Delta t$ between the new and the old cell: + +$$TA_{\text{new}} = TA_{\text{old}} + 2\Delta t.$$ + +## 6.3 Synchronisation procedures + +The synchronisation procedures are identical to those of the 3.84Mcps TDD option [clause 4.4]. + +## 6.4 Discontinuous transmission (DTX) procedure + +The discontinuous transmission procedure is identical to that of the 3.84Mcps TDD option [clause 4.5]. + +## 6.5 Downlink transmit diversity + +Downlink transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-AGCH, E-HICH and SCH is optional in UTRAN. Its support is mandatory at the UE. + +### 6.5.1 Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH + +Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH is identical to the 3.84Mcps TDD option [clause 4.6.1]. + +### 6.5.2 Transmit diversity for SCH and S-CCPCH + +Transmit diversity for SCH and S-CCPCH is identical to the 3.84Mcps TDD option [clause 4.6.2]. + +### 6.5.3 Transmit diversity for Beacon Channels + +When beacon channels use burst type 4, SCTD shall not be applied. + +When beacon channels use burst type 1, Space Code Transmit Diversity (SCTD) for beacon channels may be employed optionally in the UTRAN. The support is mandatory in the UE except for the case where the UE only supports burst type 4. The use of SCTD will be indicated by higher layers. If SCTD is active within a cell: + +- SCTD shall be applied to any beacon channel, and +- the maximum number $K_{\text{Cell}}$ of midambles for burst type 1 that are supported in this cell may be 8 or 16, see [8]. The case of $K_{\text{Cell}} = 4$ midambles is not allowed for this burst type. + +#### 6.5.3.1 SCTD transmission scheme + +The open loop downlink transmit diversity scheme for beacon channels is shown in figure 12. Channel coding, rate matching, interleaving and bit-to-symbol mapping are performed as in the non-diversity mode. In Space Code Transmit Diversity mode the data sequence is spread with the channelisation codes and and scrambled with the cell specific scrambling code. The spread sequence on code is then transmitted on the diversity antenna. The power applied to each antenna shall be equal. + +![Block Diagram of the transmitter SCTD. The diagram shows 'Encoded and Interleaved Data Symbols, 2 data fields' entering from the left. This data is split into two parallel paths. The top path goes through a block labeled 'SPR-SCR c(1)' and then into a 'MUX' block. The bottom path goes through a block labeled 'SPR-SCR c(2)' and then into another 'MUX' block. The top 'MUX' block also receives 'Midamble 1' and has an output labeled 'Tx. Antenna 1'. The bottom 'MUX' block also receives 'Midamble 2' and has an output labeled 'Tx. Antenna 2'.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +Block Diagram of the transmitter SCTD. The diagram shows 'Encoded and Interleaved Data Symbols, 2 data fields' entering from the left. This data is split into two parallel paths. The top path goes through a block labeled 'SPR-SCR c(1)' and then into a 'MUX' block. The bottom path goes through a block labeled 'SPR-SCR c(2)' and then into another 'MUX' block. The top 'MUX' block also receives 'Midamble 1' and has an output labeled 'Tx. Antenna 1'. The bottom 'MUX' block also receives 'Midamble 2' and has an output labeled 'Tx. Antenna 2'. + +**Figure 12: Block Diagram of the transmitter SCTD** + +## 6.6 Random access procedure + +The physical random access procedure described below is invoked whenever a higher layer requests transmission of a message on the RACH. The physical random access procedure is controlled by primitives from RRC and MAC. Retransmission on the RACH in case of failed transmission (e.g. due to a collision) is controlled by higher layers. Thus, the backoff algorithm and associated handling of timers is not described here. The definition of the RACH in terms of PRACH Access Service Classes is broadcast on the BCH in each cell. Parameters for common physical channel uplink outer loop power control are also broadcast on the BCH in each cell. The UE needs to decode this information prior to transmission on the RACH. + +### 6.6.1 Physical random access procedure + +The physical random access procedure is identical to that of the 3.84Mcps TDD option [clause 4.7.1]. + +## 6.6A E-RUCCH transmission procedure + +The E-RUCCH transmission procedure is identical to that of the 3.84Mcps TDD option [clause 4.7A] + +## 6.7 DSCH procedure + +Higher layer signalling is used to indicate to the UE the need for PDSCH detection. + +## 6.8 Idle periods for IPDL location method + +The IPDL procedure is identical to that of the 3.84Mcps TDD option [clause 4.10]. + +## 6.9 HS-DSCH procedure + +### 6.9.1 Link adaptation procedure + +For HS-DSCH, the modulation scheme and effective code rate shall be selected by higher layers located within the NodeB. This shall be achieved by appropriate selection of an HS-DSCH transport block size, modulation format and resources by higher layers. Selection of these parameters may be based on CQI reports from the UE. + +The overall HS-DSCH link adaptation procedure consists of *two parts*: + +*Node B procedure:* + +- 1) The NodeB shall transmit HS-SCCH carrying a UE identity identifying the UE for which HS-DSCH TTI allocation has been given. In the case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same HS-SCCH shall be used for associated signalling. +- 2) The NodeB transmits HS-DSCH to the UE using the resources indicated in the HS-SCCH. + +- 3) Upon receiving the HS-SICH from the respective UE, the status report (ACK/NACK and CQI) shall be passed to higher layers. + +*UE procedure:* + +- 1) When indicated by higher layers, the UE shall start monitoring all HS-SCCHs that are in its HS-SCCH set as signalled to it by higher layers. The information carried on the HS-SCCH is described in [8]. +- 2) In the case that a HS-SCCH is identified to be correct by its CRC, the UE shall read the HS-PDSCHs indicated by the HS-SCCH. In the case that a HS-SCCH is identified to be incorrect, the UE shall discard the data on the HS-SCCH and return to monitoring. +- 3) After reading the HS-PDSCHs, the UE shall generate an ACK/NACK message and transmit this to the NodeB in the associated HS-SICH, along with the most recently derived CQI. + +The mapping of HS-PDSCH channelisation code set and timeslot information carried by the HS-SCCH for a given HS-DSCH TTI is described in [9]. + +For a given allocation of HS-PDSCH resources to a UE for a specific HS-DSCH TTI, the following shall apply: + +- If timeslot information on HS-SCCH indicates two or more timeslots, none of these timeslots shall comprise a beacon channel. +- If timeslot information on HS-SCCH indicates a single timeslot and this timeslot comprises a beacon channel then: + - The Node-B shall not indicate SF=1 for any HS-PDSCH resource. + - The set of HS-PDSCH resources allocated by the Node-B to a UE shall exclusively comprise either beacon function or non-beacon function physical channels. The Node B shall therefore not allocate both beacon function and non-beacon function physical channels within the beacon timeslot to the UE. If the HS-DSCH for a specific HS-DSCH TTI is mapped to the beacon channel, this shall be signalled using $k_{start} = 1$ and $k_{stop} = 1$ . For a definition of the first and last allocated channelisation code indices $k_{start}$ and $k_{stop}$ on HS-SCCH refer to [9]. + - When SCTD antenna diversity is applied to the beacon channel, then the presence of channelisation code within the channelisation code set information on HS-SCCH shall implicitly indicate the presence of channelisation code . + +## 6.9.2 HS-DSCH channel quality indication procedure + +The HS-DSCH channel quality indication procedure is identical to that of the 3.84Mcps TDD option [clause 4.11.2]. + +## 6.10 Macro-diversity procedure + +The macrodiversity procedure is identical to that of the 3.84Mcps TDD option [clause 4.12]. + +## 6.11 E-DCH related procedures + +### 6.11.1 ACK/NACK detection + +The procedure for detection of ACK/NACK is identical to that of the 3.84Mcps option [subclause 4.13.1] + +### 6.11.2 Serving and neighbour cell pathloss metric derivation + +The procedure for serving and neighbour cell metric derivation is identical to that of the 3.84Mcps option [subclause 4.13.2] + +### 6.11.3 Channelisation code hopping procedure for E-PUCH + +For the 7.68Mcps option, the procedure for channelisation code hopping on E-PUCH is identical to that of the 3.84Mcps option [subclause 4.13.3] with two exceptions: + +- i) the code hopping index parameter is calculated as: + +ii) the code hopping index parameter sequences of table 1c are substituted for the values of table 4 below. + +**Table 4: Hopping index parameter sequences for the 7.68Mcps options** + +| CRRI | Hop index $h_i$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------|-----------------|---|----|----|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | +| SF32 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 31 | 1 | 17 | 9 | 5 | 21 | 3 | 29 | 3 | 19 | 11 | 7 | 7 | 23 | 5 | 31 | 2 | 8 | 10 | 6 | 6 | 22 | 4 | 30 | 4 | 0 | 12 | 8 | 8 | 24 | 6 | 32 | | +| 2 | 32 | 2 | 18 | 10 | 6 | 22 | 4 | 30 | 4 | 20 | 12 | 8 | 8 | 24 | 6 | 32 | 1 | 7 | 9 | 5 | 5 | 21 | 3 | 29 | 3 | 9 | 11 | 7 | 7 | 23 | 5 | 31 | | +| 3 | 33 | 3 | 19 | 11 | 7 | 23 | 5 | 31 | 1 | 17 | 9 | 5 | 5 | 21 | 3 | 29 | 4 | 0 | 12 | 8 | 8 | 24 | 6 | 32 | 2 | 8 | 10 | 6 | 6 | 22 | 4 | 30 | | +| 4 | 34 | 4 | 20 | 12 | 8 | 24 | 6 | 32 | 2 | 18 | 10 | 6 | 6 | 22 | 4 | 30 | 3 | 9 | 11 | 7 | 7 | 23 | 5 | 31 | 1 | 7 | 9 | 5 | 5 | 21 | 3 | 29 | | +| 5 | 35 | 5 | 21 | 13 | 9 | 1 | 17 | 9 | 25 | 7 | 23 | 15 | 1 | 3 | 19 | 1 | 27 | 6 | 2 | 14 | 0 | 2 | 18 | 0 | 26 | 8 | 4 | 16 | 2 | 4 | 20 | 2 | 28 | +| 6 | 36 | 6 | 22 | 14 | 0 | 2 | 18 | 0 | 26 | 8 | 24 | 16 | 2 | 4 | 20 | 2 | 28 | 5 | 1 | 13 | 9 | 1 | 17 | 9 | 25 | 7 | 3 | 15 | 1 | 3 | 19 | 1 | 27 | +| 7 | 37 | 7 | 23 | 15 | 1 | 3 | 19 | 1 | 27 | 5 | 21 | 13 | 9 | 1 | 17 | 9 | 25 | 8 | 4 | 16 | 2 | 4 | 20 | 2 | 28 | 6 | 2 | 14 | 0 | 2 | 18 | 0 | 26 | +| 8 | 38 | 8 | 24 | 16 | 2 | 4 | 20 | 2 | 28 | 6 | 22 | 14 | 0 | 2 | 18 | 0 | 26 | 7 | 3 | 15 | 1 | 3 | 19 | 1 | 27 | 5 | 1 | 13 | 9 | 1 | 17 | 9 | 25 | +| 9 | 39 | 9 | 25 | 1 | 7 | 13 | 29 | 5 | 21 | 1 | 27 | 3 | 9 | 15 | 31 | 7 | 23 | 10 | 6 | 2 | 8 | 14 | 30 | 6 | 22 | 12 | 8 | 4 | 0 | 16 | 32 | 8 | 24 | +| 10 | 40 | 0 | 26 | 2 | 8 | 14 | 30 | 6 | 22 | 2 | 28 | 4 | 0 | 16 | 32 | 8 | 24 | 9 | 5 | 1 | 7 | 13 | 29 | 5 | 21 | 11 | 7 | 3 | 9 | 15 | 31 | 7 | 23 | +| 11 | 41 | 1 | 27 | 3 | 9 | 15 | 31 | 7 | 23 | 9 | 25 | 1 | 7 | 13 | 29 | 5 | 21 | 12 | 8 | 4 | 0 | 16 | 32 | 8 | 24 | 10 | 6 | 2 | 8 | 14 | 30 | 6 | 22 | +| 12 | 42 | 2 | 28 | 4 | 0 | 16 | 32 | 8 | 24 | 0 | 26 | 2 | 8 | 14 | 30 | 6 | 22 | 11 | 7 | 3 | 9 | 15 | 31 | 7 | 23 | 9 | 5 | 1 | 7 | 13 | 29 | 5 | 21 | +| 13 | 43 | 3 | 29 | 5 | 1 | 9 | 25 | 1 | 17 | 5 | 31 | 7 | 3 | 11 | 27 | 3 | 19 | 14 | 0 | 6 | 2 | 10 | 26 | 2 | 18 | 16 | 2 | 8 | 4 | 12 | 28 | 4 | 20 | +| 14 | 44 | 4 | 30 | 6 | 2 | 10 | 26 | 2 | 18 | 6 | 32 | 8 | 4 | 12 | 28 | 4 | 20 | 13 | 9 | 5 | 1 | 9 | 25 | 1 | 17 | 15 | 1 | 7 | 3 | 11 | 27 | 3 | 19 | +| 15 | 45 | 5 | 31 | 7 | 3 | 11 | 27 | 3 | 19 | 3 | 29 | 5 | 1 | 9 | 25 | 1 | 17 | 16 | 2 | 8 | 4 | 12 | 28 | 4 | 20 | 14 | 0 | 6 | 2 | 10 | 26 | 2 | 18 | +| 16 | 46 | 6 | 32 | 8 | 4 | 12 | 28 | 4 | 20 | 4 | 30 | 6 | 2 | 10 | 26 | 2 | 18 | 15 | 1 | 7 | 3 | 11 | 27 | 3 | 19 | 13 | 9 | 5 | 1 | 9 | 25 | 1 | 17 | +| 17 | 47 | 7 | 1 | 25 | 9 | 21 | 5 | 9 | 13 | 9 | 3 | 27 | 1 | 23 | 7 | 1 | 15 | 18 | 2 | 26 | 0 | 22 | 6 | 0 | 14 | 20 | 4 | 28 | 2 | 24 | 8 | 2 | 16 | +| 18 | 48 | 8 | 2 | 26 | 0 | 22 | 6 | 0 | 14 | 0 | 4 | 28 | 2 | 24 | 8 | 2 | 16 | 17 | 1 | 25 | 9 | 21 | 5 | 9 | 13 | 19 | 3 | 27 | 1 | 23 | 7 | 1 | 15 | +| 19 | 49 | 9 | 3 | 27 | 1 | 23 | 7 | 1 | 15 | 7 | 1 | 25 | 9 | 21 | 5 | 9 | 13 | 20 | 4 | 28 | 2 | 24 | 8 | 2 | 16 | 18 | 2 | 26 | 0 | 22 | 6 | 0 | 14 | +| 20 | 50 | 0 | 4 | 28 | 2 | 24 | 8 | 2 | 16 | 8 | 2 | 26 | 0 | 22 | 6 | 0 | 14 | 19 | 3 | 27 | 1 | 23 | 7 | 1 | 15 | 17 | 1 | 25 | 9 | 21 | 5 | 9 | 13 | +| 21 | 51 | 1 | 5 | 29 | 3 | 17 | 1 | 5 | 9 | 3 | 7 | 31 | 5 | 19 | 3 | 7 | 11 | 22 | 6 | 30 | 4 | 18 | 2 | 6 | 10 | 24 | 8 | 32 | 6 | 20 | 4 | 8 | 12 | +| 22 | 52 | 2 | 6 | 30 | 4 | 18 | 2 | 6 | 10 | 4 | 8 | 32 | 6 | 20 | 4 | 8 | 12 | 21 | 5 | 29 | 3 | 17 | 1 | 5 | 9 | 23 | 7 | 31 | 5 | 19 | 3 | 7 | 11 | +| 23 | 53 | 3 | 7 | 31 | 5 | 19 | 3 | 7 | 11 | 1 | 5 | 29 | 3 | 17 | 1 | 5 | 9 | 24 | 8 | 32 | 6 | 20 | 4 | 8 | 12 | 22 | 6 | 30 | 4 | 18 | 2 | 6 | 10 | +| 24 | 54 | 4 | 8 | 32 | 6 | 20 | 4 | 8 | 12 | 2 | 6 | 30 | 4 | 18 | 2 | 6 | 10 | 23 | 7 | 31 | 5 | 19 | 3 | 7 | 11 | 21 | 5 | 29 | 3 | 17 | 1 | 5 | 9 | +| 25 | 55 | 5 | 9 | 17 | 1 | 29 | 13 | 1 | 5 | 7 | 11 | 19 | 3 | 31 | 15 | 3 | 7 | 26 | 0 | 18 | 2 | 30 | 14 | 2 | 6 | 28 | 2 | 20 | 4 | 32 | 16 | 4 | 8 | +| 26 | 56 | 6 | 10 | 18 | 2 | 30 | 14 | 2 | 6 | 8 | 12 | 20 | 4 | 32 | 16 | 4 | 8 | 25 | 9 | 17 | 1 | 29 | 13 | 1 | 5 | 27 | 1 | 19 | 3 | 31 | 15 | 3 | 7 | +| 27 | 57 | 7 | 11 | 19 | 3 | 31 | 15 | 3 | 7 | 5 | 9 | 17 | 1 | 29 | 13 | 1 | 5 | 28 | 2 | 20 | 4 | 32 | 16 | 4 | 8 | 26 | 0 | 18 | 2 | 30 | 14 | 2 | 6 | +| 28 | 58 | 8 | 12 | 20 | 4 | 32 | 16 | 4 | 8 | 6 | 10 | 18 | 2 | 30 | 14 | 2 | 6 | 27 | 1 | 19 | 3 | 31 | 15 | 3 | 7 | 25 | 9 | 17 | 1 | 29 | 13 | 1 | 5 | +| 29 | 59 | 9 | 13 | 21 | 5 | 25 | 9 | 7 | 1 | 1 | 15 | 23 | 7 | 27 | 11 | 9 | 3 | 30 | 4 | 22 | 6 | 26 | 10 | 8 | 2 | 32 | 6 | 24 | 8 | 28 | 12 | 0 | 4 | +| 30 | 60 | 0 | 14 | 22 | 6 | 26 | 10 | 8 | 2 | 2 | 16 | 24 | 8 | 28 | 12 | 0 | 4 | 29 | 3 | 21 | 5 | 25 | 9 | 7 | 1 | 31 | 5 | 23 | 7 | 27 | 11 | 9 | 3 | +| 31 | 61 | 1 | 15 | 23 | 7 | 27 | 11 | 9 | 3 | 9 | 13 | 21 | 5 | 25 | 9 | 7 | 1 | 32 | 6 | 24 | 8 | 28 | 12 | 0 | 4 | 30 | 4 | 22 | 6 | 26 | 10 | 8 | 2 | +| 32 | 62 | 2 | 16 | 24 | 8 | 28 | 12 | 0 | 4 | 0 | 14 | 22 | 6 | 26 | 10 | 8 | 2 | 31 | 5 | 23 | 7 | 27 | 11 | 9 | 3 | 29 | 3 | 21 | 5 | 25 | 9 | 7 | 1 | +| SF16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|---|----|----|---|----|----|---|----|---|----|----|---|----|----|---|----|----|---|----|---|----|----|---|----|----|---|----|---|----|----|---|----|--| +| 1 | 15 | | 1 | | 1 | | | | | 1 | | | | | 1 | | | | | 1 | | | | | 1 | | | | | 1 | | | | | +| | | 1 | 9 | 5 | 3 | 3 | 11 | 7 | 15 | 2 | 10 | 6 | 4 | 4 | 12 | 8 | 16 | 1 | 9 | 5 | 3 | 3 | 11 | 7 | 15 | 2 | 0 | 6 | 4 | 4 | 12 | 8 | 16 | | +| 2 | 16 | | | | 1 | | | | | | | | 1 | | | | | | | | 1 | | | | | | | 1 | | | | | | | +| | | 2 | 10 | 6 | 4 | 4 | 12 | 8 | 16 | 1 | 9 | 5 | 3 | 3 | 11 | 7 | 15 | 2 | 0 | 6 | 4 | 4 | 12 | 8 | 16 | 1 | 9 | 5 | 3 | 3 | 11 | 7 | 15 | | +| 3 | 17 | | | | 1 | | | | | | | | 1 | | | | | | | | 1 | | | | | | | 1 | | | | | | | +| | | 3 | 11 | 7 | 5 | 1 | 9 | 5 | 13 | 4 | 12 | 8 | 6 | 2 | 10 | 6 | 14 | 3 | 1 | 7 | 5 | 1 | 9 | 5 | 13 | 4 | 2 | 8 | 6 | 2 | 10 | 6 | 14 | | +| 4 | 18 | | | | 1 | | | | | | | | 1 | | | | | | | | 1 | | | | | | | 1 | | | | | | | +| | | 4 | 12 | 8 | 6 | 2 | 10 | 6 | 14 | 3 | 11 | 7 | 5 | 1 | 9 | 5 | 13 | 4 | 2 | 8 | 6 | 2 | 10 | 6 | 14 | 3 | 1 | 7 | 5 | 1 | 9 | 5 | 13 | | +| 5 | 19 | | | | | | | | | | | 1 | | | | | | | 1 | | | | | | | | | 1 | | | | | | | +| | | 5 | 13 | 1 | 9 | 7 | 15 | 3 | 11 | 6 | 14 | 2 | 0 | 8 | 16 | 4 | 12 | 5 | 3 | 1 | 9 | 7 | 15 | 3 | 11 | 6 | 4 | 2 | 0 | 8 | 16 | 4 | 12 | | +| 6 | 20 | | | | 1 | | | | | | | | | | | | | 1 | | | | | | | | | 1 | | | | | | | | +| | | 6 | 14 | 2 | 0 | 8 | 16 | 4 | 12 | 5 | 13 | 1 | 9 | 7 | 15 | 3 | 11 | 6 | 4 | 2 | 0 | 8 | 16 | 4 | 12 | 5 | 3 | 1 | 9 | 7 | 15 | 3 | 11 | | +| 7 | 21 | | | | 1 | | | | | | | | | | | | | 1 | | | | | | | | | 1 | | | | | | | | +| | | 7 | 15 | 3 | 1 | 5 | 13 | 1 | 9 | 8 | 16 | 4 | 2 | 6 | 14 | 2 | 10 | 7 | 5 | 3 | 1 | 5 | 13 | 1 | 9 | 8 | 6 | 4 | 2 | 6 | 14 | 2 | 10 | | +| 8 | 22 | | | | 1 | | | | | | | | | | | | | 1 | | | | | | | | | 1 | | | | | | | | +| | | 8 | 16 | 4 | 2 | 6 | 14 | 2 | 10 | 7 | 15 | 3 | 1 | 5 | 13 | 1 | 9 | 8 | 6 | 4 | 2 | 6 | 14 | 2 | 10 | 7 | 5 | 3 | 1 | 5 | 13 | 1 | 9 | | +| 9 | 23 | | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 9 | 1 | 13 | 5 | 11 | 3 | 5 | 7 | 0 | 2 | 14 | 6 | 12 | 4 | 6 | 8 | 9 | 1 | 13 | 5 | 11 | 3 | 5 | 7 | 10 | 2 | 14 | 6 | 12 | 4 | 6 | 8 | | +| 10 | 24 | 1 | | | | | | 1 | | | | | | 1 | | | | | | | | 1 | | | | | | 1 | | | | | | | +| | | 0 | 2 | 14 | 6 | 12 | 4 | 6 | 8 | 9 | 1 | 13 | 5 | 11 | 3 | 5 | 7 | 10 | 2 | 14 | 6 | 12 | 4 | 6 | 8 | 9 | 1 | 13 | 5 | 11 | 3 | 5 | 7 | | +| 11 | 25 | 1 | | | | | | 1 | | | | | | 1 | | | | | | | | 1 | | | | | | 1 | | | | | | | +| | | 1 | 3 | 15 | 7 | 9 | 1 | 3 | 5 | 2 | 4 | 16 | 8 | 10 | 2 | 4 | 6 | 11 | 3 | 15 | 7 | 9 | 1 | 3 | 5 | 12 | 4 | 16 | 8 | 10 | 2 | 4 | 6 | | +| 12 | 26 | 1 | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 2 | 4 | 16 | 8 | 10 | 2 | 4 | 6 | 1 | 3 | 15 | 7 | 9 | 1 | 3 | 5 | 12 | 4 | 16 | 8 | 10 | 2 | 4 | 6 | 11 | 3 | 15 | 7 | 9 | 1 | 3 | 5 | | +| 13 | 27 | 1 | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 3 | 5 | 9 | 1 | 15 | 7 | 1 | 3 | 4 | 6 | 10 | 2 | 16 | 8 | 2 | 4 | 13 | 5 | 9 | 1 | 15 | 7 | 1 | 3 | 14 | 6 | 10 | 2 | 16 | 8 | 2 | 4 | | +| 14 | 28 | 1 | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 4 | 6 | 10 | 2 | 16 | 8 | 2 | 4 | 3 | 5 | 9 | 1 | 15 | 7 | 1 | 3 | 14 | 6 | 10 | 2 | 16 | 8 | 2 | 4 | 13 | 5 | 9 | 1 | 15 | 7 | 1 | 3 | | +| 15 | 29 | 1 | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 5 | 7 | 11 | 3 | 13 | 5 | 9 | 1 | 6 | 8 | 12 | 4 | 14 | 6 | 0 | 2 | 15 | 7 | 11 | 3 | 13 | 5 | 9 | 1 | 16 | 8 | 12 | 4 | 14 | 6 | 0 | 2 | | +| 16 | 30 | 1 | | | | | | 1 | | 1 | | | | | | 1 | | | | | | | 1 | | 1 | | | | | | 1 | | | | +| | | 6 | 8 | 12 | 4 | 14 | 6 | 0 | 2 | 5 | 7 | 11 | 3 | 13 | 5 | 9 | 1 | 16 | 8 | 12 | 4 | 14 | 6 | 0 | 2 | 15 | 7 | 11 | 3 | 13 | 5 | 9 | 1 | | + +SF8 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---|----|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 7 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | +| 2 | 8 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | 2 | 6 | 4 | 8 | 1 | 5 | 3 | 7 | +| 3 | 9 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | +| 4 | 10 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | 4 | 8 | 2 | 6 | 3 | 7 | 1 | 5 | +| 5 | 11 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | +| 6 | 12 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | 6 | 2 | 8 | 4 | 5 | 1 | 7 | 3 | +| 7 | 13 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | +| 8 | 14 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | 8 | 4 | 6 | 2 | 7 | 3 | 5 | 1 | + +SF4 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 3 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | +| 2 | 4 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | 2 | 4 | 1 | 3 | +| 3 | 5 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | +| 4 | 6 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | 4 | 2 | 3 | 1 | + +SF2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 1 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | +| 2 | 2 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | + +SF1 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| + +## Annex A (informative): Power Control + +### A.1 Example implementation of downlink power control in the UE + +The power control may be realized by two cascaded control loops. The outer loop controls the transmission quality, whose reference value is set by higher layers [15], by providing the reference value for the inner loop. This reference value should be the SIR at the UE [15]. The inner loop controls the physical quantity for which the outer loop produces the reference value (e. g. the SIR) by generating TPC commands. This may be done by comparing the measured SIR to its reference value. When the measured value is higher than the target SIR value, TPC command = "down". When this is lower than or equal to the target SIR value, TPC command = "up". + +In case of a downlink transmission pause on the DPCH or PDSCH, the receive power (RSCP) of the data can no longer be used for inner loop SIR calculations in the UE. In this case the UE should trace the fluctuations of the pathloss based on the P-CCPCH and use these values instead for generating the TPC commands. This pathloss together with the timeslot ISCP measurement in the data timeslot, which is ongoing, should be used to calculate a virtual SIR value: + +$$\text{SIR}_{\text{virt}}(i) = \text{RSCP}_{\text{virt}}(i) - \text{ISCP}(i) + 10 \lg \text{SF},$$ + +$$\text{RSCP}_{\text{virt}}(i) = \text{RSCP}_0 + L_0 - L(i) + \sum_{k=1}^{i-1} \text{TPC}(k)$$ + +RSCP: Received signal code power in dBm + +ISCP: Interference signal code power in the DPCH / PDSCH timeslot in dBm + +SF: Used spreading factor + +L: pathloss in dB measured on the P-CCPCH. The same weighting of the long- and short-term pathloss should be used as for uplink open loop power control, see Annex A.1 + +i: index for the frames during a transmission pause, $1 \leq i \leq$ number of frames in the pause + +$L_0$ : weighted pathloss in the last frame before the transmission pause in dB + +$\text{RSCP}_0$ : RSCP of the data that was used in the SIR calculation of the last frame before the pause in dBm + +TPC (k): $\pm$ power control stepsize in dB according to the TPC bit generated and transmitted in frame k, TPC bit "up" = +stepsize, TPC bit "down" = -stepsize + +### A.2 Example implementation of closed loop uplink power control in Node B for 1.28Mcps TDD + +Uplink power control is based on a quality target, set by higher layers. An example implementation for a Node B TPC calculation algorithm is SIR based. In this algorithm, an outer loop sets a target SIR value, $\text{SIR}_{\text{target}}$ , which may be adjusted from time to time in order to ensure that the quality target is met. In the meantime, as part of an inner loop a calculation of SIR in associated uplink transmissions may be carried out. When the measured value is higher than the target SIR value, TPC command = "down". When the measurement is lower than or equal to the target SIR, TPC command = "up". + +### A.3 Example implementation of downlink power control in UE for 1.28Mcps TDD when TSTD is used + +Downlink power control is based on a quality target, set by higher layers. An example implementation for a UE TPC calculation algorithm is SIR based. In this algorithm, an outer loop sets a target SIR value, $\text{SIR}_{\text{target}}$ , which may be adjusted from time to time in order to ensure that the quality target is met. In the meantime, as part of an inner loop a calculation of SIR in associated downlink transmissions may be carried out. When the measured value is higher than the + +target SIR value, TPC command = "down". When the measurement is lower than or equal to the target SIR, TPC command = "up". + +When TSTD is applied, the UE can use the consecutive measurements of SIR to calculate $SIR_{AVG}$ : + +$$SIR_{AVG}(i) = w_1 SIR(i-1) + w_2 SIR(i),$$ + +where, $w_1 + w_2 = 1$ , $w_1 \geq 0$ , $w_2 \geq 0$ , and $SIR(i)$ is the measurement of SIR in sub-frame $i$ and $SIR_{AVG}(i)$ is the measurement of $SIR_{AVG}$ in sub-frame $i$ . If $SIR_{AVG}$ is greater than the target SIR value, TPC command = "down". If the $SIR_{AVG}$ is smaller than the target SIR value, TPC command = "up". + +In case of a downlink transmission pause on the DPCH, the example in Annex A.1 can be used for DL power control with $RSCP_{virt}(i)$ and $ISCP(i)$ replaced by $RSCP_{AVG}(i)$ and $ISCP_{AVG}(i)$ , where + +$$RSCP_{AVG}(i) = w_1 RSCP_{virt}(i-1) + w_2 RSCP_{virt}(i),$$ + +$$ISCP_{AVG}(i) = w_1 ISCP(i-1) + w_2 ISCP(i).$$ + +## A.4 Example implementation of open loop power control for access procedure for 1.28Mcps TDD + +The higher layer signals (on BCH) a power increment that is applied to the SYNC-UL burst only for the access procedure. At each new transmission of a SYNC-UL burst during the access procedure, the transmit power level can be increased by this power increment. + +## A.5 Example implementation of closed loop uplink HS-SICH power control in Node B for 1.28Mcps TDD + +If the UE is not configured in MIMO mode, uplink power control is based on a quality target and a power offset, set by higher layers. An example implementation for a Node B TPC calculation algorithm is SIR based (HS-SICH SIR Target). In this algorithm, if an ACK is decoded from HS-SICH, the Node B shall adjust the measured value of HS-SICH with a power offset. When the (adjusted) measured value is higher than the target SIR value, TPC command = "down". When the (adjusted) measurement is lower than or equal to the target SIR, TPC command = "up" + +If the UE is configured in MIMO mode, uplink power control is based on a quality target and a power offset, set by higher layers. An example implementation for a Node B TPC calculation algorithm is SIR based (HS-SICH SIR Target). In this algorithm, if an ACK is decoded from HS-SICH for single stream transmission or two ACKs are decoded from HS-SICH for dual stream transmission, the Node B shall adjust the measured value of HS-SICH with a power offset. When the (adjusted) measured value is higher than the target SIR value, TPC command = "down". When the (adjusted) measurement is lower than or equal to the target SIR, TPC command = "up". + +--- + +## Annex B (informative): Determination of weight information + +Selective Transmit Diversity (STD) and Transmit Adaptive Antennas (TxAA) are examples of transmit diversity schemes for dedicated physical channels. + +--- + +### B.1 STD weights + +The weight vector will take only two values depending on the signal strength received by each antenna in the uplink slot. For each user, the antenna receiving the highest power will be selected (i.e. the corresponding weight will be set to 1). + +**Table B.1: STD weights for two TX antennas** + +| | W1 | W2 | +|-----------------------------------|----------------------|----------------------| +| Antenna 1 receiving highest power | 1 | 0 | +| Antenna 2 receiving highest power | 0 | 1 | + +--- + +### B.2 TxAA weights + +In a generic sense, the weight vector to be applied at the transmitter is the $\underline{w}$ that maximises: + +$$P = \underline{w}^H H^H H \underline{w} \quad (1)$$ + +where + +$$H = [\underline{h}_1 \ \underline{h}_2] \text{ and } \underline{w} = [w_1, w_2]^T$$ + +and where the column vector $\underline{h}_i$ represents the estimated uplink channel impulse response for the i'th transmission antenna, of length equal to the length of the channel impulse response. + +--- + +## Annex C (informative): Cell search procedure for 3.84Mcps TDD + +During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code and frame synchronisation of that cell. The cell search is typically carried out in three steps: + +### Step 1: Primary synchronisation code acquisition + +During the first step of the cell search procedure, the UE uses the SCH's primary synchronisation code to find a cell. This is typically done with a single matched filter (or any similar device) matched to the primary synchronisation code which is common to all cells. A cell can be found by detecting peaks in the matched filter output. + +Note that for a cell of SCH slot configuration case 1, the SCH can be received periodically every 15 slots. In case of a cell of SCH slot configuration case 2, the following SCH slot can be received at offsets of either 7 or 8 slots from the previous SCH slot. + +### Step 2: Code group identification and slot synchronisation + +During the second step of the cell search procedure, the UE uses the SCH's secondary synchronisation codes to identify 1 out of 32 code groups for the cell found in the first step. This is typically done by correlating the received signal with the secondary synchronisation codes at the detected peak positions of the first step. The primary synchronisation code provides the phase reference for coherent detection of the secondary synchronisation codes. The code group can then uniquely be identified by detection of the maximum correlation values. + +Each code group indicates a different $t_{offset}$ parameter and 4 specific cell parameters. Each of the cell parameters is associated with one particular downlink scrambling code and one particular long and short basic midamble code. When the UE has determined the code group, it can unambiguously derive the slot timing of the found cell from the detected peak position in the first step and the $t_{offset}$ parameter of the found code group in the second step. + +Note that the modulation of the secondary synchronisation codes also indicates the position of the SCH slot within a 2 frames period, e.g. a frame with even or odd SFN. Additionally, in the case of SCH slot configuration following case 2, the SCH slot position within one frame, e.g. first or last SCH slot, can be derived from the modulation of the secondary synchronisation codes. + +### Step 3: Downlink scrambling code, basic midamble code identification and frame synchronisation + +During the third and last step of the cell search procedure, the UE determines the exact downlink scrambling code, basic midamble code and frame timing used by the found cell. The long basic midamble code can be identified by correlation over the P-CCPCH (or any other beacon channel) with the 4 possible long basic midamble codes of the code group found in the second step. A P-CCPCH (or any other beacon channel) always uses the midamble $m^{(1)}$ (and in case of SCTD also midamble $m^{(2)}$ ) derived from the long basic midamble code and always uses a fixed and pre-assigned channelisation code. + +When the long basic midamble code has been identified, downlink scrambling code and cell parameter are also known. The UE can read system and cell specific BCH information and acquire frame synchronisation. + +Note that even for an initial cell parameter assignment, a cell cycles through a set composed of 2 different cell parameters according to the SFN of a frame, e.g. the downlink scrambling code and the basic midamble code of a cell alternate for frames with even and odd SFN. Cell parameter cycling leaves the code group of a cell unchanged. + +If the UE has received information about which cell parameters or SCH configurations to search for, cell search can be simplified. + +--- + +## Annex CA (informative): Cell search procedure for 1.28Mcps TDD + +During the initial cell search, the UE searches for a cell. It then determines the DwPTS synchronization, scrambling and basic midamble code identification, control multi-frame synchronisation and then reads the contents in BCH. This initial cell search is carried out in 4 steps: + +### Step 1: Search for DwPTS + +During the first step of the initial cell search procedure, the UE uses the SYNC-DL (in DwPTS) to acquire DwPTS synchronization to a cell. This is typically done with one or more matched filters (or any similar device) matched to the received SYNC-DL which is chosen from PN sequences set. A single or more matched filter (or any similar device) is used for this purpose. During this procedure, the UE needs to identify which of the 32 possible SYNC-DL sequences is used. + +### Step 2: Scrambling and basic midamble code identification + +During the second step of the initial cell search procedure, the UE receives the midamble of the P-CCPCH. The P-CCPCH is followed by the DwPTS. In the 1.28 Mcps TDD each DwPTS code corresponds to a group of 4 different basic midamble code. Therefore there are total 128 midamble codes and these codes are not overlapping with each other. Basic midamble code number divided by 4 gives the SYNC-DL code number. Since the SYNC-DL and the group of basic midamble codes of the P-CCPCH are related one by one (i.e, once the SYNC-DL is detected, the 4 midamble codes can be determined), the UE knows which 4 basic midamble codes are used. Then the UE can determine the used basic midamble code using a try and error technique. The same basic midamble code will be used throughout the frame. As each basic midamble code is associated with a scrambling code, the scrambling code is also known by that time. According to the result of the search for the right midamble code, UE may go to next step or go back to step 1. + +### Step 3: Control multi-frame synchronisation + +During the third step of the initial cell search procedure, the UE searches for the MIB( Master Indication Block) of multi-frame of the BCH in the P-CCPCH indicated by QPSK phase modulation of the DwPTS with respect to the P-CCPCH midamble. The control multi-frame is positioned by a sequence of QPSK symbols modulated on the DwPTS. [n] consecutive DwPTS are sufficient for detecting the current position in the control multi-frame. According to the result of the control multi-frame synchronisation for the right midamble code, UE may go to next step or go back to step 2. + +### Step 4: Read the BCH + +The (complete) broadcast information of the found cell in one or several BCHs is read. According to the result the UE may move back to previous steps or the initial cell search is finished. + +## For Dedicated Carrier MBSFN + +For the MS burst, the preamble codes (see the Table AA.1a in TS25.221) are segmented into even code group and odd code group, $P_{p,even}$ group and $P_{p,odd}$ group (see the clause 8.3Aa in TS25.223). When the preamble of the MS burst is $P_{p,odd}$ , it indicates that the next sub-frame is the beginning of the multi-frame of PCCPCH; otherwise, the preamble of MS burst uses the $P_{p,even}$ ( $P_{p,even}$ and $P_{p,odd}$ belong to the same subgroup). The preamble of MT burst is decided by the upper-layer signaling. This initial SFN cell search is carried out in 4 steps: + +### Step 1: Search for $P_{p,even}$ + +During the first step of the initial SFN cell search procedure, the UE uses the $P_{p,even}$ (in MS burst) to acquire synchronization to a SFN cell. + +### Step 2: Multi-frame synchronization + +During the second step of the initial SFN cell search procedure, the UE searches for the $P_{p,odd}$ (in MS burst) to get the beginning position of the multi-frame of PCCPCH. According to the result of multi-frame synchronization, UE may go to next step or go back to step 1. + +### Step 3: Read the BCCH + +The UE reads the MIB (Master Indication Block) of multi-frame P-CCPCHs in the BCH and gets the system information of the found SFN cell. According to the result of reading the BCCH, UE may go to next step or go back to step 2. + +#### **Step 4: Read the MCCH** + +The UE reads the MCCH indicated by the BCCH information. According to the result the UE may move back to previous steps or the initial cell search is finished. + +## Annex CB (informative): Examples random access procedure for 1.28Mcps TDD + +**Table CB.1: One PRACH, TTI=5ms, WT=4, L =1, SF4 PRACH** + +| Sub-frame Number | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | +|----------------------------|---|--------|--------|--------|--------|---|---|---|---|---|----| +| Users sending on UpPCH | | 1
2 | 3
4 | 5
6 | 7
8 | | | | | | | +| Acknowledged user on FPACH | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | +| User sending on PRACH 0 | | | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | + +User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH. + +**Table CB.2: Two PRACHs, TTI=10ms, WT=4, L =2, SF8 PRACH** + +| Sub-frame Number | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | +|----------------------------|---|--------|--------|--------|--------|---|---|---|---|---|----|--------| +| Users sending on UpPCH | | 1
2 | 3
4 | 5
6 | 7
8 | | | | | | | | +| Acknowledged user on FPACH | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | | +| User sending on PRACH 0 | | | | | | 2 | 2 | 4 | 4 | 6 | 6 | | +| User sending on PRACH 1 | | | | | | 1 | 1 | 3 | 3 | 5 | 5 | 7
7 | + +User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH. + +**Table CB.3: Four PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH** + +| Sub-frame Number | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | +|----------------------------|---|--------|--------|--------|--------|---|---|---|---|---|----|----|----|----| +| Users sending on UpPCH | | 1
2 | 3
4 | 5
6 | 7
8 | | | | | | | | | | +| Acknowledged user on FPACH | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | | | | +| User sending on PRACH 0 | | | | | | | 4 | 4 | 4 | 4 | | | | | +| User sending on PRACH 1 | | | | | | 1 | 1 | 1 | 1 | 5 | 5 | 5 | 5 | | +| User sending on PRACH 2 | | | | | | 2 | 2 | 2 | 2 | 6 | 6 | 6 | 6 | | +| User sending on PRACH 3 | | | | | | | 3 | 3 | 3 | 3 | 7 | 7 | 7 | 7 | + +User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH. + +**Table CB.4: Two PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH** + +| Sub-frame Number | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | +|----------------------------|---|---|---|---|---|---|---|---|---|---|----|----|----| +| Users sending on UpPCH | 1 | 3 | 5 | 7 | | | | | | | | | | +| | 2 | 4 | 6 | 8 | | | | | | | | | | +| Acknowledged user on FPACH | X | 1 | | | 2 | 3 | | | X | X | | | | +| User sending on PRACH 0 | | | | | | | 2 | 2 | 2 | 2 | | | | +| User sending on PRACH 1 | | | | | 1 | 1 | 1 | 1 | 3 | 3 | 3 | 3 | | + +The FPACH is used ONLY in sub-frames 0, 1, 4, 5, 8, 9, ... because they correspond to the used RACH resources. + +The FPACH in sub-frame 0 is not used because no UpPCH is preceding. + +The FPACH in sub-frames 8,9 is not used because no UpPCH is preceding in the last 4 sub-frames. + +In contrast to the previous examples users 4,5,6,7 are not granted because they would not lead to a RACH anyway. In this example their grant would come too late. + +User 8 is not granted because more than 4 sub-frames would have passed since the UpPCH. + +--- + +## Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99594 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99698 | 001 | 01 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99698 | 002 | - | Measurement procedure of received reference power for OL-TPC in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99699 | 004 | 1 | STTD capability for P-CCPCH, TDD component | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99697 | 005 | 1 | Alignment of Terminology Regarding Spreading for TDD Mode | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000070 | 003 | 2 | Cycling of cell parameters | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 007 | 2 | Clarifications on the UL synchronisation and Timing advance | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 008 | - | Modification of SIR threshold on setting TPC | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 009 | 1 | New section describing the random access procedure | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 011 | - | Removal of Synchronisation Case 3 in TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 012 | 1 | Clarifications on power control procedures | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 013 | - | Signal Point Constellation | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 014 | 2 | Out-of-sync handling for UTRA TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000070 | 015 | - | Removal of ODMA from the TDD specifications | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000274 | 016 | - | Editorial correction for the power control section in 25.224 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 017 | - | Power control for TDD during DTX | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 018 | 1 | Power Control for PDSCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 020 | 1 | Editorial modification of 25.224 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 021 | - | Clarifications on TxDiversity for UTRA TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 022 | 1 | Introduction of the TDD DSCH detection procedure in TS 25.224 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000274 | 023 | - | Downlink power control on timeslot basis | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000347 | 019 | 1 | Gain Factors for TDD Mode | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 025 | - | Terminology regarding the beacon function | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 026 | 1 | Synchronisation of timing advance adjustment and timing deviation measurement | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 027 | 1 | CCTrCH UL/DL pairing for DL inner loop power control | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 028 | 1 | RACH timing in TDD mode | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 030 | 1 | TDD Access Bursts for HOV | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 032 | - | Removal of ODMA related abbreviations and correction of references | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000347 | 033 | - | Clarifications on the Out-of-sync handling for UTRA TDD | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000544 | 035 | 1 | Radio Link establishment and sync status reporting | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000544 | 040 | - | Clarification on PICH power setting | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000544 | 042 | - | Correction to TDD timing advance description | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000544 | 043 | - | Limit on maximum value of alpha used for open loop power control | 3.4.0 | 3.5.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 036 | - | DTX and Special Burst Scheduling | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 037 | 1 | RACH random access procedure | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 045 | - | Introduction of closed-loop Tx diversity for the PDSCH and DTX for the PUSCH/PDSCH | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 046 | 2 | Corrections of TDD power control sections | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 050 | - | Use of a special burst in reconfiguration | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010065 | 053 | - | Known TFCI for the TDD special burst | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010073 | 044 | 2 | Layer 1 procedure for Node B synchronisation | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 047 | 1 | Inclusion of 1,28 Mcps TDD in TS 25.224 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010072 | 048 | 1 | Idle periods for IPDL location method | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010338 | 057 | - | Correction of Timing Advance section for 3.84 Mcps TDD | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010338 | 059 | - | Addition to the abbreviation list | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010343 | 049 | - | Clarification of IP_Frame(x) definition | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010343 | 055 | 1 | Correction of IPDL burst parameters | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010525 | 064 | 1 | Correction of criteria for OOS indication | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010531 | 060 | - | Corrections for TS 25.224 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010531 | 062 | 1 | Corrections of Annex E in 25.224 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010531 | 061 | - | Corrections and Clarifications for calculation of idle period position in subclause 4.10.3 in 25.224 | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010742 | 066 | - | Removal of the remark on power control | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010742 | 068 | 1 | Transmit Diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010742 | 070 | 1 | Correction to random access procedure (Primitive from MAC) | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010749 | 073 | 1 | Random access procedure for 1.28Mcps TDD | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010749 | 074 | - | Transmit diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010749 | 075 | - | Correction of Annex A.3 in 25.224 | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010749 | 076 | - | Removal of the remark on power control | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010749 | 077 | - | Corrections to DL-PC sections for 1.28 Mcps TDD | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020052 | 079 | 1 | Removal of quantisation of bj gain factor when calculated from a reference TFC | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020052 | 084 | 1 | TDD MAC layer subchannel assignment | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020052 | 086 | - | Transmit diversity on PICH | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020057 | 080 | - | Introduction of "UE Positioning Enhancements for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|---------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 08/03/02 | RAN_15 | RP-020055 | 082 | 1 | Introduction of "Node B synchronization for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | +| 08/03/02 | RAN_15 | RP-020058 | 081 | 1 | Power Control and Procedures for HSDPA | 4.3.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020315 | 088 | - | Clarification on power control and TxDiversity procedure for 1.28 Mcps TDD | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 089 | - | TxDiversity for HSDPA in TDD | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 090 | - | Correction to HS-SCCH Power Control (TDD) | 5.0.0 | 5.1.0 | +| 20/09/02 | RAN_17 | RP-020586 | 091 | 1 | Corrections to 25.224 for HSDPA | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020572 | 094 | 2 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020577 | 097 | 1 | Corrections to uplink synchronisation procedure | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020577 | 099 | - | Correction to the PRACH open loop power control procedure for 1.28 Mcps TDD | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020579 | 101 | 1 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 | +| 15/10/02 | - | - | - | - | Separate subclause 5.1.1.3, which was by accident merged into the header of subclause 5.1.1.4 | 5.2.0 | 5.2.1 | +| 22/12/02 | RAN_18 | RP-020854 | 102 | 1 | Corrections and clarifications to TDD CQI description | 5.2.1 | 5.3.0 | +| 22/12/02 | RAN_18 | RP-020852 | 105 | - | Editorial modification to the section numberings | 5.2.1 | 5.3.0 | +| 24/03/03 | RAN_19 | RP-030141 | 109 | 1 | Corrections to TPC Procedures During a DL Transmission Pause | 5.3.0 | 5.4.0 | +| 24/03/03 | RAN_19 | RP-030141 | 114 | 1 | Corrections to link adaptation procedure for UTRA TDD (3.84 Mcps Option) | 5.3.0 | 5.4.0 | +| 24/03/03 | RAN_19 | RP-030141 | 115 | 2 | Minimum timing requirement for CQI transmission on HS-SICH in UTRA TDD | 5.3.0 | 5.4.0 | +| 24/03/03 | RAN_19 | RP-030141 | 117 | 2 | Clarification of downlink closed loop power control procedures for 3.84 Mcps TDD | 5.3.0 | 5.4.0 | +| 24/03/03 | RAN_19 | RP-030133 | 119 | 2 | Corrections to the LCR power control procedure | 5.3.0 | 5.4.0 | +| 24/06/03 | RAN_20 | RP-030277 | 120 | - | Clarifications for the 1.28Mcps TDD power control procedure | 5.4.0 | 5.5.0 | +| 22/09/03 | RAN_21 | RP-030460 | 121 | 3 | Clarification on PDSCH Downlink Power Control Procedures | 5.5.0 | 5.6.0 | +| 22/09/03 | RAN_21 | RP-030476 | 125 | 1 | DTX and Special Bursts in case of no data on S-CCPCH and Beacon Channels | 5.5.0 | 5.6.0 | +| 06/01/04 | RAN_22 | RP-030698 | 128 | 1 | Correction to computed gain factors with signalled reference gain factor values | 5.6.0 | 5.7.0 | +| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.7.0 | 6.0.0 | +| 09/06/04 | RAN_24 | RP-040235 | 131 | 2 | Addition of TSTD for S-CCPCH in 3.84Mcps TDD | 6.0.0 | 6.1.0 | +| 07/09/04 | RAN_25 | RP-040316 | 134 | - | Transmit diversity usage for beacon channels in LCR TDD | 6.1.0 | 6.2.0 | +| 07/09/04 | RAN_25 | RP-040319 | 137 | 1 | Corrections of radio access procedure for 1.28Mcps TDD | 6.1.0 | 6.2.0 | +| 13/12/04 | RAN_26 | RP-040451 | 138 | - | Introduction of MICH | 6.2.0 | 6.3.0 | +| 13/12/04 | RAN_26 | RP-040452 | 139 | - | Introduction of MBMS soft combining for TDD | 6.2.0 | 6.3.0 | +| 14/03/05 | RAN_27 | RP-050097 | 140 | 2 | Improvements to uplink closed-loop power control for 1.28Mcps TDD | 6.3.0 | 6.4.0 | +| 14/03/05 | RAN_27 | RP-050089 | 141 | - | Release 6 HS-DSCH operation without a DL DPCH for 3.84Mcps TDD | 6.3.0 | 6.4.0 | +| 16/06/05 | RAN_28 | RP-050255 | 144 | 2 | Clarification of UpPCH Sub-channel for 1.28 Mcps TDD | 6.4.0 | 6.5.0 | +| 12/12/05 | RAN_30 | RP-050724 | 0146 | 1 | Clarify the power control procedure of HS-SCCH for TDD | 6.5.0 | 6.6.0 | +| 20/03/06 | RAN_31 | RP-060078 | 0149 | - | Introduction of the Physical Layer Common Control Channel (PLCCH) | 6.6.0 | 7.0.0 | +| 20/03/06 | RAN_31 | RP-060079 | 0150 | - | Introduction of 7.68Mcps TDD option | 6.6.0 | 7.0.0 | +| 29/09/06 | RAN_33 | RP-060497 | 0152 | - | Release 7 Timing Advance (3.84 Mcps and 7.68 Mcps TDD) | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | RP-060492 | 0153 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | - | - | - | Editorial correction for Tdoc number of CR0140R2 from RP-050096 to RP-050097 on table of history change | 7.0.0 | 7.1.0 | +| 13/03/07 | RAN_35 | RP-070118 | 0159 | 2 | Introduction of E-DCH for 1.28Mcps TDD | 7.1.0 | 7.2.0 | +| 13/03/07 | RAN_35 | RP-070113 | 0155 | 1 | Modification on the power control function of HS-SICH for LCR TDD | 7.1.0 | 7.2.0 | +| 13/03/07 | RAN_35 | RP-070113 | 0158 | 2 | Clarification of closed Loop Uplink HS-SICH Power Control for 1.28Mcps TDD | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070385 | 0160 | 1 | Support for MBSFN operation | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070386 | 0162 | 1 | Support for 1.28Mcps TDD MBSFN operation | 7.2.0 | 7.3.0 | +| 11/09/07 | RAN_37 | RP-070640 | 0164 | 1 | Improvement on the power control of E-PUCH in 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 11/09/07 | RAN_37 | RP-070650 | 0163 | 1 | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 14/09/07 | RAN_37 | RP-070726 | 0166 | 1 | Correction to the calculating formula of SIR | 7.3.0 | 7.4.0 | +| 27/11/07 | RAN_38 | RP-070942 | 0172 | - | Clarification of gain factor $\beta_e$ and $P_{e-base}$ in LCR TDD EUL | 7.4.0 | 7.5.0 | +| 27/11/07 | RAN_38 | RP-070943 | 0171 | 1 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.4.0 | 7.5.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0170 | 2 | EUL power control improvements for 1.28Mcps TDD | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0176 | - | Improvement of the UL synchronisation of E-PUCH for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0177 | 1 | Clarification and Correction of E-PUCH power control for LCR TDD | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.6.0 | 8.0.0 | +| 09/09/08 | RAN_41 | RP-080661 | 186 | 4 | HS-SCCH and HS-SICH power control clarification for 1.28Mcps | 8.0.0 | 8.1.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|----------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | | | | TDD | | | +| 09/09/08 | RAN_41 | RP-080664 | 187 | - | Use of Special Bursts for DTX on MBSFN FACH in 1.28 Mcps TDD | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 188 | - | Correction of E-PUCH power control for 1.28 Mcps TDD EUL | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 190 | 1 | Clarification of the E-AGCH monitoring for 1.28Mcps TDD EUL | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 192 | - | Correction of UpPCHPOS bit number in subclause 5.2.7 | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 193 | - | EUL power control clarification for 1.28Mcps TDD | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080661 | 194 | 1 | EUL power control improvement for 1.28Mcps TDD | 8.0.0 | 8.1.0 | +| 03/12/08 | RAN_42 | RP-080976 | 199 | 1 | Modification of HS-SICH sync description for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-080976 | 201 | 1 | Clarification of precision and quantization mode for coderate and beta of E-PUCH for 1.28Mcps TDD EUL | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-080987 | 202 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-081118 | 203 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.1.0 | 8.2.0 | +| 03/03/09 | RAN_43 | RP-090230 | 205 | - | Clarification of the beta value for smallest E-TFC of E-PUCH for 1.28Mcps TDD EUL | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090240 | 206 | 1 | Introducing of CPC for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090241 | 207 | 1 | Introducing of MIMO for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090230 | 209 | 2 | E-DCH power control clarification for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 26/05/09 | RAN_44 | RP-090533 | 210 | 1 | Clarification of HS-SICH and E-PUCH power control in semi-persistent transmission for LCR TDD | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090533 | 211 | 1 | Clarification of E-PUCH synchronization in semi-persistent transmission for LCR TDD | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090533 | 212 | 2 | Clarification of DRX operation in CPC for LCR TDD | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090526 | 216 | - | Clarification of the transmit power for E-RUCCH for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090531 | 218 | 2 | Pilot power behaviour for MBSFN IMB | 8.3.0 | 8.4.0 | +| 15/09/09 | RAN_45 | RP-090892 | 219 | 4 | Clarification on HS-DSCH procedure when using BCCH specific H-RNTI in CELL_PCH or URA_PCH state for 1.28Mcps TDD | 8.4.0 | 8.5.0 | +| 15/09/09 | RAN_45 | RP-090892 | 224 | 1 | Change the timing definition in CELL_PCH for 1.28Mcps TDD | 8.4.0 | 8.5.0 | +| 15/09/09 | RAN_45 | RP-090887 | 226 | 2 | Clarification of SNPL calculation and reporting for 1.28 Mcps TDD | 8.4.0 | 8.5.0 | +| 01/12/09 | RAN_46 | RP-091258 | 217 | 5 | Correction of Out of synchronisation handling for 1.28Mcps TDD CPC usage | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | RP-091166 | 230 | 3 | Correction on Control Channel DRX description for 1.28Mcps TDD | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | RP-091166 | 232 | 1 | Clarification of the Control Channel DRX operation for 1.28Mcps TDD | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | RP-091167 | 234 | 1 | Terminology correction for 1.28Mcps TDD standalone midamble channel | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | RP-091169 | 236 | - | Clarification of HS-DSCH channel quality indication procedure in CELL_FACH state for 1.28Mcps TDD | 8.5.0 | 8.6.0 | +| 01/12/09 | RAN_46 | - | - | - | Creation of Release 9 (v9.0.0) at RAN#46 | 8.6.0 | 9.0.0 | +| 16/03/10 | RAN_47 | RP-100201 | 244 | - | Clarification of the TPC and SS on HS-SCCH uplink synchronization establishment command for 1.28Mcps TDD | 9.0.0 | 9.1.0 | +| 16/03/10 | RAN_47 | RP-100202 | 246 | 1 | Clarification of HS-DSCH Channel Quality Indication Procedure for 1.28Mcps TDD | 9.0.0 | 9.1.0 | +| 16/03/10 | RAN_47 | RP-100201 | 248 | - | Clarification of ePCH modulation scheme | 9.0.0 | 9.1.0 | +| 14/09/10 | RAN_49 | RP-100896 | 254 | 2 | Clarification on HS-DSCH transmission in CELL_PCH or URA_PCH state for 1.28Mcps TDD | 9.1.0 | 9.2.0 | +| 07/12/10 | RAN_50 | RP-101314 | 261 | - | Correction of MC-HSDPA DRX for 1.28Mcps TDD | 9.2.0 | 9.3.0 | +| 07/12/10 | RAN_50 | RP-101316 | 263 | 2 | Clarification for special burst power calculation for 1.28Mcps TDD | 9.2.0 | 9.3.0 | +| 07/12/10 | RAN_50 | RP-101317 | 257 | 3 | Introduction of MC-HSUPA for LCR TDD | 9.3.0 | 10.0.0 | +| 07/12/10 | RAN_50 | RP-101319 | 259 | 1 | Introduction of MU-MIMO for LCR TDD | 9.3.0 | 10.0.0 | +| 15/03/11 | RAN_51 | RP-110252 | 265 | 1 | Correction of the special burst transmission power calculation for 1.28Mcps TDD | 10.0.0 | 10.1.0 | +| 01/06/11 | RAN_52 | RP-110817 | 266 | - | Clarification on SCCPCH selection for LCR TDD | 10.1.0 | 10.2.0 | +| 15/09/11 | RAN_53 | RP-111227 | 270 | 2 | Clarifications on SYNC-UL signatures for E-RUCCH procedure for LCR TDD | 10.2.0 | 10.3.0 | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.3.0 | 11.0.0 | +| 04/12/12 | RAN_58 | RP-121847 | 272 | 2 | Clarification about the frequency on which UE initiates uplink synchronization in enhanced CELL_PCH state for 1.28Mcps TDD | 11.0.0 | 11.1.0 | +| 04/12/13 | RAN_62 | RP-131895 | 273 | 1 | Introduction of HSPA signalling enhancements for more efficient resource usage for LCR TDD | 11.1.0 | 12.0.0 | +| 07/12/15 | SP_70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25225/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/25_series/25225/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd4df0752d9158ba9b0c3f6dd8b1e428f8731986 --- /dev/null +++ b/marked/Rel-16/25_series/25225/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:836935aa4bc41d49e6afb83a441aca0532c600d0ee99b4621505d2dea616243d +size 13001 diff --git a/marked/Rel-16/25_series/25225/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/Rel-16/25_series/25225/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8af17a5ee7cd1a901d319c6eadacb180718a3488 --- /dev/null +++ b/marked/Rel-16/25_series/25225/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d4221c764723f561bae84736f8cad8a6654fdcdb1c67b879deef2899d1d0554 +size 22031 diff --git a/marked/Rel-16/25_series/25225/raw.md b/marked/Rel-16/25_series/25225/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..853a06b04555fe7616a3493829d58f73b4b0e476 --- /dev/null +++ b/marked/Rel-16/25_series/25225/raw.md @@ -0,0 +1,769 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 7 | +| 4 Control of UE/UTRAN measurements ..... | 7 | +| 4.1 General measurement concept ..... | 8 | +| 4.2 Measurements for cell selection/reselection ..... | 8 | +| 4.3 Measurements for Handover ..... | 8 | +| 4.4 Measurements for DCA ..... | 8 | +| 4.5 Measurements for timing advance ..... | 8 | +| 5 Measurement abilities for UTRA TDD ..... | 9 | +| 5.1 UE measurement abilities..... | 9 | +| 5.1.1 P-CCPCH RSCP..... | 10 | +| 5.1.2 CPICH RSCP..... | 10 | +| 5.1.3 Timeslot ISCP ..... | 10 | +| 5.1.4 UTRA carrier RSSI ..... | 10 | +| 5.1.5 GSM carrier RSSI..... | 11 | +| 5.1.6 SIR..... | 11 | +| 5.1.7 CPICH Ec/No ..... | 11 | +| 5.1.8 Transport channel BLER..... | 11 | +| 5.1.9 UE transmitted power..... | 12 | +| 5.1.10 SFN-SFN observed time difference ..... | 13 | +| 5.1.11 SFN-CFN observed time difference ..... | 14 | +| 5.1.12 Observed time difference to GSM cell..... | 14 | +| 5.1.13 UE GPS Timing of Cell Frames for UE positioning ..... | 15 | +| 5.1.14 Timing Advance ( $T_{ADV}$ ) for 1.28Mcps TDD ..... | 15 | +| 5.1.15 UE GPS code phase..... | 15 | +| 5.1.16 UE transmission power headroom (1.28Mcps option only)..... | 16 | +| 5.1.17 UE transmission power headroom (3.84Mcps and 7.68Mcps options)..... | 16 | +| 5.1.18 E-UTRA RSRP..... | 17 | +| 5.1.19 E-UTRA RSRQ ..... | 17 | +| 5.1.20 IEEE 802.11 Beacon RSSI ..... | 18 | +| 5.2 UTRAN measurement abilities ..... | 18 | +| 5.2.1 RSCP ..... | 18 | +| 5.2.2 Timeslot ISCP ..... | 18 | +| 5.2.3 Received total wide band power..... | 18 | +| 5.2.4 SIR..... | 19 | +| 5.2.5 Transport channel BER ..... | 19 | +| 5.2.6 Transmitted carrier power ..... | 19 | +| 5.2.7 Transmitted code power ..... | 19 | +| 5.2.8 RX Timing Deviation..... | 20 | +| 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning ..... | 20 | +| 5.2.10 SFN-SFN observed time difference ..... | 20 | +| 5.2.11 Cell Sync Burst Timing..... | 21 | +| 5.2.12 Cell Sync Burst SIR..... | 21 | +| 5.2.13 Received SYNC-UL Timing Deviation for 1.28Mcps TDD..... | 22 | +| 5.2.14 Angle of Arrival (AOA) for 1.28Mcps TDD ..... | 22 | +| 5.2.15 HS-SICH reception quality..... | 22 | +| 5.2.16 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission..... | 23 | +| 5.2.17 UpPTS interference (1.28Mcps TDD) ..... | 23 | +| Annex A (informative): Monitoring GSM from TDD: Calculation Results..... | 24 | +| A.1 Low data rate traffic using 1 uplink and 1 downlink slot (for the 3.84 Mcps option) ..... | 24 | +| A.1.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot ..... | 25 | +| A.2 Low data rate traffic using 1 uplink and 1 downlink slot (for the 1.28 Mcps option) ..... | 26 | + +A.2.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot (for 1.28Mcps TDD)..... 27 + +Annex B (informative): Change history..... 29 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the description and definition of the measurements done at the UE and network in TDD mode in order to support operation in idle mode and connected mode. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [11] 3GPP TS 25.302: "Services provided by the Physical layer". +- [12] 3GPP TS 25.303: "UE functions and interlayer procedures in connected mode". +- [13] 3GPP TS 25.304: "UE procedures in idle mode". +- [14] 3GPP TS 25.331: "RRC Protocol Specification". +- [15] 3GPP TR 25.922: "Radio Resource Management Strategies". +- [16] 3GPP TR 25.923: "Report on Location Services (LCS)". +- [17] 3GPP TS 25.102: "UTRA (UE) TDD; Radio transmission and Reception" +- [18] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and Reception" +- [19] 3GPP TS 25.123: "Requirements for Support of Radio Resources Management (TDD)" +- [20] 3GPP TS 36.211: "E-UTRA; Physical Channels and Modulation" +- [21] 3GPP TS 36.214: "E-UTRA; Physical layer – Measurements" +- [22] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std.". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-------------------------------------------------------------------| +| BCH | Broadcast Channel | +| BCCH | Broadcast Control Channel (GSM) | +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| CFN | Connection Frame Number | +| CPICH | Common Pilot Channel (FDD) | +| CRC | Cyclic Redundancy Check | +| DCA | Dynamic Channel Allocation | +| DCH | Dedicated Channel | +| DPCH | Dedicated Physical Channel | +| Ec/No | Received energy per chip divided by the power density in the band | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| FACH | Forward Access Channel | +| FCCH | Frequency Correction Channel (GSM) | +| FDD | Frequency Division Duplex | +| GSM | Global System for Mobile Communication | +| GPS | Global Positioning System | +| ISCP | Interference Signal Code Power | +| P-CCPCH | Primary Common Control Physical Channel | +| PCH | Paging Channel | +| PLMN | Public Land Mobile Network | +| PRACH | Physical Random Access Channel | +| PDSCH | Physical Downlink Shared Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RSCP | Received Signal Code Power | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| S-CCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronisation Channel | +| SCTD | Space Code Transmit Diversity | +| SF | Spreading Factor | +| SFN | System Frame Number | +| SIR | Signal-to-Interference Ratio | +| TDD | Time Division Duplex | +| TDMA | Time Division Multiple Access | +| TrCH | Transport Channel | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| USCH | Uplink Shared Channel | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Control of UE/UTRAN measurements + +In this clause the general measurement control concept of the higher layers is briefly described to provide an understanding on how L1 measurements are initiated and controlled by higher layers. + +## 4.1 General measurement concept + +L1 provides with the measurement specifications a toolbox of measurement abilities for the UE and the UTRAN. These measurements can be differentiated in different measurement types: intra-frequency, inter-frequency, inter-system, traffic volume, quality and internal measurements (see [14]). + +In the L1 measurement specifications the measurements are distinguished between measurements in the UE (the messages will be described in the RRC Protocol) and measurements in the UTRAN (the messages will be described in the NBAP and the Frame Protocol). + +To initiate a specific measurement the UTRAN transmits a 'measurement control message' to the UE including a measurement ID and type, a command (setup, modify, release), the measurement objects and quantity, the reporting quantities, criteria (periodical/event-triggered) and mode (acknowledged/unacknowledged), see [14]. + +When the reporting criteria is fulfilled the UE shall answer with a 'measurement report message' to the UTRAN including the measurement ID and the results. + +In idle mode the measurement control message is broadcast in a System Information. + +Intra-frequency reporting events, traffic volume reporting events and UE internal measurement reporting events described in [14] define events which trigger the UE to send a report to the UTRAN. This defines a toolbox from which the UTRAN can choose the needed reporting events. + +## 4.2 Measurements for cell selection/reselection + +Whenever a PLMN has been selected the UE shall start to find a suitable cell to camp on, this is 'cell selection'. + +When camped on cell the UE regularly searches for a better cell depending on the cell reselection criteria, this is called 'cell reselection'. The procedures for cell selection and reselection are described in [13] and the measurements carried out by the UE are explained in this specification. + +## 4.3 Measurements for Handover + +For the handover preparation the UE receives from the UTRAN a list of cells (e.g. TDD, FDD or GSM), which the UE shall monitor (see 'monitored set' in [14]) in its idle timeslots. + +At the beginning of the measurement process the UE shall find synchronization to the cell to measure using the synchronization channel. This is described under 'cell search' in [9] if the monitored cell is a TDD cell and in [4] if it is an FDD cell. + +For a TDD cell to monitor after this procedure the exact timing of the midamble of the P-CCPCH is known and the measurements can be performed. Depending on the UE implementation and if timing information about the cell to monitor is available, the UE may perform the measurements on the P-CCPCH directly without prior SCH synchronisation. + +## 4.4 Measurements for DCA + +DCA is used to optimise the resource allocation by means of a channel quality criteria or traffic parameters. The DCA measurements are configured by the UTRAN. The UE reports the measurements to the UTRAN. + +For DCA no measurements are performed in idle mode in the serving TDD cell. + +When connecting with the initial access the UE immediately starts measuring the ISCP of time slots which are communicated on the BCH. The measurements and the preprocessing are done while the UTRAN assigns an UL channel for the UE for signalling and measurement reporting. + +In connected mode the UE performs measurements according to a measurement control message from the UTRAN. + +## 4.5 Measurements for timing advance + +To update timing advance of a moving UE the UTRAN measures 'Received Timing Deviation', i.e. the time difference of the received UL transmission (PRACH, DPCH, PUSCH) in relation to its timeslot structure that means in relation to the ideal case where an UL transmission would have zero propagation delay. The measurements are reported to higher layers, where timing advance values are calculated and signalled to the UE. + +# 5 Measurement abilities for UTRA TDD + +In this clause the physical layer measurements reported to higher layers. (this may also include UE internal measurements not reported over the air-interface) are defined. + +## 5.1 UE measurement abilities + +The structure of the table defining a UE measurement quantity is shown below. + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Column field | Comment | +| Definition | Contains the definition of the measurement. | +| Applicable for |

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

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

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

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

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

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

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

Type 1:
SFN-SFN observed time difference =

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

where:

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

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

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

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

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

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

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

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

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

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

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

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

| +| Applicable for |

Type 1: CELL_FACH intra

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

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

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

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

Observed time difference to GSM cell is reported as the time difference T_m in ms, where
T_m = T_{RxGSMk} - T_{RxSFN0i}
T_{RxSFN0i} = time of start (defined by the first detected path in time) of the received frame SFN=0 of the serving TDD cell i
T_{RxGSMk} = time of start of the GSM BCCH 51-multiframe of the considered target GSM frequency k received closest in time after the time T_{RxSFN0i}. If the next GSM BCCH 51-multiframe is received exactly at T_{RxSFN0i} then T_{RxGSMk} = T_{RxSFN0i} (which leads to T_m=0). The beginning of the GSM BCCH 51-multiframe is defined as the beginning of the first tail bit of the frequency correction burst in the first TDMA-frame of the GSM BCCH 51-multiframe, i.e. the TDMA-frame following the IDLE-frame.
The reference point for the Observed time difference to GSM cell shall be the antenna connector of the UE.
The reported time difference is calculated from the actual measurement in the UE. The actual measurement shall be based on:
T_{MeasGSM,j}: The start of the first tail bit of the most recently received GSM SCH on frequency j
T_{MeasSFN,i}: The start of the last frame received in TDD cell i before receiving the GSM SCH on frequency j
For calculating the reported time difference, the frame lengths are always assumed to be 10 ms for UTRA and (60/13) ms for GSM.

| +| Applicable for | Idle, URA PCH inter-RAT, CELL PCH inter-RAT, CELL_DCH Inter-RAT | + +### 5.1.13 UE GPS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | T UE-GPSj is defined as the time of occurrence of a specified UTRAN event according to GPS Time Of Week. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j P-CCPCH. The reference point for T UE-GPSj shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.14 Timing Advance (TADV) for 1.28Mcps TDD + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The 'timing advance (TADV)' is the time difference

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

Where

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

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

The reference point for the Timing Advance (TADV) shall be the antenna connector of the UE.

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

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

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

where:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The reference point for the SIR shall be the Rx antenna connector. | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.5 Transport channel BER + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The transport channel BER is an estimation of the average bit error rate (BER) of DCH or USCH data. The transport channel (TrCH) BER is measured from the data considering only non-punctured bits at the input of the channel decoder in Node B. It shall be possible to report an estimate of the transport channel BER for a TrCH after the end of each TTI of the TrCH. The reported TrCH BER shall be an estimate of the BER during the latest TTI for that TrCH. Transport channel BER is only required to be reported for TrCHs that are channel coded. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.6 Transmitted carrier power + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Where

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

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

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

Round Trip Time RTT is defined by

$RTT = UpPCH_{ADV} + UpPCH_{POS} - 8 \cdot 16 T_c$

Where

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

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

AOA defines the estimated angle of a user with respect to a reference direction. The reference direction for this measurement shall be the North, positive in a counter-clockwise direction.

The AOA is determined at the BS antenna for an UL channel corresponding to this UE. When Cell Portions are defined in the cell, the AOA for cell portion can be measured if possible.

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

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

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

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

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

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

for a given UE counted during the reporting period.

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

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

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

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

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.17 UpPTS interference (1.28Mcps TDD) + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The level of interference in the UpPTS, defined as the difference between the mean received power in the UpPTS and the sum of the estimated mean power levels of all detected UpPCH transmissions. In the case of antenna diversity, the linear average of the UpPTS interference levels calculated for each antenna branch shall be calculated. The reference point for the UpPTS interference measurement shall be the Rx antenna connector. When Cell Portions are defined in the cell, the UpPTS interference for each Cell Portion can be measured and reported to higher layers.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# Annex A (informative): Monitoring GSM from TDD: Calculation Results + +## A.1 Low data rate traffic using 1 uplink and 1 downlink slot (for the 3.84 Mcps option) + +NOTE: The section evaluates the time to acquire the FCCH if all idle slots are devoted to the tracking of a FCCH burst, meaning that no power measurements is done concurrently. The derived figures are better than those for GSM. The section does not derive though any conclusion. A conclusion may be that the use of the idle slots is a valid option. An alternative conclusion may be that this is the only mode to be used, removing hence the use of the slotted frames for low data traffic or the need for a dual receiver, if we were to considering the monitoring of GSM cells only, rather than GSM, TDD and FDD. + +If a single synthesiser UE uses only one uplink and one downlink slot, e.g. for speech communication, the UE is not in transmit or receive state during 13 slots in each frame. According to the timeslot numbers allocated to the traffic, this period can be split into two continuous idle intervals A and B as shown in the figure below. + +![Figure A.1: Possible idle periods in a frame with two occupied timeslots. The diagram shows a horizontal timeline representing a 10 ms frame, divided into 15 timeslots. The first timeslot is labeled 'Tx' (transmit) and is shaded grey. The fifth timeslot is labeled 'Rx' (receive) and is also shaded grey. The remaining 13 timeslots are white and represent idle periods. These 13 idle slots are divided into two continuous intervals: 'A' (between the Tx and Rx slots) and 'B' (between the Rx and Tx slots). A vertical line separates the 10 ms frame from the next one.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +Figure A.1: Possible idle periods in a frame with two occupied timeslots. The diagram shows a horizontal timeline representing a 10 ms frame, divided into 15 timeslots. The first timeslot is labeled 'Tx' (transmit) and is shaded grey. The fifth timeslot is labeled 'Rx' (receive) and is also shaded grey. The remaining 13 timeslots are white and represent idle periods. These 13 idle slots are divided into two continuous intervals: 'A' (between the Tx and Rx slots) and 'B' (between the Rx and Tx slots). A vertical line separates the 10 ms frame from the next one. + +**Figure A.1: Possible idle periods in a frame with two occupied timeslots** + +A is defined as the number of idle slots between the Tx and Rx slots and B the number of idle slots between the Rx and Tx slots. It is clear that $A+B=13$ time slots. + +In the scope of low cost terminals, a [0.8] ms period is supposed to be required to perform a frequency jump from UMTS to GSM. This lets possibly two free periods of $A \cdot T_s - 1.6$ ms and $B \cdot T_s - 1.6$ ms during which the mobile station can monitor GSM, $T_s$ being the slot period. + +Following table evaluates the average synchronisation time and maximum synchronisation time, where the announced synchronisation time corresponds to the time needed to find the FCCH. The FCCH is supposed to be perfectly detected meaning that the FCCH is found if it is entirely present in the monitoring window. The FCCH being found the SCH location is unambiguously known from that point. All the 13 idle slots are assumed to be devoted to FCCH tracking and the UL traffic is supposed to occupy the time slot 0. + +**Table A.1: example- of average and maximum synchronisation time with two busy timeslots per frame and with 0.8 ms switching time (\*)** + +| Downlink time slot number | Number of free TS in A | Number of free TS in B | Average synchronisation time (ms) | Maximum synchronisation time (ms) | +|---------------------------|------------------------|------------------------|-----------------------------------|-----------------------------------| +| 1 | 0 | 13 | 44 | 140 | +| 2 | 1 | 12 | 50 | 187 | +| 3 | 2 | 11 | 58 | 188 | +| 4 | 3 | 10 | 66 | 189 | +| 5 | 4 | 9 | 70 | 233 | +| 6 | 5 | 8 | 77 | 234 | +| 7 | 6 | 7 | 75 | 189 | +| 8 | 7 | 6 | 75 | 189 | +| 9 | 8 | 5 | 75 | 235 | +| 10 | 9 | 4 | 67 | 235 | +| 11 | 10 | 3 | 63 | 186 | +| 12 | 11 | 2 | 56 | 186 | +| 13 | 12 | 1 | 49 | 186 | +| 14 | 13 | 0 | 43 | 132 | + +(\*) All simulations have been performed with a random initial delay between GSM frames and UMTS frames. + +Each configuration of TS allocation described above allows a monitoring period sufficient to acquire synchronisation. + +### A.1.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot + +The minimum idle time to detect a complete FCCH burst for all possible alignments between the GSM and the TDD frame structure (called 'guaranteed FCCH detection'), assuming that monitoring happens every TDD frame, can be calculated as follows ( $t_{FCCH}$ = one GSM slot): + +$$t_{min, guaranteed} = 2 \times t_{synth} + t_{FCCH} + \frac{10ms}{13} = 2 \times t_{synth} + \frac{35ms}{26}$$ + +- (e.g for $t_{synth}=0ms$ : 3 TDD **consecutive** idle timeslots needed, for $t_{synth}=0,3ms$ : 3 slots, for $t_{synth}=0,5ms$ : 4 slots, for $t_{synth}=0,8ms$ : 5 slots). Under this conditions the FCCH detection time can never exceed the time of 660ms. +- (For a more general consideration $t_{synth}$ may be considered as a sum of all delays before starting monitoring is possible). +- For detecting SCH instead of FCCH (for a parallel search) the same equation applies. +- In the equation before the dual synthesiser UE is included if the synthesiser switching time is 0ms. + +**Table A.2: FCCH detection time for a dual synthesizer UE monitoring GSM from TDD every TDD frame** + +| occupied slots=
15-idle slots | cases | FCCH detection time in ms | | +|----------------------------------|-------|---------------------------|---------| +| | | Average | maximum | +| 2 | 105 | 37 | 189 | +| 3 | 455 | 46 | 327 | +| 4 | 1365 | 58 | 419 | +| 5 | 3003 | 72 | 501 | +| 6 | 5005 | 90 | 646 | +| 7 | 6435 | 114 | 660 | +| 8 | 6435 | 144 | 660 | +| 9 | 5005 | 175 | 660 | +| 10 | 3003 | 203 | 660 | +| 11 | 1365 | 228 | 660 | +| 12 | 455 | 254 | 660 | +| 13 | 105 | - | - | +| 14 | 15 | - | - | + +In the table above for a given number of occupied slots in the TDD mode all possible cases of distributions of these occupied TDD slots are considered (see 'cases'). For every case arbitrary alignments of the TDD and the GSM frame structure are taken into account for calculating the average FCCH detection time (only these cases are used which guarantee FCCH detection for all alignments; only the non-parallel FCCH search is reflected by the detection times in the table 2). + +The term 'occupied slots' means that the UE is not able to monitor in these TDD slots. + +For a synthesiser switching time of one or one half TDD timeslot the number of needed consecutive idle TDD timeslots is summarized in the table below: + +**Table A.3: Link between the synthesiser performance and the number of free consecutive TSs for guaranteed FCCH detection, needed for GSM monitoring** + +| One-way switching time for the synthesiser | Number of free consecutive TDD timeslots needed in the frame for a guaranteed FCCH detection | +|--------------------------------------------|----------------------------------------------------------------------------------------------| +| 1 TS (=2560 chips) | 5 | +| 0.5 TS (=1280 chips) | 4 | +| 0 (dual synthesiser) | 3 | + +## A.2 Low data rate traffic using 1 uplink and 1 downlink slot (for the 1.28 Mcps option) + +NOTE: The section evaluates the time to acquire the FCCH if all idle slots are devoted to the tracking of a FCCH burst, meaning that no power measurements is done concurrently. The derived figures are better than those for GSM. The section does not derive though any conclusion. A conclusion may be that the use of the idle slots is a valid option. An alternative conclusion may be that this is the only mode to be used, removing hence the use of the slotted frames for low data traffic or the need for a dual receiver, if we were to considering the monitoring of GSM cells only, rather than GSM, TDD and FDD. + +If a single synthesiser UE uses only one uplink and one downlink slot, e.g. for speech communication, the UE is not in transmit or receive state during 5 slots in each frame. According to the timeslot numbers allocated to the traffic, this period can be split into two continuous idle intervals A and B as shown in the figure below. + +![Diagram of a subframe showing idle periods A and B. The subframe is divided into 8 timeslots. Timeslot 1 is TX (uplink), timeslot 5 is RX (downlink). Idle periods A and B are indicated by arrows below the timeslots. A is the number of idle slots between TX and RX (timeslots 2, 3, 4). B is the number of idle slots between RX and TX (timeslots 6, 7, 8). C is the DwPTS+GP+UpPTS period at the end of the subframe.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +Diagram of a subframe showing idle periods A and B. The subframe is divided into 8 timeslots. Timeslot 1 is TX (uplink), timeslot 5 is RX (downlink). Idle periods A and B are indicated by arrows below the timeslots. A is the number of idle slots between TX and RX (timeslots 2, 3, 4). B is the number of idle slots between RX and TX (timeslots 6, 7, 8). C is the DwPTS+GP+UpPTS period at the end of the subframe. + +**Figure A.2: Possible idle periods in a subframe with two occupied timeslots** + +A is defined as the number of idle slots between the Tx and Rx slots and B the number of idle slots between the Rx and Tx slots. It is clear that $A+B=5$ time slots and C is equal to the DwPTS+GP+UpPTS. + +In the scope of low cost terminals, a [0.5] ms period is supposed to be required to perform a frequency jump from 1.28 Mcps TDD to GSM and vice versa. This lets possibly two free periods of $A \times \text{Timeslots} - 1$ ms and $B \times \text{Timeslots} + C - 1$ ms during which the mobile station can monitor GSM, Timeslots being the slot period. + +Following table evaluates the average synchronisation time and maximum synchronisation time, where the announced synchronisation time corresponds to the time needed to find the FCCH. The FCCH is supposed to be perfectly detected which means that it is entirely present in the monitoring window. The FCCH being found the SCH location is unambiguously known from that point. All the 5 idle slots and the DwPTS+GP+UpPTS are assumed to be devoted to FCCH tracking and the UL traffic is supposed to occupy the time slot 1. + +**Table A.4: example- of average and maximum synchronisation time with two busy timeslots per sub-frame and with 0.5 ms switching time** + +| Downlink time slot number | Number of free Timeslots in A | Number of free Timeslots in B | Average synchronisation time (ms) | Maximum synchronisation time (ms) | +|---------------------------|-------------------------------|-------------------------------|-----------------------------------|-----------------------------------| +| 0 | 5 | 0 | 83 | 231 | +| 2 | 0 | 5 | 75 | 186 | +| 3 | 1 | 4 | 98 | 232 | +| 4 | 2 | 3 | 185 | 558 | +| 5 | 3 | 2 | 288 | 656 | +| 6 | 4 | 1 | 110 | 371 | + +(\*) All simulations have been performed with a random initial delay between GSM frames and 1.28Mcps TDD sub-frames. + +Each configuration of Timeslots allocation described above allows a monitoring period sufficient to acquire synchronisation. + +NOTE: Considering about the frame structure of 1.28Mcps TDD, there are total 7 timeslots in each sub-frame that can be used as data traffic. If more than 1 uplink and/or 1 downlink TDD timeslot are used for data traffic, that means it will occupy at least 3 time slots, equal to $0.675 \times 3 = 2.025\text{ms}$ . And more time slots for traffic data means more switching point are needed to switch between the GSM and the 1.28Mcps TDD. As it was mentioned above, each switching will take 0.5ms. As a result, the idle time left for monitoring the GSM will be very little. So monitoring GSM from 1.28Mcps TDD under this situation will be considered in the future. It will need more carefully calculation and simulation. + +### A.2.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot (for 1.28Mcps TDD) + +The minimum idle time to detect a complete FCCH burst for all possible alignments between the GSM and the 1.28Mcps TDD frame structure (called 'guaranteed FCCH detection'), assuming that monitoring happens every sub-frame, can be calculated as follows ( $t_{\text{FCCH}}$ = one GSM slot): + +$$t_{\text{min, guaranteed}} = 2 \times t_{\text{synth}} + t_{\text{FCCH}} + \frac{5\text{ms}}{13} = 2 \times t_{\text{synth}} + \frac{25\text{ms}}{26}$$ + +- (e.g for $t_{\text{synth}} = 0\text{ms}$ : 2 1.28Mcps TDD **consecutive** idle timeslots needed, for $t_{\text{synth}} = 0.3\text{ms}$ : 3 slots (or 2 slots and the DwPTS+GP+UpPTS), for $t_{\text{synth}} = 0.5\text{ms}$ : 3 slots, for $t_{\text{synth}} = 0.8\text{ms}$ : 4 slots). Under this conditions the FCCH detection time can never exceed the time of 660ms. +- (For a more general consideration $t_{\text{synth}}$ may be considered as a sum of all delays before starting monitoring is possible). +- For detecting SCH instead of FCCH (for a parallel search) the same equation applies. +- In the equation before the dual synthesiser UE is included if the synthesiser switching time is 0ms. + +**Table A.5 : FCCH detection time for a single synthesizer UE monitoring GSM from 1.28Mcps TDD every sub-frame** + +| Occupied Slots | Cases | AVERAGE FCCH detection time in ms | MAXIMUM FCCH detection time in ms | +|----------------|-------|-----------------------------------|-----------------------------------| +| 2 | 21 | 136.625 | 660.785 | +| 3 | 35 | 188.451 | 660.785 | +| 4 | 35 | 231.115 | 660.785 | +| 5 | 21 | - | - | +| 6 | 7 | - | - | +| 7 | 1 | - | - | + +The result in the above table is based on the following assumption: + +- A single synthesizer is used. +- A [0.5] ms period is supposed to be required to perform a frequency jump from 1.28Mcps TDD to GSM and vice versa. +- For a given number of occupied slots in the TDD mode all possible cases of distributions of these occupied TDD slots are considered (see 'cases'). For every case arbitrary alignments of the TDD and the GSM frame structure are taken into account for calculating the average FCCH detection time (only these cases are used which guarantee FCCH detection for all alignments; only the non-parallel FCCH search is reflected by the detection times in the above table). + +The term 'occupied slots' means that the UE is not able to monitor in these TDD slots. + +For a synthesiser switching time of one or one half TDD timeslot the number of needed consecutive idle TDD timeslots is summarized in the table below: + +**Table A.6 : Link between the synthesiser performance and the number of free consecutive Timeslots for guaranteed FCCH detection, needed for GSM monitoring** + +| One-way switching time for the synthesiser | Number of free consecutive 1.28Mcps TDD timeslots needed in the sub-frame for a guaranteed FCCH detection | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| 1 Timeslot (=864 chips) | 4 | +| 0.5 Timeslot (=432 chips) | 3 | +| 0 (dual synthesiser) | 2 | + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99595 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99700 | 001 | 1 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99701 | 002 | 1 | Block STTD capability for P-CCPCH, TDD component | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99700 | 003 | 1 | Update concerning measurement definitions, ranges and mappings | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000071 | 004 | 1 | Correction of CPICH measurements and 'RX Timing Deviation' range | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000071 | 005 | 2 | Editorial modifications to 25.225 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000071 | 006 | 1 | Corrections to 25.225 Measurements for TDD | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000275 | 009 | - | Clarifications on TxDiversity for UTRA TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000275 | 010 | - | Removal of Range/mapping | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000275 | 011 | - | Removal of transport channel BLER | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000348 | 012 | 1 | Alignment of TDD measurements with FDD : GPS related measurements | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 013 | 1 | Alignment of TDD measurements with FDD :SFN-CFN observed time difference | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 014 | - | Clarification of the Timeslot ISCP measurements | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 015 | - | Terminology regarding the beacon function | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 016 | - | Removal of Physical Channel BER | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 017 | - | Update of TS25.225 due to recent change for FDD: Reporting of UTRAN TX carrier power | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000545 | 018 | 2 | Corrections and Clarifications to 25.225 | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 019 | 1 | Corrections and Clarifications to 25.225 | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 020 | 1 | Clarification of measurement reference points | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 021 | - | Removal of incorrect note relating to RSCP measurements | 3.4.0 | 3.5.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010066 | 023 | - | Correction of the observed time difference to GSM measurement | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010073 | 022 | - | Measurements for Node B synchronisation | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 024 | 1 | Inclusion of 1.28Mcps TDD in TS 25.225 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010072 | 025 | - | RTD measurement in UTRAN for UP-TDD | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010339 | 029 | - | Renaming of LCS measurements | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010339 | 030 | - | Addition to the abbreviation list | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010526 | 034 | - | Clarification of the Beacon Measurement in TS25.225 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010707 | 031 | 1 | RxTiming Deviation for 1.28 Mcps TDD | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010532 | 032 | - | SFN-SFN type 1 for 1.28 Mcps TDD | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010743 | 036 | 1 | Removal of references to Block STTD | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010743 | 040 | - | Correction of measurement definition for UTRA Carrier RSSI and CPICH_Ec/No | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010750 | 038 | 1 | Introduction of new "UE GPS code phase" measurement | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010750 | 042 | - | Corrections in annex A.2 in TS 25.225 | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020055 | 041 | 1 | Introduction of "Node B synchronization for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | +| 08/03/02 | RAN_15 | RP-020057 | 043 | - | Introduction of "UE Positioning Enhancements for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020312 | 050 | 2 | Clarification of UE measurements Applicability | 5.0.0 | 5.1.0 | +| 20/09/02 | RAN_17 | RP-020578 | 053 | - | Correction to SFN-SFN Type 2 measurement | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020558 | 061 | - | Correction of UE SFN-SFN type 1 measurement for TDD | 5.1.0 | 5.2.0 | +| 22/12/02 | RAN_18 | RP-020844 | 064 | - | Received Total Wide Band Power Measurement Definition | 5.2.0 | 5.3.0 | +| 24/03/03 | RAN_19 | RP-030080 | 065 | 2 | Addition of HS-SICH quality measurement for UTRA TDD | 5.3.0 | 5.4.0 | +| 24/06/03 | RAN_20 | RP-030366 | 070 | 1 | Power Measurement in non HSDPA codes for TDD | 5.4.0 | 5.5.0 | +| 24/06/03 | RAN_20 | RP-030365 | 074 | - | Correction of transmitted carrier power definition in case of Tx diversity | 5.4.0 | 5.5.0 | +| 06/01/04 | RAN_22 | RP-030651 | 071 | 4 | Definition of Transmitted Code Power and ISCP measurements in the case of antenna diversity for TDD | 5.5.0 | 5.6.0 | +| 13/01/04 | RAN_22 | - | - | - | created for M.1457 update | 5.6.0 | 6.0.0 | +| 23/03/04 | RAN_23 | RP-040088 | 069 | 1 | Interference measurement in UpPTS for 1.28Mcps TDD | 6.0.0 | 6.1.0 | +| 23/03/04 | RAN_23 | RP-040084 | 078 | 1 | Clarification of TA definition for 1.28Mcps TDD | 6.0.0 | 6.1.0 | +| 20/03/06 | RAN_31 | RP-060079 | 0079 | - | Introduction of 7.68Mcps TDD option | 6.1.0 | 7.0.0 | +| 12/06/06 | RAN_32 | RP-060294 | 0081 | - | Clarify the reference point for LCR TDD TA | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | RP-060492 | 0083 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.1.0 | 7.2.0 | +| 07/03/07 | RAN_35 | RP-070120 | 087 | - | Physical layerspecification of UE Power Headroom measurement | 7.2.0 | 7.3.0 | +| 07/03/07 | RAN_35 | RP-070118 | 086 | - | Introduction of E-DCH for 1.28Mcps TDD | 7.2.0 | 7.3.0 | +| 13/03/07 | RAN_35 | RP-070113 | 085 | 1 | Modification on the HS-SICH reception quality of HS-SICH for LCR TDD | 7.2.0 | 7.3.0 | +| 11/09/07 | RAN_37 | RP-070650 | 088 | - | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.4.0 | 8.0.0 | +| 09/09/08 | RAN_41 | RP-080667 | 0089 | - | E-UTRA measurements for UTRA TDD – E-UTRA interworking | 8.0.0 | 8.1.0 | +| 03/03/09 | RAN_43 | RP-090232 | 0091 | 2 | RSRP and RSRQ Measurement Definitions | 8.1.0 | 8.2.0 | +| 15/09/09 | RAN_45 | RP-090888 | 0092 | - | Clarification on reference point of RSRP and RSRQ for EUTRA | 8.2.0 | 8.3.0 | +| 15/09/09 | RAN_45 | RP-090891 | 0093 | - | Clarification of UE measurement definitions for RX diversity of LCR TDD | 8.2.0 | 8.3.0 | +| 01/12/09 | RAN_46 | RP-091175 | 0094 | 3 | Introduction of Cell Portion for 1.28 Mcps TDD | 8.3.0 | 9.0.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 16/03/10 | RAN_47 | RP-100205 | 0095 | 1 | Modification of RSRQ definition | 9.0.0 | 9.1.0 | +| 01/06/10 | RAN_48 | RP-100584 | 0098 | - | Correction to the reference table number for nominal maximum output power for 1.28Mcps TDD | 9.1.0 | 9.2.0 | +| 07/12/10 | RAN_50 | RP-101317 | 0099 | 2 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.2.0 | 10.0.0 | +| 01/06/11 | RAN_52 | RP-110817 | 0101 | 2 | Introduction of Cell Portion in AOA measurement for LCR TDD | 10.0.0 | 10.1.0 | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | +| 10/09/14 | RAN_65 | RP-141484 | 0104 | - | Inclusion of definition of WLAN Beacon RSSI in UMTS specifications | 11.0.0 | 12.0.0 | +| 09/03/15 | RAN_67 | RP-150361 | 0103 | 3 | New E-UTRA RSRQ measurement definition | 12.0.0 | 12.1.0 | +| 07/12/15 | SP_70 | - | - | - | Creation of Release 13 further to SP_70 decision | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25302/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/25_series/25302/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb735b492cf9559f067321f74f8552c7dab4127d --- /dev/null +++ b/marked/Rel-16/25_series/25302/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000e52a5f1a865521f62321f3a7b0844e3aae45e7a8b76f75f93001e35c67ed6 +size 21432 diff --git a/marked/Rel-16/25_series/25302/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-16/25_series/25302/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa1a3827d9fc09ce351670a9f2f5b07dd8576333 --- /dev/null +++ b/marked/Rel-16/25_series/25302/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:812c26a071530980cd855bf21fee825069de6a61b840b4c689a6a50db9a1feb2 +size 65443 diff --git a/marked/Rel-16/25_series/25302/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-16/25_series/25302/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db637a5312c9817db5ca2015d365b9c3fafefe3e --- /dev/null +++ b/marked/Rel-16/25_series/25302/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:475147720e76871ca611fd00a46a6dcd53dc5df24105a8aaec14ce9b8181f640 +size 62759 diff --git a/marked/Rel-16/25_series/25302/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-16/25_series/25302/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c17d9db9e6fd56d635e878a87017f7d4b21e4aff --- /dev/null +++ b/marked/Rel-16/25_series/25302/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a93a04f2072e6aea529a363fc77911818246eb101da01588f96d4ddd05aa66f +size 27248 diff --git a/marked/Rel-16/25_series/25302/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/25_series/25302/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4af3ae6e96b12307da4c4cd18067060c970f3c5 --- /dev/null +++ b/marked/Rel-16/25_series/25302/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7689c9250b60b47d7dfeb5cdcd2330866951881252dea41d44dd93cf1813d6a +size 102624 diff --git a/marked/Rel-16/25_series/25302/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/25_series/25302/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f12d05bec631ccc24e3daf7fb4b99a12e73ea968 --- /dev/null +++ b/marked/Rel-16/25_series/25302/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59443348eee066e34d23df8da8ca3817fceba64869d4819c7889ab397a492b1b +size 38009 diff --git a/marked/Rel-16/25_series/25302/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/25_series/25302/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80097b10c71b54a5b31979fd316b18da2109244c --- /dev/null +++ b/marked/Rel-16/25_series/25302/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8467815b374fa77d5357fc552a6f929b14463f13ebc68246b1a5e6246262a416 +size 51046 diff --git a/marked/Rel-16/25_series/25302/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/25_series/25302/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f541d677cb7313fe3195b9ecd43acd99952f6ec9 --- /dev/null +++ b/marked/Rel-16/25_series/25302/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9489d50e9534699d30cba4d3d71d967544c7ba29d551fe17fa3b9747a5196293 +size 29677 diff --git a/marked/Rel-16/25_series/25302/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/25_series/25302/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fab8b1605211882051df60951f6a7984d2f74a5c --- /dev/null +++ b/marked/Rel-16/25_series/25302/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1b6720532d3e10461925c4531159f77e122314c71b6b1b22a436d14e34851fe +size 39213 diff --git a/marked/Rel-16/25_series/25302/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25302/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df7f5241878e9c6ff420b8a672010d78ab04c25c --- /dev/null +++ b/marked/Rel-16/25_series/25302/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d0ceffd8cc8cd7eca350471ffe425241431874c2428bbb58b7fc435df8786d6 +size 16672 diff --git a/marked/Rel-16/25_series/25302/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/25_series/25302/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29b89d679592919aa89d109cae4a7df2bca7980a --- /dev/null +++ b/marked/Rel-16/25_series/25302/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b416110f2095248228ed0127fb553de087e04adc46e57c9a8584acc307209c4d +size 44396 diff --git a/marked/Rel-16/25_series/25302/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/25_series/25302/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2d6c807c00637d2842282cbe8ede16c627e6a43 --- /dev/null +++ b/marked/Rel-16/25_series/25302/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f286034e0e97f076ead1d4d75f402a1baa4a9b5a4c612baed5a4c17b6df39922 +size 26152 diff --git a/marked/Rel-16/25_series/25302/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/25_series/25302/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42df8717e9299d94c45ea1fdba98b6312ece2999 --- /dev/null +++ b/marked/Rel-16/25_series/25302/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a69151360794d85ab6c95051bc36495da20238bbc30233e375b764e9669678d +size 26620 diff --git a/marked/Rel-16/25_series/25302/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/25_series/25302/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d02afab4d3787b1ee9cd0421aa56df25e1e5f47 --- /dev/null +++ b/marked/Rel-16/25_series/25302/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7ea30e52dc027ef447fb9417118e74bdc376f6f66e58be14227dd27ec2b2f86 +size 41164 diff --git a/marked/Rel-16/25_series/25302/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-16/25_series/25302/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ed4e5ddb3d514bd34afadc59e91dd6c0927478 --- /dev/null +++ b/marked/Rel-16/25_series/25302/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eba3ae06011c224bddef76f2624b36742865759e6a3ade4970fe1231e5e99afe +size 21158 diff --git a/marked/Rel-16/25_series/25302/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-16/25_series/25302/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efbd2bb84f9ea88f84000a42eb64621cb8ae59e2 --- /dev/null +++ b/marked/Rel-16/25_series/25302/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f18100f5d671faa5cdce188701e9724868f46bc82a3edd87f64fba88e8c971a +size 19665 diff --git a/marked/Rel-16/25_series/25302/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/25_series/25302/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3970d18454838d212f8733e5210b2186618449f3 --- /dev/null +++ b/marked/Rel-16/25_series/25302/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3671a98dba08cd00f7bff751bac806ff838f59bb4f875841d53304aee99e6f50 +size 94049 diff --git a/marked/Rel-16/25_series/25302/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/25_series/25302/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d36c032da61ea08484075534ab5272a11c5e5b45 --- /dev/null +++ b/marked/Rel-16/25_series/25302/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9586b0d2b4e297ab37578b35e19b0610f4cd184b4631da294b03c89d303a48 +size 44529 diff --git a/marked/Rel-16/25_series/25302/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/25_series/25302/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299c14b72bca0b6e3f8380141d74aa1be406b289 --- /dev/null +++ b/marked/Rel-16/25_series/25302/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7563eab976248f792a4e0b5e58894115d6e67e0ae7943a4b7854630b5f41197 +size 26077 diff --git a/marked/Rel-16/25_series/25302/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/25_series/25302/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b1d0859a258209a998db2491783df22479d2b30 --- /dev/null +++ b/marked/Rel-16/25_series/25302/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5747d5388a82a0066d5d8d48abb16a9606a8ca5afb838adb73e024e4d51c7c1e +size 13084 diff --git a/marked/Rel-16/25_series/25302/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25302/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a013f16cee24457a881a86d5355fde2bfcc3b363 --- /dev/null +++ b/marked/Rel-16/25_series/25302/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3141f11a51d1c88085e808ecde305ebe957288eb86b45b062f2327c5964b0fab +size 33879 diff --git a/marked/Rel-16/25_series/25302/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/25_series/25302/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55ac621860957e334e823937c810d676a8e8e7e8 --- /dev/null +++ b/marked/Rel-16/25_series/25302/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e308e7f30f4433500fa410ce35faac58b8f6d1a5b99a06fd65e0c78352b7b61 +size 62464 diff --git a/marked/Rel-16/25_series/25302/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25302/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..455d3e13fd4d0e5cef99aa44a8ef0415194b3d06 --- /dev/null +++ b/marked/Rel-16/25_series/25302/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3742009381c665baac96c3bd2eb2d7eaee0430c30c61b65972ee219a73e460eb +size 51356 diff --git a/marked/Rel-16/25_series/25302/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/25_series/25302/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..018d8e098a8677b588580ac634b3d0b7a71d8ad9 --- /dev/null +++ b/marked/Rel-16/25_series/25302/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a523999d5596cafcec2464a21b34a313c6cea23dc04d62772d07b498d43e0dd8 +size 50472 diff --git a/marked/Rel-16/25_series/25302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/25_series/25302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adaaec5205a3c64115b4db3fa256d9887acaef87 --- /dev/null +++ b/marked/Rel-16/25_series/25302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:696907fb7c2fbb65d3a36d4210382415333b54a375c3938b5bcf5d3ee8f74e0b +size 26383 diff --git a/marked/Rel-16/25_series/25302/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/25_series/25302/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f3b733bfdfba0a584a0c821961044e5cd70b8ce --- /dev/null +++ b/marked/Rel-16/25_series/25302/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7372f133000c9a231e0fa82c14b2d668ba25e40a9fde994e24c7ba225bd797ed +size 58730 diff --git a/marked/Rel-16/25_series/25302/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-16/25_series/25302/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..669a81e187aa9c2a0d69f2266ed936ded52f8b33 --- /dev/null +++ b/marked/Rel-16/25_series/25302/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cbd0ff5439d047333253039360761acb2cfc25719eb35be47487ea92238c744 +size 51941 diff --git a/marked/Rel-16/25_series/25302/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/25_series/25302/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adc5d419113e7e7fa395a44a730766a499d587d1 --- /dev/null +++ b/marked/Rel-16/25_series/25302/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13b74b6374d6591c9c7a1744b6e62713a04f589202a284a4f057ea9e2ed68334 +size 21821 diff --git a/marked/Rel-16/25_series/25302/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/25_series/25302/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34e347c7f2fc8fab4c9be00fea88cb554ff72d9f --- /dev/null +++ b/marked/Rel-16/25_series/25302/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781fc1f6182dc42b9980b80c16f4a18d4f2e827bf9b5ac013cea64df8e69683f +size 43051 diff --git a/marked/Rel-16/25_series/25302/c64555b7f91435b01997807dbb4bcc4c_img.jpg b/marked/Rel-16/25_series/25302/c64555b7f91435b01997807dbb4bcc4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bdaf08aba9d16489548795e23217727f78c26b2 --- /dev/null +++ b/marked/Rel-16/25_series/25302/c64555b7f91435b01997807dbb4bcc4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecc411200faa9d561738a491140cb2c31f6b8492060a37f96767d14337dfd1cd +size 28726 diff --git a/marked/Rel-16/25_series/25302/c80dd550f724de455f5efebaed25198d_img.jpg b/marked/Rel-16/25_series/25302/c80dd550f724de455f5efebaed25198d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54681112e3cabf4b12e3e0c455237a8736c3c8b8 --- /dev/null +++ b/marked/Rel-16/25_series/25302/c80dd550f724de455f5efebaed25198d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24e47352396e5aa69cbb65d125632db04c2c262fce6370a37d272e31d55e0433 +size 16504 diff --git a/marked/Rel-16/25_series/25302/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/25_series/25302/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..598b74c9c3f4c4d8cd42ab9aa26a887f2eedb22a --- /dev/null +++ b/marked/Rel-16/25_series/25302/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:935352908f0cbae56b97ee5103969239ca9e7d58f2fa7c1d20fbd78868fedd94 +size 45592 diff --git a/marked/Rel-16/25_series/25302/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/25_series/25302/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49000c8017150b01bff6f6aba981fb33432529d8 --- /dev/null +++ b/marked/Rel-16/25_series/25302/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:306ce6aee64ca459a634a35bca46b1fc69e45f735dacd2f57f1e88022554c411 +size 31511 diff --git a/marked/Rel-16/25_series/25302/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/25_series/25302/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..681d801dd5aedf15709de6a92256876ace5dc210 --- /dev/null +++ b/marked/Rel-16/25_series/25302/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34ff1a30409fd43bf2fc1aa6aeaf9b78577da29ff679aafa7c97c4e1043688a4 +size 27231 diff --git a/marked/Rel-16/25_series/25302/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/25_series/25302/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1cf8d48df73e62f8afe0684719acf1420d7aa68 --- /dev/null +++ b/marked/Rel-16/25_series/25302/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af880798707c729b7a8b5771b9bfe9ce913c73b6e93e716ff6ef4ca7a019149c +size 21816 diff --git a/marked/Rel-16/25_series/25302/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-16/25_series/25302/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71883f06a5a59663f68d7d3f108091fe2a05e0ea --- /dev/null +++ b/marked/Rel-16/25_series/25302/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97208c303a5cced6c9429ab6ddc9db702567626b8099ed038e5259d511af520a +size 25298 diff --git a/marked/Rel-16/25_series/25302/raw.md b/marked/Rel-16/25_series/25302/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3718be0c99d6ed4534434a3e6ec98010faf715bf --- /dev/null +++ b/marked/Rel-16/25_series/25302/raw.md @@ -0,0 +1,3439 @@ + + +--- + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|--------------------------------------------------------------------|----| +| Foreword..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations..... | 10 | +| 4 Interfaces to the physical layer..... | 11 | +| 4.1 Interface to MAC..... | 12 | +| 4.2 Interface to RRC..... | 12 | +| 5 Services and functions of the physical layer..... | 12 | +| 5.1 General..... | 12 | +| 5.2 Overview of L1 functions..... | 13 | +| 5.3 L1 interactions with L2 retransmission functionality..... | 13 | +| 6 Model of physical layer of the UE..... | 14 | +| 6.1 Uplink models..... | 14 | +| 6.2 Downlink models..... | 19 | +| 7 Formats and configurations for L1 data transfer..... | 34 | +| 7.1 General concepts about Transport Channels..... | 34 | +| 7.1.1 Transport Block..... | 35 | +| 7.1.2 Transport Block Set..... | 35 | +| 7.1.3 Transport Block Size..... | 35 | +| 7.1.4 Transport Block Set Size..... | 35 | +| 7.1.5 Transmission Time Interval..... | 35 | +| 7.1.6 Transport Format..... | 36 | +| 7.1.6a Transport Format for HS-DSCH..... | 37 | +| 7.1.7 Transport Format for E-DCH..... | 37 | +| 7.1.7a Transport Format Set..... | 38 | +| 7.1.8 Transport Format Combination..... | 39 | +| 7.1.9 Transport Format Combination Set..... | 39 | +| 7.1.10 Transport Format Indicator (TFI)..... | 40 | +| 7.1.11 Transport Format Combination Indicator (TFCI)..... | 40 | +| 7.1.12 Rate matching..... | 40 | +| 7.1.13 HARQ information..... | 41 | +| 7.1.14 Transport Format and Resource Indication (TFRI)..... | 41 | +| 7.1.15 E-DCH Transport Format Combination Indication (E-TFCI)..... | 41 | +| 7.2 Types of Transport Channels..... | 41 | +| 7.3 Compressed Mode..... | 44 | +| 8 UE Simultaneous Physical Channels combinations..... | 44 | +| 8.1 FDD Uplink..... | 45 | +| 8.2 FDD Downlink..... | 49 | +| 8.3 TDD Uplink..... | 65 | +| 8.3.1 3.84/7.68 Mcps TDD Uplink..... | 65 | +| 8.3.2 1.28 Mcps TDD Uplink..... | 67 | +| 8.4 TDD Downlink..... | 69 | +| 8.4.1 3.84/7.68 Mcps TDD Downlink..... | 69 | +| 8.4.2 1.28 Mcps TDD Downlink..... | 70 | +| 8.4.3 3.84 Mcps TDD IMB Downlink..... | 75 | +| 9 Measurements provided by the physical layer..... | 75 | +| 9.1 Model of physical layer measurements..... | 76 | +| 9.2 UE Measurements..... | 77 | +| 9.2.1 SFN-CFN observed time difference..... | 77 | +| 9.2.2 Void..... | 77 | +| 9.2.3 CPICH E b /N 0 ..... | 78 | + +| | | | +|--------|-------------------------------------------------------------------------------------------------------------------|----| +| 9.2.4 | Void..... | 78 | +| 9.2.5 | CPICH RSCP..... | 78 | +| 9.2.6 | P-CCPCH RSCP..... | 78 | +| 9.2.7 | Timeslot ISCP..... | 78 | +| 9.2.8 | Void..... | 78 | +| 9.2.9 | SIR..... | 78 | +| 9.2.10 | UTRA carrier RSSI..... | 79 | +| 9.2.11 | GSM carrier RSSI..... | 79 | +| 9.2.12 | Transport channel BLER..... | 79 | +| 9.2.13 | UE transmitted power..... | 79 | +| 9.2.14 | UE Rx-Tx time difference..... | 79 | +| 9.2.15 | SFN-SFN Observed time difference..... | 80 | +| 9.2.16 | UE GPS Timing of Cell Frames for UE positioning..... | 80 | +| 9.2.17 | Timing Advance ( $T_{ADV}$ ) for 1.28 Mcps TDD..... | 80 | +| 9.2.18 | UE GPS code phase..... | 80 | +| 9.2.19 | UE GANSS Timing of Cell Frames for UE positioning..... | 81 | +| 9.2.20 | UE GANSS code measurement..... | 81 | +| 9.2.21 | UE transmission power headroom..... | 81 | +| 9.3 | UTRAN Measurements..... | 81 | +| 9.3.1 | Received total wide band power..... | 81 | +| 9.3.2 | Transmitted carrier power..... | 82 | +| 9.3.3 | Transmitted code power..... | 82 | +| 9.3.4 | Void..... | 82 | +| 9.3.5 | Physical channel BER..... | 82 | +| 9.3.6 | Transport channel BER..... | 82 | +| 9.3.7 | RX timing deviation..... | 82 | +| 9.3.8 | Timeslot ISCP..... | 83 | +| 9.3.9 | RSCP..... | 83 | +| 9.3.10 | Round Trip Time..... | 83 | +| 9.3.11 | Void..... | 83 | +| 9.3.12 | Acknowledged PRACH preambles..... | 83 | +| 9.3.13 | Void..... | 83 | +| 9.3.14 | Void..... | 83 | +| 9.3.15 | SIR..... | 84 | +| 9.3.16 | PRACH Propagation Delay..... | 84 | +| 9.3.17 | UTRAN GPS Timing of Cell Frames for UE positioning..... | 84 | +| 9.3.18 | SIR ERROR..... | 84 | +| 9.3.19 | Received SYNC_UL Timing Deviation..... | 84 | +| 9.3.20 | Cell Sync Burst Timing..... | 85 | +| 9.3.21 | Cell Sync Burst SIR..... | 85 | +| 9.3.22 | SFN-SFN Observed time difference..... | 85 | +| 9.3.23 | Angle of Arrival (AOA) for 1.28 Mcps TDD..... | 85 | +| 9.3.24 | HS-SICH reception quality..... | 85 | +| 9.3.25 | Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission..... | 86 | +| 9.3.26 | UpPTS interference (1.28Mcps TDD)..... | 86 | +| 9.3.27 | DL Transmission Branch Load..... | 86 | +| 9.3.28 | Received scheduled E-DCH power share (RSEPS)..... | 87 | +| 9.3.29 | UTRAN GANSS Timing of Cell Frames for UE positioning..... | 87 | +| 9.3.30 | Common E-DCH resource usage..... | 88 | +| 10 | Primitives of the physical layer..... | 88 | +| 10.1 | Generic names of primitives between layers 1 and 2..... | 89 | +| 10.1.1 | PHY-Access-REQ..... | 89 | +| 10.1.2 | PHY-Access-CNF..... | 90 | +| 10.1.3 | PHY-Data-REQ..... | 90 | +| 10.1.4 | PHY-Data-IND..... | 90 | +| 10.1.5 | Void..... | 91 | +| 10.1.6 | Void..... | 91 | +| 10.1.7 | PHY-Status-IND..... | 91 | +| 10.2 | Generic names of primitives between layers 1 and 3..... | 91 | +| 10.2.1 | STATUS PRIMITIVES..... | 91 | + +| | | | +|-----------|-------------------------------------------------------|-----| +| 10.2.1.1 | CPHY-Sync-IND..... | 91 | +| 10.2.1.2 | CPHY-Out-of-Sync-IND..... | 92 | +| 10.2.1.3 | CPHY-Measurement-REQ..... | 92 | +| 10.2.1.4 | CPHY-Measurement-IND..... | 92 | +| 10.2.1.5 | CPHY-Error-IND..... | 92 | +| 10.2.1.6 | Void..... | 92 | +| 10.2.2 | CONTROL PRIMITIVES..... | 92 | +| 10.2.2.1 | CPHY-TrCH-Config-REQ..... | 93 | +| 10.2.2.2 | CPHY-TrCH-Config-CNF..... | 93 | +| 10.2.2.3 | CPHY-TrCH-Release-REQ..... | 93 | +| 10.2.2.4 | CPHY-TrCH-Release-CNF..... | 93 | +| 10.2.2.5 | CPHY-RL-Setup-REQ..... | 93 | +| 10.2.2.6 | CPHY-RL-Setup-CNF..... | 93 | +| 10.2.2.7 | CPHY-RL-Release-REQ..... | 93 | +| 10.2.2.8 | CPHY-RL-Release-CNF..... | 93 | +| 10.2.2.9 | CPHY- RL-Modify-REQ..... | 94 | +| 10.2.2.10 | CPHY-RL-Modify-CNF..... | 94 | +| 10.2.2.11 | CPHY-Commit-REQ..... | 94 | +| 10.2.2.12 | Void..... | 94 | +| 10.2.2.13 | Void..... | 94 | +| 10.2.2.14 | Void..... | 94 | +| 10.2.2.15 | Void..... | 94 | +| 10.2.2.16 | CPHY-Out-of-Sync-Config-REQ..... | 94 | +| 10.2.2.17 | CPHY-Out-of-Sync-Config-CNF..... | 94 | +| 10.2.2.18 | CPHY-MBMS-Config-REQ..... | 95 | +| 10.2.2.19 | CPHY-MBMS-Config-CNF..... | 95 | +| 10.3 | Parameter definition..... | 95 | +| 10.3.1 | Error code..... | 95 | +| 10.3.2 | Event value..... | 95 | +| 10.3.3 | Access Information..... | 95 | +| 10.3.4 | Transport Format Subset..... | 95 | +| 10.3.5 | Physical channel description..... | 96 | +| 10.3.5.1 | Primary SCH..... | 96 | +| 10.3.5.2 | Secondary SCH..... | 96 | +| 10.3.5.3 | Primary CCPCH..... | 96 | +| 10.3.5.4 | Secondary CCPCH..... | 96 | +| 10.3.5.4a | Secondary CCPCH frame type 2..... | 96 | +| 10.3.5.5 | PRACH..... | 97 | +| 10.3.5.6 | Uplink DPDCH+DPCCH..... | 97 | +| 10.3.5.7 | Uplink DPCH..... | 97 | +| 10.3.5.8 | Downlink DPCH..... | 98 | +| 10.3.5.8a | F-DPCH (FDD only)..... | 98 | +| 10.3.5.9 | Void..... | 98 | +| 10.3.5.10 | PICH..... | 98 | +| 10.3.5.11 | AICH..... | 98 | +| 10.3.5.12 | Void..... | 99 | +| 10.3.5.13 | Void..... | 99 | +| 10.3.5.14 | Void..... | 99 | +| 10.3.5.15 | Void..... | 99 | +| 10.3.5.16 | PDSCH (TDD only)..... | 99 | +| 10.3.5.17 | PUSCH..... | 99 | +| 10.3.5.18 | DwPCH (1.28 Mcps TDD only)..... | 100 | +| 10.3.5.19 | UpPCH (1.28 Mcps TDD only)..... | 100 | +| 10.3.5.20 | FPACH (1.28 Mcps TDD only)..... | 100 | +| 10.3.5.21 | PNBSCH (Physical Node B Synchronisation channel)..... | 100 | +| 10.3.5.22 | HS-SCCH..... | 100 | +| 10.3.5.23 | HS-SICH (TDD only)..... | 100 | +| 10.3.5.24 | E-AGCH..... | 100 | +| 10.3.5.25 | E-DPCCH (FDD only)..... | 101 | +| 10.3.5.26 | E-DPDCH (FDD only)..... | 101 | +| 10.3.5.27 | E-HICH..... | 101 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------|------------| +| 10.3.5.28 | E-RGCH (FDD only)..... | 101 | +| 10.3.5.28a | E-RUCCH (TDD only)..... | 101 | +| 10.3.5.29 | MICH..... | 101 | +| 10.3.6 | Feedback information..... | 102 | +| 10.3.7 | HARQ process..... | 102 | +| 10.3.8 | HS-DSCH information..... | 102 | +| 10.3.9 | HARQ status..... | 102 | +| 10.3.10 | E-DCH information..... | 102 | +| 10.3.11 | MBMS information..... | 102 | +| 11 | Transport block transmission..... | 103 | +| Annex A (normative): | Description of Transport Formats..... | 104 | +| Annex B (informative): | Example of Transport format attributes for AMR speech codec..... | 107 | +| Annex C (informative): | Change history..... | 108 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is a technical specification of the services provided by the physical layer of UTRA to upper layers. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 23.110: "UMTS Access Stratum; Services and Functions". +- [2] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [4] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [5] 3GPP TS 25.224: "Physical Layer Procedures (TDD)". +- [6] 3GPP TS 25.215: "Physical Layer – Measurements (FDD)". +- [7] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [8] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [9] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)". +- [10] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)". +- [11] 3GPP TS 25.225: "Physical Layer – Measurements (TDD)". +- [12] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [13] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [14] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in [3] and the following apply: + +**E-DCH active set (FDD only):** The set of cells which carry the E-DCH for one UE. In CELL\_FACH state and Idle mode, the E-DCH active set contains the Serving E-DCH cell only. + +**Serving E-DCH cell:** Cell from which the UE receives Absolute Grants from the Node-B scheduler. A UE has one Serving E-DCH cell. + +**Serving E-DCH RLS or Serving RLS (FDD only):** Set of cells which contains at least the Serving E-DCH cell and from which the UE can receive and combine one Relative Grant. The UE has only one Serving E-DCH RLS. + +**Non-serving E-DCH RL or Non-serving RL (FDD only):** Cell which belongs to the E-DCH active set but does not belong to the Serving E-DCH RLS and from which the UE can receive one Relative Grant. The UE can have zero, one or several Non-serving E-DCH RL(s). + +**Primary downlink frequency:** If a single downlink frequency is configured for the UE, then it is the primary downlink frequency. In case more than one downlink frequency is configured for the UE, then the primary downlink frequency is the frequency on which the Serving HS-DSCH cell is transmitted. + +**Secondary downlink frequency:** In case more than one downlink frequency is configured for the UE, then a secondary downlink frequency is a frequency on which a secondary Serving HS-DSCH cell is transmitted. + +**Activated uplink frequency:** For a specific UE, an uplink frequency is said to be activated if the UE is allowed to transmit on that frequency. The primary uplink frequency is always activated when configured while a secondary uplink frequency has to be activated by means of an HS-SCCH order in order to become activated. + +**Configured uplink frequency:** For a specific UE, an uplink frequency is said to be configured if the UE has received all relevant information from higher layers in order to perform transmission on that frequency. + +**Primary uplink frequency:** If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequency is configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**Secondary uplink frequency:** A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. + +**1st Secondary serving HS-DSCH cell:** If the UE is configured with two uplink frequencies, the 1st secondary serving HS-DSCH cell is the secondary serving HS-DSCH cell that is associated with the secondary uplink frequency. If the UE is configured with a single uplink frequency, the 1st secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**2nd Secondary serving HS-DSCH cell:** If the UE is configured with more than two serving HS-DSCH cells, the 2nd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**3rd Secondary serving HS-DSCH cell:** If the UE is configured with four or more serving HS-DSCH cells, the 3rd secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**4th Secondary serving HS-DSCH cell:** If the UE is configured with five or more serving HS-DSCH cells, the 4th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**5th Secondary serving HS-DSCH cell:** If the UE is configured with six or more serving HS-DSCH cells, the 5th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**6th Secondary serving HS-DSCH cell:** If the UE is configured with seven or more serving HS-DSCH cells, the 6th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**7th Secondary serving HS-DSCH cell:** If the UE is configured with eight serving HS-DSCH cells, the 7th secondary serving HS-DSCH cell is a secondary serving HS-DSCH cell whose index is indicated by higher layers. + +**Multiflow (FDD only):** A mode of operation with two simultaneous HS-DSCH transport channels per carrier frequency, where the HS-DSCH transport channels may belong to the same or different Node Bs. + +**Assisting serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the same frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Assisting secondary serving HS-DSCH Cell:** In addition to the serving HS-DSCH cell, a cell in the secondary downlink frequency, where the UE is configured to simultaneously monitor a HS-SCCH set and receive HS-DSCH if it is scheduled in that cell. + +**Serving E-DCH cell decoupling (FDD only):** An E-DCH operation mode in which the Serving HS-DSCH cell and the Serving E-DCH cell are different. + +**Radio links without DPCCH/F-DPCCH (FDD only):** An operation mode in which UE supports to not receive both DPCCH and F-DPCCH downlink channels from the indicated Non-serving E-DCH cell(s). + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|-----------------------------------------------------------------| +| ARQ | Automatic Repeat Request | +| BCCH | Broadcast Control Channel | +| BCH | Broadcast Channel | +| C- | Control- | +| CC | Call Control | +| CCCH | Common Control Channel | +| CCH | Control Channel | +| CCTrCH | Coded Composite Transport Channel | +| CLTD | Closed Loop Transmit Diversity | +| CN | Core Network | +| CQI | Channel Quality Indicator | +| CRC | Cyclic Redundancy Check | +| DC | Dedicated Control (SAP) | +| DCA | Dynamic Channel Allocation | +| DCCH | Dedicated Control Channel | +| DCH | Dedicated Channel | +| DL | Downlink | +| DPCCH2 | Dedicated Physical Control Channel 2 | +| DRNC | Drift Radio Network Controller | +| DSCH | Downlink Shared Channel | +| DTCH | Dedicated Traffic Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced DCH | +| E-DPCCH | E-DCH Dedicated Physical Control Channel (FDD only) | +| E-DPDCH | E-DCH Dedicated Physical Data Channel (FDD only) | +| E-HICH | E-DCH HARQ Acknowledgement Indicator Channel | +| E-PUCH | E-DCH Physical Uplink Channel (TDD only) | +| E-RGCH | E-DCH Relative Grant Channel (FDD only) | +| E-ROCH | E-DCH Rank and Offset Channel (FDD only) | +| E-RUCCH | E-DCH Random access Uplnk Control Channel (TDD only) | +| E-TFC | E-DCH Transport Format Combination | +| E-UCCH | E-DCH Uplink Control Channel (3.84 Mcps and 7.68 Mcps TDD only) | +| FACH | Forward Link Access Channel | +| FCS | Fame Check Sequence | +| FDD | Frequency Division Duplex | +| F-DPCCH | Fractional Dedicated Physical Channel (FDD only) | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| GC | General Control (SAP) | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| HARQ | Hybrid Automatic Repeat Request | +| HS-DPCCH | High Speed Dedicated Physical Control CHannel | +| HS-DSCH | High Speed Downlink Shared CHannel | +| HS-SCCH | High Speed Shared Control CHannel | +| HS-SICH | High Speed Shared Information CHannel | +| HO | Handover | +| ITU | International Telecommunication Union | +| kbps | kilo-bits per second | +| L1 | Layer 1 (physical layer) | +| L2 | Layer 2 (data link layer) | +| L3 | Layer 3 (network layer) | +| LAC | Link Access Control | +| LAI | Location Area Identity | + +| | | +|-----------|----------------------------------------------| +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MCCH | MBMS point-to-multipoint Control Channel | +| MICH | MBMS notification Indicator Channel | +| MM | Mobility Management | +| MSCH | MBMS point-to-multipoint Scheduling Channel | +| MTCH | MBMS point-to-multipoint Traffic Channel | +| Nt | Notification (SAP) | +| PCCH | Paging Control Channel | +| PCH | Paging Channel | +| PDU | Protocol Data Unit | +| PHY | Physical layer | +| PhyCH | Physical Channels | +| RACH | Random Access Channel | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RNTI | Radio Network Temporary Identity | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| SDU | Service Data Unit | +| S-E-DPCCH | Secondary E-DPCCH (FDD only) | +| S-E-DPDCH | Secondary E-DPDCH (FDD only) | +| SRNC | Serving Radio Network Controller | +| SRNS | Serving Radio Network Subsystem | +| SS | Synchronisation Shift | +| TCH | Traffic Channel | +| TDD | Time Division Duplex | +| TFCI | Transport Format Combination Indicator | +| TFI | Transport Format Indicator | +| TFRI | Transport Format and Resource Indicator | +| TMSI | Temporary Mobile Subscriber Identity | +| TPC | Transmit Power Control | +| TSN | Transmission Sequence Number | +| U- | User- | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| URA | UTRAN Registration Area | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Interfaces to the physical layer + +The physical layer (layer 1) is the lowest layer in the OSI Reference Model and it supports all functions required for the transmission of bit streams on the physical medium. + +The physical layer interfaces the Medium Access Control (MAC) Layer and the Radio Resource Control (RRC) Layer as depicted in figure 1. + +![Diagram showing the interfaces with the Physical Layer (Layer 1). Layer 3 (Radio Resource Control (RRC)) connects to Layer 1 via CPHY primitives. Layer 2 (Medium Access Control (MAC)) connects to Layer 1 via PHY primitives.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the protocol stack interfaces. At the top is Layer 3, containing a box labeled 'Radio Resource Control (RRC)'. Below it is Layer 2, containing a box labeled 'Medium Access Control (MAC)'. At the bottom is Layer 1, labeled 'Physical Layer'. A vertical line descends from the RRC box in Layer 3, passing through a horizontal dotted line representing the Layer 3/Layer 2 interface, to another horizontal dotted line representing the Layer 2/Layer 1 interface. This vertical line is labeled 'CPHY primitives' and terminates at a circle on the Physical Layer box. Another vertical line descends from the MAC box in Layer 2, passing through the Layer 2/Layer 1 interface, to a circle on the Physical Layer box. This vertical line is labeled 'PHY primitives'. + +Diagram showing the interfaces with the Physical Layer (Layer 1). Layer 3 (Radio Resource Control (RRC)) connects to Layer 1 via CPHY primitives. Layer 2 (Medium Access Control (MAC)) connects to Layer 1 via PHY primitives. + +**Figure 1: Interfaces with the Physical Layer** + +## 4.1 Interface to MAC + +The physical layer interfaces the MAC entity of layer 2. Communication between the Physical Layer and MAC is in an abstract way performed by means of PHY-primitives defined which do not constrain implementations. + +NOTE: The terms physical layer and layer 1, will be used synonymously in this description. + +The PHY-primitives exchanged between the physical layer and the data link layer provide the following functions: + +- transfer of transport blocks over the radio interface; +- indicate the status of the layer 1 to layer 2. + +## 4.2 Interface to RRC + +The physical layer interfaces the RRC entity of layer 3 in the UE and in the network. + +Communication is performed in an abstract way by means of CPHY-primitives. They do not constrain implementations. + +The CPHY-primitives exchanged between the physical layer and the Network layer provide the following function: + +- control of the configuration of the physical layer. + +The currently identified exchange of information across that interface has only a local significance to the UE or Network. + +# 5 Services and functions of the physical layer + +## 5.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. The characteristics of a transport channel are defined by its transport format (or format set), specifying the physical layer processing to be applied to the transport channel in question, such as convolutional channel coding and interleaving, and any service-specific rate matching as needed. + +The physical layer operates exactly according to the L1 radio frame timing. A transport block is defined as the data accepted by the physical layer to be jointly CRC protected. The transmission block timing is then tied exactly to the TTI timing, e.g. every transmission block is generated precisely every TTI. + +A UE can set up multiple transport channels simultaneously, each having own transport characteristics (e.g. offering different error correction capability). Each transport channel can be used for information stream transfer of one radio bearer or for layer 2 and higher layer signalling messages. + +The multiplexing of transport channels onto the same or different physical channels is carried out by L1. Except for HS-DSCH and E-DCH the Transport Format Combination Indication field (TFCI) shall uniquely identify the transport format used by each transport channel of the Coded Composite Transport Channel within the current radio frame. + +In case of HS-DSCH the identification of the transport format and channelisation codes is realised with the Transport Format and Resource Indication field (TFRI) on an associated shared control channel. + +In case of FDD E-DCH the identification of the transport format is realised with the E-DCH Transport Format Combination Indication field (E-TFCI) on an associated dedicated control channel. + +In the case of TDD E-DCH the identification of the transport format is realised with the E-DCH Transport Format Combination Indication field (E-TFCI) multiplexed onto E-PUCH. + +## 5.2 Overview of L1 functions + +The physical layer performs the following main functions: + +- FEC encoding/decoding of transport channels; +- measurements and indication to higher layers (e.g. FER, SIR, interference power, transmission power, etc...); +- macrodiversity distribution/combining and soft handover execution; +- error detection on transport channels; +- multiplexing of transport channels and demultiplexing of coded composite transport channels; +- rate matching; +- mapping of coded composite transport channels on physical channels; +- modulation and spreading/demodulation and despreading of physical channels; +- frequency and time (chip, bit, slot, frame) synchronisation; +- closed-loop power control; +- power weighting and combining of physical channels; +- RF processing; +- support of Uplink Synchronisation as defined in [5] (TDD only); +- timing advance on uplink channels (TDD only). + +## 5.3 L1 interactions with L2 retransmission functionality + +Provided that the RLC PDUs are mapped one-to-one onto the Transport Blocks, Error indication may be provided by L1 to L2. For that purpose, the L1 CRC can be used for individual error indication of each RLC PDU. + +The L1 CRC may serve multiple purposes: + +- error indication for uplink macro diversity selection combining (L1); +- error indication for each erroneous Transport Block in transparent and unacknowledged mode RLC; +- quality indication; +- error indication for each erroneous Transport Block in acknowledged mode RLC. + +Regardless of the result of the CRC check, all Transport Blocks are delivered to L2 along with the associated error indications for transport channel other than HS-DSCH and E-DCH. In case of HS-DSCH and E-DCH an error indication is provided to L2 in case of CRC failure. + +In case of HS-DSCH and E-DCH retransmissions of Transport Blocks may be requested before transport blocks are delivered to L2. + +# --- 6 Model of physical layer of the UE + +## 6.1 Uplink models + +Figure 2 shows models of the UE's physical layer in the uplink for both FDD and TDD mode. It shows the models for DCH, RACH, E-DCH, and USCH (TDD only). Some restriction exist for the use of different types of transport channel at the same time, these restrictions are described in the clause "UE Simultaneous Physical Channel combinations". More details can be found in [3] and [4]. + +Error: + +15 + +Error: Reference source not + +![Diagram of DCH model showing three DCH inputs entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)'. This channel enters a 'Demultiplexing/splitting' block, which outputs 'Physical Channel Data Streams'. These streams are then split into two 'Phy CH' blocks. To the right, a 'Transport Format Combination Indicator (TFCI)' block points to a 'TPC -> Phy CH' block.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +**DCH model** + +``` +graph TD; DCH1[DCH] --> CM[Coding and multiplexing]; DCH2[DCH] --> CM; DCH3[DCH] --> CM; CM -- "Coded Composite Transport Channel (CCTrCH)" --> DS[Demultiplexing/splitting]; DS -- "Physical Channel Data Streams" --> PC1[Phy CH]; DS -- "Physical Channel Data Streams" --> PC2[Phy CH]; TFCI[Transport Format Combination Indicator (TFCI)] --> TPC[TPC -> Phy CH]; +``` + +Diagram of DCH model showing three DCH inputs entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)'. This channel enters a 'Demultiplexing/splitting' block, which outputs 'Physical Channel Data Streams'. These streams are then split into two 'Phy CH' blocks. To the right, a 'Transport Format Combination Indicator (TFCI)' block points to a 'TPC -> Phy CH' block. + +![Diagram of RACH model showing a single RACH input entering a 'Coding' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which then enters a 'Phy CH' block.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +**RACH model** + +``` +graph TD; RACH --> C[Coding]; C -- "Coded Composite Transport Channel (CCTrCH)" --> PC[Phy CH]; +``` + +Diagram of RACH model showing a single RACH input entering a 'Coding' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which then enters a 'Phy CH' block. + +![Diagram of USCH model showing two USCH inputs entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which enters a 'Demultiplexing/splitting' block. This block outputs 'TPC TFCI' and 'Physical Channel Data Streams'. The 'TPC TFCI' and 'Data Streams' are then split into two 'Phy CH' blocks.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +**USCH model** + +``` +graph TD; USCH1[USCH] --> CM[Coding and multiplexing]; USCH2[USCH] --> CM; CM -- "Coded Composite Transport Channel (CCTrCH)" --> DS[Demultiplexing/splitting]; DS -- "TPC TFCI" --> PC1[Phy CH]; DS -- "Physical Channel Data Streams" --> PC2[Phy CH]; +``` + +Diagram of USCH model showing two USCH inputs entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which enters a 'Demultiplexing/splitting' block. This block outputs 'TPC TFCI' and 'Physical Channel Data Streams'. The 'TPC TFCI' and 'Data Streams' are then split into two 'Phy CH' blocks. + +DCH model with HS-DSCH support + +![Diagram of DCH model with HS-DSCH support. It shows two DCH inputs (represented by ovals) entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which enters a 'Demultiplexing/Splitting' block. This block outputs 'Physical Channel Data Streams' which are split into two 'Phy CH' blocks. To the right, there are two additional 'Phy CH' blocks. The first 'Phy CH' block receives 'TDD TPC & TFCI' input. The second 'Phy CH' block receives 'FDD TPC & TFCI' input. The third 'Phy CH' block receives 'ACK/NACK CQI TPC (TDD)' input.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` +graph TD; DCH1((DCH)) --> CM[Coding and multiplexing]; DCH2((DCH)) --> CM; CM -- "Coded Composite Transport Channel (CCTrCH)" --> DS[Demultiplexing/Splitting]; DS -- "Physical Channel Data Streams" --> PC1[Phy CH]; DS -- "Physical Channel Data Streams" --> PC2[Phy CH]; TDD[ +TDD +TPC & TFCI +] --> PC3[Phy CH]; FDD[ +FDD +TPC & TFCI +] --> PC4[Phy CH]; ACK[ +ACK/NACK +CQI +TPC (TDD) +] --> PC5[Phy CH]; +``` + +Diagram of DCH model with HS-DSCH support. It shows two DCH inputs (represented by ovals) entering a 'Coding and multiplexing' block. The output is a 'Coded Composite Transport Channel (CCTrCH)' which enters a 'Demultiplexing/Splitting' block. This block outputs 'Physical Channel Data Streams' which are split into two 'Phy CH' blocks. To the right, there are two additional 'Phy CH' blocks. The first 'Phy CH' block receives 'TDD TPC & TFCI' input. The second 'Phy CH' block receives 'FDD TPC & TFCI' input. The third 'Phy CH' block receives 'ACK/NACK CQI TPC (TDD)' input. + +### DCH and E-DCH model with HS-DSCH support + +![Diagram showing DCH and E-DCH model with HS-DSCH support. It illustrates two parallel processing paths. The left path for DCH shows two input channels entering a 'Coding and multiplexing' block, resulting in a 'Coded Composite Transport Channel (CCTrCH)'. This is then processed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams' and 'TPC & TFCI'. These are mapped to 'Phy CH' blocks, with 'ACK/NACK' and 'CQI' also being mapped. The right path for E-DCH shows one input channel entering a similar 'Coding and multiplexing' block, followed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams', 'E-DCH TFCI', and 'E-DCH HARQ', which are mapped to 'Phy CH' blocks.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +DCH DCH + +Coding and multiplexing + +Coded Composite Transport Channel (CCTrCH) + +Demultiplexing / Splitting + +Physical Channel Data Streams + +TPC & TFCI + +ACK/NACK + +CQI + +Phy CH + +E-DCH + +Coding and multiplexing + +Coded Composite Transport Channel (CCTrCH) + +Demultiplexing / Splitting + +Physical Channel Data Streams + +E-DCH TFCI + +E-DCH HARQ + +Phy CH + +Diagram showing DCH and E-DCH model with HS-DSCH support. It illustrates two parallel processing paths. The left path for DCH shows two input channels entering a 'Coding and multiplexing' block, resulting in a 'Coded Composite Transport Channel (CCTrCH)'. This is then processed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams' and 'TPC & TFCI'. These are mapped to 'Phy CH' blocks, with 'ACK/NACK' and 'CQI' also being mapped. The right path for E-DCH shows one input channel entering a similar 'Coding and multiplexing' block, followed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams', 'E-DCH TFCI', and 'E-DCH HARQ', which are mapped to 'Phy CH' blocks. + +E-DCH with HS-DSCH (no DCH) + +![Diagram showing E-DCH with HS-DSCH (no DCH). A single input channel enters a 'Coding and multiplexing' block, resulting in a 'Coded Composite Transport Channel (CCTrCH)'. This is processed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams'. 'ACK/NACK', 'CQI', and 'TPC' are mapped to one 'Phy CH' block. The data streams are mapped to two 'Phy CH' blocks. Additionally, 'E-UCCH TPC' and 'E-RUCCH' are mapped to a third 'Phy CH' block.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +Coding and multiplexing + +Coded Composite Transport Channel (CCTrCH) + +Demultiplexing / Splitting + +Physical Channel Data Streams + +ACK/NACK + +CQI + +TPC + +Phy CH + +E-UCCH TPC + +E-RUCCH + +Phy CH + +Diagram showing E-DCH with HS-DSCH (no DCH). A single input channel enters a 'Coding and multiplexing' block, resulting in a 'Coded Composite Transport Channel (CCTrCH)'. This is processed by 'Demultiplexing / Splitting' to produce 'Physical Channel Data Streams'. 'ACK/NACK', 'CQI', and 'TPC' are mapped to one 'Phy CH' block. The data streams are mapped to two 'Phy CH' blocks. Additionally, 'E-UCCH TPC' and 'E-RUCCH' are mapped to a third 'Phy CH' block. + +![Diagram showing the mapping of transport channels to physical channels.](8307f6b04df072c9332f9987e034272c_img.jpg) + +E-DCH with DCH and HS-DSCH + +The diagram shows two main paths. + Left path: Two DCH inputs enter a 'Coding and multiplexing' block. The output is labeled 'Coded Composite Transport Channel (CCTrCH)'. This leads to a 'Demultiplexing/Splitting' block, which outputs 'Physical Channel Data Streams' to multiple 'Phy CH' blocks. Control signals 'TPC & TFCI' are also mapped to a 'Phy CH'. + Right path: An E-DCH input enters a 'Coding and multiplexing' block. The output is labeled 'Coded Composite Transport Channel (CCTrCH)'. This leads to a 'Demultiplexing/Splitting' block, which outputs to multiple 'Phy CH' blocks. Control signals 'ACK/NACK', 'CQI', and 'TPC' are mapped to a 'Phy CH'. Additionally, 'E-UCCH' (with TPC) and 'E-RUCCH' are mapped to their respective 'Phy CH' blocks. + +Diagram showing the mapping of transport channels to physical channels. + +![A partially obscured diagram showing channel mapping.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +This section contains a diagram that is mostly obscured by black rectangles. Visible elements at the bottom show arrows pointing from white rectangular blocks to grey 'Phy CH' blocks, similar to the structure in the top diagram. Control signal arrows are also visible on the right side of these blocks. + +A partially obscured diagram showing channel mapping. + +![Figure 2: Model of the UE's physical layer – uplink. The diagram shows a large black rectangle at the top, representing the physical channel. Below it, a white rectangle is centered, representing the CCTrCH. Below the white rectangle, two grey rectangles are stacked vertically, representing the DCH and USCH transport channels. The diagram is partially obscured by a large black rectangle at the top.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 2: Model of the UE's physical layer – uplink. The diagram shows a large black rectangle at the top, representing the physical channel. Below it, a white rectangle is centered, representing the CCTrCH. Below the white rectangle, two grey rectangles are stacked vertically, representing the DCH and USCH transport channels. The diagram is partially obscured by a large black rectangle at the top. + +NOTE 1: USCH is for TDD only. + +**Figure 2: Model of the UE's physical layer – uplink** + +The DCH model shows that one or several DCHs can be processed and multiplexed together by the same coding and multiplexing unit. The detailed functions of the coding and multiplexing unit are not defined in the present document but in [3] and [4]. The single output data stream from the coding and multiplexing unit is denoted *Coded Composite Transport Channel (CCTrCH)*. + +The bits on a CCTrCH Data Stream can be mapped on the same Physical Channel and should have the same C/I requirement. + +On the downlink, multiple CCTrCH can be used simultaneously with one UE. In the case of FDD, only one fast power control loop is necessary for these different CCTrCH, but the different CCTrCH can have different C/I requirements to provide different QoS on the mapped Transport Channels. In the case of TDD, different power control loops can be applied for different CCTrCH. One physical channel can only have bits coming from the same CCTrCH. + +On the uplink and in the case of FDD, when E-DCH is not configured, only one CCTrCH can be used simultaneously. On the uplink and in the case of TDD, multiple CCTrCH can be used simultaneously. + +On the uplink and in case of FDD, two CCTrCHs are used simultaneously when the E-DCH Transport Channel is configured. + +When multiple CCTrCH are used by one UE, one or several TFCI can be used, but each CCTrCH has only zero or one corresponding TFCI. In the case of FDD, these different words are mapped on the same DPCCH. In the case of TDD, these different TFCIs can be mapped on different DPCH. + +The data stream of the CCTrCH is fed to a data demultiplexing/splitting unit that demultiplexes/splits the CCTrCH's data stream onto one or several *Physical Channel Data Streams*. + +The current configuration of the coding and multiplexing unit is either signalled to, or optionally blindly detected by, the network for each 10 ms frame. If the configuration is signalled, it is represented by the *Transport Format Combination Indicator (TFCI)* bits. Note that the TFCI signalling only consists of pointing out the current transport format combination within the already configured transport format combination set. In the uplink there is only one TFCI representing the current transport formats on all DCHs of one CCTrCH simultaneously. In FDD mode, the physical channel data stream carrying the TFCI is mapped onto the physical channel carrying the power control bits and the pilot. In TDD mode the TFCI is time multiplexed onto the same physical channel(s) as the DCHs. The exact locations and coding of the TFCI are signalled by higher layers. + +The DCH and USCH have the possibility to perform Timing Advance in TDD mode. + +The model for the RACH case shows that RACH is a common type transport channel in the uplink. RACHs are always mapped one-to-one onto physical channels (PRACHs), i.e. there is no physical layer multiplexing of RACHs, and there can only be one RACH TrCH and no other TrCH in a RACH CCTrCH. Service multiplexing is handled by the MAC layer. In one cell several RACHs/PRACHs may be configured. If more than one PRACH is configured in a cell, the UE performs PRACH selection as specified in [4]. + +In FDD, the RACHs mapped to the PRACHs may all employ the same Transport Format and Transport Format Combination Sets, respectively. It is however also possible that individual RACH Transport Format Sets are applied on each available RACH/PRACH. + +In TDD, there is no TFCI transmitted in the burst, and therefore each RACH is configured with a single transport format within its TFS. The RACHs mapped to the PRACHs may all employ the same Transport Format. It is however also possible that individual RACH Transport Formats are applied on each available RACH/PRACH combination. + +The available pairs of RACH and PRACHs and their parameters are indicated in system information. In FDD mode, the various PRACHs are distinguished either by employing different preamble scrambling codes, or by using a common scrambling code but distinct (non-overlapping) partitions of available signatures and available subchannels. In TDD mode, the various PRACHs are distinguished either by employing different timeslots, or by using a common timeslot but distinct (non-overlapping) partitions of available channelisation codes and available subchannels. Examples of RACH/PRACH configurations are given in [6]. + +In FDD in case of a configured HS-DSCH in CELL\_DCH state, one physical channel (HS-DPCCH) is configured for the reporting of HS-DSCH transport block acknowledgement / negative acknowledgement and channel quality indicator. The HS-DPCCH is only configured on the primary uplink frequency. When MIMO mode is configured, the HS-DPCCH also carries precoding control information. In FDD, when more than three secondary cells are configured, two HS-DPCCHs are configured to carry feedback information related to the HS-DSCH transport channels. + +In FDD in case of a configured Multiflow in CELL\_DCH state, one physical channel (HS-DPCCH) is configured for reporting of HS-DSCH transport block acknowledgement / negative acknowledgement and channel quality indicators from the serving and assisting HS-DSCH cells. The HS-DPCCH is only configured on the primary uplink frequency. When MIMO mode is configured, the HS-DPCCH also carries precoding control information. + +In TDD in case of a configured HS-DSCH a shared physical channel (HS-SICH) is configured for the reporting of HS-DSCH transport block acknowledgement / negative acknowledgement, channel quality indicator and transmit power control symbols. + +In FDD in case of a configured HS-DSCH reception in CELL\_FACH, CELL\_PCH or URA\_PCH states there is neither acknowledgement / negative acknowledgement nor channel quality indicator. Therefore, no physical channel (HS-DPCCH) is configured. + +If the E-DCH is applicable, there can only be one E-DCH TrCH and no other TrCH in an E-DCH CCTrCH per activated uplink frequency. For FDD, the E-DCH CCTrCH is carried on E-DPDCH(s) physical channel(s). E-DCH TFCI and E-DCH HARQ information are carried on an E-DPCCH physical channel. For FDD, a single bit is transmitted on the E-DPCCH physical channel per activated uplink frequency to indicate whether the UE could use more resources or not. For TDD, the E-DCH is carried on the E-PUCH physical channel(s). The E-PUCH also carries E-UCCH (E-DCH TFCI and E-DCH HARQ information). + +In FDD mode and CELL\_DCH state when Dual Cell E-DCH operation is configured, one E-DCH transport channel is transmitted on each activated uplink frequency. Each E-DCH transport channel has its own associated uplink signalling. + +In FDD mode and CELL\_DCH state when uplink CLTD is configured, two dedicated pilot channels, DPCCH and S-DPCCH, are transmitted in the uplink. + +In FDD mode and CELL\_DCH state, when uplink MIMO is configured and the CLTD activation state is 1 [8], two dedicated pilot channel, DPCCH and S-DPCCH, are transmitted in the uplink. Two transport blocks may be transmitted in parallel: a primary transport block on the primary precoding vector using E-DPDCH physical channels, and a secondary transport block on the secondary precoding vector using S-E-DPDCH physical channels. When the secondary transport block is present, then S-E-DPCCH is transmitted on the primary precoding vector providing the E-TFCI and E-DCH HARQ information for the secondary transport block. + +In FDD mode and CELL\_DCH state, when DPCCH2 is configured, two dedicated channels, DPCCH and DPCCH2, are transmitted in the uplink. + +## 6.2 Downlink models + +Figure 3 and figure 4 show the model of the UE's physical layer for the downlink in FDD and TDD mode, respectively. Note that there is a different model for each transport channel type. + +![Diagram showing three models: FACH & PCH model, BCH model, and DCH model. The FACH & PCH model shows PCH, FACH, and FACH channels being decoded and demultiplexed from a Coded Composite Transport Channel (CCTrCH). The BCH model shows a single BCH channel being decoded from a CCTrCH. The DCH model shows three DCH channels being decoded and demultiplexed from a CCTrCH, which is then multiplexed (MUX) with Physical Channel Data Streams from three cells (Cell 1, Cell 2, Cell 3) to produce TPC streams 1, 2, and 3 with TFCI.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +**FACH & PCH model** + +PCH FACH FACH + +Decoding and demultiplexing + +Coded Composite Transport Channel (CCTrCH) + +PI ← Phy CH TFCI ← Phy CH + +**BCH model** + +BCH + +Decoding + +Coded Composite Transport Channel (CCTrCH) + +Phy CH + +**DCH model** + +DCH DCH DCH + +Decoding and demultiplexing + +Coded Composite Transport Channel (CCTrCH) + +MUX + +Physical Channel Data Streams + +| | | | | +|--------|--------|--------|----------------------| +| Cell 1 | Phy CH | Phy CH | → TPC stream 1, TFCI | +| Cell 2 | Phy CH | Phy CH | → TPC stream 2, TFCI | +| Cell 3 | Phy CH | Phy CH | → TPC stream 3, TFCI | + +Diagram showing three models: FACH & PCH model, BCH model, and DCH model. The FACH & PCH model shows PCH, FACH, and FACH channels being decoded and demultiplexed from a Coded Composite Transport Channel (CCTrCH). The BCH model shows a single BCH channel being decoded from a CCTrCH. The DCH model shows three DCH channels being decoded and demultiplexed from a CCTrCH, which is then multiplexed (MUX) with Physical Channel Data Streams from three cells (Cell 1, Cell 2, Cell 3) to produce TPC streams 1, 2, and 3 with TFCI. + +HS-DSCH(s) model in CELL\_FACH, CELL\_PCH and URA\_PCH states + PI only used in CELL\_PCH and URA\_PCH states + +![Diagram of the HS-DSCH model. It shows an HS-DSCH channel being decoded to produce a Coded Composite Transport Channel (CCTrCH). This CCTrCH is multiplexed (MUX) with Physical Channel Data Streams from Cell 1. The MUX also receives TFRI and HARQ information. The output of the MUX is a PI (Packet Indicator) and a Phy CH.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +HS-DSCH + +Decoding + +Coded Composite Transport Channel (CCTrCH) + +MUX + +Physical Channel Data Streams + +TFRI HARQ information TFRI HARQ information + +PI + +Phy CH + +Cell 1 + +Diagram of the HS-DSCH model. It shows an HS-DSCH channel being decoded to produce a Coded Composite Transport Channel (CCTrCH). This CCTrCH is multiplexed (MUX) with Physical Channel Data Streams from Cell 1. The MUX also receives TFRI and HARQ information. The output of the MUX is a PI (Packet Indicator) and a Phy CH. + +DCH model with HS-DSCH(s) + +![Diagram showing two channel models. The left model shows DCH channels being decoded and demultiplexed from a Coded Composite Transport Channel (CCTrCH), which is then multiplexed (MUX) from Physical Channel Data Streams. The right model shows an HS-DSCH channel being decoded from a CCTrCH, which is then multiplexed (MUX) from Physical Channel Data Streams, with additional TFRI HARQ information inputs.](a3472689858b068ef469213682965325_img.jpg) + +The diagram illustrates two channel processing models. The left model shows multiple DCH channels being decoded and demultiplexed from a Coded Composite Transport Channel (CCTrCH). This CCTrCH is then multiplexed (MUX) from Physical Channel Data Streams. The output is shown as three TPC streams (TPC stream 1, TPC stream 2, TPC stream 3) with TFRI information. The right model shows an HS-DSCH channel being decoded from a CCTrCH. This CCTrCH is then multiplexed (MUX) from Physical Channel Data Streams. The output is shown as a single TPC stream (TPC stream 1) with TFRI HARQ information. Both models include a 'Physical Channel Data Streams' input and a 'MUX' block. + +**Left Model: DCH model with HS-DSCH(s)** + +- DCH channels are input to a **Decoding and demultiplexing** block. +- The output is a **Coded Composite Transport Channel (CCTrCH)**. +- The CCTrCH is input to a **MUX** block. +- The MUX block also receives **Physical Channel Data Streams**. +- The output of the MUX block is shown as: + - Cell 1: Phy CH Phy CH → TPC stream 1, TFRI + - Cell 2: Phy CH Phy CH → TPC stream 2, TFRI + - Cell 3: Phy CH Phy CH → TPC stream 3, TFRI + +**Right Model: HS-DSCH model** + +- HS-DSCH is input to a **Decoding** block. +- The output is a **Coded Composite Transport Channel (CCTrCH)**. +- The CCTrCH is input to a **MUX** block. +- The MUX block also receives **Physical Channel Data Streams**. +- The output of the MUX block is shown as: + - Cell 1: Phy CH Phy CH → TPC stream 1, TFRI HARQ information +- Additional **TFRI HARQ information** is input to the MUX block. + +Diagram showing two channel models. The left model shows DCH channels being decoded and demultiplexed from a Coded Composite Transport Channel (CCTrCH), which is then multiplexed (MUX) from Physical Channel Data Streams. The right model shows an HS-DSCH channel being decoded from a CCTrCH, which is then multiplexed (MUX) from Physical Channel Data Streams, with additional TFRI HARQ information inputs. + +DCH and HS-DSCH model with E-DCH support + +![Diagram of DCH and HS-DSCH model with E-DCH support showing uplink and downlink data flows across multiple cells.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +This diagram illustrates the DCH and HS-DSCH model with E-DCH support. It shows the processing of physical channels from multiple cells into transport channels. + +**Left Side (Uplink/Control):** Physical Channels (Phy CH) from Cell $d_1$ to Cell $d_n$ are shown. Some are multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH), which is then processed by a 'Decoding and demultiplexing' block to output two DCH streams. Control signals include TPC stream 1/TFCI 1 through TPC stream $n$ /TFCI $n$ . + +**Right Side (Downlink/Control):** Physical Channels from Cell $e_1$ , Cell $e_s$ , and Cell $e_m$ are processed. Control signals include ACK/NACK stream 1,... $m$ , Relative Grant stream 1,... $m$ , Absolute Grant, and TFRI HARQ. These are multiplexed (MUX) into a CCTrCH, which is then decoded into an HS-DSCH. + +Diagram of DCH and HS-DSCH model with E-DCH support showing uplink and downlink data flows across multiple cells. + +HS-DSCH(s) with F-DPCH model + +![Diagram of HS-DSCH(s) with F-DPCH model showing data flow from a single cell and a TPC stream legend.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +This diagram illustrates the HS-DSCH(s) with F-DPCH model. It shows physical channels from Cell 1 being multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH) and then decoded into an HS-DSCH. Control inputs include TFRI HARQ information. + +**Legend:** + +- Cell 1   [Phy CH] [Phy CH] → TPC stream 1 +- Cell 2   [Phy CH] [Phy CH] → TPC stream 2 +- Cell 3   [Phy CH] [Phy CH] → TPC stream 3 + +Diagram of HS-DSCH(s) with F-DPCH model showing data flow from a single cell and a TPC stream legend. + +HS-DSCH with F-DPCH model and E-DCH support + +![Diagram of HS-DSCH with F-DPCH model and E-DCH support. On the left, Cell 1, Cell 2, and Cell 3 each have two 'Phy CH' blocks pointing to 'TPC stream 1', 'TPC stream 2', and 'TPC stream 3' respectively. The main diagram shows a base station with 'ACK/NACK stream 1,...m', 'Relative Grant stream 1,...m', and 'Absolute Grant' inputs. These are transmitted via 'Phy CH' blocks to multiple cells (Cell e1, Cell es, Cell em). On the UE side, 'TFRI HARQ' and 'Physical Channel Data Streams' are inputs to a 'MUX' block, which outputs a 'Coded Composite Transport Channel (CCTrCH)' to a 'Decoding' block, which finally outputs the 'HS-DSCH'.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Cell 1 Phy CH Phy CH → TPC stream 1 +Cell 2 Phy CH Phy CH → TPC stream 2 +Cell 3 Phy CH Phy CH → TPC stream 3 + +ACK/NACK stream 1,...m Relative Grant stream 1,...m Absolute Grant TFRI HARQ TFRI HARQ HS-DSCH +Decoding +Coded Composite Transport Channel (CCTrCH) +MUX +Physical Channel Data Streams +Cell e1 Phy CH Phy CH Phy CH Phy CH Cell 1 +Cell es Phy CH +Cell em + +Diagram of HS-DSCH with F-DPCH model and E-DCH support. On the left, Cell 1, Cell 2, and Cell 3 each have two 'Phy CH' blocks pointing to 'TPC stream 1', 'TPC stream 2', and 'TPC stream 3' respectively. The main diagram shows a base station with 'ACK/NACK stream 1,...m', 'Relative Grant stream 1,...m', and 'Absolute Grant' inputs. These are transmitted via 'Phy CH' blocks to multiple cells (Cell e1, Cell es, Cell em). On the UE side, 'TFRI HARQ' and 'Physical Channel Data Streams' are inputs to a 'MUX' block, which outputs a 'Coded Composite Transport Channel (CCTrCH)' to a 'Decoding' block, which finally outputs the 'HS-DSCH'. + +HS-DSCH with F-DPCH model and E-DCH support (serving E-DCH cell decoupling active) + +![Diagram of HS-DSCH with F-DPCH model and E-DCH support with serving E-DCH cell decoupling active. The left side is identical to the previous diagram. The main diagram is similar, but the 'Absolute Grant' is transmitted via 'Phy CH' blocks to Cell e1, Cell es (where es != 1), and Cell em. Cell 1 is shown separately on the right side of the UE, receiving 'Phy CH' blocks from the 'MUX'.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Cell 1 Phy CH Phy CH → TPC stream 1 +Cell 2 Phy CH Phy CH → TPC stream 2 +Cell 3 Phy CH Phy CH → TPC stream 3 + +ACK/NACK stream 1,...m Relative Grant stream 1,...m Absolute Grant TFRI HARQ TFRI HARQ HS-DSCH +Decoding +Coded Composite Transport Channel (CCTrCH) +MUX +Physical Channel Data Streams +Cell e1 Phy CH Phy CH Phy CH Phy CH Cell 1 +Cell es ≠ Cell 1 Phy CH +Cell em + +Diagram of HS-DSCH with F-DPCH model and E-DCH support with serving E-DCH cell decoupling active. The left side is identical to the previous diagram. The main diagram is similar, but the 'Absolute Grant' is transmitted via 'Phy CH' blocks to Cell e1, Cell es (where es != 1), and Cell em. Cell 1 is shown separately on the right side of the UE, receiving 'Phy CH' blocks from the 'MUX'. + +![Diagram of the UE's physical layer - downlink FDD mode. It shows three cells (Cell 1, Cell 2, Cell 3) each with a 'Phy CH' leading to 'TFCI'. These are combined into a 'Coded Composite Transport Channel (CCTrCH)', which then enters a 'Decoding and demultiplexing' block. The output of this block is multiple 'FACH' channels, with an ellipsis between them. Above the FACH channels is the text 'FACH model (macro-diversity case)'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +FACH model (macro-diversity case) + +FACH FACH +... + +Decoding and demultiplexing + +Coded Composite Transport Channel (CCTrCH) + +Cell 1 Phy CH → TFCI + +Cell 2 Phy CH → TFCI + +Cell 3 Phy CH → TFCI + +Diagram of the UE's physical layer - downlink FDD mode. It shows three cells (Cell 1, Cell 2, Cell 3) each with a 'Phy CH' leading to 'TFCI'. These are combined into a 'Coded Composite Transport Channel (CCTrCH)', which then enters a 'Decoding and demultiplexing' block. The output of this block is multiple 'FACH' channels, with an ellipsis between them. Above the FACH channels is the text 'FACH model (macro-diversity case)'. + +Figure 3: Model of the UE's physical layer - downlink FDD mode + +![Four block diagrams showing channel models: FACH & PCH, BCH, DCH, and DSCH. Each diagram shows the flow from Physical Channel Data Streams through a MUX to a Coded Composite Transport Channel (CCTrCH), and then through Decoding and demultiplexing to the final channels (FACH, PCH, BCH, DCH, or DSCH).](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates four channel models, each showing the flow from Physical Channel Data Streams through a MUX to a Coded Composite Transport Channel (CCTrCH), and then through Decoding and demultiplexing to the final channels. + +**FACH & PCH model:** Physical Channel Data Streams (PI ← Phy CH, TFCI ← Phy CH, Phy CH) are multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH). This is then decoded and demultiplexed into FACH, FACH, and PCH. + +**BCH model:** A single Physical Channel (Phy CH) is multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH). This is then decoded into a single BCH. + +**DCH model:** Physical Channel Data Streams (TPC SS TFCK ← Phy CH, Phy CH) are multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH). This is then decoded and demultiplexed into three DCH channels. + +**DSCH model:** Physical Channel Data Streams (TPC SS TFCK ← Phy CH, Phy CH) are multiplexed (MUX) into a Coded Composite Transport Channel (CCTrCH). This is then decoded and demultiplexed into two DSCH channels. + +Four block diagrams showing channel models: FACH & PCH, BCH, DCH, and DSCH. Each diagram shows the flow from Physical Channel Data Streams through a MUX to a Coded Composite Transport Channel (CCTrCH), and then through Decoding and demultiplexing to the final channels (FACH, PCH, BCH, DCH, or DSCH). + +HS-DSCH(s) for 3.84 and 7.68 +Mcps TDD with DL DPCH + +![Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD with DL DPCH. It shows a 'Decoding and demultiplexing' block receiving 'DCH' inputs and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH') and a 'TFCI' input. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD with DL DPCH. It shows a 'Decoding and demultiplexing' block receiving 'DCH' inputs and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH') and a 'TFCI' input. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'. + +![Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD without DL DPCH. It shows a 'Decoding' block receiving an 'HS-DSCH' input and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH'). Above the MUX, 'TFRI HARQ information HCSN' is shown being input from two 'Phy CH' sources. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD without DL DPCH. It shows a 'Decoding' block receiving an 'HS-DSCH' input and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH'). Above the MUX, 'TFRI HARQ information HCSN' is shown being input from two 'Phy CH' sources. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'. + +HS-DSCH(s) for 3.84 and 7.68 +Mcps TDD without DL DPCH + +![Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD without DL DPCH. It shows a 'Decoding' block receiving an 'HS-DSCH' input and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH'). Above the MUX, 'TFRI HARQ information HCSN' is shown being input from two 'Phy CH' sources. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +Diagram of HS-DSCH(s) for 3.84 and 7.68 Mcps TDD without DL DPCH. It shows a 'Decoding' block receiving an 'HS-DSCH' input and outputting a 'Coded Composite Transport Channel (CCTrCH)'. This is followed by a 'MUX' block that also receives 'Physical Channel Data Streams' from 'Cell 1' (via 'Phy CH'). Above the MUX, 'TFRI HARQ information HCSN' is shown being input from two 'Phy CH' sources. The output of the MUX is the 'Coded Composite Transport Channel (CCTrCH)'. + +HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD + +![Diagram of HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD showing data flow from DCH through decoding, multiplexing, and physical channels.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +This diagram illustrates the data flow for HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD. At the top, two ovals labeled 'DCH' and '.....' are connected to a rectangular block labeled 'Decoding and demultiplexing'. This block outputs a 'Coded Composite Transport Channel (CCTrCH)' to a 'MUX' block. The 'MUX' block also receives 'Physical Channel Data Streams' from below, indicated by arrows and '.....'. The 'MUX' block outputs 'TPC', 'TFCI', and 'SS' to the right. Below the 'MUX' block, two rectangular blocks labeled 'Phy CH' are shown, with an arrow pointing from 'Cell 1' to them. An arrow also points from the 'Phy CH' blocks to the 'MUX' block. + +Diagram of HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD showing data flow from DCH through decoding, multiplexing, and physical channels. + +![Diagram of HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD showing data flow from HS-DSCH through decoding, multiplexing, and physical channels, including control information.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +This diagram illustrates the data flow for HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD. At the top, an oval labeled 'HS-DSCH' is connected to a rectangular block labeled 'Decoding'. This block outputs a 'Coded Composite Transport Channel (CCTrCH)' to a 'MUX' block. The 'MUX' block also receives 'Physical Channel Data Streams' from below, indicated by arrows and '.....'. The 'MUX' block outputs 'TFRI', 'HARQ info', 'HCSN', 'TPC', and 'SS' to the left. Below the 'MUX' block, four rectangular blocks labeled 'Phy CH' are shown, with an arrow pointing from 'Cell 1' to them. An arrow also points from the 'Phy CH' blocks to the 'MUX' block. Above the 'Phy CH' blocks, two sets of control information are shown: 'TFRI', 'HARQ info', 'HCSN', 'TPC', 'SS' and 'TFRI', 'HARQ info', 'HCSN'. + +Diagram of HS-DSCH(s) with DL DPCH for 1.28 Mcps TDD showing data flow from HS-DSCH through decoding, multiplexing, and physical channels, including control information. + +HS-DSCH(s) without DL DPCH for 1.28 Mcps TDD + +![Diagram of HS-DSCH(s) without DL DPCH for 1.28 Mcps TDD showing data flow from HS-DSCH through decoding, multiplexing, and physical channels, with a separate PLCCH block.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +This diagram illustrates the data flow for HS-DSCH(s) without DL DPCH for 1.28 Mcps TDD. At the top, an oval labeled 'HS-DSCH' is connected to a rectangular block labeled 'Decoding'. This block outputs a 'Coded Composite Transport Channel (CCTrCH)' to a 'MUX' block. The 'MUX' block also receives 'Physical Channel Data Streams' from below, indicated by arrows and '.....'. The 'MUX' block outputs 'TFRI', 'HARQ info', 'HCSN', 'TPC', 'SS' and 'TFRI', 'HARQ info', 'HCSN' to the left. Below the 'MUX' block, four rectangular blocks labeled 'Phy CH' are shown, with an arrow pointing from 'Cell 1' to them. An arrow also points from the 'Phy CH' blocks to the 'MUX' block. To the left of the 'Phy CH' blocks, a separate block shows 'TPC, SS' above a 'Phy CH' block, with an arrow pointing from 'PLCCH' to the 'Phy CH' block. + +Diagram of HS-DSCH(s) without DL DPCH for 1.28 Mcps TDD showing data flow from HS-DSCH through decoding, multiplexing, and physical channels, with a separate PLCCH block. + +E-DCH model with HS-DSCH (no DCH) (3.84 Mcps and 7.68 Mcps TDD) + +![Block diagram of E-DCH model with HS-DSCH (no DCH) for 3.84 Mcps and 7.68 Mcps TDD. The diagram shows the flow from HS-DSCH through a Decoding block to a MUX block, resulting in a Coded Composite Transport Channel (CCTrCH). This CCTrCH is then split into three physical channels (Phy CH): E-HICH (ACK/NACK), HS-SCCH (carrying TPC, E-AGCH Absolute Grant, and TFRI), and HARQ. Each of these three channels is associated with its own Phy CH block.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +Block diagram of E-DCH model with HS-DSCH (no DCH) for 3.84 Mcps and 7.68 Mcps TDD. The diagram shows the flow from HS-DSCH through a Decoding block to a MUX block, resulting in a Coded Composite Transport Channel (CCTrCH). This CCTrCH is then split into three physical channels (Phy CH): E-HICH (ACK/NACK), HS-SCCH (carrying TPC, E-AGCH Absolute Grant, and TFRI), and HARQ. Each of these three channels is associated with its own Phy CH block. + +E-DCH with DCH and HS-DSCH (3.84 Mcps and 7.68 Mcps TDD) + +![Block diagram of E-DCH with DCH and HS-DSCH for 3.84 Mcps and 7.68 Mcps TDD. On the left, two DCH inputs go into a 'Coding and multiplexing' block, which outputs a Coded Composite Transport Channel (CCTrCH). This CCTrCH goes into a MUX block along with 'TPC & TFCI'. The output of this MUX is split into multiple Physical Channel Data Streams, each represented by a Phy CH block. In the center, an E-HICH (ACK/NACK) is shown with its own Phy CH block. On the right, an HS-DSCH goes through a 'Decoding' block to produce a CCTrCH, which then goes into another MUX block. This MUX block also receives inputs from a HS-SCCH (carrying TPC, E-AGCH Absolute Grant, and TFRI) and HARQ. The output of this second MUX is split into two Phy CH blocks.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +Block diagram of E-DCH with DCH and HS-DSCH for 3.84 Mcps and 7.68 Mcps TDD. On the left, two DCH inputs go into a 'Coding and multiplexing' block, which outputs a Coded Composite Transport Channel (CCTrCH). This CCTrCH goes into a MUX block along with 'TPC & TFCI'. The output of this MUX is split into multiple Physical Channel Data Streams, each represented by a Phy CH block. In the center, an E-HICH (ACK/NACK) is shown with its own Phy CH block. On the right, an HS-DSCH goes through a 'Decoding' block to produce a CCTrCH, which then goes into another MUX block. This MUX block also receives inputs from a HS-SCCH (carrying TPC, E-AGCH Absolute Grant, and TFRI) and HARQ. The output of this second MUX is split into two Phy CH blocks. + +E-DCH model with HS-DSCH (no DCH) (1.28 Mcps TDD) + +![Block diagram of E-DCH model with HS-DSCH (no DCH) for 1.28 Mcps TDD. The diagram shows the flow from HS-DSCH through a Decoding block to a MUX block, resulting in a Coded Composite Transport Channel (CCTrCH). This CCTrCH is then split into three physical channels (Phy CH): E-HICH (ACK/NACK), HS-SCCH (carrying E-AGCH Absolute Grant, TFRI, HARQ, TPC, and SS), and HARQ. Each of these three channels is associated with its own Phy CH block.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +Block diagram of E-DCH model with HS-DSCH (no DCH) for 1.28 Mcps TDD. The diagram shows the flow from HS-DSCH through a Decoding block to a MUX block, resulting in a Coded Composite Transport Channel (CCTrCH). This CCTrCH is then split into three physical channels (Phy CH): E-HICH (ACK/NACK), HS-SCCH (carrying E-AGCH Absolute Grant, TFRI, HARQ, TPC, and SS), and HARQ. Each of these three channels is associated with its own Phy CH block. + +![Diagram of E-DCH with DCH and HS-DSCH (1.28 Mcps TDD) showing uplink and downlink processing.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +E-DCH with DCH and HS-DSCH (1.28 Mcps TDD) + +The diagram illustrates the E-DCH with DCH and HS-DSCH (1.28 Mcps TDD) architecture. On the uplink (left), two DCH transport channels are processed through 'Coding and multiplexing' to form a 'Coded Composite Transport Channel (CCTrCH)'. This is then multiplexed ('MUX') with 'TPC', 'TFCI', and 'SS' control information. The resulting 'Physical Channel Data Streams' are transmitted over 'Phy CH' blocks. On the downlink (right), 'HS-DSCH' data is processed through 'Decoding' to form a 'Coded Composite Transport Channel (CCTrCH)'. This is then multiplexed ('MUX') with 'TPC', 'SS', and 'HARQ info' (including 'TFRI'). The resulting 'Physical Channel Data Streams' are transmitted over 'Phy CH' blocks. In the center, control channels are shown: 'E-HICH' (ACK/NACK), 'E-AGCH' (Absolute Grant, TPC, SS), and 'HS-SCCH' (TFRI, HARQ info, TPC, SS), each associated with a 'Phy CH' block. + +Diagram of E-DCH with DCH and HS-DSCH (1.28 Mcps TDD) showing uplink and downlink processing. + +![Diagram of FACH model (transport channel combining case) showing data streams from multiple cells being combined.](474a819357587e34949a3e110ff19b30_img.jpg) + +FACH model +(transport channel combining case) + +The diagram illustrates the FACH model (transport channel combining case). At the bottom, data streams from 'Cell 1', 'Cell 2', and 'Cell 3' are shown. Each cell has two 'Phy CH' blocks. The streams from 'Cell 1' and 'Cell 2' are combined in a 'Frame based (CCTrCH) TrCH processing + de-mux' block. The output of this block is then processed by two 'Maximum Ratio Combining' blocks, which produce 'FACH1' and 'FACH2' transport channels. The streams from 'Cell 3' are also processed by the 'Frame based (CCTrCH) TrCH processing + de-mux' block, resulting in 'TFCI3'. The 'Frame based (CCTrCH) TrCH processing + de-mux' block also outputs 'TFCI1' for Cell 1 and 'TFCI2' for Cell 2. + +Diagram of FACH model (transport channel combining case) showing data streams from multiple cells being combined. + +E-DCH with HS-DSCH in CELL\_FACH (1.28 Mcps TDD) + +![Block diagram of E-DCH with HS-DSCH in CELL_FACH (1.28 Mcps TDD) showing signal flow from HS-DSCH through decoding and multiplexing to various physical channels.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +This diagram illustrates the signal flow for E-DCH with HS-DSCH in CELL\_FACH at 1.28 Mcps TDD. At the top, the HS-DSCH signal enters a 'Decoding' block. The output of this block is the 'Coded Composite Transport Channel (CCTrCH)'. This channel is then processed by a 'MUX' block. The MUX block has two inputs from below, both labeled 'Phy CH'. The output of the MUX block is connected to three 'Phy CH' blocks. Above the first 'Phy CH' block is the label 'E-HICH ACK/NACK'. Above the second 'Phy CH' block is the label 'E-AGCH Absolute Grant TPC, SS'. Above the third 'Phy CH' block is a box containing 'HS-SCCH TFRI HARQ TPC,SS'. + +Block diagram of E-DCH with HS-DSCH in CELL\_FACH (1.28 Mcps TDD) showing signal flow from HS-DSCH through decoding and multiplexing to various physical channels. + +HS-DSCH in CELL\_PCH and URA\_PCH (1.28 Mcps TDD) + +![Block diagram of HS-DSCH in CELL_PCH and URA_PCH (1.28 Mcps TDD) showing signal flow from HS-DSCH through decoding and multiplexing to various physical channels.](6470d350326789d5306eabcb76533951_img.jpg) + +This diagram illustrates the signal flow for HS-DSCH in CELL\_PCH and URA\_PCH at 1.28 Mcps TDD. At the top, the HS-DSCH signal enters a 'Decoding' block. The output of this block is the 'Coded Composite Transport Channel (CCTrCH)'. This channel is then processed by a 'MUX' block. The MUX block has two inputs from below, both labeled 'Phy CH'. The output of the MUX block is connected to three 'Phy CH' blocks. Above the first 'Phy CH' block is the label 'PI'. Above the second 'Phy CH' block is a box containing 'HS-SCCH TFRI HARQ TPC,SS'. + +Block diagram of HS-DSCH in CELL\_PCH and URA\_PCH (1.28 Mcps TDD) showing signal flow from HS-DSCH through decoding and multiplexing to various physical channels. + +![A large black rectangular area with a small grey rectangle at the bottom center and three grey rectangles at the bottom right, likely representing a placeholder or a corrupted image.](c80dd550f724de455f5efebaed25198d_img.jpg) + +A large black rectangular area, possibly a placeholder or a corrupted image. At the bottom center, there is a small grey rectangle. At the bottom right, there are three grey rectangles arranged horizontally. + +A large black rectangular area with a small grey rectangle at the bottom center and three grey rectangles at the bottom right, likely representing a placeholder or a corrupted image. + +![Figure 4: Model of the UE's physical layer - downlink TDD mode. The diagram shows a large black rectangle representing the physical channel. At the bottom of this rectangle, there are three small grey rectangles. Above the black rectangle, there are two grey rectangles, each with an upward-pointing arrow. The two grey rectangles are positioned such that they appear to be receiving data from the physical channel.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Figure 4: Model of the UE's physical layer - downlink TDD mode. The diagram shows a large black rectangle representing the physical channel. At the bottom of this rectangle, there are three small grey rectangles. Above the black rectangle, there are two grey rectangles, each with an upward-pointing arrow. The two grey rectangles are positioned such that they appear to be receiving data from the physical channel. + +**Figure 4: Model of the UE's physical layer - downlink TDD mode** + +For the DCH case, the mapping between DCHs and physical channel data streams works in the same way as for the uplink. Note however, that the number of DCHs, the coding and multiplexing etc. may be different in uplink and downlink. + +In the FDD mode, the differences are mainly due to the soft and softer handover. Further, the pilot, TPC bits and TFCI are time multiplexed onto the same physical channel(s) as the DCHs, in case of HS-DSCH(s) without a DCH in the DL TPC bits are carried onto F-DPCH(s). Further, the definition of physical channel data stream is somewhat different from the uplink. In TDD mode the TFCI is time multiplexed onto the same physical channel(s) as the DCHs. The exact locations and coding of the TFCI are signalled by higher layers. + +Note that it is logically one and the same physical data stream in the active set of cells, even though physically there is one stream for each cell. The same processing and multiplexing is done in each cell. The only difference between the cells is the actual codes, and these codes correspond to the same spreading factor. + +The physical channels carrying the same physical channel data stream are combined in the UE receiver, excluding the pilot, and in some cases the TPC bits. TPC bits received on certain physical channels may be combined provided that UTRAN has informed the UE that the TPC information on these channels is identical. + +A PCH and one or several FACH can be encoded and multiplexed together forming a CCTrCH. Similarly as in the DCH model there is one TFCI for each CCTrCH for indication of the transport formats used on each PCH and FACH. The PCH is associated with a separate physical channel carrying page indicators (PIs) which are used to trigger UE reception of the physical channel that carries PCH. A FACH or a PCH can also be individually mapped onto a separate physical channel. The BCH is always mapped onto one physical channel without any multiplexing with other transport channels, and there can only be one BCH TrCH and no other TrCH in a BCH CCTrCH. + +For point-to-multipoint transmission [14], FACH can be distributed on a set of physical layer combinable CCTrCHs, i.e., for macro-diversity combining: soft combining (FDD and TDD) or transport channel combining (TDD only). The physical layer combinable CCTrCHs shall have the same TFC during the TTIs in which soft combining can be used. The physical layer combinable CCTrCHs need not have the same TFC during the TTIs in which transport channel + +combining can be used. The possibility of performing macro-diversity combining (either soft combining or transport channel combining) shall be signalled to the UE. + +In the TDD mode a CCTrCh carrying PCH and one or several FACH can be multiplexed onto one or several physical channel data streams. + +For each HS-DSCH TTI, each HS-SCCH carries HS-DSCH-related downlink signalling for one UE when in CELL\_DCH state, or in FDD and 1.28Meps TDD mode for one UE or multiple UEs in CELL\_FACH, CELL\_PCH or URA\_PCH state. The following information is carried on the HS-SCCH: + +- Transport Format and Resource Indicator (TFRI); +- Hybrid-ARQ-related Information (HARQ information); +- UE Identity via a UE specific CRC; +- HS-SCCH Cyclic Sequence Number (HCSN) for TDD. + +In addition, for the case of 1.28 Meps TDD, the HS-SCCH also carries Transmit Power Control and Synchronisation Shift symbols. + +In FDD mode and CELL\_DCH state when MIMO mode is configured, single stream and dual stream transmission of HS-DSCH can be performed for each HS-DSCH TTI in the Serving HS-DSCH cell. In the case of dual stream transmission, two HS-DSCH transport blocks are transmitted to the UE per HS-DSCH TTI and the HS-SCCH includes information for both of these HS-DSCH transport blocks. When the UE is configured for Dual Cell HSDPA operation, one HS-DSCH transport channel is transmitted on each configured downlink frequency. Each of these HS-DSCH transport channels has its own associated uplink and downlink signalling, and own HARQ entity. When the UE is configured for Dual Band HSDPA operation, single stream transmission of HS-DSCH is performed for each HS-DSCH TTI on each configured downlink frequency. When the UE is configured to operate in Dual Cell HSDPA with MIMO mode, either or both of the HS-DSCH serving cells can be configured with MIMO operation, i.e. depending on the configuration up to four HS-DSCH transport blocks can be transmitted to UE per HS-DSCH TTI. When the UE is configured for Four Carrier HSDPA operation, there is one Serving HS-DSCH cell and up to three Secondary serving HS-DSCH cells. When the UE is configured for Eight Carrier HSDPA operation, there is one Serving HS-DSCH cell and up to seven Secondary serving HS-DSCH cells. When MIMO is not configured on any of the serving or secondary serving HS-DSCH cells, one HS-DSCH transport channel is transmitted on each configured serving and secondary serving HS-DSCH cells, and each of these HS-DSCH transport channels has its own associated uplink and downlink signalling, and its own HARQ entity. Further, a UE may be configured for Four Carrier HSDPA or Eight Carrier HSDPA operation with MIMO mode on any of the serving or secondary serving HS-DSCH cells. Depending on the MIMO configuration up to sixteen HS-DSCH transport blocks can be transmitted to the UE per HS-DSCH TTI. + +In FDD mode and CELL\_DCH state when MIMO mode with four transmit antennas is configured, single stream, dual stream, three streams and four streams transmissions of HS-DSCH can be performed for each HS-DSCH TTI in the Serving HS-DSCH cell and the Secondary serving HS-DSCH cells. In case of dual/three/four stream transmission the respective number of HS-DSCH transport blocks are transmitted to the UE and the HS-SCCH includes information for the transmitted HS-DSCH transport blocks. When the UE is configured to operate in Dual Cell HSDPA and MIMO mode with four transmit antennas, either or both of the Serving HS-DSCH cells can be configured in MIMO mode with four transmit antennas. Further, a UE may be configured with Four Carrier HSDPA operation in MIMO mode with four transmit antennas on any of the serving or Secondary serving HS-DSCH cells. Depending on the MIMO mode with four transmit antennas configuration up to sixteen HS-DSCH transport blocks can be transmitted to the UE per HS-DSCH TTI. + +In FDD mode and CELL\_DCH state when Multiflow is configured, two HS-DSCH cells can be configured on the same frequency. The HS-DSCH cells can belong either to the same Node B (intra-Node B configuration), or two different Node Bs (inter-Node B configuration). Each HS-DSCH transport channel has its own associated uplink and downlink signalling, and own HARQ entity. When a UE is configured to operate in Multiflow and MIMO mode, each HS-DSCH serving and assisting cell can be configured independently with MIMO operation. When MIMO mode is configured, single stream and dual stream transmission of HS-DSCH can be performed for each HS-DSCH TTI in the serving, or assisting serving, or (assisting) secondary serving HS-DSCH cell. + +The Multiflow assisting serving cell on the primary frequency must be part of the UE active set. When a UE is configured to operate in Multiflow operation on four cells on two frequencies and Dual Cell E-DCH operation, the Multiflow assisting secondary serving cell must be part of the UE active set on the secondary uplink frequency. + +In TDD mode, HS-DSCH operation is supported without an associated DL DPCH. + +In FDD mode, if the UE is in CELL\_DCH state, the E-DCH active set can be identical or a subset of the DCH active set. If the UE is in CELL\_FACH state or Idle mode, the UE's E-DCH active set consists of a single serving cell. If Dual Cell E-DCH operation is configured in CELL\_DCH state, DCH is not supported in uplink and downlink. The active set and E-DCH active set on both uplink frequencies are independent, but the Serving E-DCH cells in both E-DCH active sets belong to the same Node B. On secondary uplink frequency the active set and E-DCH active set have the same size. + +For FDD: The E-DCH ACK/NACKs are transmitted by each cell of the E-DCH active set on a physical channel called E-HICH. The E-HICHs of the cells belonging to the same RLS (same MAC-e entity i.e. same Node B) shall have the same content and be combined by the UE. The set of cells transmitting identical ACK/NACK information is the same as the set of cells sending identical TPC bits (excluding the cells which are not in the E-DCH active set). + +For 3.84 Mcps and 7.68 Mcps TDD: The E-DCH ACK/NACKs are transmitted via the current serving cell on a physical channel called the E-HICH. + +For 1.28 Mcps TDD: For each uplink frequency, an E-DCH ACK/NACK is transmitted via the current serving cell on the E-HICH indicated on E-AGCH. + +The E-DCH Absolute Grant is transmitted by a single cell, the Serving E-DCH cell (Cell $e_s$ on figure 3) on a physical channel called E-AGCH. The Serving E-DCH cell and the HS-DSCH Serving cell are identical except when Serving E-DCH cell decoupling operation is configured (i.e. Cell $e_s \neq$ Cell 1 on figure 3). + +The E-DCH Relative Grants (FDD only) can be transmitted by each cell of the E-DCH active set on a physical channel called E-RGCH. The E-RGCHs of the cells belonging to the same serving E-DCH RLS shall have the same content and be combined by the UE. There is one Serving E-DCH RLS (containing the Serving E-DCH cell) and optionally one or several Non-serving E-DCH RL(s). + +In FDD mode and CELL\_DCH state when Dual Cell E-DCH operation is configured, for each activated uplink frequency the F-DPCH, E-AGCH, E-RGCH and E-HICH are transmitted on the corresponding downlink frequency. The E-DCH Absolute Grant and E-DCH Relative Grants are provided per uplink frequency. + +In FDD mode and CELL\_DCH state when uplink CLTD is configured, the corresponding Transmitted Precoding Indicator is carried on the F-TPICH. The F-TPICH is either transmitted by a single cell which determines the precoding weights, or transmitted by all the cells within the RLS that the cell which determines the precoding weights belongs to. + +In FDD mode and CELL\_DCH state, when uplink MIMO is configured, the corresponding Transmitted Precoding Indicator is carried on the F-TPICH. The F-TPICH is either transmitted by the serving E-DCH cell, or transmitted by all the cells within the RLS that the serving E-DCH cell belongs to. The E-ROCH physical channel, which is transmitted by the serving E-DCH cell, provides additional information on the transmission rank and offset. + +In FDD mode and in CELL\_DCH state, when Radio Links without DPCH/F-DPCH is configured, a subset of indicated Non-serving E-DCH radio links in the UE's E-DCH active could be operated without the presence of F-DPCH or DPCH, i.e. UE is required to only receive E-HICH and optionally E-RGCH from the indicated Non-serving E-DCH cell(s). + +In FDD mode and CELL\_DCH state, when DPCCH2 is configured, in addition to the DL DPCCH/F-DPCH, another F-DPCH is transmitted by the serving HS-DSCH cell to carry TPC commands for the introduced DPCCH2 channel. + +# --- 7 Formats and configurations for L1 data transfer + +## 7.1 General concepts about Transport Channels + +Layer 2 is responsible for the mapping of data onto L1 via the L1/L2 interface that is formed by the transport channels. In order to describe how the mapping is performed and how it is controlled, some definitions and terms are required. The required definitions are given in the following subclauses. Note that the definitions are generic for all transport channel types, i.e. not only for DCHs. + +All Transport Channels are defined as unidirectional (i.e. uplink or downlink). This means that a UE can have simultaneously (depending on the services and the state of the UE) one or several transport channels in the downlink, and one or more Transport Channel in the uplink. + +### 7.1.1 Transport Block + +This is the basic unit exchanged between L1 and MAC, for L1 processing. + +Layer 1 adds a CRC for each Transport Block. + +### 7.1.2 Transport Block Set + +This is defined as a set of Transport Blocks, which are exchanged between L1 and MAC at the same time instance using the same transport channel. + +In case of HS-DSCH and E-DCH the Transport Block Set consists of one Transport Block only. + +### 7.1.3 Transport Block Size + +This is defined as the number of bits in a Transport Block. The Transport Block Size is always fixed within a given Transport Block Set, i.e. all Transport Blocks within a Transport Block Set are equally sized. + +### 7.1.4 Transport Block Set Size + +This is defined as the number of bits in a Transport Block Set. + +### 7.1.5 Transmission Time Interval + +This is defined as the inter-arrival time of Transport Block Sets, and is equal to the periodicity at which a Transport Block Set is transferred by the physical layer on the radio interface. It is always a multiple of the minimum interleaving period (e.g. 10ms, the length of one Radio Frame). The MAC delivers one Transport Block Set to the physical layer every TTI. + +Figure 6 shows an example where Transport Block Sets, at certain time instances, are exchanged between MAC and L1 via three parallel transport channels. Each Transport Block Set consists of a number of Transport Blocks. The Transmission Time Interval, i.e. the time between consecutive deliveries of data between MAC and L1, is also illustrated. + +![Figure 6: Exchange of data between MAC and L1. The diagram illustrates four transport channels (DCH1, DCH2, DCH3, and HS-DSCH) over time. Each channel shows Transport Blocks being transmitted within Transmission Time Intervals (TTIs). DCH1 shows one Transport Block per TTI. DCH2 shows three Transport Blocks per TTI. DCH3 shows five Transport Blocks per TTI. HS-DSCH shows one Transport Block per TTI.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The diagram illustrates the exchange of data between MAC and L1 across four transport channels over time. Each channel is represented by a horizontal timeline with arrows indicating the direction of data flow. Transport Blocks are shown as rectangular boxes above the timeline, and Transmission Time Intervals (TTIs) are indicated by double-headed arrows below the timeline. + +- DCH1:** Shows a single Transport Block within each TTI. +- DCH2:** Shows three Transport Blocks within each TTI. +- DCH3:** Shows five Transport Blocks within each TTI. +- HS-DSCH:** Shows a single Transport Block within each TTI. + +Figure 6: Exchange of data between MAC and L1. The diagram illustrates four transport channels (DCH1, DCH2, DCH3, and HS-DSCH) over time. Each channel shows Transport Blocks being transmitted within Transmission Time Intervals (TTIs). DCH1 shows one Transport Block per TTI. DCH2 shows three Transport Blocks per TTI. DCH3 shows five Transport Blocks per TTI. HS-DSCH shows one Transport Block per TTI. + +Figure 6: Exchange of data between MAC and L1 + +### 7.1.6 Transport Format + +This subclause applies to transport channel types other than HS-DSCH and E-DCH. + +This is defined as a format offered by L1 to MAC (and vice versa) for the delivery of a Transport Block Set during a Transmission Time Interval on a Transport Channel. The Transport Format constitutes of two parts – one *dynamic* part and one *semi-static* part. + +Attributes of the dynamic part are: + +- Transport Block Size; +- Transport Block Set Size; +- Transmission Time Interval (optional dynamic attribute for TDD only); + +Attributes of the semi-static part are: + +- Transmission Time Interval (mandatory for FDD, optional for the dynamic part of TDD NRT bearers); +- error protection scheme to apply: + - type of error protection, turbo code, convolutional code or no channel coding (TDD only); + - coding rate; + - static rate matching parameter; + +- size of CRC. + +In the following example, the Transmission Time Interval is seen as a semi-static part. + +#### EXAMPLE: + +Dynamic part: {320 bits, 640 bits}, Semi-static part: {10ms, convolutional coding only, static rate matching parameter = 1}. + +An empty Transport Format is defined as a Transport Format that has Block Set Size equal to zero. + +For the two realisations of an empty Transport Format, see clause 11. + +### 7.1.6a Transport Format for HS-DSCH + +This is defined as a format offered by L1 to MAC (and vice versa) for the delivery of a transport block during a Transmission Time Interval on a Transport Channel. The Transport Format consists of three parts – one *dynamic* part, one *semi-static* part and one *static* part. + +The Transport Format for HS-DSCH is always explicitly signalled. There is no support of blind transport format detection. + +Attributes of the dynamic part are: + +- Transport block size (same as Transport block set size); +- Redundancy version/Constellation; +- Modulation scheme. + +Attributes of the semi-static part are: + +- no semi-static attributes are defined. + +Attributes of the static part are: + +- Transmission time interval. The Transmission time interval is fixed to 2ms in FDD, 10ms in 3.84/7.68 Mcps TDD and 5ms in 1.28 Mcps TDD. +- error protection scheme to apply: + - type of error protection is turbo coding; + - coding rate is 1/3; + - size of CRC is 24 bits. + +### 7.1.7 Transport Format for E-DCH + +This is defined as a format offered by L1 to MAC (and vice versa) for the delivery of a transport block during a Transmission Time Interval on a Transport Channel. The Transport Format consists of three parts – one *dynamic* part, one *semi-static* part and one *static* part. + +The Transport Format for E-DCH is always explicitly signalled. There is no support of blind transport format detection. + +Attributes of the dynamic part are: + +- Transport block size (same as Transport block set size); +- Redundancy version; + +Attributes of the semi-static part are: + +- Transmission Time Interval. For FDD, both Transmission time interval of 2ms and 10 ms are supported; for 3.84 Mcps and 7.68 Mcps TDD only a Transmission time interval of 10 ms is supported, for 1.28 Mcps TDD only a transmission time interval of 5 ms is supported. + +Attributes of the static part are: + +- error protection scheme to apply: + - type of error protection is turbo coding; + - coding rate is 1/3; + - size of CRC is 24 bits.7.1. + +### 7.1.7a Transport Format Set + +This is defined as the set of Transport Formats associated to a Transport Channel. + +The semi-static parts of all Transport Formats are the same within a Transport Format Set. + +Effectively the Transport Block Size and Transport Block Set Size form the instantaneous bit rate on the Transport Channel. Variable bit rate on a Transport Channel may, depending on the type of service, which is mapped onto the transport channel, be achieved by changing between each Transmission Time Interval one of the following: + +1. the Transport Block Set Size only (not applicable for HS-DSCH and E-DCH); +2. both the Transport Block Size and the Transport Block Set Size + +Example 1 for DCHs: + +- dynamic part: {20 bits, 20 bits}; {40 bits, 40 bits}; {80 bits, 80 bits}; {160 bits, 160 bits}. +- Semi-static part: {10ms, Convolutional coding only, static rate matching parameter = 1} + +Example 2 for DCHs: + +- dynamic part: {320 bits, 320 bits}; {320 bits, 640 bits}; {320 bits, 1 280 bits}. +- Semi-static part: {10ms, Convolutional coding only, static rate matching parameter = 2}. + +Example 3 for HS-DSCH: + +- dynamic part: {320 bits, 320 bits, Redundancy version 1, QPSK}; {640, 640, Redundancy version 1, QPSK}; {1280, 1280, Redundancy version 2, 16QAM}. +- static part: See subclause 7.1.6a. + +Example 4 for E-DCH: + +- dynamic part: {320 bits, 320 bits, Redundancy version 0}; {320 bits, 320 bits, Redundancy version 1}; {640, 640, Redundancy version 0 }; {640, 640, Redundancy version 1 }; +- Semi-static part: {10ms}. +- static part: See subclause 7.1.7. + +The first example may correspond to a Transport Channel carrying a speech service, requiring blocks delivered on a constant time basis. In the second example, which illustrates the situation where a non-real time service is carried by the Transport Channel, the number of blocks delivered per Transmission Time Interval varies between the different Transport Formats within the Transport Format Set. Referring to figure 6, the Transport Block Size is varied on DCH1 and DCH2. That is, a Transport Format Set where the dynamic part has a variable Transport Block Size has been assigned for DCH1. On DCH3 it is instead only the Transport Block Set Size that is varied. That is, the dynamic parts of the corresponding Transport Format Sets only include variable Transport Block Set Sizes. + +### 7.1.8 Transport Format Combination + +The layer 1 multiplexes one or several Transport Channels, and for each Transport Channel, there exists a list of transport formats (Transport Format Set) which are applicable. Nevertheless, at a given point of time, not all combinations may be submitted to layer 1 but only a subset, the Transport Format Combination. This is defined as an authorised combination of the combination of currently valid Transport Formats that can be submitted simultaneously to the layer 1 for transmission on a Coded Composite Transport Channel of a UE, i.e. containing one Transport Format from each Transport Channel. + +EXAMPLE: + +DCH1: + +Dynamic part: {20 bits, 20 bits}, Semi-static part: {10ms, Convolutional coding only, static rate matching parameter = 2}; + +DCH2: + +Dynamic part: {320 bits, 1 280 bits}, Semi-static part: {10ms, Convolutional coding only, static rate matching parameter = 3}; + +DCH3: + +Dynamic part: {320 bits, 320 bits}, Semi-static part: {40ms, Turbo coding, static rate matching parameter = 2}. + +An empty Transport Format Combination is defined as a Transport Format Combination that is only made up of empty Transport Formats. + +### 7.1.9 Transport Format Combination Set + +This is defined as a set of Transport Format Combinations on a Coded Composite Transport Channel. + +EXAMPLE for DCHs: + +- dynamic part: + - combination 1: DCH1: {20 bits, 20 bits}, DCH2: {320 bits, 1280 bits}, DCH3: {320 bits, 320 bits}; + - combination 2: DCH1: {40 bits, 40 bits}, DCH2: {320 bits, 1280 bits}, DCH3: {320 bits, 320 bits}; + - combination 3: DCH1: {160 bits, 160 bits}, DCH2: {320 bits, 320 bits}, DCH3: {320 bits, 320 bits} +- semi-static part: + - DCH1: {10ms, Convolutional coding only, static rate matching parameter = 1}; + - DCH2: {10ms, Convolutional coding only, static rate matching parameter = 1}; + - DCH3: {40ms, Turbo coding, static rate matching parameter = 2}. + +The Transport Format Combination Set is what is given to MAC for control. However, the assignment of the Transport Format Combination Set is done by L3. When mapping data onto L1, MAC chooses between the different Transport Format Combinations given in the Transport Format Combination Set. Since it is only the dynamic part that differ between the Transport format Combinations, it is in fact only the dynamic part that MAC has any control over. + +The semi-static part, together with the target value for the L1 closed loop power control, correspond to the service attributes: + +- quality (e.g. BER); +- transfer delay. + +These service attributes are then offered by L1. However, it is L3 that guarantees that the L1 services are fulfilled since it is in charge of controlling the L1 configuration, i.e. the setting of the semi-static part of the Transport Formats. Furthermore, L3 controls the target for the L1 closed loop power control through the outer loop power control (which actually is a quality control rather than a power control). + +Note that a Transport Format Combination Set need not contain all possible Transport Format Combinations that can be formed by Transport Format Sets of the corresponding Transport Channels. It is only the allowed combinations that are included. Thereby a maximum total bit rate of all transport channels of a Code Composite Transport Channel can be set appropriately. That can be achieved by only allowing Transport Format Combinations for which the included Transport Formats (one for each Transport Channel) do not correspond to high bit rates simultaneously. + +The selection of Transport Format Combinations can be seen as a fast part of the radio resource control. The dedication of these fast parts of the radio resource control to MAC, close to L1, means that the flexible variable rate scheme provided by L1 can be fully utilised. These parts of the radio resource control should be distinguished from the slower parts, which are handled by L3. Thereby the bit rate can be changed very fast, without any need for L3 signalling. + +### 7.1.10 Transport Format Indicator (TFI) + +The TFI is a label for a specific transport format within a transport format set. It is used in the inter-layer communication between MAC and L1 each time a transport block set is exchanged between the two layers on a transport channel. + +When the DSCH is associated with a DCH, the TFI of the DSCH also indicates the physical channel (i.e. the channelisation code) of the DSCH that has to be listened to by the UE. + +### 7.1.11 Transport Format Combination Indicator (TFCI) + +This is a representation of the current Transport Format Combination. + +There is a one-to-one correspondence between a certain value of the TFCI and a certain Transport Format Combination. The TFCI is used in order to inform the receiving side of the currently valid Transport Format Combination, and hence how to decode, de-multiplex and deliver the received data on the appropriate Transport Channels. The TFCI is not used for the HS-DSCH and E-DCH. + +MAC indicates the TFI to Layer 1 at each delivery of Transport Block Sets on each Transport Channel. Layer 1 then builds the TFCI from the TFIs of all parallel transport channels of the UE, processes the Transport Blocks appropriately and appends the TFCI to the physical control signalling. Through the detection of the TFCI the receiving side is able to identify the Transport Format Combination. For FDD, in case of limited Transport Format Combination Sets the TFCI signalling may be omitted, instead relying on blind detection. Nevertheless, from the assigned Transport Format Combinations, the receiving side has all information it needs in order to decode the information and transfer it to MAC on the appropriate Transport Channels. + +The multiplexing and exact rate matching patterns follow predefined rules and may therefore be derived (given the Transport Format Combinations) by transmitter and receiver without signalling over the radio interface. + +When the meaning of the TFCI field needs to be reconfigured, two procedures can be used depending on the level of reconfiguration: + +- **complete reconfiguration of TFCI:** in this procedure all TFCI values are reinitialised and new values are defined instead. The complete reconfiguration requires an explicit synchronisation between the UE and UTRAN regarding when the reconfiguration becomes valid. +- **incremental reconfiguration of TFCI:** in this procedure, a part of the TFCI values before and after the reconfiguration remain identical (note that this must be true for at least a TFCI that carry the signalling connection). This procedure supports addition, removal or redefinition of TFCI values. This procedure does not require an explicit execution time. This procedure may imply the loss of some user-plane data. + +### 7.1.12 Rate matching + +Two levels of rate matching are defined on the radio interface: + +- a static rate matching per Transport Channel. The static rate matching is part of the semi-static attributes of the Transport Channel. Static rate matching is not applicable to HS-DSCH; +- a dynamic rate matching per CCTrCH. The dynamic rate matching adjusts the size of the physical layer data payload to the physical channel as requested by RRC. + +The static rate matching and the dynamic rate matching to be applied by the physical layer are indicated by RRC to the physical layer. + +In FDD, RRC is also responsible for configuring the physical layer on whether: + +- Blind Rate Detection or TFCI is used; +- dynamic rate matching is applied or not on the downlink. + +### 7.1.13 HARQ information + +Hybrid ARQ is defined for HS-DSCH and E-DCH. For HS-DSCH with the help of the HARQ information the UE is enabled to identify the process being used for the transport block that is received on the HS-DSCH. For FDD E-DCH the + +HARQ process is derived in an implicit way. For TDD E-DCH the HARQ process identifier is signalled via the E-UCCH. For both HS-DSCH and E-DCH the HARQ information also includes information that indicates whether a new data block is transmitted for the first time or a retransmission. Furthermore it is used to decode the received data correctly. For FDD, the redundancy version is either explicitly indicated as part of the HARQ information (for the HS-DSCH) or is derived from the retransmission indicator (RSN) and the CFN and in case of 2ms TTI additionally from sub-frame number (for the E-DCH). For TDD, the redundancy version is either explicitly indicated as part of the HARQ information (for the HS-DSCH) or is derived from the retransmission indicator (RSN). + +### 7.1.14 Transport Format and Resource Indication (TFRI) + +The TFRI includes information about the dynamic part of the HS-DSCH transport format, including transport block set size and modulation scheme. The TFRI also includes information about the set of physical channels (channelisation codes) onto which HS-DSCH is mapped in the corresponding HS-DSCH TTI. + +### 7.1.15 E-DCH Transport Format Combination Indication (E-TFCI) + +The E-TFCI includes information about the transport block set size. + +## 7.2 Types of Transport Channels + +A general classification of transport channels is into two groups: + +- common channels; and +- dedicated channels (where the UEs can be unambiguously identified by the physical channel, i.e. code and frequency). + +Common transport channel types are: + +1. Random Access Channel(s) (RACH) characterised by: + - existence in uplink only; + - limited data field; + - collision risk; + - open loop power control. +2. Forward Access Channel(s) (FACH) characterised by: + - existence in downlink only; + - possibility to use slow power control; + - possibility to change rate fast (each 10ms); and + - lack of inner loop power control. +3. Broadcast Channel (BCH) characterised by: + - existence in downlink only; + - low fixed bit rate; and + - requirement to be broadcast in the entire coverage area of the cell. +4. Paging Channel (PCH) characterised by: + - existence in downlink only; + - association with a physical layer signal, the Page Indicator, to support efficient sleep mode procedures; and + - requirement to be broadcast in the entire coverage area of the cell. +5. Downlink Shared Channel(s) (DSCH) characterised by: + +- used in TDD only; +- existence in downlink only; +- possibility to use beamforming; +- possibility to use slow power control; +- possibility to use inner loop power control, when associated with dedicated channel(s); +- possibility to be broadcast in the entire cell; +- always associated with another channel (DCH or FACH). + +### 6. Uplink Shared channel (USCH) characterised by: + +- used in TDD only; +- existence in uplink only; +- possibility to use beam forming; +- possibility to use power control; +- possibility to change rate fast; +- possibility to use Uplink Synchronisation; +- possibility to use Timing advance. + +### 7. High Speed Downlink Shared Channel (HS-DSCH) characterised by: + +- existence in downlink only; +- possibility to use beamforming; +- possibility to use MIMO; +- possibility to use MIMO mode with four transmit antennas; +- for FDD, possibility to be configured into Dual Cell operation; +- for FDD, possibility to be configured into Dual Band operation; +- for FDD, possibility to be configured into Four Carrier operation; +- for FDD, possibility to be configured into Eight Carrier operation; +- for FDD, possibility to be configured into the Multiflow operation; +- for FDD, possibility to be configured into DPCCH2 operation; +- possibility of applying HARQ; +- possibility of applying link adaptation by varying the modulation, coding and transmit power; +- possibility to be broadcast in the entire cell; +- associated with a DPCH or F-DPCH (CELL\_DCH state only) and one or more shared physical control channel. +- In FDD and 1.28Mcps TDD, in CELL\_FACH, CELL\_PCH and URA\_PCH states associated with one or more shared physical control channel. + +### 8. Dedicated Channel (E-DCH) characterised by (FDD and 1.28Mcps TDD only): + +- existing in uplink only for CELL\_FACH state and Idle mode; +- for FDD, collision risk, with collision resolution possible if E-RNTI is allocated to the UE; + +- for 1.28Mcps TDD, E-RNTI collision risk, with collision resolution possible in case of CCCH transmission; +- possibility to change rate fast (each TTI) after collision resolution; +- inner loop power control; +- possibility of applying HARQ; +- possibility of applying link adaptation by varying the coding and transmit power; +- for FDD, E-DCH is always associated with a DPCCH and one or more physical control channel. +- for 1.28Mcps TDD, E-DCH is always associated with uplink and downlink physical control channels. + +Dedicated transport channel type: + +1. Dedicated Channel (DCH) characterised by: + - existing in uplink or downlink; + - for FDD and in uplink, possibility to be configured into CLTD operation; + - possibility to use beam forming; + - possibility to change rate fast (each 10ms); + - inner loop power control; + - possibility to use timing advance in uplink (TDD only); + - possibility to use Uplink Synchronisation. +2. Dedicated Channel (E-DCH) characterised by: + - existing in uplink only; + - for FDD, possibility to be configured into Dual Cell operation; + - for FDD, possibility to be configured into CLTD operation; + - for FDD, possibility to be configured into uplink MIMO operation; + - for FDD, possibility to be configured into radio links without DPCH/F-DPCH; + - possibility to change rate fast (each TTI); + - inner loop power control; + - possibility of applying HARQ; + - possibility of applying link adaptation by varying the coding and transmit power; + - For FDD, E-DCH is always associated with a DPCCH and one or more physical control channel. + - For TDD, E-DCH is always associated with uplink and downlink physical control channels. + - For 1.28 Mcps TDD, the possibility to be configured into multi-carrier operation. + +To each transport channel, there is an associated Transport Format (for transport channels with a fixed or slow changing rate) or an associated Transport Format Set (for transport channels with fast changing rate). + +## 7.3 Compressed Mode + +Compressed Mode is defined as the mechanism whereby certain idle periods are created in radio frames so that the UE can perform measurements during these periods (more details can be found in [3]). + +Compressed Mode is obtained by layer 2 using transport channels provided by the layer 1 as follows: + +- compressed mode is controlled by the RRC layer, which configures the layer 2 and the physical layer; +- the number of occurrences of compressed frames is controlled by RRC, and can be modified by RRC signalling; +- it is under the responsibility of the layer 2 if necessary and if possible to either buffer some layer 2 PDUs (typically at the RLC layer for NRT services) or to rate-adapt the data flow (similarly to GSM) so that there is no loss of data because of compressed mode. This will be service dependent and controlled by the RRC layer. + +For measurements in compressed mode, a transmission gap pattern sequence is defined. A transmission gap pattern sequence consists of alternating transmission gap patterns 1 and 2, and each of these patterns in turn consists of one or two transmission gaps. The transmission gap pattern structure, position and repetition are defined with physical channel parameters described in [6]. In addition, the UTRAN configures compressed mode pattern sequences with the following parameters: + +- **TGMP:** Transmission Gap pattern sequence Measurement Purpose: This parameter defines the purpose this transmission gap pattern sequence is intended for. The following values are used: + - for TDD measurements, one compressed mode pattern sequence can be configured with purpose 'TDD measurement', + - for FDD measurements, one compressed mode pattern sequence can be configured with purpose 'FDD measurement', + - for GSM measurements, three simultaneous compressed mode pattern sequences can be configured with purposes 'GSM carrier RSSI measurement', 'Initial BSIC identification' and 'BSIC re-confirmation', +- **TGPSI:** Transmission Gap Pattern Sequence Identifier selects the compressed mode pattern sequence for which the parameters are to be set. The range of TGPSI is [1 to ]. + +The UE shall support a total number of simultaneous compressed mode pattern sequences, which is determined by the UE's capability to support each of the measurement types categorised by the TGMP. For example, a UE supporting FDD and GSM shall support four simultaneous compressed mode pattern sequences and a UE supporting FDD and TDD shall support two simultaneous compressed mode pattern sequences. + +When using simultaneous pattern sequences, it is the responsibility of the NW to ensure that the compressed mode gaps do not overlap and are not scheduled to overlap the same frame. Gaps exceeding the maximum gap length shall not be processed by the UE and shall interpreted as a faulty message. If the UE detects overlapping gaps, it shall process the gap from the pattern sequence having the lowest TGPSI. + +# --- 8 UE Simultaneous Physical Channels combinations + +This clause describes the requirements from the UE to send and receive on multiple Transport Channels, which are mapped on different physical channels simultaneously depending on the service capabilities and requirements. The clause will describe the impacts on the support for multiple services (e.g. speech call and SMS-CB) depending on the UE capabilities. + +## 8.1 FDD Uplink + +The table 1-1 describes the possible combinations of FDD physical channels that can be supported in the uplink on the same frequency by one UE simultaneously. + +Table 1-1: FDD Uplink + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|--------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | PRACH | RACH | Mandatory | The PRACH physical channel includes the preambles and the message. | +| 2 | (Void) | | | | +| 3 | DPCCH+DPDCH | One or more DCH coded into a single CCTrCH | Mandatory | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 4 | DPCCH+ more than one DPDCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 5 | DPCCH+one or more DPDCH+ HS-DPCCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink. | +| 6 | DPCCH+one or more DPDCH+E-DPCCH+one or more E-DPDCH | One or more DCH coded into a single CCTrCH + One E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 7 | DPCCH+one or more DPDCH+ HS-DPCCH+E-DPCCH+ one or more E-DPDCH | One or more DCH coded into a single CCTrCH + One E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink. | +| 8 | DPCCH+HS-DPCCH+E-DPCCH+ one or more E-DPDCH | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink. | +| 9 | DPCCH+E-DPCCH+ one or more E-DPDCH | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink. | +| 10 | DPCCH+one or more DPDCH+ +S-DPCCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination CLTD is configured in uplink. | +| 11 | DPCCH+one or more DPDCH+ HS-DPCCH+S-DPCCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink. | +| 12 | DPCCH+one or more DPDCH+ HS-DPCCH+E-DPCCH+ one or more E-DPDCH +S-DPCCH | One or more DCH coded into a single CCTrCH + One E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink. | +| 13 | DPCCH+HS-DPCCH+E-DPCCH+ one or more E-DPDCH +S-DPCCH | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink. | +| 14 | DPCCH+HS-DPCCH+E-DPCCH+ S-E-DPCCH+one or more E-DPDCH +S-DPCCH+one or more S-E-DPDCH | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and MIMO is configured in uplink. | +| 15 | DPCCH+one or more DPDCH+ HS-DPCCH+DPCC H2 | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and DPCCCH2 is configured. | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|---------------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 16 | DPCH+one or more DPDCH+ HS-DPCCH+E-DPCCH+ one or more E-DPDCH+ DPCCH2 | One or more DCH coded into a single CCTrCH + One E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and DPCCH2 is configured. | +| 17 | DPCH+HS-DPCCH+E-DPCCH+ one or more E-DPDCH+DPCH H2 | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and DPCCH2 is configured. | +| 18 | DPCH+one or more DPDCH+ HS-DPCCH+S-DPCCH+DPCH H2 | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink and DPCCH2 is configured. | +| 19 | DPCH+one or more DPDCH+ HS-DPCCH+E-DPCCH+ one or more E-DPDCH +S-DPCCH+DPCH H2 | One or more DCH coded into a single CCTrCH + One E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink and DPCCH2 is configured. | +| 20 | DPCH+HS-DPCCH+E-DPCCH+ one or more E-DPDCH +S-DPCCH+DPCH H2 | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink and CLTD is configured in uplink and DPCCH2 is configured. | +| 21 | DPCH+HS-DPCCH+E-DPCCH+ S-E-DPCCH+one or more E-DPDCH +S-DPCCH+one or more S-E-DPDCH+DPCH H2 | One E-DCH | Depending on UE radio access capabilities | The maximum bit rate is dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured in downlink, MIMO is configured in uplink and DPCCH2 is configured. | + +The table 1-2 describes the possible combinations of FDD physical channels that can be supported in the uplink on two configured uplink frequencies by one UE simultaneously. + +**Table 1-2: FDD Uplink** + +| Physical Channel Combination | Physical Channel Combination on Primary uplink frequency | Physical Channel Combination on Secondary uplink frequency | Mandatory or dependent on UE radio access capabilities | Comment | +|-------------------------------------|-----------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| A | 8 | 9 | Depending on UE radio access capabilities | In this combination HS-DSCH(s) are configured on each corresponding downlink frequency. | +| B | 17 | 9 | Depending on UE radio access capabilities | In this combination HS-DSCH(s) are configured on each corresponding downlink frequency. | +| C | 7 | 9 | Depending on UE radio access capabilities | In this combination HS-DSCH(s) are configured on each corresponding downlink frequency. | + +## 8.2 FDD Downlink + +The table 2-1 describes the possible combinations of FDD physical channels that can be supported in the downlink on the same frequency by one UE simultaneously. + +**Table 2-1: FDD Downlink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|---------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | PCCPCH | BCH | Mandatory | | +| 2 | SCCPCH | One or more FACH
Or
PCH
Or
one or more FACH + PCH | Mandatory | The maximum channel bit rate that can be supported is dependent on the UE radio access capabilities.
The PCH is included when the UE needs to receive paging on the SCCPCH.
The reception of (one or more FACH + PCH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. | +| 3 | PCCPCH + SCCPCH | BCH + (one or more FACH or PCH or (one or more FACH + PCH)) | Mandatory | Simultaneous reception of PCCPCH and SCCPCH is only needed at occurrences when the UE needs to read system information on BCH while being in CELL_FACH state, i.e. continuous reception of both PCCPCH and SCCPCH at the same time is not required.
The requirement holds for PCCPCH and SCCPCH sent in different cells or in the same cell.
The PCH is included when the UE needs to receive paging on the SCCPCH.
The reception of (one or more FACH + PCH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. | +| 4 | SCCPCH + AICH | (One or more FACH or PCH or (one or more FACH + PCH))+ RACH in uplink | Mandatory | The maximum channel bit rate that can be supported is dependent on the UE radio access capabilities.
The PCH is included when the UE needs to receive paging on the SCCPCH.
The reception of (one or more FACH + PCH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. | +| 5 | (Void) | | | | +| 6 | More than one SCCPCH | More than one (one or more FACH or PCH or (one or more FACH + PCH)) | Depending on UE radio access capabilities | The PCH is included when the UE needs to receive paging on the SCCPCH.
The reception of (one or more FACH + PCH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH.
One or more FACHs are used to enable the reception of MBMS (i.e., MCCH, MSCH and MTCH). The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. The combination includes the case where one or more MBMS FACHs are transmitted on the same SCCPCH as used for non-MBMS FACH or PCH. | +| 7 | PICH | N/A | Mandatory | | +| 8 | DPCCH + DPDCH | One or more DCH coded into a single CCTrCH | Mandatory | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 9 | DPCCH + more than one DPDCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 10 | (Void) | | | | +| 11 | (Void) | | | | +| 12 | (Void) | | | | +| 13 | One DPCCH + more than one DPDCH | More than one DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 14 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH | BCH (neighbour cell) + one or more DCHs | Mandatory | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements. | +| 15 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. NOTE | +| 16 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. NOTE | +| 17 | DPCCH + one or more DPDCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH | One or more DCH coded into a single CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH is configured in uplink. | +| 18 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH is configured in uplink. NOTE | +| 19 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH is configured in uplink. NOTE | +| 20 | F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH | HS-DSCH | Depending on UE radio access capabilities | The maximum channel bit rate is dependent on UE radio access capabilities. NOTE | +| 21 | PCCPCH (neighbour cell) + F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH | BCH (neighbour cell) + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 22 | F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH+ one or more E-HICH + one E-AGCH + zero, one or more E-RGCH | HS-DSCH | Depending on UE radio access capabilities | The maximum channel bit rate is dependent on UE radio access capabilities. In this combination E-DCH is configured in uplink. NOTE | +| 23 | PCCPCH (neighbour cell) + F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH+ one or more E-HICH + one E-AGCH + zero, one or more E-RGCH | BCH (neighbour cell) + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH is configured in uplink. NOTE | +| 24 | MICH | N/A | Depending on UE radio access capabilities | | +| 25 | MICH + PICH | N/A | Depending on UE radio access capabilities | | +| 26 | MICH + one SCCPCH | More than one (one or more FACH or PCH or (one or more FACH + PCH)) | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of non-MBMS FACH or PCH. | +| 27 | PICH + one or more SCCPCH | One or more FACH | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 28 | PCCPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + SCCPCH | BCH + HS-DSCH + one or more FACH | Depending on UE radio access capabilities | Simultaneous reception of PCCPCH, SCCPCH and HS-SCCH is only needed at occurrences when the UE needs to read system information on BCH while being in CELL_PCH state, i.e. continuous reception of PCCPCH, and SCCPCH and HS-SCCH at the same time is not required. SCCPCH and HS-SCCH are to be detected at the same time. One HS-DSCH is used in CELL_PCH state to enable the reception of BCCH, DCCH, DTCH, or PCCH logical channel data. In CELL_PCH state the reception of one or more FACH is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. The requirement holds for PCCPCH, SCCPCH and HS-SCCH sent in different cells or in the same cell. NOTE | +| 29 | Zero, one or more HS-SCCHs + zero, one or more HS-PDSCH | HS-DSCH | Depending on UE radio access capabilities | One HS-DSCH is used in CELL_FACH state to enable the reception of BCCH, CCCH, DCCH, or DTCH logical channel data. One HS-DSCH is used in CELL_PCH state to enable reception of BCCH, DCCH, DTCH or PCCH logical channel. One HS-DSCH is used in URA_PCH state to enable reception of PCCH logical channel. This combination is required by a UE in CELL_DCH state to be able to receive the HS-DSCH on the secondary DL frequency. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 30 | One or more HS-SCCHs + zero, one or more HS-PDSCH + more than one SCCPCH | HS-DSCH + one or more FACH | Depending on UE radio access capabilities | One HS-DSCH is used in CELL_FACH state to enable the reception of BCCH, CCCH, DCCH, or DTCH logical channel data.
One HS-DSCH is used in CELL_PCH state to enable reception of BCCH, DCCH, DTCH or PCCH logical channel.
In CELL_PCH state the reception of (one or more FACH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH.
One or more FACHs are used to enable the reception of MBMS (i.e., MCCH, MSCH and MTCH) in CELL_FACH or CELL_PCH state. The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. The combination includes the case where one or more MBMS FACHs are transmitted on the same SCCPCH as used for non-MBMS FACH. NOTE | +| 31 | MICH + one or more HS-SCCH + zero, one or more HS-PDSCH + SCCPCH | HS-DSCH | Depending on UE radio access capabilities | Allowing reception of MBMS notification indication during reception of HS-DSCH in CELL_FACH state. | +| 32 | DPCCH + one or more DPDCH +F-TPICH | More than one DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination CLTD is configured in uplink. | +| 33 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH+F-TPICH | BCH (neighbour cell) + one or more DCHs | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while CLTD is configured in uplink. | +| 34 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH+F-TPICH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination CLTD is configured in uplink. NOTE | +| 35 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH +F-TPICH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination CLTD is configured in uplink. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 36 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + F-TPICH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH and CLTD is configured in uplink. NOTE | +| 37 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH + F-TPICH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and CLTD is configured in uplink. NOTE | +| 38 | F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + F-TPICH | HS-DSCH | Depending on UE radio access capabilities | The maximum channel bit rate is dependent on UE radio access capabilities. In this combination CLTD is configured in uplink. NOTE | +| 39 | PCCPCH (neighbour cell) + F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + F-TPICH | BCH (neighbour cell) + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination CLTD is configured in uplink. NOTE | +| 40 | F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + F-TPICH | HS-DSCH | Depending on UE radio access capabilities | The maximum channel bit rate is dependent on UE radio access capabilities. In this combination E-DCH and CLTD is configured in uplink. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 41 | PCCPCH (neighbour cell) + F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH+ one or more E-HICH + one E-AGCH + zero, one or more E-RGCH+F-TPICH | BCH (neighbour cell) + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and CLTD is configured in uplink. NOTE | +| 42 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH+ one or more E-HICH + one E-AGCH + zero, one or more E-RGCH+F-TPICH + one E-ROCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH and uplink MIMO is configured in uplink. NOTE | +| 43 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH+F-TPICH + one E-ROCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and UL MIMO is configured in uplink. NOTE | +| 44 | F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH+ one or more E-HICH + one E-AGCH + zero, one or more E-RGCH+F-TPICH + one E-ROCH | HS-DSCH | Depending on UE radio access capabilities | The maximum channel bit rate is dependent on UE radio access capabilities. In this combination E-DCH and UL MIMO is configured in uplink. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 45 | PCCPCH (neighbour cell) + F-DPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + F-TPICH + one E-ROCH | BCH (neighbour cell) + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and UL MIMO is configured in uplink. NOTE | +| 46 | DPCCH + one or more DPDCH + zero, one or more HS-SCCHs + zero, one or more HS-PDSCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. This combination is required by a UE in CELL_DCH state to be able to receive the HS-DSCH on the assisting serving HS-DSCH cell. NOTE | +| 47 | DPCCH + one or more DPDCH + zero, one or more HS-SCCHs + zero, one or more HS-PDSCH + one or more E-HICH + zero, one or more E-RGCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH is configured in uplink. This combination is required by a UE in CELL_DCH state to be able to receive the HS-DSCH on the assisting serving HS-DSCH cell. NOTE | +| 48 | F-DPCH + zero, one or more HS-SCCHs + zero, one or more HS-PDSCH | HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to receive the HS-DSCH on the assisting serving HS-DSCH cell. NOTE | +| 49 | F-DPCH + zero, one or more HS-SCCHs + zero, one or more HS-PDSCH + one or more E-HICH + zero, one or more E-RGCH | HS-DSCH | Depending on UE radio access capabilities | In this combination E-DCH is configured in uplink. This combination is required by a UE in CELL_DCH state to be able to receive the HS-DSCH on the assisting serving and assisting secondary HS-DSCH cell. NOTE | +| 50 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one F-DPCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination DPCCH2 is configured. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 51 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one F-DPCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination DPCCH2 is configured. NOTE | +| 52 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + one F-DPCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH is configured in uplink and DPCCH2 is configured. NOTE | +| 53 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH + one F-DPCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH is configured in uplink and DPCCH2 is configured. NOTE | +| 54 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + F-TPICH + one F-DPCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination CLTD is configured in uplink and DPCCH2 is configured. NOTE | +| 55 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + F-TPICH + one F-DPCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination CLTD is configured in uplink and DPCCH2 is configured. NOTE | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 56 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + F-TPICH + one F-DPCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH and CLTD is configured in uplink and DPCCH2 is configured. NOTE | +| 57 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH + F-TPICH + one F-DPCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and CLTD is configured in uplink and DPCCH2 is configured. NOTE | +| 58 | DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + one E-AGCH + zero, one or more E-RGCH + F-TPICH + one E-ROCH + one F-DPCH | One or more DCH coded into a single CCTrCH + HS-DSCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH and uplink MIMO is configured in uplink and DPCCH2 is configured. NOTE | +| 59 | PCCPCH (neighbour cell) + DPCCH + one or more DPDCH + one or more HS-SCCH + zero, one or more HS-PDSCH + one or more E-HICH + E-AGCH + zero, one or more E-RGCH + F-TPICH + one E-ROCH + one F-DPCH | BCH (neighbour cell) + one or more DCHs + HS-DSCH | Depending on UE radio access capabilities | This combination is required by a UE in CELL_DCH state to be able to read the SFN of a neighbouring cell and support "SFN-CFN observed time difference" and "SFN-SFN observed time difference" measurements while HS-DSCH is configured. In this combination E-DCH and UL MIMO is configured in uplink and DPCCH2 is configured. NOTE | +| 60 | PCCPCH + SCCPCH | BCH (on PCCPCH and SCCPCH) | Depending on UE radio access capabilities | System information broadcast channel (BCH on PCCPCH). Second system information broadcast channel (BCH on SCCPCH) | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory dependent on UE radio access capabilities | Comment | +|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 61 | PCCPCH + two or more SCCPCH | BCH (on PCCPCH and SCCPCH) + (one or more FACH or PCH or (one or more FACH + PCH)) | Depending on UE radio access capabilities |

The PCH is included when the UE needs to receive paging on the SCCPCH.

The reception of (one or more FACH + PCH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH.

System information broadcast channel (BCH on PCCPCH). Second system information broadcast channel (BCH on SCCPCH). Simultaneous reception of BCH on SCCPCH and FACH/CTCH occasions is not required.

| +| 62 | PCCPCH + two or more SCCPCH + one or more HS-SCCH + zero, one or more HS-PDSCH | BCH (on PCCPCH and SCCPCH) + HS-DSCH + or one or more FACH | Depending on UE radio access capabilities |

SCCPCH and HS-SCCH are to be detected at the same time.

One HS-DSCH is used in CELL_PCH state to enable the reception of BCCH, DCCH, DTCH, or PCCH logical channel data.

In CELL_PCH state the reception of one or more FACH is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH.

The requirement holds for PCCPCH, SCCPCH and HS-SCCH sent in different cells or in the same cell. NOTE

System information broadcast channel (BCH on PCCPCH). Second system information broadcast channel (BCH on SCCPCH). Simultaneous reception of BCH on SCCPCH and FACH/CTCH occasions is not required.

| +| NOTE: When one or more HS-PDSCHs are received, it is sufficient for the UE to monitor only one HS-SCCH. | | | | | + +The table 2-2 describes the possible combinations of FDD physical channels that can be supported in the downlink on two, three, four, five, six, seven or eight configured downlink frequencies by one UE simultaneously depending on UE radio access capabilities. + +Table 2-2: FDD Downlink + +| Physical Channel Combination n | Downlink frequency | | | | | | | | Comment | | +|--------------------------------|--------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|--------------------------------------|--| +| | Primary | Secondary | | | | | | | | | +| | | 1 st | 2 nd | 3 rd | 4 th | 5 th | 6 th | 7 th | | | +| A1 | 15 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | | | +| A2 | 16 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | | | +| A3 | 18 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| A4 | 19 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| A5 | 15 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | | | +| A6 | 15 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | | | +| A7 | 16 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | | | +| A8 | 16 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | | | +| A9 | 18 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| A10 | 18 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 1 | | +| A11 | 19 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| A12 | 19 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 1 | | +| A13 to A16 | 15 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 3 | | +| A17 to A20 | 16 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 3 | | +| A21 to A24 | 18 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE3 | | +| A25 to A28 | 19 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 3 | | +| A29 to A35 | 34 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 5 | | +| A36 to A42 | 35 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 5 | | +| A43 to A49 | 36 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 4
NOTE 5 | | +| A50 to A56 | 37 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 4
NOTE 5 | | +| A57 to A63 | 50 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 6 | | +| A64 to A70 | 51 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 6 | | +| A71 to A77 | 52 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 4
NOTE 6 | | +| A78 to A84 | 53 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 4
NOTE 6 | | +| A85 to A91 | 54 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 5
NOTE 6 | | +| A92 to A98 | 55 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4
NOTE 5
NOTE 6 | | +| A99 to A105 | 56 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 4
NOTE 5
NOTE 6 | | +| A106 to A112 | 57 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 4
NOTE 5
NOTE 6 | | +| B1 | 20 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | | | +| B2 | 21 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | | | +| B3 | 22 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| B4 | 23 | 29 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| B5 | 20 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | | | +| B6 | 20 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | | | +| B7 | 21 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | | | +| B8 | 21 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | | | +| B9 | 22 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | + +| Physical Channel Combination | Downlink frequency | | | | | | | | Comment | | +|------------------------------|--------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|------------------------|--| +| | Primary | Secondary | | | | | | | | | +| | | 1 st | 2 nd | 3 rd | 4 th | 5 th | 6 th | 7 th | | | +| B10 | 22 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 1 | | +| B11 | 23 | 29 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 1 | | +| B12 | 23 | 29 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 1 | | +| B13 to B16 | 20 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 3 | | +| B17 to B20 | 21 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 3 | | +| B21 to B24 | 22 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 3 | | +| B25 to B28 | 23 | 29 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 3 | | +| B29 to B35 | 38 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4, NOTE 5 | | +| B36 to B42 | 39 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4, NOTE 5 | | +| B43 to B49 | 40 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 4, NOTE 5 | | +| B50 to B56 | 41 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 4, NOTE 5 | | +| C1 | 22 | 22 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 2 | | +| C2 | 23 | 22 | n/a | n/a | n/a | n/a | n/a | n/a | NOTE 2 | | +| C3 | 22 | 22 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 2 | | +| C4 | 22 | 22 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 2 | | +| C5 | 23 | 22 | 29 | n/a | n/a | n/a | n/a | n/a | NOTE 2 | | +| C6 | 23 | 22 | 29 | 29 | n/a | n/a | n/a | n/a | NOTE 2 | | +| C7 to C10 | 22 | 22 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2, NOTE 3 | | +| C11 to C14 | 23 | 22 | 29 | 29 | 29 | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2, NOTE 3 | | + +NOTE 1: In this combination E-DCH is configured on the uplink frequency corresponding to the primary downlink frequency. + +NOTE 2: In this combination E-DCH is configured on the uplink frequencies corresponding to the primary downlink frequency and 1st secondary downlink frequency. + +NOTE 3: In these combinations, the 1st combination referred to has the 4th Secondary downlink frequency combination 29, the 2nd combination has the 4th and 5th Secondary downlink frequency combinations of 29, the 3rd combination has the 4th, 5th and 6th Secondary downlink frequency combination of 29, the 4th combination has the 4th, 5th, 6th and 7th Secondary downlink frequency combination 29. + +NOTE 4: In these combinations, the 1st combination referred to has the 1st Secondary downlink frequency combination 29, the 2nd combination has the 1st and 2nd Secondary downlink frequency combination 29, the 3rd combination has the 1st, 2nd and 3rd Secondary downlink frequency combination 29, etc. + +NOTE 5: In this combination CLTD is configured on the uplink frequency corresponding to the primary downlink frequency. + +NOTE 6: In this combination DPCCH2 is configured on the uplink frequency corresponding to the primary downlink frequency. + +The table 2-3 describes the possible combinations of FDD physical channels that can be supported on at least two configured downlink and two uplink frequencies by one UE simultaneously. + +**Table 2-3: FDD Downlink and Uplink** + +| Physical Channel Combination | Downlink frequency | | | Uplink frequency | | +|------------------------------|--------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------|------------------|-----------| +| | Primary | Secondary (1 st ) | Secondary (2 nd , 3 rd , 4 th , 5 th , 6 th , and 7 th ) | Primary | Secondary | +| D1 | 22 | 22 | 29 | 8 | 9 | +| D2 | 23 | 22 | 29 | 8 | 9 | +| D3 | 22 | 29 | 29 | 8 | N/A | +| D4 | 23 | 29 | 29 | 8 | N/A | +| D5 | 18 | 22 | 29 | 7 | 9 | +| D6 | 19 | 22 | 29 | 7 | 9 | +| D7 | 18 | 29 | 29 | 7 | N/A | +| D8 | 19 | 29 | 29 | 7 | N/A | + +The Table 2-4 describes the possible combinations of FDD physical channels that can be supported for Multiflow in the downlink on one, two or three configured downlink frequencies by one UE depending on UE radio capabilities. + +**Table 2-4: FDD Downlink (Multiflow)** + +| Physical Channel Combination | Downlink frequency | | | | | | Comment | | +|------------------------------|--------------------|------------------------|------------------------------|----------------------------------|------------------------------|----------------------------------|------------------------|--| +| | Primary | | Secondary (1 st ) | | Secondary (2 nd ) | | | | +| | serving cell | assisting serving cell | secondary serving cell | assisting secondary serving cell | secondary serving cell | assisting secondary serving cell | | | +| E1 to E4 | 15 | 46 | 29 or n/a | 29 or n/a | | | | | +| E5 to E8 | 16 | 46 | 29 or n/a | 29 or n/a | | | | | +| E9 to E12 | 18 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1 | | +| E13 to E16 | 19 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1 | | +| E17 to E20 | 34 | 46 | 29 or n/a | 29 or n/a | | | NOTE 2 | | +| E21 to E24 | 35 | 46 | 29 or n/a | 29 or n/a | | | NOTE 2 | | +| E25 to E28 | 36 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 2 | | +| E29 to E32 | 37 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 2 | | +| E33 to E36 | 42 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 3 | | +| E37 to E40 | 43 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 3 | | +| E41 to E44 | 50 | 46 | 29 or n/a | 29 or n/a | | | NOTE 4 | | +| E45 to E48 | 51 | 46 | 29 or n/a | 29 or n/a | | | NOTE 4 | | +| E49 to E52 | 52 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 4 | | +| E53 to E56 | 53 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 4 | | +| E57 to E60 | 54 | 46 | 29 or n/a | 29 or n/a | | | NOTE 2, NOTE 4 | | +| E61 to E64 | 55 | 46 | 29 or n/a | 29 or n/a | | | NOTE 2, NOTE 4 | | +| E65 to E68 | 56 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 2, NOTE 4 | | +| E69 to E72 | 57 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 2, NOTE 4 | | +| E73 to E76 | 58 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 3, NOTE 4 | | +| E77 to E80 | 59 | 47 | 29 or n/a | 29 or n/a | | | NOTE 1, NOTE 3, NOTE 4 | | +| E81 to E82 | 15 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | | | +| E83 to E84 | 16 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | | | +| E85 to E86 | 18 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1 | | +| E87 to E88 | 19 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1 | | +| E89 to E90 | 34 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2 | | +| E91 to E92 | 35 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2 | | +| E93 to E94 | 36 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 2 | | +| E95 to E96 | 37 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 2 | | +| E97 to E98 | 42 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 3 | | +| E99 to E100 | 43 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 3 | | +| E101 to E102 | 50 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4 | | +| E103 to E104 | 51 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 4 | | +| E105 to E106 | 52 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 4 | | +| E107 to E108 | 53 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1, NOTE 4 | | +| E109 to E110 | 54 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2, NOTE 4 | | +| E111 to E112 | 55 | 46 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2, NOTE 4 | | + +| Physical Channel Combination | Downlink frequency | | | | | | Comment | +|------------------------------|--------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------|----------------------------------|----------------------------| +| | Primary | | Secondary (1 st ) | | Secondary (2 nd ) | | | +| | serving cell | assisting serving cell | secondary serving cell | assisting secondary serving cell | secondary serving cell | assisting secondary serving cell | | +| E113 to E114 | 56 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 2
NOTE 4 | +| E115 to E116 | 57 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 2
NOTE 4 | +| E117 to E118 | 58 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 3
NOTE 4 | +| E119 to E120 | 59 | 47 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1
NOTE 3
NOTE 4 | +| F1 to F4 | 20 | 48 | 29 or n/a | 29 or n/a | | | | +| F5 to F8 | 21 | 48 | 29 or n/a | 29 or n/a | | | | +| F9 to F12 | 22 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1 | +| F13 to F16 | 23 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1 | +| F17 to F20 | 38 | 48 | 29 or n/a | 29 or n/a | | | NOTE 2 | +| F21 to F24 | 39 | 48 | 29 or n/a | 29 or n/a | | | NOTE 2 | +| F25 to F28 | 40 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1,
NOTE 2 | +| F29 to F32 | 41 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1,
NOTE 2 | +| F33 to F36 | 44 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1,
NOTE 3 | +| F37 to F40 | 45 | 49 | 29 or n/a | 29 or n/a | | | NOTE 1,
NOTE 3 | +| F41 to F42 | 20 | 48 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | | +| F43 to F44 | 21 | 48 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | | +| F45 to F46 | 22 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1 | +| F47 to F48 | 23 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1 | +| F49 to F50 | 38 | 48 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2 | +| F51 to F52 | 39 | 48 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 2 | +| F53 to F54 | 40 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1,
NOTE 2 | +| F55 to F56 | 41 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1,
NOTE 2 | +| F57 to F58 | 44 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1,
NOTE 3 | +| F59 to F60 | 45 | 49 | 29 or n/a | 29 or n/a | 29 or n/a | 29 or n/a | NOTE 1,
NOTE 3 | +| G1 to G2 | 22 | 49 | 22 | 49 or n/a | | | NOTE 1a | +| G3 to G4 | 23 | 49 | 22 | 49 or n/a | | | NOTE 1a | +| G5 | 22 | 49 | 22 | n/a | 29 | n/a | NOTE 1a | +| G6 | 23 | 49 | 22 | n/a | 29 | n/a | NOTE 1a | +| | | |

NOTE 1: In this combination E-DCH is configured on the uplink frequency corresponding to the primary downlink frequency.

NOTE 1a: In this combination E-DCH is configured on the uplink frequency corresponding to the primary downlink frequency and 1st secondary downlink frequency.

NOTE 2: In this combination CLTD is configured on the uplink frequency corresponding to the primary downlink frequency.

NOTE 3: In this combination UL MIMO is configured on the uplink frequency corresponding to the primary downlink frequency.

NOTE 4: In this combination DPCCH2 is configured on the uplink frequency corresponding to the primary downlink frequency.

| | | | | + +The table 2-5 describes the possible combinations of FDD physical channels that can be supported for Multiflow on two configured downlink and uplink frequencies by one UE simultaneously. + +**Table 2-5: FDD Downlink and Uplink (Multiflow)** + +| Physical Channel Combination | Downlink frequency | | | | | | Uplink frequency | | +|------------------------------|--------------------|------------------------|------------------------------|----------------------------------|------------------------------|----------------------------------|------------------|-----------| +| | Primary | | Secondary (1 st ) | | Secondary (2 nd ) | | Primary | Secondary | +| | Serving cell | Assisting serving cell | Secondary Serving cell | Assisting secondary serving cell | Secondary Serving cell | Assisting secondary serving cell | | | +| H1 to H2 | 22 | 49 | 22 | 49 or n/a | | | 8 | 9 | +| H3 to H4 | 23 | 49 | 22 | 49 or n/a | | | 8 | 9 | +| H5 to H6 | 22 | 49 | 29 | 29 or n/a | | | 8 | N/A | +| H7 to H8 | 23 | 49 | 29 | 29 or n/a | | | 8 | N/A | +| H9 | 22 | 49 | 22 | n/a | 29 | n/a | 8 | 9 | +| H10 | 23 | 49 | 22 | n/a | 29 | n/a | 8 | 9 | +| H11 | 22 | 49 | 22 | n/a | 29 | n/a | 8 | N/A | +| H12 | 23 | 49 | 22 | n/a | 29 | n/a | 8 | N/A | + +## 8.3 TDD Uplink + +### 8.3.1 3.84/7.68 Mcps TDD Uplink + +The table addresses the possible combinations of 3.84/7.68 Mcps TDD physical channels that can be supported in the uplink by one UE simultaneously on the same frequency in any one 10ms frame. In 3.84/7.68 Mcps TDD a physical channel corresponds to one code, one timeslot and one frequency. + +**Table 3: 3.84/7.68 Mcps TDD Uplink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | PRACH | RACH | Mandatory | | +| 2 | DPCH | One or more DCH coded into a single CCTrCH | Mandatory | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.
This combination is used as reference measurement channel. | +| 3 | One or more than one DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 4 | PRACH + one or more DPCH | RACH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.
This combination may be used for shared channel operation only.
At least the usage of two timeslots is required. | +| 5 | One or more PUSCH | One or more USCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination is used for shared channel operation. | +| 6 | PRACH + one or more PUSCH | RACH + One or more USCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination may be used for shared channel operation only. At least the usage of two timeslots is required. | +| 7 | One or more PUSCH + one or more DPCH | One or more USCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.

This combination may be used for shared channel operation. | +| 8 | PRACH + one or more PUSCH + one or more DPCH | RACH + one or more USCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.

This combination may be used for shared channel operation.
At least the usage of two timeslots is required. | +| 9 | One or more DPCH + HS-SICH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | | +| 10 | Zero, one or more DPCH + zero or one HS-SICH + E-RUCCH | One or more DCH | Depending on UE radio access capabilities | 3.84 and 7.68 Mcps only.
The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities | +| 11 | Zero, one or more DPCH + zero or one HS-SICH + one E-PUCH | One or more DCH + E-DCH | Depending on UE radio access capabilities | 3.84 and 7.68 Mcps only.
The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities | + +### 8.3.2 1.28 Mcps TDD Uplink + +The table 4-1 addresses the possible combinations of 1.28 Mcps TDD physical channels that can be supported in the uplink by one UE simultaneously on the same frequency in the TDD 1.28 Mcps option in any one 5 ms subframe. In 1.28 Mcps TDD a physical channel corresponds to one code, one timeslot, one frequency. + +**Table 4-1: 1.28 Mcps TDD Uplink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|----------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | UpPCH | N/A | Mandatory | UpPCH is used to establish the uplink synchronisation. | +| 2 | PRACH | RACH | Mandatory | | +| 3 | UpPCH + One DPCH | One or more DCH coded into a single CCTrCH | Mandatory | One DPCH is needed as reference measurement channel.
UpPCH transmission to target cell in case of handover. | +| 4 | One DPCH | One or more DCH coded into a single CCTrCH | Mandatory | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities
This combination is required for the reference measurement channel. | +| 5 | More than one DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 6 | UpPCH+ one or more DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities.
This configuration is required for UE that operate shared channels and dedicated channels simultaneously. | +| 7 | PRACH + one or more DPCHs | RACH + one or more DCH coded into one or more than one CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities.
This configuration is required for UE that operate shared channels and dedicated channels simultaneously. | +| 8 | One or more PUSCH | One or more USCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This configuration is required for UE that operate shared channels. | +| 9 | UpPCH + one or more PUSCH | One or more USCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination may be used for shared channel operation only. | +| 10 | PRACH + one or more PUSCH | RACH + One or more USCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination may be used for shared channel operation only | +| 11 | One or more PUSCH + one or more DPCH | One or more USCH coded onto one or more CCTrCH + one or more DCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.
This configuration is required for UE that operate shared channels and dedicated channels simultaneously | +| 12 | UpPCH + one or more PUSCH + one or more DPCH | One or more USCH coded onto one or more CCTrCH + one or more DCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.
This combination may be used for shared channel operation. | +| 13 | PRACH + one or more PUSCH + one or more DPCH | RACH + one or more USCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.
This combination may be used for shared channel operation. | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------------------------------------|-----------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| 14 | One or more DPCH + HS-SICH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | | +| 15 | One or more DPCH + Zero or one HS-SICH + one or more E-RUCCH + E-PUCH | One or more DCH + one E-DCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities | +| 16 | One HS-SICH + one or more E-RUCCH + E-PUCH | One E-DCH | Depending on UE radio access capabilities | The maximum channel bit rate are dependent on UE radio access capabilities | + +The table 4-2 describes the possible combinations of 1.28Mcps TDD physical channels that can be supported in the uplink on two or more configured uplink frequencies by one UE simultaneously. + +**Table 4-2: 1.28 Mcps TDD Uplink** + +| Physical Channel Combination | Physical Channel Combination on Primary E-DCH carrier | Physical Channel Combination on Additional E-DCH carrier | Mandatory or dependent on UE radio access capabilities | Comment | +|-------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | zero or one DPCH + zero or one or more HS-SICH + one or more E-RUCCH + E-PUCH | zero or one or more HS-SICH + E-PUCH | Depending on UE radio access capabilities | The maximum number of E-DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination HS-DSCH(s) are configured on each corresponding downlink frequency. | + +## 8.4 TDD Downlink + +### 8.4.1 3.84/7.68 Mcps TDD Downlink + +The table describes the possible combinations of 3.84/7.68 Mcps TDD physical channels that can be supported in the downlink by one UE simultaneously on the same frequency in any one 10ms frame, where a 3.84/7.68 Mcps TDD physical channel corresponds to one code, one timeslot and one frequency. + +Depending on UE radio capabilities UEs may be required to decode occasionally P-CCPCH of its own cell in the following Physical Channel Combinations to maintain open loop power control and/or acquire parameters for RACH access: 4, 6, 7, 8, 9, 10, 11, 12, 13. + +Depending on UE radio capabilities UEs may be required to decode occasionally one P-CCPCH of neighbour cells in the following Physical Channel Combinations for handover: 6, 8, 11, 12, 13. + +**Table 5: 3.84/7.68 Mcps TDD Downlink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | P-CCPCH + One S-CCPCH | BCH and PCH and/or one or more FACH | Mandatory | | +| 2 | P-CCPCH | BCH | Mandatory | | +| 3 | S-CCPCH | FACH or/and PCH | Mandatory | | +| 4 | More than one S-CCPCH | one or more FACH+ one or more PCH | Depending on UE capabilities | One or more FACHs are used to enable the reception of MBMS (i.e., MCCH, MSCH and MTCH). The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. The combination includes the case where one or more MBMS FACHs are transmitted on the same SCCPCH as used for non-MBMS FACH or PCH. | +| 5 | PICH | N/A | Mandatory | | +| 6 | Three or more DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 7 | One or two DPCH | One or more DCH coded into a single CCTrCH | Mandatory | This combination is used for reference measurement channel. | +| 8 | One or more S-CCPCH + one or more DPCH | PCH and/or one or more FACH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The number of DCHs and the maximum channel bit rate are dependent on the UE radio access capabilities. This combination is used for shared channel operation only. | +| 9 | One or more PDSCH | One or more DSCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination is used for shared channel operation. | +| 10 | One or more PDSCH + one or more S-CCPCH | PCH and/or one or more FACH + one or more DSCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This combination is used for shared channel operation. | +| 11 | One or more PDSCH + one or more DPCH | One or more DSCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities.

This combination is used for shared channel operation. | +| 12 | One or more PDSCH + one or more S-CCPCH + one or more DPCH | PCH and/or one or more FACH + one or more DSCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs and the maximum channel bit rate are dependent on UE radio access capabilities. This combination is used for shared channel operation. | +| 13 | Zero, one or more DPCH + zero, one or more HS-PDSCH + one or more HS-SCCH | Zero, one or more DCH coded into one or more CCTrCH + one or more HS-DSCH coded into one CCTrCH | Depending on UE radio access capabilities | | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| 14 | MICH | N/A | Depending on UE radio access capabilities | | +| 15 | MICH + PICH | N/A | Depending on UE radio access capabilities | | +| 16 | MICH + one or more SCCPCH | One or more FACH + one or more PCH + (NOTE 2) | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of non-MBMS FACH or PCH. | +| 17 | PICH + one or more SCCPCH | One or more FACH + (NOTE 2) | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 18 | MICH + PICH + one or more SCCPCH | One or more FACH + (NOTE 2) | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 19 | Zero, one or more DPCH + zero, one or more HS-PDSCH + one or more HS-SCCH + zero, one or more E-AGCH + zero or one E-HICH | Zero, one or more DCHs coded into zero, one or more CCTrCH + one HS-DSCH | Depending on UE radio access capabilities | 3.84 and 7.68 Mcps only. | + +NOTE 1: Reference: [12]. + +NOTE 2: + (zero, one or more DCH coded onto one or more CCTrCH) + (zero, one or more DSCH coded onto one or more CCTrCH) + (zero, one or more HS-DSCH coded onto one or more CCTrCH). + +### 8.4.2 1.28 Mcps TDD Downlink + +The table 6-1 addresses the possible combinations of 1.28 Mcps TDD physical channels that can be supported in the downlink by one UE simultaneously on the same frequency in any one 5ms subframe. In 1.28 Mcps TDD a physical channel corresponds to one code, one timeslot, one frequency. + +Depending on UE radio capabilities UEs may be required to decode occasionally P-CCPCH of its own cell in the following Physical Channel Combinations: 5, 11, 12, 13, 14, 15, 16, 17, 18. + +To support handover it depends on UE capabilities if a UE can support the occasional decoding of neighbour cell P-CCPCH in the physical channel combinations 8, 9, 10, 11, 15, 16, 17, 18. + +**Table 6-1: 1.28 Mcps TDD Downlink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|---------------------------------------------|-------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | FPACH | N/A | Mandatory | FPACH is used to answer the UE and to adjust the timing and synchronization shift of the UE | +| 2 | P-CCPCH | BCH | Mandatory | | +| 3 | S-CCPCH | FACH or/and PCH | Mandatory | | +| 4 | P-CCPCH + S-CCPCH | BCH + (FACH or/and PCH) | Mandatory | | +| 5 | More than one S-CCPCH | one or more FACH+ one or more PCH | Depending on UE capabilities | One or more FACHs are used to enable the reception of MBMS (i.e., MCCH, MSCH and MTCH). The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. The combination includes the case where one or more MBMS FACHs are transmitted on the same SCCPCH as used for non-MBMS FACH or PCH. | +| 6 | PICH | N/A | Mandatory | | +| 7 | FPACH + P-CCPCH + none, one or more S-CCPCH | BCH + (none, one or more FACH+ none, one or more PCH) | Depending on UE capabilities | | +| 8 | 2 DPCH | One or more DCH coded into a single CCTrCH | Mandatory | The maximum number of DCH and the maximum channel bit rate are dependent on UE radio access capabilities
This channel is used as reference measurement channel | +| 9 | One or more DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities. | +| 10 | FPACH + one or more DPCH | One or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | FPACH is used to answer the UE and to adjust the timing and synchronization shift of the UE.

The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities.

This configuration is required for UE that operate shared channels and dedicated channels simultaneously. | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|-----------------------------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | One or more S-CCPCH + one or more DPCH | (One or more FACH or/and PCH) + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | The maximum number of DCHs, the maximum number of CCTrCH and the maximum channel bit rate are dependent on UE radio access capabilities.
This configuration is required for UE that operate shared channels and dedicated channels simultaneously. | +| 12 | One or more PDSCH | One or more DSCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This configuration is required for UE that operate shared channels. | +| 13 | FPACH + one or more PDSCH | One or more DSCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This configuration is desirable but not essential for UE supporting shared channels. | +| 14 | One or more S-CCPCH + one or more PDSCH | (One or more FACH and/or PCH) + One or more DSCH coded onto one or more CCTrCH | Depending on UE radio access capabilities | This configuration is desirable but not essential for UE supporting shared channels. | +| 15 | One or more PDSCH + one or more DPCH | One or more DSCH coded onto one or more CCTrCH + one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities | This configuration is required for UE that operate shared channels and dedicated channels simultaneously. | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 16 | FPACH
+ one or more PDSCH
+ one or more DPCH | one or more DSCH coded onto one or more CCTrCH
+ one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities. | FPACH is used to answer the UE and to adjust the timing and synchronization shift of the UE.

This configuration is desirable but not essential for UE supporting shared channels and dedicated channels simultaneously. | +| 17 | One or more S-CCPCH
+ one or more PDSCH
+ one or more DPCH | (One or more FACH and/or PCH)
+ one or more DSCH coded onto one or more CCTrCH
+ one or more DCH coded into one or more CCTrCH | Depending on UE radio access capabilities. | This configuration is desirable but not essential for UE supporting shared channels and dedicated channels simultaneously. | +| 18 | One or more DPCH + zero, one or more HS-PDSCH + one or more HS-SCCH | One or more DCH coded into one or more CCTrCH
+ one or more HS-DSCH coded into one CCTrCH | Depending on UE radio access capabilities | | +| 19 | MICH | N/A | Depending on UE radio access capabilities | | +| 20 | MICH + PICH | N/A | Depending on UE radio access capabilities | | +| 21 | MICH + one or more SCCPCH | One or more FACH + one or more PCH + (NOTE 1) | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of non-MBMS FACH or PCH. | +| 22 | PICH + one or more SCCPCH | One or more FACH + (NOTE 1) | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 23 | MICH + PICH + one or more SCCPCH | One or more FACH + (NOTE 1) | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 24 | FPACH +Zero, one or more DPCH + zero, one or more HS-PDSCH + one or more HS-SCCH + zero, one or more E-AGCH + zero or one E-HICH | Zero, one or more DCHs coded into zero, one or more CCTrCH + one HS-DSCH | Depending on UE radio access capabilities | The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|----|--------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 25 | P-CCPCH + one or more HS-SCCH + zero, one or more HS-PDSCH + S-CCPCH | BCH + one HS-DSCH + one or more FACH | Depending on UE radio access capabilities | Simultaneous reception of P-CCPCH, S-CCPCH and HS-SCCH is only needed at occurrences when the UE needs to read system information on BCH while being in CELL_FACH state, i.e. continuous reception of P-CCPCH, and S-CCPCH and HS-SCCH at the same time is not required. S-CCPCH and HS-SCCH are to be detected at the same time. One HS-DSCH is used in CELL_FACH state to enable the reception of CCCH, BCCH, DCCH and DTCH logical channel data. The reception of one or more FACH is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. The requirement holds for P-CCPCH, S-CCPCH and HS-SCCH sent in different cells or in the same cell. | +| 26 | One or more HS-SCCHs + zero, one or more HS-PDSCH | One HS-DSCH | Depending on UE radio access capabilities | One HS-DSCH is used in CELL_FACH state to enable the reception of CCCH, BCCH, DCCH and DTCH logical channel data. | +| 27 | One or more HS-SCCHs + zero, one or more HS-PDSCH + more than one SCCPCH | One HS-DSCH + one or more FACH | Depending on UE radio access capabilities | One HS-DSCH is used in CELL_FACH state to enable the reception of CCCH, DCCH and DTCH logical channel data. In CELL_FACH state the reception of (one or more FACH) is to enable the reception of broadcast services on the CTCH, mapped to one of the FACH. One or more FACHs are used to enable the reception of MBMS (i.e., MCCH, MSCH and MTCH). The maximum number of S-CCPCHs and the maximum bit rate depend on the UE implementation. The combination includes the case where one or more MBMS FACHs are transmitted on the same S-CCPCH as used for non-MBMS FACH. | +| 28 | MICH + one or more HS-SCCH + zero, one or more HS-PDSCH + S-CCPCH | One HS-DSCH | Depending on UE radio access capabilities | Allowing reception of MBMS notification indication during reception of HS-DSCH in CELL_FACH state. | + +NOTE 1: + (zero, one or more DCH coded onto one or more CCTrCh) + (zero, one or more DSCH coded onto one or more CCTrCh) + (zero, one or more HS-DSCH coded onto one or more CCTrCh). + +The table 6-2 describes the possible combinations of 1.28Mcps TDD physical channels that can be supported in the downlink on two or more configured downlink frequencies by one UE simultaneously. + +**Table 6-2: 1.28 Mcps TDD Downlink for Multi-carrier HS-DSCH** + +| Physical Channel Combination | Physical Channel Combination on Primary HS-DSCH carrier | Physical Channel Combination on Additional HS-DSCH carrier | Mandatory or dependent on UE radio access capabilities | Comment | +|-------------------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Zero or one DPCH + zero, one or more HS-PDSCH + HS-SCCH + E-AGCH + E-HICH | zero, one or more HS-PDSCH + HS-SCCH + E-AGCH + E-HICH | Depending on UE radio access capabilities | The maximum number of HS-DSCHs and the maximum channel bit rate are dependent on UE radio access capabilities. In this combination E-DCH(s) are configured on each corresponding uplink frequency. | + +### 8.4.3 3.84 Mcps TDD IMB Downlink + +The table describes the possible combinations of 3.84 Mcps TDD IMB physical channels that can be supported in the downlink on the same frequency by one UE simultaneously. + +**Table 6a: 3.84 Mcps TDD IMB Downlink** + +| | Physical Channel Combination | Transport Channel Combination | Mandatory or dependent on UE radio access capabilities | Comment | +|---|-------------------------------------|--------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | PCCPCH | BCH | Mandatory | | +| 2 | SCCPCH | FACH | Mandatory | | +| 3 | SCCPCH frame type 2 | One or more FACH | Mandatory | The maximum channel bit rate that can be supported is dependent on the UE radio access capabilities. | +| 4 | SCCPCH + SCCPCH frame type 2 | More than one FACH | Mandatory | One or more FACHs are used to enable the reception of MBMS (i.e., MCCH and MTCH). The maximum number of SCCPCHs and the maximum bit rate depend on the UE implementation. | +| 5 | More than one SCCPCH frame type 2 | More than one FACH | Depending on UE radio access capabilities | | +| 6 | MICH | N/A | Depending on UE radio access capabilities | | +| 7 | MICH + SCCPCH | FACH | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of MBMS FACH. | +| 8 | MICH+ SCCPCH frame type 2 | One or more FACH | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of MBMS FACH. | +| 9 | MICH + SCCPCH+ SCCPCH frame type 2 | More than one FACH | Depending on UE radio access capabilities | Allowing MBMS notification indication during reception of MBMS FACH. | + +# 9 Measurements provided by the physical layer + +One of the key services provided by the physical layer is the measurement of various quantities, which are used to trigger or perform a multitude of functions. Both the UE and the UTRAN are required to perform a variety of measurements. The standard will not specify the method to perform these measurements or stipulate that the list of measurements provided in this clause must all be performed. While some of the measurements are critical to the functioning of the network and are mandatory for delivering the basic functionality (e.g., handover measurements, power control measurements), others may be used by the network operators in optimising the network (e.g., radio environment). + +Measurements may be made periodically and reported to the upper layers or may be event-triggered (e.g., primary CCPCH becomes better than the previous best primary CCPCH). Another reporting strategy may combine the event triggered and the periodical approach (e.g. falling of link quality below a certain threshold initiates periodical reporting). The measurements are tightly coupled with the service primitives in that the primitives' parameters may constitute some of the measurements. + +The list and frequency of measurements, which the physical layer reports to higher layers, is described in this clause. The detailed definition of measurement control and abilities is contained in [6] for FDD and [11] for TDD. The measurement performance requirements together with accuracy, range and mapping is specified in [9] for TDD and in [10] for FDD. + +The measurement quantities measured by the physical layer shall be such that the following principles are applied: + +- for handover measurements, the decoding of parameters on the BCCH logical channel of monitored neighbouring cells, should not, in general, be needed for calculating the measurement result. If there is a need to adjust the measurement result with parameters broadcast on the PCCPCH, these parameters shall be provided by the UTRAN in inband measurement control messages. There may be some exceptions to this rule; + +### EXAMPLE: + +It may be necessary to decode the SFN of the measured neighbouring cell for time difference measurements. + +- in idle mode or in RRC connected mode using common Transport Channels, the UE shall be able to monitor cells for cell reselection, without being required to frequently decode parameters on the BCCH logical channel of the monitored neighbouring cells. The decoding frequency of these parameters, set by the cell reselection algorithm, should be such that UE standby times are not significantly decreased. + +## 9.1 Model of physical layer measurements + +This subclause describes a model for how the physical layer measurements are performed. This model applies both to the UE and Node B measurements. This model sets the requirement on the behaviour of the measurement elaboration and reporting performed by L1 as well as filtering controlled by higher layers. It is not meant to be a requirement for implementation as long as the performance requirements in [9] and [10] are fulfilled. + +The measurement model for physical layer measurements is represented in the figure 7. + +![Figure 7: Measurement model diagram. The diagram shows a flow from input A through a series of processing blocks: Layer 1 filtering, Layer 3 filtering, and Evaluation of reporting criteria, resulting in output D. Two 'parameters' boxes provide input to the Layer 3 filtering and Evaluation of reporting criteria blocks. A feedback loop connects the output D back to the input A.](c64555b7f91435b01997807dbb4bcc4c_img.jpg) + +``` + +graph LR + A((A)) --> L1[Layer 1 filtering] + L1 -- B --> L3[Layer 3 filtering] + L3 -- C --> E[Evaluation of reporting criteria] + E -- D --> D_out((D)) + D -- feedback --> A + P1[parameters] --> L3 + P2[parameters] --> E + E -- C_prime --> L3 + +``` + +Figure 7: Measurement model diagram. The diagram shows a flow from input A through a series of processing blocks: Layer 1 filtering, Layer 3 filtering, and Evaluation of reporting criteria, resulting in output D. Two 'parameters' boxes provide input to the Layer 3 filtering and Evaluation of reporting criteria blocks. A feedback loop connects the output D back to the input A. + +Figure 7: Measurement model + +The model is described below: + +- **A:** measurements (samples) internal to the physical layer in support to the measurements to be provided to higher layers; +- **Layer 1 filtering:** internal layer 1 filtering of the inputs measured at point A. Exact filtering is implementation dependant. 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 i.e. the model does not state a specific sampling rate or even if the sampling is periodic or not. What the standard specifies in [9] and [10] is the performance objective and measurement period at point B in the model. The performance objectives for the physical layer measurements are specified in [9] and [10]; +- **B:** A measurement reported by layer 1 after layer 1 filtering. The reporting rate at point B shall be sufficient to meet the performance objectives as defined in [9] and [10]; + +- **Layer 3 filtering:** Filtering performed on the measurements provided at point B. The behaviour of the Layer 3 filters are standardised and the configuration of the layer 3 filters is provided by RRC signalling (UE measurements) or NBAP signalling (Node B measurements). Each filtered result at point C shall correspond to a Layer 3 filtering performed using a reporting period equal to one measurement period at point B; +- **C:** A measurement after processing in the layer 3 filter. The reporting rate is identical to the reporting rate at point B and is therefore also measurement type specific. Although this is not shown in the figure, one measurement can be used by a multiplicity of evaluation of reporting criteria; +- **Evaluation of reporting criteria:** This checks whether actual measurement reporting is necessary at point D i.e. whether a message need to be sent to higher layers on the radio interface or Iub interface. 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, C', etc. The UE shall evaluate the reporting criteria at least every time a new measurement result is reported at point C, C' etc. The reporting criteria are standardised and the configuration is provided by RRC signalling (UE measurements) or NBAP signalling (Node B measurements). Examples are periodic reporting and event based reporting. In case periodical reporting is in use and if the reporting interval is different from the filtering period defined by the layer 3 filter, the last measurement result filtered by the L3 filter shall be used as the value of the reported result. In case event triggered reporting is in use and the reporting criteria is fulfilled, the last measurement result filtered by the L3 filter shall be used as the value for reporting criteria evaluation and as the value of the reported result. This applies also for any additional measurements that shall be reported as a consequence of the event; +- **D:** a measurement report information (message) sent on the radio or Iub interface. + +## 9.2 UE Measurements + +For definitions of the measurements, see [6] and [11]. + +### 9.2.1 SFN-CFN observed time difference + +This measure is mandatory for UE. + +| | | +|-------------------|----------------------------------------------------------------------------------------| +| Measurement | SFN-CFN observed time difference | +| Source | L1 (UE) | +| Destination | RRC (RNC) for handover | +| Reporting Trigger | On-demand, Event-triggered | +| Description | Time difference between the SFN of the target neighbouring cell and the CFN in the UE. | + +### 9.2.2 Void + +### 9.2.3 CPICH $E_c/N_0$ + +This measure is mandatory for UE with FDD mode capability. + +| | | +|-------------------|-----------------------------------------------------------------------------------------------| +| Measurement | CPICH $E_c/N_0$ | +| Source | L1(UE) | +| Destination | RRC (UE, RNC) | +| Reporting Trigger | Periodic, on demand and event triggered | +| Description | The received energy per chip of the CPICH divided by the power density in the frequency band. | + +### 9.2.4 Void + +### 9.2.5 CPICH RSCP + +This measure is mandatory for UE with FDD mode capability. + +| | | +|-------------------|------------------------------------------| +| Measurement | CPICH RSCP | +| Source | L1(UE) | +| Destination | RRC (UE, RNC) | +| Reporting Trigger | periodic or event triggered | +| Description | Received signal code power of the CPICH. | + +### 9.2.6 P-CCPCH RSCP + +This measure is mandatory for UE with TDD mode capability. + +| | | +|-------------------|-------------------------------------------| +| Measurement | P-CCPCH RSCP | +| Source | L1(UE) | +| Destination | RRC (UE, RNC) | +| Reporting Trigger | periodic or event triggered | +| Description | Received signal code power of the P-CCPCH | + +### 9.2.7 Timeslot ISCP + +This measure is mandatory for UE with TDD mode capability. + +| | | +|-------------------|----------------------------------------------------------------------------------------------------| +| Measurement | Timeslot ISCP | +| Source | L1(UE) | +| Destination | RRC (UE, RNC) | +| Reporting Trigger | periodic or event triggered | +| Description | Interference Signal Code Power is the interference on the received signal in a specified timeslot. | + +### 9.2.8 Void + +### 9.2.9 SIR + +This measure is mandatory for UE with TDD mode capability. + +| | | +|-------------------|------------------------------------------------------------| +| Measurement | SIR | +| Source | L1(UE) | +| Destination | RRC (UE,RNC) | +| Reporting Trigger | Periodic, once every power control cycle , event triggered | +| Description | Signal to Interference Ratio | + +### 9.2.10 UTRA carrier RSSI + +This measure is mandatory for UE. + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | UTRA carrier RSSI | +| Source | L1(UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered, on demand | +| Description | Received Signal Strength Indicator, the wideband received power within the relevant channel bandwidth. For TDD this is measured in specified timeslots. | + +### 9.2.11 GSM carrier RSSI + +This measure is mandatory for UE with GSM capability. + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | GSM carrier RSSI | +| Source | L1(UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered, on demand | +| Description | Received Signal Strength Indicator, the wide-band received power within the relevant channel bandwidth. Details are specified in the GSM specification 05.08 | + +### 9.2.12 Transport channel BLER + +This measure is mandatory for UE. + +| | | +|-------------------|--------------------------------------------------------------| +| Measurement | Transport channel BLER (BBlock Error Rate) | +| Source | L1(UE) | +| Destination | RRC (RNC,UE) | +| Reporting Trigger | Periodic, on demand | +| Description | Estimation of the transport channel block error rate (BLER). | + +### 9.2.13 UE transmitted power + +This measure is mandatory for UE. + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------| +| Measurement | UE transmitted power | +| Source | L1(UE) | +| Destination | RRC (UE,RNC) | +| Reporting Trigger | On-demand, periodic, Event-triggered | +| Description | Sum of the total UE transmitted power on all configured uplink carriers. For TDD this is measured in specified timeslots. | + +### 9.2.14 UE Rx-Tx time difference + +This measure is mandatory for UE with FDD mode capability. + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | UE Rx-Tx time difference | +| Source | L1 (UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, periodic, event-triggered | +| Description | Time difference between the UE uplink DPCCH/DPDCH frame transmission and the first detected path (in time) of the downlink DPCH or F-DPCH frame from the measured radio link. Type 1 and Type 2 are defined. | + +### 9.2.15 SFN-SFN Observed time difference + +This measure is mandatory for UE. + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------| +| Measurement | SFN-SFN observed time difference | +| Source | L1 (UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered | +| Description | Time difference between a specific reference UTRA cell and a target UTRA cell. Type 1 and Type 2 are defined. | + +### 9.2.16 UE GPS Timing of Cell Frames for UE positioning + +This measure is mandatory for UE that has the capability to measure GPS reference time. + +| | | +|-------------------|----------------------------------------------------| +| Measurement | UE GPS Timing of Cell Frames for UE positioning | +| Source | L1 (UE) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The timing between UTRA cell and GPS Time Of Week. | + +### 9.2.17 Timing Advance ( $T_{ADV}$ ) for 1.28 Mcps TDD + +This measure is mandatory for 1.28 Mcps TDD UE. + +| | | +|-------------------|----------------------------------------------------------------------------------| +| Measurement | Timing Advance ( $T_{ADV}$ ) for 1.28 Mcps TDD | +| Source | L1 (UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | Difference between the uplink transmission of the UE and the downlink reception. | + +### 9.2.18 UE GPS code phase + +This measure is mandatory for UE with UE-assisted GPS capability. + +NOTE: The UE transmits the GPS code phase in the IE "Whole GPS Chips" and in the IE "Fractional GPS Chips" defined in [13]. + +| | | +|-------------------|-----------------------------------------------------------------------------------| +| Measurement | UE GPS code phase | +| Source | L1 (UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The whole and fractional phase of the spreading code of the GPS satellite signal. | + +### 9.2.19 UE GANSS Timing of Cell Frames for UE positioning + +This measure is mandatory for UE that has the capability to measure GANSS reference time for a given GANSS system and signal. + +| | | +|-------------------|-----------------------------------------------------| +| Measurement | UE GANSS Timing of Cell Frames for UE positioning | +| Source | L1 (UE) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The timing between UTRA cell and GANSS Time of Day. | + +### 9.2.20 UE GANSS code measurement + +This measure is mandatory for UE with UE-assisted GANSS capability. + +NOTE: The UE transmits the GANSS code phase in the IE "GANSS Code Phase" and in the IE "GANSS Integer Code Phase" defined in [13]. + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------| +| Measurement | UE GANSS code phase | +| Source | L1 (UE) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The code phase and optionally the Integer code phase of the spreading code of the GANSS satellite signal. | + +### 9.2.21 UE transmission power headroom + +This measure is mandatory for UE with FDD mode capability. + +| | | +|-------------------|-------------------------------------------------------------------------------------------------| +| Measurement | UE transmission power headroom | +| Source | L1(UE) | +| Destination | MAC (UE, Node B) | +| Reporting Trigger | Periodic, Event-triggered | +| Description | For each uplink DPCCH, the ratio of the maximum UE transmission power and the DPCCH code power. | + +## 9.3 UTRAN Measurements + +### 9.3.1 Received total wide band power + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Received total wide band power | +| Source | L1 (Node B) | +| Destination | RRC(RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The received wide band power including noise generated in the receiver, within the bandwidth defined by the pulse shaping filter. For TDD mode, this is measured in specified timeslots. | + +### 9.3.2 Transmitted carrier power + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Transmitted carrier power | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, periodic, Event-triggered | +| Description | Transmitted carrier power is the ratio between the total transmitted power on one DL carrier from one UTRAN access point, compared to the maximum power possible to use on that DL carrier at this moment of time. For TDD mode, this is measured in specified timeslots. | + +### 9.3.3 Transmitted code power + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Transmitted code power | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, periodic, Event-triggered | +| Description | Transmitted Code Power is the transmitted power on one carrier, one scrambling and one channelisation code. For TDD mode, this is measured in specified timeslots. | + +### 9.3.4 Void + +### 9.3.5 Physical channel BER + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Physical channel BER | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, periodic | +| Description | The Physical channel BER is an estimation of the average bit error rate (BER) on the DPCCH of a Radio Link Set.
This measurement applies to FDD mode only. | + +### 9.3.6 Transport channel BER + +| | | +|-------------------|-------------------------------------------------------------------------------------------| +| Measurement | Transport channel BER | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, periodic | +| Description | The transport channel BER is an estimation of the average bit error rate (BER) data part. | + +### 9.3.7 RX timing deviation + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | RX timing deviation | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered | +| Description | The difference of the time of arrival of the UL transmissions in relation to the arrival time of a signal with zero propagation delay. This measurement is applicable for TDD mode. | + +### 9.3.8 Timeslot ISCP + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Timeslot ISCP | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | periodic or event triggered | +| Description | Interference on Signal Code Power, is the interference on the received signal in a specified timeslot. This measurement is applicable is applicable to TDD mode only. | + +### 9.3.9 RSCP + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | RSCP | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | periodic or event triggered | +| Description | Received Signal Code Power is the received power on DPCH or PRACH, PUSCH or HS-SICH. This measurement is applicable for TDD mode only. | + +### 9.3.10 Round Trip Time + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Round Trip Time | +| Source | L1(Node B or LMU) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | on demand, event triggered | +| Description | This is an estimate of the round trip time of signals between the Node B and the UE This measurement is applicable for FDD mode only. | + +### 9.3.11 Void + +### 9.3.12 Acknowledged PRACH preambles + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Acknowledged PRACH preambles | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered, On demand | +| Description | This measurement indicates the number of positive acquisition indicators used to allow transmission on the PRACH message part transmitted per access frame on each AICH. This measurement is applicable for FDD mode only. | + +### 9.3.13 Void + +### 9.3.14 Void + +### 9.3.15 SIR + +| | | +|-------------------|-------------------------------| +| Measurement | SIR | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered | +| Description | Signal to Interference Ratio. | + +### 9.3.16 PRACH Propagation Delay + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------| +| Measurement | Propagation delay | +| Source | L1( Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Event triggered, periodic | +| Description | The one-way propagation delay as measured during PRACH access. This measurement is applicable for FDD mode only. | + +### 9.3.17 UTRAN GPS Timing of Cell Frames for UE positioning + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------| +| Measurement | UTRAN GPS Timing of Cell Frames for UE positioning | +| Source | L1 (LMU) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | This is the absolute time reference measurement in respect to GPS Time Of Week for the transmission of a particular frame. | + +### 9.3.18 SIR ERROR + +| | | +|-------------------|------------------------------------------------------------------------------------------| +| Measurement | SIR ERROR | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered | +| Description | Signal to Interference Ratio Error
This measurement is applicable for FDD cells only. | + +### 9.3.19 Received SYNC\_UL Timing Deviation + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Received SYNC_UL Timing Deviation | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Event triggered | +| Definition | 'Received SYNC_UL Timing Deviation' is the time difference
$UpPCH_{POS} = UpPTS_{Rxpath} - UpPTS_{TS}$ Where
$UpPTS_{Rxpath}$ : time of the reception in the Node B of the SYNC_UL to be used in the uplink synchronization process
$UpPTS_{TS}$ : time instance two symbols prior to the end of the DwPCH according to the Node B internal timing | + +### 9.3.20 Cell Sync Burst Timing + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Cell Sync Burst Timing | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered | +| Definition | Cell sync burst timing is the time of start (defined by the first detected path in time) of the cell sync burst of a neighbouring cell. Type 1 is used for the initial phase of Node B synchronization. Type 2 is used for the steady-state phase of Node B synchronization. | + +### 9.3.21 Cell Sync Burst SIR + +| | | +|-------------------|---------------------------------------------------------------------------------------------| +| Measurement | Cell Sync Burst SIR | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Periodic, event triggered | +| Definition | Signal to Interference Ratio for the cell sync burst, defined as: RSCP/Interference, where: | + +### 9.3.22 SFN-SFN Observed time difference + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------| +| Measurement | SFN-SFN observed time difference | +| Source | L1 (LMU) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | On-demand, Periodic, On Modification | +| Description | Measured time between reception of signal from a specific reference UTRA cell and from a neighbour UTRA cell. | + +### 9.3.23 Angle of Arrival (AOA) for 1.28 Mcps TDD + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Angle of Arrival (AOA) for 1.28Mcps TDD | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | Event-triggered, on-demand | +| Description | AOA defines the estimated angle of a user with respect to a reference direction. The reference direction for this measurement shall be the North, positive in a counter-clockwise direction.
The AOA is determined at the UTRAN access point antenna for an UL channel corresponding to this UE. | + +### 9.3.24 HS-SICH reception quality + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | HS-SICH reception quality | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The HS-SICH reception quality is defined via the the number of expected HS-SICH transmissions from a given UE and the number of unsuccessful HS-SICH receptions for this same UE in the Node B. For 1.28 Mcps TDD, only measurements made on HS-SICH transmissions that were transmitted using open loop power control are reported as part of this measurement.

This measurement is applicable for TDD cells only. | + +### 9.3.25 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, periodic, Event-triggered | +| Description | Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission is the ratio between the total transmitted power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission on one DL carrier from one UTRAN access point, and the maximum transmission power possible to use on that DL carrier at this moment of time.

For TDD mode, this is measured in specified timeslots. | + +### 9.3.26 UpPTS interference (1.28Mcps TDD) + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | UpPTS interference (1.28Mcps TDD) | +| Source | L1 (Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, periodic, Event-triggered | +| Description | The level of interference in the UpPTS is the difference between the mean received power in the UpPTS and the sum of the estimated mean power levels of all detected UpPCH transmissions. In the case of antenna diversity, the linear average of the UpPTS interference levels for each antenna branch shall be calculated. The reference point for the UpPTS interference measurement shall be the Rx antenna connector. | + +### 9.3.27 DL Transmission Branch Load + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | DL Transmission Branch Load | +| Source | L1(Node B) | +| Destination | RRC (RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | The 'DL transmission branch load' is the maximum of the transmission branch loads calculated for each branch.
A 'transmission branch load' is the ratio between the total transmitted power [W] on the considered branch and the 'maximum DL branch capability' on this branch.
The 'maximum DL branch capability' defines the maximum transmission power possible to use on that branch.
The reference point for the transmission branch load measurement shall be the TX antenna connector. | + +### 9.3.28 Received scheduled E-DCH power share (RSEPS) + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Received scheduled E-DCH power share (RSEPS) | +| Source | L1 (Node B) | +| Destination | RRC(RNC) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description |

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

1. RSEPS: defined as a quotient:
sum of all scheduled E-DPDCH and corresponding E-DPCCH power contributions determined in the RSEPS measurement period T=t2-t1>0 for all UEs for which this cell is the serving E-DCH cell divided by the corresponding total received wideband power value determined for this cell during T.

2. RTWP*:
This is the received total wideband power (RTWP) measured for this cell as defined in section 9.3.1 but determined for the same time period T starting at t1 and ending at t2 during which RSEPS is determined.

If the E-DPCCH can but the E-DPDCH transport block can not be decoded successfully even from subsequent retransmissions, it is considered as scheduled transmission.
The reference point for the RSEPS and RTWP* measurements shall be the Rx antenna connector.
When cell portions are defined in the cell, RSEPS (and RTWP*) shall be measured for each cell portion.

This measurement applies to FDD mode only.

| + +### 9.3.29 UTRAN GANSS Timing of Cell Frames for UE positioning + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | UTRAN GANSS Timing of Cell Frames for UE positioning | +| Source | L1 (LMU) | +| Destination | RRC (RNC-UE positioning) | +| Reporting Trigger | On-demand, Event-triggered, Periodic | +| Description | This is the absolute time reference measurement in respect to GANSS Time Of Day for the transmission of a particular frame. This is provided in a specific GANSS system time. | + +### 9.3.30 Common E-DCH resource usage + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement | Common E-DCH resource usage | +| Source | L1(Node B) | +| Destination | RRc (RNC) | +| Reporting Trigger | Periodic, event triggered, On demand | +| Description |

This measurement pertains only to the case where Enhanced Uplink in CELL_FACH state and Idle mode is enabled in the considered cell. This measurement is applicable for FDD mode only. The 'Common E-DCH resource usage' is defined as a report of 5 values for a considered cell:

  1. 1. Granted E-DCH Resources: defined as the number of common E-DCH resources that have been granted per access frame on each AICH. In case Concurrent deployment of 2ms and 10ms TTI is configured in a cell, it is defined as the number of 10ms TTI common E-DCH resources that have been granted per access frame on each AICH for the UEs that request for 10ms TTI common E-DCH resource.
  2. 2. Denied E-DCH Resources: defined as the number of PRACH preambles received at the NodeB that were not granted a common E-DCH resource. In case Concurrent deployment of 2ms and 10ms TTI is configured in a cell, it is defined as the number of PRACH preambles received at the NodeB that were not granted a 10ms TTI common E-DCH resource for the UEs that requested for 10ms TTI common E-DCH resource.
  3. 3. 2ms Granted E-DCH RACH Resources: defined as the number of 2ms TTI common E-DCH resources that have been granted per access frame on each AICH in case Concurrent deployment of 2ms and 10ms TTI is configured in a cell.
  4. 4. 2ms Overridden E-DCH RACH Resources: defined as the number of 10ms TTI common E-DCH resources that have been granted per access frame on each AICH for the UEs that request for 2ms TTI but are granted 10ms TTI common E-DCH resources in case Concurrent deployment of 2ms and 10ms TTI is configured in a cell.
  5. 5. 2ms Denied E-DCH RACH Resources: defined as the number of PRACH preambles received at the NodeB that are granted neither a 2ms nor 10ms TTI common E-DCH resource for the UEs that request for 2ms TTI common E-DCH resource in case of Concurrent deployment of 2ms and 10ms TTI is configured in a cell.
| + +# --- 10 Primitives of the physical layer + +The Physical layer interacts with other entities as illustrated in figure 1. The interactions with the MAC layer and the RRC layer are shown in terms of primitives where the primitives represent the logical exchange of information and control between the physical layer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points (SAPs). Primitives, therefore, are the conveyers of the information exchange and control through SAPs. + +Four types of primitives are used for the present document, as follows. + +- **REQUEST (REQ):** + - This type is used when a higher layer is requesting a service from a lower layer. +- **INDICATION (IND):** + - This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer. +- **RESPONSE (RESP):** + - This type is used by a higher layer providing the indicated service to respond to its lower layer that the activity has been completed. +- **CONFIRM (CNF):** + - This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed. + +The primitives defined below are for local communications between MAC and L1, as well as RRC and L1 in the same protocol stack. + +For the physical layer two sets of primitives are defined: + +- **Primitives between layer 1 and 2:** + - PHY - Generic name - Type: Parameters. +- **Primitives between layer 1 and the RRC entity:** + - CPHY - Generic name - Type: Parameters. + +NOTE: This is a logical description of the primitives and does not cover addressing aspects (e.g. Transport Channel ID, Physical Channel ID, start frame number or disconnect frame number). + +## 10.1 Generic names of primitives between layers 1 and 2 + +The primitives between layer 1 and layer 2 are shown in table 7. + +**Table 7: Primitives between layer 1 and 2** + +| Generic Name | Parameter | | | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------|------------------------| +| | REQ | IND | RESP | CNF | +| PHY-Access | Transport Format subset (1), ASC selected for Transport Block Set to be transmitted (5) Random Access Type (9), Random access for common E-DCH transmission (1) | Not Defined | Not Defined | access information (1) | +| PHY-Data | TFI, E-TFI (8), Transport Block Set, CFN CELL , TTI within CFN (7), Paging Indicators (2), ASC selected for that Transport Block Set (3), HS-DSCH information (6), E-DCH information (8) | TFI, E-TFI (8) Transport Block Set, CRC check result, TD (4), HARQ process (7) | Not Defined | Not Defined | +| PHY-Status | HARQ status (7) | Event value, HS-DSCH Feedback information (7) | Not Defined | Not Defined | + +NOTE (1): FDD only. +NOTE (2): PCH only +NOTE (3): 3.84/7.68 Mcps TDD RACH only +NOTE (4): optional, TDD only +NOTE (5): FDD RACH, and 1.28 Mcps TDD RACH and E-DCH access only +NOTE (6): HS-DSCH only +NOTE (7): HS-DSCH and E-DCH only +NOTE (8): E-DCH only +NOTE (9): 1.28 Mcps TDD only + +### 10.1.1 PHY-Access-REQ + +The PHY-Access-REQ primitive is used to request access to either a RACH transport channel from the physical layer. A PHY-Access primitive is submitted once before the actual data for peer-to-peer communication is passed to the physical layer using the PHY-Data primitive. This primitive is used in FDD and 1.28 Mcps TDD only. + +In FDD, the PHY-Access-REQ primitive is also used to request the physical layer to access a common E-DCH transport channel. A PHY-Access-REQ primitive is submitted before the actual data for peer-to-peer communication is passed to the physical layer. + +#### **Parameters:** + +- Transport Format subset. +- ASC selected for Transport Block Set to be transmitted (FDD RACH, FDD common E-DCH and 1.28 Mcps TDD RACH and E-DCH access only) +- Random Access Type (1.28 Mcps TDD only) +- Random access for common E-DCH transmission (FDD only for common E-DCH) + +### 10.1.2 PHY-Access-CNF + +The PHY-Access-CNF primitive is used to confirm that physical layer synchronisation has been established and that the physical layer is ready for data transmission using the PHY-Data primitive. This primitive is used in FDD and 1.28 Mcps TDD only. + +#### **Parameters:** + +- access information. + +### 10.1.3 PHY-Data-REQ + +The PHY-Data primitives are used to request SDUs used for communications passed to and from the physical layer. One PHY-Data primitive is submitted every Transmission Time Interval for each Transport Channel. + +#### **Parameters:** + +- TFI; +- E-TFI (E-DCH only); +- HARQ Process (TDD E-DCH only); +- Transport Block Set; +- CFNCELL; +- TTI within CFN (HS-DSCH and FDD E-DCH (2ms TTI) only); +- Page Indicators (PIs) (PCH only); +- HS-DSCH information (HS-DSCH information); +- E-DCH information (E-DCH information); +- ASC selected for that Transport Block Set (3.84/7.68 Mcps TDD RACH only); +- Random access type (1.28 Mcps TDD RACH only). + +### 10.1.4 PHY-Data-IND + +The PHY-Data primitives are used to indicate SDUs used for Layer 2 passed to and from the physical layer. One PHY-Data primitive is submitted every Transmission Time Interval for each Transport Channel. + +#### **Parameters:** + +- TFI; +- E-TFI (E-DCH only); +- Transport Block Set; +- CRC check result; +- TD (RX Timing Deviation measurement) (optional, TDD only); + +- Process Id (HS-DSCH and E-DCH only); +- Retransmission number (E-DCH only). + +### 10.1.5 Void + +### 10.1.6 Void + +### 10.1.7 PHY-Status-IND + +The PHY-Status-IND primitive can be used by the layer 1 to notify higher layers of an event that has occurred. + +#### Parameters: + +- Feedback information (HS-DSCH and E-DCH only); +- Event value: + - L1 hardware failure has occurred. + +## 10.2 Generic names of primitives between layers 1 and 3 + +The status primitives between layer 1 and 3 are shown in table 8. + +**Table 8: Status primitives between layer 1 and 3** + +| Generic Name | Parameter | | | | +|-------------------------|------------------------------------------------------|------------------------|-------------|-------------| +| | REQ | IND | RESP | CNF | +| CPHY-Sync | Not Defined | CCTrCH ID (1) | Not Defined | Not Defined | +| CPHY-Out-of-Sync | Not Defined | CCTrCH ID (1) | Not Defined | Not Defined | +| CPHY-Measurement | transmission power threshold, measurement parameters | measurement parameters | Not Defined | Not Defined | +| CPHY-Error | Not Defined | error code | Not Defined | Not Defined | +| NOTE (1): TDD only. | | | | | + +### 10.2.1 STATUS PRIMITIVES + +#### 10.2.1.1 CPHY-Sync-IND + +This primitive is used for L1 to indicate to RRC that synchronisation of a certain physical channel has been done in the receiver. In FDD synchronisation is based on reception of the DPCCH or F-DPCH, and in TDD synchronisation is based on Special Burst, TB reception, and DPCH burst quality estimation. For 3.84/7.68 Mcps TDD, when the UE is in cell\_DCH state but no DL DPCH is configured the primitive is based on the methods specified in [5]. + +##### Parameters: + +- CCTrCH ID (TDD only). + +#### 10.2.1.2 CPHY-Out-of-Sync-IND + +Primitive sent from L1 to RRC indicating that synchronisation of a previously configured connection has been lost in the receiver. In FDD synchronisation is based on reception of the DPCCH or F-DPCH, and in TDD synchronisation is based on Special Burst, TB reception, and DPCH burst quality estimation. For 3.84 /7.68 Mcps TDD, when the UE is in cell\_DCH state but no DL DPCH is configured the primitive is based on the methods specified in [5]. + +##### Parameters: + +- CCTrCH ID (TDD only). + +#### 10.2.1.3 CPHY-Measurement-REQ + +The Request primitive is used for RRC to configure L1 measurements. + +##### **Parameters:** + +- transmission power threshold; +- refer to clause 9 for measurement parameters. + +#### 10.2.1.4 CPHY-Measurement-IND + +The Indication primitive is used to report the measurement results. + +##### **Parameters:** + +- refer to clause 9 for measurement parameters. + +#### 10.2.1.5 CPHY-Error-IND + +The CPHY-Error primitive is used to indicate to the management entity that an error has occurred as a result of a physical layer fault. + +##### **Parameters:** + +- error code. + +#### 10.2.1.6 Void + +### 10.2.2 CONTROL PRIMITIVES + +The control primitives between layer 1 and 3 are shown in table 9. + +**Table 9: Control primitives between layer 1 and 3** + +| Generic Name | Parameter | | | | +|--------------------------------|----------------------------------|-------------|-------------|--------------| +| | REQ | IND | RESP | CNF | +| CPHY-TrCH-Config | transport channel description | Not Defined | Not Defined | No Parameter | +| CPHY-TrCH-Release | No Parameter | Not Defined | Not Defined | No Parameter | +| CPHY-RL-Setup | physical channel description | Not Defined | Not Defined | No Parameter | +| CPHY-RL-Release | No Parameter | Not Defined | Not Defined | No Parameter | +| CPHY-RL-Modify | physical channel description | Not Defined | Not Defined | No Parameter | +| CPHY-Commit | activation time | Not Defined | Not Defined | Not Defined | +| CPHY-Out-of-Sync-Config | Out of Sync detection parameters | Not Defined | Not Defined | No Parameter | +| CPHY-MBMS-Config | MBMS information | Not Defined | Not Defined | No Parameter | + +#### 10.2.2.1 CPHY-TrCH-Config-REQ + +This primitive is used for setting up and configuring a transport channel, and also to modify an existing transport channel. + +##### **Parameters:** + +- transport channel description. + +#### 10.2.2.2 CPHY-TrCH-Config-CNF + +This primitive is used for confirming the setting up and configuring a transport channel, and also modifying an existing transport channel. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.3 CPHY-TrCH-Release-REQ** + +This primitive is used for releasing a transport channel. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.4 CPHY-TrCH-Release-CNF** + +This primitive is used for confirming the releasing a transport channel. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.5 CPHY-RL-Setup-REQ** + +The Request primitive is sent from RRC to L1 for establishment of a Radio link to a certain UE. + +##### **Parameters:** + +- physical channel description. + +#### **10.2.2.6 CPHY-RL-Setup-CNF** + +The Confirm primitive is returned from L1 to RRC when the Radio link is established. In case L1 is unable to execute the request, this is indicated in the confirm primitive. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.7 CPHY-RL-Release-REQ** + +The Request primitive is sent from RRC to L1 for release of a Radio link to a certain UE. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.8 CPHY-RL-Release-CNF** + +The Confirm primitive is returned from L1 to RRC when the radio link is released. + +##### **Parameters:** + +- No Parameter. + +#### **10.2.2.9 CPHY- RL-Modify-REQ** + +The Request primitive is sent from RRC to L1 for modification of a Radio link to a certain UE. + +##### **Parameters:** + +- physical channel description. + +#### **10.2.2.10 CPHY-RL-Modify-CNF** + +The Confirm primitive is returned from L1 to RRC when the radio link is modified. In case L1 is unable to execute the request, this is indicated in the confirm primitive. + +##### **Parameters:** + +- No Parameter. + +#### 10.2.2.11 CPHY-Commit-REQ + +This primitive is sent from RRC to L1 to synchronise UE and NW for the physical channel modification. + +##### **Parameters:** + +- activation time. + +#### 10.2.2.12 Void + +#### 10.2.2.13 Void + +#### 10.2.2.14 Void + +#### 10.2.2.15 Void + +#### 10.2.2.16 CPHY-Out-of-Sync-Config-REQ + +This primitive is sent from RRC to Node B L1 to reconfigure the parameters to detect "in sync" and "out of sync" conditions of uplink physical channel transmission. + +##### **Parameters:** + +- Out of Sync detection parameters + +#### 10.2.2.17 CPHY-Out-of-Sync-Config-CNF + +This primitive is sent from Node B L1 to RRC for confirming the Reconfiguration of the Out-of-Sync parameters on Node B L1. + +##### **Parameters:** + +- No Parameter. + +#### 10.2.2.18 CPHY-MBMS-Config-REQ + +This primitive is sent from UE RRC to L1 for the configuration of the MBMS information. + +##### **Parameters:** + +- MBMS information. + +#### 10.2.2.19 CPHY-MBMS-Config-CNF + +This primitive is used to confirm the configuration of the MBMS information. + +##### **Parameters:** + +- No Parameter. + +## 10.3 Parameter definition + +### 10.3.1 Error code + +- Hardware failure. + +### 10.3.2 Event value + +- Maximum transmission power has been reached. +- Allowable transmission power has been reached. +- Average transmission power is below allowable transmission power. +- Maximum number of retransmissions has been reached. +- Loss of DL DPCCH. + +### 10.3.3 Access Information + +- Ready for RACH data transmission (in case of FDD mode: when Ack on AICH has been received and Random access for common E-DCH transmission was not included in the PHY-Access-REQ, in case of 1.28 Mcps TDD: when Ack on FPACH has been received); +- timeout, no response on AICH (FDD only) or FPACH (1.28 Mcps TDD only) has been received while maximum number of access preamble transmissions (FDD only) /synchronisation attempts (1.28 Mcps TDD only) has been performed. + +The following value of this parameter apply to FDD only: + +- NACK has been received carried with an AI, if the use of E-AIs is not configured, or carried with an E-AI, if the use of E-AIs is configured on AICH; +- E-DCH resource index received on AICH (when Ack carried with an AI has been received, or when Nack carried with an AI and no Nack carried with an E-AI has been received), if Random access for common E-DCH transmission was included in the PHY-Access-REQ. + +### 10.3.4 Transport Format Subset + +- A subset of the Transport Format set of a Transport Channel. + +### 10.3.5 Physical channel description + +#### 10.3.5.1 Primary SCH + +- Tx diversity mode. + +#### 10.3.5.2 Secondary SCH + +- Tx diversity mode. + +#### 10.3.5.3 Primary CCPCH + +- Frequency info. +- DL scrambling code. +- Tx diversity mode. +- Timeslot (TDD only). +- Burst type (3.84/7.68 Mcps TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). + +#### 10.3.5.4 Secondary CCPCH + +- DL scrambling code. +- Channelisation code. +- Tx diversity mode. +- Timeslot (TDD only). +- Burst type (3.84/7.68 Mcps TDD only). +- Midamble shift (TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). +- TFCI presence (TDD only). +- MCCH modification period (only S-CCPCH carrying MCCH). +- MCCH repetition period (only S-CCPCH carrying MCCH). +- MCCH access info period (only S-CCPCH carrying MCCH). +- MSCH scheduling period/offset (only S-CCPCH carrying MSCH). + +#### 10.3.5.4a Secondary CCPCH frame type 2 + +- Channelisation code(s). +- Sub-frame. +- MSCH scheduling period/offset (only S-CCPCH carrying MSCH). + +#### 10.3.5.5 PRACH + +- Access Slot (FDD only). +- Preamble scrambling code (FDD only). +- Available preamble signatures (FDD only). +- Spreading factor for data part. +- Power control info: + - UL target SIR; + - primary CCPCH DL TX Power; + - UL interference; + - power offset (Power ramping) (FDD only). +- Access Service Class Information (PRACH Partitioning): + - Available signatures for each ASC (FDD only). + - Available Channelisation codes for each ASC (TDD only). + - Available Subchannels for each ASC. +- AICH transmission timing parameter (FDD only). + +- Timeslots (TDD only). +- Available Channelisation Codes (TDD only) +- Spreading Factor (TDD only). +- Midamble Type (TDD only). + +#### 10.3.5.6 Uplink DPDCH+DPCCH + +- UL scrambling code. +- DPCCH slot structure ( $N_{\text{pilot}}, N_{\text{TPC}}, N_{\text{TFCI}}, N_{\text{FBI}}$ ). +- Transmission Time offset value. + +#### 10.3.5.7 Uplink DPCH + +- Timing Advance (TDD only). +- DPCH channelisation code (TDD only). +- Burst Type (3.84/7.68 Mcps TDD only). +- DPCH midamble shift (TDD only). +- Timeslot (TDD only). +- Offset (TDD only). +- Repetition Period (TDD only). +- Repetition length (TDD only). +- TFCI presence (TDD only). + +#### 10.3.5.8 Downlink DPCH + +- Transmission Time offset value. +- DL scrambling code: + - DL Channelisation code. +- Tx diversity mode: + - FB mode (FDD only). +- Slot structure ( $N_{\text{pilot}}, N_{\text{TPC}}, N_{\text{TFCI}}, N_{\text{FBI}}, N_{\text{data1}}, N_{\text{data2}}$ ) (FDD only). +- Burst Type (3.84/7.68 Mcps TDD only). +- DPCH midamble shift (TDD only). +- Timeslot (TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). +- TFCI presence (TDD only). + +#### 10.3.5.8a F-DPCH (FDD only) + +- Transmission Time offset value. + +- DL scrambling code: + - DL Channelisation code. + +#### 10.3.5.9 Void + +#### 10.3.5.10 PICH + +- Scrambling code. +- Channelisation code. +- Timeslot (TDD only). +- Burst Type (3.84/7.68 Mcps TDD only). +- Midamble shift (TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). + +#### 10.3.5.11 AICH + +- Scrambling code. +- Channelisation code. +- Tx diversity mode. + +NOTE: The value for the parameters needs to be consistent with the corresponding PRACH. + +#### 10.3.5.12 Void + +#### 10.3.5.13 Void + +#### 10.3.5.14 Void + +#### 10.3.5.15 Void + +#### 10.3.5.16 PDSCH (TDD only) + +- Scrambling code. +- Channelisation code. +- Tx diversity mode: +- DL channelisation code (TDD only). +- Burst Type (3.84/7.68 Mcps TDD only). +- PDSCH Midamble shift (TDD only). +- Timeslot (TDD only). + +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). +- TFCI presence (TDD only). + +#### 10.3.5.17 PUSCH + +- PUSCH channelisation code. +- Burst Type (3.84/7.68 Mcps TDD only). +- PUSCH midamble shift (TDD only). +- Timeslot (TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). +- TFCI presence (TDD only). +- Timing Advance (TDD only). + +#### 10.3.5.18 DwPCH (1.28 Mcps TDD only) + +- Tx diversity mode. +- SYNC\_DL code ID. + +#### 10.3.5.19 UpPCH (1.28 Mcps TDD only) + +- SYNC\_UL code ID. + +#### 10.3.5.20 FPACH (1.28 Mcps TDD only) + +- Scrambling code +- Channelisation code +- Timeslot +- Midamble shift +- Tx diversity mode. + +#### 10.3.5.21 PNB SCH (Physical Node B Synchronisation channel) + +- Node B - Node B over the air communication. +- Only for TDD cells. +- Repetition period. +- Concatenated periodically Extended Complementary sequences. + +#### 10.3.5.22 HS-SCCH + +- Scrambling code. +- Channelisation code. +- Timeslot (TDD only). + +- Burst type (3.84/7.68 Mcps TDD only). + +#### 10.3.5.23 HS-SICH (TDD only) + +- Channelisation code. +- Burst Type 1 (3.84/7.68 Mcps TDD only). +- Midamble shift. +- Timeslot. + +#### 10.3.5.24 E-AGCH + +- Scrambling code. +- Channelisation code. +- Tx diversity mode. +- Timeslot (TDD only). +- Burst type (3.84 Mcps and 7.68 Mcps TDD only). + +#### 10.3.5.25 E-DPCCH (FDD only) + +- No parameter. + +#### 10.3.5.26 E-DPDCH (FDD only) + +- No parameter. + +#### 10.3.5.27 E-HICH + +FDD: + +- Scrambling code. +- Channelisation code. +- Hadamard sequence. + +TDD: + +- Scrambling code. +- Channelisation code. +- First Hadamard sequence. +- Second Hadamard sequence. +- Timeslot. + +#### 10.3.5.28 E-RGCH (FDD only) + +- Scrambling code. +- Channelisation code. +- Hadamard sequence. + +#### 10.3.5.28a E-RUCCH (TDD only) + +- Power control info: + - UL target SIR; + +- primary CCPCH DL TX Power; +- UL interference. +- Timeslot; +- Available Channelisation Code; +- Random access type (1.28 Mcps TDD only) + +#### 10.3.5.29 MICH + +- Scrambling code. +- Channelisation code. +- Timeslot (TDD only). +- Burst Type (3.84/7.68 Mcps TDD only). +- Midamble shift (TDD only). +- Offset (TDD only). +- Repetition period (TDD only). +- Repetition length (TDD only). + +### 10.3.6 Feedback information + +In CELL\_DCH state: + +- Quality indication (HS-DSCH only). +- HARQ Status (HS-DSCH and E-DCH only). + +In CELL\_FACH state, if a common E-DCH is allocated to a UE (FDD only): + +- Quality indication (HS-DSCH only). +- HARQ Status (HS-DSCH and E-DCH only). + +In Idle mode, if a common E-DCH is allocated to a UE (FDD only): + +- HARQ Status (E-DCH only). + +### 10.3.7 HARQ process + +- Process Id. + +### 10.3.8 HS-DSCH information + +- Modulation scheme. +- Channelisation code. +- Timeslot (TDD only). +- Redundancy version/Constellation. +- Process Id. +- HS-SCCH Cyclic Sequence Number (HCSN) for TDD. + +### 10.3.9 HARQ status + +- HARQ acknowledgement (acknowledgement or negative acknowledgement). + +### 10.3.10 E-DCH information + +- Number of allowed redundancy versions. +- Maximum number of transmissions +- New transmission indication +- Process Id. +- Power offset + +### 10.3.11 MBMS information + +- MBMS L1 combining schedule. +- MBMS service transmission schedule. + +# --- 11 Transport block transmission + +Data exchange between MAC and the physical layer, is defined in terms of Transport Block Sets (TBS). On a Transport Channel, one Transport Block Set can be transmitted for every Transmission Time Interval. A TBS consists of one or several Transport Blocks which shall be numbered $1, \dots, m, \dots, M$ and is delivered in the order of the index $m$ . A Transport Block is identical with a MAC PDU. A Transport Block (MAC PDU) is a bit string ordered from first to last, where the first and last bits are numbered 1 and $A$ , respectively, where $A$ is the number of bits of the Transport Block. In case of Transport Block size=0 bit and $M \neq 0$ , only parity bits as given by the CRC size are sent and $A=0$ . This case is one realisation of an empty Transport Format. The second realisation of an empty Transport Format is represented by $M=0$ (no transport block). In this case, no parity bits are transmitted for this Transport Format. + +The bits of the $m$ th Transport Block in a TBS, are denoted as $a_{im1}, \dots, a_{imA}$ for a Transport Channel identified by an index $i$ (cf. [3] and [4]). + +# Annex A (normative): Description of Transport Formats + +The following table describes the characterisation of a Transport Format. + +**Table A.1: Characterisation of Transport Format** + +| | | Attribute values | BCH | PCH | FACH | RACH | +|------------------|--------------------------------------------------------------|--------------------------------------------------------------|-------------------------------------------------------------|------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Dynamic part | Transport Block Size | 0 to 5 000
1 bit granularity | 246 | 1 to 5000
1 bit granularity | 0 to 5 000
1 bit granularity | 0 to 5 000
1 bit granularity | +| | Transport Block Set Size | 0 to 200 000
1 bit granularity | 246 | 1 to 200 000
1 bit granularity | 0 to 200 000
1 bit granularity | 0 to 200 000
1 bit granularity | +| | Transmission Time Interval (option for TDD only) | 10, 20 ms, 40 and 80 ms | | | | | +| Semi-static part | Transmission Time Interval (FDD, option for TDD NRT bearers) | 10, 20 ms, 40 and 80 ms | 20 ms
40ms (only for 1.28 Mcps TDD MBSFN only mode) | 10ms for FDD, 20ms for TDD | 10, 20 ms, 40 and 80 ms | 10 ms and 20 ms for FDD,
10 ms for 3.84/7.68 Mcps TDD
5ms, 10ms and 20ms for 1.28 Mcps TDD | +| | Type of channel coding | No Coding (TDD only)
Turbo coding
Convolutional coding | Convolutional coding | Convolutional coding | No coding (TDD only)
Turbo coding
Convolutional coding | Convolutional coding | +| | Code rates | 1/2, 1/3 | 1/2 for FDD and 3.84/7.68 Mcps TDD
1/3 for 1.28 Mcps TDD | 1/2 for FDD and 3.84/7.68 Mcps TDD
1/2, 1/3 for 1.28 Mcps TDD | 1/2, 1/3 | 1/2 | +| | CRC size | 0, 8, 12, 16, 24 | 16 | 0, 8, 12, 16, 24 | 0, 8, 12, 16, 24 | 0, 8, 12, 16, 24 | +| | Resulting ratio after static rate matching | 0,5 to 4 | | | | | + +| | | Attribute values | DCH | DSCH | USCH | +|------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| Dynamic part | Transport Block Size | 0 to 5 000
1 bit granularity | 0 to 5 000
1 bit granularity | 0 to 5 000
1 bit granularity | 0 to 5 000
1 bit granularity | +| | Transport Block Set Size | 0 to 200 000
1 bit granularity | 0 to 200 000
1 bit granularity | 0 to 200 000
1 bit granularity | 0 to 200 000
1 bit granularity | +| | Transmission Time Interval (option for TDD only) | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | +| Semi-static part | Transmission Time Interval (FDD, option for TDD NRT bearers) | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | 10, 20 ms, 40 and 80 ms | +| | Type of channel coding | No coding (TDD only)
Turbo coding
Convolutional coding | No coding (TDD only)
Turbo coding
Convolutional coding | No coding (TDD only)
Turbo coding
Convolutional coding | No coding (TDD only)
Turbo coding
Convolutional coding | +| | code rates (in case of convolutional coding) | 1/2, 1/3 | 1/2, 1/3 | 1/2, 1/3 | 1/2, 1/3 | +| | CRC size | 0, 8, 12, 16, 24 | 0, 8, 12, 16, 24 | 0, 8, 12, 16, 24 | 0, 8, 12, 16, 24 | +| | Resulting ratio after static rate matching | 0,5 to 4 | | | | + +| | | HS-DSCH | +|--------------|----------------------------------|-----------------------------------------------------------------------| +| Dynamic part | Transport Block Size | 1 to 200 000
8 bit granularity | +| | Transport Block Set Size | 1 to 200 000
8 bit granularity | +| | Modulation scheme | QPSK, 16 QAM | +| | Redundancy version/Constellation | 1 to 8 | +| Static part | Transmission Time Interval | 2ms for FDD
5 ms for 1.28 Mcps TDD
10 ms for 3.84/7.68 Mcps TDD | +| | Type of channel coding | Turbo coding | +| | Code rates | 1/3 | +| | CRC size | 24 | + +| | | E-DCH | +|------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Dynamic part | Transport Block Size | FDD: 1 to 200 000
1 bit granularity
3.84 Mcps
TDD: 1 to 92014
1.28 Mcps
TDD: 1 to 11160 | +| | Transport Block Set Size | FDD: 1 to 200 000
1 bit granularity
3.84 Mcps
TDD: 1 to 92014
7.68 Mcps
TDD: 1 to 177130
1.28 Mcps
TDD: 1 to 11160 | +| | Redundancy version | 0 to 3 | +| Semi-static part | Transmission Time Interval | (FDD only)
2ms,
(FDD, 3.84 Mcps and 7.68 Mcps TDD)
10ms
(1.28 Mcps TDD) 5ms | +| Static part | Type of channel coding | Turbo coding | +| | Code rates | 1/3 | +| | CRC size | 24 | + +NOTE 1: The maximum size of the Transport Block has been chosen so as to avoid any need for segmentation in the physical layer into sub-blocks (segmentation should be avoided in the physical layer). + +NOTE 2: Code rate is fixed to 1/3 in case of Turbo coding. + +NOTE 3: All channels using the same resources as the BCH (i.e. the same timeslot and code, e.g. in a multiframe pattern) have to use different Transport Formats than the BCH to allow the identification of the BCH channel by physical layer parameters. Due to the differing parameters, decoding of other transport channels than BCH will result in an erroneous CRC. + +# Annex B (informative): Example of Transport format attributes for AMR speech codec + +The support for the AMR speech codec is exemplified below. On the radio interface, one Transport Channel is established per class of bits i.e. DCH A for class A, DCH B for class B and DCH C for class C. Each DCH has a different transport format combination set which corresponds to the necessary protection for the corresponding class of bits as well as the size of these class of bits for the various AMR codec modes. + +With this principle, the AMR codec mode which is used during a given TTI can be deduced from the format of the transport channels DCH A, DCH B and DCH C for that particular TTI. + +Note that a similar principle can also be applied for other source codecs e.g. other speech codecs or video codecs. + +An example of transport channel description for each class of bits is given in table B.1. + +**Table B.1** + +| | Attribute | Value | | | +|------------------|--------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------| +| | | Class A | Class B | Class C | +| Dynamic part | Transport Block Size | 81
65
75
61
58
55
49
42
39 | 103
99
84
87
76
63
54
53
0 | 60
40
0
0
0
0
0
0
0 | +| | Transport Block Set Size | Same as the transport block sizes | | | +| Semi-static part | Transmission Time Interval | 20 ms | | | +| | Type of channel coding | Convolutional coding | | | +| | code rates | 1/2, 1/3
+ class-specific rate matching | None (TDD only), 1/2, 1/3
+ class-specific rate matching | None (TDD only), 1/2, 1/3
+ class-specific rate matching | +| | CRC size | 8 | 0 | 0 | +| | Resulting ratio after static rate matching | 0.5 to 4 (with no coding the rate matching ratio needs to be >1) | | | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|------------------------------------------------------------------------------------------------------------------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 08/1999 | RP-04 | RP-99309 | - | | | Approved after TSG-RAN #4 and TSG-RAN WG2 #6 (08/1999) by correspondence and placed under Change Control | 3.0.0 | +| 10/1999 | RP-05 | RP-99461 | 001 | | | Making all transport block equally sized within a transport block set | 3.1.0 | +| | RP-05 | RP-99461 | 002 | 1 | | UE Simultaneous Physical Channel Combinations in TDD Mode | 3.1.0 | +| | RP-05 | RP-99461 | 004 | | | Timing advance (TDD only) | 3.1.0 | +| | RP-05 | RP-99461 | 005 | | | Measurements for TDD provided by physical layer | 3.1.0 | +| | RP-05 | RP-99461 | 006 | | | Change of the Downlink model of the UE in relation to PCH | 3.1.0 | +| | RP-05 | RP-99461 | 007 | | | Physical channel description for TDD | 3.1.0 | +| | RP-05 | RP-99461 | 008 | | | Attributes of the semi-static part and coding terminology | 3.1.0 | +| | RP-05 | RP-99461 | 009 | | | Editorial changes following LS received from WG1 | 3.1.0 | +| | RP-05 | RP-99461 | 010 | | | Support of Uplink Synchronization Feature in UL channels (TDD only) | 3.1.0 | +| | RP-05 | RP-99461 | 011 | | | Simultaneous reception of AICH and S-CCPCH | 3.1.0 | +| | RP-05 | RP-99461 | 012 | | | Removal of Measurement Precision Requirements | 3.1.0 | +| | RP-05 | RP-99461 | 013 | | | Compressed mode | 3.1.0 | +| | RP-05 | RP-99461 | 014 | | | Change of the model of the UE with respect to shared channel multiplexing | 3.1.0 | +| 12/1999 | RP-06 | RP-99624 | 015 | | | Alignment of measurement names with RAN | 3.2.0 | +| | RP-06 | RP-99623 | 018 | | | Compressed Mode description | 3.2.0 | +| | RP-06 | RP-99624 | 022 | | | Alignment with TDD layer 1 | 3.2.0 | +| | RP-06 | RP-99624 | 023 | 1 | | Physical Channel Parameters | 3.2.0 | +| | RP-06 | RP-99624 | 025 | | | Addition of PICH and Corrections for Primary | 3.2.0 | +| | RP-06 | RP-99624 | 026 | | | Removal of compressed mode inband signalling | 3.2.0 | +| | RP-06 | RP-99624 | 028 | 1 | | Measurement of Transmitted carrier power | 3.2.0 | +| | RP-06 | RP-99623 | 030 | 1 | | Editorial issues | 3.2.0 | +| | RP-06 | RP-99624 | 031 | | | Measurement of Physical Channel BER | 3.2.0 | +| 01/2000 | - | - | - | | | E-mail approval by TSG-RAN WG2 of different implementation of CR 015 and CR 028 according to authors' intentions | 3.3.0 | +| 03/2000 | RP-07 | RP-000035 | 032 | 2 | | Revision of CPCH model | 3.4.0 | +| | RP-07 | RP-000035 | 033 | 1 | | Error Correction Coding for FACH | 3.4.0 | +| | RP-07 | RP-000035 | 034 | 3 | | Revision of compressed mode description | 3.4.0 | +| | RP-07 | RP-000035 | 036 | | | TrBLK size | 3.4.0 | +| | RP-07 | RP-000035 | 037 | | | PDSCH multi-code | 3.4.0 | +| | RP-07 | RP-000035 | 038 | 1 | | Primitives for CPCH Abnormal Situation Handling | 3.4.0 | +| | RP-07 | RP-000035 | 039 | | | Physical channel BER | 3.4.0 | +| | RP-07 | RP-000035 | 041 | | | Editorial modification on AMR trblk size | 3.4.0 | +| | RP-07 | RP-000035 | 042 | 1 | | Corrections and clarifications on L1 and L2 functionality descriptions | 3.4.0 | +| | RP-07 | RP-000035 | 043 | 1 | | Transport Block Transmission | 3.4.0 | +| | RP-07 | RP-000035 | 044 | | | Clarification to layer 1 model regarding transport blocks received by UE with CRC failure | 3.4.0 | +| | RP-07 | RP-000035 | 045 | | | Removal of SCH and SCCH | 3.4.0 | +| | RP-07 | RP-000035 | 046 | | | Replacement of Time of Arrival Measurement by RTT | 3.4.0 | +| | RP-07 | RP-000035 | 047 | 1 | | Incorporation of Measurement filtering model | 3.4.0 | +| | RP-07 | RP-000035 | 048 | | | Separation of physical channel BER measurements | 3.4.0 | +| 06/2000 | RP-08 | RP-000215 | 049 | 1 | | Maximum number of simultaneous compressed mode pattern sequences per measurement purpose | 3.5.0 | +| | RP-08 | RP-000215 | 050 | 1 | | Removal of CPICH SIR measurement quantity | 3.5.0 | +| | RP-08 | RP-000215 | 051 | | | Measurements | 3.5.0 | +| | RP-08 | RP-000215 | 052 | 1 | | End of CPCH transmission | 3.5.0 | +| | RP-08 | RP-000215 | 053 | 1 | | Measurements of RACH and CPCH | 3.5.0 | +| | RP-08 | RP-000215 | 056 | | | Editorial modification on Transport Block Size | 3.5.0 | +| | RP-08 | RP-000215 | 057 | 3 | | CPCH correction | 3.5.0 | +| | RP-08 | RP-000215 | 058 | 1 | | SFN Transmission Rate and the Need to Maintain CFN in TDD Mode | 3.5.0 | +| | RP-08 | RP-000215 | 059 | | | Addition of out-of-sync-configuration control primitives | 3.5.0 | +| | RP-08 | RP-000215 | 060 | | | Addition of propagation delay measurement | 3.5.0 | +| | RP-08 | RP-000215 | 061 | 2 | | Layer 1 LCS measurements | 3.5.0 | +| | RP-08 | RP-000215 | 062 | 1 | | Refinement of the definition of a Transport Block | 3.5.0 | +| | RP-08 | RP-000215 | 063 | 1 | | Corrections of CPCH Emergency stop and start of message Indicator | 3.5.0 | +| | RP-08 | RP-000215 | 064 | | | BLER | 3.5.0 | +| 09/2000 | RP-09 | RP-000353 | 065 | | | Filtering period in case of periodical reporting | 3.6.0 | +| | RP-09 | RP-000353 | 066 | | | UE simultaneous Physical and Transport channel combinations for PDSCH and DSCH | 3.6.0 | +| | RP-09 | RP-000353 | 067 | | | Inclusion of SIR ERROR measurement | 3.6.0 | +| | RP-09 | RP-000353 | 068 | 1 | | Simultaneous reception of PCCPCH and SCCPCH | 3.6.0 | +| | RP-09 | RP-000353 | 070 | | | Removal of puncturing limit from the transport format definition | 3.6.0 | +| | RP-09 | RP-000353 | 071 | | | Clarification of the Timeslot ISCP Measurements | 3.6.0 | +| 12/2000 | RP-10 | RP-000563 | 072 | | | RACH model | 3.7.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| | RP-10 | RP-000563 | 073 | | | Clarification of UTRAN SIR measurement | 3.7.0 | +| | RP-10 | RP-000563 | 074 | | | Removal of compressed mode measurement purpose "other" | 3.7.0 | +| | RP-10 | RP-000563 | 075 | | | Removal of compressed mode measurement purpose "GSM" | 3.7.0 | +| | RP-10 | RP-000563 | 076 | | | Removal of physical channel BER measurement for TDD | 3.7.0 | +| | RP-10 | RP-000563 | 077 | | | CPCH model correction | 3.7.0 | +| | RP-10 | RP-000563 | 078 | 1 | | Removal of FAUSCH and ODMA | 3.7.0 | +| | RP-10 | RP-000563 | 080 | 2 | | Correction to transport channel mapping | 3.7.0 | +| | RP-10 | RP-000563 | 081 | | | Alignment of measurement reference description | 3.7.0 | +| | RP-10 | RP-000563 | 082 | | | Changing the name of "RSSI" to "Received total wide band power" | 3.7.0 | +| 03/2001 | RP-11 | RP-010020 | 084 | 2 | | Additional physical channel combination for FDD downlink to allow COUNT-C-SFN difference measurement | 3.8.0 | +| | RP-11 | RP-010020 | 087 | | | In & Out of Sync Indications per CCTrCH in TDD | 3.8.0 | +| | RP-11 | RP-010020 | 088 | | | Correction & Clarification to TDD RACH Model and Primitives | 3.8.0 | +| | RP-11 | RP-010020 | 089 | 1 | | Alignment of measurements provided by the physical layer | 3.8.0 | +| | RP-11 | RP-010020 | 092 | 1 | | Physical channel combinations in TDD | 3.8.0 | +| | RP-11 | RP-010020 | 094 | | | Measurement model clarifications | 3.8.0 | +| | RP-11 | RP-010020 | 095 | | | Removal of DPCCH Gating from Release 99 | 3.8.0 | +| | RP-11 | RP-010020 | 096 | 1 | | Clarification of simultaneous operation of DRAC and CTCH | 3.8.0 | +| | RP-11 | RP-010037 | 090 | 2 | | 1.28 Mcps TDD | 4.0.0 | +| | RP-11 | RP-010041 | 093 | 1 | | Measurements for Node B synchronisation | 4.0.0 | +| 06/2001 | RP-12 | RP-010303 | 100 | | | Physical Channel Combination | 4.1.0 | +| | RP-12 | RP-010303 | 102 | | | General corrections and clarifications | 4.1.0 | +| | RP-12 | RP-010303 | 105 | | | Definition of empty TF and TFC | 4.1.0 | +| | RP-12 | RP-010320 | 106 | | | Timing Advance (TADV) for 1.28 Mcps TDD | 4.1.0 | +| 09/2001 | RP-13 | RP-010537 | 098 | | | Transmission of selected ASC to physical layer | 4.2.0 | +| | RP-13 | RP-010537 | 108 | | | Corrected definition of the CCTrCH concerning BCH, RACH and CPCH | 4.2.0 | +| | RP-13 | RP-010537 | 110 | | | Transport Format Set Annex Correction | 4.2.0 | +| | RP-13 | RP-010537 | 112 | | | Corrections on un-supported features | 4.2.0 | +| 12/2001 | RP-14 | RP-010754 | 116 | | | Correction of control primitive parameter (CPHY-Out-of-Sync-Config) | 4.3.0 | +| | RP-14 | RP-010769 | 117 | | | UTRAN SFN-SFN observed time difference measurement | 4.3.0 | +| 03/2002 | RP-15 | RP-020231 | 121 | 1 | | Removal of channel coding option "no coding" for FDD | 4.4.0 | +| | RP-15 | RP-020079 | 119 | 1 | | UE GPS Code Phase Measurement | 4.4.0 | +| | RP-15 | RP-020090 | 118 | | | Introduction of AOA measurement for 1.28Mcps TDD | 5.0.0 | +| | RP-15 | RP-020094 | 122 | 2 | | Introduction of HSDPA | 5.0.0 | +| 06/2002 | RP-16 | RP-020322 | 127 | | | Correction to inconsistency between 25.302 and RRM Specifications (25.123/25.133) | 5.1.0 | +| | RP-16 | RP-020341 | 128 | | | HSDPA corrections | 5.1.0 | +| 09/2002 | RP-17 | RP-020665 | 131 | 1 | | Correction of transport to physical channel mapping for TDD | 5.2.0 | +| 12/2002 | RP-18 | RP-020715 | 134 | | | Two realisations of an Empty Transport Format | 5.3.0 | +| | RP-18 | RP-020732 | 135 | | | Corrections to the channel models for TDD | 5.3.0 | +| 03/2003 | RP-19 | RP-030112 | 136 | | | HCSN in TDD DL physical model | 5.4.0 | +| | RP-19 | RP-030112 | 137 | | | Correction on HSDPA physical channel combination | 5.4.0 | +| 06/2003 | RP-20 | RP-030299 | 138 | | | Measurements on HS-SICH for UTRA TDD | 5.5.0 | +| | RP-20 | RP-030278 | 139 | | | Power Measurement in non HSDPA codes for TDD | 5.5.0 | +| 09/2003 | RP-21 | RP-030480 | 142 | | | Correction to FDD downlink transport channel combinations for SCCPCH | 5.6.0 | +| | RP-21 | RP-030492 | 143 | | | Correcting model of the UE's physical layer regarding DCH with HS-DSCH | 5.6.0 | +| 12/2003 | RP-22 | RP-030622 | 144 | | | Correction to TDD HSDPA channel combinations | 5.7.0 | +| | RP-22 | - | - | | | Upgrade to Release 6 - no technical change | 6.0.0 | +| 03/2004 | RP-23 | RP-040088 | 145 | | | Interference measurement in UpPTS for 1.28Mcps TDD | 6.1.0 | +| 12/2004 | RP-26 | RP-040550 | 146 | 2 | | Introduction of Enhanced Uplink | 6.2.0 | +| 03/2005 | RP-27 | RP-050089 | 148 | | | Release 6 HS-DSCH operation without a DL DPCH for 3.84 Mcps TDD | 6.3.0 | +| | RP-27 | RP-050074 | 149 | | | Introduction of F-DPCH | 6.3.0 | +| | RP-27 | RP-050076 | 150 | 1 | | Introduction of MBMS | 6.3.0 | +| | RP-27 | RP-050050 | 151 | | | Introduction of 'DL Transmission Branch Load' measurement | 6.3.0 | +| 06/2005 | RP-28 | RP-050318 | 0152 | | | Correction to the description of RACH transport channel | 6.4.0 | +| | RP-28 | RP-050318 | 0153 | | | Add physical layer signalling information in the figures of UE's physical layer model for TDD mode | 6.4.0 | +| | RP-28 | RP-050322 | 0154 | | | Release 6 HS-DSCH operation without a DL DPCH for 3.84 Mcps TDD | 6.4.0 | +| | RP-28 | RP-050306 | 0156 | | | Feature Clean Up: Removal of observet time difference to GSM cell | 6.4.0 | +| | RP-28 | RP-050308 | 0158 | | | Feature Clean-up: Removal of DSCH (FDD) | 6.4.0 | +| | RP-28 | RP-050309 | 0160 | | | Feature Clean Up: Removal of CPCH | 6.4.0 | +| | RP-28 | RP-050311 | 0162 | | | Feature Clean Up: Removal of DRAC | 6.4.0 | +| | RP-28 | RP-050327 | 0163 | | | Correction of E-DCH Relative Grants | 6.4.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| | RP-28 | RP-050456 | 0165 | | | Feature Clean Up: Removal of CPCH | 6.5.0 | +| 03/2006 | RP-31 | RP-060090 | 0166 | | | Editorial correction on the Model of the UE's physical layer - downlink TDD mode | 6.6.0 | +| | RP-31 | RP-060098 | 0167 | | | 7.68 Mcps TDD Option (Release 7) | 7.0.0 | +| 06/2006 | RP-32 | RP-060351 | 0169 | | | Definition of Non-serving E-DCH RLS or Non-serving RLS | 7.1.0 | +| | RP-32 | RP-060351 | 0171 | | | Removal of FFS regarding E-DCH | 7.1.0 | +| 09/2006 | RP-33 | RP-060495 | 0173 | 2 | | Introduction of a Node B measurement for E-DCH RRM | 7.2.0 | +| | RP-33 | RP-060574 | 0175 | | | RGCH requirement in physical channel combinations | 7.2.0 | +| | RP-33 | RP-060586 | 0176 | | | Introduction of 3.84 and 7.68 Mcps TDD E-DCH | 7.2.0 | +| 03/2007 | RP-35 | RP-070157 | 0177 | | | Introduction of 1.28 Mcps TDD E-DCH | 7.3.0 | +| | RP-35 | RP-070165 | 0178 | | | Alignment of 25.302 with 25.321 and 25.331 to enable HS-DSCH operation without an associated DL DPCH for all TDD modes | 7.3.0 | +| 06/2007 | RP-36 | RP-070403 | 0179 | 1 | | Introduction of Enhanced CELL_FACH state in FDD | 7.4.0 | +| 09/2007 | RP-37 | RP-070628 | 0180 | 1 | | Adding GANSS related services within the list of services provided by the physical layer | 7.5.0 | +| 12/2007 | RP-38 | RP-070902 | 0181 | | | More improvement on Dedicated Carrier for 1.28Mcps TDD MBMS | 7.6.0 | +| | RP-38 | - | - | | | Upgrade to Release 8 - no technical change | 8.0.0 | +| 09/2008 | RP-41 | RP-080696 | 0183 | | | Introduction of Enhanced Uplink in CELL_FACH in 25.302 | 8.1.0 | +| 12/2008 | RP-42 | RP-081022 | 0184 | 1 | | Replacement of E-AICH in 25.302 | 8.2.0 | +| | RP-42 | RP-081025 | 0185 | - | | Introduction of enhanced CELL_FACH, CELL_PCH and URA_PCH for 1.28Mcps TDD | 8.2.0 | +| 06/2009 | RP-44 | RP-090519 | 0186 | - | | Support for 3.84 Mcps MBSFN IMB operation | 8.3.0 | +| 09/2009 | RP-45 | RP-090904 | 0188 | - | | Introduction of Rel-7 HSDPA MIMO for FDD | 8.4.0 | +| 12/2009 | RP-46 | RP-091308 | 0190 | - | | Updates to Rel-7 HSDPA MIMO for FDD | 8.5.0 | +| | RP-46 | RP-091325 | 0191 | 1 | | Introduction of DC-HSDPA for FDD | 8.5.0 | +| 12/2009 | RP-46 | RP-091336 | 0192 | - | | Introduction of DC-HSUPA, DC-HSDPA+MIMO, and Dual Band HSDPA for FDD | 9.0.0 | +| 03/2010 | RP-47 | RP-100290 | 0194 | - | | Corrections to FDD DL physical channel combinations | 9.1.0 | +| | RP-47 | RP-100303 | 0195 | - | | Clarification of FDD DL channel combination applicability for DC-HSUPA | 9.1.0 | +| 09/2010 | RP-49 | RP-100883 | 0201 | - | | Corrections to physical channel combinations for Enhanced CELL_FACH state for FDD | 9.2.0 | +| 09/2010 | RP-49 | - | - | | | v10.0.0 created based on v9.2.0 | 10.0.0 | +| | RP-49 | RP-100863 | 0202 | - | | Introduction of 4C-HSDPA for FDD | 10.0.0 | +| 12/2010 | RP-50 | RP-101365 | 0203 | 2 | | Introduction of MC-HSUPA for 1.28Mcps TDD | 10.1.0 | +| | RP-50 | RP-101366 | 0204 | 2 | | Introduction of 4C-HSDPA definitions | 10.1.0 | +| 09/2011 | RP-53 | RP-111296 | 0205 | 1 | | Correction to the model of physical layer for 1.28Mcps TDD multi-carrier HSDPA | 10.2.0 | +| 12/2011 | RP-54 | RP-111736 | 0207 | 3 | | Introduction of uplink CLTD and 8C-HSDPA into 25.302 | 11.0.0 | +| 09/2012 | RP-57 | RP-121369 | 0211 | 1 | | Introduction of Multiflow in TS 25.302 | 11.1.0 | +| | RP-57 | RP-121366 | 0212 | - | | Correction on F-TPICH transmission for UL CLTD | 11.1.0 | +| 12/2012 | RP-58 | RP-121942 | 0215 | - | | Introduction of 4Tx-HSDPA in 25.302 | 11.2.0 | +| | RP-58 | RP-121945 | 0216 | 1 | | Introduction of UL MIMO with 64QAM in TS 25.302 | 11.2.0 | +| | RP-58 | RP-121943 | 0217 | - | | Introduction of Multiflow and CLTD | 11.2.0 | +| 03/2013 | RP-59 | RP-130239 | 0218 | - | | Introduction of FE-FACH subfeature concurrent deployment of 2ms and 10ms TTI in a cell | 11.3.0 | +| 06/2013 | RP-60 | RP-130806 | 0220 | 1 | | Combination of Multiflow and UL MIMO | 11.4.0 | +| 06/2014 | RP-64 | RP-140874 | 0222 | 1 | | Correction of physical channel combinations with Multiflow operation | 11.5.0 | +| | RP-64 | RP-140874 | 0223 | 1 | | 25.302 CR Clarification on secondary ASET during MF-HSDPA and DC-HSUPA operation | 11.5.0 | +| 09/2014 | RP-65 | RP-141501 | 0232 | - | | The introduction of E-DCH decoupling operation | 12.0.0 | +| | RP-65 | RP-141502 | 0235 | 2 | | Introduction of a second broadcast channel | 12.0.0 | +| | RP-65 | RP-141501 | 0233 | - | | Introduction of Radio link without F-DPCH | 12.0.0 | +| | RP-65 | RP-141501 | 0234 | - | | CR to 25.302 on the introduction of DPCH2 | 12.0.0 | +| 12/2014 | RP-66 | RP-142111 | 0236 | - | | Clarification to physical channel combinations regarding MIMO operation | 12.1.0 | +| 09/2015 | RP-69 | RP-151444 | 0237 | 2 | | Introduction of the Multiflow 3F-4C configuration | 13.0.0 | +| 12/2015 | RP-70 | RP-152047 | 0241 | 1 | | Clarification for physical channel combination of DC-HSUPA and MC-HSDPA | 13.1.0 | +| | RP-70 | RP-152065 | 0242 | 1 | | Introduction of Dual Carrier HSUPA enhancements for UTRAN CS in TS 25.302 | 13.1.0 | +| 03/2016 | RP-71 | RP-160470 | 0243 | - | | Editorial cleanups in the table header with multi-carrier physical channel combinations | 13.2.0 | +| 03/2017 | RP-75 | RP-170651 | 0244 | 1 | F | Addition of physical channel combinations for FDD-Uplink | 13.3.0 | +| 03/2017 | RP-75 | | | | | Upgraded to Rel-14, no technical change | 14.0.0 | +| 06/2018 | RP-80 | | | | | Upgraded to Rel-15, no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25303/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/25_series/25303/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b457999d8247714381733e7f677f00b93bb62c73 --- /dev/null +++ b/marked/Rel-16/25_series/25303/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f229ec9719d6cd2590269081b85389cbb225bdcb8cbed54bc6a7b865759603 +size 61351 diff --git a/marked/Rel-16/25_series/25303/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-16/25_series/25303/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c8c9b3237ea3c7268923420a2baf6a0c10bb6a --- /dev/null +++ b/marked/Rel-16/25_series/25303/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d269d38e844b7951887b8bb9e3c5e108e0640f7ab5e18f58d7dae5bf2034a325 +size 80164 diff --git a/marked/Rel-16/25_series/25303/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/25_series/25303/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0c0a6dc4f1bd3b386ec9dfa49c230a33d9d5d91 --- /dev/null +++ b/marked/Rel-16/25_series/25303/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:488e30fdd4e515eb584590c1297abe3db6a7417df8aa582fe4a48657826561e0 +size 80260 diff --git a/marked/Rel-16/25_series/25303/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/25_series/25303/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5856d28cb78f9cfbac01acde9fe3c766ca02796 --- /dev/null +++ b/marked/Rel-16/25_series/25303/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b4a96d3f309a86d131f48f46a8e911bb59736f2fdbb146ce05e5c03533590af +size 118521 diff --git a/marked/Rel-16/25_series/25303/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/marked/Rel-16/25_series/25303/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..742e5a51b921be4ba3a12fab39ad33e09b1c59a7 --- /dev/null +++ b/marked/Rel-16/25_series/25303/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43c1c4fa2917590b9489ba09f7ad83fd66dbe4ad82b1fa626a500be2612f220b +size 96602 diff --git a/marked/Rel-16/25_series/25303/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Rel-16/25_series/25303/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df40a2f14fcf9e73e11be8c462f8b248205bceed --- /dev/null +++ b/marked/Rel-16/25_series/25303/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ab460f03f542594e69c53ca73bfe708a5d4694f242bad05f1ef1ee43b4e654 +size 116358 diff --git a/marked/Rel-16/25_series/25303/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/25_series/25303/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b90152700842dcd5bcee13697721c8cc82171ffe --- /dev/null +++ b/marked/Rel-16/25_series/25303/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f3ecbeca131bee0632e3d71ac2493b8e8d965eafda11456dd587e2a79856291 +size 136803 diff --git a/marked/Rel-16/25_series/25303/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25303/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..976022ecd58d173ff9595f39fe3b7cc3d8f88efe --- /dev/null +++ b/marked/Rel-16/25_series/25303/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfcf27a7b72a41bb428e5174d563de57d5606b057fb99478c59c4b7afd4937d8 +size 133405 diff --git a/marked/Rel-16/25_series/25303/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/25_series/25303/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9302a0c9d680a7a3ff154d314698a0856fbc7a --- /dev/null +++ b/marked/Rel-16/25_series/25303/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40b6c826041ed566c01251673d2449c26aa865f93595a3dd9c715cff0733110c +size 32031 diff --git a/marked/Rel-16/25_series/25303/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-16/25_series/25303/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df58cc0972ba1d607868e98c675395d88716dfb7 --- /dev/null +++ b/marked/Rel-16/25_series/25303/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6867c7d4a18df093b23ee1fd8c67943dbaa6a7ba20a1de8a02da46335a5f8bfe +size 155926 diff --git a/marked/Rel-16/25_series/25303/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/25_series/25303/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc1c4506ff339c55920d4a9c878984b764da0ee --- /dev/null +++ b/marked/Rel-16/25_series/25303/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8edea9042107f3d39a66d91124da4c5a7022b4055a18cdaff8d4cdae9d50993 +size 151565 diff --git a/marked/Rel-16/25_series/25303/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/25_series/25303/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bb6c61373553633b742f259d9e98f0c58659a55 --- /dev/null +++ b/marked/Rel-16/25_series/25303/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff779d7c4f729672c78f826783705cceef8f5b565f927df3c3ece56e07c538ad +size 72142 diff --git a/marked/Rel-16/25_series/25303/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-16/25_series/25303/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26481f5eac203ac69aa12b11f46015bd474c788c --- /dev/null +++ b/marked/Rel-16/25_series/25303/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f169d669ada81ba3e5f7904b8a9659b41f084bcbcf1618b9525b6af85a342ee8 +size 81692 diff --git a/marked/Rel-16/25_series/25303/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/25_series/25303/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30424c11fa4c68d258a0354c47bd9e8107a6c8a5 --- /dev/null +++ b/marked/Rel-16/25_series/25303/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b6a396568c08fd19ab8c5db0c2e44ad59a8462302fa2c5fb9c1a0e4f86276e0 +size 147600 diff --git a/marked/Rel-16/25_series/25303/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/25_series/25303/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bef9ac04839930e380a06c5ea00432e7454b442e --- /dev/null +++ b/marked/Rel-16/25_series/25303/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deda93e2dc69cafe137f4a680bbf1ee2031a15040d42c457e0ffd03921ebfb77 +size 135552 diff --git a/marked/Rel-16/25_series/25303/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/Rel-16/25_series/25303/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40cfbb39541c7556381f9b2dc599464395ee39a8 --- /dev/null +++ b/marked/Rel-16/25_series/25303/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae82cce7702efbd64a47a8b665ff9a60f34723e2f1f42975066521ad915dad1a +size 80716 diff --git a/marked/Rel-16/25_series/25303/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/25_series/25303/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8466d9376a0ad2a076a71236f5c385c679097764 --- /dev/null +++ b/marked/Rel-16/25_series/25303/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d364b03064a30038da78a95cb5bf466e3c0a6fcc044932e31bf1c53ae3277bd0 +size 200053 diff --git a/marked/Rel-16/25_series/25303/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25303/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4efe7daf86cd746d16d04c4c935052caebb4c0 --- /dev/null +++ b/marked/Rel-16/25_series/25303/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f8dedcf1d20b032fa72c2ac1499e74f4f9a3cf5665bda26842c34c35b96ac4d +size 132332 diff --git a/marked/Rel-16/25_series/25303/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/25_series/25303/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f8f2d2b270bdee7ff257388fce3d8637e935dae --- /dev/null +++ b/marked/Rel-16/25_series/25303/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:673ef9003b1bde7c393ddcda697ef46bd7a711e984afc58c4dedc11501c3294d +size 48968 diff --git a/marked/Rel-16/25_series/25303/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/25_series/25303/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b575bbd4a9e7c802c517936bde7d67b17122849 --- /dev/null +++ b/marked/Rel-16/25_series/25303/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45233cbd6445e6326b2dd00e15c473cd05613983a5bfdf24e68fb14050882c86 +size 118881 diff --git a/marked/Rel-16/25_series/25303/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/25_series/25303/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f72ac01e648541e53b4b3d7cf19ee05778b21e17 --- /dev/null +++ b/marked/Rel-16/25_series/25303/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0246f25ea40ff9f738281243157796c5794f48d0e06ff0676771b859b31331ea +size 104821 diff --git a/marked/Rel-16/25_series/25303/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/25_series/25303/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..686a18b26d5f56db68a8a624c844e9fbeefe17f0 --- /dev/null +++ b/marked/Rel-16/25_series/25303/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7f784bab0ca874abd87771a1823bec82e986026fdb74490e59e0e80ef759a1 +size 130235 diff --git a/marked/Rel-16/25_series/25303/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/25_series/25303/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d2c150ccdcadb6a77b451ebebf48475757fb5f9 --- /dev/null +++ b/marked/Rel-16/25_series/25303/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:811516872427d0a17a5e0ac7c97042fef3376c4298351115aa82d391274b23ad +size 103939 diff --git a/marked/Rel-16/25_series/25303/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/25_series/25303/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fed9ad31ffb48eef55f2c26d4710306802d82b3 --- /dev/null +++ b/marked/Rel-16/25_series/25303/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d653e191b668b7e4ee07433b103125ffa2c5de3297fedc403c1ad260c72bc8db +size 157046 diff --git a/marked/Rel-16/25_series/25303/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/25_series/25303/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f9645ee135fcbf0b11213481ff0aa3fb1f94ecf --- /dev/null +++ b/marked/Rel-16/25_series/25303/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4de4e32ec031f983ced90b820f1ac497e9e6f8c28a314700bc1bd81e12fada3 +size 46989 diff --git a/marked/Rel-16/25_series/25303/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-16/25_series/25303/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc1ee80711e3fc391be2f2c19fd3c698ab115890 --- /dev/null +++ b/marked/Rel-16/25_series/25303/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:166e70d16a532c4922b1e391f72beb74557ee6278c46dad95aebbf6e3c43a216 +size 76917 diff --git a/marked/Rel-16/25_series/25303/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/25_series/25303/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86abaf253028ebce86f39bdefc3ab39304646ea2 --- /dev/null +++ b/marked/Rel-16/25_series/25303/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f621aa487ce9c180a41503f493cced983e8431cebe9664773f087113ad0ba745 +size 202784 diff --git a/marked/Rel-16/25_series/25303/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-16/25_series/25303/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3becdba1611315a387dd75bf162cf51268c81f9b --- /dev/null +++ b/marked/Rel-16/25_series/25303/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:676c95d1d1a057df4db38480e22ee633533c981a795544fc20d85923d2e58239 +size 94223 diff --git a/marked/Rel-16/25_series/25303/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25303/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e2a33f7da8a969469dc12ddb13df0c06435e750 --- /dev/null +++ b/marked/Rel-16/25_series/25303/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:557521ba396e2972da92b806d83bc87e693c4627c1f80091e99affc731df1246 +size 103047 diff --git a/marked/Rel-16/25_series/25303/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/25_series/25303/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baf85450e59501f19bd3a9b71229e25a8d549e6b --- /dev/null +++ b/marked/Rel-16/25_series/25303/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e1537ad644d1aa5fa33ace65dba3acaf0c5c3894ddeb31040f5c571c5f6fc1d +size 222006 diff --git a/marked/Rel-16/25_series/25303/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/25_series/25303/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e8588dd4cd2854656e7d95e39536cf5a60742bd --- /dev/null +++ b/marked/Rel-16/25_series/25303/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:401f438f1dad0b3cedfc6eddea1557a20c115ff7dcfdeda91e8e25a5aad217ba +size 206368 diff --git a/marked/Rel-16/25_series/25303/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/25_series/25303/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edee4c50ba9653f69a4349a1164c5a3d406d6cd2 --- /dev/null +++ b/marked/Rel-16/25_series/25303/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b19eafe061391bd4efb61e9410ebdc18a9d4be6a0f891148659fa2bcd9b230cc +size 31018 diff --git a/marked/Rel-16/25_series/25303/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/25_series/25303/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01798ab6835375f1b1c478b66254b4da56ade1f3 --- /dev/null +++ b/marked/Rel-16/25_series/25303/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:513fb8052b30a01a5f74415981438b1852eea436f83b64ec69307a33f2a7f573 +size 76098 diff --git a/marked/Rel-16/25_series/25303/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/25_series/25303/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f213703978c250e0c1b90795309dcdb1ec85a6e9 --- /dev/null +++ b/marked/Rel-16/25_series/25303/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef47b171e8d870b308c30fadda1099c59dca622502571def0e9a9c69333169ac +size 130973 diff --git a/marked/Rel-16/25_series/25303/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/25_series/25303/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8748bcdad9d19db219af23376b1296b23eec870 --- /dev/null +++ b/marked/Rel-16/25_series/25303/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9cf7f63b26501c9c98e0494f17800395818dd36d0dbc1ba7aae738772cf4a23 +size 126411 diff --git a/marked/Rel-16/25_series/25303/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/25_series/25303/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b87458f6b9e871575632f515d085d06f91d7ecd4 --- /dev/null +++ b/marked/Rel-16/25_series/25303/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7957bdaf46b07cf124dfc9f3c5a2ce83cc258254ced5b93bc0a8cff545a3c818 +size 163056 diff --git a/marked/Rel-16/25_series/25303/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/25_series/25303/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..268ccdc3603997f2ba8dff52f80307162c720feb --- /dev/null +++ b/marked/Rel-16/25_series/25303/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e79b62b4a25a881be67182ffbab2ab3f84cf2ba2ee32ee668f5b1a82f80e4ca6 +size 158219 diff --git a/marked/Rel-16/25_series/25303/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/25_series/25303/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d511417ad9223604ba83089f7f48086f2f4a0f3 --- /dev/null +++ b/marked/Rel-16/25_series/25303/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7db253f78d9a7c37efa05449e49d3694abda85cabc11369537f7982469de2f2b +size 136427 diff --git a/marked/Rel-16/25_series/25303/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/Rel-16/25_series/25303/dfafe39c233a62ec8ebd71e42992c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..223e0ef2d1079c36823ace5843b522d40632ecec --- /dev/null +++ b/marked/Rel-16/25_series/25303/dfafe39c233a62ec8ebd71e42992c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b92fd6969c22680d44d914075461910e3976efca156d4955d557a49be86ceee +size 103672 diff --git a/marked/Rel-16/25_series/25303/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/Rel-16/25_series/25303/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14968daf7392fa54aea7ca843c1b6c5ed7bdacaf --- /dev/null +++ b/marked/Rel-16/25_series/25303/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4efc7dfc07917f49c486d399771b5bffb50ed4cd535f5afc9d7d5d601247446 +size 137495 diff --git a/marked/Rel-16/25_series/25303/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-16/25_series/25303/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8943a73e59992e1b1c6a3b40c8f7d3272babf7ff --- /dev/null +++ b/marked/Rel-16/25_series/25303/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ec4c17521a3dd4838f90e626b0d8ad64178adedd54c96e575750702be95150d +size 94644 diff --git a/marked/Rel-16/25_series/25303/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/marked/Rel-16/25_series/25303/f796c4b6ef101faa39b887a86820c3d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bcf7d180810db4a5c96c300a6a401cd4bbb143b --- /dev/null +++ b/marked/Rel-16/25_series/25303/f796c4b6ef101faa39b887a86820c3d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d455df817bb5f1313655ffa8b6329704f1a40c00933bb33424161f244b53085e +size 50695 diff --git a/marked/Rel-16/25_series/25303/raw.md b/marked/Rel-16/25_series/25303/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0453afa454ba6f3fd72353900f6aab52b2bdb974 --- /dev/null +++ b/marked/Rel-16/25_series/25303/raw.md @@ -0,0 +1,2270 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General Description of Connected Mode..... | 7 | +| 5 Radio Bearer Control - Overview of Procedures ..... | 8 | +| 5.1 Configurable parameters ..... | 8 | +| 5.2 Typical configuration cases..... | 8 | +| 5.3 RRC Elementary Procedures..... | 9 | +| 5.3.1 Category 1: Radio Bearer Configuration..... | 9 | +| 5.3.2 Category 2: Transport Channel Configuration ..... | 9 | +| 5.3.3 Category 3: Physical Channel Configuration ..... | 10 | +| 5.3.4 Category 4: Transport Format Combination Restriction..... | 10 | +| 5.3.5 Category 5: Uplink Dedicated Channel Control in CRNC ..... | 10 | +| 6 Examples of procedures..... | 10 | +| 6.1 RRC Connection Establishment and Release Procedures..... | 11 | +| 6.1.1 RRC connection establishment..... | 11 | +| 6.1.2 UE Initiated Signalling Connection Establishment ..... | 13 | +| 6.1.3 Normal RRC Connection Release ..... | 13 | +| 6.1.3.1 RRC Connection Release from Dedicated Physical Channel..... | 14 | +| 6.1.3.2 RRC Connection Release without Dedicated Physical Channel ..... | 15 | +| 6.2 Radio Bearer Control Procedures..... | 17 | +| 6.2.1 Radio Bearer Configuration ..... | 17 | +| 6.2.1.1 Radio Bearer Establishment..... | 17 | +| 6.2.1.1.1 Radio Bearer Establishment with Dedicated Physical Channel Activation..... | 17 | +| 6.2.1.1.2 Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification ..... | 19 | +| 6.2.1.1.3 Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification ..... | 20 | +| 6.2.1.1.4 Radio Bearer Establishment without Dedicated Physical Channel..... | 22 | +| 6.2.1.1.5 Void..... | 23 | +| 6.2.1.2 Radio Bearer Release..... | 23 | +| 6.2.1.2.1 Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification ..... | 23 | +| 6.2.1.3 Radio Bearer Reconfiguration ..... | 25 | +| 6.2.1.3.1 Unsynchronised Radio Bearer Reconfiguration..... | 25 | +| 6.2.2 Transport Channel Reconfiguration ..... | 27 | +| 6.2.2.1 Unsynchronised Transport Format Set Reconfiguration ..... | 27 | +| 6.2.3 Physical Channel Reconfiguration ..... | 29 | +| 6.2.3.1 UE-Originated DCH Activation ..... | 29 | +| 6.2.3.2 UE-terminated synchronised DCH Modify ..... | 31 | +| 6.2.3.3 UE-terminated DCH Release..... | 32 | +| 6.2.4 Transport Format Combination Control..... | 34 | +| 6.2.4.1 Transport Format Combination Limitation..... | 34 | +| 6.2.5 Dynamic Resource Allocation Control of Uplink DCHs ..... | 35 | +| 6.2.6 Variable Rate Transmission of Uplink DCHs ..... | 37 | +| 6.3 Data transmission..... | 39 | +| 6.3.1 Void ..... | 39 | +| 6.3.2 Void ..... | 39 | +| 6.3.3 Void ..... | 39 | +| 6.3.4 Data transfer on USCH (TDD only)..... | 39 | +| 6.3.5 Data transfer on DSCH (TDD only)..... | 40 | +| 6.4 RRC Connection mobility procedures ..... | 41 | +| 6.4.1 Handover Measurement Reporting..... | 41 | +| 6.4.2 Cell Update ..... | 42 | +| 6.4.3 URA Update ..... | 44 | + +| | | | +|------------------------|----------------------------------------------------------------------------|----| +| 6.4.4 | Radio Link Addition (FDD) ..... | 47 | +| 6.4.5 | Radio Link Removal (FDD)..... | 48 | +| 6.4.6 | Combined radio link addition and removal ..... | 49 | +| 6.4.7 | Hard Handover (FDD and TDD)..... | 50 | +| 6.4.8 | SRNS Relocation..... | 51 | +| 6.4.8.1 | Combined Cell/URA Update and SRNS relocation (lossless radio bearers)..... | 51 | +| 6.4.8.2 | Combined Hard Handover and SRNS relocation (lossless radio bearers)..... | 54 | +| 6.4.8.3 | Combined Cell/URA Update and SRNS relocation (seamless radio bearers)..... | 56 | +| 6.4.8.4 | Combined Hard Handover and SRNS relocation (seamless radio bearers)..... | 58 | +| 6.4.9 | RRC Connection re-establishment ..... | 60 | +| 6.4.10 | Inter-system Handover: GSM/BSS to UTRAN ..... | 61 | +| 6.4.11 | Inter-RAT Handover: UTRAN to GSM/BSS, CS domain services..... | 63 | +| 6.5 | CN originated paging request in connected mode ..... | 65 | +| 6.5.1 | UTRAN coordinated paging using DCCH..... | 65 | +| 6.6 | UTRAN originated paging request and paging response..... | 67 | +| 6.7 | Other procedures ..... | 68 | +| 6.7.1 | UE Capability Information ..... | 68 | +| 6.7.2 | Random access transmission sequence (FDD)..... | 69 | +| 6.7.3 | Random access transmission sequence (TDD)..... | 70 | +| 6.7.3.1 | Random access transmission sequence (3.84 Mcps TDD)..... | 70 | +| 6.7.3.2 | Random access transmission sequence (1.28 Mcps TDD)..... | 71 | +| 6.7.4 | Void ..... | 72 | +| 7 | Traffic volume monitoring..... | 73 | +| Annex A (informative): | Change history..... | 74 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes all procedures that assign, reconfigure and release radio resources. Included are e.g. procedures for transitions between different states and substates, handovers and measurement reports. The emphasis is on showing the combined usage of both peer-to-peer messages and interlayer primitives to illustrate the functional split between the layers, as well as the combination of elementary procedures for selected examples. The peer-to-peer elementary procedure descriptions and interlayer dependencies are described in the related protocol descriptions /1, 2, 3/ and they are thus not within the scope of the present document. + +The interlayer procedures and interlayer dependencies in the present document are informative. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". +- [2] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". +- [3] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [4] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [5] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [6] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [7] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification". +- [8] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in [8] apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------| +| ASC | Access Service Class | +| DC-SAP | Dedicated Control SAP | +| DCH | Dedicated transport CHannels | +| RNTI | Radio Network Temporary Identity | + +# --- 4 General Description of Connected Mode + +The connected mode is entered when the RRC connection is established. The UE is assigned a Radio Network Temporary Identity (RNTI) to be used as UE identity on common transport channels. Two types of RNTI exist. The Serving RNC allocates an s-RNTI for all UEs having an RRC connection. The combination of s-RNTI and an RNC-ID is unique within a PLMN. c-RNTI is allocated by each Controlling RNC through which UE is able to communicate on DCCH. c-RNTI is always allocated by UTRAN when a new UE context is created to an RNC, but the UE needs its c-RNTI only for communicating on common transport channels. + +The UE leaves the connected mode and returns to idle mode when the RRC connection is released or at RRC connection failure. + +Within connected mode the level of UE connection to UTRAN is determined by the quality of service requirements of the active radio bearers and the characteristics of the traffic on those bearers. + +The UE-UTRAN interface is designed to support a large number of UEs using packet data services by providing flexible means to utilize statistical multiplexing. Due to limitations, such as air interface capacity, UE power consumption and network h/w availability, the dedicated resources cannot be allocated to all of the packet service users at all times. + +Variable rate transmission provides the means that for services of variable rate the data rate is adapted according to the maximum allowable output power. + +The UE state in the connected mode defines the level of activity associated to the UE. The key parameters of each state are the required activity and resources within the state and the required signalling prior to the data transmission. The state of the UE shall at least be dependent on the application requirement and the period of inactivity. + +The different levels of UE connection to UTRAN are listed below: + +- No signalling connection exists +The UE is in idle mode and has no relation to UTRAN, only to CN. For data transfer, a signalling connection has to be established. +- Signalling connection exists +When at least one signalling connection exists, the UE is in connected mode and there is normally an RRC connection between UE and UTRAN. The UE position can be known on different levels: + - UTRAN Registration Area (URA) level +The UE position is known on URA level. The URA is a set of cells + - Cell level +The UE position is known on cell level. Different transport channel types can be used for data transfer: + - Common transport channels (RACH / FACH, DSCH) + - Dedicated transport CHannels (DCH) + +Assuming that there exists an RRC connection, there are two basic families of RRC connection mobility procedures, URA updating and handover. Different families of RRC connection mobility procedures are used in different levels of UE connection (cell level and URA level): + +- URA updating is a family of procedures that updates the UTRAN registration area of a UE when an RRC connection exists and the position of the UE is known on URA level in the UTRAN; +- handover is a family of procedures that adds or removes one or several radio links between one UE and UTRAN when an RRC connection exists and the position of the UE is known on cell level in the UTRAN. + +# --- 5 Radio Bearer Control - Overview of Procedures + +## 5.1 Configurable parameters + +The following layer 1, MAC and RLC parameters should be configurable by RRC. The list is not complete. + +- Radio bearer parameters, e.g.: + - RLC parameters per RLC link (radio bearer), which may include e.g. PDU size and timeout values. Used by RLC. + - Multiplexing priority per DCCH/DTCH. Used by MAC in case of MAC multiplexing of logical channels. +- Transport channel parameters, e.g.: + - Scheduling priority per transport channel. Used by MAC in case of layer 1 multiplexing of transport channels. + - Transport format set (TFS) per transport channel. Used by MAC and L1. + - Transport format combination set (TFCS) per UE. Used by MAC and L1. + - Allowed subset of TFCS per UE. Used by MAC. +- Physical channel parameters, which may include e.g. carrier frequency and codes. Used by L1. + +## 5.2 Typical configuration cases + +Table 1 gives a proposal which main combination cases of parameter configuration that shall be supported, in terms of which parameters that shall be able to configure simultaneously (by one procedure). Note that the "Transport channel type switching" is not a parameter as such, it only indicates that switching of transport channel type may take place for that combination case. + +**Table 1: Typical configuration cases.** +**An "X" indicates that the parameter can (but need not) be configured** + +| Parameter | | Layer | A | B | C | D | E | F | +|------------------------------|---------------------------------------|--------|---|---|---|---|---|---| +| Radio bearer parameters | RLC parameters | RLC | X | | | | | | +| | Logical channel multiplexing priority | MAC | X | | | | | | +| Transport channel parameters | Transport channel scheduling priority | MAC | X | | | | | | +| | TFS | L1+MAC | X | X | | | | | +| | TFCS | L1+MAC | X | X | | | | | +| | Subset of TFCS | MAC | | | | | X | X | +| | Transport channel type switching | MAC | X | X | X | | | | +| Physical channel parameters | | L1 | X | X | X | X | | | + +Case A is typically when a radio bearer is established or released, or when the QoS of an existing radio bearer need to be changed. + +Case B is when the traffic volume of a radio bearer has changed so the TFS used on the DCH need to be changed, which may in turn affect any assigned set of physical channels. Another example is to make the UE use a new transport channel and at the same time supplying the TFS for that channel. + +Case C is when the traffic volume of one radio bearer has changed so that the used transport channel type is changed, e.g. from CELL\_FACH to CELL\_DCH. This case includes the assignment or release of a set of physical channels. + +Case D is e.g. the change of used DL channelisation code, when a DCH is currently used. No transport channel type switching takes place. + +Case E is a temporary restriction and/or a release of restriction for usage of the TFCS by the UE (total uplink rate). + +Case F is used to dynamically control the allocation of resources on uplink DCHs in the CRNC, using broadcast information such as transmission probability and maximum bit rate. + +## 5.3 RRC Elementary Procedures + +### 5.3.1 Category 1: Radio Bearer Configuration + +The first category of procedures includes Case A and are characterized by: + +- are executed upon request by higher layers and the parameter configuration is based on QoS; +- affects L1, MAC and RLC. + +There are three RRC procedures included in this category: + +- **Radio Bearer Establishment:** this procedure establishes a new radio bearer. The establishment includes, based on QoS, assignment of RLC parameters, multiplexing priority for the DTCH, scheduling priority for DCH, TFS for DCH and update of TFCS. It may also include assignment of a physical channel(s) and change of the used transport channel types / RRC state. +- **Radio Bearer Release:** this procedure releases a radio bearer. The RLC entity for the radio bearer is released. The procedure may also release a DCH, which affects the TFCS. It may include release of physical channel(s) and change of the used transport channel types / RRC state. +- **Radio Bearer Reconfiguration:** this procedure reconfigures parameters for a radio bearer (e.g. the signalling link) to reflect a change in QoS. It may include change of RLC parameters, change of multiplexing priority for DTCH/DCCH, change of DCH scheduling priority, change of TFS for DCH, change of TFCS, assignment or release of physical channel(s) and change of used transport channel types. + +### 5.3.2 Category 2: Transport Channel Configuration + +The second category of procedures includes Case B and are characterized by: + +- configuration of TFS for a transport channel and reconfiguration of TFCS is done, but sometimes also physical channel parameters; +- affects L1 and MAC; +- switching of used transport channel(s) may take place. + +There is one RRC procedure included in this category: + +- **Transport Channel Reconfiguration:** this procedure reconfigures parameters related to a transport channel such as the TFS. The procedure also assigns a TFCS and may change physical channel parameters to reflect a reconfiguration of a transport channel in use. + +NOTE: It is expected that the configuration of TFS/TFCS needs to be done more seldom than the assignment of physical channel. A "pre-configuration" of TFS/TFCS of a transport channel not in use can be done by this procedure, to be used after transport channel type switching when the physical channel is assigned. + +### 5.3.3 Category 3: Physical Channel Configuration + +The third category of procedures includes the cases C and D and are characterized by: + +- may assign or release a physical channel for the UE (which may result in transport channel type switching); +- may make a combined release and assignment (replacement) of a physical channel in use (which does not result in transport channel type switching / change of RRC state); +- affects mainly L1, and only the transport channel type switching part of MAC; +- the transport format sets (TFS and TFCS) are not assigned by this type of procedure. However, the UE can be directed to a transport channel, which TFS is already assigned to the UE. + +There is one RRC procedure included in this category: + +- **Physical Channel Reconfiguration:** this procedure may assign, replace or release a set of physical channels used by an UE. As a result of this, it may also change the used transport channel type (RRC state). For example, + +when the first physical channel is assigned the UE enters the DCH/DCH state. When the last physical channel is released the UE leaves the CELL\_DCH state and enters a state (and transport channel type) indicated by the network. A special case of using this procedure is to change the DL channelisation code of a dedicated physical channel. + +NOTE: The procedure does not change the active set, in the downlink the same number of physical channels are added or replaced for each radio link. + +### 5.3.4 Category 4: Transport Format Combination Restriction + +The fourth category of procedures includes Case E and are characterized by: + +- does only control MAC by means of the transport format combinations that may be used within the set without affecting L1. + +There is one RRC procedure included in this category: + +- **Transport format combination control:** the network uses this procedure towards an UE, to control the used transport format combinations in the uplink within the transport format combination set. + +### 5.3.5 Category 5: Uplink Dedicated Channel Control in CRNC + +The fifth category of procedures includes Case F and are characterized by: + +- does control UE MAC by means of broadcasting transmission probability and maximum total bit rate that shall be used for uplink DCHs, which are under control by this procedure. + +There is one RRC procedure included in this category: + +- **Dynamic Resource Allocation Control of Uplink DCHs:** the network uses this procedure towards all UEs, to control the probability of transmission and the maximum total bit rate used by uplink DCHs, which are under control by this procedure. + +# --- 6 Examples of procedures + +These sequences are examples and do not provide a comprehensive set of all different scenarios. + +In cases where the logical and / or transport channel for a given message is known, it can be shown in front of the message name (*Logical\_Ch: Transport\_Ch: Message*). For example: DCCH:RACH:Acknowledged Data indicates a data message on DCCH mapped onto RACH. Either logical or transport channel can be omitted, if it is unspecified for the message. + +## 6.1 RRC Connection Establishment and Release Procedures + +### 6.1.1 RRC connection establishment + +RRC connection establishment (see [5]) is shown in figure 1 (protocol termination for common channels is shown according to former case A, case C can be found for comparison in annex A). The RRC layer in the UE leaves the idle mode and initiates an RRC connection establishment by sending an RRC Connection Request message using transparent mode on CCCH logical channel, and it is transmitted by MAC on the RACH transport channel. + +On the network side, upon the reception of RRC Connection Request, the RRC layer performs admission control, assigns an s-RNTI for the RRC connection and selects radio resource parameters (such as transport channel type, transport format sets etc). If a DCH is to be established, CPHY-RL-Setup and CPHY-TrCH-Config request primitives (transmitted as one RADIO LINK SETUP PDU) are sent to all Node Bs that would be involved in the channel establishment. The physical layer operation is started and confirmation primitives are returned from each Node B. RRC configures parameters on layer 2 to establish the DCCH logical channel locally. The selected parameters including the RNTI, are transmitted to the UE in an RRC Connection Setup message using unacknowledged mode on the CCCH logical channel. + +Upon reception of the RRC Connection Setup message, the RRC layer in the UE configures the L1 and L2 using these parameters to locally establish the DCCH logical channel. In case of DCH, layer 1 indicates to RRC when it has reached synchronisation. + +The RLC signalling link is locally established on both sides. The establishment can be mapped on either RACH / FACH or DCH by MAC. When the UE has established the RLC signalling link, it transmits an RRC Connection Setup Complete message to the network using acknowledged mode on the DCCH. + +![Sequence diagram of RRC connection establishment (with common channel termination case A).](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates the RRC connection establishment process between a User Equipment (UE) and a Radio Network Controller (RNC). The sequence of messages is as follows: + +- UE-RRC** sends **RLC-TR-Data-REQ [RRR Connection Request]** to **UE-RLC**. +- UE-RLC** sends **MAC-Data-REQ** to **UE-MAC**. +- UE-MAC** sends **RACH: CCCH Data [RRR Connection Request]** to **Node B-L1**. +- Node B-L1** sends **MAC-Data-IND [RRR Connection Request]** to **SRNC-MAC**. +- SRNC-MAC** sends **RLC-TR-Data-IND** to **SRNC-RLC**. +- SRNC-RLC** triggers **Admission control & radio resource allocation**. +- SRNC-RLC** sends **CPHY-RL-Setup-REQ (only if DCH)** to **Node B-L1**. +- SRNC-RLC** sends **CPHY-TrCH-Config-REQ (only if DCH)** to **Node B-L1**. +- Node B-L1** triggers **Start tx/rx**. +- Node B-L1** sends **CPHY-RL-Setup-CNF (only if DCH)** to **SRNC-RLC**. +- Node B-L1** sends **CPHY-TrCH-Config-CNF (only if DCH)** to **SRNC-RLC**. +- SRNC-RLC** sends **CPHY-RL-Setup-REQ (only if DCH)** to **RNC-L1**. +- SRNC-RLC** sends **CPHY-TrCH-Config-REQ (only if DCH)** to **RNC-L1**. +- SRNC-RLC** sends **CMA-C-S/H-Config-REQ** to **CRNC-MAC**. +- SRNC-RLC** sends **CMA-C-D-Config-REQ** to **SRNC-MAC**. +- SRNC-RLC** sends **CRLC-Config-REQ** to **SRNC-MAC**. +- SRNC-MAC** triggers **L2 link establishment**. +- SRNC-RLC** sends **RLC-UM-Data-REQ [RRR Connection Setup]** to **SRNC-MAC**. +- SRNC-MAC** sends **FACH: CCCH Data [RRR Connection Setup]** to **Node B-L1**. +- Node B-L1** sends **MAC-Data-IND** to **UE-MAC**. +- UE-MAC** sends **MAC-Data-IND [RRR Connection Setup]** to **UE-RLC**. +- UE-RLC** sends **RLC-UM-Data-IND [RRR Connection Setup]** to **UE-RRC**. +- UE-RRC** sends **CPHY-RL-Setup-REQ (only if DCH)** to **UE-L1**. +- UE-RRC** sends **CPHY-TrCH-Config-REQ (only if DCH)** to **UE-L1**. +- UE-RRC** sends **CMA-C-S/H-D-Config-REQ** to **UE-MAC**. +- UE-MAC** triggers **Start tx/rx**. +- UE-MAC** triggers **L1 synchronisation (DCH)**. +- UE-L1** sends **CPHY-Sync-IND (only if DCH)** to **UE-RRC**. +- Node B-L1** sends **CPHY-Sync-IND (only if DCH)** to **SRNC-RLC**. +- UE-RRC** sends **CRLC-Config-REQ** to **UE-RLC**. +- UE-RLC** triggers **L2 link establishment**. +- UE-RLC** sends **RLC-Data-REQ [RRR Connection Setup Complete]** to **UE-RRC**. +- UE-RRC** sends **DCCH Acknowledged Data [RRR Connection Setup Complete]** to **Node B-L1**. +- Node B-L1** sends **DCCH Data ack** to **SRNC-RLC**. +- SRNC-RLC** sends **RLC-Data-IND [RRR Connection Setup Complete]** to **SRNC-RRC**. +- SRNC-RRC** sends **RLC-Data-CNF** to **UE-RLC**. + +Sequence diagram of RRC connection establishment (with common channel termination case A). + +Figure 1: RRC connection establishment (with common channel termination case A) + +### 6.1.2 UE Initiated Signalling Connection Establishment + +NOTE 1: In case additional UE capability information is needed at RRC Connection Establishment, it is transmitted in the RRC Connection Setup Complete message. + +The sequence in figure 2 shows the establishment of the first Signalling Connection for the UE, initiated by the UE. + +RRC Signalling Connection Establishment is requested by the non access stratum in the UE with a primitive over the Dedicated Control (DC) SAP. The primitive contains an initial message to be transferred transparently by RRC to the non-access stratum entity on the network side. + +NOTE 2: The initial NAS message could for a GSM based Core Network be e.g. CM Service Request, Location Update Request etc. + +If no RRC connection exists, the RRC layer makes an RRC connection establishment, which includes the transmission of UE capability information. When the RRC connection establishment is completed, the signalling connection establishment can be resumed. + +The initial message from NAS is transferred in the RRC message "Initial Direct Transfer" using acknowledged mode on the DCCH, to the network, where it is passed on with an RRC Signalling Connection Establish IND primitive over the DC-SAP. + +When the UE-RRC has requested UE-RLC to transmit the INITIAL DIRECT TRANSFER message, the Signalling Connection Establishment is confirmed by the UE-RRC. + +![Sequence diagram of UE initiated Signalling Connection Establishment. The diagram shows the interaction between UE-RRC, UE-RLC, SRNC-RLC, and SRNC-RRC across Uu and Iub interfaces. The process starts with RRC Signalling Connection Establishment Requested at UE-RRC, followed by RRC Connection Establishment. Then, INITIAL DIRECT TRANSFER is sent from UE-RRC to SRNC-RLC via UE-RLC (RLC-Data-REQ). SRNC-RLC receives it (RLC-Data-IND) and passes it to SRNC-RRC. SRNC-RRC indicates RRC Signalling Connection Establishment. UE-RRC confirms RRC Signalling Connection Establishment. Finally, DCCH: Data ack is sent from SRNC-RLC to UE-RLC.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant SRNC-RLC + participant SRNC-RRC + + Note left of UE-RRC: RRC Signalling Connection Establishment Requested + UE-RRC->>UE-RLC: RLC-Data-REQ INITIAL DIRECT TRANSFER + Note right of UE-RRC: Confirm RRC Signalling Connection Establishment + UE-RLC->>SRNC-RLC: DCCH: Acknowledged Data INITIAL DIRECT TRANSFER + SRNC-RLC->>SRNC-RRC: RLC-Data-IND INITIAL DIRECT TRANSFER + Note right of SRNC-RRC: Indicate RRC Signalling Connection Establishment + SRNC-RLC->>UE-RLC: DCCH: Data ack + +``` + +Sequence diagram of UE initiated Signalling Connection Establishment. The diagram shows the interaction between UE-RRC, UE-RLC, SRNC-RLC, and SRNC-RRC across Uu and Iub interfaces. The process starts with RRC Signalling Connection Establishment Requested at UE-RRC, followed by RRC Connection Establishment. Then, INITIAL DIRECT TRANSFER is sent from UE-RRC to SRNC-RLC via UE-RLC (RLC-Data-REQ). SRNC-RLC receives it (RLC-Data-IND) and passes it to SRNC-RRC. SRNC-RRC indicates RRC Signalling Connection Establishment. UE-RRC confirms RRC Signalling Connection Establishment. Finally, DCCH: Data ack is sent from SRNC-RLC to UE-RLC. + +Figure 2: UE initiated Signalling Connection Establishment + +### 6.1.3 Normal RRC Connection Release + +A normal RRC Connection Release procedure is initiated on the network side by an RRC Signalling Connection Release request for the last Signalling Connection of a UE. The procedure is slightly different depending on whether the UE has dedicated physical channel(s) allocated. + +#### 6.1.3.1 RRC Connection Release from Dedicated Physical Channel + +![Sequence diagram for RRC Connection Release from Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves RRC signalling release request, DCCH messages, and subsequent MAC and PHY layer releases.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +sequenceDiagram + participant SRNC-RRC + participant SRNC-RLC + participant SRNC-MAC + participant CRNC-MAC + participant RNC-L1 + participant Node B-L1 + participant UE-L1 + participant UE-MAC + participant UE-RLC + participant UE-RRC + + Note right of SRNC-RRC: RRC Signalling Connection Release Requested + SRNC-RRC->>SRNC-RLC: Last Signalling Connection & DCH released + Note right of SRNC-RLC: DCCH: DCH: RRC CONNECTION RELEASE (unacknowledged) + SRNC-RLC->>UE-L1: DCCH: DCH: RRC CONNECTION RELEASE (unacknowledged) + UE-RRC->>UE-RLC: RRC Signalling Connection Release Indicated + UE-L1->>SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + Note right of SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + UE-L1->>SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + Note right of SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + UE-L1->>SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + Note right of SRNC-RRC: DCCH: DCH: RRC CONNECTION RELEASE COMPLETE (unacknowledged, Quick Repeat) + UE-RRC->>UE-RLC: CRLC-Config-REQ + UE-RLC->>UE-MAC: L2 link released + UE-MAC->>UE-L1: CMAC-C / SH / D-Config-REQ + SRNC-RLC->>SRNC-MAC: CRLC-Config-REQ + SRNC-MAC->>SRNC-RLC: L2 link released + SRNC-RLC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>CRNC-MAC: CMAC-C / SH -Config-REQ + CRNC-MAC->>UE-L1: CPHY-TrCH-Release-REQ + UE-L1->>UE-MAC: CPHY-RL-Release-REQ + Note right of UE-MAC: ----- + SRNC-RLC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>Node B-L1: CPHY-TrCH-Release-REQ + Node B-L1->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>Node B-L1: CPHY-Out-Of-Sync-IND + Node B-L1->>SRNC-RRC: CPHY-TrCH-Release-REQ + SRNC-RRC->>SRNC-RLC: CPHY-RL-Release-REQ + +``` + +Sequence diagram for RRC Connection Release from Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves RRC signalling release request, DCCH messages, and subsequent MAC and PHY layer releases. + +Figure 3: RRC Connection Release from Dedicated Physical Channel + +The RRC layer entity in the network issues an RRC CONNECTION RELEASE message using unacknowledged mode on the DCCH. Upon reception of this message the UE-RRC sends an RRC Signalling Connection Release Indication primitive to NAS. The UE replies with an RRC CONNECTION RELEASE COMPLETE message, which is sent in unacknowledged-mode on the dedicated channel. To improve the reliability of the message, quick repeat on RRC-level can be used. The UE will then proceed to release RLC(s), MAC and the radio link(s) after which the UE RRC enters Idle Mode. + +The primary method to detect the release of the signalling link in the NW is the RRC CONNECTION RELEASE COMPLETE-message from the UE. Should the message be lost despite the use of quick repeat, the release of the signalling link is detected by the out-of-sync primitive from either Node-B L1 or RNC-L1 to RNC RRC. After receiving this primitive, the RNC-RRC layer releases L2 and L1 resources on the network side and enters the idle mode. + +#### 6.1.3.2 RRC Connection Release without Dedicated Physical Channel + +The RRC layer entity in the network issues an RRC CONNECTION RELEASE message using unacknowledged or acknowledged mode on the DCCH. Upon reception of this message the UE-RRC sends an RRC Signalling Connection Release Indication primitive to NAS and an RRC CONNECTION RELEASE COMPLETE message to UTRAN using acknowledged mode on the DCCH. + +After receiving the RRC CONNECTION RELEASE COMPLETE message the network RRC layer releases L2 resources, sends an RRC Signalling Connection Release confirmation to DC-SAP and goes to Idle Mode (more precisely: only the RRC entity dedicated to this UE goes to Idle Mode). + +Error! No + +15 + +Error! No text of specified style in + +![Sequence diagram for RRC Connection Release without Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves RRC signalling, data transfer over FACH/RACH, and subsequent MAC/RLC configuration requests.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant SRNC-RRC + participant SRNC-RLC + participant SRNC-MAC + participant CRNC-MAC + participant RNC-L1 + participant Node B-L1 + participant UE-L1 + participant UE-MAC + participant UE-RLC + participant UE-RRC + + Note right of SRNC-RRC: RRC Signalling Connection Release Requested + SRNC-RRC->>SRNC-RLC: Last Signalling Connection & no DCH + Note right of SRNC-RLC: DCCH: FACH: RRC CONNECTION RELEASE (acknowledged) + SRNC-RLC->>UE-RLC: RLC-Data-REQ [RRC Connection Release Complete] + Note right of UE-RLC: DCCH: RACH: Acknowledged Data + UE-RLC->>SRNC-RLC: [RRC Connection Release Complete] + SRNC-RLC->>SRNC-MAC: RLC-Data-IND + Note right of SRNC-MAC: DCCH: FACH: Data ack + SRNC-MAC->>UE-RLC: RLC-Data-CNF + Note right of UE-RLC: RRC Signalling Connection Release Indicated + UE-RLC->>SRNC-RLC: CRLC-Config-REQ + SRNC-RLC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>CRNC-MAC: CMAC-C/SH-Config-REQ + CRNC-MAC->>UE-MAC: CRLC-Config-REQ + UE-MAC->>UE-L1: CMAC-C / SH / D-Config-REQ + Note right of SRNC-RRC: RRC Signalling Connection Release Confirmed + +``` + +Sequence diagram for RRC Connection Release without Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves RRC signalling, data transfer over FACH/RACH, and subsequent MAC/RLC configuration requests. + +Figure 4: RRC Connection Release without Dedicated Physical Channel + + + +## 6.2 Radio Bearer Control Procedures + +### 6.2.1 Radio Bearer Configuration + +#### 6.2.1.1 Radio Bearer Establishment + +The procedures for establishing radio bearers may vary according to the relation between the radio bearer and a dedicated transport channel. Depending on the QoS parameters, there may or may not be a permanently allocated dedicated channel associated with the RB. Circuit-switched bearers, or bearers classified as real-time services typically need a permanent association to a DCH to meet the delay requirements. Packet-switched bearers, or bearers classified as non-real-time services can in many cases be served as best-effort, requesting capacity from an associated DCH based on need. + +When establishing an RB together with a DCH, the DCH may be attached to either a newly activated physical channel or it may be accommodated by modifying an existing physical channel. The modification is further broken down into two different options: synchronised and unsynchronised. If the old and new physical channel settings are compatible (TFCI etc.) in the sense that executing the modification in the NW and the UE with arbitrary timing does not introduce transmission errors, the unsynchronised procedure can be applied. If the old and new settings are incompatible, due to e.g. assignment of the same TFCI value to a new set of physical layer configuration, the synchronised procedure must be used. + +##### 6.2.1.1.1 Radio Bearer Establishment with Dedicated Physical Channel Activation + +The procedure in figure 5 is applied when a new physical channel needs to be created for the radio bearer. A Radio Bearer Establishment is initiated when an RB Establish Request primitive is received from the DC-SAP on the network side of the RRC layer. This primitive contains a bearer reference and QoS parameters. Based on these QoS parameters, L1 and L2 parameters are chosen by the RRC entity on the network side. + +The physical layer processing on the network side is started with the CPHY-RL-Setup request primitive issued to all applicable Node Bs. If any of the intended recipients is / are unable to provide the service, it will be indicated in the confirmation primitive(s). After setting up L1 including the start of Tx / Rx in Node B, the NW-RRC sends a RADIO BEARER SETUP message to its peer entity (acknowledged or unacknowledged transmission optional for the NW). This message contains L1, MAC and RLC parameters. After receiving the message, the UE-RRC configures L1 and MAC. + +When L1 synchronisation is indicated, the UE sends a RADIO BEARER SETUP COMPLETE message in acknowledged-mode back to the network. The NW-RRC configures MAC and RLC on the network side. + +The UE-RRC creates a new RLC entity associated with the new radio bearer. The applicable method of RLC establishment may depend on RLC transfer mode. The RLC connection can be either implicitly established, or explicit signalling can be applied. + +Finally, an RB Establish Indication primitive is sent by UE-RRC and an RB Establish Confirmation primitive is issued by the RNC-RRC. + +![Sequence diagram for Radio Bearer Establishment with Dedicated Physical Channel Activation. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the RNC to establish a radio bearer.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note right of SRNC-RRC: Request for RB Establishment + SRNC-RRC->>SRNC-RLC: New DCH needed + SRNC-RLC->>Node B-L1: CPHY-RL-Setup-REQ + SRNC-RLC->>Node B-L1: CPHY-TrCH-Config-REQ + Node B-L1->>Node B-L1: Start tx/rx + Node B-L1->>SRNC-RLC: CPHY-RL-Setup-CNF + SRNC-RLC->>RNC-L1: CPHY-RL-Setup-REQ + SRNC-RLC->>RNC-L1: CPHY-TrCH-Config-REQ + RNC-L1->>UE-RRC: DCCH: RADIO BEARER SETUP (acknowledged or unacknowledged optional) + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + UE-L1->>UE-L1: Start tx/rx + UE-L1->>UE-RRC: CPHY-TrCH-Config-REQ + UE-RRC->>UE-MAC: CMAC-D / C / SH-Config-REQ + UE-MAC->>UE-L1: L1 Connection Establishment + UE-L1->>UE-RRC: CPHY-Sync-IND + Node B-L1->>SRNC-RRC: CPHY-Sync-IND + UE-RRC->>UE-RLC: RLC-Data-REQ + Note left of UE-RLC: [Radio Bearer Setup Complete] + RNC-L1->>SRNC-RLC: DCCH: Acknowledged Data + Note right of SRNC-RLC: [Radio Bearer Setup Complete] + SRNC-RLC->>SRNC-RRC: RLC-Data-IND + Note right of SRNC-RRC: [Radio Bearer Setup Complete] + UE-RRC->>UE-RLC: CRLC-Config-REQ + UE-RLC->>UE-MAC: DTCH: RLC Link Established + SRNC-RRC->>CRNC-MAC: CMAC-C / SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>SRNC-RLC: CRLC-Config-REQ + SRNC-RLC->>SRNC-MAC: DTCH: RLC Link Established + UE-RRC->>UE-RRC: RB Establish Indication + SRNC-RRC->>SRNC-RRC: RB Establish Confirmation + +``` + +Sequence diagram for Radio Bearer Establishment with Dedicated Physical Channel Activation. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the RNC to establish a radio bearer. + +Figure 5: Radio Bearer Establishment with Dedicated Physical Channel Activation + +##### 6.2.1.1.2 + +##### Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification + +![Sequence diagram for Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification. Lifelines include UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, and SRNC-RRC. The process involves RRC signaling, physical channel configuration, MAC and RLC setup, and final confirmation messages.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note right of SRNC-RRC: Request for RB Establishment + Note right of SRNC-RRC: Compatible DCH Modification required + SRNC-RRC->>Node B-L1: CPHY-RL-Modify-REQ + SRNC-RRC->>Node B-L1: CPHY-TrCH-Config-REQ + Node B-L1->>SRNC-RRC: CPHY-RL-Modify-CNF + SRNC-RRC->>RNC-L1: CPHY-RL-Modify-REQ + SRNC-RRC->>RNC-L1: CPHY-TrCH-Config-REQ + SRNC-RRC->>UE-RRC: DCCH: RADIO BEARER SETUP (acknowledged or unacknowledged optional) + UE-RRC->>UE-L1: CPHY-RL-Modify-REQ + UE-RRC->>UE-L1: CPHY-TrCH-Config-REQ + UE-RRC->>UE-MAC: CMAC-D / C / SH-Config-REQ + UE-RRC->>UE-RLC: RLC-Data-REQ [Radio Bearer Setup Complete] + UE-RLC->>SRNC-RLC: DCCH: Acknowledged Data [Radio Bearer Setup Complete] + SRNC-RLC->>UE-RLC: DCCH: Data ack + SRNC-RLC->>SRNC-RRC: RLC-Data-IND [Radio Bearer Setup Complete] + UE-RLC->>UE-RRC: RLC-Data-CNF + UE-RRC->>UE-RLC: CRLC-Config-REQ + SRNC-RRC->>CRNC-MAC: CMAC-C / SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>SRNC-RLC: CRLC-Config-REQ + Note left of UE-RLC: DTCH: RLC Link Established + Note right of SRNC-RLC: DTCH: RLC Link Established + Note left of UE-RRC: RB Establish Indication + Note right of SRNC-RRC: RB Establish Confirmation + +``` + +Sequence diagram for Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification. Lifelines include UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, and SRNC-RRC. The process involves RRC signaling, physical channel configuration, MAC and RLC setup, and final confirmation messages. + +**Figure 6: Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification** + +The establishment of a radio bearer, when unsynchronised physical channel modification is applicable, is shown in figure 6. If the old and new physical layer configurations are compatible in the sense that they can coexist in the peer entities, an unsynchronised procedure for radio bearer establishment can be applied. In this case no fixed activation time is required. + +The modifications on the physical layer in the network are done in response to a CPHY\_modify request. Failure to comply is indicated in the confirmation primitive. In an error-free case the RADIO BEARER SETUP message on L3 is transmitted. Acknowledged or unacknowledged transmission is a network option. Configuration changes on the UE-side proceed after this message has been received. Reception of the RADIO BEARER SETUP COMPLETE message triggers configuration changes in MAC and RLC in the network. + +##### 6.2.1.1.3 Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification + +In this case the CPHY-RL-Modify request doesn't immediately cause any changes in the physical layer configuration, it only checks the availability of the requested configuration and makes a "reservation". After the confirmations have been received from all applicable Node Bs, the RRC chooses the appropriate "activation time" when the new configuration can be activated. This information is signalled to MAC, RLC and also the physical layer (CPHY\_Commit request primitive). + +After the RADIO BEARER SETUP message (acknowledged transmission on L2 required) between peer L3 entities the setup proceeds on the UE-side. The new configuration is now available both on the UE and the network side, and at the scheduled activation time the new configuration is assumed by all applicable peer entities. + +In case the old and the new physical channel configurations are incompatible with each other (due to different DPCCH format, TFCI patterns or similar differences), the modification on physical layer and L2 require exact synchronisation between the UE and the NW, as shown in figure 7. + +![Sequence diagram for Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the RNC to establish a radio bearer with a dedicated physical channel modification.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant SRNC-RRC + participant SRNC-RLC + participant SRNC-MAC + participant CRNC-MAC + participant RNC-L1 + participant Node B-L1 + participant UE-L1 + participant UE-MAC + participant UE-RLC + participant UE-RRC + + Note right of SRNC-RRC: Request for RB Establishment + SRNC-RRC->>SRNC-RLC: Request for RB Establishment + Note right of SRNC-RLC: Incompatible DCH Modification required + SRNC-RLC->>Node B-L1: CPHY-RL-Modify-REQ + Node B-L1-->>SRNC-RLC: CPHY-RL-Modify-CNF + Note right of SRNC-RLC: Choose ActivationTime + SRNC-RLC->>Node B-L1: CPHY-commit-REQ + Node B-L1-->>SRNC-RLC: CPHY-RL-Modify-CNF + SRNC-RLC->>Node B-L1: CPHY-TrCH-Config-REQ + Node B-L1-->>SRNC-RLC: DCCH: Acknowledged Data [Radio Bearer Setup] + SRNC-RLC->>UE-RLC: RLC-Data-REQ [Radio Bearer Setup] + UE-RLC-->>SRNC-RLC: DCCH: Data ack + SRNC-RLC->>UE-RRC: RLC-Data-IND [Radio Bearer Setup] + UE-RRC-->>SRNC-RLC: CPHY-RL-Modify-REQ + SRNC-RLC->>Node B-L1: CPHY-TrCH-Config-REQ + Node B-L1-->>SRNC-RLC: DCCH: Acknowledged Data [Radio Bearer Setup] + SRNC-RLC->>RNC-L1: CPHY-RL-Modify-REQ + RNC-L1-->>SRNC-RLC: CPHY-RL-Modify-CNF + SRNC-RLC->>CRNC-MAC: CPHY-TrCH-Config-REQ + CRNC-MAC-->>SRNC-RLC: CMAC-C / SH-Config-REQ + SRNC-RLC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC-->>SRNC-RLC: CMAC-D / C / SH-Config-REQ + SRNC-RLC->>UE-MAC: CRLC-Config-REQ + UE-MAC-->>SRNC-RLC: CRLC-Config-REQ + Note over UE-L1, SRNC-RLC: L1, MAC and RLC Modified + Note left of UE-RLC: DTCH: RLC Link Established + Note right of SRNC-RLC: DTCH: RLC Link Established + SRNC-RLC->>UE-RLC: RLC-Data-REQ [Radio Bearer Setup Complete] + UE-RLC-->>SRNC-RLC: DCCH: Data ack + SRNC-RLC->>UE-RRC: RLC-Data-IND [Radio Bearer Setup Complete] + UE-RRC-->>SRNC-RLC: RLC-Data-CNF + UE-RRC-->>SRNC-RLC: RB Establish Indication + SRNC-RLC-->>SRNC-RRC: RB Establish Confirmation + +``` + +Sequence diagram for Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the RNC to establish a radio bearer with a dedicated physical channel modification. + +Figure 7: Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification + +##### 6.2.1.1.4 + +##### Radio Bearer Establishment without Dedicated Physical Channel + +![Sequence diagram for Radio Bearer Establishment without Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves DCCH: RADIO BEARER SETUP, CMAC-D/C/SH-Config-REQ, RLC-Data-REQ, and subsequent confirmations and link establishment messages.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The sequence diagram illustrates the interaction for Radio Bearer Establishment without a Dedicated Physical Channel. It begins with the SRNC-RRC sending a 'Request for RB Establishment' to the SRNC-RLC. A decision diamond 'No DCH Required' follows. The SRNC-RLC then sends a 'DCCH: RADIO BEARER SETUP (acknowledged or unacknowledged optional)' message to the UE-RRC. The UE-RRC responds with 'CMAC-D / C / SH-Config-REQ' to the UE-MAC. The UE-MAC sends 'RLC-Data-REQ' to the UE-RLC. A '[Radio Bearer Setup Complete]' message is sent from the UE-RLC to the SRNC-RLC via the DCCH. The SRNC-RLC sends 'RLC-Data-IND' to the SRNC-RRC and '[Radio Bearer Setup Complete]' to the UE-RLC. The UE-RLC sends 'RLC-Data-CNF' to the UE-RRC. The SRNC-RRC sends 'CRLC-Config-REQ' to the SRNC-RLC, which in turn sends 'CMAC-D-Config-REQ' to the SRNC-MAC. The SRNC-MAC sends 'CMAC-C / SH-Config-REQ' to the CRNC-MAC. The CRNC-MAC sends 'CRLC-Config-REQ' to the UE-RLC. The UE-RLC sends a 'DTCH: RLC Link Established' message to the UE-RRC. The SRNC-RLC sends a 'DTCH: RLC Link Established' message to the SRNC-RRC. Finally, the UE-RRC sends an 'RB Establish Indication' and the SRNC-RRC sends an 'RB Establish Confirmation'. + +Sequence diagram for Radio Bearer Establishment without Dedicated Physical Channel. Lifelines: UE-RRC, UE-RLC, UE-MAC, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The process involves DCCH: RADIO BEARER SETUP, CMAC-D/C/SH-Config-REQ, RLC-Data-REQ, and subsequent confirmations and link establishment messages. + +Figure 8: Radio Bearer Establishment without Dedicated Physical Channel + +For some radio bearers dedicated radio resources are not permanently associated. Therefore the setting up of the physical resource is separate from the actual radio bearer setup, which involves only RLC and MAC. + +MAC can be initially configured to operate either on existing dedicated transport and physical channels or on common channels. + +##### 6.2.1.1.5 Void + +#### 6.2.1.2 Radio Bearer Release + +Similar as for Radio Bearer Establishment procedure, the Radio Bearer Release can include physical channel modification or physical channel deactivation depending on the differences between new and old QoS parameters. These can also be both synchronised and unsynchronised. + +The Radio Bearer Release procedure is initiated when the release is requested from the RRC layer on the NW side. This request contains a bearer reference, and on retrieval a RB Release Confirm primitive is immediately returned to the Non-Access Stratum. + +New L1 and L2 parameters may be chosen for remaining radio bearers if any. A RADIO BEARER RELEASE message is sent from the RRC layer in the network to its peer entity in the UE. This message includes possible new L1, MAC and RLC parameters for remaining radio bearers and identification of the radio bearer to be released (note). An RB Release Indication is sent by the UE-RRC. + +NOTE: In synchronised case a specific activation time would be needed for the change of L1 and L2 configuration to avoid data loss. + +The RRC on the UE side configures L1 and MAC, and releases the RLC entity associated to the released radio bearer. After receiving a RADIO BEARER RELEASE COMPLETE message from the UE, the NW-RRC does a similar reconfiguration also on the network side. + +##### 6.2.1.2.1 Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification + +The example in figure 10 shows the case where release can be executed as an unsynchronised physical channel modification, i.e. without physical channel deactivation. + +After notifying upper layers of the release, a RADIO BEARER RELEASE message (acknowledged or unacknowledged transmission optional for the network) is sent to the UE triggering the reconfiguration in the UE. When this is finalised the UE sends a RADIO BEARER RELEASE COMPLETE message to the network, after which the reconfiguration is executed in the network. + +![Sequence diagram for Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification. Lifelines include UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, and SRNC-RRC. The process involves a request for RB release, a decision on DCH modification, and subsequent configuration and release messages across the layers.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant SRNC-RRC + participant SRNC-RLC + participant SRNC-MAC + participant CRNC-MAC + participant RNC-L1 + participant Node B-L1 + participant UE-L1 + participant UE-MAC + participant UE-RLC + participant UE-RRC + + Note right of SRNC-RRC: Request for RB Release + SRNC-RRC->>SRNC-RLC: Request for RB Release + SRNC-RLC->>SRNC-RRC: RB Release Confirmation + SRNC-RLC->>SRNC-RRC: Compatible DCH Modification required + Note right of SRNC-RRC: DCCH: RADIO BEARER RELEASE (acknowledged or unacknowledged optional) + SRNC-RRC->>UE-RRC: DCCH: RADIO BEARER RELEASE (acknowledged or unacknowledged optional) + UE-RRC->>UE-RRC: RB Release Indication + UE-RRC->>UE-RLC: CRLC-Config-REQ (DTCH) + UE-RLC->>UE-RLC: L2 link released (DTCH) + UE-RLC->>UE-MAC: CMAC-D / C / SH-Config-REQ + UE-MAC->>UE-L1: CPHY-TrCH-Release-REQ + UE-MAC->>UE-L1: CPHY-RL-Release-REQ + Note right of UE-L1: DCCH: RADIO BEARER RELEASE COMPLETE (acknowledged) + UE-L1->>SRNC-RRC: DCCH: RADIO BEARER RELEASE COMPLETE (acknowledged) + SRNC-RRC->>SRNC-RLC: CRLC-Config-REQ (DTCH) + SRNC-RLC->>SRNC-RLC: L2 link released (DTCH) + SRNC-RLC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>CRNC-MAC: CMAC-C / SH-Config-REQ + CRNC-MAC->>RNC-L1: CPHY-TrCH-Release-REQ + CRNC-MAC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>Node B-L1: CPHY-TrCH-Release-REQ + RNC-L1->>Node B-L1: CPHY-RL-Release-REQ + Node B-L1->>UE-L1: CPHY-RL-Modify-CNF + +``` + +Sequence diagram for Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification. Lifelines include UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, and SRNC-RRC. The process involves a request for RB release, a decision on DCH modification, and subsequent configuration and release messages across the layers. + +Figure 10: Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification + +#### 6.2.1.3 Radio Bearer Reconfiguration + +For Radio Bearer Reconfiguration, both synchronised and unsynchronised procedures are applicable. The unsynchronised procedure is shown as an example. + +##### 6.2.1.3.1 Unsynchronised Radio Bearer Reconfiguration + +Because of the unsynchronised nature of the procedure in figure 11, there is no activation time and no separate commit request for the Node B physical layer is needed. The possibility for executing the requested modification will be reported in the confirmation primitives from the physical layer. If the modification involves the release of an old configuration, the release can be postponed to the end of the procedure. After the reception of a RADIO BEARER RECONFIGURATION from the RNC-RRC (acknowledged or unacknowledged transmission optional for the network), the UE executes the modifications on L1 and L2. + +Upon reception of a RADIO BEARER RECONFIGURATION COMPLETE message from the UE-RRC, the NW-RRC executes the modifications on L1 and L2. Finally the old configuration, if any, is released from Node B-L1. + +![Sequence diagram for Unsynchronised Radio Bearer Reconfiguration. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows two reconfiguration procedures separated by a 'Radio Bearer Reconfiguration Complete' message.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note over UE-L1, Node B-L1: Uu + Note over Node B-L1, RNC-L1: Iub + + SRNC-RRC->>Node B-L1: CPHY-RL-Modify-REQ + SRNC-RRC->>Node B-L1: CPHY-TrCH-Config-REQ + Node B-L1->>SRNC-RRC: CPHY-RL-Modify-CNF + Node B-L1->>UE-L1: DCCH: RADIO BEARER RECONFIGURATION (acknowledged or unacknowledged optional) + UE-RRC->>UE-L1: CPHY-RL-Modify-REQ + UE-RRC->>UE-L1: CPHY-TrCH-Config-REQ + UE-RRC->>UE-MAC: CMAC-D / C / SH-Config-REQ + UE-RRC->>UE-RLC: CRLC-Config-REQ + UE-RRC->>UE-RLC: RLC-Data-REQ +[Radio Bearer Reconfiguration Complete] + UE-RLC->>SRNC-RLC: DCCH: Acknowledged Data +[Radio Bearer Reconfiguration Complete] + SRNC-RLC->>UE-RLC: DCCH: Data ack + UE-RLC->>UE-RRC: RLC-Data-CNF + SRNC-RLC->>SRNC-RRC: RLC-Data-IND +[Radio Bearer Reconfiguration Complete] + SRNC-RRC->>RNC-L1: CPHY-RL-Modify-REQ + SRNC-RRC->>RNC-L1: CPHY-TrCH-Config-REQ + SRNC-RRC->>SRNC-MAC: CMAC-C / SH-Config-REQ + SRNC-RRC->>CRNC-MAC: CMAC-D-Config-REQ + SRNC-RRC->>SRNC-RLC: CRLC-Config-REQ + SRNC-RLC-->>Node B-L1: CPHY-RL-Modify-REQ (release old) + SRNC-RLC-->>Node B-L1: CPHY-TrCH-Config-REQ (release old) + Node B-L1-->>SRNC-RLC: CPHY-RL-Modify-CNF + +``` + +Sequence diagram for Unsynchronised Radio Bearer Reconfiguration. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows two reconfiguration procedures separated by a 'Radio Bearer Reconfiguration Complete' message. + +Figure 11: Unsynchronised Radio Bearer Reconfiguration + +### 6.2.2 Transport Channel Reconfiguration + +For transport channel reconfiguration, both synchronised and unsynchronised procedures are applicable. + +#### 6.2.2.1 Unsynchronised Transport Format Set Reconfiguration + +Figure 12 illustrates an example of a procedure for a change of the Transport Format Set for one transport channel. This is done with the Transport Channel Reconfiguration procedure. + +A change of the transport format set for a transport channel is triggered in the RRC layer in the network. A TRANSPORT CHANNEL RECONFIGURATION message is sent from the RRC layer in the network to its peer entity (acknowledged or unacknowledged transmission is a network option). This message contains the new transport format set and a new transport format combination Set, i.e. new parameters for L1 and MAC (note). When this message is received in the UE a reconfiguration of L1 and MAC is done. A similar reconfiguration is also done on the network side after the reception of a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message. + +NOTE: In a synchronised procedure a specific activation time is needed for the change of L1 and L2 configuration to avoid data loss. + +During the reconfiguration of the transport format set for a transport channel, radio traffic on this channel could be halted temporarily since the UE and the network are not necessarily aligned in their configuration. This traffic can resume after the COMPLETE-message. + +![Sequence diagram for Unsyncronised Transport Format Set Reconfiguration. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows message exchanges between these entities across Uu and Iub interfaces.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The sequence diagram illustrates the interaction for Unsyncronised Transport Format Set Reconfiguration. The lifelines are grouped by interface: Uu (UE-RRC, UE-RLC, UE-MAC, UE-L1) and Iub (Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC). The sequence of messages is as follows: + +- SRNC-RRC sends **CPHY-RL-Modify-REQ** to Node B-L1. +- Node B-L1 responds with **CPHY-RL-Modify-CNF** to SRNC-RRC. +- Node B-L1 sends **DCCH: DCH:TRANSPORT CHANNEL RECONFIGURATION (acknowledged or unacknowledged optional)** to UE-L1. +- UE-L1 sends **CPHY-RL-Modify-REQ** to UE-RRC. +- UE-RRC sends **CMAC-D / C / SH-Config-REQ [Change TFS]** to UE-MAC. +- UE-MAC sends **TRANSPORT CHANNEL RECONFIGURATION COMPLETE (acknowledged)** to SRNC-RRC. +- SRNC-RRC sends **CMAC-C / SH-Config-REQ [Change TFS]** to CRNC-MAC. +- CRNC-MAC sends **CMAC-D-Config-REQ [Change TFS]** to SRNC-MAC. + +Sequence diagram for Unsyncronised Transport Format Set Reconfiguration. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows message exchanges between these entities across Uu and Iub interfaces. + +Figure 12: Unsyncronised Transport Format Set Reconfiguration + +### 6.2.3 Physical Channel Reconfiguration + +For physical channel reconfiguration, both synchronised and unsynchronised procedures are applicable. + +#### 6.2.3.1 UE-Originated DCH Activation + +Figure 13 illustrates an example of a procedure for a switch from common channels (CELL\_FACH) to dedicated (CELL\_DCH) channels. + +In the UE the traffic volume measurement function decides to send a MEASUREMENT REPORT message to the network. In the network this measurement report could trigger numerous different actions. For example the network could do a change of transport format set, channel type switching or, if the system traffic is high, no action at all. In this case a switch from CELL\_FACH to CELL\_DCH is initiated. + +Whether the report should be sent with acknowledged or unacknowledged data transfer is configured by the network. + +First, the modifications on L1 are requested and confirmed on the network side with CPHY-RL-Setup primitives. + +The RRC layer on the network side sends a PHYSICAL CHANNEL RECONFIGURATION message to its peer entity in the UE (acknowledged or unacknowledged transmission optional to the network). This message is sent on DCCH mapped to FACH. The message includes information about the new physical channel, such as codes and the period of time for which the DCH is activated (note). + +**NOTE:** This message does not include new transport formats. If a change of these is required due to the change of transport channel, this is done with the separate procedure Transport Channel Reconfiguration. This procedure only handles the change of transport channel. + +When the UE has detected synchronisation on the new dedicated channel L2 is configured on the UE side and a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message can be sent on DCCH mapped on DCH to RRC in the network. Triggered by either the NW CPHY\_sync\_ind or the L3 complete message, the RNC-L1 and L2 configuration changes are executed in the NW. + +![Sequence diagram for UE-Originated DCH Activation. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the network to activate a DCH.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note over UE-RRC, SRNC-RRC: Uu lub + + UE-MAC->>UE-RRC: CMAC-measurement-IND + UE-MAC->>SRNC-RRC: DCCH: RACH: MEASUREMENT REPORT (acknowledged or unacknowledged RLC transmission configurable by UTRAN) + Note right of SRNC-RRC: Switch decision + SRNC-RRC->>Node B-L1: CPHY-RL-Setup-REQ + Note right of Node B-L1: Start tx/rx + Node B-L1->>SRNC-RRC: CPHY-RL-Setup-CNF + Node B-L1->>UE-RRC: DCCH: FACH: PHYSICAL CHANNEL RECONFIGURATION (acknowledged or unacknowledged RLC transmission optional) + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + Note right of UE-L1: Start tx/rx + Note right of UE-L1: Establish L1 connection + UE-L1->>UE-RRC: CPHY-Sync-IND + Node B-L1->>SRNC-RRC: CPHY-Sync-IND + UE-RRC->>UE-MAC: CMAC-D / C / SH-Config-REQ + UE-RRC->>UE-RLC: CRLC-Config-REQ + SRNC-RRC->>UE-RRC: DCCH: DCH: PHYSICAL CHANNEL RECONFIGURATION COMPLETE + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + RNC-L1->>CRNC-MAC: CMAC-C / SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>SRNC-RLC: CRLC-Config-REQ + +``` + +Sequence diagram for UE-Originated DCH Activation. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between the UE and the network to activate a DCH. + +Figure 13: UE-Originated DCH Activation + +#### 6.2.3.2 UE-terminated synchronised DCH Modify + +![Sequence diagram for UE-terminated synchronised DCH Modify. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between these entities to modify a DCH, including RRC signaling, RLC data transfer, and MAC/PHY configuration updates.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note right of SRNC-RRC: Choose ActivationTime + + SRNC-RRC->>SRNC-RLC: CPHY-RL-Modify-REQ + SRNC-RRC->>Node B-L1: CPHY-RL-Modify-CNF + SRNC-RRC->>SRNC-RLC: CPHY-commit-REQ + SRNC-RRC->>SRNC-RLC: RLC-Data-REQ + SRNC-RLC->>Node B-L1: DCCH: DCH: Acknowledged Data + Note right of Node B-L1: [Physical Channel Reconfiguration] + Node B-L1->>SRNC-RLC: DCCH: DCH: Data ack + SRNC-RLC->>UE-RLC: RLC-Data-IND + Note right of UE-RLC: [Physical Channel Reconfiguration] + UE-RLC->>UE-RRC: CPHY-RL-Modify-REQ + UE-RRC->>CRNC-MAC: CMAC-D / C / SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-C / SH-Config-REQ + SRNC-MAC->>SRNC-RLC: CMAC-D-Config-REQ + SRNC-RLC->>UE-RLC: CRLC-Config-REQ + Note over UE-RLC, SRNC-RLC: Modify L1, MAC, RLC + UE-RLC->>UE-RRC: RLC-Data-REQ + Note right of UE-RRC: [Physical Channel Reconfiguration Complete] + SRNC-RLC->>Node B-L1: DCCH: DCH: Acknowledged Data + Note right of Node B-L1: [Physical Channel Reconfiguration Complete] + Node B-L1->>SRNC-RLC: DCCH: DCH: Data ack + SRNC-RLC->>UE-RLC: RLC-Data-IND + Note right of UE-RLC: [Physical Channel Reconfiguration Complete] + UE-RLC->>UE-RRC: RLC-Data-CNF + +``` + +Sequence diagram for UE-terminated synchronised DCH Modify. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between these entities to modify a DCH, including RRC signaling, RLC data transfer, and MAC/PHY configuration updates. + +Figure 14: UE-terminated synchronised DCH Modify + +Figure 14 illustrates an example of a synchronised procedure for DCH modification. Triggering of this procedure could for example be accomplished by an inactivity timer. The procedure can e.g. release all transport formats of a radio bearer without releasing the DCH, due to another bearer using it. The synchronised procedure is applied in the case when the old and new configurations are not compatible e.g. change of channelisation code. + +After the CPHY-RL-Modify requests have been confirmed, an activation time is chosen by NW-RRC. After deciding upon the activation time, the NW-RRC sends a PHYSICAL CHANNEL RECONFIGURATION message as acknowledged data transfer to the UE. In both uplink and downlink this message is sent on DCCH mapped on DCH. + +After reception the UE reconfigures L1 and L2 to DCH resources. If a complete message is used it would be sent on DCCH mapped on DCH. In the unsynchronised case this message could trigger a modification of L1 and L2 resources in the network associated with the dedicated channel. + +#### 6.2.3.3 UE-terminated DCH Release + +Figure 15 illustrates an example of a procedure for a switch from dedicated (CELL\_DCH) to common (CELL\_FACH) channels. All DCHs used by a UE are released and all dedicated logical channels are transferred to CELL\_FACH instead. Triggering of this procedure could for example be an inactivity timer. + +A switch from DCH to common channels is decided and a PHYSICAL CHANNEL RECONFIGURATION message is sent (acknowledged or unacknowledged data transfer is a network option) from the RRC layer in the network to the UE. This message is sent on DCCH mapped on DCH. + +NOTE 1: This message does not include new transport formats. If a change of these is required due to the change of transport channel, this is done with the separate procedure Transport Channel Reconfiguration. This procedure only handles the change of transport channel. + +If the loss of L1 sync is used to detect in the NW that the UE has released the DCHs, as is one possibility in the figure, then there may be a need to configure the Node B-L1 to a short timeout for detecting loss of sync. This is presented by the CPHY-Out-of-Sync-Config primitives in the figure. + +After reception the UE reconfigures L1 and L2 to release old DCH resources. The PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the network is here sent on DCCH mapped on RACH (message acknowledgement on FACH). This message triggers a normal release of L1 and L2 resources in the network associated with the dedicated channel. + +NOTE 2: When a Switch to CELL\_FACH is done it is important to free the old code as fast as possible so that it can be reused. Therefore instead of waiting for the Physical Channel Reconfiguration Complete message the network can reconfigure L1 and L2 when the acknowledged data confirmation arrives and the network is sure that the UE has received the Physical Channel Reconfiguration message. To be even more certain that the UE has released the old DCH resources the network can wait until after the Out of sync Indication from L1. These steps including a timer starting when the Physical Channel Reconfiguration is sent, gives the network four different indications that the released DCH is really released, and that resources can be reused. + +Error! No + +Error! No text of specified style in + +![Sequence diagram for UE-terminated DCH Release. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between these entities to release a DCH, including messages like DCCH: DCH: PHYSICAL CHANNEL RECONFIGURATION, CPHY-Out-Of-Sync-Config-REQ, and CPHY-RL-Release-REQ.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note over UE-RRC, UE-L1: Uu + Note over Node B-L1, SRNC-RRC: Iub + + SRNC-RRC->>SRNC-RLC: CPHY-Out-Of-Sync-Config-REQ + SRNC-RLC->>SRNC-MAC: CPHY-Out-Of-Sync-Config-CNF + SRNC-MAC->>Node B-L1: DCCH: DCH: PHYSICAL CHANNEL RECONFIGURATION (acknowledged or unacknowledged optional) + Node B-L1-->>UE-L1: CPHY-RL-Release-REQ + UE-L1-->>UE-MAC: CPHY-Out-Of-Sync-IND + UE-MAC->>UE-RLC: CMAC-D / C / SH-Config-REQ + UE-RLC->>UE-RRC: CRLC-Config-REQ + SRNC-RRC->>SRNC-RLC: DCCH: RACH: PHYSICAL CHANNEL RECONFIGURATION COMPLETE + SRNC-RLC->>SRNC-MAC: CPHY-RL-Release-REQ + SRNC-MAC->>CRNC-MAC: CPHY-RL-Release-REQ + CRNC-MAC->>RNC-L1: CMAC-C / SH-Config-REQ + RNC-L1->>Node B-L1: CMAC-D-Config-REQ + Node B-L1->>UE-L1: CRLC-Config-REQ + +``` + +Sequence diagram for UE-terminated DCH Release. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC. The diagram shows the interaction between these entities to release a DCH, including messages like DCCH: DCH: PHYSICAL CHANNEL RECONFIGURATION, CPHY-Out-Of-Sync-Config-REQ, and CPHY-RL-Release-REQ. + +Figure 15: UE-terminated DCH Release + +### 6.2.4 Transport Format Combination Control + +#### 6.2.4.1 Transport Format Combination Limitation + +![Sequence diagram illustrating Transport Format Combination Limitation. The diagram shows the interaction between UE-RRC, UE-RLC, UE-MAC, SRNC-RLC, and SRNC-RRC across Uu and Iub interfaces. The process involves a 'DCCH: TRANSPORT FORMAT COMBINATION CONTROL' message from SRNC-RRC to UE-RRC, followed by a 'CMAC-D-Config-REQ' from UE-RRC to UE-MAC with '[New smaller TFCS]'. Later, another 'DCCH: TRANSPORT FORMAT COMBINATION CONTROL' message is sent, followed by a 'CMAC-D-Config-REQ' with '[Original TFCS]'. The SRNC-RRC also has internal states 'TFC limitation triggered' and 'TFC limitation released'.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note right of SRNC-RRC: TFC limitation triggered + SRNC-RRC->>UE-RRC: DCCH: TRANSPORT FORMAT COMBINATION CONTROL (acknowledged, unacknowledged or transparent optional) + UE-RRC->>UE-MAC: CMAC-D-Config-REQ [New smaller TFCS] + Note right of SRNC-RRC: TFC limitation released + SRNC-RRC->>UE-RRC: DCCH: TRANSPORT FORMAT COMBINATION CONTROL (acknowledged, unacknowledged or transparent optional) + UE-RRC->>UE-MAC: CMAC-D-Config-REQ [Original TFCS] +``` + +Sequence diagram illustrating Transport Format Combination Limitation. The diagram shows the interaction between UE-RRC, UE-RLC, UE-MAC, SRNC-RLC, and SRNC-RRC across Uu and Iub interfaces. The process involves a 'DCCH: TRANSPORT FORMAT COMBINATION CONTROL' message from SRNC-RRC to UE-RRC, followed by a 'CMAC-D-Config-REQ' from UE-RRC to UE-MAC with '[New smaller TFCS]'. Later, another 'DCCH: TRANSPORT FORMAT COMBINATION CONTROL' message is sent, followed by a 'CMAC-D-Config-REQ' with '[Original TFCS]'. The SRNC-RRC also has internal states 'TFC limitation triggered' and 'TFC limitation released'. + +**Figure 16: Transport Format Combination Limitation** + +Figure 16 illustrates an example of a Transport Format Combination Control procedure. A congestion situation occurs and allowed transport format combinations are restricted temporarily. When the congestion is resolved the restriction is removed. + +This procedure is initiated with a Transport Format Combination Control message from the network to the UE (acknowledged, unacknowledged or transparent transmission optional to the NW). This message contains a subset of the ordinary Transport Format Combination Set. The UE then continues with a reconfiguration of MAC. MAC sees the TFC subset as a completely new set. + +Further, after a while when the congestion is resolved a new Transport Format Combination Control message is sent to the UE from the RRC layer in the network. This message contains a subset that is the entire original set. Again, the UE reconfigures the MAC. + +### 6.2.5 Dynamic Resource Allocation Control of Uplink DCHs + +![Sequence diagram showing dynamic resource allocation control of uplink DCHs between UE-RRC, UE-MAC, and CRNC-RRC.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +The diagram illustrates the interaction for dynamic resource allocation control of uplink DCHs. It features three lifelines: UE-RRC, UE-MAC, and CRNC-RRC. The UE-RRC and UE-MAC lifelines are grouped under the label 'Uu', while the CRNC-RRC lifeline is under 'Iub'. + +The sequence of messages and actions is as follows: + +- The CRNC-RRC sends a message to the UE-RRC labeled "Update UL resources allocation control parameters (Max Rate, $p_{tr}$ )". +- The UE-RRC performs an internal action: "Check permission for DCHs. If granted select TFCS subset for DCHs, Else wait for $T_{retry}$ ". +- Following this, the UE-RRC sends a message to the UE-MAC labeled "CMAC-D\_conf\_req [subset of TFCS]". +- Finally, a horizontal bar spanning the UE-MAC and CRNC-RRC lifelines indicates "UL DCH : Transmission during $T_{validity}$ ". + +Sequence diagram showing dynamic resource allocation control of uplink DCHs between UE-RRC, UE-MAC, and CRNC-RRC. + +Figure 17: Dynamic Resource Allocation Control of Uplink DCHs + +Figure 17 illustrates an example of a Dynamic Resource Allocation Control (DRAC) procedure of uplink DCHs. The CRNC regularly broadcasts the following parameters: + +- transmission probability $p_{tr}$ , which indicates the probability for a UE to be allowed to transmit on its DCHs, which are under control by this procedure, during the next period $T_{validity}$ ; +- maximum total bit rate allowed to be used by the UE on its DCH which are under controlled by this procedure, during the next allowed period $T_{validity}$ . + +Besides these parameters, the RNC has allocated the following parameters to the UE: + +- transmission time validity, $T_{validity}$ , which indicates the time duration for which an access for transmission is granted; +- reaccess time $T_{retry}$ , which indicates the time duration before retrying to access the resources, in case transmission has not been granted. + +This procedure is initiated with a SYSTEM INFORMATION message containing the above DRAC parameters regularly broadcast by the CRNC on the FACH. It applies to all UEs capable of simultaneous reception of Secondary CCPCH and DPCH and having DCHs that can be controlled dynamically. The UEs have to listen to this message prior to transmission on these DCHs. The UE RRC checks whether transmission is allowed, and then reconfigures MAC with a new subset of TFCS derived from the maximum total bit rate parameter. This TFCS subset shall control only the DCHs that are under control by this procedure. + +In case of soft handover on the uplink DCH, The UE is requested either to listen to broadcast information from its primary cell (the one with the lowest pathloss), or from all cells involved in its Active Set, depending on its class. In the latter case, the UE is expected to react according to the stricter control information. + +### 6.2.6 Variable Rate Transmission of Uplink DCHs + +![Sequence diagram for Variable Rate Transmission of Uplink DCHs showing interactions between UE layers (RR, RLC, MAC, L1) and RNC layers (L1, RLC, RR) over Uu and Iub interfaces.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +The sequence diagram illustrates the interaction for Variable Rate Transmission of Uplink DCHs. It features lifelines for UE-RR, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, SRNC-RLC, and SRNC-RR. The process begins with an RB Establishment procedure in SRNC-RR, followed by a DCCH: RADIO BEARER SETUP message from SRNC-RR to UE-RR. A horizontal bar indicates the DTCH: RLC Link Established. The UE-RR then sends a CPHY-Measurement-REQ to UE-L1. UE-L1 transmits DCH: Acknowledged Data to RNC-L1. Upon reaching the maximum allowable transmit power, UE-L1 sends a PHY-Status-IND to UE-MAC, which triggers a 'Decrease data rate within TFCS' action. Once the power is below the threshold, UE-L1 sends another PHY-Status-IND, leading to an 'Increase data rate within TFCS' action. Finally, packet transmission resumes, indicated by a series of dots and the text 'continue packet transmission'. + +Sequence diagram for Variable Rate Transmission of Uplink DCHs showing interactions between UE layers (RR, RLC, MAC, L1) and RNC layers (L1, RLC, RR) over Uu and Iub interfaces. + +Figure 18: Variable Rate Transmission of Uplink DCHs + +Figure 18 illustrates an example of the Variable Rate Transmission procedure of uplink DCHs. With this procedure the QoS of service with variable rate can be maintained and unnecessary interference can be avoided by a temporary reduction of the data rate within the TFCS. + +When a connection for a variable rate service is established the RRC assigns the TFCS to MAC. At the radio bearer set-up procedure the maximum allowable Tx power can also be set for each user if it shall be different from the UE capability class. + +With the CPHY-Measurement-REQ the power thresholds will be set to the UE. If during a transmission the allowable transmit power is above the set threshold the event will be signalled to the MAC that will decrease the data rate within the set TFCS at the next transmission time interval. In the UE, the PDUs that can not be transmitted in a TTI (i.e. MAC has indicated that some of the available PDUs can not be transmitted) shall be buffered according to the discard configuration set by RRC. + +When channel conditions improve and the averaged transmission power falls below the allowable transmission power the physical layer indicates this event to the MAC. If there is enough data to be sent, the MAC in response increases the data rate by increasing the number of transport blocks delivered to L1 and the physical layer increases the total transmission power to the UE by the predefined amount. This allows the data that was buffered during bad channel conditions to be delivered to the UTRAN. + +## 6.3 Data transmission + +### 6.3.1 Void + +### 6.3.2 Void + +### 6.3.3 Void + +### 6.3.4 Data transfer on USCH (TDD only) + +In figure 23 a data transfer procedure on USCH is presented. It is assumed that the RB establishment has been performed for example with the RB Establishment procedure without Dedicated Physical Channel as illustrated in subclause 6.2.1.1.4 and that the RB is mapped on the USCH and DSCH transport channels. Use of the USCH is possible with or without an associated DCH. + +In the UE the traffic measurement function decides to send a Capacity Request to the network using the SHCCH logical channel mapped on the RACH or USCH. In the C-RRC the USCH/DSCH scheduling function will decide to allocate physical resources to this logical channel and RRC in C-RNC sends a PhyShChAllocation to its peer entity in the UE. This message specifies the physical resources and the period of time the MAC-c/sh can transfer the data on the USCH transport channel. + +Both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the USCH and at the specified time MAC-c/sh in the UE conveys the data using the specified PUSCH resources. + +This operation may be repeated several times till the RLC buffer is empty. + +In the diagram it is assumed that the PhyShChAllocation has allocated additionally to the PUSCH resources some PDSCH resources, so that at the time specified in the allocation message both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the DSCH and at the specified time MAC-c/sh in the C-RNC conveys the acknowledgement message of the UTRAN RLC to its UE peer entity using the specified PDSCH resources. + +Transmitting the acknowledgement message via FACH is also possible. + +![Sequence diagram for Data transfer on USCH. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, NodeB-L1, CRNC-MAC, SRNC-MAC, CRNC-RRC, SRNC-RLC, SRNC-RR. The diagram shows the interaction between the UE and the RNC for data transfer on the USCH transport channel. It includes steps for RLC buffer scanning, SHCCH:MAC-Unit-Data-REQ, Capacity Request, Scheduling, PhyShChAllocation, CMAC-C/SH/D-Config-REQ, MAC-Data-REQ, USCH:Data, MAC-Data-IND, and PDU-Ack.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant NodeB-L1 + participant CRNC-MAC + participant SRNC-MAC + participant CRNC-RRC + participant SRNC-RLC + participant SRNC-RR + + Note left of UE-RRC: RLC buffer scanning + UE-RRC->>UE-MAC: SHCCH:MAC-Unit-Data-REQ + UE-MAC->>UE-L1: [ Capacity Request ] + UE-L1->>NodeB-L1: RACH/USCH: SHCCH-Data + NodeB-L1->>CRNC-MAC: [ Capacity Request ] + CRNC-MAC->>SRNC-MAC: SHCCH: MAC-Unit-Data-IND + SRNC-MAC->>CRNC-RRC: [ Capacity Request ] + Note right of CRNC-RRC: Scheduling + CRNC-RRC->>SRNC-MAC: SHCCH:MAC-Unit-Data-REQ + SRNC-MAC->>NodeB-L1: PhyShChAllocation + NodeB-L1->>UE-L1: FACH/USCH: SHCCH-Data + UE-L1->>UE-MAC: [ PhyShChAllocation ] + UE-MAC->>UE-RRC: SHCCH: MAC-Unit-Data-IND + Note left of UE-RRC: Data transfer in the user plane + UE-RRC->>UE-MAC: CMAC-C/SH/D-Config-REQ + UE-MAC->>UE-L1: MAC-Data-REQ + UE-L1->>NodeB-L1: USCH:Data + NodeB-L1->>CRNC-MAC: [ ] + CRNC-MAC->>SRNC-MAC: MAC-Data-IND + SRNC-MAC->>SRNC-RLC: [ ] + UE-MAC->>UE-L1: MAC-Data-REQ + UE-L1->>NodeB-L1: USCH:Data + NodeB-L1->>CRNC-MAC: [ ] + CRNC-MAC->>SRNC-MAC: MAC-Data-IND + SRNC-MAC->>SRNC-RLC: [ ] + UE-MAC->>UE-L1: MAC-Data-REQ + UE-L1->>NodeB-L1: USCH:Data + NodeB-L1->>CRNC-MAC: [ ] + CRNC-MAC->>SRNC-MAC: MAC-Data-IND + SRNC-MAC->>SRNC-RLC: [ ] + UE-RRC->>UE-MAC: CMAC-C/SH/D-Config-REQ + UE-MAC->>UE-L1: MAC-Data-REQ + UE-L1->>NodeB-L1: DPSCH DSCH/FACH : + NodeB-L1->>CRNC-MAC: [ PDU-Ack ] + CRNC-MAC->>SRNC-MAC: CMAC-C/SH/D-Config-REQ + SRNC-MAC->>CRNC-RRC: MAC-Data-REQ + CRNC-RRC->>SRNC-RLC: [ PDU-Ack ] + SRNC-RLC->>SRNC-RR: [ ] + UE-L1->>UE-MAC: MAC-Data-IND + UE-MAC->>UE-RRC: [ PDU-Ack ] + +``` + +Sequence diagram for Data transfer on USCH. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, NodeB-L1, CRNC-MAC, SRNC-MAC, CRNC-RRC, SRNC-RLC, SRNC-RR. The diagram shows the interaction between the UE and the RNC for data transfer on the USCH transport channel. It includes steps for RLC buffer scanning, SHCCH:MAC-Unit-Data-REQ, Capacity Request, Scheduling, PhyShChAllocation, CMAC-C/SH/D-Config-REQ, MAC-Data-REQ, USCH:Data, MAC-Data-IND, and PDU-Ack. + +Figure 23: Data transfer on USCH + +### 6.3.5 Data transfer on DSCH (TDD only) + +In figure 24 a data transfer procedure on DSCH is presented. It is assumed that the RB establishment has been performed for example with the RB Establishment procedure without Dedicated Physical Channel as illustrated in subclause 6.2.1.1.4 and that the RB is mapped on the USCH and DSCH transport channels. + +Use of the DSCH is possible with or without an associated DCH. + +In the C-RRC the USCH/DSCH scheduling function will decide to allocate physical resources in the downlink and RRC in C-RNC sends a PhyShChAllocation message to its peer entity in the UE using SHCCH mapped on the FACH or DSCH. This message specifies the physical resources and the period of time the MAC-c/sh can transfer the data on the DSCH transport channel. + +Both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the DSCH and at the specified time MAC-c/sh in the C-RNC conveys the data using the specified PDSCH resources. + +This operation may be repeated several times till the RLC buffer is empty. + +In the diagram it is assumed that the PhyShChAllocation has allocated additionally to the PDSCH resources some PUSCH resources, so that at the time specified in the allocation message both RRC in the CRNC and the UE configure + +their respective Layer 1 and MAC for the data transfer on the USCH and at the specified time MAC-c/sh in the UE conveys the acknowledgement message of the UE to its C-RNC peer entity using the specified PUSCH resources. + +Transmitting the acknowledgement message via RACH is also possible. + +![Sequence diagram illustrating data transfer on DSCH between UE and NodeB.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +The diagram shows the interaction between the User Equipment (UE) and the NodeB for data transfer on the Downlink Shared Channel (DSCH). The lifelines are organized into three groups: MAC-Data-IND (UE-RRC, UE-RLC, UE-MAC, UE-L1), Uu (NodeB-L1), and Iub (CRNC-MAC, SRNC-MAC, CRNC-RRC, SRNC-RLC, SRNC-RRC). A box labeled 'Data transfer in the user plane' is connected to the UE-RRC lifeline. A box labeled 'RLC buffer scanning Scheduling' is connected to the CRNC-RRC lifeline. + +The sequence of messages is as follows: + +- The CRNC-RRC initiates 'RLC buffer scanning Scheduling'. +- The CRNC-RRC sends a 'SHCCH:MAC-Unit-Data-REQ' to the CRNC-MAC. +- The CRNC-MAC sends a 'FACH/DSCH SHCCH Data' message to the NodeB-L1, with a '[ PhyShCh Allocation ]' indication. +- The NodeB-L1 sends a 'SHCCH: MAC-Unit-Data-IND' to the UE-RRC, with a '[ PhyShCh Allocation ]' indication. +- The UE-RRC sends a 'CMAC-C/SH/D-Config-REQ' to the UE-MAC. +- The CRNC-RRC sends a 'CMAC-C/SH-Config-REQ' to the CRNC-MAC. +- The NodeB-L1 sends 'DSCH:Data' messages to the UE-L1. +- The UE-L1 sends 'MAC-Data-IND' messages to the UE-MAC. +- The CRNC-MAC sends 'MAC-Data-REQ' messages to the SRNC-MAC. +- The SRNC-MAC sends 'MAC-Data-IND' messages to the SRNC-RLC. +- The SRNC-RLC sends '[PDU-Ack ]' messages to the SRNC-RRC. +- The UE-MAC sends 'MAC-Data-REQ' messages to the UE-RLC. +- The UE-RLC sends '[PDU-Ack ]' messages to the UE-RRC. + +Sequence diagram illustrating data transfer on DSCH between UE and NodeB. + +Figure 24: Data transfer on DSCH + +## 6.4 RRC Connection mobility procedures + +The RRC handover protocol must be common for the FDD and TDD modes. This means that the same protocol must support all the following handover procedures. + +### 6.4.1 Handover Measurement Reporting + +Figure 25 illustrates an example where a measurement control and a measurement report procedure is used for handover measurements. The NW RRC requests the UE to start measurements and reporting with a MEASUREMENT CONTROL message. The message includes an indication of a measurement type (e.g. intra-frequency measurement), the radio links to evaluate, the reporting criteria and a measurement identity number. The UE configures L1 to start measurements. When measurement reporting criteria are fulfilled the UE sends a MEASUREMENT REPORT message. + +![Sequence diagram for Handover measurement reporting](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The diagram illustrates the interaction between UE-RRC, UE-L1, and SRNC-RRC for handover measurement reporting. The sequence starts with SRNC-RRC sending a MEASUREMENT CONTROL message to UE-RRC. UE-RRC then sends a CPHY-Measurement-REQ to UE-L1. UE-L1 performs a Measurement and sends a CPHY-Measurement-IND to UE-RRC. UE-RRC checks if the Reporting criteria fulfilled. If so, it sends a MEASUREMENT REPORT to SRNC-RRC. The diagram also shows two additional Measurement blocks in UE-L1, each followed by a CPHY-Measurement-IND to UE-RRC. + +``` +sequenceDiagram + participant SRNC-RRC + participant UE-RRC + participant UE-L1 + Note right of SRNC-RRC: MEASUREMENT CONTROL + SRNC-RRC->>UE-RRC: MEASUREMENT CONTROL + UE-RRC->>UE-L1: CPHY-Measurement-REQ + UE-L1->>UE-RRC: CPHY-Measurement-IND + Note right of UE-L1: Measurement + UE-L1->>UE-RRC: CPHY-Measurement-IND + Note right of UE-L1: Measurement + UE-L1->>UE-RRC: CPHY-Measurement-IND + Note right of UE-RRC: Reporting criteria fulfilled + UE-RRC->>SRNC-RRC: MEASUREMENT REPORT +``` + +Sequence diagram for Handover measurement reporting + +Figure 25: Handover measurement reporting + +### 6.4.2 Cell Update + +Figure 26 illustrates an example of a cell update procedure. + +The cell update procedure is triggered by the cell re-selection function in the UE, which notifies which cell the UE should switch to. The UE reads the broadcast information of the new cell. Subsequently, the UE RRC layer sends a CELL UPDATE message to the UTRAN RRC via the CCCH logical channel and the RACH transport channel. The RACH transmission includes the current U-RNTI (S-RNTI and the SRNC Identity). + +Upon reception of the CELL UPDATE, the UTRAN registers the change of cell. If the registration is successful it replies with a CELL UPDATE CONFIRM message transmitted on the DCCH/FACH to the UE. The message includes the current U-RNTI (S-RNTI and SRNC Identity) and it may also include new C-RNTI and / or U-RNTI (S-RNTI + SRNC Identity). By using DCCH for the confirm message the contents of the message can be ciphered. + +Error! No + +Error! No text of specified style in + +![Sequence diagram of the cell update procedure showing interactions between UE layers (RRC, RLC, MAC, L1) and network elements (Node B, RNC, CRNC, SRNC) across Uu, Iub, and Iur interfaces.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-MAC + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note left of UE-RRC: Cell reselection triggered + UE-RRC->>UE-L1: CPHY-RL-Release-REQ (Stop RX and TX) + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ (Start RX) + UE-L1->>UE-MAC: CPHY-Sync-IND + Node B-MAC->>UE-L1: BCCH: BCH Message [System info] + Node B-MAC->>UE-MAC: MAC-B-Data-IND [New system info] + UE-MAC->>UE-L1: CPHY-RL-Setup-REQ (Start TX) + UE-L1->>UE-RLC: RLC-TM-Data-REQ [Cell Update] + UE-RLC->>UE-MAC: MAC-C/SH-Data-REQ [Cell Update] + UE-MAC->>Node B-MAC: CCCH: RACH: CCCH Message [Cell Update] + Node B-MAC->>SRNC-RRC: + Note right of SRNC-RRC: Register change of cell + SRNC-RRC->>SRNC-RLC: RLC-TM-Data-REQ [Cell Update Confirm] + SRNC-RLC->>SRNC-MAC: MAC-D-Data-REQ [Cell Update Confirm] + SRNC-MAC->>CRNC-MAC: MAC-C/SH-Data-REQ [Cell Update Confirm] + CRNC-MAC->>Node B-MAC: DCCH: FACH: DCCH Message [Cell Update Confirm] + Node B-MAC->>UE-MAC: MAC-D-Data-IND [Cell Update Confirm] + UE-MAC->>UE-RLC: RLC-TM-Data-IND [Cell Update Confirm] + +``` + +Sequence diagram of the cell update procedure showing interactions between UE layers (RRC, RLC, MAC, L1) and network elements (Node B, RNC, CRNC, SRNC) across Uu, Iub, and Iur interfaces. + +Figure 26: Cell update procedure + +### 6.4.3 URA Update + +Figure 27 illustrates an example of a URA Update procedure. For a more detailed figure on the interlayer interaction for CCCH or DCCH transmission please refer to "Cell Update" in the previous subclause. + +When cell re-selection is triggered, the UE abandons the radio link in the old cell and establishes a radio link to the new cell. The URA update procedure is triggered when the UE reads the broadcast information of the new cell and recognises that a URA update is required. After that, the UE RRC layer sends a URA UPDATE on the CCCH to the UE MAC layer, which transfers the message on the RACH to UTRAN. The RACH transmission includes the current U-RNTI (S-RNTI and SRNC Identity). + +Upon reception of the URA UPDATE, the UTRAN registers the change of URA. Then the CRNC-RRC requests the CRNC-MAC to send a URA UPDATE CONFIRM message on the FACH to the UE. The message includes the current U-RNTI (S-RNTI and SRNC Identity) and may also include new C-RNTI, U-RNTI (S-RNTI and SRNC Identity). + +The logical channel used for URA UPDATE CONFIRM depends on the SRNC relocation policy. If SRNC is always relocated before URA UPDATE CONFIRM is sent, a DCCH should be used (to allow ciphering of the message contents). If SRNC is not relocated, the CCCH logical channel should be used to be able to utilize the RNSAP Iur procedures and not being forced to set up user plane on the Iur for this procedure. + +![Sequence diagram showing the beginning of the URA update procedure across Uu, Iub, and Iur interfaces.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The sequence diagram illustrates the initial steps of a URA update procedure. It is divided into three vertical sections representing different interfaces: Uu, Iub, and Iur, separated by vertical lines. A dashed line separates the Iub and Iur sections. + +- Uu Interface (UE side):** + - The process starts with a box labeled "URA reselection triggered" in the UE-RRC lifeline. + - UE-RRC sends a **CPHY-RL-Release-REQ (Stop RX and TX)** to UE-L1. + - UE-RRC sends a **CPHY-RL-Setup-REQ (Start RX)** to UE-L1. + - UE-L1 sends a **CPHY-Sync-IND** to UE-RRC. + - UE-L1 receives a **BCCH: BCH: BCCH Message [System info]** from Node B-MAC. + - Node B-MAC sends a **MAC-B-Data-IND [New system info]** to UE-RRC. + - UE-RRC sends a **CPHY-RL-Setup-REQ (Start TX)** to UE-L1. +- Iub Interface:** + - UE-L1 sends a **CCCH: RACH: URA UPDATE** message to CRNC-MAC. +- Iur Interface:** + - CRNC-MAC sends a message to SRNC-RRC. + - SRNC-RRC leads to a box labeled "Register change of URA". + - This is followed by a box labeled "Continue to A or B", indicating a choice between two cases. + +Sequence diagram showing the beginning of the URA update procedure across Uu, Iub, and Iur interfaces. + +Figure 27: Beginning of the URA update procedure – continue either to case A or case B + +#### **Case A: URA UPDATE CONFIRM on DCCH:** + +![Sequence diagram for Case A: URA UPDATE CONFIRM on DCCH. It shows the flow of a message from SRNC-RRC through CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to UE-RRC. The message is labeled 'DCCH: FACH: URA UPDATE CONFIRM'. The diagram is divided into three sections: Uu, Iub, and Iur.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +The diagram illustrates the protocol stack and message flow for Case A. It is divided into three vertical sections: Uu, Iub, and Iur. The Uu section contains UE-RRC, UE-MAC, and UE-L1. The Iub section contains RNC-L1. The Iur section contains CRNC-MAC and SRNC-RRC. A message labeled 'DCCH: FACH: URA UPDATE CONFIRM' is shown being transmitted from the SRNC-RRC in the Iur section, through the CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to the UE-RRC in the Uu section. Each protocol layer is represented by a box, and the message flow is indicated by a horizontal arrow with a vertical line pointing to the UE-RRC box. + +Sequence diagram for Case A: URA UPDATE CONFIRM on DCCH. It shows the flow of a message from SRNC-RRC through CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to UE-RRC. The message is labeled 'DCCH: FACH: URA UPDATE CONFIRM'. The diagram is divided into three sections: Uu, Iub, and Iur. + +**Figure 28: Case A continuation of URA update, CONFIRM message can be ciphered** + +#### **Case B: URA UPDATE CONFIRM on CCCH:** + +In this case transmission between SRNC and CRNC takes place on the RNSAP Downlink Signalling Transfer and the CCCH logical channel is used. + +![Sequence diagram for Case B: URA UPDATE CONFIRM on CCCH. It shows the flow of a message from SRNC-RRC through CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to UE-RRC. The message is labeled 'CCCH: FACH: URA UPDATE CONFIRM'. The diagram is divided into three sections: Uu, Iub, and Iur.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +The diagram illustrates the protocol stack and message flow for Case B. It is divided into three vertical sections: Uu, Iub, and Iur. The Uu section contains UE-RRC, UE-MAC, and UE-L1. The Iub section contains RNC-L1. The Iur section contains CRNC-MAC and SRNC-RRC. A message labeled 'CCCH: FACH: URA UPDATE CONFIRM' is shown being transmitted from the SRNC-RRC in the Iur section, through the CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to the UE-RRC in the Uu section. Each protocol layer is represented by a box, and the message flow is indicated by a horizontal arrow with a vertical line pointing to the UE-RRC box. + +Sequence diagram for Case B: URA UPDATE CONFIRM on CCCH. It shows the flow of a message from SRNC-RRC through CRNC-MAC, RNC-L1, UE-L1, UE-MAC, and finally to UE-RRC. The message is labeled 'CCCH: FACH: URA UPDATE CONFIRM'. The diagram is divided into three sections: Uu, Iub, and Iur. + +**Figure 29: Case B continuation of URA update, CONFIRM message cannot be ciphered** + +### 6.4.4 Radio Link Addition (FDD) + +![Sequence diagram for Radio Link Addition (FDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +The diagram illustrates the sequence of messages for Radio Link Addition (FDD) across two interfaces: Uu and Iub. The entities involved are UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC. The process begins with a 'Radio link addition triggered' event in the SRNC-RRC. The SRNC-RRC sends a CPHY-RL-Setup-REQ to the RNC-L1. The RNC-L1 then sends a CPHY-RL-Setup-REQ to the NodeB-L1. The NodeB-L1 performs 'Start RX and TX' and sends a CPHY-RL-Setup-CNF back to the RNC-L1. The RNC-L1 sends an ACTIVE SET UPDATE message to the UE-RRC. The UE-RRC sends a CPHY-RL-Setup-REQ to the UE-L1. The UE-L1 performs 'Start RX' and sends an ACTIVE SET UPDATE COMPLETE message to the SRNC-RRC. Finally, the UE-L1 sends a CPHY-RL-Setup-CNF back to the UE-RRC. + +``` +sequenceDiagram + participant SRNC-RRC + participant RNC-L1 + participant NodeB-L1 + participant UE-RRC + participant UE-L1 + + Note right of SRNC-RRC: Radio link addition triggered + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + RNC-L1->>NodeB-L1: CPHY-RL-Setup-REQ + Note right of NodeB-L1: Start RX and TX + NodeB-L1->>RNC-L1: CPHY-RL-Setup-CNF + RNC-L1->>UE-RRC: ACTIVE SET UPDATE + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + Note right of UE-L1: Start RX + UE-L1->>SRNC-RRC: ACTIVE SET UPDATE COMPLETE + UE-L1->>UE-RRC: CPHY-RL-Setup-CNF +``` + +Sequence diagram for Radio Link Addition (FDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces. + +**Figure 30: Radio Link Addition** + +Figure 30 illustrates a radio link addition procedure. Radio link addition is triggered in the network RRC layer by measurement reports sent by the UE. The NW RRC first configures the new radio link on the physical layer in Node B. Transmission and reception begins immediately. The NW RRC then sends an RRC ACTIVE SET UPDATE message to the UE RRC. The UE RRC configures layer 1 to begin reception. + +The UE shall send an ACTIVE SET UPDATE COMPLETE message to the RNC-RRC without waiting for an indication of synchronisation from the UE physical layer. + +### 6.4.5 Radio Link Removal (FDD) + +![Sequence diagram for Radio link removal (FDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +The diagram illustrates the sequence of messages for radio link removal (FDD) across the Uu and Iub interfaces. The participants are UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC. The process begins with a 'Radio link removal triggered' event in the SRNC-RRC. The SRNC-RRC sends an 'ACTIVE SET UPDATE' message to the UE-RRC. The UE-RRC sends a 'CPHY-RL-Release-REQ' message to the UE-L1. The UE-L1 performs a 'Stop RX' action. The UE-RRC sends an 'ACTIVE SET UPDATE COMPLETE' message to the SRNC-RRC. The SRNC-RRC sends a 'CPHY-RL-Release-REQ' message to the RNC-L1. The RNC-L1 sends a 'CPHY-RL-Release-REQ' message to the NodeB-L1. The NodeB-L1 performs a 'Stop RX and TX' action. The NodeB-L1 sends a 'CPHY-RL-Release-CNF' message to the RNC-L1. + +``` +sequenceDiagram + participant UE-RRC + participant UE-L1 + participant NodeB-L1 + participant RNC-L1 + participant SRNC-RRC + + Note right of SRNC-RRC: Radio link removal triggered + SRNC-RRC->>UE-RRC: ACTIVE SET UPDATE + UE-RRC->>UE-L1: CPHY-RL-Release-REQ + UE-L1: Stop RX + UE-RRC->>SRNC-RRC: ACTIVE SET UPDATE COMPLETE + SRNC-RRC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>NodeB-L1: CPHY-RL-Release-REQ + NodeB-L1: Stop RX and TX + NodeB-L1->>RNC-L1: CPHY-RL-Release-CNF +``` + +Sequence diagram for Radio link removal (FDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces. + +**Figure 31: Radio link removal** + +Figure 31 illustrates a radio link removal procedure. Radio link removal is triggered by an algorithm in the network RRC layer by measurement reports sent by the UE. Radio link removal may also be triggered in the NW due to load control algorithms. The radio link is first deactivated by the UE and then in the NW. + +The NW RRC sends an ACTIVE SET UPDATE message to the UE RRC. The UE RRC requests UE L1 to terminate reception of the radio link(s) to be removed. After this the UE RRC acknowledges radio link removal with an ACTIVE SET UPDATE COMPLETE message to the NW RRC. The NW RRC proceeds to request the NW L1 in both Node B and the RNC to release the radio link. + +### 6.4.6 Combined radio link addition and removal + +![Sequence diagram illustrating the Combined Radio Link Addition and Removal procedure. The diagram shows interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces. The process starts with a trigger in the SRNC-RRC, followed by CPHY-RL-Setup-REQ, Start rx/tx, CPHY-RL-Setup-CNF, ACTIVE SET UPDATE, CPHY-RL-Release-REQ, Stop rx, CPHY-RL-Setup-REQ, Start rx, ACTIVE SET UPDATE COMPLETE, CPHY-RL-Release-REQ, Stop rx/tx, CPHY-RL-Release-CNF, and CPHY-RL-Setup-REQ messages.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` + +sequenceDiagram + participant SRNC-RRC + participant RNC-L1 + participant NodeB-L1 + participant UE-L1 + participant UE-RRC + + Note right of SRNC-RRC: Radio link addition and removal triggered + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + RNC-L1->>NodeB-L1: Start rx / tx + NodeB-L1->>SRNC-RRC: CPHY-RL-Setup-CNF + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + RNC-L1->>UE-RRC: ACTIVE SET UPDATE + UE-RRC->>UE-L1: CPHY-RL-Release-REQ + UE-L1->>UE-RRC: Stop rx + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + UE-L1->>UE-RRC: Start rx + UE-RRC->>SRNC-RRC: ACTIVE SET UPDATE COMPLETE + SRNC-RRC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>NodeB-L1: Stop rx / tx + NodeB-L1->>SRNC-RRC: CPHY-RL-Release-CNF + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + +``` + +Sequence diagram illustrating the Combined Radio Link Addition and Removal procedure. The diagram shows interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC across Uu and Iub interfaces. The process starts with a trigger in the SRNC-RRC, followed by CPHY-RL-Setup-REQ, Start rx/tx, CPHY-RL-Setup-CNF, ACTIVE SET UPDATE, CPHY-RL-Release-REQ, Stop rx, CPHY-RL-Setup-REQ, Start rx, ACTIVE SET UPDATE COMPLETE, CPHY-RL-Release-REQ, Stop rx/tx, CPHY-RL-Release-CNF, and CPHY-RL-Setup-REQ messages. + +**Figure 32: Combined Radio Link Addition And Removal** + +Figure 32 illustrates a combined radio link addition and removal procedure. The NW RRC determines the need for radio link replacement based on received measurement reports or load control algorithms. + +When radio links are to be replaced, the NW RRC first configures the NW L1 to activate the radio link(s) that are being added. The NW RRC then sends an ACTIVE SET UPDATE message to the UE RRC, which configures the UE L1 to terminate reception on the removed radio link(s) and begin reception on the added radio link(s). + +If the UE active set is full, the replacement has to be performed in the order defined in figure 32. If UE has only one radio link, then the replacement must be done in reverse order (first add, then remove). + +The UE RRC acknowledges the replacement with an ACTIVE SET UPDATE COMPLETE message. The NW RRC then configures the NW L1 to terminate reception and transmission on the removed radio link. + +### 6.4.7 Hard Handover (FDD and TDD) + +![Sequence diagram of Hard Handover (FDD and TDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +The diagram illustrates the sequence of messages for a Hard Handover (FDD and TDD) across the Uu and Iub interfaces. The entities involved are UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC (via an Inter-handover block). + +``` + +sequenceDiagram + participant SRNC-RRC + participant RNC-L1 + participant NodeB-L1 + participant UE-L1 + participant UE-RRC + + Note right of SRNC-RRC: Inter-handover + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + RNC-L1->>NodeB-L1: Start new rx / tx + NodeB-L1->>RNC-L1: CPHY-RL-Setup-CNF + RNC-L1->>SRNC-RRC: CPHY-RL-Setup-REQ + SRNC-RRC->>UE-RRC: PHYSICAL CHANNEL RECONFIGURATION + UE-RRC->>UE-L1: CPHY-RL-Release-REQ + UE-L1->>UE-RRC: Stop rx / tx + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + UE-L1->>UE-RRC: Start rx / tx + UE-L1->>NodeB-L1: Layer 1 synchronisation + NodeB-L1->>UE-L1: CPHY-Sync-IND + Note over UE-L1, NodeB-L1: Layer 2 link established + UE-RRC->>SRNC-RRC: PHYSICAL CHANNEL RECONFIGURATION COMPLETE (acknowledged on L2) + SRNC-RRC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>NodeB-L1: Stop old rx / tx + NodeB-L1->>RNC-L1: CPHY-RL-Release-CNF + RNC-L1->>SRNC-RRC: CPHY-RL-Release-REQ + +``` + +Sequence diagram of Hard Handover (FDD and TDD) showing interactions between UE-RRC, UE-L1, NodeB-L1, RNC-L1, and SRNC-RRC. + +**Figure 33: Hard handover** + +Figure 33 illustrates a hard handover. The NW RRC determines the need for hard handover based on received measurement reports or load control algorithms. + +For inter-frequency handover the measurements are assumed to be performed in slotted mode. + +The NW RRC first configures the NW L1 to activate the new radio links. The NW L1 begins transmission and reception on the new links immediately. The NW RRC then sends the UE RRC a PHYSICAL CHANNEL RECONFIGURATION message (several other messages e.g. RADIO BEARER RECONFIGURATION and TRANSPORT CHANNEL RECONFIGURATION can also be used to perform hard handover). The message indicates the radio resources that should be used for the new radio link. The UE RRC configures the UE L1 to terminate reception on the old radio link and begin reception on the new radio link. + +After the UE L1 has achieved downlink synchronisation on the new frequency, a L2 link is established and the UE RRC sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the NW RRC. After having received the L3 acknowledgement, the NW RRC configures the NW L1 to terminate reception and transmission on the old radio link. + +### 6.4.8 SRNS Relocation + +The SRNS relocation procedure can be divided into two phases. The first phase is relocation preparation; where the resources are reserved, new RABs are established while the second phase is the transfer of the Serving RNS from source to target RNC. + +In what follows, lossless radio bearers are RBs using AM and configured to support lossless SRNS relocation. Seamless radio bearers are RBs using UM or AM not configured to support lossless SRNS relocation. + +There are three cases in which an SRNS relocation can be performed: + +- Serving SRNS relocation: This is used to move the UTRAN to CN connection point at the UTRAN side from the source SRNC to the target RNC. +- Combined Hard Handover and SRNS relocation: This is used to move the UTRAN to CN connection point at the UTRAN side from the source SRNC to the target RNC, while performing a hard handover decided by the UTRAN. +- Combined Cell/URA update and SRNS relocation: This is used to move the UTRAN to CN connection point at the UTRAN side from the source SRNC to the target RNC, while performing a cell re-selection in the UTRAN. + +and these are described in subclauses 6.4.8.1, 6.4.8.2 (for lossless radio bearers), 6.4.8.3, 6.4.8.4 (for seamless radio bearers), and in more detail in [6]. + +#### 6.4.8.1 Combined Cell/URA Update and SRNS relocation (lossless radio bearers) + +The procedure is initiated by the source RNC deciding to perform a SRNS relocation. The scenario below describes the SRNS Relocation of the type "UE not involved". In Case I the SRNS relocation is triggered by the UTRAN MOBILITY INFORMATION message. In Case II the SRNS relocation is triggered by the CELL UPDATE CONFIRM message. + +A RANAP Relocation Command is received by the source RNC from the CN, indicating the RABs to be released and the RABs that are subject to data forwarding. Lossless SRNS relocation is always, and only, configured for RABs that are subject to data forwarding. The PDCP layer shall support PDCP sequence numbering when lossless SRNS relocation is supported [7]. + +For the affected radio bearers, the RLC entity is stopped and the next PDCP sequence numbers are retrieved by RRC. The next PDCP send and receive sequence numbers are then transferred in the RNSAP Relocation Commit message from source to target RNC for RABs that support lossless SRNS relocation. The target RNC becomes the serving RNC when the RANAP Relocation Detect message is sent. + +The target RNC then sends on SRB#1 (UM/DCCH) a UTRAN MOBILITY INFORMATION (Case I) or a CELL/URA UPDATE CONFIRM (Case II); which configures the UE with the new U-RNTI and indicates the next uplink receive PDCP sequence number for each radio bearer configured to support lossless SRNS relocation. + +The target RNC establishes a UM RLC entity for SRB#1, and the DL HFN and the VT(US) are set to the values in the RRC information container, respectively. In the UM RLC entity, the "Special LI" is used to indicate that an RLC SDU begins in the beginning of an RLC PDU. + +Upon reception by the UE of the message, the UE compares the next uplink receive PDCP sequence number with the UE next uplink send PDCP sequence number. If this confirms PDCP SDUs successfully transferred before the start of relocation i.e. already received by the source RNC then these are discarded by the UE. The UE reinitialises the PDCP header compression entities of the radio bearers configured to use a header compression protocol [7]. The AM RLC entity for SRB#2 is (re-)established both on the UTRAN and UE sides, and their HFN values are set to the MAX(UL HFN of SRB2 | DL HFN of SRB2) incremented by one. + +If the UE has successfully configured itself, it shall send a UTRAN MOBILITY INFORMATION CONFIRM (Case I and Case II). These messages contain the START values and the next downlink receive PDCP sequence number for each radio bearer configured to support lossless SRNS relocation. + +Upon reception and acknowledgement by the UTRAN of the message, the UTRAN compares the next downlink receive PDCP sequence number with the next downlink send PDCP sequence number. The UTRAN initialises the PDCP header compression entities of the radio bearers configured to use a header compression protocol [7]. The RLC entities for affected radio bearers (other than SRB#2) are (re-)established both on the UTRAN and UE side. The HFN values for each RB are set to the START value in the message for the corresponding CN domain, and all the RLC data buffers are flushed. + +In case of failure, the UE shall send a UTRAN MOBILITY INFORMATION FAILURE (Case I and Case II). + +Upon reception of the UTRAN MOBILITY INFORMATION CONFIRM/FAILURE (Case I and Case II), the relocation procedure ends. + +![Sequence diagram for Combined Cell/URA Update and SRNS relocation (lossless radio bearers).](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +The diagram illustrates the interaction between a User Equipment (UE) and various Radio Network Controller (RNC) components during a combined Cell/URA update and SRNS relocation. The lifelines are divided into two groups: 'Uu lub' (UE-RRC, UE-PDCP, UE-RLC) and 'Iur / Iu' (target RNC-RLC, target RNC-PDCP, target RNC-RRC, target RNC, source RNC-RLC, source RNC-PDCP, source RNC-RRC, source RNC). The process begins with an RRC: CELL/URA UPDATE (Case II) from the UE. The source RNC makes a decision to perform SRNS relocation. A 'Relocation Preparation' phase follows, involving RNSAP: Relocation Commit and data forwarding. The target RNC sends CRLC-CONFIG-Req (Establish SRB1) to the UE. The UE responds with RRC: UTRAN MOBILITY INFORMATION (Case I) and CELL/URA UPDATE CONFIRM (Case II). The source RNC then sends RANAP: Relocation Detect to the new SGSN, which triggers a RANAP Relocation Commit. The target RNC continues configuration with CRLC-CONFIG-Req (Re-establish SRB2 and increment HFN) and CPDCP-RELOC-Req/Conf. The UE confirms with RRC: UTRAN MOBILITY INFORMATION CONFIRM. Finally, the target RNC sends CPDCP-SN-Req, CPDCP-CONFIG-Req (Initialisation), and CRLC-CONFIG-Req ((Re-)establish with START) to the UE, which responds with CRLC-CONFIG-Req (Re-establish with START). The source RNC sends RANAP: Relocation Complete to the new SGSN. + +``` + +sequenceDiagram + participant UE-RRC + participant UE-PDCP + participant UE-RLC + participant target_RNC_RLC as target RNC-RLC + participant target_RNC_PDCP as target RNC-PDCP + participant target_RNC_RRC as target RNC-RRC + participant target_RNC as target RNC + participant source_RNC_RLC as source RNC-RLC + participant source_RNC_PDCP as source RNC-PDCP + participant source_RNC_RRC as source RNC-RRC + participant source_RNC as source RNC + + Note over UE-RRC, UE-RLC: Uu lub + Note over target_RNC_RLC, target_RNC: Iur / Iu + + UE-RRC->>source_RNC_RRC: RRC: CELL/URA UPDATE (Case II) + source_RNC_RRC->>source_RNC: Decision to perform SRNS relocation (could be initiated by CELL/URA UPDATE from UE) + Note over target_RNC_RLC, source_RNC_RRC: Relocation Preparation + source_RNC_RLC->>source_RNC: CRLC-CONFIG-Req (Stop) + source_RNC_PDCP->>source_RNC_RLC: CPDCP-RELOC-Req + source_RNC_RLC->>source_RNC_PDCP: CPDCP-RELOC-Conf (Next_Send_SN, Next_Receive_SN) + target_RNC->>source_RNC: RNSAP: Relocation Commit + target_RNC->>source_RNC: Forwarding of Data + target_RNC->>source_RNC: RANAP: Relocation Detect (to new SGSN) + source_RNC->>external: RANAP: Relocation Detect (Triggered by RANAP Relocation Commit) + target_RNC->>UE-RLC: CRLC-CONFIG-Req (Establish SRB1) + UE-RRC->>target_RNC_RRC: RRC: UTRAN MOBILITY INFORMATION (Case I); CELL/URA UPDATE CONFIRM (Case II) (New U-RNTI, Next_Receive_SN) + UE-RLC->>UE-PDCP: CRLC-CONFIG-Req (Stop) + UE-PDCP->>UE-RLC: CPDCP-RELOC-Req (Next_Receive_SN) + UE-RLC->>UE-PDCP: CPDCP-RELOC-Conf (Next_Receive_SN) + UE-PDCP->>UE-RLC: CPDCP-CONFIG-Req (Re-initialisation) + UE-RLC->>UE-PDCP: CRLC-CONFIG-Req (Re-establish SRB2 and increment HFN) + target_RNC->>UE-RLC: CRLC-CONFIG-Req (Establish SRB2 and increment HFN) + UE-RRC->>target_RNC_RRC: RRC: UTRAN MOBILITY INFORMATION CONFIRM (Case I and Case II) (Next_Receive_SN, START) + target_RNC_PDCP->>target_RNC_RRC: CPDCP-SN-Req (PDCP_SN) + target_RNC_PDCP->>target_RNC_RRC: CPDCP-CONFIG-Req (Initialisation) + target_RNC->>UE-RLC: CRLC-CONFIG-Req ((Re-)establish with START) + UE-RLC->>UE-PDCP: CRLC-CONFIG-Req (Re-establish with START) + source_RNC->>external: RANAP: Relocation Complete (to new SGSN) + +``` + +Sequence diagram for Combined Cell/URA Update and SRNS relocation (lossless radio bearers). + +Figure 34: Combined Cell/URA Update and SRNS relocation (lossless radio bearers) + +#### 6.4.8.2 Combined Hard Handover and SRNS relocation (lossless radio bearers) + +Based on measurement results and knowledge of the UTRAN topology, the source SRNC decides to initiate a combined hard handover and SRNS relocation. The UE is still under control of the SRNC but is moving to a location controlled by the target RNC. The scenario below describes the SRNS Relocation of the type "UE involved". + +A RANAP Relocation Command is received by the source RNC from the CN, indicating the RABs to be released, the Target RNC to Source RNC Transparent Container and the RABs that are subject to data forwarding. Lossless SRNS relocation is always, and only, configured for RABs that are subject to data forwarding. The PDCP layer shall support PDCP sequence numbering when lossless SRNS relocation is supported [7]. The Target RNC to Source RNC Transparent Container includes the RRC message (e.g. PHYSICAL CHANNEL RECONFIGURATION) for hard handover. + +Upon reception of the RANAP Relocation Command, the RRC entity in the source RNC stops the RLC entities for the affected radio bearers and retrieves the PDCP sequence numbers. It then triggers the execution of the relocation of SRNS by sending the RRC message to the UE using the acknowledged mode dedicated signalling radio bearer (SRB #2). This message includes the new U-RNTI (from the target RNC) and the next uplink receive PDCP sequence number for each radio bearer configured to support lossless SRNS relocation (from the source RNC). The UE reinitialises the PDCP header compression entities of the radio bearers configured to use a header compression protocol [7]. + +The next PDCP send and receive sequence numbers are then transferred via the CN during the forwarding of SRNS contexts from source to target RNC. The target RNC becomes the serving RNC when the RANAP Relocation Detect message is sent. + +Upon reception and acknowledgment by the UE of the message, the RLC entity for the acknowledged mode dedicated signalling radio bearer (SRB #2) is re-established, both on the UTRAN and UE sides and their HFN values are set to the $\text{MAX}(\text{uplink HFN of RB2} \mid \text{downlink HFN of RB2}) + 1$ . Care should be taken by UTRAN in timing the SRNS relocation so that there is no risk of a SN rollover on SRB #2 during this procedure. + +The UE compares the next uplink receive PDCP sequence number with the next uplink send PDCP sequence number. If this confirms PDCP SDUs successfully transferred before the start of relocation i.e. already received by the source RNC then these are discarded by the UE. + +If the UE has successfully configured itself, it sends a response message, in this case a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the target RNC using the acknowledged mode dedicated signalling radio bearer (SRB #2). This message contains the START values and the next downlink receive PDCP sequence number for each radio bearer configured to support lossless SRNS relocation. + +Upon acknowledgement of the message, the RLC entities for affected radio bearers are re-established both on the UTRAN and UE side. The HFN values for each RB are set to the START value in the message for the corresponding CN domain. + +UTRAN compares the next downlink receive PDCP sequence number with the next downlink send PDCP sequence number. The UTRAN initialises the PDCP header compression entities of the radio bearers configured to use a header compression protocol [7]. + +The UTRAN and the UE continue the RLC and PDCP entities of the affected RBs and the relocation procedure ends. + +![Sequence diagram for Combined Hard Handover and SRNS relocation (lossless radio bearers).](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the signaling sequence for a combined hard handover and SRNS relocation. It involves the following entities and steps: + +- UE (User Equipment):** Contains sub-layers UE-RRC, UE-PDCP, and UE-RLC. It is labeled "UE involved" at the start. +- Source RNC (Radio Network Controller):** Contains sub-layers source RNC-RLC, source RNC-PDCP, source RNC-RRC, and source RNC. It initiates the relocation preparation. +- Target RNC:** Four instances are shown, each with sub-layers target RNC-RLC, target RNC-PDCP, target RNC-RRC, and target RNC. It receives the UE and completes the handover. +- SGSN (Serving GPRS Support Node):** Old and new SGSNs are involved in the RANAP signaling. +- Interfaces:** + - Uu:** Between UE and RNC. + - Iub:** Between UE-RLC and Source RNC-RLC. + - Iur / Iu:** Between Source RNC and Target RNC. + +**Sequence of Events:** + +- Decision to perform SRNS relocation:** Made by the source RNC. +- Relocation Preparation:** Source RNC sends **RANAP: Relocation Command (from old SGSN)** to the old SGSN, which then sends **CRLC-CONFIG-Req (Stop)** to the source RNC-RLC. +- Forwarding of SRNS contexts via the CN:** Source RNC sends **CPDCP-RELOC-Req (Next\_Receive\_SN)** to source RNC-PDCP, which sends **CPDCP-RELOC-Conf (Next\_Send\_SN, Next\_Receive\_SN)** to source RNC-RRC. +- RRc: PHYSICAL CHANNEL RECONFIGURATION:** Source RNC-RRC sends this message to UE-RRC with parameters (New U-RNTI, Next\_Receive\_SN). +- UE Response:** UE-RRC sends **CRLC-CONFIG-Req (Stop)** to UE-RLC, **CPDCP-RELOC-Req (Next\_Receive\_SN)** to UE-PDCP, and **CPDCP-RELOC-Conf (Next\_Receive\_SN)** back to UE-RRC. UE-PDCP then sends **CPDCP-CONFIG-Req (Re-initialisation)** to UE-PDCP and **CRLC-CONFIG-Req (Re-establish SRB2 and increment HFN)** to UE-RLC. +- Forwarding of Data:** Source RNC sends data to target RNC. +- UE detected by target RNC:** A dashed box indicates this detection point. +- RRc: PHYSICAL CHANNEL RECONFIGURATION COMPLETE:** Target RNC-RRC sends this message to UE-RRC with parameters (Next\_Receive\_SN, START). +- UE Finalization:** UE-RRC sends **CRLC-CONFIG-Req (Re-establish with START)** to UE-RLC. Target RNC-RLC sends **CRLC-CONFIG-Req (Establish with START)** to target RNC-PDCP, which sends **CPDCP-SN-Req (PDCP\_SN)** to target RNC-RRC, which then sends **CPDCP-CONFIG-Req (Initialisation)** to target RNC-PDCP. +- SGSN Updates:** Target RNC sends **RANAP: Relocation Detect (to new SGSN)** and **RANAP: Relocation Complete (to new SGSN)**. The new SGSN triggers the detection of the UE at the lower layers. + +Sequence diagram for Combined Hard Handover and SRNS relocation (lossless radio bearers). + +Figure 35: Combined Hard Handover and SRNS relocation (lossless radio bearers) + +#### 6.4.8.3 Combined Cell/URA Update and SRNS relocation (seamless radio bearers) + +The procedure is initiated by the source RNC deciding to perform a SRNS relocation. The scenario below describes the SRNS Relocation of the type "UE not involved". In Case I the SRNS relocation is triggered by the UTRAN MOBILITY INFORMATION message. In Case II the SRNS relocation is triggered by the CELL UPDATE CONFIRM message. + +A RANAP Relocation Command is received by the source RNC from the CN, indicating the RABs to be released. PDCP of the source RNC takes a snapshot of the header compression context on the radio bearers and header compression protocols configured to apply the context relocation [7] and transfers the context information to target RNC. The source RNC continues the downlink data transmission on radio bearers supporting seamless SRNS relocation until the target RNC becomes the serving RNC. The target RNC becomes the serving RNC when the RANAP Relocation Detect message is sent. + +The target RNC sends on SRB#1 (UM/DCCH) a UTRAN MOBILITY INFORMATION (Case I) or a CELL/URA UPDATE CONFIRM (Case II); which configures the UE with the new U-RNTI. + +The target RNC establishes a UM RLC entity for SRB#1, and the DL HFN and the VT(US) are set to the values in the RRC information container, respectively. In the UM RLC entity, the "Special LI" is used to indicate that an RLC SDU begins in the beginning of an RLC PDU. + +Upon reception by the UE of the message, the AM RLC entity for SRB#2 is (re-)established both on the UTRAN and UE sides, and their HFN values are set to the MAX(UL HFN of SRB2 | DL HFN of SRB2) incremented by one. + +If the UE has successfully configured itself, it shall send a UTRAN MOBILITY INFORMATION CONFIRM (Case I and Case II). These messages contain the START values (to be used in integrity protection and in ciphering on radio bearers using UM and AM RLC). + +Upon reception and acknowledgement by the UTRAN of the message, the UTRAN initialises and the UE reinitialises the PDCP header compression protocols of the radio bearers configured to use a header compression protocol without the context relocation [7]. For the radio bearers and header compression protocols applying context relocation, UTRAN initialises header compression protocols based on the context information received from the source RNC and UE continues header compression without re-initialisation. Further description of specific actions in UTRAN and UE in the case of context relocation is found in [7]. The RLC entities for affected radio bearers (other than SRB#2) are (re-)established both on the UTRAN and UE side. The HFN values for each RB are set to the START value in the message for the corresponding CN domain, and all the RLC data buffers are flushed. + +In case of failure, the UE shall send a UTRAN MOBILITY INFORMATION FAILURE (Case I and Case II). + +Upon reception of the UTRAN MOBILITY INFORMATION CONFIRM/FAILURE (Case I and Case II), the relocation procedure ends. + +![Sequence diagram for Combined Cell/URA Update and SRNS relocation (seamless radio bearers).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The diagram illustrates the interaction between a User Equipment (UE) and a Radio Network Controller (RNC) during a combined Cell/URA Update and SRNS relocation. The sequence is divided into two main parts by a vertical dashed line: 'Uu lub' on the left and 'Iur / Iu' on the right. + +**Participants:** + +- UE:** UE-RRC, UE-PDCP, UE-RLC +- target RNC:** target RNC-RLC, target RNC-PDCP, target RNC-RR, target RNC +- source RNC:** source RNC-RLC, source RNC-PDCP, source RNC-RR, source RNC + +**Sequence of Messages:** + +- RR: CELL/URA UPDATE (Case II)**: UE-RRC sends a message to source RNC-RR. +- Decision to perform SRNS relocation**: source RNC-RR makes a decision (could be initiated by CELL/URA UPDATE from UE). +- Relocation Preparation**: source RNC-RR sends a message to target RNC-RR. +- RANAP: Relocation Command (from old SGSN)**: source RNC-RR receives a command from the old SGSN. +- CPDCP-CONTEXT-Req**: source RNC-PDCP sends a request to target RNC-PDCP. +- CPDCP-CONTEXT-Conf (Context-Info)**: target RNC-PDCP sends a response to source RNC-PDCP. +- RNSAP: Relocation Commit**: source RNC-RLC sends a commit to target RNC-RLC. +- RANAP: Relocation Detect (to new SGSN)**: source RNC-RLC sends a detect message to the new SGSN (Triggered by RANAP Relocation Commit). +- CRLC-CONFIG-Req (Establish SRB1)**: target RNC-RLC sends a request to UE-RLC. +- RR: UTRAN MOBILITY INFORMATION (Case I); CELL/URA UPDATE CONFIRM (Case II) (New U-RNTI)**: UE-RRC sends a response to target RNC-RR. +- CRLC-CONFIG-Req (Re-establish SRB2 and increment HFN)**: target RNC-RLC sends a request to UE-RLC. +- RR: UTRAN MOBILITY INFORMATION CONFIRM (Case I and Case II) (START)**: UE-RRC sends a response to target RNC-RR. +- CPDCP-CONFIG-Req (Re-initialisation/Context relocation)**: target RNC-PDCP sends a request to UE-PDCP. +- CRLC-CONFIG-Req (Re-establish with START)**: target RNC-RLC sends a request to UE-RLC. +- RANAP: Relocation Complete (to new SGSN)**: source RNC-RLC sends a complete message to the new SGSN. +- CPDCP-CONFIG-Req (Initialisation/Context relocation, Context-Info)**: target RNC-PDCP sends a request to UE-PDCP. + +Sequence diagram for Combined Cell/URA Update and SRNS relocation (seamless radio bearers). + +Figure 36: Combined Cell/URA Update and SRNS relocation (seamless radio bearers) + +#### 6.4.8.4 Combined Hard Handover and SRNS relocation (seamless radio bearers) + +Based on measurement results and knowledge of the UTRAN topology, the source SRNC decides to initiate a combined hard handover and SRNS relocation. The UE is still under control of the SRNC but is moving to a location controlled by the target RNC. The scenario below describes the SRNS Relocation of the type "UE involved". + +The source RNC continues the downlink data transmission on radio bearers supporting seamless SRNS relocation until the target RNC becomes the serving RNC. The target RNC becomes the serving RNC when the RANAP Relocation Detect message is sent. + +A RANAP Relocation Command is received by the source RNC from the CN, indicating the RABs to be released. The Target RNC to Source RNC Transparent Container includes the RRC message (e.g. PHYSICAL CHANNEL RECONFIGURATION) for hard handover. This message includes the new U-RNTI. + +Upon reception of the RANAP Relocation Command, the source RNC triggers the execution of the relocation of SRNS by sending the RRC message to the UE using the acknowledged mode dedicated signalling radio bearer. Simultaneously PDCP of the source RNC takes a snapshot of the header compression contexts on each of those radio bearers and header compression protocols configured to apply the context relocation and transfers them to target RNC during the "forwarding of SRNS contexts via the CN" phase [7]. + +Upon reception and acknowledgment by the UE of the PHYSICAL CHANNEL RECONFIGURATION message, the RLC entity for the acknowledged mode dedicated signalling radio bearer (SRB #2) is re-established, both on the UTRAN (target SRNC) and UE sides, and their HFN values are set to $\text{MAX}(\text{uplink HFN of RB2} \mid \text{downlink HFN of RB2}) + 1$ . Care should be taken by UTRAN in timing the SRNS relocation so that there is no risk of a SN rollover on SRB #2 during this procedure. + +If the UE has successfully configured itself, it sends a response message, in this case PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the target RNC using the acknowledged mode dedicated signalling radio bearer (SRB #2). This message is transmitted based on the new RLC context and contains the START values (to be used in integrity protection and in ciphering on radio bearers using UM and AM RLC). The UTRAN initialises and the UE reinitialises the PDCP header compression protocols of the radio bearers configured to use a header compression protocol without the context relocation [7]. For those radio bearers and header compression protocols applying context relocation, UTRAN initialises header compression protocols based on the context information received from the source RNC and UE continues header compression without re-initialisation. Further description of specific actions in UTRAN and UE in the case of context relocation is found in [7]. + +Upon acknowledgement of the message, the RLC entities for the rest of the affected radio bearers are re-established both on the UTRAN and UE side. The HFN values for each RB are set to the START value in the message for the corresponding CN domain. The HFN values for each remaining signalling radio bearer (other than SRB #2) are set to the START value in the message for the last configured CN domain. + +The relocation procedure ends. + +![Sequence diagram for Combined Hard Handover and SRNS relocation (seamless radio bearers).](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The diagram illustrates the signaling sequence for a combined hard handover and SRNS relocation. It features lifelines for the UE (UE-RRC, UE-PDCP, UE-RLC), target RNC (target RNC-RLC, target RNC-PDCP, target RNC-RRC, target RNC), and source RNC (source RNC-RLC, source RNC-PDCP, source RNC-RRC, source RNC). The process begins with a 'Decision to perform SRNS relocation' in the source RNC, triggered by a 'RANAP: Relocation Command' from the old SGSN. This is followed by 'Relocation Preparation' and context transfer ('CPDCP-CONTEXT-Req', 'CPDCP-CONTEXT-Conf (Context-Info)'). The source RNC sends an 'RRc: PHYSICAL CHANNEL RECONFIGURATION on AM RLC' to the UE, providing a 'New U-RNTI'. Simultaneously, SRNS contexts are forwarded via the CN. The UE re-establishes SRB 2 and increments the HFN ('CRLC-CONFIG-Req (Re-establish SRB 2 and increment HFN)'). Upon detection by the target RNC, a 'RANAP: Relocation Detect' is sent to the new SGSN. The UE completes the reconfiguration ('RRc: PHYSICAL CHANNEL RECONFIGURATION COMPLETE on AM RLC (with START value)'), and the target RNC initiates context relocation ('CPDCP-CONFIG-Req (Initialisation/Context relocation, Context-Info)') and re-establishes SRB 2 with the START value ('CRLC-CONFIG-Req (Establish with START)'). Finally, a 'RANAP: Relocation Complete' is sent to the new SGSN, triggered by UE detection from lower layers. The UE performs final re-initialisation ('CPDCP-CONFIG-Req (Re-initialisation/Context relocation)') and re-establishes SRB 2 with START ('CRLC-CONFIG-Req (Re-establish with START)'). + +``` + +sequenceDiagram + participant UE as UE + participant TargetRNC as target RNC + participant SourceRNC as source RNC + participant CN as CN + participant SGSN as SGSN + + Note right of SourceRNC: Decision to perform SRNS relocation + SourceRNC->>SGSN: RANAP: Relocation Command (from old SGSN) + Note left of SourceRNC: Relocation Preparation + SourceRNC->>TargetRNC: CPDCP-CONTEXT-Req + TargetRNC->>SourceRNC: CPDCP-CONTEXT-Conf (Context-Info) + SourceRNC->>UE: RRc: PHYSICAL CHANNEL RECONFIGURATION on AM RLC (New U-RNTI) + Note left of TargetRNC: Forwarding of SRNS contexts via the CN + TargetRNC->>SourceRNC: CRLC-CONFIG-Req (Establish SRB 2 and increment HFN) + Note right of UE: UE detected by target RNC + TargetRNC->>SGSN: RANAP: Relocation Detect (to new SGSN) + UE->>TargetRNC: RRc: PHYSICAL CHANNEL RECONFIGURATION COMPLETE on AM RLC (with START value) + TargetRNC->>SGSN: RANAP: Relocation Complete (to new SGSN) + Note right of SGSN: (Triggered by detection of the UE as indicated from the lower layers) + UE->>TargetRNC: CRLC-CONFIG-Req (Re-establish SRB 2 and increment HFN) + TargetRNC->>UE: CPDCP-CONFIG-Req (Initialisation/Context relocation, Context-Info) + TargetRNC->>UE: CRLC-CONFIG-Req (Establish with START) + UE->>TargetRNC: CPDCP-CONFIG-Req (Re-initialisation/Context relocation) + UE->>TargetRNC: CRLC-CONFIG-Req (Re-establish with START) + +``` + +Sequence diagram for Combined Hard Handover and SRNS relocation (seamless radio bearers). + +Figure 37: Combined Hard Handover and SRNS relocation (seamless radio bearers) + +### 6.4.9 RRC Connection re-establishment + +![Sequence diagram for RRC connection re-establishment showing interactions between UE layers (RRC, RLC, MAC, L1) and network layers (NodeB-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC) over Uu and Iub interfaces.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +The sequence diagram illustrates the RRC connection re-establishment process. It begins with the UE-RRC sending a CCCH: CELL UPDATE message. The SRNC-RRC responds with a CPHY-RL-Setup-REQ to the NodeB-L1, which replies with CPHY-RL-Setup-CNF. The SRNC-RRC then sends another CPHY-RL-Setup-REQ to the RNC-L1. The NodeB-L1 sends a CCCH: CELL UPDATE CONFIRM to the UE-RRC. The UE-RRC sends a CPHY-RL-Setup-REQ to the UE-L1, which performs 'Start rx / tx' and 'L1 synchronisation'. The NodeB-L1 sends a CPHY-Sync-IND to the UE-L1, which in turn sends a CPHY-Sync-IND to the UE-MAC. The SRNC-RRC sends CMAC-C/SH-Config-REQ to the CRNC-MAC, which sends CMAC-C/SH-Config-REQ to the SRNC-MAC. The SRNC-MAC sends CMAC-D-Config-REQ to the SRNC-RLC, which sends CRLC-Config-REQ to the SRNC-RRC. Finally, the SRNC-RRC sends CCCH: PHYSICAL CHANNEL RECONFIGURATION COMPLETE to the UE-RRC. The UE-RRC then sends CMAC-C / SH / D-Config-REQ to the UE-MAC, which sends CRLC-configure-REQ to the UE-RLC. + +``` +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant NodeB-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + + Note over UE-RRC, UE-L1: Uu + Note over NodeB-L1, SRNC-RRC: Iub + + UE-RRC->>SRNC-RRC: CCCH: CELL UPDATE + SRNC-RRC->>NodeB-L1: CPHY-RL-Setup-REQ + NodeB-L1-->>SRNC-RRC: CPHY-RL-Setup-CNF + SRNC-RRC->>RNC-L1: CPHY-RL-Setup-REQ + NodeB-L1->>UE-RRC: CCCH: CELL UPDATE CONFIRM + UE-RRC->>UE-L1: CPHY-RL-Setup-REQ + Note over UE-L1: Start rx / tx + Note over UE-L1: L1 synchronisation + NodeB-L1->>UE-L1: CPHY-Sync-IND + UE-L1->>UE-MAC: CPHY-Sync-IND + SRNC-RRC->>CRNC-MAC: CMAC-C/SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-C/SH-Config-REQ + SRNC-MAC->>SRNC-RLC: CMAC-D-Config-REQ + SRNC-RLC->>SRNC-RRC: CRLC-Config-REQ + SRNC-RRC->>UE-RRC: CCCH: PHYSICAL CHANNEL RECONFIGURATION COMPLETE + UE-RRC->>UE-MAC: CMAC-C / SH / D-Config-REQ + UE-MAC->>UE-RLC: CRLC-configure-REQ +``` + +Sequence diagram for RRC connection re-establishment showing interactions between UE layers (RRC, RLC, MAC, L1) and network layers (NodeB-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC) over Uu and Iub interfaces. + +Figure 38: RRC connection re-establishment + +Figure 38 shows an example of the procedure when a UE loses radio connection due to e.g. radio link failure. After having selected a new cell, the UE RRC sends the NW RRC a CELL UPDATE message. The CELL UPDATE message contains information to the network that it was sent due to a radio link failure. The NW RRC configures the NW and acknowledges the connection re-establishment to the UE RRC with a CELL UPDATE CONFIRM message. The UE RRC configures the UE L1 to activate the new radio link(s). After the UE has synchronised to at least one radio link, the MAC and RLC layers can be configured (if necessary). + +When the procedure is completed on the UE side, a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message is sent. + +### 6.4.10 Inter-system Handover: GSM/BSS to UTRAN + +The handover from GSM/BSS to UTRAN for a dual-mode GSM MS / UMTS UE is illustrated in figure 39. On the network side, upon the reception of a HARD HANDOVER PROCEED 2 command through the RANAP protocol, the RRC layer performs admission control and radio resource allocation assigning an RNTI for the RRC connection and selecting radio resource parameters (such as transport channel type, transport format sets, etc). RRC configures these parameters on layer 1 and layer 2 to locally establish the DCH logical channel. + +The selected parameters including the RNTI, were previously transmitted to UE via RANAP message HARD HANDOVER PROCEED 1 and GSM upgraded message HANDOVER COMMAND. + +Upon reception of the HANDOVER COMMAND message, the GSM RR layer transmits the required parameters to the UMTS RRC layer using an RR-Data-IND primitive. UE RRC configures L1 and L2 using these parameters to locally establish the DCH logical channel. Layer 1 indicates to RRC when it has reached synchronisation. An RLC signalling link establishment is then initiated by the UE. A HANDOVER COMPLETE message is finally sent by the UE. + +. + +Error! No + +62 + +Error! No text of specified style in + +![Sequence diagram for GSM to UMTS inter-system handover. Lifelines include MS-RR, UE-RR, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC, CN/AS, and BSC-RR. The process involves RANAP signaling, CPHY and CMAC configuration, L1 synchronization, and L2 link establishment across GSM Mode, Transition state, and Cell connected state.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +The sequence diagram illustrates the inter-system handover from GSM to UMTS. It begins with the BSC-RR sending a RANAP: HARD HANDOVER PROCEED 2 message to the SRNC-RRC. The SRNC-RRC triggers internal processes in the CN/AS (Inter-network message exchange) and SRNC-RRC (Admission control & Radio Resource Allocation). The SRNC-RRC then sends a CPHY-RL-Setup-REQ to the Node B-L1, which responds with Start tx / rx and CPHY-RL-Setup-CNF. The SRNC-RRC continues configuration via CPHY-RL-Setup-REQ to RNC-L1, CMAC-D-Config-REQ to SRNC-MAC, and CMAC-C/SH-Config-REQ to CRNC-MAC. The RNC-L1 sends a HANDOVER COMMAND to the UE-L1. In the GSM Mode, the MS-RR sends an RR-Data-IND [Handover Command] to the UE-RR, which then sends CPHY-RL-Setup-REQ and CMAC-C / SH / D-Config-REQ to the UE-L1. The UE-L1 performs L1 synchronisation and sends CPHY-Sync-IND to the UE-RR and Node B-L1. In the Transition state, the UE-RR sends a CRLC-Config-REQ to the UE-RLC, and the SRNC-RRC sends a CRLC-Config-REQ to the SRNC-RLC. A common L2 Link Establishment phase follows. In the Cell connected state, the UE-RLC sends an RLC-Data-REQ [Handover Complete] to the UE-RR, which receives an RLC-Data-CNF. Simultaneously, the SRNC-RLC sends DCCH: Acknowledged Data [Handover Complete] and DCCH: Data Ack to the Node B-L1, which then sends an RLC-Data-IND [Handover Complete] to the SRNC-RRC. Finally, the SRNC-RRC sends a RANAP: HARD HANDOVER COMPLETE message to the CN/AS. + +Sequence diagram for GSM to UMTS inter-system handover. Lifelines include MS-RR, UE-RR, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC, CN/AS, and BSC-RR. The process involves RANAP signaling, CPHY and CMAC configuration, L1 synchronization, and L2 link establishment across GSM Mode, Transition state, and Cell connected state. + +Figure 39: GSM to UMTS inter-system handover + +### 6.4.11 Inter-RAT Handover: UTRAN to GSM/BSS, CS domain services + +![Sequence diagram for UTRAN to GSM inter-RAT handover. Lifelines include MS-RR, UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC, CN/AS, and BSC-RR. The process involves RANAP signaling between SRNC-RRC and CN/AS, followed by internal RRC and RLC configuration and release messages within the UE and SRNC, and finally physical information exchange and completion signaling between the BSC-RR and the UE's lower layers.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant MS-RR + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant CRNC-MAC + participant SRNC-MAC + participant SRNC-RLC + participant SRNC-RRC + participant CN/AS + participant BSC-RR + + Note left of MS-RR: UTRA RRC Connected Mode + SRNC-RRC->>CN/AS: RANAP: RELOCATION REQUIRED + CN/AS->>BSC-RR: HANDOVER REQUEST + BSC-RR->>CN/AS: HANDOVER REQUEST ACK + CN/AS->>SRNC-RRC: RANAP: RELOCATION COMMAND + SRNC-RRC->>UE-RRC: HANDOVER FROM UTRAN COMMAND (acknowledged on L2) + UE-RRC->>MS-RR: [GSM-RR message] + Note left of MS-RR: ----- + Note left of MS-RR: Transition state + MS-RR->>UE-RRC: [Release] + UE-RRC->>UE-RLC: CRLC-Config-REQ + UE-RLC->>UE-MAC: CMAC-C / SH / D-Config-REQ + UE-MAC->>UE-L1: CPHY-RL-Release-REQ + UE-L1->>Node B-L1: HANDOVER ACCESS + Node B-L1->>RNC-L1: PHYSICAL INFORMATION (unacknowledged) + RNC-L1->>BSC-RR: HANDOVER COMPLETE + BSC-RR->>CN/AS: HANDOVER COMPLETE + Note left of MS-RR: ----- + Note left of MS-RR: GSM Connected Mode + CN/AS->>SRNC-RRC: RANAP: IU RELEASE COMMAND + SRNC-RRC->>SRNC-RLC: CRLC-configureure-REQ + SRNC-RLC->>CRNC-MAC: CMAC-C/SH-Config-REQ + CRNC-MAC->>SRNC-MAC: CMAC-D-Config-REQ + SRNC-MAC->>RNC-L1: CPHY-RL-Release-REQ + RNC-L1->>Node B-L1: CPHY-RL-Release-REQ + Node B-L1->>SRNC-RRC: RANAP: IU RELEASE COMPLETE + +``` + +Sequence diagram for UTRAN to GSM inter-RAT handover. Lifelines include MS-RR, UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, CRNC-MAC, SRNC-MAC, SRNC-RLC, SRNC-RRC, CN/AS, and BSC-RR. The process involves RANAP signaling between SRNC-RRC and CN/AS, followed by internal RRC and RLC configuration and release messages within the UE and SRNC, and finally physical information exchange and completion signaling between the BSC-RR and the UE's lower layers. + +Figure 40: UTRAN to GSM inter-RAT handover + +NOTE: The scope of this description is restricted to a UE having a connection only to CS domain services, i.e. no simultaneous PS signalling connection. + +For CS domain services UTRAN to GSM inter-RAT Handover procedure is based on measurement reports from the UE but initiated from the UTRAN. HANDOVER FROM UTRAN COMMAND is sent using acknowledged data transfer on the DCCH. The UE transition from UTRAN Connected Mode starts when an HANDOVER FROM UTRAN COMMAND is received. The transition to GSM Connected mode is finished when HANDOVER COMPLETE message is sent from the UE. + +UTRAN sends a RELOCATION REQUIRED to CN/AS. This message contains information needed for the GSM system to be able to perform a handover (e.g. serving cell, target cell). Some parts of this information (e.g. MS classmark) have been obtained at setup of the RRC Connection and are stored in CN. + +The CN/AS sends a HANDOVER REQUEST message to BSC-RR allocating the necessary resources to be able to receive the GSM MS and acknowledge this by sending HANDOVER REQUEST ACKNOWLEDGE to CN/AS. The HANDOVER REQUEST ACKNOWLEDGE contains a GSM-RR message with all radio-related information that the UE needs for the handover. + +CN/AS sends a RELOCATION COMMAND (type UTRAN-to-BSS HARD HANDOVER) to the UTRAN to start the execution of the handover. This message contains a GSM-RR message with all the information needed for the UE to be able to switch to the GSM cell and perform a handover to GSM. + +Upon reception of the HANDOVER FROM UTRAN COMMAND message in the UE, the UE-RRC entity forwards the GSM-RR message to the MS-RR entity. To release the UTRA resources the MS-RR entity requests the UE-RRC entity to release the RRC connection locally. The UE-RRC entity can then locally release the resources on the RLC, MAC and physical layers of the UE. + +After having switched to the assigned GSM channel received in the HANDOVER FROM UTRAN COMMAND, the GSM MS sends HANDOVER ACCESS in successive layer 1 frames, just as it typically would have done for a conventional GSM handover initiation. + +When the BSC-RR has received the HANDOVER ACCESS it indicates this to the CN/AS by sending a HANDOVER DETECT message. The BSC-RR sends a PHYSICAL INFORMATION message to the GSM MS in unacknowledged mode that contains various fields of physical layer-related information allowing a proper transmission by the MS. + +After layer 1 and 2 connections are successfully established, the GSM MS returns the HANDOVER COMPLETE message. + +CN/AS is then able to release the UTRAN resources that were used for the UE in UTRAN Connected Mode. The CN/AS send a IU RELEASE COMMAND to UTRAN, after which UTRAN can release all NW resources from RLC, MAC and the physical layer. When the release operation is complete, a IU RELEASE COMPLETE message is sent to CN / AS. + +## 6.5 CN originated paging request in connected mode + +### 6.5.1 UTRAN coordinated paging using DCCH + +![Sequence diagram showing UTRAN coordinated paging using DCCH. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, RNC-MAC, RNC-RLC, RNC-RRC. The sequence starts with RNC-RRC sending an RRC Paging request to RNC-RLC, which then sends an RLC-Data-REQ to RNC-MAC. RNC-MAC sends a [PAGING TYPE 2 (UE Paging id)] to RNC-L1, which is transmitted via Node B-L1 over the DCCH (DCH: Acknowledged Data) to UE-L1. UE-L1 passes it through MAC and RLC layers, resulting in an RLC-Data-IND at UE-RLC with the same [PAGING TYPE 2] indicator. Finally, UE-RLC sends an RRC Notification indication (UE Paging Id) to UE-RRC.](742a5484e7dd016256ab99921bbd635d_img.jpg) + +``` +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-L1 + participant Node B-L1 + participant RNC-L1 + participant RNC-MAC + participant RNC-RLC + participant RNC-RRC + + Note right of RNC-RRC: RRC Paging request +(UE Paging Id, Area, +Paging Group Calc +Info) + RNC-RRC->>RNC-RLC: RLC-Data-REQ + RNC-RLC->>RNC-MAC: [PAGING TYPE 2 (UE Paging id)] + RNC-MAC->>RNC-L1: [PAGING TYPE 2 (UE Paging id)] + RNC-L1->>Node B-L1: DCCH: DCH: Acknowledged Data + Note right of Node B-L1: [PAGING TYPE 2] + Node B-L1->>UE-L1: DCCH: DCH: Acknowledged Data + Note right of UE-L1: [PAGING TYPE 2] + UE-L1->>UE-MAC: + UE-MAC->>UE-RLC: RLC-Data-IND + Note right of UE-RLC: [PAGING TYPE 2 (UE Paging id)] + UE-RLC->>UE-RRC: RRC Notification indication (UE Paging Id) +``` + +Sequence diagram showing UTRAN coordinated paging using DCCH. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, RNC-L1, RNC-MAC, RNC-RLC, RNC-RRC. The sequence starts with RNC-RRC sending an RRC Paging request to RNC-RLC, which then sends an RLC-Data-REQ to RNC-MAC. RNC-MAC sends a [PAGING TYPE 2 (UE Paging id)] to RNC-L1, which is transmitted via Node B-L1 over the DCCH (DCH: Acknowledged Data) to UE-L1. UE-L1 passes it through MAC and RLC layers, resulting in an RLC-Data-IND at UE-RLC with the same [PAGING TYPE 2] indicator. Finally, UE-RLC sends an RRC Notification indication (UE Paging Id) to UE-RRC. + +Figure 41: Example sequence of CN initiated paging request using DCCH + +The above sequence illustrates a CN originated paging request, when the UE is in connected mode and can be reached on the DCCH. The coordination of the paging request with the existing RRC connection is done in UTRAN. + +The entity above RRC on the network side requests paging of a UE over the Nt-SAP. The request contains a UE paging identity, an area where the page request is to be broadcast, information for calculation of the paging group. + +Since the UE can be reached on the DCCH, the RRC layer formats a PAGING TYPE 2 message containing the UE paging identity, and the message is transmitted directly to the UE using unacknowledged data transfer. + +## 6.6 UTRAN originated paging request and paging response + +![Sequence diagram for UTRAN originated paging request and paging response. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, CRNC-MAC, CRNC-RLC, CRNC-RRC, SRNC-RRC. The sequence shows the flow of messages from the CRNC-RRC down to the UE and back up through the layers and interfaces (Uu, Iub, Iur).](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +``` +sequenceDiagram + participant CRNC-RRC + participant SRNC-RRC + participant CRNC-RLC + participant CRNC-MAC + participant Node B-L1 + participant UE-L1 + participant UE-MAC + participant UE-RLC + participant UE-RRC + + Note right of CRNC-RRC: Trigger UTRAN originated paging + CRNC-RRC->>CRNC-MAC: PCCH: MAC-Data-REQ [PAGING TYPE 1 (UTRAN UE id, paging group)] + CRNC-MAC->>Node B-L1: PCH: Transparent mode Data [PAGING TYPE 1 (UTRAN UE id)] + Node B-L1->>UE-L1: CELL UPDATE (Unacknowledged on L2) + UE-L1->>UE-MAC: PCCH: MAC-Data-IND [PAGING TYPE 1 (UTRAN UE id)] + UE-MAC->>UE-RLC: CELL UPDATE CONFIRM (Unacknowledged on L2) + UE-RLC->>UE-RRC: UTRAN MOBILITY INFORMATION CONFIRM (Acknowledged on L2) +``` + +Sequence diagram for UTRAN originated paging request and paging response. Lifelines: UE-RRC, UE-RLC, UE-MAC, UE-L1, Node B-L1, CRNC-MAC, CRNC-RLC, CRNC-RRC, SRNC-RRC. The sequence shows the flow of messages from the CRNC-RRC down to the UE and back up through the layers and interfaces (Uu, Iub, Iur). + +Figure 42: Example sequence for UTRAN initiated paging request with paging response + +The RRC layer in the network uses this sequence to trigger a switch to CELL\_FACH state, when the UE can only be reached on the PCH (the CELL\_PCH state or the URA\_PCH state). A Paging Type 1 message is prepared, containing the UTRAN UE identity (s-RNTI + RNC-ID). The RRC requests the transmission of the message by MAC on the PCCH, indicating the paging group. + +In the UE, the RRC layer continuously monitors the paging group on the PCH and compares the UE identities in received paging request messages with its own identities. A match occurs, and in this case the RRC layer changes state to CELL\_FACH state. + +The UE prepares a Cell Update message, which is sent on CCCH. + +When the network receives the Cell Update message, a c-RNTI is allocated and signalled to UE using the Cell Update Confirm message, which is sent on DCCH using unacknowledged mode. The latter message also acknowledges the reception of the Cell Update message. The UE configures MAC to use the new c-RNTI and prepares a UTRAN MOBILITY INFORMATION CONFIRM message. When the network receives the UTRAN MOBILITY INFORMATION CONFIRM message on DCCH it can delete any old c-RNTI and the DCCH/DTCH logical channels can be used also in the downlink using the new c-RNTI. + +## 6.7 Other procedures + +### 6.7.1 UE Capability Information + +![Sequence diagram for UE Capability Information procedure. The diagram shows the interaction between UE-RRC, UE-RLC, RNC-RLC, and RNC-RRC layers across Uu and Iub interfaces. The process starts with 'Sending of UE capability triggered' in the UE. The UE sends 'DCCH: UE CAPABILITY INFORMATION (acknowledged)' to the RNC-RRC. The RNC-RRC responds with 'DCCH: UE CAPABILITY INFORMATION CONFIRM (acknowledged)' back to the UE. A horizontal bar labeled 'RRc connected mode' spans the duration of the exchange.](f796c4b6ef101faa39b887a86820c3d1_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant RNC-RLC + participant RNC-RRC + Note left of UE-RRC: Sending of UE capability triggered + UE-RRC->>RNC-RRC: DCCH: UE CAPABILITY INFORMATION (acknowledged) + RNC-RRC-->>UE-RRC: DCCH: UE CAPABILITY INFORMATION CONFIRM (acknowledged) + +``` + +Sequence diagram for UE Capability Information procedure. The diagram shows the interaction between UE-RRC, UE-RLC, RNC-RLC, and RNC-RRC layers across Uu and Iub interfaces. The process starts with 'Sending of UE capability triggered' in the UE. The UE sends 'DCCH: UE CAPABILITY INFORMATION (acknowledged)' to the RNC-RRC. The RNC-RRC responds with 'DCCH: UE CAPABILITY INFORMATION CONFIRM (acknowledged)' back to the UE. A horizontal bar labeled 'RRc connected mode' spans the duration of the exchange. + +Figure 43: UE Capability Information + +The UE transfers its capability information to the network by transmitting the RRC message UE Capability Information using acknowledged mode on the DCCH. UTRAN confirms the reception of the UE capabilities by transmitting an UE CAPABILITY INFORMATION CONFIRM message using acknowledged mode on the DCCH. This procedure is performed during the lifetime of the RRC Connection if the UE capability information changes (e.g. due to change in UE power class). UE capability information can also explicitly be requested by UTRAN. + +### 6.7.2 Random access transmission sequence (FDD) + +![Sequence diagram of Random access transmission sequence (FDD) showing interactions between UE layers (RR, RL, MAC, PHY) and Node B layers (PHY, MAC) over Uu and Iub interfaces.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +``` + +sequenceDiagram + participant UE-RRC + participant UE-RLC + participant UE-MAC + participant UE-PHY + participant Node B-PHY + participant RNC-MAC + + Note right of UE-PHY: Uu + Note right of Node B-PHY: Iub + + UE-RRC->>UE-PHY: CPHY-TrCH-Config-REQ + UE-RRC->>UE-MAC: CMAC-Config-REQ + UE-RLC->>UE-MAC: MAC-Data-REQ + Note right of UE-MAC: Initial backoff time + UE-MAC->>UE-PHY: PHY-Access-REQ [Access Service Class,..] + Note right of UE-PHY: Preamble transmission with power ramping + UE-PHY->>Node B-PHY: AICH "Nack" + Note right of Node B-PHY: Nack may be sent or not + Note right of UE-PHY: Condition + Note right of UE-MAC: subsequent backoff time + UE-MAC->>UE-PHY: PHY-Access-REQ [Access Service Class,..] + Note right of UE-MAC: Increment preamble retransmission cycle counter + Note right of UE-PHY: Preamble transmission with power ramping + UE-PHY->>Node B-PHY: AICH "ack" + UE-MAC->>UE-PHY: PHY-Access-CNF + UE-MAC->>UE-PHY: PHY-Data-REQ + Note right of UE-PHY: RACH Data + Note right of Node B-PHY: MAC-Data-IND + Note right of RNC-MAC: Evaluation of the MAC header + +``` + +Sequence diagram of Random access transmission sequence (FDD) showing interactions between UE layers (RR, RL, MAC, PHY) and Node B layers (PHY, MAC) over Uu and Iub interfaces. + +**Figure 44: Random access transmission sequence (FDD)** + +The RACH and AICH are configured once via a CPHY-TrCH-Config-REQ primitive. This primitive is issued only for initial configuration or when a parameter shall be changed, not for every RACH transmission. + +The CMAC-Config-REQ primitive is used to configure MAC parameters required for the random access procedure (e.g. persistence value, maximum number of preamble ramping cycles, initial and subsequent backoff times). + +When there is data to be transmitted on the RACH, i.e. reception of a MAC-Data-REQ primitive, the RACH transmission control procedure is started, which includes selection of Access Service Class (ASC). + +After some initial backoff, a primitive PHY-Access-REQ containing the selected ASC is sent to L1. This triggers the PRACH preamble transmission procedure, i.e. the physical layer selects a PRACH access slot and signature without further backoff delay imposed on L1, but within the constraints of the selected ASC. + +If the maximum permitted transmission power was reached without receiving an acknowledgement, or a negative acknowledgement (Nack) has been received on AICH, the preamble ramping cycle is repeated. The number of preamble ramping cycles is counted in MAC. + +Upon successful transmission of a preamble, MAC receives an acknowledgement via PHY-Access-CNF primitive that the acquisition indicator was received. Then message transmission is requested with the PHY-Data-REQ primitive. + +### 6.7.3 Random access transmission sequence (TDD) + +#### 6.7.3.1 Random access transmission sequence (3.84 Mcps TDD) + +![Sequence diagram of Random access transmission sequence (3.84 Mcps TDD)](9b9262a549828579ab904148450734f6_img.jpg) + +The diagram illustrates the interaction between UE-RRC, UE-MAC, UE-PHY, Node B-PHY, RNC-MAC, and RNC-RRC for random access transmission. The process is divided into two attempts separated by a collision. + +- Initial Configuration:** UE-RRC sends CPHY-TrCH-Config-REQ to UE-PHY. UE-RRC sends CMAC-Config-REQ to UE-MAC. +- First Attempt:** UE-RRC sends MAC-Data-REQ to UE-MAC. UE-MAC starts a backoff timer. After the backoff, UE-MAC sends PHY-Data-REQ to UE-PHY. UE-PHY transmits RACH Data to Node B-PHY, but it results in a collision (indicated by an 'X'). +- Collision Handling:** UE-RRC sets a timer and waits for an ACK from the UTRAN on the FACH. Upon timer expiry, the process restarts. +- Second Attempt:** UE-RRC sends CPHY-TrCH-Config-REQ to UE-PHY. UE-RRC sends CMAC-Config-REQ to UE-MAC. UE-RRC sends MAC-Data-REQ to UE-MAC. UE-MAC starts a backoff timer. After the backoff, UE-MAC sends PHY-Data-REQ to UE-PHY. UE-PHY transmits RACH Data to Node B-PHY. Node B-PHY receives the data and sends MAC-Data-IND to RNC-MAC. RNC-MAC performs an evaluation of the MAC header and then sends MAC-Data-IND to RNC-RRC. Finally, an ACK is sent on the FACH from RNC-RRC back to UE-RRC. + +Sequence diagram of Random access transmission sequence (3.84 Mcps TDD) + +**Figure 45: Random access transmission sequence (3.84 Mcps TDD)** + +The RACH is configured once via a CPHY-TrCH-Config-REQ primitive. This primitive needs to be used only for initial configuration (e.g. power parameter) or when a parameter shall be changed, not for every RACH transmission. + +The CMAC-Config-REQ primitive is used to configure MAC parameters required for the random access procedure. The parameters could include random access control parameters such as, persistence value and Access Service Class (ASC) parameters. + +When there is data to be transmitted on the RACH, i.e. reception of a MAC-Data-REQ primitive, the RACH transmission control procedure is started, which includes selection of an Access Service Class (ASC). + +After some backoff, a primitive PHY-Data-REQ is sent to L1, which triggers the PRACH message transmission, i.e. the physical layer selects a PRACH spreading-code without further backoff delay imposed on L1, but within the constraints of the selected ASC. Note that the backoff time on MAC may in certain conditions be set to zero (e.g. when the uplink load is low). + +At the UTRAN-side MAC the further processing of received RACH message depends on the MAC header. An acknowledgement that the message was received correctly is given by a RRC procedure. In case of transparent RLC, message retransmission shall be handled entirely on RRC employing retransmission timers. In case of non-transparent RLC, the timers are controlled by the RLC. The parameters of PRACH transmission are chosen such that the number of retransmissions for the messages are kept low. Message loss on the PRACH should be due to a collision on the same spreading code. + +#### 6.7.3.2 Random access transmission sequence (1.28 Mcps TDD) + +![Sequence diagram of Random access transmission sequence (1.28 Mcps TDD)](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +The diagram illustrates the interaction between various protocol layers in a User Equipment (UE) and the Node B during a random access procedure. The lifelines are UE-RRC, UE-RLC, UE-MAC, UE-PHY, Node B-PHY, and RNC-MAC. The sequence starts with configuration primitives (CPHY-TrCH-Config-REQ, CMAC-Config-REQ) from UE-RRC. Data to be transmitted is requested via MAC-Data-REQ from UE-RLC. The MAC layer performs an initial backoff and then sends a PHY-Access-REQ to the PHY layer. The PHY layer initiates a SYNC\_UL transmission. A collision occurs at the Node B-PHY, indicated by crossed arrows. After the timer expires, a subsequent backoff is performed, and another PHY-Access-REQ is sent. The Node B-PHY receives the transmission and sends an FPACH "ACK" back to the UE-PHY. The UE-PHY then sends a PHY-Access-CNF to the MAC layer. Following another subsequent backoff, the MAC layer sends a PHY-Data-REQ to the PHY layer, which transmits the RACH Data to the Node B-PHY. The Node B-PHY then sends a MAC-Data-IND to the RNC-MAC, which proceeds with the evaluation of the MAC header. + +Sequence diagram of Random access transmission sequence (1.28 Mcps TDD) + +**Figure 46: Random access transmission sequence(1.28 Mcps TDD)** + +The RACH is configured once via a CPHY-TrCH-Config-REQ primitive. This primitive needs to be used only for initial configuration or when a parameter shall be changed, not for every RACH transmission. + +The CMAC-Config-REQ primitive is used to configure MAC parameters required for the random access procedure. The parameters could include random access control parameters such as persistence value, Access Service Class (ASC) parameters and maximum number of synchronisation attempts. + +When there is data to be transmitted on the RACH, i.e. reception of a MAC-Data-REQ primitive, the RACH transmission control procedure is started, which includes selection of an Access Service Class (ASC). + +After some backoff, a primitive PHY-Access-REQ is sent to L1, which triggers the PRACH message transmission, i.e. the physical layer selects a SYNC\_UL code without further backoff delay imposed on L1, but within the constraints of the selected ASC. + +If PHY received no acknowledgement on the FPACH and the maximum number of synchronisation attempts permitted has not been exceeded, the PHY-Access-REQ procedure is repeated. + +If the SYNC\_UL burst has been acknowledged on the FPACH, MAC receives an acknowledgement via PHY-Access-CNF primitive. Then data transmission is requested with a PHY-DATA-REQ primitive, and the PRACH transmission procedure shall be completed with transmission of the PRACH message on the PRACH resources associated with FPACH. + +### 6.7.4 Void + +# 7 Traffic volume monitoring + +An algorithm will be defined for the UE to trigger a message to the NW based on transmitter buffer status. + +Figure 48 illustrates the example of message sequence of traffic volume monitoring procedure. RRC in UE gets the parameters necessary for traffic volume measurement from Measurement Control message or System information message sent by RRC in UTRAN. RRC in UE passes the MAC the parameters for traffic volume measurement with the CMAC-Measurement-REQ. Meanwhile, RLC passes the data to MAC with buffer status. There are two ways MAC indicates the traffic volume measurement report to RRC, periodic and event-triggered. If it is periodic report, the MAC reports the measurement result to RRC periodically. If it is event-triggered, MAC in UE reports the measurement result to RRC when the result is beyond the specified threshold value. After that, based on the measurement report from MAC and reporting criteria received from UTRAN, RRC makes a decision whether it should send Measurement Report Message to UTRAN. When RRC in UTRAN receives the Measurement Report Message, it takes a proper action based on the measurement report from UE. It can be bearer reconfiguration, transport channel reconfiguration, physical channel reconfiguration or transport channel combination control procedure. The report mode, periodic and event-triggered, can be used exclusively, or simultaneously as shown in figure 1. + +![Sequence diagram of Traffic Volume Measurement Report Procedure showing interactions between UE-RRC, UE-RLC, UE-MAC, UE-PHY, NodeB-PHY, RNC-MAC, RNC-RLC, and RNC-RRC.](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +The sequence diagram illustrates the Traffic Volume Measurement Report Procedure across two interfaces: Uu (between UE and NodeB) and Iub (between NodeB and RNC). The lifelines are UE-RRC, UE-RLC, UE-MAC, UE-PHY, NodeB-PHY, RNC-MAC, RNC-RLC, and RNC-RRC. + +- Uu Interface:** + - NodeB-PHY sends a **BCCH: System Information Message [Traffic Volume Measurement]** to UE-PHY. + - NodeB-PHY sends a **DCCH: MEASUREMENT CONTROL Message [Traffic Volume Measurement]** to UE-PHY. +- UE Internal:** + - UE-RRC receives the messages from NodeB-PHY and sends a **CMAC-MEASUREMENT-REQ** to UE-MAC. + - UE-RLC sends **MAC-DATA-REQ** to UE-MAC. This occurs periodically (indicated by 'Report Interval'). + - UE-MAC performs measurements and sends **CMAC-MEASUREMENT-IND** to UE-RRC. This can be periodic or triggered when a **Threshold exceeds**. + - UE-RRC receives the indication and makes a **Decide to report** decision. +- Iub Interface:** + - UE-RRC sends a **DCCH: MEASUREMENT REPORT Message [Traffic Volume Measurement]** to RNC-RRC. + - RNC-RRC receives the message and **Choose Action accordingly**. +- Bottom Section:** + - The action chosen by RNC-RRC leads to **Radio Bearer Control Procedures**, which include: **[Bearer Reconfiguration / Transport Channel Reconfiguration / Physical Channel Reconfiguration / Transport Format Combination Control]**. + +Sequence diagram of Traffic Volume Measurement Report Procedure showing interactions between UE-RRC, UE-RLC, UE-MAC, UE-PHY, NodeB-PHY, RNC-MAC, RNC-RLC, and RNC-RRC. + +Figure 48: Traffic Volume Measurement Report Procedure + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 06/1999 | RP-04 | RP-99310 | - | | | Approved at TSG-RAN #4 placed under Change Control | 3.0.0 | +| 10/1999 | RP-05 | RP-99462 | 001 | | | RRC connection establishment procedure | 3.1.0 | +| | RP-05 | RP-99462 | 002 | 1 | | RRC Connection release procedure | 3.1.0 | +| | RP-05 | RP-99462 | 003 | | | Cell update and URA update procedures | 3.1.0 | +| | RP-05 | RP-99462 | 004 | | | Removal of FFS in DSCH transmission example | 3.1.0 | +| | RP-05 | RP-99462 | 005 | | | Incorporation of DSCH transmission with one TFCI | 3.1.0 | +| | RP-05 | RP-99462 | 006 | | | RRC Traffic Volume Monitoring Procedure | 3.1.0 | +| | RP-05 | RP-99462 | 007 | | | Transfer and update of system information | 3.1.0 | +| | RP-05 | RP-99462 | 008 | | | UE controlled AMR mode adaptation | 3.1.0 | +| | RP-05 | RP-99462 | 009 | | | Model of RACH procedures | 3.1.0 | +| | RP-05 | RP-99462 | 012 | | | USCH/DSCH data transfer for TDD | 3.1.0 | +| | RP-05 | RP-99462 | 013 | | | Removal of UE State Description | 3.1.0 | +| | RP-05 | RP-99462 | 014 | | | Editorial renaming request | 3.1.0 | +| | RP-05 | RP-99462 | 015 | | | Release version for Asymmetric transport channel reconfiguration procedure | 3.1.0 | +| | RP-05 | RP-99462 | 016 | | | Example message sequence for RACH transmissions in TDD mode | 3.0.0 | +| 12/1999 | RP-06 | RP-99629 | 017 | 1 | | Support of shared channel operation in TDD and alignment to Mac-c/sh merge | 3.2.0 | +| | RP-06 | RP-99628 | 018 | 2 | | Corrections to RRC State Names | 3.2.0 | +| | RP-06 | RP-99628 | 021 | | | Editorial issues | 3.2.0 | +| 03/2000 | RP-07 | RP-000036 | 022 | 4 | | CPCH start of message indication | 3.3.0 | +| | RP-07 | RP-000036 | 023 | | | Correction to Transport Format Combination Control procedure | 3.3.0 | +| | RP-07 | RP-000036 | 025 | 1 | | CPCH Emergency Stop sequence | 3.3.0 | +| | RP-07 | RP-000036 | 026 | 1 | | Variable Rate Packet Transmission for uplink DCH | 3.3.0 | +| | RP-07 | RP-000036 | 027 | | | Random access transmission sequence | 3.3.0 | +| 06/2000 | RP-08 | RP-000216 | 029 | | | Corrections to L2 link management and radio link setup in interlayer message sequence charts | 3.4.0 | +| | RP-08 | RP-000216 | 030 | | | Alignment of FDD downlink shared channel descriptions with 25.331 | 3.4.0 | +| | RP-08 | RP-000216 | 031 | 1 | | End of CPCH transmission | 3.4.0 | +| | RP-08 | RP-000216 | 033 | | | Out-of-synch corrections | 3.4.0 | +| | RP-08 | RP-000216 | 034 | | | Traffic Volume Monitoring | 3.4.0 | +| 09/2000 | RP-09 | RP-000354 | 035 | 2 | | SRNS relocation | 3.5.0 | +| | RP-09 | RP-000354 | 037 | | | Variable Rate Transmission | 3.5.0 | +| 12/2000 | RP-10 | RP-000564 | 038 | 1 | | Corrections to SRNS Relocation | 3.6.0 | +| | RP-10 | RP-000564 | 040 | | | Correction to Relocation text | 3.6.0 | +| 03/2001 | RP-11 | RP-010021 | 041 | 1 | | Text corrections | 3.7.0 | +| | RP-11 | RP-010021 | 042 | | | SRNS relocation | 3.7.0 | +| | RP-11 | RP-010021 | 044 | | | Clean-up | 3.7.0 | +| | RP-11 | RP-010037 | 043 | | | 1.28Mcps TDD | 4.0.0 | +| 06/2001 | RP-12 | RP-010304 | 046 | | | Corrections to procedure examples | 4.1.0 | +| 09/2001 | RP-13 | RP-010538 | 051 | | | SRNS relocation and header compression protocol | 4.2.0 | +| | RP-13 | RP-010538 | 053 | | | Alignment on active set update | 4.2.0 | +| | RP-13 | RP-010538 | 057 | | | Proposed correction to SRNS relocation procedure | 4.2.0 | +| 12/2001 | RP-14 | RP-010755 | 059 | | | Correction to RNTI in cell-update and URA-update procedures | 4.3.0 | +| | RP-14 | RP-010755 | 061 | | | HFN transfer between network nodes in SRNS relocation | 4.3.0 | +| 03/2002 | RP-15 | RP-020062 | 064 | | | Correction on RRC connection establishment procedure | 4.4.0 | +| | RP-15 | RP-020062 | 067 | | | Alignment of SRNS relocation in CELL_DCH | 4.4.0 | +| | RP-15 | RP-020062 | 069 | | | Corrections on combined Cell/URA update and SRNS relocation | 4.4.0 | +| | RP-15 | - | - | | | Upgrade to Release 5 - no technical change | 5.0.0 | +| 06/2002 | RP-16 | RP-020323 | 072 | | | Clarification on lossless SRNS Relocation | 5.1.0 | +| | RP-16 | RP-020345 | 073 | | | RFC 3095 context relocation | 5.1.0 | +| 12/2003 | RP-22 | - | - | | | Upgrade to Release 6 - no technical change | 6.0.0 | +| 09/2004 | RP-25 | RP-040338 | 074 | | | Clarification to SRNS Relocation | 6.1.0 | +| 12/2004 | RP-26 | RP-040478 | 076 | | | Clarification of inter-layer dependencies | 6.2.0 | +| 06/2005 | RP-28 | RP-050308 | 0078 | | | Feature Clean-up: Removal of DSCH (FDD) | 6.3.0 | +| | RP-28 | RP-050309 | 0080 | | | Feature Clean Up: Removal of CPCH | 6.3.0 | +| 03/2006 | RP-31 | - | - | | | Upgrade to the Release 7 - no technical change | 7.0.0 | +| 12/2007 | RP-38 | - | - | | | Upgrade to the Release 8 - no technical change | 8.0.0 | +| 12/2009 | RP-46 | - | - | | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 03/2011 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | +| 09/2014 | RP-65 | - | - | - | | Upgrade to the Release 12 - no technical change | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | | Upgrade to the Release 14 - no technical change | 14.0.0 | +| 06/2018 | RP-80 | - | - | - | | Upgrade to the Release 15 - no technical change | 15.0.0 | + +| | | | | | | | | +|---------|--------|---|---|---|---|----------------------------------------------------|--------| +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +|---------|--------|---|---|---|---|----------------------------------------------------|--------| \ No newline at end of file diff --git a/marked/Rel-16/25_series/25304/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/25_series/25304/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf26bcc5228b76eba74667af7409d12ff9b7c2df --- /dev/null +++ b/marked/Rel-16/25_series/25304/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c3478d08bd583e2da27b9587154fd8cc6c4fb0996db0fb4da84023eb7e81b31 +size 148237 diff --git a/marked/Rel-16/25_series/25304/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/25_series/25304/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb3f1ad59b1ff171c8da04ff581c50e2e9f40462 --- /dev/null +++ b/marked/Rel-16/25_series/25304/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09622d7f5e665f688637d87acfe6a4ececbf5f36ea2ae1a7db8dcc88579b80ee +size 70821 diff --git a/marked/Rel-16/25_series/25304/raw.md b/marked/Rel-16/25_series/25304/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..391dcd2f74fcec545cf77084507aff0bfdd3ec7a --- /dev/null +++ b/marked/Rel-16/25_series/25304/raw.md @@ -0,0 +1,2298 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 10 | +| 4 General description of Idle mode..... | 12 | +| 4.1 Overview ..... | 12 | +| 4.2 Functional division between AS and NAS in Idle mode ..... | 13 | +| 4.3 Service type in Idle and Connected Mode ..... | 15 | +| 5 Process and procedure descriptions ..... | 17 | +| 5.1 PLMN selection..... | 17 | +| 5.1.1 General ..... | 17 | +| 5.1.2 Support for PLMN Selection..... | 17 | +| 5.1.2.1 General..... | 17 | +| 5.1.2.2 UTRA case..... | 17 | +| 5.1.2.3 GSM case..... | 17 | +| 5.1.2.4 E-UTRA case..... | 18 | +| 5.2 Cell selection and reselection in idle mode..... | 18 | +| 5.2.1 Introduction ..... | 18 | +| 5.2.2 States and state transitions in Idle Mode ..... | 19 | +| 5.2.2.1 Cell Selection process overview ..... | 19 | +| 5.2.2.2 Camped normally state overview ..... | 20 | +| 5.2.2.3 Connected mode State overview..... | 20 | +| 5.2.2.4 Any cell selection State overview..... | 20 | +| 5.2.2.5 Camped on any cell State overview..... | 20 | +| 5.2.3 Cell Selection Process ..... | 21 | +| 5.2.3.1 UTRA case..... | 21 | +| 5.2.3.1.1 Description ..... | 21 | +| 5.2.3.1.2 Criteria..... | 21 | +| 5.2.3.2 GSM case..... | 22 | +| 5.2.3.3 E-UTRA case..... | 22 | +| 5.2.3.4 CSG cells and Hybrid cells in Cell Selection ..... | 22 | +| 5.2.4 Void ..... | 22 | +| 5.2.5 Camped Normally State ..... | 22 | +| 5.2.5.1 UTRA case..... | 22 | +| 5.2.5.2 GSM case..... | 23 | +| 5.2.5.3 E-UTRA case..... | 23 | +| 5.2.6 Cell Reselection Evaluation Process ..... | 23 | +| 5.2.6.1 UTRA case..... | 23 | +| 5.2.6.1.0 Use of MBMS PL..... | 23 | +| 5.2.6.1.1 Measurement rules for cell re-selection when HCS is not used..... | 23 | +| 5.2.6.1.1a High-mobility state when HCS is not used..... | 24 | +| 5.2.6.1.2 Measurement rules for cell re-selection when HCS is used..... | 24 | +| 5.2.6.1.2a Measurement rules for inter-frequency and inter-RAT cell reselection when absolute priorities are used ..... | 26 | +| 5.2.6.1.3 Highest ranked cells with cell reservations, access restrictions or unsuitable for normal camping ..... | 27 | +| 5.2.6.1.4 Cell Reselection Criteria ..... | 28 | +| 5.2.6.1.4a Absolute priority based criteria for inter-frequency and inter-RAT cell reselection ..... | 32 | +| 5.2.6.1.5 Cell reselection parameters in system information broadcasts ..... | 34 | +| 5.2.6.2 GSM case..... | 38 | +| 5.2.6.3 E-UTRA case..... | 38 | +| 5.2.6.4 Cell reselection with CSG cells ..... | 38 | +| 5.2.6.4.1 Cell reselection from a non-CSG cell to a CSG cell ..... | 38 | +| 5.2.6.4.2 Cell reselection from a CSG cell to non-CSG cell..... | 38 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------------|----| +| 5.2.6.4.3 | Cell reselection from a CSG cell to a CSG cell ..... | 39 | +| 5.2.6.5 | Cell Reselection with Hybrid Cells ..... | 39 | +| 5.2.7 | Cell Selection when leaving connected mode ..... | 39 | +| 5.2.7.1 | UTRA case..... | 39 | +| 5.2.7.2 | GSM case..... | 39 | +| 5.2.7.3 | E-UTRA case..... | 39 | +| 5.2.8 | Any Cell Selection state ..... | 40 | +| 5.2.9 | Camped on Any Cell State ..... | 40 | +| 5.2.9.1 | UTRA case..... | 40 | +| 5.2.9.2 | GSM case..... | 40 | +| 5.2.9.3 | E-UTRA case..... | 40 | +| 5.3 | Cell Reservations and Access Restrictions (cells not operating in MBSFN mode)..... | 40 | +| 5.3.1 | UTRA cells ..... | 40 | +| 5.3.1.1 | Cell status and cell reservations..... | 40 | +| 5.3.1.2 | Access Control..... | 42 | +| 5.3.1.3 | Emergency Call..... | 42 | +| 5.3.2 | GSM cells ..... | 42 | +| 5.3.3 | E-UTRA cells ..... | 42 | +| 5.3a | Cell Reservations and Access Restrictions (MBSFN cells only for FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD) ..... | 42 | +| 5.4 | Cell Selection and Reselection Processes in RRC Connected Mode ..... | 43 | +| 5.4.1 | Void ..... | 43 | +| 5.4.2 | Void ..... | 43 | +| 5.4.3 | Cell Reselection Process in RRC connected mode ..... | 43 | +| 5.4.4 | Cell Selection Process in RRC connected mode ..... | 43 | +| 5.5 | Location Registration ..... | 43 | +| 5.6 | Support for manual CSG Selection ..... | 43 | +| 5.6.1 | UTRA case ..... | 43 | +| 5.6.2 | E-UTRA case..... | 44 | +| 5.7 | Logged Measurements ..... | 44 | +| 5.8 | Logged UTRAN ANR ..... | 44 | +| 5.8.1 | General ..... | 44 | +| 5.8.2 | UTRAN ANR measurement process..... | 44 | +| 5.8.2.1 | Intra-freq and inter-freq ANR case..... | 44 | +| 5.8.2.2 | Inter-RAT ANR case ..... | 45 | +| 5.9 | Accessibility measurements ..... | 45 | +| 5.10 | RAN-assisted WLAN interworking ..... | 45 | +| 5.10.1 | RAN assistance parameter handling in Idle mode, CELL_PCH, URA_PCH and CELL_FACH ..... | 45 | +| 5.10.2 | Access network selection and traffic steering rules..... | 45 | +| 5.10.3 | RAN assistance parameters definition..... | 46 | +| 6 | Broadcast information receiving..... | 47 | +| 6.1 | Reception of System Information ..... | 47 | +| 6.2 | Cell Broadcast in Idle Mode, CELL_PCH and URA_PCH..... | 47 | +| 6.3 | MBMS Services ..... | 48 | +| 6.3.1 | MBSFN cluster selection and reselection..... | 48 | +| 6.3.1.1 | MBSFN cluster selection ..... | 48 | +| 6.3.1.2 | Camped on MBSFN cluster ..... | 48 | +| 6.3.1.3 | MBSFN inter frequency neighbour information ..... | 48 | +| 7 | Void..... | 49 | +| 8 | Paging and SCCPCH selection and in FDD and 1.28 Mcps TDD the H-RNTI selection..... | 49 | +| 8.1 | Paging Channel selection ..... | 49 | +| 8.2 | SCCPCH selection when entering Connected mode..... | 49 | +| 8.2b | H-RNTI selection when entering Connected mode (FDD and 1.28 Mcps TDD)..... | 50 | +| 8.3 | Discontinuous Reception for Paging..... | 51 | +| 8.4 | Discontinuous Reception for MBMS..... | 52 | +| 8.4.1 | Discontinuous Reception for MCCH ..... | 53 | +| 8.4.1.1 | Discontinuous Reception via MICH..... | 53 | +| 8.4.1.2 | Discontinuous Reception via MODIFIED SERVICES INFORMATION..... | 53 | +| 8.4.2 | Discontinuous Reception for MTCH..... | 53 | + +8a MBMS Notification ..... 54 +9 Void..... 54 +10 Void..... 54 +Annex A (informative): Change history..... 55 + +# --- 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 Access Stratum (AS) part of the Idle Mode procedures applicable to a UE. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in [5]. + +The present document also specifies cell selection and reselection processes applicable to UEs in connected mode. Invocation of these processes is described in [4]. + +The present document specifies the model for the functional division between the NAS and AS in a UE. + +The present document applies to all UEs that support at least UTRA, including multi-RAT UEs as described in 3GPP specifications, in the following cases: + +- When the UE is camped on a UTRA cell; +- When the UE is searching for a cell to camp on; + +NOTE: The details for those cases are described in the specifications of the other RAT. + +The present document presents also examples of inter-layer procedures related to the idle mode processes and describes idle mode functionality of a multi-RAT UTRA/GSM/E-UTRA UE. + +The present document also specifies how idle-mode and reselection procedures are affected by the provision of MBMS services. + +# --- 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 43.022: "Functions related to Mobile Station in idle mode and group receive mode". +- [2] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [3] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode". +- [4] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [5] 3GPP TS 23.122: "NAS functions related to Mobile Station (MS) in idle mode ". +- [6] 3GPP TR 25.922: "Radio Resource Management Strategies". +- [7] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [8] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [9] 3GPP TS 22.011: "Service accessibility". +- [10] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)". +- [11] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)". +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +- [13] 3GPP TS 45.008: "Radio subsystem link control". +- [14] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [15] 3GPP TS 25.224: "Physical Layer Procedures (TDD)". +- [16] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols - Stage 3". +- [17] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (Stage-2)". +- [18] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [19] 3GPP TS 25.321: "MAC Protocol Specification". +- [20] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". +- [21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [22] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [23] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [24] IEEE 802.11-2012, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std.". +- [25] Wi-Fi Alliance Technical Committee, Hotspot 2.0 Technical Task Group: "Hotspot 2.0 (Release 2) Technical Specification". +- [26] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [27] 3GPP TS 25.225: "Physical layer – Measurements (TDD)". +- [28] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions and the definitions in [12] apply. + +**Absolute priority layer:** A priority level can be defined for a UTRA frequency, a group of GSM frequencies or a E-UTRA frequency. + +**CSG whitelist:** A list provided by NAS containing all the CSG identities and their associated PLMN IDs of the CSGs to which the subscriber belongs. + +NOTE: This list is known as Allowed CSG List in Rel-8 Access Stratum specifications. + +**Acceptable Cell:** A cell that satisfies certain conditions as specified in 4.3. A UE can always attempt emergency calls on an acceptable cell. + +**Available PLMN:** A PLMN for which the UE has found at least one cell and read its PLMN identity. + +**Barred Cell:** A cell a UE is not allowed to camp on. + +**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information. + +**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity. + +**Camped on MBSFN cluster:** UE has completed the MBSFN Cluster selection/reselection process and has chosen a MBSFN Cluster. The UE monitors system information and receives notifications for MBMS services and possibly receives a MBMS service. + +**Closed Subscriber Group (CSG):** A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells). + +**CSG cell:** A cell broadcasting a CSG Indicator that is set to TRUE and a specific CSG identity. All the UTRAN CSG cells sharing the same identity and PLMN identity are identifiable as a single group for the purposes of mobility management and charging. + +**CSG identity:** An identifier broadcast by a CSG or hybrid cell/cells and used by the UE to facilitate access for authorised members of the associated Closed Subscriber Group. + +**CSG member cell:** a cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity. + +**DRX cycle:** Individual time interval between monitoring Paging Occasion for a specific UE. + +**EHPLMN:** Any of the PLMN entries contained in the Equivalent HPLMN list stored on the USIM [5]. + +**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, MBSFN Cluster selection MBSFN Cluster reselection, and handover according to the information provided by the NAS. + +**HNB Name:** The Home NodeB Name is a broadcast string in free text format that provides a human readable name for the Home NodeB CSG identity and any broadcasted PLMN identity. + +**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI. + +**Hybrid cell:** A cell not broadcasting a CSG Indicator but broadcasting a specific CSG identity. + +**Location Registration (LR):** UE registers its presence in a registration area, for instance regularly or when entering a new registration area. + +**Maximum DRX cycle:** Time interval for the longest possible DRX cycle in a cell. + +**MBMS Activated Service:** An MBMS service that the UE has joined (multicast) or is interested in (broadcast). + +**MBMS Preferred Layer (PL):** A frequency layer that is indicated by the UTRAN to be preferred for camping for MBMS purposes. + +**MBSFN cluster:** Set of cells operating in MBSFN mode providing only MBMS service in PtM mode and seen as one cell by a UE. + +**MBSFN mode:** In order to achieve higher spectral efficiency synchronized cells operate in MBSFN mode which implies that they transmit exactly the same content over an area that is seen as one MBSFN cell by the UE. + +**Paging Block Periodicity (PBP):** Period of the occurrence of Paging Blocks. (For FDD, PBP = 1). + +**Paging Message Receiving Occasion (TDD only):** The frame where the UE receives actual paging message. + +**Paging occasion:** + +(FDD) The SFN of the PICH frame where the UE monitors its paging indicator (i.e. the SFN of the PCCPCH frame in which the PICH frame begins). + +(TDD) The paging block, which consists of several frames. The value of Paging Occasion is equal to the first frame of the Paging Block. + +**Power saving mode:** Mode allowing the UE to reduce its power consumption, as defined in TS 24.008 [16], TS 23.060 [21], TS 23.682 [22]. + +**Process:** A local action in the UE invoked by a RRC procedure or an Idle Mode procedure. + +**Radio Access Mode:** Radio access mode of the cell, FDD or TDD. + +**Radio Access Technology:** Type of technology used for radio access, for instance UTRA or GSM. + +**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred [5]. + +**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure. + +**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information. + +**Restricted Cell:** A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred. + +**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically. + +**Serving cell:** The cell on which the UE is camped. + +**Strongest cell:** The cell on a particular carrier that is considered strongest according to the layer 1 cell search procedure [14][15]. As the details of the layer 1 cell search are implementation dependent, the precise definition of 'strongest cell' is also implementation dependent. + +**Suitable Cell:** This is a cell on which an UE may camp. For a UTRA cell, the criteria are defined in subclause 4.3, for a GSM cell the criteria are defined in [1] and for a E-UTRA cell the criteria are defined in [18]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------------------------| +| ACDC | Application specific Congestion control for Data Communication | +| ANDSF | Access Network Discovery and Selection Function | +| ANR | Automatic Neighbor Relation | +| AS | Access Stratum | +| BCCH | Broadcast Control Channel | +| BSS | Basic Service Set | +| CM | Connection Management | +| CMAS | Commercial Mobile Alert System | +| CN | Core Network | +| CSG | Closed Subscriber Group | +| DRX | Discontinuous Reception | +| DSCH | Downlink Shared Channel | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| E-UTRAN | Evolved UMTS Terrestrial Radio Access Network | +| ETWS | Earthquake and Tsunami Warning System | +| FDD | Frequency Division Duplex | +| GC | General Control (SAP) | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile Communications | +| HCS | Hierarchical Cell Structure | +| IMB | Integrated Mobile Broadcast | +| IMSI | International Mobile Subscriber Identity | +| MBMS | Multimedia Broadcast-Multicast Service | +| MBSFN | MBMS over a Single Frequency Network | +| MCC | Mobile Country Code | +| MCCH | MBMS point-to-multipoint Control Channel | +| MDT | Minimization of Drive Tests | +| MICH | MBMS notification Indicator Channel | +| MM | Mobility Management | +| MNC | Mobile Network Code | +| MSCH | MBMS point-to-multipoint Scheduling Channel | +| MTCH | MBMS point-to-multipoint Traffic Channel | +| NAS | Non-Access Stratum | +| NI | (MBMS) Notification Indicator | +| PCH | Paging Channel | + +| | | +|-------|--------------------------------------------| +| PI | Page Indicator | +| PICH | Page Indication Channel | +| PLMN | Public Land Mobile Network | +| PSM | Power Saving Mode | +| RAT | Radio Access Technology | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| TDD | Time Division Duplex | +| TMGI | Temporary Mobile Group Identity | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 General description of Idle mode + +## 4.1 Overview + +When a UE is switched on, a public land mobile network (PLMN) is selected and the UE searches for a suitable cell of this PLMN to camp on. Criteria for cell selection and cell re-selection between radio access technologies (RATs) described in this document only consider radio criteria. In addition to RAT, the PLMN type may differ as well. In this specification, the term PLMN is used as a generic term covering both GSM MAP and ANSI-41 type of PLMNs. According to the type of PLMN, the way to identify it can be different. If the PLMN type is GSM, the PLMN is identified by 'PLMN identity' and if the PLMN type is ANSI-41, the PLMN is identified by 'SID' + +The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use for cell selection and cell reselection. + +The UE searches for a suitable cell of the selected PLMN and chooses that cell to provide available services, and tunes to its control channel. This choosing is known as "camping on the cell". The UE will, if necessary, then register its presence, by means of a NAS registration procedure, in the registration area of the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN [5]. + +If the UE finds a more suitable cell, it reselects onto that cell and camps on it. If the new cell is in a different registration area, location registration is performed. + +If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in [9] and search for a suitable cell if another PLMN has been selected by NAS. + +NOTE: For RRC connected mode the requirements for the search for higher priority PLMNs are defined in [4]. + +Search of available CSGs may be triggered by NAS to support manual CSG selection. + +If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an indication of which PLMNs are available is given to the user, so that a manual selection can be made (manual mode). + +Registration is not performed by UEs only capable of services that need no registration. + +The purpose of camping on a cell in idle mode is fourfold: + +- a) It enables the UE to receive system information from the PLMN. +- b) When registered and if the UE wishes to establish an RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped. +- c) If the PLMN receives a call for the registered UE, it knows (in most cases) the registration area of the cell in which the UE is camped. It can then send a "paging" message for the UE on control channels of all the cells in the registration area. The UE will then receive the paging message because it is tuned to the control channel of a cell in that registration area and the UE can respond on that control channel. +- d) It enables the UE to receive cell broadcast services. + +If the UE is unable to find a suitable cell to camp on, or the USIM is not inserted, or if the location registration failed (except for LR rejected with cause #12, cause #14, cause #15 or cause #25, see [5] and [16]), it attempts to camp on a cell irrespective of the PLMN identity, and enters a "limited service" state in which it can only attempt to make emergency calls, receive ETWS, and receive CMAS. + +The idle mode tasks can be subdivided into four processes: + +- PLMN selection; +- Cell selection and reselection; +- Location registration; +- Support for manual CSG selection. + +The relationship between these processes is illustrated in Figure 1. + +![Figure 1: Overall Idle Mode process flowchart showing the interaction between PLMN Selection, Support for manual CSG selection, Cell Selection and Reselection, and Location Registration.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +graph TD + subgraph Manual_Mode [Manual Mode] + direction TB + M1[ ] -- "Indication to user" --> M2[ ] + end + subgraph Automatic_Mode [Automatic mode] + direction TB + A1[ ] -- "Available (PLMN, CSG IDs) to NAS" --> A2[ ] + end + PLMN_Selection[PLMN Selection] + Manual_CSG_Selection[Support for manual CSG selection] + Cell_Selection[Cell Selection and Reselection] + Location_Registration[Location Registration] + + PLMN_Selection -- "PLMNs available" --> Manual_CSG_Selection + Manual_CSG_Selection -- "CSG selected" --> Cell_Selection + PLMN_Selection -- "PLMN selected (optional CSG ID)" --> Cell_Selection + Cell_Selection -- "Registration Area changes" --> Location_Registration + Location_Registration -- "Location Registration response" --> PLMN_Selection + Service_Requests[Service requests] --> Location_Registration + NAS_Control[NAS Control] -.-> Cell_Selection + Radio_Measurements[Radio measurements] -.-> Cell_Selection + +``` + +The diagram illustrates the overall idle mode process. It consists of four main functional blocks: **PLMN Selection**, **Support for manual CSG selection**, **Cell Selection and Reselection**, and **Location Registration**. The process starts with **PLMN Selection**, which receives inputs from **Manual Mode** (indication to user) and **Automatic mode** (available PLMN, CSG IDs to NAS). It outputs **PLMNs available** to **Support for manual CSG selection** and **PLMN selected (optional CSG ID)** to **Cell Selection and Reselection**. **Support for manual CSG selection** outputs **CSG selected** to **Cell Selection and Reselection**. **Cell Selection and Reselection** receives **Registration Area changes** from **Location Registration** and outputs **Location Registration response** to **PLMN Selection**. **Location Registration** also receives **Service requests** and is influenced by **NAS Control** and **Radio measurements**. + +Figure 1: Overall Idle Mode process flowchart showing the interaction between PLMN Selection, Support for manual CSG selection, Cell Selection and Reselection, and Location Registration. + +**Figure 1: Overall Idle Mode process** + +When NAS indicates that PSM starts, the AS configuration (e.g. priorities provided by dedicated signalling and logged measurements) is kept, all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while the UE is in PSM it is up to UE implementation whether it performs the corresponding action immediately or the latest when PSM ends. When NAS indicates that PSM ends, the UE shall perform all idle mode tasks. + +When NAS indicates that extended DRX in Idle mode parameters have been received, the AS configuration (e.g. priorities provided by dedicated signalling and logged measurements) is kept, all running timers continue to run but the UE need not perform any idle mode tasks. When NAS indicates that extended DRX in Idle mode parameters have been received, the AS starts a timer to indicate the start of the paging transmission window. If a timer expires while the UE is in extended DRX it is up to UE implementation whether it performs the corresponding action immediately or the latest when the paging transmission window starts. When the timer of the extended DRX expires, the AS re-starts the timer of the extended DRX, the AS starts a timer to indicate the end of the paging transmission window, and the UE shall perform all idle mode tasks until the timer of the paging transmission window expires. + +## 4.2 Functional division between AS and NAS in Idle mode + +Table 1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in idle mode. The NAS part is specified in [5] and the AS part in the present document. Examples of different idle mode procedures are presented in Clause 10. + +**Table 1: Functional division between AS and NAS in idle mode** + +| Idle Mode Process | UE Non-Access Stratum | UE Access Stratum | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Selection |

Maintain the list of allowed PLMN types. It can be GSM-MAP only, ANSI-41 only or both.

Maintain a list of PLMNs in priority order according to [5]. Select a PLMN using automatic or manual mode as specified in [5] and request AS to select a cell belonging to this PLMN. For each PLMN, associated RAT(s) may be set.

Evaluate reports of available PLMNs from AS for PLMN selection.

Maintain a list of equivalent PLMN identities.

|

Search for available PLMNs.

If associated RAT(s) is (are) set for the PLMN, search in this (these) RAT(s) and other RAT(s) for that PLMN as specified in [5].

Perform measurements to support PLMN selection.

Synchronise to a broadcast channel to identify found PLMNs.

Report available PLMNs with associated PLMN type and RAT to NAS on request from NAS or autonomously.

It shall respect allowed PLMN types indications from NAS.

| +| Cell Selection |

Control cell selection for example by indicating RAT(s) associated with the selected PLMN to be used initially in the search of a cell in the cell selection. NAS is also maintaining lists of forbidden registration areas and a CSG whitelist. NAS provides these lists to AS.

|

Perform measurements needed to support cell selection.

Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS.

Search for a suitable cell. The cells broadcast their 'PLMN identity' (GSM-MAP) or 'SID' and may broadcast a CSG ID and CSG indicator in the system information. Respond to NAS whether such cell is found or not.

If associated RATs is (are) set for the PLMN, perform the search in this (these) RAT(s) and other RATs for that PLMN as specified in [5].

If such a cell is found, the cell is selected to camp on.

| +| Cell Reselection |

Control cell reselection by for example, maintaining lists of forbidden registration areas.

Maintain a list of equivalent PLMN identities and provide the list to AS.

Maintain a list of forbidden LAs and provide the list to AS.

Maintain a CSG whitelist and provide the list to AS.

|

Perform measurements needed to support cell reselection.

Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS.

Change cell if a more suitable cell is found.

| +| Location registration |

Register the UE as active after power on.

Register the UE's presence in a registration area, for instance regularly or when entering a new registration area.

Maintain lists of forbidden LAs.

Deregister UE when shutting down.

|

Report registration area information to NAS.

| + +| Idle Mode Process | UE Non-Access Stratum | UE Access Stratum | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBMS |

Maintain priority information for various services and participate in service selection.

Indicate to AS if an offered session has previously been received.

|

Maintain a list of TMGIs of activated services.

Notify NAS of service availability and request NAS to prioritise in case of service conflicts.

Report to NAS when an activated service requires action.

Receive and handle the MCCH and MTCH, and, if applicable, the MSCH and MICH.

| +| Support for manual CSG selection |

Provide request to search for available CSG(s).

Evaluate reports of available CSG(s) from AS for CSG selection.

Select a CSG and request AS to select a suitable cell belonging to this CSG.

|

Search for cells with a CSG ID.

Read the HNB name from system information if a cell with a CSG ID is found.

Report CSG ID(s) of the found cells broadcasting a CSG ID together with the HNB name and PLMN(s) to NAS. On selection of a CSG by NAS, select any cell belonging to the selected CSG fulfilling the cell selection criteria and not barred or reserved for operator use for UEs not belonging to AC 11 or 15 and give an indication to NAS that access is possible (for the registration procedure).

| + +## 4.3 Service type in Idle and Connected Mode + +This clause defines the level of service that may be provided by the network to a UE in Idle mode and Connected Mode. + +The action of camping on a cell is necessary to get access to some services. Three levels of services are defined for UE: + +- Limited service (emergency calls, ETWS if supported, and CMAS if supported on an acceptable cell) +- Normal service (for public use on a suitable cell) +- Operator service (for operators only on a reserved cell) + +Furthermore, the cells are categorised according to which services they offer: + +### acceptable cell: + +An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls, receive ETWS if supported, and receive CMAS if supported). Such a cell shall fulfil the following requirements, which is the minimum set of requirements to initiate an emergency call and to receive ETWS primary notification and ETWS secondary notification and to receive CMAS notification in a UTRAN network: + +- The cell is not barred, see subclause 5.3.1.1; +- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2; + +### suitable cell: + +A "suitable cell" is a cell on which the UE may camp on to obtain normal service. Such a cell shall fulfil all the following requirements. + +- The cell shall be part of either: + - the selected PLMN, or; + - the registered PLMN, or; + +- a PLMN of the Equivalent PLMN list +- For a CSG cell, the cell is a CSG member cell for the UE; +According to the latest information provided by the NAS. +- The cell is not barred, see subclause 5.3.1.1; +- The cell is part of at least one LA that is not part of the list of "forbidden LAs for roaming" [9], which belongs to a PLMN that fulfills the first bullet above; +- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2. + +If the IE "Multiple PLMN List" [4] is broadcast in the cell, the cell is considered to be part of all LAs with LAIs constructed from the PLMN identities in the "Multiple PLMN List" and the LAC broadcast in the cell. + +### barred cell: + +A cell is barred if it is so indicated in the system information [4]. + +### reserved cell: + +A cell is reserved if it is so indicated in system information [4]. + +Following exceptions to these definitions are applicable for UEs: + +- camped on a cell that belongs to a LA that is forbidden for regional provision of service, and during emergency calls. +- as an outcome of the manual CSG selection procedure the UE is allowed to access an acceptable cell which fulfils the cell selection criteria and is not barred or reserved for operator use for UEs not belonging to AC 11 or 15 and inform NAS that access is possible (for location registration procedure). + +NOTE: UE is not required to support manual search and selection of CSG(s) while in RRC CONNECTED state. + +A cell that belongs to a LA that is forbidden for regional provision service ([5], [16]) is suitable but provides only limited service. + +If a UE has an ongoing emergency call, all acceptable cells of that PLMN are treated as suitable for cell reselection for the duration of the emergency call. + +### suitable MBSFN cluster: + +A cell is part of an MBSFN cluster if it is indicated in system information [4]. An MBSFN cluster provides exclusively MBMS services. A suitable MBSFN cluster shall fulfil all the following requirements: + +- For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD the MBSFN cluster shall be part of either: + - the registered PLMN, or: + - a PLMN of the Equivalent PLMN list + +The MBSFN cluster shall be indicated as: + +- providing MBSFN only service + +For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD MBSFN cluster selection/reselection process for MBSFN clusters operating on the same frequency shall be based on reception quality. Details of the process are not specified. + +# 5 Process and procedure descriptions + +## 5.1 PLMN selection + +### 5.1.1 General + +In the UE, the AS shall report available PLMNs to the NAS on request from the NAS or autonomously. + +UE shall maintain a list of allowed PLMN types. The allowed PLMN type can be GSM-MAP only, ANSI-41 only or both. During PLMN selection, based on the list of allowed PLMN types and a list of PLMN identities in priority order, the particular PLMN may be selected either automatically or manually. Each PLMN in the list of PLMN identities can be identified by either 'PLMN identity' (GSM-MAP) or 'SID'. In the system information on the broadcast channel, the UE can receive a 'PLMN identity' (GSM-MAP) or a 'SID' or a 'PLMN identity' (GSM-MAP) and a 'SID', in a given cell. For a given cell, the UE might receive several 'PLMN identities' from the system information on the broadcast channel. The result of the PLMN selection is an identifier of the selected PLMN, the choice being based on the allowed PLMN types, UE capability or other factors. This identifier is one of either 'PLMN identity' for GSM-MAP type of PLMNs or 'SID' for ANSI-41 type of PLMNs. + +In case that the list of allowed PLMN types includes GSM-MAP, the non-access part of the PLMN selection process is specified in [5]. In the case that list of allowed PLMN types includes ANSI-41, the non-access stratum part of the PLMN selection is specified in TTA/EIA/IS-2000.5 and TTA/EIA/IS-707. + +### 5.1.2 Support for PLMN Selection + +#### 5.1.2.1 General + +On request of the NAS the AS should perform a search for available PLMNs and report them to NAS. + +#### 5.1.2.2 UTRA case + +The UE shall scan all RF channels in the UTRA bands according to its capabilities to find available PLMNs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the PLMN reading in [4]) shall be reported to the NAS as a high quality PLMN (but without the RSCP value), provided that the following high quality criterion is fulfilled: + +1. For an FDD cell, the measured primary CPICH RSCP value shall be greater than or equal to -95 dBm. +2. For a TDD cell, the measured P-CCPCH RSCP shall be greater than or equal to -84 dBm. + +Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and P-CCPCH RSCP for UTRA TDD cells. The quality measure reported by the UE to NAS shall be the same for each PLMN found in one cell. + +The search for PLMNs on the rest of the carriers may be stopped on request of the NAS. The UE may optimise this search by using stored information of carrier frequencies and optionally also information on cell parameters, e.g. scrambling codes, from previously received measurement control information elements. + +Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of that PLMN to camp on. + +If a CSG ID is provided by NAS as part of PLMN selection, the UE shall search for an acceptable or suitable cell belonging to the provided CSG ID to camp on. When the UE is no longer camped on a cell with the provided CSG ID, AS shall inform NAS. + +#### 5.1.2.3 GSM case + +Support for network selection in GSM is described in [1]. + +#### 5.1.2.4 E-UTRA case + +Support for network selection in E-UTRA is described in [18]. + +## 5.2 Cell selection and reselection in idle mode + +### 5.2.1 Introduction + +As stated in clause 1, the present document applies to UEs that support at least UTRA. + +Different types of measurements are used in different RATs and modes for the cell selection and reselection. The performance requirements for the measurements are specified in [10] and [11]. + +The NAS can control the RAT(s) in which the cell selection should be performed, for instance by indicating RAT(s) associated with the selected PLMN, and by maintaining a list of forbidden registration area(s) and a list of equivalent PLMNs. The UE shall select a suitable cell and the radio access mode based on idle mode measurements and cell selection criteria. + +In order to speed up the cell selection process, stored information for several RATs may be available in the UE. + +When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected. The change of cell may imply a change of RAT. Details on performance requirements for cell reselection can be found in [10] and [11]. + +The NAS is informed if the cell selection and reselection results in changes in the received system information. + +For normal service, the UE has to camp on a suitable cell, tune to that cell's control channel(s) so that the UE can: + +- Receive system information from the PLMN; + - Receive registration area information from the PLMN, e.g., location area and routing area; and + - Receive other AS and NAS Information; +- If registered: + - receive paging and notification messages from the PLMN; and + - initiate call setup for outgoing calls or other actions from the UE. + +### 5.2.2 States and state transitions in Idle Mode + +Figure 2 shows the states and procedures in Idle Mode. + +![Flowchart of Idle Mode Cell Selection and Reselection states and transitions.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1 + 1 --> StoredInformationCellSelection: cell information stored for the PLMN + 1 --> InitialCellSelection: no cell information stored for the PLMN + StoredInformationCellSelection --> NoSuitableCellFound1: no suitable cell found + StoredInformationCellSelection --> 2: suitable cell found + InitialCellSelection --> NoSuitableCellFound2: no suitable cell found + InitialCellSelection --> 2: suitable cell found + NoSuitableCellFound1 --> CellSelectionLeavingConnectedMode1: Cell Selection when leaving connected mode + NoSuitableCellFound2 --> AnyCellSelection: Any Cell Selection + CellSelectionLeavingConnectedMode1 --> ConnectedMode1: Connected mode + CellSelectionLeavingConnectedMode1 --> 2: suitable cell found + CellSelectionLeavingConnectedMode1 --> NoSuitableCellFound1: no suitable cell found + ConnectedMode1 --> CellSelectionLeavingConnectedMode1: return to idle mode + 2 --> CampedNormally: Camped normally + CampedNormally --> NoAcceptableCellFound: no acceptable cell found + CampedNormally --> NAS_Rejected: NAS indicates that registration on selected PLMN is rejected + CampedNormally --> Trigger1: trigger + NAS_Rejected --> AnyCellSelection + Trigger1 --> CellReselectionEvaluationProcess1: Cell Reselection Evaluation Process + CellReselectionEvaluationProcess1 --> NoSuitableCellFound1: no suitable cell found + CellReselectionEvaluationProcess1 --> 2: suitable cell found + CellReselectionEvaluationProcess1 --> CampedNormally: suitable cell found + AnyCellSelection --> 1: USIM inserted + AnyCellSelection --> NoAcceptableCellFound: no acceptable cell found + AnyCellSelection --> CampedOnAnyCell: acceptable cell found + NoAcceptableCellFound --> CellSelectionLeavingConnectedMode2: Cell Selection when leaving connected mode + CampedOnAnyCell --> NoAcceptableCellFound: no acceptable cell found + CampedOnAnyCell --> 2: suitable cell found + CampedOnAnyCell --> Trigger2: trigger + Trigger2 --> CellReselectionEvaluationProcess2: Cell Reselection Evaluation Process + CellReselectionEvaluationProcess2 --> NoAcceptableCellFound: no acceptable cell found + CellReselectionEvaluationProcess2 --> CampedOnAnyCell: acceptable cell found + CellReselectionEvaluationProcess2 --> ConnectedMode2: Connected mode (Emergency calls only) + ConnectedMode2 --> CellSelectionLeavingConnectedMode2: return to idle mode + CellSelectionLeavingConnectedMode2 --> NoAcceptableCellFound: no acceptable cell found + CellSelectionLeavingConnectedMode2 --> CampedOnAnyCell: acceptable cell found + CellSelectionLeavingConnectedMode2 --> ConnectedMode2: leave idle mode + +``` + +The flowchart illustrates the states and state transitions in Idle Mode. It begins with an entry point 'I' leading to a circle labeled '1' with the note 'go here whenever a new PLMN is selected'. From '1', two paths emerge: 'cell information stored for the PLMN' leads to 'Stored information Cell Selection', and 'no cell information stored for the PLMN' leads to 'Initial Cell Selection'. Both lead to a circle labeled '2' if a 'suitable cell found'. If 'no suitable cell found', 'Stored information Cell Selection' leads to 'Cell Selection when leaving connected mode' and 'Initial Cell Selection' leads to 'Any Cell Selection'. 'Cell Selection when leaving connected mode' leads to 'Connected mode' and back to 'Idle mode' (circle '1'). 'Any Cell Selection' is reached from 'no suitable cell found' in 'Initial Cell Selection', 'NAS indicates that registration on selected PLMN is rejected', or 'no acceptable cell found' in 'Camped on any cell'. It leads to circle '1' if 'USIM inserted' or to 'Camped on any cell' if an 'acceptable cell found'. 'Camped normally' is reached from circle '2' or 'suitable cell found' in 'Cell Reselection Evaluation Process'. It leads to 'Camped on any cell' if 'no acceptable cell found', to 'Cell Reselection Evaluation Process' if a 'trigger', or to 'Connected mode' if 'leave idle mode'. 'Camped on any cell' leads to 'Camped normally' if 'suitable cell found' (circle '2'), to 'Cell Reselection Evaluation Process' if a 'trigger', or to 'Connected mode (Emergency calls only)' if 'leave idle mode'. 'Cell Reselection Evaluation Process' leads to 'Camped normally' or 'Camped on any cell' if 'suitable cell found' or 'acceptable cell found' respectively, or back to the initial 'no suitable/acceptable cell found' state if none found. + +Flowchart of Idle Mode Cell Selection and Reselection states and transitions. + +**Figure 2: Idle Mode Cell Selection and Reselection** +In any state, a new PLMN selection causes an exit to number 1 + +#### 5.2.2.1 Cell Selection process overview + +Whenever a PLMN has been selected by NAS, the UE shall attempt to find a suitable cell to camp on. + +The NAS may control the cell selection by: + +- providing information on RAT(s) associated with the selected PLMN; +- maintaining lists of forbidden registration areas; +- providing a list of equivalent PLMNs; + +One or several RATs may be associated with the selected PLMN. In [5] it is specified which RAT a UE shall select to search for a suitable cell of the selected PLMN. + +The AS shall attempt to find a suitable cell to camp on as specified in clause 5.2.3. + +When the MBMS frequency layer dispersion is triggered, the UE actions are specified in [4]. + +If a suitable cell is found, the UE shall select this cell to camp on, and report this event to NAS so that the necessary NAS registration procedures can be performed. When the registration is successful, the UE enters in state *Camped normally* in order to obtain normal service. + +If the UE is unable to find any suitable cell of selected PLMN the UE shall enter the *Any cell selection* state. + +#### 5.2.2.2 Camped normally state overview + +In this state, the UE obtains normal service and performs the tasks specified in 5.2.5. + +If after a *Cell reselection evaluation process* a better cell is found, the *Cell reselection procedure* is performed. If no suitable cell is found, the UE shall enter the state *Any cell selection*. + +If a necessary NAS registration is rejected, the UE shall enter the *Any cell selection* state, except if the LR is rejected with cause #12, cause #14, cause #15 or cause #25. In this case the UE shall behave as specified in [5] and [16]. + +When UE leaves idle mode in order to enter the state *Connected mode*, the UE shall attempt to access the current serving cell. If the access attempt to the serving cell fails, the UE shall use the *Cell reselection evaluation procedure*. + +#### 5.2.2.3 Connected mode State overview + +The procedures in *Connected mode* state are specified in [4] + +When returning to idle mode, the UE shall use the procedure *Cell selection when leaving connected mode* in order to find a suitable cell to camp on and enter state *Camped normally*. If a suitable cell is found, then the AS reports this event to NAS to be capable to perform necessary NAS registration procedures. If no suitable cell is found, the *Stored information cell selection procedure* shall be used. + +If no suitable cell is found in *cell reselection evaluation process*, the UE enters the state *Any cell selection*. + +#### 5.2.2.4 Any cell selection State overview + +In this state the UE performs the tasks specified in subclause 5.2.8 + +The state *Any cell selection* is also entered if the NAS indicates that a location registration is rejected except if the LR is rejected with cause #12, cause #14, cause #15 or cause #25, see [5] and [16], or if there is no USIM in the UE. + +If the UE received an LR reject with cause #12, cause #14, cause #15 or cause #25, the UE shall behave as specified in [5] and [16]. + +If an acceptable cell is found, the UE shall inform the NAS and camp on this cell and obtain limited service, state *Camped on any cell*. The subsequent actions of the NAS regarding the PLMN selection are specified in [5]. + +#### 5.2.2.5 Camped on any cell State overview + +In this state the UE obtains limited service and shall behave as specified in subclause 5.2.9. In this state if the UE supports CS voice services, the UE shall avoid reselecting an acceptable cell of E-UTRA regardless of priorities provided in system information of current cell. The UE shall regularly attempt to find a suitable cell, trying all RATs that are supported by the UE. If a suitable cell is found, this causes an exit to number 2 in figure 2. + +NOTE: The 'PLMN selection' process may select a new PLMN at any time in idle mode, which in Figure 2 causes an exit to number 1. + +### 5.2.3 Cell Selection Process + +#### 5.2.3.1 UTRA case + +##### 5.2.3.1.1 Description + +The UE shall use one of the following two search procedures: + +- a) Initial Cell Selection + + +This procedure requires no prior knowledge of which RF channels are UTRA carriers. The UE shall scan all RF channels in the UTRA bands according to its capabilities to find a suitable cell. On each carrier, the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be selected. +- b) Stored Information Cell Selection + + +This procedure requires stored information of carrier frequencies and optionally also information on cell parameters, e.g. scrambling codes, from previously received measurement control information elements. Once the UE has found a suitable cell the UE shall select it. If no suitable cell is found the Initial cell selection procedure shall be started. + +##### 5.2.3.1.2 Criteria + +The cell selection criterion S is fulfilled when: + +| | | +|----------------|------------------------------------| +| for FDD cells: | $S_{rxlev} > 0$ AND $S_{qual} > 0$ | +| for TDD cells: | $S_{rxlev} > 0$ | + +Where: + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $S_{qual} = Q_{qualmeas} - (Q_{qualmin} + Q_{qualminOffset}) - Q_{offsettemp}$ $S_{rxlev} = Q_{rxlevmeas} - (Q_{rxlevmin} + Q_{rxlevminOffset}) - P_{compensation} - Q_{offsettemp}$ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Where: + +the signalled values $Q_{qualminOffset}$ and $Q_{rxlevminOffset}$ are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic search for higher priority PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN. + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Squal | Cell Selection quality value (dB)
Applicable only for FDD cells. | +| Srxlev | Cell Selection RX level value (dB) | +| Qoffsettemp | Offset temporarily applied to a cell as specified in [4] (dB) | +| Qqualmeas | Measured cell quality value. The quality of the received signal expressed in CPICH $E_c/N_0$ (dB) for FDD cells. CPICH $E_c/N_0$ shall be averaged as specified in [10]. Applicable only for FDD cells. | +| Qrxlevmeas | Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) and P-CCPCH RSCP for TDD cells (dBm). | +| Qqualmin | Minimum required quality level in the cell (dB). Applicable only for FDD cells. | +| QqualminOffset | Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5] | +| Qrxlevmin | Minimum required RX level in the cell (dBm) | +| QrxlevminOffset | Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5] | +| Pcompensation | $\max(\text{UE\_TXPWR\_MAX\_RACH} - \text{P\_MAX}, 0)$ (dB) | +| UE_TXPWR_MAX_RACH | Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm) | +| P_MAX | Maximum RF output power of the UE (dBm) | + +#### 5.2.3.2 GSM case + +The cell selection criteria and procedures in GSM are specified in [1]. + +#### 5.2.3.3 E-UTRA case + +The cell selection criteria and procedures in E-UTRA are specified in [18]. + +#### 5.2.3.4 CSG cells and Hybrid cells in Cell Selection + +In addition to normal cell selection rules a manual selection of CSGs shall be supported by the UE upon request from higher layers as defined in subclause 5.6. + +### 5.2.4 Void + +### 5.2.5 Camped Normally State + +#### 5.2.5.1 UTRA case + +When camped normally, the UE shall perform the following tasks: + +- select and monitor the indicated PICH and PCH of the cell as specified in clause 8 according to information sent in system information; +- monitor relevant System Information. This is specified in [4]; +- perform necessary measurements for the cell reselection evaluation procedure; +- execute the cell reselection evaluation process on the following occasions/triggers: + - 1) UE internal triggers, so as to meet performance as specified in [10] and [11]; + - 2) When information on the BCCH used for the cell reselection evaluation procedure has been modified + +If the UE supports MBMS and MBMS is active in the cell and the UE is permitted to receive MBMS services in the cell, the UE shall perform MBMS tasks as specified in subclause 6.3. + +#### 5.2.5.2 GSM case + +The Camped Normally State is specified in [1]. + +#### 5.2.5.3 E-UTRA case + +The Camped Normally State is specified in [18]. + +### 5.2.6 Cell Reselection Evaluation Process + +#### 5.2.6.1 UTRA case + +The cell reselection process is specified in the following sub-clauses: + +##### 5.2.6.1.0 Use of MBMS PL + +In the cell reselection process, an MBMS PL shall only be applicable while the UE is receiving an MBMS session from one or more of the ongoing activated MBMS services for which this PL is indicated. + +##### 5.2.6.1.1 Measurement rules for cell re-selection when HCS is not used + +The measurement rules below apply in Idle, URA\_PCH, CELL\_PCH states. For FDD, 3.84 Mcps TDD and 7.68 Mcps TDD, in CELL\_FACH state the measurement rules below apply only if HS-DSCH discontinuous reception, with or without second DRX cycle, is configured, as specified in [4] and according to the requirements specified in [10]. Otherwise, the UE is required to perform measurements on all intra-frequency, inter-frequency and inter-RAT cells listed in system information according to requirements specified in [10]. For 1.28 Mcps TDD, in CELL\_FACH state the UE is required to perform measurements on all intra-frequency, inter-frequency and inter-RAT cells listed in system information according to requirements specified in [11]. In Idle, URA\_PCH, CELL\_PCH and CELL\_FACH states the UE shall only consider those cells the UE is mandated to measure according to the measurement rules below as measured cells in the cell reselection criteria (subclause 5.2.6.1.4). + +If the system information broadcast in the serving cell indicates that HCS is not used, then for intra-frequency and inter-frequency measurements and inter-RAT measurements, the UE shall: + +- use Squal for FDD cells and Srxlev for TDD for $S_x$ , and apply the following rules. + 1. If $S_x > S_{intraSearch}$ , UE may choose to not perform intra-frequency measurements. +If $S_x \leq S_{intraSearch}$ , perform intra-frequency measurements. +If $S_{intraSearch}$ is not sent for serving cell, perform intra-frequency measurements. + +If the system information broadcast in the serving cell indicates that HCS is not used and absolute priorities for inter-frequency layers are not provided, then for inter-frequency measurements the UE shall: + +2. If $S_x > S_{interSearch}$ and MBMS PL has not been indicated, and $S_{rxlev} > S_{searchHCS}$ if $S_{searchHCS}$ is signalled, UE may choose to not perform inter-frequency measurements. +If $S_x > S_{interSearch}$ and MBMS PL has been indicated and the serving cell belongs to the MBMS PL, and $S_{rxlev} > S_{searchHCS}$ if $S_{searchHCS}$ is signalled, UE may choose to not perform inter-frequency measurements. +If $S_x > S_{interSearch}$ , and MBMS PL has been indicated and the serving cell does not belong to the MBMS PL, and $S_{rxlev} > S_{searchHCS}$ if $S_{searchHCS}$ is signalled, UE shall at least perform inter-frequency measurements on the MBMS PL. +If $S_x \leq S_{interSearch}$ , or $S_{rxlev} \leq S_{searchHCS}$ if $S_{searchHCS}$ is signalled, perform inter-frequency measurements. +If $S_{interSearch}$ is not sent for serving cell, perform inter-frequency measurements. +If Dedicated CSG frequencies have been indicated by system information the UE may choose not to perform inter-frequency measurements of these frequencies. + +If the system information broadcast in the serving cell indicates that HCS is not used and absolute priorities for some inter-RAT layers are not provided, then for inter-RAT measurements on RATs for which absolute priority information is not provided the UE shall: + +3. If $S_x > S_{searchRAT\ m}$ , and $S_{rxlev} > S_{HCS,RAT\ m}$ if $S_{HCS,RAT\ m}$ is signalled, UE may choose to not perform measurements on cells of RAT "m". +If $S_x \leq S_{searchRAT\ m}$ , or $S_{rxlev} \leq S_{HCS,RAT\ m}$ if $S_{HCS,RAT\ m}$ is signalled, perform measurements on cells of RAT "m". +If $S_{searchRAT\ m}$ is not sent for serving cell, perform measurements on cells of RAT "m". + +If HCS is not used and if $S_{limit,SearchRAT\ m}$ is sent for serving cell, UE shall ignore it. + +NOTE: The presence of $S_{\text{searchHCS}}$ and $S_{\text{HCS,RATm}}$ thresholds in system information are used to avoid introducing new parameters to system information and their presence does not imply that HCS is used. + +##### 5.2.6.1.1a High-mobility state when HCS is not used + +High-mobility state, as applied in HCS case, is also applicable in non-HCS if the parameters non-HCS\_ $T_{\text{CRmax}}$ , non-HCS\_ $N_{\text{CR}}$ and non-HCS\_ $T_{\text{CRmaxHyst}}$ are sent on the system information broadcast. + +If in non-HCS environment the number of cell reselections during time period non-HCS\_ $T_{\text{CRmax}}$ exceeds non-HCS\_ $N_{\text{CR}}$ , or if the network (via RRC signalling) has ordered the UE to consider itself to be in high-mobility state, then high-mobility state has been detected. + +When the number of cell reselections during time period non-HCS\_ $T_{\text{CRmax}}$ no longer exceeds non-HCS\_ $N_{\text{CR}}$ , the UE shall: + +- continue in high-mobility state. +- if the criteria for entering high-mobility state is not detected during time period non-HCS- $T_{\text{CRmaxHyst}}$ : + - exit high-mobility state. + +If the UE is in non-HCS environment and in high-mobility state, the UE shall apply the speed dependent scaling rules as defined in subclause 5.2.6.1.4. + +##### 5.2.6.1.2 Measurement rules for cell re-selection when HCS is used + +The measurement rules below apply in Idle, URA\_PCH, CELL\_PCH states. For FDD, 3.84 Mcps TDD and 7.68 Mcps TDD, in CELL\_FACH state the measurement rules below apply only if HS-DSCH discontinuous reception, with or without second DRX cycle, is configured, as specified in [4] and according to the requirements specified in [10]. Otherwise, the UE is required to perform measurements on all intra-frequency, inter-frequency and inter-RAT cells listed in system information according to requirements specified in [10]. For 1.28 Mcps TDD, in CELL\_FACH state the UE is required to perform measurements on all intra-frequency, inter-frequency and inter-RAT cells listed in system information according to requirements specified in [11]. In Idle, URA\_PCH, CELL\_PCH and CELL\_FACH states the UE shall only consider those cells the UE is mandated to measure according to the measurement rules below as measured cells in the cell reselection criteria (subclause 5.2.6.1.4). + +The UE shall not use HCS for inter-frequency reselection if absolute priority based cell reselection (see subclause 5.2.6.1.4a) is used for inter-frequency reselection. The UE shall not use HCS for inter-RAT reselection if absolute priority based cell reselection (see subclause 5.2.6.1.4a) is used for that RAT. + +Use Squal for FDD cells and Srxlev for TDD cells for Sx and apply the following rules. + +If the system information broadcast in the serving cell indicates that HCS is used, then for intra-frequency and inter-frequency measurements, the UE shall: + +use HCS priority1 as the HCS priority broadcast in the system information and apply the following rule: + +IF an MBMS PL is used THEN + +- If the UE is not in high-mobility state, for serving cell and neighbour cells belonging to the MBMS PL set the HCS priority = HCS priority1 + HCS\_OFFmbms. +- If the UE is in high-mobility state, for serving cell and neighbour cells belonging to the MBMS PL set the HCS priority = HCS priority1. +- for serving cell and neighbour cells not belonging to the MBMS PL, set the HCS priority = HCS priority1. + +IF an MBMS PL is not used THEN + +For serving cell and all neighbour cells set HCS priority = HCS priority1 + +Then apply this to the following: + +1. For intra-frequency and inter-frequency measurement rules for UEs not in high-mobility state + +IF ( $S_{\text{rxlevs}} \leq S_{\text{searchHCS}}$ ) or (if FDD and $S_x \leq S_{\text{intersearch}}$ ) THEN + +measure on all intra-frequency and inter-frequency cells. + +ELSE + +IF ( $S_x > S_{\text{intrasearch}}$ ) THEN + +measure on all intra-frequency and inter-frequency cells, which have higher HCS priority level than the serving cell + +ELSE + +measure on all intra-frequency and inter-frequency cells, which have equal or higher HCS priority level than the serving cell + +ENDIF + +IF ( $S_{\text{intrasearch}}$ is not sent for the serving cell) THEN + +measure on all intra-frequency cells. UEs in high-mobility state may also use this rule. + +measure on all inter-frequency cells, which have higher HCS priority level than the serving cell unless measurement rules for UEs in high-mobility state are triggered. + +ENDIF + +ENDIF + +If HCS is used and if $S_{\text{searchHCS}}$ or $S_{\text{intersearch}}$ (in FDD) are not sent for the serving cell, UE shall: + +measure on all intra-frequency and inter-frequency cells. + +###### 2. For intra-frequency and inter-frequency measurement rules for UE's in high-mobility state: + +If the number of cell reselections during time period $T_{\text{CRmax}}$ exceeds $N_{\text{CR}}$ , or if the network (via RRC signalling) has ordered the UE to consider itself in high-mobility state, then high-mobility state has been detected. In this high-mobility state, the UE shall + +IF ( $S_{\text{rxlevs}} \leq S_{\text{searchHCS}}$ ) or (if FDD and $S_x \leq S_{\text{intersearch}}$ ), or $S_{\text{searchHCS}}$ or $S_{\text{intersearch}}$ (in FDD) are not sent for the serving cell THEN + +measure on all intra-frequency and inter-frequency cells. + +ELSE + +measure intra-frequency and inter-frequency neighbouring cells, which have equal or lower HCS priority than serving cell. + +ENDIF + +When the number of cell reselections during time period $T_{\text{CRmax}}$ no longer exceeds $N_{\text{CR}}$ , UE shall + +- continue these measurements during time period $T_{\text{CRmaxHyst}}$ +- if the criteria for entering high-mobility state is not detected during time period $T_{\text{CRmaxHyst}}$ : + - exit high-mobility state. + +If Dedicated CSG frequencies have been indicated by System Information the UE may choose not to perform inter-frequency measurements of these frequencies. + +When serving cell belongs to a hierarchical cell structure, the UE shall follow these rules for Inter-RAT measurements: + +###### 1. Inter-RAT threshold-based measurement rules for UEs not in high-mobility state + +IF ( $S_{\text{rxlevs}} \leq S_{\text{HCS,RATm}}$ ) or (if FDD and $S_x \leq S_{\text{SearchRATm}}$ ) THEN + +UE shall measure on all inter-RATm cells. + +ELSE + +IF ( $S_x > S_{\text{limit,SearchRATm}}$ ) THEN + +UE may choose to not measure neighbouring cells in RAT "m". + +ELSE + +UE shall measure on all neighbouring cells in RAT "m", which have equal or higher HCS priority level than the serving cell + +ENDIF + +ENDIF + +If HCS is used and if $S_{\text{HCS,RATm}}$ is not sent for the serving cell, UE shall measure on all inter-RATm cells. + +###### 2. Inter-RAT measurement rules for UEs in high-mobility state + +- If the number of cell reselections during time period $T_{\text{CRmax}}$ exceeds $N_{\text{CR}}$ , or if the network (via RRC signalling) has ordered the UE to consider itself in high-mobility state, then high-mobility state has been detected. In this high-mobility state, the UE shall + +- IF ( $S_{\text{rxlevs}} \leq S_{\text{HCS,RATm}}$ ) or (if FDD and $S_x \leq S_{\text{SearchRATm}}$ ), or $S_{\text{HCS,RATm}}$ or $S_{\text{SearchRATm}}$ are not sent for the serving cell THEN + +- UE shall measure on all inter-RATm cells. + +ELSE + +- measure the neighbouring cells in RAT "m", which have an equal or lower HCS priority than the serving cell + +- ENDIF + +When the number of cell reselections during time interval $T_{\text{CRmax}}$ no longer exceeds $N_{\text{CR}}$ , UE shall + +- continue these measurements during time period $T_{\text{CRmaxHyst}}$ + +- if the criteria for entering high-mobility state is not detected during time period $T_{\text{CRmaxHyst}}$ + +- exit high-mobility state. + +##### 5.2.6.1.2a Measurement rules for inter-frequency and inter-RAT cell reselection when absolute priorities are used + +The measurement rules below apply in Idle, URA\_PCH, CELL\_PCH states. In CELL\_FACH state, if (High Priority Layers is indicated in CELL\_FACH Absolute Priority Measurement Indicator [4] and $S_{\text{rxlevServingCell}} > S_{\text{prioritysearch1}}$ and $S_{\text{qualServingCell}} > S_{\text{prioritysearch2}}$ ) or (All Layers is indicated in CELL\_FACH Absolute Priority Measurement Indicator [4]) then the measurement rules below apply, otherwise the measurement rules in 5.2.6.1.1 and 5.2.6.1.2 apply. + +The UE is required to perform measurements of inter-frequency and inter-RAT cells listed in system information according to Measurement requirements are specified in [10]. UE specific priorities are not applied in camped on any cell state. + +If the UE has received absolute priority information for inter-frequency layers, the UE shall follow these rules: + +- The UE shall perform measurements of inter-frequency layers with a priority higher than the priority of the current serving layer. + +NOTE: The rate of these measurements may vary depending on whether $S_{\text{rxlev}}$ and $S_{\text{qual}}$ of the serving cell are above or below $S_{\text{prioritysearch1}}$ and $S_{\text{prioritysearch2}}$ . This is specified in [10]. + +- When the UE in *camped normally* state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of network configured values). +- For inter-frequency layers with a priority equal or lower than the priority of the current serving layer: + - If $Srxlev_{ServingCell} > S_{prioritysearch1}$ and $Squal_{ServingCell} > S_{prioritysearch2}$ the UE may choose not to perform measurements of inter-frequency layers of equal or lower priority. + - If $Srxlev_{ServingCell} \leq S_{prioritysearch1}$ or $Squal_{ServingCell} \leq S_{prioritysearch2}$ the UE shall perform measurements of inter-frequency layers of equal or lower priority. +- The UE may choose not to perform measurements of inter-frequency layers for which the UE has no absolute priority. + +If the UE has received absolute priority information for inter-RAT layers, the UE shall follow these rules: + +- The UE shall perform measurements of inter-RAT layers with a priority higher than the priority of the current serving cell. + +NOTE: The rate of these measurements may vary depending on whether $Srxlev$ and $Squal$ of the serving cell are above or below $S_{prioritysearch1}$ and $S_{prioritysearch2}$ . This is specified in [10]. + +- For inter-RAT layers with a priority lower than the priority of the current serving cell: + - If $Srxlev_{ServingCell} > S_{prioritysearch1}$ and $Squal_{ServingCell} > S_{prioritysearch2}$ the UE may choose not to perform measurements of inter-RAT layers of lower priority. + - If $Srxlev_{ServingCell} \leq S_{prioritysearch1}$ or $Squal_{ServingCell} \leq S_{prioritysearch2}$ the UE shall perform measurements of inter-RAT layers of lower priority. +- If absolute priority information is provided for any inter-RAT layers in a RAT, the UE may choose not to perform measurements on layers in that RAT for which the UE has no absolute priority. +- The UE shall perform measurements according to subclause 5.2.6.1.1 for inter-RAT layers for which the UE has no absolute priority. For all inter-RAT layers belonging to one RAT, either the rules above or the rules in subclause 5.2.6.1.1 or 5.2.6.1.2 shall apply. +- In CELL\_FACH state: If there are UTRAN inter-frequency, GERAN and E-UTRAN neighbours configured and required to be measured according to the measurement rules above, then the UE shall perform measurements on UTRAN inter-frequency and E-UTRAN layers (i.e. the UE is not required to measure GERAN, regardless of whether GERAN has absolute priorities assigned). + +##### 5.2.6.1.3 Highest ranked cells with cell reservations, access restrictions or unsuitable for normal camping + +For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.6.1.4, or for the best cell according to absolute priority reselection criteria specified in subclause 5.2.6.1.4a, the UE shall check if the access is restricted according to the rules in subclause 5.3.1.1. + +If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1.1, the UE shall not consider these as candidates for cell reselection. This limitation is removed when the highest ranked cell changes. + +If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list of forbidden LAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a maximum of 300s. If the UE has to perform an *any cell selection* procedure any limitation shall be removed. If the UE is redirected under UTRAN control to a frequency for which the timer is running, any limitation on that frequency shall be removed. + +If the highest ranked cell or best cell according to absolute priority reselection rules is an inter-RAT cell which is not suitable due to being part of the "list of forbidden LAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered PLMN, the UE shall not consider this cell and other cells on the same frequency as candidates for reselection for a maximum of 300s. If the UE has to perform an *any cell selection* procedure any + +limitation shall be removed. If the UE is redirected under UTRAN control to a frequency for which the timer is running, any limitation on that frequency shall be removed. + +##### 5.2.6.1.4 Cell Reselection Criteria + +The following cell re-selection criteria are used for intra-frequency cells, inter-frequency cells if no absolute priority information for any inter-frequency layer is available to the UE, and inter-RAT cells if no absolute priority information for any inter-RAT layer is available to the UE for that RAT. For inter-frequency and inter-RAT layers in a RAT for which absolute priorities are defined, then the cell reselection criteria in subclause 5.2.6.1.4a shall apply. + +The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised ranking according to hierarchical cell re-selection rules shall apply, and is defined by: + +$$\begin{aligned} H_s &= Q_{\text{meas},s} - Q_{\text{hcs},s} \\ H_n &= Q_{\text{meas},n} - Q_{\text{hcs},n} - TO_n * L_n \end{aligned}$$ + +If it is indicated in system information that HCS is not used, the quality level threshold criterion H is not applied. + +The cell-ranking criterion R is defined by: + +$$\begin{aligned} R_s &= Q_{\text{meas},s} + Q_{\text{hyst},s} + Q_{\text{offmbms}} - Q_{\text{offsettemp}} \\ R_n &= Q_{\text{meas},n} - Q_{\text{offsets},n} + Q_{\text{offmbms}} - TO_n * (1 - L_n) - Q_{\text{offsettemp}} \end{aligned}$$ + +where: + +- the signalled value $Q_{\text{offmbms}}$ is only applied to those cells (serving or neighbouring) belonging to the MBMS PL +- for a CSG cell not included in the neighbour cell list, then $Q_{\text{offsets},n}$ and $Q_{\text{offmbms}}$ have the value 0. + +where: + +$$\begin{aligned} TO_n &= \text{TEMP\_OFFSET}_n * W(\text{PENALTY\_TIME}_n - T_n) \\ L_n &= 0 \quad \text{if } \text{HCS\_PRIO}_n = \text{HCS\_PRIO}_s \\ L_n &= 1 \quad \text{if } \text{HCS\_PRIO}_n <> \text{HCS\_PRIO}_s \\ W(x) &= 0 \quad \text{for } x < 0 \\ W(x) &= 1 \quad \text{for } x \geq 0 \end{aligned}$$ + +$\text{TEMP\_OFFSET}_n$ applies an offset to the H and R criteria for the duration of $\text{PENALTY\_TIME}_n$ after a timer $T_n$ has started for that neighbouring cell. + +$\text{TEMP\_OFFSET}_n$ and $\text{PENALTY\_TIME}_n$ are only applicable if the usage of HCS is indicated in system information. + +For a CSG cell not included in the neighbour cell list, then $\text{TEMP\_OFFSET}_n$ has the value of 0. + +The timer $T_n$ is implemented for each neighbouring cell. $T_n$ shall be started from zero when one of the following conditions becomes true: + +- if $HCS\_PRIO_n \neq HCS\_PRIO_s$ and + +$$Q_{meas,n} \geq Q_{hcs,n}$$ + +Or + +- if $HCS\_PRIO_n = HCS\_PRIO_s$ and + - for serving FDD and neighbour FDD cells if the quality measure for cell selection and reselection is set to CPICH RSCP in the serving cell, and: + +$$Q_{meas,n} > Q_{meas,s} + Qoffset1_{s,n}$$ + +- for serving FDD and neighbour FDD cells if the quality measure for cell selection and reselection is set to CPICH Ec/No in the serving cell, and: + +$$Q_{meas,n} > Q_{meas,s} + Qoffset2_{s,n}$$ + +- for all other serving and neighbour cells: + +$$Q_{meas,n} > Q_{meas,s} + Qoffset1_{s,n}$$ + +$T_n$ for the associated neighbour cell shall be stopped as soon as any of the above conditions are no longer fulfilled. Any value calculated for $TO_n$ is valid only if the associated timer $T_n$ is still running else $TO_n$ shall be set to zero. + +At cell-reselection, a timer $T_n$ is stopped only if the corresponding cell is not a neighbour cell of the new serving cell, or if the criteria given above for starting timer $T_n$ for the corresponding cell is no longer fulfilled with the parameters of the new serving cell. On cell re-selection, timer $T_n$ shall be continued to be run for the corresponding cells but the criteria given above shall be evaluated with parameters broadcast in the new serving cell if the corresponding cells are neighbours of the new serving cell. + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $S_n$ | Cell Selection value of the neighbouring cell, (dB) | +| $Q_{meas}$ | Quality value. The quality value of the received signal derived from the averaged CPICH Ec/No or CPICH RSCP for FDD cells, from the averaged P-CCPCH RSCP for TDD cells and from the averaged received signal level for GSM cells. The averaging of these measurement quantities are performed as specified in [10] and [11]. For FDD cells, the measurement that is used to derive the quality value is set by the Cell selection and reselection quality measure information element. | + +Cell reselection parameters broadcast in system information are listed in subclause 5.2.6.1.5. + +The cell selection criterion S used for cell reselection is fulfilled when: + +| | | +|--------------------|------------------------------| +| for FDD cells: | $Srxlev > 0$ AND $Squal > 0$ | +| for TDD cells: | $Srxlev > 0$ | +| for GSM cells: | $Srxlev > 0$ | +| for E-UTRAN cells: | $Srxlev > 0$ AND $Squal > 0$ | + +Where : + +$$\begin{aligned} S_{qual} &= Q_{qualmeas} - Q_{qualmin} - Q_{offsettemp} \\ S_{rxlev} &= Q_{rxlevmeas} - Q_{rxlevmin} - P_{compensation} - Q_{offsettemp} \end{aligned}$$ + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| S qual | Cell Selection quality value (dB)
Applicable only for FDD cells and E-UTRA cells. | +| S rxlev | Cell Selection RX level value (dB) | +| Q offsettemp | Offset temporarily applied to a cell as specified in [4] (dB) | +| Q qualmeas | Measured cell quality value. The quality of the received signal expressed in CPICH E c /N 0 (dB) for FDD cells, and RSRQ for E-UTRA cells. CPICH E c /N 0 and RSRQ shall be averaged as specified in [10].
Applicable only for FDD cells and E-UTRA cells. | +| Q rxlevmeas | Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm), P-CCPCH RSCP for TDD cells (dBm), the averaged received signal level as specified in [10] for GSM cells (dBm) and the averaged RSRP as specified in [10] for E-UTRA cells (dBm). CPICH RSCP, P-CCPCH RSCP, the received signal level for GSM cells and the RSRP for E-UTRA cells shall be averaged as specified in [10] and [11]. | +| Q qualmin | Minimum required quality level in the cell (dB). Applicable only for FDD cells and E-UTRA cells. | +| Q rxlevmin | Minimum required RX level in the cell (dBm) | +| P compensation | max(UE_TXPWR_MAX_RACH - P_MAX, 0) (dB) | +| UE_TXPWR_MAX_RACH | Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm) | +| P_MAX | Maximum RF output power of the UE (dBm) | + +For a CSG cell not included in the neighbour cell list, the cell specific parameter values to be used shall be the same as the serving cell. + +If HCS is not used in the serving cell the UE shall perform ranking of all cells that fulfil the criterion S, among: + +- all measured cells (see subclause 5.2.6.1.1). + +If HCS is used in the serving cell, then from the cells that fulfil the criterion S, the UE shall perform ranking of all cells among + +1. when not in high-mobility state (see subclause 5.2.6.1.2), + - all measured cells, that have the highest HCS\_PRIO among those cells that fulfil the criterion $H \geq 0$ . + - all measured cells, not considering HCS priority levels, if no cell fulfil the criterion $H \geq 0$ . +2. when in high-mobility state (see subclause 5.2.6.1.2), + - all measured cells, and among these cells: + - if there are cells with a lower HCS priority than the serving cell that fulfil the criterion $H \geq 0$ : + - from the cells that have a lower HCS priority than the serving cell, all cells that have the highest HCS\_PRIO among those cells that fulfil the criterion $H \geq 0$ ; + - else: + - if there are cells that fulfil the criterion $H \geq 0$ with an HCS priority higher or equal to the HCS priority of the serving cell: + - from the cells that have an HCS priority higher or equal to the HCS priority of the serving cell, all cells that have the lowest HCS\_PRIO among those cells that fulfil the criterion $H \geq 0$ ; + - else + - all cells not considering HCS priority levels. + +The cells shall be ranked according to the R criteria specified above, deriving $Q_{meas,n}$ and $Q_{meas,s}$ and calculating the R values using CPICH RSCP, P-CCPCH RSCP and the averaged received signal level as specified in [10] and [11] for FDD, TDD and GSM cells, respectively. + +The offset $Q_{offset1,s,n}$ is used for $Q_{offset,s,n}$ to calculate $R_n$ , the hysteresis $Q_{hyst1,s}$ is used for $Q_{hyst,s}$ to calculate $R_s$ . For UE in RRC connected mode states CELL\_PCH or URA\_PCH the hysteresis $Q_{hyst,s}$ takes the value $Q_{hyst1,s,PCH}$ to calculate $R_s$ , if provided in SIB4 [see 4]. For UE in RRC connected mode state CELL\_FACH the hysteresis $Q_{hyst,s}$ takes the value $Q_{hyst1,s,FACH}$ to calculate $R_s$ , if provided in SIB4 [see 4]. + +If the usage of HCS is indicated in system information, $TEMP\_OFFSET1_n$ is used for $TEMP\_OFFSET_n$ to calculate $TO_n$ . If it is indicated in system information that HCS is not used, $TEMP\_OFFSET_n$ is not applied when calculating $R_n$ . The best ranked cell is the cell with the highest R value. + +If a TDD or GSM cell is ranked as the best cell, then the UE shall perform cell re-selection to that TDD or GSM cell. + +If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to CPICH RSCP, the UE shall perform cell re-selection to that FDD cell. If this cell is found to be not suitable, the UE shall behave according to subclause 5.2.6.1.3. + +If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to CPICH Ec/No, the UE shall perform a second ranking of the FDD cells according to the R criteria specified above, but using the measurement quantity CPICH Ec/No for deriving the $Q_{meas,n}$ and $Q_{meas,s}$ and calculating the R values of the FDD cells. The offset $Q_{offset2,s,n}$ is used for $Q_{offset,s,n}$ to calculate $R_n$ , the hysteresis $Q_{hyst2,s}$ is used for $Q_{hyst,s}$ to calculate $R_s$ . For UE in RRC connected mode states CELL\_PCH or URA\_PCH the hysteresis $Q_{hyst,s}$ takes the value $Q_{hyst2,s,PCH}$ to calculate $R_s$ , if provided in SIB4 [see 4]. For UE in RRC connected mode state CELL\_FACH the hysteresis $Q_{hyst,s}$ takes the value $Q_{hyst2,s,FACH}$ to calculate $R_s$ , if provided in SIB4 [see 4]. If the usage of HCS is indicated in system information, $TEMP\_OFFSET2_n$ is used to calculate $TO_n$ . If it is indicated in system information that HCS is not used, $TEMP\_OFFSET_n$ is not applied when calculating $R_n$ . Following this second ranking, the UE shall perform cell re-selection to the best ranked FDD cell. If this cell is found to be not suitable, the UE shall behave according to subclause 5.2.6.1.3. + +In all cases, the UE shall reselect the new cell, only if the following conditions are met: + +- the new cell is better ranked than the serving cell during the preceding time interval $Treselection$ . For UE in RRC connected mode states CELL\_PCH or URA\_PCH the interval $Treselection_{s,PCH}$ applies, if provided in SIB4 [see 4], while for UE in RRC connected mode state CELL\_FACH the interval $Treselection_{s,FACH}$ applies, if provided in SIB4 [see 4]. For hierarchical cell structures when high-mobility state has not been detected, if according to the HCS rules the serving cell is not ranked then all the ranked cells are considered to be better ranked than the serving cell. In case the UE reselects to a cell on an MBMS preferred frequency to receive an MBMS service not available on the current frequency the UE may reduce interval $Treselection_{s,PCH}$ and $Treselection_{s,FACH}$ . + +Additionally the UE shall apply the following scaling rules to $Treselection_s$ or $Treselection_{s,PCH}$ or $Treselection_{s,FACH}$ : + +- For intra-frequency cells and high-mobility state not detected: + - no scaling applied. +- For intra-frequency cells and high-mobility state is detected: + - multiply $Treselection_s$ or $Treselection_{s,PCH}$ or $Treselection_{s,FACH}$ by the IE "Speed dependent ScalingFactor for Treselection" if sent on system information. +- For inter-frequency cells and high-mobility state not detected: + - multiply $Treselection_s$ or $Treselection_{s,PCH}$ or $Treselection_{s,FACH}$ by the IE "Inter-frequency ScalingFactor for Treselection" if sent on system information. +- For inter-frequency cells and high-mobility state is detected: + - multiply $Treselection_s$ or $Treselection_{s,PCH}$ or $Treselection_{s,FACH}$ by both the IEs "Speed dependent ScalingFactor for Treselection" if sent on system information and "Inter-frequency ScalingFactor for Treselection" if sent on system information. + +- For inter-RAT cells and high-mobility state not detected: + - multiply $T_{reselection,s}$ or $T_{reselection,s,PCH}$ or $T_{reselection,s,FACH}$ by the IE "Inter-RAT ScalingFactor for Treselection" if sent on system information. +- For inter-RAT cells and high-mobility state is detected: + - multiply $T_{reselection,s}$ or $T_{reselection,s,PCH}$ or $T_{reselection,s,FACH}$ by both the IEs "Speed dependent ScalingFactor for Treselection" if sent on system information and "Inter-RAT ScalingFactor for Treselection" if sent on system information. + +In case scaling is applied to $T_{reselection,s}$ or $T_{reselection,s,PCH}$ , the UE shall round up the result after all scalings to the nearest second. In case scaling is applied to $T_{reselection,s,FACH}$ , the UE shall round up the result after all scalings to the nearest 0.2 seconds. + +- more than 1 second has elapsed since the UE camped on the current serving cell. +- For FDD the UE does not have an allocated common E-DCH resource. +- For 1.28 Mcps TDD, the UE does not have CELL Reselection Indication procedure ongoing. + +For FDD the UE continues taking intra-frequency measurements and ranking cells while it has an allocated common E-DCH resource. If supported by the UE and configured to perform Cell Reselection Indication Reporting, the UE shall inform the MAC layer that the cell reselection criteria are met. + +For 1.28 Mcps TDD, the UE continues taking measurements and ranking cells while it has the CELL Reselection Indication procedure ongoing as in [19]. + +##### 5.2.6.1.4a Absolute priority based criteria for inter-frequency and inter-RAT cell reselection + +Absolute priorities of different absolute priority layers may be provided to the UE. The following cell reselection criteria are used for inter-frequency cells if absolute priority information for inter-frequency is available to the UE, and inter-RAT cells if absolute priority information for inter-RAT is available to the UE. + +If System Information Block 18 with UTRAN information is provided then the UE shall apply the inter-frequency priority rules below only to UTRAN cells of the selected PLMN or equivalent PLMNs. If System Information Block 18 is not provided, or is provided but contains no information for UTRAN, then the rules below apply for the entire UTRAN RAT. + +If System Information Block 18 with GERAN information is provided then the UE shall apply the GERAN RAT priority rules below only to GERAN cells of the selected PLMN or equivalent PLMNs. If System Information Block 18 is not provided, or is provided but contains no information for GERAN, then the rules below apply for the entire GERAN RAT. + +If priority information is provided for any inter-frequency layers, cells belonging to inter-frequency layers for which no priority or no threshold is assigned shall not be considered for reselection. + +If priority information is provided for any inter-RAT layers in a RAT, cells belonging to layers in that RAT for which no priority or no threshold is assigned shall not be considered for reselection. + +If none of the inter-frequency layers in UTRAN are provided with both priority and threshold parameters, the cell reselection criteria in subclause 5.2.6.1.4 shall apply for inter-frequency layers in UTRAN. + +If none of the inter-RAT layers in a RAT are provided with both priority and threshold parameters, the cell reselection criteria in subclause 5.2.6.1.4 shall apply for that RAT. + +If both criteria in subclause 5.2.6.1.4 and criteria in subclause 5.2.6.1.4a are simultaneously fulfilled, the order in which the reselection criteria are evaluated is left to UE implementation. + +NOTE: In order not to apply absolute priority but the cell reselection criteria in subclause 5.2.6.1.4 for inter-frequencies cell reselection in UTRAN or for inter-RAT cell reselection, the network may choose to configure no inter-frequency layers in UTRAN or no inter-RAT layers in a RAT in SIB19 even though dedicated priorities are provided. + +For all inter-frequency layers or all inter-RAT layers belonging to one RAT, either the criteria below or the criteria in subclause 5.2.6.1.4 shall apply. + +The UE may apply either priorities broadcast in system information or priorities received through dedicated signalling. The rules regarding which set of priorities shall apply are defined in [4]. UE specific priorities shall be cleared when the validity time of the UE specific priorities expires, or when a PLMN selection is performed on request by NAS. UE specific priorities are not applied in camped on any cell state. + +When the UE in *camped normally* state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of network configured values). + +The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection. + +The following definitions apply for the layers for which $\text{Thresh}_{x,\text{high}2}$ or $\text{Thresh}_{x,\text{low}2}$ are not provided: + +- Criterion 1: the $\text{Srxlev}_{\text{nonServingCell},x}$ of a cell on an evaluated higher absolute priority layer is greater than $\text{Thresh}_{x,\text{high}}$ during a time interval $\text{Treselection}$ ; +- Criterion 2: ( $\text{Srxlev}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}}$ or $\text{Squal}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}2}$ ) and the $\text{Srxlev}_{\text{nonServingCell},x}$ of a inter-frequency cell on an evaluated equal absolute priority layer is greater than $\text{Thresh}_{x,\text{low}}$ during a time interval $\text{Treselection}$ ; +- Criterion 3: ( $\text{Srxlev}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}}$ or $\text{Squal}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}2}$ ) and the $\text{Srxlev}_{\text{nonServingCell},x}$ of a cell on an evaluated lower absolute priority layer is greater than $\text{Thresh}_{x,\text{low}}$ during a time interval $\text{Treselection}$ ; + +The following definitions apply for the layers for which both $\text{Thresh}_{x,\text{high}2}$ and $\text{Thresh}_{x,\text{low}2}$ are provided: + +- Criterion 4: the $\text{Squal}_{\text{nonServingCell},x}$ of a cell on an evaluated higher absolute priority layer is greater than $\text{Thresh}_{x,\text{high}2}$ during a time interval $\text{Treselection}$ ; +- Criterion 5: for FDD, ( $\text{Srxlev}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}}$ or $\text{Squal}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}2}$ ) and the $\text{Squal}_{\text{nonServingCell},x}$ of a cell on an evaluated lower absolute priority layer is greater than $\text{Thresh}_{x,\text{low}2}$ during a time interval $\text{Treselection}$ ; for 1.28 Mcps TDD, ( $\text{Srxlev}_{\text{ServingCell}} < \text{Thresh}_{\text{serving},\text{low}}$ ) and the $\text{Squal}_{\text{nonServingCell},x}$ of a cell on an evaluated lower absolute priority layer is greater than $\text{Thresh}_{x,\text{low}2}$ during a time interval $\text{Treselection}$ ; + +Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if criterion 1 or 4 is fulfilled. + +Cell reselection to an inter-frequency cell on an equal absolute priority layer to the camped frequency shall be performed if criterion 2 is fulfilled. + +Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3 or 5 is fulfilled. + +If more than one cell meets the above criteria, the UE shall reselect the cell with the highest $\text{Srxlev}_{\text{nonServingCell},x}$ among the cells meeting the criteria on the highest absolute priority layer. + +The UE shall not perform cell reselection to cells for which the cell selection criterion S is not fulfilled. + +The UE shall not perform cell reselection until more than 1 second has elapsed since the UE camped on the current serving cell. + +The UE shall not consider any black listed cells as candidate for cell reselection to E-UTRA. + +In CELL\_FACH state, the UE shall not perform cell reselection to E-UTRA when E-UTRA measurement for CELL\_FACH is configured. Except in the case that the cell reselection is to an E-UTRA CSG member cell, in this case cell reselection is performed as defined in [18]. + +The UE should not perform cell reselection while the UE has an allocated common E-DCH resource. + +For UE in RRC connected mode states CELL\_PCH or URA\_PCH the interval $\text{Treselection}_{s,\text{PCH}}$ applies, if provided in SIB4 (see [4]), while for UE in RRC connected mode state CELL\_FACH the interval $\text{Treselection}_{s,\text{FACH}}$ applies, if provided in SIB4 (see [4]). + +In all the above criteria the values of $\text{Treselection}_{s}$ , $\text{Treselection}_{s,\text{PCH}}$ or $\text{Treselection}_{s,\text{FACH}}$ apply for $\text{Treselection}$ and are scaled according to the UE mobility state, as specified in 5.2.6.1.1a. For UTRA cells apply the scaling rules in 5.2.6.1.4. For GSM cells apply the scaling rules in 5.2.6.1.4 if "GSM ScalingFactor for $\text{Treselection}$ " is not sent on system + +information, else follow the rules below for GSM. For EUTRA cells apply the scaling rules in 5.2.6.1.4 if "E-UTRA ScalingFactor for Treselection" is not sent on system information, else follow the rules below for EUTRA. + +- The UE shall apply the following scaling rules to Treselections or Treselections,PCH or Treselections,FACH: + - For inter-RAT cells and high-mobility state not detected: + - for GERAN cells multiply Treselections or Treselections,PCH or Treselections,FACH by the IE "GSM ScalingFactor for Treselection" if sent on system information. + - for EUTRA cells multiply Treselections or Treselections,PCH or Treselections,FACH by the IE "E-UTRA ScalingFactor for Treselection" if sent on system information. + - For inter-RAT cells and high-mobility state is detected: + - for GERAN cells multiply Treselections or Treselections,PCH or Treselections,FACH by both the IEs "Speed dependent ScalingFactor for Treselection" if sent on system information and "GSM ScalingFactor for Treselection" if sent on system information. + - for EUTRA cells multiply Treselections or Treselections,PCH or Treselections,FACH by both the IEs "Speed dependent ScalingFactor for Treselection" if sent on system information and "E-UTRA ScalingFactor for Treselection" if sent on system information. + +In case scaling is applied to Treselections or Treselections,PCH, the UE shall round up the result after all scalings to the nearest second. In case scaling is applied to Treselections,FACH, the UE shall round up the result after all scalings to the nearest 0.2 seconds. + +Cell reselection from UTRAN to E-UTRAN, for which Squal (RSRQ) based cell reselection parameters are broadcast in system information, shall be performed based on the Squal criteria (criterion 4 or 5) if the UE supports Squal based cell reselection from E-UTRAN to UTRAN. Otherwise, cell reselection to E-UTRAN shall be performed based on Srxlev criteria. + +##### 5.2.6.1.5 Cell reselection parameters in system information broadcasts + +The selection of values for network controlled parameters can be optimised by means of different methods. Examples of methods are described in [6]. Cell reselection parameters are broadcast in system information and are read in the serving cell as follows: + +###### **Qoffset1s,n** + +This specifies the offset between the two cells. It is used for TDD and GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP. + +###### **Qoffset2s,n** + +This specifies the offset between the two cells. It is used for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH Ec/No. + +###### **Qhyst1s** + +This specifies the hysteresis value (Qhyst). It is used for TDD and GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP. + +###### **Qhyst1s,PCH** + +This specifies the hysteresis value (Qhyst) to be used in RRC connected mode states CELL\_PCH and URA\_PCH. It is used for TDD and GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP. If this parameter is not provided in SIB4, Qhyst1s shall be used. + +###### **Qhyst1s,FACH** + +This specifies the hysteresis value (Qhyst) to be used in RRC connected mode state CELL\_FACH. It is used for TDD and GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP. If this parameter is not provided in SIB4, Qhyst1s shall be used. + +###### **Qhyst2s** + +This specifies the hysteresis value (Qhyst). It is used for FDD cells if the quality measure for cell selection and re-selection is set to CPICH Ec/No. + +###### **Qhyst2s,PCH** + +This specifies the hysteresis value (Qhyst) to be used in RRC connected mode states CELL\_PCH and URA\_PCH. It is used for FDD cells if the quality measure for cell selection and re-selection is set to CPICH Ec/No. If this parameter is not provided in SIB4, Qhyst2s shall be used. + +###### **Qhyst2s,FACH** + +This specifies the hysteresis value (Qhyst) to be used in RRC connected mode state CELL\_FACH. It is used for FDD cells if the quality measure for cell selection and re-selection is set to CPICH Ec/No. If this parameter is not provided in SIB4, Qhyst2s shall be used. + +###### **HCS\_PRIOs, HCS\_PRIOn** + +This specifies the HCS priority level (0-7) for serving cell and neighbouring cells. + +HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. + +###### **HCS\_OFFmbms** + +This specifies the offset to the normal HCS priority level that is used for cells belonging to the MBMS PL. + +###### **Qhcss, Qhcsn** + +This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection. + +###### **Qoffmbms** + +This specifies the additional offset added to cells belonging to the MBMS PL. + +###### **Qoffsettemp** + +This specifies the additional offset to be used for cell selection and re-selection. It is temporarily used for FDD cells in case the RRC Connection Establishment fails on the cell as specified in [4]. + +###### **Qqualmin** + +This specifies the minimum required quality level in the cell in dB. It is not applicable for TDD cells or GSM cells. + +###### **Qrxlevmin** + +This specifies the minimum required RX level in the cell in dBm. + +###### **PENALTY\_TIMEn** + +This specifies the time duration for which the TEMPORARY\_OFFSETn is applied for a neighbouring cell. + +###### **TEMPORARY\_OFFSET1n** + +This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY\_TIMEn. It is used for TDD and GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP. + +###### **TEMPORARY\_OFFSET2n** + +This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY\_TIMEn. It is used for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH Ec/No. + +###### **TCRmax** + +This specifies the duration for evaluating allowed amount of cell reselection(s). + +###### **NCR** + +This specifies the maximum number of cell reselections. + +###### **TCRmaxHyst** + +This specifies the additional time period before the UE can exit high-mobility. + +###### **non-HCS\_TCRmax** + +This specifies the duration for evaluating allowed amount of cell reselection(s) in case of non-HCS usage. + +###### **non-HCS\_NCR** + +This specifies the maximum number of cell reselections in case of non-HCS usage. + +###### **non-HCS\_TCRmaxHyst** + +This specifies the additional time period before the UE can revert to low-mobility measurements in case of non-HCS usage. + +##### **Treselection** + +This specifies the cell reselection timer value. + +###### **Treselection,s,PCH** + +This specifies the cell reselection timer value the UE shall use in RRC connected mode states CELL\_PCH and URA\_PCH if provided in SIB4, otherwise Treselection shall be used. + +###### **Treselection,s,FACH** + +This specifies the cell reselection timer value the UE shall use in RRC connected mode state CELL\_FACH if provided in SIB4, otherwise Treselection shall be used. + +###### **SqualServingCell** + +This is the Squal value of the serving cell. + +###### **SsearchHCS** + +This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell. + +###### **SsearchRAT i - SsearchRAT k** + +This specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. + +###### **SHCS,RATm** + +This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. + +###### **Sintrasearch** + +This specifies the threshold (in dB) for intra frequency measurements and for the HCS measurement rules. + +###### **Sintersearch** + +This specifies the threshold (in dB) for inter-frequency measurements and for the HCS measurement rules. + +###### **Slimit,SearchRATm** + +This threshold is used in the measurement rules for cell re-selection when HCS is used. It specifies the RAT specific threshold (in dB) in the serving UTRA cell above which the UE may choose to not perform any inter-RAT measurements in RAT "m". + +###### **SrxlevnonServingCell,x** + +This is the Srxlev value of an evaluated neighbour cell on an absolute priority layer. + +###### **SrxlevServingCell** + +This is the Srxlev value of the serving cell. + +###### **Sprioritysearch1** + +This threshold is used in the measurement rules for cell re-selection when absolute priorities are used. It specifies the value of Srxlev in the serving cell controlling the rate of inter-frequency and inter-RAT measurements. + +###### **Sprioritysearch2** + +This threshold is used in the measurement rules for cell re-selection when absolute priorities are used. It specifies the value of Squal in the serving cell controlling the rate of inter-frequency and inter-RAT measurements. + +###### **Speed dependent ScalingFactor for Treselection** + +This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselections or Treselections,PCH or Treselections,FACH in case high-mobility state has been detected. + +###### **Inter-frequency ScalingFactor for Treselection** + +This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case. + +###### **Inter-RAT ScalingFactor for Treselection** + +This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case. + +##### **GSM ScalingFactor for Treselection** + +This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the GSM case. This scaling is only applicable at absolute priority based criteria for cell reselection to GSM. + +###### **E-UTRA ScalingFactor for Treselection** + +This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the EUTRA case. This scaling is only applicable at absolute priority based criteria for cell reselection to EUTRA. + +###### **Threshx,high** + +A Srxlev based threshold used by the UE for cell reselection towards a higher absolute priority layer when absolute priorities are applied. A threshold is defined for each absolute priority layer. + +###### **Threshx,high2** + +A Squal based threshold used by the UE for cell reselection towards a higher absolute priority layer when absolute priorities are applied. A threshold is defined for each absolute priority layer. + +###### **Threshx,low** + +A Srxlev based threshold used by the UE for cell reselection towards an equal or lower absolute priority layer when absolute priorities are applied. A threshold is defined for each absolute priority layer. + +###### **Threshx,low2** + +A Squal based threshold used by the UE for cell reselection towards a lower absolute priority layer when absolute priorities are applied. A threshold is defined for each absolute priority layer. + +###### **Threshserving,low** + +This threshold is used in the rules for cell reselection when absolute priorities are used. It specifies the limit for Srxlev in the serving cell below which the UE may perform cell reselection to a cell on an equal or lower absolute priority layer. + +###### **Threshserving,low2** + +This threshold is used in the rules for cell reselection when absolute priorities are used. It specifies the limit for Squal in the serving cell below which the UE may perform cell reselection to a cell on an equal or lower absolute priority layer. + +##### **Dedicated CSG frequency** + +This specifies a frequency which is used for CSG deployment only. + +#### **5.2.6.2 GSM case** + +The cell reselection procedure in GSM, including reselection from GSM to UTRA, is specified in [1]. + +#### **5.2.6.3 E-UTRA case** + +The cell reselection procedure in E-UTRA, including inter-RATs reselection, is specified in [18]. + +#### **5.2.6.4 Cell reselection with CSG cells** + +##### **5.2.6.4.1 Cell reselection from a non-CSG cell to a CSG cell** + +In addition to normal cell reselection, the UE shall use an autonomous search function to detect at least previously visited CSG member cells on serving frequency, non serving frequencies and inter-RAT frequencies, according to the performance requirements specified in [10], when at least one CSG with associated PLMN identity ID is included in the UE's CSG whitelist. The UE is required to perform autonomous search function in Idle, Cell\_PCH, URA\_PCH and CELL\_FACH states. For CELL\_FACH, the autonomous search function for reselection to non-serving frequencies and inter-RAT frequencies needs only to be performed when second DRX is used. The UE shall disable the autonomous search function for CSG cells if the UE's CSG whitelist is empty. If "Dedicated CSG frequency(ies) " IE is present, the UE may use the autonomous search function only on these dedicated frequencies and on the other frequencies listed in the system information. + +NOTE: The UE autonomous search function, per UE implementation, determines when and/or where to search for CSG member cells. + +When the UE has no or an empty CSG whitelist, the UE may ignore cells with PSC in the stored range "CSG PSC Split Information" [4] reserved for CSG cells for intra-frequency and inter-frequency measurements and cell re-selections. + +If the UE detects a suitable CSG cell on the same frequency it shall reselect this cell if the concerned CSG cell is the highest ranked cell, according to 5.2.6.1.4. + +If the UE detects a suitable CSG cell on a different frequency it shall reselect this cell irrespective of the cell reselection rules applicable for the cell the UE is currently camped on, if the detected suitable CSG cell is the strongest cell on that frequency. If suitable CSG cells are detected on different frequencies and these are the strongest cells on their frequencies, then the UE shall reselect to any one of them. + +If the UE detects one or more suitable CSG cell on another RAT, the UE shall reselect to one of them according to [18]. + +##### **5.2.6.4.2 Cell reselection from a CSG cell to non-CSG cell** + +While camped on a suitable CSG cell, the UE shall consider the frequency of the serving cell to be the highest priority frequency (i.e. higher than any of network configured values or highest HCS priority) and shall not reselect to non-CSG cell as long as the serving cell remains the highest ranked cell on that frequency (This includes the case when the UE has only dedicated priorities for other frequencies but not for the current frequency, i.e. the UE does not consider the current frequency to be the lowest priority frequency according to rules in 5.2.6.1.2a and 5.2.6.1.4a). Cell reselection rules as defined in section 5.2.6.1 are applied for cell reselection from a CSG cell to non-CSG cell. + +##### **5.2.6.4.3 Cell reselection from a CSG cell to a CSG cell** + +To search for CSG cells not listed in the system information of the serving CSG cell, the UE may use the autonomous search function when at least one CSG ID with associated PLMN identity is included in the UE's CSG whitelist. The UE is required to perform autonomous search function in Idle, Cell\_PCH, URA\_PCH and CELL\_FACH states. For + +CELL\_FACH, the autonomous search function for reselection to non-serving frequencies and inter-RAT frequencies needs only to be performed when second DRX is used. If "Dedicated CSG frequency(ies)" IE is present, the UE may use the autonomous search function only on dedicated frequencies and on other frequencies listed in the system information. + +If the UE detects a suitable CSG cell on the same frequency, it shall reselect to this cell if the concerned CSG cell is the highest ranked cell, according to 5.2.6.1.4. + +While camped on a suitable CSG cell, the UE shall consider the frequency of the serving cell to be the highest priority frequency (i.e. higher than any of network configured values or highest HCS priority) as long as the serving cell is the highest ranked cell on that frequency (This includes the case when the UE has only dedicated priorities for other frequencies but not for the current frequency, i.e. the UE does not consider the current frequency to be the lowest priority frequency according to rules in 5.2.6.1.2a and 5.2.6.1.4a). + +If the UE detects one or more suitable CSG cell on another RAT, the UE may reselect to one of them according to [18]. + +For reselection to neighbour CSG cells listed in the system information of the serving CSG cell the UE shall apply cell measurement rules according to 5.2.6. If the UE detects a suitable CSG cell that is listed in the system information of the serving cell on other frequencies, and the detected CSG cell is the strongest cell on that frequency, then the UE shall consider these frequencies to have a priority equal to the current frequency and shall follow cell reselection rules according to 5.2.6.1.4 and 5.2.6.1.4a. + +#### 5.2.6.5 Cell Reselection with Hybrid Cells + +In addition to normal cell reselection rules, the UE shall use an autonomous search function to detect at least previously visited hybrid cells whose CSG ID and associated PLMN identity is in the UE's CSG whitelist according to the performance requirements specified in [10]. The UE shall treat detected hybrid cells as CSG cells if the CSG ID and any of the broadcasted PLMN identity of the hybrid cell is in the UE's CSG whitelist and as normal cells otherwise. + +### 5.2.7 Cell Selection when leaving connected mode + +#### 5.2.7.1 UTRA case + +When returning to idle mode from connected mode, the UE shall select a suitable cell to camp on. Candidate cells for this selection are the cell(s) used immediately before leaving connected mode. If no suitable cell is found, the UE shall use the Stored information cell selection procedure in order to find a suitable cell to camp on. + +When returning to idle mode after an emergency call on any PLMN, the UE shall select an acceptable cell to camp on. Candidate cells for this selection are the cell(s) used immediately before leaving connected mode. If no acceptable cell is found, the UE shall continue to search for an acceptable cell of any PLMN in state Any cell selection. + +#### 5.2.7.2 GSM case + +Cell selection when leaving connected mode in GSM is specified in [1]. + +#### 5.2.7.3 E-UTRA case + +Cell selection when leaving connected mode in E-UTRA is specified in [18]. + +### 5.2.8 Any Cell Selection state + +In this state, the UE shall attempt to find an acceptable cell of an any PLMN to camp on, trying all RATs that are supported by the UE and searching first for a high quality cell, as defined in subclause 5.1.2.2. + +The UE, which is not camped on any cell, shall stay in this state until an acceptable cell is found. + +### 5.2.9 Camped on Any Cell State + +#### 5.2.9.1 UTRA case + +In this state, the UE shall perform the following tasks: + +- select and monitor the indicated PICH and PCH of the cell as specified in clause 8; + +- monitor relevant System Information; This is specified in [4]; +- perform necessary measurements for the cell reselection evaluation procedure; +- Execute the cell reselection evaluation process on the following occasions/triggers: + - 1) UE internal triggers, so as to meet performance as specified in [10] and [11]; + - 2) When information on the BCCH used for the cell reselection evaluation procedure has been modified; +- regularly attempt to find a suitable cell trying all RATs that are supported by the UE. If a suitable cell is found, this causes an exit to number 2 in Figure 2. + +In this state the UE is not permitted to receive any MBMS services. + +#### 5.2.9.2 GSM case + +The camped on any cell state in GSM is specified in [1]. + +#### 5.2.9.3 E-UTRA case + +The camped on any cell state in E-UTRA is specified in [18]. + +## 5.3 Cell Reservations and Access Restrictions (cells not operating in MBSFN mode) + +### 5.3.1 UTRA cells + +There are two mechanisms which allow an operator to impose cell reservations or access restrictions. The first mechanism uses indication of cell status and special reservations for control of cell selection and re-selection procedures. The second mechanism, referred to as Access Control, shall allow to prevent selected classes of users from sending initial access messages for load control reasons. At subscription, one or more Access Classes are allocated to the subscriber and stored in the USIM [9], which are employed for this purpose. + +#### 5.3.1.1 Cell status and cell reservations + +Cell status and cell reservations are indicated with the *Cell Access Restriction* Information Element in the System Information Message [4] by means of four Information Elements: + +- Cell barred (IE type: "barred" or "not barred"), +- Cell Reserved for operator use (IE type: "reserved" or "not reserved"), +- Cell reserved for future extension (IE type: "reserved" or "not reserved"). +- Cell reserved for CSG (IE type: "true" or not present). + +When cell status is indicated as "not barred", "not reserved" for operator use and "not reserved" for future extension (Cell Reservation Extension), + +- All UEs shall treat this cell as candidate during the cell selection and cell re-selection procedures in Idle mode and in Connected mode. + +When cell status is indicated as "not barred", "not reserved" for operator use and "reserved" for future extension (Cell Reservation Extension), + +- If Cell Reserved for CSG is indicated then CSG capable UEs shall behave as if cell status is indicated as "not reserved" for future extension (Cell Reservation Extension). +- If Cell Reserved for CSG is not indicated then UEs shall behave as if cell status "barred" is indicated using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator" and the maximum value for $T_{\text{barred}}$ , see [4] (see also below). + +When cell status is indicated as "not barred" and "reserved" for operator use, + +- If the UE is assigned an Access Class 11 or 15 and if the cell belongs to the home PLMN or to any EHPLMN: + - the UE shall treat this cell as candidate during the cell selection and cell re-selection procedures in Idle mode and in Connected mode. +- else: + - UEs shall behave as if cell status "barred" is indicated using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator" and the maximum value for $T_{\text{barred}}$ , see [4] (see also below). + +When cell status "barred" is indicated, + +- The UE is not permitted to select/re-select this cell, not even for emergency calls. +- The UE shall ignore the "Cell Reserved for future extension (Cell Reservation Extension) use" IE. +- The UE is not permitted to receive any MBMS services. +- The UE shall select another cell according to the following rule: + - If the "Intra-frequency cell re-selection indicator" IE in Cell Access Restriction IE is set to value "allowed", the UE may select another cell on the same frequency if selection/re-selection criteria are fulfilled. + - If the UE is camping on another cell, the UE shall exclude the barred cell from the neighbouring cell list until the expiry of a time interval $T_{\text{barred}}$ . The time interval $T_{\text{barred}}$ is sent via system information in a barred cell together with Cell status information in the Cell Access Restriction IE. + - If the UE does not select another cell, and the barred cell remains to be the "best" one, the UE shall after expiry of the time interval $T_{\text{barred}}$ again check whether the status of the barred cell has changed. + - If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall not re-select a cell on the same frequency as the barred cell. During an ongoing emergency call, the Intra-frequency cell re-selection indicator IE shall be ignored, i.e. even if it is set to "not allowed" the UE may select another intra-frequency cell. + - If the barred cell remains to be the "best" one, the UE shall after expiry of the time interval $T_{\text{barred}}$ again check whether the status of the barred cell has changed. + +If the "Intra-frequency cell re-selection indicator" IE has been read from a CSG cell it shall be ignored by the UE and the UE is allowed to reselect another cell on the same frequency if the cell reselection criteria are fulfilled. + +The reselection to another cell may also include a change of RAT. + +#### 5.3.1.2 Access Control + +Information on cell access restrictions associated with the Access Classes and ACDC are broadcast as system information, [4]. + +The UE shall ignore Access Class related cell access restrictions when selecting a cell to camp on, i.e. it shall not reject a cell for camping on because access on that cell is not allowed for any of the Access Classes of the UE. A change of the indicated access restriction shall not trigger cell re-selection by the UE. + +Access Class related cell access restrictions shall be checked by the UE before sending an RRC CONNECTION REQUEST message when entering Connected Mode from UTRAN Idle mode. Access Class related cell access restrictions, if it is sent as a part of Domain Specific Access Restriction parameters, shall also be checked by the UE before sending INITIAL DIRECT TRANSFER message. Access Class related cell access restrictions, if it is sent as a part of Paging Permission with Access Control Parameters, shall be checked by the UE before sending a response to Paging message or before initiating a Location/Registration procedure. Access Class related cell access restrictions, if it is sent as a part of Extended Access Barring parameters, shall be checked by the UE before sending an RRC CONNECTION REQUEST message or INITIAL DIRECT TRANSFER message subject to extended access barring as indicated by higher layers. Otherwise, cell access restrictions associated with the Access Classes shall not apply for a UE which already is in Connected Mode. + +For Access Class 0 to 9, ACDC related cell access restrictions, if it is sent in ACDC Barring Information parameters shall be checked by the UE before sending an RRC CONNECTION REQUEST message when entering Connected Mode from UTRAN Idle mode in PS domain. + +#### 5.3.1.3 Emergency Call + +A restriction on emergency calls, if needed, shall be indicated in the "Access class barred list" IE [4]. If access class 10 is indicated as barred in a cell, UEs with access class 0 to 9 or without an IMSI are not allowed to initiate emergency calls in this cell. For UEs with access classes 11 to 15, emergency calls are not allowed if both access class 10 and the relevant access class (11 to 15) are barred. Otherwise, emergency calls are allowed for those UEs. + +Full details of operation under "Access class barred list" are described in [9]. + +### 5.3.2 GSM cells + +The cell access restrictions applicable to GSM are specified in [1]. + +### 5.3.3 E-UTRA cells + +The cell access restrictions applicable to E-UTRA are specified in [18]. + +## 5.3a Cell Reservations and Access Restrictions (MBSFN cells only for FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD) + +For an MBSFN cluster (see [4]) when cell status is indicated "not reserved" for operator use and "not reserved" for future extension (Cell Reservation Extension), and Cell Barred is set to "barred" or "not barred", + +- All UEs shall treat this MBSFN cluster as a candidate during the MBSFN cluster selection and MBSFN cluster re-selection procedures. + +For an MBSFN cluster (see [4]) when cell status is indicated as "not reserved" for operator use and "reserved" for future extension (Cell Reservation Extension), + +- UEs shall not consider this MBSFN cluster as a candidate during the MBSFN cluster selection and MBSFN cluster re-selection procedures. The UE may choose to not recheck the status of this MBSFN cluster during the time corresponding to the maximum value for $T_{\text{barred}}$ (see [4]). + +For an MBSFN cluster (see [4]) when cell status is indicated as "reserved" for operator use, + +- if a UE is assigned to Access Class 11 or 15 and the MBSFN cluster belongs to the home PLMN or to any EHPLMN: + - the UE shall treat this MBSFN cluster as a candidate during the MBSFN cluster selection and MBSFN cluster re-selection procedures. +- else: + - UEs shall not consider this MBSFN cluster as candidate during the MBSFN cluster selection and MBSFN cluster re-selection procedures The UE may choose to not recheck the status of this MBSFN cluster during the time corresponding to the maximum value for $T_{\text{barred}}$ (see [4]). + +NOTE: The UE should in all cases assume "intra-frequency cell re-selection" has the value "allowed". + +## 5.4 Cell Selection and Reselection Processes in RRC Connected Mode + +### 5.4.1 Void + +### 5.4.2 Void + +### 5.4.3 Cell Reselection Process in RRC connected mode + +The *cell reselection* process in Connected Mode is the same as *cell reselection evaluation process* used for idle mode, described in subclause 5.2.6. + +### 5.4.4 Cell Selection Process in RRC connected mode + +The *cell selection* process in Connected Mode is for 'out of service' conditions [4] is the same as the *cell selection process* used for idle mode, described in subclause 5.2.3. + +Selection of a suitable cell during a state transition or a change of frequency in Connected Mode is the same as the selection of a suitable UTRA cell used for idle mode, described in subclause 5.2.3.1. If the UE is ordered to select a suitable UTRA cell on a given frequency, it shall attempt to select a suitable cell on that frequency before considering cells on other frequencies. + +## 5.5 Location Registration + +In the UE, the AS shall report registration area information to the NAS. + +If the UE reads more than one PLMN identity in the current cell, the UE shall report the found PLMN identities that make the cell suitable in the registration area information to NAS. + +The non-access part of the location registration process is specified in [5]. + +Actions for the UE AS upon reception of Location Registration reject are specified in [9] and [16]. + +## 5.6 Support for manual CSG Selection + +### 5.6.1 UTRA case + +In the UE on request of NAS, the AS shall scan all RF channels in the UTRA bands according to its capabilities to find available CSGs. On each carrier, the UE shall at least search for the strongest cell, read its system information and report available CSG ID(s) together with their "HNB name" (if broadcast) and PLMN(s) to the NAS. The search for available CSGs may be stopped on request of the NAS. + +If NAS has selected a CSG and provided this selection to AS, the UE shall search for an acceptable or suitable cell belonging to the selected CSG to camp on. + +### 5.6.2 E-UTRA case + +Support for manual CSG selection in E-UTRA is described in [18]. + +## 5.7 Logged Measurements + +The UE may be configured to perform logging of measurement results in idle mode, CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used with LOGGING MEASUREMENT CONFIGURATION message specified in TS 25.331 [4]. This configuration is valid while the logging duration timer is running. + +If the configuration of logged measurements is valid, the UE shall perform logging of measurement results if all of the following conditions are met: + +- the UE is in *camped normally* state in idle mode, CELL\_PCH or URA\_PCH states or CELL\_FACH state when second DRX cycle is used; +- the RPLMN of the UE is present in the MDT PLMN identity list, if received in the LOGGING MEASUREMENT CONFIGURATION message, or the RPLMN of the UE is the same as the RPLMN at the point of time of LOGGING MEASUREMENT CONFIGURATION message reception; +- the UE is camped on a cell belonging to Area Configuration (see TS 25.331 [4]), if configured; +- the UE is camped on the RAT where the logged measurement configuration was received. + +Otherwise, the logging of measurement results shall be suspended. + +NOTE: Even if logging of measurement results is suspended, the logging duration timer and time stamp will continue, and the logged measurement configuration and corresponding log are kept. + +## 5.8 Logged UTRAN ANR + +### 5.8.1 General + +The UE may be configured to perform UTRAN ANR measurement and logging in IDLE mode, CELL\_PCH, URA\_PCH state and CELL\_FACH state when second DRX cycle is used with Logging Measurement Configuration message as specified in [4]. If configured, the UE will + +- perform measurements and evaluation on the cells which are not included in the neighbour cell list in IDLE mode, CELL\_PCH, URA\_PCH state and CELL\_FACH state when second DRX cycle is used. +- log information of the detected cells meeting the logging rules as specified in [4]. + +### 5.8.2 UTRAN ANR measurement process + +#### 5.8.2.1 Intra-freq and inter-freq ANR case + +If configured via the Logging Measurement Configuration message, the UE may perform intra-freq and inter-freq ANR measurements and logging only when: + +- in IDLE mode, CELL\_PCH, URA\_PCH state and CELL\_FACH state when second DRX cycle is used. +- the UE is camping normally on a UTRAN cell belonging to the PLMN or the list of Equivalent PLMNs where the Logging Measurement Configuration is received. + +During the intra-freq and inter-freq ANR process, the UE may measure on the frequencies associated with the cells listed in the neighbour cell list and log corresponding information of the detected set cells as specified in TS 25.331 [4]. + +#### 5.8.2.2 Inter-RAT ANR case + +If configured to perform inter-RAT ANR via the Logging Measurement Configuration message, the UE may perform inter-RAT ANR logging only when: + +- after inter-RAT cell reselection from E-UTRAN or GSM to a normal UTRAN cell belonging to the PLMN or the list of Equivalent PLMNs where the Logging Measurement Configuration is received. + +During the inter-RAT ANR process, the UE may log the corresponding information of the previously camped E-UTRAN or GSM cell as specified in TS 25.331 [4]. + +## 5.9 Accessibility measurements + +The UE logs failure information when the RRC connection establishment procedure fails as specified in TS 25.331 [4]. + +## 5.10 RAN-assisted WLAN interworking + +The purpose of this procedure is to facilitate RAN-assisted WLAN interworking. + +### 5.10.1 RAN assistance parameter handling in Idle mode, CELL\_PCH, URA\_PCH and CELL\_FACH + +UEs in idle mode or in CELL\_FACH, CELL\_PCH or URA\_PCH state shall store and apply RAN assistance parameters for the rules in sub-clause 5.10.2 as defined in the following: + +- RAN assistance parameters received in System information block type 23 are used only if the UE is in camped *normally* state; +- upon cell reselection, and cell selection to another cell than the serving cell (or the best cell in case of UEs previously in CELL\_DCH state and configured with DCHs only), the UE shall discard the RAN assistance parameters received in the UTRAN MOBILITY INFORMATION message or in the CELL UPDATE CONFIRM message and apply the RAN assistance parameters received in System information block type 23. + +### 5.10.2 Access network selection and traffic steering rules + +The rules in this sub-clause are only applicable for WLANs for which identifiers have been signaled to the UE by UTRAN and the UE is capable of access network selection and traffic steering rules. Coexistence with ANDSF based WLAN selection and traffic steering methods on the UE is based on mechanism described in TS 23.402 [23]. The rules refer to the following WLAN quantities: + +| | | +|------------------------|---------------------------------------------------------------------| +| ChannelUtilizationWLAN | WLAN channel utilization as defined in sub-clause 8.4.2.30 in [24]. | +| BackhaulRateDIWLAN | WLAN DLBandwidth as defined in sub-clause 9.1.2 in [25]. | +| BackhaulRateUIWLAN | WLAN ULBandwidth as defined sub-clause 9.1.2 in in [25]. | +| BeaconRSSI | WLAN Beacon RSSI as defined in [26] and [27]. | + +The upper layers in the UE shall be notified (see TS 24.302 [28]) when and for which WLAN(s), that matches all the provided identifiers (in sub-clause 5.10.3) for a specific entry in the list, the following conditions 1 and 2 for steering traffic from UTRAN to WLAN are satisfied for a time interval $T_{\text{steeringWLAN}}$ : + +- 1) In the UTRAN serving cell: + +$$\text{Qrxlevmeas} < \text{Thresh}_{\text{ServingOffloadWLAN, Low}}; \text{ or}$$ + +$$\text{Qqualmeas} < \text{Thresh}_{\text{ServingOffloadWLAN, Low2}}.$$ + +- 2) In the target WLAN: + +$$\text{ChannelUtilizationWLAN} < \text{Thresh}_{\text{ChUtilWLAN, Low}}; \text{ and}$$ + +$$\text{BackhaulRateDIWLAN} > \text{Thresh}_{\text{BackhRateDLWLAN, High}}; \text{ and}$$ + +$$\text{BackhaulRateUIWLAN} > \text{Thresh}_{\text{BackhRateULWLAN, High}}; \text{ and}$$ + +$$\text{BeaconRSSI} > \text{Thresh}_{\text{BeaconRSSIWLAN, High}}.$$ + +The UE shall not consider the metrics for which a threshold has not been provided. The UE shall evaluate the UTRAN conditions on the serving cell in Idle mode, URA\_PCH, CELL\_PCH, CELL\_FACH and CELL\_DCH. If not all metrics related to the provided thresholds can be acquired for a WLAN BSS, the UE shall exclude that WLAN BSS from the evaluation of the above rule. + +The upper layers in the UE shall be notified (see TS 24.302 [28]) when the following conditions 3 or 4 for steering traffic from WLAN to UTRAN are satisfied for a time interval $T_{\text{steeringWLAN}}$ : + +- 1) In the source WLAN: + +$$\text{ChannelUtilizationWLAN} > \text{Thresh}_{\text{ChUtilWLAN, High}}; \text{ or}$$ + +$$\text{BackhaulRateDIWLAN} < \text{Thresh}_{\text{BackhRateDLWLAN, Low}}; \text{ or}$$ + +$$\text{BackhaulRateUIWLAN} < \text{Thresh}_{\text{BackhRateULWLAN, Low}}; \text{ or}$$ + +$$\text{BeaconRSSI} < \text{Thresh}_{\text{BeaconRSSIWLAN, Low}}.$$ + +- 2) In the target UTRANcell: + +$$\text{Qrxlevmeas} > \text{Thresh}_{\text{ServingOffloadWLAN, High}}; \text{ and}$$ + +$$\text{Qqualmeas} > \text{Thresh}_{\text{ServingOffloadWLAN, High2}}.$$ + +The UE shall not consider the metrics for which a threshold has not been provided. The UE shall evaluate the UTRAN conditions on the serving cell in Idle mode, URA\_PCH, CELL\_PCH, CELL\_FACH and CELL\_DCH. + +If the FDD UE is configured with DCH only, the reference cell to use, for the rules defined in this sub-clause, is the best cell in active set. + +### 5.10.3 RAN assistance parameters definition + +The following RAN assistance parameters for RAN-assisted WLAN interworking may be provided: + +#### **ThreshServingOffloadWLAN, Low** + +This specifies the CPICH RSCP for FDD cells (dBm) and P-CCPCH RSCP for TDD cells (dBm) used by the UE for traffic steering from UTRAN to WLAN. + +#### **ThreshServingOffloadWLAN, High** + +This specifies the CPICH RSCP for FDD cells (dBm) and P-CCPCH RSCP for TDD cells (dBm) used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshServingOffloadWLAN, Low2** + +This specifies the CPICH $E_c/N_0$ (dB) for FDD cells used by the UE for traffic steering from UTRAN to WLAN. + +#### **ThreshServingOffloadWLAN, High2** + +This specifies the CPICH $E_c/N_0$ (dB) for FDD cells used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshChUtilWLAN, Low** + +This specifies the WLAN channel utilization (BSS load) threshold used by the UE for traffic steering from UTRAN to WLAN. + +#### **ThreshChUtilWLAN, High** + +This specifies the WLAN channel utilization (BSS load) threshold used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshBackhRateDLWLAN, Low** + +This specifies the backhaul available downlink bandwidth threshold used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshBackhRateDLWLAN, High** + +This specifies the backhaul available downlink bandwidth threshold used by the UE for traffic steering from UTRAN to WLAN. + +#### **ThreshBackhRateULWLAN, Low** + +This specifies the backhaul available uplink bandwidth threshold used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshBackhRateULWLAN, High** + +This specifies the backhaul available uplink bandwidth threshold used by the UE for traffic steering from UTRAN to WLAN. + +#### **ThreshBeaconRSSIWLAN, Low** + +This specifies the Beacon RSSI threshold used by the UE for traffic steering from WLAN to UTRAN. + +#### **ThreshBeaconRSSIWLAN, High** + +This specifies the Beacon RSSI threshold used by the UE for traffic steering from UTRAN to WLAN. + +#### **TsteeringWLAN** + +This specifies the timer value during which the rules should be fulfilled before starting traffic steering between UTRAN and WLAN. + +#### **WLAN identifiers** + +Only the SSIDs, BSSIDs and HESSIDs which are provided in this parameter shall be considered for traffic steering between UTRAN and WLAN based on the rules in this chapter. + +# 6 Broadcast information receiving + +## 6.1 Reception of System Information + +Requirements are specified in [4]. + +## 6.2 Cell Broadcast in Idle Mode, CELL\_PCH and URA\_PCH + +A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode, in URA\_PCH and CELL\_PCH. When several PCHs exist in the cell, the FACH which carries the CTCH may be mapped to a different SCCPCH than the PCH selected by the UE for paging in Idle mode (as specified in Sec. 8.1). In this case, UEs with basic service capabilities shall be capable to change from the SCCPCH that carries the PCH selected for paging to another SCCPCH which carries Cell Broadcast messages (i.e. the CTCH mapped to an FACH) and receive BMC messages during time intervals which do not conflict with the UE specific paging occasions. + +The second system information broadcast channel (BCH on SCCPCH) is mapped on a separate SCCPCH, i.e. different from the SCCPCH which carries the FACH with CTCH. In case CTCH occasions collide with transmissions of the second system information broadcast channel, the UE supporting second system information broadcast channel may decide not to receive the second broadcast channel. + +NOTE: In case certain BMC messages conflict with the UE specific paging occasions the reception of CBS cannot be guaranteed and depends on UE capabilities. + +## 6.3 MBMS Services + +If the UE has activated MBMS services and MBMS is available in the cell (i.e., the MCCH information is provided on the BCCH) and the UE is permitted to receive MBMS in the cell, the UE shall: + +- receive the MCCH as specified in clause 8.4 and in [4]; +- participate in MBMS counting as specified in [4]; +- receive each FACH on which the MTCH carrying an MBMS activated service that does not require the establishment of an RRC connection is mapped. + +The UE may: + +- monitor the MICH as specified in clause 8a and in [4]; +- receive the MSCH. + +### 6.3.1 MBSFN cluster selection and reselection + +#### 6.3.1.1 MBSFN cluster selection + +MBSFN cluster selection/reselection process for MBSFN clusters operating on the same frequency may be based on reception quality of the CPICH for FDD and 3.84 Mcps TDD IMB or P-CCPCH for TDD. Details of the process are not specified. + +The UE shall search for MBSFN clusters if the frequencies on which MBSFN clusters are available are not indicated in the cell that the UE is camping on for normal service if the mobile is configured to receive services via MBSFN mode. Details of the process are not specified. + +For 1.28 Mcps TDD, the UE that needs receive MBMS services delivered in an MBSFN cluster may at the first step select a non MBSFN cell (i.e. a unicast cell), that the MBSFN cluster is associated with. The UE can get synchronized to the MBSFN cluster with the help of the information indicated in system information broadcast by the associated unicast cell, and receive the system information and MCCH messages in the MBSFN Special Timeslot. The details of the association between MBSFN clusters and non MBSFN cells operating in a unicast carrier are not specified. In case + +there are more than one MBSFN clusters indicated in system information broadcast by a unicast cell, the process of which MBSFN cluster should be selected for searching is not specified. + +#### 6.3.1.2 Camped on MBSFN cluster + +When camped on a MBSFN cluster, the UE shall perform the following tasks: + +- receive the MCCH as specified in clause 8.4 and in [4]; +- monitor the available MBMS services on the MBSFN cluster that the UE is camping on + +The UE may: + +- monitor the MICH as specified in clause 8a and in [4]; +- receive the MSCH. + +#### 6.3.1.3 MBSFN inter frequency neighbour information + +Upon detection of one MBSFN cluster all other frequencies on which MBMS service is provided in MBSFN mode for one of the PLMN assigned to the MBSFN cluster are indicated as specified in [4]. + +The UE chooses the frequency for the MBSFN cluster to be received based on the information on the services that are provided on the MBSFN clusters of those frequencies. + +In the case that the UE does not receive a service from the current MBSFN cluster and the UE is configured to receive an MBMS service in MBSFN mode it should attempt to receive information on ongoing services as specified in [4]. + +# --- 7 Void + +# --- 8 Paging and SCCPCH selection and in FDD and 1.28 Mcps TDD the H-RNTI selection + +## 8.1 Paging Channel selection + +System information block type 5 (SIB 5) and System information block type 5bis (SIB 5bis) define common channels to be employed in Idle mode [4]. In a cell, a single or several PCHs may be established. Each Secondary Common Control Physical Channel (SCCPCH) indicated to the UE in system information may carry up to one PCH. Thus, for each defined PCH there is one uniquely associated PICH also indicated. + +In case that more than a single PCH and associated PICH are defined in SIB 5 or SIB 5bis, the UE shall perform a selection according to the following rule: + +- The UE shall select a SCCPCH from the ones listed in SIB 5 or SIB 5bis based on IMSI as follows: + +$$\text{"Index of selected SCCPCH"} = \text{IMSI mod } K,$$ + +where K is equal to the number of listed SCCPCHs which carry a PCH (i.e. SCCPCHs carrying FACH only shall not be counted). These SCCPCHs shall be indexed in the order of their occurrence in SIB 5 or SIB 5bis from 0 to K-1. + +For GSM-MAP, i.e. "IMSI (GSM-MAP)" is given as sequence of digits of type Integer(0..9), IMSI shall in the formula above be interpreted as a decimal integer number, where the first digit given in the sequence represents the highest order digit. + +For DS-41, i.e. "IMSI (DS-41)" is given as octet string, IMSI shall in the formulae above correspond to the decoded decimal representation of the IMSI-S part included in the octet string (see TTA/ETSI/IS-2000-5). + +For example: + +$$\text{IMSI (GSM-MAP)} = 12 \text{ (digit1=1, digit2=2)}$$ + +In the calculations, this shall be interpreted as the decimal integer "12", not " $1 \times 16 + 2 = 18$ ". + +"Index of selected SCCPCH" identifies the selected SCCPCH with the PCH and the uniquely associated PICH to be used by the UE. + +If the UE has no IMSI, for instance when making an emergency call without USIM, the UE shall use as default number IMSI = 0. + +## 8.2 SCCPCH selection when entering Connected mode + +If HS-DSCH operation in CELL\_FACH state (FDD and 1.28 Mcps TDD) is not configured to the cell, when entering Connected mode from Idle mode by sending an RRC CONNECTION REQUEST message, the UE shall select the SCCPCH which carries an FACH to be used for reception of the RRC CONNECTION SETUP message according to the following rule: + +- the UE shall select an SCCPCH from the SCCPCHs listed in System Information Block type 5 (SIB 5) or System Information Block type 5bis (SIB 5bis) based on "Initial UE Identity" as follows: + +$$\text{"Index of selected SCCPCH"} = \text{"Initial UE Identity"} \bmod K,$$ + +where K is equal to the number of listed SCCPCHs which carry a FACH (i.e. SCCPCHs carrying PCH only shall not be counted). These SCCPCHs shall be indexed from 0 to K-1 in the order of their occurrence in SIB 5 or SIB 5bis, and "Index of selected SCCPCH" identifies the selected SCCPCH. "Initial UE Identity" refers to the Information Element included by the UE into the RRC CONNECTION REQUEST message. In the above formula, the parameter "Initial UE Identity" shall be interpreted as follows, depending on the choice of UE-Id type of the respective IE: + +For UE-Id type "IMSI (GSM-MAP)", i.e. the IE is given as sequence of digits of type Integer(0..9), "Initial UE Identity" shall be interpreted as an integer number, where the first digit given in the sequence represents the highest order digit. + +For UE-Id types "TMSI and LAI (GSM-MAP)" or "P-TMSI and RAI (GSM-MAP)", only the TMSI or P-TMSI parts given as Bitstring(32) shall be used, and "Initial UE Identity" shall be interpreted as a binary representation of an integer number, where the first bit in the Bitstring represents the highest order bit. + +For UE-Id type "IMEI", i.e. the IE is given as sequence of hexadecimal digits of type Integer(0..15), "Initial UE Identity" shall be interpreted as a hexadecimal representation of an integer number, where the first digit given in the sequence represents the highest order digit. + +For UE-Id type "IMSI (DS-41)", i.e. the IE is given as octet string, "Initial UE Identity" shall correspond to the decoded decimal representation of the IMSI-S part included in the octet string (see TTA/EIA/IS-2000-5). + +For UE-Id types "ESN (DS-41)" or "TMSI (DS-41)", i.e. the IE is given as Bitstring(32), "Initial UE Identity" shall be interpreted as a binary representation of an integer number, where the first bit in the Bitstring represents the highest order bit. + +For UE-Id type "IMSI and ESN (DS-41)" only the ESN part shall be used as "Initial UE Identity", as defined above. + +## 8.2b H-RNTI selection when entering Connected mode (FDD and 1.28 Mcps TDD) + +If HS-DSCH operation in CELL\_FACH state is configured to the cell in System Information Block type 5 (SIB 5) or System Information Block type 5bis, when entering Connected mode from Idle mode by sending an RRC CONNECTION REQUEST message, the UE shall start listening to the HS-SCCH indicated in System Information Block type 5 (SIB 5) or in System Information Block type 5bis (SIB 5bis). + +The detection of HS-SCCH is based on Common H-RNTI listed in System Information Block type 5 (SIB 5) or System Information Block type 5bis (SIB 5bis). The UE shall select the Common H-RNTI to be used for reception of the RRC CONNECTION SETUP message according to the following rule: + +- the UE shall select a Common H-RNTI from the Common H-RNTIs listed in System Information Block type 5 (SIB 5) or System Information Block type 5bis (SIB 5bis) based on "Initial UE Identity" as follows: + +$$\text{"Index of selected Common H-RNTI"} = \text{"Initial UE Identity"} \bmod K,$$ + +- where K is equal to the number of listed Common H-RNTI. These Common H-RNTIs shall be indexed from 0 to K-1 in the order of their occurrence in SIB 5 or SIB 5bis, and "Index of selected Common H-RNTI" identifies the selected Common H-RNTI. "Initial UE Identity" refers to the Information Element included by the UE into the RRC CONNECTION REQUEST message. In the above formula, the parameter "Initial UE Identity" shall be interpreted as follows, depending on the choice of UE-Id type of the respective IE: + +For UE-Id type "IMSI (GSM-MAP)", i.e. the IE is given as sequence of digits of type Integer(0..9), "Initial UE Identity" shall be interpreted as an integer number, where the first digit given in the sequence represents the highest order digit. + +For UE-Id types "TMSI and LAI (GSM-MAP)" or "P-TMSI and RAI (GSM-MAP)", only the TMSI or P-TMSI parts given as Bitstring(32) shall be used, and "Initial UE Identity" shall be interpreted as a binary representation of an integer number, where the first bit in the Bitstring represents the highest order bit. + +For UE-Id type "IMEI", i.e. the IE is given as sequence of hexadecimal digits of type Integer(0..15), "Initial UE Identity" shall be interpreted as a hexadecimal representation of an integer number, where the first digit given in the sequence represents the highest order digit. + +For UE-Id type "IMSI (DS-41)", i.e. the IE is given as octet string, "Initial UE Identity" shall correspond to the decoded decimal representation of the IMSI-S part included in the octet string (see TTA/EIA/IS-2000-5). + +For UE-Id types "ESN (DS-41)" or "TMSI (DS-41)", i.e. the IE is given as Bitstring(32), "Initial UE Identity" shall be interpreted as a binary representation of an integer number, where the first bit in the Bitstring represents the highest order bit. + +For UE-Id type "IMSI and ESN (DS-41)" only the ESN part shall be used as "Initial UE Identity", as defined above. + +After detecting the HS-SCCH with Common H-RNTI, the UE start reception of the corresponding HS-PDSCH(s) TTI. + +## 8.3 Discontinuous Reception for Paging + +The UE may use Discontinuous Reception (DRX) in idle mode in order to reduce power consumption. When DRX is used the UE needs only to monitor one Page Indicator, PI, (see definition in [7] and [8]) in one Paging Occasion per DRX cycle. + +The DRX cycle length shall be $\text{MAX}(2^k, \text{PBP})$ frames, where k is an integer and PBP is the Paging Block Periodicity. PBP is only applicable for TDD and is equal to the PICH repetition period that is broadcast in system information. For FDD, PBP=1. + +The UE may be attached to different CN domains with different CN domain specific DRX cycle lengths. The UE shall store each CN domain specific DRX cycle length for each CN domain the UE is attached to and use the shortest of those DRX cycle lengths. The CS CN specific DRX cycle length coefficient shall be updated locally in the UE using information given in system information. On the other hand, the PS CN specific DRX cycle length coefficient shall be updated after the negotiation between the UE and PS CN by NAS procedure. If no specific value "k" is negotiated in NAS procedure, the UE and PS CN shall use the DRX cycle length given for PS CN domain in system information. + +The DRX cycle lengths to use for UTRAN connected mode is the shortest of the following: + +- UTRAN DRX cycle length; +- any of the stored CN domain specific DRX cycle length for the CN domains the UE is only attached to with no signalling connection established. + +For TDD, and for FDD in IDLE mode as well as in RRC Connected mode, if HS-DSCH operation in CELL\_PCH and URA\_PCH state is not configured to the cell, or for 1.28 Mcps TDD if both HS-DSCH operation in CELL\_PCH and URA\_PCH state and legacy PCH are configured to the cell but no dedicated H-RNTI is allocated to the UE, the UE shall use the IMSI, the number of available SCCPCH which carry a PCH (K) as derived according to subclause 8.1, the Cell System Frame Number (SFN), Np (for FDD, Np is the number of page indicators within a frame; for TDD, Np is + +the number of page indicators within a paging block), Frame offset (For FDD, Frame offset = 0; for TDD, PICH frame offset values are given in system information), PBP and the DRX cycle length to determine the Paging Occasions. + +For FDD, if HS-DSCH operation in CELL\_PCH and URA\_PCH state is configured to the cell, the UE in RRC Connected mode shall use the IMSI, the number of indexed PICH for HSDPA supported paging (K) as derived from System Information Block Type 5 or System Information Block Type 5bis, the Cell System Frame Number (SFN), Np (Np is the number of page indicators within a frame), Frame offset (Frame offset = 0), PBP and the DRX cycle length to determine the Paging Occasions. + +For 1.28 Mcps TDD, if HS-DSCH operation in CELL\_PCH and URA\_PCH state is configured to the cell and no legacy PCH is configured in the cell, or if both HS-DSCH operation in CELL\_PCH and URA\_PCH state and legacy PCH are configured to the cell and the dedicated H-RNTI is allocated to the UE, the UE in RRC Connected mode shall use the IMSI, the number of indexed PICH for HSDPA supported paging (K) as derived from System Information Block Type 5 or System Information Block Type 5bis, the Cell System Frame Number (SFN), Np (Np is the number of page indicators within a frame), Frame offset, PBP and the DRX cycle length to determine the Paging Occasions. + +In FDD the UE shall monitor its paging indicator in the PICH frame with SFN given by the Paging Occasion + +In TDD the UE shall monitor its paging indicator in the paging block given by the Paging Occasion. The Paging Occasion gives the SFN of the first frame of the paging block. + +The value of the Paging Occasion is determined as follows: + +$$\text{Paging Occasion} = \{(\text{IMSI div } K) \bmod (\text{DRX cycle length div } \text{PBP})\} * \text{PBP} + n * \text{DRX cycle length} + \text{Frame Offset}$$ + +Where $n = 0, 1, 2, \dots$ as long as SFN is below its maximum value. + +The actual Page Indicator within a Paging Occasion that the UE shall read is similarly determined based on IMSI. + +The Page Indicator to use is calculated by using the following formula: + +$$\text{PI} = \text{DRX Index} \bmod \text{Np}$$ + +where $\text{DRX Index} = \text{IMSI div } 8192$ + +In FDD mode, $\text{Np} = (18, 36, 72, 144)$ is the number of Page Indicators per frame, and is given in IE "Number of PI per frame", part of system information in FDD mode. In TDD mode, $\text{Np}$ is the number of Page Indicators per paging block and is calculated by the Paging Indicator Length $L_{\text{PI}}$ , the Burst Type (long or short midamble for 3.84/7.68 Mcps TDD) and the PICH repetition length, which are given in system information. + +If the UE has no IMSI, for instance when making an emergency call without USIM, the UE shall use as default numbers, $\text{IMSI} = 0$ and $\text{DRX cycle length} = 256$ (2.56 s), in the formulas above. + +For FDD, see [7] for details about the timing between a PICH frame and when the paging message is transmitted on the PCH in the associated S-CCPCH frame. + +In TDD mode, in case of PCCH mapping on PCH, the Paging Message Receiving Occasion is calculated using the following formula: + +$$\text{Paging Message Receiving Occasion} = \text{Paging Occasion} + N_{\text{PICH}} + N_{\text{GAP}} + \{(\text{DRX Index} \bmod \text{Np}) \bmod N_{\text{PCH}}\} * 2$$ + +For 1.28 Mcps TDD, in case of PCCH on HS-DSCH, the Paging Message Receiving Occasion is calculated using the following formula: + +$$\text{Paging Message Receiving Occasion} = \text{Paging Occasion} + N_{\text{PICH}} + N_{\text{GAP}} + \{(\text{DRX Index} \bmod \text{Np}) \bmod N_{\text{HS-PCH}}\} * m$$ + +Where $N_{\text{HS-PCH}}$ is the number of Paging sub-channels for PCCH on HS-DSCH and $m$ is the length of each sub-channel in Radio Frame. The timing of PICH and Paging Message on HS-DSCH as well as the transmission pattern of PCCH on HS-DSCH is defined in [8]. + +The value $N_{\text{PICH}}$ is the number of frames for PICH transmission and is equal to the PICH repetition length given in system information. The value $N_{\text{GAP}}$ is the number of frames between the last frame carrying PICH for this Paging Occasion and the first frame carrying paging messages for this Paging Occasion. The value $N_{\text{PCH}}$ is the number of Paging Groups. $N_{\text{PCH}}$ and $N_{\text{GAP}}$ are given in system information. + +For GSM-MAP, i.e. "IMSI (GSM-MAP)" is given as sequence of digits of type Integer(0..9), IMSI shall in the formulae above be interpreted as a decimal integer number, where the first digit given in the sequence represents the highest order digit. + +For DS-41, i.e. "IMSI (DS-41)" is given as octet string, IMSI shall in the formulae above correspond to the decoded decimal representation of the IMSI-S part included in the octet string (see TTA/EIA/IS-2000-5). + +For example: + +$$\text{IMSI (GSM-MAP)} = 12 \text{ (digit1=1, digit2=2)}$$ + +In the calculations, this shall be interpreted as the decimal integer "12", not $1 \times 16 + 2 = 18$ . + +## 8.4 Discontinuous Reception for MBMS + +The UE may use discontinuous reception (DRX) on MBMS channels (MCCH, MSCH, MTCH) to reduce power consumption while subscribed to MBMS services. + +### 8.4.1 Discontinuous Reception for MCCH + +The UE may operate DRX on the MCCH either by monitoring the MICH to determine when it needs to receive the MCCH or by using the MODIFIED SERVICES INFORMATION message on the MCCH to determine that it does not need to acquire the remainder of the MCCH information. + +The timing of the MCCH information transmission and the need to receive the MCCH are described in detail in [4]. + +#### 8.4.1.1 Discontinuous Reception via MICH + +When the UE operates DRX on the MCCH through monitoring the MICH, the UE needs to monitor one Notification Indicator (NI), as defined in [7], [8], for each MBMS service it is subscribed to. For each service, a corresponding NI will be set continuously through the entire length of the modification period preceding a change in the associated MCCH information. The modification period should be long enough that a UE that only receives the MICH during its paging occasions can still reliably detect a notification. + +For each service, the 16 bit Notification Indicator to use is calculated as a function of the TMGI: + +$$\text{NI} = (\text{TMGI} + \lfloor \text{TMGI}/G \rfloor) \bmod G, \text{ where } G = 2^{16}.$$ + +A UE with one or more activated MBMS services may monitor the MICH. The exact timing with which the UE reads the MICH within a given modification period is left to the UE implementation, with the proviso that the UE needs to be able to detect notifications reliably for its activated MBMS service(s). + +The TMGI is structured as follows [16]: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------|---|---|---|-------------|---|---|---|---------| +| Temporary Mobile Group Identity IEI | | | | | | | | Octet 1 | +| Length of Temporary Mobile Group Identity contents | | | | | | | | Octet 2 | +| MBMS Service ID | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | +| MCC digit 2 | | | | MCC digit 1 | | | | Octet 6 | +| MNC digit 3 | | | | MNC digit 3 | | | | Octet 7 | +| MNC digit 2 | | | | MNC digit 1 | | | | Octet 8 | + +NOTE: The MBMS Service identity, which is signalled in [4] (see subclause 10.3.9a.8), concerns a signalling optimisation of the TMGI. + +For the calculation of the NI, the TMGI shall be interpreted as a binary representation of an integer number, represented by the bitstring formed by the exclusive OR operation of the MBMS Service ID (octets 3 to 5 of the TMGI) and the PLMN identity (octets 6 to 8 of the TMGI) with the first/ leftmost/ most significant bit corresponding with b8 of the first octet. + +#### 8.4.1.2 Discontinuous Reception via MODIFIED SERVICES INFORMATION + +If the UE receives the MODIFIED SERVICES INFORMATION message on the MCCH and determines from its contents that no service whose information the UE needs to acquire has been modified, the UE may refrain from receiving the MCCH for the remainder of the modification period. + +### 8.4.2 Discontinuous Reception for MTCH + +If the UE operates DRX on the MTCH, the UE shall receive the MSCH as described in [4] to obtain scheduling information for the MTCH. + +The reception intervals for MBMS services are given by the IE "Service transmissions list" in the MBMS SCHEDULING INFORMATION message on the MSCH. + +# --- 8a MBMS Notification + +The structure of the MICH is described in [7] and [14]. + +The RRC-layer behaviour of a UE receiving an MBMS notification indicator is specified in [4]. + +# --- 9 Void + +# --- 10 Void + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|--------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 10/1999 | RP-05 | RP-99464 | - | - | | Approved at TSG-RAN #5 and placed under Change Control | 3.0.0 | +| 12/1999 | RP-06 | RP-99632 | 001 | 2 | | Modification and editorial changes | 3.1.0 | +| | RP-06 | RP-99633 | 002 | 3 | | Specification of Cell reselection procedures in | 3.1.0 | +| | RP-06 | RP-99633 | 003 | 2 | | Integration of Cell Broadcast Service (CBS) | 3.1.0 | +| | RP-06 | RP-99633 | 004 | 2 | | Measurement used as a quality estimate for cell | 3.1.0 | +| | RP-06 | RP-99632 | 006 | | | Discontinuous reception | 3.1.0 | +| | RP-06 | RP-99633 | 008 | 3 | | Barred Cells and Access Control | 3.1.0 | +| | RP-06 | RP-99633 | 009 | | | Introduction of network control of UE measurement | 3.1.0 | +| | RP-06 | RP-99631 | 011 | | | Editorial issues | 3.1.0 | +| 03/2000 | RP-07 | RP-000037 | 007 | 2 | | Cell Selection for DS-41 mode | 3.2.0 | +| | RP-07 | RP-000037 | 014 | | | Modified description of cell search procedure | 3.2.0 | +| | RP-07 | RP-000037 | 018 | 1 | | UE individual DRX cycles in CELL_PCH and URA_PCH states | 3.2.0 | +| | RP-07 | RP-000037 | 019 | 1 | | Cell re-selection criteria including HCS | 3.2.0 | +| | RP-07 | RP-000037 | 021 | | | Modified description of DRX | 3.2.0 | +| 06/2000 | RP-08 | RP-000217 | 025 | | | Triggering of inter-system measurements for cell re-selection when HCS is used | 3.3.0 | +| | RP-08 | RP-000217 | 026 | 5 | | Cell re-selection | 3.3.0 | +| | RP-08 | RP-000217 | 027 | 4 | | Access Control | 3.3.0 | +| | RP-08 | RP-000217 | 028 | | | Downlink signalling failure | 3.3.0 | +| | RP-08 | RP-000217 | 029 | | | Cell-reselection parameter signalling | 3.3.0 | +| | RP-08 | RP-000217 | 030 | | | Cell Selection and Reselection | 3.3.0 | +| | RP-08 | RP-000217 | 031 | 1 | | CN DRX cycle coefficient | 3.3.0 | +| 09/2000 | RP-09 | RP-000355 | 035 | 2 | | Paging channel selection | 3.4.0 | +| | RP-09 | RP-000355 | 037 | 1 | | Editorial corrections | 3.4.0 | +| | RP-09 | RP-000355 | 039 | | | HCS measurement rules | 3.4.0 | +| | RP-09 | RP-000355 | 042 | 2 | | Usage of Ec/N0 measurement quantity for cell ranking | 3.4.0 | +| | RP-09 | RP-000355 | 044 | | | Correction and restructuring | 3.4.0 | +| 12/2000 | RP-10 | RP-000565 | 046 | 1 | | Support for PLMN selection | 3.5.0 | +| | RP-10 | RP-000565 | 049 | 1 | | Correction of algorithm for paging channel selection | 3.5.0 | +| | RP-10 | RP-000565 | 050 | | | Alignment of use of TEMP_OFFSET parameters with TS 25.331 | 3.5.0 | +| | RP-10 | RP-000565 | 051 | 2 | | Clarifications and Editorial Corrections | 3.5.0 | +| | RP-10 | RP-000565 | 052 | 1 | | Clarifications to cell selection and reselection procedures | 3.5.0 | +| | RP-10 | RP-000565 | 053 | | | Removal of immediate cell evaluation | 3.5.0 | +| | RP-10 | RP-000565 | 054 | | | One step cell selection | 3.5.0 | +| 03/2001 | RP-11 | RP-010022 | 055 | 1 | | Usage of HCS Parameters in Cell Reselection | 3.6.0 | +| | RP-11 | RP-010022 | 056 | | | Clarification of usage of "Initial UE-Id" for SCCPCH selection | 3.6.0 | +| | RP-11 | RP-010022 | 058 | | | Clarification of paging occasion | 3.6.0 | +| | RP-11 | RP-010022 | 059 | 1 | | Correction in Any Cell Selection State | 3.6.0 | +| | RP-11 | RP-010022 | 061 | | | Correction to the definition of a suitable cell | 3.6.0 | +| | RP-11 | RP-010022 | 062 | | | Correction to discontinuous reception in TDD | 3.6.0 | +| | RP-11 | RP-010022 | 063 | 1 | | Correction of PI calculation for Paging DRX | 3.6.0 | +| | RP-11 | RP-010200 | 064 | 3 | | Equivalent PLMN codes | 3.6.0 | +| | RP-11 | RP-010022 | 065 | | | High quality cell in PLMN selection | 3.6.0 | +| | RP-11 | RP-010022 | 066 | | | Clean-up | 3.6.0 | +| | RP-11 | RP-010037 | 057 | 1 | | Support of 1.28Mcps TDD | 4.0.0 | +| 06/2001 | RP-12 | RP-010305 | 072 | | | Corrections to 25.304 | 4.1.0 | +| | RP-12 | RP-010435 | 074 | 1 | | Emergency calls in barred cells | 4.1.0 | +| | RP-12 | RP-010305 | 078 | | | Clarification to usage of measurement thresholds | 4.1.0 | +| 09/2001 | RP-13 | RP-010539 | 080 | | | Clarification to usage of measurement thresholds for HCS | 4.2.0 | +| | RP-13 | RP-010539 | 082 | | | Definition of strongest cell in cell search procedures | 4.2.0 | +| | RP-13 | RP-010539 | 084 | 1 | | Miscellaneous corrections | 4.2.0 | +| | RP-13 | RP-010539 | 086 | | | Correction to cells reserved for operator use | 4.2.0 | +| | RP-13 | RP-010539 | 088 | 1 | | Service type also valid in connected mode | 4.2.0 | +| | RP-13 | RP-010539 | 090 | | | Cell Access Restrictions for emergency calls | 4.2.0 | +| 12/2001 | RP-14 | RP-010756 | 092 | | | Clarification on DRX cycle length in connected mode | 4.3.0 | +| | RP-14 | RP-010756 | 094 | | | Correction to search for available PLMNs | 4.3.0 | +| 03/2002 | RP-15 | RP-020063 | 096 | | | Correction to TDD paging message receiving occasion | 4.4.0 | +| | RP-15 | RP-020063 | 098 | | | Clarification of IMSI at Paging channel selection and DRX calculation | 4.4.0 | +| | RP-15 | - | - | | | Upgrade to Release 5 - no technical change | 5.0.0 | +| 06/2002 | RP-16 | RP-020324 | 101 | | | Limitations of CBS reception | 5.1.0 | +| 12/2002 | RP-18 | RP-020716 | 104 | | | Highest HCS priority | 5.2.0 | +| 06/2003 | RP-20 | RP-030289 | 107 | | | Correction to cell selection process to include RRC connected mode | 5.3.0 | +| 12/2003 | RP-22 | - | - | | | Upgrade to Release 6 - no technical changes | 6.0.0 | +| 03/2004 | RP-23 | RP-040094 | 111 | 1 | | H criteria & High mobility reselection | 6.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|-------------------------------------------------------------------------------------------------|-------| +| 06/2004 | RP-24 | RP-040208 | 113 | 1 | | Correction to UE selection of reserved cells | 6.2.0 | +| | RP-24 | RP-040208 | 116 | | | Modification of the Sintersearch and Ssearch RAT,m behaviour | 6.2.0 | +| | RP-24 | RP-040208 | 114 | 3 | | Selection of suitable cell | 6.2.0 | +| 09/2004 | RP-25 | RP-040332 | 119 | | | HCS measurement rules & high-mobility | 6.3.0 | +| 12/2004 | RP-26 | RP-040526 | 121 | 2 | | Cell selection and reselection parameters | 6.4.0 | +| | RP-26 | RP-040506 | 123 | | | Use of access class restrictions at Inter-RAT cell change | 6.4.0 | +| | RP-26 | RP-040494 | 124 | | | Network Sharing and multiple PLMN identities | 6.4.0 | +| | RP-26 | RP-040488 | 126 | | | TS 25.304 Introduction of MBMS | 6.4.0 | +| | RP-26 | RP-040488 | 127 | | | Addition of MBMS Frequency Layer Convergence to 25.304 | 6.4.0 | +| 03/2005 | RP-27 | RP-050081 | 125 | 1 | | Correction to "selected PLMN" in access stratum | 6.5.0 | +| | RP-27 | RP-050073 | 129 | 1 | | Reselection procedure (1235) | 6.5.0 | +| | RP-27 | RP-050073 | 131 | 1 | | RSCP Thresholds | 6.5.0 | +| | RP-27 | RP-050073 | 132 | 2 | | HCS High-mobility measurement rules | 6.5.0 | +| | RP-27 | RP-050112 | 133 | | | H criterion in HCS high-mobility | 6.5.0 | +| | RP-27 | RP-050077 | 134 | | | MBMS Scope | 6.5.0 | +| | RP-27 | RP-050128 | 137 | 1 | | Correction to cell selection and reselection parameters to enable enhanced cell reselection | 6.5.0 | +| | RP-27 | RP-050073 | 139 | 1 | | Intra frequency measurement rules for HCS | 6.5.0 | +| 06/2005 | RP-28 | RP-050314 | 0140 | | | Addition of idle mode cell selection due to FLD | 6.6.0 | +| | RP-28 | RP-050314 | 0141 | | | MBMS Frequency Layer Convergence | 6.6.0 | +| | RP-28 | RP-050314 | 0142 | | | Removal of sentences in brackets in 25.304 | 6.6.0 | +| 09/2005 | RP-29 | RP-050460 | 0145 | | | Correction to condition for starting penalty timer in HCS reselection | 6.7.0 | +| | RP-29 | RP-050479 | 0146 | | | Selecting the correct priority layer in HCS high mobility | 6.7.0 | +| | RP-29 | RP-050479 | 0147 | | | Correction to inter-frequency cell reselection when HCS is not used | 6.7.0 | +| | RP-29 | RP-050468 | 0148 | | | Correction to cell reselection when HCS is not used and MBMS PL is indicated | 6.7.0 | +| 12/2005 | RP-29 | RP-050788 | 0150 | | | Structure and use of TMGI for MBMS notification | 6.8.0 | +| 03/2006 | RP-31 | RP-060188 | 0151 | 2 | | Effect of partial roaming restrictions on cell reselection and proposed performance enhancement | 6.9.0 | +| | RP-31 | RP-060090 | 0152 | 1 | | Corrected UE behaviour at LR reject | 6.9.0 | +| | RP-31 | RP-060090 | 0153 | | | Clarification regarding Access Class and Initial Direct Transfer | 6.9.0 | +| | RP-31 | RP-060098 | 0154 | | | 7.68 Mpcs TDD Option (Release 7) | 7.0.0 | +| 12/2006 | RP-34 | RP-060712 | 0155 | 1 | | Introduction high mobility detection on RRC state change | 7.1.0 | +| 06/2007 | RP-36 | RP-070403 | 0156 | | | Introduction of HS-DSCH operation in CELL_FACH state | 7.2.0 | +| | RP-36 | RP-070407 | 0157 | | | S-CCPCH and PCH channel selection for Band IV or Band IX or Band X | 7.2.0 | +| | RP-36 | RP-070407 | 0158 | | | PLMN selection ping-pong control | 7.2.0 | +| | RP-36 | RP-070400 | 0159 | | | MBMS FDD and TDD Physical Layer Improvements | 7.2.0 | +| 09/2007 | RP-37 | RP-070671 | 0160 | | | H-RNTI selection | 7.3.0 | +| 12/2007 | RP-38 | RP-070902 | 0161 | | | More improvement on Dedicated Carrier for 1.28Mpcs TDD MBMS | 7.4.0 | +| | RP-38 | - | - | | | Upgrade to the Release 8 - no technical change | 8.0.0 | +| 03/2008 | RP-39 | RP-080177 | 0164 | 1 | | Clarification on Treselection for MBMS | 8.1.0 | +| 05/2008 | RP-40 | RP-080403 | 0166 | 1 | | Correction to HCS | 8.2.0 | +| 09/2008 | RP-41 | RP-080680 | 0168 | 2 | | MBSFN Corrections | 8.3.0 | +| | RP-41 | RP-080701 | 0169 | - | | Correction and Clarification in HCS Reselection | 8.3.0 | +| | RP-41 | RP-080694 | 0172 | 1 | | E-UTRA Introduction/Priority reselection method for inter-frequency and inter-RAT cells | 8.3.0 | +| | RP-41 | RP-080697 | 0173 | 1 | | Introduction of HS-DSCH DRX in CELL_FACH state | 8.3.0 | +| | RP-41 | RP-080696 | 0176 | 2 | | Triggering of cell reselection in CELL_FACH | 8.3.0 | +| 12/2008 | RP-42 | RP-081015 | 0179 | 1 | | Prevention of excessive OOS due to failure of Squal criterion | 8.4.0 | +| | RP-42 | RP-081025 | 0181 | - | | Introduction of Cell_FACH enhancement operation for LCR TDD | 8.4.0 | +| | RP-42 | RP-081015 | 0182 | - | | Correction to absolute priority reselection procedure | 8.4.0 | +| | RP-42 | RP-081032 | 0183 | - | | Introduction of the UE behavior on PPAC parameter | 8.4.0 | +| | RP-42 | RP-081126 | 0185 | 2 | | Support for 3.84 Mpcs MBSFN IMB operation | 8.4.0 | +| 03/2009 | RP-43 | RP-090135 | 0190 | - | | Baseline CR for CSG introduction | 8.5.0 | +| | RP-43 | RP-090132 | 0192 | - | | Correction to serving cell dedicated priority handling when no priority is available | 8.5.0 | +| | RP-43 | RP-090132 | 0194 | 2 | | Priority handling in camped on any cell state in Rel8 | 8.5.0 | +| | RP-43 | RP-090132 | 0195 | - | | Inheriting of dedicated priorities at inter-RAT reselection | 8.5.0 | +| | RP-43 | RP-090132 | 0196 | - | | Correction to the definition of priority search thresholds | 8.5.0 | +| | RP-43 | RP-090132 | 0199 | 1 | | Clarification for the case Absolute Priority is not applied | 8.5.0 | +| 06/2009 | RP-44 | RP-090519 | 0201 | - | | Correction to UE behaviour while 300s frequency barring timer is running | 8.6.0 | +| | RP-44 | RP-090517 | 0202 | 1 | | Correction of Manual CSG ID selection | 8.6.0 | +| | RP-44 | RP-090506 | 0203 | - | | Removal of FFS in 25.304 reference to GERAN timer T3230 | 8.6.0 | +| | RP-44 | RP-090506 | 0207 | 2 | | Clarification of the Priority Handling in CSG Cell | 8.6.0 | +| | RP-44 | RP-090517 | 0208 | - | | CR on Adding "cause#25" to 25.304 | 8.6.0 | +| | RP-44 | RP-090506 | 0209 | - | | Priorities of non Selected PLMN | 8.6.0 | +| | RP-44 | RP-090517 | 0210 | 1 | | Addition of CSG cell reservation behaviour | 8.6.0 | +| | RP-44 | RP-090519 | 0211 | - | | Correction of mobility states | 8.6.0 | +| | RP-44 | RP-090517 | 0212 | 1 | | CR for Clarification on outbound mobility for UTRAN | 8.6.0 | +| 09/2009 | RP-45 | RP-090901 | 0215 | - | | Applicability of EHPLMN to 'reserved for operator use' barring | 8.7.0 | +| | RP-45 | RP-090911 | 0220 | - | | clarifications for manual CSG ID selection | 8.7.0 | +| 12/2009 | RP-46 | RP-091330 | 0225 | - | | Correction to the manual CSG ID selection procedure | 8.8.0 | +| 12/2009 | RP-46 | RP-091343 | 0222 | - | | Clarifications on autonomous search function for CSG | 9.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|--------------------------------------------------------------------------------------------------------------|--------| +| | RP-46 | RP-091343 | 0224 | 3 | | Stage3 CR for UMTS hybrid cell Idle Mode Mobility | 9.0.0 | +| | RP-46 | RP-091343 | 0229 | - | | Access Stratum support for manual CSG selection across PLMN (CR 25.304 Rel-9) | 9.0.0 | +| | RP-46 | RP-091343 | 0232 | 1 | | Renaming Allowed CSG List (25.304 Rel-9) | 9.0.0 | +| 03/2010 | RP-47 | RP-100292 | 0236 | - | | Reception of ETWS notification in limited service state | 9.1.0 | +| | RP-47 | RP-100285 | 0241 | - | | Alternative clarification to priority based mobility | 9.1.0 | +| | RP-47 | RP-100294 | 0243 | - | | Correction to Access Class handling for 'not barred' cells | 9.1.0 | +| | RP-47 | RP-100294 | 0245 | - | | Handling MBSFN cluster selection in the case of 'reserved' cell status | 9.1.0 | +| | RP-47 | RP-100308 | 0247 | - | | Cell reselection enhancements CR for 25.304 | 9.1.0 | +| 06/2010 | RP-48 | RP-100539 | 0249 | - | | Clarification of discontinuous reception for paging in enhanced CELL_FACH state for 1.28 Mcps TDD | 9.2.0 | +| | RP-48 | RP-100556 | 0253 | - | | Corrections to cell reselection enhancements to E-UTRA | 9.2.0 | +| | RP-48 | RP-100556 | 0255 | - | | CSG Cell Reselection testing | 9.2.0 | +| | RP-48 | RP-100538 | 0257 | - | | Clarifications on cell reselection to a CSG cell | 9.2.0 | +| 09/2010 | RP-49 | RP-100855 | 0258 | - | | Clarification on CSG autonomous search | 9.3.0 | +| | RP-49 | RP-100849 | 0260 | 1 | | Triggering of absolute priority based reselection while common E-DCH allocated | 9.3.0 | +| | RP-49 | RP-100851 | 0261 | - | | Correction to EUTRA Qqualmin handling in reselection from UTRA | 9.3.0 | +| 03/2011 | RP-51 | RP-110271 | 0273 | - | | 25.304 correction on manual CSG selection | 9.4.0 | +| 03/2011 | RP-51 | RP-110282 | 0270 | - | | Introduction of Minimization of Drive Tests | 10.0.0 | +| 06/2011 | RP-52 | RP-110835 | 0276 | - | | CR to align NAS and AS for handling of CSG cells | 10.1.0 | +| | RP-52 | RP-110843 | 0277 | 1 | | Correction for definition of MDT PLMN | 10.1.0 | +| | RP-52 | RP-110842 | 0283 | 1 | | Introduction of UTRAN Automatic Neighbor Relation | 10.1.0 | +| 09/2011 | RP-53 | RP-111286 | 0286 | - | | 25.304 CR including ePLMN support for ANR | 10.2.0 | +| | RP-53 | RP-111281 | 0289 | 2 | | Lifetime of dedicated priorities | 10.2.0 | +| | RP-53 | RP-111285 | 0295 | - | | Clean up MDT text | 10.2.0 | +| 12/2011 | RP-54 | RP-111710 | 0299 | 1 | | CR to 25.304 on Clarification of inter-RAT cell reselection enhancements | 10.3.0 | +| | RP-54 | RP-111712 | 0302 | - | | Clarification to absolute priority based criteria | 10.3.0 | +| 03/2012 | RP-55 | RP-120321 | 0307 | - | | Clarification on the black listed cells for cell reselection to E-UTRA (Rel-10) | 10.4.0 | +| 06/2012 | RP-56 | RP-120814 | 0319 | - | | Clarification for HCS and absolute priority based cell reselection | 10.5.0 | +| 09/2012 | RP-57 | RP-121361 | 0339 | - | | Support of cell reselection to EUTRA using Criterion-5 for 1.28Mcps TDD | 10.6.0 | +| | RP-57 | RP-121371 | 0330 | - | | Introduction of EAB | 11.0.0 | +| | RP-57 | RP-121370 | 0333 | - | | Introduction of MDT multi-PLMN | 11.0.0 | +| | RP-57 | RP-121368 | 0337 | - | | Introduction of absolute priority based measurements and reselection in CELL_FACH State in 25.304 | 11.0.0 | +| 12/2012 | RP-58 | RP-121936 | 0343 | - | | Clarification to measurement rules for inter-Freq&RAT layers without absolute priority being assigned | 11.1.0 | +| | RP-58 | RP-121957 | 0344 | - | | Correction to absolute priority cell reselection | 11.1.0 | +| | RP-58 | RP-121941 | 0345 | 2 | | Introduction of Further Enhancements to CELL_FACH in 25.304 | 11.1.0 | +| | RP-58 | RP-121946 | 0346 | - | | Introduction of MDT accessibility measurements | 11.1.0 | +| | RP-58 | RP-121941 | 0347 | - | | Clarification of absolute priority based measurements and reselection in CELL_FACH State | 11.1.0 | +| | RP-58 | RP-121958 | 0348 | - | | Inter-RAT Treselection enhancement | 11.1.0 | +| | RP-58 | RP-121925 | 0350 | - | | TEMP_OFFSET value for CSG cells not in the neighbor cell list | 11.1.0 | +| 03/2013 | RP-59 | RP-130236 | 0351 | - | | Extend 3G ANR Applicable RRC State | 11.2.0 | +| | RP-59 | RP-130247 | 0353 | - | | Corrections on mobility to CSG and hybrid cells in idle mode for UMTS | 11.2.0 | +| 06/2013 | RP-60 | RP-130802 | 0355 | 1 | | Receive CMAS notification in the limited service state | 11.3.0 | +| | RP-60 | RP-130809 | 0356 | - | | Correction in the definition of Threshx,low2 | 11.3.0 | +| | RP-60 | RP-130806 | 0359 | 1 | | Limiting Inter-RAT measurements for FE-FACH absolute priority reselection | 11.3.0 | +| 09/2013 | RP-61 | RP-131313 | 0360 | - | | Correction to autonomous CSG search function on intra-frequency | 11.4.0 | +| 12/2013 | RP-62 | RP-131995 | 0361 | - | | Cleanup corrections to TS 25.304 | 11.5.0 | +| | RP-62 | RP-131998 | 0362 | - | | Allowing reselection to a member E-UTRA CSG in CELL_FACH when E-UTRA measurement for CELL_FACH is configured | 12.0.0 | +| | RP-62 | RP-131998 | 0363 | - | | Introduction of CSG CELL_FACH mobility | 12.0.0 | +| 03/2014 | RP-63 | RP-140347 | 0365 | - | | Introduction of Cell_FACH with Second DRX to 3G Logged MDT | 12.1.0 | +| 06/2014 | RP-64 | RP-140875 | 0373 | - | | Introduction of cell reselection indication during uplink transmission with common E-DCH | 12.2.0 | +| | RP-64 | RP-140881 | 0374 | - | | Introduction of support for UE power saving mode | 12.2.0 | +| | RP-64 | RP-140892 | 0376 | 1 | | Introduction of RRC Connection Establishment failure temporary Qoffset handling | 12.2.0 | +| 09/2014 | RP-65 | RP-141502 | 0381 | 1 | | Introduction of a second broadcast channel | 12.3.0 | +| | RP-65 | RP-141504 | 0378 | 1 | | Procedures of WLAN/3GPP Radio Interworking for UMTS | 12.3.0 | +| 12/2014 | RP-66 | RP-142122 | 0382 | - | | Clarification on handling of dedicated parameters upon cell selection | 12.4.0 | +| 03/2015 | RP-67 | RP-150373 | 0386 | - | | Correction on provision of WLAN identifiers | 12.5.0 | +| | RP-67 | RP-150373 | 0385 | 1 | | Cleanup on RAN-assisted WLAN interworking | 12.5.0 | +| 06/2015 | RP-68 | RP-150923 | 0387 | - | | Cleanup corrections to TS 25.304 | 12.6.0 | +| 12/2015 | RP-70 | RP-152052 | 0388 | - | | Corrections to WLAN/3GPP radio interworking | 12.7.0 | +| 12/2015 | RP-70 | RP-152066 | 0391 | 1 | | Introduction of Application specific Congestion control for Data Communication (ACDC) in UTRAN | 13.0.0 | +| | RP-70 | RP-152063 | 0389 | 1 | | Introduction of extended DRX in Idle mode | 13.0.0 | +| | RP-70 | RP-152075 | 0392 | 1 | | Extension of Frequency Priorities | 13.0.0 | + +| | | | | | | | | +|---------|--------|---|---|---|---|----------------------------------------------------|--------| +| 03/2017 | RP-75 | | | | | Upgrade to Rel-14, no technical change | 14.0.0 | +| 06/2018 | RP-80 | | | | | Upgrade to Rel-15, no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25305/0c58b6f5c78547fec73ffbcf6df2c30c_img.jpg b/marked/Rel-16/25_series/25305/0c58b6f5c78547fec73ffbcf6df2c30c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5539bda587c0f7303810e2f4e51ee3b2df5143f7 --- /dev/null +++ b/marked/Rel-16/25_series/25305/0c58b6f5c78547fec73ffbcf6df2c30c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1224150bdcb977e7ea69493664e06d2c78527692d61c8cf611c9b933cc41213 +size 11580 diff --git a/marked/Rel-16/25_series/25305/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/25_series/25305/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304c4d134d642aeb6095378a5b93486b9e7f843d --- /dev/null +++ b/marked/Rel-16/25_series/25305/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54421a8965133547b58b1384c6ca7f36a4ae4427d970b7e4b899a6fc7400a9b8 +size 55635 diff --git a/marked/Rel-16/25_series/25305/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-16/25_series/25305/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c424d958518dcb602491d800c1260e66f63520 --- /dev/null +++ b/marked/Rel-16/25_series/25305/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d8cda4c9994fc7861ca94a300617657c1b7595b6f39124ba45a0d4f79c7cc21 +size 28576 diff --git a/marked/Rel-16/25_series/25305/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/25_series/25305/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..922807e5e01bf2be2bef6924f60ece5aa8adf007 --- /dev/null +++ b/marked/Rel-16/25_series/25305/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:804faa191070313faa2179463e5b6dafdea8f1f7fc8bf72d1937a4fcd06da075 +size 13073 diff --git a/marked/Rel-16/25_series/25305/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25305/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05c75c589aef3aea633bef5be0f6a6b4438462a --- /dev/null +++ b/marked/Rel-16/25_series/25305/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a50c77d3b9b031ba050135a91e2bcd465080aa1d6f832e2e72122902b7ab4026 +size 43242 diff --git a/marked/Rel-16/25_series/25305/1da66f5fec34c001912c84a9abf145d7_img.jpg b/marked/Rel-16/25_series/25305/1da66f5fec34c001912c84a9abf145d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7692f16fc627894e90d67b33bea6668a7a7f9a9 --- /dev/null +++ b/marked/Rel-16/25_series/25305/1da66f5fec34c001912c84a9abf145d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee8f8a6b28aa7435af8b6b6aae054329dbad7b006b86e91c1fe58a5cc61aa702 +size 29367 diff --git a/marked/Rel-16/25_series/25305/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/25_series/25305/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e31740653732539a2acc2dd4dc9744b7c8bdb88 --- /dev/null +++ b/marked/Rel-16/25_series/25305/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e77e52ccd1f38545f3d11ff568a5b3a689ef40a60b877431fbaabc16ec33508a +size 51233 diff --git a/marked/Rel-16/25_series/25305/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/25_series/25305/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7517e4fe9d097d08428591f1eedd76201e69e7c1 --- /dev/null +++ b/marked/Rel-16/25_series/25305/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e246cc72cd6243cd3b309d38b7877b0622fd9033b26523590321a144d7afc96 +size 119280 diff --git a/marked/Rel-16/25_series/25305/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/25_series/25305/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6bd9d3ff0834f61abdeaa07ff64c359c5673963 --- /dev/null +++ b/marked/Rel-16/25_series/25305/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0f9c1b4074e2b44c861f6e0b5382397cf3c33c522f76c1e61d1a8a81fe4537b +size 95370 diff --git a/marked/Rel-16/25_series/25305/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/25_series/25305/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e0ceb0afb2a9001948357de6a993612bb5356ad --- /dev/null +++ b/marked/Rel-16/25_series/25305/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd4dc02b46350a220aad272ec4d92a8a425ab9f4bb405a83f8b4fa9b7e09cfa2 +size 92960 diff --git a/marked/Rel-16/25_series/25305/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/25_series/25305/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e768a5c0fd7400e4ac2bbe165fd1b5de13d8a8e5 --- /dev/null +++ b/marked/Rel-16/25_series/25305/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:779fa07667425bcc314037378279de7a3c023d294fd5570be678a6016a35bf9a +size 101197 diff --git a/marked/Rel-16/25_series/25305/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-16/25_series/25305/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4b488ab6fdcaec5de8ba8cfbfb1e4e344e99e62 --- /dev/null +++ b/marked/Rel-16/25_series/25305/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c16aa65f47316af96f8cde66f1d78fb57de477feab6854f858e0f18b2125373b +size 73391 diff --git a/marked/Rel-16/25_series/25305/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/25_series/25305/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f30bd8bfc1e1947f925cf502ef1332ea486c59d --- /dev/null +++ b/marked/Rel-16/25_series/25305/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c08266309ad01f1ad4f012377ff05d0024677290c43ffb682aa0f2b5f087050 +size 123822 diff --git a/marked/Rel-16/25_series/25305/64323b705244afc70bf77babdacb6ce5_img.jpg b/marked/Rel-16/25_series/25305/64323b705244afc70bf77babdacb6ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef18bc6987f8ff3970ae7d09a1a5fed87ceedae --- /dev/null +++ b/marked/Rel-16/25_series/25305/64323b705244afc70bf77babdacb6ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a3e276bf34b85cb9180757dba448f2b3c6a3d27967371677fa107abe8c1b5c1 +size 62889 diff --git a/marked/Rel-16/25_series/25305/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/25_series/25305/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c425c07b1df013882cc00d5fceb6a13c068b2c88 --- /dev/null +++ b/marked/Rel-16/25_series/25305/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5d1a1b8292643226e118c3e91909e76d26e19456fa562027bd20735907f1dfc +size 51435 diff --git a/marked/Rel-16/25_series/25305/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/25_series/25305/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b27cbda7bdf2491bd11590c6ba234fe9f49609db --- /dev/null +++ b/marked/Rel-16/25_series/25305/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af124279954f7e13de056f58a86dbc7702faad5c42b5ac35444597a5317db2b2 +size 119255 diff --git a/marked/Rel-16/25_series/25305/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/25_series/25305/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a75b0067f204ad9323fc47394dde75fb922f18 --- /dev/null +++ b/marked/Rel-16/25_series/25305/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22f7f80437ff6bd631b4dd040e86aa0e3bfcfadd9adb8ebf84eb25e00c58caa2 +size 217966 diff --git a/marked/Rel-16/25_series/25305/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25305/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c3810814d36ddd3699fe5c70c527a6923ff3714 --- /dev/null +++ b/marked/Rel-16/25_series/25305/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1056d3f99a8735c9a92d6325ba49a63bcf6d6b47ab8bd6bf6499f4789bb8b7c4 +size 33308 diff --git a/marked/Rel-16/25_series/25305/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-16/25_series/25305/875c6f4f441fdd3ca7e1908fd1582983_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18ec9b25b6263ab010d05f93c3428b19888a91bf --- /dev/null +++ b/marked/Rel-16/25_series/25305/875c6f4f441fdd3ca7e1908fd1582983_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1462d2e576b1c85e1129342a69277c6fc614e8e75a8f673a9a5dd10e0ed3287f +size 82831 diff --git a/marked/Rel-16/25_series/25305/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/25_series/25305/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec8da1e871c736f9663a08690f323f01e5c3e2a --- /dev/null +++ b/marked/Rel-16/25_series/25305/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:880dae7a64492208ff8bdfd5bb743c14d572220cba10f6c9f6103aef7acf0039 +size 9494 diff --git a/marked/Rel-16/25_series/25305/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/25_series/25305/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba7370a3e791c164d6e221c040f3af444e542c26 --- /dev/null +++ b/marked/Rel-16/25_series/25305/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c43ea4bc1a3fed3a3f0cd93d33f157e4c906ef4c663ab838e4d8ed28f2b80021 +size 118948 diff --git a/marked/Rel-16/25_series/25305/96c8d8b0159c47a7478ada46d781060b_img.jpg b/marked/Rel-16/25_series/25305/96c8d8b0159c47a7478ada46d781060b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd228efee5ec0ffed0281b1b3bb49099c2b399bf --- /dev/null +++ b/marked/Rel-16/25_series/25305/96c8d8b0159c47a7478ada46d781060b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f5668995c78c2d77b1cc30d5d11b2797d286f3b66b9217339be272926ca5ef +size 51995 diff --git a/marked/Rel-16/25_series/25305/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-16/25_series/25305/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7244ab4c41db6d46164b92c092a0d3809cd92e73 --- /dev/null +++ b/marked/Rel-16/25_series/25305/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:355fddf063805128dfc6f6f3d308a6d6a650d3a2ed473cd03083bda72bd2f701 +size 15991 diff --git a/marked/Rel-16/25_series/25305/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/25_series/25305/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4416d5bc8426cdd57c90988d85a04a1da0ab7378 --- /dev/null +++ b/marked/Rel-16/25_series/25305/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19d1bd95172c28301e30dbe4252751d7fa81d5516930437e5adbdffb0595c098 +size 52046 diff --git a/marked/Rel-16/25_series/25305/9c888dd6588358989047de6ced8b2bdb_img.jpg b/marked/Rel-16/25_series/25305/9c888dd6588358989047de6ced8b2bdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60394cb95a5b5ead4ff7b5a9196a645c3a11b36a --- /dev/null +++ b/marked/Rel-16/25_series/25305/9c888dd6588358989047de6ced8b2bdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495345ed0c33fc75c92146221eb86c48e053dc61c0d9e8b0cc4d63573b65b3ee +size 46495 diff --git a/marked/Rel-16/25_series/25305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/25_series/25305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c763fef65afc252bac245120b0943bb92aa002a --- /dev/null +++ b/marked/Rel-16/25_series/25305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29e4deb5c593013ad579cb2e37ac79a16d8885c12b6a771a551ca71bda0b0d61 +size 151566 diff --git a/marked/Rel-16/25_series/25305/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/25_series/25305/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e43d0ae7a991b6d1ce5e69879e64877fd8cc70a3 --- /dev/null +++ b/marked/Rel-16/25_series/25305/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b77fd0b8ffb78ccffcba06b9d9dfac31dac050a4de891bf03eccd434019f5c7 +size 24061 diff --git a/marked/Rel-16/25_series/25305/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-16/25_series/25305/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8491ba26134537c64f8c2b92a91dc1233fb62d --- /dev/null +++ b/marked/Rel-16/25_series/25305/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:937f8effbbbd02b574185077d43f79d2e6b80952b3963b95186e488296807810 +size 58009 diff --git a/marked/Rel-16/25_series/25305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/25_series/25305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae492de881b2cbc14227af462b3a55acda32d78c --- /dev/null +++ b/marked/Rel-16/25_series/25305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb5a384c069ee26c3cf9a96ddc6a5f2c74456ab1e3b73130d18e79216d70932a +size 35491 diff --git a/marked/Rel-16/25_series/25305/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-16/25_series/25305/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e23f104045d5a190e2cdaf3245ef1edf771bdaf9 --- /dev/null +++ b/marked/Rel-16/25_series/25305/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd7a3f7002274a05e26e916cf70b57eaa053c470891f9a2651be93a9fa402727 +size 24618 diff --git a/marked/Rel-16/25_series/25305/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/25_series/25305/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abc3e2679a06850f5f47e81ac784bfb9a93b5918 --- /dev/null +++ b/marked/Rel-16/25_series/25305/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9089eb12a7fc1696653ab064317708ad6564da73f3cf427a0d3c7166e992c1 +size 35260 diff --git a/marked/Rel-16/25_series/25305/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-16/25_series/25305/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336262b2e1fa1d491db5ba3fdb5586f3ca3a4199 --- /dev/null +++ b/marked/Rel-16/25_series/25305/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c848380bcafd961c54d41e07652c43c77d18588fc6e0f8bd69c06b20e91a015e +size 96747 diff --git a/marked/Rel-16/25_series/25305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/25_series/25305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9168cb425c46ea607ad4d0104a24e0bba2807063 --- /dev/null +++ b/marked/Rel-16/25_series/25305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bf4d7f610b118a5ef39c14705a252087c7d2c8839ccb39bd13059aeec142fc5 +size 204827 diff --git a/marked/Rel-16/25_series/25305/db7ae70402c81d140ae7df14b002e057_img.jpg b/marked/Rel-16/25_series/25305/db7ae70402c81d140ae7df14b002e057_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99ee03256f114033b03785f1c086cb23b7e6e0c8 --- /dev/null +++ b/marked/Rel-16/25_series/25305/db7ae70402c81d140ae7df14b002e057_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4413c4c8c85e1fe941c912d82f73370b867c2724be345e3c5cb1eadb7687a824 +size 20021 diff --git a/marked/Rel-16/25_series/25305/ddfefccc6c2fcfadf4e398109548faf8_img.jpg b/marked/Rel-16/25_series/25305/ddfefccc6c2fcfadf4e398109548faf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe30f38d4db2ca35b46964debe8601da46c70f26 --- /dev/null +++ b/marked/Rel-16/25_series/25305/ddfefccc6c2fcfadf4e398109548faf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a757761744a1419b50408676909ced78b90958e55f7451b6c58329633a40db7 +size 10245 diff --git a/marked/Rel-16/25_series/25305/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/25_series/25305/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52eecddfdb6ff1e3d322c91c22330403f112d27b --- /dev/null +++ b/marked/Rel-16/25_series/25305/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3c020d915159e7973187ac84e0b9b6f29e36de8e3aa6f8e036372993e523976 +size 84214 diff --git a/marked/Rel-16/25_series/25305/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/25_series/25305/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af1eb14b6250c74c9c8c3a95ba2ded33ce97c1fc --- /dev/null +++ b/marked/Rel-16/25_series/25305/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:664e67171bd8872b74343be8ab9d5aade2f662976636628320afe4bcd8bba440 +size 92159 diff --git a/marked/Rel-16/25_series/25305/raw.md b/marked/Rel-16/25_series/25305/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bbef1e3528e484821e99b58d738a0a6b694a07b7 --- /dev/null +++ b/marked/Rel-16/25_series/25305/raw.md @@ -0,0 +1,3258 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 2.1 Normative references ..... | 8 | +| 2.2 Informative references..... | 9 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Main concepts and requirements..... | 11 | +| 4.1 Assumptions..... | 12 | +| 4.2 UE Positioning Methods ..... | 12 | +| 4.3 Standard UE Positioning Methods ..... | 13 | +| 4.3.1 Cell ID and Enhanced Cell ID Based Methods ..... | 13 | +| 4.3.2 OTDOA-IPDL Method with network configurable idle periods ..... | 13 | +| 4.3.3 Network-assisted GNSS Methods ..... | 14 | +| 4.3.4 U-TDOA Method ..... | 14 | +| 4.3.5 Barometric Pressure positioning..... | 14 | +| 4.3.6 WLAN positioning ..... | 14 | +| 4.3.7 Bluetooth positioning ..... | 14 | +| 4.3.8 TBS positioning..... | 14 | +| 5 UTRAN UE Positioning Architecture ..... | 15 | +| 5.1 UE Positioning Operations..... | 15 | +| 5.1.1 Co-ordination, Measurement and Calculation Functions ..... | 16 | +| 5.2 Functional Description of UTRAN UE Positioning related elements ..... | 17 | +| 5.2.1 Radio Network Controller (RNC) ..... | 17 | +| 5.2.1.1 Serving RNC..... | 17 | +| 5.2.1.1.1 RNC Centric Mode..... | 17 | +| 5.2.1.1.2 SAS Centric Mode ..... | 17 | +| 5.2.1.2 Other RNC ..... | 18 | +| 5.2.1.2.1 Controlling RNC ..... | 18 | +| 5.2.1.2.2 Drift RNC..... | 19 | +| 5.2.2 Node B..... | 19 | +| 5.2.3 Location measurement unit (LMU)..... | 19 | +| 5.2.4 User Equipment (UE) ..... | 20 | +| 5.2.5 Stand-alone SMLC ..... | 21 | +| 6 Signalling protocols and interfaces ..... | 21 | +| 6.1 LCS signalling between SRNC and MSC/SGSN ..... | 21 | +| 6.2 SRNC signalling to a target UE ..... | 21 | +| 6.3 Controlling RNC signalling to a standalone LMU..... | 21 | +| 6.4 Controlling RNC signalling to an associated LMU..... | 21 | +| 6.5 RNC-to-RNC signalling for UE Positioning support..... | 21 | +| 6.5a SAS to RNC signalling for PCAP..... | 22 | +| 6.6 Interfaces ..... | 22 | +| 6.6.1 Iu Interface..... | 22 | +| 6.6.2 Iur Interface ..... | 22 | +| 6.6.2.1 Signalling between SRNC and DRNC ..... | 22 | +| 6.6.2.2 Signalling between SRNC and CRNC..... | 22 | +| 6.6.3 Iub Interface..... | 23 | +| 6.6.3.1 Signalling between CRNC and associated LMU..... | 23 | +| 6.6.4 Uu Interface ..... | 23 | +| 6.6.4.1 Signalling between SRNC and Target UE..... | 23 | +| 6.6.4.1.1 Assistance Data Delivery to UE..... | 25 | +| 6.6.4.1.2 Error Handling..... | 25 | +| 6.6.4.1.3 Broadcast of Assistance Data..... | 25 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|----| +| 6.6.4.1.4 | Signalling Flow for Assistance Data Broadcast Using the Common UTRAN Broadcast Service..... | 25 | +| 6.6.4.1.5 | UE Positioning Assistance Data Ciphering..... | 26 | +| 6.6.4.1.6 | UE Positioning Assistance Data Ciphering Algorithm..... | 26 | +| 6.6.4.2 | Signalling between RNC and stand-alone LMU..... | 27 | +| 6.6.5 | Iuipc Interface..... | 28 | +| 6.6.5.1 | Signalling between RNC and SAS..... | 28 | +| 6.6.5.1.1 | PCAP Position Calculation..... | 28 | +| 6.6.5.1.2 | PCAP Information Exchange..... | 29 | +| 6.6.5.1.3 | PCAP for SAS based Positioning Method Selection..... | 30 | +| 7 | General UTRAN UE Positioning procedures..... | 31 | +| 7.1 | General procedures in UTRAN for UE Positioning..... | 31 | +| 7.2 | Common procedures supporting UE Positioning interaction between RNCs..... | 32 | +| 7.2.1 | Signalling in case of SRNS relocation..... | 32 | +| 7.3 | Exception procedures..... | 32 | +| 7.3.1 | Procedures in the SRNC..... | 32 | +| 7.3.1.1 | RNC Centric Mode..... | 32 | +| 7.3.1.2 | SAS Centric Mode..... | 33 | +| 7.3.2 | Procedures in a LMU..... | 34 | +| 7.3.3 | Procedures in the target UE..... | 34 | +| 7.3.4 | Procedures in the SAS..... | 34 | +| 7.3.4.1 | RNC Centric Mode..... | 34 | +| 7.3.4.2 | SAS Centric Mode..... | 34 | +| 7.4 | Radio interface timing procedures..... | 35 | +| 7.4.1 | LMU Functions..... | 35 | +| 7.4.2 | CRNC Functions..... | 35 | +| 7.4.3 | LMU-CRNC Interactions..... | 35 | +| 8 | Cell ID and Enhanced Cell ID based positioning methods..... | 36 | +| 8.1 | Cell ID determination..... | 39 | +| 8.1.1 | UE Cell ID is not known..... | 39 | +| 8.1.2 | UE Cell ID is known..... | 39 | +| 8.1.2.1 | UE not in Soft handover..... | 39 | +| 8.1.2.2 | UE in Soft handover..... | 39 | +| 8.2 | Mapping the Cell ID to Geographic Co-ordinates or a Service Area..... | 40 | +| 8.3 | Enhanced Cell ID Methods..... | 40 | +| 8.3.1 | Cell-ID with RTT..... | 41 | +| 8.3.2 | Cell-ID with Pathloss and Related Measurements..... | 41 | +| 8.3.2.1 | RF Pattern Matching (RFPM)..... | 41 | +| 8.3.3 | Cell-ID with Angle of Arrival..... | 41 | +| 9 | OTDOA positioning method..... | 41 | +| 9.1 | Use of Idle Periods..... | 43 | +| 9.2 | Relative Time Difference (RTD)..... | 43 | +| 9.3 | Time of Day (ToD)..... | 44 | +| 9.4 | Node B Synchronisation..... | 44 | +| 9.5 | OTDOA-IPDL and OTDOA Modes..... | 44 | +| 9.5.1 | Information to be transferred between UTRAN elements..... | 44 | +| 9.6 | OTDOA network positioning procedures..... | 46 | +| 9.6.1 | RNC based selection of OTDOA..... | 46 | +| 9.6.2 | SAS based selection of OTDOA..... | 48 | +| 10 | Network-assisted GPS positioning method..... | 51 | +| 10.1 | Timing calibration..... | 52 | +| 10.2 | Timing assistance..... | 52 | +| 10.3 | GPS assistance data..... | 52 | +| 10.4 | UE search..... | 53 | +| 10.5 | Position determination..... | 53 | +| 10.5.1 | Information to be transferred between UTRAN elements..... | 53 | +| 10.5.1.1 | Almanac data..... | 54 | +| 10.5.1.2 | DGPS corrections..... | 55 | +| 10.5.1.3 | Ionospheric corrections..... | 55 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------|-----------| +| 10.5.1.4 | Ephemeris data and clock correction ..... | 55 | +| 10.5.1.5 | Real Time integrity monitor function ..... | 55 | +| 10.5.1.6 | GPS reference time ..... | 56 | +| 10.5.1.7 | UTC ..... | 56 | +| 10.5.1.8 | Reference Location ..... | 56 | +| 10.5.1.9 | Additional non-GPS related information ..... | 56 | +| 10.6 | RNC based Network Assisted GPS positioning Procedure ..... | 57 | +| 10.7 | SAS initiated Network Assisted GPS positioning Procedure ..... | 58 | +| 11 | Information storage ..... | 60 | +| 12 | Uplink-Time Difference Of Arrival (U-TDOA) positioning method ..... | 60 | +| 12.1 | General ..... | 60 | +| 12.2 | U-TDOA SAS architecture ..... | 63 | +| 12.3 | RNC based U-TDOA positioning for Cell_DCH and Cell_FACH RRC states ..... | 63 | +| 12.3.1 | UE in CELL_DCH state ..... | 63 | +| 12.3.2 | UE in CELL_FACH state ..... | 64 | +| 12.4 | Optional SAS initiated U-TDOA positioning for Cell_DCH and Cell_FACH RRC states ..... | 66 | +| 12.4.1 | UE in CELL_DCH state ..... | 66 | +| 12.4.1.1 | Message Flow ..... | 66 | +| 12.4.2 | UE in CELL_FACH state ..... | 68 | +| 12.4.2.1 | Message flow ..... | 68 | +| 13 | Network-assisted GNSS positioning method ..... | 70 | +| 13.1 | Network-assisted GPS positioning method ..... | 71 | +| 13.2 | Network-assisted Galileo positioning method ..... | 71 | +| 13.3 | Network-assisted GLONASS positioning method ..... | 71 | +| 13.4 | Network-assisted Satellite Based Augmentation Systems (SBAS) ..... | 71 | +| 13.5 | Network-assisted Quasi-Zenith Satellite System (QZSS) ..... | 71 | +| 13.6 | Network-assisted BeiDou Navigation Satellite System (BDS) positioning method ..... | 71 | +| 14 | Barometric Pressure positioning methods ..... | 72 | +| 14.1 | General ..... | 72 | +| 14.2 | Information to be transferred between UTRAN Elements ..... | 72 | +| 14.2.1 | Information that may be transferred from the UE to Network ..... | 72 | +| 14.2.1.1 | Standalone mode ..... | 72 | +| 14.2.1.2 | UE-assisted mode ..... | 72 | +| 14.3 | Location Information Transfer Procedure ..... | 73 | +| 14.3.1 | SAS initiated Barometric Pressure positioning procedure ..... | 73 | +| 15 | WLAN positioning method ..... | 74 | +| 15.1 | Information to be transferred between UTRAN elements ..... | 75 | +| 15.2 | SAS initiated WLAN positioning procedure ..... | 75 | +| 16 | Bluetooth positioning methods ..... | 77 | +| 16.1 | Information to be transferred between UTRAN elements ..... | 78 | +| 16.2 | SAS initiated Bluetooth positioning procedure ..... | 78 | +| 17 | TBS positioning methods ..... | 80 | +| 17.1 | General ..... | 80 | +| 17.2 | Information to be transferred between UTRAN Elements ..... | 81 | +| 17.2.1 | Information that may be transferred from the UE to SAS ..... | 81 | +| 17.2.1.1 | Standalone mode ..... | 81 | +| 17.2.1.2 | UE-assisted mode ..... | 81 | +| 17.3 | Location Information Transfer Procedure ..... | 81 | +| 17.3.1 | SAS initiated TBS positioning procedure ..... | 81 | +| Annex A (informative): | Definitions and Terms ..... | 84 | +| Annex B (informative): | Reference Model of Functional Entities for UTRAN UE Positioning ..... | 86 | +| B.1 | Internal Client Group ..... | 88 | +| B.1.1 | Internal UTRAN Location Client Function (U-LCF) ..... | 88 | +| B.2 | UTRAN System Handling group ..... | 88 | +| B.2.1 | UTRAN Location System Control Function (U-LSCF) ..... | 88 | +| B.2.2 | UTRAN Location System Operations Function (U-LSOF) ..... | 89 | + +| | | | +|-------------------------------|----------------------------------------------------------------|-----------| +| B.2.3 | UTRAN Location Information Relay Function (U-LIRF)..... | 89 | +| B.2.4 | UTRAN Location System Control Function in SAS (U-LSCFS)..... | 89 | +| B.2.5 | UTRAN Location System Assistance Data Function (U-LSADF)..... | 90 | +| B.3 | Positioning group ..... | 90 | +| B.3.1 | UTRAN Position Radio Co-ordination Function (U-PRCF) ..... | 90 | +| B.3.2 | UTRAN Position Calculation Function (U-PCF)..... | 90 | +| B.3.3 | UTRAN Position Signal Measurement Function (U-PSMF)..... | 90 | +| B.3.4 | UTRAN Position Radio Resource Management (U-PRRM)..... | 91 | +| B.3.5 | UTRAN Position Related Communication Function (U-PRComF) ..... | 91 | +| B.4 | Assignment of LCS Functional Entities to UTRAN Elements ..... | 91 | +| Annex C (informative): | Location Services Categories..... | 93 | +| Annex D (informative): | Change history..... | 94 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the stage 2 of the UE Positioning function of UTRAN, which provides the mechanisms to support the calculation of the geographical position of a UE. UE position knowledge can be used for example in support of Radio Resource Management functions, location-based services for operators, subscribers and third party service providers. The purpose of this stage 2 specification is to define the UTRAN UE Positioning architecture, functional entities and operations to support positioning methods. This description is confined to the UTRAN Access Stratum. It does not define nor describe how the results of the UE position calculation can be utilised in the Core Network (e.g. LCS) or in UTRAN (e.g. RRM). + +UE Positioning may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included. + +This stage 2 specification covers the UTRAN positioning methods, state descriptions, and message flows to support UE Positioning. + +# --- 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*. + +## 2.1 Normative references + +- [1] Void. +- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] Void. +- [4] 3GPP TS 23.271: "Location Services (LCS); (Functional description) - Stage 2". +- [5] 3GPP TS 22.071: "Location Services (LCS); Service description, Stage 1". +- [6] 3GPP TS 22.100: "UMTS phase 1". +- [7] 3GPP TS 22.101: "Services aspects; Service principles". +- [8] 3GPP TS 22.105: "Services and Service Capabilities". +- [9] 3GPP TS 22.115: "Services aspects; Charging and Billing". +- [10] 3GPP TS 22.121: "Services aspects; The Virtual Home Environment; Stage 1". +- [11] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [12] 3GPP TS 23.110: "UMTS Access Stratum; Services and Functions". +- [13] 3GPP TS 23.171: "Functional stage 2 description of location services in UMTS". +- [14] 3GPP TS 25.214: "Physical layer procedures (FDD)" +- [15] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". + +- [16] 3GPP TS 25.225: "Physical layer – Measurements (TDD)". +- [17] 3GPP TS 25.306: "UE Radio Access Capabilities". +- [18] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [19] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [20] 3GPP TS 25.423: "UTRAN Iur interface RNSAP signalling". +- [21] 3GPP TS 25.430: "UTRAN Iub interface: General aspects and Principles". +- [22] 3GPP TS 25.433: "UTRAN Iub interface NBAP signalling". +- [23] ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interfaces". +- [24] RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service" (v.2.2.) +- [25] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols - Stage 3". +- [26] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [27] 3GPP TS 25.453: "UTRAN Iupc interface PCAP signalling". +- [28] 3GPP TS 25.412: "Iu interface signalling transport". +- [31] BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 2.0), December 2013". +- [32] IEEE 802.11 Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. +- [33] Bluetooth Special Interest Group: "Bluetooth Core Specification v4.2", December 2014. +- [34] ATIS-0500027: "Recommendations for Establishing Wide Scale Indoor Location Performance," May 2015. + +## 2.2 Informative references + +- [29] Third generation (3G) mobile communication system; Technical study report on the location services and technologies, ARIB ST9 December 1998. +- [30] The North American Interest Group of the GSM MoU ASSOCIATION: Location Based Services, Service Requirements Document of the Services Working Group. + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in [7] and some of the terms and definitions in annex A apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply. + +| | | +|---------|----------------------------------------------------------| +| 3G-MSC | 3 rd Generation MSC | +| 3G-SGSN | 3 rd Generation SGSN | +| A-GNSS | Assisted Global Navigation Satellite System | +| A-GPS | Assisted Global Positioning Systems | +| ARIB | Association of Radio Industries and Business | +| BDS | BeiDou Navigation Satellite System | +| CAMEL | Customised Application For Mobile Network Enhanced Logic | +| CN | Core Network | + +| | | +|---------|----------------------------------------------------------------------------------------------| +| CRNC | Controlling RNC | +| DGNSS | Differential Global Navigation Satellite System | +| DGPS | Differential Global Positioning Systems | +| DL | Downlink | +| DRNC | Drift RNC | +| EGNOS | European Geostationary Navigation Overlay Service | +| E-OTD | Enhanced Observed Time Difference | +| GAGAN | GPS Aided Geo Augmented Navigation | +| GDOP | Geometric Dilution of Precision | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GMLC | Gateway MLC | +| GNSS | Global Navigation Satellite System | +| GPRS | General Packet Radio System | +| GPS | Global Positioning System | +| HLR | Home Location Register | +| HOW | HandOver Word | +| IM | Integrity Monitor | +| IPDL | Idle Period Downlink | +| LBS | Location Based Services | +| LCCF | Location Client Control Function | +| LCF | Location Client Function | +| LCS | LoCation Services | +| LIRF | Location Information Relay Function | +| LMU | Location Measurement Unit | +| LSADF | Location System Assistance Data Function | +| LSCF | Location System Control Function | +| LSCFS | Location System Control Function in SAS | +| LSOF | Location System Operation Function | +| MBS | Metropolitan Beacon System | +| MLC | Mobile Location Centre | +| MMS | Multimedia Messaging Service | +| MSAS | Multi-functional Satellite Augmentation System | +| MSC | Mobile services Switching Centre | +| NAS | Non Access Stratum | +| OTDOA | Observed Time Difference Of Arrival | +| PCAP | Positioning Calculation Application Part | +| PCF | Position Calculation Function | +| PLMN | Public Land Mobile Network | +| PRC | Pseudo-Range Correction | +| PRCF | Positioning Radio Co-ordination Function | +| PRComF | Positioning Radio Communication Function | +| PRRC | Pseudo-Range Rate Correction | +| PRRM | Positioning Radio Resource Management | +| PSMF | Positioning Signal Measurement Function | +| QoS | Quality of Service | +| QZSS | Quasi-Zenith Satellite System | +| RAN | Radio Access Network | +| RANAP | Radio Access Network Application Part | +| RNC | Radio Network Controller | +| RRM | Radio Resource Management | +| RTD | Real Time Difference | +| RTT | Round Trip Time | +| SAI | Service Area Identifier | +| SAS | Stand-Alone SMLC | +| SBAS | Satellite Based Augmentation System | +| SGSN | Serving GPRS Support Node | +| SIM | Subscriber Identity Module | +| SMS | Short Message Service | +| SRNC | Serving RNC | +| SSDT | Site Selection Diversity Transmit | +| TBS | Terrestrial Beacon System | +| TOA | Time Of Arrival | + +| | | +|----------|------------------------------------------------| +| TOW | Time Of Week | +| U-..... | UMTS-(LCS functional block) | +| U-LCF | internal UTRAN Location Client Function | +| U-LSCF | UTRAN Location System Control Function | +| U-LSOF | UTRAN Location System Operations Function | +| U-LIRF | UTRAN Location Information Relay Function | +| U-LSCFS | UTRAN Location System Control Function in SAS | +| U-LSADF | UTRAN Location System Assistance Data Function | +| U-PRCF | UTRAN Position Radio Co-ordination Function | +| U-PCF | UTRAN Position Calculation Function | +| U-PSMF | UTRAN Position Signal Measurement Function | +| U-PRRM | UTRAN Position Radio Resource Management | +| U-PRComF | UTRAN Position Related Communication Function | +| UDRE | User Differential Range Error | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunication System | +| USIM | User Service Identity Module | +| UTC | Universal Time Coordinates | +| U-TDOA | Uplink – Time Difference Of Arrival | +| UTRAN | Universal Terrestrial Radio Access Network | +| WAAS | Wide Area Augmentation System | +| WCDMA | Wideband Code Division Multiple Access | +| WLAN | Wireless Local Area Network | + +# --- 4 Main concepts and requirements + +The stage 1 LCS description providing an overall service description and the core requirements for the LCS at the service level is given in [5]. The stage 2 LCS description providing a system functional model for the whole system, the LCS system architecture, state descriptions and message flows are described in [13]. + +By measuring radio signals the capability to determine the geographic position and velocity of the UE shall be provided. The position information may be requested by and reported to a client (application) associated with the UE, or by a client within or attached to the CN. The position information may also be utilised internally by UTRAN, for example, for location-assisted handover or to support other features such as home location billing. The position information shall be reported in standard formats, such as those for cell based or geographical co-ordinates, together with the estimated errors (uncertainty) of the position and velocity of the UE and, if available, the positioning method (or the list of the methods) used to obtain the position estimate. Restrictions on the geographic shape encoded within the 'position information' parameter may exist for certain LCS client types. The SRNC shall comply with any shape restrictions defined in GSM/UMTS and, in a particular country, with any shape restrictions defined for a specific LCS client type in relevant national standards. For example, in the US, national interim standard TIA/EIA/IS-J-STD-036 restricts the geographic shape for an emergency services LCS client to minimally either an "ellipsoid point" or an "ellipsoid point with uncertainty circle and confidence" as defined in [11]. + +It shall be possible for the majority of the UE (active or inactive) within a network to use the feature without compromising the radio transmission or signalling capabilities of the UTRAN. + +The uncertainty of the position measurement shall be network implementation dependent at the choice of the network operator. The uncertainty may vary between networks as well as from one area within a network to another. The uncertainty may be hundreds of metres in some areas and only a few metres in others. In the event that the position measurement is also a UE-assisted process, the uncertainty may also depend on the capabilities of the UE. In some jurisdictions, there is a regulatory requirement for location service accuracy that is part of an emergency service. Further details of the accuracy requirements can be found in [5]. + +The uncertainty of the position information is dependent on the method used, the position of the UE within the coverage area and the activity of the UE. Several design options of the UTRAN system (e.g. size of cell, adaptive antenna technique, path loss estimation, timing accuracy, Node B surveys) shall allow the network operator to choose a suitable and cost effective UE Positioning method for their market. + +There are many different possible uses for the positioning information. The positioning functions may be used internally by the UTRAN, by value-added network services, by the UE itself or through the network, and by "third party" + +services. The feature may also be used by an emergency service (which may be mandated or "value-added"), but the location service is not exclusively for emergencies. + +The UTRAN is a new radio system design without a pre-existing deployment of UE operating according to the radio interface. This freedom from legacy equipment enables the location service feature design to make use of appropriate techniques to provide the most accurate results. The technique must also be a cost-effective total solution, must allow evolution to meet evolving service requirements and be able to take advantage of advances in technology over the lifetime of UTRAN deployments. + +## 4.1 Assumptions + +As a basis for the operation of UE Positioning in UTRAN the following assumptions apply: + +- both TDD and FDD will be supported; +- the provision of the UE Positioning function in UTRAN is optional through support of the specified method(s) in Node B, the SAS, and the RNC; +- UE Positioning is applicable to any target UE whether or not the UE supports LCS, but with restrictions on use of certain positioning method depending on UE capability as defined in [17]; +- The SMLC may be either a stand-alone network element (SAS) or an internal function of the RNC; +- UE Positioning information is transported between RNCs via the Iur interface independent of whether the SMLC is a stand-alone network element (SAS) or an internal function of the RNC; +- the positioning information may be used for internal system operations to improve system performance; +- different types of LMU are defined, e.g. a standalone LMU and/or LMU integrated in Node B; +- the UE Positioning architecture and functions shall include the option to accommodate several techniques of measurement and processing to ensure evolution to follow changing service requirements and to take advantage of advancing technology; +- the RNC manages the overall coordination and scheduling of resources required to perform positioning of a UE. It may also calculate the final position and velocity estimate and accuracy. + +## 4.2 UE Positioning Methods + +The UTRAN may utilise one or more positioning methods in order to determine the position of an UE. + +Positioning the UE involves two main steps: + +- signal measurements; and +- Position estimate and optional velocity computation based on the measurements. + +The signal measurements may be made by the UE, the Node B or an LMU. The basic signals measured are typically the UTRA radio transmissions, however, some methods may make use of other transmissions such as general radio navigation signals. + +The positioning function should not be limited to a single method or measurement. That is, it should be capable of utilising other standard methods and measurements, as are available and appropriate, to meet the required service needs of the location service client. This additional information could consist of readily available UTRAN measurements such as RTT in FDD or Rx Timing deviation measurement and knowledge of the UE timing advance, in TDD. + +The position estimate computation may be made by the UE or by the UTRAN (i.e. SRNC or SAS). + +## 4.3 Standard UE Positioning Methods + +The standard positioning methods supported within UTRAN are: + +- cell ID based method; +- OTDOA method that may be assisted by network configurable idle periods; + +- network-assisted GNSS methods; +- U-TDOA; +- Barometric Pressure method; +- WLAN method; +- Bluetooth method; +- Terrestrial Beacon System methods. + +NOTE: Barometric Pressure method, WLAN method, Bluetooth method, and Terrestrial Beacon System methods can only be configured using RRC signaling together with OTDOA or GPS positioning methods. + +### 4.3.1 Cell ID and Enhanced Cell ID Based Methods + +In the cell ID based (i.e. cell coverage) method, the position of an UE is estimated with the knowledge of its serving Node B. The information about the serving Node B and cell may be obtained by paging, locating area update, cell update, URA update, or routing area update. + +The cell coverage based positioning information can be indicated as the Cell Identity of the used cell, the Service Area Identity or as the geographical co-ordinates of a position related to the serving cell. The position information shall include a QoS estimate (e.g. regarding achieved accuracy) and, if available, the positioning method (or the list of the methods) used to obtain the position estimate. + +When geographical co-ordinates are used as the position information, the estimated position of the UE can be a fixed geographical position within the serving cell (e.g. position of the serving Node B), the geographical centre of the serving cell coverage area, or some other fixed position within the cell coverage area. Enhanced Cell ID methods use additional UE and/or UTRAN radio resource related measurements. + +The operation of the cell ID and Enhanced Cell ID based positioning methods are described in clause 8. + +### 4.3.2 OTDOA-IPDL Method with network configurable idle periods + +The OTDOA-IPDL method involves measurements made by the UE and LMU of the UTRAN frame timing (e.g. SFN-SFN observed time difference). These measures are then sent to the SRNC and, in networks which include an SAS, may be forwarded to the SAS. Depending on the configuration of the network, the position of the UE is calculated in the SRNC or in the SAS. + +The simplest case of OTDOA-IPDL is without idle periods. In this case the method can be referred to as simply OTDOA. + +The Node B may provide idle periods in the downlink, in order to potentially improve the hearability of neighbouring Node Bs. The support of these idle periods in the UE is optional. Support of idle periods in the UE means that its OTDOA performance will improve when idle periods are available. + +Alternatively, the UE may perform the calculation of the position using measurements and assistance data. + +The detailed description of the OTDOA-IPDL positioning method and its operation are described in clause 9. + +### 4.3.3 Network-assisted GNSS Methods + +These methods make use of UEs, which are equipped with radio receivers capable of receiving GNSS signals. + +Examples of GNSS include GPS, Modernized GPS, Galileo, GLONASS, Satellite Based Augmentation Systems (SBAS), Quasi Zenith Satellite System (QZSS), and BeiDou Navigation Satellite System (BDS). + +In this concept, different GNSS (e.g. GPS, Galileo, etc.) can be used separately or in combination to perform the location of a UE. + +The operation of the network-assisted GNSS methods is described in clause 13. + +### 4.3.4 U-TDOA Method + +The U-TDOA positioning method is based on network measurements of the Time Of Arrival (TOA) of a known signal sent from the UE and received at four or more LMUs. The method requires LMUs in the geographic vicinity of the UE to be positioned to accurately measure the TOA of the bursts. Since the geographical coordinates of the measurement units are known, the UE position can be calculated via hyperbolic trilateration. This method will work with existing UE without any modification. + +The operation of the U-TDOA location method is described in clause 12. + +### 4.3.5 Barometric Pressure positioning + +The barometric pressure method makes use of barometric pressure sensors for identifying height information and to determine the vertical component of the position of the UE. This method should be combined with other positioning methods to determine the 3D position of the UE. + +The operation of the Barometric Pressure positioning method is described in clause 14. + +### 4.3.6 WLAN positioning + +The WLAN positioning method makes use of the WLAN measurements (AP identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN [32] access points. Using the measurements results and a references database, the location of the UE is calculated. + +The operation of the WLAN positioning method is described in clause 15. + +### 4.3.7 Bluetooth positioning + +The Bluetooth positioning method makes use of the Bluetooth measurements (Bluetooth beacon identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from Bluetooth [33] beacons. Using the measurements results and a references database, the location of the UE is calculated. + +The operation of the Bluetooth positioning method is described in clause 16. + +### 4.3.8 TBS positioning + +A Terrestrial Beacon System (TBS) consists of a network of ground-based transmitters, broadcasting signals only for positioning purposes. The current type of TBS positioning signals are the MBS (Metropolitan Beacon System) signals [34]. + +The operation of the TBS positioning method is described in clause 17. + +# --- 5 UTRAN UE Positioning Architecture + +Figure 5.1 shows the general arrangement of the UE positioning feature in UTRAN. Communication among the UTRAN UE Positioning entities makes use of the messaging and signalling capabilities of the UTRAN interfaces (Iub, Iur, Iupc). + +The SRNC, receives authenticated requests for UE positioning information from the CN across the Iu interface. RNCs manage the UTRAN resources (including Node Bs, LMUs, the SAS) the UE and calculation functions, to estimate the position of the UE and return the result to the CN. SRNC may also make use of the UE Positioning function for internal purpose e.g. position based handover. + +![Figure 5.1: General arrangement of UE Positioning in UTRAN. The diagram shows a UE connected to a Node B (Associated LMU), which is connected to an RNC. The RNC is connected to a CN via an Iu interface. A Stand-Alone LMU is connected to the UE via a Uu interface. A SAS is connected to the RNC via an Iupc interface. A second Node B (Associated LMU) is connected to another RNC via an Iub interface. The second RNC is connected to the first RNC via an Iur interface. A legend indicates that dashed lines represent Optional connections and solid lines represent Mandatory connections.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +graph TD + StandAloneLMU[Stand-Alone LMU] -.->|Uu| UE[UE] + UE --- NodeB1[Node B +(Associated LMU)] + NodeB1 --- Iub --- RNC1[RNC] + RNC1 --- Iu --- CN[CN] + SAS[SAS] -.->|Iupc| RNC1 + RNC1 --- Iur --- RNC2[RNC] + NodeB2[Node B +(Associated LMU)] --- Iub --- RNC2 + style StandAloneLMU fill:none,stroke:none + style SAS fill:none,stroke:none + style UE fill:none,stroke:none + style NodeB1 fill:none,stroke:none + style RNC1 fill:none,stroke:none + style CN fill:none,stroke:none + style NodeB2 fill:none,stroke:none + style RNC2 fill:none,stroke:none + style Iub1[Iub] fill:none,stroke:none + style Iu1[Iu] fill:none,stroke:none + style Iupc1[Iupc] fill:none,stroke:none + style Iur1[Iur] fill:none,stroke:none + style Uu1[Uu] fill:none,stroke:none + style Optional[Optional] fill:none,stroke:none + style Mandatory[Mandatory] fill:none,stroke:none + +``` + +Figure 5.1: General arrangement of UE Positioning in UTRAN. The diagram shows a UE connected to a Node B (Associated LMU), which is connected to an RNC. The RNC is connected to a CN via an Iu interface. A Stand-Alone LMU is connected to the UE via a Uu interface. A SAS is connected to the RNC via an Iupc interface. A second Node B (Associated LMU) is connected to another RNC via an Iub interface. The second RNC is connected to the first RNC via an Iur interface. A legend indicates that dashed lines represent Optional connections and solid lines represent Mandatory connections. + +**Figure 5.1: General arrangement of UE Positioning in UTRAN** + +## 5.1 UE Positioning Operations + +The schematic functional description of LCS operations in UMTS is defined in [13]. + +Upon request from the Core Network or for internal operations, a UTRAN UE Positioning function should: + +- request measurements, typically from the UE and one or more Node B; +- send the measurement results to the appropriate calculating function within UTRAN; +- receive the result from the calculating function within UTRAN; +- perform any needed co-ordinate transformations; +- send the results to the LCS entities in the CN or to application entities within UTRAN (this function applies to the RNC only). + +In the event that the client is internal to UTRAN the request may be made directly to the UTRAN UE Positioning entities as the internal clients are considered to be "pre-authorised". + +As part of its operation, the UTRAN UE Positioning calculating function may require additional information. This may be obtained by the function directly by communication with a database, or it may be through a request to UTRAN UE Positioning entities that will mediate the request and return of information from the appropriate database (or databases if more than one is needed to fulfil the requests). + +There may possibly also be available independent information that is able to supply the positioning information directly, or may be able to supply auxiliary information to the calculation function. The UTRAN UE Positioning co-ordination function, as part of its activity to supervise the positioning process, may query the UE or other elements of the UTRAN to determine their capabilities and use this information to select the mode of operation. + +This general operation is outlined in the following (generic) sequence diagram figure 5.2. This figure is not intended to show the complete UE Positioning operation for UTRAN, but to simply to outline the basis for operation. + +![Sequence diagram for UE Positioning operation showing interactions between CN LCS Entities and UTRAN Entities (Coordination, Measurement, Calculation).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant CN_LCS as CN LCS Entities + participant UTRAN as UTRAN Entities + Note right of UTRAN: Coordination | Measurement | Calculation + CN_LCS->>UTRAN: Location Request + UTRAN->>UTRAN: measure request + UTRAN->>UTRAN: measurements + UTRAN->>UTRAN: calculation request + UTRAN->>UTRAN: calculation results + UTRAN->>CN_LCS: Location Response + +``` + +Sequence diagram for UE Positioning operation showing interactions between CN LCS Entities and UTRAN Entities (Coordination, Measurement, Calculation). + +**Figure 5.2: General sequence for UE Positioning operation** + +### 5.1.1 Co-ordination, Measurement and Calculation Functions + +The UTRAN functions for UE Positioning provide the co-ordination, measurement and calculation functions needed to provide a position and optional velocity estimate. The functions interface with the requesting application and select the appropriate positioning method and speed of response. The functions co-ordinate the operations of the radio and measurement equipment to transmit the needed signals and to make the needed measurements. The measurements may be made by the Node Bs, or by the LMU. The LMU may be associated with the Node B, independently located or remote (i.e. communicating over the Uu interface). + +The functions may also access databases or other sources of information appropriate for the positioning method. The functions also provide the calculation functions appropriate for the positioning method to estimate the UE position and the accuracy of the report. The functions may also make co-ordinates translations to the geographic co-ordinates system requested by the application. The functions also may record information on the usage of the UE Positioning that may be used for administrative purposes (e.g. forwarded to a billing function in the CN). If needed by the positioning method, the functions will ensure the broadcast of information and gather and update information concerning UTRAN operating parameters (e.g. timing of Node B transmissions) needed for UE Positioning operations. + +These entities are mainly concerned with the positioning method, controlling the radio equipment and performing the calculations to determine the position and thus may be associated with the RNC in the UTRAN. These functions may receive location requests from either the CN or from applications internal to the UTRAN. + +The UTRAN UE Positioning entities may also request the subscription and authorisation functions in the CN to authenticate an application or a UE subscription or to verify the subscriber privacy parameters. + +The RNC functions communicate with the CN across the Iu interface, with other RNC entities across the Iur interface and with the Node B and LMU across the Iub interface, with the SAS across the Iupc interface, and with the UE and the remote LMU across the Uu interface. + +## 5.2 Functional Description of UTRAN UE Positioning related elements + +### 5.2.1 Radio Network Controller (RNC) + +#### 5.2.1.1 Serving RNC + +The SRNC is a network element of UTRAN and contains functionality required to support LCS in one PLMN. The SRNC can work either in the RNC centric mode or in a SAS centric mode where the SAS has control over the positioning procedures. + +##### 5.2.1.1.1 RNC Centric Mode + +In RNC centric mode the SRNC provides the following functionality: + +- request of information from other RNC: +The SRNC may request information regarding UE Positioning from other RNCs; +- flow control of positioning requests: +If several simultaneous positioning requests are present within one SRNC, the SRNC co-ordinates the positioning requests taking into account priority of the requests (e.g. for Emergency Clients); +- positioning method selection: +The positioning method selection is based on the location request, QoS, capabilities of UE Positioning elements and UE positioning capabilities; +- position calculation: +The SRNC may calculate the position of a UE and may also support conversion of the position estimate between different geographic reference systems. In case RNC estimates the UE position, it is also responsible to estimate the accuracy of the position estimate. This accuracy estimate should include, for example, the effect of geometric dilution of precision (GDOP), the capabilities of the signal measuring hardware, the effects of multipath propagation and the effects of timing and synchronisation unknowns. The accuracy should be returned as a measure of distance in the same units as the position estimate. The accuracy zone may be reported as the axis and orientation of an ellipse surrounding the position estimate. If available, the positioning method (or the list of the methods) used to obtain the position estimate may also be returned to the CN with the position information. If the CN has requested an accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +- provide UE Positioning assistance data: +The SRNC may provide assistance data in the support of the various positioning methods; +- Overall UE Positioning coordination and control: +If both an SAS and an SRNC with SMLC internal functionality are available, the SRNC is responsible for the overall coordination and control of UE Positioning. For example, although the SAS has a position calculation function, the SRNC may also have a position calculation function. The SRNC is responsible for managing the co-ordination and control of these multiple resources. + +The SRNC, of course, also provides CRNC functionality regarding UE Positioning for its associated Node Bs and LMUs. + +##### 5.2.1.1.2 SAS Centric Mode + +In SAS centric mode the SRNC provides the following functionality: + +- Forwarding of location requests to the SAS: +The SRNC forwards incoming location requests to the SAS and provides further information like UE capabilities and UE Cell ID to guide the positioning method selection in the SAS +- Forwarding of UE positioning assistance data and measurement instructions +Upon request from the SAS, the SRNC forwards assistance data and/or measurement instructions from the SAS to the UE in support of the various positioning methods. +- Delivery of positioning information +Upon request from the SAS the SRNC gathers location related information from the NodeBs and the UE and sends this information back to the SAS. +- Forwarding of positioning estimates +The SRNC forwards the positioning result received from the SAS to the requesting CN entity. + +#### 5.2.1.2 Other RNC + +##### 5.2.1.2.1 Controlling RNC + +The CRNC provides the following functionality: + +- resources management: +When allocating resources the CRNC determines which UTRAN elements are involved and what to measure. The RNC is also responsible for managing the effect of UE Positioning operations on the overall performance of the radio network by: + - controlling the variation of the UL and DL signal power level due to UE Positioning; + - calculating the DL and UL power/interference due to UE Positioning; + - to admit/reject the new positioning requests; + - co-operating with Admission Control, and entities of the RRM (such as power control) to provide the system stability in terms of radio resources; + - controlling the IPDL mechanism for OTDOA measurements. This may include the overall control of the periodical measurement fulfilment. Co-ordination among RNCs (e.g. to assure non-overlapping idle periods) will be communicated through the Iur interface. +- broadcast of system information: +The CRNC broadcasts information in support of the selected positioning method. This broadcast information may be specially coded (i.e. encrypted) to ensure its availability only to subscribers of the service. For the case where there exists an SAS, the broadcast data is generated within the CRNC and/or, depending on the positioning method, may also be generated in the SAS which then forwards it to the CRNC over the Iupc interface for eventual broadcast over the Uu interface. + +The information to be broadcast could include, for example: + +- identification and spreading codes of the neighbouring cells (the channels that are used for measurements); +- Relative Time Difference (RTD), i.e. the timing offsets, asynchronicity between base stations, could be based on measurement results obtained by LMUs; +- roundtrip delay estimates in connected mode; +- the geographic position co-ordinates of the neighbouring Node B; +- the idle period places within the frame structure for multiple cells; +- the local time-of-day; +- reference time, reference position, DGNSS corrections, ephemeris and clock data, and almanac data. +- request UE Positioning related measurements from its associated Node Bs and LMUs: +The measurements requested by CRNC from its associated Node Bs and LMUs is dependant on the positioning method used. The following measurement returned by a LMU to a CRNC has a general status and may be used for more than one positioning method: + - radio interface timing information. + +Signalling between Node B or LMU and CRNC is transferred using Iub signalling. + +##### 5.2.1.2.2 Drift RNC + +The DRNC is a UTRAN element that has an active link to the UE that shall be located. The DRNC, of course, also provides CRNC functionality regarding UE Positioning for its associated Node Bs and LMUs. + +### 5.2.2 Node B + +Node B is a network element of UTRAN that may provide measurement results for position estimation and makes measurements of radio signals and communicates these measurements to the CRNC. + +The Node B may make its measurements in response to requests (e.g. from the CRNC), or it may autonomously measure and report regularly or when there are significant changes in radio conditions (e.g. changes in the UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference). + +### 5.2.3 Location measurement unit (LMU) + +Location Measurement Units (LMU) are associated with either the CRNC or the SAS. LMUs associated with the SAS are outside the scope of this specification. + +The Location Measurement Unit (LMU) entity makes measurements (e.g. of radio signals) and communicates these measurements to a RNC. The LMU may also perform calculations associated with the measurements. + +All positioning and assistance measurements obtained by an LMU are supplied to a particular CRNC associated with the LMU. Instructions concerning the timing, the nature and any periodicity of these measurements are either provided by the CRNC or are pre-administered in the CRNC (e.g. using O&M). + +The LMU may make its measurements in response to requests (e.g. from the CRNC), or it may autonomously measure and report regularly (e.g. timing of Node B transmissions) or when there are significant changes in radio conditions (e.g. changes in the UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference). + +There may be one or more LMU associated with the UTRAN and an UE Positioning request may involve measurements by one or more LMU. The LMU may be of several types and the CRNCs will select the appropriate LMUs depending on the UE Positioning method being used. + +The LMU may be used, for example, to measure UTRAN transmissions either UL or DL. These measurements may be made either, for example, to locate the UE or to measure a system parameter needed by the UE Positioning such as the timing offset (UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference) of transmissions Node Bs. The LMU may also measure other transmissions, such as those of satellite navigation systems (i.e. GPS) and either report the measurements for use by the CRNC, or report the positioning results as determined by internal calculations of the LMU. The details of the measurements to be made by the LMU will be defined by the chosen UE Positioning method. + +An LMU makes radio measurements to support one or more positioning methods. These measurements fall into one of two categories: + +- (a) positioning measurements specific to one UE and used to compute its position; +- (b) assistance measurements applicable to all UEs in a certain geographic area. + +There are two classes of LMU: + +- **Stand-Alone LMU:** communicates with RNCs via the Uu interface; +- **Associated LMU:** communicates with RNCs via the Iub interface. + +The associated LMU signalling protocol is the NBAP. The protocol for stand-alone LMU UTRAN signalling will be the RRC protocol. + +#### Stand-Alone LMU + +A stand-alone LMU is accessed exclusively over the UTRAN air interface (Uu interface). There is no other connection from the stand-alone LMU to any other UTRAN network element. + +NOTE 1: This does not preclude a stand-alone LMU from also communicating with other access networks (e.g. GSM) through interfaces that are not part of the present document. + +A stand-alone LMU has a serving Node B that provides signalling access to its CRNC. A stand-alone LMU also has a serving 3G-MSC, VLR and a subscription profile in an HLR. A stand-alone LMU always has a unique IMSI and supports all radio resource and mobility management functions of the UTRAN radio interface that are necessary to support signalling. A stand-alone LMU shall support those connection management functions necessary to support UE Positioning signalling transactions with the CRNC and may support certain call control functions of to support signalling to an CRNC using a circuit switched data connection. + +NOTE 2: A network operator may assign specific ranges of IMSI for its LMUs and may assign certain digits within the IMSI to indicate the associated CRNC. Certain digits in the IMSI may also be used as a local identifier for an LMU within an CRNC. + +To ensure that a Stand-alone LMU and its associated CRNC can always access one another, an LMU may be homed (camped) on a particular cell site or group of cell sites belonging to one 3G-MSC. For any Stand-alone LMU with a subscription profile in an HLR, a special profile may be used to indicate the assigned supplementary services (e.g. the SMS-PP MT for data download via the SIM application toolkit, and barring of all incoming and possibly outgoing calls). An identifier in the HLR profile also distinguishes an LMU from a normal UE. All other data specific to an LMU is administered in the LMU and in its associated CRNC. + +#### Associated LMU + +An associated LMU is accessed over the Iub interface from an RNC. An associated LMU may make use of the radio apparatus and antennas of its associated Node B. The LMU may be either a logically separate network element addressed using some pseudo-cell ID, or connected to or integrated in a Node B. Signalling to an associated LMU is by means of messages routed through the controlling Node B. + +An associated LMU may be separated from the Node B, but still communicate with the CRNC via the Node B Iub interface. The interface between the associated LMU and its Node B is not part of the present document. + +NOTE 3: An associated LMU is not precluded from also communicating with other access networks (e.g. GSM) through interfaces that are not part of the present document. + +#### Measurements + +The assistance measurements obtained by an LMU are generic and are usable by more than one positioning method. These include: + +- **Radio Interface Timing measurements:** include UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference of the signals transmitted by Node B, where timing differences are measured relative to either some common reference clock (UTRAN GPS timing of cell frames) or the signals of another Node B (SFN-SFN Observed Time Difference); +- **Inter-System Timing measurements:** include timing measurements between the UTRAN radio signals transmitted by a Node B and an external system such as the GPS or GSM. + +### 5.2.4 User Equipment (UE) + +The UE may transmit the needed signals for uplink based UE Positioning measurements and to make measurements of downlink signals. The measurements to be made will be determined by the chosen positioning method. + +The UE may also contain LCS applications, or access an LCS application through communication with a network accessed by the UE or an application residing in the UE. This application may include the needed measurement and calculation functions to determine the UE's position with or without assistance of the UTRAN UE Positioning entities. This is outside of the scope of this specification. + +The UE may also, for example, contain an independent positioning function (e.g., GPS, WLAN, Bluetooth, Barometric Pressure, TBS) and thus be able to report its position, independent of the UTRAN transmissions. The UE with an independent positioning function may also make use of information broadcast by the UTRAN that assists the function. + +### 5.2.5 Stand-alone SMLC + +An SAS performs one or more of the following procedures: + +- Provide GNSS assistance data to the RNC, for both UE-assisted and UE-based method types, to be delivered through point-to-point or broadcast channels to UE; +- Act as a location calculation server if the location estimates are not to be calculated in the RNC; +- Performs a U-TDOA positioning of a particular UE on request of the SRNC; +- Optionally, the SAS may determine the most appropriate positioning method or combination of positioning methods. When the SAS location method determination option is selected: + +- o The SAS is responsible to select the set of GNSS assistance data to be sent to the UE for A-GNSS based positioning and provide that assistance data to the SRNC within the PCAP Position Activation Request message; + - o The SAS is responsible to request UE positioning related information from the SRNC, e.g. channel information or round trip time; + - o The SAS is responsible for coordination of simultaneous UE positioning requests from the CN. +- Selecting the set of U-TDOA capable LMUs to be involved in a U-TDOA location determination. + +The SAS communicates with the RNC over the Iupc interface enabling it to forward UE Positioning assistance data to UEs and to receive UE Positioning measurement data from the RNC. + +When timing assistance is needed, the SAS may rely on associated LMUs or on the RNC (and on the possibility to have GNSS receivers co-located with the RNC, the Node Bs and/or present in the UEs) to obtain that. + +# --- 6 Signalling protocols and interfaces + +## 6.1 LCS signalling between SRNC and MSC/SGSN + +LCS signalling between SRNC and MSC/SGSN is handled through the Iu interface, which is described in clause 6.6.1. + +## 6.2 SRNC signalling to a target UE + +SRNC signalling to a target UE is handled through the Uu interface, which is described in clause 6.6.4.1. + +## 6.3 Controlling RNC signalling to a standalone LMU + +CRNC signalling to a standalone LMU is handled through the Uu interface, which is described in clause 6.6.4.2. + +## 6.4 Controlling RNC signalling to an associated LMU + +CRNC signalling to an associated LMU is handled through the Iub interface, which is described in clause 6.6.3. + +## 6.5 RNC-to-RNC signalling for UE Positioning support + +The RNC-to-RNC signalling for UE Positioning support is handled through the Iur interface, which is described in clause 6.6.2. + +## 6.5a SAS to RNC signalling for PCAP + +The SAS to RNC signalling is described in clause 6.6.5. + +## 6.6 Interfaces + +There are five interfaces through which the UE Positioning entities communicate. These are the Iu, Iur, Iub, Uu and Iupc. + +NOTE: the interfaces between the Internal or External LCS applications and the 3G-MSC or 3G-SGSN are outside the scope of the present document. + +### 6.6.1 Iu Interface + +The Iu interface is used to communicate between the LCS functional entities in the CN and the UE Positioning entities in the UTRAN. Further specification of the messages and operations for LCS across the Iu interface may be found in reference [19]. + +### 6.6.2 Iur Interface + +UE Positioning operations at the Iur interface are defined in [20]. + +The Iur interface is used to communicate between the UE Positioning functional entities associated with the SRNC and other RNC in the UTRAN. The Iur interface is also used to communicate between the SRNC and the Internal UE Positioning Applications in the UTRAN. The UE Positioning entities associated with the SRNC are responsible for coordinating and responding to positioning requests received from the LCS entities in the CN or Internal Clients. + +When communicating between the SRNC and the UTRAN Internal UE Positioning Applications (e.g. located within other RNCs), the messages and protocols are those used over the Iur interface. Some positioning methods may require measurements by several LMU or Node B, some of which may be associated with other RNC. Commands and responses from these UE Positioning Entities are communicated over the Iur interface. In some cases, the UE Positioning Entities in the SRNC may make use of entities associated with other RNC. For example, a calculating function may be used in another RNC if the SRNC is too busy or does not contain the function or database information required by the chosen positioning method. + +Iur shall be used for UE Positioning signalling whenever it is available, even in the case when the RNCs connected to different 3G-MSCs or 3G-SGSN. + +Within UTRAN, Iur supports inter-RNC soft handover. Inter-RNC handover should also include UE Positioning, meaning that whenever an inter-RNC soft handover occurs, Iur should be able to support the functionality of the UE Positioning entities in RNCs. + +Iur shall be used also to collect RTD and other UE Positioning information from Node Bs under different RNCs that are not involved in handover. + +#### 6.6.2.1 Signalling between SRNC and DRNC + +Signalling between SRNC and DRNC is used to obtain LCS information specific to a UE that has an UE context to the DRNC. + +The signalling between SRNC and DRNC is done by using RNSAP procedures specified in [20]. + +#### 6.6.2.2 Signalling between SRNC and CRNC + +Signalling between SRNC and CRNC is used to obtain UE Positioning information and request LCS related transmissions or other radio operation (e.g. information about IPDL configuration) that is needed by SRNC for a certain positioning method. The requested information may be e.g. GPS assistance data in case a reference GPS receiver is not available at the SRNC or RTD results that may be provided by the CRNC. + +The procedures used for the signalling between SRNC and CRNC are not specified yet. + +### 6.6.3 Iub Interface + +UE Positioning operations at the Iub interface are defined in [21]. + +The Iub interface is used to communicate among the UE Positioning entities associated with the CRNC, the Node B and the associated LMU. + +This interface passes the request for measurements, the measurement results and requests for UE Positioning related transmissions or other radio operations needed by the positioning method (e.g. broadcast of parameters needed for a UE-based positioning method). Measurement requests and results are signalled by using NBAP procedures. + +#### 6.6.3.1 Signalling between CRNC and associated LMU + +Signalling exchanges between an CRNC and a LMU under the control of that CRNC will be specified in the NBAP protocol for associated LMUs. + +The protocol layers employed to enable signalling between the CRNC and an associated LMU are defined in [22]. The LMU signalling information elements are included directly in the NBAP protocol, defined in [22]. + +### 6.6.4 Uu Interface + +UE Positioning operations at the Uu interface are generally defined in [13]. This specification defines in more detail the procedures needed for messaging for each individual positioning method. + +The Uu interface is used to communicate among the UE Positioning entities associated with the SRNC, the UEs and the stand-alone LMU. + +The Uu interface may pass measurement requests and results to and from the UE or the stand-alone LMU. + +The Uu interface may also be used for broadcast of information that may be used by the UE or stand-alone LMU for their UE Positioning operations. This may, for example, include timing and code information about nearby Node B transmissions that may assist the UE or LMU in making their measurements. + +The Uu interface is also used to transport signalling between LCS entities in the CN and the UE, e.g. positioning requests from internal or external LCS Applications at the UE. This is part of the NAS procedures and it is outside the scope of this specification. + +#### 6.6.4.1 Signalling between SRNC and Target UE + +UE Positioning related signalling between an SRNC and a target UE is supported by the RRC protocol as specified in [18]. + +The positioning request to UE signalling flow is generic for all UE-based or UE-assisted positioning methods (OTDOA and Network-assisted GNSS). + +![Sequence diagram showing the OTDOA / GNSS Positioning Message Flow between an SRNC and a UE. The SRNC sends an RRC Measurement Control to the UE. The UE responds with an RRC Measurement Report. Subsequent RRC Measurement Reports are sent from the UE to the SRNC, indicated by dashed arrows and vertical ellipsis between the second and third reports.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant UE + Note left of SRNC: RRC Measurement Control + SRNC->>UE: RRC Measurement Control + Note right of UE: RRC Measurement Report + UE->>SRNC: RRC Measurement Report + Note right of UE: RRC Measurement Report + UE-->>SRNC: RRC Measurement Report + Note right of UE: ... + Note right of UE: RRC Measurement Report + UE-->>SRNC: RRC Measurement Report +``` + +Sequence diagram showing the OTDOA / GNSS Positioning Message Flow between an SRNC and a UE. The SRNC sends an RRC Measurement Control to the UE. The UE responds with an RRC Measurement Report. Subsequent RRC Measurement Reports are sent from the UE to the SRNC, indicated by dashed arrows and vertical ellipsis between the second and third reports. + +**Figure 6.1: OTDOA / GNSS Positioning Message Flow** + +1. The SRNC determines possible assistance data and sends a MEASUREMENT CONTROL request to the UE. The MEASUREMENT CONTROL message may contain a request for periodic reporting with an amount of reports greater than one. In networks that include an SAS, the assistance data is generated within the SRNC or in the SAS and passed to the SRNC over the Iupc interface. If both an SAS and an SRNC with SMLC internal functionality are available, selection is based on SRNC configuration. +2. The UE performs the requested measurements. If the UE is able to calculate its own position and optionally, velocity, and this is requested, the UE computes a position estimate, and optionally, a velocity estimate based on measurements. Assistance data necessary to perform these operations will either be provided in the MEASUREMENT CONTROL request and possibly in subsequent MEASUREMENT CONTROL messages or be available from broadcast sources. The resulting measurements or position and optional velocity estimates are returned to UTRAN in a MEASUREMENT REPORT response. If the UE cannot fulfil the request, a MEASUREMENT CONTROL FAILURE message is returned. +3. If periodic reporting was requested in step 1 with an amount of reports greater than one, the UE continues to send MEASUREMENT REPORT messages one reporting interval after the previous MEASUREMENT REPORT message until the requested amount of reports is attained, or until a request from the SRNC is received to stop the periodic reporting. + +In case the UE is not able to fulfill the measurements because the assistance data stored in the UE is not sufficient or out of date the UE returns a MEASUREMENT REPORT requesting for more additional data. + +![Sequence diagram showing OTDOA / GNSS Positioning Message Flow with additional assistance data request. The diagram shows two lifelines: SRNC and UE. The sequence of messages is: 1. UE sends an RRC Measurement Report to SRNC. 2. SRNC sends an RRC Measurement Control to UE. 3. UE sends another RRC Measurement Report to SRNC. Vertical ellipses indicate messages before and after this sequence.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant UE + Note right of UE: ... + UE->>SRNC: RRC Measurement Report + SRNC->>UE: RRC Measurement Control + UE->>SRNC: RRC Measurement Report + Note right of UE: ... + +``` + +Sequence diagram showing OTDOA / GNSS Positioning Message Flow with additional assistance data request. The diagram shows two lifelines: SRNC and UE. The sequence of messages is: 1. UE sends an RRC Measurement Report to SRNC. 2. SRNC sends an RRC Measurement Control to UE. 3. UE sends another RRC Measurement Report to SRNC. Vertical ellipses indicate messages before and after this sequence. + +**Figure 6.2: OTDOA / GNSS Positioning Message Flow with additional assistance data request** + +1. The UE cannot fulfil the request or cannot continue to send UE Positioning measurements when the reporting criteria are fulfilled, because its assistance data is not sufficient or out of date, a MEASUREMENT REPORT message is returned requesting for additional assistance data. +2. The SRNC may send more or new assistance data based on UE request. +3. The requested measurement results are returned to the SRNC. The UE continues the measurement reporting according to the stored MEASUREMENT CONTROL information (e.g., when periodic reporting was requested). + +##### 6.6.4.1.1 Assistance Data Delivery to UE + +The assistance data signalling flow illustrated here is generic for the point-to-point delivery of positioning related assistance data to the UE, including OTDOA and Network-assisted GNSS. + +![Sequence diagram showing OTDOA or GNSS Assistance Data Delivery Flow. The diagram shows two lifelines: SRNC and UE. A single message labeled 'RRC ASSISTANCE DATA DELIVERY' is sent from SRNC to UE.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant UE + SRNC->>UE: RRC ASSISTANCE DATA DELIVERY + +``` + +Sequence diagram showing OTDOA or GNSS Assistance Data Delivery Flow. The diagram shows two lifelines: SRNC and UE. A single message labeled 'RRC ASSISTANCE DATA DELIVERY' is sent from SRNC to UE. + +**Figure 6.2b: OTDOA or GNSS Assistance Data Delivery Flow** + +1. The SRNC determines assistance data and sends it in the RRC ASSISTANCE DATA DELIVERY message to the UE. In networks that include an SAS, the UE Positioning assistance data is generated within in the SAS and passed to the SRNC over the Iupc interface. + +##### 6.6.4.1.2 Error Handling + +The error handling for signalling on the Uu interface is handled by the RRC protocol in [18]. + +##### 6.6.4.1.3 Broadcast of Assistance Data + +For OTDOA and GNSS, UTRAN may broadcast assistance data to the UE. + +The assistance data to be broadcast for OTDOA contains the reference and neighbour cells to measure and for each neighbour cell the approximate cell timing and possibly IPDL information. The approximate cell timing may be used to simplify OTDOA measurements. Additionally, RTD values (e.g. in case of a non-synchronised network) and Node B co-ordinates for UE based OTDOA may be included for each neighbour cell. The length of the message depends on how many neighbours are included in the assistance data. Part of the broadcast message (e.g. the serving and neighbour Node B geographic co-ordinates) may be ciphered. + +The assistance data to be broadcast for assisted GNSS may contain a subset of or all of the following information: reference time, reference position, DGNSS corrections, ephemeris and clock corrections, and almanac and other data. The broadcast message may be ciphered. + +The broadcast channel that is used for the OTDOA and GNSS assistance data makes use of the common UTRAN broadcast service specified in [18]. + +##### 6.6.4.1.4 Signalling Flow for Assistance Data Broadcast Using the Common UTRAN Broadcast Service + +The UTRAN may broadcast positioning related assistance data to UEs within the system information. + +![Diagram showing the broadcast of system information from a CRNC to a UE. The CRNC is on the left and the UE is on the right. A horizontal arrow labeled 'SYSTEM INFORMATION' points from the CRNC to the UE. Vertical lines extend downwards from both the CRNC and the UE.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +graph LR + CRNC[CRNC] -- SYSTEM INFORMATION --> UE[UE] + CRNC --- CRNC_L[ ] + UE --- UE_L[ ] + style CRNC_L fill:none,stroke:none + style UE_L fill:none,stroke:none + +``` + +Diagram showing the broadcast of system information from a CRNC to a UE. The CRNC is on the left and the UE is on the right. A horizontal arrow labeled 'SYSTEM INFORMATION' points from the CRNC to the UE. Vertical lines extend downwards from both the CRNC and the UE. + +**Figure 6.3: Broadcast of system information** + +##### 6.6.4.1.5 UE Positioning Assistance Data Ciphering + +To allow control of access to the assistance data, parts of the broadcast assistance data may be ciphered. Ciphering is done with a specific ciphering key delivered by the CN for this purpose. The management of the key is described in the System Aspects Stage 2 ([13]). + +##### 6.6.4.1.6 UE Positioning Assistance Data Ciphering Algorithm + +The algorithm used for ciphering the UE Positioning assistance data is the standard 56-bit Data Encryption Standard (DES) algorithm. + +The deciphering of broadcast assistance messages is done in the UEs. The deciphering will utilize the deciphering keys delivered during the location update request. Details can be found in [25]. + +The RNC ciphers the parts of the UE Positioning Broadcast Data message to be protected using the 56-bit DES algorithm and a ciphering keys (56 bits) and Ciphering Serial Number (16 bits) for the broadcast location area. + +The ciphered part is variable in length with one bit resolution. By using the UE Positioning Broadcast Data message header, the UEs can determine what part of message is ciphered. + +Inputs to the 56-bit DES algorithm are the following: + +- 56-bit key K (deciphering key); +- 16-bit Ciphering Serial Number from broadcast message, which is denoted here by IV (Initialisation Vector); +- plain-text bits (the ciphered part of broadcast message). + +The ciphering process is illustrated in the following diagram. Ciphering is done by producing a mask bit stream, which is then "XORed" bit-by-bit to the plain-text data to obtain the cipher-text data. First, the Initialisation Vector (IV) is concatenated with 0-bits in order to achieve a 64-bit block $I_1$ . This block is then encrypted by the DES algorithm using the key K. Output is a 64-bit block $I_2$ . This constitutes the first 64 bits of the mask bit stream. If the message is longer than 64 bits, then more bits are needed. These are produced by encrypting $I_2$ again by the DES algorithm using the key K. The output is a 64-bit block $I_3$ . This is the next 64 bits of the mask bit stream. This iteration is continued until enough bits are produced. The unnecessary bits from the last 64-bit block $I_j$ are discarded. The figure below illustrates the first two mask bit generations and the two ciphered 64-bit blocks. + +![Figure 6.4: Data Assistance Ciphering Algorithm diagram. The diagram shows the process of ciphering broadcast message blocks. Inputs include I1 (Ciphering Serial Number (16 bits) and Fill Bits (48 bits)), K (Ciphering Key (56 bits)), and I2 (1st Mask Bit Stream (64 bits)). I1 and K are inputs to a DES block. The output of DES is XORed with I2 and the 1st 64-bit block of the broadcast message to be ciphered to produce the 1st 64-bit ciphered block. This 1st ciphered block is then input to another DES block along with I3 (2nd Mask Bit Stream (64 bits)). The output of this second DES block is XORed with I3 and the 2nd 64-bit block of the broadcast message to be ciphered to produce the 2nd 64-bit ciphered block.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 6.4: Data Assistance Ciphering Algorithm diagram. The diagram shows the process of ciphering broadcast message blocks. Inputs include I1 (Ciphering Serial Number (16 bits) and Fill Bits (48 bits)), K (Ciphering Key (56 bits)), and I2 (1st Mask Bit Stream (64 bits)). I1 and K are inputs to a DES block. The output of DES is XORed with I2 and the 1st 64-bit block of the broadcast message to be ciphered to produce the 1st 64-bit ciphered block. This 1st ciphered block is then input to another DES block along with I3 (2nd Mask Bit Stream (64 bits)). The output of this second DES block is XORed with I3 and the 2nd 64-bit block of the broadcast message to be ciphered to produce the 2nd 64-bit ciphered block. + +**Figure 6.4: Data Assistance Ciphering Algorithm** + +Deciphering is done similarly. The same mask bit stream is produced and these are XORed, bit-by-bit, to the cipher-text data bits. The result will be the plain-text data. + +#### 6.6.4.2 Signalling between RNC and stand-alone LMU + +Signalling exchanges between an RNC and a stand-alone LMU under the control of that RNC will be specified in the RRC protocol for stand-alone LMUs. This does not preclude a stand-alone LMU from also communicating with other networks (e.g. GSM) through interfaces (e.g. LLP protocol) that are not part of the present document. + +Each update of the LMU measurement (including the initial one) is triggered by a LCS request from the client that is internal to UTRAN. The request may be made directly to the UTRAN LCS entities as the internal clients are considered to be "pre-authorised" (clause 5) or comes from CN with authentication. + +The following figure illustrate the protocol layers used to support signalling between an RNC and a stand-alone LMU over the Uu interface. + +The protocol layers employed to enable signalling between the RNC and a stand-alone LMU are defined in [18]. The LMU signalling information elements are included directly in the RRC protocol, also defined in [18]. + +![Figure 6.5: Signalling between an RNC and a Stand-Alone LMU using a signalling bearer diagram. The diagram shows the protocol stack for signalling between a Stand-alone LMU and an SRNC (RNC) via a Node B over the Uu interface. The protocol layers are RRC (RRC Connection), RLC, MAC, and L1. The Stand-alone LMU and SRNC have identical protocol stacks. The RRC layer is shown as a double-headed arrow between the LMU and the Node B, indicating bidirectional signalling. The RLC, MAC, and L1 layers are shown as single-headed arrows pointing from the LMU to the Node B, indicating data flow.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +Figure 6.5: Signalling between an RNC and a Stand-Alone LMU using a signalling bearer diagram. The diagram shows the protocol stack for signalling between a Stand-alone LMU and an SRNC (RNC) via a Node B over the Uu interface. The protocol layers are RRC (RRC Connection), RLC, MAC, and L1. The Stand-alone LMU and SRNC have identical protocol stacks. The RRC layer is shown as a double-headed arrow between the LMU and the Node B, indicating bidirectional signalling. The RLC, MAC, and L1 layers are shown as single-headed arrows pointing from the LMU to the Node B, indicating data flow. + +**Figure 6.5: Signalling between an RNC and a Stand-Alone LMU using a signalling bearer** + +### 6.6.5 Iupc Interface + +UE Positioning operations on the Iupc interface are described in [27]. That specification defines in more detail the procedures needed for messages for the UE positioning method. + +The Iupc interface is used to allow communication between an RNC and an SAS. This interface is used to signal position and optionally, velocity estimate requests and responses as well as UE Positioning related information using mechanisms consistent with the other internal UTRAN interfaces. The Iupc interface is used for providing the RNC with UE Positioning data to be used for both point-to-point and broadcast purposes. The Iupc interface uses an Iups-like protocol stack for the transport layer which is described in [28]. + +#### 6.6.5.1 Signalling between RNC and SAS + +The signalling between RNC and SAS is done by using PCAP procedures specified in [27]. + +##### 6.6.5.1.1 PCAP Position Calculation + +The PCAP Position Calculation message flow illustrates how an SRNC invokes an SAS to calculate a position estimate of a UE. This message flow is repeated by the SRNC as needed for a periodic location procedure. + +The SRNC initiates the PCAP Position Calculation message flow in the RNC centric mode for UEs that support the following positioning method types: + +- UE assisted; +- UE assisted is preferred, but UE based is allowed; +- UE based is preferred, but UE assisted is allowed; + +when the chosen positioning method type is 'UE Assisted'. + +For UEs that only support the UE based positioning method or that, supporting both, have selected the 'UE Based' option, the PCAP Position Calculation message flow is not applicable. + +The SRNC also initiates the PCAP Position Calculation Request message flow to invoke the U-TDOA positioning method in the case that U-TDOA is initiated from the SRNC and not from the SAS. + +![Sequence diagram showing the PCAP Position Calculation Request Message Flow between SRNC and SAS.](db7ae70402c81d140ae7df14b002e057_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: SRNC initiates PCAP Position Calculation Request + SRNC->>SAS: PCAP Position Calculation Request + Note right of SAS: SAS calculates position and returns response + SAS-->>SRNC: PCAP Position Calculation Response +``` + +The diagram illustrates a sequence of two messages between an SRNC (Source RNC) and an SAS (Serving AS). The SRNC sends a 'PCAP Position Calculation Request' message to the SAS, indicated by a solid arrow pointing from the SRNC lifeline to the SAS lifeline. The SAS then responds with a 'PCAP Position Calculation Response' message, indicated by a solid arrow pointing from the SAS lifeline back to the SRNC lifeline. + +Sequence diagram showing the PCAP Position Calculation Request Message Flow between SRNC and SAS. + +**Figure 6.6: PCAP Position Calculation Request Message Flow** + +1. The SRNC initiates a PCAP Position Calculation Request Message. This message contains data necessary for the SAS to calculate a position, and optionally a velocity estimate for a UE and, if required, initiate U-TDOA positioning for the UE. The PCAP Position Calculation Request message may contain periodic location information (reporting interval and number of outstanding requests for the overall periodic location procedure) to enable the SAS to better fulfil future such requests. +2. If the SAS is able to calculate the position, and optional velocity estimate, possibly after performing U-TDOA positioning if requested in step 1, it shall return it to the SRNC in a PCAP Position Calculation Response + +Message. If the SAS cannot fulfil the request, it shall return a PCAP Position Calculation Failure Message to the SRNC. + +##### 6.6.5.1.2 PCAP Information Exchange + +The PCAP Information Exchange message flow illustrates how an RNC initiates and terminates an exchange of UE Positioning related information with an SAS. The UE Positioning related information received from the SAS can be used by the RNC to either provide assistance data to a particular UE through dedicated signalling or to build up System Information Blocks containing assistance data to be broadcast to UEs in a particular area. + +![Sequence diagram of PCAP Information Exchange Message Flow between RNC and SAS.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` +sequenceDiagram + participant RNC + participant SAS + Note left of RNC: RNC initiates exchange + RNC->>SAS: PCAP Information Exchange Initiation Request + Note right of SAS: SAS responds + SAS-->>RNC: PCAP Information Exchange Initiation Response + Note right of SAS: or failure + SAS-->>RNC: PCAP Information Exchange Initiation Failure + Note right of SAS: periodic/on-mod reporting + SAS-->>RNC: PCAP Information Report + Note right of SAS: failure indication + SAS-->>RNC: PCAP Information Exchange Failure Indication + Note left of RNC: RNC terminates exchange + RNC-->>SAS: PCAP Information Exchange Termination Request +``` + +The diagram illustrates the message flow between an RNC and an SAS for PCAP Information Exchange. It starts with the RNC sending a 'PCAP Information Exchange Initiation Request' to the SAS. The SAS responds with either a 'PCAP Information Exchange Initiation Response' or a 'PCAP Information Exchange Initiation Failure'. If the response is a failure, the SAS sends a 'PCAP Information Exchange Initiation Failure' message. If the response is a success, the SAS may send one or more 'PCAP Information Report' messages. Additionally, the SAS may send a 'PCAP Information Exchange Failure Indication' message. Finally, the RNC sends a 'PCAP Information Exchange Termination Request' to the SAS to terminate the exchange. + +Sequence diagram of PCAP Information Exchange Message Flow between RNC and SAS. + +**Figure 6.7: PCAP Information Exchange Message Flow** + +1. The RNC initiates a PCAP Information Exchange Initiation Request Message. This message contains data necessary for the SAS to provide the requested UE Positioning related information to the RNC. Upon reception of this message, the SAS shall provide the requested UE Positioning related information according to the reporting parameters given in the request. These parameters specify how the UE Positioning related information is to be reported (i.e. on-demand, periodically, or on-modification). +2. If the SAS is able to determine the information requested by the RNC, it shall respond with a PCAP Information Exchange Initiation Response Message. +3. If the SAS cannot provide the requested UE Positioning related information, it shall return a PCAP Information Exchange Initiation Failure Message. +4. In cases where the RNC has specified that the UE Positioning related information is to be reported periodically or on-modification, the SAS shall return the requested information in one or more PCAP Information Report Messages. +5. In cases where the RNC has specified that the UE Positioning related information is to be reported periodically or on-modification, the SAS may initiate an Information Exchange Failure Indication Message to notify the RNC that the requested information associated with a particular reporting activity can no longer be reported. +6. In cases where the RNC has specified that the UE Positioning related information is to be reported periodically or on-modification, the RNC may terminate a particular information reporting activity by initiating a PCAP Information Exchange Termination Request Message. Upon reception, the SAS shall terminate the particular information exchange activity indicated by the RNC. + +##### 6.6.5.1.3 PCAP for SAS based Positioning Method Selection + +As a configuration option, the SAS shall be able to determine the positioning method used for individual positioning events. In this case the SRNC shall allow A-GNSS, OTDOA, Cell ID, U-TDOA, WLAN, Bluetooth, Barometric Pressure and TBS positioning events to be originated by the SAS via PCAP messages on the Iupc interface. + +![Sequence diagram showing the fundamental SAS centric signal flow over the Iupc interface between RNC and SAS. The sequence starts with RNC sending a PCAP: Position Initiation Req to SAS. SAS responds with PCAP: Position Activation Req. RNC then performs an RNC Positioning Procedure. SAS sends another PCAP: Position Activation Req. RNC performs another RNC Positioning Procedure. SAS sends a PCAP: Position Activation Resp. SAS then performs an SAS Positioning Procedure. RNC sends a PCAP: Position Periodic Report. SAS responds with PCAP: Position Periodic Result. RNC sends a PCAP: Position Initiation Resp.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SAS + Note left of RNC: 1. PCAP: Position Initiation Req + RNC->>SAS: 1. PCAP: Position Initiation Req + Note right of SAS: 2. PCAP: Position Activation Req + SAS->>RNC: 2. PCAP: Position Activation Req + Note left of RNC: 3. RNC Positioning Procedure + RNC->>RNC: 3. RNC Positioning Procedure + Note right of SAS: 4. PCAP: Position Activation Resp + RNC->>SAS: 4. PCAP: Position Activation Resp + Note right of SAS: 5. SAS Positioning Procedure + SAS->>SAS: 5. SAS Positioning Procedure + Note right of SAS: 2. PCAP: Position Activation Req + SAS->>RNC: 2. PCAP: Position Activation Req + Note left of RNC: 3. RNC Positioning Procedure + RNC->>RNC: 3. RNC Positioning Procedure + Note right of SAS: 4. PCAP: Position Activation Resp + RNC->>SAS: 4. PCAP: Position Activation Resp + Note right of SAS: 5. SAS Positioning Procedure + SAS->>SAS: 5. SAS Positioning Procedure + Note left of RNC: 6. PCAP: Position Periodic Report + RNC->>SAS: 6. PCAP: Position Periodic Report + Note right of SAS: 7. PCAP: Position Periodic Result + SAS->>RNC: 7. PCAP: Position Periodic Result + Note left of RNC: 8. PCAP: Position Initiation Resp + RNC->>SAS: 8. PCAP: Position Initiation Resp + +``` + +Sequence diagram showing the fundamental SAS centric signal flow over the Iupc interface between RNC and SAS. The sequence starts with RNC sending a PCAP: Position Initiation Req to SAS. SAS responds with PCAP: Position Activation Req. RNC then performs an RNC Positioning Procedure. SAS sends another PCAP: Position Activation Req. RNC performs another RNC Positioning Procedure. SAS sends a PCAP: Position Activation Resp. SAS then performs an SAS Positioning Procedure. RNC sends a PCAP: Position Periodic Report. SAS responds with PCAP: Position Periodic Result. RNC sends a PCAP: Position Initiation Resp. + +**Figure 6.8: Fundamental SAS centric signal flow over the Iupc interface** + +1. The SRNC forwards the information contained in the RANAP Location Reporting Control message plus Cell ID and UE capability information to the SAS in a PCAP Position Initiation Request message. +2. The SAS may initiate a specific positioning method by sending a PCAP Position Activation Request message to the SRNC containing the required positioning method and any assistance data and instructions associated with that positioning method. For positioning methods which require RRC signalling (e.g., OTDOA or A-GPS), the positioning instructions include the required settings for the "measurement validity" IE in the RRC signalling message (e.g., CELL\_DCH, all states except CELL\_DCH, or all states) [18]. +3. The SRNC performs the positioning procedure requested by the SAS including any signalling interaction with the UE in the case of UE assisted or UE based positioning (e.g. for A-GNSS or OTDOA). +4. The SRNC sends a PCAP Position Activation Response message to the SAS confirming the requested action and providing any information required by the requested positioning method; e.g. UE channel information for the U-TDOA positioning method or A-GNSS measurements for UE assisted A-GNSS. If periodic UE reporting is activated by the SRNC in step 3, the PCAP Position Activation Response message includes the used settings for the IE "measurement validity" in the corresponding RRC signalling [18]. +5. The SAS instigates any further positioning associated with the positioning method chosen in step 2 – e.g. obtains measurements from LMUs in the case of U-TDOA. + +Note: + +Repeating steps 2, 3, 4 and 5 to invoke additional positioning methods may provide higher location accuracy or successfully provide UE locations under difficult propagation circumstances, e.g. the hybrid positioning method. When steps 2, 3, 4 and 5 are repeated, the SAS shall not send a new PCAP Position Activation Request message until the SRNC has responded to a previous request or the SAS has timed out on a response. The SAS may, however, send a new PCAP Position Activation Request message in a repetition of step 2 while SAS positioning for a previous step 5 is ongoing. In this case, SAS positioning (e.g. for U-TDOA) could execute in parallel with SRNC positioning (e.g. for A-GNSS or OTDOA) thereby reducing overall response time. + +6. If an RNC positioning procedure has been invoked in step 3 which requests periodic UE reporting according to subclause 6.6.4.1, the subsequent periodic UE measurement reports (e.g. for A-GPS or OTDOA) are conveyed to the SAS using one or more PCAP Position Periodic Report messages. + +NOTE: If a periodic RNC positioning procedure has been invoked by the SRNC in step 3, the PCAP Position Activation Response message in step 4 may be returned immediately (i.e., before step 3) confirming the requested action and not including any measurements. In that case, all periodic measurement reports are conveyed to the SAS using PCAP Position Periodic Report messages. + +7. If periodic positioning was invoked in step 1, the successive periodic position estimates (or an indication of positioning failure) are conveyed to the SRNC using one or more PCAP Position Periodic Result messages. +8. The SAS provides the UE location or, when periodic positioning was invoked in step 1, the final UE location to the SRNC in a PCAP Position Initiation Response message. In case of periodic positioning, the final location estimate may be provided, as an implementation option, in a PCAP Position Periodic Result message followed by a PCAP Position Initiation Response message that does not contain any UE location estimate. + +# --- 7 General UTRAN UE Positioning procedures + +## 7.1 General procedures in UTRAN for UE Positioning + +The General UE positioning procedure in UTRAN starts with a request over Iu from the CN. The request from the core network may be a request for direct (on demand) reporting or periodic reporting. UTRAN then determines the UE position by selecting a suitable positioning method. UTRAN then responds to the request with the estimated position and optionally, the estimated velocity, possibly the associated accuracies and if available, the positioning method (or the list of the methods) used to obtain the position and optional velocity estimates. If periodic reporting was requested by the CN, UTRAN responds to the request according to the received periodic reporting criteria and sends the estimated position together with other information (e.g., velocity, associated accuracies, positioning methods used, etc.) one reporting interval after the previous report until the desired amount of reports has been attained or the procedure is cancelled by the UTRAN or CN. + +## 7.2 Common procedures supporting UE Positioning interaction between RNCs + +In the case that the positioning information is needed from an associated LMU in a Node B that is not controlled by the SRNC then the transfer of this information needs to be supported on the Iur interface. This information is the same information that is signalled between an associated LMU and the corresponding CRNC in the case when Iur support is not needed. + +The SRNC requests the information it requires (e.g. GPS timing of cell measurements) from the CRNC of the Node B, which has the associated LMU. The CRNC in turn requests the information from the Node B and upon success returns the results to the SRNC. + +Similarly when the SRNC needs a Node B measurement on a UE when that Node B is not controlled by that SRNC there needs to be support on the Iur. One example is the RTT measurement. + +Other information that may need to be signalled over the Iur includes LMU parameters (geographical position, covered cells etc.). + +NOTE: Confirmation or FS is needed by R3 experts. + +### 7.2.1 Signalling in case of SRNS relocation + +In case of SRNC relocation UE Positioning functionalities may be transferred in order for DRNC to be able to handle the responsibility of SRNC in LCS process. Therefore the Source RNC may transfer the following information to the Target RNC: + +- last known position, time stamp and accuracy of the position calculation; +- LCS capabilities of the UE. + +If there is a positioning procedure going on in order to estimate the position of the UE (e.g. in case of periodic reporting) and an SRNS relocation occurs, the positioning procedure shall be stopped in the old SRNC. After SRNS relocation, it is under the responsibility of the MSC, MSC Server or SGSN to restart an Iu aborted positioning procedure. In the UE, the positioning procedure is going on and positioning information (e.g. measurement results) may be sent back to UTRAN if the UE was requested to do so. The new SRNC then decides whether it wants to use these information or discard them. If an SAS is used, the SRNC shall send an Abort message to the SAS over the Iupec interface. + +## 7.3 Exception procedures + +### 7.3.1 Procedures in the SRNC + +The SRNC can work in either the RNC centric mode or in a SAS centric mode where the SAS has control over the positioning procedures. + +#### 7.3.1.1 RNC Centric Mode + +When a positioning attempt fails due to failure of a position method itself (e.g. due to inaccurate or insufficient position measurements and related data) and the SRNC is unable to instigate another positioning attempt (e.g. due to a requirement on response time), the SRNC shall return a Location response over the Iu interface containing a less accurate position estimate if available, even if this position estimate is not within the accuracy requested from the CN. In this case, the Location response shall indicate that the position estimate does not satisfy the requested accuracy. If a less accurate estimate is not available, the SRNC shall return a Location response message containing no position estimate and indicating the cause of failure. + +When a positioning attempt is interrupted by some other unrecoverable error event inside the SRNC, the SRNC shall immediately terminate the positioning attempt and return a Location Response message containing the reason for the positioning attempt cancellation. In that case, SRNC may also abort any dialogue previously opened with an LMU for the purpose of instigating position measurements for the UE being located. + +In networks that include an SAS, the SRNC will receive a PCAP Position Calculation Response message on the Iupec interface and then return a Location response over the Iu interface containing the results that were provided over the Iupec interface (a less accurate position estimate, cause of failure indication, etc). This is described in subclause 7.3.4. + +If the uplink channel characteristics for the target UE change while a U-TDOA positioning is ongoing, the SRNC shall send a PCAP Position Parameter Modification message to the SAS containing the updated channel characteristics and cell information. + +When a positioning attempt is interrupted by some other unrecoverable error event inside the SRNC, the SRNC may also abort any dialogue previously opened with an LMU for the purpose of instigating position measurements for the UE being located. + +When periodic reporting was requested from the CN and when no location estimate is available at the SRNC when the reporting criteria are fulfilled (e.g. due to failure of a position method itself), the SRNC shall return a location response message containing no position estimate and indicating the cause of failure. + +#### 7.3.1.2 SAS Centric Mode + +When the SRNC is unable to accept a PCAP Position Activation Request message due to congestion or any other failure, the PCAP Position Activation Failure message shall be sent to the SAS on the Iupec interface. + +If an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a PCAP Position Activation Request message, and if the SRNC or UE terminates the measurement reporting (e.g. after RRC state transition), the SRNC shall send a PCAP Position Periodic Termination message to the SAS indicating the cause of termination. + +When the SRNC is unable to continue positioning activity due to cell reselection that results in a different SRNC, loss of contact with the UE or any other reason, the PCAP Abort message shall be sent to the SAS on the Iupec interface. + +A PCAP Position Parameter Modification message shall be sent containing updated channel characteristics (including cell information) whenever the RF channel parameters associated with the UE connection change due to cell reselection or handover within the same SRNC, modification of the channel capacity or any other reason within the control of a single RNC. The SRNC shall keep the SAS updated on any change in serving cell status (using PCAP Position + +Parameter Modification message) so that the SAS can provide correct assistance data to the UE whenever the SAS invokes a positioning method or methods. + +If an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a PCAP Position Activation Request message, and if there is a RRC state transition during the RRC measurement procedure, which results not in a termination of the UE measurement reporting, the SRNC shall send a PCAP Position Parameter Modification message informing the SAS about the new UE state. The SRNC shall continue to notify the SAS of such state changes until the periodic position measurement reporting has been completed by the UE, cancelled by the SAS or terminated by the SRNC. + +Sending of a PCAP Position Parameter Modification message does not change the status in the SRNC of any position method or position methods that may have been previously activated through receipt of a PCAP Position Activation Request message. + +If the SRNC receives a new PCAP Position Activation Request message before it has responded to a previous PCAP request for the same UE or while it is still performing activity for a previous non-periodic request (e.g. in the case of U-TDOA in CELL\_FACH state), the SRNC shall terminate all activity for the previous request, including sending any response to the SAS, and shall process the new request. + +If the SRNC receives a new PCAP Position Activation Request message for UE position measurement reporting using A-GPS or OTDOA or Barometric Pressure or WLAN or Bluetooth or TBS (periodic or non-periodic) while it is still performing activity for a previous A-GPS or OTDOA or Barometric Pressure or WLAN or Bluetooth or TBS periodic request, the SRNC shall terminate all activity for the previous request, including terminating the periodic measurement reporting in the UE, and shall process the new request. + +If the SRNC receives a new PCAP Position Activation Request message for cell ID-RTT or U-TDOA while it is still performing activity for a previous A-GPS or OTDOA or Barometric Pressure or WLAN or Bluetooth or TBS periodic request (but after returning any PCAP Position Activation Response for this request), the SRNC may both continue with the previous request and process the new request. + +If an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a PCAP Position Activation Request message, and if the SRNC receives a PCAP Position Periodic Termination message from the SAS, the SRNC shall terminate the periodic UE positioning measurement reporting in the UE. + +If the SRNC receives a request for assistance data from a UE positioning procedure (periodic or non-periodic) that uses A-GNSS, the SRNC should indicate this to the SAS by sending a Position Activation Response message. The Position Activation Response message shall include the assistance data types requested by the UE. In case of periodic UE positioning reporting and after a Position Activation Response message has already been returned to the SAS, the request for additional assistance data may be conveyed in a Position Periodic Report message. + +### 7.3.2 Procedures in a LMU + +An LMU shall return an error indication to its CRNC when positioning measurements previously ordered by the RNC cannot be provided due to any error condition. + +### 7.3.3 Procedures in the target UE + +A target UE shall terminate any positioning procedure or the transfer of RRC positioning assistance data without sending any response to the SRNC if any UE Positioning RRC message is received from the SRNC that starts some other RRC management procedure. The new RRC procedure shall then be executed by the UE. + +### 7.3.4 Procedures in the SAS + +The SAS can work in either the RNC centric mode or in a SAS centric mode where the SAS has control over the positioning procedures. + +#### 7.3.4.1 RNC Centric Mode + +In the RNC centric mode, when a UE positioning attempt fails (e.g. due to inaccurate or insufficient position measurements and related data), the SAS may return a PCAP Position Calculation Response message over the Iupec interface containing a less accurate position estimate. If a less accurate estimate is not available or will not meet the + +accuracy requirement, the SAS may instead return a PCAP Position Calculation Failure message containing no position estimate and indicating the cause of failure. + +When a positioning attempt is interrupted by some other unrecoverable error event inside the SAS, the SAS shall immediately terminate the positioning attempt and return a PCAP Position Calculation Failure message containing the reason for the positioning attempt cancellation. + +#### 7.3.4.2 SAS Centric Mode + +If the SAS invokes a positioning method by sending a PCAP Position Activation Request message to the SRNC, it may subsequently receive a PCAP Position Activation Failure or PCAP Abort message from the SRNC, while positioning in the SRNC is active, according to subclause 7.3.1.2. At any time after receiving a PCAP Position Initiation Request message and whether positioning in the SRNC is active or not active, the SAS may receive a PCAP Abort message or PCAP Position Parameter Modification message from the SRNC, according to subclause 7.3.1.2. + +If the SAS receives a PCAP Abort message it shall immediately cease positioning attempts and return a PCAP Position Initiation Response message to the SRNC carrying any location estimate already obtained or a Position Initiation Failure message containing a cause of failure indication. If the SAS receives a PCAP Position Activation Failure message, the SAS may either terminate positioning as for receipt of a PCAP Abort or continue the positioning attempt using the same or other positioning methods, e.g. if permitted by the QoS response time requirement. If the SAS receives a PCAP Position Parameter Modification message, the SAS shall take the received information into account in either performing ongoing positioning (e.g. reconfigure LMUs for U-TDOA) or invoking new positioning (e.g. use new serving cell to provide A-GPS timing assistance). + +If the SAS is unable to accept or continue processing a PCAP Position Initiation Request from the SRNC due to capacity constraints or equipment failure, a PCAP Position Initiation Failure message shall be sent to the SRNC on the Iupc interface carrying an appropriate cause of the failure indication. + +## 7.4 Radio interface timing procedures + +The Radio Interface Timing determination system consists of functions in LMUs in the SRNC, and in the SAS for networks that include an SAS. The system runs continuously offering cell timing information for UE Positioning. + +### 7.4.1 LMU Functions + +The Radio Interface Timing functionality in the CRNC associated LMU should be capable of performing the following functions: + +- The LMU performs necessary radio interface measurements from signals transmitted by Node Bs; +- If the LMU contains a common reference clock, e.g. GPS TOW, it time stamps reception of Node B signals by performing measurements of UTRAN GPS timing of cell frames; +- If there is no reference clock available, the LMU may make SFN-SFN Observed Time Difference or measurements, i.e. measures the time difference between arrival of SFNs from neighbouring Node Bs and a reference Node B; +- The LMU may perform some processing of measurements, like averaging and filtering, using parameters delivered to it, or in their absence using default settings. + +### 7.4.2 CRNC Functions + +The CRNC must be capable of performing the following functions related to Radio Interface Timing determination: + +- The CRNC sends to LMUs requests for Radio Interface Timing measurement information; +- The CRNC will communicate regularly with LMUs; thus, the CRNC can monitor operation of LMUs. If a LMU fails to send Radio Interface Timing information, the CRNC shall try to restart the LMU, and if this restarting fails, the CRNC shall inform O&M system. CRNC can use also diagnostics messages to query the status of LMUs; +- The CRNC receives Radio Interface Timing measurement results from LMUs; + +- The CRNC stores or queries extra information required for Node B synchronization determination, like Node B and LMU coordinates, Node B identity information; +- The CRNC determines synchronization differences between different downlink signals using LMU measurements and other information; +- Synchronization information is delivered for UE Positioning purposes. + +### 7.4.3 LMU-CRNC Interactions + +The request for Radio Interface Timing measurement information from the CRNC to a LMU contains the following parameters: + +- Measurement type. This indicates whether the CRNC wants the LMU to perform UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference; +- Measurement result reporting frequency. This indicates how often the LMU should send Radio Interface Timing measurement results; +- Measurement duration. This indicates how long the LMU should make measurements and report results; +- Instructions about filtering of raw measurement data; +- Instructions about Primary CPICH signals to be measured. The LMU unit can measure autonomously a certain number of most strongly received signals. Another possibility is that the CRNC tells which Node B signals it should measure; +- In the SFN-SFN Observed Time Difference case, which common Primary CPICH the LMU should use as a reference in the measurements; +- Instruction of how the measurement quality should be reported. + +In case a SFN-SFN Observed Time Difference measurement was requested by the CRNC, the LMU returns the following information to CRNC: + +- Identity of the Node B at which the associated LMU is residing; +- Primary CPICH info of the measured signals; +- SFN-SFN observed time difference between neighbour cells and reference cell; +- Identity of the neighbour cells; +- SFN-SFN drift between neighbour cells and reference cell; +- Time stamp of the measurement (e.g. SFN); +- Accuracy of the measurement. + +In case a UTRAN GPS timing of cell frames measurement was requested by the CRNC, the LMU returns the following information to the CRNC: + +- Cell id of the measured cell; +- SFN; +- Time stamp (e.g. GPS TOW) of the SFN; +- Node B clock drift; +- Accuracy of the measurement. + +# 8 Cell ID and Enhanced Cell ID based positioning methods + +The Cell ID and Enhanced Cell ID based positioning method can work in either the RNC centric mode or in an SAS centric mode where the SAS has control over the positioning procedures. + +This subclause outlines the procedures for Cell ID and Enhanced Cell ID positioning methods. Subclause 8.1 provides procedures for the determination of the cell ID depending on the operational status of the target UE. Subclause 8.2 provides a procedure for the mapping of the cell ID to a corresponding SAI to be returned to the LCS application in the CN. Subclause 8.3 provides additional information on other Enhanced Cell ID methods. + +In the RNC centric Cell ID based method, the SRNC determines the identification of the cell providing coverage for the target UE and may request additional UE and/or UTRAN measurements for Enhanced Cell ID methods. The general flow to determine the cell ID and UE and/or UTRAN measurements for Enhanced Cell ID methods is shown in figure 8.1. For Enhanced Cell ID methods, the SRNC may request measurements either from the Node B(s) (e.g., RTT, Rx Timing Deviation, Angle of Arrival) or from the target UE using RRC measurement procedure (e.g., pathloss, CPICH RSCP, CPICH Ec/No). The available measurements for Enhanced Cell ID are described in Section 8.3. If the location request from the CN is a request for periodic reporting, the general procedure may be repeated and UTRAN sends an LCS response one reporting interval after the previous LCS response message until the desired amount of reports is attained, or until the procedure is cancelled by UTRAN or CN. + +![Sequence diagram illustrating RNC Centric, Cell ID and Enhanced Cell ID Based Methods. The diagram shows interactions between UE, Node B, and SRNC. It starts with a 'Request to locate UE' from an external source to the SRNC. A yellow box indicates a state where no cell ID is available (e.g., URA_PCH or idle mode), involving a 'Forced state transition (e.g. by paging)' and a 'State transition'. The SRNC then sends an 'RRC Measurement Control' to the UE, which responds with an 'RRC Measurement Report'. The SRNC sends a 'Node B Measurements Request' to the Node B, which responds with a 'Node B Measurement Response'. Finally, the SRNC performs 'Mapping the cell ID to the cell coverage or service area' and sends an 'LCS Response' to the external source.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +``` + +sequenceDiagram + participant External + participant SRNC + participant NodeB as Node B + participant UE + + Note right of SRNC: UE is in a state where no cell ID is available (for example URA_PCH) or in idle mode + External->>SRNC: Request to locate UE + Note right of SRNC: Forced state transition (e.g. by paging) + Note right of SRNC: State transition + SRNC->>UE: RRC Measurement Control + UE->>SRNC: RRC Measurement Report + SRNC->>NodeB: Node B Measurements Request + NodeB->>SRNC: Node B Measurement Response + Note right of SRNC: Mapping the cell ID to the cell coverage or service area + SRNC->>External: LCS Response + +``` + +Sequence diagram illustrating RNC Centric, Cell ID and Enhanced Cell ID Based Methods. The diagram shows interactions between UE, Node B, and SRNC. It starts with a 'Request to locate UE' from an external source to the SRNC. A yellow box indicates a state where no cell ID is available (e.g., URA\_PCH or idle mode), involving a 'Forced state transition (e.g. by paging)' and a 'State transition'. The SRNC then sends an 'RRC Measurement Control' to the UE, which responds with an 'RRC Measurement Report'. The SRNC sends a 'Node B Measurements Request' to the Node B, which responds with a 'Node B Measurement Response'. Finally, the SRNC performs 'Mapping the cell ID to the cell coverage or service area' and sends an 'LCS Response' to the external source. + +**Figure 8.1: RNC Centric, Cell ID and Enhanced Cell ID Based Methods** + +In the SAS centric mode the request for a Cell ID or Enhanced Cell ID based position may be originated by an associated SAS via a PCAP Position Activation Request message on the Iupc interface as discussed in subclause 6.6.5.1.3. In this case the Cell ID and other measurements for Enhanced Cell ID would be provided to the SAS in a PCAP Position Activation Response message as shown in figure 8.2. + +For periodic reporting, the SAS may continue to invoke Cell ID or Enhanced Cell ID based position via PCAP Position Activation Request messages and the SAS sends the periodic location reports to the SRNC in PCAP Position Periodic Result messages until the desired amount of reports is attained (or until the procedure is cancelled by UTRAN or CN) + +as shown in Figure 8.2. The final location estimate may be provided to the SRNC either in a PCAP Position Periodic Result or in a PCAP Position Initiation Response message, as described in subclause 6.6.5.1.3. + +![Sequence diagram for SAS Centric, Cell ID and Enhanced Cell ID Based Methods. Lifelines: UE, Node B, SAS, SRNC. The diagram shows two main interaction flows. In the first flow, SRNC sends a 'Request to locate UE' to SAS, which responds with 'PCAP Position Initiation Req' and 'PCAP Position Activation Req'. A yellow box indicates a state where no Cell ID is available (e.g., URA_PCH or idle mode), requiring a 'Forced state transition (e.g. by paging)' from SAS to UE. UE then sends 'RRC Measurement Control' to Node B, which responds with 'RRC Measurement Report'. SAS sends 'NodeB Measurement Request' to Node B, which responds with 'NodeB Measurement Response'. SAS then sends 'PCAP Pos Activation Resp' to SRNC. A box indicates 'Mapping the Cell ID to the cell coverage or service area'. In the second flow, SAS sends 'PCAP Position Periodic Result' to SRNC, which responds with 'LCS Response'. SAS also sends 'PCAP Position Activation Req' to SRNC. Another yellow box indicates the same state transition scenario. UE sends 'RRC Measurement Control' to Node B, which responds with 'RRC Measurement Report'. SAS sends 'NodeB Measurement Request' to Node B, which responds with 'NodeB Measurement Response'. SAS then sends 'PCAP Pos Activation Resp' to SRNC. A box indicates 'Mapping the Cell ID to the cell coverage or service area'. SAS sends 'PCAP Position Periodic Result' to SRNC, which responds with 'LCS Response'. A bracket on the left labeled 'Periodic Reporting' encompasses the second flow. At the bottom, a box labeled 'Periodic Location Event N' is shown. Finally, SAS sends 'PCAP Position Initiation Resp' to SRNC, which responds with 'LCS Response'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NodeB as Node B + participant SAS + participant SRNC + + SRNC->>SAS: Request to locate UE + SAS->>SRNC: PCAP Position Initiation Req + SAS->>SRNC: PCAP Position Activation Req + + Note over UE, SRNC: UE is in a state where no Cell ID is available (e.g. URA_PCH or idle mode) + SAS->>UE: Forced state transition (e.g. by paging) + UE->>SRNC: State transition + + SRNC->>UE: RRC Measurement Control + UE->>SRNC: RRC Measurement Report + SAS->>NodeB: NodeB Measurement Request + NodeB->>SAS: NodeB Measurement Response + SAS->>SRNC: PCAP Pos Activation Resp + + Note over SAS: Mapping the Cell ID to the cell coverage or service area + + rect rgb(240, 240, 240) + Note left of UE: Periodic Reporting + SAS-->>SRNC: PCAP Position Periodic Result + SRNC-->>SAS: LCS Response + SAS-->>SRNC: PCAP Position Activation Req + + Note over UE, SRNC: UE is in a state where no Cell ID is available (e.g. URA_PCH or idle mode) + SAS->>UE: Forced state transition (e.g. by paging) + UE->>SRNC: State transition + + SRNC->>UE: RRC Measurement Control + UE->>SRNC: RRC Measurement Report + SAS->>NodeB: NodeB Measurement Request + NodeB->>SAS: NodeB Measurement Response + SAS->>SRNC: PCAP Pos Activation Resp + + Note over SAS: Mapping the Cell ID to the cell coverage or service area + + SAS-->>SRNC: PCAP Position Periodic Result + SRNC-->>SAS: LCS Response + Note over UE, SRNC: Periodic Location Event N + end + + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>SAS: LCS Response + +``` + +Sequence diagram for SAS Centric, Cell ID and Enhanced Cell ID Based Methods. Lifelines: UE, Node B, SAS, SRNC. The diagram shows two main interaction flows. In the first flow, SRNC sends a 'Request to locate UE' to SAS, which responds with 'PCAP Position Initiation Req' and 'PCAP Position Activation Req'. A yellow box indicates a state where no Cell ID is available (e.g., URA\_PCH or idle mode), requiring a 'Forced state transition (e.g. by paging)' from SAS to UE. UE then sends 'RRC Measurement Control' to Node B, which responds with 'RRC Measurement Report'. SAS sends 'NodeB Measurement Request' to Node B, which responds with 'NodeB Measurement Response'. SAS then sends 'PCAP Pos Activation Resp' to SRNC. A box indicates 'Mapping the Cell ID to the cell coverage or service area'. In the second flow, SAS sends 'PCAP Position Periodic Result' to SRNC, which responds with 'LCS Response'. SAS also sends 'PCAP Position Activation Req' to SRNC. Another yellow box indicates the same state transition scenario. UE sends 'RRC Measurement Control' to Node B, which responds with 'RRC Measurement Report'. SAS sends 'NodeB Measurement Request' to Node B, which responds with 'NodeB Measurement Response'. SAS then sends 'PCAP Pos Activation Resp' to SRNC. A box indicates 'Mapping the Cell ID to the cell coverage or service area'. SAS sends 'PCAP Position Periodic Result' to SRNC, which responds with 'LCS Response'. A bracket on the left labeled 'Periodic Reporting' encompasses the second flow. At the bottom, a box labeled 'Periodic Location Event N' is shown. Finally, SAS sends 'PCAP Position Initiation Resp' to SRNC, which responds with 'LCS Response'. + +**Figure 8.2: SAS Centric, Cell ID and Enhanced Cell ID Based Methods** + +## 8.1 Cell ID determination + +In order for the SRNC to determine the cell ID when an UE Positioning request is received, additional operations may be needed depending on the operational status of the UE. + +When the LCS request is received from the CN the SRNC checks the state of the target UE. If the UE is in a state where the cell ID is available, the target cell ID is chosen as the basis for the UE Positioning. In states where the cell ID is not available, the UE is paged, so that SRNC can establish the cell with which the target UE is associated. The SRNC may also map the cell ID to a corresponding SAI to match the service coverage information available in the CN. + +The cell ID based method shall determine the position of the UE regardless of the UE RRC mode (i.e. connected or idle). + +### 8.1.1 UE Cell ID is not known + +For UE for which the cell ID is not known at the time the UE Positioning request is received at the SRNC, the UE may be paged to locate its current cell ID. If the UE is in an idle mode and there is a need for it to be paged, then the paging shall be initiated by the CN. If the UE is in URA\_PCH state the paging may be initiated by the SRNC in UTRAN. For example, the UE can be forced to perform a transition to a Cell\_FACH state to define the cell ID of its current cell. + +If the UE is in an idle mode, or in a RRC connected state when there is a need to page for the UE to obtain the cell ID, the CN may initiate paging, authentication and ciphering, as specified in [13]. + +Alternatively, the cell ID may be determined as the one that was used during the last active connection to the UE. In the case the UE is not reachable, the last known position should include the age of location field. + +### 8.1.2 UE Cell ID is known + +#### 8.1.2.1 UE not in Soft handover + +The cell ID may be determined as the cell that is providing an active connection for the UE at the time of receiving the UE Positioning request at the SRNC. + +#### 8.1.2.2 UE in Soft handover + +In order for the SRNC to provide the geographical co-ordinates of a target UE in soft handover, the SRNC combines the information about all cells associated with the UE. + +In soft handover, the UE may have several signal branches connected to different cells, reporting different cell IDs. A reference cell ID may be determined by the SRNC based on the coverage area of each cell. The reference cell ID may be selected based on one or more of the following principles: + +- the cell ID may be selected based on the parameters defining the quality of the received signal branches. That is, the cell ID with the best quality signal branch is selected as the reference cell ID; +- the cell ID may be selected that was used during connection set-up between the UE and the serving Node B; +- the cell ID of the cell most recently associated with the UE may be selected; +- the cell ID of the latest "new" cell that the UE has started to receive, but has not yet been handed over to may be selected; +- the cell ID may be selected as the cell to which UE has the shortest distance (to the Node B site); +- the cell ID may be selected as the cell that provides an active connection for the UE at the time of receiving the UE Positioning request at the SRNC. + +The selection may also be based on RTT measurements, power levels and received signal strengths in UE and related Node B or LMU. + +Other relevant mechanisms such as IPDL or SSDT power control should also be taken into account when applying the cell ID selection procedure for UE in a soft handover mode. + +## 8.2 Mapping the Cell ID to Geographic Co-ordinates or a Service Area + +A UTRAN cell ID should be mapped to geographical coordinates or a SAI before being sent from UTRAN to the CN. The Service Area Identifier may include one or several cells. The mapping may be accomplished either in the SRNC, in a Network Management System, including Network Management Unit or by co-operation of various access network elements. + +The CN may request the geographical co-ordinates or the SAI, or both for the target UE. The SAI may be used for routing of corresponding Emergency calls, or for CAMEL services to correspond to the usage of Cell ID in the core network of GSM. However, the MSC shall not send the Service Area Identity to GMLC. + +Although the mapping of the cell(s) associated with the target UE into geographical co-ordinates by the SRNC is not standardised, the response to the CN Location request with geographical co-ordinates shall be as defined in [11]. + +In order to determine a cell coverage estimate and to map it to the geographical coordinates or Service Area parameter Identity, the SRNC may use parameters such as the best reference signal, RTT in FDD [15] or Rx Timing Deviation [16] and knowledge of the UE timing advance in TDD, as well as antenna beam direction parameters. + +Alternatively, the service area coverage of a cell may be determined by using a reference signal power budget. Based on the reference signal power budget it is possible to obtain, for example, the Node B transmitted power, isotropic path loss, coverage threshold at coverage area border for a given location probability, and a cell radius for an indoor and outdoor coverage. + +The SRNC may use a reference signal link budget based cell radius estimate, in conjunction with the cell identifier, to make a coverage estimation for the cell(s) related to the target UE. + +Additionally, the SRNC may compare the received power levels with the power budget, whereby more accurate information of the position of the UE may be provided. + +Also, the interaction between neighbouring cell coverage areas may be used to determine a more exact UE Positioning. + +## 8.3 Enhanced Cell ID Methods + +Techniques which use additional UE and/or UTRAN radio resource related measurements are defined under Enhanced Cell ID. Measurements for these ECID methods may include: + +UE measurements: + +- UE Rx-Tx Time Difference (FDD); +- pathloss; +- CPICH RSCP (FDD); +- CPICH Ec/No (FDD); +- Timing Advance (TDD). + +UTRAN measurements: + +- RTT (FDD); +- Rx Timing Deviation (TDD); +- Angle of Arrival (1.28 Mcps TDD). + +Various techniques exist to use these measurements to estimate the location of the target UE. The specific techniques are beyond the scope of this specification. Examples of other Enhanced Cell ID method include the following: + +### 8.3.1 Cell-ID with RTT + +Cell-ID with Round Trip Time measurements: + +This variant uses in addition NodeB measurements of the signal Round-Trip-Time (RTT). These measurements can be + +made for all NodeBs in the active set. If RTT measurements to several geographically dispersed NodeBs are available, the UE location may be found via trilateration. The RTT measurements may be complemented by the UE measurement of the Rx-Tx Time Difference Type 1 and/or Type 2. In case of TDD mode, the distance measurement may be based on RX Timing Deviation and/or Timing Advance. + +### 8.3.2 Cell-ID with Pathloss and Related Measurements + +Cell-ID and Pathloss related measurements: + +This variant uses in addition several UE measurements for the serving and neighboring cells related to pathloss or SNR. UE measurements which could be used include: + +- Pathloss (as defined in [18] subclause 10.3.7.3); +- CPICH RSCP (FDD); +- CPICH Ec/N0 (FDD). + +These measurements may be used to obtain distance related information, or the measurements may be used for statistical modeling approaches, etc. + +#### 8.3.2.1 RF Pattern Matching (RFPM) + +The RF Pattern Matching positioning method is based on radio link measurements collected from the network and/or the UE. The method relies on predictions or models of the radio environment against which it performs an algorithmic comparison of the measurements to determine a best match estimation of the UE's location. RFPM may utilize measurements other than the pathloss measurements noted above. + +### 8.3.3 Cell-ID with Angle of Arrival + +Cell-ID with Angle-Of-Arrival (AOA) measurements (1.28 Mcps TDD only): + +This variant uses NodeB angle-of-arrival measurements, usually together with distance related measurements obtained via timing advance to estimate the UE location. + +# --- 9 OTDOA positioning method + +The primary standard OTDOA measurement is the "SFN-SFN observed time difference" observed at the UE (see [15] and [16]). These measurements, together with other information concerning the surveyed geographic position of the transmitters and the RTD of the actual transmissions of the downlink signals may be used to calculate an estimate of the position and optionally, the velocity of the UE. Each OTDOA measurement for a pair of downlink transmissions describes a line of constant difference (a hyperbola (see note 1)) along which the UE may be located. The UE's position is determined by the intersection of these lines for at least two pairs of Node Bs. The accuracy of the position estimates made with this technique depends on the precision of the timing measurements, the relative position of the Node Bs involved (see note 2), and is also subject to the effects of multipath radio propagation. This is illustrated in the figure 9.1. + +NOTE 1: This is really a figure in three dimensions, a hyperboloid. For convenience here, this will be simplified to the hyperbola representing the intersection of this surface with the surface of the earth. For location service in three dimensions the hyperboloid must be considered. + +NOTE 2: The geometry of the Node B positions may affect the accuracy of the position and optional velocity estimates. The best results are when the Node Bs equally surround the UE. If they do not, there is a reduction in accuracy, which is sometimes termed the Geometric Dilution of Position (GDP). + +The primary OTDOA measurements (made by the UE) are sent to the SRNC. These measures are sent via signaling over the Uu, Iub (and Iur) interfaces between the UE and the SRNC. In networks with a SAS, the SRNC may forward the measurement results over the Iupc interface to the SAS. The calculation function makes use of the measurements, the known positions of the transmitter sites and the RTD of the transmissions to estimate the UE's position. + +![Diagram illustrating the OTDOA Positioning Method. A User Equipment (UE) is shown at the center. A blue circle labeled 'RTT Circle' is centered on Node B -(c). Two hyperbolic curves, labeled 'OTDOA Hyperboloid', are shown, one centered on Node B -(a) and another on Node B -(b). The intersection of the RTT Circle and the OTDOA Hyperboloids defines the 'Estimated UE Position Region'. Red lightning bolts represent signals from the Node Bs to the UE.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Diagram illustrating the OTDOA Positioning Method. A User Equipment (UE) is shown at the center. A blue circle labeled 'RTT Circle' is centered on Node B -(c). Two hyperbolic curves, labeled 'OTDOA Hyperboloid', are shown, one centered on Node B -(a) and another on Node B -(b). The intersection of the RTT Circle and the OTDOA Hyperboloids defines the 'Estimated UE Position Region'. Red lightning bolts represent signals from the Node Bs to the UE. + +**Figure 9.1: OTDOA Positioning Method** + +The OTDOA method may be operated in two modes: UE-assisted OTDOA and UE-based OTDOA. The two modes differ in where the actual position calculation is carried out. + +In the *UE-assisted* mode, the UE measures the difference in time of arrival of several cells and signals the measurement results to the network, where the SRNC or the SAS carries out the position calculation. + +In the *UE-based* mode, the UE makes the measurements and also carries out the position calculation, and thus requires additional information (such as the position of the measured Node Bs) that is required for the position calculation. + +The signalling requirements for the two OTDOA modes are described in subclause 9.6. As the UE Positioning involves measurements, there is always uncertainty in the results. Physical conditions, errors and resolution limits in the apparatus all contribute to uncertainty. To minimise the uncertainty in the UE Positioning result, it is important that as many measurements of OTDOA (and assistance data as RTT in FDD and Rx Timing Deviation in TDD) as are possible for a UE are provided to the UE. Thus it is important that the standard UE Positioning method not be restricted to rely on a single measure. The UE thus provides SFN-SFN observed time difference measurements for as many cells as it can receive. The cells to be measured shall include those in the active set and the monitored set. + +In order to support the OTDOA method, the positions of the UTRAN transmitters needs to be accurately known by the calculation function in SRNC or SAS (for UE-assisted method) or UE (for UE-based method). This information may be measured by appropriate conventional surveying techniques (see note 3). The surveyed position should be the electrical centre of the transmitting antenna (and not the position of the radio equipment building). The use of antenna diversity, beamforming or beam steering techniques may cause the effective antenna position to change with time and this information is also needed to perform calculations. The methods of measuring the position of the UTRAN transmitters are outside the scope of the present document. + +NOTE 3: These surveying methods may, for example, make use of a GPS receiver. + +In order to support the OTDOA method, the RTD of the DL transmissions must also be known to perform the calculation. If the UTRAN transmitters are unsynchronised, the RTD will change over time as the individual clocks drift. Thus, RTD estimations may need to be made regularly and the calculation function updated appropriately. + +One convenient method is to make use of an LMU at a fixed position. This unit performs timing measurements (e.g. UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference) of all the local transmitters. The CRNC then may convert these measures into the actual (absolute) relative time difference for each of the transmitters by making use of the known position of the LMU and the transmitters. + +In some conditions a sufficient number of cells may not be available for measure at the UE. This may occur, for example, if the UE is located quite close to the UTRAN transmitter and its receiver is blocked by the strong local transmissions. This is referred to as the "hearability" problem. + +## 9.1 Use of Idle Periods + +Location based services needs the support of physical layer as a prerequisite, so that the measurements required for the UE position, and optional velocity calculation can be carried out. In UTRAN there are several factors that must be taken into account while considering the physical layer procedures related to location services: + +- hearability: a basic consequence of a CDMA radio system is that a terminal near its serving Node B cannot hear other Node Bs on the same frequency. In order to calculate its position the UE should be able to receive at least three Node Bs. To facilitate this some special means are required; +- asynchronous network causes significant uncertainty to the time-difference-of-arrival (TDOA) measurements. To compensate for the effects of this, the relative time difference (the synchronicity) between Node B transmissions must be measured, and used for correcting OTDOA measurement; +- capacity loss: signalling related to position calculation may take capacity from other services. This capacity loss should be minimised. + +Based on the results in [29] a solution for the above mentioned hearability problem is the IPDL method. In this method each Node B ceases its transmission for short periods of time (idle periods). Therefore the Node B is configured appropriately by the CRNC using the NBAP protocol [22]. During an idle period of a Node B, terminals within the cell can measure other Node Bs and the hearability problem is reduced. The UEs are made aware of the occurrences of IPDLs by using RRC signalling over the Uu interface [18]. Also, during idle periods the real time difference measurements can be carried out. Because the IPDL method is based on downlink the location service can be provided efficiently to a large number of terminals simultaneously. + +The specification and operation of the IPDL technique are provided in [14] and [26]. + +## 9.2 Relative Time Difference (RTD) + +In order to calculate the estimate of the position of the UE, the calculation function needs to know: + +- the OTDOA measurements; +- the surveyed geographic positions of the Node Bs that have had their signals measured; and +- the actual relative time difference between the transmissions of the Node Bs at the time the OTDOA measurements were made. + +The accuracy of each of these measurements contributes to the overall accuracy of the position estimate. The measurement of the RTD is described in the following. + +There are several approaches to determining the RTD. One is to synchronise the transmissions of Node B. In this technique the RTD are known constant values (see NOTE) that may be entered in the database and used by the calculation function when making a position estimate. The synchronisation must be done to a level of accuracy of the order of tens of nanoseconds (as 10 nanoseconds uncertainty contributes 3 metres error in the position estimate). Drift and jitter in the synchronisation timing must also be well controlled as these also contribute uncertainty in the position estimate. Synchronisation to this level of accuracy is currently only readily available through satellite based time-transfer techniques. Generally in the TDD operating mode, the Node Bs are synchronised. + +NOTE: The transmission times may all be aligned to a common reference (such as UTC) in which case all RTD have a common value. However, in a more general case the transmissions may have a fixed offset with reference to UTC, and thus the RTD values are non-zero and may be stored in the database for use by the calculation function. + +Alternatively (typically in FDD mode), Node Bs may be left to free run within some constraint of maximum frequency error. In this scenario, the RTD will change (slowly) with time. The rate of change will depend on the frequency difference and jitter between Node Bs. If, for example, the maximum frequency difference between two Node Bs is $\pm 10^{-9}$ , then the start of transmission of a 10 millisecond code sequence will drift through a cycle in about 1 390 hours (or 57 days). With this relatively slow rate of drift the measurements needed to obtain the RTD can be performed by fixed LMUs at known positions and stored in the database for use by the calculation function. The jitter and drift of the individual oscillators in each Node B may cause the change of timing to slow, remain constant or reverse direction over time. Ongoing measurements may be made to assure the most current values are available for the calculation function. The measurement units needed to support RTD estimation may be co-located with the Node Bs or installed at other convenient positions in the UTRAN coverage area, and report their results through the UTRAN signalling. + +The LMUs may directly measure the SFN-SFN Observed Time Difference between neighbouring and reference cells and return the measurements to the CRNC. Alternatively the LMUs may measure the UTRAN GPS timing of cell frames of the neighbouring and reference cells and return the measurements to the CRNC. If the CRNC is not the SRNC the information is also forwarded from CRNC to SRNC. In networks with a SAS the information may also be forwarded to the SAS. + +The SRNC or SAS then uses the UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference measurements to calculate the RTD values. The information to be transferred in each case is listed in 7.4.3. + +## 9.3 Time of Day (ToD) + +If there are frequency drifts between the (unsynchronised) Node Bs, as noted in subclause 9.2, the OTDOA measurements must be reported together with the time-of-day they were made (timestamp). This is necessary so that the appropriate value of the RTD may be used by the calculation function. + +In order to assure less than a 20 nanosecond uncertainty in the RTD value, the time of day must be known to better than 10 seconds (if the maximum frequency difference between the Node Bs is $\pm 10^{-9}$ ). The method by which the ToD is measured is the system the frame number, which provides a 10 millisecond resolution and can be unambiguous up to 40.95 seconds. + +## 9.4 Node B Synchronisation + +It is preferable that the positioning methods do not require the Node B to be synchronised. The needed level of synchronisation accuracy for UE Positioning is not by any means straightforward to achieve. The necessary information to obtain RTD between Node Bs can be measured by LMU (e.g. UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference) and distributed in the network (e.g. as broadcast information). Also, these measurements may benefit from the IPDL option. + +In the TDD operating mode the Node Bs will typically be synchronised and this may be of assistance to the UE Positioning technique. + +## 9.5 OTDOA-IPDL and OTDOA Modes + +There are two modes of operation for the OTDOA-IPDL and OTDOA methods. + +In the *UE-assisted* mode, the UE measures the difference in time of arrival of several cells and signals the measurement results to the network, where the SRNC or SAS carries out the position calculation. + +In the *UE-based* mode, the UE makes the measurements and also carries out the position calculation, and thus requires additional information (such as the position of the measured Node Bs) that is required for the position calculation. This information is provided by the System Information Broadcast. + +### 9.5.1 Information to be transferred between UTRAN elements + +Table 9.1 lists the required information for both UE-assisted and UE-based modes that may be sent from UTRAN to UE. The required information can be signalled to the UE either in a broadcast channel or partly also as dedicated signalling. + +**Table 9.1: Information to be transferred from UTRAN to UE ('Yes' = information required, 'No' = Information not required)** + +| Information | UE-assisted | UE-based | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------| +| Intra frequency Cell Info (neighbour list) | Yes | Yes | +| Ciphering information for UE Positioning (see note 1) | No | Yes | +| Measurement control information (idle period locations) | Yes | Yes | +| Sectorisation of the neighbouring cells | No | Yes | +| Measurements results needed for RTD values for Cells mentioned at Intra frequency Cell Info | No | Yes | +| RTD accuracy | No | Yes | +| Measured roundtrip delay for primary serving cell | No | Yes | +| Geographical position of the primary serving cell | No | Yes | +| Relative neighbour cell geographical position | No | Yes | +| Accuracy range of the geographic position values | No | Yes | +| IPDL parameters | Yes | Yes | +| IPDL-Alpha parameter for Open Loop Power Control when using IPDLs in TDD (see note 2) | Yes | Yes | +| Maximum Power increase the UE may use when using IPDLs in TDD (see note 2) | Yes | Yes | +| NOTE 1: The idea behind UE Positioning specific ciphering information is e.g. that the operator can sell information that the UE needs for calculating its position. For reference in the GSM world see [4]. | | | +| NOTE 2: These parameters are not required for 1.28 Mcps TDD in this release. | | | + +When IPDLs for 3.84/7.68 Mcps TDD are applied and the IPDLs occur in the slot carrying the PCCPCH, a special alpha parameter needs to be signalled from SRNC to the UE in order to take the impact of the IPDLs on the Open Loop Power Control into account. Additionally the UE shall not increase the transmit power by a certain value between an IPDL slot and the next slot carrying the PCCPCH when IPDLs are applied within a cell. OTDOA for 1.28 Mcps TDD is based on DwPTS and so these requirements do not apply. + +The information that may be signalled from UE to SRNC is listed in table 9.2. + +**Table 9.2: Information to be transferred from UE to SRNC** + +| Information | UE-assisted | UE-based | +|---------------------------------------------------------------------------------|-------------|----------| +| OTDOA measurement results | Yes | No | +| OTDOA measurement accuracy | Yes | No | +| UE geographical position | No | Yes | +| Position accuracy indicator (based on the signalled and measurement accuracies) | No | Yes | + +Table 9.3 shows the information that may be transferred from Node B to its CRNC. If the CRNC is not the SRNC the information is also forwarded from CRNC to SRNC. + +**Table 9.3: Information to be transferred from Node B/LMU to CRNC and between RNCs** + +| Information | UE assisted | UE based | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------|----------| +| Measured UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference values for Cells mentioned at Intra frequency Cell Info | Yes | Yes | +| UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference accuracy | Yes | Yes | + +Table 9.4 shows the information that may be transferred from CRNC to Node B. If the CRNC is not the SRNC the information may also be sent from CRNC to SRNC. + +**Table 9.4: Information to be transferred from CRNC to Node B/LMU and between RNCs** + +| Information | UE assisted | UE based | +|-----------------|-------------|----------| +| IPDL parameters | Yes | Yes | + +Table 9.5 shows the information that may be transferred between RNCs. + +**Table 9.5: Information to be transferred between RNCs** + +| Information | UE assisted | UE based | +|-----------------------------------------------------------------------------------------|-------------|----------| +| Geographical position of the primary serving cell | Yes | Yes | +| Relative neighbour cell geographical position | Yes | Yes | +| Accuracy range of the geographic position values | Yes | Yes | +| IPDL-Alpha parameter for Open Loop Power Control when using IPDLs in 3.84/7.68 Mcps TDD | Yes | Yes | +| Maximum Power the UE may use when using IPDLs in 3.84/7.68 Mcps TDD | Yes | Yes | + +## 9.6 OTDOA network positioning procedures + +OTDOA may be selected by the SRNC as the method to be used on receipt of an LCS positioning request from the CN or, optionally, when the SRNC receives a PCAP Position Activation Request message indicating the OTDOA positioning method from a SAS that is configured to select the positioning method. In the SAS initiated case the OTDOA measurement information will be returned to the SAS in a PCAP Position Activation Response message, or – if periodic reporting was requested – in one or more PCAP Position Periodic Report messages as discussed below. + +### 9.6.1 RNC based selection of OTDOA + +The following diagram illustrates the operations for the OTDOA method for UE Positioning when the request for positioning information is initiated by an LCS application from the CN. + +This illustration only includes the information flow related to UE Positioning operations and does not indicate other operations that may be required, for example, to establish a signalling connection between the UE and the SRNC. Also not illustrated is the signalling used to initiate the location service request from the CN or a UE-based application. + +![Sequence diagram illustrating OTDOA Signalling Operations between CN, SRNC, Node B, and UE. The diagram shows two instances of the procedure. In the first instance, the CN sends a 'Location request' to the SRNC. The SRNC sends an 'OTDOA measurements request' and a 'UE Rx-Tx timing request' to the UE. The UE responds with 'OTDOA measurements report' and 'UE Rx-Tx timing measurements report' to the SRNC. The SRNC then sends an 'RTT measurements request' to the Node B, which responds with an 'RTT measurements report'. Finally, the SRNC sends a 'Location estimate' to the CN. A dashed box encloses the second instance, which repeats the steps from the SRNC to the UE and back, ending with the SRNC sending a 'Location estimate' to the CN. Vertical ellipsis marks follow the second instance.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SRNC + participant NodeB as Node B + participant UE + + Note left of CN: First Instance + CN->>SRNC: Location request + SRNC->>UE: OTDOA measurements request + SRNC-->>UE: UE Rx-Tx timing request + UE-->>SRNC: OTDOA measurements report + UE-->>SRNC: UE Rx-Tx timing measurements report + SRNC-->>NodeB: RTT measurements request + NodeB-->>SRNC: RTT measurements report + SRNC->>CN: Location estimate + + Note left of CN: Second Instance (enclosed in dashed box) + SRNC-->>UE: OTDOA measurements request + SRNC-->>UE: UE Rx-Tx timing request + UE-->>SRNC: OTDOA measurements report + UE-->>SRNC: UE Rx-Tx timing measurements report + SRNC-->>NodeB: RTT measurements request + NodeB-->>SRNC: RTT measurements report + SRNC->>CN: Location estimate + + Note center: ... + +``` + +Sequence diagram illustrating OTDOA Signalling Operations between CN, SRNC, Node B, and UE. The diagram shows two instances of the procedure. In the first instance, the CN sends a 'Location request' to the SRNC. The SRNC sends an 'OTDOA measurements request' and a 'UE Rx-Tx timing request' to the UE. The UE responds with 'OTDOA measurements report' and 'UE Rx-Tx timing measurements report' to the SRNC. The SRNC then sends an 'RTT measurements request' to the Node B, which responds with an 'RTT measurements report'. Finally, the SRNC sends a 'Location estimate' to the CN. A dashed box encloses the second instance, which repeats the steps from the SRNC to the UE and back, ending with the SRNC sending a 'Location estimate' to the CN. Vertical ellipsis marks follow the second instance. + +**Figure 9.2: OTDOA Signalling Operations** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the CN being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC considers the request and the UTRAN and UE capabilities. +2. The SRNC requests from the UE the measurement of the OTDOA for the signals in the active and neighbourhood sets. These measurements are made while the UE is in connected mode CELL\_DCH state. If the location request from the CN in step 1 contained periodic reporting information (reporting interval and amount of reports), the SRNC may at this step request periodic OTDOA measurement reporting from the UE according to subclause 6.6.4.1. +3. If it is considered advantageous to do so, the SRNC requests the UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information from the UE. If the location request from the CN in step 1 contained periodic reporting information (reporting interval and amount of reports), the SRNC may at this step request periodic measurement reporting from the UE according to subclause 6.6.4.1. +4. The UE returns the OTDOA measures to the SRNC. The SRNC receives the OTDOA information and co-ordinates obtaining other information to support the calculation request. +5. The UE returns the UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information to the SRNC, together with a time stamp of when the value was obtained. +6. If there are insufficient OTDOA measures, or it is otherwise considered advantageous to do so, the SRNC requests the RTT (in FDD) or Rx timing deviation (in TDD) and/or angle of arrival (in 1.28 Mcps TDD) measure for the UE from the serving Node B. + +7. In FDD, the SRNC requests the RTD values for the associated transmitters from the associated database. These may be stored locally if they are constant over time, otherwise they must be updated to represent the RTD timing at the time-of-day the OTDOA measurements were made. +8. The Node B returns the RTT (in FDD) or Rx Timing Deviation (in TDD) and/or angle of arrival (in 1.28 Mcps TDD) measures to the SRNC if they were requested. +9. The SRNC performs a position, and optional velocity calculation using the OTDOA, RTD and, if necessary, RTT (in FDD) or Rx timing deviation and UE timing advance (in TDD) information and angle of arrival information (1.28 Mcps TDD). The calculation may include a co-ordinate transformation to the geographic system requested by the application. The position estimate includes the position and the estimated accuracy of the results. The optional velocity estimate may also include an estimated accuracy. In networks that include the SAS, the SAS may perform the position calculation and then pass the position estimate to the SRNC. +10. The SRNC passes the position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position and optional velocity estimate. If the CN has requested an accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +11. If periodic reporting was requested from the CN in step 1, and steps 2 or 3 requested periodic UE reporting according to subclause 6.6.4.1, steps 4 to 10 are repeated. If periodic reporting was requested from the CN in step 1, but the SRNC does not request periodic UE reporting at steps 2 or 3, the SRNC repeats steps 2 to 10. The SRNC sends a location estimate to the CN one reporting interval after the previous location estimate until the desired amount of reports has been attained (or until the procedure is cancelled by UTRAN or CN). + +### 9.6.2 SAS based selection of OTDOA + +The following describes the signalling for the optional selection of the OTDOA positioning procedure by the SAS when the CN has requested UE positioning. + +![Sequence diagram illustrating OTDOA Signalling Operations for SAS based positioning method selection. The diagram shows interactions between CN, SAS, SRNC, Node B, and UE. It includes messages like Location Request, PCAP Position Initiation Req, OTDOA Measurement Request, and periodic reporting sequences.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant Node B + participant UE + + CN->>SRNC: Location Request + SRNC->>SAS: PCAP Position Initiation Req + SAS->>SRNC: PCAP Position Activation Req + SRNC->>UE: OTDOA Measurement Request + UE-->>SRNC: UE Rx-Tx Timing Request + UE->>SRNC: OTDOA Measurement Report + SRNC-->>SAS: UE Rx-Tx Timing Measurement Report + SRNC->>SAS: PCAP Position Activation Resp + SAS->>SRNC: PCAP Position Activation Req + SRNC-->>Node B: RTT Measurement Req + Node B-->>SRNC: RTT Measurement Report + SRNC-->>SAS: PCAP Position Activation Resp + SRNC-->>SAS: PCAP Position Periodic Result + SAS-->>CN: Location Estimate + + rect rgb(240, 240, 240) + Note over CN, UE: Periodic Reporting + UE-->>SRNC: OTDOA Measurement Report + UE-->>SRNC: UE Rx-Tx Timing Measurement Report + SRNC-->>SAS: PCAP Position Periodic Report + SAS-->>SRNC: PCAP Position Activation Req + SRNC-->>Node B: RTT Measurement Req + Node B-->>SRNC: RTT Measurement Report + SRNC-->>SAS: PCAP Position Activation Resp + SRNC-->>SAS: PCAP Position Periodic Result + SAS-->>CN: Location Estimate + Note over SAS, SRNC: Location Reporting Event N + end + + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>CN: Location Estimate + +``` + +Sequence diagram illustrating OTDOA Signalling Operations for SAS based positioning method selection. The diagram shows interactions between CN, SAS, SRNC, Node B, and UE. It includes messages like Location Request, PCAP Position Initiation Req, OTDOA Measurement Request, and periodic reporting sequences. + +**Figure 9.3: OTDOA Signalling Operations for SAS based positioning method selection** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the CN being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC considers the request and the UTRAN and UE capabilities. +2. The SRNC forwards the information contained in the RANAP Location Reporting Control message, including any periodic reporting information, plus the Cell ID and UE capability information to the SAS in a PCAP Position Initiation Request message. +3. The SAS sends a PCAP Position Activation Request message to the SRNC that requests the OTDOA positioning method and may also request the UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information from the UE. The PCAP Position Activation Request message may include periodic reporting information (amount of reports and reporting interval). +4. The SRNC requests from the UE the measurement of the OTDOA for the signals in the active and neighbourhood sets. The OTDOA measurement request may include a request for periodic reporting as described in subclause 6.6.4.1. These measurements are made while the UE is in connected mode CELL\_DCH state. +5. If the SAS has requested Rx-Tx timing information, the SRNC requests the UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information from the UE. The measurement request may include a request for periodic reporting as described in subclause 6.6.4.1. + +6. The UE returns the OTDOA measures to the SRNC. The SRNC receives the OTDOA information and co-ordinates obtaining other information to support the calculation request. +7. The UE returns the UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information to the SRNC, together with a time stamp of when the value was obtained. +8. The SRNC forward the OTDOA measurement report information and, if available, the UE Rx-Tx timing measurement report information to the SAS in a PCAP Position Activation Response message. +9. If there are insufficient OTDOA measures, or it is otherwise considered advantageous to do so, the SAS requests the RTT (in FDD) or Rx timing deviation (in TDD) and/or angle of arrival (in 1.28 Mcps TDD) measure for the UE from the serving Node B by sending a PCAP Position Activation Request message that requires the SRNC to execute the Cell ID positioning method toward the UE being positioned. +10. In FDD, the RTD values for the associated transmitters are calculated and stored in the SAS based upon input from its associated LMUs. +11. The Node B returns the RTT (in FDD) or Rx Timing Deviation (in TDD) and/or angle of arrival (in 1.28 Mcps TDD) measures to the SRNC if they were requested. +12. The SRNC forwards Cell ID and RTT (in FDD) or Rx timing deviation and UE timing advance (in TDD) information and angle of arrival information (1.28 Mcps TDD) to the SAS in a PCAP: Position Activation Response message. +13. The SAS performs the OTDOA based or Cell ID based position calculation. If periodic reporting was not requested in step 1, the SAS forwards the position information to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 1, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The calculation may include a co-ordinate transformation to the geographic system requested by the application. The position estimate includes the position and the estimated accuracy of the results. The optional velocity estimate may also include an estimated accuracy. +14. The SRNC passes the position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position and optional velocity estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +15. If periodic UE reporting was requested in step 4 or 5, the UE continues to send OTDOA measurements or UE Rx-Tx timing difference (FDD only) or UE timing advance, $T_{ADV}$ , (1.28 Mcps TDD) information to the SRNC, together with a time stamp of when the value was obtained, one reporting interval after the previous measurement report. The SRNC forwards the OTDOA measurement report information and, if available, the UE Rx-Tx timing measurement report information to the SAS in a PCAP Position Periodic Report message. The SRNC may aggregate the OTDOA measurement report information and the UE Rx-Tx timing measurement report information, if both are received from the UE in separate RRC messages, into the same PCAP Position Periodic Report message or may send this information in two separate PCAP Position Periodic Report messages. Steps 9 to 12 may be repeated for each new position estimate, and the SAS performs OTDOA based or Cell ID based position calculation and forwards each new position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position and optional velocity estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 15 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. +16. If periodic UE reporting was not requested in step 4 or 5, but was requested in step 2, the SAS may repeat the steps 3 to 14 as for the first request until the desired amount of reports has been attained or the procedure is canceled by the CN or UTRAN. When repeating step 13 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +# --- 10 Network-assisted GPS positioning method + +When GPS is designed to inter-work with the UTRAN, the network assists the UE GPS receiver to improve the performance in several respects. These performance improvements will: + +- reduce the UE GPS start-up and acquisition times; the search window can be limited and the measurements speed up significantly; +- increase the UE GPS sensitivity; positioning assistance messages are obtained via UTRAN so the UE GPS can operate also in low SNR situations when it is unable to demodulate UE GPS signals; +- allow the UE to consume less handset power than with stand-alone GPS; this is due to rapid start-up times as the GPS can be in idle mode when it is not needed. + +The Network-assisted GPS methods rely on signalling between UE GPS receivers (possibly with reduced complexity) and a continuously operating GPS reference receiver network, which has clear sky visibility of the same GPS constellation as the assisted UEs. GPS reference receivers may be connected to the UTRAN to enable derivation of UE assistance signals. + +Figures 10.1 and 10.2 provide an example of the end-to-end call flows for UE-assisted and UE-based positioning respectively. The SAS is an optional network element and the call segments do not apply in a network where the UE Positioning resides within the SRNC. + +![Sequence diagram for Network-assisted GPS methods – UE-Assisted](552328a9daaf3bc0069424b500025880_img.jpg) + +``` +sequenceDiagram + participant SAS + participant SRNC + participant UE + + Note left of SAS: UP request or assistance data request + SAS->>SRNC: + Note right of SRNC: SRNC collects available network info about UE +SAS or SRNC computes GPS assistance + SRNC->>SAS: SRNC invokes SAS + SAS-->>SRNC: + SRNC->>UE: A-GPS assistance information is conveyed to the UE + Note right of UE: UE makes GPS measurements with the help of GPS assistance data + UE->>SRNC: GPS measurement results are conveyed to the SAS or SRNC (UE-assisted) + Note left of SRNC: SAS or SRNC calculates location fix + SRNC-->>SAS: + Note left of SAS: SAS provides UE location info to SRNC + SAS->>SRNC: + Note left of SRNC: UE location info + SRNC->>SAS: +``` + +The diagram illustrates the sequence of interactions for UE-assisted GPS positioning. It involves three main entities: SAS (Serving Area Server), SRNC (Radio Network Controller), and UE (User Equipment). The process begins with a 'UP request or assistance data request' from an external source to the SAS. The SAS sends a message to the SRNC. The SRNC then performs internal steps: 'SRNC collects available network info about UE' and 'SAS or SRNC computes GPS assistance'. Next, the SRNC sends an 'SRNC invokes SAS' message to the SAS. The SAS responds with a dashed return arrow. The SRNC then sends 'A-GPS assistance information is conveyed to the UE' to the UE. The UE performs 'UE makes GPS measurements with the help of GPS assistance data' and sends 'GPS measurement results are conveyed to the SAS or SRNC (UE-assisted)' back to the SRNC. The SRNC then performs 'SAS or SRNC calculates location fix' and sends a dashed return arrow to the SAS. The SAS performs 'SAS provides UE location info to SRNC' and sends a message to the SRNC. Finally, the SRNC performs 'UE location info' and sends a message back to the SAS. + +Sequence diagram for Network-assisted GPS methods – UE-Assisted + +Figure 10.1: Network-assisted GPS methods – UE-Assisted + +![Sequence diagram illustrating Network-assisted GPS methods – UE-Based. The diagram shows three lifelines: SAS, SRNC, and UE. The process starts with a 'UP request or assistance data request' from the UE to the SRNC. The SRNC then performs internal steps: 'SRNC collects available network info about UE' and 'SAS or SRNC computes GPS assistance'. Next, the SRNC invokes the SAS ('SRNC invokes SAS'). The SAS responds with 'A-GPS assistance information is conveyed to the UE' to the SRNC, which then passes it to the UE. The UE then 'calculates location fix' and sends 'UE location info (UE-based)' back to the SRNC. Finally, the SRNC sends 'UE location info' to the SAS.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + participant SAS + Note right of SRNC: SRNC collects available network info about UE +SAS or SRNC computes GPS assistance + UE->>SRNC: UP request or assistance data request + SRNC->>SAS: SRNC invokes SAS + SAS-->>SRNC: A-GPS assistance information is conveyed to the UE + SRNC->>UE: A-GPS assistance information is conveyed to the UE + Note right of UE: UE calculates location fix + UE->>SRNC: UE location info (UE-based) + SRNC->>SAS: UE location info + +``` + +Sequence diagram illustrating Network-assisted GPS methods – UE-Based. The diagram shows three lifelines: SAS, SRNC, and UE. The process starts with a 'UP request or assistance data request' from the UE to the SRNC. The SRNC then performs internal steps: 'SRNC collects available network info about UE' and 'SAS or SRNC computes GPS assistance'. Next, the SRNC invokes the SAS ('SRNC invokes SAS'). The SAS responds with 'A-GPS assistance information is conveyed to the UE' to the SRNC, which then passes it to the UE. The UE then 'calculates location fix' and sends 'UE location info (UE-based)' back to the SRNC. Finally, the SRNC sends 'UE location info' to the SAS. + +**Figure 10.2: Network-assisted GPS methods – UE-Based** + +## 10.1 Timing calibration + +Timing calibration is achieved by using UE or UTRAN GPS timing measurements as specified in [15]. + +## 10.2 Timing assistance + +The UTRAN may derive the estimated UE position using UTRAN parameters (e.g. Cell-ID or IPDL) and may use this information, in conjunction with satellite specific ephemeris data received from the GPS reference receiver network, to derive the estimated times of arrival (code phases) for equivalent GPS satellite signals received by the UE-based GPS receiver functionality. For the UE-assisted method, the estimated code phase data may be conveyed, together with $T_{UTRAN-GPS}$ (as specified in [15] and [16]), from the UTRAN to the UE using higher layer signalling. The estimated code phase data value is uncertain to a degree depending on the accuracy of the UTRAN timing calibration and initial position determination methods used. + +Alternatively, for the UE-based method, the UE itself may derive its location aided by assistance messages. The ephemeris data are transmitted from UTRAN to the UE using higher layer signalling. The UE may use this information, in conjunction with the UE's reference location, to derive the times of arrival (code phases) for GPS satellite signals received by the UE-based GPS receiver functionality. + +## 10.3 GPS assistance data + +The UE may receive GPS information through the UTRAN radio interface, using higher layer signalling. Once a UE Positioning measurement is setup by the SRNC the UE is responsible to maintain valid and up to date GPS assistance data in order to report the requested measurement results. In case that the UE has not sufficient assistance data or the data is out of date then the UE should indicate it to the SRNC and additionally request for assistance data. + +When the UE is unable to detect a sufficient number of satellites, the assisted GPS method can be combined with other positioning methods. Altitude assistance can compensate for one satellite measurement. + +The assistance data signalled to the UE may include all information listed below or a selected subset: + +- data assisting the measurements; e.g. reference time, visible satellite list, satellite signal Doppler, code phase, Doppler and code phase search windows. This data can be valid for a few minutes (e.g., less than 5 minutes) or longer depending on the code phase and Doppler search window size that can be accommodated by the UE; +- data providing means for position calculation; e.g. reference time, reference position, satellite ephemeris, clock corrections. Satellite ephemeris and clock corrections data can be used for up to six hours. + +NOTE: Certain types of GPS Assistance data may be derived, wholly or partially, from other types of GPS Assistance data. + +If DGPS is utilised, then differential corrections may also be transmitted. If Selective Availability is turned off, these corrections can be valid for a few minutes or more. The DGPS data is valid for a large geographical area, so one centrally located reference receiver can be used to service this large region. + +## 10.4 UE search + +Provided that timing assistance, data assistance, and/or frequency reference is available in the UE, they should be applied in the GPS signal search procedure. The UE search procedure involves a three-dimensional search for a satellite pseudorandom code, time of arrival of a signal and the associated carrier Doppler. + +"Modulation wipe-off" is defined here to mean a removal of the GPS navigation data bit modulation to GPS signals received at the UE, through the application of UTRAN timing and data assistance provided from the UTRAN to the UE. This process allows the UE to coherently integrate received GPS signals beyond 1 data bit period (i.e., 20 milliseconds). + +## 10.5 Position determination + +There are two types of network-assisted GPS methods, namely UE-based and UE-assisted, which differ according to where the actual position and optional velocity calculation is carried out. + +Computation of the position and optional velocity fix can either be performed in UTRAN (i.e. SRNC or SAS) for UE-assisted or in the UE for UE-based. + +The UE-based method maintains a full GPS receiver functionality in the UE, and the position and optional velocity calculation is carried out by the UE, thus allowing stand-alone position and optionally, velocity fixes. + +In the UE-assisted method, the UE employs a reduced complexity GPS receiver functionality. This carries out the pseudorange (code phase) measurements. These are signalled, using higher layer signalling, to the specific network element that estimates the position of the UE and carries out the remaining GPS operations. In this method, accurately timed code phase signalling (as specified in [15] and [16]) is required on the downlink. If DGPS is performed in the UE, then differential corrections must be signalled to it. On the other hand, DGPS corrections can be applied to the final result in the network to improve the position accuracy without extra signalling to the UE. + +### 10.5.1 Information to be transferred between UTRAN elements + +Table 10.1 lists information for both UE-assisted and UE-based modes that may be sent from the network to UE. This information can be signalled to the UE either in a broadcast channel or as dedicated signalling. + +**Table 10.1: Information that may be transferred from the network to UE('Yes' = information applicable 'No' = information not applicable** + +| Information | UE-assisted | UE-based | +|-----------------------------------------------------------------------------------|-------------|----------| +| Number of satellites for which assistance is provided | Yes | Yes | +| reference time for GPS (T UTRAN-GPS ) (specified in [15] and [16]) | Yes | Yes | +| 3-d reference position (specified in [11]) | No | Yes | +| ionospheric corrections | No | Yes | +| satellite ID for identifying the satellites for which assistance data is provided | Yes | Yes | +| Ephemeris & clock corrections | Yes | Yes | +| UTC offset | No | Yes | +| DGPS corrections | No | Yes | +| almanac data | Yes | Yes | +| real-time integrity (e.g. a list of unusable satellites) | No | Yes | +| doppler (0 th order term) | Yes | No | +| Doppler Search Window width | Yes | No | +| doppler (1 st order term) | Yes | No | +| azimuth | Yes | No | +| elevation | Yes | No | +| code phase | Yes | No | +| code phase centre and search window width | Yes | No | + +The information that may be signalled from UE to the network is listed in table 10.2. + +**Table 10.2: Information that may be transferred from UE to the network** + +| Information | UE-assisted | UE-based | +|------------------------------------------------------------------------------------|-------------|----------| +| reference time for GPS (T UE-GPS ) (specified in [15] and [16]) | Yes | Yes | +| serving cell information | No | Yes | +| Latitude/Longitude/Altitude/Error ellipse | No | Yes | +| velocity estimate in the UE | No | Yes | +| satellite ID for which measurement data is valid | Yes | No | +| Whole/Fractional chips for information about the code-phase measurement | Yes | No | +| C/No of the received signal from the particular satellite used in the measurements | Yes | No | +| doppler frequency measured by the UE for the particular satellite | Yes | No | +| pseudorange RMS error | Yes | No | +| multipath indicator | Yes | No | +| number of Pseudoranges | Yes | No | + +Table 10.3 shows the information that may be transferred from Node B to its CRNC. If the CRNC is not the SRNC the information is also forwarded from CRNC to SRNC. + +**Table 10.3: Information that may be transferred from Node B/LMU to CRNC and between RNCs** + +| Information | UE-assisted | UE-based | +|-------------------------------------------------------------------------------|-------------|----------| +| reference time for GPS (T UTRAN-GPS ) (specified in [15] and [16]) | Yes | Yes | + +#### 10.5.1.1 Almanac data + +The almanac parameters specify the coarse, long-term model of the satellite positions and clocks. These parameters are a subset of the ephemeris and clock correction parameters in the Navigation Model, although with reduced resolution and accuracy. The almanac model is useful for receiver tasks that require coarse accuracy, such as determining satellite visibility. The model is valid for up to one year, typically. Since it is a long-term model, the field should be provided for all satellites in the GPS constellation. + +Optionally, "SV Global Health" information may accompany this almanac information. This additional information is composed of the sequence of all non-parity data bits contained in words 3-10 of page 25 of subframe 4 of the GPS navigation message followed by the sequence of all non-parity bits contained in words 3-10 of page 25 of subframe 5 of the GPS navigation message. The following GPS navigation message fields are excluded when constructing these sequences: "Data ID", "SV (Page) ID", and "t". + +#### 10.5.1.2 DGPS corrections + +In order to allow a UE to estimate its position more accurate, biases in the pseudorange measurements may be provided to the UE. + +##### **Status/Health** + +This information indicates the status of the differential corrections contained in the message. + +##### **IODE** + +This is the sequence number for the ephemeris for the particular satellite. The UE can use this information to determine if new ephemeris is used for calculating the corrections that are provided in the broadcast message. This eight-bit IE is incremented for each new set of ephemeris for the satellite and may occupy the numerical range of [0, 239] during normal operations. More information about this field can be found from [24]. + +##### **User Differential Range Error (UDRE)** + +The UDRE provides an estimate of the uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the common Corrections Status/Health field to determine the final UDRE estimate for the particular satellite. More information about this field can be found from [24]. + +##### **Pseudo-Range Correction (PRC)** + +The PRC indicates the correction to the pseudorange for the particular satellite at the GPS Reference Time, $t_0$ . The PRC definition here is different from the one given in [24]. + +##### **Pseudo-Range Rate Correction (PRRC)** + +This information indicates the rate-of-change of the pseudorange correction for the particular satellite, using the satellite ephemeris identified by the IODE IE. + +#### 10.5.1.3 Ionospheric corrections + +The Ionospheric Model contains information needed to model the propagation delays of the GPS signals through the ionosphere. Proper use of these information allows a single-frequency GPS receiver to remove approximately 50% of the ionospheric delay from the range measurements. The Ionospheric Model is valid for the entire constellation and changes slowly relative to the Navigation Model. + +#### 10.5.1.4 Ephemeris data and clock correction + +Ephemeris data and clock corrections provide an accurate model of the satellite positions to the UE. + +#### 10.5.1.5 Real Time integrity monitor function + +An Integrity Monitor (IM) function in the network should detect unhealthy (i.e., failed/failing) satellites. Excessively large pseudo range errors, as evidenced by the magnitude of the corresponding DGPS correction determined by the IM, may be used to detect unhealthy satellites. Unhealthy satellites should be detected very close to the occurrence of the satellite failure (e.g. 10 seconds) and marked in an unhealthy satellite list as unusable/bad. When unhealthy satellites are detected, the assistance and/or DGPS correction data should not be supplied for these satellites. Upon receiving the list of unhealthy satellites from the SRNC, the UE shall consider the data associated with these satellites to be invalid. + +The IM function should also inform the UE of measurement quality in DGPS modes when satellites are healthy. This can be done by computing the position of the DGPS reference receiver using its derived pseudo ranges and differential corrections at the IM, and differencing the IM computed position with the known location of the DGPS reference receiver to compute a position error. When the error in the IM computed position is excessive for solutions based upon healthy satellites only, DGPS users should be informed of measurement quality through the supplied User Differential + +Range Error (UDRE) adjusted values based on the operation of the IM. The UE should use the measurement quality as a factor in weighing data obtained from associated satellites in its position calculation. + +NOTE: UDRE is one of the IEs contained in the DGPS information ([19]). + +The real-time Integrity Monitor function provides the following information to a UE: + +- BadSATid; +- UDRE value adjusted based on the measurement quality. + +BadSATid is a list of unhealthy (i.e., failed/failing) satellites. The UE shall consider any assistance or DGPS data of these satellites as invalid. + +Adjusted UDRE value reports the measurement quality of the corresponding satellites. The UE should consider the quality while calculating its position. + +#### 10.5.1.6 GPS reference time + +GPS reference time may be used to provide a mapping between UTRAN and GPS time. + +##### GPS TOW Assist + +This information contains several fields in the Telemetry (TLM) Word and Handover Word (HOW) that are currently being broadcast by the respective GPS satellites. Combining this information with GPS TOW helps the UE with time-recovery needed to predict satellite signal. + +##### TLM Message + +This information contains a 14-bit value representing the Telemetry Message (TLM) being broadcast by the GPS satellite identified by the particular SatID, with the MSB occurring first in the satellite transmission. + +##### Anti-Spoof/Alert + +These information contain the Anti-Spoof and Alert flags that are being broadcast by the GPS satellite identified by SatID. + +##### TLM Reserved + +These information contain the two reserved bits in the TLM Word being broadcast by the GPS satellite identified by SatID, with the MSB occurring first in the satellite transmission. + +#### 10.5.1.7 UTC + +UTC parameters may be used to provide Coordinated Universal Time to the UE. + +#### 10.5.1.8 Reference Location + +The Reference Location contains a 3-D location (with uncertainty) specified as per [11]. The purpose of this field is to provide the UE with a priori knowledge of its position in order to improve GPS receiver performance. + +#### 10.5.1.9 Additional non-GPS related information + +Additional non-GPS measurements performed by UTRAN or UE may be used by the SRNC to improve the performance of the UE-assisted GPS method. This information may be RTT in FDD or Rx Timing Deviation in TDD, UE receiving transmitting time (UE Rx-Tx), SFN-SFN observed time difference or CPICH Ec/No. All the additional measurements are defined in [15] and [16] and can be made available through RRC signalling for UE measurements or NBAP signalling for UTRAN measurements. + +Furthermore, to those UE technologies requiring externally provided sensitivity and time aiding data, some navigation bits may be sent from UTRAN to UE for sensitivity assistance and time recovery. + +## 10.6 RNC based Network Assisted GPS positioning Procedure + +The diagram in Figure 10.3 and Figure 10.2 illustrate the operations for the network assisted GPS when the request for position information is initiated by a LCS application signalled from the Core Network. A detailed description of the + +positioning procedure is given as follows. Note that the procedure is for illustration purpose and actual implementations may vary. + +![Sequence diagram illustrating RNC based Network-assisted GPS methods. The diagram shows three main entities: CN (Core Network), SRNC (Serving Radio Network Controller), and UE (User Equipment). The sequence of messages is as follows: 1. CN sends a 'Location request' to SRNC. 2. SRNC sends a 'GPS measurements request (GPS assistance data)' to UE. 3. UE sends a 'GPS measurements report or GPS position report' back to SRNC. 4. SRNC sends a 'Location estimate' back to CN. A dashed box encloses the interaction between SRNC and UE, indicating a sub-process. Inside this box, the messages are repeated with dashed lines: SRNC sends 'GPS measurements request (GPS assistance data)' to UE, and UE sends 'GPS measurements report or GPS position report' back to SRNC. Below the dashed box, there are three vertical dots, indicating further steps in the process.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +Sequence diagram illustrating RNC based Network-assisted GPS methods. The diagram shows three main entities: CN (Core Network), SRNC (Serving Radio Network Controller), and UE (User Equipment). The sequence of messages is as follows: 1. CN sends a 'Location request' to SRNC. 2. SRNC sends a 'GPS measurements request (GPS assistance data)' to UE. 3. UE sends a 'GPS measurements report or GPS position report' back to SRNC. 4. SRNC sends a 'Location estimate' back to CN. A dashed box encloses the interaction between SRNC and UE, indicating a sub-process. Inside this box, the messages are repeated with dashed lines: SRNC sends 'GPS measurements request (GPS assistance data)' to UE, and UE sends 'GPS measurements report or GPS position report' back to SRNC. Below the dashed box, there are three vertical dots, indicating further steps in the process. + +**Figure 10.3: RNC based Network-assisted GPS methods** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. The SRNC considers the request and the capabilities of the UE and the UTRAN. In networks that include the SAS, the SRNC may invoke the SAS via the Iupc interface. +2. Depending on the UE capabilities, the network sends to the UE certain GPS assistance information. This information may include: the reference time for GPS, the satellite IDs, the Doppler frequency, the search window and its centre, the ephemeris and clock corrections, the almanac, and other information specified in 10.5.1. Depending on the UE capabilities, the network sends a request for GPS positioning to the UE. If the location request from the CN in step 1 contained periodic reporting information (reporting interval and amount of reports), the SRNC may at this step request periodic measurement reporting from the UE according to subclause 6.6.4.1. If the UE has not enough assistance data to perform the measurements, the UE should indicate it to the SRNC and additionally request for assistance data. + +For UE-based method, jump to step 8. + +3. For UE-assisted method, the SRNC may optionally request the following information before the assistance message(s) is (are) sent to the UE: the LMU update (see NOTE), the RTT measurements (from the Node Bs in the active set) to compensate for the one-way propagation delays. The LMU (associated or stand-alone) returns the information containing the time difference between the Node B and the GPS (e.g. UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference) to the CRNC. The Node B returns its RTT measurement to the CRNC. If the CRNC is not the SRNC, the CRNC forwards these information to SRNC. +4. The network requests from the UE the measurement of GPS satellite pseudoranges and other information specified in 10.5.1. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. The SRNC may request SFN-SFN Observed Time Difference measurements and Rx-Tx timing difference information from the UE to support the processing related to the RTT measurements. +5. The UE returns to the network the measurement of GPS satellite pseudoranges and other information specified in 10.5.1. If requested, the UE returns to the SRNC SFN-SFN measurements and the Rx-Tx time difference information, together with a time stamp of when these values were obtained. +6. The UE position and optional velocity is calculated in the network. +7. If there is insufficient information to yield a UE positioning estimate, the SRNC may start a new process from step 3. +8. In case of UE based method, UE returns the position and optional velocity estimate to the SRNC. This estimate includes the position and optionally, velocity, the estimated accuracy of the results and the time of the estimate. +9. In networks that include the SAS, the SAS passes the position estimate to the SRNC. + +10. The SRNC passes the position and optional velocity estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested an accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +11. If periodic reporting was requested from the CN in step 1, and the SRNC requested periodic UE reporting in step 2 according to subclause 6.6.4.1, steps 5 to 10 are repeated and the UE reports new measurements one reporting interval after the previous measurement report. If periodic reporting was requested from the CN in step 1, but the SRNC does not request periodic UE reporting in step 2, the SRNC repeats steps 2 to 10. The SRNC sends a location estimate to the CN one reporting interval after the previous location estimate until the desired amount of reports has been attained (or until the procedure is cancelled by UTRAN or CN). + +NOTE: The LMU update (of the time difference between the GPS and the Node B) may be performed on a per-request basis (with respect to each UE Positioning request) or be performed timely that is independent of individual UE Positioning request. The latter is preferable when there is a large volume of UE Positioning requests. + +## 10.7 SAS initiated Network Assisted GPS positioning Procedure + +The following describes the signalling for the optional initiation of the network assisted GPS positioning procedure by the SAS. + +![Sequence diagram showing the SAS initiated Network Assisted GPS positioning procedure. Lifelines: CN, SAS, SRNC, UE. The process involves a Location Request from CN to SRNC, followed by PCAP Position Initiation and Activation requests from SAS to SRNC. The SRNC sends a GPS Measurement Request to the UE, which responds with a GPS Measurement Report or GPS Position Report. The SRNC then sends PCAP Position Activation Response and PCAP Position Periodic Result/Report messages to the SAS. A 'Periodic Reporting' loop is shown where the SRNC sends periodic results to the SAS, which in turn send Location Estimates to the CN. The process concludes with a PCAP Position Initiation Response from SAS to SRNC and a final Location Estimate from SRNC to CN.](d7948c38a18636aefecdd95388196460_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant UE + + Note left of CN: Location Request + CN->>SRNC: Location Request + Note left of SAS: PCAP Position Initiation Req + SAS->>SRNC: PCAP Position Initiation Req + Note left of SAS: PCAP Position Activation Req + SAS->>SRNC: PCAP Position Activation Req + Note left of SRNC: GPS Measurement Request (GPS Assistance Data) + SRNC->>UE: GPS Measurement Request (GPS Assistance Data) + Note left of UE: GPS Measurement Report or GPS Position Report + UE->>SRNC: GPS Measurement Report or GPS Position Report + Note left of SRNC: PCAP Position Activation Resp + SRNC->>SAS: PCAP Position Activation Resp + Note left of SRNC: PCAP Position Periodic Result + SRNC-->>SAS: PCAP Position Periodic Result + Note left of SAS: Location Estimate + SAS-->>CN: Location Estimate + Note left of SRNC: PCAP Position Periodic Report + SRNC-->>SAS: PCAP Position Periodic Report + Note left of SAS: Location Estimate + SAS-->>CN: Location Estimate + Note left of SRNC: PCAP Position Periodic Result + SRNC-->>SAS: PCAP Position Periodic Result + Note left of SAS: Location Estimate + SAS-->>CN: Location Estimate + Note left of SRNC: Location Reporting Event N + Note left of SAS: PCAP Position Initiation Resp + SAS->>SRNC: PCAP Position Initiation Resp + Note left of SRNC: Location Estimate + SRNC-->>CN: Location Estimate + +``` + +Sequence diagram showing the SAS initiated Network Assisted GPS positioning procedure. Lifelines: CN, SAS, SRNC, UE. The process involves a Location Request from CN to SRNC, followed by PCAP Position Initiation and Activation requests from SAS to SRNC. The SRNC sends a GPS Measurement Request to the UE, which responds with a GPS Measurement Report or GPS Position Report. The SRNC then sends PCAP Position Activation Response and PCAP Position Periodic Result/Report messages to the SAS. A 'Periodic Reporting' loop is shown where the SRNC sends periodic results to the SAS, which in turn send Location Estimates to the CN. The process concludes with a PCAP Position Initiation Response from SAS to SRNC and a final Location Estimate from SRNC to CN. + +**Figure 10.4: Network-assisted GPS methods when initiated by the SAS** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. +2. The SRNC sends parameters received in the location request, including any periodic reporting information, together with the Cell ID and UE capability information to the SAS in a PCAP: Position Initiation Request message via the Iupc interface. + +3. Depending on the UE capabilities, the SAS initiates an A-GPS positioning procedure by sending a PCAP: Position Activation Request message containing A-GPS assistance data to the SRNC via the Iupc interface. The PCAP Position Activation Request message may include periodic reporting information (number of reports and reporting interval). The SAS may provide all or some A-GPS assistance data needed by the UE. This may include timing assistance data that the SAS may have obtained from associated LMUs or from another source (e.g. GPS Reference Network or measurements from UEs previously positioned by the SAS using A-GPS). +4. The SRNC forwards to the UE the A-GPS positioning request received from the SAS using RRC signalling. The SRNC also forwards in the RRC signalling message(s) the SAS request for either A-GPS measurements, in the case of UE assisted A-GPS, or an A-GPS position and optional velocity estimate, in the case of UE based A-GPS. The RRC signalling may include a request for periodic reporting as described in subclause 6.6.4.1 if this was received in step 3. For a description of UE based A-GPS, jump to step 9. +5. For UE assisted A-GPS, the SRNC requests from the UE the measurement of GPS satellite pseudoranges and other information specified in subclause 10.5.1. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. The SRNC may request SFN-SFN Observed Time Difference measurements and Rx-Tx timing difference information from the UE to support the processing related to the RTT measurements. +6. The UE returns to the SRNC the measurement of GPS satellite pseudoranges and other information specified in 10.5.1. If requested, the UE returns to the SRNC SFN-SFN measurements and the Rx-Tx time difference information, together with a time stamp of when these values were obtained. +7. The information obtained in step 6 is sent from the SRNC to the SAS in a PCAP: Position Activation Response message. +8. The SAS calculates the UE position and optional velocity. If periodic reporting was not requested in step 2, the SAS returns the UE position and optional velocity to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +9. In case of UE based method, the UE returns the position and optional velocity estimate to the SRNC via RRC signalling. The SRNC forwards the position and optional velocity estimate to the SAS in a PCAP: Position Activation Response message. This estimate includes the position and optionally, velocity, the estimated accuracy of the results and the time of the estimate. +10. The SAS may verify the UE position estimate received in step 9 (e.g. using cell ID information). If periodic reporting was not requested in step 2, the SAS returns the resulting estimate to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position estimate to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +11. If there is insufficient information to yield a UE positioning estimate satisfying the requested accuracy, the SAS may start a new process from step 3. +12. The SRNC passes the position estimate received from the SAS to the CN including the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +13. If periodic UE reporting was requested in step 4, the UE continues to send GPS measurement reports one reporting interval after the previous measurement report. The SRNC forward the GPS measurement report information to the SAS in a PCAP Position Periodic Report message. The SAS may calculate the UE position and optional velocity and may verify the calculated UE position estimate or the received UE position estimate (e.g. using cell ID information) and sends the position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position and optional velocity estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 13 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final + +location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. + +14. If periodic UE reporting was not requested in step 4, but was requested in step 2, the SAS may repeat the steps 3 to 12 as for the first request until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. When repeating step 10 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +NOTE: An update to the SAS from an associated LMU, of the time difference between GPS and the Node B, may be performed on a per-request basis (with respect to each UE Positioning request) or be performed in a timely manner that is independent of individual UE Positioning requests. The latter is preferable when there is a large volume of UE Positioning requests. + +# --- 11 Information storage + +NOTE This clause just outlines the information that may need to be stored in the UTRAN UE Positioning that may need to be standardised (if any). + +# --- 12 Uplink-Time Difference Of Arrival (U-TDOA) positioning method + +## 12.1 General + +The U-TDOA method calculates the location of a transmitting UE by using the difference in time of arrival of signals at different LMUs. The time required for a signal transmitted by a UE to reach a U-TDOA capable LMU is proportional to the length of the transmission path between the UE and the U-TDOA capable LMU. The U-TDOA method does not require knowledge of the time the UE transmits nor does it require any new functionality in the UE. + +![Figure 12.1: Ideal Signal Collection. The diagram shows two identical time-domain signal waveforms, one positioned above the other. Each signal begins with a low-amplitude noise floor, followed by a sharp rising edge to a higher-amplitude oscillating signal. The top waveform is shifted to the right relative to the bottom waveform. Three vertical lines connect corresponding peaks and troughs between the two signals to illustrate the time offset (phase difference) between them.](0c58b6f5c78547fec73ffbcf6df2c30c_img.jpg) + +Figure 12.1: Ideal Signal Collection. The diagram shows two identical time-domain signal waveforms, one positioned above the other. Each signal begins with a low-amplitude noise floor, followed by a sharp rising edge to a higher-amplitude oscillating signal. The top waveform is shifted to the right relative to the bottom waveform. Three vertical lines connect corresponding peaks and troughs between the two signals to illustrate the time offset (phase difference) between them. + +**Figure 12.1: Ideal Signal Collection** + +Figure 12.1 shows a time domain representations of two perfectly matched signals as received from the same UE by two U-TDOA capable LMUs in ideal conditions, including high signal-to-noise ratio and no multipath distortion. Because the receivers are at different distances from the transmitting UE, the signals are out of phase; they do not correlate. + +![Figure 12.2: Ideal and Attenuated Waveforms. The figure shows two waveforms. The top waveform is a high-amplitude signal with a complex shape, representing an ideal received signal. The bottom waveform is a significantly attenuated version of the top signal, with much lower amplitude, representing a signal received under more realistic conditions with increased distance, multipath distortion, and interference. Vertical lines connect corresponding peaks between the two waveforms to show their relative timing and shape.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +Figure 12.2: Ideal and Attenuated Waveforms. The figure shows two waveforms. The top waveform is a high-amplitude signal with a complex shape, representing an ideal received signal. The bottom waveform is a significantly attenuated version of the top signal, with much lower amplitude, representing a signal received under more realistic conditions with increased distance, multipath distortion, and interference. Vertical lines connect corresponding peaks between the two waveforms to show their relative timing and shape. + +**Figure 12.2. Ideal and Attenuated Waveforms** + +Figure 12.2 shows the theoretical effects of increased distance, multipath distortion, and interference on a received signal. The top signal was received under ideal conditions. The lower one represents what that signal would look like in more realistic conditions. It is attenuated to a level much closer to the noise floor. Nevertheless, there is a correlation with the original signal. + +**Cross-correlation** is a statistical technique that compares the waveforms of two signals point for point. Identical signals in perfect phase would yield a correlation coefficient of 1. In Figure 12.3, even though the waveform in (b) is attenuated compared to (a), the alignment would still yield a very high correlation, say 0.999. + +![Figure 12.3: Using Cross-Correlation to Compute Time Delay. The figure shows three waveforms labeled (a), (b), and (c). Waveform (a) is the reference signal. Waveform (b) is an attenuated and delayed version of (a). Waveform (c) is waveform (b) shifted to the left to align with (a). A horizontal double-headed arrow between the start of (a) and the start of (c) is labeled 'phase shift = time delay'. Vertical lines connect corresponding peaks between (a) and (c) to show perfect alignment.](1da66f5fec34c001912c84a9abf145d7_img.jpg) + +Figure 12.3: Using Cross-Correlation to Compute Time Delay. The figure shows three waveforms labeled (a), (b), and (c). Waveform (a) is the reference signal. Waveform (b) is an attenuated and delayed version of (a). Waveform (c) is waveform (b) shifted to the left to align with (a). A horizontal double-headed arrow between the start of (a) and the start of (c) is labeled 'phase shift = time delay'. Vertical lines connect corresponding peaks between (a) and (c) to show perfect alignment. + +**Figure 12.3. Using Cross-Correlation to Compute Time Delay** + +Figure 12.3 shows (a) a signal received by a U-TDOA capable LMU that is close to the transmitter and (b) the same signal received by a second U-TDOA capable LMU farther away. The latter signal is attenuated and perhaps distorted. It is also out of phase with the original signal because it was received at a later time. The correlation coefficient between (b) and (a) would be quite low. However, by shifting the (b) curve to the left, it is possible to find a position in which the correlation coefficient is maximized (shown by (c)). For this position, the amount of shift required is equal to the arrival time difference of the signal between the two U-TDOA capable LMUs. + +![Figure 12.4: Deriving the Hyperbolic Function for Time Delay. The diagram shows two reference sites, Rx1 and Rx2, represented by red and green squares respectively. Concentric circles of varying radii (solid and dashed) are centered around each site. A blue curve, labeled 'hyperbola', passes through the intersection points of corresponding circles from both sets. The hyperbola opens horizontally, with its vertices on the line segment between Rx1 and Rx2.](9c888dd6588358989047de6ced8b2bdb_img.jpg) + +Figure 12.4: Deriving the Hyperbolic Function for Time Delay. The diagram shows two reference sites, Rx1 and Rx2, represented by red and green squares respectively. Concentric circles of varying radii (solid and dashed) are centered around each site. A blue curve, labeled 'hyperbola', passes through the intersection points of corresponding circles from both sets. The hyperbola opens horizontally, with its vertices on the line segment between Rx1 and Rx2. + +**Figure 12.4. Deriving the Hyperbolic Function for Time Delay** + +In this model (Figure 12.4), Rx1 and Rx2 represent fixed locations of two U-TDOA capable LMUs in a network. The pairs of intersecting circles centered around Rx1 and Rx2 have radii such that each radius represents the time, $t_{TR}$ , it takes a signal to travel from a UE transmitter to each U-TDOA capable LMU (that time being unknown). The difference between radii is a constant equal to the difference between $t_{TR1}$ for the first U-TDOA capable LMU and $t_{TR2}$ for the second U-TDOA capable LMU. $t_{TR1} - t_{TR2}$ is the value that the U-TDOA system measures. When you plot and connect the points of intersections between each pair of circles, the resulting shape is a hyperbola. The hyperbola defined by the reference site in comparison to another site constitutes a baseline. If you constructed a similar hyperbola for another pair of U-TDOA capable LMUs receiving transmissions from the same UE, that hyperbola would intersect at two points with the first hyperbola, yielding two possible locations for the UE. A third such hyperbola (Figure 12.5) would yield a unique location for the calling phone, so that a minimum of four reception sites is needed to obtain the unique location estimate. + +![Figure 12.5: Intersection of Three Hypothetical Hyperbolas Calculated from Time Delay Differences. The diagram shows three hyperbolas in black. Two hyperbolas open horizontally in opposite directions, while the third hyperbola opens vertically. All three curves intersect at a single common point, illustrating how three hyperbolas can uniquely determine a location.](ddfefccc6c2fcfadf4e398109548faf8_img.jpg) + +Figure 12.5: Intersection of Three Hypothetical Hyperbolas Calculated from Time Delay Differences. The diagram shows three hyperbolas in black. Two hyperbolas open horizontally in opposite directions, while the third hyperbola opens vertically. All three curves intersect at a single common point, illustrating how three hyperbolas can uniquely determine a location. + +**Figure 12.5. Intersection of Three Hypothetical Hyperbolas Calculated from Time Delay Differences** + +In the U-TDOA method, the reference measurement is the one that represents the U-TDOA capable LMU site that collects the signal with the highest quality. That site is usually the site closest to the UE, and normally generates the highest signal level as well as the highest SNR. In addition, it presumably exhibits the lowest multi-path error. Therefore the reference time delay is the one against which time differences are measured. Any errors introduced into the time delay measurement yield inaccuracies in the intersection point. Since the speed of light is approximately 0.3 m/nsec in air, a nanosecond error in time delay measurement introduces 0.3 meters of error. + +The more hyperbolas that are calculated, that is, the more cooperating U-TDOA capable LMUs used in the calculation, the more accurate is the estimate of the UE's position. This is another way of saying that statistical confidence improves + +with an increase in sample points. When many sites enter into the calculation, the effects of a large time delay measurement error at a single site are minimized. + +## 12.2 U-TDOA SAS architecture + +The overall network architecture is similar to the previous architecture and is illustrated in Figure 12.6. The only difference is that the U-TDOA capable LMU are connected directly to the SAS via an overlay network. + +![Diagram of U-TDOA SAS Architecture showing UE, U-TDOA Capable LMUs, SAS, Node B, RNC, and CN with various interfaces.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +The diagram illustrates the U-TDOA SAS architecture. On the left, a UE (User Equipment) is shown. It has two connections: one to a group of three LMUs (Location Measurement Units) labeled 'U-TDOA Capable', and another to a Node B. The LMUs are connected to a SAS (Serving Access Station) via dashed lines, indicating an overlay network. The SAS is connected to an RNC (Radio Network Controller) via an Iupc interface. The RNC is connected to a CN (Core Network) via an Iu interface. The Node B is connected to the RNC via an Iub interface. A legend at the bottom right indicates the line types: Optional (dotted line), Mandatory (solid line), and Not Specified (dashed line). + +Diagram of U-TDOA SAS Architecture showing UE, U-TDOA Capable LMUs, SAS, Node B, RNC, and CN with various interfaces. + +Figure 12.6 – U-TDOA SAS Architecture + +The impact on the SAS centric approach due to the presence of the Iur is FFS. + +## 12.3 RNC based U-TDOA positioning for Cell\_DCH and Cell\_FACH RRC states + +The U-TDOA positioning method can be performed when the UE is in either the CELL\_DCH or CELL\_FACH RRC states. If the UE is in the CELL\_PCH or URA\_PCH state the SRNC shall first bring the UE to the CELL\_FACH or CELL\_DCH states so that the U-TDOA measurements can be performed by the LMUs and to provide the current serving Cell ID if the UE was in the URA\_PCH state. + +### 12.3.1 UE in CELL\_DCH state + +The SRNC may invoke the U-TDOA positioning method using the PCAP: Position Calculation Request message that contains the Cell ID and RF channel information for the UE being positioned when that UE is in the CELL\_DCH state. The SAS executes the U-TDOA positioning method and returns the location and optional velocity, or appropriate error indication to the SRNC using the PCAP: Position Calculation Response message as described below. + +![Sequence diagram of RNC initiated U-TDOA positioning procedure in CELL_DCH state. The diagram shows three lifelines: CN, SRNC, and SAS. The process starts with a 'Location request' from CN to SRNC. SRNC sends a 'PCAP: Position Calc. Request containing RF Channel info that indicates to the SAS the UE is on a DCH' to SAS. SAS then initiates and controls the U-TDOA positioning method. SAS returns a 'PCAP: Position Calc Response containing UE position or error indication' to SRNC, which in turn sends a 'Location estimate' to CN. A dashed box indicates a repeatable loop where SRNC sends the request again to SAS, SAS repeats the positioning method, and SRNC sends another 'Location estimate' to CN. Vertical ellipsis indicates further repetitions.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SRNC + participant SAS + Note right of SAS: SAS initiates and controls the U-TDOA positioning method + Note right of SAS: SAS initiates and controls the U-TDOA positioning method + Note center: ... + Note left of CN: Location estimate + Note left of SRNC: PCAP: Position Calc. Request containing RF Channel info that indicates to the SAS the UE is on a DCH + Note left of SAS: PCAP: Position Calc. Request containing RF Channel info that indicates to the SAS the UE is on a DCH + Note left of SAS: PCAP: Position Calc Response containing UE position or error indication + Note left of SRNC: PCAP: Position Calc Response containing UE position or error indication + Note left of CN: Location request + +``` + +Sequence diagram of RNC initiated U-TDOA positioning procedure in CELL\_DCH state. The diagram shows three lifelines: CN, SRNC, and SAS. The process starts with a 'Location request' from CN to SRNC. SRNC sends a 'PCAP: Position Calc. Request containing RF Channel info that indicates to the SAS the UE is on a DCH' to SAS. SAS then initiates and controls the U-TDOA positioning method. SAS returns a 'PCAP: Position Calc Response containing UE position or error indication' to SRNC, which in turn sends a 'Location estimate' to CN. A dashed box indicates a repeatable loop where SRNC sends the request again to SAS, SAS repeats the positioning method, and SRNC sends another 'Location estimate' to CN. Vertical ellipsis indicates further repetitions. + +**Figure 12.7: RNC initiated U-TDOA positioning procedure in CELL\_DCH state** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC in a RANAP: Location Reporting Control message. The request from the CN may be a request for on-demand or periodic reporting. The SRNC may invoke the U-TDOA positioning method via the Iupc interface. +2. The SRNC sends a PCAP: Position Calculation Request message to the SAS containing the contents of the RANAP Location Reporting Control message, the RF channel information and Cell ID for the UE being positioned. This information indicates that the UE is in the CELL\_DCH state. +3. The SAS configures the U-TDOA capable LMUs, analyzes the returned information and calculates the UE position and optionally, velocity. +4. The SAS returns the UE position and optionally the velocity or error indication to the SRNC in a PCAP: Position Calculation Response message. +5. The SRNC returns the UE position and optionally the velocity, to the CN in a RANAP: Location Report message. +6. If periodic reporting was requested by the CN at step 1, steps 2 to 5 may be repeated until the desired amount of reports has been attained, or the procedure is cancelled by UTRAN or CN. + +### 12.3.2 UE in CELL\_FACH state + +The SRNC may invoke the U-TDOA positioning method using the PCAP: Position Calculation Request message that contains the contents of the RANAP Location Reporting Control message, Cell ID and RF channel information for the UE being positioned. If the UE is in the CELL\_FACH state the SRNC, after sending the Position Calculation Request message, shall execute a procedure that causes the UE being positioned to transmit a certain number of pre-coded bits within a certain period of time. The procedure described in steps 6-8 in subclause 12.4.2.1 below is offered as an example that could be used for the U-TDOA positioning method when the UE is in the CELL\_FACH state. + +The SAS executes the U-TDOA positioning method and returns the location or appropriate error indication to the SRNC using the PCAP: Position Calculation Response message as described below. + +![Sequence diagram of RNC initiated U-TDOA positioning procedure in CELL_FACH state. The diagram shows interactions between CN, SRNC, and SAS. The first sequence shows a successful positioning request and response. A second sequence, enclosed in a dashed box, shows a subsequent positioning request and response. In both sequences, the SRNC configures the UE to transmit RLC Status PDUs on the FACH, and the SAS initiates and controls the U-TDOA positioning method after a configurable time interval.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SRNC + participant SAS + + CN->>SRNC: Location request + SRNC->>SAS: PCAP: Position Calc. Request containing RF Channel info indicating to the SAS that the UE is on a FACH + Note over SRNC: SRNC configures UE to transmit RLC Status PDUs on the FACH + Note over SAS: SAS initiates and controls the U-TDOA positioning method which begins after a configurable time interval + SAS->>SRNC: PCAP: Position Calc Response containing UE position or error indication + SRNC->>CN: Location estimate + + rect rgb(255, 255, 255) + Note over CN, SAS: (Dashed box indicating repetition) + SRNC-->>SAS: PCAP: Position Calc. Request containing RF Channel info indicating to the SAS that the UE is on a FACH + Note over SRNC: SRNC configures UE to transmit RLC Status PDUs on the FACH + Note over SAS: SAS initiates and controls the U-TDOA positioning method which begins after a configurable time interval + SAS-->>SRNC: PCAP: Position Calc Response containing UE position or error indication + SRNC-->>CN: Location estimate + end + + Note over SRNC, SAS: ... + +``` + +Sequence diagram of RNC initiated U-TDOA positioning procedure in CELL\_FACH state. The diagram shows interactions between CN, SRNC, and SAS. The first sequence shows a successful positioning request and response. A second sequence, enclosed in a dashed box, shows a subsequent positioning request and response. In both sequences, the SRNC configures the UE to transmit RLC Status PDUs on the FACH, and the SAS initiates and controls the U-TDOA positioning method after a configurable time interval. + +**Figure 12.8: RNC initiated U-TDOA positioning procedure in CELL\_FACH state** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC in a RANAP: Location Reporting Control message. The request from the CN may be a request for either on-demand or periodic reporting. The SRNC may invoke the U-TDOA positioning method via the Iupc interface. +2. The SRNC sends a PCAP: Position Calculation Request message to the SAS containing the contents of the RANAP Location Reporting Control message, the RF channel information and Cell ID for the UE being positioned. This information indicates that the UE is on a FACH. +3. After sending the Position Calculation Request message the SRNC shall execute a procedure that causes the UE being positioned to transmit a certain minimum number of pre-coded bits within a recommended maximum time interval of three seconds. The number of bits and actual time interval should be related to the required location accuracy, the propagation conditions in the serving cell and the LMU configuration for the SAS and may be determined in an implementation dependent manner. As an example of a method to cause the UE to transmit, the SRNC may configure the UE to transmit RLC Status PDUs as described in subclause 12.4.2 below. +4. After a configurable time interval the SAS configures the U-TDOA capable LMUs, analyzes the returned information and calculates the UE position and optionally, velocity. + +5. The SAS returns the UE position and optionally, velocity to the SRNC in a PCAP: Position Calculation Response message. +6. The SRNC returns the UE position and optionally, the velocity to the CN in a RANAP: Location Report message. +7. If periodic reporting was requested by the CN at step 1, steps 2 to 6 may be repeated until the desired amount if reports has been attained, or the procedure is cancelled by UTRAN or CN. + +## 12.4 Optional SAS initiated U-TDOA positioning for Cell\_DCH and Cell\_FACH RRC states + +This subclause describes the U-TDOA positioning procedures in the CELL\_DCH and CELL\_FACH states when the location method to be used is determined by the SAS. + +### 12.4.1 UE in CELL\_DCH state + +#### **FDD Mode:** + +Data (either signalling data (DCCH) or user data (DTCH)) transmitted by a UE in CELL\_DCH state will always be sent on the DCH (Transport Channel). The DCH in turn is mapped to the DPDCH (Dedicated Physical Data Channel) by the physical layer. The DPDCH is identified by the allocated frequency, the channelization code and the scrambling code. + +The DPDCH always has an associated DPCCH (Dedicated Physical Control Channel). The DPCCH carries control information relevant to the physical layer. The DPCCH is under the same scrambling code, but uses a different spreading code. + +While the DPDCH is active only during actual transmission of user data, the DPCCH is continuously transmitted as long as the UE is in the CELL\_DCH state. The UE transmits either the DPCCH *and* the DPDCH, or solely the DPCCH – the scrambling code allocated to the UE can be received continuously as long as the UE is in the CELL\_DCH state. + +When the UE is in CELL\_DCH state, the allocated scrambling code can be used to identify the UE for U-TDOA positioning determination. No additional interference is generated to locate the UE using the U-TDOA positioning method when in the CELL\_DCH state. + +#### **TDD Mode:** + +Data (either signalling data (DCCH) or user data (DTCH)) transmitted by a UE in CELL\_DCH state will always be sent on the DCH (Transport Channel). The DCH in turn is mapped to the DPCH (Dedicated Physical Channel) by the physical layer. The DPCH is identified by the allocated frequency, the channelization code(s)/timeslot(s) and the scrambling code associated with the cell that the UE is attached to (the scrambling code is cell-specific).. + +The DPCH is active: + +- during actual transmission of user data +- during the transmission of special bursts [26]. + +Special bursts are generated periodically when the UE has no data to send. + +When the UE is in CELL\_DCH state, the allocated uplink scrambling code assigned to the UE's cell and the channelisation code(s) / timeslot(s) can be used to identify the UE for U-TDOA positioning determination. No additional interference is generated to locate the UE using the U-TDOA positioning method when in the CELL\_DCH state. + +#### 12.4.1.1 Message Flow + +![Sequence diagram showing U-TDOA message flow between SAS, RNC, and CN. The diagram illustrates the interaction for positioning a UE in the CELL_DCH state. It includes steps for RANAP Location Reporting Control, PCAP Position Initiation Request/Response, PCAP Position Activation, SAS configuration of LMUs, and periodic reporting of UE position estimates.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant CN + participant RNC + participant SAS + + Note right of SAS: 5. SAS configures LMUs which measure the DPCCH and possibly DPDCH + + Note left of RNC: Periodic Reporting + + CN->>RNC: 1. RANAP Location Reporting Control + RNC->>SAS: 2. PCAP Position Initiation Request + SAS->>RNC: 3. PCAP Position Activation Request for U-TDOA + RNC->>SAS: 4. PCAP Position Activation Response plus channel information + Note right of SAS: 5. SAS configures LMUs which measure the DPCCH and possibly DPDCH + Note left of RNC: Periodic Reporting + SAS-->>RNC: 5a. PCAP Position Periodic Result containing UE Position Estimate + RNC-->>CN: 5a. RANAP Location Report (UE Position Estimate) + SAS-->>RNC: 5a. PCAP Position Periodic Result containing UE Position Estimate + RNC-->>CN: 5a. RANAP Location Report (UE Position Estimate) + Note right of RNC: 5a. Location Reporting Event N + SAS->>RNC: 6. PCAP Position Initiation Response containing UE Position Estimate + RNC->>CN: 7. RANAP Location Report (UE Position Estimate) + +``` + +Sequence diagram showing U-TDOA message flow between SAS, RNC, and CN. The diagram illustrates the interaction for positioning a UE in the CELL\_DCH state. It includes steps for RANAP Location Reporting Control, PCAP Position Initiation Request/Response, PCAP Position Activation, SAS configuration of LMUs, and periodic reporting of UE position estimates. + +**Figure 12.9 U-TDOA message flow, UE in the CELL\_DCH state** + +- 1) The procedure starts when a RANAP: Location Reporting Control message requesting a geographical UE position is received at the SRNC. The RANAP Location Reporting Control message may contain periodic location information (amount of reports and reporting interval). +- 2) Location Reporting Control message parameters, including any periodic location information, plus UE capability information plus Cell ID are forwarded to the SAS in the PCAP: Position Initiation Request message. +- 3) Based upon the service type (emergency service, etc), and the requested QoS, the SAS initiates a U-TDOA position, and sends a PCAP: Position Activation Request message indicating U-TDOA to the SRNC. The SRNC chooses to bring the UE to the CELL\_DCH state if not already in this state. +- 4) The SRNC returns U-TDOA channel information in a PCAP: Position Activation Response message to the SAS. +- 5) The SAS configures the U-TDOA capable LMUs to perform measurements. The U-TDOA capable LMUs measure the [FDD: DPCCH and possibly DPDCH] [TDD: DPCH]. +- 5a) If periodic reporting was requested in step 2, the SAS obtains a position, and optionally a velocity estimate using the U-TDOA capable LMU measurements and returns it to the SRNC in a PCAP: Position Periodic Result message. The SAS continues to send PCAP: Position Periodic Result messages to the SRNC until the requested amount of reports has been attained or the procedure is cancelled by UTRAN or CN. The SAS sends the final location information to the SRNC in a PCAP Position Initiation Response message. The SAS may repeat steps 3 and 4 at any time to obtain or verify the U-TDOA channel information. The SRNC returns the individual position estimates and optionally the velocity estimate to the CN in a RANAP: Location Report message. +- 6) If periodic reporting was not requested in step 2, the SAS obtains a position, and optionally a velocity estimate using the U-TDOA capable LMU measurements and returns it to the SRNC in a PCAP: Position Initiation Response message. +- 7) The SRNC returns the position estimate and optionally the velocity estimate to the CN in a RANAP: Location Report message. + +### 12.4.2. UE in CELL\_FACH state + +In the CELL\_FACH state the mobile is sharing a common uplink channel and is usually not sending data in the uplink direction. It is not possible to rely on the user application to cause the UE to transmit. For the U-TDOA location method the SRNC must force the UE to transmit. + +As an example, this may be achieved by sending a RRC Radio Bearer Reconfiguration message that causes the UE to periodically send a RLC: Status PDU to the SRNC for an Acknowledged Mode DCCH. When sufficient repetitions have occurred to meet the requested location QoS the RRC Radio Bearer Reconfiguration message would be used to return the UE to the default state. In the TDD mode, the DCCH signalling radio bearer carrying the status PDUs shall be mapped to the RACH transport channel, not the USCH. + +#### 12.4.2.1 Message flow + +![Sequence diagram illustrating the Example U-TDOA message flow, UE in the CELL_FACH state. The diagram shows interactions between UE, Node B, SAS, RNC, and CN. The process involves RANAP Location Reporting Control, PCAP Position Initiation Request, PCAP Position Activation Request for U-TDOA, and subsequent periodic reporting steps involving Radio Bearer Reconfig and RLC Status PDUs. A 'Periodic Reporting' bracket on the left indicates the repeating nature of steps 6-8 and 8a-8b. A 'T_rach' timer is shown between RNC and CN.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +The sequence diagram illustrates the message flow for U-TDOA positioning when the UE is in the CELL\_FACH state. The participants are UE, Node B, SAS, RNC, and CN. + +- The process begins with the CN sending a **1. RANAP Location Reporting Control** message to the RNC. +- The RNC then sends a **2. PCAP Position Initiation Request** to the SAS. +- The SAS responds with a **3. PCAP Position Activation Request for U-TDOA** to the RNC. +- The RNC sends a **4. PCAP Position Activation Response plus channel information** back to the SAS. +- A box indicates that **5. SAS configures LMUs which measure the PRACH and possibly PCPCH**. +- The RNC sends a **6. Radio\_Bearer\_Reconfig.** message to the Node B, with a note **(Timer\_Status\_Periodic = 100 mS for SRB 2 or 3)**. The Node B then sends a **6. Radio\_Bearer\_Recon.** message to the UE. +- The UE sends three **7. RLC: Status PDU** messages to the Node B. +- The RNC sends an **8. Radio\_Bearer\_Reconfig.** message to the Node B, with a note **(Timer\_Status\_Periodic = N/A for SRB 2 or 3)**. The Node B then sends an **8. Radio\_Bearer\_Recon.** message to the UE. +- A bracket on the left labeled **Periodic Reporting** encompasses steps 8a through 8b, indicating a repeating sequence. + - 8a. PCAP Position Periodic Result** is sent from the SAS to the RNC. + - The RNC sends a **8a. RANAP Location Report (UE Position Estimate)** to the CN. + - The RNC also sends a **8b PCAP Position Activation Request for U-TDOA** to the SAS. + - The SAS responds with a **8b PCAP Position Activation Response plus channel information** to the RNC. + - A box indicates that **SAS configures LMUs which measure the PRACH and possibly PCPCH**. + - The RNC sends a **8b Radio\_Bearer\_Reconfig.** message to the Node B, with a note **(Timer\_Status\_Periodic = 100 mS for SRB 2 or 3)**. The Node B then sends an **8b Radio\_Bearer\_Recon.** message to the UE. + - The UE sends three **8b RLC: Status PDU** messages to the Node B. + - The RNC sends another **8b Radio\_Bearer\_Reconfig.** message to the Node B, with a note **(Timer\_Status\_Periodic = N/A for SRB 2 or 3)**. The Node B then sends another **8b Radio\_Bearer\_Recon.** message to the UE. + - The SAS sends a **8b PCAP Position Periodic Result** to the RNC. + - The RNC sends an **8b RANAP Location Report (UE Position Estimate)** to the CN. +- After the periodic reporting, the SAS sends a **9. PCAP Position Initiation Response containing UE Position Estimate** to the RNC. +- Finally, the RNC sends a **10. RANAP Location Report (UE Position Estimate)** to the CN. + +A vertical double-headed arrow labeled **T\_rach** is shown between the RNC and CN, indicating a timer or interval. + +Sequence diagram illustrating the Example U-TDOA message flow, UE in the CELL\_FACH state. The diagram shows interactions between UE, Node B, SAS, RNC, and CN. The process involves RANAP Location Reporting Control, PCAP Position Initiation Request, PCAP Position Activation Request for U-TDOA, and subsequent periodic reporting steps involving Radio Bearer Reconfig and RLC Status PDUs. A 'Periodic Reporting' bracket on the left indicates the repeating nature of steps 6-8 and 8a-8b. A 'T\_rach' timer is shown between RNC and CN. + +**Figure 12.10 Example U-TDOA message flow, UE in the CELL\_FACH state** + +- 1) The procedure starts when a RANAP: Location Reporting Control message requesting a geographical UE position is received at the SRNC. The RANAP Location Reporting Control message may contain periodic location information (amount of reports and reporting interval). +- 2) Location Reporting Control message parameters, including any periodic location information, plus Cell ID plus UE capability information are forwarded to the SAS in the PCAP: Position Initiation Request message. + +- 3) Based upon the service type (emergency service, etc), and the requested QOS, the SAS initiates a U-TDOA position, and sends a PCAP: Position Activation Request message indicating U-TDOA to the SRNC. The SRNC chooses to bring the UE to the CELL\_FACH state if initially in the CELL\_PCH or URA\_PCH state. +- 4) The SRNC returns U-TDOA channel information in a PCAP: Position Activation Response message to the SAS. +- 5) The SAS configures the U-TDOA capable LMUs to perform measurements. The U-TDOA capable LMUs measure the PRACH or PCPCH bursts associated with the UE being positioned. +- 6) The SRNC, after sending the PCAP Position Activation Response message, shall execute a procedure that causes the UE being positioned to transmit a certain number of pre-coded bits within a certain period of time. The number of pre-coded bits and period of time should be based upon (e.g. set equal to) a recommended number of bits and recommended time interval defined by the SAS in the PCAP Position Activation Request message invoking U-TDOA positioning. As an example, the SRNC could reconfigure the radio bearer so that the UE begins to send RLC status PDUs every 100 mS by sending the UE a Radio\_Bearer\_Reconfiguration message with the TimerStatusPeriodic IE configured for 100 milliseconds. +- 7) The UE begins to send RLC status PDUs every 100 milliseconds. +- 8) After expiration of the configurable T\_rach timer the SRNC sends the UE a Radio\_Bearer\_Reconfiguration message with the TimerStatusPeriodic IE set to NA in order to stop the periodic status reporting. +- 8a) If periodic reporting was requested in step 2, the SAS obtains a position, and optionally a velocity estimate using the U-TDOA capable LMU measurements and returns it to the SRNC in a PCAP: Position Periodic Result message. The SRNC returns the position estimate and optionally the velocity estimate to the CN in a RANAP: Location Report message. When the periodic reporting interval transpired, the SAS may send a new PCAP: Position Activation Request message to the SRNC and steps 3 to 8 may be repeated until the requested amount of reports has been attained or the procedure is cancelled by UTRAN or CN. The SAS sends the final location information to the SRNC in a PCAP Position Initiation Response message. The SRNC returns the individual position estimates and optionally the velocity estimate to the CN in a RANAP: Location Report message. +- 9) If periodic reporting was not requested in step 2, the SAS obtains a position, and optionally a velocity estimate using the U-TDOA capable LMU measurements and returns it to the SRNC in a PCAP: Position Initiation Response message. +- 10) The SRNC returns the position estimate and optionally a velocity estimate to the CN in a RANAP: Location Report message. + +# --- 13 Network-assisted GNSS positioning method + +In this concept, different GNSS (e.g. GPS, Galileo, GLONASS and BDS) can be used separately or in combination to perform the location of a UE. The aim of such combination is to improve: + +- the availability of the location service, +- the accuracy of the position, +- the sensitivity to e.g. fading, +- the integrity of the signal, +- the reliability of the signal, +- the in-building penetration. + +This can be done thanks to the combination of different global navigation satellite systems and the increased number of satellites. + +## 13.1 Network-assisted GPS positioning method + +Refer to clause 10. + +"Modernized-GPS" refers to a family of modernized GPS satellites which bring support for new navigation signals, such as a Civilian L2 (L2C) signal, a Safety-of-Life L5 signal, and a new Civilian L1 (L1C) signal, together with improved navigation message data. + +## 13.2 Network-assisted Galileo positioning method + +The procedure is the same as for network-assisted GPS positioning method except that the Galileo satellites and parameters are used instead of those of the GPS. + +## 13.3 Network-assisted GLONASS positioning method + +The procedure is the same as for network-assisted GPS positioning method except that the GLONASS satellites and parameters are used instead of those of the GPS. + +## 13.4 Network-assisted Satellite Based Augmentation Systems (SBAS) + +Several independent but compatible satellite based augmentation systems exist: The American Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Indian GPS Aided GEO Augmented Navigation System (GAGAN), and the Japanese Multi-functional Satellite Augmentation System (MSAS). The (GPS-like) ranging signals from all these SBASs are here considered as a single GNSS, although this GNSS is not a standalone positioning system because of the small number of satellites and their distribution in space. Usually, this GNSS is used in combination with e.g., GPS, Galileo, or GLONASS ranging signals. + +The procedure is the same as for network-assisted GPS positioning method except that the SBAS satellites and parameters are used instead of those of the GPS. + +## 13.5 Network-assisted Quasi-Zenith Satellite System (QZSS) + +Quasi-Zenith Satellite System (QZSS) is a regional navigation satellite system. The eccentricity and elevation of the satellite orbits are selected so that the minimum elevation angle through 24 hours in Japan is larger than about 60 degrees. The satellite signals are fully compatible and interoperable with current and modernized future GPS. Similar to SBAS ranging signals, this GNSS is not a standalone positioning system and is usually used in combination with other GNSS ranging signals, such as GPS, Galileo, GLONASS, etc. + +The procedure is the same as for network-assisted GPS positioning method except that the QZSS satellites and parameters are used instead of those of the GPS. + +## 13.6 Network-assisted BeiDou Navigation Satellite System (BDS) positioning method + +The procedure is the same as for network-assisted GPS positioning method except that the BDS satellites and parameters [31] are used instead of those of the GPS. + +# --- 14 Barometric Pressure positioning methods + +## 14.1 General + +In the Barometric Pressure positioning method, the UE vertical component of the position is estimated by combining the measured atmospheric pressure and a reference atmospheric pressure. This is accomplished through barometric pressure sensors measuring atmospheric pressure at the UE, and applying a height determination algorithm using the reference atmospheric pressure. + +Two positioning modes are supported: + +- *UE-Assisted*: The UE performs Barometric Pressure measurements without assistance from the network and sends these measurements to the SAS/RNC where the vertical position calculation may take place, possibly using additional measurements from other sources; + +- *Standalone*: The UE performs Barometric Pressure measurements and calculates its own vertical component of the position, possibly using additional measurements from other sources. + +A UE with Barometric Pressure sensing capability operates without assistance from the network. + +## 14.2 Information to be transferred between UTRAN Elements + +This subclause defines the information (e.g., vertical position and/or measurement data) that may be transferred between UTRAN elements. + +### 14.2.1 Information that may be transferred from the UE to Network + +The information that may be signalled from UE to the SAS/RNC is listed in table 14.2.1-1. + +**Table 14.2.1-1: Information that may be transferred from UE to the Network** + +| Information | UE-assisted | Standalone | +|---------------------------------------------------|-------------|------------| +| UE 3D position estimate with uncertainty shape | No | Yes | +| Indication of used positioning methods in the fix | No | Yes | +| Timestamp | Yes | Yes | +| Barometric Pressure measurements | Yes | No | + +The information reported from the UE to the Network depends on the positioning mode (i.e., standalone, or UE-assisted). + +#### 14.2.1.1 Standalone mode + +In standalone mode, the UE reports the altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of which positioning method(s) have been used to calculate a fix. + +#### 14.2.1.2 UE-assisted mode + +In UE-assisted mode, the UE reports the Barometric Pressure measurements together with associated quality estimates. These measurements enable the Network to calculate the vertical location of the UE, possibly using other measurements and data. + +If requested by the SAS/RNC and supported by the UE, the UE may report Barometric Pressure measurements together with associated quality measurements, if available. + +## 14.3 Location Information Transfer Procedure + +The purpose of this procedure is to enable the SAS/RNC to request Barometric Pressure measurements or 3D position estimate from the UE, or to enable the UE to provide Barometric Pressure measurements to the SAS/RNC for vertical position calculation (e.g., in case of basic self location where the UE requests its own location). + +### 14.3.1 SAS initiated Barometric Pressure positioning procedure + +The following describes the signalling for the optional initiation of the network Barometric Pressure vertical positioning procedure by the SAS. + +![Sequence diagram illustrating Barometric Pressure methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends PCAP Position Activation Req to SRNC. SRNC sends Barometric pressure measurements request to UE. UE returns Barometric pressure measurements report or position report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' block contains dashed arrows for Location estimate, PCAP Position Periodic Result, and PCAP Position Periodic Report between SRNC, SAS, and UE. A 'Location Reporting Event N' box is shown. Finally, SAS sends PCAP Position Initiation Resp to SRNC, and SRNC sends Location estimate to CN.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant UE + + Note left of CN: Location request + CN->>SRNC: Location request + SRNC->>SAS: PCAP Position Initiation Req + SRNC->>SAS: PCAP Position Activation Req + SAS->>SRNC: PCAP Position Activation Req + SRNC->>UE: Barometric pressure measurements request + UE-->>SRNC: Barometric pressure measurements report or position report + SRNC->>SAS: PCAP Position Activation Resp + + subgraph Periodic Reporting + SRNC-->>SAS: Location estimate + SRNC-->>SAS: PCAP Position Periodic Result + SRNC-->>SAS: PCAP Position Periodic Report + SRNC-->>SAS: PCAP Position Periodic Result + SRNC-->>SAS: Location estimate + UE-->>SRNC: Barometric pressure measurements report or position report + end + + Note right of SRNC: Location Reporting Event N + + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>CN: Location estimate + +``` + +Sequence diagram illustrating Barometric Pressure methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends PCAP Position Activation Req to SRNC. SRNC sends Barometric pressure measurements request to UE. UE returns Barometric pressure measurements report or position report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' block contains dashed arrows for Location estimate, PCAP Position Periodic Result, and PCAP Position Periodic Report between SRNC, SAS, and UE. A 'Location Reporting Event N' box is shown. Finally, SAS sends PCAP Position Initiation Resp to SRNC, and SRNC sends Location estimate to CN. + +**Figure 14.3.1-1: Barometric Pressure methods when initiated by the SAS** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. +2. The SRNC sends parameters received in the location request, including any periodic reporting information, together with the Cell ID and UE capability information to the SAS in a PCAP: Position Initiation Request message via the Iupc interface. +3. Depending on the UE capabilities, the SAS initiates a Barometric Pressure positioning procedure by sending a PCAP: Position Activation Request message that allows for the use of Barometric Pressure positioning (along with GPS or OTDOA, and optionally WLAN, Bluetooth or TBS positioning methods) to the SRNC via the Iupc interface. The PCAP Position Activation Request message may include periodic reporting information (number of reports and reporting interval). +4. The SRNC forwards to the UE the Barometric Pressure positioning request received from the SAS using RRC signalling. The SRNC also forwards in the RRC signalling message(s) the SAS request for either Barometric Pressure measurements, in the case of UE assisted, or a vertical position coordinate, in the case of standalone. The RRC signalling may include a request for periodic reporting as described in subclause 6.6.4.1 if this was received in step 3. For a description of standalone Barometric Pressure mode, jump to step 9. +5. For UE assisted Barometric Pressure, the SRNC requests from the UE the atmospheric pressure measurements. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. +6. The UE returns to the SRNC the available barometric pressure measurements, together with a time stamp of when these values were obtained. +7. The information obtained in step 6 is sent from the SRNC to the SAS in a PCAP: Position Activation Response message. + +8. The SAS calculates the vertical UE position. If periodic reporting was not requested in step 2, the SAS returns the UE position to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +9. In case of standalone method, the UE returns the vertical position estimate to the SRNC via RRC signalling. The SRNC forwards the position estimate to the SAS in a PCAP: Position Activation Response message. This estimate includes the position, the estimated accuracy of the results and the time of the estimate. +10. If periodic reporting was not requested in step 2, the SAS returns the resulting estimate to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position estimate to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +11. If there is insufficient information to yield a UE vertical positioning estimate satisfying the requested accuracy, the SAS may start a new process from step 3. +12. The SRNC passes the position estimate received from the SAS to the CN including the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +13. If periodic UE reporting was requested in step 4, the UE continues to send Barometric Pressure measurement reports one reporting interval after the previous measurement report. The SRNC forward the Barometric Pressure measurement report information to the SAS in a PCAP Position Periodic Report message. The SAS may calculate the UE vertical position and sends the position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 13 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. +14. If periodic UE reporting was not requested in step 4, but was requested in step 2, the SAS may repeat the steps 3 to 12 as for the first request until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. When repeating step 10 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +# --- 15 WLAN positioning method + +In the WLAN positioning method, the UE position is estimated with the knowledge of geographical coordinate of reference WLAN access points. This is accomplished by collecting a certain amount of measurements from UE's WLAN receiver, and applying a location determination algorithm using databases of the estimated position's references points. + +The UE measurements can include: + +- WLAN Received Signal Strength (RSSI); +- Round Trip Time (RTT) between WLAN Access Point and the UE. + +Two modes are supported for WLAN positioning: + +- *Standalone*: in this mode, the UE performs WLAN measurements and calculates its own location; +- *UE-Assisted*: The UE performs WLAN measurements without assistance from the network and sends these measurements to the SAS/RNC where the position calculation takes place using a database. + +A UE with WLAN capability operates without assistance from the network. + +## 15.1 Information to be transferred between UTRAN elements + +The information that may be signalled from the UE to the network is listed in table 15.1-1. + +**Table 15.1-1: Information that may be transferred from the UE to the network** + +| Information | UE-assisted | Standalone | +|------------------------------------------------------|-------------|------------| +| WLAN Location Information | | | +| BSSID | Yes | No | +| SSID | Yes | No | +| Received Signal Strength (RSSI) | Yes | No | +| Round Trip Time (RTT) | Yes | No | +| Measurement Time Stamp | Yes | No | +| Measurement Characteristics | Yes | No | +| UE Location Information | | | +| UE 3D Position estimate with uncertainty shape | No | Yes | +| Location Time Stamp | No | Yes | +| Location Source (method(s) used to compute location) | No | Yes | + +## 15.2 SAS initiated WLAN positioning procedure + +The following describes the signalling for the optional initiation of the network WLAN positioning procedure by the SAS. + +![Sequence diagram illustrating WLAN methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends WLAN measurements request to UE. UE returns WLAN measurements report or position coordinates report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase follows, where SRNC sends PCAP Position Periodic Result to SAS, SAS sends Location estimate to CN, SRNC sends PCAP Position Periodic Report to SAS, SAS sends PCAP Position Periodic Result to SRNC, SRNC sends Location estimate to CN, and finally a Location Reporting Event N is sent from SRNC to CN. The process concludes with PCAP Position Initiation Resp from SAS to SRNC and a final Location estimate from SRNC to CN.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant UE + + Note left of CN: Periodic Reporting + CN->>SRNC: Location request + SRNC->>SAS: PCAP Position Initiation Req + SRNC->>SAS: PCAP Position Activation Req + SRNC->>UE: WLAN measurements request + UE-->>SRNC: WLAN measurements report or position coordinates report + SRNC->>SAS: PCAP Position Activation Resp + Note right of SRNC: Periodic Reporting + SRNC-->>SAS: PCAP Position Periodic Result + SAS-->>CN: Location estimate + SRNC-->>SAS: PCAP Position Periodic Report + SAS-->>SRNC: PCAP Position Periodic Result + SRNC-->>CN: Location estimate + Note right of SRNC: Location Reporting Event N + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>CN: Location estimate + +``` + +Sequence diagram illustrating WLAN methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends WLAN measurements request to UE. UE returns WLAN measurements report or position coordinates report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase follows, where SRNC sends PCAP Position Periodic Result to SAS, SAS sends Location estimate to CN, SRNC sends PCAP Position Periodic Report to SAS, SAS sends PCAP Position Periodic Result to SRNC, SRNC sends Location estimate to CN, and finally a Location Reporting Event N is sent from SRNC to CN. The process concludes with PCAP Position Initiation Resp from SAS to SRNC and a final Location estimate from SRNC to CN. + +**Figure 15.2-1: WLAN methods when initiated by the SAS** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. +2. The SRNC sends parameters received in the location request, including any periodic reporting information, together with the Cell ID and UE capability information to the SAS in a PCAP: Position Initiation Request message via the Iupc interface. +3. Depending on the UE capabilities, the SAS initiates a WLAN positioning procedure by sending a PCAP: Position Activation Request message that allows for the use of WLAN positioning (along with GPS or OTDOA, and optionally Barometric Pressure, Bluetooth or TBS positioning methods) via the Iupc interface. The PCAP Position Activation Request message may include periodic reporting information (number of reports and reporting interval). +4. The SRNC forwards to the UE the WLAN positioning request received from the SAS using RRC signalling. The SRNC also forwards in the RRC signalling message(s) the SAS request for either WLAN measurements, in the case of UE assisted, or a position coordinates, in the case of standalone. The RRC signalling may include a request for periodic reporting as described in subclause 6.6.4.1 if this was received in step 3. For a description of standalone WLAN, jump to step 9. +5. For UE assisted WLAN, the SRNC requests from the UE the measurement of WLAN RSSI and RTT. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. + +6. The UE returns to the SRNC the available WLAN measurements, together with a time stamp of when these values were obtained. +7. The information obtained in step 6 is sent from the SRNC to the SAS in a PCAP: Position Activation Response message. +8. The SAS calculates the UE position. If periodic reporting was not requested in step 2, the SAS returns the UE position to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +9. In case of standalone method, the UE returns the position estimate to the SRNC via RRC signalling. The SRNC forwards the position estimate to the SAS in a PCAP: Position Activation Response message. This estimate includes the position, the estimated accuracy of the results and the time of the estimate. +10. The SAS may verify the UE position estimate received in step 9 (e.g. using cell ID information). If periodic reporting was not requested in step 2, the SAS returns the resulting estimate to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position estimate to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +11. If there is insufficient information to yield a UE positioning estimate satisfying the requested accuracy, the SAS may start a new process from step 3. +12. The SRNC passes the position estimate received from the SAS to the CN including the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +13. If periodic UE reporting was requested in step 4, the UE continues to send WLAN measurement reports one reporting interval after the previous measurement report. The SRNC forward the WLAN measurement report information to the SAS in a PCAP Position Periodic Report message. The SAS may calculate the UE position and may verify the calculated UE position estimate or the received UE position estimate (e.g. using cell ID information) and sends the position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 13 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. +14. If periodic UE reporting was not requested in step 4, but was requested in step 2, the SAS may repeat the steps 3 to 12 as for the first request until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. When repeating step 10 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +# --- 16 Bluetooth positioning methods + +In the Bluetooth positioning method, the UE position is estimated with the knowledge of geographical coordinate of reference Bluetooth beacons. This is accomplished by collecting a certain amount of measurements from UE's Bluetooth receiver, and applying a location determination algorithm using databases of the estimated position's references points. + +The UE measurements can include: + +- Bluetooth beacon's Received Signal Strength (RSSI). + +Two modes are supported for Bluetooth positioning: + +- *Standalone*: in this mode, the UE performs Bluetooth measurements and calculates its own location; + +- *UE-Assisted*: The UE performs Bluetooth measurements without assistance from the network and sends these measurements to the SAS/RNC where the position calculation takes place using a database. + +A UE with Bluetooth capability operates without assistance from the network. + +## 16.1 Information to be transferred between UTRAN elements + +The information that may be signalled from the UE to the network is listed in table 16.1-1. + +**Table 16.1-1: Information that may be transferred from the UE to the network** + +| Information | UE-assisted | Standalone | +|------------------------------------------------------|-------------|------------| +| Bluetooth Location Information | | | +| MAC Address | Yes | No | +| Received Signal Strength (RSSI) | Yes | No | +| Measurement Time Stamp | Yes | No | +| Measurement Characteristics | Yes | No | +| UE Location Information | | | +| UE 3D Position estimate with uncertainty shape | No | Yes | +| Location Time Stamp | No | Yes | +| Location Source (method(s) used to compute location) | No | Yes | + +## 16.2 SAS initiated Bluetooth positioning procedure + +The following describes the signalling for the optional initiation of the network Bluetooth positioning procedure by the SAS. + +![Sequence diagram illustrating Bluetooth methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends Bluetooth measurements request to SRNC, which then sends Bluetooth measurements report or position coordinates report to UE. UE sends Bluetooth measurements report or position coordinates report back to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase is shown with dashed arrows: PCAP Position Periodic Result from SAS to SRNC, Location estimate from SRNC to CN, PCAP Position Periodic Report from SRNC to SAS, PCAP Position Periodic Result from SAS to SRNC, and Location estimate from SRNC to CN. A 'Location Reporting Event N' is indicated. Finally, SAS sends PCAP Position Initiation Resp to SRNC, and SRNC sends Location estimate to CN.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant UE + + Note left of CN: Location request + CN->>SRNC: Location request + SRNC->>SAS: PCAP Position Initiation Req + SRNC->>SAS: PCAP Position Activation Req + SAS->>SRNC: Bluetooth measurements request + SRNC->>UE: Bluetooth measurements request + UE->>SRNC: Bluetooth measurements report or position coordinates report + SRNC->>SAS: PCAP Position Activation Resp + + Note left of CN: Periodic Reporting + SAS-->>SRNC: PCAP Position Periodic Result + SRNC-->>CN: Location estimate + SRNC-->>SAS: PCAP Position Periodic Report + SAS-->>SRNC: PCAP Position Periodic Result + SRNC-->>CN: Location estimate + + Note right of CN: Location Reporting Event N + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>CN: Location estimate + +``` + +Sequence diagram illustrating Bluetooth methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends Bluetooth measurements request to SRNC, which then sends Bluetooth measurements report or position coordinates report to UE. UE sends Bluetooth measurements report or position coordinates report back to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase is shown with dashed arrows: PCAP Position Periodic Result from SAS to SRNC, Location estimate from SRNC to CN, PCAP Position Periodic Report from SRNC to SAS, PCAP Position Periodic Result from SAS to SRNC, and Location estimate from SRNC to CN. A 'Location Reporting Event N' is indicated. Finally, SAS sends PCAP Position Initiation Resp to SRNC, and SRNC sends Location estimate to CN. + +**Figure 16.2-1: Bluetooth methods when initiated by the SAS** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. +2. The SRNC sends parameters received in the location request, including any periodic reporting information, together with the Cell ID and UE capability information to the SAS in a PCAP: Position Initiation Request message via the Iupc interface. +3. Depending on the UE capabilities, the SAS initiates a Bluetooth positioning procedure by sending a PCAP: Position Activation Request message that allows for the use of Bluetooth positioning (along with GPS or OTDOA, and optionally Barometric Pressure, WLAN or TBS positioning methods) via the Iupc interface. The PCAP Position Activation Request message may include periodic reporting information (number of reports and reporting interval). +4. The SRNC forwards to the UE the Bluetooth positioning request received from the SAS using RRC signalling. The SRNC also forwards in the RRC signalling message(s) the SAS request for either Bluetooth measurements, in the case of UE assisted, or a position coordinates, in the case of standalone. The RRC signalling may include a request for periodic reporting as described in subclause 6.6.4.1 if this was received in step 3. For a description of standalone Bluetooth, jump to step 9. +5. For UE assisted Bluetooth, the SRNC requests from the UE the measurement of Bluetooth RSSI. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. + +6. The UE returns to the SRNC the available Bluetooth measurements, together with a time stamp of when these values were obtained. +7. The information obtained in step 6 is sent from the SRNC to the SAS in a PCAP: Position Activation Response message. +8. The SAS calculates the UE position. If periodic reporting was not requested in step 2, the SAS returns the UE position to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +9. In case of standalone method, the UE returns the position estimate to the SRNC via RRC signalling. The SRNC forwards the position estimate to the SAS in a PCAP: Position Activation Response message. This estimate includes the position, the estimated accuracy of the results and the time of the estimate. +10. The SAS may verify the UE position estimate received in step 9 (e.g. using cell ID information). If periodic reporting was not requested in step 2, the SAS returns the resulting estimate to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position estimate to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +11. If there is insufficient information to yield a UE positioning estimate satisfying the requested accuracy, the SAS may start a new process from step 3. +12. The SRNC passes the position estimate received from the SAS to the CN including the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +13. If periodic UE reporting was requested in step 4, the UE continues to send Bluetooth measurement reports one reporting interval after the previous measurement report. The SRNC forward the Bluetooth measurement report information to the SAS in a PCAP Position Periodic Report message. The SAS may calculate the UE position and may verify the calculated UE position estimate or the received UE position estimate (e.g. using cell ID information) and sends the position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 13 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. +14. If periodic UE reporting was not requested in step 4, but was requested in step 2, the SAS may repeat the steps 3 to 12 as for the first request until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. When repeating step 10 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +# --- 17 TBS positioning methods + +## 17.1 General + +Terrestrial Beacon Systems (TBS) is the standard generic term for a network of ground-based transmitters broadcasting signals for geo-spatial positioning with wide-area or regional coverage. The following TBSs are supported in this version of the specification: + +- Metropolitan Beacon Systems (MBS). + +Each TBS can be used individually or in combination with others. When used in combination, the effective number of navigation signals would be increased. + +Two positioning modes are supported: + +- *UE-Assisted*: The UE performs TBS measurements without assistance from the network, and sends these measurements to the SAS where the position calculation takes place, possibly using additional measurements from other (non TBS) sources; +- *Standalone*: The UE performs TBS measurements and calculates its own location, possibly using additional measurements from other (non TBS) sources. + +A UE with TBS capability operates without assistance from the network. + +## 17.2 Information to be transferred between UTRAN Elements + +This subclause defines the information (e.g., position, measurement data) that may be transferred between UTRAN elements. + +### 17.2.1 Information that may be transferred from the UE to SAS + +The information that may be signalled from UE to the SAS/RNC is listed in table 17.2.1-1. + +**Table 17.2.1-1: Information that may be transferred from UE to the SAS** + +| Information | UE-assisted | Standalone | +|-----------------------------------------------------|-------------|------------| +| UE 3D Position estimate with uncertainty shape | No | Yes | +| Timestamp | Yes | Yes | +| Indication of used positioning methods in the fix | No | Yes | +| TBS measurements (code phase (MBS)) | Yes | No | +| Measurement quality parameters for each measurement | Yes | No | + +The TBS information reported from the UE to the SAS depends on the positioning mode (i.e., standalone, or UE-assisted). + +#### 17.2.1.1 Standalone mode + +In standalone mode, the UE reports the latitude, longitude and possibly altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of TBS method used and possibly other positioning methods used to calculate the fix. + +#### 17.2.1.2 UE-assisted mode + +In UE-assisted mode, the UE reports the TBS associated measurements, together with associated quality estimates. These measurements enable the SAS/RNC to calculate the location of the UE, possibly using other measurements and data. + +## 17.3 Location Information Transfer Procedure + +The purpose of this procedure is to enable the SAS/RNC to request TBS measurements or location estimate from the UE, or to enable the UE to provide TBS measurements to the SAS/RNC for position calculation (e.g., in case of basic self location where the UE requests its own location). + +### 17.3.1 SAS initiated TBS positioning procedure + +The following describes the signalling for the optional initiation of the network TBS positioning procedure by the SAS. + +![Sequence diagram illustrating TBS methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends TBS measurements request to SRNC, which then sends it to UE. UE returns TBS measurements report or position coordinates report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase follows, with SRNC sending PCAP Position Periodic Result to SAS, which then sends Location estimate to CN. SRNC also sends PCAP Position Periodic Report to CN. A 'Location Reporting Event N' is shown as a separate block. Finally, SAS sends PCAP Position Initiation Resp to SRNC, which sends Location estimate to CN.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` + +sequenceDiagram + participant CN + participant SAS + participant SRNC + participant UE + + Note left of CN: Location request + CN->>SRNC: Location request + SRNC->>SAS: PCAP Position Initiation Req + SRNC->>SAS: PCAP Position Activation Req + SAS->>SRNC: TBS measurements request + SRNC->>UE: TBS measurements request + UE->>SRNC: TBS measurements report or position coordinates report + SRNC->>SAS: PCAP Position Activation Resp + + Note left of CN: Periodic Reporting + SRNC-->>SAS: PCAP Position Periodic Result + SAS-->>CN: Location estimate + SRNC-->>SAS: PCAP Position Periodic Report + SAS-->>CN: Location estimate + SRNC-->>SAS: PCAP Position Periodic Result + SAS-->>CN: Location estimate + + Note right of CN: Location Reporting Event N + SAS->>SRNC: PCAP Position Initiation Resp + SRNC->>CN: Location estimate + +``` + +Sequence diagram illustrating TBS methods when initiated by the SAS. The diagram shows interactions between CN, SAS, SRNC, and UE. The process starts with a Location request from CN to SRNC. SRNC sends PCAP Position Initiation Req and PCAP Position Activation Req to SAS. SAS sends TBS measurements request to SRNC, which then sends it to UE. UE returns TBS measurements report or position coordinates report to SRNC. SRNC sends PCAP Position Activation Resp to SAS. A 'Periodic Reporting' phase follows, with SRNC sending PCAP Position Periodic Result to SAS, which then sends Location estimate to CN. SRNC also sends PCAP Position Periodic Report to CN. A 'Location Reporting Event N' is shown as a separate block. Finally, SAS sends PCAP Position Initiation Resp to SRNC, which sends Location estimate to CN. + +**Figure 17.3.1-1: TBS methods when initiated by the SAS** + +1. The operation begins with an authenticated request for positioning information about a UE from an application in the core network being received at the SRNC. The request from the CN may be a request for on-demand or periodic reporting. The SRNC acts as interface between the Core Network and the UE Positioning entities in the UTRAN. +2. The SRNC sends parameters received in the location request, including any periodic reporting information, together with the Cell ID and UE capability information to the SAS in a PCAP: Position Initiation Request message via the Iupc interface. +3. Depending on the UE capabilities, the SAS initiates a TBS positioning procedure by sending a PCAP: Position Activation Request message that allows for the use of TBS positioning (along with GPS or OTDOA, and optionally Barometric Pressure or WLAN, Bluetooth positioning methods) to the SRNC via the Iupc interface. The PCAP Position Activation Request message may include periodic reporting information (number of reports and reporting interval). +4. The SRNC forwards to the UE the TBS positioning request received from the SAS using RRC signalling. The SRNC also forwards in the RRC signalling message(s) the SAS request for either TBS measurements, in the case of UE assisted, or a position coordinate, in the case of standalone. The RRC signalling may include a request for periodic reporting as described in subclause 6.6.4.1 if this was received in step 3. For a description of standalone TBS mode, jump to step 9. +5. For UE assisted TBS, the SRNC requests from the UE the TBS measurements. These measurements may be made while the UE is in RRC connected mode CELL\_DCH state. +6. The UE returns to the SRNC the available TBS measurements, together with a time stamp of when these values were obtained. +7. The information obtained in step 6 is sent from the SRNC to the SAS in a PCAP: Position Activation Response message. + +8. The SAS calculates the UE position. If periodic reporting was not requested in step 2, the SAS returns the UE position to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position information to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +9. In case of standalone method, the UE returns the position estimate to the SRNC via RRC signalling. The SRNC forwards the position estimate to the SAS in a PCAP: Position Activation Response message. This estimate includes the position, the estimated accuracy of the results and the time of the estimate. +10. If periodic reporting was not requested in step 2, the SAS returns the resulting estimate to the SRNC in a PCAP: Position Initiation Response message. If periodic reporting was requested in step 2, the SAS forwards the position estimate to the SRNC in a PCAP Position Periodic Result message. The PCAP Position Initiation Response or PCAP Position Periodic Result message may include the positioning method(s) used and an indication of whether the position estimate satisfies the requested accuracy or not. +11. If there is insufficient information to yield a UE positioning estimate satisfying the requested accuracy, the SAS may start a new process from step 3. +12. The SRNC passes the position estimate received from the SAS to the CN including the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. +13. If periodic UE reporting was requested in step 4, the UE continues to send TBS measurement reports one reporting interval after the previous measurement report. The SRNC forward the TBS measurement report information to the SAS in a PCAP Position Periodic Report message. The SAS may calculate the UE position and sends the position information to the SRNC in a PCAP Position Periodic Result message. The SRNC passes the new position estimate to the CN including, if available, the positioning method (or the list of the methods) used to obtain the position estimate. If the CN has requested accuracy for the position estimate, the Location response shall include an indication whether the position estimate satisfies the requested accuracy or not. This step 13 is repeated until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. The SAS may send the final location estimate in a PCAP Position Initiation Response message to the SRNC, and the SRNC forwards the final location information to the CN. +14. If periodic UE reporting was not requested in step 4, but was requested in step 2, the SAS may repeat the steps 3 to 12 as for the first request until the desired amount of reports has been attained or the procedure is cancelled by the CN or UTRAN. When repeating step 10 for the final request, the SAS returns the resulting final position estimate to the SRNC in a PCAP: Position Initiation Response message. + +# --- Annex A (informative): Definitions and Terms + +This annex provides definitions and terms for the general LCS. Not all of these are applicable to the UTRAN environment. + +**CAMEL:** CAMEL is a network functionality, which provides the mechanisms of Intelligent Network to a UE. + +**Current Position:** after a location attempt has successfully delivered a position estimate and its associated time stamp, the position estimate and time stamp is referred to as the 'current position' at that point in time. + +**Deferred location request:** a location request where the location response (responses) is (are) not required immediately. + +**Frequency reference:** the frequency reference of the UE obtained from the UTRAN radio interface that may be used to minimize the frequency search associated with acquiring GPS satellite signals. When the UE acquisition process is aligned to this reference, the carrier Doppler uncertainty that must be searched for a particular satellite signal need only account for minor residual uncertainties related to UE dynamics and initial position. This frequency reference may also be used to maintain the UE's estimate of GPS time between positioning events, thus making accurate GPS time available within the UE to support reacquisition of satellite signals. + +**Global Positioning System:** the Global Positioning System (GPS) consists of three functional elements: Space Segment (satellites), User Segment (receivers), and Control Segment (maintenance etc.). The GPS receiver estimates its own location based on the observed times of arrival of the satellite signals. + +**Immediate location request:** a location request where a single location response only is required immediately. + +**Initial Position:** in the context of an originating emergency call the position estimate and the associated time stamp at the commencement of the call set-up is referred to as 'initial position'. + +**Last Known Position:** the current position estimate and its associated time stamp for Target UE stored in the LCS Server is referred to as the 'last known position' and until replaced by a later position estimate and a new time stamp is referred to as the 'last known position'. + +**LCS (LoCation Services):** LCS is a service concept in system (e.g. GSM or UMTS) standardisation. LCS specifies all the necessary network elements and entities, their functionalities, interfaces, as well as communication messages, due to implement the location service functionality in a cellular network. + +NOTE: LCS does not specify any location based (value added) services except locating of emergency calls. + +**LCS Client:** a software and/or hardware entity that interacts with a LCS Server for the purpose of obtaining location information for one or more UEs. LCS Clients subscribe to LCS in order to obtain location information. LCS Clients may or may not interact with human users. The LCS Client is responsible for formatting and presenting data and managing the user interface (dialogue). The LCS Client may reside in the UE. + +**LCS Client Access barring list:** an optional list of MSISDNs per LCS Client where the LCS Client is not allowed to locate any MSISDN therein. + +**LCS Client Subscription Profile:** a collection of subscription attributes of LCS related parameters that have been agreed for a contractual period of time between the LCS client and the service provider. + +**LCS Feature:** the capability of a PLMN to support LCS Client/server interactions for locating Target UEs. + +**LCS Server:** a software and/or hardware entity offering LCS capabilities. The LCS Server accepts requests, services requests, and sends back responses to the received requests. The LCS server consists of LCS components, which are distributed to one or more PLMN and/or service provider. + +**Local Service:** a service, which can be exclusively provided in the current serving network by a Value added Service Provider. + +**Local Information:** information related to a given location, or general information, which is made available in a given location. + +**Location (Based) Application:** a location application is an application software processing location information or utilising it in some way. The location information can be input by a user or detected by UTRAN or UE. Navigation is one location application example. + +**Location Based Service (LBS):** a service provided either by teleoperator or a 3rd party service provider that utilises the available location information of the terminal. Location Application offers the User Interface for the service. LBS is either a pull or a push type of service (see Location Dependent Services and Location Independent Services). + +**Location Dependent Service:** a service provided either by teleoperator or a 3rd party service provider that is available (pull type) or is activated (push type) when the user arrives to a certain area. It doesn't require any subscription in advance, but the push type activation shall be confirmed by the user. The offered service itself can be any kind of service (e.g. a public Xerox machine or the discount list in a store). + +**Location Independent Service:** a service provided either by teleoperator or a 3rd party service provider that is available and therefore can be activated anywhere in the network coverage. It is activated by the user's request or by other user's activated service, and therefore it requires a subscription in advance (pull type). The offered service itself can be any kind of service (e.g. MMS, SWDL, or LBS!). + +**Position Estimate:** the geographic position of a UE expressed in latitude and longitude data, and optionally altitude data. The Position Estimate shall be represented in a well-defined universal format. Translation from this universal format to another geographic positioning system may be supported, although the details are considered outside the scope of the primitive services. + +**Positioning:** positioning is a functionality, which estimates a geographical position (of e.g. a UE). + +**Positioning method:** a principle and/or algorithm that the estimation of geographical position is based on, e.g. AOA, TOA, TDOA. For example, GPS is based on TOA, and E-OTD (on GSM) or OTDOA (on UMTS) are based on TDOA. + +**Positioning technology:** a technology or system concept including the specifications of RF interfaces, data types, etc. to process the estimation of a geographical position, e.g. GPS, E-OTD (GSM), and IPDL-TDOA (UMTS). + +**PLMN Access barring list:** an optional list of MSISDN per PLMN where any LCS Client is not allowed to locate any MSISDN therein except for certain exceptional cases. + +**Predefined area:** a geographical area that is not related to cell or radio coverage. The UE may take special action when it recognises it has entered or left a predefined area. + +**Privacy Class:** list of LCS Clients defined within a privacy exception class to which permission may be granted to locate the target UE. The permission shall be granted either on activation by the target UE or permanently for a contractual period of time agreed between the target UE and the service provider. + +**Privacy Exception List:** a list consisting of various types of privacy classes (i.e. operator related, personal etc.). Certain types of classes may require agreement between the service provider and the target UE. + +**Prohibited area:** an area where the UE must not activate its transmitter. The Prohibited area may be a Predefined area described above or related to radio cell(s). + +**Subscription Profile:** the profile detailing the subscription to various types of privacy classes. + +**Target UE:** the UE being located. + +**Velocity Estimate:** the speed and direction of a UE expressed as horizontal speed and bearing data, and optionally vertical speed data. + +# Annex B (informative): Reference Model of Functional Entities for UTRAN UE Positioning + +The UTRAN functional entities for UE Positioning are shown in figure B.1 and figure B.2. In these reference models, the LCS clients in the core network communicate with the UTRAN UE Positioning entities across the Iu interface. The RNC LCS Handling Entities and the Positioning Handling Entities work together with the UE to measure and calculate the position information for the requested target UE. These entities within the UTRAN are described in more detail in the following subclauses. + +The figure shows the general arrangement of the UE Positioning function in UTRAN. Communication among these entities makes use of the messaging and signalling capabilities of the UTRAN across the Iu, Iur, Iub, Iupc and Uu interfaces. A LMU is also added to the UTRAN to make measurements as needed by the selected positioning method. + +This figure does not include elements of 3G Core Network, but focuses on those that participate with the UE Positioning functions in the UTRAN. The association of the LCS entities within the Core Network (CN) (e.g. with 3G-MSC or 3G-SGSN) is outside the scope of the present document and is not illustrated in the diagram. + +Within the UTRAN, the UE Positioning Entities may be associated with, or part of the SAS, RNC, the Node B and the UE. Internal LCS Applications may also be part of the RNC and the UE. + +The UE Position Calculation Function (PCF) is logically associated with the SRNC or with the SAS. + +The UE Positioning in UTRAN also makes use of the standardised Iur interface between RNCs, when Node B information, measurements and results are collected. + +The functional model presented in the figure includes functional entities for UE utilising either or both circuit switched (CS) and packet switched (PS) services. This model also supports of all the entities needed for different positioning methods (e.g. network-based, UE-based, UE-assisted, and network assisted (see note 1) methods) exploiting either uplink or downlink measurements. + +NOTE 1: In this approach UE may use the GPS technique but still make use of auxiliary information from the serving network. + +NOTE 2: Figure B.2 shows the SMLC as a node that implements the PCF. In actuality it is more than the PCF, for example, the SMLC can provide GPS assistance data. See Subclause 5.2.5 for the normative definition of an SMLC. + +![Figure B.1: UTRAN UE Positioning Functional Entities (RNC centric mode). The diagram shows the functional entities and their interactions for UE positioning in UTRAN. On the left, the UE (User Equipment) contains LCF, PCF, and PSMF. It is connected via the Uu interface to an External LCS Application (containing LCF) and an LMU (remote) (containing PSMF). The UE is also connected via the Iur interface to the UTRAN LCS Entities. The UTRAN LCS Entities are divided into three main sections: RNC, S-RNC, and Node-B, LMU. The RNC section contains the RNC entity. The S-RNC section contains Handling Entities (LCF, LSOF, LSCF) and Positioning Handling Entities (PCF, PRCF, PRRM). The Node-B, LMU section contains the Node-B, LMU entity. The S-RNC Handling Entities are connected to the RNC via the Iur interface. The S-RNC Positioning Handling Entities are connected to the Node-B, LMU via the Iub interface. The S-RNC Handling Entities are also connected to the Core Network (CN) via the Iu interface. The Core Network (CN) contains LCS Entities (Client, Subscriber) and is connected to the S-RNC Handling Entities via the Iu interface. The CN sends a Location Service Request to the S-RNC and receives a Location Service Response.](96c8d8b0159c47a7478ada46d781060b_img.jpg) + +Figure B.1: UTRAN UE Positioning Functional Entities (RNC centric mode). The diagram shows the functional entities and their interactions for UE positioning in UTRAN. On the left, the UE (User Equipment) contains LCF, PCF, and PSMF. It is connected via the Uu interface to an External LCS Application (containing LCF) and an LMU (remote) (containing PSMF). The UE is also connected via the Iur interface to the UTRAN LCS Entities. The UTRAN LCS Entities are divided into three main sections: RNC, S-RNC, and Node-B, LMU. The RNC section contains the RNC entity. The S-RNC section contains Handling Entities (LCF, LSOF, LSCF) and Positioning Handling Entities (PCF, PRCF, PRRM). The Node-B, LMU section contains the Node-B, LMU entity. The S-RNC Handling Entities are connected to the RNC via the Iur interface. The S-RNC Positioning Handling Entities are connected to the Node-B, LMU via the Iub interface. The S-RNC Handling Entities are also connected to the Core Network (CN) via the Iu interface. The Core Network (CN) contains LCS Entities (Client, Subscriber) and is connected to the S-RNC Handling Entities via the Iu interface. The CN sends a Location Service Request to the S-RNC and receives a Location Service Response. + +Figure B.1: UTRAN UE Positioning Functional Entities (RNC centric mode) + +![Figure B.2: UTRAN UE Positioning Functional Entities – SAS version (RNC centric mode).](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +This diagram illustrates the functional entities for UTRAN UE positioning in RNC centric mode. On the left, an 'External LCS Application' (containing LCF) connects to a 'UE' (containing LCF, PCF, PSMF) via a 'Uu' interface. The 'UE' connects to an 'LMU (remote)' (containing PSMF) via a 'Uu' interface. The 'UE' also connects to the 'UTRAN LCS Entities' via a 'Uu' interface. The 'UTRAN LCS Entities' box contains an 'RNC' at the top, which connects to an 'S-RNC' (containing LCF, LSOF, LSCF) via an 'Iur' interface. The 'S-RNC' connects to 'Positioning Handling Entities' (containing PRCF, PRRM) via an 'Iu' interface. The 'Positioning Handling Entities' connect to 'SMLC' (containing PCF) and 'Node-B, LMU' (containing PSMF) via 'Iux' and 'Iub' interfaces. The 'Core Network (CN)' (containing LCS Entities (Client, Subscriber)) connects to the 'S-RNC' via 'Location Service Request' and 'Location Service Response' messages over an 'Iu' interface. + +Figure B.2: UTRAN UE Positioning Functional Entities – SAS version (RNC centric mode). + +Figure B.2: UTRAN UE Positioning Functional Entities – SAS version (RNC centric mode) + +![Figure B.3: UTRAN UE Positioning Functional Entities – SAS version (SAS centric mode).](64323b705244afc70bf77babdacb6ce5_img.jpg) + +This diagram illustrates the functional entities for UTRAN UE positioning in SAS centric mode. On the left, an 'External LCS Application' (containing LCF) connects to a 'UE' (containing LCF, PCF, PSMF) via a 'Uu' interface. The 'UE' connects to an 'LMU (remote)' (containing PSMF) via a 'Uu' interface. The 'UE' also connects to the 'UTRAN LCS Entities' via a 'Uu' interface. The 'UTRAN LCS Entities' box contains an 'RNC' at the top, which connects to an 'S-RNC' (containing LCF, LSOF, LIRF, LSADF) via an 'Iur' interface. The 'S-RNC' connects to 'Positioning Handling Entities' (containing PRConf, PRRM) via an 'Iu' interface. The 'Positioning Handling Entities' connect to 'System Handling Entities' (containing LSCFS, LSOF) and 'Node-B, LMU' (containing PSMF) via 'IuPC' and 'Iub' interfaces. The 'System Handling Entities' connect to 'Positioning Handling Entities' (containing PRCF, PCF) via an 'Iu' interface. The 'Core Network (CN)' (containing LCS Entities (Client, Subscriber)) connects to the 'S-RNC' via 'Location Service Request' and 'Location Service Response' messages over an 'Iu' interface. + +Figure B.3: UTRAN UE Positioning Functional Entities – SAS version (SAS centric mode). + +Figure B.3: UTRAN UE Positioning Functional Entities – SAS version (SAS centric mode) + +Several functional groupings may be defined to describe the UE Positioning functions. These groupings occur in both the CN and the UTRAN. The overall LCS functional grouping is described in reference [13]. Each grouping encompasses a number of functional components and functions. + +Within UTRAN the functional entities may be grouped as follows: + +- the *Internal Client* group that includes: + - Internal UTRAN Location Client Function (U-LCF); +- the *UTRAN System Handling* group that includes: + +For RNC centric mode: + +- UTRAN Location System Control Function (U-LSCF), + +- UTRAN Location System Operations Function (U-LSOF); + +For SAS centric mode: + +- UTRAN Location Information Relay Function (U-LIRF) +- UTRAN Location System Control Function in SAS (U-LSCFS) +- UTRAN Location System Assistance Data Function (U-LSADF) +- the *UTRAN Positioning* group that includes: + - UTRAN Position Radio Co-ordination Function (U-PRCF), + - UTRAN Position Calculation Function (U-PCF), + - UTRAN Position Signal Measurement Function (U-PSMF), + - UTRAN Position Radio Resource Management (U-PRRM), + - UTRAN Position Related Communication Function (U-PRComF) for SAS centric mode. + +The functions within the UTRAN are described in more detail in the following subclauses. + +## B.1 Internal Client Group + +### B.1.1 Internal UTRAN Location Client Function (U-LCF) + +The UTRAN Location Client Function (U-LCF) represents a logical interface between the internal UTRAN LCS applications and the LCS RNC Handling entities (e.g. the Location System Control Function (U-LSCF) in the RNC). + +NOTE: There is not necessarily a requirement for a LCCF (Location Client Control Function) for the UTRAN Internal Client as is described for external clients in reference [13] (the system stage specification). + +The UTRAN may make use of positioning information for internal operations such as location assisted handover. In such a case, a U-LCF representing the internal UTRAN LCS application may communicate with the U-LSCF to request and receive the positioning information. + +## B.2 UTRAN System Handling group + +### B.2.1 UTRAN Location System Control Function (U-LSCF) + +The UTRAN Location System Control Function (U-LSCF) **in RNC** is responsible for co-ordinating UE Positioning requests within the RNC handling entity. This function manages call-related and non-call-related UE Positioning requests and allocates network resources for handling them. This function "insulates" the Location clients in the Core Network from the detailed operation of the positioning method in order that the UTRAN may be used by several types of core network and with several positioning methods. + +The U-LSCF provides flow control between simultaneous UE Positioning requests. Simultaneous UE Positioning requests must be queued in a controlled manner to account for priority requests (e.g. for Emergency Clients). The details of the flow control, priority selection and queuing are beyond the scope of the present document. + +The U-LSCF will select the appropriate positioning method based on the availability of resources and parameters of the UE Positioning request. The U-LSCF co-ordinates resources and activities needed to obtain data (e.g. Node B geographic co-ordinates) needed for the positioning method. It also records LCS RNC usage data for the location service request that may be passed to a Location System Recording Function (U-LSRF) or OA&M function in the Core Network. + +If the positioning method requires the broadcast of system information, the LSCF initiates and maintains this activity through the Position Radio Co-ordination Function (U-PRCF). Broadcast information (such as the geographic co-ordinates of the Node Bs) may be required, for example, to support a Position Calculation Function (U-PCF) located in the UE. These broadcasts may also include other information (such as currently observable satellites) that may assist a UE in the use of external location services. + +The information to be broadcast is selected based on the positioning methods offered for use by the LCS and the needs of the UE. This broadcast information may be specially coded (i.e. encrypted) to ensure its availability only to subscribers of the service. The use of broadcasts or other methods for signalling to the UE or the LMU may be selected based on the chosen positioning method. + +The information to be broadcast could include, for example: + +- identification and spreading codes of the neighbouring Node Bs (the channels that are used for measurements); +- Relative Time Difference (RTD), i.e. the timing offsets, asynchronicity between Node Bs, could be obtained from measurement results obtained by LMUs; +- roundtrip delay estimates in connected mode; +- the geographic position, co-ordinates, of the neighbouring Node Bs; +- the idle period places within the frame structure for multiple Node Bs; +- the local time-of-day. + +Some of this information may be broadcast to support other UTRAN operations (e.g. handover). The function of the LSCF is to ensure information is broadcast when needed for the LCS operations and the LSCF may make use of other UTRAN processes to do so. + +### B.2.2 UTRAN Location System Operations Function (U-LSOF) + +The UTRAN Location System Operations Function (U-LSOF) is responsible for provisioning of data, positioning capabilities, data related to clients and subscription (LCS client data and UE data), fault management and performance management of LCS within the RNC. + +An LSOF may be associated with each entity. The LSOF interacts with Internal (OAM) Clients for administration and maintenance of the data. + +The Iur interface may pass messages relating to changes or reporting of the data associated with the LSOF in the RNC. + +The Iub interface may pass messages relating to changes or reporting of the data associated with the LSOF in the Node B or the LMU. + +The Uu interface may pass messages relating to changes or reporting of the data associated with the LSOF in the UE or the remote LMU. When the SAS is present, with either RNC or SAS centric mode, the U-LSOF may be split across SAS and SRNC. + +### B.2.3 UTRAN Location Information Relay Function (U-LIRF) + +The UTRAN Location Information Relay Function (U-LIRF) is responsible for forwarding of Location Requests from the LCS clients to the U-LSCFS and for forwarding of UE positioning estimates to the requesting LCS client. The U-LIRF also interfaces with the U-LSOF to obtain provisioned location information. + +The U-LIRF communicates with the U-LSADF to handle assistance data requests received from the CN. The U-LIRF also forwards the UE positioning capability information and a coarse position estimate to the U-LSCFS. + +### B.2.4 UTRAN Location System Control Function in SAS (U-LSCFS) + +The UTRAN Location System Control Function in SAS (U-LSCFS) is only used in the SAS centric mode. It performs similar tasks as the U-LSCF in the RNC centric mode, but instead of communicating directly with the LCS clients, it communicates with the U-LIRF in the SRNC. + +### B.2.5 UTRAN Location System Assistance Data Function (U-LSADF) + +The UTRAN Location System Assistance Data Function (U-LSADF) is responsible for the handling location related assistance data within the RNC. This includes handling of location related assistance data requests from the CN and the broadcasting of location related assistance data, if requested by the U-LSCFS. + +## B.3 Positioning group + +### B.3.1 UTRAN Position Radio Co-ordination Function (U-PRCF) + +The UTRAN Position Radio Co-ordination Function (U-PRCF) manages a UE Positioning for a UE through overall co-ordination and scheduling of resources to perform positioning measurements. This function interfaces with the U-PSMF, the U-PRRM and the U-PCF. The U-PRCF determines the positioning method to be used based on the UE Positioning request, the QoS, the capabilities of the UTRAN, and the UE's capabilities. The U-PRCF also manages the needed radio resources through the U-PRRM. It determines which U-PSMFs are to be involved, what to measure, and obtains processed signal measurements from the U-PSMF. + +Some positioning methods may involve measurements made at the UE. In this case the U-PRCF interfaces with the UE to obtain the measurements (or the positioning results if they have been determined by the UE). Some positioning methods may involve measurements or information from several sources, including radio units at several Node B (or other LMU) and involve a series of transmissions and receptions. The U-PRCF entity also provides ancillary measurements in case of network-assisted positioning method. Ancillary information may be extracted from navigating systems like GPS. + +The U-PRCF forwards the signal measurement data to the U-PCF. + +It is the function of the U-PRCF to co-ordinate the sequence of activities and compensate for failures (if they occur) to provide the position estimate. In SAS centric mode the U-PRCF communicates to LMU, NodeB and UE via the U-PRComF. + +### B.3.2 UTRAN Position Calculation Function (U-PCF) + +The UTRAN Position Calculation Function (U-PCF) is responsible for calculating the position of the UE. This function applies an algorithmic computation on the collected signal measurements to compute the final position estimate and accuracy. + +The U-PCF may also support conversion of the position estimate between different geographic reference systems. It may obtain related data (e.g.: Node B geographic co-ordinates) needed for the calculation. There may be more than one calculating function available within, or associated with, the calculation function of the UTRAN. + +In the cell ID based positioning method, the U-PCF shall determine the geographical co-ordinates corresponding to the cell(s) associated with the target UE. + +The PCF is also responsible for estimating the accuracy of the position estimate. This accuracy estimate should include, for example, the effect of geometric dilution of precision (GDOP), the capabilities of the signal measuring hardware, the effects of multipath propagation and the effects of timing and synchronisation unknowns. The accuracy should be returned as a measure of distance in the same units as the position estimate. The accuracy zone may be reported as the axis and orientation of an ellipse surrounding the position estimate. + +### B.3.3 UTRAN Position Signal Measurement Function (U-PSMF) + +The UTRAN Position Signal Measurement Function (U-PSMF) is responsible for performing and gathering uplink or downlink radio signal measurements for use in the calculation of a UE position. These measurements can be positioning related or ancillary. + +There may be one or more PSMF within a UTRAN and they may be located at the UE, the Node B, or a separate LMU. The PSMF, generally, may provide measurement of signals (i.e. satellite signals) in addition to measurements of the UTRA radio transmissions. The measurements to be made will depend on the selected positioning method. + +### B.3.4 UTRAN Position Radio Resource Management (U-PRRM) + +The UTRAN Position Radio Resource Management (U-PRRM) entity is responsible for managing the effect of LCS operations on the overall performance of the radio network. This may ensure, for example, that the operation of the U-PSMF does not degrade the QoS of other calls. The U-PRRM handles following functions: + +- controlling the variation of the UL and DL signal power level due to the LCS application; +- calculating the DL and UL power/interference due to UE positioning operations; + +- to admit/reject the new LCS requests; +- co-operating with Admission Control, and entities of the RRM (such as power control) to provide the system stability in terms of radio resources; +- controlling the RTD obtaining mechanism. It may also forward the results of the UTRAN GPS timing of cell frames or SFN-SFN Observed Time Difference (or any similar timing parameter) measurements to the PRCF (or PCF); +- controlling the IPDL mechanism for positioning measurements. This may include the overall control of the periodical measurement fulfilment. Co-ordination among RNCs (e.g. to assure non-overlapping idle periods) will be communicated through the Iur interface. + +### B.3.5 UTRAN Position Related Communication Function (U-PRComF) + +The UTRAN Position Related Communication Function (U-PRComF) manages the collection of positioning measurements as requested by the U-PRCF. + +The U-PRComF terminates the NBAP protocol for positioning related measurements requested from NodeB or LMU. + +The U-PRComF terminates the RRC protocol for positioning related measurements requested from the UE. + +## B.4 Assignment of LCS Functional Entities to UTRAN Elements + +Figure B.1, Figure B.2, Figure B.3 and tables B.1 and B.2 show the generic configuration for different positioning methods, including network-based, UE-based, UE-assisted and network-assisted methods. With this approach both UTRAN and the UE are able to measure the timing of signals and compute the UE position estimate. Depending on the applied positioning method it is possible to utilise the corresponding configuration containing all needed entities. For instance, if a network-based positioning method is applied, the entities that are involved in measuring the UE's signal and calculating its position estimate are allocated to the network elements of the access stratum. On the other hand, in case UE-based or network-assisted methods are used these entities should be allocated to the UE. + +**Table B.1: Example Allocation of LCS Functional Entities to Network Elements for RNC centric mode** + +| UTRAN | UE | Node B | LMU | RNC | SAS | +|-------|----|--------|-----|-----|-----| +| LCF | X | | | X | | +| LSCF | | | | X | | +| PRCF | | | | X | | +| PCF | X | | | X | X | +| PRRM | | | | X | | +| PSMF | X | X | X | | | +| LSOF | X | X | X | X | | + +**Table B.2: Example Allocation of LCS Functional Entities to Network Elements for SAS centric mode** + +| UTRAN | UE | Node B | LMU | RNC | SAS | +|--------|----|--------|-----|-----|-----| +| LCF | X | | | X | | +| LSCFS | | | | | X | +| LIRF | | | | X | | +| PRCF | | | | | X | +| PCF | X | | | | X | +| PRRM | | | | X | | +| PSMF | X | X | X | | | +| LSOF | X | X | X | X | X | +| PRComF | | | | X | | + +# --- Annex C (informative): Location Services Categories + +Generally there are four categories of usage of the location service: + +- the **Commercial LCS** (or **Value Added Services**); +- the **Internal LCS**; +- the **Emergency LCS**; +- the **Lawful Intercept LCS**. + +These location services categories are further defined in [13] and [5]. + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 12/1999 | RP-06 | RP-99635 | - | | | Approved at TSG-RAN #6 and placed under Change Control | 3.0.0 | +| 03/2000 | RP-07 | RP-000038 | 001 | 3 | | Network assisted GPS LCS | 3.1.0 | +| | RP-07 | RP-000038 | 002 | 1 | | Enhancements for cell coverage based positioning | 3.1.0 | +| | RP-07 | RP-000038 | 003 | | | Replacement for Figure 4.1 | 3.1.0 | +| | RP-07 | RP-000038 | 004 | 1 | | Restructuring | 3.1.0 | +| | RP-07 | RP-000038 | 006 | | | Target UE-RNC signalling model | 3.1.0 | +| | RP-07 | RP-000038 | 007 | | | LMU description | 3.1.0 | +| | RP-07 | RP-000038 | 008 | 2 | | LMU signalling description | 3.1.0 | +| | RP-07 | RP-000038 | 009 | | | Incorporation of R1 Liaisons R2-000022 and R2-000023 | 3.1.0 | +| | RP-07 | RP-000038 | 010 | 3 | | OTDOA - GPS Location Procedures | 3.1.0 | +| | RP-07 | RP-000038 | 011 | 1 | | Clarification of the different LMU types | 3.1.0 | +| 06/2000 | RP-08 | RP-000218 | 013 | 2 | | Modifications to LCS text on cell-ID method | 3.2.0 | +| | RP-08 | RP-000218 | 015 | | | Editorial modifications of OTDOA descriptions for alignment with TDD | 3.2.0 | +| | RP-08 | RP-000218 | 016 | | | Update on clause 5 | 3.2.0 | +| | RP-08 | RP-000218 | 017 | 1 | | Editorial additions | 3.2.0 | +| | RP-08 | RP-000218 | 018 | | | Clarification of OTDOA signalling operation | 3.2.0 | +| | RP-08 | RP-000218 | 019 | 1 | | Assisted GPS procedures | 3.2.0 | +| 09/2000 | RP-09 | RP-000356 | 020 | | | Alignment of FDD and TDD positioning methods and editorial changes | 3.3.0 | +| | RP-09 | RP-000356 | 021 | 3 | | Assisted GPS Procedures | 3.3.0 | +| | RP-09 | RP-000356 | 022 | 2 | | TDD/FDD alignment of OTDOA and GPS assisted positioning methods | 3.3.0 | +| | RP-09 | RP-000356 | 023 | | | Clean-up | 3.3.0 | +| | RP-09 | RP-000356 | 024 | | | Corrections from LCS Ad Hoc | 3.3.0 | +| 12/2000 | RP-10 | RP-000566 | 025 | 1 | | Editorial and Minor Technical Clean-up | 3.4.0 | +| | RP-10 | RP-000566 | 026 | | | Editorial corrections | 3.4.0 | +| | RP-10 | RP-000566 | 027 | | | Removal of SoLSA concepts | 3.4.0 | +| | RP-10 | RP-000566 | 029 | 1 | | Signalling flows on Iub and Iur | 3.4.0 | +| | RP-10 | RP-000566 | 030 | 1 | | LCS functionality during SRNS relocation | 3.4.0 | +| | RP-10 | RP-000566 | 031 | | | UE Search Correction from R2-001721 (CR 021r3) | 3.4.0 | +| | RP-10 | RP-000566 | 032 | 2 | | Signaling Between RNC and Stand-Alone LMU | 3.4.0 | +| | RP-10 | RP-000566 | 033 | 5 | | Use of RTT measurements in the Assisted GPS procedure | 3.4.0 | +| | RP-10 | RP-000566 | 034 | 1 | | LCS assistance data delivery | 3.4.0 | +| | RP-10 | RP-000566 | 035 | 2 | | Description for frequency reference | 3.4.0 | +| | RP-10 | RP-000566 | 036 | 2 | | Editorial clean-up | 3.4.0 | +| | RP-10 | RP-000566 | 038 | 2 | | Clarification on information to be transferred between UTRAN nodes | 3.4.0 | +| | RP-10 | RP-000566 | 039 | 1 | | Moving of semantic descriptions from RRC | 3.4.0 | +| 03/2001 | RP-11 | RP-010023 | 040 | | | Correction to Assistance Data Delivery procedure | 3.5.0 | +| | RP-11 | RP-010023 | 041 | 1 | | Clarification of assisted GPS related parameters | 3.5.0 | +| | RP-11 | RP-010023 | 042 | | | Clarification of paging initiation | 3.5.0 | +| | RP-11 | RP-010023 | 045 | 1 | | Editorial Corrections | 3.5.0 | +| | RP-11 | RP-010023 | 046 | 1 | | Clarification of Timing Assistance | 3.5.0 | +| | RP-11 | RP-010023 | 047 | | | Clarification of Integrity Monitor Function | 3.5.0 | +| | RP-11 | RP-010040 | 048 | 1 | | Introduction of IPDLs for TDD | 4.0.0 | +| | RP-11 | RP-010044 | 044 | 4 | | Support of Stand-Alone A-GPS SMLC over an open interface | 5.0.0 | +| 06/2001 | RP-12 | RP-010306 | 053 | | | Removal of positioning request transfer during SRNS relocation | 5.1.0 | +| | RP-12 | RP-010325 | 054 | | | Iupc architectural aspects modifications | 5.1.0 | +| | RP-12 | RP-010325 | 055 | | | Removal of RAN3 dependency w.r.t. PCAP signalling flows | 5.1.0 | +| | RP-12 | RP-010325 | 056 | 1 | | PCAP message flows | 5.1.0 | +| 09/2001 | RP-13 | RP-010556 | 060 | 1 | | Support for all Rel. 4 positioning methods in standalone SMLC | 5.2.0 | +| 12/2001 | RP-14 | RP-010757 | 065 | | | Correction of broadcast of assistance data | 5.3.0 | +| | RP-14 | RP-010757 | 072 | | | Migration of Descriptive Text from TS 25.331 | 5.3.0 | +| | RP-14 | RP-010770 | 062 | | | Correction of RTD usage in TDD | 5.3.0 | +| 03/2002 | RP-15 | RP-020080 | 074 | | | Corrections Relating to IPDL and Timing Advance for 1.28 Mcps TDD | 5.4.0 | +| | RP-15 | RP-020065 | 081 | 1 | | Correction to CELL ID positioning when UE is not reachable | 5.4.0 | +| | RP-15 | RP-020090 | 075 | | | Including IPDL, UE Timing Advance and Angle of Arrival for 1.28 Mcps TDD | 5.4.0 | +| 03/2003 | RP-19 | RP-030110 | 085 | | | Update to figure 5.1, LMU terminology | 5.5.0 | +| 06/2003 | RP-20 | RP-030290 | 088 | | | Handling of UP assistance data | 5.6.0 | +| | RP-20 | RP-030300 | 089 | | | Addition of Position Method Used, to attributes returned with position estimate | 5.6.0 | +| 09/2003 | RP-21 | RP-030481 | 092 | | | Correction to UE Positioning privacy procedures | 5.7.0 | +| | RP-21 | RP-030481 | 095 | | | Alignment with 25.331 regarding A-GPS assistance data | 5.7.0 | +| | RP-21 | RP-030481 | 098 | | | UE positioning support in the UE | 5.7.0 | +| 12/2003 | RP-22 | RP-030613 | 101 | 2 | | Correction to Location Reporting procedure | 5.8.0 | +| | RP-22 | - | - | | | Upgrade to Release 6 - no technical change | 6.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------|--------| +| 06/2004 | RP-24 | RP-040209 | 103 | | | Corrections to time stamp in position information report and to SRNC relocation | 6.1.0 | +| | RP-24 | RP-040216 | 104 | | | Indication of achieved accuracy in position estimate | 6.1.0 | +| 06/2005 | RP-28 | RP-050330 | 0105 | | | Addition of the U-TDOA location method to the UTRAN | 7.0.0 | +| 09/2005 | RP-29 | RP-050478 | 0106 | | | Enabling the Providing of Velocity | 7.1.0 | +| | RP-29 | RP-050619 | 0107 | 1 | | Harmonization with the Stage 3 specification (TS 25.453) and addition of TDD functionality for the U-TDOA positioning method | 7.1.0 | +| 03/2006 | RP-31 | RP-060098 | 0108 | | | 7.68 Mpcs TDD Option (Release 7) | 7.2.0 | +| 06/2006 | RP-32 | RP-060356 | 0109 | | | Introducing A-GNSS in UTRAN | 7.3.0 | +| | RP-32 | RP-060357 | 0110 | | | Addition of Periodic Location Procedures | 7.3.0 | +| 09/2007 | RP-37 | RP-070577 | 0111 | | | SAS-Centric A-GPS - UE requesting additional Assistance Data | 7.4.0 | +| 12/2007 | RP-38 | - | - | | | Upgrade to the Release 8 - no technical change | 8.0.0 | +| 12/2008 | RP-42 | RP-081029 | 0112 | - | | Support for additional navigation satellite systems in UTRAN | 8.1.0 | +| 12/2009 | RP-46 | - | - | | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 09/2010 | RP-49 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| | RP-49 | RP-100864 | 0119 | 1 | | Support of RF Pattern Matching in UTRAN | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | +| 12/2013 | RP-62 | RP-131997 | 0122 | 1 | | Introduction of BDS in UTRAN | 12.0.0 | +| 12/2014 | RP-66 | RP-142119 | 0123 | - | | BDS Satellite Specific ICD update to version 2.0 | 12.1.0 | +| | RP-66 | RP-142140 | 0124 | - | | Cleanup corrections on abbreviations | 12.1.0 | +| 12/2015 | RP-70 | RP-152109 | 0125 | 3 | | RAT-Independent positioning enhancements | 13.0.0 | +| 03/2017 | RP-75 | - | - | | | Upgraded to Release 14 - no technical change | 14.0.0 | +| 06/2018 | RP-80 | - | - | | | Upgraded to Release 15 - no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25367/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/25_series/25367/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd3292761b7500e920e0e0770af1983f1b083a47 --- /dev/null +++ b/marked/Rel-16/25_series/25367/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:584187376ce3320e3b0fc9d6edeac1c0ccd1f2bf4afa3047b8f696a8f667e9bd +size 77939 diff --git a/marked/Rel-16/25_series/25367/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/25_series/25367/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cc724dee8bfd5178fb72d054aedb3bd158c92b2 --- /dev/null +++ b/marked/Rel-16/25_series/25367/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45ac94ceee3c667d854fd716374f255411292fdeab00e6d0b7a051a28c1d21f8 +size 52193 diff --git a/marked/Rel-16/25_series/25367/raw.md b/marked/Rel-16/25_series/25367/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..632ad0ea4dad749eed37889421c9d5e315cd0de5 --- /dev/null +++ b/marked/Rel-16/25_series/25367/raw.md @@ -0,0 +1,432 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Overview..... | 7 | +| 5 CSG Identification ..... | 8 | +| 6 CSG Selection..... | 8 | +| 6.1 Manual CSG ID Selection..... | 8 | +| 7 CSG Cell Reselection..... | 9 | +| 7.1 Measurement Rules for CSG Cells ..... | 9 | +| 7.2 Reselection to CSG Cell..... | 9 | +| 7.2.1 Criteria for Intra-frequency Cell Reselection..... | 9 | +| 7.2.2 Criteria for Inter-frequency Cell Reselection..... | 9 | +| 7.2.3 Criteria for Inter-RAT Cell Reselection..... | 9 | +| 7.3 Reselection from CSG Cell ..... | 9 | +| 7.3.1 Criteria for Intra-frequency Cell Reselection..... | 9 | +| 7.3.2 Criteria for Inter-frequency Cell Reselection..... | 9 | +| 7.3.3 Criteria for Inter-RAT Cell Reselection..... | 9 | +| 7.4 Reselection from CSG Cell to CSG Cell ..... | 10 | +| 7.5 Parameters for CSG Cell Reselection ..... | 10 | +| 8 CSG and Hybrid Cell Handover ..... | 10 | +| 8.1 Handover to CSG/Hybrid Cell ..... | 10 | +| 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure ..... | 11 | +| 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure ..... | 12 | +| 8.2 Handover from CSG Cell..... | 13 | +| 8.3 Handover from CSG Cell to CSG Cell ..... | 13 | +| 9 Support of Hybrid Cells ..... | 13 | +| 9.1 Measurement Rules..... | 13 | +| 9.2 Reselection ..... | 13 | +| Annex B (informative): Void..... | 14 | +| Annex C (informative): Change history..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This document provides a high level description of the mobility procedures applicable to Home NodeB support in the current Release. Where appropriate, the reasons behind the agreements are provided. Throughout this document, unless otherwise stated, the UE is assumed to be a current Release UE that supports the Closed Subscriber Group (CSG) feature, whether it is actually a member of a CSG or not. A UE that does not support the CSG feature is not required to support any of the procedures stated in this document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.304: "UE procedures in idle mode and procedures for cell reselection in connected mode". +- [3] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [4] 3GPP TS 23.011: "Service accessibility". +- [5] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs". +- [6] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB)". +- [7] 3GPP TS 25.214: "Physical layer procedures (FDD)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Acceptable Cell:** A cell that satisfies certain conditions as specified [2]. A UE can always attempt emergency calls on an acceptable cell. + +**CSG whitelist:** A list provided by NAS containing all the CSG Identities of the CSGs to which the subscriber belongs. + +NOTE: This list is known as Allowed CSG List in Rel-8 Access Stratum specifications. + +**Available PLMN:** A PLMN for which the UE has found at least one cell and read its PLMN identity. + +**Barred Cell:** A cell a UE is not allowed to camp on. + +**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information. + +**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity. + +**Closed Subscriber Group (CSG):** A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells). + +**CSG Cell:** A cell, part of the PLMN, broadcasting a CSG Indicator that is set to TRUE and a specific CSG identity. A CSG cell is accessible by the members of the closed subscriber group for that CSG identity. + +**CSG Identity (CSG ID):** An identifier broadcast by a CSG/Hybrid cell or cells and used by the UE to facilitate access for authorised members of the associated Closed Subscriber Group. + +**CSG member cell:** A cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity. + +**DRX cycle:** Individual time interval between monitoring Paging Occasion for a specific UE. + +**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, MBSFN Cluster selection MBSFN Cluster reselection and handover according to the information provided by the NAS. + +**Home NodeB (HNB):** A HNB is a customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a mobile operator's network using broadband IP backhaul. + +**HNB Name:** The Home NodeB Name is a broadcast string in free text format that provides a human readable name for the Home NodeB CSG identity. + +**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI. + +**Hybrid cell:** A cell broadcasting a CSG identity which is accessible as a CSG cell by UEs which are members of the CSG and as a normal cell by all other UEs. + +**Non-CSG Cell:** A cell that is not a CSG cell, e.g. a macro cell. + +**Process:** A local action in the UE invoked by a RRC procedure or an Idle Mode procedure. + +**Radio Access Mode:** Radio access mode of the cell, FDD or TDD. + +**Radio Access Technology:** Type of technology used for radio access, for instance UTRA or GSM. + +**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred. + +**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure. + +**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information. + +**Restricted Cell:** A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred. + +**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically. + +**Serving cell:** The cell on which the UE is camped. + +**Strongest cell:** The cell on a particular carrier that is considered strongest according to the layer 1 cell search procedure [7]. As the details of the layer 1 cell search are implementation dependent, the precise definition of 'strongest cell' is also implementation dependent. + +**Suitable Cell:** This is a cell on which an UE may camp. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|---------------------------| +| AS | Access Stratum | +| BCCH | Broadcast Control Channel | +| CM | Connection Management | +| CN | Core Network | +| CSG | Closed Subscriber Group | + +| | | +|--------|--------------------------------------------| +| DRX | Discontinuous Reception | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| FDD | Frequency Division Duplex | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile Communications | +| HCS | Hierarchical Cell Structure | +| HNB | Home NodeB | +| IMSI | International Mobile Subscriber Identity | +| MCC | Mobile Country Code | +| MM | Mobility Management | +| MNC | Mobile Network Code | +| NAS | Non-Access Stratum | +| PCH | Paging Channel | +| PI | Page Indicator | +| PICH | Page Indication Channel | +| PLMN | Public Land Mobile Network | +| RAT | Radio Access Technology | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| TDD | Time Division Duplex | +| TMGI | Temporary Mobile Group Identity | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Overview + +A Home NodeB may provide restricted access to only UEs belonging to a Closed Subscriber Group (CSG). One or more of such cells providing restricted access, known as CSG cells, are identified by a unique numeric identifier called CSG Identity. To facilitate access control, a UE with CSG subscription would have an CSG whitelist, which contains one or more CSG Identities associated with the CSG cells on which the UE is allowed access. The UE uses the CSG whitelist along with the CSG Identity and associated PLMN ID broadcast by the CSG Cells in CSG cell selection and reselection. + +A HNB can also be operated as a hybrid cell. A hybrid cell is accessed as a CSG cell by a UE whose CSG whitelist contains the cell's CSG ID and associated PLMN ID and as a normal cell by all other UEs. Members of the CSG are expected to receive preferential access according to [5]. + +NOTE: Although pre-Rel-9 UEs are able to camp on hybrid cells (which would be regarded as normal cells for access) there is no possibility for these UEs to identify a hybrid cell as a CSG cell even though the cell's CSG identity and associated PLMN ID are in the UE's CSG whitelist. + +In addition, manual selection of CSG Identity is introduced, which enables the human user to manually select a CSG Identity for UE to camp on. + +This document provides high level descriptions and procedures of the mobility features to support CSG deployment in the current Release. The following areas will be covered in the subsequent chapters: + +- Identifiers associated with the CSG framework +- Manual selection of CSG Identity +- Measurement rules for CSG Cells +- Cell reselection to a CSG cell, from a CSG cell, and between CSG cells +- Handover to a CSG cell, from a CSG cell, and between CSG cells, where applicable +- Measurement rules, (re)selection and handover procedures for hybrid cells. + +# --- 5 CSG Identification + +One or more Closed Subscriber Group (CSG) cells are identified by a unique numeric identifier called CSG Identity or CSG ID. A UE belonging to a CSG has the corresponding CSG ID and associated PLMN ID in its CSG whitelist. The CSG whitelist is maintained and provided by NAS. The CSG ID is broadcast in system information by the CSG cell or hybrid cell, and used by the UE for cell (re)selection and handover purposes. + +A cell may optionally broadcast the CSG Indicator, whose presence and value of TRUE indicates the cell is a CSG cell. The absence of the CSG indicator in a cell which broadcasts a CSG identity indicates that it is a hybrid cell. + +A CSG cell or hybrid cell may broadcast the HNB Name, a textual identifier, in system information. The HNB Name can be used to aid the human user in manual selection of a CSG ID. + +At the physical layer, a CSG cell is identified by its carrier frequency (UARFCN) and Primary Scrambling Code (PSC). A set of PSCs could be reserved for CSG deployment and this reserved PSC range may be signalled in system information. The PSC of a CSG cell belongs to the reserved PSC range if broadcast. + +On the mixed carrier frequency shared by both non-CSG cells (UMTS macro cells) and CSG cells, CSG cells broadcast in system information the PSC range reserved by the network for CSG cells. The non-CSG cells may also broadcast the reserved PSC range. The reserved PSC range is only applicable to the UARFCN within the PLMN where the UE received this information. The UE considers the last received reserved PSC range to be valid within the entire PLMN for the duration of 24 hours. The UE may use the reserved PSC information for CSG cell search and (re)selection purposes, according to UE's implementation. + +NOTE: In shared network scenario, aligned PSC ranges are beneficial in the shared carrier frequency across the involved PLMNs. Furthermore, in deployments where cells broadcast different primary PLMN (with or without multiple PLMN IDs), it is beneficial that CSG and non-CSG cells will broadcast same PSC ranges. Moreover, it is beneficial if a CSG cell, if listed in system information and associated with a PLMN, is associated with the primary PLMN of the serving cell. + +Non-CSG cells and CSG cells may broadcast indications of one or more carrier frequencies used for dedicated CSG deployment. This information may be used by a UE to avoid unnecessary measurements on that frequency even when cell measurement rules would require measurements of this carrier frequency. Indications of which carrier frequencies are dedicated to CSG-only deployment may be signalled in system information and are applicable only in the cell where this information is broadcast. + +# --- 6 CSG Selection + +## 6.1 Manual CSG ID Selection + +Manual CSG ID selection enables a human user to select a CSG ID. In manual CSG ID selection the UE may scan all frequencies in the supported frequency bands and display a list of found CSG IDs or the corresponding HNB Names if broadcast by the CSG cells or hybrid cells, and indications as to whether the found CSG IDs and associated PLMN IDs are contained in the UE's CSG whitelist. When the user selects an entry in the list, the UE selects any CSG cell or hybrid cell among the ones with same CSG ID and PLMN ID. The UE may normally camp on the chosen cell if it is a CSG member cell or a hybrid cell. + +During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell that is not a CSG member cell. + +Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE's CSG whitelist is updated. + +The UE is allowed to *not* support manual CSG ID selection in connected mode. + +# --- 7 CSG Cell Reselection + +## 7.1 Measurement Rules for CSG Cells + +To measure CSG member cell(s), a UE applies an autonomous search function, per UE implementation, regardless of which RAT the UE is camping on. The autonomous search function determines when and where to search for the CSG member cells. + +Autonomous search procedure is disabled by the search function if UE's CSG whitelist does not exist or is empty. + +On a mixed carrier, a UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells. + +A UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells on the carrier frequency dedicated to CSG deployment. + +## 7.2 Reselection to CSG Cell + +The cell reselection criteria described in this section is applicable when the UE is in the following call states: Idle Mode, Cell\_PCH, URA\_PCH and Cell\_FACH states, unless otherwise stated. + +Inter-RAT and inter-frequency reselection in CELL\_FACH state only needs to be performed when second DRX is used. + +### 7.2.1 Criteria for Intra-frequency Cell Reselection + +For intra-frequency reselection from a non-CSG cell to a CSG member cell, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. The UE may ignore not allowed CSG cells in the ranking. The UE applies reselection parameters broadcast by the serving cell. A UE may normally camp on a CSG member cell. + +### 7.2.2 Criteria for Inter-frequency Cell Reselection + +For inter-frequency cell reselection, the UE considers the frequency where its CSG member cell is on to have the highest priority value, irrespective of network configured frequency priorities, as long as the CSG member cell remains best ranked on that frequency. + +### 7.2.3 Criteria for Inter-RAT Cell Reselection + +Inter-RAT reselection to a CSG member cell is supported when the UE is camped on another RAT. The UE requirements are defined in the specifications of the concerned RAT. + +## 7.3 Reselection from CSG Cell + +### 7.3.1 Criteria for Intra-frequency Cell Reselection + +For intra-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2]. + +### 7.3.2 Criteria for Inter-frequency Cell Reselection + +For inter-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2]. + +### 7.3.3 Criteria for Inter-RAT Cell Reselection + +For reselection from a CSG cell to a GSM or E-UTRA cell, the UE follows the respective procedures defined in [2]. + +## 7.4 Reselection from CSG Cell to CSG Cell + +For reselection between CSG member cells, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. + +## 7.5 Parameters for CSG Cell Reselection + +No new parameters are defined for CSG cell ranking. The same cell reselection parameters defined for the UTRA case in [2] are used for CSG cell ranking purposes, if configured. The operator may configure the cell reselection parameters, such as Qoffset and Qhyst, to bias the reselection of CSG cells. + +# --- 8 CSG and Hybrid Cell Handover + +## 8.1 Handover to CSG/Hybrid Cell + +Handover to a HNB/HeNB follows the framework as specified in [3], [6]. Handover to a HNB/HeNB is different from the normal handover procedure in four aspects: + +1. **Proximity Estimation:** in case the UE is able to determine, based on UE implementation, that it is near a CSG member cell, the UE may provide to the SRNC an indication of proximity. The CSG proximity indication may be used as follows: + - a. If a measurement configuration is not present for the concerned frequency/RAT, the SRNC may configure the UE to perform measurements and reporting for the concerned frequency/RAT. + - b. The SRNC may determine whether to perform other actions related to handover to HNB/HeNBs based on having received a proximity indication (for example, the SRNC may not configure compressed mode gaps for the UE to detect the HNB/HeNB on a different frequency/RAT unless it has received a proximity indication). +2. **PSC/PCI Confusion:** due to the typical cell size of HNB/HeNBs being much smaller than macro cells, there can be multiple HNBs/HeNBs within the coverage of the SRNC that have the same PSC/PCI. This leads to a condition referred to as PSC/PCI confusion, wherein the SRNC is unable to determine the correct target cell for handover from the PSC/PCI included in the measurement reports from the UE. PSC/PCI confusion is solved by the UE reporting the cell identity of the target HNB/HeNB. +3. **Access Control:** If the target cell is a hybrid cell, prioritization of allocated resources may be performed based on the UE's membership status. Access control is done by a two step process, where first the UE reports whether the target cell is a CSG member cell based on the UE's CSG whitelist, and then the network verifies the reported status. +4. **PLMN Report:** If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. + +Mobility from SRNC to a CSG/hybrid cell from network perspective is described in [6]. The following two sections describe the radio aspects. The SRNC in the call flows of these sections can be an RNC or a HNB. + +### 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure + +![Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + Note right of SRNC: 5. Handover processing [6] + SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)] + UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication] + SRNC->>UE: 3. MEASUREMENT CONTROL [(CSG Intrafrequency cell info), (Intra-frequency SI Acquisition)] + UE-->>SRNC: 4. MEASUREMENT REPORT [PSC, Cell Identity, CSG Member Indication] + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC). The process begins with the SRNC sending a 'MEASUREMENT CONTROL' message to the UE, specifying 'CSG Proximity detection' as the measurement type. The UE responds with a 'MEASUREMENT REPORT' containing a 'CSG Proximity Indication'. Upon receiving this, the SRNC sends another 'MEASUREMENT CONTROL' message, this time providing 'CSG Intrafrequency cell info' and requesting 'Intra-frequency SI Acquisition'. The UE then sends a 'MEASUREMENT REPORT' that includes the 'PSC', 'Cell Identity', and 'CSG Member Indication'. Finally, the SRNC initiates 'Handover processing' as described in reference [6]. + +Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC. + +**Figure 8.1.1-1: Intra-frequency Measurement Procedure of CSG and Hybrid cells** + +- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type. +- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). +- 3) If a measurement configuration for CSG/hybrid cells is not present, the SRNC configures the UE with relevant measurement configuration which includes the PSCs that the UE must measure and the PSCs for which SI acquisition should be performed. The network may use the CSG proximity indication for intra-frequency case to minimize the time during which measurements for CSG/hybrid cells are configured. +- 4) The UE sends a measurement report including the measured PSC, Cell Identity, CSG ID and CSG membership indication of the target HNB to the SRNC (e.g., due to a triggered intra-frequency event 1d). The UE can acquire MIB and SIB3/SIB4 of intra-frequency target HNB cells in parallel with reception of the serving cell transmissions in CELL\_DCH. No measurement gaps are required for reading MIB and SIB3/SIB4. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. +- 5) SRNC can then proceed with the handover processing as described in [6]. + +After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements configured. + +The PSC confusion is resolved by steps 3 and 4. The SRNC can request SI acquisition and reporting for any PSC, not limited to PSCs of CSG or hybrid cells. + +### 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure + +![Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + Note left of UE: 6. UE reads System Information of the target HNB + Note right of SRNC: 8. Handover processing [6] + SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)] + UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication] + SRNC->>UE: 3. MEASUREMENT CONTROL [ CSG Inter-frequency cell info] + UE-->>SRNC: 4. MEASUREMENT REPORT [measured PSCs] + SRNC->>UE: 5. MEASUREMENT CONTROL [(report criteria = Periodical reporting criteria), (Amount of reporting = 1), (Inter-frequency SI Acquisition)], + UE-->>SRNC: 7. MEASUREMENT REPORT [Cell Identity, CSG Member Indication] + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC). The process begins with the SRNC sending a 'MEASUREMENT CONTROL' message to the UE, specifying 'CSG Proximity detection' as the measurement type. The UE responds with a 'MEASUREMENT REPORT' containing a 'CSG Proximity Indication'. The SRNC then sends another 'MEASUREMENT CONTROL' message providing 'CSG Inter-frequency cell info'. The UE replies with a 'MEASUREMENT REPORT' showing 'measured PSCs'. Next, the SRNC sends a 'MEASUREMENT CONTROL' message with specific reporting criteria: 'Periodical reporting criteria', 'Amount of reporting = 1', and 'Inter-frequency SI Acquisition'. While this is happening, the UE reads the 'System Information of the target HNB'. Finally, the UE sends a 'MEASUREMENT REPORT' with 'Cell Identity, CSG Member Indication', and the SRNC proceeds with 'Handover processing'. + +Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC. + +**Figure 8.1.2-1: Inter-frequency Measurement Procedure of CSG and Hybrid cells.** + +- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type. +- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). The CSG proximity indication includes the RAT and frequency of the cell. +- 3) The SRNC configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells. Compressed mode gaps, if required by the UE, are also activated to allow UE to perform measurements on the reported RAT and frequency. The network may also use the proximity indication to minimize the requesting of handover preparation information of CSG/hybrid cells by avoiding requesting such information when the UE is not in the geographical area where its CSG member cells are located. +- 4) The UE sends a measurement report including the measured PSCs/PCIs. +- 5) The SRNC configures the UE to perform SI acquisition and reporting of a particular PSC/PCI. +- 6) The UE performs SI acquisition using autonomous gaps, i.e., the UE may suspend reception and transmission with the SRNC to acquire the relevant system information from the target HNB/HeNB. +- 7) The UE sends a measurement report including Cell Identity, CSG ID and CSG membership indication. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. +- 8) SRNC can then proceed with the handover processing. The handover processing for inter-frequency handover to a CSG/Hybrid cell is described in [6]. + +NOTE: The above steps also apply to inter-RAT mobility from UMTS cell to HeNB. + +After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements on the reported RAT and frequency. + +In the above procedure, step 2 may not be performed in case the UE has not previously visited the HNB, e.g., when the UE first visits a CSG/hybrid cell. + +The PSC/PCI confusion is resolved by steps 5, 6 and 7. The SRNC can request SI acquisition and reporting for any PSC/PCI, not limited to PSCs/PCIs of CSG or hybrid cells. + +## 8.2 Handover from CSG Cell + +In Cell\_DCH state, the handover procedure from a CSG member cell to a non-CSG cell is expected to be the same as the procedure specified in [3]. + +## 8.3 Handover from CSG Cell to CSG Cell + +In Cell\_DCH state, handover between CSG member cells with the same CSG ID is expected to be the same as the procedure specified in Section 8.1. + +In Cell\_DCH state, handover between CSG member cells with different CSG IDs is expected to be the same as the procedure specified in Section 8.1. + +# --- 9 Support of Hybrid Cells + +## 9.1 Measurement Rules + +To measure for hybrid cells with a CSG Identity and its associated PLMN ID belonging to an entry in the UE's CSG whitelist, measurement rules of Chapter 7.1 apply. Otherwise, normal measurement rules apply. + +NOTE: The autonomous search for hybrid cells does not imply that UE need to constantly check the CSG ID of all cells it sees. + +## 9.2 Reselection + +In case the UE has CSG ID and its associated PLMN ID of the hybrid cell in its CSG whitelist, cell reselection procedures will be the same as for a CSG cell as described in Chapter 7.2. + +For all other UEs, cell reselection procedures will utilise normal cell reselection rules. + +# Annex B (informative): Void + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 2008-11-17 | RAN2#64 | | | | | Proposal for 25.367 TS structure and Text Proposals | 0.0.0 | +| 2008-11-20 | RAN2#64 | | | | | Revision based on discussion for email agreement. | 0.0.1 | +| 2008-11-21 | RAN2#64 | | | | | Final text proposals for email agreement. | 0.0.2 | +| 2008-11-25 | RAN2#64 | | | | | Revision based on email agreement. | 1.0.0 | +| 2008-12 | RP-42 | RP-080873 | - | - | | v1.0.0 was approved at RAN #42 as v8.0.0 and put under CR control | 8.0.0 | +| 2009-03 | RP-43 | RP-090135 | 0001 | 1 | | Corrections to manual CSG search | 8.1.0 | +| | RP-43 | RP-090135 | 0002 | 1 | | Allignment to latest stage 3 agreements | 8.1.0 | +| 2009-06 | RP-44 | RP-090524 | 0003 | - | | Idle mode requirements to support hybrid cells for HNB | 9.0.0 | +| 2009-09 | RP-45 | RP-090930 | 0005 | 4 | | CR capturing HNB inbound mobility agreements | 9.1.0 | +| | RP-45 | RP-090911 | 0008 | - | | Correction to manual CSG ID selection 25.367CR(R9) | 9.1.0 | +| 2009-12 | RP-46 | RP-091343 | 0010 | 1 | | CR on Add Hybrid cell into the manual CSG ID selection in 25.367 | 9.2.0 | +| | RP-46 | RP-091343 | 0011 | 2 | | Draft CR capturing HNB inbound mobility agreements | 9.2.0 | +| | RP-46 | RP-091343 | 0012 | - | | Removal of description related to small repetition of SIB3/4 | 9.2.0 | +| | RP-46 | RP-091343 | 0014 | 1 | | Renaming Allowed CSG List (25.367 Rel-9) | 9.2.0 | +| | RP-46 | RP-091330 | 0015 | - | | Correction to definition of CSG cell. | 9.2.0 | +| 2010-03 | RP-47 | RP-100306 | 0017 | - | | CR capturing HNB inbound mobility agreements | 9.3.0 | +| 2010-06 | RP-48 | RP-100551 | 0018 | - | | Some corrections to 25.367 | 9.4.0 | +| 2010-12 | RP-50 | RP-101206 | 0019 | - | | Correction to the limitation of SI acquisition | 9.5.0 | +| 2011-03 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 2012-06 | RP-56 | RP-120880 | 0026 | - | | PSC range note on RAN sharing | 11.0.0 | +| 2013-03 | RP-59 | RP-130247 | 0028 | 1 | | Corrections on mobility to CSG and hybrid cells for UMTS | 11.1.0 | +| 2013-12 | RP-62 | RP-131998 | 0030 | 1 | | Introduction of inbound mobility to shared CSG/hybrid cell | 12.0.0 | +| | RP-62 | RP-131998 | 0031 | - | | Introduction of CSG CELL_FACH mobility | 12.0.0 | +| 2015-12 | RP-70 | | | | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 2017-03 | RP-75 | | | | | Upgrade to Release 14 - no technical change | 14.0.0 | +| 2018-06 | SA-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25402/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/25_series/25402/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c71c7cc3ac9ce659931c76ab1edabe56ca350c --- /dev/null +++ b/marked/Rel-16/25_series/25402/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b9095a08ee458c64f9d956650164d8ed0bff1d6633131d36fc75322ef868b68 +size 80837 diff --git a/marked/Rel-16/25_series/25402/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/25_series/25402/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a49facdac0f476c1dfd6e442cbc940b9170b3d22 --- /dev/null +++ b/marked/Rel-16/25_series/25402/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b11dbd6207975a8ea19575decbafc7a703e0f5e0675b7b8f1932b658e947c8 +size 81573 diff --git a/marked/Rel-16/25_series/25402/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/25_series/25402/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3542455ab8f41fc2df835999a4caae2b4f6e248 --- /dev/null +++ b/marked/Rel-16/25_series/25402/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb5fec32f92aae0d77c2db9d148872f926d8c6d2189204a65781327c70a80b5 +size 20997 diff --git a/marked/Rel-16/25_series/25402/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Rel-16/25_series/25402/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35039b5af296f0bc352db9100617b944e70283fa --- /dev/null +++ b/marked/Rel-16/25_series/25402/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1469a7b155516a2d43fbab472711ad436755d53221b0f080975f8d72925d09ab +size 28765 diff --git a/marked/Rel-16/25_series/25402/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-16/25_series/25402/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83156c8884004fe3bdd41d789227376e40c5b127 --- /dev/null +++ b/marked/Rel-16/25_series/25402/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed4e2eec10e7c90b2f05616f3f5ab744dfe07eba3d019aa96c282dca7548ac1 +size 82394 diff --git a/marked/Rel-16/25_series/25402/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-16/25_series/25402/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a6050eb89f514262f31dd54be2b3a39ff381a4 --- /dev/null +++ b/marked/Rel-16/25_series/25402/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7580094abdb2f160acff758ce5c68562a07f0efb4e6191ab94a4cd3bf067c6a +size 48229 diff --git a/marked/Rel-16/25_series/25402/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/25_series/25402/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cb98e65bce86a73d2e22058c90f37cffe809ca --- /dev/null +++ b/marked/Rel-16/25_series/25402/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2a30e6063ead259b022090dedec1064c238293e26f930a5fdc328ee9e39da4e +size 54194 diff --git a/marked/Rel-16/25_series/25402/26e334e61dd059cff029338a2a604d8d_img.jpg b/marked/Rel-16/25_series/25402/26e334e61dd059cff029338a2a604d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b60f5fde5eaf82c1f370c0a03d7410c20b312a27 --- /dev/null +++ b/marked/Rel-16/25_series/25402/26e334e61dd059cff029338a2a604d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f71123221aeb41195d121ad54d3ebc4244aea2154be16066d49de0c895f933f +size 67196 diff --git a/marked/Rel-16/25_series/25402/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/25_series/25402/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6eec32e9e2af8d1b4f71b22c51ba1403c9c973c --- /dev/null +++ b/marked/Rel-16/25_series/25402/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2030c56d70a23fe3a45a45a6d738940fdbb034bba454f8749481b839f577208e +size 80062 diff --git a/marked/Rel-16/25_series/25402/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25402/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36942dd749feddc57ef5c83c8091885eafb7ffd9 --- /dev/null +++ b/marked/Rel-16/25_series/25402/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e923ca65987c0efc6a0874a2bd5a584f780298184997617b0fd76448274c6e6 +size 177624 diff --git a/marked/Rel-16/25_series/25402/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/25_series/25402/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aad030ff0b9e18cc94c1646dee4b8a5645d2cab --- /dev/null +++ b/marked/Rel-16/25_series/25402/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29f5dbf606a16d39dcae1f58216ba8ebc79a6d30129fd58e4edd9bd406f7c822 +size 50500 diff --git a/marked/Rel-16/25_series/25402/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/25_series/25402/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3c58a380f3f34bcbdbbc3a79a80519c29dd28b3 --- /dev/null +++ b/marked/Rel-16/25_series/25402/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0e93c3d39de0d6d24740d9b7c74ff2514b74eabff3f78fb9bcf101a3511a279 +size 28087 diff --git a/marked/Rel-16/25_series/25402/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25402/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a61f459e1197b71bb85fdcd07b0f430b4d0ca63 --- /dev/null +++ b/marked/Rel-16/25_series/25402/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5603200502b89dd9e0b319e67a88bf928364b3d2297d3cd225bb03f8d132cdcf +size 92046 diff --git a/marked/Rel-16/25_series/25402/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/25_series/25402/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b3ab69991635928e80daae215ee86cc6657f9df --- /dev/null +++ b/marked/Rel-16/25_series/25402/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:248e6f89d288e4612a6c37a449d76de99aea91b7f27428c7443531b30e415a6e +size 179534 diff --git a/marked/Rel-16/25_series/25402/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/25_series/25402/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7c6950924742b6800f9839ee8d64909977ca4b5 --- /dev/null +++ b/marked/Rel-16/25_series/25402/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0e48b1bb79dea20a6fdcf41feaae68cb21ef3c2dcf21f6e1e02656b3c41e217 +size 75866 diff --git a/marked/Rel-16/25_series/25402/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/25_series/25402/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66c1eacc5a206473b0b41c1cf5106d58416e33c0 --- /dev/null +++ b/marked/Rel-16/25_series/25402/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b50d7f78d2bf2d41db00275ab3dbe7bf60cc5e376c32c59b3e559d4169fa9327 +size 136813 diff --git a/marked/Rel-16/25_series/25402/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-16/25_series/25402/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7b33f2db153651aa439b1e0312868ab4bd91a1d --- /dev/null +++ b/marked/Rel-16/25_series/25402/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367af1c7c211b6bdad6274e05763b282136437b7379b194bab5b98deaae6434e +size 27864 diff --git a/marked/Rel-16/25_series/25402/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25402/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2c5edf147b566bd74f59fad4157798da52ba8e0 --- /dev/null +++ b/marked/Rel-16/25_series/25402/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:583aa70056f47c03ba8fdc1c4816fa659f3075138ca58dacf6cae9db581c88af +size 107743 diff --git a/marked/Rel-16/25_series/25402/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/25_series/25402/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdc5c9f190394f5215a0eb57bbe5a41075a2eb9f --- /dev/null +++ b/marked/Rel-16/25_series/25402/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dea29f114a720adaa299680196eb99b93f236956a1b6b942398e76875e3807c0 +size 180366 diff --git a/marked/Rel-16/25_series/25402/b78854f39d5fe3c45a918555e158ee58_img.jpg b/marked/Rel-16/25_series/25402/b78854f39d5fe3c45a918555e158ee58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35c3d7f99411e2e5655febcc32e21f18af07748f --- /dev/null +++ b/marked/Rel-16/25_series/25402/b78854f39d5fe3c45a918555e158ee58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fac9c91b3f2c2d3f4ce38f0c8341a0c3b44cf67924adaf3d202f0404c5f6a35 +size 48747 diff --git a/marked/Rel-16/25_series/25402/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/25_series/25402/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d4421d6b1a6004b2b2112b80d972f963d15e805 --- /dev/null +++ b/marked/Rel-16/25_series/25402/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da6f38284d65d7c01d591c4491c62adb996c19650a3ab63abe4cb9ad3b52cb30 +size 79856 diff --git a/marked/Rel-16/25_series/25402/c3e1070b4f3194b1fb1b9d5300dac25f_img.jpg b/marked/Rel-16/25_series/25402/c3e1070b4f3194b1fb1b9d5300dac25f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c04a1571cdfe7e948b15a60c8809b6dcd4937a2 --- /dev/null +++ b/marked/Rel-16/25_series/25402/c3e1070b4f3194b1fb1b9d5300dac25f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59ba9c3baed68d65275e921cec0e28dc3ca0df21894c542f41202c0810e14144 +size 252961 diff --git a/marked/Rel-16/25_series/25402/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg b/marked/Rel-16/25_series/25402/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9dcee875b7d77b6a60a60d7cb6bad3fcaba0f2d --- /dev/null +++ b/marked/Rel-16/25_series/25402/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:744f7d08de11d00adea604afdbb6933fdddef3f2ec7b4eb79e9a84ff4f497aac +size 33621 diff --git a/marked/Rel-16/25_series/25402/d1c99a42332e5ee19f3b840281c26681_img.jpg b/marked/Rel-16/25_series/25402/d1c99a42332e5ee19f3b840281c26681_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc782058ef7ca1a647de405c7d56346c2df529c0 --- /dev/null +++ b/marked/Rel-16/25_series/25402/d1c99a42332e5ee19f3b840281c26681_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2376bf557346e670dd45eb45fe819f558f197d7b9330aeb7721be26fdd9de776 +size 49917 diff --git a/marked/Rel-16/25_series/25402/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-16/25_series/25402/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eee11ad630759352ac3dfe0651354509e81de303 --- /dev/null +++ b/marked/Rel-16/25_series/25402/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca97db3ad98da73a85feabaf39d7590e6385fe770ef4696b55f1b7ee03d08fdc +size 35081 diff --git a/marked/Rel-16/25_series/25402/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/25_series/25402/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aac7615975946aaa69fb31528759a4032c52c77a --- /dev/null +++ b/marked/Rel-16/25_series/25402/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79f938e6108f33520681b575e4f2671bbab3d2c625e5399f72a5c355a689d0df +size 95898 diff --git a/marked/Rel-16/25_series/25402/raw.md b/marked/Rel-16/25_series/25402/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a32ebd192cd4db53ec61afd71276d4288e112273 --- /dev/null +++ b/marked/Rel-16/25_series/25402/raw.md @@ -0,0 +1,1732 @@ + + + + +# Keywords --- + +UMTS, radio, stage 2, synchronization + +# Contents + +| | | +|-----------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 3.4 Specification Notations ..... | 8 | +| 4 Synchronisation Issues..... | 10 | +| 4.1 General ..... | 10 | +| 4.2 Network Synchronisation..... | 11 | +| 4.3 Node Synchronisation ..... | 11 | +| 4.4 Transport Channel Synchronisation..... | 11 | +| 4.5 Radio Interface Synchronisation ..... | 12 | +| 4.6 Time Alignment Handling ..... | 12 | +| 4.7 Uplink Synchronisation..... | 12 | +| 5 Synchronisation Counters and Parameters..... | 12 | +| 6 Node Synchronisation ..... | 16 | +| 6.1 General ..... | 16 | +| 6.1.1 RNC-Node B Node Synchronisation..... | 16 | +| 6.1.2 Inter Node B Node Synchronisation..... | 18 | +| 6.1.2.1 TDD Node B Synchronisation Ports..... | 18 | +| 6.1.2.2 TDD Inter Node B Node Synchronisation procedure [3.84Mcps TDD]..... | 21 | +| 6.1.2.2.1 Preliminary Phase..... | 21 | +| 6.1.2.2.1A Frequency Acquisition Phase ..... | 22 | +| 6.1.2.2.1B Initial Phase ..... | 22 | +| 6.1.2.2.2 Steady-State Phase ..... | 23 | +| 6.1.2.2.3 Late-Entrant Cells ..... | 23 | +| 6.1.2.3 TDD Inter Node B Node Synchronisation procedure [1.28Mcps TDD]..... | 23 | +| 6.1.2.3.1 Preliminary Phase..... | 24 | +| 6.1.2.3.2 Initial Phase ..... | 24 | +| 6.1.2.3.3 Steady-State Phase ..... | 25 | +| 6.1.2.3.3.1 Basic method ..... | 25 | +| 6.1.2.3.3.2 Extended method ..... | 25 | +| 6.1.2.3.4 Late-Entrant Cells ..... | 26 | +| 6.1.2.4 Node B synchronisation for 3.84Mcps TDD MBSFN IMB..... | 27 | +| 7 Transport Channel Synchronisation..... | 27 | +| 7.1 General ..... | 27 | +| 7.2 Timing adjustment and Time of Arrival monitoring on Iub/Iur interfaces ..... | 28 | +| 8 Radio Interface Synchronisation..... | 31 | +| 8.1 General ..... | 31 | +| 8.2 FDD Radio Interface Synchronisation ..... | 31 | +| 8.2.1 General ..... | 31 | +| 8.2.2 Neighbour cell list timing information ..... | 33 | +| 8.3 TDD Radio Interface Synchronisation..... | 33 | +| 8.3.1 General ..... | 33 | +| 8.3.2 Intercell Synchronisation..... | 33 | +| 8.3.3 Multi Frame Synchronisation..... | 34 | +| 8.3.4 Timing Advance for 3.84Mcps and 7.68Mcps TDD..... | 34 | +| 8.3.4.1 Measurement of the timing deviation on the physical channels..... | 35 | +| 8.3.4.2 Assignment of correct timing advance value when establishing new channels ..... | 35 | +| 8.3.4.2.1 Transition to CELL_DCH State..... | 35 | +| 8.3.4.2.2 When establishing an USCH in CELL_FACH state..... | 36 | + +| | | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------|----| +| 8.3.4.2.3 | When establishing E-DCH in CELL_DCH state (E-DCH/HS-DSCH operation with no UL DPCH)..... | 36 | +| 8.3.4.3 | Update of timing advance value for channels in operation ..... | 36 | +| 8.3.4.3.1 | UE in CELL_DCH state..... | 36 | +| 8.3.4.3.2 | UE with USCH Traffic in CELL_FACH state..... | 36 | +| 8.3.4.4 | Setting of timing advance value for target cell at handover ..... | 37 | +| 8.3.4.4.1 | General ..... | 37 | +| 8.3.4.4.2 | Handover from TDD to TDD with synchronised cells ..... | 37 | +| 8.3.4.4.3 | Handover from FDD to TDD, Handover from other systems to TDD, or Handover from TDD to TDD with unsynchronised cells..... | 37 | +| 8.3.5 | UL Synchronisation for 1.28Mcps TDD ..... | 37 | +| 8.3.5.1 | The establishment of uplink synchronisation ..... | 37 | +| 8.3.5.1.1 | Preparation of uplink synchronisation by downlink synchronisation ..... | 37 | +| 8.3.5.1.2 | Establishment of uplink synchronisation ..... | 38 | +| 8.3.5.2 | Maintenance of uplink synchronisation..... | 38 | +| 9 | Usage of Synchronisation Counters and Parameters to support Transport Channel and Radio Interface Synchronisation ..... | 38 | +| 9.1 | General ..... | 38 | +| 9.2 | Calculations performed in the UTRAN ..... | 41 | +| 9.2.1 | UE in CELL_FACH/PCH state..... | 41 | +| 9.2.2 | UE changes from CELL_FACH/PCH state to CELL_DCH state: 1 RL ..... | 41 | +| 9.2.3 | [FDD - UE changes from CELL_FACH/PCH state to CELL_DCH state: several RL's]..... | 41 | +| 9.2.4 | UE in CELL_DCH state: addition of a new RL or handover to a new cell ..... | 41 | +| 9.2.5 | Handover from other RAN to UMTS..... | 42 | +| 9.3 | Calculations performed in the UE..... | 42 | +| 9.3.A | UE in CELL_FACH/PCH state..... | 42 | +| 9.3.1 | UE changes from CELL_FACH/PCH state to CELL_DCH state: 1 RL ..... | 42 | +| 9.3.1A | [FDD - UE changes from CELL_FACH/PCH to CELL_DCH state: several RL's]..... | 42 | +| 9.3.2 | UE in CELL_DCH state: addition of a new RL or handover to a new cell ..... | 42 | +| 9.4 | Synchronisation of L1 configuration changes..... | 43 | +| 9.5 | Examples of synchronisation counters during state transitions ..... | 43 | +| 10 | Time Alignment Handling ..... | 47 | +| 11 | MBMS related Transport Channel Synchronisation..... | 48 | +| 11.1 | General ..... | 48 | +| 11.2 | FDD MBMS related Transport Channel Synchronisation ..... | 48 | +| 11.3 | TDD MBMS related Transport Channel Synchronisation..... | 49 | +| 11.4 | Inter-Node B Synchronisation of MTCH Transmissions for IP Multicast ..... | 49 | +| 11.5 | 3.84Mcps TDD MBSFN IMB Transport Channel Synchronisation..... | 50 | +| Annex A (informative): | Change history..... | 51 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document constitutes the stage 2 specification of different synchronisation mechanisms in UTRAN and on Uu. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. + +- [1] 3GPP TS 25.401: "UTRAN overall description". +- [2] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling". +- [3] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". +- [4] 3GPP TS 25.435: "UTRAN Iub interface user plane protocols for Common Transport Channel data streams". +- [5] 3GPP TS 25.427: "UTRAN Iub/Iur Interface user plane protocol for DCH data streams". +- [6] TIA/EIA 422 B: "Electrical characteristics of balanced voltage digital interface circuits". +- [7] 3GPP TS 25.411: "UTRAN Iu interface layer 1". +- [8] 3GPP TS 25.421: "UTRAN Iur interface layer 1". +- [9] 3GPP TS 25.431: "UTRAN Iub interface layer 1". +- [10] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". +- [11] Void. +- [12] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [13] 3GPP TS 25.215: "Physical layer; Measurements (FDD)". +- [14] 3GPP TS 25.225: "Physical layer; Measurements (TDD)". +- [15] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [16] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [17] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)". +- [18] ITU-T Recommendation G.811 (1997-09): "Timing Characteristics of Primary Reference Clocks". +- [19] ITU-T Recommendation G.812 (1998-06): "Timing Requirements of Slave Clocks suitable for use as Node Clocks in Synchronization Network". +- [20] ITU-T Recommendation G.813 (1996-08): "Timing Characteristics of SDH equipment slave clocks (SEC)". + +- [21] ETSI EN 300 462-4-1(1998-03): "Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 4-1: Timing characteristics of slave clocks suitable for synchronization supply to Synchronous Digital Hierarchy (SDH) and Plesiochronous Digital Hierarchy (PDH) equipment". +- [22] ETSI EN 300 462-5-1 (1996-09):"Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 5-1: Timing characteristics of slave clocks suitable for operation in Synchronous Digital Hierarchy (SDH) equipment". +- [23] ETSI EN 300 462-7-1 (2001-04): "Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 7-1: Timing characteristics of slave clocks suitable for synchronisation supply to equipment in local node applications". +- [24] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [25] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [26] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". +- [27] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +**Network Synchronisation:** generic concept that depicts the way of distributing a common frequency to all elements in a network + +**Reference Timing Signal:** timing signal of specified performance that can be used as a timing source for a slave clock + +**Holdover mode:** operating condition of a clock which has lost its controlling reference input and is using stored data, acquired while in locked operation (that is while controlled by an external input reference), to control its output. The stored data are used to control phase and frequency variations, allowing the locked condition to be reproduced within specifications. + +## 3.2 Symbols + +No special symbols are defined in this document. + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------------------|------------------------------------| +| ACK | (time alignment) acknowledgement | +| BFN | Node B Frame Number (counter) | +| CFN | Connection Frame Number (counter) | +| CH | Channel | +| CN | Core Network | +| CPICH | Common Pilot Channel | +| CRNC | Controlling RNC | +| DL | Down Link | +| DCH | Dedicated Channel | +| DOFF FDD | FDD Default DPCH Offset value | +| DOFF TDD | TDD Default DPCH Offset value | +| DPCH | Dedicated Physical Channel | +| DPCCH | Dedicated Physical Control Channel | +| DRNC | Drift RNC | +| DSCH | Downlink Shared Channel | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| F-DPCH | Fractional DPCH | +| GPS | Global Positioning System | + +| | | +|--------|-----------------------------------------------------| +| HO | Handover | +| IMB | Integrated Mobile Broadcast | +| LTOA | Latest Time of Arrival | +| L1 | Layer 1 | +| L2 | Layer 2 | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MBSFN | Multicast/Broadcast over a Single Frequency Network | +| MCCH | MBMS point-to-multipoint Control Channel | +| MFN | Multicast Frame Number (counter) | +| MTCH | MBMS point-to-multipoint Traffic Channel | +| NACK | (time alignment) negative acknowledgement | +| PCCPCH | Primary Common Control Physical Channel | +| PCH | Paging Channel | +| PDU | Packet Data Unit | +| PTP | Point-to-Point | +| PTM | Point-to-Multipoint | +| PUSCH | Physical Uplink Shared Channel | +| RAB | Radio Access Bearer | +| RACH | Random Access Channel | +| RAN | Radio Access Network | +| RFN | RNC Frame Number (counter) | +| RL | Radio Link | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| SCH | Synchronisation Channel | +| SFN | Cell System Frame Number (counter) | +| SRNC | Serving RNC | +| SRNS | Serving RNS | +| TBS | Transport Block Set | +| TDD | Time Division Duplex | +| TOA | Time Of Arrival | +| TOAWE | Time Of Arrival Window Endpoint | +| TOAWS | Time Of Arrival Window Startpoint | +| TTI | Time Transmission Interval | +| UE | User Equipment | +| UL | Up Link | +| UMTS | Universal Mobile Telecommunications System | +| USCH | Uplink Shared CHannel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.4 Specification Notations + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. +- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. + +- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. +- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. +- Procedure When referring to an elementary procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Link Setup procedure. +- Message When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. +- IE When referring to an information element (IE) in the specification, the *Information Element Name* is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. *Transport Format Set* IE. +- Value of an IE When referring to the value of an information element (IE) in the specification, the "Value" is enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)". +- Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. FACH FLOW CONTROL control frame. + +# --- 4 Synchronisation Issues + +## 4.1 General + +This clause identifies the different UTRAN synchronisation issues, i.e.: + +- Network Synchronisation; +- Node Synchronization; + +- Transport Channel Synchronisation; +- Radio Interface Synchronisation; +- Time Alignment Handling; +- Uplink Synchronisation. + +The Nodes involved by the above mentioned synchronisation issues (with the exception of Network and Node Synchronisation) are shown by the Synchronisation Issues Model of Figure 1. + +![Figure 1: Synchronisation Issues Model. This diagram illustrates the network architecture and the specific nodes involved in various synchronization tasks. The architecture includes a CN (Core Network) at the top, connected to a Vocoder and an RNC (Radio Network Controller). The RNC is connected to multiple Node Bs (Base Stations), which in turn connect to UEs (User Equipment). The diagram is divided into three horizontal sections on the left, each corresponding to a synchronization issue: 'Time Alignment Handling' (involving the Vocoder and RNC), 'Transport Channel Synchronisation' (involving the RNC and Node Bs), and 'Radio Interface Synchronisation' (involving the Node Bs and UEs). A dashed box labeled 'RNS' (Radio Network Subsystem) encloses the RNC and its associated Node Bs. Another dashed box labeled 'UTRAN' encloses the RNC, Node Bs, and UEs. A specific 'TDD Cell Sync.' is indicated between two Node Bs. A note at the bottom right mentions 'Optional TDD only input & output sync ports'.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Figure 1: Synchronisation Issues Model. This diagram illustrates the network architecture and the specific nodes involved in various synchronization tasks. The architecture includes a CN (Core Network) at the top, connected to a Vocoder and an RNC (Radio Network Controller). The RNC is connected to multiple Node Bs (Base Stations), which in turn connect to UEs (User Equipment). The diagram is divided into three horizontal sections on the left, each corresponding to a synchronization issue: 'Time Alignment Handling' (involving the Vocoder and RNC), 'Transport Channel Synchronisation' (involving the RNC and Node Bs), and 'Radio Interface Synchronisation' (involving the Node Bs and UEs). A dashed box labeled 'RNS' (Radio Network Subsystem) encloses the RNC and its associated Node Bs. Another dashed box labeled 'UTRAN' encloses the RNC, Node Bs, and UEs. A specific 'TDD Cell Sync.' is indicated between two Node Bs. A note at the bottom right mentions 'Optional TDD only input & output sync ports'. + +**Figure 1: Synchronisation Issues Model** + +The UTRAN solutions for most of the identified items are described in clauses 6-10. Additional information on UTRAN synchronisation issues and the detailed specification of UTRAN solutions can be found in the following Technical Specifications: + +- Summary of UTRAN Synchronisation Issues: +TS 25.401 [1] "UTRAN Overall Description", clause 9. +- Network Synchronisation: +TS 25.411 [7] "UTRAN Iu Interface Layer 1", subclause 4.2; +TS 25.104 [10] "UTRA (BS) FDD; Radio transmission and reception", subclause 6.3; +TS 25.105 [17] "UTRA (BS) TDD, Radio transmission and reception", subclause 6.3. +- RNC-Node B Node Synchronisation: +TS 25.427 [5] "Iub/Iur Interface User Plane Protocol for DCH Data Streams", subclause 5.5; +TS 25.435 [4] "UTRAN Iub Interface User Plane Protocols for COMMON TRANSPORT CHANNEL Data Streams", subclause 5.2. +- Transport Channel Synchronisation: +TS 25.427 [5] "Iub/Iur Interface User Plane Protocol for DCH Data Streams", subclauses 5.2 – 5.3; +TS 25.435 [4] "UTRAN Iub Interface User Plane Protocols for COMMON TRANSPORT CHANNEL Data Streams", subclauses 5.3 – 5.4. +- Time Alignment Handling: +TS 25.415 [27] "UTRAN Iu Interface User Plane Protocols", subclauses 6.5.4. + +## 4.2 Network Synchronisation + +Network Synchronisation relates to the distribution of synchronisation references to the UTRAN Nodes and the stability of the clocks in the UTRAN (and performance requirements on UTRAN internal interfaces). + +The distribution of an accurate frequency reference to the network elements in the UTRAN is related to several aspects. One main issue is the possibility to provide a synchronisation reference with a frequency accuracy better than 0.05 ppm at the Node B in order to properly generate signals on the radio interface (see references TS 25.104 [10] and TS 25.105 [17]). + +A general recommendation is to supply a traceable synchronisation reference according to reference ITU-T Rec. G.811 [18]. + +The clock to be implemented in UTRAN Nodes shall be chosen with characteristics that depend on the L1 adopted (see reference TS 25.421 [8] and TS 25.431 [9]) and on the Network Synchronisation strategy adopted. Already standardized clocks may be used (see references ITU-T Rec. G.812 [19], ITU-T Rec. G.813 [20], ETSI EN 300 462-4-1 [21], ETSI EN 300 462-5-1 [22] and ETSI EN 300 462-7-1 [23]). + +For example in order to support STM-N interfaces at the RNC, the ITU-T Recommendation G.813 (see reference ITU-T Rec. G.813 [20]) may be sufficient. The implementation in the UTRAN of a better performing clock (in terms of holdover) may be recommended for distribution of a 0.05 ppm during failures in the synchronisation network (EN 300 462-7-1, see reference ETSI EN 300 462-7-1 [23], EN 300 462-4-1, see reference ETSI EN 300 462-4-1 [21], or ITU-T Recommendation G.812 type 1, type 2 or type 3, see reference ITU-T Rec. G.812 [19]). + +## 4.3 Node Synchronisation + +Node Synchronisation relates to the estimation and compensation of timing differences among UTRAN nodes. FDD and TDD modes have different requirements on the accuracy of the timing difference estimation and on the necessity to compensate for these differences. + +Two types of Node Synchronisation can be identified, "RNC-Node B" and "Inter Node B" Node Synchronisation. Their usage differs and the requirements differ between the FDD and TDD modes. + +"RNC-Node B" Node Synchronisation allows to get knowledge of the timing differences between RNC and its Node Bs. + +"Inter Node B" Node Synchronisation may be used in the TDD mode to compensate the timing differences among Node Bs in order to achieve a common timing reference. The purpose of having a common timing reference is to allow Intercell Synchronisation, which is used, within neighbouring cells to minimise cross-interference. + +Positioning / Localisation functions may also set requirements on Node Synchronisation. + +## 4.4 Transport Channel Synchronisation + +The Transport Channel Synchronisation mechanism defines synchronisation of the frame transport between RNC and Node B, considering radio interface timing. + +DL TBS transmission is adjusted to fit receiver by adjusting the DL TBS timing in upper node. + +## 4.5 Radio Interface Synchronisation + +The Radio Interface Synchronisation relates to the timing of the radio frame transmission (either in downlink [FDD] or in both directions [TDD]). FDD and TDD have different mechanisms to determine the exact timing of the radio frame transmission and also different requirements on the accuracy of this timing. + +In FDD Radio Interface Synchronisation is necessary to assure that the UE receives radio frames synchronously from different cells, in order to minimise UE buffers. + +In TDD Radio Interface Synchronisation refers to the following two aspects: + +- Intercell Synchronisation that is used to synchronise radio frames within neighbouring cells in order to minimise cells cross-interference, to allow frame wise hopping mechanisms among cells (e.g. Cell Parameter Cycling) + +according to reference TS 25.223 [12]) and to make procedures involving more cells (e.g. handover) easier and more efficient; + +- Timing advance that is used between UE and UTRAN in order to minimise UE-cell interference. In the 1.28 Mcps TDD option, timing advance is provided by uplink synchronisation. + +## 4.6 Time Alignment Handling + +The Time Alignment Handling procedure over Iu relates to the control of DL transmission timing in the CN nodes in order to minimise the buffer delay in SRNC. This procedure is controlled by SRNC. + +## 4.7 Uplink Synchronisation + +In 1.28Mpcs TDD Uplink Synchronisation is performed at Layer 1 for PRACH and uplink DPCH. This procedure includes the establishment of UL synchronisation and maintenance of the UL synchronisation. + +# 5 Synchronisation Counters and Parameters + +This clause defines counters and parameters used in the different UTRAN synchronisation procedures. + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BFN | Node B Frame Number counter. This is the Node B common frame number counter.
[FDD -BFN is optionally frequency-locked to a Network synchronisation reference].
Range: 0 .. 4095 frames. | +| RFN | RNC Frame Number counter. This is the RNC node common frame number counter. RFN is optionally frequency-locked to a Network synchronisation reference.
Range: 0 .. 4095 frames. | +| SFN | Cell System Frame Number counter. SFN is sent on BCH. SFN is used for paging groups and system information scheduling etc.
In FDD SFN = BFN adjusted with T cell .
In TDD, if Inter Node B synchronisation port is used, SFN is locked to the BFN (i.e. SFN mod 256 = BFN mod 256).
Range: 0 .. 4095 frames. | +| CFN | Connection Frame Number (counter). CFN is the frame counter used for the L2/transport channel synchronisation between UE and UTRAN. A CFN value is associated to each TBS and it is passed together with it through the MAC-L1 SAP. CFN provides a common frame reference (at L2) to be used e.g. for synchronised transport channel reconfiguration (see TS 25.423 [2] and TS 25.433 [3]).

The duration of the CFN cycle is longer than the maximum allowed transport delay between MAC and L1 (in UTRAN side, between SRNC and Node B, because the L1 functions that handle the transport channel synchronisation are in the Node B).
Range: 0 .. 255 frames. When used for PCH the range is 0 .. 4095 frames. | + +**Frame Offset** Frame Offset is a radio link specific L1 parameter used to map the CFN, used in the transport channel, into the SFN that defines the specific radio frame for the transmission on the air interface. + +At the L1/L2 interaction, the mapping is performed as: + +$$- \text{SFN mod } 256 = (\text{CFN} + \text{Frame Offset}) \bmod 256 \text{ (from L2 to L1)} \quad (5.1);$$ + +$$- \text{CFN} = (\text{SFN} - \text{Frame Offset}) \bmod 256 \text{ (from L1 to L2)} \quad (5.2).$$ + +The resolution of all three parameters is 1 frame. Frame Offset and CFN have the same range (0...255) and only the 8 least significant bits of the SFN are used. The operations above are modulo 256. + +In the UTRAN, the Frame Offset parameter is calculated by the SRNC and provided to the Node B. + +## **OFF** + +The parameter OFF is calculated by the UE and reported to the UTRAN only when the UTRAN has requested the UE to send this parameter. In the neighbouring cell list, the UTRAN indicates for each cell if the Frame Offset is already known by the UTRAN or shall be measured and reported by the UE. + +OFF has a resolution of 1 frame and a range of 0 .. 255. + +Five different cases are discerned related to the determination of the OFF value by the UE: + +1. The UE changes from common channel state to dedicated channel state: 1 RL. +In this case OFF is zero. +2. [FDD -The UE changes from common channel state to dedicated channel state: several RL's. +OFF is in this case defined as being the difference between SFN of the candidate cells and the SFN of the camping cell. Again the UE sets OFF to zero for the cell to which the UE sends an UL RRC message (cell #1). For cells #2 to n, the UE sets OFF to the difference between the SFN of cell#2, n and the SFN of cell#1. +This could be seen as if a virtual dedicated physical channel (DPCH) already is aligned with cell #1]. +3. The UE adds another RL or moves to another cell in dedicated channel state. +OFF is in this case defined as being the time difference between the CFN and the SFN of the cell in which the RL is to be added. In case this difference cannot be measured, a value as in [FDD - TS 25.215[13]] [TDD - TS 25.225 [14]] shall be reported instead. +4. The UE is coming from another RAN and goes to dedicated channel state: 1 RL. +This case is identical to case 1). +5. [FDD - The UE is coming from another RAN or another frequency in the same RAN and goes to dedicated channel state: several RL's. +This case is identical to case 2], with one exception: OFF will not be zero for the cell to which the UE sends an UL RRC message (the measurement information will be received via the CN in this case) but for a reference cell selected by the UE. All other reported OFF values will be relative to the SFN of this selected reference cell]. + +## **[FDD – DOFFFDD]** + +The DOFFFDD (FDD Default DPCH Offset value) is used to define Frame Offset and Chip Offset at first RL setup. The DOFFFDD is used for both the DPCH and the F-DPCH. The resolution should be good enough to spread out load over Iub and load in Node B (based on certain load distributing algorithms). In addition it is used to spread out the location of Pilot Symbol in order to reduce the peak DL power since Pilot symbol is always transmitting at the fixed location within a slot (the largest number of chips for one symbol is 512 chips). + +The SRNC sends a DOFFFDD parameter to the UE when the new RL will make the UE change its state (from Cell\_FACH state or other when coming from another RAN) to Cell\_DCH state. + +Resolution: 512 chips; Range: 0 .. 599 (< 80 ms). + +## **[TDD – DOFFTDD]** + +The DOFFTDD (TDD Default DPCH Offset value) is used to define Frame Offset at first RL setup, in order to spread out load over Iur and load in Node B (based on certain load distributing algorithms). + +The SRNC sends a DOFFTDD parameter to the UE when the new RL will make the UE change its state (from Cell\_FACH state or other when coming from another RAN) to the Cell\_DCH state. + +Resolution: 1 frame; Range: 0 .. 7 frames. + +**[FDD – Chip Offset]** The Chip Offset is used as offset for the DL DPCH or the F-DPCH relative to the PCCPCH timing. The Chip Offset parameter has a resolution of 1 chip and a range of 0 .. 38399 (< 10 ms). + +The Chip Offset parameter is calculated by the SRNC and provided to the Node B. + +Frame Offset + Chip Offset (sent via NBAP) are in Node B rounded together to closest 256 chip boundary. The 256 chip boundary is used regardless of the used spreading factor, also when the spreading factor is 512. The rounded value (which is calculated in Node B) controls the DL DPCH air-interface timing or the F-DPCH air-interface timing. + +The "Frame Offset + Chip Offset" 256 chip boundary rounding rules for Node B to consider for each DL DPCH and each F-DPCH are: + +1. IF (Frame Offset x 38 400 + Chip Offset) modulo 256 [chips] = {1..127} THEN round (Frame Offset x 38 400 + Chip Offset) modulo 256 frames down to closest 256 chip boundary. +2. IF (Frame Offset x 38 400 + Chip Offset) modulo 256 [chips] = {128..255} THEN round (Frame Offset x 38 400 + Chip Offset) modulo 256 frames up to closest 256 chip boundary. +3. IF (Frame Offset x 38 400 + Chip Offset) modulo 256 [chips] = 0 THEN "Frame Offset x 38 400 + Chip Offset" is already on a 256 chip boundary. + +### **[FDD – DPCH Frame Offset]** + +The DPCH Frame Offset is used as offset for the DL DPCH or the F-DPCH relative to the PCCPCH timing at both the Node B and the UE. The DPCH Frame Offset parameter has a resolution of 256 chips and a range of 0 .. 38144 chips (< 10 ms). + +The DPCH Frame Offset is equivalent to Chip Offset rounded to the closest 256 chip boundary. It is calculated by the SRNC and sent to the UE by the SRNC for each radio link in the active set. + +The DPCH Frame Offset controls the DL DPCH air-interface timing or the F-DPCH air-interface timing. It enables the DL DPCHs or the F-DPCH for radio links in the Active Set to be received at the UE at approximately the same time, which can then be soft combined during soft handover. + +## **[FDD – S-CCPCH Frame Offset]** + +The S-CCPCH Frame Offset is used as offset for the S-CCPCH relative to the P-CCPCH timing of the same cell at the Node B. It may be applied to S-CCPCHs carrying MTCH. The purpose of S-CCPCH Frame Offset is enabling of soft combining of MBMS data at the UE, in particular for the case of long-lived MBMS sessions. + +The S-CCPCH Frame Offset can take the values 0, 10, 20 or 40msecs. + +**[FDD –Tm]** The reported Tm parameter has a resolution of 1 chip and a range of 0 .. 38399. The Tm shall always be sent by the UE. + +Five different cases are discerned related to the determination of the Tm value by the UE: + +1. The UE changes from common channel state to dedicated channel state: 1 RL. In this case the Tm will be zero. +2. The UE changes from common channel state to dedicated channel state: several RL's. +Tm is in this case defined as being the time difference between the received PCCPCH path of the source cell and the received PCCPCH paths of the other target cells. Again the UE sets Tm to zero for the cell to which the UE sends an UL RRC message (cell #1). For cells #2 to n, the UE sets Tm to the time difference of the PCCPCH reception timing of cell#2,n from the PCCPCH reception timing of cell#1. + +3. The UE adds another RL in dedicated channel state (macro-diversity). +Tm is in this case defined as being the time difference between " $T_{UETX} - T_0$ " and the earliest received PCCPCH path of the target cell. $T_{UETX}$ is the time when the UE transmits an uplink DPCCH frame, hence " $T_{UETX} - T_0$ " is the nominal arrival time for the first path of a received DPCH. +4. The UE is coming from another RAN and goes to dedicated channel state: 1 RL. This case is identical to case 1. +5. The UE is coming from another RAN or another frequency in the same RAN and goes to dedicated channel state: several RL's. +This case is identical to case 2, with one exception: Tm will not be zero for the cell to which the UE sends an UL RRC message (the measurement information will be received via the CN in this case) but for a reference cell selected by the UE. All other reported Tm values will be relative to the timing of the PCCPCH in this cell. + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD – T_cell] | T_cell represents the Timing delay used for defining the start of SCH, CPICH and the DL Scrambling Code(s) in a cell relative BFN. The main purpose is to avoid having overlapping SCHs in different cells belonging to the same Node B. A SCH burst is 256 chips long. SFN in a cell is delayed T_cell relative BFN.
Resolution: 256 chips. Range: 0 .. 9 x 256 chips. | +| T1 | RNC specific frame number (RFN) that indicates the time when RNC sends the DL NODE SYNCHRONISATION control frame through the SAP to the transport layer.
Resolution: 0.125 ms; Range: 0 .. 40959.875 ms. | +| T2 | Node B specific frame number (BFN) that indicates the time when Node B receives the correspondent DL NODE SYNCHRONISATION control frame through the SAP from the transport layer.
Resolution: 0.125 ms; Range: 0 .. 40959.875 ms. | +| T3 | Node B specific frame number (BFN) that indicates the time when Node B sends the UL NODE SYNCHRONISATION control frame through the SAP to the transport layer.
Resolution: 0.125 ms; Range: 0 .. 40959.875 ms. | +| T4 | RNC specific frame number (RFN) that indicates the time when RNC receives the UL NODE SYNCHRONISATION control frame. Used in RNC locally. Not standardised over Iub. | +| TOAWS | TOAWS (Time of Arrival Window Startpoint) is the window startpoint. DL DATA FRAMES are expected to be received after this window startpoint. TOAWS is defined with a positive value relative Time of Arrival Window Endpoint (TOAWE) (see Figure 10). A data frame arriving before TOAWS gives a TIMING ADJUSTMENT control frame response.
The resolution is 1 ms, the range is: {0 .. CFN length/2 –1 ms}. | +| TOAWE | TOAWE (Time of Arrival Window Endpoint) is the window endpoint. DL DATA FRAMES are expected to be received before this window endpoint (see Figure 10). TOAWE is defined with a positive value relative Latest Time of Arrival (LTOA). A data frame arriving after TOAWE gives a TIMING ADJUSTMENT control frame response.
The resolution is 1 ms, the range is: {0 .. CFN length –1 ms}. | +| LTOA | LTOA (Latest Time of Arrival) is the latest time instant a Node B can receive a data frame and still be able to process it. Data frames received after LTOA can not be processed (discarded). LTOA is defined internally in Node B to be a processing time before the data frame is sent in air-interface. The processing time (T proc ) could be vendor and service dependent.
LTOA is the reference for TOAWE (see Figure 14). | + +## **TOA** + +TOA (Time of Arrival) is the time difference between the TOAWE and when a data frame is received. A positive TOA means that data frames are received before TOAWE, a negative TOA means that data frames are received after TOAWE. Data frames that are received after TOAWE but before LTOA are processed by Node B. + +TOA has a resolution of 125 $\mu\text{s}$ . TOA is positive when data frames are received before TOAWE (see Figure 12). + +The range is: $\{0 .. +CFN\ length/2 - 125\ \mu\text{s}\}$ . + +TOA is negative when data frames are received after TOAWE. + +The range is: $\{-125\ \mu\text{s} .. -CFN\ length/2\}$ . + +# 6 Node Synchronisation + +## 6.1 General + +By Node Synchronisation it's generally meant the achievement of a common timing reference among different nodes. In UTRAN although a common timing reference among all the nodes could be useful, it is not required. In fact different nodes' counters (RFN and BFN), even if frequency-locked to the same network synchronisation reference, may be not phased aligned (see Figure 2). + +![Figure 2: Timing of UTRAN counters. The diagram shows three horizontal timelines representing counters. The top timeline is labeled 'RNC' on the left and 'RFN' on the right, with tick marks at 4094, 4095, 0, 1, 2, 3, and 4. The middle timeline is labeled 'Node B-1' on the left and 'BFN-1' on the right, with tick marks at 147, 148, 149, 150, 151, 152, and 153. The bottom timeline is labeled 'Node B-2' on the left and 'BFN-2' on the right, with tick marks at 401, 402, 403, 404, 405, 406, 407, and 408. Vertical dashed lines connect the tick marks across the three timelines, showing that the counters are not phase-aligned. For example, the tick mark for 0 in the RFN counter does not align with the tick mark for 149 in the BFN-1 counter or 404 in the BFN-2 counter.](df1d0e45191302de72176e4390224c16_img.jpg) + +Figure 2: Timing of UTRAN counters. The diagram shows three horizontal timelines representing counters. The top timeline is labeled 'RNC' on the left and 'RFN' on the right, with tick marks at 4094, 4095, 0, 1, 2, 3, and 4. The middle timeline is labeled 'Node B-1' on the left and 'BFN-1' on the right, with tick marks at 147, 148, 149, 150, 151, 152, and 153. The bottom timeline is labeled 'Node B-2' on the left and 'BFN-2' on the right, with tick marks at 401, 402, 403, 404, 405, 406, 407, and 408. Vertical dashed lines connect the tick marks across the three timelines, showing that the counters are not phase-aligned. For example, the tick mark for 0 in the RFN counter does not align with the tick mark for 149 in the BFN-1 counter or 404 in the BFN-2 counter. + +**Figure 2: Timing of UTRAN counters** + +However in order to minimise the transmission delay and the buffering time for the DL transmission on the air interface, it can be useful to estimate the timing differences between RNC and Node Bs, without the need to compensate for the phase differences between RNC's and Node B's counters. + +On the other hand the achievement of a common timing reference among Node B's may be used in TDD to support Cell Synchronisation. + +For these reasons in UTRAN node synchronisation refers to the following two aspects: + +- RNC-Node B Node Synchronisation; +- Inter Node B Node Synchronisation. + +### 6.1.1 RNC-Node B Node Synchronisation + +The Node Synchronisation between RNC and Node B can be used to find out the timing reference differences between the UTRAN nodes (RFN in RNC and BFN in Node B). The use is mainly for determining good DL and UL offset values for transport channel synchronisation between RNC and their Node B's. Knowledge of timing relationships between these nodes is based on a measurement procedure called RNC-Node B Node Synchronisation Procedure. The procedure is defined in the user plane protocols for Iub (DCH, DSCH [TDD], HS-DSCH (Type1, enhanced CELL/URA\_PCH operation), and FACH/PCH) and Iur (DCH, HS-DSCH). + +When the procedure is used from SRNC over the DCH user plane, it allows finding out the actual round-trip-delay a certain service has (as the NODE SYNCHRONISATION control frames are transferred the same way as the DCH frames). + +The procedure may also be carried out over a high priority transport bearer (beneficial when used between CRNC and Node Bs for the RNC-Node B Synchronisation purpose). Measurements of node offsets can be made at start or restart as well as during normal operation to supervise the stability of the nodes. + +If an accurate Reference Timing Signal is used, the frequency deviation between nodes will be low, but could occur. If no accurate Reference Timing Signal is available, the local node reference oscillator must be relied upon. Then the RNC-Node B Synchronisation procedure can be used as a background process to find out the frequency deviation between nodes. + +In the RNC-Node B Node Synchronisation procedure, the RNC sends a DL NODE SYNCHRONISATION control frame to Node B containing the parameter T1. Upon reception of a DL NODE SYNCHRONISATION control frame, the Node B shall respond with UL NODE SYNCHRONISATION Control Frame, indicating T2 and T3, as well as T1 which was indicated in the initiating DL Node Synchronisation control frame (see Figure 3). + +![Figure 3: RNC-Node B Node Synchronisation. A timing diagram showing the exchange of control frames between SRNC and Node B. The SRNC timeline (RFN) has markers 4094, 4095, 0, 1, 2, 3, 4. The Node B timeline (BFN) has markers 147, 148, 149, 150, 151, 152, 153. A DL NODE SYNCHRONISATION frame is sent from SRNC at T1 (RFN 4094.250) and received by Node B at T2 (BFN 149.500). A UL NODE SYNCHRONISATION frame is sent from Node B at T3 (BFN 150.500) and received by SRNC at T4 (RFN 3.000). The diagram indicates that the round trip delay is (T2-T1) + (T4-T3).](21ad58fee90f2be50708ff541d225507_img.jpg) + +These two paths (T2-T1 + T4-T3) give together the Round Trip Delay + +SRNC + +4094 4095 0 1 2 3 4 RFN + +T1 + +**DL NODE SYNCHRONISATION** +[T1=40941.250] + +T2 + +T3 + +**UL NODE SYNCHRONISATION** +[T1=40941.250, T2=1492.500, T3=1505.000] + +T4 + +Node B + +147 148 149 150 151 152 153 BFN + +Figure 3: RNC-Node B Node Synchronisation. A timing diagram showing the exchange of control frames between SRNC and Node B. The SRNC timeline (RFN) has markers 4094, 4095, 0, 1, 2, 3, 4. The Node B timeline (BFN) has markers 147, 148, 149, 150, 151, 152, 153. A DL NODE SYNCHRONISATION frame is sent from SRNC at T1 (RFN 4094.250) and received by Node B at T2 (BFN 149.500). A UL NODE SYNCHRONISATION frame is sent from Node B at T3 (BFN 150.500) and received by SRNC at T4 (RFN 3.000). The diagram indicates that the round trip delay is (T2-T1) + (T4-T3). + +**Figure 3: RNC-Node B Node Synchronisation** + +In case of Node synchronization for HS-DSCH, the DRNC should transparently forward to the Node B a DL NODE SYNCHRONISATION control frame received from the SRNC, and should transparently forward to SRNC the UL NODE SYNCHRONISATION control frame received from the Node B. + +In case of macro-diversity with recombining in the DRNC, the DL NODE SYNCHRONISATION control frame is duplicated in the DRNC on the different links, while the UL NODE SYNCHRONISATION control frames received from all the Node B's are forwarded transparently to the SRNC (see Figure 4). + +![Figure 4: [FDD - RNC-Node B Node Synchronisation during soft handover with selection/recombining in the DRNC]](4356776ca004ecba5d599667a155d7d4_img.jpg) + +This diagram illustrates the timing relationships for FDD Node B synchronisation during a soft handover. It shows four horizontal timelines: SRNC (RFN 4094-4095-0-1-2-3-4), DRNC (RFN 1025-1026-1027-1028-1029-1030-1031), Node B-1 (BFN 2943-2944-2945-2946-2947-2948-2949), and Node B-2 (BFN 147-148-149-150-151-152-153). Vertical dashed lines represent radio frames. Arrows indicate Downlink (DL) and Uplink (UL) Node Synchronisation signals. DL signals are shown from SRNC to DRNC, DRNC to Node B-1, and Node B-1 to Node B-2. UL signals are shown from Node B-1 to DRNC and from Node B-2 to DRNC. Timing parameters like T1, T2-1, T3-1, T2-2, T3-2, T4-1, and T4-2 are indicated. The DRNC performs selection/recombining of these signals. + +Figure 4: [FDD - RNC-Node B Node Synchronisation during soft handover with selection/recombining in the DRNC] + +**Figure 4: [FDD - RNC-Node B Node Synchronisation during soft handover with selection/recombining in the DRNC]** + +### 6.1.2 Inter Node B Node Synchronisation + +In the FDD mode Inter Node B Node Synchronisation could be reached via the RNC-Node B Node Synchronisation in order to determine inter Node B timing reference relations. + +This could be used to determine Inter-cell relationships (considering $T\_cell$ ) which can be used in the neighbour cell lists in order to speed up and simplify cell search done by UE at handover. + +In TDD Inter Node B Node Synchronisation is used to achieve a common timing reference among Node B's (see Figure 5), that allows to support Intercell Synchronisation. + +![Figure 5: Synchronisation of BFNs through TDD Inter Node B Synchronisation](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +This diagram shows the synchronisation of multiple Node Bs through TDD Inter Node B Synchronisation. It features three horizontal timelines: RNC (RFN 4094-4095-0-1-2-3-4), Node B-1 (BFN-1 147-148-149-150-151-152-153), and Node B-2 (BFN-2 402-403-404-405-406-407-408). Vertical dashed lines represent radio frames. Arrows indicate synchronisation signals originating from the RNC and being received by both Node B-1 and Node B-2, establishing a common timing reference across the different Node Bs. + +Figure 5: Synchronisation of BFNs through TDD Inter Node B Synchronisation + +**Figure 5: Synchronisation of BFNs through TDD Inter Node B Synchronisation** + +In TDD Inter Node B Node Synchronisation may be achieved via a standardised synchronisation port (see subclause 6.1.2.1) that allows to synchronise the Node B to an external reference. + +Another option to achieve the Inter Node B Node Synchronisation in a TDD system is the synchronisation of cells or Node Bs via the air interface ([3.84Mcps TDD - see subclause 6.1.2.2], [1.28Mcps TDD - see subclause 6.1.2.3]). This feature is not available for 7.68Mcps TDD. + +#### 6.1.2.1 TDD Node B Synchronisation Ports + +This subclause defines the Node B input and an output synchronisation ports that can be used for Inter Node B Node Synchronisation. These synchronisation ports are optional. + +The input synchronisation port (SYNC IN) allows the Node B to be synchronised to an external reference (e.g. GPS), while the output synchronisation port (SYNC OUT) allows the Node B to synchronise directly another Node B (see Figure 6). + +![Figure 6: Usage of Synchronisation Ports. The diagram shows an 'External Sync. Source' connected to an 'Adaptor'. The 'Adaptor' is connected to the 'Sync Input Port' of a 'Node B'. This 'Node B' is connected to the 'Sync Output Port' of another 'Node B'. This second 'Node B' is connected to the 'Sync Input Port' of a third 'Node B'. Finally, the third 'Node B' is connected to the 'Sync Output Port' of a fourth 'Node B'. Each 'Node B' block contains labels for 'Sync Input Port' and 'Sync Output Port'.](10781f43062bf3e9601a1e086710556c_img.jpg) + +Figure 6: Usage of Synchronisation Ports. The diagram shows an 'External Sync. Source' connected to an 'Adaptor'. The 'Adaptor' is connected to the 'Sync Input Port' of a 'Node B'. This 'Node B' is connected to the 'Sync Output Port' of another 'Node B'. This second 'Node B' is connected to the 'Sync Input Port' of a third 'Node B'. Finally, the third 'Node B' is connected to the 'Sync Output Port' of a fourth 'Node B'. Each 'Node B' block contains labels for 'Sync Input Port' and 'Sync Output Port'. + +**Figure 6: Usage of Synchronisation Ports** + +This allows connecting Node B's in a daisy chain configuration, so that a single external reference is enough and all remaining Node B's can be synchronised (e.g. in case of indoor operation). + +The Node B starts the synchronisation to the external reference when a valid input synchronisation signal is detected at the input synchronisation port. + +If a valid synchronisation signal is detected, the Node B regenerates that signal at its output synchronisation port. + +The electrical characteristics of the synchronisation ports shall conform to RS422 TIA/EIA 422 B [6] (output synchronisation port: subclause 4.1; input synchronisation port: subclause 4.2). + +The synchronisation signal (illustrated in Figure 7a) is a 100 Hz signal having positive pulses of width between 5 $\mu\text{s}$ and 1 ms, with the following exceptions: + +- when $(\text{SFN mod } 256 = 0)$ and not $(\text{SFN mod } 4096 = 0)$ , the pulse shall have a width between 2 ms and 3 ms. + +This signal establishes the 10 ms frame interval, the 2.56 s multiframe interval, and the 4096 frames SFN period. The start of all frames in the cell of the node B is defined by the falling edge of the pulse. The required accuracy for the phase difference between the start of the 10ms frame interval is defined in TS 25.123 [15]. The time delay from the falling edge of the signal at the SYNC IN port to the start of the transmitted radio frame shall not exceed 500ns. + +The start of the 256 frame period is defined by the falling edge of the pulse corresponding to the frames where $\text{SFN mod } 256 = 0$ (i.e. of width between 2 ms and 3 ms, or between 4ms and 5 ms, respectively). + +The start of the 4096 frame period is defined by the falling edge of the pulse corresponding to the frames where $\text{SFN mod } 4096 = 0$ (i.e. of width between 4 ms and 5 ms). + +The synchronisation signal at the input port shall have frequency accuracy better than the one of the Node B. + +The relative phase difference of the synchronisation signals at the input port of any Node B in the synchronised area shall not exceed 2.5 $\mu\text{s}$ . + +![Figure 7: Synchronisation signal with 256 frames markers (Release 99). The diagram shows a periodic square wave signal. A 10 ms interval is marked between two consecutive pulses. A 2.56 s interval is marked between two special pulses, which are indicated by downward arrows. The duration of a pulse is specified as >2 ms and <5 ms. The interval between a special pulse and the next regular pulse is specified as >5 μs and <1 ms.](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +Figure 7: Synchronisation signal with 256 frames markers (Release 99). The diagram shows a periodic square wave signal. A 10 ms interval is marked between two consecutive pulses. A 2.56 s interval is marked between two special pulses, which are indicated by downward arrows. The duration of a pulse is specified as >2 ms and <5 ms. The interval between a special pulse and the next regular pulse is specified as >5 μs and <1 ms. + +**Figure 7: Synchronisation signal with 256 frames markers (Release 99)** + +![Figure 7a: Synchronisation signal with 256 and 4096 frames markers (Release 4). This diagram extends Figure 7 to show two different frame marker periods. It shows a 2.56 s interval between two special pulses (SFN=0) and a 40.96 s interval between another pair of special pulses (SFN=0). The 10 ms interval between regular pulses is also shown. Pulse durations and intervals are consistent with Figure 7: pulse width >2 ms <5 ms, interval between special and regular pulse >5 μs <1 ms, and interval between two special pulses >4 ms <5 ms.](c531b0e7e06671c980f2ed0d753d2fbc_img.jpg) + +Figure 7a: Synchronisation signal with 256 and 4096 frames markers (Release 4). This diagram extends Figure 7 to show two different frame marker periods. It shows a 2.56 s interval between two special pulses (SFN=0) and a 40.96 s interval between another pair of special pulses (SFN=0). The 10 ms interval between regular pulses is also shown. Pulse durations and intervals are consistent with Figure 7: pulse width >2 ms <5 ms, interval between special and regular pulse >5 μs <1 ms, and interval between two special pulses >4 ms <5 ms. + +**Figure 7a: Synchronisation signal with 256 and 4096 frames markers (Release 4)** + +##### Synchronisation by a GPS receiver + +The signal transmitted by a Global Positioning System (GPS) satellite indicates the GPS time that provides an absolute time reference. This makes the GPS receiver suitable for Inter Node B Node Synchronisation. + +Inter Node B Node Synchronisation is achieved by relating the synchronisation signal (at the input synchronisation port) to the GPS signal. Since the period of this signal is 2.56 s, this implies that every 6400 frames the start of a 256 frame period coincides with an integer GPS second, i.e. a multiframe shall start when $\text{GPS time mod } 64 = 0$ . + +In general, at each start of a GPS second indicating the GPS time in seconds, the associated full SFN (the 12 bits value) can be derived as: $\text{SFN} = (\text{GPS time} * 100) \bmod 4096$ . If the synchronisation port signal shall be derived from GPS, the special pulses for the 256 frames period and the 4096 frames period shall be present in the synch port signal when $\text{SFN mod } 256 = 0$ or $\text{SFN mod } 4096 = 0$ , respectively, where the SFN in these equations is linked to the GPS time by the said equation. + +##### Synchronisation by a Galileo receiver + +The signal transmitted by a Galileo receiver indicates the Galileo time that provides an absolute time reference. This makes the Galileo receiver suitable for Inter Node B Node Synchronisation. + +A Galileo receiver furthermore ensures integrity with a Time To Alert of 6s. The receiver shall only provide the date $t$ , where $t = t_0 + D_t$ , $D_t$ representing 15s (duration evaluated by the internal clock of the receiver) and $t_0$ being the Galileo date evaluated 15s earlier, if it has not received and alert from the Galileo system between $t_0$ and $t$ . In the following paragraphs, $t$ so calculated is called Galileo time. + +Inter Node B Node Synchronisation is achieved by relating the synchronisation signal (at the input synchronisation port) to the Galileo signal. Since the period of this signal is 2.56 s, this implies that every 6400 frames the start of a 256 frame period coincides with an integer Galileo second, i.e. a multiframe shall start when $\text{Galileo time mod } 64 = 0$ . + +In general, at each start of a Galileo second indicating the Galileo time in seconds, the associated full SFN (the 12 bits value) can be derived as: $\text{SFN} = (\text{Galileo time} * 100) \bmod 4096$ . If the synchronisation port signal shall be derived from Galileo, the special pulses for the 256 frames period and the 4096 frames period shall be present in the synch port signal when $\text{SFN} \bmod 256 = 0$ or $\text{SFN} \bmod 4096 = 0$ , respectively, where the SFN in these equations is linked to the Galileo time by the said equation. + +##### Backward compatibility to Release 99 + +The Release 4 synchronisation port definition is backward compatible with the Release 99 synchronisation port in the following sense: It is possible to feed a Release 99 Node B with the Release 4 synchronisation port signal. This results from the fact that the Release 4 synchronisation port pulses defined for $\text{SFN} \bmod 256 = 0$ and those defined for $\text{SFN} \bmod 4096 = 0$ both meet the pulse width tolerance defined for $\text{SFN} \bmod 256 = 0$ in Release 99. So the Release 99 Node B will recognise these two classes of Release 4 pulses as valid Release 99 pulses for definition of the 256 frames multiframe start. The Release 99 Node B will, however, ignore the differences between the 256 frames period pulse and the 4096 frames period pulse: The result is the 256 frames multiframe synchronisation as specified for Release 99. + +The opposite scenario, however, i.e. connecting a Release 99 synchronisation port signal (without the 4096 frames marker) to a Release 4 Node B, shall be excluded. This would cause confusion for the "synchronisation via radio interface" procedure. The TDD cells in Release 4 shall be either "reference" cells where the SFN is fully synchronised to an external reference, or they shall be "non-reference" without any external, local frame clock reference. + +#### 6.1.2.2 TDD Inter Node B Node Synchronisation procedure [3.84Mcps TDD] + +The Node B synchronisation procedure is an optional procedure based on transmissions of cell synchronisation bursts in predetermined PRACH time slots according to an RNC schedule. Such soundings between neighbouring cells facilitate timing offset measurements by the cells. The measured timing offset values are reported to the RNC for processing. The RNC generates cell timing updates that are transmitted to the Node B and cells for implementation. + +The synchronisation procedure has four phases to bring a network into a synchronised operation, the preliminary phase, the frequency acquisition phase, the initial phase and the steady-state phase. The procedure for late entrant cells is slightly different and is described separately. + +For synchronisation via the air interface it has to be considered that as long as a cell is not synchronised the cell may interfere the neighbouring cells. This applies especially in case of late entrant cells where first the new cell has to be setup before the synchronisation procedure starts. By this Cell Setup procedure the SCH is already transmitting. The RNC shall therefore disable the downlink time slots on Cell Setup procedure by means of the *Time Slot Status* IE. When the cell synchronisation has been performed the downlink time slots shall be enabled by means of the Cell Reconfiguration procedure. + +There should be at least one cell in each RNS which is synchronised by an external reference (e.g. GPS receiver). The RNC evaluates the absolute time thanks to these reference cells. + +If the source is a Galileo receiver, the RNC shall only send corrections based on time $t = t_0 + D_t$ with $D_t = 15\text{s}$ (duration evaluated by the RNC's internal clock), and $t_0$ the date evaluated by the Galileo measurement 15s earlier, if the Galileo receiver has not received alert message between $t_0$ and $t$ . + +##### 6.1.2.2.1 Preliminary Phase + +- 1) The reference cells, synchronised by an external reference, shall initialise their SFN counter so that the frame with $\text{SFN}=0$ starts on January 6, 1980 at 00:00:00 GMT. +- 2) The RNC has to be informed at which of the cells the external reference clock is connected. Therefore, a 'Reference Clock availability' indicator is added within the RESOURCE STATUS INDICATION message that is sent from the Node B to the RNC when a Local Cell becomes existing at the Node B. +- 3) At Cell Setup a 'Reference SFN offset' may be given to the cells where the reference clock is connected in order to separate the synchronisation bursts from different RNC areas. +- 4) The RNC has to retrieve the reference time from the cells with the reference clock. For the reference time retrieval the DL Transport Channels Synchronisation procedure or the Node Synchronisation procedure on the PCH frame protocol (see TS 25.435 [4]) shall be used. The Node B shall consider the SFN derived from the synchronisation port and the Reference SFN offset given by the RNC. +- 5) Now the RNC proceeds by updating the timing of all the remaining cells in the RNS, instructing them to adjust their clocks. Therefore, first the DL Transport Channels Synchronisation procedure on the PCH frame protocol + +shall be performed in order to determine the deviation from the reference SFN. The RNC then sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST message to all the cells for SFN update, apart from the one(s) containing the reference clock. The cells shall adjust their SFN and frame timing accordingly. + +##### 6.1.2.2.1A Frequency Acquisition Phase + +The frequency acquisition phase is used to bring cells of an RNS area to within frequency limits prior to initial synchronisation. No traffic is supported during this phase. + +- 1) The cell(s) identified as reference cell, i.e. external reference clock is connected to, shall transmit continuously cell synchronisation bursts in every time slot where possible according to the information's given in the CELL SYNCHRONISATION INITIATION REQUEST message. +- 2) All other cells are considered as unlocked (i.e. not in frequency lock) shall listen for transmission from other cells and perform frequency locking to any transmission received. For setting the parameters within the Node B to listen for transmission from other cells, the CELL SYNCHRONISATION INITIATION REQUEST message is used. +- 3) A cell shall signal completion of frequency acquisition to the RNC, as soon as it has locked its frequency to the received signal, fulfilling the Frequency Stability requirement set in TS 25.105 [17]. +- 4) If the cell(s) have received transmission request on instructing the frequency acquisition and the cell(s) have performed frequency locking, the cell(s) shall begin transmitting the specified code for frequency locking of other cells. +- 5) When the RNC has received completion of frequency acquisition signals from all cells the frequency acquisition phase is completed. + +##### 6.1.2.2.1B Initial Phase + +The procedure for initial synchronisation is used to bring cells of an RNS area into synchronisation at network start up. No traffic is supported during this phase. + +- 1) For the synchronisation procedure it is useful to know which cells can “hear” each other. Therefore, all cells are instructed to transmit their cell synchronisation bursts in turn one after the other. The same cell synchronisation burst code and code offset is used by all cells. +- 2) Each cell shall listen for transmissions from other cells. Each cell shall report the timing and received SIR of successfully detected cell sync bursts to the RNC. +- 3) Upon reception of a CELL SYNCHRONISATION ADJUSTMENT message the cell shall adjust its timing accordingly. The timing adjustment shall be completed before the CELL SYNCHRONISATION ADJUSTMENT RESPONSE message is sent. It shall be implemented by adjusting the timing and/or tuning the clock frequency. +- 4) Steps 1 to 3 are repeated as often as necessary in order to reach the minimum synchronisation accuracy defined in TS 25.224 [16]. This serves the purpose to bring the network into tight synchronisation. The SIR value within the cell sync burst reports is used by the RNC to define the schedule for the steady-state phase. I.e. to define when which cells transmit a cell synchronisation burst and when which cell synchronisation bursts shall be received. Cells which are sufficiently separated can be allowed to send the same cell synchronisation burst at the same time. Cells which are not sufficiently separated have to use different cell synchronisation codes and code offsets for distinctions. + +##### 6.1.2.2.2 Steady-State Phase + +The steady-state phase allows cells to reach and/or maintain the required synchronisation accuracy. With the start of the steady-state phase traffic is supported in a cell. The steady-state phase starts with the Cell Synchronisation Reconfiguration procedure (see TS 25.433 [3]) which defines the synchronisation schedule. I.e. each cell gets the information when to transmit a cell synchronisation burst and when the individual cell synchronisation bursts from the neighbouring cells shall be measured. + +For definition of the SFN when the cell shall transmit or receive cell synchronisation bursts, the SFN period is divided into cycles that have the same schedule. Within each cycle the Frame numbers for the cell synchronisation bursts are calculated by the number of repetitions per cycle and by an offset. Code and code offset are used to identify the individual cell synchronisation bursts. + +- 1) The cell shall transmit a cell synchronisation burst and measure cell synchronisation bursts from neighbouring cells according to the information's given in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. Reception times for all relevant codes and code offsets shall be reported to the RNC with the CELL SYNCHRONISATION REPORT message. +- 2) Upon determination of an error in timing, the RNC adjusts the cell timing by means of the CELL SYNCHRONISATION ADJUSTMENT message. The timing adjustment shall be started at the beginning of the frame with the SFN given in the command. It shall be completed by the next cell synchronisation slot. Timing adjustments shall be implemented via gradual steps at the beginning of a frame. The whole adjustment shall be implemented with maximum stepsize of one sample per frame. +- 3) Step 1 and 2 continue indefinitely + +##### 6.1.2.2.3 Late-Entrant Cells + +The scheme for introducing new cells into a synchronised RNS is as follows: + +- 1) Late entrant cells (new cells being added without reference clock) or cells recovering from unavailability shall first be roughly synchronised. Therefore, first the DL Transport Channels Synchronisation procedure on the PCH frame protocol shall be performed in order to determine the deviation from the reference SFN. The RNC then sends a CELL SYNCHRONISATION ADJUSTMENT message to the late-entrant cells for SFN update. +- 2) Frequency acquisition of the late entrant cell is started by instructing the late entrant cell first to listen to the regular schedule of cell sync bursts of the surrounding cells. The transmission schedule of the surrounding cells shall be signalled to the late entrant cell within the CELL SYNCHRONISATION INITIATION REQUEST message. Frequency locking is reported using the CELL SYNCHRONISATION REPORT message. +- 3) In addition or instead of a regular schedule a single common cell synchronisation burst is transmitted in parallel by cells which are synchronised in the system and which are preferably the ones surrounding the late-entrant cell. The single cell synchronisation burst is initiated by means of the CELL SYNCHRONISATION INITIATION REQUEST message to the surrounding cells. +- 4) The late entrant cell shall correlate against the cell synchronisation burst according to the measurement information within the CELL SYNCHRONISATION INITIATION REQUEST message. The reception window shall be +/- 3 frames around the SFN frame given in the measurement information. The late entrant cell shall take the earliest reception as the timing of the system and adjusts its own timing and SFN number accordingly. +- 5) Thereafter, the late entrant cell shall start regular measurements after the reception of a CELL SYNCHRONISATION RECONFIGURATION REQUEST message and it shall report the timing of the measured cell synchronisation bursts to the RNC. In turn, the late entrant cell receives its own schedules for synchronisation transmissions and receptions and enters the steady-state phase. + +#### 6.1.2.3 TDD Inter Node B Node Synchronisation procedure [1.28Mcps TDD] + +The Node B synchronization procedure for 1.28 Mcps TDD is an optional procedure based on the usage of the transmissions of the DwPCH to achieve Node B synchronisation over the air. + +The main difference to the corresponding procedure for 3.84 Mcps TDD is the use of the DwPCH instead of the PRACH for synchronisation burst transmission and reception. + +In addition, some extensions for the Steady State phase compared to the 3.84Mcps TDD solution have been specified: + +- The ability to perform averaging of correlation results of several received SYNC\_DL codes within a Synchronisation Cycle; +- The ability of the cell to perform self-adjustment of the timing based on measurements, and to report the accumulated adjustments to the RNC. + +The synchronization procedure has three phases to bring a network into a synchronized operation, the preliminary phase, the initial phase and the steady-state phase. In addition there is a procedure for late entrant cells. + +For synchronisation via the air interface it has to be considered that as long as a cell is not synchronised the cell may interfere the neighbouring cells. This applies especially in case of late entrant cells where first the new cell has to be setup before the synchronisation procedure starts. The RNC shall therefore disable the downlink time slots on Cell + +Setup procedure by means of the *Time Slot Status* IE. When the cell synchronisation has been performed the downlink time slots shall be enabled by means of the Cell Reconfiguration procedure. + +There should be at least one cell in each RNS which is synchronised by an external reference (e.g. GPS receiver). The RNC evaluates the absolute time thanks to these "master cells". + +If the source is a Galileo receiver, the RNC shall only send corrections based on time $t = t_0 + D_t$ with $D_t = 15\text{s}$ (duration evaluated by the RNC's internal clock), and $t_0$ the date evaluated by the Galileo measurement 15s earlier, if the Galileo receiver has not received alert message between $t_0$ and $t$ . + +##### 6.1.2.3.1 Preliminary Phase + +- 1) The "master cells", synchronised by an external reference, shall initialise their SFN counter so that the frame with SFN=0 starts on January 6, 1980 at 00:00:00 GMT. +- 2) The RNC has to be informed which of the cells are master cells. Therefore, a "Reference Clock availability" indicator is added within the RESOURCE STATUS INDICATION message that is sent from the Node B to the RNC when a Local Cell becomes existing at the Node B. +- 3) At Cell Setup a "Reference SFN offset" may be given to the cells where the reference clock is connected in order to separate the synchronisation bursts from different RNC areas. +- 4) The RNC has to retrieve the reference time from the cells with reference clock. For the reference time retrieval the DL Transport Channels Synchronisation procedure or the Node Synchronisation procedure on the PCH frame protocol (see TS 25.435 [4]) shall be used. The Node B shall consider the SFN derived from the synchronisation port and the Reference SFN offset given by the RNC. +- 5) Now the RNC proceeds by updating the timing of all the remaining cells in the RNS, instructing them to adjust their clocks. Therefore, first the DL Transport Channels Synchronisation procedure or the Node Synchronisation procedure on the PCH frame protocol shall be performed in order to determine the deviation from the reference SFN. The RNC then sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST message to all the cells for SFN update, apart from the one(s) containing the reference clock. The cells shall adjust their SFN and frame timing accordingly. + +##### 6.1.2.3.2 Initial Phase + +The procedure for initial synchronization is used to bring cells of an RNS area into synchronization at a network start up. No traffic is supported during this phase: + +- 1) For the synchronisation procedure it is useful to know which cells can "hear" each other. Therefore, all cells are instructed to transmit their SYNC\_DL Codes one-at-a-time. +- 2) Each cell shall listen to transmissions from other cells based on RNC schedule for initial synchronisation. The SYNC\_DL sequence is transmitted continuously throughout each radio frame period. Each cell shall report the timing and received $S/(N+I)$ of successfully detected SYNC\_DL codes to the RNC. +- 3) Upon reception of a CELL SYNCHRONISATION ADJUSTMENT message the cell shall adjust its timing accordingly. The timing adjustment shall be completed before the CELL SYNCHRONISATION ADJUSTMENT RESPONSE message is sent. It shall be implemented by adjusting the timing and/or tuning the clock frequency. +- 4) Steps 1 to 3 are repeated as often as necessary in order to reach the minimum synchronisation accuracy defined in TS 25.224 [16]. This serves the purpose to bring the network into tight synchronisation. The rapid updates allow the correction of the clock frequencies as well as the clock timings to be adjusted in a short timeframe. This rapidly brings the network into tight synchronization. The $S/(N+I)$ values are used to define the schedule for the steady-state phase. Cells which are sufficiently separated or use different frequency bands can be allowed to send the same SYNC\_DL code at the same time. Cells which are not sufficiently separated have to use different SYNC\_DL codes for distinctions. + +##### 6.1.2.3.3 Steady-State Phase + +The steady-state phase allows the system to reach or maintain the required synchronization accuracy. There is a "basic method", and there are extensions which may be required under adverse circumstances, to achieve reliable measurements of SYNC\_DL codes from neighbour cells, and to achieve immediate, fast timing corrections while reducing the Iub interface signalling load. + +###### 6.1.2.3.3.1 Basic method + +With the start of the steady-state phase traffic is supported in a cell. The steady-state phase starts with the Cell Synchronisation Reconfiguration procedure (see TS 25.433 [3]) which defines the synchronisation schedule. I.e. each cell gets the information when to transmit a SYNC\_DL code and when the individual SYNC\_DL codes from the neighbouring cells shall be measured. + +For definition of the "Synchronisation Frames", i.e. the SFNs when the cell shall transmit or receive SYNC\_DL codes, the SFN period is divided into Synchronisation Cycles that include the same number of Synchronisation Frames. The interval from one Synchronisation Frame to the next is called a Repetition Period. Each Synchronisation Cycle has the same transmit and receive schedule. + +To be specific, the SFNs which are used as Synchronisation Frames are calculated from the "Number of cycles per SFN period" and the "Number of Repetitions per Cycle" as follows (where Repetition Period may be a non-integer number): + +Cycle length: $4096 / \text{value of the IE 'Number of cycles per SFN period'}$ + +Repetition period: $\text{Cycle length} / \text{value of IE 'Number of repetitions per cycle period'}$ + +Synchronisation Frame SFN = $\text{floor}((k-1) * \text{Cycle length} + (i-1)* \text{Repetition period})$ + +$k = \{1, 2, 3, \dots, \text{Number of cycle per SFN period}\} = \text{cycle counter}$ + +$i = \{1, 2, 3, \dots, \text{Number of repetitions within cycle period}\} = \text{Repetition counter}$ + +This provides the set of Synchronisation Frames SFN within the SFN period or 4096 frames. Then the procedure works as follows: + +- 1) Each of the cells transmits its own predetermined SYNC\_DL sequence on the DwPCH and receives the specific SYNC\_DL code of neighbouring cells according to the information given in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. All cells shall report the reception timing for each specific SYNC\_DL code to the RNC with the CELL SYNCHRONISATION REPORT message. +- 2) Upon determination of an error in timing, the RNC adjusts the cell timing by means of the CELL SYNCHRONISATION ADJUSTMENT message. The timing adjustment shall be started at the beginning of the frame with the SFN given in the command. It shall be completed by the next cell synchronisation slot. Timing adjustments shall be implemented via gradual steps at the beginning of a frame. The whole adjustment shall be implemented with maximum stepsize of one sample per frame. +- 3) Steps 1 and 2 continue indefinitely. + +###### 6.1.2.3.3.2 Extended method + +The following extensions of the basic scheme are available: Averaging of measurements, and self-adjustment of the radio interface timing. + +- 1) **Averaging of measurements:** For increasing the S/(N+I) values of measured SYNC\_DL codes, it shall be possible for a cell to apply an averaging of SYNC\_DL codes received from the same neighbouring cell, before deriving the receive timing from the correlation result (During the averaging period, the timing in the neighbouring cells transmitting the SYNC\_DL codes should be "frozen" in order to avoid "blurring" of the averaged measurements). This optional averaging is supported by subdividing the Synchronisation Cycles into a number of "Subcycles" where in each Subcycle, a full set of SYNC\_DL samples is received, and by averaging over the subcycles, such that at the end of a Synchronisation Cycle a full set of timing deviation measurements with improved S/(N+I) is available. The number of subcycles is configured by the CRNC. + +This introduction of "Subcycles" implies a change in the equations how to calculate the Synchronisation Frames SFN: The *Number of subcycles per cycle period* IE is taken into account as follows: + +Cycle length: $4096 / \text{value of the IE 'Number of cycles per SFN period'}$ + +Subcycle length: $\text{Cycle length} / \text{value of IE 'Number of subcycles per cycle period'}$ + +Repetition period: $\text{Subcycle length} / \text{value of IE 'Number of repetitions per subcycle period'}$ + +Synchronisation Frame SFN = $\text{floor}((k-1) * \text{Cycle length} + (l-1)* \text{Repetition period})$ + +$k = \{1, 2, 3, \dots, \text{Number of cycle per SFN period}\} = \text{cycle counter}$ + +$j = \{1, 2, 3, \dots, \text{Number of subcycles per cycle}\} = \text{subcycle counter}$ + +$I = \{1, 2, 3, \dots, \text{Number of repetitions within cycle period}\} = \text{Repetition counter}$ + +This provides the set of Synchronisation Frames SFN within the SFN period of 4096 frames. + +NOTE 1: Subcycle length and Repetition period can have non-integer values. + +NOTE 2: If the number of subcycles per cycle is set to unity, the "subcycles" are identical to the "cycles", and no averaging occurs. + +At the end of each Cycle, a full set of Time of Arrival measurements is available, with or without averaging. So these measurements can be further processed as in the basic method. + +- 2) **Self-adjustment of the radio interface timing:** It should be possible for the RNC to allow the Node B to perform a timing correction based on its own measurements autonomously without requiring the RNC to calculate the amount of timing correction. This reduces the amount of Iub interface signalling while allowing for fast corrections of timing deviations. – So the RNC shall indicate the possibility of self-adjustment, by including a *Propagation Delay Compensation* IE into the CELL SYNCHRONISATION RECONFIGURATION message, in addition to the SYNC\_DL code to measure. Whenever this optional IE is present, the Node B should use the respective SYNC\_DL measurement (after potential averaging) to perform the self-adjustment at the end of a Synchronisation Cycle. – Whenever this IE is not present, no self-adjustment shall be performed. – In each measurement report where the Node B reports the measured Time of Arrival values, the Node B shall also include the accumulated phase adjustments since the last measurement report to the RNC for surveillance purposes. + +##### 6.1.2.3.4 Late-Entrant Cells + +The scheme for introducing new cells into a synchronized RNS is as follows: + +- 1) Late-entrant cells (new cells being added without reference clock) or cells recovering from unavailability shall first be roughly synchronised via Iub interface messages. Therefore, first the DL Transport Channels Synchronisation procedure or the Node Synchronisation procedure on the PCH frame protocol shall be performed in order to determine the deviation from the reference SFN. The RNC then sends a CELL SYNCHRONISATION ADJUSTMENT message to the late-entrant cells for SFN update. +- 2) The RNC should tell the late-entrant which SYNC\_DL codes and carrier frequencies to listen for, corresponding to its neighbour cells signalled within the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. +- 3) The late entrant then reports the timing of the SYNC\_DL codes using the CELL SYNCHRONISATION REPORT message. The RNC knows the location of all cells and therefore should be able to compute a timing adjustment for the late-entrant that takes into account the expected propagation delays between the late-entrant and its neighbouring cells. The RNC adjusts the cell and the cycle is repeated until the RNC is satisfied that the cell's timing accuracy fulfils the requirements to be allowed to enter the Steady State phase. + +#### 6.1.2.4 Node B synchronisation for 3.84Mcps TDD MBSFN IMB + +In 3.84Mcps TDD MBSFN IMB operation a timing reference of high accuracy is required at the Node Bs in the MBSFN. The required accuracy of Inter Node B Node Synchronisation may be achieved via an external reference, e.g. GPS or other means. + +# 7 Transport Channel Synchronisation + +## 7.1 General + +The Transport Channel (or L2) synchronisation provides a L2 common frame numbering between UTRAN and UE (frame synchronisation between the L2 entities). This frame number is the Connection Frame Number (CFN) and it is associated at L2 to every TBS and passed to L1: the same CFN is received on the peer side associated with the same TBS. + +The CFN is not transmitted in the air interface for each TBS, but is mapped by L1 to the SFN of the first radio frame used for the transmission of the TBS (the SFN is broadcast at L1 in the BCH). The mapping is performed via the Frame Offset parameters (see Figure 8). + +![Figure 8: Transport Channel Synchronisation diagram showing the relationship between RNC, Node B, and UE DL/UL frames, CFN, and SFN.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +The diagram illustrates the transport channel synchronisation process across three layers: RNC, Node B, and UE. + +- RNC Layer:** Shows a sequence of frames numbered 147 to 153. A **DL DATA FRAME [CFN=150]** is shown being transmitted from the RNC to Node B. A **UL DATA FRAME [CFN=150]** is shown being received by the RNC from Node B. The horizontal axis is labeled **CFN**. +- Node B Layer:** Shows two sequences of frames. The top sequence (147-153) corresponds to the CFN. The bottom sequence (1171-1177) corresponds to the **SFN**. A **DL RADIO FRAME** is shown being transmitted from Node B to UE DL at SFN 1174. A **UL RADIO FRAME** is shown being received by Node B from UE DL at SFN 1174. A **Receiving Window** and **TOA** (Time of Arrival) are indicated for the UL radio frame. The horizontal axis is labeled **CFN** and **SFN**. A **Frame Offset** is indicated between the CFN and SFN axes. +- UE DL Layer:** Shows a sequence of frames numbered 147 to 153, corresponding to the CFN. The horizontal axis is labeled **CFN**. + +Arrows represent the first chip or first bit in frames. A note indicates: *UL is delayed To compared with DL*. A caption at the bottom states: *Frame arrows represent first chip or first bit in frames, TTI=10 ms, [FDD - Chip Offset = 0]*. + +Figure 8: Transport Channel Synchronisation diagram showing the relationship between RNC, Node B, and UE DL/UL frames, CFN, and SFN. + +**Figure 8: Transport Channel Synchronisation** + +This transport channel synchronisation mechanism is valid for all downlink transport channels. + +In case of soft handover (i.e. only for DCHs), the Frame Offsets of the different radio links are selected in order to have a timed transmission of the diversity branches on the air interface (see Figure 9). + +![Figure 9: [FDD - Transport Channel Synchronisation during soft handover]](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates the timing relationship between the RNC, Node B-1, Node B-2, and the UE during a soft handover. The horizontal axis represents the Chip Number (CFN) for the RNC and UE, ranging from 147 to 153. Vertical dashed lines indicate frame boundaries. The RNC transmits a DL DATA FRAME (CFN=150) which is received by Node B-1 and Node B-2. Node B-1 and Node B-2 also transmit UL DATA FRAMES (CFN=150) which are received by the RNC. The UE receives a DL RADIO FRAME from Node B-1 and Node B-2. The diagram shows that the UE's DL timing is synchronized with the RNC's DL timing. The Frame Offset and SFN are indicated for Node B-1 and Node B-2. The caption states: 'Frame arrows represent first chip or first bit in frames, TTI=10 ms, Chip Offset = 0'. + +Figure 9: [FDD - Transport Channel Synchronisation during soft handover] + +Figure 9: [FDD - Transport Channel Synchronisation during soft handover] + +## 7.2 Timing adjustment and Time of Arrival monitoring on Iub/Iur interfaces + +A receiving window is configured in Node B at Transport bearer Setup and Reconfiguration for DL frames (TOAWS and TOAWE). The purpose is to make it possible to supervise whether data frames are received in the window or not. When a frame is received outside that window, a response is sent to RNC by means of a TIMING ADJUSTMENT control frame containing the Time of Arrival information (TOA) (see Figure 10 and Figure 11). This allows the L1 to indicate to L2 (through the L1-MAC primitive carried by the TIMING ADJUSTMENT control frame) the necessity to adjust the timing of the DL transmission, in order to control and minimise the transmission delay and the buffering time for the transmission on the air interface (i.e. to ensure that the TBS does not arrive too much in advance respect to the transmission time). + +![Figure 10: Illustration of TOAWS, TOAWE, LTOA and TOA. The diagram shows a timeline 't' with arrival markers: Early (blue triangle), OK (green triangle), Late (yellow triangle), and Too late (red triangle). It defines a 'Receiving Window' between TOAWS and TOAWE. LTOA is the Latest Time of Arrival. Tproc is the processing time. Below the timeline, DL RADIO FRAMES are shown with CFN (149-153) and SFN (1635-1639) values, indicating a Frame Offset.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +DL DATA FRAME #152 received:     **Early**     **OK**     **Late**     **Too late** + +*[FDD - Note: in this figure it is assumed that Chip Offset = 0]* + +| | | | | +|-------|------------------------|------------|------------------------------------------------------| +| TOA | Time Of Arrival | TOAWE | TOA Window Endpoint | +| LTOA | Latest Time Of Arrival | $T_{proc}$ | Processing time before transmission on air-interface | +| TOAWS | TOA Window Startpoint | | | + +Figure 10: Illustration of TOAWS, TOAWE, LTOA and TOA. The diagram shows a timeline 't' with arrival markers: Early (blue triangle), OK (green triangle), Late (yellow triangle), and Too late (red triangle). It defines a 'Receiving Window' between TOAWS and TOAWE. LTOA is the Latest Time of Arrival. Tproc is the processing time. Below the timeline, DL RADIO FRAMES are shown with CFN (149-153) and SFN (1635-1639) values, indicating a Frame Offset. + +**Figure 10: Illustration of TOAWS, TOAWE, LTOA and TOA** + +The window could be defined to have a margin before LTOA ( $TOAWE > 0$ ). This is to indicate to RNC that data frames are a bit late but they are still processed by Node B. In this case, data frames are received after TOAWE but before LTOA. + +Using this window definition and supervising method, it is possible to determine the correct timing for sending data frames from the RNC over Iur/ Iub. + +The window size and position is chosen with respect to expected data frame delay variation and different macro-diversity leg delays. + +![Figure 11: Timing Adjustment Procedure. A sequence diagram between SRNC and Node B. SRNC sends a DL DATA FRAME [CFN=150] which arrives at Node B within the Receiving Window. Node B calculates the TOA and sends a TIMING ADJUSTMENT [TOA=-5.250 ms] back to SRNC. Both entities have synchronized CFN timelines (147-153).](b78854f39d5fe3c45a918555e158ee58_img.jpg) + +Figure 11: Timing Adjustment Procedure. A sequence diagram between SRNC and Node B. SRNC sends a DL DATA FRAME [CFN=150] which arrives at Node B within the Receiving Window. Node B calculates the TOA and sends a TIMING ADJUSTMENT [TOA=-5.250 ms] back to SRNC. Both entities have synchronized CFN timelines (147-153). + +**Figure 11: Timing Adjustment Procedure** + +In order to monitor the TOA when no DL DATA FRAMES are sent, a synchronisation procedure is defined in the Iub/Iur frame protocols (TS 25.435 [4], TS 25.427 [5]). This procedure makes use of UL and DL SYNCHRONISATION control frames (see Figure 12 and Figure 13). The SRNC sends DL SYNCHRONISATION control frame containing the CFN in which the control frame should be received by the Node B. When the Node B receives the DL SYNCHRONISATION control frame, it always replies with an UL SYNCHRONISATION control frame containing the TOA, even if the DL SYNCHRONISATION control frame is received within the receiving window as in Figure 12. + +![Timing diagram for TOA monitoring with TOA > 0. It shows two timelines: SRNC (CFN 147-153) and Node B (CFN 147-153). A DL SYNCHRONISATION frame is sent from SRNC at CFN=151 and received by Node B. A UL SYNCHRONISATION frame is sent from Node B at TOA=5.750 ms and received by SRNC at CFN=151. A 'Receiving Window' is shown on the Node B timeline, and the TOA is indicated as the time difference between the DL and UL frames at Node B.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Timing diagram for TOA monitoring with TOA > 0. It shows two timelines: SRNC (CFN 147-153) and Node B (CFN 147-153). A DL SYNCHRONISATION frame is sent from SRNC at CFN=151 and received by Node B. A UL SYNCHRONISATION frame is sent from Node B at TOA=5.750 ms and received by SRNC at CFN=151. A 'Receiving Window' is shown on the Node B timeline, and the TOA is indicated as the time difference between the DL and UL frames at Node B. + +Figure 12: TOA monitoring through Frame Protocol Synchronisation Procedure (TOA > 0) + +![Timing diagram for TOA monitoring with TOA < 0. It shows two timelines: SRNC (CFN 147-153) and Node B (CFN 147-153). A DL SYNCHRONISATION frame is sent from SRNC at CFN=150 and received by Node B. A UL SYNCHRONISATION frame is sent from Node B at TOA=-5.250 ms and received by SRNC at CFN=151. A 'Receiving Window' is shown on the Node B timeline, and the TOA is indicated as the time difference between the DL and UL frames at Node B.](d1c99a42332e5ee19f3b840281c26681_img.jpg) + +Timing diagram for TOA monitoring with TOA < 0. It shows two timelines: SRNC (CFN 147-153) and Node B (CFN 147-153). A DL SYNCHRONISATION frame is sent from SRNC at CFN=150 and received by Node B. A UL SYNCHRONISATION frame is sent from Node B at TOA=-5.250 ms and received by SRNC at CFN=151. A 'Receiving Window' is shown on the Node B timeline, and the TOA is indicated as the time difference between the DL and UL frames at Node B. + +Figure 13: TOA monitoring through Frame Protocol Synchronisation Procedure (TOA < 0) + +In case of macro-diversity with recombining in the DRNC, the DL SYNCHRONISATION control frame is duplicated in the DRNC on the different links, while the UL SYNCHRONISATION control frames received from all the Node B's are forwarded transparently to the SRNC (see Figure 14). + +![Figure 14: [FDD - TOA monitoring through FP Synchronisation Procedure during soft handover with selection/recombining in the DRNC]. The diagram shows four horizontal timelines for SRNC, DRNC, Node B-1, and Node B-2. The SRNC timeline has CFN markers at 254, 255, 0, 1, 2, 3, 4. The DRNC timeline has CFN markers at 0, 1, 2, 3, 4. Node B-1 and Node B-2 timelines both have CFN markers at 254, 255, 0, 1, 2, 3, 4. Arrows indicate synchronization signals: DL SYNCHRONISATION [CFN=1] from SRNC to DRNC, Node B-1, and Node B-2; UL SYNCHRONISATION [TOA-1] from Node B-1 to SRNC; UL SYNCHRONISATION [TOA-2] from Node B-2 to SRNC. Yellow horizontal bars highlight the DL SYNCHRONISATION [CFN=1] signals at Node B-1 and Node B-2.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Figure 14: [FDD - TOA monitoring through FP Synchronisation Procedure during soft handover with selection/recombining in the DRNC]. The diagram shows four horizontal timelines for SRNC, DRNC, Node B-1, and Node B-2. The SRNC timeline has CFN markers at 254, 255, 0, 1, 2, 3, 4. The DRNC timeline has CFN markers at 0, 1, 2, 3, 4. Node B-1 and Node B-2 timelines both have CFN markers at 254, 255, 0, 1, 2, 3, 4. Arrows indicate synchronization signals: DL SYNCHRONISATION [CFN=1] from SRNC to DRNC, Node B-1, and Node B-2; UL SYNCHRONISATION [TOA-1] from Node B-1 to SRNC; UL SYNCHRONISATION [TOA-2] from Node B-2 to SRNC. Yellow horizontal bars highlight the DL SYNCHRONISATION [CFN=1] signals at Node B-1 and Node B-2. + +**Figure 14: [FDD - TOA monitoring through FP Synchronisation Procedure during soft handover with selection/recombining in the DRNC]** + +Once the SRNC receives the two UL SYNCHRONISATION control frames containing TOA1 and TOA2, it may consider either TOA1 or TOA2 to advance or delay DL transmission (see Table 1). + +**Table 1** + +| Relation between TOA1 and TOA2 | TOA considered and action performed by the SRNC | +|--------------------------------|---------------------------------------------------| +| $TOA1 < TOA2 < 0$ | TOA1 may be considered to advance DL transmission | +| $TOA2 < TOA1 < 0$ | TOA2 may be considered to advance DL transmission | +| $TOA1 < 0, TOA2 > 0$ | TOA1 may be considered to advance DL transmission | +| $TOA2 < 0, TOA1 > 0$ | TOA2 may be considered to advance DL transmission | +| $TOA1 > TOA2 > 0$ | TOA2 may be considered to delay DL transmission | +| $TOA2 > TOA1 > 0$ | TOA1 may be considered to delay DL transmission | + +# 8 Radio Interface Synchronisation + +## 8.1 General + +This subclause describes the Radio Interface Synchronisation for FDD and TDD. + +## 8.2 FDD Radio Interface Synchronisation + +### 8.2.1 General + +This section is fully applicable to both the DL DPCH and the F-DPCH. As such, wherever "DL DPCH" appears in this section (in text, figure and equations), it has to be replaced with "F-DPCH" in the context of "F-DPCH". + +FDD Radio Interface Synchronisation assures that UE gets the correct frames when received from several cells. The UE measures the Timing difference between its DPCH and SFN in the target cell when doing handover and reports it to SRNC. SRNC sends this Time difference value in two parameters Frame Offset and Chip Offset over Iub to Node B. Node B rounds this value to the closest 256 chip boundary in order to get DL orthogonality (regardless of used spreading factor). The rounded value is used in Node B for the DL DPCH or the F-DPCH. + +$DOFF_{FDD}$ is selected by the SRNC considering the interleaving period (e.g. 10, 20, 40 or 80 ms) when entering in dedicated state from common channel state. + +Services are scheduled by using DOFFFDD in order to average out the Iub traffic load and the Node B processing load. DOFFFDD (FDD Default DPCH Offset value) is only used when setting up the first RL in order to initialise Frame Offset and Chip Offset and to tell UE when frames are expected. + +UE uses the UL DPCH as it is a more defined time instant compared with DL DPCH. + +The handover reference is the time instant $T_{UETx} - T_o$ , which is called DL DPCHnom in the timing diagram. + +$T_{cell}$ is used to skew cells in the same Node B in order to not get colliding SCH bursts, one SCH burst is 1/10 of a slot time. + +The timing diagram in Figure 15 shows an example with two cells connected to one UE where handover is done from source cell (Cell 1) to target cell (Cell 2). + +![Figure 15: FDD Radio Interface Synchronisation timing diagram. This diagram illustrates the timing relationships between various signals at Node B1, Node B2, and the User Equipment (UE) during a handover from Cell 1 to Cell 2. The signals shown include DL BFN, DL SFN (Cell 1), DL SFN mod 256 frames, DL DPCH (CFN), DL DPCH, UL DPCH (TUETx), DL DPCHnom (TUETx - To), DL DPCH2, DL SFN2, DL SFN2 (Cell 2), DL DPCH2 (CFN), and UL DPCH2. Key timing parameters like Tcell, Tm, To, Tp1, Tp2, and alpha are indicated. The diagram also includes formulas for calculating offsets and examples of chip and frame values.](c3e1070b4f3194b1fb1b9d5300dac25f_img.jpg) + +**Timing Diagram Details:** + +- DL BFN1:** 4094, 4095, 0, 1, 2, 3, 4 +- DL SFN1 (Cell 1):** 4094, 4095, 0, 1, 2, 3, 4. Delayed by $T_{cell}$ relative to BFN. +- DL SFN1 mod 256 frames:** 254, 255, 0, 1, 2, 3, 4. Derived from SFN1. +- DL DPCH1 (CFN):** 252, 253, 254, 255, 0, 1, 2. Derived from SFN1 mod 256 frames using $\text{Rounded}(\text{Frame\_offset} + \text{Chip\_offset})$ . Example: $\text{Frame\_offset} = 2$ , $\text{Chip\_offset} = 10240$ chips. +- DL DPCH1:** 252, 253, 254, 255, 0, 1, 2. Delayed by $T_{p1}$ from CFN. +- UL DPCH ( $T_{UETx}$ ):** 252, 253, 254, 255, 0, 1, 2. UE transmission time. +- DL DPCHnom ( $T_{UETx} - T_o$ ):** 252, 253, 254, 255, 0, 1, 2. Used as reference at UE. Example: $\text{OFF} + T_m = 3.3300$ frames $\rightarrow \text{OFF} = 3$ , $T_m = 12672$ chips. +- DL DPCH2:** 252, 253, 254, 255, 0, 1, 2. Received at UE, delayed by $T_m$ from Node B2. +- DL SFN2:** 4095, 0, 1, 2, 3, 4, 5. Delayed by $T_{p2}$ from Node B2 at UE. +- DL SFN2 (Cell 2):** 4095, 0, 1, 2, 3, 4, 5. +- DL DPCH2 (CFN):** 252, 253, 254, 255, 0, 1, 2. Derived from SFN2 (Cell 2) using $\text{Rounded}(\text{Frame\_offset} + \text{Chip\_offset})$ . Example: $\text{Chip\_offset} = 12672$ gives 128 chips rounding error (12800 - 12672). +- UL DPCH2:** 252, 253, 254, 255, 0, 1, 2. Relative to DL DPCH2 at NB2, delayed by $T_o \pm \alpha \pm 2T_{p2}$ . + +**Legend:** + +| | | | | +|-----------------|-------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha$ | 1 st received DL DPCH finger relative DL DPCH nom | $T_{cell}$ | Specifies the SFN delay relative BFN | +| BFN | Node B Frame Number (counter) | $T_m$ | Measured by UE at HO, $T_m$ has a range from 0 to 38399 chips. | +| CFN | Connection Frame Number (DPCH related) | $T_o$ | Is a constant of 1024 chips, is the nominal difference between first received DPCH finger (DL DPCH nom ) and $T_{UETx}$ at UE. | +| DPCH | Dedicated Physical Channel (CFN related) | $T_{px}$ | Propagation delay (one way), UE to Cell X | +| HO | Handover | $T_{UETx}$ | The time when UE transmits an UL Dedicated Physical Channel. | +| NB x | Node B (x: 1=source, 2=target) | | | +| OFF | Offset with a range from 0 to 255 frames | | | +| RFN | RNC Frame Number (counter) | | | +| RNC | Radio Network Controller | | | +| SFN | System Frame Number (counter) | | | + +Figure 15: FDD Radio Interface Synchronisation timing diagram. This diagram illustrates the timing relationships between various signals at Node B1, Node B2, and the User Equipment (UE) during a handover from Cell 1 to Cell 2. The signals shown include DL BFN, DL SFN (Cell 1), DL SFN mod 256 frames, DL DPCH (CFN), DL DPCH, UL DPCH (TUETx), DL DPCHnom (TUETx - To), DL DPCH2, DL SFN2, DL SFN2 (Cell 2), DL DPCH2 (CFN), and UL DPCH2. Key timing parameters like Tcell, Tm, To, Tp1, Tp2, and alpha are indicated. The diagram also includes formulas for calculating offsets and examples of chip and frame values. + +Figure 15: FDD Radio Interface Synchronisation timing diagram + +SFN1 is found in Cell 1 at Node B1 and SFN2 at Cell 2 and Node B2. SFN1 is sent $T_{cell1}$ after the Node B1 reference BFN1. CFN is the frame numbering that is related to each DL and UL Dedicated Physical Channel (DPCH). UL DPCH + +is sent from UE to both Cells (both Node B's in this example). UL DPCH2 at Node B2 is shown to indicate the difference to the DL DPCH2 at Node B2. + +The new RL (DL DPCH2) which is setup at the HO will face some deviation from nominal position due to the rounding of Frame Offset and Chip Offset to 256 chip boundary in Node B. Time dispersion and UE movements are examples of other factors affecting this phase deviation. + +The nominal DL DPCH timing at UE is $T_0$ before the $T_{UETX}$ time instant, which could be expressed: + +$$DL\ DPCH_{nom} = T_{UETX} - T_0 \quad (8.1)$$ + +In UE dedicated state, OFF and $T_m$ are measured at UE according to the following equation: + +$$OFF + T_m = (SFN_{target} - DL\ DPCH_{nom}) \bmod 256 \text{ frames [chips]} \quad (8.2)$$ + +NOTE: OFF has the unit Frames and $T_m$ the unit Chips. + +EXAMPLE 1: Assume that $OFF + T_m$ equals "3.3300" frames (as given as an example in Figure 15). Then $OFF = 3$ and $T_m = "0.33"$ which corresponds to $T_m = 12672$ chips. + +In other words (referring to the timing diagram in Figure 15): + +- How to determine $T_m$ at UE: Select a time instant 1) where frame N starts at DL $SFN_2$ e.g. frame number 3, the time from that time instant to the next frame border of DL $DPCH_{nom}$ 2) equals $T_m$ (if these are in phase with each other, $T_m$ is zero). +- How to determine OFF: The difference between the frame number selected for time instant 1) and the frame number starting at instant 2) $\bmod 256$ frames equals OFF. +EXAMPLE 2: $(3 - 0) \bmod 256 = 3$ , another example is $(1 - 254) \bmod 256 = 3$ . + +### 8.2.2 Neighbour cell list timing information + +A cell can optionally broadcast a neighbouring cell list that indicates timing information for neighbouring cells. The list contains the inter cell timing difference to neighbour cells with associated estimated uncertainty. The inter cell timing uncertainty depends on what timing difference estimating means that are used in the system (No means at all, Node synchronisation measurements, UE inter-cell measurements, Cells belonging to the same Node B or even GPS). The purpose with the neighbouring cell list timing information is to enable shorter cell search time for UE, to save UE battery and to potentially lower BCH Tx power for cells in a synchronised cluster. + +## 8.3 TDD Radio Interface Synchronisation + +### 8.3.1 General + +The TDD Radio Interface Synchronisation relates to the following two aspects: + +- Intercell Synchronisation; +- Timing Advance for 3.84Mcps and 7.68 Mcps TDD, and Uplink Synchronisation for 1.28Mcps TDD. + +In TDD mode Intercell Synchronisation may be achieved by means of: + +- Inter Node B Node Synchronisation that allows to achieve a common timing reference among Node B's. + +The Radio Interface Synchronisation between UE and UTRAN is achieved by means of the Timing Advance mechanism. + +### 8.3.2 Intercell Synchronisation + +Intercell Synchronisation ensures that the frame boundaries are positioned at the same time instant in adjacent cells (see Figure 16). + +This requirement is necessary to minimise the interference between UEs in neighbouring cell. + +In addition it automatically ensures that the slots of different cells are synchronised, i.e. they do not overlap at the UE. + +![Figure 16: Intercell Synchronisation diagram showing two nodes, Node B-1 and Node B-2, across two frames, FRAME K and FRAME N. Node B-1 has slots 1, 2, 3, 9, 10, 11. Node B-2 has slots 1, 2, 3, 9, 10, 11. Arrows indicate active slots: Node B-1 has down arrows in slots 2 and 10, and an up arrow in slot 11. Node B-2 has down arrows in slots 1 and 3, and up arrows in slots 9 and 11. A vertical double-headed arrow on the left indicates 'ACTIVE SLOTS'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +Figure 16: Intercell Synchronisation diagram showing two nodes, Node B-1 and Node B-2, across two frames, FRAME K and FRAME N. Node B-1 has slots 1, 2, 3, 9, 10, 11. Node B-2 has slots 1, 2, 3, 9, 10, 11. Arrows indicate active slots: Node B-1 has down arrows in slots 2 and 10, and an up arrow in slot 11. Node B-2 has down arrows in slots 1 and 3, and up arrows in slots 9 and 11. A vertical double-headed arrow on the left indicates 'ACTIVE SLOTS'. + +**Figure 16: Intercell Synchronisation** + +Furthermore, Intercell Synchronisation assures the synchronisation of the last 8 bits of the SFN, that is required if frame wise hopping mechanisms among cells are used. It also can be used to keep more efficient and faster all procedures involving a switch from one cell to another, such as searching for new cells, locking to new cells or handover. + +### 8.3.3 Multi Frame Synchronisation + +Void. + +### 8.3.4 Timing Advance for 3.84Mcps and 7.68Mcps TDD + +Timing Advance is used in uplink to align the uplink radio signals from the UE to the UTRAN both in case of uplink Dedicated Physical Channels (DPCH), E-PUCH, E-RUCCH and of Physical Uplink Shared Channels (PUSCH). + +The handling of timing advance can be divided in four main categories: measurement, initial assignment, updates during operation, and setting on handover. For each category, a number of different cases can be distinguished. + +1. Measurement of the timing deviation on the physical channels: + - On PRACH transmissions; + - On DPCH transmissions; + - On PUSCH transmissions; + - On E-PUCH transmissions; + - On E-RUCCH transmissions +2. Assignment of correct timing advance value when establishing new channels: + - At transition to CELL\_DCH state; + - When establishing an USCH in CELL\_FACH state. +3. Update of timing advance value for channels in operation: + - UE in CELL\_DCH state; + - UE with USCH in CELL\_FACH state. +4. Setting of timing advance value for target cell at handover: + - Handover from TDD to TDD with synchronised cells; + - Handover from TDD to TDD with unsynchronised cells; + - Handover from FDD to TDD; + - Handover from other systems to TDD. + +#### 8.3.4.1 Measurement of the timing deviation on the physical channels + +Timing deviation measurements are always performed in the physical layer in Node B. These measurements have to be reported to the higher layers, where timing advance values are calculated and signalled to the UE. For this reporting, a number of different ways are foreseen, depending on the used physical channels. + +**PRACH:** The Node B physical layer measures the timing deviation of the received PRACH signal (RX Timing Deviation) and passes this together with the transport block to the CRNC (by means of the Iub RACH Frame Protocol). In case the RACH carries a DDCH or DTCH, the measured timing deviation may be passed from DRNC to the SRNC over Iur interface (by means of the Iur RACH Frame Protocol). + +**NOTE:** PRACH transmissions themselves are transmitted with a large guard period so they do not require timing advance. + +**PUSCH:** The Node B physical layer measures the timing deviation of the received PUSCH signal (RX Timing Deviation) and passes this together with the transport block to the CRNC (by means of the Iub USCH Frame Protocol). + +**DPCH:** The Node B physical layer measures the timing deviation of the received DPCH signal (RX Timing Deviation) and passes this value, if the conditions for reporting the measurement are met, to the SRNC (by means of the Iub & Iur DCH Frame Protocols – Rx Timing Deviation Frame Protocol). + +**E-PUCH:** The Node B physical layer measures the timing deviation of the received E-PUCH signal (RX Timing Deviation) and passes this value, if conditions for reporting the measurement are met, to the SRNC (by means of the Iub & Iur DCH Frame Protocols – Rx Timing Deviation Frame Protocol). + +**E-RUCH:** The Node B physical layer measures the timing deviation of the received E-RUCH signal (RX Timing Deviation) and passes this value, if conditions for reporting the measurement are met, to the SRNC (by means of the Iub & Iur DCH Frame Protocols – Rx Timing Deviation Frame Protocol). When the E-RUCH represents a Timing Advance Request message TS 25.321 [26] the Node B calculates the timing advance and responds with a Timing Advance Response message TS 25.321 [26]. + +#### 8.3.4.2 Assignment of correct timing advance value when establishing new channels + +##### 8.3.4.2.1 Transition to CELL\_DCH State + +The transition to CELL\_DCH state from CELL\_FACH state or Idle Mode operates in the following manner: + +- The SRNC checks whether an up to date timing deviation measurement is available. Such a measurement can be available from a recent RACH access (e.g. from initial access) or from a recent USCH transmission. If no up to date timing deviation measurement is available, e.g. because of lack of uplink transmissions, or during USCH over Iur, the SRNC is not informed about RX Timing Deviations, and has to trigger an uplink transmission from the UE before it can assign a DCH (for example, a RRC procedure requiring a response from the UE). The SRNC calculates the required timing advance value and saves it in the UE context in the SRNC for later use in dedicated or shared channel activation. +- The SRNC attaches the timing advance value to the channel allocation message that it signals to the UE via FACH (RRC message CONNECTION SETUP or RRC message RADIO BEARER SETUP). +- When the UE receives the channel allocation message it configures its physical layer with the given absolute timing advance value. When a timing advance command is signalled to the UE, the CFN that the new timing advance is to be applied is always signalled. + +##### 8.3.4.2.2 When establishing an USCH in CELL\_FACH state + +For uplink traffic using the USCH, short time allocations are sent to the UE regularly. Therefore establishing an USCH in CELL\_FACH state is very similar to handling of timing advance updates during USCH operation. The UTRAN shall use a recent timing deviation measurement. Such a measurement shall be available from a recent USCH burst or a recent RACH access (e.g. from the RRC message PUSCH CAPACITY REQUEST). + +##### 8.3.4.2.3 When establishing E-DCH in CELL\_DCH state (E-DCH/HS-DSCH operation with no UL DPCH) + +The UTRAN shall use timing deviation. Such measurements shall be available in relation to recent transmissions on E-RUCCH and/or E-PUCH. + +#### 8.3.4.3 Update of timing advance value for channels in operation + +##### 8.3.4.3.1 UE in CELL\_DCH state + +An UE that is operating a dedicated channel (CELL\_DCH state) has to update the timing advance from time to time to keep the received signal at the Node B within the required time window. Under reasonable assumptions the worst case update frequency is in the order of 8 seconds. + +The timing advance update procedure operates in the following manner: + +1. The SRNC determines whether a new timing advance value has to be transmitted to the UE taking into account the timing deviation measurements. The new timing advance value is calculated taking into account the UE's current timing advance value. +2. The new timing advance value and the CFN in which it is to take effect are signalled to the UE via RRC signalling on FACH or DCH (PHYSICAL CHANNEL RECONFIGURATION, TRANSPORT CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION or UPLINK PHYSICAL CHANNEL CONTROL are examples of possible messages on the DCCH). +3. The SRNC shall also send the updated timing advance value and the CFN in which it is to take effect to the Node B, using a user plane control message. The Node B may adjust its physical layer to take the change in uplink transmission into account. +4. When the UE receives a new timing advance value, it shall configure its physical layer so that the updated timing advance value takes effect on the given CFN specified within the RRC message. The timing advance value shall be applied to all DPCHs and, if present, to all PUSCHs. + +There is no need for the UE to acknowledge the timing advance update: the Node B continually measures and reports the UE timing deviation and the UE reports the received timing advance value as part of its measurement reporting. The SRNC is thus able to detect if a timing advance update has not been received and needs to be resent. + +##### 8.3.4.3.2 UE with USCH Traffic in CELL\_FACH state + +If the UE uses an USCH in CELL\_FACH state (no DCH), the timing advance update procedure operates in the following manner: + +1. The CRNC determines whether a new timing advance value has to be transmitted to the UE taking into account when the last timing advance update was signalled. Two cases are possible: + - If the data transfer is uplink after a longer idle period then the UE has to transmit a capacity request on the RACH. The CRNC is therefore informed of any timing deviation on this RACH. + - If a new allocation follows an USCH transmission, the timing deviation is already known to the CRNC from measurements of the last uplink transmission. +2. If a Timing Advance update is needed, the CRNC includes a new timing advance value and the CFN in which it will take effect in the next USCH allocation message to the UE (PHYSICAL SHARED CHANNEL ALLOCATION). +3. The CRNC shall also send a user plane control message indicating the CFN and the updated timing advance value to the Node B so the Node B can adjust its physical layer averaging to take the change in uplink transmission into account. +4. When the UE receives a new timing advance value, the UE shall configure its physical layer, so that the updated timing advance value takes effect on the given CFN specified within the PHYSICAL SHARED CHANNEL ALLOCATION message. The timing advance value shall be applied to all present PUSCHs. + +#### 8.3.4.4 Setting of timing advance value for target cell at handover + +##### 8.3.4.4.1 General + +Since the uplink radio signals need to be adjusted only because of large enough distances between the UE and the cell transmission, certain cells will have a small enough radius that timing advance needs to not be used. In those cells the timing advance value in the UE is set to zero and UE autonomous adjustment of timing advance upon handover is disabled in the handover messages to the UE. + +In these cells, where TA is not applied, the “RX Timing Deviation” measurement can be omitted if no other procedure (e.g. LCS) requires it. + +##### 8.3.4.4.2 Handover from TDD to TDD with synchronised cells + +When two TDD cells are involved in handover and the two cells are sufficiently synchronised, a UE is able to measure the time offset between P-CCPCH reception of the two cells and, consequently, is able to autonomously correct its timing on handover without UTRAN assistance. However to improve the accuracy for the UE calculated timing advance, the SRNC can include an updated timing advance based on the timing deviation measured by the old cell in the messages triggering the handover in the UE. Note that this update shall apply in the old cell at the specified CFN if handover is performed on a later CFN or if the handover fails and falls back to the old cell. The UE shall use this new value as the basis for the UE autonomous update. + +After a successful handover, a response message is transmitted in the new cell. In this message, if the UE autonomously updated its timing advance it shall report the calculated timing advance value, which it is using for access to the new cell. By this way, the SRNC is informed as fast as possible about the absolute timing advance value in the UE, and it can correct the timing advance immediately or in the future based on this value, if necessary. + +##### 8.3.4.4.3 Handover from FDD to TDD, Handover from other systems to TDD, or Handover from TDD to TDD with unsynchronised cells + +In these cases, synchronisation between the handover cells is not possible. In the case where DPCH(s) are assigned, the new TDD cell must use a burst type with a large enough transmission window to allow the immediate transmission of data without the need of timing advance adjustment in the new cell, since timing adjustment can only be performed in these cells after the first uplink transmission. In the case where E-DCH/HS-DSCH operation is configured without a DPCH then the UE obtains timing advance in the new cell (using TA Request, see TS 25.321 [26]) before transmitting data. + +### 8.3.5 UL Synchronisation for 1.28Mcps TDD + +This section describes the details of the UL synchronisation including the establishment of UL synchronisation and maintenance of the UL synchronisation. + +#### 8.3.5.1 The establishment of uplink synchronisation + +##### 8.3.5.1.1 Preparation of uplink synchronisation by downlink synchronisation + +When a UE is powered on, it first needs to establish the downlink synchronisation with the cell. Only after the UE can establish and maintain the downlink synchronisation, it can start the uplink synchronisation procedure. + +##### 8.3.5.1.2 Establishment of uplink synchronisation + +Although the UE can receive the downlink synchronisation signal from the Node B, the distance to Node B is still uncertain which would lead to unsynchronised uplink transmission. Therefore, the first transmission in uplink direction is performed in Uplink Pilot Channel (UpPCH), to avoid interference in traffic time-slots. + +The timing used for the SYNC\_UL code are set e.g. according to the received power level of DwPCH and/or P-CCPCH. + +At the detection of the SYNC\_UL sequence in the searching window, the Node B will evaluate the received power levels and timing, and reply by sending the adjustment information to UE to modify its timing and power level for next transmission and for establishment of the uplink synchronisation procedure. Within the next 4 sub-frames, the Node B will send the adjustment information to the UE (in a single subframe message in the FPACH). The uplink synchronisation procedure, normally used for a random access to the system, can also be used for the re-establishment of the uplink synchronisation when uplink is out of synchronisation. + +#### 8.3.5.2. Maintenance of uplink synchronisation + +For the maintenance of the uplink synchronisation, the midamble field of each uplink burst can be used. + +In each uplink time slot the midamble in each UE is different. The Node B can estimate the power level and timing shift by measuring the midamble field of each UE in the same time slot. Then, in the next available downlink time slot, the Node B will signal the Synchronisation Shift (SS) and the Power Control (PC) commands to enable the UE to properly adjust respectively its Tx timing and Tx power level. + +These procedures guarantee the reliability of the uplink synchronisation. The uplink synchronisation can be checked once per 1.28Mcps TDD subframe. The step size in uplink synchronisation is configurable and re-configurable and can be adapted from 1/8 chip to 1 chip duration. The following updates for UL synchronisation are possible: 1 step up; 1 step down; no update. + +For 3.84Mcps and 7.68Mcps TDD option, uplink synchronisation is mentioned in 4.3 of TS 25.224 [16]. But the implementation method is a little different with the 1.28Mcps TDD option. For 1.28Mcps TDD option, the establishment of the UL synchronisation is done by using the UpPCH and the FPACH. + +UE will select one of the set of SYNC\_UL codes which can be used in the cell to establish uplink synchronisation in the access procedure. The benefit of this method is when the UE wants to do random access, the PRACH will have minimum interference to other traffic channel. Vice versa, it will also reduce the interference from traffic channels to PRACH. + +# --- 9 Usage of Synchronisation Counters and Parameters to support Transport Channel and Radio Interface Synchronisation + +## 9.1 General + +This subclause describes how the different synchronisation parameters and counters are computed and used in order to obtain Transport Channel (L2) and Radio Interface (L1) Synchronisation. + +The parameters that need to be determined by the UE are CFN, OFF [FDD – and Tm]. + +The parameter that need to be determined by the UTRAN are [FDD – DOFFFDD], [TDD – DOFFTDD], Frame Offset and [FDD – Chip Offset]. + +Figure 17 summarises how these parameters are computed. A detailed description of the actions in each state is given in the sections 9.2 – 9.4, while some examples of corrections applied to synchronisation counters during UE state transitions are shown in section 9.5. + +![Figure 17: Calculations performed by UE and UTRAN. A flowchart showing four states: Cell_FACH State, Cell_DCH State (1 RL), [FDD] Cell_DCH State (several RL's), and Cell_DCH State (additional RL or UE moves to another cell). Each state contains calculations for UE and UTRAN regarding CFN, SFN, DOFF, and Frame Offset. Arrows indicate transitions between states, with 'FDD only' labels on some transitions.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +**Cell\_FACH State** + +| | | | | | +|----|-----------------------|------------------------|-------|----------------------------------------------| +| UE | $CFN = SFN \bmod 256$ | Cell_FACH State | UTRAN | $CFN = SFN \bmod 256$
$Frame\_offset = 0$ | +|----|-----------------------|------------------------|-------|----------------------------------------------| + +**Cell\_DCH State (1 RL)** + +| | | | | | +|----|----------------------------------------------------------------------------------------------------------------|--|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE | [FDD] $CFN = ((SFN - (DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$
[TDD] $CFN = (SFN - DOFF_{TDD}) \bmod 256$ | | UTRAN | [FDD] $DOFF_{FDD}$ generated by SRNC
$Frame\ Offset * 38400 + Chip\ Offset = DOFF_{FDD} * 512 \Rightarrow Frame\ Offset, Chip\ Offset$
[TDD] $DOFF_{TDD}$ generated by SRNC; $Frame\ Offset = DOFF_{TDD}$ | +|----|----------------------------------------------------------------------------------------------------------------|--|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**[FDD] Cell\_DCH State (several RL's)** + +| | | | | | +|----|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE | $CFN = (SFN_j - (DOFF_{FDD} * 512) \bmod 38400) \bmod 256$
$OFF_k + Tm_k = (SFN_k - CFN) \bmod 256 \Rightarrow OFF_k, Tm_k$ | j: reference cell
k: all other cells | UTRAN | $DOFF_{FDD}$ generated by SRNC
$Frame\ Offset_k * 38400 + Chip\ Offset_k = DOFF_{FDD} * 512 + OFF_k * 38400 + Tm_k \Rightarrow Frame\ Offset_k, Chip\ Offset_k$ | +|----|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Cell\_DCH State (additional RL or UE moves to another cell)** + +| | | | | | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE | if SFN target is available [FDD] $OFF_{target} + Tm_{target} = (SFN_{target} - CFN) \bmod 256 \Rightarrow OFF_{target}, Tm_{target}$
[TDD] $OFF_{target} = (SFN_{target} - CFN) \bmod 256$
if OFF target known by the UTRAN CFN is unchanged, otherwise $CFN = (SFN - OFF_{target}) \bmod 256$ | | UTRAN | [FDD] $Frame\ Offset_{target} * 38400 + Chip\ Offset_{target} = OFF_{target} * 38400 + Tm_{target} \Rightarrow Frame\ \&\ Chip\ Off.$
[TDD] $Frame\ Offset_{target} = OFF_{target}$ if UE can measure $SFN_{target}$ otherwise $Frame\ Offset_{target} = DOFF_{FDD}$ | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +(\*) only in FDD +(\*\*) only in TDD + +Figure 17: Calculations performed by UE and UTRAN. A flowchart showing four states: Cell\_FACH State, Cell\_DCH State (1 RL), [FDD] Cell\_DCH State (several RL's), and Cell\_DCH State (additional RL or UE moves to another cell). Each state contains calculations for UE and UTRAN regarding CFN, SFN, DOFF, and Frame Offset. Arrows indicate transitions between states, with 'FDD only' labels on some transitions. + +**Figure 17: Calculations performed by UE and UTRAN** + +Figure 18 describes what offset parameters are signalled and used in the different nodes at Initial RL setup and at Handover (HO) in FDD. The rounding to closest 256 chip boundary is done in Node B. The rounded Frame Offset and Chip Offset control the DL DPCH air-interface timing or the F-DPCH air-interface timing. The 256 chip boundary is to maintain DL orthogonality in the cell (the rounding to the closest 256 chip boundary is done in Node B to facilitate the initial UL chip synchronisation process in Node B). As this figure is also applicable to F-DPCH, "DL DPCH" has to be replaced by "F-DPCH" everywhere in the figure in the context of F-DPCH. + +![Figure 18: Sequence diagram for FDD showing offset usage at initial RL and HO. The diagram involves UE, Node B (Source cell), Node B (Target cell), and SRNC. At initial RL, DOFF_FDD (RRC) and Frame Offset + Chip Offset (NBAP) are used to establish DL DPCH (Uu) timing. At HO, OFF_target + Tm_target (RRC) and Frame Offset_target + Chip Offset_target (NBAP) are used. A note indicates Node B rounds the offset to the closest 256 chip boundary.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +The diagram illustrates the timing relationships for FDD. At the top, four entities are shown: UE, Node B (Source cell), Node B (Target cell), and SRNC. The timeline is divided into two sections: "At initial RL" and "At HO". + +- At initial RL:** + - The UE sends a message to the SRNC labeled $DOFF_{FDD}$ (RRC). + - The SRNC responds with $Frame\ Offset + Chip\ Offset$ (NBAP) to the Target cell. + - The Target cell sends a message to the Source cell. + - The Source cell sends a message to the UE labeled $DL\ DPCH$ (Uu). + - Below this, $DL\ DPCH_{nom} = T_{UETx} - T_o$ (UE) is indicated. + - Further down, $DL\ SFN$ and $timing\ reference$ (Uu) are shown as dashed lines. +- At HO:** + - The UE sends $OFF_{target} + Tm_{target}$ (RRC) to the SRNC. + - The SRNC sends $Frame\ Offset_{target} + Chip\ Offset_{target}$ (NBAP) to the Target cell. + - A note with a dashed circle around the Target cell's timing indicates: "Node B rounds $Frame\ Offset + Chip\ Offset$ to closest 256 chip boundary, which controls the $DL\ DPCH$ air-interface timing". + - The Target cell sends a message to the UE labeled $DL\ DPCH$ (Uu). + +At the bottom, a legend shows two types of arrows: a dashed arrow for "Air-interface channel timing (Uu and Uu related in UE)" and a solid arrow for "Signals over a certain protocol (NBAP or RRC in this case)". + +Figure 18: Sequence diagram for FDD showing offset usage at initial RL and HO. The diagram involves UE, Node B (Source cell), Node B (Target cell), and SRNC. At initial RL, DOFF\_FDD (RRC) and Frame Offset + Chip Offset (NBAP) are used to establish DL DPCH (Uu) timing. At HO, OFF\_target + Tm\_target (RRC) and Frame Offset\_target + Chip Offset\_target (NBAP) are used. A note indicates Node B rounds the offset to the closest 256 chip boundary. + +Figure 18: [FDD - Usage of Offset values at initial RL and at HO] + +Figure 19 describes what offset parameters are signalled and used in the different nodes at Initial RL setup and at Handover (HO) in TDD. + +Note that in some cases the parameter $OFF_{target}$ cannot be measured by the UE before handover (e.g. in case of inter frequency handover or inter-mode handover). In these cases a value as defined in [FDD - 13] [TDD - 14] shall be reported by the UE. + +![Figure 19: Sequence diagram for TDD showing offset usage at initial RL and HO. The diagram involves UE, Node B (Source cell), Node B (Target cell), and SRNC. At initial RL, DOFF_TDD (RRC) and Frame Offset (NBAP) are used. At HO, OFF_target (RRC) and Frame Offset_target (NBAP) are used. A note indicates Node B controls the DL DPCH air-interface timing.](26e334e61dd059cff029338a2a604d8d_img.jpg) + +The diagram illustrates the timing relationships for TDD. At the top, four entities are shown: UE, Node B (Source cell), Node B (Target cell), and SRNC. The timeline is divided into two sections: "At initial RL" and "At HO". + +- At initial RL:** + - The UE sends a message to the SRNC labeled $DOFF_{TDD}$ (RRC). + - The SRNC responds with $Frame\ Offset$ (NBAP) to the Target cell. + - The Target cell sends a message to the Source cell. + - The Source cell sends a message to the UE labeled $DL\ DPCH$ (Uu). + - Below this, $DL\ SFN$ and $timing\ reference$ (Uu) are shown as dashed lines. +- At HO:** + - The UE sends $OFF_{target}$ (RRC) to the SRNC. + - The SRNC sends $Frame\ Offset_{target}$ (NBAP) to the Target cell. + - A note with a dashed circle around the Target cell's timing indicates: "Node B controls the $DL\ DPCH$ air-interface timing". + - The Target cell sends a message to the UE labeled $DL\ DPCH$ (Uu). + +At the bottom, a legend shows two types of arrows: a dashed arrow for "Air-interface channel timing (Uu and Uu related in UE)" and a solid arrow for "Signals over a certain protocol (NBAP or RRC in this case)". + +Figure 19: Sequence diagram for TDD showing offset usage at initial RL and HO. The diagram involves UE, Node B (Source cell), Node B (Target cell), and SRNC. At initial RL, DOFF\_TDD (RRC) and Frame Offset (NBAP) are used. At HO, OFF\_target (RRC) and Frame Offset\_target (NBAP) are used. A note indicates Node B controls the DL DPCH air-interface timing. + +Figure 19: [TDD- Usage of Offset values at initial RL and at HO] + +## 9.2 Calculations performed in the UTRAN + +### 9.2.1 UE in CELL\_FACH/PCH state + +In CELL\_FACH/PCH state the Frame Offset is set to 0 (for all common and shared channels). + +### 9.2.2 UE changes from CELL\_FACH/PCH state to CELL\_DCH state: 1 RL + +[FDD - Based on the received parameters from the UE and the $\text{DOFF}_{\text{FDD}}$ value generated in the SRNC, the SRNC calculates the Frame Offset and the Chip Offset from formula (9.1) or formula (9.1.a): + +$$\text{Frame Offset} * 38400 + \text{Chip Offset} = \text{DOFF}_{\text{FDD}} * 512 \quad (9.1)$$ + +$$\text{Frame Offset} * 38400 + \text{Chip Offset} = \text{DOFF}_{\text{FDD}} * 512 + 256 \quad (9.1.a)$$ + +Frame Offset and Chip Offset are then signalled to the Node B controlling the serving cell.] + +[TDD - Based on the $\text{DOFF}_{\text{TDD}}$ value generated in the SRNC, the SRNC calculates the Frame Offset = $\text{DOFF}_{\text{TDD}}$ . + +Frame Offset is then signalled to the Node B controlling the serving cell.] + +[TDD - Note that for all common and shared channels Frame Offset is set to 0 even during CELL\_DCH state.] + +### 9.2.3 [FDD - UE changes from CELL\_FACH/PCH state to CELL\_DCH state: several RL's] + +Based on the received parameters from the UE for each $\text{cell}_k$ ( $\text{OFF}_k$ and $\text{Tm}_k$ ) and the $\text{DOFF}_{\text{FDD}}$ value generated in the SRNC, the SRNC calculates the $\text{Frame Offset}_k$ and the $\text{Chip Offset}_k$ . The $\text{Frame Offset}_k$ and the $\text{Chip Offset}_k$ are calculated from formula (9.2) or formula (9.2.a): + +$$\text{Frame Offset}_k * 38400 + \text{Chip Offset}_k = \text{DOFF}_{\text{FDD}} * 512 + \text{OFF}_k * 38400 + \text{Tm}_k \quad (9.2)$$ + +$$\text{Frame Offset}_k * 38400 + \text{Chip Offset}_k = \text{DOFF}_{\text{FDD}} * 512 + \text{OFF}_k * 38400 + \text{Tm}_k + 256 \quad (9.2.a)$$ + +NOTE: Formula (9.2) is covering formula (9.1) since in the case described in section 9.2.2, $\text{OFF}_k$ and $\text{Tm}_k$ are both equal to zero. + +Each $\text{Frame Offset}_k$ and $\text{Chip Offset}_k$ are then signalled to the Node B controlling the $\text{cell}_k$ . + +### 9.2.4 UE in CELL\_DCH state: addition of a new RL or handover to a new cell + +[FDD - Based on the received parameters from the UE or already known by the UTRAN ( $\text{OFF}_{\text{target}}$ , $\text{Tm}_{\text{target}}$ ), the SRNC calculates the $\text{Frame Offset}_{\text{target}}$ and the $\text{Chip Offset}_{\text{target}}$ with formula (9.3): + +$$\text{Frame Offset}_{\text{target}} * 38400 + \text{Chip Offset}_{\text{target}} = \text{OFF}_{\text{target}} * 38400 + \text{Tm}_{\text{target}} \quad (9.3)$$ + +During hard handover in case the parameter $\text{OFF}_{\text{target}}$ cannot be measured by the UE and it is not already known by the UTRAN, than the SRNC calculates the $\text{Frame Offset}_{\text{target}}$ and the $\text{Chip Offset}_{\text{target}}$ with formula (9.1). + +$\text{Frame Offset}_{\text{target}}$ and $\text{Chip Offset}_{\text{target}}$ are then signalled to the Node B controlling the target cell.] + +[TDD - Based on the parameter $\text{OFF}_{\text{target}}$ received from the UE or already known by the UTRAN, the SRNC calculates the $\text{Frame Offset}_{\text{target}} = \text{OFF}_{\text{target}}$ . + +In case the parameter $\text{OFF}_{\text{target}}$ cannot be measured by the UE and it is not already known by the UTRAN, than the SRNC calculates the $\text{Frame Offset}_{\text{target}} = \text{DOFF}_{\text{TDD}}$ . + +It is signalled to the Node B controlling the target cell.] + +### 9.2.5 Handover from other RAN to UMTS + +[FDD - Based on the definitions for OFF and Tm formula (9.1) can also be used when the UE enters the UTRAN from another CN and establishes one dedicated RL. The same is true for formula (9.2) when establishing one or more dedicated RL's.] + +[TDD - When the UE enters the UTRAN from another CN and establishes one dedicated RL, OFF is 0.] + +## 9.3 Calculations performed in the UE + +### 9.3.A UE in CELL\_FACH/PCH state + +In CELL\_FACH/PCH state the CFN is initialised with the values CFN = SFN for PCH and CFN = SFN mod 256 for all other common and shared channels. The CFN for all common and shared channels in the CRNC is increased (mod 256) by 1 every frame, except PCH, which CFN has the same range of the SFN. + +### 9.3.1 UE changes from CELL\_FACH/PCH state to CELL\_DCH state: 1 RL + +[FDD - Based on the received DOFFFDD and the SFN of the cell in which the UE is source, the UE can initialise the CFN with the value given by formula (9.4): + +$$\text{CFN} = (\text{SFN} - ((\text{DOFF}_{\text{FDD}} * 512) \text{ div } 38400)) \text{ mod } 256 \quad (9.4)$$ + +This formula gives the CFN of the downlink DPCH frame or of the F-DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN.] + +[TDD - Based on the received DOFFTDD, the UE can initialise the CFN with the value given by formula (9.5): + +$$\text{CFN} = (\text{SFN} - \text{DOFF}_{\text{TDD}}) \text{ mod } 256 \quad (9.5)]$$ + +After the initialisation, the CFN in the UE is increased (mod 256) by 1 every frame. + +[TDD - Note that for all common and shared channels CFN = SFN mod 256 even during CELL\_DCH state.] + +#### 9.3.1A[FDD - UE changes from CELL\_FACH/PCH to CELL\_DCH state: several RL's] + +The UE reports to the SRNC the parameters OFFk and Tmk for each cellk measured respect to the reference cellj determined by means of formula (9.6): + +$$\text{OFF}_k + \text{Tm}_k = (\text{SFN}_k - \text{CFN}) \text{ mod } 256 \quad (9.6)$$ + +After having performed OFFk and Tmk measurements for all target cells, the UE initialises the CFN with the value given by formula (9.7), based on the received DOFFFDD and the SFNj of the reference cell: + +$$\text{CFN} = (\text{SFN}_j - ((\text{DOFF}_{\text{FDD}} * 512) \text{ div } 38400)) \text{ mod } 256 \quad (9.7)$$ + +This formula gives the CFN of the downlink DPCH frame or of the F-DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. + +After the initialisation, the CFN in the UE is increased (mod 256) by 1 every frame. + +### 9.3.2 UE in CELL\_DCH state: addition of a new RL or handover to a new cell + +The UE in CELL\_DCH state may be requested by the UTRAN to report OFFtarget by means of System Info broadcast in the source cell. + +[FDD - In case the SFNtarget can be measured, the target cell OFFtarget is calculated using formula (9.8): + +$$\text{OFF}_{\text{target}} + \text{Tm}_{\text{target}} = (\text{SFN}_{\text{target}} - \text{CFN}) \text{ mod } 256 \quad (9.8)$$ + +otherwise a value as defined in TS 25.215 [13] is reported. Tmtarget is always reported, except for the case of FDD-TDD handover.] + +[TDD - In case the $SFN_{target}$ can be measured, the target cell $OFF_{target}$ is calculated using formula (9.9): + +$$OFF_{target} = (SFN_{target} - CFN) \bmod 256 \quad (9.9)$$ + +otherwise a value as defined in TS 25.225 [14] is reported.] + +Note that, regarding the CFN, two cases may occur: + +- a) the value of $OFF_{target}$ is known by the UTRAN before handover execution: + - a1) either because the $SFN_{target}$ has been measured by the UE and reported to the UTRAN by means of the $OFF_{target}$ before handover; + - a2) or because the UTRAN already knows the difference between serving cell $SFN_{source}$ and target cell $SFN_{target}$ and derives $OFF_{target}$ from $OFF_{source}$ by applying the difference between $SFN_{target}$ and $SFN_{source}$ (this difference between SFNs may be known in the UTRAN from previous UE's measurement reports); + - a3) [TDD - or because cells involved in the handover are synchronised – and hence $OFF_{target}$ equals $OFF_{source}$ ]. +- b) the value of $OFF_{target}$ is not known by the UTRAN before handover execution because the $SFN_{target}$ cannot be measured by the UE before handover and the UTRAN does not know the difference between serving cell SFN and target cell SFN. + +In case a) the UTRAN shall not signal to the UE any value of [FDD- $DOFF_{FDD}$ ] [TDD- $DOFF_{TDD}$ ] before handover in the RRC message PHYSICAL CHANNEL RECONFIGURATION, and the UE shall maintain the old CFN, i.e. no correction to CFN is needed during handover. + +In case b) the UTRAN shall signal to the UE the new value of [FDD- $DOFF_{FDD}$ ] [TDD- $DOFF_{TDD}$ ] before handover by means of the RRC message PHYSICAL CHANNEL RECONFIGURATION. The CFN shall be re-initialised after handover (as soon as the UE reads the $SFN_{target}$ according to formula [FDD- (9.4)] [TDD- (9.5)]). + +Note that in cases a2) and a3) the UTRAN may not request the UE to report $OFF_{target}$ , while in case b) the value of $OFF_{target}$ reported by the UE is the one defined in [FDD - 13], [TDD - 14] for this case. + +## 9.4 Synchronisation of L1 configuration changes + +When a synchronised L1 configuration change shall be made, the SRNC commands the related Node B's to prepare for the change. When preparations are completed and SRNC informed, serving RNC decides appropriate change time (see TS 25.212 [24], subclause 4.2.14 and TS 25.222 [25], subclause 4.2.13). SRNC tells the CFN for the change by a suitable RRC message. The Node B's are informed the CFN by RNSAP and NBAP Synchronised Radio Link Reconfiguration procedures. + +At indicated switch time UE and Node B's change the L1 configuration. + +## 9.5 Examples of synchronisation counters during state transitions + +The example of Figure 20 shows the corrections applied to UTRAN synchronisation counters during multiple transitions from CELL\_FACH/PCH state to CELL\_DCH state before and after handover, without SRNS relocation. In this example two handover cases described in 9.3.2 are considered. + +![Figure 20: Example 1. A sequence of five network diagrams showing UTRAN synchronization transitions. Each diagram shows an SRNC connected to an RNC or DRNC, which in turn connects to multiple Node Bs (B11, B12, B13, B21, B22, B23). A UE is shown connected to one of the Node Bs. The diagrams illustrate transitions between CELL_FACH/PCH and CELL_DCH states, with specific CFN (Cell Frame Number) calculation formulas provided for each state transition. The first transition is from CELL_FACH/PCH to CELL_DCH (RNC), then to CELL_DCH (DRNC) after handover, then back to CELL_FACH/PCH (DRNC), and finally to CELL_DCH (DRNC). Arrows on the left indicate the sequence of states.](32ff77da4286b58c4778033acaa10836_img.jpg) + +**CELL\_FACH/PCH state** + +SRNC — RNC + +Node B11 (a b c)   Node B12 (a b c)   Node B13 (a b c)   Node B21 (a b c)   Node B22 (a b c)   Node B23 (a b c) + +UE (connected to Node B13) + +$CFN = SFN_{13c} \bmod 256$ + +**CELL\_DCH state** + +SRNC — RNC + +Node B11 (a b c)   Node B12 (a b c)   Node B13 (a b c)   Node B21 (a b c)   Node B22 (a b c)   Node B23 (a b c) + +UE (connected to Node B13) + +[FDD] $CFN = (SFN_{13c} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ +[TDD] $CFN = (SFN_{13c} - DOFF_{TDD}) \bmod 256$ + +**CELL\_DCH state after handover** + +SRNC — DRNC + +Node B11 (a b c)   Node B12 (a b c)   Node B13 (a b c)   Node B21 (a b c)   Node B22 (a b c)   Node B23 (a b c) + +UE (connected to Node B21) + +a) No correction to CFN +b) [FDD] $CFN = (SFN_{21a} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ +[TDD] $CFN = (SFN_{21a} - DOFF_{TDD}) \bmod 256$ + +**CELL\_FACH/PCH state** + +SRNC — DRNC + +Node B11 (a b c)   Node B12 (a b c)   Node B13 (a b c)   Node B21 (a b c)   Node B22 (a b c)   Node B23 (a b c) + +UE (connected to Node B21) + +$CFN = SFN_{21a} \bmod 256$ + +**CELL\_DCH state** + +SRNC — DRNC + +Node B11 (a b c)   Node B12 (a b c)   Node B13 (a b c)   Node B21 (a b c)   Node B22 (a b c)   Node B23 (a b c) + +UE (connected to Node B21) + +[FDD] $CFN = (SFN_{21a} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ +[TDD] $CFN = (SFN_{21a} - DOFF_{TDD}) \bmod 256$ + +$SFN_{xyk}$ : SFN of the cell k belonging to the Node Bxy + +Figure 20: Example 1. A sequence of five network diagrams showing UTRAN synchronization transitions. Each diagram shows an SRNC connected to an RNC or DRNC, which in turn connects to multiple Node Bs (B11, B12, B13, B21, B22, B23). A UE is shown connected to one of the Node Bs. The diagrams illustrate transitions between CELL\_FACH/PCH and CELL\_DCH states, with specific CFN (Cell Frame Number) calculation formulas provided for each state transition. The first transition is from CELL\_FACH/PCH to CELL\_DCH (RNC), then to CELL\_DCH (DRNC) after handover, then back to CELL\_FACH/PCH (DRNC), and finally to CELL\_DCH (DRNC). Arrows on the left indicate the sequence of states. + +Figure 20: Example 1 + +The example of Figure 21 shows the corrections applied to UTRAN synchronisation during multiple transitions from CELL\_FACH/PCH state to CELL\_DCH state after cell reselection, without SRNC relocation. + +![Figure 21: Example 2. A diagram showing four network states and transitions between them. Each state shows an SRNC connected to an RNC, CRNC, or DRNC, which in turn connect to multiple nodes (B11-B13, B21-B23). A UE is shown in each state. Transitions are labeled with states: CELL_FACH/PCH, CELL_FACH/PCH after cell reselection, CELL_DCH, and CELL_FACH/PCH. CFN (Cell Frame Number) calculation formulas are provided for each state.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +**CELL\_FACH/PCH state** + +SRNC — RNC + Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + $CFN = SFN_{13c} \bmod 256$ + UE + +**CELL\_FACH/PCH state after cell reselection** + +SRNC — CRNC + Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + $CFN = SFN_{21a} \bmod 256$ + UE + +**CELL\_DCH state** + +SRNC — DRNC + Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + [FDD] $CFN = (SFN_{21a} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ + [TDD] $CFN = SFN_{21a} \bmod 256$ + UE + +**CELL\_FACH/PCH state** + +SRNC — DRNC + Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + $CFN = SFN_{21a} \bmod 256$ + UE + +$SFN_{xyz} : SFN$ of the cell $k$ belonging to the Node $Bxy$ + +Figure 21: Example 2. A diagram showing four network states and transitions between them. Each state shows an SRNC connected to an RNC, CRNC, or DRNC, which in turn connect to multiple nodes (B11-B13, B21-B23). A UE is shown in each state. Transitions are labeled with states: CELL\_FACH/PCH, CELL\_FACH/PCH after cell reselection, CELL\_DCH, and CELL\_FACH/PCH. CFN (Cell Frame Number) calculation formulas are provided for each state. + +**Figure 21: Example 2** + +The example of Figure 22 shows the corrections applied to UTRAN synchronisation counters during multiple transitions from CELL\_FACH/PCH state to CELL\_DCH state before and after handover and SRNS relocation (without UE involvement). In this example two handover cases described in 9.3.2 are considered. + +![Figure 22: Example 3. A diagram showing five network configurations illustrating time alignment handling. Each configuration shows an SRNC or RNC connected to Node B11, B12, B13, B21, B22, and B23, with a UE connected to Node B13. The configurations are: 1. CELL_FACH/PCH state: CFN = SFN_13c mod 256. 2. CELL_DCH state: [FDD] CFN = (SFN_13c - ((DOFF_FDD * 512) div 38400)) mod 256; [TDD] CFN = (SFN_13c - DOFF_TDD) mod 256. 3. CELL_DCH state after handover: a) No correction to CFN; b) [FDD] CFN = (SFN_21a - ((DOFF_FDD * 512) div 38400)) mod 256; [TDD] CFN = (SFN_21a - DOFF_TDD) mod 256. 4. CELL_DCH state after SRNS relocation: No correction to CFN. 5. CELL_FACH/PCH state: CFN = SFN_21a mod 256. A legend at the bottom defines SFN_xyk as the SFN of the cell k belonging to the Node Bxy.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +**CELL\_FACH/PCH state** + +SRNC — RNC + +Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + +UE + +$CFN = SFN_{13c} \bmod 256$ + +**CELL\_DCH state** + +SRNC — RNC + +Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + +UE + +[FDD] $CFN = (SFN_{13c} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ +[TDD] $CFN = (SFN_{13c} - DOFF_{TDD}) \bmod 256$ + +**CELL\_DCH state after handover** + +SRNC — DRNC + +Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + +UE + +a) No correction to CFN +b) [FDD] $CFN = (SFN_{21a} - ((DOFF_{FDD} * 512) \bmod 38400)) \bmod 256$ +[TDD] $CFN = (SFN_{21a} - DOFF_{TDD}) \bmod 256$ + +**CELL\_DCH state after SRNS relocation** + +RNC — SRNC + +Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + +UE + +No correction to CFN + +**CELL\_FACH/PCH state** + +RNC — SRNC + +Node B11 Node B12 Node B13 Node B21 Node B22 Node B23 + +UE + +$CFN = SFN_{21a} \bmod 256$ + +$SFN_{xjk}$ : SFN of the cell k belonging to the Node Bxy + +Figure 22: Example 3. A diagram showing five network configurations illustrating time alignment handling. Each configuration shows an SRNC or RNC connected to Node B11, B12, B13, B21, B22, and B23, with a UE connected to Node B13. The configurations are: 1. CELL\_FACH/PCH state: CFN = SFN\_13c mod 256. 2. CELL\_DCH state: [FDD] CFN = (SFN\_13c - ((DOFF\_FDD \* 512) div 38400)) mod 256; [TDD] CFN = (SFN\_13c - DOFF\_TDD) mod 256. 3. CELL\_DCH state after handover: a) No correction to CFN; b) [FDD] CFN = (SFN\_21a - ((DOFF\_FDD \* 512) div 38400)) mod 256; [TDD] CFN = (SFN\_21a - DOFF\_TDD) mod 256. 4. CELL\_DCH state after SRNS relocation: No correction to CFN. 5. CELL\_FACH/PCH state: CFN = SFN\_21a mod 256. A legend at the bottom defines SFN\_xyk as the SFN of the cell k belonging to the Node Bxy. + +Figure 22: Example 3 + +# 10 Time Alignment Handling + +The purpose of the time alignment procedure over Iu is to minimise the buffering delay in SRNC by controlling the DL transmission timing in the CN node. The time alignment procedure is controlled by SRNC and is invoked whenever the + +SRNC detects the reception of Iu User Plane PDU at an inappropriate timing that leads to an unnecessary buffering delay. The SRNC indicates to the CN node by means of a TIME ALIGNMENT control frame. The necessary amount of the delay or advance adjustment is indicated by expressing a number of (+/-) 500 µs steps (see Figure 23). + +![Figure 23: Time Alignment Handling sequence diagram. The diagram shows vertical lines for CN and SRNC. Arrows represent DL Data Frames from CN to SRNC. A specific 'TIME ALIGNMENT [n * 500 µs]' control frame is sent from SRNC to CN, followed by an 'ACK' from CN to SRNC. A supervision timer T_TA is shown as a yellow wedge starting at the SRNC when the control frame is sent. Below the SRNC line, a 'Buffer in the SRNC' is depicted with a 'Buffer threshold' dashed line. DL Data Frames (solid arrows) are written into the buffer, and DL Data Frames (dashed arrows) are read from the buffer towards Node B.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +Figure 23: Time Alignment Handling sequence diagram. The diagram shows vertical lines for CN and SRNC. Arrows represent DL Data Frames from CN to SRNC. A specific 'TIME ALIGNMENT [n \* 500 µs]' control frame is sent from SRNC to CN, followed by an 'ACK' from CN to SRNC. A supervision timer T\_TA is shown as a yellow wedge starting at the SRNC when the control frame is sent. Below the SRNC line, a 'Buffer in the SRNC' is depicted with a 'Buffer threshold' dashed line. DL Data Frames (solid arrows) are written into the buffer, and DL Data Frames (dashed arrows) are read from the buffer towards Node B. + +**Figure 23: Time Alignment Handling** + +A supervision timer $T_{TA}$ is started after sending the Time Alignment control frame in order to supervise the reception of the TIME ALIGNMENT ACKNOWLEDGEMENT control frame. + +The requested CN node adjusts the transmission timing by the amount as indicated by SRNC and sends a time alignment acknowledgement frame (ACK). Upon reception of a time alignment acknowledgement frame, the SRNC stops the supervision timer $T_{TA}$ . + +The procedure can be signalled at any time when transfer of user data is not suspended by another control procedure. + +If the TIME ALIGNMENT control frame could not be handled by the requested CN node, a TIME ALIGNMENT NEGATIVE ACKNOWLEDGEMENT control frame (NACK) is sent with a corresponding cause. When the SRNC receives a NACK with cause "Time Alignment not supported", then the SRNC shall not send additional Time Alignment frames for that RAB (unless the Iu User Plane conditions change for that RAB). The cause value "Requested Time Alignment not possible" is used to indicate that the requested time alignment was not possible at that moment. At a later moment the SRNC may initiate a new Time Alignment procedure when needed. + +If the SRNC detects that the time alignment command has not been correctly interpreted or received, i.e. NACK received or timer expires, and the time alignment need still persists, the SRNC should re-trigger a Time Alignment procedure. If after "k" repetitions, the error situation persists, the SRNC take appropriate local actions. + +Upon reception of a NACK, the SRNC stops the supervision timer $T_{TA}$ . + +In order to avoid oscillation in the time alignment handling over Iu, it is beneficial to avoid initiating a new Time Alignment procedure too early after successful completion of a Time Alignment procedure. + +# 11 MBMS related Transport Channel Synchronisation + +## 11.1 General + +Point-to-multipoint transmission is used to transfer MBMS specific control/user plane information between the network and several UEs in RRC Connected or Idle Mode. In p-t-m mode, FACH is used as a transport channel for MTCH and MCCH. S-CCPCH is used as a physical channel for FACH carrying MTCH or MCCH. + +## 11.2 FDD MBMS related Transport Channel Synchronisation + +For support of MBMS soft combining in the UE and operation in MBSFN mode, relative timing difference of MTCH transmissions from different cells respectively from different Node Bs has to be limited. + +In the intra-Node B case, relative timing difference of MTCH transmissions is inherently controllable via S-CCPCH timing: + +- S-CCPCH CFNs have a configured timing difference relative to the P-CCPCH of the cell (e.g. *FDD SCCPCH Offset* IE TS 25.433 [3]) +- P-CCPCHs of all cells in a Node B are based on the BFN (and linked via *T Cell* IE TS 25.433 [3]). + +For the inter-Node B case synchronisation of MTCH transmissions from different cells in different Node Bs may be achieved and maintained as follows: + +1. RNC-Node B Node synchronisation (as described in chapter 6) + +After carrying out this procedure, RNC is able to calculate BFN offsets assuming that the DL and UL propagation delay have the same value. Since, for every cell the relative timing of P-CCPCHs/SFNs is known to CRNC (as *T Cell* is known in CRNC) based on this measurement. + +2. Calculations for Initial Uu-Timing Alignment of MTCH transmission on S-CCPCHs + +Taking into account that transmission of a certain MTCH PDU has to start at CFNmodTTI=0, S-CCPCH timing offsets can be chosen in a way that the relative timing offset of the same MTCH PDU can be minimised. S-CCPCH timing offsets can be created by combining *FDD SCCPCH Offset* (roughly in the range of 0..10msec TS 25.433 [3]) and *FDD S-CCPCH Frame Offset* (10msec, 20msec or 40msec; 0msec in case IE not present TS 25.433 [3]) and will be associated with those S-CCPCHs carrying MTCH at the time of set up (i.e. at COMMON TRANSPORT CHANNEL SETUP REQUEST TS 25.433 [3]). Initial Timing Alignment for MTCH Transmission is depicted in figure 24 below. + +3. Maintenance of Uu-Timing Alignment of MTCH transmissions on S-CCPCHs + +After S-CCPCHs have been established, Node Bs timing difference may increase due to drifting Node B time reference (Node B clock). Increasing differences in relative timing may be detected by the RNC when periodically performing RNC-Node B Node synchronisation measurements. In case time differences are growing unacceptably large, RNC may decide to either re-schedule the MTCH PDUs to the existing S-CCPCHs (granularity: 1TTI) or to delete and re-establish the corresponding S-CCPCHs (granularity: 256 chips when using *FDD SCCPCH Offset* TS 25.433 [3]). + +![Figure 24: Initial Timing Alignment for MTCH Transmission. The diagram shows the flow of data from an SRNC through a Router and then to two NodeBs (NodeB0 and NodeB1) and their respective cells (Cell 0 of NB0 and Cell 1 of NB1). It illustrates the timing alignment for MTCH transmission, showing the relationship between Radio Frame Numbers (RFN, BFN, CFN) and the timing of data frames. The SRNC sends a DL DATA FRAME [MFN = 255] to the Router, which then sends an IP Multicast to NodeB0 and NodeB1. NodeB0 and NodeB1 then transmit the data to their respective cells. The timing alignment is shown by the alignment of the data frames across the different nodes and cells.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +The diagram illustrates the timing alignment for MTCH transmission across different network elements. The SRNC (Radio Network Controller) sends a DL DATA FRAME with MFN = 255. The Router receives this and sends an IP Multicast. NodeB0 and NodeB1 receive the IP Multicast and then transmit the data to their respective cells. The timing alignment is shown by the alignment of the data frames across the different nodes and cells. The diagram includes frame numbers for RFN, BFN, and CFN, and the CFN Offset for each cell. + +| Node/Cell | BFN | BFN mod 256 | CFN | SCCPCH | CFN Offset | +|---------------|------------------------------------------|-----------------------------------|-----------------------------------|---------|------------| +| NodeB0 | 403, 404, 405, 406, 407, 408, 409 | 147, 148, 149, 150, 151, 152, 153 | 147, 148, 149, 150, 151, 152, 153 | SCCPCH0 | 103 | +| Cell 0 of NB0 | | | 147, 148, 149, 150, 151, 152, 153 | SCCPCH0 | 103 | +| NodeB1 | 1232, 1233, 1234, 1235, 1236, 1237, 1238 | 208, 209, 210, 211, 212, 213, 214 | 208, 209, 210, 211, 212, 213, 214 | SCCPCH1 | 43 | +| Cell 1 of NB1 | | | 208, 209, 210, 211, 212, 213, 214 | SCCPCH1 | 43 | + +Figure 24: Initial Timing Alignment for MTCH Transmission. The diagram shows the flow of data from an SRNC through a Router and then to two NodeBs (NodeB0 and NodeB1) and their respective cells (Cell 0 of NB0 and Cell 1 of NB1). It illustrates the timing alignment for MTCH transmission, showing the relationship between Radio Frame Numbers (RFN, BFN, CFN) and the timing of data frames. The SRNC sends a DL DATA FRAME [MFN = 255] to the Router, which then sends an IP Multicast to NodeB0 and NodeB1. NodeB0 and NodeB1 then transmit the data to their respective cells. The timing alignment is shown by the alignment of the data frames across the different nodes and cells. + +Figure 24: Initial Timing Alignment for MTCH Transmission +(Example: MCCH and MTCH on separate S-CCPCH; 40msec TTI on MTCH) + +## 11.3 TDD MBMS related Transport Channel Synchronisation + +Soft combining of MBMS related transmissions in the UE and MBSFN delivery may be supported by those TDD Radio Interface Synchronisation schemes depicted in section 8.3. + +## 11.4 Inter-Node B Synchronisation of MTCH Transmissions for IP Multicast + +In case a transport bearer is used by several FACH channels with IP multicast option, the transport channel synchronisations of different FACHs respectively from different Node Bs shall be maintained as described in subclause 11.2 and 11.3. In addition, when Node B receives data frame from an IP multicast group, it shall consider the value of the CFN field in the data frame as MFN and calculate the radio frame in which the first data shall be transmitted on the concerned FACH according to: + +$$\text{CFN} = (\text{MFN} - \text{CFN Offset}) \bmod 256,$$ + +where: + +- CFN Offset is a FACH parameter indicated by RNC TS 25.433 [3]. + +When setting the value of CFN Offset for a FACH, the RNC shall take into account the timing difference of different S-CCPCHs so that relative timing difference of MTCH transmissions from different cells respectively from different Node Bs can meet the requirement of the MBMS combining method used (see Figure 25). + +![Figure 25: Inter-Node B Synchronisation of MTCH Transmissions for IP Multicast. The diagram shows the timing alignment of data frames across SRNC, Router, NodeB0, Cell 0 of NB0, NodeB1, and Cell 1 of NB1. It illustrates the flow of an IP multicast data frame from the SRNC through the Router to two different NodeBs and their respective cells, showing how the frames are synchronized based on the BFN (Base Frame Number) and CFN (Cell Frame Number).](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates the timing alignment for IP multicast transmissions across different NodeBs. The timeline is shown in several horizontal tracks: + +- SRNC:** Shows RFN (Radio Frame Number) from 511 to 517. A "DL DATA FRAME [MFN = 255]" is shown being transmitted from SRNC to Router. +- Router:** Shows the "IP Multicast" data flow. +- NodeB0:** Shows BFN (Base Frame Number) from 403 to 409 and BFN mod 256 from 147 to 153. A blue box highlights the transmission of "SCCPCH0" in Cell 0 of NB0, with CFN Offset=103. +- NodeB1:** Shows BFN from 1232 to 1238 and BFN mod 256 from 208 to 214. A blue box highlights the transmission of "SCCPCH1" in Cell 1 of NB1, with CFN Offset=43. + +Arrows indicate the flow of the IP multicast data from the SRNC, through the Router, and then being distributed to NodeB0 and NodeB1. The diagram shows that the data frames are synchronized across the different NodeBs based on the BFN and CFN. + +Figure 25: Inter-Node B Synchronisation of MTCH Transmissions for IP Multicast. The diagram shows the timing alignment of data frames across SRNC, Router, NodeB0, Cell 0 of NB0, NodeB1, and Cell 1 of NB1. It illustrates the flow of an IP multicast data frame from the SRNC through the Router to two different NodeBs and their respective cells, showing how the frames are synchronized based on the BFN (Base Frame Number) and CFN (Cell Frame Number). + +**Figure 25: Inter-Node B Synchronisation of MTCH Transmissions for IP Multicast +(Example: 40msec TTI on MTCH)** + +NOTE: Please refer to section 7.2 for the detailed Timing Adjustment and Time of Arrival monitoring on Iub/Iur interfaces. + +## 11.5 3.84Mcps TDD MBSFN IMB Transport Channel Synchronisation + +High accuracy Transport Channel Synchronisation is achieved through Inter Node B Node Synchronisation (chapter 6.1.2.4), where the BFN is frequency-locked to a high accuracy Network synchronisation reference. The Transport Channel Synchronisation, as described for FDD in this document, is performed with frequency-locked BFN. + +# Annex A (informative): Change history + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|---------------------|-----|----------------------------------------------------------------------------------|--------| +| 11 | RP-010164 | 14 | | Approved at TSG RAN #11 | 4.0.0 | +| 11 | RP-010166 | 16, 17 | | Approved at TSG RAN #11 | 4.0.0 | +| 12 | RP-010371 | 019,0
20,02
4 | | Approved at TSG RAN #12 | 4.1.0 | +| 12 | RP-010390 | 021.0
22 | | Approved at TSG RAN #12 | 4.1.0 | +| 13 | RP-010576 | 027 | | Notation of Time Instances | 4.2.0 | +| 13 | RP-010705 | 025 | 1 | Correction of the Frequency Accuracy in the Frequency Acquisition Phase | 4.2.0 | +| 14 | RP-010869 | 028 | | Text amendments for TDD Node B synchronisation | 4.3.0 | +| 14 | RP-010846 | 030 | 2 | Correction to CFN Calculation for UE | 4.3.0 | +| 15 | RP-020163 | 034 | | Clarification on the DPCH frame offset | 4.4.0 | +| 15 | RP-020191 | 032 | | Node B Synchronisation for 1.28Mcps TDD | 5.0.0 | +| 16 | RP-020400 | 037 | | Reference corrections | 5.1.0 | +| 20 | RP-030318 | 039 | | Removal of the Frequency Acquisition for Late-Entrant Cells for 1.28Mcps TDD | 5.2.0 | +| 22 | RP-030684 | 042 | 1 | Removal of the ambiguity about the activation time | 5.3.0 | +| 22 | - | - | - | Introduction of Release 6 specification | 6.0.0 | +| 26 | RP-040437 | 045 | 3 | MBMS related changes | 6.1.0 | +| 27 | RP-050056 | 046 | - | Introduction of Fractional DPCH | 6.2.0 | +| 28 | RP-050222 | 048 | - | Feature clean-up: Removal of DSCH (FDD mode) | 6.3.0 | +| 28 | RP-050228 | 050 | 1 | Synchronisation for MBMS p-t-m Transmissions from Multiple Cells (Simulcast) | 6.3.0 | +| 31 | RP-060073 | 051 | 1 | Introduction of 7.68Mcps TDD option | 7.0.0 | +| 33 | RP-060499 | 053 | - | Correction of CFN for MBMS | 7.1.0 | +| 34 | RP-060702 | 055 | - | Adding a new formula for Frame Offset and Chip Offset calculation | 7.2.0 | +| 34 | RP-060837 | 056 | 1 | Consistency of Specification Notations | 7.2.0 | +| 36 | RP-070335 | 58 | - | Introduction of MBMS SFN (TDD) | 7.3.0 | +| 36 | RP-070333 | 59 | - | Introduction of MBMS SFN (FDD) | 7.3.0 | +| 36 | RP-070336 | 61 | - | Introduction of MBMS LCR TDD physical layer enhancements | 7.3.0 | +| 37 | RP-070568 | 63 | 1 | Introduction of GANSS (Galileo and Additional Navigation Satellite Systems) | 7.4.0 | +| 37 | RP-070629 | 64 | | Timing Advance Corrections for 3.84/7.68 Mcps TDD EDCH | 7.4.0 | +| 38 | RP-070846 | 65 | 2 | The Improvement of Iub Efficiency for MBMS in IP RAN | 7.5.0 | +| 38 | RP-070840 | 67 | | Further corrections on Enhanced Cell FACH | 7.5.0 | +| 41 | RP-080575 | 74 | - | Enable node synchronization is supported by the user plane protocols for HS-DSCH | 7.6.0 | +| 42 | RP-081120 | 0076 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.0.0 | +| 44 | RP-090633 | 0077 | | Correction of Transport Channel Synchronisation contradiction | 8.1.0 | +| 12/2009 | | | | Created version 9.0.0 based on version 8.1.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Created version 10.0.0 based on version 9.0.1 | 10.0.0 | +| 06/2011 | RP-110686 | 0079 | | Correction related to the References and clean-up of 25.402 | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | - | - | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2014 | RP-142093 | 0080 | 1 | Rapporteur Review | 12.1.0 | +| 12/2015 | - | - | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25410/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/25_series/25410/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..879a7ceccd065fee03f3069967d32a577f03c661 --- /dev/null +++ b/marked/Rel-16/25_series/25410/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2abab724f2da0f1b5517f7c01df578b289a41aa62bf0ca811c438eddcd86cd5 +size 121464 diff --git a/marked/Rel-16/25_series/25410/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/25_series/25410/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..844c2a785fee3fda69267da52e2a5213fff48e30 --- /dev/null +++ b/marked/Rel-16/25_series/25410/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6ff39bf37d0ec59af87d0de6b530c6d0f3f5d8ac38ffb1c661ea83ef8e81cf6 +size 57498 diff --git a/marked/Rel-16/25_series/25410/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/25_series/25410/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c858ce03f2f43c3a503de93f59bb078e0a44a8a7 --- /dev/null +++ b/marked/Rel-16/25_series/25410/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9af8097ca5d231d6e4882987702e117e7965de937985230d087b2a82ebb26df +size 49003 diff --git a/marked/Rel-16/25_series/25410/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/25_series/25410/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e49ab94fffa395ff977bf86414a0d524c9a529bc --- /dev/null +++ b/marked/Rel-16/25_series/25410/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a6bd599ead44c8cd0d7fcdd20323bbd03c0bb3321e09ad24a5120a5d2bc024 +size 58938 diff --git a/marked/Rel-16/25_series/25410/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-16/25_series/25410/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89625ebf4517388cbb842e1f480dacd9e906a382 --- /dev/null +++ b/marked/Rel-16/25_series/25410/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cf77a0509d189bfb0bd2a0afca3de1dc9dab139022ade0794cdb61b0eb50e9 +size 99328 diff --git a/marked/Rel-16/25_series/25410/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/25_series/25410/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f3cbb22588c2e6f7bf335b6fbf04dea57aabfcb --- /dev/null +++ b/marked/Rel-16/25_series/25410/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7da66a9956d2168237bb1eb4908090379761c9cf1a3f83bac98fdb365992d4a +size 128243 diff --git a/marked/Rel-16/25_series/25410/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/Rel-16/25_series/25410/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffa03199a0c8e0b94e9dae3c9bced3a39fd69c1f --- /dev/null +++ b/marked/Rel-16/25_series/25410/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:138678d29b56e748b4fe382396df021b3975f98e75b446cf7f7f1b0eaa7b0d25 +size 55838 diff --git a/marked/Rel-16/25_series/25410/raw.md b/marked/Rel-16/25_series/25410/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3dd5464c3393bcf0d2049f670ccb2c96e1ed2296 --- /dev/null +++ b/marked/Rel-16/25_series/25410/raw.md @@ -0,0 +1,1024 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 3.3 Specification Notations ..... | 8 | +| 4 General Aspects ..... | 9 | +| 4.1 UTRAN Architecture ..... | 9 | +| 4.1.1 Iu Interface Architecture..... | 9 | +| 4.1.2 I u connection principles ..... | 10 | +| 4.1.3 Implementation of the NAS Node Selection Function..... | 10 | +| 4.1.4 Implementation of MOCN configuration support..... | 10 | +| 4.2 I u Interface General Principles ..... | 10 | +| 4.3 I u Interface Specification Objectives..... | 10 | +| 4.4 I u Interface Capabilities..... | 11 | +| 4.5 I u Interface Characteristics ..... | 12 | +| 4.5.1 Use of Transport Network User Plane as Signalling Bearer ..... | 12 | +| 4.5.1.1 Use of SCCP..... | 12 | +| 4.5.1.1.1 General ..... | 12 | +| 4.5.1.1.2 SCCP Connection Establishment procedure..... | 12 | +| 4.5.1.1.3 SCCP Connection Release procedure ..... | 14 | +| 4.5.1.1.4 General SCCP Abnormal Conditions..... | 15 | +| 4.5.1.2 Use of MTP3b..... | 15 | +| 4.5.2 Use of Transport Network User Plane as User Data Bearer..... | 15 | +| 4.5.2.1 Use of AAL2..... | 15 | +| 4.5.2.2 Use of GTP-U ..... | 15 | +| 4.5.2.3 Use of RTP..... | 15 | +| 4.5.3 Use of Transport Network User Plane on Iu-BC..... | 15 | +| 5 Functions of the I u Interface Protocols & Functional Split..... | 16 | +| 5.1 General ..... | 16 | +| 5.2 RAB management Functions ..... | 18 | +| 5.2.1 RAB establishment, modification and release function ..... | 18 | +| 5.2.2 RAB characteristics mapping to Uu bearers function ..... | 18 | +| 5.2.3 RAB characteristics mapping to Iu transport bearers..... | 18 | +| 5.2.4 RAB queuing, pre-emption and priority function ..... | 18 | +| 5.3 Radio Resource Management over Iu ..... | 19 | +| 5.3.1 Radio resource admission control ..... | 19 | +| 5.3.2 Broadcast information management..... | 19 | +| 5.4 I u link Management functions ..... | 19 | +| 5.4.1 I u Signalling Link Management function ..... | 19 | +| 5.4.2 ATM Virtual Connection Management function ..... | 19 | +| 5.4.3 AAL2 connection establish and release function ..... | 19 | +| 5.4.4 AAL5 management function ..... | 19 | +| 5.4.5 GTP-U tunnels management function ..... | 19 | +| 5.4.6 TCP Management Function..... | 20 | +| 5.4.7 Buffer Management..... | 20 | +| 5.4.8 RTP Session Management Function ..... | 20 | +| 5.5 I u U-plane (RNL) Management Functions ..... | 20 | +| 5.5.1 I u U-plane frame protocol mode selection function..... | 20 | +| 5.5.2 I u U-plane frame protocol initialisation ..... | 20 | +| 5.6 Mobility Management Functions ..... | 20 | +| 5.6.1 Location information update function ..... | 20 | +| 5.6.2 Handover and Relocation functions ..... | 21 | +| 5.6.2.1 Inter RNC hard HO function, Iur not used or not available ..... | 21 | +| 5.6.2.2 Serving RNS Relocation function..... | 21 | + +| | | | +|------------------------|-----------------------------------------------------------------------------------------------|----| +| 5.6.2.3 | Inter system Handover (e.g. UMTS-GSM) function ..... | 21 | +| 5.6.2A | Inter System Change (e.g. UMTS-GSM) function..... | 21 | +| 5.6.3 | Paging Triggering..... | 21 | +| 5.6.4 | Shared Networks Access Control..... | 21 | +| 5.6.5 | GERAN System Information Retrieval..... | 21 | +| 5.7 | Security Functions..... | 21 | +| 5.7.1 | Data Confidentiality ..... | 21 | +| 5.7.1.1 | Radio interface ciphering function ..... | 21 | +| 5.7.1.2 | Ciphering key management function..... | 22 | +| 5.7.2 | Data integrity ..... | 22 | +| 5.7.2.1 | Integrity checking ..... | 22 | +| 5.7.2.2 | Integrity key management ..... | 22 | +| 5.8 | Service and Network Access Functions ..... | 22 | +| 5.8.1 | Core Network signalling data transfer function ..... | 22 | +| 5.8.2 | Data Volume Reporting..... | 22 | +| 5.8.3 | UE Tracing ..... | 22 | +| 5.8.4 | Location reporting function..... | 22 | +| 5.8.5 | MDT ..... | 22 | +| 5.9 | Co-ordination Functions..... | 22 | +| 5.9.1 | Paging Co-ordination function ..... | 22 | +| 5.9.2 | NAS Node Selection Function ..... | 23 | +| 5.9.3 | Information Transfer Function ..... | 23 | +| 5.9.4 | MOCN Rerouting Function..... | 23 | +| 5.9.5 | SIPTO at Iu-PS Function..... | 23 | +| 5.9.6 | SIPTO at the Local Network with Standalone GW..... | 23 | +| 5.10 | MBMS Functions ..... | 23 | +| 5.10.1 | MBMS RAB Management functions ..... | 23 | +| 5.10.2 | MBMS UE Linking Function..... | 23 | +| 5.10.3 | MBMS Registration Control Function ..... | 23 | +| 5.10.4 | MBMS Enquiry Function ..... | 24 | +| 6 | I u Interface Protocol Structure..... | 24 | +| 6.1 | General ..... | 24 | +| 6.2 | Iu-CS ..... | 25 | +| 6.3 | I u -BC..... | 26 | +| 6.4 | I u -PS ..... | 27 | +| 7 | Other I u Interface Specifications ..... | 27 | +| 7.1 | UTRAN I u Interface: Layer 1 (3GPP TS 25.411) ..... | 27 | +| 7.2 | UTRAN I u Interface: Signalling Transport (3GPP TS 25.412) ..... | 27 | +| 7.3 | UTRAN I u Interface: RANAP Specification (3GPP TS 25.413)..... | 27 | +| 7.4 | UTRAN I u Interface: Data Transport and Transport Signalling (3GPP TS 25.414)..... | 28 | +| 7.5 | UTRAN I u Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415)..... | 28 | +| 7.6 | UTRAN I u Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) ..... | 28 | +| 7.7 | Summary ..... | 28 | +| Annex A (informative): | Change History..... | 29 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 3GPP TS 25.41x series of Technical Specifications that define the Iu interface for the interconnection of Radio Network Controller (RNC) component of the UMTS Terrestrial Radio Access Network (UTRAN) to the Core Network of the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.401: "UTRAN Overall Description". +- [2] 3GPP TR 23.930: "Iu Principles". +- [3] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions". +- [4] 3GPP TS 25.411: "UTRAN Iu Interface Layer 1". +- [5] 3GPP TS 25.412: "UTRAN Iu Interface Signalling Transport". +- [6] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [7] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling". +- [8] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols". +- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [14] 3GPP TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP". +- [15] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [16] ITU-T Recommendation Q.2630.1: "AAL type 2 signalling protocol - (Capability Set 1)". +- [17] ITU-T Recommendation Q.2630.2: "AAL type 2 signalling protocol - Capability Set 2". +- [18] IETF RFC 3332 (2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [19] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications". +- [20] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [21] IETF RFC 793 (1981-09): "TCP, Transmission Control Protocol". + +- [22] IETF RFC 791 (1981-09): "Internet Protocol". +- [23] Void +- [24] Void +- [25] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [26] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [27] 3GPP TS23.246: Multimedia Broadcast/Multicast Service (MBMS) Architecture and functional description +- [28] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [29] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [30] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 25.401 [1] apply. + +### MBMS related terms and definitions: + +**MBMS bearer service:** as defined in TS 23.246 [27]. + +**MBMS RAB:** as defined in TS 25.346 [28]. + +**MBMS Iu signalling connection:** as defined in TS 25.346 [28]. + +**MBMS session start:** as defined in TS 25.346 [28]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|------------------------------------------------------| +| 3G-MSC | 3 rd Generation Mobile Switching Centre | +| 3G-SGSN | 3 rd Generation Serving GPRS Support Node | +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| BC | Broadcast | +| BSSMAP | Base Station Subsystem Management Application Part | +| CBS | Cell Broadcast Service | +| CC | Connection Confirm | +| CN | Core Network | +| CR | Connection Release | +| CREF | Connection Refusal | +| CS | Circuit Switched | +| GT | Global Title | +| GTP-U | GPRS Tunnelling Protocol | +| GWCN | Gateway Core Network | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| L-GW | Local GateWay | +| LA | Location Area | + +| | | +|----------|--------------------------------------------------| +| M3UA | MTP3 User Adaptation Layer | +| MBMS | Multimedia Broadcast Multicast Service | +| MDT | Minimization of Drive-Tests | +| MOCN | Multi Operator Core Network | +| NAS | Non Access Stratum | +| NACC | Network Assisted Cell Change | +| NNSF | NAS Node Selection Function | +| O&M | Operation and Maintenance | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | +| PSTN | Public Switched Telephone Network | +| PVC | Permanent Virtual Circuit | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RA | Routing Area | +| RAB | Radio Access Bearer | +| RANAP | Radio Access Network Application Part | +| RIM | RAN Information Management | +| RLP | Radio Link Protocol | +| RNC | Radio Network Controller | +| RNL | Radio Network Layer | +| RRC | Radio Resource Control | +| RTCP | Real Time Control Protocol | +| RTP | Real Time Protocol | +| SA | Service Area | +| SABP | Service Area Broadcast Protocol | +| SAP | Service Access Point | +| SCCP | Signalling Connection Control Part | +| SIPTO | Selected IP Traffic Offload | +| SIPTO@LN | Selected IP Traffic Offload at the Local Network | +| SCTP | Stream Control Transmission Protocol | +| SNA | Shared Network Area | +| SPC | Signalling Point Code | +| SRNS | Serving Radio Network Subsystem | +| SSN | Sub-System Number | +| SVC | Switched Virtual Circuit | +| S-GW | Serving GateWay | +| TCP | Transmission Control Protocol | +| UE | User Equipment | +| UDP | User Datagram Protocol | +| UP | User Plane | +| URA | UTRAN Registration Area | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VC | Virtual Circuit | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Network Layer procedures. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | +| Frame | When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH transport frame. | + +# 4 General Aspects + +## 4.1 UTRAN Architecture + +### 4.1.1 Iu Interface Architecture + +The overall UMTS architecture and UTRAN architectures are described in TS 25.401 [1]. This subclause specifies only the architecture of the Iu interface, and shall not constrain the network architecture of either Core or Radio Access Networks. + +The Iu interface is specified at the boundary between the Core Network and UTRAN. Figure 4.1 depicts the logical division of the Iu interface. From the Iu perspective, the UTRAN access point is an RNC. + +![Figure 4.1: Iu Interface Architecture diagram showing UTRAN on the left and Core Network (CN) on the right, separated by the Iu Interface. UTRAN contains four Node Bs connected to two RNCs. The RNCs are connected to the Iu Interface, which is then connected to three domains in the CN: CS Domain, PS Domain, and BC Domain. The connections are labeled 'Iu-CS', 'Iu-PS', and 'Iu-BC'.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +The diagram illustrates the Iu Interface Architecture. On the left, the UTRAN (Radio Access Network) contains four Node Bs connected to two RNCs (Radio Network Controllers). The RNCs are connected to the Iu Interface, which is represented by a vertical dashed line. On the right, the Core Network (CN) is divided into three domains: CS Domain (Circuit Switched), PS Domain (Packet Switched), and BC Domain (Broadcast). The RNCs are connected to these domains via the Iu Interface. The connections are labeled as follows: 'Iu-CS' for the CS Domain, 'Iu-PS' for the PS Domain, and 'Iu-BC' for the BC Domain. The diagram shows that each RNC can have multiple connections to different domains in the CN. + +Figure 4.1: Iu Interface Architecture diagram showing UTRAN on the left and Core Network (CN) on the right, separated by the Iu Interface. UTRAN contains four Node Bs connected to two RNCs. The RNCs are connected to the Iu Interface, which is then connected to three domains in the CN: CS Domain, PS Domain, and BC Domain. The connections are labeled 'Iu-CS', 'Iu-PS', and 'Iu-BC'. + +**Figure 4.1: Iu Interface Architecture** + +The Iu interface towards the PS-domain of the core network is called Iu-PS, and the Iu interface towards the CS-domain is called Iu-CS. The differences between Iu-CS and Iu-PS are treated elsewhere in the present document. The Iu interface to the Broadcast domain is called Iu-BC. + +There shall not be more than one Iu interface (Iu-PS) towards the PS-domain from any one RNC— except where the NNSF is used, see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. Each RNC shall not have more than one Iu interface (Iu-CS) towards its default CN node within the CS domain, but may also have further Iu interfaces (Iu-CS) towards other CN nodes within the CS domain. (See [6] for definition of Default CN node.) These further Iu interfaces (Iu-CS) shall only be used as a result of intra-MSC inter-system handover or SRNS relocation, in the case the anchor CN node directly connects to the target RNC. There may also be more than one Iu interface towards the CS-Domain if the NNSF is used – see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. There shall not be more than one Iu interface (Iu-BC) from an RNC towards the Broadcast domain. + +In the separated core network architecture, this means that there shall be separate signalling and user data connections towards the PS and CS domains – this applies in both transport and radio network layers. + +In the combined architecture, there shall be separate connections in the user plane towards the PS and CS domains (in both transport and radio network layers). In the control plane, there shall be separate SCCP connections to the two logical domains. + +In either architecture, there can be several RNCs within UTRAN and so UTRAN may have several Iu access points towards the Core Network. As a minimum, each Iu access point (in UTRAN or CN) shall independently fulfil the requirements of the relevant Iu specifications (25.41x series – see clause 7). + +### 4.1.2 Iu connection principles + +The Iu interface has a hierarchical architecture where one higher layer entity controls several lower layer entities. The hierarchy for the CN - UTRAN signalling connection end points is described below: + +- Each CN Access Point may be connected to one or more UTRAN Access Points. +- For the PS domain, each UTRAN Access Point shall not be connected to more than one CN Access Point – except where the NNSF is used, see subclause 4.1.3, or when RNC is shared in MOCN configuration.. +- For the CS domain, each UTRAN Access Point may be connected to one or more CN Access Points. +- For the BC domain, each UTRAN Access Point may be connected to one CN Access Point only. + +### 4.1.3 Implementation of the NAS Node Selection Function + +The optional NAS Node Selection Function (NNSF) is described in TS 23.236 [25]. + +If the NAS Node Selection Function is used by an RNC: + +- There may be more than one Iu interface (Iu-CS) towards the CS domain and/or more than one Iu interface (Iu-PS) towards the PS-domain from this RNC. + +### 4.1.4 Implementation of MOCN configuration support + +The MOCN configuration is described in TS 23.251 [26]. When the RNC is shared in MOCN configuration: + +- There may be more than one Iu interface (Iu-CS) towards the CS domain of different CN operators and/or more than one Iu interface (Iu-PS) towards the PS-domain of different CN operators from this RNC. +- The MOCN Rerouting Function shall be supported. + +## 4.2 Iu Interface General Principles + +From a UTRAN perspective, maximising the commonality of the various protocols that flow on the Iu interface is desirable. This means at the minimum that: + +- A common set of radio access bearer services will be offered by UTRAN to the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN). + +There will be a common functional split between UTRAN and the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN). + +Signalling in the radio network control plane shall not depend on the specific choice of transport layers. + +## 4.3 Iu Interface Specification Objectives + +The following objectives are partly derived from TR 23.930 [2]. + +The Iu interface shall be specified such that it can support: + +- the interconnection of RNCs with Core Network Access Points within a single PLMN, and within several PLMNs in case of network sharing, as described in TS 23.251 [26]. +- the interconnection of RNCs with Core Network Access Points irrespective of the manufacturer of any of the elements. +- all UMTS services. + +The Iu interface shall facilitate the use of the same RNC, MSC or SGSN in all PLMNs. + +The Iu interface shall facilitate the sharing of transport technology between Iu-PS and Iu-BC. + +The Iu interface shall allow interworking to the GSM Core Network. + +Independence between the protocol layers and between control and user planes shall be maintained on the Iu interface. + +The Iu interface shall allow independent evolution of technologies within the Core, Radio Access and Transport Networks. + +The Iu interface shall allow separate evolution of O&M facilities. + +The Iu interface shall be standardised as an open and multi-vendor interface. + +The Iu interface specifications shall facilitate the migration of some services from the CS-domain to the PS-domain. In particular, the RANAP protocol shall be common to both PS and CS domains, and the Iu user plane protocol(s) shall be independent of the core network domain (PS or CS), except where a specific feature is only required for one domain. + +## 4.4 Iu Interface Capabilities + +The following capabilities are derived from the requirements described in TR 23.930 [2]. + +The Iu interface supports: + +- procedures to establish, maintain and release Radio Access Bearers; +- procedures to perform SRNS relocation, intra-system handover, inter-system handover and inter-system change; +- procedures to support the Cell Broadcast service; +- a set of general procedures, not related to a specific UE; +- the separation of each UE on the protocol level for user specific signalling management; +- the transfer of NAS signalling messages between UE and CN; +- location services by transferring requests from the CN to UTRAN, and location information from UTRAN to CN. The location information may comprise a geographical area identifier or global co-ordinates with uncertainty parameters; +- simultaneous access to multiple CN domains for a single UE; +- mechanisms for resource reservation for packet data streams; +- procedures to support MBMS bearer services; +- mechanisms to support SIPTO at Iu-PS for a specific UE (optional); +- mechanisms to support SIPTO at the Local Network with standalone GW for a specific UE (optional). + +## 4.5 Iu Interface Characteristics + +### 4.5.1 Use of Transport Network User Plane as Signalling Bearer + +#### 4.5.1.1 Use of SCCP + +##### 4.5.1.1.1 General + +The SCCP (ITU-T Rec. Q.711 [9] /ITU-T Rec. Q.712 [10]/ITU-T Rec. Q.713 [11]/ITU-T Rec. Q.714 [12]) is used to support signalling messages between the CNs and the RNC. One user function of the SCCP, called Radio Access Network Application Part (RANAP), is defined. The RANAP uses one SCCP signalling connection per active UE and CN for the transfer of layer 3 messages. RANAP also uses one SCCP signalling connection per MBMS bearer service. + +Both connectionless and connection-oriented procedures are used to support the RANAP. TS 25.413 [6] explains whether connection oriented or connectionless services should be used for each layer 3 procedure. + +RANAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing scheme to use for the SCCP is an operator matter. + +When GT addressing is utilised, the following settings shall be used: + +- SSN Indicator = 1 (RANAP SSN as defined in TS 23.003 [13] shall always be included). +- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator). +- Translation Type = 0000 0000 (not used). +- Numbering Plan = 0001 (E.163/4). +- Nature of Address Indicator = 000 0100 (International Significant Number). +- Encoding Scheme = 0001 or 0010 (BCD, odd or even). +- Routing indicator = 0 or 1 (route on GT or PC/SSN). + +When used, the GT shall be the E.164 address of the relevant node. + +The following subclauses describe the use of SCCP connections for RANAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection release procedures. Subclause 4.5.1.4 describes abnormal conditions. + +##### 4.5.1.1.2 SCCP Connection Establishment procedure + +A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between RNC and CN, and no SCCP connection exists between the CN and the RNC involved, for the concerned UE. A new SCCP connection is also established for MBMS service purpose between the RNC and CN. + +Various SCCP connection establishment cases have to be distinguished: + +- i) RNC Initiated SCCP Signalling Connection for a UE; +- ii) CN Initiated SCCP Signalling Connection for a UE; +- iii) CN Initiated SCCP Signalling Connection for an MBMS Service. + +The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future. + +###### 4.5.1.1.2.1 Establishment procedure in case i + +The SCCP signalling connection establishment is initiated, by the RNC, at the reception of the first layer 3 non access stratum message from the UE or at the execution of the enhanced relocation or at the initiation of the UE Registration Query procedure. + +###### Initiation + +The RNC sends SCCP CONNECTION REQUEST message to the Core Network. A RANAP message shall be included in the user data field of the SCCP CONNECTION REQUEST message when the RANAP message size is less than or equal to the maximum size of the user data field in the SCCP CONNECTION REQUEST message. When the RANAP message is longer than the maximum size, the user data field shall not be included in the SCCP CONNECTION REQUEST message. + +If the Core Network receives an SCCP CONNECTION REQUEST message for a UE for which an SCCP connection already exists, or if the Core Network receives an SCCP CONNECTION REQUEST message that does not include a user data field, and later finds out that the SCCP CONNECTION REQUEST message was for a UE for which an SCCP connection already exists, the Core Network shall ensure that the new SCCP connection and the already existing SCCP connection are for the same UE, e.g. by security functions, and if so, release the already existing SCCP connection via the normal Iu Release procedure and all UTRAN resources allocated to it. + +###### Termination + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the RNC. +- **unsuccessful outcome** + +- If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the RNC. This message may contain a RANAP message in the user data field. + +For more information on how the RANAP procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query are handled, please see the elementary procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query in TS 25.413 [6]. + +![Sequence diagram for RNC Initiated SCCP Signalling Connection. It shows the RNC sending a CR (Connection Request) to the CN, and the CN responding with either a CC (Connection Confirm) or a CREF (Connection Reference) message. The diagram includes message details like SSN=RANAP and local/destination references a1, a2, x, and y.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note right of RNC: RNC + Note right of CN: CN + RNC->>CN: CR {SSN=RANAP, a1=x, RANAP message or no user data} + Note right of CN: CC {a1=y, a2=x, RANAP message or no user data} + Note right of CN: or + Note right of CN: CREF{a2=x, RANAP message or no user data} + CN-->>RNC: CC or CREF + Note right of RNC: a1 = source local reference, + Note right of RNC: a2 = destination local reference, + Note right of RNC: x = SCCP connection reference at the RNC, + Note right of RNC: y = SCCP connection reference at the CN. + +``` + +Sequence diagram for RNC Initiated SCCP Signalling Connection. It shows the RNC sending a CR (Connection Request) to the CN, and the CN responding with either a CC (Connection Confirm) or a CREF (Connection Reference) message. The diagram includes message details like SSN=RANAP and local/destination references a1, a2, x, and y. + +**Figure 4.2: Setting-up of RNC Initiated SCCP Signalling Connection** + +###### **4.5.1.1.2.2 Establishment procedure in case ii** + +The SCCP signalling connection establishment is initiated, by the Core Network, in connection with performing a Relocation. + +###### **Initiation** + +The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message. + +###### **Termination** + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network. +- **unsuccessful outcome** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field. + +![Sequence diagram for CN Initiated SCCP Signalling Connection. It shows the CN sending a CR (Connection Request) to the RNC, and the RNC responding with either a CC (Connection Confirm) or a CREF (Connection Reference) message. The diagram includes message details like SSN=RANAP and local/destination references a1, a2, x, and y.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note right of RNC: RNC + Note right of CN: CN + CN->>RNC: CR {SSN=RANAP, a1=y, RANAP message or no user data} + Note right of RNC: CC {a1=x, a2=y, RANAP message or no user data} + Note right of RNC: or + Note right of RNC: CREF{a2=y, RANAP message or no user data} + RNC-->>CN: CC or CREF + Note right of RNC: a1 = source local reference, + Note right of RNC: a2 = destination local reference, + Note right of RNC: x = SCCP connection reference at the RNC, + Note right of RNC: y = SCCP connection reference at the CN. + +``` + +Sequence diagram for CN Initiated SCCP Signalling Connection. It shows the CN sending a CR (Connection Request) to the RNC, and the RNC responding with either a CC (Connection Confirm) or a CREF (Connection Reference) message. The diagram includes message details like SSN=RANAP and local/destination references a1, a2, x, and y. + +**Figure 4.3: Setting-up of CN Initiated SCCP Signalling Connection** + +###### 4.5.1.1.2.3 Establishment procedure in case iii + +The SCCP signalling connection establishment is initiated, by the Core Network, to establish a new SCCP connection between the RNC and the CN for an MBMS service at the start of an MBMS session and when no SCCP connection already exists between the CN and the RNC involved, for the concerned MBMS service. + +###### Initiation + +The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message. + +###### Termination + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network. +- **unsuccessful outcome** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field. + +##### 4.5.1.1.3 SCCP Connection Release procedure + +This procedure is always initiated at the Core Network side in normal release case. + +An SCCP connection is released when the CN realises that a given signalling connection is no longer required. + +The CN sends a SCCP RELEASED message. + +The procedure may be initiated at the Core Network side and the RNC side in any abnormal release case. + +##### 4.5.1.1.4 General SCCP Abnormal Conditions + +If a user-out-of-service information or signalling-point-inaccessible information is received by the RANAP, no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received. + +When a user-out-of-service information or signalling-point-inaccessible is received by the RNC, an optional timer may be started. When the timer expires, all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped. + +If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RANAP procedures are being performed or while a dedicated resource is still allocated, the following actions are taken: + +###### At RNC: + +- Any RNC procedure relating to that connection is abandoned. +- The UTRAN resources allocated to the connection are released. + +###### At Core Network: + +- The resources associated with the SCCP connection are cleared as soon as possible. + +#### 4.5.1.2 Use of MTP3b + +- For a given MSC, the RNC shall be able to access RANAP and ALCAP either under the same MTP3b (IETF RFC 3332 [18]) destination point code, or under different point codes; +- For a given RNC, the MSC shall be able to access RANAP and ALCAP either under the same MTP3b destination point code, or under different point codes. + +### 4.5.2 Use of Transport Network User Plane as User Data Bearer + +#### 4.5.2.1 Use of AAL2 + +In the ATM transport option AAL2 is used as the user data bearer towards the CS domain. + +Q.2630.2 is used as the protocol for dynamically setup AAL-2 connections over Iu towards the CS domain. Q.2630.2 adds new optional capabilities to Q.2630.1. + +#### 4.5.2.2 Use of GTP-U + +GTP-U is used as the user data bearer towards the PS domain. + +RANAP Signalling is used to establish, modify and release the GTP-U tunnels towards the PS domain. + +#### 4.5.2.3 Use of RTP + +RTP/UDP/IP (IETF RFC 1889 [19]/ IETF RFC 768 [20]/ IETF RFC 791[22]) is used as the user data bearer towards the CS domain in the IP transport option. The use of RTCP (IETF RFC 1889 [19]) is optional. + +RANAP Signalling is used to establish, modify and release RTP sessions towards the CS domain. + +### 4.5.3 Use of Transport Network User Plane on Iu-BC + +TCP/IP (IETF RFC 793[21]/ IETF RFC 791[22]) is used as the bearer for the radio network layer protocol over Iu-BC. + +The TCP connection is normally established by the CN using standard TCP procedures. + +A new TCP connection is established by the RNC only when there is information (e.g. failure or restart indications) that needs to be sent from RNC to the CN, and there is no existing TCP connection. The RNC shall establish the connection using standard TCP procedures. + +The node that established the connection shall release the TCP connection. + +# --- 5 Functions of the Iu Interface Protocols & Functional Split + +## 5.1 General + +This subclause defines the functional split between the core network and the UMTS radio access network. In addition, the possible interaction between the functions is defined. The functional split is shown in table 5.1. + +**Table 5.1: Iu interface functional split** + +| Function | UTRAN | CN | +|-----------------------------------------------------------------|-------|----| +| RAB management functions: | | | +| RAB establishment, modification and release | X | X | +| RAB characteristics mapping I u transmission bearers | X | | +| RAB characteristics mapping Uu bearers | X | | +| RAB queuing, pre-emption and priority | X | X | +| Radio Resource Management functions: | | | +| Radio Resource admission control | X | | +| Broadcast Information | X | X | +| Iu link Management functions: | | | +| I u signalling link management | X | X | +| ATM VC management | X | X | +| AAL2 establish and release | X | X | +| AAL5 management | X | X | +| GTP-U Tunnels management | X | X | +| TCP Management | X | X | +| Buffer Management | X | | +| Iu U-plane (RNL) Management: | | | +| I u U-plane frame protocol management | | X | +| I u U-plane frame protocol initialization | X | | +| Mobility management functions: | | | +| Location information reporting | X | X | +| Handover and Relocation | | | +| Inter RNC hard HO, Iur not used or not available | X | X | +| Serving RNS Relocation (intra/inter MSC) | X | X | +| Inter system hard HO (UMTS-GSM) | X | X | +| Inter system Change (UMTS-GSM) | X | X | +| Paging Triggering | | X | +| GERAN System Information Retrieval | X | X | +| Security Functions: | | | +| Data confidentiality | | | +| Radio interface ciphering | X | | +| Ciphering key management | | X | +| User identity confidentiality | X | X | +| Data integrity | | | +| Integrity checking | X | | +| Integrity key management | | X | +| Service and Network Access functions: | | | +| CN Signalling data | X | X | +| Data Volume Reporting | X | | +| UE Tracing | X | X | +| MDT | X | X | +| Location reporting | X | X | +| QoE | X | X | +| Iu Co-ordination functions: | | | +| Paging co-ordination | X | X | +| NAS Node Selection Function | X | | +| MOCN Rerouting Function | X | X | +| SIPTO at Iu-PS | X | X | +| SIPTO at the Local Network with Standalone GW | X | X | +| MBMS functions | X | X | +| MBMS RAB Management | X | X | +| MBMS UE Linking Function | X | X | +| MBMS Registration Control Function | X | X | +| MBMS Enquiry Function | X | X | + +## 5.2 RAB management Functions + +### 5.2.1 RAB establishment, modification and release function + +The RAB, Radio Access Bearer, is defined to be set-up between UE and CN. Depending on subscription, service, requested QoS etc. different types of RABs will be used. It is the CN that controls towards the UTRAN the establishment, modification or release of a RAB. Furthermore, the CN selects the type of the transport bearer, i.e. ATM or IP. + +The RAB identity is allocated by CN by mapping the value for the NAS Binding information (from the actual protocol IE for the respective CN domain) to the RAB ID as specified in TS 23.110 [3]. The RAB identity is globally significant on both the radio bearer and on the Iu bearer for a given UE in a particular CN domain. + +RAB establishment, modification and release is a CN initiated function. + +RAB establishment, modification and release is a UTRAN executed function. + +RAB release request is a UTRAN initiated function, triggered when UTRAN e.g. fails to keep the RAB established with the UE. + +### 5.2.2 RAB characteristics mapping to Uu bearers function + +The RAB characteristics mapping function is used to map the radio access bearers to the Uu bearers. The mapping is performed during the establishment of the RAB. UTRAN shall perform the mapping between the bearers. + +RAB mapping to Uu transmission bearers is a UTRAN function. + +### 5.2.3 RAB characteristics mapping to Iu transport bearers + +The RAB characteristics mapping function is used to map the radio access bearers to the Iu interface transport bearers. The mapping is performed during the establishment of the RAB. + +UTRAN shall perform this mapping between the bearers if AAL2 is used, since it is the UTRAN that establishes the AAL2 connections. + +In case of RAB towards the PS domain, UTRAN shall perform the mapping between the radio access bearers and the IP layer. + +RAB characteristics mapping to Iu transport bearers is a UTRAN function. + +### 5.2.4 RAB queuing, pre-emption and priority function + +The allocation/retention priority level of a RAB is determined by the CN based on e.g. subscription information, QoS information etc. Accordingly, the CN shall request RAB establishment or modification with an indication of the priority level and the pre-emption capability of that RAB and the queuing vulnerability. Queuing and resource pre-emption shall be performed by UTRAN accordingly. + +RAB queuing, pre-emption and allocation/retention priority handling is a UTRAN controlled function. + +RAB queuing, pre-emption and allocation/retention priority setting is a CN function. + +## 5.3 Radio Resource Management over Iu + +### 5.3.1 Radio resource admission control + +When UTRAN receives a request to establish or modify a radio access bearer from the CN, the current radio resource situation is analysed and the admission control either accepts or rejects the request. This is called "Radio resource admission control" and is handled by the UTRAN. If the request is queued, it is handled by the RAB queuing, pre-emption and priority function. + +### 5.3.2 Broadcast information management + +This function consists in the broadcast from network toward UE of some information in the coverage area of the whole network or different parts of the network. + +There are two kinds of Broadcast information management. UTRAN broadcast information, and Cell Broadcast information management. All UTRAN broadcast information management shall be handled locally within UTRAN. All Cell Broadcast information is controlled by CN and executed by UTRAN. + +## 5.4 Iu link Management functions + +### 5.4.1 Iu Signalling Link Management function + +The Iu signalling link management function provides a reliable transfer of the radio network signalling between UTRAN and CN. Both CN and UTRAN manage the function. + +This function is in particular responsible for Iu signalling connection establishment, which can be established either by the CN or the RNC and for Iu signalling connection release, which is controlled by CN possibly upon UTRAN request. + +### 5.4.2 ATM Virtual Connection Management function + +This function refers to handling of ATM Virtual Connections (VCs) between CN and UTRAN. + +This function shall be used to establish, maintain and release the ATM VCs. For permanent VCs, it is regarded to be an O&M function. + +This function also includes the selection of a Virtual Circuit to be used for a particular RAB. The selection of ATM VC upon an Iu radio access bearer service request, shall be done by UTRAN. The selected VC shall fulfil the requirements of the request. The VC may consist of several sublinks: such as SCCP connections, AAL2 connections or IP flows. + +### 5.4.3 AAL2 connection establish and release function + +This function is used to establish and release the AAL type 2 connections between CN and UTRAN upon an Iu radio access bearer service request. Both UTRAN and CN are taking part in the establishment of AAL2 connection. UTRAN shall initiate both establishment and release of AAL2 connections. In abnormal cases, the CN may also initiate release of AAL2 connections. The use of AAL2 for Iu transmission bearers depends on type of CN. + +### 5.4.4 AAL5 management function + +AAL5 connections between CN and UTRAN shall be pre-configured at system initialisation. Basic configuration is PVCs. For user data, SVC is possible. + +The AAL5 management is a function handled by both the CN and the UTRAN. + +### 5.4.5 GTP-U tunnels management function + +This function is used to establish and release GTP-U tunnels between CN and UTRAN upon a radio access bearer service request. This involves assigning a tunnel identifier for each direction and the creation of a context containing the tunnel information. The tunnel identifier for the downlink is allocated by the UTRAN, and the tunnel identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the context. The use of GTP-U for Iu transport bearers depends on type of CN. + +### 5.4.6 TCP Management Function + +This function is used to establish and release the TCP connections between CN and UTRAN over Iu-BC. + +The TCP management function exists in both UTRAN and CN. + +### 5.4.7 Buffer Management + +Congestion control shall be performed over the Iu user plane using buffer management and no flow control. + +This function includes buffers to store received packet data units that at reception can not be processed due to e.g. congestion. In UTRAN, there must be a buffer management function handling received packets from the peer CN node. + +The used mechanism is not in the scope of the present document and not relevant to be standardised. + +Buffer management is a UTRAN function. + +### 5.4.8 RTP Session Management Function + +This function is used to establish and release RTP sessions between CN and UTRAN upon a radio access bearer service request. This involves assigning a RTP session identifier for each direction and the creation of a context containing the RTP session information. The RTP session identifier for the downlink is allocated by the UTRAN, and the RTP session identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the RTP session context. The use of RTP for Iu transport bearers depends on type of CN. + +## 5.5 Iu U-plane (RNL) Management Functions + +### 5.5.1 Iu U-plane frame protocol mode selection function + +The Iu UP in the Radio Network Layer provides modes of operation that can be activated on RAB basis. For a given RAB, the Iu UP operates either in a Transparent or in Support mode. Iu U-plane frame protocol mode is selected by the CN. A set of appropriate U-plane version(s) is indicated within RANAP. The final U-plane version is selected during the Iu UP initiation procedure among the indicated version(s). + +This function is a CN function. + +### 5.5.2 Iu U-plane frame protocol initialisation + +Iu U-plane frame protocol is initialised by the UTRAN. In certain cases, as described in TS 23.153 [15], the Iu U-plane frame protocol may be initialised by the CN. + +## 5.6 Mobility Management Functions + +### 5.6.1 Location information update function + +Some functionality within the CN, needs information about the present location of an active UE, i.e. a UE with established signalling connection. The Location information update function is used to transfer this information from the UTRAN to the CN. It is the UTRAN responsibility to send this information initially at the signalling connection establishment for a UE and at any change of the UE location as long as the signalling connection exists. For this function, the location information shall be at Location and Routing Area level. + +### 5.6.2 Handover and Relocation functions + +#### 5.6.2.1 Inter RNC hard HO function, Iur not used or not available + +This functionality includes procedures for handover from one RNC to another RNC when Iur interface is not used or is not available, i.e. soft handover is not possible. The connection is switched in the CN, so both UTRAN and CN are involved. Both intra and inter CN entity cases are applicable. This functionality includes also the moving of the Serving RNS functionality from one RNC to another RNC. + +#### 5.6.2.2 Serving RNS Relocation function + +This functionality allows moving the Serving RNS functionality from one RNC to another RNC, e.g. closer to where the UE has moved during the communication. The Serving RNS Relocation procedure may be applied when active cell management functionality has created a suitable situation for it. Both UTRAN and CN are involved. + +#### 5.6.2.3 Inter system Handover (e.g. UMTS-GSM) function + +Inter system handover is performed when a mobile hands over between cells belonging to different systems such as GSM and UMTS. For intersystem handover between UMTS and GSM, the GSM procedures are used within the GSM network. Both UTRAN and CN are involved. + +NOTE: The GSM BSSMAP procedures are outside the scope of the present document. + +### 5.6.2A Inter System Change (e.g. UMTS-GSM) function + +Inter system change is performed when a GPRS attached mobile moves from cells belonging to different systems such as GSM and UMTS. For intersystem change between UMTS and GSM, the GPRS procedures are used within the GPRS network. Both UTRAN and CN are involved. + +### 5.6.3 Paging Triggering + +The Core Network shall, when considered necessary, trigger the Location/Routing/RNC Area paging in the UTRAN system. + +### 5.6.4 Shared Networks Access Control + +The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to the UTRAN and the neighbouring networks on a PLMN or an SNA basis. The Shared Networks Access Control function is further described in TS 25.401 [1]. + +### 5.6.5 GERAN System Information Retrieval + +In order to provide the UE with system information related to NACC towards a GERAN system - to be used as an optimisation - the GERAN System Information Retrieval function allows the source system to request GERAN (via CN) to provide this system information. The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in TS 25.401 [1] + +## 5.7 Security Functions + +### 5.7.1 Data Confidentiality + +#### 5.7.1.1 Radio interface ciphering function + +The radio interface shall be ciphered upon request of the Core Network. Both Signalling and user data may be subject to ciphering. The ciphering shall be done within UTRAN. + +#### 5.7.1.2 Ciphering key management function + +The ciphering key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm. + +### 5.7.2 Data integrity + +#### 5.7.2.1 Integrity checking + +The purpose of the integrity check is to make sure that the signalling continues between the same elements as by authentication. The integrity check shall be done within the UTRAN. + +#### 5.7.2.2 Integrity key management + +The integrity key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm. + +## 5.8 Service and Network Access Functions + +### 5.8.1 Core Network signalling data transfer function + +The NAS CN signalling data such as Call Control (CC), Session Management (SM), Mobility Management (MM), Short Message Services Point to Point and Supplementary Services (SS) shall be transparently conveyed between the CN and the UE. Over the Iu interface, the same Iu interface channel that is used for the UTRAN-CN signalling shall be used. + +### 5.8.2 Data Volume Reporting + +The data volume reporting function is used to report the volume of unacknowledged data to the CN. The function shall be in the UTRAN and is triggered from the CN. + +### 5.8.3 UE Tracing + +This feature allows tracing of various events related to the UE and its activities. This is an O&M functionality. + +### 5.8.4 Location reporting function + +The positioning function performs the determination of the geographical position and optionally the velocity for an UE. The location reporting function transfers the positioning information between the UTRAN and the CN according to CN commands. This function involves UTRAN and CN. + +### 5.8.5 MDT + +This feature enables the transfer of MDT measurements collected by the UE, as defined in TS 37.320 [30]. This is an O&M functionality. + +## 5.9 Co-ordination Functions + +### 5.9.1 Paging Co-ordination function + +The two CN domain architecture implies need for a page co-ordination, i.e. handling of page triggered by one CN node when UE has a signalling connection to the other CN node. The paging co-ordination is performed by UTRAN and/or optionally by CN. The Common ID is used for UTRAN paging co-ordination. The CN provides the UTRAN with the Common ID. + +The paging co-ordination is a UTRAN function. Optionally the paging co-ordination may be performed in the CN. + +### 5.9.2 NAS Node Selection Function + +The optional NAS Node Selection Function enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource. + +The method by which the RNC initially assigns CN resources is implementation dependent. + +The NNSF is described in detail in TS 23.236 [25]. + +### 5.9.3 Information Transfer Function + +The Information Transfer function allows configuration data to be passed from the CN to the RNC upon CN trigger. This function is operated in acknowledged mode. It should be used by the CN to maintain alignment between the data as configured in the CN and the configuration data provided to the UTRAN. This may be used e.g. to coordinate the SNA geographical definition (LA to SNA mapping) between CN and UTRAN in order to apply access control on an SNA basis. + +### 5.9.4 MOCN Rerouting Function + +Rerouting is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration for network sharing non-supporting UEs when they perform initial attach /registration. In this case RNC may not know towards which CN to route the initial UE request message and the latter may be rerouted to another CN via RNC. + +The MOCN Rerouting Function is described in detail in TS 23.251 [26]. + +### 5.9.5 SIPTO at Iu-PS Function + +If supported, SIPTO at Iu-PS Function provides the capability to offload certain PS RABs from the CN at RAB setup. The SIPTO at Iu-PS is implementation dependent and may be implemented in a separate entity outside of RNS, for further information see TS 23.060 [29]. + +### 5.9.6 SIPTO at the Local Network with Standalone GW + +SIPTO@LN provides access to a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's core network by using standalone GW (with S-GW and L-GW collocated) in the local network, as specified in TS 23.060 [29]. + +## 5.10 MBMS Functions + +### 5.10.1 MBMS RAB Management functions + +The MBMS RAB, Radio Access Bearer, is defined to be set-up between the CN and one or several UEs for MBMS. Depending on the MBMS service characteristics, different types of MBMS RABs will be used. It is the CN that controls towards the UTRAN the establishment, update or release of an MBMS RAB. The MBMS RAB is defined for the PS domain only. + +### 5.10.2 MBMS UE Linking Function + +This function provides the RNC with the list of MBMS services that a given UE, with existing dedicated Iu-PS signalling connection, has "joined" or has "left" TS 23.246 [27]. + +### 5.10.3 MBMS Registration Control Function + +This function allows the RNC to either register or deregister to the PS core network domain for a specific MBMS bearer service so that it is notified whenever a session of this service starts. + +It also allows the CN to inform the RNC that a given MBMS bearer service is no longer available. + +### 5.10.4 MBMS Enquiry Function + +This function allows the RNC to request to the SGSN the list of MBMS bearer services that a given UE has "joined" TS 23.246 [27] or the IP Multicast Address and APN defined in TS 23.246 [27] which correspond to a given MBMS bearer service. + +# --- 6 Iu Interface Protocol Structure + +## 6.1 General + +The Radio Network signalling over Iu consists of the Radio Access Network Application Part (RANAP). The RANAP protocol consists of mechanisms to handle all procedures between the CN and UTRAN. It is also capable of conveying messages transparently between the CN and the UE without interpretation or processing by the UTRAN. + +Over the Iu interface the RANAP protocol is, e.g. used for: + +- Facilitate a set of general UTRAN procedures from the Core Network such as paging -notification as defined by the notification SAP in TS 23.110 [3]. +- Separate each User Equipment (UE) on the protocol level for mobile specific signalling management as defined by the dedicated SAP in TS 23.110 [3]. +- Transfer of transparent non-access signalling as defined in the dedicated SAP in TS 23.110 [3]. +- Request of various types of UTRAN Radio Access Bearers through the dedicated SAP in TS 23.110 [3]. +- Perform the SRNS Relocation function. +- Perform the various MBMS procedures. +- Perform SIPTO at Iu-PS (optional). + +The Radio Access Bearers are provided by the Access Stratum. + +Over Iu-BC, a datagram mechanism is used, so there is no clear separation of control and user planes, and the SABP protocol is used for data transfer and signalling. + +## 6.2 Iu-CS + +Figure 6.1 shows the protocol structure for Iu-CS, following the structure described in TS 25.401 [1]. + +![Protocol structure diagram for Iu-CS interface towards CS Domain. It shows three vertical columns: Control Plane, Transport Network Control Plane, and User Plane. The Control Plane contains RANAP, SCCP, M3UA, MTP3b, SCTP, IP, AAL5, Data Link, and ATM. The Transport Network Control Plane contains Q.2630.2, Q.2150.1, MTP3b, SSCF-NNI, SSCOP, AAL5, and ATM. The User Plane contains Iu UP Protocol Layer, AAL2, RTP/RTCP(*), UDP/IP, ATM, and Data Link. All three planes share a common Physical Layer at the bottom.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +The diagram illustrates the protocol stack for the Iu-CS interface, organized into three main vertical sections: Control Plane, Transport Network Control Plane, and User Plane, all sitting atop a common Physical Layer. + +- Control Plane:** At the top is the Radio Network Layer containing RANAP. Below it, the Transport Network Layer contains SCCP, which is further divided into M3UA and MTP3b. Below SCCP are SCTP and SSCOP, followed by IP and AAL5. At the bottom of this column are Data Link and ATM. +- Transport Network Control Plane:** This central column contains Q.2630.2 at the top, followed by Q.2150.1, MTP3b, SSCF-NNI, SSCOP, and AAL5. It ends with ATM at the bottom. +- User Plane:** At the top is the Iu UP Protocol Layer. Below it, the Transport Network Layer contains AAL2, RTP/RTCP(\*), and UDP/IP. This is followed by ATM and Data Link at the bottom. + +Vertical arrows indicate the flow of data and signaling between the layers within each plane, and horizontal arrows show the interaction between the Control Plane and the User Plane through the Transport Network layers. + +Protocol structure diagram for Iu-CS interface towards CS Domain. It shows three vertical columns: Control Plane, Transport Network Control Plane, and User Plane. The Control Plane contains RANAP, SCCP, M3UA, MTP3b, SCTP, IP, AAL5, Data Link, and ATM. The Transport Network Control Plane contains Q.2630.2, Q.2150.1, MTP3b, SSCF-NNI, SSCOP, AAL5, and ATM. The User Plane contains Iu UP Protocol Layer, AAL2, RTP/RTCP(\*), UDP/IP, ATM, and Data Link. All three planes share a common Physical Layer at the bottom. + +\*) RTCP is optional. + +Figure 6.1: Iu -Interface Protocol Structure towards CS Domain + +## 6.3 Iu-BC + +Figure 6.2 shows the protocol structure for the Iu-BC. + +![Protocol stack diagram for Iu-BC interface showing layers from Radio Network Layer down to Physical Layer, with SA Broadcast Plane and Transport Network Layer components.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the protocol structure for the Iu-BC interface. It is divided into two main sections: the Radio Network Layer and the Transport Network Layer. + +- Radio Network Layer:** Contains the SA Broadcast Plane, which includes the SABP Protocol Layer. +- Transport Network Layer:** Contains the Transport User Plane and the Network Plane. The Transport User Plane consists of TCP, IP, and AAL5 layers. The Network Plane consists of TCP, IP, and ATM layers. The ATM layer is connected to the Data Link layer, which is connected to the Physical Layer. + +Vertical arrows indicate the flow of data between the layers: from the SABP Protocol Layer down through the Transport User Plane, and from the Network Plane down through the ATM, Data Link, and Physical layers. + +Protocol stack diagram for Iu-BC interface showing layers from Radio Network Layer down to Physical Layer, with SA Broadcast Plane and Transport Network Layer components. + +**Figure 6.2: Iu Interface Protocol Structure towards Broadcast Domain** + +## 6.4 Iu-PS + +Figure 6.3 shows the protocol structure for Iu-PS, following the structure described in TS 25.401 [1]. + +![Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram shows the protocol stack for the Iu-PS interface. At the top is the Radio Network Layer, which contains the Control Plane (RANAP) and the User Plane (Iu UP Protocol Layer). Below this is the Transport Network Layer, which is divided into three vertical sections: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The left section contains SCCP, MTP3-B, M3UA, SCTP, SSCF-NNI, SSCP, AAL5, ATM, and Physical Layer. The right section contains GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. Arrows indicate the flow of data and signaling between the layers.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram shows the protocol stack for the Iu-PS interface. At the top is the Radio Network Layer, which contains the Control Plane (RANAP) and the User Plane (Iu UP Protocol Layer). Below this is the Transport Network Layer, which is divided into three vertical sections: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The left section contains SCCP, MTP3-B, M3UA, SCTP, SSCF-NNI, SSCP, AAL5, ATM, and Physical Layer. The right section contains GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. Arrows indicate the flow of data and signaling between the layers. + +Figure 6.3: Iu Interface Protocol Structure towards PS Domain + +# 7 Other Iu Interface Specifications + +## 7.1 UTRAN Iu Interface: Layer 1 (3GPP TS 25.411) + +TS 25.411 [4] specifies the range of physical layer technologies that may be used to support the Iu interface. + +## 7.2 UTRAN Iu Interface: Signalling Transport (3GPP TS 25.412) + +TS 25.412 [5] specifies the signalling bearers for the RANAP and transport network control plane protocols for both Iu-PS and Iu-CS. + +## 7.3 UTRAN Iu Interface: RANAP Specification (3GPP TS 25.413) + +TS 25.413 [6] specifies the RANAP protocol for radio network control plane signalling over the Iu interface. + +## 7.4 UTRAN Iu Interface: Data Transport and Transport Signalling (3GPP TS 25.414) + +TS 25.414 [7] specifies the transport bearers for the user plane of the Iu interface. It also specifies the protocol used to control these transport bearers. + +## 7.5 UTRAN Iu Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415) + +TS 25.415 [8] specifies the user plane frame handling protocol for the Iu interface. + +## 7.6 UTRAN Iu Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) + +TS 25.419 [14] specifies the communication requirements over the Iu interface towards the BC domain. + +## 7.7 Summary + +The present document, 3GPP TS 25.410, specifies the general aspects and principles of the Iu interface as a whole. + +The relationship between the other technical specifications that define the UTRAN Iu interface is shown in figure 7.1. + +![Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the protocol stack for the Iu interface, organized into three vertical planes: Control Plane, User Plane, and SA Broadcast Plane. At the top is the Radio Network Layer. Below it is the Transport Network Layer, which is subdivided into Transport User Plane and Transport Network Control Plane. The Control Plane (TS 25.413) and SA Broadcast Plane (TS 25.419) both connect to the Transport Network Control Plane. The User Plane (TS 25.415) connects to the Transport User Plane. The Transport User Plane and Transport Network Control Plane both connect to a central area representing the core network protocols (TS 25.412, 25.414, and 25.411).](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the protocol stack for the Iu interface, organized into three vertical planes: Control Plane, User Plane, and SA Broadcast Plane. At the top is the Radio Network Layer. Below it is the Transport Network Layer, which is subdivided into Transport User Plane and Transport Network Control Plane. The Control Plane (TS 25.413) and SA Broadcast Plane (TS 25.419) both connect to the Transport Network Control Plane. The User Plane (TS 25.415) connects to the Transport User Plane. The Transport User Plane and Transport Network Control Plane both connect to a central area representing the core network protocols (TS 25.412, 25.414, and 25.411). + +**Figure 7.1: Summary of Iu Interface Specification Structure** + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|----------------------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| RP-43 | RP-090078 | 0068 | 1 | RANAP: Enhanced Relocation Complete Request in SCCP: Connection Request | 8.1.0 | +| 12/2009 | - | - | - | Created version 9.0.0 based on v. 8.1.0 | 9.0.0 | +| 12/2010 | | | | Created version 10.0.0 based on v. 9.0.0 | 10.0.0 | +| RP-50 | RP-101389 | 0070 | - | Introduction of the SIPTO at Iu-PS Function | 10.0.0 | +| SP-49 | SP-100629 | | - | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.0 | +| RP-51 | RP-110230 | 0074 | 1 | Support for MDT | 10.1.0 | +| RP-52 | RP-110684 | 0075 | - | Correction of references | 10.2.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| RP-62 | RP-131909 | 0076 | 6 | Introduction of Standalone GW for SIPTO@LN | 12.0.0 | +| RP-70 | RP-152088 | 0077 | 1 | Introduction of improvements to CS/PS coordination in UTRAN Shared Network | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RAN#75 | RP-170545 | 0079 | 1 | B | Introduction of QMC for streaming services | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25411/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-16/25_series/25411/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b2223bac3e6c1670788752a14e604f11362ac54 --- /dev/null +++ b/marked/Rel-16/25_series/25411/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fb69ac588ef4c41975b1315d4dad913ed6017b477e00cacc1904bb83d22edc6 +size 21395 diff --git a/marked/Rel-16/25_series/25411/raw.md b/marked/Rel-16/25_series/25411/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a209f5bd112522761379718b6418a1817a151e87 --- /dev/null +++ b/marked/Rel-16/25_series/25411/raw.md @@ -0,0 +1,219 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Abbreviations..... 6 +- 4 Iu Layer 1 ..... 6 + - 4.1 Introduction ..... 6 + - 4.2 Layer 1 Description..... 6 + - 4.2.1 Layer 1 Synchronised..... 6 + - 4.2.2 [IP – Layer 1 Unsynchronised]..... 8 + - 4.3 Requirements from higher layer..... 8 + - 4.4 Services Provided by Layer 1..... 8 + - 4.4.1 ATM Transport..... 8 + - 4.5 Interface to Management Plane..... 8 +- Annex A (informative): Change History..... 10 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the Iu interface. + +The specification of transmission delay requirements and O&M requirements are not in the scope of the present document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] ITU-T Recommendation I.432.2 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, 155 520 kbit/s and 622 080 kbit/s operation". +- [2] Void. +- [3] ITU-T Recommendation G.703 (1998-10): "Physical/electrical characteristics of hierarchical digital interfaces". +- [4] ITU-T Recommendation G.704 (1998-10): "Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels". +- [5] ITU-T Recommendation G.957 (1995-07): "Optical interfaces for equipments and systems relating to the synchronous digital hierarchy". +- [6] ITU-T Recommendation I.432.1 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, General characteristics". +- [7] ITU-T Recommendation G.823 (2000-03): "The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy". +- [8] ITU-T Recommendation G.824 (2000-03): "The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy". +- [9] ITU-T Recommendation G.825 (2001-08): "The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)". +- [10] ITU-T Recommendation G.826 (1996-08): "Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate". +- [11] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [12] ATM Forum AF-PHY-0016.000 (1994-09): "DS1 Physical Layer Specification". +- [13] ATM Forum AF-PHY-0064.000 (1996-09): "E1 Physical Layer Interface Specification". +- [14] ATM Forum AF-PHY-0086.001 (1999-02): "Inverse Multiplexing for ATM (IMA) Specification Version 1.1". +- [15] ITU-T Recommendation G.751 (1988-11): "Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 kbit/s and using positive justification". + +- [16] ITU-T Recommendation G.811 (1997-02): "Timing Characteristics of Primary Reference Clocks". +- [17] ITU-T Recommendation G.804 (1998-02): "ATM cell mapping into plesiochronous digital hierarchy (PDH)". +- [18] Standard ECMA-226: "Private Integrated Services Network (PISN) - Mapping Functions for the Employment of Dedicated Circuit Mode Connections as Inter-PTNX Connections (MAPPING-CM-STATIC)". +- [19] ITU-T Recommendation I.431 (1988-11): "Primary rate user-network interface - Layer 1 specification". +- + +# 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------| +| ATM | Asynchronous Transfer Mode | +| HEC | Header Error Control | +| IMA | Inverse Multiplexing on ATM | +| IP | Internet Protocol | +| PDH | Plesiochronous Digital Hierarchy | +| PMD | Physical Media Dependent | +| PHY-SAP | Physical Service Access Point | +| SDH | Synchronous Digital Hierarchy | +| SDU | Service Data Unit | +| SONET | Synchronous Optical Networking | + +--- + +# 4 Iu Layer 1 + +## 4.1 Introduction + +The main functions of Layer 1 are summarised in the following: + +- Interface to physical medium; +- [ATM-Cell delineation]; +- Line clock extraction capability; +- Layer 1 alarms extraction and generation; +- In-sequence delivery; +- Transmission quality control. + +## 4.2 Layer 1 Description + +### 4.2.1 Layer 1 Synchronised + +When the Layer 1 Synchronised option is used (i.e. PDH/SDH/SONET links), the following requirements shall be met: + +Layer 1 reference configuration shall be according to ITU-T Rec. I.432.1 [6]. + +The physical layer is divided into: + +- Physical Media Dependent (PMD) sublayer; +- Transmission Convergence (TC) sublayer defined according to ITU-T Rec. I.432.1 [6]. + +The PMD shall comply with at least one of the following standards: + +- ETSI STM-4 (622 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-4.1 interface according to ITU-T Rec. G.957 [5]. +- SONET STS-12c (622 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode. +- SONET STS-3c (155 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode. +- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with electrical interface (CMI) to ITU-T Rec. G.703 [3]. +- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-1.1 interface according to ITU-T Rec. G.957 [5]. +- ITU STS-1 (51 Mb/s) interface according to ANSI, T1.105-1995 with electrical interface. +- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with electrical interface. +- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with optical S-1.1 interface according to ITU-T Rec. G.957 [5]. +- J2, 6.3 Mb/s interface according to Japanese standard JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). + +NOTE: J2 requires that the ATM cells be mapped into the physical layer according to HEC based mapping in ITU-R Rec. G.804 [17]. + +- E2, 8Mb/s according to ETSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). +- E3, 34 Mb/s interface according to ETSI/ITU G.751 (ITU-T Rec. G.751 [15]) (75 Ohm). +- T3, 45 Mb/s interface according to ANSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). +- E1, 2Mb/s interface balanced 120 Ohm symmetrical according to ETS 300 420 (Standard ECMA-226 [18]), ITU-T Rec. G.704 [4] and TBR 013 (ITU-T Rec. G.703 [3]), and AF-PHY-0064.000 [13]. +- E1, 2Mb/s according to ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (75 Ohm), and AF-PHY-0064.000 [13]. +- J1, 1.5 Mb/s interface according to JT-I.431-a (ITU-T Rec. I.431 [19]) (100 Ohm). +- J1, 1.5 Mb/s interface according to JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (110 Ohm). +- T1, 1.5 Mb/s interface according to AF-PHY-0016.000 [12] and ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (100 Ohm). + +Services provided to the upper layer shall be independent from the used underlying technology. + +The support of intervening transport networks - like PDH or SDH terrestrial links, Point-to-point or Point-to-Multipoint radio links - shall not be prevented. + +When using E1, T1, or J1, it shall be possible to use inverse multiplexing of ATM (IMA) (ATM Forum AF-PHY-0086.001 [14]) within suitable subsets of the physical ports on the respective Exchange Termination (ET). + +The jitter and wander performance requirements on the interface shall be in accordance with network limits for output wander at traffic interfaces of either Reference ITU-T Rec. G.823 [7], ITU-T Rec. G.824 [8] or network limits for the maximum output jitter and wander at any hierarchical interface of Reference ITU-T Rec. G.825 [9], whichever is applicable. + +The synchronisation reference extracted from the Iu may be used as UTRAN synchronisation reference. A general recommendation is to supply a traceable synchronisation reference according to reference ITU-T Rec. G.811 [16]. + +Transmission quality control shall be provided according to ITU-T Rec. G.826 [10]. + +### 4.2.2 [IP – Layer 1 Unsynchronised] + +When Layer 1 unsynchronised option is used, the following requirements shall be met: + +The support of any suitable physical layer - like Ethernet L1 or other suitable point-to-point or point-to-multipoint techniques - shall not be prevented. + +## 4.3 Requirements from higher layer + +No specific requirements beyond the ones listed in the introduction have been identified. + +## 4.4 Services Provided by Layer 1 + +### 4.4.1 ATM Transport + +The physical layer provides services to the upper layer via the Physical Service Access Point (PHY-SAP) according to ITU-T I.361 [11], as described in the following figure: + +![Diagram showing the Service Access Point (PHY-SAP) between the ATM Layer and the Physical Layer.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +The diagram illustrates the interface between the ATM Layer and the Physical Layer. At the top is a rectangular box labeled **ATM Layer**. At the bottom is a rectangular box labeled **Physical Layer**. A vertical line connects the two boxes, passing through a central oval shape. To the right of this oval, the text **PHY-SAP** is displayed, indicating the point of service access. + +Diagram showing the Service Access Point (PHY-SAP) between the ATM Layer and the Physical Layer. + +**Figure 1: SAP between Physical Layer and ATM Layer** + +According to ITU-T Rec. I.361 [11], subclause 3.2, the following primitives are provided over PHY-SAP: + +- PHY-DATA request (PHY-SDU); +- PHY-DATA indication (PHY-SDU). + +The parameter PHY-SDU contains one ATM cell as defined in ITU-T I.361 [11] received or to be transferred over the physical medium. + +## 4.5 Interface to Management Plane + +The description of the interface towards Management Plane is out of scope of this document, anyhow at least the following O&M functions should be foreseen: + +- Performance Monitoring Functions; +- Alarm Status Reporting Functions; +- Synchronisation Source Management. + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| 03/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 06/2011 | RP-110684 | 0019 | | Correction of references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25419/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-16/25_series/25419/098802c99831a6a7d445310d5e874e16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80a54250af6ff036f362185d0cce69a70fe97dd1 --- /dev/null +++ b/marked/Rel-16/25_series/25419/098802c99831a6a7d445310d5e874e16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a346556a05bfb4cda1d1f8db132ee4d29339a85beb325cded03ef3db17b9411d +size 9567 diff --git a/marked/Rel-16/25_series/25419/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-16/25_series/25419/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a8c0779c68fd7080d47d1c58683a6029a8b7514 --- /dev/null +++ b/marked/Rel-16/25_series/25419/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0795672325dc9c0d415f637e1b7c122ba97c5fc77994bc8b7fa3e5496180fe00 +size 15057 diff --git a/marked/Rel-16/25_series/25419/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/marked/Rel-16/25_series/25419/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b2f8a9f8fda1f55e651c9cf2fbc18961d5d5255 --- /dev/null +++ b/marked/Rel-16/25_series/25419/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aed4a6cfdb4643e87fb723770c7824e27875e6ca98dd628278d7c4190f99fb0e +size 73728 diff --git a/marked/Rel-16/25_series/25419/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-16/25_series/25419/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b370edc08705cc9d565587b05daf798e1c0c89fd --- /dev/null +++ b/marked/Rel-16/25_series/25419/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc4219ae06517b6c29f4e246fe926a2a8e3685a0160d339ac6228fddb5a47da +size 12221 diff --git a/marked/Rel-16/25_series/25419/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/25_series/25419/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6b4dc574175a40525c175053c3ec623ac492dc7 --- /dev/null +++ b/marked/Rel-16/25_series/25419/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9005a89cae9fb5eec9e47aa84a145d859094bb6e047416641d3cff166ebbe43b +size 19243 diff --git a/marked/Rel-16/25_series/25419/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-16/25_series/25419/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80afe3770e54bbfd113c2423915269c0fd0d1a43 --- /dev/null +++ b/marked/Rel-16/25_series/25419/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abd2b8d296096a6b5c2475df37f336c2645fec09b990e76425caca7f35a279a5 +size 9376 diff --git a/marked/Rel-16/25_series/25419/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Rel-16/25_series/25419/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aec0f40cfbf4e5d448f4cc5963ea81d1a1692ce --- /dev/null +++ b/marked/Rel-16/25_series/25419/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b35e76fe4cd04bafcadfeeb9c43c588e602802d4695eccfc4ae4abcc3caeeaf2 +size 15921 diff --git a/marked/Rel-16/25_series/25419/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/25_series/25419/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..420fb9aa82d5607912a1f2823097605835e423ef --- /dev/null +++ b/marked/Rel-16/25_series/25419/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd2197af23694994464ebb10b847fa88f08ae18a31d5572d9e6515d8d62f0d5a +size 15043 diff --git a/marked/Rel-16/25_series/25419/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/25_series/25419/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4820105588b2d911ea47a406e5dd22944dc121d0 --- /dev/null +++ b/marked/Rel-16/25_series/25419/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37a98c8fbcfcdd0f2514b8ecd1ca077fd00b48435f01c97400ad9b76749cbfd7 +size 15060 diff --git a/marked/Rel-16/25_series/25419/87b70d2e8951032d28b4412d82cf1413_img.jpg b/marked/Rel-16/25_series/25419/87b70d2e8951032d28b4412d82cf1413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a709ed0299b2bb4b621d3d0e9a3cf988f37c0e99 --- /dev/null +++ b/marked/Rel-16/25_series/25419/87b70d2e8951032d28b4412d82cf1413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fa9e13496da0ec37637a72d0184e6c71043baab75881813895c66e4c24f0eb3 +size 21228 diff --git a/marked/Rel-16/25_series/25419/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/Rel-16/25_series/25419/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea9d66ee0ed4124875bbc501c482d63ae1dd16c7 --- /dev/null +++ b/marked/Rel-16/25_series/25419/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbd046df9bc9bfdcb454fe0bb2738bc281fb8cb6a718faa7cc2d0cb5d02fa168 +size 75930 diff --git a/marked/Rel-16/25_series/25419/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/25_series/25419/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3963a071059722b76d56d6cf78dd902546adb261 --- /dev/null +++ b/marked/Rel-16/25_series/25419/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d4b48edfe50826df58e44808b860cc7f1fd7806bc7564805db8a70f40f88f98 +size 86079 diff --git a/marked/Rel-16/25_series/25419/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/Rel-16/25_series/25419/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69a005a8b164ab4604b8cbcd4039fd4dba5db3fa --- /dev/null +++ b/marked/Rel-16/25_series/25419/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae7df507a8d62c9d6a2eb1ff79af583b046153ca3421ac14c3ba70ce34fb5eb0 +size 75034 diff --git a/marked/Rel-16/25_series/25419/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-16/25_series/25419/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdc7269def489b5dd8590d583b9a8513aa0883a6 --- /dev/null +++ b/marked/Rel-16/25_series/25419/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c259ba595a78969e4633899143b915a22aa9014fa4f3f456684ba19bd1ceb84 +size 12058 diff --git a/marked/Rel-16/25_series/25419/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-16/25_series/25419/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eed0f820838df44b50ebf4c911485ea0d2e46c66 --- /dev/null +++ b/marked/Rel-16/25_series/25419/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1a3c7b011e45ac4bd8672450fc8da4d6376d75a61bce856cc78a8aed22843aa +size 75071 diff --git a/marked/Rel-16/25_series/25419/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/marked/Rel-16/25_series/25419/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f368472eea25df9ca6a07d6d989025bb1e48736 --- /dev/null +++ b/marked/Rel-16/25_series/25419/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ae756608bd0a4fb8b9449871f614a01abaa4e22c5ed2ed7ba331916b0a1fe06 +size 75016 diff --git a/marked/Rel-16/25_series/25419/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/25_series/25419/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45e22129cd241192a9a124625844573763259a98 --- /dev/null +++ b/marked/Rel-16/25_series/25419/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1fbce9b7a282c56aafdd75f4b06c4b440de492642e517b54a9512d53454c385 +size 15840 diff --git a/marked/Rel-16/25_series/25419/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/25_series/25419/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf32d80f3c5f7cfa2388e56cc41eb69c29b9496c --- /dev/null +++ b/marked/Rel-16/25_series/25419/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad62976fa3616defd35351d1f0665ad721226db3f9d11bf40fc8a681e1df663 +size 15286 diff --git a/marked/Rel-16/25_series/25419/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-16/25_series/25419/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..778f260b4308841b14de9fa1b4ff661e184e2965 --- /dev/null +++ b/marked/Rel-16/25_series/25419/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a801836834d132022dd06d6629696d755ce6a313acf3e189119e877ed615b1d8 +size 19635 diff --git a/marked/Rel-16/25_series/25419/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/25_series/25419/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d9978676156bc4caff46a3ff8bb2e9c76f26277 --- /dev/null +++ b/marked/Rel-16/25_series/25419/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6baa3e0a351c4cf9e29c01390549b2ca22fe5e04a0449278e9c0b8a113cd0d27 +size 12136 diff --git a/marked/Rel-16/25_series/25419/raw.md b/marked/Rel-16/25_series/25419/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..510212a41d6840362c0a4718dec3c1059ad669ca --- /dev/null +++ b/marked/Rel-16/25_series/25419/raw.md @@ -0,0 +1,3391 @@ + + + + + + +# --- Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 4.1 Procedure Specification Principles..... | 8 | +| 4.2 Forwards and Backwards Compatibility..... | 9 | +| 4.3 Specification Notations ..... | 9 | +| 5 Services provided by SABP..... | 9 | +| 6 Services expected from the Transport layer..... | 9 | +| 7 Functions of SABP..... | 10 | +| 8 SABP Procedures..... | 10 | +| 8.1 Elementary Procedures..... | 10 | +| 8.2 Write-Replace..... | 10 | +| 8.2.1 General ..... | 10 | +| 8.2.2 Successful Operation..... | 11 | +| 8.2.3 Unsuccessful Operation..... | 12 | +| 8.2.4 Abnormal Conditions ..... | 13 | +| 8.3 Kill..... | 13 | +| 8.3.1 General ..... | 13 | +| 8.3.2 Successful Operation..... | 13 | +| 8.3.3 Unsuccessful Operation..... | 14 | +| 8.3.4 Abnormal Conditions ..... | 14 | +| 8.4 Load Status Enquiry ..... | 14 | +| 8.4.1 General ..... | 14 | +| 8.4.2 Successful Operation..... | 14 | +| 8.4.3 Unsuccessful Operation..... | 15 | +| 8.4.4 Abnormal Conditions ..... | 15 | +| 8.5 Message Status Query ..... | 15 | +| 8.5.1 General ..... | 15 | +| 8.5.2 Successful Operation..... | 16 | +| 8.5.3 Unsuccessful Operation..... | 16 | +| 8.5.4 Abnormal Conditions ..... | 17 | +| 8.6 Reset..... | 17 | +| 8.6.1 General ..... | 17 | +| 8.6.2 Successful Operation..... | 17 | +| 8.6.3 Unsuccessful Operation..... | 17 | +| 8.6.4 Abnormal Conditions ..... | 18 | +| 8.7 Restart Indication ..... | 18 | +| 8.7.1 General ..... | 18 | +| 8.7.2 Successful Operation..... | 18 | +| 8.7.3 Abnormal Conditions ..... | 18 | +| 8.8 Failure Indication ..... | 18 | +| 8.8.1 General ..... | 18 | +| 8.8.2 Successful Operation..... | 19 | +| 8.8.3 Abnormal Conditions ..... | 19 | +| 8.9 Error Indication ..... | 19 | +| 8.9.1 General ..... | 19 | +| 8.9.2 Successful Operation..... | 19 | +| 8.9.3 Abnormal Conditions ..... | 20 | + +| | | | +|---------|--------------------------------------------------------------------|----| +| 9 | Elements for SABP Communication ..... | 20 | +| 9.1 | Message Functional Definiton and Content..... | 20 | +| 9.1.1 | General ..... | 20 | +| 9.1.2 | Message Contents..... | 20 | +| 9.1.2.1 | Presence ..... | 20 | +| 9.1.2.2 | Criticality ..... | 20 | +| 9.1.2.3 | Range ..... | 20 | +| 9.1.2.4 | Assigned Criticality ..... | 21 | +| 9.1.3 | WRITE-REPLACE ..... | 21 | +| 9.1.4 | WRITE-REPLACE COMPLETE ..... | 21 | +| 9.1.5 | WRITE-REPLACE FAILURE ..... | 21 | +| 9.1.6 | KILL ..... | 22 | +| 9.1.7 | KILL COMPLETE ..... | 22 | +| 9.1.8 | KILL FAILURE ..... | 22 | +| 9.1.9 | LOAD QUERY ..... | 22 | +| 9.1.10 | LOAD QUERY COMPLETE ..... | 23 | +| 9.1.11 | LOAD QUERY FAILURE ..... | 23 | +| 9.1.12 | MESSAGE STATUS QUERY..... | 23 | +| 9.1.13 | MESSAGE STATUS QUERY COMPLETE ..... | 23 | +| 9.1.14 | MESSAGE STATUS QUERY FAILURE..... | 24 | +| 9.1.15 | RESET ..... | 24 | +| 9.1.16 | RESET COMPLETE..... | 24 | +| 9.1.17 | RESET FAILURE ..... | 24 | +| 9.1.18 | RESTART ..... | 25 | +| 9.1.19 | FAILURE ..... | 25 | +| 9.1.20 | ERROR INDICATION ..... | 25 | +| 9.2 | Information Element Definitions ..... | 25 | +| 9.2.0 | General ..... | 25 | +| 9.2.1 | MessageType..... | 26 | +| 9.2.2 | Broadcast Message Content ..... | 26 | +| 9.2.3 | Serial Number..... | 26 | +| 9.2.4 | Old Serial Number..... | 26 | +| 9.2.5 | New Serial Number ..... | 27 | +| 9.2.6 | Service Areas List..... | 27 | +| 9.2.7 | Category ..... | 27 | +| 9.2.8 | Repetition Period..... | 27 | +| 9.2.9 | Number of Broadcasts Requested ..... | 27 | +| 9.2.10 | Number of Broadcasts Completed List ..... | 28 | +| 9.2.11 | Service Area Identifier..... | 29 | +| 9.2.12 | Failure List..... | 29 | +| 9.2.13 | Radio Resource Loading List ..... | 29 | +| 9.2.14 | Cause ..... | 30 | +| 9.2.15 | Data Coding Scheme ..... | 32 | +| 9.2.16 | Recovery Indication..... | 32 | +| 9.2.17 | Criticality Diagnostics ..... | 32 | +| 9.2.18 | Available Bandwidth..... | 34 | +| 9.2.19 | Message Identifier ..... | 34 | +| 9.2.20 | Message Structure ..... | 34 | +| 9.2.21 | Paging ETWS Indicator..... | 35 | +| 9.2.22 | Warning Type..... | 35 | +| 9.2.23 | Warning Security Information..... | 36 | +| 9.2.24 | Broadcast Message Content Validity Indicator ..... | 36 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1) ..... | 36 | +| 9.3.0 | General ..... | 36 | +| 9.3.1 | Usage of protocol extension mechanism for non-standard use ..... | 36 | +| 9.3.2 | Elementary Procedure Definitions..... | 38 | +| 9.3.3 | PDU Definitions ..... | 41 | +| 9.3.4 | Information Element Definitions..... | 51 | +| 9.3.5 | Common Definitions ..... | 56 | +| 9.3.6 | Constant Definitions ..... | 57 | +| 9.3.7 | Container Definitions ..... | 58 | +| 9.4 | Message Transfer Syntax ..... | 61 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------|-----------| +| 10 | Handling of Unknown, Unforeseen or Erroneous Protocol Data ..... | 61 | +| 10.1 | General ..... | 61 | +| 10.2 | Transfer Syntax Error..... | 61 | +| 10.3 | Abstract Syntax Error..... | 61 | +| 10.3.1 | General ..... | 61 | +| 10.3.2 | Criticality Information..... | 62 | +| 10.3.3 | Presence Information..... | 62 | +| 10.3.4 | Not comprehended IE/IE group..... | 63 | +| 10.3.4.1 | Procedure Code..... | 63 | +| 10.3.4.1A | Type of Message..... | 63 | +| 10.3.4.2 | IEs other than the Procedure Code and Type of Message ..... | 63 | +| 10.3.5 | Missing IE or IE group ..... | 64 | +| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 65 | +| 10.4 | Logical Error ..... | 66 | +| 10.5 | Exceptions ..... | 66 | +| Annex A (informative): | Guidelines for Usage of the Criticality Diagnostics IE ..... | 67 | +| A.1 | EXAMPLE MESSAGE Layout ..... | 67 | +| A.2 | Example on a Received EXAMPLE MESSAGE ..... | 68 | +| A.3 | Content of Criticality Diagnostics..... | 69 | +| A.3.1 | Example 1 ..... | 69 | +| A.3.2 | Example 2 ..... | 70 | +| A.3.3 | Example 3 ..... | 71 | +| A.3.4 | Example 4 ..... | 72 | +| A.3.5 | Example 5 ..... | 73 | +| A.4 | ASN.1 of EXAMPLE MESSAGE..... | 74 | +| Annex B (informative): | Change history..... | 77 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the *Service Area Broadcast Protocol (SABP)* between the Cell Broadcast Centre (CBC) and the Radio Network Controller (RNC). It fulfils the CBC - RNC communication requirements specified in TS 23.041 [5] and is defined over the Iu-BC – reference point. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] Void +- [3] Void +- [4] 3GPP TR 25.931: "UTRAN Functions: Examples on Signalling Procedures". +- [5] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [6] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling". +- [7] ITU-T Recommendation X.680 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [8] ITU-T Recommendation X.681 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [9] ITU-T Recommendation X.691 (2002-07): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [10] 3GPP TR 25.921 (Version 7.0.0): "Guidelines and Principles for Protocol Description and Error Handling". +- [11] 3GPP TS 25.324: "Broadcast/Multicast Control BMC". +- [12] 3GPP TS 23.003: "Numbering, addressing and identification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Elementary Procedure:** SABP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CN (CBC) and the RNC. These EPs are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several SABP EPs together with each other and EPs from other interfaces can be found in reference TR 25.931 [4]. + +An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure). +- **Class 2:** Elementary Procedures without response. + +For Class 1 EPs, the types of responses can be as follows: + +### Successful + +- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. + +### Unsuccessful + +- A signalling message explicitly indicates that the EP failed. +- On time supervision expiry (i.e. absence of expected response). + +Class 2 EPs are considered always successful. + +**Message Reference:** This is defined as consisting of the following parameters: Message Identifier, Serial Number, and SAI (Service Area Identifier). + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|---------------------------------| +| CBC | Cell Broadcast Centre | +| CBS | Cell Broadcast Service | +| CN | Core Network | +| EP | Elementary Procedure | +| FP | Frame Protocol | +| PDU | Protocol Data Unit | +| RNC | Radio Network Controller | +| SA | Service Area | +| SABP | Service Area Broadcast Protocol | + +# --- 4 General + +The protocol described in the present document is the protocol between CN (CBC) and RNC needed for the CBC Application. The CBC Application is described in TS 23.041 [5]. + +## 4.1 Procedure Specification Principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and completely. The CN functional behaviour is left unspecified. + +The following specification principles have been applied for the procedure text in clause 8: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + +### 2) Functionality which "shall, if supported" be executed: + +- The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. + +## 4.2 Forwards and Backwards Compatibility + +The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Write-Replace procedure. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. WRITE-REPLACE message. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Old Serial Number IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 Services provided by SABP + +- During normal operation the CN (CBC) initiates all message transfer and query operations. The RNC responds to the message transfer and query operations initiated by the CBC. +- The RNC will open the connection only in case an error (Failure Indication Procedure) or recovery (Restart Indication Procedure) is to be reported. +- The initiator of a connection is responsible for the termination of the connection. + +# --- 6 Services expected from the Transport layer + +Following service is expected from the transport layer: + +- in sequence delivery of Signalling data TS 25.414 [6]. + +# 7 Functions of SABP + +The SABP has the following functions: + +- Message Handling. This function is responsible for the broadcast of new messages, amend existing broadcasted messages and to stop the broadcasting of specific messages. +- Load Handling. This function is responsible for determining the loading of the broadcast channels at any particular point in time. +- Reset. This function permits the CBC to end broadcasting in one or more Service Areas. +- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined. + +These functions are implemented by one or several SABP elementary procedures described in the following clauses. + +# 8 SABP Procedures + +## 8.1 Elementary Procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 Procedures. + +**Table 1: Class 1** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|----------------------|--------------------|------------------------|-----------------------| +| | | Response message | Response message | +| Write-Replace | WRITE-REPLACE | WRITE-REPLACE COMPLETE | WRITE-REPLACE FAILURE | +| Kill | KILL | KILL COMPLETE | KILL FAILURE | +| Load Status Enquiry | LOAD QUERY | LOAD QUERY COMPLETE | LOAD QUERY FAILURE | +| Message Status Query | MESSAGE QUERY | MESSAGE QUERY COMPLETE | MESSAGE QUERY FAILURE | +| Reset | RESET | RESET COMPLETE | RESET FAILURE | + +**Table 2: Class 2** + +| Elementary Procedure | Message | +|----------------------|------------------| +| Restart Indication | RESTART | +| Failure Indication | FAILURE | +| Error Indication | ERROR INDICATION | + +## 8.2 Write-Replace + +### 8.2.1 General + +The purpose of this Write-Replace procedure is to broadcast new information or replace a message already broadcast to a chosen Service Area(s). + +### 8.2.2 Successful Operation + +![Sequence diagram showing the Write-Replace Procedure: Successful Operation. The diagram involves two entities: RNC (Radio Network Controller) and CN (Core Network). The CN sends a WRITE-REPLACE message to the RNC. The RNC responds with a WRITE-REPLACE COMPLETE message to the CN.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant CN + participant RNC + Note left of CN: CN initiates procedure + CN->>RNC: WRITE-REPLACE + Note right of RNC: RNC broadcasts message + RNC->>CN: WRITE-REPLACE COMPLETE + +``` + +Sequence diagram showing the Write-Replace Procedure: Successful Operation. The diagram involves two entities: RNC (Radio Network Controller) and CN (Core Network). The CN sends a WRITE-REPLACE message to the RNC. The RNC responds with a WRITE-REPLACE COMPLETE message to the CN. + +**Figure 1: Write-Replace Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a WRITE-REPLACE message to the RNC. + +The presence of a *New Serial Number* IE will indicate that this is a new broadcast. The presence of both the *Old Serial Number* IE and a *New Serial Number* IE will indicate that this message is a replacement of an existing broadcast. + +The RNC will initiate broadcasting of a new message or replace a message already broadcast as requested to the service areas as indicated in the *Service Areas List* IE. + +The RNC shall uniquely identify the CBS message by the *Message Identifier* IE together with the twelve leftmost bits of the serial number in the *New Serial Number* IE and the *Service Area Identifier* IE. + +The RNC shall perform the broadcast according to the value of the *Category* IE as follows: + +- The *Category* IE, if given in the WRITE-REPLACE message, shall be treated as follows: + 1. If the value of *Category* IE is indicated as "High Priority", the RNC shall perform the broadcast immediately; + 2. If the value of *Category* IE is indicated as "Background", the RNC shall perform the broadcast when no other broadcast message indicated as "High Priority" or "Normal"; + 3. If the value of *Category* IE is indicated as "Normal", the RNC shall perform the broadcast according to the *Repetition Period* IE. +- If the *Category* IE is not given in the WRITE-REPLACE message, the RNC shall perform the broadcast as the same category indicated as "Normal". + +The RNC shall pass the *Data Coding Scheme* IE transparently to the radio interface protocol. + +The RNC shall pass the *Broadcast Message Content* IE Transparently to the radio interface protocol. + +The RNC shall broadcast the message frequently according to the value of the *Number of Broadcasts Requested* IE. If the value is set to "0", the RNC shall broadcast the message until the CN requests otherwise. If the value is different than "0", the RNC shall broadcast the message as many times as indicated in the *Number of Broadcasts Requested* IE, and after the completion of the broadcast, the RNC shall release the involved messages and their status stored for each service area. + +Upon receipt of the WRITE-REPLACE message the RNC shall respond using the WRITE-REPLACE COMPLETE message containing a *New Serial Number* IE indicating that resources are available as requested for the Service Area(s) specified and a *Number of Broadcasts Completed List* IE to indicate the number of times the version of the old CBS message identified by the *Message Identifier* IE and the *Old Serial Number* IE, has been successfully broadcast to the particular Service Area(s). If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +If the WRITE-REPLACE message sent from the CN: + +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, the *Number of Broadcasts* IE within the *Number of Broadcasts Completed List* IE is set to "0" for each included Service Area in the corresponding WRITE-REPLACE COMPLETE message. +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, an entry is made in the *Number of Broadcasts* IE in the *Number of Broadcasts Completed List* IE for each included Service Area in the corresponding WRITE-REPLACE COMPLETE message. The RNC shall also release the involved old messages and their status stored for each service area. + +If *Paging ETWS Indicator* IE is included in the WRITE-REPLACE message, the RNC shall construct and send paging message towards the UE. The paging message contains warning information based on *Warning Type* IE. If the *Broadcast Message Content Validity Indicator* IE is included in the WRITE-REPLACE message then the RNC shall ignore the contents of the *Broadcast Message Content* IE, *Repetition Period* IE and *Number of Broadcasts Requested* IE. + +If the *Warning Security Information* IE is included in the WRITE-REPLACE message sent from the CN, the RNC shall send the *Warning Security Information* IE together with the paging message. + +### 8.2.3 Unsuccessful Operation + +![Sequence diagram illustrating the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two vertical lifelines: RNC (left) and CN (right). A horizontal arrow labeled 'WRITE-REPLACE' points from the CN to the RNC. A horizontal arrow labeled 'WRITE-REPLACE FAILURE' points from the RNC back to the CN. Both lifelines end with a thick horizontal bar at the bottom.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` + +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: WRITE-REPLACE + Note right of RNC: + RNC-->>CN: WRITE-REPLACE FAILURE + Note right of CN: + +``` + +Sequence diagram illustrating the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two vertical lifelines: RNC (left) and CN (right). A horizontal arrow labeled 'WRITE-REPLACE' points from the CN to the RNC. A horizontal arrow labeled 'WRITE-REPLACE FAILURE' points from the RNC back to the CN. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 2: Write-Replace Procedure: Un-Successful Operation** + +If there is at least one Service Area specified in the WRITE-REPLACE message for which the RNC cannot allocate all the resources requested or for which the RNC cannot complete as requested, then the RNC shall return a WRITE-REPLACE FAILURE message to the CN as an outcome of the procedure. A list of Service Area(s) where the requested resources are unavailable or for which the RNC cannot complete as requested and appropriate cause value shall be provided in this WRITE-REPLACE FAILURE message in the *Failure List* IE. + +This WRITE-REPLACE FAILURE message may also include those Service Area(s) where the requested resources were available and shall indicate in the *Number of Broadcasts Completed List* IE those Service Area(s) which completed the request successfully. + +If the WRITE-REPLACE message sent from the CN: + +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, the *Number of Broadcasts* IE within the *Number of Broadcasts Completed List* IE is set to '0' for each included Service Area in the corresponding WRITE-REPLACE FAILURE message. +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, and the CBS message is already used by the RNC, it shall consider the Write Replace procedure as failed for this Service Area and return a WRITE-REPLACE FAILURE message with the Service Area Identifier of this particular Service Area included in the *Failure List* IE together with the cause value "Message-reference already-used". + +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, an entry is made in *Number of Broadcasts* IE in the *Number of Broadcasts Completed List* IE for each included Service Area in the corresponding WRITE-REPLACE FAILURE message. +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, but if the old CBS message is unknown to the RNC (i.e. it can not execute the kill request) for a particular Service Area, it shall consider the Write Replace procedure as failed for this Service Area. When the procedure is completed, the RNC shall return a WRITE-REPLACE-FAILURE message which includes the Service Area Identifier of this particular Service Area in the *Failure List* IE together with the cause value “Valid-CN-message-not-identified”. + +### 8.2.4 Abnormal Conditions + +## 8.3 Kill + +### 8.3.1 General + +The purpose of the Kill procedure is to stop the broadcast of the indicated message. + +### 8.3.2 Successful Operation + +![Sequence diagram of the Kill Procedure: Successful Operation. It shows two vertical lifelines: RNC (left) and CN (right). A horizontal arrow labeled 'KILL' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'KILL COMPLETE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note right of CN: KILL + CN->>RNC: KILL + Note left of RNC: KILL COMPLETE + RNC->>CN: KILL COMPLETE +``` + +Sequence diagram of the Kill Procedure: Successful Operation. It shows two vertical lifelines: RNC (left) and CN (right). A horizontal arrow labeled 'KILL' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'KILL COMPLETE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom. + +Figure 3: Kill Procedure: Successful Operation + +The CN shall initiate the procedure by sending a KILL message to the RNC. + +Upon receipt of the KILL message the RNC shall stop broadcasting the CBS message, which is indicated in the *Message Identifier* IE and the twelve leftmost bits of the *Old Serial Number* IE, in the indicated Service Area(s) as indicated in the *Service Areas List* IE. + +The RNC shall respond using the KILL COMPLETE message, containing the *Old Serial Number* IE copied from the request and the *Number of Broadcast Completed List* IE when all Service Areas successfully stopped the broadcast. It shall indicate in the *Number of Broadcast Completed List* IE for each of these Service Area(s), the number of times the version of the CBS message identified by the *Message Identifier* IE and the *Old Serial Number* IE received has been sent to this particular Service Area(s) for broadcast. The RNC shall also release the involved messages and their status stored for each service area. If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +### 8.3.3 Unsuccessful Operation + +![Sequence diagram for Kill Procedure: Un-Successful Operation](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: KILL + Note right of CN: + RNC-->>CN: KILL FAILURE + Note right of RNC: +``` + +The diagram shows a sequence of messages between a CN (Core Network) and an RNC (Radio Network Controller). The CN sends a 'KILL' message to the RNC. The RNC responds with a 'KILL FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for Kill Procedure: Un-Successful Operation + +**Figure 4: Kill Procedure: Un-Successful Operation** + +If the RNC fails to stop broadcasting the CBS message as indicated in the KILL message in at least one service area, the RNC shall return the KILL FAILURE message to the CN. A *Failure List* IE indicating the list of Service Area(s) where the CBS message was not recognized or the broadcast could not be stopped together with the appropriate cause value shall be provided in the KILL FAILURE message. This response message may also – if applicable - indicate in the *Number of Broadcasts Completed List* IE those Service Area(s) where the KILL message successfully stopped the broadcast. + +### 8.3.4 Abnormal Conditions + +## 8.4 Load Status Enquiry + +### 8.4.1 General + +The purpose of this Load Status Enquiry procedure is to obtain the current permissible bandwidth available for broadcast within particular Service Area(s). + +### 8.4.2 Successful Operation + +![Sequence diagram for Load Status Enquiry Procedure: Successful Operation](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: LOAD QUERY + Note right of CN: + RNC-->>CN: LOAD QUERY COMPLETE + Note right of RNC: +``` + +The diagram shows a sequence of messages between a CN (Core Network) and an RNC (Radio Network Controller). The CN sends a 'LOAD QUERY' message to the RNC. The RNC responds with a 'LOAD QUERY COMPLETE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for Load Status Enquiry Procedure: Successful Operation + +**Figure 5: Load Status Enquiry Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a LOAD QUERY message to the RNC. The message shall include a *Service Areas List* IE. Upon reception of the LOAD QUERY message the RNC shall respond with a LOAD QUERY COMPLETE message containing the *Radio Resource Loading List* IE indicating the available bandwidth of the Service Area(s). + +### 8.4.3 Unsuccessful Operation + +![Sequence diagram for Figure 6: Load Status Enquiry Procedure: Un-Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a 'LOAD QUERY' message to the RNC. The RNC responds with a 'LOAD QUERY FAILURE' message to the CN.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: LOAD QUERY + Note right of RNC: + RNC-->>CN: LOAD QUERY FAILURE + Note right of CN: +``` + +Sequence diagram for Figure 6: Load Status Enquiry Procedure: Un-Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a 'LOAD QUERY' message to the RNC. The RNC responds with a 'LOAD QUERY FAILURE' message to the CN. + +**Figure 6: Load Status Enquiry Procedure: Un-Successful Operation** + +If the RNC contains Service Area(s) for which the RNC was not able to respond to, it shall respond with a LOAD QUERY FAILURE message which includes the *Failure List* IE. + +The LOAD QUERY FAILURE response message may – if applicable - also contain a *Radio Resource Loading List* IE for which the LOAD STATUS QUERY reporting was successful. + +### 8.4.4 Abnormal Conditions + +## 8.5 Message Status Query + +### 8.5.1 General + +The Message Status Query procedure is used by the CN to obtain the message status of a broadcast message. + +### 8.5.2 Successful Operation + +![Sequence diagram for Figure 7: Message Status Query Procedure: Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a 'MESSAGE STATUS QUERY' message to the RNC. The RNC responds with a 'MESSAGE STATUS QUERY COMPLETE' message to the CN.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: MESSAGE STATUS QUERY + Note right of RNC: + RNC-->>CN: MESSAGE STATUS QUERY COMPLETE + Note right of CN: +``` + +Sequence diagram for Figure 7: Message Status Query Procedure: Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a 'MESSAGE STATUS QUERY' message to the RNC. The RNC responds with a 'MESSAGE STATUS QUERY COMPLETE' message to the CN. + +**Figure 7: Message Status Query Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a MESSAGE STATUS QUERY message to the RNC. The message shall contain the *Old Serial Number* IE along with the *Service Areas List* IE containing the Service Area Identifiers the status query is intended for. The status is requested for the version of the CBS message identified by the *Message Identifier* IE and the full value of the *Old Version Number* IE. + +Upon receipt of the MESSAGE STATUS QUERY message the RNC shall respond using the MESSAGE STATUS QUERY COMPLETE message. + +Within this message the *Number of Broadcasts Completed List* IE contains each Service Area which successfully performed the requested operation and for each of these Service Area(s), the number of times the version of this CBS message has been sent to this particular Service Area(s) for broadcast. If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +### 8.5.3 Unsuccessful Operation + +![Sequence diagram showing the Message Status Query Procedure for an Unsuccessful Operation. The diagram shows two lifelines: RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY FAILURE message to the CN.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: MESSAGE STATUS QUERY + Note right of RNC: + RNC-->>CN: MESSAGE STATUS QUERY FAILURE + Note right of CN: +``` + +Sequence diagram showing the Message Status Query Procedure for an Unsuccessful Operation. The diagram shows two lifelines: RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY FAILURE message to the CN. + +**Figure 8: Message Status Query Procedure: Un-Successful Operation** + +If the requested operation fails (e.g. because the CBS message is unknown, or when the RNC cannot send the status for a known CBS message) the RNC shall send a MESSAGE STATUS QUERY FAILURE message to the CN containing a *Failure List* IE for Service Area(s) for which the requested operation failed. + +The MESSAGE STATUS QUERY FAILURE message may – if applicable - also include the *Number of Broadcasts Completed List* IE indicating those Service Area(s) for which the MESSAGE STATUS QUERY message was successful. + +### 8.5.4 Abnormal Conditions + +## 8.6 Reset + +### 8.6.1 General + +The purpose of the Reset procedure is to end broadcasting in one or more Service Areas in the RNC. + +### 8.6.2 Successful Operation + +![Sequence diagram for Successful Reset Operation](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note right of CN: + CN->>RNC: RESET + Note left of RNC: + RNC->>CN: RESET COMPLETE +``` + +A sequence diagram illustrating the successful reset procedure. It features two vertical lifelines: RNC on the left and CN on the right. The CN sends a 'RESET' message to the RNC, represented by a horizontal arrow pointing from the CN lifeline to the RNC lifeline. The RNC then responds with a 'RESET COMPLETE' message, represented by a horizontal arrow pointing from the RNC lifeline to the CN lifeline. Both lifelines have a thick horizontal bar at the bottom, indicating the end of the sequence. + +Sequence diagram for Successful Reset Operation + +**Figure 9: Reset Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a RESET message to the RNC, in order to end broadcasting in one or more Service Areas of the RNC. + +Upon receipt of this message the RNC shall end broadcasting in the indicated Service Area(s) and shall respond using a RESET COMPLETE message. + +### 8.6.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Reset Operation](29f586959675cafdf81cf934954908eb_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note right of CN: + CN->>RNC: RESET + Note left of RNC: + RNC->>CN: RESET FAILURE +``` + +A sequence diagram illustrating the unsuccessful reset procedure. It features two vertical lifelines: RNC on the left and CN on the right. The CN sends a 'RESET' message to the RNC, represented by a horizontal arrow pointing from the CN lifeline to the RNC lifeline. The RNC then responds with a 'RESET FAILURE' message, represented by a horizontal arrow pointing from the RNC lifeline to the CN lifeline. Both lifelines have a thick horizontal bar at the bottom, indicating the end of the sequence. + +Sequence diagram for Unsuccessful Reset Operation + +**Figure 10: Reset Procedure: Un-Successful Operation** + +If upon receipt of this message the RNC can not end broadcasting in the indicated Service Area(s), it shall respond using a RESET FAILURE message. The RESET FAILURE message may contain the *Service Areas List* IE and shall contain the *Failure List* IE indicating the relevant Service Area(s) in which the RESET message was successful and unsuccessful respectively, along with the appropriate cause value. + +The sum of the Service Area(s) included in the *Service Areas List* and *Failure List* IEs shall be the same as indicated in the *Service Areas List* IE of the initiating RESET message. + +### 8.6.4 Abnormal Conditions + +## 8.7 Restart Indication + +### 8.7.1 General + +The purpose of the Restart Indication procedure is for the RNC to indicate to the CN that a Service Area broadcasting related restart situation has occurred in one or more of its Service Areas e.g. when a Service Area becomes operational or when the RNC is initialised. + +### 8.7.2 Successful Operation + +![Sequence diagram for Restart Indication Procedure: Successful Operation](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +A sequence diagram showing the interaction between an RNC and a CN. The RNC is on the left and the CN is on the right. A horizontal arrow labeled "RESTART" points from the RNC to the CN. Both the RNC and the CN have a thick horizontal bar at the bottom of their lifelines, indicating the start of the procedure. + +Sequence diagram for Restart Indication Procedure: Successful Operation + +**Figure 11: Restart Indication Procedure: Successful Operation** + +The RNC shall initiate the procedure by sending a RESTART message to the CN. This message shall contain a *Service Areas List* IE for reference and may also include the *Recovery Indication* IE to indicate whether the previous broadcast information needs to be loaded. In the absence of the *Recovery Indication* IE, the CN shall interpret it as "lost". + +### 8.7.3 Abnormal Conditions + +## 8.8 Failure Indication + +### 8.8.1 General + +The purpose of the Failure Indication procedure is to indicate to the CN from the RNC that a Service Area broadcasting related problem is occurring in one or more of its Service Areas. + +### 8.8.2 Successful Operation + +![Sequence diagram for Failure Indication Procedure: Successful Operation](098802c99831a6a7d445310d5e874e16_img.jpg) + +A sequence diagram showing the interaction between an RNC and a CN. The RNC is on the left and the CN is on the right. A horizontal arrow labeled "FAILURE" points from the RNC to the CN. Both the RNC and the CN have a thick horizontal bar at the bottom of their lifelines, indicating the start of the procedure. + +Sequence diagram for Failure Indication Procedure: Successful Operation + +**Figure 12: Failure Indication Procedure: Successful Operation** + +The RNC shall initiate the procedure by sending a FAILURE message to the CN. The FAILURE message shall contain the *Service Areas List* IE to indicate which Service Area(s) has a Service Area broadcasting related problem. + +Upon receipt of this FAILURE message, the CN will not generate further WRITE or REPLACE messages for these Service Area(s) until the CN is informed by a RESTART message that the Service Area can resume normal Service Area broadcasting operation. + +### 8.8.3 Abnormal Conditions + +## 8.9 Error Indication + +### 8.9.1 General + +The Error Indication procedure is initiated by the RNC to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +### 8.9.2 Successful Operation + +![Sequence diagram showing the Error Indication Procedure: Successful Operation. It features two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'ERROR INDICATION' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note left of RNC: + RNC->>CN: ERROR INDICATION + Note right of CN: +``` + +Sequence diagram showing the Error Indication Procedure: Successful Operation. It features two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'ERROR INDICATION' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 13: Error Indication Procedure: Successful Operation** + +When the conditions defined in chapter 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. + +The ERROR INDICATION message shall contain at least either the *Cause* IE or the *Criticality Diagnostics* IE. + +Examples for possible cause values for protocol error indications are: + +- "Transfer Syntax Error". +- "Abstract Syntax Error (reject)". + +### 8.9.3 Abnormal Conditions + +# --- 9 Elements for SABP Communication + +## 9.1 Message Functional Definition and Content + +### 9.1.1 General + +Section 9.1 presents the contents of SABP messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [10]. + +For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message. + +### 9.1.2 Message Contents + +#### 9.1.2.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 3 + +**Table 3: Meaning of abbreviations used in SABP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| M | IE's marked as Mandatory (M) will always be included in the message. | +| O | IE's marked as Optional (O) may or may not be included in the message. | +| C | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible. + +**Table 4: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +### 9.1.3 WRITE-REPLACE + +This message is sent by the CN to the RNC. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Old Serial Number | O | | 9.2.4 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | reject | +| Category | O | | 9.2.7 | | yes | ignore | +| Repetition Period | M | | 9.2.8 | | yes | reject | +| Number of Broadcasts Requested | M | | 9.2.9 | | yes | reject | +| Data Coding Scheme | M | | 9.2.15 | | yes | reject | +| Broadcast Message Content | M | | 9.2.2 | | yes | reject | +| Warning Security Information | O | | 9.2.23 | See TS 23.041 [5]. | yes | ignore | +| Paging ETWS Indicator | O | | 9.2.21 | | yes | ignore | +| Warning Type | O | | 9.2.22 | | yes | ignore | +| Broadcast Message Content Validity Indicator | O | | 9.2.24 | | yes | ignore | + +### 9.1.4 WRITE-REPLACE COMPLETE + +This message will be sent by the RNC to the CN in a successful response to a WRITE-REPLACE message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Number of Broadcasts
Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.5 WRITE-REPLACE FAILURE + +This message will be sent by the RNC to the CN as an unsuccessful response to a WRITE-REPLACE message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Number of Broadcasts
Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.6 KILL + +This message is sent by the CN to the RNC to stop broadcasting of a specific message. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.7 KILL COMPLETE + +This message is sent by the RNC to the CN as a successful response to a KILL message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts
Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.8 KILL FAILURE + +This message is sent by the RNC to the CN as unsuccessful response to a KILL message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Number of Broadcasts Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.9 LOAD QUERY + +This message is sent by the CN to the RNC to gain an indication of broadcast resources available. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.10 LOAD QUERY COMPLETE + +This message will be sent by the RNC as a successful response to the LOAD QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Radio Resource Loading List | M | | 9.2.13 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.11 LOAD QUERY FAILURE + +This message is sent by the RNC to the CN as an unsuccessful response to a LOAD QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Radio Resource Loading List | O | | 9.2.13 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.12 MESSAGE STATUS QUERY + +This message is sent by the CN to the RNC to obtain the current status of a Service Area broadcasting message. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.13 MESSAGE STATUS QUERY COMPLETE + +This message is sent by the RNC to the CN as a successful response to a MESSAGE QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.14 MESSAGE STATUS QUERY FAILURE + +This message is sent by the RNC to the CN in an unsuccessful response to a MESSAGE QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.15 RESET + +The message is sent by the CN to the RNC to request that the RNC end broadcasting in one or more Service Areas. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.16 RESET COMPLETE + +This message is sent from the RNC to the CN as a successful response to a RESET message where indicated Service-Area(s) are now not broadcasting any messages. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.17 RESET FAILURE + +This message is sent from the RNC to the CN as an unsuccessful response to a RESET message to indicate that a Service Area broadcasting related problem exists in one or more of its Service Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Service Areas List | O | | 9.2.6 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.18 RESTART + +This message is sent from the RNC to the CN to indicate a Service Area broadcasting related restart situation in one or more of its Service-Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | ignore | +| Recovery Indication | O | | 9.2.16 | | yes | ignore | + +### 9.1.19 FAILURE + +This message is sent from the RNC to the CN to indicate that a Service Area broadcasting related problem exists in one or more of its Service-Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | ignore | + +### 9.1.20 ERROR INDICATION + +This message is sent by the RNC to CN and is used to indicate that some errors have been detected in the node. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Message Identifier | O | | 9.2.19 | | yes | ignore | +| Serial Number | O | | 9.2.3 | | yes | ignore | +| Cause | O | | 9.2.14 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +## 9.2 Information Element Definitions + +### 9.2.0 General + +Section 9.2 presents the SABP IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); +- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information; + +### 9.2.1 MessageType + +*MessageType* IE uniquely identifies the message being sent. It is mandatory for all messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Message Type | | | | | +| >Procedure Code | M | | ENUMERATED (Write-Replace, Kill, Load Status Enquiry, Message Status Query, Reset, Restart Indication, Failure Indication, Error Indication ....) | | +| >Type of Message | M | | ENUMERATED (Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome) | | + +### 9.2.2 Broadcast Message Content + +*Broadcast Message Content* IE is sent from the CN to the RNC containing user information i.e. the message, and will be broadcast over the radio interface. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------------|----------|-------|----------------------|------------------------------------------------------------| +| Broadcast Message Content | M | | BIT STRING (1..9968) | The size of the received bitstring shall be multiple of 8. | + +### 9.2.3 Serial Number + +*Serial Number* IE is a 16-bit integer which identifies a particular message from the source and type indicated by the Message Identifier and is altered every time the message with a given Message Identifier is changed. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|----------------|-----------------------| +| Serial Number | O | | BIT STRING(16) | | + +### 9.2.4 Old Serial Number + +*Old Serial Number* IE enables identification of an existing message to be identified. The format of this IE is defined in subclause 9.2.3. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------|-----------------------| +| Old Serial Number | M | | 9.2.3 | | + +### 9.2.5 New Serial Number + +*New Serial Number* IE enables identification of a new message for broadcast to be identified, and is altered every time the message is changes. The format of this IE is defined in subclause 9.2.3. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------|-----------------------| +| New Serial Number | O | | 9.2.3 | | + +### 9.2.6 Service Areas List + +The *Service Areas List* IE identifies a sequence of one or more Service Areas to which the message(s) apply. The *Service Areas List* IE must include at least one Service Area. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------------|----------|---------------------|-------------|-----------------------| +| Service Areas List | | 1 to | | | +| >Service Area Identifier | M | | 9.2.11 | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Areas List. Value is 65535 | + +### 9.2.7 Category + +*Category* IE is sent from the CN to the RNC, and is used to indicate the priority of the message. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Category | O | | Enumerated (High Priority, Background, Normal, Default) | This IE contains the broadcast priority of the message.
The value "Default" shall not be used | + +### 9.2.8 Repetition Period + +*Repetition Period* IE is sent from the CN to the RNC and indicates the periodicity of message broadcasts. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------------|---------------------------------------------------------------------------------------------------------------| +| Repetition Period | M | | INTEGER (1..4096) | Range is 1 to 4096 where each unit will represent a repetition of one second to a maximum of once per ~1 hour | + +### 9.2.9 Number of Broadcasts Requested + +*Number of Broadcasts Requested* IE is sent from the CN to the RNC and indicates the number of times a message is to be broadcast. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------------|----------|------------|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of Broadcasts Requested | M | 0 to 65535 | INTEGER (0..65535) | This specifies the number of times the message is to be broadcast.
"0" indicates the message shall be broadcasted until CN request otherwise. | + +### 9.2.10 Number of Broadcasts Completed List + +*Number of Broadcasts Completed List* IE is sent from the RNC to the CN, and indicates the number of times that a CN message (all pages) has been sent to each Service Area specified in the *Service Areas List* IE of the request message for broadcast over the radio interface. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------------------------|----------|--------------------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of Broadcasts Completed List | | 1 to | | | +| >Service Area Identifier | M | | OCTET STRING (7) | | +| >Number of Broadcasts | M | | INTEGER (0.. 65535 ) | | +| >Number of Broadcasts Compl Info | O | | ENUMERATED (overflow, unknown) | Overflow indicates that the number of times that CN message sent to the radio interface has been overflow.
Unknown indicates that no information regarding the number of times that CN message sent to the radio interface. | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Areas List Value is 65535 | + +### 9.2.11 Service Area Identifier + +*Service Area Identifier* IE in BC domain is used to identify an area consisting of one cell TS 23.003 [12]. Such an area is called a Service Area. For this protocol, only a Service Area that is defined to be applicable to the BC domain shall be used. + +| IE/Group Name | Presence | Range | IE type and Reference | Semantics description | +|----------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SAI | | | | | +| >PLMN identity | M | | OCTET STRING (SIZE (3)) |
  • - digits 0 to 9, two digits per octet,
  • - each digit encoded 0000 to 1001,
  • - 1111 used as filler
  • - bit 4 to 1 of octet n encoding digit 2n-1
  • - bit 8 to 5 of octet n encoding digit 2n

  • -The PLMN identity consists of 3 digits from MCC followed by either
  • -a filler plus 2 digits from MNC (in case of 2 digit MNC) or
  • -3 digits from MNC (in case of a 3 digit MNC).
| +| >LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. | +| >SAC | M | | OCTET STRING (2) | | + +### 9.2.12 Failure List + +*Failure List* IE identifies the list of Service-Area(s) for which the RNC could not complete as requested. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------|----------|--------------------|-------------|-----------------------| +| Failure List | | 1 to | | | +| >Service Area Identifier | M | | 9.2.11 | | +| >Cause | M | | 9.2.14 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service-Area-List. Value is 65535 | + +### 9.2.13 Radio Resource Loading List + +*Radio Resource Loading List* IE presents the available bandwidth available for Broadcast purposes of a specific Service Area. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|------------------------------------|----------|--------------------|-------------|-----------------------| +| Radio Resource Loading List | | 1 to | | | +| >Service Area Identifier | M | | 9.2.11 | | +| >Available Bandwidth | M | | 9.2.18 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Area List. Value is 65535 | + +### 9.2.14 Cause + +*Cause* IE indicates the reason for a particular error event for the SABP protocol. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >Cause | M | | INTEGER (

Parameter-not-recognised(0),













Parameter-value invalid(1), | Range is 0-255

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

Sent when a failure occurred due to the value of a parameter being invalid, e.g. out of range, or in Write- | + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | |






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



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





Unrecognised-message(4)




Missing-mandatory-element(5),




RNC-capacity-exceeded(6),









RNC-memory-exceeded(7),







Service-Area-broadcast-not-supported(8),






Service-Area-broadcast-not-operational(9),

|

Replace, the parameter "no of pages" does not equal the number of pages received

Sent when the RNC does not recognise the CN message reference

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

Sent when the RNC did not recognise the message at all

Sent when a mandatory element is missing from the message

Sent when a write-replace fails because the RNC cannot meet the requested repetition period because of the cell loading

Sent when the RNC is unable to store a CBS message as the RNC memory has been exceeded.

Sent when the SABCH/CN related Radio Resource is not configured for a Service-Area

Sent when the SABCH/CN related radio resource is not available because of error conditions or due to maintenance activities

| + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Message-reference already-used(10), | Sent when the recipient was unable to act upon the Write-Replace message received due to a previous Write-Replace received with the same message reference. | +| | | | Unspecified-error(11), | Sent when none of the above cause values apply. | +| | | | (Transfer Syntax Error(12), | Sent to indicate transfer syntax error in any message | +| | | | Semantic Error (12), | Sent to indicate semantic error any message | +| | | | Message not compatible with receiver state (14), | Sent to indicate that received message is not compatible with the receiver state | +| | | | Abstract Syntax Error (Reject) (15), | Sent to indicate rejection due to Abstract Syntax Error | +| | | | Abstract Syntax Error (Ignore and Notify) (16), | Sent to indicate Abstract Syntax Error in some IE that has been ignored | +| | | | Abstract Syntax Error (Falsely Constructed Message) (17)) | Sent to indicate Abstract Syntax Error due to false message construction | + +### 9.2.15 Data Coding Scheme + +*Data Coding Scheme* IE is sent from the RNC to the CN and identifies the alphabet or coding employed for the message characters and message handling at the UE (it is passed transparently from the CN to the UE). + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------|----------|-------|---------------|-----------------------| +| Data Coding Scheme | M | | BIT STRING(8) | | + +### 9.2.16 Recovery Indication + +*Recovery Indication* IE is used to indicate whether the CN related data was lost or is still available. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|------------------------------|-----------------------| +| Recovery Indication | O | | ENUMERATED (Lost, Available) | | + +### 9.2.17 Criticality Diagnostics + +For further details on how to use the *Criticality Diagnostics* IE, see annex A. + +The *Criticality Diagnostics* IE is sent by the RNC or the CN when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs that were not comprehended or were missing. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-----------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | | | +| >Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| >Triggering Message | O | | ENUMERATED(initiating message, successful outcome, unsuccessful outcome, outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | +| >Procedure Criticality | O | | ENUMERATED(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0 to | | | +| >IE Criticality | M | | ENUMERATED(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | +| >IE ID | M | | INTEGER (0..65535) | The IE Id of the not understood or missing IE | +| >Repetition Number | O | | INTEGER (0..255) | The Repetition Number IE gives
  • in case of a not understood IE: The number of occurrences of the reported IE up to and including the not understood occurrence
| + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | |
  • in case of a missing IE:
    The number of occurrences up to but not including the missing occurrence.

Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.

| +| >Message Structure | O | | 9.2.20 | The Message Structure IE describes the structure where the not understood or missing IE was detected. This IE is included if the not understood IE is not the top level of the message. | +| >Type of Error | M | | ENUMERATED(not understood, missing, ...) | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------------------------| +| Maxnooferrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. | + +### 9.2.18 Available Bandwidth + +*Available Bandwidth* IE is used to indicate the Bandwidth available for the broadcast of messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-------------------------| +| Available Bandwidth | O | | INTEGER (0..20480) | The unit is: bit/second | + +### 9.2.19 Message Identifier + +*Message Identifier* IE is set by the CN, transfer to the UE by the RNC. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Identifier | M | | BIT STRING(16) | This IE is set by the CN, transfer to the UE by the RNC, the RNC needs not to understand what is the meaning of the value but shall treat it as a identifier of a message. The Message Identifier is defined in TS 25.324 [11]. | + +### 9.2.20 Message Structure + +The *Message Structure* IE gives information for each level with assigned criticality in an hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the *Information Element Criticality Diagnostics* IE). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message structure | | 1 to | | The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message. | GLOBAL | ignore | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of this level's IE containing the not understood or missing IE. | - | | +| >Repetition Number | O | | INTEGER (1..256) |

The Repetition Number IE gives, if applicable, the number of occurrences of this level's reported IE up to and including the occurrence containing the not understood or missing IE.

Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.

| - | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------| +| maxnooflevels | Maximum no. of message levels to report. The value for maxnooflevels is 256. | + +### 9.2.21 Paging ETWS Indicator + +*Paging ETWS Indicator* IE is used to indicate to the RNC that the received SABP message contains ETWS contents that need to be sent via paging message towards the UE. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-----------------------|----------|-------|--------------------------|-----------------------| +| Paging ETWS Indicator | M | | ENUMERATED (Paging, ...) | | + +### 9.2.22 Warning Type + +Warning Type IE indicates the types of the disaster. This IE can be used by the UE to differentiate type of alert according to the type of disaster. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|------------------|-----------------------| +| Warning Type | M | | OCTET STRING (2) | | + +### 9.2.23 Warning Security Information + +*Warning Security Information* IE is set by the CN, transferred to the UE by the RNC. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and
Reference | Semantics Description | +|------------------------------|----------|-------|--------------------------|-----------------------| +| Warning Security Information | M | | OCTET STRING(50) | | + +### 9.2.24 Broadcast Message Content Validity Indicator + +The *Broadcast Message Content Validity Indicator* IE indicates that the *Broadcast Message Content* IE does not contain any valid information. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and
Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------------------------------------|-----------------------| +| Broadcast Message Content Validity Indicator | M | | ENUMERATED
(Broadcast Message Content not valid) | | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +SABP ASN.1 definition conforms with ITU-T Rec. X.680 [7] and ITU-T Rec. X.681 [8]. + +The ASN.1 definition specifies the structure and content of SABP messages. SABP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a SABP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a SABP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 10.3.6. + +### 9.3.1 Usage of protocol extension mechanism for non-standard use + +The protocol extension mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability. +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +SABP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM SABP-CommonDataTypes + + Error-Indication, + Failure, + Kill, + Kill-Complete, + Kill-Failure, + Load-Query, + Load-Query-Complete, + Load-Query-Failure, + Reset, + Reset-Complete, + Reset-Failure, + Restart, + Message-Status-Query, + Message-Status-Query-Complete, + Message-Status-Query-Failure, + Write-Replace, + Write-Replace-Complete, + Write-Replace-Failure +FROM SABP-PDU-Contents + + id-Error-Indication, + id-Failure-Indication, + id-Kill, + id-Reset, + id-Restart-Indication, + id-Load-Status-Enquiry, + +``` + +``` + + id-Message-Status-Query, + id-Write-Replace +FROM SABP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +SABP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME + + &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU Definition +-- +-- ***** + +SABP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SABP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SABP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + +``` + +``` + value SABP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) + } + + -- ***** + -- + -- Interface Elementary Procedure List + -- + -- ***** + + SABP-ELEMENTARY-PROCEDURES SABP-ELEMENTARY-PROCEDURE ::= { + SABP-ELEMENTARY-PROCEDURES-CLASS-1 | + SABP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... + } + + SABP-ELEMENTARY-PROCEDURES-CLASS-1 SABP-ELEMENTARY-PROCEDURE ::= { + write-Replace | + kill | + load-Status-Enquiry | + message-Status-Query | + reset , + ... + } + + SABP-ELEMENTARY-PROCEDURES-CLASS-2 SABP-ELEMENTARY-PROCEDURE ::= { + restart-Indication | + failure-Indication | + error-Indication , + ... + } + + write-Replace SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Write-Replace + SUCCESSFUL OUTCOME Write-Replace-Complete + UNSUCCESSFUL OUTCOME Write-Replace-Failure + PROCEDURE CODE id-Write-Replace + CRITICALITY reject + } + + kill SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Kill + SUCCESSFUL OUTCOME Kill-Complete + UNSUCCESSFUL OUTCOME Kill-Failure + PROCEDURE CODE id-Kill + CRITICALITY reject + } + + load-Status-Enquiry SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Load-Query + SUCCESSFUL OUTCOME Load-Query-Complete + UNSUCCESSFUL OUTCOME Load-Query-Failure + PROCEDURE CODE id-Load-Status-Enquiry + CRITICALITY reject + } +``` + +``` + +message-Status-Query SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Message-Status-Query + SUCCESSFUL OUTCOME Message-Status-Query-Complete + UNSUCCESSFUL OUTCOME Message-Status-Query-Failure + PROCEDURE CODE id-Message-Status-Query + CRITICALITY reject +} + +reset SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset + SUCCESSFUL OUTCOME Reset-Complete + UNSUCCESSFUL OUTCOME Reset-Failure + PROCEDURE CODE id-Reset + CRITICALITY reject +} + +restart-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Restart + PROCEDURE CODE id-Restart-Indication + CRITICALITY ignore +} + +failure-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Failure + PROCEDURE CODE id-Failure-Indication + CRITICALITY ignore +} + +error-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Error-Indication + PROCEDURE CODE id-Error-Indication + CRITICALITY ignore +} + +END + +``` + +### 9.3.3 PDU Definitions + +``` + +-- ***** +-- +-- PDU definitions for SABP. +-- +-- ***** + +SABP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- + +``` + +``` +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Broadcast-Message-Content, + Category, + Cause, + Criticality-Diagnostics, + Data-Coding-Scheme, + Failure-List, + Message-Identifier, + New-Serial-Number, + Number-of-Broadcasts-Completed-List, + Number-of-Broadcasts-Requested, + Old-Serial-Number, + Paging-ETWS-Indicator, + Radio-Resource-Loading-List, + Recovery-Indication, + Repetition-Period, + Serial-Number, + Service-Areas-List, + WarningSecurityInfo, + Warning-Type, + Broadcast-Message-Content-Validity-Indicator +FROM SABP-IEs + + ProtocolExtensionContainer{}, + ProtocolIE-Container{}, + SABP-PROTOCOL-EXTENSION, + SABP-PROTOCOL-IES +FROM SABP-Containers + + id-Broadcast-Message-Content, + id-Category, + id-Criticality-Diagnostics, + id-Cause, + id-Data-Coding-Scheme, + id-Failure-List, + id-Message-Identifier, + id-New-Serial-Number, + id-Number-of-Broadcasts-Completed-List, + id-Number-of-Broadcasts-Requested, + id-Old-Serial-Number, + id-Paging-ETWS-Indicator, + id-Radio-Resource-Loading-List, + id-Recovery-Indication, + id-Repetition-Period, + id-Serial-Number, + id-Service-Areas-List, + id-WarningSecurityInfo, + id-Warning-Type, + id-Broadcast-Message-Content-Validity-Indicator +FROM SABP-Constants; +``` + +``` +-- ***** +-- +-- Write-Replace +-- +-- ***** +``` + +``` +Write-Replace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Extensions} } OPTIONAL, + ... +} +``` + +``` +Write-Replace-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY ignore TYPE Old-Serial-Number PRESENCE optional } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Category CRITICALITY ignore TYPE Category PRESENCE optional } | + { ID id-Repetition-Period CRITICALITY reject TYPE Repetition-Period PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Requested + CRITICALITY reject TYPE Number-of-Broadcasts-Requested PRESENCE mandatory } | + { ID id-Data-Coding-Scheme CRITICALITY reject TYPE Data-Coding-Scheme PRESENCE mandatory } | + { ID id-Broadcast-Message-Content + CRITICALITY reject TYPE Broadcast-Message-Content PRESENCE mandatory }, + ... +} +``` + +``` +Write-Replace-Extensions SABP-PROTOCOL-EXTENSION ::= { + { ID id-WarningSecurityInfo CRITICALITY ignore EXTENSION WarningSecurityInfo PRESENCE optional } | + { ID id-Paging-ETWS-Indicator CRITICALITY ignore EXTENSION Paging-ETWS-Indicator PRESENCE optional } | + { ID id-Warning-Type CRITICALITY ignore EXTENSION Warning-Type PRESENCE optional } | + { ID id-Broadcast-Message-Content-Validity-Indicator CRITICALITY ignore EXTENSION Broadcast-Message-Content-Validity-Indicator PRESENCE optional }, + ... +} +``` + +``` +-- ***** +-- +-- Write-Replace-Complete +-- +-- ***** +``` + +``` +Write-Replace-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Complete-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Complete-Extensions} } OPTIONAL, + ... +} +``` + +``` +Write-Replace-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, +``` + +``` + + ... + } + + Write-Replace-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Write-Replace-Failure + -- + -- ***** + + Write-Replace-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Failure-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Failure-Extensions} } OPTIONAL, + ... + } + + Write-Replace-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... + } + + Write-Replace-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Kill + -- + -- ***** + + Kill ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Kill-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Kill-Extensions} } OPTIONAL, + ... + } + + Kill-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... + } + + Kill-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +} + +-- ***** +-- +-- Kill-Complete +-- +-- ***** + +Kill-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Kill-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Kill-Complete-Extensions}} OPTIONAL, + ... +} + +Kill-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Kill-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Kill-Failure +-- +-- ***** + +Kill-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Kill-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Kill-Failure-Extensions}} OPTIONAL, + ... +} + +Kill-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Kill-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +} + +-- ***** +-- +-- Load-Query +-- +-- ***** + +Load-Query ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Load-Query-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Extensions}} OPTIONAL, + ... +} + +Load-Query-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Load-Query-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Load-Query-Complete +-- +-- ***** + +Load-Query-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Load-Query-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Complete-Extensions}} OPTIONAL, + ... +} + +Load-Query-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Radio-Resource-Loading-List + CRITICALITY reject TYPE Radio-Resource-Loading-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Load-Query-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Load-Query-Failure +-- +-- ***** + +Load-Query-Failure ::= SEQUENCE { + +``` + +``` + + protocolIEs ProtocolIE-Container {{Load-Query-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Failure-Extensions}} OPTIONAL, + ... +} + +Load-Query-Failure-IEs SABP-PROTOCOL-IES ::= { + + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Radio-Resource-Loading-List + CRITICALITY ignore TYPE Radio-Resource-Loading-List + PRESENCE optional } | + + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Load-Query-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query +-- +-- ***** + +Message-Status-Query ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Extensions}} OPTIONAL, + ... +} + +Message-Status-Query-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Message-Status-Query-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query-Complete +-- +-- ***** + +Message-Status-Query-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Complete-Extensions}} OPTIONAL, + ... +} + +``` + +``` + +Message-Status-Query-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Message-Status-Query-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query-Failure +-- +-- ***** + +Message-Status-Query-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Failure-Extensions}} OPTIONAL, + ... +} + +Message-Status-Query-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Message-Status-Query-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset +-- +-- ***** + +Reset ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Extensions}} OPTIONAL, + ... +} + +``` + +``` + +Reset-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Reset-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Complete +-- +-- ***** + +Reset-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Complete-Extensions}} OPTIONAL, + ... +} + +Reset-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional } , + ... +} + +Reset-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Failure +-- +-- ***** + +Reset-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Failure-Extensions}} OPTIONAL, + ... +} + +Reset-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional } , + ... +} + +Reset-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- Restart +-- +-- ***** + +Restart ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Restart-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Restart-Extensions}} OPTIONAL, + ... +} + +Restart-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY ignore TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Recovery-Indication CRITICALITY ignore TYPE Recovery-Indication PRESENCE optional } , + ... +} + +Restart-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Failure +-- +-- ***** + +Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Failure-Extensions}} OPTIONAL, + ... +} + +Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY ignore TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Error-Indication +-- +-- ***** + +Error-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Error-Indication-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Error-Indication-Extensions}} OPTIONAL, + ... +} + +``` + +``` + +Error-Indication-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY ignore TYPE Message-Identifier PRESENCE optional } | + { ID id-Serial-Number CRITICALITY ignore TYPE Serial-Number PRESENCE optional } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Error-Indication-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +### 9.3.4 Information Element Definitions + +``` + +-- ************************************************************** +-- +-- Information Element Definitions +-- +-- ************************************************************** + +``` + +``` + +SABP-IEs { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) sabp (3) version1 (1) sabp-IEs (2) } + +``` + +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +``` + +``` + +BEGIN + +``` + +``` + +IMPORTS + +``` + +``` + + maxNrOfErrors, + maxnoofSAI, + maxNrOfLevels, + + id-MessageStructure, + id-TypeOfError + +``` + +``` + +FROM SABP-Constants + +``` + +``` + + Criticality, + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID + +``` + +``` + +FROM SABP-CommonDataTypes + +``` + +``` + + ProtocolExtensionContainer{}, + + SABP-PROTOCOL-EXTENSION + +``` + +FROM SABP-Containers; + +-- A + +Available-Bandwidth := INTEGER (0..20480) + -- bits/sec + +-- B + +Broadcast-Message-Content := BIT STRING (SIZE (1..9968)) -- This IE is sent from the CN to the RNC containing user information i.e. + -- the message. + +Broadcast-Message-Content-Validity-Indicator := ENUMERATED { + broadcast-Message-Content-not-valid, + ... +} + +-- C + +Category := ENUMERATED { + high-priority, + background-priority, + normal-priority, + default-priority, + ... +} + +Cause := INTEGER { + parameter-not-recognised (0), + parameter-value-invalid (1), + valid-CN-message-not-identified (2), + service-area-identity-not-valid (3), + unrecognised-message (4), + missing-mandatory-element (5), + rNC-capacity-exceeded (6), + rNC-memory-exceeded (7), + service-area-broadcast-not-supported (8), + service-area-broadcast-not-operational (9), + message-reference-already-used (10), + unspecified-error (11), + transfer-syntax-error (12), + semantic-error (13), + message-not-compatible-with-receiver-state (14), + abstract-syntax-error-reject (15), + abstract-syntax-error-ignore-and-notify (16), + abstract-syntax-error-falsely-constructed-message (17) +} (0..255) + +Criticality-Diagnostics := SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + +``` + + ... + } + + CriticalityDiagnostics-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... + } + + CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + repetitionNumber RepetitionNumber0 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, + ... + } + + CriticalityDiagnostics-IE-List-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + { ID id-MessageStructure CRITICALITY ignore EXTENSION MessageStructure PRESENCE optional } | + { ID id-TypeOfError CRITICALITY ignore EXTENSION TypeOfError PRESENCE mandatory }, + ... + } + + MessageStructure ::= SEQUENCE (SIZE (1..maxNrOfLevels)) OF + SEQUENCE { + iE-ID ProtocolIE-ID, + repetitionNumber RepetitionNumber1 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MessageStructure-ExtIEs} } OPTIONAL, + ... + } + + MessageStructure-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... + } + +-- D + +Data-Coding-Scheme ::= BIT STRING (SIZE (8)) + +-- E + +-- F + +Failure-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF Failure-List-Item + +Failure-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + cause Cause, + iE-Extensions ProtocolExtensionContainer { {FailureListItemIE-ExtIEs} } OPTIONAL, + ... +} + +FailureListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + +``` + +``` +... +} + +-- G + +-- H + +-- I + +-- J + +-- K + +-- L + +-- M + +Message-Identifier ::= BIT STRING (SIZE (16)) + +-- N + +New-Serial-Number ::= Serial-Number + +Number-of-Broadcasts-Completed-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF + Number-of-Broadcasts-Completed-List-Item + +Number-of-Broadcasts-Completed-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + number-of-broadcasts-completed INTEGER (0..65535), + number-of-broadcasts-completed-info Number-Of-Broadcasts-Completed-Info OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NoOfBroadcastsCompletedListItemIE-ExtIEs} } OPTIONAL, + ... +} + +NoOfBroadcastsCompletedListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +Number-Of-Broadcasts-Completed-Info ::= ENUMERATED { + overflow, + unknown, + ... +} + +Number-of-Broadcasts-Requested ::= INTEGER { + broadcast-indefinitely (0) +} (0..65535) + +-- O + +Old-Serial-Number ::= Serial-Number + +-- P + +Paging-ETWS-Indicator ::= ENUMERATED { +``` + +``` + + paging, + ... +} + +-- Q + +-- R + +Radio-Resource-Loading-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF + Radio-Resource-Loading-List-Item + +Radio-Resource-Loading-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + available-bandwidth Available-Bandwidth, + iE-Extensions ProtocolExtensionContainer { {RadioResourceLoadingListItemIE-ExtIEs} } OPTIONAL, + ... +} + +RadioResourceLoadingListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +Recovery-Indication ::= ENUMERATED { + data-lost, + data-available +} + +RepetitionNumber0 ::= INTEGER(0..255) + +RepetitionNumber1 ::= INTEGER(1..256) + +Repetition-Period ::= INTEGER (1..4096) +-- Each unit represents a repetition of one second to a maximum of +-- once per 4096 seconds (~1 hour). + +-- S + +Serial-Number ::= BIT STRING (SIZE (16)) + +Service-Area-Identifier ::= SEQUENCE { + pLMNIdentity OCTET STRING (SIZE (3)) + -- Digits 0 to 9, two digits per octet. -- + -- Each octet encoded 0000 to 1001. -- + -- 1111 used as filler -- + -- Bit 4 to 1 of octet n encoding digit 2n-1. -- + -- Bit 8 to 5 of octet n encoding digit 2n. -- + -- The PLMN identity consists of 3 digits from MCC -- + -- followed by either a filler plus 2 digits -- + -- from MNC (in case of 2 digit MNC) or 3 digits -- + -- from MNC (in case of 3 digit MNC). -- , + lac OCTET STRING (SIZE (2)) + -- 0000 and FFFE not allowed -- , + sac OCTET STRING (SIZE (2)) +} + +``` + +``` + +} + +-- **TODO** The IE type for these parameters is not known as yet +Service-Areas-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF Service-Area-Identifier + +-- T + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} + +-- U + +-- V + +-- W + +WarningSecurityInfo ::= OCTET STRING (SIZE (50)) + +Warning-Type ::= OCTET STRING (SIZE(2)) + +-- X + +-- Y + +END + +``` + +### 9.3.5 Common Definitions + +``` + +-- ****************************************************************************** +-- +-- Common definitions +-- +-- ****************************************************************************** + +SABP-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) sabp (3) version1 (1) sabp-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +ProtocolExtensionID ::= INTEGER (0..65535) + +``` + +``` + +ProtocolIE-ID ::= INTEGER (0..65535) + +TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful-outcome, outcome} + +END + +``` + +### 9.3.6 Constant Definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +SABP-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + +id-Write-Replace INTEGER ::= 0 +id-Kill INTEGER ::= 1 +id-Load-Status-Enquiry INTEGER ::= 2 +id-Message-Status-Query INTEGER ::= 3 +id-Restart-Indication INTEGER ::= 4 +id-Reset INTEGER ::= 5 +id-Failure-Indication INTEGER ::= 6 +id-Error-Indication INTEGER ::= 7 + +-- ***** +-- +-- IEs +-- +-- ***** + +id-Broadcast-Message-Content INTEGER ::= 0 +id-Category INTEGER ::= 1 +id-Cause INTEGER ::= 2 +id-Criticality-Diagnostics INTEGER ::=3 +id-Data-Coding-Scheme INTEGER ::= 4 +id-Failure-List INTEGER ::= 5 +id-Message-Identifier INTEGER ::= 6 +id-New-Serial-Number INTEGER ::= 7 +id-Number-of-Broadcasts-Completed-List INTEGER ::= 8 +id-Number-of-Broadcasts-Requested INTEGER ::= 9 +id-Old-Serial-Number INTEGER ::= 10 + +``` + +``` + +id-Radio-Resource-Loading-List INTEGER ::= 11 +id-Recovery-Indication INTEGER ::= 12 +id-Repetition-Period INTEGER ::= 13 +id-Serial-Number INTEGER ::= 14 +id-Service-Areas-List INTEGER ::= 15 +id-MessageStructure INTEGER ::= 16 +id-TypeOfError INTEGER ::= 17 +id-Paging-ETWS-Indicator INTEGER ::= 18 +id-Warning-Type INTEGER ::= 19 +id-WarningSecurityInfo INTEGER ::= 20 +id-Broadcast-Message-Content-Validity-Indicator INTEGER ::= 21 + +-- ***** +-- +-- Extension constants +-- +-- ***** + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNrOfErrors INTEGER ::= 256 +maxnoofSAI INTEGER ::= 65535 + +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 +maxNrOfLevels INTEGER ::= 256 + +END + +``` + +### 9.3.7 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +SABP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +``` + +``` + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM SABP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM SABP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +SABP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +SABP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +``` + +``` + +ProtocolIE-Container {SABP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {SABP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id SABP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality SABP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value SABP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, SABP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {SABP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {SABP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id SABP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality SABP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue SABP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} + +END + +``` + +## 9.4 Message Transfer Syntax + +SABP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [9]. + +# 10 Handling of Unknown, Unforeseen or Erroneous Protocol Data + +## 10.1 General + +Protocol Error cases can be divided into three classes: + +- Transfer Syntax Error; +- Abstract Syntax Error; +- Logical Error. + +Protocol errors can occur in the following functions within a receiving node: + +![Diagram illustrating Protocol Errors in SABP. It shows two boxes: 'SABP functional entity' at the top and 'ASN.1 Decoding' at the bottom. A dashed arrow points from 'ASN.1 Decoding' to 'SABP functional entity'. To the right of the boxes, there are three error categories: 'Logical Errors', 'Abstract Syntax Errors', and 'Transfer Syntax Errors'. Brackets indicate that 'SABP functional entity' is associated with 'Logical Errors' and 'Abstract Syntax Errors', while 'ASN.1 Decoding' is associated with 'Transfer Syntax Errors'. A large upward arrow on the far right points from the bottom to the top, indicating the flow of error reporting.](87b70d2e8951032d28b4412d82cf1413_img.jpg) + +Diagram illustrating Protocol Errors in SABP. It shows two boxes: 'SABP functional entity' at the top and 'ASN.1 Decoding' at the bottom. A dashed arrow points from 'ASN.1 Decoding' to 'SABP functional entity'. To the right of the boxes, there are three error categories: 'Logical Errors', 'Abstract Syntax Errors', and 'Transfer Syntax Errors'. Brackets indicate that 'SABP functional entity' is associated with 'Logical Errors' and 'Abstract Syntax Errors', while 'ASN.1 Decoding' is associated with 'Transfer Syntax Errors'. A large upward arrow on the far right points from the bottom to the top, indicating the flow of error reporting. + +**Figure 14: Protocol Errors in SABP** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional SABP entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE id); +2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; + +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the SABP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE; +- Ignore IE and Notify Sender; +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, SABP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class SABP-PROTOCOL-IES, SABP-PROTOCOL-IES-PAIR, SABP-PROTOCOL-EXTENSION or SABP-PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following: + +**Reject IE:** + +- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +**Ignore IE and Notify Sender:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +**Ignore IE:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +#### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +#### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +**Reject IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +##### **Ignore IE and Notify Sender:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +##### **Ignore IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex A) also the *Message Structure* IE shall be included. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex A) also the *Message Structure* IE shall be included. + +### 10.3.5 Missing IE or IE group + +The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver: + +#### **Reject IE:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. + +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +#### Ignore IE and Notify Sender: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +#### Ignore IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex A) also the *Message Structure* IE shall be included. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. In the *Information Element Criticality Diagnostics* IE the *Repetition Number* IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex A) also the *Message Structure* IE shall be included. + +### 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present + +If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: + +- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. + +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". +- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered. + +## 10.4 Logical Error + +Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IE's/IE groups containing the erroneous values. + +### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error; +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. + +# Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE + +## A.1 EXAMPLE MESSAGE Layout + +Assume the following message format: + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-----------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | | | YES | reject | +| A | M | | | | YES | reject | +| B | M | | | | YES | reject | +| >E | | 1.. | | | EACH | ignore | +| >>F | | 1.. | | | - | | +| >>>G | | 0..3, ... | | | EACH | ignore | +| >>H | | 1.. | | | EACH | ignore | +| >>>G | | 0..3, ... | | | EACH | ignore and notify | +| >>G | M | | | | YES | reject | +| >>J | | 1.. | | | - | | +| >>>G | | 0..3, ... | | | EACH | reject | +| C | M | | | | YES | reject | +| >K | | 1.. | | | EACH | ignore and notify | +| >>L | | 1.. | | | - | | +| >>>M | O | | | | - | | +| D | M | | | | YES | reject | + +Note 1. The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Container. + +For the corresponding ASN.1 layout, see subclause A.4. + +## A.2 Example on a Received EXAMPLE MESSAGE + +Assume further more that a received message based on the above tabular format is according to figure A.1. + +![A hierarchical diagram showing the structure of a received message across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (under E), H (under E), G (under E), J (under K), and L (under K). Level 4 contains seven G boxes, each with multiple overlapping boxes behind it, representing repetitions. A legend below shows a box with arrows pointing to '1st repetition', '2nd repetition', and 'Nth repetition'. A key at the bottom shows a solid box for 'IE based on a protocol container' and a dashed box for 'IE being an "ordinary" ASN.1 type'.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Legend: + +1st repetition + +2nd repetition + +... + +Nth repetition + +IE based on a protocol container + +IE being an "ordinary" ASN.1 type + +A hierarchical diagram showing the structure of a received message across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (under E), H (under E), G (under E), J (under K), and L (under K). Level 4 contains seven G boxes, each with multiple overlapping boxes behind it, representing repetitions. A legend below shows a box with arrows pointing to '1st repetition', '2nd repetition', and 'Nth repetition'. A key at the bottom shows a solid box for 'IE based on a protocol container' and a dashed box for 'IE being an "ordinary" ASN.1 type'. + +Figure A.1: Example of content of a received SABP message based on the EXAMPLE MESSAGE + +## A.3 Content of Criticality Diagnostics + +### A.3.1 Example 1 + +![Diagram of a hierarchical message structure with four levels. Level 1 contains IEs A, B, C, and D. Level 2 contains IE E (with 4 repetitions) and IE K. Level 3 contains IE F (dashed), IE H, IE G (5), IE J (dashed), and IE L (dashed). Level 4 contains multiple instances of IE G. IE J on level 3 is shown with dashed lines and contains an instance of IE G on level 4 (instances 10, 11, 12) which is shaded grey. Arrows indicate that IE E on level 2 is included in the Message Structure IE, and the shaded IE G instance on level 4 is included in the Information Element Criticality Diagnostics IE. The legend indicates: a) IE ID IE, b) Repetition Number IE.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Information Element Criticality Diagnostics IE*: + +- a) *IE ID IE* +- b) *Repetition Number IE* + +Diagram of a hierarchical message structure with four levels. Level 1 contains IEs A, B, C, and D. Level 2 contains IE E (with 4 repetitions) and IE K. Level 3 contains IE F (dashed), IE H, IE G (5), IE J (dashed), and IE L (dashed). Level 4 contains multiple instances of IE G. IE J on level 3 is shown with dashed lines and contains an instance of IE G on level 4 (instances 10, 11, 12) which is shaded grey. Arrows indicate that IE E on level 2 is included in the Message Structure IE, and the shaded IE G instance on level 4 is included in the Information Element Criticality Diagnostics IE. The legend indicates: a) IE ID IE, b) Repetition Number IE. + +**Figure A.2: Example of a received SABP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure A.2, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows: + +| IE name | Value | Comment | +|---------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 4. | +| IE ID | id-G | IE ID from the reported level, i.e. level 4. | +| Repetition Number | 11 | Repetition number on the reported level, i.e. level 4.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2).) | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +Note 2. The IE J on level 3 cannot be included in the *Message Structure IE* since they have no criticality of their own. + +Note 3. The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +### A.3.2 Example 2 + +![Diagram of a received SABP message structure showing four levels. Level 1 (top) has A, B, C, D. Level 2 has E (under B) and K (under C, with sub-instances 1, 2, 3). Level 3 has F (dashed), H, G, J (dashed), L (dashed, grey). Level 4 has seven G boxes. Arrows indicate inclusion in Message Structure IE (C, K) and Information Element Criticality Diagnostics IE (K, L).](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- IE ID IE* +- Repetition Number IE* + +Diagram of a received SABP message structure showing four levels. Level 1 (top) has A, B, C, D. Level 2 has E (under B) and K (under C, with sub-instances 1, 2, 3). Level 3 has F (dashed), H, G, J (dashed), L (dashed, grey). Level 4 has seven G boxes. Arrows indicate inclusion in Message Structure IE (C, K) and Information Element Criticality Diagnostics IE (K, L). + +**Figure A.3: Example of a received SABP message containing a not comprehended IE** + +If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure A.3, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows: + +| IE name | Value | Comment | +|--------------------------------------------|-------------------|---------------------------------------------------------------------| +| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 2. | +| IE ID | id-K | IE ID from the reported level, i.e. level 2. | +| Repetition Number | 3 | Repetition number on the reported level, i.e. level 2. | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-C | IE ID from the lowest level above the reported level, i.e. level 1. | + +Note 4. The IE L on level 3 cannot be reported individually included in the *Message Structure IE* since it has no criticality of its own. + +### A.3.3 Example 3 + +![Diagram of a received SABP message structure showing four levels of Information Elements (IEs). Level 1 contains A, B, C, D. Level 2 contains E (with 4 repetitions) and K. Level 3 contains F, H (with 2 repetitions), G, J, L. Level 4 contains multiple instances of G. Arrows indicate nesting and repetition. One instance of G in H is highlighted in grey. Annotations point to 'Message Structure IE' and 'Information Element Criticality Diagnostics IE'.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- IE ID IE* +- Repetition Number IE* + +Diagram of a received SABP message structure showing four levels of Information Elements (IEs). Level 1 contains A, B, C, D. Level 2 contains E (with 4 repetitions) and K. Level 3 contains F, H (with 2 repetitions), G, J, L. Level 4 contains multiple instances of G. Arrows indicate nesting and repetition. One instance of G in H is highlighted in grey. Annotations point to 'Message Structure IE' and 'Information Element Criticality Diagnostics IE'. + +**Figure A.4: Example of a received SABP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure A.4, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows: + +| IE name | Value | Comment | +|----------------------------------------------------|-------------------|---------------------------------------------------------------------------------| +| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 4. | +| IE ID | id-G | IE ID from the reported level, i.e. level 4. | +| Repetition Number | 2 | Repetition number on the reported level, i.e. level 4. | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from level 2. | +| >Repetition Number | 3 | Repetition number from level 2. | +| Message Structure, third repetition | | | +| >IE ID | id-H | IE ID from the lowest level above the reported level, i.e. level 3. | +| >Repetition Number | 1 | Repetition number from the lowest level above the reported level, i.e. level 3. | + +Note 5. The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3). + +### A.3.4 Example 4 + +![Diagram of a received SABP message structure showing four levels of Information Elements (IEs). Level 1 contains A, B, C, D. Level 2 contains E (with 4 repetitions) and K. Level 3 contains F, H, G (grey, 5th repetition), J, L. Level 4 contains multiple instances of G with repetition numbers. Arrows indicate inclusion in Message Structure IE and Information Element Criticality Diagnostics IE.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- a) *IE ID IE* +- b) *Repetition Number IE* + +Diagram of a received SABP message structure showing four levels of Information Elements (IEs). Level 1 contains A, B, C, D. Level 2 contains E (with 4 repetitions) and K. Level 3 contains F, H, G (grey, 5th repetition), J, L. Level 4 contains multiple instances of G with repetition numbers. Arrows indicate inclusion in Message Structure IE and Information Element Criticality Diagnostics IE. + +**Figure A.5: Example of a received SABP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure A.5, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows: + +| IE name | Value | Comment | +|----------------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 3. | +| IE ID | id-G | IE ID from the reported level, i.e. level 3. | +| Repetition Number | 5 | Repetition number on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2).) | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +Note 6. The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +### A.3.5 Example 5 + +![Diagram of a received SABP message structure showing levels 1 to 4. Level 1 contains A, B, C, D. Level 2 contains E (with 4 instances) and K. Level 3 contains F, H, G (grey), J, L. Level 4 contains multiple instances of G. Arrows indicate relationships and include notes about Message Structure IE and Information Element Criticality Diagnostics IE.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- IE ID IE* +- Repetition Number IE* + +Diagram of a received SABP message structure showing levels 1 to 4. Level 1 contains A, B, C, D. Level 2 contains E (with 4 instances) and K. Level 3 contains F, H, G (grey), J, L. Level 4 contains multiple instances of G. Arrows indicate relationships and include notes about Message Structure IE and Information Element Criticality Diagnostics IE. + +**Figure A.6: Example of a received SABP message with a missing IE** + +If the instance marked as grey in the IE G in the IE E shown in the figure A.6, is missing this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as follows: + +| IE name | Value | Comment | +|----------------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 3. | +| IE ID | id-G | IE ID from the reported level, i.e. level 3. | +| Repetition Number | 4 | Repetition number up to the missing IE on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence.) | +| Type of Error | missing | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +Note 7. The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +## A.4 ASN.1 of EXAMPLE MESSAGE + +``` + +ExampleMessage ::= SEQUENCE { + ProtocolIEs ProtocolIE-Container {{ExampleMessage-IEs}}, + ProtocolExtensions ProtocolExtensionContainer {{ExampleMessage-Extensions}} OPTIONAL, + ... +} + +ExampleMessage-IEs SABP-PROTOCOL-IES ::= { + { ID id-A CRITICALITY reject TYPE A PRESENCE mandatory} | + { ID id-B CRITICALITY reject TYPE B PRESENCE mandatory} | + { ID id-C CRITICALITY reject TYPE C PRESENCE mandatory} | + { ID id-D CRITICALITY reject TYPE D PRESENCE mandatory} , + ... +} + +B ::= SEQUENCE { + e E-List, + iE-Extensions ProtocolExtensionContainer { {B-ExtIEs} } OPTIONAL, + ... +} + +B-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Container { {E-IEs} } + +E-IEs SABP-PROTOCOL-IES ::= { + { ID id-E CRITICALITY ignore TYPE E PRESENCE mandatory }, + ... +} + +E ::= SEQUENCE { + f F-List, + h H-List, + g G-List1, + j J-List, + iE-Extensions ProtocolExtensionContainer { {E-ExtIEs} } OPTIONAL, + ... +} + +E-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +F-List ::= SEQUENCE (SIZE (1..maxF)) OF F + +F ::= SEQUENCE { + g G-List2 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {F-ExtIEs} } OPTIONAL, + ... +} + +F-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G2-IEs} } + +G2-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory }, + ... +} + +H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Container { {H-IEs} } + +H-IEs SABP-PROTOCOL-IES ::= { + { ID id-H CRITICALITY ignore TYPE H PRESENCE mandatory }, + ... +} + +H ::= SEQUENCE { + g G-List3 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +H-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G3-IEs} } + +G3-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY notify TYPE G PRESENCE mandatory }, + ... +} + +G-List1 ::= ProtocolIE-Container { {G1-IEs} } + +G1-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory }, + ... +} + +J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J + +J ::= SEQUENCE { + g G-List4 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {J-ExtIEs} } OPTIONAL, + ... +} + +J-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G4-IEs} } + +G4-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory }, + ... +} + +C ::= SEQUENCE { + k K-List, + iE-Extensions ProtocolExtensionContainer { {C-ExtIEs} } OPTIONAL, + ... +} + +C-ExtIEsA -PROTOCOL-EXTENSION ::= { + ... +} + +K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Container { {K-IEs} } + +K-IEs SABP-PROTOCOL-IES ::= { + { ID id-K CRITICALITY notify TYPE K PRESENCE mandatory }, + ... +} + +K ::= SEQUENCE { + l L-List, + iE-Extensions ProtocolExtensionContainer { {K-ExtIEs} } OPTIONAL, + ... +} + +K-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +L-List ::= SEQUENCE (SIZE (1..maxL)) OF L + +L ::= SEQUENCE { + m M OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {L-ExtIEs} } OPTIONAL, + ... +} + +L-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +ExampleMessage-Extensions SABP-PROTOCOL-EXTENSION ::= { + +``` + +} ... + +# Annex B (informative): Change history + +| Change history | | | | | | +|----------------|---------|----------------------------------------------------------------------------------|-----------|-------------|--------------------------------------------------------| +| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment | +| RAN_07 | - | - | - | 3.0.0 | Approved at TSG RAN #7 and placed under Change Control | +| RAN_08 | 3.0.0 | - | RP-000239 | 3.1.0 | Approved at TSG RAN #8 | +| RAN_09 | 3.1.0 | 011
012
014
015
016
017
018
019
020
021
022
023 | RP-000377 | 3.2.0 | Approved at TSG RAN #9 | +| RAN_10 | 3.2.0 | 024
025
026
027
028
029 | RP-000616 | 3.3.0 | Approved at TSG RAN #10 | +| RAN_11 | 3.3.0 | 030
031
032
033
034 | RP-010114 | 3.4.0 | Approved at TSG RAN #11 | + +| Change history | | | | | | | | | +|----------------|-------|-----------|---------------------------------------------------------|-----|------------------------------------------------------------------------------------|-------|-------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| March 01 | 11 | - | - | | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | | +| 06/2001 | 12 | RP-010377 | 036,0
38,04
0,042
,043,
044,0
48,05
0 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 | | +| 09/2001 | 13 | RP-010582 | 051 | 1 | SABP criticality | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 052 | 1 | Correction to the Error handling of the ERROR INDICATION message | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 056 | 1 | Error handling of the Erroneously Present Conditional IEs | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 058 | 1 | Clarification of chapter 10 | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 060 | 1 | SABP General Corrections | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 062 | 2 | Clarification of the usage of the Number of Broadcasts Requested IE | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 064 | 1 | Clarification of the usage of the SABP Reset Procedure | 4.1.0 | 4.2.0 | | +| 09/2001 | 13 | RP-010582 | 066 | 2 | Clarification of the usage of the Service Areas List IE within the Reset Procedure | 4.1.0 | 4.2.0 | | +| 12/2001 | 14 | RP-010852 | 068 | 1 | SAI Clarification | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 070 | | Bitstrings ordering | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 072 | | Procedure Code Criticality in Error Indication | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 074 | 2 | Addition of amendment to clarify the PER encoding of bitstrings | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 076 | | Section 9.2.0 missing | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 078 | 2 | CR on 25.419 (R4) Usage of "Number of Broadcasts Completed List" IE | 4.2.0 | 4.3.0 | | +| 12/2001 | 14 | RP-010852 | 080 | | Correction the Clause 10 Error Handling | 4.2.0 | 4.3.0 | | +| 03/2002 | 15 | RP-020167 | 082 | | Correction of the value Default in Category IE | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 084 | 1 | Correction of the wording of maximum value | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 086 | | Service expected from the transport layer | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 088 | 1 | ASN.1 take precedence if contradiction between ASN.1 and tabular | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 090 | 1 | Mismatch the type of some IE between 24.419 and 25.324 | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 092 | | Correction of the usage of Write-Replace Failure message | 4.3.0 | 4.4.0 | | +| 03/2002 | 15 | RP-020167 | 094 | | Error Indication correction | 4.3.0 | 4.4.0 | | + +| | | | | | | | | +|---------|-------|-----------|-----|---|-------------------------------------------------------------|--------|--------| +| 03/2002 | 15 | - | - | | Approved at TSG RAN #15 and placed under Change Control | - | 5.0.0 | +| 06/2002 | 16 | RP-020404 | 097 | | Criticality Information Decoding Failure Handling | 5.0.0 | 5.1.0 | +| 06/2002 | 16 | RP-020404 | 100 | 1 | Clarification for the usage of the cause value | 5.0.0 | 5.1.0 | +| 06/2002 | 16 | RP-020404 | 103 | | SABP: WRITE-REPLACE Procedure Clarification | 5.0.0 | 5.1.0 | +| 09/2002 | 17 | RP-020602 | 106 | 1 | Correction to ASN.1 coding: criticality information missing | 5.1.0 | 5.2.0 | +| 03/2003 | 19 | RP-030057 | 108 | 1 | Correction of Write and Replace functions | 5.2.0 | 5.3.0 | +| 06/2003 | 20 | RP-030315 | 112 | 1 | Correction of Kill Unsuccessful Outcome | 5.3.0 | 5.4.0 | +| 06/2003 | 20 | RP-030326 | 117 | | Correction of Failure message used for logical errors | 5.3.0 | 5.4.0 | +| 09/2003 | 21 | RP-030445 | 118 | | Alignment of title and sub-clause text of chapter 10.3.4.2 | 5.4.0 | 5.5.0 | +| 09/2003 | 21 | RP-030446 | 119 | 1 | Removal of the note in chapter 10 | 5.4.0 | 5.5.0 | +| 09/2003 | 21 | RP-030438 | 124 | 2 | Correction of number of broadcast to be reported | 5.4.0 | 5.5.0 | +| 12/2003 | 22 | RP-030673 | 130 | | Correction of finite number of broadcast | 5.5.0 | 5.6.0 | +| 12/2003 | 22 | - | - | - | Introduction of Release 6 specification | 5.6.0 | 6.0.0 | +| 03/2004 | 23 | RP-040063 | 132 | 1 | Correction to 25.419 for Broadcast Message Content IE | 6.0.0 | 6.1.0 | +| 12/2004 | 26 | RP-040441 | 133 | | outdated ITU-T reference | 6.1.0 | 6.2.0 | +| 03/2006 | 31 | - | - | - | Introduction of Release 7 specification | 6.2.0 | 7.0.0 | +| 12/2008 | 42 | RP-080857 | 135 | 2 | CR on ETWS support in UTRAN SABP | 7.0.0 | 8.0.0 | +| 12/2008 | 42 | RP-080857 | 136 | 1 | CR on Security Information for Primary Notification | 7.0.0 | 8.0.0 | +| 12/2009 | 46 | RP-091179 | 138 | 1 | Correction of ETWS for Rel8 HSPA | 8.0.0 | 8.1.0 | +| 12/2009 | - | - | - | - | Creation of Rel-9 version based on v8.1.0 | 8.1.0 | 9.0.0 | +| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.0 | 9.0.1 | +| 03/2011 | | | | | Creation of Rel-10 version based on v9.0.1 | 9.0.1 | 10.0.0 | +| 06/2011 | 52 | RP-110685 | 140 | - | Removal of unused references | 10.0.0 | 10.1.0 | +| 09/2011 | 53 | RP-111223 | 141 | 1 | Correction of a typo in ASN.1 code | 10.1.0 | 10.2.0 | +| 09/2012 | | | | | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 03/2013 | 59 | RP-130212 | 151 | 2 | Invalidation of ETWS with security feature | 11.0.0 | 11.1.0 | +| 09/2014 | | | | | Update to Rel-12 version (MCC) | 11.1.0 | 12.0.0 | +| 01/2014 | 66 | RP-142094 | 152 | 3 | Adding a new reference of TS 25.921 | 12.0.0 | 12.1.0 | +| 12/2015 | | | | | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25420/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/25_series/25420/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcd5ef924073e495169bd5a3a4ccfc4c2d9a42d2 --- /dev/null +++ b/marked/Rel-16/25_series/25420/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b733cfdbc50e27ad6cd6d4fa1ec6712337325c2da92bc620f6e1ef5513c6f30e +size 44578 diff --git a/marked/Rel-16/25_series/25420/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/Rel-16/25_series/25420/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb3a6b40a390fde1d401eafdf35413b7dba82cf8 --- /dev/null +++ b/marked/Rel-16/25_series/25420/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df09b8eaa8bb1c494330f8a303c5622fe727f89f34d314217f2fb78e7c43c203 +size 100871 diff --git a/marked/Rel-16/25_series/25420/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg b/marked/Rel-16/25_series/25420/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30d12e5a2ac2cd3f4dff508e7e7c6eb1ed596de2 --- /dev/null +++ b/marked/Rel-16/25_series/25420/a7835229df7a34816e1d35b5bbbc8c9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56e935b765b70ccfe5343d2f6417a85fb103f32797e85916debdca613586857f +size 119205 diff --git a/marked/Rel-16/25_series/25420/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-16/25_series/25420/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fdf5c1e9bbe208e47f6c57213d787cdaddebe41 --- /dev/null +++ b/marked/Rel-16/25_series/25420/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e8b2bea243772209d54e8150166d9144b2e0e10ed8b52a0379dfd351c27eda0 +size 23604 diff --git a/marked/Rel-16/25_series/25420/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25420/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3168a8acdef914fda6acd9789744678983c26977 --- /dev/null +++ b/marked/Rel-16/25_series/25420/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e1f106d6bce122a5946237f790de12d1bde635009c8435b2c49c07c704a3518 +size 108713 diff --git a/marked/Rel-16/25_series/25420/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/25_series/25420/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48ea6cdc1ce168d624692a12579e453f9e22cba5 --- /dev/null +++ b/marked/Rel-16/25_series/25420/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58819222f0a8182eb685dfa9ac015e237bb11f31854ae4097b399718ed59f881 +size 42002 diff --git a/marked/Rel-16/25_series/25420/raw.md b/marked/Rel-16/25_series/25420/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b040616ac3b6fbd002db1a637f62ac8d9dd99159 --- /dev/null +++ b/marked/Rel-16/25_series/25420/raw.md @@ -0,0 +1,891 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 3.2 Specification Notations ..... | 8 | +| 4 General Aspects ..... | 9 | +| 4.1 Introduction ..... | 9 | +| 4.2 Iur Interface General Principles ..... | 9 | +| 4.3 Iur Interface Specification Objectives..... | 9 | +| 4.3.1 General ..... | 9 | +| 4.3.2 Addressing of RNSs over the Iur Interface ..... | 9 | +| 4.4 Iur Interface Capabilities..... | 10 | +| 4.4.1 Radio application related signalling ..... | 10 | +| 4.4.2 Iub/Iur DCH data streams..... | 10 | +| 4.4.3 Iur RACH data streams ..... | 10 | +| 4.4.4 Iur DSCH data streams [TDD]..... | 10 | +| 4.4.5 Iur USCH data streams [TDD]..... | 10 | +| 4.4.6 Iur FACH data streams..... | 10 | +| 4.4.7 Iur HS-DSCH data streams ..... | 10 | +| 4.4.8 Iub/Iur E-DCH data streams..... | 10 | +| 4.4.9 Iur IuUP data streams for CS data forwarding ..... | 11 | +| 4.5 Iur Interface Characteristics ..... | 11 | +| 4.5.1 Uses of SCCP ..... | 11 | +| 4.5.1.1 General..... | 11 | +| 4.5.1.2 SCCP connection establishment ..... | 11 | +| 4.5.1.3 Establishment procedure initiated from the SRNC..... | 11 | +| 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information..... | 12 | +| 4.5.1.4 SCCP connection release..... | 13 | +| 4.5.1.5 General SCCP Abnormal Conditions ..... | 13 | +| 4.5.1.5.1 SCCP bearer failure..... | 13 | +| 4.5.1.5.2 SCCP connection failure ..... | 13 | +| 4.5.2 SCCP Addressing Scheme ..... | 14 | +| 4.5.2.1 General..... | 14 | +| 5 Functions of the I ur Interface Protocols..... | 14 | +| 5.1 Functional List..... | 14 | +| 5.2 Functional Split over Iur ..... | 15 | +| 5.2.1 Combining/Splitting ..... | 15 | +| 5.2.2 Control of Combining/Splitting Topology ..... | 15 | +| 5.2.3 Handling of DRNS Hardware Resources ..... | 15 | +| 5.2.4 Allocation of Physical Channels ..... | 15 | +| 5.2.5 UpLink Power Control ..... | 15 | +| 5.2.6 Down-Link Power Control ..... | 15 | +| 5.2.7 Admission Control..... | 16 | +| 5.2.8 Radio Protocol Functional Split ..... | 16 | +| 5.2.9 MBMS Bearer Type Control..... | 16 | +| 5.2.10 MBSFN MCCH Information Control ..... | 16 | +| 6 I ur Interface Protocols..... | 16 | +| 6.1 General ..... | 16 | +| 6.2 Radio Signalling Protocols..... | 17 | +| 6.2.1 RNSAP Protocol..... | 17 | +| 6.3 User Plane Frame Protocols ..... | 17 | +| 6.3.1 Iub/Iur DCH Frame Protocol..... | 17 | + +| | | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------|----| +| 6.3.2 | Iur DSCH Frame Protocol [TDD] ..... | 18 | +| 6.3.3 | Iur USCH Frame Protocol [TDD] ..... | 18 | +| 6.3.4 | Iur RACH Frame Protocol..... | 18 | +| 6.3.5 | Iur FACH Frame Protocol ..... | 18 | +| 6.3.6 | Iur HS-DSCH Frame Protocol..... | 18 | +| 6.3.7 | Iur E-DCH Frame Protocol ..... | 19 | +| 6.4 | Mapping of Frame Protocols onto transport bearers ..... | 19 | +| 7 | DRNS logical Model over I ur ..... | 19 | +| 7.1 | Overview ..... | 19 | +| 7.2 | Logical Model Elements ..... | 20 | +| 7.2.1 | Radio Link ..... | 20 | +| 7.2.2 | Cell ..... | 20 | +| 7.2.3 | Iur DCH Data Port..... | 20 | +| 7.2.4 | Iur DSCH Data Port [TDD]..... | 21 | +| 7.2.5 | Iur USCH Data Port [TDD]..... | 21 | +| 7.2.6 | Iur RACH/FACH Data Port ..... | 21 | +| 7.2.7 | Iur Control Port..... | 21 | +| 7.2.8 | Iur HS-DSCH Data Port ..... | 21 | +| 7.2.9 | Iur E-DCH Data Port ..... | 21 | +| 8 | I ur Interface Protocol Structure..... | 21 | +| 9 | Other I ur Interface Specifications ..... | 22 | +| 9.1 | UTRAN Iur Interface: Layer 1 (TS 25.421) ..... | 22 | +| 9.2 | UTRAN Iur Interface: Signalling Transport (TS 25.422)..... | 22 | +| 9.3 | UTRAN Iur Interface: RNSAP Specification (TS 25.423)..... | 22 | +| 9.4 | UTRAN Iur Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424)..... | 22 | +| 9.5 | UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425) ..... | 22 | +| 9.6 | UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426)..... | 23 | +| 9.7 | UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427) ..... | 23 | +| 9.8 | Summary of UTRAN Iur Interface Technical Specifications..... | 23 | +| Annex A (informative): | Change History..... | 24 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the TSG RAN TS 25.42x series of UMTS Technical Specifications that define the Iur Interface. It is a logical interface for the interconnection of two Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.427: "UTRAN Iub/Iur Interface User Plane Protocol for DCH Data Streams". +- [2] 3GPP TS 25.425: "UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams". +- [3] 3GPP TS 25.421: "UTRAN Iur Interface: Layer 1". +- [4] 3GPP TS 25.422: "UTRAN Iur Interface: Signalling Transport". +- [5] 3GPP TS 25.423: "UTRAN Iur Interface: Radio Network Subsystem Application Part (RNSAP) signalling". +- [6] 3GPP TS 25.424: "UTRAN Iur Interface: Data Transport & Transport Signalling ". +- [7] Void +- [8] 3GPP TS 25.426: "UTRAN Iur & Iub Interface: Data Transport & Transport Signalling for DCH Data Streams". +- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [14] Void +- [15] Void +- [16] Void +- [17] 3GPP TR 43.930: "Iur-g interface; Stage 2". +- [18] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [19] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2". +- [20] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +None. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|------------------------------------------------------------------| +| AAL2 | ATM Adaptation Layer type 2 | +| AAL5 | ATM Adaptation Layer type 5 | +| ALCAP | Access Link Control Application Part | +| ATM | Asynchronous Transfer Mode | +| BSS | Base Station Subsystem | +| CRNC | Controlling RNC | +| CTP | Common Transport Protocol | +| DCH | Dedicated Transport Channel | +| DL | Downlink | +| DPCH | Dedicated Physical Channel | +| DRNC | Drift Radio Network Controller | +| DRNS | Drift Radio Network Subsystem | +| DSCH | Downlink Shared Channel | +| E-DCH | Enhanced Dedicated Channel | +| EDGE | Enhanced Data rates for GSM Evolution | +| FACH | Forward Access Channel | +| F-DPCH | Fractional DPCH | +| FFS | For Further Study | +| GERAN | GSM/EDGE Radio Access Network | +| GSM | Global System for Mobile communications | +| GT | Global Title | +| HARQ | Hybrid Automatic Repeat Request | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MRNC | MBMS Master RNC | +| MTP3-B | Message Transfer Part level 3 (for Q.2140) | +| PLMN | Public Land Mobile Network | +| PTM | Point To Multipoint | +| PTP | Point To Point | +| QoS | Quality of Service | +| RACH | Random Access Channel | +| RF | Radio Frequency | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RNSAP | Radio Network Subsystem Application Part | +| RRC | Radio Resource Control | +| SCCP | Signalling Connection Control Part | +| SPC | Signalling Point Code | +| SRNC | Serving Radio Network Controller | +| SRNS | Serving Radio Network Subsystem | +| SS7 | Signalling System N° 7 | +| SSCF-NNI | Service Specific Co-ordination Function – Network Node Interface | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSN | Sub-System Number | +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UL | Up-link | + +| | | +|-------|-------------------------------------------| +| UMTS | Universal Mobile Telecommunication System | +| URA | UTRAN Registration Area | +| USCH | Uplink Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.2 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD] | This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. | +| [TDD] | This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. | +| [3.84Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. | +| [1.28Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. | +| [7.68Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. | +| [FDD - ...] | This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. | +| [TDD - ...] | This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. | +| [3.84Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. | +| [1.28Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. | +| [7.68Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. | +| Procedure | When referring to a procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. RNSAP Basic Mobility Procedures. | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message | When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | +| Frame | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH data frame. | + +# --- 4 General Aspects + +## 4.1 Introduction + +The logical connection that exists between any two RNCs within the UTRAN is referred to as the Iur interface. + +## 4.2 Iur Interface General Principles + +The general principles for the specification of the Iur interface are as follows: + +- The Iur interface should be open; +- The Iur interface shall support the exchange of signalling information between two RNCs, in addition the interface may need to support one or more Iur data streams; +- From a logical standpoint, the Iur is a point-to-point interface between two RNCs within the UTRAN. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two RNCs. + +## 4.3 Iur Interface Specification Objectives + +### 4.3.1 General + +The Iur interface specifications shall facilitate the following: + +- inter-connection of RNCs supplied by different manufacturers; +- support of continuation between RNSs of the UTRAN services offered via the Iu interface; +- separation of Iur interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology. + +### 4.3.2 Addressing of RNSs over the Iur Interface + +- For an RRC connection using a dedicated channel or for a UE using F-DPCH in the downlink, the Iur standard shall allow the addition / deletion of radio links supported by cells belonging to any RNS within the PLMN. +- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing a signalling bearer over Iur. +- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing user data bearers for Iur data streams. + +RNSAP shall allow different kinds of addressing schemes to be used for the signalling bearer. + +## 4.4 Iur Interface Capabilities + +### 4.4.1 Radio application related signalling + +The Iur interface provides capability to support radio interface mobility between RNSs, of UEs having a connection with UTRAN. This capability includes the support of handover, radio resource handling, MBMS handling and synchronisation between RNSs. + +### 4.4.2 Iub/Iur DCH data streams + +The Iur interface provides the means for transport of uplink and downlink Iub/Iur DCH frames carrying user data and control information between SRNC and Node B (DRNS), via the DRNC. + +In the UTRAN, one DCH data stream always corresponds to a bi-directional transport channel. Although the TFS is configured separately for each DCH direction and a DCH could be configured with e.g. only a zero-bit transport format in one direction, the DCH is always treated as a bi-directional transport channel in the UTRAN. As a result, two uni-directional Uu DCH transport channels with opposite directions can be mapped to either one or two DCH transport channels in the UTRAN. + +### 4.4.3 Iur RACH data streams + +The Iur interface provides the means for transport of uplink RACH transport frames between DRNC and SRNC. + +### 4.4.4 Iur DSCH data streams [TDD] + +An Iur DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE. A UE may have multiple Iur DSCH data streams. + +The Iur interface provides a means of transporting down link MAC-c/sh SDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC. + +### 4.4.5 Iur USCH data streams [TDD] + +An Iur USCH data stream corresponds to the data carried on one USCH transport channel for one UE. A UE may have multiple Iur USCH data streams. + +### 4.4.6 Iur FACH data streams + +The Iur interface provides the means for transport of downlink FACH transport frames between SRNC and DRNC. + +### 4.4.7 Iur HS-DSCH data streams + +An Iur HS-DSCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple Iur HS-DSCH data streams. + +The Iur interface provides a means of transporting down link MAC-d PDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC. + +### 4.4.8 Iub/Iur E-DCH data streams + +The Iur interface provides the means for transport of Iub/Iur E-DCH frames carrying user data between NodeB (DRNS) and SRNC, via the DRNC. + +An Iur E-DCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple E-DCH data streams. In addition, the interface provides the following: + +- A means for the Node B to indicate the number of HARQ retransmissions to the SRNC ITU-T Rec. Q.713 [11]; +- A means to indicate to the SRNC, for the purposes of re-ordering, the CFN and Subframe Number that have been added by the Node B in the DRNSTS 25.427 [1]. + +### 4.4.9 Iur IuUP data streams for CS data forwarding + +In order to support data forwarding for CS services like during enhanced relocation, Iu UP protocol is used according to the procedures described in TS 25.415 [20] on the Iur link for forwarding the CS data from source RNC to target RNC. It is assumed that the Target RNC supports the same Iu UP mode version as the one used between the source SRNC and the CN. + +## 4.5 Iur Interface Characteristics + +### 4.5.1 Uses of SCCP + +#### 4.5.1.1 General + +The SCCP (ITU-T Rec. Q.711 [9] / ITU-T Rec. Q.712 [10] / ITU-T Rec. Q.713 [11] / ITU-T Rec. Q.714 [12]) is used to support signalling messages between two RNCs. One user function of the SCCP, called Radio Network Subsystem Application Part (RNSAP), is defined. The RNSAP uses one signalling connection per DRNC and UE where a UE is having one or more active radio links for the transfer of layer 3 messages. RNSAP also uses one signalling connection per RNC providing common measurements and information to a particular RNC (i.e. if measurements and information are transferred in both directions between a pair of RNCs, then two SCCP connections are used). + +Both connectionless and connection-oriented procedures are used to support the RNSAP. TS 25.423 [6] explains whether connection oriented or connectionless services should be used for a layer 3 procedure. + +The following subclauses describe the use of SCCP connections for RNSAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection establishment procedures initiated from SRNC. Subclause 4.5.1.4 describes the connection release procedures. Subclause 4.5.1.5 describes abnormal conditions. + +#### 4.5.1.2 SCCP connection establishment + +A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between two RNCs, and no SCCP connection exists between the two RNCs involved, for the concerned UE. + +In this case, the SCCP connection is established by the SRNC. + +A new SCCP connection is established when a request for common measurements or information is made towards a particular RNC and no SCCP connection for common measurements and information transfer has been established from the RNC requesting the measurements or information towards the one providing the measurements or the information. + +In this case, the SCCP connection is established by the RNC requesting the measurements or the information. + +#### 4.5.1.3 Establishment procedure initiated from the SRNC + +The SCCP signalling connection establishment is initiated, by the SRNC, when the SRNC needs to request dedicated resources, i.e. a DCH, from a DRNC. + +##### Initiation + +- The SRNC sends the SCCP: CR message to the DRNC. The RADIO LINK SETUP REQUEST message or the ENHANCED RELOCATION REQUEST may be included in the user data field of an SCCP Connection Request message. + +##### Termination + +1. Successful outcome: + - The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the SRNC. +2. Unsuccessful outcome: + - If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the SRNC. This message may optionally contain a connection oriented RNSAP message. + +For more information on how the RNSAP procedures Radio Link Setup and Enhanced Relocation are handled, please see the procedures Radio Link Setup and Enhanced Relocation in TS 25.423 [5]. + +![Sequence diagram showing the setting-up of an SCCP Signalling Connection between SRNC and DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant DRNC + Note right of SRNC: CR {SSN=RNSAP, a1=x, RNSAP message or no user data } + SRNC->>DRNC: CR {SSN=RNSAP, a1=x, RNSAP message or no user data } + Note left of DRNC: CC {a1=y, a2=x, RNSAP message or no user data} + DRNC-->>SRNC: CC {a1=y, a2=x, RNSAP message or no user data} + Note left of DRNC: OR + Note left of DRNC: CREF{a2=x, RNSAP message or no user data} + DRNC-->>SRNC: CREF{a2=x, RNSAP message or no user data} + +``` + +| | | +|----|------------------------------------------| +| a1 | = source local reference, | +| a2 | = destination local reference | +| x | = SCCP connection reference at the SRNC, | +| y | = SCCP connection reference at the DRNC. | + +Sequence diagram showing the setting-up of an SCCP Signalling Connection between SRNC and DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC. + +**Figure 1: Setting-up of SCCP Signalling Connection** + +#### 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information + +The SCCP signalling connection establishment is initiated, by an RNC, when the RNC needs to request common measurements or provision of information from another RNC and there is no signalling bearer existing for this purpose. For the description below, the RNC requesting the measurements or the information is called RNC1 and the RNC being requested to provide the measurements or the information is called RNC2. + +##### Initiation + +- The RNC1 sends the SCCP: CR message to the RNC2. The COMMON MEASUREMENT INITIATION REQUEST or the INFORMATION EXCHANGE INITIATION REQUEST message shall be included in the user data field of the SCCP Connection Request message. + +##### Termination + +1. Successful outcome: + - The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the RNC1. +2. Unsuccessful outcome: + - If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the RNC1. This message may optionally contain a connection oriented RNSAP message. + +RNSAP Common Measurement Initiation and Information Exchange Initiation procedures are described in TS 25.423 [5]. + +![Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant RNC1 + participant RNC2 + Note right of RNC1: a1 = source local reference, +a2 = destination local reference +x = SCCP connection reference at the SRNC, +y = SCCP connection reference at the DRNC. + RNC1->>RNC2: CR {SSN=RNSAP, a1=x, RNSAP message } + RNC2-->>RNC1: CC {a1=y, a2=x, RNSAP message or no user data} + Note over RNC1, RNC2: OR + RNC2-->>RNC1: CREF {a2=x, RNSAP message or no user data} + +``` + +Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC. + +**Figure 1a: Setting-up of SCCP Signalling Connection** + +#### 4.5.1.4 SCCP connection release + +An SCCP connection related to a specific UE is released in all normal release cases when the RNC which established the SCCP connection realises that a given signalling connection is no longer required. + +The RNC which established SCCP connection sends an SCCP Released message. + +The procedure may be initiated at the SRNC side and the DRNC side in any abnormal release case. + +An SCCP connection used for common measurements and information exchanges is released in all normal release cases when the RNC1 (see 4.5.1.3A) determines that a given signalling connection is no longer required. The RNC1 sends an SCCP Released message. + +In case an SCCP Release message is received after the successful completion of an SRNC Relocation procedure while dedicated resources are still allocated the new SRNC shall only release the SCCP connection and the Iur related dedicated resource. + +The procedure may be initiated at the RNC 1 side and the RNC 2 side in any abnormal release case. + +#### 4.5.1.5 General SCCP Abnormal Conditions + +##### 4.5.1.5.1 SCCP bearer failure + +If a user-out-of-service information or signalling-point-inaccessible information is received by the RNSAP, no new attempt to establish SCCP connections or to send SCCP Connectionless messages towards the affected signalling point (indicated by the affected signalling point code) will be started until the corresponding user-in-service information or signalling-point-accessible information is received. + +When a user-out-of-service information or signalling-point-inaccessible is received by an RNC, an optional timer may be started. When the timer expires, the RNC shall take actions as described in TS 25.423 [5] Annex D.1.1. When the user-in-service or signalling-point-accessible is received, the timer is stopped. + +##### 4.5.1.5.2 SCCP connection failure + +If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RNSAP procedures are being performed or while a dedicated resource is still allocated, this shall be handled by the RNC as described in TS 25.423 [5] Annex D.1.2. + +### 4.5.2 SCCP Addressing Scheme + +#### 4.5.2.1 General + +RNSAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing schemes to use for the SCCP is an operator matter. + +When GT addressing is utilised, the following settings shall be used: + +- SSN Indicator = 1 (RNSAP SSN as defined in TS 23.003 [13] shall always be included); +- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation Type = 0000 0000 (not used); +- Numbering Plan = 0001 (E.163/4); +- Nature of Address Indicator = 000 0100 (International Significant Number); +- Encoding Scheme = 0001 or 0010 (BCD, odd or even); +- Routing indicator = 0 or 1 (route on GT or PC/SSN). + +When used, the GT shall be the E.164 address of the relevant node. + +# --- 5 Functions of the Iur Interface Protocols + +## 5.1 Functional List + +The list of functions on the Iur interface is the following: + +1. Transport Network Management. +2. Traffic management of Common Transport Channels: + - Preparation of Common Transport Channel resources; + - Paging. +3. Traffic Management of Dedicated Transport Channels: + - Radio Link Setup/ Addition/ Deletion; + - Measurement Reporting. +4. [TDD - Traffic Management of Downlink Shared Transport Channels and Uplink Shared Transport Channels]: + - Radio Link Setup/ Addition/ Deletion; + - Capacity Allocation. +5. Measurement reporting for common and dedicated measurement objects. +6. Information exchange of UTRAN, GERAN and MBMS bearer service information. +7. Tracing of various events related to a UE. +8. MBMS related functions + - MBMS UE Linking/De-linking + - MBMS URA linking/De-linking + - MBMS Channel type Indication + - MBSFN MCCH Information Control + +## 5.2 Functional Split over Iur + +### 5.2.1 Combining/Splitting + +DRNS may perform combining/splitting of data streams communicated via its cells. SRNS performs combining/splitting of Iur data streams received from/sent to DRNS(s), and data streams communicated via its own cells. + +The UL combining of information streams may be performed using any suitable algorithm, for example: + +- [FDD - based on maximum ratio algorithm (maximum ratio combining)]; +- [FDD - based on quality information associated to each TBS (selection-combining)]; +- [TDD - based on the presence/absence of the signal (selection)]. + +The internal DRNS handling of combining (respectively splitting) of Iub (respectively Iur) DCH frames is controlled by the DRNS. + +### 5.2.2 Control of Combining/Splitting Topology + +When requesting the addition of a new cell for a UE-UTRAN connection for DCH, the RNC of the SRNS (i.e. the SRNC) can explicitly request to the RNC of the DRNS (i.e. the DRNC) a new Iur data stream, in which case the combining and splitting function within the DRNS is not used for that cell. The SRNC can also explicitly request from the DRNC the use of the combining and splitting function inside the DRNS for that cell. Otherwise, the DRNS takes the decision whether combining and splitting function is used inside the DRNS for that cell i.e. whether a new Iur data stream shall be added or not. + +For E-DCH combining at the DRNC is not allowed. However, combining in NodeB of the DRNS is mandatory where applicable as described in TS 25.319 [19]. + +### 5.2.3 Handling of DRNS Hardware Resources + +Allocation and control of DRNS hardware resources, used for Iur data streams and radio interface transmission/reception in DRNS is performed by DRNS. + +### 5.2.4 Allocation of Physical Channels + +Allocation of physical channels in cells belonging to DRNS is performed in DRNS. + +### 5.2.5 UpLink Power Control + +This group of functions controls the level of the uplink transmitted power in order to minimise uplink interference and keep the quality of the connections. If the connection involves both a SRNS and a DRNS the function UL Outer Loop Power Control (located in the SRNC) sets the target quality for the UL Inner Loop Power Control function (located in Node B for DCH [FDD]). For E-DCH, the DRNS (NodeB) reports the number of HARQ retransmissions to SRNC as an input to the Outer Loop Power Control function. + +### 5.2.6 Down-Link Power Control + +This group of functions controls the level of the downlink transmitted power. In FDD it is also used to correct the downlink power drifting between several radio links. SRNC regularly (or under some algorithms) sends the target down link power reference based on the measurement report from UE. + +### 5.2.7 Admission Control + +Admission control in a DRNC is implicitly invoked during radio link setup/modify. + +Information on UL interference and DL power on cells controlled by the DRNC should be available across Iur. + +Additional information exchanges between admission control functions located in different RNCs are for further study. + +### 5.2.8 Radio Protocol Functional Split + +Iur supports the radio protocol functional split between SRNC and DRNC. + +### 5.2.9 MBMS Bearer Type Control + +MBMS Bearer type control is split between SRNC and DRNC. The CRNC is in control of an MBMS Bearer of PTM type. The MBMS bearer services activated by the UE are transferred over Iur from SRNC to DRNC. In case the CRNC is a DRNC for one or several UEs, it indicates the selected bearer type to SRNC but it is SRNC decision to set up or release MBMS bearers of PTP type for a given UE as described in TS 25.346 [18]. + +### 5.2.10 MBSFN MCCH Information Control + +In case MRNC is used, MBSFN MCCH Information Control function is split between MRNC and CRNC. The MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). The MRNC informs the CRNC of the MCCH configuration and schedule information to be used. The CRNC performs the MCCH configuration and sends the MCCH information accordingly. + +# 6 Iur Interface Protocols + +## 6.1 General + +There shall exist a clear separation between the Radio Network Layer and the Transport Layer. Therefore, the radio network signalling and Iur data streams are separated from the data transport resource and traffic handling as shown in Figure 2. Data transport resource and traffic handling is controlled by Transport Signalling. The Transport Signalling is carried by a Signalling Bearer over the Iur interface. + +![Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. In the Radio Network layer, there are two components: Radio Signalling Protocols and User Plane Framing Protocols. In the Transport layer, there are three components: Signalling Bearer, Transport Signalling, and Data Transport. Arrows indicate the flow: Radio Signalling Protocols connect to Signalling Bearer; User Plane Framing Protocols connect to Data Transport; Signalling Bearer connects to Transport Signalling; Transport Signalling connects to Data Transport.](df1d0e45191302de72176e4390224c16_img.jpg) + +``` + +graph TD + subgraph RNL [Radio Network layer] + RSP((Radio Signalling Protocols)) + UPFP((User Plane Framing Protocols)) + end + subgraph TL [Transport layer] + SB[Signalling Bearer] + TS[Transport Signalling] + DT[Data Transport] + end + RSP --> SB + UPFP --> DT + SB --> TS + TS --> DT + +``` + +Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. In the Radio Network layer, there are two components: Radio Signalling Protocols and User Plane Framing Protocols. In the Transport layer, there are three components: Signalling Bearer, Transport Signalling, and Data Transport. Arrows indicate the flow: Radio Signalling Protocols connect to Signalling Bearer; User Plane Framing Protocols connect to Data Transport; Signalling Bearer connects to Transport Signalling; Transport Signalling connects to Data Transport. + +Figure 2: Separation of Radio Network Protocols and transport over Iur + +## 6.2 Radio Signalling Protocols + +### 6.2.1 RNSAP Protocol + +The protocol responsible for providing signalling information across the Iur interface is called the Radio Network Subsystem Application Part (RNSAP). A subset of RNSAP is used over the Iur-g interface. + +The RNSAP is terminated by the two RNCs inter-connected via the Iur interface RNSAP Procedure Modules. In addition, the RNSAP is terminated by a RNC and a BSS supporting Iu mode inter-connected via the Iur-g interface (TR 43.930 [17]). For 1.28Mcps TDD, the RNSAP may be terminated by a RNC and a BSS supporting A/Gb mode inter-connected via the Iur-g interface. + +RNSAP procedures are divided into four modules as follows: + +1. RNSAP Basic Mobility Procedures; +2. RNSAP Dedicated Procedures; + +3. RNSAP Common Transport Channel Procedures; +4. RNSAP Global Procedures; +5. RNSAP MBMS Procedures. + +The Basic Mobility Procedures module contains procedures used to handle the mobility within UTRAN as well as to handle mobility in case of UTRAN/GERAN interworking. + +The Dedicated Procedures module contains procedures that are used to handle DCHs, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCHs] and HS-DSCH between two RNSs. If procedures from this module are not used in a specific Iur, then the usage of DCH, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCH] and HS-DSCH traffic between corresponding RNSs is not possible. + +The Common Transport Channel Procedures module contains procedures that are used to control common transport channel data streams (excluding the DSCH, HS-DSCH, E-DCH and USCH) over Iur interface. + +The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above modules involving two peer CRNCs. The procedures in this module are also used in cases involving one RNC and one BSS. + +The MBMS Procedures module contains procedures that are specific to MBMS and used for cases that cannot be handled by other modules. + +## 6.3 User Plane Frame Protocols + +### 6.3.1 Iub/Iur DCH Frame Protocol + +There are two types of Iub/Iur DCH FP frames: + +- DCH data frame; +- DCH control frame. + +The contents of the Iub/Iur DCH data frame include: + +- Transport Block Sets; +- Quality estimate. + +The contents of the Iur DCH control frame include: + +- Measurement reports; +- Power control information; +- Synchronisation information. + +For a more detailed description of the Iur/Iub DCH frame protocol refer to 'UTRAN Iur & Iub Interface User Plane Protocol for DCH Data Streams' TS 25.427 [1]. + +### 6.3.2 Iur DSCH Frame Protocol [TDD] + +There are two types of Iur DSCH FP frames: + +- DSCH data frame; +- DSCH control frames. + +The contents of the Iur DSCH data frame include: + +- MAC-c/sh SDUs; +- User Buffer Status. + +The contents of the Iur DSCH control frame include: + +- Flow control Information (UL); +- Capacity Request Information (DL). + +For a more detailed description of the Iur DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.3 Iur USCH Frame Protocol [TDD] + +There is one type of Iur USCH FP frames: + +- USCH data frame. + +The contents of the Iur USCH data frame include: + +- MAC-c/sh SDUs. + +For a more detailed description of the Iur USCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.4 Iur RACH Frame Protocol + +For a more detailed description of the Iur RACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.5 Iur FACH Frame Protocol + +For a more detailed description of the Iur FACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.6 Iur HS-DSCH Frame Protocol + +There are two types of Iur HS-DSCH FP frames: + +- HS-DSCH data frame; +- HS-DSCH control frames. + +The contents of the Iur HS-DSCH data frame include: + +- MAC-d PDUs; +- User Buffer Status. + +The contents of the Iur HS-DSCH control frame include: + +- Flow control Information (UL); +- Capacity Request Information (DL). + +For a more detailed description of the Iur HS-DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.7 Iur E-DCH Frame Protocol + +There is one type of Iur E-DCH FP frames: + +- E-DCH data frame; + +The contents of the Iur E-DCH data frame include: + +- Mac-es PDUs (multiplexed); +- Number of HARQ retransmissions; +- CFN and Sub frame number. + +For a more detailed description of the Iur E-DCH frame protocol refer to 'UTRAN Iur Interface User Plane Protocols for DCH Data Streams' TS 25.427 [1]. + +## 6.4 Mapping of Frame Protocols onto transport bearers + +| | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DCH | One Iur DCH data stream is carried on one transport bearer except in the case of co-ordinated DCHs in which case a set of co-ordinated DCHs are multiplexed onto the same transport bearer. | +| [TDD - DSCH | One Iur DSCH data stream is carried on one transport bearer.] | +| HS-DSCH | One Iur HS-DSCH data stream is carried on one transport bearer. | +| E-DCH | One Iur E-DCH data stream is carried on one transport bearer. For each E-DCH data stream, a transport bearer must be established over the Iur interface. | +| [TDD - USCH | One Iur USCH data stream is carried on one transport bearer.] | +| RACH | Multiple RACH data streams may be carried on one transport bearer. | +| FACH | Multiple FACH data streams may be carried on one transport bearer. | + +RACH and FACH data streams for one UE are carried on same transport bearer. + +# 7 DRNS logical Model over Iur + +## 7.1 Overview + +The model in Figure 3 shows the Drift Radio Network System as seen from the SRNC. It is modelled as a «black box» with a set of Radio Links on the Uu side of the box and another set of User Plane access ports on the Iur side of the box. The Radio Links are connected to the Iur user ports via the internal transport mechanisms of the DRNS. Operations for controlling the connections between ports are sent from the SRNC to the DRNC via an Iur Control Plane port. + +![Figure 3: Drift RNS Logical Model. The diagram shows the 'Serving Radio Network System' at the top connected to the 'Drift Radio Network System' (DRNS) via an 'Iur Control Plane' port. The DRNS contains a series of 'Data Ports' for various data streams: Iur DCH, Iur E-DCH, Iur TDD DSCH, Iur HS-DSCH, and Iur RACH/FACH. These ports are connected to internal 'Radio Links' which are grouped into 'Cells'. The 'Radio User Plane' is shown at the bottom, connected to the Radio Links. A box labeled 'RACH/FACH Traffic Contexts With attributes' is also shown.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +The diagram illustrates the logical model of a Drift Radio Network System (DRNS) as seen from the Serving Radio Network System (SRNC). At the top, the SRNC is connected to the DRNS via an Iur Control Plane port. The DRNS is represented as a large box containing several Data Ports on its Iur side and Radio Links on its Uu side. The Data Ports are labeled from left to right: Iur Control Port, Iur DCH Data Port, Iur E-DCH Data Port, Iur TDD DSCH Data Port, Iur HS-DSCH Data Port, Iur TDD DSCH Data Port, Iur RACH/FACH Data Port, and Iur RACH/FACH Data Port. These ports are connected to internal Radio Links, which are grouped into two Cells. Each Cell contains three Radio Links. The Radio Links are connected to the Radio User Plane at the bottom. A box labeled 'RACH/FACH Traffic Contexts With attributes' is shown on the right side of the DRNS box. + +Figure 3: Drift RNS Logical Model. The diagram shows the 'Serving Radio Network System' at the top connected to the 'Drift Radio Network System' (DRNS) via an 'Iur Control Plane' port. The DRNS contains a series of 'Data Ports' for various data streams: Iur DCH, Iur E-DCH, Iur TDD DSCH, Iur HS-DSCH, and Iur RACH/FACH. These ports are connected to internal 'Radio Links' which are grouped into 'Cells'. The 'Radio User Plane' is shown at the bottom, connected to the Radio Links. A box labeled 'RACH/FACH Traffic Contexts With attributes' is also shown. + +Figure 3: Drift RNS Logical Model + +## 7.2 Logical Model Elements + +### 7.2.1 Radio Link + +A Radio Link represents a User Plane access point on the UTRAN side of the Uu interface between the User Equipment and the UTRAN. + +The semantics of a Radio Link include the following: + +- It is created, destroyed, and added by SRNC. +- It can be attached to one or more Iur Data Ports at any given time. +- Its resources are allocated and controlled by the DRNS. + +### 7.2.2 Cell + +It is defined by: + +- A Cell identifier. + +The semantics of a Cell include the following: + +- It is created and destroyed by administrative procedures. + +### 7.2.3 Iur DCH Data Port + +One Iur DCH Data port represents one user plane transport bearer. One user plane transport bearer will carry only one DCH data stream except in the case of co-ordinated DCHs, in which case the data streams of all co-ordinated DCHs shall be multiplexed on one and the same user plane transport bearer. + +The semantics of an Iur DCH Data Port include the following: + +- It is created and destroyed by administrative procedures when transport facilities are added to, or deleted from, the Iur interface between the SRNS and DRNS. It can also be created and destroyed dynamically using dynamically setup transport bearers to add or remove transport facilities. +- It is assigned and released by the SRNC in reaction to requests for bearer services from the UE. +- It may be attached to one or more Radio Links. When attached to Radio Links in the downlink direction, it acts as a point-to-multipoint connection for diversity transmission. When attached to multiple Radio Links in the uplink direction, it acts as a multipoint-to-point connection for diversity reception [FDD]. +- The transmit and receive combining/splitting resources required to implement the point-to-multipoint and multipoint-to-point connections are controlled by the DRNS [FDD]. +- The Iur DCH Data Stream emanating from the Iur DCH Data Port terminates in the SRNS connected to DRNS. + +### 7.2.4 Iur DSCH Data Port [TDD] + +One Iur DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one DSCH data stream. + +### 7.2.5 Iur USCH Data Port [TDD] + +One Iur USCH Data port represents one Iur user plane transport bearer. One Iur user plane transport bearer will carry only one USCH data stream. + +### 7.2.6 Iur RACH/FACH Data Port + +The Iur RACH/FACH data port represents a transport bearer and is identified with a transport bearer identity. + +### 7.2.7 Iur Control Port + +An Iur Control Port represents the Control Plane access point on the Iur interface between the SRNS and the DRNS. It is defined by: + +- A transport bearer channel identifier. + +The semantics of an Iur Control Port include the following: + +- It is created via administrative procedures when the Iur interface is created. + +### 7.2.8 Iur HS-DSCH Data Port + +One Iur HS-DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one HS-DSCH data stream. + +### 7.2.9 Iur E-DCH Data Port + +One Iur E-DCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one E-DCH data stream. It is assigned and released by the SRNC in reaction to requests for bearer services from the UE. [FDD - It may be attached to one or more Radio Links. When attached to multiple Radio Links in the uplink direction, the receive combining resources required to implement the multipoint-to-point connections is in the NodeB of the DRNS.] + +# 8 Iur Interface Protocol Structure + +The Iur interface protocol architecture consists of two functional layers: + +- Radio Network Layer, defines the procedures related to the interaction of two RNCs within a PLMN. The radio network layer consists of a Radio Network Control Plane and a Radio Network User Plane. +- Transport layer, defines procedures for establishing physical connections between two RNCs within a PLMN. + +![Figure 4: Iur Interface Protocol Structure diagram showing the protocol stack for Control Plane, User Plane, and Transport Network layers.](a7835229df7a34816e1d35b5bbbc8c9e_img.jpg) + +The diagram illustrates the Iur Interface Protocol Structure, organized into three main vertical sections representing different planes and layers: + +- Radio Network Layer (Top):** + - Control Plane:** Contains the **RNSAP** protocol. + - User Plane:** Contains **Iur Data Stream(s)**. +- Transport Network Layer (Middle):** + - Transport Network User Plane (Left):** Connects the Control Plane's RNSAP to the Physical Layer. The stack includes: **SCCP** (with **MTP3-B**, **M3UA**, **M3UA**), **SSCF-NNI** (with **SCTP**, **SCTP**), **SSCOP** (with **IP**, **IP**), **AAL5**, **ATM**, and **Data Link**. + - Transport Network Control Plane (Center):** Connects the User Plane's Iur Data Stream(s) to the Physical Layer. The stack includes: **Q.2630.2**, **STC (Q.2150.1)** (with **MTP3-B**, **M3UA**), **SSCF-NNI** (with **SCTP**, **SCTP**), **SSCOP** (with **IP**, **IP**), **AAL5**, **ATM**, and **Data Link**. + - Transport Network User Plane (Right):** Connects the User Plane's Iur Data Stream(s) to the Physical Layer. The stack includes: **AAL2** (with **UDP/IP**, **UDP/IP**), **ATM**, and **Data Link**. +- Physical Layer (Bottom):** A single shared layer at the base of all three stacks. + +Figure 4: Iur Interface Protocol Structure diagram showing the protocol stack for Control Plane, User Plane, and Transport Network layers. + +Figure 4: Iur Interface Protocol Structure + +# --- 9 Other Iur Interface Specifications + +## 9.1 UTRAN Iur Interface: Layer 1 (TS 25.421) + +TS 25.421 [3] specifies the range of physical layer technologies that may be used to support the Iur interface and the Iur-g interface. + +## 9.2 UTRAN Iur Interface: Signalling Transport (TS 25.422) + +TS 25.422 [4] specifies the signalling bearers for the RNSAP for Iur Interface and for Iur-g interface. + +## 9.3 UTRAN Iur Interface: RNSAP Specification (TS 25.423) + +TS 25.423 [5] specifies the RNSAP protocol for radio network control plane signalling over the Iur interface and over the Iur-g interface. + +## 9.4 UTRAN Iur Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424) + +TS 25.424 [6] specifies the transport bearers for the user plane of the Iur interface. It also specifies the ALCAP protocol used to control these transport bearers. + +## 9.5 UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425) + +TS 25.425 [2] specifies the user plane frame handling protocol for the common channels on Iur interface. + +## 9.6 UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426) + +TS 25.426 [8] specifies the transport bearers for the user plane of the Iub/Iur interface. It also specifies the ALCAP protocol used to control these transport bearers. + +## 9.7 UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427) + +TS 25.427 [1] specifies the user plane frame handling protocol for the dedicated channels on Iub/Iur interface. + +## 9.8 Summary of UTRAN Iur Interface Technical Specifications + +The relationship between the technical specifications that define the UTRAN Iur interface is shown in Figure 5. + +![Diagram of Iur Interface Technical Specifications showing layers and protocols for Radio Network Control Plane, Transport Network Control Plane, and User Plane.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the technical specifications for the Iur interface, organized into three main planes: Radio Network Control Plane, Transport Network Control Plane, and User Plane. These are further categorized into layers: Radio Network Layer and Transport Layer. + +| Plane | Radio Network Control Plane | Transport Network Control Plane | User Plane | | +|---------------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------| +| Radio Network Layer | RNSAP
TS 25.423 | | Dedicated Channels
TS 25.427 | Common Channels
TS 25.425 | +| Transport Layer | Signalling Transport
TS 25.422 | Transport Signaling
TS 25.426
(Dedicated Channel Transport)
TS 25.424
(Common Channel Transport) | Dedicated Channel Transport
TS 25.426 | Common Channel Transport
TS 25.424 | +| | | Physical Layer TS 25.421 | | | + +Diagram of Iur Interface Technical Specifications showing layers and protocols for Radio Network Control Plane, Transport Network Control Plane, and User Plane. + +Figure 5: Iur Interface Technical Specifications + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|----------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Rel-8 version created based on v7.3.0 | 8.0.0 | +| 42 | RP-080849 | 0059 | - | Enable to dynamically control the MBMS services in MBSFN | 8.0.0 | +| 43 | RP-090078 | 0060 | 1 | RNSAP: Enhanced Relocation Request in SCCP: Connection Request | 8.1.0 | +| 12/2009 | - | - | - | Created Rel-9 version based on v8.1.0 | 9.0.0 | +| 49 | RP-100909 | 0061 | - | CS Data forwarding support for lur interface | 9.1.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.1.1 | +| 03/2011 | | | | Created Rel-10 version based on v9.1.1 | 10.0.0 | +| 06/2011 | RP-110684 | 0063 | - | Correction of references | 10.1.0 | +| 06/2011 | RP-110694 | 0064 | 2 | Introduction of Enhancements of lur-g Interface | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25421/raw.md b/marked/Rel-16/25_series/25421/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c3a09c339817694fd9bf3bf187abed849cb0a0af --- /dev/null +++ b/marked/Rel-16/25_series/25421/raw.md @@ -0,0 +1,85 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 Iur Layer 1..... | 5 | +| Annex A (informative): Change history..... | 6 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the Iur interface. The specification of transmission delay requirements and O&M requirements are not in the scope of this document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TS 25.411: "UTRAN Iur interface Layer 1". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 25.411 [1] apply. + +# --- 4 Iur Layer 1 + +The Iur Layer 1 shall comply with the requirements of chapter 4 in TS 25.411 [1]. + +# Annex A (informative): Change history + +| Date | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| 02/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 06/2011 | RP-110684 | 0003 | - | Correction of references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25426/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-16/25_series/25426/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482cca0fbd481cc10abe3e6c7fbb2080dfed8c02 --- /dev/null +++ b/marked/Rel-16/25_series/25426/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f356c21cc3fe0fe93b10ff706b31b5eb93b3b2249c94f3e5545ac7863d4eb4 +size 61460 diff --git a/marked/Rel-16/25_series/25426/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/25_series/25426/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd1d27eaf051e8f04f6d5a1cda9d228e255f7d7f --- /dev/null +++ b/marked/Rel-16/25_series/25426/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd51b4459edab82810e1761cc001ad9cfc88080ca19a0144c5acdf92852be873 +size 65388 diff --git a/marked/Rel-16/25_series/25426/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/25_series/25426/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1c6dff2736775b6570f7f6f41b2a543ab0f2d58 --- /dev/null +++ b/marked/Rel-16/25_series/25426/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f644c6ea7c4b19f7586ef9fc7c85f07bc0155c396a4b9a5155706791cc4e2f8 +size 26893 diff --git a/marked/Rel-16/25_series/25426/raw.md b/marked/Rel-16/25_series/25426/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24f655703eb44159d6b84ff8c85b0eb589191705 --- /dev/null +++ b/marked/Rel-16/25_series/25426/raw.md @@ -0,0 +1,338 @@ + + + + +# ***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. + +© 2020, 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 + +| | | +|-------------------------------------------------------------------------|----| +| Contents..... | 3 | +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Data Link Layer ..... | 7 | +| 4.1 ATM Transport Option ..... | 7 | +| 4.1.1 Protection Switching at ATM Layer..... | 7 | +| 4.2 IP Transport Option..... | 7 | +| 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams ..... | 8 | +| 5.1 Introduction ..... | 8 | +| 5.2 ATM Transport Option ..... | 8 | +| 5.3 IP Transport Option..... | 8 | +| 6 Transport Signalling Application for DCH and E-DCH Data Streams ..... | 9 | +| 6.1 Introduction ..... | 9 | +| 6.2 ALCAP in ATM Transport Option ..... | 9 | +| 6.3 ALCAP in IP Transport Option ..... | 9 | +| 7 Signalling Bearer for ALCAP on Iub Interface ..... | 9 | +| 7.1 Introduction ..... | 9 | +| 7.2 Signalling Bearer in ATM Transport Option ..... | 10 | +| 7.3 Signalling Bearer in IP Transport Option ..... | 10 | +| 8 Signalling Bearer for ALCAP on Iur Interface ..... | 10 | +| 8.1 Introduction ..... | 10 | +| 8.2 Signalling Bearer in ATM Transport Option ..... | 11 | +| 8.3 Signalling Bearer in IP Transport Option ..... | 11 | +| 9 Interworking between ATM and IP Transport Options ..... | 11 | +| 9.1 Introduction ..... | 11 | +| 9.2 Interworking Alternatives ..... | 11 | +| Annex A (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the transport bearers for the DCH/E-DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. The physical layer for the transport bearers is outside the scope of the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams". +- [2] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [3] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer specification; Type 2 AAL". +- [4] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2". +- [5] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)". +- [6] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing". +- [7] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Systems Interconnection - Network Service Definition". +- [8] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [9] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the User-Network Interface (SSCF at UNI)". +- [10] ITU-T Recommendation Q.2150.2 (1999-12): "AAL type 2 signalling transport converter on SSCOP". +- [11] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of the ITU-T Recommendation Q.2140". +- [12] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the Network Node Interface (SSCF at NNI)". +- [13] ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP". +- [14] IETF RFC 791 (1981-09): "Internet Protocol". +- [15] IETF RFC 1483 (1993-07): "Multiprotocol Encapsulation over ATM Adaptation Layer 5". +- [16] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM". +- [17] IETF RFC 768 (1980-08): "User Datagram Protocol". + +- [18] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol". +- [19] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [20] ITU-T Recommendation I.630 (1999-02): "ATM protection switching". +- [21] ITU-T Recommendation Q.Imp2210 (1996-07): "Implementor's guide (03/99) for Recommendation Q.2210 (07/96)". +- [22] ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)". +- [23] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)". +- [24] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing". +- [25] IETF RFC 2507 (1999-02): "IP header compression". +- [26] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)". +- [27] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [28] IETF RFC 2509 (1999-02): "IP Header Compression over PPP". +- [29] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [30] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [31] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [32] IETF RFC 3153 (2001-08): "PPP Multiplexing". +- [33] IETF RFC 2364 (1998-07): "PPP over AAL5". +- [34] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture". +- [35] Void +- [36] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan ". +- [37] IETF RFC 3309 (2002-09): "SCTP Checksum Change". +- [38] 3GPP TS 25.414: "UTRAN Iu Interface data transport & transport signalling". +- [39] 3GPP TS 25.401: "UTRAN overall description". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following term and definition applies: + +**ALCAP:** transport signalling protocol used to setup and tear down transport bearers + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|----------------------------------| +| AAL2 | ATM Adaptation Layer type 2 | +| AESA | ATM End System Address | +| ATM | Asynchronous Transfer Mode | +| CPCS | Common Part Convergence Sublayer | +| CPS | Common Part Sublayer | + +| | | +|---------|-------------------------------------------------------| +| DCH | Dedicated Channel | +| E-DCH | Enhanced DCH | +| HDLC | High level Data Link Control | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| LC | Link Characteristics | +| M3UA | SS7 MTP3 User Adaptation layer | +| ML/MC | Multi-link / Multi-class | +| MPLS | Multiprotocol Label Switching | +| MTP | Message Transfer Part | +| NNI | Network-Node Interface | +| NSAP | Network Service Access Point | +| PPP | Point to Point Protocol | +| PT | Path Type | +| SAAL | Signalling ATM Adaptation Layer | +| SAR | Segmentation and Reassembly | +| SCTP | Stream Control Transmission Protocol | +| SSCF | Service Specific Co-ordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| SSSAR | Service Specific Segmentation and Reassembly sublayer | +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UNI | User-Network Interface | + +# 4 Data Link Layer + +## 4.1 ATM Transport Option + +ATM shall be used in the transport network user plane and transport network control plane according to ITU-T Rec. I.361 [2]. + +### 4.1.1 Protection Switching at ATM Layer + +If redundancy of pathways at ATM Layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Rec. I.630 [20]. + +## 4.2 IP Transport Option + +A UTRAN node supporting IP transport option shall support PPP protocol IETF RFC 1661 [23] with HDLC framing (IETF RFC 1662 [24]). + +NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [32]), (IETF RFC 2364 [33]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [34]), etc.) fulfilling the UTRAN requirements towards the upper layers. + +A UTRAN node supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [25]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [26], IETF RFC 2686 [27]). In this case the negotiation of header compression (ITU-T Rec. I.630 [20]) over PPP shall be performed via IETF RFC 2509 [28]. + +# 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams + +## 5.1 Introduction + +The Frame Protocol for DCH and E-DCH data streams (TS 25.427 [1]) is the user of the transport layer specified in the present document. + +There are two options for the transport layer of the DCH and E-DCH data streams in Iur and Iub: + +- 1) ATM based transport (ATM Transport Option) +- 2) IP based transport (IP Transport Option) + +The following figure shows the protocol stacks of the two options. + +![Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack for the ATM transport option shows layers from top to bottom: AAL2/SSAR (I.361), AAL2/PM (I.362), ATM, and Physical. The right stack for the IP transport option shows layers from top to bottom: UDP (RFC 768), IP (RFC 2460), IPsec (RFC 2401), Data link layer, and Physical. Both stacks are labeled with 'Radio Network Layer' at the top and 'Transport Network Layer' on the left. The caption below the diagram reads: 'Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces'.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack for the ATM transport option shows layers from top to bottom: AAL2/SSAR (I.361), AAL2/PM (I.362), ATM, and Physical. The right stack for the IP transport option shows layers from top to bottom: UDP (RFC 768), IP (RFC 2460), IPsec (RFC 2401), Data link layer, and Physical. Both stacks are labeled with 'Radio Network Layer' at the top and 'Transport Network Layer' on the left. The caption below the diagram reads: 'Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces'. + +Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces + +## 5.2 ATM Transport Option + +Asynchronous Transfer Mode (ATM) (ITU-T Rec. I.361 [2]) and ATM Adaptation Layer type 2 (AAL2) (ITU-T Rec. I.363.2 [3], ITU-T Rec. I.366.1 [4]) are used as a transport layer for DCH and E-DCH data streams on Iur and Iub interfaces. Service Specific Segmentation and Reassembly (SSAR) sublayer for AAL2 is used for the segmentation and reassembly of AAL2 SDUs. + +## 5.3 IP Transport Option + +UDP (IETF RFC 768 [17]) over IP shall be supported as the transport for DCH and E-DCH data streams on Iub and Iur interfaces. The data link layer is as specified in chapter 4.2. + +An IP UTRAN Node shall support IPv6 (IETF RFC 2460[29]). The support of IPv4 (IETF RFC 791[14]) is optional. + +NOTE: This does not preclude single implementation and use of IPv4. + +IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network. + +The transport bearer is identified by the UDP port number and the IP address (source UDP port number, destination UDP port number, source IP address, destination IP address). + +The source IP address and destination IP address exchanged via Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [39]. + +IP Differentiated Services code point marking (IETF RFC 2474 [30]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M. Traffic categories are implementation-specific and may be determined from the application parameters. + +# 6 Transport Signalling Application for DCH and E-DCH Data Streams + +## 6.1 Introduction + +This chapter specifies the ALCAP protocol(s) to be used in Iur and Iub interfaces for DCH data streams. + +## 6.2 ALCAP in ATM Transport Option + +AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) is the signalling protocol to control AAL2 connections on Iub and Iur interfaces. ITU-T Rec. Q.2630.2 [22] adds new optional capabilities to ITU-T Rec. Q.2630.1 [5]. + +Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 [22]. + +User Plane Transport bearers for Iur interface are established, in all normal cases released and optionally modified by the ALCAP in the Serving RNC. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iur interface in the Drift RNC. + +User Plane Transport bearers for Iub interface are established, in all normal cases released and optionally modified by the ALCAP in the Controlling RNC. Binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. In case of a Reset initiated by the CRNC, the ALCAP in the Node B shall release the transport bearers involved in the impacted Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers for the removed dedicated channels that were remaining within the cell when the cell is deleted. + +AAL2 transport layer addressing is based on embedded E.164 or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [6], ITU-T Rec. X.213 [7]). Native E.164 addressing (ITU-T Rec. E.164 [36]) shall not be used. + +The Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol. + +If there is an AAL2 switching function in the transport network layer of the interface, the Path Type parameter (PT) may be included in the Establish Request message of AAL2 signalling protocol for prioritisation at ATM level. + +If the value in either the Maximum CPS-SDU Bit Rate or the Average CPS-SDU Bit Rate of the Link Characteristics(LC) in AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [22] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher. + +NOTE: Separation of traffic (e.g. HS-DSCH, E-DCH) that is using this modified interpretation of Link Characteristics in ref. ITU-T Rec. Q.2630.2 [22] from other traffic is highly recommended. Otherwise the potential bursty nature of this specific traffic in combination with its unknown bit rate may decrease the QoS of all traffic within the same AAL type 2 path. + +## 6.3 ALCAP in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +Application of ALCAP in IP to ATM interworking case is defined in chapter 9 of this Technical Specification. + +# --- 7 Signalling Bearer for ALCAP on Iub Interface + +## 7.1 Introduction + +This clause specifies the signalling bearer for the ALCAP on Iub interface. + +## 7.2 Signalling Bearer in ATM Transport Option + +SAAL-UNI (ITU-T Rec. Q.2110 [8], ITU-T Rec. Q.2130 [9]) is used as the signalling bearer for the AAL Type 2 Signalling protocol on Iub interface. Signalling Transport Converter for SSCOP is applied ITU-T Rec. Q.2150.2 [10]. The following figure shows the signalling bearer protocol stack for the ALCAP on Iub interface. + +![Diagram of the signalling bearer for ALCAP on Iub interface. It shows a stack of protocols: ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains sub-components SSCF-UNI, SSCOP, AAL5 Common Part, CPCS, and SAR. The stack continues with ATM and PHY at the bottom. A dashed box encloses the entire stack from ALCAP down to PHY, with a horizontal line passing through the middle of the stack.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Diagram of the signalling bearer for ALCAP on Iub interface. It shows a stack of protocols: ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains sub-components SSCF-UNI, SSCOP, AAL5 Common Part, CPCS, and SAR. The stack continues with ATM and PHY at the bottom. A dashed box encloses the entire stack from ALCAP down to PHY, with a horizontal line passing through the middle of the stack. + +Figure 2: Signalling bearer for ALCAP on Iub interface + +## 7.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +# --- 8 Signalling Bearer for ALCAP on Iur Interface + +## 8.1 Introduction + +This clause specifies the signalling bearer for the ALCAP on the Iur interface. + +## 8.2 Signalling Bearer in ATM Transport Option + +There are two protocol stacks specified for Iur ALCAP Signalling Bearer in ATM option - one based on MTP-3B (ITU-T Rec. Q.2210 [11], ITU-T Rec. Q.Imp2210 [21]) and SAAL-NNI (ITU-T Rec. Q.2140 [12], ITU-T Rec. Q.2110 [8]) and the other based on SCTP (IETF RFC 2960 [18]). Signalling Transport Converter for MTP-3B is applied (ITU-T Rec. Q.2150.1 [13]). MTP-3 User Adaptation Layer (M3UA) for SCTP is applied in IETF RFC 3332 [19]. Classical IP over ATM is specified in IETF RFC 2225 [16]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 1483 [15]. The checksum method specified in IETF RFC 3309 [37] shall be used instead of the method specified in IETF RFC 2960 [18]. The following figure shows the signalling bearer protocol stacks for the ALCAP on Iur interface. + +![Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is MTP-3B based, starting with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1), MTP-3B, AAL5 SSCS (with SSCF-NNI, SSCOP, CPCS, SAR), ATM, and PHY. The right stack is IP based, starting with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1), M3UA, SCTP, IP, AAL5, ATM, and PHY.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates two protocol stacks for the ALCAP Signalling Bearer on the Iur interface. Both stacks start with ALCAP (Q.2630.2) at the top, separated by a vertical line with a circle. The left stack, labeled 'MTP-3B based Iur ALCAP Signalling Bearer', consists of the following layers from top to bottom: STC (Q.2150.1), MTP-3B, AAL5 SSCS (which includes SSCF-NNI, SSCOP, CPCS, and SAR), ATM, and PHY. The right stack, labeled 'IP based Iur ALCAP Signalling Bearer', consists of the following layers from top to bottom: STC (Q.2150.1), M3UA, SCTP, IP, AAL5, ATM, and PHY. + +Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is MTP-3B based, starting with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1), MTP-3B, AAL5 SSCS (with SSCF-NNI, SSCOP, CPCS, SAR), ATM, and PHY. The right stack is IP based, starting with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1), M3UA, SCTP, IP, AAL5, ATM, and PHY. + +**Figure 3: Signalling bearers for ALCAP on Iur interface** + +## 8.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +# 9 Interworking between ATM and IP Transport Options + +## 9.1 Introduction + +This clause specifies the interworking between IP and ATM transport options. A UTRAN node supporting IP transport option shall provide interworking to a UTRAN node supporting only ATM transport option. + +## 9.2 Interworking Alternatives + +For interworking with a UTRAN node supporting only ATM option, the UTRAN node supporting IP option shall additionally support at least one of the following interworking mechanisms: + +- 1) ATM&IP dual stack. An ALCAP protocol is not required in this interworking solution. + +Annex A of TS 25.414 [38] shows an example of protocols for the case the ATM&IP RNC/CN-node has no ATM connectivity. + +- 2) An Interworking Function (IWF), either internal or external to the UTRAN node. AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) shall be supported as ALCAP protocol between the Interworking Function and the UTRAN node supporting ATM transport option. + +Annex A of TS 25.414 [38] shows an example of a protocol stack for the bearer control protocol between the RNC/CN IP Node and its IWF for the case when the IWF is an external unit to the RNC/CN node. Other protocol stacks for this case are not precluded. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|-------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110686 | 0053 | - | Correction related to the References and clean-up of 25.426 | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25427/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/marked/Rel-16/25_series/25427/220869911a1ecfa1dd4aa6d750319aad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76cd9e4df3512955caa11a7536a2aeb86bb9fada --- /dev/null +++ b/marked/Rel-16/25_series/25427/220869911a1ecfa1dd4aa6d750319aad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4cd6e391b6066404ef9014f984950585cfe9e406e6d503a7df1e0b203ba6503 +size 13162 diff --git a/marked/Rel-16/25_series/25427/2c532a9bb51e081048d718316f509294_img.jpg b/marked/Rel-16/25_series/25427/2c532a9bb51e081048d718316f509294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20cd3365d85b6bc4af2b28d8defd0b51d51ed30d --- /dev/null +++ b/marked/Rel-16/25_series/25427/2c532a9bb51e081048d718316f509294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:674bf55f0d6708336dde43f2ba065555b11893083800a40231ac2ef8b83e244b +size 30618 diff --git a/marked/Rel-16/25_series/25427/3d832e1d9f2029a103f70128d8287f43_img.jpg b/marked/Rel-16/25_series/25427/3d832e1d9f2029a103f70128d8287f43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f70def5153a5232d941709e9781589341fa6409 --- /dev/null +++ b/marked/Rel-16/25_series/25427/3d832e1d9f2029a103f70128d8287f43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3d5a88d637f0647272948b528a46eaf0f606d2dda341825f2d3ef673c8d868a +size 12341 diff --git a/marked/Rel-16/25_series/25427/3e73823c346c1d339cca8e25b296bf1a_img.jpg b/marked/Rel-16/25_series/25427/3e73823c346c1d339cca8e25b296bf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9577d4f15d10b7609852afafe09d580c2c336366 --- /dev/null +++ b/marked/Rel-16/25_series/25427/3e73823c346c1d339cca8e25b296bf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2390bdc6d7cffba27bddf716b1cbdca7c566f5924fc39aeb20421df6bbea293 +size 13554 diff --git a/marked/Rel-16/25_series/25427/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/25_series/25427/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27ed903749c98852abd61a9c30e3b8dab8b16b4a --- /dev/null +++ b/marked/Rel-16/25_series/25427/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9570e52d663d366ebee4c550e8362e9c5edbd08ab055010be6a7fc3de39f19d4 +size 10665 diff --git a/marked/Rel-16/25_series/25427/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-16/25_series/25427/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0610854d992c1825447eefac5d8f66513288de8a --- /dev/null +++ b/marked/Rel-16/25_series/25427/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cfc2bd1728efc515aa35e76138e3a2116ffb41f0254b1ac3124e5c51912c785 +size 68726 diff --git a/marked/Rel-16/25_series/25427/4d3ae95eface3b9d7eeeaa18e7036024_img.jpg b/marked/Rel-16/25_series/25427/4d3ae95eface3b9d7eeeaa18e7036024_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcc7ea9ed546739dda7c7514fb9cc646b7aab88 --- /dev/null +++ b/marked/Rel-16/25_series/25427/4d3ae95eface3b9d7eeeaa18e7036024_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78a841c1b0901d5bb444bef2fc734300bfb7a41f8d6ff326af88c73242f1df51 +size 40984 diff --git a/marked/Rel-16/25_series/25427/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/25_series/25427/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc362821fa769a6d9cc66936f77f08ef3579b0dd --- /dev/null +++ b/marked/Rel-16/25_series/25427/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:766a9f63e230ef4b86e1f5e386ee13c2025da80284876467f4fa344dbb2a8552 +size 118009 diff --git a/marked/Rel-16/25_series/25427/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/25_series/25427/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c4950bec1309d5215d089541232331eb5a2c7d6 --- /dev/null +++ b/marked/Rel-16/25_series/25427/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c6cb9ba5289c21d05fd4d8cbbb4dd5809a289bab93e385060cfe454abf91aaf +size 109073 diff --git a/marked/Rel-16/25_series/25427/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/25_series/25427/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..578015c1766ff11445690142b4168452eb26d3ca --- /dev/null +++ b/marked/Rel-16/25_series/25427/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bdb6dbb4affe9d2b52714cf663b11978c7434c628c0b0eaad6fc1ef84c8a756 +size 10486 diff --git a/marked/Rel-16/25_series/25427/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25427/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25d8f65e245be77d1dc25a1e62e3fcfee6817f7e --- /dev/null +++ b/marked/Rel-16/25_series/25427/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ceeb216055ab3f505ef5a223c9761e5129e70170f75394b9dbe35f899be583d2 +size 15774 diff --git a/marked/Rel-16/25_series/25427/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/25_series/25427/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed62272dfc07a66d70b95d422ddb269b200a3f1d --- /dev/null +++ b/marked/Rel-16/25_series/25427/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5955afe3403e5c36b878ea051292ab98eda0cca17125d534693522c2b420bdf6 +size 33834 diff --git a/marked/Rel-16/25_series/25427/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/25_series/25427/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65500ccd220e002a1a610b449855f28d704799f7 --- /dev/null +++ b/marked/Rel-16/25_series/25427/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8091a7913230b268d12d5bf3a6b8fac2ac4450c066aa7ad909fd0b08803f38ad +size 10721 diff --git a/marked/Rel-16/25_series/25427/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25427/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..188a93f451ba77f6bc1dc87d5bab09ce47808fa0 --- /dev/null +++ b/marked/Rel-16/25_series/25427/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be1b794dc2d70f2f2f0c805e317aa9ca0bdaccd85300f4c264e373aa2963e34c +size 11625 diff --git a/marked/Rel-16/25_series/25427/92b615e70a7ecf197adf6e9b513ebd2c_img.jpg b/marked/Rel-16/25_series/25427/92b615e70a7ecf197adf6e9b513ebd2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..446328a499118da0ddf125c566a3783a4970c3d5 --- /dev/null +++ b/marked/Rel-16/25_series/25427/92b615e70a7ecf197adf6e9b513ebd2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c30a8a4c99defdf77acaf531b95404cb7f7e4ef9d1e9f1819327e89b97af4737 +size 29627 diff --git a/marked/Rel-16/25_series/25427/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/Rel-16/25_series/25427/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27a8af0108c36dbd2194097079e8cbbc482d55ac --- /dev/null +++ b/marked/Rel-16/25_series/25427/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6b6384159652890f82070f945df408b184a99e82db16b29f2100777adb6f6c9 +size 11213 diff --git a/marked/Rel-16/25_series/25427/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-16/25_series/25427/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95ad74a1a05511d081312352a7b4543047383c11 --- /dev/null +++ b/marked/Rel-16/25_series/25427/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7871178e5bd0421621f9a4e5fd65f6dfa13f2383433c7c6da768a90a90a62040 +size 18079 diff --git a/marked/Rel-16/25_series/25427/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/25_series/25427/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8905667bec0f9a66ee68fcb42fa2385624cd174f --- /dev/null +++ b/marked/Rel-16/25_series/25427/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0954c3163d389eca241f9c4920143f428c76311f208382c397abd509d7251d4d +size 15979 diff --git a/marked/Rel-16/25_series/25427/b81d1613e285a9353171cdc5ef97a1f0_img.jpg b/marked/Rel-16/25_series/25427/b81d1613e285a9353171cdc5ef97a1f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d49df271b0ca910abd512630f16edc613e7af375 --- /dev/null +++ b/marked/Rel-16/25_series/25427/b81d1613e285a9353171cdc5ef97a1f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ce6354c3c87189c8125a5b3852d706fb9fc81eb28b88d4aa1d1e31d42e08458 +size 28825 diff --git a/marked/Rel-16/25_series/25427/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-16/25_series/25427/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e54d67ddf14a78814d8ab50aabdb223032567bd --- /dev/null +++ b/marked/Rel-16/25_series/25427/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d791d2c92acfb5cfb8e699f92da4389ada976ccf3afd2b7e18a0300edf951a1 +size 10551 diff --git a/marked/Rel-16/25_series/25427/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-16/25_series/25427/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09fc033fb89c3a181a5b67ffb4600ae8ff5006a2 --- /dev/null +++ b/marked/Rel-16/25_series/25427/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d18a914a31985f8944b7f4a154c35a14343efa03aa89d6b89ec2763002082ed +size 10840 diff --git a/marked/Rel-16/25_series/25427/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-16/25_series/25427/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..657bc82c24e7d6e5d124f75e334c74e9a3fbe9da --- /dev/null +++ b/marked/Rel-16/25_series/25427/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52920929c4e97bb7a9936181da68da03e961a69d05bc3ed02a6d1f28c4c081db +size 11216 diff --git a/marked/Rel-16/25_series/25427/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Rel-16/25_series/25427/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d8612cfd838cb5ebb714bd8a2bcf883784befa5 --- /dev/null +++ b/marked/Rel-16/25_series/25427/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f959e5e283e2da72011a9b1373bd5626352d79401f4fce0165f3a889a17c882 +size 5242 diff --git a/marked/Rel-16/25_series/25427/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-16/25_series/25427/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0290ec5dd4d140f0ae6c1ff36aac2f150090904 --- /dev/null +++ b/marked/Rel-16/25_series/25427/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:465c2c5ba8081f396162791a67e5db7c3b82e510890c1bb3f9f97028ec0a2b02 +size 187397 diff --git a/marked/Rel-16/25_series/25427/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/25_series/25427/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..084eb2439ef685d85c55092d78e4f08b08cb6a08 --- /dev/null +++ b/marked/Rel-16/25_series/25427/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db14d2620995417f48a0b7791357004e0d523d6b49fd50798cbcca2b9b7f52ed +size 184274 diff --git a/marked/Rel-16/25_series/25427/e4cc1eed414abddb18a100c9b3ee64e0_img.jpg b/marked/Rel-16/25_series/25427/e4cc1eed414abddb18a100c9b3ee64e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3305942cb59be1a13caf35f1a0de576c39415773 --- /dev/null +++ b/marked/Rel-16/25_series/25427/e4cc1eed414abddb18a100c9b3ee64e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b49b8b4148790819e09fc5b36ccc9765e1e0431cfba814d3f71756b8a97b49b9 +size 16673 diff --git a/marked/Rel-16/25_series/25427/eb2ecad845f6639684b50f51a346cec9_img.jpg b/marked/Rel-16/25_series/25427/eb2ecad845f6639684b50f51a346cec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ceffcddeb6005713ebde7bab472f24031159d34 --- /dev/null +++ b/marked/Rel-16/25_series/25427/eb2ecad845f6639684b50f51a346cec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe09c3beffa4dcc7e2e893c6e6a786caccfce87e8bf3392e199559cb4440335 +size 33090 diff --git a/marked/Rel-16/25_series/25427/fd856db65d36f12fa7dd9b1a1f03eb75_img.jpg b/marked/Rel-16/25_series/25427/fd856db65d36f12fa7dd9b1a1f03eb75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..120e59ee1193a68aad52c454defeee636da086d8 --- /dev/null +++ b/marked/Rel-16/25_series/25427/fd856db65d36f12fa7dd9b1a1f03eb75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:872ff357a610215d2daf03e2da9af7171f5962bb952dcd290db7830b2cb04fe2 +size 13958 diff --git a/marked/Rel-16/25_series/25427/raw.md b/marked/Rel-16/25_series/25427/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a2be253586ee8fbdf992b0ebf52723d3ec5fa85f --- /dev/null +++ b/marked/Rel-16/25_series/25427/raw.md @@ -0,0 +1,1911 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 3.3 Specification Notations ..... | 8 | +| 4 General aspects ..... | 9 | +| 4.1 DCH and E-DCH FP services..... | 10 | +| 4.2 Services expected from the Data Transport Network layer ..... | 10 | +| 4.3 Protocol Version..... | 10 | +| 5 DCH Frame Protocol procedures ..... | 11 | +| 5.1 Data Transfer..... | 11 | +| 5.1.0 General ..... | 11 | +| 5.1.1 Uplink for DCH..... | 11 | +| 5.1.1a Uplink for E-DCH ..... | 11 | +| 5.1.2 Downlink ..... | 12 | +| 5.2 Timing Adjustment ..... | 13 | +| 5.3 DCH Synchronisation ..... | 14 | +| 5.4 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD]..... | 14 | +| 5.5 Node Synchronisation ..... | 14 | +| 5.6 Rx Timing Deviation Measurement [3.84 Mcps and 7.68 Mcps TDD] ..... | 15 | +| 5.7 DSCH TFCI Signalling [FDD] ..... | 15 | +| 5.8 Radio Interface Parameter Update [FDD]..... | 15 | +| 5.9 Timing Advance [3.84 Mcps and 7.68 Mcps TDD] ..... | 16 | +| 5.10 General ..... | 16 | +| 5.10.1 Transport bearer replacement..... | 16 | +| 5.10.2 Transport channel addition..... | 17 | +| 5.11 Generation of subframe number..... | 17 | +| 5.12 Generation of number of HARQ retransmissions..... | 17 | +| 5.13 Indication of HARQ failure..... | 18 | +| 5.14 TNL Congestion Indication..... | 19 | +| 6 Frame structure and coding..... | 19 | +| 6.1 General ..... | 19 | +| 6.1.1 General principles for the coding ..... | 20 | +| 6.2 Data frames ..... | 20 | +| 6.2.1 Introduction ..... | 20 | +| 6.2.2 UL DATA FRAME..... | 20 | +| 6.2.2.1 UL DATA FRAME FOR DCH..... | 20 | +| 6.2.2.2 UL DATA FRAME FOR E-DCH TYPE 1 ..... | 21 | +| 6.2.2.3 UL DATA FRAME FOR E-DCH TYPE 2 ..... | 23 | +| 6.2.3 DL DATA FRAME..... | 24 | +| 6.2.4 Coding of information elements in data frames ..... | 24 | +| 6.2.4.1 Header CRC..... | 24 | +| 6.2.4.2 Frame Type (FT)..... | 25 | +| 6.2.4.3 Connection Frame Number (CFN) ..... | 25 | +| 6.2.4.4 Transport Format Indicator (TFI) ..... | 25 | +| 6.2.4.5 Quality Estimate (QE) ..... | 25 | +| 6.2.4.6 Transport Block (TB)..... | 26 | +| 6.2.4.7 CRC indicator (CRCI) ..... | 26 | +| 6.2.4.8 Payload CRC..... | 26 | +| 6.2.4.9 Spare Extension ..... | 26 | +| 6.2.4.10 Subframe Number..... | 26 | +| 6.2.4.11 Number of HARQ Retransmissions, NHR ..... | 26 | +| 6.2.4.12 Number of Subframes ..... | 27 | + +| | | | +|------------|-------------------------------------------------------|----| +| 6.2.4.13 | Number of MAC-es PDUs..... | 27 | +| 6.2.4.14 | Data Description Indicator, DDI..... | 27 | +| 6.2.4.15 | Number of MAC-d PDUs, N ..... | 27 | +| 6.2.4.16 | FSN – Frame Sequence Number ..... | 27 | +| 6.2.4.17 | Number of MAC-is PDUs ..... | 27 | +| 6.2.4.18 | User Buffer size ..... | 27 | +| 6.2.4.19 | Number of MAC-is SDU in frame ..... | 28 | +| 6.2.4.20 | MAC-is PDU descriptor ..... | 28 | +| 6.2.4.21 | UL Multiplexing Information (UL Mux Info)[FDD] ..... | 28 | +| 6.2.4.22 | UL CLTD Removal (CLTD-R)[FDD] ..... | 28 | +| 6.3 | Control frames ..... | 28 | +| 6.3.1 | Introduction ..... | 28 | +| 6.3.2 | Header structure of the control frames ..... | 29 | +| 6.3.2.1 | Frame CRC ..... | 29 | +| 6.3.2.2 | Frame Type (FT)..... | 29 | +| 6.3.2.3 | Control Frame Type..... | 29 | +| 6.3.3 | Payload structure and information elements ..... | 30 | +| 6.3.3.1 | TIMING ADJUSTMENT ..... | 30 | +| 6.3.3.1.1 | Payload structure ..... | 30 | +| 6.3.3.1.2 | CFN ..... | 30 | +| 6.3.3.1.3 | Time of Arrival (ToA)..... | 30 | +| 6.3.3.1.4 | Spare Extension..... | 30 | +| 6.3.3.2 | DL SYNCHRONISATION ..... | 30 | +| 6.3.3.2.1 | Payload structure ..... | 30 | +| 6.3.3.2.2 | CFN ..... | 30 | +| 6.3.3.2.3 | Spare Extension..... | 31 | +| 6.3.3.3 | UL SYNCHRONISATION ..... | 31 | +| 6.3.3.3.1 | Payload structure ..... | 31 | +| 6.3.3.3.2 | CFN ..... | 31 | +| 6.3.3.3.3 | Time of Arrival (ToA)..... | 31 | +| 6.3.3.3.4 | Spare Extension..... | 31 | +| 6.3.3.4 | OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD]..... | 31 | +| 6.3.3.4.1 | Payload structure ..... | 31 | +| 6.3.3.4.2 | SIR Target ..... | 32 | +| 6.3.3.4.3 | Spare Extension..... | 32 | +| 6.3.3.4.4 | UL Mux Info ..... | 32 | +| 6.3.3.5 | DL NODE SYNCHRONISATION ..... | 32 | +| 6.3.3.5.1 | Payload structure ..... | 32 | +| 6.3.3.5.2 | T1 ..... | 32 | +| 6.3.3.5.3 | Spare Extension..... | 32 | +| 6.3.3.6 | UL NODE SYNCHRONISATION ..... | 32 | +| 6.3.3.6.1 | Payload structure ..... | 32 | +| 6.3.3.6.2 | T1 ..... | 33 | +| 6.3.3.6.3 | T2 ..... | 33 | +| 6.3.3.6.4 | T3 ..... | 33 | +| 6.3.3.6.5 | Spare Extension..... | 33 | +| 6.3.3.7 | RX TIMING DEVIATION [3.84 Mcps and 7.68Mcps TDD]..... | 33 | +| 6.3.3.7.1 | Payload structure ..... | 33 | +| 6.3.3.7.2 | Rx Timing Deviation [3.84 Mcps TDD]..... | 34 | +| 6.3.3.7.2A | Rx Timing Deviation [7.68 Mcps TDD]..... | 34 | +| 6.3.3.7.2B | E-RUCCH Flag ..... | 35 | +| 6.3.3.7.3 | Spare Extension..... | 35 | +| 6.3.3.7.4 | CFN ..... | 35 | +| 6.3.3.7.5 | New IE Flags ..... | 35 | +| 6.3.3.8 | DSCH TFCI SIGNALLING [FDD] ..... | 35 | +| 6.3.3.8.1 | Payload structure ..... | 35 | +| 6.3.3.8.2 | TFCI (field 2) ..... | 35 | +| 6.3.3.8.3 | Spare Extension..... | 35 | +| 6.3.3.8.4 | CFN ..... | 36 | +| 6.3.3.9 | RADIO INTERFACE PARAMETER UPDATE [FDD] ..... | 36 | +| 6.3.3.9.1 | Payload structure ..... | 36 | +| 6.3.3.9.2 | Radio Interface Parameter Update flags..... | 36 | + +| | | | +|------------------------|------------------------------------------------------------------------|----| +| 6.3.3.9.3 | TPC Power Offset (TPC PO) ..... | 37 | +| 6.3.3.9.4 | Spare Extension..... | 37 | +| 6.3.3.9.4A | CFN ..... | 37 | +| 6.3.3.9.5 | DPC Mode..... | 37 | +| 6.3.3.9.6 | TFCI Power Offset (TFCI PO)..... | 37 | +| 6.3.3.9.7 | TFCI Power Offset for primary cell (TFCI PO_primary)..... | 37 | +| 6.3.3.9.8 | Multiple RL Sets Indicator..... | 37 | +| 6.3.3.9.9 | Maximum UE TX Power ..... | 37 | +| 6.3.3.9.10 | Multiple RL Sets Indicator on the secondary uplink frequency..... | 38 | +| 6.3.3.10 | TIMING ADVANCE [3.84Mcps and 7.68 Mcps TDD]..... | 38 | +| 6.3.3.10.1 | Payload structure ..... | 38 | +| 6.3.3.10.2 | CFN ..... | 38 | +| 6.3.3.10.3 | TA [3.84 Mcps]..... | 39 | +| 6.3.3.10.3A | TA [7.68 Mcps]..... | 39 | +| 6.3.3.10.4 | Spare Extension..... | 39 | +| 6.3.3.10.5 | New IE Flags [7.68Mcps TDD] ..... | 39 | +| 6.3.3.11 | TNL CONGESTION INDICATION..... | 39 | +| 6.3.3.11.1 | Payload structure ..... | 39 | +| 6.3.3.11.2 | Congestion Status..... | 39 | +| 6.3.3.11.3 | Spare Extension..... | 39 | +| 7 | Handling of Unknown, Unforeseen and Erroneous Protocol Data ..... | 40 | +| 7.1 | General ..... | 40 | +| 7.2 | Error detection..... | 40 | +| 7.2.1 | CRC Calculation..... | 40 | +| 7.2.1.1 | Relation between input and output of the Cyclic Redundancy Check ..... | 40 | +| Annex A (informative): | Change history..... | 42 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document shall provide a description of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams as agreed within the TSG-RAN working group 3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.301: "Radio interface protocol architecture". +- [2] 3GPP TS 25.401: "UTRAN overall description". +- [3] 3GPP TS 25.302: "Services provided by the physical layer". +- [4] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". +- [5] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2". +- [6] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling". +- [7] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [8] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [9] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [10] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [11] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [12] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [13] 3GPP TS 25.319: "Enhanced uplink; Overall description; Stage 2" +- [14] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)" +- [15] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification" +- [16] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Transport Bearer:** service provided by the transport layer and used by frame protocol for the delivery of FP PDU + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------| +| BER | Bit Error Rate | +| CCTrCH | Coded Composite Transport Channel | +| CFN | Connection Frame Number | +| CRC | Cyclic Redundancy Checksum | +| CRCI | CRC Indicator | +| DCH | Dedicated Transport Channel | +| DL | Downlink | +| DPC | Downlink Power Control | +| DRNC | Drift RNC | +| DSCH | Downlink Shared Channel | +| DTX | Discontinuous Transmission | +| E-DCH | Enhanced DCH | +| FP | Frame Protocol | +| FT | Frame Type | +| HARQ | Hybrid ARQ | +| LTOA | Latest Time of Arrival | +| PC | Power Control | +| PDU | Protocol Data Unit | +| PO | Power Offset | +| QE | Quality Estimate | +| RL | Radio Link | +| SIR | Signal-to-Interference Ratio | +| SRNC | Serving RNC | +| TB | Transport Block | +| TBS | Transport Block Set | +| TFI | Transport Format Indicator | +| TFCI | Transport Format Combination Indicator | +| ToA | Time of Arrival | +| ToAWE | Time of Arrival Window Endpoint | +| ToAWS | Time of Arrival Window Startpoint | +| TPC | Transmit Power Control | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. +- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. +- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. + +- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD – " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- Procedure When referring to a procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Timing Adjustment procedure. +- Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DL SYNCHRONISATION control frame. +- IE When referring to an information element (IE) in the specification, the *Information Element Name* is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. *Connection Frame Number* IE. +- Value of an IE When referring to the value of an information element (IE) in the specification, the "Value" is written as it is specified in subclause 6.2.4 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255". + +# 4 General aspects + +The specification of Iub DCH and E-DCH data streams is also valid for Iur DCH and E-DCH data streams. + +The complete configuration of the transport channel is selected by the SRNC and signalled to the Node B via the Iub and Iur control plane protocols. + +The parameters of a transport channel are described in TS 25.301 [1]. Transport channels are multiplexed on the downlink by the Node B on radio physical channels, and de-multiplexed on the uplink from radio physical channels to transport channels. + +In Iur interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B or DRNC, is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iur DCH data ports for that communication. + +In Iub interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iub DCH data ports for that communication. + +Bi-directional transport bearers are used. + +## 4.1 DCH and E-DCH FP services + +DCH frame protocol provides the following services: + +- Transport of TBS across Iub and Iur interface. +- Transport of outer loop power control information between the SRNC and the Node B. +- Support of transport channel synchronisation mechanism. +- Support of node synchronization mechanism. +- [3.84 Mcps TDD and 7.68 Mcps - Transfer of Rx timing deviation from the Node B to the SRNC.] +- Transfer of radio interface parameters from the SRNC to the Node B. + +[FDD – E-DCH frame protocol provides the following services: + +- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC. +- Transport of outer loop power control information between the SRNC and the Node B. +- Transfer of radio interface parameters from the SRNC to the Node B. +- Transport of network congestion indication from SRNC across Iub and Iur interface. +- Transport of hybrid ARQ information between SRNC and Node B.] + +[TDD – E-DCH frame protocol provides the following services: + +- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC. +- Transport of outer loop power control information between the SRNC and the Node B. +- Transport of network congestion indication from SRNC across Iub and Iur interface. +- Transport of hybrid ARQ information between SRNC and Node B.] + +## 4.2 Services expected from the Data Transport Network layer + +Following service is required from the transport layer: + +- Delivery of FP PDU. + +In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and should be avoided. + +## 4.3 Protocol Version + +This revision of the specification specifies version 1 of the protocol. + +# --- 5 DCH Frame Protocol procedures + +## 5.1 Data Transfer + +### 5.1.0 General + +When there is some data to be transmitted, DCH data frames are transferred every transmission time interval from the SRNC to the Node B for downlink transfer, and DCH/E-DCH data frames are transferred every transmission time interval from Node B to the SRNC for uplink transfer. [FDD – For 2 ms Uu TTI and depending on configuration from higher layers, the uplink E-DCH MAC-es or MAC-is PDU's from one or more 2ms Uu TTI's may be bundled into one E-DCH Data Frame before being transferred at an interval of e.g. 10ms from the Node B to the SRNC.] + +An optional error detection mechanism may be used to protect the data transfer if needed. At the transport channel setup it shall be specified if the error detection on the user data is used. + +### 5.1.1 Uplink for DCH + +![Diagram of Uplink Data Transfer procedure for DCH. It shows a 'Node B' box on the left and an 'SRNC' box on the right. A horizontal arrow labeled 'UL DATA FRAME' points from the 'Node B' box to the 'SRNC' box. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or base.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Diagram of Uplink Data Transfer procedure for DCH. It shows a 'Node B' box on the left and an 'SRNC' box on the right. A horizontal arrow labeled 'UL DATA FRAME' points from the 'Node B' box to the 'SRNC' box. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or base. + +**Figure 1: Uplink Data Transfer procedure** + +Two modes can be used for the UL transmission: *normal mode* and *silent mode*. The mode is selected by the SRNC when the transport bearer is setup and signalled to the Node B with the relevant control plane procedure. + +- In normal mode, the Node B shall always send an UL DATA FRAME to the RNC for all the DCHs in a set of coordinated DCHs regardless of the number of Transport Blocks of the DCHs. +- In silent mode and in case only one transport channel is transported on a transport bearer, the Node B shall not send an UL DATA FRAME to the RNC when it has received a TFI indicating "number of TB equal to 0" for the transport channel during a TTI. +- In silent mode and in case of coordinated DCHs, when the Node B receives a TFI indicating "number of TB equal to 0" for all the DCHs in a set of coordinated DCHs, the Node B shall not send an UL DATA FRAME to the RNC for this set of coordinated DCHs. + +For any TTI in which the Node B Layer 1 generated at least one CPHY-Out-of-Sync-IND primitive, the Node B is not required to send an UL DATA FRAME to the SRNC. + +When Node B receives an invalid TFCI, no UL DATA FRAME shall be sent to the SRNC. + +#### 5.1.1a Uplink for E-DCH + +![Diagram of Uplink Data Transfer procedure for E-DCH. It shows a 'Node B' box on the left and an 'SRNC' box on the right. A horizontal arrow labeled 'E-DCH UL DATA FRAME' points from the 'Node B' box to the 'SRNC' box. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or base.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) + +Diagram of Uplink Data Transfer procedure for E-DCH. It shows a 'Node B' box on the left and an 'SRNC' box on the right. A horizontal arrow labeled 'E-DCH UL DATA FRAME' points from the 'Node B' box to the 'SRNC' box. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or base. + +**Figure 1a: Uplink Data Transfer procedure** + +When a MAC-e or MAC-i PDU is received, it is demultiplexed into MAC-d flows which are then each sent on separate transport bearers to the RNC using the E-DCH UL DATA FRAME TYPE 1 (MAC-e) or TYPE 2 (MAC-i). + +Only silent mode is used, i.e. E-DCH user-plane payload is transmitted using the E-DCH UL DATA FRAME only when some payload has been successfully received. + +[FDD – In case of Multi Cell E-DCH operation two transport bearer modes can be used for the E-DCH payload transmission: *separate Iub transport bearer mode* and *E-DCH UL flow multiplexing mode*. The mode is selected by the SRNC when the RL on secondary UL frequency is setup and signalled to the Node B with the relevant control plane procedure. + +- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in cells of the different UL frequencies (primary and secondary) on separate transport bearers, one per frequency, to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i). + +- In E-DCH UL flow multiplexing mode, the Node B shall send the MAC-d flows received on all UL frequencies (primary as well as secondary) on one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i).] + +[1.28Mcps TDD – In case of multiple carriers E-DCH operation two transport bearer modes can be used for the E-DCH payload transmission: *separate Iub transport bearer mode* and *E-DCH UL flow multiplexing mode*. The mode is selected by the SRNC when the RL is setup and signalled to the Node B with the relevant control plane procedure. + +- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in the different frequencies on separate transport bearers, one per frequency, to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i). +- In E-DCH UL flow multiplexing mode, the Node B shall send one MAC-d flow received on all frequencies on one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i).] + +### 5.1.2 Downlink + +![Diagram illustrating the Downlink Data Transfer procedure. A box labeled 'Node B' is on the left and a box labeled 'SRNC' is on the right. A horizontal arrow labeled 'DL DATA FRAME' points from the SRNC to the Node B. Both boxes have vertical lines extending downwards to a solid horizontal bar at the bottom, representing the radio link or user plane.](853f59c89931a666c07903b31d098277_img.jpg) + +Diagram illustrating the Downlink Data Transfer procedure. A box labeled 'Node B' is on the left and a box labeled 'SRNC' is on the right. A horizontal arrow labeled 'DL DATA FRAME' points from the SRNC to the Node B. Both boxes have vertical lines extending downwards to a solid horizontal bar at the bottom, representing the radio link or user plane. + +**Figure 2: Downlink Data Transfer procedure** + +The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on this transport bearer before LTOA (TS 25.402 [5]). + +The Node B shall consider the DL user plane of a certain RL synchronised once all transport bearers established to carry DCH DL DATA FRAMES included in the CCTrCH for this RL are considered as synchronised. Once synchronised, the Node B shall assume the DL user plane for this Radio Link stays synchronised as long as the Radio Link exists, even if transport bearers are added (see 5.10.2), replaced (see subclause 5.10.1), or removed. When a RL established through the Radio Link Addition procedure (TS 25.433 [4] TS 25.423 [6]) is combined with a RL whose DL user plane is considered as synchronised, the Node B shall consider the DL user plane of this newly established RL as synchronised. + +[FDD - The Node B shall transmit on the DL DPDCH(s) of a certain RL only when the DL user plane of this RL is considered synchronised.] + +[TDD – The Node B shall transmit special bursts on the DL DPCH as per TS 25.224 [11], until the DL user plane is considered synchronised]. + +When the DL user plane is considered synchronised and the Node B does not receive a valid DL DATA FRAME in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the following cases: + +- [TDD – If the Node B receives no valid DL DATA FRAMES for any transport channel assigned to a UE it shall assume DTX and transmit special bursts as per TS 25.224 [11]]. +- If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. If the TFS contains both a TFI corresponding to "TB length equal to 0 bits" and a TFI corresponding to "number of TB equal to 0", the Node B shall assume the TFI corresponding to "number of TB equal to 0". When combining the TFI's of the different transport channels, a valid TFCI might result and in this case data shall be transmitted on Uu. +- If the Node B is not aware of a TFI value corresponding to zero bits for this transport channel or if combining the TFI corresponding to zero bits with other TFI's, results in an unknown TFI combination, the handling as described in the following paragraph shall be applied. + +At each radio frame, the Node B shall build the TFCI value of each CCTrCH, according to the TFI of the DCH data frames multiplexed on this CCTrCH and scheduled for that frame. [FDD - In case the Node B receives an unknown + +combination of TFIs from the DL DATA FRAMES, it shall transmit only the DPCCH without TFCI bits.] [TDD - In case the Node B receives an unknown combination of DCH DL DATA FRAMES, it shall apply DTX, i.e. suspend transmission on the corresponding DPCHs.] + +## 5.2 Timing Adjustment + +The Timing Adjustment procedure is used to keep the synchronization of the DCH data stream in DL direction, i.e to ensure that the Node B receives the DL frames in an appropriate time for the transmission of the data in the air interface. + +SRNC always includes the Connection Frame Number (CFN) to all DCH DL DATA FRAMES. + +If a DL DATA FRAME arrives outside the arrival window defined in the Node B, the Node B shall send a TIMING ADJUSTMENT control frame, containing the measured ToA and the CFN value of the received DL DATA FRAME. + +![Diagram illustrating the Timing Adjustment procedure. A Node B (represented by a box) sends a TIMING ADJUSTMENT control frame (represented by an arrow) to an SRNC (represented by a box).](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` + +graph LR + NodeB[Node B] -- "TIMING ADJUSTMENT" --> SRNC[SRNC] + +``` + +Diagram illustrating the Timing Adjustment procedure. A Node B (represented by a box) sends a TIMING ADJUSTMENT control frame (represented by an arrow) to an SRNC (represented by a box). + +**Figure 3: Timing Adjustment procedure** + +The arrival window and the time of arrival are defined as follows: + +**Time of Arrival Window Endpoint (ToAWE):** ToAWE represents the time point by which the DL data shall arrive to the Node B from Iub. The ToAWE is defined as the amount of milliseconds before the last time point from which a timely DL transmission for the identified CFN would still be possible taking into account the Node B internal delays. ToAWE is set via control plane. If data does not arrive before ToAWE a TIMING ADJUSTMENT control frame shall be sent by Node B. + +**Time of Arrival Window Startpoint (ToAWS):** ToAWS represents the time after which the DL data shall arrive to the Node B from Iub. The ToAWS is defined as the amount of milliseconds from the ToAWE. ToAWS is set via control plane. If data arrives before ToAWS a TIMING ADJUSTMENT control frame shall be sent by Node B. + +**Time of Arrival (ToA):** ToA is the time difference between the end point of the DL arrival window (ToAWE) and the actual arrival time of DL frame for a specific CFN. A positive ToA means that the frame is received before the ToAWE, a negative ToA means that the frame is received after the ToAWE. + +The general overview on the Timing Adjustment procedure is reported in TS 25.401 [2]. + +## 5.3 DCH Synchronisation + +DCH Synchronisation procedure is used to achieve or restore the synchronisation of the DCH data stream in DL direction, and as a keep alive procedure in order to maintain activity on the Iur/Iub transport bearer. + +The procedure is initiated by the SRNC by sending a DL SYNCHRONISATION control frame towards Node B. This control frame indicates the target CFN. + +Upon reception of the DL SYNCHRONISATION control frame, Node B shall immediately respond with UL SYNCHRONISATION control frame indicating the ToA for the DL SYNCHRONISATION control frame and the CFN indicated in the received DL SYNCHRONISATION control frame. + +UL SYNCHRONISATION control frame shall always be sent, even if the DL SYNCHRONISATION control frame is received by the Node B within the arrival window. + +![Figure 4: DCH Synchronisation procedure diagram. It shows two vertical lines representing Node B and SRNC. A horizontal arrow labeled 'DL SYNCHRONISATION' points from SRNC to Node B. A horizontal arrow labeled 'UL SYNCHRONISATION' points from Node B to SRNC. Both lines have a thick black horizontal bar at the bottom.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 4: DCH Synchronisation procedure diagram. It shows two vertical lines representing Node B and SRNC. A horizontal arrow labeled 'DL SYNCHRONISATION' points from SRNC to Node B. A horizontal arrow labeled 'UL SYNCHRONISATION' points from Node B to SRNC. Both lines have a thick black horizontal bar at the bottom. + +**Figure 4: DCH Synchronisation procedure** + +## 5.4 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD] + +Based, for example, on the CRCI values and on the quality estimate in the UL DATA FRAME, SRNC modifies the SIR target used by the UL inner loop power control by including the absolute value of the new SIR target in the OUTER LOOP PC control frame sent to the Node B's. + +At the reception of the OUTER LOOP PC control frame, the Node B shall immediately update the SIR target used for the inner loop power control [1.28 Mcps TDD - of the respective CCTrCH for UL DCHs] with the specified value. + +The OUTER LOOP PC control frame can be sent via any of the transport bearers dedicated to one UE. [1.28 Mcps TDD - In case of multiple CCTrCHs carrying DCHs, the OUTER LOOP PC control frame can be sent via any of the transport bearers carrying DCHs which belong to the CCTrCH for which the UL SIR target shall be adjusted.] + +![Figure 5: Outer Loop Power Control Information Transfer procedure diagram. It shows two vertical lines representing Node B and SRNC. A horizontal arrow labeled 'OUTER LOOP PC' points from SRNC to Node B. Both lines have a thick black horizontal bar at the bottom.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +Figure 5: Outer Loop Power Control Information Transfer procedure diagram. It shows two vertical lines representing Node B and SRNC. A horizontal arrow labeled 'OUTER LOOP PC' points from SRNC to Node B. Both lines have a thick black horizontal bar at the bottom. + +**Figure 5: Outer Loop Power Control Information Transfer procedure** + +## 5.5 Node Synchronisation + +The Node Synchronisation procedure is used by the SRNC to acquire information on the Node B timing. + +The procedure is initiated by the SRNC by sending a DL NODE SYNCHRONISATION control frame to Node B containing the parameter T1. + +Upon reception of a DL NODE SYNCHRONISATION control frame, the Node B shall respond with UL NODE SYNCHRONISATION control frame, including the parameters T2 and T3, as well as the T1 which was indicated in the initiating DL NODE SYNCHRONISATION control frame. + +The T1, T2, T3 parameters are defined as: + +- T1: RNC specific frame number (RFN) that indicates the time when RNC sends the DL NODE SYNCHRONISATION control frame through the SAP to the transport layer. +- T2: Node B specific frame number (BFN) that indicates the time when Node B receives the correspondent DL NODE SYNCHRONIZATION control frame through the SAP from the transport layer. +- T3: Node B specific frame number (BFN) that indicates the time when Node B sends the UL NODE SYNCHRONISATION control frame through the SAP to the transport layer. + +The general overview on the Node Synchronisation procedure is reported in TS 25.401 [2]. + +![Figure 6: Node Synchronisation procedure diagram](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +A sequence diagram showing the Node Synchronisation procedure between Node B and SRNC. The diagram consists of two vertical lifelines, 'Node B' on the left and 'SRNC' on the right, each with a rectangular box at the top and a thick horizontal bar at the bottom. Two messages are shown: 'DL NODE SYNCHRONISATION' as a horizontal arrow pointing from SRNC to Node B, and 'UL NODE SYNCHRONISATION' as a horizontal arrow pointing from Node B to SRNC. + +Figure 6: Node Synchronisation procedure diagram + +Figure 6: Node Synchronisation procedure + +## 5.6 Rx Timing Deviation Measurement [3.84 Mcps and 7.68 Mcps TDD] + +In case the *Timing Advance Applied* IE indicates "Yes" (see TS 25.433 [4]) in a cell, the Node B shall, for all UEs using DCHs/E-DCHs, monitor the receiving time of the uplink DPCH/E-PUCH bursts arriving over the radio interface, and shall calculate the Rx timing deviation. Additionally, the Rx timing deviation shall be calculated when an E-RUCCH or a TA Request (TS 25.319 [13]) transmission is received. If the calculated value, after rounding, is not zero, it shall be reported to the SRNC in a RX TIMING DEVIATION control frame belonging to that UE. For limitation of the frequency of this reporting, the Node B shall not send more than one RX TIMING DEVIATION control frame per UE within one radio frame. The RX TIMING DEVIATION control frame indicates whether the deviation is derived from a conventional E-RUCCH or a TA Request reception. + +If the *Timing Advance Applied* IE indicates "No" (see TS 25.433 [4]) in a cell, monitoring of the receiving time of the uplink DPCH bursts is not necessary and no RX TIMING DEVIATION control frame shall be sent. + +![Figure 7: Rx Timing Deviation Measurement procedure diagram](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +A sequence diagram showing the Rx Timing Deviation Measurement procedure between Node B and SRNC. The diagram consists of two vertical lifelines, 'Node B' on the left and 'SRNC' on the right, each with a rectangular box at the top and a thick horizontal bar at the bottom. A single message is shown: 'RX TIMING DEVIATION' as a horizontal arrow pointing from Node B to SRNC. + +Figure 7: Rx Timing Deviation Measurement procedure diagram + +Figure 7: Rx Timing Deviation Measurement procedure + +## 5.7 DSCH TFCI Signalling [FDD] + +Void. + +## 5.8 Radio Interface Parameter Update [FDD] + +This procedure is used to update radio interface parameters which are applicable to all RL's, or E-DCH Serving Radio Link Set, for the concerning UE. Both synchronised and unsynchronised parameter updates are supported. + +The procedure consists of a RADIO INTERFACE PARAMETER UPDATE control frame sent by the SRNC to the Node B. + +![Figure 9: Radio Interface Parameter Update procedure diagram](220869911a1ecfa1dd4aa6d750319aad_img.jpg) + +A sequence diagram showing the Radio Interface Parameter Update procedure between Node B and SRNC. The diagram consists of two vertical lifelines, 'Node B' on the left and 'SRNC' on the right, each with a rectangular box at the top and a thick horizontal bar at the bottom. A single message is shown: 'RADIO INTERFACE PARAMETER UPDATE' as a horizontal arrow pointing from SRNC to Node B. + +Figure 9: Radio Interface Parameter Update procedure diagram + +Figure 9: Radio Interface Parameter Update procedure + +If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid TPC power offset value, the Node B shall apply the newly provided TPC PO in DL. + +If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid Maximum UE TX Power value, the E-DCH serving Node B may use the provided value to improve E-DCH scheduling. + +If the frame contains a valid DPC mode value, the Node B shall apply the newly provided value in DL power control. + +The new values shall be applied as soon as possible in case no valid CFN is included or from the indicated CFN. If the frame contains a valid Multiple RL Sets Indicator value, the Node B may use the newly provided value in Multiple RL Sets Indicator whenever the Node B loses UL synchronization on a RL Set after initial UL synchronization as described in TS 25.214 [12]. + +If the frame contains a valid Multiple RL Sets Indicator on the secondary uplink frequency value, the Node B may use the newly provided value in Multiple RL Sets Indicator on the secondary uplink frequency whenever the Node B loses UL synchronization on a RL Set after initial UL synchronization on the secondary uplink frequency as described in TS 25.214 [12]. + +## 5.9 Timing Advance [3.84 Mcps and 7.68 Mcps TDD] + +This procedure is used in order to signal to the Node B the adjustment to be performed by the UE in the uplink timing. + +The Node B shall use the CFN and timing adjustment values to adjust its layer 1 to allow for accurate impulse averaging. + +![Diagram illustrating the Timing Advance procedure. A Node B (left) and an SRNC (right) are shown. A horizontal arrow labeled 'TIMING ADVANCE' points from the SRNC to the Node B. Both entities have a vertical line representing a timeline, with a thick horizontal bar at the bottom indicating the ground or reference point.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +Diagram illustrating the Timing Advance procedure. A Node B (left) and an SRNC (right) are shown. A horizontal arrow labeled 'TIMING ADVANCE' points from the SRNC to the Node B. Both entities have a vertical line representing a timeline, with a thick horizontal bar at the bottom indicating the ground or reference point. + +Figure 9A: Timing Advance procedure + +## 5.10 General + +### 5.10.1 Transport bearer replacement + +As described in NBAP (TS 25.433 [4]) and RNSAP (TS 25.423 [6]), transport bearer replacement can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. In both cases the following steps can be discerned: + +- 1) The new transport bearer is established after which 2 transport bearers exist in parallel. +- 2) The transport channel(s) is/are switched to the new transport bearer. +- 3) The old transport bearer is released. + +In step 1), communication on the old transport bearer continues as normal. In addition, the Node B shall support DL DATA FRAMES, the DCH Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new bearer. This enables the SRNC to determine the timing on the new transport bearer. DL DATA FRAMES transported on the new transport bearer shall not be transmitted on the DL DPDCH before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. + +Regarding step 2), the moment of switching is determined differently in the synchronised and unsynchronised case: + +- When using the combination of the Synchronised Radio Link Reconfiguration Preparation procedure and the Synchronised Radio Link Reconfiguration Commit procedure, the UL/DL DATA FRAMES shall be transported on the new transport bearer from the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message [FDD - or in the case the the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message the Node B shall start using the new transport bearer for the + +transport of UL DATA FRAMES from the CFN at which the NodeB detects that the UE uses the new configuration in the uplink]. + +- When using the Unsynchronised Radio Link Reconfiguration procedure, the Node B shall start using the new transport bearer for the transport of UL DATA FRAMES from the CFN at which the new transport bearer is considered synchronised (i.e. has received a DL DATA FRAME before LTOA (TS 25.433 [4])). Not applicable for E-DCH. Change is done directly in case of an E-DCH. + +In both cases, starting from this CFN the Node-B shall support all applicable DCH/E-DCH Frame Protocol procedures on the new transport bearer and no requirements exist regarding support of DCH/E-DCH Frame Protocol procedures on the old transport bearer. + +Finally in step 3), the old transport bearer is released. + +### 5.10.2 Transport channel addition + +As described in NBAP (TS 25.433 [4]) and RNSAP (TS 25.423 [6]), transport channel addition can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. + +When using the Synchronised Radio Link Reconfiguration Preparation procedure the Node B shall support DL DATA FRAMES, the Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new transport bearer also before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message, in order to enable the SRNC to determine the timing on the new transport bearer. DL DATA FRAMES transported on the new transport bearer before this CFN shall not be transmitted on the DL DPDCH. Starting from this CFN the Node B shall support all applicable DCH and E-DCH frame protocol procedures on the new transport bearer. + +When using the Unsynchronised Radio Link Reconfiguration procedure the Node B shall support data frames and control frames when the new transport bearer is established. + +## 5.11 Generation of subframe number + +The *CFN* and *Subframe Number* IE's values in the E-DCH Data Frame shall reflect the CFN and subframe number when the payload in the E-DCH Data Frame was correctly received on the Uu. This corresponds to when the HARQ process correctly decoded the data. [FDD - The subframe number is for 2 ms TTI set to values {0-4} and for 10 ms TTI set to {0}]. [3.84Mcps TDD, 7.68 Mcps TDD - the subframe number is set to {0}]. [1.28 Mcps TDD - the subframe number is set to {0-1}]. + +## 5.12 Generation of number of HARQ retransmissions + +After successful decoding of E-DCH payload received over Uu, the Node B shall insert the following values in the *Number of HARQ Retransmissions* IE: + +- If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value 0, 1 [FDD - or 2], then the Node B shall insert the same value in the *Number Of HARQ Retransmissions* IE in the E-DCH Data Frame. +- If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value [TDD -2 or] 3, then the Node B shall insert the calculated value of the actual number of retransmissions used for the successful decoding into the *Number of HARQ Retransmissions* IE in the E-DCH Data Frame. If the actual number of retransmission cannot be calculated, then the Node B shall insert the value 15 in the *Number of HARQ Retransmissions* IE, indicating that the number of HARQ retransmissions is unknown. +- If the UE was power limited at the time the subframe was received, or another condition applies in which the number of retransmissions should not influence the SIR target level, then the Node B shall insert value 13 into the *Number of HARQ Retransmissions* IE, indicating that the *Number of HARQ Retransmissions* IE is inappropriate as input to the outer loop power control. + +After unsuccessful decoding of the E-DCH payload, the serving Node B shall act according to section 5.13, Indication of HARQ failure. + +## 5.13 Indication of HARQ failure + +After unsuccessful decoding of the E-DCH payload and under conditions listed below, the serving Node B shall send a HARQ Failure Indication to the SRNC. [FDD - The non-serving Node B(s) shall not send a HARQ Failure Indication.] + +The serving Node B shall send a HARQ Failure Indication to the SRNC under any of the following conditions: + +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded and the RSN [TDD -and HARQ process ID] indicates the transmission of a new MAC-e or MAC-i PDU for the same HARQ process and the number of HARQ retransmissions that had already occurred was equal or higher than the lowest of the maximum HARQ retransmissions values for the UE's configured MAC-d flows. +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded and the maximum retransmissions for the MAC-d flow with the highest maximum HARQ retransmissions value valid for the UE connection have occurred, or should have occurred in case the HARQ related outband signalling (RSN) on the [FDD - E-DPCCH] [TDD - E-UCCH] could not be decoded. +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded when the MAC-e or MAC-i Reset is performed in UE. The Node B knows the timing of the MAC-e or MAC-i Reset in the UE via higher layer. + +The HARQ Failure Indication shall be sent on only one transport bearer. The Node B may select any of the transport bearers associated with the UE for which the HARQ failure relates to. + +[FDD – In case of Multi Cell E-DCH operation: + +- In E-DCH UL flow multiplexing mode, the NodeB may select any of the transport bearers associated with the UE for which the HARQ failure relates to, and including UL Mux Info (UL Multiplexing Information) into data frame to indicate on which frequency the HARQ failure happens - primary UL frequency or secondary UL frequency. +- In separate Iub transport bearer mode, the NodeB may select any of the transport bearers associated with the frequency of the UE for which the HARQ failure relates to]. + +The HARQ failure is indicated in a user data frame with values set as follows: + +- The *CFN* and *Subframe Number* IE values shall reflect the time when the failure was detected +- TYPE 1: The *Number of MAC-es PDUs* IE shall be set to zero. As a consequence there are no *DDI* and *N* IEs in the header and 4 bits padding is used after *Number of MAC-es PDUs* IE in order to have the octet aligned structure, and there are no *MAC-es PDUs* IEs in the payload part of the data frame related to the HARQ failure. +- TYPE 2: The *Number of MAC-is PDUs* IE shall be set to zero. As a consequence there are no *MAC-is PDU descriptor* IE and there are no *MAC-is PDUs* IEs in the payload part of the data frame related to the HARQ failure. +- The *Number of HARQ Retransmissions* IE shall be set to the number of HARQ retransmissions that occurred when the failure was detected. The coding shall be the same as for a correctly decoded payload as described in section 5.12. +- [FDD - In case of Multi Cell E-DCH operation, the *UL Mux Info* IE shall indicate the frequency in which the failure was detected - primary UL frequency or secondary UL frequency as described in subclause [6.2.4.21 in E-DCH UL flow multiplexing mode of Multi Cell E-DCH operation](#).] + +## 5.14 TNL Congestion Indication + +This procedure is used by the SRNC to signal, on a transport bearer carrying an E-DCH MAC-d flow, that a transport network congestion situation on Iub/Iur has been detected. + +![Diagram of TNL Congestion Indication procedure showing Node B and SRNC.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates the TNL Congestion Indication procedure. It features two main entities: 'Node B' on the left and 'SRNC' on the right, each enclosed in a rectangular box. Below each box is a thick horizontal line representing an interface. A horizontal arrow labeled 'TNL CONGESTION INDICATION' points from the SRNC box towards the Node B box, indicating the direction of the control frame transmission. + +Diagram of TNL Congestion Indication procedure showing Node B and SRNC. + +**Figure 9AB: TNL Congestion Indication procedure** + +At the reception of the TNL CONGESTION INDICATION control frame, the Node B should reduce the bit rate on the Iub interface. + +If the TNL CONGESTION INDICATION control frame is indicating “TNL Congestion – detected by frame loss”, or the TNL CONGESTION INDICATION control frame is indicating “TNL Congestion – detected by delay build-up”, the Node B should reduce the bit rate for at least the MAC-d flow on which the congestion indication control frame was received. + +If the TNL CONGESTION INDICATION control frame is indicating “No TNL Congestion”, the Node B can gradually go back to normal operation. + +# 6 Frame structure and coding + +## 6.1 General + +The general structure of a DCH FP frame consists of a header and a payload. The structure is depicted in figure 9B. + +![Diagram of general structure of a frame protocol PDU showing Header and Payload.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +The diagram shows the general structure of a frame protocol PDU. It is a horizontal rectangle divided into two sections: 'Header' on the left and 'Payload' on the right. The 'Header' section is narrower than the 'Payload' section. + +Diagram of general structure of a frame protocol PDU showing Header and Payload. + +**Figure 9B: General structure of a frame protocol PDU** + +The header contains a CRC checksum, the frame type field and information related to the frame type. + +There are two types of DCH FP frames (indicated by the *FT IE*): + +- DCH data frame. +- DCH control frame. + +For the UL direction there is also an E-DCH data frame (indicated by signalling). The E-DCH data frame is defined with two structures, TYPE 1 and TYPE 2 depending of if it contains MAC-es PDUs (TYPE 1) or MAC-is PDUs (TYPE 2). + +- E-DCH data frame. + +The payload of the data frames contains radio interface user data, quality information for the transport blocks and for the radio interface physical channel during the transmission time interval (for UL only), and an optional CRC field. + +The payload of the control frames contains commands and measurement reports related to transport bearer and the radio interface physical channel but not directly related to specific radio interface user data. + +### 6.1.1 General principles for the coding + +In the present document the structure of frames will be specified by using pictures similar to figure 10. + +![](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Condition | +|-----------------|---|---|---|---------|---|---------|---|-----------| +| Field 1 | | | | | | Field 2 | | Byte 1 | +| Field 3 | | | | | | | | Byte 2 | +| Field 3 (cont.) | | | | Field 4 | | | | Byte 3 | +| Spare Extension | | | | | | | | | +| | | | | | | | | | + +**Figure 10: Example of notation used for the definition of the frame structure** + +Unless otherwise indicated, fields which consist of multiple bits within a byte will have the more significant bit located at the higher bit position (indicated above frame in figure 10). In addition, if a field spans several bytes, more significant bits will be located in lower numbered bytes (right of frame in figure 10). + +On the Iub/Iur interface, the frame will be transmitted starting from the lowest numbered byte. Within each byte, the bits are sent according decreasing bit position (bit position 7 first). + +The parameters are specified giving the value range and the step (if not 1). The coding is done as follows (unless otherwise specified): + +- Unsigned values are binary coded. +- Signed values are coded with the 2's complement notation. + +Bits labelled "Spare" shall be set to zero by the transmitter and shall be ignored by the receiver. The *Spare Extension* IE indicates the location where new IEs can in the future be added in a backward compatible way. The *Spare Extension* IE shall not be used by the transmitter and shall be ignored by the receiver. + +## 6.2 Data frames + +### 6.2.1 Introduction + +The purpose of the user data frames is to transparently transport the transport blocks between Node B and SRNC. + +The protocol allows for multiplexing of coordinated dedicated transport channels, with the same transmission time interval, onto one transport bearer. + +The transport blocks of all the coordinated DCHs for one transmission time interval are included in one frame. + +SRNC indicates the multiplexing of coordinated dedicated transport channels in the appropriate RNSAP/NBAP message. + +### 6.2.2 UL DATA FRAME + +#### 6.2.2.1 UL DATA FRAME FOR DCH + +The structure of the UL DATA FRAME is shown in figure 11. + +![](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +|-------------------------------|---|---|------------------|-----------------------------|-----|---|---|-----|----------------| +| Header CRC | | | | | | | | FT | Header | +| CFN | | | | | | | | | | +| Spare bits 7-5 | | | TFI of first DCH | | | | | | | +| Spare bits 7-5 | | | TFI of last DCH | | | | | | | +| First TB of first DCH | | | | | | | | | Payload | +| First TB of first DCH (cont) | | | | | | | | Pad | | +| Last TB of first DCH | | | | | | | | | | +| Last TB of first DCH (cont) | | | | | | | | Pad | | +| First TB of last DCH | | | | | | | | | | +| First TB of last DCH (cont) | | | | | | | | Pad | | +| Last TB of last DCH | | | | | | | | | | +| Last TB of last DCH (cont) | | | | | | | | Pad | | +| QE | | | | | | | | | | +| CRCI of first TB of first DCH | | | | | | | | | | +| | | | | CRCI of last TB of last DCH | Pad | | | | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | + +**Figure 11: UL DATA FRAME structure** + +For the description of the fields see subclause 6.2.4. + +There are as many TFI fields as number of DCH multiplexed in the same transport bearer. + +The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). + +The size and the number of TBs for each DCH are defined by the correspondent TFI. + +If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). + +There is a CRCI for each TB included in the frame irrespective of the size of the TB, i.e. the CRCI is included also when the TB length is zero. If the CRCIs of one data frame do not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex. 3 CRCI bits require 5 bits of padding, but there are no CRCI bits and no padding, when the number of TBs is zero). + +The *Payload CRC* IE is optional, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). + +#### 6.2.2.2 UL DATA FRAME FOR E-DCH TYPE 1 + +The structure of the E-DCH UL DATA FRAME TYPE 1 is shown in Figure 11a. TYPE 1 frame structure is used when the E-DCH UL DATA FRAME is carrying MAC-es PDUs (TS 25.321 [16]). + +![](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-------------------------------------|--------------------|---|---|---------------------------------|---|---|---|------------------| +| Header CRC | | | | | | | | Header | +| Header CRC (cont) | | | | FSN | | | | | +| Spare bits 7-4 | | | | Number of subframes | | | | | +| CFN | | | | | | | | | +| Spare | N of HARQ Retransm | | | 1 st subframe number | | | | | +| N of MAC-es PDUs | | | | First DDI | | | | | +| First DDI cont | First N | | | | | | | | +| Last DDI | | | | | | | | | +| Last N cont | | | | Pad | | | | | +| Spare | N of HARQ Retransm | | | Last Subframe number | | | | | +| N of MAC-es PDUs | | | | First DDI | | | | | +| First DDI cont | First N | | | | | | | | +| Last DDI | | | | | | | | | +| Last N cont | | | | Pad | | | | | +| Spare bits 7-6 | | | | | | | | Payload | +| First MAC-es PDU of first Subframe | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | +| Second MAC-es PDU of first Subframe | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | +| Last MAC-es PDU of first Subframe | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | +| First MAC-es PDU of last Subframe | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | +| Second MAC-es PDU of last Subframe | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | +| Last MAC-es PDU of last Subframe | | | | | | | | | +| Spare Extension | | | | | | | | Optional Payload | +| Payload CRC | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | + +**Figure 11a: E-DCH UL DATA FRAME TYPE 1 structure** + +For the description of the fields see subclause 6.2.4. + +When there is an even, including zero, number of DDI + N field pairs for a subframe, then 4 bits padding is used as shown in the figure in order to have the octet aligned structure. + +The *Payload CRC* IE is optional in frames that contain a *Payload*, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The *Payload CRC* IE may only be present if the E-DCH UL data frame contains payload. + +#### 6.2.2.3 UL DATA FRAME FOR E-DCH TYPE 2 + +The structure of the E-DCH UL DATA FRAME TYPE 2 is shown in Figure 11b. TYPE 2 frame structure is used when the E-DCH UL DATA FRAME is carrying MAC-is PDUs (TS 25.321 [16]). + +![](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------------------------------------------|--------------------|---|---------------------------------|---|---|---|----| +| Header CRC | | | | | | | FT | +| Header CRC (cont) | | | FSN | | | | | +| Spare bits 7-6 | UL Mux info | | Number of subframes | | | | | +| CFN | | | | | | | | +| User Buffer Size (UB Size) | | | | | | | | +| User Buffer Size (UB Size) cont | | | | | | | | +| UB Size cont | Spare bits 5-6 | | Nr of MAC-is SDU in frame | | | | | +| Nr of MAC-is SDU in frame(cont) | | | | | | | | +| Spare | N of HARQ Retransm | | 1 st Subframe number | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | +| Spare | N of HARQ Retransm | | 2 nd Subframe number | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | +| | | | | | | | | +| Spare | N of HARQ Retransm | | Last Subframe number | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of 1st subframe | | | | | | | | +| MAC-is PDU descriptor of 2nd MAC-is PDU of 1st subframe | | | | | | | | +| | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of 1st subframe | | | | | | | | +| | | | | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of last subframe | | | | | | | | +| | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of last subframe | | | | | | | | +| First MAC-is PDU of first subframe | | | | | | | | +| Second MAC-is PDU of first subframe | | | | | | | | +| | | | | | | | | +| Last MAC-is PDU of first subframe | | | | | | | | +| | | | | | | | | +| First MAC-is PDU of last subframe | | | | | | | | +| | | | | | | | | +| Last MAC-is PDU of last subframe | | | | | | | | +| Spare Extension | | | | | | | | +| Payload CRC | | | | | | | | +| Payload CRC (cont) | | | | | | | | + +Frame header +Frame Payload +Optional Frame Payload + +**Figure 11b: E-DCH UL DATA FRAME TYPE 2 structure** + +For the description of the fields see subclause 6.2.4. + +The *Payload CRC* IE is optional in frames that contain a Payload, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The *Payload CRC* IE may only be present if the E-DCH UL data frame contains payload. + +### 6.2.3 DL DATA FRAME + +The structure of the DL DATA FRAME is shown in figure 12. + +![](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +|------------------------------|-------------|------------------|-------------|-------------|-------------|-------------|-------------|-------------------------|--| +| Header CRC | | | | | | | FT | Header | | +| CFN | | | | | | | | | | +| Spare bits 7-6 | | TFI of first DCH | | | | | | | | +| Spare bits 7-6 | | TFI of last DCH | | | | | | | | +| First TB of first DCH | | | | | | | | Payload | | +| First TB of first DCH (cont) | | | | | Pad | | | | | +| Last TB of first DCH | | | | | | | | | | +| Last TB of first DCH (cont) | | | | | | | Pad | | | +| First TB of last DCH | | | | | | | | | | +| First TB of last DCH (cont) | | | | | Pad | | | | | +| Last TB of last DCH | | | | | | | | | | +| Last TB of last DCH (cont) | | | | | Pad | | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | | | +| Spare bits 7-1 | | | | | | | CLTD-R | | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | Optional Payload | | + +**Figure 12: DL DATA FRAME structure** + +Bit 0 of New IE Flags in DL DATA FRAME structure indicates if CLTD-R is present (1) or not (0) in the octet following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in DL DATA FRAME shall be set to 0. + +Field length of *Spare Extension* IE in DL DATA FRAME is 0-30 octets. + +For the description of the fields see subclause 6.2.4. + +There are as many TFI fields as number of DCH multiplexed in the same transport bearer. + +The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). + +The size and the number of TBs for each DCH are defined by the correspondent TFI. + +If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). + +The *Payload CRC* IE is optional, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). + +### 6.2.4 Coding of information elements in data frames + +#### 6.2.4.1 Header CRC + +**Description:** Result of the CRC applied to the remaining part of the header, i.e. from bit 0 of the first byte (the *FT* IE) to the bit 0 (included) of the last byte of the header (not including the *Header CRC Cont* four bits), with one of the + +corresponding generator polynomials: + +$G(D) = D^7 + D^6 + D^2 + 1$ for the 7 bit header CRC, + +$G(D) = D^{11} + D^9 + D^8 + D^2 + D + 1$ for the 11 bit header CRC. + +See subclause 7.2. + +**Field Length:** 7 bits. 11 bits for UL Data Frame for E-DCH. + +#### 6.2.4.2 Frame Type (FT) + +**Description:** Describes if it is a control frame or a data frame. + +**Value range:** {0=data, 1=control}. + +**Field Length:** 1 bit. + +#### 6.2.4.3 Connection Frame Number (CFN) + +**Description:** Indicator as to which radio frame the first data was received on uplink or shall be transmitted on downlink. See TS 25.401 [2]. For E-DCH the Connection Frame Number shall indicate the radio frame when the HARQ process correctly decoded the data. + +For E-DCH apart from reordering purposes, CFN (and Subframe number) can be used for dynamic delay measurements. + +**Value range:** {0-255}. + +**Field length:** 8 bits. + +#### 6.2.4.4 Transport Format Indicator (TFI) + +**Description:** TFI is the local number of the transport format used for the transmission time interval. For information about what the transport format includes see TS 25.302 [3]. + +**Value range:** {0-31}. + +**Field length:** 5 bits. + +#### 6.2.4.5 Quality Estimate (QE) + +**Description:** The quality estimate is derived from the transport channel BER [FDD - or physical channel BER.] + +[FDD - If the DCH FP frame includes TB's for the DCH which was indicated as "selected" with the *QE-selector* IE in the control plane (TS 25.433 [4] TS 25.423 [6]), then the QE is the transport channel BER for the selected DCH. If no transport channel BER is available the QE is the physical channel BER.] + +[FDD - If the value of the *QE-Selector* IE equals "non-selected" for all DCHs in the DCH FP frame, then the QE is the physical channel BER.] + +[TDD - If no transport channel BER is available, then the QE shall be set to 0. This is in particular the case when no transport blocks have been received. The value of QE will be ignored by the RNC in this case.] + +The quality estimate shall be set to the transport channel BER [FDD - or physical channel BER] and be measured in the units TrCh\_BER\_LOG [FDD - and PhCh\_BER\_LOG respectively] (see TS 25.133 [7] and TS 25.123 [8]). The quality estimate is needed in order to select a transport block when all CRC indications are showing bad (or good) frame. The UL outer loop power control may also use the quality estimate. + +**Value range:** {0-255}. + +**Granularity:** 1. + +**Field length:** 8 bits. + +#### 6.2.4.6 Transport Block (TB) + +**Description:** A block of data to be transmitted or received over the air interface. The transport format indicated by the TFI describes the transport block length and transport block set size. See TS 25.302 [3]. + +**Field length:** The length of the TB is specified by the TFI. + +#### 6.2.4.7 CRC indicator (CRCI) + +**Description:** Indicates the correctness/incorrectness of the TB CRC received on the Uu interface. For every transport block included in the data frame a CRCI bit will be present, irrespective of the presence of a TB CRC on the Uu interface. If no CRC was present on the Uu for a certain TB, the corresponding CRCI bit shall be set to "0". + +**Value range:** {0=Correct, 1=Not Correct}. + +**Field length:** 1 bit. + +#### 6.2.4.8 Payload CRC + +**Description:** CRC for the payload. This field is optional. It is the result of the CRC applied to the remaining part of the payload, i.e. from the bit 7 of the first byte of the payload to the bit 0 of the byte of the payload before the *Payload CRC* IE, with the corresponding generator polynomial: + $G(D) = D^{16} + D^{15} + D^2 + 1$ . See clause 7.2. + +**Field length:** 16 bits. + +#### 6.2.4.9 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.2.4.10 Subframe Number + +**Description:** Indicates the subframe number in which the payload was received. Apart from reordering purposes, Subframe number (and CFN) can be used for dynamic delay measurements. [3.84 Mcps TDD, 7.68 Mcps TDD – This will always be set to "0".][1.28 Mcps TDD – This will be set to {0-1}.] + +**Value range:** {0-4} + +**Field length:** 3 bits. + +#### 6.2.4.11 Number of HARQ Retransmissions, NHR + +**Description:** Indicates the number of HARQ retransmissions used for successful decoding of the payload, or in case of HARQ decoding failure the number of HARQ retransmissions that were used at the time when the HARQ decoding failure was detected. The value 13 indicates that the actual number of retransmissions is inappropriate as input to the outer loop power control. The value 15 indicates that the Node B could not calculate the number of HARQ retransmissions. + +**Value range:** {0-15} + +Value {12}: Used for indicating that the number of HARQ retransmissions was 12 or higher. + +Value {13}: Used for indicating that the number of HARQ retransmissions shall not be used by the outer loop power control + +Values {14}: Reserved in this user plane revision. Shall be ignored by the receiver. + +Value {15}: Used for indicating that the number of HARQ retransmissions is unknown. + +**Field length:** 4 bits. + +#### 6.2.4.12 Number of Subframes + +**Description:** The *Number of Subframes* field indicates how many subframes that follows in the frame. [TDD – This will always be set to "1".] + +Note: A subframe has both a header portion and a payload portion in the frame. + +**Value range:** {1-16} + +The binary coding is derived from the value minus 1. E.g. value 1 is coded as binary “0000” and value 16 is coded as binary “1111”. + +Values {11, 12, 13, 14, 15, 16}: Reserved in this user plane revision. Shall be ignored by the receiver. + +**Field length:** 4 bits. + +#### 6.2.4.13 Number of MAC-es PDUs + +**Description:** Indicates the number of MAC-es PDUs in the user data frame in the payload part for the corresponding subframe number. + +**Value range:** {0-15} + +**Field length:** 4 bits. + +#### 6.2.4.14 Data Description Indicator, DDI + +**Description:** The *Data Description Indicator* is mapped directly from the DDI field received over the Uu. + +**Field length:** 6 bits. + +#### 6.2.4.15 Number of MAC-d PDUs, N + +**Description:** The *Number of MAC-d PDUs* is mapped directly from the N field received over the Uu. + +**Field length:** 6 bits. + +#### 6.2.4.16 FSN – Frame Sequence Number + +**Description:** The 4-bit *Frame Sequence Number* is incremented (modulo 16) for each transmitted data frame. Each flow generates its own Frame Sequence. [FDD – In case E-DCH UL flow multiplexing mode is used for secondary E-DCH, Node B shall set the value per carrier.] + +**Value range:** {0..15}. + +**Granularity:** 1. + +**Field length:** 4 bits. + +#### 6.2.4.17 Number of MAC-is PDUs + +**Description:** Indicates the number of MAC-is PDUs in the user data frame in the payload part for the corresponding subframe number. + +**Value range:** {0-15} + +**Field length:** 4 bits. + +#### 6.2.4.18 User Buffer size + +**Description:** Indicates the total size of the UL DATA FRAME TYPE 2 in octets + +**Value range:** {0-262 140}. + +**Field length:** 18 bits. + +#### 6.2.4.19 Number of MAC-is SDU in frame + +**Description:** Total number of MAC-is SDUs in all MAC-is PDUs in the UL DATA FRAME TYPE 2. + +**Value range:** {0-4095}. + +**Field length:** 12 bits. + +#### 6.2.4.20 MAC-is PDU descriptor + +**Description:** The *MAC-is PDU descriptor* contains the Length (L), Logical channel identifier (LCH-ID) and Flag (F) fields mapped directly from the "MAC-i Header n" field ( $n > 0$ ) received over the Uu (TS 25.321 [16]). + +**Field length:** variable; length of *MAC-is PDU descriptor* in octets = $2 \times$ number of MAC-is SDU contained in the corresponding MAC-is PDU as described in TS 25.321 [16]. + +#### 6.2.4.21 UL Multiplexing Information (UL Mux Info)[FDD] + +**Description:** Applicable to Multi Cell E-DCH operation in E-DCH UL flow multiplexing mode. Indicates the frequency of the cell in which the MAC-i frame was received - primary UL frequency or secondary UL frequency. + +Primary UL frequency Value = "0" + +Secondary UL frequency Value = "1" + +In separate Iub transport bearer mode or non Multi Cell E-DCH operation Value = "0" shall be used, ignored by the receiver + +**Value range:** {0-3}. + +Values {2, 3}: Reserved in this user plane revision. Shall be ignored by the receiver. + +**Field length:** 2 bits. + +#### 6.2.4.22 UL CLTD Removal (CLTD-R)[FDD] + +**Description:** Indicator of the removal of UL CLTD + +**Value range:** {0= UL CLTD not relevant, 1= UL CLTD Removal}. + +**Field length:** 1 bit. + +## 6.3 Control frames + +### 6.3.1 Introduction + +Control frames are used to transport control information between SRNC and Node B. + +On the uplink, these frames are not combined – all frames are passed transparently from Node B to SRNC. On the downlink, the same control frame is copied and sent transparently to all the Node Bs from the SRNC. + +The structure of the control frames is shown in the figure 13. + +![](92b615e70a7ecf197adf6e9b513ebd2c_img.jpg) + +| | | | | | | | | +|----------------------------|---|---|---|---|---|---|----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Frame CRC | | | | | | | FT | +| Control Frame Type | | | | | | | | +| Control Information | | | | | | | | +| Control Information (cont) | | | | | | | | +| Spare Extension | | | | | | | | + +| | +|---------------------------------| +| Header | +| Payload
(variable
length) | + +| | +|---------------------------------| +| Header | +| Payload
(variable
length) | + +**Figure 13: General structure of the control frames** + +*Control Frame Type* IE defines the type of the control frame. + +The structure of the header and the payload of the control frames is defined in the following subclauses. + +### 6.3.2 Header structure of the control frames + +#### 6.3.2.1 Frame CRC + +**Description:** It is the result of the CRC applied to the remaining part of the frame, i.e. from bit 0 of the first byte of the header (the *FT IE*) to bit 0 of the last byte of the payload, with the corresponding generator polynomial: $G(D) = D^7+D^6+D^2+1$ . See subclause 7.2. + +**Field Length:** 7 bits. + +#### 6.3.2.2 Frame Type (FT) + +**Description:** Describes if it is a control frame or a data frame. + +**Value range:** {0=data, 1=control}. + +**Field Length:** 1 bit. + +#### 6.3.2.3 Control Frame Type + +**Description:** Indicates the type of the control information (information elements and length) contained in the payload. + +**Value:** The values are defined in table 1. + +**Table 1** + +| Control frame type | Coding | +|----------------------------------|-----------| +| OUTER LOOP POWER CONTROL | 0000 0001 | +| TIMING ADJUSTMENT | 0000 0010 | +| DL SYNCHRONISATION | 0000 0011 | +| UL SYNCHRONISATION | 0000 0100 | +| Reserved Value | 0000 0101 | +| DL NODE SYNCHRONISATION | 0000 0110 | +| UL NODE SYNCHRONISATION | 0000 0111 | +| RX TIMING DEVIATION | 0000 1000 | +| RADIO INTERFACE PARAMETER UPDATE | 0000 1001 | +| TIMING ADVANCE | 0000 1010 | +| TNL CONGESTION INDICATION | 0000 1011 | + +**Field length:** 8 bits. + +The "Reserved Value" for the *Control Frame Type* IE shall not be used by the SRNC. A control frame whose *Control Frame Type* IE is set to the "Reserved Value" shall be ignored by the Node B. + +### 6.3.3 Payload structure and information elements + +#### 6.3.3.1 TIMING ADJUSTMENT + +##### 6.3.3.1.1 Payload structure + +Figure 14 shows the structure of the payload when control frame is used for the timing adjustment. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------------|---|---|---|---|---|---|---|------------| +| CFN | | | | | | | | | +| ToA | | | | | | | | | +| ToA (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 14: Structure of the payload for the TIMING ADJUSTMENT control frame** + +##### 6.3.3.1.2 CFN + +**Description:** The CFN value is extracted from the corresponding DL DATA FRAME. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.1.3 Time of Arrival (ToA) + +**Description:** Time difference between the arrival of the DL frame with respect to ToAWE (based on the CFN value in the frame). + +**Value range:** {-1280, +1279.875 msec}. + +**Granularity:** 125 µs. + +**Field length:** 16 bits. + +##### 6.3.3.1.4 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.3.3.2 DL SYNCHRONISATION + +##### 6.3.3.2.1 Payload structure + +Figure 15 shows the structure of the payload when control frame is used for the user plane synchronisation. + +![](3d832e1d9f2029a103f70128d8287f43_img.jpg) + +| | | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|----------|----------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 15: Structure of the payload for the DL SYNCHRONISATION control frame** + +##### 6.3.3.2.2 CFN + +**Description:** The CFN value is the target CFN and used to calculate ToA. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.2.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.3 UL SYNCHRONISATION + +##### 6.3.3.3.1 Payload structure + +Figure 16 shows the structure of the payload when the control frame is used for the user plane synchronisation. + +![](e4cc1eed414abddb18a100c9b3ee64e0_img.jpg) + +| | | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|----------|----------|-----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| ToA | | | | | | | | | +| ToA (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32bytes | + +**Figure 16: Structure of the UL SYNCHRONISATION control frame** + +##### 6.3.3.3.2 CFN + +**Description:** The CFN value is extracted from the corresponding DL SYNCHRONISATION control frame. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.3.3 Time of Arrival (ToA) + +The *ToA* IE is described in subclause 6.3.3.1.3. + +##### 6.3.3.3.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.4 OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD] + +##### 6.3.3.4.1 Payload structure + +Figure 17 shows the structure of the payload when control frame is used for the UL outer loop power control. + +![](b81d1613e285a9353171cdc5ef97a1f0_img.jpg) + +| | | | | | | | | +|----------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| UL SIR TARGET | | | | | | | | +| New
IE fl
7(E) | New
IE fl 6 | New
IE fl 5 | New
IE fl 4 | New
IE fl 3 | New
IE fl 2 | New
IE fl 1 | New
IE fl 0 | +| Spare bits 7-2 | | | | | | UL Mux Infor | | +| Spare Extension | | | | | | | | + +0-30 bytes + +**Figure 17: Structure of the payload for OUTER LOOP PC control frame** + +Bit 0 of New IE Flags in OUTER LOOP POWER CONTROL indicates if the UL Mux Info is present (1) or not present (0) in the byte following the *New IE Flags* IE. + +Bits 1 through 6 of New IE Flags in OUTER LOOP POWER CONTROL shall be set to 0. + +##### 6.3.3.4.2 SIR Target + +**Description:** Value (in dB) of the SIR target to be used by the UL inner loop power control. + +SIR Target is given in the unit UL\_SIR\_TARGET where: + +| | | +|---------------------|----------------------| +| UL_SIR_TARGET = 000 | SIR Target = -8.2 dB | +| UL_SIR_TARGET = 001 | SIR Target = -8.1 dB | +| UL_SIR_TARGET = 002 | SIR Target = -8.0 dB | +| ... | | +| UL_SIR_TARGET = 254 | SIR Target = 17.2 dB | +| UL_SIR_TARGET = 255 | SIR Target = 17.3 dB | + +**Value range:** {-8.2...17.3 dB}. + +**Granularity:** 0.1 dB. + +**Field length:** 8 bits. + +##### 6.3.3.4.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +##### 6.3.3.4.4 UL Mux Info + +The *UL Mux Info* IE is described in subclause [6.2.4.21](#). + +#### 6.3.3.5 DL NODE SYNCHRONISATION + +##### 6.3.3.5.1 Payload structure + +Figure 18 shows the structure of the payload for the DL NODE SYNCHRONISATION control frame. + +![](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------------|---|---|---|---|---|---|---|------------| +| T1 | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T1 (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 18: Structure of the payload for the DL NODE SYNCHRONISATION control frame** + +##### 6.3.3.5.2 T1 + +**Description:** RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. + +**Value range:** As defined in subclause 6.3.3.6.2. + +**Field length:** 24 bits. + +##### 6.3.3.5.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.6 UL NODE SYNCHRONISATION + +##### 6.3.3.6.1 Payload structure + +The payload of the UL NODE SYNCHRONISATION control frames is shown in figure 19. + +![](eb2ecad845f6639684b50f51a346cec9_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------------|---|---|---|---|---|---|---|------------| +| T1 | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T2 | | | | | | | | | +| T2 (cont) | | | | | | | | | +| T2 (cont) | | | | | | | | | +| T3 | | | | | | | | | +| T3 (cont) | | | | | | | | | +| T3 (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 19: Structure of the payload for UL NODE SYNCHRONISATION control frame** + +##### 6.3.3.6.2 T1 + +**Description:** T1 timer is extracted from the correspondent DL NODE SYNCHRONISATION control frame. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.3 T2 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B received the correspondent DL NODE SYNCHRONISATION control frame through the SAP from the transport layer. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.4 T3 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B sends the frame through the SAP to the transport layer. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.5 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.7 RX TIMING DEVIATION [3.84 Mcps and 7.68Mcps TDD] + +##### 6.3.3.7.1 Payload structure + +Figure 20 shows the structure of the payload when the control frame is used for the Rx timing deviation. + +![](4d3ae95eface3b9d7eeeaa18e7036024_img.jpg) + +| | | | | | | | | +|------------------------------------------------------------|-------------|-------------|-------------|-------------|-----------------|----------------------------|-------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CFN | | | | | | | | +| Rx Timing Deviation | | | | | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | +| Spare bits 7-2 for 3.84Mcps
Spare bits 7-3 for 7.68Mcps | | | | | E-RUCCH CH flag | Rx Timing Deviation (cont) | | +| Spare Extension | | | | | | | | + +0-30 bytes + +**Figure 20: Structure of the payload for RX TIMING DEVIATION control frame** + +Bit 0 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the *New IE Flags* IE. + +Bit 1 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME indicates if the E-RUCCH Flag is present (1) or not present (0) in the byte (bit 1 for 3.84 Mcps TDD, bit2 for 7.68 Mcps TDD) following the *New IE Flags* IE. + +Bits 2 through 6 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME shall be set to 0. + +##### 6.3.3.7.2 Rx Timing Deviation [3.84 Mcps TDD] + +**Description:** Measured Rx Timing deviation as a basis for timing advance. + +**Value range:** {-1024, ..., +1023 chips}. + +$$\{N * 4 - 256\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1) * 4 - 256\} \text{ chips}$$ + +With $N = 0, 1, \dots, 127$ + +$$\{(N-128)*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N-127)*4 - 1024\} \text{ chips}$$ + +With $N = 128, 129, \dots, 319$ + +$$\{N*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N+1)*4 - 1024\} \text{ chips}$$ + +With $N = 320, 321, \dots, 511$ + +**Granularity:** 4 chips. + +**Field length:** 9 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant bit is contained in the RX timing deviation (continuation) field. + +##### 6.3.3.7.2A Rx Timing Deviation [7.68 Mcps TDD] + +**Description:** Measured Rx Timing deviation as a basis for timing advance. + +**Value range:** {-2056, ..., +2055} chips + +$$\{N*4 - 2056\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1)*4 - 2056\} \text{ chips}$$ + +With N = 0, 1, ..., 1027 + +**Granularity:** 4 chips. + +**Field length:** 10 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant 2 bits are contained in the RX timing deviation (continuation) field. + +##### 6.3.3.7.2B E-RUCCH Flag + +**Description:** Indicates whether the timing deviation is derived from a conventional E-RUCCH (carrying Scheduling Information) reception or a TA Request reception. + +**Value range:** {0 conventional E-RUCCH reception, 1 TA Request reception} + +**Field length:** 1 bit. + +##### 6.3.3.7.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +Field length of *Spare Extension* IE in RX TIMING DEVIATION CONTROL FRAME is 0-30 octets. + +##### 6.3.3.7.4 CFN + +**Description:** The CFN value in this control frame is the CFN when the RX timing deviation was measured. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.7.5 New IE Flags + +**Description:** The *New IE Flags* IE is only present if at least one new IE is present. The *New IE Flags* IE contains flags indicating which new IEs that are present following the *New IE Flags* IE. The last bit position of the *New IE Flags* IE is used as the Extension Flag to allow the extension of the *New IE Flags* IE in the future. Extension octets of the *New IE Flags* IE shall follow directly after the first octet of the *New IE Flags* IE. When an extension octet of the *New IE Flags* IE is present, then all previous extension octets of the *New IE Flags* IE and the *New IE Flags* IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs. + +**Value range:** + +Bit 0-6 of each octet: Indicates if a new IE is present (1) or not present (0) in the bytes following the *New IE Flags* IE. The meaning of each bit is explained in the corresponding DATA FRAME subclause; + +Bit 7 of each octet: Indicates if an extension octet of the *New IE Flags* IE follows (1) or not (0). + +**Field length:** 1 – 31 octets. + +#### 6.3.3.8 DSCH TFCI SIGNALLING [FDD] + +##### 6.3.3.8.1 Payload structure + +Void. + +##### 6.3.3.8.2 TFCI (field 2) + +Void. + +##### 6.3.3.8.3 Spare Extension + +Void. + +##### 6.3.3.8.4 CFN + +Void. + +#### 6.3.3.9 RADIO INTERFACE PARAMETER UPDATE [FDD] + +##### 6.3.3.9.1 Payload structure + +The figure 22 shows the structure of the payload when the control frame is used for signalling radio interface parameter updates. + +![](4b587081b669e7c6695b0e5db5ea7f6d_img.jpg) + +| | | | | | | | | +|----------------------------------------|--------------------------------------------------------------|---------------|----------|----------|----------|----------|----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Radio Interface Parameter Update Flags | | | | | | | | +| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CRN | | | | | | | | +| Spare bits 7-6 | | DPC Mode | TPC PO | | | | | +| Multiple RL sets Indicator | Multiple RL Sets Indicator on the secondary uplink frequency | Reserved Bits | | | | | | +| Spare | Reserved Bits | | | | | | | +| Spare | MAX_UE_TX_POW | | | | | | | +| Spare Extension | | | | | | | | + +0-29 bytes + +**Figure 22: Structure of the payload for the RADIO INTERFACE PARAMETER UPDATE control frame** + +##### 6.3.3.9.2 Radio Interface Parameter Update flags + +**Description:** Contains flags indicating which information is valid in this control frame. + +###### **Value range:** + +Bit 0: Indicates if the 3rd byte of the control frame payload contains a valid CFN (1) or not (0); + +Bit 1: Indicates if the 4th byte (bits 0-4) of the control frame payload contains a valid TPC PO (1) or not (0); + +Bit 2: Indicates if the 4th byte (bit 5) of the control frame payload contains a valid DPC mode (1) or not (0); + +Bit 3: Reserved bit; + +Bit 4: Reserved bit; + +Bit 5: Indicates if the 5th byte (bit 7) of the control frame payload contains a valid Multiple RL Sets Indicator (1) or not (0); + +Bit 6: Indicates if the 7th byte (bits 0-6) of the control frame payload contains a valid Maximum UE TX Power (1) or not (0); + +Bit 7: Indicates if the 5th byte (bit 6) of the control frame payload contains a valid Multiple RL Sets Indicator on the secondary uplink frequency (1) or not (0); + +Bit 8-15: Set to (0): reserved in this user plane revision. Any indicated flags shall be ignored by the receiver. + +Reserved bits shall be set to 0 by the SRNC and ignored by the Node B. + +**Field length:** 16 bits. + +##### 6.3.3.9.3 TPC Power Offset (TPC PO) + +**Description:** Power offset to be applied in the DL between the DPDCH information and the TPC bits on the DPCCH as specified in the clause 5.2 of TS 25.214 [12]. + +**Value range:** {0-7.75 dB}. + +**Granularity:** 0.25 dB. + +**Field length:** 5 bits. + +##### 6.3.3.9.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +##### 6.3.3.9.4A CFN + +**Description:** The CFN value indicates when the presented parameters shall be applied. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.9.5 DPC Mode + +**Description:** DPC mode to be applied in the UL. + +**Value range:** {0,1}. + +The DPC mode shall be applied as specified in TS 25.214 [12]. + +**Field length:** 1 bit. + +##### 6.3.3.9.6 TFCI Power Offset (TFCI PO) + +Void. + +##### 6.3.3.9.7 TFCI Power Offset for primary cell (TFCI PO\_primary) + +Void. + +##### 6.3.3.9.8 Multiple RL Sets Indicator + +**Description:** Multiple RL Sets Indicator indicates whether the UE has several RL Sets or not. + +**Value range:** {0=UE has only one RL Set, 1=UE has several RL Sets}. + +**Field length:** 1 bit. + +##### 6.3.3.9.9 Maximum UE TX Power + +**Description:** The Maximum UE TX Power is the lower of the maximum output power of the UE power class, defined in ref TS 25.101 [14], and the Maximum Allowed UL TX Power that is also sent to the UE, see ref TS 25.331 [15]. + +Maximum UE TX Power is given in the unit MAX\_UE\_TX\_POW where: + +| | | +|--------------------|-------------------------------| +| MAX_UE_TX_POW = 00 | Maximum UE TX Power = -55 dBm | +| MAX_UE_TX_POW = 01 | Maximum UE TX Power = -54 dBm | +| MAX_UE_TX_POW = 02 | Maximum UE TX Power = -53 dBm | +| ... | | +| MAX_UE_TX_POW = 87 | Maximum UE TX Power = 32 dBm | +| MAX_UE_TX_POW = 88 | Maximum UE TX Power = 33 dBm | + +**Value range:** {-55..33 dBm}. + +**Granularity:** 1 dBm + +**Field length:** 7 bit + +##### 6.3.3.9.10 Multiple RL Sets Indicator on the secondary uplink frequency + +**Description:** Multiple RL Sets Indicator indicates whether the UE has several RL Sets or not on the secondary uplink frequency. + +**Value range:** {0=UE has only one RL Set, 1=UE has several RL Sets}. + +**Field length:** 1 bit. + +#### 6.3.3.10 TIMING ADVANCE [3.84Mcps and 7.68 Mcps TDD] + +##### 6.3.3.10.1 Payload structure + +Figure 23 shows the structure of the payload when the control frame is used for timing advance. + +![](2c532a9bb51e081048d718316f509294_img.jpg) + +| | | | | | | | | | +|-----------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| TA | | | | | | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | | +| Spare bits 7-1 | | | | | | | | TA (cont) | +| Spare Extension | | | | | | | | 0-30 bytes | + +**Figure 23a: Structure of the TIMING ADVANCE control frame for 7.68Mcps TDD** + +![](3e73823c346c1d339cca8e25b296bf1a_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| TA | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 23b: Structure of the TIMING ADVANCE control frame for 3.84Mcps TDD** + +[7.68Mcps TDD - Bit 0 of New IE Flags in TIMING ADVANCE CONTROL FRAME indicates if the extended bits of the TA are present (1) or not present (0) in the byte following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in TIMING ADVANCE CONTROL FRAME shall be set to 0.] + +##### 6.3.3.10.2 CFN + +**Description:** The CFN value in this control frame is the frame that the timing advance will occur. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +6.3.3.10.3 TA [3.84 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0-1020 chips}. + +**Granularity:** 4 chips. + +**Field length:** 8 bits. + +6.3.3.10.3A TA [7.68 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0-2044 chips}. + +**Granularity:** 4 chips. + +**Field length:** 9 bits. + +6.3.3.10.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +[7.68Mcps TDD - Field length of *Spare Extension* IE in TIMING ADVANCE CONTROL FRAME is 0-30 octets]. + +6.3.3.10.5 New IE Flags [7.68Mcps TDD] + +The *New IE Flags* IE is described in subclause 6.3.3.7.5. + +6.3.3.11 TNL CONGESTION INDICATION + +6.3.3.11.1 Payload structure + +Figure 24 shows the structure of the payload when the control frame is used for TNL CONGESTION INDICATION. + +![](fd856db65d36f12fa7dd9b1a1f03eb75_img.jpg) + +| | | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|-------------------|----------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| Spare bits 7-2 | | | | | | Congestion Status | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 24: Structure of the TNL CONGESTION INDICATION control frame** + +6.3.3.11.2 Congestion Status + +**Description:** The Congestion Status indicates whether there is transport network congestion or not. + +**Value range:** + +- 0 No TNL congestion +- 1 Reserved for future use. +- 2 TNL Congestion – detected by delay build-up +- 3 TNL Congestion – detected by frame loss + +**Field length:** 2 bits. + +6.3.3.11.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +# 7 Handling of Unknown, Unforeseen and Erroneous Protocol Data + +## 7.1 General + +A frame protocol frame with illegal or not comprehended parameter value shall be ignored. Frame protocol frames sent with a CFN in which the radio resources assigned to the associated Iub data port are not available, shall be ignored. + +Frame protocol data frames with CFN value that does not fulfil the requirement set in clause [FDD - 4.2.14 of TS 25.212 [9]] [TDD - 4.2.12 of TS 25.222 [10]], shall be ignored. + +## 7.2 Error detection + +Error detection is provided on frames through a Cyclic Redundancy Check. The length of the CRC for the payload is 16 bits, for the data frame header 7 or 11 bits and for control frames it is 7 bits. + +### 7.2.1 CRC Calculation + +The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{CRC16}(D) = D^{16} + D^{15} + D^2 + 1$$ + +$$g_{CRC11}(D) = D^{11} + D^9 + D^8 + D^2 + D + 1$$ + +$$g_{CRC7}(D) = D^7 + D^6 + D^2 + 1$$ + +Denote the bits in a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ , and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of a protected data and $L_i$ is 16, 11 or 7 depending on the CRC length. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial for the payload + +$$a_1 D^{A_i+15} + a_2 D^{A_i+14} + \dots + a_{A_i} D^{16} + p_1 D^{15} + p_2 D^{14} + \dots + p_{15} D^1 + p_{16}$$ + +yields a remainder equal to 0 when divided by $g_{CRC16}(D)$ , the polynomial for the data frame header with 11 bit CRC + +$$a_1 D^{A_i+11} + a_2 D^{A_i+10} + \dots + a_{A_i} D^{11} + p_1 D^{10} + p_2 D^9 + \dots + p_{10} D^1 + p_{11}$$ + +yields a remainder equal to 0 when divided by $g_{CRC11}(D)$ and the polynomial for the data frame header with 7 bit CRC and control frame + +$$a_1 D^{A_i+6} + a_2 D^{A_i+5} + \dots + a_{A_i} D^7 + p_1 D^6 + p_2 D^5 + \dots + p_6 D^1 + p_7$$ + +yields a remainder equal to 0 when divided by $g_{CRC7}(D)$ . If $A_i = 0$ , $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ . + +#### 7.2.1.1 Relation between input and output of the Cyclic Redundancy Check + +The bits after CRC attachment are denoted by $b_1, b_2, b_3, \dots, b_{B_i}$ , where $B_i = A_i + L_i$ . + +The parity bits for the payload are attached at the end of the frame: + +$$b_k = a_k \quad k = 1, 2, 3, \dots, A_i$$ + +$$b_k = p_{(k-A_i)} \quad k = A_i + 1, A_i + 2, A_i + 3, \dots, A_i + L_i$$ + +The parity bits for the frame header and the control frames are attached at the beginning of the frame: + +$$b_k = p_k \quad k = 1, 2, 3, \dots, L_i$$ + +$$b_k = a_{(k-L_i)} \quad k = L_i + 1, L_i + 2, L_i + 3, \dots, L_i + A_i$$ + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|---------|------------------------------------------------------|-----------|-------------|--------------------------------------------------------| +| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment | +| RAN_05 | - | - | - | 3.0.0 | Approved at TSG RAN #5 and placed under Change Control | +| RAN_06 | 3.0.0 | - | RP-99758 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_06 | 3.0.0 | - | RP-99759 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_06 | 3.0.0 | 005 | RP-99760 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_07 | 3.1.0 | - | - | 3.2.0 | Approved at TSG RAN #7 | +| RAN_08 | 3.2.0 | - | RP-000248 | 3.3.0 | Approved at TSG RAN #8 | +| RAN_09 | 3.3.0 | 026
028
029
031
032
033
034
035 | RP-000384 | 3.4.0 | Approved at TSG RAN #9 | +| RAN_10 | 3.4.0 | 036
037
038 | RP-000625 | 3.5.0 | Approved at TSG RAN #10 | +| RAN_11 | 3.5.0 | 039
040
043 | RP-010122 | 3.6.0 | Approved at TSG RAN #11 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-------------|-----|--------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| March 01 | 11 | RP-010160 | 045 | | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | +| March 01 | 11 | RP-010164 | 042 | | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | +| 06/2001 | 12 | RP-010381 | 050,
054 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 | +| 06/2001 | 12 | RP-010395 | 047 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 | +| 09/2001 | 13 | RP-010586 | 056 | | Transport bearer replacement clarification | 4.1.0 | 4.2.0 | +| 09/2001 | 13 | RP-010586 | 063 | 1 | General Corrections on lub_lur UP protocol for DCH data streams | 4.1.0 | 4.2.0 | +| 09/2001 | 13 | RP-010598 | 057 | | Uplink power control for LCR TDD | 4.1.0 | 4.2.0 | +| 09/2001 | 13 | RP-010598 | 060 | 1 | DPC Mode Correction in the User Plane | 4.1.0 | 4.2.0 | +| 09/2001 | 13 | RP-010598 | 061 | | 25.427 Correction | 4.1.0 | 4.2.0 | +| 12/2001 | 14 | RP-010860 | 067 | | Correction to inconsistencies in TS 25.427 | 4.2.0 | 4.3.0 | +| 12/2001 | 14 | RP-010860 | 069 | 1 | Clarifications on data/control frame support | 4.2.0 | 4.3.0 | +| 12/2001 | 14 | RP-010860 | 071 | | Specification Notations | 4.2.0 | 4.3.0 | +| 12/2001 | 14 | RP-010860 | 077 | 2 | Terminology Correction – Rel4 | 4.2.0 | 4.3.0 | +| 03/2002 | 15 | RP-020194 | 082 | 1 | DCH FP changes for TFCI power control in DSCH hard split mode | 4.3.0 | 5.0.0 | +| 12/2002 | 18 | RP-020744 | 088 | | Correction for the DL DPDCH transmission | 5.0.0 | 5.1.0 | +| 09/2003 | 21 | RP-030447 | 089 | 1 | Coordination with RRC about the TFS of DL DCH for HS-DSCH | 5.1.0 | 5.2.0 | +| 12/2003 | 22 | RP-030678 | 090 | 1 | Signalling support for soft handover indicator | 5.2.0 | 5.3.0 | +| 12/2003 | 22 | RP-030682 | 093 | 1 | Spare Extension in Data frame | 5.2.0 | 5.3.0 | +| 12/2003 | 22 | - | - | - | Introduction of Release 6 specification | 5.3.0 | 6.0.0 | +| 12/2004 | 26 | RP-040440 | 095 | 2 | Changes on 25.427 due to the introduction of Enhanced Uplink | 6.0.0 | 6.1.0 | +| 03/2005 | 27 | RP-050054 | 097 | - | Reference for QE mapping is incorrect | 6.1.0 | 6.2.0 | +| 03/2005 | 27 | RP-050137 | 102 | 1 | EDCH Frame format update | 6.1.0 | 6.2.0 | +| 06/2005 | 28 | RP-050234 | 103 | | Correction to the range of TDD parameter in RX TIMING DEVIATION [3.84Mcps TDD] FRAME | 6.2.0 | 6.3.0 | +| 06/2005 | 28 | RP-050229 | 104 | 1 | Support for HARQ Retransmission and Failure Indication | 6.2.0 | 6.3.0 | +| 06/2005 | 28 | RP-050229 | 105 | | Clarification of the use of CFN for Enhanced Uplink | 6.2.0 | 6.3.0 | +| 06/2005 | 28 | RP-050229 | 106 | | Removing the abbreviation SFN for Subframe Number | 6.2.0 | 6.3.0 | +| 06/2005 | 28 | RP-050222 | 108 | 1 | Feature clean-up: Removal of DSCH (FDD mode) | 6.2.0 | 6.3.0 | +| 06/2005 | 28 | RP-050229 | 109 | 1 | Transport Network CongestionDetection and Control | 6.2.0 | 6.3.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 09/2005 | 29 | RP-050434 | 110 | 1 | CRC-11 Polynomial for E-DCH | 6.3.0 | 6.4.0 | +| 09/2005 | 29 | RP-050434 | 115 | 1 | Value range missing for Number of Subframes and Number of Mac-es PDUs fields | 6.3.0 | 6.4.0 | +| 09/2005 | 29 | RP-050434 | 118 | 3 | Maximum UE Tx Power for EDCH | 6.3.0 | 6.4.0 | +| 12/2005 | 30 | RP-050702 | 120 | 1 | Conditions for sending HARQ Failure | 6.4.0 | 6.5.0 | +| 12/2005 | 30 | RP-050702 | 121 | 1 | HARQ failure shall be sent on highest bearer | 6.4.0 | 6.5.0 | +| 03/2006 | 31 | RP-060066 | 125 | 1 | HARQ Failure Indication due to MAC-e Reset in UE | 6.5.0 | 6.6.0 | +| 03/2006 | 31 | RP-060066 | 126 | 2 | Clarification for HARQ Failure Indication | 6.5.0 | 6.6.0 | +| 03/2006 | 31 | RP-060073 | 124 | | Introduction of 7.68Mcps TDD option | 6.6.0 | 7.0.0 | +| 06/2006 | 32 | RP-060290 | 127 | 1 | Release 7 Timing Advance (3.84 Mpcs and 7.68 Mcps TDD) | 7.0.0 | 7.1.0 | +| 06/2006 | 32 | RP-060284 | 129 | 1 | Missing new frame protocol services in list of services in clause 4.1 | 7.0.0 | 7.1.0 | +| 09/2006 | 33 | RP-060511 | 133 | 1 | Introduction of 3.84 Mcps and 7.68Mcps TDD Enhanced Uplink | 7.1.0 | 7.2.0 | +| 12/2006 | 34 | RP-060709 | 135 | 1 | Fast Reconfiguration | 7.2.0 | 7.3.0 | +| 12/2006 | 34 | RP-060699 | 137 | 1 | No Payload CRC if no Payload | 7.2.0 | 7.3.0 | +| 12/2006 | 34 | RP-060702 | 139 | | TNL congestion indication signal not applicable for DCH | 7.2.0 | 7.3.0 | +| 12/2006 | 34 | RP-060837 | 140 | 1 | Consistency of Specification Notations | 7.2.0 | 7.3.0 | +| 03/2007 | 35 | RP-070062 | 141 | 1 | Introduction of 1.28 Mcps TDD Enhanced Uplink | 7.3.0 | 7.4.0 | +| 09/2007 | 37 | RP-070629 | 142 | | Timing Advance Corrections for 3.84/7.68 Mcps TDD EDCH | 7.4.0 | 7.5.0 | +| 03/2008 | 39 | RP-080083 | 144 | 1 | Introduction of Improved L2 for Uplink | 7.5.0 | 8.0.0 | +| 12/2008 | 42 | RP-080843 | 145 | | Corrections to IE definitions for UL DATA FRAME FOR E-DCH TYPE 2 | 8.0.0 | 8.1.0 | +| 12/2008 | 42 | RP-080855 | 146 | 1 | Improved EUL power control at UE power limitation freeze SIR target | 8.0.0 | 8.1.0 | +| 12/2009 | 46 | RP-091181 | 149 | | Correction on value range for Number of MAC-is SDU in frame | 8.1.0 | 8.2.0 | +| 12/2009 | - | - | - | - | Creation of version 9.0.0 based on v 8.2.0 | 8.2.0 | 9.0.0 | +| 12/2009 | 46 | RP-091186 | 148 | 1 | Introduction of Dual-Cell HSUPA | 8.2.0 | 9.0.0 | +| 12/2010 | | | | | Creation of version 10.0.0 based on v.9.0.0 | 9.0.0 | 10.0.0 | +| 12/2010 | 50 | RP-101274 | 150 | 1 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.0.0 | 10.0.0 | +| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.0 | 10.0.1 | +| 06/2011 | 52 | RP-110688 | 151 | 2 | Correction to mapping of MAC-is SDU to MAC-d PDU | 10.0.1 | 10.1.0 | +| 06/2011 | 52 | RP-110686 | 153 | | Correction related to the References and clean-up of 25.427 | 10.0.1 | 10.1.0 | +| 12/2011 | | | | | Creation of version 11.0.0 based on v.10.1.0 | 10.1.0 | 11.0.0 | +| 12/2011 | 52 | RP-111653 | 154 | 1 | Indicator to the old UL CLTD Control Node B | 10.1.0 | 11.0.0 | +| 06/2014 | | | | | Creation of version 12.0.0 based on v.11.0.0 | 11.0.0 | 12.0.0 | +| 06/2014 | 64 | RP-140895 | 159 | - | Correction on Multiple RL Sets Indicator for DC-HSUPA | 11.0.0 | 12.0.0 | +| 09/2014 | 65 | RP-141608 | 161 | 1 | Rapporteur Review - Change figures to table style | 12.0.0 | 12.1.0 | +| 12/2015 | | | | | Creation of version 13.0.0 based on v.12.1.0 | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25432/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-16/25_series/25432/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e05b670bf2cd17f30f64308b6e00de74ec47931 --- /dev/null +++ b/marked/Rel-16/25_series/25432/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27a4de273f70bdcc413f830c55dd409bc43e57caf2795eb8530cda792eaec909 +size 45450 diff --git a/marked/Rel-16/25_series/25432/raw.md b/marked/Rel-16/25_series/25432/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8a56fcae21b4703c40a60846c898e11860664cf7 --- /dev/null +++ b/marked/Rel-16/25_series/25432/raw.md @@ -0,0 +1,193 @@ + + + + + + +# --- 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 Data Link Layer ..... | 6 | +| 4.1 ATM Transport Option ..... | 6 | +| 4.1.1 Protection switching at ATM Layer..... | 6 | +| 4.2 Data Link Layer for IP Transport Option..... | 6 | +| 5 NBAP signalling bearer ..... | 7 | +| 5.1 Introduction ..... | 7 | +| 5.2 Signalling bearer in case of ATM Transport Option..... | 7 | +| 5.3 Signalling bearer in case of IP Transport Option..... | 7 | +| Annex A (informative): Change history..... | 9 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the signalling transport related to NBAP signalling to be used across the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The radio network control signalling between these nodes is based on the Node B application part (NBAP). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN signalling ATM adaptation layer (SAAL) overview description". +- [2] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user network interface (SSCF–UNI)". +- [3] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer – Service specific connection oriented protocol (SSCOP)". +- [4] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Specification : Type 5 AAL". +- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [6] ITU-T Recommendation I.630 (1999-02): "ATM protection switching". +- [7] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol". +- [8] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [9] IETF RFC 791 (1981-09): "Internet Protocol". +- [10] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [11] IETF RFC 1661 (1994-07): "The Point-to-Point Protocol (PPP)". +- [12] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing". +- [13] IETF RFC 2507 (1999-02): "IP header compression". +- [14] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)". +- [15] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [16] IETF RFC 2509 (1999-02): "IP Header Compression over PPP". +- [17] IETF RFC 3153 (2001-08): "PPP Multiplexing". +- [18] IETF RFC 2364 (1998-07): "PPP over AAL5". +- [19] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture". + +- [20] IETF RFC 3309 (2002-09): "Stream Control Transmission Protocol (SCTP) Checksum Change". +- [21] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**IP UTRAN node:** An UTRAN Node supporting the IP Transport Option + +## 3.2 Symbols + +(void) + +## 3.3 Abbreviations + +| | | +|-------|-----------------------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| HDLC | High-level Data Link Control | +| IP | Internet Protocol | +| NBAP | Node B Application Part | +| PPP | Point-to-Point Protocol | +| RNC | Radio Network Controller | +| SAAL | Signalling ATM Adaptation Layer | +| SCTP | Stream Control Transmission Protocol | +| SSCF | Service Specific Coordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| UNI | User-Network Interface | + +# --- 4 Data Link Layer + +## 4.1 ATM Transport Option + +ATM shall be used in the radio network control plane according to ITU-T Rec. I.361 [5]. + +### 4.1.1 Protection switching at ATM Layer + +If redundancy of pathways at ATM layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Rec. I.630 [6]. + +## 4.2 Data Link Layer for IP Transport Option + +A RNC or Node B supporting IP Transport Option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [11], IETF RFC 1662 [12]). + +**NOTE:** This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [17], IETF RFC 2364 [18]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [19]), etc.) fulfilling the UTRAN requirements towards the upper layers. + +A RNC or Node B supporting IP transport option and having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [13]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [14], IETF RFC 2686 [15]). In this case, negotiation of header compression (IETF RFC 2507 [13]) over PPP shall be performed via (IETF RFC 2509 [16]). + +# 5 NBAP signalling bearer + +## 5.1 Introduction + +The Signalling Bearer for NBAP (TS 25.433 [21]) is a point-to-point protocol. There may be multiple point-to-point links between an RNC and a Node B. As shown in figure 1, the standard allows operators to choose one out of two protocol suites for transporting the NBAP messages. + +![Diagram illustrating the two protocol suites for NBAP signalling transport over the Iub interface. The left side shows the ATM transport option, and the right side shows the IP transport option.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +The diagram illustrates two protocol stacks for NBAP signalling transport over the Iub interface: + +- Protocol Suite for ATM Transport Option (Left):** + - NodeB Application Part (NBAP) + - SSCF-UNI + - SSCOP + - AAL Type 5 + - ATM + - Physical Layer (dashed box) +- Protocol Suite for IP Transport Option (Right):** + - NodeB Application Part (NBAP) + - SCTP + - IP + - Data Link Layer (dashed box) + - Physical Layer (dashed box) + +Diagram illustrating the two protocol suites for NBAP signalling transport over the Iub interface. The left side shows the ATM transport option, and the right side shows the IP transport option. + +Figure 1: Iub NBAP Signalling Transport + +## 5.2 Signalling bearer in case of ATM Transport Option + +The signalling bearer in the Radio Network Control Plane is SAAL-UNI (ITU-T Rec. Q.2100 [1]) over ATM. The protocols to be used to support NBAP signalling are SSCF-UNI (ITU-T Rec. Q.2130 [2]) on top of SSCOP (ITU-T Rec. Q.2110 [3]) and AAL Type 5 (ITU-T Rec. I.363.5 [4]). + +## 5.3 Signalling bearer in case of IP Transport Option + +SCTP (IETF RFC 2960 [7]) over IP shall be supported as the transport for NBAP signalling bearer on Iub Interface. A RNC equipped with the SCTP stack option shall initiate the INIT procedure for establishing association. The data link layer is as specified in chapter 4.2. + +The checksum method specified in IETF RFC 3309 [20] shall be used instead of the method specified in IETF RFC 2960 ([7]). + +An IP UTRAN node shall support IPv6 (IETF RFC 2460 [8]). The support of IPv4 (IETF RFC 791 [9]) is optional. + +NOTE: This does not preclude single implementation and use of IPv4. + +IP dual stack is recommended for the potential transition period from IPv4 to IPv6 in the transport network. + +Each signalling bearer between the RNC and Node B shall correspond to one single SCTP stream in UL and one single SCTP stream in DL direction, both streams belonging to the same SCTP association. + +IP Differentiated Services code point marking (IETF RFC 2474 [10]) shall be supported. The Diffserv code point may be determined from the application parameters. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110685 | 0008 | 1 | Correction to the References | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25433/01465752f3ac36c403672804f406a676_img.jpg b/marked/Rel-16/25_series/25433/01465752f3ac36c403672804f406a676_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6b91a6a151da7f828eef0ffdc527594dc790585 --- /dev/null +++ b/marked/Rel-16/25_series/25433/01465752f3ac36c403672804f406a676_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:822585b6d7119ca6277875e5cb44c1ca2d51b3e0341bcc3943e93267428c8eb7 +size 9317 diff --git a/marked/Rel-16/25_series/25433/02e16c8e8e61c2706b5c0129674884a8_img.jpg b/marked/Rel-16/25_series/25433/02e16c8e8e61c2706b5c0129674884a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cda39432dfcd7272971609b1cb4ffcc65b739a6 --- /dev/null +++ b/marked/Rel-16/25_series/25433/02e16c8e8e61c2706b5c0129674884a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11f2abc75057d11f602d04abc0a4e459398c59d606b9dfe159ff49c39ec18deb +size 18811 diff --git a/marked/Rel-16/25_series/25433/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-16/25_series/25433/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2820a21df4d6bf129fc3f7d7f8e0b535ac8ccd23 --- /dev/null +++ b/marked/Rel-16/25_series/25433/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc961a42f945c75d0e4d34c7553bef1ae30c2e522a3390f13952ec7559837f90 +size 16909 diff --git a/marked/Rel-16/25_series/25433/0710ab057e5a25c06032594433b01316_img.jpg b/marked/Rel-16/25_series/25433/0710ab057e5a25c06032594433b01316_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a045f34b46f3c432042e1c006d0b95874b4f3649 --- /dev/null +++ b/marked/Rel-16/25_series/25433/0710ab057e5a25c06032594433b01316_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25f9478417fe3d3ddebb9739ba529f65f520511c3a83309b7b6cbd98fef94085 +size 9130 diff --git a/marked/Rel-16/25_series/25433/097b0c14308c81dcfcc168e261aa0bba_img.jpg b/marked/Rel-16/25_series/25433/097b0c14308c81dcfcc168e261aa0bba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d48ab3ba5ae9590aa5ff2cd0321f0d4153c3fe28 --- /dev/null +++ b/marked/Rel-16/25_series/25433/097b0c14308c81dcfcc168e261aa0bba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c18df54548b12daea6783d0da016179d72b473292887dcaa56e89f0952a34d82 +size 11369 diff --git a/marked/Rel-16/25_series/25433/099af350ac41fa6901be8b5be0091f8c_img.jpg b/marked/Rel-16/25_series/25433/099af350ac41fa6901be8b5be0091f8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a4b07bdcbad87a4433e58630dbf86f9f6df0bc2 --- /dev/null +++ b/marked/Rel-16/25_series/25433/099af350ac41fa6901be8b5be0091f8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f21e1f6c35a3cadd7b036cb82ce030c9fecd906b966b2416254362f4eceb77d2 +size 13447 diff --git a/marked/Rel-16/25_series/25433/0bdf45f8598420cf51abdd73300adc83_img.jpg b/marked/Rel-16/25_series/25433/0bdf45f8598420cf51abdd73300adc83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43a27ddf97a1e58cb755b0d5aaa1be72fad745e8 --- /dev/null +++ b/marked/Rel-16/25_series/25433/0bdf45f8598420cf51abdd73300adc83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dca2eebf86a6ae1c6a07fdd8e5d2f9ad499dd150cc9423f221358967b1c4473 +size 16767 diff --git a/marked/Rel-16/25_series/25433/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/25_series/25433/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdf9613e73acceca65269f573efa8de78330b3ca --- /dev/null +++ b/marked/Rel-16/25_series/25433/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6e832a410a5625738126bda4eab79552a49c9ba9ff824777c812b10842693af +size 10262 diff --git a/marked/Rel-16/25_series/25433/0d0a2d20d13bb78869a2d42f736d0c7a_img.jpg b/marked/Rel-16/25_series/25433/0d0a2d20d13bb78869a2d42f736d0c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fee393d16e67732a8b1a74ccfd0e5e20f9674fb --- /dev/null +++ b/marked/Rel-16/25_series/25433/0d0a2d20d13bb78869a2d42f736d0c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b69a055a7c2e5db2130848dbdb693da6b97f097b220a219029ca1bc036e2e790 +size 9241 diff --git a/marked/Rel-16/25_series/25433/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Rel-16/25_series/25433/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00ed84b256c60d6d005d7d1f2339719c66d7da85 --- /dev/null +++ b/marked/Rel-16/25_series/25433/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0197b6baf9900b486d14ecc5643861a0f61bde7ae8c6bdd21e8c04c90c6768a +size 3936 diff --git a/marked/Rel-16/25_series/25433/1aa60e916522640d538e81fd202045b4_img.jpg b/marked/Rel-16/25_series/25433/1aa60e916522640d538e81fd202045b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2c19ac3075c5f1c2d39a5102208679e724227b3 --- /dev/null +++ b/marked/Rel-16/25_series/25433/1aa60e916522640d538e81fd202045b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5021efd04bf597ef747826cd66ec3605ee538e0d6b91aff426602e3729ec9ea9 +size 15026 diff --git a/marked/Rel-16/25_series/25433/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/Rel-16/25_series/25433/1c79f31a718d63814feb28ab46f64f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6a6316df252ffd6bfe291d8439913b772b1a628 --- /dev/null +++ b/marked/Rel-16/25_series/25433/1c79f31a718d63814feb28ab46f64f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01520225993a02aca923b12e58ae6cedd263058824256804adea936891753b19 +size 13018 diff --git a/marked/Rel-16/25_series/25433/1ca688982d625c3b8a8e382b675de466_img.jpg b/marked/Rel-16/25_series/25433/1ca688982d625c3b8a8e382b675de466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..016e75fe235f9faf78523a105d793c51640742c2 --- /dev/null +++ b/marked/Rel-16/25_series/25433/1ca688982d625c3b8a8e382b675de466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca91eb5da0909a5000148ccedd306582f956bfd4676719052ac25b3d33ed5bdd +size 13257 diff --git a/marked/Rel-16/25_series/25433/1d08a1409256e10ac71d29289d872168_img.jpg b/marked/Rel-16/25_series/25433/1d08a1409256e10ac71d29289d872168_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd2f623fa0e24ae9f0ce779b7333ef9d7a364566 --- /dev/null +++ b/marked/Rel-16/25_series/25433/1d08a1409256e10ac71d29289d872168_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfe1dface5c63a31ec54bcb0c297dbc725ef763b1ad2c2088f6bcfdba20fbe3c +size 9751 diff --git a/marked/Rel-16/25_series/25433/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-16/25_series/25433/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d93088b35a9d5fee630e764ccfa1965bb85427e --- /dev/null +++ b/marked/Rel-16/25_series/25433/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:908ee3e2b6099ae13d88aa8acc1e10cabb11748636982535bc7a6a0f9331847c +size 11191 diff --git a/marked/Rel-16/25_series/25433/26d37a5ec149b21b1520a5bb18422208_img.jpg b/marked/Rel-16/25_series/25433/26d37a5ec149b21b1520a5bb18422208_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fcc6eb7783b18f6d4526019fbdc77493c7652b7 --- /dev/null +++ b/marked/Rel-16/25_series/25433/26d37a5ec149b21b1520a5bb18422208_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91b22ba2cee03ced58ab275ca92a6023adca7a2772c2d2194115ffbee9da890c +size 15417 diff --git a/marked/Rel-16/25_series/25433/2beb95006f1933bed737cfe1e6598db8_img.jpg b/marked/Rel-16/25_series/25433/2beb95006f1933bed737cfe1e6598db8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ee45b4c39d37a4d93aadedebd50f9cb4e7623d --- /dev/null +++ b/marked/Rel-16/25_series/25433/2beb95006f1933bed737cfe1e6598db8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba01d622b85e0d8dbf50422b38cd5289d6952f5791fa439ea28a0a8bf0314f1d +size 19053 diff --git a/marked/Rel-16/25_series/25433/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/Rel-16/25_series/25433/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42e2dfa8c7a53c0689ed3b0c5dd35971d08e7a26 --- /dev/null +++ b/marked/Rel-16/25_series/25433/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33bd44cc2e09616a4eb4232a59e70749a2af51cb962b8023de91f3fb0441960c +size 9498 diff --git a/marked/Rel-16/25_series/25433/2e9c6c1583e99f58d7fbf0c354855f4c_img.jpg b/marked/Rel-16/25_series/25433/2e9c6c1583e99f58d7fbf0c354855f4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa2a75957c41e9d1fe1672b5b8c501b35583804f --- /dev/null +++ b/marked/Rel-16/25_series/25433/2e9c6c1583e99f58d7fbf0c354855f4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c6b1139ee6bab3a0ca21ee916d83b7401d3d03674c13500dcdde0874f114f4c +size 15348 diff --git a/marked/Rel-16/25_series/25433/2fa9981a71c3ed101a792578163cb90e_img.jpg b/marked/Rel-16/25_series/25433/2fa9981a71c3ed101a792578163cb90e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..067e0f3d04eea6c9fb22be581efd0994744c8200 --- /dev/null +++ b/marked/Rel-16/25_series/25433/2fa9981a71c3ed101a792578163cb90e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92432bd7e17c63100452fe1ef37193687d68a12efc4d4fe375b80c9190ebe564 +size 16478 diff --git a/marked/Rel-16/25_series/25433/305c3b31c7d60405cf039fd098ba4669_img.jpg b/marked/Rel-16/25_series/25433/305c3b31c7d60405cf039fd098ba4669_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e24b162416a7a5f709d83c7cf4a9d501095dd049 --- /dev/null +++ b/marked/Rel-16/25_series/25433/305c3b31c7d60405cf039fd098ba4669_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5b889b46d32341699e1fcbdc1dddd5434b254ad874bd6e7eca66c0a3eaa6319 +size 7476 diff --git a/marked/Rel-16/25_series/25433/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/marked/Rel-16/25_series/25433/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f1cc42797825acd514228f7696ceeb2ef023d57 --- /dev/null +++ b/marked/Rel-16/25_series/25433/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e305a9cc491400dd31cd84c7266cb9c3f986b2f99e2450fc1d5161dbc042f75 +size 8615 diff --git a/marked/Rel-16/25_series/25433/35a7554182eb055209552843f341a1ae_img.jpg b/marked/Rel-16/25_series/25433/35a7554182eb055209552843f341a1ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71e40b278b0b6c8b26262f2f13f3c1987c178b22 --- /dev/null +++ b/marked/Rel-16/25_series/25433/35a7554182eb055209552843f341a1ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7abd92218982497e7ae5dd220b510d9e586dab1c0826847c5d699a2b1e857e9 +size 12143 diff --git a/marked/Rel-16/25_series/25433/39e4a95c2c20ea45e33f953869f345bc_img.jpg b/marked/Rel-16/25_series/25433/39e4a95c2c20ea45e33f953869f345bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..526317639b367ba68138dd7c2a2d140dbaeadc30 --- /dev/null +++ b/marked/Rel-16/25_series/25433/39e4a95c2c20ea45e33f953869f345bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b66d3300f936e54f770eb5c462e67263a2bed0db4c9f2bff9519ef2b95e772ca +size 7642 diff --git a/marked/Rel-16/25_series/25433/3ae0872dc01de8bf4c43996b9507914b_img.jpg b/marked/Rel-16/25_series/25433/3ae0872dc01de8bf4c43996b9507914b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5155ac302dd52d9b5bdf5bf28de7c6c332e85d22 --- /dev/null +++ b/marked/Rel-16/25_series/25433/3ae0872dc01de8bf4c43996b9507914b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7f494cd9d5f2fa78aee2fd99999280aa8c706ad926222f8c49279581e79b10 +size 14656 diff --git a/marked/Rel-16/25_series/25433/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/25_series/25433/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09e846c81ee27db9bcfbb46d953720a982a7e82b --- /dev/null +++ b/marked/Rel-16/25_series/25433/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd68104252195586b7a1d856ac885f3f777a75e45ea88027ff6d0056edc36c4 +size 18330 diff --git a/marked/Rel-16/25_series/25433/40b3d859722c55c5cc5f8512aaefa01a_img.jpg b/marked/Rel-16/25_series/25433/40b3d859722c55c5cc5f8512aaefa01a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e23c99d42b1e56bce3f10d61858d401547b14cf --- /dev/null +++ b/marked/Rel-16/25_series/25433/40b3d859722c55c5cc5f8512aaefa01a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b8ceed678d49c6bdac030725d134d73a1107b3818f0d74b032d90b23a7be6c1 +size 13188 diff --git a/marked/Rel-16/25_series/25433/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/25_series/25433/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee05b4d7283bcedc42ea0606bce8f82a0eb36319 --- /dev/null +++ b/marked/Rel-16/25_series/25433/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dca051c6fd0003a48750b781078158a1ac59f678d371c8d86ac31605ccc0f3fb +size 10738 diff --git a/marked/Rel-16/25_series/25433/46ed1f28ea8dfc28049900e848488ae7_img.jpg b/marked/Rel-16/25_series/25433/46ed1f28ea8dfc28049900e848488ae7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d36f0d264bc64c67922725317ff69f11051a1b --- /dev/null +++ b/marked/Rel-16/25_series/25433/46ed1f28ea8dfc28049900e848488ae7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2226853bee99f8d4c554367951d0ab892e230ddc66ce266b9420113ac368be5b +size 15774 diff --git a/marked/Rel-16/25_series/25433/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/marked/Rel-16/25_series/25433/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31438c8639e505024a69e5ffa0a2e3f2a6e16817 --- /dev/null +++ b/marked/Rel-16/25_series/25433/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dca8c5e2f7ba2666fa151adf549c78fbb953b3cabbb83954d320132d9fc3198b +size 14499 diff --git a/marked/Rel-16/25_series/25433/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-16/25_series/25433/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98abfe577b7acc4fa7fc667be8bd61426f858429 --- /dev/null +++ b/marked/Rel-16/25_series/25433/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c9fb0d3b8a5dc57d8398164fe00faa7270ebdc1344dc8181ff141c668e3ab9c +size 15429 diff --git a/marked/Rel-16/25_series/25433/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Rel-16/25_series/25433/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..432f2647ba415de718b3806af1227b150ae2ad00 --- /dev/null +++ b/marked/Rel-16/25_series/25433/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8adf796a34062e905a9d64f2ae48ce5629b1ba34158a716f45f94f34bd50b4f9 +size 11083 diff --git a/marked/Rel-16/25_series/25433/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-16/25_series/25433/5bba23cc120ad806779f82df1c01bebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..438e27a54017471a022d1de4a0d61e112e37bc52 --- /dev/null +++ b/marked/Rel-16/25_series/25433/5bba23cc120ad806779f82df1c01bebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aefc4ebf93b572509dfc6263e7f45f43b53629ba3630568afe62983dbf4adab +size 19067 diff --git a/marked/Rel-16/25_series/25433/5be761f3d780e80637364abc66fa3916_img.jpg b/marked/Rel-16/25_series/25433/5be761f3d780e80637364abc66fa3916_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c42454247b16f775d0c64b772ef4d633dcfdcf4 --- /dev/null +++ b/marked/Rel-16/25_series/25433/5be761f3d780e80637364abc66fa3916_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de6fed04e9718ddd0d5d81b7c87a73efa47f23e49e5b595023bf9dbcbb6beb11 +size 8783 diff --git a/marked/Rel-16/25_series/25433/6078636a87fbe0e699aab4a6fddd15d7_img.jpg b/marked/Rel-16/25_series/25433/6078636a87fbe0e699aab4a6fddd15d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..921e339a77f9102e4272665060602ff514c2d8cf --- /dev/null +++ b/marked/Rel-16/25_series/25433/6078636a87fbe0e699aab4a6fddd15d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:810a0b0e31a71b9097a5d8e2c24d162c76891b56d02602ebf9e00ba23a06ef8d +size 9344 diff --git a/marked/Rel-16/25_series/25433/6399940001d500190d1024ea66f2f7f0_img.jpg b/marked/Rel-16/25_series/25433/6399940001d500190d1024ea66f2f7f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59b451ebd0564b9f64868aa123b2c57f630c0b73 --- /dev/null +++ b/marked/Rel-16/25_series/25433/6399940001d500190d1024ea66f2f7f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66095fa926d3f0b8c060474bebb64100f43ceeb7db2c64c3f644b7edcf495c72 +size 13749 diff --git a/marked/Rel-16/25_series/25433/667b755d2a359d7b9a54cfceac78350a_img.jpg b/marked/Rel-16/25_series/25433/667b755d2a359d7b9a54cfceac78350a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f37194ea403893559e7d33c621daf8b6d47708f8 --- /dev/null +++ b/marked/Rel-16/25_series/25433/667b755d2a359d7b9a54cfceac78350a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c12c2d487e9ef1f0b25350bc3a8da68e501bc1365b4da3a8cc6e2e01025215be +size 15235 diff --git a/marked/Rel-16/25_series/25433/68dad113f9a15ab01945110cb50cdcfb_img.jpg b/marked/Rel-16/25_series/25433/68dad113f9a15ab01945110cb50cdcfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7f9eb291dd755f35fb14b392a7774d90992c59c --- /dev/null +++ b/marked/Rel-16/25_series/25433/68dad113f9a15ab01945110cb50cdcfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6170b962b29a106f5ee4d78e7288c70737efbd72fefbd5f00ad9259bdc3020d8 +size 7616 diff --git a/marked/Rel-16/25_series/25433/6c6c57fd6906a27054b02c6be574f417_img.jpg b/marked/Rel-16/25_series/25433/6c6c57fd6906a27054b02c6be574f417_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..103fac120307c9077a7b37cd4fac238e9c054690 --- /dev/null +++ b/marked/Rel-16/25_series/25433/6c6c57fd6906a27054b02c6be574f417_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25a6403f0f3a629ef2a44dc67a8e58f29ead98c7fc426779e8d5acc719780ee4 +size 11244 diff --git a/marked/Rel-16/25_series/25433/78258750e6697a1b47b76f9df9735773_img.jpg b/marked/Rel-16/25_series/25433/78258750e6697a1b47b76f9df9735773_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7c2a9be26cd1c3c13cd63a0363a66b9da3e5548 --- /dev/null +++ b/marked/Rel-16/25_series/25433/78258750e6697a1b47b76f9df9735773_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:266ba4ab0579d263494c7f661e17c41d1351a07bbc743ca4190f59daa6b0b0e9 +size 14547 diff --git a/marked/Rel-16/25_series/25433/7a1dee155822446f7828dcb055c465c3_img.jpg b/marked/Rel-16/25_series/25433/7a1dee155822446f7828dcb055c465c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..001a6a328099d433b35b38045866e289f26a9a28 --- /dev/null +++ b/marked/Rel-16/25_series/25433/7a1dee155822446f7828dcb055c465c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86b18b264e09607b8435bec5cc8dfe1531d4f0e78c9fc439ef72b58bce009623 +size 10437 diff --git a/marked/Rel-16/25_series/25433/7cb62a0db45266260cb60c33f7c8b4d9_img.jpg b/marked/Rel-16/25_series/25433/7cb62a0db45266260cb60c33f7c8b4d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0885d65ef250e272a944b1ee470414e0ef7aba5 --- /dev/null +++ b/marked/Rel-16/25_series/25433/7cb62a0db45266260cb60c33f7c8b4d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f3ffb5863c21e5fe90fd7493972bd43b2c4202bdd72dc54818bfd5bcb56a9cc +size 14072 diff --git a/marked/Rel-16/25_series/25433/7d3ed9c56124e26db58cd7475467dfab_img.jpg b/marked/Rel-16/25_series/25433/7d3ed9c56124e26db58cd7475467dfab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6c2bdbf4510edd7b93b68b297d3c848151a0bdc --- /dev/null +++ b/marked/Rel-16/25_series/25433/7d3ed9c56124e26db58cd7475467dfab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb98250d29941ef8138757437ac78da319d448f991d5e0b0f1be5be5d985d5d6 +size 13874 diff --git a/marked/Rel-16/25_series/25433/822e033872d5ab16e861571f47b81ba7_img.jpg b/marked/Rel-16/25_series/25433/822e033872d5ab16e861571f47b81ba7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d55b9fa0e9a9d9ebc10f7ff65b32b9790cb1746 --- /dev/null +++ b/marked/Rel-16/25_series/25433/822e033872d5ab16e861571f47b81ba7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5389910a36f2599e1db6c05fecb1344ac56e3ed260f68341f3d47778c04f570c +size 20193 diff --git a/marked/Rel-16/25_series/25433/832570a3a00d9064e8068d0bb5def3a9_img.jpg b/marked/Rel-16/25_series/25433/832570a3a00d9064e8068d0bb5def3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea098a51a0bcea217d3a369369613854122a549e --- /dev/null +++ b/marked/Rel-16/25_series/25433/832570a3a00d9064e8068d0bb5def3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cccd449f0a57b8a95f6c241fda29e35c2f4867a6a85910bffd07999510ccbdb +size 6794 diff --git a/marked/Rel-16/25_series/25433/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/25_series/25433/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8452695f6aa875e934e5a8e03d265137fe3037af --- /dev/null +++ b/marked/Rel-16/25_series/25433/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:603f3d93f841956af2c14574c62474c4827b14c3b2bc7083b2c45d3c9fb934c8 +size 9525 diff --git a/marked/Rel-16/25_series/25433/85412017cb0c8ea0fd14bdaab53baeae_img.jpg b/marked/Rel-16/25_series/25433/85412017cb0c8ea0fd14bdaab53baeae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..520d59cc588dea018f9a996195cc9932002d8518 --- /dev/null +++ b/marked/Rel-16/25_series/25433/85412017cb0c8ea0fd14bdaab53baeae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4536b369d2da7d9f047358d41e91fd3e4c9c6e14a0b99176fca8d05959e115a5 +size 14442 diff --git a/marked/Rel-16/25_series/25433/864e6cb4a0166a5b21a5d19f694e1606_img.jpg b/marked/Rel-16/25_series/25433/864e6cb4a0166a5b21a5d19f694e1606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd38edb24079fd6c3d09313bfe3a30f5053960a7 --- /dev/null +++ b/marked/Rel-16/25_series/25433/864e6cb4a0166a5b21a5d19f694e1606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d5118258b243eb65da77c32b31f3d8ce976f25e5ded74f793f74246d773fc70 +size 14348 diff --git a/marked/Rel-16/25_series/25433/8aeef954d0c39404560f5f3968756f82_img.jpg b/marked/Rel-16/25_series/25433/8aeef954d0c39404560f5f3968756f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5477514f6594f99f21a787489aa6011dcd21dfa --- /dev/null +++ b/marked/Rel-16/25_series/25433/8aeef954d0c39404560f5f3968756f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5122b9896f48944e3ced78e33ffb3e33114ef7af58d351106b11c3324befc63 +size 9619 diff --git a/marked/Rel-16/25_series/25433/8d1bb05debbaef0f72751449b2b55172_img.jpg b/marked/Rel-16/25_series/25433/8d1bb05debbaef0f72751449b2b55172_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7162dfc01a320eb258b661501cfca490576cf0b --- /dev/null +++ b/marked/Rel-16/25_series/25433/8d1bb05debbaef0f72751449b2b55172_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f771c7c5b212ecfee7e4669fe60760719d82a970c03dc0ee82c3c1a4bfed9b70 +size 16990 diff --git a/marked/Rel-16/25_series/25433/98d0322515464572a78f3e4ee94105ed_img.jpg b/marked/Rel-16/25_series/25433/98d0322515464572a78f3e4ee94105ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a1a9d74715768cf49a959f8684cc27910a4feba --- /dev/null +++ b/marked/Rel-16/25_series/25433/98d0322515464572a78f3e4ee94105ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61fe6000fce560bd16fade67913dff23f5831a3851130d210219b2fcaffbd956 +size 9220 diff --git a/marked/Rel-16/25_series/25433/a89d151b67109378baed0c117830cf78_img.jpg b/marked/Rel-16/25_series/25433/a89d151b67109378baed0c117830cf78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdb2d36fee45dd9f1ea1d194ebc16673e2a59dd1 --- /dev/null +++ b/marked/Rel-16/25_series/25433/a89d151b67109378baed0c117830cf78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69154067d354baacd2ec6057d39ff0b99b86562ca65ce4f78fdf5a972ccd237d +size 5986 diff --git a/marked/Rel-16/25_series/25433/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg b/marked/Rel-16/25_series/25433/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26a6337620bd18b09f8e01c6f5a09faeff01dd09 --- /dev/null +++ b/marked/Rel-16/25_series/25433/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f8492828e23957dbc6bdfe7135cdfd68167c69158d4f40ee9136d40b8e3a6a +size 13453 diff --git a/marked/Rel-16/25_series/25433/aa73c8651865e31f7a2f7b8a9c068461_img.jpg b/marked/Rel-16/25_series/25433/aa73c8651865e31f7a2f7b8a9c068461_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d4f5db0534d5d1c7671ca14b6263bf87c3736e1 --- /dev/null +++ b/marked/Rel-16/25_series/25433/aa73c8651865e31f7a2f7b8a9c068461_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edbf9f0142e37daf0780a2f8aa0d24bfabf15fc185ce04479d12277788172a0f +size 13014 diff --git a/marked/Rel-16/25_series/25433/b15cf8c50195a52cca59b4645c6f59fa_img.jpg b/marked/Rel-16/25_series/25433/b15cf8c50195a52cca59b4645c6f59fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab1bcdc288a7034258b6f44a4f2b4000af724132 --- /dev/null +++ b/marked/Rel-16/25_series/25433/b15cf8c50195a52cca59b4645c6f59fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:222a90d2d5c5c9c3212ed49343ac56f4b5224842d38e9eb8d0b3eff5e688127f +size 12272 diff --git a/marked/Rel-16/25_series/25433/b9f3b61f140ea64afb9205312d52eb0e_img.jpg b/marked/Rel-16/25_series/25433/b9f3b61f140ea64afb9205312d52eb0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f191ea6fbae02389ebcabd60ed078d8873dc9702 --- /dev/null +++ b/marked/Rel-16/25_series/25433/b9f3b61f140ea64afb9205312d52eb0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f327553b6bc638965537346c52e153e98b379f2a6ea772abb8f24f2eb686f086 +size 14598 diff --git a/marked/Rel-16/25_series/25433/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-16/25_series/25433/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5976e79718b9d8e3b2e2b5e7e81d51734fcc166 --- /dev/null +++ b/marked/Rel-16/25_series/25433/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ae8159c49dc490b80484e33c4134e88b634f6bf7ccbf674e46907218113a5c0 +size 10778 diff --git a/marked/Rel-16/25_series/25433/bdb44cc8120caccddc2adf0c3db54261_img.jpg b/marked/Rel-16/25_series/25433/bdb44cc8120caccddc2adf0c3db54261_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..354a65b189e3a3ff8e8ba4887da9b27748e76927 --- /dev/null +++ b/marked/Rel-16/25_series/25433/bdb44cc8120caccddc2adf0c3db54261_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96bd95b62ad8dcc76d635aace9f74be7a7b969daae0229032b1dfb94e69c27b0 +size 9656 diff --git a/marked/Rel-16/25_series/25433/bdd19e1aefc189598ab515f8f12518dd_img.jpg b/marked/Rel-16/25_series/25433/bdd19e1aefc189598ab515f8f12518dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d36e1cc5ef3a3c25ee53150eed731ffd337fd6ad --- /dev/null +++ b/marked/Rel-16/25_series/25433/bdd19e1aefc189598ab515f8f12518dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88202283704843848aec37a4d317a6f3480a34170cefb9c438a191771721deb5 +size 6224 diff --git a/marked/Rel-16/25_series/25433/c4f4e64722ba94da46d926c92ef35b46_img.jpg b/marked/Rel-16/25_series/25433/c4f4e64722ba94da46d926c92ef35b46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80a073419aa363dd15950e3ed0423b30ad11500d --- /dev/null +++ b/marked/Rel-16/25_series/25433/c4f4e64722ba94da46d926c92ef35b46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19972b5895b04bf7d0e286a59325b37d782ae109543f5036262d3286a0027df3 +size 17081 diff --git a/marked/Rel-16/25_series/25433/c75343ea87825a0429d6a0ad27e2a6cd_img.jpg b/marked/Rel-16/25_series/25433/c75343ea87825a0429d6a0ad27e2a6cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e9b8a03643493b75a63ecde16ea1f8fa24e8ead --- /dev/null +++ b/marked/Rel-16/25_series/25433/c75343ea87825a0429d6a0ad27e2a6cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15d71df6661496ac1ea93a28a8f6adc5085c667321a53f2765f1caafce0226cf +size 14241 diff --git a/marked/Rel-16/25_series/25433/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-16/25_series/25433/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69943e915382659e0fad256f6f8b6a0cc5f42cf4 --- /dev/null +++ b/marked/Rel-16/25_series/25433/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f659d176c2b1af677f6d5600e835467878d9798aedfb1a56c7d310018e253388 +size 17009 diff --git a/marked/Rel-16/25_series/25433/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg b/marked/Rel-16/25_series/25433/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..935a94f83963ff287d75adc27c19c54a7695a476 --- /dev/null +++ b/marked/Rel-16/25_series/25433/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90e10c8a44c2c309784f38421c9fab5c50bbb066d3bd605505f018fd2acc2c95 +size 8989 diff --git a/marked/Rel-16/25_series/25433/e1136c8a41c5a8081a8a554e513cd86e_img.jpg b/marked/Rel-16/25_series/25433/e1136c8a41c5a8081a8a554e513cd86e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c584adebcfdee1b4a20da43e73af0d19efc15800 --- /dev/null +++ b/marked/Rel-16/25_series/25433/e1136c8a41c5a8081a8a554e513cd86e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f19623e35bee09bd29c2d228fd466b1ce17dd30f44f4c1a8d0d6d338c2a60e4f +size 12299 diff --git a/marked/Rel-16/25_series/25433/e1a3f5045f139b39707b3ebb76ad254c_img.jpg b/marked/Rel-16/25_series/25433/e1a3f5045f139b39707b3ebb76ad254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb3ba94f3636f886ca0b2e4078b5a3a95f42d7e9 --- /dev/null +++ b/marked/Rel-16/25_series/25433/e1a3f5045f139b39707b3ebb76ad254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2593131b17e8210a0565f3339303c1291a27843740835282d9c7397fe121f150 +size 9152 diff --git a/marked/Rel-16/25_series/25433/e2fd964b19c1159de4d15785eb8af621_img.jpg b/marked/Rel-16/25_series/25433/e2fd964b19c1159de4d15785eb8af621_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c918a2e1967b2b1b5515f0dde1d9adfb1cd2cad --- /dev/null +++ b/marked/Rel-16/25_series/25433/e2fd964b19c1159de4d15785eb8af621_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d29cf8130182b82787275289d1d1ae54a55414db478ea120425295752969b06 +size 14230 diff --git a/marked/Rel-16/25_series/25433/e42cc691d9c7c4d23e66b04472bb494e_img.jpg b/marked/Rel-16/25_series/25433/e42cc691d9c7c4d23e66b04472bb494e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0716350fd3dede888793252cb130923f74df330a --- /dev/null +++ b/marked/Rel-16/25_series/25433/e42cc691d9c7c4d23e66b04472bb494e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36729e0efccfe5a654147b7fddbd76b231a87b8614d1e7e4cdacc1501115e96c +size 8534 diff --git a/marked/Rel-16/25_series/25433/e67bca96ac67ddab7a8762b49d4c438d_img.jpg b/marked/Rel-16/25_series/25433/e67bca96ac67ddab7a8762b49d4c438d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ca5ac4008f5c1ea5426b5a58e71ee431d3b9330 --- /dev/null +++ b/marked/Rel-16/25_series/25433/e67bca96ac67ddab7a8762b49d4c438d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24743c94277f1fc17184dd0f77568d1b501cd4f9961390afb597fb92db0d8494 +size 9775 diff --git a/marked/Rel-16/25_series/25433/e80b1f0d2748dacbe9d5fc551da02feb_img.jpg b/marked/Rel-16/25_series/25433/e80b1f0d2748dacbe9d5fc551da02feb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4891aaf957608dc069ffe274e226fd7a43e53b68 --- /dev/null +++ b/marked/Rel-16/25_series/25433/e80b1f0d2748dacbe9d5fc551da02feb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85a3e73bd729702d12b337a33c9af82fbd08ab1581b82681df604405ce2be4e6 +size 8671 diff --git a/marked/Rel-16/25_series/25433/eb92aaf8c058798b58d42d889c556d36_img.jpg b/marked/Rel-16/25_series/25433/eb92aaf8c058798b58d42d889c556d36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..385b35eb6a9b5fe47ff68c2f4553cdde30bba6ff --- /dev/null +++ b/marked/Rel-16/25_series/25433/eb92aaf8c058798b58d42d889c556d36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36fefb7cb1f274b62f2a620497010e458d004b6964a1a2c3e57ccc5681a27d19 +size 17239 diff --git a/marked/Rel-16/25_series/25433/f04d32f713a4aeb9f63c3f8e1015145c_img.jpg b/marked/Rel-16/25_series/25433/f04d32f713a4aeb9f63c3f8e1015145c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95a73f2227f58fdd15328253b152f95e00217fe0 --- /dev/null +++ b/marked/Rel-16/25_series/25433/f04d32f713a4aeb9f63c3f8e1015145c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9150acdbb4118f597c1ff7873b2f98120e0f772a002dbc6fac01de96b13b853 +size 19262 diff --git a/marked/Rel-16/25_series/25433/f0addfb9cb95476594c62d37d1208037_img.jpg b/marked/Rel-16/25_series/25433/f0addfb9cb95476594c62d37d1208037_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4574c14452ebe7a8e87705747a02739f8fa5110b --- /dev/null +++ b/marked/Rel-16/25_series/25433/f0addfb9cb95476594c62d37d1208037_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98a9eedef7090de2749dbdee7e666432802cafd3489129905673cb94c4b4dfbf +size 9875 diff --git a/marked/Rel-16/25_series/25433/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-16/25_series/25433/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c60d995bc5617472927052a39aa3ef22453c2d36 --- /dev/null +++ b/marked/Rel-16/25_series/25433/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d539a33346610ca6c2bfd97df757275da66383cde5e83e008084a0bd722619ce +size 9520 diff --git a/marked/Rel-16/25_series/25433/f3c73e8e478b8b2d9f6a96a970040556_img.jpg b/marked/Rel-16/25_series/25433/f3c73e8e478b8b2d9f6a96a970040556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1786968fd5383133c6e7aa98057c02aba00ab38c --- /dev/null +++ b/marked/Rel-16/25_series/25433/f3c73e8e478b8b2d9f6a96a970040556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8b5a12575504fd769b9c1ee650b87a2fd481ca5b6ddce5e7737979400e3fb5a +size 10293 diff --git a/marked/Rel-16/25_series/25433/raw.md b/marked/Rel-16/25_series/25433/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f2d79fecdc9a5d8954bae4b7f4a4306147e86ad5 --- /dev/null +++ b/marked/Rel-16/25_series/25433/raw.md @@ -0,0 +1,37555 @@ +# --- Contents + +| | | +|-----------------------------------------------------|----| +| Foreword..... | 25 | +| 1 Scope..... | 26 | +| 2 References..... | 26 | +| 3 Definitions, Symbols and Abbreviations..... | 28 | +| 3.1 Definitions..... | 28 | +| 3.2 Symbols..... | 28 | +| 3.3 Abbreviations..... | 29 | +| 4 General..... | 30 | +| 4.1 Procedure Specification Principles..... | 30 | +| 4.2 Forwards and Backwards Compatibility..... | 31 | +| 4.3 Specification Notations..... | 31 | +| 5 NBAP Services..... | 32 | +| 5.1 Parallel Transactions..... | 32 | +| 6 Services Expected from Signalling Transport..... | 32 | +| 7 Functions of NBAP..... | 32 | +| 8 NBAP Procedures..... | 35 | +| 8.1 Elementary Procedures..... | 35 | +| 8.2 NBAP Common Procedures..... | 37 | +| 8.2.1 Common Transport Channel Setup..... | 37 | +| 8.2.1.1 General..... | 37 | +| 8.2.1.2 Successful Operation..... | 38 | +| 8.2.1.3 Unsuccessful Operation..... | 41 | +| 8.2.1.4 Abnormal Conditions..... | 42 | +| 8.2.2 Common Transport Channel Reconfiguration..... | 43 | +| 8.2.2.1 General..... | 43 | +| 8.2.2.2 Successful Operation..... | 43 | +| 8.2.2.3 Unsuccessful Operation..... | 45 | +| 8.2.2.4 Abnormal Conditions..... | 46 | +| 8.2.3 Common Transport Channel Deletion..... | 46 | +| 8.2.3.1 General..... | 46 | +| 8.2.3.2 Successful Operation..... | 46 | +| 8.2.3.3 Unsuccessful Operation..... | 47 | +| 8.2.3.4 Abnormal Conditions..... | 47 | +| 8.2.4 Block Resource..... | 47 | +| 8.2.4.1 General..... | 47 | +| 8.2.4.2 Successful Operation..... | 47 | +| 8.2.4.3 Unsuccessful Operation..... | 48 | +| 8.2.4.4 Abnormal Conditions..... | 49 | +| 8.2.5 Unblock Resource..... | 49 | +| 8.2.5.1 General..... | 49 | +| 8.2.5.2 Successful Operation..... | 49 | +| 8.2.5.3 Abnormal Conditions..... | 49 | +| 8.2.6 Audit Required..... | 49 | +| 8.2.6.1 General..... | 49 | +| 8.2.6.2 Successful Operation..... | 50 | +| 8.2.6.3 Abnormal Conditions..... | 50 | +| 8.2.7 Audit..... | 50 | +| 8.2.7.1 General..... | 50 | +| 8.2.7.2 Successful Operation..... | 50 | +| 8.2.7.3 Unsuccessful Operation..... | 53 | +| 8.2.7.4 Abnormal Conditions..... | 53 | +| 8.2.8 Common Measurement Initiation..... | 53 | +| 8.2.8.1 General..... | 53 | + +| | | | +|------------|----------------------------------------------|-----| +| 8.2.8.2 | Successful Operation..... | 53 | +| 8.2.8.3 | Unsuccessful Operation..... | 62 | +| 8.2.8.4 | Abnormal Conditions..... | 62 | +| 8.2.9 | Common Measurement Reporting..... | 66 | +| 8.2.9.1 | General..... | 66 | +| 8.2.9.2 | Successful Operation..... | 66 | +| 8.2.9.3 | Abnormal Conditions..... | 67 | +| 8.2.10 | Common Measurement Termination..... | 67 | +| 8.2.10.1 | General..... | 67 | +| 8.2.10.2 | Successful Operation..... | 67 | +| 8.2.10.3 | Abnormal Conditions..... | 68 | +| 8.2.11 | Common Measurement Failure..... | 68 | +| 8.2.11.1 | General..... | 68 | +| 8.2.11.2 | Successful Operation..... | 68 | +| 8.2.11.3 | Abnormal Conditions..... | 68 | +| 8.2.12 | Cell Setup..... | 68 | +| 8.2.12.1 | General..... | 68 | +| 8.2.12.2 | Successful Operation..... | 68 | +| 8.2.12.3 | Unsuccessful Operation..... | 70 | +| 8.2.12.4 | Abnormal Conditions..... | 71 | +| 8.2.13 | Cell Reconfiguration..... | 71 | +| 8.2.13.1 | General..... | 71 | +| 8.2.13.2 | Successful Operation..... | 71 | +| 8.2.13.3 | Unsuccessful Operation..... | 74 | +| 8.2.13.4 | Abnormal Conditions..... | 74 | +| 8.2.14 | Cell Deletion..... | 75 | +| 8.2.14.1 | General..... | 75 | +| 8.2.14.2 | Successful Operation..... | 75 | +| 8.2.14.3 | Unsuccessful Operation..... | 75 | +| 8.2.14.4 | Abnormal Conditions..... | 75 | +| 8.2.15 | Resource Status Indication..... | 75 | +| 8.2.15.1 | General..... | 75 | +| 8.2.15.2 | Successful Operation..... | 76 | +| 8.2.15.3 | Abnormal Conditions..... | 83 | +| 8.2.16 | System Information Update..... | 83 | +| 8.2.16.1 | General..... | 83 | +| 8.2.16.2 | Successful Operation..... | 83 | +| 8.2.16.3 | Unsuccessful Operation..... | 84 | +| 8.2.16.4 | Abnormal Conditions..... | 85 | +| 8.2.17 | Radio Link Setup..... | 85 | +| 8.2.17.1 | General..... | 85 | +| 8.2.17.2 | Successful Operation..... | 86 | +| 8.2.17.3 | Unsuccessful Operation..... | 112 | +| 8.2.17.4 | Abnormal Conditions..... | 114 | +| 8.2.18 | Physical Shared Channel Reconfiguration..... | 118 | +| 8.2.18.1 | General..... | 118 | +| 8.2.18.2 | Successful Operation..... | 118 | +| 8.2.18.3 | Unsuccessful Operation..... | 133 | +| 8.2.18.4 | Abnormal Conditions..... | 134 | +| 8.2.19 | Reset..... | 136 | +| 8.2.19.1 | General..... | 136 | +| 8.2.19.2 | Successful Operation..... | 136 | +| 8.2.19.2.1 | Reset Initiated by the CRNC..... | 136 | +| 8.2.19.2.2 | Reset Initiated by the Node B..... | 137 | +| 8.2.19.3 | Unsuccessful Operation..... | 137 | +| 8.2.19.4 | Abnormal Conditions..... | 137 | +| 8.2.20 | Cell Synchronisation Initiation [TDD]..... | 137 | +| 8.2.20.1 | General..... | 137 | +| 8.2.20.2 | Successful Operation..... | 137 | +| 8.2.20.3 | Unsuccessful Operation..... | 139 | +| 8.2.20.4 | Abnormal Conditions..... | 139 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.2.21 | Cell Synchronisation Reconfiguration [TDD]..... | 139 | +| 8.2.21.1 | General..... | 139 | +| 8.2.21.2 | Successful Operation..... | 140 | +| 8.2.21.2.1 | General..... | 140 | +| 8.2.21.2.2 | [3.84Mcps TDD - Cell Sync Burst Schedule]..... | 140 | +| 8.2.21.2.3 | [1.28Mcps TDD - SYNC_DL Code Schedule]..... | 140 | +| 8.2.21.2.4 | [3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration] [1.28Mcps TDD -
SYNC_DL Code Transmission Reconfiguration]..... | 141 | +| 8.2.21.2.5 | [3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration] [1.28Mcps TDD -
SYNC_DL Code Measurement Reconfiguration]..... | 142 | +| 8.2.21.3 | Unsuccessful Operation..... | 143 | +| 8.2.21.4 | Abnormal Conditions..... | 143 | +| 8.2.22 | Cell Synchronisation Reporting [TDD]..... | 143 | +| 8.2.22.1 | General..... | 143 | +| 8.2.22.2 | Successful Operation..... | 144 | +| 8.2.22.3 | Abnormal Conditions..... | 144 | +| 8.2.23 | Cell Synchronisation Termination [TDD]..... | 144 | +| 8.2.23.1 | General..... | 144 | +| 8.2.23.2 | Successful Operation..... | 144 | +| 8.2.23.3 | Abnormal Conditions..... | 145 | +| 8.2.24 | Cell Synchronisation Failure [TDD]..... | 145 | +| 8.2.24.1 | General..... | 145 | +| 8.2.24.2 | Successful Operation..... | 145 | +| 8.2.24.3 | Abnormal Conditions..... | 145 | +| 8.2.25 | Cell Synchronisation Adjustment [TDD]..... | 145 | +| 8.2.25.1 | General..... | 145 | +| 8.2.25.2 | Successful Operation..... | 145 | +| 8.2.25.3 | Unsuccessful Operation..... | 146 | +| 8.2.25.4 | Abnormal Conditions..... | 147 | +| 8.2.26 | Information Exchange Initiation..... | 147 | +| 8.2.26.1 | General..... | 147 | +| 8.2.26.2 | Successful Operation..... | 147 | +| 8.2.26.3 | Unsuccessful Operation..... | 150 | +| 8.2.26.4 | Abnormal Conditions..... | 150 | +| 8.2.27 | Information Reporting..... | 151 | +| 8.2.27.1 | General..... | 151 | +| 8.2.27.2 | Successful Operation..... | 151 | +| 8.2.27.3 | Abnormal Conditions..... | 151 | +| 8.2.28 | Information Exchange Termination..... | 151 | +| 8.2.28.1 | General..... | 151 | +| 8.2.28.2 | Successful Operation..... | 151 | +| 8.2.28.3 | Abnormal Conditions..... | 152 | +| 8.2.29 | Information Exchange Failure..... | 152 | +| 8.2.29.1 | General..... | 152 | +| 8.2.29.2 | Successful Operation..... | 152 | +| 8.2.30 | MBMS Notification Update..... | 152 | +| 8.2.30.1 | General..... | 152 | +| 8.2.30.2 | Successful Operation..... | 152 | +| 8.2.30.3 | Abnormal Conditions..... | 153 | +| 8.2.31 | UE Status Update [FDD and 1.28Mcps TDD]..... | 153 | +| 8.2.31.1 | General..... | 153 | +| 8.2.31.2 | Successful Operation..... | 153 | +| 8.2.31.3 | Abnormal Conditions..... | 153 | +| 8.2.32 | UE Status Update Confirmation [FDD and 1.28Mcps TDD]..... | 153 | +| 8.2.32.1 | General..... | 153 | +| 8.2.32.2 | Successful Operation..... | 153 | +| 8.2.32.3 | Abnormal Conditions..... | 154 | +| 8.3 | NBAP Dedicated Procedures..... | 154 | +| 8.3.1 | Radio Link Addition..... | 154 | +| 8.3.1.1 | General..... | 154 | +| 8.3.1.2 | Successful Operation..... | 154 | + +| | | | +|----------|-----------------------------------------------------------|-----| +| 8.3.1.3 | Unsuccessful Operation..... | 184 | +| 8.3.1.4 | Abnormal conditions..... | 186 | +| 8.3.2 | Synchronised Radio Link Reconfiguration Preparation..... | 190 | +| 8.3.2.1 | General..... | 190 | +| 8.3.2.2 | Successful Operation..... | 190 | +| 8.3.2.3 | Unsuccessful Operation..... | 237 | +| 8.3.2.4 | Abnormal Conditions..... | 239 | +| 8.3.3 | Synchronised Radio Link Reconfiguration Commit..... | 245 | +| 8.3.3.1 | General..... | 245 | +| 8.3.3.2 | Successful Operation..... | 245 | +| 8.3.3.3 | Abnormal Conditions..... | 246 | +| 8.3.4 | Synchronised Radio Link Reconfiguration Cancellation..... | 247 | +| 8.3.4.1 | General..... | 247 | +| 8.3.4.2 | Successful Operation..... | 247 | +| 8.3.4.3 | Abnormal Conditions..... | 247 | +| 8.3.5 | Unsynchronised Radio Link Reconfiguration..... | 247 | +| 8.3.5.1 | General..... | 247 | +| 8.3.5.2 | Successful Operation..... | 247 | +| 8.3.5.3 | Unsuccessful Operation..... | 288 | +| 8.3.5.4 | Abnormal Conditions..... | 289 | +| 8.3.6 | Radio Link Deletion..... | 295 | +| 8.3.6.1 | General..... | 295 | +| 8.3.6.2 | Successful Operation..... | 295 | +| 8.3.6.3 | Unsuccessful Operation..... | 295 | +| 8.3.6.4 | Abnormal Conditions..... | 295 | +| 8.3.7 | Downlink Power Control [FDD]..... | 295 | +| 8.3.7.1 | General..... | 295 | +| 8.3.7.2 | Successful Operation..... | 296 | +| 8.3.7.3 | Abnormal Conditions..... | 297 | +| 8.3.8 | Dedicated Measurement Initiation..... | 297 | +| 8.3.8.1 | General..... | 297 | +| 8.3.8.2 | Successful Operation..... | 297 | +| 8.3.8.3 | Unsuccessful Operation..... | 300 | +| 8.3.8.4 | Abnormal Conditions..... | 301 | +| 8.3.9 | Dedicated Measurement Reporting..... | 302 | +| 8.3.9.1 | General..... | 302 | +| 8.3.9.2 | Successful Operation..... | 302 | +| 8.3.9.3 | Abnormal Conditions..... | 302 | +| 8.3.10 | Dedicated Measurement Termination..... | 303 | +| 8.3.10.1 | General..... | 303 | +| 8.3.10.2 | Successful Operation..... | 303 | +| 8.3.10.3 | Abnormal Conditions..... | 303 | +| 8.3.11 | Dedicated Measurement Failure..... | 303 | +| 8.3.11.1 | General..... | 303 | +| 8.3.11.2 | Successful Operation..... | 303 | +| 8.3.11.3 | Abnormal Conditions..... | 304 | +| 8.3.12 | Radio Link Failure..... | 304 | +| 8.3.12.1 | General..... | 304 | +| 8.3.12.2 | Successful Operation..... | 304 | +| 8.3.12.3 | Abnormal Conditions..... | 305 | +| 8.3.13 | Radio Link Restoration..... | 305 | +| 8.3.13.1 | General..... | 305 | +| 8.3.13.2 | Successful Operation..... | 305 | +| 8.3.13.3 | Abnormal Condition..... | 306 | +| 8.3.14 | Compressed Mode Command [FDD]..... | 306 | +| 8.3.14.1 | General..... | 306 | +| 8.3.14.2 | Successful Operation..... | 306 | +| 8.3.14.3 | Abnormal Conditions..... | 307 | +| 8.3.15 | Downlink Power Timeslot Control [TDD]..... | 307 | +| 8.3.15.1 | General..... | 307 | +| 8.3.15.2 | Successful Operation..... | 307 | + +| | | | +|----------|--------------------------------------------------------|-----| +| 8.3.15.3 | Abnormal Conditions..... | 307 | +| 8.3.16 | Radio Link Pre-emption..... | 307 | +| 8.3.16.1 | General..... | 307 | +| 8.3.16.2 | Successful Operation..... | 308 | +| 8.3.16.3 | Abnormal Conditions..... | 308 | +| 8.3.17 | Bearer Re-arrangement..... | 308 | +| 8.3.17.1 | General..... | 308 | +| 8.3.17.2 | Successful Operation..... | 308 | +| 8.3.17.3 | Abnormal Conditions..... | 309 | +| 8.3.18 | Radio Link Activation..... | 309 | +| 8.3.18.1 | General..... | 309 | +| 8.3.18.2 | Successful Operation..... | 309 | +| 8.3.18.3 | Abnormal Conditions..... | 310 | +| 8.3.19 | Radio Link Parameter Update..... | 310 | +| 8.3.19.1 | General..... | 310 | +| 8.3.19.2 | Successful Operation..... | 310 | +| 8.3.19.3 | Abnormal Conditions..... | 311 | +| 8.3.20 | Secondary UL Frequency Reporting [FDD]..... | 312 | +| 8.3.20.1 | General..... | 312 | +| 8.3.20.2 | Successful Operation..... | 312 | +| 8.3.20.3 | Abnormal Conditions..... | 312 | +| 8.3.21 | Secondary UL Frequency Update [FDD]..... | 312 | +| 8.3.21.1 | General..... | 312 | +| 8.3.21.2 | Successful Operation..... | 313 | +| 8.3.21.3 | Abnormal Conditions..... | 313 | +| 8.4 | Error Handling Procedures..... | 313 | +| 8.4.1 | Error Indication..... | 313 | +| 8.4.1.1 | General..... | 313 | +| 8.4.1.2 | Successful Operation..... | 313 | +| 8.4.1.3 | Abnormal Conditions..... | 314 | +| 9 | Elements for NBAP communication..... | 314 | +| 9.1 | Message Functional Defintion and Contents..... | 314 | +| 9.1.1 | General..... | 314 | +| 9.1.2 | Message Contents..... | 315 | +| 9.1.2.1 | Presence..... | 315 | +| 9.1.2.2 | Criticality..... | 315 | +| 9.1.2.3 | Range..... | 315 | +| 9.1.2.4 | Assigned Criticality..... | 315 | +| 9.1.3 | COMMON TRANSPORT CHANNEL SETUP REQUEST..... | 316 | +| 9.1.3.1 | FDD Message..... | 316 | +| 9.1.3.2 | TDD Message..... | 320 | +| 9.1.4 | COMMON TRANSPORT CHANNEL SETUP RESPONSE..... | 330 | +| 9.1.5 | COMMON TRANSPORT CHANNEL SETUP FAILURE..... | 330 | +| 9.1.6 | COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST..... | 331 | +| 9.1.6.1 | FDD Message..... | 331 | +| 9.1.6.2 | TDD Message..... | 332 | +| 9.1.7 | COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE..... | 335 | +| 9.1.8 | COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE..... | 335 | +| 9.1.9 | COMMON TRANSPORT CHANNEL DELETION REQUEST..... | 336 | +| 9.1.10 | COMMON TRANSPORT CHANNEL DELETION RESPONSE..... | 336 | +| 9.1.11 | BLOCK RESOURCE REQUEST..... | 336 | +| 9.1.12 | BLOCK RESOURCE RESPONSE..... | 337 | +| 9.1.13 | BLOCK RESOURCE FAILURE..... | 337 | +| 9.1.14 | UNBLOCK RESOURCE INDICATION..... | 337 | +| 9.1.15 | AUDIT REQUIRED INDICATION..... | 337 | +| 9.1.16 | AUDIT REQUEST..... | 338 | +| 9.1.17 | AUDIT RESPONSE..... | 339 | +| 9.1.17A | AUDIT FAILURE..... | 346 | +| 9.1.18 | COMMON MEASUREMENT INITIATION REQUEST..... | 347 | +| 9.1.19 | COMMON MEASUREMENT INITIATION RESPONSE..... | 350 | +| 9.1.20 | COMMON MEASUREMENT INITIATION FAILURE..... | 351 | + +| | | | +|----------|------------------------------------------------|-----| +| 9.1.21 | COMMON MEASUREMENT REPORT..... | 352 | +| 9.1.22 | COMMON MEASUREMENT TERMINATION REQUEST..... | 353 | +| 9.1.23 | COMMON MEASUREMENT FAILURE INDICATION..... | 353 | +| 9.1.24 | CELL SETUP REQUEST..... | 354 | +| 9.1.24.1 | FDD Message..... | 354 | +| 9.1.24.2 | TDD Message..... | 357 | +| 9.1.25 | CELL SETUP RESPONSE..... | 361 | +| 9.1.26 | CELL SETUP FAILURE..... | 361 | +| 9.1.27 | CELL RECONFIGURATION REQUEST..... | 362 | +| 9.1.27.1 | FDD Message..... | 362 | +| 9.1.27.2 | TDD Message..... | 364 | +| 9.1.28 | CELL RECONFIGURATION RESPONSE..... | 367 | +| 9.1.29 | CELL RECONFIGURATION FAILURE..... | 367 | +| 9.1.30 | CELL DELETION REQUEST..... | 367 | +| 9.1.31 | CELL DELETION RESPONSE..... | 367 | +| 9.1.32 | RESOURCE STATUS INDICATION..... | 368 | +| 9.1.33 | SYSTEM INFORMATION UPDATE REQUEST..... | 378 | +| 9.1.34 | SYSTEM INFORMATION UPDATE RESPONSE..... | 379 | +| 9.1.35 | SYSTEM INFORMATION UPDATE FAILURE..... | 380 | +| 9.1.36 | RADIO LINK SETUP REQUEST..... | 381 | +| 9.1.36.1 | FDD message..... | 381 | +| 9.1.36.2 | TDD message..... | 385 | +| 9.1.37 | RADIO LINK SETUP RESPONSE..... | 390 | +| 9.1.37.1 | FDD message..... | 390 | +| 9.1.37.2 | TDD Message..... | 392 | +| 9.1.38 | RADIO LINK SETUP FAILURE..... | 395 | +| 9.1.38.1 | FDD Message..... | 395 | +| 9.1.38.2 | TDD Message..... | 397 | +| 9.1.39 | RADIO LINK ADDITION REQUEST..... | 398 | +| 9.1.39.1 | FDD Message..... | 398 | +| 9.1.39.2 | TDD Message..... | 401 | +| 9.1.40 | RADIO LINK ADDITION RESPONSE..... | 405 | +| 9.1.40.1 | FDD message..... | 405 | +| 9.1.40.2 | TDD Message..... | 407 | +| 9.1.41 | RADIO LINK ADDITION FAILURE..... | 410 | +| 9.1.41.1 | FDD Message..... | 410 | +| 9.1.41.2 | TDD Message..... | 411 | +| 9.1.42 | RADIO LINK RECONFIGURATION PREPARE..... | 412 | +| 9.1.42.1 | FDD Message..... | 412 | +| 9.1.42.2 | TDD Message..... | 417 | +| 9.1.43 | RADIO LINK RECONFIGURATION READY..... | 429 | +| 9.1.44 | RADIO LINK RECONFIGURATION FAILURE..... | 431 | +| 9.1.45 | RADIO LINK RECONFIGURATION COMMIT..... | 432 | +| 9.1.46 | RADIO LINK RECONFIGURATION CANCEL..... | 432 | +| 9.1.47 | RADIO LINK RECONFIGURATION REQUEST..... | 433 | +| 9.1.47.1 | FDD Message..... | 433 | +| 9.1.47.2 | TDD Message..... | 437 | +| 9.1.48 | RADIO LINK RECONFIGURATION RESPONSE..... | 442 | +| 9.1.49 | RADIO LINK DELETION REQUEST..... | 444 | +| 9.1.50 | RADIO LINK DELETION RESPONSE..... | 444 | +| 9.1.51 | DL POWER CONTROL REQUEST [FDD]..... | 445 | +| 9.1.52 | DEDICATED MEASUREMENT INITIATION REQUEST..... | 446 | +| 9.1.53 | DEDICATED MEASUREMENT INITIATION RESPONSE..... | 448 | +| 9.1.54 | DEDICATED MEASUREMENT INITIATION FAILURE..... | 450 | +| 9.1.55 | DEDICATED MEASUREMENT REPORT..... | 451 | +| 9.1.56 | DEDICATED MEASUREMENT TERMINATION REQUEST..... | 452 | +| 9.1.57 | DEDICATED MEASUREMENT FAILURE INDICATION..... | 453 | +| 9.1.58 | RADIO LINK FAILURE INDICATION..... | 454 | +| 9.1.59 | RADIO LINK RESTORE INDICATION..... | 455 | +| 9.1.60 | COMPRESSED MODE COMMAND [FDD]..... | 455 | +| 9.1.61 | ERROR INDICATION..... | 456 | + +| | | | +|----------|-------------------------------------------------------------|-----| +| 9.1.62 | PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST..... | 456 | +| 9.1.62.1 | FDD Message..... | 456 | +| 9.1.62.2 | TDD Message..... | 458 | +| 9.1.63 | PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE..... | 479 | +| 9.1.64 | PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE..... | 480 | +| 9.1.65 | RESET REQUEST..... | 481 | +| 9.1.66 | RESET RESPONSE..... | 482 | +| 9.1.67 | DL POWER TIMESLOT CONTROL REQUEST [TDD]..... | 483 | +| 9.1.68 | RADIO LINK PREEMPTION REQUIRED INDICATION..... | 483 | +| 9.1.69 | INFORMATION EXCHANGE INITIATION REQUEST..... | 483 | +| 9.1.70 | INFORMATION EXCHANGE INITIATION RESPONSE..... | 484 | +| 9.1.71 | INFORMATION EXCHANGE INITIATION FAILURE..... | 484 | +| 9.1.72 | INFORMATION REPORT..... | 484 | +| 9.1.73 | INFORMATION EXCHANGE TERMINATION REQUEST..... | 484 | +| 9.1.74 | INFORMATION EXCHANGE FAILURE INDICATION..... | 485 | +| 9.1.75 | CELL SYNCHRONISATION INITIATION REQUEST [TDD]..... | 485 | +| 9.1.76 | CELL SYNCHRONISATION INITIATION RESPONSE [TDD]..... | 486 | +| 9.1.77 | CELL SYNCHRONISATION INITIATION FAILURE [TDD]..... | 486 | +| 9.1.78 | CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD]..... | 487 | +| 9.1.79 | CELL SYNCHRONISATION RECONFIGURATION RESPONSE [TDD]..... | 489 | +| 9.1.80 | CELL SYNCHRONISATION RECONFIGURATION FAILURE [TDD]..... | 489 | +| 9.1.81 | CELL SYNCHRONISATION REPORT [TDD]..... | 489 | +| 9.1.82 | CELL SYNCHRONISATION TERMINATION REQUEST [TDD]..... | 490 | +| 9.1.83 | CELL SYNCHRONISATION FAILURE INDICATION [TDD]..... | 491 | +| 9.1.84 | CELL SYNCHRONISATION ADJUSTMENT REQUEST [TDD]..... | 491 | +| 9.1.85 | CELL SYNCHRONISATION ADJUSTMENT RESPONSE [TDD]..... | 491 | +| 9.1.86 | CELL SYNCHRONISATION ADJUSTMENT FAILURE [TDD]..... | 492 | +| 9.1.87 | BEARER REARRANGEMENT INDICATION..... | 493 | +| 9.1.88 | RADIO LINK ACTIVATION COMMAND..... | 494 | +| 9.1.88.1 | FDD Message..... | 494 | +| 9.1.88.2 | TDD Message..... | 494 | +| 9.1.89 | RADIO LINK PARAMETER UPDATE INDICATION..... | 495 | +| 9.1.89.1 | FDD Message..... | 495 | +| 9.1.89.2 | TDD Message..... | 496 | +| 9.1.90 | MBMS NOTIFICATION UPDATE COMMAND..... | 496 | +| 9.1.91 | UE STATUS UPDATE COMMAND..... | 496 | +| 9.1.92 | SECONDARY UL FREQUENCY REPORT..... | 497 | +| 9.1.92.1 | FDD Message..... | 497 | +| 9.1.93 | SECONDARY UL FREQUENCY UPDATE INDICATION..... | 497 | +| 9.1.93.1 | FDD Message..... | 497 | +| 9.1.94 | UE STATUS UPDATE CONFIRM REQUEST..... | 497 | +| 9.1.95 | UE STATUS UPDATE CONFIRM RESPONSE..... | 498 | +| 9.2 | Information Element Functional Definition and Contents..... | 498 | +| 9.2.0 | General..... | 498 | +| 9.2.1 | Common parameters..... | 498 | +| 9.2.1.1 | Add/Delete Indicator..... | 498 | +| 9.2.1.1A | Allocation/Retention Priority..... | 498 | +| 9.2.1.1B | Alternative Format Reporting Indicator..... | 499 | +| 9.2.1.2 | Availability Status..... | 499 | +| 9.2.1.3 | BCCH Modification Time..... | 499 | +| 9.2.1.4 | Binding ID..... | 500 | +| 9.2.1.4A | BLER..... | 500 | +| 9.2.1.5 | Blocking Priority Indicator..... | 500 | +| 9.2.1.5A | Burst Mode Parameters..... | 500 | +| 9.2.1.5B | Broadcast Common Transport Bearer Indication..... | 501 | +| 9.2.1.5C | Broadcast Reference..... | 501 | +| 9.2.1.6 | Cause..... | 502 | +| 9.2.1.7 | CFN..... | 507 | +| 9.2.1.8 | CFN Offset..... | 508 | +| 9.2.1.9 | C-ID..... | 508 | +| 9.2.1.9A | Common Channels Capacity Consumption Law..... | 508 | + +| | | | +|-------------|------------------------------------------------------|-----| +| 9.2.1.9B | Common Measurement Accuracy..... | 509 | +| 9.2.1.10 | Common Measurement Object Type..... | 509 | +| 9.2.1.11 | Common Measurement Type..... | 509 | +| 9.2.1.12 | Common Measurement Value..... | 511 | +| 9.2.1.12A | Common Measurement Value Information..... | 517 | +| 9.2.1.13 | Common Physical Channel ID..... | 517 | +| 9.2.1.13A | Common Physical Channel Status Information..... | 518 | +| 9.2.1.14 | Common Transport Channel ID..... | 518 | +| 9.2.1.14A | Common Transport Channel Information Response..... | 518 | +| 9.2.1.14B | Common Transport Channel Status Information..... | 518 | +| 9.2.1.15 | Communication Control Port ID..... | 518 | +| 9.2.1.16 | Configuration Generation ID..... | 519 | +| 9.2.1.17 | Criticality Diagnostics..... | 519 | +| 9.2.1.18 | CRNC Communication Context ID..... | 521 | +| 9.2.1.18A | CTFC..... | 521 | +| 9.2.1.19 | DCH Combination Indicator..... | 522 | +| 9.2.1.20 | DCH ID..... | 522 | +| 9.2.1.20A | Dedicated Channels Capacity Consumption Law..... | 522 | +| 9.2.1.20B | DL Or Global Capacity Credit..... | 523 | +| 9.2.1.20C | DCH Information Response..... | 524 | +| 9.2.1.21 | DL Power..... | 524 | +| 9.2.1.22 | Dedicated Measurement Object Type..... | 524 | +| 9.2.1.23 | Dedicated Measurement Type..... | 524 | +| 9.2.1.24 | Dedicated Measurement Value..... | 525 | +| 9.2.1.24A | Dedicated Measurement Value Information..... | 528 | +| 9.2.1.24B | DGPS Corrections..... | 528 | +| 9.2.1.24C | Delayed Activation..... | 529 | +| 9.2.1.24D | Delayed Activation Update..... | 530 | +| 9.2.1.24E | Discard Timer..... | 530 | +| 9.2.1.25 | Diversity Control Field..... | 530 | +| 9.2.1.26 | Diversity Indication..... | 531 | +| 9.2.1.26A | DL DPCH Timing Adjustment..... | 531 | +| 9.2.1.27 | DSCH ID..... | 531 | +| 9.2.1.27A | DSCH Information Response..... | 531 | +| 9.2.1.28 | DSCH Transport Format Set..... | 531 | +| 9.2.1.29 | DSCH Transport Format Combination Set..... | 531 | +| 9.2.1.29A | End Of Audit Sequence Indicator..... | 531 | +| 9.2.1.29B | FN Reporting Indicator..... | 531 | +| 9.2.1.30 | Frame Handling Priority..... | 532 | +| 9.2.1.31 | Frame Offset..... | 532 | +| 9.2.1.31A | IB_OC_ID..... | 532 | +| 9.2.1.31B | GPS Navigation Model & Time Recovery..... | 532 | +| 9.2.1.31C | GPS Ionospheric Model..... | 534 | +| 9.2.1.31D | GPS UTC Model..... | 534 | +| 9.2.1.31E | GPS Real-Time Integrity..... | 535 | +| 9.2.1.31F | GPS Almanac..... | 535 | +| 9.2.1.31G | GPS Receiver Geographical Position (GPS RX Pos)..... | 536 | +| 9.2.1.31Ga | HSDPA Capability..... | 537 | +| 9.2.1.31H | HS-DSCH Information To Modify..... | 537 | +| 9.2.1.31HA | HS-DSCH Information To Modify Unsynchronised..... | 541 | +| 9.2.1.31Ha | HS-DSCH Initial Capacity Allocation..... | 544 | +| 9.2.1.31Hb | HS-DSCH Initial Window Size..... | 544 | +| 9.2.1.31I | HS-DSCH MAC-d Flow ID..... | 544 | +| 9.2.1.31IA | HS-DSCH MAC-d Flows Information..... | 545 | +| 9.2.1.31IB | HS-DSCH MAC-d Flows To Delete..... | 547 | +| 9.2.1.31IC | HS-DSCH MAC-d PDU Size Capability..... | 547 | +| 9.2.1.31ID | HS-DSCH MAC-d PDU Size Format..... | 547 | +| 9.2.1.31Ia | HS-DSCH Physical Layer Category..... | 547 | +| 9.2.1.31Iaa | HS-DSCH Provided Bit Rate Value..... | 548 | +| 9.2.1.31Ib | HS-DSCH Provided Bit Rate Value Information..... | 548 | +| 9.2.1.31Iba | HS-DSCH Required Power Value..... | 548 | + +| | | | +|------------|--------------------------------------------------------|-----| +| 9.2.1.31Ic | HS-DSCH Required Power Value Information..... | 548 | +| 9.2.1.31J | HS-DSCH RNTI..... | 549 | +| 9.2.1.31K | HS-SCCH Code Change Indicator..... | 549 | +| 9.2.1.31L | HS-SCCH Code Change Grant..... | 549 | +| 9.2.1.31M | HS-PDSCH Code Change Indicator [FDD]..... | 549 | +| 9.2.1.31N | HS-PDSCH Code Change Grant [FDD]..... | 550 | +| 9.2.1.32 | IB_SG_DATA..... | 550 | +| 9.2.1.33 | IB_SG_POS..... | 550 | +| 9.2.1.34 | IB_SG_REP..... | 550 | +| 9.2.1.35 | IB Type..... | 550 | +| 9.2.1.36 | Indication Type..... | 551 | +| 9.2.1.36A | Information Exchange Object Type..... | 551 | +| 9.2.1.36B | Information Report Characteristics..... | 552 | +| 9.2.1.36C | Information Exchange ID..... | 552 | +| 9.2.1.36D | Information Type..... | 552 | +| 9.2.1.36E | Information Threshold..... | 555 | +| 9.2.1.36F | IPDL Indicator..... | 555 | +| 9.2.1.37 | Limited Power Increase..... | 555 | +| 9.2.1.37A | Local Cell Group ID..... | 555 | +| 9.2.1.38 | Local Cell ID..... | 556 | +| 9.2.1.38A | MAC-d PDU Size..... | 556 | +| 9.2.1.38Aa | MAC-hs Guaranteed Bit Rate..... | 556 | +| 9.2.1.38Ab | MAC-hs Reordering Buffer Size for RLC-UM..... | 556 | +| 9.2.1.38Ac | MAC-hs Reset Indicator..... | 556 | +| 9.2.1.38B | MAC-hs Window Size..... | 557 | +| 9.2.1.38C | MAC PDU Size Extended..... | 557 | +| 9.2.1.39 | Maximum DL Power Capability..... | 557 | +| 9.2.1.40 | Maximum Transmission Power..... | 557 | +| 9.2.1.40A | Measurement Availability Indicator..... | 557 | +| 9.2.1.40B | Measurement Change Time..... | 557 | +| 9.2.1.41 | Measurement Filter Coefficient..... | 558 | +| 9.2.1.41A | Measurement Hysteresis Time..... | 558 | +| 9.2.1.42 | Measurement ID..... | 558 | +| 9.2.1.43 | Measurement Increase/Decrease Threshold..... | 558 | +| 9.2.1.43A | Measurement Recovery Behavior..... | 561 | +| 9.2.1.43B | Measurement Recovery Reporting Indicator ..... | 561 | +| 9.2.1.43C | Measurement Recovery Support Indicator..... | 561 | +| 9.2.1.44 | Measurement Threshold..... | 562 | +| 9.2.1.45 | Message Discriminator..... | 566 | +| 9.2.1.45A | Message Structure..... | 567 | +| 9.2.1.46 | Message Type..... | 567 | +| 9.2.1.46a | MICH CFN..... | 568 | +| 9.2.1.46A | Minimum DL Power Capability..... | 568 | +| 9.2.1.47 | Minimum Spreading Factor..... | 568 | +| 9.2.1.47a | Modification Period..... | 568 | +| 9.2.1.47A | N_INSYNC_IND..... | 569 | +| 9.2.1.47B | N_OUTSYNC_IND..... | 569 | +| 9.2.1.47C | Neighbouring FDD Cell Measurement Information..... | 569 | +| 9.2.1.47D | Neighbouring TDD Cell Measurement Information..... | 569 | +| 9.2.1.47E | Neighbouring TDD Cell Measurement Information LCR..... | 569 | +| 9.2.1.47F | NI..... | 570 | +| 9.2.1.48 | Node B Communication Context ID..... | 570 | +| 9.2.1.49 | Payload CRC Presence Indicator..... | 570 | +| 9.2.1.49A | PICH Power..... | 570 | +| 9.2.1.49B | Power Local Cell Group ID..... | 571 | +| 9.2.1.49C | Priority Queue ID..... | 571 | +| 9.2.1.49D | Process Memory Size..... | 571 | +| 9.2.1.50 | Puncture Limit..... | 571 | +| 9.2.1.50A | QE-Selector..... | 572 | +| 9.2.1.51 | Report Characteristics..... | 572 | +| 9.2.1.51a | Report Periodicity..... | 574 | + +| | | | +|-----------|---------------------------------------------------------------|-----| +| 9.2.1.51A | Requested Data Value..... | 574 | +| 9.2.1.51B | Requested Data Value Information..... | 576 | +| 9.2.1.52 | Resource Operational State..... | 576 | +| 9.2.1.52A | Retention Priority..... | 576 | +| 9.2.1.52B | RLC Mode..... | 576 | +| 9.2.1.53 | RL ID..... | 576 | +| 9.2.1.53a | RNC-Id..... | 577 | +| 9.2.1.53b | RTWP* Reporting Indicator..... | 577 | +| 9.2.1.53c | RTWP* for Cell Portion Reporting Indicator..... | 577 | +| 9.2.1.53A | SFN..... | 577 | +| 9.2.1.53B | Segment Type..... | 577 | +| 9.2.1.53C | SFN-SFN Measurement Threshold Information..... | 578 | +| 9.2.1.53D | SFN-SFN Measurement Time Stamp..... | 578 | +| 9.2.1.53E | SFN-SFN Measurement Value Information..... | 578 | +| 9.2.1.53F | SFN-SFN Value..... | 579 | +| 9.2.1.53G | RL Specific DCH Information..... | 580 | +| 9.2.1.53H | Scheduling Priority Indicator..... | 580 | +| 9.2.1.53I | SID..... | 580 | +| 9.2.1.54 | SIB Deletion Indicator..... | 580 | +| 9.2.1.55 | SIB Originator..... | 580 | +| 9.2.1.55A | Signalling Bearer Request Indicator..... | 581 | +| 9.2.1.56 | Shutdown Timer..... | 581 | +| 9.2.1.56a | T1..... | 581 | +| 9.2.1.56A | T_RLFAILURE..... | 581 | +| 9.2.1.56B | Start Of Audit Sequence Indicator..... | 581 | +| 9.2.1.56C | TFCI2 Bearer Request Indicator..... | 582 | +| 9.2.1.57 | TFCI Presence..... | 582 | +| 9.2.1.58 | TFCS (Transport Format Combination Set)..... | 582 | +| 9.2.1.58A | TNL QoS..... | 583 | +| 9.2.1.59 | Transport Format Set..... | 584 | +| 9.2.1.60 | ToAWE..... | 585 | +| 9.2.1.61 | ToAWS..... | 586 | +| 9.2.1.62 | Transaction ID..... | 586 | +| 9.2.1.62A | Transport Bearer Request Indicator..... | 586 | +| 9.2.1.63 | Transport Layer Address..... | 586 | +| 9.2.1.64 | TSTD Indicator..... | 587 | +| 9.2.1.64A | T UTRAN-GPS Measurement Value Information..... | 587 | +| 9.2.1.64B | T UTRAN-GPS Measurement Threshold Information..... | 588 | +| 9.2.1.64C | T UTRAN-GPS Accuracy Class..... | 588 | +| 9.2.1.65 | UARFCN..... | 588 | +| 9.2.1.65A | UL Capacity Credit..... | 588 | +| 9.2.1.65B | UTRAN Cell Identifier (UC-Id)..... | 588 | +| 9.2.1.65C | Extended RNC-ID..... | 589 | +| 9.2.1.66 | UL FP Mode..... | 589 | +| 9.2.1.67 | UL interference level..... | 589 | +| 9.2.1.67A | UL SIR..... | 589 | +| 9.2.1.68 | Unidirectional DCH Indicator..... | 589 | +| 9.2.1.69 | E-DCH MAC-d Flow Multiplexing List..... | 590 | +| 9.2.1.70 | E-DCH Capability..... | 590 | +| 9.2.1.71 | E-DCH Logical Channel Information..... | 590 | +| 9.2.1.72 | E-DCH Logical Channel To Modify..... | 591 | +| 9.2.1.73 | E-DCH MAC-d Flows To Delete..... | 592 | +| 9.2.1.74 | E-DCH MAC-d Flow ID..... | 593 | +| 9.2.1.74A | E-DCH MAC-d PDU Size Capability..... | 593 | +| 9.2.1.74B | E-DCH MAC-d PDU Size Format..... | 593 | +| 9.2.1.75 | E-RNTI..... | 593 | +| 9.2.1.76 | E-DCH DDI Value..... | 593 | +| 9.2.1.77 | E-DCH Provided Bit Rate Value..... | 594 | +| 9.2.1.78 | E-DCH Provided Bit Rate Value Information..... | 594 | +| 9.2.1.79 | E-DCH Processing Overload Level..... | 594 | +| 9.2.1.80 | Logical channel ID..... | 594 | + +| | | | +|------------|-------------------------------------------------------------------|-----| +| 9.2.1.81 | Maximum Number Of Retransmissions For E-DCH..... | 595 | +| 9.2.1.82 | MAC-es Guaranteed Bit Rate..... | 595 | +| 9.2.1.83 | MAC-e Reset Indicator..... | 595 | +| 9.2.1.84 | Scheduling Information..... | 595 | +| 9.2.1.85 | E-DCH Power Offset for Scheduling Info..... | 595 | +| 9.2.1.86 | MBMS Capability..... | 595 | +| 9.2.1.87 | Modulation..... | 596 | +| 9.2.1.88 | DGANSS Corrections..... | 596 | +| 9.2.1.89 | GANSS Almanac..... | 598 | +| 9.2.1.90 | GANSS Clock Model..... | 603 | +| 9.2.1.90a | GANSS Additional Clock Models..... | 604 | +| 9.2.1.91 | GANSS Ionospheric Model..... | 606 | +| 9.2.1.91a | GANSS Additional Ionospheric Model..... | 606 | +| 9.2.1.92 | GANSS Navigation Model..... | 606 | +| 9.2.1.93 | GANSS Orbit Model..... | 606 | +| 9.2.1.93a | GANSS Additional Orbit Models..... | 607 | +| 9.2.1.94 | GANSS Real Time Integrity..... | 612 | +| 9.2.1.95 | GANSS Receiver Geographical Position (GANSS RX Pos)..... | 613 | +| 9.2.1.96 | GANSS Time Model..... | 613 | +| 9.2.1.96a | GANSS Additional Time Models..... | 614 | +| 9.2.1.97 | GANSS UTC Model..... | 614 | +| 9.2.1.97a | GANSS Additional UTC Models..... | 615 | +| 9.2.1.98 | TUTRAN-GANSS Accuracy Class..... | 617 | +| 9.2.1.99 | TUTRAN-GANSS Measurement Threshold Information..... | 617 | +| 9.2.1.100 | TUTRAN-GANSS Measurement Value Information..... | 618 | +| 9.2.1.101 | GANSS Reference Time..... | 620 | +| 9.2.1.102 | HARQ Memory Partitioning..... | 621 | +| 9.2.1.103 | GANSS Data Bit Assistance..... | 622 | +| 9.2.1.104 | GANSS ID..... | 622 | +| 9.2.1.104a | GANSS Time ID..... | 622 | +| 9.2.1.105 | GANSS Navigation Model And Time Recovery..... | 622 | +| 9.2.1.105a | GANSS Additional Navigation Models And Time Recovery..... | 623 | +| 9.2.1.106 | GANSS Signal ID..... | 624 | +| 9.2.1.107 | GANSS Transmission Time..... | 624 | +| 9.2.1.107a | GANSS Earth Orientation Parameters..... | 625 | +| 9.2.1.107b | SBAS ID..... | 625 | +| 9.2.1.107c | GANSS Auxiliary Information..... | 626 | +| 9.2.1.107d | Additional Ionospheric Model Request..... | 626 | +| 9.2.1.107e | Earth Orientation Parameters Request..... | 626 | +| 9.2.1.107f | GANSS Additional Navigation Models And Time Recovery Request..... | 626 | +| 9.2.1.107g | GANSS Additional UTC Models Request..... | 627 | +| 9.2.1.107h | GANSS Auxiliary Information Request..... | 627 | +| 9.2.1.108 | IP Multicast Indication..... | 627 | +| 9.2.1.109 | IP Multicast Data Bearer Indication..... | 627 | +| 9.2.1.110 | SixtyfourQAM DL Capability..... | 627 | +| 9.2.1.111 | FACH Measurement Occasion Cycle Length Coefficient..... | 628 | +| 9.2.1.112 | MAC-ehs Reset Timer..... | 628 | +| 9.2.1.113 | Paging MAC Flow ID..... | 628 | +| 9.2.1.114 | Enhanced FACH Capability..... | 628 | +| 9.2.1.115 | Enhanced PCH Capability..... | 628 | +| 9.2.1.116 | Enhanced UE DRX Capability..... | 629 | +| 9.2.1.117 | Priority Queue Information for Enhanced FACH/PCH..... | 629 | +| 9.2.1.118 | MIMO Capability..... | 629 | +| 9.2.1.119 | MIMO Activation Indicator..... | 629 | +| 9.2.1.120 | MIMO Mode Indicator..... | 629 | +| 9.2.1.121 | SixtyfourQAM DL and MIMO Combined Capability..... | 629 | +| 9.2.1.122 | DL RLC PDU Size Format..... | 630 | +| 9.2.1.123 | UE Aggregate Maximum Bit Rate..... | 630 | +| 9.2.1.124 | Dormant Mode Indicator..... | 631 | +| 9.2.1.125 | DGNSS Validity Period..... | 631 | +| 9.2.1.126 | E-RNTI Release Status..... | 631 | + +| | | | +|------------|------------------------------------------------------------------------------|-----| +| 9.2.1.127 | DBDS Corrections..... | 631 | +| 9.2.1.128 | BDS Ionospheric Grid Model..... | 632 | +| 9.2.1.129 | Improved Synchronized RRC Indicator..... | 632 | +| 9.2.2 | FDD specific parameters..... | 633 | +| 9.2.2.a | ACK-NACK Repetition Factor..... | 633 | +| 9.2.2.b | ACK Power Offset..... | 633 | +| 9.2.2.A | Active Pattern Sequence Information..... | 633 | +| 9.2.2.B | Adjustment Period..... | 634 | +| 9.2.2.C | Adjustment Ratio..... | 634 | +| 9.2.2.D | AICH Power..... | 634 | +| 9.2.2.1 | AICH Transmission Timing..... | 634 | +| 9.2.2.1A | AP Preamble Signature..... | 634 | +| 9.2.2.1B | AP Sub Channel Number..... | 634 | +| 9.2.2.1Ba | Best Cell Portions..... | 635 | +| 9.2.2.1Bb | Bundling Mode Indicator..... | 635 | +| 9.2.2.1C | CD Sub Channel Numbers..... | 635 | +| 9.2.2.1Ca | Cell Portion ID..... | 635 | +| 9.2.2.1D | Channel Assignment Indication..... | 635 | +| 9.2.2.2 | Chip Offset..... | 635 | +| 9.2.2.2A | Closed Loop Timing Adjustment Mode..... | 635 | +| 9.2.2.3 | Common Channels Capacity Consumption Law..... | 636 | +| 9.2.2.3A | Compressed Mode Deactivation Flag..... | 636 | +| 9.2.2.4 | Compressed Mode Method..... | 636 | +| 9.2.2.4A | CPCH Allowed Total Rate..... | 636 | +| 9.2.2.4B | CPCH Scrambling Code Number..... | 636 | +| 9.2.2.4C | CPCH UL DPCCH Slot Format..... | 636 | +| 9.2.2.4Ca | CQI Power Offset..... | 636 | +| 9.2.2.4Cb | CQI Repetition Factor..... | 636 | +| 9.2.2.4D | DCH FDD Information..... | 637 | +| 9.2.2.4E | DCHs FDD To Modify..... | 637 | +| 9.2.2.4F | DCH Indicator For E-DCH-HSDPA Operation..... | 638 | +| 9.2.2.4G | Transport Bearer Not Requested Indicator..... | 638 | +| 9.2.2.4H | Transport Bearer Not Setup Indicator..... | 638 | +| 9.2.2.5 | D-Field Length..... | 638 | +| 9.2.2.6 | Dedicated Channels Capacity Consumption Law..... | 638 | +| 9.2.2.7 | Diversity Control Field..... | 638 | +| 9.2.2.8 | Diversity Indication..... | 638 | +| 9.2.2.9 | Diversity Mode..... | 639 | +| 9.2.2.10 | DL DPCH Slot Format..... | 639 | +| 9.2.2.10A | DL DPCH Timing Adjustment..... | 639 | +| 9.2.2.11 | DL frame type..... | 639 | +| 9.2.2.12 | DL or Global Capacity Credit..... | 639 | +| 9.2.2.12A | DL_power_averaging_window_size..... | 639 | +| 9.2.2.12B | DL Power Balancing Information..... | 639 | +| 9.2.2.12C | DL Power Balancing Activation Indicator..... | 640 | +| 9.2.2.12D | DL Power Balancing Updated Indicator..... | 640 | +| 9.2.2.13 | DL Scrambling Code..... | 640 | +| 9.2.2.13A | DL TPC Pattern 01 Count..... | 641 | +| 9.2.2.13B | DSCH FDD Information..... | 641 | +| 9.2.2.13C | DPC Mode..... | 641 | +| 9.2.2.13D | DSCH FDD Common Information..... | 641 | +| 9.2.2.13Da | E-DCH FDD Information..... | 641 | +| 9.2.2.13DA | E-DCH FDD Update Information..... | 642 | +| 9.2.2.13Db | E-DCH FDD Information Response..... | 643 | +| 9.2.2.13Dc | E-DCH FDD DL Control Channel Information..... | 643 | +| 9.2.2.13De | E-DCH RL Indication..... | 645 | +| 9.2.2.13Df | E-DCH FDD Information to Modify..... | 645 | +| 9.2.2.13Dh | E-DCH Transport Format Combination Set Information (E-TFCS Information)..... | 648 | +| 9.2.2.13Di | E-TTI..... | 649 | +| 9.2.2.13Dj | E-DPCCH Power Offset..... | 649 | +| 9.2.2.13Dk | E-DCH HARQ Power Offset FDD..... | 649 | + +| | | | +|------------|-----------------------------------------------------------------------------------|-----| +| 9.2.2.13Dl | E-DCH MAC-d Flow Multiplexing List..... | 649 | +| 9.2.2.13Dm | Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission..... | 649 | +| 9.2.2.13Dn | HARQ Process Allocation For 2ms TTI..... | 649 | +| 9.2.2.13Dp | Reference E-TFCI Power Offset..... | 650 | +| 9.2.2.13Dq | Extended Reference E-TFCI Power Offset..... | 650 | +| 9.2.2.13Dr | Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission..... | 650 | +| 9.2.2.13E | Enhanced DSCH PC..... | 650 | +| 9.2.2.13F | Enhanced DSCH PC Counter..... | 650 | +| 9.2.2.13G | Enhanced DSCH PC Indicator..... | 651 | +| 9.2.2.13H | Enhanced DSCH PC Wnd..... | 651 | +| 9.2.2.13I | Enhanced DSCH Power Offset..... | 651 | +| 9.2.2.13Ia | E- RGCH/E-HICH FDD Code Information..... | 651 | +| 9.2.2.13Ib | E- AGCH FDD Code Information..... | 651 | +| 9.2.2.13Ic | E-RGCH Release Indicator..... | 651 | +| 9.2.2.13Id | E-AGCH Power Offset..... | 652 | +| 9.2.2.13Ie | E-RGCH Power Offset..... | 652 | +| 9.2.2.13If | E-HICH Power Offset..... | 652 | +| 9.2.2.13Ig | E-RGCH 2-Index-Step Threshold..... | 652 | +| 9.2.2.13Ih | E-RGCH 3-Index-Step Threshold..... | 652 | +| 9.2.2.13J | E-DCH Capability..... | 653 | +| 9.2.2.13Ja | E-DCH Capacity Consumption Law..... | 653 | +| 9.2.2.13K | E-DCH Logical Channel Information..... | 654 | +| 9.2.2.13L | E-DCH Logical Channel To Modify..... | 654 | +| 9.2.2.13M | E-DCH MAC-d Flows Information..... | 654 | +| 9.2.2.13N | E-DCH MAC-d Flows To Delete..... | 656 | +| 9.2.2.13O | E-DCH MAC-d Flow ID..... | 656 | +| 9.2.2.13P | E-RNTI..... | 656 | +| 9.2.2.13Q | E-DCH DDI Value..... | 656 | +| 9.2.2.13R | E-DCH Provided Bit Rate Value..... | 656 | +| 9.2.2.13S | E-DCH Provided Bit Rate Value Information..... | 656 | +| 9.2.2.13T | E-DCH Maximum Bitrate..... | 656 | +| 9.2.2.13U | E-DCH Processing Overload Level..... | 656 | +| 9.2.2.13V | E-DCH TTI2ms Capability..... | 656 | +| 9.2.2.13W | E-DCH SF Capability..... | 657 | +| 9.2.2.13X | E-DCH HARQ Combining Capability..... | 657 | +| 9.2.2.13Y | E-DCH Reference Power Offset..... | 657 | +| 9.2.2.13Z | E-DCH Power Offset for Scheduling Info..... | 657 | +| 9.2.2.14 | FDD DL Channelisation Code Number..... | 657 | +| 9.2.2.14A | FDD DL Code Information..... | 658 | +| 9.2.2.14B | FDD S-CCPCH Frame Offset..... | 658 | +| 9.2.2.15 | FDD SCCPCH Offset..... | 658 | +| 9.2.2.16 | FDD TPC DL Step Size..... | 658 | +| 9.2.2.16a | F-DPCH Capability..... | 659 | +| 9.2.2.16A | First RLS Indicator..... | 659 | +| 9.2.2.17 | Gap Period..... | 659 | +| 9.2.2.18 | Gap Position Mode..... | 659 | +| 9.2.2.18a | HARQ Preamble Mode..... | 659 | +| 9.2.2.18b | HARQ Preamble Mode Activation Indicator..... | 659 | +| 9.2.2.18ba | HARQ Info for E-DCH..... | 659 | +| 9.2.2.18c | Logical channel ID..... | 660 | +| 9.2.2.18A | Limited Power Increase..... | 660 | +| 9.2.2.18B | Inner Loop DL PC Status..... | 660 | +| 9.2.2.18C | IPDL FDD Parameters..... | 660 | +| 9.2.2.18Ca | HS-DSCH configured indicator..... | 660 | +| 9.2.2.18D | HS-DSCH FDD Information..... | 661 | +| 9.2.2.18Da | HS-DSCH FDD Secondary Serving Information..... | 663 | +| 9.2.2.18E | HS-DSCH FDD Information Response..... | 665 | +| 9.2.2.18EA | HS-DSCH FDD Secondary Serving Information Response..... | 665 | +| 9.2.2.18EB | HS-DSCH FDD Secondary Serving Information To Modify..... | 666 | +| 9.2.2.18EC | HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised..... | 668 | +| 9.2.2.18Ea | HS-DSCH FDD Update Information..... | 669 | + +| | | | +|-------------|-----------------------------------------------------------------|-----| +| 9.2.2.18Eaa | HS-DSCH FDD Secondary Serving Update Information..... | 670 | +| 9.2.2.18Eb | HS-DSCH Serving Cell Change Information..... | 670 | +| 9.2.2.18Ec | HS-DSCH Serving Cell Change Information Response..... | 671 | +| 9.2.2.18Eca | HS-DSCH Secondary Serving Cell Change Information Response..... | 671 | +| 9.2.2.18Ed | E-DCH Serving Cell Change Information Response..... | 671 | +| 9.2.2.18Ee | HS-DSCH TB Size Table Indicator..... | 672 | +| 9.2.2.18F | HS-PDSCH FDD Code Information..... | 672 | +| 9.2.2.18G | HS-SCCH FDD Code Information..... | 672 | +| 9.2.2.18H | HS-SCCH ID..... | 673 | +| 9.2.2.18I | HS-SCCH Power Offset..... | 673 | +| 9.2.2.18K | Initial DL DPCH Timing Adjustment Allowed..... | 673 | +| 9.2.2.19 | Max Adjustment Period..... | 673 | +| 9.2.2.20 | Max Adjustment Step..... | 673 | +| 9.2.2.20A | Max Number Of PCPCHs..... | 674 | +| 9.2.2.20B | Max Number Of UL E-DPDCHs..... | 674 | +| 9.2.2.20C | Maximum Set of E-DPDCHs..... | 674 | +| 9.2.2.20D | Maximum Number Of Retransmissions For E-DCH..... | 674 | +| 9.2.2.20E | MAC-es Guaranteed Bit Rate..... | 674 | +| 9.2.2.20F | MAC-e Reset Indicator..... | 674 | +| 9.2.2.21 | Maximum Number Of UL DPDCHs..... | 674 | +| 9.2.2.21a | Maximum Target Received Total Wide Band Power..... | 674 | +| 9.2.2.21b | Target Non-serving E-DCH to Total E-DCH Power Ratio..... | 675 | +| 9.2.2.21A | Maximum PDSCH Power..... | 675 | +| 9.2.2.21B | CQI Feedback Cycle k..... | 675 | +| 9.2.2.21C | Measurement Power Offset..... | 675 | +| 9.2.2.21D | MICH Mode..... | 675 | +| 9.2.2.22 | Minimum UL Channelisation Code Length..... | 675 | +| 9.2.2.22a | Min UL Channelisation Code Length For E-DCH FDD..... | 676 | +| 9.2.2.23 | Multiplexing Position..... | 676 | +| 9.2.2.23a | NACK Power Offset..... | 676 | +| 9.2.2.23A | N_EOT..... | 676 | +| 9.2.2.23B | NF_max..... | 676 | +| 9.2.2.23C | N_Start_Message..... | 676 | +| 9.2.2.23D | Number Of Reported Cell Portions..... | 676 | +| 9.2.2.24 | Pattern Duration (PD)..... | 676 | +| 9.2.2.24A | PCP Length..... | 676 | +| 9.2.2.25 | PDSCH Code Mapping..... | 676 | +| 9.2.2.26 | PICH Mode..... | 677 | +| 9.2.2.27 | Power Adjustment Type..... | 677 | +| 9.2.2.28 | Power Control Mode..... | 677 | +| 9.2.2.29 | Power Offset..... | 677 | +| 9.2.2.29A | Power_Raise_Limit..... | 677 | +| 9.2.2.30 | Power Resume Mode..... | 677 | +| 9.2.2.31 | Preamble Signatures..... | 678 | +| 9.2.2.32 | Preamble Threshold..... | 678 | +| 9.2.2.33 | Primary CPICH Power..... | 678 | +| 9.2.2.33A | Primary CPICH Usage For Channel Estimation..... | 678 | +| 9.2.2.34 | Primary Scrambling Code..... | 678 | +| 9.2.2.35 | Propagation Delay..... | 679 | +| 9.2.2.35A | Extended Propagation Delay..... | 679 | +| 9.2.2.36 | QE-Selector..... | 679 | +| 9.2.2.36A | Qth Parameter..... | 679 | +| 9.2.2.37 | RACH Slot Format..... | 679 | +| 9.2.2.38 | RACH Sub Channel Numbers..... | 680 | +| 9.2.2.39 | RL Set ID..... | 680 | +| 9.2.2.39a | RL Specific E-DCH Information..... | 680 | +| 9.2.2.39A | Received Total Wide Band Power..... | 680 | +| 9.2.2.39B | Reference Received Total Wide Band Power..... | 681 | +| 9.2.2.39C | Reference Received Total Wide Band Power Reporting..... | 681 | +| 9.2.2.39D | Reference Received Total Wide Band Power Support Indicator..... | 681 | +| 9.2.2.40 | S-Field Length..... | 681 | + +| | | | +|-----------|-----------------------------------------------------------------------|-----| +| 9.2.2.40A | Scheduling Information..... | 681 | +| 9.2.2.41 | Scrambling Code Change..... | 681 | +| 9.2.2.42 | Scrambling Code Number..... | 682 | +| 9.2.2.43 | Secondary CCPCH Slot Format..... | 682 | +| 9.2.2.43A | Secondary CPICH Information Change..... | 682 | +| 9.2.2.44 | SSDT Cell Identity..... | 682 | +| 9.2.2.44A | SSDT Cell Identity For EDSCHPC..... | 682 | +| 9.2.2.45 | SSDT Cell ID Length..... | 682 | +| 9.2.2.46 | SSDT Support Indicator..... | 682 | +| 9.2.2.47 | SSDT Indication..... | 682 | +| 9.2.2.48 | STTD Indicator..... | 683 | +| 9.2.2.48A | Synchronisation Indicator..... | 683 | +| 9.2.2.48B | Serving E-DCH RL..... | 683 | +| 9.2.2.49 | T Cell..... | 683 | +| 9.2.2.49A | TFCI2 Bearer Information Response..... | 683 | +| 9.2.2.50 | TFCI Signalling Mode..... | 683 | +| 9.2.2.51 | TGD..... | 684 | +| 9.2.2.52 | TGL..... | 684 | +| 9.2.2.53 | Transmit Diversity Indicator..... | 684 | +| 9.2.2.53A | Transmission Gap Pattern Sequence Information..... | 684 | +| 9.2.2.53B | Transmission Gap Pattern Sequence Code Information..... | 686 | +| 9.2.2.54 | UL/DL compressed mode selection..... | 686 | +| 9.2.2.55 | UL delta SIR..... | 687 | +| 9.2.2.56 | UL delta SIR after..... | 687 | +| 9.2.2.57 | UL DPCCH Slot Format..... | 687 | +| 9.2.2.58 | UL SIR..... | 687 | +| 9.2.2.59 | UL Scrambling Code..... | 687 | +| 9.2.2.60 | UL Capacity Credit..... | 687 | +| 9.2.2.61 | UL DPDCH Indicator For E-DCH Operation..... | 687 | +| 9.2.2.62 | Fast Reconfiguration Mode..... | 687 | +| 9.2.2.63 | Fast Reconfiguration Permission..... | 688 | +| 9.2.2.64 | Continuous Packet Connectivity DTX-DRX Capability..... | 688 | +| 9.2.2.65 | Continuous Packet Connectivity HS-SCCH less Capability..... | 688 | +| 9.2.2.66 | Continuous Packet Connectivity DTX-DRX Information..... | 688 | +| 9.2.2.67 | Continuous Packet Connectivity DTX-DRX Information To Modify..... | 690 | +| 9.2.2.68 | Continuous Packet Connectivity HS-SCCH less Information..... | 692 | +| 9.2.2.69 | Continuous Packet Connectivity HS-SCCH less Information Response..... | 692 | +| 9.2.2.69A | Continuous Packet Connectivity HS-SCCH less Deactivate Indicator..... | 693 | +| 9.2.2.70 | MIMO Capability..... | 693 | +| 9.2.2.71 | MIMO Activation Indicator..... | 693 | +| 9.2.2.72 | MIMO Mode Indicator..... | 693 | +| 9.2.2.73 | MIMO Pilot Configuration..... | 693 | +| 9.2.2.74 | SixtyfourQAM DL Capability..... | 693 | +| 9.2.2.74A | Sixtyfour QAM Usage Allowed Indicator..... | 693 | +| 9.2.2.74B | SixtyfourQAM DL Usage Indicator..... | 694 | +| 9.2.2.75 | HS-DSCH Common System Information..... | 694 | +| 9.2.2.76 | HS-DSCH Paging System Information..... | 696 | +| 9.2.2.77 | HS-DSCH Common System Information Response..... | 696 | +| 9.2.2.78 | HS-DSCH Paging System Information Response..... | 697 | +| 9.2.2.79 | Common MAC Flow ID..... | 697 | +| 9.2.2.80 | Paging MAC Flow ID..... | 697 | +| 9.2.2.81 | HSDPA Associated PICH Information..... | 698 | +| 9.2.2.82 | FACH Measurement Occasion Cycle Length Coefficient..... | 698 | +| 9.2.2.83 | Priority Queue Information for Enhanced FACH/PCH..... | 698 | +| 9.2.2.84 | RACH Measurement Result..... | 698 | +| 9.2.2.85 | BCCH Specific HS-DSCH RNTI Information..... | 698 | +| 9.2.2.86 | Enhanced FACH Capability..... | 698 | +| 9.2.2.87 | Enhanced PCH Capability..... | 698 | +| 9.2.2.88 | SixteenQAM UL Capability..... | 699 | +| 9.2.2.88A | SixteenQAM UL Operation Indicator..... | 699 | +| 9.2.2.88B | E-TFCI Boost Information..... | 699 | + +| | | | +|-----------|----------------------------------------------------------------|-----| +| 9.2.2.88C | SixtyfourQAM UL Operation Indicator..... | 699 | +| 9.2.2.89 | SixteenQAM UL Information..... | 699 | +| 9.2.2.90 | SixteenQAM UL Information To Modify..... | 699 | +| 9.2.2.91 | Modulation Power Offset..... | 699 | +| 9.2.2.92 | Extended Secondary CCPCH Slot Format..... | 700 | +| 9.2.2.93 | F-DPCH Slot Format..... | 700 | +| 9.2.2.94 | F-DPCH Slot Format Capability..... | 700 | +| 9.2.2.95 | Max UE DTX Cycle..... | 700 | +| 9.2.2.96 | MIMO N/M Ratio..... | 701 | +| 9.2.2.97 | Common MAC Flows To Delete..... | 701 | +| 9.2.2.98 | Paging MAC Flows To Delete..... | 701 | +| 9.2.2.99 | MAC-ehs Reset Timer..... | 701 | +| 9.2.2.100 | E-AGCH Table Choice..... | 701 | +| 9.2.2.101 | Common E-DCH Capability..... | 702 | +| 9.2.2.102 | E-AI Capability..... | 702 | +| 9.2.2.103 | Common E-DCH System Information..... | 702 | +| 9.2.2.104 | Common E-DCH System Information Response..... | 707 | +| 9.2.2.105 | Common E-DCH MAC-d Flow Specific Information..... | 708 | +| 9.2.2.106 | Maximum TB Size..... | 709 | +| 9.2.2.107 | Enhanced UE DRX Capability..... | 709 | +| 9.2.2.108 | Enhanced UE DRX Information..... | 710 | +| 9.2.2.109 | E-DPCCH Power Boosting Capability..... | 710 | +| 9.2.2.110 | SixtyfourQAM DL and MIMO Combined Capability..... | 710 | +| 9.2.2.111 | HS-DSCH Preconfiguration Info..... | 710 | +| 9.2.2.112 | HS-DSCH Preconfiguration Setup..... | 712 | +| 9.2.2.113 | Multi Cell Capability Info..... | 715 | +| 9.2.2.114 | Minimum Reduced E-DPDCH Gain Factor..... | 715 | +| 9.2.2.115 | IMB Parameters..... | 716 | +| 9.2.2.116 | Common E-DCH HS-DPCCH Capability..... | 716 | +| 9.2.2.117 | UE Support Indicator Extension..... | 716 | +| 9.2.2.118 | MIMO Power Offset For S-CPICH Capability..... | 717 | +| 9.2.2.119 | Power Offset For Secondary CPICH for MIMO..... | 717 | +| 9.2.2.120 | MIMO Pilot Configuration Extension..... | 718 | +| 9.2.2.121 | TX Diversity on DL Control Channels by MIMO UE Capability..... | 718 | +| 9.2.2.122 | Single Stream MIMO Capability..... | 718 | +| 9.2.2.123 | Single Stream MIMO Activation Indicator..... | 718 | +| 9.2.2.124 | Single Stream MIMO Mode Indicator..... | 718 | +| 9.2.2.125 | Dual Band Capability Info..... | 718 | +| 9.2.2.126 | Void..... | 719 | +| 9.2.2.127 | HS-DSCH MAC-ehs Format..... | 719 | +| 9.2.2.128 | Activation Information..... | 719 | +| 9.2.2.129 | Cell Capability Container..... | 720 | +| 9.2.2.130 | Multicell E-DCH Transport Bearer Mode..... | 724 | +| 9.2.2.131 | Additional E-DCH FDD Setup Information..... | 725 | +| 9.2.2.132 | Additional E-DCH RL Specific Information To Setup..... | 725 | +| 9.2.2.133 | Additional E-DCH RL Specific Information To Add..... | 726 | +| 9.2.2.134 | Additional E-DCH RL Specific Information To Modify..... | 726 | +| 9.2.2.135 | Additional E-DCH FDD Information Response..... | 727 | +| 9.2.2.136 | Additional E-DCH Configuration Change Information..... | 728 | +| 9.2.2.137 | Additional E-DCH FDD Information..... | 729 | +| 9.2.2.138 | Additional E-DCH FDD Update Information..... | 730 | +| 9.2.2.139 | E-RNTI List..... | 730 | +| 9.2.2.140 | Multicell E-DCH Information..... | 730 | +| 9.2.2.141 | Additional Modified E-DCH FDD Information Response..... | 731 | +| 9.2.2.142 | Multicell E-DCH RL Specific Information..... | 731 | +| 9.2.2.143 | Precoding Weight Set Restriction..... | 731 | +| 9.2.2.144 | Non-Serving RL Preconfiguration Setup..... | 732 | +| 9.2.2.145 | Non-Serving RL Preconfiguration Info..... | 732 | +| 9.2.2.146 | Void..... | 734 | +| 9.2.2.147 | Usefulness of Battery Optimization..... | 734 | +| 9.2.2.148 | Common HS-DSCH RNTI List..... | 734 | + +| | | | +|-----------|------------------------------------------------------------------------|-----| +| 9.2.2.149 | Puncturing Handling in First Rate Matching Stage..... | 734 | +| 9.2.2.150 | Support of Dynamic DTXDRX Related HS-SCCH Order..... | 734 | +| 9.2.2.151 | UL CLTD Information Reconf..... | 734 | +| 9.2.2.152 | UL CLTD Information..... | 735 | +| 9.2.2.153 | UL CLTD Information To Modify..... | 735 | +| 9.2.2.154 | UL CLTD Information Removal..... | 735 | +| 9.2.2.155 | UL CLTD State Update Information..... | 736 | +| 9.2.2.156 | F-TPICH Slot Format..... | 736 | +| 9.2.2.157 | F-TPICH Offset..... | 736 | +| 9.2.2.158 | S-DPCCH Power Offset Information..... | 736 | +| 9.2.2.159 | UL CLTD Activation Information..... | 736 | +| 9.2.2.160 | F-TPICH Information..... | 737 | +| 9.2.2.161 | F-TPICH Information To Modify..... | 737 | +| 9.2.2.162 | F-TPICH Information Removal..... | 737 | +| 9.2.2.163 | F-TPICH Information Reconf..... | 737 | +| 9.2.2.164 | MIMO with four transmit antennas Activation Indicator..... | 738 | +| 9.2.2.165 | MIMO with four transmit antennas Pilot Configuration..... | 738 | +| 9.2.2.166 | MIMO with four transmit antennas Mode Indicator..... | 738 | +| 9.2.2.167 | Dual Stream MIMO with four transmit antennas Activation Indicator..... | 738 | +| 9.2.2.168 | Dual Stream MIMO with four transmit antennas Mode Indicator..... | 738 | +| 9.2.2.169 | Multiflow Reconfiguration..... | 739 | +| 9.2.2.170 | Multiflow Information..... | 739 | +| 9.2.2.171 | Multiflow Information To Modify..... | 739 | +| 9.2.2.172 | Multiflow Stop..... | 740 | +| 9.2.2.173 | Multiflow Role..... | 740 | +| 9.2.2.174 | Multiflow MIMO..... | 740 | +| 9.2.2.175 | Multiflow Timing..... | 740 | +| 9.2.2.176 | UL MIMO Reconfiguration..... | 741 | +| 9.2.2.177 | UL MIMO Information..... | 741 | +| 9.2.2.178 | UL MIMO Information To Modify..... | 742 | +| 9.2.2.179 | UL MIMO Removal..... | 742 | +| 9.2.2.180 | UL MIMO DL Control Channel Information..... | 742 | +| 9.2.2.181 | E-ROCH Power Offset..... | 742 | +| 9.2.2.182 | S-E-DPCCH Power Offset..... | 743 | +| 9.2.2.183 | Inter-stream Interference Compensation Index..... | 743 | +| 9.2.2.184 | Secondary Transport Block E-HICH Release Indicator..... | 743 | +| 9.2.2.185 | Further Enhanced UE DRX Information..... | 743 | +| 9.2.2.186 | Common E-DCH Preamble Control Information extension list..... | 744 | +| 9.2.2.187 | Common E-DCH Preamble Control Information extension..... | 745 | +| 9.2.2.188 | Common E-DCH AICH Information..... | 745 | +| 9.2.2.189 | Common E-RGCH Info..... | 745 | +| 9.2.2.190 | Common E-DCH HS-DPCCH Information for Concurrent TTI..... | 745 | +| 9.2.2.191 | Common E-DCH system info parameters for Concurrent TTI..... | 746 | +| 9.2.2.192 | Precoder weight set restriction..... | 746 | +| 9.2.2.193 | Multiflow Repetition Factors..... | 746 | +| 9.2.2.194 | E-DCH Decoupling Indication..... | 747 | +| 9.2.2.195 | DCH Enhancements Information Reconf..... | 747 | +| 9.2.2.196 | DCH Enhancements Information..... | 747 | +| 9.2.2.197 | DCH Enhancements Information to Modify..... | 748 | +| 9.2.2.198 | DCH Enhancements Information Removal..... | 748 | +| 9.2.2.199 | Gain Factors 10ms Mode..... | 749 | +| 9.2.2.200 | Extended E-DPCCH Power Offset..... | 749 | +| 9.2.2.201 | Radio Links without DPCH/F-DPCH Indication..... | 749 | +| 9.2.2.202 | UL DPCCH2 Reconfiguration..... | 750 | +| 9.2.2.203 | UL DPCCH2 Information..... | 750 | +| 9.2.2.204 | UL DPCCH2 Information To Modify..... | 750 | +| 9.2.2.205 | UL DPCCH2 Information Removal..... | 750 | +| 9.2.2.206 | CQI Feedback Cycle2 k..... | 751 | +| 9.2.2.207 | UE Measurement Forwarding..... | 751 | +| 9.2.2.208 | UE Measurement Value..... | 751 | +| 9.2.2.209 | TTI Update Indication..... | 751 | + +| | | | +|------------|---------------------------------------------------------|-----| +| 9.2.2.2.10 | Activation Delay..... | 751 | +| 9.2.2.2.11 | Fast TTI switching Mode Supported..... | 752 | +| 9.2.2.2.12 | Fast TTI switching Mode Requested Synchronized..... | 752 | +| 9.2.2.2.13 | Fast TTI switching Mode Requested UnSynchronized..... | 752 | +| 9.2.2.2.14 | Downlink TPC enhancements Information..... | 752 | +| 9.2.2.2.15 | Downlink TPC enhancements Reconf..... | 752 | +| 9.2.2.2.16 | Downlink TPC enhancements Information Removal..... | 753 | +| 9.2.2.2.17 | TPC slot position..... | 753 | +| 9.2.2.2.18 | E-RNTI Set..... | 753 | +| 9.2.2.2.19 | Dual Cell E-DCH Operation Enhancements Information..... | 754 | +| 9.2.2.2.20 | HS-SCCH DRX Information..... | 754 | +| 9.2.3 | TDD specific Parameters..... | 754 | +| 9.2.3.1 | Block STTD Indicator..... | 754 | +| 9.2.3.2 | Burst Type..... | 754 | +| 9.2.3.3 | CCTrCH ID..... | 755 | +| 9.2.3.4 | Cell Parameter ID..... | 755 | +| 9.2.3.4A | Constant Value..... | 755 | +| 9.2.3.4B | DL Timeslot ISCP..... | 755 | +| 9.2.3.4C | DCH TDD Information..... | 755 | +| 9.2.3.4D | DCHs TDD To Modify..... | 756 | +| 9.2.3.4E | DL Timeslot Information..... | 757 | +| 9.2.3.4F | DL Time Slot ISCP Info..... | 757 | +| 9.2.3.4G | Cell Sync Burst Code..... | 758 | +| 9.2.3.4H | Cell Sync Burst Code Shift..... | 758 | +| 9.2.3.4I | CSB Measurement ID..... | 758 | +| 9.2.3.4J | Cell Sync Burst Repetition Period..... | 758 | +| 9.2.3.4K | Cell Sync Burst SIR..... | 758 | +| 9.2.3.4L | Cell Sync Burst Timing..... | 759 | +| 9.2.3.4La | Cell Sync Burst Timing LCR..... | 759 | +| 9.2.3.4M | Cell Sync Burst Timing Threshold..... | 759 | +| 9.2.3.4N | CSB Transmission ID..... | 759 | +| 9.2.3.4O | DL Timeslot Information LCR..... | 759 | +| 9.2.3.4P | DL Time Slot ISCP Info LCR..... | 760 | +| 9.2.3.4Q | UpPCH Position LCR..... | 760 | +| 9.2.3.5 | DPCH ID..... | 760 | +| 9.2.3.5a | DSCH ID..... | 761 | +| 9.2.3.5b | DSCH Information Response..... | 761 | +| 9.2.3.5A | DSCH TDD Information..... | 761 | +| 9.2.3.5B | DwPCH Power..... | 762 | +| 9.2.3.5C | Frame Adjustment Value..... | 762 | +| 9.2.3.5D | IPDL TDD Parameters..... | 762 | +| 9.2.3.5E | Max FPACH Power..... | 762 | +| 9.2.3.5F | HS-DSCH TDD Information..... | 762 | +| 9.2.3.5G | HS-DSCH TDD Information Response..... | 764 | +| 9.2.3.5GA | HS-DSCH TDD Update Information..... | 767 | +| 9.2.3.5Ga | HS-SCCH ID..... | 767 | +| 9.2.3.5Gb | HS-SICH ID..... | 767 | +| 9.2.3.5Gc | 1.28 Mcps TDD Uplink Physical Channel Capability..... | 767 | +| 9.2.3.5H | IPDL TDD Parameters LCR..... | 768 | +| 9.2.3.5I | TSN-Length..... | 768 | +| 9.2.3.5J | Extended HS-SCCH ID..... | 768 | +| 9.2.3.5K | Extended HS-SICH ID..... | 768 | +| 9.2.3.6 | Max PRACH Midamble Shift..... | 768 | +| 9.2.3.7 | Midamble Shift And Burst Type..... | 769 | +| 9.2.3.7A | Midamble Shift LCR..... | 769 | +| 9.2.3.7Aa | Notification Indicator Length..... | 770 | +| 9.2.3.7B | Number Of Cycles Per SFN Period..... | 770 | +| 9.2.3.7C | Number Of Repetitions Per Cycle Period..... | 770 | +| 9.2.3.7D | Number Of Subcycles Per Cycle Period..... | 770 | +| 9.2.3.8 | Paging Indicator Length..... | 771 | +| 9.2.3.9 | PCCPCH Power..... | 771 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 9.2.3.10 | PDSCH ID..... | 771 | +| 9.2.3.11 | PDSCH Set ID..... | 771 | +| 9.2.3.11A | Primary CCPCH RSCP..... | 771 | +| 9.2.3.11B | Primary CCPCH RSCP Delta..... | 771 | +| 9.2.3.12 | PUSCH ID..... | 772 | +| 9.2.3.13 | PUSCH Set ID..... | 772 | +| 9.2.3.14 | PRACH Midamble..... | 772 | +| 9.2.3.14A | Reference Clock Availability..... | 772 | +| 9.2.3.14B | Reference SFN Offset..... | 772 | +| 9.2.3.15 | Repetition Length..... | 773 | +| 9.2.3.16 | Repetition Period..... | 773 | +| 9.2.3.17 | SCH Time Slot..... | 773 | +| 9.2.3.18 | Sync Case..... | 773 | +| 9.2.3.18A | Special Burst Scheduling..... | 774 | +| 9.2.3.18B | SYNC_DL Code ID..... | 774 | +| 9.2.3.18C | Sync Frame Number..... | 774 | +| 9.2.3.18D | Synchronisation Report Characteristics..... | 774 | +| 9.2.3.18E | Synchronisation Report Type..... | 775 | +| 9.2.3.18F | TDD ACK NACK Power Offset..... | 776 | +| 9.2.3.19 | TDD Channelisation Code..... | 776 | +| 9.2.3.19a | TDD Channelisation Code LCR..... | 776 | +| 9.2.3.19A | TDD DPCH Offset..... | 776 | +| 9.2.3.19B | TDD DL Code Information..... | 777 | +| 9.2.3.19C | TDD DL Code Information LCR..... | 777 | +| 9.2.3.19D | TDD DL DPCH Time Slot Format LCR..... | 777 | +| 9.2.3.20 | TDD Physical Channel Offset..... | 778 | +| 9.2.3.21 | TDD TPC DL Step Size..... | 778 | +| 9.2.3.21a | TDD TPC UL Step Size..... | 778 | +| 9.2.3.21A | TDD UL Code Information..... | 778 | +| 9.2.3.21B | TDD UL Code Information LCR..... | 779 | +| 9.2.3.21C | TDD UL DPCH Time Slot Format LCR..... | 779 | +| 9.2.3.22 | TFCI Coding..... | 779 | +| 9.2.3.22a | Timing Adjustment Value..... | 779 | +| 9.2.3.22b | Timing Adjustment Value LCR..... | 780 | +| 9.2.3.22A | Timing Advance Applied..... | 780 | +| 9.2.3.23 | Time Slot..... | 780 | +| 9.2.3.24 | Time Slot Direction..... | 780 | +| 9.2.3.24A | Time Slot LCR..... | 780 | +| 9.2.3.24B | Time Slot LCR Extension..... | 781 | +| 9.2.3.25 | Time Slot Status..... | 781 | +| 9.2.3.26 | Transmission Diversity Applied..... | 781 | +| 9.2.3.26A | UL Timeslot ISCP..... | 781 | +| 9.2.3.26B | UL PhysCH SF Variation..... | 781 | +| 9.2.3.26C | UL Timeslot Information..... | 781 | +| 9.2.3.26D | UL Time Slot ISCP Info..... | 782 | +| 9.2.3.26E | UL Timeslot Information LCR..... | 782 | +| 9.2.3.26F | UL Time Slot ISCP Info LCR..... | 782 | +| 9.2.3.26G | Uplink Synchronisation Frequency..... | 783 | +| 9.2.3.26H | Uplink Synchronisation Step Size..... | 783 | +| 9.2.3.27 | USCH ID..... | 783 | +| 9.2.3.28 | USCH Information..... | 783 | +| 9.2.3.29 | USCH Information Response..... | 784 | +| 9.2.3.30 | SCTD Indicator..... | 784 | +| 9.2.3.31 | PLCCH Information..... | 784 | +| 9.2.3.32 | PLCCH Sequence Number..... | 785 | +| 9.2.3.33 | Common Physical Channel ID 7.68Mcps..... | 785 | +| 9.2.3.34 | TDD Channelisation Code 7.68Mcps..... | 785 | +| 9.2.3.35 | Midamble Shift And Burst Type 7.68Mcps..... | 785 | +| 9.2.3.36 | Common Physical Channel Status Information 7.68Mcps..... | 786 | +| 9.2.3.37 | Neighbouring TDD Cell Measurement Information 7.68Mcps..... | 786 | +| 9.2.3.38 | UL Timeslot Information 7.68Mcps TDD..... | 786 | + +| | | | +|-----------|----------------------------------------------------------------------|-----| +| 9.2.3.39 | DL Timeslot Information 7.68Mcps TDD..... | 787 | +| 9.2.3.40 | TDD UL Code Information 7.68Mcps TDD..... | 787 | +| 9.2.3.41 | TDD DL Code Information 7.68Mcps TDD..... | 787 | +| 9.2.3.42 | DPCH ID 7.68Mcps..... | 788 | +| 9.2.3.43 | PDSCH ID 7.68Mcps..... | 788 | +| 9.2.3.44 | Max E-RUCCH Midamble Shift..... | 788 | +| 9.2.3.45 | E-PUCH Information..... | 788 | +| 9.2.3.45a | E-PUCH Information LCR..... | 789 | +| 9.2.3.46 | E-TFCS Information TDD..... | 790 | +| 9.2.3.47 | E-DCH MAC-d Flows Information TDD..... | 791 | +| 9.2.3.48 | E-DCH Non-scheduled Grant Information TDD..... | 791 | +| 9.2.3.48a | E-DCH Non-scheduled Grant Information LCR TDD..... | 792 | +| 9.2.3.49 | E-DCH TDD Information..... | 793 | +| 9.2.3.49a | E-DCH TDD Information LCR..... | 794 | +| 9.2.3.50 | E-DCH TDD Information Response..... | 796 | +| 9.2.3.51 | E-AGCH ID TDD..... | 796 | +| 9.2.3.51a | E-HICH ID TDD..... | 797 | +| 9.2.3.51b | Extended E-HICH ID TDD..... | 797 | +| 9.2.3.52 | E-DCH TDD Information to Modify..... | 797 | +| 9.2.3.53 | E-DCH Grant Type TDD..... | 798 | +| 9.2.3.54 | Timeslot Resource Related Information..... | 799 | +| 9.2.3.54a | Timeslot Resource Related Information LCR..... | 799 | +| 9.2.3.55 | Power Resource Related Information..... | 799 | +| 9.2.3.56 | E-PUCH Offset..... | 799 | +| 9.2.3.57 | E-DCH TDD Maximum Bitrate..... | 799 | +| 9.2.3.58 | LTGI Presence..... | 799 | +| 9.2.3.59 | E-HICH Time Offset..... | 800 | +| 9.2.3.59a | E-HICH Time Offset LCR..... | 800 | +| 9.2.3.60 | E-DCH TDD Capacity Consumption Law..... | 800 | +| 9.2.3.61 | E-DCH HARQ Power Offset TDD..... | 800 | +| 9.2.3.61a | E-DCH MAC-d Flow Retransmission Timer..... | 800 | +| 9.2.3.62 | SNPL Reporting Type..... | 801 | +| 9.2.3.63 | Maximum Generated Received Total Wide Band Power in Other Cells..... | 801 | +| 9.2.3.64 | E-DCH Non-scheduled Grant Information 7.68Mcps TDD..... | 801 | +| 9.2.3.65 | E-DCH TDD Information 7.68Mcps..... | 801 | +| 9.2.3.66 | E-DCH TDD Maximum Bitrate 7.68Mcps..... | 802 | +| 9.2.3.67 | E-DCH Physical Layer Category LCR..... | 802 | +| 9.2.3.67A | Extended E-DCH Physical Layer Category LCR..... | 802 | +| 9.2.3.67B | Multi-Carrier E-DCH Physical Layer Category LCR..... | 802 | +| 9.2.3.68 | E-HICH Type..... | 802 | +| 9.2.3.69 | Maximum Target Received Total Wide Band Power LCR..... | 803 | +| 9.2.3.70 | MBSFN Only Mode Indicator..... | 803 | +| 9.2.3.71 | MBSFN Only Mode Capability..... | 803 | +| 9.2.3.72 | HS-DSCH Common System Information LCR..... | 803 | +| 9.2.3.73 | HS-DSCH Paging System Information LCR..... | 805 | +| 9.2.3.74 | HS-DSCH Common System Information Response LCR..... | 806 | +| 9.2.3.75 | HS-DSCH Paging System Information Response LCR..... | 807 | +| 9.2.3.76 | Common MAC Flow ID LCR..... | 808 | +| 9.2.3.77 | HSDPA Associated PICH Information LCR..... | 808 | +| 9.2.3.78 | Common MAC Flows To Delete LCR..... | 809 | +| 9.2.3.79 | Common E-DCH System Information LCR..... | 809 | +| 9.2.3.80 | Common E-DCH System Information Response LCR..... | 811 | +| 9.2.3.81 | Common E-DCH MAC-d Flow Specific Information LCR..... | 811 | +| 9.2.3.82 | Enhanced UE DRX Information LCR..... | 812 | +| 9.2.3.83 | Common E-PUCH Information LCR..... | 812 | +| 9.2.3.84 | Common E-RNTI Information LCR..... | 813 | +| 9.2.3.85 | Paging MAC Flows To Delete LCR..... | 814 | +| 9.2.3.86 | Common E-DCH MAC-d Flows To Delete LCR..... | 814 | +| 9.2.3.87 | Common E-DCH MAC-d Flow ID LCR..... | 814 | +| 9.2.3.88 | HS-SCCH ID LCR..... | 815 | +| 9.2.3.89 | BCCH Specific HS-DSCH RNTI Information LCR..... | 815 | + +| | | | +|-----------|-------------------------------------------------------------------|------| +| 9.2.3.90 | MAC-es Maximum Bit Rate LCR..... | 815 | +| 9.2.3.91 | Semi-Persistent scheduling Capability LCR..... | 815 | +| 9.2.3.92 | Continuous Packet Connectivity DRX Capability LCR..... | 815 | +| 9.2.3.93 | Continuous Packet Connectivity DRX Information LCR..... | 816 | +| 9.2.3.94 | Continuous Packet Connectivity DRX Information To Modify LCR..... | 816 | +| 9.2.3.95 | Continuous Packet Connectivity DRX Information Response LCR..... | 817 | +| 9.2.3.96 | HS-DSCH Semi-Persistent scheduling Information LCR..... | 818 | +| 9.2.3.96a | HS-DSCH Semi-Persistent scheduling Information to modify LCR..... | 819 | +| 9.2.3.97 | E-DCH Semi-Persistent scheduling Information LCR..... | 821 | +| 9.2.3.97a | E-DCH Semi-Persistent scheduling Information to modify LCR..... | 822 | +| 9.2.3.98 | HS-DSCH Semi-Persistent scheduling Information Response LCR..... | 822 | +| 9.2.3.99 | E-DCH Semi-Persistent scheduling Information Response LCR..... | 824 | +| 9.2.3.100 | HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR..... | 825 | +| 9.2.3.101 | E-DCH Semi-Persistent scheduling Deactivate Indicator LCR..... | 825 | +| 9.2.3.102 | Idle Interval Information..... | 825 | +| 9.2.3.103 | HS-SICH Reference Signal Information..... | 826 | +| 9.2.3.104 | UE Selected MBMS Service Information..... | 827 | +| 9.2.3.105 | Best Cell Portions LCR..... | 827 | +| 9.2.3.106 | Cell Portion Capability LCR..... | 828 | +| 9.2.3.107 | Cell Portion LCR ID..... | 828 | +| 9.2.3.108 | Number Of Reported Cell Portions LCR..... | 828 | +| 9.2.3.109 | TS0 Capability LCR..... | 828 | +| 9.2.3.110 | UE TS0 Capability LCR..... | 828 | +| 9.2.3.111 | DCH Measurement Occasion Information..... | 829 | +| 9.2.3.112 | Multi-Carrier E-DCH Information LCR..... | 830 | +| 9.2.3.113 | Multi-Carrier E-DCH Transport Bearer Mode LCR..... | 830 | +| 9.2.3.114 | Multi-Carrier E-DCH Information Response LCR..... | 830 | +| 9.2.3.115 | Cell Capability Container TDD LCR..... | 831 | +| 9.2.3.116 | MU-MIMO Information..... | 832 | +| 9.2.3.117 | MU-MIMO Information To Reconfigure..... | 833 | +| 9.2.3.118 | MU-MIMO Information Response..... | 833 | +| 9.2.3.119 | MU-MIMO Capability Container..... | 834 | +| 9.2.3.120 | MU-MIMO Indicator..... | 834 | +| 9.2.3.121 | MU-MIMO Usage Indicator..... | 835 | +| 9.2.3.122 | Adaptive Special Burst Power Capability LCR..... | 835 | +| 9.2.3.123 | In Sync Indication Information LCR..... | 835 | +| 9.2.3.124 | AOA per Cell Portion LCR..... | 835 | +| 9.2.3.125 | UE RF Band Capability LCR..... | 836 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 837 | +| 9.3.0 | General..... | 837 | +| 9.3.1 | Usage of Private Message mechanism for non-standard use..... | 837 | +| 9.3.2 | Elementary Procedure Definitions..... | 837 | +| 9.3.3 | PDU Definitions..... | 856 | +| 9.3.4 | Information Elements Definitions..... | 1103 | +| 9.3.5 | Common Definitions..... | 1330 | +| 9.3.6 | Constant Definitions..... | 1331 | +| 9.3.7 | Container Definitions..... | 1357 | +| 9.4 | Message Transfer Syntax..... | 1362 | +| 9.5 | Timers..... | 1362 | +| 10 | Handling of Unknown, Unforeseen and Erroneous Protocol Data..... | 1362 | +| 10.1 | General..... | 1362 | +| 10.2 | Transfer Syntax Error..... | 1362 | +| 10.3 | Abstract Syntax Error..... | 1363 | +| 10.3.1 | General..... | 1363 | +| 10.3.2 | Criticality Information..... | 1363 | +| 10.3.3 | Presence Information..... | 1364 | +| 10.3.4 | Not comprehended IE/IE group..... | 1364 | +| 10.3.4.1 | Procedure ID..... | 1364 | +| 10.3.4.1A | Type of Message..... | 1364 | +| 10.3.4.2 | IEs Other Than the Procedure ID and Type of Message..... | 1364 | +| 10.3.5 | Missing IE or IE Group..... | 1366 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------|-------------| +| 10.3.6 | IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present. | 1367 | +| 10.4 | Logical Error..... | 1367 | +| 10.5 | Exceptions..... | 1368 | +| Annex A (normative): | Allocation and Pre-emption of Radio Links in the Node B..... | 1369 | +| A.1 | Deriving Allocation Information for a Radio Link..... | 1369 | +| A.1.1 | Establishment of a New Radio Link..... | 1369 | +| A.1.2 | Modification of an Existing Radio Link..... | 1369 | +| A.2 | Deriving Retention Information for a Radio Link..... | 1370 | +| A.3 | The Allocation/Retention Process..... | 1371 | +| A.4 | The Pre-emption Process..... | 1371 | +| Annex B (informative): | Measurement Reporting..... | 1372 | +| Annex C (informative): | Guidelines for Usage of the Criticality Diagnostics IE..... | 1376 | +| C.1 | EXAMPLE MESSAGE Layout..... | 1376 | +| C.2 | Example on a Received EXAMPLE MESSAGE..... | 1377 | +| C.3 | Content of Criticality Diagnostics..... | 1378 | +| C.3.1 | Example 1..... | 1378 | +| C.3.2 | Example 2..... | 1379 | +| C.3.3 | Example 3..... | 1380 | +| C.3.4 | Example 4..... | 1381 | +| C.3.5 | Example 5..... | 1382 | +| C.4 | ASN.1 of EXAMPLE MESSAGE..... | 1383 | +| Annex D (normative): | IB_SG_DATA Encoding..... | 1385 | +| D.1 | Overall Description..... | 1385 | +| D.2 | IB_SG_DATA Encoding Variant 1..... | 1385 | +| D.3 | IB_SG_DATA Encoding Variant 2..... | 1385 | +| Annex E (informative): | Reporting the status of resources used for frequency (1.28 Mcps TDD only)..... | 1386 | +| Annex F (informative): | Change History..... | 1387 | + +--- + +## Foreword + +This Technical Specification has been produced by the 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 this TS, 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 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document specifies the radio network layer signalling protocol called Node B Application Part (NBAP) specification to be used for Control Plane over Iub Interface. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.401: "UTRAN Overall Description". +- [2] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams". +- [3] CCITT Recommendation X.731 (1992-01): "Information Technology – Open Systems Interconnection – Systems Management: State Management function". +- [4] 3GPP TS 25.215: "Physical layer; Measurements (FDD)". +- [5] 3GPP TS 25.225: "Physical layer; Measurements (TDD)". +- [6] 3GPP TS 25.430: "UTRAN Iub General Aspect and Principle". +- [7] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [8] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [9] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [10] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [11] ITU-T Recommendation X.691, (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [12] ITU-T Recommendation X.680, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1):Specification of basic notation". +- [13] ITU-T Recommendation X.681, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [14] 3GPP TS 25.104: "UTRA (BS) FDD; Radio Transmission and Reception". +- [15] 3GPP TS 25.105: "UTRA (BS) TDD; Radio Transmission and Reception". +- [16] 3GPP TS 25.427: "UTRAN Iur/Iub Interface User Plane Protocol for DCH Data Stream". +- [17] 3GPP TS 25.402: "Synchronisation in UTRAN Stage2". +- [18] 3GPP TS 25.331: "RRC Protocol Specification". +- [19] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels[TDD]". + +- [20] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [21] 3GPP TS 25.224: "Physical Layer Procedures (TDD)". +- [22] 3GPP TS 25.133: "Requirements for support of Radio Resource management (FDD)". +- [23] 3GPP TS 25.123: "Requirements for support of Radio Resource management (TDD)". +- [24] 3GPP TS 25.435: "UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams". +- [25] 3GPP TS 25.302: "Services Provided by the Physical Layer". +- [26] 3GPP TR 25.921 (version.7.0.0): "Guidelines and Principles for Protocol Description and Error Handling". +- [27] ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interface". +- [28] RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)". +- [29] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [30] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [31] 3GPP TS 25.434: "UTRAN Iub Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams ". +- [32] 3GPP TS 25.321: "MAC protocol specification". +- [33] 3GPP TS 25.306: "UE Radio Access capabilities". +- [34] 3GPP TS 25.222: "Multiplexing and Channel Coding (TDD)". +- [35] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [36] IETF RFC 2475 (1998-12): "An Architecture for Differentiated Services". +- [37] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode". +- [38] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2". +- [39] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2. February 2014, European Union. +- [40] Void. +- [41] IETF RFC 3376 (2002-12): "Internet Group Management Protocol, Version 3". +- [42] IETF RFC 3810 (2004-06): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". +- [43] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [44] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, (2005-09-22). +- [45] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, (2008-03-31). +- [46] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [47] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, (2008-06-17). +- [48] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002. +- [49] 3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2" + +- [50] 3GPP TS 36.133: "Requirements for support of radio resource management". +- [51] BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 1.0)", December 2013. +- [52] 3GPP TS 25.300: "Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2". + +--- + +## 3 Definitions, Symbols and Abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**CRNC Communication Context:** The CRNC Communication Context contains the necessary information for the CRNC for communication with a specific UE. The CRNC Communication Context is identified by the CRNC Communication Context ID. + +**Elementary Procedure:** The NBAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CRNC and the Node B. + +An EP consists of an initiating message and possibly a response message. + +Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure). +- **Class 2:** Elementary Procedures without response. + +For **Class 1** EPs, the types of responses can be as follows: + +Successful + +- A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response. + +Unsuccessful + +- A signalling message explicitly indicates that the EP failed. + +**Class 2** EPs are considered always successful. + +**Node B Communication Context:** The Node B Communication Context contains the necessary information for the Node B for communication with a specific UE. The Node B Communication Context is created by the Radio Link Setup procedure and deleted by the Radio Link Deletion procedure when deleting the last Radio Link within the Node B Communication Context. The Node B Communication Context is identified by the Node B Communication Context ID. + +**Prepared Reconfiguration:** A Prepared Reconfiguration exists when the Synchronised Radio Link Reconfiguration Preparation procedure has been completed successfully. The Prepared Reconfiguration does not exist anymore only after either of the procedures Synchronised Radio Link Reconfiguration Commit or Synchronised Radio Link Reconfiguration Cancellation has been completed. In particular, the Prepared Reconfiguration still exists if the object (e.g. Radio Link) concerned by the Synchronised Radio Link Reconfiguration (e.g. in the case of an HS-DSCH Setup) is removed, but the Node B Communication Context still exists. + +### 3.2 Symbols + +Void. + +### 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|--------------| +| A-GPS | Assisted GPS | +|-------|--------------| + +| | | +|----------|----------------------------------------------------------------------------------------------| +| AICH | Acquisition Indicator Channel | +| ALCAP | Access Link Control Application Part | +| ASN.1 | Abstract Syntax Notation One | +| BCCH | Broadcast Control Channel | +| BDS | BeiDou Navigation Satellite System | +| CCPCH | Common Control Physical Channel | +| CFN | Connection Frame Number | +| CLTD | Closed Loop Transmit Diversity | +| CM | Compressed Mode | +| CPICH | Common Pilot Channel | +| CRNC | Controlling Radio Network Controller | +| DBDS | Differential BDS | +| DCH | Dedicated Channel | +| DGANSS | Differential GANSS | +| DGPS | Differential GPS | +| DL | Downlink | +| DPCCH | Dedicated Physical Control Channel | +| DPCH | Dedicated Physical Channel | +| DPDCH | Dedicated Physical Data Channel | +| DSCH | Downlink Shared Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced UL DCH | +| EGNOS | European Geostationary Navigation Overlay Service | +| E-HICH | E-DCH HARQ Acknowledgement Indicator Channel | +| E-PUCH | Enhanced Uplink Physical Channel (TDD only) | +| E-RNTI | E-DCH RNTI | +| E-RUCCH | E-DCH Random Access Uplink Control Channel (TDD only) | +| E-TFCI | E-DCH Transport Format Combination Indicator | +| E-UCCH | E-DCH Uplink Control Channel (TDD only) | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| F-DPCH | Fractional DPCH | +| FP | Frame Protocol | +| FPACH | Fast Physical Access Channel (TDD only) | +| F-TPICH | Fractional Transmitted Precoding Indicator Channel | +| GAGAN | GPS Aided Geo Augmented Navigation | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| HSDPA | High Speed Downlink Packet Access | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | High Speed Shared Control Channel | +| HS-SICH | High Speed Shared Information Channel | +| ICD | Interface Control Document | +| IMB | Integrated Mobile Broadcast | +| IP | Internet Protocol | +| IPDL | Idle Periods in the DownLink | +| ISCP | Interference Signal Code Power | +| L1 | Layer 1 | +| L2 | Layer 2 | +| MBMS | Multimedia Broadcast Multicast Service | +| MBSFN | MBMS over a Single Frequency Network | +| MFN | Multicast Frame Number | +| MIB | Master Information Block | +| MICH | MBMS Notification Indicator Channel | +| MIMO | Multiple Input Multiple Output | +| MSAS | Multi-functional Satellite Augmentation System | +| NAICS | Network Assisted Interference Cancellation and Suppression | +| NBAP | Node B Application Part | + +| | | +|---------|----------------------------------------------| +| NI | MBMS Notification Indicator | +| O&M | Operation and Maintenance | +| PCCPCH | Primary Common Control Physical Channel | +| PCH | Paging Channel | +| PDSCH | Physical Downlink Shared Channel | +| PICH | Paging Indication Channel | +| PLCCCH | Physical Layer Common Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| QZSS | Quasi-Zenith Satellite System | +| RACH | Random Access Channel | +| RL | Radio Link | +| RLS | Radio Link Set | +| RNC | Radio Network Controller | +| RRC | Radio Resource Control | +| SB | Scheduling Block | +| SBAS | Satellite Based Augmentation System | +| SCCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronisation Channel | +| SCTD | Space Code Transmit Diversity | +| S-DPCCH | Secondary Dedicated Physical Control Channel | +| SIB | System Information Block | +| SRNC | Serving Radio Network Controller | +| STTD | Space Time Transmit Diversity | +| TDD | Time Division Duplex | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TFCS | Transport Format Combination Set | +| TFS | Transport Format Set | +| TPC | Transmit Power Control | +| TSTD | Time Switched Transmit Diversity | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| USCH | Uplink Shared Channel | +| UTC | Universal Coordinated Time | +| UTRA | Universal Terrestrial Radio Access | +| UTRAN | Universal Terrestrial Radio Access Network | +| WAAS | Wide Area Augmentation System | + +--- + +## 4 General + +### 4.1 Procedure Specification Principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the Node B exactly and completely. The CRNC functional behaviour is left unspecified. The Reset procedure is an exception from this principle. + +The following specification principles have been applied for the procedure text in subclause 8: + +- The procedure text discriminates between: + +- 1) Functionality which "shall" be executed + +The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + +- 2) Functionality which "shall, if supported" be executed + +The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. + +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including *Criticality Diagnostics* IE, see section 10. For examples on how to use the *Criticality Diagnostics* IE, see Annex C. + +## 4.2 Forwards and Backwards Compatibility + +The forwards and backwards compatibility of the protocol is assured by a mechanism in which all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +- | | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD] | This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. | +| [TDD] | This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD. | +| [3.84Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. | +| [1.28Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. | +| [7.68Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. | +| [FDD - ...] | This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. | +| [TDD - ...] | This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. | +| [3.84Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. | +| [1.28Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [7.68Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. | +| [3.84Mcps TDD IMB - ...] | This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD IMB]" applies only to 3.84Mcps TDD IMB. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD IMB]" and the section following the heading applies only to 3.84Mcps TDD IMB. | +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Link Setup procedure. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Transport Format Set IE . | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)". | + +## 5 NBAP Services + +### 5.1 Parallel Transactions + +Unless explicitly indicated in the procedure description, at any instance in time one protocol peer shall have a maximum of one ongoing dedicated NBAP procedure related to a certain Node B Communication Context. + +## 6 Services Expected from Signalling Transport + +NBAP requires an assured in-sequence delivery service from the signalling bearer, and notification if the assured in-sequence delivery service is no longer available. + +## 7 Functions of NBAP + +The NBAP protocol provides the following functions: + +- Cell Configuration Management. This function gives the CRNC the possibility to manage the cell configuration information in a Node B. +- Common Transport Channel Management. This function gives the CRNC the possibility to manage the configuration of Common Transport Channels in a Node B. +- System Information Management. This function gives the CRNC the ability to manage the scheduling of System Information to be broadcast in a cell. +- Resource Event Management. This function gives the Node B the ability to inform the CRNC about the status of Node B resources. +- Configuration Alignment. This function gives the CRNC and the Node B the possibility to verify and enforce that both nodes have the same information on the configuration of the radio resources. +- Measurements on Common Resources. This function allows the CRNC to initiate measurements on common resources in the Node B. The function also allows the Node B to report the result of the measurements. + +- Radio Link Management. This function allows the CRNC to manage radio links using dedicated resources in a Node B. +- Radio Link Supervision. This function allows the CRNC to report failures and restorations of a Radio Link. +- Compressed Mode Control [FDD]. This function allows the CRNC to control the usage of compressed mode in a Node B. +- Measurements on Dedicated Resources. This function allows the CRNC to initiate measurements on dedicated resources in the Node B. The function also allows the Node B to report the result of the measurements. +- DL Power Drifting Correction [FDD]. This function allows the CRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links. +- Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined. +- Physical Shared Channel Management. This function allows the CRNC to manage physical resources in the Node B belonging to High Speed Downlink Shared Channels and High Speed Shared Control Channels [TDD - and High Speed Shared Indication Channels and Shared Channels (USCH/DSCH)]. +- DL Power Timeslot Correction [TDD]. This function enables the Node B to apply an individual offset to the transmission power in each timeslot according to the downlink interference level at the UE. +- Cell Synchronisation [1.28 Mcps TDD and 3.84 Mcps TDD]. This function allows the synchronisation of cells or Node Bs via the air interface. +- Information Exchange. This function allows the CRNC to initiate information provision from the Node B. The function also allows the Node B to report the requested information. +- Bearer Rearrangement. This function allows the Node B to indicate the need for bearer re-arrangement for a Node B Communication Context. The function also allows the CRNC to re-arrange bearers for a Node B Communication Context. +- MBMS Notification. This function allows the CRNC to send MBMS Notification indicators to the Node B to be broadcasted in a cell. +- UE Status Notification [FDD and 1.28 Mcps TDD]. This function allows the CRNC to update UE related information stored in the Node B. +- Exchanging information about the secondary UL frequency. This function allows the CRNC to transfer information about the secondary UL frequency to the Node B and the Node B to transfer information about the secondary UL frequency to SRNC in Dual-Cell E-DCH operation. + +The mapping between the above functions and NBAP elementary procedures is shown in the table below. + +**Table 1: Mapping between functions and NBAP elementary procedures** + +| Function | Elementary Procedure(s) | +|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Configuration Management | a) Cell Setup
b) Cell Reconfiguration
c) Cell Deletion | +| Common Transport Channel Management | a) Common Transport Channel Setup
b) Common Transport Channel Reconfiguration
c) Common Transport Channel Deletion | +| System Information Management | System Information Update | +| Resource Event Management | a) Block Resource
b) Unblock Resource
c) Resource Status Indication | +| Configuration Alignment | a) Audit Required
b) Audit
c) Reset | +| Measurements on Common Resources | a) Common Measurement Initiation
b) Common Measurement Reporting
c) Common Measurement Termination
d) Common Measurement Failure | +| Radio Link Management. | a) Radio Link Setup
b) Radio Link Addition
c) Radio Link Deletion
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation
h) Radio Link Pre-emption
i) Radio Link Activation
j) Radio Link Parameter Update | +| Radio Link Supervision. | a) Radio Link Failure
b) Radio Link Restoration | +| Compressed Mode Control [FDD] | a) Radio Link Setup
b) Radio Link Addition
c) Compressed Mode Command
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation | +| Measurements on Dedicated Resources | a) Dedicated Measurement Initiation
b) Dedicated Measurement Reporting
c) Dedicated Measurement Termination
d) Dedicated Measurement Failure | +| DL Power Drifting Correction [FDD] | Downlink Power Control | +| Reporting of General Error Situations | Error Indication | +| Physical Shared Channel Management | Physical Shared Channel Reconfiguration | +| DL Power Timeslot Correction [TDD] | Downlink Power Timeslot Control | +| Cell Synchronisation [1.28 Mcps TDD and 3.84 Mcps TDD] | a) Cell Synchronisation Initiation
b) Cell Synchronisation Reconfiguration
c) Cell Synchronisation Reporting
d) Cell Synchronisation Termination
e) Cell Synchronisation Failure
f) Cell Synchronisation Adjustment | +| Information Exchange | a) Information Exchange Initiation
b) Information Reporting
c) Information Exchange Termination
d) Information Exchange Failure | +| Bearer Re-arrangement | a) Bearer Re-arrangement Indication
b) Unsynchronised Radio Link Reconfiguration
c) Synchronised Radio Link Reconfiguration Preparation
d) Synchronised Radio Link Reconfiguration Commit
e) Synchronised Radio Link Reconfiguration Cancellation | +| MBMS Notification | a) MBMS Notification Update | +| UE Status Notification [FDD and 1.28 Mcps TDD] | a) UE Status Update
b) UE Status Update Confirmation | +| Exchanging information about the secondary UL frequency | a) Secondary UL Frequency Reporting
b) Secondary UL Frequency Update | + +--- + +## 8 NBAP Procedures + +### 8.1 Elementary Procedures + +NBAP procedures are divided into common procedures and dedicated procedures. + +- NBAP common procedures are procedures that request initiation of a Node B Communication Context for a specific UE in Node B or are not related to a specific UE. NBAP common procedures also incorporate logical O&M (TS 25.401 [1]) procedures. +- NBAP dedicated procedures are procedures that are related to a specific Node B Communication Context in Node B. This Node B Communication Context is identified by a Node B Communication Context identity. + +The two types of procedures may be carried on separate signalling links. + +In the following tables, all EPs are divided into Class 1 and Class 2 EPs: + +Table 2: Class 1 + +| Elementary Procedure | Message | Successful Outcome | Unsuccessful Outcome | +|-----------------------------------------------------|--------------------------------------------------|---------------------------------------------------|--------------------------------------------------| +| | | Response message | Response message | +| Cell Setup | CELL SETUP REQUEST | CELL SETUP RESPONSE | CELL SETUP FAILURE | +| Cell Reconfiguration | CELL RECONFIGURATION REQUEST | CELL RECONFIGURATION RESPONSE | CELL RECONFIGURATION FAILURE | +| Cell Deletion | CELL DELETION REQUEST | CELL DELETION RESPONSE | | +| Common Transport Channel Setup | COMMON TRANSPORT CHANNEL SETUP REQUEST | COMMON TRANSPORT CHANNEL SETUP RESPONSE | COMMON TRANSPORT CHANNEL SETUP FAILURE | +| Common Transport Channel Reconfiguration | COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST | COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE | COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE | +| Common Transport Channel Deletion | COMMON TRANSPORT CHANNEL DELETION REQUEST | COMMON TRANSPORT CHANNEL DELETION RESPONSE | | +| Physical Shared Channel Reconfiguration | PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST | PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE | PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE | +| Audit | AUDIT REQUEST | AUDIT RESPONSE | AUDIT FAILURE | +| Block Resource | BLOCK RESOURCE REQUEST | BLOCK RESOURCE RESPONSE | BLOCK RESOURCE FAILURE | +| Radio Link Setup | RADIO LINK SETUP REQUEST | RADIO LINK SETUP RESPONSE | RADIO LINK SETUP FAILURE | +| System Information Update | SYSTEM INFORMATION UPDATE REQUEST | SYSTEM INFORMATION UPDATE RESPONSE | SYSTEM INFORMATION UPDATE FAILURE | +| Common Measurement Initiation | COMMON MEASUREMENT INITIATION REQUEST | COMMON MEASUREMENT INITIATION RESPONSE | COMMON MEASUREMENT INITIATION FAILURE | +| Radio Link Addition | RADIO LINK ADDITION REQUEST | RADIO LINK ADDITION RESPONSE | RADIO LINK ADDITION FAILURE | +| Radio Link Deletion | RADIO LINK DELETION REQUEST | RADIO LINK DELETION RESPONSE | | +| Synchronised Radio Link Reconfiguration Preparation | RADIO LINK RECONFIGURATION PREPARE | RADIO LINK RECONFIGURATION READY | RADIO LINK RECONFIGURATION FAILURE | +| Unsynchronised Radio Link Reconfiguration | RADIO LINK RECONFIGURATION REQUEST | RADIO LINK RECONFIGURATION RESPONSE | RADIO LINK RECONFIGURATION FAILURE | +| Dedicated Measurement Initiation | DEDICATED MEASUREMENT INITIATION REQUEST | DEDICATED MEASUREMENT INITIATION RESPONSE | DEDICATED MEASUREMENT INITIATION FAILURE | +| Reset | RESET REQUEST | RESET RESPONSE | | +| Cell Synchronisation Initiation [TDD] | CELL SYNCHRONISATION INITIATION REQUEST | CELL SYNCHRONISATION INITIATION RESPONSE | CELL SYNCHRONISATION INITIATION FAILURE | +| Cell Synchronisation Reconfiguration [TDD] | CELL SYNCHRONISATION RECONFIGURATION REQUEST | CELL SYNCHRONISATION RECONFIGURATION RESPONSE | CELL SYNCHRONISATION RECONFIGURATION FAILURE | +| Cell Synchronisation Adjustment [TDD] | CELL SYNCHRONISATION ADJUSTMENT REQUEST | CELL SYNCHRONISATION ADJUSTMENT RESPONSE | CELL SYNCHRONISATION ADJUSTMENT FAILURE | +| Information Exchange Initiation | INFORMATION EXCHANGE INITIATION REQUEST | INFORMATION EXCHANGE INITIATION RESPONSE | INFORMATION EXCHANGE INITIATION FAILURE | +| UE Status Update Confirmation | UE STATUS UPDATE CONFIRM REQUEST | UE STATUS UPDATE CONFIRM RESPONSE | | + +Table 3: Class 2 + +| Elementary Procedure | Message | +|------------------------------------------------------|-------------------------------------------| +| Resource Status Indication | RESOURCE STATUS INDICATION | +| Audit Required | AUDIT REQUIRED INDICATION | +| Common Measurement Reporting | COMMON MEASUREMENT REPORT | +| Common Measurement Termination | COMMON MEASUREMENT TERMINATION REQUEST | +| Common Measurement Failure | COMMON MEASUREMENT FAILURE INDICATION | +| Synchronised Radio Link Reconfiguration Commit | RADIO LINK RECONFIGURATION COMMIT | +| Synchronised Radio Link Reconfiguration Cancellation | RADIO LINK RECONFIGURATION CANCEL | +| Radio Link Failure | RADIO LINK FAILURE INDICATION | +| Radio Link Restoration | RADIO LINK RESTORE INDICATION | +| Dedicated Measurement Reporting | DEDICATED MEASUREMENT REPORT | +| Dedicated Measurement Termination | DEDICATED MEASUREMENT TERMINATION REQUEST | +| Dedicated Measurement Failure | DEDICATED MEASUREMENT FAILURE INDICATION | +| Downlink Power Control [FDD] | DL POWER CONTROL REQUEST | +| Compressed Mode Command [FDD] | COMPRESSED MODE COMMAND | +| Unblock Resource | UNBLOCK RESOURCE INDICATION | +| Error Indication | ERROR INDICATION | +| Downlink Power Timeslot Control [TDD] | DL POWER TIMESLOT CONTROL REQUEST | +| Radio Link Pre-emption | RADIO LINK PREEMPTION REQUIRED INDICATION | +| Cell Synchronisation Reporting [TDD] | CELL SYNCHRONISATION REPORT | +| Cell Synchronisation Termination [TDD] | CELL SYNCHRONISATION TERMINATION REQUEST | +| Cell Synchronisation Failure [TDD] | CELL SYNCHRONISATION FAILURE INDICATION | +| Information Reporting | INFORMATION REPORT | +| Information Exchange Termination | INFORMATION EXCHANGE TERMINATION REQUEST | +| Information Exchange Failure | INFORMATION EXCHANGE FAILURE INDICATION | +| Bearer Re-arrangement | BEARER REARRANGEMENT INDICATION | +| Radio Link Activation | RADIO LINK ACTIVATION COMMAND | +| Radio Link Parameter Update | RADIO LINK PARAMETER UPDATE INDICATION | +| MBMS Notification Update | MBMS NOTIFICATION UPDATE COMMAND | +| UE Status Update [FDD and 1.28 Mcps TDD] | UE STATUS UPDATE COMMAND | +| Secondary UL Frequency Reporting | SECONDARY UL FREQUENCY REPORT | +| Secondary UL Frequency Update | SECONDARY UL FREQUENCY UPDATE INDICATION | + +## 8.2 NBAP Common Procedures + +### 8.2.1 Common Transport Channel Setup + +#### 8.2.1.1 General + +This procedure is used for establishing the necessary resources in Node B, regarding Secondary CCPCH, PICH, PRACH, AICH [FDD], FACH, PCH, MICH, RACH, BCH, E-RUCCH [3.84 Mcps and 7.68 Mcps TDD], PLCCH [1.28Mcps TDD] and FPACH [1.28Mcps TDD]. + +### 8.2.1.2 Successful Operation + +![Sequence diagram showing the Common Transport Channel Setup procedure. A CRNC sends a 'COMMON TRANSPORT CHANNEL SETUP REQUEST' to a Node B, and the Node B responds with a 'COMMON TRANSPORT CHANNEL SETUP RESPONSE'.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + Note right of Node B: Node B + CRNC->>Node B: COMMON TRANSPORT CHANNEL SETUP REQUEST + Node B-->>CRNC: COMMON TRANSPORT CHANNEL SETUP RESPONSE + +``` + +Sequence diagram showing the Common Transport Channel Setup procedure. A CRNC sends a 'COMMON TRANSPORT CHANNEL SETUP REQUEST' to a Node B, and the Node B responds with a 'COMMON TRANSPORT CHANNEL SETUP RESPONSE'. + +**Figure 1: Common Transport Channel Setup procedure, Successful Operation** + +The procedure is initiated with a COMMON TRANSPORT CHANNEL SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +One message can configure only one of the following combinations: + +- [FDD - one Secondary CCPCH, and FACHs, BCH, PCH, PICH and MICH related to that Secondary CCPCH], or +- [TDD - one CCTrCH consisting of Secondary CCPCHs and FACHs, PCH with the corresponding PICH and MICH related to that group of Secondary CCPCHs], or +- one [1.28Mcps TDD - or more] PRACH, one RACH and one AICH [FDD] and one FPACH[1.28Mcps TDD] related to that PRACH, or +- one PLCCH [1.28Mcps TDD], or +- one E-RUCCH [3.84Mcps TDD and 7.68Mcps TDD]. + +#### Secondary CCPCH: + +[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Secondary CCPCH* IE, the Node B shall configure and activate the indicated Secondary CCPCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.] + +[FDD - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *FDD S-CCPCH Frame Offset* IE within the *Secondary CCPCH* IE, the Node B shall apply the indicated frame offset for the concerned Secondary CCPCH.] + +[TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Secondary CCPCH* IE, the Node B shall configure and activate the indicated Secondary CCPCH(s) according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.] + +[3.84Mcps TDD and 7.68Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *TFCI Presence* IE, the Node B shall apply the indicated TFCI presence in the timeslot of the S-CCPCH. If all the S-CCPCHs defined in a timeslot do not have a *TFCI Presence* IE included, the Node B shall apply a TFCI field in the lowest numbered S-CCPCH of the timeslot.] + +[TDD - FACHs and PCH may be mapped onto a CCTrCH which may consist of several Secondary CCPCHs] + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *FACH Parameters* IE, the Node B shall configure and activate the indicated FACH(s) according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *PCH Parameters* IE, the Node B shall configure and activate the concerned PCH and the associated PICH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *BCH Parameters* IE, the Node B shall configure and activate the concerned BCH mapped on SCCPCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +[1.28Mcps TDD - If the *PCH Power* IE is included in the *PCH Parameters* IE of the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall use this value as the power at which the PCH shall be transmitted.] + +[TDD - If the *TSTD Indicator* IE for the S-CCPCH is included and is set to "active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall activate TSTD diversity for all S-CCPCHs defined in the message that are not beacon channels (TS 25.221 [19], TS 25.224 [21]). If the *TSTD Indicator* IE is not included or is set to "not active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall not activate TSTD diversity for the S-CCPCHs defined in the message.] + +[1.28Mcps TDD - If the *TSTD Indicator* IE for the PICH is included and is set to "active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST message, the Node B shall activate TSTD diversity for the PICH if it is not a beacon channel (TS 25.221 [19], TS 25.224 [21]). If the *TSTD Indicator* IE is set to "not active" or the *TSTD Indicator* IE is not included for the PICH in the COMMON TRANSPORT CHANNEL SETUP REQUEST message, the Node B shall not activate TSTD diversity for the PICH.] + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *MICH Parameters* IE, the Node B shall configure and activate the concerned MICH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Modulation Power Offset* IE, in the *Secondary CCPCH* IE, the Node B shall apply the indicated modulation, and power offset in case of 16QAM, for the concerned Secondary CCPCH.] + +[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Extended Secondary CCPCH Slot Format* IE, in the *Secondary CCPCH* IE, the Node B shall ignore the *Secondary CCPCH Slot Format* IE and apply the slot format indicated in the *Extended Secondary CCPCH Slot Format* IE.] + +[3.84Mcps TDD and 7.68Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Modulation* IE, the Node B shall apply the indicated modulation for the CCTrCH.] + +[3.84Mcps TDD and 7.68Mcps TDD - If a timeslot has been configured for MBSFN operation then the contents of the [3.84Mcps TDD - *Midamble Shift and Burst Type* IE] [7.68Mcps TDD - *Midamble Shift and Burst Type 7.68Mcps* IE] shall be ignored and burst type 4, *Kcell*=1 shall be used (TS 25.221 [19]).] + +[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the *MBSFN Special Time Slot LCR* IE indicates from CRNC to the Node B whether the channel is deployed on the MBSFN Special Time Slot for MBSFN only mode (TS 25.221 [19]).] + +[1.28Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *UARFCN* IE in the *Secondary CCPCHs* IE, this Secondary CCPCH providing MBMS service in non-MBSFN only mode shall be setup on the secondary frequency indicated by the *UARFCN* IE.] + +[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *IMB Parameters* IE within the *Secondary CCPCH* IE, the Node B shall apply 3.84Mcps MBSFN IMB operation.] + +[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Last DL Channelisation Code Number* IE within the *IMB Parameters* IE, the Node B may use the indicated range of the DL channelization codes in the new configuration.] + +## PRACH: + +When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *PRACH* IE, the Node B shall configure and activate the indicated PRACH and the associated RACH [FDD - and the associated AICH] according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +[1.28Mcps TDD - The resource indicated by the *PRACH* IE is used for RACH random access as well as E-DCH random access. The way to differentiate the two access type on PRACH physical resource shall be operated according to TS 25.224 [21].] + +[1.28Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *UARFCN* IE in the *PRACH* IE, the PRACH shall be set up on the secondary frequency indicated by the *UARFCN* IE.] + +## [1.28Mcps TDD - FPACH]: + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *FPACH* IE, the Node B shall configure and activate the indicated FPACH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +Where more than one FPACH is defined, the FPACH that Node B should use is defined by the UpPCH signature (SYNC\_UL) code that the UE used. The FPACH number = N mod M where N denotes the signature number (0..7) and M denotes the number of FPACHs that are defined in a cell. The FPACH number is in ascending order by *Common Physical Channel ID* IE contained in the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +If the *FPACH* IE contains the *UARFCN* IE, the FPACH shall be set up on the secondary frequency indicated by the *UARFCN* IE. + +When the FPACH is set up on the secondary frequency of a multi-frequency cell, if the *PRACH LCR* IE contains the *UARFCN* IE, the *RACH* IE included in the *PRACH LCR* IE shall be ignored; otherwise all IEs included in the *PRACH LCR* IE shall be ignored. + +#### [1.28Mcps TDD - PLCCH]: + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *PLCCH* IE, the Node B shall configure and activate the indicated PLCCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message when one or more of the PLCCH sequence numbers have been assigned to one or more radio links.] + +#### [3.84Mcps TDD and 7.68Mcps TDD - E-RUCCH]: + +When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the [3.84Mcps TDD - *E-RUCCH* IE] [7.68Mcps TDD - *E-RUCCH* 7.68Mcps IE], the Node B shall configure and activate the indicated E-RUCCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message. + +#### RACH, FACH, and PCH: + +If the *TNL QoS* IE is included for a RACH, FACH, or PCH and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related RACH, FACH or PCH. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Broadcast Reference* IE in the *FACH Parameters* IE, and one or more established FACH common transport channels with the same Broadcast Reference, the same Transport Format Set, the same ToAWS and the same ToAWE exist (all of them in other distinct cells within the Node B), the Node B may include the *Broadcast Common Transport Bearer Indication* IE in the *Common Transport Channel Information Response* IE in the COMMON TRANSPORT CHANNEL SETUP RESPONSE message to inform the CRNC that the existing transport bearer, identified by *Broadcast Common Transport Bearer Indication* IE, shall be used instead of establishing a new transport bearer. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Broadcast Reference* IE in the *FACH Parameters* IE and no common transport channel with the same Broadcast Reference, the same Transport Format Set, the same ToAWS and the same ToAWE exists in another cell within the Node B, or if the Node B decides to establish a new transport bearer, the Node B may store the value of *Broadcast Reference* IE. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *IP Multicast Indication* IE, and if supported, the Node B may join the indicated IP multicast group if it has not done so yet (IETF RFC 3376 [41] in case of IPv4, IETF RFC 3810 [42] in case of IPv6). If the Node B does join the IP multicast group, or is already joined to the IP multicast group as a result of a previous procedure, the Node B shall include the *IP Multicast Data Bearer Indication* IE in the COMMON TRANSPORT CHANNEL INFORMATION RESPONSE message to inform the CRNC that the existing IP multicast transport bearer, identified by *IP Multicast Indication* IE in the corresponding COMMON TRANSPORT CHANNEL SETUP REQUEST message, shall be used instead of using a IP unicast transport bearer. If the COMMON TRANSPORT CHANNEL INFORMATION RESPONSE message does not contain the *IP Multicast Data Bearer Indication* IE, the CRNC shall send FACH data frames on the IP unicast transport bearer. No matter whether the Node B has joined the indicated IP multicast group, a new transport bearer shall be established using the *Transport Layer Address* IE and *Binding ID* IE and FACH specific control frames, e.g. TIMING ADJUSTMENT, shall be sent on the established Iub transport bearer. + +#### General: + +After successfully configuring the requested common transport channels and the common physical channels, the Node B shall store the value of *Configuration Generation ID IE* and it shall respond with the COMMON TRANSPORT CHANNEL SETUP RESPONSE message with the *Common Transport Channel ID IE*, the *Binding ID IE* (if no *Broadcast Common Transport Bearer Indication IE* is included or if no *BCH Parameters IE* is included) and the *Transport Layer Address IE* (if no *Broadcast Common Transport Bearer Indication IE* is included or if no *BCH Parameters IE* is included) for the configured common transport channels. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message includes the *Transport Layer Address* and *Binding ID IEs*, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the indicated common transport channels. + +After a successful procedure and once the transport bearers are established, the configured common transport channels and the common physical channels shall adopt the state Enabled (TS 25.430 [6]) in the Node B and the common physical channels exist on the Uu interface. + +### 8.2.1.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Common Transport Channel Setup procedure. The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST to Node B, and Node B responds with a COMMON TRANSPORT CHANNEL SETUP FAILURE.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON TRANSPORT CHANNEL SETUP REQUEST + CRNC->>Node B: COMMON TRANSPORT CHANNEL SETUP REQUEST + Note left of Node B: COMMON TRANSPORT CHANNEL SETUP FAILURE + Node B-->>CRNC: COMMON TRANSPORT CHANNEL SETUP FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Common Transport Channel Setup procedure. The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST to Node B, and Node B responds with a COMMON TRANSPORT CHANNEL SETUP FAILURE. + +**Figure 2: Common Transport Channel Setup procedure, Unsuccessful Operation** + +If the Node B is not able to support all or part of the configuration, it shall reject the configuration of all the channels in the COMMON TRANSPORT CHANNEL SETUP REQUEST message. The channels in the COMMON TRANSPORT CHANNEL SETUP REQUEST message shall remain in the same state as prior to the procedure. The *Cause IE* shall be set to an appropriate value. The value of *Configuration Generation ID IE* from the COMMON TRANSPORT CHANNEL SETUP REQUEST message shall not be stored. + +If the configuration was unsuccessful, the Node B shall respond with a COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +Typical cause values are as follows: + +#### Radio Network Layer Cause: + +- Cell not available +- Power level not supported +- Node B Resources unavailable +- Requested Tx Diversity Mode not supported +- UL SF not supported +- DL SF not supported +- Common Transport Channel Type not supported +- MICH not supported + +#### Transport Layer Cause: + +- Transport Resources Unavailable + +#### Miscellaneous Cause: + +- O&M Intervention + +- Control processing overload +- HW failure + +### 8.2.1.4 Abnormal Conditions + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Secondary CCPCH* IE, and that IE contains [FDD - neither the *FACH Parameters* IE nor the *PCH Parameters* IE, nor the *BCH Parameters* IE] [TDD - neither the *FACH* IE nor the *PCH* IE], the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +[TDD - If the *FACH CCTrCH Id* IE or the *PCH CCTrCH Id* IE does not equal the *SCCPCH CCTrCH Id* IE, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.] + +[TDD - If the *TDD Physical Channel Offset* IE, the *Repetition Period* IE, and the *Repetition Length* IE are not equal for each SCCPCH configured within the CCTrCH or the *TFCI Presence* IE are not equal for any two SCCPCHs configured in the same timeslot, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.] + +[1.28Mcps TDD - If the *Common Transport Channel ID* IE, and the *Transport Format Set* IE are not equal for each RACH configured in PRACH, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.] + +[1.28Mcps TDD - If the *UARFCN* IE in the *PRACH LCR* IE is not equal to the *UARFCN* IE in any other *PRACH LCR* IE configured on one RACH, or if the *UARFCN* IE in *PRACH LCR* IE is not equal to the *UARFCN* IE in *FPACH* IE, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.] + +If the state is already Enabled or Disabled (TS 25.430 [6]) for at least one channel in the COMMON TRANSPORT CHANNEL SETUP REQUEST message which is received, the Node B shall reject the configuration of all channels with the *Cause* IE set to "Message not compatible with receiver state". + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport channel intended to be established, the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *MICH Parameters* IE but not the *FACH Parameters* IE [FDD - for one S-CCPCH], the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains a *Broadcast Reference* IE value already associated to an existing FACH in the same cell, or if the message contains the same value for the *Broadcast Reference* IEs included in the *FACH Parameters* IEs for several FACHs in the list of FACHs defined on the Secondary CCPCH, the Node B shall reject the procedure, using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains both the *Broadcast Reference* IE and the *IP Multicast Indication* IE, the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the *IMB Parameters* IE that includes the *Last DL Channelisation Code Number* IE and if the Secondary CCPCH Slot Format IE is set to "1", then the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.] + +If ALCAP is not used, if the COMMON TRANSPORT CHANNEL SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *FACH Parameters* IE, *PCH Parameters* IE and/or [FDD-*RACH Parameters*][TDD - *RACH*] IE, then the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message. + +## 8.2.2 Common Transport Channel Reconfiguration + +### 8.2.2.1 General + +This procedure is used for reconfiguring common transport channels and/or common physical channels, while they still might be in operation. + +### 8.2.2.2 Successful Operation + +![Sequence diagram showing the successful operation of Common Transport Channel Reconfiguration. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B with the text 'COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST'. A return horizontal arrow points from Node B to CRNC with the text 'COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE'.](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST + CRNC->>Node B: COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST + Note left of Node B: COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE + Node B-->>CRNC: COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE + +``` + +Sequence diagram showing the successful operation of Common Transport Channel Reconfiguration. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B with the text 'COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST'. A return horizontal arrow points from Node B to CRNC with the text 'COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE'. + +**Figure 3: Common Transport Channel Reconfiguration, Successful Operation** + +The procedure is initiated with a COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +One message can configure only one of the following combinations: + +- [FDD - FACHs, BCH, one PCH, one PICH and/or one MICH related to one Secondary CCPCH], or +- [TDD - one CCTrCH consisting of Secondary CCPCHs and FACHs, PCH with the corresponding PICH and MICH related to that group of Secondary CCPCHs], or +- one RACH and/or one AICH[FDD] and/or one FPACH[1.28Mcps TDD] related to one PRACH, or +- [1.28Mcps TDD - One UpPCH]. + +#### SCCPCH: + +[TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *SCCPCH Power IE*, the Node B shall reconfigure the maximum power that the indicated S-CCPCH shall use.] + +#### FACH: + +If the *FACH Parameters IE* is present, the Node B shall reconfigure the indicated FACH(s). + +[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Max FACH Power IE*, the Node B shall reconfigure the maximum power that the indicated FACH may use.] + +[1.28Mcps TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Max FACH Power IE*, the Node B shall reconfigure the maximum power that the indicated FACH may use.] + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *ToAWS IE*, the Node B shall reconfigure the time of arrival window startpoint that the indicated FACH shall use. In case a transport bearer is used by several FACH channels in different cells, the reconfiguration of the time of arrival window startpoint requested in one cell shall be applied to all these FACH channels. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *ToAWE IE*, the Node B shall reconfigure the time of arrival window endpoint that the indicated FACH shall use. In case a transport bearer is used by several FACH channels in different cells, the reconfiguration of the time of arrival window endpoint requested in one cell shall be applied to all these FACH channels. + +If the *TNL QoS IE* is included and if ALCAP is not used, the *TNL QoS IE* may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related FACH. + +#### PCH: + +If the *PCH Parameters IE* is present, the Node B shall reconfigure the indicated PCH. + +[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *PCH Power* IE, the Node B shall reconfigure the power that the PCH shall use.] + +[1.28Mcps TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *PCH Power* IE, the Node B shall reconfigure the power that the PCH shall use.] + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *ToAWS* IE, the Node B shall reconfigure the time of arrival window startpoint that the PCH shall use. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *ToAWE* IE, the Node B shall reconfigure the time of arrival window endpoint that the PCH shall use. + +If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related PCH. + +#### **BCH:** + +If the *BCH Parameters* IE is present, the Node B shall reconfigure the indicated BCH mapped on SCCPCH. + +[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *BCH Power* IE, the Node B shall reconfigure the power that the BCH shall use.] + +#### **PICH:** + +If the *PICH Parameters* IE is present, the Node B shall reconfigure the indicated PICH. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *PICH Power* IE, the Node B shall reconfigure the power that the PICH shall use. + +#### **MICH:** + +If the *MICH Parameters* IE is present, the Node B shall reconfigure the MICH. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *MICH Power* IE, the Node B shall reconfigure the power that the MICH shall use. + +#### **[FDD - PRACH]:** + +If the *PRACH Parameters* IE is present, the Node B shall reconfigure the indicated PRACH(s). + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Preamble Signatures* IE, the Node B shall reconfigure the preamble signatures that the indicated PRACH shall use. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Allowed Slot Format Information* IE, the Node B shall reconfigure the slot formats that the indicated PRACH shall use. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *RACH Sub Channel Numbers* IE, the Node B shall reconfigure the sub channel numbers that the indicated PRACH shall use. + +If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related RACH. + +#### **[FDD - AICH]:** + +If the *AICH Parameters* IE is present, the Node B shall reconfigure the indicated AICH(s). + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *AICH Power* IE, the Node B shall reconfigure the power that the indicated AICH shall use. + +#### **[1.28Mcps TDD - FPACH]:** + +If the *FPACH Parameters* IE is included, the Node B shall reconfigure the indicated FPACH. + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Max FPACH Power* IE, the Node B shall reconfigure the power that the FPACH shall use. + +#### **[1.28Mcps TDD - UpPCH]:** + +If the *UpPCH Parameters* IE is included, the Node B shall reconfigure the position of the UpPCH. + +For a multi-frequency cell: + +- If the *UpPCH Position LCR* IE and the *UARFCN* IE are included, and the indicated frequency is primary frequency, the Node B shall reconfigure the position of the UpPCH on the primary frequency. +- If the *UpPCH Position LCR* IE and the *UARFCN* IE are included, and the indicated frequency is a secondary frequency, the Node B shall configure or reconfigure the position of the UpPCH on the secondary frequency. +- If the *UpPCH Position LCR* IE is not included, the Node B may delete the UpPCH on the secondary frequency indicated by the *UARFCN* IE. + +#### [1.28Mcps TDD - PLCCH]: + +If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the *Max PLCCH Power* IE, the Node B shall reconfigure the power that the PLCCH shall use. + +#### General: + +After a successful procedure, the channels will have adopted the new configuration in the Node B. The channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall remain in the same state as prior to the procedure. The Node B shall store the value of *Configuration Generation ID* IE and the Node B shall respond with the COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE message. + +### 8.2.2.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Common Transport Channel Reconfiguration procedure. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST' points from CRNC to Node B. A return horizontal arrow labeled 'COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE' points from Node B back to CRNC.](822e033872d5ab16e861571f47b81ba7_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST + CRNC->>Node B: COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST + Note left of Node B: COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE + Node B-->>CRNC: COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Common Transport Channel Reconfiguration procedure. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST' points from CRNC to Node B. A return horizontal arrow labeled 'COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE' points from Node B back to CRNC. + +**Figure 4: Common Transport Channel Reconfiguration procedure, Unsuccessful Operation** + +If the Node B is not able to support all or part of the configuration, it shall reject the configuration of all the channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message. The channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall remain in the same state as prior to the procedure. The *Cause* IE shall be set to an appropriate value. The value of *Configuration Generation ID* IE from the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall not be stored. + +If the configuration was unsuccessful, the Node B shall respond with the COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message. + +Typical cause values are as follows: + +#### Radio Network Layer Cause: + +- Cell not available +- Power level not supported +- Node B Resources unavailable + +#### Transport Layer Cause: + +- Transport Resources Unavailable + +#### Miscellaneous Cause: + +- O&M Intervention + +- Control processing overload +- HW failure + +### 8.2.2.4 Abnormal Conditions + +[1.28Mcps TDD - For a single frequency cell, if the *UpPCH Parameters* IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the *UpPCH Position LCR* IE is not present, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.] + +[1.28Mcps TDD - For a single frequency cell, if the *UARFCN* IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.] + +[1.28Mcps TDD - For a multi-frequency cell, if the *UpPCH Parameters* IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the *UpPCH Position LCR* IE is not present, and the frequency indicated by the *UARFCN* IE is primary frequency, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.] + +[1.28Mcps TDD - For a multi-frequency cell, if the *UpPCH Parameters* IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the *UpPCH Position LCR* IE is not present, and the frequency indicated by the *UARFCN* IE is secondary frequency on which the UpPCH is not configured, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.] + +## 8.2.3 Common Transport Channel Deletion + +### 8.2.3.1 General + +This procedure is used for deleting common physical channels and common transport channels. + +### 8.2.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Common Transport Channel Deletion procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'COMMON TRANSPORT CHANNEL DELETION REQUEST' points from CRNC to Node B. A return horizontal arrow labeled 'COMMON TRANSPORT CHANNEL DELETION RESPONSE' points from Node B back to CRNC.](2beb95006f1933bed737cfe1e6598db8_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON TRANSPORT CHANNEL DELETION REQUEST + CRNC->>Node B: COMMON TRANSPORT CHANNEL DELETION REQUEST + Note left of Node B: COMMON TRANSPORT CHANNEL DELETION RESPONSE + Node B-->>CRNC: COMMON TRANSPORT CHANNEL DELETION RESPONSE + +``` + +Sequence diagram showing the successful operation of the Common Transport Channel Deletion procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'COMMON TRANSPORT CHANNEL DELETION REQUEST' points from CRNC to Node B. A return horizontal arrow labeled 'COMMON TRANSPORT CHANNEL DELETION RESPONSE' points from Node B back to CRNC. + +**Figure 5: Common Transport Channel Deletion procedure, Successful Operation** + +The procedure is initiated with a COMMON TRANSPORT CHANNEL DELETION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +#### Secondary CCPCH: + +If the *Common Physical Channel ID* IE or *Common Physical Channel ID 7.68Mcps* IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a Secondary CCPCH, the Node B shall delete the indicated channel and the FACHs and PCH supported by that Secondary CCPCH. If there is a PCH that is deleted, the PICH associated with that PCH shall also be deleted. If an S-CCPCH is deleted, the MICH associated with that S-CCPCH shall also be deleted. + +If the *Common Physical Channel ID* IE or *Common Physical Channel ID 7.68Mcps* IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a common transport channel that is sharing a common transport bearer with other one or several common transport channels, the Node B shall delete the indicated channel but keep the common transport bearer which is shared by the remaining common transport channel(s). + +If the *Common Physical Channel ID* IE or *Common Physical Channel ID 7.68Mcps* IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a common transport channel which is using an IP multicast transport bearer, the Node B shall leave the IP multicast group if this channel is the last one in the group (IETF RFC 3376 [41] in case of IPv4, IETF RFC 3810 [42] in case of IPv6). + +#### PRACH: + +If the *Common Physical Channel ID* IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a PRACH, the Node B shall delete the indicated channel and the RACH supported by the PRACH. [FDD - The AICH associated with the RACH shall also be deleted.] + +#### [1.28Mcps TDD PLCCH: + +If the *Common Physical Channel ID* IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a PLCCH, the Node B shall delete the indicated channel.] + +#### General: + +[TDD - If the requested common physical channel is a part of a CCTrCH, all common transport channels and all common physical channels associated with this CCTrCH shall be deleted.] + +After a successful procedure, the channels are deleted in the Node B. The channels in the COMMON TRANSPORT CHANNEL DELETION REQUEST message shall be set to state Not Existing ref. TS 25.430 [6]. The Node B shall store the received value of the *Configuration Generation ID* IE and respond with the COMMON TRANSPORT CHANNEL DELETION RESPONSE message. + +### 8.2.3.3 Unsuccessful Operation + +- + +### 8.2.3.4 Abnormal Conditions + +If the C-ID in the COMMON TRANSPORT CHANNEL DELETION REQUEST message is not existing in the Node B or the Common Physical Channel ID does not exist in the Cell, the Node B shall respond with the COMMON TRANSPORT CHANNEL DELETION RESPONSE message. + +## 8.2.4 Block Resource + +### 8.2.4.1 General + +The Node B initiates this procedure to request the CRNC to prohibit the usage of the specified logical resources. + +The logical resource that can be blocked is a cell. + +### 8.2.4.2 Successful Operation + +![Sequence diagram showing the Block Resource procedure. The diagram has two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'BLOCK RESOURCE REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'BLOCK RESOURCE RESPONSE' points from CRNC to Node B.](bdd19e1aefc189598ab515f8f12518dd_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: Initiate procedure + Node B->>CRNC: BLOCK RESOURCE REQUEST + CRNC-->>Node B: BLOCK RESOURCE RESPONSE + +``` + +Sequence diagram showing the Block Resource procedure. The diagram has two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'BLOCK RESOURCE REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'BLOCK RESOURCE RESPONSE' points from CRNC to Node B. + +**Figure 6: Block Resource procedure, Successful Operation** + +The procedure is initiated with a *BLOCK RESOURCE REQUEST* message sent from the Node B to the CRNC using the Node B Control Port. + +Upon reception of the *BLOCK RESOURCE REQUEST* message, the CRNC shall prohibit the use of the indicated logical resources according to the *Blocking Priority Indicator* IE. + +If the *Blocking Priority Indicator* IE in the BLOCK RESOURCE REQUEST message indicates "High Priority", the CRNC shall prohibit the use of the logical resources immediately. + +If the *Blocking Priority Indicator* IE in the BLOCK RESOURCE REQUEST message indicates "Normal Priority", the CRNC shall prohibit the use of the logical resources if the resources are idle or immediately upon expiry of the shutdown timer specified by the *Shutdown Timer* IE in the BLOCK RESOURCE REQUEST message. New traffic shall not be allowed to use the logical resources while the CRNC waits for the resources to become idle and once the resources are blocked. + +If the *Blocking Priority Indicator* IE in the BLOCK RESOURCE REQUEST message indicates "Low Priority", the CRNC shall prohibit the use of the logical resources when the resources become idle. New traffic shall not be allowed to use the logical resources while the CRNC waits for the resources to become idle and once the resources are blocked. + +If the resources are successfully blocked, the CRNC shall respond with a BLOCK RESOURCE RESPONSE message. Upon reception of the BLOCK RESOURCE RESPONSE message, the Node B may disable [3.84Mcps TDD - SCH], [FDD - the Primary SCH, the Secondary SCH, the Primary CPICH, if present the Secondary CPICH(s)], [1.28Mcps TDD - DwPCH] and the Primary CCPCH. The other logical resources in the cell shall be considered as blocked. + +Reconfiguration of logical resources and change of System Information can be done, even when the logical resources are blocked. + +#### Interactions with the Unblock Resource procedure: + +If the UNBLOCK RESOURCE INDICATION message is received by the CRNC while a Block Resource procedure on the same logical resources is in progress, the CRNC shall cancel the Block Resource procedure and proceed with the Unblock Resource procedure. + +If the BLOCK RESOURCE RESPONSE message or the BLOCK RESOURCE FAILURE message is received by the Node B after the Node B has initiated an Unblock Resource procedure on the same logical resources as the ongoing Block Resource procedure, the Node B shall ignore the response to the Block Resource procedure. + +### 8.2.4.3 Unsuccessful Operation + +![Sequence diagram showing the Block Resource procedure, Unsuccessful Operation. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'BLOCK RESOURCE REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'BLOCK RESOURCE FAILURE' points from CRNC to Node B.](a89d151b67109378baed0c117830cf78_img.jpg) + +``` +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: Initiate Block Resource procedure + Node B->>CRNC: BLOCK RESOURCE REQUEST + Note left of CRNC: Reject request + CRNC->>Node B: BLOCK RESOURCE FAILURE +``` + +Sequence diagram showing the Block Resource procedure, Unsuccessful Operation. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow labeled 'BLOCK RESOURCE REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'BLOCK RESOURCE FAILURE' points from CRNC to Node B. + +Figure 7: Block Resource procedure, Unsuccessful Operation + +The CRNC may reject the request to block the logical resources, in which case the logical resources will remain unaffected and the CRNC shall respond to the Node B with the BLOCK RESOURCE FAILURE message. Upon reception of the BLOCK RESOURCE FAILURE message, the Node B shall leave the logical resources in the state that they were in prior to the start of the Block Resource procedure. + +Typical cause values are as follows: + +#### Miscellaneous Cause: + +- O&M Intervention +- Control processing overload +- HW failure + +#### Radio Network Layer Cause: + +- Priority transport channel established + +#### 8.2.4.4 Abnormal Conditions + +- + +### 8.2.5 Unblock Resource + +#### 8.2.5.1 General + +The Node B initiates this procedure to indicate to the CRNC that logical resources are now unblocked. + +The logical resource that can be unblocked is a cell. + +#### 8.2.5.2 Successful Operation + +![Sequence diagram for Unblock Resource procedure, Successful Operation](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow labeled "UNBLOCK RESOURCE INDICATION" points from the Node B to the CRNC. + +Sequence diagram for Unblock Resource procedure, Successful Operation + +**Figure 8: Unblock Resource procedure, Successful Operation** + +The procedure is initiated with an UNBLOCK RESOURCE INDICATION message sent from the Node B to the CRNC using the Node B Control Port. The Node B shall enable [3.84Mcps TDD - SCH], [FDD - the Primary SCH, the Secondary SCH, the Primary CPICH, the Secondary CPICH(s) (if present)], [1.28Mcps TDD - DwPCH] and the Primary CCPCH that had been disabled due to the preceding Block Resource procedure before sending the UNBLOCK RESOURCE INDICATION message. Upon reception of the UNBLOCK RESOURCE INDICATION message, the CRNC may permit the use of the logical resources. + +All physical channels and transport channels associated to the cell that is unblocked are also unblocked. + +#### 8.2.5.3 Abnormal Conditions + +- + +### 8.2.6 Audit Required + +#### 8.2.6.1 General + +The Node B initiates this procedure to request the CRNC to perform an audit of the logical resources at the Node B. This procedure is used to indicate a possible misalignment of state or configuration information. + +#### 8.2.6.2 Successful Operation + +![Sequence diagram for Audit Required procedure, Successful Operation](e1a3f5045f139b39707b3ebb76ad254c_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow labeled "AUDIT REQUIRED INDICATION" points from the Node B to the CRNC. + +Sequence diagram for Audit Required procedure, Successful Operation + +**Figure 9: Audit Required procedure, Successful Operation** + +The procedure is initiated with an AUDIT REQUIRED INDICATION message sent from the Node B to the CRNC using the Node B Control Port. + +If the Node B cannot ensure alignment of the state or configuration information, it should initiate the Audit Required procedure. + +Upon receipt of the AUDIT REQUIRED INDICATION message, the CRNC should initiate the Audit procedure. + +### 8.2.6.3 Abnormal Conditions + +- + +## 8.2.7 Audit + +### 8.2.7.1 General + +This procedure is executed by the CRNC to perform an audit of the configuration and status of the logical resources in the Node B. A complete audit of a Node B is performed by one or more Audit procedures, together performing an audit sequence. The audit may cause the CRNC to re-synchronise the Node B to the status of logical resources known by the CRNC, that the Node B can support. + +### 8.2.7.2 Successful Operation + +![Sequence diagram showing the audit procedure between CRNC and Node B. The CRNC sends an AUDIT REQUEST message to the Node B. The Node B responds with an AUDIT RESPONSE message to the CRNC.](215165a27ad7d72bd39fdf55a3cb7486_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: AUDIT REQUEST + CRNC->>Node B: AUDIT REQUEST + Note left of Node B: AUDIT RESPONSE + Node B-->>CRNC: AUDIT RESPONSE + +``` + +Sequence diagram showing the audit procedure between CRNC and Node B. The CRNC sends an AUDIT REQUEST message to the Node B. The Node B responds with an AUDIT RESPONSE message to the CRNC. + +**Figure 10: Audit procedure, Successful Operation** + +The procedure is initiated with an AUDIT REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +If the *Start Of Audit Sequence Indicator* IE in the AUDIT REQUEST message is set to "start of audit sequence" a new audit sequence is started, any ongoing audit sequence shall be aborted and the Node B shall provide (part of the) audit information. If the *Start Of Audit Sequence Indicator* IE is set to "not start of audit sequence", the Node B shall provide (part of) the remaining audit information not already provided during this audit sequence. + +If the information provided in the AUDIT RESPONSE message completes the audit sequence, the Node B shall set the *End Of Audit Sequence Indicator* IE in the AUDIT RESPONSE message to "End of Audit Sequence". If not all audit information has been provided yet as part of the ongoing audit sequence, the Node B shall set the *End Of Audit Sequence Indicator* IE in the AUDIT RESPONSE message to "Not End of Audit Sequence". + +#### Information Provided In One Audit Sequence: + +The Node B shall include one *Local Cell Information* IE for each local cell present in the Node B. The Node B shall include the *Maximum DL Power Capability* IE, the *Minimum Spreading Factor* IE and the *Minimum DL Power Capability* IE when any of those values are known by the Node B. The Node B shall include the *HSDPA Capability* IE set to "HSDPA Capable" and may include *HS-DSCH MAC-d PDU Size Capability* IE for every HSDPA-capable Local Cell. The Node B shall include the *E-DCH Capability* IE set to "E-DCH Capable" and may include *E-DCH MAC-d PDU Size Capability* IE for every E-DCH-capable Local Cell. The Node B shall include the *MBMS Capability* IE set to "MBMS Capable" for every MBMS-capable Local Cell. [FDD - The Node B shall include the *F-DPCH Capability* IE set to "F-DPCH Capable" for every F-DPCH-capable Local Cell.] [FDD - The Node B shall include the *Continuous Packet Connectivity DTX-DRX Capability* IE set to "Continuous Packet Connectivity DTX-DRX Capable" when Continuous Packet Connectivity DTX-DRX is supported for every Local Cell that is both HSDPA-capable and E-DCH-capable.] [FDD - The Node B shall include the *Continuous Packet Connectivity HS-SCCH less Capability* IE set to "Continuous Packet Connectivity HS-SCCH less Capable" when Continuous Packet Connectivity HS-SCCH less is supported for every Local Cell that is both HSDPA-capable and E-DCH-capable.] [FDD - The Node B shall include the *MIMO Capability* IE set to "MIMO Capable" for every MIMO-capable Local Cell.] [FDD - The Node B shall include the *SixtyfourQAM DL Capability* IE set to "SixtyfourQAM DL Capable" for every SixtyfourQAM DL-capable Local + +Cell.] [FDD - The Node B shall include the *Enhanced FACH Capability* IE set to "Enhanced FACH Capable" for every Enhanced FACH-capable Local Cell.] [FDD - The Node B shall include the *SixteenQAM UL Capability* IE set to "SixteenQAM UL Capable" for every SixteenQAM UL-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *MBSFN Only Mode Capability* IE set to "MBSFN Only Mode Capable" for every MBSFN Only Mode-capable Local Cell.] [FDD - The Node B shall include the *F-DPCH Slot Format Capability* IE set to "F-DPCH Slot Format Capable" for every F-DPCH Slot Format-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *SixtyfourQAM DL Capability* IE set to "SixtyfourQAM DL Capable" for every SixtyfourQAM DL-capable Local Cell.] [FDD - The Node B shall include the *Common E-DCH Capability* IE set to "Common E-DCH Capable" for every Common E-DCH capable Local Cell.] The Node B shall include the *E-DPCCH Power Boosting Capability* IE set to "E-DPCCH Power Boosting Capable" for every E-DPCCH Power Boosting-capable Local Cell. [FDD - The Node B shall include the *SixtyfourQAM DL and MIMO Combined Capability* IE set to "SixtyfourQAM DL and MIMO Combined Capable" when Combined SixtyfourQAM DL and MIMO is supported for every Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable.] [1.28Mcps TDD - The Node B shall include the *Enhanced FACH Capability* IE set to "Enhanced FACH Capable" for every Enhanced FACH-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *Enhanced PCH Capability* IE set to "Enhanced PCH Capable" for every Enhanced PCH-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *Enhanced UE DRX Capability LCR* IE set to "Enhanced UE DRX Capable" for every Enhanced UE DRX Capable Local Cell.] [FDD - The Node B shall include the *Multi Cell Capability Info* IE and set the *Multi Cell Capability* IE value to "Multi Cell Capable" for every Multi Cell operation capable Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multiple adjacent and/or non-adjacent carrier operation (TS 25.133 [22]) (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the *Possible Secondary Serving Cell List* IE. For each cell in the *Possible Secondary Serving Cell List* IE that is Multi Cell E-DCH Capable, indicated in the *Cell Capability Container* IE with the "Multi Cell E-DCH Capability" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the *Multicell E-DCH Restriction* IE set to "TRUE" in the *Possible Secondary Serving Cell List* IE.] [1.28Mcps TDD - The Node B shall include the *Semi-Persistent scheduling Capability LCR* IE set to "Semi-Persistent scheduling Capable" for every semi-persistent scheduling Capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *Continuous Packet Connectivity DRX Capability LCR* IE set to "Continuous Packet Connectivity DRX Capability Capable" for Continuous Packet Connectivity DRX Capability Capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *MIMO Capability* IE set to "MIMO Capable" for every MIMO-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *SixtyfourQAM DL and MIMO Combined Capability* IE set to "SixtyfourQAM DL and MIMO Combined Capable" when Combined SixtyfourQAM DL and MIMO is supported for every Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable.] [FDD - The Node B shall include the *Enhanced UE DRX Capability* IE set to "Enhanced UE DRX Capable" for every Enhanced UE DRX capable Local Cell.] [1.28Mcps TDD - The Node B shall include the *Cell Portion Capability LCR* IE set to "Cell Portion Capable" for every Cell Portion Capable Local Cell.] [FDD - The Node B shall include the *MIMO Power Offset For S-CPICH Capability* IE set to "S-CPICH Power Offset Capable" for every MIMO-capable Local Cell able to transmit S-CPICH at a power offset from P-CPICH.] [FDD - The Node B shall include the *TX Diversity on DL Control Channels by MIMO UE Capability* IE set to "DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable" for every MIMO-capable Local Cell able to support DL control channels in transmit diversity for MIMO UEs when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7]).] [FDD - The Node B shall include the *Single Stream MIMO Capability* IE set to "Single Stream MIMO Capable" for every Single Stream MIMO capable Local Cell.] [FDD - The Node B shall include the *Dual Band Capability Info* IE and set the *Dual Band Capability* IE value to "Dual Band Capable" for every Dual Band HS-DSCH operation capable Local Cell, and set the *Dual Band E-DCH Capability* IE value to "Dual Band Capable" for every Dual Band E-DCH operation capable Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multiple dual band carrier operation (TS 25.133 [22]) (same sector) that can act as secondary serving HS-DSCH shall be listed in the *Possible Secondary Serving Cell List* IE. For each cell in the *Possible Secondary Serving Cell List* IE that is Multi Band E-DCH Capable, as indicated in the *Dual Band E-DCH Capability* IE for that cell, and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the *Multicell E-DCH Restriction* IE set to "TRUE" in the *Possible Secondary Serving Cell List* IE.] [FDD - The Node B shall include the *Cell Capability Container* IE if the Local Cell is capable of at least one feature listed in 9.2.2.129 and indicate the capabilities listed in 9.2.2.129 for the local cell.] [1.28Mcps TDD - The Node B shall include the *TS0 Capability LCR* IE set to "TS0 Capable" for every TS0 Capable Local Cell.] [FDD - For every MIMO-capable and/or Single Stream MIMO Capable Local Cell the Node B may include the *Precoding Weight Set Restriction* IE set to "Preferred", if configuration of the precoding weight set restriction defined in TS 25.331 [18] is preferred.] [1.28Mcps TDD - The Node B shall include the *Cell Capability Container TDD LCR* IE if the Local Cell is capable of at least one feature listed in 9.2.3.115 and indicate the capabilities listed in 9.2.3.115 for the local cell.] [1.28Mcps TDD - The Node B shall include *MU-MIMO Capability Container* IE if the Local Cell is capable of at least one feature listed in 9.2.3.119 and indicate the capabilities listed in 9.2.3.119 for the local cell.] [1.28Mcps TDD - The Node B shall include the *Adaptive Special Burst* + +*Power Capability LCR* IE set to "Adaptive Special Burst Power Capable" for every Adaptive Special Burst Power Capable Local Cell.] + +[TDD - The Node B shall include the *Reference Clock Availability* IE to indicate the availability of a Reference clock connected to the Local Cell.] + +If the Node B internal resources are pooled for a group of cells, the Node B shall include one *Local Cell Group Information* IE containing the Node B internal resource capacity and the consumption laws per group of cells [FDD - , including also the *E-DCH Capacity consumption Law* IE, if E-DCH is supported] [TDD - , including also the *E-DCH TDD Capacity Consumption Law* IE, if E-DCH is supported]. If the *UL Capacity Credit* IE is not present in the *Local Cell Group Information* IE, then the internal resource capabilities of the Node B for the Local Cell Group are modelled as shared resources between Uplink and Downlink. + +If the Node B internal power resources are pooled for a group of Local Cells, the Node B shall include one *Power Local Cell Group Information* IE containing the Maximum DL Power Capability for each Power Local Cell Group for which this value is known by the Node B. In this case, the Node B shall also include the *Maximum DL Power Capability* IE in the *Local Cell Information* IE for all the Local Cells belonging to a Power Local Cell Group reported in the *Power Local Cell Group Information* IE. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group. + +The Node B shall include, for each local cell present in the Node B, the Node B internal resource capability and consumption laws within the *Local Cell Information* IE [FDD - , including also the *E-DCH Capacity Consumption Law*, if E-DCH is supported] [TDD - , including also the *E-DCH TDD Capacity Consumption Law* IE, if E-DCH is supported]. If the *UL Capacity Credit* IE is not present in the *Local Cell Information* IE, then the internal resource capabilities of the local cell are modelled as shared resources between Uplink and Downlink. If the Local Cell utilises Node B internal resource capabilities that are pooled for several Local Cell(s), the *Local Cell Group ID* IE shall contain the identity of the used Local Cell Group. If the Local Cell utilises Node B internal power resources that are pooled for several Local Cells, the *Power Local Cell Group ID* IE shall contain the identity of the concerned Power Local Cell Group. + +The Node B shall include one *Cell Information* IE for each cell in the Node B and information about all common transport channels and all common physical channels for each cell. If a *Configuration Generation ID* IE for a cell can not be trusted, the Node B shall set this *Configuration Generation ID* IE = "0". The Node B shall include the *HS-DSCH Resources Information* IE for every Cell which has been configured with HS-DSCH resources. [FDD - The Node B shall include the *E-DCH Resources Information* IE for every Cell which has been configured with E-DCH resources.] [TDD - The Node B shall include the *E-DCH Resources Information* IE and the [3.84Mcps TDD - *E-RUCCH Information* IE] [7.68Mcps TDD - *E-RUCCH Information* IE] for every cell which has been configured with E-DCH resources.] + +[1.28Mcps TDD - The Node B may include the *UpPCH Information LCR* IE for each frequency on which the UpPCH channel is not configured in the timeslot of UpPTS.] + +[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the *UARFCN* IE in the *HS-DSCH Resources Information* IE to report the status of the HS-DSCH resources on the indicated frequency, the Node B may also not include any *UARFCN* IE in the *HS-DSCH Resources Information* IE to report the status of the HS-DSCH resources for the whole cell.] + +[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the *UARFCN* IE in the *E-DCH Resources Information* IE to report the status of the E-DCH resources on the indicated frequency, the Node B may also not include any *UARFCN* IE in the *E-DCH Resources Information* IE to report the status of the E-DCH resources for the whole cell.] + +The Node B shall also include one *Communication Control Port Information* IE for each Communication Control Port in the Node B. + +[1.28Mcps TDD - For a multi-frequency cell, the Node B should report the status of the resources used for each frequency. A reporting method can be found in Annex E.] + +### 8.2.7.3 Unsuccessful Operation + +![Sequence diagram for Audit procedure, Unsuccessful Operation. A CRNC sends an AUDIT REQUEST message to Node B. Node B responds with an AUDIT FAILURE message.](bccc028d0e75bc30c41528056f581545_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: AUDIT REQUEST + CRNC->>Node B: AUDIT REQUEST + Note left of Node B: AUDIT FAILURE + Node B-->>CRNC: AUDIT FAILURE + +``` + +Sequence diagram for Audit procedure, Unsuccessful Operation. A CRNC sends an AUDIT REQUEST message to Node B. Node B responds with an AUDIT FAILURE message. + +**Figure 10A: Audit procedure, Unsuccessful Operation** + +If the Node B cannot perform an audit of the configuration and status of the logical resources, it shall send a AUDIT FAILURE message with the *Cause* IE set to an appropriate value. + +### 8.2.7.4 Abnormal Conditions + +If the Node B receives the AUDIT REQUEST message with the *Start Of Audit Sequence Indicator* IE set to "not start of audit sequence" and there is no ongoing audit sequence, the Node B shall send the AUDIT FAILURE message with the appropriate cause value. + +## 8.2.8 Common Measurement Initiation + +### 8.2.8.1 General + +This procedure is used by a CRNC to request the initiation of measurements on common resources in a Node B. + +### 8.2.8.2 Successful Operation + +![Sequence diagram for Common Measurement Initiation procedure, Successful Operation. A CRNC sends a COMMON MEASUREMENT INITIATION REQUEST message to Node B. Node B responds with a COMMON MEASUREMENT INITIATION RESPONSE message.](1ca688982d625c3b8a8e382b675de466_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON MEASUREMENT INITIATION REQUEST + CRNC->>Node B: COMMON MEASUREMENT INITIATION REQUEST + Note left of Node B: COMMON MEASUREMENT INITIATION RESPONSE + Node B-->>CRNC: COMMON MEASUREMENT INITIATION RESPONSE + +``` + +Sequence diagram for Common Measurement Initiation procedure, Successful Operation. A CRNC sends a COMMON MEASUREMENT INITIATION REQUEST message to Node B. Node B responds with a COMMON MEASUREMENT INITIATION RESPONSE message. + +**Figure 11: Common Measurement Initiation procedure, Successful Operation** + +The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall initiate the requested measurement according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications. + +[TDD - If the [3.84Mcps TDD - *Time Slot* IE] [1.28Mcps TDD - *Time Slot LCR* IE] is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested time slot individually.] + +[1.28Mcps TDD - If *Time Slot LCR* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all the available time slots in the frequency.] + +[1.28Mcps TDD - If the *Common Measurement Type* IE is not set to "HS-DSCH Provided Bit Rate" and *UARFCN* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all the frequencies in the cell.] [1.28Mcps TDD - If the *Common Measurement Type* IE is not set to "HS-DSCH Provided Bit Rate" and neither *UARFCN* IE nor *Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all time slots in all frequencies in which the measurements are applicable.] + +[1.28Mcps TDD - If *Additional Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested additional time slots indicated in the *Additional Time Slot LCR* IE.] + +[1.28Mcps TDD - If the *UpPCH Position LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, and the *Common Measurement Type* IE is set to "UpPCH interference", the measurement request shall apply to the requested UpPCH position individually.] + +If the *Common Measurement Type* IE is not set to "SFN-SFN Observed Time Difference" and the *SFN Reporting Indicator* IE is set to "FN Reporting Required", the *SFN* IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the *Report Characteristics* IE is set to "On Demand". The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference", the *SFN Reporting Indicator* IE shall be ignored. + +[FDD - If the *Common Measurement Type* IE is set to "Received Scheduled E-DCH Power Share" and the *RTWP\* Reporting Indicator* IE is set to "RTWP\* Reporting Required", the *RTWP\* Value* IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the *Report Characteristics* IE is set to "On Demand". This is the received total wideband power (RTWP) determined for the same time period during which RSEPS is determined.] + +[FDD - If the *Common Measurement Type* IE is set to "Received Scheduled E-DCH Power Share for Cell Portion" and the *RTWP\*for Cell Portion Reporting Indicator* IE is set to "RTWP\* Reporting Required", the *RTWP\* Value* IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the *Report Characteristics* IE is set to "On Demand".] + +[1.28Mcps TDD - For a multi-frequency cell, if *Common Measurement Type* IE is set to "HS-DSCH Provided Bit Rate", and the *UARFCN* IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the indicated frequency, if *Common Measurement Type* IE is set to "HS-DSCH Provided Bit Rate", and the *UARFCN* IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the whole cell.] + +[FDD - If the *Common Measurement Type* IE is set to "E-DCH RACH Report", and the *Concurrent Deployment of 2ms and 10ms TTI* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the *2ms Granted E-DCH RACH Resources* IE, *2ms Overridden E-DCH RACH Resources* IE and *2ms Denied E-DCH RACH Resources* IE should be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT INITIATION RESPONSE message, the latter only in the case the *Report Characteristics* IE is set to "On Demand".] + +#### Common measurement type: + +If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference", then the Node B shall initiate the SFN-SFN Observed Time Difference measurements between the reference cell identified by *C-ID* IE and the neighbouring cells identified by the *UTRAN Cell Identifier(UC-Id)* IE in the *Neighbouring Cell Measurement Information* IE. + +If the *Common Measurement Type* IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall initiate the UTRAN GANSS Timing of Cell Frames measurements using the GNSS system time identified by *GANSS Time ID* IE included in the COMMON MEASUREMENT INITIATION REQUEST message. + +- If the *Common Measurement Type* IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and the *GANSS Time ID* IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall assume that the corresponding GANSS time is "Galileo" system time. + +[FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion", "Transmitted Carrier Power for Cell Portion", [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion"], "HS-DSCH Required Power for Cell Portion", "HS-DSCH Provided Bit Rate for Cell Portion"[1.28Mcps TDD - , "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the Node B shall initiate the corresponding measurements for all the cell portions which are configured under the cell indicated by *C-ID* IE in the COMMON MEASUREMENT INITIATION REQUEST message.] + +### Report characteristics: + +The *Report Characteristics* IE indicates how the reporting of the measurement shall be performed. See also Annex B. + +If the *Report Characteristics* IE is set to "On Demand" and if the *SFN* IE is not provided, the Node B shall return the result of the requested measurement immediately. If the *SFN* IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). + +If the *Report Characteristics* IE is set to "Periodic", the Node B shall periodically initiate a Common Measurement Reporting procedure for this measurement, with the requested report frequency. If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference", all the available measurement results shall be reported in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE in the *SFN-SFN Measurement Value Information* IE and the Node B shall indicate in the *Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE all the remaining neighbouring cells with no measurement result available in the Common Measurement Reporting procedure. If the *SFN* IE is provided, it indicates the frame for which the first measurement value of a periodic reporting shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). + +If the *Report Characteristics* IE is set to "Event A", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero for the hysteresis time. If the *Common Measurement Type* IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion" or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion"][1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"]], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "Event B", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero for the hysteresis time. If the *Common Measurement Type* IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion" or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion"][1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"]], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "Event C", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next C event reporting for the same measurement cannot be initiated before the rising time specified by the *Measurement Change Time* IE has elapsed since the previous event reporting. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"]], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "Event D", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next D event reporting for the same measurement cannot be initiated before the falling time specified by the *Measurement Change Time* IE has elapsed since the previous event reporting. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH + +transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "Event E", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises above the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the *Report Periodicity* IE is provided, the Node B shall initiate the Common Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity falls below the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Common Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the Node B shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. If the *Common Measurement Type* IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"][1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion" or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "Event F", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls below the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the *Report Periodicity* IE is provided the Node B shall also initiate the Common Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity rises above the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Common Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the Node B shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. If the *Common Measurement Type* IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"][1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion" or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.] + +If the *Report Characteristics* IE is set to "On Modification" and if the *SFN* IE is not provided, the Node B shall report the result of the requested measurement immediately. If the *SFN* IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). Then, the Node B shall initiate the Common Measurement Reporting procedure in accordance to the following conditions: + +1. If the *Common Measurement Type* IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning": + - If the *TUTRAN-GPS Change Limit* IE is included in the *TUTRAN-GPS Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of TUTRAN-GPS value ( $F_n$ ). The Node B shall initiate the Common Measurement Reporting procedure and set $n$ equal to zero when the absolute value of $F_n$ rises above the threshold indicated by the *TUTRAN-GPS Change Limit* IE. The change of TUTRAN-GPS value ( $F_n$ ) is calculated according to the following: + +$$F_n = 0 \text{ for } n = 0$$ + +$$F_n = (M_n - M_{n-1}) \bmod 37158912000000 - ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + F_{n-1}$$ + +$$\text{for } n > 0$$ + +$F_n$ is the change of the $T_{\text{UTRAN-GPS}}$ value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at $SFN_n$ . + +$M_{n-1}$ is the previous measurement result received after point C in the measurement model (TS 25.302 [25]), measured at $SFN_{n-1}$ . + +$M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [25]), after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$M_0$ is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered. + +- If the *Predicted TUTRAN-GPS Deviation Limit* IE is included in the *TUTRAN-GPS Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the $P_n$ and $F_n$ . The Node B shall initiate the Common Measurement Reporting procedure and set n equal to zero when $F_n$ rises above the threshold indicated by the *Predicted TUTRAN-GPS Deviation Limit* IE. The $P_n$ and $F_n$ are calculated according to the following: + +$$P_n = b \text{ for } n=0$$ + +$$P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096)/100 + ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + P_{n-1}) \bmod 37158912000000 \text{ for } n>0$$ + +$$F_n = \min((M_n - P_n) \bmod 37158912000000, (P_n - M_n) \bmod 37158912000000) \text{ for } n>0$$ + +$P_n$ is the predicted $T_{\text{UTRAN-GPS}}$ value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$a$ is the last reported $T_{\text{UTRAN-GPS}}$ Drift Rate value. + +$b$ is the last reported $T_{\text{UTRAN-GPS}}$ value. + +$F_n$ is the deviation of the last measurement result from the predicted $T_{\text{UTRAN-GPS}}$ value ( $P_n$ ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at $SFN_n$ . + +$M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [25]), after the first Common Measurement Reporting at initiation or after the last event was triggered. + +The $T_{\text{UTRAN-GPS}}$ Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]). + +2. If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference": + +- If the *SFN-SFN Change Limit* IE is included in the *SFN-SFN Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of $SFN-SFN$ value ( $F_n$ ). The Node B shall initiate the Common Measurement Reporting procedure in order to report the particular $SFN-SFN$ measurement which has triggered the event and set n equal to zero when $F_n$ rises above the threshold indicated by the *SFN-SFN Change Limit* IE. The change of the $SFN-SFN$ value is calculated according to the following: + +$$F_n = 0 \text{ for } n=0$$ + +$$[FDD - F_n = (M_n - a) \bmod 614400 \text{ for } n>0]$$ + +$$[TDD - F_n = (M_n - a) \bmod 40960 \text{ for } n>0]$$ + +$F_n$ is the change of the $SFN-SFN$ value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$a$ is the last reported SFN-SFN. + +$M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at SFN $_n$ . + +$M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [25]) after the first Common Measurement Reporting at initiation or after the last event was triggered. + +- If the *Predicted SFN-SFN Deviation Limit* IE is included in the *SFN-SFN Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the $P_n$ and $F_n$ . The Node B shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set $n$ equal to zero when the $F_n$ rises above the threshold indicated by the *Predicted SFN-SFN Deviation Limit* IE. The $P_n$ and $F_n$ are calculated according to the following: + +$$P_n = b \text{ for } n=0$$ + +$$[FDD - P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096)/100 + P_{n-1}) \bmod 614400 \quad \text{for } n>0]$$ + +$$[FDD - F_n = \min((M_n - P_n) \bmod 614400, (P_n - M_n) \bmod 614400) \quad \text{for } n>0]$$ + +$$[TDD - P_n = ((a/16) * (15*(SFN_n - SFN_{n-1}) \bmod 4096 + (TS_n - TS_{n-1}))/1500 + P_{n-1}) \bmod 40960 \quad \text{for } n>0]$$ + +$$[TDD - F_n = \min((M_n - P_n) \bmod 40960, (P_n - M_n) \bmod 40960) \quad \text{for } n>0]$$ + +$P_n$ is the predicted *SFN-SFN* value when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$a$ is the last reported SFN-SFN Drift Rate value. + +$b$ is the last reported SFN-SFN value. + +$abs$ denotes the absolute value. + +$F_n$ is the deviation of the last measurement result from the predicted *SFN-SFN* value ( $P_n$ ) when $n$ measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$M_n$ is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at [TDD - the Time Slot $TS_n$ ] of the Frame $SFN_n$ . + +$M_1$ is the first measurement result received after point C in the measurement model (TS 25.302 [25]) after the first Common Measurement Reporting at initiation or after the last event was triggered. + +The SFN-SFN Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]). + +3. If the *Common Measurement Type* IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning": + +- If the *TUTRAN-GANSS Change Limit* IE is included in the *TUTRAN-GANSS Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of TUTRAN-GANSS value ( $F_n$ ). The Node B shall initiate the Common Measurement Reporting procedure and set $n$ equal to zero when the absolute value of $F_n$ rises above the threshold indicated by the *TUTRAN-GANSS Change Limit* IE. The change of TUTRAN-GANSS value ( $F_n$ ) is calculated according to the following: + +$$F_n = 0 \text{ for } n=0$$ + +$$F_n = (GAM_n - GAM_{n-1}) \bmod 5308416000000 - ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + F_{n-1}$$ + +$$\text{for } n>0$$ + +$F_n$ is the change of the TUTRAN-GANSS value expressed in unit [1/16 chip] when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$GAM_n$ is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_n$ . + +$GAM_{n-1}$ is the previous GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_{n-1}$ . + +$GAM_1$ is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$GAM_0$ is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered. + +GANSS measurement model is the timing between cell j and GANSS Time Of Day. $T_{UE-GANSSj}$ is defined as the time of occurrence of a specified UTRAN event according to GANSS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for $T_{UE-GANSSj}$ shall be the antenna connector of the UE. + +- If the Predicted *TUTRAN-GANSS Deviation Limit* IE is included in the *TUTRAN-GANSS Measurement Threshold Information* IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the $P_n$ and $F_n$ . The Node B shall initiate the Common Measurement Reporting procedure and set $n$ equal to zero when $F_n$ rises above the threshold indicated by the *Predicted TUTRAN-GANSS Deviation Limit* IE. The $P_n$ and $F_n$ are calculated according to the following: + +$$P_n = b \text{ for } n=0$$ + +$$P_n = ((a/16) * ((SFN_n - SFN_{n-1}) \bmod 4096)/100 + ((SFN_n - SFN_{n-1}) \bmod 4096) * 10 * 3.84 * 10^3 * 16 + P_{n-1}) \bmod 5308416000000 \text{ for } n > 0$$ + +$$F_n = \min((GAM_n - P_n) \bmod 5308416000000, (P_n - GAM_n) \bmod 5308416000000) \text{ for } n > 0$$ + +$P_n$ is the predicted $T_{UTRAN-GANSS}$ value when $n$ measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$a$ is the last reported $T_{UTRAN-GANSS}$ Drift Rate value. + +$b$ is the last reported $T_{UTRAN-GANSS}$ value. + +$F_n$ is the deviation of the last measurement result from the predicted $T_{UTRAN-GANSS}$ value ( $P_n$ ) when $n$ measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. + +$GAM_n$ is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at $SFN_n$ . + +$GAM_1$ is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered. + +The $T_{UTRAN-GANSS}$ Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]). + +If the *Report Characteristics* IE is not set to "On Demand", the Node B is required to perform reporting for a common measurement object, in accordance with the conditions provided in the COMMON MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no common measurement object(s) for which a measurement is defined exists anymore, the Node B shall terminate the measurement locally, i.e. without reporting this to the CRNC. + +If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the Node B shall initiate the Common Measurement Reporting procedure immediately, and then continue with the measurements as specified in the COMMON MEASUREMENT INITIATION REQUEST message. + +#### Higher layer filtering: + +The *Measurement Filter Coefficient* IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting. + +The averaging shall be performed according to the following formula. + +The variables in the formula are defined as follows: + +$F_n$ is the updated filtered measurement result + +$F_{n-1}$ is the old filtered measurement result + +$M_n$ is the latest received measurement result from physical layer measurements, the unit used for $M_n$ is the same unit as the reported unit in the COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for $F_n$ ) + +$a = 1/2^{(k/2)}$ , where $k$ is the parameter received in the *Measurement Filter Coefficient* IE. If the *Measurement Filter Coefficient* IE is not present, $a$ shall be set to 1 (no filtering) + +In order to initialise the averaging filter, $F_0$ is set to $M_1$ when the first measurement result from the physical layer measurement is received. + +#### Common measurement accuracy: + +If the *Common Measurement Type* IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning", then the Node B shall use the *UTRAN GPS Timing Measurement Accuracy Class* IE included in the *Common Measurement Accuracy* IE according to the following: + +- If the *UTRAN GPS Timing Measurement Accuracy Class* IE indicates "Class A", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes A, B and C. +- If the *UTRAN GPS Timing Measurement Accuracy Class* IE indicates "Class B", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes B and C. +- If the *UTRAN GPS Timing Measurement Accuracy Class* IE indicates "Class C", then the Node B shall perform the measurements with the accuracy according to class C. + +If the *Common Measurement Type* IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall use the *TUTRAN-GANSS Measurement Accuracy Class* IE included in the *Common Measurement Accuracy* IE according to the following: + +- If the *TUTRAN-GANSS Measurement Accuracy Class* IE indicates "Class A", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes A, B and C. +- If the *TUTRAN-GANSS Measurement Accuracy Class* IE indicates "Class B", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes B and C. +- If the *TUTRAN-GANSS Measurement Accuracy Class* IE indicates "Class C", then the Node B shall perform the measurements with the accuracy according to class C. + +#### Measurement Recovery Behavior: + +If the *Measurement Recovery Behavior* IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall, if Measurement Recovery Behavior is supported, include the *Measurement Recovery Support Indicator* IE in the COMMON MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.2.9.2. + +#### [FDD - Noise Floor Reporting:] + +[FDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power" and if the *Reference Received Total Wide Band Power Reporting* IE is included in the same COMMON MEASUREMENT INITIATION REQUEST message, the Node B may include the *Reference Received Total Wide Band Power* IE in the message used to report the common measurement.] + +[FDD - If the *Reference Received Total Wide Band Power Reporting* IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall if supported, include the *Reference Received Total Wide Band Power Support Indicator* IE or the *Reference Received Total Wide Band Power* IE in the COMMON MEASUREMENT INITIATION RESPONSE.] + +#### Response message: + +If the Node B was able to initiate the measurement requested by the CRNC, it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message sent over the Node B Control Port. The message shall include the same Measurement ID that was used in the measurement request. Only in the case where the *Report Characteristics* IE is set to "On Demand" or "On Modification", the COMMON MEASUREMENT INITIATION RESPONSE message shall include the measurement result and also the *Common Measurement Achieved Accuracy* IE if the *Common Measurement Type* IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning" or "UTRAN GANSS Timing of Cell Frames for UE positioning". + +[1.28Mcps TDD –If *Time Slot LCR* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all the available time slots in the frequency.] + +[1.28Mcps TDD - If the *Common Measurement Type* IE is not set to "HS-DSCH Provided Bit Rate" and *UARFCN* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all the frequencies in the cell.] + +[1.28Mcps TDD - If the *Common Measurement Type* IE is not set to "HS-DSCH Provided Bit Rate" and neither *UARFCN* IE nor *Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all available time slots in all frequencies.] + +[1.28Mcps TDD - If *Additional Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of the additional time slot (s) should be included in the COMMON MEASUREMENT INITIATION RESPONSE message.] + +If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference" and the *Report Characteristics* IE is set to "On Demand" or "On Modification", all the available measurement results shall be reported in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE in the *SFN-SFN Measurement Value Information* IE and the Node B shall indicate in the *Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE all the remaining neighbouring cells with no measurement result available in the COMMON MEASUREMENT INITIATION RESPONSE message. For all available measurement results, the Node B shall include in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE the *SFN-SFN Quality* IE and the *SFN-SFN Drift Rate Quality* IE, if available. + +If the *Common Measurement Type* IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning" and the *Report Characteristics* IE is set to "On Demand" or "On Modification", the Node B shall include in the *TUTRAN-GPS Measurement Value Information* IE the *TUTRAN-GPS Quality* IE and the *TUTRAN-GPS Drift Rate Quality* IE, if available. + +[FDD and 1.28Mcps TDD - If the *Common Measurement Type* IE is set to "Received Total Wide Band Power for Cell Portion", "Transmitted Carrier Power for Cell Portion", [FDD -"Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"], "HS-DSCH Required Power for Cell Portion" [1.28Mcps TDD – , "UL Timeslot ISCP for Cell Portion", "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"] or "HS-DSCH Provided Bit Rate for Cell Portion" and the *Report Characteristics* IE is set to "On Demand", all the available measurement results for each cell portion shall be included in the COMMON MEASUREMENT INITIATION RESPONSE message.] + +If the *Common Measurement Type* IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and the *Report Characteristics* IE is set to "On Demand" or "On Modification", the Node B shall include in the *TUTRAN-GANSS Measurement Value Information* IE, the *TUTRAN-GANSS Quality* IE and the *TUTRAN-GANSS Drift Rate Quality* IE, if available. + +#### 8.2.8.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Common Measurement Initiation procedure. A CRNC sends a COMMON MEASUREMENT INITIATION REQUEST to Node B, and Node B responds with a COMMON MEASUREMENT INITIATION FAILURE.](a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON MEASUREMENT INITIATION REQUEST + CRNC->>Node B: COMMON MEASUREMENT INITIATION REQUEST + Note left of Node B: COMMON MEASUREMENT INITIATION FAILURE + Node B-->>CRNC: COMMON MEASUREMENT INITIATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Common Measurement Initiation procedure. A CRNC sends a COMMON MEASUREMENT INITIATION REQUEST to Node B, and Node B responds with a COMMON MEASUREMENT INITIATION FAILURE. + +Figure 12: Common Measurement Initiation procedure, Unsuccessful Operation + +If the requested measurement cannot be initiated [1.28Mcps TDD-in any time slot], the Node B shall send a COMMON MEASUREMENT INITIATION FAILURE message over the Node B Control Port. The message shall include the same Measurement ID that was used in the COMMON MEASUREMENT INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +**Radio Network Layer Cause:** + +- Measurement not supported for the object. +- Measurement Temporarily not Available + +#### 8.2.8.4 Abnormal Conditions + +The allowed combinations of the Common Measurement Type received in the *Common Measurement Type* IE and the Common Measurement Object Type received in the COMMON MEASUREMENT INITIATION REQUEST message are shown in the table below. For not allowed combinations, the Node B shall regard the Common Measurement Initiation procedure as failed. + +**Table 3a: Allowed Common Measurement Type and Common Measurement Object Type combinations** + +| Common Measurement Type | Common Measurement Object Type | | | | +|-------------------------|--------------------------------|------|------------------------|------------| +| | Cell | RACH | Power Local Cell Group | E-DCH RACH | +| | | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---|----------|---| +| Received Total Wide Band Power | X | | | | +| Transmitted Carrier Power | X | | | | +| Acknowledged PRACH Preambles | | X | | | +| E-DCH RACH Report | | | | X | +| UL Timeslot ISCP | X | | | | +| UTRAN GPS Timing of Cell Frames for UE Positioning | X | | | | +| SFN-SFN Observed Time Difference | X | | | | +| [TDD - Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission]
[FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission] | X | | | | +| HS-DSCH Required Power | X | | | | +| HS-DSCH Provided Bit Rate | X | | | | +| Received Total Wide Band Power for Cell Portion | FDD and 1.28Mcps
TDD only | | | | +| Transmitted Carrier Power for Cell Portion | FDD and 1.28Mcps
TDD only | | | | +| Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion | FDD only | | | | +| UpPCH interference | 1.28 Mcps
TDD only | | | | +| DL Transmission Branch Load | FDD only | | FDD only | | +| HS-DSCH Required Power for Cell Portion | FDD and 1.28Mcps
TDD only | | | | +| HS-DSCH Provided Bit Rate for Cell Portion | FDD and 1.28Mcps
TDD only | | | | +| E-DCH Provided Bit Rate | X | | | | +| E-DCH Non-serving Relative Grant Down Commands | FDD only | | | | +| Received Scheduled E-DCH Power Share | FDD only | | | | +| Received Scheduled E-DCH Power Share for Cell Portion | FDD only | | | | +| UTRAN GANSS Timing of Cell Frames for UE Positioning | X | | | | +| UL Timeslot ISCP for Cell Portion | 1.28Mcps
TDD only | | | | +| Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion | 1.28Mcps
TDD only | | | | +| E-DCH Provided Bit Rate for Cell Portion | 1.28Mcps
TDD only | | | | +| UpPCH interference for Cell Portion | 1.28Mcps
TDD only | | | | + +[TDD - If the Common Measurement Type requires the Time Slot Information but the [3.84Mcps TDD and 7.68Mcps TDD - *Time Slot IE*] [1.28Mcps TDD - *Time Slot LCR IE*] is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed.] + +[1.28Mcps TDD - For a multi-frequency cell, if the *Additional Time Slot LCR IE* is present in the COMMON MEASUREMENT INITIATION REQUEST message, only on-demand and period measurement could be used, otherwise, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.] + +If the COMMON MEASUREMENT INITIATION REQUEST message contains the *SFN-SFN Measurement Threshold Information IE* (in the *Measurement Threshold IE* contained in the *Report Characteristics IE*) and it does not contain at least one IE, the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message. + +If the COMMON MEASUREMENT INITIATION REQUEST message contains the *TUTRAN-GPS Measurement Threshold Information* IE (in the *Measurement Threshold* IE contained in the *Report Characteristics* IE) and it does not contain at least one IE, the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message. + +If the *Common Measurement Type* IE is set to "SFN-SFN Observed Time Difference", but the *Neighbouring Cell Measurement Information* IE is not received in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed. + +If the *Common Measurement Type IE* is set to "UTRAN GPS Timing of Cell Frames for UE Positioning", but the *TUTRAN-GPS Measurement Accuracy Class IE* in the *Common Measurement Accuracy IE* is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed. + +If the *Common Measurement Type IE* is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", but the *TUTRAN-GANSS Measurement Accuracy Class IE* in the *Common Measurement Accuracy IE* is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed. + +[FDD - If the COMMON MEASUREMENT INITIATION REQUEST message contains the *Reference Received Total Wide Band Power Reporting* IE and it does not contain the *Common Measurement Type* IE set to "Received Total Wide Band Power", the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.] + +The allowed combinations of the Common Measurement Type and Report Characteristics Type are shown in the table below marked with "X". For not allowed combinations, the Node B shall regard the Common Measurement Initiation procedure as failed. + +**Table 4: Allowed Common Measurement Type and Report Characteristics Type combinations** + +| Common Measurement Type | Report Characteristics Type | | | | | | | | | +|-------------------------|-----------------------------|----------|---------|---------|---------|---------|---------|---------|-----------------| +| | On Demand | Periodic | Event A | Event B | Event C | Event D | Event E | Event F | On Modification | + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---| +| Received Total Wide Band Power | X | X | X | X | X | X | X | | +| Transmitted Carrier Power | X | X | X | X | X | X | X | | +| Acknowledged PRACH Preambles | X | X | X | X | X | X | X | | +| E-DCH RACH Report | X | X | X | X | X | X | X | | +| UL Timeslot ISCP | X | X | X | X | X | X | X | | +| UTRAN GPS Timing of Cell Frames for UE Positioning | X | X | | | | | | X | +| SFN-SFN Observed Time Difference | X | X | | | | | | X | +| [TDD - Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission]
[FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission] | X | X | X | X | X | X | X | | +| HS-DSCH Required Power | X | X | X | X | | X | X | | +| HS-DSCH Provided Bit Rate | X | X | | | | | | | +| [FDD and 1.28Mcps TDD - Received Total Wide Band Power for Cell Portion] | X | X | X | X | X | X | X | | +| [FDD and 1.28Mcps TDD - Transmitted Carrier Power for Cell Portion] | X | X | X | X | X | X | X | | +| [FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion] | X | X | X | X | X | X | X | | +| UpPTS interference | X | X | X | X | X | X | X | | +| UpPCH interference for Cell Portion | X | X | X | X | X | X | X | | +| DL Transmission Branch Load | X | X | X | X | | X | X | | +| [FDD and 1.28Mcps TDD - HS-DSCH Required Power for Cell Portion] | X | X | X | X | | X | X | | +| [FDD and 1.28Mcps TDD - HS-DSCH Provided Bit Rate for Cell Portion] | X | X | | | | | | | +| E-DCH Provided Bit Rate | X | X | | | | | | | +| E-DCH Provided Bit Rate for Cell Portion | X | X | | | | | | | +| E-DCH Non-serving Relative Grant Down Commands | X | X | X | X | | X | X | | +| Received Scheduled E-DCH Power Share | X | X | X | X | X | X | X | | + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---|---| +| [FDD - Received Scheduled E-DCH Power Share for Cell Portion] | X | X | X | X | X | X | X | X | | +| UTRAN GANSS Timing of Cell Frames for UE Positioning | X | X | | | | | | | X | +| [1.28Mcps TDD - UL Timeslot ISCP for Cell Portion] | X | X | X | X | X | X | X | X | | +| [1.28Mcps TDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion] | X | X | X | X | X | X | X | X | | + +If the *SFN* IE is included in the COMMON MEASUREMENT INITIATION REQUEST message and the *Report Characteristics* IE is other than "Periodic", "On Demand" or "On Modification", the Node B shall regard the Common Measurement Initiation procedure as failed. + +## 8.2.9 Common Measurement Reporting + +### 8.2.9.1 General + +This procedure is used by the Node B to report the result of measurements requested by the CRNC with the Common Measurement Initiation procedure. + +### 8.2.9.2 Successful Operation + +![Sequence diagram showing the Common Measurement Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'COMMON MEASUREMENT REPORT' centered above the arrow.](e42cc691d9c7c4d23e66b04472bb494e_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: COMMON MEASUREMENT REPORT + Node B->>CRNC: COMMON MEASUREMENT REPORT + +``` + +Sequence diagram showing the Common Measurement Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'COMMON MEASUREMENT REPORT' centered above the arrow. + +**Figure 13: Common Measurement Reporting procedure, Successful Operation** + +If the requested measurement reporting criteria are met, the Node B shall initiate the Common Measurement Reporting procedure. The COMMON MEASUREMENT REPORT message shall use the Node B Control Port. + +The *Measurement ID* IE shall be set to the Measurement ID provided by the CRNC when initiating the measurement with the Common Measurement Initiation procedure. + +[1.28Mcps TDD –If *Time Slot LCR* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all the available time slots in the frequency should be included in the COMMON MEASUREMENT INITIATION REPORT message.] + +[1.28Mcps TDD - If *UARFCN* IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all the frequencies in the cell should be included in the COMMON MEASUREMENT INITIATION REPORT message.] + +[1.28Mcps TDD - If neither *UARFCN* IE nor *Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all available time slots in all frequencies should be included in the COMMON MEASUREMENT INITIATION REPORT message.] + +[1.28Mcps TDD - If *Additional Time Slot LCR* IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of the additional time slot (s) should be included in the COMMON MEASUREMENT INITIATION REPORT message.] + +If the achieved measurement accuracy does not fulfil the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the *Common Measurement Value Information* IE shall indicate Measurement not Available. If the Node B was configured to perform the Measurement Recovery Behavior, the Node B shall indicate Measurement Available to the CRNC when the achieved measurement accuracy again fulfils the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) and include the *Measurement Recovery Report Indicator* IE in the COMMON MEASUREMENT REPORT message if the requested measurement reporting criteria are not met. + +For measurements included in the *Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information* IE, the Node B shall include the *SFN-SFN Quality* IE and the *SFN-SFN Drift Rate Quality* IE if available. + +If the Common Measurement Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "UTRAN GPS Timing of Cell Frames for UE Positioning", then the Node B shall include in the *TUTRAN-GPS Measurement Value Information* IE the *TUTRAN-GPS Quality* IE and the *TUTRAN-GPS Drift Rate Quality* IE, if available. + +If the Common Measurement Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall include in the *TUTRAN-GANSS Measurement Value Information* IE the *TUTRAN-GANSS Quality* IE and the *TUTRAN-GANSS Drift Rate Quality* IE, if available. + +[FDD and 1.28Mcps TDD - For Received Total Wide Band Power for Cell Portion, Transmitted Carrier Power for Cell Portion, [FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion][1.28Mcps TDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion], HS-DSCH Required Power for Cell Portion, HS-DSCH Provided Bit Rate for Cell Portion[1.28Mcps TDD - , "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"], [FDD - Received Scheduled E-DCH Power Share for Cell Portion][1.28Mcps TDD - UL Timeslot ISCP for Cell Portion] measurements, all the available measurement results for each cell portion shall be included in the COMMON MEASUREMENT REPORT message.] + +If the Common Measurement Object Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "Cell" or "RACH", then the Node B, if supported, shall include the *C-ID* IE in the COMMON MEASUREMENT REPORT message. + +### 8.2.9.3 Abnormal Conditions + +- + +## 8.2.10 Common Measurement Termination + +### 8.2.10.1 General + +This procedure is used by the CRNC to terminate a measurement previously requested by the Common Measurement Initiation procedure. + +### 8.2.10.2 Successful Operation + +![Sequence diagram showing the Common Measurement Termination procedure. A horizontal arrow labeled 'COMMON MEASUREMENT TERMINATION REQUEST' points from the CRNC to the Node B.](bdb44cc8120caccddc2adf0c3db54261_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: COMMON MEASUREMENT TERMINATION REQUEST + CRNC->>Node B: COMMON MEASUREMENT TERMINATION REQUEST + +``` + +Sequence diagram showing the Common Measurement Termination procedure. A horizontal arrow labeled 'COMMON MEASUREMENT TERMINATION REQUEST' points from the CRNC to the Node B. + +**Figure 14: Common Measurement Termination procedure, Successful Operation** + +This procedure is initiated with a COMMON MEASUREMENT TERMINATION REQUEST message, sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall terminate reporting of common measurements corresponding to the received *Measurement ID IE*. + +### 8.2.10.3 Abnormal Conditions + +- + +## 8.2.11 Common Measurement Failure + +### 8.2.11.1 General + +This procedure is used by the Node B to notify the CRNC that a measurement previously requested by the Common Measurement Initiation procedure can no longer be reported. + +### 8.2.11.2 Successful Operation + +![Sequence diagram for Common Measurement Failure procedure, Successful Operation](01465752f3ac36c403672804f406a676_img.jpg) + +``` +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: COMMON MEASUREMENT FAILURE INDICATION + Node B->>CRNC: COMMON MEASUREMENT FAILURE INDICATION +``` + +A sequence diagram showing the interaction between a Node B and a CRNC. The Node B sends a message labeled "COMMON MEASUREMENT FAILURE INDICATION" to the CRNC. The CRNC is represented by a vertical line on the left, and the Node B by a vertical line on the right. The message arrow points from the Node B to the CRNC. + +Sequence diagram for Common Measurement Failure procedure, Successful Operation + +**Figure 15: Common Measurement Failure procedure, Successful Operation** + +This procedure is initiated with a COMMON MEASUREMENT FAILURE INDICATION message, sent from the Node B to the CRNC using the Node B Control Port, to inform the CRNC that a previously requested measurement can no longer be reported. The Node B has locally terminated the indicated measurement. + +### 8.2.11.3 Abnormal Conditions + +- + +## 8.2.12 Cell Setup + +### 8.2.12.1 General + +This procedure is used to set up a cell in the Node B. The CRNC takes the cell, identified via the *C-ID IE*, into service and uses the resources in the Node B identified via the *Local Cell ID IE*. + +### 8.2.12.2 Successful Operation + +![Sequence diagram for Cell Setup procedure, Successful Operation](1aa60e916522640d538e81fd202045b4_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CELL SETUP REQUEST + CRNC->>Node B: CELL SETUP REQUEST + Note right of Node B: CELL SETUP RESPONSE + Node B->>CRNC: CELL SETUP RESPONSE +``` + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC sends a message labeled "CELL SETUP REQUEST" to the Node B. The Node B responds with a message labeled "CELL SETUP RESPONSE" to the CRNC. The CRNC is represented by a vertical line on the left, and the Node B by a vertical line on the right. The first message arrow points from the CRNC to the Node B, and the second message arrow points from the Node B to the CRNC. + +Sequence diagram for Cell Setup procedure, Successful Operation + +**Figure 16: Cell Setup procedure, Successful Operation** + +The procedure is initiated with a CELL SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon Reception, the Node B shall reserve the necessary resources and configure the new cell according to the parameters given in the message. + +[FDD - If the CELL SETUP REQUEST message includes one or more *Secondary CPICH Information IE*, the Node B shall configure and activate the Secondary CPICH(s) in the cell according to received configuration data.] + +The *Maximum Transmission Power* IE value shall be stored in the Node B and, at any instance of time, the total maximum output power in the cell shall not be above this value. [1.28Mcps TDD - For a multi-frequency cell, at any instance of time, the total maximum output power for each frequency of the cell shall not be above this value.] + +[FDD - If the *Closed Loop Timing Adjustment Mode* IE is included in the CELL SETUP REQUEST message, the value shall be stored in the Node B and applied when closed loop Feed-Back mode diversity is used on DPCH.] + +[TDD - If the *Reference SFN Offset* IE is included in the CELL SETUP REQUEST message, the Node B where a reference clock is connected shall consider the SFN derived from the synchronisation port and the reference offset for reference time setting. All other Node Bs shall ignore the *Reference SFN Offset* IE if included.] + +[FDD - If the *IPDL Parameter Information* IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL shall be stored in the Node B and applied according to the *IPDL Indicator* IE value. If the *Burst Mode Parameters* IE is included in the *IPDL FDD Parameters* IE, the IPDL shall be operated in burst mode according to ref TS 25.214 [10].] + +[3.84Mcps TDD and 7.68Mcps TDD - If the *IPDL Parameter Information* IE containing *IPDL TDD Parameters* IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL in 3.84Mcps TDD and 7.68Mcps TDD modes shall be stored in the Node B and applied according to the *IPDL Indicator* IE value. If the *Burst Mode Parameters* IE is included in the *IPDL TDD Parameters* IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].] + +[1.28Mcps TDD - If the *IPDL Parameter Information LCR* IE containing *IPDL TDD Parameters LCR* IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL in 1.28Mcps TDD mode shall be stored in the Node B and applied according to the *IPDL Indicator* IE value. For MBSFN only mode, this IE shall be ignored by the Node B. If the *Burst Mode Parameters* IE is included in the *IPDL TDD Parameters LCR* IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].] + +[1.28Mcps TDD - For a multi-frequency cell, the *UARFCN Information LCR* IE indicates information about the configuration of the frequency and timeslot of the secondary frequency/frequencies.] + +When the cell is successfully configured, the Node B shall store the *Configuration Generation ID* IE value and send a CELL SETUP RESPONSE message as a response. + +[FDD - When the cell is successfully configured the CPICH(s), Primary SCH, Secondary SCH, Primary CCPCH and BCH exist.] [3.84Mcps TDD and 7.68Mcps TDD - When the cell is successfully configured the SCH, Primary CCPCH and BCH exist and the switching-points for the 3.84Mcps TDD / 7.68Mcps TDD frame structure are defined.] + +[1.28Mcps TDD - When the cell is successfully configured, the DwPCH, Primary CCPCH and BCH exist and the switching-points for the 1.28Mcps TDD frame structure are defined.] The cell and the channels shall be set to the state Enabled (TS 25.430 [6]). + +[1.28Mcps TDD - For a multi-frequency cell, the Node B shall consider the cell as having been successfully configured as long as the primary frequency is normally setup. When the cell is successfully configured, the Node B shall respond with the CELL SETUP RESPONSE message.] + +[TDD - The Node B shall ignore the *DPCH/PUSCH/PRACH Constant Value* IEs.] + +[1.28Mcps TDD - For a multi-frequency cell, when the cell is successfully configured, the Node B shall configure the UpPCH channel of the primary frequency in the timeslot of UpPTS.] + +[FDD - If the CELL SETUP REQUEST message includes *Cell Portion Information* IE, the Node B shall associate *Associated Secondary CPICH* IE to the cell portion indicated by *Cell Portion ID* IE and the *Maximum Transmission Power for Cell Portion* IE value shall be stored in the Node B and at any instance of time the total maximum output power in the cell portion indicated by *Cell Portion ID* IE shall not be above this value.] + +[FDD - If the *MIMO Pilot Configuration* IE is included in the CELL SETUP REQUEST message, then the parameters defining the pilot configuration for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].] + +[3.84Mcps TDD and 7.68Mcps TDD - If the CELL SETUP REQUEST message includes the *MBSFN Cell Parameter ID* IE, then the Node B shall configure the associated timeslot to operate in MBSFN mode using the scrambling codes and midambles dictated by the *MBSFN Cell Parameter ID* IE.] + +[1.28Mcps TDD - If the CELL SETUP REQUEST message includes the *MBSFN Only Mode Indicator* IE, the Node B shall configure the associated timeslot(s) to operate as MBSFN time slot(s) using the scrambling codes and basic midamble codes dictated by the *Time Slot Parameter ID* IE.] + +[1.28Mcps TDD - If the cell is operating in MBSFN only mode, the *DwPCH Information* IE shall be ignored by the Node B.] + +[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the PCCPCH shall be deployed on the MBSFN Special Time Slot (TS 25.221 [19]).] + +[FDD - If the *MIMO Pilot Configuration Extension* IE is included in CELL SETUP REQUEST, then the parameters extending the pilot information for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10]] + +[FDD - If the *MIMO with four transmit antennas Pilot Configuration* IE is included in CELL SETUP REQUEST, then the parameters defining the pilot configuration for MIMO with four transmit antennas shall be stored in the Node B and applied when MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode is used according to TS 25.214 [10].] + +### 8.2.12.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Cell Setup procedure. The diagram illustrates the interaction between a CRNC and a Node B. The CRNC sends a CELL SETUP REQUEST message to the Node B. The Node B responds with a CELL SETUP FAILURE message back to the CRNC.](8d1bb05debbaef0f72751449b2b55172_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: + CRNC->>Node B: CELL SETUP REQUEST + Note right of Node B: + Node B-->>CRNC: CELL SETUP FAILURE + Note left of CRNC: + +``` + +Sequence diagram showing the Unsuccessful Operation of the Cell Setup procedure. The diagram illustrates the interaction between a CRNC and a Node B. The CRNC sends a CELL SETUP REQUEST message to the Node B. The Node B responds with a CELL SETUP FAILURE message back to the CRNC. + +**Figure 17: Cell Setup procedure: Unsuccessful Operation** + +If the Node B cannot set up the cell according to the information given in CELL SETUP REQUEST message the CELL SETUP FAILURE message shall be sent to the CRNC. + +In this case, the cell is Not Existing in the Node B. The Configuration Generation ID shall not be changed in the Node B. + +The *Cause* IE shall be set to an appropriate value. + +Typical cause values are as follows: + +#### Radio Network Layer Cause: + +- S-CPICH not supported +- Requested Tx Diversity Mode not supported +- Power level not supported +- Node B Resources unavailable +- IPDL not supported +- [FDD - S-CPICH power offset support not available] + +#### Miscellaneous Cause: + +- O&M Intervention +- Control processing overload +- HW failure + +#### 8.2.12.4 Abnormal Conditions + +If the state of the cell already is Enabled or Disabled (TS 25.430 [6]) when the CELL SETUP REQUEST message is received in the Node B, it shall reject the configuration of the cell and all channels in the CELL SETUP REQUEST message by sending a CELL SETUP FAILURE message with the *Cause* IE set to "Message not compatible with receiver state". + +If the Local Cell on which the cell is mapped does not belong to a Power Local Cell Group and the requested maximum transmission power indicated by the *Maximum Transmission Power* IE exceeds the Maximum DL Power Capability of the Local Cell, the Node B shall consider the procedure as having failed and send a CELL SETUP FAILURE message to the CRNC. + +If the Local Cell on which the cell is mapped belongs to a Power Local Cell Group and the requested maximum transmission power indicated by *Maximum Transmission Power* IE exceeds the Maximum DL Power Capability of the Power Local Cell Group, the Node B shall consider the procedure as having failed and send a CELL SETUP FAILURE message to the CRNC. + +### 8.2.13 Cell Reconfiguration + +#### 8.2.13.1 General + +This procedure is used to reconfigure a cell in the Node B. + +#### 8.2.13.2 Successful Operation + +![Sequence diagram showing the Cell Reconfiguration procedure. The CRNC sends a CELL RECONFIGURATION REQUEST message to the Node B, and the Node B responds with a CELL RECONFIGURATION RESPONSE message.](02e16c8e8e61c2706b5c0129674884a8_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: CELL RECONFIGURATION REQUEST + CRNC->>Node B: CELL RECONFIGURATION REQUEST + Note left of Node B: CELL RECONFIGURATION RESPONSE + Node B-->>CRNC: CELL RECONFIGURATION RESPONSE + +``` + +Sequence diagram showing the Cell Reconfiguration procedure. The CRNC sends a CELL RECONFIGURATION REQUEST message to the Node B, and the Node B responds with a CELL RECONFIGURATION RESPONSE message. + +**Figure 18: Cell Reconfiguration procedure, Successful Operation** + +The procedure is initiated with a CELL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon Reception, the Node B shall reconfigure the cell according to the parameters given in the message. + +[FDD - If the CELL RECONFIGURATION REQUEST message includes the *Primary SCH Information* IE, the Node B shall reconfigure the Primary SCH power in the cell according to *Primary SCH Power* IE value.] + +[FDD - If the CELL RECONFIGURATION REQUEST message includes the *Secondary SCH Information* IE, the Node B shall reconfigure the Secondary SCH power in the cell according to the *Secondary SCH Power* IE value.] + +[FDD - If the CELL RECONFIGURATION REQUEST message includes the *Primary CPICH Information* IE, the Node B shall reconfigure the Primary CPICH power in the cell according to the *Primary CPICH Power* IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CPICH power according to the new value.] + +[FDD - If the CELL RECONFIGURATION REQUEST message includes one or more *Secondary CPICH Information* IE, the Node B shall reconfigure the power for each Secondary CPICH in the cell according to their *Secondary CPICH Power* IE value.] + +[3.84Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *SCH Information* IE, the Node B shall reconfigure the SCH power in the cell according to the *SCH Power* IE value.] + +[7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *SCH Information 7.68Mcps* IE, the Node B shall reconfigure the SCH power in the cell according to the *SCH Power* IE value.] + +[TDD - If the CELL RECONFIGURATION REQUEST message includes the *Timing Advance Applied* IE, the Node B shall apply the necessary functions for Timing Advance in that cell including reporting of the Rx Timing Deviation measurement, according to the *Timing Advance Applied* IE value.] + +[FDD - If the CELL RECONFIGURATION REQUEST message includes the *Primary CCPCH Information* IE, the Node B shall reconfigure the BCH power in the cell according to the *BCH Power* IE value.] + +[1.28Mcps TDD and 3.84Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *PCCPCH Information* IE, the Node B shall reconfigure the P-CCPCH power in the cell according to the *PCCPCH Power* IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CCPCH power according to the new value.] + +[7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *PCCPCH Information 7.68Mcps* IE, the Node B shall reconfigure the P-CCPCH power in the cell according to the *PCCPCH Power* IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CCPCH power according to the new value.] + +If the CELL RECONFIGURATION REQUEST message includes the *Maximum Transmission Power* IE, the value shall be stored in the Node B and at any instance of time the total maximum output power in the cell shall not be above this value. + +[3.84Mcps TDD and 7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *Time Slot Configuration* IE, the Node B shall reconfigure switching-point structure in the cell according to the *Time Slot* IE value.] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *Time Slot Configuration LCR* IE, the Node B shall reconfigure switching-point structure in the cell according to the *Time Slot LCR* IE value.] + +[TDD - If the CELL RECONFIGURATION REQUEST message includes any of the *DPCH/PUSCH/PRACH Constant Value* IEs, the Node B shall ignore them] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *DwPCH Information* IE, the Node B shall reconfigure the DwPCH power in the Cell according to the *DwPCH Power* IE.] + +[FDD - If the CELL RECONFIGURATION REQUEST message includes the *IPDL Parameter Information* IE with the *IPDL Indicator* IE set to the value "Active" the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the *IPDL FDD Parameters* IE. If the *Burst Mode Parameters* IE is included in the *IPDL FDD Parameters* IE, the IPDL shall be operated in burst mode according to ref TS 25.214 [10].] + +[3.84Mcps TDD and 7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *IPDL Parameter Information* IE with the *IPDL Indicator* IE set to the value "Active", the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the *IPDL TDD Parameters* IE. If the *Burst Mode Parameters* IE is included in the *IPDL TDD Parameters* IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *IPDL Parameter Information LCR* IE with the *IPDL Indicator* IE set to the value "Active", the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the *IPDL TDD Parameters LCR* IE. If the *Burst Mode Parameters* IE is included in the *IPDL TDD Parameters LCR* IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].] + +If the CELL RECONFIGURATION REQUEST message includes the *IPDL Parameter Information* IE with the *IPDL Indicator* IE set to the value "Inactive", the Node B shall deactivate the ongoing IPDL. + +When the cell is successfully reconfigured, the Node B shall store the new *Configuration Generation ID* IE value and send a CELL RECONFIGURATION RESPONSE message as a response. + +If the CELL RECONFIGURATION REQUEST message includes the *Synchronisation Configuration* IE, the Node B shall reconfigure the indicated parameters in the cell according to the value of the *N\_INSYNC\_IND*, *N\_OUTSYNC\_IND* and *T\_RLFFAILURE* IEs. When the parameters in the *Synchronisation Configuration* IE affect the thresholds applied to a RL set, the Node B shall immediately apply the new thresholds. When applying the new thresholds, the Node B shall not change the state or value of any of the timers and counters for which the new thresholds apply. + +[FDD - If the CELL RECONFIGURATION REQUEST message includes *Cell Portion Information* IE, the *Maximum Transmission Power for Cell Portion* IE value shall be stored in the Node B and at any instance of time the total maximum output power in the cell portion indicated by *Cell Portion ID* IE shall not be above this value.] + +[FDD - If the *MIMO Pilot Configuration* IE is included in the CELL RECONFIGURATION REQUEST message, then the parameters defining the pilot configuration for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].] + +[3.84Mcps TDD and 7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *MBSFN Cell Parameter ID* IE, then the Node B shall configure the associated timeslot to operate in MBSFN mode using the scrambling code and midamble dictated by the *MBSFN Cell Parameter ID* IE.] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *UARFCN Information To Add LCR* IE, the Node B shall reserve the necessary resource and add a secondary frequency to the cell according to the information indicated in the *UARFCN Information To Add LCR* IE.] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *UARFCN Information To Modify LCR* IE, the Node B shall reconfigure the configuration of the secondary frequency within the cell according to the information indicated in the *UARFCN Information To Modify LCR* IE.] + +[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the *UARFCN Information To Delete LCR* IE, the Node B shall remove the secondary frequency from the cell and any remaining dedicated channels on the secondary frequency according to the frequency information given in the *UARFCN Information To Delete LCR* IE. The states for the frequency within the cell shall be set to "Not existing". The Node B shall remove all Radio Links and all Node B Communication Contexts related to the secondary frequency within the cell. The Node B shall also initiate the release of the user plane transport bearers for the removed dedicated channels on the secondary frequency within the cell.] + +[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the PCCPCH shall be deployed on the MBSFN Special Time Slot (TS 25.221 [19]).] + +[FDD - If the *MIMO Pilot Configuration Extension* IE is included in CELL RECONFIGURATION REQUEST, then the parameters extending the pilot information for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].] + +[FDD - If the *MIMO with four transmit antennas Pilot Configuration* IE is included in CELL RECONFIGURATION REQUEST, then the parameters defining the pilot configuration for MIMO with four transmit antennas shall be stored in the Node B and applied when MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode is used according to TS 25.214 [10].] + +If the CELL RECONFIGURATION REQUEST message includes the *Dormant Mode Indicator* IE, the Node B shall initiate the requested function. If *Dormant Mode Indicator* IE = "Enter Dormant Mode", after completion of the reconfiguration to dormant mode there shall be no power transmitted in the cell. If the *Dormant Mode Indicator* IE = "Leave Dormant Mode", the Node B shall initiate reconfiguration of the cell and resume the normal operating mode. + +### 8.2.13.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Cell Reconfiguration procedure. The CRNC sends a CELL RECONFIGURATION REQUEST to Node B, and Node B responds with a CELL RECONFIGURATION FAILURE.](5bba23cc120ad806779f82df1c01bebf_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: CELL RECONFIGURATION REQUEST + CRNC->>Node B: CELL RECONFIGURATION REQUEST + Note left of Node B: CELL RECONFIGURATION FAILURE + Node B-->>CRNC: CELL RECONFIGURATION FAILURE +``` + +Sequence diagram showing the Unsuccessful Operation of the Cell Reconfiguration procedure. The CRNC sends a CELL RECONFIGURATION REQUEST to Node B, and Node B responds with a CELL RECONFIGURATION FAILURE. + +**Figure 19: Cell Reconfiguration procedure: Unsuccessful Operation** + +If the Node B cannot reconfigure the cell according to the information given in CELL RECONFIGURATION REQUEST message, the CELL RECONFIGURATION FAILURE message shall be sent to the CRNC. + +In this case, the Node B shall keep the old configuration of the cell and the Configuration Generation ID shall not be changed in the Node B. + +The *Cause* IE shall be set to an appropriate value. + +Typical cause values are as follows: + +#### Radio Network Layer Cause: + +- Power level not supported +- Node B Resources unavailable +- IPDL not supported +- [FDD - S-CPICH power offset support not available] +- [FDD - Requested Configuration Not Supported] + +#### Miscellaneous Cause: + +- O&M Intervention +- Control processing overload +- HW failure + +### 8.2.13.4 Abnormal Conditions + +If the *IPDL Indicator* IE set to the value "Active" is included in the CELL RECONFIGURATION REQUEST message and there is active IPDL ongoing in the Node B, the Node B shall respond with the CELL RECONFIGURATION FAILURE message with the cause value "IPDL already activated". + +If the *IPDL Indicator* IE set to the value "Active" is included in the CELL RECONFIGURATION REQUEST message and there is no IPDL stored in the Node B defining the IPDL, the Node B shall respond with the CELL RECONFIGURATION FAILURE message with the cause value "IPDL parameters not available". + +If the Local Cell on which the cell is mapped does not belong to of a Power Local Cell Group and the requested maximum transmission power indicated by the *Maximum Transmission Power* IE exceeds the Maximum DL Power Capability of the Local Cell, the Node B shall consider the procedure as having failed and send a CELL RECONFIGURATION FAILURE message to the CRNC. + +If the Local Cell on which the cell is mapped belongs to a Power Local Cell Group and the requested maximum transmission power indicated by *Maximum Transmission Power* IE exceeds the Maximum DL Power Capability of the Power Local Cell Group, the Node B shall consider the procedure as having failed and send a CELL RECONFIGURATION FAILURE message to the CRNC. + +## 8.2.14 Cell Deletion + +### 8.2.14.1 General + +This procedure is used to delete a cell in the Node B. + +### 8.2.14.2 Successful Operation + +![Sequence diagram showing the successful operation of the Cell Deletion procedure. The CRNC sends a CELL DELETION REQUEST message to the Node B, and the Node B responds with a CELL DELETION RESPONSE message.](aa73c8651865e31f7a2f7b8a9c068461_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: CELL DELETION REQUEST + Node B-->>CRNC: CELL DELETION RESPONSE +``` + +Sequence diagram showing the successful operation of the Cell Deletion procedure. The CRNC sends a CELL DELETION REQUEST message to the Node B, and the Node B responds with a CELL DELETION RESPONSE message. + +**Figure 20: Cell Deletion procedure, Successful Operation** + +The procedure is initiated with a CELL DELETION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon reception, the Node B shall remove the cell and any remaining common and dedicated channels within the cell. The states for the cell and the deleted common channels shall be set to Not Existing (TS 25.430 [6]). The Node B shall remove all Radio Links from the Cell and all Node B Communication Contexts that as a result do not have a Radio Link. The Node B shall also initiate release of the user plane transport bearers for the removed common and dedicated channels except the case that there is at least one FACH channel in this cell using the same transport bearer existing in other cell(s) in the Node B. In this case, the Node B shall remove the cell and any remaining common and dedicated channels within the cell but keep the common transport bearer which is used by the remaining common transport channel(s) in other cell(s). + +When the cell is deleted, the Node B shall send a CELL DELETION RESPONSE message as a response. + +### 8.2.14.3 Unsuccessful Operation + +- + +### 8.2.14.4 Abnormal Conditions + +If the CELL DELETION REQUEST message includes a *C-ID* IE value that is not existing in the Node B, the Node B shall respond with the CELL DELETION RESPONSE message. + +## 8.2.15 Resource Status Indication + +### 8.2.15.1 General + +This procedure is used in the following cases: + +1. When a Local Cell becomes Existing at the Node B. +2. When a Local Cell is to be deleted in Node B, i.e. becomes Not Existing. +3. When the capabilities of the Local Cell change at the Node B. +4. When a cell has changed its capability and/or its resource operational state at the Node B. +5. When common physical channels and/or common transport channels have changed their capabilities at the Node B. + +6. When a Communication Control Port has changed its resource operational state at the Node B. +7. When a Local Cell Group has changed its resource capability at the Node B. +8. [1.28Mcps TDD - For a multi-frequency cell, when a cell has been successfully set up but a secondary frequency failure has occurred within the cell.] + +Each of the above cases shall trigger a Resource Status Indication procedure and the RESOURCE STATUS INDICATION message shall contain the logical resources affected for that case and the cause value when applicable. + +## 8.2.15.2 Successful Operation + +![Sequence diagram showing the Resource Status Indication procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'RESOURCE STATUS INDICATION' centered above the arrow.](350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: RESOURCE STATUS INDICATION + Node B->>CRNC: RESOURCE STATUS INDICATION + +``` + +Sequence diagram showing the Resource Status Indication procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'RESOURCE STATUS INDICATION' centered above the arrow. + +**Figure 21: Resource Status Indication procedure, Successful Operation** + +The procedure is initiated with a RESOURCE STATUS INDICATION message sent from the Node B to the CRNC using the Node B Control Port. + +### Local Cell Becomes Existing: + +When a Local Cell becomes Existing at the Node B, the Node B shall make it available to the CRNC by sending a RESOURCE STATUS INDICATION message containing a "No Failure" Indication, the *Local Cell ID* IE and the *Add/Delete Indicator* IE set equal to "Add". + +When the capacity credits and consumption laws are shared between several Local Cells, the Node B includes the *Local Cell Group ID* IE for the Local Cell. If the *Local Cell Group Information* IE has not already been reported in a previous RESOURCE STATUS INDICATION message, the Node B shall include the capacity credits and the consumption laws in the *Local Cell Group Information* IE [FDD - , including also the E-DCH capacity consumption law, if E-DCH is supported]. + +If the *Local Cell* IE contains both the *DL Or Global Capacity Credit* IE and the *UL Capacity Credit* IE, then the internal resource capabilities of the Local Cell are modelled independently in the Uplink and Downlink direction. If the *UL Capacity Credit* IE is not present, then the internal resource capabilities of the Local Cell are modelled as shared resources between Uplink and Downlink. If the *Local Cell Group Information* IE contains both the *DL Or Global Capacity Credit* IE and the *UL Capacity Credit* IE, then the internal resource capabilities of the Local Cell Group are modelled independently in the Uplink and Downlink direction. If the *UL Capacity Credit* IE is not present, then the internal resource capabilities of the Local Cell Group are modelled as shared resources between Uplink and Downlink. + +If the Node B internal power resources are pooled for a group of Local Cells, the Node B shall include the *Power Local Cell Group ID* IE for the Local Cell. If the *Power Local Cell Group Information* IE has not already been reported in a previous RESOURCE STATUS INDICATION message, the Node B shall include this IE for the concerned Power Local Cell Group in this message. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group. + +If the Local Cell is HSDPA-capable when it becomes Existing, the Node B shall include the *HSDPA Capability* IE set to "HSDPA Capable" and may include *HS-DSCH MAC-d PDU Size Capability* IE for the Local Cell. + +If the Local Cell is E-DCH-capable when it becomes Existing, the Node B shall include the *E-DCH Capability* IE set to "E-DCH Capable" and may include *E-DCH MAC-d PDU Size Capability* IE for the Local Cell. + +If the Local Cell is MBMS-capable when it becomes Existing, the Node B shall include the *MBMS Capability* IE set to "MBMS Capable" for the Local Cell. + +[FDD - If the Local Cell is F-DPCH-capable when it becomes Existing, the Node B shall include the *F-DPCH Capability* IE set to "F-DPCH Capable" for the Local Cell.] + +[FDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the *Continuous Packet Connectivity DTX-DRX Capability* IE set to "Continuous Packet Connectivity DTX-DRX Capable" for the Local Cell when Continuous Packet Connectivity DTX-DRX is supported.] + +[FDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the *Continuous Packet Connectivity HS-SCCH less Capability* IE set to "Continuous Packet Connectivity HS-SCCH less Capable" for the Local Cell when Continuous Packet Connectivity HS-SCCH less is supported.] + +[FDD - If the Local Cell is MIMO-capable when it becomes Existing, then the Node B shall include the *MIMO Capability* IE set to "MIMO Capable" for the Local Cell.] + +[FDD - If the Local Cell is SixtyfourQAM DL-capable when it becomes Existing, then the Node B shall include the *SixtyfourQAM DL Capability* IE set to "SixtyfourQAM DL Capable" for the Local Cell.] + +[FDD - If the Local Cell is Enhanced FACH-capable when it becomes Existing, the Node B shall include the *Enhanced FACH Capability* IE set to "Enhanced FACH Capable" for the Local Cell.] + +[FDD - If the Local Cell is SixteenQAM UL-capable when it becomes Existing, then the Node B shall include the *SixteenQAM UL Capability* IE set to "SixteenQAM UL Capable" for the Local Cell.] + +[1.28Mcps TDD - If the Local Cell is MBSFN Only Mode-capable when it becomes Existing, the Node B shall include the *MBSFN Only Mode Capability* IE set to "MBSFN Only Mode Capable" for the Local Cell.] + +[FDD - If the Local Cell is F-DPCH Slot Format-capable when it becomes Existing, then the Node B shall include the *F-DPCH Slot Format Capability* IE set to " F-DPCH Slot Format Capable" for the Local Cell.] + +[1.28Mcps TDD - If the Local Cell is SixtyfourQAM DL-capable when it becomes Existing, then the Node B shall include the *SixtyfourQAM DL Capability* IE set to "SixtyfourQAM DL Capable" for the Local Cell.] + +[FDD - If the Local Cell is Common E-DCH-capable when it becomes Existing, the Node B shall include the *Common E-DCH Capability* IE set to "Common E-DCH Capable" for the Local Cell.] + +If the Local Cell is E-DPCCH Power Boosting-capable when it becomes Existing, the Node B shall include the *E-DPCCH Power Boosting Capability* IE set to " E-DPCCH Power Boosting Capable" for the Local Cell. + +[FDD - If the Local Cell is both SixtyfourQAM DL-capable and MIMO-capable when it becomes Existing, then the Node B shall include the *SixtyfourQAM DL and MIMO Combined Capability* IE set to "SixtyfourQAM DL and MIMO Combined Capable" for the Local Cell when Combined SixtyfourQAM DL and MIMO is supported.] + +[1.28Mcps TDD - If the Local Cell is Enhanced FACH-capable when it becomes Existing, the Node B shall include the *Enhanced FACH Capability* IE set to "Enhanced FACH Capable" for the Local Cell.] + +[1.28Mcps TDD - The Node B shall include the *Enhanced PCH Capability* IE set to "Enhanced PCH Capable" for every Enhanced PCH-capable Local Cell.] + +[1.28Mcps TDD - The Node B shall include the *Enhanced UE DRX Capability LCR* IE set to " Enhanced UE DRX Capable " for every Enhanced UE DRX Capable Local Cell.] + +[FDD - If the Local Cell is Multi Cell Capable when it becomes Existing, the Node B shall include the *Multi Cell Capability Info* IE and set the *Multi Cell Capability* IE value to "Multi Cell Capable" for the Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multicell adjacent and/or non-adjacent carrier operation (TS 25.133 [22]) (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the *Possible Secondary Serving Cell List* IE. For each cell in the *Possible Secondary Serving Cell List* IE that is Multi Cell E-DCH Capable, indicated in the *Cell Capability Container* IE with the "Multi Cell E-DCH Capability" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the *Multicell E-DCH Restriction* IE set to "TRUE" in the *Possible Secondary Serving Cell List* IE.] + +[1.28Mcps TDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the *Continuous Packet Connectivity DRX Capability LCR* IE set to " Continuous Packet Connectivity DRX Capable " for the Local Cell when Continuous Packet Connectivity DRX is supported.] + +[1.28Mcps TDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the *Semi-Persistent scheduling Capability LCR* IE set to " Semi-Persistent scheduling Capable" for the Local Cell when Semi-Persistent scheduling operation is supported.] + +[1.28Mcps TDD- If the Local Cell is + +MIMO-capable when it becomes Existing, then the Node B shall include the *MIMO Capability* IE set to "MIMO Capable" for the Local Cell.] + +[1.28Mcps TDD - If the Local Cell is both SixtyfourQAM DL-capable and MIMO-capable when it becomes Existing, then the Node B shall include the *SixtyfourQAM DL and MIMO Combined Capability* IE set to "SixtyfourQAM DL and MIMO Combined Capable" for the Local Cell when Combined SixtyfourQAM DL and MIMO is supported.] + +[FDD - If the Local Cell is Enhanced UE DRX-capable when it becomes Existing, the Node B shall include the *Enhanced UE DRX Capability* IE set to "Enhanced UE DRX Capable" for the Local Cell.] + +[1.28Mcps TDD- If the Local Cell is Cell Portion capable when it becomes Existing, then the Node B shall include the *Cell Portion CapabilityLCR* IE set to "Cell Portion Capable" for the Local Cell.] + +[FDD - If the Local Cell is MIMO-capable and supports the MIMO Power Offset For S-CPICH Capability when it becomes Existing, the Node B shall include the *MIMO Power Offset For S-CPICH Capability* IE set to "S-CPICH Power Offset Capable" for the Local Cell.] + +[FDD - If the Local Cell is MIMO-capable and supports DL control channels in transmit diversity for MIMO UEs (when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7])) when it becomes Existing, the Node B shall include the *TX Diversity on DL Control Channels by MIMO UE Capability* IE set to "DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable".] + +[FDD - If the Local Cell is Single Stream MIMO-capable when it becomes Existing, then the Node B shall include the *Single Stream MIMO Capability* IE set to "Single Stream MIMO Capable" for the Local Cell.] + +[FDD - If the Local Cell is HS-DSCH Dual Band Capable when it becomes Existing, the Node B shall include the *Dual Band Capability Info* IE and set the *Dual Band Capability* IE value to "Dual Band Capable" for the Local Cell. If the cell can be the serving HS-DSCH then the possible cells to serve dual band carrier operation (TS 25.133 [22]) (same sector) that can act as secondary serving HS-DSCH shall be listed in the *Possible Secondary Serving Cell List* IE If the Local Cell is E-DCH Dual Band Capable, the Node B shall include the *Dual Band E-DCH Capability* IE in the *Dual Band Capability Info* IE, and set its value to "Dual Band Capable". For each cell in the *Possible Secondary Serving Cell List* IE that is Multi Band E-DCH Capable, and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the *Multicell E-DCH Restriction* IE set to "TRUE" in the *Possible Secondary Serving Cell List* IE.] + +[FDD - If the local cell is capable of at least one feature listed in 9.2.2.129 when it becomes existing, the Node B shall include the *Cell Capability Container* IE and indicate the capabilities listed in 9.2.2.129 for the local cell.] + +[1.28Mcps TDD - If the Local Cell is TS0-capable when it becomes Existing, the Node B shall include the *TS0 Capability LCR* IE set to "TS0 Capable" for every TS0 Capable Local Cell.] + +[FDD - If the Local Cell, when it becomes Existing, is MIMO-capable and/or Single Stream MIMO-capable and configuration of the precoding weight set restriction defined in TS 25.331 [18] is preferred, the Node B may include the *Precoding Weight Set Restriction* IE set to "Preferred" for the Local Cell.] + +[1.28Mcps TDD- If the local cell is capable of at least one feature listed in 9.2.3.115 when it becomes existing, the Node B shall include the *Cell Capability Container TDD LCR* IE and indicate the capabilities listed in 9.2.3.115 for the local cell.] + +[1.28Mcps TDD - If the local cell is capable of at least one feature listed in 9.2.3.119 when it becomes existing, the Node B shall include the *MU-MIMO Capability Container* IE and indicate the capabilities listed in 9.2.3.119 for the local cell.] + +[1.28Mcps TDD - If the Local Cell is Adaptive Special Burst Power Capable when it becomes Existing, the Node B shall include the *Adaptive Special Burst Power Capability LCR* IE set to "Adaptive Special Burst Power Capable" for every Adaptive Special Burst Power Capable Local Cell.] + +#### **Local Cell Deletion:** + +When a Local Cell is to be deleted in the Node B, i.e. becomes Not Existing, the Node B shall withdraw the Local Cell from the CRNC by sending a RESOURCE STATUS INDICATION message containing a "No Failure" Indication, the *Local Cell ID* IE and the *Add/Delete Indicator* IE set to "Delete". The Node B shall not withdraw a previously configured cell at the Node B that the CRNC had configured using the Cell Setup procedure, until the CRNC has deleted that cell at the Node B using the Cell Delete procedure. + +### Capability Change of a Local Cell: + +When the capabilities of a Local Cell change at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the *Local Cell ID* IE. + +The Node B shall include the *Minimum DL Power Capability* IE when it is known by the Node B. + +If the maximum DL power capability of the Local Cell has changed, the new capability shall be indicated in the *Maximum DL Power Capability* IE. + +If the DL capability for supporting the minimum spreading factor has changed, the new capability shall be indicated in the *Minimum Spreading Factor* IE. + +[TDD - If the availability of the Reference clock connected to a Local Cell has changed, the new availability condition shall be indicated in the *Reference Clock Availability* IE.] + +The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +If the internal resource capabilities of the Local Cell are affected, it shall be reported in the following way: + +- If the internal resource capabilities of the Local Cell are modelled as shared resources between Uplink and Downlink, the new capacity shall be reported in the *DL Or Global Capacity Credit* IE. +- If the internal resource capabilities of the Local Cell are modelled independently in the Uplink and Downlink direction, then the *DL Or Global Capacity Credit* IE and the *UL Capacity Credit* IE shall be present in the RESOURCE STATUS INDICATION. + +If the Capacity Consumption Law for Common Channels has changed for the Local Cell, the new law shall be reported by the Node B in the *Common Channels Capacity Consumption Law* IE. + +If the Capacity Consumption Law for Dedicated Channels has changed for the Local Cell, the new law shall be reported by the Node B in the *Dedicated Channels Capacity Consumption Law* IE. + +[FDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell, the new law shall be reported by the Node B in the *E-DCH Capacity Consumption Law* IE.] + +[TDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell, the new law shall be reported by the Node B in the *E-DCH TDD Capacity Consumption Law* IE.] + +If the HSDPA capability has changed for the Local Cell, the new capability shall be indicated in the *HSDPA Capability* IE. + +If the HS-DSCH MAC-d PDU Size Capability has changed for the Local Cell, the new capability shall be indicated in the *HS-DSCH MAC-d PDU Size Capability* IE. + +If the E-DCH capability has changed for the Local Cell, the new capability shall be indicated in the *E-DCH Capability* IE. [FDD - The Node B shall include the *E-DCH Capability* IE if any of the E-DCH TTI2ms, SF or HARQ Combining capabilities has changed for the E-DCH capable Local Cell.] + +If the E-DCH MAC-d PDU Size Capability has changed for the Local Cell, the new capability shall be indicated in the *E-DCH MAC-d PDU Size Capability* IE. + +If the MBMS capability has changed for the Local Cell, the new capability shall be indicated in the *MBMS Capability* IE. + +[FDD - If the F-DPCH capability has changed for the Local Cell, the new capability shall be indicated in the *F-DPCH Capability* IE.] + +[FDD - If the Continuous Packet Connectivity DTX-DRX capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the *Continuous Packet Connectivity DTX-DRX Capability* IE. The Node B shall include the *Continuous Packet Connectivity DTX-DRX Capability* IE if the Max UE DTX Cycle supported by the Continuous Packet Connectivity DTX-DRX capable Local Cell has changed. If the Continuous Packet Connectivity HS-SCCH less capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the *Continuous Packet Connectivity HS-SCCH less Capability* IE.] + +[FDD - If the MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the *MIMO Capability* IE.] + +[FDD - If the SixtyfourQAM DL capability has changed for the Local Cell, then the new capability shall be indicated in the *SixtyfourQAM DL Capability* IE.] + +[FDD - If the Enhanced FACH capability has changed for the Local Cell, the new capability shall be indicated in the *Enhanced FACH Capability* IE. The Node B shall include the *Enhanced FACH Capability* IE if the Enhanced PCH capability has changed for the Enhanced PCH capable Local Cell.] + +[FDD - If the SixteenQAM UL capability has changed for the Local Cell, then the new capability shall be indicated in the *SixteenQAM UL Capability* IE.] + +[1.28Mcps TDD - If the MBSFN Only Mode capability has changed for the Local Cell, the new capability shall be indicated in the *MBSFN Only Mode Capability* IE.] + +[FDD - If the F-DPCH Slot Format capability has changed for the Local Cell, then the new capability shall be indicated in the *F-DPCH Slot Format Capability* IE.] + +[1.28Mcps TDD - If the SixtyfourQAM DL capability has changed for the Local Cell, then the new capability shall be indicated in the *SixtyfourQAM DL Capability* IE.] + +[FDD - If the Common E-DCH capability has changed for the Local Cell, the new capability shall be indicated in the *Common E-DCH Capability* IE. The Node B shall include the *Common E-DCH Capability* IE if the E-AI capability has changed for the Common E-DCH capable Local Cell. The Node B shall include the *Common E-DCH Capability* IE if the HS-DPCH capability for Common E-DCH has changed for the Common E-DCH capable Local Cell.] + +If the Support for E-DPCH Power Boosting Capability has changed for the Local Cell, the new capability shall be indicated in the *E-DPCH Power Boosting Capability* IE. + +[FDD – If the SixtyfourQAM DL and MIMO Combined capability has changed for the Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable, then the new capability shall be indicated in the *SixtyfourQAM DL and MIMO Combined Capability* IE.] + +[1.28Mcps TDD - If the Enhanced FACH capability has changed for the Local Cell, the new capability shall be indicated in the *Enhanced FACH Capability* IE. The Node B shall include the *Enhanced FACH Capability* IE if the Enhanced PCH capability has changed for the Enhanced PCH capable Local Cell.] + +[1.28Mcps TDD - If the Enhanced PCH capability has changed for the local cell, the new capability shall be indicated in the *Enhanced PCH Capability* IE.] + +[1.28Mcps TDD - If the Enhanced UE DRX capability has changed for the local cell, the new capability shall be indicated in the *Enhanced UE DRX Capability LCR* IE.] + +[FDD - If the Multi Cell Capability, the list of possible secondary serving cells and/or cells restricted for use as an Additional E-DCH on the secondary uplink frequency have changed for the Local Cell, the new capability including the list of possible secondary serving cells, and optionally the *Multicell E-DCH Restriction* IE, shall be indicated in the *Multi Cell Capability Info*.] + +[FDD - If the Dual Band Capability, the Dual Band E-DCH Capability, the list of possible secondary serving cells and/or cells restricted for use as an Additional E-DCH on the secondary uplink frequency have changed for the Local Cell, the new capability including the list of possible secondary serving cells, and optionally the *Multicell E-DCH Restriction* IE, shall be indicated in the *Dual Band Capability* IE] + +[1.28Mcps TDD - If the Continuous Packet Connectivity DRX capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the *Continuous Packet Connectivity DRX Capability LCR* IE. If the Semi-Persistent scheduling operation capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the *Semi-Persistent scheduling Capability LCR* IE.] + +[1.28Mcps TDD- If the MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the *MIMO Capability* IE.] + +[1.28Mcps TDD- If the SixtyfourQAM DL and MIMO Combined capability has changed for the Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable, then the new capability shall be indicated in the *SixtyfourQAM DL and MIMO Combined Capability IE*.] + +[FDD - If the Enhanced UE DRX capability has changed for the Local Cell, the new capability shall be indicated in the *Enhanced UE DRX Capability IE*.] + +[1.28Mcps TDD- If the Cell Portion capability has changed for the Local Cell, the new capability shall be indicated in the *Cell Portion CapabilityLCR IE*.] + +[FDD - If the support for MIMO Power Offset For S-CPICH Capability has changed for the Local Cell, the new capability shall be indicated in the *MIMO Power Offset For S-CPICH Capability IE*.] + +[FDD - If the support for DL control channels in transmit diversity for MIMO UEs (when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7])) has changed for the Local Cell, the new capability shall be indicated in the *TX Diversity on DL Control Channels by MIMO UE Capability IE*.] + +[FDD - If the Single Stream MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the *Single Stream MIMO Capability IE*.] + +[FDD - If any of the capabilities indicated 9.2.2.129 has changed for the Local Cell, the new capabilities shall be indicated in the *Cell Capability Container IE*.] + +[1.28Mcps TDD - If the TS0 capability has changed for the Local Cell, then the new capability shall be indicated in the *TS0 Capability LCR IE*.] + +[FDD - If the preference regarding configuration of the precoding weight set restriction defined in TS 25.331 [18] has changed for the Local Cell, the new value shall be indicated in the *Precoding Weight Set Restriction IE*.] + +[1.28Mcps TDD - If any of the capabilities indicated 9.2.3.115 has changed for the Local Cell, the new capabilities shall be indicated in the *Cell Capability Container TDD LCR IE*.] + +[1.28Mcps TDD - If any of the capabilities indicated 9.2.3.119 has changed for the Local Cell, the new capabilities shall be indicated in the *MU-MIMO Capability Container IE*.] + +[1.28Mcps TDD - If the Adaptive Special Burst Power capability has changed for the Local Cell, then the new capability shall be indicated in the *Adaptive Special Burst Power Capability LCR IE*.] + +#### **Capability Change of a Cell:** + +When the capabilities and/or resource operational state of a cell changes at the Node B, the Node B shall report the new capability and/or resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication, the *Resource Operational State IE* and the *Availability Status IE*. The *Cause IE* in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +#### **Capability Change of a Common Physical Channel and/or Common Transport Channel:** + +The Node B shall not delete any common or dedicated channels due to the cell being "Disabled". For all affected common and dedicated channels, the Node B shall report the impact to the CRNC with the relevant procedures. + +When the capabilities and/or resource operational state of common physical channels and/or common transport channels have changed, the Node B shall report the new capability and/or resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication, the *Resource Operational State IE* and the *Availability Status IE* set to appropriate values for the affected channel(s). The *Cause IE* in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +When a power value for a common physical channel and/or a common transport channel becomes beyond the supported power value range due to a change in capability in the Node B, it shall be reported to the CRNC in the RESOURCE STATUS INDICATION message, with the *Resource Operational State IE* set to "Enabled", the *Availability Status IE* set to "Degraded" and the *Cause IE* set to "Power level not supported". Affected channels shall use the nearest power value that is supported. + +#### **[1.28Mcps TDD - Capability Change of a UpPCH channel:]** + +When the capabilities of UpPCH channels which are not configured in the timeslot of UpPTS on one or multiple frequencies have changed, the Node B may include the *UpPCH Information LCR* IE in the RESOURCE STATUS INDICATION message. + +#### Capability Change of a Communication Control Port: + +When the resource operational state of a Communication Control Port has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the *Communication Control Port ID* IE. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +#### Capability Change of HS-DSCH Resources: + +When the resource operational state of the HS-DSCH resources has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the *UARFCN* IE in the *HS-DSCH Resources Information* IE to report the status of the HS-DSCH resources on the indicated frequency, the Node B may also not include any *UARFCN* IE in the *HS-DSCH Resources Information* IE to report the status of the HS-DSCH resources for the whole cell.] + +#### Capability Change of E-DCH Resources: + +When the resource operational state of the E-DCH resources has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value. + +[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the *UARFCN* IE in the *E-DCH Resources Information* IE to report the status of the E-DCH resources on the indicated frequency, the Node B may also not include any *UARFCN* IE in the *E-DCH Resources Information* IE to report the status of the E-DCH resources for the whole cell.] + +#### Capability Change of a Local Cell Group: + +When the resource capabilities of a Local Cell Group change at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the *Local Cell Group Information* IE reporting the change. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value. If the RESOURCE STATUS INDICATION message contains both the *DL Or Global Capacity Credit* IE and the *UL Capacity Credit* IE, then the internal resource capabilities of the Node B are modelled independently in the Uplink and Downlink direction. If the *UL Capacity Credit* IE is not present, then the internal resource capabilities of the Node B are modelled as shared resources between Uplink and Downlink. + +If the Capacity Consumption Law for Common Channels has changed for the Local Cell Group, the new law shall be reported by the Node B in the *Common Channels Capacity Consumption Law* IE. + +If the Capacity Consumption Law for Dedicated Channels has changed for the Local Cell Group, the new law shall be reported by the Node B in the *Dedicated Channels Capacity Consumption Law* IE. + +[FDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell Group, the new law shall be reported by the Node B in the *E-DCH Capacity Consumption Law* IE.] + +[TDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell Group, the new law shall be reported by the Node B in the *E-DCH TDD Capacity Consumption Law* IE.] + +#### Capability Change of a Power Local Cell Group: + +When the power capability of a Power Local Cell Group changes at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message with the *Indication Type* IE set equal to "Service Impacting" and the *Power Local Cell Group Information* IE reporting the change. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value. In this case, the Node B shall also include the *Maximum DL Power Capability* IE in the *Local Cell Information* IE for all the Local Cells belonging to the concerned Power Local Cell Group. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group. + +[1.28Mcps TDD - For a multi-frequency cell, when a cell has been successfully setup but a secondary frequency failure has occurred, the Node B shall report the status of the secondary frequency indicated by *UARFCN* IE on which the failure occurred by immediately sending a RESOURCE STATUS INDICATION message with the *Indication Type* IE set equal to "Service Impacting", the *Resource Operational State* IE and the *Availability Status* IE. The *Cause* IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value.] + +#### General: + +When the RESOURCE STATUS INDICATION message is used to report an error, only one cause value for all reported objects can be sent in one message. When the RESOURCE STATUS INDICATION message is used to clear errors, only all errors for one object can be cleared per message. It is not possible to clear one out of several errors for one object. + +[1.28Mcps TDD - For a multi-frequency cell, the Node B should report the status of the resources used for each frequency. A reporting method can be found in Annex E.] + +### 8.2.15.3 Abnormal Conditions + +- + +## 8.2.16 System Information Update + +### 8.2.16.1 General + +The System Information Update procedure performs the necessary operations in order for the Node B to apply the correct scheduling of and/or to include the appropriate contents to the system information segments broadcast on the BCCH. + +### 8.2.16.2 Successful Operation + +![Sequence diagram showing the System Information Update procedure. A CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to a Node B, and the Node B responds with a SYSTEM INFORMATION UPDATE RESPONSE message.](0bdf45f8598420cf51abdd73300adc83_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + CRNC->>Node B: SYSTEM INFORMATION UPDATE REQUEST + Note right of Node B: Node B + Node B-->>CRNC: SYSTEM INFORMATION UPDATE RESPONSE + +``` + +Sequence diagram showing the System Information Update procedure. A CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to a Node B, and the Node B responds with a SYSTEM INFORMATION UPDATE RESPONSE message. + +**Figure 22: System Information Update procedure, Successful Operation** + +The procedure is initiated with a SYSTEM INFORMATION UPDATE REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +The Node B shall consider the requested updates to the BCCH schedule in the same order as the MIB/SB/SIB information is included in the SYSTEM INFORMATION UPDATE REQUEST message. + +If the SYSTEM INFORMATION UPDATE REQUEST message includes the *BCCH Modification Time* IE, the updates to the BCCH schedule (possibly consisting of IB occurrence additions, IB occurrence deletions and IB occurrence contents updates) indicated in the SYSTEM INFORMATION UPDATE REQUEST message shall be applied by the Node B at the first time instance starting from the SFN value set by the *BCCH Modification Time* IE. If no *BCCH Modification Time* IE is included, the updates to the BCCH schedule shall be applied as soon as possible. + +The Node B shall consider the requested updates to be the BCH mapped on SCCPCH if the *BCH mapped on SCCPCH Indication* IE is included in the SYSTEM INFORMATION UPDATE REQUEST message. + +#### Information Block addition: + +If the SYSTEM INFORMATION UPDATE REQUEST message includes segments of a certain MIB/SB/SIB, the Node B shall assume that all segments for that Information Block are included in the message and ordered with increasing Segment Index (starting from 0). For each included segment, segment type information and *IB SG POS* IE are also given in the SYSTEM INFORMATION UPDATE REQUEST message. + +The Node B shall determine the correct cell system frame number(s) (SFN) for transmission of the segments of system information, from the scheduling parameters provided in the SYSTEM INFORMATION UPDATE REQUEST message. The SFN for transmitting the segments shall be determined by the *IB SG REP* IE and *IB SG POS* IE such that: + +- SFN mod IB\_SG\_REP = IB\_SG\_POS + +If the SYSTEM INFORMATION UPDATE REQUEST message contains Master Information Block (MIB) segments in addition to SIB or SB segments, the MIB segments shall first be sent in the physical channel by the Node B. Once these MIB segments have been sent in the physical channel, the updated SB/SIB segments shall then be sent in the physical channel. + +Only if the inclusion of each new IB segment in the BCCH schedule leads to a valid segment combination according to TS 25.331 [18], the Node B shall accept the system information update. + +If the *SIB Originator* IE value is set to "Node B", the Node B shall create the SIB segment of the SIB type given by the *IB Type* IE and autonomously update the SIB segment and apply the scheduling and repetition as given by the *IB SG REP* IE and *IB SG POS* IE. + +SIBs originating from the Node B can only be SIBs containing information that the Node B can obtain on its own. + +If the SYSTEM INFORMATION UPDATE REQUEST message contains SB3 segment in addition to SIB, the BCH mapped on SCCPCH is used. The SB3 segments shall first be sent in the physical channel SCCPCH by the Node B. Once the SB3 segment has been sent in the physical channel SCCPCH, the updated SIB segments shall then be sent in the physical channel SCCPCH. + +#### Information Block deletion: + +If an IB Deletion is indicated in an instance of *MIB/SB/SIB information* IE in the SYSTEM INFORMATION UPDATE REQUEST message, the Node B shall delete the IB indicated by the *IB Type* IE and *IB OC ID* IE from the transmission schedule on BCCH. + +If the *BCH mapped on SCCPCH Indication* IE is included, and an IB Deletion is indicated in an instance of *MIB/SB/SIB information* IE in the SYSTEM INFORMATION UPDATE REQUEST message, the Node B shall delete the IB indicated by the *IB Type* IE and *IB OC ID* IE from the transmission schedule on BCH which is mapped on SCCPCH. + +#### Information Block update: + +If the SYSTEM INFORMATION UPDATE REQUEST message contains segments for an IB without *IB SG REP* IE and *IB SG POS* IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCCH schedule by an IB deletion indicated in a *MIB/SB/SIB information* IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB segments are included, then the Node B shall only update the contents of the IB segments without any modification in segment scheduling. + +If the SYSTEM INFORMATION UPDATE REQUEST message contains the *BCH mapped on SCCPCH Indication* IE and the segments for an IB without *IB SG REP* IE and *IB SG POS* IE and there is already an IB in the BCH mapped on SCCPCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCH mapped on SCCPCH schedule by an IB deletion indicated in a *MIB/SB/SIB information* IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB segments are included, then the Node B shall only update the contents of the IB segments without any modification in segment scheduling. + +If the Node B successfully completes the updating of the physical channel scheduling cycle according to the parameters given in the SYSTEM INFORMATION UPDATE REQUEST message, it shall respond to the CRNC with a SYSTEM INFORMATION UPDATE RESPONSE message. + +### 8.2.16.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the System Information Update procedure. A CRNC sends a SYSTEM INFORMATION UPDATE REQUEST to a Node B, and the Node B responds with a SYSTEM INFORMATION UPDATE FAILURE.](c4f4e64722ba94da46d926c92ef35b46_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: 8.2.16.3 Unsuccessful Operation + CRNC->>Node B: SYSTEM INFORMATION UPDATE REQUEST + Node B-->>CRNC: SYSTEM INFORMATION UPDATE FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the System Information Update procedure. A CRNC sends a SYSTEM INFORMATION UPDATE REQUEST to a Node B, and the Node B responds with a SYSTEM INFORMATION UPDATE FAILURE. + +Figure 23: System Information Update procedure, Unsuccessful Operation + +If the Node B is unable to update the physical channel scheduling cycle according to all the parameters given in the SYSTEM INFORMATION UPDATE REQUEST message, it shall respond with a SYSTEM INFORMATION UPDATE FAILURE message with an appropriate cause value. + +The Node B shall not incorporate any of the requested changes into the physical channel scheduling cycle, and the previous system information configuration shall remain intact. + +Typical cause values are: + +#### Radio Network Layer Cause: + +- SIB Origination in Node B not Supported +- BCH mapped on SCCPCH scheduling error + +#### Miscellaneous Cause: + +- Hardware failure +- Control Processing overload +- O&M Intervention + +### 8.2.16.4 Abnormal Conditions + +The Node B shall reject, with the cause value "SIB origination in Node B not supported", requests for Node B originated system information blocks that make use of a value tag. + +The Node B shall reject the requested update with cause value "BCCH scheduling error" if: + +- After having handled a certain *MIB/SB/SIB information* IE repetition, an illegal BCCH schedule results; +- If a *MIB/SB/SIB Information* IE repetition includes an *IB SG REP* IE or an *IB SG POS* IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCCH schedule by an IB deletion indicated in a *MIB/SB/SIB information* IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB addition is indicated. This rule shall apply even if the scheduling instructions in *IB SG REP* IE and *IB SG POS* IE were the same as the current scheduling instructions for the concerned IB; +- If a *MIB/SB/SIB Information* IE repetition includes no *IB SG REP* IE and *IB SG POS* IE and there is no IB in the BCCH schedule with the same IB Type and IB OC ID; +- If a *MIB/SB/SIB Information* IE repetition includes no *IB SG REP* IE and *IB SG POS* IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID but it is requested to be deleted from the BCCH schedule by an IB deletion indicated in a *MIB/SB/SIB information* IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB addition is indicated. + +The Node B shall reject the requested update with cause value "BCH mapped on SCCPCH scheduling error": + +- If a *MIB/SB/SIB Information* IE repetition includes the MIB segment and the SB3 segment in the SYSTEM INFORMATION UPDATE REQUEST message. +- If a *MIB/SB/SIB Information* IE repetition includes the SB3 segment in the SYSTEM INFORMATION UPDATE REQUEST message, but the *BCH mapped to SCCPCH Indication* IE is not set to "InUse". + +### 8.2.17 Radio Link Setup + +#### 8.2.17.1 General + +This procedure is used for establishing the necessary resources for a new Node B Communication Context in the Node B. + +[FDD - The Radio Link Setup procedure is used to establish one or more radio links. The procedure establishes one or more DCHs on all radio links, and in addition, it can include the establishment of an HS-DSCH on one radio link and it can include the establishment of an E-DCH on one or more radio links.] + +[TDD - The Radio Link Setup procedure is used to establish one radio link including one or more transport channels. The transport channels can be a mix of DCHs, DSCHs, and USCHs, or DCHs and an HS-DSCH, or DCHs, an HS-DSCH and an E-DCH, including also combinations where one or more transport channel types are not present.] + +## 8.2.17.2 Successful Operation + +![Sequence diagram showing the Radio Link Setup procedure between CRNC and Node B. The CRNC sends a RADIO LINK SETUP REQUEST message to Node B, and Node B responds with a RADIO LINK SETUP RESPONSE message.](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: + CRNC->>Node B: RADIO LINK SETUP REQUEST + Note right of Node B: + Node B-->>CRNC: RADIO LINK SETUP RESPONSE + Note left of CRNC: + +``` + +Sequence diagram showing the Radio Link Setup procedure between CRNC and Node B. The CRNC sends a RADIO LINK SETUP REQUEST message to Node B, and Node B responds with a RADIO LINK SETUP RESPONSE message. + +**Figure 24: Radio Link Setup procedure, Successful Operation** + +The procedure is initiated with a RADIO LINK SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception of the RADIO LINK SETUP REQUEST message, the Node B shall reserve necessary resources and configure the new Radio Link(s) according to the parameters given in the message. + +The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A. + +If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. + +[FDD - If the *Usefulness of Battery Optimization* IE is contained in the RADIO LINK SETUP REQUEST message, the Node B may store the received value and use it to determine whether this UE can benefit from battery optimization techniques.] + +### Transport Channels Handling: + +#### DCH(s): + +[TDD - If the *DCH Information* IE is present, the Node B shall configure the new DCH(s) according to the parameters given in the message.] + +If the RADIO LINK SETUP REQUEST message includes a *DCH Information* IE with multiple *DCH Specific Info* IEs, then the Node B shall treat the DCHs in the *DCH Information* IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. + +If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Uplink DCH only", the Node B shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. + +If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Downlink DCH only", the Node B shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. + +[FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the *QE-Selector* IE set to "selected", the Transport channel BER from that DCH shall be the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If the *QE-Selector* IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].] + +For a set of co-ordinated DCHs, the Transport channel BER from the DCH with the *QE-Selector* IE set to "selected" shall be used for the QE in the UL data frames, ref. TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If all DCHs have *QE-Selector* IE set to "non-selected", the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]]. + +The Node B shall use the included *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs as the FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the configuration. + +The Node B shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the configuration. + +The Node B shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the configuration. + +The received *Frame Handling Priority* IE specified for each Transport Channel should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the Node B once the new RL(s) has been activated. + +If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs. + +[FDD - The *Diversity Control Field* IE indicates for each RL (except the first RL in the message) whether the Node B shall combine the concerned RL or not. + +- If the *Diversity Control Field* IE is set to "May", the Node B shall decide for either of the alternatives. +- If the *Diversity Control Field* IE is set to "Must", the Node B shall combine the RL with one of the other RL. +- If the *Diversity Control Field* IE is set to "Must not", the Node B shall not combine the RL with any other existing RL. + +The signalled *Diversity Control Field* IE is applied to Dedicated Transport Channels (DCH) only. In case of E-DCH it shall always be assumed to be set to "Must". When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with.] + +[FDD - In the RADIO LINK SETUP RESPONSE message, the Node B shall indicate for each RL with the Diversity Indication in the *RL Information Response* IE whether the RL is combined or not.] + +- [FDD - In case of not combining with a RL previously listed in the RADIO LINK SETUP RESPONSE message or for the first RL in the RADIO LINK SETUP RESPONSE message, and if the *DCH Indicator For E-DCH-HSDPA Operation* IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall:] + - [FDD - include in the *DCH Information Response* IE in the RADIO LINK SETUP RESPONSE message for which the *Transport Bearer Not Requested Indicator* IE was not included the *Binding ID* IE and *Transport Layer Address* IE for the transport bearer to be established for each DCH of this RL.] + - [FDD - include in the RADIO LINK SETUP RESPONSE message the *Transport Bearer Not Setup Indicator* IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK SETUP REQUEST message.] +- [FDD - For the first E-DCH RL in the RADIO LINK SETUP RESPONSE message, the Node B shall:] + - [FDD - include in the *E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for the transport bearer to be established for each E-DCH MAC-d flow of this RL.] + - [FDD - include in the RADIO LINK SETUP RESPONSE message the *Transport Bearer Not Setup Indicator* IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK SETUP REQUEST message.] + +- [FDD - Otherwise in case of combining, the *RL ID* IE indicates (one of) the RL(s) previously listed in this RADIO LINK SETUP RESPONSE message with which the concerned RL is combined and if the ALCAP is not used and the transport bearer for the DCH is already established, the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used. In case of combining an E-DCH RL, one of the RLs previously listed in this RADIO LINK SETUP RESPONSE message including the *E-DCH FDD Information Response* IE shall be regarded as the RL with which the concerned E-DCH RL is combined.] + +[TDD - The Node B shall include in the *DCH Information Response* IE in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for the transport bearer to be established for each DCH of this RL.] + +[TDD - If an E-DCH has been established, the Node B shall include in the *E-DCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for the transport bearer to be established for each E-DCH MAC-d flow of the RL.] + +In the case of a set of co-ordinated DCHs, the *Binding ID* IE and the *Transport Layer Address* IE shall be specified for only one of the DCHs in the set of co-ordinated DCHs [FDD - where the *Transport Bearer Not Requested Indicator* IE was not included]. + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for a DCH, then the Node B shall not establish a transport bearer for the concerned DCH and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for a DCH and:] + +- [FDD - if the Node B establishes a transport bearer for the concerned DCH, the Node B shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH being established.] +- [FDD - if the Node B does not establish a transport bearer for the concerned DCH, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.] + +#### **[FDD – DCH Enhancements]:** + +[FDD – If the RADIO LINK SETUP REQUEST message includes the *DCH Enhancements Information* IE, then the Node B shall store the corresponding information in the concerned Node B communication context, setup the requested DCH Enhancements operation [52], and:] + +- [FDD – Use the *PO-SRB* IE to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].] +- [FDD – Use the *DL FET Mode* IE to configure the DL FET mode [8, 52].] +- [FDD – Use the information contained in the *DL DCH Concatenation* IE, if present, to identify the Transport Channels that shall be concatenated according to TS 25.212 [8].] + +#### **[TDD - DSCH(s)]:** + +[TDD - If the *DSCH Information* IE is present, the Node B shall configure the new DSCH(s) according to the parameters given in the message.] + +[TDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *DSCH Information* IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DSCH.] + +[TDD - The Node B shall include in the *DSCH Information Response* IE in the RADIO LINK SETUP RESPONSE the *Binding ID* IE and the *Transport Layer Address* IE for the transport bearer to be established for each DSCH of this RL.] + +[TDD - If the RADIO LINK SETUP REQUEST message includes the *TNL QoS* IE in the *DSCH TDD Information* IE and if ALCAP is not used, the Node B may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.] + +**[TDD - USCH(s)]:** + +[TDD - If the *USCH Information* IE is present, the Node B shall configure the new USCH(s) according to the parameters given in the message.] + +[TDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *USCH Information* IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the USCH.] + +[TDD - If the RADIO LINK SETUP REQUEST message includes the *TNL QoS* IE in the *USCH Information* IE and if ALCAP is not used, the Node B may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related USCH.] + +[TDD - If the *USCH Information* IE is present, the Node B shall include in the *USCH Information Response* IE in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and the *Transport Layer Address* IE for the transport bearer to be established for each USCH of this RL.] + +**HS-DSCH:** + +If the *HS-DSCH Information* IE is present in the RADIO LINK SETUP REQUEST message, then: + +- The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. +- The Node B shall include the *HARQ Memory Partitioning* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK SETUP RESPONSE message. [FDD - The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE or the *MIMO with four transmit antennas Activation Indicator* IE or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Mcps TDD- The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.] +- The Node B shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established. +- If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *HS-DSCH Information* IE for an HS-DSCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. +- If the RADIO LINK SETUP REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK SETUP REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. + +- [FDD – If the RADIO LINK SETUP REQUEST message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information* IE , then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK SETUP RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK SETUP REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK SETUP REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Measurement Power Offset* IE in the *HS-DSCH Information* IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK SETUP RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *HS-SICH SIR Target* IE in the *HS-DSCH Information* IE, the Node B shall use this value to determine the HS-SICH SIR Target. The *HS-SICH SIR Target* IE indicates the received UL SIR target of HS-SICH NACK for this UE.] +- If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]). +- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow. +- [FDD - If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.] + +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information IE*, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response IE* in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information IE*, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response IE* in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information IE* with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information IE*, then the Node B may use: ] + - a) - [FDD - a different HS-SCCH in consecutive TTIs for this UE] + - b) - [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information IE* the Node B may use the supported HSDPA functions for this UE. ] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information IE* with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response IE* in the RADIO LINK SETUP RESPONSE message.] +- [1.28Mcps TDD - If the *TSN-Length* IE is included in the *HS-DSCH TDD Information IE*, then the IE is used to indicate the TSN bits applied to the MAC-hs PDU frame.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Number of Supported Carriers* IE in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B shall use this information to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK SETUP REQUEST message includes the *Multi-carrier HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B shall use this information together with the *HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information IE* in the *HS-DSCH Information IE* to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *UE TS0 Capability LCR* IE in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B may use this information in HSDPA resources allocation for the UE.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple carriers and include the *HS-SCCH Specific Information Response LCR per UARFCN* IE in the *HS-DSCH TDD Information Response IE* in the RADIO LINK SETUP RESPONSE message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall include the *HARQ Memory Partitioning per UARFCN* IE in the *HS-DSCH TDD Information Response IE* in the RADIO LINK SETUP RESPONSE message.] + +- [1.28Mcps TDD - If the Node B allows UE to apply HSDPA resources distributed over multiple carriers, the Node B may indicate the number of carriers actually used by the UE and include the *Multi-Carrier number* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the *UsedFrequency* IE in the *HS-SCCH Specific Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the *UARFCN* IE in the *HS-SCCH Specific Information Response LCR per UARFCN* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD - If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] +- If the RADIO LINK SETUP REQUEST message includes the *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *CQI Feedback Cycle2 k* IE and the *CQI Cycle Switch Timer* IE is included in *HS-DSCH FDD Information* IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.] + +#### [FDD - Secondary Serving HS-DSCH:] + +[FDD - If the *Additional HS Cell Information RL Setup* IE is present in the RADIO LINK SETUP REQUEST message, then:] + +- [FDD - The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] + +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.] +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and more than one secondary serving HS-DSCH Radio Link is setup, then the Node B shall use this value in the physical layer.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If Sixtyfour QAM will not be used for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] + +#### **[FDD - Multiflow Setup]:** + +[FDD - If the *Multiflow Information* IE is present in *HS-DSCH FDD Information* IE in the RADIO LINK SETUP REQUEST message, then the Node B shall setup the requested Multiflow operation and then:] + +- [FDD – Use *Total number of HS-DSCH cells* IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] + +- [FDD – Use *Role* IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – Use *MIMO* IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If *Timing* IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B* IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors* IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.] + +#### [FDD - E-DCH]: + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DCH Minimum Set E-TFCI* IE the Node B shall use the value for the related resource allocation operation.] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the Node B shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10].] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DPCH Information* IE, which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the Node B shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18]. ] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK SETUP REQUEST message:] + +- [FDD - The Node B shall setup the requested E-DCH resources on the Radio Links indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *RL specific E-DCH FDD Information* IE for an E-DCH MAC-d flow, then if the *Transport Bearer Not Requested Indicator* IE is not included for this E-DCH MAC-d flow, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. The Node B shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the *Transport Bearer Not Requested Indicator* IE was not included.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for an E-DCH MAC-d flow and:] + +- c) - [FDD - if the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.] +- d) - [FDD - if the Node B does not establish a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related reordering queue.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" the Node B shall assume scheduled grants being configured for the concerned E-DCH MAC-d flow.] +- [FDD - If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [FDD - The Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK SETUP RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B] +- e) - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK SETUP RESPONSE message.] +- f) - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the serving E-DCH RL.] + +- g) - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- h) - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK SETUP RESPONSE message for the serving E-DCH RL.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH ReferencePower Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *UPH Filtering Measurement Forwarding Request* IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] +- [FDD - If the *Serving Cell Change CFN* IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.] +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] +- i) - [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].] + +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-RNTI* IE in the *E-DPCH Information* IE but does not include the *E-RNTI* IE in the *RL Information* IE, the Node B shall use the information to detect the information related to the E-RNTI which is configured in the Node B when the UE was in Cell\_FACH state.] + +**[FDD – Additional E-DCH Setup:]** + +[FDD - If the *Additional E-DCH Cell Information RL Setup Req* IE is present in the RADIO LINK SETUP REQUEST message, then the *Additional E-DCH Cell Information Setup Req* IE defines the new configuration and then:] + +- [FDD - The Node B shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resource on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency. The Node B shall, if supported, use the *Dual Cell E-DCH Operation Enhancements Information* IE for the Secondary uplink frequency if it is included in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE are present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] +- [FDD - If the *Propagation Delay* IE, the *F-DPCH Slot Format* IE and/or the *E-RNTI* IE are present in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Extended Propagation Delay* IE, the *Primary CPICH Usage For Channel Estimation* IE, the *Secondary CPICH Information* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Processing Overload Level* IE, the *E-DCH Minimum Set E-TFCI* IE, the *Implicit Grant handling* IE, the *Minimum TEBS threshold* IE and/or the *DTX Information2* IE are present in the *Additional E-DCH FDD Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [FDD – If the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] +- [FDD - If Separate Iub Transport Bearer Mode is used in the new configuration, then:] + - j) - [FDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the *Transport Bearer Not Requested Indicator* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE to determine the transport bearer configuration in the new configuration for the MAC-d flow of the Secondary Uplink Frequency.] + +- k) - [FDD - If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall include in the RADIO LINK SETUP RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.] +- [FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK SETUP REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the RADIO LINK SETUP RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD – If the Additional Serving E-DCH Radio Link is configured in the Node B, then:] +- l) - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- m) - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2IE*.] +- n) - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and + +include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response IE* in the RADIO LINK SETUP RESPONSE message.] + +- o) - [FDD - If the *Serving Cell Change CFN IE* is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. If the *Serving Cell Change CFN IE* is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link + +**[FDD - E-DCH - HS-DSCH]:** + +[FDD - If the RADIO LINK SETUP REQUEST message includes the DCH Indicator For E-DCH-HSDPA Operation IE, then the Node B shall ignore the DCH Information IE in the RADIO LINK SETUP REQUEST message.] + +**[FDD – E-DCH decoupling operation]** + +[FDD – If the RADIO LINK SETUP REQUEST message includes the *E-DCH Decoupling Indication IE* then the Node B shall if supported use this indication for E-DCH decoupling operation.] + +**[TDD - E-DCH]:** + +[TDD - If the [3.84Mcps TDD - *E-DCH Information IE*] [1.28Mcps TDD - *E-DCH Information 1.28Mcps IE*][7.68Mcps TDD - *E-DCH Information 7.68Mcps IE*] is present in the RADIO LINK SETUP REQUEST message:] + +- [TDD - The Node B shall setup the requested E-DCH resources on the Radio Link indicated by the *E-DCH Serving RL IE*.] +- [TDD - If the *TNL QoS IE* is included in the *E-DCH MAC-d Flows Information TDD IE* for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS IE* may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address IE* and *Binding ID IE* in the *E-DCH MAC-d Flows Information TDD IE* for an E-DCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.] +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List IE* for an E-DCH MAC-d flow in the *E-DCH MAC-d Flows Information TDD IE*, the Node B shall use this information for the related resource allocation operation.] +- [TDD - If in the RADIO LINK SETUP REQUEST message the *E-DCH Grant Type IE* in the *E-DCH MAC-d Flows Information TDD IE* is set to "Non-scheduled" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants are configured for that E-DCH MAC-d flow and shall use the information within the [3.84Mcps - *E-DCH Non-scheduled Grant Information TDD IE*] [1.28Mcps - *E-DCH Non-scheduled Grant Information LCR TDD IE*] [7.68Mcps - *E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE*], if included, for the related resource allocation operation.] +- [TDD - If in the RADIO LINK SETUP REQUEST message the *E-DCH Grant Type IE* in the *E-DCH MAC-d Flows Information TDD IE* is set to "Scheduled" the Node B shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.] +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *MAC-es Guaranteed Bit Rate IE* in the *E-DCH Logical Channel Information IE* in the *E-DCH MAC-d Flows Information TDD IE*, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related queue.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *MAC-es Maximum Bit Rate LCR IE* in the *E-DCH Logical Channel Information IE* in the *E-DCH MAC-d Flows Information TDD IE*, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] + +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [3.84Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH TDD Maximum Bitrate* IE in the *E-DCH TDD Information* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE in the *E-DCH TDD Information LCR* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [7.68Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE in the *E-DCH TDD Information 7.68Mcps* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Processing Overload Level* IE in the [3.84Mcps TDD - *E-DCH TDD Information* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE][1.28Mcps TDD - *E-DCH TDD Information LCR* IE], then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE in the [3.84Mcps TDD - *E-DCH TDD Information* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE], then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Maximum Number of Retransmission for Scheduling Info LCR* IE and the *E-DCH Retransmission timer for Scheduling Info LCR* IE in the *E-DCH TDD Information LCR* IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] +- [3.84Mcps TDD and 7.68Mcps TDD - The Node B shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s), [1.28Mcps - E-HICHs] assigned in the *E-DCH Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- 1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Multi-Carrier E-DCH Physical Layer Category LCR* IE in the *E-DCH TDD Information LCR* IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] +- [1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present and if the RADIO LINK SETUP REQUEST message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] + +#### [1.28 Mcps TDD - Multi-Carrier E-DCH Setup:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information* IE is present in the RADIO LINK SETUP REQUEST message, then the *Multi-Carrier E-DCH Information* IE defines the new configuration and then:] + +- [1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] +- [1.28Mcps TDD - The Node B shall use the corresponding *PRXdes\_base* IE for power control on each uplink frequency according to TS 25.331 [18].] + +- [1.28Mcps TDD - If the *SNPL Carrier Group Indicator* IE is present in the *Multi-Carrier E-DCH Information LCR* IE, the Node B shall use the information to determine which SNPL Carrier Group each frequency indicated by the *UARFCN* IE belongs to.] +- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iub transport bearer mode", the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "E-DCH UL flow multiplexing mode", the Node B shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iub transport bearer.] +- [1.28Mcps TDD - If the Separate Iub transport bearer mode is used in the new configuration, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] +- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] + +## Physical Channels Handling: + +### [FDD - Compressed Mode]: + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE, the Node B shall store the information about the Transmission Gap Pattern Sequences to be used in the Compressed Mode Configuration. This Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or the Node B Communication Context is deleted.] + +[FDD - If the *Downlink Compressed Mode Method* IE in one or more Transmission Gap Pattern Sequence is set to "SF/2" in the RADIO LINK SETUP REQUEST message, the Node B shall use or not the alternate scrambling code as indicated for each DL Channelisation Code in the *Transmission Gap Pattern Sequence Code Information* IE.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE and the *Active Pattern Sequence Information* IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received *CM Configuration Change CFN* refers to the latest passed CFN with that value The Node B shall treat the received *TGCFN* IEs as follows:] + +- [FDD - If any received *TGCFN* IE has the same value as the received *CM Configuration Change CFN* IE, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] +- [FDD - If any received *TGCFN* IE does not have the same value as the received *CM Configuration Change CFN* IE but the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE has already passed, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] +- [FDD - For all other Transmission Gap Pattern Sequences included in the *Active Pattern Sequence Information* IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE for the Transmission Gap Pattern Sequence.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE and the *Active Pattern Sequence Information* IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.] + +#### **[FDD - DL Code Information]:** + +[FDD - When more than one DL DPDCH is assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.212 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "*PhCH number 1*", the second to "*PhCH number 2*", and so on until the *p*th to "*PhCH number p*".] + +#### **[TDD - PDSCH RL ID]:** + +[TDD - If the *PDSCH RL ID* IE is included in RADIO LINK SETUP REQUEST message, the Node B shall use the PDSCH RL ID as an identifier for the PDSCH and/or PUSCH in this radio link.] + +#### **[FDD - Phase Reference Handling]:** + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Primary CPICH Usage For Channel Estimation* IE and has the value "Primary CPICH shall not be used", the Node B shall assume that the UE is not using the Primary CPICH for channel estimation. If the RADIO LINK SETUP REQUEST message does not include the *Primary CPICH Usage For Channel Estimation* IE or includes the *Primary CPICH Usage For Channel Estimation* IE and has the value "Primary CPICH may be used", the Node B shall assume that the UE may use the Primary CPICH for channel estimation.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Secondary CPICH Information* IE, the Node B shall assume that the UE may use the Secondary CPICH indicated by the *Common Physical Channel ID* IE for channel estimation.] + +#### **General:** + +[FDD - If the *Propagation Delay* IE and optionally the *Extended Propagation Delay* IE are included, the Node B may use this information to speed up the detection of L1 synchronisation.] + +[FDD - The *UL SIR Target* IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control.] + +[1.28Mcps TDD - The *UL SIR Target* IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21].] + +[FDD - If the received *Limited Power Increase* IE is set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control.] + +[1.28Mcps TDD - If the *UL CCTrCH Information* IE includes the *TDD TPC UL Step Size* IE, the Node B shall configure the uplink TPC step size according to the parameters given in the message.] + +[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the *TDD TPC DL Step Size* IE of the lowest numbered DL CCTrCH whose *DL CCTrCH Information* IE includes the *TDD TPC DL Step Size* IE.] + +[1.28 Mcps TDD - If no *TDD TPC DL Step Size* IE is included in the *DL CCTrCH Information* IE, the Node B shall use the *E-AGCH TPC step size* IE in the *E-PUCH Information LCR* IE in the *E-DCH Information 1.28Mcps* IE for HS-SCCH inner loop power control related operation.] + +[1.28Mcps TDD - If the *UL Timeslot Information LCR* IE includes the *PLCCH Information* IE, the Node B shall transmit TPC /SS bits on a PLCCH according to the parameters given in the message.] + +#### **[FDD - DPCH Handling]:** + +[FDD - If the *UL DPDCH Indicator For E-DCH Operation* IE is set to "UL DPDCH not present", the *Min UL Channelisation Code Length* IE, the *Puncture Limit* IE and the *TFCS* IE within the *UL DPCH Information* IE shall be ignored and no UL DPDCH resources shall be allocated.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *DL DPCH Information* IE, then the Node B shall configure the concerned Node B Communication Context to use DPCH in the downlink, i.e. with a DL DPCCH and a DL DPDCH.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *F-DPCH Information* IE, then the Node B shall configure the concerned Node B Communication Context to use F-DPCH in the downlink, i.e. with transmission of only the TPC field.] + +#### **[FDD - Continuous Packet Connectivity Handling]:** + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:] + +[FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].] + +[FDD - If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] + +- [FDD - If *UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] +- [FDD - If *Inactivity Threshold for UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:] + +- [FDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].] +- [FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD - If at least one of *HS-PDSCH Second Code Support* IE is set to "True", then the Node B shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK SETUP RESPONSE message.] + +#### **[1.28 Mcps TDD - Continuous Packet Connectivity Handling]:** + +[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message.] + +[1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the *Enabling Delay Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].] + +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allocated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD – The Node B shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD – The Node B shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allocated E-DCH Semi-persistent resource* IE in the RADIO LINK SETUP RESPONSE message.] + +#### **[1.28 Mcps TDD - MU-MIMO Handling:]** + +[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *MU-MIMO Information* IE, then:] + +- [1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the *MU-MIMO indicator* IE and shall include the *MU-MIMO Information Response* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information* IE is included in the *MU-MIMO Information* IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information request* IE is included in the *MU-MIMO Information* IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK SETUP RESPONSE message, else the Node B shall not include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK SETUP RESPONSE message].] + +#### **[FDD - UL CLTD Handling:]** + +[FDD - If the *UL CLTD Information* IE is present in the RADIO LINK SETUP REQUEST message, then the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights and then :] + +- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] +- [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.] + +#### **[FDD - UL MIMO Setup:]** + +[FDD - If the *UL MIMO Information* IE is present in the RADIO LINK SETUP REQUEST message, then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.] + +- [FDD - If the RADIO LINK SETUP REQUEST message includes the *Serving E-DCH RL IE* indicating that the Serving E-DCH RL is in this Node B] +- p) - [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information IE* in the RADIO LINK SETUP RESPONSE message. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] +- q) - [FDD - If the RADIO LINK SETUP REQUEST message includes the *E-ROCH Power Offset IE* in the *UL MIMO Information IE*, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] +- [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence IE* in *UL MIMO DL Control Channel Information IE* in the RADIO LINK SETUP RESPONSE message for every RL indicated by the *E-DCH RL Indication IE*, set to "E-DCH", in the *RL Information IE* and it should include it for the Serving E-DCH RL.] + +## Radio Link Handling: + +### [FDD - Transmit Diversity]: + +[FDD - When the *Diversity Mode IE* is set to "STTD" or "Closedloop mode1", the Node B shall activate/deactivate the Transmit Diversity for each Radio Link in accordance with the *Transmit Diversity Indication IE*] + +[FDD - If the *Diversity Mode IE* is included in the *HS-DSCH FDD Secondary Serving Information IE* in the *Additional HS Cell Information RL Setup IE* in the RADIO LINK SETUP REQUEST message, the Node B shall apply cell specific transmit diversity configuration and if the *Diversity Mode IE* is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator IE* in the *HS-DSCH FDD Secondary Serving Information IE*.] + +### DL Power Control: + +[FDD - The Node B shall start any DL transmission using the initial DL power specified in the message on each DL DPCH or on the F-DPCH of the RL until either UL synchronisation on the Uu interface is achieved for the RLS or Power Balancing is activated. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) and the power control procedure (see subclause 8.3.7), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message. If the Node B Communication Context is configured to use DPCH in the downlink, during compressed mode, the $\delta P_{curr}$ , as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] + +[FDD - If the *DPC Mode IE* is present in the RADIO LINK SETUP REQUEST message, the Node B shall apply the DPC mode indicated in the message and be prepared that the DPC mode may be changed during the lifetime of the RL. If the *DPC Mode IE* is not present in the RADIO LINK SETUP REQUEST message, DPC mode 0 shall be applied (see ref. TS 25.214 [10]).] + +[3.84 Mcps TDD and 7.68Mcps TDD - The Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Initial DL Transmission Power IE* is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the *Initial DL Transmission Power IE* included in the *RL Information IE*. The Node B shall start any DL transmission on each DCH type CCTrCH using the initial CCTrCH DL power, as determined above, on each DL DPCH and on each Time Slot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.] + +[3.84 Mcps TDD and 7.68Mcps TDD - The Node B shall determine the maximum DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power IE* is included for + +that CCTrCH, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum DL Power* IE included in the *RL Information* IE.] + +[3.84 Mcps TDD and 7.68 Mcps TDD - The Node B shall determine the minimum DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum DL Power* IE included in the *RL Information* IE.] + +[3.84 Mcps TDD and 7.68 Mcps TDD - The initial power, maximum power, and minimum power for DSCH type CCTrCH shall be determined as follows: + +- If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs. +- If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol]. + +[1.28 Mcps TDD - The Node B shall determine the initial DL power for each timeslot within the DCH type CCTrCH by the following rule: If the *Initial DL Transmission Power* IE is included in the *DL Timeslot Information LCR* IE, then the Node B shall use that power for the Initial DL Power and ignore the *DL Time Slot ISCP info LCR* IE, otherwise the initial DL Power is the *Initial DL Transmission Power* IE included in the *RL Information* IE and if *DL Time Slot ISCP info LCR* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall start any DL transmission on each timeslot within each DCH type CCTrCH using the initial DL power, as determined above, on each DL DPCH and on each timeslot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.] + +[1.28 Mcps TDD - The Node B shall determine the maximum DL power for each timeslot within the DCH type CCTrCH by the following rule: If the *Maximum DL Power* IE is included in the *DL Timeslot Information LCR* IE, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum DL Power* IE included in the *RL Information* IE.] + +[1.28 Mcps TDD - The Node B shall determine the minimum DL power for each timeslot within the DCH type CCTrCH by the following rule: If the *Minimum DL Power* IE is included in the *DL Timeslot Information LCR* IE, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum DL Power* IE included in the *RL Information* IE.] + +[1.28 Mcps TDD - The Node B shall determine the initial power for each timeslot within the DSCH type CCTrCH by the following rule: If both the *CCTrCH Initial DL Transmission Power* IE, included in the *DL CCTrCH Information* IE, and the *DL Time Slot ISCP Info LCR* IE, included in the *RL Information* IE, are included then the Node B shall use that power for the PDSCH and ignore the *Initial DL Transmission Power* IE included in the *RL Information* IE, otherwise the initial DL Power is the *Initial DL Transmission Power* IE included in the *RL Information* IE and if *DL Time Slot ISCP info LCR* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall start any DL transmission on each timeslot within each DSCH type CCTrCH using the initial DL power, as determined above, on each DL PDSCH and on each timeslot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.] + +[1.28 Mcps TDD - The Node B shall determine the maximum DL power for each timeslot within the DSCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power* IE, included in the + +*DL CCTrCH Information* IE, is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum DL Power* IE included in the *RL Information* IE.] + +[1.28 Mcps TDD - The Node B shall determine the minimum DL power for each timeslot within the DSCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE, included in the *DL CCTrCH Information* IE, is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum DL Power* IE included in the *RL Information* IE.] + +[3.84Mcps TDD and 7.68Mcps TDD - If the *DL Time Slot ISCP Info* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.] + +[FDD - If the received *Inner Loop DL PC Status* IE is set to "Active", the Node B shall activate the inner loop DL power control for all RLs. If *Inner Loop DL PC Status* IE is set to "Inactive", the Node B shall deactivate the inner loop DL power control for all RLs according to ref. TS 25.214 [10].] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *DL Power Balancing Information* IE and the *Power Adjustment Type* IE is set to "Common" or "Individual", the Node B shall activate the power balancing, if activation of power balancing by the RADIO LINK SETUP REQUEST message is supported, according to subclause 8.3.7, using the *DL Power Balancing Information* IE. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. *Pinit* shall be set to the power level indicated by the *Initial DL Transmission Power* IE.] + +[FDD - If activation of power balancing by the RADIO LINK SETUP REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message.] + +#### **[1.28Mcps TDD - Uplink Synchronisation Parameters LCR]:** + +[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message contains the *Uplink Synchronisation Parameters LCR* IE, the Node B shall use the indicated values of *Uplink Synchronisation Stepsize* IE and *Uplink Synchronisation Frequency* IE when evaluating the timing of the UL synchronisation.] + +#### **[1.28Mcps TDD - Power Control GAP]:** + +[1.28Mcps TDD - If the *Power Control GAP* IE is included in the RADIO LINK SETUP REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].] + +#### **[1.28Mcps TDD - E-UTRAN Inter-RAT measurement]:** + +[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Idle Interval Information* IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to the TS 25.331 [18].] + +#### **[1.28Mcps TDD - HS-DSCH-RNTI for FACH]:** + +[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH-RNTI for FACH* IE, if supported, the Node B shall store this information and include the *E-RNTI for FACH* IE in the RADIO LINK SETUP RESPONSE message.] + +#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement]:** + +[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] + +#### **[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]** + +[FDD – If the RADIO LINK SETUP REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE for a Radio Link not indicated by the *HS-PDSCH RL ID* IE the Node B shall if + +supported preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [49:] + +- [FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK SETUP REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *C-IDs* in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK SETUP REQUEST message.] +- [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:] + - [FDD – - by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell] + - [FDD – - by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells] +- [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].] +- [FDD – The Node B shall return these codes in the *Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message.] +- [FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell's HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].] +- [FDD – The Node B shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message, IEs according to the rules defined for HS-DSCH Setup and:] + - [FDD – - if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE] + - [FDD – - if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – - if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell] + - [FDD – - if Sixtyfour QAM Usage Allowed Indicator is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell] + +- [FDD -- if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE] +- [FDD -- if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall store this information in the preconfigured configuration.] +- [FDD -- if the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B may store this information in the preconfigured configuration.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD – The Node B shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] + - [FDD -- The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] + - [FDD -- The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *E-DCH Indicator* IE for a secondary cell, the Node B shall include in the *Additional E-DCH Preconfiguration Information* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK SETUP RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK SETUP FAILURE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator* IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] + - [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] + - [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.] + +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.] + +[FDD – If the RADIO LINK SETUP REQUEST message includes the *Non-Serving RL Preconfiguration Setup* IE in the *RL Information* IE and:] + +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK SETUP RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK SETUP RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK SETUP RESPONSE message.] +- [FDD –If the *F-TPICH Information* IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].] + +#### [1.28Mcps TDD – Non-rectangular resource operation:] + +[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message contains the *UE support of non-rectangular resource allocation* IE, the Node B shall, if supported, use this information to determine whether includes the *Non-rectangular resource allocation indicator* IE and the *Non-rectangular resource timeslot set* IE or not.] + +#### [FDD – UL DPCCH2 Handling:] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *UL DPCCH2 Information* IE, then:] + +- [FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].] +- [FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.] + +- [FDD – If the *UL DPCCH2 Information* IE includes the *Extended E-DPCCH Power Offset* IE and if the *E-DCH FDD Information* IE is present in the RADIO LINK SETUP REQUEST message, the Node B shall use the value to calculate the E-DPCCH gain factor.] + +**[FDD – Downlink TPC enhancements Handling:]** + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Downlink TPC enhancements Information* IE, then:] + +- [FDD – The Node B shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *RL Information* is included in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCH Cell Information RL Setup Req* is included in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +**General:** + +If the RADIO LINK SETUP REQUEST message includes the *RL Specific DCH Information* IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs. + +The Node B shall start reception on the new RL(s) after the RLs are successfully established. + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Synchronisation Indicator* IE, set to "Timing Maintained Synchronisation", the Node B shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10].] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Initial DL DPCH Timing Adjustment Allowed* IE, then the Node B may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the Node B shall include, for the concerned Radio Link(s), the *Initial DL DPCH Timing Adjustment* IE in the *Radio Link Information Response* IE in the RADIO LINK SETUP RESPONSE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *F-DPCH Slot Format* IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *E-RNTI* IE in the *RL Information* IE, the Node B shall use the information to detect the information related to the E-RNTI which is configured in the Node B when the UE was in Cell\_FACH state.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *F-TPICH Information* IE in the *RL Information* IE, the Node B shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] + +**[FDD - Radio Link Set Handling:]** + +[FDD - The *First RLS Indicator* IE indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The *First RLS Indicator* IE shall be used by the Node B together with the value of the *DL TPC Pattern 01 Count* IE which the Node B has received in the Cell Setup procedure, to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.] + +[FDD - For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the *RL Set ID* IE included in the RADIO LINK SETUP RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Sets shall not be common.] + +[FDD - For all RLs having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the *RL Set ID* IE included in the RADIO LINK SETUP RESPONSE message the same value. This value shall + +uniquely identify the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.] + +[FDD - The UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N\_INSYNC\_IND, that are configured in the cells supporting the radio links of the RL Set.] + +[FDD - For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the *E-DCH RL Set ID* IE in the RADIO LINK SETUP RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] + +**[FDD – Radio Links without DPCH/F-DPCH operation]** + +[FDD – If the *Radio Links without DPCH/F-DPCH Indication* IE is present in the RADIO LINK SETUP REQUEST message:] + +- [FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.] + +**Response Message:** + +If the RLs are successfully established, the Node B shall and respond with a RADIO LINK SETUP RESPONSE message. + +After sending the RADIO LINK SETUP RESPONSE message the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface. + +For each RL for which the *Delayed Activation* IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall: + +- [FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].] +- [TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].] + +For each RL for which the *Delayed Activation* IE is included in the RADIO LINK SETUP REQUEST message, the Node B shall: + +- if the *Delayed Activation* IE indicates "Separate Indication": + - not start any DL transmission for the concerned RL on the Uu interface; +- if the *Delayed Activation* IE indicates "CFN": + - [FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the *Activation CFN* IE.] + - [TDD - start transmission on the new RL at the CFN indicated in the *Activation CFN* IE as specified in TS 25.427 [16].] + +### 8.2.17.3 Unsuccessful Operation + +![Sequence diagram showing the Radio Link Setup procedure for an Unsuccessful Operation. A CRNC sends a RADIO LINK SETUP REQUEST to a Node B, and the Node B responds with a RADIO LINK SETUP FAILURE.](40b3d859722c55c5cc5f8512aaefa01a_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: RADIO LINK SETUP REQUEST + CRNC->>Node B: RADIO LINK SETUP REQUEST + Note left of Node B: RADIO LINK SETUP FAILURE + Node B-->>CRNC: RADIO LINK SETUP FAILURE + +``` + +Sequence diagram showing the Radio Link Setup procedure for an Unsuccessful Operation. A CRNC sends a RADIO LINK SETUP REQUEST to a Node B, and the Node B responds with a RADIO LINK SETUP FAILURE. + +**Figure 25: Radio Link Setup procedure, Unsuccessful Operation** + +If the establishment of at least one radio link is unsuccessful, the Node B shall respond with a RADIO LINK SETUP FAILURE message. The message contains the failure cause in the *Cause* IE. + +[FDD - If some radio links were established successfully, the Node B shall indicate this in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. In this case, the Node B shall include the *Communication Control Port Id* IE in the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RL identified by the *HS-PDSCH RL ID* IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the *HS-DSCH FDD Information Response* IE in the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RL identified by the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK SETUP FAILURE message. If the establishment of the RL identified by the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE, i.e. secondary serving HS-DSCH Radio Link is unsuccessful but the establishment of the RL identified by the *HS-PDSCH RL ID* IE for the serving HS-DSCH Radio Link is successful, then the Node B shall indicate the unsuccessful secondary serving HS-DSCH Radio Link in the *Unsuccessful RL Information Response* IE in the RADIO LINK SETUP FAILURE message by setting the *RL ID* IE to the same value as the unsuccessful *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Setup* IE.] + +[FDD - If the RL identified by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. If the establishment of the RL identified by the *E-DCH Additional RL ID* IE is unsuccessful, then the Node B shall indicate the unsuccessful setup of the Additional E-DCH Radio Link in the *Unsuccessful RL Information Response* IE in the RADIO LINK SETUP FAILURE message by setting the *RL ID* IE to the same value as the unsuccessful *E-DCH Additional RL ID* IE in the *Additional E-DCH Cell Information Setup* IE.] + +Typical cause values are as follows: + +#### **Radio Network Layer Cause:** + +- Combining not supported +- Combining Resources not available +- Requested Tx Diversity Mode not supported +- Number of DL codes not supported +- Number of UL codes not supported +- UL SF not supported +- DL SF not supported +- Dedicated Transport Channel Type not supported +- Downlink Shared Channel Type not supported +- Uplink Shared Channel Type not supported +- CM not supported +- [FDD - DPC mode change not supported] +- Delayed Activation not supported +- F-DPCH not supported +- [FDD - Continuous Packet Connectivity DTX-DRX operation not available] +- [FDD - Continuous Packet Connectivity UE DTX Cycle not available] + +- [FDD - MIMO not available] +- E-DCH MAC-d PDU Size Format not available +- [FDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - Multi Cell operation not available.] +- [1.28Mcps TDD- MIMO not available] +- [1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - TX diversity for MIMO UE on DL Control Channels not available] +- [FDD – Single Stream MIMO not available] +- [FDD - Multi Cell operation with MIMO not available] +- [FDD - Multi Cell operation with Single Stream MIMO not available] +- [FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available] +- [FDD - Multi Cell E-DCH operation not available] +- [FDD – Frequency Specific Compressed mode operation not available] +- [FDD - UL CLTD operation not available] +- [FDD - MIMO with four transmit antennas not available] +- [FDD - Dual Stream MIMO with four transmit antennas not available] +- [FDD – Multiflow operation not available] +- [FDD - SixtyfourQAM UL operation not available] +- [FDD – UL MIMO operation not available] +- [FDD – UL MIMO and SixteenQAM operation not available] +- [FDD – UL MIMO and SixtyfourQAM operation not available] +- [FDD – E-DCH decoupling operation not available] +- [FDD – Basic DCH Enhancements operation not available] +- [FDD – Full DCH Enhancements operation not available] +- [FDD – Radio Links without DPCH/F-DPCH operation not available] +- [FDD –UL DPCCH2 operation not available] +- [FDD –Downlink TPC enhancements operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with different TTI operation not available] + +**Transport Layer Cause:** + +- Transport Resources Unavailable + +**Miscellaneous Cause:** + +- O&M Intervention +- Control processing overload +- HW failure + +#### 8.2.17.4 Abnormal Conditions + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Active Pattern Sequence Information* IE, but the *Transmission Gap Pattern Sequence Information* IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected"], the Node B shall regard the Radio Link Setup procedure as failed and shall respond with a RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message includes a *DCH Information* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCH Information* IE do not have the same *Transmission Time Interval* IE in the *Semi-static Transport Format Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message includes the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE or *RL Specific E-DCH Information* IE included in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to "Must" [FDD - or the RL is combined with an E-DCH RL previously listed in the RADIO LINK SETUP RESPONSE message], the Node B shall regard the Radio Link Setup procedure as failed and respond with the RADIO LINK SETUP FAILURE message. + +If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to "May", the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. + +If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to "Must Not", the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. + +If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE for the first RL in the *RL Information* IE and/or [FDD - in the *RL Specific E-DCH Information* IE in the *RL Information* IE for the first E-DCH RL][TDD – in the *E-DCH MAC-d Flows Information TDD* IE], the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. + +If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for an HS-DSCH MAC-d Flow in the *HS-DSCH MAC-d Flows Information* IE, the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. + +[TDD - If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for a DSCH in the *DSCH TDD Information* IE and/or for an USCH in the *USCH Information* IE, the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.] + +If the RADIO LINK SETUP REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message includes an *HS-PDSCH RL-ID* IE for a serving HS-DSCH not referring to one of the radio links to be established, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message contains the *HS-DSCH Information* IE and if the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value "Flexible MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +[FDD - If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[TDD - If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Synchronisation Indicator* IE, set to "Timing Maintained Synchronisation", and if the *First RLS indicator* IE is set to "not first RLS", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *HS-DSCH Information* IE and if the *Measurement Power Offset* IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *F-DPCH Information* IE and the *DL DPCH Information* IE configured simultaneously to one downlink frequency, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Active Pattern Sequence Information* IE, which activates a transmission gap pattern sequence with an SF/2 downlink compressed mode method, and if the concerned Node B Communication Context is configured to use DPCH in downlink and the Transmission Gap Pattern Sequence Code Information is not available for any Radio Link, the Node B shall reject the Radio Link Setup procedure using the RADIO LINK SETUP FAILURE message with the cause value "Invalid CM Settings".] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Primary CPICH Usage For Channel Estimation* IE set to the value "Primary CPICH shall not be used" and doesn't include the *Secondary CPICH Information* IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes one of the *Not Used* IEs, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *E-DCH RL Indication* IE set to "E-DCH", but does not contain the *E-DCH FDD Information* IE, or if the message contains the *E-DCH FDD Information* IE, but does not contain the *E-DCH RL Indication* IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +If the RADIO LINK SETUP REQUEST message does not contain the *E-DCH Decoupling Indication* IE but contains the *HS-PDSCH RL ID* IE and the *Serving E-DCH RL* IE, and the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not configured to be in the same cell, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *HS-PDSCH RL ID* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as "HS-DSCH not configured" then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *E-DPCH Information* IE but does not contain the *UL DPDCH Indicator For E-DCH Operation* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Serving Cell Change CFN* IE, but neither the *Serving E-DCH RL* IE nor *HS-DSCH Information* IE is included, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Transport Bearer Not Requested Indicator* IE for a DCH, but does not contain the *Unidirectional DCH indicator* IE set to "Uplink DCH only" in the *DCH Specific Info* IE for the DCH, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[1.28Mcps TDD - For a multi-frequency cell, if the *UARFCN* IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall reject the procedure by sending the RADIO LINK SETUP FAILURE message.] + +[1.28Mcps TDD - For the cell in which only one frequency is configured, if the *UARFCN* IE is included in the RADIO LINK SETUP REQUEST message, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains the *UL DPCCH Slot Format* set to "4" but does not contain the *F-DPCH Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains the *UL DPCCH Slot Format* set to "0" or "2" and the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the *UL DPCH Information* IE in the RADIO LINK SETUP REQUEST message contains *Diversity Mode* IE set to "Closed loop mode 1" and *UL DPCCH Slot Format* not set to "2" or "3", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *MIMO Activation Indicator* IE, *Sixtyfour QAM Usage Allowed Indicator* IE set to "Allowed", the the *Additional HS Cell Information RL Setup* IE, the *Single Stream MIMO Activation Indicator* IE, the *MIMO with four transmit antennas Activation Indicator* IE and/or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE but does not contain the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD – If the RADIO LINK SETUP REQUEST message contains the *Continuous Packet Connectivity DTX-DRX Information* IE but does not contain the *F-DPCH Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message] + +[FDD – If the RADIO LINK SETUP REQUEST message contains the *Serving E-DCH RL ID* IE but contains the *Transport Bearer Not Requested Indicator* IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH for a specific RL and the specific RL is combined with RL which the transport bearer is configured to be established for the DCH, previously listed in the RADIO LINK SETUP RESPONSE message in the Node B, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE and if the *HS-DSCH Information* IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +If the RADIO LINK SETUP REQUEST message includes the *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE set to "Flexible RLC PDU Size", and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +If the RADIO LINK SETUP REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, and the *DL RLC PDU Size Format* IE in the *HS-DSCH Information* IE has the value "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message. + +[FDD - If the RADIO LINK SETUP REQUEST message contains a *MIMO Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Setup* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Setup* IE the *Diversity Mode* IE not set to "None" but not the + +*Transmit Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode* IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and if the *E-DPCH Information* IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional E-DCH Cell Information RL Setup Req* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE containing more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are received in the *Ordinal Number Of Frequency* IE in the in the *HS-DSCH FDD Secondary Serving Information* IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Additional HS Cell Information RL Setup* IE containing more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message with the cause value "Invalid CM settings".] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *UL MIMO Information* IE in *E-DCH FDD Information* IE but does not contain the *UL CLTD Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message contains the *DCH Enhancements Information* IE, and either the *DL DPCH Slot Format* IE is not set to "17" or "18", or the *UL DPCCH Slot Format* IE is not set to "5", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the RADIO LINK SETUP REQUEST message does not contain the *DCH Enhancements Information* IE, and either (i) the *DL DPCH Slot Format* IE is set to "17", or (ii) the *DL DPCH Slot Format* IE is set to "18", or (iii) the *UL DPCCH Slot Format* IE is set to "5", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup but the *Dual Cell E-DCH Operation Enhancements Information* IE is not included in the RADIO LINK SETUP REQUEST message, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup and if the *Continuous Packet Connectivity DTX-DRX Information* IE is included in the RADIO LINK SETUP REQUEST message, but the *DTX Information* IE does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.] + +## 8.2.18 Physical Shared Channel Reconfiguration + +### 8.2.18.1 General + +This procedure is used to assign HS-DSCH related resources to the Node B. + +[TDD - This procedure is also used for handling PDSCH Sets and PUSCH Sets in the Node B, i.e. + +- Adding new PDSCH Sets and/or PUSCH Sets, +- Modifying these, and +- Deleting them.] + +This procedure is also used to assign E-DCH related resources to the Node B. + +### 8.2.18.2 Successful Operation + +![Sequence diagram showing the successful operation of Physical Shared Channel Reconfiguration. A CRNC sends a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message to a Node B, and the Node B responds with a PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.](eb92aaf8c058798b58d42d889c556d36_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST + CRNC->>Node B: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST + Note left of Node B: PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE + Node B-->>CRNC: PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE + +``` + +Sequence diagram showing the successful operation of Physical Shared Channel Reconfiguration. A CRNC sends a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message to a Node B, and the Node B responds with a PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. + +**Figure 26: Physical Shared Channel Reconfiguration, Successful Operation** + +The procedure is initiated with a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall activate the new configuration at the head boundary of the SFN according to the parameters given in the message. + +If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes an *SFN* IE, the Node B shall activate the new configuration at the head boundary of that specified SFN. If no *SFN* IE is included Node B shall activate the new configuration immediately. + +#### E-DCH and HS-DSCH Resources: + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power* IE, the Node B shall not exceed this maximum transmission power on all HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes in the cell. If a value has never been set or if the value of the *HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power* IE is equal to or greater than the maximum transmission power of the cell the Node B may use all unused power for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH And E-HICH Total Power* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall not exceed this maximum transmission power on all HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes in the cell portion indicated by *Cell Portion ID* IE. If a value has never been set or if the value of the *HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH And E-HICH Total Power* IE for the cell portion is equal to or greater than the maximum transmission power of the cell portion, the Node B may use all unused power for HS-PDSCH, HS-SCCH and E-AGCH, E-RGCH and E-HICH codes.] + +#### HS-DSCH Resources: + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH And HS-SCCH Scrambling Code* IE, the Node B shall use this as the scrambling code for all HS-PDSCHs and HS-SCCHs. If a value has never been set, the Node B shall use the primary scrambling code for all HS-PDSCH and HS-SCCH codes.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH FDD Code Information* IE, the Node B shall: + +- if the *Number Of HS-PDSCH Codes* IE is set to "0", delete any existing HS-PDSCH resources from the cell. +- if the *Number Of HS-PDSCH Codes* IE is set to any value other than "0" and HS-PDSCH resources are not currently configured in the cell, use this list as the range of codes for HS-PDSCH channels. +- if the *Number Of HS-PDSCH Codes* IE is set to any value other than "0" and HS-PDSCH resources are currently configured in the cell, replace the current range of codes with this new range of codes for HS-PDSCH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-SCCH FDD Code Information* IE, the Node B shall: + +- If the *HS-SCCH FDD Code Information* IE contains no codes, delete any existing HS-SCCH resources from the cell. +- If the *HS-SCCH FDD Code Information* IE contains one or more codes and HS-SCCH resources are not currently configured in the cell, use this list of codes as the list of codes for HS-SCCH channels. +- If the *HS-SCCH FDD Code Information* IE contains one or more codes and HS-SCCH resources are currently configured in the cell, replace the current list of codes with this new list of codes for HS-SCCH channels.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH and HS-SCCH Total Power* IE [1.28 Mcps TDD – or *HS-PDSCH and HS-SCCH Total Power per CELL PORTION* IE in the *DL Timeslot and Code Information LCR per UARFCN* IE] for a particular timeslot, the Node B shall not exceed this maximum transmission power on all HS-PDSCH and HS-SCCH codes in that timeslot. If a value has never been set for that timeslot or if the value of the *HS-PDSCH and HS-SCCH Total Power* IE for that timeslot is equal to or greater than the maximum transmission power of the cell the Node B may use all unused power in that timeslot for HS-PDSCH and HS-SCCH codes.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH TDD Information* IE, the Node B shall: + +- If the *HS-PDSCH TDD Information* IE contains no [3.84 Mcps TDD - *DL Timeslot and Code Information* IE] [1.28 Mcps TDD - *DL Timeslot and Code Information LCR per UARFCN* IE] [7.68 Mcps TDD - *DL Timeslot and Code Information 7.68Mcps* IE], delete any existing HS-PDSCH resources from the cell. +- If the *HS-PDSCH TDD Information* IE contains [3.84 Mcps TDD - *DL Timeslot and Code Information* IE] [1.28 Mcps TDD - *DL Timeslot and Code Information LCR* IE] [7.68 Mcps TDD - *DL Timeslot and Code Information 7.68Mcps* IE] and HS-PDSCH resources are not currently configured in the cell, use this IE as the list of timeslots / codes for HS-PDSCH channels. +- If the *HS-PDSCH TDD Information* IE contains [3.84 Mcps TDD - *DL Timeslot and Code Information* IE] [1.28 Mcps TDD - *DL Timeslot and Code Information LCR* IE] [7.68 Mcps TDD - *DL Timeslot and Code Information 7.68Mcps* IE] and HS-PDSCH resources are currently configured in the cell, replace the current list of timeslots / codes with this new list of timeslots / codes for HS-PDSCH channels.] +- [1.28Mcps TDD - If the *HS-PDSCH TDD Information* IE contains any *DL Timeslot and Code Information LCR per UARFCN* IE and HS-PDSCH resources are not currently configured on the indicated frequency within the cell, use this IE as the list of frequency / timeslots / codes for HS-PDSCH channels on the frequency, the HSDPA resources on other frequency shall remain unchanged.] +- [1.28Mcps TDD - If the *HS-PDSCH TDD Information* IE contains any *DL Timeslot and Code Information LCR per UARFCN* IE and HS-PDSCH resources are currently configured on the indicated frequency within the cell, the current list of frequency / timeslots / codes shall be replaced with this new list of frequency / timeslots / codes for HS-PDSCH channels on this frequency, the HSDPA resources on other frequency/frequencies shall remain unchanged.] + +- [1.28Mcps TDD - If the *DL Timeslot and Code Information LCR per UARFCN* IE contains no *DL Timeslot and Code Information LCR* IE but contains *UARFCN* IE, the existing HS-PDSCH resources on the frequency indicated by the *UARFCN* IE shall be deleted, the HSDPA resources on other frequency/frequencies shall remain unchanged.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Add to HS-SCCH Resource Pool* IE, the Node B shall add this resource to the HS-SCCH resource pool to be used to assign HS-SCCH sets.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify HS-SCCH Resource Pool* IEs and includes any of [3.84Mcps TDD - *TDD Channelisation Code* IE, *Midamble Shift and Burst Type* IE, *Time Slot* IE], [1.28Mcps TDD - *First TDD Channelisation Code* IE, *Second TDD Channelisation Code* IE, *Midamble Shift LCR* IE, *Time Slot LCR* IE, *TDD Channelisation Code* IE], [7.68Mcps TDD - *TDD Channelisation Code 7.68Mcps* IE, *Midamble Shift and Burst Type 7.68Mcps* IE, *Time Slot* IE], for either HS-SCCH or HS-SICH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify HS-SCCH Resource Pool* IEs and includes any *UARFCN* IEs related to HS-SCCH or HS-SICH channels, the Node B shall apply these configurations on the new frequency, otherwise the old frequency is still applicable.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify HS-SCCH Resource Pool* IEs and includes the *HS-SCCH Maximum Power* IE, the Node B shall apply this value for the specified HS-SCCH code otherwise the old value is still applicable.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify HS-SCCH Resource Pool* IEs and includes the *HS-SICH Reference Signal Information* IE in the *HS-SICH Reference Signal Information Modify* IE, the Node B shall apply this HS-SICH reference signal configuration. Else if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify HS-SCCH Resource Pool* IEs and includes the *HS-SICH Reference Signal Modify* IE but does not contain the *HS-SICH Reference Signal Information* IE in the *HS-SICH Reference Signal Modify* IE, the Node B shall delete this HS-SICH reference signal configuration for the specified HS-SCCH. Otherwise the old configuration is still applicable.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Delete from HS-SCCH Resource Pool* IEs, the Node B shall delete these resources from the HS-SCCH resource pool.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Add to Non-HS-SCCH associated HS-SICH Resource Pool* IEs and includes *UARFCN* IEs related to HS-SICH channel, the Node B shall add this resource to the non-HS-SCCH associated HS-SICH resource pool on the indicated frequency, otherwise the Node B shall add this resource to the non-HS-SCCH associated HS-SICH resource pool on the primary frequency.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Modify Non-HS-SCCH associated HS-SICH Resource Pool* IEs and includes *UARFCN* IEs related to HS-SICH channel, the Node B shall apply these configurations on the new frequency, otherwise the old frequency is still applicable.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Delete from Non-HS-SCCH associated HS-SICH Resource Pool* IEs, the Node B shall delete these resources from the non-HS-SCCH associated HS-SICH resource pool.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH And HS-SCCH Scrambling Code* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall use this as the scrambling code for all HS-PDSCHs and HS-SCCHs for the cell portion indicated by Cell Portion ID. If a value has never been set, the Node B shall use the primary scrambling code for all HS-PDSCH and HS-SCCH codes for the cell portion indicated by Cell Portion ID.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-PDSCH FDD Code Information* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall: + +- if the *Number Of HS-PDSCH Codes* IE is set to "0", delete any existing HS-PDSCH resources from the cell portion indicated by *Cell Portion ID* IE. + +- if the *Number Of HS-PDSCH Codes* IE is set to any value other than "0" and HS-PDSCH resources are not currently configured in the cell portion indicated by *Cell Portion ID* IE, use this list as the range of codes for HS-PDSCH channels. +- if the *Number Of HS-PDSCH Codes* IE is set to any value other than "0" and HS-PDSCH resources are currently configured in the cell portion indicated by *Cell Portion ID* IE, replace the current range of codes with this new range of codes for HS-PDSCH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-SCCH FDD Code Information* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall: + +- If the *HS-SCCH FDD Code Information* IE contains no codes, delete any existing HS-SCCH resources from the cell portion indicated by *Cell Portion ID* IE. +- If the *HS-SCCH FDD Code Information* IE contains one or more codes and HS-SCCH resources are not currently configured in the cell portion indicated by *Cell Portion ID* IE, use this list of codes as the list of codes for HS-SCCH channels. +- If the *HS-SCCH FDD Code Information* IE contains one or more codes and HS-SCCH resources are currently configured in the cell portion indicated by *Cell Portion ID* IE, replace the current list of codes with this new list of codes for HS-SCCH channels.] + +#### [FDD - Enhanced Cell\_FACH Operation]: + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-DSCH Common System Information* IE, then the Node B shall: + +- If the *HS-DSCH Common Information* IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration: +- If the *Discard Timer* IE is included in the *Priority Queue Information for Enhanced FACH* IE, then the Node B shall use this information to discard out-of-date MAC-ehs SDUs from the related HSDPA Priority Queue. +- If the *FACH Measurement Occasion Cycle Length Coefficient* IE is included in the *HS-DSCH Common Information* IE, then the Node B shall use this information for MAC-ehs scheduling decisions. +- The Node B shall allocate HS-SCCH codes and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH Common System Information Response* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. +- The Node B shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH Common System Information Response* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. +- If the *Common MAC Flow Specific Information* IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration: +- If the common MAC flow indicated by the *Common MAC Flow ID* exists in the Node B, then the Node B shall apply the parameters to modify this common MAC flow; otherwise, the Node B shall apply the parameters to newly establish the common MAC flow. +- If the *Transport Layer Address* IE and *Binding ID* IE are included in the *Common MAC Flow Specific Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Common MAC flow or Common MAC flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. +- If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer. +- The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every Common MAC flow being established. +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the *HS-DSCH Common System Information Response* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE + +message for every Common MAC flow being established, if the Node B allows the CRNC to start transmission of MAC-c PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. + +- If the *Common MAC Flow Priority Queue Information* IE is included in the *Common MAC Flow Specific Information* IE, the Node B shall use the information for configuring HSDPA Priority Queues.] +- If the *Common HS-DSCH RNTI List* IE is included, then the Node B may use this information for MAC-ehs scheduling decisions.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common MAC Flows To Delete* IEs, then the Node B shall use this information to delete the indicated Common MAC flows. When a Common MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common MAC Flows To Delete* IE requesting the deletion of all remaining Common MAC flows, then the Node B shall delete the HS-DSCH common system configuration and release the resources for enhanced FACH.] + +#### [FDD - Enhanced Cell/URA\_PCH Operation]: + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-DSCH Paging System Information* IE, then the Node B shall: + +- If the Paging MAC flow indicated by the Paging MAC Flow ID exists in the Node B, then the Node B shall apply the parameters to modify this Paging MAC flow; otherwise, the Node B shall apply the parameters to newly establish the Paging MAC flow. +- If the *Transport Layer Address* IE and *Binding ID* IE are included in the *Paging MAC Flow Specific Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Paging MAC flow or Paging MAC flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. +- If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Paging MAC Flows To Delete* IEs, then the Node B shall use this information to delete the indicated Paging MAC flows. When a Paging MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Paging MAC Flows To Delete* IE requesting the deletion of all remaining Paging MAC flows, then the Node B shall delete the HS-DSCH paging system configuration and release the resources for enhanced PCH.] + +#### [1.28Mcps TDD - Enhanced Cell\_FACH Operation]: + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-DSCH Common System Information LCR* IE, then the Node B shall: + +- If the *HS-DSCH Common Information LCR* IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration: + - If the *Discard Timer* IE is included in the *Priority Queue Information for Enhanced FACH LCR* IE, then the Node B shall use this information to discard out-of-date MAC-ehs SDUs from the related HSDPA Priority Queue. + - If the *FACH Measurement Occasion Cycle Length Coefficient* IE is included in the *HS-DSCH Common Information LCR* IE, then the Node B shall use this information for MAC-hs scheduling decisions. +- The Node B shall allocate HS-SCCH codes and include the *HS-SCCH Specific Information Response LCR* IE in the *HS-DSCH Common System Information Response LCR* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. +- The Node B shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH Common System Information Response LCR* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. +- For a multi-frequency cell, if the *HARQ Memory Partitioning* IE is included in the *HS-DSCH Common System Information Response LCR* IE, the Node B shall include the *UARFCN* IE in the *HS-DSCH Common* + +*System Information Response LCR IE* to indicate the frequency of the *HARQ Memory Partitioning IE* in the *HS-DSCH Common System Information Response LCR IE*. + +- For a multi-frequency cell, the Node B can include the *HARQ Memory Partitioning Per UARFCN IE* in the *HS-DSCH Common System Information Response LCR IE* to indicate the HARQ Memory Partitioning information on the frequency indicated by the *UARFCN IE* in the *HARQ Memory Partitioning Per UARFCN IE*. +- The Node B shall use the value of the *E-AGCH TPC Step Size IE* contained in the *Common E-PUCH Information LCR IE* in the *Common E-DCH System Information LCR IE* for HS-SCCH inner loop power control.] +- If the Common MAC Flow Specific Information LCR IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration: + - If the common MAC flow indicated by the *Common MAC Flow ID LCR IE* exists in the Node B, then the Node B shall apply the parameters to modify this common MAC flow; otherwise, the Node B shall apply the parameters to newly establish the common MAC flow. + - If the *Transport Layer Address IE* and *Binding ID IE* are included in the *Common MAC Flow Specific Information LCR IE*, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Common MAC flow or Common MAC flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator IE*. + - If the *TNL QoS IE* is included and if ALCAP is not used, the *TNL QoS IE* may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer. + - The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the *Binding ID IE* and *Transport Layer Address IE* for establishment of transport bearer for every Common MAC flow being established. + - The Node B shall include the *HS-DSCH Initial Capacity Allocation IE* in the *HS-DSCH Common System Information Response LCR IE* in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message for every Common MAC flow being established, if the Node B allows the CRNC to start transmission of MAC-c PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. + - If the *Common MAC Flow Priority Queue Information LCR IE* is included in the *Common MAC Flow Specific Information LCR IE*, the Node B shall use the information for configuring HSDPA Priority Queues.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common MAC Flows To Delete LCR IEs*, then the Node B shall use this information to delete the indicated Common MAC flows. When a Common MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common MAC Flows To Delete LCR IE* requesting the deletion of all remaining Common MAC flows, then the Node B shall delete the HS-DSCH common system configuration and release the resources for enhanced FACH.] + +[1.28Mcps TDD - If the *Power Control GAP for CELL\_FACH IE* is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B may use the value for the power control for HS-SCCH, HS-SICH and E-AGCH according to TS 25.224 [21].] + +[1.28Mcps TDD - If the *UL Synchronisation Parameters LCR IE* is included in the *Common E-DCH System Information LCR IE* in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the indicated values of *Uplink Synchronisation Step Size IE* and *Uplink Synchronisation Frequency IE* when evaluating the timing of the UL synchronisation.] + +[1.28Mcps TDD - If the *Physical Channel ID for Common E-RNTI Requested Indicator IE* in the *Common E-DCH System Information LCR IE*, if supported, the Node B shall include the *Associated Physical Channel ID IE* in the *Common E-RNTI Information LCR IE* in the *Common E-DCH System Information Response LCR IE* to indicate the E-RUCCH associated with the related common E-RNTI group.] + +**[1.28Mcps TDD - Enhanced Cell/URA\_PCH Operation]:** + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-DSCH Paging System Information LCR IE*, then the Node B shall: + +- If the Paging MAC flow indicated by the *Paging MAC Flow ID IE* exists in the Node B, then the Node B shall apply the parameters to modify this Paging MAC flow; otherwise, the Node B shall apply the parameters to newly establish the Paging MAC flow. +- If the *Transport Layer Address IE* and *Binding ID IE* are included in the *Paging MAC Flow Specific Information LCR IE*, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Paging MAC flow or Paging MAC flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator IE*. +- If the *TNL QoS IE* is included and if ALCAP is not used, the *TNL QoS IE* may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Paging MAC Flows To Delete LCR IEs*, then the Node B shall use this information to delete the indicated Paging MAC flows. When a Paging MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Paging MAC Flows To Delete LCR IE* requesting the deletion of all remaining Paging MAC flows, then the Node B shall delete the HS-DSCH paging system configuration and release the resources for enhanced PCH.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH System Information LCR IE*, and the *Scheduling Priority Indicator IE* is present in the *Common E-DCH Logical Channel information IE* in the *Common E-DCH MAC-d Flow Specific Information LCR IE*, the Node B may use this IE to do the related scheduling operation. + +#### **[FDD - E-DCH Resources]:** + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE*, the Node B shall use this as the scrambling code for all E-AGCHs, E-RGCHs and E-HICHs. If a value has never been set, the Node B shall use the primary scrambling code for all E-AGCH, E-RGCH and E-HICH codes.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH FDD Code Information IE*, the Node B shall:] + +- [FDD - If the *E-AGCH FDD Code Information IE* contains no codes, delete any existing E-AGCH resources from the cell.] +- [FDD - If the *E-AGCH FDD Code Information IE* contains one or more codes and E-AGCH resources are not currently configured in the cell, use this list of codes as the list of codes for E-AGCH channels.] +- [FDD - If the *E-AGCH FDD Code Information IE* contains one or more codes and E-AGCH resources are currently configured in the cell, replace the current list of codes with this new list of codes for E-AGCH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-RGCH/E-HICH FDD Code Information IE*, the Node B shall:] + +- [FDD - If the *E-RGCH/E-HICH FDD Code Information IE* contains no codes, delete any existing E-RGCH/E-HICH resources from the cell.] +- [FDD - If the *E-RGCH/E-HICH FDD Code Information IE* contains one or more codes and E-RGCH/E-HICH resources are not currently configured in the cell, use this list of codes as the list of codes for E-RGCH/E-HICH channels.] +- [FDD - If the *E-RGCH/E-HICH FDD Code Information IE* contains one or more codes and E-RGCH/E-HICH resources are currently configured in the cell, replace the current list of codes with this new list of codes for E-RGCH/E-HICH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Maximum Target Received Total Wide Band Power IE*, the Node B shall use this value to control E-DCH scheduling.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Reference Received Total Wide Band Power* IE, the Node B may use this value to control E-DCH scheduling.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Target Non-serving E-DCH to Total E-DCH Power Ratio* IE, the Node B shall store this value and use this value for E-DCH scheduling by controlling the ratio of received E-DCH wide band power from non-serving UEs to the total received E-DCH power.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall use this as the scrambling code for all E-AGCHs, E-RGCHs and E-HICHs for the cell portion indicated by Cell Portion ID. If a value has never been set, the Node B shall use the primary scrambling code for all E-AGCH, E-RGCH and E-HICH codes for the cell portion indicated by Cell Portion ID.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH FDD Code Information* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall:] + +- [FDD - If the *E-AGCH FDD Code Information* IE contains no codes, delete any existing E-AGCH resources from the cell portion indicated by *Cell Portion ID* IE.] +- [FDD - If the *E-AGCH FDD Code Information* IE contains one or more codes and E-AGCH resources are not currently configured in the cell portion indicated by *Cell Portion ID* IE, use this list of codes as the list of codes for E-AGCH channels.] +- [FDD - If the *E-AGCH FDD Code Information* IE contains one or more codes and E-AGCH resources are currently configured in the cell portion indicated by *Cell Portion ID* IE, replace the current list of codes with this new list of codes for E-AGCH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-RGCH/E-HICH FDD Code Information* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall:] + +- [FDD - If the *E-RGCH/E-HICH FDD Code Information* IE contains no codes, delete any existing E-RGCH/E-HICH resources from the cell portion indicated by *Cell Portion ID* IE.] +- [FDD - If the *E-RGCH/E-HICH FDD Code Information* IE contains one or more codes and E-RGCH/E-HICH resources are not currently configured in the cell portion indicated by *Cell Portion ID* IE, use this list of codes as the list of codes for E-RGCH/E-HICH channels.] +- [FDD - If the *E-RGCH/E-HICH FDD Code Information* IE contains one or more codes and E-RGCH/E-HICH resources are currently configured in the cell portion indicated by *Cell Portion ID* IE, replace the current list of codes with this new list of codes for E-RGCH/E-HICH channels.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Maximum Target Received Total Wide Band Power* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B shall, if supported, use this value to control E-DCH scheduling in the cell portion indicated by *Cell Portion ID* IE.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Reference Received Total Wide Band Power* IE in the *HSDPA And E-DCH Cell Portion Information* IE, the Node B may use this value to control E-DCH scheduling in the cell portion indicated by *Cell Portion ID* IE.] + +#### **[TDD - E-DCH Resources]:** + +[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-PUCH Information* IE, the Node B shall: + +- If the *E-PUCH Information* IE contains no *E-PUCH Timeslot Information* IE, then the Node B shall delete any existing E-DCH resources from the cell. +- If the *E-PUCH Information* IE contains *E-PUCH Timeslot Information* IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots for E-PUCH channels. +- If the *E-PUCH Information* IE contains *E-PUCH Timeslot Information* IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots with this new list of timeslots for E-PUCH channels.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-PUCH Information 1.28Mcps* IE, the Node B shall: + +- If the *E-PUCH Information 1.28Mcps* IE contains no *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE, then the Node B shall delete any existing E-DCH resources from the cell. +- For a single-frequency cell, if the *E-PUCH Information 1.28Mcps* IE contains *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots / codes for E-PUCH channels. +- For a single-frequency cell, if the *E-PUCH Information 1.28Mcps* IE contains *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots / codes with this new list of timeslots / codes for E-PUCH channels. +- For a multi-frequency cell, if the *E-PUCH Information 1.28Mcps* IE contains *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE and E-DCH resources are not currently configured on the indicated frequency in the cell, use this IE as the list of frequency / timeslots / codes for E-PUCH channels, the E-DCH resources on other frequency shall remain unchanged. +- For a multi-frequency cell, if the *E-PUCH Information 1.28Mcps* IE contains *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE and E-DCH resources are currently configured on the indicated frequency in the cell, replace the current list of frequency / timeslots / codes with this new list of timeslots / codes for E-PUCH channels, the E-DCH resources on other frequency shall remain unchanged. +- For a multi-frequency cell, if the *E-PUCH Information 1.28Mcps* IE contains *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE but only *UARFCN* IE is included, then the Node B shall delete the existing E-DCH resources on the frequency indicated by the *UARFCN* IE from the cell, the E-DCH resources on other frequency shall remain unchanged.] + +[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-PUCH Information 7.68Mcps* IE, the Node B shall: + +- If the *E-PUCH Information 7.68Mcps* IE contains no *E-PUCH Timeslot Information* IE, then the Node B shall delete any existing E-DCH resources from the cell. +- If the *E-PUCH Information 7.68Mcps* IE contains *E-PUCH Timeslot Information* IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots for E-PUCH channels. +- If the *E-PUCH Information 7.68Mcps* IE contains *E-PUCH Timeslot Information* IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots with this new list of timeslots for E-PUCH channels.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes [3.84Mcps TDD - *Add to E-AGCH Resource Pool* IE] [1.28Mcps TDD - *Add to E-AGCH Resource Pool 1.28Mcps* IE][7.68Mcps TDD - *Add to E-AGCH Resource Pool 7.68Mcps* IE], the Node B shall add this resource to the E-AGCH resource pool to be used to assign E-AGCH sets.] + +[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify E-AGCH Resource Pool* IEs and includes any of *TDD Channelisation Code* IE, *Midamble Shift and Burst Type* IE, *Time Slot* IE, for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify E-AGCH Resource Pool 1.28Mcps* IEs and includes any of *First TDD Channelisation Code* IE, *Second TDD Channelisation Code* IE, *Midamble Shift LCR* IE, *Time Slot LCR* IE, *UARFCN* IE for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify E-AGCH Resource Pool 7.68Mcps* IEs and includes any of *TDD Channelisation Code 7.68Mcps* IE, *Midamble Shift and Burst Type 7.68Mcps* IE, *Time Slot* IE, for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any [3.84Mcps TDD - *Modify E-AGCH Resource Pool* IEs] [1.28Mcps - *Modify E-AGCH Resource Pool 1.28Mcps* IEs] [7.68Mcps + +TDD - *Modify E-AGCH Resource Pool 7.68Mcps* IEs] and includes the *Maximum E-AGCH Power* IE, the Node B shall apply this value for the specified E-AGCH code otherwise the old value is still applicable.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Delete from E-AGCH Resource Pool* IEs, the Node B shall delete these resources from the E-AGCH resource pool.] + +[3.84Mcps TDD and 7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the [3.84Mcps TDD - *E-HICH Information* IE] [7.68Mcps TDD - *E-HICH Information 7.68Mcps* IE], the Node B shall configure the E-HICH according to the parameters.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Add to E-HICH Resource Pool 1.28Mcps* IE, the Node B shall add this resource to the E-HICH resource pool to be used to assign Scheduled or Non-scheduled E-HICH sets.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify E-HICH Resource Pool 1.28Mcps* IEs and includes any of *E-HICH Type* IE, *TDD Channelisation Code* IE, *Midamble Shift LCR* IE, *Time Slot LCR* IE, *UARFCN* IE for E-HICH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Modify E-HICH Resource Pool 1.28Mcps* IEs and includes the *Maximum E-HICH Power* IE, the Node B shall apply this value for the specified E-HICH code otherwise the old value is still applicable.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any *Delete from E-HICH Resource Pool 1.28Mcps* IEs, the Node B shall delete these resources from the E-HICH resource pool.] + +[3.84Mcps TDD and 7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Maximum Generated Received Total Wide Band Power in Other Cells* IE, the Node B shall use this value to control E-DCH scheduling.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Maximum Target Received Total Wide Band Power LCR* IE, the Node B shall use this value to control E-DCH scheduling.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Maximum RTWP per UARFCN information LCR* IE, the Node B may use this value to control E-DCH scheduling in a multi-frequency cell and ignore the *Maximum Target Received Total Wide Band Power LCR* IE.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *Maximum Target Received Total Wide Band Power per CELL PORTION LCR* IE, the Node B may use this value to control E-DCH scheduling for the cell portion indicated by *Cell Portion ID* IE.] + +#### **[TDD - PDSCH/PUSCH Addition]:** + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be added, the Node B shall add these new sets to its PDSCH/PUSCH configuration.] + +[1.28Mcps TDD - If the *TSTD Indicator* IE is included in *PDSCH To Add Information LCR* IE and is set to "active", the Node B shall activate TSTD diversity for PDSCH transmissions using the specified PDSCH Set that are not beacon channels (TS 25.221 [19], TS 25.224 [21]). If the *TSTD Indicator* IE is set to "not active" or the *TSTD Indicator* IE is not included in *PDSCH To Add Information LCR* IE, the Node B shall not activate TSTD diversity for the PDSCH Set.] + +#### **[TDD - PDSCH/PUSCH Modification]:** + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be modified, and includes any of [3.84Mcps TDD - *DL/UL Code Information* IE, *Midamble Shift And Burst Type* IE, *Time Slot* IE], [1.28Mcps TDD - *DL/UL Code Information LCR* IE, *Midamble Shift LCR* IE, *Time Slot LCR* IE], [7.68Mcps TDD - *DL/UL Code Information 7.68Mcps* IE, *Midamble Shift And Burst Type 7.68Mcps* IE, *Time Slot* IE], *TDD Physical Channel Offset* IE, *Repetition Period* IE, *Repetition Length* IE, or *TFCI Presence* IE, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.] + +#### **[TDD - PDSCH/PUSCH Deletion]:** + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be deleted the Node B shall delete these sets from its PDSCH/PUSCH configuration.] + +**[1.28Mcps TDD - SYNC\_UL Partition]:** + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *SYNC\_UL Partition Information* IE, the Node B shall store the *E-RUCCH SYNC\_UL codes bitmap* IE used to differentiate the E-DCH random access from the RACH random access according to TS 25.224 [21].] + +**[FDD – Common E-DCH Operation]:** + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH System Information* IE, then the Node B shall: + +- If the *Common E-DCH UL DPCH Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: +- If the *Common E-DCH E-DPCH Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: + - If the *E-RGCH 2-Index-Step Threshold* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the value when the new configuration is being used. For the case of initial assignment of E-DCH related resources to the Node B, if *E-RGCH 2-Index-Step Threshold* IE is not present, the Node B shall use the default value defined in TS 25.331 [18]. + - If the *E-RGCH 3-Index-Step Threshold* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the value when the new configuration is being used. For the case of initial assignment of E-DCH related resources to the Node B, if *E-RGCH 3-Index-Step Threshold* IE is not present, the Node B shall use the default value defined in TS 25.331 [18]. +- If the *Common E-DCH Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: + - If the *E-DCH Reference Power Offset* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-i PDU and to determine the value of the actual HARQ power offset. + - If the *E-DCH Power Offset for Scheduling Info* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-is PDUs. + - If the *Maximum TB Sizes* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this information for the Node B scheduler in the new configuration. + - If the *Common E-DCH Additional Transmission Back Off* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this information for the related common E-DCH resource allocation operation. + - If the *Common E-DCH Implicit Release Timer* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for the related common E-DCH resource release decision. +- If the *Common E-DCH HS-DPCCH Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration. + - If the Common E-DCH CQI Information is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the information for CQI operation in the new configuration. +- If the *Common E-DCH Preamble Control Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: + - If the *E-AI Indicator* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this value for configuration of E-AIs on the AICH. + +- If the *Common E-DCH AICH Information* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH. +- If the *Common E-DCH F-DPCH Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration. +- If the *Initial DL Transmission Power* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Initial DL Transmission Power on the F-DPCH. +- If the *Maximum DL Power* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Maximum DL Power on the F-DPCH. +- If the *Minimum DL Power* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Minimum DL Power on the F-DPCH. +- If the *Common E-DCH E-AGCH Channelisation Code Number* IE is included, then the Node B shall use the indicated channelization code for the E-AGCH for the common E-DCH in the new configuration. +- If the *Common E-DCH Resource Combination Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: +- If the *E-RGCH Signature Sequence* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall configure the E-RGCH for the combination and use indicated signature sequence. +- If the *UL Common MAC Flow Specific Information* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: +- If the *Transport Layer Address* IE and *Binding ID* IE are included in the *UL Common MAC Flow Specific Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned UL Common MAC flow. +- If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer. +- The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every UL Common MAC flow being established. +- If the *Bundling Mode Indicator* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the Common E-DCH UL data frames for the related UL Common MAC flow, otherwise the Node B shall use the non-bundling mode for the Common E-DCH UL data frames for the related UL Common MAC flow. +- If the *E-DCH MAC-d Flow Multiplexing List* IE is included for a Common E-DCH MAC-d flow in the *Common E-DCH MAC-d Flow Specific Information* IE, the Node B shall use this information for the related resource allocation operation.] +- If the *Concurrent Deployment of 2ms and 10ms TTI* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message and if the *Common E-DCH MAC-d flow info for Concurrent TTI* IE is included for a Common E-DCH MAC-d flow in the *Common E-DCH MAC-d Flow Specific Information* IE, the Node B shall use this information for the transmission with the concurrent TTI. +- If the *E-RNTI List Request* IE is included, then the Node B shall, if supported, include the *E-RNTI List* IE in the *Common E-DCH System Information Response* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. +- If the *E-RNTI Set* IE is included, then the Node B shall, if supported, not allocate any E-RNTIs listed in this IE for a UE. + +- If supported, the Node B shall include *UE Status Update Confirm Indicator* IE in the *Common E-DCH System Information Response* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message to indicate that the Node B supports of UE status update confirmation procedure for releasing E-RNTI. +- If the *Concurrent Deployment of 2ms and 10ms TTI* IE is included, then the Node B shall, if supported, apply the parameters to the common E-DCH in new configuration: + - If the *E-DPCCH Power Offset*, *E-RGCH 2-Index-Step Threshold*, *E-RGCH 3-Index-Step Threshold*, or *E-DCH Reference Power Offset* IE is not included in the *Common E-DCH System Info Parameters for Concurrent TTI* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the corresponding IE included in *Common E-DCH E-DPCH Information* IE. + - If the *E-DCH Reference Power Offset*, *E-DCH Power Offset for Scheduling Info*, *Maximum E-DCH resource allocation for CCCH*, *Maximum period for collision resolution phase*, *Maximum TB Sizes*, or *Common E-DCH Additional Transmission Back Off* IE is not included in the *Common E-DCH System Info Parameters for Concurrent TTI* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the corresponding IE included in **Common E-DCH Information** IE. + - If the *Common E-DCH E-AGCH Channelisation Code Number* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use corresponding IE included in *Common E-DCH System Information* IE. + - If the *Common E-DCH HS-DPCCH Information for Concurrent TTI* IE is included in the *Common E-DCH System Info Parameters for Concurrent TTI* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for the related HS-DPCCH information in the new configuration. +- If the *Common E-DCH Preamble Control Information extension Type1* IE is included, then the Node B shall, if supported, use this information for 10ms TTI type decisions in new configuration.: + - If the *AICH Info* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH. +- If the *Common E-DCH Preamble Control Information extension Type2* IE is included, then the Node B shall, if supported, use this information for 2ms TTI type and Concurrent TTI capability decisions in new configuration.: + - If the *AICH Info* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH. +- If the *Common E-DCH Preamble Control Information extension Type3* IE is included, then the Node B shall, if supported, use this information for 2ms TTI type and Per HARQ and TTI alignment capability decisions in new configuration.: + - If the *AICH Info* IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH. +- If the *NodeB Triggered HS-DPCCH Transmission Information* IE is included, then the Node B shall, if supported, apply the parameters to the Node B Triggered HS-DPCCH Transmission in new configuration: +- If the *Per HARQ Activation and Deactivation* IE is included, then the Node B shall apply the parameters to the Per HARQ Activation and Deactivation in new configuration. +- If the *Coffset* IE is included, then the Node B shall, if supported, apply the parameters to the TTI alignment in new configuration. + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common UL MAC Flows To Delete* IEs, then the Node B shall use this information to delete the indicated Common UL MAC flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common UL MAC Flows To Delete* IE requesting the deletion of all remaining Common UL MAC flows, then the Node B shall delete the common E-DCH system configuration and release the resources for Common E-DCH.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to delete the indicated Common E-DCH MAC-d flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the + +*Common E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining Comm E-DCH MAC-d flows associated to a Common UL MAC flow, then the Node B shall release the resources for the Common UL MAC flow.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *E-AGCH Power Offset* IE, then the Node B may use this value to determine the E-AGCH power.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *E-RGCH Power Offset* IE, then the Node B may use this value to determine the E-RGCH power.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *E-HICH Power Offset* IE, then the Node B may use this value to determine the E-HICH power.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-RGCH Operation Indicator* IE, then the Node B shall, if supported, contain the *Common E-RGCH Info* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.] + +#### [1.28Mcps TDD – Common E-DCH Operation]: + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH System Information LCR* IE, then the Node B shall: + +- If the *UL Common MAC Flow Specific Information LCR* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration: + - If the *Transport Layer Address* IE and *Binding ID* IE are included in the *UL Common MAC Flow Specific Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned UL Common MAC flow. + - If the *TNL QoS* IE is included and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer. + - The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every UL Common MAC flow being established. + - If the *E-DCH MAC-d Flow Multiplexing List* IE is included for a Common E-DCH MAC-d flow in the *Common E-DCH MAC-d Flow Specific Information LCR* IE, the Node B shall use this information for the related resource allocation operation.] +- If the *Common E-PUCH Information LCR* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration. +- If the *E-TFCS Information TDD* IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration. +- If supported, the Node B shall include *UE Status Update Confirm Indicator* IE in the *Common E-DCH System Information Response LCR* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message to indicate that the Node B supports of UE status update confirmation procedure for releasing E-RNTI. + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH MAC-d Flows To Delete LCR* IEs, then the Node B shall use this information to delete the indicated Common E-DCH MAC-d flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common UL MAC Flows to Delete LCR* IE requesting the deletion of all remaining Comm E-DCH MAC-d flows associated to a Common UL MAC flow, then the Node B shall release the resources for the Common UL MAC flow.] + +#### [FDD – Enhanced UE DRX Operation]: + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Enhanced UE DRX Information* IE, then the Node B shall use the information to execute Enhanced UE DRX for the cell.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Further Enhanced UE DRX Information* IE, then the Node B shall, if supported, use the information to execute Further Enhanced UE DRX in new configuration: + +- For the case of *1-level DRX* is configured to the Node B, if *HS-DSCH second Rx burstFACH* or *T32y* IE is not present, the Node B shall use the default value defined in TS 25.331 [18]. +- For the case of *2-level DRX* is configured to the Node B, if *T32x*, *HS-DSCH first Rx burstFACH*, *HS-DSCH first DRX cycleFACH*, *HS-DSCH second Rx burstFACH*, or *T32y* IE is not present, the Node B shall use the default value defined in TS25.331 [18]. + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-SCCH DRX Information IE*, then the Node B shall use the information to execute HS-SCCH DRX operation defined in TS25.308 for the cell [49].] + +**[1.28Mcps DD – Enhanced UE DRX Operation]:** + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Enhanced UE DRX Information LCR* IE, then the Node B shall use the information to execute Enhanced UE DRX for the cell.] + +**[1.28Mcps TDD - Shared physical channels Synchronisation Detection]:** + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Out-of-sync Detection Window* IE, then the Node B shall use this IE to detect the synchronization status of UE as described in ref TS 25.224 [21], subclause 5.3.2A.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Treset Usage Indicator* IE, if supported, the Node B shall stop using all configured MAC-ehs Reset Timers for the UEs in enhanced CELL\_PCH or CELL\_FACH with dedicated H-RNTI according to TS 25.321 [32].] + +**[1.28Mcps TDD – Shared physical channels In Synchronisation Indication]:** + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *In Sync Indication Information LCR* IE, then the Node B may use this information for MAC-hs/ehs scheduling.] + +**Response Message:** + +**HS-DSCH/HS-SCCH Resources:** + +In the successful case involving HS-PDSCH or HS-SCCH resources, the Node B shall store the value of *Configuration Generation ID* IE and it shall make these resources available to all the current and future HS-DSCH transport channels; and shall respond with PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. + +**[TDD - PDSCH/PUSCH Addition/Modification/Deletion]:** + +[TDD - In the successful case involving PDSCH/PUSCH addition, modification or deletion, the Node B shall add, modify and delete the PDSCH Sets and PUSCH Sets in the Common Transport Channel data base, as requested in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, and shall make these available to all the current and future DSCH and USCH transport channels. The Node B shall respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.] + +### 8.2.18.3 Unsuccessful Operation + +![Sequence diagram showing the Physical Shared Channel Reconfiguration procedure for an Unsuccessful Operation. The diagram shows two vertical lines representing the CRNC (left) and Node B (right). A horizontal arrow points from the CRNC to Node B, labeled 'PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST'. A return horizontal arrow points from the Node B back to the CRNC, labeled 'PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE'.](f04d32f713a4aeb9f63c3f8e1015145c_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST + CRNC->>Node B: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST + Note left of Node B: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE + Node B-->>CRNC: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE + +``` + +Sequence diagram showing the Physical Shared Channel Reconfiguration procedure for an Unsuccessful Operation. The diagram shows two vertical lines representing the CRNC (left) and Node B (right). A horizontal arrow points from the CRNC to Node B, labeled 'PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST'. A return horizontal arrow points from the Node B back to the CRNC, labeled 'PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE'. + +**Figure 27: Physical Shared Channel Reconfiguration procedure: Unsuccessful Operation** + +If the Node B is not able to support all parts of the configuration, it shall reject the configuration of all the channels in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message. The *Cause* IE shall be set to an appropriate value [TDD - either a single general cause value or PDSCH and PUSCH set specific cause values for each set that caused a failure within the *Unsuccessful DL Shared Channel Set* IE for PDSCH sets or *Unsuccessful UL Shared Channel Set* IE for PUSCH sets]. The *Configuration Generation ID* shall not be changed in the Node B. + +If the configuration was unsuccessful, the Node B shall respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message: + +[1.28Mcps TDD - For a multi-frequency cell, if the Node B is not able to support all parts of the configuration, in the case the Node B can only support configuration on one or some frequencies, the HSDPA or E-DCH related resources on this or these frequencies may be regarded as having successfully been established/reconfigured/removed, the Node B shall reject the HSDPA or E-DCH related configuration on other failed frequencies. The Node B may respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. The *HS-Cause* IE or *E-Cause* IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message may be set to specific cause values for each frequency that caused a HSDPA or E-DCH related configuration failure. If the failure occurs on the HS-PDSCH, HS-SCCH, E-PUCH or E-AGCH resources, the Node B may store the value of the *Configuration Generation ID* IE and it shall make these resources available to all the current and future HS-DSCH or E-DCH transport channels. If the Node B is not able to support the HSDPA or E-DCH related configuration on any frequencies, the *Cause* IE may be set to an appropriate value, which is either a general cause value or specific cause values for each frequency that caused a failure. For the successfully configured HSUPA frequencies, the *E-HICH Time Offset LCR per UARFCN* IE may be included in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. For the successfully configured Enhanced CELL\_FACH frequencies, the *Common System Information Response LCR* IE may be included in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +Typical cause values are as follows: + +#### Radio Network Layer Cause: + +- Cell not available +- Node B Resources unavailable + +#### Transport Layer Cause: + +- Transport Resources Unavailable + +#### Miscellaneous Cause: + +- O&M Intervention +- Control processing overload +- HW failure + +### 8.2.18.4 Abnormal Conditions + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains *Add to HS-SCCH Resource Pool* IE, the *Modify HS-SCCH Resource Pool* IE, or the *Delete from HS-SCCH Resource Pool* IE and does not contain the *Configuration Generation ID* the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Add to E-AGCH Resource Pool* IE, the *Modify E-AGCH Resource Pool* IE, or the *Delete from E-AGCH Resource Pool* IE and does not contain the *Configuration Generation ID* the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Add to E-AGCH Resource Pool 1.28Mcps* IE, the *Modify E-AGCH Resource Pool 1.28Mcps* IE, or the *Delete from E-AGCH Resource Pool* IE and does not contain the *Configuration Generation ID* the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Add to E-HICH Resource Pool 1.28Mcps* IE, the *Modify E-HICH Resource Pool 1.28Mcps* IE, or the *Delete from E-* + +*HICH Resource Pool 1.28Mcps* IE and does not contain the *Configuration Generation ID* the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Add to E-AGCH Resource Pool 7.68Mcps* IE, the *Modify E-AGCH Resource Pool 7.68Mcps* IE, or the *Delete from E-AGCH Resource Pool* IE and does not contain the *Configuration Generation ID* the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *Configuration Generation ID* IE and does not contain at least one of *Add to HS-SCCH Resource Pool* IE, the *Modify HS-SCCH Resource Pool* IE, [3.84Mcps TDD - the *Add to E-AGCH Resource Pool* IE, the *Modify E-AGCH Resource Pool* IE, the *Delete from E-AGCH Resource Pool* IE,] [1.28Mcps TDD - the *Add to E-AGCH Resource Pool 1.28Mcps* IE, the *Modify E-AGCH Resource Pool 1.28Mcps* IE, the *Delete from E-AGCH Resource Pool* IE, the *Add to E-HICH Resource Pool 1.28Mcps* IE, the *Modify E-HICH Resource Pool 1.28Mcps* IE, the *Delete from E-HICH Resource Pool 1.28Mcps* IE,][7.68Mcps TDD - the *Add to E-AGCH Resource Pool 7.68Mcps* IE, the *Modify E-AGCH Resource Pool 7.68Mcps* IE, the *Delete from E-AGCH Resource Pool* IE,] or the *Delete from HS-SCCH Resource Pool* IE the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[FDD - If neither E-AGCH nor E-HICH/E-RGCH resources are configured in the cell, and if one or more codes are included in the *E-AGCH FDD Code Information* IE and/or *E-RGCH/E-HICH FDD Code Information* IE but the *Maximum Target Received Total Wide Band Power* IE is not included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall send PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE, and the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE is not identical to the scrambling code of the phase reference, then the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE in the *HSDPA And E-DCH Cell Portion Information* IE, and the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE is not identical to the scrambling code of the phase reference, then the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-DSCH Common Information* IE and/or *Common MAC Flow Specific Information* IE and if the Priority Queues associated with the same *Common MAC Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *UARFCN* IE in the *DL Timeslot and Code Information LCR per UARFCN* IE in the *HS-PDSCH TDD Information* IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *UARFCN* IE in the *HS-SCCH Information LCR* IE in the *Add to HS-SCCH Resource Pool* IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *UARFCN* IE in the *HS-SCCH Information LCR* IE in the *Modify HS-SCCH Resource Pool* IE, the HS-SCCH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *UARFCN* IE in the *E-AGCH Information 1.28Mcps* IE in the *Modify E-AGCH Resource Pool 1.28Mcps* IE, the E-AGCH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the *UARFCN* IE in the *E-HICH Information 1.28Mcps* IE in the *Modify E-HICH Resource Pool 1.28Mcps* IE, the E-HICH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *DL Timeslot and Code Information LCR* IE in the *DL Timeslot and Code Information LCR per UARFCN* IE in the *HS-PDSCH TDD Information* IE but contains *UARFCN* IE, and no HS-DSCH resources are configured on the frequency within the cell, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *UARFCN* IE in the *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE in the *E-PUCH Information 1.28Mcps* IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *UARFCN* IE in the *Add to E-AGCH Resource Pool 1.28Mcps* IE, the *Modify E-AGCH Resource Pool 1.28Mcps* IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *UARFCN* IE in the *Add to E-HICH Resource Pool 1.28Mcps* IE, the *Modify E-HICH Resource Pool 1.28Mcps* IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the *E-PUCH Timeslot Information 1.28Mcps* IE in the *E-PUCH Timeslot Information 1.28Mcps per UARFCN* IE in the *E-PUCH Information 1.28Mcps* IE but contains *UARFCN* IE, and no E-DCH resources are configured on the frequency within the cell, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-DCH System Information* IE and if the message does not contain the *HS-DSCH Common System Information* IE or the resource for enhanced FACH is not configured for the cell, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Enhanced UE DRX Information* IE and if the message does not contain the *HS-DSCH Common System Information* IE or the resource for enhanced FACH is not configured for the cell, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *HS-SCCH DRX Information* IE and if the message does not contain the *HS-DSCH Common System Information* IE or the resource for enhanced FACH is not configured for the cell, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes *HS-DSCH Paging System Information* IE and *Paging MAC Flow Specific Information* IE and if the Priority Queues associated with the same *Paging MAC Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Further Enhanced UE DRX Information* IE and if the message does not contain the *Enhanced UE DRX Information* IE, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the *Common E-RGCH Operation Indicator* IE and if the message does not contain the *Common E-DCH System Information* IE, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.] + +If ALCAP is not used, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the newly established Common MAC Flow, Paging MAC Flow and/or UL Common MAC Flow, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. + +## 8.2.19 Reset + +### 8.2.19.1 General + +The purpose of the Reset procedure is to align the resources in the CRNC and the Node B in the event of an abnormal failure. The CRNC or the Node B may initiate the procedure. + +### 8.2.19.2 Successful Operation + +#### 8.2.19.2.1 Reset Initiated by the CRNC + +![Sequence diagram for Figure 27A: Reset procedure (CRNC to Node B), Successful Operation. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'RESET REQUEST' points from CRNC to Node B. A horizontal arrow labeled 'RESET RESPONSE' points from Node B back to CRNC.](e1136c8a41c5a8081a8a554e513cd86e_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: RESET REQUEST + Node B-->>CRNC: RESET RESPONSE +``` + +Sequence diagram for Figure 27A: Reset procedure (CRNC to Node B), Successful Operation. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'RESET REQUEST' points from CRNC to Node B. A horizontal arrow labeled 'RESET RESPONSE' points from Node B back to CRNC. + +**Figure 27A Reset procedure (CRNC to Node B), Successful Operation** + +The procedure is initiated with a RESET REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +If the *Reset Indicator* IE is set to "Communication Context", the Node B shall remove all the indicated Node B Communication Contexts (identified by a *Node B Communication Context ID* or a *CRNC Communication Context ID* IE) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC. + +If the *Reset Indicator* IE is set to "Communication Control Port", the Node B shall remove all the Node B Communication Contexts controlled via the indicated Communication Control Port(s) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC. + +If the *Reset Indicator* IE is set to "Node B", the Node B shall remove all the Node B Communication Contexts within the Node B and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC. + +#### 8.2.19.2.2 Reset Initiated by the Node B + +![Sequence diagram for Figure 27B: Reset procedure (Node B to CRNC), Successful Operation. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'RESET REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'RESET RESPONSE' points from CRNC back to Node B.](097b0c14308c81dcfcc168e261aa0bba_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Node B->>CRNC: RESET REQUEST + CRNC-->>Node B: RESET RESPONSE +``` + +Sequence diagram for Figure 27B: Reset procedure (Node B to CRNC), Successful Operation. The diagram shows two vertical lifelines for CRNC and Node B. A horizontal arrow labeled 'RESET REQUEST' points from Node B to CRNC. A horizontal arrow labeled 'RESET RESPONSE' points from CRNC back to Node B. + +**Figure 27B Reset procedure (Node B to CRNC ), Successful Operation** + +The procedure is initiated with a RESET REQUEST message sent from the Node B to the CRNC using the Node B Control Port. + +If the *Reset Indicator* IE is set to "Communication Context", for all indicated CRNC Communication Contexts (indicated by a *CRNC Communication Context ID* or a *Node B Communication Context ID* IE), the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the indicated CRNC Communication Contexts. After clearing all related resources, the CRNC shall return the RESET RESPONSE message to the Node B. + +If the *Reset Indicator* IE is set to "Communication Control Port", for all the CRNC Communication Contexts controlled via the indicated Communication Control Port(s), the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the CRNC Communication Contexts controlled via the indicated Communication Control Port(s). After clearing all related resources, the CRNC shall return the RESET RESPONSE message to Node B. + +If the *Reset Indicator* IE is set to the "Node B", for all the CRNC Communication Contexts related to this Node B, the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the CRNC Communication Contexts related to this Node B. After clearing all related resources, the CRNC shall return the RESET RESPONSE message to Node B. + +#### 8.2.19.3 Unsuccessful Operation + +- + +#### 8.2.19.4 Abnormal Conditions + +If the RESET REQUEST message is received any ongoing procedure related to a CRNC Communication Context in the CRNC or Node B Communication Context in the Node B indicated (explicitly or implicitly) in the message shall be aborted. + +### 8.2.20 Cell Synchronisation Initiation [TDD] + +#### 8.2.20.1 General + +This procedure is used by a CRNC to request the transmission of [3.84Mcps TDD - Cell Synchronisation Bursts sent in the PRACH time slots] [1.28Mcps TDD - SYNC\_DL code sent in the DwPTS] and/or to start measurements on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL code] in a Node B. + +#### 8.2.20.2 Successful Operation + +![Sequence diagram showing the Cell Synchronisation Initiation procedure. A CRNC sends a CELL SYNCHRONISATION INITIATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION INITIATION RESPONSE.](3ae0872dc01de8bf4c43996b9507914b_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + Note right of Node B: Node B + CRNC->>Node B: CELL SYNCHRONISATION INITIATION REQUEST + Node B-->>CRNC: CELL SYNCHRONISATION INITIATION RESPONSE +``` + +Sequence diagram showing the Cell Synchronisation Initiation procedure. A CRNC sends a CELL SYNCHRONISATION INITIATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION INITIATION RESPONSE. + +**Figure 27C Cell Synchronisation Initiation procedure, Successful Operation** + +The procedure is initiated with a CELL SYNCHRONISATION INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall initiate the requested transmission according to the parameters given in the request and start the measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL code] if requested. + +#### **[3.84Mcps TDD - Cell Sync Burst Transmission Initiation] [1.28Mcps TDD - SYNC\_DL Code Transmission Initiation LCR]:** + +When the [3.84Mcps TDD - Cell Sync Burst Transmission Initiation Information] [1.28Mcps TDD - SYNC\_DL Code Transmission Initiation Information LCR] is present, the Node B shall configure the transmission of the cell synchronisation burst according to the parameters given in the CELL SYNCHRONISATION INITIATION REQUEST message. The *SFN* IE indicates the frame number when the cell shall start transmitting cell synchronisation bursts. + +[3.84Mcps TDD - When the Cell Sync Burst Transmission Initiation Information is present and the "Frequency Acquisition" is indicated within the *Synchronisation Report Type* IE, the Node B shall first perform only frequency locking on received cell synchronisation bursts. Transmission of the indicated cell synchronisation bursts shall be + +started only if the frequency locking is performed successfully and "Frequency Acquisition completed" is reported to the RNC.] + +**[3.84Mcps TDD - Cell Sync Burst Measurement characteristics] [1.28Mcps TDD - SYNC\_DL Code Measurement characteristics LCR]:** + +When the [3.84Mcps TDD - Cell Sync Burst Measurement Initiation Information][1.28Mcps TDD - SYNC\_DL Code Measurement Initiation Information LCR] is present, the Node B shall initiate measurements on the indicated cell synchronisation burst. + +If the *SFN* IE is present, the Node B shall after measurement of the indicated [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] adjust the frame number of the indicated cell according to the *SFN* of the CELL SYNCHRONISATION INITIATION REQUEST message. This adjustment shall only apply to the late entrant cell at the late entrant phase. + +**Synchronisation Report characteristics:** + +The *Synchronisation Report Characteristics* IE indicates how the reporting of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] measurement shall be performed. Whenever the Cell Synchronisation Initiation procedure is initiated, only [3.84Mcps TDD - the "Frequency Acquisition completed" or] "Frame related" report characteristics type shall apply. + +[3.84Mcps TDD - If the *Synchronisation Report characteristics type* IE is set to "Frequency Acquisition completed", the Node B shall signal completion of frequency acquisition to the RNC when locking is completed.] + +If the *Synchronisation Report characteristics type* IE is set to "Frame related", the Node B shall report the result of the cell synchronisation burst measurement after every measured frame. + +[3.84Mcps TDD - If the *Cell Sync Burst Arrival Time* IE is included in the *Cell Sync Burst Information* IE of the *Synchronisation Report Characteristics* IE, it indicates to the Node B the reference time at which the reception of the cell synchronisation burst of a neighbouring cell is expected.] + +[3.84Mcps TDD - If the *Cell Sync Burst Timing Threshold* IE is included in the *Cell Sync Burst Information* IE of the *Synchronisation Report Characteristics* IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.] + +[1.28Mcps TDD - If the *SYNC\_DL Code ID Arrival Time* IE is included in the *SYNC\_DL Code Information LCR* IE of the *Synchronisation Report Characteristics* IE, it indicates to the Node B the reference time at which the reception of the *SYNC\_DL Code* of a neighbouring cell is expected.] + +[1.28Mcps TDD - If the *SYNC\_DL Code ID Timing Threshold* IE is included in the *SYNC\_DL Code Information LCR* IE of the *Synchronisation Report Characteristics* IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.] + +**Response message:** + +If the Node B was able to initiate the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] transmission and/or measurement requested by the CRNC it shall respond with the CELL SYNCHRONISATION INITIATION RESPONSE message sent over the Node B Control Port. + +**8.2.20.3 Unsuccessful Operation** + +![Sequence diagram showing an unsuccessful cell synchronisation initiation. A CRNC sends a CELL SYNCHRONISATION INITIATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION INITIATION FAILURE.](7d3ed9c56124e26db58cd7475467dfab_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: Requesting cell synchronisation + CRNC->>Node B: CELL SYNCHRONISATION INITIATION REQUEST + Note right of Node B: Failure + Node B-->>CRNC: CELL SYNCHRONISATION INITIATION FAILURE + +``` + +Sequence diagram showing an unsuccessful cell synchronisation initiation. A CRNC sends a CELL SYNCHRONISATION INITIATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION INITIATION FAILURE. + +**Figure 27D Cell Synchronisation Initiation procedure, Unsuccessful Operation** + +If the requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Code] cannot be initiated, the Node B shall send a CELL SYNCHRONISATION INITIATION FAILURE message over the Node B control port. The message shall include the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +**Radio Network Layer Cause:** + +- Cell Synchronisation not supported +- Power level not supported +- Measurement Temporarily not Available +- Frequency Acquisition not supported + +**Miscellaneous Cause:** + +- O&M Intervention +- HW failure + +## 8.2.20.4 Abnormal Conditions + +- + +## 8.2.21 Cell Synchronisation Reconfiguration [TDD] + +### 8.2.21.1 General + +This procedure is used by a CRNC to reconfigure the transmission of [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Code] and/or to reconfigure measurements on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Code] in a Node B. + +### 8.2.21.2 Successful Operation + +#### 8.2.21.2.1 General + +![Sequence diagram showing the Cell Synchronisation Reconfiguration procedure. A CRNC sends a CELL SYNCHRONISATION RECONFIGURATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION RECONFIGURATION RESPONSE.](2fa9981a71c3ed101a792578163cb90e_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: CELL SYNCHRONISATION RECONFIGURATION REQUEST + Node B-->>CRNC: CELL SYNCHRONISATION RECONFIGURATION RESPONSE + +``` + +Sequence diagram showing the Cell Synchronisation Reconfiguration procedure. A CRNC sends a CELL SYNCHRONISATION RECONFIGURATION REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION RECONFIGURATION RESPONSE. + +**Figure 27E Cell Synchronisation Reconfiguration procedure, Successful Operation** + +The procedure is initiated with a CELL SYNCHRONISATION RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall reconfigure the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] transmission and/or measurements according to the parameters given in the request. + +#### 8.2.21.2.2 [3.84Mcps TDD - Cell Sync Burst Schedule] + +Within the CELL SYNCHRONISATION RECONFIGURATION REQUEST message first the schedule for the steady state phase is fixed. I.e. the number of cycles per SFN period is defined with the same schedule. For each cycle, the number of repetitions is defined according to following equations: + +Cycle length: $4096 / \text{value of } \textit{Number Of Cycles Per SFN Period IE}$ + +Repetition period: $\text{Cycle length} / \text{value of } \textit{Number Of Repetitions Per Cycle Period IE}$ + +Cell Sync Frame number is calculated by: + +$$\text{SFN} = \text{floor}((k-1) * \text{Cycle length} + (i-1) * \text{Repetition period})$$ + +$k = \{1, 2, 3, \dots \text{ Number of cycle per SFN period}\}$ + +$i = \{1, 2, 3, \dots \text{ Cell Sync Frame number within cycle period}\}$ + +### 8.2.21.2.3 [1.28Mcps TDD - SYNC\_DL Code Schedule] + +Within the CELL SYNCHRONISATION RECONFIGURATION REQUEST message first the schedule for the steady state phase is fixed. The "schedule" includes + +- the list of frame numbers SFN within the SFN period where SYNC\_DL Code transmission or reception takes place, i.e. the "synchronisation frames", and +- the associated actions (SYNC\_DL Code transmission, reception, averaging, reporting etc) to be performed for synchronisation purpose by the Node B at each of these SFNs. + +Within the synchronisation frames, only the first subframe shall be used for sending or receiving a SYNC\_DL Code in the DwPTS while in the second subframe, normal operation continues. + +The synchronisation schedule includes the option of averaging of measured correlation results within the Node B over a sequence of measurements, for increasing the reliability of the Time of Arrival measurement obtained from the correlation results. For this purpose, the concept of "subcycles" has been introduced: Each Synchronisation Cycle is divided into "subcycles" where in each subcycle, the same set of SYNC\_DL transmissions and receptions is performed, and averaging takes place over all the subcycles within a Synchronisation Cycle. Since the list of actions (transmission, measurements etc) is the same in each subcycle, and the subcycles are repeated to make up a cycle, and the cycles make up an SFN period, the full list of actions is derived by the actions specified for a subcycle. + +The full list of SFNs which make up the synchronisation schedule within the SFN period are calculated in Node B and CRNC autonomously based on the following parameters included in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message: "Number of cycles per SFN period", "Number of subcycles per cycle period", and "Number of repetitions per cycles period", along the following equations: + +Cycle length: $4096 / \text{value of Number Of Cycles Per SFN Period IE}$ + +Subcycle length: $\text{Cycle length} / \text{value of Number Of Subcycles Per Cycle Period IE}$ + +Repetition period: $\text{Subcycle length} / \text{value of Number Of Repetitions Per Cycle Period IE}$ + +$\text{SFN} = \text{floor}((k-1) * \text{Cycle length} + (j-1)*\text{Subcycle length} + (i-1)* \text{Repetition period})$ + +$k = \{1, 2, 3, \dots \text{ Number of cycle per SFN period}\}$ + +$j = \{1, 2, 3, \dots \text{ Number of subcycles per cycle}\}$ + +$i = \{1, 2, 3, \dots \text{ Number of repetitions per cycle period}\}$ + +Note that if the *Number Of Subcycles Per Cycle IE* is equal to 1, then the subcycles are identical to the "Synchronisation Cycles". + +If the *Number Of Subcycles Per Cycle IE* is included in the CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD] message, then the Node B shall apply this number for dividing the Synchronisation Cycles in Subcycles. If the IE is not present, then the Node B shall assume that there is one subcycle per synchronisation cycle only, which is identical to the synchronisation cycle. + +Averaging is performed as follows: + +- From each SYNC\_DL code being received according to the schedule, the Node B shall calculate a "correlation function" by matching the received data with the respective expected code. +- Therefore the set of measurements within one subcycle provides a set of "correlation functions". +- The set of correlation functions of the first subcycle within a synchronisation cycle is stored in an averaging memory. +- The sets of correlation functions of the subsequent subcycles within a synchronisation cycle are combined with the available contents of the "averaging memory", to produce an average over all the sets of correlation functions within a synchronisation cycle. + +- At the end of a synchronisation cycle, the Time-of-Arrival measurements for that synchronisation cycle are obtained by evaluating the final set of correlation functions. + +These Time-of-Arrival measurements, together with associated SIR values obtained from the averaged correlation functions, are included in a Measurement Report to the CRNC, according to a measurement reporting plan. + +In addition, the Time-of-Arrival measurements may optionally be used for autonomous self-adjustment of the timing of the respective cell. + +#### 8.2.21.2.4 [3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration] [1.28Mcps TDD - SYNC\_DL Code Transmission Reconfiguration] + +When the [3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration Information] [1.28Mcps TDD - SYNC\_DL Code Transmission Reconfiguration Information LCR] is present, the Node B shall reconfigure the transmission of the [3.84Mcps TDD - cell synchronisation burst] [1.28Mcps TDD - SYNC\_DL Code] according to the parameters given in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. + +[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the *Cell Sync Burst Code* IE, the Node B shall reconfigure the synchronisation code in the cell according to the *Cell Sync Burst Code* IE value.] + +[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the *Cell Sync Burst Code Shift* IE, the Node B shall reconfigure the synchronisation code shift in the cell according to the *Cell Sync Burst Code Shift* IE value.] + +[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the *DL Transmission Power* IE, the Node B shall reconfigure the DL transmission power of the cell synchronisation burst in the cell according to the *DL Transmission Power* IE value.] + +[1.28Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the *DwPCH Power* IE, the Node B shall store the DwPCH power according to the *DwPCH Power* IE value. For the duration of those subsequent transmissions of the DwPCH which are specifically for the purpose of Node B synchronisation the power of the DwPCH shall be set to the stored power. During subsequent transmissions of the DwPCH which are for normal operation the power of the DwPCH shall assume its normal level.] + +[1.28Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the *Sync\_DL Code ID* IE, the Node B shall reconfigure the SYNC\_DL Code in the cell according to the *Sync\_DL Code ID* IE value.] + +#### 8.2.21.2.5 [3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration] [1.28Mcps TDD - SYNC\_DL Code Measurement Reconfiguration] + +When the [3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration Information] [1.28Mcps TDD - Cell SYNC\_DL Code Measurement Reconfiguration Information LCR] is present, the Node B shall reconfigure the [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Code] measurements according to the parameters given in the message. + +If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the [3.84Mcps TDD - Cell Sync Burst Measurement Information] [1.28Mcps TDD - SYNC\_DL Code Measurement Information LCR], the measurements shall apply on the individual [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Codes] on the requested Sync Frame number. + +[1.28Mcps TDD - When the *Propagation Delay Compensation* IE is present in the SYNC\_DL Code Measurement Information LCR, the Node B shall, if supported, perform the following functions: (1) use the respective SYNC\_DL measurement (after potential averaging) to perform the self-adjustment of the respective cell's timing at the end of a Synchronisation Cycle; (2) include the *Accumulated Clock Update* IE in the CELL SYNCHRONISATION REPORT message, to report the total accumulated amount of timing adjustments since the last report to the RNC. This Accumulated Clock Update value shall also include the adjustments which may have been performed by explicit order from the CRNC in the CELL SYNCHRONISATION ADJUSTMENT REQUEST message. The times for self-adjustment at the end of a synchronisation cycle shall be independent from the measurement reporting characteristics; the Accumulated Adjustment values shall be included in the CELL SYNCHRONISATION REPORT messages without influencing the frequency of measurement reporting.] + +If the *Synchronisation Report Type* IE is provided, the measurement reporting shall apply according to the parameter given in the message. + +### Synchronisation Report characteristics: + +The *Synchronisation Report Characteristics* IE indicates how the reporting of the cell synchronisation burst measurement shall be performed. + +If the *Synchronisation Report Characteristics Type* IE is set to "Frame related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] measurement after every measured frame. + +If the *Synchronisation Report Characteristics Type* IE is set to "SFN period related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] measurements after every SFN period. + +If the *Synchronisation Report Characteristics Type* IE is set to "Cycle length related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] measurements after every cycle length within the SFN period. + +If the *Synchronisation Report Characteristics Type* IE is set to "Threshold exceeding", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] measurement when the [3.84Mcps TDD - Cell Synchronisation Burst timing] [1.28Mcps TDD - SYNC\_DL Code timing] rises or falls more than the requested threshold value compared to the arrival time in synchronised state which is represented by the [3.84Mcps TDD - *Cell Sync Burst Arrival Time* IE] [1.28Mcps TDD - *SYNC\_DL Code ID Arrival Time* IE]. + +[3.84Mcps TDD - If the *Cell Sync Burst Arrival Time* IE is included in the *Cell Sync Burst Information* IE of the *Synchronisation Report Characteristics* IE, it indicates to the Node B the reference time at which the reception of the cell synchronisation burst of a neighbouring cell is expected.] + +[3.84Mcps TDD - If the *Cell Sync Burst Timing Threshold* IE is included in the *Cell Sync Burst Information* IE of the *Synchronisation Report Characteristics* IE, the Node B shall use this new threshold as a trigger for the CELL SYNCHRONISATION REPORT message.] + +[1.28Mcps TDD - If the *SYNC\_DL Code ID Arrival Time* IE is included in the *SYNC\_DL Code Information LCR* IE of the *Synchronisation Report Characteristics* IE, it indicates to the Node B the reference time at which the reception of the SYNC\_DL Code of a neighbouring cell is expected.] + +[1.28Mcps TDD - If the *SYNC\_DL Code ID Timing Threshold* IE is included in the *SYNC\_DL Code Information LCR* IE of the *Synchronisation Report Characteristics* IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.] + +### Response message: + +If the Node B was able to reconfigure the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] transmission and/or measurement requested by the CRNC, it shall respond with the CELL SYNCHRONISATION RECONFIGURATION RESPONSE message sent over the Node B Control Port. + +## 8.2.21.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Cell Synchronisation Reconfiguration procedure. The diagram shows two vertical lines representing the CRNC and Node B. A solid arrow points from the CRNC to the Node B, labeled 'CELL SYNCHRONISATION RECONFIGURATION REQUEST'. A dashed arrow points from the Node B back to the CRNC, labeled 'CELL SYNCHRONISATION RECONFIGURATION FAILURE'.](85412017cb0c8ea0fd14bdaab53baeae_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: CELL SYNCHRONISATION RECONFIGURATION REQUEST + CRNC->>Node B: CELL SYNCHRONISATION RECONFIGURATION REQUEST + Note left of Node B: CELL SYNCHRONISATION RECONFIGURATION FAILURE + Node B-->>CRNC: CELL SYNCHRONISATION RECONFIGURATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Cell Synchronisation Reconfiguration procedure. The diagram shows two vertical lines representing the CRNC and Node B. A solid arrow points from the CRNC to the Node B, labeled 'CELL SYNCHRONISATION RECONFIGURATION REQUEST'. A dashed arrow points from the Node B back to the CRNC, labeled 'CELL SYNCHRONISATION RECONFIGURATION FAILURE'. + +**Figure 27F Cell Synchronisation Reconfiguration procedure, Unsuccessful Operation** + +If the Node B cannot reconfigure the requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code], the CELL SYNCHRONISATION RECONFIGURATION FAILURE message shall be sent to the CRNC. The message shall include the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +### Radio Network Layer Cause: + +- Cell Synchronisation not supported + +- Power level not supported +- Measurement Temporarily not Available + +#### Miscellaneous Cause: + +- O&M Intervention +- HW failure + +### 8.2.21.4 Abnormal Conditions + +- + +## 8.2.22 Cell Synchronisation Reporting [TDD] + +### 8.2.22.1 General + +This procedure is used by a Node B to report the result of [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Code] measurements requested by the CRNC with the Cell Synchronisation Initiation or Cell Synchronisation Reconfiguration procedure. + +### 8.2.22.2 Successful Operation + +![Sequence diagram showing the Cell Synchronisation Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'CELL SYNCHRONISATION REPORT' centered above the arrow.](305c3b31c7d60405cf039fd098ba4669_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: CELL SYNCHRONISATION REPORT + Node B->>CRNC: CELL SYNCHRONISATION REPORT + +``` + +Sequence diagram showing the Cell Synchronisation Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'CELL SYNCHRONISATION REPORT' centered above the arrow. + +**Figure 27G Cell Synchronisation Reporting procedure, Successful Operation** + +If the requested synchronisation measurement reporting criteria are met, the Node B shall initiate a Cell Synchronisation Reporting procedure. The CELL SYNCHRONISATION REPORT message shall use the Node B Control Port. + +In the steady state phase when several [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Codes] shall be measured per Sync Frame number, the sequence of the reported measured values shall be the same as defined in the Cell Synchronisation Reconfiguration procedure. + +[1.28Mcps TDD - The Node B shall, if supported, include the *Accumulated Clock Update* IE in the CELL SYNCHRONISATION REPORT message whenever the CRNC has included at least one instance of the *Propagation Delay Compensation* IE in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. The *Accumulated Clock Update* IE shall include the accumulated timing adjustment which has been done as commanded by the CRNC, as well as by self-adjustment, since the last *Accumulated Clock Update* IE report.] + +If the achieved measurement accuracy does not fulfil the given accuracy requirement defined in TS 25.123 [23], the Cell Sync Burst not available shall be reported. + +### 8.2.22.3 Abnormal Conditions + +- + +## 8.2.23 Cell Synchronisation Termination [TDD] + +### 8.2.23.1 General + +This procedure is used by the CRNC to terminate a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] transmission or measurement previously requested by the Cell Synchronisation Initiation procedure or Cell Synchronisation Reconfiguration procedure. + +### 8.2.23.2 Successful Operation + +![Sequence diagram for Cell Synchronisation Termination procedure, Successful Operation](f0addfb9cb95476594c62d37d1208037_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow points from the CRNC to the Node B. Above the arrow, the text "CELL SYNCHRONISATION TERMINATION REQUEST" is displayed. + +Sequence diagram for Cell Synchronisation Termination procedure, Successful Operation + +**Figure 27H Cell Synchronisation Termination procedure, Successful Operation** + +This procedure is initiated with a CELL SYNCHRONISATION TERMINATION REQUEST message, sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall terminate [3.84Mcps TDD - transmission of Cell Synchronisation Bursts or reporting of Cell Synchronisation Burst measurements] [1.28Mcps TDD - transmission of SYNC\_DL Codes or reporting of SYNC\_DL Code measurements] corresponding to the *CSB Transmission ID IE* or *CSB Measurement ID IE*. + +### 8.2.23.3 Abnormal Conditions + +- + +## 8.2.24 Cell Synchronisation Failure [TDD] + +### 8.2.24.1 General + +This procedure is used by the Node B to notify the CRNC that a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] transmission or synchronisation measurement procedure can no longer be supported. + +### 8.2.24.2 Successful Operation + +![Sequence diagram for Cell Synchronisation Failure procedure, Successful Operation](0d0a2d20d13bb78869a2d42f736d0c7a_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow points from the Node B to the CRNC. Above the arrow, the text "CELL SYNCHRONISATION FAILURE INDICATION" is displayed. + +Sequence diagram for Cell Synchronisation Failure procedure, Successful Operation + +**Figure 27I Cell Synchronisation Failure procedure, Successful Operation** + +This procedure is initiated with a CELL SYNCHRONISATION FAILURE INDICATION message, sent from the Node B to the CRNC using the Node B Control Port, to inform the CRNC that a previously requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC\_DL Codes] can no longer be supported. + +If the transmission of a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] has failed, then the Node B shall include the *CSB Transmission ID IE* in the CELL SYNCHRONISATION FAILURE INDICATION message to uniquely identify the concerned [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] Transmission. + +If the measurement of a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] has failed, then the Node B shall include the *CSB Measurement ID IE* in the CELL SYNCHRONISATION FAILURE + +INDICATION message to uniquely identify the concerned [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC\_DL Code] Measurement. + +### 8.2.24.3 Abnormal Conditions + +- + +## 8.2.25 Cell Synchronisation Adjustment [TDD] + +### 8.2.25.1 General + +The purpose of Cell Synchronisation Adjustment procedure is to allow the CRNC to adjust the timing of the radio transmission of a cell within a Node B for time alignment. + +### 8.2.25.2 Successful Operation + +![Sequence diagram showing the successful operation of Cell Synchronisation Adjustment. The CRNC sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST message to Node B, and Node B responds with a CELL SYNCHRONISATION ADJUSTMENT RESPONSE message.](6399940001d500190d1024ea66f2f7f0_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: CELL SYNCHRONISATION ADJUSTMENT REQUEST + CRNC->>Node B: CELL SYNCHRONISATION ADJUSTMENT REQUEST + Note left of Node B: CELL SYNCHRONISATION ADJUSTMENT RESPONSE + Node B-->>CRNC: CELL SYNCHRONISATION ADJUSTMENT RESPONSE + +``` + +Sequence diagram showing the successful operation of Cell Synchronisation Adjustment. The CRNC sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST message to Node B, and Node B responds with a CELL SYNCHRONISATION ADJUSTMENT RESPONSE message. + +**Figure 27J Cell Synchronisation Adjustment, Successful Operation** + +This procedure is initiated with a CELL SYNCHRONISATION ADJUSTMENT REQUEST message sent by the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B adjusts its timing according to the parameters given in the message. + +If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *Frame Adjustment Value* IE the Node B shall apply the frame adjustment in the cell according to the *Frame Adjustment Value* IE value. + +[3.84Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *Timing Adjustment Value* IE the Node B shall apply the timing adjustment in the cell according to the *Timing Adjustment Value* IE value.] + +[1.28Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *Timing Adjustment Value LCR* IE the Node B shall apply the timing adjustment in the cell according to the *Timing Adjustment Value LCR* IE value.] + +[3.84Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *DL Transmission Power* IE, the Node B shall apply the transmission power of the Cell Synchronisation Burst according to the *DL Transmission Power* IE value.] + +[1.28Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *DwPCH Power* IE, the Node B shall store the DwPCH power according to the *DwPCH Power* IE value. For the duration of those subsequent transmissions of the DwPCH which are specifically for the purpose of Node B synchronisation the power of the DwPCH shall be set to the stored power. During subsequent transmissions of the DwPCH which are for normal operation the power of the DwPCH shall assume its normal level.] + +If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the *SFN* IE, the Node B shall apply the synchronisation adjustment starting with the SFN number indicated in the message. + +When the cell synchronisation adjustment is successfully done by the Node B, the Node B shall respond with a CELL SYNCHRONISATION ADJUSTMENT RESPONSE message. + +### 8.2.25.3 Unsuccessful Operation + +![Sequence diagram for Cell Synchronisation Adjustment, Unsuccessful Operation. A CRNC sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION ADJUSTMENT FAILURE.](48090d8f1db2e826aaa740035aa12ecb_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: CELL SYNCHRONISATION ADJUSTMENT REQUEST + CRNC->>Node B: CELL SYNCHRONISATION ADJUSTMENT REQUEST + Note left of Node B: CELL SYNCHRONISATION ADJUSTMENT FAILURE + Node B-->>CRNC: CELL SYNCHRONISATION ADJUSTMENT FAILURE + +``` + +Sequence diagram for Cell Synchronisation Adjustment, Unsuccessful Operation. A CRNC sends a CELL SYNCHRONISATION ADJUSTMENT REQUEST to Node B, and Node B responds with a CELL SYNCHRONISATION ADJUSTMENT FAILURE. + +**Figure 27K Cell Synchronisation Adjustment, Unsuccessful Operation** + +If the Node B cannot perform the indicated cell synchronisation adjustment due to hardware failure or other problem it shall send the CELL SYNCHRONISATION ADJUSTMENT FAILURE as a response. + +Typical cause values are as follows: + +#### Radio Network Layer Cause + +- Cell Synchronisation Adjustment not supported +- Power level not supported + +#### Miscellaneous Cause + +- O&M Intervention +- HW failure + +### 8.2.25.4 Abnormal Conditions + +- + +## 8.2.26 Information Exchange Initiation + +### 8.2.26.1 General + +This procedure is used by a CRNC to request the initiation of information provisioning from a Node B. + +### 8.2.26.2 Successful Operation + +![Sequence diagram for Information Exchange Initiation procedure, Successful Operation. A CRNC sends an INFORMATION EXCHANGE INITIATION REQUEST to Node B, and Node B responds with an INFORMATION EXCHANGE INITIATION RESPONSE.](78258750e6697a1b47b76f9df9735773_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: INFORMATION EXCHANGE INITIATION REQUEST + CRNC->>Node B: INFORMATION EXCHANGE INITIATION REQUEST + Note left of Node B: INFORMATION EXCHANGE INITIATION RESPONSE + Node B-->>CRNC: INFORMATION EXCHANGE INITIATION RESPONSE + +``` + +Sequence diagram for Information Exchange Initiation procedure, Successful Operation. A CRNC sends an INFORMATION EXCHANGE INITIATION REQUEST to Node B, and Node B responds with an INFORMATION EXCHANGE INITIATION RESPONSE. + +**Figure 27L: Information Exchange Initiation procedure, Successful Operation** + +The procedure is initiated with the INFORMATION EXCHANGE INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall provide the requested information according to the *Information Type Item* IE. Unless specified below, the meaning of the parameters are given in other specifications. + +If the *Information Type* IE contains a *GANSS Generic Data* IE, at least one of the *GANSS Navigation Model And Time Recovery*, *GANSS Time Model GNSS-GNSS*, *GANSS UTC Model*, *GANSS Almanac*, *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *GANSS Additional Navigation Models And Time Recovery*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information*, *DBDS Corrections Request*, *BDS Ionospheric Grid Model Request* IEs shall be present in the *GANSS Generic Data* IE. + +- If the *GANSS Generic Data* IE does not contain the *GANSS ID* IE, the Node B shall assume that the corresponding GANSS is "Galileo". + +### Information Report Characteristics + +The *Information Report Characteristics* IE indicates how the reporting of the information shall be performed. + +If the *Information Report Characteristics* IE is set to "On Demand", the Node B shall report the requested information immediately. + +If the *Information Report Characteristics* IE is set to "Periodic", the Node B shall immediately report the requested information and then shall periodically initiate the Information Reporting procedure for all the requested information, with the requested reporting frequency. + +If the *Information Report Characteristics* IE is set to "On Modification", the Node B shall immediately report the requested information if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the Node B shall initiate the Information Reporting procedure when the requested information becomes available. The Node B shall then initiate the Information Reporting procedure in accordance to the following conditions related to the *Information Type* IE: + +- 1) If the *Information Type Item* IE is set to "DGPS Corrections", the Node B shall initiate the Information Reporting procedure when either the PRC has drifted from the previously reported value more than the threshold indicated in the *PRC Deviation* IE in the *Information Threshold* IE or a change has occurred in the IODE. +- 2) If the *Information Type Item* IE is set to "GPS Information" and the *GPS Information Item* IE includes "GPS Navigation Model & Time Recovery", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred regarding either the IODC or the list of visible satellites, identified by the *Sat ID* IEs. +- 3) If the *Information Type Item* IE is set to "GPS Information" and the *GPS Information Item* IE includes "GPS Ionospheric Model", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred. +- 4) If the *Information Type Item* IE is set to "GPS Information" and the *GPS Information Item* IE includes "GPS UTC Model", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred in the $t_{ot}$ or $WN_t$ parameter. +- 5) If the *Information Type Item* IE is set to "GPS Information" and the *GPS Information Item* IE includes "GPS Almanac", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change in the $t_{oa}$ or $WN_a$ parameter has occurred. +- 6) If the *Information Type Item* IE is set to "GPS Information" and the *GPS Information Item* IE includes "GPS Real-Time Integrity", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred. +- 7) If the *Information Type Item* IE is set to "DGANSS Corrections", the Node B shall initiate the Information Reporting procedure when either the PRC has drifted from the previously reported value more than the threshold indicated in the *PRC Deviation* IE in the *Information Threshold* IE or a change has occurred in the IOD. +- 8) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Navigation Model And Time Recovery* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the *Sat ID* IEs. +- 9) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Ionospheric Model* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 10) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Time Model* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 11) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS UTC Model* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the $t_{ot}$ or $WN_t$ parameter. + +- 12) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Almanac* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change in the $T_{oa}$ , $IOD_a$ or Week Number parameter has occurred. +- 13) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Real Time Integrity* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred +- 14) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Data Bit Assistance* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 15) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Additional Navigation Models And Time Recovery* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the *Sat ID* IEs. +- 16) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Additional Ionospheric Model* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 17) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Additional UTC Models* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the $t_{ot}$ , $WN_{ot}$ , $WN_t$ , or $N^A$ parameter. +- 18) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Earth Orientation Parameters* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the $t_{EOP}$ parameter. +- 19) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Auxiliary Information* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the *Signals Available* or *Channel Number* IE parameter. +- 20) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *DBDS Corrections Request* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 21) If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *BDS Ionospheric Grid Model Request* IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. +- 22) If any of the above *Information Type* IEs becomes temporarily unavailable, the Node B shall initiate the Information Reporting procedure for this specific Information Item by indicating "Information Not Available" in the *Requested Data Value Information* IE. If the Information becomes available again, the Node B shall initiate the Information Reporting procedure for this specific Information. + +### Response message + +If the Node B is able to initiate the information provision requested by the CRNC, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message sent over the Node B Control Port. The message shall include the same Information Exchange ID that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the *Report Characteristics* IE is set to "On Modification" or "Periodic", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the requested data if the data are available. When the *Report Characteristics* IE is set to "On Demand", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the *Requested Data Value* IE. + +If the *Requested Data Value* IE contains the *GANSS Common Data* IE, at least one of the *GANSS Ionospheric Model*, *GANSS RX Pos*, *GANSS Additional Ionospheric Model*, or *GANSS Earth Orientation Parameters* IEs shall be present. + +Any *GANSS Generic Data* IE associated with a given GANSS included in the *Requested Data Value* IE shall contain at least one of the *DGANSS Corrections*, *GANSS Navigation Model And Time Recovery*, *GANSS Time Model*, *GANSS UTC Model*, *GANSS Almanac*, *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *GANSS Additional Time Models*, *GANSS Additional Navigation Models And Time Recovery*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information*, *DBDS Corrections*, or *BDS Ionospheric Grid Model* IEs. + +- If the *GANSS Generic Data* IE does not contain the *GANSS ID* IE, the corresponding GANSS is "Galileo". +- The *DGANSS Corrections* IE contains one or several *DGANSS Information* IE(s), each of them associated with a GANSS Signal. A *DGANSS Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [18], clause 10.3.3.45a. +- The *DBDS Corrections* IE contains one or several *DBDS information* IE(s), each of them associated with a GANSS Signal. A *DBDS information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [18], clause 10.3.3.45a. +- The *GANSS Real Time Integrity* IE contains one or several *Satellite Information* IEs, each of them associated with a satellite and a GANSS Signal. A *Satellite Information* IE for a particular GANSS that does not contain the *Bad GANSS Signal ID* IE is by default associated with all the signals of the corresponding satellite (see [39, 43, 44, 45, 46, 47, 48]). + +If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Time Model GNSS-GNSS* IE with exactly one bit set to value "1", the Node B shall include the *GANSS Time Model* IE in the *Requested Data Value* IE with the requested time information. + +If the *Information Type Item* IE is set to "GANSS Information" and the *GANSS Information* IE includes the *GANSS Time Model GNSS-GNSS* IE with more than one bit set to value "1", the Node B shall include the *GANSS Additional Time Models* IE in *Requested Data Value* IE with the requested time information for each GANSS. + +If the *Information Type Item* IE is set to "DGPS Corrections", the Node B shall include the *DGPS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available. + +If the *Information Type Item* IE is set to "DGANSS Corrections", the Node B shall include the *DGANSS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available. + +If the *Information Type Item* IE is set to "GPS Almanac", the Node B shall include the *GPS Almanac* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available. + +If the *Information Type Item* IE is set to "GANSS Almanac", the Node B shall include the *GANSS Almanac* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available. + +If the *Information Type Item* IE is set to "GANSS Time Model GNSS-GNSS", the Node B shall include the *GANSS Time Model* IE in *Requested Data Value* IE with the *Delta\_T* IE included, if available. + +### 8.2.26.3 Unsuccessful Operation + +![Sequence diagram showing the Information Exchange Initiation procedure for an Unsuccessful Operation. A CRNC sends an INFORMATION EXCHANGE INITIATION REQUEST to Node B, and Node B responds with an INFORMATION EXCHANGE INITIATION FAILURE.](c75343ea87825a0429d6a0ad27e2a6cd_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: INFORMATION EXCHANGE INITIATION REQUEST + CRNC->>Node B: INFORMATION EXCHANGE INITIATION REQUEST + Note left of Node B: INFORMATION EXCHANGE INITIATION FAILURE + Node B-->>CRNC: INFORMATION EXCHANGE INITIATION FAILURE + +``` + +Sequence diagram showing the Information Exchange Initiation procedure for an Unsuccessful Operation. A CRNC sends an INFORMATION EXCHANGE INITIATION REQUEST to Node B, and Node B responds with an INFORMATION EXCHANGE INITIATION FAILURE. + +**Figure 27M: Information Exchange Initiation procedure, Unsuccessful Operation** + +If the *Information Type Item* received in the *Information Type Item* IE indicates a type of information that cannot be provided, the Node B shall regard the Information Exchange Initiation procedure as failed. + +If the requested information provision cannot be initiated, the Node B shall send the INFORMATION EXCHANGE INITIATION FAILURE message over the Node B control port. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +#### Radio Network Layer Cause + +- Information temporarily not available. + +- Information Provision not supported for the object. + +#### 8.2.26.4 Abnormal Conditions + +If the *Information Report Characteristics* IE is set to "On Modification", and the *Information Type Item* IE is set to "DGPS Corrections", or "DGANSS Corrections", but the *Information Threshold* IE is not received in the INFORMATION EXCHANGE INITIATION REQUEST message, the Node B shall regard the Information Exchange Initiation procedure as failed. + +If the *Information Type Item* IE is not set to "DGPS Correction" or "DGANSS Corrections", the *Information Report Characteristics* IE is set to "On Modification" and the *Information Threshold* IE is included in the INFORMATION EXCHANGE INITIATION REQUEST message, the Node B shall regard the Information Exchange Initiation procedure as failed. + +### 8.2.27 Information Reporting + +#### 8.2.27.1 General + +This procedure is used by a Node B to report the information requested by the CRNC with the Information Exchange Initiation procedure. + +#### 8.2.27.2 Successful Operation + +![Sequence diagram showing the Information Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'INFORMATION REPORT' centered above the arrow.](832570a3a00d9064e8068d0bb5def3a9_img.jpg) + +``` +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: INFORMATION REPORT + Node B->>CRNC: INFORMATION REPORT +``` + +Sequence diagram showing the Information Reporting procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from the Node B line to the CRNC line, with the text 'INFORMATION REPORT' centered above the arrow. + +**Figure 27N: Information Reporting procedure, Successful Operation** + +If the requested information reporting criteria are met, the Node B shall initiate the Information Reporting procedure. The INFORMATION REPORT message shall use the Node B Control Port. Unless specified below, the meaning of the parameters are given in other specifications. + +The *Information Exchange ID* IE shall be set to the Information Exchange ID provided by the CRNC when initiating the Information Exchange with the Information Exchange Initiation procedure. + +The *Requested Data Value* IE shall include at least one IE containing the data to be reported. + +#### 8.2.27.3 Abnormal Conditions + +- + +### 8.2.28 Information Exchange Termination + +#### 8.2.28.1 General + +This procedure is used by the CRNC to terminate the provision of information previously requested by the Information Exchange Initiation procedure. + +## 8.2.28.2 Successful Operation + +![Sequence diagram for Figure 27O: Information Exchange Termination procedure, Successful Operation. A message labeled 'INFORMATION EXCHANGE TERMINATION REQUEST' is sent from CRNC to Node B.](f3c73e8e478b8b2d9f6a96a970040556_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: INFORMATION EXCHANGE TERMINATION REQUEST +``` + +Sequence diagram for Figure 27O: Information Exchange Termination procedure, Successful Operation. A message labeled 'INFORMATION EXCHANGE TERMINATION REQUEST' is sent from CRNC to Node B. + +**Figure 27O: Information Exchange Termination procedure, Successful Operation** + +This procedure is initiated with an INFORMATION EXCHANGE TERMINATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception, the Node B shall terminate the provision of information corresponding to the Information Exchange ID. + +## 8.2.28.3 Abnormal Conditions + +- + +## 8.2.29 Information Exchange Failure + +### 8.2.29.1 General + +This procedure is used by the Node B to notify the CRNC that information previously requested by the Information Exchange Initiation procedure can no longer be reported. + +### 8.2.29.2 Successful Operation + +![Sequence diagram for Figure 27P: Information Exchange Failure procedure, Successful Operation. A message labeled 'INFORMATION EXCHANGE FAILURE INDICATION' is sent from Node B to CRNC.](e67bca96ac67ddab7a8762b49d4c438d_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Node B->>CRNC: INFORMATION EXCHANGE FAILURE INDICATION +``` + +Sequence diagram for Figure 27P: Information Exchange Failure procedure, Successful Operation. A message labeled 'INFORMATION EXCHANGE FAILURE INDICATION' is sent from Node B to CRNC. + +**Figure 27P: Information Exchange Failure procedure, Successful Operation** + +This procedure is initiated with the INFORMATION EXCHANGE FAILURE INDICATION message sent from the Node B to the CRNC using the Node B Control Port to inform the CRNC that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +## 8.2.30 MBMS Notification Update + +### 8.2.30.1 General + +This procedure is used to update the MBMS Notification Indicators to be sent over the MICH. + +### 8.2.30.2 Successful Operation + +![Sequence diagram for Figure 27Q: MBMS Notification Update procedure, Successful Operation. A message labeled 'MBMS NOTIFICATION UPDATE COMMAND' is sent from CRNC to Node B.](5be761f3d780e80637364abc66fa3916_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: MBMS NOTIFICATION UPDATE COMMAND +``` + +Sequence diagram for Figure 27Q: MBMS Notification Update procedure, Successful Operation. A message labeled 'MBMS NOTIFICATION UPDATE COMMAND' is sent from CRNC to Node B. + +**Figure 27Q: MBMS Notification Update procedure, Successful Operation** + +The procedure is initiated with an MBMS NOTIFICATION UPDATE COMMAND message sent from the CRNC to the Node B using the Node B Control Port. + +The Node B shall use the different NIs in the *NI Information* IE to generate, as specified in ref. TS 25.211 [7], the notification indicators it shall transmit on the MICH starting at the next coming MICH CFN equal to the value in the *MICH CFN* IE and for a duration equal to the Modification Period. If the value of *MICH CFN* IE is the same as the one in a previously received MBMS NOTIFICATION UPDATE COMMAND message, and if the MICH CFN occurrence has not been reached yet, the Node B shall overwrite the value of the *NI Information* IE in the previously received MBMS NOTIFICATION UPDATE COMMAND message. + +If the *Modification Period* IE is included in the MBMS NOTIFICATION UPDATE COMMAND message, the Node B shall use this as the new Modification Period starting at the next coming MICH CFN equal to the value in the *MICH CFN* IE. If the value of *MICH CFN* IE is the same as the one in a previously received MBMS NOTIFICATION UPDATE COMMAND message, and if the MICH CFN occurrence has not been reached yet, the Node B shall overwrite the value of the *Modification Period* IE in the previously received MBMS NOTIFICATION UPDATE COMMAND message. + +If the *Modification Period* IE is not included in the MBMS NOTIFICATION UPDATE COMMAND message, the Node B shall use the lastest stored Modification Period. + +### 8.2.30.3 Abnormal Conditions + +If the *Modification Period* IE is not included in the MBMS NOTIFICATION UPDATE COMMAND message and no Modification Period is stored in the Node B, the Node B shall initiate the Error Indication procedure. + +## 8.2.31 UE Status Update [FDD and 1.28Mcps TDD] + +### 8.2.31.1 General + +This procedure is used by the CRNC to inform Node B that one or several E-RNTIs, previously allocated to UEs in CELL\_FACH or URA\_PCH state, may be released as the UE no longer use the E-RNTI. + +### 8.2.31.2 Successful Operation + +![Sequence diagram showing the UE Status Update procedure, Successful Operation. A horizontal arrow labeled 'UE STATUS UPDATE COMMAND' points from the CRNC to the Node B.](39e4a95c2c20ea45e33f953869f345bc_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: UE STATUS UPDATE COMMAND + CRNC->>Node B: UE STATUS UPDATE COMMAND +``` + +Sequence diagram showing the UE Status Update procedure, Successful Operation. A horizontal arrow labeled 'UE STATUS UPDATE COMMAND' points from the CRNC to the Node B. + +**Figure 27R: UE Status Update procedure, Successful Operation** + +The procedure is initiated with a UE STATUS UPDATE COMMAND message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception of the UE STATUS UPDATE COMMAND message, the Node B may use the information about vacant E-RNTI in *Vacant E-RNTI* IE in *Cell E-RNTI status information* IE to determine which E-RNTIs are no longer used in the cell and thus allowed to be allocated to another UE using E-DCH + +### 8.2.31.3 Abnormal Conditions + +- + +## 8.2.32 UE Status Update Confirmation [FDD and 1.28Mcps TDD] + +### 8.2.32.1 General + +This procedure is used by the CRNC to inform the Node B that one or several E-RNTIs, previously allocated to UEs in CELL\_FACH or URA\_PCH state, may be released as the UE no longer uses the E-RNTI. The Node B then responds with the status of the releasing procedure. + +## 8.2.32.2 Successful Operation + +![Sequence diagram for UE Status Update Confirmation procedure, Successful Operation](b15cf8c50195a52cca59b4645c6f59fa_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: UE STATUS UPDATE CONFIRM REQUEST + CRNC->>Node B: UE STATUS UPDATE CONFIRM REQUEST + Note left of Node B: UE STATUS UPDATE CONFIRM RESPONSE + Node B-->>CRNC: UE STATUS UPDATE CONFIRM RESPONSE +``` + +A sequence diagram showing the interaction between CRNC and Node B. The CRNC sends a 'UE STATUS UPDATE CONFIRM REQUEST' message to the Node B. The Node B responds with a 'UE STATUS UPDATE CONFIRM RESPONSE' message back to the CRNC. + +Sequence diagram for UE Status Update Confirmation procedure, Successful Operation + +**Figure 27S: UE Status Update Confirmation procedure, Successful Operation** + +The procedure is initiated with a UE STATUS UPDATE CONFIRM REQUEST message sent from the CRNC to the Node B using the Node B Control Port. + +Upon reception of the UE STATUS UPDATE CONFIRM REQUEST message, the Node B may use the information about vacant E-RNTI in *Vacant E-RNTI* IE in *Cell E-RNTI Status Information* IE to determine which E-RNTIs are no longer used in the cell and thus allowed to be allocated to another UE using E-DCH. The Node B shall, if supported, sends UE STATUS UPDATE CONFIRM RESPONSE to indicate that the releasing procedure is performed properly in the Node B. + +## 8.2.32.3 Abnormal Conditions + +- + +# 8.3 NBAP Dedicated Procedures + +## 8.3.1 Radio Link Addition + +### 8.3.1.1 General + +This procedure is used for establishing the necessary resources in the Node B for one or more additional RLs towards a UE when there is already a Node B Communication Context for this UE in the Node B. + +The Radio Link Addition procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. + +### 8.3.1.2 Successful Operation + +![Sequence diagram for Radio Link Addition procedure, Successful Operation](7cb62a0db45266260cb60c33f7c8b4d9_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: RADIO LINK ADDITION REQUEST + CRNC->>Node B: RADIO LINK ADDITION REQUEST + Note left of Node B: RADIO LINK ADDITION RESPONSE + Node B-->>CRNC: RADIO LINK ADDITION RESPONSE +``` + +A sequence diagram showing the interaction between CRNC and Node B. The CRNC sends a 'RADIO LINK ADDITION REQUEST' message to the Node B. The Node B responds with a 'RADIO LINK ADDITION RESPONSE' message back to the CRNC. + +Sequence diagram for Radio Link Addition procedure, Successful Operation + +**Figure: 28 Radio Link Addition procedure, Successful Operation** + +The procedure is initiated with a RADIO LINK ADDITION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context. + +Upon reception, the Node B shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. + +The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A. + +If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. + +#### Physical Channels Handling: + +[TDD - If the [3.84Mcps TDD - *UL DPCH Information* IE] [1.28Mcps TDD - *UL DPCH Information LCR* IE] [7.68Mcps TDD - *UL DPCH Information 7.68Mcps* IE] is present, the Node B shall configure the new UL DPCH(s) according to the parameters given in the message.] + +[TDD - If the [3.84Mcps TDD - *DL DPCH Information* IE] [1.28Mcps TDD - *DL DPCH Information LCR* IE] [7.68Mcps TDD - *DL DPCH Information 7.68Mcps* IE] is present, the Node B shall configure the new DL DPCH(s) according to the parameters given in the message.] + +[1.28Mcps TDD - If the *UL Timeslot Information LCR* IE includes the *PLCCH Information* IE, the Node B shall transmit TPC /SS bits on a PLCCH according to the parameters given in the message.] + +#### [FDD - Compressed Mode]: + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Compressed Mode Deactivation Flag* IE with value "Deactivate", the Node B shall not activate any compressed mode pattern in the new RLs. In all the other cases (Flag set to "Maintain Active" or not present), the ongoing compressed mode (if existing) shall be applied also to the added RLs.] + +[FDD - If the Node B Communication Context is configured to use DPCH in the downlink and if the RADIO LINK ADDITION REQUEST message contains the *Transmission Gap Pattern Sequence Code Information* IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated for each DL Channelisation Code for which the *Transmission Gap Pattern Sequence Code Information* IE is set to "Code Change".] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Active Pattern Sequence Information* IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received *CM Configuration Change CFN* refers to the latest passed CFN with that value The Node B shall treat the received *TGCFN* IEs as follows:] + +- [FDD - If any received *TGCFN* IE has the same value as the received *CM Configuration Change CFN* IE, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] +- [FDD - If any received *TGCFN* IE does not have the same value as the received *CM Configuration Change CFN* IE but the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE has already passed, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] +- [FDD - For all other Transmission Gap Pattern Sequences included in the *Active Pattern Sequence Information* IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the *CM Configuration Change CFN* with a value equal to the *TGCFN* IE for the Transmission Gap Pattern Sequence.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.] + +#### [FDD - DL Code Information]: + +[FDD - When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to ref. TS 25.212 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "*PhCH number 1*", the second to "*PhCH number 2*", and so on until the *p*th to "*PhCH number p*".] + +#### [TDD - CCTrCH Handling]: + +[TDD - If the *UL CCTrCH Information* IE is present, the Node B shall configure the new UL CCTrCH(s) according to the parameters given in the message.] + +[1.28Mcps TDD - If the *UL CCTrCH Information* IE includes the *TDD TPC UL Step Size* IE, the Node B shall configure the uplink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.] + +[TDD - If the *DL CCTrCH Information* IE is present, the Node B shall configure the new DL CCTrCH(s) according to the parameters given in the message.] + +[TDD - If the *DL CCTrCH Information* IE includes the *TDD TPC DL Step Size* IE, the Node B shall configure the downlink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.] + +[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the *TDD TPC DL Step Size* IE of the lowest numbered DL CCTrCH whose *DL CCTrCH Information* IE includes the *TDD TPC DL Step Size* IE. If no *DL CCTrCH Information* IE includes the *TDD TPC DL Step Size* IE, it shall use the step size configured in other radio link.] + +[1.28 Mcps TDD - If the *TDD TPC DL Step Size* IE is not included in the *DL CCTrCH Information* IE, the Node B shall use the *E-AGCH TPC step size* IE in the *E-PUCH Information LCR* IE in the *E-DCH Information 1.28Mcps* IE for HS-SCCH inner loop power control related operation.] + +#### **[FDD - UL CLTD Handling]:** + +[FDD - If the *UL CLTD Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights and then :] + +- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] +- [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.] + +#### **[FDD - UL MIMO Setup]:** + +[FDD - If the *UL MIMO Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.] + +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B] +- [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information* IE in the RADIO LINK ADDITION RESPONSE message. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-ROCH Power Offset* IE in the *UL MIMO Information* IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] +- [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence* IE in *UL MIMO DL Control Channel Information* IE in the RADIO LINK ADDITION RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE and it should include it for the Serving E-DCH RL.] + +#### **Radio Link Handling:** + +##### **Diversity Combination Control:** + +The *Diversity Control Field* IE indicates for each RL whether the Node B shall combine the new RL with existing RL(s) or not. + +- If the *Diversity Control Field* IE is set to "May", the Node B shall decide for any of the alternatives. +- If the *Diversity Control Field* IE is set to "Must", the Node B shall combine the RL with one of the other - RL. +- If the *Diversity Control Field* IE is set to "Must not", the Node B shall not combine the RL with any other existing RL. + +[FDD - The signalled *Diversity Control Field* IE is only applicable for DCHs. In case of E-DCH, if any UARFCN(s) of the cells in the added RL(s) is not equal to at least one of the UARFCN(s) of the cells in the existing RL(s) in the Node B Communication Context, the Diversity Control Field, for those RL(s) shall be assumed to be set to "May", otherwise it shall be assumed to be set to "Must".] + +When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with. + +In the case of not combining a RL with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or a RL previously listed in the RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message that no combining is done. In this case, the Node B shall: + +- include in the *DCH Information Response* IE both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DCH of the RL in the RADIO LINK ADDITION RESPONSE message. [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included]. +- [FDD - include in the RADIO LINK ADDITION RESPONSE message the *Transport Bearer Not Setup Indicator* IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the *Transport Bearer Not Requested Indicator* IE in the RADIO LINK ADDITION REQUEST message.] +- [FDD - For E-DCH, include in the *E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for the transport bearers to be established for each E-DCH MAC-d flow of this RL for which the *Transport Bearer Not Requested Indicator* IE was not included.] + +In the case of combining with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message that the RL is combined and if the ALCAP is not used [FDD - and the transport bearer for this DCH is already established], the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE included in the *RL Information* IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. In this case, the *RL ID* IE indicates (one of) the previously established RL(s) or a RL previously listed in this RADIO LINK ADDITION RESPONSE message with which the new RL is combined. + +[FDD - In the case of combining with an E-DCH RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, one of the previously established RLs or a RL previously listed in this RADIO LINK ADDITION RESPONSE message including the *E-DCH FDD Information Response* IE shall be regarded as the RL with which the concerned E-DCH RL is combined. In case E-DCH RL is established for the first time, the Node B shall include *E-DCH FDD Information Response* IE instead of using the Diversity Indication of DCH RL in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message. It shall include in the *E-DCH FDD Information Response* IE the *Binding ID* IE and *Transport Layer Address* IE for the transport bearers to be established for each E-DCH MAC-d flow of this E-DCH RL for which the *Transport Bearer Not Requested Indicator* IE was not included.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Additional E-DCH Cell Information RL Add Req* IE, then:] + +- [FDD - if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [FDD - if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] +- [FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:] + - [FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the *Transport Bearer Not Requested Indicator* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE to determine the transport bearer configuration in the new configuration for the MAC-d flow of the Secondary Uplink Frequency.] + - [FDD - If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.] + +In the case of a set of co-ordinated DCHs, the *Binding ID* IE and the *Transport Layer Address* IE shall be included for only one of the DCHs in a set of coordinated DCHs [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included]. + +[TDD - The Node B shall include in the RADIO LINK ADDITION RESPONSE message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DSCH and USCH.] + +#### **[FDD - Transmit Diversity]:** + +[FDD - If the *Transmit Diversity Indicator* IE and/or *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall activate/deactivate the Transmit Diversity for each new Radio Link and/or secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE and/or *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE and the already known diversity mode for the physical channel.] + +#### **DL Power Control:** + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Initial DL Transmission Power* IE, the Node B shall apply the given power to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or Power Balancing is activated. If no *Initial DL Transmission Power* IE is included, the Node B shall use any transmission power level currently used on already existing RLs for this Node B Communication Context. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) with DPC MODE currently configured for the relevant Node B Communication Context and the downlink power control procedure (see subclause 8.3.7).] + +[3.84 Mcps TDD and 7.68 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Initial DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the *Initial DL Transmission Power* IE included in the *RL Information* IE. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If + +no *Initial DL Transmission Power* IE is included (even if *CCTrCH Initial DL Transmission Power* IEs are included), the Node B shall use any transmission power level currently used on already existing CCTrCHs for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4).] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial DL power for each timeslot within a DCH type CCTrCH by the following rule: If the *Initial DL Transmission Power* IE is included in the *DL Timeslot Information LCR* IE, then the Node B shall use that power for the initial DL power and ignore the *DL Time Slot ISCP info LCR*, otherwise the initial DL power is the *Initial DL Transmission Power* IE included in the *RL Information* IE and if *DL Time Slot ISCP info LCR* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no *Initial DL Transmission Power* IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum DL Power* IE, the Node B shall store this value and not transmit with a higher power on any DL DPCH or on the F-DPCH of the RL. If no *Maximum DL Power* IE is included, any Maximum DL power stored for already existing RLs for this Node B Communication Context shall be applied. If the Node B Communication Context is configured to use DPCH in the downlink, during compressed mode, the $\delta P_{curr}$ , as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Minimum DL Power* IE, the Node B shall store this value and never transmit with a lower power on any DL DPCH or on the F-DPCH of the RL. If no *Minimum DL Power* IE is included, any Minimum DL power stored for already existing RLs for this Node B Communication Context shall be applied.] + +[3.84 Mcps TDD and 7.68 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum DL Power* IE, the Node B shall determine the maximum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the maximum CCTrCH DL power, otherwise the maximum CCTrCH DL power is the *Maximum DL Power* IE included in the *RL Information* IE. If no *Maximum DL Power* IE is included (even if *CCTrCH Maximum DL Transmission Power* IEs are included), any maximum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.] + +[3.84 Mcps TDD and 7.68 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Minimum DL Power* IE, the Node B shall determine the minimum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the minimum CCTrCH DL power, otherwise the minimum CCTrCH DL power is the *Minimum DL Power* IE included in the *RL Information* IE. If no *Minimum DL Power* IE is included (even if *CCTrCH Minimum DL Transmission Power* IEs are included), any minimum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum DL Power* IE, the Node B shall determine the maximum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the *Maximum DL Power* IE is included in the *DL Timeslot Information LCR* IE for that timeslot, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum DL Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a higher power on any applicable DL DPCH. If no *Maximum DL Power* IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Minimum DL Power* IE, the Node B shall determine the minimum DL power for each timeslot within a DCH type CCTrCH by the + +following rule: If the *Minimum DL Power* IE is included in the *DL Timeslot Information LCR* IE for that timeslot, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum DL Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a lower power on any applicable DL DPCH. If no *Minimum DL Power* IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.] + +[3.84Mcps TDD and 7.68Mcps TDD - The initial power, maximum power, and minimum power for DSCH type CCTrCH shall be determined as follows: + +- If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs. +- If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol. + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial DL power for each timeslot within a DSCH type CCTrCH by the following rule: If both the *CCTrCH Initial DL Transmission Power* IE, included in the *DL CCTrCH Information* IE, and the *DL Time Slot ISCP Info LCR* IE, included in the *RL Information* IE, are included then the Node B shall use that power for the PDSCH and ignore the *Initial DL Transmission Power* IE included in the *RL Information* IE, otherwise the initial DL Power is the *Initial DL Transmission Power* IE included in the *RL Information* IE and if *DL Time Slot ISCP info LCR* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL PDSCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no *Initial DL Transmission Power* IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum DL Power* IE, the Node B shall determine the maximum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power* IE, included in the *DL CCTrCH Information* IE, is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum DL Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a higher power on any applicable PDSCH. If no *Maximum DL Power* IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Minimum DL Power* IE, the Node B shall determine the minimum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE, included in the *DL CCTrCH Information* IE, is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum DL Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a lower power on any applicable PDSCH. If no *Minimum DL Power* IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.] + +[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *DL Time Slot ISCP Info* IE, the Node B shall use the indicated value when deciding the DL TX Power for each timeslot as specified in ref. TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.] + +[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and the RADIO LINK ADDITION REQUEST message includes the *DL Reference Power* IE, the Node B shall activate the power balancing and + +use the *DL Reference Power* IE for the power balancing procedure in the new RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level indicated by the *Initial DL Transmission Power* IE (if received) or the decided DL TX power level on each DL channelisation code of a RL based on power level of existing RLs.] + +[1.28Mcps TDD - Uplink Synchronisation Parameters LCR]: + +[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message contains the *Uplink Synchronisation Parameters LCR* IE, the Node B shall use the indicated values of *Uplink Synchronisation Stepsize* IE and *Uplink Synchronisation Frequency* IE when evaluating the timing of the UL synchronisation.] + +**[1.28Mcps TDD - Power Control GAP:]** + +[1.28Mcps TDD - If the *Power Control GAP* IE is included in the RADIO LINK ADDITION REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].] + +[1.28Mcps TDD - E-UTRAN Inter-RAT measurement:] + +[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Idle Interval Information* IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to TS 25.331 [18].] + +**[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]** + +[1.28Mcps TDD - If the RADIO LINK ADDITON REQUEST message includes the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] + +**[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]** + +[FDD – If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE for a Radio Link not indicated by the *HS-PDSCH RL ID* IE in the *HS-DSCH Serving Cell Change Information* IE the Node B shall if supported preconfigure the indicated cells or Enhanced HS Serving Cell Change according to [49.]:] + +- [FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK ADDITION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *Secondary C-IDs* in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK ADDITION REQUEST message.] +- [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:] + - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell] + - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells] +- [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].] +- [FDD – The Node B shall return these codes in the *Sets of HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message.] + +- [FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell's HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].] +- [FDD – The Node B shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:] + - [FDD – - if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE] + - [FDD – - if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – - if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfigured configuration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell] + - [FDD – - if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell] + - [FDD – - if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE] + - [FDD – - If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall store this information in the preconfigured configuration.] + - [FDD – - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B may store this information in the preconfigured configuration.] + - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD – The Node B shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] + - [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] + +- [FDD –The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD –If the *HS-DSCH Preconfiguration Setup* IE includes the *E-DCH Indicator* IE for a secondary cell, the Node B shall include in the *Additional E-DCH Preconfiguration Information* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK ADDITION RESPONSE message or in the *Successful RL Information Response* IE of the RADIO LINK ADDITION FAILURE message the *E-DCH FDD DL Control Channel Information* IE containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator* IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] +- [FDD –The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.] + +[FDD – If the RADIO LINK ADDITION REQUEST message includes the *Non-Serving Preconfiguration Setup* IE in the *RL Information* IE and:] + +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK ADDITION RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK ADDITION RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK ADDITION RESPONSE message.] + +- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD –If the *F-TPICH Information* IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].] + +#### [1.28 Mcps TDD –Multi-Carrier E-DCH:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information* IE is present in the RADIO LINK ADDITION REQUEST message, then the *Multi-Carrier E-DCH Information* IE defines the new configuration and then:] + +- [1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequencies indicated by the the *Multi-Carrier E-DCH Information LCR* IE.] +- [1.28Mcps TDD - The Node B shall use the corresponding *PRXdes\_base* IE for power control on each uplink frequency according to TS 25.331 [18].] +- [1.28Mcps TDD - If the *SNPL Carrier Group Indicator* IE is present in the *Multi-Carrier E-DCH Information LCR* IE, the Node B shall use the information to determine which SNPL Carrier Group each frequency indicated by the *UARFCN* IE belongs to.] +- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iub transport bearer mode", the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [1.28Mcps TDD – If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "E-DCH UL flow multiplexing mode", the Node B shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iub transport bearer.] +- [1.28Mcps TDD - If the Separate Iub transport bearer mode is used in the new configuration, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] +- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] + +#### [FDD – UL DPCCH2:] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *UL DPCCH2 Information* IE, then:] + +- [FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].] +- [FDD – If the *UL DPCCH2 Information* IE includes the *Extended E-DPCCH Power Offset* IE and if the *E-DCH FDD Information* IE is present in the RADIO LINK ADDITION REQUEST message, the Node B shall use the value to calculate the E-DPCCH gain factor.] + +#### [FDD – Downlink TPC enhancements:] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Downlink TPC enhancements Information* IE, then:] + +- [FDD – The NodeB shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *RL Information* is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCHCell Information RL Add Req* is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +#### General: + +If the RADIO LINK ADDITION REQUEST message includes the *RL Specific DCH Information* IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included]. + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for a DCH, then the Node B shall not establish a transport bearer for the concerned DCH and shall include the *Transport Bearer Not Setup Indicator* IE for every corresponding DCH in the RADIO LINK ADDITION RESPONSE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for a DCH and:] + +- [FDD - if the Node B establishes a transport bearer for the concerned DCH, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH being established.] +- [FDD - if the Node B does not establish a transport bearer for the concerned DCH, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.] + +If the RADIO LINK ADDITION REQUEST message includes the *RL Specific E-DCH Information* IE, the Node B may use the transport layer addresses and the binding identifiers received from the CRNC when establishing transport bearers for the MAC-d flows of the E-DCHs. + +The Node B shall start reception on the new RL(s) after the RLs are successfully established. + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Initial DL DPCH Timing Adjustment Allowed* IE, then the Node B may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the Node B shall include, for the concerned Radio Link(s), the *Initial DL DPCH Timing Adjustment* IE in the *Radio Link Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Synchronisation Indicator* IE, set to "Timing Maintained Synchronisation", the Node B shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10]. The Node B shall select the TPC pattern as if "first RLS indicator" is set to "first RLS" according to subclause 5.1.2.2.1.2 in TS 25.214 [10].] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *F-DPCH Slot Format* IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *F-TPICH Information* IE in the *RL Information* IE, the Node B shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] + +#### [FDD - Radio Link Set Handling]: + +[FDD - For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the *RL Set ID* IE included in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Sets shall not be common.] + +[FDD - For all RLs having a common generation of the TPC commands in the DL with another new or existing RL, the Node B shall assign the *RL Set ID* IE included in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.] + +[FDD - After addition of the new RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the previously existing and newly established RL Set(s), use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N\_INSYNC\_IND, that are configured in the cells supporting the radio links of the RL Set.] + +[FDD - For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the *E-DCH RL Set ID* IE in the RADIO LINK ADDITION RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] + +#### **[FDD - Serving HS-DSCH Radio Link Change]:** + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Serving Cell Change Information* IE, then *HS-PDSCH RL ID* IE indicates the new Serving HS-DSCH Radio Link:] + +- [FDD - In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link.] +- [FDD - The Node B may include the *HARQ Memory Partitioning* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- [FDD - If the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +#### **[FDD - HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change]:** + +[FDD - If the *HS-DSCH Information* IE is present in the *HS-DSCH Serving Cell Change Information* IE, then:] + +- [FDD - The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.] +- [FDD - the *HS-DSCH Information* IE defines the new HS-DSCH configuration in the Node B to be used on the new HS-DSCH Radio Link.] +- [FDD - The Node B shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message. The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE or the *MIMO with four transmit antennas Activation Indicator* IE, or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.] + +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.] +- [FDD – If the RADIO LINK ADDITION REQUEST message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information* IE , then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] +- [FDD - The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK ADDITION REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Measurement Power Offset* IE in the *HS-DSCH Information* IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).] +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO + +and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the *RADIO LINK ADDITION RESPONSE* message.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the *RADIO LINK ADDITION RESPONSE* message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] +- [FDD - If the *RADIO LINK ADDITION REQUEST* message includes the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *RADIO LINK ADDITION RESPONSE* message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may use:] + - r) - [FDD - a different HS-SCCH in consecutive TTIs for this UE.] + - s) - [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the Node B may use the supported HSDPA functions for this UE.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the *RADIO LINK ADDITION RESPONSE* message.] +- [FDD - If the *RADIO LINK ADDITION REQUEST* message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].] +- [FDD - If the *RADIO LINK ADDITION REQUEST* message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall, if supported, consider the data of the HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change Information* IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the *RADIO LINK ADDITION RESPONSE* message.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the *HS-DSCH Serving Cell Change Information Response* IE in the *RADIO LINK ADDITION RESPONSE* message.] + +- [FDD - If the *CQI Feedback Cycle2 k* IE and the *CQI Cycle Switch Timer* IE is included in *HS-DSCH FDD Information* IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.] +- [FDD - If the *Serving Cell Change CFN* IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.] +- [FDD - If the *Serving Cell Change CFN* IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.] +- [FDD - If the *Serving Cell Change CFN* IE is not included into the RADIO LINK ADDITION REQUEST message, then the Node B shall include the *Transport Layer Address* IE and the *Binding ID* IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *HS-DSCH Information* IE is present in the *HS-DSCH Serving Cell Change Information* IE, then the Node B shall include the *Transport Layer Address* IE and the *Binding ID* IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the Node B needs a bearer re-arrangement, then the Node B may include the *Transport Layer Address* IE and the *Binding ID* IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the *HS-DSCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If a reset of the MAC-hs is not required the Node B shall include the *MAC-hs Reset Indicator* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the requested Serving HS-DSCH Radio Link Change was successful or unsuccessful, the Node B shall indicate this in the *HS-DSCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *HS-DSCH Serving Cell Change Information* IE includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:] + - [FDD - The Node B shall configure the new Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].] + - [FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the *HS-DSCH Serving Cell Change Information Response* IE.] + - [FDD - If at least one of *HS-PDSCH Second Code Support* IE is set to "True", then the Node B shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD – If the *HS-DSCH Serving Cell Change Information* IE includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:] + - [FDD – The Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].] + - [FDD – If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].] + - [FDD – If *UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].] + - [FDD – If *Inactivity Threshold for UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned + +Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].] + +**[FDD – Secondary Serving HS-DSCH Radio Link Change]:** + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Additional HS Cell Information RL Addition* IE, then *HS-PDSCH RL ID* IE indicates the new secondary serving HS-DSCH Radio Link:] + +- [FDD - In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Secondary Serving HS-PDSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +**[FDD - Secondary Serving HS-DSCH Setup on a New Radio Link at Secondary Serving HS-DSCH Radio Link Change:]** + +- [FDD - The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE.] +- [FDD - The *HS-DSCH FDD Secondary Serving Information* IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell* + +*Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If Sixtyfour QAM will not be used for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Addition* IE in the RADIO LINK ADDITION REQUEST message the Node B shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.] +- [FDD - If the *Serving Cell Change CFN* IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.] +- [FDD - If the *Serving Cell Change CFN* IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.] +- [FDD - If the requested Secondary Serving HS-DSCH Radio Link Change was successful or unsuccessful, the Node B shall indicate this in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - Node B may include the *Precoder weight set restriction* IE in *HS-DSCH FDD Secondary Serving Information Response* IE in the *HS-DSCH Secondary Serving Cell Change Information Response* IE in the *Additional HS Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +#### **[FDD - Additional Serving E-DCH Radio Link Change:]** + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Additional E-DCH Cell Information Addition* IE in the *Additional E-DCH Cell Information RL Add Req* IE and *HS-PDSCH RL ID* IE the *Additional HS Cell Information RL Addition* IE, the *HS-PDSCH RL ID* IE indicates the new Additional Serving E-DCH Radio Link:] + +- [FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] + +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - The Node B may include in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION RESPONSE message the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2 IE*] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional E-DCH FDD Information Response IE* in the RADIO LINK ADDITION RESPONSE message.] +- [FDD – The Node B may include the *E-RGCH/E-HICH Channelisation Code IE* and/or the *E-HICH Signature Sequence IE* and/or the *E-RGCH Signature Sequence IE* or may alternatively include the *E-RGCH Release Indicator IE* in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH FDD Information Response IE*.] +- [FDD - If the *Serving Cell Change CFN IE* is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC, or earlier. In this case, in the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.] +- [FDD - If the *Serving Cell Change CFN IE* is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.] +- [FDD - If the addition of the requested Additional Serving E-DCH Radio Link was successful but the Additional Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the *Additional E-DCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION RESPONSE message.] + +#### [FDD - Multiflow Setup]: + +[FDD - If the *Multiflow Information IE* is present in *HS-DSCH FDD Information IE* in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested Multiflow operation and then:] + +- [FDD – Use *Total number of HS-DSCH cells IE* to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] +- [FDD – Use *Role IE* to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – Use *MIMO IE* to decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If *Timing IE* is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B IE* is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors IE* is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.] + +#### [FDD - E-DCH]: + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *E-DCH RL Indication IE*, set to "E-DCH", in the *RL Information IE*, then for every such RL:] + +- [FDD - The Node B shall setup the E-DCH resources as configured in the Node B Communication Context.] +- [FDD - The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH" in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] + +#### [FDD - Serving E-DCH Radio Link Change:] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Serving E-DCH RL* IE, then *Serving E-DCH RL* IE indicates the new Serving E-DCH Radio Link:] + +- [FDD - If the new Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the new serving E-DCH RL.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK ADDITION RESPONSE message for the new serving E-DCH RL.] +- [FDD - The Node B may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the *E-DCH FDD DL Control Channel Information* IE in *RL Information Response* IE.] +- [FDD - If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.] +- [FDD - If the *Serving Cell Change CFN* IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving E-DCH Radio Link.] +- [FDD - If the addition of the requested Serving E-DCH Radio Link was successful but the Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + +#### [FDD - E-DPCH Handling:] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes an *E-DPCH Information* IE it defines the new E-DPCH configuration in the Node B to be used on the new E-DCH Radio Link and, the Node B shall use the new parameters for the related resource allocation operations.] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the Node B shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10].] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes an *E-DPCH Information* IE, which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the Node B shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].] + +#### [FDD - E-DCH Setup on a new Radio Link:] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK ADDITION REQUEST message:] + +- [FDD - the *E-DCH FDD Information* IE defines the new E-DCH FDD configuration in the Node B to be used on the new E-DCH Radio Link.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel information* IE in the *E-DCH FDD Information* IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE, then the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]) +- [FDD - If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *E-DCH Serving Cell Change Information Response* IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the serving E-DCH RL.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new configuration and include the new configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK ADDITION RESPONSE message for the serving E-DCH RL.] + +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Reference Power Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *UPH Filtering Measurement Forwarding Request* IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] + - [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to (TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to (TS 25.321 [32].] +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for an E-DCH MAC-d flow, then the Node B + +shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.] + +- [FDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for an E-DCH MAC-d flow and:] + - [FDD - if the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.] + - [FDD - if the Node B does not establish a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.] + +#### [FDD - Additional E-DCH Setup:] + +[FDD - If the *Additional E-DCH Cell Information RL Add Req* IE is present in the RADIO LINK ADDITION REQUEST message and the choice of *Setup Or Addition Of E-DCH On Secondary UL Frequency* is "Setup", then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:] + +- [FDD - If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the additional E-DCH shall be setup] + - [FDD - The Node B shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the Additional E-DCH shall be setup.] + - [FDD - The Node B shall setup the Additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE] +- [FDD - The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency. The Node B shall, if supported, use the *Dual Cell E-DCH Operation Enhancements Information* IE for the Secondary uplink frequency if it is included in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPCH Gain Factor* IE are present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Secondary UL Frequency Activation State* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] +- [FDD - If the *F-DPCH Slot Format* IE is present in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Primary CPICH Usage For Channel Estimation* IE, the *Secondary CPICH Information* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Processing Overload Level* IE, the *E-DCH Minimum Set E-TFCI* IE, the *Implicit Grant handling* IE, the *Minimum TEBS threshold* IE and/or the *DTX Information2* IE are present in the *Additional E-DCH FDD Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] + +- [FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK ADDITION REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - If the Additional Serving E-DCH Radio Link is configured in the Node B, then:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] + - [FDD - If the *Serving Cell Change CFN* IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. If the *Serving Cell Change CFN* IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.] + +#### [FDD – Additional E-DCH RL Addition:] + +[FDD - If the *Additional E-DCH Cell Information RL Add Req* IE is present in the RADIO LINK ADDITION REQUEST message and the choice of *Setup Or Addition Of E-DCH On Secondary UL Frequency* is "Addition", then the *Additional E-DCH Cell Information Addition* IE defines the new configuration and then:] + +- [FDD - The Node B shall setup the requested E-DCH resources as requested, or as configured in the Node B Communication Context, on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Add* IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - if the *Multicell E-DCH Information* IE is included and contains the *Minimum Reduced E-DPDCH Gain Factor* IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.] +- [FDD - If the *Additional E-DCH FDD Information* IE is included and contains the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Minimum Set E-TFCI* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Processing Overload Level* IE, the *Implicit Grant handling* IE, the *Minimum TEBS threshold* IE and/or the *DTX Information* IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.] +- [FDD - If the Initial DL Transmission Power IE, the Maximum DL Power IE, the Minimum DL Power IE and/or the F-DPCH Slot Format IE are present in the *Additional E-DCH RL Specific Information To Add* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *DL Reference Power* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Add* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the *E-DCH Additional RL Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level indicated by the Initial DL Transmission Power IE (if received) in the *Additional E-DCH RL Specific Information To Add* IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DDCH RLs.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH* + +*Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Add* IE in the RADIO LINK ADDITION RESPONSE message.] + +**[FDD – E-DCH decoupling operation]** + +[FDD – If the *E-DCH Decoupling Indication* IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall if supported use this indication for the E-DCH decoupling operation.] + +**[FDD – Radio Links without DPCH/F-DPCH operation]** + +[FDD – If the *Radio Links without DPCH/F-DPCH Indication* IE is present in the RADIO LINK ADDITION REQUEST message:] + +- [FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.] + +**[TDD - HS-DSCH Setup]:** + +[TDD - If the *HS-DSCH Information* IE is present in the RADIO LINK ADDITION REQUEST message, then:] + +- [TDD - The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.] +- [TDD - The Node B shall include the *HARQ Memory Partitioning* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).] +- [TDD - The Node B shall include in the RADIO LINK ADDITION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *HS-DSCH Information* IE for an HS-DSCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].] +- [TDD - The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the + +peer of *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE* to the values of the corresponding peer received in *RADIO LINK ADDITION REQUEST* in the *HS-DSCH MAC-d Flows Information IE* in the *HS-DSCH Information IE* for a Priority Queue including *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE*.] + +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR IE*] in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [1.28Mcps TDD - If the *TSN-Length IE* is included in the *HS-DSCH TDD Information IE*, then the IE is used to indicate the TSN bits applied to the MAC-hs PDU frame.] +- [1.28Mcps TDD - If the *RADIO LINK ADDITION REQUEST* message includes the *Number of Supported Carriers IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B shall use this information to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - For a multi-frequency cell, if the *RADIO LINK ADDITION REQUEST* message includes the *Multi-carrier HS-DSCH Physical Layer Category IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B shall use this information together with the *HS-DSCH Physical Layer Category IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE* to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - If the *RADIO LINK ADDITION REQUEST* message includes the *UE TS0 Capability LCR IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE*, the Node B may use this information in HSDPA resources allocation for the UE.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple carriers and include the *HS-SCCH Specific Information Response LCR per UARFCN IE* in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall include the *HARQ Memory Partitioning per UARFCN IE* in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [1.28Mcps TDD - If the Node B allows UE to apply HSDPA resources distributed over multiple carriers, the Node B may indicate the number of carriers actually used by the UE and include the *Multi-Carrier number IE* in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the *UsedFrequency IE* in the *HS-SCCH Specific Information Response LCR IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the *UARFCN IE* in the *HS-SCCH Specific Information Response LCR per UARFCN IE* in the *RADIO LINK ADDITION RESPONSE* message.] + +[1.28 Mcps TDD - If the *MIMO Activation Indicator IE* is included in the *HS-DSCH TDD Information IE*, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream IE* in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] + +#### **[TDD - Intra-Node B Serving HS-DSCH Radio Link Change]:** + +[TDD - If the *RADIO LINK ADDITION REQUEST* message includes the *HS-PDSCH RL ID IE*, this indicates the new Serving HS-DSCH Radio Link]: + +- [TDD - The Node B may include the *HARQ Memory Partitioning IE* in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response IE*] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR IE*] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps IE*] in the *HS-DSCH TDD Information Response IE* in the *RADIO LINK ADDITION RESPONSE* message.] + +**[TDD - E-DCH]:** + +[TDD - If the [3.84Mcps TDD - *E-DCH Information* IE][1.28Mcps TDD - *E-DCH Information* 1.28Mcps IE] +[7.68Mcps TDD - *E-DCH Information* 7.68Mcps IE] is present in the RADIO LINK ADDITION REQUEST message:] + +- [TDD - The Node B shall setup the requested E-DCH resources on the Radio Link indicated by the *E-DCH Serving RL* IE.] +- [TDD - If the *TNL QoS* IE is included in the *E-DCH MAC-d Flows Information TDD* IE for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IE in the *E-DCH MAC-d Flows Information TDD* IE for an E-DCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flows Information TDD* IE, the Node B shall use this information for the related resource allocation operation.] +- [TDD - If in the RADIO LINK ADDITION REQUEST message the *E-DCH Grant Type* IE in the *E-DCH MAC-d Flows Information TDD* IE is set to "Non-scheduled" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants are configured for that E-DCH MAC-d flow and shall use the information within the [3.84Mcps TDD - *E-DCH Non-scheduled Grant Information TDD* IE] [1.28Mcps TDD - *E-DCH Non-scheduled Grant Information LCR TDD* IE] [7.68Mcps TDD - *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE], if included, for the related resource allocation operation.] +- [TDD - If in the RADIO LINK ADDITION REQUEST message the *E-DCH Grant Type* IE in the *E-DCH MAC-d Flows Information TDD* IE is set to "Scheduled" the Node B shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related queue.] +- [1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows Information TDD* IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [3.84Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH TDD Maximum Bitrate* IE in the *E-DCH TDD Information* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE in the *E-DCH TDD Information LCR* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE in the *E-DCH TDD Information 7.68Mcps* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Processing Overload Level* IE in the [3.84Mcps TDD - *E-DCH TDD Information* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE], then if the Node B could not decode the E-PUCH for + +the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level IE*, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] + +- [TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Power Offset for Scheduling Info IE* in the [3.84Mcps TDD - *E-DCH TDD Information IE*] [1.28Mcps TDD - *E-DCH TDD Information LCR IE*] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps IE*], then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Maximum Number of Retransmission for Scheduling Info LCR IE* and the *E-DCH Retransmission timer for Scheduling Info LCR IE* in the *E-DCH TDD Information LCR IE*, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] +- [TDD - The Node B shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the *E-DCH Information Response IE* in the RADIO LINK ADDITION RESPONSE message.] +- [1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Multi-Carrier E-DCH Physical Layer Category LCR IE* in the *E-DCH TDD Information LCR IE*, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] +- [1.28Mcps TDD - If the *UE TS0 Capability LCR IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE* is not present and if the RADIO LINK ADDITION REQUEST message includes the *UE TS0 Capability LCR IE* in the *E-DCH TDD Information LCR IE*, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] + +#### **[TDD - Intra-Node B Serving E-DCH Radio Link Change]:** + +[TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL IE*, this indicates the new Serving E-DCH Radio Link]: + +- [TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - E-HICH parameters] corresponding to the E-DCH and include the E-AGCH Specific Information Response TDD IE, [1.28Mcps TDD - E-HICH Specific Information Response 1.28Mcps TDD IE] in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.] + +#### **[1.28 Mcps TDD - Continuous Packet Connectivity Handling]:** + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *Continuous Packet Connectivity DRX Information LCR IE*, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR IE* in the RADIO LINK ADDITION RESPONSE message.] + +[1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext IE* is included in the *Continuous Packet Connectivity DRX Information LCR IE*, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the *Enabling Delay Ext IE* is included in the *Continuous Packet Connectivity DRX Information LCR IE*, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR IE*, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID IE* for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR IE* in the RADIO LINK ADDITION RESPONSE message.] +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator IE* is included in the *HS-DSCH Semi-Persistent scheduling Information LCR IE*, then the Node B shall include *Allcoated HS-PDSCH Semi-persistent resource IE* in the RADIO LINK ADDITION RESPONSE message.] + +- [1.28 Mcps TDD - The Node B shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.] +- [1.28 Mcps TDD - The Node B shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK SETUP RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allcoated E-DCH Semi-persistent resource* IE in the RADIO LINK ADDITON RESPONSE message.] + +#### **[1.28 Mcps TDD - MU-MIMO Handling:]** + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the *MU-MIMO Information* IE, then:] + +- [1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the *MU-MIMO indicator* IE and shall include the *MU-MIMO Information Response* IE in the RADIO LINK ADDITION RESPONSE message.] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information* IE is included in the *MU-MIMO Information* IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information request* IE is included in the *MU-MIMO Information* IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK ADDITION RESPONSE message, else the Node B shall not include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK ADDITON RESPONSE message.] + +#### **[1.28 Mcps TDD – Non-rectangular resource operation:]** + +[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message contains the *UE support of non-rectangular resource allocation* IE, the Node B shall, if supported, use this information to determine whether includes the *Non-rectangular resource allocation indicator* IE and the *Non-rectangular resource timeslot set* IE or not.] + +#### **Response Message:** + +If all requested RLs are successfully added, the Node B shall respond with a RADIO LINK ADDITION RESPONSE message. + +After sending the RADIO LINK ADDITION RESPONSE message, the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface. + +For each RL for which the *Delayed Activation* IE is not included in the RADIO LINK ADDITION REQUEST message, the Node B shall: + +- [FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].] +- [TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].] + +For each RL for which the *Delayed Activation* IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall: + +- if the *Delayed Activation* IE indicates "Separate Indication": + - not start any DL transmission for the concerned RL on the Uu interface; +- if the *Delayed Activation* IE indicates "CFN": + +- [FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the *Activation CFN IE*.] +- [TDD - start transmission on the new RL at the CFN indicated in the *Activation CFN IE* as specified in TS 25.427 [16].] + +### 8.3.1.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Radio Link Addition procedure. A CRNC sends a RADIO LINK ADDITION REQUEST to a Node B, and the Node B responds with a RADIO LINK ADDITION FAILURE.](864e6cb4a0166a5b21a5d19f694e1606_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: RADIO LINK ADDITION REQUEST + CRNC->>Node B: RADIO LINK ADDITION REQUEST + Note right of Node B: RADIO LINK ADDITION FAILURE + Node B-->>CRNC: RADIO LINK ADDITION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Radio Link Addition procedure. A CRNC sends a RADIO LINK ADDITION REQUEST to a Node B, and the Node B responds with a RADIO LINK ADDITION FAILURE. + +**Figure 29: Radio Link Addition procedure: Unsuccessful Operation** + +If the establishment of at least one radio link is unsuccessful, the Node B shall respond with a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the *Cause IE*. + +[FDD - If some RL(s) were established successfully, the Node B shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as in the RADIO LINK ADDITION RESPONSE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST contains a *C-ID IE* indicating that a Radio Link must be established on a Cell where DPC Mode change is not supported and DPC Mode can be changed for the relevant Node B Communication Context, the Node B shall consider the procedure as failed for the concerned Radio Link and shall respond with a RADIO LINK ADDITION FAILURE with the appropriate cause value ("DPC Mode change not supported").] + +[FDD - If the requested Serving HS-DSCH Radio Link Change was successful, or if the addition of the requested serving HS-DSCH Radio Link was successful or existed already but the Serving HS-DSCH Radio Link change was unsuccessful, the Node B shall indicate this in the *HS-DSCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the requested secondary serving HS-DSCH Radio Link Change was successful, or if the addition of the requested secondary serving HS-DSCH Radio Link was successful or existed already but the secondary serving HS-DSCH Radio Link change was unsuccessful, the Node B shall indicate this in the *HS-DSCH Secondary Serving Cell Change Information Response IE* in the *Additional HS Cell Change Information Response IE* in the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the requested Serving E-DCH Radio Link Change was successful, or if the addition of the requested serving E-DCH Radio Link was successful or existed already but the Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the *E-DCH Serving Cell Change Information Response IE* in the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the requested additional serving E-DCH Radio Link Change was successful, or if the addition of the requested additional serving E-DCH Radio Link was successful or existed already but the additional serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the *Additional E-DCH Serving Cell Change Information Response IE* in the *Additional E-DCH Cell Information Response RL Add IE* in the RADIO LINK ADDITION FAILURE message.] + +Typical cause values are as follows: + +#### Radio Network Layer Cause + +- Combining not supported +- Combining Resources not available +- Requested Tx Diversity Mode not supported + +- UL SF not supported +- DL SF not supported +- Reconfiguration CFN not elapsed +- CM not supported +- [FDD - DPC Mode change not supported] +- Delayed Activation not supported +- [FDD - Continuous Packet Connectivity DTX-DRX operation not available] +- [FDD - Continuous Packet Connectivity UE DTX Cycle not available] +- [FDD - MIMO not available] +- [FDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - Multi Cell operation not available.] +- [1.28Meps TDD- MIMO not available] +- [1.28Meps TDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - TX diversity for MIMO UE on DL Control Channels not available] +- [FDD – Single Stream MIMO not available] +- [FDD - Multi Cell operation with MIMO not available.] +- [FDD - Multi Cell operation with Single Stream MIMO not available.] +- [FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available] +- [FDD - Multi Cell E-DCH operation not available] +- [FDD – Frequency Specific Compressed mode operation not available] +- [FDD - UL CLTD operation not available] +- [FDD - MIMO with four transmit antennas not available] +- [FDD - Dual Stream MIMO with four transmit antennas not available] +- [FDD – Multiflow operation not available] +- [FDD - SixtyfourQAM UL operation not available] +- [FDD – UL MIMO operation not available] +- [FDD – UL MIMO and SixteenQAM operation not available] +- [FDD – UL MIMO and SixtyfourQAM operation not available] +- [FDD – E-DCH decoupling operation not available] +- [FDD – Radio Links without DPCH/F-DPCH operation not available] +- [FDD – UL DPCCH2 operation not available] +- [FDD – Downlink TPC enhancements operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with different TTI operation not available] + +## Transport Layer Cause + +- Transport Resources Unavailable + +### Miscellaneous Cause + +- O&M Intervention +- Control processing overload +- HW failure + +### 8.3.1.4 Abnormal conditions + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Compressed Mode Deactivation Flag* IE with the value "Deactivate" when compressed mode is active for the existing RL(s), and at least one of the new RL is added in a cell that has the same UARFCN (both UL and DL) of at least one cell with an already existing RL and frequency specific compressed mode is not supported, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM settings".] + +[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and if the *DL Reference Power* IEs are included in the *RL Information* IE but the *DL Reference Power* IE is not present for each RL in the *RL Information* IE, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *DL Reference Power* IEs in the *RL Information* IE but the power balancing is not active in the existing RL(s) or the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s), the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Power Balancing status not compatible".] + +If the RADIO LINK ADDITION REQUEST message includes the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE or *RL Specific E-DCH Information* IE included in the *RL Information* IE for a specific RL [FDD - and the E-DCH RL is already configured in the Node B] and the *Diversity Control Field* IE is set to "Must", the Node B shall regard the Radio Link Addition procedure as failed and respond with the RADIO LINK ADDITION FAILURE message. + +If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to "May", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. + +If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE in the *RL Information* IE for a specific RL and the *Diversity Control Field* IE is set to "Must Not", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. + +If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE in [FDD - the *RL Specific E-DCH Information* IE in the *RL Information* IE for the first E-DCH RL][TDD – the *E-DCH MAC-d Flows Information TDD* IE], the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK SETUP FAILURE message. + +If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for an HS-DSCH MAC-d Flow in the *HS-DSCH MAC-d Flows Information* IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. + +If the RADIO LINK ADDITION REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK ADDITION REQUEST message does not include the *UARFCN* IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.] + +[1.28Mcps TDD - For a single frequency cell, if the RADIO LINK ADDITION REQUEST message includes the *UARFCN* IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to use DPCH in downlink and if a transmission gap pattern sequence is active with an SF/2 downlink compressed mode method and the RADIO LINK ADDITION REQUEST message does not contain the transmission gap pattern sequence code information for any new radio link, the Node B shall reject the Radio Link Addition procedure using the RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM Settings".] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-DSCH Serving Cell Change Information* IE but not the *HS-DSCH FDD Information* IE and the Node B Communication Context is not configured for HS-DSCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Serving E-DCH RL* IE but the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Serving Cell Change CFN* IE but neither the *Serving E-DCH RL* IE nor *HS-DSCH Serving Cell Change Information* IE is included into, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK ADDITION REQUEST message, but the *E-DPCH Information* IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH RL Indication* IE set to "E-DCH", but no *E-DCH FDD Information* IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH FDD Information* IE but no *E-DCH RL Indication* IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message includes the *HS-PDSCH RL-ID* IE not equal to the *RL ID* IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message includes the *E-DCH Serving RL* IE not equal to the *RL ID* IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message contains the *HS-DSCH Information* IE and if the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +If the RADIO LINK ADDITION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information*] and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information*] has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +If the RADIO LINK ADDITION REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information*] and the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information*] has the value "Flexible MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +[FDD - If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE, and + +there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for HS-DSCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[TDD - If the RADIO LINK ADDITION REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for E-DCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +If the RADIO LINK ADDITION REQUEST message does not contain the *E-DCH Decoupling Indication* IE but contains the *HS-PDSCH RL ID* IE [FDD - in the *HS-DSCH Serving Cell Change Information* IE] and/or *Serving E-DCH RL* IE, and if both HS-DSCH and E-DCH are configured in the Node B but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *HS-DSCH Serving Cell Change Information* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as "HS-DSCH not configured" then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Transport Bearer Not Requested Indicator* IE for a DCH but the DCH is configured to be included as a part of the downlink CCTrCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *MIMO Activation Indicator* IE, *Sixtyfour QAM Usage Allowed Indicator* IE set to "Allowed", the *Additional HS Cell Information RL Addition* IE, the *Single Stream MIMO Activation Indicator* IE, the *MIMO with four transmit antennas Activation Indicator* IE and/or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE but does not contain the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD – If the RADIO LINK ADDITION REQUEST message contains the *Serving E-DCH RL ID* IE but contains the *Transport Bearer Not Requested Indicator* IE or there is at least one E-DCH MAC-d flow which transport bearer was not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH for a specific RL and the specific RL is combined with the existing RL which the transport bearer is established for the DCH in Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition* IE and if the HS-DSCH is not configured in the Node B Communication Context and the *HS-DSCH Information* IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +If the RADIO LINK ADDITION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information* IE] set to "Flexible RLC PDU Size", *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information* IE] has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +If the RADIO LINK ADDITION REQUEST message does not include the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information* IE] and the *DL RLC PDU Size Format* IE in the *HS-DSCH Information* IE [FDD - in the *HS-DSCH Serving Cell Change Information* IE] has the value "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message. + +[FDD - If the RADIO LINK ADDITION REQUEST message contains a *MIMO Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE in the *HS-DSCH Serving Cell Change* + +*Information IE* or in the *HS-DSCH FDD Secondary Serving Information IE* in the *Additional HS Cell Information RL Addition IE*, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Diversity Mode IE* in the *HS-DSCH FDD Secondary Serving Information IE* in the *Additional HS Cell Information RL Addition IE* and the secondary serving HS-DSCH is already configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the secondary serving HS-DSCH is not configured in the Node B Communication Context and if the RADIO LINK ADDITION REQUEST message contains in the *HS-DSCH FDD Secondary Serving Information IE* in the *Additional HS Cell Information RL Addition IE* the *Diversity Mode IE* not set to "None" but not the *Transmit Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode IE* not set to "None", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Add Req IE* and if the *E-DPCH Information IE* is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Add Req IE* and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended IE* in the *E-DCH MAC-d Flows Information IE* in the *E-DCH FDD Information IE* is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional E-DCH Cell Information RL Add Req IE* and the *C-ID IE* is not included in the *Additional E-DCH RL Specific Information To Setup IE* in the *Additional E-DCH FDD Setup Information IE* in the *Additional E-DCH Cell Information Setup IE*, and the Radio Link indicated by the *E-DCH Additional RL ID IE* is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition IE* and the new configuration contains more than one secondary serving HS-DSCH RL and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the *Ordinal Number Of Frequency IE* in the *HS-DSCH FDD Secondary Serving Information IE*, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Additional HS Cell Information RL Addition IE* and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *Affected HS-DSCH serving cell List IE* in the *Active Pattern Sequence Information IE* and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM settings".] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *UL CLTD Information IE* but does not contain the *F-TPICH Information IE*, or if it contains *HS-DSCH Preconfiguration Setup IE* with *UL CLTD Information IE* but without *F-TPICH Information IE*, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains the *UL MIMO Information IE* in *E-DCH FDD Information IE* but does not contain the *UL CLTD Information IE*, or if it contains *HS-DSCH Preconfiguration Setup IE* with *UL MIMO Information IE* but without *UL CLTD Information IE*, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the RADIO LINK ADDITION REQUEST message contains more than one of a *MIMO Activation Indicator IE*, a *MIMO with four transmit antennas Activation Indicator IE*, a *Dual Stream MIMO with four transmit antennas Activation Indicator IE* in *HS-DSCH Preconfiguration Setup IE* or in the *Secondary Cells IE* in the *HS-DSCH Preconfiguration Setup IE*, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup but the *Dual Cell E-DCH Operation Enhancements Information* IE is not included in the RADIO LINK ADDITION REQUEST message, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup and if the *Continuous Packet Connectivity DTX-DRX Information* IE in the *HS-DSCH Serving Cell Change Information* IE is included in the RADIO LINK ADDITION REQUEST message, but the *DTX Information* IE does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup and if the DTX related Information is not signalled but the currently used value is not from the set of values defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] + +## 8.3.2 Synchronised Radio Link Reconfiguration Preparation + +### 8.3.2.1 General + +The Synchronised Radio Link Reconfiguration Preparation procedure is used to prepare a new configuration of Radio Link(s) related to one Node B Communication Context. + +The Synchronised Radio Link Reconfiguration Preparation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. + +### 8.3.2.2 Successful Operation + +![Sequence diagram showing the Synchronised Radio Link Reconfiguration Preparation procedure between CRNC and Node B. The CRNC sends a RADIO LINK RECONFIGURATION PREPARE message to Node B, and Node B responds with a RADIO LINK RECONFIGURATION READY message.](b9f3b61f140ea64afb9205312d52eb0e_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: RADIO LINK RECONFIGURATION PREPARE + CRNC->>Node B: RADIO LINK RECONFIGURATION PREPARE + Note left of Node B: RADIO LINK RECONFIGURATION READY + Node B-->>CRNC: RADIO LINK RECONFIGURATION READY + +``` + +Sequence diagram showing the Synchronised Radio Link Reconfiguration Preparation procedure between CRNC and Node B. The CRNC sends a RADIO LINK RECONFIGURATION PREPARE message to Node B, and Node B responds with a RADIO LINK RECONFIGURATION READY message. + +**Figure 30: Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation** + +The Synchronised Radio Link Reconfiguration Preparation procedure is initiated by the CRNC by sending the RADIO LINK RECONFIGURATION PREPARE message to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context. + +Upon reception, the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. + +The Node B shall prioritise resource allocation for the RL(s) to be modified according to Annex A. + +If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. + +If the *Improved Synchronized RRC Indicator* IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may use this instruction to handle the improved synchronized RRC procedures. + +#### DCH Modification: + +If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs To Modify* IE then the Node B shall treat them each as follows: + +- If the *DCHs To Modify* IE includes the *Frame Handling Priority* IE, the Node B should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the Node B once the new configuration has been activated. + +- If the *DCHs To Modify* IE includes the *Transport Format Set* IE for the UL of a DCH, the Node B shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration. +- If the *DCHs To Modify* IE includes the *TNL QoS* IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The *TNL QoS* IE may be used to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs. +- If the *DCHs To Modify* IE includes the *Transport Format Set* IE for the DL of a DCH, the Node B shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration. +- If the *DCHs To Modify* IE includes the *Allocation/Retention Priority* IE for a DCH, the Node B shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A. +- If the *DCHs To Modify* IE includes multiple *DCH Specific Info* IEs, the Node B shall treat the DCHs in the *DCHs to Modify* IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. +- [FDD - If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to "Uplink DCH only", the Node B shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.] +- [FDD - If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to "Downlink DCH only", the Node B shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.] +- If the *DCHs To Modify* IE includes the *UL FP Mode* IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- If the *DCHs To Modify* IE includes the *ToAWS* IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- If the *DCHs To Modify* IE includes the *ToAWE* IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- [TDD - If the *DCHs To Modify* IE includes the *CCTrCH ID* IE for the DL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Downlink of this DCH in the new configuration.] +- [TDD - If the *DCHs To Modify* IE includes the *CCTrCH ID* IE for the UL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.] + +#### DCH Addition: + +If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs To Add* IEs then the Node B shall treat them each as follows: + +- If the *DCHs To Add* IE includes multiple *DCH Specific Info* IEs, the Node B shall treat the DCHs in the *DCHs To Add* IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. +- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Uplink DCH only", the Node B shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. +- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Downlink DCH only", the Node B shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. +- [FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the *QE-Selector* IE set to "selected", the Transport channel BER from that DCH shall be the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS + +25.427 [16]. If the *QE-Selector* IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].] + +- For a set of co-ordinated DCHs, the Transport channel BER from the DCH with the *QE-Selector* IE set to "selected" shall be used for the QE in the UL data frames, ref. TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If all DCHs have the *QE-Selector* IE set to "non-selected", the Physical channel BER shall be used for the QE, ref. TS 25.427 [16].] +- The Node B should store the *Frame Handling Priority* IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated. +- If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The *TNL QoS* IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs. +- The Node B shall use the included *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- The Node B shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- The Node B shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- [TDD - The Node B shall apply the *CCTrCH ID* IE (for the DL) in the Downlink of this DCH in the new configuration.] +- [TDD - The Node B shall apply the *CCTrCH ID* IE (for the UL) in the Uplink of this DCH in the new configuration.] + +#### **DCH Deletion:** + +If the RADIO LINK RECONFIGURATION PREPARE message includes any *DCHs To Delete* IE, the Node B shall not include the referenced DCHs in the new configuration. + +If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the Node B shall not include this set of co-ordinated DCHs in the new configuration. + +#### **[FDD – DCH Enhancements]:** + +[FDD - If the *DCH Enhancements Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Setup", then the Node B shall store the corresponding information in the concerned Node B communication context, setup the requested DCH Enhancements operation [52], and:] + +- [FDD – Use the *PO-SRB* IE to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].] +- [FDD – Use the *DL\_FET Mode* IE to configure the DL FET mode [8, 52].] +- [FDD – Use the information contained in the *DL DCH Concatenation* IE, if present, to identify the Transport Channels that shall be concatenated according to TS 25.212 [8].] + +[FDD - If the *DCH Enhancements Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Configuration Change", then the Node B shall modify the corresponding information in the concerned Node B communication context, and: ] + +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *PO-SRB* IE, then the Node B shall use this value to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].] +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *DL\_FET Mode* IE, then the Node B shall configure the DL FET mode accordingly [8, 52].] +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DCH Concatenation* IE, then the Node B shall use the respective information to identify the Transport Channels to be concatenated according to TS 25.212 [8].] + +[FDD - If the *DCH Enhancements Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Removal", then all DCH Enhancements Information shall be removed from the concerned Node B communications context.] + +#### Physical Channel Modification: + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *UL DPCH Information* IE, then the Node B shall apply the parameters to the new configuration as follows:] + +- [FDD - If the *UL DPCH Information* IE includes the *Uplink Scrambling Code* IE, the Node B shall apply this Uplink Scrambling Code to the new configuration.] +- [FDD - If the *UL DPCH Information* IE includes the *Min UL Channelisation Code Length* IE, the Node B shall apply the value in the new configuration. The Node B shall apply the contents of the *Max Number of UL DPDCHs* IE (if it is included) in the new configuration.] +- [FDD - If the *UL DPCH Information* IE includes the *UL SIR Target* IE, the Node B shall use the value for the UL inner loop power control when the new configuration is being used.] +- [FDD - If the *UL DPCH Information* IE includes the *Puncture Limit* IE, the Node B shall apply the value in the uplink of the new configuration.] +- [FDD - The Node B shall use the *TFCS* IE for the UL (if present) when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the Uplink of the new configuration.] +- [FDD - If the *UL DPCH Information* IE includes the *UL DPCCH Slot Format* IE, the Node B shall set the new Uplink DPCCH Structure to the new configuration.] +- [FDD - If the *UL DPCH Information* IE includes the *Diversity Mode* IE, the Node B shall apply diversity according to the given value.] +- [FDD - If the *UL DPCH Information* IE includes the *UL DPDCH Indicator For E-DCH Operation* IE and it is set to "UL DPDCH not present", the UL DPDCH resources shall be removed from the configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DPCH Information* IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink in the old configuration, the Node B shall configure the concerned Node B Communication Context to use DPCH in the downlink in the new configuration.] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DPCH Power Information* IE, the Node B shall use the information contained in it for the power settings of the DL DPCH. In particular, if the received *Inner Loop DL PC Status* IE is set to "Active", the Node B shall activate the inner loop DL power control for all RLs. If *Inner Loop DL PC Status* IE is set to "Inactive", the Node B shall deactivate the inner loop DL power control for all RLs according to ref. TS 25.214 [10].] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes a *DL DPCH Information* IE, the Node B shall apply the parameters to the new configuration as follows:] + +- [FDD - The Node B shall use the *TFCS* IE for the DL (if it is present) when reserving resources for the downlink of the new configuration. The Node B shall apply the new TFCS in the Downlink of the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *TFCI Signalling Mode* IE or the *TFCI Presence* IE, the Node B shall use the information when building TFCIs in the new configuration.] + +- [FDD - If the *DL DPCH Information* IE includes the *DL DPCH Slot Format* IE, the Node B shall set the new Downlink DPCH Structure to the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *Multiplexing Position* IE, the Node B shall apply the indicated multiplexing type in the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to "Not Used", the Node B shall not use Limited Power Increase for the inner loop DL power control in the new configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *F-DPCH Information* IE, the Node B shall configure the concerned Node B Communication Context to use F-DPCH in the downlink in the new configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transmission Gap Pattern Sequence Information* IE, the Node B shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated or once the previous Compressed Mode Configuration has been deactivated. This new Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or Node B Communication Context is deleted.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:] + +- [FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].] +- [FDD - If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] +- [FDD - If *UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] +- [FDD - If *Inactivity Threshold for UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then:] + +- [FDD - If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.] +- [FDD - If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].] +- [FDD - If the *DTX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of *DTX Information To Modify* IE is "Deactivate", then DRX should be deactivated together with DTX.] +- [FDD - If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:] + +- [FDD - The Node B shall configure the Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation in the new configuration according to TS 25.214 [10].] +- [FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If at least one of *HS-PDSCH Second Code Support* IE is set to "True", then the Node B shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK RECONFIGURATION READY message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE, then the Node B shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.] +- [1.28 Mcps TDD - If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.] +- [1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Enabling Delay Ext* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allocated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include Allocated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *Transport Block Size List* IE or/and *Repetition Period list* IE is/are included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall modify the configuration of Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21]. +- [1.28 Mcps TDD - If the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall use this information to modify the buffer size for HS-DSCH Semi-Persistent scheduling operation. +- [1.28 Mcps TDD - If the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall use this information to allocate the number of processes for HS-DSCH Semi-Persistent scheduling operation. +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall apply this information for HS-DSCH Semi-Persistent scheduling operation.] + +- [1.28 Mcps TDD - If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28 Mcps TDD - If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *Repetition Period list* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall modify the configuration of Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21]. + +[1.28 Mcps TDD - If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall apply this information for E-DCH Semi-Persistent scheduling operation.] + +- [1.28 Mcps TDD - If the *Semi-Persistent E-DCH releted E-HICH Information* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall use this information to modify the configuration of Semi-Persistent E-DCH releted E-HICH.] +- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall include *Allcoated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the Node B shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the Node B shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MU-MIMO Information* IE, then:] + +- [1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the *MU-MIMO indicator* IE and shall include the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information* IE is included in the *MU-MIMO Information* IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information request* IE is included in the *MU-MIMO Information* IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION READY message, else the Node B shall not include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MU-MIMO Information To Reconfigure* IE, then:] + +- [1.28 Mcps TDD - If the choice of *MU-MIMO Information To Reconf* IE is "Modify", then the Node B shall use this information to modify the indicated MU-MIMO Information parameter in the new configuration.] +- [1.28 Mcps TDD - If the choice of *MU-MIMO Information To Reconf* IE is "Continue", then the Node B shall continue using the old configuration for MU-MIMO operation.] + +#### **[FDD - E-DPCH Handling]:** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DPCH Information* IE, the Node B shall apply the parameters to the new configuration as follows:] + +- [FDD - If the *E-DPCH Information* IE includes the *Maximum Set of E-DPDCHs* IE, the Node B shall apply the contents of the Maximum Set in the new configuration.] +- [FDD - If the *E-DPCH Information* IE includes the *Puncture Limit* IE, the Node B shall apply the value in the uplink of the new configuration] +- [FDD - If the *E-DPCH Information* IE includes the *E-TFCS Information* IE, the Node B shall use the *E-TFCS Information* IE for the E-DCH when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the uplink of the new configuration. If the *E-TFCS Information* IE contains the *E-DCH Minimum Set E-TFCI* IE the Node B shall use the value for the related resource allocation operation.] +- [FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message.] +- [FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the Node B shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message.] +- [FDD - If the *E-DPCH Information* IE includes the *E-TTI* IE, the Node B shall use the value when the new configuration is being used.] +- [FDD - If the *E-DPCH Information* IE includes the *E-DPCCH Power Offset* IE, the Node B shall use the value when the new configuration is being used.] + +- [FDD - If the *E-DPCH Information* IE includes the *E-RGCH 2-Index-Step Threshold* IE, the Node B shall use the value when the new configuration is being used.] +- [FDD - If the *E-DPCH Information* IE includes the *E-RGCH 3-Index-Step Threshold* IE, the Node B shall use the value when the new configuration is being used.] +- [FDD - If the *E-DPCH Information* IE includes the *HARQ Info for E-DCH* IE, the Node B shall use the value when the new configuration is being used.] +- [FDD - If the *E-DPCH Information* IE includes the *HS-DSCH Configured Indicator* IE, the Node B shall use the value when the new configuration is being used.] +- [FDD - If the *E-DPCH Information* IE includes the *Minimum Reduced E-DPDCH Gain Factor* IE , then the Node B shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].] + +#### [TDD - UL/DL CCTrCH Modification] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any *UL CCTrCH to Modify* or *DL CCTrCH to Modify* IE, then the Node B shall treat them each as follows:] + +- [TDD - If the IE includes any of the *TFCS* IE, *TFCS coding* IE or *Puncture Limit* IE, the Node B shall apply these as the new values, otherwise the old values specified for this CCTrCH are still applicable.] +- [TDD - If the IE includes any *UL DPCH To Add* IE, *UL DPCH To Add LCR* IE, *UL DPCH To Add 7.68Mcps* IE, *DL DPCH To Add 7.68Mcps* IE, *DL DPCH To Add LCR* IE, or *DL DPCH To Add* IE, the Node B shall include this DPCH in the new configuration.] +- [TDD - If the IE includes any *UL DPCH To Delete* IE or *DL DPCH To Delete* IE, the Node B shall remove this DPCH in the new configuration.] +- [TDD - If the IE includes any *UL DPCH To Modify* IE or *DL DPCH To Modify* IE and includes any of the *Repetition Period* IE, *Repetition Length* IE or *TDD DPCH Offset* IE, or the message includes UL/DL Timeslot Information and includes any of the [3.84Mcps TDD - *Midamble Shift And Burst Type* IE], [1.28Mcps TDD - *Midamble Shift LCR* IE], [7.68Mcps TDD - *Midamble Shift And Burst Type 7.68Mcps* IE], or *TFCS Presence* IE or the message includes UL/DL Code information and includes [3.84Mcps TDD - *TDD Channelisation Code* IE], [1.28Mcps TDD - *TDD Channelisation Code LCR* IE] , [7.68Mcps TDD - *TDD Channelisation Code 7.68Mcps* IE], [1.28Mcps TDD - *TDD UL DPCH Time Slot Format LCR* IE or *TDD DL DPCH Time Slot Format LCR* IE], the Node B shall apply these specified information elements as the new values, otherwise the old values specified for this DPCH configuration are still applicable.] +- [1.28Mcps TDD - If the *UL CCTrCH To Modify* IE includes the *UL SIR Target* IE, the Node B shall use the value for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21] when the new configuration is being used.] +- [1.28Mcps TDD - If the *UL CCTrCH to Modify* IE includes the *TDD TPC UL Step Size* IE, the Node B shall apply this value to the uplink TPC step size in the new configuration.] +- [TDD - If the *DL CCTrCH to Modify* IE includes the *TDD TPC DL Step Size* IE, the Node B shall apply this value to the downlink TPC step size in the new configuration.] +- [1.28Mcps TDD - If the *DL DPCH To Modify Per RL* IE includes the *TDD TPC DL Step Size* IE and the *RL ID* IE in the *DL DPCH To Modify Per RL* IE is same as the *HS-PDSCH RL ID* IE , the Node B shall apply this value to the HS-SCCH TPC step size in the new configuration.] +- [1.28Mcps TDD - If the *UL Timeslot Information LCR* IE includes the *PLCCH Information* IE, the Node B shall delete / add / modify the PLCCH assignment according to the content when the new configuration is used.] + +#### [TDD - UL/DL CCTrCH Addition] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any *UL CCTrCH To Add* IE or *DL CCTrCH To Add* IE, the Node B shall include this CCTrCH in the new configuration.] + +[TDD - If the *UL/DL CCTrCH To Add* IE includes any [3.84Mcps TDD - *UL/DL DPCH Information* IE] [1.28Mcps TDD - *UL/DL DPCH Information LCR* IE] [7.68Mcps TDD - *TDD Channelisation Code 7.68Mcps* IE], the Node B shall reserve necessary resources for the new configuration of the UL/DL DPCH(s) according to the parameters given in the message.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *TDD TPC DL Step Size* IE within a *DL CCTrCH To Add* IE, the Node B shall set the downlink TPC step size of that CCTrCH to that value, otherwise the Node B shall set the TPC step size of that CCTrCH to the same value as the lowest numbered DL CCTrCH in the current configuration.] + +[1.28Mcps TDD - If the *UL CCTrCH To Add* IE includes the *TDD TPC UL Step Size* IE, the Node B shall apply the uplink TPC step size in the new configuration.] + +[1.28Mcps TDD - The Node B shall use the *UL SIR Target* IE in the *UL CCTrCH To Add* IE as the UL SIR value for the inner loop power control for this CCTrCH according to TS 25.221 [19] and TS 25.224 [21] in the new configuration.] + +[1.28Mcps TDD - If the *DL DPCH To Add Per RL* IE includes the *TDD TPC DL Step Size* IE and the *RL ID* IE in the *DL DPCH To Add Per RL* IE is same as the *HS-PDSCH RL ID* IE, the Node B shall apply this value to the HS-SCCH TPC step size in the new configuration. If no *TDD TPC DL Step Size* IE is included in the *DL DPCH To Add Per RL* IE, the value of *HS-SCCH TPC Step Size* IE should applied to the HS-SCCH TPC step size in the new configuration.] + +[1.28Mcps TDD - If the *UL Timeslot Information LCR* IE includes the *PLCCH Information* IE, the Node B shall add the PLCCH assignment when the new configuration is used.] + +#### **[TDD - UL/DL CCTrCH Deletion]** + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any UL or DL CCTrCH to be deleted, the Node B shall remove this CCTrCH in the new configuration.] + +#### **[FDD - UL CLTD Setup:]** + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Setup", then: the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights according the new configuration defined in the *UL CLTD Information* IE and then:] + +- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] +- [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.] + +#### **[FDD – UL CLTD Modification:]** + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Configuration Change", then: the *UL CLTD Information To Modify* IE defines the new configuration and then:] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE in the *UL CLTD Information To Modify* IE, then the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *S-DPCH Power Offset Information* IE in the *UL CLTD Information To Modify* IE, then the Node B shall use this value to determine the S-DPCH power.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UL CLTD Activation Information* IE in the *UL CLTD Information To Modify* IE, then the Node B shall use this value to update the local state of UL CLTD for the concerned Node B Communication Context. If the *UL CLTD Activation Information* IE is set to "De-activated", the Node B should release the F-TPICH resource configured for the concerned Node B Communication Context.] + +#### **[FDD - UL CLTD Removal:]** + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Removal", then the configured UL CLTD for the concerned Node B Communication Context shall be removed.] + +#### **[FDD - UL MIMO Setup:]** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UL MIMO Information* IE in the *E-DCH FDD Information* IE, or the *UL MIMO Reconfiguration* IE and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Setup", then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] + - [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-ROCH Power Offset* IE in the *UL MIMO Information* IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] + - [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence* IE in *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE and it should include it for the Serving E-DCH RL.] + +#### **[FDD – UL MIMO Modification:]** + +[FDD - If the *UL MIMO Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Configuration Change", then the *UL MIMO Information To Modify* IE defines the new configuration.] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Serving E-DCH RL* IE:] + - [FDD – If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-ROCH resources of the old Serving E-DCH RL at the activation of the new configuration.] + - [FDD - If the new Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] + - [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-ROCH Power Offset* IE in the *UL MIMO Information To Modify* IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] + - [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence* IE or it may alternatively include the *Secondary Transport Block E-HICH Release Indicator* IE in *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE and it should include it for the Serving E-DCH RL.] + +#### **[FDD - UL MIMO Removal:]** + +[FDD - If the *UL MIMO Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Removal", then the configured UL MIMO for the concerned Node B Communication Context shall be removed.] + +#### **DL Power Control:** + +- [FDD - If the *RL Information* IE includes the *DL Reference Power* IEs and the power balancing is active, the Node B shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported, when the new configuration has been activated, according to subclause 8.3.7, using the *DL Reference Power* IE. If the CFN modulo the value of the *Adjustment Period* IE is not equal to 0, the power balancing continues with the old reference power until the end of the current adjustment period, and the updated reference power shall be used from the next adjustment period.] + +[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the *DL Power Balancing Updated Indicator* IE in the *RL Information Response* IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.] + +**[TDD - DSCH Addition/Modification/Deletion]:** + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any *DSCH To Add*, *DSCH To Modify* or *DSCH To Delete* IE, then the Node B shall use this information to add/modify/delete the indicated DSCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.] + +[TDD - The Node B shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each DSCH.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *TNL QoS* IE in the *DSCH TDD Information* IE and if ALCAP is not used, the Node B may use the *TNL QoS* IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.] + +**[TDD - USCH Addition/Modification/Deletion]:** + +- [TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes USCH information for the USCHs to be added/modified/deleted then the Node B shall use this information to add/modify/delete the indicated USCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.] +- [TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes USCH information for the USCHs to be added/modified, if the *TNL QoS* IE is included and if ALCAP is not used, the Node B may use the *TNL QoS* IE to determine the transport bearer characteristics to apply between the Node B and the CRNC for the related USCHs.] +- [TDD - The Node B shall include in the RADIO LINK RECONFIGURATION READY message both the *Transport Layer Address* IE and the *Binding ID* IE for the transport bearer to be established for each USCH.] + +**RL Information:** + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *RL Information* IE, the Node B shall treat it as follows: + +- [FDD - When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.212 [8]. When *p* number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "*PhCH number 1*", the second to "*PhCH number 2*", and so on until the *p*th to "*PhCH number p*".] +- [FDD - If the *RL Information* IE includes a *DL Code Information* IE, the Node B shall apply the values in the new configuration.] +- [FDD - If the *RL Information* IE contains the *Transmission Gap Pattern Sequence Code Information* IE in the *DL Code Information* IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated whenever the downlink compressed mode method SF/2 is active in the new configuration.] +- [FDD - If the *RL Information* IE includes the *Maximum DL Power* and/or the *Minimum DL Power* IEs, the Node B shall apply the values in the new configuration. During compressed mode, the $\delta P_{curr}$ , as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] +- [3.84 Mcps TDD and 7.68 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the maximum CCTrCH DL power for the DCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the maximum + +CCTrCH DL power, otherwise the maximum CCTrCH DL power is the *Maximum Downlink Power* IE included in the *RL Information* IE. If no *Maximum Downlink Power* IE is included (even if *CCTrCH Maximum DL Transmission Power* IEs are included), any maximum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.] + +- [3.84 Mcps TDD and 7.68 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the minimum CCTrCH DL power for the DCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the minimum CCTrCH DL power, otherwise the minimum CCTrCH DL power is the *Minimum Downlink Power* IE included in the *RL Information* IE. If no *Minimum Downlink Power* IE is included (even if *CCTrCH Minimum DL Transmission Power* IEs are included), any minimum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.] +- [3.84 Mcps TDD and 7.68 Mcps TDD - If the *DL CCTrCH To Modify* IE is included and *Maximum CCTrCH DL Power to Modify* IE and/or *Minimum CCTrCH DL Power to Modify* IE are included, the Node B shall apply the values in the new configuration for this DCH type CCTrCH. If the *RL Information* IE includes *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values for all other DCH type CCTrCHs of the radio link.] +- [1.28 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the maximum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the *Maximum DL Power* IE is included in the *DL Timeslot Information LCR* IE for that timeslot, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum Downlink Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a higher power on any applicable DL DPCH. If no *Maximum Downlink Power* IE is included, any maximum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.] +- [1.28 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the minimum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the *Minimum DL Power* IE is included in the *DL Timeslot Information LCR* IE for that timeslot, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum Downlink Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a lower power on any applicable DL DPCH. If no *Minimum Downlink Power* IE is included, any minimum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.] +- [1.28 Mcps TDD - If the *DL CCTrCH To Modify* IE is included and *Maximum DL Power to Modify LCR* IE and/or *Minimum DL Power to Modify LCR* IE are included, the Node B shall apply the values in the new configuration for this timeslot, if the *RL Information* IE includes *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values in the new configuration for all other timeslots.] +- [3.84 Mcps TDD and 7.68 Mcps TDD - If the *RL Information* IE includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the *CCTrCH Initial DL Transmission Power* IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the *Initial DL Transmission Power* IE included in the *RL Information* IE. The Node B shall apply the determined initial CCTrCH DL power to the transmission on each DPCH of the CCTrCH when starting transmission on a new CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no *Initial DL Transmission Power* IE is included with a new CCTrCH (even if *CCTrCH Initial DL Transmission Power* IEs are included), the Node B shall use any transmission power level currently used on already existing CCTrCHs when starting transmission for a new CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4).] +- [3.84 Mcps TDD and 7.68 Mcps TDD - The initial power, maximum power, and minimum power for a DSCH type CCTrCH to be added or modified, shall be determined as follows: + - If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs. + - If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value + +determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol]. + +- [1.28 Mcps TDD - If the *RL Information* IE includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial DL power for each timeslot in a DCH type CCTrCH by the following rule: If the *Initial DL Transmission Power* IE is included in the *DL Timeslot Information LCR* IE, then the Node B shall use that power for the initial DL power, otherwise the initial DL power is the *Initial DL Transmission Power* IE included in the *RL Information* IE. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no *Initial DL Transmission Power* IE is included, the Node B shall use any transmission power level currently used on already existing timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).] +- [1.28 Mcps TDD - If the *RL Information* IE includes the *Initial DL Transmission Power* IE, the Node B shall determine the initial DL power for each timeslot within the DSCH type CCTrCH by the following rule: If both the *CCTrCH Initial DL Transmission Power* IE and the *DL Time Slot ISCP Info LCR* IE are included then the Node B shall use that power for the PDSCH power, otherwise the PDSCH power is the *Initial DL Transmission Power* IE included in the *RL Information* IE. If *DL Time Slot ISCP info LCR* IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each PDSCH and on each timeslot of the CCTrCH when starting transmission on a new CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no *Initial DL Transmission Power* IE is included with a new CCTrCH (even if *CCTrCH Initial DL Transmission Power* IEs are included), the Node B shall use any transmission power level currently used on already existing RL/timeslots when starting transmission for a new CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).] +- [1.28 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the maximum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the *CCTrCH Maximum DL Transmission Power* IE is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the *Maximum Downlink Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a higher power on any applicable DL PDSCH. If no *Maximum Downlink Power* IE is included, any maximum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.] +- [1.28 Mcps TDD - If the *DL CCTrCH To Add* IE is included, the Node B shall determine the minimum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the *CCTrCH Minimum DL Transmission Power* IE is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the *Minimum Downlink Power* IE included in the *RL Information* IE. The Node B shall store this value and not transmit with a lower power on any applicable DL PDSCH. If no *Minimum Downlink Power* IE is included, any minimum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.] +- [1.28 Mcps TDD - If the *DL CCTrCH To Modify* IE is included and the *Maximum CCTrCH DL Power to Modify* IE and/or the *Minimum CCTrCH DL Power to Modify* IE are included, the Node B shall apply the values in the new configuration for this DSCH type CCTrCH, if the *RL Information* IE includes *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values in the new configuration for all other timeslots.] +- [FDD - If the *RL Information* IE includes the *DL DPCH Timing Adjustment* IE, the Node B shall adjust the timing of the radio link accordingly in the new configuration.] +- [1.28 Mcps TDD - If the *RL Information* IE message contains the *Uplink Synchronisation Parameters LCR* IE, the Node B shall use the indicated values of *Uplink Synchronisation Step size* IE and *Uplink Synchronisation Frequency* IE when evaluating the timing of the UL synchronisation.] +- [FDD - If the *RL Information* IE includes the *F-DPCH Slot Format* IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].] + +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Setup", then the Node B shall use the information in *F-TPICH Information* IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214[10].] +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Configuration Change", then: the *F-TPICH Information To Modify* IE defines the new configuration and then:] +- [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Slot Format* IE, then the Node B shall use this information to configure the F-TPICH slot format according to TS 25.211 [7]. +- [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Offset* IE, the Node B shall use this information to configure the time offset of F-TPICH.] +- [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Channelisation Code Number* IE, the Node B shall use this information to configure the channelization code of F-TPICH.] +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Removal", then the Node B shall remove the configured F-TPICH for the RL.] + +#### [TDD - PDSCH RL ID]: + +- [TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *PDSCH RL ID* IE then in the new configuration the Node B shall use the PDSCH and/or PUSCH in this radio link.] + +#### Signalling bearer rearrangement: + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *Signalling Bearer Request Indicator* IE the Node B shall allocate a new Communication Control Port for the control of the Node B Communication Context and include the *Target Communication Control Port ID* IE in the RADIO LINK RECONFIGURATION READY message. + +#### HS-DSCH Setup: + +If the *HS-DSCH Information* IE is present in the RADIO LINK RECONFIGURATION PREPARE message, then: + +- The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. +- The Node B shall include the *HARQ Memory Partitioning* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION READY message. [FDD - The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE, or the *MIMO with four transmit antennas Activation Indicator* IE, or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Meps TDD- The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. + +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information* IE , then the Node B shall , if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Measurement Power Offset* IE in the *HS-DSCH Information* IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SICH SIR Target* IE in the *HS-DSCH Information* IE, the Node B shall use this value to determine the HS-SICH SIR Target. The *HS-SICH SIR Target* IE indicates the received UL SIR target of HS-SICH NACK for this UE.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]). +- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow. +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] + - [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] + - [FDD - If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may use:] + - [FDD - a different HS-SCCH in consecutive TTIs for this UE] + - [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE] + - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the Node B may use the supported HSDPA functions for this UE.] + - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + - [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the *Number of Supported Carriers* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B shall use this information to allocate HSDPA resources over multiple frequencies for UE.] + - [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the *Multi-carrier HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B shall use this information together with the *HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE to allocate HSDPA resources over multiple carriers for the UE.] + - [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B may use this information in HSDPA resources allocation for the UE.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple frequencies and include the *HS-SCCH Specific Information Response LCR per UARFCN* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall include the *HARQ Memory Partitioning per UARFCN* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may indicate the number of multiple frequencies actually used by the UE and include the *Multi-Carrier number* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [1.28 Mcps TDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH TDD Information* IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. + - [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows* + +*Information IE* in the *HS-DSCH Information IE*, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] + +- [FDD - If the *Single Stream MIMO Activation Indicator IE* is included in the *HS-DSCH FDD Information IE*, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator IE* or the *Dual Stream MIMO with four transmit antennas Activation Indicator IE* is included in the *HS-DSCH FDD Information IE*, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – The Node B may include *Precoder weight set restriction IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *CQI Feedback Cycle2 k IE* and the *CQI Cycle Switch Timer IE* is included in *HS-DSCH FDD Information IE*, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.] + +#### [FDD – Secondary Serving HS-DSCH Setup:] + +[FDD – If the *C-ID IE* is present in the *Additional HS Cell Information RL Reconf Prep IE* in the RADIO LINK RECONFIGURATION PREPARE message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the Node B or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency IEs*, in the *HS-DSCH FDD Secondary Serving Information IE* or in the *HS-DSCH FDD Secondary Serving Information To Modify IE* for each instance of the *Additional HS Cell Information RL Reconf Prep IE*, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:] + +- [FDD – The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID IE*. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset IE* in the *HS-DSCH FDD Secondary Serving Information IE*, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *MIMO Activation Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Single Stream MIMO Activation Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE*, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator IE* is included in the *HS-DSCH FDD Secondary Serving Information IE* with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] + +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, the Node B shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – The Node B may include *Precoder weight set restriction* IE the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### Intra-Node B Serving HS-DSCH Radio Link Change: + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-PDSCH RL ID* IE, this indicates the new Serving HS-DSCH Radio Link: + +- In the new configuration the Node B shall de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link and allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link. +- The Node B may include the *HARQ Memory Partitioning* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION READY message. [FDD - The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] [1.28Mcps TDD- The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow. +- If a reset of the MAC-hs is not required the Node B shall include the *MAC-hs Reset Indicator* IE in the RADIO LINK RECONFIGURATION READY message. +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify* IE and the value is set to "allowed" or if *HS-DSCH Information To Modify* IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD – The Node B may include *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### [FDD – Intra-Node B Secondary Serving HS-DSCH Radio Link Change:] + +[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE and the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the Node B and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE for each instance of the *Additional HS Cell Information RL Reconf Prep* IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-Node B secondary serving HS-DSCH Radio Link change then the *HS-PDSCH RL ID* IE indicates the new secondary serving HS-DSCH Radio Link:] + +- [FDD - In the new configuration the Node B shall de-allocate the HS-PDSCH resources of the old secondary serving HS-PDSCH Radio Link and allocate the HS-PDSCH resources for the new secondary serving HS-PDSCH Radio Link. The Node B shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE and the value is set to "allowed" or if *HS-DSCH FDD Secondary Serving Information To Modify* IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the *HS-DSCH FDD Secondary Serving Information* IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link, and then:] + - [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] + - [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + - [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] + - [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary + +serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *Diversity Mode* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, the Node B shall apply cell specific transmit diversity configuration and if the *Diversity Mode* IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information* IE.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – The Node B may include the *Precodeer weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +**[FDD - Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE and an additional non serving E-DCH RL exists in the cell indicated by the *C-ID* IE, the *HS-PDSCH RL ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE indicates the new Additional Serving E-DCH Radio Link.] + +- [FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD -The Node B may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links on secondary UL frequency in the Node B.] + +**[FDD - Additional Serving E-DCH Radio Link Change to a new RL:]** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information RL Reconf Prep* IE and the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE and there is no radio links in the cell indicated by the *C-ID* IE for the Node B Communication Context, the *HS-PDSCH RL ID* IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.] + +- [FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] +- [FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - The Node B may include in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION READY message.] + +### HS-DSCH Modification: + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information To Modify* IE, then: + +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE for every HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the Node B allows the CRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information To Modify* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE in the *HS-DSCH Information To Modify* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH Information To Modify* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH Information To Modify* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. + +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Window Size* IE or *TI* IE in the *HS-DSCH Information To Modify* IE, then the Node B shall use the indicated values in the new configuration for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-d PDU Size Index* IE in the *Modify Priority Queue* choice, the Node B shall delete the previous list of MAC-d PDU Size Index values for the related HSDPA Priority Queue and use the MAC-d PDU Size Index values indicated in the *MAC-d PDU Size Index* IE in the new configuration. +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *CQI Feedback Cycle k* IE, the *CQI Repetition Factor* IE, the *ACK-NACK Repetition Factor* IE, the *ACK Power Offset* IE, the *NACK Power Offset* IE or the *CQI Power Offset* IE in the *HS-DSCH Information To Modify* IE, then the Node B shall use the indicated CQI Feedback Cycle k value, the CQI Repetition Factor or the ACK-NACK Repetition Factor, ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.] +- [FDD - If the *CQI Feedback Cycle2 k* IE or the *CQI Cycle Switch Timer* IE is included in *HS-DSCH Information To Modify* IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in the new configuration.] +- [FDD - If the *HS-SCCH Power Offset* IE is included in the *HS-DSCH Information To Modify* IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *Measurement Power Offset* IE in the *HS-DSCH Information* IE or the *HS-DSCH Information To Modify* IE, then the Node B shall use the measurement power offset as described in TS 25.214 [10] subclause 6A.2.] +- [TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *TDD ACK NACK Power Offset* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use the indicated power offset in the new configuration.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SICH SIR Target* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use this value to the SIR Target in the new configuration. The *HS-SICH SIR Target* IE indicates the received UL SIR target of HS-SICH NACK for this UE.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-SICH TPC step size* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use this value to the HS-SICH TPC step size in the new configuration.] +- [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the *Multi-carrier HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use this information together with the *HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE, the Node B may use this information in HSDPA resources allocation for the UE.] +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information To Modify* IE, then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] +- [FDD - If the *HS-DSCH Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, then the Node B may modify the HS-SCCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the *HS-SCCH Specific Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [TDD - If the *HS-DSCH Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, then the Node B may modify the HS-SCCH parameters corresponding to the HS-DSCH. The Node B shall then report the values for the parameters which are used in the new configuration specified in the [3.84Mcps TDD - *HS-SCCH Specific Information Response*] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR*] + +[7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps*] IEs in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD - If the *HS-DSCH Information To Modify* IE includes the *HS-PDSCH Code Change Grant* IE, then the Node B may modify the HS-PDSCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the concerned Node B is not in Continuous Packet Connectivity HS-SCCH less mode, the RNC shall not include the *HS-PDSCH Code Change Grant* IE in the *HS-DSCH Information To Modify* IE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information To Modify* IE, then the Node B shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information To Modify* IE, then the Node B shall use, in the new configuration, the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]). +- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow. +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Physical Layer Category* IE in the *HS-DSCH Information To Modify* IE, the Node B shall use this information in the new configuration and may include the *HARQ Memory Partitioning* IE in the RADIO LINK RECONFIGURATION READY message. The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is included in the *HS-DSCH Information To Modify* IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] +- [FDD - If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.] +- [FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] +- [1.28Mcps TDD - For a multi-frequency cell, if the *HS-DSCH Information To Modify* IE includes the *HS-SCCH Code Change Grant* IE, and the Node B allows UE to use HSDPA resources distributed over multiple + +frequencies, then the Node B may modify the HS-SCCH Codes corresponding to the HS-DSCH over multiple frequencies, the Node B shall then report the codes which are used in the new configuration specified in the *HS-SCCH Specific Information Response LCR per UARFCN IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] + +- [1.28Mcps TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Physical Layer Category IE* in the *HS-DSCH Information To Modify IE*, the Node B shall use this information in the new configuration and may include the *HARQ Memory Partitioning IE* in the RADIO LINK RECONFIGURATION READY message. The *HARQ Memory Partitioning IE* may contain the *HARQ Memory Partitioning Information Extension For MIMO IE*.] +- [1.28Mcps TDD- If the *MIMO Mode Indicator IE* is included in the *HS-DSCH Information To Modify IE*, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator IE*.] + - [1.28 Mcps TDD - If the *MIMO Mode Indicator IE* is set to "Activate", then the Node B shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream IE* in the *HS-DSCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format IE* for a Priority Queue in the in the *HS-DSCH Information To Modify IE*, the *DL RLC PDU Size Format IE* may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. +- [FDD - If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify IE* the Node B may use the supported HSDPA functions for this UE.] +- [FDD - If the *UE Support Indicator Extension IE* is included in the *HS-DSCH Information To Modify IE* with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Single Stream MIMO Mode Indicator IE* is included in the *HS-DSCH Information To Modify IE*, then the Node B shall activate/deactivate the Single Stream MIMO mode for the HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator IE*.] +- [FDD - If the *MIMO with four transmit antennas Mode Indicator IE*, or the *Dual Stream MIMO with four transmit antennas Mode Indicator IE* is included in the *HS-DSCH Information To Modify IE*, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in accordance with the *MIMO with four transmit antennas Mode Indicator IE* or *Dual Stream MIMO with four transmit antennas Mode Indicator IE*.] +- [FDD - The Node B may include the *Precoder weight set restriction IE* in the *HS-DSCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] + +#### [FDD – Secondary Serving HS-DSCH Modification:] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH FDD Secondary Serving Information To Modify IE* in the *Additional HS Cell Information RL Reconf Prep IE*, then:] + +- [FDD - If the *HS-SCCH Power Offset IE* is included in the *HS-DSCH FDD Secondary Serving Information To Modify IE*, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *Measurement Power Offset IE* in the *HS-DSCH FDD Secondary Serving Information IE* or the *HS-DSCH FDD Secondary Serving Information To Modify IE*, then the Node B shall use the measurement power offset as described in TS 25.214 [10] subclause 6A.2.] +- [FDD - If the *HS-DSCH FDD Secondary Serving Information To Modify IE* includes the *HS-SCCH Code Change Grant IE*, then the Node B may modify the secondary serving HS-SCCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the *HS-SCCH Specific Secondary Serving Information Response IE* in the *HS-DSCH FDD Secondary Serving Information Response IE* in the *Additional HS Cell Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD - If the *MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the Node B shall activate/deactivate the MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link , the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *Diversity Mode* IE is included, then: + - [FDD- the Node B shall apply cell specific transmit diversity configuration for the secondary serving HS-DSCH radio link according to *Diversity Mode* IE and *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information To Modify* IE] + - [FDD - If the *Diversity Mode* IE is not set to "None", the Node B shall apply diversity for the secondary serving HS-DSCH radio link according to the value given in the *Transmit Diversity Indicator* IE in the *HS-DSCH FDD Secondary Serving Information To Modify* IE.] +- [FDD - If the *Non Cell Specific Tx Diversity* IE equals "Tx Diversity" is included, the Node B shall apply non cell specific transmit diversity configuration and reconfigure the transmit diversity setting for the secondary serving HS-DSCH radio link to the same value as defined for the serving HS-DSCH radio link in the new configuration.] +- [FDD -If the *MIMO with four transmit antennas Mode Indicator* IE or the *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or the Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in accordance with the *MIMO with four transmit antennas Mode Indicator* IE or the *Dual Stream MIMO with four transmit antennas Mode Indicator* IE.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### **[FDD – Secondary Serving HS-DSCH Removal:]** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Secondary Serving Remove* IE in the *Additional HS Cell Information RL Reconf Prep* IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.] + +### HS-DSCH MAC-d Flow Addition/Deletion: + +If the RADIO LINK RECONFIGURATION PREPARE message includes any *HS-DSCH MAC-d Flows To Add* or *HS-DSCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to add/delete the indicated HS-DSCH MAC-d flows. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed. + +If the RADIO LINK RECONFIGURATION PREPARE message includes an *HS-DSCH MAC-d Flows To Delete* IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the HS-DSCH configuration from the Node B Communication Context and release the HS-PDSCH resources. + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH MAC-d Flows To Add* IE, then: + +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being added, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size" format for the HS-DSCH, then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE message in the *HS-DSCH MAC-d Flows To Add* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-hs Guaranteed Bit Rate* IE in the *HS-DSCH MAC-d Flows To Add* IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. +- The Node B may include the *HARQ Memory Partitioning* IE in the RADIO LINK RECONFIGURATION READY message. [FDD - The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow. +- [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may include the *HARQ Memory Partitioning per UARFCN* IE in the RADIO LINK RECONFIGURATION READY message.] +- If the RADIO LINK RECONFIGURATION PREPARE message includes *DL RLC PDU Size Format* IE for a Priority Queue in the in the *HS-DSCH MAC-d Flows To Add* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] + +### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] + +[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE the Node B shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [49]:] + +- [FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION PREPARE message. The list of secondary serving HS-DSCH cells is designated by the list of *C-IDs* in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION PREPARE message.] +- [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:] + - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell] + - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells] +- [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].] +- [FDD – The Node B shall return these codes in the *Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK RECONFIGURATION READY message.] +- [FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell's HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].] +- [FDD – The Node B shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION READY message, IEs according to the rules defined for HS-DSCH Setup and:] + - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE.] + - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.] + - [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.] + - [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE.] + - [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] + - [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell.] + - [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell.] + - [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE.] + - [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall store this information in the preconfigured configuration.] + +- [FDD – if the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B may store this information in the preconfigured configuration.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – The Node B shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION READY message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] +- [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *E-DCH Indicator* IE for a secondary cell, the Node B shall include in the *Additional E-DCH Preconfiguration Information* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION READY message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator* IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] +- [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.] + +[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Non-Serving Preconfiguration Setup* IE in the *RL Information* IE and:] + +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD –If the *F-TPICH Information* IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].] + +#### [FDD – Enhanced HS Serving Cell Change:] + +[FDD - Upon receipt of the RADIO LINK RECONFIGURATION PREPARE message, if the Enhanced HS Serving Cell Change is preconfigured in the Node B for the Node B Communication Context, the Node B may execute the Enhanced HS Serving Cell Change procedure according to TS 25.308 [49]] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Enhanced HS Serving CC Abort* IE in the *HS-DSCH Information To Modify* IE or the *HS-DSCH FDD Information* IE then the Node B shall not execute the synchronized Enhanced HS Serving Cell Change procedure when performing the Intra-Node B Serving HS-DSCH Radio Link Change or, at inter Node B radio link change, the HS-DSCH Setup.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Non-Serving RL Preconfiguration Removal* IE, the Node B shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.] + +#### [FDD - Multiflow Setup:] + +[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Multiflow Information* IE in *HS-DSCH FDD Information* IE, or it includes *Multiflow Reconfiguration* IE in *HS-DSCH FDD Information To Modify* IE and the choice of *Setup or Change or Stop* is “Setup”, then the Node B shall setup the requested Multiflow operation and then:] + +- [FDD – Use *Total number of HS-DSCH cells* IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] +- [FDD – Use *Role* IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – Use *MIMO* IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If *Timing* IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B* IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors* IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.] + +#### [FDD - Multiflow Modification:] + +[FDD - If the *Multiflow Reconfiguration* IE is present in *HS-DSCH Information To Modify* IE the RADIO LINK RECONFIGURATION PREPARE message, and the choice of *Setup or Change or Stop* is “Change”, then the Node B shall use new configuration as follows:] + +- [FDD – If the *Total number of HS-DSCH cells* IE is included, then apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] +- [FDD – If the *Role* IE is included, then all the Multiflow cells configured at this Node B are assisting ones, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – If the *MIMO* IE is included, then decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If *Timing* IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B* IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors* IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.] + +#### [FDD - Multiflow Removal:] + +[FDD - If the *Multiflow Reconfiguration* IE is present the *HS-DSCH Information To Modify* IE in the RADIO LINK RECONFIGURATION PREPARE message, and the choice of *Setup or Change or Stop* is “Stop”, then the Node B shall terminate the Multiflow operation.] + +#### [FDD - E-DCH Setup:] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION PREPARE message:] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel information* IE in the *E-DCH FDD Information* IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, then the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [FDD - If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Reference Power Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UPH Filtering Measurement Forwarding Request* IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B:] +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the serving E-DCH RL.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION READY message for the serving E-DCH RL.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *SixteenQAM UL Operation Indicator* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] + +- [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].] + +#### [FDD - E-DCH Radio Link Handling:] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH RL Indication* IE in the *RL Information* IE:] + +- [FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B communication context, on the Radio Links indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - The Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - The Node B shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the *E-DCH RL Indication* set to "Non E-DCH".] +- [FDD - For each RL for which the *E-DCH RL Indication* IE is set to "E-DCH", and which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the *E-DCH RL Set ID* IE in the RADIO LINK RECONFIGURATION READY message. The value of the *E-DCH RL Set ID* IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] + +#### [FDD - Serving E-DCH Radio Link Change:] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Serving E-DCH RL* IE, this indicates the new Serving E-DCH Radio Link:] + +- [FDD - If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link at the activation of the new configuration.] +- [FDD - If the new Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the new serving E-DCH RL.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION READY message for the new serving E-DCH RL.] + - [FDD - The Node B may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links in the Node B.] + +#### [FDD - E-DCH Modification:] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information To Modify* IE, then:] + +- [FDD - If the *E-DCH FDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH HARQ Power Offset FDD* IE in the *E-DCH FDD Information To Modify* IE for an E-DCH MAC-d flow the Node B shall use this information for calculating the unquantised gain factor for an E-TFC ( $\beta_{ed,j,uq}$ ) as defined in TS 25.214 [10].] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the E-DCH Grant Type and it is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information To Modify* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d PDU Size Format* IE in the *E-DCH FDD Information To Modify* IE, then the Node B shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the Node B shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Logical Channel To Modify* IE, the Node B shall use this information to modify the indicated logical channels: + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Guaranteed Bit Rate* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *E-DCH DDI Value* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the Node B shall apply the value in the new configuration.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information To Modify* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Reference Power Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-e Reset Indicator* IE in the *E-DCH FDD Information To Modify* IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *SixteenQAM UL Operation Indicator* IE in the *E-DCH FDD Information To Modify* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] +- [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH DL Control Channel Grant Information* IE in the *E-DCH FDD Information To Modify* IE, the Node B may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the *E-DCH RL ID* IE. The Node B shall then report the modified configuration which is used in the new configuration specified in the *E-DCH FDD DL Control Channel Information* IE for each E-DCH RL in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Fast TTI switching Mode Requested Synchronized* IE in the *E-DCH FDD Information To Modify* IE and Mode 1 is indicated, the Node B shall if supported start the TTI switching process preparation.] +- [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the *Fast TTI switching Mode Requested Synchronized* IE in the *E-DCH FDD Information To Modify* IE and Mode 2 is indicated, the Node B + +shall if supported send the HS-SCCH order at the CFN indicated in Mode 2 to execute the TTI switching process. Refer to TS 25.214 [10]. + +- [FDD - If the *Fast TTI switching Mode Requested Synchronized* IE is included in the *E-DCH FDD Information To Modify* IE in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may indicate which TTI switching Mode it supports in the *Fast TTI switching Mode Supported* IE in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### [FDD - E-DCH MAC-d Flow Addition/Deletion:] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH MAC-d Flows To Add* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flows To Add* IE, then:] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall use this information to optimise MAC-e scheduling decisions.] +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] + +#### [FDD – Additional E-DCH Setup:] + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Prep* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Setup", then the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:] + +- [FDD - If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the Additional E-DCH shall be setup.] +- [FDD - The Node B shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the Additional E-DCH shall be setup.] +- [FDD - The Node B shall setup the Additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.] + +- [FDD - The Node B shall, if supported, use the *Dual Cell E-DCH Operation Enhancements Information IE* for the Secondary uplink frequency if it is included in the *Additional E-DCH FDD Information IE* in the *Additional E-DCH FDD Setup Information IE*.] +- [FDD - If the *DL Power Balancing Information IE* and/or the *Minimum Reduced E-DPDCH Gain Factor IE* are present in the *Multicell E-DCH Information IE* in the *Additional E-DCH FDD Setup Information IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Secondary UL Frequency Activation State* is present in the *Multicell E-DCH Information IE* in the *Additional E-DCH FDD Setup Information IE*, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] +- [FDD - If the *F-DPCH Slot Format IE* is present in the *Additional E-DCH RL Specific Information To Setup IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Primary CPICH Usage For Channel Estimation IE*, the *Secondary CPICH Information*, the *E-AGCH Power Offset IE*, the *E-RGCH Power Offset IE* and/or the *E-HICH Power Offset IE* are present in the *Multicell E-DCH RL Specific Information IE* in the *Additional E-DCH RL Specific Information To Setup IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE*, the *E-DCH Maximum Bitrate IE*, the *E-DCH Minimum Set E-TFCI IE*, the *E-DCH Processing Overload Level IE*, the *Implicit Grant handling IE*, the *Minimum TEBS threshold IE* and/or the *DTX Information2 IE* are present in the *Additional E-DCH FDD Information IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the *DL Power Balancing Activation Indicator IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID IE* included in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID IE* included in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID IE* for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup IE* in the *Additional E-DCH FDD Setup Information IE* the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE* and shall include the *E-RGCH/E-HICH Channelisation Code IE* and the corresponding *E-HICH Signature Sequence IE* and the Node B may include the corresponding *E-RGCH Signature Sequence IE* for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD – If the Additional Serving E-DCH Radio Link is configured in the Node B, then:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding + +E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message.] + +- [FDD - The Node B may include the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION READY message.] + +#### [FDD – Additional E-DCH Configuration Change] + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Prep IE* is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Configuration Change", then the *Additional E-DCH Cell Information Configuration Change IE* defines the new configuration and then:] + +- [FDD - If the *UL Scrambling Code IE* and/or the *UL SIR Target IE* are present in the *UL DPCH Information IE* in the *Additional E-DCH Configuration Change Information IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Minimum Reduced E-DPDCH Gain Factor IE* is present in the *Multicell E-DCH Information IE* in the *Additional E-DCH Configuration Change Information IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *F-DPCH Information IE* is present in the *Additional E-DCH Configuration Change Information IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Dual Cell E-DCH Operation Enhancements Information IE* is present in the *Additional E-DCH FDD Information IE* in the *Additional E-DCH FDD Information To Modify IE* in the *Additional E-DCH Configuration Change Information IE*, the Node B shall, if supported, use the information for the Secondary uplink frequency.] + +#### [FDD – Additional E-DCH RL Addition:] + +[FDD - If the *Additional E-DCH RL Specific Information To Add IE* is present in the *Additional E-DCH Configuration Change Information IE*, then:] + +- [FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B Communication Context, on the Radio Links indicated by the *E-DCH Additional RL ID IE*. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - If the *Initial DL Transmission Power IE*, the *Maximum DL Power IE*, the *Minimum DL Power IE* and/or the *F-DPCH Slot Format IE* are present in the *Additional E-DCH RL Specific Information To Add IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *DL Reference Power IE*, the *E-AGCH Power Offset IE*, the *E-RGCH Power Offset IE*, and/or the *E-HICH Power Offset IE* are present in the *Multicell E-DCH RL Specific Information IE* in the *Additional E-DCH RL Specific Information To Add IE*, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION PREPARE message includes the *DL Reference Power IE*, the Node B shall activate the power balancing and use the *DL Reference Power IE* for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the + +RADIO LINK RECONFIGURATION READY message is supported, according to subclause 8.3.7. In this case, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *E-DCH Additional RL Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{\text{init}}$ shall be set to the power level indicated by the *Initial DL Transmission Power* IE (if received) in the *Additional E-DCH RL Specific Information To Add* IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DCH RLs.] + +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### [FDD – Additional E-DCH RL Modification:] + +[FDD - If the *Additional E-DCH RL Specific Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then the RL indicated by the *E-DCH Additional RL ID* IE indicates the RL on which E-DCH resources shall be modified:] + +- [FDD - If the *DL Code Information* IE, the *Maximum DL Power* IE, the *Minimum DL Power* IE, and/or the *F-DPCH Slot Format* IE are present in the *Additional E-DCH RL Specific Information To Modify* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *DL Reference Power* IE, the *Primary CPICH Usage For Channel Estimation* IE, the *Secondary CPICH Information Change* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE and/or the *E-DCH DL Control Channel Grant* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Modify* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the *DL Power* + +*Balancing Updated Indicator IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.]* + +#### **[FDD – Additional E-DCH Modification:]** + +[FDD - If the *Additional E-DCH FDD Information To Modify IE* is present in the *Additional E-DCH Configuration Change Information IE*, then:] + +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* and/or the *E-DCH Minimum Set E-TFCI IE* is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *E-DCH Maximum Bitrate IE* is included, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the *E-DCH Processing Overload Level IE* is included, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level IE*, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the Additional E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional Modified E-DCH FDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] +- [FDD - If the *DTX Information2 IE* is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *Implicit Grant handling IE* is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *Minimum TEBS threshold IE* is included, the Node B shall use this information for the related resource allocation operation.] + +#### **[FDD – Additional E-DCH Removal]** + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Prep IE* is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Removal", then the additional E-DCH on the secondary uplink frequency shall be removed.] + +#### **[FDD – Radio Links without DPCH/F-DPCH operation]** + +[FDD – If the *Radio Links without DPCH/F-DPCH Indication IE* is present in the RADIO LINK RECONFIGURATION PREPARE message:] + +- [FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.] + +#### **[TDD - Intra-Node B Serving E-DCH Radio Link Change:]** + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Serving RL IE*, this indicates the new Serving E-DCH Radio Link:] + +- [TDD - In the new configuration the Node B shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.] +- [TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - and E-HICH parameters] corresponding to the E-DCH and include the *E-AGCH Specific Information Response TDD IE* [1.28Mcps TDD - and *E-HICH Specific Information Response TDD IE*] in the *E-DCH TDD Information Response IE* in the RADIO LINK RECONFIGURATION READY message.] + +- [TDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] + +#### [TDD - E-PUCH Handling]: + +[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-PUCH Information* IE, the Node B shall apply the parameters to the new configuration.] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-PUCH Information LCR* IE, the Node B shall apply the parameters to the new configuration.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-TFCS Information TDD* IE, the Node B shall apply the beta parameters to the new configuration.] + +#### [3.84Mcps TDD - E-DCH Setup]: + +[3.84Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information* IE and *E-DCH Non-scheduled Grant Information TDD* IE if there are to be non-scheduled grants.] + +#### [1.28Mcps TDD - E-DCH Setup]: + +[1.28Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information LCR* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information LCR* IE and *E-DCH Non-scheduled Grant Information LCR TDD* IE if there are to be non-scheduled grants.] + +[1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information LCR* IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] + +#### [7.68Mcps TDD - E-DCH Setup]: + +[7.68Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information 7.68Mcps* IE and *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE if there are to be non-scheduled grants.] + +#### [TDD - E-DCH MAC-d Flow Addition/Deletion]: + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information TDD* IE in the *E-DCH MAC-d Flows To Add* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining non-scheduled E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the non-scheduled E-DCH configuration from the Node B Communication Context and release the non-scheduled E-DCH resources [1.28 Mcps TDD - and the related Signature Sequence of the Non-scheduled E-HICH].] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d Flows To Add* IE, then:] + +- [TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall use this information to optimise MAC-e scheduling decisions.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *MAC-es Maximum Bit Rate LCR* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] + +### [3.84Mcps TDD - E-DCH Non-scheduled allocations:] + +[3.84Mcps TDD - If the *E-DCH Non-scheduled Grant Information TDD* IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +### [1.28Mcps TDD - E-DCH Non-scheduled allocations:] + +[1.28Mcps TDD - If the *E-DCH Non-scheduled Grant Information LCR TDD* IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +### [7.68Mcps TDD - E-DCH Non-scheduled allocations:] + +[7.68Mcps TDD - If the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +### [TDD - E-DCH Modification:] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH TDD Information To Modify* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH MAC-d PDU Size Format* IE in the *E-DCH TDD Information To Modify* IE, then the Node B shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the [3.84Mcps TDD - *E-DCH TDD Information* IE][1.28Mcps TDD - *E-DCH TDD Information LCR* IE][7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE], then:] + +- [3.84Mcps TDD - If the *E-DCH TDD Information* IE includes the *E-DCH TDD Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR* IE includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [7.68Mcps TDD - If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the [3.84Mcps TDD - *E-DCH TDD Information* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE] includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [TDD - If the [3.84Mcps TDD - *E-DCH TDD Information* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE] includes the *E-DCH Power Offset for Scheduling* + +*Info IE*, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] + +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR IE* includes the *Maximum Number of Retransmission for Scheduling Info LCR IE* and the *E-DCH Retransmission timer for Scheduling Info LCR IE*, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] +- [1.28Mcps TDD - If the *UE TS0 Capability LCR IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information To Modify IE* is not present, or if the *UE TS0 Capability LCR IE* in the *UE Capabilities Information IE* in the *HS-DSCH Information IE* is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the *UE TS0 Capability LCR IE* in the *E-DCH TDD Information to Modify IE*, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR IE* includes the *Multi-Carrier E-DCH Physical Layer Category LCR IE*, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] + +[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH TDD Information To Modify IE*, then:] + +- [TDD - If the *E-DCH TDD Information To Modify IE* contains a *E-DCH MAC-d Flow Specific Information IE* which includes the *Allocation/Retention Priority IE*, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] +- [TDD - If the *E-DCH TDD Information To Modify IE* message includes the *Maximum Number of Retransmissions for E-DCH IE* for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.] +- [1.28Mcps TDD - If the *E-DCH TDD Information To Modify IE* message includes the *E-DCH MAC-d Flow Retransmission Timer IE* for an E-DCH MAC-d flow then the Node B shall use this information to set the retransmission timer.] +- [TDD - If the *E-DCH TDD Information To Modify IE* message includes the *E-DCH HARQ Power Offset TDD IE* for an E-DCH MAC-d flow the Node B shall use this new power offset value.] +- [TDD - If the *E-DCH TDD Information To Modify IE* includes the *E-DCH MAC-d Flow Multiplexing List IE* for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [TDD - If the *E-DCH TDD Information To Modify IE* includes the *E-DCH Grant Type IE*, the Node B shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.] +- [TDD - If the *E-DCH TDD Information To Modify IE* includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the Node B shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.] +- [TDD - If the *E-DCH TDD Information To Modify IE* includes the *E-DCH Logical Channel To Modify IE*, the Node B shall use this information to modify the indicated logical channels:] + - [TDD - If the *E-DCH Logical Channel To Modify IE* includes *Scheduling Priority Indicator IE*, the Node B shall apply the values in the new configuration.] + - [TDD - If the *E-DCH Logical Channel To Modify IE* includes *Scheduling Information IE*, the Node B shall apply the values in the new configuration.] + - [TDD - If the *E-DCH Logical Channel To Modify IE* includes *MAC-es Guaranteed Bit Rate IE*, the Node B shall apply the values in the new configuration.] + - [1.28Mcps TDD - If the *E-DCH Logical Channel To Modify IE* includes *MAC-es Maximum Bit Rate LCR IE*, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] + - [TDD - If the *E-DCH Logical Channel To Modify IE* includes *E-DCH DDI Value IE*, the Node B shall apply the values in the new configuration.] + +- [TDD - If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the Node B shall apply the value in the new configuration.] +- [TDD - If the *E-DCH TDD Information To Modify* IE includes the *MAC-e Reset Indicator* IE in the *E-DCH TDD Information To Modify* IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.] + +#### **[FDD - Phase Reference Handling]:** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Primary CPICH Usage For Channel Estimation* IE, the Node B shall assume that Primary CPICH usage for channel estimation has been reconfigured.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Secondary CPICH Information Change* IE, the Node B shall assume that Secondary CPICH usage for channel estimation has been reconfigured.] + +#### **[FDD - Fast Reconfiguration]:** + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Fast Reconfiguration Mode* IE, the Node B shall, if supported, and if it is possible to base the synchronization of the reconfiguration on the detection of the change in the uplink scrambling code for this reconfiguration, include the *Fast ReconfigurationPermission* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### **[1.28Mcps TDD - Power Control GAP]:** + +[1.28Mcps TDD - If the *Power Control GAP* IE is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to the TS 25.224 [21].] + +#### **[1.28Mcps TDD - E-UTRAN Inter-RAT measurement]:** + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Idle Interval Information* IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to the TS 25.331 [18].] + +#### **[1.28Mcps TDD - HS-DSCH-RNTI for FACH]:** + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH-RNTI for FACH* IE, if supported, the Node B shall store this information and include the *E-RNTI for FACH* IE in the RADIO LINK RECONFIGURATION READY message.] + +#### **[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement]:** + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] + +#### **[1.28Mcps TDD –Multi-Carrier E-DCH Continue]:** + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.] + +#### **[1.28Mcps TDD – Multi-Carrier E-DCH Setup]:** + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Setup", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:] + +- [1.28Mcps TDD - The Node B shall use the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE to decide the transport bearer mode in the new configuration.] +- [1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] + +#### [1.28Mcps TDD – Multi-Carrier E-DCH Change:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Change", then: the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:] + +- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is different from current configured frequencies, then the Node B shall setup the E-DCH resources, as requested in the Node B Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] +- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is the same as any current configured frequency, then the Node B shall reconfigure the E-DCH resources, as requested or as configured in the Node B Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of *Continue, Setup or Change* is "Change" and the *Removal UL Multi-Carrier info* IE is included, then the Node B shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the *UARFCN* IE in the *Removal UL Multi-Carrier info* IE.] + +#### [1.28Mcps TDD – Non-rectangular resource operation:] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *UE support of non-rectangular resource allocation* IE, the Node B shall, if supported, use this information to determine whether includes the *Non-rectangular resource allocation indicator* IE and the *Non-rectangular resource timeslot set* IE or not.] + +#### [FDD - UL DPCCH2 Setup:] + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Setup", then:] + +- [FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].] +- [FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.] +- [FDD – If the *UL DPCCH2 Reconfiguration* IE includes the *Extended E-DPCCH Power Offset* IE, the concerned Node B shall use the value when the new configuration is being used.] + +#### [FDD – UL DPCCH2 Modification:] + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Configuration Change", then: the *UL DPCCH2 Information To Modify* IE defines the new configuration and then:] + +- [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *F-DPCH info* IE in the *UL DPCCH2 Information To Modify* IE and if the serving HS-DSCH RL is in the Node B, then the Node B shall use this value to update the second F-DPCH for the concerned Node B Communication Context.] +- [FDD – If the *UL DPCCH2 Reconfiguration* IE includes the *Extended E-DPCCH Power Offset* IE, the concerned Node B shall use the value when the new configuration is being used.] + +#### [FDD - UL DPCCH2 Removal:] + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Removal", then the configured UL DPCCH2 for the concerned Node B Communication Context shall be removed.] + +#### [FDD – Downlink TPC enhancements Setup:] + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Setup", then:] + +- [FDD – The NodeB shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *RL Information* is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCH Cell Information Setup* is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.] + +#### **[FDD –Downlink TPC enhancements Modification:]** + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Configuration Change", then: the *Downlink TPC enhancements Information To Modify* IE defines the new configuration and then:] + +- [FDD - The NodeB shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to reconfigure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *RL Information* is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCH Cell Information Configuration Change* is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.] + +#### **[FDD - Downlink TPC enhancements Removal:]** + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Removal", then the configured power control Algorithm 3 for the concerned Node B Communication Context shall be removed.] + +### **General** + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Layer Address* IE and *Binding ID* IEs in the [TDD - *DSCHs To Modify, DSCHs To Add, USCHs To Modify, USCHs To Add*], *HS-DSCH Information, HS-DSCH Information To Modify, HS-DSCH MAC-d Flows To Add*, [TDD - *E-DCH MAC-d Flows to Add, E-DCH TDD Information to Modify* IE] [FDD - *RL Specific E-DCH Information* IE] or in the *RL Specific DCH Information* IEs, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] being added, or any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. + +If the requested modifications are allowed by the Node B and the Node B has successfully reserved the required resources for the new configuration of the Radio Link(s), it shall respond to the CRNC with the RADIO LINK RECONFIGURATION READY message. When this procedure has been completed successfully there exists a Prepared Reconfiguration, as defined in subclause 3.1. + +The Node B shall include in the RADIO LINK RECONFIGURATION READY message the *Transport Layer Address* IE and the *Binding ID* IE for any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] being added or any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. + +In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iub interface, the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE shall be included [FDD - if the *Transport Bearer Not Requested Indicator* IE is not included for this DCH,] only for one of the DCH in the set of co-ordinated DCHs. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for a DCH or an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for a DCH or an E-DCH MAC-d flow and:] + +- [FDD - if the Node B establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include in the RADIO LINK RECONFIGURATION READY message the *Binding ID* IE and *Transport Layer Address* IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.] +- [FDD - if the Node B does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.] + +In the case of a Radio Link being combined with another Radio Link within the Node B, the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE shall be included only for one of the combined Radio Links [FDD - if the *Transport Bearer Not Requested Indicator* IE is not included for this DCH]. + +[FDD - In the case of an E-DCH RL being combined with another E-DCH RL within the Node B, the *E-DCH FDD Information Response* IE shall be included only for one of the combined E-DCH RLs.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Additional E-DCH Cell Information RL Reconf Prep* IE, then:] + +- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [FDD – if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] +- [FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:] + - [FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Not Requested Indicator* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and/or the *Transport Bearer Request Indicator* IE in the *E-DCH FDD Information To Modify* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] + - [FDD - If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE or in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information To Modify* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information Configuration Change* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION READY message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE and/or and/or include the *Binding ID* IE and *Transport Layer Address* IE for the E-DCH MAC-d flow has been modified in the + +*Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional Modified E-DCH FDD Information Response IE.]* + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Multi-Carrier E-DCH Information Reconf* IE, then:] + +- [1.28Mcps TDD - If the *Multi-carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.] +- [1.28Mcps TDD - If the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Setup" and the Separate Iub transport bearer mode is used in the new configuration, or if the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Change" and the Transport Bearer Mode is changed to "Separate Iub Transport Bearer Mode" indicated by *Multi-carrier E-DCH Transport Bearer Mode LCR* IE, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] +- [1.28Mcps TDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Request Indicator* IE in the *E-DCH TDD Information to Modify* IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.] +- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the *Transport Bearer Request Indicator* IE is set to " Bearer Requested ", then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] + +### 8.3.2.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Synchronised Radio Link Reconfiguration Preparation procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B with the label 'RADIO LINK RECONFIGURATION PREPARE'. A horizontal arrow points from Node B back to CRNC with the label 'RADIO LINK RECONFIGURATION FAILURE'.](26d37a5ec149b21b1520a5bb18422208_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: RADIO LINK RECONFIGURATION PREPARE + CRNC->>Node B: RADIO LINK RECONFIGURATION PREPARE + Note right of Node B: RADIO LINK RECONFIGURATION FAILURE + Node B-->>CRNC: RADIO LINK RECONFIGURATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Synchronised Radio Link Reconfiguration Preparation procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B with the label 'RADIO LINK RECONFIGURATION PREPARE'. A horizontal arrow points from Node B back to CRNC with the label 'RADIO LINK RECONFIGURATION FAILURE'. + +**Figure 31: Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation** + +If the Node B cannot reserve the necessary resources for all the new DCHs of one set of co-ordinated DCHs requested to be added, it shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed. + +If the requested Synchronised Radio Link Reconfiguration Preparation procedure fails for one or more RLs, the Node B shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC, indicating the reason for failure. + +Typical cause values are as follows: + +#### Radio Network Layer Cause + +- UL SF not supported +- DL SF not supported +- Downlink Shared Channel Type not supported +- Uplink Shared Channel Type not supported + +- CM not supported +- Number of DL codes not supported +- Number of UL codes not supported +- RL Timing Adjustment not supported +- F-DPCH not supported +- [FDD - Continuous Packet Connectivity DTX-DRX operation not available] +- [FDD - Continuous Packet Connectivity UE DTX Cycle not available] +- [FDD - MIMO not available] +- E-DCH MAC-d PDU Size Format not available +- [FDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - Multi Cell operation not available.] +- [1.28Meps TDD- MIMO not available] +- [1.28Meps TDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - TX diversity for MIMO UE on DL Control Channels not available] +- [FDD – Single Stream MIMO not available] +- [FDD - Multi Cell operation with MIMO not available] +- [FDD - Multi Cell operation with Single Stream MIMO not available] +- [FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available] +- [FDD - Multi Cell E-DCH operation not available] +- [FDD - UL CLTD operation not available] +- [FDD - MIMO with four transmit antennas not available] +- [FDD - Dual Stream MIMO with four transmit antennas not available] +- [FDD – Multiflow operation not available] +- [FDD - SixtyfourQAM UL operation not available] +- [FDD – UL MIMO operation not available] +- [FDD – UL MIMO and SixteenQAM operation not available] +- [FDD – UL MIMO and SixtyfourQAM operation not available] +- [FDD – E-DCH decoupling operation not available] +- [FDD – Basic DCH Enhancements operation not available] +- [FDD – Full DCH Enhancements operation not available] +- [FDD – Radio Links without DPCH/F-DPCH operation not available] +- [FDD – UL DPCCH2 operation not available] +- [FDD – Downlink TPC enhancements operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with different TTI operation not available] + +### Transport Layer Cause + +- Transport Resources Unavailable + +### Miscellaneous Cause + +- O&M Intervention +- Control processing overload +- HW failure + +## 8.3.2.4 Abnormal Conditions + +If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC. + +If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected"], the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as failed and shall respond with a RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION PREPARE message includes a *DCHs To Modify* IE or *DCHs To Add* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCHs To Modify* IE or *DCHs To Add* IE do not have the same *Transmission Time Interval* IE in the *Semi-Static Transport Format Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the *RL Information* IE includes the *DL Reference Power* IE, but the power balancing is not active in the indicated RL(s), the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the Node B shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".] + +[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s) but the RADIO LINK RECONFIGURATION PREPARE message IE includes more than one *DL Reference Power* IE, the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the Node B shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".] + +If the RADIO LINK RECONFIGURATION PREPARE message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message is to modify UE channel estimation information for an existing RL and the modification is not allowed according to TS 25.214 [10] subclause 4.3.2.1, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE or *HS-DSCH MAC-d Flows To Delete* IE in addition to the *HS-DSCH Information* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE, *HS-DSCH MAC-d Flows To Delete* IE or *HS-PDSCH RL ID* IE and the Serving HS-DSCH Radio Link is not in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information* IE and does not include the *HS-PDSCH RL-ID* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Information To Modify* IE deleting the last remaining Priority Queue of an HS-DSCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-PDSCH RL-ID* IE indicating a Radio Link not existing in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[TDD - If multiple radio links exist within the Node B Communication Context and the RADIO LINK RECONFIGURATION PREPARE message does not include a *RL ID* IE within each *UL DPCH To Add Per RL* IE, *DL DPCH To Add Per RL* IE, *UL DPCH To Modify Per RL* IE, and *DL DPCH To Modify Per RL* IE that is present in the message, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *HS-DSCH Information* IE, *HS-DSCH Information To Modify* IE, or *HS-DSCH MAC-d Flows To Add* IE and if in the new configuration the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Indexed MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Fixed MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *HS-DSCH Information* IE and if the *Measurement Power Offset* IE is not present, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION PREPARE message includes *HS-DSCH Information* IE and the HS-DSCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *F-DPCH Information* IE and the *DL DPCH Information* IE configured simultaneously to one downlink frequency, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned the Node B Communication Context is configured to use DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes the *DL DPCH Power Information* IE , then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to use F-DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes at least one but not all of the *TFCS* IE, *DL DPCH Slot Format* IE, *TFCI Signalling Mode* IE, *Multiplexing Position* IE, *Limited Power Increase* IE and *DL DPCH Power Information* IE in the *DL DPCH Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION PREPARE message, but the *E-DPCH Information* IE is not present or if any of the *Maximum Set of E-DPDCHs* IE, *Puncture Limit* IE, *E-TFCS Information* IE, *E-TTI* IE, *E-DPCCH Power Offset* IE, *E-RGCH 2-Index-Step Threshold* IE, *E-RGCH 3-Index-* + +*Step Threshold IE, HARQ Info for E-DCH IE or HS-DSCH Configured Indicator IE* are not present in the *E-DPCH Information IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Primary CPICH Usage For Channel Estimation IE* and/or *Secondary CPICH Information Change IE* and if in the new configuration Node B shall assume that the UE is not using the Primary CPICH for channel estimation nor the Secondary CPICH, Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes one of the *Not Used IEs*, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH RL Indication IE* set to "E-DCH", but no *E-DCH FDD Information IE*, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information IE* but no *E-DCH RL Indication IE* set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION PREPARE message does not contain the *E-DCH Decoupling Indication IE* but contains the *HS-PDSCH RL ID IE* and/or the *Serving E-DCH RL IE*, and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *HS-PDSCH RL ID IE* and the *E-DPCH Information IE* which includes the *HS-DSCH Configured Indicator IE* set as "HS-DSCH not configured" then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE* or *E-DCH MAC-d Flows To Delete IE* in addition to the *E-DCH FDD Information IE*, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains any of the *E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE, E-DCH MAC-d Flows To Delete IE* and the Node B Communication Context is not configured for E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH FDD Information To Modify IE* deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes *E-DCH FDD Information IE* and the E-DCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[TDD - if the radio link was not previously configured to support E-DCH, then if the RADIO LINK RECONFIGURATION PREPARE message includes one of the following E-DCH information elements then it shall contain all of them otherwise the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.: *E-DCH Serving RL IE*, [3.84Mcps TDD and 7.68Mcps TDD - *E-PUCH Information IE, E-TFCS Information TDD IE*], [1.28Mcps TDD - *E-PUCH Information LCR IE, E-TFCS Information TDD IE*], *E-DCH MAC-d Flows to Add IE*, and [3.84Mcps TDD - *E-DCH TDD Information IE*], [1.28Mcps TDD - *E-DCH TDD Information LCR IE*] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps IE*.] + +[FDD - If the *Fast Reconfiguration IE* is included in the RADIO LINK RECONFIGURATION PREPARE message and the *UL Scrambling Code IE* does not indicate an uplink scrambling code different from the currently used uplink scrambling code the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* in addition to the *Continuous Packet Connectivity DTX-DRX Information IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE in addition to the *Continuous Packet Connectivity HS-SCCH less Information* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE while the Continuous Packet Connectivity HS-SCCH less configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE while the Continuous Packet Connectivity DTX-DRX configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *DRX Information To Modify* IE in *Continuous Packet Connectivity DTX-DRX Information To Modify* IE while the Continuous Packet Connectivity DRX configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to "Uplink DCH only" but no *Transport Format Set* IE for the uplink for this DCH and the Node B had ignored the configuration of Transport Format Set for uplink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH Indicator* IE set to "Downlink DCH only" but no *Transport Format Set* IE for the downlink for this DCH and the Node B had ignored the configuration of Transport Format Set for downlink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Transport Bearer Not Requested Indicator* IE for a DCH but does not contain the corresponding *DCH ID* IE and the *Unidirectional DCH indicator* IE set to "Uplink DCH only" for the DCH in *DCH Information To Add* IE, the Node B shall reject the procedure using the the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 4 but is not configured to use F-DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply the "Closed loop mode 1" and if the concerned Node B Communication Context is not configured to apply UL DPCCH Slot Format 2 or 3, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply MIMO, allowed to apply 64 QAM, establish the the secondary serving HS-DSCH Radio Link or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE for a DCH in the *RL Specific DCH Information* IE but does not include the *DCH ID* IE for the DCH in the *DCHs to Add* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the *Continuous Packet Connectivity DTX-DRX Information* IE but does not contain the *F-DPCH Information* IE and the concerned Node B Communication Context is not previously configured to use F-DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the Transport Bearer is not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *Transport Bearer Not Requested Indicator* IE for a DCH for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION PREPARE message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DCH, the E-DCH MAC-d flow and/or the HS-DSCH MAC-d flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[TDD - If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DSCH and/or a USCH but the RADIO LINK RECONFIGURATION PREPARE message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DSCH and/or the USCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information to Modify LCR* IE in addition to the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information to Modify LCR* IE in addition to the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size" for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH FDD Secondary Serving Information* IE but does not contain the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE or the message includes the *C-ID* IE but does not contain the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains a *MIMO Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a *MIMO Activation Indicator* IE, a *Single Stream MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Diversity Mode* IE in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE and the secondary serving HS-DSCH is already configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the secondary serving HS-DSCH is not configured in the Node B Communication Context and if the RADIO LINK RECONFIGURATION PREPARE message contains in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE the *Diversity Mode* IE not set to "None" but not the *Transmit* + +*Diversity Indicator* or contains the *Transmit Diversity Indicator* but not the *Diversity Mode* IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Diversity Mode* IE in the *Secondary Serving Information To Modify* IE in the *Additional HS Cell Information RL Reconf Prep* IE and the *Non Cell Specific Tx Diversity* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH Cell Information RL Reconf Prep* IE and if the *E-DPCH Information* IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH Cell Information RL Reconf Prep* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE is not present, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE in the *Additional E-DCH Cell Information RL Reconf Prep* IE and the *C-ID* IE is not included but the Radio Link indicated by the *E-DCH Additional RL ID* IE is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional HS Cell Information RL Reconf Prep* IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the *Ordinal Number Of Frequency* IE in the *HS-DSCH FDD Secondary Serving Information* IE or the *HS-DSCH FDD Secondary Serving Information To Modify* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Additional HS Cell Information RL Reconf Prep* IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have *Ordinal Number Of Frequency* value "1", the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *UL CLTD Information* IE but does not contain the *F-TPICH Information* IE, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL CLTD Information* IE but without *F-TPICH Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *UL MIMO Reconfiguration* IE in *E-DCH FDD Information* IE, and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Setup", but the *UL CLTD Information* IE is not present and is not previously configured, or if it contains *HS-DSCH Preconfiguration Setup* IE with *UL MIMO Information* IE but without *UL CLTD Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a *MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *DCH Enhancements Information* IE, and either the *DL DPCH Slot Format* IE is not set to "17" or "18", or the *UL DPCCH Slot Format* IE is not set to "5", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message does not contain the *DCH Enhancements Information* IE, and either (i) the *DL DPCH Slot Format* IE is set to "17", or (ii) the *DL DPCH Slot Format* IE is set to "18", or (iii) the *UL DPCCH Slot Format* IE is set to "5", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the *Fast TTI switching Mode Requested UnSynchronized* IE in the *E-DCH FDD Information To Modify* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured but the *Dual Cell E-DCH Operation Enhancements Information* IE is not included in the RADIO LINK RECONFIGURATION PREPARE message, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured and if the *Continuous Packet Connectivity DTX-DRX Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message, but the *DTX Information* IE does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured but the *DTX Information To Modify* IE, if included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE in the RADIO LINK RECONFIGURATION PREPARE message and the choice is “Modify”, does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured and if the DTX related Information is not signalled but the currently used value is not from the set of values defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +### 8.3.3 Synchronised Radio Link Reconfiguration Commit + +#### 8.3.3.1 General + +This procedure is used to order the Node B to switch to the new configuration for the Radio Link(s) within the Node B, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure. + +When Mode 1 is used for the fast TTI switching, the procedure shall if supported be used to order the Node B to execute the TTI switching process. + +The message shall use the Communication Control Port assigned for this Node B Communication Context. + +#### 8.3.3.2 Successful Operation + +![Sequence diagram showing the Synchronised Radio Link Reconfiguration Commit procedure. A CRNC sends a RADIO LINK RECONFIGURATION COMMIT message to a Node B.](98d0322515464572a78f3e4ee94105ed_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + Note right of Node B: Node B + CRNC->>Node B: RADIO LINK RECONFIGURATION COMMIT + +``` + +Sequence diagram showing the Synchronised Radio Link Reconfiguration Commit procedure. A CRNC sends a RADIO LINK RECONFIGURATION COMMIT message to a Node B. + +**Figure 32: Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation** + +[FDD - If the *Activation Delay* IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the Node B shall if supported send the HS-SCCH order to execute the TTI switching process according to TS 25.214 [10]. The *CFN* IE in the RADIO LINK RECONFIGURATION COMMIT message shall be ignored by the Node B.] + +The Node B shall switch to the new configuration previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure + +- [TDD - at the next coming CFN with a value equal to the value requested by the CRNC in the *CFN* IE (see ref. TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the CRNC.] +- [FDD - if the *Fast Reconfiguration* IE is not included in the RADIO LINK RECONFIGURATION COMMIT message at the next coming CFN with a value equal to the value requested by the CRNC in the *CFN* IE (see ref. TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the CRNC.] +- [FDD - if the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message as soon as the Node B detects that the UE uses the new configuration in the uplink (e.g. the Node B + +detects that the UE uses the new scrambling code used for the uplink by sending the RADIO LINK RESTORATION message). In order to limit the period for the detection in the Node B the CFN in the RADIO LINK RECONFIGURATION COMMIT message indicates the earliest possible time instant at which the UE might use the new configuration.] + +[FDD - If the *Active Pattern Sequence Information* IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the *CM Configuration Change CFN* IE in the *Active Pattern Sequence Information* IE shall be ignored by the Node B.] + +[FDD - If the *Active Pattern Sequence Information* IE is not included in the RADIO LINK RECONFIGURATION COMMIT message and a new Compressed Mode Configuration exists in the prepared configuration, the Node B shall behave as if an *Active Pattern Sequence Information* IE with an empty *Transmission Gap Pattern Sequence Status* IE was included.] + +When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1. + +In the case of a Transport Channel or MAC-d flow modification for which a new transport bearer was requested and established, the switch to the new transport bearer shall also take place at the configuration switching point (defined above). The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [16], subclause 5.10.1 and in TS 25.435 [24], subclauses 5.8.2 and 5.8.3. + +In the case of a signalling bearer re-arrangement, the new Communication Control Port shall be used once the Node B has received the RADIO LINK RECONFIGURATION COMMIT message via the old Communication Control Port. + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT includes the *Active Pattern Sequence Information* IE, the Node B shall deactivate all the ongoing Transmission Gap Pattern Sequences at the configuration switching point (defined above). From that moment on, all Transmission Gap Pattern Sequences included in *Transmission Gap Pattern Sequence Status* IE repetitions shall be started when the indicated *TGCFN* IE elapses. The *CFN* IE and *TGCFN* IE for each sequence refer to the next coming CFN with that value. If the values of the *CFN* IE and the *TGCFN* IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the *CFN* IE.] + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the *Active Pattern Sequence Information* IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing.] + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.] + +### 8.3.3.3 Abnormal Conditions + +If a new transport bearer is required for the new reconfiguration and it is not available at the configuration switching point (defined above), the Node B shall initiate the Radio Link Failure procedure. + +[FDD - If the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message and the Node B did not include the *Fast ReconfigurationPermission* IE in the RADIO LINK RECONFIGURATION READY message, the Node B shall initiate the Radio Link Failure procedure.] + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the *Active Pattern Sequence Information* IE which activates a downlink transmission gap pattern sequence with an SF/2 downlink compressed mode method and if the concerned Node B Communication Context is configured to use DPCH in downlink and for any Radio Link the transmission gap pattern sequence code information is not available, the Node B shall trigger the Radio Link Failure procedure with the cause value "Invalid CM Settings".] + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK FAILURE message with the cause value "Invalid CM settings".] + +[FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the *Activation Delay* IE but the *Fast TTI switching Mode Requested Synchronized* IE is not presented in the RADIO LINK RECONFIGURATION PREPARE or the Mode 1 is not supported, the Node B shall initiate the Radio Link Failure procedure.] + +## 8.3.4 Synchronised Radio Link Reconfiguration Cancellation + +### 8.3.4.1 General + +This procedure is used to order the Node B to release the new configuration for the Radio Link(s) within the Node B, previously prepared by the Synchronised Radio Link Preparation Reconfiguration procedure. + +The message shall use the Communication Control Port assigned for this Node B Communication Context. + +### 8.3.4.2 Successful Operation + +![Sequence diagram for Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation. It shows a single message 'RADIO LINK RECONFIGURATION CANCEL' being sent from CRNC to Node B.](0710ab057e5a25c06032594433b01316_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: RADIO LINK RECONFIGURATION CANCEL +``` + +Sequence diagram for Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation. It shows a single message 'RADIO LINK RECONFIGURATION CANCEL' being sent from CRNC to Node B. + +**Figure 33: Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation** + +When receiving the RADIO LINK RECONFIGURATION CANCEL message from the CRNC, the Node B shall release the new configuration ([FDD - including the new Transmission Gap Pattern Sequence parameters (if existing)]) previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure and continue using the old configuration. When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1. + +### 8.3.4.3 Abnormal Conditions + +- + +## 8.3.5 Unsynchronised Radio Link Reconfiguration + +### 8.3.5.1 General + +The Unsynchronised Radio Link Reconfiguration procedure is used to reconfigure Radio Link(s) related to one UE-UTRAN connection within a Node B. + +The Unsynchronised Radio Link Reconfiguration procedure is used when there is no need to synchronise the time of the switching from the old to the new configuration in one Node B used for a UE-UTRAN connection with any other Node B also used for the UE-UTRAN connection. + +The Unsynchronised Radio Link Reconfiguration procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. + +### 8.3.5.2 Successful Operation + +![Sequence diagram for Unsynchronised Radio Link Reconfiguration Procedure, Successful Operation. It shows two messages: 'RADIO LINK RECONFIGURATION REQUEST' from CRNC to Node B, and 'RADIO LINK RECONFIGURATION RESPONSE' from Node B back to CRNC.](46ed1f28ea8dfc28049900e848488ae7_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: RADIO LINK RECONFIGURATION REQUEST + Node B-->>CRNC: RADIO LINK RECONFIGURATION RESPONSE +``` + +Sequence diagram for Unsynchronised Radio Link Reconfiguration Procedure, Successful Operation. It shows two messages: 'RADIO LINK RECONFIGURATION REQUEST' from CRNC to Node B, and 'RADIO LINK RECONFIGURATION RESPONSE' from Node B back to CRNC. + +**Figure 34: Unsynchronised Radio Link Reconfiguration Procedure, Successful Operation** + +The Unsynchronised Radio Link Reconfiguration procedure is initiated by the CRNC by sending the RADIO LINK RECONFIGURATION REQUEST message to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context. + +Upon reception, the Node B shall modify the configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. + +The Node B shall prioritise resource allocation for the RL(s) to be modified according to Annex A. + +If the *UE Aggregate Maximum Bit Rate* IE is contained in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. + +#### DCH Modification: + +If the RADIO LINK RECONFIGURATION REQUEST message includes any *DCHs To Modify* IE then the Node B shall treat them each as follows: + +- If the *DCHs To Modify* IE includes the *Frame Handling Priority* IE, the Node B should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated. +- If the *DCHs To Modify* IE includes the *TNL QoS* IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The *TNL QoS* IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs. +- If the *DCHs To Modify* IE includes the *Transport Format Set* IE for the UL, the Node B shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration. +- If the *DCHs To Modify* IE includes the *Transport Format Set* IE for the DL, the Node B shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration. +- If the *DCHs To Modify* IE includes the *Allocation/Retention Priority* IE for a DCH, the Node B shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A. +- If the *DCHs To Modify* IE includes multiple *DCH Specific Info* IEs, then the Node B shall treat the DCHs in the *DCHs To Modify* IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. +- [FDD - If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to "Uplink DCH only", the Node B shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.] +- [FDD - If the *DCHs to Modify* IE contains a *DCH Specific Info* IE which includes the *Unidirectional DCH indicator* IE set to "Downlink DCH only", the Node B shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.] +- If the *DCHs To Modify* IE includes the *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- If the *DCHs To Modify* IE includes the *ToAWS* IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- If the *DCHs To Modify* IE includes the *ToAWE* IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- [TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *CCTrCH ID* IE for the DL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Downlink of this DCH in the new configuration.] +- [TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *CCTrCH ID* IE for the UL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.] + +#### DCH Addition: + +If the RADIO LINK RECONFIGURATION REQUEST message includes any *DCH To Add* IE, the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCHs in the new configuration. In particular: + +- If a *DCHs To Add* IE includes multiple *DCH Specific Info* IEs for a DCH to be added, the Node B shall treat the DCHs in the *DCHs To Add* IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. +- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Uplink DCH only", the Node B shall ignore the *Transport Format Set* IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. +- If the *DCH Specific Info* IE includes the *Unidirectional DCH Indicator* IE set to "Downlink DCH only", the Node B shall ignore the *Transport Format Set* IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. +- [FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the *QE-Selector* IE set to "selected", the Node B shall use the Transport channel BER from that DCH as the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE TS 25.427 [16]. If the *QE-Selector* IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].] +- For a set of co-ordinated DCHs, the Node B shall use the Transport channel BER from the DCH with the *QE-Selector* IE set to "selected" as the QE in the UL data frames TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE TS 25.427 [16]. If all DCHs have the *QE-Selector* IE set to "non-selected", the Physical channel BER shall be used for the QE TS 25.427 [16].] +- The Node B should store the *Frame Handling Priority* IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated. +- If the *TNL QoS* IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The *TNL QoS* IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs. +- The Node B shall use the included *UL FP Mode* IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- The Node B shall use the included *ToAWS* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- The Node B shall use the included *ToAWE* IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. +- [TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *CCTrCH ID* IE for the DL of a DCH to be added, the Node B shall apply the new CCTrCH ID in the downlink of this DCH in the new configuration.] +- [TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *CCTrCH ID* IE for the UL of a DCH to be added, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.] + +#### DCH Deletion: + +If the RADIO LINK RECONFIGURATION REQUEST message includes any DCH to be deleted from the Radio Link(s), the Node B shall not include this DCH in the new configuration. + +If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the Node B shall not include this set of co-ordinated DCHs in the new configuration. + +**[FDD - Physical Channel Modification]:** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *UL DPCH Information* IE, then the Node B shall apply the parameters to the new configuration as follows:] + +- [FDD - If the *UL DPCH Information* IE includes the *TFCS* IE for the UL, the Node B shall apply the new TFCS in the Uplink of the new configuration.] +- [FDD - If the *UL DPCH Information* IE includes the *UL DPDCH Indicator For E-DCH Operation* IE set to "UL DPDCH not present", the UL DPDCH resources shall be removed from the configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes a *DL DPCH Information* IE, then the Node B shall apply the parameters to the new configuration as follows:] + +- [FDD - If the *DL DPCH Information* IE includes on the *TFCS* IE for the DL, the Node B shall apply the new TFCS in the Downlink of the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *TFCI Signalling Mode* IE, the Node B shall use the information when building TFCIs in the new configuration. +- [FDD - If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.] +- [FDD - If the *DL DPCH Information* IE includes the *Limited Power Increase* IE set to "Not Used", the Node B shall not use Limited Power Increase for the inner loop DL power control in the new configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transmission Gap Pattern Sequence Information* IE, the Node B shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated. This new Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or Node B Communication Context is deleted.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information* IE, then:] + +- [FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].] +- [FDD - If *DRX Information* IE is included in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] +- [FDD - If *UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] +- [FDD - If *Inactivity Threshold for UE DRX Cycle 2* IE is included in the *DRX Information* IE in the *Continuous Packet Connectivity DTX-DRX Information* IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then:] + +- [FDD - If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.] +- [FDD - If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].] +- [FDD - If the *DTX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this information to modify the indicated DTX Information + +parameter in the new configuration. If the choice of *DTX Information To Modify* IE is "Deactivate", then DRX should be deactivated together with DTX.] + +- [FDD - If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DTX-DRX Information To Modify* IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Information* IE, then:] + +- [FDD - The Node B shall configure the Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation in the new configuration according to TS 25.214 [10].] +- [FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the *Continuous Packet Connectivity HS-SCCH less Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If at least one of *HS-PDSCH Second Code Support* IE is set to "True", then the Node B shall include *HS-PDSCH Second Code Index* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE, then the Node B shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the *Continuous Packet Connectivity DRX Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *UE DTX DRX Offset* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall apply the indicated Offset in *UE DTX DRX Cycle* IE in the new configuration.] +- [1.28 Mcps TDD - If the *Enabling Delay* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *DRX Information To Modify* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.] +- [1.28 Mcps TDD - If the *Inactivity Threshold for UE DRX Cycle Ext* IE is included in the *Continuous Packet Connectivity DRX Information LCR* IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the *Enabling Delay Ext* IE is included in the *Continuous Packet Connectivity DRX Information To Modify LCR* IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION READY message.] + +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information LCR* IE, then:] + +- [1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall include *Allcoated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *Transport Block Size List* IE or/and *Repetition Period list* IE is/are included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall modify the configuration of Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall use this information to modify the buffer size for HS-DSCH Semi-Persistent scheduling operation.] +- [1.28 Mcps TDD - If the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall use this information to allocate the number of processes for HS-DSCH Semi-Persistent scheduling operation.] +- [1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent Resource Reservation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall include *Allcoated HS-PDSCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the *HS-DSCH Semi-Persistent scheduling operation Indicator* IE is included in the *HS-DSCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall apply this information for HS-DSCH Semi-Persistent scheduling operation.] + +- [1.28 Mcps TDD - If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the *Buffer Size for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [1.28 Mcps TDD - If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the *Number of Processes for HS-DSCH Semi-Persistent scheduling* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then:] + +- [1.28 Mcps TDD - If the *Repetition Period list* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, the Node B shall modify the configuration of Serving E-DCH Radio Link indicated by the *E-DCH Serving RL* IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].] + +[1.28 Mcps TDD - If the *E-DCH Semi-Persistent scheduling Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall apply this information for E-DCH Semi-Persistent scheduling operation.] + +- [1.28 Mcps TDD - If the *Semi-Persistent E-DCH releted E-HICH Information* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall use this information to modify the configuration of Semi-Persistent E-DCH releted E-HICH.] + +- [1.28 Mcps TDD - If the *E-DCH Semi-Persistent Resource Reservation Indicator* IE is included in the *E-DCH Semi-Persistent scheduling Information to modify LCR* IE, then the Node B shall include *Allocated E-DCH Semi-persistent resource* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the Node B shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Semi-Persistent scheduling Deactivate Indicator LCR* IE, then the Node B shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *MU-MIMO Information* IE, then:] + +- [1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the *MU-MIMO indicator* IE and shall include the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information* IE is included in the *MU-MIMO Information* IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].] +- [1.28 Mcps TDD - If the *Standalone Midamble Channel Information request* IE is included in the *MU-MIMO Information* IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message, else the Node B shall not include the *Standalone Midamble Channel Information* IE in the *MU-MIMO Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message]. + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *MU-MIMO Information To Reconfigure* IE, then:] + +- [1.28 Mcps TDD - If the choice of *MU-MIMO Information To Reconf* IE is "Modify", then the Node B shall use this information to modify the indicated MU-MIMO Information parameter in the new configuration.] +- [1.28 Mcps TDD - If the choice of *MU-MIMO Information To Reconf* IE is "Continue", then the Node B shall continue using the old configuration for MU-MIMO operation.] + +#### **[FDD - E-DPCH Handling]:** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DPCH Information* IE which contains the *E-TFCS Information* IE, the Node B shall use the *E-TFCS Information* IE for the E-DCH when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the uplink of the new configuration. If the *E-TFCS Information* IE contains the *E-DCH Minimum Set E-TFCI* IE the Node B shall use the value for the related resource allocation operation.] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-DPDCH Power Interpolation* IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the *E-DPDCH Power Interpolation* IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION REQUEST message.] + +[FDD - If the *E-TFCS Information* IE in the *E-DPCH Information* IE contains the *E-TFCI Boost Information* IE, the Node B shall use the information according to TS 25.214 [10]. If the *E-TFCI Boost Information* IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10] if the *E-DCH FDD Information* IE is included in the RADIO LINK RECONFIGURATION PREPARE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-DPCH Power Offset* IE, the Node B shall use the value when the new configuration is being used.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-RGCH 2-Index-Step Threshold* IE, the Node B shall use the value when the new configuration is being used.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *E-RGCH 3-Index-Step Threshold* IE, the Node B shall use the value when the new configuration is being used.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *HARQ Info for E-DCH* IE, the Node B shall use the value when the new configuration is being used.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an *E-DPCH Information* IE which contains the *Minimum Reduced E-DPDCH Gain Factor* IE, then the Node B shall use the value to determine the applicable minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. For the case the *Minimum Reduced E-DPDCH Gain Factor* IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].] + +#### [TDD - UL/DL CCTrCH Modification] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any *UL CCTrCH To Modify* IE or *DL CCTrCH To Modify* IE in the Radio Link(s), the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message.] + +[TDD - If the *UL CCTrCH To Modify* IE or *DL CCTrCH To Modify* IE includes *TFCS* IE and/or *Puncture Limit* IE, the Node B shall apply these as the new values, otherwise the old values specified for this CCTrCH are still applicable.] + +[1.28Mcps TDD - If the *UL CCTrCH To Modify* IE includes *UL SIR Target* IE, the Node B shall apply this value as the new configuration and use it for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21].] + +#### [TDD - UL/DL CCTrCH Deletion] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any *UL CCTrCH To Delete* IE or *DL CCTrCH To Delete* IE, the Node B shall not include this CCTrCH in the new configuration.] + +#### [FDD - UL CLTD Setup:] + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Setup", then: the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights according the new configuration defined in the *UL CLTD Information* IE and then:] + +- [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the *C-ID* IE shall be included in the *UL CLTD Information* IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] +- [FDD - If the *UL CLTD Activation Information* IE is included in the *UL CLTD Information* IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.] + +#### [FDD - UL CLTD Modification:] + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Configuration Change", then: the *UL CLTD Information To Modify* IE defines the new configuration and then:] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID* IE in the *UL CLTD Information To Modify* IE, then the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context. Otherwise the Node B shall configure the serving E-DCH cell or the HS-DSCH serving cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *S-DPCCH Power Offset Information* IE in the *UL CLTD Information To Modify* IE, then the Node B shall use this value to determine the S-DPCCH power.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UL CLTD Activation Information* IE in the *UL CLTD Information To Modify* IE, then the Node B shall use this value to update the local state of UL CLTD for the concerned Node B Communication Context. If the *UL CLTD Activation Information* IE is set to "De-activated", the Node B should release the F-TPICH resource configured for the concerned Node B Communication Context.] + +**[FDD - UL CLTD Removal:]** + +[FDD - If the *UL CLTD Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL CLTD* is "Removal", then the configured UL CLTD for the concerned Node B Communication Context shall be removed.] + +**[FDD - UL MIMO Setup:]** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UL MIMO Information* IE in the *E-DCH FDD Information* IE, or the *UL MIMO Reconfiguration* IE and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Setup", then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Serving E-DCH RL* IE indicating that the Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] + - [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-ROCH Power Offset* IE in the *UL MIMO Information* IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] +- [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence* IE in *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE and it should include it for the Serving E-DCH RL.] + +**[FDD – UL MIMO Modification:]** + +[FDD - If the *UL MIMO Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Configuration Change", then the *UL MIMO Information To Modify* IE defines the new configuration.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Serving E-DCH RL* IE:] + - [FDD – If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-ROCH resources of the old Serving E-DCH RL at the activation of the new configuration.] + - [FDD - If the new Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-ROCH Power Offset* IE in the *UL MIMO Information To Modify* IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.] +- [FDD - The Node B may include the the *Secondary Transport Block E-HICH Signature Sequence* IE or it may alternatively include the *Secondary Transport Block E-HICH Release Indicator* IE in *UL MIMO DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE and it should include it for the Serving E-DCH RL.] + +**[FDD - UL MIMO Removal:]** + +[FDD - If the *UL MIMO Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Removal", then the configured UL MIMO for the concerned Node B Communication Context shall be removed.] + +#### DL Power Control: + +- [FDD - If the *Radio Link Information* IE includes the *DL Reference Power* IE and the power balancing is active, the Node B shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported, using the *DL Reference Power* IE in the RADIO LINK RECONFIGURATION REQUEST message. The updated reference power shall be used from the next adjustment period.] + +[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Updated Indicator* IE in the *RL Information Response* IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### RL Information: + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *RL Information* IE, the Node B shall treat it as follows: + +- [FDD - If the *RL Information* IE includes the *Maximum DL Power* IE, the Node B shall apply this value to the new configuration and not transmit with a higher power on any Downlink DPCH or on the F-DPCH of the Radio Link once the new configuration is being used. During compressed mode, the $\delta P_{curr}$ , as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] +- [FDD - If the *RL Information* IE includes the *Minimum DL Power* IE, the Node B shall apply this value to the new configuration and never transmit with a lower power on any Downlink Channelisation Code or on the F-DPCH of the Radio Link once the new configuration is being used.] +- [3.84 Mcps TDD and 7.68Mcps TDD - If the *CCTrCH Maximum DL Transmission Power* IE and/or the *CCTrCH Minimum DL Transmission Power* IE are included, the Node B shall apply the values in the new configuration for this DCH type CCTrCH, if the *RL Information* IE includes *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values in the new configuration for all other DCH type CCTrCHs.] +- [3.84 Mcps TDD and 7.68Mcps TDD - The maximum power and minimum power for a DSCH type CCTrCH to be modified, shall be determined as follows: + - If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum and maximum power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs. + - If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum power, however, is subject to control by the CRNC via the frame protocol]. +- [1.28 Mcps TDD - If *Maximum DL Power* IE and/or *Minimum DL Power* IE are included within *DL Timeslot Information LCR* IE, the Node B shall apply the values in the new configuration for this timeslot within a DCH type CCTrCH, if the *RL Information* IE includes *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values in the new configuration for all other timeslots.] +- [1.28 Mcps TDD - If the *CCTrCH Maximum DL Transmission Power* IE and/or the *CCTrCH Minimum DL Transmission Power* IE are included, the Node B shall apply the values in the new configuration for this DSCH type CCTrCH, if the *RL Information* IE includes the *Maximum Downlink Power* and/or the *Minimum Downlink Power* IEs, the Node B shall apply the values in the new configuration for other timeslots.] +- [FDD - If the concerned Node B Communication Context is configured to use DPCH in the downlink and if the *RL Information* IE contains the *Transmission Gap Pattern Sequence Code Information* IE in the *DL Code Information* IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated whenever the downlink compressed mode method SF/2 is active in the new configuration.] +- [1.28Mcps TDD - If the *RL Information* IE contains the *Uplink Synchronisation Parameters LCR* IE, the Node B shall use the indicated values of *Uplink Synchronisation Stepsize* IE and *Uplink Synchronisation Frequency* IE when evaluating the timing of the UL synchronisation.] + +- [FDD - If the *RL Information* IE contains the *F-DPCH Slot Format* IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].] +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Setup", then the Node B shall use the information in *F-TPICH Information* IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214[10].] +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Configuration Change", then: the *F-TPICH Information To Modify* IE defines the new configuration and then:] + - [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Slot Format* IE, then the Node B shall use this information to configure the F-TPICH slot format according to TS 25.211 [7].] + - [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Offset* IE, the Node B shall use this information to configure the time offset of F-TPICH.] + - [FDD - If the *F-TPICH Information To Modify* IE includes the *F-TPICH Channelisation Code Number* IE, the Node B shall use this information to configure the channelization code of F-TPICH.] +- [FDD - If the *RL Information* IE includes the *F-TPICH Information Reconf* IE and the choice of *Setup, Configuration Change or Removal of F-TPICH Information* is "Removal", then the Node B shall remove the configured F-TPICH for the RL.] + +#### Signalling Bearer Re-arrangement: + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *Signalling Bearer Request Indicator* IE, the Node B shall allocate a new Communication Control Port for the control of the Node B Communication Context and include the *Target Communication Control Port ID* IE in the RADIO LINK RECONFIGURATION RESPONSE message. + +#### HS-DSCH Setup: + +If the *HS-DSCH Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then: + +- The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. +- The Node B shall include the *HARQ Memory Partitioning* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD - The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE or *MIMO with four transmit antennas Activation Indicator* IE, or *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Information* IE.] [1.28Mcps TDD- The *HARQ Memory Partitioning* IE shall either contain the *HARQ Memory Partitioning Information Extension For MIMO* IE or the *Number of Processes* IE set to a value higher than "8", if the *MIMO Activation Indicator* IE is included in the *HS-DSCH Information* IE.] +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. + +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION REQUEST message includes *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION REQUEST in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Measurement Power Offset* IE in the *HS-DSCH Information* IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SICH SIR Target* IE in the *HS-DSCH Information* IE, the Node B shall use this value to determine the HS-SICH SIR Target. The *HS-SICH SIR Target* IE indicates the received UL SIR target of HS-SICH NACK for this UE.] +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE in the *HS-DSCH Information* IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]). +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d PDU Size Format* IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] + - [FDD - If the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B may use:] + - [FDD - a different HS-SCCH in consecutive TTIs for this UE] + - [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE] + - t) - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE the Node B may use the supported HSDPA functions for this UE.] + - u) - [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH FDD Information* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] + - [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the *Number of Supported Carriers* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B shall use this information to allocate HSDPA resources over multiple frequencies for UE.] + - [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the *Multi-carrier HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B shall use this information together with the *HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE to allocate HSDPA resources over multiple carriers for the UE.] + - [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE, the Node B may use this information in HSDPA resources allocation for the UE.] + - [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information* IE, then the Node B shall , if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple frequencies and include the *HS-SCCH Specific Information Response LCR per UARFCN* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall include the *HARQ Memory Partitioning per UARFCN* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may indicate the number of multiple frequencies actually used by the UE and include the *Multi-Carrier number* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [1.28 Mcps TDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH TDD Information* IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +- If the RADIO LINK RECONFIGURATION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *Priority Queue Information* IE in the *HS-DSCH MAC-d Flows Information* IE in the *HS-DSCH Information* IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *CQI Feedback Cycle2 k* IE and the *CQI Cycle Switch Timer* IE is included in *HS-DSCH FDD Information* IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.] + +#### [FDD – Secondary Serving HS-DSCH Setup:] + +[FDD – If the *C-ID* IE is present in the *Additional HS Cell Information RL Reconf Req* IE in the RADIO LINK RECONFIGURATION REQUEST message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the Node B or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE or in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE for each instance of the *Additional HS Cell Information RL Reconf Req* IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:] + +- [FDD – The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the *HS-PDSCH RL ID* IE. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### Intra-Node B Serving HS-DSCH Radio Link Change: + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-PDSCH RL ID* IE, this indicates the new Serving HS-DSCH Radio Link: + +- The Node B shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new Serving HS-DSCH Radio Link. +- The Node B may include the *HARQ Memory Partitioning* IE in the [FDD - *HS-DSCH FDD Information Response* IE] [TDD - *HS-DSCH TDD Information Response* IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD - The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] [1.28Mcps TDD- The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Information Response* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - *HS-SCCH Specific Information Response* IE] [1.28Mcps TDD - *HS-SCCH Specific Information Response LCR* IE] [7.68Mcps TDD - *HS-SCCH Specific Information Response 7.68Mcps* IE] in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- If a reset of the MAC-hs is not required the Node B shall include the *MAC-hs Reset Indicator* IE in the RADIO LINK RECONFIGURATION RESPONSE message. +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify* IE and the value is set to "allowed" or if *HS-DSCH Information To Modify* IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### [FDD – Intra-Node B Secondary Serving HS-DSCH Radio Link Change:] + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID* IE and the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Req* IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the Node B and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the *Ordinal Number Of Frequency* IEs, in the *HS-DSCH FDD Secondary Serving Information* IE for each instance of the *Additional HS Cell Information RL Reconf Req* IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-Node B secondary serving HS-DSCH Radio Link change and, then the *HS-PDSCH RL ID* IE indicates the new secondary serving HS-DSCH Radio Link:] + +- [FDD - The Node B shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The Node B shall remove the old secondary serving HS-PDSCH Radio Link. Non cell specific secondary serving if no E-DCH resources are allocated to the RL. Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] +- [FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the *HS-SCCH Specific Secondary Serving Information Response* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify* IE and the value is set to "allowed" or if *HS-DSCH FDD Secondary Serving Information To Modify* IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the *HS-DSCH FDD Secondary Serving Information* IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link, and then:] + - [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SCCH Power Offset* IE in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] + - [FDD - If the *MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - If the *Single Stream MIMO Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] + - [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary + +serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Information* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] +- [FDD - If the *MIMO with four transmit antennas Activation Indicator* IE or the *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information* IE, then the Node B shall activate the MIMO with four transmit antennas mode or the Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +**[FDD - Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *C-ID* IE in the *Additional HS Cell Information RL Reconf Req* IE and an additional non serving E-DCH RL exists in the cell indicated by the *C-ID* IE, the *HS-PDSCH RL ID* IE in the *HS Cell Information RL Reconf Req* IE indicates the new Additional Serving E-DCH Radio Link.] - [FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] + +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – The Node B may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the *Additional Modified E-DCH FDD Information Response RL Reconf* IE in the *Additional E-DCH Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links on secondary UL frequency in the Node B.] + +**[FDD - Additional Serving E-DCH Radio Link Change to a new RL:]** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information RL Reconf Req* IE and the *C-ID* IE in the *Additional HS Cell Information RL Reconf Req* IE and there is no radio links in the cell indicated by the *C-ID* IE for the Node B Communication Context, the *HS-PDSCH RL ID* IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.] + +- [FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] +- [FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - The Node B may include in the *E-DCH FDD DL Control Channel Information IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION RESPONSE message the *Serving Grant Value IE* and *Primary/Secondary Grant Selector IE* for the initial grant for the additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2 IE*.] +- [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* in the *Additional E-DCH FDD Information Response IE* in the *Additional E-DCH Cell Information Response RL Reconf IE* in the RADIO LINK RECONFIGURATION RESPONSE message. ] + +#### HS-DSCH Modification: + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Information To ModifyUnsynchronised IE* and if the Serving HS-DSCH Radio Link is in the Node B, then: + +- The Node B shall include the *HS-DSCH Initial Capacity Allocation IE* for every HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the Node B allows the CRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size", then Node B shall only set in the *HS-DSCH Initial Capacity Allocation IE* the values for the peer of *Scheduling Priority Indicator IE* and *Maximum MAC-d PDU Size Extended IE* to the values of the corresponding peer for the Priority Queue of Node B Communication Context. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-hs Guaranteed Bit Rate IE* in the *HS-DSCH Information To ModifyUnsynchronised IE*, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer IE* for a Priority Queue in the *HS-DSCH Information To ModifyUnsynchronised IE*, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *ACK Power Offset IE*, the *NACK Power Offset IE* or the *CQI Power Offset IE* in the *HS-DSCH Information To ModifyUnsynchronised IE*, then the Node B shall use the indicated ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.] +- [FDD - If the *CQI Feedback Cycle2 k IE* or the *CQI Cycle Switch Timer IE* is included in *HS-DSCH Information To Modify IE*, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in the new configuration.] +- [FDD - If the *HS-SCCH Power Offset IE* is included in the *HS-DSCH Information To ModifyUnsynchronised IE*, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] +- [TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *TDD ACK NACK Power Offset IE* in the *HS-DSCH Information To ModifyUnsynchronised IE*, the Node B shall use the indicated power offset in the new configuration.] + +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SICH SIR Target* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B shall use this value to the SIR Target in the new configuration. The *HS-SICH SIR Target* IE indicates the received UL SIR target of HS-SICH NACK for this UE.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-SICH TPC step size* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B shall use this value to the HS-SICH TPC step size in the new configuration.] +- [1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the *Multi-carrier HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B shall use this information together with the *HS-DSCH Physical Layer Category* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify Unsynchronised* IE to allocate HSDPA resources over multiple carriers for the UE.] +- [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B may use this information in HSDPA resources allocation for the UE.] +- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Puncturing Handling in First Rate Matching Stage* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the *Puncturing Handling in First Rate Matching Stage* IE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Preamble Mode* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the *HARQ Preamble Mode* IE is not included or if the mode 0 is applied, then the Node B shall not include the *HARQ Preamble Mode Activation Indicator* IE in the *HS-DSCH Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Physical Layer Category* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B shall use this information in the new configuration and may include the *HARQ Memory Partitioning* IE in the RADIO LINK RECONFIGURATION RESPONSE message. The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.] +- [FDD - If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] + +- [FDD - Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.] +- [FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] +- [1.28Mcps TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Physical Layer Category* IE in the *HS-DSCH Information To Modify Unsynchronised* IE, the Node B shall use this information in the new configuration and may include the *HARQ Memory Partitioning* IE in the RADIO LINK RECONFIGURATION RESPONSE message. The *HARQ Memory Partitioning* IE may contain the *HARQ Memory Partitioning Information Extension For MIMO* IE.] +- [1.28Mcps TDD- If the *MIMO Mode Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE.] + - [1.28 Mcps TDD - If the *MIMO Mode Indicator* IE is set to "Activate", then the Node B shall decide the SF mode for HS-PDSCH dual stream and include the *MIMO SF Mode for HS-PDSCH dual stream* IE in the *HS-DSCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE the Node B may use the supported HSDPA functions for this UE.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Information To Modify* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *HS-DSCH FDD Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### [FDD – Secondary Serving HS-DSCH Modification:] + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE in the *Additional HS Cell Information RL Reconf Req* IE and if the Secondary Serving HS-DSCH Radio Link is in the Node B, then:] + +- [FDD - If the *HS-SCCH Power Offset* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] +- [FDD - If the *MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the MIMO mode for the the secondary serving HS-DSCH Radio Link in accordance with the *MIMO Mode Indicator* IE.] +- [FDD - If the *MIMO Mode Indicator* IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the *MIMO N/M Ratio* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Single Stream MIMO Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the *Single Stream MIMO Mode Indicator* IE.] +- [FDD - If the *Ordinal Number Of Frequency* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.] + +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the *SixtyfourQAM DL Usage Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE with value set to "not allowed", then the Node B shall not use 64 QAM for the Secondary Serving HS-DSCH Radio Link.] +- [FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the *HS-DSCH TB Size Table Indicator* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.] +- [FDD - If the *MIMO with four transmit antennas Mode Indicator* IE or the *Dual Stream MIMO with four transmit antennas Mode Indicator* IE is included in the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link in accordance with the *MIMO with four transmit antennas Mode Indicator* IE, or *Dual Stream MIMO with four transmit antennas Mode Indicator* IE.] +- [FDD - The Node B may include the *Precoder weight set restriction* IE in the *HS-DSCH FDD Secondary Serving Information Response* IE in the *Additional HS Cell Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### **[FDD – Secondary Serving HS-DSCH Removal:]** + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Secondary Serving Remove* IE in the *Additional HS Cell Information RL Reconf Req* IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.] + +#### **HS-DSCH MAC-d Flow Addition/Deletion:** + +If the RADIO LINK RECONFIGURATION REQUEST message includes any *HS-DSCH MAC-d Flows To Add* or *HS-DSCH MAC-d Flows To Delete* IEs and if the Serving HS-DSCH Radio Link is in the Node B, then the Node B shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed. + +If the RADIO LINK RECONFIGURATION REQUEST message includes an *HS-DSCH MAC-d Flows To Delete* IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the HS-DSCH configuration from the Node B Communication Context and release any existing HS-PDSCH resources. + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH MAC-d Flows To Add* IE and if the Serving HS-DSCH Radio Link is in the Node B, then: + +- The Node B shall include the *HS-DSCH Initial Capacity Allocation* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being added, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size" format for the HS-DSCH, then Node B shall only set in the *HS-DSCH Initial Capacity Allocation* IE the values for the peer of *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION REQUEST message in the *HS-DSCH MAC-d Flows To Add* IE for a Priority Queue including *Scheduling Priority Indicator* IE and *Maximum MAC-d PDU Size Extended* IE. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-hs Guaranteed Bit Rate* IE in the *HS-DSCH MAC-d Flows To Add* IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. + +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Discard Timer* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. +- If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, then the Node B shall ignore the *SID* IE and *MAC-d PDU Size* IE in the *MAC-d PDU Size Index* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related HSDPA Priority Queue. +- [FDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] +- If the RADIO LINK RECONFIGURATION REQUEST message includes *DL RLC PDU Size Format* IE for a Priority Queue in the in the *HS-DSCH MAC-d Flows To Add* IE, the *DL RLC PDU Size Format* IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24]. +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE for a Priority Queue in the *HS-DSCH MAC-d Flows To Add* IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] + +#### [FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Preconfiguration Setup* IE in the *RL Information* IE the Node B shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change according to TS 25.308 [49]: ] + +- [FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the *C-ID* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of *C-IDs* in the *HS-DSCH Preconfiguration Setup* IE part of the *RL Information* IE in the RADIO LINK RECONFIGURATION REQUEST message. ] +- [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ] + - [FDD – by the *Num Primary HS-SCCH Codes* IE in the *HS-DSCH Preconfiguration Setup* IE, for the primary serving HS-DSCH cell] + - [FDD – by the *Num Secondary HS-SCCH Codes* IE in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE for each of the secondary serving HS-DSCH cells] +- [FDD – If *Num Primary HS-SCCH Codes* IE or *Num Secondary HS-SCCH Codes* IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ] +- [FDD – The Node B shall return these codes in the *Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE of the RADIO LINK RECONFIGURATION RESPONSE message. ] +- [FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell's HS-SCCH codes in the *HS-SCCH Preconfigured Codes* IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18]. ] +- [FDD – The Node B shall include, in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message, IEs according to the rules defined for HS-DSCH Setup and: ] + - [FDD – if *HARQ Preamble Mode* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *HARQ Preamble Mode Activation Indicator* IE] + - [FDD – if *MIMO Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] + +- [FDD – if *Ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] +- [FDD – if *MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] +- [FDD – if *Dual Stream MIMO with four transmit antennas Activation Indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE or in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE the *MIMO N/M Ratio* IE] +- [FDD – if *Multiflow ordinal number of frequency* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE] +- [FDD – if *HS-DSCH MAC-d PDU Size Format* IE is included in the *HS-DSCH Preconfiguration Setup* IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration the *HS-DSCH TB Size Table Indicator* IE for each preconfigured cell] +- [FDD – if *Sixtyfour QAM Usage Allowed Indicator* IE is included in the *Secondary Cells* IE in the *HS-DSCH Preconfiguration Setup* IE or in the *HS-DSCH Preconfiguration Setup* IE the *SixtyfourQAM DL Usage Indicator* IE for each preconfigured cell] +- [FDD – if *Continuous Packet Connectivity HS-SCCH less Information* IE is included in the *HS-DSCH Preconfiguration Setup* IE the *Continuous Packet Connectivity HS-SCCH less Information Response* IE] +- [FDD – if the *UE with enhanced HS-SCCH support indicator* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B shall store this information in the preconfigured configuration. ] +- [FDD – if the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE, then the Node B may store this information in the preconfigured configuration.] +- [FDD - If the *UE Support Indicator Extension* IE is included in the *HS-DSCH Preconfiguration Setup* IE with the bit *UE DTXDRX related HS-SCCH orders uniform behavior indicator* set to 0, then the Node B shall, if supported, include the *Support of dynamic DTXDRX related HS-SCCH order* IE in the *Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – The Node B shall include in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] + - [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] + - [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *E-DCH Indicator* IE for a secondary cell, the Node B shall include in the *Additional E-DCH Preconfiguration Information* IE in the *HS-DSCH Preconfiguration Info* IE in the *RL Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message the *E-DCH FDD DL Control Channel Information* containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the *E-DCH Indicator* IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] + - [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE.] + - [FDD – The Node B may configure for the preconfigured configuration the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE for the initial grant for the serving Additional E-DCH RL and include these values in the *E-DCH FDD DL Control Channel Information* IE.] + +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *Multiflow Information* IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *F-TPICH Information* IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL CLTD Information* IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *UL MIMO Information* IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixteenQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.] +- [FDD – If the *HS-DSCH Preconfiguration Setup* IE includes the *SixtyfourQAM UL Operation Indicator* IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.] + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Non-Serving Preconfiguration Setup* IE in the *RL Information* IE and:] + +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE and/or *New non-serving RL E-DCH FDD DL Control Channel Information B* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE in the *Non-Serving RL Preconfiguration Info* IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – if the choice of *new Serving RL* is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the *New non-serving RL E-DCH FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* for the RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – if the *Additional E-DCH Non-Serving RL Preconfiguration Setup* IE is included, the Node B may include the *New non-serving E-DCH RL FDD DL Control Channel Information A* IE, the *New non-serving RL E-DCH FDD DL Control Channel Information B* IE and/or the *New non-serving RL E-DCH FDD DL Control Channel Information C* IE according to the choice of *new Serving RL* in *Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information* IE for the additional non serving E-DCH RL in the *Non-Serving RL Preconfiguration Info* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – If the *F-TPICH Information* IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].] + +#### [FDD – Enhanced HS Serving Cell Change:] + +[FDD - Upon receipt of the RADIO LINK RECONFIGURATION REQUEST message, if the Enhanced HS Serving Cell Change is preconfigured in the Node B for the Node B Communication Context, the Node B may execute the Enhanced HS Serving Cell Change procedure according to TS 25.308 [49]] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Enhanced HS Serving CC Abort* IE in the *HS-DSCH Information To Modify Unsynchronised* IE or the *HS-DSCH FDD Information* IE then the Node B shall not execute the unsynchronized Enhanced HS Serving Cell Change procedure when performing the Intra-Node B Serving HS-DSCH Radio Link Change or, at inter Node B radio link change, the HS-DSCH Setup. ] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *No of Target Cell HS-SCCH Order* IE then the Node B shall repeat the Target Cell HS-SCCH Order on the HS-SCCH the number of times defined in the IE. ] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Non-Serving RL Preconfiguration Removal* IE, the Node B shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.] + +#### [FDD - Multiflow Setup]: + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Multiflow Information* IE in *HS-DSCH FDD Information* IE, or it includes the *Multiflow Reconfiguration* IE in *HS-DSCH FDD Information To Modify Unsynchronized* IE and the choice of *Setup or Change or Stop* is “Setup”, then the Node B shall setup the requested Multiflow operation and then:] + +- [FDD – Use *Total number of HS-DSCH cells* IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] +- [FDD – Use *Role* IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – Use *MIMO* IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If *Timing* IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B* IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors* IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.] + +#### [FDD - Multiflow Modification]: + +[FDD - If the *Multiflow Reconfiguration* IE is present in *HS-DSCH Information To Modify Unsynchronized* IE the RADIO LINK RECONFIGURATION REQUEST message, and the choice of *Setup or Change or Stop* is “Change”, then the Node B shall use new configuration as follows:] + +- [FDD – If the *Total number of HS-DSCH cells* IE is included, then apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.] +- [FDD – If the *Role* IE is included, then all the Multiflow cells configured at this Node B are assisting ones, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.] +- [FDD – If the *MIMO* IE is included, then decide whether to apply the MIMO HS-DPCCH format at the physical layer.] +- [FDD – If the *Timing* IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.] +- [FDD – If the *Max number of HS-SCCH sets per Node B* IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.] +- [FDD – If the *Assisting Repetition Factors* IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration] + +#### [FDD - Multiflow Removal]: + +[FDD - If the *Multiflow Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, and the choice of *Setup or Change or Stop* is “Stop”, then the Node B shall terminate the Multiflow operation.] + +#### [FDD - E-DCH Setup]: + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message:] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH Logical Channel information* IE in the *E-DCH MAC-d Flows Information* IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH Information* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).] +- [FDD - If the *TNL QoS* IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Reference Power Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UPH Filtering Measurement Forwarding Request* IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Serving E-DCH RL* IE:] + - [FDD - the Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the serving E-DCH RL.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the serving E-DCH RL.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then + +the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DPCH Information* IE which contains the *HS-DSCH Configured Indicator* IE and/or the *Maximum Set of E-DPDCHs* IE, and/or the *Puncture Limit* IE and/or the *E-TTI* IE, the Node B shall use and apply the value(s) in the new configuration.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] +- [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH FDD Information* IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] + +#### [FDD - E-DCH Radio Link Handling:] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH RL Indication* IE in the *RL Information* IE:] + +- [FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B communication context, on the Radio Links indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - The Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the *E-DCH RL Indication* IE, set to "E-DCH", in the *RL Information* IE.] +- [FDD - The Node B shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the *E-DCH RL Indication* set to "Non E-DCH".] +- [FDD - For each RL for which the *E-DCH RL Indication* IE is set to "E-DCH", and which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the *E-DCH RL Set ID* IE in the RADIO LINK RECONFIGURATION RESPONSE message. The value of the *E-DCH RL Set ID* IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] + +#### [FDD - Serving E-DCH Radio Link Change:] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Serving E-DCH RL* IE, this indicates the new Serving E-DCH Radio Link:] + +- [FDD - If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link.] +- [FDD - If the New Serving E-DCH RL is in this Node B:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the new serving E-DCH RL.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - The Node B may include the *Default Serving Grant in DTX Cycle 2* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the new serving E-DCH RL.] + - [FDD - The Node B may include the *E-RGCH/E-HICH Channelisation Code* IE and/or the *E-HICH Signature Sequence* IE and/or the *E-RGCH Signature Sequence* IE or may alternatively include the *E-RGCH Release Indicator* IE in the *E-DCH FDD DL Control Channel Information* IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links in the Node B.] + +#### [FDD - E-DCH Modification:] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information To Modify* IE, then:] + +- [FDD - If the *E-DCH FDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH HARQ Power Offset FDD* IE in the *E-DCH FDD Information To Modify* IE for an E-DCH MAC-d flow the Node B shall use this information for calculating the unquantised gain factor for an E-TFC ( $\beta_{ed,j,uq}$ ) as defined in TS 25.214 [10].] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the E-DCH Grant Type and it is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant* IE, if included, for the related resource allocation operation.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the Node B shall use this information to add/delete the + +indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Logical Channel To Modify* IE, the Node B shall use this information to modify the indicated logical channels:] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Guaranteed Bit Rate* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes *E-DCH DDI Value* IE, the Node B shall apply the values in the new configuration.] + - [FDD - If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the Node B shall apply the value in the new configuration.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Bundling Mode Indicator* IE for an E-DCH MAC-d flow in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH FDD Information To Modify* IE and the *Bundling Mode Indicator* IE is set to "Bundling" and the *E-TTI* IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Reference Power Offset* IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Power Offsetfor Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-AGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-RGCH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-HICH Power Offset* IE in the *RL Specific E-DCH Information* IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *SixteenQAM UL Operation Indicator* IE in the *E-DCH FDD Information To Modify* IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the *SixteenQAM UL Operation Indicator* IE.] +- [FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH DL Control Channel Grant Information* IE in the *E-DCH FDD Information To Modify* IE, the Node B may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the *E-DCH RL ID* IE. The Node B shall then report the modified configuration which is used in the new configuration specified in the *E-DCH FDD DL Control Channel Information* IE for each E-DCH RL in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Fast TTI switching Mode Requested UnSynchronized* IE in the *E-DCH FDD Information To Modify* IE and Mode 1 is indicated, the Node B shall if supported send the HS-SCCH order to execute the TTI switching process according to TS 25.214 [10]]. +- [FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the *Fast TTI switching Mode Requested UnSynchronized* IE in the *E-DCH FDD Information To Modify* IE and Mode 2 is indicated, the Node B shall if supported send the HS-SCCH order at the CFN indicated in Mode 2 to execute the TTI switching process according to TS 25.214 [10]]. + +#### [FDD - E-DCH MAC-d Flow Addition/Deletion:] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended* IE for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information* IE in the *E-DCH MAC-d Flows To Add* IE, then the Node B shall ignore the *MAC-d PDU Size* IE in the *MAC-d PDU Size List* IE and use *Maximum MAC-d PDU Size Extended* IE to optimise capacity allocation for the related E-DCH Logical Channel.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete* IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flows To Add* IE, then:] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate* IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall use this information to optimise MAC-e scheduling decisions.] +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *UE Aggregate Maximum Bit Rate Enforcement Indicator* IE in the *E-DCH Logical Channel Information* IE in the *E-DCH MAC-d Flows To Add* IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] + +#### [FDD – Additional E-DCH Setup:] + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Setup", then: the *Additional E-DCH Cell Information Setup* IE defines the new configuration and then:] + +- [FDD - If the *C-ID* IE is included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *C-ID* IE indicates the cell in which the additional E-DCH shall be setup.] +- [FDD - The Node B shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the *E-DCH Additional RL ID* IE and the *C-ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *C-ID* IE is not included in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the *E-DCH Additional RL ID* IE indicates the existing RL on which the additional E-DCH shall be setup.] +- [FDD - The Node B shall setup the additional E-DCH on the Radio Links indicated by the *E-DCH Additional RL ID* IE in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.] +- [FDD - The Node B shall, if supported, use the *Dual Cell E-DCH Operation Enhancements Information* IE for the Secondary uplink frequency if it is included in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE.] +- [FDD - If the *DL Power Balancing Information* IE and/or the *Minimum Reduced E-DPDCH Gain Factor* IE are present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Secondary UL Frequency Activation State* is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH FDD Setup Information* IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] +- [FDD - If the *F-DPCH Slot Format* IE is present in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Primary CPICH Usage For Channel Estimation* IE, the *Secondary CPICH Information*, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE and/or the *E-HICH Power Offset* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Setup* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE, the *E-DCH Maximum Bitrate* IE, the *E-DCH Minimum Set E-TFCI* IE, the *E-DCH Processing Overload Level* IE, the *Implicit Grant handling* IE, the *Minimum TEBS threshold* IE and/or the *DTX Information2* IE are present in the *Additional E-DCH FDD Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message the same value. This value shall uniquely identify the RL + +Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] + +- [FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Setup* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the Additional Serving E-DCH Radio Link is configured in the Node B, then:] + - [FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + - [FDD - The Node B may include the *Serving Grant Value* IE and *Primary/Secondary Grant Selector* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the *Default Serving Grant in DTX Cycle 2* IE.] + - [FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE and include the new/changed configuration in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### [FDD – Additional E-DCH Configuration Change] + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Configuration Change", then: the *Additional E-DCH Cell Information Configuration Change* IE defines the new configuration and then] + +- [FDD - If the *UL Scrambling Code* IE and/or the *UL SIR Target* IE are present in the *UL DPCH Information* IE in the *Additional E-DCH Configuration Change Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Minimum Reduced E-DPDCH Gain Factor* IE is present in the *Multicell E-DCH Information* IE in the *Additional E-DCH Configuration Change Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *F-DPCH Information* IE is present in the *Additional E-DCH Configuration Change Information* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *Dual Cell E-DCH Operation Enhancements Information* IE is present in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH Configuration Change Information* IE, the Node B shall, if supported, use the information for the Secondary uplink frequency.] + +[FDD – Additional E-DCH RL Addition:] + +[FDD - If the *Additional E-DCH RL Specific Information To Add* IE is present in the *Additional E-DCH Configuration Change Information* IE, then:] + +- [FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B Communication Context, on the Radio Links indicated by the *E-DCH Additional RL ID* IE. Non + +cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] + +- [FDD - If the *Initial DL Transmission Power* IE, the *Maximum DL Power* IE, the *Minimum DL Power* IE and/or the *F-DPCH Slot Format* IE are present in the *Additional E-DCH RL Specific Information To Add* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *DL Reference Power* IE, the *E-AGCH Power Offset* IE, the *E-RGCH PowerOffset* IE, and/or the *E-HICH Power Offset* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Add* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION REQUEST message includes the *DL Reference Power* IE, the Node B shall activate the power balancing and use the *DL Reference Power* IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION RESPONSE message is supported, according to subclause 8.3.7. In this case, the Node B shall include the *DL Power Balancing Activation Indicator* IE in the *E-DCH Additional RL Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. $P_{init}$ shall be set to the power level indicated by the *Initial DL Transmission Power* IE (if received) in the *Additional E-DCH RL Specific Information To Add* IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DCH RLs.] +- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] +- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the *RL Set ID* IE included in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] +- [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the *E-DCH RL Set ID* IE for the Additional E-DCH RL in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - For every additional E-DCH RL indicated in the *Additional E-DCH RL Specific Information To Add* IE in the *Additional E-DCH FDD Setup Information* IE the Node B may include the *E-AGCH And E-RGCH/E-HICH FDD Scrambling Code* IE and shall include the *E-RGCH/E-HICH Channelisation Code* IE and the corresponding *E-HICH Signature Sequence* IE and the Node B may include the corresponding *E-RGCH Signature Sequence* IE for each Additional E-DCH RL in the *E-DCH FDD DL Control Channel Information* IE in the *Additional E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response IE RL Reconf* in the RADIO LINK RECONFIGURATION RESPONSE message.] + +**[FDD – Additional E-DCH RL Modification:]** + +[FDD - If the *Additional E-DCH RL Specific Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then the RL indicated by the *E-DCH Additional RL ID* IE indicates the RL on which E-DCH resources shall be modified:] + +- [FDD - If the *Maximum DL Power* IE, the *Minimum DL Power* IE, and/or the F-DPCH Slot Format IE are present in the *Additional E-DCH RL Specific Information To Modify* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If the *DL Reference Power* IE, the *Primary CPICH Usage For Channel Estimation* IE, the *Secondary CPICH Information Change* IE, the *E-AGCH Power Offset* IE, the *E-RGCH Power Offset* IE, the *E-HICH Power Offset* IE and/or the *E-DCH DL Control Channel Grant* IE are present in the *Multicell E-DCH RL Specific Information* IE in the *Additional E-DCH RL Specific Information To Modify* IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] +- [FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the *DL Power Balancing Updated Indicator* IE in the *Additional Modified E-DCH FDD Information Response* IE in the *Additional E-DCH Cell Information Response RL Reconf* IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### [FDD – Additional E-DCH Modification:] + +[FDD - If the *Additional E-DCH FDD Information To Modify* IE is present in the *Additional E-DCH Configuration Change Information* IE, then:] + +- [FDD - If the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE and/or the *E-DCH Minimum Set E-TFCI* IE is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *E-DCH Maximum Bitrate* IE is included, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [FDD - If the *E-DCH Processing Overload Level* IE is included, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [FDD - If the Additional E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the *HARQ Process Allocation For 2ms Scheduled Transmission Grant* IE in the *Additional Modified E-DCH FDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [FDD - If the *DTX Information2* IE is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *Implicit Grant handling* IE is included, the Node B shall use this information for the related resource allocation operation.] +- [FDD - If the *Minimum TEBS threshold* IE is included, the Node B shall use this information for the related resource allocation operation.] + +#### [FDD – Additional E-DCH Removal] + +[FDD - If the *Additional E-DCH Cell Information RL Reconf Req* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency* is "Removal", then the additional E-DCH on the secondary uplink frequency shall be removed.] + +#### [FDD – E-DCH decoupling operation] + +[FDD – If the *E-DCH Decoupling Indication* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then the Node B shall if supported use this indication for the E-DCH decoupling operation.] + +**[FDD – Radio Links without DPCH/F-DPCH operation]** + +[FDD – If the *Radio Links without DPCH/F-DPCH Indication* IE is present in the RADIO LINK RECONFIGURATION REQUEST message:] + +- [FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.] + +**[FDD - UL DPCCH2 Setup:]** + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Setup", then:] + +- [FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].] +- [FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.] +- [FDD – If the *UL DPCCH2 Reconfiguration* IE includes the *Extended E-DPCCH Power Offset* IE, the concerned Node B shall use the value when the new configuration is being used.] + +**[FDD – UL DPCCH2 Modification:]** + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Configuration Change", then: the *UL DPCCH2 Information To Modify* IE defines the new configuration and then:] + +- [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *F-DPCH info* IE in the *UL DPCCH2 Information To Modify* IE and if the serving HS-DSCH RL is in the Node B, then the Node B shall use this value to update the second F-DPCH for the concerned Node B Communication Context.] +- [FDD – If the *UL DPCCH2 Reconfiguration* IE includes the *Extended E-DPCCH Power Offset* IE, the concerned Node B shall use the value when the new configuration is being used.] + +**[FDD - UL DPCCH2 Removal:]** + +[FDD - If the *UL DPCCH2 Reconfiguration* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Removal", then the configured UL DPCCH2 for the concerned Node B Communication Context shall be removed.] + +**[FDD – Downlink TPC enhancements Setup:]** + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Setup", then:] + +- [FDD – The NodeB shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Radio Link Information* is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCH Cell Information Setup* is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +**[FDD –Downlink TPC enhancements Modification:]** + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Configuration Change", then: the *Downlink TPC enhancements Information To Modify* IE defines the new configuration and then:] + +- [FDD - The NodeB shall, if supported, use the *Decimation factor for primary frequency* IE and/or the *Decimation factor for secondary frequency* IE to reconfigure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Radio Link Information* is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +[FDD - If the *TPC slot position* in the *Additional E-DCH Cell Information Configuration Change* is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.] + +#### **[FDD - Downlink TPC enhancements Removal:]** + +[FDD - If the *Downlink TPC enhancements Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Removal", then the configured power control Algorithm 3 for the concerned Node B Communication Context shall be removed.] + +#### **[TDD - Intra-Node B Serving E-DCH Radio Link Change:]** + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH Serving RL* IE, this indicates the new Serving E-DCH Radio Link:] + +- [TDD - In the new configuration the Node B shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.] +- [TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - and E-HICH parameter] corresponding to the E-DCH and include the *E-AGCH Specific Information Response TDD* IE [1.28Mcps TDD - and *E-HICH Specific Information Response TDD* IE] in the *E-DCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] +- [TDD - If the *TNL QoS* IE is included for a MAC-d flow and if ALCAP is not used, the *TNL QoS* IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.] + +#### **[TDD - E-PUCH Handling:]** + +[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-PUCH Information* IE, the Node B shall apply the parameters to the new configuration.] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-PUCH Information LCR* IE, the Node B shall apply the parameters to the new configuration.] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-TFCS Information TDD* IE, the Node B shall apply the beta parameters to the new configuration.] + +[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the *E-AGCH TPC step size* IE configured in *E-PUCH Information LCR* IE in the *E-DCH Information 1.28Mcps* IE.] + +#### **[3.84Mcps TDD - E-DCH Setup:]** + +[3.84Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information* IE and *E-DCH Non-scheduled Grant Information TDD* IE if there are to be non-scheduled grants.] + +#### **[1.28Mcps TDD - E-DCH Setup:]** + +[1.28Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL* IE, *E-PUCH Information LCR* IE, *E-TFCS Information TDD* IE, *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information LCR* IE and *E-DCH Non-scheduled Grant Information LCR TDD* IE if there are to be non-scheduled grants.] + +[1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message + +includes the *UE TS0 Capability LCR IE* in the *E-DCH TDD Information LCR IE*, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] + +#### **[7.68Mcps TDD - E-DCH Setup]:** + +[7.68Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: *E-DCH Serving RL IE*, *E-PUCH Information IE*, *E-TFCS Information TDD IE*, *E-DCH MAC-d Flows to Add IE*, *E-DCH TDD Information 7.68Mcps IE* and *E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE* if there are to be non-scheduled grants.] + +#### **[TDD - E-DCH MAC-d Flow Addition/Deletion]:** + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any *E-DCH MAC-d Flows To Add* or *E-DCH MAC-d Flows To Delete* IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Maximum MAC-d PDU Size Extended IE* for a E-DCH Logical Channel in the *E-DCH MAC-d Flows Information IE* in the *E-DCH MAC-d Flows To Add IE*, then the Node B shall ignore the *MAC-d PDU Size IE* in the *MAC-d PDU Size List IE* and use *Maximum MAC-d PDU Size Extended IE* to optimise capacity allocation for the related E-DCH Logical Channel.] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete IE* requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an *E-DCH MAC-d Flows To Delete IE* requesting the deletion of all remaining non-scheduled E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the non-scheduled E-DCH configuration from the Node B Communication Context and release the non-scheduled E-DCH resources [1.28 Mcps TDD - and the related Signature Sequence of the Non-scheduled E-HICH].] + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH MAC-d Flows To Add IE*, then if the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Guaranteed Bit Rate IE* in the *E-DCH MAC-d Flows To Add IE*, the Node B shall use this information to optimise MAC-e scheduling decisions.] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *MAC-es Maximum Bit Rate LCR IE* in the *E-DCH Logical Channel Information IE* in the *E-DCH MAC-d Flows To Add IE*, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] + +#### **[3.84Mcps TDD - E-DCH Non-scheduled allocations]:** + +[3.84Mcps TDD - If the *E-DCH Non-scheduled Grant Information TDD IE* is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +#### **[1.28Mcps TDD - E-DCH Non-scheduled allocations]:** + +[1.28Mcps TDD - If the *E-DCH Non-scheduled Grant Information LCR TDD IE* is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +#### **[7.68Mcps TDD - E-DCH Non-scheduled allocations]:** + +[7.68Mcps TDD - If the *E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE* is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.] + +#### **[TDD - E-DCH Modification]:** + +[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the [3.84Mcps TDD - *E-DCH TDD Information IE*] [1.28Mcps TDD - *E-DCH TDD Information LCR IE*] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps IE*], then:] + +- [3.84Mcps TDD - If the *E-DCH TDD Information* IE includes the *E-DCH TDD Maximum Bitrate* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR* IE includes the *E-DCH Physical Layer Category LCR* IE or *Extended E-DCH Physical Layer Category LCR* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [7.68Mcps TDD - If the *E-DCH TDD Information 7.68Mcps* IE includes the *E-DCH TDD Maximum Bitrate 7.68Mcps* IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the [3.84Mcps TDD - *E-DCH TDD Information* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE] includes the *E-DCH Processing Overload Level* IE, then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the *E-DCH Processing Overload Level* IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.] +- [TDD - If the [3.84Mcps TDD - *E-DCH TDD Information* IE] [1.28Mcps TDD - *E-DCH TDD Information LCR* IE] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps* IE] includes the *E-DCH Power Offset for Scheduling Info* IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR* IE includes the *Maximum Number of Retransmission for Scheduling Info LCR* IE and the *E-DCH Retransmission timer for Scheduling Info LCR* IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] +- [1.28Mcps TDD - If the *E-DCH TDD Information LCR* IE includes the *Multi-Carrier E-DCH Physical Layer Category LCR* IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.][TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH TDD Information To Modify* IE, then:] + - [TDD - If the *E-DCH TDD Information To Modify* IE contains a *E-DCH MAC-d Flow Specific Information* IE which includes the *Allocation/Retention Priority* IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] + - [TDD - If the *E-DCH TDD Information To Modify* IE message includes the *Maximum Number of Retransmissions for E-DCH* IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.] + - [1.28Mcps TDD - If the *E-DCH TDD Information To Modify* IE message includes the *E-DCH MAC-d Flow Retransmission Timer* IE for an E-DCH MAC-d flow then the Node B shall use this information to set the retransmissions timer.] + - [TDD - If the *E-DCH TDD Information To Modify* IE message includes the *E-DCH HARQ Power Offset TDD* IE for an E-DCH MAC-d flow the Node B shall use this new power offset value.] + - [TDD - If the *E-DCH TDD Information To Modify* IE includes the *E-DCH MAC-d Flow Multiplexing List* IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.] + - [TDD - If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Grant Type* IE, the Node B shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.] + - [TDD - If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Add* or *E-DCH Logical Channel To Delete* IEs, the Node B shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.] + - [TDD - If the *E-DCH TDD Information To Modify* IE includes the *E-DCH Logical Channel To Modify* IE, the Node B shall use this information to modify the indicated logical channels:] + - [TDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Priority Indicator* IE, the Node B shall apply the values in the new configuration.] + - [TDD - If the *E-DCH Logical Channel To Modify* IE includes *Scheduling Information* IE, the Node B shall apply the values in the new configuration.] + +- [TDD - If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Guaranteed Bit Rate* IE, the Node B shall apply the values in the new configuration.] +- [1.28Mcps TDD - If the *E-DCH Logical Channel To Modify* IE includes *MAC-es Maximum Bit Rate LCR* IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] +- [TDD - If the *E-DCH Logical Channel To Modify* IE includes *E-DCH DDI Value* IE, the Node B shall apply the values in the new configuration.] +- [TDD - If the *E-DCH Logical Channel To Modify* IE includes the *Maximum MAC-d PDU Size Extended* IE, the Node B shall apply the value in the new configuration.] +- [TDD - If the *E-DCH TDD Information To Modify* IE includes the *MAC-e Reset Indicator* IE in the *E-DCH TDD Information To Modify* IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.] +- [1.28Mcps TDD - If the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information To Modify* IE is not present, or if the *UE TS0 Capability LCR* IE in the *UE Capabilities Information* IE in the *HS-DSCH Information* IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the *UE TS0 Capability LCR* IE in the *E-DCH TDD Information to Modify* IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].] + +#### [1.28Mcps TDD - Power Control GAP:] + +[1.28Mcps TDD - If the *Power Control GAP* IE is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].] + +#### [1.28Mcps TDD - E-UTRAN Inter-RAT measurement:] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Idle Interval Information* IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to TS 25.331 [18].] + +#### [1.28Mcps TDD - HS-DSCH-RNTI for FACH:] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH-RNTI for FACH* IE, if supported, the Node B shall store this information and include the *E-RNTI for FACH* IE in the RADIO LINK RECONFIGURATION RESPONSE message.] + +#### [1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Measurement occasion pattern sequence parameters* IE in the *DCH Measurement Occasion Information* IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] + +#### [1.28Mcps TDD –Multi-Carrier E-DCH Continue:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.] + +#### [1.28Mcps TDD – Multi-Carrier E-DCH Setup:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Setup", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:] + +- [1.28Mcps TDD - The Node B shall use the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE to decide the transport bearer mode in the new configuration.] +- [1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] + +### [1.28Mcps TDD – Multi-Carrier E-DCH Change:] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Change", then the *Multi-Carrier E-DCH Information LCR* IE defines the new configuration and then:] + +- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is different from current configured frequencies, then the Node B shall setup the E-DCH resources, as requested in the Node B Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] +- [1.28Mcps TDD - If the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE is the same as any current configured frequency, then the Node B shall reconfigure the E-DCH resources, as requested or as configured in the Node B Communication Context, on the uplink frequencies indicated by the *UARFCN* IE in the *Multi-Carrier E-DCH Information LCR* IE.] + +[1.28Mcps TDD - If the *Multi-Carrier E-DCH Information Reconf* IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of *Continue, Setup or Change* is "Change" and the *Removal UL Multi-Carrier info* IE is included, then the Node B shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the *UARFCN* IE in the *Removal UL Multi-Carrier info* IE.] + +### [1.28Mcps TDD – Non-rectangular resource operation:] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *UE support of non-rectangular resource allocation* IE, the Node B shall, if supported, use this information to determine whether includes the *Non-rectangular resource allocation indicator* IE and the *Non-rectangular resource timeslot set* IE or not.] + +## General + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Layer Address* IE and *Binding ID* IEs in the *HS-DSCH Information* IE, *HS-DSCH Information To Modify Unsynchronised* IE, *HS-DSCH MAC-d Flows To Add* IE, [FDD - *RL Specific E-DCH Information* IE] [TDD - *E-DCH MAC-d Flows to Add* IE, *E-DCH TDD Information to Modify* IE] or in the *RL Specific DCH Information* IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] being added or any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. + +If the requested modifications are allowed by the Node B, the Node B has successfully allocated the required resources, and changed to the new configuration, it shall respond to the CRNC with the RADIO LINK RECONFIGURATION RESPONSE message. + +The Node B shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Transport Layer Address* IE and the *Binding ID* IE for any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included], or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included], being added or any Transport Channel [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] or MAC-d flow [FDD - for which the *Transport Bearer Not Requested Indicator* IE was not included] being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE. The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [16], subclause 5.10.1 and in TS 25.435 [24], subclause 5.8.3. + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer shall not be Established" for a DCH or an E-DCH MAC-d flow being added, then the Node B shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE set to "Transport Bearer may not be Established" for a DCH or an E-DCH MAC-d flow being added and:] + +- [FDD - if the Node B establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include in the RADIO LINK RECONFIGURATION RESPONSE message the *Binding ID* IE and + +*Transport Layer Address* IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.] + +- [FDD - if the Node B does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include the *Transport Bearer Not Setup Indicator* IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.] + +In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iub interface, the *Transport Layer Address* IE and the *Binding ID* IE in the *DCH Information Response* IE shall be included only for one of the DCH [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] in the set of coordinated DCHs. + +In the case of a Radio Link being combined with another Radio Link within the Node B, the *Transport Layer Address* IE and the *Binding ID* IE [FDD - for which the *Transport Bearer Not Requested Indicator* IE is not included] in the *DCH Information Response* IE shall be included only for one of the combined Radio Links. + +[FDD - In the case of an E-DCH RL being combined with another E-DCH RL within the Node B, the *E-DCH FDD Information Response* IE shall be included only for one of the combined E-DCH RLs.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Additional E-DCH Cell Information RL Reconf Req* IE, then:] + +- [FDD - if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] +- [FDD - if the *Multicell E-DCH Transport Bearer Mode* IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] +- [FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:] + - [FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Not Requested Indicator* IE in the *E-DCH MAC-d Flow Specific Information* IE in the *E-DCH MAC-d Flows Information* IE in the *E-DCH FDD Information* IE and/or the *Transport Bearer Request Indicator* IE in the *E-DCH FDD Information To Modify* IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] + - [FDD - If the *Transport Layer Address* IE and *Binding ID* IE is included for an E-DCH MAC-d flow in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information* IE in the *Additional E-DCH FDD Setup Information* IE in the *Additional E-DCH Cell Information Setup* IE or in the *Additional E-DCH MAC-d Flows Specific Information* IE in the *Additional E-DCH FDD Information To Modify* IE in the *Additional E-DCH Configuration Change Information* IE in the *Additional E-DCH Cell Information Configuration Change* IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION RESPONSE message the *Binding ID* IE and *Transport Layer Address* IE in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional E-DCH FDD Information Response* IE and/or and/or include the *Binding ID* IE and *Transport Layer Address* IE for the E-DCH MAC-d flow has been modified in the *Additional E-DCH MAC-d Flow Specific Information Response* IE in the *Additional Modified E-DCH FDD Information Response* IE.] + +[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Multi-Carrier E-DCH Information Reconf* IE, then:] + +- [1.28Mcps TDD - If the *Multi-carrier E-DCH Transport Bearer Mode LCR* IE is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] + +- [1.28Mcps TDD - If the *Multi-Carrier E-DCH Transport Bearer Mode LCR* IE is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.] +- [1.28Mcps TDD - If the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Setup" and the Separate Iub transport bearer mode is used in the new configuration, or if the choice of *Continue, Setup or Change* in the the *Multi-Carrier E-DCH Information Reconf* IE is "Change" and the Transport Bearer Mode is changed to "Separate Iub Transport Bearer Mode" indicated by *Multi-carrier E-DCH Transport Bearer Mode LCR* IE, then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *Multi-Carrier E-DCH Information Response LCR* IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] +- [1.28Mcps TDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the *Transport Bearer Request Indicator* IE in the *E-DCH TDD Information to Modify* IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.] +- [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the *Transport Bearer Request Indicator* IE is set to " Bearer Requested ", then the Node B shall include the *Binding ID* IE and *Transport Layer Address* IE in the *E-DCH TDD Information Response* IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] + +In the case of a signalling bearer re-arrangement, the new Communication Control Port shall be used once the Node B has sent the RADIO LINK RECONFIGURATION RESPONSE message via the old Communication Control Port. + +### 8.3.5.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful radio link reconfiguration procedure between CRNC and Node B.](2e9c6c1583e99f58d7fbf0c354855f4c_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: Unsuccessful Operation + CRNC->>Node B: RADIO LINK RECONFIGURATION REQUEST + Node B-->>CRNC: RADIO LINK RECONFIGURATION FAILURE + +``` + +The diagram illustrates a sequence of messages between a CRNC and Node B. It starts with the CRNC sending a 'RADIO LINK RECONFIGURATION REQUEST' message to Node B. Node B responds with a 'RADIO LINK RECONFIGURATION FAILURE' message, indicating that the operation was unsuccessful. + +Sequence diagram showing an unsuccessful radio link reconfiguration procedure between CRNC and Node B. + +**Figure 35: Unsynchronised Radio Link Reconfiguration procedure, Unsuccessful Operation** + +If the Node B cannot allocate the necessary resources for all the new DCHs of one set of co-ordinated DCHs requested to be set-up, it shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed. + +If the requested Unsynchronised Radio Link Reconfiguration procedure fails for one or more Radio Link(s), the Node B shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC, indicating the reason for failure. + +Typical cause values are as follows: + +#### Radio Network Layer Cause + +- CM not supported +- [FDD - Continuous Packet Connectivity DTX-DRX operation not available] +- [FDD - Continuous Packet Connectivity UE DTX Cycle not available] +- [FDD - MIMO not available] +- E-DCH MAC-d PDU Size Format not available +- [FDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD - Multi Cell operation not available.] +- [1.28Mcps TDD - MIMO not available] + +- [1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available] +- [FDD – Single Stream MIMO not available] +- [FDD - Multi Cell operation with MIMO not available] +- [FDD - Multi Cell operation with Single Stream MIMO not available] +- [FDD - Multi Cell E-DCH operation not available] +- [FDD - UL CLTD operation not available] +- [FDD - MIMO with four transmit antennas not available] +- [FDD - Dual Stream MIMO with four transmit antennas not available] +- [FDD – Multiflow operation not available] +- [FDD - SixtyfourQAM UL operation not available] +- [FDD – UL MIMO operation not available] +- [FDD – UL MIMO and SixteenQAM operation not available] +- [FDD – UL MIMO and SixtyfourQAM operation not available] +- [FDD – E-DCH decoupling operation not available] +- [FDD – Radio Links without DPCH/F-DPCH operation not available] +- [FDD – UL DPCCH2 operation not available] +- [FDD – Downlink TPC enhancements operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available] +- [FDD – Dual Cell E-DCH operation enhancements with different TTI operation not available] + +#### Transport Layer Cause + +- Transport Resources Unavailable + +#### Miscellaneous Cause + +- O&M Intervention +- Control processing overload +- HW failure + +### 8.3.5.4 Abnormal Conditions + +If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC. + +[FDD - If the concerned Node B Communication Context is configured to use DPCH in the downlink and if the *RL Information* IE contains the *DL Code Information* IE and this IE includes *DL Scrambling Code* and *FDD DL Channelisation Code Number* IEs not matching the DL Channelisation code(s) already allocated to the Radio Link identified by *RL ID* IE, then the Node B shall consider the Unsynchronised Radio Link Reconfiguration procedure as having failed and it shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.] + +If more than one DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the *QE-Selector* IE set to "selected"], the Node B shall regard the Unsynchronised Radio Link Reconfiguration Preparation procedure as failed and shall respond with a RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message includes a *DCHs To Modify* IE or *DCHs To Add* IE with multiple *DCH Specific Info* IEs, and if the DCHs in the *DCHs To Modify* IE or *DCHs To Add* IE do not have the same *Transmission Time Interval* IE in the *Semi-Static Transport Format Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the *RL Information* IE includes the *DL Reference Power* IEs, but the power balancing is not active in the indicated RL(s), the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and the Node B shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".] + +[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s) but the *RL Information* IE includes more than one *DL Reference Power* IEs, the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and the Node B shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".] + +If the RADIO LINK RECONFIGURATION REQUEST message contains the *Transport Layer Address* IE or the *Binding ID* IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the *Transport Bearer Request Indicator* IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE or *HS-DSCH MAC-d Flows To Delete* IE in addition to the *HS-DSCH Information* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information To Modify* IE, *HS-DSCH MAC-d Flows To Add* IE, *HS-DSCH MAC-d Flows To Delete* IE or *HS-PDSCH RL ID* IE and the Serving HS-DSCH Radio Link is not in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH Information* IE and does not include the *HS-PDSCH RL-ID* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-PDSCH RL-ID* IE indicating a Radio Link not existing in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *HS-DSCH Information* IE, *HS-DSCH Information To Modify* IE, or *HS-DSCH MAC-d Flows To Add* IE and if in the new configuration the Priority Queues associated with the same *HS-DSCH MAC-d Flow ID* IE have the same *Scheduling Priority Indicator* IE value, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Indexed MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Fixed MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *HS-DSCH Information* IE and if the *Measurement Power Offset* IE is not present, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION REQUEST message includes *HS-DSCH Information* IE and the HS-DSCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the concerned Node B Communication Context is configured to use F-DPCH in the downlink and if the *RL Information* IE contains the *DL Code Information* IE, then the Node B shall consider the Unsynchronised Radio Link Reconfiguration procedure as having failed and it shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.] + +[FDD - If the *E-DCH FDD Information* IE is present in the RADIO LINK RECONFIGURATION REQUEST message, but the *E-DPCH Information* IE is not present, or if any of the *Maximum Set of E-DPDCHs* IE, *Puncture Limit* IE, *E-TFCS Information* IE, *E-TTI* IE, *E-DPCCH Power Offset* IE, *E-RGCH 2-Index-Step Threshold* IE, *E-RGCH 3-Index-Step Threshold* IE, *HARQ Info for E-DCH* IE or *HS-DSCH Configured Indicator* IE are not present in the *E-DPCH Information* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If any of the *HS-DSCH Configured Indicator* IE, of the *Maximum Set of E-DPDCHs* IE, *Puncture Limit* IE or *E-TTI* IE are present in the *E-DPCH Information* IE and the *E-DCH FDD Information* IE is not present in the RADIO LINK RECONFIGURATION REQUEST message, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes one of the *Not Used* IEs, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH RL Indication* IE set to "E-DCH", but no *E-DCH FDD Information* IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information* IE but no *E-DCH RL Indication* IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the RADIO LINK RECONFIGURATION REQUEST message does not contain the *E-DCH Decoupling Indication* IE but contains the *HS-PDSCH RL ID* IE and/or the *Serving E-DCH RL* IE, and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *HS-PDSCH RL ID* IE and the *E-DPCH Information* IE which includes the *HS-DSCH Configured Indicator* IE set as "HS-DSCH not configured" then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *E-DCH FDD Information To Modify* IE, *E-DCH MAC-d Flows To Add* IE or *E-DCH MAC-d Flows To Delete* IE in addition to the *E-DCH FDD Information* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains any of the *E-DCH FDD Information To Modify* IE, *E-DCH MAC-d Flows To Add* IE, *E-DCH MAC-d Flows To Delete* IE and the Node B Communication Context is not configured for E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *E-DCH FDD Information To Modify* IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes *E-DCH FDD Information* IE and the E-DCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[TDD - if the radio link was not previously configured to support E-DCH, then if the RADIO LINK RECONFIGURATION REQUEST message includes one of the following E-DCH information elements then it shall contain all of them otherwise the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.: *E-DCH Serving RL IE*, [3.84Mcps TDD and 7.68Mcps - *E-PUCH Information IE*, *E-TFCS Information TDD IE*], [1.28Mcps TDD - *E-PUCH Information LCR IE*, *E-TFCS Information TDD IE*], *E-DCH MAC-d Flows to Add IE*, and [3.84Mcps TDD - *E-DCH TDD Information IE*] [1.28Mcps TDD - *E-DCH TDD Information LCR IE*] [7.68Mcps TDD - *E-DCH TDD Information 7.68Mcps IE*.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* in addition to the *Continuous Packet Connectivity DTX-DRX Information To Modify IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE* in addition to the *Continuous Packet Connectivity HS-SCCH less Information IE*, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. ] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE* while the Continuous Packet Connectivity HS-SCCH less configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* while the Continuous Packet Connectivity DTX-DRX configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *DRX Information To Modify IE* in *Continuous Packet Connectivity DTX-DRX Information To Modify IE* while the Continuous Packet Connectivity DRX configuration isn't configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If the *DCHs to Modify IE* contains a *DCH Specific Info IE* which includes the *Unidirectional DCH Indicator IE* set to "Uplink DCH only" but no *Transport Format Set IE* for the uplink for this DCH and the Node B had ignored the configuration of Transport Format Set for uplink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If the *DCHs to Modify IE* contains a *DCH Specific Info IE* which includes the *Unidirectional DCH Indicator IE* set to "Downlink DCH only" but no *Transport Format Set IE* for the downlink for this DCH and the Node B had ignored the configuration of Transport Format Set for downlink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Transport Bearer Not Requested Indicator IE* for a DCH but does not contain the corresponding *DCH ID IE* and the *Unidirectional DCH indicator IE* set to "Uplink DCH only" for the DCH in *DCH Information To Add IE*, the Node B shall reject the procedure using the the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply MIMO, allowed to apply 64 QAM, establish the secondary serving HS-DSCH Radio Link, or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator IE* for a DCH in the *RL Specific DCH Information IE* but does not include the *DCH ID IE* for the DCH in the *DCHs to Add IE*, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the *Continuous Packet Connectivity DTX-DRX Information IE* but the concerned Node B Communication Context is not previously configured to use F- + +DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the Transport Bearer is not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *Transport Bearer Not Requested Indicator* IE for a DCH for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION REQUEST message does not include the *Transport Layer Address* IE and the *Binding ID* IE for the DCH, the E-DCH MAC-d flow and/or HS-DSCH MAC-d flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *HS-DSCH Semi-Persistent scheduling Information to Modify LCR* IE in addition to the *HS-DSCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the *E-DCH Semi-Persistent scheduling Information to Modify LCR* IE in addition to the *E-DCH Semi-Persistent scheduling Information LCR* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size" for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +If, in the new configuration, the concerned Node B Communication Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the *HS-DSCH FDD Secondary Serving Information* IE but does not contain the *C-ID* IE in the *Additional HS Cell Information RL Reconf Prep* IE or the message includes the *C-ID* IE but does not contain the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Prep* IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains a *MIMO Activation Indicator* IE and a *Single Stream MIMO Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Req* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a *MIMO Activation Indicator* IE, a *Single Stream MIMO Activation Indicator* IE, a *MIMO with four transmit antennas Activation Indicator* IE, a *Dual Stream MIMO with four transmit antennas Activation Indicator* IE in the *HS-DSCH FDD Information* IE or in the *HS-DSCH FDD Secondary Serving Information* IE in the *Additional HS Cell Information RL Reconf Req* IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the concerned Node B Communication Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH Cell Information RL Reconf Req* IE and if the *E-DPCH Information* IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH Cell Information RL Reconf Req* IE and there exist a logical channel for which the *Maximum MAC-d PDU Size Extended IE* in the *E-DCH MAC-d Flows Information IE* in the *E-DCH FDD Information IE* is not present, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional E-DCH RL Specific Information To Setup IE* in the *Additional E-DCH FDD Setup Information IE* in the *Additional E-DCH Cell Information Setup IE* in the *Additional E-DCH Cell Information RL Reconf Req* IE and the *C-ID IE* is not included but the Radio Link indicated by the *E-DCH Additional RL ID IE* is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional HS Cell Information RL Reconf Req* IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1" which are previously assigned to the RL or received in the *Ordinal Number Of Frequency IE* in the *HS-DSCH FDD Secondary Serving Information IE* or the *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE*, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Additional HS Cell Information RL Reconf Req* IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *UL CLTD Information IE* but does not contain the *F-TPICH Information IE*, or if it contains *HS-DSCH Preconfiguration Setup IE* with *UL CLTD Information IE* but without *F-TPICH Information IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *UL MIMO Reconfiguration IE* in *E-DCH FDD Information IE*, and the choice of *Setup, Configuration Change or Removal of UL MIMO* is "Setup", or if it contains *HS-DSCH Preconfiguration Setup IE* with *UL MIMO Information IE* but without *UL CLTD Information IE*, but the *UL CLTD Information IE* is not present and is not previously configured, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a *MIMO Activation Indicator IE*, a *MIMO with four transmit antennas Activation Indicator IE*, a *Dual Stream MIMO with four transmit antennas Activation Indicator IE* in *HS-DSCH Preconfiguration Setup IE* or in the *Secondary Cells IE* in the *HS-DSCH Preconfiguration Setup IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the *Fast TTI switching Mode Requested Synchronized IE* in the *E-DCH FDD Information To Modify IE*, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured but the *Dual Cell E-DCH Operation Enhancements Information IE* is not included in the RADIO LINK RECONFIGURATION REQUEST message, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured and if the *Continuous Packet Connectivity DTX-DRX Information IE* is included in the RADIO LINK RECONFIGURATION REQUEST message, but the *DTX Information IE* does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured but the *DTX Information To Modify IE*, if included in the *Continuous Packet Connectivity DTX-DRX Information To Modify IE* in the RADIO LINK RECONFIGURATION REQUEST message and the choice is "Modify", does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +[FDD - If the Dual Cell E-DCH operation enhancements configuration is setup or configured and if the DTX related Information is not signalled but the currently used value is not from the set of values defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] + +## 8.3.6 Radio Link Deletion + +### 8.3.6.1 General + +The Radio Link Deletion procedure is used to release the resources in a Node B for one or more established radio links towards a UE. + +The Radio Link Deletion procedure may be initiated by the CRNC at any time when the Node B Communication Context exists. + +### 8.3.6.2 Successful Operation + +![Sequence diagram showing the successful operation of the Radio Link Deletion procedure. The CRNC sends a RADIO LINK DELETION REQUEST message to the Node B, and the Node B responds with a RADIO LINK DELETION RESPONSE message.](099af350ac41fa6901be8b5be0091f8c_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: Radio Link Deletion procedure, Successful Operation + CRNC->>Node B: RADIO LINK DELETION REQUEST + Node B-->>CRNC: RADIO LINK DELETION RESPONSE + +``` + +Sequence diagram showing the successful operation of the Radio Link Deletion procedure. The CRNC sends a RADIO LINK DELETION REQUEST message to the Node B, and the Node B responds with a RADIO LINK DELETION RESPONSE message. + +**Figure 36: Radio Link Deletion procedure, Successful Operation** + +The procedure is initiated with a RADIO LINK DELETION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context. + +Upon receipt of this message, the Node B shall delete the radio link(s) identified by the *RL ID IE*, *Node B Communication Context ID IE* and *CRNC Communication Context ID IE* and release all associated resources and respond to the CRNC with a RADIO LINK DELETION RESPONSE message. + +[FDD - After deletion of the RL(s), the UL out-of-sync algorithm defined in ref. TS 25.214 [10] shall for each of the remaining RL Set(s) use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE that are configured in the cells supporting the radio links of the RL Set and the UL in-sync algorithm defined in ref. TS 25.214 [10] shall for each of the remaining RL Set(s) use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.] + +[FDD – If the RL indicated by the *RL ID IE* in the RADIO LINK DELETION REQUEST message is the serving HS-DSCH Radio link and a related secondary serving HS-DSCH Radio Link exists in the Node B, the Node B shall delete the secondary serving HS-DSCH Radio Link.] + +[FDD – If the RL indicated by the *RL ID IE* in the RADIO LINK DELETION REQUEST message is the secondary serving HS-DSCH Radio link, the Node B shall delete the secondary serving HS-DSCH Radio Link.] + +### 8.3.6.3 Unsuccessful Operation + +- + +### 8.3.6.4 Abnormal Conditions + +If the RL indicated by the *RL ID IE*, *Node B Communication Context ID IE* and *CRNC Communication Context ID IE* does not exist, the Node B shall respond with the RADIO LINK DELETION RESPONSE message and use the *CRNC Communication Context ID IE* received in the RADIO LINK DELETION REQUEST message. + +## 8.3.7 Downlink Power Control [FDD] + +### 8.3.7.1 General + +The purpose of this procedure is to balance the DL transmission powers of one or more Radio Links used for the related UE-UTRAN connection within the Node B. The Downlink Power Control procedure may be initiated by the CRNC at + +any time when the Node B Communication Context exists, irrespective of other ongoing CRNC initiated dedicated NBAP procedures towards this Node B Communication Context. The only exception occurs when the CRNC has requested the deletion of the last RL via this Node B, in which case the Downlink Power Control procedure shall no longer be initiated. + +### 8.3.7.2 Successful Operation + +![Diagram showing the Downlink Power Control procedure, Successful Operation. A horizontal arrow labeled 'DL POWER CONTROL REQUEST' points from 'CRNC' on the left to 'Node B' on the right.](e80b1f0d2748dacbe9d5fc551da02feb_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: DL POWER CONTROL REQUEST + CRNC->>Node B: DL POWER CONTROL REQUEST + +``` + +Diagram showing the Downlink Power Control procedure, Successful Operation. A horizontal arrow labeled 'DL POWER CONTROL REQUEST' points from 'CRNC' on the left to 'Node B' on the right. + +**Figure 37: Downlink Power Control procedure, Successful Operation** + +The procedure is initiated by the CRNC sending a DL POWER CONTROL REQUEST message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context. + +The *Power Adjustment Type* IE defines the characteristic of the power adjustment. + +If the value of the *Power Adjustment Type* IE is "Common", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Common". As long as the Power Balancing Adjustment Type of the Node B Communication Context is set to "Common", the Node B shall perform the power adjustment (see below) for all existing and future radio links associated with the context identified by the *Node B Communication Context ID* IE and use a common DL reference power level. + +If the value of the *Power Adjustment Type* IE is "Individual", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Individual". The Node B shall perform the power adjustment (see below) for all radio links addressed in the message using the given DL Reference Powers per RL. If the Power Balancing Adjustment Type of the Node B Communication Context was set to "Common" before this message was received, power balancing on all radio links not addressed by the DL POWER CONTROL REQUEST message shall remain to be executed in accordance with the existing power balancing parameters which are now considered RL individual parameters. Power balancing will not be started on future radio links without a specific request. + +If the value of the *Power Adjustment Type* IE is "None", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "None" and the Node B shall suspend on going power adjustments for all radio links for the Node B Communication Context. + +If the *Inner Loop DL PC Status* IE is present and set to "Active", the Node B shall activate inner loop DL power control for all radio links for the Node B Communication Context. If the *Inner Loop DL PC Status* IE is present and set to "Inactive", the Node B shall deactivate inner loop DL power control for all radio links for the Node B Communication Context according to ref. TS 25.214 [10]. + +#### Power Adjustment + +The power balancing adjustment shall be superimposed on the inner loop power control adjustment (see ref. TS 25.214 [10]) if activated. The power balancing adjustment shall be such that: + +with an accuracy of $\pm 0.5$ dB + +where the sum is performed over an adjustment period corresponding to a number of frames equal to the value of the *Adjustment Period* IE, $P_{ref}$ is the value of the *DL Reference Power* IE, $P_{p-CPICH}$ is the power used on the primary CPICH, $P_{mit}$ is the code power of the last slot of the previous adjustment period and $r$ is given by the *Adjustment Ratio* IE. If the last slot of the previous adjustment period is within a transmission gap due to compressed mode, $P_{mit}$ shall be set to the same value as the code power of the slot just before the transmission gap. + +The adjustment within one adjustment period shall in any case be performed with the constraints given by the *Max Adjustment Step* IE and the DL TX power range set by the CRNC. + +The power adjustments shall be started at the first slot of a frame with CFN modulo the value of *Adjustment Period* IE equal to 0 and shall be repeated for every adjustment period and shall be restarted at the first slot of a frame with CFN=0, until a new DL POWER CONTROL REQUEST message is received or the RL is deleted. + +### 8.3.7.3 Abnormal Conditions + +- + +## 8.3.8 Dedicated Measurement Initiation + +### 8.3.8.1 General + +This procedure is used by a CRNC to request the initiation of measurements on dedicated resources in a Node B. + +The Dedicated Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1 except when the *Node B Communication Context ID* IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC". + +If the *Node B Communication Context ID* IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC", the Dedicated Measurement Initiation procedure may be initiated by the CRNC at any time when the Node B Communication Context exists. + +### 8.3.8.2 Successful Operation + +![Sequence diagram showing the Dedicated Measurement Initiation procedure between CRNC and Node B. The CRNC sends a DEDICATED MEASUREMENT INITIATION REQUEST message to Node B, and Node B responds with a DEDICATED MEASUREMENT INITIATION RESPONSE message.](667b755d2a359d7b9a54cfceac78350a_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + Note right of Node B: Node B + CRNC->>Node B: DEDICATED MEASUREMENT INITIATION REQUEST + Node B-->>CRNC: DEDICATED MEASUREMENT INITIATION RESPONSE + +``` + +Sequence diagram showing the Dedicated Measurement Initiation procedure between CRNC and Node B. The CRNC sends a DEDICATED MEASUREMENT INITIATION REQUEST message to Node B, and Node B responds with a DEDICATED MEASUREMENT INITIATION RESPONSE message. + +**Figure 38: Dedicated Measurement Initiation procedure, Successful Operation** + +The procedure is initiated with a DEDICATED MEASUREMENT INITIATION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the Node B Communication Context. + +Upon reception, the Node B shall initiate the requested measurement according to the parameters given in the DEDICATED MEASUREMENT INITIATION REQUEST message. Unless specified below the meaning of the parameters are given in other specifications. + +If the *Node B Communication Context ID* IE equals the reserved value "All NBCC", this measurement request shall apply for all current and future Node B Communication Contexts controlled via the Communication Control Port on which the DEDICATED MEASUREMENT INITIATION REQUEST message was received. Otherwise, this measurement request shall apply for the requested Node B Communication Context ID only. + +If the *Node B Communication Context ID* IE equals the reserved value "All NBCC", the measurement request shall be treated as a single measurement, despite applying to multiple contexts. This means that it may only be terminated or failed on "All NBCC". + +If the *Node B Communication Context ID* IE equals the reserved value "All NBCC", the measurement shall be initiated only for those Node B Communication Contexts handling a mode (FDD, 3.84Mcps TDD, 7.68Mcps TDD or 1.28Mcps TDD) for which the concerned measurement is specified in TS 25.215 [4] and TS 25.225 [5]. The initiation of the measurement for a Node B Communication Context may be delayed until the Reconfiguration CFN has elapsed if either a Prepared Reconfiguration exists or a Prepared Reconfiguration no longer exists but the Reconfiguration CFN has not yet elapsed. + +If the Dedicated Measurement Object Type is indicated as being "RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all indicated Radio Links. + +[FDD - If the Dedicated Measurement Object Type is indicated as being "RLS" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all indicated Radio Link Sets.] + +[FDD - If the Dedicated Measurement Object Type is indicated as being "ALL RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all current and future Radio Links within the Node B Communication Context.] + +[TDD - If the Dedicated Measurement Object Type is indicated as being "ALL RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for one existing DPCH per CCTrCH in each used time slot of current and future Radio Links within the Node B Communication Context, provided the measurement type is applicable to the respective DPCH.] + +[FDD - If the Dedicated Measurement Object Type is indicated as being "ALL RLS" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all existing and future Radio Link Sets within the Node B Communication Context.] + +[TDD - If the *DPCH ID* IE or *DPCH ID 7.68Mcps* IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually. If no *DPCH ID* IE, *HS-SICH ID* IE, *DPCH ID 7.68Mcps* IE and no *PUSCH Information* IE is provided within the RL Information, the measurement request shall apply for one existing physical channel per CCTrCH in each used time slot of the Radio Link, provided the measurement type is applicable to this physical channel.] + +[TDD - If the *PUSCH Information* IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.] + +[TDD - If the *HS-SICH Information* IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.] + +[TDD - If the *Dedicated Measurement Type* IE is set to "HS-SICH reception quality ", the Node B shall initiate measurements of the failed, missed and total HS-SICH transmissions on all of the HS-SICH assigned to this Node B Communication Context. If either the failed or missed HS-SICH transmission satisfies the requested report characteristics, the Node B shall report the result of both failed and missed transmission measurements along with the total number of transmissions.] + +If the *CFN Reporting Indicator* IE is set to "FN Reporting Required", the *CFN* IE shall be included in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message, the latter only in the case the *Report Characteristics* IE is set to "On Demand". The reported CFN shall be the CFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). + +[FDD - If the *Number Of Reported Cell Portions* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the value shall be used to determine how many *Cell Portion ID* IEs and *SIR Value* IEs shall be included in *Best Cell Portions* IE in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message.] + +[1.28Mcps TDD - If the *Number Of Reported Cell Portions LCR* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the value shall be used to determine how many *Cell Portion LCR ID* IEs and *RSCP Value* IEs shall be included in *Best Cell Portions LCR* IE in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message. + +[1.28Mcps TDD - If the *Dedicated Measurement Type* IE is set to "AOA per Cell Portion LCR", the Node B shall initiate measurements of the Angle Of Arrival LCR for all Best CELL Portions in the CELL.] + +### Report characteristics + +The *Report Characteristics* IE indicates how the reporting of the measurement shall be performed. See also Annex B. + +If the *Report Characteristics* IE is set to "On Demand" and if the *CFN* IE is not provided, the Node B shall return the result of the measurement immediately. If the *CFN* IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). + +If the *Report Characteristics* IE is set to "Periodic", the Node B shall periodically initiate the Dedicated Measurement Report procedure for this measurement, with the requested report frequency. If the *CFN* IE is provided, it indicates the frame for which the first measurement value of a periodic reporting shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). + +If the *Report Characteristics* IE is set to "Event A", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero for the hysteresis time. + +If the *Report Characteristics* IE is set to "Event B", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero for the hysteresis time. + +If the *Report Characteristics* IE is set to "Event C", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next C event reporting for the same measurement cannot be initiated before the rising time specified by the *Measurement Change Time* IE has elapsed since the previous event reporting. + +If the *Report Characteristics* IE is set to "Event D", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next D event reporting for the same measurement cannot be initiated before the falling time specified by the *Measurement Change Time* IE has elapsed since the previous event reporting. + +If the *Report Characteristics* IE is set to "Event E", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the *Report Periodicity* IE is provided, the Node B shall also initiate the Dedicated Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity falls below the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Dedicated Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the Node B shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. + +If the *Report Characteristics* IE is set to "Event F", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the *Report Periodicity* IE is provided, the Node B shall also initiate the Dedicated Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity rises above the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Dedicated Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the *Measurement Threshold 2* IE is not present, the Node B shall use the value of the *Measurement Threshold 1* IE instead. If the *Measurement Hysteresis Time* IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. + +If the *Report Characteristics* IE is set to "On Modification" and if the *SFN* IE is not provided, the Node B shall report the result of the requested measurement immediately. If the *SFN* IE is provided, it indicates the frame for which the measurement value shall be provided. Then, the Node B shall initiate the Dedicated Measurement Reporting procedure in accordance to the following conditions: + +1. If the *Dedicated Measurement Type* IE is set to "Best Cell Portions LCR": + - The Node B shall initiate the Dedicated Measurement Reporting procedure when the Dedicated Measurement Value "Best Cell Portions LCR" changes. + +If the *Report Characteristics* IE is not set to "On Demand", the Node B is required to perform reporting for a dedicated measurement object, in accordance with the conditions provided in the DEDICATED MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no dedicated measurement object for which a measurement is defined exists anymore, the Node B shall terminate the measurement locally, i.e. without reporting this to the CRNC. + +If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the Node B shall initiate the Dedicated Measurement Reporting procedure immediately, and then continue with the measurements as specified in the DEDICATED MEASUREMENT INITIATION REQUEST message. + +**Higher layer filtering** + +The *Measurement Filter Coefficient* IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting. + +The averaging shall be performed according to the following formula. + +The variables in the formula are defined as follows + +$F_n$ is the updated filtered measurement result + +$F_{n-1}$ is the old filtered measurement result + +$M_n$ is the latest received measurement result from physical layer measurements, the unit used for $M_n$ is the same unit as the reported unit in the DEDICATED MEASUREMENT INITIATION RESPONSE, DEDICATED MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for $F_n$ ) + +$a = 1/2^{(k/2)}$ , where $k$ is the parameter received in the *Measurement Filter Coefficient* IE. If the *Measurement Filter Coefficient* IE is not present, $a$ shall be set to 1 (no filtering) + +In order to initialise the averaging filter, $F_0$ is set to $M_1$ when the first measurement result from the physical layer measurement is received. + +#### Measurement Recovery Behavior: + +If the *Measurement Recovery Behavior* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B shall, if Measurement Recovery Behavior is supported, include the *Measurement Recovery Support Indicator* IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.3.9.2. + +#### Response message + +If the Node B was able to initiate the measurement requested by the CRNC, it shall respond with the DEDICATED MEASUREMENT INITIATION RESPONSE message using the Communication Control Port assigned to the Node B Communication Context. The message shall include the same Measurement ID that was used in the measurement request. The DEDICATED MEASUREMENT INITIATION RESPONSE message shall be sent even if the initiation is delayed for some Node B Communication Contexts due to an existing Prepared Reconfiguration or that the Reconfiguration CFN has not yet elapsed. + +Only in the case where the *Report Characteristics* IE is set to "On Demand", the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the *Dedicated Measurement Object Type* IE containing the measurement result. [TDD - In the case that the measurement was performed on a particular HS-SICH, the Node B shall include the *HS-SICH ID* IE that indicates which HS-SICH was measured.] + +In the case where the *Node B Communication Context ID* IE is set to "All NBCC", the *CRNC Communication Context ID* IE in the DEDICATED MEASUREMENT INITIATION RESPONSE shall be set to the value "All CRNCCC", which is reserved for this purpose. + +[FDD - If the *Alternative Format Reporting Indicator* IE is set to "Alternative format is allowed" in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B may include the *Extended Round Trip Time* IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message.] + +#### Interaction with Reset Procedure: + +If a measurement has been requested with the *Node B Communication Context ID* IE set to "All NBCC", the Node B shall terminate the measurement locally if either the CRNC or the Node B initiates the Reset procedure for the relevant Communication Control Port or the entire Node B. + +### 8.3.8.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Dedicated Measurement Initiation procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B, labeled 'DEDICATED MEASUREMENT INITIATION REQUEST'. A return horizontal arrow points from Node B back to CRNC, labeled 'DEDICATED MEASUREMENT INITIATION FAILURE'.](e2fd964b19c1159de4d15785eb8af621_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: Request measurement + CRNC->>Node B: DEDICATED MEASUREMENT INITIATION REQUEST + Note right of Node B: Failure + Node B-->>CRNC: DEDICATED MEASUREMENT INITIATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Dedicated Measurement Initiation procedure. The diagram shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B, labeled 'DEDICATED MEASUREMENT INITIATION REQUEST'. A return horizontal arrow points from Node B back to CRNC, labeled 'DEDICATED MEASUREMENT INITIATION FAILURE'. + +**Figure 39: Dedicated Measurement Initiation procedure: Unsuccessful Operation** + +If the requested measurement cannot be initiated, the Node B shall send a DEDICATED MEASUREMENT INITIATION FAILURE message using the Communication Control Port assigned to the Node B Communication Context. The message shall include the same Measurement ID that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +In the case where the *Node B Communication Context ID* IE is set to "All NBCC" the *CRNC Communication Context ID* IE in the DEDICATED MEASUREMENT INITIATION FAILURE shall be set to the value "All CRNCCC", which is reserved for this purpose. + +Typical cause values are as follows: + +#### **Radio Network Layer cause** + +- Measurement not supported for the object +- Measurement Temporarily not Available + +#### **Miscellaneous Cause** + +- O&M Intervention +- Control processing overload +- HW failure + +### **8.3.8.4 Abnormal Conditions** + +The allowed combinations of the Dedicated Measurement Type and Report Characteristics Type are shown in the table below marked with "X". For not allowed combinations, the Node B shall regard the Dedicated Measurement Initiation procedure as failed. + +**Table 4: Allowed Dedicated Measurement Type and Report Characteristics Type combinations** + +| Dedicated Measurement Type | Report Characteristics Type | | | | | | | | | +|---------------------------------------|-----------------------------|----------|---------|---------|---------|---------|---------|---------|-----------------| +| | On Demand | Periodic | Event A | Event B | Event C | Event D | Event E | Event F | On Modification | +| SIR | X | X | X | X | X | X | X | X | | +| SIR Error | X | X | X | X | X | X | X | X | | +| Transmitted Code Power | X | X | X | X | X | X | X | X | | +| RSCP | X | X | X | X | X | X | X | X | | +| Rx Timing Deviation | X | X | X | X | | | X | X | | +| Round Trip Time | X | X | X | X | X | X | X | X | | +| Rx Timing Deviation LCR | X | X | X | X | | | X | X | | +| HS-SICH reception quality | X | X | X | X | | | X | X | | +| Best Cell Portions | X | X | | | | | | | | +| Angle Of Arrival LCR | X | X | | | | | | | | +| Rx Timing Deviation 7.68Mcps | X | X | X | X | | | X | X | | +| Rx Timing Deviation 3.84Mcps Extended | X | X | X | X | | | X | X | | +| Best Cell Portions LCR | X | X | | | | | | | X | +| AOA per Cell Portion LCR | X | X | | | | | | | | +| UE transmission power headroom | X | X | | X | | | | X | | +| DL transport block size | X | X | | | | | | | | + +If the Dedicated Measurement Type received in the *Dedicated Measurement Type* IE is not defined in ref. TS 25.215 [4] or TS 25.225 [5] to be measured on the Dedicated Measurement Object Type received in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Dedicated Measurement Initiation procedure as failed. + +If the *CFN* IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message and the *Report Characteristics* IE is other than "Periodic" or "On Demand", the Node B shall regard the Dedicated Measurement Initiation procedure as failed. + +### 8.3.9 Dedicated Measurement Reporting + +#### 8.3.9.1 General + +This procedure is used by the Node B to report the result of measurements requested by the CRNC with the Dedicated Measurement Initiation procedure. The Node B may initiate the Dedicated Measurement Reporting procedure at any time after establishing a Radio Link, as long as the Node B Communication Context exists. + +#### 8.3.9.2 Successful Operation + +![Sequence diagram showing the Dedicated Measurement Reporting procedure. A vertical line on the left is labeled CRNC and a vertical line on the right is labeled Node B. A horizontal arrow points from Node B to CRNC, labeled DEDICATED MEASUREMENT REPORT.](68dad113f9a15ab01945110cb50cdcfb_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: CRNC + Note right of Node B: Node B + Node B->>CRNC: DEDICATED MEASUREMENT REPORT + +``` + +Sequence diagram showing the Dedicated Measurement Reporting procedure. A vertical line on the left is labeled CRNC and a vertical line on the right is labeled Node B. A horizontal arrow points from Node B to CRNC, labeled DEDICATED MEASUREMENT REPORT. + +**Figure 40: Dedicated Measurement Reporting procedure, Successful Operation** + +If the requested measurement reporting criteria are met, the Node B shall initiate the Dedicated Measurement Reporting procedure. The DEDICATED MEASUREMENT REPORT message shall use the Communication Control Port + +assigned to the Node B Communication Context. If the measurement was initiated (by the Dedicated Measurement Initiation procedure) for multiple dedicated measurement objects, the Node B may include measurement values for multiple objects in the DEDICATED MEASUREMENT REPORT message. Unless specified below, the meaning of the parameters are given in other specifications. + +The *Measurement ID* IE shall be set to the Measurement ID provided by the CRNC when initiating the measurement with the Dedicated Measurement Initiation procedure. + +[TDD - In the case that the measurement was performed on a particular HS-SICH, the Node B shall include the *HS-SICH ID* IE that indicates which HS-SICH was measured.] + +If the achieved measurement accuracy does not fulfil the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Measurement not available shall be reported. If the Node B was configured to perform the Measurement Recovery Behavior, the Node B shall indicate Measurement Available to the CRNC when the achieved measurement accuracy again fulfils the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) and include the *Measurement Recovery Report Indicator* IE in the DEDICATED MEASUREMENT REPORT message if the requested measurement reporting criteria are not met. + +[FDD - If the *Alternative Format Reporting Indicator* IE was set to "Alternative format is allowed" in the DEDICATED MEASUREMENT INITIATION REQUEST message setting up the measurement to be reported, the Node B may include the *Extended Round Trip Time* IE in the DEDICATED MEASUREMENT REPORT message.] + +#### 8.3.9.3 Abnormal Conditions + +- + +### 8.3.10 Dedicated Measurement Termination + +#### 8.3.10.1 General + +This procedure is used by the CRNC to terminate a measurement previously requested by the Dedicated Measurement Initiation procedure. + +The Dedicated Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1 except if the measurement was initiated by the Dedicated Measurement Initiation procedure using the reserved value "All NBCC". + +If the measurement was initiated by the Dedicated Measurement Initiation procedure using the reserved value "All NBCC", the Dedicated Measurement Termination procedure may be initiated by the CRNC at any time. + +#### 8.3.10.2 Successful Operation + +![Sequence diagram showing the Dedicated Measurement Termination procedure. A horizontal arrow labeled 'DEDICATED MEASUREMENT TERMINATION REQUEST' points from the CRNC to the Node B.](1d08a1409256e10ac71d29289d872168_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note over CRNC, Node B: DEDICATED MEASUREMENT TERMINATION REQUEST + CRNC->>Node B: DEDICATED MEASUREMENT TERMINATION REQUEST +``` + +Sequence diagram showing the Dedicated Measurement Termination procedure. A horizontal arrow labeled 'DEDICATED MEASUREMENT TERMINATION REQUEST' points from the CRNC to the Node B. + +**Figure 41: Dedicated Measurement Termination procedure, Successful Operation** + +This procedure is initiated with a DEDICATED MEASUREMENT TERMINATION REQUEST message, sent from the CRNC to the Node B using the Communication Control Port assigned to the Node B Communication Context. + +Upon reception, the Node B shall terminate reporting of dedicated measurements corresponding to the received *Measurement ID* IE. + +#### 8.3.10.3 Abnormal Conditions + +- + +### 8.3.11 Dedicated Measurement Failure + +#### 8.3.11.1 General + +This procedure is used by the Node B to notify the CRNC that a measurement previously requested by the Dedicated Measurement Initiation procedure can no longer be reported. The Node B is allowed to initiate the DEDICATED MEASUREMENT FAILURE INDICATION message at any time after having sent the RADIO LINK SETUP RESPONSE message, as long as the Node B Communication Context exists. + +#### 8.3.11.2 Successful Operation + +![Sequence diagram for Dedicated Measurement Failure procedure, Successful Operation](7a1dee155822446f7828dcb055c465c3_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow points from the Node B to the CRNC, labeled "DEDICATED MEASUREMENT FAILURE INDICATION". + +Sequence diagram for Dedicated Measurement Failure procedure, Successful Operation + +**Figure 42: Dedicated Measurement Failure procedure, Successful Operation** + +This procedure is initiated with a DEDICATED MEASUREMENT FAILURE INDICATION message, sent from the Node B to the CRNC using the Communication Control Port assigned to the Node B Communication Context, to inform the CRNC that a previously requested measurement can no longer be reported. The Node B has locally terminated the indicated measurement. + +If the failed measurement was initiated with the *Node B Communication Context ID* IE set to the reserved value "All NBCC" and the Node B has terminated the measurement reporting of the measurement corresponding to the Measurement ID indicated in the DEDICATED MEASUREMENT FAILURE INDICATION message, the *CRNC Communication Context ID* IE shall be set to the value "All CRNCCC". + +#### 8.3.11.3 Abnormal Conditions + +- + +### 8.3.12 Radio Link Failure + +#### 8.3.12.1 General + +This procedure is used by the Node B to indicate a failure in one or more Radio Links [FDD - or Radio Link Sets][TDD or CCTrCHs within a Radio Link]. + +The Node B may initiate the Radio Link Failure procedure at any time after establishing a Radio Link. + +#### 8.3.12.2 Successful Operation + +![Sequence diagram for Radio Link Failure procedure, Successful Operation](6c6c57fd6906a27054b02c6be574f417_img.jpg) + +A sequence diagram showing the interaction between a CRNC and a Node B. The CRNC is on the left and the Node B is on the right. A horizontal arrow points from the Node B to the CRNC, labeled "RADIO LINK FAILURE INDICATION". + +Sequence diagram for Radio Link Failure procedure, Successful Operation + +**Figure 43: Radio Link Failure procedure, Successful Operation** + +When the Node B detects that one or more Radio Link(s) [FDD - or Radio Link Set(s)] [TDD - or CCTrCHs within a Radio Link] are no longer available, it sends the RADIO LINK FAILURE INDICATION message to the CRNC indicating the failed Radio Link(s) or Radio Link Set(s) or CCTrCHs with the most appropriate cause values in the *Cause* IE. The message shall use the Communication Control Port assigned to the concerned Node B Communication Context. + +If the failure concerns one or more individual Radio Link(s), the Node B shall indicate the affected Radio Link(s) using the *RL Information* IE. [FDD - If the failure concerns one or more Radio Link Set(s), the Node B shall indicate the affected Radio Link Set(s) using the *RL Set Information* IE.] [TDD - If the failure concerns only the failure of one or more CCTrCHs within a radio link, the Node B shall indicate the affected CCTrCHs using the *CCTrCH ID* IE.] + +When the Radio Link Failure procedure is used to notify the loss of UL synchronisation of a [FDD - Radio Link Set] [TDD - Radio Link or CCTrCHs within a Radio Link] on the Uu interface, the RADIO LINK FAILURE INDICATION message shall be sent, with the *Cause* IE set to "Synchronisation Failure", when indicated by the UL out-of-sync algorithm defined in TS 25.214 [10] and TS 25.224 [21]. [FDD - The algorithms in TS 25.214 [10] shall use the maximum value of the parameters N\_OUTSYNC\_IND and T\_RLFAILURE, and the minimum value of the parameters N\_INSYNC\_IND, that are configured in the cells supporting the radio links of the RL Set.] + +[FDD - When the Radio Link Failure procedure is used to indicate permanent failure in one or more Radio Link(s) / Radio Link Set(s) due to the occurrence of an UL or DL frame with more than one transmission gap caused by one or more compressed mode pattern sequences, the DL transmission shall be stopped and the RADIO LINK FAILURE INDICATION message shall be sent with the cause value "Invalid CM Settings". After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the Node B shall not remove the Radio Link(s)/Radio Link Set(s) from the Node B Communication Context or the Node B Communication Context itself.] + +[FDD - When the Radio Link Failure Procedure is used to indicate E-DCH non serving cell processing issue, the RADIO LINK FAILURE INDICATION shall be sent, with the *Cause* IE set to "Not enough user plane processing resources".] + +In the other cases, the Radio Link Failure procedure is used to indicate that one or more Radio Link(s)/Radio Link Set(s) are permanently unavailable and cannot be restored. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the Node B shall not remove the Radio Link/Radio Link Set from the Node B Communication Context or the Node B Communication Context itself. When applicable, the retention priorities associated with the transport channels shall be used by the Node B to prioritise which Radio Link(s)/Radio Link Set(s) to indicate as unavailable to the CRNC. + +Typical cause values are: + +##### **Radio Network Layer Causes:** + +- Synchronisation Failure +- Invalid CM settings + +##### **Transport Layer Causes:** + +- Transport Resources Unavailable + +##### **Miscellaneous Causes:** + +- Control Processing Overload +- HW Failure +- O&M Intervention +- Not enough user plane processing resources + +#### **8.3.12.3 Abnormal Conditions** + +- + +### **8.3.13 Radio Link Restoration** + +#### **8.3.13.1 General** + +This procedure is used by the Node B to notify the achievement and re-achievement of uplink synchronisation of one or more [FDD - Radio Link Sets][TDD - Radio Links or CCTrCHs within a Radio Link] on the Uu interface. + +The Node B may initiate the Radio Link Restoration procedure at any time after establishing a Radio Link. + +#### 8.3.13.2 Successful Operation + +![Sequence diagram for Figure 44: Radio Link Restoration procedure, Successful Operation. It shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from Node B to CRNC, labeled 'RADIO LINK RESTORE INDICATION'.](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +Sequence diagram for Figure 44: Radio Link Restoration procedure, Successful Operation. It shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from Node B to CRNC, labeled 'RADIO LINK RESTORE INDICATION'. + +**Figure 44: Radio Link Restoration procedure, Successful Operation** + +The Node B shall send the RADIO LINK RESTORE INDICATION message to the CRNC when indicated by the UL synchronisation detection algorithm defined in ref. TS 25.214 [10] and TS 25.224 [21] [FDD -, or when the *Fast Reconfiguration Mode* IE has been included in the RADIO LINK RECONFIGURATION COMMIT message and the Node B has detected that the UE has changed to the new configuration. The algorithm in ref. TS 25.214 [10] shall use the minimum value of the parameters N\_INSYNC\_IND that are configured in the cells supporting the radio links of the RL Set.] The message shall use the Communication Control Port assigned to the concerned Node B Communication Context. + +[TDD - If the re-established Uu synchronisation concerns one or more individual Radio Links, the Node B shall indicate the affected Radio Link(s) using the *RL Information* IE.] [TDD - If the re-established Uu synchronisation concerns one or more individual CCTrCHs within a radio link, the Node B shall indicate the affected CCTrCHs using the *CCTrCH ID* IE.] [FDD - If the re-established Uu synchronisation concerns one or more Radio Link Set(s), the Node B shall indicate the affected Radio Link Set(s) using the *RL Set Information* IE.] + +[FDD - The Node B shall send the RADIO LINK RESTORE INDICATION message when the E-DCH processing issue condition has ceased.] + +#### 8.3.13.3 Abnormal Condition + +- + +### 8.3.14 Compressed Mode Command [FDD] + +#### 8.3.14.1 General + +The Compressed Mode Command procedure is used to activate or deactivate the compressed mode in the Node B for one Node B Communication Context. + +The Compressed Mode Command procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. + +#### 8.3.14.2 Successful Operation + +![Sequence diagram for Figure 47: Compressed Mode Command procedure, Successful Operation. It shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B, labeled 'COMPRESSED MODE COMMAND'.](8aeef954d0c39404560f5f3968756f82_img.jpg) + +Sequence diagram for Figure 47: Compressed Mode Command procedure, Successful Operation. It shows two vertical lifelines: CRNC on the left and Node B on the right. A horizontal arrow points from CRNC to Node B, labeled 'COMPRESSED MODE COMMAND'. + +**Figure 47: Compressed Mode Command procedure, Successful Operation** + +The procedure is initiated by the CRNC sending a COMPRESSED MODE COMMAND message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context. + +The Node B shall deactivate all the ongoing Transmission Gap Pattern Sequences at the *CM Configuration Change CFN* IE requested by the CRNC when receiving the COMPRESSED MODE COMMAND message from the CRNC. From that moment on, all Transmission Gap Pattern Sequences included in *Transmission Gap Pattern Sequence Status* IE repetitions (if present) shall be started when the indicated *TGCFN* IE elapses. The *CM Configuration Change CFN* + +IE in the *Active Pattern Sequence Information* IE and *TGCFN* IE for each sequence refer to the next coming CFN with that value. + +If the values of the *CM Configuration Change CFN* IE and the *TGCFN* IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the *CM Configuration Change CFN* IE. + +If the *Affected HS-DSCH serving cell List* IE is included, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with *C-ID* IE included in *Affected HS-DSCH serving cell List* IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells. + +If the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing.. + +#### 8.3.14.3 Abnormal Conditions + +[FDD – If the concerned Node B Communication Context is not configured to use F-DPCH in the downlink and if a transmission gap pattern sequence is activated with an SF/2 downlink compressed mode method and for any Radio Link the transmission gap pattern sequence code information is not available, the Node B shall trigger the Radio Link Failure procedure with the cause value "Invalid CM Settings".] + +[FDD - If the COMPRESSED MODE COMMAND message contains the *Affected HS-DSCH serving cell List* IE in the *Active Pattern Sequence Information* IE and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK FAILURE message with the cause value "Invalid CM settings".] + +### 8.3.15 Downlink Power Timeslot Control [TDD] + +#### 8.3.15.1 General + +The purpose of this procedure is to enable the Node B to use the indicated DL Timeslot ISCP values when deciding the DL TX Power for each timeslot. + +The Downlink Power Timeslot Control procedure can be initiated by the CRNC at any time when the Node B Communication Context exists, irrespective of other ongoing CRNC initiated dedicated NBAP procedures towards this Node B Communication Context. The only exception occurs when the CRNC has requested the deletion of the last RL via this Node B, in which case the Downlink Power Timeslot Control procedure shall no longer be initiated. + +#### 8.3.15.2 Successful Operation + +![Sequence diagram showing the Downlink Power Timeslot Control procedure. A CRNC sends a DL POWER TIMESLOT CONTROL REQUEST message to a Node B.](cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: DL POWER TIMESLOT CONTROL REQUEST + CRNC->>Node B: DL POWER TIMESLOT CONTROL REQUEST + +``` + +Sequence diagram showing the Downlink Power Timeslot Control procedure. A CRNC sends a DL POWER TIMESLOT CONTROL REQUEST message to a Node B. + +**Figure 47A: Downlink Power Timeslot Control procedure, Successful Operation** + +The procedure is initiated by the CRNC sending a DL POWER TIMESLOT CONTROL REQUEST message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context. + +Upon reception, the Node B shall use the indicated DL Timeslot ISCP value when deciding the DL TX Power for each timeslot as specified in ref. TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. + +If the *Primary CCPCH RSCP Delta* IE is included, the Node B shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [23], and the value is equal to the *Primary CCPCH RSCP Delta* IE. If the *Primary CCPCH RSCP Delta* IE is not included and the *Primary CCPCH RSCP* IE is included, the Node B shall assume that the reported value is in the non-negative range as per TS 25.123 [23], and the value is equal to + +the *Primary CCPCH RSCP* IE. The Node B should use the indicated value for HS-DSCH scheduling and transmit power adjustment. + +#### 8.3.15.3 Abnormal Conditions + +- + +### 8.3.16 Radio Link Pre-emption + +#### 8.3.16.1 General + +This procedure is started by the Node B when resources need to be freed. + +The Node B may initiate the Radio Link Pre-emption procedure at any time after establishing a Radio Link. + +#### 8.3.16.2 Successful Operation + +![Sequence diagram of the Radio Link Pre-emption procedure, Successful Operation. It shows a vertical line for CRNC on the left and a vertical line for Node B on the right. A box labeled 'RL to be pre-empted' is on the Node B line. An arrow labeled 'RADIO LINK PREEMPTION REQUIRED INDICATION' points from the Node B line to the CRNC line.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +``` +sequenceDiagram + participant CRNC + participant Node B + Note right of Node B: RL to be pre-empted + Node B->>CRNC: RADIO LINK PREEMPTION REQUIRED INDICATION +``` + +Sequence diagram of the Radio Link Pre-emption procedure, Successful Operation. It shows a vertical line for CRNC on the left and a vertical line for Node B on the right. A box labeled 'RL to be pre-empted' is on the Node B line. An arrow labeled 'RADIO LINK PREEMPTION REQUIRED INDICATION' points from the Node B line to the CRNC line. + +**Figure 47B: Radio Link Pre-emption procedure, Successful Operation** + +When the Node B detects that a one or more Radio Links should be pre-empted (see Annex A), it shall send the RADIO LINK PREEMPTION REQUIRED INDICATION message to the CRNC using the Communication Control Port assigned to the concerned Node B Communication Context. + +If all Radio Links for a CRNC Communication Context ID should be pre-empted, the *RL Information* IE shall be omitted. If one or several but not all Radio Links should be pre-empted for a CRNC Communication Context, the Radio Links that should be pre-empted shall be indicated in the *RL Information* IE. The Radio Link(s) that should be pre-empted should be deleted by the CRNC. + +#### 8.3.16.3 Abnormal Conditions + +- + +### 8.3.17 Bearer Re-arrangement + +#### 8.3.17.1 General + +This procedure is started by the Node B when Bearers for the Node B Communication Context need to be rearranged. + +The Node B may initiate the Bearer Rearrangement procedure at any time after establishing a Radio Link. + +#### 8.3.17.2 Successful Operation + +![Sequence diagram showing the Bearer Re-arrangement Indication, Successful Operation. A message labeled 'BEARER REARRANGEMENT INDICATION' is sent from Node B to CRNC.](35a7554182eb055209552843f341a1ae_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: BEARER REARRANGEMENT INDICATION + Node B->>CRNC: BEARER REARRANGEMENT INDICATION + +``` + +Sequence diagram showing the Bearer Re-arrangement Indication, Successful Operation. A message labeled 'BEARER REARRANGEMENT INDICATION' is sent from Node B to CRNC. + +**Figure 47C: Bearer Re-arrangement Indication, Successful Operation** + +When the Node B detects that a signaling bearer or a transport bearer or both need to be re-arranged for the Node B Communication Context, it shall send the BEARER REARRANGEMENT INDICATION message to the CRNC. The message shall use the Communication Control Port assigned for this Node B Communication Context. + +If the signaling bearer for the control of the Node B Communication Context needs to be rearranged, the *Signalling Bearer Requested Indicator* IE shall be included in the BEARER REARRANGEMENT INDICATION message. + +If the transport bearer for a transport channel needs to be rearranged, the ID of the transport channel for which a new transport bearer is required, shall be included in the BEARER REARRANGEMENT INDICATION message. + +[FDD - If the separate Iub transport bearer mode is used and the transport bearer for an E-DCH MAC-d flow needs to be rearranged, the *Additional E-DCH Cell Information Bearer Rearrangement* IE shall be included in the BEARER REARRANGEMENT INDICATION message.] + +#### 8.3.17.3 Abnormal Conditions + +- + +### 8.3.18 Radio Link Activation + +#### 8.3.18.1 General + +This procedure is used to activate or de-activate the DL transmission on the Uu interface regarding selected RLs. + +#### 8.3.18.2 Successful Operation + +![Sequence diagram showing the Radio Link Activation procedure. A message labeled 'RADIO LINK ACTIVATION COMMAND' is sent from CRNC to Node B.](6078636a87fbe0e699aab4a6fddd15d7_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note left of CRNC: RADIO LINK ACTIVATION COMMAND + CRNC->>Node B: RADIO LINK ACTIVATION COMMAND + +``` + +Sequence diagram showing the Radio Link Activation procedure. A message labeled 'RADIO LINK ACTIVATION COMMAND' is sent from CRNC to Node B. + +**Figure 47D: Radio Link Activation procedure** + +This procedure is initiated by sending the RADIO LINK ACTIVATION COMMAND message from the CRNC to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context. Upon reception, the Node B shall for each concerned RL: + +- if the *Delayed Activation Update* IE indicates "Activate": + - if the *Activation Type* IE equals "Unsynchronised": + - [FDD - start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [16].] + +- [TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].] +- if the *Activation Type* IE equals "Synchronised": + - [FDD - start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [16], however never before the CFN indicated in the *Activation CFN* IE.] + - [TDD - start transmission on the new RL at the CFN indicated in the *Activation CFN* IE as specified in TS 25.427 [16].] +- [FDD - the Node B shall apply the power level indicated in the *Initial DL Tx Power* IE to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or power balancing is activated. During this period no inner loop power control shall be performed and, unless activated by the DL POWER CONTROL REQUEST message, no power balancing shall be performed. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) and downlink power balancing adjustments (see subclause 8.3.7).] +- [TDD - the Node B shall apply the power level indicated in the *Initial DL Tx Power* IE to the transmission on each DL DPCH and on each Time Slot of the RL when starting transmission until the UL synchronisation on the Uu interface is achieved for the RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.133 [22], subclause 4.2.3.3).] +- [FDD - if the *Propagation Delay* IE and optionally the *Extended Propagation Delay* IE are included, the Node B may use this information to speed up the detection of UL synchronisation on the Uu interface.] +- [FDD - if the *First RLS Indicator* IE is included, it indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The *First RLS Indicator* IE shall be used by the Node B together with the value of the *DL TPC Pattern 01 Count* IE which the Node B has received in the Cell Setup procedure, to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.] +- if the *Delayed Activation Update* IE indicates "Deactivate": + - stop DL transmission immediately, if the *Deactivation Type* IE equals "Unsynchronised", or at the CFN indicated by the *Deactivation CFN* IE, if the *Deactivation Type* IE equals "Synchronised". + +#### 8.3.18.3 Abnormal Conditions + +[FDD - If the *Delayed Activation Update* IE is included in the RADIO LINK ACTIVATION COMMAND message, it indicates "Activate" and the *First RLS Indicator* IE is not included, the Node B shall initiate the Error Indication procedure.] + +### 8.3.19 Radio Link Parameter Update + +#### 8.3.19.1 General + +The Radio Link Parameter Update procedure is executed by the Node B when the update of HS-DSCH [FDD - or E-DCH or UL CLTD] related radio link parameter values are needed on the Node B side. With this procedure, Node B can suggest some HS-DSCH [FDD - or E-DCH or UL CLTD] related Radio Link Parameter values to RNC. + +The Radio Link Parameter Update procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. + +#### 8.3.19.2 Successful Operation + +![Sequence diagram showing the successful operation of the Radio Link Parameter Update procedure. A vertical line on the left represents the CRNC, and a vertical line on the right represents the Node B. A horizontal arrow points from the Node B to the CRNC, labeled 'RADIO LINK PARAMETER UPDATE INDICATION'.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: RADIO LINK PARAMETER UPDATE INDICATION + Node B->>CRNC: + +``` + +Sequence diagram showing the successful operation of the Radio Link Parameter Update procedure. A vertical line on the left represents the CRNC, and a vertical line on the right represents the Node B. A horizontal arrow points from the Node B to the CRNC, labeled 'RADIO LINK PARAMETER UPDATE INDICATION'. + +Figure 48: Radio Link Parameter Update Indication, Successful Operation + +The Node B initiates the Radio Link Parameter Update procedure by sending the RADIO LINK PARAMETER UPDATE INDICATION message to the CRNC. The message contains suggested value(s) of the HS-DSCH [FDD - or E-DCH] related parameter(s) that should be reconfigured on the radio link(s). + +If the Node B needs to update HS-DSCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including [FDD - *HS-DSCH FDD Update Information IE*] [TDD - *HS-DSCH TDD Update Information IE*]. + +If the Node B needs to allocate new HS-SCCH Codes, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *HS-SCCH Code Change Indicator IE*. + +[FDD - If the Node B needs to allocate new HS-PDSCH Codes, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *HS-PDSCH Code Change Indicator IE*.] + +[FDD - If the Node B needs to update the CQI Feedback Cycle k, CQI Feedback Cycle2 k, CQI Cycle Switch Timer, CQI Repetition Factor, ACK-NACK Repetition Factor, CQI Power Offset, ACK Power Offset and/or NACK Power Offset, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *CQI Feedback Cycle k IE*, *CQI Repetition Factor IE*, *ACK-NACK Repetition Factor IE*, *CQI Power Offset IE*, *ACK Power Offset IE* and/or *NACK Power Offset IE*.] + +[FDD - If the Node B needs to update the Precoder weight set restriction, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Precoder weight set restriction IE*.] + +[FDD - If the Node B needs to update Secondary Serving HS-DSCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Additional HS Cell Information RL Param Upd IE*.] + +- [FDD - If the Node B needs to allocate new secondary serving HS-SCCH Codes, the Node B shall include the *HS-SCCH Code Change Indicator IE* in the *HS-DSCH FDD Secondary Serving Update Information IE*.] +- [FDD - If the Node B needs to update the Precoder weight set restriction, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Precoder weight set restriction IE* in the *HS-DSCH FDD Secondary Serving Update Information IE*.] + +[TDD - If the Node B needs to update the TDD ACK-NACK Power Offset the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *TDD ACK-NACK Power Offset IE*.] + +[FDD - If the Node B needs to update E-DCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *E-DCH FDD Update Information IE*.] + +[FDD - If the Node B needs to update the HARQ process allocation for non-scheduled transmission and/or HARQ process allocation for scheduled Transmission, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE* for the concerned MAC-d Flows and/or *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE*.] + +[FDD - If the Node B needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *E-DCH DL Control Channel Change Information IE*.] + +[FDD - If the Node B needs to indicate to RNC that the TTI switching has been triggered and confirmed by the UE, the Node B shall if supported initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *TTI Update Indication IE* in the *E-DCH FDD Update Information IE*.] + +[FDD - If the Node B needs to update Additional E-DCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Additional E-DCH Cell Information RL Param Upd IE*.] + +- [FDD - If the Node B needs to update the HARQ process allocation for scheduled Transmission, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the *HARQ Process Allocation For 2ms Scheduled Transmission Grant IE* for the concerned MAC-d Flows.] +- [FDD - If the Node B needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *Additional E-DCH DL Control Channel Change Information IE*.] + +[FDD - If the Node B needs to update the local activation state of UL CLTD of the UE in UL CLTD operation, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION including the *UL CLTD State Update Information* IE.] + +[FDD – If the Node B needs to indicate that the CPC Recovery has been initiated, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *CPC Recovery Report* IE.] + +[FDD – If the Node B needs to forward the UE measurement, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *UE Measurement Forwarding* IE.] + +[FDD – If the Node B needs to perform the improved synchronized RRC procedures, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including *CFN* IE.] + +#### 8.3.19.3 Abnormal Conditions + +- + +### 8.3.20 Secondary UL Frequency Reporting [FDD] + +#### 8.3.20.1 General + +The purpose of this procedure is to inform the Node B about the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation, or change the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured. + +#### 8.3.20.2 Successful Operation + +![Sequence diagram showing the Secondary UL Frequency Reporting procedure. A CRNC sends a SECONDARY UL FREQUENCY REPORT message to a Node B.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + Note right of CRNC: SECONDARY UL FREQUENCY REPORT + CRNC->>Node B: + +``` + +Sequence diagram showing the Secondary UL Frequency Reporting procedure. A CRNC sends a SECONDARY UL FREQUENCY REPORT message to a Node B. + +**Figure 48A: Secondary UL Frequency Reporting procedure** + +The Secondary UL Frequency Reporting procedure is initiated by sending the *SECONDARY UL FREQUENCY REPORT* message from the CRNC to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context. + +The *Activation Information* IE is included it defines the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, or the change request of activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured. + +- If the value of *Uu Activation State* IE is "Activated": the Node B shall if supported use this information for resource allocation operation of the secondary E-DCH radio link(s), F-DPCH transmission and DPCCH detection. +- If the value of *Uu Activation State* IE is "De-Activated": the Node B shall if supported use this information for release of the related resources for the secondary E-DCH radio link(s), cease of F-DPCH transmission and DPCCH detection. +- If the value of *Uu Activation State* IE is "Change Request": the Node B shall if supported change the activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured. + +#### 8.3.20.3 Abnormal Conditions + +- + +### 8.3.21 Secondary UL Frequency Update [FDD] + +#### 8.3.21.1 General + +The purpose of this procedure is to inform the CRNC about updates to activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation or change the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured. + +#### 8.3.21.2 Successful Operation + +![Sequence diagram showing the Secondary UL Frequency Update procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from Node B to CRNC, with the text 'SECONDARY UL FREQUENCY UPDATE INDICATION' written above it.](853f59c89931a666c07903b31d098277_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note right of Node B: SECONDARY UL FREQUENCY UPDATE INDICATION + Node B->>CRNC: + +``` + +Sequence diagram showing the Secondary UL Frequency Update procedure. A vertical line on the left is labeled 'CRNC' and a vertical line on the right is labeled 'Node B'. A horizontal arrow points from Node B to CRNC, with the text 'SECONDARY UL FREQUENCY UPDATE INDICATION' written above it. + +**Figure 48B: Secondary UL Frequency Update procedure** + +The Secondary UL Frequency Update procedure is initiated by the Node B by sending the SECONDARY UL FREQUENCY UPDATE INDICATION message to the CRNC. The message shall use the Communication Control Port assigned to the concerned Node B Communication Context. + +If the Node B needs to update the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, the Node B shall send SECONDARY UL FREQUENCY UPDATE INDICATION message and include the *Activation Information IE*. + +#### 8.3.21.3 Abnormal Conditions + +- + +## 8.4 Error Handling Procedures + +### 8.4.1 Error Indication + +#### 8.4.1.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 response message. + +#### 8.4.1.2 Successful Operation + +When the conditions defined in subclause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. + +In case the Error Indication procedure was triggered by a dedicated procedure, the following applies: + +- When the ERROR INDICATION message is sent from a Node B to its CRNC, the *CRNC Communication Context ID IE* shall be included in the message if the corresponding Node B Communication Context, addressed by the *Node B Communication Context ID IE* which was received in the message triggering the Error Indication procedure, exists; +- When the ERROR INDICATION message is sent from a CRNC to a Node B, the *Node B Communication Context ID IE* shall be included in the message if the corresponding CRNC Communication Context, addressed by the *CRNC Communication Context ID IE* which was received in the message triggering the Error Indication procedure, exists; +- When the message triggering the Error Indication procedure is received in the Node B and there is no Node B Communication Context as indicated by the *Node B Communication Context ID IE*, the Node B shall include the unknown *Node B Communication Context ID IE* from the received message in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure. + +- When the message triggering the Error Indication procedure is received in the CRNC and there is no CRNC Communication Context as indicated by the *CRNC Communication Context ID* IE, the CRNC shall include the unknown *CRNC Communication Context ID* IE from the received message in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure. + +The ERROR INDICATION message shall include either the *Cause* IE, or the *Criticality Diagnostics* IE or both the *Cause* IE and the *Criticality Diagnostics* IE. + +Typical cause values for the ERROR INDICATION message are: + +##### **Protocol Causes:** + +- Transfer Syntax Error +- Abstract Syntax Error (Reject) +- Abstract Syntax Error (Ignore and Notify) +- Message not Compatible with Receiver State +- Unspecified + +![Sequence diagram showing the Error Indication procedure from Node B to CRNC.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Node B->>CRNC: ERROR INDICATION + +``` + +Sequence diagram showing the Error Indication procedure from Node B to CRNC. + +**Figure 49: Error Indication procedure (Node B to CRNC): Successful Operation** + +![Sequence diagram showing the Error Indication procedure from CRNC to Node B.](2e399449b7f62d40167a65ca88888917_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant Node B + CRNC->>Node B: ERROR INDICATION + +``` + +Sequence diagram showing the Error Indication procedure from CRNC to Node B. + +**Figure 50: Error Indication procedure (CRNC to Node B), Successful Operation** + +#### 8.4.1.3 Abnormal Conditions + +- + +# --- 9 Elements for NBAP communication + +## 9.1 Message Functional Definition and Contents + +### 9.1.1 General + +Subclause 9.1 presents the contents of NBAP messages in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in ref. TR 25.921 [26]. + +### 9.1.2 Message Contents + +#### 9.1.2.1 Presence + +An information element can be of the following types: + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------| +| M | IEs marked as Mandatory (M) shall always be included in the message. | +| O | IEs marked as Optional (O) may or may not be included in the message. | +| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. | + +In case of an Information Element group, the group is preceded by a name for the info group (in bold). It is also indicated how many times a group may be repeated in the message and whether the group is conditional. The presence field of the Information Elements inside one group defines if the Information Element is mandatory, optional or conditional if the group is present. + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible: + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. 'YES' is usable only for non-repeatable information elements. | +| GLOBAL | The information element and all its repetitions together have one common criticality information. 'GLOBAL' is usable only for repeatable information elements. | +| EACH | Each repetition of the information element has its own criticality information. It is not allowed to assign different criticality values to the repetitions. 'EACH' is usable only for repeatable information elements. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +### 9.1.3 COMMON TRANSPORT CHANNEL SETUP REQUEST + +#### 9.1.3.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------------------------------|-------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| CHOICE Common Physical Channel To Be Configured | M | | | | YES | ignore | +| >Secondary CCPCH | | | | | | | +| >>Secondary CCPCH | | 1 | | | – | | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>FDD SCCPCH Offset | M | | 9.2.2.15 | Corresponds to TS 25.211 [7]:
S-CCPCH.k | – | | +| >>>DL Scrambling Code | C-PCH | | 9.2.2.13 | In case of BCH, ignore the IE. | – | | +| >>>FDD DL Channelisation Code Number | M | | 9.2.2.14 | In case of IMB using multiple channelization codes then this IE indicates the first one.
In case of BCH using 2 to 33. | – | | +| >>>TFCS | M | | 9.2.1.58 | For the DL. In case of BCH, refer to 25.331[18] | – | | +| >>>Secondary CCPCH Slot Format | M | | 9.2.2.43 | If Extended Secondary CCPCH Slot Format IE is present, this IE shall be ignored.
In case of BCH, ignore the IE. | – | | +| >>>TFCI Presence | C-SlotFormat or 3.84Mcps TDD IMB | | 9.2.1.57 | Refer to TS 25.211 [7].
In case of BCH, ignore the IE. | – | | +| >>>Multiplexing Position | M | | 9.2.2.23 | | – | | +| >>>Power Offset Information | | 1 | | | – | | +| >>>>PO1 | M | | Power Offset 9.2.2.29 | Power offset for the TFCI bits | – | | +| >>>>PO3 | M | | Power Offset 9.2.2.29 | Power offset for the pilot bits | – | | +| >>>STTD Indicator | M | | 9.2.2.48 | | – | | +| >>>FACH Parameters | | 0.. | | | GLOBAL | reject | +| >>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | + +| | | | | | | | +|----------------------------------------|---|-------------|-------------------|------------------------------------------------------|-----|--------| +| >>>>Transport Format Set | M | | 9.2.1.59 | For the DL. | – | | +| >>>>ToAWS | M | | 9.2.1.61 | | – | | +| >>>>ToAWE | M | | 9.2.1.60 | | – | | +| >>>>Max FACH Power | M | | DL Power 9.2.1.21 | Maximum allowed power on the FACH. | – | | +| >>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>Broadcast Reference | O | | 9.2.1.5C | | YES | ignore | +| >>>>IP Multicast Indication | O | | 9.2.1.108 | | YES | ignore | +| >>>PCH Parameters | | 0..1 | | | YES | reject | +| >>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>Transport Format Set | M | | 9.2.1.59 | For the DL. | – | | +| >>>>ToAWS | M | | 9.2.1.61 | | – | | +| >>>>ToAWE | M | | 9.2.1.60 | | – | | +| >>>>PCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>>> PICH Parameters | | 1 | | | – | | +| >>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>FDD DL Channelisation Code Number | M | | 9.2.2.14 | | – | | +| >>>>>PICH Power | M | | 9.2.1.49A | | – | | +| >>>>>PICH Mode | M | | 9.2.2.26 | Number of PI per frame | – | | +| >>>>>STTD Indicator | M | | 9.2.2.48 | | – | | +| >>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | + +| | | | | | | | +|-----------------------------------------|---|-------------------------------|----------------------|--------------------------------------------------------------------|-----|--------| +| >>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>> MICH Parameters | | 0..1 | | | YES | reject | +| >>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>FDD DL Channelisation Code Number | M | | 9.2.2.14 | | – | | +| >>>>MICH Power | M | | PICH Power 9.2.1.49A | | – | | +| >>>>MICH Mode | M | | 9.2.2.21D | Number of NI per frame | – | | +| >>>>STTD Indicator | M | | 9.2.2.48 | | – | | +| >>>FDD S-CCPCH Frame Offset | O | | 9.2.2.14B | | YES | reject | +| >>>Modulation Power Offset | O | | 9.2.2.91 | Used for MBSFN operation and 3.84Mcps TDD MBSFN IMB operation only | YES | reject | +| >>>Extended Secondary CCPCH Slot Format | O | | 9.2.2.92 | Used for MBSFN operation only | YES | reject | +| >>>IMB Parameters | O | | 9.2.2.115 | Used for 3.84Mcps TDD MBSFN IMB operation only | YES | reject | +| >>> BCH Parameters | | 0..1 | | | YES | ignore | +| >>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>BCH Power | M | | DL Power 9.2.1.21 | Maximum allowed power on the BCH. | – | | +| > PRACH | | | | | | | +| >> PRACH | | 1 | | | – | | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>Scrambling Code Number | M | | 9.2.2.42 | | – | | +| >>>TFCS | M | | 9.2.1.58 | For the UL. | – | | +| >>>Preamble Signatures | M | | 9.2.2.31 | | – | | +| >>>Allowed Slot Format Information | | 1.. | | | – | | +| >>>>RACH Slot Format | M | | 9.2.2.37 | | – | | +| >>>RACH Sub Channel Numbers | M | | 9.2.2.38 | | – | | +| >>>Puncture Limit | M | | 9.2.1.50 | For the UL | – | | +| >>>Preamble Threshold | M | | 9.2.2.32 | | – | | +| >>> RACH Parameters | | 1 | | | YES | reject | + +| | | | | | | | +|---------------------------------------|---|---|-----------|--------------------------------------------------------------|-----|--------| +| >>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>Transport Format Set | M | | 9.2.1.59 | For the UL. | – | | +| >>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>AICH Parameters | | 1 | | | – | | +| >>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>AICH Transmission Timing | M | | 9.2.2.1 | | – | | +| >>>>FDD DL Channelisation Code Number | M | | 9.2.2.14 | | – | | +| >>>>AICH Power | M | | 9.2.2.D | | – | | +| >>>>STTD Indicator | M | | 9.2.2.48 | | – | | +| >Not Used | | | NULL | This choice shall not be used. Reject procedure if received. | | | + +| Condition | Explanation | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SlotFormat or 3.84Mcps TDD IMB | The IE shall be present if the Secondary CCPCH Slot Format IE is set to any of the values from 8 to 17 or if the IMB Parameters IE is included. | +| PCH | The IE shall be present if the PCH Parameters IE is not present. | + +| Range Bound | Explanation | +|--------------------------------|------------------------------------------------------------------| +| maxNrOfFACHs | Maximum number of FACHs that can be defined on a Secondary CCPCH | +| maxNrOfSlotFormatsPRACH | Maximum number of SF for a PRACH | + +#### 9.1.3.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| CHOICE Common Physical Channel To Be Configured | M | | | | YES | ignore | +| >Secondary CCPCHs | | | | | | | +| >>SCCPCH CCTrCH ID | M | | CCTrCH ID
9.2.3.3 | For DL CCTrCH supporting one or several Secondary CCPCHs | – | | +| >>TFCS | M | | 9.2.1.58 | For DL CCTrCH supporting one or several Secondary CCPCHs | – | | +| >>TFCI Coding | M | | 9.2.3.22 | | – | | +| >>Puncture Limit | M | | 9.2.1.50 | | – | | +| >>CHOICE HCR or LCR or 7.68 Mcps | M | | | See note 1 below | – | | +| >>>3.84Mcps TDD | | | | | – | | +| >>>>Secondary CCPCH | | 1.. | | See note 2 below | GLOBAL | reject | +| >>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>>>>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>>>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>>>SCCPCH Power | M | | DL Power
9.2.1.21 | | – | | +| >>>>>TFCI Presence | O | | 9.2.1.57 | | YES | notify | +| >>>1.28Mcps TDD | | | | | – | | +| >>>>Secondary CCPCH LCR | | 1.. | | See note 2 below | GLOBAL | reject | +| >>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | + +| | | | | | | | +|---------------------------------------------|---|-------------------------|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>>Midamble Shift LCR | M | | 9.2.3.7A | For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, the Node B shall ignore the contents of this IE. | – | | +| >>>>>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>>>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>>>SCCPCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>>>>SCCPCH Time Slot Format LCR | M | | TDD DL DPCH Time Slot Format LCR 9.2.3.19D | | – | | +| >>>>>MBSFN Special Time Slot LCR | O | | Time Slot LCR Extension 9.2.3.24B | Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The Time Slot LCR IE for the Secondary CCPCH LCR shall be ignored if this IE appears. | YES | ignore | +| >>>7.68 Mcps TDD | | | | | – | | +| >>>> Secondary CCPCH 7.68 Mcps | | 1.. | | | GLOBAL | reject | +| >>>>>Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >>>>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>>>>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>>>>Repetition Period | M | | 9.2.3.16 | | – | | + +| | | | | | | | +|--------------------------------------------|---|--------------------------------|-------------------|------------------------------------------------------|--------|--------| +| >>>>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>>>SCCPCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>FACH Parameters | | 0..<maxNrOfFACHs> | | | GLOBAL | reject | +| >>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>FACH CCTrCH ID | M | | CCTrCH ID 9.2.3.3 | | – | | +| >>>Transport Format Set | M | | 9.2.1.59 | For the DL. | – | | +| >>>ToAWS | M | | 9.2.1.61 | | – | | +| >>>ToAWE | M | | 9.2.1.60 | | – | | +| >>>Max FACH Power | O | | DL Power 9.2.1.21 | Applicable to 1.28Mcps TDD only | YES | reject | +| >>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>Broadcast Reference | O | | 9.2.1.5C | | YES | ignore | +| >>>IP Multicast Indication | O | | 9.2.1.108 | | YES | ignore | +| >>PCH Parameters | | 0..1 | | | YES | reject | +| >>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>PCH CCTrCH ID | M | | CCTrCH ID 9.2.3.3 | | – | | +| >>>Transport Format Set | M | | 9.2.1.59 | For the DL. | – | | +| >>>ToAWS | M | | 9.2.1.61 | | – | | +| >>>ToAWE | M | | 9.2.1.60 | | – | | +| >>>CHOICE HCR or LCR or 7.68Mcps | M | | | See note 1 below | – | | +| >>>>3.84Mcps TDD | | | | | – | | +| >>>>>PICH Parameters | | 0..1 | | | YES | reject | +| >>>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>>>>Time Slot | M | | 9.2.3.23 | | – | | + +| | | | | | | | +|----------------------------------------------|---|------|---------------------------------------|--|-----|--------| +| >>>>>>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>>>>>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>>>>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>>>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>>>>Paging Indicator Length | M | | 9.2.3.8 | | – | | +| >>>>>>PICH Power | M | | 9.2.1.49A | | – | | +| >>>>1.28Mcp s TDD | | | | | – | | +| >>>>>PICH Parameters LCR | | 0..1 | | | YES | reject | +| >>>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>>>>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>>>>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>>>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>>>>Paging Indicator Length | M | | 9.2.3.8 | | – | | +| >>>>>>PICH Power | M | | 9.2.1.49A | | – | | +| >>>>>>Second TDD Channelisation Code LCR | M | | TDD Channelisation Code LCR 9.2.3.19a | | – | | +| >>>>>>TSTD Indicator | O | | 9.2.1.64 | | YES | reject | +| >>>>7.68Mcp s TDD | | | | | – | | +| >>>>>PICH Parameters | | 0..1 | | | YES | reject | +| >>>>>Common Physical Channel ID 7.68Mcp s | M | | 9.2.3.33 | | – | | +| >>>>>TDD Channelisation Code 7.68Mcp s | M | | 9.2.3.34 | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble Shift And Burst Type 7.68Mcp s | M | | 9.2.3.35 | | – | | + +| | | | | | | | +|--------------------------------------------|---|-------------|----------------------------|------------------------------------------------------------------|-----|--------| +| >>>>>>>TDD
Physical Channel
Offset | M | | 9.2.3.20 | | – | | +| >>>>>>>Repetition
Period | M | | 9.2.3.16 | | – | | +| >>>>>>>Repetition
Length | M | | 9.2.3.15 | | – | | +| >>>>>>>Paging
Indicator Length | M | | 9.2.3.8 | | – | | +| >>>>>>>PICH
Power | M | | 9.2.1.49A | | – | | +| >>>PCH Power | O | | DL Power
9.2.1.21 | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>>Binding ID | O | | 9.2.1.4 | Shall be
ignored if
bearer
establishment
with ALCAP. | YES | ignore | +| >>>Transport Layer
Address | O | | 9.2.1.63 | Shall be
ignored if
bearer
establishment
with ALCAP. | YES | ignore | +| >>>TNL QoS | O | | 9.2.1.58A | Shall be
ignored if
bearer
establishment
with ALCAP. | YES | ignore | +| >>TSTD Indicator | O | | 9.2.1.64 | | YES | reject | +| >> MICH Parameters | | 0..1 | | | YES | reject | +| >>>Common Physical
Channel ID | M | | 9.2.1.13 | | – | | +| >>>TDD Physical
Channel Offset | M | | 9.2.3.20 | | – | | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>Notification Indicator
Length | M | | 9.2.3.7Aa | | – | | +| >>>MICH Power | M | | PICH
Power
9.2.1.49A | | – | | +| >>>CHOICE HCR or
LCR or 7.68 Mcps | M | | | | – | | +| >>>>>3.84Mcps TDD | | | | | | | +| >>>>> MICH
Parameters HCR | | 1 | | | – | | +| >>>>>>>TDD
Channelisation
Code | M | | 9.2.3.19 | | – | | +| >>>>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>>>Midamble
Shift And Burst
Type | M | | 9.2.3.7 | | – | | +| >>>>>1.28Mcps TDD | | | | | | | +| >>>>> MICH
Parameters LCR | | 1 | | | – | | + +| | | | | | | | +|-----------------------------------------------------|---|------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>>>>>>TDD
Channelisation
Code LCR | M | | 9.2.3.19a | | – | | +| >>>>>>>Time Slot
LCR | M | | 9.2.3.24A | | – | | +| >>>>>>>Midamble
Shift LCR | M | | 9.2.3.7A | For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, the Node B shall ignore the contents of this IE. | – | | +| >>>>>>>Second
TDD
Channelisation
Code LCR | M | | TDD
Channelisation Code
LCR
9.2.3.19a | | – | | +| >>>>>>>TSTD
Indicator | M | | 9.2.1.64 | | – | | +| >>>>>>>MBSFN
Special Time Slot
LCR | O | | Time Slot
LCR
Extension
9.2.3.24B | Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The Time Slot LCR IE for the MICH parameters LCR shall be ignored if this IE appears. | YES | ignore | +| >>>>7.68 Mcps TDD | | | | | | | +| >>>>>>>MICH
Parameters 7.68
Mcps | | 1 | | | – | | +| >>>>>>>TDD
Channelisation
Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>>>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>>>Midamble
Shift And Burst
Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>Modulation | O | | 9.2.1.87 | Applicable to 3.84Mcps TDD and 7.68Mcps TDD in MBSFN operation only | YES | reject | +| >>Time Slot
Configuration LCR | | 0..7 | | Applicable to 1.28Mcps TDD for MBSFN. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | GLOBAL | reject | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | + +| | | | | | | | +|-----------------------------------|---|---|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>>Time Slot Parameter ID | M | | Cell Parameter ID 9.2.3.4 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). This IE indicates the frequency of the Secondary Frequency on which SCCPCH is configured. Applicable to 1.28Mcps TDD MBSFN. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >PRACH | | | | | | | +| >>CHOICE HCR or LCR or 7.68 Mcps | M | | | See note 1 below | – | | +| >>>3.84Mcps TDD | | | | | – | | +| >>>>PRACH | | 1 | | | YES | reject | +| >>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>TFCS | M | | 9.2.1.58 | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>>>Max PRACH Midamble Shift | M | | 9.2.3.6 | | – | | +| >>>>>PRACH Midamble | M | | 9.2.3.14 | | – | | +| >>>>>RACH | | 1 | | | YES | reject | +| >>>>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>>>Transport Format Set | M | | 9.2.1.59 | For the UL | – | | +| >>>>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>1.28Mcps TDD | | | | | – | | + +| | | | | | | | +|------------------------------------------|---|----------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>>>PRACH LCR | | 1..<maxNr
OfPRACH
LCRs> | | | GLOBAL | reject | +| >>>>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>>>TFCS | M | | 9.2.1.58 | | – | | +| >>>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>>>RACH | | 1 | | | YES | reject | +| >>>>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>>>Transport Format Set | M | | 9.2.1.59 | For the UL | – | | +| >>>>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of the secondary frequency on which PRACH to be set up. See note 3 below. | YES | reject | +| >>>7.68 Mcps TDD | | | | | – | | +| >>>>PRACH | | 1 | | | YES | reject | +| >>>>>Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >>>>>TFCS | M | | 9.2.1.58 | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>>>>Max PRACH Midamble Shift | M | | 9.2.3.6 | | – | | + +| | | | | | | | +|-----------------------------------|---|------|-------------------|-------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>>>>PRACH Midamble | M | | 9.2.3.14 | | – | | +| >>>>> RACH | | 1 | | | YES | reject | +| >>>>>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>>>>Transport Format Set | M | | 9.2.1.59 | For the UL | – | | +| >>>>>>Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >>>>>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >> FPACH | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>Max FPACH Power | M | | 9.2.3.5E | | – | | +| >>>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). This IE indicates the frequency of Secondary Frequency on which FPACH to be set up. | YES | reject | +| > PLCCH | | | | 1.28 Mcps TDD only | YES | ignore | +| >>Max PLCCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| > E-RUCCH | | | | 3.84Mcps TDD only | YES | ignore | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | – | | + +| | | | | | | | +|---------------------------------------|---|--|-------------------------|-------------------|-----|--------| +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>Max E-RUCCH Midamble Shift | M | | 9.2.3.44 | | – | | +| >>E-RUCCH Midamble | M | | PRACH Midamble 9.2.3.14 | | – | | +| >E-RUCCH 7.68Mcps | | | | 7.68Mcps TDD only | YES | ignore | +| >>Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>Max E-RUCCH Midamble Shift | M | | 9.2.3.44 | | – | | +| >>E-RUCCH Midamble | M | | PRACH Midamble 9.2.3.14 | | – | | + +NOTE 1: This information element is a simplified representation of the ASN.1. The choice is in reality performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. + +NOTE 2: This information element is a simplified representation of the ASN.1. Repetitions 1 to 8 and repetitions 9 to maxNrOfSCCPCHs / maxNrOfSCCPCHLCRs are represented by separate ASN.1 structures. + +NOTE 3: The configured PRACH resources on secondary frequency shall only be used for E-DCH random access. + +| Range Bound | Explanation | +|--------------------------|-----------------------------------------------------------------------------| +| maxNrOfSCCPCHs | Maximum number of Secondary CCPCHs per CCTrCH for 3.84Mcps TDD | +| maxNrOfSCCPCHLCRs | Maximum number of Secondary CCPCHs per CCTrCH for 1.28Mcps TDD | +| maxNrOfSCCPCHs768 | Maximum number of Secondary CCPCHs per CCTrCH for 7.68 Mcps TDD | +| maxNrOfFACHs | Maximum number of FACHs that can be defined on a Secondary CCPCH | +| maxNrOfPRACHLCRs | Maximum number of PRACHs LCR that can be defined on a RACH for 1.28Mcps TDD | + +### 9.1.4 COMMON TRANSPORT CHANNEL SETUP RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|--------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| FACH Parameters Info | | 0..<maxNrOfFACHs> | | The FACH Parameters may be combined with PCH Parameters | GLOBAL | ignore | +| >FACH Parameters | M | | Common Transport Channel Information Response 9.2.1.14A | | – | | +| PCH Parameters | O | | Common Transport Channel Information Response 9.2.1.14A | The PCH Parameters may be combined with FACH Parameters | YES | ignore | +| RACH Parameters | O | | Common Transport Channel Information Response 9.2.1.14A | The RACH Parameters shall not be combined with FACH Parameters or PCH Parameters | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| BCH Parameters | O | | Common Transport Channel Information Response 9.2.1.14A | | YES | ignore | + +| Range Bound | Explanation | +|---------------------|-----------------------------------------------------------------------------------------------------------| +| maxNrOfFACHs | Maximum number of FACHs that can be defined on a Secondary CCPCH[FDD] / a group of Secondary CCPCHs [TDD] | + +### 9.1.5 COMMON TRANSPORT CHANNEL SETUP FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | – | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | – | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.6 COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST + +#### 9.1.6.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|-------------------|-----------------------|--------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| CHOICE Common Physical Channel To Be Configured | M | | | | YES | reject | +| >Secondary CCPCH | | | | | | | +| >>FACH Parameters | | 0.. | | | GLOBAL | reject | +| >>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>Max FACH Power | O | | DL Power 9.2.1.21 | Maximum allowed power on the FACH. | – | | +| >>>ToAWS | O | | 9.2.1.61 | | – | | +| >>>ToAWE | O | | 9.2.1.60 | | – | | +| >>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer reconfiguration with ALCAP. | YES | ignore | +| >>PCH Parameters | | 0..1 | | | YES | reject | +| >>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>PCH Power | O | | DL Power 9.2.1.21 | Power to be used on the PCH. | – | | +| >>>ToAWS | O | | 9.2.1.61 | | – | | +| >>>ToAWE | O | | 9.2.1.60 | | – | | +| >>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer reconfiguration with ALCAP. | YES | ignore | +| >>PICH Parameters | | 0..1 | | | YES | reject | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>PICH Power | O | | 9.2.1.49A | | – | | +| >>MICH Parameters | | 0..1 | | | YES | reject | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>MICH Power | O | | PICH Power 9.2.1.49A | | – | | +| >>BCH Parameters | | 0..1 | | | YES | ignore | +| >>>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>>BCH Power | O | | DL Power 9.2.1.21 | Power to be used on the BCH | – | | +| >PRACH | | | | | | | +| >>PRACH Parameters | | 0.. | | | GLOBAL | reject | + +| | | | | | | | +|------------------------------------|---|-------------------------------------------|-----------|--------------------------------------------------------------|--------|--------| +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>Preamble Signatures | O | | 9.2.2.31 | | – | | +| >>>Allowed Slot Format Information | | 0..<maxNrOfSlotFormatsPRACH> | | | – | | +| >>>>RACH Slot Format | M | | 9.2.2.37 | | – | | +| >>>RACH Sub Channel Numbers | O | | 9.2.2.38 | | – | | +| >>>TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer reconfiguration with ALCAP. | YES | ignore | +| >>AICH Parameters | | 0..<maxPRACHCell> | | | GLOBAL | reject | +| >>>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>>AICH Power | O | | 9.2.2.D | | – | | +| >Not Used | | | NULL | This choice shall not be used. Reject procedure if received. | | | + +| Range Bound | Explanation | +|--------------------------------|------------------------------------------------------------------| +| maxFACHCell | Maximum number of FACHs that can be defined in a Cell | +| maxPRACHCell | Maximum number of PRACHs and AICHs that can be defined in a Cell | +| maxNrOfSlotFormatsPRACH | Maximum number of SF for a PRACH | + +#### 9.1.6.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| Secondary CCPCH Parameters | | 0..1 | | | YES | reject | + +| | | | | | | | +|----------------------------------------------|---|-----------------------------------|----------------------|------------------------------------------------------------------------------|--------|--------| +| >CCTrCH ID | M | | 9.2.3.3 | For DL CCTrCH supporting one or several Secondary CCPCHs | – | | +| >Secondary CCPCHs To Be Configured | | 0..<maxNrOfSCCPC Hs> | | See note 1 below | GLOBAL | reject | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>SCCPCH Power | O | | DL power 9.2.1.21 | | – | | +| PICH Parameters | | 0..1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >PICH Power | O | | 9.2.1.49A | | – | | +| FACH Parameters | | 0..<maxNrOfFACHs > | | | GLOBAL | reject | +| >Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >ToAWS | O | | 9.2.1.61 | | – | | +| >ToAWE | O | | 9.2.1.60 | | | | +| >Max FACH Power | O | | DL Power 9.2.1.21 | Applicable to 1.28Mcps TDD only | YES | reject | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer reconfiguration with ALCAP. | YES | ignore | +| PCH Parameters | | 0..1 | | | YES | reject | +| >Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >ToAWS | O | | 9.2.1.61 | | – | | +| >ToAWE | O | | 9.2.1.60 | | – | | +| >PCH Power | O | | DL Power 9.2.1.21 | Applicable to 1.28Mcps TDD only | YES | reject | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer reconfiguration with ALCAP. | YES | ignore | +| FPACH Parameters | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.. | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Max FPACH Power | O | | 9.2.3.5E | | – | | +| MICH Parameters | | 0..1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >MICH Power | O | | PICH Power 9.2.1.49A | | – | | + +| | | | | | | | +|--------------------------------------------|---|--------------------------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| PLCCH Parameters | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | ignore | +| >Max PLCCH Power | O | | DL Power 9.2.1.21 | | – | | +| Secondary CCPCH Parameters 7.68Mcps | | 0..1 | | Applicable to 7.68 Mcps TDD only | YES | reject | +| >CCTrCH ID | M | | 9.2.3.3 | For DL CCTrCH supporting one or several Secondary CCPCHs | – | | +| >Secondary CCPCHs To Be Configured | | 0..<maxNrOfSCCPC Hs768> | | | – | | +| >>Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >>SCCPCH Power | O | | DL power 9.2.1.21 | | – | | +| PICH Parameters 7.68Mcps | | 0..1 | | Applicable to 7.68 Mcps TDD only | YES | reject | +| >Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >PICH Power | O | | 9.2.1.49A | | – | | +| MICH Parameters 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | reject | +| >Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >MICH Power | O | | PICH Power 9.2.1.49A | | – | | +| UpPCH Parameters | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | reject | +| >UpPCH Position LCR | O | | 9.2.3.4Q | This position of UpPCH. For a multi-frequency cell, if this IE is not included in this message, UpPCH in secondary frequency indicated by "UARFCN" shall be deleted. | – | | +| >UARFCN | O | | 9.2.1.65 | Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]). | – | | + +NOTE 1: This information element is a simplified representation of the ASN.1. Repetitions 1 to 8 and repetitions 9 to maxNrOfSCCPCHs are represented by separate ASN.1 structures. Furthermore, maxNrOfSCCPCHs has different values in the ASN.1 for each of the two TDD options. + +| Range Bound | Explanation | +|--------------------------|----------------------------------------------------------------------| +| maxNrOfSCCPCHs | Maximum number of SCCPCHs that can be repeated in a Cell | +| maxNrOfFACHs | Maximum number of FACHs that can be repeated in a Cell | +| maxNrOfSCCPCHs768 | Maximum number of SCCPCHs that can be repeated in a Cell at 7.68Mcps | + +### 9.1.7 COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.8 COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.9 COMMON TRANSPORT CHANNEL DELETION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Common Physical Channel ID | M | | 9.2.1.13 | Indicates the Common Physical Channel for which the Common Transport Channels (together with the Common Physical Channel) shall be deleted. | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| Common Physical Channel ID 7.68Mcps | O | | 9.2.3.33 | Included at 7.68 Mcps when the physical channel ID exceeds the range of " Common Physical Channel ID" | YES | reject | + +### 9.1.10 COMMON TRANSPORT CHANNEL DELETION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.11 BLOCK RESOURCE REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|---------------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Blocking Priority Indicator | M | | 9.2.1.5 | | YES | reject | +| Shutdown Timer | C-BlockNormal | | 9.2.1.56 | | YES | reject | + +| Condition | Explanation | +|-------------|---------------------------------------------------------------------------------------------------| +| BlockNormal | The IE shall be present if the Blocking Priority Indicator IE indicates "Normal Priority". | + +### 9.1.12 BLOCK RESOURCE RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.13 BLOCK RESOURCE FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.14 UNBLOCK RESOURCE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | ignore | + +### 9.1.15 AUDIT REQUIRED INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | + +### 9.1.16 AUDIT REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Start Of Audit Sequence Indicator | M | | 9.2.1.56B | | YES | reject | + +### 9.1.17 AUDIT RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|----------------------------------|-------------------------------------------------------|-----------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| End Of Audit Sequence Indicator | M | | 9.2.1.29A | | YES | ignore | +| Cell Information | | 0..<maxCellinNodeB> | | | EACH | ignore | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Configuration Generation ID | M | | 9.2.1.16 | | – | | +| >Resource Operational State | M | | 9.2.1.52 | | – | | +| >Availability Status | M | | 9.2.1.2 | | – | | +| >Local Cell ID | M | | 9.2.1.38 | The local cell that the cell is configured on | – | | +| >Primary SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to FDD only | YES | ignore | +| >Secondary SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to FDD only | YES | ignore | +| >Primary CPICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to FDD only | YES | ignore | +| >Secondary CPICH Information | | 0..<maxSCPICHCell> | | Applicable to FDD only | EACH | ignore | +| >>Secondary CPICH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >Primary CCPCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| >BCH Information | O | | Common Transport Channel Status Information 9.2.1.14B | | YES | ignore | +| >Secondary CCPCH Information | | 0..<maxSCPCHC> | | See note 1 below | EACH | ignore | + +| | | | | | | | +|--|--|------|--|--|--|--| +| | | e//> | | | | | +|--|--|------|--|--|--|--| + +| | | | | | | | +|------------------------------------------|---|--------------------------------|-------------------------------------------------------|--------------------------------------------------|------|--------| +| >>Secondary CCPCH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >PCH Information | O | | Common Transport Channel Status Information 9.2.1.14B | | YES | ignore | +| >PICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| > FACH Information | | 0..<maxFACHCell> | | | EACH | ignore | +| >>FACH Individual Information | M | | Common Transport Channel Status Information 9.2.1.14B | | – | | +| > PRACH Information | | 0..<maxPRACHCell> | | | EACH | ignore | +| >>PRACH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| > RACH Information | | 0..<maxRACHCell> | | | EACH | ignore | +| >>RACH Individual Information | M | | Common Transport Channel Status Information 9.2.1.14B | | – | | +| > AICH Information | | 0..<maxPRACHCell> | | Applicable to FDD only | EACH | ignore | +| >>AICH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >Not Used 1 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >Not Used 2 | O | | NULL | This item shall not be used. Ignore if received. | – | | + +| | | | | | | | +|--------------------------------|---|--------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------|------|--------| +| >Not Used 3 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >Not Used 4 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | TDD Sync Channel Applicable to 3.84Mcps TDD only | YES | ignore | +| >FPACH Information | | 0..<maxFPACHCell> | | Applicable to 1.28Mcps TDD only | EACH | ignore | +| >>FPACH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >DwPCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to 1.28Mcps TDD only | YES | ignore | +| >HS-DSCH Resources Information | | 0..<maxFrequencyinCell> | | See note 2 below | EACH | ignore | +| >>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>Availability Status | M | | 9.2.1.2 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable to 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| >MICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| >E-DCH Resources Information | | 0..<maxFrequencyinCell> | | See note 2 below | EACH | ignore | +| >>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>Availability Status | M | | 9.2.1.2 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable to 1.28Mcps TDD when | YES | ignore | + +| | | | | | | | +|--|--|--|--|-----------------------------|--|--| +| | | | | using multiple frequencies. | | | +|--|--|--|--|-----------------------------|--|--| + +| | | | | | | | +|----------------------------------------------------|---|---------------------------------|---------------------------------------------------------------|--------------------------------------------------|------|--------| +| >PLCCH Information | | 0..<maxPLCCHCell> | | Applicable to 1.28Mcps TDD only | EACH | ignore | +| >>PLCCH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >Primary CCPCH Information 7.68Mcps | O | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | YES | ignore | +| >Secondary CCPCH Information 7.68Mcps | | 0..<maxSCCPCHCell> | | | EACH | ignore | +| >>Secondary CCPCH Individual Information 7.68 Mcps | M | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | – | | +| >PICH Information 7.68Mcps | O | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | YES | ignore | +| >PRACH Information 7.68Mcps | | 0..<maxPRACHCell> | | | EACH | ignore | +| >>PRACH Individual Information 7.68Mcps | M | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | – | | +| >SCH Information 7.68Mcps | O | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | TDD Sync Channel Applicable to 7.68Mcps TDD only | YES | ignore | +| >MICH Information 7.68Mcps | O | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | YES | ignore | +| >E-RUCCH Information | | 0..<maxERUCCHCell> | | 3.84Mcps TDD only | EACH | ignore | +| >>E-RUCCH Individual Information | M | | Common Physical Channel Status | | – | | + +| | | | | | | | +|--|--|--|--------------------------|--|--|--| +| | | | Information
9.2.1.13A | | | | +|--|--|--|--------------------------|--|--|--| + +| | | | | | | | +|-----------------------------------------------|---|---------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------|--------| +| >E-RUCCH Information 7.68Mcps | | 0..<maxE-RUCCHCell> | | 7.68Mcps
TDD only | EACH | ignore | +| >>E-RUCCH Individual Information 7.68Mcps | M | | Common Physical Channel Status Information 7.68 Mcps 9.2.3.36 | | – | | +| >UARFCN Information LCR | | 0..<maxFrequencyinCell> | | Applicable to 1.28Mcps TDD when using multiple frequencies. | EACH | ignore | +| >>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | – | | +| >>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>Availability Status | M | | 9.2.1.2 | | – | | +| >UpPCH Information LCR | | 0..<maxFrequencyinCell> | | Applicable to 1.28Mcps TDD only. | EACH | ignore | +| >>UARFCN | O | | 9.2.1.65 | Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]). | – | | +| >>UpPCH Position LCR | M | | 9.2.3.4Q | | – | | +| >>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>Availability Status | M | | 9.2.1.2 | | – | | +| Communication Control Port Information | | 0..<maxCCPinNodeB> | | | EACH | ignore | +| >Communication Control Port ID | M | | 9.2.1.15 | | – | | +| >Resource Operational State | M | | 9.2.1.52 | | – | | +| >Availability Status | M | | 9.2.1.2 | | – | | +| Local Cell Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >Local Cell ID | M | | 9.2.1.38 | | – | | +| >DL Or Global Capacity Credit | M | | 9.2.1.20B | | – | | +| >UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >Common Channels Capacity Consumption Law | M | | 9.2.1.9A | | – | | +| >Dedicated Channels Capacity Consumption Law | M | | 9.2.1.20A | | – | | +| >Maximum DL Power Capability | O | | 9.2.1.39 | | – | | +| >Minimum Spreading | O | | 9.2.1.47 | | – | | + +| | | | | | | | +|---------------------------------------------------------|----------------------------|--|----------------------------|---------------------------|-----|--------| +| Factor | | | | | | | +| >Minimum DL Power Capability | O | | 9.2.1.46A | | – | | +| >Local Cell Group ID | O | | 9.2.1.37A | | – | | +| >Reference Clock Availability | O | | 9.2.3.14A | TDD only | YES | ignore | +| >Power Local Cell Group ID | O | | 9.2.1.49B | | YES | ignore | +| >HSDPA Capability | O | | 9.2.1.31Ga | | YES | ignore | +| >E-DCH Capability | O | | 9.2.1.70 | | YES | ignore | +| >E-DCH TTI2ms Capability | C-EDCHCap ability | | 9.2.2.13V | FDD only | YES | ignore | +| >E-DCH SF Capability | C-EDCHCap ability | | 9.2.2.13W | FDD only | YES | ignore | +| >E-DCH HARQ Combining Capability | C-EDCHCap ability | | 9.2.2.13X | FDD only | YES | ignore | +| >E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | +| >F-DPCH Capability | O | | 9.2.2.16a | FDD only | YES | ignore | +| >E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| >Continuous Packet Connectivity DTX-DRX Capability | O | | 9.2.2.64 | FDD only | YES | ignore | +| >Max UE DTX Cycle | C-DTX-DRXCapa bility | | 9.2.2.95 | FDD only | YES | ignore | +| >Continuous Packet Connectivity HS-SCCH less Capability | O | | 9.2.2.65 | FDD only | YES | ignore | +| >MIMO Capability | O | | 9.2.1.118 | FDD and 1.28Mcps TDD only | YES | ignore | +| >SixtyfourQAM DL Capability | O | | 9.2.1.110 | FDD and 1.28Mcps TDD only | YES | ignore | +| >MBMS Capability | O | | 9.2.1.86 | | YES | ignore | +| >Enhanced FACH Capability | O | | 9.2.1.114 | FDD and 1.28Mcps TDD only | YES | ignore | +| >Enhanced PCH Capability | C-Enhanced FACHCap ability | | 9.2.1.115 | FDD and 1.28Mcps TDD only | YES | ignore | +| >SixteenQAM UL Capability | O | | 9.2.2.88 | FDD only | YES | ignore | +| >HS-DSCH MAC-d PDU Size Capability | O | | 9.2.1.31IC | | YES | ignore | +| >MBSFN Only Mode Capability | O | | 9.2.3.71 | 1.28Mcps TDD only | YES | ignore | +| >F-DPCH Slot Format Capability | O | | 9.2.2.94 | FDD only | YES | ignore | +| >E-DCH MAC-d PDU Size Capability | O | | 9.2.1.74A | | YES | ignore | +| >Common E-DCH Capability | O | | 9.2.2.101 | FDD only | YES | Ignore | +| >E-AI Capability | C-CommonE DCHCapa bility | | 9.2.2.102 | FDD only | YES | Ignore | +| >Enhanced UE DRX Capability | O | | 9.2.1.116 | FDD only | YES | ignore | +| >Enhanced UE DRX Capability LCR | O | | Enhanced UE DRX Capability | 1.28Mcps TDD only | YES | ignore | + +| | | | | | | | +|------------------------------------------------------------|--------------------------------|---------------------------------------|------------|-----------------------------------|------|--------| +| | | | 9.2.1.116 | | | | +| >E-DPCCH Power Boosting Capability | O | | 9.2.2.109 | | YES | ignore | +| >SixtyfourQAM DL and MIMO Combined Capability | O | | 9.2.1.121 | FDD and 1.28Mcps
TDD only only | YES | ignore | +| >Multi Cell Capability Info | O | | 9.2.2.113 | FDD only | YES | ignore | +| >Semi-Persistent scheduling Capability LCR | O | | 9.2.3.91 | 1.28Mcps
TDD only | YES | ignore | +| >Continuous Packet Connectivity DRX Capability LCR | O | | 9.2.3.92 | 1.28Mcps
TDD only | YES | ignore | +| >Common E-DCH HS-DPCCH Capability | C-CommonE
DCHCapa
bility | | 9.2.2.116 | FDD only | YES | ignore | +| >MIMO Power Offset For S-CPICH Capability | O | | 9.2.2.118 | FDD only | YES | ignore | +| >TX Diversity on DL Control Channels by MIMO UE Capability | O | | 9.2.2.121 | FDD only | YES | ignore | +| >Single Stream MIMO Capability | O | | 9.2.2.122 | FDD only | YES | ignore | +| >Dual Band Capability Info | O | | 9.2.2.125 | FDD only | YES | ignore | +| >Cell Portion Capability LCR | O | | 9.2.3.106 | 1.28Mcps
TDD only | YES | ignore | +| >Cell Capability Container | O | | 9.2.2.129 | FDD only | YES | ignore | +| >TS0 Capability LCR | O | | 9.2.3.109 | 1.28Mcps
TDD only | YES | ignore | +| >Precoding Weight Set Restriction | O | | 9.2.2.143 | FDD only | YES | ignore | +| >Cell Capability Container TDD LCR | O | | 9.2.3.115 | 1.28Mcps
TDD only | YES | ignore | +| >MU-MIMO Capability Container | O | | 9.2.3.119 | 1.28Mcps
TDD only | YES | ignore | +| >Adaptive Special Burst Power Capability LCR | O | | 9.2.3.122 | 1.28Mcps
TDD only | YES | ignore | +| Local Cell Group Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >Local Cell Group ID | M | | 9.2.1.37A | | – | | +| >DL Or Global Capacity Credit | M | | 9.2.1.20B | | – | | +| >UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >Common Channels Capacity Consumption Law | M | | 9.2.1.9A | | – | | +| >Dedicated Channels Capacity Consumption Law | M | | 9.2.1.20A | | – | | +| >E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | +| >E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| Power Local Cell Group Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >Power Local Cell Group ID | M | | 9.2.1.49B | | – | | +| >Maximum DL Power Capability | M | | 9.2.1.39 | | – | | + +NOTE 1: This information element is a simplified representation of the ASN.1. [TDD - Repetitions 1 to 8 and repetitions 9 to maxSCCPCHCell are represented by separate ASN.1 structures.] Furthermore, maxSCCPCHCell has different values in the ASN.1 for FDD and for each of the two TDD options. + +NOTE 2: For 1.28Mcps TDD when using multiple frequencies, this information element for Repetition 1 and repetition 2 through maxFrequencyinCell are represented by respective ASN.1 structures with different criticalities. + +| Condition | Explanation | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EDCHCapability | The IE shall be present if the E-DCH Capability IE is set to "E-DCH Capable". | +| EnhancedFACHCapability | The IE shall be present if the Enhanced FACH Capability IE is set to "Enhanced FACH Capable". | +| DTX-DRXCapability | The IE shall be present if the Continuous Packet Connectivity DTX-DRX Capability IE is present and set to "Continuous Packet Connectivity DTX-DRX Capable". | +| CommonEDCHCapability | The IE shall be present if the Common E-DCH Capability IE is set to "Common E-DCH Capable". | + +| Range Bound | Explanation | +|----------------------------|-------------------------------------------------------------------------------------| +| maxCellinNodeB | Maximum number of Cells that can be configured in Node B | +| maxCCPinNodeB | Maximum number of Communication Control Ports that can exist in the Node B | +| maxLocalCellinNodeB | Maximum number of Local Cells that can exist in the Node B | +| maxSCPICHCell | Maximum number of Secondary CPICHs that can be defined in a Cell. | +| maxSCCPCHCell | Maximum number of Secondary CCPCHs that can be defined in a Cell. | +| maxSCCPCHCell768 | Maximum number of Secondary CCPCHs that can be defined in a Cell for 7.68 Mcps TDD. | +| maxFACHCell | Maximum number of FACHs that can be defined in a Cell | +| maxPRACHCell | Maximum number of PRACHs that can be defined in a Cell | +| maxRACHCell | Maximum number of RACHs that can be defined in a Cell | +| maxFPACHCell | Maximum number of FPACHs that can be defined in a Cell | +| maxPLCCHCell | Maximum number of PLCCHs that can be defined in a Cell | +| maxE-RUCCHCell | Maximum number of E-RUCCHs that can be defined in a Cell | +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.17A AUDIT FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.18 COMMON MEASUREMENT INITIATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | reject | +| CHOICE Common Measurement Object Type | M | | | | YES | reject | +| >Cell | | | | | | | +| >>C-ID | M | | 9.2.1.9 | | – | | +| >>Time Slot | O | | 9.2.3.23 | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only | – | | +| >>Time Slot LCR | O | | 9.2.3.24A | Applicable to 1.28Mcps TDD only | YES | reject | +| >>Neighbouring Cell Measurement Information | | 0..<maxNrOfMeasN Cell> | | | GLOBAL | ignore | +| >>>CHOICE Neighbouring Cell Measurement Information | | | | | – | | +| >>>>Neighbouring FDD Cell Measurement Information | | | | FDD only | | | +| >>>>>Neighbouring FDD Cell Measurement Information | M | | 9.2.1.47C | | – | | +| >>>>Neighbouring TDD Cell Measurement Information | | | | Applicable to 3.84Mcps TDD only | | | +| >>>>>Neighbouring TDD Cell Measurement Information | M | | 9.2.1.47D | | – | | +| >>>>Additional Neighbouring Cell Measurement Information | | | | See Note 1 | | | +| >>>>>Neighbouring TDD Cell Measurement Information LCR | | | | Applicable to 1.28Mcps TDD only | | | +| >>>>>>Neighbouring TDD Cell Measurement Information LCR | M | | 9.2.1.47E | | YES | reject | +| >>>>>Neighbouring TDD Cell Measurement Information 7.68Mcps | | | | Applicable to 7.68 Mcps TDD only | | | +| >>>>>>Neighbouring TDD Cell Measurement Information 7.68Mcps | M | | 9.2.3.37 | | YES | reject | +| >>UARFCN | O | | 9.2.1.65 | Applicable for 1.28 Mcps TDD only | YES | reject | +| >>UpPCH Position LCR | O | | 9.2.3.4Q | Applicable to | YES | reject | + +| | | | | | | | +|--|--|--|--|----------------------|--|--| +| | | | | 1.28Mcps TDD
only | | | +|--|--|--|--|----------------------|--|--| + +| | | | | | | | +|----------------------------------------------------|---|------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>Additional Time Slot LCR | | 0..<maxFrequencyinCell – 1> | | Applicable to 1.28Mcps TDD only.
If the IE present, the measurement type should also be applied to the time slot (s). | GLOBAL | ignore | +| >>>UARFCN | M | | 9.2.1.65 | | – | | +| >>>Time Slot Initiated LCR | | 0..6 | | If the value is zero, the measurement type should be applied to all time slots in the UARFCN which satisfies the requirement of the measurement type | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >RACH | | | | FDD only | | | +| >>C-ID | M | | 9.2.1.9 | | – | | +| >>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >Not Used | | | NULL | This choice shall not be used. Reject procedure if received. | | | +| >Additional Common Measurement Object Types | | | | See Note 1 | | | +| >>Power Local Cell Group | | | | | – | | +| >>>Power Local Cell Group ID | M | | 9.2.1.49B | | YES | reject | +| >>E-DCH RACH | | | | FDD only | – | | +| >>>C-ID | M | | 9.2.1.9 | | YES | reject | +| Common Measurement Type | M | | 9.2.1.11 | | YES | reject | +| Measurement Filter Coefficient | O | | 9.2.1.41 | | YES | reject | +| Report Characteristics | M | | 9.2.1.51 | | YES | reject | +| SFN Reporting Indicator | M | | FN Reporting Indicator 9.2.1.29B | | YES | reject | +| SFN | O | | 9.2.1.53A | | YES | reject | +| Common Measurement Accuracy | O | | 9.2.1.9B | | YES | reject | +| Measurement Recovery Behavior | O | | 9.2.1.43A | | YES | ignore | +| RTWP* Reporting Indicator | O | | 9.2.1.53b | | YES | reject | +| RTWP* for Cell Portion Reporting Indicator | O | | 9.2.1.53c | | YES | reject | +| Reference Received Total Wide Band Power Reporting | O | | 9.2.2.39C | FDD only | YES | ignore | +| GANSS Time ID | O | | 9.2.1.104a | This IE may only be present if the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames" | YES | ignore | + +| | | | | | | | +|--|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | for UE Positioning". If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and this IE is absent, the GANSS time is Galileo system time. | | | +|--|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +NOTE 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a *ProtocolIE-Single-Container* and a *ProtocolExtensionContainer* within the ASN.1. + +| Range Bound | Explanation | +|-------------------------------|---------------------------------------------------------------------| +| maxNrOfMeasNCell | Maximum number of neighbouring cells that can be measured on. | +| maxFrequencyinCell - 1 | Maximum number of frequencies that can be used in the cell minus 1. | + +### 9.1.19 COMMON MEASUREMENT INITIATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|--------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| CHOICE Common Measurement Object Type | O | | | Common Measurement Object Type that the measurement was initiated with. | YES | ignore | +| >Cell | | | | | | | +| >>Common Measurement Value | M | | 9.2.1.12 | For 1.28Mcps TDD, if the IE Additional Measurement Value is present, this IE shall be ignored. | – | | +| >>Additional Measurement Value | | 0..<maxFrequencyinCell> | | Applicable to 1.28Mcps TDD only. If more than one measurement value needs to be reported, this IE shall be used. | GLOBAL | ignore | +| >>>UARFCN | M | | 9.2.1.65 | | – | | +| >>>Time Slot Measurement Value LCR | | 1..6 | | | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | The IE shall be ignored if the Measurement Type is frequency level. | – | | +| >>>>Common Measurement Value | M | | 9.2.1.12 | | – | | +| >RACH | | | | FDD only | | | +| >>Common Measurement Value | M | | 9.2.1.12 | | – | | +| >Not Used | | | NULL | This choice shall not be used. | | | +| >Additional Common Measurement Object Types | | | | See Note 1 | | | +| >>Power Local Cell Group | | | | | – | | +| >>>Common Measurement Value | M | | 9.2.1.12 | | YES | ignore | +| >>E-DCH RACH | | | | FDD only | | | +| >>>Common Measurement Value | M | | 9.2.1.12 | | YES | ignore | +| SFN | O | | 9.2.1.53A | Common Measurement Time Reference | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| Common Measurement Achieved Accuracy | O | | Common Measurement Accuracy 9.2.1.9B | | YES | ignore | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|-----------|----------|-----|--------| +| Measurement Recovery Support Indicator | O | | 9.2.1.43C | | YES | ignore | +| Reference Received Total Wide Band Power Support Indicator | O | | 9.2.2.39D | FDD only | YES | ignore | +| Reference Received Total Wide Band Power | O | | 9.2.2.39B | FDD only | YES | ignore | +| NOTE 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. | | | | | | | + +| Range Bound | Explanation | +|---------------------------|--------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell. | + +### 9.1.20 COMMON MEASUREMENT INITIATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.21 COMMON MEASUREMENT REPORT + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|--------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| CHOICE Common Measurement Object Type | M | | | Common Measurement Object Type that the measurement was initiated with. | YES | ignore | +| >Cell/ | | | | | | | +| >>Common Measurement Value Information | M | | 9.2.1.12A | For 1.28Mcps TDD, if the IE Additional Measurement Value is present, this IE shall be ignored. | – | | +| >>C-ID | O | | 9.2.1.9 | | YES | ignore | +| >>Additional Measurement Value Information | | 0..<maxFrequencyinCell> | | Applicable to 1.28Mcps TDD only. If more than one measurement value needs to be reported, this IE shall be used. | GLOBAL | ignore | +| >>>UARFCN | | | 9.2.1.65 | | | | +| >>>Time Slot Measurement Value LCR | | 1..6 | | | | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | The IE shall be ignored if the Measurement Type is frequency level. | | | +| >>>>Common Measurement Value Information | M | | 9.2.1.12A | | | | +| >RACH | | | | FDD only | | | +| >>Common Measurement Value Information | M | | 9.2.1.12A | | – | | +| >>C-ID | O | | 9.2.1.9 | | YES | ignore | +| >Not Used | | | NULL | This choice shall not be used. | | | +| >Additional Common Measurement Object Types | | | | See Note 1 | | | +| >>Power Local Cell Group | | | | | – | | +| >>>Common Measurement Value Information | M | | 9.2.1.12A | | YES | ignore | +| >>E-DCH RACH | | | | FDD only | | | +| >>>Common Measurement Value Information | M | | 9.2.1.12A | | YES | ignore | +| SFN | O | | 9.2.1.53A | Common Measurement Time Reference | YES | ignore | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|-----------|----------|-----|--------| +| Measurement Recovery Reporting Indicator | O | | 9.2.1.43B | | YES | ignore | +| Reference Received Total Wide Band Power | O | | 9.2.2.39B | FDD only | YES | ignore | +| NOTE 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. | | | | | | | + +| Range Bound | Explanation | +|---------------------------|--------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell. | + +### 9.1.22 COMMON MEASUREMENT TERMINATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | + +### 9.1.23 COMMON MEASUREMENT FAILURE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | + +### 9.1.24 CELL SETUP REQUEST + +#### 9.1.24.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Local Cell ID | M | | 9.2.1.38 | | YES | reject | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| T Cell | M | | 9.2.2.49 | | YES | reject | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nu (TS 25.104 [14]) for UTRA operating bands for which it is defined; ignored for UTRA operating bands for which Nu is not defined. | YES | reject | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nd (TS 25.104 [14]) | YES | reject | + +| | | | | | | | +|-------------------------------------------|---|----------------------------|--------------------------------------------------------------------------------|--|------|--------| +| Maximum Transmission Power | M | | 9.2.1.40 | | YES | reject | +| Closed Loop Timing Adjustment Mode | O | | 9.2.2.2A | | YES | reject | +| Primary Scrambling Code | M | | 9.2.2.34 | | YES | reject | +| Synchronisation Configuration | | 1 | | | YES | reject | +| >N_INSYNC_IND | M | | 9.2.1.47A | | – | | +| >N_OUTSYNC_IND | M | | 9.2.1.47B | | – | | +| >T_RLFAILURE | M | | 9.2.1.56A | | – | | +| DL TPC Pattern 01 Count | M | | 9.2.2.13A | | YES | reject | +| Primary SCH Information | | 1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Primary SCH Power | M | | DL Power 9.2.1.21 | | – | | +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| Secondary SCH Information | | 1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Secondary SCH Power | M | | DL Power 9.2.1.21 | | – | | +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| Primary CPICH Information | | 1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Primary CPICH power | M | | 9.2.2.33 | | – | | +| >Transmit Diversity Indicator | M | | 9.2.2.53 | | – | | +| Secondary CPICH Information | | 0..CPICHCel
l> | | | EACH | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >DL Scrambling Code | M | | 9.2.2.13 | | – | | +| >FDD DL Channelisation Code Number | M | | 9.2.2.14 | | – | | +| >Secondary CPICH Power | M | | DL Power 9.2.1.21 | | – | | +| >Transmit Diversity Indicator | M | | 9.2.2.53 | | – | | +| Primary CCPCH Information | | 1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >BCH Information | | 1 | Ignored for UTRA operating bands for which Nu is not defined (TS 25.104 [14]). | | – | | +| >>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>BCH Power | M | | DL Power 9.2.1.21 | | – | | +| >STTD Indicator | M | | 9.2.2.48 | | – | | +| Limited Power Increase Information | | 1 | | | YES | reject | +| >Power_Raise_Limit | M | | 9.2.2.29A | | – | | +| >DL_power_averaging_win dow_size | M | | 9.2.2.12A | | – | | +| IPDL Parameter Information | | 0..1 | | | YES | reject | +| >IPDL FDD Parameters | M | | 9.2.2.18C | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | +| Cell Portion Information | | 0..OfCellPortionsPerCell> | | | | | +| >Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >Associated Secondary CPICH | M | | Common Physical Channel ID 9.2.1.13 | | – | | +| >Maximum Transmission Power for Cell Portion | M | | Maximum Transmission Power 9.2.1.40 | | – | | +| MIMO Pilot Configuration | O | | 9.2.2.73 | | YES | reject | +| MIMO Pilot Configuration Extension | O | | 9.2.2.120 | Can only be present if the MIMO Pilot Configuration IE is present | YES | reject | +| MIMO with four transmit antennas Pilot Configuration | O | | 9.2.2.165 | | YES | reject | + +| Range Bound | Explanation | +|-----------------------------------|-------------------------------------------------------------------| +| maxSCPICHCell | Maximum number of Secondary CPICHs that can be defined in a Cell. | +| MaxNrOfCellPortionsPerCell | Maximum number of Cell Portions in a cell | + +#### 9.1.24.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Local Cell ID | M | | 9.2.1.38 | | YES | reject | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation Id | M | | 9.2.1.16 | | YES | reject | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
For 1.28Mcps TDD, if multiple frequencies exist within the cell indicated by C-ID, this IE indicates the frequency of Primary Frequency. | YES | reject | +| Cell Parameter ID | M | | 9.2.3.4 | For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE indicates the preamble code used in the MBSFN Special Time Slot (TS 25.221 [19]). | YES | reject | +| Maximum Transmission Power | M | | 9.2.1.40 | | YES | reject | +| Transmission Diversity Applied | M | | 9.2.3.26 | | YES | reject | +| Sync Case | M | | 9.2.3.18 | | YES | reject | +| Synchronisation Configuration | | 1 | | | YES | reject | +| >N_INSYNC_IND | M | | 9.2.1.47A | | – | | +| >N_OUTSYNC_IND | M | | 9.2.1.47B | | – | | +| >T_RLFAILURE | M | | 9.2.1.56A | | – | | +| DPCH Constant Value | M | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| PUSCH Constant Value | M | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| PRACH Constant Value | M | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| Timing Advance Applied | M | | 9.2.3.22A | | YES | reject | +| SCH Information | | 0..1 | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >CHOICE Sync Case | M | | | | YES | reject | +| >>Case 1 | | | | | | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>Case 2 | | | | | | | +| >>>SCH Time Slot | M | | 9.2.3.17 | | – | | +| >SCH Power | M | | DL Power | | – | | + +| | | | | | | | +|--|--|--|----------|--|--|--| +| | | | 9.2.1.21 | | | | +|--|--|--|----------|--|--|--| + +| | | | | | | | +|------------------------------------|---|-------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| PCCPCH Information | | 0..1 | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >Repetition Period | M | | 9.2.3.16 | | – | | +| >Repetition Length | M | | 9.2.3.15 | | – | | +| >PCCPCH Power | M | | 9.2.3.9 | | – | | +| >SCTD Indicator | M | | 9.2.3.30 | | – | | +| Time Slot Configuration | | 0..15 | | Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD. | GLOBAL | reject | +| >Time Slot | M | | 9.2.3.23 | | – | | +| >Time Slot Status | M | | 9.2.3.25 | | – | | +| >Time Slot Direction | M | | 9.2.3.24 | | – | | +| >MBSFN Cell Parameter ID | O | | Cell Parameter ID 9.2.3.4 | | YES | reject | +| Time Slot Configuration LCR | | 0..7 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot configuration of Primary Frequency. | GLOBAL | reject | +| >Time Slot LCR | M | | 9.2.3.24A | | – | | +| >Time Slot Status | M | | 9.2.3.25 | | – | | +| >Time Slot Direction | M | | 9.2.3.24 | | – | | +| >Time Slot Parameter ID | O | | Cell Parameter ID 9.2.3.4 | Applicable only to MBSFN only mode | YES | reject | +| PCCPCH Information LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]). | YES | reject | + +| | | | | | | | +|---------------------------------------|---|------|-----------|-----------------------------------------------------------------------------|-----|--------| +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >Repetition Period | M | | 9.2.3.16 | | – | | +| >Repetition Length | M | | 9.2.3.15 | | – | | +| >PCCPCH Power | M | | 9.2.3.9 | | – | | +| >SCTD Indicator | M | | 9.2.3.30 | | – | | +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| DwPCH Information | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| >DwPCH Power | M | | 9.2.3.5B | | – | | +| Reference SFN Offset | O | | 9.2.3.14B | | YES | ignore | +| IPDL Parameter Information | | 0..1 | | Applicable to 3.84 Mcps TDD and 7.68 Mcps TDD only | YES | reject | +| >IPDL TDD Parameters | M | | 9.2.3.5D | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | +| IPDL Parameter Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | reject | +| >IPDL TDD Parameters LCR | M | | 9.2.3.5H | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | + +| | | | | | | | +|-----------------------------------------|---|-------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------| +| PCCPCH Information 7.68 Mcps TDD | | 0..1 | | Mandatory for 7.68 Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD. | YES | reject | +| >Common Physical Channel ID 7.68 Mcps | M | | 9.2.3.33 | | – | | +| >TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >Repetition Period | M | | 9.2.3.16 | | – | | +| >Repetition Length | M | | 9.2.3.15 | | – | | +| >PCCPCH Power | M | | 9.2.3.9 | | – | | +| >SCTD Indicator | M | | 9.2.3.30 | | – | | +| SCH Information 7.68Mcps TDD | | 0..1 | | Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84Mcps TDD. | YES | reject | +| >Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >CHOICE Sync Case | M | | | | YES | reject | +| >>Case 1 | | | | | | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>Case 2 | | | | | | | +| >>>SCH Time Slot | M | | 9.2.3.17 | | – | | +| >SCH Power | M | | DL Power 9.2.1.21 | | – | | +| >TSTD Indicator | M | | 9.2.1.64 | | – | | +| MBSFN Only Mode Indicator | O | | 9.2.3.70 | Mandatory for 1.28Mcps TDD when the cell is operating in MBSFN only mode. Not applicable to FDD, 3.84Mcps TDD or 7.68Mcps TDD | YES | reject | +| UARFCN Information LCR | | 0..
| | Mandatory for 1.28Mcps TDD when using multiple frequencies. It indicates the UARFCN and Time Slot configuration information of the Secondary Frequencies. There could be several secondary frequencies | EACH | reject | +| >UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). This IE indicates the frequency of a Secondary Frequency. | – | | +| >Time Slot Configuration LCR | | 1..7 | | This IE indicates the | – | | + +| | | | | | | | +|--------------------------|---|--|---------------------------|---------------------------------------------------|-----|--------| +| | | | | Time Slot configuration of a Secondary Frequency. | | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Time Slot Status | M | | 9.2.3.25 | | – | | +| >>Time Slot Direction | M | | 9.2.3.24 | | – | | +| >>Time Slot Parameter ID | O | | Cell Parameter ID 9.2.3.4 | | YES | reject | + +| Range Bound | Explanation | +|---------------------------|-------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.25 CELL SETUP RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.26 CELL SETUP FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.27 CELL RECONFIGURATION REQUEST + +#### 9.1.27.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|------------------------------------|-------------------------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| Maximum Transmission Power | O | | 9.2.1.40 | | YES | reject | +| Synchronisation Configuration | | 0..1 | | | YES | reject | +| >N_INSYNC_IND | M | | 9.2.1.47A | | – | | +| >N_OUTSYNC_IND | M | | 9.2.1.47B | | – | | +| >T_RLFAILURE | M | | 9.2.1.56A | | – | | +| Primary SCH Information | | 0..1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Primary SCH Power | M | | DL Power 9.2.1.21 | | – | | +| Secondary SCH Information | | 0..1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Secondary SCH Power | M | | DL Power 9.2.1.21 | | – | | +| Primary CPICH Information | | 0..1 | | | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Primary CPICH Power | M | | 9.2.2.33 | | – | | +| Secondary CPICH Information | | 0.. | | | EACH | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Secondary CPICH Power | M | | DL Power 9.2.1.21 | | – | | +| Primary CCPCH Information | | 0..1 | | | YES | reject | +| > BCH Information | | 1 | | | – | | +| >>Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| >>BCH Power | M | | DL Power 9.2.1.21 | | – | | +| IPDL Parameter Information | | 0..1 | | | YES | reject | +| >IPDL FDD Parameters | O | | 9.2.2.18C | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | +| Cell Portion Information | | 0.. | | | EACH | reject | +| >Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >Maximum Transmission Power for Cell Portion | M | | Maximum Transmission Power 9.2.1.40 | | – | | +| MIMO Pilot Configuration | O | | 9.2.2.73 | | YES | reject | +| MIMO Pilot Configuration Extension | O | | 9.2.2.120 | | YES | reject | +| Dormant Mode Indicator | O | | 9.2.1.124 | | YES | reject | +| MIMO with four transmit antennas Pilot Configuration | O | | 9.2.2.165 | | YES | reject | + +| Range Bound | Explanation | +|-----------------------------------|------------------------------------------------------------------| +| maxSCPICHCell | Maximum number of Secondary CPICH that can be defined in a Cell. | +| maxNrOfCellPortionsPerCell | Maximum number of Cell Portions in a cell | + +#### 9.1.27.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| Synchronisation Configuration | | 0..1 | | | YES | reject | +| >N_INSYNC_IND | M | | 9.2.1.47A | | – | | +| >N_OUTSYNC_IND | M | | 9.2.1.47B | | – | | +| >T_RLFAILURE | M | | 9.2.1.56A | | – | | +| Timing Advance Applied | O | | 9.2.3.22A | | YES | reject | +| SCH Information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >SCH Power | M | | DL Power 9.2.1.21 | | – | | +| PCCPCH Information | | 0..1 | | Not applicable to 7.68Mcps TDD only. For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]). | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >PCCPCH Power | M | | 9.2.3.9 | | – | | +| Maximum Transmission Power | O | | 9.2.1.40 | | YES | reject | +| DPCH Constant Value | O | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| PUSCH Constant Value | O | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| PRACH Constant Value | O | | Constant Value 9.2.3.4A | This IE shall be ignored by the Node B. | YES | reject | +| Time Slot Configuration | | 0..15 | | Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD. | GLOBAL | reject | +| >Time Slot | M | | 9.2.3.23 | | – | | +| >Time Slot Status | M | | 9.2.3.25 | | – | | +| >Time Slot Direction | M | | 9.2.3.24 | | – | | +| >MBSFN Cell Parameter ID | O | | Cell Parameter ID 9.2.3.4 | | YES | reject | + +| | | | | | | | +|---------------------------------------|---|------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Time Slot Configuration LCR | | 0..7 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot reconfiguration of Primary Frequency. | GLOBAL | reject | +| >Time Slot LCR | M | | 9.2.3.24A | | – | | +| >Time Slot Status | M | | 9.2.3.25 | | – | | +| >Time Slot Direction | M | | 9.2.3.24 | | – | | +| DwPCH Information | | 0..1 | | Applicable to 1.28Mcps TDD only. | YES | reject | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >DwPCH Power | M | | 9.2.3.5B | | – | | +| IPDL Parameter Information | | 0..1 | | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only | YES | reject | +| >IPDL TDD Parameters | O | | 9.2.3.5D | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | +| IPDL Parameter Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | reject | +| >IPDL TDD Parameters LCR | O | | 9.2.3.5H | | – | | +| >IPDL Indicator | M | | 9.2.1.36F | | – | | +| SCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | reject | +| >Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >SCH Power | M | | DL Power 9.2.1.21 | | – | | +| PCCPCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | reject | +| >Common Physical Channel ID 7.68Mcps | M | | 9.2.3.33 | | – | | +| >PCCPCH Power | M | | 9.2.3.9 | | – | | +| CHOICE UARFCN Adjustment | O | | | Applicable to 1.28Mcps TDD when using multiple frequencies | YES | reject | +| >Add | | | | | | | +| >>UARFCN Information To Add LCR | | 1 | | | – | | +| >>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). This IE indicates the frequency of a Secondary Frequency to add. | – | | + +| | | | | | | | +|-------------------------------------------------|---|-------------------------------|-----------|------------------------------------------------------------------------------------------------------------|-----|--------| +| >>>Time Slot Configuration LCR | | 1..7 | | This IE indicates the Time Slot configuration of a Secondary Frequency to add. | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>Time Slot Status | M | | 9.2.3.25 | | – | | +| >>>>Time Slot Direction | M | | 9.2.3.24 | | – | | +| >Modify | | | | | | | +| >>UARFCN Information To Modify LCR | | 1..
| | there could be several secondary frequencies | – | | +| >>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of a Secondary Frequency to modify. | – | | +| >>>Time Slot Configuration LCR | | 1..7 | | This IE indicates the Time Slot reconfiguration of a Secondary Frequency to modify. | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>Time Slot Status | M | | 9.2.3.25 | | – | | +| >>>>Time Slot Direction | M | | 9.2.3.24 | | – | | +| >Delete | | | | | | | +| >>UARFCN Information To Delete LCR | | 1 | | | – | | +| >>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of Secondary Frequency to delete. | – | | +| Dormant Mode Indicator | O | | 9.2.1.124 | | YES | reject | + +| Range Bound | Explanation | +|---------------------------|-------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.28 CELL RECONFIGURATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.29 CELL RECONFIGURATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.30 CELL DELETION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | + +### 9.1.31 CELL DELETION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.32 RESOURCE STATUS INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------------------|-----------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CHOICE Indication Type | M | | | | YES | ignore | +| >No Failure | | | | | | | +| >>Local Cell Information | | 1.. | | | EACH | ignore | +| >>>Local Cell ID | M | | 9.2.1.38 | | – | | +| >>>Add/Delete Indicator | M | | 9.2.1.1 | | – | | +| >>>DL Or Global Capacity Credit | C-add | | 9.2.1.20B | | – | | +| >>>UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >>>Common Channels Capacity Consumption Law | C-add | | 9.2.1.9A | | – | | +| >>>Dedicated Channels Capacity Consumption Law | C-add | | 9.2.1.20A | | – | | +| >>>Maximum DL Power Capability | C-add | | 9.2.1.39 | | – | | +| >>>Minimum Spreading Factor | C-add | | 9.2.1.47 | | – | | +| >>>Minimum DL Power Capability | C-add | | 9.2.1.46A | | – | | +| >>>Local Cell Group ID | O | | 9.2.1.37A | | – | | +| >>>Reference Clock Availability | O | | 9.2.3.14A | TDD only | YES | ignore | +| >>>Power Local Cell Group ID | O | | 9.2.1.49B | | YES | ignore | +| >>>HSDPA Capability | O | | 9.2.1.31Ga | | YES | ignore | +| >>>E-DCH Capability | O | | 9.2.1.70 | | YES | ignore | +| >>>E-DCH TTI2ms Capability | C-EDCHCap ability | | 9.2.2.13V | FDD only | YES | ignore | +| >>>E-DCH SF Capability | C-EDCHCap ability | | 9.2.2.13W | FDD only | YES | ignore | +| >>>E-DCH HARQ Combining Capability | C-EDCHCap ability | | 9.2.2.13X | FDD only | YES | ignore | +| >>>E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | +| >>>F-DPCH Capability | O | | 9.2.2.16a | FDD only | YES | ignore | +| >>>E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| >>>Continuous Packet Connectivity DTX-DRX Capability | O | | 9.2.2.64 | FDD only | YES | ignore | +| >>>Max UE DTX Cycle | C-DTX-DRXCapa bility | | 9.2.2.95 | FDD only | YES | ignore | +| >>>Continuous Packet Connectivity HS-SCCH less Capability | O | | 9.2.2.65 | FDD only | YES | ignore | + +| | | | | | | | +|--------------------------------------------------------------|----------------------------|--|--------------------------------------|---------------------------|-----|--------| +| >>>MIMO Capability | O | | 9.2.1.118 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>SixtyfourQAM DL Capability | O | | 9.2.1.110 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>MBMS Capability | O | | 9.2.1.86 | | YES | ignore | +| >>>Enhanced FACH Capability | O | | 9.2.1.114 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>Enhanced PCH Capability | C-Enhanced FACHCap ability | | 9.2.1.115 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>SixteenQAM UL Capability | O | | 9.2.2.88 | FDD only | YES | ignore | +| >>>HS-DSCH MAC-d PDU Size Capability | O | | 9.2.1.31C | | YES | ignore | +| >>>MBSFN Only Mode Capability | O | | 9.2.3.71 | 1.28Mcps TDD only | YES | ignore | +| >>>F-DPCH Slot Format Capability | O | | 9.2.2.94 | FDD only | YES | ignore | +| >>>E-DCH MAC-d PDU Size Capability | O | | 9.2.1.74A | | YES | ignore | +| >>>Common E-DCH Capability | O | | 9.2.2.101 | FDD only | YES | Ignore | +| >>>E-AI Capability | C-CommonE DCHCapa bility | | 9.2.2.102 | FDD only | YES | Ignore | +| >>>Enhanced UE DRX Capability | O | | 9.2.1.116 | FDD only | YES | ignore | +| >>>Enhanced UE DRX Capability LCR | O | | Enhanced UE DRX Capability 9.2.1.116 | 1.28Mcps TDD only | YES | ignore | +| >>>E-DPCCH Power Boosting Capability | O | | 9.2.2.109 | | YES | ignore | +| >>>SixtyfourQAM DL and MIMO Combined Capability | O | | 9.2.1.121 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>Multi Cell Capability Info | O | | 9.2.2.113 | FDD only | YES | ignore | +| >>>Semi-Persistent scheduling Capability LCR | O | | 9.2.3.91 | 1.28Mcps TDD only | YES | ignore | +| >>>Continuous Packet Connectivity DRX Capability LCR | O | | 9.2.3.92 | 1.28Mcps TDD only | YES | ignore | +| >>>Common E-DCH HS-DPCCH Capability | C-CommonE DCHCapa bility | | 9.2.2.116 | FDD only | YES | Ignore | +| >>>MIMO Power Offset For S-CPICH Capability | O | | 9.2.2.118 | FDD only | YES | ignore | +| >>>TX Diversity on DL Control Channels by MIMO UE Capability | O | | 9.2.2.121 | FDD only | YES | ignore | +| >>>Single Stream MIMO Capability | O | | 9.2.2.122 | FDD only | YES | Ignore | +| >>>Dual Band Capability Info | O | | 9.2.2.125 | FDD only | YES | ignore | + +| | | | | | | | +|---------------------------------------------------|---|---------------------------------------|------------|-------------------|------|--------| +| >>>Cell Portion Capability LCR | O | | 9.2.3.106 | 1.28Mcps TDD only | YES | ignore | +| >>>Cell Capability Container | O | | 9.2.2.129 | FDD only | YES | ignore | +| >>>TS0 Capability LCR | O | | 9.2.3.109 | 1.28Mcps TDD only | YES | ignore | +| >>>Precoding Weight Set Restriction | O | | 9.2.2.143 | FDD only | YES | ignore | +| >>>Cell Capability Container TDD LCR | O | | 9.2.3.115 | 1.28Mcps TDD only | YES | ignore | +| >>>MU-MIMO Capability Container | O | | 9.2.3.119 | 1.28Mcps TDD only | YES | ignore | +| >>>Adaptive Special Burst Power Capability LCR | O | | 9.2.3.122 | 1.28Mcps TDD only | YES | ignore | +| >>Local Cell Group Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >>>Local Cell Group ID | M | | 9.2.1.37A | | – | | +| >>>DL Or Global Capacity Credit | M | | 9.2.1.20B | | – | | +| >>>UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >>>Common Channels Capacity Consumption Law | M | | 9.2.1.9A | | – | | +| >>>Dedicated Channels Capacity Consumption Law | M | | 9.2.1.20A | | – | | +| >>>E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | +| >>>E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| >>Power Local Cell Group Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >>>Power Local Cell Group ID | M | | 9.2.1.49B | | – | | +| >>>Maximum DL Power Capability | M | | 9.2.1.39 | | – | | +| >Service Impacting | | | | | | | +| >>Local Cell Information | | 0..<maxLocalCellinNodeB> | | | EACH | ignore | +| >>>Local Cell ID | M | | 9.2.1.38 | | – | | +| >>>DL Or Global Capacity Credit | O | | 9.2.1.20B | | – | | +| >>>UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >>>Common Channels Capacity Consumption Law | O | | 9.2.1.9A | | – | | +| >>>Dedicated Channels Capacity Consumption Law | O | | 9.2.1.20A | | – | | +| >>>Maximum DL Power Capability | O | | 9.2.1.39 | | – | | +| >>>Minimum Spreading Factor | O | | 9.2.1.47 | | – | | +| >>>Minimum DL Power Capability | O | | 9.2.1.46A | | – | | + +| | | | | | | | +|-----------------------------------------------------------|----------------------------|--|------------|---------------------------|-----|--------| +| >>>Reference Clock Availability | O | | 9.2.3.14A | TDD only | YES | ignore | +| >>>HSDPA Capability | O | | 9.2.1.31Ga | | YES | ignore | +| >>>E-DCH Capability | O | | 9.2.1.70 | | YES | ignore | +| >>>E-DCH TTI2ms Capability | C-EDCHCap ability | | 9.2.2.13V | FDD only | YES | ignore | +| >>>E-DCH SF Capability | C-EDCHCap ability | | 9.2.2.13W | FDD only | YES | ignore | +| >>>E-DCH HARQ Combining Capability | C-EDCHCap ability | | 9.2.2.13X | FDD only | YES | ignore | +| >>>E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | +| >>>F-DPCH Capability | O | | 9.2.2.16a | | YES | ignore | +| >>>E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| >>>Continuous Packet Connectivity DTX-DRX Capability | O | | 9.2.2.64 | FDD only | YES | ignore | +| >>>Max UE DTX Cycle | C-DTX-DRXCapa bility | | 9.2.2.95 | FDD only | YES | ignore | +| >>>Continuous Packet Connectivity HS-SCCH less Capability | O | | 9.2.2.65 | FDD only | YES | ignore | +| >>>MIMO Capability | O | | 9.2.1.118 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>SixtyfourQAM DL Capability | O | | 9.2.1.110 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>MBMS Capability | O | | 9.2.1.86 | | YES | ignore | +| >>>Enhanced FACH Capability | O | | 9.2.1.114 | FDD only and 1.28Mcps TDD | YES | ignore | +| >>>Enhanced PCH Capability | C-Enhanced FACHCap ability | | 9.2.1.115 | FDD only and 1.28Mcps TDD | YES | ignore | +| >>>SixteenQAM UL Capability | O | | 9.2.2.88 | FDD only | YES | ignore | +| >>>HS-DSCH MAC-d PDU Size Capability | O | | 9.2.1.31IC | | YES | ignore | +| >>>MBSFN Only Mode Capability | O | | 9.2.3.71 | 1.28Mcps TDD only | YES | ignore | +| >>>F-DPCH Slot Format Capability | O | | 9.2.2.94 | FDD only | YES | ignore | +| >>>E-DCH MAC-d PDU Size Capability | O | | 9.2.1.74A | | YES | ignore | +| >>>Common E-DCH Capability | O | | 9.2.2.101 | FDD only | YES | ignore | +| >>>E-AI Capability | C-CommonE DCHCapa bility | | 9.2.2.102 | FDD only | YES | ignore | +| >>>Enhanced UE DRX Capability | O | | 9.2.1.116 | FDD only | YES | ignore | + +| | | | | | | | +|--------------------------------------------------------------|--------------------------|----------------------------------------|--------------------------------------|---------------------------|------|--------| +| >>>Enhanced UE DRX Capability LCR | O | | Enhanced UE DRX Capability 9.2.1.116 | 1.28Mcps TDD only | YES | ignore | +| >>>E-DPCCH Power Boosting Capability | O | | 9.2.2.109 | | YES | ignore | +| >>>SixtyfourQAM DL and MIMO Combined Capability | O | | 9.2.1.121 | FDD and 1.28Mcps TDD only | YES | ignore | +| >>>Multi Cell Capability Info | O | | 9.2.2.113 | FDD only | YES | ignore | +| >>>Semi-Persistent scheduling Capability LCR | O | | 9.2.3.91 | 1.28Mcps TDD only | YES | ignore | +| >>>Continuous Packet Connectivity DRX Capability LCR | O | | 9.2.3.92 | 1.28Mcps TDD only | YES | ignore | +| >>>Common E-DCH HS-DPCCH Capability | C-CommonE DCHCapa bility | | 9.2.2.116 | FDD only | YES | Ignore | +| >>>MIMO Power Offset For S-CPICH Capability | O | | 9.2.2.118 | FDD only | YES | ignore | +| >>>TX Diversity on DL Control Channels by MIMO UE Capability | O | | 9.2.2.121 | FDD only | YES | ignore | +| >>>Single Stream MIMO Capability | O | | 9.2.2.122 | FDD only | YES | ignore | +| >>>Dual Band Capability Info | O | | 9.2.2.125 | FDD only | YES | ignore | +| >>>Cell Portion Capability LCR | O | | 9.2.3.106 | 1.28Mcps TDD only | YES | ignore | +| >>>Cell Capability Container | O | | 9.2.2.129 | FDD only | YES | ignore | +| >>>TS0 Capability LCR | O | | 9.2.3.109 | 1.28Mcps TDD only | YES | ignore | +| >>>Precoding Weight Set Restriction | O | | 9.2.2.143 | FDD only | YES | ignore | +| >>>Cell Capability Container TDD LCR | O | | 9.2.3.115 | 1.28Mcps TDD only | YES | ignore | +| >>>MU-MIMO Capability Container | O | | 9.2.3.119 | 1.28Mcps TDD only | YES | ignore | +| >>>Adaptive Special Burst Power Capability LCR | O | | 9.2.3.122 | 1.28Mcps TDD only | YES | ignore | +| >>Local Cell Group Information | | 0..<maxLocalCellinN odeB> | | | EACH | ignore | +| >>>Local Cell Group ID | M | | 9.2.1.37A | | – | | +| >>>DL Or Global Capacity Credit | O | | 9.2.1.20B | | – | | +| >>>UL Capacity Credit | O | | 9.2.1.65A | | – | | +| >>>Common Channels Capacity Consumption Law | O | | 9.2.1.9A | | – | | +| >>>Dedicated Channels Capacity Consumption Law | O | | 9.2.1.20A | | – | | +| >>>E-DCH Capacity Consumption Law | O | | 9.2.2.13Ja | FDD only | YES | ignore | + +| | | | | | | | +|-------------------------------------------------------|---|------------------------------------|-------------------------------------------------------|------------------|------|--------| +| >>>E-DCH TDD Capacity Consumption Law | O | | 9.2.3.60 | TDD only | YES | ignore | +| >>Communication Control Port Information | | 0..<maxC CPinNode B> | | | EACH | ignore | +| >>>Communication Control Port ID | M | | 9.2.1.15 | | – | | +| >>>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>>Availability Status | M | | 9.2.1.2 | | – | | +| >>Cell Information | | 0..<maxCellinNode B> | | | EACH | ignore | +| >>>C-ID | M | | 9.2.1.9 | | – | | +| >>>Resource Operational State | O | | 9.2.1.52 | | – | | +| >>>Availability Status | O | | 9.2.1.2 | | – | | +| >>>Primary SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | FDD only | YES | ignore | +| >>>Secondary SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | FDD only | YES | ignore | +| >>>Primary CPICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | FDD only | YES | ignore | +| >>>Secondary CPICH Information | | 0..<maxS CPICHCell /> | | FDD only | EACH | ignore | +| >>>>Secondary CPICH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >>>Primary CCPCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| >>>BCH Information | O | | Common Transport Channel Status Information 9.2.1.14B | | YES | ignore | +| >>>Secondary CCPCH Information | | 0..<maxS CCPCHCell /> | | See note 1 below | EACH | ignore | +| >>>>Secondary CCPCH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | + +| | | | | | | | +|----------------------------------|---|--------------------------------|-------------------------------------------------------|--------------------------------------------------|------|--------| +| >>>PCH Information | O | | Common Transport Channel Status Information 9.2.1.14B | | YES | ignore | +| >>>PICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| >>> FACH Information | | 0..<maxFACHCell> | | | EACH | ignore | +| >>>>FACH Individual Information | M | | Common Transport Channel Status Information 9.2.1.14B | | – | | +| >>> PRACH Information | | 0..<maxPRACHCell> | | | EACH | ignore | +| >>>>PRACH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >>> RACH Information | | 0..<maxPRACHCell> | | | EACH | ignore | +| >>>>RACH Individual Information | M | | Common Transport Channel Status Information 9.2.1.14B | | – | | +| >>> AICH Information | | 0..<maxPRACHCell> | | FDD only | EACH | ignore | +| >>>>AICH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >>>Not Used 1 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >>>Not Used 2 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >>>Not Used 3 | O | | NULL | This item shall not be used. Ignore if received. | – | | +| >>>Not Used 4 | O | | NULL | This item shall not be used. Ignore if received. | – | | + +| | | | | | | | +|----------------------------------|---|--------------------------------------|------------------------------------------------------|----------------------------------------------------------------------------------------------------|------|--------| +| >>>SCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to 3.84Mcps TDD only | YES | ignore | +| >>>FPACH Information | | 0..<maxFPACHCell> | | Applicable to 1.28Mcps TDD only | EACH | ignore | +| >>>>FPACH Individual Information | M | | Common Physical Channel Status Information 9.2.1.13A | | – | | +| >>>DwPCH Information | O | | Common Physical Channel Status Information 9.2.1.13A | Applicable to 1.28Mcps TDD only | YES | ignore | +| >>>HS-DSCH Resources Information | | 0..<maxFrequencyinCell> | | See note 2 below | EACH | ignore | +| >>>>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>>>Availability Status | M | | 9.2.1.2 | | – | | +| >>>>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| >>>MICH Information | O | | Common Physical Channel Status Information 9.2.1.13A | | YES | ignore | +| >>>E-DCH Resources Information | | 0..<maxFrequencyinCell> | | See note 2 below | EACH | ignore | +| >>>>Resource Operational State | M | | 9.2.1.52 | | – | | +| >>>>Availability Status | M | | 9.2.1.2 | | – | | +| >>>>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| >>>PLCCH Information | | 0..<maxPLCCHCell> | | Applicable to 1.28Mcps TDD only | EACH | ignore | + +| | | | | | | | +|-----------------------------------------------------------|---|----------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------|------|--------| +| >>>>PLCCH
Individual Information | M | | Common
Physical
Channel
Status
Information
9.2.1.13A | | – | | +| >>>Primary CCPCH
Information 7.68Mcps | O | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | YES | ignore | +| >>>Secondary CCPCH
Information 7.68Mcps | | 0..<maxS
CCPCHC
ell768> | | | EACH | ignore | +| >>>>Secondary
CCPCH Individual
Information 7.68Mcps | M | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | – | | +| >>>PICH Information
7.68Mcps | O | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | YES | ignore | +| >>>PRACH
Information 7.68Mcps | | 0..<maxP
RACHCell
> | | | EACH | ignore | +| >>>>PRACH
Individual Information
7.68Mcps | M | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | – | | +| >>>SCH Information
7.68Mcps | O | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | Applicable to
7.68Mcps TDD
only | YES | ignore | +| >>>MICH Information
7.68Mcps | O | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | YES | ignore | +| >>>E-RUCCH
Information | | 0..<maxE-
RUCCHC
ell> | | Applicable to
3.84Mcps TDD
only | EACH | ignore | +| >>>>E-RUCCH
Individual Information | M | | Common
Physical
Channel
Status
Information
9.2.1.13A | | – | | +| >>>E-RUCCH
Information 7.68Mcps | | 0..<maxE-
RUCCHC
ell> | | Applicable to
7.68Mcps TDD
only | EACH | ignore | + +| | | | | | | | +|---------------------------------------------------|---|-------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|------|--------| +| >>>>E-RUCCH
Individual Information
7.68Mcps | M | | Common
Physical
Channel
Status
Information
7.68Mcps
9.2.3.36 | | – | | +| >>>UARFCN
Information LCR | | 0..<maxFr
equencyin
Cell> | | Applicable to
1.28Mcps TDD
when using
multiple
frequencies. | EACH | ignore | +| >>>>UARFCN | M | | 9.2.1.65 | Corresponds to
Nt (TS 25.105
[15]). | – | | +| >>>>Resource
Operational State | M | | 9.2.1.52 | | – | | +| >>>>Availability
Status | M | | 9.2.1.2 | | – | | +| >>>>Cause | O | | 9.2.1.6 | | – | | +| >>>UpPCH
Information LCR | | 0..<maxFr
equencyin
Cell> | | Applicable to
1.28Mcps TDD
only. | EACH | ignore | +| >>>>UARFCN | O | | 9.2.1.65 | Mandatory for
1.28Mcps TDD
when using
multiple
frequencies.
Corresponds to
Nt (TS 25.105
[15]). | – | | +| >>>>UpPCH Position
LCR | M | | 9.2.3.4Q | | – | | +| >>>>Resource
Operational State | M | | 9.2.1.52 | | – | | +| >>>>Availability
Status | M | | 9.2.1.2 | | – | | +| >>Power Local Cell
Group Information | | 0..<maxLo
calCellinN
odeB> | | | EACH | ignore | +| >>>Power Local Cell
Group ID | M | | 9.2.1.49B | | – | | +| >>>Maximum DL Power
Capability | M | | 9.2.1.39 | | – | | +| Cause | O | | 9.2.1.6 | | YES | ignore | + +NOTE 1: This information element is a simplified representation of the ASN.1. [TDD - Repetitions 1 to 8 and repetitions 9 to maxSCCPCHCell are represented by separate ASN.1 structures.] Furthermore, maxSCCPCHCell has different values in the ASN.1 for FDD and for each of the two TDD options. + +NOTE 2: For 1.28Mcps TDD when using multiple frequencies, this information element for Repetition 1 and repetition 2 through maxFrequencyinCell are represented by respective ASN.1 structures with different criticalities. + +| Condition | Explanation | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| add | The IE shall be present if the Add/Delete Indicator IE is set to "Add". | +| EDCHCapability | The IE shall be present if the E-DCH Capability IE is set to "E-DCH Capable". | +| EnhancedFACHCapability | The IE shall be present if the Enhanced FACH Capability IE is set to "Enhanced FACH Capable". | +| DTX-DRXCapability | The IE shall be present if the Continuous Packet Connectivity DTX-DRX Capability IE is present and set to " Continuous Packet Connectivity DTX-DRX Capable". | +| CommonEDCHCapability | The IE shall be present if the Common E-DCH Capability IE is set to "Common E-DCH Capable". | + +| Range Bound | Explanation | +|----------------------------|----------------------------------------------------------------------------| +| maxLocalCellinNodeB | Maximum number of Local Cells that can exist in the Node B | +| maxCellinNodeB | Maximum number of C-IDs that can be configured in the Node B | +| maxSCPICHCell | Maximum number of Secondary CPICHs that can be defined in a Cell. | +| maxSCCPCHCell | Maximum number of Secondary CCPCHs that can be defined in a Cell. | +| maxFACHCell | Maximum number of FACHs that can be defined in a Cell | +| maxPRACHCell | Maximum number of PRACHs and AICHs that can be defined in a Cell | +| maxCCPinNodeB | Maximum number of Communication Control Ports that can exist in the Node B | +| maxFPACHCell | Maximum number of FPACHs that can be defined in a Cell | +| maxPLCCHCell | Maximum number of PLCCHs that can be defined in a Cell | +| maxE-RUCCHCell | Maximum number of E-RUCCHs that can be defined in a Cell | +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.33 SYSTEM INFORMATION UPDATE REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|-------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| BCCH Modification Time | O | | 9.2.1.3 | | YES | reject | +| MIB/SB/SIBInformation | | 1.. | | | GLOBAL | reject | +| >IB Type | M | | 9.2.1.35 | | – | | +| >IB OC ID | M | | 9.2.1.31A | In one message, every occurrence of IB Type can only be deleted once and/or added once. | – | | +| >CHOICE IB Deletion Indicator | M | | | | – | | +| >>No Deletion | | | | | | | +| >>>SIB Originator | C-SIB | | 9.2.1.55 | | – | | +| >>>IB SG REP | O | | 9.2.1.34 | | – | | +| >>>Segment Information | | 1.. | | | GLOBAL | reject | +| >>>>IB SG POS | O | | 9.2.1.33 | | – | | +| >>>>Segment Type | C-CRNCOrigination | | 9.2.1.53B | | – | | +| >>>>IB SG DATA | C-CRNCOrigination | | 9.2.1.32 | | – | | +| >>Deletion | | | NULL | | | | +| BCH mapped on SCCPCH Indication | O | | ENUMERATED (InUse) | | YES | reject | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------| +| maxIB | Maximum number of information Blocks supported in one message | +| maxIBSEG | Maximum number of segments for one Information Block | + +| Condition | Explanation | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CRNCOriGination | The IE shall be present if the SIB Originator IE is set to "CRNC" or if the IB Type IE is set to "MIB", "SB1" or "SB2". | +| SIB | The IE shall be present if the IB Type IE is set to "SIB". | + +### 9.1.34 SYSTEM INFORMATION UPDATE RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.35 SYSTEM INFORMATION UPDATE FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.36 RADIO LINK SETUP REQUEST + +9.1.36.1 FDD message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|--------------|------------------|------------------------------|---------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | reject | +| UL DPCH Information | | 1 | | | YES | reject | +| >UL Scrambling Code | M | | 9.2.2.59 | | – | | +| >Min UL Channelisation Code Length | M | | 9.2.2.22 | | – | | +| >Max Number of UL DPDCHs | C-CodeLen | | 9.2.2.21 | | – | | +| >Puncture Limit | M | | 9.2.1.50 | For UL | – | | +| >TFCS | M | | 9.2.1.58 | For UL | – | | +| >UL DPCCH Slot Format | M | | 9.2.2.57 | | – | | +| >UL SIR Target | M | | UL SIR 9.2.1.67A | | – | | +| >Diversity Mode | M | | 9.2.2.9 | | – | | +| >Not Used | O | | NULL | | – | | +| >Not Used | O | | NULL | | – | | +| >DPC Mode | O | | 9.2.2.13C | | YES | reject | +| >UL DPDCH Indicator For E-DCH Operation | O | | 9.2.2.61 | This IE may be present without the presence of the E-DPCH Information IE | YES | reject | +| DL DPCH Information | | 0..1 | | | YES | reject | +| >TFCS | M | | 9.2.1.58 | For DL | – | | +| >DL DPCH Slot Format | M | | 9.2.2.10 | | – | | +| >TFCI Signalling Mode | M | | 9.2.2.50 | | – | | +| >TFCI Presence | C-SlotFormat | | 9.2.1.57 | | – | | +| >Multiplexing Position | M | | 9.2.2.23 | | – | | +| >Not Used | O | | NULL | | – | | +| >Not Used | O | | NULL | | – | | +| >Power Offset Information | | 1 | | | – | | +| >>PO1 | M | | Power Offset 9.2.2.29 | Power offset for the TFCI bits | – | | +| >>PO2 | M | | Power Offset 9.2.2.29 | Power offset for the TPC bits | – | | +| >>PO3 | M | | Power Offset 9.2.2.29 | Power offset for the pilot bits | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Limited Power Increase | M | | 9.2.2.18A | | – | | +| >Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| DCH Information | M | | DCH FDD Information 9.2.2.4D | | YES | reject | +| RL Information | | 1.. | | | EACH | notify | +| >RL ID | M | | 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >First RLS Indicator | M | | 9.2.2.16A | | – | | +| >Frame Offset | M | | 9.2.1.31 | | – | | + +| | | | | | | | +|-----------------------------------------------|------------------|-------------|-------------------------------------|--------------------------------------------|-----|--------| +| >Chip Offset | M | | 9.2.2.2 | | – | | +| >Propagation Delay | O | | 9.2.2.35 | | – | | +| >Diversity Control Field | C-NotFirstRL | | 9.2.1.25 | | – | | +| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | – | | +| >Initial DL Transmission Power | M | | DL Power 9.2.1.21 | Initial power on DPCH or on F-DPCH | – | | +| >Maximum DL Power | M | | DL Power 9.2.1.21 | Maximum allowed power on DPCH or on F-DPCH | – | | +| >Minimum DL Power | M | | DL Power 9.2.1.21 | Minimum allowed power on DPCH or on F-DPCH | – | | +| >Not Used | O | | NULL | | – | | +| >Transmit Diversity Indicator | C-Diversity mode | | 9.2.2.53 | | – | | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >Delayed Activation | O | | 9.2.1.24C | | YES | reject | +| >Primary CPICH Usage For Channel Estimation | O | | 9.2.2.33A | | YES | ignore | +| >Secondary CPICH Information | O | | Common Physical Channel ID 9.2.1.13 | | YES | ignore | +| >E-DCH RL Indication | O | | 9.2.2.13De | | YES | reject | +| >RL Specific E-DCH Information | O | | 9.2.2.39a | | YES | ignore | +| >Synchronisation Indicator | O | | 9.2.2.48A | | YES | ignore | +| >Extended Propagation Delay | O | | 9.2.2.35A | | YES | ignore | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | YES | reject | +| > HS-DSCH Preconfiguration Setup | O | | 9.2.2.112 | | YES | ignore | +| >E-RNTI | O | | 9.2.1.75 | | YES | ignore | +| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.144 | | YES | ignore | +| >F-TPICH Information | O | | 9.2.2.160 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | +| Transmission Gap Pattern Sequence Information | O | | 9.2.2.53A | | YES | reject | +| Active Pattern Sequence Information | O | | 9.2.2.A | | YES | reject | +| DL Power Balancing Information | O | | 9.2.2.12B | | YES | ignore | +| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.18D | | YES | reject | +| HS-DSCH RNTI | C-InfoHSDS CH | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | C-InfoHSDS CH | | RL ID 9.2.1.53 | | YES | reject | +| E-DPCH Information | | 0..1 | | | YES | reject | + +| | | | | | | | +|---------------------------------------------------------|-------------|----------------------|-----------------------|--------------------------------------------------------------------|------|--------| +| >Maximum Set of E-DPDCHs | M | | 9.2.2.20C | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >E-TFCS Information | M | | 9.2.2.13Dh | | – | | +| >E-TTI | M | | 9.2.2.13Di | | – | | +| >E-DPCCH Power Offset | M | | 9.2.2.13Dj | | – | | +| >E-RGCH 2-Index-Step Threshold | M | | 9.2.2.13lg | | – | | +| >E-RGCH 3-Index-Step Threshold | M | | 9.2.2.13lh | | – | | +| >HARQ Info for E-DCH | M | | 9.2.2.18ba | | – | | +| >HS-DSCH Configured Indicator | M | | 9.2.2.18Ca | | – | | +| >E-RNTI | O | | 9.2.1.75 | Shall be ignored if E-RNTI IE is included in the RL Information IE | YES | reject | +| >Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.114 | | YES | ignore | +| E-DCH FDD Information | C-EDPCHInfo | | 9.2.2.13Da | | YES | reject | +| Serving E-DCH RL | O | | 9.2.2.48B | | YES | reject | +| F-DPCH Information | | 0..1 | | | YES | reject | +| >Power Offset Information | | 1 | | | – | | +| >>PO2 | M | | Power Offset 9.2.2.29 | This IE shall be ignored by Node B. | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Limited Power Increase | M | | 9.2.2.18A | | – | | +| >Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| Initial DL DPCH Timing Adjustment Allowed | O | | 9.2.2.18K | | YES | ignore | +| DCH Indicator For E-DCH-HSDPA Operation | O | | 9.2.2.4F | | YES | reject | +| Serving Cell Change CFN | O | | CFN 9.2.1.7 | | YES | reject | +| Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.66 | | YES | reject | +| Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.68 | | YES | reject | +| Additional HS Cell Information RL Setup | | 0.. | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >HS-DSCH FDD Secondary Serving Information | M | | 9.2.2.18Da | | – | | +| UE Aggregate Maximum Bit Rate | O | | 9.2.1.123 | | YES | ignore | +| Additional E-DCH Cell Information RL Setup Req | | 0..1 | | For E-DCH on multiple frequencies in | YES | reject | + +| | | | | | | | +|----------------------------------------------------|---|--------------------|-----------|-------------------------------------------------------------------|-----|--------| +| | | | | this Node B. | | | +| >Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.130 | | – | | +| >Additional E-DCH Cell Information Setup | | 1.. | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>Additional E-DCH FDD Setup Information | M | | 9.2.2.131 | | – | | +| Usefulness of Battery Optimization | O | | 9.2.2.147 | | YES | ignore | +| UL CLTD Information | O | | 9.2.2.152 | | YES | reject | +| E-DCH Decoupling Indication | O | | 9.2.2.194 | | YES | reject | +| DCH Enhancements Information | O | | 9.2.2.196 | | YES | reject | +| Radio Links without DPCH/F-DPCH Indication | O | | 9.2.2.201 | | YES | reject | +| UL DPCCH2 Information | O | | 9.2.2.203 | | YES | reject | +| Downlink TPC enhancements Information | O | | 9.2.2.214 | | YES | reject | + +| Condition | Explanation | +|----------------|------------------------------------------------------------------------------------------------------------| +| CodeLen | The IE shall be present if Min UL Channelisation Code Length IE equals to 4. | +| NotFirstRL | The IE shall be present if the RL is not the first one in the RL Information IE. | +| SlotFormat | The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. | +| Diversity mode | The IE shall be present if Diversity Mode IE in UL DPCH Information IE is not set to "none". | +| InfoHSDSCH | The IE shall be present if HS-DSCH Information IE is present. | +| EDPCHInfo | This IE shall be present if E-DPCH Information IE is present. | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.36.2 TDD message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|----------------------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | reject | +| UL CCTrCH Information | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | M | | 9.2.1.58 | | – | | +| >TFCI Coding | M | | 9.2.3.22 | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >UL DPCH Information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information | M | | 9.2.3.26C | | – | | +| >UL DPCH Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information LCR | M | | 9.2.3.26E | | – | | +| >UL SIR Target | O | | UL SIR 9.2.1.67A | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >TDD TPC UL Step Size | O | | 9.2.3.21a | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >UL DPCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information 7.68Mcps | M | | 9.2.3.38 | | – | | +| DL CCTrCH Information | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | M | | 9.2.1.58 | | – | | +| >TFCI Coding | M | | 9.2.3.22 | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >TDD TPC DL Step Size | M | | 9.2.3.21 | | – | | +| >TPC CCTrCH List | | 0..<maxNrOfCCTrCHs> | | List of uplink CCTrCH which | – | | + +| | | | | | | | +|--|--|---------------|--|-------------|--|--| +| | | Hs> | | provide TPC | | | +|--|--|---------------|--|-------------|--|--| + +| | | | | | | | +|---------------------------------------------|---|------|-------------------------------------|-----------------------------------------------------------|-----|--------| +| >>TPC CCTrCH ID | M | | CCTrCH ID
9.2.3.3 | | – | | +| >DL DPCH information | | 0..1 | | Applicable to
3.84Mcps TDD
only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot
Information | M | | 9.2.3.4E | | – | | +| >DL DPCH information
LCR | | 0..1 | | Applicable to
1.28Mcps TDD
only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot
Information LCR | M | | 9.2.3.4O | | – | | +| >>TSTD Indicator | M | | 9.2.1.64 | | – | | +| >CCTrCH Initial DL
Transmission Power | O | | DL Power
9.2.1.21 | | YES | ignore | +| >CCTrCH Maximum DL
Transmission Power | O | | DL Power
9.2.1.21 | | YES | ignore | +| >CCTrCH Minimum DL
Transmission Power | O | | DL Power
9.2.1.21 | | YES | ignore | +| >DL DPCH information
7.68Mcps | | 0..1 | | Applicable to
7.68Mcps TDD
only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot
Information 7.68Mcps | M | | 9.2.3.39 | | – | | +| DCH Information | O | | DCH TDD
Information
9.2.3.4C | | YES | reject | +| DSCH Information | O | | DSCH TDD
Information
9.2.3.5A | | YES | reject | +| USCH Information | O | | 9.2.3.28 | | YES | reject | +| RL Information | | 1 | | | YES | reject | +| >RL ID | M | | 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Frame Offset | M | | 9.2.1.31 | | – | | +| >Special Burst Scheduling | M | | 9.2.3.18A | | – | | +| >Initial DL Transmission
Power | M | | DL Power
9.2.1.21 | | – | | +| >Maximum DL Power | M | | DL Power
9.2.1.21 | | – | | +| >Minimum DL Power | M | | DL Power
9.2.1.21 | | – | | +| >DL Time Slot ISCP Info | O | | 9.2.3.4F | Applicable to
3.84Mcps TDD
and 7.68Mcps
TDD only | – | | +| >DL Time Slot ISCP Info
LCR | O | | 9.2.3.4P | Applicable to
1.28Mcps TDD
only | YES | reject | +| >RL Specific DCH
Information | O | | 9.2.1.53G | | YES | ignore | +| >Delayed Activation | O | | 9.2.1.24C | | YES | reject | +| >UL Synchronisation | | 0..1 | | Mandatory for | YES | reject | + +| | | | | | | | +|-----------------------------------------------------|---------------|------|----------------------------------|-------------------------------------------------------------------------------------------------|-----|--------| +| Parameters LCR | | | | 1.28Mcps TDD.
Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | | | +| >>Uplink Synchronisation Step Size | M | | 9.2.3.26H | | – | | +| >>Uplink Synchronisation Frequency | M | | 9.2.3.26G | | – | | +| >UARFCN | O | | 9.2.1.65 | Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]). | YES | reject | +| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.5F | | YES | reject | +| HS-DSCH RNTI | C-InfoHSDS CH | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | C-InfoHSDS CH | | RL ID 9.2.1.53 | | YES | reject | +| PDSCH-RL-ID | O | | RL ID 9.2.1.53 | | YES | ignore | +| E-DCH Information | | 0..1 | | 3.84Mcps TDD only | YES | reject | +| >E-PUCH Information | M | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information TDD | O | | 9.2.3.48 | | – | | +| >E-DCH TDD Information | M | | 9.2.3.49 | | – | | +| E-DCH Serving RL | O | | RL ID 9.2.1.53 | | YES | reject | +| E-DCH Information 7.68Mcps | | 0..1 | | 7.68Mcps TDD only | YES | reject | +| >E-PUCH Information | M | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information 7.68Mcps TDD | O | | 9.2.3.64 | | – | | +| >E-DCH TDD Information 7.68Mcps | M | | 9.2.3.65 | | – | | +| E-DCH Information 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | YES | reject | +| >E-PUCH Information LCR | M | | 9.2.3.45a | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information LCR TDD | O | | 9.2.3.48a | | – | | +| >E-DCH TDD Information LCR | M | | 9.2.3.49a | | – | | +| Power Control GAP | O | | INTEGER (1..255) | Unit: Number of subframes
Applicable to 1.28Mcps TDD only | YES | ignore | + +| | | | | | | | +|----------------------------------------------------|---|------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.93 | 1.28 Mcps TDD only | YES | reject | +| HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.96 | 1.28 Mcps TDD only | YES | reject | +| E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.97 | 1.28 Mcps TDD only | YES | reject | +| Idle Interval Information | O | | 9.2.3.102 | TDD only | YES | ignore | +| UE Selected MBMS Service Information | O | | 9.2.3.104 | This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only. | YES | ignore | +| HS-SCCH TPC step size | O | | TDD TPC DL Step Size 9.2.3.21 | 1.28 Mcps TDD only. This IE is mandatory if DL CCTrCH Information IE and E-DCH Information 1.28Mcps IE are both absent. | YES | ignore | +| DCH Measurement Occasion Information | O | | 9.2.3.111 | Applicable for 1.28 Mcps TDD. | YES | reject | +| HS-DSCH-RNTI for FACH | O | | HS-DSCH RNTI 9.2.1.31J | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only | YES | reject | +| >Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.113 | 1.28 Mcps TDD only | – | | +| >Multi-Carrier E-DCH Information LCR | M | | 9.2.3.112 | 1.28 Mcps TDD only | – | | +| MU-MIMO Information | O | | 9.2.3.116 | 1.28 Mcps TDD only | YES | ignore | +| UE support of non-rectangular resource allocation | O | | ENUMERATED (support) | 1.28 Mcps TDD only. The absence of this IE indicates that the UE does not support the non-rectangular resource allocation. | YES | ignore | + +| Range Bound | Explanation | +|-----------------------|------------------------------| +| maxNrOfCCTrCHs | Number of CCTrCHs for one UE | + +| Condition | Explanation | +|------------|----------------------------------------------------------------------| +| InfoHSDSCH | The IE shall be present if HS-DSCH Information IE is present. | + +### 9.1.37 RADIO LINK SETUP RESPONSE + +9.1.37.1 FDD message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------|----------|-----------------------|--------------------------------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| Communication Control Port ID | M | | 9.2.1.15 | | YES | ignore | +| RL Information Response | | 1.. | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >RL Set ID | M | | 9.2.2.39 | | – | | +| >Received Total Wide Band Power | M | | 9.2.2.39A | | – | | +| >CHOICE Diversity Indication | M | | | | – | | +| >>Combining | | | | | | | +| >>>RL ID | M | | 9.2.1.53 | Reference RL ID for the combining | – | | +| >>Non Combining or First RL | | | | | | | +| >>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >Not Used | O | | NULL | | – | | +| >SSDT Support Indicator | M | | 9.2.2.46 | | – | | +| >DL Power Balancing Activation Indicator | O | | 9.2.2.12C | | YES | ignore | +| >E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment 9.2.2.10A | | YES | ignore | +| > HS-DSCH Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| HS-DSCH Information Response | O | | HS-DSCH FDD Information Response 9.2.2.18E | | YES | ignore | +| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.69 | | YES | ignore | +| Additional HS Cell Information Response | | 0.. | | For secondary serving HS-DSCH cell. Max | EACH | ignore | + +| | | | | | | | +|-----------------------------------------------------------|---|----------------------------|-------------------|---------------------------------------------------------------------------------|------|--------| +| | | | | 7 in this 3GPP release. | | | +| >HS-PDSCH RL ID | M | | RL ID
9.2.1.53 | | – | | +| >HS-DSCH FDD
Secondary Serving
Information Response | M | | 9.2.2.18EA | | – | | +| Additional E-DCH Cell
Information Response | | 0..OfEDCH-1
> | | E-DCH on
Secondary
uplink
frequency -
max 1 in this
3GPP release | EACH | ignore | +| >Additional E-DCH FDD
Information Response | M | | 9.2.2.135 | | – | | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.37.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|-------|-------------------------------------------|------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| Communication Control Port ID | M | | 9.2.1.15 | | YES | ignore | +| RL Information Response | | 0..1 | | Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD. | YES | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >UL Time Slot ISCP Info | M | | 9.2.3.26D | | – | | +| >UL PhysCH SF Variation | M | | 9.2.3.26B | | – | | +| >DCH Information Response | O | | 9.2.1.20C | | YES | ignore | +| >DSCH Information Response | O | | 9.2.3.5b | | YES | ignore | +| >USCH Information Response | O | | 9.2.3.29 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| RL Information Response LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >UL Time Slot ISCP Info LCR | M | | 9.2.3.26F | | – | | +| >UL PhysCH SF Variation | M | | 9.2.3.26B | | – | | +| >DCH Information Response | O | | 9.2.1.20C | | YES | ignore | +| >DSCH Information Response | O | | 9.2.3.5b | | YES | ignore | +| >USCH Information Response | O | | 9.2.3.29 | | YES | ignore | +| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.5G | | YES | ignore | +| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.50 | | YES | ignore | +| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.95 | 1.28 Mcps TDD only | YES | ignore | +| HS-DSCH Semi-Persistent | O | | 9.2.3.98 | 1.28 Mcps TDD only | YES | ignore | + +| | | | | | | | +|-----------------------------------------------------------------|---|--|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| scheduling Information
Response LCR | | | | | | | +| E-DCH Semi-Persistent
scheduling Information
Response LCR | O | | 9.2.3.99 | 1.28 Mcps TDD
only | YES | ignore | +| E-RNTI for FACH | O | | E-RNTI
9.2.1.75 | 1.28 Mcps TDD
only | YES | ignore | +| Multi-Carrier E-DCH
Information Response LCR | O | | 9.2.3.114 | 1.28 Mcps TDD
only | YES | ignore | +| MU-MIMO Information
Response | O | | 9.2.3.118 | 1.28 Mcps TDD
only | YES | reject | +| Non-rectangular resource
allocation indicator | O | | ENUMERATED
(activate) | 1.28 Mcps TDD
only.
The absence of
this IE indicates
that the non-
rectangular
resource
allocation is not
used. | YES | reject | +| Non-rectangular resource
timeslot set | O | | BIT
STRING
(SIZE(7)) | 1.28 Mcps TDD
only.
The absence of
this IE means
that the specific
timeslot(s) of
the non-
rectangular
resource is
defined in
3GPP TS
25.222 [34].
This IE indicates
which of the
timeslot(s)
is/are allocated
for non-
rectangular
resource.
Bit 0 is for
timeslot 0. Bit 1
is for timeslot 1.
Bit 2 is for
timeslot 2. Bit 3
is for timeslot 3.
Bit 4 is for
timeslot 4. Bit 5
is for timeslot 5.
Bit 6 is for
timeslot 6.
The value 0 of
a bit means the
corresponding
timeslot is not
allocated for
non-rectangular
resource. The
value 1 of a bit
means the
corresponding
timeslot is
allocated for
non-rectangular
resource.
Bit 0 is the
first/leftmost bit
of the bit string. | YES | reject | + + + +### 9.1.38 RADIO LINK SETUP FAILURE + +9.1.38.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|-----------|-----------------|---------------------------|--------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Node B Communication Context ID | C-Success | | 9.2.1.48 | The reserved value "All NBCC" shall not be used | YES | ignore | +| Communication Control Port ID | O | | 9.2.1.15 | | YES | ignore | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | – | | +| > RL Specific | | | | | | | +| >> Unsuccessful RL Information Response | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | +| >> Successful RL Information Response | | 0.. | | Note: There will never be maxNrOfRLs repetitions of this sequence. | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >>>Received Total Wide Band Power | M | | 9.2.2.39A | | – | | +| >>>CHOICE Diversity Indication | M | | | | – | | +| >>>> Combining | | | | | | | +| >>>>>RL ID | M | | 9.2.1.53 | Reference RL ID for the combining | – | | +| >>>> Non Combining or First RL | | | | | | | +| >>>>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >>>>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >>>Not Used | O | | NULL | | – | | +| >>>Not Used | O | | NULL | | – | | +| >>>SSDT Support Indicator | M | | 9.2.2.46 | | – | | +| >>>DL Power Balancing Activation Indicator | O | | 9.2.2.12C | | YES | ignore | +| >>>E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >>>E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >>>Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment | | YES | ignore | + +| | | | | | | | +|-----------------------------------------------------------------------------|---|---------------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------|------|--------| +| | | | 9.2.2.10A | | | | +| >>> HS-DSCH
Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >>>Non-Serving RL
Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| >>HS-DSCH Information
Response | O | | HS-DSCH
FDD
Information
Response
9.2.2.18E | | YES | ignore | +| >>Continuous Packet
Connectivity HS-SCCH
less Information
Response | O | | 9.2.2.69 | | YES | ignore | +| >> Additional HS Cell
Information Response | | 0..<maxNr
OfHSDSC
H-1> | | For secondary
serving HS-
DSCH cell. Max
7 in this 3GPP
release. | EACH | ignore | +| >>>HS-PDSCH RL ID | M | | RL ID
9.2.1.53 | | – | | +| >>>HS-DSCH FDD
Secondary Serving
Information Response | M | | 9.2.2.18EA | | – | | +| >> Additional E-DCH Cell
Information Response | | 0..<maxNr
OfEDCH-1
> | | E-DCH on
Secondary
uplink
frequency -
max 1 in this
3GPP release | EACH | ignore | +| >>>Additional E-DCH
FDD Information
Response | M | | 9.2.2.135 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------------| +| Success | The IE shall be present if at least one of the radio links has been successfully set up. | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.38.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | – | | +| > RL Specific | | | | | | | +| >> Unsuccessful RL Information Response | | 1 | | | YES | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.39 RADIO LINK ADDITION REQUEST + +9.1.39.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------------------|-----------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| Compressed Mode Deactivation Flag | O | | 9.2.2.3A | Shall be ignored if IE "Active Pattern Sequence Information" is present | YES | reject | +| RL Information | | 1.. | | | EACH | notify | +| >RL ID | M | | 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Frame Offset | M | | 9.2.1.31 | | – | | +| >Chip Offset | M | | 9.2.2.2 | | – | | +| >Diversity Control Field | M | | 9.2.1.25 | | – | | +| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | Initial power on DPCH or on F-DPCH | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on DPCH or on F-DPCH | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on DPCH or on F-DPCH | – | | +| >Not Used | O | | NULL | | – | | +| >Transmit Diversity Indicator | O | | 9.2.2.53 | | – | | +| >DL Reference Power | O | | DL power 9.2.1.21 | Power on DPCH or on F-DPCH | YES | ignore | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >Delayed Activation | O | | 9.2.1.24C | | YES | reject | +| >E-DCH RL Indication | O | | 9.2.2.13De | | YES | reject | +| >RL Specific E-DCH Information | O | | 9.2.2.39a | | YES | ignore | +| >Synchronisation Indicator | O | | 9.2.2.48A | | YES | ignore | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | YES | reject | +| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.112 | | YES | ignore | +| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.144 | | YES | ignore | +| >F-TPICH Information | O | | 9.2.2.160 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | +| Initial DL DPCH Timing Adjustment Allowed | O | | 9.2.2.18K | | YES | ignore | +| Serving E-DCH RL | O | | 9.2.2.48B | | YES | reject | +| Serving Cell Change CFN | O | | CFN 9.2.1.7 | | YES | reject | + +| | | | | | | | +|---------------------------------------------------------------------|-------------|-----------------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------|------|--------| +| HS-DSCH Serving Cell Change Information | O | | 9.2.2.18Eb | | YES | reject | +| E-DPCH Information | | 0..1 | | | YES | reject | +| >Maximum Set of E-DPDCHs | M | | 9.2.2.20C | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >E-TFCS Information | M | | 9.2.2.13Dh | | – | | +| >E-TTI | M | | 9.2.2.13Di | | – | | +| >E-DPCCH Power Offset | M | | 9.2.2.13Dj | | – | | +| >E-RGCH 2-Index-Step Threshold | M | | 9.2.2.13lg | | – | | +| >E-RGCH 3-Index-Step Threshold | M | | 9.2.2.13lh | | – | | +| >HARQ Info for E-DCH | M | | 9.2.2.18ba | | – | | +| >HS-DSCH Configured Indicator | M | | 9.2.2.18Ca | | YES | reject | +| > Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.114 | | YES | ignore | +| E-DCH FDD Information | C-EDPCHInfo | | 9.2.2.13Da | | YES | reject | +| Additional HS Cell Information RL Addition | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >HS-DSCH FDD Secondary Serving Information | M | | 9.2.2.18Da | | – | | +| UE Aggregate Maximum Bit Rate | O | | 9.2.1.123 | | YES | ignore | +| Additional E-DCHCell Information RL Add Req | | 0..1 | | For E-DCH on multiple frequencies in this Node B. | YES | reject | +| >CHOICE Setup Or Addition Of E-DCH On Secondary UL Frequency | M | | | | – | | +| >>Setup | | | | Used when the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context | – | | +| >>>Multicell E-DCH Transport Bearer Mode | M | | 9.2.2.130 | | – | | +| >>>Additional E-DCH Cell Information Setup | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.131 | | – | | +| >>Addition | | | | Used when there exist additional E- | – | | + +| | | | | | | | +|---------------------------------------------------------------|---|--------------------|-----------|-------------------------------------------------------------------|-----|--------| +| | | | | DCH RLs in the current Node B Communication Context | | | +| >>>Additional E-DCH Cell Information Addition | | 1.. | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>Additional E-DCH RL Specific Information To Add | M | | 9.2.2.133 | | – | | +| >>>>Additional E-DCH FDD Information | O | | 9.2.2.137 | | – | | +| >>>>Multicell E-DCH Information | O | | 9.2.2.140 | | YES | ignore | +| Active Pattern Sequence Information | O | | 9.2.2.A | | YES | ignore | +| UL CLTD Information | O | | 9.2.2.152 | | YES | reject | +| E-DCH Decoupling Indication | O | | 9.2.2.194 | | YES | reject | +| Radio Links without DPCH/F-DPCH Indication | O | | 9.2.2.201 | | YES | reject | +| UL DPCCH2 Information | O | | 9.2.2.203 | | YES | reject | +| Downlink TPC enhancements Information | O | | 9.2.2.214 | | YES | reject | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------| +| EDPCHInfo | This IE shall be present if E-DPCH Information IE is present. | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.39.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|----------------------------------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| UL CCTrCH Information | | 0..<maxNrOfCCTrCHs> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >UL DPCH Information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information | M | | 9.2.3.26C | | – | | +| >UL DPCH Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information LCR | M | | 9.2.3.26E | | – | | +| >TDD TPC UL Step Size | O | | 9.2.3.21a | Applicable to 1.28Mcps TDD only | YES | reject | +| >UL DPCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>UL Timeslot Information 7.68Mcps | M | | 9.2.3.38 | | – | | +| DL CCTrCH Information | | 0..<maxNrOfCCTrCHs> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >DL DPCH information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot Information | M | | 9.2.3.4E | | – | | +| >DL DPCH information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot Information LCR | M | | 9.2.3.4O | | – | | +| >CCTrCH Initial DL | O | | DL Power | | YES | ignore | + +| | | | | | | | +|----------------------------------------------|--------------------|------|----------------------------------|-------------------------------------------------------------------------------------------------|-----|--------| +| Transmission Power | | | 9.2.1.21 | | | | +| >TDD TPC DL Step Size | O | | 9.2.3.21 | | YES | reject | +| >CCTrCH Maximum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >CCTrCH Minimum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >DL DPCH information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | notify | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>DL Timeslot Information 7.68Mcps | M | | 9.2.3.39 | | – | | +| RL Information | | 1 | | | YES | reject | +| >RL ID | M | | 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Frame Offset | M | | 9.2.1.31 | | – | | +| >Diversity Control Field | M | | 9.2.1.25 | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >DL Time Slot ISCP Info | O | | 9.2.3.4F | Applicable to 3.84Mcps TDD and 7.68Mcps TDD only | – | | +| >DL Time Slot ISCP Info LCR | O | | 9.2.3.4P | Applicable to 1.28Mcps TDD only | YES | reject | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >Delayed Activation | O | | 9.2.1.24C | | YES | reject | +| >UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>Uplink Synchronisation Step Size | M | | 9.2.3.26H | | – | | +| >>Uplink Synchronisation Frequency | M | | 9.2.3.26G | | – | | +| >UARFCN | O | | 9.2.1.65 | Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]). | YES | reject | +| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.5F | | YES | reject | +| HS-DSCH RNTI | C-HSDSCH RadioLink | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | O | | RL ID 9.2.1.53 | | YES | reject | +| E-DCH Information | | 0..1 | | 3.84Mcps TDD only | YES | reject | + +| | | | | | | | +|-----------------------------------------------------|---|------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >E-PUCH Information | M | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information TDD | O | | 9.2.3.48 | | – | | +| >E-DCH TDD Information | M | | 9.2.3.49 | | – | | +| E-DCH Serving RL | O | | RL ID
9.2.1.53 | | YES | reject | +| E-DCH Information 7.68Mcps | | 0..1 | | 7.68Mcps TDD only | YES | reject | +| >E-PUCH Information | M | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information 7.68Mcps TDD | O | | 9.2.3.64 | | – | | +| >E-DCH TDD Information 7.68Mcps | M | | 9.2.3.65 | | – | | +| E-DCH Information 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | YES | reject | +| >E-PUCH Information LCR | M | | 9.2.3.45a | | – | | +| >E-TFCS Information TDD | M | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows Information TDD | M | | 9.2.3.47 | | – | | +| >E-DCH Non-scheduled Grant Information LCR TDD | O | | 9.2.3.48a | | – | | +| >E-DCH TDD Information LCR | M | | 9.2.3.49a | | – | | +| Power Control GAP | O | | INTEGER (1..255) | Unit: Number of subframes
Applicable to 1.28Mcps TDD only | YES | ignore | +| Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.93 | 1.28 Mcps TDD only | YES | reject | +| HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.96 | 1.28 Mcps TDD only | YES | reject | +| E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.97 | 1.28 Mcps TDD only | YES | reject | +| Idle Interval Information | O | | 9.2.3.102 | TDD only | YES | ignore | +| UE Selected MBMS Service Information | O | | 9.2.3.104 | This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only. | YES | ignore | +| HS-SCCH TPC step size | O | | TDD TPC DL Step Size
9.2.3.21 | 1.28 Mcps TDD only.
This IE is mandatory if DL CCTrCH Information IE and E-DCH Information 1.28Mcps IE are both absent. | YES | ignore | +| DCH Measurement Occasion | O | | 9.2.3.111 | Applicable for | YES | reject | + +| | | | | | | | +|---------------------------------------------------|---|------|----------------------|----------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Information | | | | 1.28 Mcps TDD. | | | +| Multi-Carrier E-DCH Information | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only | YES | reject | +| >Multi-carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.113 | 1.28 Mcps TDD only | – | | +| >Multi-Carrier E-DCH Information LCR | M | | 9.2.3.112 | 1.28 Mcps TDD only | – | | +| MU-MIMO Information | O | | 9.2.3.116 | 1.28 Mcps TDD only | YES | ignore | +| UE support of non-rectangular resource allocation | O | | ENUMERATED (support) | 1.28 Mcps TDD only. The absence of this IE indicates that the UE does not support the non-rectangular resource allocation. | YES | ignore | + +| Range Bound | Explanation | +|-----------------------|-----------------------------| +| maxNrOfCCTrCHs | Number of CCTrCH for one UE | + +| Condition | Explanation | +|-----------------|----------------------------------------------------------------| +| HSDSCHRadioLink | The IE shall be present if HS-PDSCH RL ID IE is present | + +### 9.1.40 RADIO LINK ADDITION RESPONSE + +9.1.40.1 FDD message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|-----------------------|-------------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| RL Information Response | | 1.. | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >RL Set ID | M | | 9.2.2.39 | | – | | +| >Received Total Wide Band Power | M | | 9.2.2.39A | | – | | +| >CHOICE Diversity Indication | M | | | | – | | +| >>Combining | | | | | | | +| >>>RL ID | M | | 9.2.1.53 | Reference RL | – | | +| >>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >>Non Combining | | | | | | | +| >>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >SSDT Support Indicator | M | | 9.2.2.46 | | – | | +| >DL Power Balancing Activation Indicator | O | | 9.2.2.12C | | YES | ignore | +| >E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment 9.2.2.10A | | YES | ignore | +| > HS-DSCH Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| HS-DSCH Serving Cell Change Information Response | O | | 9.2.2.18Ec | | YES | ignore | +| E-DCH Serving Cell Change Information Response | O | | 9.2.2.18Ed | | YES | ignore | +| MAC-hs Reset Indicator | O | | 9.2.1.38Ac | | YES | ignore | +| Additional HS Cell Change Information Response | | 0.. | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >HS-DSCH Secondary Serving Cell Change Information Response | M | | 9.2.2.18Eca | | – | | +| Additional E-DCH Cell Information Response RL | | 0.. | | E-DCH on Secondary | EACH | ignore | + +| | | | | | | | +|------------------------------------------------------------|---|---|-----------------------------------------------------------|------------------------------------------------|---|--| +| Add | | > | | uplink frequency - max 1 in this 3GPP release. | | | +| > Additional E-DCH FDD Information Response | O | | 9.2.2.135 | | – | | +| >Additional E-DCH Serving Cell Change Information Response | O | | E-DCH Serving Cell Change Information Response 9.2.2.18Ed | | – | | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.40.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| RL Information Response | | 0..1 | | Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD. | YES | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >UL Time Slot ISCP Info | M | | 9.2.3.26D | | – | | +| >UL PhysCH SF Variation | M | | 9.2.3.26B | | – | | +| >DCH Information | | 0..1 | | | – | | +| >>CHOICE Diversity Indication | M | | | | – | | +| >>> Combining | | | | Indicates whether the old Transport Bearer shall be reused or not | | | +| >>>>RL ID | M | | 9.2.1.53 | Reference RL | – | | +| >>> Non Combining | | | | | | | +| >>>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >DSCH Information Response | O | | 9.2.3.5b | | YES | ignore | +| >USCH Information Response | O | | 9.2.3.29 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| RL Information Response LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >UL Time Slot ISCP Info LCR | M | | 9.2.3.26F | | – | | +| >UL PhysCH SF Variation | M | | 9.2.3.26B | | – | | +| >DCH Information | | 0..1 | | | – | | +| >>CHOICE Diversity indication | M | | | | – | | +| >>> Combining | | | | Indicates whether the old Transport Bearer shall be reused or not | | | +| >>>>RL ID | M | | 9.2.1.53 | Reference RL | – | | +| >>> Non Combining | | | | | | | +| >>>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >DSCH Information Response | O | | 9.2.3.5b | | YES | ignore | +| >USCH Information Response | O | | 9.2.3.29 | | YES | ignore | + +| | | | | | | | +|-------------------------------------------------------------|---|--|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| HS-DSCH Information Response | O | | HS-DSCH TDD Information Response 9.2.3.5G | | YES | ignore | +| E-DCH Information Response | O | | E-DCH TDD Information Response 9.2.3.50 | | YES | ignore | +| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.95 | 1.28 Mcps TDD only | YES | ignore | +| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.98 | 1.28 Mcps TDD only | YES | ignore | +| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.99 | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.114 | 1.28 Mcps TDD only | YES | ignore | +| MU-MIMO Information Response | O | | 9.2.3.118 | 1.28 Mcps TDD only | YES | reject | +| Non-rectangular resource allocation indicator | O | | ENUMERATED (activate) | 1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used. | YES | reject | +| Non-rectangular resource timeslot set | O | | BIT STRING (SIZE(7)) | 1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicates which of the timeslot(s) is/are allocated for non-rectangular resource.
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular | YES | reject | + +| | | | | | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource. Bit 0 is the first/leftmost bit of the bit string. | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +### 9.1.41 RADIO LINK ADDITION FAILURE + +#### 9.1.41.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|-------------------|-------------------------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | – | | +| > RL Specific | | | | | | | +| >> Unsuccessful RL Information Response | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>> Cause | M | | 9.2.1.6 | | – | | +| >> Successful RL Information Response | | 0.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >>>Received Total Wide Band Power | M | | 9.2.2.39A | | – | | +| >>>CHOICE Diversity Indication | M | | | | – | | +| >>>> Combining | | | | | | | +| >>>>>RL ID | M | | 9.2.1.53 | Reference RL | – | | +| >>>>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >>>> Non Combining | | | | | | | +| >>>>>DCH Information Response | M | | 9.2.1.20C | | – | | +| >>>>>E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >>>SSDT Support Indicator | M | | 9.2.2.46 | | – | | +| >>>DL Power Balancing Activation Indicator | O | | 9.2.2.12C | | YES | ignore | +| >>>E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >>>E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >>>Initial DL DPCH Timing Adjustment | O | | DL DPCH Timing Adjustment 9.2.2.10A | | YES | ignore | +| >>> HS-DSCH Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >>>Non-Serving RL Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| HS-DSCH Serving Cell Change Information Response | O | | 9.2.2.18Ec | | YES | ignore | + +| | | | | | | | +|-------------------------------------------------------------|---|-----------------------------------|-----------------------------------------------------------|--------------------------------------------------------------------|------|--------| +| E-DCH Serving Cell Change Information Response | O | | 9.2.2.18Ed | | YES | ignore | +| Additional HS Cell Change Information Response | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >HS-DSCH Secondary Serving Cell Change Information Response | M | | 9.2.2.18Eca | | – | | +| MAC-hs Reset Indicator | O | | 9.2.1.38Ac | | YES | ignore | +| Additional E-DCH Cell Information Response RL Add | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.. | EACH | ignore | +| >Additional E-DCH FDD Information Response | O | | 9.2.2.135 | | – | | +| >Additional E-DCH Serving Cell Change Information Response | O | | E-DCH Serving Cell Change Information Response 9.2.2.18Ed | | – | | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.41.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | – | | +| > RL Specific | | | | | | | +| >> Unsuccessful RL Information Response | | 1 | | | YES | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>> Cause | M | | 9.2.1.6 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.42 RADIO LINK RECONFIGURATION PREPARE + +#### 9.1.42.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|--------------|-------------------|---------------------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| UL DPCH Information | | 0..1 | | | YES | reject | +| >UL Scrambling Code | O | | 9.2.2.59 | | – | | +| >UL SIR Target | O | | UL SIR
9.2.1.67A | | – | | +| >Min UL Channelisation Code Length | O | | 9.2.2.22 | | – | | +| >Max Number of UL DPDCHs | C-CodeLen | | 9.2.2.21 | | – | | +| >Puncture Limit | O | | 9.2.1.50 | For UL | – | | +| >TFCS | O | | 9.2.1.58 | | – | | +| >UL DPCCH Slot Format | O | | 9.2.2.57 | | – | | +| >Diversity Mode | O | | 9.2.2.9 | | – | | +| >Not Used | O | | NULL | | – | | +| >Not Used | O | | NULL | | – | | +| >UL DPDCH Indicator For E-DCH Operation | O | | 9.2.2.61 | | YES | reject | +| DL DPCH Information | | 0..1 | | | YES | reject | +| >TFCS | O | | 9.2.1.58 | | – | | +| >DL DPCH Slot Format | O | | 9.2.2.10 | | – | | +| >TFCI Signalling Mode | O | | 9.2.2.50 | | – | | +| >TFCI Presence | C-SlotFormat | | 9.2.1.57 | | – | | +| >Multiplexing Position | O | | 9.2.2.23 | | – | | +| >Not Used | O | | NULL | | – | | +| >Not Used | O | | NULL | | – | | +| >Limited Power Increase | O | | 9.2.2.18A | | – | | +| >DL DPCH Power Information | | 0..1 | | | YES | reject | +| >>Power Offset Information | | 1 | | | – | | +| >>>PO1 | M | | Power Offset
9.2.2.29 | Power offset for the TFCI bits | – | | +| >>>PO2 | M | | Power Offset
9.2.2.29 | Power offset for the TPC bits | – | | +| >>>PO3 | M | | Power Offset
9.2.2.29 | Power offset for the pilot bits | – | | +| >>FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >>Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| DCHs To Modify | O | | DCHs FDD To Modify
9.2.2.4E | | YES | reject | +| DCHs To Add | O | | DCH FDD Information
9.2.2.4D | | YES | reject | +| DCHs To Delete | | 0.. | | | GLOBAL | reject | +| >DCH ID | M | | 9.2.1.20 | | – | | +| RL Information | | 0..OfRLs> | | | | | +|--|--|------------------|--|--|--|--| + +| | | | | | | | +|-----------------------------------------------|------------------|--|-------------------------------------------------|--------------------------------------------|-----|--------| +| >RL ID | M | | 9.2.1.53 | | – | | +| >DL Code Information | O | | FDD DL Code Information 9.2.2.14A | | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on DPCH or on F-DPCH | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on DPCH or on F-DPCH | – | | +| >Not Used | O | | NULL | | – | | +| >Not Used | O | | NULL | | – | | +| >Transmit Diversity Indicator | C-Diversity mode | | 9.2.2.53 | | – | | +| >DL Reference Power | O | | DL Power 9.2.1.21 | Power on DPCH or on F-DPCH | YES | ignore | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >DL DPCH Timing Adjustment | O | | 9.2.2.10A | Required RL Timing Adjustment | YES | reject | +| >Primary CPICH Usage For Channel Estimation | O | | 9.2.2.33A | | YES | ignore | +| >Secondary CPICH Information Change | O | | 9.2.2.43A | | YES | ignore | +| >E-DCH RL Indication | O | | 9.2.2.13De | | YES | reject | +| >RL Specific E-DCH Information | O | | 9.2.2.39a | | YES | ignore | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | YES | reject | +| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.112 | | YES | ignore | +| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.144 | | YES | ignore | +| >Non-Serving RL Preconfiguration Removal | O | | Non-Serving RL Preconfiguration Setup 9.2.2.144 | | YES | ignore | +| >F-TPICH Information Reconf | O | | 9.2.2.163 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | +| Transmission Gap Pattern Sequence Information | O | | 9.2.2.53A | | YES | reject | +| Signalling Bearer Request Indicator | O | | 9.2.1.55A | | YES | reject | +| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.18D | | YES | reject | +| HS-DSCH Information To Modify | O | | 9.2.1.31H | | YES | reject | +| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.31IA | | YES | reject | +| HS-DSCH MAC-d Flows To | O | | 9.2.1.31IB | | YES | reject | + +| | | | | | | | +|-------------------------------------------------------------------|--------------------|-----------|-----------------------------------------|-------------------------------------|------|--------| +| Delete | | | | | | | +| HS-DSCH RNTI | C-HSDSCH RadioLink | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | O | | RL ID 9.2.1.53 | | YES | reject | +| E-DPCH Information | | 0..1 | | | YES | reject | +| >Maximum Set of E-DPDCHs | O | | 9.2.2.20C | | – | | +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >E-TFCS Information | O | | 9.2.2.13Dh | | – | | +| >E-TTI | O | | 9.2.2.13Di | | – | | +| >E-DPCCH Power Offset | O | | 9.2.2.13Dj | | – | | +| >E-RGCH 2-Index-Step Threshold | O | | 9.2.2.13lg | | – | | +| >E-RGCH 3-Index-Step Threshold | O | | 9.2.2.13lh | | – | | +| >HARQ Info for E-DCH | O | | 9.2.2.18ba | | – | | +| >HS-DSCH Configured Indicator | O | | 9.2.2.18Ca | | – | | +| > Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.114 | | YES | ignore | +| E-DCH FDD Information | O | | E-DCH FDD Information 9.2.2.13Da | | YES | reject | +| E-DCH FDD Information To Modify | O | | 9.2.2.13Df | | YES | reject | +| E-DCH MAC-d Flows To Add | O | | E-DCH MAC-d Flows Information 9.2.2.13M | | YES | reject | +| E-DCH MAC-d Flows To Delete | O | | 9.2.1.73 | | YES | reject | +| Serving E-DCH RL | O | | 9.2.2.48B | | YES | reject | +| F-DPCH Information | | 0..1 | | | YES | reject | +| > Power Offset Information | | 1 | | | – | | +| >>PO2 | M | | Power Offset 9.2.2.29 | This IE shall be ignored by Node B. | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Limited Power Increase | M | | 9.2.2.18A | | – | | +| >Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| Fast Reconfiguration Mode | O | | 9.2.2.62 | | YES | ignore | +| CPC Information | | 0..1 | | | YES | reject | +| >Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.66 | | – | | +| >Continuous Packet Connectivity DTX-DRX Information To Modify | O | | 9.2.2.67 | | – | | +| >Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.68 | | – | | +| >Continuous Packet Connectivity HS-SCCH less Deactivate Indicator | O | | 9.2.2.69A | | YES | reject | +| Additional HS Cell | | 0..Information RL Reconf Prep | | OfHSDSCH-1> | | serving HS-DSCH cell. Max 7 in this 3GPP release. | | | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >C-ID | O | | 9.2.1.9 | | – | | +| >HS-DSCH FDD Secondary Serving Information | O | | 9.2.2.18Da | | – | | +| >HS-DSCH FDD Secondary Serving Information To Modify | O | | 9.2.2.18EB | | – | | +| >HS-DSCH Secondary Serving Remove | O | | NULL | | – | | +| UE Aggregate Maximum Bit Rate | O | | 9.2.1.123 | | YES | ignore | +| Additional E-DCH Cell Information RL Reconf Prep | | 0.1 | | For E-DCH on multiple frequencies in this Node B. | YES | reject | +| >CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency | M | | | | – | | +| >> Setup | | | | Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context | – | | +| >>> MultiCell E-DCH Transport Bearer Mode | M | | 9.2.2.130 | | – | | +| >>> Additional E-DCH Cell Information Setup | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.131 | | – | | +| >> Configuration Change | | | | Used when RLs with additional E-DCH on the secondary UL frequency exist in the current Node B Communication context and the configuration is modified (adding new RLs or modification of existing RLs) | – | | + +| | | | | | | | +|---------------------------------------------------------------------------|---|---------------------------------|--------------------------|-----------------------------------------------------------------------|-----|--------| +| >>>Additional E-DCH Cell Information Configuration Change | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>> Additional E-DCH Configuration Change Information | M | | 9.2.2.136 | | – | | +| >>Removal | | | | Used when all RLs on the indicated secondary UL frequency is removed. | – | | +| >>>Additional E-DCH Cell Information Removal | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>RL on Secondary UL Frequency | M | | ENUMERATED (Remove, ...) | Removal of all RL on secondary UL frequency | – | | +| UL CLTD Information Reconf | O | | 9.2.2.151 | | YES | reject | +| E-DCH Decoupling Indication | O | | 9.2.2.194 | | YES | reject | +| DCH Enhancements Information Reconf | O | | 9.2.2.195 | | YES | reject | +| Radio Links without DPCH/F-DPCH Indication | O | | 9.2.2.201 | | YES | reject | +| UL DPCCH2 Reconfiguration | O | | 9.2.2.202 | | YES | reject | +| Downlink TPC enhancements Reconf | O | | 9.2.2.215 | | YES | reject | +| Improved Synchronized RRC Indicator | O | | 9.2.1.129 | | YES | ignore | + +| Condition | Explanation | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| CodeLen | The IE shall be present if the Min UL Channelisation Code Length IE is equals to 4. | +| SlotFormat | The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. | +| Diversity mode | The IE shall be present if the Diversity Mode IE is present in the UL DPCH Information IE and is not set to "none". | +| HSDSCH Radio Link | The IE shall be present if HS-PDSCH RL ID IE is present. | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for a UE | +| maxNrOfRLs | Maximum number of RLs for a UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.42.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|----------------------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| UL CCTrCH To Add | | 0..<maxNrOfCCTrCHs> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | M | | 9.2.1.58 | | – | | +| >TFCI Coding | M | | 9.2.3.22 | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| > UL DPCH To Add Per RL | | 0..<maxNrOfRLs> | | See note 1 below | – | | +| >> UL DPCH Information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot Information | M | | 9.2.3.26C | | – | | +| >> UL DPCH Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot Information LCR | M | | 9.2.3.26E | | – | | +| >>UL SIR Target | O | | UL SIR 9.2.1.67A | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD | YES | reject | +| >>TDD TPC UL Step Size | O | | 9.2.3.21a | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>RL ID | O | | 9.2.1.53 | | YES | ignore | +| >> UL DPCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot Information 7.68Mcps | M | | 9.2.3.38 | | – | | +| UL CCTrCH To Modify | | 0..<maxNrOfCCTrCHs> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | O | | 9.2.1.58 | | – | | +| >TFCI Coding | O | | 9.2.3.22 | | – | | + +| | | | | | | | +|-----------------------------------------------------|---|-------------------------------------|-----------|---------------------------------|--------|--------| +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >UL DPCH To Modify Per RL | | 0..<maxNr OfRLs> | | See note 1 below | – | | +| >>UL DPCH To Add | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot Information | M | | 9.2.3.26C | | – | | +| >>UL DPCH To Modify | | 0..1 | | | YES | reject | +| >>>Repetition Period | O | | 9.2.3.16 | | – | | +| >>>Repetition Length | O | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | O | | 9.2.3.19A | | – | | +| >>>UL Timeslot Information | | 0..<maxNr OfULTSs> | | Applicable to 3.84Mcps TDD only | – | | +| >>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>Midamble Shift And Burst Type | O | | 9.2.3.7 | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>UL Code Information | | 0..<maxNr OfDPCHs> | | | – | | +| >>>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>>UL Timeslot Information LCR | | 0..<maxNr OfULTSL CRs> | | Applicable to 1.28Mcps TDD only | GLOBAL | reject | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>UL Code Information LCR | | 0..<maxNr OfDPCHL CRs> | | | – | | +| >>>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>>TDD Channelisation Code LCR | O | | 9.2.3.19a | | – | | +| >>>>>TDD UL DPCH Time Slot Format LCR | O | | 9.2.3.21C | | YES | reject | +| >>>>PLCCH Information | O | | 9.2.3.31 | | YES | reject | +| >>>UL Timeslot Information 7.68Mcps | | 0..<maxNr OfULTSs> | | Applicable to 7.68Mcps TDD only | GLOBAL | reject | +| >>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.35 | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>UL Code Information 7.68Mcps | | 0..<maxNr OfDPCHs> | | | – | | +| >>>>>DPCH ID | M | | 9.2.3.5 | | – | | + +| | | | | | | | +|---------------------------------------------|---|--------------------------------------------|----------------------|-----------------------------------------------|--------|--------| +| >>>>>TDD
Channelisation Code
7.68Mcps | O | | 9.2.3.34 | | – | | +| >>UL DPCH To Delete | | 0..<maxNr
OfDPCHs
> | | | GLOBAL | reject | +| >>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>UL DPCH To Add LCR | | 0..1 | | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot
Information LCR | M | | 9.2.3.26E | | – | | +| >>UL SIR Target | O | | UL SIR
9.2.1.67A | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>TDD TPC UL Step Size | O | | 9.2.3.21a | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>RL ID | O | | 9.2.1.53 | | YES | ignore | +| >>UL DPCH To Add
7.68Mcps | | 0..1 | | Applicable to
7.68Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>UL Timeslot
Information 7.68Mcps | M | | 9.2.3.38 | | – | | +| UL CCTrCH To Delete | | 0..<maxNr
OfCCTrCHs
> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| DL CCTrCH To Add | | 0..<maxNr
OfCCTrCHs
> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | M | | 9.2.1.58 | | – | | +| >TFCI Coding | M | | 9.2.3.22 | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >TPC CCTrCH List | | 0..<maxNr
OfCCTrCHs
> | | List of uplink
CCTrCH which
provide TPC | – | | +| >>TPC CCTrCH ID | M | | CCTrCH ID
9.2.3.3 | | – | | +| >DL DPCH To Add Per RL | | 0..<maxNr
OfRLs> | | See Note 1
below | – | | +| >>DL DPCH Information | | 0..1 | | Applicable to
3.84Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>DL Timeslot
Information | M | | 9.2.3.4E | | – | | +| >>DL DPCH Information
LCR | | 0..1 | | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | + +| | | | | | | | +|-------------------------------------------|---|--|----------------------|--|-----|--------| +| >>>DL Timeslot
Information LCR | M | | 9.2.3.4O | | – | | +| >>CCTrCH Initial DL
Transmission Power | O | | DL Power
9.2.1.21 | | YES | ignore | +| >>TDD TPC DL Step Size | O | | 9.2.3.21 | | YES | reject | + +| | | | | | | | +|------------------------------------------------|---|----------------------|-------------------|-----------------------------------------|--------|--------| +| >>CCTrCH Maximum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >>CCTrCH Minimum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >>RL ID | O | | 9.2.1.53 | | YES | ignore | +| >>DL DPCH Information 7.68Mcps | | 0..1 | | Applicable to 7.68Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>DL Timeslot Information 7.68Mcps | M | | 9.2.3.39 | | – | | +| DL CCTrCH To Modify | | 0.. | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | O | | 9.2.1.58 | | – | | +| >TFCI Coding | O | | 9.2.3.22 | | – | | +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >TPC CCTrCH List | | 0.. | | List of uplink CCTrCH which provide TPC | – | | +| >>TPC CCTrCH ID | M | | CCTrCH ID 9.2.3.3 | | – | | +| >DL DPCH To Modify Per RL | | 0.. | | See Note 1 below | – | | +| >>DL DPCH To Add | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>DL Timeslot Information | M | | 9.2.3.4E | | – | | +| >>DL DPCH To Modify | | 0..1 | | | YES | reject | +| >>>Repetition Period | O | | 9.2.3.16 | | – | | +| >>>Repetition Length | O | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | O | | 9.2.3.19A | | – | | +| >>>DL Timeslot Information | | 0.. | | Applicable to 3.84Mcps TDD only | – | | +| >>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>Midamble Shift And Burst Type | O | | 9.2.3.7 | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>DL Code Information | | 0.. | | | – | | +| >>>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>>DL Timeslot Information LCR | | 0.. | | Applicable to 1.28Mcps TDD only | GLOBAL | reject | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>DL Code Information LCR | | 0.. | | | – | | + +| | | | | | | | +|--|--|------|--|--|--|--| +| | | CRs> | | | | | +|--|--|------|--|--|--|--| + +| | | | | | | | +|--------------------------------------------------|---|---------------------------------------------|-----------------------|---------------------------------------|--------|--------| +| >>>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>>TDD
Channelisation Code
LCR | O | | 9.2.3.19a | | – | | +| >>>>>TDD DL
DPCH Time Slot
Format LCR | O | | 9.2.3.19D | | YES | reject | +| >>>>Maximum DL
Power to Modify LCR | O | | DL Power
9.2.1.21 | Maximum
allowed power
on DPCH | YES | ignore | +| >>>>Minimum DL
Power to Modify LCR | O | | DL Power
9.2.1.21 | Minimum
allowed power
on DPCH | YES | ignore | +| >>>DL Timeslot
Information 7.68Mcps | | 0..<maxNr
OfDLTSSs> | | Applicable to
7.68Mcps TDD
only | GLOBAL | reject | +| >>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>Midamble Shift
And Burst Type
7.68Mcps | O | | 9.2.3.35 | | – | | +| >>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>DL Code
Information
7.68Mcps | | 0..<maxNr
OfDPCHs
768> | | | – | | +| >>>>>DPCH ID
7.68Mcps | M | | 9.2.3.42 | | – | | +| >>>>>TDD
Channelisation Code
7.68Mcps | O | | 9.2.3.34 | | – | | +| >>DL DPCH To Delete | | 0..<maxNr
OfDPCHs
> | | | GLOBAL | reject | +| >>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>DL DPCH To Add LCR | | 0..1 | | Applicable to
1.28Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>DL Timeslot
Information LCR | M | | 9.2.3.40 | | – | | +| >>TDD TPC DL Step Size | O | | 9.2.3.21 | | YES | reject | +| >>Maximum CCTrCH DL
Power to Modify | O | | DL Power
9.2.1.21 | | YES | ignore | +| >>Minimum CCTrCH DL
Power to Modify | O | | DL Power
9.2.1.21 | | YES | ignore | +| >>RL ID | O | | 9.2.1.53 | | YES | ignore | +| >>DL DPCH To Add
7.68Mcps | | 0..1 | | Applicable to
7.68Mcps TDD
only | YES | reject | +| >>>Repetition Period | M | | 9.2.3.16 | | – | | +| >>>Repetition Length | M | | 9.2.3.15 | | – | | +| >>>TDD DPCH Offset | M | | 9.2.3.19A | | – | | +| >>>DL Timeslot
Information 7.68Mcps | M | | 9.2.3.39 | | – | | +| DL CCTrCH To Delete | | 0..<maxNr
OfCCTrCHs> | | | GLOBAL | reject | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| DCHs To Modify | O | | DCHs TDD
To Modify | | YES | reject | + +| | | | | | | | +|--|--|--|----------|--|--|--| +| | | | 9.2.3.4D | | | | +|--|--|--|----------|--|--|--| + +| | | | | | | | +|-------------------------------------|---|---------------------------------|-------------------------------|------------------------------------------------------|--------|--------| +| DCHs To Add | O | | DCH TDD Information 9.2.3.4C | | YES | reject | +| DCHs To Delete | | 0..<maxNr OfDCHs> | | | GLOBAL | reject | +| >DCH ID | M | | 9.2.1.20 | | – | | +| DSCH To Modify | | 0..<maxNr OfDSCHs> | | | GLOBAL | reject | +| >DSCH ID | M | | 9.2.3.5a | | – | | +| >CCTrCH ID | O | | 9.2.3.3 | DL CCTrCH in which the DSCH is mapped | – | | +| >Transport Format Set | O | | 9.2.1.59 | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >Frame Handling Priority | O | | 9.2.1.30 | | – | | +| >ToAWS | O | | 9.2.1.61 | | – | | +| >ToAWE | O | | 9.2.1.60 | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| DSCH To Add | O | | DSCH TDD Information 9.2.3.5A | | YES | reject | +| DSCH To Delete | | 0..<maxNr OfDSCHs> | | | GLOBAL | reject | +| >DSCH ID | M | | 9.2.3.5a | | – | | +| USCH To Modify | | 0..<maxNr OfUSCHs> | | | GLOBAL | reject | +| >USCH ID | M | | 9.2.3.27 | | – | | +| >Transport Format Set | O | | 9.2.1.59 | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >CCTrCH ID | O | | 9.2.3.3 | UL CCTrCH in which the USCH is mapped | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | + +| | | | | | | | +|----------------------------------------------|--------------------|--------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------|--------|--------| +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | +| USCH To Add | O | | USCH Information 9.2.3.28 | | YES | reject | +| USCH To Delete | | 0..<maxNrOfUSCHs> | | | GLOBAL | reject | +| >USCH ID | M | | 9.2.3.27 | | – | | +| RL Information | | 0..<maxNrOfRLs> | | See Note 1 below | YES | reject | +| >RL ID | M | | 9.2.1.53 | | – | | +| >Maximum Downlink Power | O | | DL Power 9.2.1.21 | | – | | +| >Minimum Downlink Power | O | | DL Power 9.2.1.21 | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore | +| >>Uplink Synchronisation Step Size | M | | 9.2.3.26H | | – | | +| >>Uplink Synchronisation Frequency | M | | 9.2.3.26G | | – | | +| >DL Time Slot ISCP Info LCR | O | | 9.2.3.4P | Applicable to 1.28Mcps TDD only | YES | ignore | +| >UARFCN | O | | 9.2.1.65 | Applicable to 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]). | YES | reject | +| Signalling Bearer Request Indicator | O | | 9.2.1.55A | | YES | reject | +| HS-DSCH Information | O | | HS-DSCH TDD Information 9.2.3.5F | | YES | reject | +| HS-DSCH Information To Modify | O | | 9.2.1.31H | | YES | reject | +| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.31IA | | YES | reject | +| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.31IB | | YES | reject | +| HS-DSCH RNTI | C-HSDSCH RadioLink | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | O | | RL ID | | YES | reject | + +| | | | | | | | +|--|--|--|----------|--|--|--| +| | | | 9.2.1.53 | | | | +|--|--|--|----------|--|--|--| + +| | | | | | | | +|-----------------------------------------------------------|---|------|-----------------------------------------------------------|-----------------------------------------------------------------------|-----|--------| +| PDSCH-RL-ID | O | | RL ID
9.2.1.53 | | YES | ignore | +| E-DCH Information | | 0..1 | | 3.84Mcps TDD
only | YES | reject | +| >E-PUCH Information | O | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to
Add | O | | E-DCH
MAC-d
Flows
Information
TDD
9.2.3.47 | | – | | +| >E-DCH MAC-d Flows to
Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled
Grant Information TDD | O | | 9.2.3.48 | | – | | +| >E-DCH TDD Information | O | | 9.2.3.49 | | – | | +| >E-DCH TDD Information to
Modify | O | | 9.2.3.52 | | – | | +| E-DCH Serving RL | O | | RL ID
9.2.1.53 | | YES | reject | +| E-DCH Information
7.68Mcps | | 0..1 | | 7.68Mcps TDD
only | YES | reject | +| >E-PUCH Information | O | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to
Add | O | | E-DCH
MAC-d
Flows
Information
TDD
9.2.3.47 | | – | | +| >E-DCH MAC-d Flows to
Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled
Grant Information 7.68Mcps
TDD | O | | 9.2.3.64 | | – | | +| >E-DCH TDD Information
7.68Mcps | O | | 9.2.3.65 | | – | | +| >E-DCH TDD Information to
Modify | O | | 9.2.3.52 | | – | | +| E-DCH Information
1.28Mcps | | 0..1 | | 1.28Mcps TDD
only | YES | reject | +| >E-PUCH Information LCR | O | | 9.2.3.45a | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to
Add | O | | E-DCH
MAC-d
Flows
Information
TDD
9.2.3.47 | | – | | +| >E-DCH MAC-d Flows to
Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled
Grant Information LCR TDD | O | | 9.2.3.48a | | – | | +| >E-DCH TDD Information
LCR | O | | 9.2.3.49a | | – | | +| >E-DCH TDD Information to
Modify | O | | 9.2.3.52 | | – | | +| Power Control GAP | O | | INTEGER
(1..255) | Unit: Number of
subframes
Applicable to
1.28Mcps TDD
only | YES | ignore | +| CPC Information | | 0..1 | | 1.28Mcps TDD
only | YES | reject | +| >Continuous Packet | O | | 9.2.3.93 | | – | | + +| | | | | | | | +|---------------------------------------------------------------|---|------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Connectivity DRX Information LCR | | | | | | | +| >Continuous Packet Connectivity DRX Information To Modify LCR | O | | 9.2.3.94 | | – | | +| >HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.96 | | – | | +| >HS-DSCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.96a | | – | | +| >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.100 | | – | | +| >E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.97 | | – | | +| >E-DCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.97a | | – | | +| >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.101 | | – | | +| Idle Interval Information | O | | 9.2.3.102 | TDD only | YES | Ignore | +| UE Selected MBMS Service Information | O | | 9.2.3.104 | This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only. | YES | ignore | +| HS-SCCH TPC step size | O | | TDD TPC DL Step Size 9.2.3.21 | 1.28 Mcps TDD only. | YES | ignore | +| DCH Measurement Occasion Information | O | | 9.2.3.111 | Applicable for 1.28 Mcps TDD. | YES | reject | +| HS-DSCH-RNTI for FACH | O | | HS-DSCH RNTI 9.2.1.31J | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information Reconf | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation for 1.28 Mcps TDD only | YES | reject | +| >CHOICE continue, Setup or Change | M | | | | – | | +| >>continue | | | | Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration keeps unchanged. | – | | +| >>Setup | | | | Used when the Multi-carrier E-DCH is not configured for this RL in the current Node B | – | | + +| | | | | | | | +|---------------------------------------------------|---|------------------------------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | Communication Context | | | +| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.113 | | – | | +| >>>UL Multi-Carrier E-DCH Information LCR | M | | 9.2.3.112 | | – | | +| >>change | | | | Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration is modified (adding new frequencies, modification of existing configuration or removing existing frequencies) | – | | +| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | O | | 9.2.3.113 | | – | | +| >>>UL Multi-Carrier E-DCH Information LCR | O | | 9.2.3.112 | | – | | +| >>>Removal UL Multi-Carrier info | | 0..<maxNrOfULCarriersLCR-1> | | | – | | +| >>>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | – | | +| MU-MIMO Information | O | | 9.2.3.116 | 1.28 Mcps TDD only | YES | ignore | +| MU-MIMO Information To Reconfigure | O | | 9.2.3.117 | 1.28 Mcps TDD only | YES | ignore | +| UE support of non-rectangular resource allocation | O | | ENUMERATED (support) | 1.28 Mcps TDD only. The absence of this IE indicates that the UE does not support the non-rectangular resource allocation. | YES | ignore | + +NOTE 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticalities. + +| Condition | Explanation | +|-----------------|-----------------------------------------------------------------| +| HSDSCHRadiolink | The IE shall be present if HS-PDSCH RL ID IE is present. | + +| Range Bound | Explanation | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for a UE | +| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE | +| maxNrOfDPCHs | Maximum number of DPCHs in one CCTrCH for 3.84Mcps TDD.
Maximum number of uplink DPCHs in one CCTrCH for 7.68Mcps TDD | +| maxNrOfDPCHLCRs | Maximum number of DPCHs in one CCTrCH for 1.28Mcps TDD | +| maxNrOfDPCHs768 | Maximum number of downlink DPCHs in one CCTrCH for 7.68Mcps TDD | +| maxNrOfDSCHs | Maximum number of DSCHs for one UE | +| maxNrOfUSCHs | Maximum number of USCHs for one UE | +| maxNrOfDLTSs | Maximum number of Downlink time slots per Radio Link for 3.84Mcps TDD | +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD | +| maxNrOfULTSs | Maximum number of Uplink time slots per Radio Link for 3.84Mcps TDD | +| maxNrOfULTSLCRs | Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD | +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfULCarriersLCR-1 | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation | + +### 9.1.43 RADIO LINK RECONFIGURATION READY + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------|----------|------------------------------------|-----------------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| RL Information Response | | 0..<maxNr OfRLs> | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >DCH Information Response | O | | 9.2.1.20C | | YES | ignore | +| >DSCH Information Response | O | | 9.2.3.5b | TDD only | YES | ignore | +| >USCH Information Response | O | | 9.2.3.29 | TDD only | YES | ignore | +| >Not Used | O | | NULL | | – | | +| >DL Power Balancing Updated Indicator | O | | 9.2.2.12D | | YES | ignore | +| >E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >HS-DSCH Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| Target Communication Control Port ID | O | | Communication Control Port ID 9.2.1.15 | | YES | ignore | +| HS-DSCH FDD Information Response | O | | 9.2.2.18E | FDD only | YES | ignore | +| HS-DSCH TDD Information Response | O | | 9.2.3.5G | TDD only | YES | ignore | +| E-DCH TDD Information Response | O | | E-DCH TDD Information Response 9.2.3.50 | TDD only | YES | ignore | +| MAC-hs Reset Indicator | O | | 9.2.1.38Ac | | YES | ignore | +| Fast Reconfiguration Permission | O | | 9.2.2.63 | FDD only | YES | ignore | +| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.69 | FDD only | YES | ignore | +| Additional HS Cell Information Response | | 0..<maxNr OfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >HS-DSCH FDD Secondary Serving | M | | 9.2.2.18EA | FDD only | – | | + +| | | | | | | | +|-------------------------------------------------------------|---|--------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------| +| Information Response | | | | | | | +| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.95 | 1.28 Mcps TDD only | YES | ignore | +| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.98 | 1.28 Mcps TDD only | YES | ignore | +| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.99 | 1.28 Mcps TDD only | YES | ignore | +| Additional E-DCHCell Information Response RLReconf | | 0.<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | EACH | ignore | +| >Additional E-DCH FDD Information Response | O | | 9.2.2.135 | For new E-DCH Radio Links on secondary uplink frequency | – | | +| >Additional Modified E-DCH FDD Information Response | O | | 9.2.2.141 | | – | | +| E-RNTI for FACH | O | | E-RNTI 9.2.1.75 | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.114 | 1.28 Mcps TDD only | YES | ignore | +| MU-MIMO Information Response | O | | 9.2.3.118 | 1.28 Mcps TDD only | YES | reject | +| Non-rectangular resource allocation indicator | O | | ENUMERATED (activate) | 1.28 Mcps TDD only. The absence of this IE indicates that the non-rectangular resource allocation is not used. | YES | reject | +| Non-rectangular resource timeslot set | O | | BIT STRING (SIZE(7)) | 1.28 Mcps TDD only. The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34]. This IE indicates which of the timeslot(s) is/are allocated for non-rectangular resource. Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 | YES | reject | + +| | | | | | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | is for timeslot 5.
Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource.
Bit 0 is the first/leftmost bit of the bit string. | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for a UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +### 9.1.44 RADIO LINK RECONFIGURATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | YES | ignore | +| > RL Specific | | | | | | | +| >>RLs Causing Reconfiguration Failure | | 0..< maxNrOfRLs > | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>> Cause | M | | 9.2.1.6 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +| Range Bound | Explanation | +|-------------------|--------------------------------| +| maxNrOfRLs | Maximum number of RLs for a UE | + +### 9.1.45 RADIO LINK RECONFIGURATION COMMIT + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| CFN | M | | 9.2.1.7 | | YES | ignore | +| Active Pattern Sequence Information | O | | 9.2.2.A | FDD only | YES | ignore | +| Fast Reconfiguration Mode | O | | 9.2.2.62 | FDD only | YES | reject | +| Activation Delay | O | | 9.2.2.210 | FDD only | YES | reject | + +### 9.1.46 RADIO LINK RECONFIGURATION CANCEL + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | + +### 9.1.47 RADIO LINK RECONFIGURATION REQUEST + +9.1.47.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|------------------|-------------------------------------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| UL DPCH Information | | 0..1 | | | YES | reject | +| >TFCS | O | | 9.2.1.58 | For the UL. | – | | +| >UL DPDCH Indicator For E-DCH Operation | O | | 9.2.2.61 | | YES | reject | +| DL DPCH Information | | 0..1 | | | YES | reject | +| >TFCS | O | | 9.2.1.58 | For the DL. | – | | +| >TFCI Signalling Mode | O | | 9.2.2.50 | | – | | +| >Limited Power Increase | O | | 9.2.2.18A | | – | | +| DCHs To Modify | O | | DCHs FDD To Modify 9.2.2.4E | | YES | reject | +| DCHs To Add | O | | DCH FDD Information 9.2.2.4D | | YES | reject | +| DCHs To Delete | | 0.. | | | GLOBAL | reject | +| >DCH ID | M | | 9.2.1.20 | | – | | +| Radio Link Information | | 0.. | | | EACH | reject | +| >RL ID | M | | 9.2.1.53 | | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on DPCH or on F-DPCH | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on DPCH or on F-DPCH | – | | +| >DL Code Information | C-SF/2 | | FDD DL Code Information 9.2.2.14A | | – | | +| >DL Reference Power | O | | DL Power 9.2.1.21 | Power on DPCH or on F-DPCH | YES | ignore | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >E-DCH RL Indication | O | | 9.2.2.13De | | YES | reject | +| >RL Specific E-DCH Information | O | | 9.2.2.39a | | YES | ignore | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | YES | reject | +| >HS-DSCH Preconfiguration Setup | O | | 9.2.2.112 | | YES | ignore | +| >Non-Serving RL Preconfiguration Setup | O | | 9.2.2.144 | | YES | ignore | +| >Non-Serving RL Preconfiguration Removal | O | | Non-Serving RL Preconfiguration Setup 9.2.2.144 | | YES | ignore | +| >F-TPICH Information Reconf | O | | 9.2.2.163 | | YES | ignore | + +| | | | | | | | +|---------------------------------------------------------------|--------------------|------|---------------------------------------------|--|-----|--------| +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | +| Transmission Gap Pattern Sequence Information | O | | 9.2.2.53A | | YES | reject | +| Signalling Bearer Request Indicator | O | | 9.2.1.55A | | YES | reject | +| HS-DSCH Information | O | | HS-DSCH FDD Information 9.2.2.18D | | YES | reject | +| HS-DSCH Information To Modify Unsynchronised | O | | 9.2.1.31HA | | YES | reject | +| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information 9.2.1.31IA | | YES | reject | +| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.31IB | | YES | reject | +| HS-DSCH RNTI | C-HSDSCH RadioLink | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | O | | RL ID 9.2.1.53 | | YES | reject | +| E-DPCH Information | | 0..1 | | | YES | reject | +| >Maximum Set of E-DPDCHs | O | | 9.2.2.20C | | – | | +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >E-TFCS Information | O | | 9.2.2.13Dh | | – | | +| >E-TTI | O | | 9.2.2.13Di | | – | | +| >E-DPCCH Power Offset | O | | 9.2.2.13Dj | | – | | +| >E-RGCH 2-Index-Step Threshold | O | | 9.2.2.13lg | | – | | +| >E-RGCH 3-Index-Step Threshold | O | | 9.2.2.13lh | | – | | +| >HARQ Info for E-DCH | O | | 9.2.2.18ba | | – | | +| >HS-DSCH Configured Indicator | O | | 9.2.2.18Ca | | – | | +| > Minimum Reduced E-DPDCH Gain Factor | O | | 9.2.2.114 | | YES | ignore | +| E-DCH FDD Information | O | | E-DCH FDD Information 9.2.2.13Da | | YES | reject | +| E-DCH FDD Information To Modify | O | | 9.2.2.13Df | | YES | reject | +| E-DCH MAC-d Flows To Add | O | | E-DCH FDD MAC-d Flows Information 9.2.2.13M | | YES | reject | +| E-DCH MAC-d Flows To Delete | O | | 9.2.1.73 | | YES | reject | +| Serving E-DCH RL | O | | 9.2.2.48B | | YES | reject | +| CPC Information | | 0..1 | | | YES | reject | +| >Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.66 | | – | | +| >Continuous Packet Connectivity DTX-DRX Information To Modify | O | | 9.2.2.67 | | – | | +| >Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.68 | | – | | +| >Continuous Packet | O | | 9.2.2.69A | | YES | reject | + +| | | | | | | | +|------------------------------------------------------------------------------------------|---|-----------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------| +| Connectivity HS-SCCH less Deactivate Indicator | | | | | | | +| No of Target Cell HS-SCCH Order | O | | INTEGER (1..30) | | YES | ignore | +| Additional HS Cell Information RL Reconf Req | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | reject | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >C-ID | O | | 9.2.1.9 | | – | | +| >HS-DSCH FDD Secondary Serving Information | O | | 9.2.2.18Da | | – | | +| >HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised | O | | 9.2.2.18EC | | – | | +| >HS-DSCH Secondary Serving Remove | O | | NULL | | – | | +| UE Aggregate Maximum Bit Rate | O | | 9.2.1.123 | | YES | ignore | +| Additional E-DCHCell Information RL Reconf Req | | 0..1 | | For E-DCH on multiple frequencies in this Node B. | YES | reject | +| >CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency | M | | | | YES | reject | +| >>Setup | | | | Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context | – | | +| >>> MultiCell E-DCH Transport Bearer Mode | M | | 9.2.2.130 | | – | | +| >>> Additional E-DCH Cell Information Setup | | 1..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>Additional E-DCH FDD Setup Information | M | | 9.2.2.131 | | – | | +| >>Configuration Change | | | | Used when RLs with additional E-DCH on the secondary UL frequency exist in the current Node B Communication context and the configuration is modified | – | | + +| | | | | | | | +|---------------------------------------------------------------------------|---|--------------------|--------------------------|-----------------------------------------------------------------------|-----|--------| +| | | | | (adding new RLs or modification of existing RLs) | | | +| >>>Additional E-DCH Cell Information Configuration Change | | 1.. | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>> Additional E-DCH Configuration Change Information | M | | 9.2.2.136 | | – | | +| >>Removal | | | | Used when all RLs on the indicated secondary UL frequency is removed. | – | | +| >>>Additional E-DCH Cell Information Removal | | 1.. | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | – | | +| >>>>RL on Secondary UL Frequency | M | | ENUMERATED (Remove, ...) | Removal of all RL on secondary UL frequency | – | | +| UL CLTD Information Reconf | O | | 9.2.2.151 | | YES | reject | +| E-DCH Decoupling Indication | O | | 9.2.2.194 | | YES | reject | +| Radio Links without DPCH/F-DPCH Indication | O | | 9.2.2.201 | | YES | reject | +| UL DPCCH2 Reconfiguration | O | | 9.2.2.202 | | YES | reject | +| Downlink TPC enhancements Reconf | O | | 9.2.2.215 | | YES | reject | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for a UE | +| maxNrOfRLs | Maximum number of RLs for a UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +| Condition | Explanation | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SF/2 | The IE shall be present if the Transmission Gap Pattern Sequence Information IE is included and the indicated Downlink Compressed Mode method for at least one of the included Transmission Gap Pattern Sequence is set to "SF/2". | +| HSDSCH Radio Link | The IE shall be present if HS-PDSCH RL ID IE is present. | + +#### 9.1.47.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-----------------------------------|------------------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| UL CCTrCH To Modify | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | O | | 9.2.1.58 | | – | | +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >UL SIR Target | O | | UL SIR 9.2.1.67A | Applicable to 1.28Mcps TDD only | YES | reject | +| UL CCTrCH To Delete | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| DL CCTrCH To Modify | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| >TFCS | O | | 9.2.1.58 | | – | | +| >Puncture Limit | O | | 9.2.1.50 | | – | | +| >DL CCTrCH To Modify Per RL | | 0..<maxNrOfRLs> | | See note 1 below | | | +| >>DL DPCH To Modify LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | ignore | +| >>>DL Timeslot Information LCR | | 0..<maxNrOfDLTSLCRs> | | | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on DPCH | – | | +| >>>>Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on DPCH | – | | +| >>CCTrCH Maximum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >>CCTrCH Minimum DL Transmission Power | O | | DL Power 9.2.1.21 | | YES | ignore | +| >>RL ID | O | | 9.2.1.53 | | YES | ignore | +| DL CCTrCH To Delete | | 0..<maxNrOfCCTrCHs> | | | EACH | notify | +| >CCTrCH ID | M | | 9.2.3.3 | | – | | +| DCHs To Modify | O | | DCHs TDD To Modify 9.2.3.4D | | YES | reject | +| DCHs To Add | O | | DCH TDD Information 9.2.3.4C | | YES | reject | +| DCHs To Delete | | 0..<maxNrOfDCHs> | | | GLOBAL | reject | +| >DCH ID | M | | 9.2.1.20 | | – | | +| RL Information | | 0..<maxNr | | See note 1 | YES | reject | + +| | | | | | | | +|--|--|------------------|--|-------|--|--| +| | | OfRLs> | | below | | | +|--|--|------------------|--|-------|--|--| + +| | | | | | | | +|----------------------------------------------|--------------------|------|--------------------------------------------------|-----------------------------------------------------------------------------|-----|--------| +| >RL ID | M | | 9.2.1.53 | | – | | +| >Maximum Downlink Power | O | | DL Power
9.2.1.21 | | – | | +| >Minimum Downlink Power | O | | DL Power
9.2.1.21 | | – | | +| >RL Specific DCH Information | O | | 9.2.1.53G | | YES | ignore | +| >UL Synchronisation Parameters LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore | +| >>Uplink Synchronisation Step Size | M | | 9.2.3.26H | | – | | +| >>Uplink Synchronisation Frequency | M | | 9.2.3.26G | | – | | +| Signalling Bearer Request Indicator | O | | 9.2.1.55A | | YES | reject | +| HS-DSCH Information | O | | HS-DSCH TDD Information
9.2.3.5F | | YES | reject | +| HS-DSCH Information To Modify Unsynchronised | O | | 9.2.1.31HA | | YES | reject | +| HS-DSCH MAC-d Flows To Add | O | | HS-DSCH MAC-d Flows Information
9.2.1.31IA | | YES | reject | +| HS-DSCH MAC-d Flows To Delete | O | | 9.2.1.31IB | | YES | reject | +| HS-DSCH RNTI | C-HSDSCH RadioLink | | 9.2.1.31J | | YES | reject | +| HS-PDSCH RL ID | O | | RL ID
9.2.1.53 | | YES | reject | +| E-DCH Information | | 0..1 | | 3.84Mcps TDD only | YES | reject | +| >E-PUCH Information | O | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to Add | O | | E-DCH MAC-d Flows Information
TDD
9.2.3.47 | | – | | +| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled Grant Information TDD | O | | 9.2.3.48 | | – | | +| >E-DCH TDD Information | O | | 9.2.3.49 | | – | | +| >E-DCH TDD Information to Modify | O | | 9.2.3.52 | | – | | +| E-DCH Serving RL | O | | RL ID
9.2.1.53 | | YES | reject | +| E-DCH Information 7.68Mcps | | 0..1 | | 7.68Mcps TDD only | YES | reject | +| >E-PUCH Information | O | | 9.2.3.45 | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to Add | O | | E-DCH MAC-d Flows Information
TDD | | – | | + +| | | | | | | | +|--|--|--|----------|--|--|--| +| | | | 9.2.3.47 | | | | +|--|--|--|----------|--|--|--| + +| | | | | | | | +|---------------------------------------------------------------|---|------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled Grant Information 7.68Mcps TDD | O | | 9.2.3.64 | | – | | +| >E-DCH TDD Information 7.68Mcps | O | | 9.2.3.65 | | – | | +| >E-DCH TDD Information to Modify | O | | 9.2.3.52 | | – | | +| E-DCH Information 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | YES | reject | +| >E-PUCH Information LCR | O | | 9.2.3.45a | | – | | +| >E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| >E-DCH MAC-d Flows to Add | O | | E-DCH MAC-d Flows Information TDD 9.2.3.47 | | – | | +| >E-DCH MAC-d Flows to Delete | O | | 9.2.1.73 | | – | | +| >E-DCH Non-scheduled Grant Information LCR TDD | O | | 9.2.3.48a | | – | | +| >E-DCH TDD Information LCR | O | | 9.2.3.49a | | – | | +| >E-DCH TDD Information to Modify | O | | 9.2.3.52 | | – | | +| Power Control GAP | O | | INTEGER (1..255) | Unit: Number of subframes Applicable to 1.28Mcps TDD only | YES | ignore | +| CPC Information | | 0..1 | | | YES | reject | +| >Continuous Packet Connectivity DRX Information LCR | O | | 9.2.3.93 | | – | | +| >Continuous Packet Connectivity DRX Information To Modify LCR | O | | 9.2.3.94 | | – | | +| >HS-DSCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.96 | | – | | +| >HS-DSCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.96a | | – | | +| >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.100 | | YES | reject | +| >E-DCH Semi-Persistent scheduling Information LCR | O | | 9.2.3.97 | | – | | +| >E-DCH Semi-Persistent scheduling Information to modify LCR | O | | 9.2.3.97a | | – | | +| >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR | O | | 9.2.3.101 | | YES | reject | +| Idle Interval Information | O | | 9.2.3.102 | TDD only | YES | ignore | +| UE Selected MBMS Service Information | O | | 9.2.3.104 | This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD | YES | ignore | + +| | | | | | | | +|--|--|--|--|-------|--|--| +| | | | | only. | | | +|--|--|--|--|-------|--|--| + +| | | | | | | | +|--------------------------------------------------|---|------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| HS-SCCH TPC step size | O | | TDD TPC DL Step Size 9.2.3.21 | 1.28 Mcps TDD only. This IE is mandatory if 'E-DCH Information 1.28Mcps' IE is absent. | YES | ignore | +| DCH Measurement Occasion Information | O | | 9.2.3.111 | Applicable for 1.28 Mcps TDD. | YES | reject | +| HS-DSCH-RNTI for FACH | O | | HS-DSCH RNTI 9.2.1.31J | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information Reconf | | 0..1 | | Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only | YES | reject | +| >CHOICE continue,Setup or Change | M | | | | – | | +| >>continue | | | | Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration keeps unchanged. | – | | +| >>Setup | | | | Used when the Multi-carrier E-DCH is not configured for this RL in the current Node B Communication Context | – | | +| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | M | | 9.2.3.113 | | – | | +| >>>UL Multi-Carrier E-DCH Information LCR | M | | 9.2.3.112 | | – | | +| >>change | | | | Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration is modified (adding new frequencies, modification of existing configuration or removing existing frequencies) | – | | +| >>>Multi-Carrier E-DCH Transport Bearer Mode LCR | O | | 9.2.3.113 | | – | | +| >>>UL Multi-Carrier E-DCH Information LCR | O | | 9.2.3.112 | | – | | + +| | | | | | | | +|---------------------------------------------------|---|------------------------------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>>Removal UL Multi-Carrier info | | 0..<maxNrOfULCarriersLCR-1> | | | – | | +| >>>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | – | | +| MU-MIMO Information | O | | 9.2.3.116 | 1.28 Mcps TDD only | YES | ignore | +| MU-MIMO Information To Reconfigure | O | | 9.2.3.117 | 1.28 Mcps TDD only | YES | ignore | +| UE support of non-rectangular resource allocation | O | | ENUMERATED (support) | 1.28 Mcps TDD only.
The absence of this IE indicates that the UE does not support the non-rectangular resource allocation. | YES | ignore | + +NOTE 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticality. + +| Range Bound | Explanation | +|-------------------------------|-----------------------------------------------------------------------| +| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE | +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD | +| maxNrOfDCHs | Maximum number of DCHs for a UE | +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfULCarriersLCR-1 | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation | + +| Condition | Explanation | +|-----------------|-----------------------------------------------------------------| +| HSDSCHRadioLink | The IE shall be present if HS-PDSCH RL ID IE is present. | + +### 9.1.48 RADIO LINK RECONFIGURATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------|----------|------------------------------------|-----------------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| RL Information Response | | 0..<maxNr OfRLs> | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >DCH Information Response | O | | 9.2.1.20C | | YES | ignore | +| >DL Power Balancing Updated Indicator | O | | 9.2.2.12D | FDD only | YES | ignore | +| >E-DCH RL Set ID | O | | RL Set ID 9.2.2.39 | | YES | ignore | +| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | YES | ignore | +| >E-DCH FDD Information Response | O | | 9.2.2.13Db | | YES | ignore | +| >HS-DSCH Preconfiguration Info | O | | 9.2.2.111 | | YES | ignore | +| >Non-Serving RL Preconfiguration Info | O | | 9.2.2.145 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| Target Communication Control Port ID | O | | Communication Control Port ID 9.2.1.15 | | YES | ignore | +| HS-DSCH FDD Information Response | O | | 9.2.2.18E | FDD only | YES | ignore | +| HS-DSCH TDD Information Response | O | | 9.2.3.5G | TDD only | YES | ignore | +| E-DCH TDD Information Response | O | | E-DCH TDD Information Response 9.2.3.50 | TDD only | YES | ignore | +| MAC-hs Reset Indicator | O | | 9.2.1.38Ac | | YES | ignore | +| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.69 | FDD only | YES | ignore | +| Additional HS Cell Information Response | | 0..<maxNr OfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >HS-DSCH FDD Secondary Serving Information Response | M | | 9.2.2.18EA | FDD only | – | | +| Continuous Packet Connectivity DRX Information Response LCR | O | | 9.2.3.95 | 1.28 Mcps TDD only | YES | ignore | +| HS-DSCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.98 | 1.28 Mcps TDD only | YES | ignore | + +| | | | | | | | +|------------------------------------------------------------|---|--------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------| +| E-DCH Semi-Persistent scheduling Information Response LCR | O | | 9.2.3.99 | 1.28 Mcps TDD only | YES | ignore | +| Additional E-DCH Cell Information Response RLReconf | | 0.. | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | EACH | ignore | +| >Additional E-DCH FDD Information Response | O | | 9.2.2.135 | For new E-DCH Radio Links on secondary uplink frequency | – | | +| >Additional Modified E-DCH FDD Information Response | O | | 9.2.2.141 | | – | | +| E-RNTI for FACH | O | | E-RNTI 9.2.1.75 | 1.28 Mcps TDD only | YES | ignore | +| Multi-Carrier E-DCH Information Response LCR | O | | 9.2.3.114 | 1.28 Mcps TDD only | YES | ignore | +| MU-MIMO Information Response | O | | 9.2.3.118 | 1.28 Mcps TDD only | YES | reject | +| Non-rectangular resource allocation indicator | O | | ENUMERATED (activate) | 1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used. | YES | reject | +| Non-rectangular resource timeslot set | O | | BIT STRING (SIZE(7)) | 1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicates which of the timeslot(s) is/are allocated for non-rectangular resource.
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for | YES | reject | + +| | | | | | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource. Bit 0 is the first/leftmost bit of the bit string. | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfRLs | Maximum number of RLs for a UE | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +### 9.1.49 RADIO LINK DELETION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-----------------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | reject | +| CRNC Communication Context ID | M | | 9.2.1.18 | | YES | reject | +| RL Information | | 1.. | | | EACH | notify | +| >RL ID | M | | 9.2.1.53 | | – | | + +| Range Bound | Explanation | +|-------------------|------------------------------------------| +| maxNrOfRLs | Maximum number of radio links for one UE | + +### 9.1.50 RADIO LINK DELETION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.51 DL POWER CONTROL REQUEST [FDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------------------|-----------------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| Power Adjustment Type | M | | 9.2.2.27 | | YES | ignore | +| DL Reference Power | C-Common | | DL power 9.2.1.21 | Power on DPCH or on F-DPCH | YES | ignore | +| Inner Loop DL PC Status | O | | 9.2.2.18B | | YES | ignore | +| DL Reference Power Information | C-Individual | 1.. | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >DL Reference Power | M | | DL power 9.2.1.21 | Power on DPCH or on F-DPCH | – | | +| Max Adjustment Step | C-CommonOrIndividual | | 9.2.2.20 | | YES | ignore | +| Adjustment Period | C-CommonOrIndividual | | 9.2.2.B | | YES | ignore | +| Adjustment Ratio | C-CommonOrIndividual | | 9.2.2.C | | YES | ignore | + +| Condition | Explanation | +|--------------------|------------------------------------------------------------------------------------------------| +| Common | The IE shall be present if the Adjustment Type IE is equal to "Common". | +| Individual | The IE shall be present if the Adjustment Type IE is equal to "Individual". | +| CommonOrIndividual | The IE shall be present if the Adjustment Type IE is equal to "Common" or "Individual". | + +| Range Bound | Explanation | +|-------------------|----------------------------------------| +| maxNrOfRLs | Maximum number of Radio Links for a UE | + +### 9.1.52 DEDICATED MEASUREMENT INITIATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|---------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used when the Report characteristics type is set to "On Demand". | YES | reject | +| Measurement ID | M | | 9.2.1.42 | | YES | reject | +| CHOICE Dedicated Measurement Object Type | M | | | | YES | reject | +| >RL | | | | | | | +| >>RL Information | | 1.. | | | EACH | reject | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>DPCH ID | O | | 9.2.3.5 | TDD only | – | | +| >>>PUSCH Information | | 0.. | | TDD only | GLOBAL | reject | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>HS-SICH Information | | 0.. | | TDD only | GLOBAL | reject | +| >>>>HS-SICH ID | M | | 9.2.3.5Gb | For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored | – | | +| >>>>Extended HS-SICH ID | O | | 9.2.3.5K | Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. See note 1 below. | – | | +| >>>DPCH ID 7.68Mcps | O | | 9.2.3.42 | Included for 7.68Mcps TDD for downlink DPCH | YES | reject | +| >RLS | | | | FDD only | | | +| >>RL Set Information | | 1.. | | | – | | + +| | | | | | | | +|----------------------------------------|---------------------------|---|----------------------------------|-------------------|-----|--------| +| | | > | | | | | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >ALL RL | | | NULL | | | | +| >ALL RLS | | | NULL | FDD only | | | +| Dedicated Measurement Type | M | | 9.2.1.23 | | YES | reject | +| Measurement Filter Coefficient | O | | 9.2.1.41 | | YES | reject | +| Report Characteristics | M | | 9.2.1.51 | | YES | reject | +| CFN Reporting Indicator | M | | FN Reporting Indicator 9.2.1.29B | | YES | reject | +| CFN | O | | 9.2.1.7 | | YES | reject | +| Number Of Reported Cell Portions | C-BestCellPortionsMeas | | 9.2.2.23D | FDD only | YES | reject | +| Measurement Recovery Behavior | O | | 9.2.1.43A | | YES | ignore | +| Alternative Format Reporting Indicator | O | | 9.2.1.1B | | YES | ignore | +| Number Of Reported Cell Portions LCR | C-BestCellPortionsMeasLCR | | 9.2.3.108 | 1.28Mcps TDD only | YES | reject | + +Note 1: This information element is a simplified representation of the ASN.1. + +| Condition | Explanation | +|-------------------------|---------------------------------------------------------------------------------------------------------| +| BestCellPortionsMeas | The IE shall be present if the Dedicated Measurement Type IE is set to "Best Cell Portions". | +| BestCellPortionsMeasLCR | The IE shall be present if the Dedicated Measurement Type IE is set to "Best Cell Portions LCR". | + +| Range Bound | Explanation | +|-----------------------|----------------------------------------------------------------------| +| maxNrOfRLs | Maximum number of individual RLs a measurement can be started on | +| maxNrOfPUSCHs | Maximum number of PUSCHs per RL a measurement can be started on | +| maxNrOfRLSets | Maximum number of individual RL Sets a measurement can be started on | +| maxNrOfHSSICHs | Maximum number of HSSICHs per RL a measurement can be started on | + +### 9.1.53 DEDICATED MEASUREMENT INITIATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|--------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | | YES | ignore | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| CHOICE Dedicated Measurement Object Type | O | | | Dedicated Measurement Object Type the measurement was initiated with | YES | ignore | +| >RL or ALL RL | | | | See Note 1 | | | +| >>RL Information | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>DPCH ID | O | | 9.2.3.5 | TDD only | – | | +| >>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>CFN | O | | 9.2.1.7 | Dedicated Measurement Time Reference | – | | +| >>>PUSCH Information | | 0.. | | TDD only
See note 3 | GLOBAL | reject | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>Dedicated Measurement Value | O | | 9.2.1.24 | | – | | +| >>>HS-SICH ID | O | | 9.2.3.5Gb | TDD only
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored | YES | reject | +| >>>Multiple Dedicated Measurement Value Information | | 0.. | | Applicable to 3.84Mcps TDD only | GLOBAL | ignore | +| >>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>Multiple Dedicated Measurement Value Information LCR | | 0.. | | Applicable to 1.28McpsTDD only | GLOBAL | ignore | +| >>>>DPCH ID | M | | 9.2.3.5 | | – | | +| >>>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>Multiple HS-SICH Measurement Value Information | | 0.. | | TDD only | GLOBAL | ignore | + +| | | | | | | | +|----------------------------------------------------------------------|---|------------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>>>HS-SICH ID | M | | 9.2.3.5Gb | For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE , the HS-SICH ID IE shall be ignored | – | | +| >>>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>>Extended HS-SICH ID | O | | 9.2.3.5K | Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | YES | ignore | +| >>>DPCH ID 7.68Mcps | O | | 9.2.3.42 | Included for 7.68Mcps TDD for downlink DPCH | YES | reject | +| >>> Multiple Dedicated Measurement Value Information 7.68Mcps | | 0..<maxNrOfDPCHs768PerRL-1> | | Applicable to 7.68Mcps TDD only | GLOBAL | ignore | +| >>>>DPCH ID 7.68Mcps | M | | 9.2.3.42 | | – | | +| >>>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | YES | reject | +| > RLS or ALL RLS | | | | FDD only
See Note 2 | | | +| >> RL Set Information | | 1..<maxNrOfRLSets> | | | EACH | ignore | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >>>Dedicated Measurement Value | M | | 9.2.1.24 | | – | | +| >>>CFN | O | | 9.2.1.7 | Dedicated Measurement Time Reference | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| Measurement Recovery Support Indicator | O | | 9.2.1.43C | | YES | ignore | + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | This is a simplified representation of the ASN.1: there are two different choice tags "RL" and "ALL RL" in the ASN.1, each having exactly the same structure. | +| Note 2: | This is a simplified representation of the ASN.1: there are two different choice tags "RLS" and "ALL RLS" in the ASN.1, each having exactly the same structure. | +| Note 3: | This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfPUSCHs are represented by separate ASN.1 structures with different criticality. | + +| Range Bound | Explanation | +|-------------------------------|---------------------------------------------------------------------------------| +| maxNrOfRLs | Maximum number of individual RLs the measurement can be started on | +| maxNrOfPUSCHs | Maximum number of PUSCHs per RL a measurement can be started on | +| maxNrOfRLSets | Maximum number of individual RL Sets a measurement can be started on | +| maxNrOfDPCHsPerRL-1 | Maximum number of DPCHs per RL a measurement can be started on for 3.84Mcps TDD | +| maxNrOfDPCHsLCRPerRL-1 | Maximum number of DPCHs per RL a measurement can be started on for 1.28Mcps TDD | +| maxNrOfHSSICHs | Maximum number of HSSICHs per RL a measurement can be started on | +| maxNrOfDPCHs768PerRL-1 | Maximum number of DPCHs per RL a measurement can be started on for 7.68Mcps TDD | + +### 9.1.54 DEDICATED MEASUREMENT INITIATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | | YES | ignore | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.55 DEDICATED MEASUREMENT REPORT + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|--------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| CHOICE Dedicated Measurement Object Type | M | | | Dedicated Measurement Object Type the measurement was initiated with | YES | ignore | +| >RL or ALL RL | | | | See Note 1 | | | +| >>RL Information | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>DPCH ID | O | | 9.2.3.5 | TDD only | – | | +| >>>Dedicated Measurement Value Information | M | | 9.2.1.24A | | – | | +| >>>PUSCH Information | | 0.. | | TDD only
See note 3 | GLOBAL | reject | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>Dedicated Measurement Value | O | | 9.2.1.24 | | – | | +| >>>HS-SICH ID | O | | 9.2.3.5Gb | TDD only
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored | YES | reject | +| >>>DPCH ID 7.68Mcps | O | | 9.2.3.42 | Included for 7.68Mcps TDD for downlink DPCH | YES | reject | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | YES | ignore | +| >RLS or ALL RLS | | | | FDD only
See Note 2 | | | +| >>RL Set Information | | 1..OfRLSets
> | | | | | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >>>Dedicated
Measurement Value
Information | M | | 9.2.1.24A | | – | | +| Measurement Recovery
Reporting Indicator | O | | 9.2.1.43B | | YES | ignore | + +Note 1: This is a simplified representation of the ASN.1: there are two different choice tags "RL" and "ALL RL" in the ASN.1, each having exactly the same structure. +Note 2: This is a simplified representation of the ASN.1: there are two different choice tags "RLS" and "ALL RLS" in the ASN.1, each having exactly the same structure. +Note 3: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfPUSCHs are represented by separate ASN.1 structures with different criticality. + +| Range Bound | Explanation | +|----------------------|----------------------------------------------------------------------| +| maxNrOfRLs | Maximum number of individual RLs the measurement can be started on | +| maxNrOfPUSCHs | Maximum number of PUSCHs per RL a measurement can be started on | +| maxNrOfRLSets | Maximum number of individual RL Sets a measurement can be started on | + +### 9.1.56 DEDICATED MEASUREMENT TERMINATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall be used if this value was used when initiating the measurement. Otherwise, the reserved value "All NBCC" shall not be used. | YES | ignore | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | + +### 9.1.57 DEDICATED MEASUREMENT FAILURE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall be used if the Node B Communication Context ID was set to "All NBCC" when initiating the measurement. Otherwise, the reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Measurement ID | M | | 9.2.1.42 | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | + +### 9.1.58 RADIO LINK FAILURE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|---------------------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Reporting Object | M | | | Object for which the Failure shall be reported. | YES | ignore | +| >RL | | | | | | | +| >>RL Information | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | +| >RL Set | | | | FDD only | | | +| >>RL Set Information | | 1.. | | | EACH | ignore | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | +| >CCTrCH | | | | TDD only | | | +| >>RL ID | M | | 9.2.1.53 | | – | | +| >>CCTrCH List | | 1.. | | | EACH | ignore | +| >>>CCTrCH ID | M | | 9.2.3.3 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | + +| Range Bound | Explanation | +|-----------------------|--------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfRLSets | Maximum number of RL Sets for one UE | +| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE | + +### 9.1.59 RADIO LINK RESTORE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|---------------------|-----------------------|-----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| CHOICE Reporting Object | M | | | Object for which the Restoration shall be reported. | YES | ignore | +| >RL | | | | TDD only | | | +| >>Radio Link Information | | 1.. | | | EACH | ignore | +| >>>RL ID | M | | 9.2.1.53 | | – | | +| >RL Set | | | | FDD only | | | +| >>RL Set Information | | 1.. | | | EACH | ignore | +| >>>RL Set ID | M | | 9.2.2.39 | | – | | +| >CCTrCH | | | | TDD only | | | +| >>RL ID | M | | 9.2.1.53 | | – | | +| >>CCTrCH List | | 1.. | | | EACH | ignore | +| >>>CCTrCH ID | M | | CCTrCH ID 9.2.3.3 | | – | | + +| Range Bound | Explanation | +|-----------------------|--------------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | +| maxNrOfRLSets | Maximum number of RL Sets for one UE | +| maxNrOfCCTrCHs | Maximum number of CCTrCHs for a UE | + +### 9.1.60 COMPRESSED MODE COMMAND [FDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| Active Pattern Sequence Information | M | | 9.2.2.A | | YES | ignore | + +### 9.1.61 ERROR INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | O | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Node B Communication Context ID | O | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| Cause | O | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.62 PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST + +#### 9.1.62.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|-------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Configuration Generation ID | M | | 9.2.1.16 | | YES | reject | +| SFN | O | | 9.2.1.53A | | YES | reject | +| HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power | O | | Maximum Transmission Power 9.2.1.40 | Maximum transmission power to be allowed for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes | YES | reject | +| HS-PDSCH And HS-SCCH Scrambling Code | O | | DL Scrambling Code 9.2.2.13 | Scrambling code on which HS-PDSCH and HS-SCCH is transmitted. 0= Primary scrambling code of the cell 1...15 = Secondary scrambling code | YES | reject | +| HS-PDSCH FDD Code Information | O | | 9.2.2.18F | | YES | reject | +| HS-SCCH FDD Code Information | O | | 9.2.2.18G | | YES | reject | + +| | | | | | | | +|-----------------------------------------------------------|---|----------------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| E-AGCH And E-RGCH/E-HICH FDD Scrambling Code | O | | DL Scrambling Code 9.2.2.13 | Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted.
0= Primary scrambling code of the cell
1...15 = Secondary scrambling code | YES | reject | +| E-AGCH FDD Code Information | O | | 9.2.2.13lb | | YES | reject | +| E-RGCH/E-HICH FDD Code Information | O | | 9.2.2.13la | | YES | reject | +| HSDPA And E-DCH Cell Portion Information | | 0..<maxNrOfCellPortionsPerCell> | | | GLOBAL | reject | +| >Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >HS-PDSCH And HS-SCCH Scrambling Code | O | | DL Scrambling Code 9.2.2.13 | Scrambling code on which HS-PDSCH and HS-SCCH is transmitted over cell portion. | – | | +| >HS-PDSCH FDD Code Information | O | | 9.2.2.18F | | – | | +| >HS-SCCH FDD Code Information | O | | 9.2.2.18G | | – | | +| >HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power | O | | Maximum Transmission Power 9.2.1.40 | Maximum transmission power to be allowed for HS-PDSCH, HS-SCCH and E-AGCH, E-RGCH and E-HICH codes over cell portion | – | | +| >E-AGCH And E-RGCH/E-HICH FDD Scrambling Code | O | | DL Scrambling Code 9.2.2.13 | Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted over cell portion. | – | | +| >E-AGCH FDD Code Information | O | | 9.2.2.13lb | | – | | +| >E-RGCH/E-HICH FDD Code Information | O | | 9.2.2.13la | | – | | +| >Maximum Target Received Total Wide Band Power | O | | 9.2.2.21a | | YES | ignore | +| >Reference Received Total Wide Band Power | O | | 9.2.2.39B | | YES | ignore | +| Maximum Target Received Total Wide Band Power | O | | 9.2.2.21a | | YES | reject | + +| | | | | | | | +|-----------------------------------------------------|---|--|-------------------------------------|--|-----|--------| +| Reference Received Total Wide Band Power | O | | 9.2.2.39B | | YES | ignore | +| Target Non-serving E-DCH to Total E-DCH Power ratio | O | | 9.2.2.21b | | YES | reject | +| HS-DSCH Common System Information | O | | 9.2.2.75 | | YES | reject | +| Common MAC Flows to Delete | O | | 9.2.2.97 | | YES | reject | +| HS-DSCH Paging System Information | O | | 9.2.2.76 | | YES | reject | +| Paging MAC Flows to Delete | O | | 9.2.2.98 | | YES | reject | +| Common E-DCH System Information | O | | 9.2.2.103 | | YES | Reject | +| Common UL MAC Flows to Delete | O | | Common MAC Flows to Delete 9.2.2.97 | | YES | Reject | +| Common E-DCH MAC-d Flows to Delete | O | | E-DCH MAC Flows to Delete 9.2.1.73 | | YES | Reject | +| Enhanced UE DRX Information | O | | 9.2.2.108 | | YES | reject | +| HS-SCCH DRX Information | O | | 9.2.2.220 | | YES | reject | +| Further Enhanced UE DRX Information | O | | 9.2.2.185 | | YES | ignore | +| Common E-RGCH Operation Indicator | O | | ENUMERATED(true) | | YES | ignore | + +| Range Bound | Explanation | +|----------------------------|-------------------------------------------| +| MaxNrOfCellPortionsPerCell | Maximum number of Cell Portions in a cell | + +##### 9.1.6.2.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-----------------------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| SFN | O | | 9.2.1.53A | | YES | reject | +| PDSCH Sets To Add | | 0.. | | | GLOBAL | reject | +| >PDSCH Set ID | M | | 9.2.3.11 | | – | | +| >PDSCH To Add Information | | 0..1 | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>DL Timeslot Information | | 1.. | | | – | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | + +| | | | | | | | +|-------------------------------------------|---|------------------------|-----------|-----------------------------------------------------------------------------|-----|--------| +| >>>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | +| >>>DL Code Information | | 1.. | | | – | | +| >>>>PDSCH ID | M | | 9.2.3.10 | | – | | +| >>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >PDSCH To Add Information LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>DL Timeslot Information LCR | | 1.. | | | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | +| >>>DL Code Information LCR | | 1.. | | | – | | +| >>>>PDSCH ID | M | | 9.2.3.10 | | – | | +| >>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>>TDD DL DPCH Time Slot Format LCR | O | | 9.2.3.19D | | YES | reject | +| >>TSTD Indicator | O | | 9.2.1.64 | | YES | reject | +| >PDSCH To Add Information 7.68Mcps | | 0..1 | | Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>DL Timeslot Information 7.68Mcps | | 1.. | | | – | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | +| >>>DL Code Information 7.68Mcps | | 1.. | | | – | | +| >>>>PDSCH ID 7.68Mcps | M | | 9.2.3.43 | | – | | + +| | | | | | | | +|--------------------------------------------------------|---|-----------------------------------|-----------|---------------------|--------|--------| +| >>>>TDD
Channelisation Code
7.68Mcps | M | | 9.2.3.34 | | – | | +| PDSCH Sets To Modify | | 0..<
maxNrOfP
DSCHSet
s> | | | GLOBAL | reject | +| >PDSCH Set ID | M | | 9.2.3.11 | | – | | +| >CHOICE HCR or LCR or
7.68 Mcps | M | | | See note 1
below | – | | +| >>3.84Mcps TDD | | | | | – | | +| >>>PDSCH To Modify
Information | | 1 | | | YES | reject | +| >>>>Repetition
Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition
Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical
Channel Offset | O | | 9.2.3.20 | | – | | +| >>>>DL Timeslot
Information | | 0..OfDLTSS> | | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble
Shift And Burst
Type | O | | 9.2.3.7 | | – | | +| >>>>>TFCI
Presence | O | | 9.2.1.57 | | – | | +| >>>>>DL Code
Information | | 0..OfPDSCH
s> | | | – | | +| >>>>>>PDSCH
ID | M | | 9.2.3.10 | | – | | +| >>>>>>TDD
Channelisation
Code | M | | 9.2.3.19 | | – | | +| >>1.28Mcps TDD | | | | | – | | +| >>>PDSCH To Modify
Information LCR | | 1 | | | YES | reject | +| >>>>Repetition
Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition
Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical
Channel Offset | O | | 9.2.3.20 | | – | | +| >>>>DL Timeslot
Information LCR | | 0..OfDLTSL
CRs> | | | – | | +| >>>>>Time Slot
LCR | M | | 9.2.3.24A | | – | | +| >>>>>Midamble
Shift LCR | O | | 9.2.3.7A | | – | | +| >>>>>TFCI
Presence | O | | 9.2.1.57 | | – | | +| >>>>>DL Code
Information LCR | | 0..OfPDSCH
s> | | | – | | +| >>>>>>PDSCH
ID | M | | 9.2.3.10 | | – | | + +| | | | | | | | +|---------------------------------------------------|---|------------------------------------|-----------|--------------------------------------------------------------------------------------------|--------|--------| +| >>>>>>TDD
Channelisation
Code LCR | M | | 9.2.3.19a | | – | | +| >>>>>>TDD DL
DPCH Time Slot
Format LCR | O | | 9.2.3.19D | | YES | reject | +| >>7.68Mcps TDD | | | | | – | | +| >>>PDSCH To Modify
Information 7.68Mcps | | 1 | | | YES | reject | +| >>>>Repetition
Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition
Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical
Channel Offset | O | | 9.2.3.20 | | – | | +| >>>>DL Timeslot
Information
7.68Mcps | | 0..OfDLTSs> | | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble
Shift And Burst
Type 7.68Mcps | O | | 9.2.3.35 | | – | | +| >>>>>TFCI
Presence | O | | 9.2.1.57 | | – | | +| >>>>>DL Code
Information
7.68Mcps | | 0..OfPDSCH
s> | | | – | | +| >>>>>PDSCH
ID 7.68Mcps | M | | 9.2.3.43 | | – | | +| >>>>>TDD
Channelisation
Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| PDSCH Sets To Delete | | 0..<
maxNrOfP
DSCHSet
s > | | | GLOBAL | reject | +| >PDSCH Set ID | M | | 9.2.3.11 | | – | | +| PUSCH Sets To Add | | 0..<
maxNrOfP
USCHSet
s > | | | GLOBAL | reject | +| >PUSCH Set ID | M | | 9.2.3.13 | | – | | +| >PUSCH To Add
Information | | 0..1 | | Mandatory for
3.84Mcps TDD.
Not Applicable
to 1.28Mcps
TDD or
7.68Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical
Channel Offset | M | | 9.2.3.20 | | – | | +| >>UL Timeslot
Information | | 1..OfULTSs> | | | – | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>Midamble Shift
And Burst Type | M | | 9.2.3.7 | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | + +| | | | | | | | +|-------------------------------------------------|---|------------------------------------|-----------|------------------------------------------------------------------------------|--------|--------| +| >>>UL Code Information | | 1..<maxNrOfPUSCHs> | | | – | | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >PUSCH To Add Information LCR | | 0..1 | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>UL Timeslot Information LCR | | 1..<maxNrOfULTSLCRs> | | | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | +| >>>UL Code Information LCR | | 1..<maxNrOfPUSCHs> | | | – | | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>>TDD UL DPCH Time Slot Format LCR | O | | 9.2.3.21C | | YES | reject | +| >PUSCH To Add Information 7.68Mcps | | 0..1 | | Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD. | YES | reject | +| >>Repetition Period | M | | 9.2.3.16 | | – | | +| >>Repetition Length | M | | 9.2.3.15 | | – | | +| >>TDD Physical Channel Offset | M | | 9.2.3.20 | | – | | +| >>UL Timeslot Information 7.68Mcps | | 1..<maxNrOfULTSSs> | | | – | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>>TFCI Presence | M | | 9.2.1.57 | | – | | +| >>>UL Code Information 7.68Mcps | | 1..<maxNrOfPUSCHs> | | | – | | +| >>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| PUSCH Sets To Modify | | 0..<maxNrOfPUSCHSets> | | | GLOBAL | reject | +| >PUSCH Set ID | M | | 9.2.3.13 | | – | | + +| | | | | | | | +|-----------------------------------------|---|------------------------|-----------|------------------|-----|--------| +| >CHOICE HCR or LCR or 7.68Mcps | M | | | See note 1 below | – | | +| >>3.84Mcps TDD | | | | | – | | +| >>>PUSCH To Modify Information | | 1 | | | YES | reject | +| >>>>Repetition Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical Channel Offset | O | | 9.2.3.20 | | – | | +| >>>>UL Timeslot Information | | 0.. | | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble Shift And Burst Type | O | | 9.2.3.7 | | – | | +| >>>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>>UL Code Information | | 0.. | | | – | | +| >>>>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>1.28Mcps TDD | | | | | – | | +| >>>PUSCH To Modify Information LCR | | 1 | | | YES | reject | +| >>>>Repetition Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical Channel Offset | O | | 9.2.3.20 | | – | | +| >>>>UL Timeslot Information LCR | | 0.. | | | – | | +| >>>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>>>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>>UL Code Information LCR | | 0.. | | | – | | +| >>>>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>>>TDD Channelisation Code LCR | M | | 9.2.3.19a | | – | | +| >>>>>>TDD UL DPCH Time Slot Format LCR | O | | 9.2.3.21C | | YES | reject | +| >>7.68Mcps TDD | | | | | – | | +| >>>PUSCH To Modify Information 7.68Mcps | | 1 | | | YES | reject | + +| | | | | | | | +|----------------------------------------------------------|---|--------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------|--------|--------| +| >>>>Repetition Period | O | | 9.2.3.16 | | – | | +| >>>>Repetition Length | O | | 9.2.3.15 | | – | | +| >>>>TDD Physical Channel Offset | O | | 9.2.3.20 | | – | | +| >>>> UL Timeslot Information 7.68Mcps | | 0..<maxNr OfULTSs> | | | – | | +| >>>>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>>>Midamble Shift And Burst Type 7.68Mcps | O | | 9.2.3.35 | | – | | +| >>>>>TFCI Presence | O | | 9.2.1.57 | | – | | +| >>>>> UL Code Information 7.68Mcps | | 0..<maxNr OfPUSCHs> | | | – | | +| >>>>>>PUSCH ID | M | | 9.2.3.12 | | – | | +| >>>>>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| PUSCH Sets To Delete | | 0..<maxNr OfPDSCH Sets> | | | GLOBAL | reject | +| >PUSCH Set ID | M | | 9.2.3.13 | | – | | +| HS-PDSCH TDD Information | | 0..1 | | | GLOBAL | reject | +| > DL Timeslot and Code Information | | 0..<maxNr OfDLTSs> | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD. | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >> Codes | | 1..<maxNr OfHSPDSCHs> | | | – | | +| >>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>HS-PDSCH and HS-SCCH Total Power | O | | Maximum Transmission Power 9.2.1.40 | Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot | YES | reject | +| > DL Timeslot and Code Information LCR per UARFCN | | 0..<maxFrequencyinCell> | | Mandatory for 1.28Mcps TDD Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. See note 2 below | EACH | reject | +| >>DL Timeslot and Code Information LCR | | 0..<maxNr OfDLTSLCRs> | | . | – | | + +| | | | | | | | +|--------------------------------------------------------------|---|-------------------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------|--------|--------| +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>Codes LCR | | 1..<maxNrOfHSPDSCHs> | | | – | | +| >>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>HS-PDSCH and HS-SCCH Total Power | O | | Maximum Transmission Power 9.2.1.40 | Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot | YES | reject | +| >>>HS-PDSCH and HS-SCCH Total Power per CELL PORTION | | 0..<maxNrOfCellPortionsPerCellLCR> | | | EACH | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>> HS-PDSCH and HS-SCCH Total Power Value for CELL PORTION | M | | Maximum Transmission Power 9.2.1.40 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Mandatory for 1.28Mcps TDD when using multiple frequencies. | – | | +| >DL Timeslot and Code Information 7.68Mcps | | 0..<maxNrOfDLTSSs> | | Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD. | GLOBAL | reject | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>Codes 7.68Mcps | | 1..<> | | | – | | +| >>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>HS-PDSCH and HS-SCCH Total Power | O | | Maximum Transmission Power 9.2.1.40 | Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot | – | – | +| Add to HS-SCCH Resource Pool | | 0..1 | | | GLOBAL | reject | +| >HS-SCCH Information | | 0..<maxNrOfHSSCCHs> | | Applicable to 3.84Mcps TDD only | – | | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | + +| | | | | | | | +|----------------------------------------|---|-----------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>Maximum HS-SCCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>HS-SICH Information | | 1 | | | – | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | | – | | +| >>>Time Slot | M | | 9.2.3.23 | | – | | +| >>>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >HS-SCCH Information LCR | | 0..<maxNrOfHSSCC Hs> | | Applicable to 1.28Mcps TDD only
See note 3 below | – | | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | If the Extended HS-SCCH ID IE is included in the HS-SCCH Information LCR IE, the HS-SCCH ID IE shall be ignored. | – | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>First TDD Channelisation Code | M | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Second TDD Channelisation Code | M | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Maximum HS-SCCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>HS-SICH Information LCR | | 1 | | | – | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored. | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | YES | ignore | + +| | | | | | | | +|---------------------------------------------|---|------------------------------------|-------------------|-----------------------------------------------------------------------------------------------------|--------|--------| +| >>Extended HS-SCCH ID | O | | 9.2.3.5J | The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31. | YES | ignore | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES- | ignore | +| >>HS-SICH Reference Signal Information | O | | 9.2.3.103 | | YES | ignore | +| >HS-SCCH Information 7.68Mcps | | 0..<maxNr OfHSSCC Hs> | | Applicable to 7.68Mcps TDD only | GLOBAL | reject | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | | - | | +| >>Time Slot | M | | 9.2.3.23 | | - | | +| >>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | - | | +| >>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | - | | +| >>Maximum HS-SCCH Power | M | | DL Power 9.2.1.21 | | - | | +| >>HS-SICH Information 7.68Mcps | | 1 | | | - | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | | - | | +| >>>Time Slot | M | | 9.2.3.23 | | - | | +| >>>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | - | | +| >>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | - | | +| Modify HS-SCCH Resource Pool | | 0..1 | | | GLOBAL | reject | +| >HS-SCCH Information | | 0..<maxNr OfHSSCC Hs> | | Applicable to 3.84Mcps TDD only | - | | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | | - | | +| >>Time Slot | O | | 9.2.3.23 | | - | | +| >>Midamble Shift And Burst Type | O | | 9.2.3.7 | | - | | +| >>TDD Channelisation Code | O | | 9.2.3.19 | | - | | +| >>Maximum HS-SCCH Power | O | | DL Power 9.2.1.21 | | - | | +| >>HS-SICH Information | | 0..1 | | | - | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | | - | | +| >>>Time Slot | O | | 9.2.3.23 | | - | | +| >>>Midamble Shift And Burst Type | O | | 9.2.3.7 | | - | | +| >>>TDD Channelisation Code | O | | 9.2.3.19 | | - | | + +| | | | | | | | +|----------------------------------------|---|-----------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >HS-SCCH Information LCR | | 0..<maxNrOfHSSCC Hs> | | Applicable to 1.28Mcps TDD only
See note 3 below | – | | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | If the Extended HS-SCCH ID IE is included in the HS-SCCH Information LCR IE , the HS-SCCH ID IE shall be ignored. | – | | +| >>Time Slot LCR | O | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>First TDD Channelisation Code | O | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Second TDD Channelisation Code | O | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Maximum HS-SCCH Power | O | | DL Power 9.2.1.21 | | – | | +| >>HS-SICH Information LCR | | 0..1 | | | – | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE , the HS-SICH ID IE shall be ignored. | – | | +| >>>Time Slot LCR | O | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | YES | ignore | +| >>Extended HS-SCCH ID | O | | 9.2.3.5J | The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31. | YES | ignore | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies. | YES | ignore | + +| | | | | | | | +|------------------------------------------------------------|---|-------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>HS-SICH Reference Signal Information Modify | | 0..1 | | | YES | reject | +| >>>HS-SICH Reference Signal Information | O | | 9.2.3.103 | | – | | +| >HS-SCCH Information 7.68Mcps | | 0..<maxNrOfHSSCC Hs> | | Applicable to 7.68Mcps TDD only | GLOBAL | reject | +| >>HS-SCCH ID | M | | 9.2.3.5Ga | | – | | +| >>Time Slot | O | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>Maximum HS-SCCH Power | O | | DL Power 9.2.1.21 | | – | | +| >>HS-SICH Information 7.68Mcps | | 0..1 | | | – | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | | – | | +| >>>Time Slot | O | | 9.2.3.23 | | – | | +| >>>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>>TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| Delete from HS-SCCH Resource Pool | | 0..<maxno of HSSCCHs > | | For 1.28Mcps TDD ,see note 3 below | GLOBAL | reject | +| >HS-SCCH ID | M | | 9.2.3.5Ga | For 1.28Mcps TDD, if the Extended HS-SCCH ID IE is included in the Delete from HS-SCCH Resource Pool IE, the HS-SCCH ID IE shall be ignored | – | | +| >Extended HS-SCCH ID | O | | 9.2.3.5J | Applicable to 1.28Mcps TDD only, the Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31. | YES | ignore | +| Configuration Generation ID | O | | 9.2.1.16 | | YES | reject | +| E-PUCH Information | | 0..1 | | 3.84Mcps TDD only | GLOBAL | reject | + +| | | | | | | | +|-----------------------------------------------------------------|---|--------------------------------------|-------------------|-----------------------------------------------|--------|--------| +| >LTGI Presence | M | | 9.2.3.58 | | – | | +| >SNPL Reporting Type | M | | 9.2.3.62 | | – | | +| >Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >E-PUCH Timeslot Information | | 1..<maxNrOfE-PUCHSlots> | | | – | | +| >>Time Slot | M | | 9.2.3.23 | | | | +| Add to E-AGCH Resource Pool | | 0..1 | | 3.84Mcps TDD only | GLOBAL | reject | +| >E-AGCH Information | | 0..<maxnoofEAGCHs> | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>Maximum E-AGCH Power | M | | DL Power 9.2.1.21 | | – | | +| Modify E-AGCH Resource Pool | | 0..1 | | 3.84Mcps TDD only | GLOBAL | reject | +| >E-AGCH Information | | 0..<maxnoofEAGCHs> | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot | O | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type | O | | 9.2.3.7 | | – | | +| >>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>Maximum E-AGCH Power | O | | DL Power 9.2.1.21 | | – | | +| Delete from E-AGCH Resource Pool | | 0..<maxnoofEAGCHs> | | | GLOBAL | reject | +| >E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| E-HICH Information | | 0..1 | | 3.84Mcps TDD only | GLOBAL | reject | +| >Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >Maximum E-HICH Power | M | | DL Power 9.2.1.21 | | – | | +| Maximum Generated Received Total Wide Band Power in Other Cells | O | | 9.2.3.63 | Applicable to 3.84Mcps and 7.68 Mcps TDD only | YES | reject | +| E-PUCH Information 7.68Mcps | | 0..1 | | 7.68Mcps TDD only | GLOBAL | reject | +| >LTGI Presence | M | | 9.2.3.58 | | – | | +| >SNPL Reporting Type | M | | 9.2.3.62 | | – | | +| >Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >E-PUCH Timeslot Information | | 1..<maxNrOfE-PUCHSlots> | | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| Add to E-AGCH Resource Pool 7.68Mcps | | 0..1 | | 7.68Mcps TDD only | GLOBAL | reject | + +| | | | | | | | +|-------------------------------------------------|---|-------------------------------------------|----------------------|----------------------|--------|--------| +| >E-AGCH Information | | 0..<maxno
ofEAG
CHs> | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And
Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>TDD Channelisation
Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >>Maximum E-AGCH
Power | M | | DL Power
9.2.1.21 | | – | | +| Modify E-AGCH Resource
Pool 7.68Mcps | | 0..1 | | 7.68Mcps TDD
only | GLOBAL | reject | +| >E-AGCH Information | | 0..<maxno
ofEAG
CHs> | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot | O | | 9.2.3.23 | | – | | +| >>Midamble Shift And
Burst Type 7.68Mcps | O | | 9.2.3.35 | | – | | +| >>TDD Channelisation
Code 7.68Mcps | O | | 9.2.3.34 | | – | | +| >>Maximum E-AGCH
Power | O | | DL Power
9.2.1.21 | | – | | +| E-HICH Information
7.68Mcps | | 0..1 | | 7.68Mcps TDD
only | GLOBAL | reject | + +| | | | | | | | +|----------------------------------------------------------|---|----------------------------|----------------------------------|-------------------------------------------------------------------------------------------------|--------|--------| +| >Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | – | | +| >Maximum E-HICH Power | M | | DL Power 9.2.1.21 | | – | | +| E-PUCH Information 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| >LTGI Presence | M | | 9.2.3.58 | | – | | +| >SNPL Reporting Type | M | | 9.2.3.62 | | – | | +| > E-PUCH Timeslot information 1.28Mcps per UARFCN | | 0.. | | See note 2 below | | | +| >> E-PUCH Timeslot Information 1.28Mcps | | 0.. | | | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>> Codes LCR | | 1.. | | | – | | +| >>>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| Add to E-AGCH Resource Pool 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| > E-AGCH Information 1.28Mcps | | 1.. | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>First TDD Channelisation Code | M | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Second TDD Channelisation Code | M | | TDD Channelisation Code 9.2.3.19 | | – | | +| >>Maximum E-AGCH Power | M | | DL Power 9.2.1.21 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| Modify E-AGCH Resource Pool 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| > E-AGCH Information 1.28Mcps | | 1.. | | | – | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| >>Time Slot LCR | O | | 9.2.3.24A | | – | | + +| | | | | | | | +|---------------------------------------------|---|--------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>First TDD
Channelisation Code | O | | TDD
Channelisation Code
9.2.3.19 | | – | | +| >>Second TDD
Channelisation Code | O | | TDD
Channelisation Code
9.2.3.19 | | – | | +| >>Maximum E-AGCH
Power | O | | DL Power
9.2.1.21 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| Add to E-HICH Resource Pool 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| >E-HICH Information 1.28Mcps | | 1.. | | | – | | +| >>E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored. | – | | +| >>E-HICH Type | M | | 9.2.3.68 | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>Maximum E-HICH
Power | M | | DL Power
9.2.1.21 | | – | | +| >>Extended E-HICH ID
TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | YES | ignore | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| Modify E-HICH Resource Pool 1.28Mcps | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| >E-HICH Information 1.28Mcps | | 1.. | | | – | | + +| | | | | | | | +|--------------------------------------------------|---|---------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored. | – | | +| >>E-HICH Type | O | | 9.2.3.68 | | – | | +| >>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>Time Slot LCR | O | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>Maximum E-HICH Power | O | | DL Power 9.2.1.21 | | – | | +| >>Extended E-HICH ID TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | YES | ignore | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Mandatory for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| Delete from E-HICH Resource Pool 1.28Mcps | | 0..<maxNrOfEHICHs> | | 1.28Mcps TDD only | GLOBAL | reject | +| >E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the Delete from E-HICH Resource Pool 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored. | – | | +| >Extended E-HICH ID TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | YES | ignore | + +| | | | | | | | +|------------------------------------------------------------|---|--------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| SYNC_UL Partition Information | | 0..1 | | Applicable to 1.28Mcps TDD to indicate the SYNC_UL partition information for the Primary Frequency. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | GLOBAL | reject | +| >E-RUCCH SYNC_UL codes bitmap | M | | BIT STRING SIZE(8) | Each bit indicates availability of a SYNC_UL code, where the SYNC_UL codes are numbered "code 0" to "code 7". The value 1 of a bit indicates that the corresponding SYNC_UL code can be used. The value 0 of a bit indicates that the corresponding SYNC_UL code can not be used. | – | | +| Maximum Target Received Total Wide Band Power LCR | O | | 9.2.3.69 | 1.28Mcps TDD only | YES | reject | +| HS-DSCH Common System Information LCR | O | | 9.2.3.72 | 1.28Mcps TDD only | YES | reject | +| Common MAC Flows To Delete LCR | O | | 9.2.3.78 | 1.28Mcps TDD only | YES | reject | +| HS-DSCH Paging System Information LCR | O | | 9.2.3.73 | 1.28Mcps TDD only | YES | reject | +| Paging MAC Flows to Delete LCR | O | | 9.2.3.85 | 1.28Mcps TDD only | YES | reject | +| Common E-DCH System Information LCR | O | | 9.2.3.79 | 1.28Mcps TDD only | YES | reject | +| Common UL MAC Flows to Delete LCR | O | | Common MAC Flows To Delete LCR 9.2.3.78 | 1.28Mcps TDD only | YES | reject | +| Common E-DCH MAC-d Flows to Delete LCR | O | | 9.2.3.86 | 1.28Mcps TDD only | YES | reject | +| Enhanced UE DRX Information LCR | O | | 9.2.3.82 | 1.28Mcps TDD only | YES | reject | +| Add to Non-HS-SCCH associated HS-SICH Resource Pool | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| >Non-HS-SCCH associated HS-SICH Information | | 0..oOfNon-
HS-
SCCH-
Assosiate
d-HS-
SICH> | | See note 4 below | – | | + +| | | | | | | | +|-----------------------------------------------------------------|---|--------------------------------------------------------------------|------------------|------------------------------------------------------------------------------------------------------------------|--------|--------| +| >>Non-HS-SCCH associated HS-SICH ID | M | | INTEGER (0..255) | | – | | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies. | – | | +| Modify Non-HS-SCCH associated HS-SICH Resource Pool | | 0..1 | | 1.28Mcps TDD only | GLOBAL | reject | +| >Non-HS-SCCH associated HS-SICH Information | | 0..oOfNon-
HS-
SCCH-
Assosiate
d-HS-
SICH> | | See note 4 below | – | | +| >>Non-HS-SCCH associated HS-SICH ID | M | | INTEGER (0..255) | | – | | +| >>Time Slot LCR | O | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | O | | 9.2.3.7A | | – | | +| >>TDD Channelisation Code | O | | 9.2.3.19 | | – | | +| >>UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies. | – | | +| Delete from Non-HS-SCCH associated HS-SICH Resource Pool | | 0..oOfNon-
HS-
SCCH-
Assosiate
d-HS-
SICH> | | 1.28Mcps TDD only.
See note 4 below | GLOBAL | reject | +| >Non-HS-SCCH associated HS-SICH ID | M | | INTEGER (0..255) | | – | | +| Power Control GAP for CELL_FACH | O | | INTEGER (1..255) | Unit: Number of subframes.

Mandatory for 1.28Mcps TDD.
Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. | YES | ignore | +| Maximum RTWP per UARFCN information LCR | | 0..<
maxFrequ
encyinCell
> | | 1.28Mcps TDD only | GLOBAL | ignore | +| >UARFCN | M | | 9.2.1.65 | | – | | + +| | | | | | | | +|---------------------------------------------------------------------|---|-------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------|--------|--------| +| >Maximum Target Received Total Wide Band Power LCR | M | | 9.2.3.69 | This IE shall be ignored if IE Maximum Target Received Total Wide Band Power per CELL PORTION LCR is included. | – | | +| >Maximum Target Received Total Wide Band Power per CELL PORTION LCR | | 0..<maxNrOfCellPortionsPerCellLCR> | | | GLOBAL | ignore | +| >>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>Maximum Target Received Total Wide Band Power LCR | M | | 9.2.3.69 | | – | | +| Out-of-sync Detection Window | O | | ENUMERATED (40, 80, 160, 320, 640, ...) | Unit: ms
Applicable to 1.28Mcps TDD. | YES | reject | +| Treset Usage Indicator | O | | NULL | Applicable to 1.28Mcps TDD only | YES | ignore | +| In Sync Indication Information LCR | O | | 9.2.3.123 | Applicable to 1.28Mcps TDD only | YES | ignore | + +Note 1: This information element is a simplified representation of the ASN.1. The choice is in reality performed through the use of ProtocolIE-Single-Container within the ASN.1. + +Note 2: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxFrequencyinCell are represented by separate ASN.1 structures with different criticalities. + +Note 3: This information element is a simplified representation of the ASN.1. Repetitions 1 to 32 and repetitions 33 to *maxNrOfHSSCCHs* are represented by separate ASN.1 structures. + +Note 4: This information element is a simplified representation of the ASN.1. Repetitions 1 to 4 and repetitions 5 to *maxNoOfNon-HS-SCCH-Associated-HS-SICH* are represented by separate ASN.1 structures. + +| Range Bound | Explanation | +|----------------------------------------------|------------------------------------------------------------------------------------------| +| maxNrOfPDSCHSets | Maximum number of PDSCH Sets in a cell. | +| maxNrOfPDSCHs | Maximum number of PDSCH in a cell. | +| maxNrOfPUSCHSets | Maximum number of PUSCH Sets in a cell. | +| maxNrOfPUSCHs | Maximum number of PUSCH in a cell. | +| maxNrOfDLTSs | Maximum number of Downlink time slots in a cell for 3.84Mcps TDD. | +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots in a cell for 1.28Mcps TDD. | +| maxNrOfULTSs | Maximum number of Uplink time slots in a cell for 3.84Mcps TDD. | +| maxNrOfULTSLCRs | Maximum number of Uplink time slots in a cell for 1.28Mcps TDD | +| maxNrOfHSSCCHs | Maximum number of HS-SCCHs in a Cell | +| maxNrOfHSPDSCHs | Maximum number of HS-PDSCHs in one time slot of a Cell for 1.28Mcps TDD and 3.84Mcps TDD | +| maxNrOfHSPDSCHs768 | Maximum number of HS-PDSCHs in one time slot of a Cell for 7.68Mcps TDD | +| maxNrOfEAGCHs | Maximum number of E-AGCHs in a Cell | +| maxNrOfE-PUCHSlots | Maximum number of E-PUCH time slots in a Cell for 3.84Mcps TDD and 7.68Mcps TDD | +| maxNrOfEHICHs | Maximum number of E-HICHs in a Cell | +| maxNrOfE-PUCHSlotsLCR | Maximum number of E-PUCH time slots in a Carrier for 1.28Mcps TDD | +| maxNrOfEPUCHcodes | Maximum number of E-PUCH codes in one time slot for 1.28Mcps TDD | +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | +| MaxNrOfCellPortionsPerCellLCR | Maximum number of Cell Portions in a cell for 1.28 Mcps TDD | +| maxNoOfNon-HS-SCCH-Associated-HS-SICH | Maximum number of Non-HS-SCCH associated HS-SICH in a cell for 1.28 Mcps TDD | + +### 9.1.63 PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| E-HICH Time Offset | O | | 9.2.3.59 | Applicable to 3.84Mcps and 7.68 Mcps TDD only | YES | reject | +| E-HICH Time Offset LCR per UARFCN | | 0.. < maxFrequencyinCell > | | 1.28Mcps TDD only.
See note 1 below | EACH | reject | +| >E-HICH Time Offset LCR | M | | 9.2.3.59a | | – | | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15])..
Mandatory for 1.28Mcps TDD when using multiple frequencies. | – | | +| HS-DSCH Common System Information Response | O | | 9.2.2.77 | FDD only | YES | ignore | +| HS-DSCH Paging System Information Response | O | | 9.2.2.78 | FDD only | YES | ignore | +| Common E-DCH System Information Response | O | | 9.2.2.104 | FDD only | YES | ignore | +| HS-DSCH Common System Information Response LCR | O | | 9.2.3.74 | 1.28Mcps TDD only | YES | ignore | +| HS-DSCH Paging System Information Response LCR | O | | 9.2.3.75 | 1.28Mcps TDD only | YES | ignore | +| Common E-DCH System Information Response LCR | O | | 9.2.3.80 | 1.28Mcps TDD only | YES | ignore | +| Common E-RGCH Info | O | | 9.2.2.189 | FDD only | YES | ignore | +| Note 1 This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxFrequencyinCell are represented by separate ASN.1 structures with different criticalities. | | | | | | | + +| Range Bound | Explanation | +|--------------------|-------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.64 PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CHOICE Cause Level | M | | | | YES | ignore | +| > General | | | | | | | +| >> Cause | M | | 9.2.1.6 | | – | | +| > Set Specific | | | | TDD Only | | | +| >> Unsuccessful DL Shared Channel Set | | 0.. | | | EACH | ignore | +| >>>PDSCH Set ID | M | | 9.2.3.11 | | – | | +| >>> Cause | M | | 9.2.1.6 | | – | | +| >> Unsuccessful UL Shared Channel Set | | 0.. | | | EACH | ignore | +| >>>PUSCH Set ID | M | | 9.2.3.13 | | – | | +| >>> Cause | M | | 9.2.1.6 | | – | | +| > Extension Cause Level | | | | | | | +| >> UARFCN Specific | | 1 | | Applicable to 1.28Mcps TDD only when using multiple frequencies | YES | ignore | +| >>> Unsuccessful UARFCN | | 0.. | | | EACH | ignore | +| >>>>UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Used to indicate the carrier on which HSDPA or E-DCH related resources configuration failure occurs. | – | | +| >>>> Cause | M | | 9.2.1.6 | | – | | +| >>>>HS-Cause | O | | Cause 9.2.1.6 | Used to indicate the cause of HSDPA configuration failure. | YES | ignore | +| >>>>E-Cause | O | | Cause 9.2.1.6 | Used to indicate the cause of E-DCH related configuration failure. | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | +| E-HIGH Time Offset LCR per UARFCN | | 0.. | | 1.28Mcps TDD only | EACH | ignore | +| >E-HIGH Time Offset LCR | M | | 9.2.3.59a | | | | + +| | | | | | | | +|-------------------------------------------------|---|------|----------|------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Used to indicate the carrier on which HSDPA or E-DCH related resources configuration failure occurs. | | | +| Common System Information Response LCR | | 0..1 | | | YES | ignore | +| >HS-DSCH Common System Information Response LCR | M | | 9.2.3.74 | 1.28Mcps TDD only | | | +| >HS-DSCH Paging System Information Response LCR | O | | 9.2.3.75 | 1.28Mcps TDD only | | | +| >Common E-DCH System Information Response LCR | M | | 9.2.3.80 | 1.28Mcps TDD only | | | + +| Range Bound | Explanation | +|---------------------------|-------------------------------------------------------------| +| maxNrOfPDSCHSets | Maximum number of PDSCH Sets in a cell | +| maxNrOfPDSCHSets | Maximum number of PUSCH Sets in a cell | +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +### 9.1.65 RESET REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | + +| | | | | | | | +|--------------------------------------------------|---|------------------------------|----------|----------------------------------------------------|------|--------| +| CHOICE Reset Indicator | M | | | | YES | ignore | +| > Communication Context | | | | | | | +| >> Communication Context Information | | 1.. | | | EACH | reject | +| >>>CHOICE Communication Context Type | M | | | | – | | +| >>>> CRNC Communication Context | | | | | | | +| >>>>> CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | – | | +| >>>> Node B Communication Context | | | | | | | +| >>>>> Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | – | | +| > Communication Control Port | | | | | | | +| >> Communication Control Port Information | | 1.. | | | EACH | reject | +| >>> Communication Control Port ID | M | | 9.2.1.15 | | – | | +| > Node B | | | NULL | | | | + +| Range Bound | Explanation | +|--------------------------------|----------------------------------------------------------------------------| +| maxCommunicationContext | Maximum number of Communication Contexts that can exist in the Node B | +| maxCCPinNodeB | Maximum number of Communication Control Ports that can exist in the Node B | + +### 9.1.66 RESET RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.67 DL POWER TIMESLOT CONTROL REQUEST [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All NBCC" shall not be used. | YES | ignore | +| DL Time Slot ISCP Info | O | | 9.2.3.4F | Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD. | YES | ignore | +| DL Time Slot ISCP Info LCR | O | | 9.2.3.4P | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD and 7.68Mcps TDD. | YES | ignore | +| Primary CCPCH RSCP | O | | 9.2.3.11A | | YES | ignore | +| Primary CCPCH RSCP Delta | O | | 9.2.3.11B | | YES | ignore | + +### 9.1.68 RADIO LINK PREEMPTION REQUIRED INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | | YES | ignore | +| RL Information | | 0..<maxNrOfRLs> | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | + +| Range Bound | Explanation | +|-------------------|------------------------------------------| +| maxNrOfRLs | Maximum number of radio links for one UE | + +### 9.1.69 INFORMATION EXCHANGE INITIATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | reject | +| CHOICE Information Exchange Object Type | M | | | | YES | reject | +| >Cell/ | | | | | | | +| >>C-ID | M | | 9.2.1.9 | | – | | +| Information Type | M | | 9.2.1.36D | | YES | reject | +| Information Report Characteristics | M | | 9.2.1.36B | | YES | reject | + +### 9.1.70 INFORMATION EXCHANGE INITIATION RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | ignore | +| CHOICE Information Exchange Object Type | O | | | | YES | ignore | +| >Cell | | | | | | | +| >>Requested Data Value | M | | 9.2.1.51A | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.71 INFORMATION EXCHANGE INITIATION FAILURE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.72 INFORMATION REPORT + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | ignore | +| CHOICE Information Exchange Object Type | M | | | | YES | ignore | +| >Cell | | | | | | | +| >>Requested Data Value Information | M | | 9.2.1.51B | | – | | + +### 9.1.73 INFORMATION EXCHANGE TERMINATION REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | ignore | + +### 9.1.74 INFORMATION EXCHANGE FAILURE INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Information Exchange ID | M | | 9.2.1.36C | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | + +### 9.1.75 CELL SYNCHRONISATION INITIATION REQUEST [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Cell Sync Burst Repetition Period | M | | 9.2.3.4J | | YES | reject | +| Time Slot Information | | 0..15 | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD. | GLOBAL | reject | +| >Time Slot | M | | 9.2.3.23 | | – | | +| Cell Sync Burst Transmission Initiation Information | | 0..1 | | Applicable to 3.84Mcps TDD only | GLOBAL | reject | +| >CSB Transmission ID | M | | 9.2.3.4N | | – | | +| >SFN | M | | 9.2.1.53A | | – | | +| >Cell Sync Burst Code | M | | 9.2.3.4G | | – | | +| >Cell Sync Burst Code Shift | M | | 9.2.3.4H | | – | | +| >Initial DL Transmission Power | M | | DL Power 9.2.1.21 | | – | | +| Cell Sync Burst Measurement Initiation Information | | 0..1 | | Applicable to 3.84Mcps TDD only | GLOBAL | reject | +| >CSB Measurement ID | M | | 9.2.3.4I | | – | | +| >Cell Sync Burst Code | M | | 9.2.3.4G | | – | | +| >Cell Sync Burst Code Shift | M | | 9.2.3.4H | | – | | +| >Synchronisation Report Type | M | | 9.2.3.18E | | – | | +| >SFN | O | | 9.2.1.53A | | – | | +| >Synchronisation Report Characteristics | M | | 9.2.3.18D | | – | | +| SYNC_DL Code Transmission Initiation Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | GLOBAL | reject | +| >CSB Transmission ID | M | | 9.2.3.4N | | – | | +| >SFN | M | | 9.2.1.53A | | – | | +| >UARFCN | M | | 9.2.1.65 | | – | | +| >SYNC_DL Code ID | M | | 9.2.3.18B | | – | | +| >DwPCH Power | M | | 9.2.3.5B | | – | | +| SYNC_DL Code Measurement Initiation Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | GLOBAL | reject | +| >CSB Measurement ID | M | | 9.2.3.4I | | – | | +| >SFN | O | | 9.2.1.53A | | – | | + +| | | | | | | | +|-----------------------------------------|---|--|-----------|--|---|--| +| >UARFCN | M | | 9.2.1.65 | | – | | +| >SYNC_DL Code ID | M | | 9.2.3.18B | | – | | +| >Synchronisation Report Type | M | | 9.2.3.18E | | – | | +| >Synchronisation Report Characteristics | M | | 9.2.3.18D | | – | | + +### 9.1.76 CELL SYNCHRONISATION INITIATION RESPONSE [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.77 CELL SYNCHRONISATION INITIATION FAILURE [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.78 CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------------|----------|-----------------------------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | reject | +| Time Slot | M | | 9.2.3.23 | Applicable to 3.84Mcps TDD only.
For 1.28Mcps TDD, the CRNC should set this to 0 and the Node B shall ignore it | YES | reject | +| Number Of Cycles Per SFN Period | M | | 9.2.3.7B | | YES | reject | +| Number Of Repetitions Per Cycle Period | M | | 9.2.3.7C | | YES | reject | +| Cell Sync Burst Transmission Reconfiguration Information | | 0..<maxNrOfCellSyncBursts> | | Applicable to 3.84Mcps TDD only | GLOBAL | reject | +| >CSB Transmission ID | M | | 9.2.3.4N | | – | | +| >Sync Frame Number To Transmit | M | | Sync Frame Number 9.2.3.18C | | – | | +| >Cell Sync Burst Code | O | | 9.2.3.4G | | – | | +| >Cell Sync Burst Code Shift | O | | 9.2.3.4H | | – | | +| >DL Transmission Power | O | | DL Power 9.2.1.21 | | – | | +| Cell Sync Burst Measurement Reconfiguration Information | | 0..1 | | Applicable to 3.84Mcps TDD only | YES | reject | +| >Cell Sync Burst Measurement Information | | 1..<maxNrOfCellSyncBursts> | | | GLOBAL | reject | +| >>Sync Frame Number To Receive | M | | Sync Frame Number 9.2.3.18C | | – | | +| >>Cell Sync Burst Information | | 1..<maxNrOfReceiptsPerSyncFrame> | | | – | | +| >>>CSB Measurement ID | M | | 9.2.3.4I | | – | | +| >>>Cell Sync Burst Code | M | | 9.2.3.4G | | – | | +| >>>Cell Sync Burst Code Shift | M | | 9.2.3.4H | | – | | +| >Synchronisation Report Type | O | | 9.2.3.18E | | YES | reject | +| >Synchronisation Report Characteristics | O | | 9.2.3.18D | | YES | reject | +| Number Of Subcycles Per Cycle Period | O | | 9.2.3.7D | Applicable to 1.28Mcps TDD only | YES | reject | +| SYNC_DL Code Transmission | | 0..<maxNrOfSyncFra | | Applicable to 1.28Mcps TDD | GLOBAL | reject | + +| | | | | | | | +|-----------------------------------------------------------------|---|----------------------------------------------------|---------------------------------------|---------------------------------|-----|--------| +| Reconfiguration Information LCR | | mesLCR> | | only | | | +| >CSB Transmission ID | M | | 9.2.3.4N | | – | | +| >Sync Frame Number For Transmission | M | | Sync Frame Number 9.2.3.18C | | – | | +| >UARFCN | M | | 9.2.1.65 | | – | | +| >SYNC_DL Code ID | O | | 9.2.3.18B | | – | | +| >DwPCH Power | O | | 9.2.3.5B | | – | | +| SYNC_DL Code Measurement Reconfiguration Information LCR | | 0..1 | | Applicable to 1.28Mcps TDD only | YES | reject | +| >SYNC_DL Code Measurement Information LCR | | 1..<maxNrOfSyncDL CodesLCR> | | | – | | +| >>Sync Frame Number To Receive | M | | Sync Frame Number 9.2.3.18C | | – | | +| >>Sync_DL Code Information LCR | | 1..<maxNrOfReceptionsperSyncFrameLCR> | | | – | | +| >>>CSB Measurement ID | M | | 9.2.3.4I | | – | | +| >>>SYNC_DL Code ID | M | | 9.2.3.18B | | – | | +| >>>UARFCN | M | | 9.2.1.65 | | – | | +| >>>Propagation Delay Compensation | O | | Timing Adjustment Value LCR 9.2.3.22b | | – | | +| >Synchronisation Report Type | O | | 9.2.3.18E | | YES | reject | +| >Synchronisation Report Characteristics | O | | 9.2.3.18D | | YES | reject | + +| Range Bound | Explanation | +|-----------------------------------------|-----------------------------------------------------------------------------------------| +| maxNrOfCellSyncBursts | Maximum number of cell synchronisation bursts per cycle for 3.84Mcps TDD | +| maxNrOfReceiptsPerSyncFrame | Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD | +| maxNrOfSyncFramesLCR | Maximum number of Sync Frames per subcycle for 1.28Mcps TDD | +| maxNrOfReceptionsperSyncFrameLCR | Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD | +| maxNrOfSyncDLCodesLCR | Maximum number of SYNC_DL Codes for 1.28Mcps TDD | + +### 9.1.79 CELL SYNCHRONISATION RECONFIGURATION RESPONSE [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.80 CELL SYNCHRONISATION RECONFIGURATION FAILURE [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cause | M | | 9.2.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.81 CELL SYNCHRONISATION REPORT [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|----------------------------------|-----------------------------------|-------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cell Synchronisation Information | | 1.. | | | GLOBAL | ignore | +| >C-ID | M | | 9.2.1.9 | | YES | ignore | +| >CHOICE Synchronisation Report Type | O | | | | YES | ignore | +| >>Initial Phase or Steady-State Phase | | | | | | | +| >>>Cell Sync Burst Measured Information | | 0.. | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD. | – | | +| >>>>SFN | M | | 9.2.1.53A | | – | | +| >>>>Cell Sync Burst Information | | 1.. | | | – | | +| >>>>>CHOICE Cell Sync Burst Availability Indicator | M | | | | – | | +| >>>>>>Cell Sync Burst Available | | | | | | | +| >>>>>>>Cell Sync Burst Timing | M | | 9.2.3.4L | | – | | +| >>>>>>>Cell Sync Burst SIR | M | | 9.2.3.4K | | – | | +| >>>>>>>Cell Sync Burst Not Available | | | NULL | | | | +| >>>Accumulated Clock Update | O | | Timing Adjustment Value 9.2.3.22a | | YES | ignore | +| >>>SYNC_DL Codes Measured Information | | 0.. | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD. | YES | ignore | +| >>>>SFN | M | | 9.2.1.53A | | – | | +| >>>>SYNC_DL Code Information | | 1..cFrameLCR> | | | | | +| >>>>>CHOICE
SYNC_DL Code
Availability Indicator | M | | | | – | | +| >>>>>>SYNC_DL
Code Available | | | | | | | +| >>>>>>>SYNC_
DL Code ID
Timing | M | | Cell Sync
Burst
Timing LCR
9.2.3.4La | | – | | +| >>>>>>>SYNC_
DL Code ID SIR | M | | Cell Sync
Burst SIR
9.2.3.4K | | – | | +| >>>>>>SYNC_DL
Code Not
Available | | | NULL | | | | +| >>Late-Entrant Cell | | | NULL | | | | +| >>Frequency Acquisition | | | NULL | | | | + +| Range Bound | Explanation | +|-----------------------------------------|-----------------------------------------------------------------------------------------| +| maxCellInNodeB | Maximum number of Cells in a Node B | +| maxNrOfCellSyncBursts | Maximum number of cell synchronisation bursts per cycle for 3.84Mcps TDD | +| maxNrOfReceiptsPerSyncFrame | Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD | +| maxNrOfSyncFramesLCR | Maximum number of SYNC Frames per measurement reporting period for 1.28Mcps TDD | +| maxNrOfReceptionsperSyncFrameLCR | Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD | + +### 9.1.82 CELL SYNCHRONISATION TERMINATION REQUEST [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | ignore | +| CSB Transmission ID | O | | 9.2.3.4N | | YES | ignore | +| CSB Measurement ID | O | | 9.2.3.4I | | YES | ignore | + +### 9.1.83 CELL SYNCHRONISATION FAILURE INDICATION [TDD] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | ignore | +| CSB Transmission ID | O | | 9.2.3.4N | | YES | ignore | +| CSB Measurement ID | O | | 9.2.3.4I | | YES | ignore | +| Cause | M | | 9.2.1.6 | | YES | ignore | + +### 9.1.84 CELL SYNCHRONISATION ADJUSTMENT REQUEST [TDD] + +| IE/Group Name | Presence | Range | IE Type | Semantics | Criticality | Assigned | +|---------------|----------|-------|---------|-----------|-------------|----------| +|---------------|----------|-------|---------|-----------|-------------|----------| + +| | | | and
Reference | Description | | Criticality | +|----------------------------------------|---|---------------------|-------------------|---------------------------------|------|-------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cell Adjustment
Information | | 1.. | | | EACH | ignore | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Frame Adjustment Value | O | | 9.2.3.5C | | – | | +| >Timing Adjustment Value | O | | 9.2.3.22a | Applicable to 3.84Mcps TDD only | – | | +| >DL Transmission Power | O | | DL Power 9.2.1.21 | Applicable to 3.84Mcps TDD only | – | | +| >SFN | O | | 9.2.1.53A | | – | | +| >DwPCH Power | O | | 9.2.3.5B | Applicable to 1.28Mcps TDD only | YES | ignore | +| >Timing Adjustment Value LCR | O | | 9.2.3.22b | Applicable to 1.28Mcps TDD only | YES | ignore | + +| Range Bound | Explanation | +|----------------|-------------------------------------| +| maxCellinNodeB | Maximum number of Cells in a Node B | + +### 9.1.85 CELL SYNCHRONISATION ADJUSTMENT RESPONSE [TDD] + +| IE/Group Name | Presence | Range | IE Type
and
Reference | Semantics
Description | Criticality | Assigned
Criticality | +|-------------------------|----------|-------|-----------------------------|--------------------------|-------------|-------------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +### 9.1.86 CELL SYNCHRONISATION ADJUSTMENT FAILURE [TDD] + +| IE/Group Name | Presence | Range | IE Type
and
Reference | Semantics
Description | Criticality | Assigned
Criticality | +|---------------------------------------------|----------|---------------------|-----------------------------|--------------------------|-------------|-------------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CHOICE Cause Level | M | | | | YES | ignore | +| >General | | | | | | | +| >>Cause | M | | 9.2.1.6 | | – | | +| >Cell Specific | | | | | | | +| >>Unsuccessful Cell
Information Response | | 1.. | | | EACH | ignore | +| >>>C-ID | M | | 9.2.1.9 | | – | | +| >>>Cause | M | | 9.2.1.6 | | – | | +| Criticality Diagnostics | O | | 9.2.1.17 | | YES | ignore | + +| Range Bound | Explanation | +|----------------|-------------------------------------| +| maxCellinNodeB | Maximum number of Cells in a Node B | + +### 9.1.87 BEARER REARRANGEMENT INDICATION + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------------------|----------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Signalling Bearer Request Indicator | O | | 9.2.1.55A | | YES | ignore | +| DCHs To Re-arrange | | 0..<maxNrOfDCHs> | | | GLOBAL | ignore | +| >DCH ID | M | | 9.2.1.20 | | – | | +| DSCHs To Re-arrange | | 0..<maxNrOfDSCHs> | | TDD only | GLOBAL | ignore | +| >DSCH ID | M | | 9.2.3.5a | | – | | +| USCHs To Re-arrange | | 0..<maxNrOfUSCHs> | | TDD only | GLOBAL | ignore | +| >USCH ID | M | | 9.2.3.27 | | – | | +| HS-DSCHs MAC-d Flow To Re-arrange | | 0..<maxNrOfMACdFlows> | | | GLOBAL | ignore | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31i | | – | | +| E-DCHs MAC-d Flow To Re-arrange | | 0..<maxNrOfEDCHMACdFlows> | | | GLOBAL | ignore | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.29ad | | – | | +| >Additional E-DCH Cell Information Bearer Rearrangement | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | EACH | ignore | +| >>Transport Bearer Rearrangement Indicator for Secondary E-DCH Separate Mode | M | | Enumerated ENUMERATED (bearer for primary carrier, bearer for secondary carrier, bearers for both primary and secondary carriers,...) | | – | | + +| Range bound | Explanation | +|-----------------------------|--------------------------------------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for a UE | +| maxNrOfDSCHs | Maximum number of DSCHs for a UE | +| maxNrOfUSCHs | Maximum number of USCHs for a UE | +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +### 9.1.88 RADIO LINK ACTIVATION COMMAND + +#### 9.1.88.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-----------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | | YES | ignore | +| Delayed Activation Information | | 1.. | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >Delayed Activation Update | M | | 9.2.1.24D | | – | | + +| Range Bound | Explanation | +|-------------|----------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | + +#### 9.1.88.2 TDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-----------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | | YES | ignore | +| Delayed Activation Information | | 1.. | | | EACH | ignore | +| >RL ID | M | | 9.2.1.53 | | – | | +| >Delayed Activation Update | M | | 9.2.1.24D | | – | | + +| Range Bound | Explanation | +|-------------|----------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | + +### 9.1.89 RADIO LINK PARAMETER UPDATE INDICATION + +#### 9.1.89.1 FDD Message + +| IE/Group name | Presence | Range | IE Type and Reference | Semantic Description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|-----------------------------------|----------------------------|-------------------------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| HS-DSCH FDD Update Information | O | | 9.2.2.18Ea | | YES | ignore | +| E-DCH FDD Update Information | O | | 9.2.2.13DA | | YES | ignore | +| Additional HS Cell Information RL Param Upd | | 0..<maxNrOfHSDSCH-1> | | For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. | EACH | ignore | +| >HS-PDSCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| >HS-DSCH FDD Secondary Serving Update Information | M | | 9.2.2.18Eaa | | – | | +| Additional E-DCH Cell Information RL Param Upd | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | EACH | ignore | +| >>Additional E-DCH FDD Update Information | M | | 9.2.2.138 | | – | | +| CPC Recovery Report | O | | ENUMERATED(Initiated, ...) | | YES | ignore | +| UL CLTD State Update Information | O | | 9.2.2.155 | | YES | ignore | +| UE Measurement Forwarding | O | | 9.2.2.207 | | YES | ignore | +| CFN | O | | 9.2.1.7 | | YES | ignore | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------| +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +#### 9.1.89.2 TDD Message + +| IE/Group name | Presence | Range | IE Type and Reference | Semantic Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| HS-DSCH TDD Update Information | O | | 9.2.3.5GA | | YES | ignore | + +### 9.1.90 MBMS NOTIFICATION UPDATE COMMAND + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------|----------|-----------------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| C-ID | M | | 9.2.1.9 | | YES | ignore | +| Common Physical Channel ID | M | | 9.2.1.13 | | YES | ignore | +| Modification Period | O | | 9.2.1.47a | This IE shall be present in the very first message | YES | ignore | +| MICH CFN | M | | 9.2.1.46a | | YES | ignore | +| NI Information | | 1.. | | | GLOBAL | ignore | +| >NI | M | | 9.2.1.47F | | – | | + +| Range Bound | Explanation | +|-------------------|-----------------------| +| maxNrOfNIs | Maximum number of NIs | + +### 9.1.91 UE STATUS UPDATE COMMAND + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cell E-RNTI Status Information | | 1.. | | | EACH | ignore | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Vacant E-RNTI | | 1.. | | | EACH | ignore | +| >>E-RNTI | M | | 9.2.1.75 | | | | + +| Range Bound | Explanation | +|--------------------------|----------------------------------------------| +| maxCellInNodeB | Maximum number of Cells in a Node B | +| maxErntiToRelease | Maximum number of E-RNTI to release per cell | + +### 9.1.92 SECONDARY UL FREQUENCY REPORT + +#### 9.1.92.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Node B Communication Context ID | M | | 9.2.1.48 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Activation Information | M | | 9.2.2.128 | | YES | ignore | + +### 9.1.93 SECONDARY UL FREQUENCY UPDATE INDICATION + +#### 9.1.93.1 FDD Message + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|----------------------------------------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | ignore | +| Transaction ID | M | | 9.2.1.62 | | – | | +| CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | YES | ignore | +| Activation Information | M | | 9.2.2.128 | | YES | ignore | + +### 9.1.94 UE STATUS UPDATE CONFIRM REQUEST + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| Cell E-RNTI Status Information | | 1.. | | | EACH | ignore | +| >C-ID | M | | 9.2.1.9 | | – | | +| >Vacant E-RNTI | | 1.. | | | EACH | ignore | +| >>E-RNTI | M | | 9.2.1.75 | | - | - | + +| Range Bound | Explanation | +|-------------------|----------------------------------------------| +| maxCellinNodeB | Maximum number of Cells in a Node B | +| maxErntiToRelease | Maximum number of E-RNTI to release per cell | + +### 9.1.95 UE STATUS UPDATE CONFIRM RESPONSE + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Discriminator | M | | 9.2.1.45 | | – | | +| Message Type | M | | 9.2.1.46 | | YES | reject | +| Transaction ID | M | | 9.2.1.62 | | – | | +| E-RNTI Release Status | M | | 9.2.1.126 | | YES | ignore | + +## 9.2 Information Element Functional Definition and Contents + +### 9.2.0 General + +Subclause 9.2 presents the NBAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in Subclause 9.3. In case there is a contradiction between the tabular format in Subclause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); +- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information; + +### 9.2.1 Common parameters + +#### 9.2.1.1 Add/Delete Indicator + +The add/delete indicator shall notify the CRNC whether the associated resource has been added to or removed from the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|--------------------------|-----------------------| +| Add/Delete Indicator | | | ENUMERATED (Add, Delete) | | + +#### 9.2.1.1A Allocation/Retention Priority + +This parameter indicates the priority level in the allocation and retention of Node B internal resources. See Annex A. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (0..15) | This IE indicates the priority of the request.
Usage:
Value "0" means "Spare"; It shall be treated as a logical error if received.
Values between "1" and "14" are ordered in decreasing order of priority, "1" being the highest and "14" the lowest.
Value "15" means "No Priority". | +| Pre-emption Capability | M | | ENUMERATED ( shall not trigger pre-emption, may trigger pre-emption) | | +| Pre-emption Vulnerability | M | | ENUMERATED ( not pre-emptable, pre-emptable) | | + +#### 9.2.1.1B Alternative Format Reporting Indicator + +This IE indicates if Node B may report a measurement using an alternative format. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-------------------------------------------------|-----------------------| +| Alternative Format Reporting Indicator | | | ENUMERATED (Alternative format is allowed, ...) | | + +#### 9.2.1.2 Availability Status + +The availability status is used to indicate more detailed information of the availability of the resource. In accordance with ref. CCITT Rec. X.731 [3], following values are defined. If the value of this IE is "empty", this implies that none of the status conditions described in ref. CCITT Rec. X.731 [3] are present. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Availability Status | | | ENUMERATED ( empty, in test, failed, power off, off line, off duty, dependency, degraded, not installed, log full, ...) | | + +#### 9.2.1.3 BCCH Modification Time + +Indicates the time after which the new system information shall be applied on BCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------| +| BCCH Modification Time | | | INTEGER (0..511) | All SFN values in which MIB may be mapped are allowed. The tabular description is presented in TS 25.331 [18]. | + +#### 9.2.1.4 Binding ID + +The Binding ID is the identifier of a user data stream. + +In case of transport bearer establishment with ALCAP (TS 25.426 [2], TS 25.434 [31]), this IE contains the identifier that is allocated at the Node B and that is unique for each transport bearer under establishment to/from the Node B. + +If the Transport Layer Address contains an IP address (IETF RFC 2460 [29]), this IE contains the UDP port (IETF RFC 768 [30]) intended to be used for the user plane transport. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Binding ID | | | OCTET STRING (1..4,...) | If the Binding ID includes an UDP port, the UDP port is included in octets 1 and 2. The first octet of the UDP port field shall be included in the first octet of the Binding ID. | + +##### 9.2.1.4A BLER + +Void. + +#### 9.2.1.5 Blocking Priority Indicator + +The Blocking priority indicator shall indicate the immediacy with which a resource should be blocked from use. The following priority classes shall be supported in the Blocking priority indicator. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Blocking Priority Indicator | | | ENUMERATED ( High, Normal, Low, ...) | "High" priority: Block resource immediately.
"Normal" priority: Block resource when idle or upon timer expiry.
"Low" priority: Block resource when idle. | + +#### 9.2.1.5A Burst Mode Parameters + +The *Burst Mode Parameters* IE provides information to be applied for IPDL burst mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|---------------------------------------| +| Burst Start | M | | INTEGER (0..15) | See TS 25.214 [10] and TS 25.224 [21] | +| Burst Length | M | | INTEGER (10..25) | See TS 25.214 [10] and TS 25.224 [21] | +| Burst Freq | M | | INTEGER (1..16) | See TS 25.214 [10] and TS 25.224 [21] | + +#### 9.2.1.5B Broadcast Common Transport Bearer Indication + +The *Broadcast Common Transport Bearer Indication* IE is used by the Node B to inform the CRNC that the transport bearer of the existing Common Transport Channel which is indicated by the *Common Transport Channel ID* IE and *C-ID* IE, shall be used instead of establishing a new transport bearer. If there are more than one Common Transport Channels sharing the same transport bearer, Node B may include any one of these Common Transport Channels together with its corresponding C-ID in *Broadcast Common Transport Bearer Indication* IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Common Transport Channel ID | M | | 9.2.1.14 | | +| C-ID | M | | 9.2.1.9 | | + +#### 9.2.1.5C Broadcast Reference + +The *Broadcast Reference* IE is a unique identifier within the CRNC identifying the intended usage of a requested Common Transport Channel (e.g. the *Broadcast Reference* IE may identify a particular MBMS session). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| Broadcast Reference | | | BIT STRING (SIZE(24)) | | + +#### 9.2.1.6 Cause + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | M | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer
Cause | M | | ENUMERATED (
unknown C-ID,
Cell not available,
Power level not supported,
DL radio resources not available,
UL radio resources not available,
RL Already Activated/allocated,
Node B Resources Unavailable,
Measurement not supported for
the object,
Combining Resources not
available,
Requested configuration not
supported,
Synchronization failure,
Priority transport channel
established,
SIB Origination in Node B not
Supported,
Requested Tx Diversity Mode not
supported,
Unspecified,
BCCH scheduling error,
Measurement Temporarily not
Available,
Invalid CM Setting,
Reconfiguration CFN not elapsed,
Number of DL codes not
supported,
S-CPICH not supported,
Combining not supported,
UL SF not supported,
DL SF not supported,
Common Transport Channel Type
not supported,
Dedicated Transport Channel
Type not supported,
Downlink Shared Channel Type
not supported,
Uplink Shared Channel Type not
supported,
CM not supported,
Tx diversity no longer supported,
Unknown Local Cell ID,
...,
Number of UL codes not
supported,
Information temporarily not
available,
Information Provision not
supported for the object,
Cell Synchronisation not
supported,
Cell Synchronisation Adjustment
not supported,
DPC Mode Change not Supported,
IPDL already activated,
IPDL not supported,
IPDL parameters not available,
Frequency Acquisition not
supported,
Power Balancing status not
compatible,
Requested type of Bearer Re- | | + +| | | | | | +|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | |

arrangement not supported,
Signalling Bearer Re-arrangement not supported,
Bearer Re-arrangement needed,
Delayed Activation not Supported,
RL Timing Adjustment not supported,
MICH not supported,
F-DPCH Not Supported,
Modification Period not available,
PLCCH not supported,
Continuous Packet Connectivity DTX-DRX operation not available,
Continuous Packet Connectivity UE DTX Cycle not available,
MIMO not available,
E-DCH MAC-d PDU Size Format not available,
Multi Cell operation not available,
Semi-Persistent scheduling not supported,
Continuous Packet Connectivity DRX not supported,
Continuous Packet Connectivity DRX not available,
SixtyfourQAM DL and MIMO Combined not available,
S-CPICH power offset support not available,
TX diversity for MIMO UE on DL Control Channels not available,
Single Stream MIMO not available,
Multi Cell operation with MIMO not available,
Multi Cell operation with Single Stream MIMO not available,
Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available,
Multi Cell E-DCH operation not available,
Frequency Specific Compressed Mode not available,
UL CLTD operation not available,
MIMO with four transmit antennas not available,
Dual Stream MIMO with four transmit antennas not available,
Multiflow operation not available,
SixtyfourQAM operation not available,
UL MIMO operation not available,
UL MIMO and SixteenQAM operation not available,
UL MIMO and SixtyfourQAM operation not available,
NodeB Triggered HS-DPCCH Transmission operation not available,
2ms and 10ms TTI Concurrent Deployment operation not available,
Further Enhanced UE DRX operation not available,
Per HARQ Activation and Deactivation operation not available,
TTI alignment operation not

| | +|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | +|-------------------------|---|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | available,
Common E-RGCH operation not available,
E-DCH decoupling operation not available,
Basic DCH Enhancements operation not available,
Full DCH Enhancements operation not available,
BCH mapped on SCCPCH scheduling error,
Radio Links without DPCH/F-DPCH operation not available,
UL DPCCH2 operation not available,
Downlink TPC enhancements operation not available,
Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available,
Dual Cell E-DCH operation enhancements with different TTI operation not available) | | +| >Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED (
Transport resource unavailable,
Unspecified,
...) | | +| >Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED (
Transfer syntax error,
Abstract syntax error (reject),
Abstract syntax error (ignore and notify),
Message not compatible with receiver state,
Semantic error,
Unspecified,
Abstract syntax error (falsely constructed message),
...) | | +| >Misc | | | | | +| >>Miscellaneous Cause | M | | ENUMERATED (
Control processing overload
Hardware failure,
O&M intervention,
Not enough user plane processing resources,
Unspecified,
...) | | + +The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that the concerned capability is present, but insufficient resources were available to perform the requested action. + +| Radio Network Layer cause | Meaning | +|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| BCCH scheduling error | The Node B has detected an illegal BCCH schedule update (see subclause 8.2.16.3). | +| BCH mapped on SCCPCH scheduling error | The Node B has detected an illegal BCH mapped on SCCPCH schedule update (see subclause 8.2.16.3). | +| Bearer Re-arrangement needed | The Node B cannot perform the requested Radio Link Reconfiguration without bearer re-arrangement. | +| Cell not Available | The concerned cell or local cell is not available. | +| Cell Synchronisation not supported | The concerned cell(s) do not support Cell Synchronisation. | +| Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available | Cell specific tx diversity handling for multi cell operation not available in the concerned cell(s) | +| Combining not supported | The Node B does not support RL combining for the concerned cells. | +| Combining Resources Not Available | The value of the received Diversity Control Field IE was set to "Must", but the Node B cannot perform the requested combining. | +| CM not supported | The concerned cell(s) do not support Compressed Mode. | +| Common Transport Channel Type not supported | The concerned cell(s) do not support the RACH and/or FACH Common Transport Channel Type. | +| Continuous Packet Connectivity DTX-DRX operation not available | CPC resources for DTX-DRX operation not available in the concerned cell(s). | +| Continuous Packet Connectivity UE DTX Cycle not available | CPC resources for the UE DTX Cycle not available in the concerned cell(s). | +| Dedicated Transport Channel Type not supported | The concerned cell(s) do not support the Dedicated Transport Channel Type. | +| Delayed Activation not Supported | The concerned cell(s) do not support delayed activation of RLs. | +| DL Radio Resources not Available | The Node B does not have sufficient DL radio resources available. | +| DL SF not supported | The concerned cell(s) do not support the requested DL SF. | +| DL Shared Channel Type not supported | The concerned cell(s) do not support the Downlink Shared Channel Type. | +| DPC Mode Change not Supported | The concerned cells do not support DPC mode changes. | +| E-DCH MAC-d PDU Size Format not available | The selected E-DCH MAC-d PDU Size Format is not available in the concerned cell(s). | +| Frequency Acquisition not supported | The concerned cell(s) do not support Frequency Acquisition. | +| F-DPCH not supported | The concerned cell(s) do not support the Fractional DPCH | +| Information Provision not supported for the object | The requested information provision is not supported for the concerned object types. | +| Information temporarily not available | The requested information can temporarily not be provided. | +| Invalid CM Settings | The concerned cell(s) consider the requested Compressed Mode settings invalid. | +| IPDL already activated | The concerned cell(s) have already active IPDL ongoing. | +| IPDL not supported | The concerned cell(s) do not support the IPDL. | +| IPDL parameters not available | The concerned cell(s) do not have IPDL parameters defining IPDL to be applied. | +| Measurement not Supported For The Object | At least one of the concerned cell(s) does not support the requested measurement on the concerned object type. | +| Measurement Temporarily not Available | The Node B can temporarily not provide the requested measurement value. | +| MICH not supported | The concerned cell does not support MICH. | +| MIMO not available | MIMO resources not available in the concerned cell(s). | +| Modification Period not available | The Node B does not have modification period available. | +| Multi Cell operation not available | Multi Cell operation resources not available in the concerned cell(s) | +| Multi Cell operation with MIMO not available | Multi Cell operation resources with MIMO not available in the concerned cell(s) | +| Multi Cell operation with Single Stream MIMO not available | Multi Cell operation resources with Single Stream MIMO not available in the concerned cell(s) | +| Multi Cell E-DCH operation not available | Multi Cell E-DCH operation resources not available in the concerned cell(s) | +| Node B resources unavailable | The Node B does not have sufficient resources available. | +| Number of DL codes not supported | The concerned cell(s) do not support the requested number of DL codes. | +| Number of UL codes not supported | The concerned cell(s) do not support the requested number of UL codes. | +| Power Level not Supported | A DL power level was requested which the concerned cell(s) do not support. | +| Power Balancing status not compatible | The power balancing status in the SRNC is not compatible with that of the Node B. | +| PLCCH not supported | The concerned cell does not support PLCCH. | +| Priority transport channel established | The CRNC cannot perform the requested blocking since a transport channel with a high priority is present. | + +| | | +|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RL Timing Adjustment not Supported | The concerned cell(s) do not support adjustments of the RL timing. | +| Reconfiguration CFN not elapsed | The requested action cannot be performed due to that a RADIO LINK RECONFIGURATION COMMIT message was received previously, but the concerned CFN has not yet elapsed. | +| Requested Configuration not Supported | The concerned cell(s) do not support the requested configuration i.e. power levels, Transport Formats, physical channel parameters. | +| Requested Type of Bearer Re-arrangement not supported | The Node B does not support the requested type of bearer re-arrangement. | +| Requested Tx Diversity mode not supported | The concerned cell(s) do not support the requested transmit diversity mode. | +| RL already Activated/ allocated | The Node B has already allocated an RL with the requested RL-id for this UE context. | +| S-CPICH not supported | The concerned cell(s) do not support S-CPICH. | +| S-CPICH power offset support not available | The support for setting up the desired power offset on S-CPICH with respect to P-CPICH is not available | +| SIB Origination in Node B not Supported | The Node B does not support the origination of the requested SIB for the concerned cell. | +| Signalling Bearer Re-arrangement not supported | The Node B does not support the Signalling bearer re-arrangement. | +| Single Stream MIMO not available | Single Stream MIMO resources not available in the concerned cell(s). | +| SixtyfourQAM DL and MIMO Combined not available | SixtyfourQAM DL and MIMO Combined not available in the concerned cell(s). | +| Synchronisation Failure | Loss of UL Uu synchronisation. | +| Cell Synchronisation Adjustment not supported | The concerned cell(s) do not support Cell Synchronisation Adjustment. | +| TX diversity for MIMO UE on DL Control Channels not available | The Node B does not have sufficient radio resources available to support transmit diversity on downlink control channels when the UE is configured in MIMO mode with P-CPICH & S-CPICH as phase references (TS 25.211 [7]) | +| Tx diversity no longer supported | Tx diversity can no longer be supported in the concerned cell. | +| UL Radio Resources not Available | The Node B does not have sufficient UL radio resources available. | +| UL SF not supported | The concerned cell(s) do not support the requested minimum UL SF. | +| UL Shared Channel Type not supported | The concerned cell(s) do not support the Uplink Shared Channel Type. | +| Unknown C-ID | The Node B is not aware of a cell with the provided C-ID. | +| Unknown Local Cell ID | The Node B is not aware of a local cell with the provided Local Cell ID | +| Unspecified | Sent when none of the above cause values applies but still the cause is Radio Network layer related. | +| Semi-Persistent scheduling not supported | The concerned cell(s) do not support the Semi-Persistent scheduling operation (for 1.28Mcps TDD only) | +| Continuous Packet Connectivity DRX not supported | The concerned cell(s) do not support the Continuous Packet Connectivity DRX operation (for 1.28Mcps TDD only) | +| Continuous Packet Connectivity DRX not available | HSPA resources for DRX operation not available in the concerned cell(s). (for 1.28Mcps TDD only) | +| Frequency Specific Compressed Mode not available | Frequency Specific Compressed Mode is not available in the concerned cell(s). | +| UL CLTD operation not available | UL CLTD resources are not available in the concerned cell(s). | +| Multiflow operation not available | Multiflow operation is not available in the concerned cell(s). | +| SixtyfourQAM UL operation not available | SixtyfourQAM UL resources are not available in the concerned cell(s). | +| UL MIMO operation not available | UL MIMO resources are not available in the concerned cell(s). | +| UL MIMO and SixteenQAM operation not available | UL MIMO and SixteenQAM resources are not available in the concerned cell(s). | +| UL MIMO and SixtyfourQAM operation not available | UL MIMO and SixtyfourQAM resources are not available in the concerned cell(s). | +| NodeB Triggered HS-DPCCH Transmission operation not available | NodeB Triggered HS-DPCCH Transmission operation is not available in the concerned cell(s). | +| 2ms and 10ms TTI Concurrent Deployment operation not available | Concurrent Deployment of 2ms and 10ms TTI operation is not available in the concerned cell(s). | +| Further Enhanced UE DRX operation not available | Further Enhanced UE DRX operation is not available in the concerned cell(s). | +| Per HARQ Activation and Deactivation operation not available | Per HARQ Activation and Deactivation operation is not available in the concerned cell(s). | +| TTI alignment operation not available | TTI alignment operation is not available in the concerned cell(s). | +| Common E-RGCH operation not available | Common E-RGCH operation is not available in the concerned cell(s). | +| MIMO with four transmit antennas not | MIMO with four transmit antennaeas not available in the concerned cell(s) | + +| | | +|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| available | | +| Dual Stream MIMO with four transmit antennas not available | Dual Stream MIMO with four transmit antennas not available in the concerned cell(s). | +| E-DCH decoupling operation not available | E-DCH decoupling operation is not available in the concerned cell(s). | +| Basic DCH Enhancements operation not available | Basic DCH Enhancements resources are not available in the concerned cell(s). | +| Full DCH Enhancements operation not available | Full DCH Enhancements resources are not available in the concerned cell(s). | +| Radio Links without DPCH/F-DPCH operation not available | Radio Links without DPCH/F-DPCH operation is not available in the concerned cell(s). | +| UL DPCCH2 operation not available | UL DPCCH2 operation is not available in the concerned cell(s). | +| Downlink TPC enhancements operation not available | Downlink TPC enhancements is not available in the concerned cell(s). | +| Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available | Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI is not available in the concerned cell(s). | +| Dual Cell E-DCH operation enhancements with different TTI operation not available | Dual Cell E-DCH operation enhancements with different TTI is not available in the concerned cell(s). | + +| Transport Network 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. | + +| Protocol cause | Meaning | +|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerned criticality indicated "reject" (see subclause 10.3). | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify" (see subclause 10.3). | +| Abstract syntax error (falsely constructed message) | The received message contained IEs in wrong order or with too many occurrences (see subclause 10.3). | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state (see subclause 10.4). | +| Semantic Error | The received message included a semantic error (see subclause 10.4). | +| Transfer Syntax Error | The received message included a transfer syntax error (see subclause 10.2). | +| Unspecified | Sent when none of the above cause values applies but still the cause is protocol related. | + +| Miscellaneous cause | Meaning | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Control Processing Overload | Node B control processing overload. | +| Hardware Failure | Node B hardware failure. | +| Not enough User Plane Processing Resources | Node B has insufficient user plane processing resources available. | +| O&M Intervention | Operation and Maintenance intervention related to Node B equipment. | +| Unspecified | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. | + +#### 9.2.1.7 CFN + +Connection Frame Number for the radio connection, see ref. TS 25.402 [17]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| CFN | | | INTEGER (0..255) | | + +#### 9.2.1.8 CFN Offset + +Void. + +#### 9.2.1.9 C-ID + +The C-ID (Cell identifier) is the identifier of a cell in one RNC. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| C-ID | | | INTEGER (0..65535) | | + +#### 9.2.1.9A Common Channels Capacity Consumption Law + +The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the allocated Spreading Factor. [FDD - For the PRACH, the reference spreading factor shall be the minimum possible spreading factor amongst the ones defined by the *RACH Slot Format* IE(s) in the Common Transport Channel Setup or Reconfiguration procedures.] + +This capacity consumption law indicates the consumption law to be used with the following procedures: + +- Common Transport Channel Setup +- Common Transport Channel Deletion +- [FDD - Common Transport Channel Reconfiguration] + +For the Common Transport Channel Setup procedure, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall be credited to the Capacity Credit for the Common Transport Channel Deletion one. + +[FDD - For the Common Transport Channel Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited if this difference is negative).] + +If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the "DL cost" shall be applied to the "DL or Global Capacity Credit" and the "UL Cost" shall be applied to the "UL Capacity Credit". If it is modelled as shared resources, both the "DL cost" and the "UL cost" shall be applied to the "DL or Global Capacity Credit". + +[FDD - When the Common Transport Channel Setup, Deletion or Reconfiguration procedures are used, the Capacity Credit shall be updated considering all physical channels related in these procedures (S-CCPCH, PICH, PRACH and AICH), i.e. one cost shall be credited to or debited from the Capacity Credit per physical channel.] + +[FDD - The costs given in the consumption law are the costs per channelization code. When multiple channelization codes are used by a physical channel, the cost credited to or debited from the Capacity Credit for this physical channel shall be taken as N times the cost given in the consumption law, where N is the number of channelization codes.] + +[TDD - When the Common Transport Channel Setup or Deletion procedures are used, the Capacity Credit shall be updated considering all physical channels related in these procedures (S-CCPCH, PICH, PRACH), i.e. one cost shall be credited to or debited from the Capacity Credit per physical channel.] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-----------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SF Allocation Law | | 1..<maxNrOfSF> | | [FDD - For each SF, cost of its allocation: the first instance corresponds to SF = 4, the second to SF = 8, the third to SF = 16 and so on.]
[TDD - For each SF, cost of its allocation: the first instance corresponds to SF = 1, the second to SF = 2, the third to SF = 4 and so on.] | +| >DL cost | M | | INTEGER (0..65535) | | +| >UL cost | M | | INTEGER (0..65535) | | + +| Range Bound | Explanation | +|------------------|-------------------------------------| +| maxNrOfSF | Maximum number of Spreading Factors | + +#### 9.2.1.9B Common Measurement Accuracy + +The *Common Measurement Accuracy* IE indicates the accuracy of the common measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------|----------|-------|-----------------------------------------------------------|-----------------------| +| CHOICE Common Measurement Accuracy | M | | | | +| > TUTRAN-GPS Measurement Accuracy Class | | | | | +| >> TUTRAN-GPS Measurement Accuracy Class | M | | TUTRAN-GPS Accuracy Class
9.2.1.64C | | +| > TUTRAN-GANSS Measurement Accuracy Class | | | | | +| >> TUTRAN-GANSS Measurement Accuracy Class | M | | TUTRAN-GANSS Accuracy Class
9.2.1.98 | | + +#### 9.2.1.10 Common Measurement Object Type + +Void. + +#### 9.2.1.11 Common Measurement Type + +The *Common Measurement Type* identifies which measurement that shall be performed. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Common Measurement Type | | |

ENUMERATED (

Received Total Wide Band Power,

Transmitted Carrier Power,

Acknowledged PRACH Preambles,

UL Timeslot ISCP,

NotUsed-1,

NotUsed-2,

...,

UTRAN GPS Timing of Cell Frames for UE Positioning,

SFN-SFN Observed Time Difference,

Transmitted carrier power of all codes not used for HS transmission,

HS-DSCH Required Power,

HS-DSCH Provided Bit Rate,

Received Total Wide Band Power for Cell Portion,

Transmitted Carrier Power for Cell Portion,

Transmitted carrier power of all codes not used for HS-PDSCH

HS-SCCH E-AGCH E-RGCH or E-HICH transmission for Cell Portion,

UpPCH Interference,

DL Transmission Branch Load,

HS-DSCH Required Power for Cell Portion,

HS-DSCH Provided Bit Rate for Cell Portion,

E-DCH Provided Bit Rate,

E-DCH Non-serving Relative Grant Down Commands,

Received Scheduled E-DCH Power Share,

Received Scheduled E-DCH Power Share for Cell Portion,

UTRAN GANSS Timing of Cell Frames for UE Positioning,

E-DCH RACH Report,

Transmitted carrier power of all codes not used for HS-PDSCH,

HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion,

UL Timeslot ISCP for Cell Portion,

E-DCH Provided Bit Rate for Cell Portion,

UpPCH Interference for Cell Portion)

|

"UL Timeslot ISCP" is used by TDD only,

"Acknowledged PRACH Preambles", "DL Transmission Branch Load", "E-DCH RACH Report" are used by FDD only,

"UpPCH interference" is used by 1.28Mcps TDD only.

This IE shall never be set to the values that are prefixed "NotUsed-".

[TDD - The IE Type "Transmitted carrier power of all codes not used for HS transmission" corresponds to the measurement "Transmitted carrier power of all codes not used for HS-PDSCH [TDD - E-AGCH, E-HICH] or HS-SCCH transmission" in TS 25.225 [5] and TS 25.123 [23].]

[FDD - The IE Type "Transmitted carrier power of all codes not used for HS transmission" corresponds to the measurement "Transmitted carrier power of all codes not used for HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH transmission" in TS 25.215 [4] and TS 25.133 [22].]

| + +#### 9.2.1.12 Common Measurement Value + +The Common Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Common Measurement Value | M | | | | – | | +| > Transmitted Carrier Power | | | | | | | +| >>Transmitted Carrier Power Value | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > Received Total Wide Band Power | | | | | | | +| >>Received Total Wide Band Power Value | M | | INTEGER (0..621) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > Acknowledged PRACH Preambles | | | | FDD Only | | | +| >>Acknowledged PRACH Preamble Value | M | | INTEGER (0..240,...) | According to mapping in TS 25.133 [22] | – | | +| > UL Timeslot ISCP | | | | TDD Only | | | +| >>UL Timeslot ISCP | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | – | | +| > Not used 1 | | | NULL | This choice shall not be used. Ignore if received. | | | +| > Not Used 2 | | | NULL | This choice shall not be used. Ignore if received. | | | +| > Additional Common Measurement Values | | | | See Note 1 | | | +| >> UTRAN GPS Timing Of Cell Frames for UE Positioning | | | | | | | +| >>>UTRAN-GPS Measurement Value Information | M | | 9.2.1.64A | | YES | ignore | +| >> SFN-SFN Observed Time Difference | | | | | | | +| >>>SFN-SFN Measurement Value Information | M | | 9.2.1.53E | | YES | ignore | +| >> Transmitted Carrier Power Of All Codes Not Used For HSTransmission | | | | | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission Value | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICHTransmission" and mapping in TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission" | YES | ignore | +| >> HS-DSCH Required Power | | | | | | | + +| | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------------------------|---------------------|-------------------------------------------|--------|--------| +| >>>HS-DSCH
Required Power
Value Information | M | | 9.2.1.31lc | | YES | ignore | +| >>HS-DSCH
Provided Bit Rate | | | | | | | +| >>>HS-DSCH
Provided Bit Rate
Value Information | M | | 9.2.1.31lb | | YES | ignore | +| >>Transmitted
Carrier Power For
Cell Portion | | | | FDD Only | | | +| >>>Transmitted
Carrier Power
For Cell Portion
Value | | 1..NrOfCel
lPortion
s> | | | GLOBAL | ignore | +| >>>>Cell
Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>Transmitted Carrier Power
Value | M | | INTEGER
(0..100) | According to mapping
in TS 25.133 [22] | – | | +| >>Received Total
Wide Band Power
For Cell Portion | | | | FDD Only | | | +| >>>Received
Total Wide Band
Power For Cell
Portion Value | | 1..NrOfCel
lPortion
s> | | | GLOBAL | ignore | +| >>>>Cell
Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>Received
Total Wide
Band Power
Value | M | | INTEGER
(0..621) | According to mapping
in TS 25.133 [22] | – | | +| >>Transmitted
Carrier Power Of
All Codes Not Used
For HS-PDSCH,
HS-SCCH, E-
AGCH, E-RGCH or
E-HICH
Transmission For
Cell Portion | | | | FDD Only | | | +| >>>Transmitted
Carrier Power Of
All Codes Not
Used For HS-
PDSCH, HS-
SCCH, E-AGCH,
E-RGCH or E-
HICH
Transmission
For Cell Portion
Value | | 1..NrOfCel
lPortion
s> | | | GLOBAL | ignore | +| >>>>Cell
Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>Transmitted Carrier Power
Of All Codes
Not Used For
HS-PDSCH,
HS-SCCH, E-
AGCH, E-
RGCH or E-
HICH
Transmission
Value | M | | INTEGER
(0..100) | According to mapping
in TS 25.133 [22] | – | | +| >>UpPCH
interference | | | | 1.28Mcps TDD Only | | | + +| | | | | | | | +|---------------------------------------------------------------------|---|----------------------------|----------------------|---------------------------------------------------|--------|--------| +| >>>UpPCH interference Value | M | | INTEGER (0..127,...) | According to mapping in TS 25.123 [23] | YES | ignore | +| >>DL Transmission Branch Load | | | | FDD Only | | | +| >>>Node B DL Transmission Branch Load Values | M | | INTEGER (0..101,...) | According to mapping in TS 25.133 [22] | YES | ignore | +| >>HS-DSCH Required Power For Cell Portion | | | | FDD Only | | | +| >>>HS-DSCH Required Power For Cell Portion Information | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>HS-DSCH Required Power Value Information | M | | 9.2.1.31lc | | – | | +| >>HS-DSCH Provided Bit Rate For Cell Portion | | | | FDD Only | | | +| >>>HS-DSCH Provided Bit Rate For Cell Portion Information | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>HS-DSCH Provided Bit Rate Value Information | M | | 9.2.1.31lb | | – | | +| >>E-DCH Provided Bit Rate | | | | | | | +| >>>E-DCH Provided Bit Rate Value Information | M | | 9.2.1.78 | | YES | ignore | +| >>E-DCH Non-serving Relative Grant Down Commands | | | | FDD Only | | | +| >>>E-DCH Non-serving Relative Grant Down Commands Value Information | M | | INTEGER (0..100,...) | Down Commands per second | YES | ignore | +| >>Received Scheduled E-DCH Power Share | | | | FDD Only According to definition in TS 25.215 [4] | | | +| >>>Received Scheduled E-DCH Power Share | | 1 | | | YES | ignore | +| >>>>RSEPS Value | M | | INTEGER (0..151) | According to mapping in TS 25.133 [22] | – | | +| >>>>RTWP* Value | O | | INTEGER (0..621) | According to mapping of RTWP in TS 25.133 [22] | – | | +| >>Received Scheduled E-DCH Power Share for Cell Portion | | | | FDD only According to definition in TS 25.215 [4] | | | +| >>>Received Scheduled E- | | 1..DCH Power Share For Cell Portion Value | | IPortions> | | | | | +| >>>>Cell Portion ID | M | | 9.2.2.1Ca | | – | | +| >>>>RSEPS for Cell Portion Value | M | | INTEGER (0..151) | According to mapping in TS 25.133 [22]. | – | | +| >>>>RTWP* for Cell Portion Value | O | | INTEGER (0..621) | According to mapping of RTWP in TS 25.133 [22] | – | | +| >>UTRAN GANSS Timing Of Cell Frames for UE Positioning | | | | | | | +| >>>T UTRAN-GANSS Measurement Value Information | M | | 9.2.1.100 | | YES | ignore | +| >>E-DCH RACH Report | | | | FDD Only | | | +| >>>E-DCH RACH Report Information | | 1..<maxNrOfCommonEDCH> | | The maximum repetitions should be limited to 1 so that this information is reported only once for a cell. | GLOBAL | ignore | +| >>>>Granted E-DCH RACH Resources | M | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25] | – | | +| >>>>Denied E-DCH RACH Resources | M | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25] | – | | +| >>>>2ms Granted E-DCH RACH Resources | O | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25]. | – | ignore | +| >>>>2ms Overridden E-DCH RACH Resources | O | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25]. | – | ignore | +| >>>>2ms Denied E-DCH RACH Resources | O | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25]. | – | ignore | +| >>Transmitted Carrier Power For Cell Portion LCR | | | | 1.28Mcps TDD Only | | | +| >>>Transmitted Carrier Power For Cell Portion Value LCR | | 1..<maxNrOfCellsPerCellLCR> | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>>Transmitted Carrier Power Value | M | | INTEGER (0..100) | According to mapping in TS 25.123 [23] | – | | +| >>Received Total Wide Band Power For Cell Portion LCR | | | | 1.28Mcps TDD Only | | | +| >>>Received Total Wide Band Power For Cell Portion Value LCR | | 1..<maxNrOfCellsPerCellLCR> | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | + +| | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|---|--------------------------------------|------------------|----------------------------------------|--------|--------| +| >>>>Received Total Wide Band Power Value | M | | INTEGER (0..621) | According to mapping in TS 25.123 [23] | – | | +| >>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion Value | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission Value | M | | INTEGER (0..100) | According to mapping in TS 25.123 [23] | – | | +| >>UL Timeslot ISCP For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>>UL Timeslot ISCP For Cell Portion Value | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>UL Timeslot ISCP | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | – | | +| >>HS-DSCH Required Power For Cell Portion LCR | | | | 1.28Mcps TDD Only | | | +| >>>HS-DSCH Required Power For Cell Portion Information LCR | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>>HS-DSCH Required Power Value Information | M | | 9.2.1.31lc | | – | | +| >>HS-DSCH Provided Bit Rate For Cell Portion LCR | | | | 1.28Mcps TDD Only | | | +| >>>HS-DSCH Provided Bit Rate For Cell | | 1.. | | | GLOBAL | ignore | + +| | | | | | | | +|----------------------------------------------------------|---|-------------------------------------|----------------------|----------------------------------------|--------|--------| +| Portion Information LCR | | sPerCellLCR> | | | | | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>>HS-DSCH Provided Bit Rate Value Information | M | | 9.2.1.31lb | | – | | +| >> E-DCH Provided Bit Rate For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>> E-DCH Provided Bit Rate For Cell Portion Information | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>> E-DCH Provided Bit Rate Value Information | M | | 9.2.1.78 | | – | | +| >> UpPCH interference For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>> UpPCH interference For Cell Portion Information | | 1.. | | | GLOBAL | ignore | +| >>>>Cell Portion LCR ID | M | | 9.2.3.107 | | – | | +| >>>> UpPCH interference Value | M | | INTEGER (0..127,...) | According to mapping in TS 25.123 [23] | – | | + +Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. + +| Range Bound | Explanation | +|--------------------------------------|----------------------------------------------------------------| +| MaxNrOfCellPortions | Maximum number of Cell Portions in a cell | +| maxNrOfCommonEDCH | Maximum number of Common E-DCH Resource Combination for a cell | +| MaxNrOfCellPortionsPerCellLCR | Maximum number of Cell Portions in a cell for 1.28 Mcps TDD | + +##### 9.2.1.12A Common Measurement Value Information + +The *Common Measurement Value Information* IE provides information both on whether the Common Measurement Value is provided in the message or not and if provided also the Common Measurement Value itself. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Measurement Availability Indicator | M | | | | +| > Measurement Available | | | | | +| >>Common Measurement Value | M | | 9.2.1.12 | | +| > Measurement Not Available | | | NULL | | + +#### 9.2.1.13 Common Physical Channel ID + +Common Physical Channel ID is the unique identifier for one common physical channel within a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID | | | INTEGER (0..255) | | + +##### 9.2.1.13A Common Physical Channel Status Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID | M | | 9.2.1.13 | | +| Resource Operational State | M | | 9.2.1.52 | | +| Availability Status | M | | 9.2.1.2 | | + +#### 9.2.1.14 Common Transport Channel ID + +Common Transport Channel ID is the unique identifier for one common transport channel within a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Common Transport Channel ID | | | INTEGER (0..255) | | + +##### 9.2.1.14A Common Transport Channel Information Response + +The *Common Transport Channel Information Response* IE provides information for Common Transport Channels that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Common Transport Channel ID | M | | 9.2.1.14 | | – | | +| Binding ID | O | | 9.2.1.4 | | – | | +| Transport Layer Address | O | | 9.2.1.63 | | – | | +| Broadcast Common Transport Bearer Indication | O | | 9.2.1.5B | | YES | ignore | +| IP Multicast Data Bearer Indication | O | | 9.2.1.109 | | YES | ignore | + +##### 9.2.1.14B Common Transport Channel Status Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Common Transport Channel ID | M | | 9.2.1.14 | | +| Resource Operational State | M | | 9.2.1.52 | | +| Availability Status | M | | 9.2.1.2 | | + +#### 9.2.1.15 Communication Control Port ID + +A Communication Control Port corresponds to one signalling bearer between the CRNC and the Node B for the control of Node B Communication Contexts. The Node B may have multiple Communication Control Ports (one per Traffic Termination Point). The Communication Control Port is selected at creation of the Node B Communication Context. The Communication Control Port ID is the identifier of the Communication Control Port. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|-----------------------| +| Communication Control Port ID | | | INTEGER (0..65535) | | + +#### 9.2.1.16 Configuration Generation ID + +The Configuration Generation ID describes the generation of the configuration of logical resources in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------| +| Configuration Generation ID | | | INTEGER (0..255) | Value "0" means "No configuration".
At possible wraparound of the ID counter in CRNC the value "0" shall not be used. | + +#### 9.2.1.17 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by a Node B or the CRNC when parts of a received message have not been comprehended or are missing, or if the message contained logical errors. When applicable, it contains information about which IEs that were not comprehended or were missing. + +For further details on how to use the *Criticality Diagnostics* IE, see Annex C. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|---------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Procedure ID | | 0..1 | | Procedure ID is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | – | | +| >Procedure Code | M | | INTEGER (0..255) | | – | | +| >Ddmode | M | | ENUMERATED ( TDD, FDD, Common, ...) | "Common" = common to FDD and TDD. | – | | +| Triggering Message | O | | ENUMERATED ( initiating message, successful outcome, unsuccessful outcome, outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication. | – | | +| Procedure Criticality | O | | ENUMERATED ( reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | – | | +| Transaction ID | O | | 9.2.1.62 | | – | | +| Information Element Criticality Diagnostics | | 0.. | | | – | | +| >IE Criticality | M | | ENUMERATED ( reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value "ignore" shall never be used. | – | | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of the not understood or missing IE | – | | +| >Repetition Number | O | | INTEGER (0..255) | The Repetition Number IE gives:
for a not understood IE:
The number of occurrences of the reported IE up to and including the not understood occurrence
for a missing IE:
The number of occurrences up to but not including the missing occurrence.
Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them. | – | | + +| | | | | | | | +|--------------------|---|--|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >Message Structure | O | | 9.2.1.45A | The Message Structure IE describes the structure where the not understood or missing IE was detected.
This IE is included if the not understood IE is not the top level of the message. | YES | ignore | +| >Type Of Error | M | | ENUMERATED (not understood, missing, ...) | | YES | ignore | + +| Range Bound | Explanation | +|----------------------|---------------------------------------------------------------------------| +| maxNrOfErrors | Maximum number of IE errors allowed to be reported with a single message. | + +#### 9.2.1.18 CRNC Communication Context ID + +The CRNC Communication Context ID is the identifier of the Communication Context in the CRNC. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CRNC Communication Context ID | | | INTEGER (0..2 20 – 1) | "2 20 -1" is a reserved value indicating all the CRNC Communication Contexts that can be reached by the Communication Control Port (All CRNCCC). | + +#### 9.2.1.18A CTFC + +The CTFC is an integer number calculated in accordance with TS 25.331 [18], subclause 14.10. Regarding the channel ordering, for all transport channels, 'TrCH1' corresponds to the transport channel having the lowest transport channel identity among all configured transport channels on this CCTrCH. 'TrCH2' corresponds to the transport channel having the next lowest transport channel identity, and so on. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE CTFC Format | M | | | | +| >2 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..3) | | +| >4 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..15) | | +| >6 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..63) | | +| >8 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..255) | | +| >12 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..4095) | | +| >16 bits long | | | | | +| >>CTFC value | M | | INTEGER (0..65535) | | +| >max nb bits long | | | | | +| >>CTFC value | M | | INTEGER (0..maxCTFC) | | + +| Range Bound | Explanation | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------| +| MaxCTFC | Maximum number of the CTFC value is calculated according to the following:

with the notation according to ref. TS 25.331 [18] | + +#### 9.2.1.19 DCH Combination Indicator + +Void. + +#### 9.2.1.20 DCH ID + +The DCH ID is the identifier of an active dedicated transport channel. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| DCH ID | | | INTEGER (0..255) | | + +##### 9.2.1.20A Dedicated Channels Capacity Consumption Law + +The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the [FDD - allocated Spreading Factor and the RL/RLS situation] [TDD - allocated Spreading Factor on each DPCH and the assigned timeslot]. [FDD - In Uplink, the reference spreading factor shall be the minimum spreading factor signalled in the Radio Link Setup Request message. This is signalled using the *Min UL Channelisation Code Length* IE.] + +This capacity consumption law indicates the consumption law to be used with the following procedures : + +- Radio Link Setup +- Radio Link Addition +- Radio Link Reconfiguration +- Radio Link Deletion +- [TDD - Physical Shared Channel Reconfiguration] + +For the Radio Link Setup and Radio Link Addition procedures, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall be credited to the Capacity Credit for the Radio Link Deletion procedure. For the Radio Link Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited when this difference is negative). + +If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit. + +[FDD - For a Radio Link creating a Radio Link Set (first RL of a RLS), the cost for the RL (cost 2) and RLS (cost 1) shall be taken into account. When adding a Radio Link to a Radio Link Set, only the RL cost (cost 2) shall be taken into account. + +In the case where multiple Radio Links are established in one procedure, for every created Radio Link Set, the first Radio Link is always the Radio Link with the lowest repetition number.] + +[FDD - The costs given in the consumption law are the costs per channelization code. When multiple channelization codes are used by either the radio links, the cost credited to or debited from the Capacity Credit shall be taken as N times the cost for one code, where N is the number of channelization codes.] + +[TDD - The cost for a radio link is a sum of the costs for each DPCH. For the first DPCH assigned to any user in a cell within a timeslot, the initial cost for a DPCH in a timeslot (cost 1) and the cost for a DPCH (cost 2) shall be taken into + +account. For any DPCH that is not the first DPCH assigned for any user in a cell within a timeslot, only the cost for a DPCH (cost 2) shall be taken into account.] + +[TDD - The cost for shared channels is the sum of the costs for each PDSCH and PUSCH assigned to a PUSCH or PDSCH set. For the first PDSCH or PUSCH assigned to any user in a cell within a timeslot, the initial cost for a PDSCH/PUSCH in a timeslot (cost 1) and the cost for a PDSCH/PUSCH (cost 2) shall be taken into account. For any PDSCH/PUSCH that is not the first PDSCH/PUSCH assigned to any user in a cell within a timeslot, only the cost for a PDSCH/PUSCH (cost 2) shall be taken into account.] + +[TDD - In the case of Physical Shared Channel Reconfiguration, the sum of the consumption cost of the each PDSCH/PUSCH of the previous configuration shall be credited to the capacity credit, and the sum of the consumption cost of each PDSCH/PUSCH of the new configuration shall be subtracted from the capacity credit.] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|----------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SF Allocation Law | | 1.. | | [FDD - For each SF, cost of its allocation: the first instance corresponds to SF = 4, the second to SF = 8, the third to SF = 16 and so on.]
[TDD - For each SF, cost of its allocation: the first instance corresponds to SF = 1, the second to SF = 2, the third to SF = 4 and so on.] | +| >DL Cost 1 | M | | INTEGER (0..65535) | [FDD - This is the cost of a RLS.]
[TDD - This is the additional cost of the first DPCH/PDSCH/PUSCH assigned to any user in a cell within a timeslot.] | +| >DL Cost 2 | M | | INTEGER (0..65535) | [FDD - This is the cost of a RL.]
[TDD - This is the cost of a DPCH/PDSCH/PUSCH] | +| >UL Cost 1 | M | | INTEGER (0..65535) | [FDD - This is the cost of a RLS.]
[TDD - This is the additional cost of the first DPCH/PDSCH/PUSCH assigned to any user in a cell within a timeslot.] | +| >UL Cost 2 | M | | INTEGER (0..65535) | [FDD - This is the cost of a RL.]
[TDD - This is the cost of a DPCH/PDSCH/PUSCH.] | + +| Range Bound | Explanation | +|-------------|-------------------------------------| +| maxNrOfSF | Maximum number of Spreading Factors | + +##### 9.2.1.20B DL Or Global Capacity Credit + +The capacity credit indicates to the CRNC the Downlink or global capacity of a Local Cell or a Local Cell Group. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| DL Or Global Capacity Credit | | | INTEGER (0..65535) | | + +#### 9.2.1.20C DCH Information Response + +The *DCH Information Response* IE provides information for DCHs that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|------------------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| DCH Information Response | | 1.. | | Only one DCH per set of coordinated DCHs shall be included | – | | +| >DCH ID | M | | 9.2.1.20 | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| >Transport Bearer Not Setup Indicator | O | | 9.2.2.4H | FDD only | YES | ignore | + +| Range Bound | Explanation | +|-------------|------------------------------| +| maxNrOfDCHs | Maximum number of DCH per UE | + +#### 9.2.1.21 DL Power + +The *DL Power* IE indicates a power level relative to the [FDD - primary CPICH power] [TDD - primary CCPCH power] configured in a cell. If Transmit Diversity is applied to a downlink physical channel, the *DL Power* IE indicates the power offset between the linear sum of the power for this downlink physical channel on all branches and the [FDD - primary CPICH power] [TDD - PCCPCH power] configured in a cell. + +[FDD - If referred to a DPCH, it indicates the power of the transmitted DPDCH symbols.] [FDD - If referred to an F-DPCH, it indicates the Reference F-DPCH TX Power.] + +[TDD - If referred to a DPCH or PDSCH, it indicates the power of a spreading factor 16 code, the power for a spreading factor 1 code would be 12 dB higher. If referred to a SCCPCH, the *DL Power* IE specifies the maximum power of the SCCPCH.] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|------------------------|-----------------------------------------------------------------------------| +| DL Power | | | INTEGER
(-350..150) | Value = DL Power /10
Unit: dB
Range: -35.0 .. +15.0 dB
Step: 0.1dB | + +#### 9.2.1.22 Dedicated Measurement Object Type + +Void. + +#### 9.2.1.23 Dedicated Measurement Type + +The Dedicated Measurement Type identifies the type of measurement that shall be performed. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dedicated Measurement Type | | | ENUMERATED (
SIR,
SIR Error,
Transmitted Code Power,
RSCP,
Rx Timing Deviation,
Round Trip Time,
...
Rx Timing Deviation LCR,
Angle Of Arrival LCR,
HS-SICH reception quality,
Best Cell Portions, Rx Timing Deviation 7.68Mcps,
Rx Timing Deviation 3.84 Mcps Extended,
Best Cell Portions LCR,
AOA per Cell Portion LCR,
UE transmission power headroom,
DL transport block size) | "RSCP" and "HS-SICH reception quality" are used by TDD only.
"Rx Timing Deviation" and "Rx Timing Deviation 3.84 Mcps Extended" are used by 3.84Mcps TDD only.
"Rx Timing Deviation LCR", "Angle Of Arrival LCR" are used by 1.28Mcps TDD only.
"Round Trip Time", "SIR Error" are used by FDD only.
"Best Cell Portions" is used by FDD only.
"Best Cell Portions LCR" is used by 1.28Mcps TDD only.
"Rx Timing Deviation 7.68Mcps" is used by 7.68Mcps TDD only.
"UE transmission power headroom" is used by FDD, 1.28Mcps TDD, 3.84Mcps TDD and 7.68Mcps TDD.
"DL transport block size" is used by FDD only. | +| Note: For definitions of the measurement types refer to TS 25.215 [4] and TS 25.225 [5]. | | | | | + +#### 9.2.1.24 Dedicated Measurement Value + +The Dedicated Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|-------|-------------------------------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Dedicated Measurement Value | M | | | | – | | +| > SIR Value | | | | | | | +| >> SIR Value | M | | INTEGER (0..63) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > SIR Error Value | | | | FDD only | | | +| >> SIR Error Value | M | | INTEGER (0..125) | According to mapping in TS 25.133 [22] | – | | +| > Transmitted Code Power Value | | | | | | | +| >> Transmitted Code Power Value | M | | INTEGER (0..127) | According to mapping in TS 25.133 [22] and TS 25.123 [23]. Values 0 to 9 and 123 to 127 shall not be used. | – | | +| > RSCP | | | | TDD only | | | +| >> RSCP | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | – | | +| > Rx Timing Deviation Value | | | | Applicable to 3.84Mcps TDD only | | | +| >> Rx Timing Deviation | M | | INTEGER (0..8191) | According to mapping in TS 25.123 [23] | – | | +| > Round Trip Time | | | | FDD only | | | +| >> Round Trip Time | M | | INTEGER (0..32767) | According to mapping in TS 25.133 [22] | – | | +| > Additional Dedicated Measurement Values | | | | See Note 1. | | | +| >> Rx Timing Deviation Value LCR | | | | Applicable to 1.28Mcps TDD only | | | +| >>> Rx Timing Deviation LCR | M | | INTEGER (0..511) | According to mapping in TS 25.123 [23] | YES | reject | +| >> Angle Of Arrival Value LCR | | | | Applicable to 1.28Mcps TDD only | | | +| >>> AOA Value LCR | | 1 | | | YES | reject | +| >>>> AOA LCR | M | | INTEGER (0..719) | According to mapping in TS 25.123 [23] | – | | +| >>>> AOA LCR Accuracy Class | M | | ENUMERATE D ( A, B, C, D, E, F, G, H,...) | According to mapping in TS 25.123 [23] | – | | +| >> HS-SICH Reception Quality | | | | Applicable to TDD only | | | +| >>> HS-SICH Reception Quality Value | | 1 | | | YES | reject | +| >>>> Failed HS-SICH | M | | INTEGER (0..20) | According to mapping in TS 25.123 [23] | – | | +| >>>> Missed HS-SICH | M | | INTEGER (0..20) | According to mapping in TS 25.123 [23] | – | | +| >>>> Total HS-SICH | M | | INTEGER (0..20) | According to mapping in TS 25.123 [23] | – | | +| >>>> Failed HS-SICH LCR extension | O | | INTEGER (0..20) | According to mapping in TS 25.123 [23] Mandatory for LCR TDD when there are more than 20 failed HS-SICH | YES | reject | +| >>>> Missed HS-SICH LCR extension | O | | INTEGER (0..20) | According to mapping in TS 25.123 [23] Mandatory for LCR | YES | reject | + +| | | | | | | | +|-----------------------------------------------|---|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------|------|--------| +| | | | | TDD when there are more than 20 missed HS-SICH | | | +| >>>>Total HS-SICH LCR extension | O | | INTEGER (0..20) | According to mapping in TS 25.123 [23]
Mandatory for LCR
TDD when there are more than 20 total HS-SICH | YES | reject | +| >>Best Cell Portions | | | | FDD only | | | +| >>>Best Cell Portions | M | | 9.2.2.1Ba | | YES | reject | +| >>Rx Timing Deviation Value 7.68Mcps | | | | Applicable to 7.68Mcps TDD only | | | +| >>>Rx Timing Deviation 7.68Mcps | M | | INTEGER (0..65535) | According to mapping in TS 25.123 [23] | YES | reject | +| >>Rx Timing Deviation Value 3.84Mcps Extended | | | | Applicable to 3.84Mcps TDD only | | | +| >>>Rx Timing Deviation 3.84Mcps Extended | M | | INTEGER (0..32767) | According to mapping in TS 25.123 [23] | YES | reject | +| >>Extended Round Trip Time | | | | FDD only | | | +| >>>Extended Round Trip Time Value | M | | INTEGER (32767..103041) | Continuation of intervals with step size as defined in TS 25.133 [22]. | YES | reject | +| >>Best Cell Portions LCR | | | | 1.28Mcps TDD only | | | +| >>>Best Cell Portions LCR | M | | 9.2.3.105 | | YES | reject | +| >>AOA per Cell Portion LCR | | | | 1.28Mcps TDD only | | | +| >>>AOA per Cell Portion LCR | M | | 9.2.3.124 | | YES | reject | +| >>UE transmission power headroom | | | | | | | +| >>>UE transmission power headroom | M | | INTEGER (0..31) | According to mapping in TS 25.133 [22] and TS 25.123 [23]. | YES | reject | +| >>DL transport block size | | | | FDD only | | | +| >>>HS-DSCH Cell List | M | 1.. | | | EACH | reject | +| >>>>HS-DSCH Cell TBS | M | | INTEGER (0..160000) | According to mapping of CQI in TS 25.214 [10].
See Note 2. | – | – | + +Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. + +Note 2: In case of Dual Stream MIMO, this information element is the sum of the transport block size values from both streams of the cell. + +| Range Bound | Explanation | +|-----------------|--------------------------------------------| +| maxNrOfHSDSCH-1 | Maximum number of HS-DSCH cells for one UE | + +##### 9.2.1.24A Dedicated Measurement Value Information + +The *Dedicated Measurement Value Information* IE provides information both on whether or not the Dedicated Measurement Value is provided in the message or not and if provided also the Dedicated Measurement Value itself. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------|--------------------------------------| +| CHOICE Measurement Availability Indicator | M | | | | +| > Measurement Available | | | | | +| >>Dedicated Measurement Value | M | | 9.2.1.24 | | +| >>CFN | O | | 9.2.1.7 | Dedicated Measurement Time Reference | +| > Measurement Not Available | | | NULL | | + +##### 9.2.1.24B DGPS Corrections + +The *DGPS Corrections* IE contains DGPS information used by the UE Positioning A-GPS method. For further details on the meaning of parameters, see RTCM-SC104 [28]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------|----------|----------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GPS TOW | M | | INTEGER (0..604799) | Time in seconds. This field indicates the baseline time for which the corrections are valid. | – | | +| Status/Health | M | | ENUMERATED ( UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.1, no data, invalid data) | This field indicates the status of the differential corrections. | – | | +| Satellite Information | | 1.. | | | – | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27]. | – | | +| >IOE | M | | BIT STRING (SIZE(8)) | This IE is the sequence number for the ephemeris for the particular satellite. It can be used to determine if new ephemeris is used for calculating the corrections that are provided. This eight-bit IE is incremented for each new set of ephemeris for the satellite and may occupy the numerical range of [0, 239] during normal operations. | – | | +| >UDRE | M | | ENUMERATED ( UDRE $\leq$ 1.0m, 1.0m < UDRE $\leq$ 4.0m, 4.0m < UDRE $\leq$ 8.0m, 8.0m < UDRE) | User Differential Range Error. This field provides an estimate of the uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the common Corrections Status/Health field to determine the final UDRE estimate for the particular satellite | – | | +| >PRC | M | | INTEGER (-2047..2047) | Pseudo Range Correction
Unit: m (meters)
Step: 0.32 meters | – | | +| >Range Correction Rate | M | | INTEGER (-127..127) | Unit: m/s
Step: 0.032 m/s | – | | +| >DGNSS Validity Period | O | | 9.2.1.125 | | YES | ignore | + +| Range Bound | Explanation | +|-------------|--------------------------------------------------------------------| +| maxNoSat | Maximum number of satellites for which information can be provided | + +#### 9.2.1.24C Delayed Activation + +The *Delayed Activation* IE indicates that the activation of the DL power shall be delayed until an indicated CFN or until a separate activation indication is received. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Delayed Activation | M | | | | +| >CFN | | | | | +| >>Activation CFN | M | | CFN 9.2.1.7 | | +| >Separate Indication | | | NULL | | + +##### 9.2.1.24D Delayed Activation Update + +The *Delayed Activation Update* IE indicates a change of the activation of the DL power for a specific RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned criticality | +|-----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE Delayed Activation Update | M | | | | – | | +| >Activate | | | | | | | +| >>CHOICE Activation Type | M | | | | – | | +| >>>Synchronised | | | | | | | +| >>>>Activation CFN | M | | CFN 9.2.1.7 | | – | | +| >>>Unsyncronised | | | NULL | | | | +| >>Initial DL TX Power | M | | DL Power 9.2.1.21 | | – | | +| >>First RLS Indicator | O | | 9.2.2.16A | FDD Only | – | | +| >>Propagation Delay | O | | 9.2.2.35 | FDD Only | – | | +| >>Extended Propagation Delay | O | | 9.2.2.35A | FDD Only | YES | reject | +| >Deactivate | | | | | | | +| >>CHOICE Deactivation Type | M | | | | – | | +| >>>Synchronised | | | | | | | +| >>>>Deactivation CFN | M | | CFN 9.2.1.7 | | – | | +| >>>Unsyncronised | | | NULL | | | | + +#### 9.2.1.24E Discard Timer + +The *Discard Timer* IE defines the time to live for a MAC-hs SDU starting from the instant of its arrival into an HSDPA Priority Queue. The Node B shall use this information to discard out-of-data MAC-hs SDUs from the HSDPA Priority Queues. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Discard Timer | | | ENUMERATED (20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 250, 300, 400, 500, 750, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 7500, ...) | Unit: ms | + +#### 9.2.1.25 Diversity Control Field + +The Diversity Control Field indicates if the current RL may, must or must not be combined with the already existing RLs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|----------------------------------------|-----------------------| +| Diversity Control Field | | | ENUMERATED ( May, Must, Must Not, ...) | | + +#### 9.2.1.26 Diversity Indication + +Void. + +##### 9.2.1.26A DL DPCH Timing Adjustment + +Void. + +#### 9.2.1.27 DSCH ID + +Void. + +##### 9.2.1.27A DSCH Information Response + +Void + +#### 9.2.1.28 DSCH Transport Format Set + +Void. + +#### 9.2.1.29 DSCH Transport Format Combination Set + +Void. + +#### 9.2.1.29A End Of Audit Sequence Indicator + +Indicates if the AUDIT RESPONSE message ends an audit sequence or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| End Of Audit Sequence Indicator | | | ENUMERATED ( End of audit sequence, Not end of audit sequence) | "End of audit sequence" = all audit information has been provided by the Node B.
"Not end of audit sequence" = more audit information is available. | + +#### 9.2.1.29B FN Reporting Indicator + +The Frame Number Reporting Indicator indicates if the SFN or CFN shall be included together with the reported measurement value. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|----------------------------------------------------------------|-----------------------| +| FN Reporting Indicator | | | ENUMERATED ( FN Reporting Required, FN Reporting Not Required) | | + +#### 9.2.1.30 Frame Handling Priority + +This parameter indicates the priority level to be used during the lifetime of the DCH [TDD - DSCH] for temporary restriction of the allocated resources due overload reason. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------| +| Frame Handling Priority | | | INTEGER (0..15) | "0" = lowest priority,
...
"15" = highest priority | + +#### 9.2.1.31 Frame Offset + +The Frame Offset is the required offset between the dedicated channel downlink transmission frames (CFN, Connection Frame Number) and the broadcast channel frame offset (Cell Frame Number). The Frame Offset is used in the translation between Connection Frame Number (CFN) on Iub/Iur and the least significant 8 bits of SFN (System Frame Number) on Uu. The Frame Offset is UE and cell specific. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Frame Offset | | | INTEGER (0..255) | Frames | + +#### 9.2.1.31A IB\_OC\_ID + +The IB OC ID identifies the occurrence of a specific Information Block. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IB OC ID | | | INTEGER (1..16) | Value 1 indicates the first occurrence for the specific Information Block.

Value 2 indicates the second occurrence for the specific Information Block.

...

Value 16 indicates the sixteenth occurrence for the specific Information Block. | + +#### 9.2.1.31B GPS Navigation Model & Time Recovery + +This IE contains subframes 1 to 3 of the GPS navigation message. For further details on the meaning of parameters, see ICD-GPS-200 [27]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------------------|------------------------|--------------------------------------------------------------------------------------------------------| +| Navigation Message 1to3 | | 1..oSat> | | | +| >Transmission TOW | M | | INTEGER (0..1048575) | Time of the Week when the message is broadcast. | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27]. | +| >TLM Message | M | | BIT STRING (SIZE(14)) | | +| >Tlm Revd (C) | M | | BIT STRING (SIZE (2)) | | +| >HO-Word | M | | BIT STRING (SIZE (22)) | | +| >WN | M | | BIT STRING (SIZE (10)) | | +| >C/A or P on L2 | M | | BIT STRING (SIZE (2)) | | +| >User Range Accuracy Index | M | | BIT STRING (SIZE (4)) | | +| >SV Health | M | | BIT STRING (SIZE (6)) | | +| >IODC | M | | BIT STRING (SIZE (10)) | | +| >L2 P Data Flag | M | | BIT STRING (SIZE (1)) | | +| >SF 1 Reserved | M | | BIT STRING (SIZE (87)) | | +| >T GD | M | | BIT STRING (SIZE (8)) | | +| >t oc | M | | BIT STRING (SIZE (16)) | | +| >af 2 | M | | BIT STRING (SIZE (8)) | | +| >af 1 | M | | BIT STRING (SIZE (16)) | | +| >af 0 | M | | BIT STRING (SIZE (22)) | | +| >C rs | M | | BIT STRING (SIZE (16)) | | +| >Δn | M | | BIT STRING (SIZE (16)) | | +| >M 0 | M | | BIT STRING (SIZE (32)) | | +| >C uc | M | | BIT STRING (SIZE (16)) | | +| >e | M | | BIT STRING (SIZE (32)) | | +| >C us | M | | BIT STRING (SIZE (16)) | | +| >(A) 1/2 | M | | BIT STRING (SIZE (32)) | | +| >t oe | M | | BIT STRING (SIZE (16)) | | +| >Fit Interval Flag | M | | BIT STRING (SIZE (1)) | | +| >AODO | M | | BIT STRING (SIZE (5)) | | +| >C ic | M | | BIT STRING (SIZE (16)) | | +| >OMEGA 0 | M | | BIT STRING (SIZE (32)) | | +| >C is | M | | BIT STRING (SIZE (16)) | | +| >i 0 | M | | BIT STRING (SIZE | | + +| | | | | | +|-----------------------|---|--|------------------------|--| +| | | | (32)) | | +| >C rc | M | | BIT STRING (SIZE (16)) | | +| >ω | M | | BIT STRING (SIZE (32)) | | +| >OMEGA dot | M | | BIT STRING (SIZE (24)) | | +| >Idot | M | | BIT STRING (SIZE (14)) | | +| >Spare/zero fill | M | | BIT STRING (SIZE (20)) | | + +| Range Bound | Explanation | +|-------------|--------------------------------------------------------------------| +| maxNoSat | Maximum number of satellites for which information can be provided | + +#### 9.2.1.31C GPS Ionospheric Model + +This IE provides the information regarding the GPS Ionospheric Model. For further details on the meaning of parameters, see ICD-GPS-200 [27]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-----------------------| +| α 0 | M | | BIT STRING (SIZE (8)) | | +| α 1 | M | | BIT STRING (SIZE (8)) | | +| α 2 | M | | BIT STRING (SIZE (8)) | | +| α 3 | M | | BIT STRING (SIZE (8)) | | +| β 0 | M | | BIT STRING (SIZE (8)) | | +| β 1 | M | | BIT STRING (SIZE (8)) | | +| β 2 | M | | BIT STRING (SIZE (8)) | | +| β 3 | M | | BIT STRING (SIZE (8)) | | + +#### 9.2.1.31D GPS UTC Model + +This IE provides the information regarding the GPS UTC Model. For further details on the meaning of parameters, see ICD-GPS-200 [27]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|------------------------|-----------------------| +| A 1 | M | | BIT STRING (SIZE (24)) | | +| A 0 | M | | BIT STRING (SIZE (32)) | | +| t ot | M | | BIT STRING (SIZE (8)) | | +| Δt LS | M | | BIT STRING (SIZE (8)) | | +| WN t | M | | BIT STRING (SIZE (8)) | | +| WN LSF | M | | BIT STRING (SIZE (8)) | | +| DN | M | | BIT STRING (SIZE (8)) | | +| Δt LSF | M | | BIT STRING (SIZE (8)) | | + +#### 9.2.1.31E GPS Real-Time Integrity + +This IE provides the information regarding the status of the GPS constellation. For further details on the meaning of parameters, see ICD-GPS-200 [27]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------| +| CHOICE Bad Satellites Presence | M | | | | +| > Bad Satellites | | | | | +| >> Satellite Information | | 1.. | | | +| >>>BadSatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27]. | +| > No Bad Satellites | | | NULL | | + +| Range Bound | Explanation | +|-----------------|--------------------------------------------------------------------| +| maxNoSat | Maximum number of satellites for which information can be provided | + +#### 9.2.1.31F GPS Almanac + +This IE provides the information regarding the GPS Almanac. For further details on the meaning of parameters, see ICD-GPS-200 [27]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| WNa | M | | BIT STRING (SIZE (8)) | | – | | +| Satellite Information | M | 1.. | | See Note 1. | – | | +| >DataID | M | | INTEGER (0..3) | | – | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27]. | – | | +| >e | M | | BIT STRING (SIZE (16)) | | – | | +| >t oa | M | | BIT STRING (SIZE (8)) | | – | | +| >δi | M | | BIT STRING (SIZE (16)) | | – | | +| >OMEGADOT | M | | BIT STRING (SIZE (16)) | | – | | +| >SV Health | M | | BIT STRING (SIZE (8)) | | – | | +| >A 1/2 | M | | BIT STRING (SIZE (24)) | | – | | +| >OMEGA 0 | M | | BIT STRING (SIZE (24)) | | – | | +| >M 0 | M | | BIT STRING (SIZE (24)) | | – | | +| >ω | M | | BIT STRING (SIZE (24)) | | – | | +| >af 0 | M | | BIT STRING (SIZE (11)) | | – | | +| >af 1 | M | | BIT STRING (SIZE (11)) | | – | | +| SV Global Health | O | | BIT STRING (SIZE (364)) | | – | | +| Complete Almanac Provided | O | | BOOLEAN | This field indicates whether almanac is provided for the full GPS constellation or not. TRUE means complete GPS almanac is provided | YES | ignore | +| Note 1: This information element is a simplified representation of the ASN.1 description. Repetitions 1 through maxNoSat and repetitions maxNoSat+1 through maxNoOfSatAlmanac are represented by separate ASN.1 structures with different criticality. | | | | | | | + +| Range Bound | Explanation | +|-------------------|----------------------------------------------------------------------------| +| maxNoOfSatAlmanac | Maximum number of satellite almanacs for which information can be provided | + +#### 9.2.1.31G GPS Receiver Geographical Position (GPS RX Pos) + +*The GPS Receiver Geographical Position is used to identify the geographical coordinates of a GPS receiver relevant for a certain Information Exchange Object.* + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED ( North, South) | | +| Degrees of Latitude | M | | INTEGER (0..2 23 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{23} \times X / 90 < N+1$
X being the latitude in degree (0°.. 90°) | +| Degrees of Longitude | M | | INTEGER (-2 23 ..2 23 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{24} \times X / 360 < N+1$
X being the longitude in degree (-180°..+180°) | +| Direction of Altitude | M | | ENUMERATED ( Height, Depth) | | +| Altitude | M | | INTEGER (0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | + +#### 9.2.1.31Ga HSDPA Capability + +This parameter defines the HSDPA capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------------------------------|-----------------------| +| HSDPA Capability | | | ENUMERATED (HSDPA Capable, HSDPA non Capable) | | + +#### 9.2.1.31H HS-DSCH Information To Modify + +The *HS-DSCH Information To Modify* IE is used for modification of HS-DSCH information in a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-----------------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH MAC-d Flow Specific Information | | 0..<maxNrOfMACdFlows> | | | – | | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| Priority Queue Information | | 0..<maxNrOfPriorityQueues> | | | – | | +| >CHOICE Priority Queue | M | | | | – | | +| >>Add Priority Queue | | | | | | | +| >>>Priority Queue ID | M | | 9.2.1.49C | | – | | +| >>>Associated HS-DSCH MAC-d Flow | M | | HS-DSCH MAC-d Flow ID
9.2.1.31I | Shall only refer to an HS-DSCH MAC-d flow already existing in the old configuration. Multiple Priority Queues can be associated with the same HS-DSCH MAC-d Flow ID. | – | | +| >>>Scheduling Priority Indicator | M | | 9.2.1.53H | | – | | +| >>>T1 | M | | 9.2.1.56a | | – | | +| >>>Discard Timer | O | | 9.2.1.24E | | – | | +| >>>MAC-hs Window Size | M | | 9.2.1.38B | | – | | +| >>>MAC-hs Guaranteed Bit Rate | O | | 9.2.1.38Aa | | – | | +| >>>MAC-d PDU Size Index | | 1..<maxNrOfMACdPDUs> | | | – | | +| >>>>SID | M | | 9.2.1.53I | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >>>>MAC-d PDU Size | M | | 9.2.1.38A | Shall be ignored if Maximum | – | | + +| | | | | | | | +|--|--|--|--|-------------------------------------------------------|--|--| +| | | | | MAC-d PDU
Size Extended
IE is present. | | | +|--|--|--|--|-------------------------------------------------------|--|--| + +| | | | | | | | +|------------------------------------------|---|----------------------------|---------------------------------|---------------------------------------------------------------------------------|-----|--------| +| >>>RLC Mode | M | | 9.2.1.52B | | – | | +| >>>Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | reject | +| >>>DL RLC PDU Size Format | O | | 9.2.1.122 | | Yes | ignore | +| >>Modify Priority Queue | | | | | | | +| >>>Priority Queue ID | M | | 9.2.1.49C | Shall only refer to a Priority Queue already existing in the old configuration. | – | | +| >>>Scheduling Priority Indicator | O | | 9.2.1.53H | | – | | +| >>>T1 | O | | 9.2.1.56a | | – | | +| >>>Discard Timer | O | | 9.2.1.24E | | – | | +| >>>MAC-hs Window Size | O | | 9.2.1.38B | | – | | +| >>>MAC-hs Guaranteed Bit Rate | O | | 9.2.1.38Aa | | – | | +| >>>MAC-d PDU Size Index | | 0.. | | | – | | +| >>>>SID | M | | 9.2.1.53I | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >>>>MAC-d PDU Size | M | | 9.2.1.38A | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >>>Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | reject | +| >>>DL RLC PDU Size Format | O | | 9.2.1.122 | | Yes | ignore | +| >>Delete Priority Queue | | | | | | | +| >>>Priority Queue ID | M | | 9.2.1.49C | Shall only refer to a Priority Queue already existing in the old configuration. | – | | +| MAC-hs Reordering Buffer Size for RLC-UM | O | | 9.2.1.38Ab | | – | | +| CQI Feedback Cycle k | O | | 9.2.2.21B | For FDD only | – | | +| CQI Repetition Factor | O | | 9.2.2.4Cb | For FDD only | – | | +| ACK-NACK Repetition Factor | O | | 9.2.2.a | For FDD only | – | | +| CQI Power Offset | O | | 9.2.2.4Ca | For FDD only | – | | +| ACK Power Offset | O | | 9.2.2.b | For FDD only | – | | +| NACK Power Offset | O | | 9.2.2.23a | For FDD only | – | | +| HS-SCCH Power Offset | O | | 9.2.2.18I | For FDD only | – | | +| Measurement Power Offset | O | | 9.2.2.21C | For FDD only | – | | +| HS-SCCH Code Change Grant | O | | 9.2.1.31L | | – | | +| TDD ACK NACK Power Offset | O | | 9.2.3.18F | For TDD only | – | | +| HARQ Preamble Mode | O | | 9.2.2.18a | For FDD only | YES | ignore | +| HS-SICH SIR Target | O | | UL SIR | Applicable to | YES | ignore | + +| | | | | | | | +|--|--|--|-----------|----------------------|--|--| +| | | | 9.2.1.67A | 1.28Mcps TDD
only | | | +|--|--|--|-----------|----------------------|--|--| + +| | | | | | | | +|---------------------------------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| UE Capabilities Information | | 0..1 | | | YES | ignore | +| >HS-DSCH Physical Layer Category | M | | 9.2.1.311a | | – | | +| >1.28 Mcps TDD Uplink Physical Channel Capability | O | | 9.2.3.5Gc | Applicable to 1.28Mcps TDD only | YES | ignore | +| >Number of Supported Carriers | O | | ENUMERATED ( One-one carrier, One-three carrier, Three-three carrier, One-six carrier, Three-six carrier, Six-six carrier, ..., One-Two carrier Discontiguous, Two-Twocarrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous) | Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier(s) the UE can support at the same time, where "x-y carrier" means x for the uplink, and y for the downlink.
One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers. | YES | reject | +| >Multi-carrier HS-DSCH Physical Layer Category | O | | HS-DSCH Physical Layer Category 9.2.1.311a | Applicable to 1.28Mcps TDD only | YES | ignore | +| >MIMO SF Mode Supported For HS-PDSCH dual stream | O | | Enumerated (SF1, SF1/SF16) | Applicable to 1.28Mcps TDD only | YES | ignore | +| >UE TS0 Capability LCR | O | | 9.2.3.110 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| >UE RF Band Capability LCR | C- NofSupportedCarriers | | 9.2.3.125 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| HS-SICH TPC step size | O | | TDD TPC UL Step Size 9.2.3.21a | Applicable to 1.28Mcps TDD only | YES | ignore | +| HS-PDSCH Code Change Grant | O | | 9.2.1.31N | For FDD only | YES | ignore | +| MIMO Mode Indicator | O | | 9.2.1.120 | For FDD and 1.28Mcps TDD only | YES | reject | + +| | | | | | | | +|-------------------------------------------------------------|---|--|----------------------------------------------------------------|----------------------------------------|-----|--------| +| HS-DSCH MAC-d PDU Size Format | O | | 9.2.1.31ID | | YES | reject | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | For FDD only | YES | ignore | +| Enhanced HS Serving CC Abort | O | | ENUMERATED (Abort Enhanced HS Serving CC, ...) | For FDD only | YES | reject | +| UE Support Indicator Extension | O | | 9.2.2.117 | | YES | ignore | +| Single Stream MIMO Mode Indicator | O | | 9.2.2.124 | For FDD only | YES | reject | +| Puncturing Handling in First Rate Matching Stage | O | | 9.2.2.149 | For FDD only | YES | ignore | +| MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.166 | For FDD only | YES | reject | +| Dual Stream MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.168 | For FDD only | YES | reject | +| Multiflow Reconfiguration | O | | 9.2.2.169 | For FDD only | YES | reject | +| CQI Feedback Cycle2 k | O | | CQI Feedback Cycle k2
9.2.2.206 | For FDD only | YES | ignore | +| CQI Cycle Switch Timer | O | | ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity) | For FDD only, refer to TS 25.331 [16]. | YES | ignore | + +| Condition | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NofSupportedCarriers | This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band. | + +| Range Bound | Explanation | +|------------------------------|--------------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | +| maxNrOfPriorityQueues | Maximum number of Priority Queues | +| maxNrOfMACdPDUIndexes | Maximum number of different MAC-d PDU SIDs | + +#### 9.2.1.31HA HS-DSCH Information To Modify Unsynchronised + +The *HS-DSCH Information To Modify Unsynchronised* IE is used for modification of HS-DSCH information in a Node B Communication Context with the Unsynchronised Radio Link Reconfiguration procedure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH MAC-d Flow Specific Information | | 0.. | | | – | | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| Priority Queue Information | | 0.. | | | – | | +| >Priority Queue ID | M | | 9.2.1.49C | | – | | +| >Scheduling Priority Indicator | O | | 9.2.1.53H | | – | | +| >Discard Timer | O | | 9.2.1.24E | | – | | +| >MAC-hs Guaranteed Bit Rate | O | | 9.2.1.38Aa | | – | | +| CQI Power Offset | O | | 9.2.2.4Ca | For FDD only | – | | +| ACK Power Offset | O | | 9.2.2.b | For FDD only | – | | +| NACK Power Offset | O | | 9.2.2.23a | For FDD only | – | | +| HS-SCCH Power Offset | O | | 9.2.2.18I | For FDD only | – | | +| TDD ACK NACK Power Offset | O | | 9.2.3.18F | For TDD only | – | | +| HARQ Preamble Mode | O | | 9.2.2.18a | For FDD only | YES | ignore | +| HS-SICH SIR Target | O | | UL SIR
9.2.1.67A | Applicable to 1.28Mcps TDD only | YES | ignore | +| UE Capabilities Information | | 0..1 | | | YES | ignore | +| >HS-DSCH Physical Layer Category | M | | 9.2.1.31la | | YES | ignore | +| >1.28 Mcps TDD Uplink Physical Channel Capability | O | | 9.2.3.5Gc | Applicable to 1.28Mcps TDD only | YES | ignore | +| >Number of Supported Carriers | O | | ENUMERATED ( One-one carrier, One-three carrier, Three-three carrier, One-six carrier, Three-six carrier, Six-six carrier, ..., One-Two carrier | Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier(s) the UE can support at the same time, where "x-y carrier" means x for the uplink, and y for the downlink.
One-Two carrier | YES | reject | + +| | | | | | | | +|-------------------------------------------------------------|-------------------------|--|----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | Discontiguous, Two-Two carrier
Discontiguous, One-Two carrier
Contiguous, Two-Two carrier
Contiguous) | Discontiguous and Two-Two carrier
Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier
Contiguous and Two-Two carrier
Contiguous mean that the UE is only capable of supporting two adjacent carriers. | | | +| >Multi-carrier HS-DSCH Physical Layer Category | O | | HS-DSCH Physical Layer Category 9.2.1.31la | Applicable to 1.28Mcps TDD only | YES | ignore | +| >MIMO SF Mode Supported For HS-PDSCH dual stream | O | | Enumerated (SF1, SF1/SF16) | Applicable to 1.28Mcps TDD only | YES | ignore | +| >UE TS0 Capability LCR | O | | 9.2.3.110 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| >UE RF Band Capability LCR | C- NofSupportedCarriers | | 9.2.3.125 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| HS-SICH TPC step size | O | | TDD TPC UL Step Size 9.2.3.21a | Applicable to 1.28Mcps TDD only | YES | ignore | +| MIMO Mode Indicator | O | | 9.2.1.120 | For FDD and 1.28Mcps TDD only | YES | reject | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | For FDD only | YES | ignore | +| Enhanced HS Serving CC Abort | O | | ENUMERATED (Abort Enhanced HS Serving CC, ...) | For FDD only | YES | reject | +| UE Support Indicator Extension | O | | 9.2.2.117 | | YES | ignore | +| Single Stream MIMO Mode Indicator | O | | 9.2.2.124 | For FDD only | YES | reject | +| Puncturing Handling in First Rate Matching Stage | O | | 9.2.2.149 | For FDD only | YES | ignore | +| MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.166 | For FDD only | YES | reject | +| Dual Stream MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.168 | For FDD only | YES | reject | +| Multiflow Reconfiguration | O | | 9.2.2.169 | For FDD only | YES | reject | + +| Condition | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NofSupportedCarriers | This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band. | + +| Range Bound | Explanation | +|------------------------------|---------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | +| maxNrOfPriorityQueues | Maximum number of Priority Queues | + +#### 9.2.1.31Ha HS-DSCH Initial Capacity Allocation + +The *HS-DSCH Initial Capacity Allocation* IE provides flow control information for each scheduling priority class for the HS-DSCH FP over Iub. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------------------------------------|---------------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH Initial Capacity Allocation | | 1..< maxNrOfPriorityQueues > | | | – | | +| >Scheduling Priority Indicator | M | | 9.2.1.53H | | – | | +| >Maximum MAC-d PDU Size | M | | MAC-d PDU Size 9.2.1.38A | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >HS-DSCH Initial Window Size | M | | 9.2.1.31Hb | | – | | +| >Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | ignore | + +| Range Bound | Explanation | +|------------------------------|-----------------------------------| +| maxNrOfPriorityQueues | Maximum number of Priority Queues | + +#### 9.2.1.31Hb HS-DSCH Initial Window Size + +Indicates the initial number of MAC-d PDUs (or octets in case *HS-DSCH MAC-d PDU Size Format* = "Flexible MAC-d PDU Size") that may be transmitted before new credits are received from the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-DSCH Initial Window Size | | | INTEGER (1..255) | Number of MAC-d PDUs
If HS-DSCH MAC-d PDU Size Format = "Flexible MAC-d PDU Size" the credit shall be determined in octets:
credit (in octets) = Maximum MAC-d PDU Size Extended * HS-DSCH Initial Window Size | + +#### 9.2.1.31I HS-DSCH MAC-d Flow ID + +HS-DSCH MAC-d Flow ID is the unique identifier for one MAC-d flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| HS-DSCH MAC-d Flow ID | | | INTEGER (0..7) | | + +#### 9.2.1.31IA HS-DSCH MAC-d Flows Information + +The *HS-DSCH MAC-d Flows Information* IE is used for the establishment of HS-DSCH MAC-d flows for a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-----------------------|-----------------------|-----------------------|-------------|----------------------| +| HS-DSCH MAC-d Flow Specific Information | | 1.. | | | – | | + +| | | | | | | | +|-----------------------------------|---|------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | – | | +| >Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| Priority Queue Information | | 1.. | | | – | | +| >Priority Queue ID | M | | 9.2.1.49C | | – | | +| >Associated HS-DSCH MAC-d Flow | M | | HS-DSCH MAC-d Flow ID 9.2.1.31I | The HS-DSCH MAC-d Flow ID shall be one of the flow IDs defined in the HS-DSCH MAC-d Flow Specific Information of this IE. Multiple Priority Queues can be associated with the same HS-DSCH MAC-d Flow ID. | – | | +| >Scheduling Priority Indicator | M | | 9.2.1.53H | | – | | +| >T1 | M | | 9.2.1.56a | | – | | +| >Discard Timer | O | | 9.2.1.24E | | – | | +| >MAC-hs Window Size | M | | 9.2.1.38B | | – | | +| >MAC-hs Guaranteed Bit Rate | O | | 9.2.1.38Aa | | – | | +| >MAC-d PDU Size Index | | 1.. | | | – | | +| >>SID | M | | 9.2.1.53I | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >>MAC-d PDU Size | M | | 9.2.1.38A | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >RLC Mode | M | | 9.2.1.52B | | – | | +| >Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | reject | +| >DL RLC PDU Size Format | O | | 9.2.1.122 | | YES | ignore | +| >UE Aggregate Maximum | O | | NULL | | YES | ignore | + +| | | | | | | | +|--------------------------------|--|--|--|--|--|--| +| Bit Rate Enforcement Indicator | | | | | | | +|--------------------------------|--|--|--|--|--|--| + +| Range Bound | Explanation | +|------------------------------|--------------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | +| maxNrOfPriorityQueues | Maximum number of Priority Queues | +| maxNrOfMACdPDUIndexes | Maximum number of different MAC-d PDU SIDs | + +#### 9.2.1.31IB HS-DSCH MAC-d Flows To Delete + +The *HS-DSCH MAC-d Flows To Delete* IE is used for the removal of HS-DSCH MAC-d flows from a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| HS-DSCH MAC-d Flows To Delete | | 1..< maxNrOfMACdFlows > | | | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | + +| Range Bound | Explanation | +|-------------------------|---------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | + +#### 9.2.1.31IC HS-DSCH MAC-d PDU Size Capability + +This parameter defines the capability for a Local Cell to support different MAC-d PDU Size formats. If this IE is set to "Flexible Size Capable" the Local Cell is "Indexed Size Capable" and "Flexible Size Capable". If this IE has not been configured or has been set to "Indexed Size Capable" the Local Cell is only "Indexed Size Capable". + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|----------------------------------------------------------|-----------------------| +| HS-DSCH MAC-d PDU Size Capability | | | ENUMERATED (Indexed Size Capable, Flexible Size Capable) | | + +#### 9.2.1.31ID HS-DSCH MAC-d PDU Size Format + +The *HS-DSCH MAC-d PDU Size Format* IE provides information about the type of MAC-d PDU Size Format used for HS-DSCH. "Indexed MAC-d PDU Size" uses MAC-d PDU sizes based on *SID* IE and *MAC-d PDU Size* IE of *MAC-d PDU Size Index* IE. "Flexible MAC-d PDU Size" uses a flexible MAC-d PDU size with a maximum PDU size as defined by *Maximum MAC-d PDU Size Extended* IE of *Priority Queue Information* IE. The actual MAC-d PDU size is determined as specified in TS 25.435 [24] and TS 25.321 [32]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|--------------------------------------------------------------|-----------------------| +| HS-DSCH MAC-d PDU Size Format | | | ENUMERATED (Indexed MAC-d PDU Size, Flexible MAC-d PDU Size) | | + +#### 9.2.1.31Ia HS-DSCH Physical Layer Category + +The *HS-DSCH Physical Layer Category* IE defines a set of UE radio access capabilities related to HSDPA, as defined in TS 25.306 [33]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| HS-DSCH Physical Layer Category | | | INTEGER (1..64,...) | | + +#### 9.2.1.31aa HS-DSCH Provided Bit Rate Value + +The *HS-DSCH Provided Bit Rate Value* IE indicates the HS-DSCH Provided Bit Rate as defined in TS 25.321 [32]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-DSCH Provided Bit Rate Value | | | INTEGER
(0..2^24-1, ...,
2^24..1,000,000,000
) | Expressed in bit/s for FDD,
1.28Mcps TDD and 3.84Mcps
TDD.
For 7.68Mcps TDD the value
shall be doubled to give the
value in bit/s. | + +#### 9.2.1.31ib HS-DSCH Provided Bit Rate Value Information + +The *HS-DSCH Provided Bit Rate Value Information* IE reports the *HS-DSCH Provided Bit Rate Value* IE for each priority class. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-----------------------------|-----------------------|-----------------------| +| HS-DSCH Provided Bit Rate Value Information | | 1.. | | | +| >Scheduling Priority Indicator | M | | 9.2.1.53H | | +| >HS-DSCH Provided Bit Rate Value | M | | 9.2.1.31aa | | + +| Range Bound | Explanation | +|------------------------|-------------------------------------------------| +| maxNrOfPriorityClasses | Maximum number of HS-DSCH Scheduling Priorities | + +#### 9.2.1.31ib HS-DSCH Required Power Value + +The *HS-DSCH Required Power Value* IE indicates the minimum necessary power for a given priority class to meet the Guaranteed Bit Rate for all the established HS-DSCH connections belonging to this priority class. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|--------------------------------------------------------| +| HS-DSCH Required Power Value | | | INTEGER (0..1000) | Expressed in thousandths of the max transmission power | + +#### 9.2.1.31ic HS-DSCH Required Power Value Information + +The *HS-DSCH Required Power Value Information* IE reports the *HS-DSCH Required Power Value* IE for each priority class. For each priority class, a list of UEs, identified by the *CRNC Communication Context* IEs, requiring a particularly high amount of power to meet the Guaranteed Bit Rate for their established HS-DSCH connections may be included. Additionally, the *HS-DSCH Required Power Per UE Weight* IE may be included for each of those UEs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| HS-DSCH Required Power Value Information | | 1.. | | | +| >Scheduling Priority Indicator | M | | 9.2.1.153H | | +| >HS-DSCH Required Power Value | M | | 9.2.1.31Iba | | +| >HS-DSCH Required Power Per UE Information | | 0.. | | List of UEs with Guaranteed Bit Rate indicating their required power consumption relative to the HS-DSCH Required Power Value. | +| >>CRNC Communication Context ID | M | | 9.2.1.18 | The reserved value "All CRNCCC" shall not be used. | +| >>HS-DSCH Required Power Per UE Weight | O | | INTEGER (0..100) | Expressed in percentage of the value provided in the HS-DSCH Required Power Value IE | + +| Range Bound | Explanation | +|--------------------------------|------------------------------------------------------------------------| +| maxNrOfContextsOnUeList | Maximum number of Communication Contexts to include in the list of UEs | +| maxNrOfPriorityClasses | Maximum number of HS-DSCH Scheduling Priorities | + +#### 9.2.1.31J HS-DSCH RNTI + +The HS-DSCH RNTI is used for the UE-specific CRC in HS-SCCH and HS-DSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| HS-DSCH RNTI | | | INTEGER (0..65535) | | + +#### 9.2.1.31K HS-SCCH Code Change Indicator + +The HS-SCCH Code Change Indicator indicates whether the HS-SCCH Code change is needed or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------------------------|-----------------------| +| HS-SCCH Code Change Indicator | | | ENUMERATED (HS-SCCH Code Change needed) | | + +#### 9.2.1.31L HS-SCCH Code Change Grant + +The *HS-SCCH Code Change Grant* IE indicates that modification of HS-SCCH Codes is granted. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------------|-----------------------| +| HS-SCCH Code Change Grant | | | ENUMERATED (Change Granted) | | + +#### 9.2.1.31M HS-PDSCH Code Change Indicator [FDD] + +The HS-PDSCH Code Change Indicator indicates whether the HS-PDSCH Code change is needed or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|------------------------------------------|-----------------------| +| HS-PDSCH Code Change Indicator | | | ENUMERATED (HS-PDSCH Code Change needed) | | + +#### 9.2.1.31N HS-PDSCH Code Change Grant [FDD] + +The *HS-PDSCH Code Change Grant* IE indicates that modification of HS-PDSCH Codes is granted. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------------|-----------------------| +| HS-PDSCH Code Change Grant | | | ENUMERATED (Change Granted) | | + +#### 9.2.1.32 IB\_SG\_DATA + +Segment as defined in ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------| +| IB_SG_DATA | | | BIT STRING | Contains "SIB data fixed" or "SIB data variable" in segment as encoded in ref. TS 25.331 [18].
See Annex D | + +#### 9.2.1.33 IB\_SG\_POS + +The lowest position of a specific Information Block segment in the SFN cycle ( $IB\_SG\_POS < IB\_SG\_REP$ ). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------| +| IB_SG_POS | | | INTEGER (0..4094) | Only even positions are allowed.
See ref. TS 25.331 [18] | + +#### 9.2.1.34 IB\_SG\_REP + +Repetition distance for an Information Block segment. The segment shall be transmitted when $SFN \bmod IB\_SG\_REP = IB\_SG\_POS$ . + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------------|------------------------------------------------| +| IB_SG_REP | | | ENUMERATED (4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096) | Repetition period for the IB segment in frames | + +#### 9.2.1.35 IB Type + +The IB Type identifies a specific system information block. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| IB Type | | | ENUMERATED (
MIB,
SB1,
SB2,
SIB1,
SIB2,
SIB3,
SIB4,
SIB5,
SIB6,
SIB7,
not-Used-SIB8,
not-Used-SIB9,
not-Used-SIB10,
SIB11,
SIB12,
SIB13,
SIB13.1,
SIB13.2,
SIB13.3,
SIB13.4,
SIB14,
SIB15,
SIB15.1,
SIB15.2,
SIB15.3,
SIB16,
...,
SIB17,
SIB15.4,
SIB18,
SIB15.5,
SIB5bis,
SIB11bis,
SIB15bis,
SIB15.1bis,
SIB15.2bis,
SIB15.3bis,
SIB15.6,
SIB15.7,
SIB15.8,
SIB15.2ter,
SIB19,
not-Applicable-
SIB20,
SIB21,
SIB22,
SIB15.1ter,
SB3,
SIB23,
SIB24,
SIB11ter,
SIB25
) | | + +#### 9.2.1.36 Indication Type + +Void. + +##### 9.2.1.36A Information Exchange Object Type + +Void. + +##### 9.2.1.36B Information Report Characteristics + +The information report characteristics defines how the reporting shall be performed. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------| +| CHOICE Information Report Characteristics Type | M | | | | +| >On Demand | | | NULL | | +| >Periodic | | | | | +| >>CHOICE Information Report Periodicity Scale | M | | | The frequency with which the Node B shall send information reports. | +| >>>minute | | | | | +| >>>>Report Periodicity Value | M | | INTEGER (1..60,...) | Unit: min | +| >>>hour | | | | | +| >>>>Report Periodicity Value | M | | INTEGER (1..24,...) | Unit: h | +| >On Modification | | | | | +| >>Information Threshold | O | | 9.2.1.36E | | + +#### 9.2.1.36C Information Exchange ID + +The Information Exchange ID uniquely identifies any requested information per Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Information Exchange ID | M | | INTEGER (0..2^20-1) | | + +#### 9.2.1.36D Information Type + +The Information Type indicates which kind of information the Node B shall provide. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------|----------------------| +| Information Type Item | M | | ENUMERATE
D (
GPS
Information,
DGPS
Corrections,
GPS RX Pos,
...,
GANSS
Information,
DGANSS
Corrections,
GANSS RX
Pos) | | – | | +| GPS Information | C-GPS | 0..GPSItems> | | | – | | +| >GPS Information
Item | | | ENUMERATE
D (
GPS
Navigation
Model & Time
Recovery,
GPS
Ionospheric
Model,
GPS UTC
Model,
GPS Almanac,
GPS Real-
Time Integrity,
...) | | – | | +| GANSS Information | C-GANSS | 1 | | | YES | ignore | +| > GANSS Common
Data | | 0..1 | | | – | | +| >>Ionospheric
Model | O | | BOOLEAN | True means
requested | – | | +| >>Additional
Ionospheric Model | O | | Additional
Ionospheric
Model
Request
9.2.1.107d | Presence
means
requested. | YES | ignore | +| >>Earth Orientation
Parameters | O | | Earth
Orientation
Parameters
Request
9.2.1.107e | | YES | ignore | +| > GANSS Generic
Data | | 0..GANSS> | | | – | | +| >>GANSS ID | O | | 9.2.1.104 | | – | | +| >>GANSS
Navigation Model
And Time Recovery | O | | BOOLEAN | True means
requested | – | | + +| | | | | | | | +|----------------------------------------------|---|-------------------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--| +| >>GANSS Time Model GNSS-GNSS | O | | BIT STRING (SIZE(9)) | Defines the time model required.

Bit 1 is the MSB and bit 9 is the LSB (see section 9.2.0).

Bit 1:GPS,
Bit 2:Galileo,
Bit 3:QZSS,
Bit 4: GLONASS,
Bit 5: BDS.

Other bits are reserved. | — | | +| >>GANSS UTC Model | O | | BOOLEAN | True means requested | — | | +| >>GANSS Almanac | O | | BOOLEAN | True means requested | — | | +| >>GANSS Real Time Integrity | O | | BOOLEAN | True means requested | — | | +| >>GANSS Data Bit Assistance | | 0..1 | | | — | | +| >>>GANSS TOD | M | | INTEGER (0..86399) | The GANSS Time Of Day for which the data bits are requested | — | | +| >>>Data Bit Assistance | | 1 | | | — | | +| >>>>DGANSS Signal ID | M | | BIT STRING (SIZE(8)) | Defined in TS 25.331 [18] | — | | +| >>>>GANSS Data Bit Interval | M | | INTEGER (0..15) | Defined in TS 25.331 [18] | — | | +| >>>>Satellite Information | | 0..<maxGANSSSat> | | | — | | + +| | | | | | | | +|--------------------------------------------------------|---------------------------------|------|-------------------------------------------------------------------------|---------------------------------------------------------|-----|--------| +| >>>>Sat ID | M | | INTEGER(0..63) | Identifies the satellite and is equal to (SV ID No - 1) | – | | +| >>GANSS Additional Navigation Models And Time Recovery | O | | GANSS Additional Navigation Models And Time Recovery Request 9.2.1.107f | | YES | ignore | +| >>GANSS Additional UTC Models | O | | GANSS Additional UTC Models Request 9.2.1.107g | | YES | ignore | +| >>GANSS Auxiliary Information | O | | GANSS Auxiliary Information Request 9.2.1.107h | | YES | ignore | +| >>SBAS ID | C-
GANSS-
ID | | 9.2.1.107b | | YES | ignore | +| >>DBDS Corrections Request | | 0..1 | | | – | | +| >>>DGANSS Signal ID | M | | BIT STRING (SIZE(8)) | Defined in TS 25.331 [18] | – | | +| >>BDS Ionospheric Grid Model Request | O | | ENUMERATE D (requested, ...) | | YES | ignore | +| DGANSS Corrections Req | C-
DGANSS
Correction
s | 1 | | | YES | ignore | +| >DGANSS Signal ID | M | | BIT STRING (SIZE(8)) | Defined in TS 25.331 [18] | – | | +| >GANSS ID | O | | 9.2.1.104 | | – | | + +| Condition | Explanation | +|--------------------------|-----------------------------------------------------------------------------------------------| +| DGANSSCorrections | The IE shall be present if the Information Type Item IE indicates "DGANSS Corrections". | +| GPS | The IE shall be present if the Information Type Item IE indicates "GPS Information". | +| GANSS | The IE shall be present if the Information Type Item IE indicates "GANSS Information". | +| GANSS-ID | This IE shall be present if the GANSS ID IE indicates "SBAS". | + +| Range Bound | Explanation | +|----------------------|-------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in the IE | +| maxNoGPSItems | Maximum number of GPS Information Items supported in one Information Exchange | +| maxNoGANSS | Maximum number of GANSS Systems | + +#### 9.2.1.36E Information Threshold + +The Information Threshold indicates which kind of information shall trigger the Information Reporting procedure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-------------------------------|------------------------------------------------------------------------------------------| +| CHOICE Information Type Item | M | | | | +| >DGPS | | | | | +| >>PRC Deviation | M | | ENUMERATED (1, 2, 5, 10, ...) | PRC deviation in meters from the previously reported value, which shall trigger a report | +| >DGANSS | | | | | +| >>PRC Deviation | M | | ENUMERATED (1, 2, 5, 10, ...) | PRC deviation in meters from the previously reported value, which shall trigger a report | + +#### 9.2.1.36F IPDL Indicator + +Indicates if IPDL periods shall be active or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------------|-----------------------| +| IPDL Indicator | | | ENUMERATED (active, inactive) | | + +#### 9.2.1.37 Limited Power Increase + +Void. + +#### 9.2.1.37A Local Cell Group ID + +The Local Cell Group ID represents resources in the Node B, which have been pooled from a capacity point of view. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------|-----------------------| +| Local Cell Group ID | | | Local Cell ID 9.2.1.38 | | + +#### 9.2.1.38 Local Cell ID + +The local cell ID represents resources in the Node B that can be used for the configuration of a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------|-----------------------| +| Local Cell ID | | | INTEGER (0...268435455) | | + +#### 9.2.1.38A MAC-d PDU Size + +The *MAC-d PDU Size* provides the size in bits of the MAC-d PDU. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|---------------------------------------------------------------------------| +| MAC-d PDU Size | | | INTEGER (1..5000,...) | In case of E-DCH, value 8 and values not multiple of 8 shall not be used. | + +#### 9.2.1.38Aa MAC-hs Guaranteed Bit Rate + +The *MAC-hs Guaranteed Bit Rate* IE indicates the guaranteed number of bits per second that Node B should deliver over the air interface under normal operating conditions (provided there is data to deliver). If the *MAC-hs Guaranteed Bit Rate* IE is received with the value set to 0 during RL set up or modification, no guarantee is applied. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------------------------------------|-----------------------| +| MAC-hs Guaranteed Bit Rate | | | INTEGER
(0..2^24-1, ...,
2^24..1,000,000,000
) | Unit: bit/s | + +#### 9.2.1.38Ab MAC-hs Reordering Buffer Size for RLC-UM + +The *MAC-hs Reordering Buffer Size for RLC-UM* IE indicates the portion of the buffer in the UE that can be used for RLC-UM traffic (i.e. for Priority Queues whose *RLC Mode* IE is set to "RLC-UM"). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| MAC-hs Reordering Buffer Size | | | INTEGER
(0..300,...) | Unit: kBytes
And N kBytes = N*1024 Bytes.
The Node B shall use this value to avoid the overflow of the MAC-hs reordering buffer. | + +#### 9.2.1.38Ac MAC-hs Reset Indicator + +The *MAC-hs Reset Indicator* IE indicates that a reset of the MAC-hs is not required. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-------------------------------------|-----------------------| +| MAC-hs Reset Indicator | | | ENUMERATED
(MAC-hs
Not Reset) | | + +#### 9.2.1.38B MAC-hs Window Size + +The *MAC-hs Window Size* IE is used for MAC-hs/MAC-ehs PDU retransmission as defined in TS 25.321 [32]. [FDD - the values 64, 128 and 256 is only allowed when the MAC header type is MAC-ehs and under conditions defined in TS 25.321 [32].] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| MAC-hs Window Size | | | ENUMERATED (4, 6, 8, 12, 16, 24, 32, ..., 64, 128, 256) | For 1.28Mcps TDD when TSN length is configured to 9bits, ENUMERATED (32, 64, 96, 128, 160, 192, 256,...) | + +#### 9.2.1.38C MAC PDU Size Extended + +The *MAC PDU Size Extended* IE provides the size in octets of the MAC level PDU when an extended MAC level PDU size is required. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-------------------------------|---------------------------------------------| +| MAC PDU Size Extended | | | INTEGER
(1..1504,...,1505) | In case of E-DCH, value 1 shall not be used | + +#### 9.2.1.39 Maximum DL Power Capability + +This parameter indicates the maximum DL power capability for a local cell or a Power Local Cell Group within the Node B. The reference point is the antenna connector. If Transmit Diversity can be used in the local cell, the parameter indicates the maximum for the linear sum of the power that can be used on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------------------------------| +| Maximum DL Power Capability | | | INTEGER (0..500) | Unit: dBm
Range: 0..50 dBm
Step: 0.1 dB | + +#### 9.2.1.40 Maximum Transmission Power + +The Maximum Transmission Power is the maximum value for the linear sum of the power of all downlink physical channels, that is allowed to be used in a cell. If Transmit Diversity is applied to one downlink physical channel, the power to be considered for this downlink physical channel is the linear sum of the power used for this downlink physical channel on all branches. [1.28Mcps TDD - For a multi-frequency cell, the Maximum Transmission Power is the maximum value for the linear sum of the power of all downlink physical channels, that is allowed to be used on one frequency in a cell.] The reference point is the antenna connector. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-------------------------------------------| +| Maximum Transmission Power | | | INTEGER (0..500) | Unit: dBm
Range: 0..50
Step: 0.1 dB | + +#### 9.2.1.40A Measurement Availability Indicator + +Void. + +##### 9.2.1.40B Measurement Change Time + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|------------------------------------------------| +| CHOICE Time Scale | M | | | | +| >millisecond | | | | | +| >>Measurement Change Time Value | M | | INTEGER (1..6000,...) | Unit: ms
Range: 10..60000 ms
Step: 10 ms | + +#### 9.2.1.41 Measurement Filter Coefficient + +The Measurement Filter Coefficient determines the amount of filtering to be applied for measurements. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------------------------------------------------------------|-----------------------| +| Measurement Filter Coefficient | | | ENUMERATED (
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 11, 13, 15, 17,
19,...) | | + +#### 9.2.1.41A Measurement Hysteresis Time + +The Measurement Hysteresis Time provides the duration during which a reporting criterion has to be fulfilled for the Measurement Reporting procedure to be triggered. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|--------------------------|------------------------------------------------| +| CHOICE Time Scale | M | | | | +| >millisecond | | | | | +| >>Measurement Hysteresis Time Value | M | | INTEGER
(1..6000,...) | Unit: ms
Range: 10..60000 ms
Step: 10 ms | + +#### 9.2.1.42 Measurement ID + +The Measurement ID uniquely identifies any measurement per (Node B or Communication) Control Port. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|------------------------|-----------------------| +| Measurement ID | | | INTEGER
(0..2^20-1) | | + +#### 9.2.1.43 Measurement Increase/Decrease Threshold + +The Measurement Increase/Decrease Threshold defines the threshold that shall trigger Event C or D. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Measurement Increase/Decrease Threshold | M | | | | – | | +| >Received Total Wide Band Power | | | | | | | +| >>Received Total Wide Band Power | M | | INTEGER (0..620) | Unit: dB
Range: 0..62 dB
Step: 0.1 dB | – | | +| >Transmitted Carrier Power | | | | | | | +| >>Transmitted Carrier Power | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| >Acknowledged PRACH Preambles | | | | FDD only | | | +| >>Acknowledged PRACH Preambles | M | | INTEGER (0..240,...) | According to mapping in TS 25.133 [22] | – | | +| >UL Timeslot ISCP | | | | TDD only | | | +| >>UL Timeslot ISCP | M | | INTEGER (0..126) | Unit: dB
Range: 0..63 dB
Step: 0.5 dB | – | | +| >SIR | | | | | | | +| >>SIR | M | | INTEGER (0..62) | Unit: dB
Range: 0..31 dB
Step: 0.5 dB | – | | +| >SIR Error | | | | FDD only | | | +| >>SIR Error | M | | INTEGER (0..124) | Unit: dB
Range: 0..62 dB
Step: 0.5 dB | – | | +| >Transmitted Code Power | | | | | | | +| >>Transmitted Code Power | M | | INTEGER (0..112,...) | Unit: dB
Range: 0..56 dB
Step: 0.5 dB | – | | +| >RSCP | | | | TDD only | | | +| >>RSCP | M | | INTEGER (0..126) | Unit: dB
Range: 0..63 dB
Step: 0.5 dB | – | | +| >Round Trip Time | | | | FDD only | | | +| >>Round Trip Time | M | | INTEGER (0..32766) | Unit: chips
Range: 0 .. 2047.875 chips
Step: 0.625 chips | – | | +| >Not Used 1 | | | NULL | This choice shall not be used. Reject procedure if received. | | | +| >Not Used 2 | | | NULL | This choice shall not be used. Reject procedure if received. | | | +| >Additional Measurement Thresholds | | | | See Note 1. | | | +| >>Transmitted Carrier Power Of All Codes Not Used For HSTransmission | | | | | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, | YES | reject | + +| | | | | | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | E-AGCH, E-RGCH or E-HICHTransmission" and mapping in TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission" | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +| | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Transmitted
Carrier Power For
Cell Portion | | | | FDD and 1.28Mcps
TDD only | | | +| >>>Transmitted
Carrier Power For
Cell Portion | M | | INTEGER
(0..100) | Mapping identical to
the one for
Transmitted Carrier
Power measurement
in TS 25.133 [22] and
TS 25.123 [23] | YES | reject | +| >>Received Total
Wide Band Power
For Cell Portion | | | | FDD and 1.28Mcps
TDD only | | | +| >>>Received
Total Wide Band
Power For Cell
Portion | M | | INTEGER
(0..620) | Unit: dB
Range: 0..62 dB
Step: 0.1 dB | YES | reject | +| >>Transmitted
Carrier Power Of
All Codes Not Used
For HS-PDSCH,
HS-SCCH, E-
AGCH, E-RGCH or
E-HICH
Transmission For
Cell Portion | | | | FDD only | | | +| >>>Transmitted
Carrier Power Of
All Codes Not
Used For HS-
PDSCH, HS-
SCCH, E-AGCH,
E-RGCH or E-
HICH
Transmission For
Cell Portion | M | | INTEGER
(0..100) | Mapping identical to
the one for
Transmitted Carrier
Power Of All Codes
Not Used For HS-
PDSCH, HS-SCCH,
E-AGCH, E-RGCH or
E-HICH Transmission
measurement in TS
25.133 [22] | YES | reject | +| >>UpPCH
interference | | | | 1.28Mcps TDD Only | | | +| >>>UpPCH
interference Value | M | | INTEGER
(0..127,...) | According to mapping
in TS 25.123 [23] | YES | reject | +| >>Received
Scheduled E-
DCH Power
Share | | | | FDD only | | | +| >>>RSEPS value | M | | INTEGER
(0..151) | According to mapping
in TS 25.133 [22] | YES | reject | +| >>Received
Scheduled E-DCH
Power Share For
Cell Portion | | | | FDD only | | | +| >>>RSEPS value | M | | INTEGER
(0..151) | According to mapping
in TS 25.133 [22] | YES | reject | +| >>E-DCH RACH
Report | | | | FDD only | | | +| >>> Denied E-
DCH RACH
Resources | M | | INTEGER
(0..240,...) | According to mapping
in TS 25.302 [25] | YES | reject | +| >>>2ms
Overridden E-
DCH RACH
Resources | O | | INTEGER
(0..240,...) | According to mapping
in TS 25.302 [25]. | YES | ignore | +| >>>2ms Denied
E-DCH RACH
Resources | O | | INTEGER
(0..240,...) | According to mapping
in TS 25.302 [25]. | YES | ignore | +| >>Transmitted
Carrier Power Of
All Codes Not Used
For HS-PDSCH,
HS-SCCH, E- | | | | 1.28Mcps TDD only | | | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| AGCH, or E-HICH Transmission For Cell Portion | | | | | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion | M | | INTEGER (0..100) | Mapping identical to the one for Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission measurement in TS 25.123 [23] | YES | reject | +| >> UL Timeslot ISCP For Cell Portion | | | | 1.28Mcps TDD only | | | +| >>>UL Timeslot ISCP for Cell Portion | M | | INTEGER (0..126) | Unit: dB
Range: 0..63 dB
Step: 0.5 dB | YES | reject | +| >> UpPCH interference For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>>UpPCH interference Value for Cell Portion | M | | INTEGER (0..127,...) | According to mapping in TS 25.123 [23] | YES | reject | +| Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. | | | | | | | + +##### 9.2.1.43A Measurement Recovery Behavior + +This IE controls the Measurement Recovery Behavior. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|-----------------------| +| Measurement Recovery Behavior | | | NULL | | + +#### 9.2.1.43B Measurement Recovery Reporting Indicator + +This IE indicates the Measurement Recovery Reporting. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|-------|-----------------------|-----------------------| +| Measurement Recovery Reporting Indicator | | | NULL | | + +#### 9.2.1.43C Measurement Recovery Support Indicator + +This IE indicates the Measurement Recovery Support. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|-----------------------| +| Measurement Recovery Support Indicator | | | NULL | | + +#### 9.2.1.44 Measurement Threshold + +The Measurement Threshold defines which threshold that shall trigger Event A, B, E, F or On Modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------|-------------|----------------------| +| CHOICE Measurement Threshold | M | | | | – | | +| > Received Total Wide Band Power | | | | | | | +| >> Received Total Wide Band Power | M | | INTEGER (0..621) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > Transmitted Carrier Power | | | | | | | +| >> Transmitted Carrier Power | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > Acknowledged PRACH Preambles | | | | FDD only | | | +| >> Acknowledged PRACH Preambles | M | | INTEGER (0..240,...) | According to mapping in TS 25.133 [22] | – | | +| > UL Timeslot ISCP | | | | TDD only | | | +| >> UL Timeslot ISCP | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | – | | +| > SIR | | | | | | | +| >> SIR | M | | INTEGER (0..63) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > SIR Error | | | | FDD only | | | +| >> SIR Error | M | | INTEGER (0..125) | According to mapping in TS 25.133 [22] | – | | +| > Transmitted Code Power | | | | | | | +| >> Transmitted Code Power | M | | INTEGER (0..127) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | – | | +| > RSCP | | | | TDD only | | | +| >> RSCP | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | – | | +| > Rx Timing Deviation | | | | Applicable to 3.84Mcps TDD only | | | +| >> Rx Timing Deviation | M | | INTEGER (0..8191) | According to mapping in TS 25.123 [23] | – | | +| > Round Trip Time | | | | FDD only | | | +| >> Round Trip Time | M | | INTEGER (0..32767) | According to mapping in TS 25.133 [22] | – | | +| > Not Used 1 | | | NULL | This choice shall not be used. Reject procedure if received. | | | +| > Not Used 2 | | | NULL | This choice shall not be used. Reject procedure if received. | | | +| > Additional Measurement Thresholds | | | | See Note 1. | | | +| >> UTRAN GPS Timing Of Cell Frames For UE Positioning | | | | | – | | +| >>> UTRAN-GPS Measurement Threshold Information | M | | 9.2.1.64B | | YES | reject | +| >> SFN-SFN Observed Time Difference | | | | | | | +| >>> SFN-SFN Measurement Threshold Information | M | | 9.2.1.53C | | YES | reject | + +| | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|---|--|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Rx Timing Deviation LCR | | | | Applicable to 1.28Mcps TDD Only | | | +| >>>Rx Timing Deviation LCR | M | | INTEGER (0..511) | According to mapping in TS 25.123 [23] | YES | reject | +| >>HS-SICH Reception Quality | | | | Applicable to TDD Only | | | +| >>>HS-SICH Reception Quality | M | | INTEGER (0..20) | According to mapping in TS 25.123 [23] | YES | reject | +| >>Transmitted Carrier Power Of All Codes Not Used For HSTransmission | | | | | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission | M | | INTEGER (0..100) | According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICHTransmission" and TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission" | YES | reject | +| >>HS-DSCH Required Power | | | | | | | +| >>>HS-DSCH Required Power Value | M | | 9.2.1.31lba | | YES | reject | +| >>Transmitted Carrier Power For Cell Portion | | | | FDD and 1.28Mcps TDD only | | | +| >>>Transmitted Carrier Power For Cell Portion | M | | INTEGER (0..100) | Mapping identical to the one for Transmitted Carrier Power measurement in TS 25.133 [22] and TS 25.123 [23] | YES | reject | +| >>Received Total Wide Band Power For Cell Portion | | | | FDD and 1.28Mcps TDD only | | | +| >>>Received Total Wide Band Power For Cell Portion | M | | INTEGER (0..621) | Mapping identical to the one for Received Total Wide Band Power measurement in TS 25.133 [22] and TS 25.123 [23] | YES | reject | +| >>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion | | | | FDD only | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E- | M | | INTEGER (0..100) | Mapping identical to the one for Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or | YES | reject | + +| | | | | | | | +|---------------------------------------------------------|---|--|------------------------------------------|--------------------------------------------------------------------------------------------------------|-----|--------| +| HICH Transmission Value For Cell Portion | | | | E-HICH Transmission measurement in TS 25.133 [22] | | | +| >>UpPCH interference | | | | 1.28Mcps TDD Only | | | +| >>>UpPCH interference Value | M | | INTEGER (0..127,...) | According to mapping in TS 25.123 [23] | YES | reject | +| >>DL Transmission Branch Load | | | | FDD Only | | | +| >>>DL Transmission Branch Load Value | M | | INTEGER (0..101,...) | According to mapping in TS 25.133 [22] | YES | reject | +| >>HS-DSCH Required Power For Cell Portion | | | | FDD and 1.28Mcps TDD only | | | +| >>>HS-DSCH Required Power Value For Cell Portion | M | | HS-DSCH Required Power Value 9.2.1.31lba | | YES | reject | +| >>E-DCH Non-serving Relative Grant Down Commands | | | | FDD only | | | +| >>>E-DCH Non-serving Relative Grant Down Commands Value | M | | INTEGER (0..100,...) | Down Commands per second | YES | reject | +| >>Rx Timing Deviation 768 | | | | Applicable to 7.68Mcps TDD Only | | | +| >>>Rx Timing Deviation 768 | M | | INTEGER (0..65535) | According to mapping in TS 25.123 [23] | YES | reject | +| >>Rx Timing Deviation 384 Extended | | | | Applicable to 3.84Mcps TDD Only | | | +| >>>Rx Timing Deviation 384 Extended | M | | INTEGER (0..32767) | According to mapping in TS 25.123 [23] | YES | reject | +| >>Extended Round Trip Time | | | | FDD only | | | +| >>>Extended Round Trip Time Value | M | | INTEGER (32767..103041) | Continuation of intervals with step size as defined in TS 25.133 [22]. | YES | reject | +| >>Received Scheduled E-DCH Power Share | | | | FDD only | | | +| >>>RSEPS value | M | | INTEGER (0..151) | According to mapping in TS 25.133 [22] | YES | reject | +| >>Received Scheduled E-DCH Power Share for Cell Portion | | | | FDD only | | | +| >>>RSEPS value | M | | INTEGER (0..151) | According to mapping in TS 25.133 [22] | YES | reject | +| >>Additional HS-SICH Reception Quality | | | | Applicable to 1.28Mcps TDD Only | | | +| >>>HS-SICH Reception Quality LCR | M | | INTEGER (0..20) | According to mapping in TS 25.123 [23] used when the Measurement Threshold Value for HS-SICH Reception | YES | reject | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | Quality are more than 20, Measurement Threshold Value = 20 + IE Value | | | +| >>UTRAN GANSS Timing Of Cell Frames For UE Positioning | | | | | | | +| >>>T UTRAN-GANSS Measurement Threshold Information | M | | 9.2.1.99 | | YES | reject | +| >> E-DCH RACH Report | | | | FDD only | | | +| >>> Denied E-DCH RACH Resources | M | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25] | YES | reject | +| >>>2ms Overridden E-DCH RACH Resources | O | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25] | YES | ignore | +| >>>2ms Denied E-DCH RACH Resources | O | | INTEGER (0..240,...) | According to mapping in TS 25.302 [25] | YES | ignore | +| >>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion | | | | 1.28Mcps TDD only | | | +| >>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion | M | | INTEGER (0..100) | Mapping identical to the one for Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission measurement in TS 25.123 [23] | YES | reject | +| >> UL Timeslot ISCP For Cell Portion | | | | 1.28Mcps TDD only | | | +| >>>UL Timeslot ISCP for Cell Portion | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | YES | reject | +| >> UpPCH interference For Cell Portion | | | | 1.28Mcps TDD Only | | | +| >>>UpPCH interference Value for Cell Portion | M | | INTEGER (0..127,...) | According to mapping in TS 25.123 [23] | YES | reject | +| >>UE transmission power headroom | | | | | | | +| >>>UE transmission power headroom | M | | INTEGER (0..31) | According to mapping in TS 25.133 [22] and TS 25.123 [23]. | YES | reject | +| Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. | | | | | | | + +#### 9.2.1.45 Message Discriminator + +This field is used to discriminate between Dedicated NBAP and Common NBAP messages. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|---------------------------------|-----------------------| +| Message Discriminator | | | ENUMERATED ( Common, Dedicated) | | + +#### 9.2.1.45A Message Structure + +The *Message Structure* IE gives information for each level with assigned criticality in an hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the *Information Element Criticality Diagnostics* IE). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|--------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Structure | | 1.. | | The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message. | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of this level's IE containing the not understood or missing IE. | +| >Repetition Number | O | | INTEGER (1..256) |

The Repetition Number IE gives, if applicable, the number of occurrences of this level's reported IE up to and including the occurrence containing the not understood or missing IE.

Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.

| + +| Range Bound | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| maxNrOfLevels | Maximum number of message levels to report. The value for maxNrOfLevels is 256. | + +#### 9.2.1.46 Message Type + +The *Message Type* uniquely identifies the message being sent. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-------------------------------------------------------------------------------------|---------------------------------| +| Procedure ID | M | 1 | | | +| >Procedure Code | M | | INTEGER (0..255) | | +| >Ddmode | M | | ENUMERATED ( TDD, FDD, Common, ...) | Common = common to FDD and TDD. | +| Type of Message | M | | ENUMERATED ( Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome) | | + +#### 9.2.1.46a MICH CFN + +The MICH CFN indicates the Connection Frame Number for the MICH. It corresponds to the Cell SFN of the frame in which the start of the S-CCPCH frame is located, see ref TS 25.211 [7]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| MICH CFN | | | INTEGER (0..4095) | | + +#### 9.2.1.46A Minimum DL Power Capability + +This parameter indicates the minimum DL power capability for a local cell within the Node B. The reference point is the antenna connector. If Transmit Diversity can be used in the local cell, the parameter indicates the minimum for the linear sum of the power that can be used on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|----------------------------------------------------| +| Minimum DL Power Capability | | | INTEGER (0..800) | Unit: dBm
Range: -30 .. +50 dBm
Step: 0.1 dB | + +#### 9.2.1.47 Minimum Spreading Factor + +This parameter indicates the minimum spreading factor supported at a cell within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|----------------------------------------------|----------------------------------------------------------------------------------------------------| +| Minimum Spreading Factor | | | ENUMERATED (4, 8, 16, 32, 64, 128, 256, 512) | [TDD - Mapping scheme for the minimum spreading factor 1 and 2:
"256" means 1
"512" means 2] | + +#### 9.2.1.47a Modification Period + +The Modification Period of the MICH, see ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------|-----------------------| +| Modification Period | | | ENUMERATED (1280, 2560, 5120, 10240,...) | Unit: ms | + +#### 9.2.1.47A N\_INSYNC\_IND + +This parameter is used by the Node B for achievement/re-achievement of UL synchronisation on the Uu interface as defined in ref. TS 25.214 [10] and TS 25.224 [21]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| N_INSYNC_IND | | | INTEGER (1..256) | | + +#### 9.2.1.47B N\_OUTSYNC\_IND + +This parameter defines the number of consecutive out-of-sync indications after which the timer T\_RLFAILURE shall be started (see also ref. TS 25.214 [10] and TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| N_OUTSYNC_IND | | | INTEGER (1..256) | | + +#### 9.2.1.47C Neighbouring FDD Cell Measurement Information + +This IE provides information on the FDD neighbouring cells used for the purpose of measurements. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|------------------------------------| +| UC-Id | M | | 9.2.1.65B | | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nd (TS 25.104 [14]) | +| Primary Scrambling Code | M | | 9.2.2.34 | | + +#### 9.2.1.47D Neighbouring TDD Cell Measurement Information + +This IE provides information on the 3.84Mcps TDD neighbouring cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the *Time Slot* IE and *Midamble Shift And Burst Type* IE shall be included if available. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|-------------------------------------| +| UC-Id | M | | 9.2.1.65B | | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | +| Cell Parameter ID | M | | 9.2.3.4 | | +| Time Slot | O | | 9.2.3.23 | | +| Midamble Shift And Burst Type | O | | 9.2.3.7 | | + +#### 9.2.1.47E Neighbouring TDD Cell Measurement Information LCR + +This IE provides information on the neighbouring 1.28Mcps TDD cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the *Time Slot LCR* IE and *Midamble Shift LCR* IE shall be included if available. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-------------------------------------| +| UC-Id | M | | 9.2.1.65B | | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | +| Cell Parameter ID | M | | 9.2.3.4 | | +| Time Slot LCR | O | | 9.2.3.24A | | +| Midamble Shift LCR | O | | 9.2.3.7A | | + +#### 9.2.1.47F NI + +The *NI* IE provides a Notification Indicator determined as specified in TS 25.304 [37]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| NI | | | INTEGER (0..65535) | | + +#### 9.2.1.48 Node B Communication Context ID + +The Node B Communication Context ID is the identifier of the Communication Context in the Node B, it corresponds to the dedicated resources which are necessary for an UE using one or more dedicated channels in a given Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Node B Communication Context ID | | | INTEGER (0..2 20 -1) | "2 20 -1" is a reserved value indicating all the existing and future Node B Communication Contexts that can be reached by the Communication Control Port (All NBCC). | + +#### 9.2.1.49 Payload CRC Presence Indicator + +This parameter indicates whether FP payload 16 bit CRC is used or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|---------------------------------------------------|-----------------------| +| Payload CRC Presence Indicator | | | ENUMERATED ( CRC Included, CRC Not Included, ...) | | + +#### 9.2.1.49A PICH Power + +The *PICH Power* IE indicates a power level relative to the [FDD - Primary CPICH power] [TDD - Primary CCPCH power] configured in a cell. If Transmit Diversity is applied to the PICH (resp. the MICH), the *PICH Power* IE indicates the power offset between the linear sum of the power for the PICH (resp. the MICH) on all branches and the [FDD - Primary CPICH power] [TDD - Primary CCPCH power] configured in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|----------------------------------------------| +| PICH Power | | | INTEGER (-10..+5) | Unit: dB
Range: -10 .. +5 dB
Step: 1dB | + +#### 9.2.1.49B Power Local Cell Group ID + +The Power Local Cell Group ID represents resources in the Node B which have been pooled from a DL power capability point of view. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|------------------------|-----------------------| +| Power Local Cell Group ID | | | Local Cell ID 9.2.1.38 | | + +#### 9.2.1.49C Priority Queue ID + +The Priority Queue ID provides the identity of the Priority Queue. The Priority Queue ID is unique across all MAC-d flows that are currently allocated for one Node B Communication Context or across all Common MAC flows [FDD - within a cell][1.28Mcps TDD - within a carrier]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Priority Queue ID | | | INTEGER (0..7) | | + +#### 9.2.1.49D Process Memory Size + +The *Process Memory Size* IE is the size of an HARQ process in the Node B expressed in bits. It provides the maximum number of soft channel bits in the virtual IR buffer (TS 25.212 [8] or TS 25.222 [34]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Process Memory Size | | | ENUMERATED (
800, 1600, 2400, 3200,
4000, 4800, 5600, 6400,
7200, 8000, 8800, 9600,
10400, 11200, 12000,
12800, 13600, 14400,
15200, 16000, 17600,
19200, 20800, 22400,
24000, 25600, 27200,
28800, 30400, 32000,
36000, 40000, 44000,
48000, 52000, 56000,
60000, 64000, 68000,
72000, 76000, 80000,
88000, 96000, 104000,
112000, 120000, 128000,
136000, 144000, 152000,
160000, 176000, 192000,
208000, 224000, 240000,
256000, 272000, 288000,
304000,...) | | + +#### 9.2.1.50 Puncture Limit + +The Puncture Limit limits the amount of puncturing that can be applied in order to minimise the number of dedicated physical channels. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| +| Puncture Limit | | | INTEGER (0..15) | Unit: %
Range: 40..100 %
Step: 4 %
100% means no puncturing
[FDD - Value "0" is not applicable for E-DPCH.] | + +#### 9.2.1.50A QE-Selector + +The QE-Selector indicates from which source the value for the quality estimate (QE) shall be taken. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------------------|-----------------------| +| QE-Selector | | | ENUMERATED (
Selected,
Non-Selected) | | + +#### 9.2.1.51 Report Characteristics + +The report characteristics define how the reporting shall be performed. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|--------------------------------|--------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Report Characteristics | M | | | | – | | +| > On Demand | | | NULL | | | | +| > Periodic | | | | | | | +| >>Report Periodicity | M | | 9.2.1.51a | The frequency with which the Node B shall send measurement reports. | – | | +| > Event A | | | | | | | +| >>Measurement Threshold | M | | 9.2.1.44 | The threshold for which the Node B shall trigger a measurement report. | – | | +| >>Measurement Hysteresis Time | O | | 9.2.1.41A | | – | | +| > Event B | | | | | | | +| >>Measurement Threshold | M | | 9.2.1.44 | The threshold for which the Node B shall trigger a measurement report. | – | | +| >>Measurement Hysteresis Time | O | | 9.2.1.41A | | – | | +| > Event C | | | | | | | +| >>Measurement Increase/Decrease Threshold | M | | 9.2.1.43 | | – | | +| >>Measurement Change Time | M | | 9.2.1.40B | The time the measurement entity shall rise on (in ms), in order to trigger a measurement report. | – | | +| > Event D | | | | | | | +| >>Measurement Increase/Decrease Threshold | M | | 9.2.1.43 | | – | | +| >>Measurement Change Time | M | | 9.2.1.40B | The time the measurement entity shall fall (in ms), in order to trigger a measurement report. | – | | +| > Event E | | | | | | | +| >>Measurement Threshold 1 | M | | Measurement Threshold 9.2.1.44 | | – | | +| >>Measurement Threshold 2 | O | | Measurement Threshold 9.2.1.44 | | – | | +| >>Measurement Hysteresis Time | O | | 9.2.1.41A | | – | | +| >>Report Periodicity | O | | 9.2.1.51a | The frequency with which the Node B shall send measurement reports. | – | | +| > Event F | | | | | | | +| >>Measurement Threshold 1 | M | | Measurement Threshold 9.2.1.44 | | – | | +| >>Measurement Threshold 2 | O | | Measurement Threshold 9.2.1.44 | | – | | +| >>Measurement Hysteresis Time | O | | 9.2.1.41A | | – | | +| >>Report Periodicity | O | | 9.2.1.51a | The frequency with which the Node B shall send | – | | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|----------|----------------------------------------------------------------------------------------------|-----|--------| +| | | | | measurement reports. | | | +| >Additional Report Characteristics | | | | See Note 1 | | | +| >>On Modification | | | | | | | +| >>>On Modification | | 1 | | | YES | reject | +| >>>>Measurement Threshold | M | | 9.2.1.44 | The IE shall be ignored if the Dedicated Measurement Type is set to "Best Cell Portions LCR" | – | | +| Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. | | | | | | | + +#### 9.2.1.51a Report Periodicity + +The Report Periodicity defines the frequency at which the Node B shall send measurement reports. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|------------------------------------------------| +| CHOICE Report Periodicity Scale | M | | | | +| > millisecond | | | | | +| >>Report Periodicity Value | M | | INTEGER (1..6000,...) | Unit: ms
Range: 10..60000 ms
Step: 10 ms | +| > minute | | | | | +| >>Report Periodicity Value | M | | INTEGER (1..60,...) | Unit: min
Range: 1..60 min
Step: 1 min | + +#### 9.2.1.51A Requested Data Value + +The *Requested Data Value* IE contains the relevant data concerning the ongoing information exchange. The *Requested Data Value* IE shall include at least one of the following IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------|--------------------|-------------------|-----------------------|-----------------------|-------------|----------------------| +| DGPS Corrections | O | | 9.2.1.24B | | – | | +| GPS Navigation Model & Time Recovery | O | | 9.2.1.31B | | – | | +| GPS Ionospheric Model | O | | 9.2.1.31C | | – | | +| GPS UTC Model | O | | 9.2.1.31D | | – | | +| GPS Almanac | O | | 9.2.1.31F | | – | | +| GPS Real-Time Integrity | O | | 9.2.1.31E | | – | | +| GPS RX Pos | O | | 9.2.1.31G | | – | | +| GANSS Common Data | | 0..1 | | | YES | ignore | +| >GANSS Ionospheric Model | O | | 9.2.1.91 | | – | | +| >GANSS RX Pos | O | | 9.2.1.95 | | – | | +| >GANSS Additional Ionospheric Model | O | | 9.2.1.91a | | YES | ignore | +| >GANSS Earth Orientation Parameters | O | | 9.2.1.107a | | YES | ignore | +| GANSS Generic Data | | 0.. | | | GLOBAL | ignore | +| >GANSS ID | O | | 9.2.1.104 | | – | | +| >DGANSS Corrections | O | | 9.2.1.88 | | – | | +| >GANSS Navigation Model And Time Recovery | O | | 9.2.1.105 | | – | | +| >GANSS Time Model | O | | 9.2.1.96 | | – | | +| >GANSS UTC Model | O | | 9.2.1.97 | | – | | +| >GANSS Almanac | O | | 9.2.1.89 | | – | | +| >GANSS Real Time Integrity | O | | 9.2.1.94 | | – | | +| >GANSS Data Bit Assistance | O | | 9.2.1.103 | | – | | +| >GANSS Additional Time Models | O | | 9.2.1.96a | | YES | ignore | +| >GANSS Additional Navigation Models And Time Recovery | O | | 9.2.1.105a | | YES | ignore | +| >GANSS Additional UTC Models | O | | 9.2.1.97a | | YES | ignore | +| >GANSS Auxiliary Information | O | | 9.2.1.107c | | YES | ignore | +| >SBAS ID | C-
GANSS-
ID | | 9.2.1.107b | | YES | ignore | +| >DBDS Corrections | O | | 9.2.1.127 | | YES | ignore | +| >BDS Ionospheric Grid | O | | 9.2.1.128 | | YES | ignore | + +| | | | | | | | +|-------|--|--|--|--|--|--| +| Model | | | | | | | +|-------|--|--|--|--|--|--| + +| Condition | Explanation | +|-----------------|----------------------------------------------------------------------| +| GANSS-ID | This IE shall be present if the GANSS ID IE indicates "SBAS". | + +| Range Bound | Explanation | +|-------------------|---------------------------------| +| maxNoGANSS | Maximum number of GANSS Systems | + +#### 9.2.1.51B Requested Data Value Information + +The *Requested Data Value Information* IE provides information on whether or not the Requested Data Value is available in the message and also the Requested Data Value itself if available. In case of "Periodic" and "On Modification" reporting, "Information Not Available" shall be used when at least one part of the requested information was not available at the moment of initiating the Information Reporting procedure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Information Availability Indicator | M | | | | +| > Information Available | | | | | +| >>Requested Data Value | M | | 9.2.1.51A | | +| > Information Not Available | | | NULL | | + +#### 9.2.1.52 Resource Operational State + +The Resource Operational State is used to indicate the current operational state of the associated resource following a Node B failure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource Operational State | | | ENUMERATED ( Enabled, Disabled) | When a resource is marked as disabled, then its child resources are implicitly disabled. Cell Resource hierarchy can be referred to TS 25.430 [6]. | + +#### 9.2.1.52A Retention Priority + +Void. + +#### 9.2.1.52B RLC Mode + +The *RLC Mode* IE indicates the RLC Mode used for a Priority Queue. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------|-----------------------| +| RLC Mode | | | ENUMERATED ( RLC-AM, RLC-UM,...) | | + +#### 9.2.1.53 RL ID + +The RL ID is the unique identifier for one RL associated with a UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| RL ID | | | INTEGER (0..31) | | + +#### 9.2.1.53a RNC-Id + +This is the identifier of one RNC in UTRAN. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| RNC-Id | | | INTEGER (0..4095) | | + +#### 9.2.1.53b RTWP\* Reporting Indicator + +The RTWP\* Reporting Indicator indicates if the RTWP\* measurement value shall be included together with the reported RSEPS measurement value. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|----------------------------------------|-----------------------| +| RTWP* Indicator | | | ENUMERATED ( RTWP* Reporting Required) | | + +#### 9.2.1.53c RTWP\* for Cell Portion Reporting Indicator + +The RTWP\* for Cell Portion Reporting Indicator indicates if the RTWP\* for Cell Portion measurement value shall be included together with the reported RSEPS measurement value. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|---------------------------------------------------------|-----------------------| +| RTWP* per Cell Portion Indicator | | | ENUMERATED ( RTWP* for Cell Portion Reporting Required) | | + +#### 9.2.1.53A SFN + +System Frame Number of the cell, see ref. TS 25.402 [17]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| SFN | | | INTEGER (0..4095) | | + +#### 9.2.1.53B Segment Type + +Segment type as defined in TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Segment Type | | | ENUMERATED ( First segment, First segment short, Subsequent segment, Last segment, Last segment short, Complete SIB, Complete SIB short, ...) | | + +#### 9.2.1.53C SFN-SFN Measurement Threshold Information + +The SFN-SFN Measurement Threshold Information defines the related thresholds SFN-SFN Observed Time Difference measurements which shall trigger the Event On Modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| SFN-SFN Change Limit | O | | INTEGER(1..256) | Change of SFN-SFN value compared to previously reported value, which shall trigger a new report.
Unit: chip
Step: 1/16 chip | +| Predicted SFN-SFN Deviation Limit | O | | INTEGER(1..256) | Deviation of the predicted SFN-SFN from the latest measurement result, which shall trigger a new report.
Unit: chip
Step: 1/16 chip | + +#### 9.2.1.53D SFN-SFN Measurement Time Stamp + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------| +| CHOICE Mode | M | | | | +| >FDD | | | | | +| >>SFN | M | | 9.2.1.53A | Indicates the SFN of the reference cell at which the measurement has been performed. | +| >TDD | | | | | +| >>SFN | M | | 9.2.1.53A | Indicates the SFN of the reference cell at which the measurement has been performed. | +| >>Time Slot | M | | 9.2.3.23 | Indicates the Time Slot of the reference cell at which this measurement has been performed. | + +#### 9.2.1.53E SFN-SFN Measurement Value Information + +The *SFN-SFN Measurement Value Information* IE indicates the measurement result related to SFN-SFN Observed Time Difference measurements. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------------------------------------------|----------|--------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information | | 1..<maxNrOfMeasNCell> | | | +| >UC-Id | M | | 9.2.1.65B | | +| >SFN-SFN Value | M | | 9.2.1.53F | | +| >SFN-SFN Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the SFN-SFN Observed Time Difference measurements in 1/16 chip.
SFN-SFN Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported SFN-SFN Value, where x is the reported SFN-SFN Value and $\mu = E[x]$ is the expectation value of x. | +| >SFN-SFN Drift Rate | M | | INTEGER (-100..+100) | Indicates the SFN-SFN drift rate in 1/256 chip per second. A positive value indicates that the Reference cell clock is running at a greater frequency than the measured neighbouring cell. | +| >SFN-SFN Drift Rate Quality | O | | INTEGER (0..100) | Indicates the standard deviation (std) of the SFN-SFN drift rate measurements in 1/256 chip per second. SFN-SFN Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported SFN-SFN Drift Rate, where x is the reported SFN-SFN Drift Rate and $\mu = E[x]$ is the expectation value of x. | +| >SFN-SFN Measurement Time Stamp | M | | 9.2.1.53D | | +| Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information | | 0..<maxNrOfMeasNCell-1> | | | +| >UC-Id | M | | 9.2.1.65B | | + +| Range Bound | Explanation | +|-------------------------|--------------------------------------------------------------| +| maxNrOfMeasNCell | Maximum number of neighbouring cells that can be measured on | + +#### 9.2.1.53F SFN-SFN Value + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------------------------| +| CHOICE Mode | M | | | | +| >FDD | | | | | +| >>SFN-SFN | M | | INTEGER (0..614399) | According to mapping in TS 25.133 [22]. | +| >TDD | | | | 1.28 Mcps and 3.84 Mcps only | +| >>SFN-SFN | M | | INTEGER (0..40961) | According to mapping in TS 25.123 [23]. | +| >TDD 7.68 Mcps | | | | | +| >>SFN-SFN | M | | INTEGER (0..81923) | According to mapping in TS 25.123 [23]. | + +#### 9.2.1.53G RL Specific DCH Information + +The *RL Specific DCH Information* IE provides RL specific DCH Information for DCHs. In the case of a set of co-ordinated DCHs requiring a new transport bearer on Iub, the *Transport Layer Address* IE and the *Binding ID* IE in the *RL Specific DCH Information* IE shall be included only for one of the DCHs in the set of co-ordinated DCHs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|------------------|-----------------------|------------------------------------------------------|-------------|----------------------| +| RL Specific DCH Information | | 1.. | | | – | | +| >DCH ID | M | | 9.2.1.20 | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Bearer Not Requested Indicator | O | | 9.2.2.4G | FDD Only | YES | ignore | + +| Range Bound | Explanation | +|-------------|-----------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for one UE | + +#### 9.2.1.53H Scheduling Priority Indicator + +Indicates the relative priority of the HS-DSCH [FDD - or E-DCH data frame]. Used by the Node B when scheduling HS-DSCH[FDD - or E-DCH]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------| +| Scheduling Priority Indicator | | | INTEGER (0..15) | Relative priority of the HS-DSCH [FDD - or E-DCH data frame]:
"0" =Lowest Priority
...
"15" =Highest Priority | + +#### 9.2.1.53I SID + +The *SID* IE provides the identity of the Size Index. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| SID | | | INTEGER (0..7) | | + +#### 9.2.1.54 SIB Deletion Indicator + +Void. + +#### 9.2.1.55 SIB Originator + +Indicates if the Node B shall fill in the SIB information or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|---------------------------------|-----------------------| +| SIB Originator | | | ENUMERATED ( Node B, CRNC, ...) | | + +#### 9.2.1.55A Signalling Bearer Request Indicator + +The *Signalling Bearer Request Indicator* IE indicates if a new signalling bearer needs to be established for the control of Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-------------------------------|-----------------------| +| Signalling Bearer Request Indicator | | | ENUMERATED (Bearer Requested) | | + +#### 9.2.1.56 Shutdown Timer + +The shutdown timer shall indicate the length of time available to the CRNC to perform the block of a resource when a Normal priority block is requested. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-----------------------| +| Shutdown Timer | | | INTEGER (1..3600) | Unit: second | + +#### 9.2.1.56a T1 + +The *T1* IE is used as described in ref TS 25.321 [32] subclause 11.6.2.3. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| T1 | | | ENUMERATED (10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 120, 140, 160, 200, 300, 400, ...) | Unit: ms
Node B may use this value to stop the re-transmission of the corresponding MAC-hs PDU. | + +#### 9.2.1.56A T\_RLFAILURE + +The Radio Link Failure procedure shall be triggered after a period of time T\_RLFAILURE has elapsed with a persisting out-of-sync indication (see also ref. TS 25.214 [10] and TS 25.224 [21]). + +| Information Element/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|---------------------------------------------------| +| T_RLFAILURE | | | INTEGER (0..255) | Unit: second
Range: 0 .. 25.5 s
Step: 0.1 s | + +#### 9.2.1.56B Start Of Audit Sequence Indicator + +Indicates if the AUDIT REQUEST message initiates a new audit sequence or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|--------------------------------------------------------------------|-----------------------| +| Start Of Audit Sequence Indicator | | | ENUMERATED ( Start Of Audit Sequence, Not Start Of Audit Sequence) | | + +#### 9.2.1.56C TFCI2 Bearer Request Indicator + +Void. + +#### 9.2.1.57 TFCI Presence + +The TFCI Presence parameter indicates whether the TFCI shall be included. [TDD - If it is present in the timeslot, it will be mapped to the channelisation code defined by TS 25.221 [19].] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------|-----------------------| +| TFCI presence | | | ENUMERATED (Present, Not Present) | | + +#### 9.2.1.58 TFCS (Transport Format Combination Set) + +The Transport Format Combination Set is defined as a set of Transport Format Combinations on a Coded Composite Transport Channel. It is the allowed Transport Format Combinations of the corresponding Transport Channels. The DL Transport Format Combination Set is applicable for DL Transport Channels. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|------------|------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE TFCS Values | M | | | | - | | +| >Always Used | | | | This choice is always made. | - | | +| >>TFCS | | 1.. | | The first instance of the parameter corresponds to TFCI zero, the second to 1 and so on.
[TDD - The first entry (for TFCI 0) should be ignored by the receiver.] | - | | +| >>>CTFC | M | | 9.2.1.18A | | - | | +| >>>CHOICE Gain Factors | C-PhysChan | | | | - | | +| >>>>Signalled Gain Factors | | | | | - | | +| >>>>>CHOICE Mode | M | | | | - | | +| >>>>>>FDD | | | | | - | | +| >>>>>>>Gain Factor $\beta_C$ | M | | INTEGER (0..15) | For UL DPCCH or control part of PRACH; mapping in accordance to TS 25.213 [9] | - | | +| >>>>>>>Gain Factor $\beta_D$ | M | | INTEGER (0..15) | For UL DPDCH or data part of PRACH; mapping in accordance to TS 25.213 [9] | - | | +| >>>>>>TDD | | | | | - | | +| >>>>>>>Gain Factor $\beta$ | M | | INTEGER (0..15) | For UL DPCH in TDD; mapping in accordance to TS 25.223 [20]. | - | | +| >>>>>Reference TFC nr | O | | INTEGER (0..3) | If this TFC is a reference TFC, this IE indicates the reference number. | - | | +| >>>>Computed Gain Factors | | | | | - | | +| >>>>>Reference TFC nr | M | | INTEGER (0..3) | Indicates the reference TFC to be used to calculate the gain factors for this TFC. | - | | +| >>>Gain Factors 10ms Mode | O | | 9.2.2.199 | For UL DPCCH in FDD, and applicable to 10ms Transmission mode [8]. | YES | reject | +| >Not Used | | | | This choice shall never be made by the CRNC and the Node B shall consider the procedure as failed if it is received. | - | | + +| Condition | Explanation | +|-----------|---------------------------------------------------------------------------| +| PhysChan | The IE shall be present if the TFCS concerns a UL DPCH or PRACH channel . | + +| Range Bound | Explanation | +|-------------|-----------------------------------------------------| +| maxNrOfTFCS | The maximum number of Transport Format Combinations | + +#### 9.2.1.58A TNL QoS + +This IE indicates the TNL QoS characteristics of the transport bearer for the uplink data traffic. + +When the *DS Field* IE is used, the value of this IE is configurable by the operator. + +When the *Generic Traffic Category* IE is used, generic traffic categories are implementation-specific (e.g. they may be determined by the sender from the application parameters). The value assigned to each of these categories and sent in the *Generic Traffic Category* IE is configurable by the operator, as well as the mapping of this value to DS field (IETF RFC 2474 [35]) at the Node B side. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE TNL QoS type | M | | | | +| > DS Field | | | | | +| >>DS Field | M | | BIT STRING (SIZE((8))) | DS Field as defined in IETF RFC 2474 [35].
Typically used when the Node B and its CRNC are in the same DS domain as defined in IETF RFC 2475 [36]. | +| > Generic Traffic Category | | | | | +| >>Generic Traffic Category | M | | BIT STRING (SIZE(8)) | | + +#### 9.2.1.59 Transport Format Set + +The Transport Format Set is defined as the set of Transport Formats associated to a Transport Channel, e.g. DCH. + +[TDD - The Transport Format Set for each transport channel within the same CCTrCH shall have the same value for the 2nd *Interleaving Mode* IE.] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------|--------------|-------------------|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dynamic Transport Format Information | | 1.. | | The first instance of the parameter corresponds to TFI zero, the second to 1 and so on. | +| >Number of Transport Blocks | M | | INTEGER (0..512) | | +| >Transport Block Size | C-Blocks | | INTEGER (0..5000) | Unit: Bits | +| >CHOICE Mode | M | | | | +| >> TDD | | | | | +| >>> Transmission Time Interval Information | C-TTIdynamic | 1.. | | | +| >>>>Transmission Time Interval | M | | ENUMERATED (10, 20, 40, 80,...) | Unit: ms | +| Semi-Static Transport Format Information | | 1 | | | +| >Transmission Time Interval | M | | ENUMERATED (10, 20, 40, 80, dynamic,...,5) | Unit: ms;
Value "dynamic" for TDD only;
Value "5" for LCR TDD only;
For FDD DCH, the value "80" is applicable only when DL DPCH Slot Format IE indicates a slot format with SF=512. | +| >Type Of Channel Coding | M | | ENUMERATED ( No codingTDD, Convolutional, Turbo, ...) | [FDD - The value "No codingTDD" shall be treated as logical error if received] | +| >Coding Rate | C-Coding | | ENUMERATED (1/2, 1/3,...) | | +| >Rate Matching Attribute | M | | INTEGER (1..maxRM) | | +| >CRC Size | M | | ENUMERATED (0, 8, 12, 16, 24,...) | | +| >CHOICE Mode | M | | | | +| >> TDD | | | | | +| >>>2 nd Interleaving Mode | M | | ENUMERATED ( Frame related, Timeslot related, ...) | | + +| Condition | Explanation | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Blocks | The IE shall be present if the Number Of Transport Blocks IE is set to a value greater than 0. | +| Coding | The IE shall be present if the Type Of Channel Coding IE is set to "Convolutional" or "Turbo". | +| TTIdynamic | The IE shall be present if the Transmission Time Interval IE in the Semi-Static Transport Format Information IE is set to "dynamic". | + +| Range Bound | Explanation | +|---------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxNrOfTFs | Maximum number of different Transport Formats that can be included in the Transport Format Set for one transport channel | +| maxRM | Maximum number that could be set as rate matching attribute for a transport channel | +| maxTTI-count | The amount of different TTIs that are possible for that Transport Format | + +#### 9.2.1.60 ToAWE + +TOAWE is the window endpoint. DL data frames are expected to be received before this window endpoint. TOAWE is defined with a positive value relative Latest Time of Arrival (LTOA). A data frame arriving after TOAWE gives a Timing Adjustment Control frame response. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| ToAWE | | | INTEGER (0..2559) | Unit: ms | + +#### 9.2.1.61 ToAWS + +TOAWS is the window startpoint. DL data frames are expected to be received after this window startpoint. TOAWS is defined with a positive value relative Time of Arrival Window Endpoint (TOAWE). A data frame arriving before TOAWS gives a Timing Adjustment Control frame response. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| ToAWS | | | INTEGER (0..1279) | Unit: ms | + +#### 9.2.1.62 Transaction ID + +The transaction ID is used to associate all the messages belonging to the same procedure. Messages belonging to the same procedure shall use the same transaction ID. + +The transaction ID is determined by the initiating peer of a procedure. For common procedures the transaction ID shall uniquely identify a procedure within all ongoing parallel procedures initiated by one protocol peer, using the same procedure code and signalled over the same Node B Control Port. For dedicated procedures the transaction ID shall uniquely identify a procedure within all ongoing parallel procedures initiated by one protocol peer, using the same procedure code and initiated towards the same Node B/CRNC context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------| +| CHOICE Transaction ID Length | | | | The Transaction ID shall be interpreted for its integer value, not for the type of encoding ("short" or "long"). | +| >Short | | | | | +| >>Transaction ID Value | M | | INTEGER (0..127) | | +| >Long | | | | | +| >>Transaction ID Value | M | | INTEGER (0..32767) | | + +#### 9.2.1.62A Transport Bearer Request Indicator + +Indicates whether a new transport bearer needs to be established for carrying the concerned transport channel. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------------------------------------------|-----------------------| +| Transport Bearer Request Indicator | | | ENUMERATED ( Bearer Requested, Bearer Not Requested, ...) | | + +#### 9.2.1.63 Transport Layer Address + +In case of transport bearer establishment with ALCAP (TS 25.426 [2], TS 25.434 [31]), this IE contains the address to be used for Transport Network Control Plane signalling to establish the transport bearer according to (TS 25.426 [2], TS 25.434 [31]). + +In order to allow transport bearer establishment without ALCAP, this IE contains the address of the transport bearer to be used for the user plane transport. + +For details on the Transport Address used see ref. (TS 25.426 [2], TS 25.434 [31]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|--------------------------------|-----------------------| +| Transport Layer Address | | | BIT STRING (SIZE(1..160, ...)) | | + +#### 9.2.1.64 TSTD Indicator + +Indicates if TSTD shall be active or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------------|-----------------------| +| TSTD Indicator | | | ENUMERATED (active, inactive) | | + +#### 9.2.1.64A $T_{\text{UTRAN-GPS}}$ Measurement Value Information + +The $T_{\text{UTRAN-GPS}}$ *Measurement Value Information* IE indicates the measurement results related to the UTRAN GPS Timing of Cell Frames for UE Positioning measurements. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $T_{\text{UTRAN-GPS}}$ | | 1 | | Indicates the UTRAN GPS Timing of Cell Frames for UE Positioning. According to mapping in TS 25.133 [22]. Significant values range from 0 to 37158911999999. | +| >MS | M | | INTEGER (0..16383) | Most Significant Part | +| >LS | M | | INTEGER (0..4294967295) | Least Significant Part | +| $T_{\text{UTRAN-GPS}}$ Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the $T_{\text{UTRAN-GPS}}$ measurements in 1/16 chip. $T_{\text{UTRAN-GPS}}$ Quality = $\sqrt{E[(x-\mu)^2]} = \text{std of reported } T_{\text{UTRAN-GPS}}$ Value, where x is the reported $T_{\text{UTRAN-GPS}}$ Value and $\mu = E[x]$ is the expectation value of x. | +| $T_{\text{UTRAN-GPS}}$ Drift Rate | M | | INTEGER (-50..+50) | Indicates the $T_{\text{UTRAN-GPS}}$ drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GPS clock. | +| $T_{\text{UTRAN-GPS}}$ Drift Rate Quality | O | | INTEGER (0..50) | Indicates the standard deviation (std) of the $T_{\text{UTRAN-GPS}}$ drift rate measurements in 1/256 chip per second. $T_{\text{UTRAN-GPS}}$ Drift Rate Quality = $\sqrt{E[(x-\mu)^2]} = \text{std of reported } T_{\text{UTRAN-GPS}}$ Drift Rate, where x is the reported $T_{\text{UTRAN-GPS}}$ Drift Rate and $\mu = E[x]$ is the expectation value of x. | + +#### 9.2.1.64B $T_{\text{UTRAN-GPS}}$ Measurement Threshold Information + +The $T_{\text{UTRAN-GPS}}$ Measurement Threshold Information defines the related thresholds for UTRAN GPS Timing of Cell Frames for UE Positioning measurements shall trigger the event On Modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| T UTRAN-GPS Change Limit | O | | INTEGER (1..256) | Change of T UTRAN-GPS value compared to previously reported value, which shall trigger a new report.
Unit in 1/16 chip. | +| Predicted T UTRAN-GPS Deviation Limit | O | | INTEGER (1..256) | Deviation of the predicted T UTRAN-GPS from the latest measurement result, which shall trigger a new report.
Unit in 1/16 chip. | + +#### 9.2.1.64C TUTRAN-GPS Accuracy Class + +The TUTRAN-GPS Accuracy Class IE indicates the accuracy class of the UTRAN GPS Timing of Cell Frames for UE Positioning measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| T UTRAN-GPS Accuracy Class | | | ENUMERATED ( Accuracy Class A, Accuracy Class B, Accuracy Class C, ...) | More information about T UTRAN-GPS Measurement Accuracy Class is included in TS 25.133 [22] and TS 25.123 [23]. | + +#### 9.2.1.65 UARFCN + +Designates the carrier frequency. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|------------------------|--------------------------------------------------------------------| +| UARFCN | | | INTEGER (0..16383,...) | As defined in subclause 5.4.3 in TS 25.104 [14] and TS 25.105 [15] | + +#### 9.2.1.65A UL Capacity Credit + +The capacity credit indicates to the CRNC the Uplink capacity of a Local Cell or a Local Cell Group. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| UL Capacity Credit | | | INTEGER (0..65535) | | + +#### 9.2.1.65B UTRAN Cell Identifier (UC-Id) + +The UC-Id (UTRAN Cell identifier) is the identifier of a cell in one UTRAN. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RNC-Id | M | | 9.2.1.53a | If the Extended RNC-ID IE is included in the UC-Id IE, the RNC-Id IE shall be ignored. | – | – | +| C-Id | M | | 9.2.1.9 | | – | – | +| Extended RNC-ID | O | | 9.2.1.65C | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject | + +#### 9.2.1.65C Extended RNC-ID + +This is the identifier of one RNC in UTRAN. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------| +| Extended RNC-ID | | | INTEGER(4096..65535) | Note: Application of the Extended RNC-ID IE to very large networks is FFS. | + +#### 9.2.1.66 UL FP Mode + +This parameter defines if normal or silent mode of the Frame Protocol shall be used for the UL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------|-----------------------| +| UL FP Mode | | | ENUMERATED (Normal, Silent, ...) | | + +#### 9.2.1.67 UL interference level + +Void. + +#### 9.2.1.67A UL SIR + +The UL SIR indicates a received UL SIR. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------| +| UL SIR | | | INTEGER (-82..173) | Value = UL SIR/10
Unit: dB
Range: -8.2 .. +17.3 dB
Step: 0.1 dB | + +#### 9.2.1.68 Unidirectional DCH Indicator + +The *Unidirectional DCH Indicator* IE indicates that the DCH is unidirectional. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-------------------------------------------------|-----------------------| +| Unidirectional DCH Indicator | | | ENUMERATED (Downlink DCH only, Uplink DCH only) | | + +#### 9.2.1.69 E-DCH MAC-d Flow Multiplexing List + +The E-DCH MAC-d Flow Multiplexing List indicates which E-DCH MAC-d flows are allowed to be multiplexed within a MAC-e/MAC-i PDU with the MAC-d flow it is associated to. If the E-DCH MAC-d Flow Multiplexing List is signalled for an E-DCH MAC-d flow it indicates that E-DCH MAC-d PDUs of this E-DCH MAC-d flow are the first E-DCH MAC-d PDU in the MAC-e/MAC-i PDU. If an E-DCH MAC-d Flow Multiplexing List was already received within a previous Radio Link related procedure and no E-DCH MAC-d Flow Multiplexing List is signalled for an E-DCH MAC-d flow, the Node B shall continue to use the previously received one. If no E-DCH MAC-d Flow Multiplexing List was ever received for an E-DCH MAC-d flow no restrictions shall be assumed for the related E-DCH MAC-d flow for multiplexing E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-DCH MAC-d Flow Multiplexing List | | | BIT STRING (SIZE(8)) |

The first Bit corresponds to E-DCH MAC-d flow 0, the second bit corresponds to E-DCH MAC-d flow 1, etc.

For 1.28Mcps TDD, if the IE is included in the Common E-DCH MAC-d Flow Specific Information LCR IE, the first bit corresponds to E-DCH MAC-d flow with the lowest E-DCH MAC-d Flow ID within the same frequency, the second bit corresponds to E-DCH MAC-d flow with the second lowest E-DCH MAC-d Flow ID within the same frequency, etc.

| + +#### 9.2.1.70 E-DCH Capability + +This parameter defines the E-DCH capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------------------------------|-----------------------| +| E-DCH Capability | | | ENUMERATED (E-DCH Capable, E-DCH non Capable) | | + +#### 9.2.1.71 E-DCH Logical Channel Information + +The *E-DCH Logical Channel Information* IE is used for the establishment of E-DCH Logical Channels. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH Logical Channel Information | | 1..<maxnooflogicalchannels> | | | – | | +| >Logical Channel ID | M | | 9.2.1.80 | | – | | +| >Scheduling Priority Indicator | M | | 9.2.1.53H | | – | | +| >Scheduling Information | M | | 9.2.1.84 | | – | | +| >MAC-es Guaranteed Bit Rate | O | | 9.2.1.82 | | – | | +| >E-DCH DDI Value | M | | 9.2.1.76 | If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value. Value “0x3F” is reserved. Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >MAC-d PDU Size List | | 1..<maxNrOfMACdPDUSize> | | | – | | +| >>MAC-d PDU Size | M | | 9.2.1.38A | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | reject | +| >MAC-es Maximum Bit Rate LCR | O | | 9.2.3.90 | 1.28Mcps TDD only | YES | ignore | +| >UE Aggregate Maximum Bit Rate Enforcement Indicator | O | | NULL | | YES | ignore | + +| Range Bound | Explanation | +|-------------------------------|-------------------------------------------------------| +| Maxnooflogicalchannels | Maximum number of logical channels | +| maxNrOfMACdPDUSize | Maximum number of MAC-d PDU size per Logical Channels | + +#### 9.2.1.72 E-DCH Logical Channel To Modify + +The *E-DCH Logical Channel To Modify* IE is used for the reconfiguration of E-DCH Logical Channels. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH Logical Channel Information | | 1.. | | | – | | +| >Logical Channel ID | M | | 9.2.1.80 | | – | | +| >Scheduling Priority Indicator | O | | 9.2.1.53H | | – | | +| >Scheduling Information | O | | 9.2.1.84 | | – | | +| >MAC-es Guaranteed Bit Rate | O | | 9.2.1.82 | | – | | +| >E-DCH DDI Value | O | | 9.2.1.76 | If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value. Value “0x3F” is reserved. Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >MAC-d PDU Size List | | 0.. | | | – | | +| >>MAC-d PDU Size | M | | 9.2.1.38A | Shall be ignored if Maximum MAC-d PDU Size Extended IE is present. | – | | +| >Maximum MAC-d PDU Size Extended | O | | MAC PDU Size Extended 9.2.1.38C | | YES | reject | +| >MAC-es Maximum Bit Rate LCR | O | | 9.2.3.90 | 1.28Mcps TDD only | YES | ignore | + +| Range Bound | Explanation | +|-------------------------------|-------------------------------------------------------| +| maxnooflogicalchannels | Maximum number of logical channels | +| maxNrOfMACdPDUSize | Maximum number of MAC-d PDU size per Logical Channels | + +#### 9.2.1.73 E-DCH MAC-d Flows To Delete + +The *E-DCH MAC-d Flows To Delete* IE is used for the removal of E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|----------------------------|-----------------------|-----------------------| +| E-DCH MAC-d Flows To Delete | | 1.. | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | + +| Range Bound | Explanation | +|-----------------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | + +#### 9.2.1.74 E-DCH MAC-d Flow ID + +The E-DCH MAC-d Flow ID is the unique identifier for one MAC-d flow on E-DCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------|-----------------------| +| E-DCH MAC-d Flow ID | | | INTEGER
(0..maxNrOfEDCHMACdFlows - 1) | | + +| Range Bound | Explanation | +|----------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | + +##### 9.2.1.74A E-DCH MAC-d PDU Size Capability + +This parameter defines the capability for a Local Cell to support different MAC-d PDU Size formats. If this IE is set to "Flexible Size Capable" the Local Cell is "Fixed Size Capable" and "Flexible Size Capable". If this IE has not been configured or has been set to "Fixed Size Capable" the Local Cell is only "Fixed Size Capable". + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------------------------------------------|-----------------------| +| E-DCH MAC-d PDU Size Capability | | | ENUMERATED
(Fixed Size Capable, Flexible Size Capable) | | + +#### 9.2.1.74B E-DCH MAC-d PDU Size Format + +The *E-DCH MAC-d PDU Size Format* IE provides information about the type of MAC-d PDU Size Format that shall be used for the E-DCH in the new configuration. "Fixed MAC-d PDU Size" uses MAC-d PDU sizes defined in *MAC-d PDU Size List* IE of the *E-DCH Logical Channel Information* IE. "Flexible MAC-d PDU Size" uses a flexible MAC-d PDU size with a maximum PDU size as defined by *Maximum MAC-d PDU Size Extended* IE of *E-DCH Logical Channel Information* IE. The actual MAC-d PDU size is determined as specified in TS 25.435 [24] and TS 25.321 [32]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|---------------------------------------------------------------|-----------------------| +| E-DCH MAC-d PDU Size Format | | | ENUMERATED
(Fixed MAC-d PDU Size, Flexible MAC-d PDU Size) | | + +#### 9.2.1.75 E-RNTI + +The E-RNTI is needed for the UE (or UE group) specific CRC in E-AGCH, see ref. TS 25.319 [38]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| E-RNTI | | | INTEGER
(0..65535) | | + +#### 9.2.1.76 E-DCH DDI Value + +The E-DCH DDI Value is the Data Description Indicator value identifying a unique combination of E-DCH MAC-d Flow ID and MAC-d PDU Size. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|-----------------------| +| E-DCH DDI Value | | | INTEGER
(0..62) | | + +#### 9.2.1.77 E-DCH Provided Bit Rate Value + +The *E-DCH Provided Bit Rate Value* IE indicates the E-DCH Provided Bit Rate as defined in TS 25.321 [32]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|------------------------------------------------|-----------------------| +| E-DCH Provided Bit Rate Value | | | INTEGER
(0..2^24-1, ..., 2^24..256,000,000) | Expressed in bit/s. | + +#### 9.2.1.78 E-DCH Provided Bit Rate Value Information + +The *E-DCH Provided Bit Rate Value Information* IE reports the *E-DCH Provided Bit Rate Value* IE for each priority class. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-----------------------------|-----------------------|-----------------------| +| E-DCH Provided Bit Rate Value Information | | 1.. | | | +| >Scheduling Priority Indicator | M | | 9.2.1.53H | | +| >E-DCH Provided Bit Rate Value | M | | 9.2.1.77 | | + +| Range Bound | Explanation | +|------------------------|-----------------------------------------------| +| maxNrOfPriorityClasses | Maximum number of E-DCH Scheduling Priorities | + +#### 9.2.1.79 E-DCH Processing Overload Level + +The *E-DCH Processing Overload Level* IE defines the threshold that determines when the Node B shall indicate processing issue problems to the RNC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-DCH Processing Overload Level | | | INTEGER (0..10,...) | Number of consecutive TTIs. The value '0' is a special value that means infinity, i.e. when this value is used, the Node B shall never indicate processing issue to the RNC. | + +#### 9.2.1.80 Logical channel ID + +The *Logical Channel ID* IE is used to identify a E-DCH logical channel in Scheduling Information that is sent over Uu. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| Logical Channel ID | | | INTEGER (1..15) | | + +#### 9.2.1.81 Maximum Number Of Retransmissions For E-DCH + +The *Maximum Number Of Retransmissions For E-DCH* IE specifies the upper boundary for retransmissions for a single MAC-d flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|-----------------------|-----------------------| +| Maximum Number Of Retransmissions For E-DCH | | | INTEGER (0..15) | | + +#### 9.2.1.82 MAC-es Guaranteed Bit Rate + +The *MAC-es Guaranteed Bit Rate* IE indicates the guaranteed number of bits per second to be delivered over the air interface under normal operating conditions (provided there is data to deliver) for which the Node B shall provide sufficient UL resources. If the *MAC-es Guaranteed Bit Rate* IE is received with the value set to 0 during RL set up or modification, no guarantee is applied. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|---------------------------------------------------------------------|-----------------------| +| MAC-es Guaranteed Bit Rate | | | INTEGER (0..2 24 -1, ..., 2 24 ..256,000,000) | Unit: bit/s | + +#### 9.2.1.83 MAC-e Reset Indicator + +Indicates the MAC-e (or MAC-i) Reset is performed in UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|--------------------------|------------------------------------------------------------------------------------------------------| +| MAC-e Reset Indicator | | | ENUMERATED (MAC-e Reset) | Means MAC-i Reset in case Maximum MAC-d PDU Size Extended is configured for an E-DCH Logical Channel | + +#### 9.2.1.84 Scheduling Information + +The *Scheduling Information* IE indicates whether the scheduling information is included for the E-DCH logical channel or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|--------------------------------------|-----------------------| +| Scheduling Information | | | ENUMERATED ( Included, Not Included) | | + +#### 9.2.1.85 E-DCH Power Offset for Scheduling Info + +The *E-DCH Power Offset for Scheduling Info* is used to calculate the [FDD - E-DPDCH][TDD - E-PUCH] power for transmission of scheduling information without any MAC-d PDUs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|------------------------| +| E-DCH Power Offset for Scheduling Info | | | INTEGER (0..6) | Unit: dB
Step: 1 dB | + +#### 9.2.1.86 MBMS Capability + +This parameter defines the MBMS capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|---------------------------------------------|-----------------------| +| MBMS Capability | | | ENUMERATED (MBMS Capable, MBMS non Capable) | | + +#### 9.2.1.87 Modulation + +Indicates the modulation to be used for a S-CCPCH CCTrCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------|-----------------------| +| Modulation | | | ENUMERATED ( QPSK, 16QAM, ...) | | + +#### 9.2.1.88 DGANSS Corrections + +This IE contains DGANSS corrections. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|-------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DGANSS Reference Time | M | | INTEGER(0..357 0 by step of 30) | Seconds. Time in GNSS system time (modulo 3600 s) when the DGANSS corrections were calculated | — | | +| DGANSS Information | | 1 to | | | — | | +| >GANSS Signal ID | O | | 9.2.1.106 | | — | | +| >Status/Health | M | | ENUMERATED( UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.2, UDRE scale 0.1, no data, invalid data) | | — | | +| >DGANSS Signal Information | C- Status/ Health | 1 to | | If the Cipher information is included these fields are ciphered. | — | | +| >>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | — | | +| >>IOD | M | | BIT STRING (SIZE(10)) | | — | | +| >>UDRE | M | | ENUMERATED( UDRE $\leq$ 1.0 m, 1.0m < UDRE $\leq$ 4.0m, 4.0m < UDRE $\leq$ 8.0m, 8.0m < UDRE) | The value in this field shall be multiplied by the UDRE Scale Factor in the IE Status/Health to determine the final UDRE estimate for the particular satellite. | — | | +| >>PRC | M | | INTEGER(-2047..2047) | Scaling factor 0.32 meters | — | | +| >>RRC | M | | INTEGER(-127..127) | Scaling factor 0.032 meters/sec | — | | +| >>DGNSS Validity Period | O | | 9.2.1.125 | | YES | ignore | + +| Condition | Explanation | +|---------------|-----------------------------------------------------------------------------------------------------| +| Status/Health | This IE shall be present if the Status/Health IE value is not equal to "no data" or "invalid data". | + +| Range Bound | Explanation | +|-------------|-------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in the IE | +| maxSgnType | Maximum number of signals for which data is included in the IE | + +#### 9.2.1.89 GANSS Almanac + +This IE contains a reduced-precision subset of the ephemeris and clock correction parameters. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-----------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Week Number | M | | INTEGER(0..255) | Almanac reference week , number of weeks since the beginning of GANSS specific system time (mod 256) | – | | +| CHOICE Almanac Model | M | | | | – | | +| > Keplerian Parameters | | | | Model 1 | – | | +| >>T oa | M | | INTEGER(0..1023) | Scaling factor 600 s Reference time of almanac within week in GANSS TOD time base (OS SIS ICD [39]). | – | | +| >>IOD a | M | | INTEGER(0..15) | Issue-Of –Data, common to all satellites (OS SIS ICD [39]). | – | | +| >> Satellite Information KP | | 1 to | | Almanacs are in the order of the SV IDs, the smallest ID first. | – | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | – | | +| >>>e | M | | BIT STRING (SIZE(11)) | dimensionless (OS SIS ICD [39]) | – | | +| >>>δi | M | | BIT STRING (SIZE(11)) | semi-circles (OS SIS ICD [39]) | – | | +| >>>OMEGADOT | M | | BIT STRING (SIZE(11)) | semi-circles/sec (OS SIS ICD [39]) | – | | +| >>>SV Status INAV | M | | BIT STRING (SIZE(4)) | Dimensionless (OS SIS ICD [39]). E5b HS occupies the 2 MSBs and E1-B HS the two LSBs. | – | | +| >>>SV Status FNAV | O | | BIT STRING (SIZE(2)) | Dimensionless. (OS SIS ICD [53]). E5a HS . | | | +| >>>delta A 1/2 | M | | BIT STRING (SIZE(13)) | (meters) 1/2 (OS SIS ICD [39]) | – | | +| >>>OMEGA 0 | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [39]) | – | | +| >>>M 0 | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [39]) | – | | +| >>>ω | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [39]) | – | | +| >>>af 0 | M | | BIT STRING (SIZE(16)) | Seconds (OS SIS ICD [39]) | – | | +| >>>af 1 | M | | BIT STRING (SIZE(13)) | sec/sec (OS SIS ICD [39]) | – | | +| > NAV Keplerian Parameters | | | | Model 2 | | | +| >>Keplerian NAV Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..255) | Scaling factor 2 12 s Reference time of almanac within week in GANSS TOD time base | – | | +| >>> Satellite information NAV-KP | | 1.. | | | – | | +| >>>>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [18]. | – | | +| >>>>e | M | | BIT STRING (SIZE(16)) | Eccentricity, dimensionless IS-QZSS [47] | – | | +| >>>>δi | M | | BIT STRING | Correction to inclination, | – | | + +| | | | | | | | +|--|--|--|------------|------------------------------|--|--| +| | | | (SIZE(16)) | semi-circles IS-QZSS
[47] | | | +|--|--|--|------------|------------------------------|--|--| + +| | | | | | | | +|----------------------------------------|---|-------------------------------------|--------------------------|--------------------------------------------------------------------------------------------------------|-----|--------| +| >>>>OMEGA D
T | M | | BIT STRING
(SIZE(16)) | Rate of right ascension,
semi-circles/sec IS-
QZSS [47] | – | | +| >>>>SV Health | M | | BIT STRING
(SIZE(8)) | Satellite health IS-QZSS
[47] | – | | +| >>>>A 1/2 | M | | BIT STRING
(SIZE(24)) | Square root of the semi-
major axis,
meters 1/2 IS-QZSS [47] | – | | +| >>>>OMEGA 0 | M | | BIT STRING
(SIZE(24)) | Longitude of ascending
node of orbit plane at
weekly epoch,
semi-circles IS-QZSS
[47] | – | | +| >>>>ω | M | | BIT STRING
(SIZE(24)) | Argument of perigee
semi-circles IS-QZSS
[47] | – | | +| >>>>M 0 | M | | BIT STRING
(SIZE(24)) | Mean anomaly at
reference time
semi-circles IS-QZSS
[47] | – | | +| >>>>af 0 | M | | BIT STRING
(SIZE(11)) | Apparent satellite clock
correction
seconds IS-QZSS [47] | – | | +| >>>>af 1 | M | | BIT STRING
(SIZE(11)) | Apparent satellite clock
correction
sec/sec IS-QZSS [47] | – | | +| >Reduced Keplerian
Parameters | | | | Model 3 | | | +| >>Keplerian Reduced
Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..2
55) | Scaling factor 2 12 s
Reference time of
almanac within week in
GANSS TOD time base | – | | +| >>>Satellite
information RED-
KP | | 1..
NSSSatA
lmanac> | | | – | | +| >>>>Sat ID | M | | INTEGER
(0..63) | Defined in TS 25.331
[18]. | – | | +| >>>>δ A | M | | BIT STRING
(SIZE(8)) | meters (IS-GPS-200
[43], IS-GPS-705 [44],
IS-GPS-800 [45], IS-
QZSS [47]) | – | | +| >>>>Ω 0 | M | | BIT STRING
(SIZE(7)) | semi-circles (IS-
GPS-200 [43], IS-
GPS-705 [44], IS-
GPS-800 [45], IS-QZSS
[47]) | – | | +| >>>>Φ 0 | M | | BIT STRING
(SIZE(7)) | semi-circles (IS-
GPS-200 [43], IS-
GPS-705 [44], IS-
GPS-800 [45], IS-QZSS
[47]) | – | | +| >>>>L1 Health | M | | BIT STRING
(SIZE(1)) | dimensionless (IS-
GPS-200 [43], IS-
GPS-705 [44], IS-
GPS-800 [45], IS-QZSS
[47]) | – | | +| >>>>L2 Health | M | | BIT STRING
(SIZE(1)) | dimensionless (IS-
GPS-200 [43], IS-
GPS-705 [44], IS-
GPS-800 [45], IS-QZSS
[47]) | – | | +| >>>>L5 Health | M | | BIT STRING
(SIZE(1)) | dimensionless (IS-
GPS-200 [43], IS-
GPS-705 [44], IS-
GPS-800 [45], IS-QZSS
[47]) | – | | + +| | | | | | | | +|--|--|--|--|-------|--|--| +| | | | | [47]) | | | +|--|--|--|--|-------|--|--| + +| | | | | | | | +|----------------------------------|---|-------------------------------------|------------------------|--------------------------------------------------------------------------------------------------|-----|--------| +| >Midi Keplerian Parameters | | | | Model 4 | | | +| >>Keplerian Midi Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..255) | Scaling factor 2 12 s
Reference time of almanac within week in GANSS TOD time base | – | | +| >>>Satellite information MIDI-KP | | 1..
NSSSatA
lmanac> | | | – | | +| >>>>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [18]. | – | | +| >>>>e | M | | BIT STRING (SIZE(11)) | dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>δ i | M | | BIT STRING (SIZE(11)) | semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>Ω dot | M | | BIT STRING (SIZE (11)) | semi-circles/sec (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>sqrtA | M | | BIT STRING (SIZE(17)) | meters 1/2 (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>Ω 0 | M | | BIT STRING (SIZE(16)) | semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>ω | M | | BIT STRING (SIZE 16)) | semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>M 0 | M | | BIT STRING (SIZE(16)) | semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>a fo | M | | BIT STRING (SIZE(11)) | seconds (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>a fr | M | | BIT STRING (SIZE(10)) | sec/sec (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>L1 Health | M | | BIT STRING (SIZE(1)) | Dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>L2 Health | M | | BIT STRING (SIZE(1)) | dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | – | | +| >>>>L5 Health | M | | BIT STRING (SIZE(1)) | dimensionless (IS-GPS-200 [43], IS- | – | | + +| | | | | | | | +|--|--|--|--|----------------------------------------------|--|--| +| | | | | GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | | | +|--|--|--|--|----------------------------------------------|--|--| + +| | | | | | | | +|--------------------------------------|---|-------------------------------------|-----------------------|----------------------------------------|-----|--------| +| >GLONASS Keplerian Parameters | | | | Model 5 | | | +| >>Keplerian GLONASS | M | | | | YES | ignore | +| >>>Satellite information GLO-KP | | 1..
NSSSatA
Imanac> | | | — | | +| >>>>N A | M | | BIT STRING (SIZE(11)) | days [48] | — | | +| >>>>η A | M | | BIT STRING (SIZE(5)) | dimensionless [48] | — | | +| >>>>H n A | M | | BIT STRING (SIZE(5)) | dimensionless [48] | — | | +| >>>>λ n A | M | | BIT STRING (SIZE(21)) | semi-circles [48] | — | | +| >>>>t λ,n A | M | | BIT STRING (SIZE(21)) | seconds [48] | — | | +| >>>>Δi n A | M | | BIT STRING (SIZE(18)) | semi-circles [48] | — | | +| >>>>ΔT n A | M | | BIT STRING (SIZE(22)) | sec/orbit period [48] | — | | +| >>>>ΔT DOT,n A | M | | BIT STRING (SIZE(7)) | sec/orbit period 2 [48] | — | | +| >>>>ε n A | M | | BIT STRING (SIZE(15)) | dimensionless [48] | — | | +| >>>>ω n A | M | | BIT STRING (SIZE(16)) | semi-circles [48] | — | | +| >>>>τ n A | M | | BIT STRING (SIZE(10)) | seconds [48] | — | | +| >>>>C n A | M | | BIT STRING (SIZE(1)) | dimensionless [48] | — | | +| >>>>M n A | O | | BIT STRING (SIZE(2)) | dimensionless [48] | — | | +| >SBAS ECEF Parameters | | | | Model 6 | | | +| >>ECEF SBAS Almanac | M | | | | YES | ignore | +| >>>Satellite information SBAS-ECEF | | 1..
NSSSatA
Imanac> | | | — | | +| >>>>Data ID | M | | BIT STRING (SIZE(2)) | Dimensionless (DTFA01-96-C-00025 [46]) | — | | +| >>>>SV ID | M | | INTEGER (0..63) | Defined in TS 25.331 [18]. | — | | +| >>>>Health | M | | BIT STRING (SIZE(8)) | Dimensionless (DTFA01-96-C-00025 [46]) | — | | +| >>>>X G | M | | BIT STRING (SIZE(15)) | meters (DTFA01-96-C-00025 [46]) | — | | +| >>>>Y G | M | | BIT STRING (SIZE(15)) | meters (DTFA01-96-C-00025 [46]) | — | | +| >>>>Z G | M | | BIT STRING (SIZE(9)) | meters (DTFA01-96-C-00025 [46]) | — | | +| >>>>X G Rate-of-Change | M | | BIT STRING (SIZE(3)) | meters/sec (DTFA01-96-C-00025 [46]) | — | | +| >>>>Y G Rate-of-Change | M | | BIT STRING (SIZE(3)) | meters/sec (DTFA01-96-C-00025 [46]) | — | | +| >>>>Z G Rate-of-Change | M | | BIT STRING (SIZE(4)) | meters/sec (DTFA01-96-C-00025 [46]) | — | | +| >>>>t 0 | M | | BIT STRING (SIZE(11)) | seconds (DTFA01-96-C-00025 [46]) | — | | +| >BDS Keplerian Parameters | | | | Model 7. | | | +| >>Keplerian BDS | M | | | | YES | ignore | + +| | | | | | | | +|-------------------------------------------------|----------|--------------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Almanac | | | | | | | +| >>>Satellite information BDS-KP | | 1 to
NSSSatA
lmanac> | | | | | +| >>>>Sat ID | M | | INTEGER
(0..63) | Defined in TS 25.331 [16]. | – | | +| >>>>t oa | M | | BIT STRING
(SIZE(8)) | Almanac reference time (seconds) (BDS-SIS-ICD [51]). | – | | +| >>>>A 1/2 | M | | BIT STRING
(SIZE(24)) | Square root of semi-major axis (meters 1/2 ) (BDS-SIS-ICD [51]). | – | | +| >>>>e | M | | BIT STRING
(SIZE(17)) | Eccentricity, dimensionless (BDS-SIS-ICD [51]). | – | | +| >>>>ω | M | | BIT STRING
(SIZE(24)) | Argument of Perigee (semi-circles) (BDS-SIS-ICD [51]). | – | | +| >>>>M 0 | M | | BIT STRING
(SIZE(24)) | Mean anomaly at reference time (semi-circles) (BDS-SIS-ICD [51]). | – | | +| >>>>Ω 0 | M | | BIT STRING
(SIZE(24)) | Longitude of ascending node of orbital plane computed according to reference time (semi-circles) (BDS-SIS-ICD [51]). | – | | +| >>>>Ω_dot | M | | BIT STRING
(SIZE(17)) | Rate of right ascension (semi-circles/sec) (BDS-SIS-ICD [51]). | – | | +| >>>>δ i | M | | BIT STRING
(SIZE(16)) | Correction of orbit reference inclination at reference time (semi-circles) (BDS-SIS-ICD [51]). | – | | +| >>>>a 0 | M | | BIT STRING
(SIZE(11)) | Satellite clock bias (seconds) (BDS-SIS-ICD [51]). | – | | +| >>>>a 1 | M | | BIT STRING
(SIZE(11)) | Satellite clock rate (sec/sec) (BDS-SIS-ICD [51]). | – | | +| >>>>Health | C-Sat-ID | | BIT STRING
(SIZE(9)) | Satellite Health Information dimensionless (BDS-SIS-ICD [51]). | – | | +| Complete Almanac Provided | O | | BOOLEAN | This field indicates whether almanac is provided for the full GANSS constellation or not. TRUE means complete GANSS almanac is provided. | YES | ignore | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------------| +| Sat-ID | This IE shall be present if the IE "Sat ID" is between 0 and 29 and not needed otherwise. | + +| Range Bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxGANSSSatAlmanac | Maximum number of satellites for which data is included in the IE | + +#### 9.2.1.90 GANSS Clock Model + +The IE contains fields needed to model the GANSS clock parameters. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------|----------|----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------| +| Satellite Clock Model | | 1 to
| | Model -1
There may be more than one clock model included if defined in SIS ICD (e.g. two for Galileo) (OS SIS ICD [39]). | +| >t oc | M | | BIT STRING (SIZE(14)) | defined in (OS SIS ICD [39]) | +| >a 12 | M | | BIT STRING (SIZE(6)) | defined in (OS SIS ICD [39]) | +| >a 11 | M | | BIT STRING (SIZE(21)) | defined in (OS SIS ICD [39]) | +| >a 10 | M | | BIT STRING (SIZE(31)) | defined in (OS SIS ICD [39]) | +| >T GD | O | | BIT STRING (SIZE(10)) | Broadcast Group Delay(BGD) defined in (OS SIS ICD [39]) | +| >SISA | M | | BIT STRING (SIZE(8)) | Signal-In-Space Accuracy (SISA), defined in OS SIS ICD [39]. | +| >Model ID | O | | INTEGER(0..1,...) | Coded as defined in TS 25.331 [18]. | + +| Range bound | Explanation | +|------------------|--------------------------------------------------------------------------------| +| maxGANSSClockMod | Maximum number of satellite clock models for which data is included in the IE. | + +##### 9.2.1.90a GANSS Additional Clock Models + +The IE contains fields needed to model the GANSS clock parameters. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Additional Clock Models | | | | | +| >NAV-Clock Model | | | | Model-2 | +| >>t oc | M | | BIT STRING (SIZE(16)) | Time of clock (seconds) IS-QZSS [47] | +| >>af 2 | M | | BIT STRING (SIZE(8)) | Clock correction polynomial coefficient (sec/sec 2 ) IS-QZSS [47] | +| >>af 1 | M | | BIT STRING (SIZE(16)) | Clock correction polynomial coefficient (sec/sec) IS-QZSS [47] | +| >>af 0 | M | | BIT STRING (SIZE(22)) | Clock correction polynomial coefficient (seconds) IS-QZSS [47] | +| >>T GD | M | | BIT STRING (SIZE(8)) | Group delay (seconds) IS-QZSS [47] | +| >CNAV/CNAV-2 Clock Model | | | | Model-3 | +| >>t oc | M | | BIT STRING (SIZE(11)) | Clock data reference time of week (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>t op | M | | BIT STRING (SIZE(11)) | Clock data predict time of week (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>URA oc Index | M | | BIT STRING (SIZE(5)) | SV clock accuracy index (dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>URA oc1 Index | M | | BIT STRING (SIZE(3)) | SV clock accuracy change index (dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>URA oc2 Index | M | | BIT STRING (SIZE(3)) | SV clock accuracy change rate index (dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>a i2-n | M | | BIT STRING (SIZE(10)) | SV clock drift rate correction coefficient (sec/sec 2 ) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>a i1-n | M | | BIT STRING (SIZE(20)) | SV clock drift correction coefficient (sec/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>a i0-n | M | | BIT STRING (SIZE(26)) | SV clock bias correction coefficient (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>T GD | M | | BIT STRING (SIZE(13)) | Group delay correction (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>ISC L1CP | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-800 [45], IS-QZSS [47]) | +| >>ISC L1CD | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------| +| | | | | (seconds) (IS-GPS-800 [45], IS-QZSS [47]) | +| >>ISC L1C/A | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-QZSS [47]) | +| >>ISC L2C | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-QZSS [47]) | +| >>ISC L5I5 | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-705 [44], IS-QZSS [47]) | +| >>ISC L5Q5 | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-705 [44], IS-QZSS [47]) | +| >GLONASS Satellite Clock Model | | | | Model-4 | +| >>τ n (t b ) | M | | BIT STRING (SIZE(22)) | Satellite clock offset (seconds) [48] | +| >>γ n (t b ) | M | | BIT STRING (SIZE(11)) | Relative frequency offset from nominal value (dimensionless) [48] | +| >>Δτ n | O | | BIT STRING (SIZE(5)) | Time difference between transmission in G2 and G1 (seconds) [48] | +| >SBAS Satellite Clock Model | | | | Model-5 | +| >>t 0 | M | | BIT STRING (SIZE(13)) | (seconds) (DTFA01-96-C-00025 [46]) | +| >>a Gfo | M | | BIT STRING (SIZE(12)) | (seconds) (DTFA01-96-C-00025 [46]) | +| >>a Gf1 | M | | BIT STRING (SIZE(8)) | (sec/sec) (DTFA01-96-C-00025 [46]) | +| >BDS Satellite Clock Model | | | | Model-6. | +| >>t loc | M | | BIT STRING (SIZE(17)) | Time of clock (seconds) (BDS-SIS-ICD [51]). | +| >>a 0 | M | | BIT STRING (SIZE(24)) | Clock correction polynomial coefficient (seconds) (BDS-SIS-ICD [51]). | +| >>a 1 | M | | BIT STRING (SIZE(22)) | Clock correction polynomial coefficient (sec/sec) (BDS-SIS-ICD [51]). | +| >>a 2 | M | | BIT STRING (SIZE(11)) | Clock correction polynomial coefficient (sec/sec 2 ) (BDS-SIS-ICD [51]). | +| >>T GD1 | M | | BIT STRING (SIZE(10)) | Equipment Group Delay Differential (seconds) (BDS-SIS-ICD [51]). | +| >>AODC | M | | BIT STRING (SIZE(5)) | Age of data, clock (dimensionless) (BDS-SIS-ICD [51]). | + +#### 9.2.1.91 GANSS Ionospheric Model + +The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| $a_{i0}$ | M | | BIT STRING (SIZE(11)) | Effective Ionisation Level 1 st order parameter. This parameter is used as defined in (OS SIS ICD [39]) | +| $a_{i1}$ | M | | BIT STRING (SIZE(11)) | Effective Ionisation Level 2 nd order parameter. This parameter is used as defined in (OS SIS ICD [39]) | +| $a_{i2}$ | M | | BIT STRING (SIZE(14)) | Effective Ionisation Level 3 rd order parameter. This parameter is used as defined in (OS SIS ICD [39]) | +| GANSS Ionosphere Regional Storm Flags | | 0..1 | | | +| >Storm Flag 1 | M | | BOOLEAN | This parameter is used as defined in (OS SIS ICD [39]) | +| >Storm Flag 2 | M | | BOOLEAN | This parameter is used as defined in (OS SIS ICD [39]) | +| >Storm Flag 3 | M | | BOOLEAN | This parameter is used as defined in (OS SIS ICD [39]) | +| >Storm Flag 4 | M | | BOOLEAN | This parameter is used as defined in (OS SIS ICD [39]) | +| >Storm Flag 5 | M | | BOOLEAN | This parameter is used as defined in (OS SIS ICD [39]) | + +##### 9.2.1.91a GANSS Additional Ionospheric Model + +The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------| +| Data ID | M | | BIT STRING (SIZE(2)) | Coded as defined in TS 25.331 [18] | +| $\alpha_0$ | M | | BIT STRING (SIZE(8)) | seconds (IS-QZSS [47]) | +| $\alpha_1$ | M | | BIT STRING (SIZE(8)) | sec/semi-circle (IS-QZSS [47]) | +| $\alpha_2$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 2 (IS-QZSS [47]) | +| $\alpha_3$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 3 (IS-QZSS [47]) | +| $\beta_0$ | M | | BIT STRING (SIZE(8)) | seconds (IS-QZSS [47]) | +| $\beta_1$ | M | | BIT STRING (SIZE(8)) | sec/semi-circle (IS-QZSS [47]) | +| $\beta_2$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 2 (IS-QZSS [47]) | +| $\beta_3$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 3 (IS-QZSS [47]) | + +#### 9.2.1.92 GANSS Navigation Model + +Void. + +#### 9.2.1.93 GANSS Orbit Model + +This IE contains information for GANSS orbit model parameters. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------| +| CHOICE Orbit Model | M | | | | +| >Keplerian Parameters | | | | Model-1 | +| >>t oe | M | | BIT STRING (SIZE(14)) | Time-of-Ephemeris in seconds, scale factor 60 (OS SIS ICD [39]) | +| >>ω | M | | BIT STRING (SIZE(32)) | Argument of Perigee (semi-circles) (OS SIS ICD [39]) | +| >>Δn | M | | BIT STRING (SIZE(16)) | Mean Motion Difference From Computed Value (semi-circles/sec) (OS SIS ICD [39]) | +| >>M 0 | M | | BIT STRING (SIZE(32)) | Mean Anomaly at Reference Time (semi-circles) (OS SIS ICD [39]) | +| >>OMEGA dot | M | | BIT STRING (SIZE(24)) | Rate of change of right ascension (semi-circles/sec) (OS SIS ICD [39]) | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity, scale factor 2 -33 (OS SIS ICD [39]) | +| >>Idot | M | | BIT STRING (SIZE(14)) | Rate of change of Inclination Angle (semi-circles/sec) (OS SIS ICD [39]) | +| >>sqrtA | M | | BIT STRING (SIZE(32)) | Square root of Semi-Major Axis in (meters) 1/2 , scale factor 2 -19 (OS SIS ICD [39]) | +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination Angle at Reference Time (semi-circles) (OS SIS ICD [39]) | +| >>OMEGA 0 | M | | BIT STRING (SIZE(32)) | Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (OS SIS ICD [39]) | +| >>C rs | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [39]) | +| >>C is | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [39]) | +| >>C us | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [39]) | +| >>C rc | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [39]) | +| >>C ic | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [39]) | +| >>C uc | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [39]) | + +##### 9.2.1.93a GANSS Additional Orbit Models + +This IE contains information for GANSS orbit model parameters. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------| +| CHOICE Additional Orbit Models | | | | | +| >NAV-Keplerian Parameters | | | | Model-2 | +| >>URA Index | M | | BIT STRING (SIZE(4)) | SV accuracy (dimensionless) (IS-QZSS [47]) | +| >>Fit Interval Flag | M | | BIT STRING (SIZE(1)) | Fit interval indication (dimensionless) (IS-QZSS [47]) | +| >>t oe | M | | BIT STRING (SIZE(16)) | Time of ephemeris (seconds) (IS-QZSS [47]) | +| >>ω | M | | BIT STRING (SIZE(32)) | Argument of perigee (semi-circles) (IS-QZSS [47]) | +| >>Δn | M | | BIT STRING (SIZE(16)) | Mean motion difference from computed value (semi-circles/sec) (IS-QZSS [47]) | +| >>M 0 | M | | BIT STRING (SIZE(32)) | Mean anomaly at reference time (semi-circles) (IS-QZSS [47]) | +| >>OMEGAdot | M | | BIT STRING (SIZE(24)) | Rate of right ascension (semi-circles/sec) (IS-QZSS [47]) | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity (dimensionless) (IS-QZSS [47]) | +| >>Idot | M | | BIT STRING (SIZE(14)) | Rate of inclination angle (semi-circles/sec) (IS-QZSS [47]) | +| >>sqrtA | M | | BIT STRING (SIZE(32)) | Square root of semi-major axis (meters 1/2 ) (IS-QZSS [47]) | +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination angle at reference time (semi-circles) (IS-QZSS [47]) | +| >>OMEGA 0 | M | | BIT STRING (SIZE(32)) | Longitude of ascending node of orbit plane at weekly epoch (semi-circles) (IS-QZSS [47]) | +| >>C rs | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-QZSS [47]) | +| >>C is | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-QZSS [47]) | +| >>C us | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-QZSS [47]) | +| >>C rc | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-QZSS [47]) | +| >>C ic | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-QZSS [47]) | +| >>C uc | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-QZSS [47]) | +| >CNAV/CNAV-2 Keplerian Parameters | | | | Model-3 | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>t op | M | | BIT STRING (SIZE(11)) | Data predict time of week (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>URA oe Index | M | | BIT STRING (SIZE(5)) | SV accuracy (dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>ΔA | M | | BIT STRING (SIZE(26)) | Semi-major axis difference at reference time (meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>A_dot | M | | BIT STRING (SIZE(25)) | Chane rate in semi-major axis (meters/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>Δn 0 | M | | BIT STRING (SIZE(17)) | Mean motion difference from computed value at reference time (semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>Δn 0 _dot | M | | BIT STRING (SIZE(23)) | Rate of mean motion difference from computed value (semi-circles/sec 2 ) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>M 0-n | M | | BIT STRING (SIZE(33)) | Mean anomaly at reference time (semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>e n | M | | BIT STRING (SIZE(33)) | Eccentricity (dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>ω n | M | | BIT STRING (SIZE(33)) | Argument of perigee (semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>Ω 0-n | M | | BIT STRING (SIZE(33)) | Reference right ascension angle (semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>ΔΩ_dot | M | | BIT STRING (SIZE(17)) | Rate of right ascension difference (semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>i 0-n | M | | BIT STRING (SIZE(33)) | Inclination angle at reference time (semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>i 0-n _dot | M | | BIT STRING (SIZE(15)) | Rate of inclination angle (semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>C is-n | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>C ic-n | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>C rs-n | M | | BIT STRING (SIZE(24)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>C rc-n | M | | BIT STRING (SIZE(24)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>C us-n | M | | BIT STRING (SIZE(21)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>C uc-n | M | | BIT STRING (SIZE(21)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >GLONASS Earth-Centered, Earth-fixed Parameters | | | | Model-4 | +| >>E n | M | | BIT STRING (SIZE(5)) | Age of data (days) [48] | +| >>P1 | M | | BIT STRING (SIZE(2)) | Time interval between two adjacent values of t b (minutes) [48] | +| >>P2 | M | | BIT STRING (SIZE(1)) | Change of t b flag (dimensionless) [48] | +| >>M | O | | BIT STRING (SIZE(2)) | Type of satellite (dimensionless) [48] | +| >> | M | | BIT STRING (SIZE(27)) | x-coordinate of satellite at time t b (kilometers) [48] | +| >> | M | | BIT STRING (SIZE(24)) | x-coordinate of satellite velocity at time t b (kilometers/sec) [48] | +| >> | M | | BIT STRING (SIZE(5)) | x-coordinate of satellite acceleration at time t b (kilometers/sec 2 ) [48] | +| >> | M | | BIT STRING (SIZE(27)) | y-coordinate of satellite at time t b (kilometers) [48] | +| >> | M | | BIT STRING (SIZE(24)) | y-coordinate of satellite velocity at time t b (kilometers/sec) [48] | +| >> | M | | BIT STRING (SIZE(5)) | y-coordinate of satellite acceleration at time t b (kilometers/sec 2 ) [48] | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------------------------|--------------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| +| >> | M | | BIT STRING (SIZE(27)) | z-coordinate of satellite at time $t_b$ (kilometers) [48] | +| >> | M | | BIT STRING (SIZE(24)) | z-coordinate of satellite velocity at time $t_b$ (kilometers/sec) [48] | +| >> | M | | BIT STRING (SIZE(5)) | z-coordinate of satellite acceleration at time $t_b$ (kilometers/sec 2 ) [48] | +| >SBAS Earth-Centered, Earth-fixed Parameters | | | | Model-5 | +| >> $t_0$ | C-ClockModel | | BIT STRING (SIZE(13)) | Time of applicability (seconds) (DTFA01-96-C-00025 [46]) | +| >>Accuracy | M | | BIT STRING (SIZE(4)) | (dimensionless) (DTFA01-96-C-00025 [46]) | +| >> $X_G$ | M | | BIT STRING (SIZE(30)) | (meters) (DTFA01-96-C-00025 [46]) | +| >> $Y_G$ | M | | BIT STRING (SIZE(30)) | (meters) (DTFA01-96-C-00025 [46]) | +| >> $Z_G$ | M | | BIT STRING (SIZE(25)) | (meters) (DTFA01-96-C-00025 [46]) | +| >> $X_G$ Rate-of-Change | M | | BIT STRING (SIZE(17)) | (meters/sec) (DTFA01-96-C-00025 [46]) | +| >> $Y_G$ Rate-of-Change | M | | BIT STRING (SIZE(17)) | (meters/sec) (DTFA01-96-C-00025 [46]) | +| >> $Z_G$ Rate-of-Change | M | | BIT STRING (SIZE(18)) | (meters/sec) (DTFA01-96-C-00025 [46]) | +| >> $X_G$ Acceleration | M | | BIT STRING (SIZE(10)) | (meters/sec 2 ) (DTFA01-96-C-00025 [46]) | +| >> $Y_G$ Acceleration | M | | BIT STRING (SIZE(10)) | (meters/sec 2 ) (DTFA01-96-C-00025 [46]) | +| >> $Z_G$ Acceleration | M | | BIT STRING (SIZE(10)) | (meters/sec 2 ) (DTFA01-96-C-00025 [46]) | +| >BDS Keplerian Parameters | | | | Model-6. | +| >>URA Index | M | | BIT STRING (SIZE(4)) | SV accuracy (dimensionless) (BDS-SIS-ICD [51]). | +| >>toe | M | | BIT STRING (SIZE(17)) | Ephemeris reference time (seconds) (BDS-SIS-ICD [51]). | +| >> $A^{1/2}$ | M | | BIT STRING (SIZE(32)) | Square root of semi-major axis (meters 1/2 ) (BDS-SIS-ICD [51]). | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity (dimensionless) (BDS-SIS-ICD [51]). | +| >> $\omega$ | M | | BIT STRING (SIZE(32)) | Argument of perigee (semi-circles) (BDS-SIS-ICD [51]). | +| >> $\Delta n$ | M | | BIT STRING (SIZE(16)) | Mean motion difference from computed value (semi-circles/sec) (BDS-SIS-ICD [51]). | +| >> $M_0$ | M | | BIT STRING (SIZE(32)) | Mean anomaly at reference time (semi-circles) (BDS-SIS-ICD [51]). | +| >> $\Omega_0$ | M | | BIT STRING (SIZE(32)) | Longitude of ascending node of orbital of plane computed according to reference time (semi-circles) (BDS-SIS-ICD [51]). | +| >> $\Omega\_dot$ | M | | BIT STRING (SIZE(24)) | Rate of right ascension (semi-circles/sec) (BDS-SIS-ICD [51]). | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------| +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination angle at reference time (semi-circles) (BDS-SIS-ICD [51]). | +| >>ldot | M | | BIT STRING (SIZE(14)) | Rate of inclination angle (semi-circles/sec) (BDS-SIS-ICD [51]). | +| >>C uc | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (BDS-SIS-ICD [51]). | +| >>C us | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (BDS-SIS-ICD [51]). | +| >>C rc | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (BDS-SIS-ICD [51]). | +| >>C rs | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (BDS-SIS-ICD [51]). | +| >>C ic | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (BDS-SIS-ICD [51]). | +| >>C is | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (BDS-SIS-ICD [51]). | +| >>AODE | M | | BIT STRING (SIZE(5)) | Age of data,ephemeris (dimensionless) (BDS-SIS-ICD [51]). | + +| Condition | Explanation | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ClockModel | This IE shall be present if “SBAS Earth-Centered, Earth-fixed Parameters” (Model-5) in IE GANSS Additional Clock Models is not included in GANSS Additional Navigation Models IE. | + +#### 9.2.1.94 GANSS Real Time Integrity + +This IE contains parameters that describe the real-time status of the GANSS constellation. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------|----------|--------------------|-----------------------|-------------------------------------| +| Satellite Information | | 1 to | | | +| >Bad GANSS Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >Bad GANSS Signal ID | O | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [18]. | + +| Range Bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in the IE | + +#### 9.2.1.95 GANSS Receiver Geographical Position (GANSS RX Pos) + +The *GANSS Receiver Geographical Position IE* is used to identify the geographical coordinates of a GANSS receiver relevant for a certain Information Exchange Object. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED (North, South) | | +| Degrees of Latitude | M | | INTEGER (0..2 31 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{31} X / 90 < N+1$
X being the latitude in degree (0°.. 90°) | +| Degrees of Longitude | M | | INTEGER (-2 31 ..2 31 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{32} X / 360 < N+1$
X being the longitude in degree (-180°..+180°) | +| Direction of Altitude | M | | ENUMERATED (Height, Depth) | | +| Altitude | M | | INTEGER (0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | + +#### 9.2.1.96 GANSS Time Model + +The *GANSS Time Model IE* contains a set of parameters needed to relate GANSS time to selected time reference indicated by GNSS\_TO\_ID. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|---------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| GANSS Time Model Reference Time | M | | INTEGER(0..37799) | GANSS reference time (modulo 1 week) in seconds. The scale factor is $2^4$ | – | | +| $T_{A0}$ | M | | INTEGER(-2147483648..2147483647) | Seconds, scale factor $2^{-35}$ | – | | +| $T_{A1}$ | O | | INTEGER(-8388608..8388607) | sec/sec, scale factor $2^{-51}$ | – | | +| $T_{A2}$ | O | | INTEGER(-64..63) | sec/sec 2 , scale factor $2^{-68}$ | – | | +| GNSS_TO_ID | M | | ENUMERATED(GPS, ..., Galileo, QZSS, GLONASS, BDS) | | – | | +| Week Number | O | | INTEGER(0..8191) | Reference week of GANSS Time Model | – | | +| Delta_T | O | | INTEGER(-128..127) | This field specifies the integer seconds of the GNSS-GNSS Time Offset. Scale factor 1 second. | YES | ignore | + +##### 9.2.1.96a GANSS Additional Time Models + +The *GANSS Additional Time Models* IE contains a set of parameters needed to relate GANSS time to selected time references. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-----------------------------|----------|-----------------|-----------------------|-----------------------| +| GNSS-GNSS Time Model | | 1.. | | | +| >GANSS Time Model | | | 9.2.1.96 | | + +| Range Bound | Explanation | +|-------------|------------------------------------------------------------------------| +| maxGANSS-1 | Maximum number of GANSS systems for which data is included in this IE. | + +#### 9.2.1.97 GANSS UTC Model + +The *GANSS UTC Model* IE contains a set of parameters needed to relate GANSS time to Universal Time Coordinate (UTC). + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------|----------|-------|-----------------------|---------------------------| +| $A_1$ | M | | BIT STRING (SIZE(24)) | sec/sec (OS SIS ICD [39]) | +| $A_0$ | M | | BIT STRING (SIZE(32)) | seconds (OS SIS ICD [39]) | +| $t_{ot}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [39]) | +| $WN_t$ | M | | BIT STRING (SIZE(8)) | weeks (OS SIS ICD [39]) | +| $\Delta t_{LS}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [39]) | +| $WN_{LSF}$ | M | | BIT STRING (SIZE(8)) | weeks (OS SIS ICD [39]) | +| DN | M | | BIT STRING (SIZE(8)) | days (OS SIS ICD [39]) | +| $\Delta t_{LSF}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [39]) | + +##### 9.2.1.97a GANSS Additional UTC Models + +The *GANSS Additional UTC Models* IE contains several sets of parameters needed to relate GANSS time to Universal Time Coordinate (UTC), as defined in [43,44,45,46,47,48]. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Additional UTC Models | | | | | +| >Model Set 1 | | | | | +| >>A 0-n | M | | BIT STRING (SIZE(16)) | Bias coefficient of GNSS time scale relative to UTC time scale (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>A 1-n | M | | BIT STRING (SIZE(13)) | Drift coefficient of GNSS time scale relative to UTC time scale (sec/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>A 2-n | M | | BIT STRING (SIZE(7)) | Drift rate correction coefficient of GNSS time scale relative to UTC time scale (sec/sec 2 ) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | Current or past leap second count (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>t ot | M | | BIT STRING (SIZE(16)) | Time data reference time of week (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>WN ot | M | | BIT STRING (SIZE(13)) | Time data reference week number (weeks) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>WN LSF | M | | BIT STRING (SIZE(8)) | Leap second reference week number (weeks) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>DN | M | | BIT STRING (SIZE(4)) | Leap second reference day number (days) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | Current or future leap second count (seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47]) | +| >Model Set 2 | | | | | +| >>N A | M | | BIT STRING (SIZE(11)) | Calendar day number within four-year period beginning since the leap year (days) [48] | +| >>τ c | M | | BIT STRING (SIZE(32)) | GLONASS time scale correction to UTC(SU) (seconds) [48] | +| >>Delta UT1 | O | | | | +| >>>B1 | M | | BIT STRING (SIZE(11)) | Coefficient to determine ΔUT1 (seconds) [48] | +| >>>B2 | M | | BIT STRING (SIZE(10)) | Coefficient to determine ΔUT1 (seconds/msd) [48] | +| >>KP | O | | BIT STRING (SIZE(2)) | Notification of expected leap second correction | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------|----------|-------|-----------------------|---------------------------------------------------| +| | | | | (dimensionless) [48] | +| >Model Set 3 | | | | | +| >>A 1WNT | M | | BIT STRING (SIZE(24)) | sec/sec (DTFA01-96-C-00025 [46], Message Type 12) | +| >>A 0WNT | M | | BIT STRING (SIZE(32)) | seconds (DTFA01-96-C-00025 [46], Message Type 12) | +| >>t ot | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [46], Message Type 12) | +| >>WN t | M | | BIT STRING (SIZE(8)) | weeks (DTFA01-96-C-00025 [46], Message Type 12) | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [46], Message Type 12) | +| >>WN LSF | M | | BIT STRING (SIZE(8)) | weeks (DTFA01-96-C-00025 [46], Message Type 12) | +| >>DN | M | | BIT STRING (SIZE(8)) | days (DTFA01-96-C-00025 [46], Message Type 12) | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [46], Message Type 12) | +| >>UTC Standard ID | M | | BIT STRING (SIZE(3)) | dimensionless Coded as defined in TS 25.331 [18] | +| >Model Set 4 | | | | | +| >>A 0UTC | M | | BIT STRING (SIZE(32)) | Seconds (BDS-SIS-ICD [51]). | +| >>A 1UTC | M | | BIT STRING (SIZE(24)) | sec/sec (BDS-SIS-ICD [51]). | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | Seconds (BDS-SIS-ICD [51]). | +| >>WN LSF | M | | BIT STRING (SIZE(8)) | Weeks (BDS-SIS-ICD [51]). | +| >>DN | M | | BIT STRING (SIZE(8)) | Days (BDS-SIS-ICD [51]). | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | Seconds (BDS-SIS-ICD [51]). | + +#### 9.2.1.98 TUTRAN-GANSS Accuracy Class + +The TUTRAN-GANSS Accuracy Class IE indicates the accuracy class of the UTRAN GANSS Timing of Cell Frames for UE Positioning measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| T UTRAN-GANSS Accuracy Class | | | ENUMERATED ( Accuracy Class A, Accuracy Class B, Accuracy Class C, ...) | More information about T UTRAN-GANSS Measurement Accuracy Class is included in TS 25.133 [22] and TS 25.123 [23]. | + +#### 9.2.1.99 TUTRAN-GANSS Measurement Threshold Information + +The TUTRAN-GANSS Measurement Threshold Information IE defines the related thresholds for UTRAN GANSS Timing of Cell Frames for UE Positioning measurements shall trigger the event On Modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| T UTRAN-GANSS Change Limit | O | | INTEGER (1..256) | Change of T UTRAN-GANSS value compared to previously reported value, which shall trigger a new report.
Unit in 1/16 chip. | +| Predicted T UTRAN-GANSS Deviation Limit | O | | INTEGER (1..256) | Deviation of the predicted T UTRAN-GANSS from the latest measurement result, which shall trigger a new report.
Unit in 1/16 chip. | + +#### 9.2.1.100 TUTRAN-GANSS Measurement Value Information + +The TUTRAN-GANSS *Measurement Value Information* IE indicates the measurement results related to the UTRAN GANSS Timing of Cell Frames for UE Positioning measurements. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| $T_{UTRAN-GANSS}$ | M | | | Indicates the UTRAN GANSS Timing of Cell Frames for UE Positioning. According to mapping in TS 25.123 [23]; significant values range from 0 to 37158911999999. | – | | +| >MS | M | | INTEGER(0..16383) | Most Significant Part | – | | +| >LS | M | | INTEGER(0..4294967295) | Least Significant Part | – | | +| $T_{UTRAN-GANSS}$ Quality | O | | INTEGER(0..255) | Indicates the standard deviation (std) of the $T_{UTRAN-GANSS}$ measurements in 1/16 chip. $T_{UTRAN-GANSS}$ Quality = $\sqrt{E[(x-\mu)^2]} = \text{std}$ of reported $T_{UTRAN-GANSS}$ Value, where x is the reported $T_{UTRAN-GANSS}$ Value and $\mu = E[x]$ is the expectation value of x. | – | | +| $T_{UTRAN-GANSS}$ Drift Rate | M | | INTEGER(-50..50) | Indicates the $T_{UTRAN-GANSS}$ drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GANSS clock. | – | | +| $T_{UTRAN-GANSS}$ Drift Rate Quality | O | | INTEGER(0..50) | Indicates the standard deviation (std) of the $T_{UTRAN-GANSS}$ drift rate measurements in 1/256 chip per second. $T_{UTRAN-GANSS}$ Drift Rate Quality = $\sqrt{E[(x-\mu)^2]} = \text{std}$ of reported $T_{UTRAN-GANSS}$ Drift Rate, where x is the reported $T_{UTRAN-GANSS}$ Drift | – | | + +| | | | | | | | +|---------------|---|--|------------|------------------------------------------------------|-----|--------| +| | | | | Rate and $\mu = E[x]$ is the expectation value of x. | | | +| GANSS Time ID | O | | 9.2.1.104a | Absence of this IE means Galileo system time. | YES | ignore | + +#### 9.2.1.101 GANSS Reference Time + +Void. + +#### 9.2.1.102 HARQ Memory Partitioning + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|---------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE HARQ Memory Partitioning | | 1 | | | – | | +| >Implicit | | | | | | | +| >>Number of Processes | M | | INTEGER (1..8,...12,14,16) | For HARQ process IDs going from 0 to "Number of Processes" – 1 the Total number of soft channel bits TS 25.306 [33] is partitioned equally between all HARQ processes according to the rules in TS 25.331 [18]. | – | | +| >Explicit | | | | | | | +| >>HARQ Memory Partitioning Information | | 1.. | | The first instance of the parameter corresponds to HARQ process with identifier 0, the second instance to HARQ process with identifier 1, and so on. | – | | +| >>>Process Memory Size | M | | 9.2.1.49D | See TS 25.331 [18] | – | | +| >>HARQ Memory Partitioning Information Extension For MIMO | | 0, 4, 6 or 8 | | For FDD and 1.28Mcps TDD only
The 1 st instance corresponds to HARQ process with identifier set to "maxnoofHARQprocesses", the 2 nd instance to HARQ process with identifier set to "maxnoofHARQprocesses+1", and so on. | GLOBAL | ignore | +| >>>Process Memory Size | M | | 9.2.1.49D | See TS 25.331 [18] | – | | + +| Range Bound | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MaxnoofHARQprocesses | Maximum number of HARQ processes for one UE [FDD and 1.28Mcps TDD- per stream (the maximum number of HARQ processes per UE is 2 * MaxnoofHARQprocesses in dual stream transmission mode)] | + +#### 9.2.1.103 GANSS Data Bit Assistance + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|------------------|----------------------------|----------------------------------------------------------------------------------------------------------------| +| GANSS TOD | M | | INTEGER(0..59,...) | Reference time (modulo 1 minute) of the first bit of the data in Data Bits IE, in seconds. | +| Data Bit Assistance List | | 1.. | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >Data Bit Assistance Sgn List | | 1.. | | | +| >>GANSS Signal ID | M | | 9.2.1.106 | | +| >>Data Bits | M | | BIT STRING (SIZE(1..1024)) | Raw data bits as transmitted from a specific satellite at the time indicated by GANSS_TOD. See TS 25.331 [18]. | + +| Range Bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in the IE | +| maxSgnType | Maximum number of GANSS signals included in the IE | + +#### 9.2.1.104 GANSS ID + +This IE defines a particular GANSS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------| +| GANSS ID | M | | INTEGER(0..7 ,...) | Defines the GANSS and is coded as defined in TS 25.331 [18]. | + +##### 9.2.1.104a GANSS Time ID + +This IE defines a particular GANSS system time. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| GANSS Time ID | M | | INTEGER(0..7 ,...) | Defines the GANSS system time for the UTRAN GANSS Timing of Cell Frames for UE Positioning. Coded as defined in TS 25.331 [18], subclause 10.3.7.93a. | + +#### 9.2.1.105 GANSS Navigation Model And Time Recovery + +This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +|---------------|----------|-------|-----------------------|-----------------------| + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------|-----------------------|---------------------------------------------------------------------------------------------------| +| GANSS Transmission Time | M | | 9.2.1.107 | GANSS Time when the Navigation model has been retrieved | +| Non-Broadcast Indication | O | | ENUMERATED(true) | If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 | +| Satellite Information | | 1 to | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >SV Health | M | | BIT STRING (SIZE(9)) | Coded as defined in (OS SIS ICD [39]) | +| >IOD | M | | BIT STRING (SIZE(10)) | | +| >GANSS Clock Model | M | | 9.2.1.90 | | +| >GANSS Orbit Model | M | | 9.2.1.93 | | +| NOTE 1 : The Non-Broadcast Indication allows to inform that the navigation model is not bit-to-bit the one broadcast by the satellite. If it is set to 1, the UE is informed that techniques such as data wiping off applied to the navigation model may not work for instance. | | | | | + +| Range bound | Explanation | +|-------------|--------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in the IE. | + +##### 9.2.1.105a GANSS Additional Navigation Models And Time Recovery + +This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|--------------------------------|----------|------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| GANSS Transmission Time | M | | 9.2.1.107 | GANSS Time when the Navigation model has been retrieved | +| Non-Broadcast Indication | O | | ENUMERATED(true) | If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 in 9.2.1.105. | +| Satellite Information | | 1.. | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >SV Health | M | | BIT STRING (SIZE(6)) | Coded as defined in TS 25.331 [18]. | +| >IOD | M | | BIT STRING (SIZE(11)) | Coded as defined in TS 25.331 [18]. | +| >GANSS Additional Clock Models | M | | GANSS Additional Clock Models 9.2.1.90a | | +| >GANSS Additional Orbit Models | M | | GANSS Additional Orbit Models 9.2.1.93a | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64 | + +#### 9.2.1.106 GANSS Signal ID + +This IE defines a specific signal within a particular GANSS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|-------------------------------------| +| GANSS Signal ID | M | | INTEGER(0..7,...) | Coded as defined in TS 25.331 [18]. | + +#### 9.2.1.107 GANSS Transmission Time + +This IE indicates the GANSS Transmission Time + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GANSS Day | O | | INTEGER(0..8191) | The sequential number of days from the origin of the GNSS system time (indicated by the GANSS_ID given in the Requested Data Value IE ) modulo 8192 days (about 22 years). | +| GANSS TOD | M | | INTEGER(0..86399) | GANSS Time of Day in seconds | + +##### 9.2.1.107a GANSS Earth Orientation Parameters + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------| +| $t_{\text{eop}}$ | M | | BIT STRING (SIZE(16)) | EOP data reference time
(seconds) IS-GPS-200 [43] | +| PM_X | M | | BIT STRING (SIZE(21)) | X-axis polar motion value at reference time
(arc-seconds) IS-GPS-200 [43] | +| PM_X_dot | M | | BIT STRING (SIZE(15)) | X-axis polar motion drift at reference time
(arc-seconds/day) IS-GPS-200 [43] | +| PM_Y | M | | BIT STRING (SIZE(21)) | Y-axis polar motion value at reference time
(arc-seconds) IS-GPS-200 [43] | +| PM_Y_dot | M | | BIT STRING (SIZE(15)) | Y-axis polar motion drift at reference time
(arc-seconds/day) IS-GPS-200 [43] | +| $\Delta\text{UT1}$ | M | | BIT STRING (SIZE(31)) | UT1-UTC difference at reference time
(seconds) IS-GPS-200 [43] | +| $\Delta\text{UT1\_dot}$ | M | | BIT STRING (SIZE(19)) | Rate of UT1-UTC difference at reference time
(seconds/day) IS-GPS-200 [43] | + +##### 9.2.1.107b SBAS ID + +This IE defines a specific SBAS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|-----------------------| +| SBAS ID | M | | ENUMERATED(
WAAS,
EGNOS,
MSAS,
GAGAN, ... ) | | + +#### 9.2.1.107c GANSS Auxiliary Information + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------|----------|-----------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------| +| CHOICE GANSS-ID | | | | | +| >GANSS-ID-1 | | | | This choice may only be present if GANSS ID indicated "Modernized GPS" | +| >>Aux Info List | | 1 ..
| | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >>>Signals Available | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [18]. | +| >GANSS-ID-3 | | | | This choice may be present if GANSS ID indicated "GLONASS" | +| >>Aux Info List | | 1 ..
| | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [18]. | +| >>>Signals Available | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [18]. | +| >>>Channel Number | M | | INTEGER (-7..13) | This field indicates the GLONASS carrier frequency number of the satellite identified by Sat ID , as defined in [48]. | + +| Range Bound | Explanation | +|-------------|---------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of GANSS satellites for which data is included in this IE. | + +##### 9.2.1.107d Additional Ionospheric Model Request + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------| +| Additional Ionospheric Model Request | M | | BIT STRING (SIZE(2)) | Data ID for GANSS Additional Ionospheric Model as defined in TS 25.331 [18], subclause 10.3.7.92b. | + +#### 9.2.1.107e Earth Orientation Parameters Request + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| Earth Orientation Parameters Request | M | | BOOLEAN | True means requested. | + +##### 9.2.1.107f GANSS Additional Navigation Models And Time Recovery Request + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Additional Navigation Models And Time Recovery Request | M | | BOOLEAN | True means requested. | + +##### 9.2.1.107g GANSS Additional UTC Models Request + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Additional UTC Models Request | M | | BOOLEAN | True means requested. | + +##### 9.2.1.107h GANSS Auxiliary Information Request + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Auxiliary Information Request | M | | BOOLEAN | True means requested. | + +#### 9.2.1.108 IP Multicast Indication + +The *IP Multicast Indication* IE indicates the IP multicast group information dedicated to an MBMS service and the CFN Offset, defined as the offset between MFN and CFN for a FACH. When Node B receives such an indication, if supported, it may join the corresponding IP multicast group. When Node B receives data frame from this IP multicast group, it shall consider the value of the CFN field in the data frame as MFN and calculate the actual CFN for the concerned FACH according to following equation: + +$$\text{CFN} = (\text{MFN} - \text{CFN Offset}) \bmod 256.$$ + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------| +| Transport Layer Address | M | | 9.2.1.63 | An MBMS service corresponds to a dedicated IP multicast address. | +| Binding ID | M | | 9.2.1.4 | Indicating multicast port. | +| CFN Offset | M | | INTEGER (0..255) | | + +#### 9.2.1.109 IP Multicast Data Bearer Indication + +The *IP Multicast Data Bearer Indication* IE indicates whether the Node B is ready for receiving concerned MBMS service data through IP multicast transport bearer. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------| +| IP Multicast Data Bearer Indication | | | BOOLEAN | True: IP multicast data bearer is used.
False: IP multicast data bearer is not used. | + +#### 9.2.1.110 SixtyfourQAM DL Capability + +This parameter defines the SixtyfourQAM downlink capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-------------------------------------------------------------------------|-----------------------| +| SixtyfourQAM DL Capability | | | ENUMERATED
(SixtyfourQAM DL Capable,
SixtyfourQAM DL Non-Capable) | | + +#### 9.2.1.111 FACH Measurement Occasion Cycle Length Coefficient + +The *FACH Measurement Occasion Cycle Length Coefficient* IE provides information used for MAC-hs scheduling decision for MAC-c PDU in Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------| +| FACH Measurement Occasion Cycle Length Coefficient | | | INTEGER (1..12) | | + +#### 9.2.1.112 MAC-ehs Reset Timer + +The *MAC-ehs Reset Timer* IE is used as Reset Timer(Treset) described in ref TS 25.321 [32] subclause 11.6.4.5. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| MAC-ehs Reset Timer | | | ENUMERATED (1, 2, 3, 4, ...) | Timer in multiples of T1 values (milliseconds). Used when MAC-ehs reordering queue is reset in CELL_FACH and CELL_PCH | + +#### 9.2.1.113 Paging MAC Flow ID + +Paging MAC Flow ID is the unique identifier for one Paging MAC flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| Paging MAC Flow ID | | | INTEGER (0..3) | | + +#### 9.2.1.114 Enhanced FACH Capability + +This parameter defines the Enhanced FACH capability for a Local Cell. [1.28Mcps TDD - This parameter defines the Enhanced FACH capability for both uplink and downlink] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|------------------------------------------------------------------|-----------------------| +| Enhanced FACH Capability | | | ENUMERATED
(Enhanced FACH Capable, Enhanced FACH Non-Capable) | | + +#### 9.2.1.115 Enhanced PCH Capability + +This parameter defines the Enhanced PCH capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| | | | | | + +| | | | | | +|-------------------------|--|--|----------------------------------------------------------------|--| +| Enhanced PCH Capability | | | ENUMERATED
(Enhanced PCH Capable, Enhanced PCH Non-Capable) | | +|-------------------------|--|--|----------------------------------------------------------------|--| + +#### 9.2.1.116 Enhanced UE DRX Capability + +This parameter defines the Enhanced UE DRX capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|----------------------------------------------------------------------|-----------------------| +| Enhanced UE DRX Capability | | | ENUMERATED
(Enhanced UE DRX Capable, Enhanced UE DRX non Capable) | | + +#### 9.2.1.117 Priority Queue Information for Enhanced FACH/PCH + +The *Priority Queue Information for Enhanced FACH/PCH* IE provides information associated to HSDPA Priority Queue used for Enhanced FACH and/or Enhanced PCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|------------------------------------|------------------------------------------| +| Priority Queue ID | M | | 9.2.1.49C | | +| Scheduling Priority Indicator | M | | 9.2.1.53H | | +| T1 | M | | 9.2.1.56a | | +| MAC-ehs Reset Timer | M | | 9.2.1.112 | | +| Discard Timer | O | | 9.2.1.24E | Shall be ignored in case of Enhanced PCH | +| MAC-hs Window Size | M | | 9.2.1.38B | | +| Maximum MAC-c PDU Size | M | | MAC PDU Size Extended
9.2.1.38C | | + +#### 9.2.1.118 MIMO Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|------------------------------------------------|-----------------------| +| MIMO Capability | | | ENUMERATED
(MIMO Capable, MIMO Non-Capable) | | + +#### 9.2.1.119 MIMO Activation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| MIMO Activation Indicator | M | | NULL | | + +#### 9.2.1.120 MIMO Mode Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|--------------------------------------|-----------------------| +| MIMO Mode Indicator | | | ENUMERATED
(Activate, Deactivate) | | + +#### 9.2.1.121 SixtyfourQAM DL and MIMO Combined Capability + +This parameter defines the SixtyfourQAM downlink and MIMO combined capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------|-----------------------| +| SixtyfourQAM DL and MIMO Combined Capability | | | ENUMERATED (SixtyfourQAM DL and MIMO Combined Capable, SixtyfourQAM DL and MIMO Combined Non-Capable) | | + +#### 9.2.1.122 DL RLC PDU Size Format + +The *DL RLC PDU Size Format* IE indicates the downlink RLC PDU size format used for a Priority Queue. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|--------------------------------------------------------------|-----------------------| +| DL RLC PDU Size Format | | | ENUMERATED ( Fixed RLC PDU size, Flexible RLC PDU size ,...) | | + +#### 9.2.1.123 UE Aggregate Maximum Bit Rate + +The *UE Aggregate Maximum Bit Rate* IE is applicable for all Non-GBR bearers per UE which is defined for the Downlink and the Uplink direction and provided by the CN to the RNC. At least one of the *UE Aggregate Maximum Bit Rate Downlink* IE and *UE Aggregate Maximum Bit Rate Uplink* IE shall be included in the *UE Aggregate Maximum Bit Rate* IE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Aggregate Maximum Bit Rate | | | | Desc:
Applicable for non-GBR bearers | +| >UE Aggregate Maximum Bit Rate Downlink | O | | INTEGER (1..1,000,000 ,000) | Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in DL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present. | +| >UE Aggregate Maximum Bit Rate Uplink | O | | INTEGER (1..1,000,000 ,000) | Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in UL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present. | + +#### 9.2.1.124 Dormant Mode Indicator + +The *Dormant Mode Indicator* IE controls the dormant mode for the cell. In dormant mode there is no power transmitted in the cell, but the cell remains existing in the Node B. When *Dormant Mode Indicator* IE = "Enter Dormant Mode" the + +Node B is requested to reconfigure the cell to dormant mode. When *Dormant Mode Indicator* IE = "Leave Dormant Mode" the Node B is requested to take the cell into normal service. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-------------------------------------------------------------|-----------------------| +| Dormant Mode Indicator | | | ENUMERATED
(Enter Dormant Mode, Leave Dormant Mode, ...) | | + +#### 9.2.1.125 DGNSS Validity Period + +This IE defines the validity period of the GNSS differential corrections provided in *DGPS corrections* and *DGANSS corrections* IEs + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UDRE Growth Rate | M | | Enumerated(
UDRE growth 1.5,
UDRE growth 2,
UDRE growth 4,
UDRE growth 6,
UDRE growth 8,
UDRE growth 10,
UDRE growth 12,
UDRE growth 16) | This field provides an estimate of the growth rate of uncertainty ( $1-\sigma$ ) in the corrections. The UDRE at time value specified in the Time of Validity for UDRE Growth Rate field is the value of this field times the value of UDRE provided in DGPS Corrections or DGANSS corrections IE (TS 25.331 [18]). | +| Time of Validity for UDRE Growth Rate | M | | Enumerated(
val20sec,
val40sec,
val80sec,
val160sec,
val320sec,
val640sec,
val1280sec,
val2560sec) | This field specifies the time when the UDRE Growth Rate field applies (TS 25.331 [18]). | + +#### 9.2.1.126 E-RNTI Release Status + +Indicates the E-RNTI is released or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|----------------------------------------|-----------------------| +| E-RNTI Release Status | | | ENUMERATED
(released, not-released) | | + +#### 9.2.1.127 DBDS Corrections + +This IE contains the DBDS differential corrections. + +| Information Element/Group name | Need | Multi | Type and Reference | Semantics description | +|--------------------------------|------|---------------------|---------------------------------|------------------------------------------------------------------------------------------| +| DBDS Reference Time | M | | Integer(0..3 570 by step of 30) | Seconds.
Time in BDS system time (modulo 3600 s) when the DBDS corrections are valid. | +| DBDS information | | 1 to | | | +| >DBDS Signal ID | O | | 9.2.1.106 | Absence of this IE means the B1I. | +| >DBDS signal information | | 1 to | | | +| >>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [18]. | +| >>UDREI | M | | INTEGER (0..15) | User Differential Range Error Index (dimensionless) (BDS-SIS-ICD [51]). | +| >>RURAI | M | | INTEGER (0..15) | BDS Regional User Range Accuracy Index, (dimensionless) (BDS-SIS-ICD [51]). | +| >>Δt | M | | BIT STRING (SIZE(13)) | Equivalent Clock Correction, (meters) (BDS-SIS-ICD [51]) | + +#### 9.2.1.128 BDS Ionospheric Grid Model + +This IE contains Ionospheric Grid information to calculate the propagation delays of the BII signals through the ionosphere. + +| Information Element/Group name | Need | Multi | Type and Reference | Semantics description | +|----------------------------------|------|-------------------|---------------------------------|---------------------------------------------------------------------------------------------------------| +| BDS Reference Time | M | | INTEGER (0..3570 by step of 30) | Seconds.
Time in BDS system time (modulo 3600 s) when the BDS Ionospheric Grid Information is valid. | +| BDS Ionospheric Grid Information | | 1 to | | The maximum number of grid points that can be included in this version of the specification is 16. | +| >IGP number | M | | INTEGER (1..320) | Ionospheric grid point number (dimensionless) (BDS-SIS-ICD [51]). | +| >Vertical Delay | M | | BIT STRING (SIZE(9)) | Vertical Delay at Ionospheric Grid Points ,(meters) (BDS-SIS-ICD [51]) | +| >GIVEI | M | | BIT STRING (SIZE(4)) | Grid Ionospheric Vertical Error Index (dimensionless) (BDS-SIS-ICD [51]). | + +| Range bound | Explanation | +|-------------|----------------------------------------------------| +| maxIGPInfo | Maximum number of ionospheric grid points for BDS. | + +#### 9.2.1.129 Improved Synchronized RRC Indicator + +The Improved Synchronized RRC Indicator is used to handle the improved synchronized RRC procedures. + +| Information Element/Group name | Need | Multi | Type and Reference | Semantics description | +|-------------------------------------|------|-------|--------------------|-----------------------| +| Improved Synchronized RRC Indicator | M | | ENUMERATED (true) | | + +### 9.2.2 FDD specific parameters + +#### 9.2.2.a ACK-NACK Repetition Factor + +The *ACK-NACK Repetition Factor* IE indicates the number of consecutive repetitions of the ACK and NACK. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| ACK-NACK Repetition Factor | | | INTEGER (1..4,...) | Step: 1 | + +#### 9.2.2.b ACK Power Offset + +The *ACK Power Offset* IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ ACK information and the associated DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------|-------------------------------------------------------------| +| ACK Power Offset | | | INTEGER (0..8,..., 9..10) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1. | + +#### 9.2.2.A Active Pattern Sequence Information + +Defines the parameters for the compressed mode gap pattern sequence activation. For details see ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|----------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CM Configuration Change CFN | M | | CFN 9.2.1.7 | | | | +| Transmission Gap Pattern Sequence Status | | 0.. | | | - | | +| >TGPS Identifier | M | | INTEGER (1..maxTGPS) | If the group is not present, none of the pattern sequences are activated. References an already defined sequence. | - | | +| >TGPRC | M | | INTEGER (0..511) | The number of transmission gap patterns within the Transmission Gap Pattern Sequence. "0"=Infinity | - | | +| >TGCFN | M | | CFN 9.2.1.7 | Connection Frame Number of the first frame of the first pattern 1 within the Transmission Gap Pattern Sequence. | - | | +| >Affected HS-DSCH serving cell List | | 0.. | | The HS-DSCH serving cells affected by the TGPS when activating frequency specific compressed mode. Max 4 in this 3GPP release. | EACH | reject | +| >>C-ID | M | | 9.2.1.9 | | - | | + +| Range Bound | Explanation | +|----------------------|-----------------------------------------------------------------------------------| +| maxTGPS | Maximum number of active pattern sequences. Value 6. | +| maxNrOfHSDSCH | Maximum number of Primary Serving plus Secondary Serving HS-DSCH cells for one UE | + +#### 9.2.2.B Adjustment Period + +The *Adjustment Period* IE defines the period to be used for power balancing. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Adjustment Period | | | INTEGER (1..256) | Unit: Frames | + +#### 9.2.2.C Adjustment Ratio + +The *Adjustment Ratio* IE (*Radji*) defines the convergence rate used for the associated Adjustment Period. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------|-----------------------------------------| +| Adjustment Ratio | | | INTEGER (0..100) | Unit: None
Range: 0..1
Step: 0.01 | + +#### 9.2.2.D AICH Power + +The *AICH Power* IE indicates a power level (measured as the power per transmitted acquisition indicator when several AIs are transmitted in parallel) relative to the primary CPICH power configured in a cell. If Transmit Diversity is applied to the AICH, the *AICH Power* IE indicates the power offset between the linear sum of the power for the AICH on all branches and the Primary CPICH power configured in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------------------------------| +| AICH Power | | | INTEGER (-22..+5) | Unit: dB
Range: -22 .. +5 dB
Step: 1 dB | + +#### 9.2.2.1 AICH Transmission Timing + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| AICH Transmission Timing | | | ENUMERATED (0, 1) | See parameter AICH_Transmission_Timing in ref. TS 25.211 [7]. | + +##### 9.2.2.1A AP Preamble Signature + +Void. + +##### 9.2.2.1B AP Sub Channel Number + +Void. + +#### 9.2.2.1Ba Best Cell Portions + +*Best Cell Portions* IE indicates the best received cell portions and their SIR values when Cell Portions are defined in the cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|--------------------------------|-----------------------|-----------------------------------------------------------| +| Best Cell Portions | | 1.. | | | +| >Cell Portion ID | M | | 9.2.2.1Ca | | +| >SIR Value | M | | INTEGER (0..63) | According to mapping in TS 25.133 [22] and TS 25.123 [23] | + +| Range Bound | Explanation | +|-------------------------|--------------------------------------------------------| +| maxnoofBestCellPortions | Maximum number of reported Best Received Cell Portions | + +#### 9.2.2.1Bb Bundling Mode Indicator + +The Bundling Mode Indicator indicates whether the bundling shall be done or shall not be done for Iub. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-------------------------------------|---------------------------------------------------------------------| +| Bundling Mode Indicator | | | ENUMERATED ( Bundling, No bundling) | The value "Bundling" is applicable only when E-TTI indicates "2ms". | + +#### 9.2.2.1C CD Sub Channel Numbers + +Void. + +#### 9.2.2.1Ca Cell Portion ID + +Cell Portion ID is the unique identifier for a cell portion within a cell. See TS 25.215 [4]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|-----------------------| +| Cell Portion ID | | | INTEGER (0..63,...) | | + +#### 9.2.2.1D Channel Assignment Indication + +Void. + +#### 9.2.2.2 Chip Offset + +The Chip Offset is defined as the radio timing offset inside a radio frame. The Chip offset is used as offset relative to the Primary CPICH timing for the DL DPCH or for the F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Chip Offset | | | INTEGER (0..38399) | Unit: chips | + +#### 9.2.2.2A Closed Loop Timing Adjustment Mode + +Indicates when the phase/amplitude adjustment is performed in the DL in relation to the receipt of the UL feedback command in case of closed loop mode transmit diversity on DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-------------------------------------|-------------------------------------------------------------------------------------------------------------| +| Closed Loop Timing Adjustment Mode | | | ENUMERATED ( Offset1, Offset2, ...) | According to ref. TS 25.214 [10] subclause 7.1:
"Offset1" = slot(j+1)mod15
"Offset2" = slot(j+2)mod15 | + +#### 9.2.2.3 Common Channels Capacity Consumption Law + +Void. + +#### 9.2.2.3A Compressed Mode Deactivation Flag + +The Compressed Mode Deactivation Flag indicates whether Compressed Mode shall be deactivated or not in the new RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-------------------------------------------|-----------------------| +| Compressed Mode Deactivation Flag | | | ENUMERATED ( Deactivate, Maintain Active) | | + +#### 9.2.2.4 Compressed Mode Method + +Void. + +#### 9.2.2.4A CPCH Allowed Total Rate + +Void. + +##### 9.2.2.4B CPCH Scrambling Code Number + +Void. + +#### 9.2.2.4C CPCH UL DPCCH Slot Format + +Void. + +#### 9.2.2.4Ca CQI Power Offset + +The *CQI Power Offset* IE indicates Power offset used in the UL between the HS-DPCCH slots carrying CQI information and the associated DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------|-------------------------------------------------------------| +| CQI Power Offset | | | INTEGER (0..8,..., 9..10) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1. | + +##### 9.2.2.4Cb CQI Repetition Factor + +The *CQI Repetiton Factor* IE indicates the number of consecutive repetitions of the CQI. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| CQI Repetition Factor | | | INTEGER (1..4,...) | Step: 1 | + +#### 9.2.2.4D DCH FDD Information + +The *DCH FDD Information* IE provides information for DCHs to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------------------------------|-----------------------|-----------------------|-------------|----------------------| +| DCH FDD Information | | 1..<maxNrOfDCHs> | | | – | | +| >Payload CRC Presence Indicator | M | | 9.2.1.49 | | – | | +| >UL FP Mode | M | | 9.2.1.66 | | – | | +| >ToAWS | M | | 9.2.1.61 | | – | | +| >ToAWE | M | | 9.2.1.60 | | – | | +| >DCH Specific Info | | 1..<maxNrOfDCHs> | | | – | | +| >>DCH ID | M | | 9.2.1.20 | | – | | +| >>Transport Format Set | M | | 9.2.1.59 | For UL | – | | +| >>Transport Format Set | M | | 9.2.1.59 | For DL | – | | +| >>Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >>Frame Handling Priority | M | | 9.2.1.30 | | – | | +| >>QE-Selector | M | | 9.2.1.50A | | – | | +| >>Unidirectional DCH Indicator | O | | 9.2.1.68 | | YES | reject | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | + +| Range Bound | Explanation | +|--------------------|-----------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for one UE | + +#### 9.2.2.4E DCHs FDD To Modify + +The *DCHs FDD To Modify* IE provides information for DCHs to be modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------------------------------|-----------------------|-----------------------|-------------|----------------------| +| DCHs FDD To Modify | | 1..<maxNrOfDCHs> | | | – | | +| >UL FP Mode | O | | 9.2.1.66 | | – | | +| >ToAWS | O | | 9.2.1.61 | | – | | +| >ToAWE | O | | 9.2.1.60 | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >DCH Specific Info | | 1..<maxNrOfDCHs> | | | – | | +| >>DCH ID | M | | 9.2.1.20 | | – | | +| >>Transport Format Set | O | | 9.2.1.59 | For the UL. | – | | +| >>Transport Format Set | O | | 9.2.1.59 | For the DL. | – | | +| >>Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >>Frame Handling Priority | O | | 9.2.1.30 | | – | | +| >>Unidirectional DCH Indicator | O | | 9.2.1.68 | | YES | reject | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | + +| Range Bound | Explanation | +|--------------------|-----------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for one UE | + +#### 9.2.2.4F DCH Indicator For E-DCH-HSDPA Operation + +The DCH Indicator For E-DCH-HSDPA Operation parameter indicates whether *DCH Information* IE should be ignored in the message in which the *DCH Indicator For E-DCH-HSDPA Operation* IE is included. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|---------------------------------|-----------------------| +| DCH Indicator For E-DCH-HSDPA Operation | | | ENUMERATED
(DCH not present) | | + +#### 9.2.2.4G Transport Bearer Not Requested Indicator + +The Transport Bearer Not Requested Indicator parameter indicates that a transport bearer shall not be established or may not to be established for a DCH or an E-DCH MAC-d flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|-------|----------------------------------------------------------------------------------------------------|-----------------------| +| Transport Bearer Not Requested Indicator | | | ENUMERATED
(Transport Bearer shall not be Established, Transport Bearer may not be Established) | | + +#### 9.2.2.4H Transport Bearer Not Setup Indicator + +The Transport Bearer Not Setup Indicator parameter indicates that a transport bearer will not be established for a DCH or an E-DCH MAC-d flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|--------------------------------------------|-----------------------| +| Transport Bearer Not Setup Indicator | | | ENUMERATED
(Transport Bearer Not Setup) | | + +#### 9.2.2.5 D-Field Length + +Void. + +#### 9.2.2.6 Dedicated Channels Capacity Consumption Law + +Void. + +#### 9.2.2.7 Diversity Control Field + +Void. + +#### 9.2.2.8 Diversity Indication + +Void. + +#### 9.2.2.9 Diversity Mode + +Define the diversity mode to be applied. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Diversity Mode | | | ENUMERATED (
None,
STTD,
Closed loop mode 1,
Not Used,...) | The Diversity Mode IE shall never be set to "Not Used". If received it shall be rejected. | + +#### 9.2.2.10 DL DPCH Slot Format + +Indicates the slot format used in DPCH in DL, accordingly to ref. TS 25.211 [7]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|----------------------------|-----------------------| +| DL DPCH Slot Format | | | INTEGER (0..16,...,17..18) | | + +#### 9.2.2.10A DL DPCH Timing Adjustment + +The DL DPCH Timing Adjustment indicates that a timing adjustment of the related radio link is required or that an Initial DL DPCH Timing Adjustment has been performed by the Node B. It also indicates whether the timing adjustment consists of a timing advance or a timing delay with respect to the SFN timing. The adjustment always consists of 256 chips. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|--------------------------------------------|-------------------------------------------------| +| DL DPCH Timing Adjustment | | | ENUMERATED ( timing advance, timing delay) | The size of the timing adjustment is 256 chips. | + +#### 9.2.2.11 DL frame type + +Void. + +#### 9.2.2.12 DL or Global Capacity Credit + +Void. + +##### 9.2.2.12A DL\_power\_averaging\_window\_size + +The *DL\_power\_averaging\_window\_size* IE defines the window size when Limited Power Increase is used (TS 25.214 [10]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------| +| DL_power_averaging_window_size | | | INTEGER (1..60) | Unit: inner loop power adjustments
Range: 1..60
Step: 1 adjustment | + +#### 9.2.2.12B DL Power Balancing Information + +The *DL Power Balancing Information* IE provides information for power balancing to be activated in the relevant RL(s). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------------------|-----------------|-----------------------|----------------------------| +| Power Adjustment Type | M | | 9.2.2.27 | | +| DL Reference Power | C-Common | | DL Power
9.2.1.21 | Power on DPCH or on F-DPCH | +| DL Reference Power Information | C-Individual | 1.. | | | +| >RL ID | M | | 9.2.1.53 | | +| >DL Reference Power | M | | DL Power
9.2.1.21 | Power on DPCH or on F-DPCH | +| Max Adjustment Step | C-CommonOrIndividual | | 9.2.2.20 | | +| Adjustment Period | C-CommonOrIndividual | | 9.2.2.B | | +| Adjustment Ratio | C-CommonOrIndividual | | 9.2.2.C | | + +| Condition | Explanation | +|--------------------|----------------------------------------------------------------------------------------------------| +| Common | The IE shall be present if the Power Adjustment Type IE is set to "Common". | +| Individual | The IE shall be present if the Power Adjustment Type IE is set to "Individual". | +| CommonOrIndividual | The IE shall be present if the Power Adjustment Type IE is set to "Common" or "Individual". | + +| Range Bound | Explanation | +|-------------------|----------------------------------------| +| maxNrOfRLs | Maximum number of Radio Links for a UE | + +#### 9.2.2.12C DL Power Balancing Activation Indicator + +The *DL Power Balancing Activation Indicator* IE indicates that the power balancing is activated in the RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-------------------------------------------|-----------------------| +| DL Power Balancing Activation Indicator | | | ENUMERATED (DL Power Balancing Activated) | | + +#### 9.2.2.12D DL Power Balancing Updated Indicator + +The *DL Power Balancing Updated Indicator* IE indicates that the power balancing related parameters is updated in the RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------------------------|-----------------------| +| DL Power Balancing Updated Indicator | | | ENUMERATED (DL Power Balancing Updated) | | + +#### 9.2.2.13 DL Scrambling Code + +DL scrambling code to be used by the RL. One cell may have multiple DL scrambling codes available. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------| +| DL Scrambling Code | | | INTEGER (0..15) | "0" = Primary scrambling code of the cell
"1".."15" = Secondary scrambling code | + +#### 9.2.2.13A DL TPC Pattern 01 Count + +The *DL TPC Pattern 01 Count* IE contains the value of the parameter n, which is used for determining the DL TPC pattern on Radio Links marked with "first RLS" by the *First RLS indicator* IE before UL synchronisation is achieved. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| DL TPC Pattern 01 Count | | | INTEGER(0..30,...) | | + +#### 9.2.2.13B DSCH FDD Information + +Void. + +#### 9.2.2.13C DPC Mode + +The *DPC Mode* IE indicates the DPC mode to be applied TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DPC Mode | | | ENUMERATED ( Mode0, Mode1, ...) |

"Mode0": The Node B shall estimate the UE transmitted TPC command and update the DL power in every slot

"Mode1": The Node B shall estimate the UE transmitted TPC command over three slots and shall update the DL power in every three slots

| + +#### 9.2.2.13D DSCH FDD Common Information + +Void. + +#### 9.2.2.13Da E-DCH FDD Information + +The *E-DCH FDD Information* IE provides information for an E-DCH to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|-------------------------------|-------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH MAC-d Flows Information | M | | 9.2.2.13M | | – | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | If this IE is not included, scheduled transmission in all HARQ processes is allowed. | – | | +| E-DCH Maximum Bitrate | O | | 9.2.2.13T | | – | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | – | | +| E-DCH Reference Power Offset | O | | 9.2.2.13Y | | – | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | YES | ignore | +| SixteenQAM UL Operation Indicator | O | | 9.2.2.88A | | YES | reject | +| E-AGCH Table Choice | C-
SixteenQAM UL Operation | | 9.2.2.100 | If the SixteenQAM UL operation is not configured for this UE, Table 16B for E-AGCH in TS 25.212 [8] shall be used. | YES | ignore | +| SixtyfourQAM UL Operation Indicator | O | | 9.2.2.88C | | YES | reject | +| UL MIMO Information | O | | 9.2.2.177 | | YES | reject | +| UPH Filtering Measurement Forwarding Request | O | | ENUMERATED (Requested, Not Requested) | | YES | reject | + +| Condition | Explanation | +|-------------------------|--------------------------------------------------------------------------------------------------| +| SixteenQAM UL Operation | The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to "Activate". | + +#### 9.2.2.13DA E-DCH FDD Update Information + +The *E-DCH FDD Update Information* IE provides information for E-DCH to be updated. At least one IE shall be present. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------------|----------|----------------------------------------|---------------------------------------------------|-----------------------|-------------|----------------------| +| E-DCH MAC-d Flow Specific Update Information | | 0..<maxNrOfEDCHMACdFlows> | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | – | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | – | | +| E-DCH DL Control Channel Change Information | | 0..<maxnoofEDCHRLs> | | | GLOBAL | Ignore | +| >E-DCH RL ID | M | | RL ID
9.2.1.53 | | – | | +| TTI Update Indication | O | | 9.2.2.209 | | YES | reject | + +| Range bound | Explanation | +|-----------------------------|----------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.13Db E-DCH FDD Information Response + +The *E-DCH FDD Information Response* IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------------|----------|----------------------------------------|---------------------------------------------------|-----------------------|-------------|----------------------| +| E-DCH MAC-d Flow Specific Information Response | | 0..<maxNrOfEDCHMACdFlows> | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| >HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | – | | +| >Transport Bearer Not Setup Indicator | O | | 9.2.2.4H | | YES | ignore | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | – | | +| Fast TTI switching Mode Supported | O | | 9.2.2.211 | | YES | ignore | + +| Range bound | Explanation | +|-----------------------------|--------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | + +#### 9.2.2.13Dc E-DCH FDD DL Control Channel Information + +The *E-DCH FDD DL Control Channel Information* IE provides information for E-DCH specific DL Control Channels to be provided to UE via RRC signalling. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-AGCH And E-RGCH/E-HICH FDD Scrambling Code | O | | DL Scrambling Code 9.2.2.13 | Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted. | – | | +| E-AGCH Channelisation Code | O | | FDD DL Channelisation Code Number 9.2.2.14 | | – | | +| Primary E-RNTI | O | | E-RNTI 9.2.1.75 | | – | | +| Secondary E-RNTI | O | | E-RNTI 9.2.1.75 | | – | | +| E-RGCH/E-HICH Channelisation Code | O | | FDD DL Channelisation Code Number 9.2.2.14 | | – | | +| E-RGCH Signature Sequence | O | | INTEGER (0..maxNrofSigSeqRGHI-1) | | – | | +| E-HICH Signature Sequence | O | | INTEGER (0..maxNrofSigSeqRGHI-1) | | – | | +| Serving Grant Value | O | | INTEGER (0..37,38) | (0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; index 38 means zero grant | – | | +| Primary/Secondary Grant Selector | O | | ENUMERATED (Primary, Secondary) | Indicates whether the Serving Grant Value is granted with a primary E-RNTI or a secondary E-RNTI | – | | +| E-RGCH Release Indicator | O | | 9.2.2.13lc | | – | | +| Default Serving Grant in DTX Cycle 2 | O | | INTEGER (0..37,38) | Serving Grant value to be used in DTX-Cycle-2. (0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; index 38 means zero grant | YES | ignore | +| UL MIMO DL Control Channel information | O | | 9.2.2.180 | | YES | ignore | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------------| +| maxNrofSigSeqRGHI | Maximum number of Signature Sequences for E-RGCH/E-HICH. | + +#### 9.2.2.13De E-DCH RL Indication + +Indicates whether a RL is an E-DCH RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------|-----------------------| +| E-DCH RL Indication | | | ENUMERATED(E-DCH, non E-DCH) | | + +#### 9.2.2.13Df E-DCH FDD Information to Modify + +The *E-DCH FDD Information to Modify* IE is used for the modification of an E-DCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------------------------------|----------|----------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH MAC-d Flow Specific Information | | 0..<maxNrOfEDCHMACdFlows> | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >TNL QoS | O | | 9.2.1.58A | | – | | +| >Maximum Number Of Retransmissions For E-DCH | O | | 9.2.1.81 | | – | | +| >E-DCH HARQ Power Offset FDD | O | | 9.2.2.13Dk | | – | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | – | | +| >CHOICE E-DCH Grant Type | O | | | | – | | +| >> E-DCH Non-Scheduled Transmission Grant | | | | | | | +| >>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | M | | 9.2.2.13Dm | If the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is present, this IE shall be ignored. When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-i PDU. | – | | +| >>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI 9.2.2.13Dn | | – | | +| >>>Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | O | | 9.2.2.13Dr | When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-i PDU. | YES | reject | +| >> E-DCH Scheduled Transmission Grant | | | NULL | | | | + +| | | | | | | | +|--------------------------------------------------------------|----------------------------|-------------------------------------------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| >Bundling Mode Indicator | O | | 9.2.2.1Bb | | – | | +| >E-DCH Logical Channel To Add | O | | E-DCH Logical Channel Information 9.2.1.71 | | – | | +| >E-DCH Logical Channel To Modify | O | | 9.2.1.72 | | – | | +| >E-DCH Logical Channel To Delete | | 0..<maxno oflogicalchannels> | | | – | | +| >>Logical Channel ID | M | | 9.2.1.80 | | – | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI 9.2.2.13Dn | | – | | +| E-DCH Maximum Bitrate | O | | 9.2.2.13T | | – | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | – | | +| E-DCH Reference Power Offset | O | | 9.2.2.13Y | | – | | +| MAC-e Reset Indicator | O | | 9.2.1.83 | | – | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | YES | ignore | +| SixteenQAM UL Operation Indicator | O | | 9.2.2.88A | | YES | reject | +| E-DCH MAC-d PDU Size Format | O | | 9.2.1.74B | | YES | reject | +| E-DCH DL Control Channel Grant Information | | 0..<maxno ofEDCHRLs> | | | GLOBAL | ignore | +| >E-DCH RL ID | M | | RL ID 9.2.1.53 | | – | | +| E-AGCH Table Choice | C- SixteenQAM UL Operation | | 9.2.2.100 | If sixteenQAM UL operation is not used in the new configuration for this UE, Table 16B for E-AGCH in TS 25.212 [8] shall be used in the new configuration. | YES | ignore | +| SixtyfourQAM UL Operation Indicator | O | | 9.2.2.88C | | YES | reject | +| UL MIMO Reconfiguration | O | | 9.2.2.176 | | YES | reject | +| Fast TTI switching Mode Requested Synchronized | O | | 9.2.2.212 | | YES | reject | +| Fast TTI switching Mode Requested UnSynchronized | O | | 9.2.2.213 | | YES | reject | + +| Condition | Explanation | +|-------------------------|--------------------------------------------------------------------------------------------------| +| SixteenQAM UL Operation | The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to “Activate”. | + +| Range bound | Explanation | +|-------------------------------|----------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows. | +| maxnooflogicalchannels | Maximum number of logical channels | +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.13Dh E-DCH Transport Format Combination Set Information (E-TFCS Information) + +Whereas the related Transport Block sizes are standardised in TS 25.321 [32] this IE gives details on the referenced Transport Block Size Table, the E-DCH Minimum Set E-TFCI, the Reference E-TFCIs and configuration parameters used for the calculation of the gain factors $\beta_{ec}$ and $\beta_{ed}$ defined in TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-TFCI Table Index | M | | INTEGER
(0..1,..., 2..7) | Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in TS 25.321 [32]. | – | | +| E-DCH Minimum Set E-TFCI | O | | INTEGER
(0..127) | For the concept of "E-DCH Minimum Set of TFCs" see TS 25.321 [32] and TS 25.331 [18]. | – | | +| Reference E-TFCI Information | | 1..oofRefET
FCIs> | | | – | | +| >Reference E-TFCI | M | | INTEGER
(0..127) | | – | | +| >Reference E-TFCI Power Offset | M | | 9.2.2.13Dp | If the Extended Reference E-TFCI Power Offset IE is present, this IE shall be ignored | – | | +| >Extended Reference E-TFCI Power Offset | O | | 9.2.2.13Dq | | YES | reject | +| E-TFCI Boost Information | O | | 9.2.2.88B | | YES | reject | +| E-DPDCH Power Interpolation | O | | BOOLEAN | True means that the E-DPDCH power interpolation formula shall be applied, False means that the E-DPDCH power extrapolation formula shall be applied for the computation of the gain factor $\beta_{ed}$ according to TS 25.214 [10] | YES | reject | + +| Range Bound | Explanation | +|-------------------------|-----------------------------------------------| +| maxnoofRefETFCIs | Maximum number of signalled reference E-TFCIs | + +#### 9.2.2.13Di E-TTI + +The E-TTI parameter indicates the Transmission Time Interval for E-DPCH operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------|-----------------------| +| E-TTI | | | ENUMERATED
(2ms, 10ms) | | + +#### 9.2.2.13Dj E-DPCCH Power Offset + +The E-DPCCH Power Offset is used to calculate the E-DPCCH gain factor $\beta_{ec}$ as defined in TS 25.214 [10], whereas $\beta_{ec}$ is related to the power difference between DPCCH and E-DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| E-DPCCH Power Offset | | | INTEGER (0..8) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3. | + +#### 9.2.2.13Dk E-DCH HARQ Power Offset FDD + +The E-DCH HARQ Power Offset FDD is used to calculate the unquantised gain factor for an E-TFC ( $\beta_{ed,j,uq}$ ) as defined in TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| E-DCH HARQ Power Offset FDD | | | INTEGER (0..6) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3. | + +#### 9.2.2.13Dl E-DCH MAC-d Flow Multiplexing List + +Void. + +#### 9.2.2.13Dm Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission + +The Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission indicates the number of bits allowed to be included in a MAC-e (or MAC-i) PDU per E-DCH MAC-d flow configured for non-scheduled transmissions. If the range of the *Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission* IE is insufficient to represent the value to be sent to the Node B, the *Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission* IE shall be used to represent the value to be sent to the Node B, see section 9.2.2.13Dr. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | | | INTEGER (1..19982) | | + +#### 9.2.2.13Dn HARQ Process Allocation For 2ms TTI + +The HARQ Process Allocation for 2ms TTI indicates those HARQ processes that are allowed. MAC-d PDU's for a MAC-d flow are only allowed to be transmitted in those processes for which the bit is set to "1". + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HARQ Process Allocation For 2ms TTI | | | BIT STRING (SIZE(8)) | The first Bit corresponds to HARQ process ID = 0, the second bit corresponds to HARQ process ID = 1, etc.
The HARQ process ID for 2ms TTI is defined in TS 25.321 [32], chapter 11.8.1.3. | + +#### 9.2.2.13Dp Reference E-TFCI Power Offset + +The Reference E-TFCI Power Offset is used to calculate the reference E-TFC gain factor $\beta_{ed,ref}$ as defined in TS 25.214 [10]. If the range of the *Reference E-TFCI Power Offset* IE is insufficient to represent the value to be sent to the Node B, the *Extended Reference E-TFCI Power Offset* IE shall be used to represent the value to be sent to the Node B, see section 9.2.2.13Dq. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|--------------------------------------------------------------| +| Reference E-TFCI Power Offset | | | INTEGER (0..29) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3 | + +#### 9.2.2.13Dq Extended Reference E-TFCI Power Offset + +The *Extended Reference E-TFCI Power Offset* IE shall be used if the range of the *Reference E-TFCI Power Offset* IE (see section 9.2.2.13Dp) is insufficient to represent the value of the Reference E-TFCI Power Offset to be sent to the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------| +| Extended Reference E-TFCI Power Offset | | | INTEGER (30..31,...) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3 | + +#### 9.2.2.13Dr Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission + +The *Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission* IE shall be used if the range of the *Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission* IE (see section 9.2.2.13Dm) is insufficient to represent the value of the Maximum Number of Bits per MAC-e (or MAC-i) PDU for Non-scheduled Transmission to be sent to the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------------------------|----------|-------|-----------------------------------------|-----------------------| +| Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | | | INTEGER (19983..22978,...,22979..34507) | | + +#### 9.2.2.13E Enhanced DSCH PC + +Void. + +#### 9.2.2.13F Enhanced DSCH PC Counter + +Void. + +#### 9.2.2.13G Enhanced DSCH PC Indicator + +Void. + +#### 9.2.2.13H Enhanced DSCH PC Wnd + +Void. + +#### 9.2.2.13I Enhanced DSCH Power Offset + +Void. + +#### 9.2.2.13Ia E- RGCH/E-HICH FDD Code Information + +This parameter defines the codes which will be assigned for E- RGCH and E-HICH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-----------------------------|--------------------------------------------|-----------------------| +| CHOICE replaceremove | M | | | | +| > replace | | | | | +| >>E-RGCH/E-HICH Code | | 1.. | | | +| >>>Code Number | M | | FDD DL Channelisation Code Number 9.2.2.14 | | +| > remove | | | NULL | | + +| Range Bound | Explanation | +|------------------------|--------------------------------------------------------------------| +| MaxNrOfE-RGCHs-E-HICHs | Maximum number of E-RGCH/E-HICH channelisation codes for one cell. | + +#### 9.2.2.13Ib E- AGCH FDD Code Information + +This parameter defines the codes which will be assigned for E- AGCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|--------------------|--------------------------------------------|-----------------------| +| CHOICE replaceremove | M | | | | +| > replace | | | | | +| >>E-AGCH Code | | 1.. | | | +| >>>Code Number | M | | FDD DL Channelisation Code Number 9.2.2.14 | | +| > remove | | | NULL | | + +| Range Bound | Explanation | +|---------------|-------------------------------------------------------------| +| MaxNrOfEAGCHs | Maximum number of E-AGCH channelisation codes for one cell. | + +#### 9.2.2.13Ic E-RGCH Release Indicator + +Indicates the E-RGCH is released. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|------------------------------|-----------------------| +| E-RGCH Release Indicator | | | ENUMERATED (E-RGCH released) | | + +#### 9.2.2.13Id E-AGCH Power Offset + +The *E-AGCH Power Offset* IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the *E-AGCH Power Offset* IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|------------------------------------------------------| +| E-AGCH Power Offset | | | INTEGER (0...255,...) | Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB | + +#### 9.2.2.13Ie E-RGCH Power Offset + +The *E-RGCH Power Offset* IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the *E-RGCH Power Offset* IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|------------------------------------------------------| +| E-RGCH Power Offset | | | INTEGER (0...255,...) | Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB | + +#### 9.2.2.13If E-HICH Power Offset + +The *E-HICH Power Offset* IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the *E-HICH Power Offset* IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|------------------------------------------------------| +| E-HICH Power Offset | | | INTEGER (0...255,...) | Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB | + +#### 9.2.2.13Ig E-RGCH 2-Index-Step Threshold + +The *E-RGCH 2-index-step Threshold* IE is used to determine the Serving Grant. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|------------------------------------------------------------| +| E-RGCH 2-Index-Step Threshold | | | INTEGER (0..37) | Refers to an index in the "SG-Table" (see TS 25.321 [32]). | + +#### 9.2.2.13Ih E-RGCH 3-Index-Step Threshold + +The *E-RGCH 3-index-step Threshold* IE is used to determine the Serving Grant. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|------------------------------------------------------------| +| E-RGCH 3-Index-Step Threshold | | | INTEGER (0..37) | Refers to an index in the "SG-Table" (see TS 25.321 [32]). | + +#### 9.2.2.13J E-DCH Capability + +Void + +#### 9.2.2.13Ja E-DCH Capacity Consumption Law + +The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the RL/RLS situation and the number of uplink E-DPDCHs and their spreading factors. The reference spreading factor and number of E-DPDCH is signalled using the *Maximum Set of E-DPDCHs* IE. + +This capacity consumption law indicates the consumption law to be used with the following procedures : + +- Radio Link Setup +- Radio Link Addition +- Radio Link Reconfiguration +- Radio Link Deletion + +For the Radio Link Setup and Radio Link Addition procedures, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall be credited to the Capacity Credit for the Radio Link Deletion procedure. For the Radio Link Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited when this difference is negative). + +If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit. + +For a Radio Link creating a Radio Link Set (first RL of a RLS), the cost for the RL (cost 2) and RLS (cost 1) shall be taken into account. When adding a Radio Link to a Radio Link Set, only the RL cost (cost 2) shall be taken into account. + +In the case where multiple Radio Links are established in one procedure, for every created Radio Link Set, the first Radio Link is always the Radio Link with the lowest repetition number. + +The costs given in the consumption law are the costs per channelization code/no of E-DPDCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SF Allocation Law | | 1.. | | The cost of SF allocation: the first instance corresponds to v2xN2plus2xN4, the second to v2xN2, the third to v2xN4, the fourth to vN4, the fifth to vN8, the sixth to vN16, the seventh to vN32, the eighth to vN64, the ninth to vN128, the tenth to vN256 and the eleventh to v2xM2plus2xM4. | +| >UL Cost 1 | M | | INTEGER (0..65535) | This is the cost of a RLS | +| >UL Cost 2 | M | | INTEGER (0..65535) | This is the cost of a RL | +| DL Cost 1 | O | | INTEGER (0..65535) | This is the cost of a RLS. If not present, zero cost shall be applied. . | +| DL Cost 2 | O | | INTEGER (0..65535) | This is the cost of a RL. If not present, zero cost shall be applied. | + +| Range Bound | Explanation | +|--------------------------|--------------------------------------------------------------------------| +| maxNrOfCombEDPDCH | Maximum number of Configurations in the Maximum Set of E-DPDCH IE | + +#### 9.2.2.13K E-DCH Logical Channel Information + +Void + +#### 9.2.2.13L E-DCH Logical Channel To Modify + +Void + +#### 9.2.2.13M E-DCH MAC-d Flows Information + +The *E-DCH MAC-d Flows Information* IE is used for the establishment of E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------------------------------|----------|---------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH MAC-d Flow Specific Information | | 1.. | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >TNL QoS | O | | 9.2.1.58A | | – | | +| >Payload CRC Presence Indicator | M | | 9.2.1.49 | | – | | +| >Maximum Number Of Retransmissions For E-DCH | M | | 9.2.1.81 | | – | | +| >E-DCH HARQ Power Offset FDD | M | | 9.2.2.13Dk | | – | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | – | | +| >CHOICE E-DCH Grant Type | M | | | | – | | +| >> E-DCH Non-Scheduled Transmission Grant | | | | | | | +| >>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | M | | 9.2.2.13Dm | If the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is present, this IE shall be ignored. When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-i PDU. | – | | +| >>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI 9.2.2.13Dn | If this IE is not included, transmission in all HARQ processes is allowed. | – | | +| >>>Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission | O | | 9.2.2.13Dr | When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-i PDU. | YES | reject | + +| | | | | | | | +|-------------------------------------------|---|--|-----------|--|-----|--------| +| >>E-DCH Scheduled Transmission Grant | | | NULL | | | | +| >Bundling Mode Indicator | O | | 9.2.2.1Bb | | – | | +| >E-DCH Logical Channel Information | M | | 9.2.1.71 | | – | | +| >Transport Bearer Not Requested Indicator | O | | 9.2.2.4G | | YES | ignore | + +| Range Bound | Explanation | +|----------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | + +#### 9.2.2.13N E-DCH MAC-d Flows To Delete + +Void + +#### 9.2.2.13O E-DCH MAC-d Flow ID + +Void + +#### 9.2.2.13P E-RNTI + +Void + +#### 9.2.2.13Q E-DCH DDI Value + +Void + +#### 9.2.2.13R E-DCH Provided Bit Rate Value + +Void + +#### 9.2.2.13S E-DCH Provided Bit Rate Value Information + +Void + +#### 9.2.2.13T E-DCH Maximum Bitrate + +The E-DCH Maximum Bitrate parameter indicates the Maximum Bitrate for an E-DCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|------------------------------------------------------|----------------------------------------------------------------| +| E-DCH Maximum Bitrate | | | INTEGER
(0..5742, ..., 5743..11498, 11499..34507) | Bitrate on transport block level.
Unit is kbits per second. | + +#### 9.2.2.13U E-DCH Processing Overload Level + +Void + +#### 9.2.2.13V E-DCH TTI2ms Capability + +This parameter defines the E-DCH TTI Capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------| +| E-DCH TTI2ms Capability | | | BOOLEAN | True = TTI 10ms and 2ms supported for E-DCH
False = only TTI 10ms supported for E-DCH | + +#### 9.2.2.13W E-DCH SF Capability + +This parameter defines the E-DCH Capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|----------------------------------------------------------------------|---------------------------------------| +| E-DCH SF Capability | | | ENUMERATED (sf64, sf32, sf16, sf8, sf4, 2sf4, 2sf2, 2sf2and2sf4,...) | Min SF supported by the cell in E-DCH | + +#### 9.2.2.13X E-DCH HARQ Combining Capability + +This parameter defines the E-DCH HARQ Combining capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|--------------------------------------------------------------------------------------------|-----------------------| +| E-DCH HARQ Combining Capability | | | ENUMERATED (IR Combining Capable, Chase Combining Capable, IR and Chase Combining Capable) | | + +#### 9.2.2.13Y E-DCH Reference Power Offset + +The E-DCH Reference Power Offset is used to estimate the E-DPDCH power from E-TFCI without decoding MAC-e PDUs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| E-DCH Reference Power Offset | | | INTEGER (0..6) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3. | + +#### 9.2.2.13Z E-DCH Power Offset for Scheduling Info + +Void + +#### 9.2.2.14 FDD DL Channelisation Code Number + +The DL Channelisation Code Number indicates the DL Channelisation Code number for a specific DL physical channel. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------| +| FDD DL Channelisation Code Number | | | INTEGER (0..511) | According to the mapping in TS 25.213 [9].
The maximum value is equal to the DL spreading factor -1. | + +##### 9.2.2.14A FDD DL Code Information + +The *FDD DL Code Information* IE provides DL Code information for the RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------|----------|--------------------|-----------------------|-----------------------| +| FDD DL Code Information | | 1.. | | | +| >DL Scrambling Code | M | | 9.2.2.13 | | +| >FDD DL Channelisation Code Number | M | | 9.2.2.14 | | +| >Transmission Gap Pattern Sequence Code Information | O | | 9.2.2.53B | | + +| Range Bound | Explanation | +|---------------------|---------------------------------------| +| maxnoofCodes | Maximum number of DL code information | + +#### 9.2.2.14B FDD S-CCPCH Frame Offset + +The *FDD S-CCPCH Frame Offset* IE represents a frame offset between the concerned S-CCPCH's CFN (Connection Frame Number) relatively to the P-CCPCH's SFN (System Frame Number) of the respective cell. The *FDD S-CCPCH Frame Offset* IE shall be the constant difference between the S-CCPCH's CFN and the least significant 8 bits of the SFN (System Frame Number) on Uu. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|--------------------------|-----------------------------------------------------------------------------| +| FDD S-CCPCH Frame Offset | | | ENUMERATED (1, 2, 4,...) | Offset in frames (corresponding to 10msec, 20msec or 40msec offset in time) | + +#### 9.2.2.15 FDD SCCPCH Offset + +The Secondary CCPCH offset is defined as the time offset towards the Primary CCPCH in the cell. The offset is a multiple of 256 chips. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------| +| FDD SCCPCH Offset | | | INTEGER (0..149) | Unit: chip
Range: 0..38144 chips
Step: 256 chips
See ref. TS 25.211 [7] | + +#### 9.2.2.16 FDD TPC DL Step Size + +This parameter indicates step size for the DL power adjustment. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------------|-----------------------| +| FDD TPC Downlink Step Size | | | ENUMERATED (0.5, 1, 1.5, 2,...) | Unit: dB | + +#### 9.2.2.16a F-DPCH Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-------------------------------------------------|-----------------------| +| F-DPCH Capability | | | ENUMERATED (F-DPCH Capable, F-DPCH Non-Capable) | | + +#### 9.2.2.16A First RLS Indicator + +The *First RLS Indicator* IE indicates if a specific Radio Link and all Radio Links which are part of the same Radio Link Set, shall be considered as the first radio links established towards the UE or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|---------------------------------------------|-----------------------| +| First RLS Indicator | | | ENUMERATED ( First RLS, Not First RLS, ...) | | + +#### 9.2.2.17 Gap Period + +Void. + +#### 9.2.2.18 Gap Position Mode + +Void. + +#### 9.2.2.18a HARQ Preamble Mode + +The *HARQ Preamble Mode* IE is used as described as in ref TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|----------------------------|----------------------------------------------------------------------------| +| HARQ Preamble Mode | | | ENUMERATED ( mode0, mode1) | "mode0" means HARQ Preamble Mode =0
"mode1" means HARQ Preamble Mode =1 | + +#### 9.2.2.18b HARQ Preamble Mode Activation Indicator + +The HARQ Preamble Activation Indicator indicates if the configured HARQ Preamble Mode has been activated in the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-------------------------------------------|-----------------------| +| HARQ Preamble Mode Activation Indicator | | | ENUMERATED(HARQ Preamble Mode Activated). | | + +##### 9.2.2.18ba HARQ Info for E-DCH + +The E-DCH HARQ Info is used to indicate the use of redundancy version (RV) for the EDCH HARQ transmissions. + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HARQ Info for E-DCH | | | ENUMERATED (rv0, rvtable) | "rv0" indicates that the UE will only use E_DCH RV index 0.
"rvtable" indicates that the UE will use an RSN based RV index as specified in TS 25.212 [8] | + +#### 9.2.2.18c Logical channel ID + +Void + +#### 9.2.2.18A Limited Power Increase + +The parameter is used for a more efficient use of the inner loop DL power control for non real time data. + +If the limited power increase is used, the Node B shall use the limited power increase algorithm as specified in TS 25.214 [10], subclause 5.2. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-------------------------------|-----------------------| +| Limited Power Increase | | | ENUMERATED ( Used, Not Used ) | | + +#### 9.2.2.18B Inner Loop DL PC Status + +The *Inner Loop DL PC Status* IE indicates whether inner loop DL control shall be active or inactive for all radio links associated with the context identified by the *Node B Communication Context Id* IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-------------------------------|-----------------------| +| Inner Loop DL PC Status | | | ENUMERATED (Active, Inactive) | | + +#### 9.2.2.18C IPDL FDD Parameters + +The *IPDL FDD Parameters* IE provides information about IPDL to be applied for FDD when activated. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------------------------------|-----------------------| +| IP SpacingFDD | M | | ENUMERATED (5, 7, 10, 15, 20, 30, 40, 50,...) | See TS 25.214 [10] | +| IP Length | M | | ENUMERATED (5, 10) | See TS 25.214 [10] | +| Seed | M | | INTEGER (0..63) | See TS 25.214 [10] | +| Burst Mode Parameters | O | | 9.2.1.5A | | +| IP Offset | M | | INTEGER (0..9) | See TS 25.214 [10] | + +#### 9.2.2.18Ca HS-DSCH configured indicator + +The *HS-DSCH Configured Indicator* IE indicates the configuration of HS-DSCH for the UE. The *HS-DSCH Configured Indicator* IE shall be used for the configuration of the E-DPDCH IQ branch mapping (TS 25.213 [9]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| HS-DSCH Configured Indicator | | | ENUMERATED (HS-DSCH configured, HS-DSCH not configured) | Indicator of the HS-DSCH for configuration of the E-DPDCHs IQ branch mapping (TS 25.213 [9]). | + +#### 9.2.2.18D HS-DSCH FDD Information + +The *HS-DSCH FDD Information* IE is used for initial addition of HS-DSCH information to a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------|-------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH MAC-d Flows Information | M | | 9.2.1.31IA | | – | | +| UE Capabilities Information | | 1 | | | – | | +| >HS-DSCH Physical Layer Category | M | | 9.2.1.31Ia | | – | | +| >1.28 Mcps TDD Uplink Physical Channel Capability | O | | 9.2.3.5Gc | Not to be used. | YES | ignore | +| >Number of Supported Carriers | O | | ENUMERATED ( One-one carrier, One-three carrier, Three-three carrier, One-six carrier, Three-six carrier, Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous) | Not to be used. | YES | reject | +| >Multi-carrier HS-DSCH Physical Layer Category | O | | 9.2.1.31Ia | Not to be used. | YES | ignore | +| >UE RF Band Capability LCR | C- NofSupportedCarriers | | 9.2.3.125 | Not to be used. | YES | ignore | +| MAC-hs Reordering Buffer Size for RLC-UM | M | | 9.2.1.38Ab | | – | | +| CQI Feedback Cycle k | M | | 9.2.2.21B | | – | | +| CQI Repetition Factor | C- CQICyclek | | 9.2.2.4Cb | | – | | +| ACK-NACK Repetition Factor | M | | 9.2.2.a | | – | | +| CQI Power Offset | M | | 9.2.2.4Ca | | – | | +| ACK Power Offset | M | | 9.2.2.b | | – | | +| NACK Power Offset | M | | 9.2.2.23a | | – | | +| HS-SCCH Power Offset | O | | 9.2.2.18I | | – | | +| Measurement Power Offset | O | | 9.2.2.21C | | – | | +| HARQ Preamble Mode | O | | 9.2.2.18a | | YES | ignore | +| MIMO Activation Indicator | O | | 9.2.1.119 | | YES | reject | +| HS-DSCH MAC-d PDU Size Format | O | | 9.2.1.31ID | If not present, "Indexed MAC-d PDU Size" shall be used. | YES | reject | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | | YES | ignore | +| UE with enhanced HS-SCCH support indicator | O | | NULL | UE supports enhanced HS-SCCH functionality:
- UE supports different HS- | YES | ignore | + +| | | | | | | | +|-------------------------------------------------------------------|---|--|----------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----|--------| +| | | | | SCCH in consecutive TTIs and - in HS-SCCH-less operation mode the UE supports HS-SCCH orders | | | +| Enhanced HS Serving CC Abort | O | | ENUMERATED (Abort Enhanced HS Serving CC, ...) | Shall be ignored in Radio Link Setup and Radio Link Addition procedures. | YES | reject | +| UE Support Indicator Extension | O | | 9.2.2.117 | | YES | ignore | +| Single Stream MIMO Activation Indicator | O | | 9.2.2.123 | | YES | reject | +| Puncturing Handling in First Rate Matching Stage | O | | 9.2.2.149 | | YES | ignore | +| MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.164 | | YES | reject | +| Dual Stream MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.167 | | YES | reject | +| Multiflow Information | O | | 9.2.2.170 | For FDD only | YES | reject | +| CQI Feedback Cycle2 k | O | | CQI Feedback Cycle k2 9.2.2.206 | For FDD only | YES | ignore | +| CQI Cycle Switch Timer | O | | ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity) | For FDD only, refer to TS 25.331 [16]. | YES | ignore | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------------------| +| CQICyclek | The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0. | + +#### 9.2.2.18Da HS-DSCH FDD Secondary Serving Information + +The *HS-DSCH FDD Secondary Serving Information* IE is used for initial addition of Secondary Serving HS-DSCH information to a Node B Communication Context and defines the cell specific parameters for the secondary serving HS-DSCH Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-SCCH Power Offset | O | | 9.2.2.18I | | - | | +| Measurement Power Offset | M | | 9.2.2.21C | | - | | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | | - | | +| HS-DSCH RNTI | M | | 9.2.1.31J | | - | | +| MIMO Activation Indicator | O | | 9.2.1.119 | | YES | reject | +| Single Stream MIMO Activation Indicator | O | | 9.2.2.123 | | YES | reject | +| Diversity Mode | O | | 9.2.2.9 | If Diversity mode = "Closed loop mode 1" the procedure shall be rejected | YES | reject | +| Transmit Diversity Indicator | O | | 9.2.2.53 | | YES | reject | +| Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link. | YES | reject | +| MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.164 | | YES | reject | +| Dual Stream MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.167 | | YES | reject | +| Multiflow Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212 [8]. In inter-Node B multiflow case, if present, the Value must be "1" when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies | YES | reject | + +| | | | | | | | +|--|--|--|--|---------------------------------------------------------------------------|--|--| +| | | | | the index of this cell for the UL HS-DPCCH as specified in TS 25.212 [8]. | | | +|--|--|--|--|---------------------------------------------------------------------------|--|--| + +#### 9.2.2.18E HS-DSCH FDD Information Response + +The HS-DSCH Information Response provides information for HS-DSCH that have been established or modified. It also provides additional HS-DSCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|--------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| HS-DSCH MAC-d Flow Specific Information Response | | 0..<maxNrOfMACdFlows> | | | – | | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| >HS-DSCH Initial Capacity Allocation | O | | 9.2.1.31Ha | | – | | +| HS-SCCH Specific Information Response | | 0..<maxNrOfHSSCCHCodes> | | | – | | +| >Code Number | M | | INTEGER (0..127) | | – | | +| HARQ Memory Partitioning | O | | 9.2.1.102 | | – | | +| HARQ Preamble Mode Activation Indicator | O | | 9.2.2.18b | | YES | ignore | +| MIMO N/M Ratio | O | | 9.2.2.96 | | YES | ignore | +| SixtyfourQAM DL Usage Indicator | O | | 9.2.2.74B | | YES | ignore | +| HS-DSCH TB Size Table Indicator | O | | 9.2.2.18Ee | | YES | ignore | +| Support of dynamic DTXDRX related HS-SCCH order | O | | 9.2.2.150 | | YES | ignore | +| Precoder weight set restriction | O | | 9.2.2.192 | | YES | ignore | + +| Range Bound | Explanation | +|---------------------------|---------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows | +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | + +#### 9.2.2.18EA HS-DSCH FDD Secondary Serving Information Response + +The HS-DSCH Secondary Serving Information Response provides information for Secondary Serving HS-DSCH that have been established or modified. It also provides additional HS-DSCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------------------|----------|--------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| HS-SCCH Specific Secondary Serving Information Response | | 0..<maxNrOfHSSCCHCodes> | | | | | +| >Code Number | M | | INTEGER (0..127) | | | | +| SixtyfourQAM DL Usage Indicator | O | | 9.2.2.74B | | | | +| HS-DSCH TB Size Table Indicator | O | | 9.2.2.18Ee | | | | +| MIMO N/M Ratio | O | | 9.2.2.96 | | YES | ignore | +| Precoder weight set restriction | O | | 9.2.2.192 | | YES | ignore | + +| Range Bound | Explanation | +|---------------------------|---------------------------------| +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | + +#### 9.2.2.18EB HS-DSCH FDD Secondary Serving Information To Modify + +The *HS-DSCH FDD Secondary Serving Information To Modify* IE is used for modification of Secondary Serving HS-DSCH information in a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|------------------|-------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-SCCH Power Offset | O | | 9.2.2.18I | | - | | +| Measurement Power Offset | O | | 9.2.2.21C | | - | | +| HS-SCCH Code Change Grant | O | | 9.2.1.31L | | - | | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | | - | | +| MIMO Mode Indicator | O | | 9.2.1.120 | | YES | reject | +| Single Stream MIMO Mode Indicator | O | | 9.2.2.124 | | YES | reject | +| Diversity Mode | O | | 9.2.2.9 | If Diversity mode = "Closed loop mode 1" the procedure shall be rejected | YES | reject | +| Transmit Diversity Indicator | C- DiversityMode | | 9.2.2.53 | | YES | reject | +| Non Cell Specific Tx Diversity | O | | ENUMERATED (Tx Diversity, ...) | Value = "Tx Diversity": Diversity Mode and Transmit Diversity Indicator shall be non cell specific. | YES | reject | +| Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link. | YES | reject | +| MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.166 | For FDD only | YES | reject | +| Dual Stream MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.168 | For FDD only | YES | reject | +| Multiflow Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS- | YES | reject | + +| | | | | | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | DSCH cell for the UL HS-DPCCH as specified in TS 25.212.
In inter-Node B multiflow case, if present, the Value must be "1" when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8]. | | | +|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +| Condition | Explanation | +|---------------|---------------------------------------------------------------------------------------| +| DiversityMode | The IE shall be present if Diversity Mode IE is present and not set to "None". | + +#### 9.2.2.18EC HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised + +The *HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised* IE is used for modification of Secondary Serving HS-DSCH information in a Node B Communication Context with the Unsynchronised Radio Link Reconfiguration procedure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-SCCH Power Offset | O | | 9.2.2.18I | | - | | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | | - | | +| MIMO Mode Indicator | O | | 9.2.1.120 | | YES | reject | +| Single Stream MIMO Mode Indicator | O | | 9.2.2.124 | | YES | reject | +| Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link. | YES | reject | +| MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.166 | For FDD only | YES | reject | +| Dual Stream MIMO with four transmit antennas Mode Indicator | O | | 9.2.2.168 | For FDD only | YES | reject | +| Multiflow Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212. In inter-Node B multiflow case, if present, the Value must be "1" when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8]. | YES | reject | + +#### 9.2.2.18Ea HS-DSCH FDD Update Information + +The *HS-DSCH FDD Update Information* IE provides information for HS-DSCH to be updated. At least one IE shall be present. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|----------------------------------------------------------------|----------------------------------------|-------------|----------------------| +| HS-SCCH Code Change Indicator | O | | 9.2.1.31K | | – | | +| CQI Feedback Cycle k | O | | 9.2.2.21B | | – | | +| CQI Repetition Factor | O | | 9.2.2.4Cb | | – | | +| ACK-NACK Repetition Factor | O | | 9.2.2.a | | – | | +| CQI Power Offset | O | | 9.2.2.4Ca | | – | | +| ACK Power Offset | O | | 9.2.2.b | | – | | +| NACK Power Offset | O | | 9.2.2.23a | | – | | +| HS-PDSCH Code Change Indicator | O | | 9.2.1.31M | | YES | ignore | +| Precoder weight set restriction | O | | 9.2.2.192 | | YES | ignore | +| CQI Feedback Cycle2 k | O | | CQI Feedback Cycle k2
9.2.2.206 | For FDD only | YES | ignore | +| CQI Cycle Switch Timer | O | | ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity) | For FDD only, refer to TS 25.331 [16]. | YES | ignore | + +#### 9.2.2.18Eaa HS-DSCH FDD Secondary Serving Update Information + +The *HS-DSCH FDD Secondary Serving Update Information* IE provides information for Secondary Serving HS-DSCH to be updated. At least one IE shall be present. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------|-------------|----------------------| +| HS-SCCH Code Change Indicator | O | | 9.2.1.31K | | – | | +| HS-PDSCH Code Change Indicator | O | | 9.2.1.31M | This IE shall never be included. If received it shall be ignored. | – | | +| Precoder weight set restriction | O | | 9.2.2.192 | | YES | ignore | + +#### 9.2.2.18Eb HS-DSCH Serving Cell Change Information + +The *HS-DSCH Serving Cell Change Information* IE contains information which is used in HS-DSCH Serving Cell change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|-------|--------------------------------------|-----------------------|-------------|----------------------| +| HS-PDSCH RL ID | M | | RL ID
9.2.1.53 | | – | | +| HS-DSCH Information | O | | HS-DSCH FDD Information
9.2.2.18D | | – | | +| HS-DSCH RNTI | M | | 9.2.1.31J | | – | | +| Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.68 | | YES | reject | +| Continuous Packet Connectivity DTX-DRX Information | O | | 9.2.2.66 | | YES | reject | + +#### 9.2.2.18Ec HS-DSCH Serving Cell Change Information Response + +The *HS-DSCH Serving Cell Change Information Response* IE contains information which is used in HS-DSCH Serving Cell change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE Serving Cell Change | | | | | – | | +| > Successful | | | | | | | +| >>HS-DSCH FDD Information Response | M | | 9.2.2.18E | | – | | +| >>Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.69 | | YES | ignore | +| > Unsuccessful | | | | | | | +| >>Cause | M | | 9.2.1.6 | | – | | + +#### 9.2.2.18Eca HS-DSCH Secondary Serving Cell Change Information Response + +The *HS-DSCH Secondary Serving Cell Change Information Response* IE contains information which is used in HS-DSCH Secondary Serving Cell change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Secondary Serving Cell Change | | | | | +| > Successful | | | | | +| >>HS-DSCH FDD Secondary Serving Information Response | M | | 9.2.2.18EA | | +| > Unsuccessful | | | | | +| >>Cause | M | | 9.2.1.6 | | + +#### 9.2.2.18Ed E-DCH Serving Cell Change Information Response + +The *E-DCH Serving Cell Change Information Response* IE contains information which is used in E-DCH Serving Cell change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-----------------|-----------------------|-----------------------| +| CHOICE Serving Cell Change | | | | | +| > Successful | | | | | +| >>RL Information Response | | 0.. | | | +| >>>RL ID | M | | 9.2.1.53 | | +| >>>E-DCH FDD DL Control Channel Information | M | | 9.2.2.13Dc | | +| > Unsuccessful | | | | | +| >>Cause | M | | 9.2.1.6 | | + +| Range bound | Explanation | +|-------------|----------------------------------| +| maxNrOfRLs | Maximum number of RLs for one UE | + +#### 9.2.2.18Ee HS-DSCH TB Size Table Indicator + +The *HS-DSCH TB Size Table Indicator* IE is used to indicate that octet aligned table TS 25.321 [32] shall be used. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|----------------------------|-----------------------| +| HS-DSCH TB Size Table Indicator | | | ENUMERATED (octet aligned) | | + +#### 9.2.2.18F HS-PDSCH FDD Code Information + +This parameter defines the codes which will be assigned for HS-PDSCHs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|------------|-------|--------------------------------------|-----------------------| +| Number Of HS-PDSCH Codes | M | | INTEGER (0..maxHS-PDSCHCodeNrComp-1) | | +| Start Code Number | C-NumCodes | | INTEGER (1..maxHS-PDSCHCodeNrComp-1) | | + +| Condition | Explanation | +|-----------|-----------------------------------------------------------------------------------------------------| +| NumCodes | The IE shall be present if the Number Of HS-PDSCH Codes IE is set to a value greater than 0. | + +| Range Bound | Explanation | +|-----------------------|----------------------------------------------------------------------------------------| +| MaxHS-PDSCHCodeNrComp | Maximum number of codes at the defined spreading factor, within the complete code tree | + +#### 9.2.2.18G HS-SCCH FDD Code Information + +This parameter defines the codes which will be assigned for HS-SCCH. The Node B will assign codes for HS-SCCHs among these codes when it sets up a HS-DSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|----------------------|-------------------------------------|-----------------------| +| CHOICE replaceremove | M | | | | +| > replace | | | | | +| >>HS-SCCH Code | | 1.. | | | +| >>>Code Number | M | | INTEGER (0..maxHS-SCCHCodeNrComp-1) | | +| > remove | | | NULL | | + +| Range Bound | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| MaxNrOfHSSCC Hs | Maximum number of HS-SCCHs for one cell. | +| MaxHS-SCCHCodeNrComp | Maximum number of codes at the defined spreading factor, within the complete code tree | + +#### 9.2.2.18H HS-SCCH ID + +Void. + +#### 9.2.2.18I HS-SCCH Power Offset + +The *HS-SCCH Power Offset* IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the *HS-SCCH Power Offset* IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|------------------------------------------------------| +| HS-SCCH Power Offset | | | INTEGER (0...255) | Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB | + +#### 9.2.2.18K Initial DL DPCH Timing Adjustment Allowed + +The *Initial DL DPCH Timing Adjustment Allowed* IE indicates that the Node B is allowed to perform a timing adjustment (either a timing advance or a timing delay with respect to the SFN timing) when establishing a radio link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|---------------------------------------------------------|-----------------------| +| Initial DL DPCH Timing Adjustment Allowed | | | ENUMERATED ( initial DL DPCH Timing Adjustment Allowed) | | + +#### 9.2.2.19 Max Adjustment Period + +Void. + +#### 9.2.2.20 Max Adjustment Step + +Defines the maximum allowed value for the change of DL power level during a certain number of slots that can be utilised by the downlink power balancing algorithm. *Max Adjustment Step* IE defines a time period, in terms of number of slots, in which the accumulated power adjustment shall be maximum 1dB. This value does not include the DL inner loop PC adjustment. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| Max Adjustment Step | | | INTEGER (1..10) | Unit: Slots | + +#### 9.2.2.20A Max Number Of PCPCHs + +Void. + +#### 9.2.2.20B Max Number Of UL E-DPDCHs + +Void. + +#### 9.2.2.20C Maximum Set of E-DPDCHs + +The Maximum Set of E-DPDCHs as defined in TS 25.212 [8]. Needed by rate matching algorithm. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|--------------------------------------------------------------------------------------------------------|-----------------------| +| Maximum Set of E-DPDCHs | | | ENUMERATED (vN256, vN128, vN64, vN32, vN16, vN8, vN4, v2xN4, v2xN2, v2xN2plus2xN4, ..., v2xM2plus2xM4) | | + +#### 9.2.2.20D Maximum Number Of Retransmissions For E-DCH + +Void + +#### 9.2.2.20E MAC-es Guaranteed Bit Rate + +Void + +#### 9.2.2.20F MAC-e Reset Indicator + +Void + +#### 9.2.2.21 Maximum Number Of UL DPDCHs + +Maximum number of uplink DPDCHs to be used during the connection. Needed by the rate matching algorithm. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Max Number Of UL DPDCHs | | | INTEGER (1..6) | | + +#### 9.2.2.21a Maximum Target Received Total Wide Band Power + +The Maximum Target Received Total Wide Band Power indicates the maximum target UL interference for a certain cell or cell portion under CRNC, including received wide band power from all sources. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| Maximum Target Received Total Wide Band Power | | | INTEGER (0..621) | The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.133 [22]. | + +#### 9.2.2.21b Target Non-serving E-DCH to Total E-DCH Power Ratio + +The Target Non-serving E-DCH to Total E-DCH Power Ratio indicates the target ratio of the received E-DCH power from non-serving UEs to the received total E-DCH power. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------| +| Target Non-serving E-DCH to Total E-DCH Power Ratio | | | INTEGER (0..100) | Unit: %
Range: 0..100 %
Step: 1 % | + +#### 9.2.2.21A Maximum PDSCH Power + +Void. + +#### 9.2.2.21B CQI Feedback Cycle k + +The *CQI Feedback Cycle k* IE provides the duration of the CQI feedback cycle. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| CQI Feedback Cycle k | | | ENUMERATED
(0, 2, 4, 8, 10, 20, 40, 80, 160, ..., 16, 32, 64) | Unit ms
The allowed values for this IE depend on the configured CQI Repetition Factor and the HS-DSCH configuration as defined in TS 25.214 [10]. | + +#### 9.2.2.21C Measurement Power Offset + +The *Measurement Power Offset* IE is used as described in ref TS 25.214 [10] subclause 6A.2. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|--------------------------------------------| +| Measurement Power Offset | | | INTEGER (-12..26) | Unit: dB
Range: -6..13dB
Step: 0.5dB | + +#### 9.2.2.21D MICH Mode + +The number of Notification Indicators (NIs) transmitted in a MICH frame. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------|-------------------------| +| MICH Mode | | | ENUMERATED
(18, 36, 72, 144, ...,
16, 32, 64, 128) | Number of NIs per frame | + +#### 9.2.2.22 Minimum UL Channelisation Code Length + +Minimum UL channelisation code length (spreading factor) of a DPDCH which is used during the connection. Needed by rate matching algorithm. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|----------------------------------------------------|-----------------------| +| Min UL Channelisation Code Length | | | ENUMERATED
(4, 8, 16, 32, 64,
128, 256, ...) | | + +##### 9.2.2.22a Min UL Channelisation Code Length For E-DCH FDD + +Void. + +#### 9.2.2.23 Multiplexing Position + +Multiplexing Position specifies whether fixed or flexible positions of transport channels shall be used in the physical channel. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-------------------------------------|-----------------------| +| Multiplexing Position | | | ENUMERATED (
Fixed,
Flexible) | | + +#### 9.2.2.23a NACK Power Offset + +The *NACK Power Offset* IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ NACK information and the associated DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-------------------------------|----------------------------------------------------------------| +| NACK Power Offset | | | INTEGER (0..8, ...,
9..10) | According to mapping in ref.
TS 25.213 [9] subclause 4.2.1. | + +#### 9.2.2.23A N\_EOT + +Void. + +#### 9.2.2.23B NF\_max + +Void. + +#### 9.2.2.23C N\_Start\_Message + +Void. + +#### 9.2.2.23D Number Of Reported Cell Portions + +Number of Reported Cell Portions indicates the number of Best Cell Portions values which shall be included in the measurement report. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| Number Of Reported Cell Portions | | | INTEGER (1..64,...) | | + +#### 9.2.2.24 Pattern Duration (PD) + +Void. + +##### 9.2.2.24A PCP Length + +Void. + +#### 9.2.2.25 PDSCH Code Mapping + +Void. + +#### 9.2.2.26 PICH Mode + +The number of paging indicators (PIs) in a PICH frame. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------|-------------------------| +| PICH Mode | | | ENUMERATED (18, 36, 72, 144,...) | Number of PIs per frame | + +#### 9.2.2.27 Power Adjustment Type + +Defines the characteristic of the power adjustment. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|----------------------------------------|-----------------------| +| Power Adjustment Type | | | ENUMERATED ( None, Common, Individual) | | + +#### 9.2.2.28 Power Control Mode + +Void. + +#### 9.2.2.29 Power Offset + +This IE defines a power offset relative to the Downlink transmission power of a DPDCH in case the Node B Communication Context is configured to use DPCH in the downlink or relative to a Secondary CCPCH data field. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|---------------------------------------------| +| Power Offset | | | INTEGER (0..24) | Unit: dB
Range: 0..6 dB
Step: 0.25 dB | + +##### 9.2.2.29A Power\_Raise\_Limit + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-------------------------------------------| +| Power_Raise_Limit | | | INTEGER (0..10) | Unit: dB
Range: 0..10 dB
Step: 1 dB | + +#### 9.2.2.30 Power Resume Mode + +Void. + +#### 9.2.2.31 Preamble Signatures + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Preamble Signatures | | | BIT STRING (SIZE(16)) | Each bit indicates availability for a signature, where the signatures are numbered "signature 0" up to "signature 15". The value 1 of a bit indicates that the corresponding signature is available and the value 0 that it is not available. The order of bits is to be interpreted according to subclause 9.3.4. See also TS 25.213 [9]. | + +#### 9.2.2.32 Preamble Threshold + +The IE sets the threshold for preamble detection. The ratio between received preamble power during the preamble period and interference level shall be above this threshold in order to be acknowledged. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|------------------------------------------------| +| Preamble Threshold | | | INTEGER (0..72) | Unit: dB
Range: -36 .. 0 dB
Step: 0.5 dB | + +#### 9.2.2.33 Primary CPICH Power + +The Primary CPICH power is the power that shall be used for transmitting the P-CPICH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CPICH, the Primary CPICH power is the linear sum of the power that is used for transmitting the Primary CPICH on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------| +| Primary CPICH Power | | | INTEGER (-100..500) | Value = Primary CPICH Power/10
Unit: dBm
Range: -10.0..+50.0 dBm
Step: 0.1 dB | + +##### 9.2.2.33A Primary CPICH Usage For Channel Estimation + +The *Primary CPICH Usage For Channel Estimation* IE indicates whether the Primary CPICH may be used for channel estimation or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|--------------------------------------------------------------------------------------|-----------------------| +| Primary CPICH Usage For Channel Estimation | | | ENUMERATED (
Primary CPICH may
be used,
Primary CPICH shall
not be used) | | + +#### 9.2.2.34 Primary Scrambling Code + +The Primary scrambling code to be used in the cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Primary Scrambling Code | | | INTEGER (0..511) | | + +#### 9.2.2.35 Propagation Delay + +The Propagation delay is the one-way propagation delay of the radio signal from the MS to the Node B. If the range of the *Propagation Delay* IE is insufficient to represent the measured value, the *Propagation Delay* IE shall be set to its maximum value, and the *Extended Propagation Delay* IE shall be used to represent the propagation delay value, see subclause 9.2.2.35A. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|----------------------------------------------------| +| Propagation Delay | | | INTEGER (0..255) | Unit: chip
Range: 0..765 chips
Step: 3 chips | + +#### 9.2.2.35A Extended Propagation Delay + +The Extended Propagation delay is the one-way propagation delay of the radio signal from the MS to the Node B. It shall be used if the *Propagation Delay* IE (see 9.2.2.35) cannot represent the measured value, due to range limitation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------| +| Extended Propagation Delay | | | INTEGER
(255..1023) | Continuation of intervals as
defined in TS 25.133 [22].
Unit: chip
Range: 765..3069 chips
Step: 3 chips | + +#### 9.2.2.36 QE-Selector + +Void. + +##### 9.2.2.36A Qth Parameter + +Void. + +#### 9.2.2.37 RACH Slot Format + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|--------------------------|-------------------------| +| RACH Slot Format | | | ENUMERATED
(0..3,...) | See ref. TS 25.211 [7]. | + +#### 9.2.2.38 RACH Sub Channel Numbers + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RACH Sub Channel Numbers | | | BIT STRING (SIZE(12)) | Each bit indicates availability for a subchannel, where the subchannels are numbered "subchannel 0" to "subchannel 11". The value 1 of a bit indicates that the corresponding subchannel is available and the value 0 indicates that it is not available. The order of bits is to be interpreted according to subclause 9.3.4. | + +#### 9.2.2.39 RL Set ID + +The RL Set ID uniquely identifies one RL Set within a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| RL Set ID | | | INTEGER (0..31) | | + +#### 9.2.2.39a RL Specific E-DCH Information + +The *RL Specific E-DCH Information* IE provides RL specific E-DCH Information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|---------------------------|-----------------------|------------------------------------------------------| +| RL Specific E-DCH Information | | 1.. | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | +| E-AGCH Power Offset | O | | 9.2.2.13ld | | +| E-RGCH Power Offset | O | | 9.2.2.13le | | +| E-HICH Power Offset | O | | 9.2.2.13lf | | + +| Range Bound | Explanation | +|-----------------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | + +#### 9.2.2.39A Received Total Wide Band Power + +The Received total wide band power indicates the UL interference at a certain cell under CRNC, see ref. TS 25.215 [4]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|-----------------------------------------| +| Received Total Wide Band Power | | | INTEGER (0..621) | According to mapping in TS 25.133 [22]. | + +#### 9.2.2.39B Reference Received Total Wide Band Power + +When sent by the CRNC, the Reference Received Total Wide Band Power indicates the reference UL interference (received noise level) for a certain cell or cell portion under CRNC. This value may be used for E-DCH scheduling in the Node B. + +When reported by the Node B, the Reference Received Total Wide Band Power indicates the reference UL interference (received noise level as an estimate of the noise floor) estimate from the Node B. This value may be used, e.g. for admission or congestion control in the CRNS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| Reference Received Total Wide Band Power | | | INTEGER (0..621) | The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.133 [22]. | + +#### 9.2.2.39C Reference Received Total Wide Band Power Reporting + +The Reference Received Total Wide Band Power Reporting controls the indication of the Reference Received Total Wide Band Power estimate from the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-----------------------------------------------------------------|-----------------------| +| Reference Received Total Wide Band Power Reporting | | | ENUMERATED (Reference Received Total Wide Band Power Requested) | | + +##### 9.2.2.39D Reference Received Total Wide Band Power Support Indicator + +The Reference Received Total Wide Band Power Support Indicator indicates whether indication of Reference Received Total Wide Band Power is supported by the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------|----------|-------|-------------------------------------------------------------------------------|-----------------------| +| Reference Received Total Wide Band Power Support Indicator | | | ENUMERATED (Indication of Reference Received Total Wide Band Power supported) | | + +#### 9.2.2.40 S-Field Length + +Void. + +##### 9.2.2.40A Scheduling Information + +Void + +#### 9.2.2.41 Scrambling Code Change + +Void. + +#### 9.2.2.42 Scrambling Code Number + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------------------------------------------| +| Scrambling Code Number | | | INTEGER (0..15) | Identification of scrambling code see ref. TS 25.213 [9]. | + +#### 9.2.2.43 Secondary CCPCH Slot Format + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Secondary CCPCH Slot Format | | | INTEGER (0..17,...) | | + +##### 9.2.2.43A Secondary CPICH Information Change + +The *Secondary CPICH Information Change* IE indicates modification of information of the Secondary CPICH for channel estimation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-------------------------------------|-----------------------| +| CHOICE Secondary CPICH Information Change | M | | | | +| >New Secondary CPICH | | | | | +| >>Secondary CPICH Information | M | | Common Physical Channel ID 9.2.1.13 | | +| >Secondary CPICH Shall Not Be Used | | | NULL | | + +#### 9.2.2.44 SSDT Cell Identity + +Void. + +##### 9.2.2.44A SSDT Cell Identity For EDSCHPC + +Void. + +#### 9.2.2.45 SSDT Cell ID Length + +Void. + +#### 9.2.2.46 SSDT Support Indicator + +The SSDT Support Indicator indicates whether a RL supports SSDT or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------------------| +| SSDT Support Indicator | | | ENUMERATED ( Not Used, SSDT Not Supported) | The SSDT Support Indicator IE shall never be set to “Not Used”. If received it shall be rejected. | + +#### 9.2.2.47 SSDT Indication + +Void. + +#### 9.2.2.48 STTD Indicator + +Indicates if STTD shall be active or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------------------|-----------------------| +| STTD Indicator | | | ENUMERATED ( active, inactive, ...) | | + +#### 9.2.2.48A Synchronisation Indicator + +The *Synchronisation Indicator* IE indicates that Timing Maintained Synchronisation shall be used at start of Radio Link, see also TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------------------------------------------|-----------------------| +| Synchronisation Indicator | | | ENUMERATED
(Timing Maintained
Synchronisation, ...) | | + +#### 9.2.2.48B Serving E-DCH RL + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Serving E-DCH RL | M | | | | +| > Serving E-DCH RL in this Node B | | | | | +| >>Serving E-DCH RL ID | M | | RL ID
9.2.1.53 | | +| > Serving E-DCH RL not in this Node B | | | NULL | | + +#### 9.2.2.49 T Cell + +Timing delay used for defining start of SCH, CPICH and the DL scrambling code(s) in a cell relative BFN. Resolution 256 chips. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------|----------------------------------------------------------------------------------| +| T Cell | | | ENUMERATED
(0, 1,...,9) | Unit: chip
Range: 0..2304 chips
Step: 256 chips
See ref. TS 25.402 [17] | + +##### 9.2.2.49A TFCI2 Bearer Information Response + +Void. + +#### 9.2.2.50 TFCI Signalling Mode + +This parameter indicates if the normal or split mode is used for the TFCI. In the event that the split mode is to be used then the IE indicates whether the split is "Hard" or "Logical", and in the event that the split is "Logical" the IE indicates the number of bits in TFCI (field 2). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| TFCI Signalling Option | M | | ENUMERATED (
Normal,
Not Used) | The value "Not Used" shall not be used by the CRNC. The procedure shall be rejected by the Node B if the value "Not Used" is received. | +| Not Used | O | | NULL | | +| Not Used | O | | NULL | | + +#### 9.2.2.51 TGD + +Void. + +#### 9.2.2.52 TGL + +Void. + +#### 9.2.2.53 Transmit Diversity Indicator + +The Transmit Diversity Indicator indicates whether transmit diversity shall be active or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|--------------------------------|-----------------------| +| Transmit Diversity Indicator | | | ENUMERATED ( active, inactive) | | + +##### 9.2.2.53A Transmission Gap Pattern Sequence Information + +Defines the parameters for the compressed mode gap pattern sequence. For details see ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|---------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transmission Gap Pattern Sequence Information | | 1.. | | | +| >TGPS Identifier | M | | INTEGER (1..maxTGPS) | Transmission Gap Pattern Sequence Identifier:
Establish a reference to the compressed mode pattern sequence. Up to simultaneous compressed mode pattern sequences can be used. | +| >TGSN | M | | INTEGER (0..14) | Transmission Gap Starting Slot Number:
The slot number of the first transmission gap slot within the TGCFN. | +| >TGL1 | M | | INTEGER (1..14) | The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots. | +| >TGL2 | O | | INTEGER (1..14) | The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1. | +| >TGD | M | | INTEGER (0, 15.. 269) | Transmission Gap Distance:
indicates the number of slots between the starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to "0" ("0" =undefined). | +| >TGPL1 | M | | INTEGER (1..144,...) | The duration of transmission gap pattern 1 in frames. | +| >Not-to-be-used-1 | O | | INTEGER (1..144,...) | This IE shall never be included in the IE group. If received it shall be ignored. | +| >UL/DL Mode | M | | ENUMERATED ( UL only, DL only, UL/DL) | Defines whether only DL, only UL or combined UL/DL compressed mode is used. | +| >Downlink Compressed Mode Method | C-DL | | ENUMERATED ( Not Used, SF/2, Higher Layer Scheduling, ...) | Method for generating downlink compressed mode gap. The Downlink Compressed Mode Method IE shall never be set to "Not Used". | +| >Uplink Compressed Mode Method | C-UL | | ENUMERATED ( SF/2, Higher Layer Scheduling, ...) | Method for generating uplink compressed mode gap. | +| >Downlink Frame Type | M | | ENUMERATED (A, B,...) | Defines if frame structure type "A" or "B" shall be used in downlink compressed mode. | +| >DeltaSIR1 | M | | INTEGER (0..30) | Delta in SIR target value to be set in the Node B during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase).
Unit: dB
Range: 0..3 dB
Step: 0.1 dB | + +| | | | | | +|-----------------|---|--|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >DeltaSIRafter1 | M | | INTEGER (0..30) | Delta in SIR target value to be set in the Node B one frame after the frame containing the start of the first transmission gap in the transmission gap pattern.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB | +| >DeltaSIR2 | O | | INTEGER (0..30) | Delta in SIR target value to be set in the Node B during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase).
When omitted, DeltaSIR2 = DeltaSIR1.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB | +| >DeltaSIRafter2 | O | | INTEGER (0..30) | Delta in SIR target value to be set in the Node B one frame after the frame containing the start of the second transmission gap in the transmission gap pattern.
When omitted, DeltaSIRafter2 = DeltaSIRafter1.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------| +| UL | The IE shall be present if the UL/DL mode IE is set to "UL only" or "UL/DL". | +| DL | The IE shall be present if the UL/DL mode IE is set to "DL only" or "UL/DL". | + +| Range Bound | Explanation | +|----------------|------------------------------------------------------| +| maxTGPS | Maximum number of transmission gap pattern sequences | + +##### 9.2.2.53B Transmission Gap Pattern Sequence Code Information + +This IE indicates whether the alternative scrambling code shall used for the Downlink compressed mode method or not in the Transmission Gap Pattern Sequence. For details see TS 25.213 [9]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-------------------------------------------|----------------------------------------------------------------------------------------------| +| Transmission Gap Pattern Sequence Code Information | | | ENUMERATED ( Code Change, No Code Change) | Indicates whether the alternative scrambling code is used for compressed mode method "SF/2". | + +#### 9.2.2.54 UL/DL compressed mode selection + +Void. + +#### 9.2.2.55 UL delta SIR + +Void. + +#### 9.2.2.56 UL delta SIR after + +Void. + +#### 9.2.2.57 UL DPCCH Slot Format + +Indicates the slot format used in DPCCH in UL, according to ref. TS 25.211 [7]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UL DPCCH Slot Format | | | INTEGER (0..5,...) | If DCH Enhancement (Basic/Full) capabilities are not supported, value 5 shall not be used. If in this case value 5 is received, the procedure shall be rejected. | + +#### 9.2.2.58 UL SIR + +Void. + +#### 9.2.2.59 UL Scrambling Code + +The UL Scrambling Code is the scrambling code used by UE. Every UE has its specific UL Scrambling Code. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|---------------------------------|-----------------------| +| UL Scrambling Code Number | M | | INTEGER (0..2 24 -1) | | +| UL Scrambling Code Length | M | | ENUMERATED (Short, Long) | | + +#### 9.2.2.60 UL Capacity Credit + +Void. + +#### 9.2.2.61 UL DPDCH Indicator For E-DCH Operation + +The UL DPDCH Indicator For E-DCH Operation parameter indicates whether some UL DPCH parameters should be ignored or not in the message in which the *UL DPDCH Indicator For E-DCH Operation* IE was included or that any UL DPDCH resources shall be removed from the communication context configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------------------------------------|-----------------------| +| UL DPDCH Indicator For E-DCH Operation | | | ENUMERATED (UL-DPDCH present, UL-DPDCH not present) | | + +#### 9.2.2.62 Fast Reconfiguration Mode + +The *Fast Reconfiguration Mode* IE is used to notify the Node B that the SRNC would like to use the activation time “when the UE is detected on the new configuration” as the timing for the reconfiguration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| Fast Reconfiguration Mode | | | ENUMERATED (Fast,...) | | + +#### 9.2.2.63 Fast Reconfiguration Permission + +The *Fast Reconfiguration Permission* IE is used to indicate to the CRNC that the Node B can apply the activation time “when the UE is detected on the new configuration” for this reconfiguration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|--------------------------|-----------------------| +| Fast Reconfiguration Permission | | | ENUMERATED (Allowed,...) | | + +#### 9.2.2.64 Continuous Packet Connectivity DTX-DRX Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------|-----------------------| +| Continuous Packet Connectivity DTX-DRX Capability | | | ENUMERATED (Continuous Packet Connectivity DTX-DRX Capable, Continuous Packet Connectivity DTX-DRX Non-Capable) | | + +#### 9.2.2.65 Continuous Packet Connectivity HS-SCCH less Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Continuous Packet Connectivity HS-SCCH less Capability | | | ENUMERATED (Continuous Packet Connectivity HS-SCCH less Capable, Continuous Packet Connectivity HS-SCCH less Non-Capable) | | + +#### 9.2.2.66 Continuous Packet Connectivity DTX-DRX Information + +The *Continuous Packet Connectivity DTX-DRX Information* IE defines the parameters used for Continuous Packet Connectivity DTX-DRX operation (see ref. TS 25.214 [10]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-------------------------------------------------------|--------------------------------------------------------------------------|-------------|----------------------| +| UE DTX DRX Offset | M | | INTEGER (0..159) | Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI | – | | +| Enabling Delay | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) | Units of radio frames | – | | +| DTX Information | | 1 | | | | | +| >CHOICE E-DCH TTI Length | M | | | | – | | +| >>2ms | | | | | – | | +| >>>UE DTX Cycle 1 | M | | ENUMERATED (1, 4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >>>UE DTX Cycle 2 | M | | ENUMERATED (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128) | Units of subframes | – | | + +| | | | | | | | +|-----------------------------------------------|---|------|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-----|--------| +| | | | 160) | | | | +| >>>MAC DTX Cycle | M | | ENUMERATED (1, 4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >>10ms | | | | | – | | +| >>>UE DTX Cycle 1 | M | | ENUMERATED (1, 5, 10, 20) | Units of subframes | – | | +| >>>UE DTX Cycle 2 | M | | ENUMERATED (5, 10, 20, 40, 80, 160) | Units of subframes | – | | +| >>>MAC DTX Cycle | M | | ENUMERATED (5, 10, 20) | Units of subframes | – | | +| >Inactivity Threshold for UE DTX Cycle 2 | M | | ENUMERATED (1, 4, 8, 16, 32, 64, 128, 256) | Units of E-DCH TTIs | – | | +| >UE DTX Long Preamble | M | | ENUMERATED (2,4,15) | Units of slots | – | | +| >MAC Inactivity Threshold | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) | Units of E-DCH TTIs | – | | +| >CQI DTX Timer | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) | Units of subframes | – | | +| >UE DPCCH burst1 | M | | ENUMERATED (1, 2, 5) | Units of subframes | – | | +| >UE DPCCH burst2 | M | | ENUMERATED (1, 2, 5) | Units of subframes | – | | +| DRX Information | | 0..1 | | | | | +| >UE DRX Cycle | M | | ENUMERATED (4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >Inactivity Threshold for UE DRX Cycle | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512) | Units of subframes | – | | +| >Inactivity Threshold for UE Grant Monitoring | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256) | Units of E-DCH TTIs | – | | +| >UE DRX Grant Monitoring | M | | BOOLEAN | True: DRX Grant Monitoring shall be applied.
False: DRX Grant Monitoring shall not be applied. | – | | +| >UE DRX Cycle 2 | O | | ENUMERATED (v4, v5, v8, v10, v16, v20) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | +| >Inactivity Threshold for UE DRX Cycle 2 | O | | ENUMERATED (v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | + +#### 9.2.2.67 Continuous Packet Connectivity DTX-DRX Information To Modify + +The *Continuous Packet Connectivity DTX-DRX Information To Modify* IE is used for modification of Continuous Packet Connectivity DTX-DRX information in a Node B Communication Context. The *Continuous Packet Connectivity DTX-DRX Information To Modify* IE shall include at least one of the following IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|------------------------------------------------------------------|--------------------------------------------------------------------------|-------------|----------------------| +| UE DTX DRX Offset | O | | INTEGER (0..159) | Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI | – | | +| Enabling Delay | O | | ENUMERATE D (0, 1, 2, 4, 8, 16, 32, 64, 128) | Units of radio frames | – | | +| CHOICE DTX Information To Modify | O | | | | | | +| >Modify | | | | | – | | +| >>CHOICE E-DCH TTI Length | O | | | | – | | +| >>>2ms | | | | | | | +| >>>>UE DTX Cycle 1 | M | | ENUMERATE D (1, 4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >>>>UE DTX Cycle 2 | M | | ENUMERATE D (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160) | Units of subframes | – | | +| >>>>MAC DTX Cycle | M | | ENUMERATE D (1, 4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >>>10ms | | | | | | | +| >>>>UE DTX Cycle 1 | M | | ENUMERATE D (1, 5, 10, 20) | Units of subframes | – | | +| >>>>UE DTX Cycle 2 | M | | ENUMERATE D (5, 10, 20, 40, 80, 160) | Units of subframes | – | | +| >>>>MAC DTX Cycle | M | | ENUMERATE D (5, 10, 20) | Units of subframes | – | | +| >>Inactivity Threshold for UE DTX Cycle 2 | O | | ENUMERATE D (1, 4, 8, 16, 32, 64, 128, 256) | Units of E-DCH TTIs | – | | +| >>UE DTX Long Preamble | O | | ENUMERATE D (2,4,15) | Units of slots | – | | +| >>MAC Inactivity Threshold | O | | ENUMERATE D ( 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) | Units of E-DCH TTIs | – | | +| >>CQI DTX Timer | O | | ENUMERATE D (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) | Units of Subframes | – | | +| >>UE DPCCH burst1 | O | | ENUMERATE D (1, 2, 5) | Units of Subframes | – | | +| >>UE DPCCH burst2 | O | | ENUMERATE D (1, 2, 5) | Units of Subframes | – | | +| >Deactivate | | | NULL | | – | | + +| | | | | | | | +|------------------------------------------------|---|--|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-----|--------| +| CHOICE DRX Information To Modify | O | | | | | | +| >Modify | | | | | – | | +| >>UE DRX Cycle | O | | ENUMERATE D ( 4, 5, 8, 10, 16, 20) | Units of subframes | – | | +| >>Inactivity Threshold for UE DRX Cycle | O | | ENUMERATE D (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512) | Units of subframes | – | | +| >>Inactivity Threshold for UE Grant Monitoring | O | | ENUMERATE D (0, 1, 2, 4, 8, 16, 32, 64, 128, 256) | Units of E-DCH TTIs | – | | +| >>UE DRX Grant Monitoring | O | | BOOLEAN | True: DRX Grant Monitoring shall be applied.
False: DRX Grant Monitoring shall not be applied. | – | | +| >>UE DRX Cycle 2 | O | | ENUMERATE D ( v4, v5, v8, v10, v16, v20) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | +| >>Inactivity Threshold for UE DRX Cycle 2 | O | | ENUMERATE D (v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | +| >Deactivate | | | NULL | | | | + +#### 9.2.2.68 Continuous Packet Connectivity HS-SCCH less Information + +The *Continuous Packet Connectivity HS-SCCH less Information* IE defines the parameters used for Continuous Packet Connectivity HS-SCCH less operation (see ref. TS 25.214 [10]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|--------------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------| +| Transport Block Size List | | 1.. | | | +| >Transport Block Size Index | M | | INTEGER (1..maxNrOfHS-DSCH-TBSs) | | +| >HS-PDSCH Second Code Support | M | | BOOLEAN | True = The second HS-PDSCH code shall also be used
False = The second HS-PDSCH code shall not be used | + +| Range Bound | Explanation | +|---------------------------------|---------------------------------------------------------------------------------| +| maxNrOfHS-DSCH-TBSs-HS-SCCHless | Maximum number of HS-DSCH Transport Block Sizes used for HS-SCCH-less operation | +| maxNrOfHS-DSCH-TBSs | Maximum number of HS-DSCH Transport Block Sizes | + +#### 9.2.2.69 Continuous Packet Connectivity HS-SCCH less Information Response + +The *Continuous Packet Connectivity HS-SCCH less Information Response* IE provides information for HS-SCCH less operation determined within the Node B (see ref. TS 25.214 [10]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------------------------|-------------------------------------------| +| HS-PDSCH First Code Index | M | | INTEGER
(1..maxHS-PDSCHCodeNrComp-1) | Index of first HS-PDSCH code | +| HS-PDSCH Second Code Index | O | | INTEGER
(1..maxHS-PDSCHCodeNrComp-1) | Index of second HS-PDSCH code See NOTE 1. | + +NOTE 1: The "HS-PDSCH second code index" value is the value of IE "HS-PDSCH First Code Index" incremented by 1. + +##### 9.2.2.69A Continuous Packet Connectivity HS-SCCH less Deactivate Indicator + +The *Continuous Packet Connectivity HS-SCCH less Deactivate Indicator* IE is used to deactivate HS-SCCH less operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Continuous Packet Connectivity HS-SCCH less Deactivate Indicator | M | | NULL | | + +| Range Bound | Explanation | +|------------------------------|----------------------------------------------------------------------------------------| +| maxHS-PDSCHCodeNrComp | Maximum number of codes at the defined spreading factor, within the complete code tree | + +#### 9.2.2.70 MIMO Capability + +Void + +#### 9.2.2.71 MIMO Activation Indicator + +Void + +#### 9.2.2.72 MIMO Mode Indicator + +Void + +#### 9.2.2.73 MIMO Pilot Configuration + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-------------------------------------|-----------------------| +| CHOICE Pilot Configuration | M | | | | +| >Primary and Secondary CPICH | | | | | +| >>Associated Secondary CPICH | M | | Common Physical Channel ID 9.2.1.13 | | +| >Normal and Diversity Primary CPICH | | | NULL | | + +#### 9.2.2.74 SixtyfourQAM DL Capability + +Void. + +##### 9.2.2.74A Sixtyfour QAM Usage Allowed Indicator + +The *Sixtyfour QAM Usage Allowed Indicator* IE indicates whether the Node B is allowed to use 64 QAM modulation for HS-DSCH transmission or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|--------------------------------------|-----------------------| +| Sixtyfour QAM Usage Allowed Indicator | M | | ENUMERATED
(Allowed, Not-Allowed) | | + +##### 9.2.2.74B SixtyfourQAM DL Usage Indicator + +The *SixtyfourQAM DL Usage Indicator* IE indicates if the Node B is using 64 QAM modulation for the HS-DSCH transmission, or if the Node B is not using 64 QAM modulation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|----------------------------------------------------------------|-----------------------| +| SixtyfourQAM DL Usage Indicator | | | ENUMERATED
(SixtyfourQAM DL Used, SixtyfourQAM DL Not Used) | | + +#### 9.2.2.75 HS-DSCH Common System Information + +The *HS-DSCH Common System Information* IE provides information for HS-DSCH configured for UE in Cell\_FACH, in Cell\_PCH and in URA\_PCH and Information related to BCCH modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|-----------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH Common Information | | 0..1 | | | – | | +| >CCCH Priority Queue ID | M | | Priority Queue ID 9.2.1.49C | | – | | +| >SRB#1 Priority Queue ID | M | | Priority Queue ID 9.2.1.49C | | – | | +| >Associated Common MAC Flow | M | | Common MAC Flow ID 9.2.2.79 | The Common MAC Flow ID shall be one of the flow IDs defined in the Common MAC Flow Specific Information of this IE or shall only refer to a Common MAC flow already existing in the old configuration. | – | | +| >FACH Measurement Occasion Cycle Length Coefficient | O | | 9.2.1.111 | | – | | +| >RACH Measurement Result | M | | 9.2.2.84 | | – | | +| >BCCH Specific HS-DSCH-RNTI Information | M | | 9.2.2.85 | | – | | +| Common MAC Flow Specific Information | | 0.. | | | – | | +| >Common MAC Flow ID | M | | 9.2.2.79 | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Common MAC Flow Priority Queue Information | | 0.. | | | – | | +| >>Priority Queue Information for Enhanced FACH | M | | Priority Queue Information for Enhanced FACH/PCH 9.2.1.117 | | – | | +| >Transport Bearer Request Indicator | O | | 9.2.1.62A | Shouldn't be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure | – | | +| Common HS-DSCH RNTI List | O | | 9.2.2.148 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------| +| maxNrOfCommonMACFlows | Maximum number of Common MAC Flows | +| maxNrOfcommonMACQueues | Maximum number of Priority Queues for Common MAC Flow | + +#### 9.2.2.76 HS-DSCH Paging System Information + +The *HS-DSCH Paging System Information* IE provides information for HS-DSCH configured for UE in Cell\_PCH and URA\_PCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-----------------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Paging MAC Flow Specific Information | | 1.. | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | +| >HSDPA Associated PICH Information | M | | 9.2.2.81 | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | +| >ToAWS | M | | 9.2.1.61 | | +| >ToAWE | M | | 9.2.1.60 | | +| >Paging MAC Flow Priority Queue Information | | 0.. | | | +| >>Priority Queue Information for Enhanced PCH | M | | Priority Queue Information for Enhanced FACH/PCH
9.2.1.117 | | +| >Transport Bearer Request Indicator | O | | 9.2.1.62A | Shouldn't be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure | +| HS-SCCH Power | M | | DL Power
9.2.1.21 | | +| HS-PDSCH Power | M | | DL Power
9.2.1.21 | | +| Number of PCCH transmissions | M | | INTEGER
(1..5) | Number of subframes used to transmit the PCCH. | +| Transport Block Size List | | 1.. | | | +| >Transport Block Size Index for Enhanced PCH | M | | INTEGER
(1..32) | Index of the value range 1 to 32 of the MAC-ehs transport block size as specified in appendix A of TS 25.321 [32] | + +| Range bound | Explanation | +|-------------------------------|---------------------------------------------------------------------------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | +| maxNrOfPagingMACQueues | Maximum number of Priority Queues for Paging MAC Flow | +| maxNrOfHS-DSCHTBSSePCH | Maximum number of HS-DSCH Transport Block Sizes used for Enhanced PCH operation associated HS-SCCH less | + +#### 9.2.2.77 HS-DSCH Common System Information Response + +The *HS-DSCH Common System Information Response* IE provides information for HS-DSCH configured for UE not in Cell\_DCH that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-----------------------------------------|-----------------------|----------------------------------------------------------------------------------------| +| HS-SCCH Specific Information Response | | 0..<maxNrOfHSSCCHCodes> | | Channelization codes on HS-SCCH is transmitted for UE not in Cell_DCH | +| >Code Number | M | | INTEGER (0..127) | First indexed HS-SCCH Channelisation code should be used for the BCCH specific H-RNTI. | +| HARQ Memory Partitioning | O | | 9.2.1.102 | | +| Common MAC Flow Specific Information Response | | 0..<maxNrOfCommonMACFlows> | | | +| >Common MAC Flow ID | M | | 9.2.2.79 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | +| >HS-DSCH Initial Capacity Allocation | O | | 9.2.1.31Ha | | + +| Range Bound | Explanation | +|------------------------------|------------------------------------| +| maxNrOfCommonMACFlows | Maximum number of Common MAC Flows | +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | + +#### 9.2.2.78 HS-DSCH Paging System Information Response + +The *HS-DSCH Paging System Information Response* IE provides information for HS-DSCH configured for UE in Cell\_PCH and URA\_PCH that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|----------------------------------------|--------------------------------------|------------------------| +| Paging MAC Flow Specific Information Response | | 1..<maxNrOfPagingMACFlow> | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | +| >HS-PDSCH Code Index | M | | INTEGER (1..maxHS-PDSCHCodeNrComp-1) | Index of HS-PDSCH code | + +| Range bound | Explanation | +|-----------------------------|------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | + +#### 9.2.2.79 Common MAC Flow ID + +Common MAC Flow ID is the unique identifier for one Common MAC flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| Common MAC Flow ID | | | INTEGER (0..7) | | + +#### 9.2.2.80 Paging MAC Flow ID + +Void. + +#### 9.2.2.81 HSDPA Associated PICH Information + +The *HSDPA Associated PICH Information* IE provides information for PICH used for Enhanced PCH operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|------------------------| +| CHOICE HSDPA PICH | | | | | +| >Shared with PCH | | | | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | +| >Not shared with PCH | | | | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | +| >>FDD DL Channelisation Code Number | M | | 9.2.2.14 | | +| >>PICH Power | M | | 9.2.1.49A | | +| >>PICH Mode | M | | 9.2.2.26 | Number of PI per frame | +| >>STTD Indicator | M | | 9.2.2.48 | | + +#### 9.2.2.82 FACH Measurement Occasion Cycle Length Coefficient + +Void. + +#### 9.2.2.83 Priority Queue Information for Enhanced FACH/PCH + +Void. + +#### 9.2.2.84 RACH Measurement Result + +The RACH Measurement Result identifies which RACH measurement result is forwarded to Node B in Frame Protocol. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-------------------------------------------------------------|-----------------------| +| RACH Measurement Result | | | ENUMERATED
(CPICH Ec/No,
CPICH RSCP,
Pathloss,...) | | + +#### 9.2.2.85 BCCH Specific HS-DSCH RNTI Information + +The *BCCH Specific HS-DSCH RNTI Information* IE provides information for BCCH Transmission using HS-DSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------|-----------------------| +| BCCH Specific HS-DSCH RNTI | M | | HS-DSCH RNTI
9.2.1.31J | | +| HS-SCCH Power | M | | DL Power
9.2.1.21 | | +| HS-PDSCH Power | M | | DL Power
9.2.1.21 | | + +#### 9.2.2.86 Enhanced FACH Capability + +Void. + +#### 9.2.2.87 Enhanced PCH Capability + +Void. + +#### 9.2.2.88 SixteenQAM UL Capability + +This parameter defines the SixteenQAM uplink capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|---------------------------------------------------------------------|-----------------------| +| SixteenQAM UL Capability | | | ENUMERATED
(SixteenQAM UL Capable,
SixteenQAM UL Non-Capable) | | + +##### 9.2.2.88A SixteenQAM UL Operation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------------------------|-----------------------| +| SixteenQAM UL Operation Indicator | | | ENUMERATED
(Activate,
Deactivate) | | + +#### 9.2.2.88B E-TFCI Boost Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|--------------------------|-------|-------------------------|---------------------------------------------------------------------------------| +| E-TFCI BetaEC Boost | M | | INTEGER
(0..127,...) | E-TFCI threshold beyond which boosting of E-DPCCH is enabled | +| UL Delta T2TP | C-E-TFCIboost 127 | | INTEGER (0..6,...) | Total E-DPDCH power across all codes to the combined power of DPCCH and E-DPCCH | + +| Condition | Explanation | +|-----------------------|---------------------------------------------------------------------------------------| +| E-TFCIboost127 | The IE shall be present if the E-TFCI BetaEC Boost IE value is not set to 127. | + +#### 9.2.2.88C SixtyfourQAM UL Operation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------------------------|-----------------------| +| SixtyfourQAM UL Operation Indicator | | | ENUMERATED
(Activate,
Deactivate) | | + +#### 9.2.2.89 SixteenQAM UL Information + +Void. + +#### 9.2.2.90 SixteenQAM UL Information To Modify + +Void. + +#### 9.2.2.91 Modulation Power Offset + +Indicates the modulation, and power offset in case of 16QAM, to be used for the Secondary CCPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------| +| CHOICE Modulation | M | | | | +| >QPSK | | | NULL | | +| >QAM | | | | | +| >>CPICH Secondary CCPCH Power Offset | M | | INTEGER (-11..4,...) | Power offset between CPICH and secondary CCPCH.
Unit: dB
Range: -11 .. +4 dB
Step: 1 dB | + +#### 9.2.2.92 Extended Secondary CCPCH Slot Format + +Indicates the slot format used for the Secondary CCPCH. The extended slot format shall only be used for MBSFN. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| Extended Secondary CCPCH Slot Format | | | INTEGER(18..23,...) | | + +#### 9.2.2.93 F-DPCH Slot Format + +The *F-DPCH Slot Format* IE defines the F-DPCH slot format for the TPC bits, as defined in TS 25.211 [7]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| F-DPCH Slot Format | | | INTEGER (0..9) | | + +#### 9.2.2.94 F-DPCH Slot Format Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-------------------------------------------------------------------------|-----------------------| +| F-DPCH Slot Format Capability | | | ENUMERATED (F-DPCH Slot Format Capable, F-DPCH Slot Format Non-Capable) | | + +#### 9.2.2.95 Max UE DTX Cycle + +The *Max UE DTX Cycle* IE defines the maximum UE DTX cycle supported by the Node B for Continuous Packet Connectivity DTX-DRX operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------| +| Max UE DTX Cycle | M | | ENUMERATED (v5, v10, v20, v40, v64, v80, v128, v160,..., v256, v320, v512, v640, v1024, v1280) | Units of subframes | + +#### 9.2.2.96 MIMO N/M Ratio + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|--------------------------------------------------------------------|-----------------------| +| MIMO N/M Ratio | M | | ENUMERATED (1/2, 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 1/1,...) | | + +#### 9.2.2.97 Common MAC Flows To Delete + +The *Common MAC Flows To Delete* IE is used for the removal of Common MAC flows from a Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|----------------------------|-----------------------|-----------------------| +| Common MAC Flows To Delete | | 1.. | | | +| >Common MAC Flow ID | M | | 9.2.2.79 | | + +| Range Bound | Explanation | +|-----------------------|------------------------------------| +| maxNrOfCommonMACFlows | Maximum number of Common MAC Flows | + +#### 9.2.2.98 Paging MAC Flows To Delete + +The *Paging MAC Flows To Delete* IE is used for the removal of Paging MAC flows from a Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|---------------------------|-----------------------|-----------------------| +| Paging MAC Flows To Delete | | 1.. | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | + +| Range Bound | Explanation | +|----------------------|------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | + +#### 9.2.2.99 MAC-ehs Reset Timer + +Void. + +#### 9.2.2.100 E-AGCH Table Choice + +The *E-AGCH Table Choice* IE indicates the choice of the E-AGCH table in TS 25.212 [8]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-AGCH Table Choice | M | | ENUMERATED (Table 16B, Table 16B-1, ...) | Table 16B indicates the Table 16B: Mapping of Absolute Grant Value in TS 25.212 [8] and Table 16B-1 indicates the Table 16B.1: Alternative Mapping of Absolute Grant Value in TS 25.212 [8]. | + +#### 9.2.2.101 Common E-DCH Capability + +This parameter defines the Common E-DCH capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-------------------------------------------------------------|-----------------------| +| Common E-DCH Capability | | | ENUMERATED (Common E-DCH Capable, Common E-DCH non Capable) | | + +#### 9.2.2.102 E-AI Capability + +This parameter defines the E-AI capability for a Common E-DCH capable Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|---------------------------------------------|-----------------------| +| E-AI Capability | | | ENUMERATED (E-AI Capable, E-AI non Capable) | | + +#### 9.2.2.103 Common E-DCH System Information + +The *Common E-DCH System Information* IE provides information for E-DCH configured for UE in Cell\_FACH and Idle state. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Common E-DCH UL DPCH Information | | 0..1 | | | – | | +| >UL SIR Target | M | | UL SIR
9.2.1.67A | | – | | +| >DPC Mode | O | | 9.2.2.13C | If received, this IE shall be ignored. DPC mode 0 shall be applied for Common E-DCH(see ref. TS 25.214 [10]). | – | | +| Common E-DCH E-DPCH Information | | 0..1 | | | – | | +| >Maximum Set of E-DPDCHs | M | | 9.2.2.20C | | – | | +| >Puncture Limit | M | | 9.2.1.50 | | – | | +| >E-TFCS Information | M | | 9.2.2.13Dh | | – | | +| >E-TTI | M | | 9.2.2.13Di | | – | | +| >E-DPCH Power Offset | M | | 9.2.2.13Dj | | – | | +| >E-RGCH 2-Index-Step Threshold | O | | 9.2.2.13lg | | – | | +| >E-RGCH 3-Index-Step Threshold | O | | 9.2.2.13lh | | – | | +| >HARQ Info for E-DCH | M | | 9.2.2.18ba | | – | | +| Common E-DCH Information | | 0..1 | | | – | | +| >E-DCH Reference Power Offset | O | | 9.2.2.13Y | | – | | +| >E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | – | | +| >Maximum E-DCH resource allocation for CCCH | M | | ENUMERATED
(8, 12, 16, 24, 32, 40, 80, 120,..., 20) | Interns of TTIs, Value 120 should not be used | – | | +| >Maximum period for collision resolution phase | M | | INTEGER(8..24,..) | Interns of TTIs | – | | +| >Maximum TB Sizes | O | | 9.2.2.106 | | – | | +| >Common E-DCH implicit release indicator | M | | BOOLEAN | TRUE means implicit release is in use. FALSE means implicit release is not in use. | – | | +| >Common E-DCH Additional Transmission Back Off | O | | INTEGER
(0..15,...) | | YES | ignore | +| >Common E-DCH Implicit Release Timer | O | | ENUMERATE(
zero,
more than zero) | Indicates the value of E-DCH transmission continuation back off as defined in TS 25.331 [18]. | YES | ignore | +| Common E-DCH HS-DPCCH Information | | 0..1 | | | – | | +| >ACK-NACK Repetition Factor | M | | 9.2.2.a | | – | | +| >ACK Power Offset | M | | 9.2.2.b | | – | | +| >NACK Power Offset | M | | 9.2.2.23a | | – | | + +| | | | | | | | +|--------------------------------------------------|-------------|------|-----------------------------------|----------------------------------------------------------------------------------------|-----|--------| +| >Common E-DCH CQI Information | O | | | | – | | +| >>CQI Feedback Cycle k | M | | 9.2.2.21B | | – | | +| >>CQI Repetition Factor | C-CQICyclek | | 9.2.2.4Cb | | – | | +| >>CQI Power Offset | M | | 9.2.2.4Ca | | – | | +| >>Measurement Power Offset | M | | 9.2.2.21C | | – | | +| Common E-DCH Preamble Control Information | | 0..1 | | | – | | +| >Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >Common E-DCH Preamble Signature | M | | Preamble Signatures 9.2.2.31 | | – | | +| >Scrambling Code Number | M | | 9.2.2.42 | | – | | +| >Preamble Threshold | M | | 9.2.2.32 | | – | | +| >E-AI Indicator | O | | BOOLEAN | TRUE means E-AIs are in use on the AICH. FALSE means E-AIs are not in use on the AICH. | – | | +| >Common E-DCH AICH Information | | 0..1 | | | – | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | – | | +| >>AICH Transmission Timing | M | | 9.2.2.1 | | – | | +| >>FDD DL Channelisation Code Number | M | | 9.2.2.14 | | – | | +| >>AICH Power | M | | 9.2.2.D | | – | | +| >>STTD Indicator | M | | 9.2.2.48 | | – | | +| Common E-DCH F-DPCH Information | | 0..1 | | | – | | +| >F-DPCH slot format | M | | 9.2.2.93 | | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | Initial power on F-DPCH | YES | ignore | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on F-DPCH | YES | ignore | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on F-DPCH | YES | ignore | +| Common E-DCH E-AGCH Channelisation Code Number | O | | FDD DL Channelisation Code Number | | – | | + +| | | | | | | | +|--|--|--|----------|--|--|--| +| | | | 9.2.2.14 | | | | +|--|--|--|----------|--|--|--| + +| | | | | | | | +|------------------------------------------------------|---|------------------------------------------|--------------------------------------------|------------------------------------------------------|-----|--------| +| Common E-DCH Resource Combination Information | | 0..<max NrOfCommonE DCH> | | | – | | +| >Soffset | M | | INTEGER (0..9,...) | | – | | +| >F-DPCH DL Code Number | M | | FDD DL Channelisation Code Number 9.2.2.14 | | – | | +| >UL DPCH Scrambling Code | M | | UL Scrambling Code 9.2.2.59 | | – | | +| >E-RGCH/E-HICH Channelisation Code | M | | FDD DL Channelisation Code Number 9.2.2.14 | | – | | +| >E-RGCH Signature Sequence | O | | INTEGER (0..maxNrofSigSeq RGHI-1) | | – | | +| >E-HICH Signature Sequence | M | | INTEGER (0..maxNrofSigSeq RGHI-1) | | – | | +| UL Common MAC Flow Specific Information | | 0..<max NrOfCommonMACFlows> | | | – | | +| >UL Common MAC Flow ID | M | | Common MAC Flow ID 9.2.2.79 | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Payload CRC Presence Indicator | M | | 9.2.1.49 | | – | | +| >Bundling Mode Indicator | O | | 9.2.2.1Bb | | – | | +| >Common E-DCH MAC-d Flow Specific Information | M | | 9.2.2.105 | | – | | +| E-RNTI List Request | O | | NULL | | YES | ignore | +| E-AGCH Power Offset | O | | 9.2.2.13Id | | YES | ignore | +| E-RGCH Power Offset | O | | 9.2.2.13Ie | | YES | ignore | +| E-HICH Power Offset | O | | 9.2.2.13If | | YES | ignore | +| Concurrent Deployment of 2ms and 10ms TTI | O | | | | YES | ignore | + +| | | | | | | | +|------------------------------------------------------------------|---|-------------------------|--------------------------------------------------------------------|------------------------------------------------------------|-----|--------| +| >Concurrent TTI Partition Index | M | | INTEGER (maxNrOfCommonEDCH) | | – | | +| >Common E-DCH System Info Parameters for Concurrent TTI | M | | 9.2.2.191 | | – | | +| Common E-DCH Preamble Control Information extension Type1 | O | | Common E-DCH Preamble Control Information extension list 9.2.2.186 | | YES | ignore | +| Common E-DCH Preamble Control Information extension Type2 | O | | Common E-DCH Preamble Control Information extension list 9.2.2.186 | | YES | ignore | +| Common E-DCH Preamble Control Information extension Type3 | O | | Common E-DCH Preamble Control Information extension list 9.2.2.186 | | YES | ignore | +| NodeB Triggered HS-DPCCH Transmission Information | O | | | | YES | ignore | +| >HS-DPCCH transmission continuation back off | M | | ENUMERATED (10,20,30,40,80, 160,320,800, infinity, ...) | In terms of ms. The value infinity means explicit release. | – | | +| Per HARQ Activation and Deactivation | O | | | | YES | ignore | +| >Configuration for 2ms TTI Common E-DCH Resources | | 1.. | | | | | +| >>2ms HARQ Process Allocation | M | | HARQ Process Allocation for 2ms TTI 9.2.2.13Dn | | – | | +| Coffset | O | | Integer(0..29) | (0..29) indicates cell offset as defined in [7] | YES | ignore | +| E-RNTI Set | O | | E-RNTI Set 9.2.2.218 | | YES | ignore | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------------------| +| CQICyclek | The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0. | + +| Range bound | Explanation | +|------------------------------|----------------------------------------------------------------| +| maxNrOfCommonMACFlows | Maximum number of Common MAC Flows | +| maxNrOfCommonEDCH | Maximum number of Common E-DCH Resource Combination for a cell | +| maxNrofSigSeqRGHI | Maximum number of Signature Sequences for E-RGCH/E-HICH. | + +#### 9.2.2.104 Common E-DCH System Information Response + +The *Common E-DCH System Information Response* IE provides information for E-DCH configured for UE in Cell\_FACH and Idle state that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------------|----------|-----------------------------|-----------------------------|----------------------------------------------------------------------------------------------------|-------------|----------------------| +| UL Common MAC Flow Specific Information Response | | 1..> | | | – | | +| >UL Common MAC Flow ID | M | | Common MAC Flow ID 9.2.2.79 | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| Serving Grant Value | M | | INTEGER (0..37,38) | (0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; Index 38 is not allowed | – | | +| E-RNTI List | O | | 9.2.2.139 | The Node B shall not allocate any E-RNTIs listed in this IE for a UE | YES | ignore | +| UE Status Update Confirm Indicator | O | | BOOLEAN | TRUE means that the Node B supports UE Status Update Confirmation Procedure | YES | ignore | +| Serving Grant Value for Concurrent Deployment of 2ms and 10ms TTI | O | | INTEGER (0..38) | (0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; Index 38 is not allowed. | YES | ignore | + +| Range bound | Explanation | +|-----------------------|------------------------------------| +| maxNrOfCommonMACFlows | Maximum number of Common MAC Flows | + +#### 9.2.2.105 Common E-DCH MAC-d Flow Specific Information + +The *Common E-DCH MAC-d Flow Specific Information* IE is used for the establishment or modify Common E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------|----------|------------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------|-------------|----------------------| +| Common E-DCH MAC-d Flow Specific Information | | 1..<maxNrOfEDCHMACdFlows> | | | - | | +| >Common E-DCH MAC-d Flow ID | M | | E-DCH MAC-d Flow ID 9.2.1.74 | The E-DCH MAC-d flow identity reserved for CCCH transmission is defined in TS 25.331 [18]. | - | | +| >Maximum Number Of Retransmissions For E-DCH | M | | 9.2.1.81 | | - | | +| >E-DCH HARQ Power Offset FDD | M | | 9.2.2.13Dk | | - | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | - | | +| >Common E-DCH Logical Channel information | | 1..<maxnooflogicalchannels> | | | - | | +| >>Logical Channel ID | M | | 9.2.1.80 | | - | | +| >>Maximum MAC-c PDU Size Extended | M | | MAC PDU Size Extended 9.2.1.38C | | - | | +| >>Scheduling Priority Indicator | O | | 9.2.1.53H | | YES | ignore | +| >Common E-DCH MAC-d flow info for Concurrent TTI | | 0..1 | | | YES | ignore | +| >>Maximum Number Of Retransmissions For E-DCH | O | | 9.2.1.81 | | - | | +| >>E-DCH HARQ Power Offset FDD | O | | 9.2.2.13Dk | | - | | + +| Range bound | Explanation | +|-------------------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d Flows | +| maxnooflogicalchannels | Maximum number of logical channels | + +#### 9.2.2.106 Maximum TB Size + +The *Maximum TB Size* IE may be used by the scheduler in order to minimize the cell edge interference for cell edge users (and other users). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| Maximum TB Size cell edge users | M | | INTEGER (0..5000,...) | Unit: Bits | +| Maximum TB Size other users | M | | INTEGER (0..5000,...) | Unit: Bits | + +#### 9.2.2.107 Enhanced UE DRX Capability + +Void. + +#### 9.2.2.108 Enhanced UE DRX Information + +The *Enhanced UE DRX Information* IE provides information for configuring the UE in Cell\_FACH state to discontinuously receive HS-DSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| T321 | M | | ENUMERATED (100, 200, 400, 800,...) | Determines the time the UE waits until initiating DRX operation, in ms. | +| HS-DSCH DRX cycle FACH | M | | ENUMERATED (4, 8, 16, 32,...) | Determines the length of the DRX Cycle during DRX operation, in frames | +| HS-DSCH Rx burst FACH | M | | ENUMERATED (1, 2, 4, 8, 16,...) | Determines the period within the DRX Cycle that the UE continuously receives HS-DSCH, in frames | +| DRX Interruption by HS-DSCH data | M | | ENUMERATED (DrxInterruptionConfigured, DrxInterruptionNotConfigured) | | + +#### 9.2.2.109 E-DPCCH Power Boosting Capability + +This parameter defines the E-DPCCH Power Boosting Capability for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|---------------------------------------------------------------------------------|-----------------------| +| E-DPCCH Power Boosting Capability | | | ENUMERATED (E-DPCCH Power Boosting Capable, E-DPCCH Power Boosting Non-Capable) | | + +#### 9.2.2.110 SixtyfourQAM DL and MIMO Combined Capability + +Void + +#### 9.2.2.111 HS-DSCH Preconfiguration Info + +The *HS-DSCH Preconfiguration Info* IE provides information of the target cell preconfiguration in the Node B as defined in TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------------|----------|-------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Sets of HS-SCCH Codes | | 1...
| | Index 1 refers to the serving HS-DSCH cell
Index 2...
refer to secondary serving HS-DSCH cells in the order as listed in 9.2.2.112 HS-DSCH Preconfiguration Setup. Max index is 4 in this 3GPP release. | – | | +| > HS-SCCH Preconfigured Codes | | 1.. | | | – | | +| >> Code Number | M | | INTEGER (0..127) | | – | | +| > SixtyfourQAM DL Usage Indicator | O | | 9.2.2.74B | | – | | +| > HS-DSCH TB Size Table Indicator | O | | 9.2.2.18Ee | | – | | +| > MIMO N/M Ratio | O | | 9.2.2.96 | Applicable for multicarrier mode of operation. | YES | ignore | +| HARQ Memory Partitioning | M | | 9.2.1.102 | | – | | +| E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | For the primary UL frequency in Dual-cell E-DCH mode of operation. | – | | +| HARQ Preamble Mode Activation Indicator | O | | 9.2.2.18b | | – | | +| MIMO N/M Ratio | O | | 9.2.2.96 | Only applicable for MIMO in singe carrier mode of operation. Shall be ignored in multicarrier mode of operation. | – | | +| Continuous Packet Connectivity HS-SCCH less Information Response | O | | 9.2.2.69 | | – | | +| Additional E-DCH Preconfiguration Information | | 0.. | | For E-DCH on multiple frequencies in this Node B.
E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. Index 1 correspond to the secondary serving HS-DSCH cells with index 2 in the IE Sets of HS-SCCH Codes . The list is in the order as listed in 9.2.2.112 HS-DSCH Preconfiguration Setup. | EACH | ignore | +| >E-DCH FDD DL Control Channel Information | M | | 9.2.2.13Dc | For the secondary UL frequency In Dual-cell E-DCH mode of operation. | – | | +| Support of dynamic DTXDRX related HS-SCCH order | O | | 9.2.2.150 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------------------------------------| +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | +| maxNrOfHSDSCH | Maximum number of Primary Serving plus Secondary Serving HS-DSCH cells for one UE | + +#### 9.2.2.112 HS-DSCH Preconfiguration Setup + +The *HS-DSCH Preconfiguration Setup* IE indicates that the Node B shall preconfigure set(s) of HS-SCCH codes and may contain a list of secondary serving, assisting serving, and assisting secondary serving HS-DSCH cells to be preconfigured for Enhanced Service Cell Change. The Cell Change procedure for Dual Cell operation is described in TS 25.308 [49] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------------|----------|------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| MAC-hs/ehs reset scheme | M | | ENUMERATED (Always, Inter NodeB Change) | MAC-hs/ehs reset handling at enhanced HS serving cell change: "Always" means always reset "Inter Node B Change" means Only reset at Inter Node B cell change | – | | +| HS-DSCH Physical Layer Category | M | | 9.2.1.31a | | – | | +| MAC-hs Reordering Buffer Size for RLC-UM | M | | 9.2.1.38Ab | | – | | +| Secondary Cells | | 0... | | Preconfigured secondary serving HS-DSCH cell. maxNrOfHSDSCH-1 is max 7 in this 3GPP release. | – | | +| >Secondary C-ID | M | | C-ID 9.2.1.9 | C-ID of the preconfigured secondary serving HS-DSCH cell | – | | +| >Num Secondary HS-SCCH Codes | O | | INTEGER (1..maxNrOfHSSCCHCodes) | For the secondary serving HS-DSCH cell | – | | +| >Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | For the secondary serving HS-DSCH cell | – | | +| >MIMO Activation Indicator | O | | 9.2.1.119 | For the secondary serving HS-DSCH cell | YES | ignore | +| >E-DCH Indicator | O | | NULL | The secondary serving HS-DSCH cell shall be pre-configured with E-DCH. | YES | ignore | +| >Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link. | YES | ignore | +| >MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.164 | For the secondary serving HS-DSCH cell. | YES | ignore | +| >Dual Stream MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.167 | For the secondary serving HS-DSCH cell. | YES | ignore | +| >Multiflow Ordinal Number Of Frequency | O | | INTEGER (1..32,...) | In intra-Node B multiflow case, the Value specifies the index of the secondary serving or | YES | ignore | + +| | | | | | | | +|-------------------------------------------------------------------|---|--|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212.
In inter-Node B multiflow case, if present, the Value must be "1" when there is one secondary serving HS-DSCH cell.
Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8]. | | | +| Num Primary HS-SCCH Codes | O | | INTEGER (1..maxNrOfHSSCCHCodes) | For the primary serving HS-DSCH cell | – | | +| HARQ Preamble Mode | O | | 9.2.2.18a | | – | | +| MIMO Activation Indicator | O | | 9.2.1.119 | In multicarrier mode of operation the IE is for the serving HS-DSCH cell | – | | +| HS-DSCH MAC-d PDU Size Format | O | | 9.2.1.31ID | If not present, "Indexed MAC-d PDU Size" shall be assumed. | – | | +| Sixtyfour QAM Usage Allowed Indicator | O | | 9.2.2.74A | For the serving HS-DSCH cell | – | | +| UE with enhanced HS-SCCH support indicator | O | | NULL | UE supports enhanced HS-SCCH functionality:
- UE supports different HS-SCCH in consecutive TTIs and
- in HS-SCCH-less operation mode the UE supports HS-SCCH orders | – | | +| Continuous Packet Connectivity HS-SCCH less Information | O | | 9.2.2.68 | | – | | +| UE Support Indicator Extension | O | | 9.2.2.117 | | YES | ignore | +| MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.164 | In multicarrier mode of operation the IE is for the serving HS-DSCH cell. | YES | ignore | +| Dual Stream MIMO with four transmit antennas Activation Indicator | O | | 9.2.2.167 | In multicarrier mode of operation the IE is for the serving HS-DSCH cell. | YES | ignore | +| Multiflow Information | O | | 9.2.2.170 | | YES | ignore | +| F-TPICH Information | O | | 9.2.2.160 | | YES | ignore | +| UL CLTD Information | O | | 9.2.2.152 | | YES | ignore | +| UL MIMO Information | O | | 9.2.2.177 | | YES | ignore | +| SixteenQAM UL Operation Indicator | O | | 9.2.2.88A | | YES | ignore | +| SixtyfourQAM UL Operation Indicator | O | | 9.2.2.88C | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|--------------------------------------------------------------| +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE | + +#### 9.2.2.113 Multi Cell Capability Info + +This parameter defines the Multi Cell capability information for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Multi Cell Capability | M | | ENUMERATED
(Multi Cell Capable, Multi Cell non Capable) | | – | | +| Possible Secondary Serving Cell List | | $0..$ | | For secondary serving HS-DSCH cell. | – | | +| >Possible Secondary Serving Cell | M | | Local Cell ID
9.2.1.38 | Cells possible to serve in multicell adjacent and/or non-adjacent carrier operation TS 25.133 [22] (same or adjacent sector in the same Node B) | – | | +| >Multicell E-DCH Restriction | O | | BOOLEAN | TRUE means restricted
FALSE means not restricted.
If not included in AUDIT RESPONSE message or in RESOURCE STATUS INDICATION message when the cell becomes existing, it means not restricted. | YES | ignore | + +| Range bound | Explanation | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. See NOTE below. | +| NOTE: In this case, " maxNrOfHSDSCH-1 " represents the maximum number of possible secondary serving cells for a local cell. | | + +#### 9.2.2.114 Minimum Reduced E-DPDCH Gain Factor + +The minimum gain factor ( $\beta_{ed,k,reduced,min}$ ) defined in TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|----------------------------------------------------------------------------|-----------------------| +| Minimum Reduced E-DPDCH Gain Factor | | | ENUMERATED
(8/15, 11/15, 15/15, 21/15, 30/15, 42/15, 60/15, 84/15, ...) | | + +#### 9.2.2.115 IMB Parameters + +The *IMB Parameters* IE contains specific parameters needed for 3.84Mcps MBSFN IMB operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|----------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Sub-frame number | M | | INTEGER (0..4,...) | | +| Last DL Channelisation Code Number | O | | DL Channelisation Code Number 9.2.2.14 | In case of IMB using multiple channelization codes this IE indicates the last one as defined TS 25.331 [18]. | + +#### 9.2.2.116 Common E-DCH HS-DPCCH Capability + +This parameter defines the HS-DPCCH capability for a Common E-DCH capable Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-------------------------------------------------------------------------------|-----------------------| +| Common E-DCH HS-DPCCH Capability | | | ENUMERATED (HS-DPCCH non-Capable, ACK-NACK Capable, ACK-NACK and CQI Capable) | | + +#### 9.2.2.117 UE Support Indicator Extension + +The *UE Support Indicator Extension* IE is used to indicate the support level in the UE for optional HSDPA functions to the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE support indicator extension | | | BIT STRING (SIZE(32)) |

Each bit indicates whether the UE supports a particular HSDPA function or not. The value 1 of a bit indicates that the corresponding functionality is supported in the UE and value 0 indicates that the corresponding functionality is not supported in the UE. Each bit is defined as follows:
the first bit: Different HS-SCCH In Consecutive TTIs Support Indicator,
the second bit: HS-SCCH orders in HS-SCCH-less Operation Support Indicator,
the third bit: RRC Rel-9 (onwards) handling of DL secondary HS-DSCH (de)activation state Support Indicator,
the fourth bit: UE DTXDRX related HS-SCCH orders uniform behavior indicator,
the fifth bit: UE longer HARQ processing time for simultaneous Multiflow and MIMO operation.
the sixth bit: UE Blind HARQ Retransmissions Indicator for HSDPA.

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

| + +#### 9.2.2.118 MIMO Power Offset For S-CPICH Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|-------|-----------------------------------------------------------------------------|-----------------------| +| MIMO Power Offset For S-CPICH Capability | | | ENUMERATED (S-CPICH Power Offset Capable, S-CPICH Power Offset Not Capable) | | + +#### 9.2.2.119 Power Offset For Secondary CPICH for MIMO + +The *Power Offset For Secondary CPICH for MIMO* IE indicates the the relative transmit power of the S-CPICH compared to the primary CPICH transmit power, when S-CPICH is used as a phase reference for a second transmit antenna in MIMO mode TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------| +| Power Offset For Secondary CPICH for MIMO | | | INTEGER(-6 .. 0) | Offset in dB | + +#### 9.2.2.120 MIMO Pilot Configuration Extension + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|--------------------------------------| +| CHOICE Pilot Configuration | M | | | | +| >Primary and Secondary CPICH | | | | | +| >> Power Offset For Secondary CPICH for MIMO | M | | 9.2.2.119 | | +| >Normal and Diversity Primary CPICH | | | NULL | This IE is not used in this release. | + +#### 9.2.2.121 TX Diversity on DL Control Channels by MIMO UE Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| TX Diversity on DL Control Channels by MIMO UE Capability | | | ENUMERATED (DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable, DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Not Capable) | | + +#### 9.2.2.122 Single Stream MIMO Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-------------------------------------------------------------------------|-----------------------| +| Single Stream MIMO Capability | | | ENUMERATED (Single Stream MIMO Capable, Single Stream MIMO Non-Capable) | | + +#### 9.2.2.123 Single Stream MIMO Activation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|-----------------------| +| Single Stream MIMO Activation Indicator | M | | NULL | | + +#### 9.2.2.124 Single Stream MIMO Mode Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------------------|-----------------------| +| Single Stream MIMO Mode Indicator | | | ENUMERATED (Activate, Deactivate) | | + +#### 9.2.2.125 Dual Band Capability Info + +This parameter defines the Dual Band capability information for a Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|----------------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Dual Band Capability | M | | ENUMERATED (Dual Band Capable, Dual Band non Capable) | For HS-DSCH | - | | +| Possible Secondary Serving Cell List | | 0.. | | For secondary serving HS-DSCH cell.] | - | | +| >Possible Secondary Serving Cell | M | | Local Cell ID 9.2.1.38 | Cells possible to serve in multicell HS-DSCH Dual Band operation TS 25.133 [22] (same sector) | - | | +| >Multicell E-DCH Restriction | O | | BOOLEAN | TRUE means restricted for E-DCH Dual Band operation
FALSE means not restricted.
If not included in AUDIT RESPONSE message or in RESOURCE STATUS INDICATION message when the cell becomes existing, it means not restricted. | YES | ignore | +| Dual Band E-DCH Capability | O | | ENUMERATED (Dual Band E-DCH Capable, Dual Band E-DCH non Capable) | For E-DCH | YES | ignore | + +| Range bound | Explanation | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| maxNrOfHSDSCH-1 | Maximum number of Secondary Serving HS-DSCH cells for one UE. See NOTE below. | +| NOTE: In this case, " maxNrOfHSDSCH-1 " represents the maximum number of possible secondary serving cells for a local cell. | | + +9.2.2.126 Void + +9.2.2.127 HS-DSCH MAC-ehs Format + +Void. + +9.2.2.128 Activation Information + +The *Activation Information* IE defines the local activation state of the secondary uplink frequency of the UE in Dual Cell E-DCH operation, or the change request of activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|--------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Activation Information | | 1.. | For secondary E-DCH. Max 1 in this 3GPP release. | | +| >Uu Activation State | M | | ENUMERATED (Activated, De-activated, ..., Change Request) | The activation state of the secondary UL frequency, or change of the activation state of the secondary UL frequency when E-DCH decoupling is configured. | + +| Range Bound | Explanation | +|---------------|--------------------------------------------------------------| +| maxNrOfEDCH-1 | Maximum number of uplink frequencies -1 for E-DCH for one UE | + +9.2.2.129 Cell Capability Container + +The *Cell Capability Container* IE indicates the cell capability by setting the corresponding bit in the BIT String. + +The cell capability of multi-cell related functions may depend on that the cell is multi-cell capable (adjacent carrier and/or non-adjacent carrier) and/or Dual Band capable. Such capability indicators in this *Cell Capability Container* IE shall be ignored by the CRNC if the local cell does not have the required cell capability: "Multi Cell Capable" as indicated with *Multi Cell Capability Info* IE and/or "Dual Band Capable" as indicated with *Dual Band Capability Info* IE. Capability indicators that depend on multi-cell (adjacent carrier) capability are indicated in the table below with /Adjacent-carrier/. Capability indicators that depend on multi-cell (non-adjacent carrier) capability are indicated in the table below with /Adjacent-carrier/ if the capability bit "Non-contiguous HSDPA operation Capability" is set. Capability indicators that depend on Dual Band capability are indicated in the table below with /Dual-band/. Capability indicators that depend on that the local cell has one or both of the capabilities multi-cell (adjacent carrier) and Dual Band are indicated in the table below with /Multi-cell/. Capability indicators that depend on that the local cell has one or both of the capabilities multi-cell (non-adjacent carrier) and Dual Band are indicated in the table below with /Multi-cell/ if the capability bit "Non-contiguous HSDPA operation Capability" is set. Cell Capability for the marked capabilities indicate capability regardless of the supported multi-cell type in a multicell configuration for the local cell: supported multi-cell type is - both serving HS-DSCH and secondary serving HS-DSCH, - secondary serving HS-DSCH or - serving HS-DSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Capability Container | | | BIT STRING (SIZE(128)) |

Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.

The first bit: Cell Specific Tx Diversity Handling For Multi Cell Operation Capability /Multi-cell/.

The second bit: Multi Cell and MIMO Capability/Adjacent-carrier/.

The third bit: Multi Cell and Single Stream MIMO Capability/Adjacent-carrier/.

The fourth bit: Multi Cell E-DCH Capability/Adjacent-carrier/.

This bit shall be ignored by the CRNC if the fifth bit: Separate Iub Transport Bearer Capability = "0" and the sixth bit: E-DCH UL Flow Multiplexing Capability = "0"

The fifth bit: Separate Iub Transport Bearer Capability/Adjacent-carrier/.

This bit shall be ignored by the CRNC if the fourth bit: Multi Cell E-DCH Capability = "0"

The sixth bit: E-DCH UL Flow Multiplexing Capability/Adjacent-carrier/.

This bit shall be ignored by the CRNC if the fourth bit: Multi Cell E-DCH Capability = "0"

The seventh to eleventh bit Maximum No of HSDPA Frequencies capability/Multi-cell/.

This capability is coded as the binary representation of the maximum number of HSDPA frequencies, with the seventh bit as the MSB and the eleventh bit as the LSB. Hexadecimal digit 0 means no support for 3 or more HSDPA. Hexadecimal digits 1 and 2 are reserved.

The twelfth bit: Dual Band and MIMO Capability/Dual Band/.

The thirteenth bit: HSDPA 3 or more Carrier and MIMO Single Band Capability/Adjacent-carrier/

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

The fourteenth bit: HSDPA 3 or more Carrier and MIMO Dual Band Capability/Dual Band/.

The fifteenth bit: Dual band and Single Stream MIMO Capability/Dual Band/.

The sixteenth bit: HSDPA 3 or more Carrier and Single Stream MIMO Single Band Capability/Adjacent-Carrier/.

The seventeenth bit: HSDPA 3 or more Carrier and Single Stream MIMO Dual Band Capability/Dual Band/.

The eighteenth bit: Frequency Specific Compressed Mode Capability/Multi-Cell/.

The nineteenth bit: UL CLTD capability.

The twentieth bit: Non-contiguous HSDPA operation Capability.

The twenty-first bit to twenty-third bit: Supported MIMO transmit antennas (N). This capability is coded as the representation of the supported MIMO transmit antennas with the twenty-first bit as the MSB and the twenty-third bit as the LSB. Hexadecimal digit 0 means no support for more than 2 MIMO transmit antennas. Hexadecimal digit 2 means MIMO with four transmit antennas support. Hexadecimal digit 1 is reserved. Undefined values are considered as spare.

The twenty-fourth bit: MIMO with N transmit antennas Capability Adjacent-carrier.

The twenty-fifth bit: MIMO with N transmit antennas Capability Dual Band/Dual Band.

The twenty-sixth bit: Multi Cell and MIMO with N transmit antennas Capability Adjacent-carrier.

The twenty-seventh bit: Multi Cell and MIMO with N transmit antennas Capability Dual Band/Dual Band.

The twenty-eighth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Adjacent-carrier.

The twenty-ninth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Dual Band/Dual Band.

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

This 3GPP release supports MIMO with four transmit antennas for up to 4 carriers.

The thirtieth bit:
Intra-Node B Multiflow.
The thirty-first bit:
Inter-Node B Multiflow.
The thirty-second to thirty fourth bits: Supported Multiflow configuration, where value 0 indicates support for one frequency two cells, value 1 indicates support for two frequencies three cells, value 2 indicates support for two frequencies four cells. Value 3 indicates support for three frequencies four cells. Values 4-7 are reserved for future use,
The thirty-fifth bit: Multiflow and MIMO.
The thirty-sixth bit: Cell Specific Tx Diversity Handling For Multiflow Cell Operation
The thirty-seventh bit: Multiflow and single stream MIMO.

The thirty eighth bit: UL SixtyfourQAM capability.
The thirty ninth bit: UL MIMO capability.
The fortieth bit: UL MIMO and UL SixteenQAM capability.
The forty-first bit: UL MIMO and UL SixtyfourQAM capability.

The forty-second bit: NodeB Triggered HS-DPCCH Transmission Capability.
The forty-third bit: 2ms and 10ms TTI Concurrent Deployment Capability.
The forty-fourth bit: Further Enhanced UE DRX Capability.
The forty-fifth bit: Per HARQ Activation and Deactivation Capability.
The forty-sixth bit: TTI alignment Capability.
The forty-seventh bit: Common E-RGCH Capability.
The forty-eighth bit: Fallback to R99 PRACH Capability.
The forty-ninth bit: E-DCH decoupling operation Capability.
The fiftieth bit: Basic DCH Enhancements Capability [52].

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

The fifty-first bit: Full DCH Enhancements Capability [52].

The fifty-second bit: BCH mapped on SCCPCH Capability.

The fifty-third bit: Radio Links without DPCH/F-DPCH operation Capability.

The fifty-fourth bit: UL DPCCH2 operation Capability.

The fifty-fifth bit: feEUL TTI switching Node B Autonomous Capability.

The fifty-sixth bit: feEUL TTI switching RNC notify Capability.

The fifty-seventh bit: downlink TPC enhancements Capability.

The fifty-eighth bit: NAICS offloading Capability.

The fifty-ninth bit: Multi Cell E-DCH with DPDCH Capability.

The sixtieth bit: Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI Capability.

The sixty-first bit: Dual Cell E-DCH operation enhancements with different TTI Capability.

The sixty-second bit: HS-SCCH DRX capability.

The sixty-third bit: Simplified HS-SCCH type 1 operation capability.

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

| +|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 9.2.2.130 Multicell E-DCH Transport Bearer Mode + +This parameter indicates the Multicell E-DCH Transport Bearer Mode. For *Multicell E-DCH Transport Bearer Mode* = "Separate Iub Transport Bearer Mode" the Mac-d flows from each carrier uses different Iub transport bearers, for *Multicell E-DCH Transport Bearer Mode* = "UL Flow Multiplexing Mode" the Mac-d flows received on the different carriers in the Node B is multiplexed on one Iub transport bearer (per Mac-d flow). The CRNC should apply the stored cell capabilities for the cell on primary UL frequency for the capabilities related to Multicell E-DCH Transport Bearer Mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-------------------------------------------------------------------------------|-----------------------| +| Multicell E-DCH Transport Bearer Mode | | | ENUMERATED
(Separate lub Transport Bearer Mode, UL Flow Multiplexing Mode) | | + +#### 9.2.2.131 Additional E-DCH FDD Setup Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| UL DPCH Information | | 1 | | | – | | +| >UL Scrambling Code | M | | 9.2.2.59 | | – | | +| >UL SIR Target | M | | UL SIR
9.2.1.67A | | – | | +| Additional E-DCH RL Specific Information To Setup | M | | 9.2.2.132 | | – | | +| Additional E-DCH FDD Information | O | | 9.2.2.137 | | – | | +| F-DPCH Information | | 1 | | | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Limited Power Increase | M | | 9.2.2.18A | | – | | +| >Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| Multicell E-DCH Information | O | | 9.2.2.140 | | YES | ignore | + +#### 9.2.2.132 Additional E-DCH RL Specific Information To Setup + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|---------------------|--------------------------------------|-----------------------|-------------|----------------------| +| E-DCH Additional RL Specific Information | | 1.. | | | – | | +| >E-DCH Additional RL ID | M | | RL ID
9.2.1.53 | | – | | +| >C-ID | O | | 9.2.1.9 | | – | | +| >First RLS Indicator | M | | 9.2.2.16A | | – | | +| >Propagation Delay | O | | 9.2.2.35 | | – | | +| >DL Code Information | M | | FDD DL Code Information
9.2.2.14A | | – | | +| >Initial DL Transmission Power | M | | DL Power
9.2.1.21 | | – | | +| >Maximum DL Power | M | | DL Power
9.2.1.21 | | – | | +| >Minimum DL Power | M | | DL Power
9.2.1.21 | | – | | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | – | | +| >E-RNTI | O | | 9.2.1.75 | | – | | +| >Multicell E-DCH RL Specific Information | O | | 9.2.2.142 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | + +| Range bound | Explanation | +|----------------|----------------------------------------| +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.133 Additional E-DCH RL Specific Information To Add + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|---------------------|-----------------------------------|-----------------------|-------------|----------------------| +| E-DCH Additional RL Specific Information To Add | | 1.. | | | – | | +| >E-DCH Additional RL ID | M | | RL ID 9.2.1.53 | | – | | +| >C-ID | M | | 9.2.1.9 | | – | | +| >DL Code Information | M | | FDD DL Code Information 9.2.2.14A | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | – | | +| >Multicell E-DCH RL Specific Information | O | | 9.2.2.142 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | + +| Range bound | Explanation | +|----------------|----------------------------------------| +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.134 Additional E-DCH RL Specific Information To Modify + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|---------------------|-----------------------------------|-----------------------|-------------|----------------------| +| E-DCH Additional RL Specific Information To Modify | | 1.. | | | – | | +| >E-DCH Additional RL ID | M | | RL ID 9.2.1.53 | | – | | +| >DL Code Information | O | | FDD DL Code Information 9.2.2.14A | | – | | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | | – | | +| >F-DPCH Slot Format | O | | 9.2.2.93 | | – | | +| >Multicell E-DCH RL Specific Information | O | | 9.2.2.142 | | YES | ignore | +| >TPC slot position | O | | 9.2.2.217 | | YES | ignore | + +| Range bound | Explanation | +|----------------|----------------------------------------| +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.135 Additional E-DCH FDD Information Response + +The *Additional E-DCH FDD Information Response* IE provides information for new E-DCH radio links on the secondary UL frequency. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------------------|----------|-----------------------------------------|---------------------------------------------------|-----------------------| +| E-DCH Additional RL Specific Information Response | | 0..<maxno ofEDCHRLs> | | | +| >E-DCH Additional RL ID | M | | RL ID
9.2.1.53 | | +| >Received Total Wide Band Power | M | | 9.2.2.39A | | +| >DL Power Balancing Activation Indicator | O | | 9.2.2.12C | | +| >RL Set ID | M | | 9.2.2.39 | | +| >E-DCH RL Set ID | M | | RL Set ID
9.2.2.39 | | +| >E-DCH FDD DL Control Channel Information | M | | 9.2.2.13Dc | | +| Additiona E-DCH MAC-d Flow Specific Information Response | | 0..<maxNr OfEDCHMACdFlows> | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | + +| Range bound | Explanation | +|-----------------------------|----------------------------------------| +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | + +#### 9.2.2.136 Additional E-DCH Configuration Change Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|-------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UL DPCH Information | | 0..1 | | | – | | +| >UL Scrambling Code | O | | 9.2.2.59 | | – | | +| >UL SIR Target | O | | UL SIR
9.2.1.67A | | – | | +| Additional E-DCH RL
Specific Information To Add | O | | 9.2.2.133 | Used when the E-DCH RL to add does not exist in the current Node B Communication Context on the secondary UL frequency. | – | | +| Additional E-DCH RL
Specific Information To Modify | O | | 9.2.2.134 | Used when an existing E-DCH RL on the secondary UL frequency is modified. | – | | +| Additional E-DCH FDD
Information To Modify | O | | Additional E-DCH FDD
Information
9.2.2.137 | Used to modify the current additional E-DCH configuration with or without a new RL added in this procedure | – | | +| F-DPCH Information | | 0..1 | | | – | | +| >FDD TPC DL Step Size | M | | 9.2.2.16 | | – | | +| >Limited Power Increase | M | | 9.2.2.18A | | – | | +| >Inner Loop DL PC Status | M | | 9.2.2.18B | | – | | +| Multicell E-DCH Information | O | | 9.2.2.140 | | YES | ignore | + +#### 9.2.2.137 Additional E-DCH FDD Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|----------|----------------------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Additional E-DCH MAC-d Flows Specific Information | | 0..<maxNrOfEDCHMACdFlows> | | | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP | – | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI 9.2.2.13Dn | | – | | +| E-DCH Maximum Bitrate | O | | 9.2.2.13T | | – | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | – | | +| E-DCH Minimum Set E-TFCI | O | | INTEGER (0..127) | For the concept of "E-DCH Minimum Set of TFCs" see TS 25.321 [32] and TS 25.331 [18] | – | | +| DTX Information2 | | 0..1 | | | | | +| >UE DTX Cycle 1 | M | | ENUMERATED (v1, v4, v5, v8, v10, v16, v20,...) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | +| >UE DTX Cycle 2 | M | | ENUMERATED (v4, v5, v8, v10, v16, v20, v32, v40, v64, v80, v128, v160, v256, v320, v512, v640, v1024, v1280,...) | Units of subframes, refer to TS 25.331 [16]. | YES | ignore | +| >Inactivity Threshold for UE DTX Cycle 2 | M | | ENUMERATED (v1, v4, v8, v16, v32, v64, v128, v256,...) | Units of E-DCH TTIs, refer to TS 25.331 [16]. | YES | ignore | +| Implicit Grant handling | O | | ENUMERATED (true) | The presence of this information element indicates that Implicit Grant handling is configured on the secondary uplink frequency | YES | ignore | +| Minimum TEBS threshold | O | | ENUMERATED (v2, v4, v8, v16, v32, v64, v128, v256, v512, v1024, v2K, v4K, v8K, v16K, v32K, v64K, v128K, v256K, | In bytes And N Kbytes = N*1024 bytes. Twelve spare values are needed, refer to TS 25.331 [16]. | YES | ignore | + +| | | | | | | | +|----------------------------------------------------------|---|--|-----------------------|--|-----|--------| +| | | | v512K,
v1024K,...) | | | | +| Dual Cell E-DCH
Operation Enhancements
Information | O | | 9.2.2.219 | | YES | reject | + +| Range bound | Explanation | +|-----------------------------|--------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | + +#### 9.2.2.138 Additional E-DCH FDD Update Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------------|----------|-------------------------------------------------|---------------------------------------------------------|-----------------------| +| HARQ Process Allocation For
2ms Scheduled Transmission
Grant | O | | HARQ Process
Allocation for
2ms TTI
9.2.2.13Dn | | +| Additional E-DCH DL Control
Channel Change Information | | 0..<max
noofED
CHRLs
> | | | +| >E-DCH Additional RL ID | M | | RL ID
9.2.1.53 | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------| +| maxnoofEDCHRLs | Maximum number of E-DCH RLs for one UE | + +#### 9.2.2.139 E-RNTI List + +The *E-RNTI List* IE provides the list of E-RNTIs which can be allocated by CRNC. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|--------------------------------------|-----------------------|-----------------------| +| E-RNTI List | | 1..<maxnoo
fERNTIs> | | | +| >E-RNTI | M | | 9.2.1.75 | | + +| Range bound | Explanation | +|----------------------|------------------------------------------------------------| +| MaxnoofERNTIs | Maximum number of ERNTIs that can be allocated by the CRNC | + +#### 9.2.2.140 Multicell E-DCH Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|-----------------------------------------------|-------------------------------------------------------------------------------------| +| DL Power Balancing
Information | O | | 9.2.2.12B | | +| Minimum Reduced E-DPDCH
Gain Factor | O | | 9.2.2.114 | | +| Secondary UL Frequency
Activation State | O | | ENUMERATED
(Activated,
Deactivated,...) | Activation state signalled to Node B at
setup of RL on secondary UL
frequency | + +#### 9.2.2.141 Additional Modified E-DCH FDD Information Response + +The *Additional Modified E-DCH FDD Information Response* IE provides information for RLs on the secondary UL frequency that has been modified and existed in the Node B Communication Context configuration before the reconfiguration procedure. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------------------|----------|-----------------------------------------|---------------------------------------------------|-----------------------| +| E-DCH Additional Modified RL Specific Information Response | | 0..<maxno ofEDCHRLs> | | | +| >E-DCH Additional RL ID | M | | RL ID
9.2.1.53 | | +| >DL Power Balancing Updated Indicator | O | | 9.2.2.12D | | +| >E-DCH FDD DL Control Channel Information | O | | 9.2.2.13Dc | | +| Additional E-DCH MAC-d Flow Specific Information Response | | 0..<maxNr OfEDCHMACdFlows> | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | +| HARQ Process Allocation For 2ms Scheduled Transmission Grant | O | | HARQ Process Allocation for 2ms TTI
9.2.2.13Dn | | + +| Range bound | Explanation | +|-----------------------------|----------------------------------------| +| maxnoOfEDCHRLs | Maximum number of E-DCH RLs for one UE | +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | + +#### 9.2.2.142 Multicell E-DCH RL Specific Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|-------------------------------------|----------------------------| +| Extended Propagation Delay | O | | 9.2.2.35A | | +| Primary CPICH Usage For Channel Estimation | O | | 9.2.2.33A | | +| Secondary CPICH Information | O | | Common Physical Channel ID 9.2.1.13 | | +| Secondary CPICH Information Change | O | | 9.2.2.43A | | +| E-AGCH Power Offset | O | | 9.2.2.13Id | | +| E-RGCH Power Offset | O | | 9.2.2.13Ie | | +| E-HICH Power Offset | O | | 9.2.2.13If | | +| DL Reference Power | O | | DL power
9.2.1.21 | Power on DPCH or on F-DPCH | +| E-DCH DL Control Channel Grant | O | | NULL | | + +#### 9.2.2.143 Precoding Weight Set Restriction + +This parameter defines the preferred precoding weight set restriction configuration as defined in TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|------------------------------------------|-----------------------| +| Precoding Weight Set Restriction | | | ENUMERATED
(Preferred, Not Preferred) | | + +#### 9.2.2.144 Non-Serving RL Preconfiguration Setup + +The *Non-Serving RL Preconfiguration Setup* IE indicates that the Node B may preconfigure E-DCH DL Code Information configured for new non-serving RL for Enhanced Service Cell Change and contains the information for the location of new serving RL after the Enhanced Serving Cell Change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE new Serving RL | M | | | | – | | +| > New Serving RL in the Node B | | | NULL | | – | | +| > New Serving RL Not in the Node B | | | NULL | | – | | +| > New Serving RL in the Node B or New Serving RL Not in the Node B | | | NULL | | – | | +| Additional E-DCH Non-Serving RL Preconfiguration Setup | O | | NULL | | YES | ignore | +| F-TPICH Information | O | | 9.2.2.160 | | YES | ignore | + +#### 9.2.2.145 Non-Serving RL Preconfiguration Info + +The *Non-Serving RL Preconfiguration Info* IE provides information for the new non-serving RL after Enhanced Serving Cell Change. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------------------------------|----------|---------------------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| New non-serving RL E-DCH FDD DL Control Channel Information A | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for non-serving RL in Serving E-DCH RLS | – | | +| New non-serving RL E-DCH FDD DL Control Channel Information B | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for non-serving RL in non serving E-DCH RLS in case serving RL is in the Node | – | | +| New non-serving RL E-DCH FDD DL Control Channel Information C | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for non-serving RL in case serving RL is not in the Node B | – | | +| Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information | | 0..<maxNrOfEDCH-1> | | E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. | EACH | ignore | +| >New non-serving RL E-DCH FDD DL Control Channel Information A | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for Additional non-serving RL in Serving E-DCH RLS | – | | +| >New non-serving RL E-DCH FDD DL Control Channel Information B | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for Additional non-serving RL in non serving E-DCH RLS in case Additional serving RL is in the Node B | – | | +| >New non-serving RL E-DCH FDD DL Control Channel Information C | O | | 9.2.2.13Dc E-DCH FDD DL Control Channel Information | E-DCH FDD DL Control Channel Information for Additional non-serving RL in case Additional serving RL is not in the Node B | – | | + +#### 9.2.2.146 Void + +#### 9.2.2.147 Usefulness of Battery Optimization + +This IE, when present, indicates whether the device can benefit from UTRAN-based battery consumption optimisation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|---------------------------------------------------|-----------------------| +| Usefulness of Battery Optimization | | | Enumerated (
CanBenefit,
CannotBenefit
) | | + +#### 9.2.2.148 Common HS-DSCH RNTI List + +The *Common HS-DSCH RNTI List* IE provides the list of Common HS-DSCH RNTIs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|----------------------------------|---------------------------|-----------------------| +| Common HS-DSCH RNTI List | | 1..ofCommon
HRNTIs> | | | +| >Common HS-DSCH RNTI | M | | HS-DSCH RNTI
9.2.1.31J | | + +| Range bound | Explanation | +|----------------------------|---------------------------------------------------| +| maxnoofCommonHRNTIs | Maximum number of Common HS-DSCH RNTIs for a cell | + +#### 9.2.2.149 Puncturing Handling in First Rate Matching Stage + +This parameter provides the puncturing handling information in first rate matching stage. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Puncturing Handling in First Rate Matching Stage | M | | BOOLEAN | True = No Puncturing in first rate matching stage
False = Normal handling
If not included: when HS-DSCH is setup, or when HS-DSCH is modified and the puncturing handling is not configured in the Node B Communication Context, value False applies. | + +#### 9.2.2.150 Support of Dynamic DTXDRX Related HS-SCCH Order + +The *Support of dynamic DTXDRX related HS-SCCH order* IE is to indicate if Node B supports the DRX/DTX related HS-SCCH order for CPC non-uniform UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|--------------------------------------------|-----------------------| +| Support of dynamic DTXDRX related HS-SCCH order | | | ENUMERATED
(Supported,Not
Supported) | | + +#### 9.2.2.151 UL CLTD Information Reconf + +The *UL CLTD Information Reconf* IE is used for the reconfiguration of the UL CLTD operation in a UE context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of UL CLTD | | 1 | | | +| >Setup | | | | Used when UL CLTD is not configured in the current UE Context | +| >>UL CLTD Information | M | | 9.2.2.152 | | +| >Configuration Change | | | | Used when the existing UL CLTD configuration in the current UE context is modified | +| >>UL CLTD information To Modify | M | | 9.2.2.153 | | +| >Removal | | | | Used when the existing UL CLTD configuration in the current UE context is removed. | +| >>UL CLTD information Removal | M | | 9.2.2.154 | | + +#### 9.2.2.152 UL CLTD Information + +The *UL CLTD Information* IE defines the parameters used for UL CLTD operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|------------------|-------|-----------------------|-----------------------| +| S-DPCCH Power Offset Information | M | | 9.2.2.158 | | +| C-ID | C-DCHorMultiflow | | 9.2.1.9 | | +| UL CLTD Activation Information | O | | 9.2.2.159 | | + +| Condition | Explanation | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DCHorMultiflow | The IE shall be present if there is no serving E-DCH RL or HS-DSCH RL configuration in the concerned Node B Communication Context. If the Multiflow operation is configured, then this IE may indicate the Multiflow assisting serving cell. | + +#### 9.2.2.153 UL CLTD Information To Modify + +The *UL CLTD information To Modify* IE is used for modification of UL CLTD information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|-----------------------| +| S-DPCCH Power Offset Information | O | | 9.2.2.158 | | +| UL CLTD Activation Information | O | | 9.2.2.159 | | + +#### 9.2.2.154 UL CLTD Information Removal + +The *UL CLTD Information Removal* IE is used for removal of UL CLTD information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|--------------------------|-----------------------| +| UL CLTD Information Removal | | | ENUMERATED (Remove, ...) | | + +#### 9.2.2.155 UL CLTD State Update Information + +The *UL CLTD State Update Information* IE provides information for the activation state of UL CLTD of the UE to be updated. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------------------------|-----------------------------------------| +| UL CLTD State Update Information | | | ENUMERATED (Activate, De-activate, ...) | The suggested UL CLTD activation state. | + +#### 9.2.2.156 F-TPICH Slot Format + +Indicates the slot format used in F-TPICH in DL, accordingly to ref. TS 25.211 [7]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| F-TPICH Slot Format | | | INTEGER (0..9,...) | | + +#### 9.2.2.157 F-TPICH Offset + +The F-TPICH Offset is defined as the time offset towards the Primary CCPCH in the cell. The offset is a multiple of 256 chips. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|--------------------------------------------------------------------| +| F-TPICH Offset | | | INTEGER (0..149) | Range: 0..38144 chips
Step: 256 chips
See ref. TS 25.211 [7] | + +#### 9.2.2.158 S-DPCCH Power Offset Information + +The S-DPCCH Power Offset is used to calculate the S-DPCCH gain factor, $\beta_{sc}$ , as defined in TS 25.214 [9], whereas $\beta_{sc}$ is related to the power difference between DPCCH and S-DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| S-DPCCH Power Offset Information | | | INTEGER (0..6,...) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.4. | + +#### 9.2.2.159 UL CLTD Activation Information + +The *UL CLTD Activation Information* IE defines the activation state of the UE in UL CLTD operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-------------------------------------------|--------------------------------------| +| >UL CLTD Activation State | M | | ENUMERATED (Activated, De-activated, ...) | The activation state of the UL CLTD. | + +#### 9.2.2.160 F-TPICH Information + +The *F-TPICH Information* IE defines the parameters used for F-TPICH configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------------------------------|-----------------------| +| F-TPICH Slot Format | M | | 9.2.2.156 | | +| F-TPICH Offset | M | | 9.2.2.157 | | +| F-TPICH Channelisation Code Number | M | | FDD DL
Channelisation Code Number 9.2.2.14 | | + +#### 9.2.2.161 F-TPICH Information To Modify + +The *F-TPICH Information To Modify* IE is used for modification of F-TPICH configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------------------------------|-----------------------| +| F-TPICH Slot Format | O | | 9.2.2.156 | | +| F-TPICH Offset | O | | 9.2.2.157 | | +| F-TPICH Channelisation Code Number | O | | FDD DL
Channelisation Code Number 9.2.2.14 | | + +#### 9.2.2.162 F-TPICH Information Removal + +The *F-TPICH Information Removal* IE is used for removal of F-TPICH information of a RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------------|-----------------------| +| F-TPICH Information Removal | | | ENUMERATED
(Remove, ...) | | + +#### 9.2.2.163 F-TPICH Information Reconf + +The *F-TPICH Information Reconf* IE is used for the reconfiguration of the UL CLTD operation of a RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of F-TPICH Information | | 1 | | | +| >Setup | | | | Used when F-TPICH is not configured in the current RL | +| >>F-TPICH Information | M | | 9.2.2.160 | | +| >Configuration Change | | | | Used when the existing UL F-TPICH configuration in the current RL is modified | +| >>F-TPICH Information To Modify | M | | 9.2.2.161 | | +| >Removal | | | | Used when the existing UL F-TPICH in the current RL is removed. | +| >>F-TPICH information Removal | M | | 9.2.2.162 | | + +#### 9.2.2.164 MIMO with four transmit antennas Activation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| MIMO with four transmit antennas Activation Indicator | M | | NULL | | + +#### 9.2.2.165 MIMO with four transmit antennas Pilot Configuration + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------|----------|-----------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Pilot Configuration | M | | | | +| >Primary and Secondary CPICH | | | | | +| >>Secondary CPICH | | 1.. | | The 3 rd and the 4 th S-CICH should have the same power offset;
The 3 rd and the 4 th D-CPICH should have the same power offset. | +| >>>Associated Secondary CPICH | M | | Common Physical Channel ID 9.2.1.13 | | +| >>>Power Offset For Associated Secondary CPICH | O | | INTEGER (-12..0) | | +| >>>Associated D-CPICH | O | | Common Physical Channel ID 9.2.1.13 | | +| >>>Power Offset For Associated D-CPICH | O | | INTEGER (-12..0) | | +| >Normal and Diversity Primary CPICH | | | NULL | | + +| Range Bound | Explanation | +|---------------|-------------------------------------------------------------------| +| maxSCPICHCell | Maximum number of Secondary CPICHs that can be defined in a Cell. | + +#### 9.2.2.166 MIMO with four transmit antennas Mode Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|-----------------------------------|-----------------------| +| MIMO with four transmit antennas Mode Indicator | | | ENUMERATED (Activate, Deactivate) | | + +#### 9.2.2.167 Dual Stream MIMO with four transmit antennas Activation Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Four Stream MIMO with four transmit antennas Activation Indicator | M | | NULL | | + +#### 9.2.2.168 Dual Stream MIMO with four transmit antennas Mode Indicator + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------------|----------|-------|-----------------------------------|-----------------------| +| Dual Stream MIMO with four transmit antennas Mode Indicator | | | ENUMERATED (Activate, Deactivate) | | + +#### 9.2.2.169 Multiflow Reconfiguration + +The *Multiflow Reconfiguration IE* is used setup, reconfigure, and stop Multiflow operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|------------------------------------------------------------| +| CHOICE Setup, or Change, or Stop | | 1 | | | +| >Setup | | | | Used when Multiflow is not configured. | +| >>Multiflow Information | M | | 9.2.2.170 | | +| >Change | | | | Used when Multiflow configuration changes. | +| >>Multiflow Information To Modify | M | | 9.2.2.171 | | +| >Stop | | | | Used when the existing Multiflow configuration is removed. | +| >>Multiflow Stop | M | | 9.2.2.172 | | + +#### 9.2.2.170 Multiflow Information + +The *Multiflow Information* IE defines parameters to setup Multiflow operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|----------------------------------------|------------------------------------------------------------------------------------------|-------------|----------------------| +| Total number of HS-DSCH cells | M | | INTEGER (2..32,...) | Total number of HS-DSCH cells configured for Multiflow. | - | | +| Role | M | | Multiflow Role 9.2.2.173 | | - | | +| MIMO | M | | Multiflow MIMO 9.2.2.174 | | - | | +| Timing | O | | Multiflow Timing 9.2.2.175 | In the inter-Node B Multiflow case, if present, this IE provides the timing information. | - | | +| Max number of HS-SCCH sets per Node B | O | | INTEGER (1..16,...) | Maximum number of HS-SCCH that can be allocated per Node B. | - | | +| Assisting repetition factors | O | | Multiflow Repetition Factors 9.2.2.193 | Additional HS-DPCCH repetition factors | YES | ignore | + +#### 9.2.2.171 Multiflow Information To Modify + +The *Multiflow Information To Modify* IE defines parameters to reconfigure Multiflow operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|----------------------------------------|------------------------------------------------------------------------------------------|-------------|----------------------| +| Total number of HS-DSCH cells | O | | INTEGER (2..32,...) | Total number of HS-DSCH cells configured for Multiflow. | - | | +| Role | O | | Multiflow Role 9.2.2.173 | | - | | +| MIMO | O | | Multiflow MIMO 9.2.2.174 | | - | | +| Timing | O | | Multiflow Timing 9.2.2.175 | In the inter-Node B Multiflow case, if present, this IE provides the timing information. | - | | +| Max number of HS-SCCH sets per Node B | O | | INTEGER (1..16,...) | Maximum number of HS-SCCH that can be allocated per Node B. | - | | +| Assisting repetition factors | O | | Multiflow Repetition Factors 9.2.2.193 | Additional HS-DPCCH repetition factors | YES | ignore | + +#### 9.2.2.172 Multiflow Stop + +The *Multiflow Stop* IE is used when the Multiflow operation is terminated. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|------------------------|-----------------------| +| Multiflow Stop | | | ENUMERATED (Stop, ...) | | + +#### 9.2.2.173 Multiflow Role + +The *Multiflow Role* IE is used to specify primary or assisting Multiflow operation mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| Multiflow Role | | | ENUMERATED (Primary, Assisting, ...) | This IE indicates whether Node B is configured with the primary serving HS-DSCH cell or assisting serving HS-DSCH cell. | + +#### 9.2.2.174 Multiflow MIMO + +The *Multiflow MIMO* IE is used to specify whether MIMO is configured for at least one of the cells. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|---------------------------|-----------------------| +| Multiflow MIMO | | | ENUMERATED (ON, OFF, ...) | | + +#### 9.2.2.175 Multiflow Timing + +The *Multiflow Timing* IE is used to specify timing information for the Multiflow operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Time Reference, or Non-time Reference | | 1 | | | +| > Time Reference | | | NULL | This indicates that the cell in the Multiflow time-reference cell (refer to TS 25.211, sub-clause 7.7.1). | +| > Non-time Reference | | | INTEGER (0..30,...) | Unit: chip
Range: 0..7680 chips
Step: 256 chips

This IE indicates that the cell is a non-time reference cell. The value corresponds to the smallest TTX_diff value of the time reference cell (refer to TS25.211, sub-clause 7.7.1) and is used to calculate the HS-DPCCH to UL DPCCH timing difference in the non-time reference cell (refer to TS 25.211, sub-clause 7.7.2). | + +#### 9.2.2.176 UL MIMO Reconfiguration + +The *UL MIMO Reconfiguration* IE is used for the reconfiguration of the UL MIMO operation in a UE context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of UL MIMO | | 1 | | | +| > Setup | | | | Used when UL MIMO is not configured in the current UE Context. | +| >>UL MIMO Information | M | | 9.2.2.177 | | +| > Configuration Change | | | | Used when the existing UL MIMO configuration in the current UE context is modified. | +| >>UL MIMO information To Modify | M | | 9.2.2.178 | | +| > Removal | | | | Used when the existing UL MIMO configuration in the current UE context is removed. | +| >>UL MIMO Removal | M | | 9.2.2.179 | | + +#### 9.2.2.177 UL MIMO Information + +The *UL MIMO Information* IE defines the parameters used for UL MIMO operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------| +| E-ROCH Power Offset | O | | 9.2.2.181 | | +| S-E-DPCCH Power Offset | M | | 9.2.2.182 | | +| Inter-stream Interference Compensation Index | M | | 9.2.2.183 | | +| Minimum E-TFCI for rank 2 transmissions | M | | INTEGER (0..127) | For the concept of "Minimum TB size for rank 2 transmissions" see TS 25.321 [32] and TS 25.331 [18]. | + +#### 9.2.2.178 UL MIMO Information To Modify + +The *UL MIMO information To Modify* IE is used for modification of UL MIMO information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------| +| E-ROCH Power Offset | O | | 9.2.2.181 | | +| S-E-DPCCH Power Offset | O | | 9.2.2.182 | According to $\Delta_{S-E-DPCCH}$ mapping in ref. TS 25.213 [9] subclause 4.2.1.5. | +| Inter-stream Interference Compensation Index | O | | 9.2.2.183 | | +| Minimum E-TFCI for rank 2 transmissions | O | | INTEGER (0..127) | For the concept of "Minimum TB size for rank 2 transmissions" see TS 25.321 [32] and TS 25.331 [18]. | + +#### 9.2.2.179 UL MIMO Removal + +The *UL MIMO Removal* IE is used for removal of UL MIMO information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|--------------------------|-----------------------| +| UL MIMO Removal | | | ENUMERATED (Remove, ...) | | + +#### 9.2.2.180 UL MIMO DL Control Channel Information + +UL MIMO DL Control Information contains the Node B allocation of the UL MIMO specific DL control channels. Secondary Transport Block E-HICH Signature Sequence is used to acknowledge the secondary transport block transmitted in the uplink, and it uses the same channelization code as the E-HICH used for non-MIMO and primary transport block acknowledgements. E-ROCH Channelization Code is selected from the pool allocated for E-AGCH codes. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------|----------|-------|--------------------------------------------|--------------------------------------------------------------------------------------------------| +| E-ROCH Channelization Code | O | | FDD DL Channelisation Code Number 9.2.2.14 | Should be present for the serving E-DCH cell only | +| Secondary Transport Block E-RNTI | O | | E-RNTI 9.2.1.75 | E-ROCH S-E-RNTI as defined in ref. TS 25.212 [8] subclause 4.10A | +| Secondary Transport Block E-HICH Signature Sequence | O | | INTEGER (0..maxnoofSigSeqE-RGHICH - 1) | One Secondary TB E-HICH signature sequence should be present at least for the serving E-DCH cell | +| Secondary Transport Block E-HICH Release Indicator | O | | 9.2.2.184 | | + +| Range Bound | Explanation | +|------------------------------|----------------------------------------------------------| +| maxnoofSigSeqE-RGHICH | Maximum number of Signature Sequences for E-RGCH/E-HICH. | + +#### 9.2.2.181 E-ROCH Power Offset + +The *E-ROCH Power Offset* IE indicates the power offset relative to the pilot bits. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|------------------------------------------------------| +| E-ROCH Power Offset | | | INTEGER (0...255,...) | Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB | + +#### 9.2.2.182 S-E-DPCCH Power Offset + +The S-E-DPCCH Power Offset is used to calculate the S-E-DPCCH gain factor $\beta_{sec}$ as defined in TS 25.214 [10], whereas $\beta_{sec}$ is related to the power difference between DPCCH and S-E-DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------| +| S-E-DPCCH Power Offset | | | INTEGER (0..17,...) | According to $\Delta_{S-E-DPCCH}$ mapping in ref. TS 25.213 [9] subclause 4.2.1.5. | + +#### 9.2.2.183 Inter-stream Interference Compensation Index + +The *Inter-stream Interference Compensation Index* IE indicates an offset that a UE applies while performing the E-TFC selection for the primary stream. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------| +| Inter-stream Interference Compensation Index | | | INTEGER (0..15,...) | According to $\Delta_{ISI}$ mapping in ref. TS 25.213 [9] subclause 4.2.1.3. | + +#### 9.2.2.184 Secondary Transport Block E-HICH Release Indicator + +Indicates the release of the Uplink MIMO transmission's Secondary Transport Block E-HICH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|--------------------------------------------------------|-----------------------| +| Secondary Transport Block E-HICH Release Indicator | | | ENUMERATED (Secondary Transport Block E-HICH released) | | + +#### 9.2.2.185 Further Enhanced UE DRX Information + +The *Further Enhanced UE DRX Information* IE provides information for configuring the UE in Cell\_FACH state to discontinuously receive HS-DSCH with the second DRX cycle. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-DSCH second DRX cycle FACH | M | | ENUMERATED
(4, 8, 16, 32, 64, 128, 256, 512) | Determines the length of the DRX Cycle during second DRX operation, in frames. | +| CHOICE DRX level | M | | | This IE indicates whether both the 1 st and the 2 nd DRX cycle are used (2-level DRX) or only the 2 nd DRX cycle is used (1-level DRX). | +| >1- level DRX | | | | | +| >> HS-DSCH second Rx burst FACH | O | | ENUMERATED
(1,2) | Determines the period within the second DRX Cycle that the UE continuously receives HS-DSCH, in frames. | +| >>T32y | O | | ENUMERATED
(0.5,1,2,4) | Determines the time the UE waits until initiating the Second DRX operation, in seconds. | +| >2- level DRX | | | | | +| >>T32x | O | | ENUMERATED
(20,40,60,80) | Determines the time the UE waits until initiating the first DRX operation, in ms. | +| >>HS-DSCH first Rx burst FACH | O | | ENUMERATED
(0.4,0.8) | Determines the period within the first DRX Cycle that the UE continuously receives HS-DSCH, in frames. | +| >>HS-DSCH first DRX cycle FACH | O | | ENUMERATED
(2,4,8,16,32,64) | Determines the length of the DRX Cycle during first DRX operation, in frames. | +| >>HS-DSCH second Rx burst FACH | O | | ENUMERATED
(1,2) | Determines the period within the second DRX Cycle that the UE continuously receives HS-DSCH, in frames. | +| >>T32y | O | | ENUMERATED
(0.5,1,2,4) | Determines the time the UE waits until initiating second DRX operation, in seconds. | + +#### 9.2.2.186 Common E-DCH Preamble Control Information extension list + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------|----------|---------------------------------------|---------------------------------------------------------------|-----------------------| +| Common E-DCH Preamble Control Information extension list | | 1 to <
maxnoofPRACHEUL
> | | | +| >Common E-DCH Preamble Control Information extension | M | | Common E-DCH Preamble Control Information extension 9.2.2.187 | | + +| Range bound | Explanation | +|------------------------|-----------------------------------------------------------------------------------| +| maxnoofPRACHEUL | Maximum number of Common E-DCH Preamble Control Information extension for a cell. | + +#### 9.2.2.187 Common E-DCH Preamble Control Information extension + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|------------------------------|-----------------------| +| Common Physical Channel ID | M | | 9.2.1.13 | | +| Scrambling Code Number | M | | 9.2.2.42 | | +| Common E-DCH Preamble Signature | M | | Preamble Signatures 9.2.2.31 | | +| Preamble Threshold | M | | 9.2.2.32 | | +| Common E-DCH AICH Information | O | | 9.2.2.188 | | + +#### 9.2.2.188 Common E-DCH AICH Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID | M | | 9.2.1.13 | | +| AICH Transmission Timing | M | | 9.2.2.1 | | +| FDD DL Channelisation Code Number | M | | 9.2.2.14 | | +| AICH Power | M | | 9.2.2.D | | +| STTD Indicator | M | | 9.2.2.48 | | + +#### 9.2.2.189 Common E-RGCH Info + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------------| +| E-RGCH Channelisation Code | M | | FDD DL Channelisation Code Number 9.2.2.14 | | +| E-RGCH Signature Sequence | M | | INTEGER (0..maxnoofSigSeq E-RGHICH - 1) | | +| Minimum Serving Grant | O | | INTEGER (0..37,38) | (0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]. Index 38 is not allowed. | + +| Range bound | Explanation | +|------------------------------|----------------------------------------------------------| +| maxnoofSigSeqE-RGHICH | Maximum number of Signature Sequences for E-RGCH/E-HICH. | + +#### 9.2.2.190 Common E-DCH HS-DPCCH Information for Concurrent TTI + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|-------------|-------|-----------------------|-----------------------| +| ACK-NACK Repetition Factor | M | | 9.2.2.a | | +| ACK Power Offset | M | | 9.2.2.b | | +| NACK Power Offset | M | | 9.2.2.23a | | +| Common E-DCH CQI Information | O | | | | +| >CQI Feedback Cycle k | M | | 9.2.2.21B | | +| >CQI Repetition Factor | C-CQICyclek | | 9.2.2.4Cb | | +| >CQI Power Offset | M | | 9.2.2.4Ca | | +| >Measurement Power Offset | M | | 9.2.2.21C | | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------------------| +| CQICyclek | The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0. | + +#### 9.2.2.191 Common E-DCH system info parameters for Concurrent TTI + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-------|-------------------------------------------------|-----------------------| +| Maximum Set of E-DPDCHs | M | | 9.2.2.20C | | +| Puncture Limit | M | | 9.2.1.50 | | +| E-TFCS Information | M | | 9.2.2.13Dh | | +| E-DPCCH Power Offset | O | | 9.2.2.13Dj | | +| E-RGCH 2-Index-Step Threshold | O | | 9.2.2.13lg | | +| E-RGCH 3-Index-Step Threshold | O | | 9.2.2.13lh | | +| E-DCH Reference Power Offset | O | | 9.2.2.13Y | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | +| Maximum E-DCH resource allocation for CCCH Extension | O | | ENUMERATED (8, 12, 16, 20, 24, 32, 40, 80, ...) | Interms of TTIs | +| Maximum period for collision resolution phase | O | | INTEGER (8..24,...) | Interms of TTIs | +| Maximum TB Sizes | O | | 9.2.2.106 | | +| Common E-DCH Additional Transmission Back Off | O | | INTEGER (0..15,...) | | +| Common E-DCH E-AGCH Channelisation Code Number | O | | FDD DL Channelisation Code Number 9.2.2.14 | | +| Common E-DCH HS-DPCCH Information for Concurrent TTI | O | | 9.2.2.190 | | + +#### 9.2.2.192 Precoder weight set restriction + +This parameter defines the preferred precoding weight set restriction configuration as defined in TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Precoder weight set restriction | | | BIT STRING (SIZE(64)) |

Each bit indicates whether a code in the Codebook is supported or not. The value 1 of a bit indicates that the corresponding code in the codebook is supported and value 0 indicates that the corresponding code in the Codebook is not supported.

Note: The Bit mapping is as defined in TS 25.331 [18]. If the bit has no corresponding code in the Codebook, it is set to 0.

| + +#### 9.2.2.193 Multiflow Repetition Factors + +The *Multiflow Repetition Factors* IE is used to indicate repetition factors for the HS-DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Assisting CQI Repetition Factor | O | | CQI Repetition Factor 9.2.2.4Cb | In the intra-NodeB Multiflow case, if present, this IE provides the Node B with the number of repetitions of the assisting CQI information in the HS-DPCCH [10]. | +| Assisting ACK-NACK Repetition Factor | O | | ACK-NACK Repetition Factor 9.2.2.a | In the intra-Node B Multiflow case, if present, this IE provides the Node B with the number of repetitions of the assisting ACK-NACK information in the HS-DPCCH [10]. | + +#### 9.2.2.194 E-DCH Decoupling Indication + +The *E-DCH Decoupling Indication* IE indicates the role of cell will be changed to Serving E-DCH cell only or Serving HS-DSCH cell only. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-DCH Decoupling Indication | M | | ENUMERATED (Serving E-DCH cell only, Serving HS-DSCH cell only, ...) | This IE indicates whether the related cell in Node B is configured to Serving E-DCH cell only or Serving HS-DSCH cell only for E-DCH decoupling operation. | + +#### 9.2.2.195 DCH Enhancements Information Reconf + +The *DCH Enhancements Information Reconf* IE is used for the reconfiguration of the DCH Enhancements [52] operation in a UE context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of DCH Enhancements | | | | | +| >Setup | | | | Used when DCH Enhancements are not configured in the current UE Context | +| >>DCH Enhancements Information | M | | 9.2.2.196 | | +| >Configuration Change | | | | Used when the existing DCH Enhancements configuration in the current UE context is modified | +| >>DCH Enhancements Information to Modify | M | | 9.2.2.197 | | +| >Removal | | | | Used when the existing DCH Enhancements configuration in the current UE context is removed. | +| >>DCH Enhancements information Removal | M | | 9.2.2.198 | | + +#### 9.2.2.196 DCH Enhancements Information + +The *DCH Enhancements Information* IE defines the parameters used for DCH Enhancements operation [52]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-----------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| PO-SRB | M | | Power Offset
9.2.2.29 | Power boost to be applied to the DL DPDCH under the conditions defined in [10]. | +| DL FET Mode | M | | ENUMERATED
(basic,
full,
...) | Indicates the DCH Enhancements configuration mode, as defined in TS 25.300. | +| DL DCH Concatenation | C-FET | 1.. | | If present, this IE provides the list of DL Transport Channels that are subject to concatenation in the physical layer [8]. | +| >DCH ID | M | | 9.2.1.20 | | + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------| +| FET | The IE shall be present if the DL FET Mode IE is set to "full". | + +| Range Bound | Explanation | +|-------------------------------|--------------------------------------| +| maxNrOfConcatenatedDCH | Maximum number of concatenated DCHs. | + +#### 9.2.2.197 DCH Enhancements Information to Modify + +The *DCH Enhancements Information to Modify* IE is used for modification of DCH Enhancements information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-----------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| PO-SRB | O | | Power Offset
9.2.2.29 | Power boost to be applied to the DL DPDCH under the conditions defined in [10]. | +| DL FET Mode | O | | ENUMERATED
(basic,
full,
...) | Indicates the DCH Enhancements configuration mode, as defined in TS 25.300 [52]. | +| DL DCH Concatenation | C-FET | 1.. | | If present, this IE provides the list of DL Transport Channels that are subject to concatenation in the physical layer [8]. | +| >DCH ID | M | | 9.2.1.20 | | + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------| +| FET | The IE shall be present if the DL FET Mode IE is present and set to "full". | + +| Range Bound | Explanation | +|-------------------------------|--------------------------------------| +| maxNrOfConcatenatedDCH | Maximum number of concatenated DCHs. | + +#### 9.2.2.198 DCH Enhancements Information Removal + +The *DCH Enhancements Information Removal* IE is used for removal of DCH Enhancements information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------------|-----------------------| +| DCH Enhancements Information Removal | | | ENUMERATED
(Remove, ...) | | + +#### 9.2.2.199 Gain Factors 10ms Mode + +The *Gain Factors 10ms Mode* IE is used to configure the gain factors in 10ms Transmission Mode [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------| +| CHOICE Gain Factors 10ms | | | | | +| > Signalled Gain Factors 10ms | | | | | +| >>Gain Factor 10ms $\beta_c$ | M | | INTEGER (0..15) | For UL DPCCH in FDD with 10ms Transmission Mode; mapping in accordance to TS 25.213 [9] | +| >>Gain Factor 10ms $\beta_D$ | M | | INTEGER (0..15) | For UL DPCCH in FDD with 10ms Transmission Mode; mapping in accordance to TS 25.213 [9] | +| >>Reference TFC nr 10ms | O | | INTEGER (0..3) | If this TFC is a reference TFC, this IE indicates the reference number. | +| > Computed Gain Factors 10ms | | | | | +| >>Reference TFC nr 10ms | M | | INTEGER (0..3) | Indicates the reference TFC to be used to calculate the gain factors for this TFC. | + +#### 9.2.2.200 Extended E-DPCCH Power Offset + +The E-DPCCH Power Offset is used to calculate the E-DPCCH gain factor $\beta_{ec}$ as defined in TS 25.214 [10], whereas $\beta_{ec}$ is related to the power difference between DPCCH and E-DPCCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|---------------------------------------------------------------| +| E-DPCCH Power Offset | | | INTEGER (9..15) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3. | + +#### 9.2.2.201 Radio Links without DPCH/F-DPCH Indication + +The *Radio Links without DPCH/F-DPCH Indication* IE indicates whether to start operation with Radio Links without DPCH/F-DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|--------------------------|-----------------------|-------------------------------------------------------------------------------------------| +| Radio Links without DPCH/F-DPCH Information | | 1..< maxNrOfRLs > | | | +| >RL ID | M | | 9.2.1.53 | | +| >Radio Links without DPCH/F-DPCH Operation indicator | M | | ENUMERATED (true) | This IE indicates that the E-DCH radio link is setup without transmission of DPCH/F-DPCH. | + +| Range bound | Explanation | +|-------------------|-------------------------------------------| +| maxNrOfRLs | Maximum number of Radio Links for one UE. | + +#### 9.2.2.202 UL DPCCH2 Reconfiguration + +The *UL DPCCH2 Reconfiguration* IE is used for the reconfiguration of the UL DPCCH2 operation in a UE context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of UL DPCCH2 | | 1 | | | +| >Setup | | | | Used when UL DPCCH2 is not configured in the current UE Context | +| >>UL DPCCH2 Information | M | | 9.2.2.203 | | +| >Configuration Change | | | | Used when the existing UL DPCCH2 configuration in the current UE context is modified | +| >>UL DPCCH2 Information To Modify | M | | 9.2.2.204 | | +| >Removal | | | | Used when the existing UL DPCCH2 configuration in the current UE context is removed. | +| >>UL DPCCH2 information Removal | M | | 9.2.2.205 | | + +#### 9.2.2.203 UL DPCCH2 Information + +The *UL DPCCH2 Information* IE defines the parameters used for UL DPCCH2 operation according to ref TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------|------------------------------------| +| F-DPCH info | | 1 | | Used when UL DPCCH2 is configured. | +| >F-DPCH slot format | M | | 9.2.2.93 | | +| >FDD DL Channelisation Code Number | M | | 9.2.2.14 | | +| >Extended E-DPCCH Power Offset | O | | 9.2.2.200 | | + +#### 9.2.2.204 UL DPCCH2 Information To Modify + +The *UL DPCCH2 Information To Modify* IE is used for modification of UL DPCCH2 information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------|------------------------------------| +| F-DPCH info To Modify | | 0..1 | | Used when UL DPCCH2 is configured. | +| >F-DPCH slot format | O | | 9.2.2.93 | | +| >FDD DL Channelisation Code Number | O | | 9.2.2.14 | | +| >Extended E-DPCCH Power Offset | O | | 9.2.2.200 | | + +#### 9.2.2.205 UL DPCCH2 Information Removal + +The *UL DPCCH2 Information Removal* IE is used for removal of UL DPCCH2 information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|--------------------------|-----------------------| +| UL DPCCH2 Information Removal | | | ENUMERATED (Remove, ...) | | + +#### 9.2.2.206 CQI Feedback Cycle2 k + +The *CQI Feedback Cycle2 k* IE provides the duration of the CQI feedback cycle. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CQI Feedback Cycle2 k | | | ENUMERATED
(v0, v8, v10, v16,
v20, v32, v40, v64,
v80, v160,...) | Unit ms
The allowed values for this IE depend on the configured CQI Repetition Factor and the HS-DSCH configuration as defined in TS 25.331 [16].

CQI Feedback Cycle2 k value shall be an integer multiple of the CQI Feedback Cycle k | + +#### 9.2.2.207 UE Measurement Forwarding + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement ID | M | | 9.2.1.42 | When reporting the “UPH Filtering Value”:
Measurement ID 1 indicates Primary UL frequency;
Measurement ID 2 indicates the Secondary UL frequency. | +| UE Measurement Value | M | | 9.2.2.208 | | + +#### 9.2.2.208 UE Measurement Value + +The UE Measurement Value contains the value to be forwarded. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------------------------| +| CHOICE Dedicated Measurement Value | M | | | | +| >UPH Filtering Value | | | | | +| >>UPH Filtering Value | M | | INTEGER (0..32) | According to mapping in TS 25.321 [32]. | + +#### 9.2.2.209 TTI Update Indication + +The TTI Update Indication indicates that the TTI switching has been triggered and confirmed by the UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE TTI Update Indication | M | | | | +| >TTI Update CFN | | | | | +| >>CFN | M | | CFN 9.2.1.7 | | +| >TTI Update Ind | | | NULL | | + +#### 9.2.2.210 Activation Delay + +The *Activation Delay* IE is the same value as the RNC sends to the UE for the TTI switching by the HS-SCCH Order. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|------------------------------------------|------------------------------------------| +| Activation Delay | | | Enumerated (v0, v1, v2, v3, v4, v5, ...) | In radio frames. Refer to TS 25.331 [18] | + +#### 9.2.2.211 Fast TTI switching Mode Supported + +The *Fast TTI switching Mode Supported* indicates which Fast TTI switching mode is supported by the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------------|-----------------------| +| Fast TTI Switching Support Mode | | | ENUMERATED (Mode 1, Mode 2) | | + +#### 9.2.2.212 Fast TTI switching Mode Requested Synchronized + +The *Fast TTI switching Mode Requested Synchronized* indicates which Mode is requested. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Fast TTI switching Mode Synchronized | M | | | | +| >Mode 1 | | | NULL | | +| >Mode 2 | | | | | +| >>CFN | M | | CFN 9.2.1.7 | | + +#### 9.2.2.213 Fast TTI switching Mode Requested UnSynchronized + +The *Fast TTI switching Mode Requested UnSynchronized* indicates which Mode is requested. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Fast TTI switching Mode UnSynchronized | M | | | | +| >Mode 1 | | | | | +| >>Activation Delay | M | | 9.2.2.210 | | +| >Mode 2 | | | | | +| >>CFN | M | | CFN 9.2.1.7 | | + +#### 9.2.2.214 Downlink TPC enhancements Information + +The *Downlink TPC enhancements Information* IE defines the parameters used for Downlink TPC enhancements operation according to ref TS 25.214 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-------------------------------|-----------------------| +| Decimation factor for primary frequency | O | | ENUMERATED (3 slots, 5 slots) | | +| Decimation factor for secondary frequency | O | | ENUMERATED (3 slots, 5 slots) | | + +#### 9.2.2.215 Downlink TPC enhancements Reconf + +The *Downlink TPC enhancements Reconf* IE is used for the reconfiguration of the Downlink TPC enhancements operation in a UE context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------| +| CHOICE Setup, Configuration Change or Removal of Downlink TPC enhancements | | 1 | | | +| >Setup | | | | Used when Downlink TPC enhancements is not configured in the current UE Context. | +| >>Downlink TPC enhancements Information | M | | 9.2.2.214 | | +| >Configuration Change | | | | Used when the existing Downlink TPC enhancements configuration in the current UE context is modified. | +| >>Downlink TPC enhancements Information To Modify | M | | 9.2.2.214 | | +| >Removal | | | | Used when the existing Downlink TPC enhancements configuration in the current UE context is removed. | +| >>Downlink TPC enhancements information Removal | M | | 9.2.2.216 | | + +#### 9.2.2.216 Downlink TPC enhancements Information Removal + +The *Downlink TPC enhancements Information Removal* IE is used for removal of Downlink TPC enhancements information in a UE Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------|----------|-------|--------------------------|-----------------------| +| Downlink TPC enhancements Information Removal | | | ENUMERATED (Remove, ...) | | + +#### 9.2.2.217 TPC slot position + +The *TPC slot position* IE is used to configure TPC slot position for power control Algorithm 3. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Slot position | O | | INTEGER (0..4) | | + +#### 9.2.2.218 E-RNTI Set + +The *E-RNTI Set* IE provides a set of E-RNTIs which can be allocated by CRNC. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|--------------------------------| +| Starting E-RNTI | M | | 9.2.1.75 | First E-RNTI value in the set. | +| Ending E-RNTI | M | | 9.2.1.75 | Last E-RNTI value in the set. | + +#### 9.2.2.219 Dual Cell E-DCH Operation Enhancements Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------------------------|-------------------------------------------------|--------------------------------------------------------------| +| E-TTI | M | | ENUMERATED (2ms, 10ms) | | +| E-DCH Reference E-TFCI Information | | 0.. | | | +| > E-DCH Reference E-TFCI | O | | INTEGER (0..127) | | +| > E-DCH Reference E-TFCI Power Offset | O | | INTEGER (0..31) | According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3 | +| E-DCH E-TFCI Boost Information | O | | E-TFCI Boost Information 9.2.2.88B | | +| E-DCH E-DPCCH Power Offset | O | | E-DPCCH Power Offset 9.2.2.13Dj | | +| E-DCH E-TFCI Table Index | O | | INTEGER (0..1, ..., 2..7) | | +| E-DCH Power Offset for Scheduling Info | O | | E-DCH Power Offset for Scheduling Info 9.2.1.85 | | +| E-DCH Maximum Set of E-DPDCHs | O | | Maximum Set of E-DPDCHs 9.2.2.20C | | + +#### 9.2.2.220 HS-SCCH DRX Information + +The *HS-SCCH DRX Information* IE provides information for configuring the UE in Cell\_FACH state to discontinuously receive HS-SCCH order and HS-DSCH. + +NOTE: Only for FDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-------------------------------------|--------------------------------------------------------------------------------------------------| +| T333 | M | | ENUMERATED (100, 200, 400, 800,...) | Determines the time the UE waits until initiating DRX operation, in ms. | +| HS-SCCH DRX cycle FACH | M | | ENUMERATED (4, 8, 16, 32, 64,...) | Determines the length of the DRX Cycle during HS-SCCH DRX operation, in frames. | +| HS-SCCH Rx burst FACH | M | | ENUMERATED (0.4, 0.8,...) | Determines the period within the DRX Cycle that the UE continuously receives HS-SCCH, in frames. | + +### 9.2.3 TDD specific Parameters + +#### 9.2.3.1 Block STTD Indicator + +Void. + +#### 9.2.3.2 Burst Type + +Void. + +#### 9.2.3.3 CCTrCH ID + +The CCTrCH ID for dedicated and shared channels identifies unambiguously an uplink or downlink CCTrCH inside a Radio Link. For S-CCPCH, it identifies unambiguously a downlink CCTrCH within a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| CCTrCH ID | | | INTEGER (0..15) | | + +#### 9.2.3.4 Cell Parameter ID + +The Cell Parameter ID identifies unambiguously the [3.84 Mcps TDD and 7.68Mcps TDD - Code Groups, Scrambling Codes, Midambles and Toffset] [1.28 Mcps TDD - SYNC-DL and SYNC-UL sequences, the scrambling codes and the midamble codes] (see ref. TS 25.223 [20]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Cell Parameter ID | | | INTEGER (0..127,...) | | + +#### 9.2.3.4A Constant Value + +The Constant Value is the power margin used by a UE to set the proper uplink power for a DCH, USCH, or a RACH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-------------------------------------------------| +| Constant Value | | | INTEGER (-10..10,...) | Unit: dB
Range: -10 .. +10 dB
Step: 1 dB. | + +#### 9.2.3.4B DL Timeslot ISCP + +The DL Timeslot ISCP is the measured interference in a downlink timeslot at the UE, see ref. TS 25.225 [5]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------|---------------------------------------------| +| DL Timeslot ISCP | | | INTEGER (0..91) | According to mapping in ref. TS 25.225 [5]. | + +#### 9.2.3.4C DCH TDD Information + +The *DCH TDD Information* IE provides information for DCHs to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|-----------|------------------|-----------------------|--------------------------------------|-------------|----------------------| +| DCH TDD Information | | 1.. | | | – | | +| >Payload CRC Presence Indicator | M | | 9.2.1.49 | | – | | +| >UL FP Mode | M | | 9.2.1.66 | | – | | +| >ToAWS | M | | 9.2.1.61 | | – | | +| >ToAWE | M | | 9.2.1.60 | | – | | +| >DCH Specific Info | | 1.. | | | – | | +| >>DCH ID | M | | 9.2.1.20 | | – | | +| >>CCTrCH ID | M | | 9.2.3.3 | UL CCTrCH in which the DCH is mapped | – | | +| >>CCTrCH ID | M | | 9.2.3.3 | DL CCTrCH in which the DCH is mapped | – | | +| >>Transport Format Set | M | | 9.2.1.59 | For UL | – | | +| >>Transport Format Set | M | | 9.2.1.59 | For DL | – | | +| >>Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >>Frame Handling Priority | M | | 9.2.1.30 | | – | | +| >>QE-Selector | C-CoorDCH | | 9.2.1.50A | | – | | +| >>Unidirectional DCH Indicator | O | | 9.2.1.68 | | YES | reject | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| CoorDCH | The IE shall be present if this DCH is part of a set of coordinated DCHs (number of instances of the DCH Specific Info IE is greater than 1). | + +| Range Bound | Explanation | +|--------------------|-----------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for one UE | + +#### 9.2.3.4D DCHs TDD To Modify + +The *DCHs TDD To Modify* IE provides information for DCHs to be modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|------------------|-----------------------|---------------------------------------|-------------|----------------------| +| DCHs TDD To Modify | | 1.. | | | – | | +| >UL FP Mode | O | | 9.2.1.66 | | – | | +| >ToAWS | O | | 9.2.1.61 | | – | | +| >ToAWE | O | | 9.2.1.60 | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >DCH Specific Info | | 1.. | | | – | | +| >>DCH ID | M | | 9.2.1.20 | | – | | +| >>CCTrCH ID | O | | 9.2.3.3 | UL CCTrCH in which the DCH is mapped. | – | | +| >>CCTrCH ID | O | | 9.2.3.3 | DL CCTrCH in which the DCH is mapped | – | | +| >>Transport Format Set | O | | 9.2.1.59 | For the UL. | – | | +| >>Transport Format Set | O | | 9.2.1.59 | For the DL. | – | | +| >>Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >>Frame Handling Priority | O | | 9.2.1.30 | | – | | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | + +| Range Bound | Explanation | +|-------------|-----------------------------------| +| maxNrOfDCHs | Maximum number of DCHs for one UE | + +#### 9.2.3.4E DL Timeslot Information + +The *DL Timeslot Information* IE provides information for DL Time slot to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------------------|-----------------------------------|-----------------------| +| DL Timeslot Information | | 1.. | | | +| >Time Slot | M | | 9.2.3.23 | | +| >Midamble Shift And Burst Type | M | | 9.2.3.7 | | +| >TFCI Presence | M | | 9.2.1.57 | | +| >DL Code Information | M | | TDD DL Code Information 9.2.3.19B | | + +| Range Bound | Explanation | +|--------------|------------------------------------------------------| +| maxNrOfDLTSs | Maximum number of Downlink time slots per Radio Link | + +#### 9.2.3.4F DL Time Slot ISCP Info + +The *DL Time Slot ISCP Info* IE provides information for DL Interference level for each time slot within the Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------------------|-----------------------|-----------------------| +| DL Time Slot ISCP Info | | 1.. | | | +| >Time Slot | M | | 9.2.3.23 | | +| >DL Timeslot ISCP | M | | 9.2.3.4B | | + +| Range Bound | Explanation | +|---------------------|------------------------------------------------------------------------| +| maxNrOfDLTSs | Maximum number of Downlink time slots per Radio Link for 3.84Mcps TDD. | + +#### 9.2.3.4G Cell Sync Burst Code + +The *Cell Sync Burst Code* IE indicates which Code is used for a given Cell Sync Burst. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|-----------------------| +| Cell Sync Burst Code | | | INTEGER (0..7,...) | | + +#### 9.2.3.4H Cell Sync Burst Code Shift + +The *Cell Sync Burst Code Shift* IE indicates the number of code shifts used for a given Cell Sync Burst. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| Cell Sync Burst Code Shift | | | INTEGER (0..7) | | + +#### 9.2.3.4I CSB Measurement ID + +The *CSB Measurement ID* IE uniquely identifies any cell synchronisation burst measurement per Node B Control Port. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| CSB Measurement ID | | | INTEGER (0..65535) | | + +#### 9.2.3.4J Cell Sync Burst Repetition Period + +The *Cell Sync Burst Repetition Period* IE represents the number of consecutive Radio Frames after which the cell synchronisation burst transmission/measurement is repeated. This means that if the Time Slot *K* is assigned to the cell synchronisation burst transmission/measurements in the Radio Frame *J*, the cell synchronisation burst transmission/measurement is also in all the Radio Frames *J+n\*Repetition Period*. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|-----------------------| +| Cell Sync Burst Repetition Period | | | INTEGER (0..4095) | | + +#### 9.2.3.4K Cell Sync Burst SIR + +Indicates the Signal to Interference Ratio of the cell synchronisation burst measurement according definition in TS 25.225 [5]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|----------------------------------------| +| Cell Sync Burst SIR | | | INTEGER (0..31) | According to mapping in TS 25.123 [23] | + +#### 9.2.3.4L Cell Sync Burst Timing + +The *Cell Sync Burst Timing* IE defines the time of start (defined by the first detected path in time) of the cell synchronisation burst of a neighbouring cell see TS 25.225 [5] for 3.84Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|--------------------------|----------------------------------------| +| CHOICE Phase | | | | According to mapping in TS 25.123 [23] | +| > Initial Phase | | | | | +| >>Cell Synch Burst Timing Value | M | | INTEGER (0..1048575,...) | | +| > Steady State Phase | | | | | +| >>Cell Synch Burst Timing Value | M | | INTEGER (0..255,...) | | + +#### 9.2.3.4La Cell Sync Burst Timing LCR + +The *Cell Sync Burst Timing LCR* IE defines the time of start (defined by the first detected path in time) of the cell synchronisation burst of a neighbouring cell see TS 25.225 [5] for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-------------------------|----------------------------------------| +| CHOICE Phase | | | | According to mapping in TS 25.123 [23] | +| > Initial Phase | | | | | +| >>Cell Synch Burst Timing Value | M | | INTEGER (0..524287,...) | | +| > Steady State Phase | | | | | +| >>Cell Synch Burst Timing Value | M | | INTEGER (0..127,...) | | + +#### 9.2.3.4M Cell Sync Burst Timing Threshold + +The *Cell Sync Burst Timing Threshold* IE defines the threshold that shall trigger a CELL SYNCHRONISATION REPORT message. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|-----------------------------------------------------------| +| Cell Sync Burst Timing Threshold | | | INTEGER (0..254) | Unit: chip
Range: 0 .. 31.75 chips
Step: 0.125 chip | + +#### 9.2.3.4N CSB Transmission ID + +The *CSB Transmission ID* IE uniquely identifies any cell synchronisation burst transmission per Node B Control Port. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| CSB Transmission ID | | | INTEGER (0..65535) | | + +#### 9.2.3.4O DL Timeslot Information LCR + +The *DL Timeslot Information LCR* IE provides information for DL Time slot to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|----------------------|---------------------------------------|-------------------------------|-------------|----------------------| +| DL Timeslot Information LCR | | 1.. | | | – | | +| >Time Slot LCR | M | | 9.2.3.24A | | – | | +| >Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >TFCI Presence | M | | 9.2.1.57 | | – | | +| >DL Code Information | M | | TDD DL Code Information LCR 9.2.3.19C | | – | | +| >Initial DL Transmission Power | O | | DL Power 9.2.1.21 | Initial power on DPCH | YES | ignore | +| >Maximum DL Power | O | | DL Power 9.2.1.21 | Maximum allowed power on DPCH | YES | ignore | +| >Minimum DL Power | O | | DL Power 9.2.1.21 | Minimum allowed power on DPCH | YES | ignore | + +| Range Bound | Explanation | +|-----------------|------------------------------------------------------------------------| +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD. | + +#### 9.2.3.4P DL Time Slot ISCP Info LCR + +The *DL Time Slot ISCP Info LCR* IE provides information for DL Interference level for each time slot within the Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|----------------------|-----------------------|-----------------------| +| DL Time Slot ISCP Info LCR | | 1.. | | | +| >Time Slot LCR | M | | 9.2.3.24A | | +| >DL Timeslot ISCP | M | | 9.2.3.4B | | + +| Range Bound | Explanation | +|-----------------|------------------------------------------------------------------------| +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD. | + +#### 9.2.3.4Q UpPCH Position LCR + +The *UpPCH Position LCR* IE indicates the start point of the UpPCH channel, where the step size is 16chips, the maximum allowed value that can be utilised is $127 \times 16 = 2032$ chips, The reference point (UpPCH Position LCR =0) is the startpoint of the timeslot of UpPTS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| UpPCH Position LCR | | | INTEGER (0..127) | | + +#### 9.2.3.5 DPCH ID + +The DPCH ID identifies unambiguously a DPCH inside a Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| DPCH ID | | | INTEGER (0..239) | | + +#### 9.2.3.5a DSCH ID + +The DSCH ID uniquely identifies a DSCH within a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| DSCH ID | | | INTEGER (0..255) | | + +##### 9.2.3.5b DSCH Information Response + +The *DSCH Information Response* IE provides information for DSCHs that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------------------|-----------------------|-----------------------| +| DSCH Information Response | | 1.. | | | +| >DSCH ID | M | | 9.2.3.5a | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | + +| Range Bound | Explanation | +|--------------|------------------------------------| +| maxNrOfDSCHs | Maximum number of DSCHs for one UE | + +#### 9.2.3.5A DSCH TDD Information + +The *DSCH TDD Information* IE provides information for DSCHs to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------------------|-----------------------|------------------------------------------------------|-------------|----------------------| +| DSCH TDD Information | | 1.. | | | – | | +| >DSCH ID | M | | 9.2.3.5a | | – | | +| >CCTrCH ID | M | | 9.2.3.3 | DL CCTrCH in which the DSCH is mapped | – | | +| >Transport Format Set | M | | 9.2.1.59 | For DSCH | – | | +| >Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >Frame Handling Priority | M | | 9.2.1.30 | | – | | +| >ToAWS | M | | 9.2.1.61 | | – | | +| >ToAWE | M | | 9.2.1.60 | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | + +| Range Bound | Explanation | +|--------------|-----------------------------------| +| MaxNrOfDSCHs | Maximum number of DSCH for one UE | + +#### 9.2.3.5B DwPCH Power + +DwPCH Power is the power that shall be used for transmitting the DwPCH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the DwPCH, the DwPCH power is the linear sum of the power that is used for transmitting the DwPCH on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------|---------------------------------------------------| +| DwPCH Power | | | INTEGER (-150..+400,...) | Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB | + +#### 9.2.3.5C Frame Adjustment Value + +The *Frame Adjustment Value* IE represents the frame number correction within the initial synchronisation phase. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|----------------------------------------------------------------------| +| Frame Adjustment Value | | | INTEGER (0..4095) | $SFN_{new} = (SFN_{old} + \text{Frame Adjustment Value}) \bmod 4096$ | + +#### 9.2.3.5D IPDL TDD Parameters + +The *IPDL TDD Parameters* IE provides information about IPDL to be applied for 3.84Mcps TDD or 7.68Mcps TDD when activated. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|------------------------------------------------------|-----------------------| +| IP SpacingTDD | M | | ENUMERATED (30, 40, 50, 70, 100, ...) | See TS 25.224 [21] | +| IP Start | M | | INTEGER (0..4095) | See TS 25.224 [21] | +| IP Slot | M | | INTEGER (0..14) | See TS 25.224 [21] | +| IP PCCPCH | M | | ENUMERATED (Switch off 1 frame, Switch off 2 frames) | See TS 25.224 [21] | +| Burst Mode parameters | O | | 9.2.1.5A | | + +#### 9.2.3.5E Max FPACH Power + +Max FPACH Power is the maximum power that shall be used for transmitting the FPACH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the FPACH, the Max FPACH Power is maximum of the linear sum of the power that is allowed for transmitting the FPACH on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------|---------------------------------------------------| +| FPACH Power | | | INTEGER (-150..+400,...) | Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB | + +#### 9.2.3.5F HS-DSCH TDD Information + +The *HS-DSCH TDD Information* IE is used for initial addition of HS-DSCH information to a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH MAC-d Flows Information | M | | 9.2.1.31IA | | – | | +| UE Capabilities Information | | 1 | | | – | | +| >HS-DSCH Physical Layer Category | M | | 9.2.1.31Ia | | – | | +| >1.28 Mcps TDD Uplink Physical Channel Capability | O | | 9.2.3.5Gc | Applicable to 1.28Mcps TDD only | YES | ignore | +| >Number of Supported Carriers | O | | ENUMERATED (
One-one carrier, One-three carrier, Three-three carrier, One-six carrier, Three-six carrier, Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous) | Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier that UE can support at the same time, where "One-three carrier" means the number of supported carrier is one for the uplink,and three for the downlink.
One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers. | YES | reject | +| >Multi-carrier HS-DSCH Physical Layer Category | O | | HS-DSCH Physical Layer Category 9.2.1.31Ia | Applicable to 1.28Mcps TDD only | YES | ignore | +| >MIMO SF Mode Supported For HS-PDSCH dual stream | O | | Enumerated (SF1, SF1/SF16) | Applicable to 1.28Mcps TDD only | YES | ignore | +| >UE TS0 Capability LCR | O | | 9.2.3.110 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| >UE RF Band Capability LCR | C-
NofSupportedCarriers | | 9.2.3.125 | Applicable to 1.28Mcps TDD only. | YES | ignore | +| MAC-hs Reordering Buffer Size for RLC-UM | M | | 9.2.1.38Ab | | – | | +| TDD ACK NACK Power Offset | M | | 9.2.3.18F | | – | | +| HS-SICH SIR Target | O | | UL SIR 9.2.1.67A | Applicable to 1.28Mcps TDD only | YES | ignore | +| HS-SICH TPC step size | O | | TDD TPC UL Step Size 9.2.3.21a | Applicable to 1.28Mcps TDD only | YES | ignore | +| HS-DSCH MAC-d PDU Size Format | O | | 9.2.1.31ID | If not present, "Indexed MAC-d PDU Size" shall be used. | YES | reject | +| TSN-Length | O | | 9.2.3.5I | Applicable for 1.28Mcps TDD when using multiple frequencies | YES | reject | +| MIMO Activation Indicator | O | | 9.2.1.119 | | YES | reject | + +| Condition | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NofSupportedCarriers | This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band. | + +#### 9.2.3.5G HS-DSCH TDD Information Response + +The HS-DSCH TDD Information Response provides information for HS-DSCH MAC-d flows that have been established or modified. It also provides additional HS-DSCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|---------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-DSCH MAC-d Flow Specific Information Response | | 0..<max NrOfMACdFlows> | | | – | | +| >HS-DSCH MAC-d Flow ID | M | | 9.2.1.31I | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| >HS-DSCH Initial Capacity Allocation | O | | 9.2.1.31Ha | | – | | +| HS-SCCH Specific Information Response | | 0..<max NrOfHSSCCHCodes> | | Not applicable to 1.28 Mcps TDD or 7.68Mcps TDD | GLOBAL | reject | +| >Time Slot | M | | 9.2.3.23 | | – | | +| >Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >HS-SICH Information | | 1 | | | – | | +| >>HS SICH ID | M | | 9.2.3.5Gb | | – | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type | M | | 9.2.3.7 | | – | | +| >>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| HS-SCCH Specific Information Response LCR per UARFCN | | 0..<max HSDPA Frequency> | | Not applicable to 3.84 Mcps TDD or 7.68Mcps TDD
See note1 below | – | | +| >HS-SCCH Specific Information Response LCR | | 1..<max NrOfHSSCCHCodes> | | Not applicable to 3.84 Mcps TDD or 7.68Mcps TDD | GLOBAL | reject | +| >>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>First TDD Channelisation Code | M | | TDD Channelisation Code
9.2.3.19 | | – | | +| >>Second TDD Channelisation Code | M | | TDD Channelisation Code
9.2.3.19 | | – | | +| >>HS-SICH Information LCR | | 1 | | | – | | +| >>>HS SICH ID | M | | 9.2.3.5Gb | If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored. | – | | +| >>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >>>TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | The Extended HS-SICH ID IE shall be used if the HS-SICH | YES | ignore | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|--------------------------------------|-------------|----------------------| +| | | | | identity has a value larger than 31. | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|-----------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>UsedFrequency | O | | UARFCN
9.2.1.65 | Applicable for 1.28Mcps TDD when using multiple frequencies. this IE indicates the frequency which is actually used by the HS-SCCH. | YES | reject | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable for 1.28Mcps TDD when using multiple frequencies. See note2 below | YES | ignore | +| HARQ Memory Partitioning per UARFCN | | 0..<max HSDPA Frequency> | | See note 1 below | – | | +| >HARQ Memory Partitioning | O | | 9.2.1.102 | | – | | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable for 1.28Mcps TDD when using multiple frequencies. See note2 below | YES | ignore | +| HS-SCCH Specific Information Response 7.68Mcps | | 0..<max NrOfHS SCCH Codes> | | Not applicable to 3.84 Mcps TDD or 1.28Mcps TDD | GLOBAL | reject | +| >Time Slot | M | | 9.2.3.23 | | – | | +| >Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >Channelisation Code 7.68Mcps | M | | TDD Channelisation Code 7.68Mcps
9.2.3.34 | | – | | +| >HS-SICH Information 7.68Mcps | | 1 | | | – | | +| >>HS SICH ID | M | | 9.2.3.5Gb | | | | +| >>Time Slot | M | | 9.2.3.23 | | – | | +| >>Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | – | | +| >>Channelisation Code 7.68Mcps | M | | TDD Channelisation Code 7.68Mcps
9.2.3.34 | | – | | +| Multi-Carrier number | O | | INTEGER(1..maxHSDPAFrequency) | Applicable for 1.28Mcps TDD when using multiple frequencies. | YES | ignore | +| MIMO SF Mode for HS-PDSCH dual stream | O | | Enumerated (SF1, SF1/SF16) | Applicable for 1.28Mcps TDD when MIMO is configured | YES | reject | +| MIMO Reference Signal Information | O | 0..<max NrOfHS SCCH Codes> | | Applicable for 1.28Mcps TDD when MIMO is configured | YES | reject | +| >HS-SICH Reference | M | | 9.2.3.103 | | YES | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------------------|-----------------------|-------------|----------------------| +| Signal Information | | | | | | | +| Note 1: | This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxHSDPAFrequency are represented by separate ASN.1 structures with different criticalities. | | | | | | +| Note 2: | The UARFCN IE in the HARQ Memory Partitioning per UARFCN IE has the same content as that in the HS-SCCH Specific Information Response LCR per UARFCN IE. They will be represented by one ASN.1 structure with same criticalities | | | | | | + +| Range Bound | Explanation | +|---------------------------|---------------------------------------------------| +| maxNrOfMACdFlows | Maximum number of HS-DSCH MAC-d flows. | +| maxNrOfHSSCCHCodes | Maximum number of HS-SCCH codes | +| maxHSDPAFrequency | Maximum number of Frequencies that UE can support | + +#### 9.2.3.5GA HS-DSCH TDD Update Information + +The *HS-DSCH TDD Update Information* IE provides information for HS-DSCH to be updated. At least one IE shall be present. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|-----------------------| +| HS-SCCH Code Change Indicator | O | | 9.2.1.31K | | +| TDD ACK NACK Power Offset | O | | 9.2.3.18F | | + +#### 9.2.3.5Ga HS-SCCH ID + +The HS-SCCH ID identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| HS SCCH ID | | | INTEGER (0..31) | | + +#### 9.2.3.5Gb HS-SICH ID + +The HS-SICH ID identifies unambiguously a HS-SICH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| HS SICH ID | | | INTEGER (0..31) | | + +#### 9.2.3.5Gc 1.28 Mcps TDD Uplink Physical Channel Capability + +The *1.28 Mcps TDD Uplink Physical Channel Capability* IE defines the UE uplink radio access capacity, see ref TS 25.306 [33]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------|----------|-------|-----------------------------------------|-----------------------| +| Maximum Number of timeslots per subframe | M | | INTEGER (1..6) | | +| Maximum number of physical channels per timeslot | M | | ENUMERATED (one, two, ..., three, four) | | + +#### 9.2.3.5H IPDL TDD Parameters LCR + +The *IPDL TDD Parameters LCR* IE provides information about IPDL to be applied for 1.28Mcps TDD when activated. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +|---------------|----------|-------|-----------------------|-----------------------| + +| | | | | | +|-----------------------|---|--|--------------------------------------------|--------------------| +| IP SpacingTDD | M | | ENUMERATED
(30, 40, 50, 70, 100, ...) | See TS 25.224 [21] | +| IP Start | M | | INTEGER (0..4095) | See TS 25.224 [21] | +| IP_Sub | M | | ENUMERATED (
First,
Second,
Both) | See TS 25.224 [21] | +| Burst Mode Parameters | O | | 9.2.1.5A | | + +#### 9.2.3.5I TSN-Length + +Indicates the TSN bits applied to the MAC-hs PDU frame. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------------|-----------------------| +| TSN-Length | | | ENUMERATED
(tsn-6bits, tsn-9bits) | | + +#### 9.2.3.5J Extended HS-SCCH ID + +The Extended HS-SCCH ID LCR identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs in a cell for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------| +| Extended HS-SCCH ID | | | INTEGER(32..255) | The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31. | + +#### 9.2.3.5K Extended HS-SICH ID + +The Extended HS-SICH ID LCR identifies unambiguously a HS-SICH in a cell for 1.28Mcps TDD + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------| +| Extended HS-SICH ID | | | INTEGER(32..255) | The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | + +#### 9.2.3.6 Max PRACH Midamble Shift + +Indicates the maximum number of Midamble shifts to be used in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-------------------------------|-----------------------| +| Max PRACH Midamble Shift | | | ENUMERATED
(4, 8, ..., 16) | | + +#### 9.2.3.7 Midamble Shift And Burst Type + +This information element indicates burst type and midamble allocation for burst types 1, 2 and 3. + +The 256 chip midamble supports 3 different time shifts, the 512 chips midamble may support 8 or even 16 time shifts. + +Three different midamble allocation schemes exist: + +Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL) + +Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only) + +UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL) + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------|----------|-------|--------------------------|------------------------------| +| CHOICE Burst Type | | | | | +| >Type1 | | | | | +| >>Midamble Configuration
Burst Type 1 And 3 | M | | ENUMERATED
(4, 8, 16) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | +| >Type2 | | | | | +| >>Midamble Configuration
Burst Type 2 | M | | ENUMERATED
(3, 6) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Short | M | | INTEGER (0..5) | | +| >Type3 | | | | UL only | +| >>Midamble Configuration
Burst Type 1 And 3 | M | | ENUMERATED
(4, 8, 16) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | + +##### 9.2.3.7A Midamble Shift LCR + +This information element indicates midamble allocation in 1.28Mcps TDD. + +Three different midamble allocation schemes exist: + +Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL) + +Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only) + +UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL) + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-------------------------------------------------------------------------------------------|------------------------------| +| Midamble Allocation Mode | M | | ENUMERATED (
Default midamble,
Common midamble,
UE specific
midamble,
...) | | +| Midamble Shift Long | C-UE | | INTEGER (0..15) | | +| Midamble Configuration LCR | M | | ENUMERATED (2,
4, 6, 8, 10, 12, 14,
16, ...) | As defined in TS 25.221 [19] | + +| Condition | Explanation | +|-----------|-----------------------------------------------------------------------------------------------------| +| UE | The IE shall be present if the Midamble Allocation Mode IE is set to "UE-specific midamble". | + +#### 9.2.3.7Aa Notification Indicator Length + +The Notification Indicator Length indicates the number of symbols for Notification Indication transmitted in one timeslot (see ref TS 25.221 [19]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|------------------------------|-----------------------| +| Notification Indicator Length | | | ENUMERATED
(2, 4, 8, ...) | | + +#### 9.2.3.7B Number Of Cycles Per SFN Period + +The *Number Of Cycles Per SFN Period* IE indicates the number of repetitions per SFN period where the same schedule shall apply. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|---------------------------------------------|-----------------------| +| Number Of Cycles Per SFN Period | | | ENUMERATED
(1, 2, 4, 8, ..., 16, 32, 64) | | + +#### 9.2.3.7C Number Of Repetitions Per Cycle Period + +The *Number Of Repetitions Per Cycle Period* IE indicates the number of Sync frames per Cycle Length where the [3.84Mcps TDD - cell synchronisation bursts] [1.28Mcps TDD - Sync\_DL Codes] shall be transmitted or the cell synchronisation bursts from the neighbouring cells shall be measured. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|-----------------------| +| Number Of Repetitions Per Cycle Period | | | INTEGER (2..10) | | + +##### 9.2.3.7D Number Of Subcycles Per Cycle Period + +The *Number Of Subcycles Per Cycle Period* IE indicates the number of subcycles within a Synchronisation Cycle. Within each subcycle, the same sequence of SYNC\_DL Code transmissions and receptions is performed. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| Number Of Subcycles Per Cycle Period | | | INTEGER (1..16,...) | | + +#### 9.2.3.8 Paging Indicator Length + +The Paging Indicator Length indicates the number of symbols for Page Indication transmitted in one timeslot (see ref TS 25.221 [19]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|------------------------------|-----------------------| +| Paging Indicator Length | | | ENUMERATED
(2, 4, 8, ...) | | + +#### 9.2.3.9 PCCPCH Power + +The Primary CCPCH power is the power that shall be used for transmitting the P CCPCH in a cell. The P CCPCH power is the reference power in a TDD-cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CCPCH, the Primary CCPCH power is the linear sum of the power that is used for transmitting the Primary CCPCH on all branches. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------|---------------------------------------------------| +| PCCPCH Power | | | INTEGER
(-150..+400,...) | Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB | + +#### 9.2.3.10 PDSCH ID + +The PDSCH ID identifies unambiguously a PDSCH inside a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| PDSCH ID | | | INTEGER (0..255) | | + +#### 9.2.3.11 PDSCH Set ID + +The PDSCH Set Id identifies unambiguously a PDSCH Set inside a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|------------------------| +| PDSCH Set ID | | | INTEGER (0..255) | See ref. TS 25.430 [6] | + +#### 9.2.3.11A Primary CCPCH RSCP + +Received Signal Code Power is the received power on PCCPCH of the target cell after despreading. The reference point for the RSCP is the antenna connector at the UE, see ref. TS 25.225 [5]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-------------------------------------------------------------------------| +| Primary CCPCH RSCP | | | INTEGER (0..91) | According to mapping of the non-negative values in ref. TS 25.123 [23]. | + +##### 9.2.3.11B Primary CCPCH RSCP Delta + +Primary CCPCH RSCP Delta is the offset used to report the negative reporting range of P-CCPCH RSCP as per TS 25.123 [23]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------| +| Primary CCPCH RSCP Delta | | | INTEGER(-5..-1,...) | If present, the actual value of Primary CCPCH RSCP = Primary CCPCH RSCP Delta | + +#### 9.2.3.12 PUSCH ID + +The PUSCH ID identifies unambiguously a PUSCH inside a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| PUSCH ID | | | INTEGER (0..255) | | + +#### 9.2.3.13 PUSCH Set ID + +The PUSCH Set ID identifies unambiguously a PUSCH Set inside a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|------------------------| +| PUSCH Set ID | | | INTEGER (0..255) | See ref. TS 25.430 [6] | + +#### 9.2.3.14 PRACH Midamble + +The PRACH Midamble indicates if only the Basic Midamble Sequence or also the time-inverted Midamble Sequence is used. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|----------------------------------------------|-----------------------| +| PRACH Midamble | | | ENUMERATED (
Inverted,
Direct,
...) | | + +#### 9.2.3.14A Reference Clock Availability + +The *Reference Clock Availability* IE is used to indicate the presence and operating of a Reference Clock connected to a TDD cell for cell synchronisation purpose. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|----------------------------------------------|-----------------------| +| Reference Clock Availability | | | ENUMERATED (
Available,
Not Available) | | + +##### 9.2.3.14B Reference SFN Offset + +The *Reference SFN Offset* IE indicates the number of frames the reference SFN shall be shifted compared to the SFN derived from the synchronisation port. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|-----------------------| +| Reference SFN Offset | | | INTEGER (0..255) | | + +#### 9.2.3.15 Repetition Length + +The Repetition Length represents the number of consecutive Radio Frames inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see ref. TS 25.331 [18]. + +[1.28Mcps TDD - When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Length represents the number of consecutive Subframes, i.e. 5ms inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see ref. TS 25.331 [18].] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Repetition Length | | | INTEGER (1..63) | | + +#### 9.2.3.16 Repetition Period + +The Repetition Period represents the number of consecutive Radio Frames after which the same assignment scheme of Time Slots to a Physical Channel is repeated. This means that if the Time Slot $K$ is assigned to a physical channel in the Radio Frame $J$ , it is assigned to the same physical channel also in all the Radio Frames $J+n*Repetition\ Period$ (where $n$ is an integer) see ref. TS 25.331 [18]. + +[1.28Mcps TDD- When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Period represents the number of consecutive Subframes, i.e. 5ms after which the same assignment scheme of Time Slots to a Physical Channel is repeated see ref. TS 25.331 [18].] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|--------------------------------------------|-----------------------| +| Repetition Period | | | ENUMERATED
(1, 2, 4, 8, 16, 32, 64,...) | | + +#### 9.2.3.17 SCH Time Slot + +The *SCH Time Slot* IE represents the first time slot (k) of a pair of time slots inside a Radio Frame that shall be assigned to the Physical Channel SCH. The *SCH Time Slot* IE is only applicable if the value of *Sync Case* IE is Case 2 since in this case the SCH is allocated in TS#k and TS#k+8. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| SCH Time Slot | | | INTEGER (0..6) | | + +#### 9.2.3.18 Sync Case + +The SCH and PCCPCH are mapped on one or two downlink slots per frame. There are two cases of SCH and PCCPCH allocation as follows: + +- Case 1) SCH and PCCPCH allocated in a single TS#k + Case 2) SCH allocated in two TS: TS#k and TS#k+8 + PCCPCH allocated in TS#k + +[1.28Mcps TDD - There is no Sync Case indication needed for 1.28Mcps TDD. If the *Sync Case* IE must be included in a message from CRNC to Node B used for 1.28Mcps TDD, the CRNC should indicate Sync Case 1 and the Node B shall ignore it.] + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Sync Case | | | INTEGER (1..2,...) | | + +#### 9.2.3.18A Special Burst Scheduling + +The number of frames between special burst transmissions during DTX. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|----------------------------------------------------------------| +| Special Burst Scheduling | | | INTEGER (1..256) | Number of frames between special burst transmission during DTX | + +#### 9.2.3.18B SYNC\_DL Code ID + +The *SYNC\_DL Code ID* identifies the *SYNC\_DL Code* which used by DwPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-----------------------|-----------------------| +| SYNC_DL Code ID | | | INTEGER (1..32,...) | | + +#### 9.2.3.18C Sync Frame Number + +The *Sync Frame Number* IE indicates the number of the Sync frame within a Synchronisation Cycle or Subcycle, respectively, where the cell synchronisation bursts shall be transmitted or the cell synchronisation bursts from the neighbouring cells shall be measured. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Sync Frame Number | | | INTEGER (1..10) | | + +#### 9.2.3.18D Synchronisation Report Characteristics + +The *Synchronisation Report Characteristics* IE defines how the reporting on measured [3.84Mcps TDD - cell synchronisation bursts] [1.28Mcps TDD - Sync\_DL Codes] shall be performed + +Different methods shall apply for the measured [3.84Mcps TDD - cell synchronisation burst] [1.28Mcps TDD - Sync\_DL Codes] reports. [3.84Mcps TDD - In the frequency acquisition phase the measurement report shall be sent when the frequency locking is completed.] In the initial phase and for the measurement on late-entrant cells an immediate report after the measured frame is expected. + +In the steady-state phase measurement reports may be given after every measured frame, after every SFN period, after every cycle length or only when the requested threshold is exceeded. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------|----------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|-------------|----------------------| +| Synchronisation Report Characteristics Type | M | | ENUMERATED ( Frame related, SFN period related, Cycle length related, Threshold exceeding, Frequency Acquisition completed, ...) | | – | | +| Threshold Exceeding | C-ThresholdExceeding | | | Applies only to the Steady State Phase | – | | +| >Cell Sync Burst Threshold Information | | 0.. | | Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD. | – | | +| >>Sync Frame Number To Receive | M | | Sync Frame Number 9.2.3.18C | | – | | +| >>Cell Sync Burst Information | | 1.. | | | – | | +| >>>Cell Sync Burst Code | M | | 9.2.3.4G | | – | | +| >>>Cell Sync Burst Code Shift | M | | 9.2.3.4H | | – | | +| >>>Cell Sync Burst Arrival Time | O | | Cell Sync Burst Timing 9.2.3.4L | | – | | +| >>>Cell Sync Burst Timing Threshold | O | | 9.2.3.4M | | – | | +| >SYNC_DL Code Threshold Information LCR | | 0.. | | Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD. | GLOBAL | ignore | +| >>Sync Frame Number To Receive | M | | Sync Frame Number 9.2.3.18C | | – | | +| >>SYNC_DL Code Information LCR | | 1.. | | | – | | + +| | | | | | | | +|-------------------------------------|---|-------------------------------|-------------------------------------------|--|---|--| +| | | eptionsperSyncFrameLCR | | | | | +| >>>SYNC_DL Code ID | M | | 9.2.3.18B | | – | | +| >>>SYNC_DL Code ID Arrival Time | O | | Cell Sync Burst Timing LCR 9.2.3.4La | | – | | +| >>>SYNC_DL Code ID Timing Threshold | O | | Cell Sync Burst Timing Threshold 9.2.3.4M | | – | | + +| Range Bound | Explanation | +|-----------------------------------------|-----------------------------------------------------------------------------------------| +| maxNrOfCellSyncBursts | Maximum number of cell synchronisation burst per cycle for 3.84Mcps TDD | +| maxNrOfReceiptsPerSyncFrame | Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD | +| maxNrOfSyncFramesLCR | Maximum number of SYNC Frames per repetition period for 1.28Mcps TDD | +| maxNrOfReceptionsperSyncFrameLCR | Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD | + +#### 9.2.3.18E Synchronisation Report Type + +The *Synchronisation Report Type* IE represents the individual types of synchronisation reports that shall apply within the individual synchronisation phases. (see TS 25.402 [17]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------| +| Synchronisation Report Type | | | ENUMERATED ( Initial Phase, Steady-State Phase, Late-Entrant Cell, Frequency Acquisition, ...) | | + +#### 9.2.3.18F TDD ACK NACK Power Offset + +The *TDD ACK NACK Power Offset* IE indicates Power offset used in the UL in the HS-SICH between transmissions carrying positive and negative acknowledgements as per TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|--------------------------------------------| +| TDD ACK NACK Power Offset | | | INTEGER (-7..8,...) | Unit: dB
Range: -7..+8 dB
Step: 1 dB | + +#### 9.2.3.19 TDD Channelisation Code + +The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|------------------------------------------------------------------------------------------------------------|-----------------------| +| TDD Channelisation Code | | | ENUMERATED (
(1/1),
(2/1), (2/2),
(4/1), .. (4/4),
(8/1), .. (8/8),
(16/1), .. (16/16),...) | | + +##### 9.2.3.19a TDD Channelisation Code LCR + +The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 1.28Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16 and there is a choice between QPSK and 8PSK modulation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|--------------------------------|----------------------------------------------------------------------------------------------------------| +| TDD Channelisation Code | | | 9.2.3.19 | | +| Modulation | | | ENUMERATED
(QPSK, 8PSK,...) | Modulation options for
1.28Mcps TDD in contrast to
3.84Mcps TDD. 8PSK denotes
16QAM for S-CCPCH | + +##### 9.2.3.19A TDD DPCH Offset + +The Offset represents the phase information for the allocation of a group of dedicated physical channels. The *Offset Type* IE = "No Initial Offset" is used when a starting offset is not required and the TDD Physical channel offset for each DPCH in the CCTrCH shall be directly determined from the TDD DPCH Offset. The *Offset Type* IE = "Initial Offset" is used when a starting offset is required. The TDD DPCH Offset shall map to the CFN and the TDD Physical Channel Offset for each DPCH in this CCTrCH shall be calculated by TDD DPCH Offset *mod* Repetition period, see ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Offset Type | | | | | +| > Initial Offset | | | | | +| >>TDD DPCH Offset Value | M | | INTEGER (0..255) | | +| > No Initial Offset | | | | | +| >>TDD DPCH Offset Value | M | | INTEGER (0..63) | | + +#### 9.2.3.19B TDD DL Code Information + +The *TDD DL Code Information* IE provides DL Code information for the RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|----------------------------|-----------------------|-----------------------| +| TDD DL Code Information | | 1..< maxNrOfDPCHs > | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code | M | | 9.2.3.19 | | + +| Range Bound | Explanation | +|---------------------|---------------------------------------| +| maxNrOfDPCHs | Maximum number of DPCHs in one CCTrCH | + +#### 9.2.3.19C TDD DL Code Information LCR + +The *TDD DL Code Information LCR* IE provides DL Code information for the RL. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|----------------------|-----------------------|-----------------------| +| TDD DL Code Information LCR | | 1.. | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code LCR | M | | 9.2.3.19a | | +| >TDD DL DPCH Time Slot Format LCR | M | | 9.2.3.19D | | + +| Range Bound | Explanation | +|-----------------|-------------------------------------------------------| +| maxNrOfDPCHLCRs | Maximum number of DPCH in one CCTrCH for 1.28Mcps TDD | + +##### 9.2.3.19D TDD DL DPCH Time Slot Format LCR + +TDD DL DPCH Time Slot Format LCR indicates the time slot formats used in DL DPCH for 1.28Mcps TDD (see ref. TS 25.221 [19]). It also applies to PDSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Modulation | M | | | | +| >QPSK | | | | | +| >>QPSK TDD DL DPCH Time Slot Format LCR | M | | INTEGER (0..24,...) | | +| >8PSK | | | | | +| >>8PSK TDD DL DPCH Time Slot Format LCR | M | | INTEGER (0..24,...) | For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE denotes MBSFN S-CCPCH time slot format , INTEGER (0..11,...). | + +#### 9.2.3.20 TDD Physical Channel Offset + +The Offset represents the phase information for the allocation of a physical channel. (SFN mod Repetition Period = Offset) see ref. TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| TDD Physical Channel Offset | | | INTEGER (0..63) | | + +#### 9.2.3.21 TDD TPC DL Step Size + +This parameter indicates step size for the DL power adjustment (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|--------------------------|-----------------------| +| TDD TPC Downlink Step Size | | | ENUMERATED (1, 2, 3,...) | Unit: dB | + +#### 9.2.3.21a TDD TPC UL Step Size + +This parameter indicates step size for the UL power adjustment (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|--------------------------|-----------------------| +| TDD TPC Uplink Step Size | | | ENUMERATED (1, 2, 3,...) | Unit: dB | + +##### 9.2.3.21A TDD UL Code Information + +The *TDD UL Code Information* IE provides information for UL Code to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------------------|-----------------------|-----------------------| +| TDD UL Code Information | | 1.. | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code | M | | 9.2.3.19 | | + +| Range Bound | Explanation | +|--------------|---------------------------------------| +| maxNrOfDPCHs | Maximum number of DPCHs in one CCTrCH | + +##### 9.2.3.21B TDD UL Code Information LCR + +The *TDD UL Code Information LCR* IE provides information for UL Code to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|----------------------|-----------------------|-----------------------| +| TDD UL Code Information LCR | | 1.. | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code LCR | M | | 9.2.3.19a | | +| >TDD UL DPCH Time Slot Format LCR | M | | 9.2.3.21C | | + +| Range Bound | Explanation | +|-----------------|--------------------------------------------------------| +| maxNrOfDPCHLCRs | Maximum number of DPCHs in one CCTrCH for 1.28Mcps TDD | + +#### 9.2.3.21C TDD UL DPCH Time Slot Format LCR + +TDD UL DPCH Time Slot Format LCR indicates the time slot formats used in UL DPCH for 1.28Mcps TDD (see ref. TS 25.221 [19]). It also applies to PUSCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Modulation | M | | | | +| >QPSK | | | | | +| >>QPSK TDD UL DPCH Time Slot Format LCR | M | | INTEGER (0..69,...) | | +| >8PSK | | | | | +| >>8PSK TDD UL DPCH Time Slot Format LCR | M | | INTEGER (0..24,...) | | + +#### 9.2.3.22 TFCI Coding + +The TFCI Coding describes the way how the TFCI bits are coded. By default 1 TFCI bit is coded with 4 bits, 2 TFCI bits are coded with 8 bits, 3-5 TFCI bits are coded with 16 bits and 6-10 TFCI bits are coded with 32 bits. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------------|-----------------------| +| TFCI Coding | | | ENUMERATED (4, 8, 16, 32,...) | | + +##### 9.2.3.22a Timing Adjustment Value + +The *Timing Adjustment Value* IE indicates the timing correction within a Frame for 3.84Mcps TDD. Type 1 is used for the initial phase of Node B synchronisation. Type 2 is used for the steady-state phase of Node B synchronisation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|--------------------------|----------------------------------------| +| CHOICE Phase | | | | According to mapping in TS 25.123 [23] | +| > Initial Phase | | | | | +| >>Timing Adjustment Value | M | | INTEGER (0..1048575,...) | | +| > Steady State Phase | | | | | +| >>Timing Adjustment Value | M | | INTEGER (0..255,...) | | + +##### 9.2.3.22b Timing Adjustment Value LCR + +The *Timing Adjustment Value LCR* IE indicates the timing correction within a Frame for 1.28Mcps TDD. Type 1 is used for the initial phase of Node B synchronisation. Type 2 is used for the steady-state phase of Node B synchronisation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-------------------------|----------------------------------------| +| CHOICE Phase | | | | According to mapping in TS 25.123 [23] | +| > Initial Phase | | | | | +| >>Timing Adjustment Value | M | | INTEGER (0..524287,...) | | +| > Steady State Phase | | | | | +| >>Timing Adjustment Value | M | | INTEGER (0..127,...) | | + +##### 9.2.3.22A Timing Advance Applied + +Defines the need for Rx Timing Deviation measurement results to be reported in a particular cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| Timing Advance Applied | | | ENUMERATED (Yes, No) | | + +#### 9.2.3.23 Time Slot + +The Time Slot represents the minimum time interval inside a Radio Frame that can be assigned to a Physical Channel. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Time Slot | | | INTEGER (0..14) | | + +#### 9.2.3.24 Time Slot Direction + +This parameter indicates whether the TS in the cell is used in Uplink or Downlink direction. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|--------------------------|-----------------------| +| Time Slot Direction | | | ENUMERATED (UL, DL, ...) | | + +##### 9.2.3.24A Time Slot LCR + +The Time Slot LCR is the number of the traffic time slot within a 5 ms subframe of LCR TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Time Slot LCR | | | INTEGER (0..6) | | + +##### 9.2.3.24B Time Slot LCR Extension + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------| +| Time Slot LCR Extension | | | ENUMERATED (ts7,...) | ts7 indicates the MBSFN Special Timeslot for 1.28Mcps TDD MBSFN Dedicated Carrier. | + +#### 9.2.3.25 Time Slot Status + +This parameter indicates whether the TS in the cell is active or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------------------|-----------------------| +| Time Slot Status | | | ENUMERATED ( Active, Not Active, ...) | | + +#### 9.2.3.26 Transmission Diversity Applied + +Defines if Transmission Diversity on physical channels that may use closed loop transmit diversity is to be applied in a cell (see ref. TS 25.221 [19]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------| +| Transmission Diversity Applied | | | BOOLEAN | True: Transmission Diversity shall be applied in this Cell.
False: Transmission Diversity shall not be applied in this Cell. | + +##### 9.2.3.26A UL Timeslot ISCP + +UL Timeslot ISCP is the measured interference in a uplink timeslot at the Node B, see ref. TS 25.225 [5]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------|-----------------------------------------| +| UL Timeslot ISCP | | | INTEGER (0..127) | According to mapping in TS 25.123 [23]. | + +#### 9.2.3.26B UL PhysCH SF Variation + +Indicates whether variation of SF in UL is supported by Radio Link or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|------------------------------------------------------------------|-----------------------| +| UL PhysCH SF Variation | | | ENUMERATED ( SF_Variation_supported, SF_Variation_NOT_supported) | | + +##### 9.2.3.26C UL Timeslot Information + +The *UL Timeslot Information* IE provides information on the time slot allocation for an UL DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------------------|-----------------------------------|-----------------------| +| UL Timeslot Information | | 1.. | | | +| >Time Slot | M | | 9.2.3.23 | | +| >Midamble Shift And Burst Type | M | | 9.2.3.7 | | +| >TFCI Presence | M | | 9.2.1.57 | | +| >UL Code Information | M | | TDD UL Code Information 9.2.3.21A | | + +| Range Bound | Explanation | +|--------------|----------------------------------------------------| +| maxNrOfULTSs | Maximum number of Uplink time slots per Radio Link | + +#### 9.2.3.26D UL Time Slot ISCP Info + +The *UL Time Slot ISCP Info* IE provides information for UL Interference level for each time slot within the Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------------------|-----------------------|-----------------------| +| UL Time Slot ISCP Info | | 1.. | | | +| >Time Slot | M | | 9.2.3.23 | | +| >UL Timeslot ISCP | M | | 9.2.3.26A | | + +| Range Bound | Explanation | +|--------------|----------------------------------------------------| +| maxNrOfULTSs | Maximum number of Uplink time slots per Radio Link | + +#### 9.2.3.26E UL Timeslot Information LCR + +The *UL Timeslot Information* IE provides information on the time slot allocation for an UL DPCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|----------------------|---------------------------------------|-----------------------|-------------|----------------------| +| UL Timeslot Information LCR | | 1.. | | | – | | +| >Time Slot LCR | M | | 9.2.3.24A | | – | | +| >Midamble Shift LCR | M | | 9.2.3.7A | | – | | +| >TFCI Presence | M | | 9.2.1.57 | | – | | +| >UL Code Information | M | | TDD UL Code Information LCR 9.2.3.21B | | – | | +| >PLCCH Information | O | | 9.2.3.31 | | YES | reject | + +| Range Bound | Explanation | +|-----------------|----------------------------------------------------------------------| +| maxNrOfULTSLCRs | Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD. | + +##### 9.2.3.26F UL Time Slot ISCP Info LCR + +The *UL Time Slot ISCP Info LCR* IE provides information for UL Interference level for each time slot within the Radio Link. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|----------------------|-----------------------|-----------------------| +| UL Time Slot ISCP Info LCR | | 1.. | | | +| >Time Slot LCR | M | | 9.2.3.24A | | +| >UL Timeslot ISCP | M | | 9.2.3.26A | | + +| Range Bound | Explanation | +|-----------------|---------------------------------------------------------------------| +| maxNrOfULTSLCRs | Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD | + +#### 9.2.3.26G Uplink Synchronisation Frequency + +The *Uplink Synchronisation Frequency* IE specifies the frequency of the adjustment of the uplink transmission timing. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|---------------------------| +| Uplink Synchronisation Frequency | | | INTEGER (1..8) | Unit: subframe
Step: 1 | + +#### 9.2.3.26H Uplink Synchronisation Step Size + +The *Uplink Synchronisation Step Size* IE specifies the step size to be used for the adjustment of the uplink transmission timing. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|----------------------------| +| Uplink Synchronisation Step Size | | | INTEGER (1..8) | Unit: 1/8 chip
Step: 1. | + +#### 9.2.3.27 USCH ID + +The USCH ID uniquely identifies a USCH within a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| USCH ID | | | INTEGER (0..255) | | + +#### 9.2.3.28 USCH Information + +The *USCH Information* IE provides information for USCHs to be established. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------------------|-----------------------|------------------------------------------------------|-------------|----------------------| +| USCH Information | | 1.. | | | – | | +| >USCH ID | M | | 9.2.3.27 | | – | | +| >CCTrCH ID | M | | 9.2.3.3 | UL CCTrCH in which the USCH is mapped | – | | +| >Transport Format Set | M | | 9.2.1.59 | For USCH | – | | +| >Allocation/Retention Priority | M | | 9.2.1.1A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | YES | ignore | +| >TNL QoS | O | | 9.2.1.58A | | YES | ignore | + +| Range Bound | Explanation | +|--------------|------------------------------------| +| maxNrOfUSCHs | Maximum number of USCHs for one UE | + +#### 9.2.3.29 USCH Information Response + +The *USCH Information Response* IE provides information for USCHs that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------------------|-----------------------|-----------------------| +| USCH Information Response | | 1.. | | | +| >USCH ID | M | | 9.2.3.27 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | + +| Range Bound | Explanation | +|--------------|------------------------------------| +| maxNrOfUSCHs | Maximum number of USCHs for one UE | + +#### 9.2.3.30 SCTD Indicator + +Indicates if SCTD antenna diversity is applied or not to beacon channels (see ref. TS 25.221 [19]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------------|-----------------------| +| SCTD Indicator | | | ENUMERATED (active, inactive) | | + +#### 9.2.3.31 PLCCH Information + +The *PLCCH Information* IE carries a PLCCH assignment for a timeslot of an UL DCH-type CCTrCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID | M | | 9.2.1.13 | | +| PLCCH Sequence Number | M | | 9.2.3.32 | | + +#### 9.2.3.32 PLCCH Sequence Number + +This sequence number represents a portion of a PLCCH used to signal TPC / SS bits to a single UE. A value of zero indicates that the PLCCH assignment has been deleted. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| PLCCH Sequence Number | | | INTEGER (0..14) | | + +#### 9.2.3.33 Common Physical Channel ID 7.68Mcps + +Common Physical Channel ID is the unique identifier for one common physical channel within a cell for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID 7.68 Mcps | | | INTEGER (0..511) | | + +#### 9.2.3.34 TDD Channelisation Code 7.68Mcps + +The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 7.68Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code that can have a spreading factor of 1, 2, 4, 8, 16 or 32. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------|-----------------------| +| TDD Channelisation Code | | | ENUMERATED((1/1), (2/1), (2/2), (4/1), .. (4/4), (8/1), .. (8/8), (16/1), .. (16/16), (32/1), .. (32,32),.... ) | | + +#### 9.2.3.35 Midamble Shift And Burst Type 7.68Mcps + +This information element indicates burst type and midamble allocation for burst types 1,2 and 3 for 7.68Mcps TDD. + +Three different midamble allocation schemes exist: + +Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL) + +Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only) + +UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL) + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------|----------|-------|-----------------------|------------------------------| +| CHOICE Burst Type | | | | | +| >Type1 | | | | | +| >>Midamble Configuration
Burst Type 1 And 3 | M | | ENUMERATED (4, 8, 16) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | +| >Type2 | | | | | +| >>Midamble Configuration
Burst Type 2 | M | | ENUMERATED (4, 8) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Short | M | | INTEGER (0..7) | | +| >Type3 | | | | UL only | +| >>Midamble Configuration
Burst Type 1 And 3 | M | | ENUMERATED (4, 8, 16) | As defined in TS 25.221 [19] | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>UE Specific
Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | + +#### 9.2.3.36 Common Physical Channel Status Information 7.68Mcps + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|-----------------------| +| Common Physical Channel ID
7.68 Mcps | M | | 9.2.3.33 | | +| Resource Operational State | M | | 9.2.1.52 | | +| Availability Status | M | | 9.2.1.2 | | + +#### 9.2.3.37 Neighbouring TDD Cell Measurement Information 7.68Mcps + +This IE provides information on the 7.68 Mcps TDD neighbouring cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the *Time Slot* IE and *Midamble Shift And Burst Type 7.68Mcps* IE shall be included if available. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|-------------------------------------| +| UC-Id | M | | 9.2.1.65B | | +| UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | +| Cell Parameter ID | M | | 9.2.3.4 | | +| Time Slot | O | | 9.2.3.23 | | +| Midamble Shift And Burst Type
7.68Mcps | O | | 9.2.3.35 | | + +#### 9.2.3.38 UL Timeslot Information 7.68Mcps TDD + +The *UL Timeslot Information* IE provides information on the time slot allocation for an UL DPCH for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|--------------------------------|-----------------------------------------------|-----------------------| +| UL Timeslot Information | | 1..<maxNrOfULTSs> | | | +| >Time Slot | M | | 9.2.3.23 | | +| >Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | +| >TFCI Presence | M | | 9.2.1.57 | | +| >UL Code Information | M | | TDD UL Code Information 7.68Mcps TDD 9.2.3.40 | | + +| Range Bound | Explanation | +|---------------------|----------------------------------------------------| +| maxNrOfULTSs | Maximum number of Uplink time slots per Radio Link | + +#### 9.2.3.39 DL Timeslot Information 7.68Mcps TDD + +The *DL Timeslot Information* IE provides information for DL Time slot to be established for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|--------------------------------|-----------------------------------------------|-----------------------| +| DL Timeslot Information | | 1..<maxNrOfDLTSs> | | | +| >Time Slot | M | | 9.2.3.23 | | +| >Midamble Shift And Burst Type 7.68Mcps | M | | 9.2.3.35 | | +| >TFCI Presence | M | | 9.2.1.57 | | +| >DL Code Information | M | | TDD DL Code Information 7.68Mcps TDD 9.2.3.41 | | + +| Range Bound | Explanation | +|---------------------|------------------------------------------------------| +| maxNrOfDLTSs | Maximum number of Downlink time slots per Radio Link | + +#### 9.2.3.40 TDD UL Code Information 7.68Mcps TDD + +The *TDD UL Code Information 7.68Mcps TDD* IE provides information for UL Code to be established for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| TDD UL Code Information | | 1..<maxNrOfDPCHs> | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | + +| Range Bound | Explanation | +|---------------------|----------------------------------------------------------| +| maxNrOfDPCHs | Maximum number of uplink DPCHs in one CCTrCH at 7.68Mcps | + +#### 9.2.3.41 TDD DL Code Information 7.68Mcps TDD + +The *TDD Code Information 7.68Mcps TDD* IE provides DL Code information for the RL for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|----------------------|-----------------------|-----------------------| +| TDD DL Code Information | | 1.. | | | +| >DPCH ID | M | | 9.2.3.5 | | +| >TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | + +| Range Bound | Explanation | +|-----------------|------------------------------------------------------------| +| maxNrOfDPCHs768 | Maximum number of downlink DPCHs in one CCTrCH at 7.68Mcps | + +#### 9.2.3.42 DPCH ID 7.68Mcps + +The *DPCH ID 7.68Mcps* identifies unambiguously a DPCH inside a downlink Radio Link for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| DPCH ID | | | INTEGER (0..479) | | + +#### 9.2.3.43 PDSCH ID 7.68Mcps + +The *PDSCH ID 7.68Mcps* identifies unambiguously a PDSCH inside a cell for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| PDSCH ID | | | INTEGER (0..511) | | + +#### 9.2.3.44 Max E-RUCCH Midamble Shift + +Indicates the maximum number of Midamble shifts to be used in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|----------------------------|-----------------------| +| Max E-RUCCH Midamble Shift | | | ENUMERATED (4, 8, ..., 16) | | + +#### 9.2.3.45 E-PUCH Information + +The *E-PUCH Information* IE provides parameters to configure the E-PUCH physical channel for 3.84Mcps TDD and 7.68 Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Minimum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | +| Maximum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | +| HARQ Info for E-DCH | M | | ENUMERATED (rv0, rvtable) | “rv0” indicates that the UE will only use E_DCH RV index 0.
“rvtable” indicates that the UE will use an RSN based RV index as specified in TS 25.212 [8] | +| N E-UCCH | M | | INTEGER (1..12) | Number of slots that are required to carry TPC and TFCI (consecutively allocated slots beginning with the first). | + +##### 9.2.3.45a E-PUCH Information LCR + +The *E-PUCH Information LCR* IE provides parameters to configure the E-PUCH physical channel for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Minimum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | – | | +| Maximum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | – | | +| HARQ Info for E-DCH | M | | ENUMERATED (rv0, rvtable) | “rv0” indicates that the UE will only use E_DCH RV index 0.
“rvtable” indicates that the UE will use an RSN based RV index as specified in TS 25.212 [8] | – | | +| PRXdes_base | M | | INTEGER (-112..-50) | dBm.
Reference Desired RX power level for E-PUCH.
Reference to Pe-base in TS 25.224 [21] | – | | +| E-PUCH TPC Step Size | M | | TDD TPC UL Step Size 9.2.3.21a | | – | | +| E-AGCH TPC Step Size | M | | TDD TPC DL Step Size 9.2.3.21 | | – | | +| E-PUCH Power Control GAP | O | | INTEGER (1..255) | Unit: Number of subframes.
Reference to E-PUCH Power Control for 1.28Mcps TDD in TS 25.224 [21]. If it is not present, UE shall deem it to be infinite in which case closed loop power control shall always be used. | YES | ignore | + +#### 9.2.3.46 E-TFCS Information TDD + +Whereas the related E-DCH Transport Block sizes are standardised in TS 25.321 [32] this IE gives details on the Reference Betas. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-----------------------|-----------------------|------------------------------------------| +| Reference Beta Information QPSK | | 1.. | | | +| >Reference Code Rate | M | | INTEGER (0..10) | Unit: -
Range: 0 ..1
Step: 0.1 | +| >Reference Beta | M | | INTEGER(-15..16) | Unit: -
Range: -15..+16
Step: 1 dB | +| Reference Beta Information 16QAM | | 1.. | | | +| >Reference Code Rate | M | | INTEGER (0..10) | Unit: -
Range: 0 ..1
Step: 0.1 | +| >Reference Beta | M | | INTEGER(-15..16) | Unit: -
Range: -15..+16
Step: 1 dB | + +| Range Bound | Explanation | +|------------------------|---------------------------------------------| +| maxnoofRefbetas | Maximum number of signalled reference betas | + +#### 9.2.3.47 E-DCH MAC-d Flows Information TDD + +The *E-DCH MAC-d Flows Information TDD* IE is used for the establishment of E-DCH MAC-d flows for TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|---------------------------|-----------------------|--------------------------------------------------------------------------| +| E-DCH MAC-d Flow Specific Information | | 1.. | | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >Allocation/Retention Priority | M | | 9.2.1.1A | | +| >TNL QoS | O | | 9.2.1.58A | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | +| >Payload CRC Presence Indicator | M | | 9.2.1.49 | | +| >Maximum Number Of Retransmissions For E-DCH | M | | 9.2.1.81 | | +| >E-DCH HARQ Power Offset TDD | M | | 9.2.3.61 | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | +| >E-DCH Grant TypeTDD | M | | 9.2.3.53 | | +| >E-DCH Logical Channel Information | M | | 9.2.1.71 | | +| >E-DCH MAC-d Flow Retransmission Timer | O | | 9.2.3.61a | Mandatory for LCR TDD. Not applicable for 3.84Mcps TDD and 7.68Mcps TDD. | + +| Range Bound | Explanation | +|-----------------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | + +#### 9.2.3.48 E-DCH Non-scheduled Grant Information TDD + +The *E-DCH Non-scheduled Grant Information TDD* IE is used to specify the details of a non-scheduled grant for TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| Timeslot Resource Related Information | M | | 9.2.3.54 | | +| Power Resource Related Information | M | | 9.2.3.55 | | +| Repetition Period | M | | 9.2.3.16 | | +| Repetition Length | M | | 9.2.3.15 | | +| TDD E-PUCH Offset | M | | 9.2.3.56 | | +| TDD Channelisation Code | M | | 9.2.3.19 | | + +##### 9.2.3.48a E-DCH Non-scheduled Grant Information LCR TDD + +Only for 1.28Mcps TDD. The *E-DCH Non-scheduled Grant Information LCR TDD* IE is used to specify the details of a non-scheduled grant for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Timeslot Resource Related Information LCR | M | | 9.2.3.54a | | – | | +| Power Resource Related Information | M | | 9.2.3.55 | | – | | +| Repetition Period | M | | 9.2.3.16 | | – | | +| Repetition Length | M | | 9.2.3.15 | | – | | +| Subframe Number | M | | ENUMERATED (0,1) | Used to indicate from which subframe of the Radio Frame indicated by TDD E-PUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant. | – | | +| TDD E-PUCH Offset | M | | 9.2.3.56 | | – | | +| TDD Channelisation Code | M | | 9.2.3.19 | | – | | +| N E-UCCH | M | | INTEGER (1..8) | Number of E-UCCH and TPC instances within an E-DCH TTI. Details are described in TS 25.221 [19] . | – | | +| E-HICH Information | | 1 | | | | | +| >E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored. | – | | +| >Signature Sequence Group Index | M | | INTEGER (0..19) | | – | | +| >Extended E-HICH ID TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | YES | ignore | + +#### 9.2.3.49 E-DCH TDD Information + +The *E-DCH TDD Information* specifies the details of the maximum bit rate and processing overload level. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|-----------------------| +| E-DCH TDD Maximum Bitrate | O | | 9.2.3.57 | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | + +##### 9.2.3.49a E-DCH TDD Information LCR + +Only for 1.28Mcps TDD. The *E-DCH TDD Information LCR* IE specifies the details of the UE physical layer category, Node B processing overload level and power offset, Maximum Number of Retransmission and E-DCH Retransmission timer for scheduling info. The *E-AGCH Inactivity Monitor Threshold* IE is used for E-AGCH channel monitoring control for scheduled transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH Physical Layer Category LCR | O | | 9.2.3.67 | If the Extended E-DCH Physical Layer Category LCR IE is included in the E-DCH TDD Information LCR IE, the E-DCH Physical Layer Category LCR IE shall be ignored. In case of multi-carrier E-DCH, this IE indicates the capability for each carrier. | – | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | – | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | – | | +| Extended E-DCH Physical Layer Category LCR | O | | 9.2.3.67A | The Extended E-DCH Physical Layer Category LCR IE shall be used if the E-DCH Physical Layer Category has a value larger than 5. In case of multi-carrier E-DCH, this IE indicates the capability for each carrier. | YES | reject | +| Maximum Number of Retransmission for Scheduling Info LCR | O | | Maximum Number of Retransmissions for E-DCH 9.2.1.81 | | YES | ignore | +| E-DCH Retransmission timer for Scheduling Info LCR | O | | E-DCH MAC-d Flow Retransmission Timer 9.2.3.61a | | YES | ignore | +| E-AGCH Inactivity Monitor Threshold | O | | Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, spare5, ..., infinity) | Units of subframes. | YES | ignore | +| SNPL Carrier Group Indicator | O | | INTEGER (1..3) | Applicable to 1.28Mcps TDD in multi-carrier E-DCH operation only.

Indicate which SNPL carrier group the carrier indicated by the UARFCN IE in the RL Information IE belongs to.

The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. Shall be ignored if Multi-Carrier E-DCH Information is not configured. | YES | ignore | +| Multi-Carrier E-DCH | O | | 9.2.3.67B | Applicable to 1.28Mcps | YES | reject | + +| | | | | | | | +|-----------------------------|---|--|-----------|--------------------------------------------|-----|--------| +| Physical Layer Category LCR | | | | TDD in multi-carrier E-DCH operation only. | | | +| UE TS0 Capability LCR | O | | 9.2.3.110 | Applicable to 1.28Mcps TDD only. | YES | ignore | + +#### 9.2.3.50 E-DCH TDD Information Response + +The *E-DCH TDD Information Response* IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------------|----------|----------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-DCH TDD MAC-d Flow Specific Information Response | | 0..<maxNrOfEDCHMACdFlows> | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Binding ID | O | | 9.2.1.4 | | – | | +| >Transport Layer Address | O | | 9.2.1.63 | | – | | +| E-AGCH Specific Information Response TDD | | 0..<maxNrOfEAGCHCodes> | | | – | | +| >E-AGCH ID TDD | M | | 9.2.3.51 | | – | | +| E-RNTI | M | | 9.2.1.75 | | – | | +| Scheduled E-HICH Specific Information Response 1.28Mcps TDD | | 0..<maxNrOfEHICHCodes> | | 1.28Mcps TDD only | – | | +| >EI | M | | INTEGER (0..3) | E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried. | – | | +| >E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored | – | | +| >Extended E-HICH ID TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | YES | ignore | + +| Range bound | Explanation | +|-----------------------------|----------------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows | +| maxNrOfEAGCHCodes | Maximum number of E-AGCHs assigned to one UE | +| maxNrOfEHICHCodes | Maximum number of E-HICHs assigned to one UE | + +#### 9.2.3.51 E-AGCH ID TDD + +The *E-AGCH ID* identifies unambiguously an E-AGCH inside a cell for TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------|-----------------------| +| E-AGCH ID | | | INTEGER
(0..31,...,32..255) | | + +#### 9.2.3.51a E-HICH ID TDD + +The *E-HICH ID TDD* IE identifies unambiguously an E-HICH inside a cell for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| E-HICH ID TDD | | | INTEGER (0..31) | | + +##### 9.2.3.51b Extended E-HICH ID TDD + +The *Extended E-HICH ID TDD* IE identifies unambiguously an E-HICH inside a cell for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| Extended E-HICH ID TDD | | | INTEGER (32..255) | | + +#### 9.2.3.52 E-DCH TDD Information to Modify + +The *E-DCH TDD Information to Modify* IE is used for the modification of an E-DCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------|----------------------| +| E-DCH MAC-d Flow Specific Information | | 0..<maxNrOfEDCHMACdFlows> | | | – | | +| >E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | – | | +| >Allocation/Retention Priority | O | | 9.2.1.1A | | – | | +| >Transport Bearer Request Indicator | M | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | | – | | +| >Maximum Number Of Retransmissions for E-DCH | O | | 9.2.1.81 | | – | | +| >E-DCH HARQ Power Offset TDD | O | | 9.2.3.61 | | – | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | – | | +| >E-DCH Grant Type | O | | 9.2.3.53 | | – | | +| >E-DCH Logical Channel To Add | O | | E-DCH Logical Channel Information 9.2.1.71 | | – | | +| >E-DCH Logical Channel To Modify | O | | 9.2.1.72 | | – | | +| >E-DCH Logical Channel To Delete | | 0..<maxnooflogicalchannels> | | | – | | +| >>Logical Channel ID | M | | 9.2.1.80 | | – | | +| >E-DCH MAC-d Flow Retransmission Timer | O | | 9.2.3.61a | LCR TDD only. | – | | +| MAC-e Reset Indicator | O | | 9.2.1.83 | | – | | +| E-DCH MAC-d PDU Size Format | O | | 9.2.1.74B | | YES | reject | +| UE TS0 Capability LCR | O | | 9.2.3.110 | Applicable to 1.28Mcps TDD only. | YES | ignore | + +| Range Bound | Explanation | +|-------------------------------|-------------------------------------| +| maxNrOfEDCHMACdFlows | Maximum number of E-DCH MAC-d flows | +| maxnooflogicalchannels | Maximum number of logical channels | + +#### 9.2.3.53 E-DCH Grant Type TDD + +The *E-DCH Grant Type* identifies whether a MAC-d flow is scheduled or non-scheduled. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------------------|-----------------------| +| E-DCH Grant Type | | | ENUMERATED (Scheduled, Non-scheduled) | | + +#### 9.2.3.54 Timeslot Resource Related Information + +The *Timeslot Resource Related Information* is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| Timeslot Resource Related Information | | | BIT STRING (SIZE(13)) | | + +##### 9.2.3.54a Timeslot Resource Related Information LCR + +Only for 1.28Mcps TDD. The *Timeslot Resource Related Information LCR* IE is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------| +| Timeslot Resource Related Information LCR | | | BIT STRING (SIZE(5)) | | + +#### 9.2.3.55 Power Resource Related Information + +The *Power Resource Related Information* specifies the maximum allowed E-PUCH power resource (dB relative to $P_{e,base}$ ) that the UE may use for non-scheduled transmissions. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------| +| Power Resource Related Information | | | INTEGER (1..32) | The Value indicates 0-31 PRRI index for mapping of Absolute Grant Value in TS 25.222 [34]. | + +#### 9.2.3.56 E-PUCH Offset + +The *E-PUCH Offset* represents the CFN offset at which a non-scheduled E-DCH grant begins. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| E-PUCH Offset | | | INTEGER (0..255) | | + +#### 9.2.3.57 E-DCH TDD Maximum Bitrate + +The *E-DCH TDD Maximum Bitrate* parameter indicates the Maximum Bitrate for an E-DCH in TDD mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-------------------------------------------------------------| +| E-DCH TDD Maximum Bitrate | | | INTEGER (0..9201,...) | Bitrate on transport block level. Unit is kbits per second. | + +#### 9.2.3.58 LTGI Presence + +The *LTGI Presence* indicates to the Node B whether it shall use the Long Term Grant Indicator within E-DCH grants issued in a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-------------------------------| +| LTGI Indicator | | | BOOLEAN | True = LTGI shall be included | + +#### 9.2.3.59 E-HICH Time Offset + +The *E-HICH Time Offset* ( aka $n_{E-HICH}$ (TS 25.221 [19])) is determined by the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| E-HICH Time Offset | | | INTEGER (4..44) | | + +##### 9.2.3.59a E-HICH Time Offset LCR + +Only for 1.28Mcps TDD. The *E-HICH Time Offset LCR* IE(aka $n_{E-HICH}$ (TS 25.221 [19]))is determined by the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| E-HICH Time Offset LCR | | | INTEGER (4..15) | | + +#### 9.2.3.60 E-DCH TDD Capacity Consumption Law + +The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the number of E-AGCH. + +This capacity consumption law indicates the consumption law to be used with the following procedures: + +- Physical Shared Channel Reconfiguration. + +When one or more radio links have been configured to use E-DCH (via Radio Link Setup, Radio Link Addition or radio link reconfiguration procedures) the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall be credited to the Capacity Credit for the Radio Link Deletion procedure that removes the last radio link configured for E-DCH. + +If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------| +| UL Cost | M | | INTEGER (0..65535) | Cost per timeslot of the E-DCH. If not present, zero cost shall be applied. | +| DL Cost | O | | INTEGER (0..65535) | Cost per E-AGCH or E-HICH configured. If not present, zero cost shall be applied. . | + +#### 9.2.3.61 E-DCH HARQ Power Offset TDD + +The *E-DCH HARQ Power Offset TDD* is the power offset measured in dB. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| E-DCH HARQ Power Offset TDD | | | INTEGER (0..6) | | + +##### 9.2.3.61a E-DCH MAC-d Flow Retransmission Timer + +Only for 1.28Mcps TDD. The *E-DCH MAC-d Flow Retransmission Timer* IE is used in the E-DCH retransmission control as defined in TS 25.321 [32]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| E-DCH MAC-d Flow Retransmission Timer | | | ENUMERATED (10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 140, 160, 200, 240, 280, 320, 400, 480, 560,...) | Unit: ms
Node B may use this value to stop the re-transmission of the corresponding MAC-e PDU. | + +#### 9.2.3.62 SNPL Reporting Type + +The *SNPL Reporting Type* indicates to the Node B whether the UEs in a cell shall use the type 1 or type 2 Serving and Neighbour Cell Pathloss metric (TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|---------------------------|-----------------------| +| SNPL Reporting Type | | | ENUMERATED (type1, type2) | | + +#### 9.2.3.63 Maximum Generated Received Total Wide Band Power in Other Cells + +The *Maximum Generated Received Total Wide Band Power in Other Cells* indicates the maximum aggregate UL interference that may be generated from scheduled transmissions into other (non-serving) cells. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| Maximum Generated Received Total Wide Band Power in Other Cells | | | INTEGER (0..621) | The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.123 [23]. | + +#### 9.2.3.64 E-DCH Non-scheduled Grant Information 7.68Mcps TDD + +The *E-DCH Non-scheduled Grant Information 7.68Mcps TDD* IE is used to specify the details of a non-scheduled grant for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| Timeslot Resource Related Information | M | | 9.2.3.54 | | +| Power Resource Related Information | M | | 9.2.3.55 | | +| Repetition Period | M | | 9.2.3.16 | | +| Repetition Length | M | | 9.2.3.15 | | +| TDD E-PUCH Offset | M | | 9.2.3.56 | | +| TDD Channelisation Code 7.68Mcps | M | | 9.2.3.34 | | + +#### 9.2.3.65 E-DCH TDD Information 7.68Mcps + +The *E-DCH TDD Information 7.68Mcps* specifies the details of the maximum bit rate and processing overload level for 7.68Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|-----------------------| +| E-DCH TDD Maximum Bitrate 7.68Mcps | O | | 9.2.3.66 | | +| E-DCH Processing Overload Level | O | | 9.2.1.79 | | +| E-DCH Power Offset for Scheduling Info | O | | 9.2.1.85 | | + +#### 9.2.3.66 E-DCH TDD Maximum Bitrate 7.68Mcps + +The *E-DCH TDD Maximum Bitrate 7.68Mcps* parameter indicates the Maximum Bitrate for an E-DCH in 7.68Mcps TDD mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|------------------------|-------------------------------------------------------------| +| E-DCH TDD Maximum Bitrate 7.68Mcps | | | INTEGER (0..17713,...) | Bitrate on transport block level. Unit is kbits per second. | + +#### 9.2.3.67 E-DCH Physical Layer Category LCR + +Only for 1.28Mcps TDD. The *E-DCH Physical Layer Category LCR* IE parameter indicates the E-DCH physical layer capability of UE in LCR TDD mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|------------------------------| +| E-DCH Physical Layer Category LCR | | | INTEGER(1..5) | As defined in TS 25.306 [33] | + +##### 9.2.3.67A Extended E-DCH Physical Layer Category LCR + +Only for 1.28Mcps TDD. The *Extended E-DCH Physical Layer Category LCR* IE parameter indicates the E-DCH physical layer capability of UE in LCR TDD mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|-----------------------|------------------------------| +| Extended E-DCH Physical Layer Category LCR | | | INTEGER(6,...) | As defined in TS 25.306 [33] | + +##### 9.2.3.67B Multi-Carrier E-DCH Physical Layer Category LCR + +Only for 1.28Mcps TDD. The *Multi-Carrier E-DCH Physical Layer Category LCR* IE parameter indicates the E-DCH physical layer capability of UE in multi-carrier E-DCH operation mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|-----------------------|------------------------------| +| Multi-Carrier E-DCH Physical Layer Category LCR | | | INTEGER(1..8,...) | As defined in TS 25.306 [33] | + +#### 9.2.3.68 E-HICH Type + +The *E-HICH Type* IE identifies whether a E-HICH is scheduled or non-scheduled inside a cell for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------|-----------------------| +| E-HICH Type | | | ENUMERATED ( Scheduled, Non-scheduled) | | + +#### 9.2.3.69 Maximum Target Received Total Wide Band Power LCR + +The *Maximum Target Received Total Wide Band Power LCR* indicates the maximum target UL interference for a certain cell or frequency or cell portion under CRNC, including received wide band power from all sources. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| Maximum Target Received Total Wide Band Power LCR | | | INTEGER (0..621) | The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.123 [23]. | + +#### 9.2.3.70 MBSFN Only Mode Indicator + +The MBSFN only mode indicator indicates from CRNC to the Node B whether the cell is setup for MBSFN only mode for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-------------------------------|-----------------------| +| MBSFN Only Mode Indicator | | | ENUMERATED ( MBSFN Only Mode) | | + +#### 9.2.3.71 MBSFN Only Mode Capability + +This parameter defines the MBSFN only mode capability for a local cell for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|--------------------------------------------------------------------|-----------------------| +| MBSFN Only Mode Capability | | | ENUMERATED ( MBSFN Only Mode capable, MBSFN Only Mode non capable) | | + +#### 9.2.3.72 HS-DSCH Common System Information LCR + +The *HS-DSCH Common System Information LCR* IE provides information for HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH and Information related to BCCH modification. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------------|----------|-------------------------------|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HS-DSCH Common Information LCR | | 0..1 | | | +| >CCCH Priority Queue ID | M | | Priority Queue ID 9.2.1.49C | Applicable for all carriers when using multiple frequencies. | +| >SRB#1 Priority Queue ID | M | | Priority Queue ID 9.2.1.49C | Applicable for all carriers when using multiple frequencies. | +| >Associated Common MAC Flow LCR | M | | Common MAC Flow ID LCR 9.2.3.76 | The Common MAC Flow ID LCR shall be one of the flow IDs defined in the Common MAC Flow Specific Information of this IE or shall only refer to a Common MAC flow already existing in the old configuration. | +| >FACH Measurement Occasion Cycle Length Coefficient | O | | 9.2.1.111 | | +| >BCCH Specific HS-DSCH RNTI Information LCR | O | | 9.2.3.89 | | +| Common MAC Flow Specific Information LCR | | 0.. | | | +| >Common MAC Flow ID LCR | M | | 9.2.3.76 | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | +| >Common MAC Flow Priority Queue Information LCR | | 0.. | | | +| >>Priority Queue Information for Enhanced FACH | M | | Priority Queue Information for Enhanced FACH/PCH 9.2.1.117 | | +| >Transport Bearer Request Indicator | O | | 9.2.1.62A | Shouldn't be contained if the MAC flow is setup in procedure. Should be contained if the MAC flow is modified in procedure | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable for 1.28Mcps TDD when using multiple frequencies. | +| Common H-RNTI Information | | 0.. | | | +| >Common H-RNTI | M | | HS-DSCH RNTI 9.2.1.31J | | +| Sync Information | | 0..1 | | | +| >T-sync | M | | ENUMERATED (40, 80, 120, 160, 200, 300, 400, 500, ...) | Units of MS. | +| >T-protect | M | | ENUMERATED (40, 60, 80, 100, 120, 200, 400, ...) | Units of MS. | + +| | | | | | +|---------------------------|---|--|--------------------------------------|--| +| >N-protect | M | | INTEGER (0..7) | | +| TDD ACK NACK Power Offset | O | | 9.2.3.18F
9.2.1.67A | | +| HS-SICH SIR Target | O | | UL SIR
9.2.1.67A | | +| HS-SICH TPC step size | O | | TDD TPC UL Step
Size
9.2.3.21a | | + +| Range bound | Explanation | +|---------------------------------|------------------------------------------------------------------------| +| maxNrOfCommonMACFlowsLCR | Maximum number of Common MAC Flows for 1.28Mcps TDD | +| maxNrOfcommonMACQueues | Maximum number of Priority Queues for Common MAC Flow for 1.28Mcps TDD | +| maxNrOfCommonHRNTI | Maximum number of Common H-RNTI | + +#### 9.2.3.73 HS-DSCH Paging System Information LCR + +The *HS-DSCH Paging System Information LCR* IE provides information for HS-DSCH configured for UE in Cell\_PCH and URA\_PCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------------------|----------|------------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Paging MAC Flow Specific Information LCR | | 0..<maxNrOfPagingMACFlow> | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | +| >HSDPA Associated PICH Information LCR | O | | 9.2.3.77 | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | +| >ToAWS | O | | 9.2.1.61 | | +| >ToAWE | O | | 9.2.1.60 | | +| >Paging MAC Flow Priority Queue Information LCR | | 0..<maxNrOfPagingMACQueues> | | | +| >>Priority Queue Information for Enhanced PCH | M | | Priority Queue Information for Enhanced FACH/PCH
9.2.1.117 | | +| >Transport Bearer Request Indicator | O | | 9.2.1.62A | Shouldn't be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure | +| HS-SCCH Power | O | | DL Power
9.2.1.21 | | +| HS-PDSCH Power | O | | DL Power
9.2.1.21 | | +| DTCH/DCCH Reception window size | O | | INTEGER (1..16) | Number of subframes for UE to detect the HS-SCCH | +| N PCH | O | | INTEGER (1..8) | | +| Paging Sub-Channel Size | O | | INTEGER (1..3) | number of frames for a Paging sub-channel | +| Transport Block Size List | | 0..<maxNrOfHS-DSCHTBSE-PCH> | | | +| >Transport Block Size Index for Enhanced PCH | M | | INTEGER (1..32) | Index of the value range 1 to 32 of the MAC-ehs transport block size as specified in TS 25.321 [32] | + +| Range bound | Explanation | +|-------------------------------|---------------------------------------------------------------------------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | +| maxNrOfPagingMACQueues | Maximum number of Priority Queues for Paging MAC Flow | +| maxNrOfHS-DSCHTBSE-PCH | Maximum number of HS-DSCH Transport Block Sizes used for Enhanced PCH operation associated HS-SCCH less | + +#### 9.2.3.74 HS-DSCH Common System Information Response LCR + +The *HS-DSCH Common System Information Response LCR* IE provides information for HS-DSCH configured for UE not in Cell\_DCH that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-SCCH Specific Information Response LCR | | 0..<maxNrOfHSSCCHsLCR> | | | - | | +| >HS SCCH ID LCR | M | | 9.2.3.88 | The HS-SCCH ID of the HS-SCCH used for the BCCH specific H-RNTI should be the minimum on each frequency. | - | | +| HARQ Memory Partitioning | O | | 9.2.1.102 | | - | | +| Common MAC Flow Specific Information Response LCR | | 0..<maxNrOfCommonMACFlowsLCR> | | | - | | +| >Common MAC Flow ID LCR | M | | 9.2.3.76 | | - | | +| >Binding ID | O | | 9.2.1.4 | | - | | +| >Transport Layer Address | O | | 9.2.1.63 | | - | | +| >HS-DSCH Initial Capacity Allocation | O | | 9.2.1.31Ha | | - | | +| UARFCN | O | | 9.2.1.65 | Applicable to 1.28Mcps TDD when using multiple frequencies. This is the UARFCN for the first Frequency repetition of HARQ Memory Partitioning | YES | reject | +| HARQ Memory Partitioning Per UARFCN | | 0..<maxFrequencyinCell-1> | | Corresponds to Nt (TS 25.105 [15]). Applicable for 1.28Mcps TDD when using multiple frequencies. | GLOBAL | reject | +| >HARQ Memory Partitioning | M | | 9.2.1.102 | | - | | +| >UARFCN | M | | 9.2.1.65 | | - | | + +| Range Bound | Explanation | +|---------------------------------|--------------------------------------------------------------------| +| maxNrOfCommonMACFlowsLCR | Maximum number of Common MAC Flows for 1.28Mcps TDD | +| maxNrOfHSSCCHsLCR | Maximum number of HS-SCCH codes for 1.28Mcps TDD | +| maxFrequencyinCell-1 | Maximum number of frequencies that can be used in the cell minus 1 | + +#### 9.2.3.75 HS-DSCH Paging System Information Response LCR + +The *HS-DSCH Paging System Information Response LCR* IE provides information for HS-DSCH configured for UE in Cell\_PCH and URA\_PCH that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------------|----------|----------------------------------------|-----------------------|-----------------------| +| Paging MAC Flow Specific Information Response LCR | | 0..<maxNrOfPagingMACFlow> | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | +| >Binding ID | O | | 9.2.1.4 | | +| >Transport Layer Address | O | | 9.2.1.63 | | +| >HS-PDSCH DL Timeslot and Code Information LCR | | 0..<maxNrOfDLTSLCRs> | | | +| >>Time Slot LCR | M | | 9.2.3.24A | | + +| | | | | | +|----------------------------|---|----------------------|----------|--| +| >>Midamble Shift LCR | M | | 9.2.3.7A | | +| >>Codes LCR | | 1.. | | | +| >>>TDD Channelisation Code | M | | 9.2.3.19 | | + +| Range bound | Explanation | +|----------------------|-------------------------------------------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | +| maxNrOfDLTSLCRs | Maximum number of Downlink time slots in a cell for 1.28Mcps TDD | +| maxNrOfHSPDSCHs | Maximum number of HS-PDSCHs in one time slot of a Cell for 1.28Mcps TDD | + +#### 9.2.3.76 Common MAC Flow ID LCR + +The *Common MAC Flow ID LCR* IE is the unique identifier for one Common MAC flow. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| Common MAC Flow ID LCR | | | INTEGER (0..255) | | + +#### 9.2.3.77 HSDPA Associated PICH Information LCR + +The *HSDPA Associated PICH Information LCR* IE provides information for PICH used for Enhanced PCH operation. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|---------------------------------------|-----------------------| +| CHOICE HSDPA PICH | | | | | +| >Shared with PCH | | | | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | +| >Not shared with PCH LCR | | | | | +| >>Common Physical Channel ID | M | | 9.2.1.13 | | +| >> TDD Channelisation Code LCR | M | | 9.2.3.19a | | +| >> Time Slot LCR | M | | 9.2.3.24A | | +| >>Midamble Shift LCR Offset | M | | Midamble Shift LCR 9.2.3.7A | | +| >>TDD Physical Channel offset | M | | 9.2.3.20 | | +| >>Repetition Period | M | | 9.2.3.16 | | +| >>Repetition Length | M | | 9.2.3.15 | | +| >>Paging Indicator Length | M | | 9.2.3.8 | | +| >>PICH Power | M | | 9.2.1.49A | | +| >> Second TDD Code LCR Code LCR | M | | TDD Channelisation Code LCR 9.2.3.19a | | +| >>TSTD Indicator | O | | 9.2.1.64 | | + +#### 9.2.3.78 Common MAC Flows To Delete LCR + +The *Common MAC Flows To Delete LCR* IE is used for the removal of Common MAC flows from a Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| Common MAC Flows To Delete LCR | | 1.. | | | +| >Common MAC Flow ID LCR | M | | 9.2.3.76 | | + +| Range Bound | Explanation | +|---------------------------------|-----------------------------------------------------| +| maxNrOfCommonMACFlowsLCR | Maximum number of Common MAC Flows for 1.28Mcps TDD | + +#### 9.2.3.79 Common E-DCH System Information LCR + +The *Common E-DCH System Information LCR* IE provides information for E-DCH configured for UE in Cell\_FACH and Idle state. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|--------------------------------------------|------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------|----------------------| +| UL Common MAC Flow Specific Information LCR | | 0..<maxNrOfCommonMACFlowsLCR> | | | – | | +| >UL Common MAC Flow ID | M | | Common MAC Flow ID LCR 9.2.3.76 | | – | | +| >Transport Bearer Request Indicator | O | | 9.2.1.62A | | – | | +| >Binding ID | O | | 9.2.1.4 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Transport Layer Address | O | | 9.2.1.63 | Shall be ignored if bearer establishment with ALCAP. | – | | +| >TNL QoS | O | | 9.2.1.58A | Shall be ignored if bearer establishment with ALCAP. | – | | +| >Payload CRC Presence Indicator | O | | 9.2.1.49 | | – | | +| >Common E-DCH MAC-d Flow Specific Information LCR | O | | 9.2.3.81 | | – | | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). Applicable for 1.28Mcps TDD when using multiple frequencies. | – | | +| Common E-PUCH Information LCR | O | | 9.2.3.83 | | – | | +| E-TFCS Information TDD | O | | 9.2.3.46 | | – | | +| Maximum Number of Retransmission for Scheduling Info LCR | O | | Maximum Number of Retransmissions for E-DCH 9.2.1.81 | | – | | +| E-DCH Retransmission timer for Scheduling Info LCR | O | | E-DCH MAC-d Flow Retransmission Timer 9.2.3.61a | | – | | +| UL Synchronisation Parameters LCR | | 0..1 | | | YES | reject | +| >Uplink Synchronisation Step Size | M | | 9.2.3.26H | | – | | +| >Uplink Synchronisation Frequency | M | | 9.2.3.26G | | – | | +| Physical Channel ID for Common E-RNTI Requested Indicator | O | | Enumerated(requested) | | YES | ignore | + +| Range bound | Explanation | +|---------------------------------|------------------------------------| +| maxNrOfCommonMACFlowsLCR | Maximum number of Common MAC Flows | + +#### 9.2.3.80 Common E-DCH System Information Response LCR + +The *Common E-DCH System Information Response LCR* IE provides information for E-DCH configured for UE in Cell\_FACH and Idle state that have been established or modified. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|------------------------------------------|---------------------------------|----------------------------------------------------------------------------------------------|-------------|----------------------| +| UL Common MAC Flow Specific Information Response LCR | | 0..<maxnoofEDCHMACFlowsLCR> | | See Note 1 below | | | +| >UL Common MAC Flow ID | M | | Common MAC Flow ID LCR 9.2.3.76 | | – | – | +| >Binding ID | O | | 9.2.1.4 | | – | – | +| >Transport Layer Address | O | | 9.2.1.63 | | – | – | +| E-AGCH Specific Information Response TDD | | 0..<maxNrOfEAGCHsLCR> | | | | | +| >E-AGCH ID TDD | M | | 9.2.3.51 | | – | – | +| E-HICH Specific Information Response 1.28Mcps TDD | | 0..<maxNrOfEHICHSLCR> | | 1.28Mcps TDD only | | | +| >EI | M | | INTEGER (0..3) | E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried. | – | – | +| >E-HICH ID TDD LCR | M | | 9.2.3.51a | | – | – | +| Common E-RNTI Information LCR | O | | 9.2.3.84 | | – | – | +| UE Status Update Confirm Indicator | O | | BOOLEAN | TRUE means that the Node B supports UE Status Update Confirmation Procedure | YES | ignore | + +Note1: This information element is a simplified representation of the ASN.1. Repetitions 1 to maxnoofEDCHMACFlows and Repetition maxnoofEDCHMACFlows+1 to maxnoofEDCHMACFlowsLCR are represented by separate ASN.1 structures with different criticality. + +| Range bound | Explanation | +|---------------------------------|-------------------------------------| +| maxNrOfCommonMACFlowsLCR | Maximum number of Common MAC Flows | +| maxNrOfEAGCHsLCR | Maximum number of E-AGCHs in a Cell | +| maxNrOfEHICHSLCR | Maximum number of E-HICHs in a Cell | + +#### 9.2.3.81 Common E-DCH MAC-d Flow Specific Information LCR + +The *Common E-DCH MAC-d Flow Specific Information LCR* IE is used for the establishment or modify Common E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|-------------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Common E-DCH MAC-d Flow Specific Information LCR | | 1..<maxNrOfEDCHMACdFlowsLCR> | | | – | | +| >Common E-DCH MAC-d Flow ID LCR | M | | 9.2.3.87 | | – | | +| >Maximum Number Of Retransmissions For E-DCH | O | | 9.2.1.81 | | – | | +| >E-DCH MAC-d Flow Multiplexing List | O | | 9.2.1.69 | | – | | +| >Common E-DCH Logical Channel information | O | 1..<maxnooflogicalchannels> | | | – | | +| >>Logical Channel ID | M | | 9.2.1.80 | | – | | + +| | | | | | | | +|----------------------------------------|---|--|------------------------------------|--|---|--------| +| >>Maximum MAC-c PDU Size Extended | O | | MAC PDU Size Extended
9.2.1.38C | | – | | +| >>Scheduling Priority Indicator | O | | 9.2.1.53H | | – | ignore | +| >E-DCH HARQ Power Offset TDD | O | | 9.2.3.61 | | – | | +| >E-DCH MAC-d Flow Retransmission Timer | O | | 9.2.3.61a | | – | | + +| Range bound | Explanation | +|--------------------------------|------------------------------------------------------| +| maxNrOfEDCHMACdFlowsLCR | Maximum number of E-DCH MAC-d Flows for 1.28Mcps TDD | +| maxnooflogicalchannels | Maximum number of logical channels | + +#### 9.2.3.82 Enhanced UE DRX Information LCR + +The *Enhanced UE DRX Information LCR* IE provides information for configuring the UE in Cell\_FACH state to discontinuously reception for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-------------------------------------|-------------------------------------------------------------------------------------------------| +| T321 | M | | ENUMERATED (100, 200, 400, 800,...) | Determines the time the UE waits until initiating DRX operation, in ms. | +| HS-DSCH DRX cycle FACH | M | | ENUMERATED (4, 8, 16, 32,...) | Determines the length of the DRX Cycle during DRX operation, in frames | +| HS-DSCH Rx burst FACH | M | | ENUMERATED (1, 2, 4, 8, 16,...) | Determines the period within the DRX Cycle that the UE continuously receives HS-DSCH, in frames | + +#### 9.2.3.83 Common E-PUCH Information LCR + +The *Common E-PUCH Information LCR* IE provides parameters to configure the E-PUCH physical channel for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|--------------------------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Minimum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | +| Maximum code rate | M | | INTEGER (0..63) | Unit: -
Range: 0.055 ..1
Step: 0.015 | +| HARQ Info for E-DCH | M | | ENUMERATED (rv0, rvtable) | “rv0” indicates that the UE will only use E_DCH RV index 0.
“rvtable” indicates that the UE will use an RSN based RV index as specified in TS 25.212 [8] | +| PRXdes_base per UARFCN | | 0..<maxFrequencyinCell> | | | +| >PRXdes_base | M | | INTEGER (-112..-50) | dBm. Reference Desired RX power level for E-PUCH. Reference to Pe-base in TS 25.224 [21] | +| >UARFCN | O | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies. | +| E-PUCH TPC Step Size | O | | TDD TPC UL Step Size
9.2.3.21a | | +| E-AGCH TPC Step Size | O | | TDD TPC DL Step Size
9.2.3.21 | | +| E-PUCH Power Control GAP | O | | INTEGER (1..255) | Unit: Number of subframes. Reference to E-PUCH Power Control for 1.28Mcps TDD in TS 25.224 [21]. If it is not present, UE shall deem it to be infinite in which case closed loop power control shall always be used. | + +| Range bound | Explanation | +|---------------------------|-------------------------------------------------------------| +| maxFrequencyinCell | Maximum number of Frequencies that can be defined in a Cell | + +#### 9.2.3.84 Common E-RNTI Information LCR + +The *Common E-RNTI Information LCR* IE provides parameters to configure the common E-RNTI used in enhanced CELL\_FACH and Idle mode. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|---------------------------------------|----------------------------------------|----------------------------------|-------------|----------------------| +| Common E-RNTI Information LCR | | 1..<maxnr ofERUCC HsLCR> | | | – | | +| >Starting E-RNTI | M | | E-RNTI
9.2.1.75 | | – | | +| >Number of group | M | | INTEGER (1..32) | | – | | +| >Number of E-RNTI per group | M | | INTEGER (1..7) | Values 3 to 7 shall not be used. | – | | +| >Associated Physical Channel ID | O | | Common Physical Channel ID
9.2.1.13 | | YES | reject | + +| Range bound | Explanation | +|--------------------------|---------------------------------------------------------| +| maxnrofERUCCHsLCR | Maximum number of E-RUCCH that can be defined in a Cell | + +#### 9.2.3.85 Paging MAC Flows To Delete LCR + +The *Paging MAC Flows To Delete LCR* IE is used for the removal of Paging MAC flows from a Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|----------------------------------------|-----------------------|-----------------------| +| Paging MAC Flows To Delete LCR | | 1..<maxNrOfPagingMACFlow> | | | +| >Paging MAC Flow ID | M | | 9.2.1.113 | | + +| Range Bound | Explanation | +|-----------------------------|------------------------------------| +| maxNrOfPagingMACFlow | Maximum number of Paging MAC Flows | + +#### 9.2.3.86 Common E-DCH MAC-d Flows To Delete LCR + +The *Common E-DCH MAC-d Flows To Delete LCR* IE is used for the removal of E-DCH MAC-d flows. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------------------------------------------|-----------------------|-----------------------| +| Common E-DCH MAC-d Flows To Delete | | 1..<maxNrOfEDCHMACdFlowsLCR> | | | +| >Common E-DCH MAC-d Flow ID LCR | M | | 9.2.3.87 | | + +| Range Bound | Explanation | +|--------------------------------|--------------------------------------------| +| maxNrOfEDCHMACdFlowsLCR | Maximum number of common E-DCH MAC-d flows | + +#### 9.2.3.87 Common E-DCH MAC-d Flow ID LCR + +The *Common E-DCH MAC-d Flow ID LCR* IE is the unique identifier for one MAC-d flow on E-DCH. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| Common E-DCH MAC-d Flow ID LCR | | | INTEGER (0..255) | | + +#### 9.2.3.88 HS-SCCH ID LCR + +The HS-SCCH ID identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-----------------------| +| HS SCCH ID LCR | | | INTEGER (0..255) | | + +#### 9.2.3.89 BCCH Specific HS-DSCH RNTI Information LCR + +The *BCCH Specific HS-DSCH RNTI Information* IE provides information for BCCH Transmission using HS-DSCH for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------|-----------------------| +| BCCH Specific HS-DSCH RNTI | M | | HS-DSCH RNTI
9.2.1.31J | | +| HS-SCCH Power | M | | DL Power
9.2.1.21 | | +| HS-PDSCH Power | M | | DL Power
9.2.1.21 | | + +#### 9.2.3.90 MAC-es Maximum Bit Rate LCR + +The *MAC-es Maximum Bit Rate LCR* IE indicates the maximum number of bits per second to be delivered over the air interface. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-------------------------------------|-----------------------| +| MAC-es Maximum Bit Rate LCR | | | INTEGER
(0..256,000,000
....) | Unit: bit/s | + +#### 9.2.3.91 Semi-Persistent scheduling Capability LCR + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|--------------------------------------------------------------------------------------------|-----------------------| +| Semi-Persistent scheduling Capability LCR | | | ENUMERATED
(Semi-Persistent scheduling Capable, Semi-Persistent scheduling Non-Capable) | | + +#### 9.2.3.92 Continuous Packet Connectivity DRX Capability LCR + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------|-----------------------| +| Continuous Packet Connectivity DRX Capability LCR | | | ENUMERATED
(Continuous Packet Connectivity DRX Capable, Continuous Packet Connectivity DRX Non-Capable) | | + +#### 9.2.3.93 Continuous Packet Connectivity DRX Information LCR + +The *Continuous Packet Connectivity DRX Information LCR* IE defines the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Enabling Delay | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) | Units of radio frames | - | | +| HS-SCCH DRX Information | | 1 | | | - | | +| >UE DRX Cycle | M | | ENUMERATED(1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >Inactivity Threshold for UE DRX Cycle | O | | ENUMERATED(1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >UE DRX Offset | M | | INTEGER (0..63) | Units of subframes. Offset of the UE DRX cycles at the given TTI | - | | +| >Inactivity Threshold for UE DRX Cycle Ext | O | | ENUMERATED(128,256,512,...) | Units of subframes | YES | ignore | +| E-AGCH DRX Information | | 0..1 | | | - | | +| CHOICE E-AGCH DRX information type | M | | | | - | | +| >Same as HS-SCCH | | | NULL | Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent | - | | +| >E-AGCH DRX parameters | | | | | - | | +| >>E-AGCH DRX cycle | M | | Enumerated (1,2,4,8,16,32,64) | Units of subframes. | - | | +| >>E-AGCH Inactivity Monitor Threshold | O | | Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity,...) | Units of subframes. | - | | +| >>E-AGCH DRX Offset | M | | Integer (0.. 63) | Units of subframes. Offset of the E-AGCH DRX cycles. | - | | +| Enabling Delay Ext | O | | Enumerated (infinity,...) | | Yes | ignore | + +#### 9.2.3.94 Continuous Packet Connectivity DRX Information To Modify LCR + +The *Continuous Packet Connectivity DRX Information To Modify LCR* IE is used for modification of Continuous Packet Connectivity DRX information in a Node B Communication Context. The *Continuous Packet Connectivity DRX Information To Modify LCR* IE shall include at least one of the following IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Enabling Delay | O | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) | Units of radio frames | - | | +| CHOICE DRX Information To Modify | O | | | | - | | +| > Modify | | | | | - | | +| >> HS-SCCH DRX-Information | | 0..1 | | | - | | +| >>>UE DRX Cycle | M | | ENUMERATED (1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >>>Inactivity Threshold for UE DRX Cycle | O | | ENUMERATED (1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >>>UE DRX Offset | M | | INTEGER (0..63) | Units of subframes. Offset of the UE DRX cycles at the given TTI. | - | | +| >>>Inactivity Threshold for UE DRX Cycle Ext | O | | ENUMERATED (128,256,512,...) | Units of subframes | YES | ignore | +| >> E-AGCH DRX Information | | 0..1 | | | - | | +| >>>CHOICE E-AGCH DRX Information type | M | | | | - | | +| >>>> Same as HS-SCCH | | | NULL | Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent. | - | | +| >>>> E-AGCH DRX parameters | | | | | - | | +| >>>>>E-AGCH DRX cycle | M | | ENUMERATED (1,2,4,8,16,32,64) | Units of subframes | - | | +| >>>>>E-AGCH Inactivity Monitor Threshold | O | | ENUMERATED (0,1,2,4,8,16,32,64,128,256,512,infinity,...) | Units of subframes | - | | +| >>>>>E-AGCH DRX Offset | M | | INTEGER (0..63) | Units of subframes. Offset of the E-AGCH DRX cycles. | - | | +| > Deactivate | | | NULL | | - | | +| Enabling Delay Ext | O | | ENUMERATED (infinity,...) | | YES | ignore | + +#### 9.2.3.95 Continuous Packet Connectivity DRX Information Response LCR + +Node B uses the *Continuous Packet Connectivity DRX Information Response LCR* IE to inform the CRNC the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). Continuous Packet Connectivity DRX related parameters shall be configured by the CRNC. For the parameters which can be accepted by Node B, the Node B shall not include the related IEs in the *Continuous Packet Connectivity DRX Information Response LCR* IE. For the parameters which can be not accepted by Node B, the Node B shall include the related IEs in the *Continuous Packet Connectivity DRX Information Response LCR* IE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Enabling Delay | O | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) | Units of radio frames | - | | +| HS-SCCH DRX Information | | 0..1 | | | - | | +| >UE DRX Cycle | O | | ENUMERATED(1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >Inactivity Threshold for UE DRX Cycle | O | | ENUMERATED(1,2,4,8,16,32,64,...) | Units of subframes | - | | +| >UE DRX Offset | O | | INTEGER (0..63) | Units of subframes. Offset of the UE DRX cycles at the given TTI | - | | +| >Inactivity Threshold for UE DRX Cycle Ext | O | | ENUMERATED (128,256,512,...) | Units of subframes | YES | ignore | +| E-AGCH DRX Information | | 0..1 | | | - | | +| CHOICE E-AGCH DRX information type | M | | | | - | | +| >Same as HS-SCCH | | | NULL | Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent | - | | +| >E-AGCH DRX parameters | | | | | - | | +| >>E-AGCH DRX cycle | O | | Enumerated (1,2,4,8,16,32,64,...) | Units of subframes. | - | | +| >>E-AGCH Inactivity Monitor Threshold | O | | Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity,...) | Units of subframes. | - | | +| >>E-AGCH DRX Offset | O | | Integer (0.. 63) | Units of subframes. Offset of the E-AGCH DRX cycles. | - | | +| Enabling Delay Ext | O | | Enumerated (infinity,...) | This IE can only be used when the Enabling Delay Ext is included in the request message, otherwise, the IE shall not be used. | Yes | ignore | + +#### 9.2.3.96 HS-DSCH Semi-Persistent scheduling Information LCR + +The *HS-DSCH Semi-Persistent scheduling Information LCR* IE defines the parameters used for HS-DSCH semi-Persistent scheduling for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|---------------------------------------------------------------|-----------------------|--------------------------------------| +| Transport Block Size List | | 1..<
maxNoOf
TBSs-
Mapping-
HS-
DSCH-
SPS > | | | +| >Transport Block Size | M | | INTEGER (0.. | Corresponds to the Transport- | + +| | | | | | +|---------------------------------------------------------------|---|------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| maping Index | | | maxNoOfTBSs-Mapping-HS-DSCH-SPS-1) | block size information field carried on HS-SCCH (see ref TS 25.222 [34]). | +| >Transport Block Size Index | M | | INTEGER (1..maxNoOfHS-DSCH-TBSsLCR) | Corresponds to the TB index in the related Transport Block Size table (see ref TS 25.321 [32]). | +| Repetition Period list | | 1..<maxNoOfRepetition-Period-LCR> | | | +| >Repetition Period Index | M | | INTEGER (0..maxNoOfRepetition-Period-LCR-1) | Corresponds to the Resource repetition period index field carried on HS-SCCH (see ref TS 25.222 [34]). | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64,...) | Units of subframes | +| >Repetition Length | O | | INTEGER (1..63) | Absence means Repetition Length equal to 1. | +| HS-DSCH Semi-Persistent Resource Reservation Indicator | O | | ENUMERATED(Reserve) | Reserve means the HS-DSCH Semi-Persistent Resource is required to be reserved and be informed via response message. | +| HS-DSCH Semi-Persistent scheduling operation Indicator | | 1 | | | +| > CHOICE configuration | | | | | +| >> Logical Channel level | | | BIT STRING (SIZE(16)) | Available when MAC-ehs is configured. Indicates the logical channels for which the HS-DSCH Semi-Persistent operation is intended to be used . | +| >> Priority Queue level | | | BIT STRING (SIZE(8)) | Indicates the Priority Queues for which the HS-DSCH Semi-Persistent operation is intended to be used. | + +| Range Bound | Explanation | +|----------------------------------------|------------------------------------------------------------------| +| maxNoOfHS-DSCH-TBSsLCR | Maximum number of HS-DSCH Transport Block Sizes | +| maxNoOfRepetition-Period-LCR | Maximum number of Repetition Period for 1.28Mcps TDD | +| maxNoOfTBSs-Mapping-HS-DSCH-SPS | Maximum number of Transport Block Size mapping index on HS-SCCH. | + +##### 9.2.3.96a HS-DSCH Semi-Persistent scheduling Information to modify LCR + +The *HS-PSCH Semi-Persistent scheduling Information to modify LCR* IE is used for the modification of HS-DSCH Semi-Persistent scheduling information for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|---------------------------------------------------|------------------------------------------------|------------------------------------------------------------------|-------------|----------------------| +| Transport Block Size List | | 0..<maxNoOfTBSs-Mapping-HS-DSCH-SPS> | | | - | | +| > Transport Block Size maping Index | M | | INTEGER (0..maxNoOfTBSs-Mapping-HS-DSCH-SPS-1) | Corresponds to the Transport-block size information field | - | | + +| | | | | | | | +|--------------------------------------------------------|---|------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | carried on HS-SCCH (see ref TS 25.222 [34]). | | | +| >Transport Block Size Index | M | | INTEGER (1..maxNoOfHS-DSCH-TBSsLCR) | Corresponds to the TB index in the related Transport Block Size table (see ref TS 25.321 [32]). | - | | +| Repetition Period list | | 0..<maxNoOfRepetition-Period-LCR> | | | - | | +| >Repetition Period Index | M | | INTEGER (0..maxNoOfRepetition-Period-LCR) | Corresponds to the Resource repetition period index field carried on HS-SCCH (see ref TS 25.222 [34]). | - | | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64,...) | Units of subframes | - | | +| >Repetition Length | O | | INTEGER (1..63) | Absence means Repetition Length equal to 1. | - | | +| HS-DSCH Semi-Persistent Resource Reservation Indicator | O | | ENUMERATED(Reserve) | Reserve means the Semi-Persistent HS-DSCH Resource is required to be reserved and be informed via response message. | YES | ignore | +| HS-DSCH Semi-Persistent scheduling operation Indicator | | 0..1 | | | YES | reject | +| >CHOICE configuration | | | | | | | +| >>Logical Channel level | | | BIT STRING (SIZE(16)) | Available when MAC-ehs is configured. Indicates the logical channels for which the HS-DSCH Semi-Persistent operation is intended to be used. | | | +| >> Priority Queue level | | | BIT STRING (SIZE(8)) | Indicates the Priority Queues for which the HS-DSCH Semi-Persistent operation is intended to be used. | | | + +| Range Bound | Explanation | +|----------------------------------------|------------------------------------------------------------------| +| maxNoOfHS-DSCH-TBSsLCR | Maximum number of HS-DSCH Transport Block Sizes | +| maxNoOfRepetition-Period-LCR | Maximum number of Repetition Period for 1.28Mcps TDD | +| maxNoOfTBSs-Mapping-HS-DSCH-SPS | Maximum number of Transport Block Size mapping index on HS-SCCH. | + +#### 9.2.3.97 E-DCH Semi-Persistent scheduling Information LCR + +The *E-DCH Semi-Persistent scheduling Information LCR* IE defines the parameters used for E-DCH semi-Persistent scheduling for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Repetition Period list | | 1..<maxNoOfRepetition-Period-LCR> | | | - | | +| >Repetition Period Index | M | | INTEGER (0..maxNoOfRepetition-Period-LCR-1) | | - | | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64,...) | Units of subframes | - | | +| >Repetition Length | O | | INTEGER (1..63) | Absence means Repetition Length equal to 1. | - | | +| E-DCH Semi-Persistent scheduling Indicator | M | | BIT STRING (SIZE(16)) | Indicates the logical channels for which the E-DCH Semi-Persistent operation is intended to be used. | - | | +| Semi-Persistent E-DCH related E-HICH Information | | 1 | | | - | | +| >E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored. | - | | +| >Signature Sequence Group Index | M | | INTEGER (0..19) | | - | | +| >Extended E-HICH ID TDD | O | | 9.2.3.51b | The Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | - | | +| E-DCH Semi-Persistent Resource Reservation Indicator | O | | ENUMERATED(Reserve) | Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response message. | YES | ignore | + +| Range Bound | Explanation | +|-------------------------------------|------------------------------------------------------| +| maxNoOfRepetition-Period-LCR | Maximum number of Repetition Period for 1.28Mcps TDD | + +##### 9.2.3.97a E-DCH Semi-Persistent scheduling Information to modify LCR + +The *E-DCH Semi-Persistent scheduling Information to modify LCR* IE is used for the modification of E-DCH Semi-Persistent scheduling information for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|------------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Repetition Period list | | 0..<maxNoOfRepetition-Period-LCR> | | | - | | +| >Repetition Period Index | M | | INTEGER (0..) | | - | | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64,...) | Units of subframes | - | | +| >Repetition Length | O | | INTEGER (1..63) | Absence means Repetition Length equal to 1. | - | | +| E-DCH Semi-Persistent scheduling Indicator | O | | BIT STRING (SIZE(16)) | Indicates the logical channels for which the E-DCH Semi-Persistent operation is intended to be used. | - | | +| Semi-Persistent E-DCH related E-HICH Information | | 0..1 | | | - | | +| >E-HICH ID TDD | M | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored. | - | | +| >Signature Sequence Group Index | M | | INTEGER (0..19) | | - | | +| >Extended E-HICH ID TDD | O | | 9.2.3.51b | The Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | - | | +| E-DCH Semi-Persistent Resource Reservation Indicator | O | | ENUMERATED(Reserve) | Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response message. | YES | ignore | + +| Range Bound | Explanation | +|-------------------------------------|------------------------------------------------------| +| maxNoOfRepetition-Period-LCR | Maximum number of Repetition Period for 1.28Mcps TDD | + +#### 9.2.3.98 HS-DSCH Semi-Persistent scheduling Information Response LCR + +The *HS-DSCH Semi-Persistent scheduling Information Response LCR* IE provides information for HS-DSCH Semi-Persistent scheduling determined within the Node B (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------------------------|----------|--------------------------|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| HS-SICH information for HS-DSCH Semi-Persistent Scheduling operation | | 1.. | | | - | | +| >HS-SICH mapping index | M | | INTEGER (0..maxNoOf-HS-SICH-SPS-1) | | - | | +| >CHOICE HS-SICH type | | | | | - | | +| >> HS-SCCH associated HS-SICH | | | | | - | | +| >>>HS-SICH ID | M | | 9.2.3.5Gb | If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored. | - | | +| >>>Extended HS-SICH ID | O | | 9.2.3.5K | The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31. | - | | +| >> Non-HS-SCCH associated HS-SICH | | | | | - | | +| >>>Non-HS-SCCH associated HS-SICH ID | M | | INTEGER (0..255) | | - | | +| Allocated HS-PDSCH Semi-persistent resource | | 0..1 | | | - | | +| > Repetition Period Index | M | | INTEGER (0..maxNoOfRepetition-Period-LCR-1) | | - | | +| >Repetition Length for HS-PDSCH Semi-persistent Resource | O | | INTEGER (1..63) | The IE is not used. | - | | +| >HS-PDSCH offset | M | | INTEGER (0..63) | Units of subframes | - | | +| >Timeslot Resource Related Information | M | | BIT STRING (SIZE(5)) | Each bit indicates availability of a timeslot, where the bit 0 corresponds to TS2, the bit 1 is TS3, the bit 3 is TS4... bit 5 corresponds to TS6.
The value 1 of a bit indicates that the corresponding timeslot is available. Bit 0 is the first/leftmost bit of the bit string. | - | | +| >Start Code | M | | TDD Channelisation Code 9.2.3.19 | | - | | +| >End Code | M | | TDD Channelisation Code 9.2.3.19 | | - | | +| >Transport Block Size Index | M | | INTEGER (0..maxNoOfTBSs-Mapping-HS-DSCH-SPS-1) | | - | | +| >Modulation type | M | | ENUMERATED (QPSK, 16QAM) | | - | | +| >HS-SICH mapping index | M | | INTEGER (0..maxNoOf-HS-SICH-SPS-1) | | - | | + +| | | | | | | | +|------------------------------------------------------------|---|--|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >HS-PDSCH Midamble Configuation | O | | Midamble Shift LCR 9.2.3.7A | | YES | reject | +| Buffer Size for HS-DSCH Semi-Persistent scheduling | O | | ENUMERATED (800..304000,...) | Indicats the buffer size that shall be reserved for HS-DSCH semi-persistent scheduling operation.

800 .. 16000 by step of 800, 17600 .. 32000 by step of 1600, 36000 .. 80000 by step of 4000, 88000 .. 160000 by step of 8000, 176000 .. 304000 by step of 16000 | - | | +| Number of Processes for HS-DSCH Semi-Persistent scheduling | O | | INTEGER (1..16) | | - | | + +| Range Bound | Explanation | +|----------------------------------------|----------------------------------------------------------------------------| +| maxNoOf-HS-SICH-SPS | Maximum number of HS-SICH for HS-DSCH Semi-Persistent scheduling operation | +| maxNoOfTBSs-Mapping-HS-DSCH-SPS | Maximum number of Transport Block Size mapping index on HS-SCCH. | + +#### 9.2.3.99 E-DCH Semi-Persistent scheduling Information Response LCR + +The *E-DCH Semi-Persistent scheduling Information Response LCR* IE provides information for E-DCH Semi-Persistent scheduling information determined within the Node B (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Allocated E-DCH Semi-persistent resource | | 1 | | | | | +| >Timeslot Resource Related Information LCR | M | | 9.2.3.54a | | | | +| >Power Resource Related Information | M | | 9.2.3.55 | | | | +| >Repetition Length | M | | INTEGER (1..63) | The IE shall be ignored. | | | +| >Subframe Number | M | | ENUMERATE D ( 0,1) | Used to indicate from which subframe of the Radio Frame indicated by TDD E-PUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant. | | | +| >TDD E-PUCH Offset | M | | 9.2.3.56 | | | | +| >TDD Channelisation Code | M | | 9.2.3.19 | | | | +| >NE-UCCH | M | | INTEGER (1..8) | Number of E-UCCH and TPC instances within an E-DCH TTI. Details are described in TS 25.221 [19] . | | | +| >Repetition Period Index | O | | INTEGER (0..maxNumberOfRepetition-Period-LCR-1) | | YES | reject | + +#### 9.2.3.100 HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR + +The *HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR* IE is used to deactivate HS-DSCH Semi-Persistent scheduling operation for 1.28 Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| HS-DSCH Semi-Persistent scheduling Deactivate Indicator | M | | NULL | | + +#### 9.2.3.101 E-DCH Semi-Persistent scheduling Deactivate Indicator LCR + +The *E-DCH Semi-Persistent scheduling Deactivate Indicator LCR* IE is used to deactivate E-DCH Semi-Persistent scheduling operation for 1.28 Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| E-DCH Semi-Persistent scheduling Deactivate Indicator | M | | NULL | | + +#### 9.2.3.102 Idle Interval Information + +The *Idle Interval Information* IE indicates the idle interval used for E-UTRAN measurements by a multi-RAT UE in CELL\_DCH state. Ref TS 36.133 [50]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| +| K | M | | INTEGER (0,2,3) | The actual idle interval period = $2^k$ .
Value "0" means to delete the configuration related to E-UTRAN measurement | +| Offset | M | | INTEGER (0..7) | The idle interval position in the period.
The IE shall be ignored when the value of the K IE is set to "0" | + +#### 9.2.3.103 HS-SICH Reference Signal Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------------------------------|------------------------------|-------------|----------------------| +| Midamble Configuration LCR | M | | ENUMERATE D (2, 4, 6, 8, 10, 12, 14, 16, ...) | As defined in TS 25.221 [19] | | | +| Midamble Shift | M | | INTEGER (0..15) | | | | +| Time Slot LCR | M | | 9.2.3.24A | | | | + +#### 9.2.3.104 UE Selected MBMS Service Information + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|---------------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Status | O | | | | | | +| > None | | | NULL | | | | +| > Some | | | | | | | +| >>Selected MBMS Service List | | 1.. | | | | | +| >>>Selected MBMS Service Time Slot Information LCR | M | 0..7 | | This IE indicates the Time Slot information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only. Mandatory if the IE UE Selected MBMS Service Action set to Selected. Otherwise optional. | – | | +| >>>>Time Slot LCR | M | | 9.2.3.24A | | – | | +| >>>MBMS Service TDM Information | | 0..1 | | Indicating the MBMS service TDM Information | | | +| >>>> Transmission Time Interval | M | | ENUMERATED
(10, 20, 40, 80,...) | Unit: ms | | | +| >>>>TDM_Rep | M | | Integer
(2..9) | | | | +| >>>>TDM_Offset | M | | Integer
(0..8) | | | | +| >>>>TDM_Length | M | | Integer
(1..8) | | | | + +#### 9.2.3.105 Best Cell Portions LCR + +*Best Cell Portions LCR* IE indicates the best received cell portions and their RSCP values when Cell Portions are defined in the cell for 1.28 Mcps TDD.. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------------------------------------------------|-----------------------|----------------------------------------| +| Best Cell Portions LCR | | 1..<maxNrOfCellPortionsPerCellLCR> | | | +| >Cell Portion LCR ID | M | | 9.2.3.107 | | +| >RSCP Value | M | | INTEGER (0..127) | According to mapping in TS 25.123 [23] | + +| Range Bound | Explanation | +|--------------------------------------|--------------------------------------------------------------------------| +| maxNrOfCellPortionsPerCellLCR | Maximum number of reported Best Received Cell Portions for 1.28 Mcps TDD | + +#### 9.2.3.106 Cell Portion Capability LCR + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-------------------------------------------------------------|-----------------------| +| Cell Portion Capability LCR | | | ENUMERATED (Cell Portion Capable, Cell Portion Non-Capable) | | + +#### 9.2.3.107 Cell Portion LCR ID + +Cell Portion LCR ID is the unique identifier for a cell portion within a cell for 1.28 Mcps TDD. See TS 25.225 [5]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| Cell Portion LCR ID | | | INTEGER (0..255,...) | | + +#### 9.2.3.108 Number Of Reported Cell Portions LCR + +Number of Reported Cell Portions LCR indicates the number of Best Cell Portions values which shall be included in the measurement report. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| Number Of Reported Cell Portions LCR | | | INTEGER (1..256,...) | | + +#### 9.2.3.109 TS0 Capability LCR + +The parameter defines the TS0 capability for a Local Cell. The TS0 Capable indicates that the HS-PDSCH can be configured in TS0 in the Local Cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-------------------------------------------|-----------------------| +| TS0 Capability LCR | | | ENUMERATED (TS0 Capable, TS0 Non-Capable) | | + +#### 9.2.3.110 UE TS0 Capability LCR + +The *UE TS0 Capability LCR* IE defines the UE TS0 enhancement capability, see ref TS 25.306 [33]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-------------------------------------------------|-----------------------| +| UE TS0 Capability LCR | | | ENUMERATED (UE TS0 Capable, UE TS0 Non-Capable) | | + +#### 9.2.3.111 DCH Measurement Occasion Information + +The *DCH Measurement Occasion Information* IE indicates Measurement Occasion Information used for inter-frequency/inter-RAT measurements in CELL\_DCH state for 1.28Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-----------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CELL_DCH measurement occasion pattern sequence | | 1 to | | | +| >Pattern sequence identifier | M | | INTEGER(1.. maxNrOfDCHMeasurementOccasionPatternSequence) | If an already defined pattern sequence is not present, references to the already defined pattern. | +| >Status Flag | M | | ENUMERATED(activate, deactivate) | This flag indicates whether the measurement occasion pattern sequence shall be activated or deactivated. | +| >Measurement occasion pattern sequence parameters | | 0..1 | | | +| >>k | M | | INTEGER(1..9) | CELL_DCH measurement occasion cycle length coefficient. The actual measurement occasion period equal to $2^k$ radio frames. Value 0 indicates continuous allocation. | +| >>Offset | M | | INTEGER(0..511) | In frames. The measurement occasion position in the measurement period. | +| >>M_Length | M | | INTEGER(1..512) | The measurement occasion length in frames starting from the Offset. | +| >>Timeslot Bitmap | M | | BIT STRING (SIZE(7)) | Bitmap indicating which of the timeslot(s) is/are allocated for measurement.
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not used for measurement. The value 1 of a bit means the corresponding timeslot is used for measurement.
Bit 0 is the first/leftmost bit of the bit string. | + +| Range Bound | Explanation | +|----------------------------------------------|---------------------------------------------------------| +| maxNrOfDCHMeasurementOccasionPatternSequence | Maximum number of measurement occasion pattern sequence | + +#### 9.2.3.112 Multi-Carrier E-DCH Information LCR + +The *Multi-Carrier E-DCH Information LCR* IE defines the parameters used for Multi-Carrier E-DCH operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------------|----------|-----------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multi-Carrier E-DCH Information | | 1.. | | | +| >UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | +| >SNPL Carrier Group Indicator | O | | INTEGER (1..3) | Indicates to which SNPL carrier Group this frequency belongs. The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. The SNPL carrier Group is defined in TS 25.331 [18]. | +| >PRXdes_base | M | | INTEGER (-112..-50) | dBm. Reference Desired RX power level for E-PUCH. Reference to Pe-base in TS 25.224 [21] | +| >Multi-Carrier E-DCH TDD MAC-d Flow Specific Information | | 0.. | | Shall be ignored if bearer establishment with ALCAP.

Shall be present only if the Separate Iub transport bearer mode is used. | +| >>E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >>Binding ID | M | | 9.2.1.4 | | +| >>Transport Layer Address | M | | 9.2.1.63 | | + +| Range Bound | Explanation | +|-----------------------------|-----------------------------------------------------------------------| +| maxNrOfULCarriersLCR | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation | +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | + +#### 9.2.3.113 Multi-Carrier E-DCH Transport Bearer Mode LCR + +This parameter indicates the Multi-Carrier E-DCH Transport Bearer Mode. For *Multi-carrier E-DCH Transport Bearer Mode LCR* = "Separate Iub transport bearer mode", the Mac-d flows from each carrier uses different Iub transport bearers. For *Multi-carrier E-DCH Transport Bearer Mode LCR* = "E-DCH UL flow multiplexing mode", one Mac-d flow received on the different carriers in the Node B is multiplexed on one Iub transport bearer. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|---------------------------------------------------------------------------------------|-----------------------| +| Multi-Carrier E-DCH Transport Bearer Mode | | | ENUMERATED (Separate Iub transport bearer mode, E-DCH UL flow multiplexing mode, ...) | | + +#### 9.2.3.114 Multi-Carrier E-DCH Information Response LCR + +The *Multi-Carrier E-DCH Information Response LCR* IE provides information for E-DCH MAC-d flows that determined within the Node B. It also provides additional E-DCH information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------------------------|----------|-----------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Multi-Carrier E-DCH Information Response | | 1.. | | | +| >UARFCN | M | | 9.2.1.65 | Corresponds to Nt (TS 25.105 [15]). | +| >E-DCH TDD MAC-d Flow Specific Information Response | | 0.. | | | +| >>E-DCH MAC-d Flow ID | M | | 9.2.1.74 | | +| >>Binding ID | O | | 9.2.1.4 | | +| >>Transport Layer Address | O | | 9.2.1.63 | | +| >E-AGCH Specific Information Response TDD | | 0.. | | | +| >>E-AGCH ID TDD | M | | 9.2.3.51 | | +| >Scheduled E-HICH Specific Information Response 1.28Mcps TDD | | 0.. | | | +| >>EI | M | | INTEGER (0..3) | E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried. | +| >>E-HICH ID TDD | O | | 9.2.3.51a | If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE , the E-HICH ID TDD IE shall be ignored | +| >>Extended E-HICH ID TDD | O | | 9.2.3.51b | Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31. | + +| Range bound | Explanation | +|-----------------------------|-----------------------------------------------------------------------| +| maxNrOfULCarriersLCR | Maximum number of uplink frequencies in Multi-Carrier E-DCH Operation | +| maxNrOfEDCHMACdFlows | Maximum number of MAC-d flows. | +| maxNrOfEAGCHCodes | Maximum number of E-AGCHs assigned to one UE | +| maxNrOfEHICHCodes | Maximum number of E-HICHs assigned to one UE | + +#### 9.2.3.115 Cell Capability Container TDD LCR + +The *Cell Capability Container TDD LCR* IE indicates the cell capability of Multi-Carrier related functions by setting the corresponding bit in the BIT String.. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Capability Container TDD LCR | | | BIT STRING (SIZE(8)) |

Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.

The first bit: Multi-Carrier E-DCH Operation Support Indicator. This bit shall be ignored by the SRNC if the second bit: Separate Iub Transport Bearer Support Indicator = "0" and the third bit: E-DCH UL Flow Multiplexing Support Indicator = "0".

The second bit: Separate Iub Transport Bearer Support Indicator, /Multi-carrier/. This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = "0".

The third bit: E-DCH UL Flow Multiplexing Support Indicator, /Multi-carrier/. This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = "0".

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

| + +#### 9.2.3.116 MU-MIMO Information + +The *MU-MIMO Information* IE defines the parameters used for MU-MIMO operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------|------------------------------| +| MU-MIMO Indicator | M | | 9.2.3.120 | | +| Standalone Midamble Channel Information request | O | | ENUMERATED (stand-alone-Midamble-Resource-Requested, stand-alone-Midamble-Resource-not-Requested) | | +| Standalone Midamble Channel Information | | 0..1 | | | +| >Standalone Midamble Configuration | M | | ENUMERATED (2,4,6,8,10,12,14,16, ...) | As defined in TS 25.221 [19] | +| >Standalone Midamble Shift | M | | INTEGER (0..15) | | +| >Timeslot | M | | 9.2.3.24A | | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, ...) | Units of subframes. | +| >Offset | M | | INTEGER (0..63) | Units of subframes. | +| >Reference Beta | C-E-DCH | | INTEGER (-15..16) | Unit range -15db to +16db | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| E-DCH | This IE shall be present if IE "E-DCH Information 1.28Mcps" is present, i.e. the E-DCH related resource is configured. Otherwise it is not needed. | + +#### 9.2.3.117 MU-MIMO Information To Reconfigure + +The *MU-MIMO Information To Reconfigure* IE is used for reconfiguration of MU-MIMO Information in a Node B Communication Context. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|----------------------------------------------|------------------------------| +| CHOICE MU-MIMO Information To reconf | M | | | | +| >Modify | | | | | +| >>MU-MIMO Indicator | O | | 9.2.3.120 | | +| >>Standalone Midamble Configuration | O | | ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...) | As defined in TS 25.221 [19] | +| >>Standalone Midamble Shift | O | | INTEGER (0..15) | | +| >>Timeslot | O | | 9.2.3.24A | | +| >>Repetition Period | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, ...) | Units of Subframes | +| >>Offset | O | | INTEGER (0..63) | Units of Subframes | +| >>Reference Beta | O | | INTEGER (-15..16) | Unit range -15db to +16db | +| >continue | | | NULL | | + +#### 9.2.3.118 MU-MIMO Information Response + +The *MU-MIMO Information Response* IE indicates if the Node B is using MU-MIMO or not. It also provides Standalone Midamble Channel Information determined within the Node B. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------|----------|-------|----------------------------------------------|------------------------------| +| MU-MIMO Usage Indicator | M | | 9.2.3.121 | | +| Standalone Midamble Channel Information | | 0..1 | | | +| >Standalone Midamble Configuration | M | | ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...) | As defined in TS 25.221 [19] | +| >Standalone Midamble Shift | M | | INTEGER (0..15) | | +| >Timeslot | M | | 9.2.3.24A | | +| >Repetition Period | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64) | Units of subframes. | +| >Offset | M | | INTEGER (0..63) | Units of subframes. | +| >Reference Beta | C-E-DCH | | INTEGER (-15..16) | Unit range -15db to +16db | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| E-DCH | This IE shall be present if IE "E-DCH Information 1.28Mcps" is present, i.e. the E-DCH related resource is configured. Otherwise it is not needed. | + +#### 9.2.3.119 MU-MIMO Capability Container + +The *MU-MIMO Capability Container* IE indicates the MU-MIMO related capabilities by setting the corresponding bit in the BIT String. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MU-MIMO Capability Container | | | BIT STRING (SIZE(8)) |

Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.

The first bit: DL MU-MIMO Capability.

The second bit: UL MU-MIMO Capability.

The third bit: Standalone Midamble Capability.

Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

| + +#### 9.2.3.120 MU-MIMO Indicator + +The *MU-MIMO Indicator* IE indicates directions for MU-MIMO operation for 1.28 Mcps TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------------------------------|-----------------------| +| MU-MIMO Indicator | M | | ENUMERATED (UL Only, DL Only, UL and DL, ...) | | + +#### 9.2.3.121 MU-MIMO Usage Indicator + +The *MU-MIMO Usage Indicator* IE indicates if the Node B is using MU-MIMO or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|--------------------------------------------------|-----------------------| +| MU-MIMO Usage Indicator | M | | ENUMERATED (MU-MIMO-Used, MU-MIMO-Not-Used, ...) | | + +#### 9.2.3.122 Adaptive Special Burst Power Capability LCR + +This parameter defines whether the Node B supports Adaptive Special Burst Power. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------|-----------------------| +| Adaptive Special Burst Power Capability LCR | | | ENUMERATED (Adaptive Special Burst Power Capable, Adaptive Special Burst Power non Capable) | | + +#### 9.2.3.123 In Sync Indication Information LCR + +The *In Sync Indication Information LCR* IE is used by RNC to inform Node B the value of N312 and T312 defined in TS 25.331 [18]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------------------------|-----------------------| +| T312 | M | | Integer (0..15) | Value in seconds. | +| N312 | M | | ENUMERATED (s1, s2, s4, s10, s20, s50, s100, s200, s400, s600, s800, s1000) | | + +#### 9.2.3.124 AOA per Cell Portion LCR + +The *AOA per Cell Portion LCR* IE indicates the AOA measurement in each cell portion for 1.28 Mcps TDD.. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------------------------------------|-----------------------------------------|----------------------------------------| +| AOA per Cell Portion LCR | | 1.. | | | +| >Cell Portion LCR ID | M | | 9.2.3.107 | | +| >AOA LCR | M | | INTEGER (0..719) | According to mapping in TS 25.123 [23] | +| >AOA LCR Accuracy Class | M | | ENUMERATED (A, B, C, D, E, F, G, H,...) | According to mapping in TS 25.123 [23] | + +| Range Bound | Explanation | +|--------------------------------|-------------------------------------------------------------| +| MaxNrOfCellPortionsPerCellILCR | Maximum number of Cell Portions in a cell for 1.28 Mcps TDD | + +#### 9.2.3.125 UE RF Band Capability LCR + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|----------------------|--------------------------------------------------|-------------------------------------------------------------| +| UE RF Band Capability Info | | 1.. | | | +| >UE RF Band Capability | M | | ENUMERATED (a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,...) | Corresponds to the radio bands definition (TS 25.105 [15]). | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +NBAP ASN.1 definition conforms with ITU-T Rec. X.680 [12] and ITU-T Rec. X.681 [13]. + +Subclause 9.3 presents the Abstract Syntax of NBAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this subclause and the tabular format in subclauses 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +The ASN.1 definition specifies the structure and content of NBAP messages. NBAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a NBAP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a NBAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in subclause 10.3.6. + +### 9.3.1 Usage of 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 multi-vendor interoperability. +- By vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +NBAP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) nbap (2) version1 (1) nbap-PDU-Descriptions (0) } + +DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +``` + +``` +-- ***** + +IMPORTS + Criticality, + ProcedureID, + MessageDiscriminator, + TransactionID +FROM NBAP-CommonDataTypes + + CommonTransportChannelSetupRequestFDD, + CommonTransportChannelSetupRequestTDD, + CommonTransportChannelSetupResponse, + CommonTransportChannelSetupFailure, + CommonTransportChannelReconfigurationRequestFDD, + CommonTransportChannelReconfigurationRequestTDD, + CommonTransportChannelReconfigurationResponse, + CommonTransportChannelReconfigurationFailure, + CommonTransportChannelDeletionRequest, + CommonTransportChannelDeletionResponse, + BlockResourceRequest, + BlockResourceResponse, + BlockResourceFailure, + UnblockResourceIndication, + AuditFailure, + AuditRequiredIndication, + AuditRequest, + AuditResponse, + CommonMeasurementInitiationRequest, + CommonMeasurementInitiationResponse, + CommonMeasurementInitiationFailure, + CommonMeasurementReport, + CommonMeasurementTerminationRequest, + CommonMeasurementFailureIndication, + CellSetupRequestFDD, + CellSetupRequestTDD, + CellSetupResponse, + CellSetupFailure, + CellReconfigurationRequestFDD, + CellReconfigurationRequestTDD, + CellReconfigurationResponse, + CellReconfigurationFailure, + CellDeletionRequest, + CellDeletionResponse, + InformationExchangeInitiationRequest, + InformationExchangeInitiationResponse, + InformationExchangeInitiationFailure, + InformationReport, + InformationExchangeTerminationRequest, + InformationExchangeFailureIndication, + BearerRearrangementIndication, + ResourceStatusIndication, + SystemInformationUpdateRequest, + SystemInformationUpdateResponse, + SystemInformationUpdateFailure, + ResetRequest, + ResetResponse, + RadioLinkActivationCommandFDD, + RadioLinkActivationCommandTDD, + RadioLinkPreemptionRequiredIndication, + RadioLinkSetupRequestFDD, + RadioLinkSetupRequestTDD, + RadioLinkSetupResponseFDD, + RadioLinkSetupResponseTDD, + RadioLinkSetupFailureFDD, + RadioLinkSetupFailureTDD, + RadioLinkAdditionRequestFDD, + RadioLinkAdditionRequestTDD, + RadioLinkAdditionResponseFDD, + RadioLinkAdditionResponseTDD, + RadioLinkAdditionFailureFDD, + RadioLinkAdditionFailureTDD, + RadioLinkParameterUpdateIndicationFDD, + RadioLinkParameterUpdateIndicationTDD, + RadioLinkReconfigurationPrepareFDD, + RadioLinkReconfigurationPrepareTDD, + RadioLinkReconfigurationReady, + RadioLinkReconfigurationFailure, + RadioLinkReconfigurationCommit, +``` + +RadioLinkReconfigurationCancel, +RadioLinkReconfigurationRequestFDD, +RadioLinkReconfigurationRequestTDD, +RadioLinkReconfigurationResponse, +RadioLinkDeletionRequest, +RadioLinkDeletionResponse, +DL-PowerControlRequest, +DL-PowerTimeslotControlRequest, +DedicatedMeasurementInitiationRequest, +DedicatedMeasurementInitiationResponse, +DedicatedMeasurementInitiationFailure, +DedicatedMeasurementReport, +DedicatedMeasurementTerminationRequest, +DedicatedMeasurementFailureIndication, +RadioLinkFailureIndication, +RadioLinkRestoreIndication, +CompressedModeCommand, +ErrorIndication, +PrivateMessage, +PhysicalSharedChannelReconfigurationRequestTDD, +PhysicalSharedChannelReconfigurationRequestFDD, +PhysicalSharedChannelReconfigurationResponse, +PhysicalSharedChannelReconfigurationFailure, +CellSynchronisationInitiationRequestTDD, +CellSynchronisationInitiationResponseTDD, +CellSynchronisationInitiationFailureTDD, +CellSynchronisationReconfigurationRequestTDD, +CellSynchronisationReconfigurationResponseTDD, +CellSynchronisationReconfigurationFailureTDD, +CellSynchronisationAdjustmentRequestTDD, +CellSynchronisationAdjustmentResponseTDD, +CellSynchronisationAdjustmentFailureTDD, +CellSynchronisationReportTDD, +CellSynchronisationTerminationRequestTDD, +CellSynchronisationFailureIndicationTDD, +MBMSNotificationUpdateCommand, +UEStatusUpdateCommand, +SecondaryULFrequencyReport, +SecondaryULFrequencyUpdateIndication, +UEStatusUpdateConfirmRequest, +UEStatusUpdateConfirmResponse + +FROM NBAP-PDU-Contents + +id-audit, +id-auditRequired, +id-blockResource, +id-cellDeletion, +id-cellReconfiguration, +id-cellSetup, +id-cellSynchronisationInitiation, +id-cellSynchronisationReconfiguration, +id-cellSynchronisationReporting, +id-cellSynchronisationTermination, +id-cellSynchronisationFailure, +id-commonMeasurementFailure, +id-commonMeasurementInitiation, +id-commonMeasurementReport, +id-commonMeasurementTermination, +id-commonTransportChannelDelete, +id-commonTransportChannelReconfigure, +id-commonTransportChannelSetup, +id-compressedModeCommand, +id-dedicatedMeasurementFailure, +id-dedicatedMeasurementInitiation, +id-dedicatedMeasurementReport, +id-dedicatedMeasurementTermination, +id-downlinkPowerControl, +id-downlinkPowerTimeslotControl, +id-errorIndicationForDedicated, +id-errorIndicationForCommon, +id-informationExchangeFailure, +id-informationExchangeInitiation, +id-informationReporting, +id-informationExchangeTermination, +id-BearerRearrangement, +id-mBMSNotificationUpdate, +id-physicalSharedChannelReconfiguration, + +``` + +id-privateMessageForDedicated, +id-privateMessageForCommon, +id-radioLinkActivation, +id-radioLinkAddition, +id-radioLinkDeletion, +id-radioLinkFailure, +id-radioLinkParameterUpdate, +id-radioLinkPreemption, +id-radioLinkRestoration, +id-radioLinkSetup, +id-reset, +id-resourceStatusIndication, +id-cellSynchronisationAdjustment, +id-synchronisedRadioLinkReconfigurationCancellation, +id-synchronisedRadioLinkReconfigurationCommit, +id-synchronisedRadioLinkReconfigurationPreparation, +id-systemInformationUpdate, +id-unblockResource, +id-unSynchronisedRadioLinkReconfiguration, +id-uEStatusUpdate, +id-secondaryULFrequencyReporting, +id-secondaryULFrequencyUpdate, +id-uEStatusUpdateConfirmation + +FROM NBAP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +NBAP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &Outcome OPTIONAL, + &messageDiscriminator MessageDiscriminator, + &procedureID ProcedureID UNIQUE, + &criticality Criticality DEFAULT ignore +} + +WITH SYNTAX { + +``` + +``` + + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + [OUTCOME &Outcome] + MESSAGE DISCRIMINATOR &messageDiscriminator + PROCEDURE ID &procedureID + [CRITICALITY &criticality] + } + + -- ***** + -- + -- Interface PDU Definition + -- + -- ***** + + NBAP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + outcome Outcome, + ... + } + + InitiatingMessage ::= SEQUENCE { + procedureID NBAP-ELEMENTARY-PROCEDURE.&procedureID ({NBAP-ELEMENTARY-PROCEDURES}), + criticality NBAP-ELEMENTARY-PROCEDURE.&criticality ({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + messageDiscriminator NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + transactionID TransactionID, + value NBAP-ELEMENTARY-PROCEDURE.&InitiatingMessage({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}) + } + + SuccessfulOutcome ::= SEQUENCE { + procedureID NBAP-ELEMENTARY-PROCEDURE.&procedureID ({NBAP-ELEMENTARY-PROCEDURES}), + criticality NBAP-ELEMENTARY-PROCEDURE.&criticality ({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + messageDiscriminator NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + transactionID TransactionID, + value NBAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}) + } + + UnsuccessfulOutcome ::= SEQUENCE { + procedureID NBAP-ELEMENTARY-PROCEDURE.&procedureID ({NBAP-ELEMENTARY-PROCEDURES}), + criticality NBAP-ELEMENTARY-PROCEDURE.&criticality ({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + messageDiscriminator NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + transactionID TransactionID, + value NBAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}) + } + + Outcome ::= SEQUENCE { + procedureID NBAP-ELEMENTARY-PROCEDURE.&procedureID ({NBAP-ELEMENTARY-PROCEDURES}), + criticality NBAP-ELEMENTARY-PROCEDURE.&criticality ({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + messageDiscriminator NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}), + transactionID TransactionID, + value NBAP-ELEMENTARY-PROCEDURE.&Outcome ({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}) + } + + -- ***** + -- + -- Interface Elementary Procedure List + -- + -- ***** + + NBAP-ELEMENTARY-PROCEDURES NBAP-ELEMENTARY-PROCEDURE ::= { + NBAP-ELEMENTARY-PROCEDURES-CLASS-1 | + NBAP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... + } + +``` + +``` +NBAP-ELEMENTARY-PROCEDURES-CLASS-1 NBAP-ELEMENTARY-PROCEDURE ::= { + cellSetupFDD + cellSetupTDD + cellReconfigurationFDD + cellReconfigurationTDD + cellDeletion + commonTransportChannelSetupFDD + commonTransportChannelSetupTDD + commonTransportChannelReconfigureFDD + commonTransportChannelReconfigureTDD + commonTransportChannelDelete + audit + blockResource + radioLinkSetupFDD + radioLinkSetupTDD + systemInformationUpdate + commonMeasurementInitiation + radioLinkAdditionFDD + radioLinkAdditionTDD + radioLinkDeletion + reset + synchronisedRadioLinkReconfigurationPreparationFDD + synchronisedRadioLinkReconfigurationPreparationTDD + unSynchronisedRadioLinkReconfigurationFDD + unSynchronisedRadioLinkReconfigurationTDD + dedicatedMeasurementInitiation + physicalSharedChannelReconfigurationTDD + ..., + informationExchangeInitiation + cellSynchronisationInitiationTDD + cellSynchronisationReconfigurationTDD + cellSynchronisationAdjustmentTDD + physicalSharedChannelReconfigurationFDD + ueStatusUpdateConfirmation +} + +NBAP-ELEMENTARY-PROCEDURES-CLASS-2 NBAP-ELEMENTARY-PROCEDURE ::= { + resourceStatusIndication + auditRequired + commonMeasurementReport + commonMeasurementTermination + commonMeasurementFailure + synchronisedRadioLinkReconfigurationCommit + synchronisedRadioLinkReconfigurationCancellation + radioLinkFailure + radioLinkPreemption + radioLinkRestoration + dedicatedMeasurementReport + dedicatedMeasurementTermination + dedicatedMeasurementFailure + downlinkPowerControlFDD + downlinkPowerTimeslotControl + compressedModeCommand + unblockResource + errorIndicationForDedicated + errorIndicationForCommon + privateMessageForDedicated + privateMessageForCommon + ..., + informationReporting + informationExchangeTermination + informationExchangeFailure + cellSynchronisationReportingTDD + cellSynchronisationTerminationTDD + cellSynchronisationFailureTDD + bearerRearrangement + radioLinkActivationFDD + radioLinkActivationTDD + radioLinkParameterUpdateFDD + radioLinkParameterUpdateTDD + mBMSNotificationUpdate + ueStatusUpdate + secondaryULFrequencyReportingFDD + secondaryULFrequencyUpdateFDD +} +``` + +``` +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +-- Class 1 + +-- *** CellSetup (FDD) *** +cellSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSetupRequestFDD + SUCCESSFUL OUTCOME CellSetupResponse + UNSUCCESSFUL OUTCOME CellSetupFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSetup, ddMode fdd } + CRITICALITY reject +} + +-- *** CellSetup (TDD) *** +cellSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSetupRequestTDD + SUCCESSFUL OUTCOME CellSetupResponse + UNSUCCESSFUL OUTCOME CellSetupFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSetup, ddMode tdd } + CRITICALITY reject +} + +-- *** CellReconfiguration (FDD) *** +cellReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellReconfigurationRequestFDD + SUCCESSFUL OUTCOME CellReconfigurationResponse + UNSUCCESSFUL OUTCOME CellReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellReconfiguration, ddMode fdd } + CRITICALITY reject +} + +-- *** CellReconfiguration (TDD) *** +cellReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellReconfigurationRequestTDD + SUCCESSFUL OUTCOME CellReconfigurationResponse + UNSUCCESSFUL OUTCOME CellReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellReconfiguration, ddMode tdd } + CRITICALITY reject +} + +-- *** CellDeletion *** +cellDeletion NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellDeletionRequest + SUCCESSFUL OUTCOME CellDeletionResponse + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellDeletion, ddMode common } + CRITICALITY reject +} + +-- *** CommonTransportChannelSetup (FDD) *** +commonTransportChannelSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonTransportChannelSetupRequestFDD + SUCCESSFUL OUTCOME CommonTransportChannelSetupResponse + UNSUCCESSFUL OUTCOME CommonTransportChannelSetupFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonTransportChannelSetup, ddMode fdd } + CRITICALITY reject +} + +-- *** CommonTransportChannelSetup (TDD) *** +commonTransportChannelSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonTransportChannelSetupRequestTDD + SUCCESSFUL OUTCOME CommonTransportChannelSetupResponse + UNSUCCESSFUL OUTCOME CommonTransportChannelSetupFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonTransportChannelSetup, ddMode tdd } + CRITICALITY reject +} + +-- *** CommonTransportChannelReconfigure (FDD) *** +``` + +``` +commonTransportChannelReconfigureFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonTransportChannelReconfigurationRequestFDD + SUCCESSFUL OUTCOME CommonTransportChannelReconfigurationResponse + UNSUCCESSFUL OUTCOME CommonTransportChannelReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonTransportChannelReconfigure, ddMode fdd } + CRITICALITY reject +} + +-- *** CommonTransportChannelReconfigure (TDD) *** +commonTransportChannelReconfigureTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonTransportChannelReconfigurationRequestTDD + SUCCESSFUL OUTCOME CommonTransportChannelReconfigurationResponse + UNSUCCESSFUL OUTCOME CommonTransportChannelReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonTransportChannelReconfigure, ddMode tdd } + CRITICALITY reject +} + +-- *** CommonTransportChannelDelete *** +commonTransportChannelDelete NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonTransportChannelDeletionRequest + SUCCESSFUL OUTCOME CommonTransportChannelDeletionResponse + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonTransportChannelDelete, ddMode common } + CRITICALITY reject +} + +-- *** Audit *** +audit NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AuditRequest + SUCCESSFUL OUTCOME AuditResponse + UNSUCCESSFUL OUTCOME AuditFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-audit, ddMode common } + CRITICALITY reject +} + +-- *** BlockResourceRequest *** +blockResource NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BlockResourceRequest + SUCCESSFUL OUTCOME BlockResourceResponse + UNSUCCESSFUL OUTCOME BlockResourceFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-blockResource, ddMode common } + CRITICALITY reject +} + +-- *** RadioLinkSetup (FDD) *** +radioLinkSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkSetupRequestFDD + SUCCESSFUL OUTCOME RadioLinkSetupResponseFDD + UNSUCCESSFUL OUTCOME RadioLinkSetupFailureFDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-radioLinkSetup, ddMode fdd } + CRITICALITY reject +} + +-- *** RadioLinkSetup (TDD) *** +radioLinkSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkSetupRequestTDD + SUCCESSFUL OUTCOME RadioLinkSetupResponseTDD + UNSUCCESSFUL OUTCOME RadioLinkSetupFailureTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-radioLinkSetup, ddMode tdd } + CRITICALITY reject +} + +-- *** SystemInformationUpdate *** +systemInformationUpdate NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SystemInformationUpdateRequest + SUCCESSFUL OUTCOME SystemInformationUpdateResponse + UNSUCCESSFUL OUTCOME SystemInformationUpdateFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-systemInformationUpdate, ddMode common } + CRITICALITY reject +} +``` + +``` +-- *** Reset *** +reset NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ResetRequest + SUCCESSFUL OUTCOME ResetResponse + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-reset, ddMode common } + CRITICALITY reject +} + +-- *** CommonMeasurementInitiation *** +commonMeasurementInitiation NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonMeasurementInitiationRequest + SUCCESSFUL OUTCOME CommonMeasurementInitiationResponse + UNSUCCESSFUL OUTCOME CommonMeasurementInitiationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonMeasurementInitiation, ddMode common } + CRITICALITY reject +} + +-- *** RadioLinkAddition (FDD) *** +radioLinkAdditionFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkAdditionRequestFDD + SUCCESSFUL OUTCOME RadioLinkAdditionResponseFDD + UNSUCCESSFUL OUTCOME RadioLinkAdditionFailureFDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkAddition, ddMode fdd } + CRITICALITY reject +} + +-- *** RadioLinkAddition (TDD) *** +radioLinkAdditionTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkAdditionRequestTDD + SUCCESSFUL OUTCOME RadioLinkAdditionResponseTDD + UNSUCCESSFUL OUTCOME RadioLinkAdditionFailureTDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkAddition, ddMode tdd } + CRITICALITY reject +} + +-- *** RadioLinkDeletion *** +radioLinkDeletion NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkDeletionRequest + SUCCESSFUL OUTCOME RadioLinkDeletionResponse + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkDeletion, ddMode common } + CRITICALITY reject +} + +-- *** SynchronisedRadioLinkReconfigurationPreparation (FDD) *** +synchronisedRadioLinkReconfigurationPreparationFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationPrepareFDD + SUCCESSFUL OUTCOME RadioLinkReconfigurationReady + UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationPreparation, +ddMode fdd } + CRITICALITY reject +} + +-- *** SynchronisedRadioLinkReconfigurationPreparation (TDD) *** +synchronisedRadioLinkReconfigurationPreparationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationPrepareTDD + SUCCESSFUL OUTCOME RadioLinkReconfigurationReady + UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationPreparation, +ddMode tdd } + CRITICALITY reject +} + +-- *** UnSynchronisedRadioLinkReconfiguration (FDD) *** +unSynchronisedRadioLinkReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationRequestFDD + SUCCESSFUL OUTCOME RadioLinkReconfigurationResponse + UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode fdd } + CRITICALITY reject +} +``` + +``` +} + +-- *** UnSynchronisedRadioLinkReconfiguration (TDD) *** +unSynchronisedRadioLinkReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationRequestTDD + SUCCESSFUL OUTCOME RadioLinkReconfigurationResponse + UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode tdd } + CRITICALITY reject +} + +-- *** DedicatedMeasurementInitiation *** +dedicatedMeasurementInitiation NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DedicatedMeasurementInitiationRequest + SUCCESSFUL OUTCOME DedicatedMeasurementInitiationResponse + UNSUCCESSFUL OUTCOME DedicatedMeasurementInitiationFailure + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-dedicatedMeasurementInitiation, ddMode common } + CRITICALITY reject +} + +-- *** PhysicalSharedChannelReconfiguration (FDD) *** +physicalSharedChannelReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PhysicalSharedChannelReconfigurationRequestFDD + SUCCESSFUL OUTCOME PhysicalSharedChannelReconfigurationResponse + UNSUCCESSFUL OUTCOME PhysicalSharedChannelReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-physicalSharedChannelReconfiguration, ddMode fdd } + CRITICALITY reject +} + +-- *** PhysicalSharedChannelReconfiguration (TDD) *** +physicalSharedChannelReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PhysicalSharedChannelReconfigurationRequestTDD + SUCCESSFUL OUTCOME PhysicalSharedChannelReconfigurationResponse + UNSUCCESSFUL OUTCOME PhysicalSharedChannelReconfigurationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-physicalSharedChannelReconfiguration, ddMode tdd } + CRITICALITY reject +} + +-- *** InformationExchangeInitiation *** +informationExchangeInitiation NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeInitiationRequest + SUCCESSFUL OUTCOME InformationExchangeInitiationResponse + UNSUCCESSFUL OUTCOME InformationExchangeInitiationFailure + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-informationExchangeInitiation, ddMode common } + CRITICALITY reject +} + +-- *** CellSynchronisationInitiation (TDD only) *** +cellSynchronisationInitiationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationInitiationRequestTDD + SUCCESSFUL OUTCOME CellSynchronisationInitiationResponseTDD + UNSUCCESSFUL OUTCOME CellSynchronisationInitiationFailureTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSynchronisationInitiation, ddMode tdd } + CRITICALITY reject +} + +-- *** CellSynchronisationReconfiguration (TDD only) *** +cellSynchronisationReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationReconfigurationRequestTDD + SUCCESSFUL OUTCOME CellSynchronisationReconfigurationResponseTDD + UNSUCCESSFUL OUTCOME CellSynchronisationReconfigurationFailureTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSynchronisationReconfiguration, ddMode tdd } + CRITICALITY reject +} + +-- *** CellSynchronisationAdjustment (TDD only) *** +cellSynchronisationAdjustmentTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationAdjustmentRequestTDD + SUCCESSFUL OUTCOME CellSynchronisationAdjustmentResponseTDD + UNSUCCESSFUL OUTCOME CellSynchronisationAdjustmentFailureTDD + MESSAGE DISCRIMINATOR common +} +``` + +``` + PROCEDURE ID { procedureCode id-cellSynchronisationAdjustment, ddMode tdd } + CRITICALITY reject + } + + -- *** UEStatusUpdateConfirmation *** + ueStatusUpdateConfirmation NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEStatusUpdateConfirmRequest + SUCCESSFUL OUTCOME UEStatusUpdateConfirmResponse + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-uEStatusUpdateConfirmation, ddMode common } + CRITICALITY reject + } + + -- Class 2 + + -- *** ResourceStatusIndication *** + resourceStatusIndication NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ResourceStatusIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-resourceStatusIndication, ddMode common } + CRITICALITY ignore + } + + -- *** AuditRequired *** + auditRequired NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AuditRequiredIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-auditRequired, ddMode common } + CRITICALITY ignore + } + + -- *** CommonMeasurementReport *** + commonMeasurementReport NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonMeasurementReport + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonMeasurementReport, ddMode common } + CRITICALITY ignore + } + + -- *** CommonMeasurementTermination *** + commonMeasurementTermination NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonMeasurementTerminationRequest + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonMeasurementTermination, ddMode common } + CRITICALITY ignore + } + + -- *** CommonMeasurementFailure *** + commonMeasurementFailure NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CommonMeasurementFailureIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-commonMeasurementFailure, ddMode common } + CRITICALITY ignore + } + + -- *** SynchronisedRadioLinkReconfigurationCommit *** + synchronisedRadioLinkReconfigurationCommit NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationCommit + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationCommit, ddMode +common } + CRITICALITY ignore + } + + -- *** SynchronisedRadioReconfigurationCancellation *** + synchronisedRadioLinkReconfigurationCancellation NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkReconfigurationCancel + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationCancellation, +ddMode common } + CRITICALITY ignore + } + + -- *** RadioLinkFailure *** + radioLinkFailure NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkFailureIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkFailure, ddMode common } +``` + +``` + CRITICALITY ignore + } + + -- *** RadioLinkPreemption *** + radioLinkPreemption NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkPreemptionRequiredIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkPreemption, ddMode common } + CRITICALITY ignore + } + + -- *** RadioLinkRestoration *** + radioLinkRestoration NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkRestoreIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkRestoration, ddMode common } + CRITICALITY ignore + } + + -- *** DedicatedMeasurementReport *** + dedicatedMeasurementReport NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DedicatedMeasurementReport + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-dedicatedMeasurementReport, ddMode common } + CRITICALITY ignore + } + + -- *** DedicatedMeasurementTermination *** + dedicatedMeasurementTermination NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DedicatedMeasurementTerminationRequest + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-dedicatedMeasurementTermination, ddMode common } + CRITICALITY ignore + } + + -- *** DedicatedMeasurementFailure *** + dedicatedMeasurementFailure NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DedicatedMeasurementFailureIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-dedicatedMeasurementFailure, ddMode common } + CRITICALITY ignore + } + + -- *** DLPowerControl (FDD only) *** + downlinkPowerControlFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DL-PowerControlRequest + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-downlinkPowerControl, ddMode fdd } + CRITICALITY ignore + } + + -- *** DLPowerTimeslotControl (TDD only) *** + downlinkPowerTimeslotControl NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DL-PowerTimeslotControlRequest + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-downlinkPowerTimeslotControl, ddMode tdd } + CRITICALITY ignore + } + + -- *** CompressedModeCommand (FDD only) *** + compressedModeCommand NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CompressedModeCommand + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-compressedModeCommand, ddMode fdd } + CRITICALITY ignore + } + + -- *** UnblockResourceIndication *** + unblockResource NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UnblockResourceIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-unblockResource, ddMode common } + CRITICALITY ignore + } + + -- *** ErrorIndication for Dedicated procedures *** + errorIndicationForDedicated NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + } +``` + +``` + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-errorIndicationForDedicated, ddMode common } + CRITICALITY ignore + } + + -- *** ErrorIndication for Common procedures *** + errorIndicationForCommon NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-errorIndicationForCommon, ddMode common } + CRITICALITY ignore + } + + -- *** CellSynchronisationReporting (TDD only) *** + cellSynchronisationReportingTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationReportTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSynchronisationReporting, ddMode tdd } + CRITICALITY ignore + } + + -- *** CellSynchronisationTermination (TDD only) *** + cellSynchronisationTerminationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationTerminationRequestTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSynchronisationTermination, ddMode tdd } + CRITICALITY ignore + } + + -- *** CellSynchronisationFailure (TDD only) *** + cellSynchronisationFailureTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellSynchronisationFailureIndicationTDD + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-cellSynchronisationFailure, ddMode tdd } + CRITICALITY ignore + } + + -- *** PrivateMessage for Dedicated procedures *** + privateMessageForDedicated NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-privateMessageForDedicated, ddMode common } + CRITICALITY ignore + } + + -- *** PrivateMessage for Common procedures *** + privateMessageForCommon NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-privateMessageForCommon, ddMode common } + CRITICALITY ignore + } + + -- *** InformationReporting *** + informationReporting NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationReport + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-informationReporting, ddMode common } + CRITICALITY ignore + } + + -- *** InformationExchangeTermination *** + informationExchangeTermination NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeTerminationRequest + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-informationExchangeTermination, ddMode common } + CRITICALITY ignore + } + + -- *** InformationExchangeFailure *** + informationExchangeFailure NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeFailureIndication + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-informationExchangeFailure, ddMode common } + CRITICALITY ignore + } + + -- *** BearerRearrangement *** +``` + +``` + +bearerRearrangement NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerRearrangementIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-BearerRearrangement, ddMode common } + CRITICALITY ignore +} + +-- *** RadioLinkActivation (FDD) *** +radioLinkActivationFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkActivationCommandFDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkActivation, ddMode fdd } + CRITICALITY ignore +} + +-- *** RadioLinkActivation (TDD) *** +radioLinkActivationTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkActivationCommandTDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkActivation, ddMode tdd } + CRITICALITY ignore +} + +-- *** RadioLinkParameterUpdate (FDD) *** +radioLinkParameterUpdateFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkParameterUpdateIndicationFDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkParameterUpdate, ddMode fdd } + CRITICALITY ignore +} + +-- *** RadioLinkParameterUpdate (TDD) *** +radioLinkParameterUpdateTDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RadioLinkParameterUpdateIndicationTDD + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-radioLinkParameterUpdate, ddMode tdd } + CRITICALITY ignore +} + +-- *** MBMSNotificationUpdate *** +mBMSNotificationUpdate NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MBMSNotificationUpdateCommand + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-mBMSNotificationUpdate, ddMode common } + CRITICALITY ignore +} + +-- *** UEStatusUpdate *** +uEStatusUpdate NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEStatusUpdateCommand + MESSAGE DISCRIMINATOR common + PROCEDURE ID { procedureCode id-uEStatusUpdate, ddMode common } + CRITICALITY ignore +} + +-- *** SecondaryULFrequencyReporting (FDD) *** +secondaryULFrequencyReportingFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SecondaryULFrequencyReport + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-secondaryULFrequencyReporting, ddMode fdd } + CRITICALITY ignore +} + +-- ***secondaryULFrequencyUpdate (FDD) +secondaryULFrequencyUpdateFDD NBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SecondaryULFrequencyUpdateIndication + MESSAGE DISCRIMINATOR dedicated + PROCEDURE ID { procedureCode id-secondaryULFrequencyUpdate, ddMode fdd } + CRITICALITY ignore +} + +END + +``` + +### 9.3.3 PDU Definitions + +``` + +-- ***** +-- +-- PDU definitions for NBAP. + +``` + +``` +-- +-- ***** + +NBAP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) nbap (2) version1 (1) nbap-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Active-Pattern-Sequence-Information, + AddorDeleteIndicator, + MIMO-withfourtransmitantennas-PilotConfiguration, + AICH-Power, + AICH-TransmissionTiming, + AllocationRetentionPriority, + AlternativeFormatReportingIndicator, + AvailabilityStatus, + ActivationDelay, + BCCH-ModificationTime, + BindingID, + BlockingPriorityIndicator, + BroadcastReference, + SCTD-Indicator, + Cause, + CCTrCH-ID, + Cell-ERNTI-Status-Information, + CellParameterID, + CellPortionID, + CellSyncBurstCode, + CellSyncBurstCodeShift, + CellSyncBurstRepetitionPeriod, + CellSyncBurstSIR, + CellSyncBurstTiming, + CellSyncBurstTimingThreshold, + CellPortion-CapabilityLCR, + CFN, + ChipOffset, + C-ID, + Closedlooptimingadjustmentmode, + CommonChannelsCapacityConsumptionLaw, + Compressed-Mode-Deactivation-Flag, + Common-MACFlows-to-DeleteFDD, + CommonMeasurementAccuracy, + CommonMeasurementType, + CommonMeasurementValue, + CommonMeasurementValueInformation, + CommonPhysicalChannelID, + CommonPhysicalChannelID768, + Common-EDCH-Capability, + Common-E-DCH-HSDPCCH-Capability, + Common-EDCH-System-InformationFDD, + Common-EDCH-System-Information-ResponseFDD, + Common-PhysicalChannel-Status-Information, + Common-PhysicalChannel-Status-Information768, + Common-TransportChannel-Status-Information, + CommonTransportChannelID, + CommonTransportChannel-InformationResponse, + CommunicationControlPortID, + ConfigurationGenerationID, + ConstantValue, + ContinuousPacketConnectivityDTX-DRX-Capability, + ContinuousPacketConnectivityDTX-DRX-Information, + ContinuousPacketConnectivityHS-SCCH-less-Capability, + ContinuousPacketConnectivityHS-SCCH-less-Information, + ContinuousPacketConnectivityHS-SCCH-less-Information-Response, + ContinuousPacketConnectivity-DRX-CapabilityLCR, + ContinuousPacketConnectivity-DRX-InformationLCR, + ContinuousPacketConnectivity-DRX-Information-ResponseLCR, + CPC-InformationLCR, +``` + +CPC-Information, +CriticalityDiagnostics, +CRNC-CommunicationContextID, +CSBMeasurementID, +CSBTransmissionID, +DCH-FDD-Information, +DCH-Indicator-For-E-DCH-HSDPA-Operation, +DCH-InformationResponse, +DCH-ID, +FDD-DCHs-to-Modify, +TDD-DCHs-to-Modify, +DCH-TDD-Information, +DedicatedChannelsCapacityConsumptionLaw, +DedicatedMeasurementType, +DedicatedMeasurementValue, +DedicatedMeasurementValueInformation, +DelayedActivation, +DelayedActivationUpdate, +DiversityControlField, +DiversityMode, +DL-DPCH-SlotFormat, +DL-DPCH-TimingAdjustment, +DL-or-Global-CapacityCredit, +DL-Power, +DL-PowerBalancing-Information, +DL-PowerBalancing-ActivationIndicator, +DLPowerAveragingWindowSize, +DL-PowerBalancing-UpdatedIndicator, +DL-ScramblingCode, +DL-TimeslotISCP, +DL-Timeslot-Information, +DL-TimeslotLCR-Information, +DL-TimeslotISCPInfo, +DL-TimeslotISCPInfoLCR, +DL-TPC-Pattern01Count, +DPC-Mode, +DPCH-ID, +DPCH-ID768, +DSCH-ID, +DSCH-InformationResponse, +DSCH-TDD-Information, +Dual-Band-Capability-Info, +DwPCH-Power, +E-AGCH-FDD-Code-Information, +E-AI-Capability, +E-DCH-Capability, +E-DCHCapacityConsumptionLaw, +E-DCH-Decoupling-Indication, +E-DCH-TTI2ms-Capability, +E-DCH-SF-Capability, +E-DCH-HARQ-Combining-Capability, +E-DCH-FDD-DL-Control-Channel-Information, +E-DCH-FDD-Information, +E-DCH-FDD-Information-Response, +E-DCH-FDD-Information-to-Modify, +E-DCH-FDD-Update-Information, +E-DCH-MACdFlow-ID, +E-DCH-MACdFlows-Information, +E-DCH-MACdFlows-to-Delete, +E-DCH-MACdPDU-SizeCapability, +E-DCH-RL-Indication, +E-DCH-Serving-Cell-Change-Info-Response, +E-DPCCH-PO, +E-RGCH-E-HICH-FDD-Code-Information, +E-RGCH-2-IndexStepThreshold, +E-RGCH-3-IndexStepThreshold, +End-Of-Audit-Sequence-Indicator, +Enhanced-FACH-Capability, +Enhanced-PCH-Capability, +Enhanced-UE-DRX-Capability, +Enhanced-UE-DRX-InformationFDD, +E-TFCS-Information, +E-TTI, +ExtendedPropagationDelay, +Fast-Reconfiguration-Mode, +Fast-Reconfiguration-Permission, +FDD-DL-ChannelisationCodeNumber, +FDD-DL-CodeInformation, + +FDD-S-CCPCH-FrameOffset, +FDD-S-CCPCH-Offset, +FDD-TPC-DownlinkStepSize, +F-DPCH-Capability, +F-DPCH-SlotFormat, +F-DPCH-SlotFormatCapability, +FirstRLS-Indicator, +FNReportingIndicator, +FPACH-Power, +FrameAdjustmentValue, +FrameHandlingPriority, +FrameOffset, +HARQ-Info-for-E-DCH, +HSDPA-Capability, +HSDSCH-Common-System-InformationFDD, +HSDSCH-Common-System-Information-ResponseFDD, +HSDSCH-Configured-Indicator, +HSDSCH-Paging-System-InformationFDD, +HSDSCH-Paging-System-Information-ResponseFDD, +HS-DSCH-Serving-Cell-Change-Info, +HS-DSCH-Serving-Cell-Change-Info-Response, +HSDSCH-MACdPDU-SizeCapability, +HS-PDSCH-FDD-Code-Information, +HS-SCCH-ID, +HS-SCCH-FDD-Code-Information, +HS-SICH-ID, +IB-OC-ID, +IB-SG-DATA, +IB-SG-POS, +IB-SG-REP, +IB-Type, +InformationExchangeID, +InformationReportCharacteristics, +InformationType, +Initial-DL-DPCH-TimingAdjustment-Allowed, +InnerLoopDLPCStatus, +IPDL-FDD-Parameters, +IPDL-TDD-Parameters, +IPDL-Indicator, +IPDL-TDD-Parameters-LCR, +IPMulticastIndication, +LimitedPowerIncrease, +Local-Cell-ID, +MaximumDL-PowerCapability, +Maximum-Target-ReceivedTotalWideBandPower, +MaximumTransmissionPower, +MaxNrOfUL-DPDCHs, +Max-Set-E-DPDCHs, +MaxPRACH-MidambleShifts, +Max-UE-DTX-Cycle, +MBMS-Capability, +MeasurementFilterCoefficient, +MeasurementID, +MeasurementRecoveryBehavior, +MeasurementRecoveryReportingIndicator, +MeasurementRecoverySupportIndicator, +MICH-CFN, +MICH-Mode, +MidambleAllocationMode, +MidambleShiftAndBurstType, +MidambleShiftAndBurstType768, +MidambleShiftLCR, +MinimumDL-PowerCapability, +MinSpreadingFactor, +MIMO-Capability, +MIMO-PilotConfiguration, +MinUL-ChannelisationCodeLength, +Modification-Period, +MultiplexingPosition, +NCyclesPerSFNperiod, +NRepetitionsPerCyclePeriod, +N-INSYNC-IND, +N-OUTSYNC-IND, +NeighbouringCellMeasurementInformation, +NeighbouringFDDCellMeasurementInformation, +NeighbouringTDDCellMeasurementInformation, +NI-Information, +NodeB-CommunicationContextID, + +Non-rectangular-resource-allocation-indicator, +Non-rectangular-resource-timeslot-set, +NotificationIndicatorLength, +NumberOfReportedCellPortions, +NumberOfReportedCellPortionsLCR, +NSubCyclesPerCyclePeriod, +PagingIndicatorLength, +Paging-MACFlows-to-DeleteFDD, +PayloadCRC-PresenceIndicator, +CCPCH-Power, +PDSCHSet-ID, +PDSCH-ID, +PDSCH-ID768, +PICH-Mode, +PICH-Power, +PLCCHInformation, +PowerAdjustmentType, +PowerOffset, +PowerRaiseLimit, +PRACH-Midamble, +PreambleSignatures, +PreambleThreshold, +PredictedSFNSFNDeviationLimit, +PredictedTUTRANGPSDeviationLimit, +PrimaryCPICH-Power, +Primary-CPICH-Usage-for-Channel-Estimation, +PrimaryScramblingCode, +PropagationDelay, +SCH-TimeSlot, +PunctureLimit, +PUSCHSet-ID, +PUSCH-ID, +QE-Selector, +RACH-SlotFormat, +RACH-SubChannelNumbers, +Reference-ReceivedTotalWideBandPower, +Reference-ReceivedTotalWideBandPowerReporting, +Reference-ReceivedTotalWideBandPowerSupportIndicator, +Maximum-Target-ReceivedTotalWideBandPower-LCR, +ReferenceClockAvailability, +ReferenceSFNOffset, +RepetitionLength, +RepetitionPeriod, +ReportCharacteristics, +RequestedDataValue, +RequestedDataValueInformation, +ResourceOperationalState, +RL-Set-ID, +RL-ID, +RL-Specific-DCH-Info, +RL-Specific-E-DCH-Info, +Received-total-wide-band-power-Value, +AdjustmentPeriod, +ScaledAdjustmentRatio, +MaxAdjustmentStep, +RNC-ID, +ScramblingCodeNumber, +Secondary-CPICH-Information-Change, +SecondaryCCPCH-SlotFormat, +Segment-Type, +Semi-PersistentScheduling-CapabilityLCR, +Serving-E-DCH-RL-ID, +SixteenQAM-UL-Capability, +SixtyfourQAM-DL-Capability, +SixtyfourQAM-DL-MIMO-Combined-Capability, +SFN, +SFNSFNChangeLimit, +SFNSFNDriftRate, +SFNSFNDriftRateQuality, +SFNSFNQuality, +ShutdownTimer, +SIB-Originator, +SpecialBurstScheduling, +SignallingBearerRequestIndicator, +Start-Of-Audit-Sequence-Indicator, +STTD-Indicator, +SSDT-SupportIndicator, +E-DPCCH-Power-Boosting-Capability, + +SyncCase, +SYNCDlCodeId, +SyncFrameNumber, +SynchronisationReportCharacteristics, +SynchronisationReportType, +Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio, +T-Cell, +T-RLFFAILURE, +TDD-ChannelisationCode, +TDD-ChannelisationCodeLCR, +TDD-ChannelisationCode768, +TDD-DL-Code-LCR-Information, +TDD-DPCHOffset, +TDD-TPC-DownlinkStepSize, +TDD-PhysicalChannelOffset, +TDD-UL-Code-LCR-Information, +TFCI-Coding, +TFCI-Presence, +TFCI-SignallingMode, +TFCS, +TimeSlot, +TimeSlotLCR, +TimeSlotDirection, +TimeSlotStatus, +TimingAdjustmentValue, +TimingAdvanceApplied, +TnlQos, +ToAWE, +ToAWS, +TransmissionDiversityApplied, +TransmitDiversityIndicator, +TransmissionGapPatternSequenceCodeInformation, +Transmission-Gap-Pattern-Sequence-Information, +TransportBearerRequestIndicator, +TransportFormatSet, +TransportLayerAddress, +TSTD-Indicator, +TUTRANGPS, +TUTRANGPSChangeLimit, +TUTRANGPSDriftRate, +TUTRANGPSDriftRateQuality, +TUTRANGPSQuality, +UARFCN, +UC-Id, +UE-Support-of-non-rectangular-resource-allocation, +USCH-Information, +USCH-InformationResponse, +UL-CapacityCredit, +UL-DPCH-SlotFormat, +UL-DPDCH-Indicator-For-E-DCH-Operation, +UL-SIR, +UL-FP-Mode, +UL-PhysCH-SF-Variation, +UL-ScramblingCode, +UL-Timeslot-Information, +UL-TimeslotLCR-Information, +UL-TimeSlot-ISCP-Info, +UL-TimeSlot-ISCP-LCR-Info, +UL-TimeslotISCP-Value, +UL-TimeslotISCP-Value-IncrDecrThres, +USCH-ID, +HSDSCH-FDD-Information, +HSDSCH-FDD-Information-Response, +HSDSCH-Information-to-Modify, +HSDSCH-Information-to-Modify-Unsynchronised, +HSDSCH-MACdFlow-ID, +HSDSCH-MACdFlows-Information, +HSDSCH-MACdFlows-to-Delete, +HSDSCH-RNTI, +HSDSCH-TDD-Information, +HSDSCH-TDD-Information-Response, +PrimaryCCPCH-RSCP, +HSDSCH-FDD-Update-Information, +HSDSCH-TDD-Update-Information, +UL-Synchronisation-Parameters-LCR, +TDD-DL-DPCH-TimeSlotFormat-LCR, +TDD-UL-DPCH-TimeSlotFormat-LCR, +TDD-TPC-UplinkStepSize-LCR, + +CellSyncBurstTimingLCR, +TimingAdjustmentValueLCR, +PrimaryCCPCH-RSCP-Delta, +SynchronisationIndicator, +TDD-UL-Code-768-Information, +UL-Timeslot768-Information, +TDD-DL-Code-768-Information, +DL-Timeslot768-Information, +E-DCH-TDD-CapacityConsumptionLaw, +E-DCH-Information, +E-DCH-Information-Response, +E-DCH-Information-Reconfig, +LTGI-Presence, +SNPL-Reporting-Type, +E-AGCH-Id, +E-HICH-TimeOffset, +Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells, +E-DCH-768-Information, +E-DCH-768-Information-Reconfig, +RTWP-ReportingIndicator, +RTWP-CellPortion-ReportingIndicator, +MAChs-ResetIndicator, +E-DCH-LCR-Information, +E-DCH-LCR-Information-Reconfig, +E-HICH-ID-TDD, +E-HICH-TimeOffsetLCR, +E-HICH-Type, +ModulationPO-MBSFN, +Secondary-CCPCH-SlotFormat-Extended, +ModulationMBSFN, +MBSFN-Only-Mode-Indicator, +MBSFN-Only-Mode-Capability, +UPPCHPositionLCR, +ControlGAP, +IdleIntervalInformation, +Extended-HS-SICH-ID, +Extended-HS-SCCH-ID, +TimeslotLCR-Extension, +Extended-E-HICH-ID-TDD, +AdditionalTimeSlotListLCR, +AdditionalMeasurementValueList, +HS-SCCH-ID-LCR, +Paging-MACFlows-to-DeleteLCR, +HSDSCH-Paging-System-InformationLCR, +HSDSCH-Paging-System-Information-ResponseLCR, +HSDSCH-Common-System-InformationLCR, +HSDSCH-Common-System-Information-ResponseLCR, +Enhanced-UE-DRX-InformationLCR, +E-DCH-MACdFlow-ID-LCR, +Common-EDCH-System-InformationLCR, +Common-EDCH-System-Information-ResponseLCR, +Common-MACFlows-to-DeleteLCR, +DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst, +E-DCH-MACdFlows-to-DeleteLCR, +HSDSCH-PreconfigurationSetup, +HSDSCH-PreconfigurationInfo, +NoOfTargetCellHS-SCCH-Order, +EnhancedHSServingCC-Abort, +GANSS-Time-ID, +HS-DSCH-FDD-Secondary-Serving-Update-Information, +HS-DSCH-Secondary-Serving-Remove, +HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised, +HS-DSCH-Secondary-Serving-Information-To-Modify, +HS-DSCH-Secondary-Serving-Cell-Change-Information-Response, +HS-DSCH-FDD-Secondary-Serving-Information-Response, +HS-DSCH-FDD-Secondary-Serving-Information, +Multi-Cell-Capability-Info, +MinimumReducedE-DPDCH-GainFactor, +IMB-Parameters, +E-RNTI, +E-DCH-Semi-PersistentScheduling-Information-LCR, +HS-DSCH-Semi-PersistentScheduling-Information-LCR, +Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext, +HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR, +E-DCH-Semi-PersistentScheduling-Information-ResponseLCR, + +HSSICH-ReferenceSignal-InformationLCR, +UE-Selected-MBMS-Service-Information, +UE-AggregateMaximumBitRate, +HSSICH-ReferenceSignal-InformationModifyLCR, +TimeSlotMeasurementValueListLCR, +MIMO-PowerOffsetForS-CPICHCapability, +MIMO-PilotConfigurationExtension, +TxDiversityOnDLControlChannelsByMIMOUECapability, +Single-Stream-MIMO-Capability, +ActivationInformation, +Cell-Capability-Container, +DormantModeIndicator, +Additional-EDCH-Setup-Info, +Additional-EDCH-Cell-Information-Response-List, +Additional-EDCH-Cell-Information-To-Add-List, +Additional-EDCH-FDD-Update-Information, +TS0-CapabilityLCR, +Out-of-Synchronization-Window, +DCH-MeasurementOccasion-Information, +Additional-EDCH-Cell-Information-Response-RLReconf-List, +Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency, +Additional-EDCH-Cell-Information-Response-RL-Add-List, +PrecodingWeightSetRestriction, +Non-Serving-RL-Preconfig-Setup, +Non-Serving-RL-Preconfig-Info, +Cell-Capability-Container-TDD-LCR, +Multi-Carrier-EDCH-Info, +Multi-Carrier-EDCH-Reconfigure, +Multi-Carrier-EDCH-Information-Response, +MU-MIMO-Capability-ContainerLCR, +MU-MIMO-InformationLCR, +MU-MIMO-Information-Response, +MU-MIMO-Information-To-ReconfigureLCR, +Adaptive-Special-Burst-Power-CapabilityLCR, +Usefulness-Of-Battery-Optimization, +In-Sync-Information-LCR, +ERNTI-Release-Status, +CellPortionLCRID, +CPC-RecoveryReport, +UL-CLTD-Information, +UL-CLTD-Information-Reconf, +UL-CLTD-State-Update-Information, +FTPICH-Information, +FTPICH-Information-Reconf, +Common-E-RGCH-InfoFDD, +Further-Enhanced-UE-DRX-InformationFDD, +Common-E-RGCH-Operation-Indicator, +DCH-ENH-Information, +DCH-ENH-Information-Reconf, +BCH-Parameters, +Radio-Links-without-DPCH-FDPCH-Indication, +UL-DPCCH2-Information, +UL-DPCCH2-Information-Reconf, +UE-Measurement-Value, +Downlink-TPC-enhancements-Information, +Downlink-TPC-enhancements-Reconf, +TPC-slot-position, +Improved-Synchronized-Indicator, +HS-SCCH-DRX-InformationFDD + +#### FROM NBAP-IEs + +PrivateIE-Container{}, +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +ProtocolIE-Single-Container{}, +ProtocolIE-ContainerList{}, +NBAP-PRIVATE-IES, +NBAP-PROTOCOL-IES, +NBAP-PROTOCOL-EXTENSION + +#### FROM NBAP-Containers + +id-Active-Pattern-Sequence-Information, +id-Additional-S-CCPCH-Parameters-CTCH-ReconfRqstTDD, +id-Additional-S-CCPCH-Parameters-CTCH-SetupRqstTDD, +id-Additional-S-CCPCH-LCR-Parameters-CTCH-ReconfRqstTDD, +id-Additional-S-CCPCH-LCR-Parameters-CTCH-SetupRqstTDD, +id-MIMO-withfourtransmitantennas-PilotConfiguration, + +id-AdjustmentRatio, +id-AICH-Information, +id-AICH-ParametersListIE-CTCH-ReconfRqstFDD, +id-AlternativeFormatReportingIndicator, +id-BCH-Information, +id-BCCH-ModificationTime, +id-bindingID, +id-BlockingPriorityIndicator, +id-BroadcastReference, +id-Cause, +id-CauseLevel-PSCH-ReconfFailure, +id-CauseLevel-RL-AdditionFailureFDD, +id-CauseLevel-RL-AdditionFailureTDD, +id-CauseLevel-RL-ReconfFailure, +id-CauseLevel-RL-SetupFailureFDD, +id-CauseLevel-RL-SetupFailureTDD, +id-CauseLevel-SyncAdjustmntFailureTDD, +id-CCP-InformationItem-AuditRsp, +id-CCP-InformationList-AuditRsp, +id-CCP-InformationItem-ResourceStatusInd, +id-CCTrCH-InformationItem-RL-FailureInd, +id-CCTrCH-InformationItem-RL-RestoreInd, +id-CCTrCH-Initial-DL-Power-RL-AdditionRqstTDD, +id-CCTrCH-Initial-DL-Power-RL-ReconfPrepTDD, +id-CCTrCH-Initial-DL-Power-RL-SetupRqstTDD, +id-CellAdjustmentInfo-SyncAdjustmntRqstTDD, +id-CellAdjustmentInfoItem-SyncAdjustmentRqstTDD, +id-Cell-ERNTI-Status-Information, +id-Cell-InformationItem-AuditRsp, +id-Cell-InformationItem-ResourceStatusInd, +id-Cell-InformationList-AuditRsp, +id-CellParameterID, +id-CellPortion-InformationItem-Cell-SetupRqstFDD, +id-CellPortion-InformationList-Cell-SetupRqstFDD, +id-CellPortion-InformationItem-Cell-ReconfRqstFDD, +id-CellPortion-InformationList-Cell-ReconfRqstFDD, +id-CellSyncBurstTransInit-CellSyncInitiationRqstTDD, +id-CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD, +id-CellSyncBurstRepetitionPeriod, +id-CellSyncBurstTransReconfiguration-CellSyncReconfRqstTDD, +id-CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD, +id-CellSyncBurstMeasReconfiguration-CellSyncReconfRqstTDD, +id-CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD, +id-CellSyncBurstInfoList-CellSyncReconfRqstTDD, +id-CellSyncInfo-CellSyncReprtTDD, +id-CellPortion-CapabilityLCR, +id-CFN, +id-CFNReportingIndicator, +id-C-ID, +id-Closed-Loop-Timing-Adjustment-Mode, +id-Common-EDCH-Capability, +id-Common-E-DCH-HSDPCCH-Capability, +id-Common-EDCH-MACdFlows-to-DeleteFDD, +id-Common-EDCH-System-InformationFDD, +id-Common-EDCH-System-Information-ResponseFDD, +id-Common-MACFlows-to-DeleteFDD, +id-CommonMeasurementAccuracy, +id-CommonMeasurementObjectType-CM-Rprt, +id-CommonMeasurementObjectType-CM-Rqst, +id-CommonMeasurementObjectType-CM-Rsp, +id-CommonMeasurementType, +id-CommonPhysicalChannelID, +id-CommonPhysicalChannelType-CTCH-ReconfRqstFDD, +id-CommonPhysicalChannelType-CTCH-SetupRqstFDD, +id-CommonPhysicalChannelType-CTCH-SetupRqstTDD, +id-Common-UL-MACFlows-to-DeleteFDD, +id-CommunicationContextInfoItem-Reset, +id-CommunicationControlPortID, +id-CommunicationControlPortInfoItem-Reset, +id-Compressed-Mode-Deactivation-Flag, +id-ConfigurationGenerationID, +id-ContinuousPacketConnectivityDTX-DRX-Capability, +id-ContinuousPacketConnectivityDTX-DRX-Information, +id-ContinuousPacketConnectivityHS-SCCH-less-Capability, +id-ContinuousPacketConnectivityHS-SCCH-less-Information, +id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response, +id-ContinuousPacketConnectivity-DRX-CapabilityLCR, +id-ContinuousPacketConnectivity-DRX-InformationLCR, + +id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR, +id-CPC-InformationLCR, +id-CPC-Information, +id-CRNC-CommunicationContextID, +id-CriticalityDiagnostics, +id-CSBTransmissionID, +id-CSBMeasurementID, +id-DCHs-to-Add-FDD, +id-DCHs-to-Add-TDD, +id-DCH-AddList-RL-ReconfPrepTDD, +id-DCH-DeleteList-RL-ReconfPrepFDD, +id-DCH-DeleteList-RL-ReconfPrepTDD, +id-DCH-DeleteList-RL-ReconfRqstFDD, +id-DCH-DeleteList-RL-ReconfRqstTDD, +id-DCH-FDD-Information, +id-DCH-TDD-Information, +id-DCH-Indicator-For-E-DCH-HSDPA-Operation, +id-DCH-InformationResponse, +id-DCH-RearrangeList-Bearer-RearrangeInd, +id-DSCH-RearrangeList-Bearer-RearrangeInd, +id-FDD-DCHs-to-Modify, +id-FDD-S-CCPCH-FrameOffset-CTCH-SetupRqstFDD, +id-TDD-DCHs-to-Modify, +id-DedicatedMeasurementObjectType-DM-Rprt, +id-DedicatedMeasurementObjectType-DM-Rqst, +id-DedicatedMeasurementObjectType-DM-Rsp, +id-DedicatedMeasurementType, +id-DelayedActivation, +id-DelayedActivationList-RL-ActivationCmdFDD, +id-DelayedActivationList-RL-ActivationCmdTDD, +id-DelayedActivationInformation-RL-ActivationCmdFDD, +id-DelayedActivationInformation-RL-ActivationCmdTDD, +id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD, +id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD, +id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD, +id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD, +id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD, +id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD, +id-DL-CCTrCH-InformationList-RL-SetupRqstTDD, +id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD, +id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD, +id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD, +id-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD, +id-DL-DPCH-InformationItem-RL-AdditionRqstTDD, +id-DL-DPCH-InformationList-RL-SetupRqstTDD, +id-DL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD, +id-DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD, +id-DL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD, +id-DL-DPCH-Information-RL-ReconfPrepFDD, +id-DL-DPCH-Information-RL-ReconfRqstFDD, +id-DL-DPCH-Information-RL-SetupRqstFDD, +id-DL-DPCH-TimingAdjustment, +id-DL-DPCH-Power-Information-RL-ReconfPrepFDD, +id-DL-PowerBalancing-Information, +id-DL-PowerBalancing-ActivationIndicator, +id-DL-ReferencePowerInformationItem-DL-PC-Rqst, +id-DL-PowerBalancing-UpdatedIndicator, +id-DLReferencePower, +id-DLReferencePowerList-DL-PC-Rqst, +id-DL-TPC-Pattern01Count, +id-DPC-Mode, +id-DPCHConstant, +id-DSCHs-to-Add-TDD, +id-DSCH-Information-DeleteList-RL-ReconfPrepTDD, +id-DSCH-Information-ModifyList-RL-ReconfPrepTDD, +id-DSCH-InformationResponse, +id-DSCH-TDD-Information, +id-Dual-Band-Capability-Info, +id-E-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code, +id-E-AI-Capability, +id-E-AGCH-FDD-Code-Information, +id-E-DCH-Capability, +id-E-DCH-Decoupling-Indication, +id-E-DCH-TTI2ms-Capability, +id-E-DCH-SF-Capability, +id-E-DCH-HARQ-Combining-Capability, +id-E-DCH-FDD-DL-Control-Channel-Information, +id-E-DCH-FDD-Information, + +id-E-DCH-FDD-Information-Response, +id-E-DCH-FDD-Information-to-Modify, +id-E-DCH-FDD-Update-Information, +id-E-DCH-MACdFlows-to-Add, +id-E-DCH-MACdFlows-to-Delete, +id-E-DCH-RearrangeList-Bearer-RearrangeInd, +id-E-DCH-Resources-Information-AuditRsp, +id-E-DCH-Resources-Information-ResourceStatusInd, +id-E-DCH-RL-Indication, +id-E-DCH-RL-Set-ID, +id-E-DCH-Serving-Cell-Change-Info-Response, +id-E-DCH-CapacityConsumptionLaw, +id-E-DPCH-Information-RL-ReconfPrepFDD, +id-E-DPCH-Information-RL-ReconfRqstFDD, +id-E-DPCH-Information-RL-SetupRqstFDD, +id-E-DPCH-Information-RL-AdditionReqFDD, +id-E-RGCH-E-HICH-FDD-Code-Information, +id-ERACH-CM-Rqst, +id-ERACH-CM-Rsp, +id-ERACH-CM-Rprt, +id-End-Of-Audit-Sequence-Indicator, +id-Enhanced-FACH-Capability, +id-Enhanced-PCH-Capability, +id-Enhanced-UE-DRX-Capability, +id-Enhanced-UE-DRX-InformationFDD, +id-ExtendedPropagationDelay, +id-FACH-Information, +id-FACH-ParametersList-CTCH-ReconfRqstTDD, +id-FACH-ParametersList-CTCH-SetupRsp, +id-FACH-ParametersListIE-CTCH-ReconfRqstFDD, +id-FACH-ParametersListIE-CTCH-SetupRqstFDD, +id-FACH-ParametersListIE-CTCH-SetupRqstTDD, +id-Fast-Reconfiguration-Mode, +id-Fast-Reconfiguration-Permission, +id-F-DPCH-Capability, +id-F-DPCH-Information-RL-ReconfPrepFDD, +id-F-DPCH-Information-RL-SetupRqstFDD, +id-F-DPCH-SlotFormat, +id-F-DPCH-SlotFormatCapability, +id-HSDPA-And-EDCH-CellPortion-Information-PSCH-ReconfRqst, +id-HSDSCH-Configured-Indicator, +id-HS-DSCH-Serving-Cell-Change-Info, +id-HS-DSCH-Serving-Cell-Change-Info-Response, +id-IndicationType-ResourceStatusInd, +id-InformationExchangeID, +id-InformationExchangeObjectType-InfEx-Rqst, +id-InformationExchangeObjectType-InfEx-Rsp, +id-InformationExchangeObjectType-InfEx-Rprt, +id-InformationReportCharacteristics, +id-InformationType, +id-InitDL-Power, +id-Initial-DL-DPCH-TimingAdjustment, +id-Initial-DL-DPCH-TimingAdjustment-Allowed, +id-InnerLoopDLPCStatus, +id-IntStdPhCellSyncInfoItem-CellSyncReprtTDD, +id-IPDLParameter-Information-Cell-ReconfRqstFDD, +id-IPDLParameter-Information-Cell-SetupRqstFDD, +id-IPDLParameter-Information-Cell-ReconfRqstTDD, +id-IPDLParameter-Information-Cell-SetupRqstTDD, +id-IPMulticastIndication, +id-LateEntranceCellSyncInfoItem-CellSyncReprtTDD, +id-Limited-power-increase-information-Cell-SetupRqstFDD, +id-Local-Cell-ID, +id-Local-Cell-Group-InformationItem-AuditRsp, +id-Local-Cell-Group-InformationItem-ResourceStatusInd, +id-Local-Cell-Group-InformationItem2-ResourceStatusInd, +id-Local-Cell-Group-InformationList-AuditRsp, +id-Local-Cell-InformationItem-AuditRsp, +id-Local-Cell-InformationItem-ResourceStatusInd, +id-Local-Cell-InformationItem2-ResourceStatusInd, +id-Local-Cell-InformationList-AuditRsp, +id-AdjustmentPeriod, +id-MaxAdjustmentStep, +id-MaximumTransmissionPower, +id-Max-UE-DTX-Cycle, +id-MeasurementFilterCoefficient, +id-MeasurementID, +id-MeasurementRecoveryBehavior, + +id-MeasurementRecoveryReportingIndicator, +id-MeasurementRecoverySupportIndicator, +id-MIB-SB-SIB-InformationList-SystemInfoUpdateRqst, +id-MBMS-Capability, +id-MICH-CFN, +id-MICH-Information-AuditRsp, +id-MICH-Information-ResourceStatusInd, +id-MICH-Parameters-CTCH-ReconfRqstFDD, +id-MICH-Parameters-CTCH-ReconfRqstTDD, +id-MICH-Parameters-CTCH-SetupRqstFDD, +id-MICH-Parameters-CTCH-SetupRqstTDD, +id-MIMO-Capability, +id-MIMO-PilotConfiguration, +id-Modification-Period, +id-multipleRL-dl-DPCH-InformationList, +id-multipleRL-dl-DPCH-InformationModifyList, +id-multipleRL-dl-CCTrCH-InformationModifyList-RL-ReconfRqstTDD, +id-multiple-RL-Information-RL-ReconfPrepTDD, +id-multiple-RL-Information-RL-ReconfRqstTDD, +id-multipleRL-ul-DPCH-InformationList, +id-multipleRL-ul-DPCH-InformationModifyList, +id-NCyclesPerSFNperiod, +id-NeighbouringCellMeasurementInformation, +id-NI-Information-NotifUpdateCmd, +id-NodeB-CommunicationContextID, +id-Non-rectangular-resource-allocation-indicator, +id-Non-rectangular-resource-timeslot-set, +id-NRepetitionsPerCyclePeriod, +id-NumberOfReportedCellPortions, +id-NumberOfReportedCellPortionsLCR, +id-Paging-MACFlows-to-DeleteFDD, +id-P-CCPCH-Information, +id-P-CPICH-Information, +id-P-SCH-Information, +id-PCPCH-Information-Cell-ReconfRqstTDD, +id-PCPCH-Information-Cell-SetupRqstTDD, +id-PCH-Parameters-CTCH-ReconfRqstTDD, +id-PCH-Parameters-CTCH-SetupRsp, +id-PCH-ParametersItem-CTCH-ReconfRqstFDD, +id-PCH-ParametersItem-CTCH-SetupRqstFDD, +id-PCH-ParametersItem-CTCH-SetupRqstTDD, +id-PCH-Information, +id-PICH-ParametersItem-CTCH-ReconfRqstFDD, +id-PDSCH-Information-AddListIE-PSCH-ReconfRqst, +id-PDSCH-Information-ModifyListIE-PSCH-ReconfRqst, +id-PDSCH-RL-ID, +id-PDSCH-Timeslot-Format-PSCH-ReconfRqst-LCR, +id-PDSCHSets-AddList-PSCH-ReconfRqst, +id-PDSCHSets-DeleteList-PSCH-ReconfRqst, +id-PDSCHSets-ModifyList-PSCH-ReconfRqst, +id-PICH-Information, +id-PICH-Parameters-CTCH-ReconfRqstTDD, +id-PICH-ParametersItem-CTCH-SetupRqstTDD, +id-PLCCH-Information-AuditRsp, +id-PLCCH-Information-ResourceStatusInd, +id-PLCCH-Information-RL-ReconfPrepTDDLCR, +id-PLCCH-InformationList-AuditRsp, +id-PLCCH-InformationList-ResourceStatusInd, +id-PLCCH-Parameters-CTCH-ReconfRqstTDD, +id-PowerAdjustmentType, +id-Power-Local-Cell-Group-choice-CM-Rqst, +id-Power-Local-Cell-Group-choice-CM-Rsp, +id-Power-Local-Cell-Group-choice-CM-Rprt, +id-Power-Local-Cell-Group-InformationItem-AuditRsp, +id-Power-Local-Cell-Group-InformationItem-ResourceStatusInd, +id-Power-Local-Cell-Group-InformationItem2-ResourceStatusInd, +id-Power-Local-Cell-Group-InformationList-AuditRsp, +id-Power-Local-Cell-Group-InformationList-ResourceStatusInd, +id-Power-Local-Cell-Group-InformationList2-ResourceStatusInd, +id-Power-Local-Cell-Group-ID, +id-PRACH-Information, +id-PRACHConstant, +id-PRACH-ParametersItem-CTCH-SetupRqstTDD, +id-PRACH-ParametersListIE-CTCH-ReconfRqstFDD, +id-PrimaryCCPCH-Information-Cell-ReconfRqstFDD, +id-PrimaryCCPCH-Information-Cell-SetupRqstFDD, +id-PrimaryCPICH-Information-Cell-ReconfRqstFDD, +id-PrimaryCPICH-Information-Cell-SetupRqstFDD, + +id-Primary-CPICH-Usage-for-Channel-Estimation, +id-PrimarySCH-Information-Cell-ReconfRqstFDD, +id-PrimarySCH-Information-Cell-SetupRqstFDD, +id-PrimaryScramblingCode, +id-SCH-Information-Cell-ReconfRqstTDD, +id-SCH-Information-Cell-SetupRqstTDD, +id-PUSCH-Information-AddListIE-PSCH-ReconfRqst, +id-PUSCH-Information-ModifyListIE-PSCH-ReconfRqst, +id-PUSCH-Timeslot-Format-PSCH-ReconfRqst-LCR, +id-PUSCHConstant, +id-PUSCHSets-AddList-PSCH-ReconfRqst, +id-PUSCHSets-DeleteList-PSCH-ReconfRqst, +id-PUSCHSets-ModifyList-PSCH-ReconfRqst, +id-RACH-Information, +id-RACH-Parameters-CTCH-SetupRsp, +id-RACH-ParametersItem-CTCH-SetupRqstFDD, +id-RACH-ParameterItem-CTCH-SetupRqstTDD, +id-ReferenceClockAvailability, +id-ReferenceSFNOffset, +id-ReportCharacteristics, +id-Reporting-Object-RL-FailureInd, +id-Reporting-Object-RL-RestoreInd, +id-ResetIndicator, +id-RL-ID, +id-RL-InformationItem-DM-Rprt, +id-RL-InformationItem-DM-Rqst, +id-RL-InformationItem-DM-Rsp, +id-RL-InformationItem-RL-AdditionRqstFDD, +id-RL-InformationItem-RL-DeletionRqst, +id-RL-InformationItem-RL-FailureInd, +id-RL-InformationItem-RL-PreemptRequiredInd, +id-RL-InformationItem-RL-ReconfPrepFDD, +id-RL-InformationItem-RL-ReconfRqstFDD, +id-RL-InformationItem-RL-RestoreInd, +id-RL-InformationItem-RL-SetupRqstFDD, +id-RL-InformationList-RL-AdditionRqstFDD, +id-RL-InformationList-RL-DeletionRqst, +id-RL-InformationList-RL-PreemptRequiredInd, +id-RL-InformationList-RL-ReconfPrepFDD, +id-RL-InformationList-RL-ReconfRqstFDD, +id-RL-InformationList-RL-SetupRqstFDD, +id-RL-InformationResponseItem-RL-AdditionRspFDD, +id-RL-InformationResponseItem-RL-ReconfReady, +id-RL-InformationResponseItem-RL-ReconfRsp, +id-RL-InformationResponseItem-RL-SetupRspFDD, +id-RL-InformationResponseList-RL-AdditionRspFDD, +id-RL-InformationResponseList-RL-ReconfReady, +id-RL-InformationResponseList-RL-ReconfRsp, +id-RL-InformationResponseList-RL-SetupRspFDD, +id-RL-InformationResponse-RL-AdditionRspTDD, +id-RL-InformationResponse-RL-SetupRspTDD, +id-RL-Information-RL-AdditionRqstTDD, +id-RL-Information-RL-ReconfRqstTDD, +id-RL-Information-RL-ReconfPrepTDD, +id-RL-Information-RL-SetupRqstTDD, +id-RL-ReconfigurationFailureItem-RL-ReconfFailure, +id-RL-Set-InformationItem-DM-Rprt, +id-RL-Set-InformationItem-DM-Rsp, +id-RL-Set-InformationItem-RL-FailureInd, +id-RL-Set-InformationItem-RL-RestoreInd, +id-RL-Specific-DCH-Info, +id-RL-Specific-E-DCH-Info, +id-S-CCPCH-Information, +id-S-CCPCH-InformationListExt-AuditRsp, +id-S-CCPCH-InformationListExt-ResourceStatusInd, +id-S-CCPCH-LCR-InformationListExt-AuditRsp, +id-S-CCPCH-LCR-InformationListExt-ResourceStatusInd, +id-S-CPICH-Information, +id-SCH-Information, +id-S-SCH-Information, +id-Secondary-CCPCHListIE-CTCH-ReconfRqstTDD, +id-Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD, +id-Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD, +id-Secondary-CPICH-Information, +id-SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD, +id-SecondaryCPICH-InformationItem-Cell-SetupRqstFDD, +id-SecondaryCPICH-InformationList-Cell-ReconfRqstFDD, +id-SecondaryCPICH-InformationList-Cell-SetupRqstFDD, + +id-Secondary-CPICH-Information-Change, +id-SecondarySCH-Information-Cell-ReconfRqstFDD, +id-SecondarySCH-Information-Cell-SetupRqstFDD, +id-Semi-PersistentScheduling-CapabilityLCR, +id-SegmentInformationListIE-SystemInfoUpdate, +id-Serving-Cell-Change-CFN, +id-Serving-E-DCH-RL-ID, +id-SixteenQAM-UL-Capability, +id-SixtyfourQAM-DL-Capability, +id-SixtyfourQAM-DL-MIMO-Combined-Capability, +id-SFN, +id-SFNReportingIndicator, +id-ShutdownTimer, +id-SignallingBearerRequestIndicator, +id-Start-Of-Audit-Sequence-Indicator, +id-Successful-RL-InformationRespItem-RL-AdditionFailureFDD, +id-Successful-RL-InformationRespItem-RL-SetupFailureFDD, +id-E-DPCH-Power-Boosting-Capability, +id-Synchronisation-Configuration-Cell-ReconfRqst, +id-Synchronisation-Configuration-Cell-SetupRqst, +id-SyncCase, +id-SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH, +id-SyncFrameNumber, +id-SynchronisationReportType, +id-SynchronisationReportCharacteristics, +id-SyncReportType-CellSyncReprtTDD, +id-T-Cell, +id-TargetCommunicationControlPortID, +id-Transmission-Gap-Pattern-Sequence-Information, +id-TimeSlotConfigurationList-Cell-ReconfRqstTDD, +id-TimeSlotConfigurationList-Cell-SetupRqstTDD, +id-timeslotInfo-CellSyncInitiationRqstTDD, +id-TimeslotISCPInfo, +id-TimingAdvanceApplied, +id-TnlQos, +id-TransmissionDiversityApplied, +id-transportlayeraddress, +id-Tstd-indicator, +id-UARFCNforNt, +id-UARFCNforNd, +id-UARFCNforNu, +id-UE-Support-of-non-rectangular-resource-allocation, +id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD, +id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD, +id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD, +id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD, +id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD, +id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD, +id-UL-CCTrCH-InformationList-RL-SetupRqstTDD, +id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD, +id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD, +id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD, +id-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD, +id-UL-DPCH-InformationItem-RL-AdditionRqstTDD, +id-UL-DPCH-InformationList-RL-SetupRqstTDD, +id-UL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD, +id-UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD, +id-UL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD, +id-UL-DPCH-Information-RL-ReconfPrepFDD, +id-UL-DPCH-Information-RL-ReconfRqstFDD, +id-UL-DPCH-Information-RL-SetupRqstFDD, +id-UL-DPDCH-Indicator-For-E-DCH-Operation, +id-Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD, +id-Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD, +id-Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD, +id-Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD, +id-Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD, +id-Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD, +id-Unsuccessful-RL-InformationResp-RL-SetupFailureTDD, +id-USCH-Information-Add, +id-USCH-Information-DeleteList-RL-ReconfPrepTDD, +id-USCH-Information-ModifyList-RL-ReconfPrepTDD, +id-USCH-InformationResponse, +id-USCH-Information, +id-USCH-RearrangeList-Bearer-RearrangeInd, +id-DL-DPCH-LCR-Information-RL-SetupRqstTDD, +id-DwPCH-LCR-Information , +id-DwPCH-LCR-InformationList-AuditRsp, + +id-DwPCH-LCR-Information-Cell-SetupRqstTDD, +id-DwPCH-LCR-Information-Cell-ReconfRqstTDD, +id-DwPCH-LCR-Information-ResourceStatusInd, +id-maxFACH-Power-LCR-CTCH-SetupRqstTDD, +id-maxFACH-Power-LCR-CTCH-ReconfRqstTDD, +id-FPACH-LCR-Information, +id-FPACH-LCR-Information-AuditRsp, +id-FPACH-LCR-InformationList-AuditRsp, +id-FPACH-LCR-InformationList-ResourceStatusInd, +id-FPACH-LCR-Parameters-CTCH-SetupRqstTDD, +id-FPACH-LCR-Parameters-CTCH-ReconfRqstTDD, +id-PCPCH-LCR-Information-Cell-SetupRqstTDD, +id-PCH-Power-LCR-CTCH-SetupRqstTDD, +id-PCH-Power-LCR-CTCH-ReconfRqstTDD, +id-PICH-LCR-Parameters-CTCH-SetupRqstTDD, +id-PRACH-LCR-ParametersList-CTCH-SetupRqstTDD, +id-RL-InformationResponse-LCR-RL-SetupRspTDD , +id-Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD, +id-TimeSlot, +id-TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD, +id-TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD, +id-TimeslotISCP-LCR-InfoList-RL-SetupRqstTDD, +id-TimeSlotLCR-CM-Rqst, +id-UL-DPCH-LCR-Information-RL-SetupRqstTDD, +id-DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD, +id-UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD, +id-TimeslotISCP-InformationList-LCR-RL-AdditionRqstTDD, +id-DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD, +id-DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD, +id-DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD, +id-TimeslotISCPInfoList-LCR-DL-PC-RqstTDD, +id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfPrepTDD, +id-UL-DPCH-LCR-InformationModify-AddList, +id-UL-TimeslotLCR-Information-RL-ReconfPrepTDD, +id-UL-SIRTarget, +id-PDSCH-AddInformation-LCR-PSCH-ReconfRqst, +id-PDSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst, +id-PDSCH-ModifyInformation-LCR-PSCH-ReconfRqst, +id-PDSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst, +id-PUSCH-AddInformation-LCR-PSCH-ReconfRqst, +id-PUSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst, +id-PUSCH-ModifyInformation-LCR-PSCH-ReconfRqst, +id-PUSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst, +id-PUSCH-Info-DM-Rqst, +id-PUSCH-Info-DM-Rsp, +id-PUSCH-Info-DM-Rprt, +id-RL-InformationResponse-LCR-RL-AdditionRspTDD, +id-IPDLParameter-Information-LCR-Cell-SetupRqstTDD, +id-IPDLParameter-Information-LCR-Cell-ReconfRqstTDD, +id-HS-PDSCH-HS-SCCH-E-AGCH-E-RGCH-E-HICH-MaxPower-PSCH-ReconfRqst, +id-HS-PDSCH-HS-SCCH-ScramblingCode-PSCH-ReconfRqst, +id-HS-PDSCH-FDD-Code-Information-PSCH-ReconfRqst, +id-HS-SCCH-FDD-Code-Information-PSCH-ReconfRqst, +id-HS-PDSCH-TDD-Information-PSCH-ReconfRqst, +id-Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst, +id-Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst, +id-Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst, +id-SYNCdlCodeId-TransInitLCR-CellSyncInitiationRqstTDD, +id-SYNCdlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD, +id-SYNCdlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD, +id-SYNCdlCodeIdMeasReconfigurationLCR-CellSyncReconfRqstTDD, +id-SYNCdlCodeIdMeasInfoList-CellSyncReconfRqstTDD, +id-SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD, +id-NSubCyclesPerCyclePeriod-CellSyncReconfRqstTDD, +id-DwPCH-Power, +id-AccumulatedClockupdate-CellSyncReprtTDD, +id-HSDPA-Capability, +id-HSDSCH-FDD-Information, +id-HSDSCH-Common-System-InformationFDD, +id-HSDSCH-Common-System-Information-ResponseFDD, +id-HSDSCH-FDD-Information-Response, +id-HSDSCH-Information-to-Modify, +id-HSDSCH-Information-to-Modify-Unsynchronised, +id-HSDSCH-MACdFlows-to-Add, +id-HSDSCH-MACdFlows-to-Delete, +id-HSDSCH-Paging-System-InformationFDD, +id-HSDSCH-Paging-System-Information-ResponseFDD, +id-HSDSCH-RearrangeList-Bearer-RearrangeInd, + +id-HSDSCH-Resources-Information-AuditRsp, +id-HSDSCH-Resources-Information-ResourceStatusInd, +id-HSDSCH-RNTI, +id-HSDSCH-TDD-Information, +id-HSDSCH-TDD-Information-Response, +id-HSPDSCH-RL-ID, +id-HSSICH-Info-DM-Rprt, +id-HSSICH-Info-DM-Rqst, +id-HSSICH-Info-DM-Rsp, +id-PrimCCPCH-RSCP-DL-PC-RqstTDD, +id-HSDSCH-FDD-Update-Information, +id-HSDSCH-TDD-Update-Information, +id-UL-Synchronisation-Parameters-LCR, +id-DL-DPCH-TimeslotFormat-LCR-ModifyItem-RL-ReconfPrepTDD, +id-UL-DPCH-TimeslotFormat-LCR-ModifyItem-RL-ReconfPrepTDD, +id-CCTrCH-Maximum-DL-Power-RL-SetupRqstTDD, +id-CCTrCH-Minimum-DL-Power-RL-SetupRqstTDD, +id-CCTrCH-Maximum-DL-Power-RL-AdditionRqstTDD, +id-CCTrCH-Minimum-DL-Power-RL-AdditionRqstTDD, +id-CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD, +id-CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD, +id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD, +id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD, +id-Maximum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD, +id-Minimum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD, +id-DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD, +id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfRqstTDD, +id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfRqstTDD, +id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD, +id-TDD-TPC-UplinkStepSize-LCR-RL-AdditionRqstTDD, +id-TDD-TPC-DownlinkStepSize-RL-AdditionRqstTDD, +id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD, +id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD, +id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD, +id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD, +id-TimeslotISCP-LCR-InfoList-RL-ReconfPrepTDD, +id-TimingAdjustmentValueLCR, +id-PrimaryCCPCH-RSCP-Delta, +id-Maximum-Target-ReceivedTotalWideBandPower, +id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp, +id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp, +id-SynchronisationIndicator, +id-Reference-ReceivedTotalWideBandPower, +id-Reference-ReceivedTotalWideBandPowerReporting, +id-Reference-ReceivedTotalWideBandPowerSupportIndicator, +id-Maximum-Target-ReceivedTotalWideBandPower-LCR, +id-multiple-PUSCH-InfoList-DM-Rsp, +id-multiple-PUSCH-InfoList-DM-Rprt, +id-Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio, +id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp, +id-PCPCH-768-Information-Cell-SetupRqstTDD, +id-SCH-768-Information-Cell-SetupRqstTDD, +id-SCH-768-Information-Cell-ReconfRqstTDD, +id-PCPCH-768-Information-Cell-ReconfRqstTDD, +id-P-CCPCH-768-Information-AuditRsp, +id-PICH-768-Information-AuditRsp, +id-PRACH-768-InformationList-AuditRsp, +id-SCH-768-Information-AuditRsp, +id-MICH-768-Information-AuditRsp, +id-CommonPhysicalChannelID768-CommonTrChDeletionReq, +id-MICH-768-Parameters-CTCH-ReconfRqstTDD, +id-PICH-768-Parameters-CTCH-SetupRqstTDD, +id-PICH-768-Parameters-CTCH-ReconfRqstTDD, +id-PRACH-768-Parameters-CTCH-SetupRqstTDD, +id-S-CCPCH-768-InformationList-AuditRsp, +id-S-CCPCH-768-Information-AuditRsp, +id-S-CCPCH-768-Parameters-CTCH-SetupRqstTDD, +id-S-CCPCH-768-Parameters-CTCH-ReconfRqstTDD, +id-S-CCPCH-768-Information-ResourceStatusInd, +id-P-CCPCH-768-Information-ResourceStatusInd, +id-PICH-768-Information-ResourceStatusInd, +id-PRACH-768-InformationList-ResourceStatusInd, +id-SCH-768-Information-ResourceStatusInd, +id-MICH-768-Information-ResourceStatusInd, +id-S-CCPCH-768-InformationList-ResourceStatusInd, +id-PRACH-768-Information, +id-UL-DPCH-768-Information-RL-SetupRqstTDD, +id-DL-DPCH-768-Information-RL-SetupRqstTDD, + +id-DL-DPCH-InformationItem-768-RL-AdditionRqstTDD, +id-UL-DPCH-InformationItem-768-RL-AdditionRqstTDD, +id-UL-DPCH-768-InformationAddItemIE-RL-ReconfPrepTDD, +id-UL-DPCH-768-InformationAddListIE-RL-ReconfPrepTDD, +id-UL-DPCH-768-InformationModify-AddItem, +id-UL-DPCH-768-InformationModify-AddList, +id-UL-Timeslot768-Information-RL-ReconfPrepTDD, +id-DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD, +id-DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD, +id-DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD, +id-DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD, +id-DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD, +id-DPCH-ID768-DM-Rqst, +id-multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp, +id-DPCH-ID768-DM-Rsp, +id-DPCH-ID768-DM-Rprt, +id-PDSCH-AddInformation-768-PSCH-ReconfRqst, +id-PDSCH-ModifyInformation-768-PSCH-ReconfRqst, +id-PUSCH-AddInformation-768-PSCH-ReconfRqst, +id-PUSCH-ModifyInformation-768-PSCH-ReconfRqst, +id-dL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst, +id-hS-SCCH-Information-768-PSCH-ReconfRqst, +id-hS-SCCH-InformationModify-768-PSCH-ReconfRqst, +id-tFCI-Presence, +id-E-RUCCH-InformationList-AuditRsp, +id-E-RUCCH-InformationList-ResourceStatusInd, +id-E-RUCCH-Information, +id-E-DCH-Information, +id-E-DCH-Information-Response, +id-E-DCH-Information-Reconfig, +id-E-PUCH-Information-PSCH-ReconfRqst, +id-Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst, +id-Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst, +id-Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst, +id-E-HICH-Information-PSCH-ReconfRqst, +id-E-DCH-TDD-CapacityConsumptionLaw, +id-E-HICH-TimeOffset, +id-Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells, +id-E-DCH-Serving-RL-ID, +id-E-RUCCH-768-InformationList-AuditRsp, +id-E-RUCCH-768-InformationList-ResourceStatusInd, +id-E-RUCCH-768-Information, +id-E-DCH-768-Information, +id-E-DCH-768-Information-Reconfig, +id-E-PUCH-Information-768-PSCH-ReconfRqst, +id-Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst, +id-Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst, +id-E-HICH-Information-768-PSCH-ReconfRqst, +id-RTWP-ReportingIndicator, +id-RTWP-CellPortion-ReportingIndicator, +id-Received-Scheduled-EDCH-Power-Share-Value, +id-Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value, +id-Received-Scheduled-EDCH-Power-Share, +id-Received-Scheduled-EDCH-Power-Share-For-CellPortion, +id-ueCapability-Info, +id-MACHs-ResetIndicator, +id-SYNC-UL-Partition-LCR, +id-E-DCH-LCR-Information, +id-E-DCH-LCR-Information-Reconfig, +id-E-PUCH-Information-LCR-PSCH-ReconfRqst, +id-Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst, +id-E-HICH-TimeOffsetLCR, +id-HSDSCH-MACdPDU-SizeCapability, +id-ModulationPO-MBSFN, +id-Secondary-CCPCH-SlotFormat-Extended, +id-MBSFN-Only-Mode-Indicator-Cell-SetupRqstTDD-LCR, +id-Time-Slot-Parameter-ID, +id-MBSFN-Only-Mode-Capability, +id-MBSFN-Cell-ParameterID-Cell-SetupRqstTDD, +id-MBSFN-Cell-ParameterID-Cell-ReconfRqstTDD, +id-S-CCPCH-Modulation, +id-TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD, +id-Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp, +id-Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp, + +id-Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD, +id-UARFCN-Adjustment, +id-Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd, +id-Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd, +id-UPPCHPositionLCR, +id-UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD, +id-UPPCH-LCR-InformationList-AuditRsp, +id-UPPCH-LCR-InformationItem-AuditRsp, +id-UPPCH-LCR-InformationList-ResourceStatusInd, +id-UPPCH-LCR-InformationItem-ResourceStatusInd, +id-multipleFreq-dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst, +id-multipleFreq-HS-DSCH-Resources-InformationList-AuditRsp, +id-multipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd, +id-UARFCNSpecificCauseList, id-Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD, +id-MultipleFreq-dL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst, +id-Extended-HS-SCCH-ID, +id-Extended-HS-SICH-ID, +id-HSSICH-InfoExt-DM-Rqst, +id-Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst, +id-HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst, +id-HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst, +id-PowerControlGAP, +id-PowerControlGAP-For-CellFACHLCR, +id-IdleIntervalInformation, +id-MBSFN-SpecialTimeslot-LCR, +id-MultipleFreq-E-DCH-Resources-InformationList-AuditRsp, +id-MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd, +id-MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst, +id-MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst, +id-Extended-E-HICH-ID-TDD, +id-E-DCH-MACdPDU-SizeCapability, +id-E-HICH-TimeOffset-Extension, +id-MultipleFreq-E-HICH-TimeOffsetLCR, +id-PLCH-parameters, +id-E-RUCCH-parameters, +id-E-RUCCH-768-parameters, +id-HS-Cause, +id-E-Cause, +id-AdditionalTimeslotListLCR, +id-AdditionalMeasurementValueList, +id-HSDSCH-Paging-System-InformationLCR, +id-HSDSCH-Paging-System-Information-ResponseLCR, +id-HSDSCH-Common-System-InformationLCR, +id-HSDSCH-Common-System-Information-ResponseLCR, +id-Paging-MACFlows-to-DeleteLCR, +id-Enhanced-UE-DRX-CapabilityLCR, +id-Enhanced-UE-DRX-InformationLCR, +id-Common-EDCH-MACdFlows-to-DeleteLCR, +id-Common-EDCH-System-InformationLCR, +id-Common-EDCH-System-Information-ResponseLCR, +id-Common-MACFlows-to-DeleteLCR, +id-Common-UL-MACFlows-to-DeleteLCR, +id-HSDSCH-PreconfigurationSetup, +id-HSDSCH-PreconfigurationInfo, +id-NoOfTargetCellHS-SCCH-Order, +id-EnhancedHSServingCC-Abort, +id-GANSS-Time-ID, +id-Additional-HS-Cell-Information-RL-Setup, +id-Additional-HS-Cell-Information-Response, +id-Additional-HS-Cell-Information-RL-Addition, +id-Additional-HS-Cell-Change-Information-Response, +id-Additional-HS-Cell-Information-RL-Reconf-Prep, +id-Additional-HS-Cell-Information-RL-Reconf-Req, +id-Additional-HS-Cell-Information-RL-Param-Upd, +id-Multi-Cell-Capability-Info, +id-MinimumReducedE-DPDCH-GainFactor, +id-IMB-Parameters, +id-E-RNTI, +id-E-DCH-Semi-PersistentScheduling-Information-LCR, +id-HS-DSCH-Semi-PersistentScheduling-Information-LCR, +id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, +id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext, +id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR, +id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR, +id-HSSICH-ReferenceSignal-InformationLCR, +id-UE-Selected-MBMS-Service-Information, + +id-HSSICH-ReferenceSignal-InformationModifyLCR, +id-TimeSlotMeasurementValueListLCR, +id-MIMO-Power-Offset-For-S-CPICH-Capability, +id-MIMO-PilotConfigurationExtension, +id-TxDiversityOnDLControlChannelsByMIMOUECapability, +id-UE-AggregateMaximumBitRate, +id-Single-Stream-MIMO-Capability, +id-ActivationInformation, +id-Cell-Capability-Container, +id-DormantModeIndicator, +id-Additional-EDCH-Cell-Information-RL-Setup-Req, +id-Additional-EDCH-Cell-Information-Response, +id-Additional-EDCH-Cell-Information-RL-Add-Req, +id-Additional-EDCH-Cell-Information-Response-RL-Add, +id-Additional-EDCH-Cell-Information-RL-Reconf-Prep, +id-Additional-EDCH-Cell-Information-RL-Reconf-Req, +id-Additional-EDCH-Cell-Information-Bearer-Rearrangement, +id-Additional-EDCH-Cell-Information-RL-Param-Upd, +id-Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst, +id-E-HICH-TimeOffset-ReconfFailureTDD, +id-Common-System-Information-ResponseLCR, +id-TS0-CapabilityLCR, +id-HSSCCH-TPC-StepSize, +id-Out-of-Synchronization-Window, +id-DCH-MeasurementOccasion-Information, +id-Additional-EDCH-Cell-Information-ResponseRLReconf, +id-PrecodingWeightSetRestriction, +id-HSDSCH-RNTI-For-FACH, +id-E-RNTI-For-FACH, +id-Treset-Usage-Indicator, +id-Non-Serving-RL-Preconfig-Info, +id-Non-Serving-RL-Preconfig-Setup, +id-Non-Serving-RL-Preconfig-Removal, +id-Cell-Capability-Container-TDD-LCR, +id-Multi-Carrier-EDCH-Setup, +id-Multi-Carrier-EDCH-Reconfigure, +id-Multi-Carrier-EDCH-Response, +id-MU-MIMO-Capability-ContainerLCR, +id-MU-MIMO-InformationLCR, +id-MU-MIMO-Information-Response, +id-MU-MIMO-Information-To-ReconfigureLCR, +id-Adaptive-Special-Burst-Power-CapabilityLCR, +id-Usefulness-Of-Battery-Optimization, +id-In-Sync-Information-LCR, +id-ERNTI-Release-Status, +id-Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst, +id-CPC-RecoveryReport, +id-UL-CLTD-Information, +id-UL-CLTD-Information-Reconf, +id-UL-CLTD-State-Update-Information, +id-FTPICH-Information, +id-FTPICH-Information-Reconf, +id-Further-Enhanced-UE-DRX-InformationFDD, +id-Common-E-RGCH-Operation-Indicator, +id-Common-E-RGCH-InfoFDD, +id-DCH-ENH-Information, +id-DCH-ENH-Information-Reconf, +id-BCH-Parameters, +id-BCH-Parameters-CTCH-SetupRsp, +id-BCH-Parameters-CTCH-ReconfRqstFDD, +id-BCH-mappedOnSCCPCH-Indication, +id-Radio-Links-without-DPCH-FDPCH-Indication, +id-UL-DPCCH2-Information, +id-UL-DPCCH2-Information-Reconf, +id-UE-Measurement-Forwarding, +id-ActivationDelay, +id-Downlink-TPC-enhancements-Information, +id-Downlink-TPC-enhancements-Reconf, +id-TPC-slot-position, +id-Improved-Synchronized-Indicator, +id-HS-SCCH-DRX-InformationFDD, + +maxNrOfCCTrCHs, +maxNrOfCellSyncBursts, +maxNrOfCodes, +maxNrOfDCHs, +maxNrOfDLTSSs, +maxNrOfDLTSLCRs, + +``` + +maxNrOfDPCHs, +maxNrOfDPCHsPerRL-1, +maxNrOfDPCHLCRs, +maxNrOfDPCHsLCRPerRL-1, +maxNrOfDPCHs768, +maxNrOfDPCHs768PerRL-1, +maxNrOfDSCHs, +maxNrOfFACHs, +maxNrOfRLs, +maxNrOfRLs-1, +maxNrOfRLs-2, +maxNrOfRLSets, +maxNrOfPDSCCHs, +maxNrOfPUSCHs, +maxNrOfPUSCHs-1, +maxNrOfPRACHLCRs, +maxNrOfPDSCCHSets, +maxNrOfPUSCHSets, +maxNrOfReceptsPerSyncFrame, +maxNrOfSCCPCHs, +maxNrOfSCCPCHsinExt, +maxNrOfSCCPCHLCRs, +maxNrOfSCCPCHsLCRinExt, +maxNrOfSCCPCHs768, +maxNrOfULTSs, +maxNrOfULTSLCRs, +maxNrOfUSCHs, +maxFACHCell, +maxFPACHCell, +maxRACHCell, +maxPLCCHCell, +maxPRACHCell, +maxSCCPCHCell, +maxSCCPCHCell768, +maxSCCPCHCellinExt, +maxSCCPCHCellinExtLCR, +maxSCPICHCell, +maxCellinNodeB, +maxCCPinNodeB, +maxCommunicationContext, +maxLocalCellinNodeB, +maxNrOfSlotFormatsPRACH, +maxIB, +maxIBSEG, +maxNrOfCellPortionsPerCell, +maxNrOfHSSCCHs, +maxNrOfHSSICHs, +maxNrOfHSSICHs-1, +maxNrOfHSPDSCHs, +maxNrOfHSPDSCHs768, +maxNrOfSyncFramesLCR, +maxNrOfReceptionpersSyncFrameLCR, +maxNrOfSyncDLCodesLCR, +maxNrOfMACdFlows, +maxNrOfEDCHMACdFlows, +maxE-RUCCHCell, +maxNrOfE-PUCHSlots, +maxNrOfEAGCHs, +maxNrOfEAGCHCodes, +maxNrOfE-PUCHSlotsLCR, +maxNrOfEPUCHcodes, +maxNrOfEHICHs, +maxFrequencyinCell, +maxFrequencyinCell-1, +maxNrOfHSSCCHsinExt, +maxNrOfHSSCCHsLCR, +maxNrOfEAGCHsLCR, +maxNrOfEHICHsLCR, +maxNrOfHSDSCH-1, +maxNrOfEDCH-1, +maxNrOfULCarriersLCR-1, +maxNrOfCellPortionsPerCellLCR + +``` + +``` +FROM NBAP-Constants; +``` + +``` + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL SETUP REQUEST FDD + +``` + +``` + +-- +-- ***** + +CommonTransportChannelSetupRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelSetupRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelSetupRequestFDD- + Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CommonTransportChannelSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE + ConfigurationGenerationID PRESENCE mandatory }| + { ID id-CommonPhysicalChannelType-CTCH-SetupRqstFDD CRITICALITY ignore TYPE + CommonPhysicalChannelType-CTCH-SetupRqstFDD PRESENCE mandatory }, + ... +} + +CommonPhysicalChannelType-CTCH-SetupRqstFDD ::= CHOICE { + secondary-CCPCH-parameters Secondary-CCPCH-CTCH-SetupRqstFDD, + pRACH-parameters PRACH-CTCH-SetupRqstFDD, + notUsed-pCPCHes-parameters NULL, + ... +} + +Secondary-CCPCH-CTCH-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + fdd-S-CCPCH-Offset FDD-S-CCPCH-Offset, + dl-ScramblingCode DL-ScramblingCode OPTIONAL, + -- This IE shall be present if the PCH Parameters IE is not present + fdd-DL-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, + tFCS TFCS, + secondary-CCPCH-SlotFormat SecondaryCCPCH-SlotFormat, + tFCI-Presence TFCI-Presence OPTIONAL, + -- This IE shall be present if the Secondary CCPCH Slot Format is set to any of the values from + 8 to 17 or if 3.84Mcps TDD IMB is used + multiplexingPosition MultiplexingPosition, + powerOffsetInformation PowerOffsetInformation-CTCH-SetupRqstFDD, + sTTD-Indicator STTD-Indicator, + fACH-Parameters FACH-ParametersList-CTCH-SetupRqstFDD OPTIONAL, + pCH-Parameters PCH-Parameters-CTCH-SetupRqstFDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { Secondary-CCPCHItem-CTCH-SetupRqstFDD-ExtIEs } + OPTIONAL, + ... +} + +Secondary-CCPCHItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MICH-Parameters-CTCH-SetupRqstFDD CRITICALITY reject EXTENSION MICH- + Parameters-CTCH-SetupRqstFDD PRESENCE optional}| + { ID id-FDD-S-CCPCH-FrameOffset-CTCH-SetupRqstFDD CRITICALITY reject EXTENSION FDD-S-CCPCH- + FrameOffset PRESENCE optional}| + { ID id-ModulationPO-MBSFN CRITICALITY reject EXTENSION ModulationPO- + MBSFN PRESENCE optional}| + { ID id-Secondary-CCPCH-SlotFormat-Extended CRITICALITY reject EXTENSION Secondary- + CCPCH-SlotFormat-Extended PRESENCE optional}| + { ID id-IMB-Parameters CRITICALITY reject EXTENSION IMB-Parameters + PRESENCE optional}| + { ID id-BCH-Parameters CRITICALITY reject EXTENSION BCH-Parameters + PRESENCE optional}, + ... +} + +PowerOffsetInformation-CTCH-SetupRqstFDD ::= SEQUENCE { + pO1-ForTFCI-Bits PowerOffset, + pO3-ForPilotBits PowerOffset, + iE-Extensions ProtocolExtensionContainer { PowerOffsetInformation- + CTCH-SetupRqstFDD-ExtIEs } OPTIONAL, + ... +} + +PowerOffsetInformation-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +} + +FACH-ParametersList-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container {{ FACH-ParametersListIEs- +CTCH-SetupRqstFDD }} + +FACH-ParametersListIEs-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-FACH-ParametersListIE-CTCH-SetupRqstFDD CRITICALITY reject TYPE FACH- +ParametersListIE-CTCH-SetupRqstFDD PRESENCE mandatory } +} + +FACH-ParametersListIE-CTCH-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF FACH- +ParametersItem-CTCH-SetupRqstFDD + +FACH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + transportFormatSet TransportFormatSet, + toAWS ToAWS, + toAWE ToAWE, + maxFACH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { FACH-ParametersItem-CTCH- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +FACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional }| + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION + TransportLayerAddress PRESENCE optional }| + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }| + { ID id-BroadcastReference CRITICALITY ignore EXTENSION + BroadcastReference PRESENCE optional }| + { ID id-IPMulticastIndication CRITICALITY ignore EXTENSION + IPMulticastIndication PRESENCE optional }, + ... +} + +PCH-Parameters-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container {{ PCH-ParametersIE-CTCH- +SetupRqstFDD }} + +PCH-ParametersIE-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-PCH-ParametersItem-CTCH-SetupRqstFDD CRITICALITY reject TYPE PCH-ParametersItem- +CTCH-SetupRqstFDD PRESENCE mandatory } +} + +PCH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + transportFormatSet TransportFormatSet, + toAWS ToAWS, + toAWE ToAWE, + pCH-Power DL-Power, + pICH-Parameters PICH-Parameters-CTCH-SetupRqstFDD, + iE-Extensions ProtocolExtensionContainer { { PCH-ParametersItem-CTCH- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +PCH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional }| + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION + TransportLayerAddress PRESENCE optional }| + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... +} + +PICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + fdd-dl-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, + pICH-Power PICH-Power, + pICH-Mode PICH-Mode, + sTTD-Indicator STTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { PICH-Parameters-CTCH- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +PICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + fdd-dl-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, + mICH-Power PICH-Power, + mICH-Mode MICH-Mode, + sTTD-Indicator STTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { MICH-Parameters-CTCH- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +MICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACH-CTCH-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + scramblingCodeNumber ScramblingCodeNumber, + tFCS TFCS, + preambleSignatures PreambleSignatures, + allowedSlotFormatInformation AllowedSlotFormatInformationList-CTCH-SetupRqstFDD, + rACH-SubChannelNumbers RACH-SubChannelNumbers, + ul-punctureLimit PunctureLimit, + preambleThreshold PreambleThreshold, + rACH-Parameters RACH-Parameters-CTCH-SetupRqstFDD, + aICH-Parameters AICH-Parameters-CTCH-SetupRqstFDD, + iE-Extensions ProtocolExtensionContainer { { PRACHItem-CTCH-SetupRqstFDD-ExtIEs} } + OPTIONAL, + ... +} + +PRACHItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +AllowedSlotFormatInformationList-CTCH-SetupRqstFDD ::= SEQUENCE (SIZE (1.. maxNrOfSlotFormatsPRACH)) +OF AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD + +AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD ::= SEQUENCE { + rACHSlotFormat RACH-SlotFormat, + iE-Extensions ProtocolExtensionContainer { { AllowedSlotFormatInformationItem-CTCH- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RACH-Parameters-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container { { RACH-ParametersIE-CTCH- +SetupRqstFDD } } + +RACH-ParametersIE-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-RACH-ParametersItem-CTCH-SetupRqstFDD CRITICALITY reject TYPE RACH-ParametersItem- +CTCH-SetupRqstFDD PRESENCE mandatory } +} + +RACH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + transportFormatSet TransportFormatSet, + iE-Extensions ProtocolExtensionContainer { { RACH-ParametersItem- +CTCH-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +RACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional } | + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION + TransportLayerAddress PRESENCE optional } | + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... +} + +``` + +``` + +} + +AICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + aICH-TransmissionTiming AICH-TransmissionTiming, + fdd-dl-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, + aICH-Power AICH-Power, + sTTD-Indicator STTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { AICH-Parameters- +CTCH-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +AICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL SETUP REQUEST TDD +-- +-- ***** + +CommonTransportChannelSetupRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {CommonTransportChannelSetupRequestTDD- +IEs} }, + protocolExtensions ProtocolExtensionContainer { {CommonTransportChannelSetupRequestTDD- +Extensions} } OPTIONAL, + ... +} + +CommonTransportChannelSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory } | + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE +ConfigurationGenerationID PRESENCE mandatory } | + { ID id-CommonPhysicalChannelType-CTCH-SetupRqstTDD CRITICALITY ignore TYPE +CommonPhysicalChannelType-CTCH-SetupRqstTDD PRESENCE mandatory }, + ... +} + +CommonTransportChannelSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CommonPhysicalChannelType-CTCH-SetupRqstTDD ::= CHOICE { + secondary-CCPCH-parameters Secondary-CCPCH-CTCH-SetupRqstTDD, + pRACH-parameters PRACH-CTCH-SetupRqstTDD, + ..., + extension-CommonPhysicalChannelType-CTCH-SetupRqstTDD Extension-CommonPhysicalChannelType- +CTCH-SetupRqstTDD +} + +Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container { { Extension- +CommonPhysicalChannelType-CTCH-SetupRqstTDDIE } } + +Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDDIE NBAP-PROTOCOL-IES ::= { + { ID id-PLCCH-parameters CRITICALITY ignore TYPE PLCCH-parameters PRESENCE +mandatory } | + { ID id-E-RUCCH-parameters CRITICALITY ignore TYPE E-RUCCH-parameters PRESENCE +mandatory } | + { ID id-E-RUCCH-768-parameters CRITICALITY ignore TYPE E-RUCCH-768-parameters PRESENCE +mandatory }, + ... +} + +Secondary-CCPCH-CTCH-SetupRqstTDD ::= SEQUENCE { + sCCPCH-CCTrCH-ID CCTrCH-ID, -- For DL CCTrCH supporting one or +several Secondary CCPCHs + tFCS TFCS, -- For DL CCTrCH supporting one or +several Secondary CCPCHs + tFCI-Coding TFCI-Coding, + punctureLimit PunctureLimit, + secondaryCCPCH-parameterList Secondary-CCPCH-parameterList-CTCH-SetupRqstTDD, + fACH-ParametersList FACH-ParametersList-CTCH-SetupRqstTDD + OPTIONAL, + pCH-Parameters PCH-Parameters-CTCH-SetupRqstTDD + OPTIONAL, +} + +``` + +``` + + iE-Extensions ProtocolExtensionContainer { {Secondary-CCPCHItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCHItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Tstd-indicator CRITICALITY reject EXTENSION TSTD- +Indicator PRESENCE optional }| + { ID id-MICH-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION MICH- +Parameters-CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-Additional-S-CCPCH-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION Secondary- +CCPCH-parameterExtendedList-CTCH-SetupRqstTDD PRESENCE optional }| + -- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be +established. + { ID id-Additional-S-CCPCH-LCR-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION +Secondary-CCPCH-LCR-parameterExtendedList-CTCH-SetupRqstTDD PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHLCRs SCCPCHs are to be +established. + { ID id-S-CCPCH-768-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION Secondary- +CCPCH-768-parameterList-CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-S-CCPCH-Modulation CRITICALITY reject EXTENSION +ModulationMBSFN PRESENCE optional }| -- Applicable to 1.28Mcps TDD, +Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION +TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency +of Secondary Frequency on which SCCPCH to be set up + ... +} + +Secondary-CCPCH-parameterList-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ Secondary-CCPCH- +parameterListIEs-CTCH-SetupRqstTDD }} + +Secondary-CCPCH-parameterListIEs-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD CRITICALITY reject TYPE Secondary- +CCPCH-parameterListIE-CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD CRITICALITY reject TYPE Secondary- +CCPCH-LCR-parameterList-CTCH-SetupRqstTDD PRESENCE optional } +} + +Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs)) OF +Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD + +Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCode TDD-ChannelisationCode, + timeslot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + s-CCPCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH- +parameterItem-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-tFCI-Presence CRITICALITY notify EXTENSION TFCI-Presence + PRESENCE optional}, + ... +} + +Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHLCRs)) OF +Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD + +Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + timeslotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR, + -- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, NodeB shall ignore the +contents of this IE. + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + s-CCPCH-Power DL-Power, +} + +``` + +``` + + s-CCPCH-TimeSlotFormat-LCR TDD-DL-DPCH-TimeSlotFormat-LCR, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-LCR- +parameterItem-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MBSFN-SpecialTimeSlot-LCR CRITICALITY ignore EXTENSION TimeslotLCR- +Extension PRESENCE optional }, + -- Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS +25.221 [19]). The IE "Time Slot LCR" shall be ignored if this IE appears + ... +} + +Secondary-CCPCH-768-parameterList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs768)) OF +Secondary-CCPCH-768-parameterItem-CTCH-SetupRqstTDD + +Secondary-CCPCH-768-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + tdd-ChannelisationCode768 TDD-ChannelisationCode768, + timeslot TimeSlot, + tFCI-Presence768 TFCI-Presence OPTIONAL, + midambleShiftAndBurstType768 MidambleShiftAndBurstType768, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + s-CCPCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH- +parameterItem-768-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCH-parameterItem-768-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +FACH-ParametersList-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container { { FACH-ParametersListIEs- +CTCH-SetupRqstTDD } } + +FACH-ParametersListIEs-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-FACH-ParametersListIE-CTCH-SetupRqstTDD CRITICALITY reject TYPE FACH- +ParametersListIE-CTCH-SetupRqstTDD PRESENCE mandatory } +} + +FACH-ParametersListIE-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF FACH- +ParametersItem-CTCH-SetupRqstTDD + +FACH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + fACH-CCTrCH-ID CCTrCH-ID, + dl-TransportFormatSet TransportFormatSet, + toAWS ToAWS, + toAWE ToAWE, + iE-Extensions ProtocolExtensionContainer { { FACH-ParametersItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +FACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-maxFACH-Power-LCR-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION DL-Power + PRESENCE optional } | + -- Applicable to 1.28Mcps TDD only + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION +TransportLayerAddress PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-BroadcastReference CRITICALITY ignore EXTENSION +BroadcastReference PRESENCE optional } | + { ID id-IPMulticastIndication CRITICALITY ignore EXTENSION +IPMulticastIndication PRESENCE optional }, + ... +} + +``` + +``` + +PCH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container { PCH-ParametersIE-CTCH- +SetupRqstTDD } + +PCH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-PCH-ParametersItem-CTCH-SetupRqstTDD CRITICALITY reject TYPE PCH-ParametersItem- +CTCH-SetupRqstTDD PRESENCE mandatory } +} + +PCH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + pCH-CCTrCH-ID CCTrCH-ID, + dl-TransportFormatSet TransportFormatSet, -- For the DL. + toAWS ToAWS, + toAWE ToAWE, + pICH-Parameters PICH-Parameters-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { PCH-ParametersItem-CTCH- +SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-PCH-Power-LCR-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION DL-Power PRESENCE +optional }| + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID PRESENCE optional }| + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE +optional }| + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-PICH-768-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION PICH-768- +ParametersItem-CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }, + -- Shall be ignored if bearer establishment with ALCAP. + ... +} + +PICH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container { PICH-ParametersIE-CTCH- +SetupRqstTDD } + +PICH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-PICH-ParametersItem-CTCH-SetupRqstTDD CRITICALITY reject TYPE PICH-ParametersItem- +CTCH-SetupRqstTDD PRESENCE optional }| + { ID id-PICH-LCR-Parameters-CTCH-SetupRqstTDD CRITICALITY reject TYPE PICH-LCR-Parameters- +CTCH-SetupRqstTDD PRESENCE optional } +} + +PICH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCode TDD-ChannelisationCode, + timeSlot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + pagingIndicatorLength PagingIndicatorLength, + pICH-Power PICH-Power, + iE-Extensions ProtocolExtensionContainer { { PICH-ParametersItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PICH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PICH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + timeSlotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + pagingIndicatorLength PagingIndicatorLength, + pICH-Power PICH-Power, + second-TDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + iE-Extensions ProtocolExtensionContainer { { PICH-LCR-ParametersItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +} + +PICH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Tstd-indicator CRITICALITY reject EXTENSION TSTD-Indicator + PRESENCE optional }, + -- Applicable to 1.28 Mcps TDD only + ... +} + +PICH-768-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + tdd-ChannelisationCode768 TDD-ChannelisationCode768, + timeSlot TimeSlot, + midambleshiftAndBurstType768 MidambleShiftAndBurstType768, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + pagingIndicatorLength PagingIndicatorLength, + pICH-Power PICH-Power, + iE-Extensions ProtocolExtensionContainer { { PICH-768-ParametersItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PICH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + notificationIndicatorLength NotificationIndicatorLength, + mICH-Power PICH-Power, + mICH-TDDOption-Specific-Parameters MICH-TDDOption-Specific-Parameters-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { MICH-Parameters-CTCH- +SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +MICH-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-TDDOption-Specific-Parameters-CTCH-SetupRqstTDD ::= CHOICE { + hCR-TDD MICH-HCR-Parameters-CTCH-SetupRqstTDD, + lCR-TDD MICH-LCR-Parameters-CTCH-SetupRqstTDD, + ..., + chRate768-TDD MICH-768-Parameters-CTCH-SetupRqstTDD +} + +MICH-HCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + tdd-ChannelisationCode TDD-ChannelisationCode, + timeSlot TimeSlot, + midambleshiftAndBurstType MidambleShiftAndBurstType, + iE-Extensions ProtocolExtensionContainer { { MICH-HCR-Parameters-CTCH- +SetupRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +MICH-HCR-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + timeSlotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR, + -- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, NodeB shall ignore the + contents of this IE. + second-TDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + tSTD-Indicator TSTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { MICH-LCR-Parameters-CTCH- +SetupRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +MICHL-CR-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MBSFN-SpecialTimeSlot-LCR CRITICALITY ignore EXTENSION TimeslotLCR- + Extension PRESENCE optional }, + -- Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS + 25.221 [19]). The IE "Time Slot LCR" shall be ignored if this IE appears + ... +} + +MICHL-768-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + tdd-ChannelisationCode768 TDD-ChannelisationCode768, + timeSlot TimeSlot, + midambleshiftAndBurstType768 MidambleShiftAndBurstType768, + iE-Extensions ProtocolExtensionContainer { { MICHL-768-Parameters-CTCH- + SetupRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +MICHL-768-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..7)) OF + TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD + +TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD ::= SEQUENCE { + timeslotLCR TimeSlotLCR, + timeslotLCR-Parameter-ID CellParameterID, + iE-Extensions ProtocolExtensionContainer { { + TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Secondary-CCPCH-parameterExtendedList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHsinExt)) + OF Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD + -- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs CCPCHs are to be + established. + +Secondary-CCPCH-LCR-parameterExtendedList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE + (1..maxNrOfSCCPCHsLCRinExt)) OF Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD + -- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHLCRs CCPCHs are to be + established. + +PRACH-CTCH-SetupRqstTDD ::= SEQUENCE { + pPRACH-Parameters-CTCH-SetupRqstTDD PRACH-Parameters-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { PRACH-CTCH- + SetupRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +PRACH-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-FPACH-LCR-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION FPACH-LCR- + Parameters-CTCH-SetupRqstTDD PRESENCE optional } | + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-PRACH-768-Parameters-CTCH-SetupRqstTDD CRITICALITY reject EXTENSION PRACH-768- + ParametersItem-CTCH-SetupRqstTDD PRESENCE optional }, + ... +} + +PRACH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container { { PRACH-ParametersIE-CTCH- + SetupRqstTDD } } + +PRACH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-ParametersItem-CTCH-SetupRqstTDD CRITICALITY reject TYPE PRACH- + ParametersItem-CTCH-SetupRqstTDD PRESENCE optional } | + { ID id-PRACH-LCR-ParametersList-CTCH-SetupRqstTDD CRITICALITY reject TYPE PRACH-LCR- + ParametersList-CTCH-SetupRqstTDD PRESENCE optional } +} + +PRACH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tFCS TFCS, + timeslot TimeSlot, +} + +``` + +``` + + tdd-ChannelisationCode TDD-ChannelisationCode, + maxPRACH-MidambleShifts MaxPRACH-MidambleShifts, + pPRACH-Midamble PRACH-Midamble, + rACH RACH-Parameter-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { PRACH- +ParametersItem-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PRACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RACH-Parameter-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ RACH-ParameterIE-CTCH- +SetupRqstTDD }} + +RACH-ParameterIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-RACH-ParameterItem-CTCH-SetupRqstTDD CRITICALITY reject TYPE RACH-ParameterItem- +CTCH-SetupRqstTDD PRESENCE mandatory } +} + +RACH-ParameterItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + uL-TransportFormatSet TransportFormatSet, -- For the UL + iE-Extensions ProtocolExtensionContainer { { RACH-ParameterItem- +CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +RACH-ParameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional }| + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION TransportLayerAddress + PRESENCE optional }| + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + -- Shall be ignored if bearer establishment with ALCAP. + ... +} + +PRACH-LCR-ParametersList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfPRACHLCRs)) OF PRACH-LCR- +ParametersItem-CTCH-SetupRqstTDD + +PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tFCS TFCS, + timeslotLCR TimeSlotLCR, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + midambleShiftLCR MidambleShiftLCR, + rACH RACH-Parameter-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { PRACH-LCR- +ParametersItem-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency +of secondary on which PRACH to be set up. + ... +} + +PRACH-768-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + tFCS TFCS, + timeslot TimeSlot, + tdd-ChannelisationCode768 TDD-ChannelisationCode768, + maxPRACH-MidambleShifts MaxPRACH-MidambleShifts, + pPRACH-Midamble PRACH-Midamble, + rACH RACH-Parameter-CTCH-SetupRqstTDD, + iE-Extensions ProtocolExtensionContainer { { PRACH-768- +ParametersItem-CTCH-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PRACH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + FPACH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, + timeslotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR, + fPACH-Power FPACH-Power, + iE-Extensions ProtocolExtensionContainer { { FPACH-LCR- + ParametersItem-CTCH-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + FPACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency + of Secondary Frequency on which FPACH to be set up. + ... + } + + PLCCH-parameters ::= SEQUENCE { + maxPowerPLCCH DL-Power, + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-ChannelisationCode TDD-ChannelisationCode, + timeslotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR, + iE-Extensions ProtocolExtensionContainer { { PLCCH- + ParametersItem-CTCH-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + PLCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + E-RUCCH-parameters ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + timeslot TimeSlot, + tdd-ChannelisationCode TDD-ChannelisationCode, + maxE-RUCCH-MidambleShifts MaxPRACH-MidambleShifts, + e-RUCCH-Midamble PRACH-Midamble, + iE-Extensions ProtocolExtensionContainer { { E-RUCCH- + ParametersItem-CTCH-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + E-RUCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + E-RUCCH-768-parameters ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + timeslot TimeSlot, + tdd-ChannelisationCode768 TDD-ChannelisationCode768, + maxE-RUCCH-MidambleShifts MaxPRACH-MidambleShifts, + e-RUCCH-Midamble PRACH-Midamble, + iE-Extensions ProtocolExtensionContainer { { E-RUCCH-768- + ParametersItem-CTCH-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + E-RUCCH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- COMMON TRANSPORT CHANNEL SETUP RESPONSE + -- + -- ***** + + CommonTransportChannelSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelSetupResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelSetupResponse- + Extensions}} OPTIONAL, + ... + } + +``` + +``` + +CommonTransportChannelSetupResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-FACH-ParametersList-CTCH-SetupRsp CRITICALITY ignore TYPE FACH- +CommonTransportChannel-InformationResponse PRESENCE optional}| + { ID id-PCH-Parameters-CTCH-SetupRsp CRITICALITY ignore TYPE CommonTransportChannel- +InformationResponse PRESENCE optional}| + { ID id-RACH-Parameters-CTCH-SetupRsp CRITICALITY ignore TYPE CommonTransportChannel- +InformationResponse PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional}| + { ID id-BCH-Parameters-CTCH-SetupRsp CRITICALITY ignore TYPE CommonTransportChannel- +InformationResponse PRESENCE optional}, + ... +} + +CommonTransportChannelSetupResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +FACH-CommonTransportChannel-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF +CommonTransportChannel-InformationResponse + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL SETUP FAILURE +-- +-- ***** + +CommonTransportChannelSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelSetupFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelSetupFailure- +Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelSetupFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +CommonTransportChannelSetupFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST FDD +-- +-- ***** + +CommonTransportChannelReconfigurationRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container + {{CommonTransportChannelReconfigurationRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer + {{CommonTransportChannelReconfigurationRequestFDD-Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE +ConfigurationGenerationID PRESENCE mandatory }| + { ID id-CommonPhysicalChannelType-CTCH-ReconfRqstFDD CRITICALITY reject TYPE +CommonPhysicalChannelType-CTCH-ReconfRqstFDD PRESENCE mandatory }, + ... +} + +CommonTransportChannelReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CommonPhysicalChannelType-CTCH-ReconfRqstFDD ::= CHOICE { + secondary-CCPCH-parameters Secondary-CCPCHList-CTCH-ReconfRqstFDD, + pRACH-parameters PRACHList-CTCH-ReconfRqstFDD, +} + +``` + +``` + notUsed-cPCH-parameters NULL, + ... +} + +Secondary-CCPCHList-CTCH-ReconfRqstFDD ::= SEQUENCE { + fACH-ParametersList-CTCH-ReconfRqstFDD FACH-ParametersList-CTCH-ReconfRqstFDD OPTIONAL, + pCH-Parameters-CTCH-ReconfRqstFDD PCH-Parameters-CTCH-ReconfRqstFDD OPTIONAL, + pICH-Parameters-CTCH-ReconfRqstFDD PICH-Parameters-CTCH-ReconfRqstFDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-CTCH- +ReconfRqstFDD-ExtIEs } } OPTIONAL, + ... +} + +Secondary-CCPCH-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MICH-Parameters-CTCH-ReconfRqstFDD CRITICALITY reject EXTENSION MICH-Parameters- +CTCH-ReconfRqstFDD PRESENCE optional } | + { ID id-BCH-Parameters-CTCH-ReconfRqstFDD CRITICALITY ignore EXTENSION BCH-Parameters- +CTCH-ReconfRqstFDD PRESENCE optional }, + ... +} + +FACH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ FACH-ParametersListIEs- +CTCH-ReconfRqstFDD }} + +FACH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-FACH-ParametersListIE-CTCH-ReconfRqstFDD CRITICALITY reject TYPE FACH- +ParametersListIE-CTCH-ReconfRqstFDD PRESENCE mandatory } +} + +FACH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxFACHCell)) OF FACH- +ParametersItem-CTCH-ReconfRqstFDD + +FACH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + maxFACH-Power DL-Power OPTIONAL, + toAWS ToAWS OPTIONAL, + toAWE ToAWE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs } } +OPTIONAL, + ... +} + +FACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }, + ... +} + +PCH-Parameters-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PCH-ParametersIE-CTCH- +ReconfRqstFDD }} + +PCH-ParametersIE-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-PCH-ParametersItem-CTCH-ReconfRqstFDD CRITICALITY reject TYPE PCH-ParametersItem- +CTCH-ReconfRqstFDD PRESENCE mandatory } +} + +PCH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + pCH-Power DL-Power OPTIONAL, + toAWS ToAWS OPTIONAL, + toAWE ToAWE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs } } +OPTIONAL, + ... +} + +PCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }, + ... +} + +PICH-Parameters-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PICH-ParametersIE-CTCH- +ReconfRqstFDD }} + +PICH-ParametersIE-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-PICH-ParametersItem-CTCH-ReconfRqstFDD CRITICALITY reject TYPE PICH-ParametersItem- +CTCH-ReconfRqstFDD PRESENCE mandatory } +} +``` + +``` + +PICH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + pICH-Power PICH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PICH-ParametersItem-CTCH- +ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +PICH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-Parameters-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + mICH-Power PICH-Power + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MICH-Parameters-CTCH- +ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +MICH-Parameters-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +BCH-Parameters-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + bCH-Power DL-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} } + OPTIONAL, + ... +} + +BCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACHList-CTCH-ReconfRqstFDD ::= SEQUENCE { + pRACH-ParametersList-CTCH-ReconfRqstFDD PRACH-ParametersList-CTCH-ReconfRqstFDD OPTIONAL, + aICH-ParametersList-CTCH-ReconfRqstFDD AICH-ParametersList-CTCH-ReconfRqstFDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRACH-CTCH-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +PRACH-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PRACH-ParametersListIEs- +CTCH-ReconfRqstFDD }} + +PRACH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-ParametersListIE-CTCH-ReconfRqstFDD CRITICALITY reject TYPE PRACH- +ParametersListIE-CTCH-ReconfRqstFDD PRESENCE mandatory } +} + +PRACH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF PRACH- +ParametersItem-CTCH-ReconfRqstFDD + +PRACH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + preambleSignatures PreambleSignatures + OPTIONAL, + allowedSlotFormatInformation AllowedSlotFormatInformationList-CTCH-ReconfRqstFDD + OPTIONAL, + rACH-SubChannelNumbers RACH-SubChannelNumbers + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRACH-ParametersItem- +CTCH-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +PRACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }, + ... +} + +``` + +``` + +AllowedSlotFormatInformationList-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfSlotFormatsPRACH)) OF AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD + +AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + rACH-SlotFormat RACH-SlotFormat, + iE-Extensions ProtocolExtensionContainer { { AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD-ExtIEs } } OPTIONAL, + ... +} + +AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +AICH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container { { AICH-ParametersListIEs-CTCH-ReconfRqstFDD } } + +AICH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-AICH-ParametersListIE-CTCH-ReconfRqstFDD CRITICALITY reject TYPE AICH-ParametersListIE-CTCH-ReconfRqstFDD PRESENCE mandatory } +} + +AICH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF AICH-ParametersItem-CTCH-ReconfRqstFDD + +AICH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + aICH-Power AICH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AICH-ParametersItemIE-CTCH-ReconfRqstFDD-ExtIEs } } OPTIONAL, + ... +} + +AICH-ParametersItemIE-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST TDD +-- +-- ***** + +CommonTransportChannelReconfigurationRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {CommonTransportChannelReconfigurationRequestTDD-IEs} }, + protocolExtensions ProtocolExtensionContainer { {CommonTransportChannelReconfigurationRequestTDD-Extensions} } OPTIONAL, + ... +} + +CommonTransportChannelReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID PRESENCE mandatory } | + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE ConfigurationGenerationID PRESENCE mandatory } | + { ID id-Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject TYPE Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-PICH-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject TYPE PICH-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-FACH-ParametersList-CTCH-ReconfRqstTDD CRITICALITY reject TYPE FACH-ParametersList-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-PCH-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject TYPE PCH-Parameters-CTCH-ReconfRqstTDD PRESENCE optional }, + ... +} + +CommonTransportChannelReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-FPACH-LCR-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION FPACH-LCR-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + -- Applicable to 1.28Mcps TDD only + { ID id-MICH-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION MICH-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-PLCH-Parameters-CTCH-ReconfRqstTDD CRITICALITY ignore EXTENSION PLCH-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-S-CCPCH-768-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION Secondary-CCPCH-768-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | + { ID id-PICH-768-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION PICH-768-Parameters-CTCH-ReconfRqstTDD PRESENCE optional } | +} + +``` + +``` + + { ID id-MICH-768-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION MICH-768- +Parameters-CTCH-ReconfRqstTDD PRESENCE optional }| + { ID id-UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION UPPCH-LCR- +Parameters-CTCH-ReconfRqstTDD PRESENCE optional }, -- Applicable to 1.28Mcps TDD +only + ... +} + +Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + CCTrCH-ID CCTrCH-ID, + secondaryCCPCHList Secondary-CCPCHList-CTCH-ReconfRqstTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCH-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Additional-S-CCPCH-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject + EXTENSION Secondary-CCPCH-parameterExtendedList-CTCH-ReconfRqstTDD PRESENCE optional }| + -- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be +reconfigured. + { ID id-Additional-S-CCPCH-LCR-Parameters-CTCH-ReconfRqstTDD CRITICALITY reject + EXTENSION Secondary-CCPCH-LCR-parameterExtendedList-CTCH-ReconfRqstTDD PRESENCE optional }, + -- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be +reconfigured. + ... +} + +Secondary-CCPCHList-CTCH-ReconfRqstTDD ::= ProtocolIE-Single-Container { { Secondary-CCPCHListIEs- +CTCH-ReconfRqstTDD } } + +Secondary-CCPCHListIEs-CTCH-ReconfRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-Secondary-CCPCHListIE-CTCH-ReconfRqstTDD CRITICALITY reject TYPE Secondary- +CCPCHListIE-CTCH-ReconfRqstTDD PRESENCE mandatory } +} + +Secondary-CCPCHListIE-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs)) OF Secondary- +CCPCHItem-CTCH-ReconfRqstTDD + +Secondary-CCPCHItem-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + sCCPCH-Power DL-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCHItem-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCHItem-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Secondary-CCPCH-parameterExtendedList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE +(1..maxNrOfSCCPCHsinExt)) OF Secondary-CCPCHItem-CTCH-ReconfRqstTDD +-- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be +reconfigured. + +Secondary-CCPCH-LCR-parameterExtendedList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE +(1..maxNrOfSCCPCHsLCRinExt)) OF Secondary-CCPCHItem-CTCH-ReconfRqstTDD +-- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be +reconfigured. + +PICH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + pICH-Power PICH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PICH-Parameters-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +FACH-ParametersList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (0..maxNrOfFACHs)) OF FACH-ParametersItem- +CTCH-ReconfRqstTDD + +FACH-ParametersItem-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, +} + +``` + +``` + + toAWS ToAWS OPTIONAL, + toAWE ToAWE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FACH-ParametersItem-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + FACH-ParametersItem-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-maxFACH-Power-LCR-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION DL- +Power PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... + } + + PCH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + toAWS ToAWS OPTIONAL, + toAWE ToAWE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs} } + OPTIONAL, + ... + } + + PCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-PCH-Power-LCR-CTCH-ReconfRqstTDD CRITICALITY reject EXTENSION DL-Power + PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... + } + + FPACH-LCR-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelId CommonPhysicalChannelID, + fPACHPower fPACH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FPACH-LCR-Parameters-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + FPACH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + MICH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelId CommonPhysicalChannelID, + mICH-Power PICH-Power + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MICH-Parameters-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + MICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PLCCH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + maxPowerPLCCH DL-Power, + iE-Extensions ProtocolExtensionContainer { { PLCCH-Parameters-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + PLCCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Secondary-CCPCH-768-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + secondaryCCPCH768List Secondary-CCPCH-768-List-CTCH-ReconfRqstTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-768-CTCH- +ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +Secondary-CCPCH-768-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Secondary-CCPCH-768-List-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs768)) OF Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD + +Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + sCCPCH-Power DL-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PICH-768-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + pICH-Power PICH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MICH-768-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + mICH-Power PICH-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +MICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE { + uPPCHPositionLCR UPPCHPositionLCR OPTIONAL, + uARFCN UARFCN OPTIONAL, + -- Mandatory for 1.28Mcps TDD when using multiple frequencies Corresponds to Nt (TS 25.105 [15]) + iE-Extensions ProtocolExtensionContainer { { UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- **************************************************************************** +-- +-- COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE +-- +-- **************************************************************************** + +CommonTransportChannelReconfigurationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelReconfigurationResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelReconfigurationResponse-Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +CommonTransportChannelReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE +-- +-- ***** + +CommonTransportChannelReconfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container + {{CommonTransportChannelReconfigurationFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer + {{CommonTransportChannelReconfigurationFailure-Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE + CriticalityDiagnostics PRESENCE optional }, + ... +} + +CommonTransportChannelReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL DELETION REQUEST +-- +-- ***** + +CommonTransportChannelDeletionRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelDeletionRequest- + IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelDeletionRequest- + Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelDeletionRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-CommonPhysicalChannelID CRITICALITY reject TYPE CommonPhysicalChannelID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE + ConfigurationGenerationID PRESENCE mandatory }, + ... +} + +CommonTransportChannelDeletionRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-CommonPhysicalChannelID768-CommonTrChDeletionReq CRITICALITY reject EXTENSION + CommonPhysicalChannelID768 PRESENCE optional }, + ... +} + +-- ***** +-- +-- COMMON TRANSPORT CHANNEL DELETION RESPONSE +-- +-- ***** + +CommonTransportChannelDeletionResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonTransportChannelDeletionResponse- + IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelDeletionResponse- + Extensions}} OPTIONAL, + ... +} + +CommonTransportChannelDeletionResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE + CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +} + +CommonTransportChannelDeletionResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- BLOCK RESOURCE REQUEST +-- +-- ***** + +BlockResourceRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{BlockResourceRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{BlockResourceRequest-Extensions}} + OPTIONAL, + ... +} + +BlockResourceRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-BlockingPriorityIndicator CRITICALITY reject TYPE BlockingPriorityIndicator + PRESENCE mandatory }| + { ID id-ShutdownTimer CRITICALITY reject TYPE ShutdownTimer + PRESENCE conditional }, + -- The IE shall be present if the Blocking Priority Indicator IE indicates "Normal Priority"-- + ... +} + +BlockResourceRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- BLOCK RESOURCE RESPONSE +-- +-- ***** + +BlockResourceResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{BlockResourceResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{BlockResourceResponse-Extensions}} + OPTIONAL, + ... +} + +BlockResourceResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional}, + ... +} + +BlockResourceResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- BLOCK RESOURCE FAILURE +-- +-- ***** + +BlockResourceFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{BlockResourceFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{BlockResourceFailure-Extensions}} + OPTIONAL, + ... +} + +BlockResourceFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +``` + +``` + +BlockResourceFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- UNBLOCK RESOURCE INDICATION +-- +-- ***** + +UnblockResourceIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{UnblockResourceIndication-IEs}}, + protocolExtensions ProtocolExtensionContainer {{UnblockResourceIndication-Extensions}} + OPTIONAL, + ... +} + +UnblockResourceIndication-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY ignore TYPE C-ID PRESENCE mandatory }, + ... +} + +UnblockResourceIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- AUDIT REQUIRED INDICATION +-- +-- ***** + +AuditRequiredIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AuditRequiredIndication-IEs}}, + protocolExtensions ProtocolExtensionContainer {{AuditRequiredIndication-Extensions}} + OPTIONAL, + ... +} + +AuditRequiredIndication-IEs NBAP-PROTOCOL-IES ::= { + ... +} + +AuditRequiredIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- AUDIT REQUEST +-- +-- ***** + +AuditRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AuditRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{AuditRequest-Extensions}} + OPTIONAL, + ... +} + +AuditRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Start-Of-Audit-Sequence-Indicator CRITICALITY reject TYPE Start-Of-Audit- + Sequence-Indicator PRESENCE mandatory }, + ... +} + +AuditRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- AUDIT RESPONSE +-- +-- ***** + +AuditResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AuditResponse-IEs}}, + +``` + +``` + + protocolExtensions ProtocolExtensionContainer {{AuditResponse-Extensions}} + OPTIONAL, + ... +} + +AuditResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-End-Of-Audit-Sequence-Indicator CRITICALITY ignore TYPE End-Of-Audit- + Sequence-Indicator PRESENCE mandatory }| + { ID id-Cell-InformationList-AuditRsp CRITICALITY ignore TYPE Cell- + InformationList-AuditRsp PRESENCE optional }| + { ID id-CCP-InformationList-AuditRsp CRITICALITY ignore TYPE CCP- + InformationList-AuditRsp PRESENCE optional }| + -- CCP (Communication Control Port) -- + { ID id-Local-Cell-InformationList-AuditRsp CRITICALITY ignore TYPE Local-Cell- + InformationList-AuditRsp PRESENCE optional }| + { ID id-Local-Cell-Group-InformationList-AuditRsp CRITICALITY ignore TYPE Local-Cell-Group- + InformationList-AuditRsp PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE + CriticalityDiagnostics PRESENCE optional }, + ... +} + +AuditResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Power-Local-Cell-Group-InformationList-AuditRsp CRITICALITY ignore EXTENSION Power- + Local-Cell-Group-InformationList-AuditRsp PRESENCE optional }, + ... +} + +Cell-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxCellInNodeB)) OF ProtocolIE-Single-Container +{{ Cell-InformationItemIE-AuditRsp}} + +Cell-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-Cell-InformationItem-AuditRsp CRITICALITY ignore TYPE Cell- + InformationItem-AuditRsp PRESENCE optional } +} + +Cell-InformationItem-AuditRsp ::= SEQUENCE { + c-ID C-ID, + configurationGenerationID ConfigurationGenerationID, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + local-Cell-ID Local-Cell-ID, + primary-SCH-Information P-SCH-Information-AuditRsp OPTIONAL, + secondary-SCH-Information S-SCH-Information-AuditRsp OPTIONAL, + primary-CPICH-Information P-CPICH-Information-AuditRsp OPTIONAL, + secondary-CPICH-InformationList S-CPICH-InformationList-AuditRsp OPTIONAL, + primary-CCPCH-Information P-CCPCH-Information-AuditRsp OPTIONAL, + bCH-Information BCH-Information-AuditRsp OPTIONAL, + secondary-CCPCH-InformationList S-CCPCH-InformationList-AuditRsp OPTIONAL, + pCH-Information PCH-Information-AuditRsp OPTIONAL, + pICH-Information PICH-Information-AuditRsp OPTIONAL, + fACH-InformationList FACH-InformationList-AuditRsp OPTIONAL, + pRACH-InformationList PRACH-InformationList-AuditRsp OPTIONAL, + rACH-InformationList RACH-InformationList-AuditRsp OPTIONAL, + aICH-InformationList AICH-InformationList-AuditRsp OPTIONAL, + notUsed-1-pCPCH-InformationList NULL OPTIONAL, + notUsed-2-cPCH-InformationList NULL OPTIONAL, + notUsed-3-aP-AICH-InformationList NULL OPTIONAL, + notUsed-4-cDCA-ICH-InformationList NULL OPTIONAL, + sCH-Information SCH-Information-AuditRsp OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Cell-InformationItem-AuditRsp-ExtIEs} } + OPTIONAL, + ... +} + +Cell-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-FPACH-LCR-InformationList-AuditRsp CRITICALITY ignore EXTENSION FPACH-LCR- + InformationList-AuditRsp PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-DwPCH-LCR-InformationList-AuditRsp CRITICALITY ignore EXTENSION Common- + PhysicalChannel-Status-Information PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-HSDSCH-Resources-Information-AuditRsp CRITICALITY ignore EXTENSION HS-DSCH-Resources- + Information-AuditRsp PRESENCE optional }| + -- For 1.28Mcps TDD, this HS-DSCH Resource Information is for the first Frequency repetition, + HS-DSCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq- + HS-DSCH-Resources-InformationList-AuditRsp. +} + +``` + +``` + + { ID id-MICH-Information-AuditRsp CRITICALITY ignore EXTENSION Common- +PhysicalChannel-Status-Information PRESENCE optional }| + { ID id-S-CCPCH-InformationListExt-AuditRsp CRITICALITY ignore EXTENSION S-CCPCH- +InformationListExt-AuditRsp PRESENCE optional }| + -- Applicable to 3.84Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the +cell. + { ID id-S-CCPCH-LCR-InformationListExt-AuditRsp CRITICALITY ignore EXTENSION S-CCPCH-LCR- +InformationListExt-AuditRsp PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the +cell. + { ID id-E-DCH-Resources-Information-AuditRsp CRITICALITY ignore EXTENSION E-DCH-Resources- +Information-AuditRsp PRESENCE optional }| + -- For 1.28Mcps TDD, this E-DCH Resource Information is for the first Frequency repetition, E- +DCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-E- +DCH-Resources-InformationList-AuditRsp. + { ID id-PLCH-InformationList-AuditRsp CRITICALITY ignore EXTENSION PLCH- +InformationList-AuditRsp PRESENCE optional }| + { ID id-P-CCPCH-768-Information-AuditRsp CRITICALITY ignore EXTENSION Common- +PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-S-CCPCH-768-InformationList-AuditRsp CRITICALITY ignore EXTENSION S-CCPCH-768- +InformationList-AuditRsp PRESENCE optional }| + { ID id-PICH-768-Information-AuditRsp CRITICALITY ignore EXTENSION Common- +PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-PRACH-768-InformationList-AuditRsp CRITICALITY ignore EXTENSION PRACH-768- +InformationList-AuditRsp PRESENCE optional }| + { ID id-SCH-768-Information-AuditRsp CRITICALITY ignore EXTENSION Common- +PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-MICH-768-Information-AuditRsp CRITICALITY ignore EXTENSION Common- +PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-E-RUCCH-InformationList-AuditRsp CRITICALITY ignore EXTENSION E-RUCCH- +InformationList-AuditRsp PRESENCE optional }| + { ID id-E-RUCCH-768-InformationList-AuditRsp CRITICALITY ignore EXTENSION E-RUCCH-768- +InformationList-AuditRsp PRESENCE optional }| + { ID id-Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp CRITICALITY ignore EXTENSION +Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp PRESENCE optional }| -- Applicable to +1.28Mcps TDD when using multiple frequencies + { ID id-UPPCH-LCR-InformationList-AuditRsp CRITICALITY ignore EXTENSION UPPCH-LCR- +InformationList-AuditRsp PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-multipleFreq-HS-DSCH-Resources-InformationList-AuditRsp CRITICALITY ignore EXTENSION +MultipleFreq-HS-DSCH-Resources-InformationList-AuditRsp PRESENCE optional }| + -- Applicable to 1.28Mcps TDD when using multiple frequencies.This HS-DSCH Resource Information is +for the 2nd and beyond frequencies. + { ID id-MultipleFreq-E-DCH-Resources-InformationList-AuditRsp CRITICALITY ignore EXTENSION +MultipleFreq-E-DCH-Resources-InformationList-AuditRsp PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. This E-DCH Resource Information +is for the 2nd and beyond frequencies. + ... +} + +P-SCH-Information-AuditRsp ::= ProtocolIE-Single-Container { { P-SCH-InformationIE-AuditRsp } } + +P-SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-P-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +S-SCH-Information-AuditRsp ::= ProtocolIE-Single-Container { { S-SCH-InformationIE-AuditRsp } } + +S-SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-S-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +P-CPICH-Information-AuditRsp ::= ProtocolIE-Single-Container { { P-CPICH-InformationIE-AuditRsp } } + +P-CPICH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-P-CPICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +S-CPICH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE-Single- +Container { { S-CPICH-InformationItemIE-AuditRsp } } + +S-CPICH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-S-CPICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +``` + +``` +P-CCPCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ P-CCPCH-InformationIE-AuditRsp }} + +P-CCPCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-P-CCPCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +BCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ BCH-InformationIE-AuditRsp }} + +BCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-BCH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +S-CCPCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCell)) OF ProtocolIE-Single- +Container {{ S-CCPCH-InformationItemIE-AuditRsp }} + +S-CCPCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-S-CCPCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +PCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ PCH-InformationIE-AuditRsp }} + +PCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-PCH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +PICH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ PICH-InformationIE-AuditRsp }} + +PICH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-PICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +FACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFACHCell)) OF ProtocolIE-Single-Container {{ +FACH-InformationItemIE-AuditRsp }} + +FACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-FACH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +PRACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container +{{ PRACH-InformationItemIE-AuditRsp }} + +PRACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +RACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxRACHCell)) OF ProtocolIE-Single-Container {{ +RACH-InformationItemIE-AuditRsp }} + +RACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-RACH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +AICH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container +{{ AICH-InformationItemIE-AuditRsp }} + +AICH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-AICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +SCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ SCH-InformationIE-AuditRsp }} + +SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +FPACH-LCR-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFPACHCell)) OF ProtocolIE-Single- +Container {{ FPACH-LCR-InformationItemIE-AuditRsp }} +``` + +``` +FPACH-LCR-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-FPACH-LCR-Information-AuditRsp CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information PRESENCE mandatory } +} + +HS-DSCH-Resources-Information-AuditRsp ::= SEQUENCE { + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ HS-DSCH-Resources- +Information-AuditRsp-ExtIEs }} OPTIONAL, + ... +} + +HS-DSCH-Resources-Information-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. + ... +} + +S-CCPCH-InformationListExt-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExt)) OF ProtocolIE- +Single-Container {{ S-CCPCH-InformationItemIE-AuditRsp }} + +S-CCPCH-LCR-InformationListExt-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExtLCR)) OF +ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-AuditRsp }} + +E-DCH-Resources-Information-AuditRsp ::= SEQUENCE { + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ E-DCH-Resources-Information- +AuditRsp-ExtIEs }} OPTIONAL, + ... +} + +E-DCH-Resources-Information-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. + ... +} + +PLCCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPLCCHCell)) OF ProtocolIE-Single-Container +{{ PLCCH-InformationItemIE-AuditRsp }} + +PLCCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-PLCCH-Information-AuditRsp CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information PRESENCE mandatory } +} + +S-CCPCH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCell768)) OF ProtocolIE-Single- +Container {{ S-CCPCH-768-InformationItemIE-AuditRsp }} + +S-CCPCH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-S-CCPCH-768-Information-AuditRsp CRITICALITY ignore TYPE Common-PhysicalChannel- +Status-Information768 PRESENCE mandatory } +} + +PRACH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single- +Container {{ PRACH-768-InformationItemIE-AuditRsp }} + +PRACH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-768-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information768 PRESENCE mandatory } +} + +E-RUCCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single- +Container {{ E-RUCCH-InformationItemIE-AuditRsp }} + +E-RUCCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-E-RUCCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information PRESENCE mandatory } +} + +E-RUCCH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single- +Container {{ E-RUCCH-768-InformationItemIE-AuditRsp }} + +E-RUCCH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-E-RUCCH-768-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information768 PRESENCE mandatory } +} +``` + +``` + +} + +Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF +ProtocolIE-Single-Container {{ Cell-Frequency-List-InformationIE-LCR-MulFreq-AuditRsp }} + +Cell-Frequency-List-InformationIE-LCR-MulFreq-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp CRITICALITY ignore TYPE +Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp PRESENCE mandatory } +} + +Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp ::= SEQUENCE { + uARFCN UARFCN, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ Cell-Frequency-List- +InformationItem-LCR-MulFreq-AuditRsp-ExtIEs }} OPTIONAL, + ... +} + +Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UPPCH-LCR-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single- +Container {{ UPPCH-LCR-InformationIE-AuditRsp }} + +UPPCH-LCR-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-UPPCH-LCR-InformationItem-AuditRsp CRITICALITY ignore TYPE UPPCH-LCR-InformationItem- +AuditRsp PRESENCE mandatory } +} + +UPPCH-LCR-InformationItem-AuditRsp ::= SEQUENCE { + uARFCN UARFCN OPTIONAL, + uPPCHPositionLCR UPPCHPositionLCR, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ UPPCH-LCR-InformationItem- +AuditRsp-ExtIEs }} OPTIONAL, + ... +} + +UPPCH-LCR-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleFreq-HS-DSCH-Resources-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell- +1)) OF ProtocolIE-Single-Container {{ MultipleFreq-HS-DSCH-Resources-InformationItem-AuditRsp }} +--Includes the 2nd through the max number of frequencies information repetitions. + +MultipleFreq-HS-DSCH-Resources-InformationItem-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-HSDSCH-Resources-Information-AuditRsp CRITICALITY ignore TYPE HS-DSCH-Resources- +Information-AuditRsp PRESENCE mandatory } +} + +MultipleFreq-E-DCH-Resources-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) +OF ProtocolIE-Single-Container {{ MultipleFreq-E-DCH-Resources-InformationItem-AuditRsp }} +-- Includes the 2nd through the max number of frequencies information repetitions. + +MultipleFreq-E-DCH-Resources-InformationItem-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-E-DCH-Resources-Information-AuditRsp CRITICALITY ignore TYPE E-DCH-Resources- +Information-AuditRsp PRESENCE mandatory } +} + +CCP-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxCCPinNodeB)) OF ProtocolIE-Single-Container +{{ CCP-InformationItemIE-AuditRsp }} + +CCP-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-CCP-InformationItem-AuditRsp CRITICALITY ignore TYPE CCP- +InformationItem-AuditRsp PRESENCE mandatory } +} + +CCP-InformationItem-AuditRsp ::= SEQUENCE { + communicationControlPortID CommunicationControlPortID, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ CCP-InformationItem-AuditRsp- +ExtIEs }} OPTIONAL, + ... +} + +``` + +``` + +} + +CCP-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Local-Cell-InformationList-AuditRsp ::=SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF ProtocolIE- +Single-Container {{ Local-Cell-InformationItemIE-AuditRsp }} + +Local-Cell-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-InformationItem-AuditRsp CRITICALITY ignore TYPE Local-Cell- +InformationItem-AuditRsp PRESENCE mandatory} +} + +Local-Cell-InformationItem-AuditRsp ::= SEQUENCE { + local-Cell-ID Local-Cell-ID, + dl-or-global-capacityCredit DL-or-Global-CapacityCredit, + ul-capacityCredit UL-CapacityCredit + OPTIONAL, + commonChannelsCapacityConsumptionLaw CommonChannelsCapacityConsumptionLaw, + dedicatedChannelsCapacityConsumptionLaw DedicatedChannelsCapacityConsumptionLaw, + maximumDL-PowerCapability MaximumDL-PowerCapability + OPTIONAL, + minSpreadingFactor MinSpreadingFactor + OPTIONAL, + minimumDL-PowerCapability MinimumDL-PowerCapability + OPTIONAL, + local-Cell-Group-ID Local-Cell-ID + OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ Local-Cell- +InformationItem-AuditRsp-ExtIEs}} OPTIONAL, + ... +} + +Local-Cell-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-ReferenceClockAvailability CRITICALITY ignore EXTENSION +ReferenceClockAvailability PRESENCE optional }| + { ID id-Power-Local-Cell-Group-ID CRITICALITY ignore EXTENSION Local-Cell-ID +PRESENCE optional }| + { ID id-HSDPA-Capability CRITICALITY ignore EXTENSION HSDPA-Capability +PRESENCE optional }| + { ID id-E-DCH-Capability CRITICALITY ignore EXTENSION E-DCH-Capability +PRESENCE optional }| + { ID id-E-DCH-TTI2ms-Capability CRITICALITY ignore EXTENSION E-DCH-TTI2ms- +Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-SF-Capability CRITICALITY ignore EXTENSION E-DCH-SF-Capability +PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-HARQ-Combining-Capability CRITICALITY ignore EXTENSION E-DCH-HARQ-Combining- +Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- +DCHCapacityConsumptionLaw PRESENCE optional }| + { ID id-F-DPCH-Capability CRITICALITY ignore EXTENSION F-DPCH-Capability +PRESENCE optional }| + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- +CapacityConsumptionLaw PRESENCE optional }| + { ID id-ContinuousPacketConnectivityDTX-DRX-Capability CRITICALITY ignore EXTENSION +ContinuousPacketConnectivityDTX-DRX-Capability PRESENCE optional }| + { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle +PRESENCE conditional }| + -- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present +and set to "Continuous Packet Connectivity DTX-DRX Capable". + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability CRITICALITY ignore EXTENSION +ContinuousPacketConnectivityHS-SCCH-less-Capability PRESENCE optional }| + { ID id-MIMO-Capability CRITICALITY ignore EXTENSION MIMO-Capability +PRESENCE optional }| + { ID id-SixtyfourQAM-DL-Capability CRITICALITY ignore EXTENSION SixtyfourQAM-DL- +Capability PRESENCE optional }| + { ID id-MBMS-Capability CRITICALITY ignore EXTENSION MBMS-Capability +PRESENCE optional }| + { ID id-Enhanced-FACH-Capability CRITICALITY ignore EXTENSION Enhanced-FACH- +Capability PRESENCE optional }| + { ID id-Enhanced-PCH-Capability CRITICALITY ignore EXTENSION Enhanced-PCH- +Capability PRESENCE conditional }| + -- The IE shall be present if Enhanced FACH Capability IE is set to "Enhanced FACH Capable". +} + +``` + +``` + + { ID id-SixteenQAM-UL-Capability CRITICALITY ignore EXTENSION SixteenQAM-UL- + Capability PRESENCE optional }| + { ID id-HSDSCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION HSDSCH-MACdPDU- + SizeCapability PRESENCE optional }| + { ID id-MBSFN-Only-Mode-Capability CRITICALITY ignore EXTENSION MBSFN-Only-Mode- + Capability PRESENCE optional }| + { ID id-F-DPCH-SlotFormatCapability CRITICALITY ignore EXTENSION F-DPCH- + SlotFormatCapability PRESENCE optional }| + { ID id-E-DCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION E-DCH-MACdPDU- + SizeCapability PRESENCE optional }| + { ID id-Common-EDCH-Capability CRITICALITY ignore EXTENSION Common-EDCH-Capability + PRESENCE optional }| + { ID id-E-AI-Capability CRITICALITY ignore EXTENSION E-AI-Capability + PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH + Capable". + { ID id-Enhanced-UE-DRX-Capability CRITICALITY ignore EXTENSION Enhanced-UE-DRX- + Capability PRESENCE optional }| + { ID id-Enhanced-UE-DRX-CapabilityLCR CRITICALITY ignore EXTENSION Enhanced-UE-DRX- + Capability PRESENCE optional }| + { ID id-E-DPCCH-Power-Boosting-Capability CRITICALITY ignore EXTENSION E-DPCCH-Power- + Boosting-Capability PRESENCE optional }| + { ID id-SixtyfourQAM-DL-MIMO-Combined-Capability CRITICALITY ignore EXTENSION SixtyfourQAM- + DL-MIMO-Combined-Capability PRESENCE optional}| + { ID id-Multi-Cell-Capability-Info CRITICALITY ignore EXTENSION Multi-Cell-Capability- + Info PRESENCE optional }| + { ID id-Semi-PersistentScheduling-CapabilityLCR CRITICALITY ignore EXTENSION Semi- + PersistentScheduling-CapabilityLCR PRESENCE optional }| + { ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR CRITICALITY ignore EXTENSION + ContinuousPacketConnectivity-DRX-CapabilityLCR PRESENCE optional }| + { ID id-Common-E-DCH-HSDPCCCH-Capability CRITICALITY ignore EXTENSION Common-E-DCH-HSDPCCCH- + Capability PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH + Capable". + { ID id-MIMO-Power-Offset-For-S-CPICH-Capability CRITICALITY ignore EXTENSION MIMO- + PowerOffsetForS-CPICHCapability PRESENCE optional }| + { ID id-TxDiversityOnDLControlChannelsByMIMOUECapability CRITICALITY ignore EXTENSION + TxDiversityOnDLControlChannelsByMIMOUECapability PRESENCE optional }| + { ID id-Single-Stream-MIMO-Capability CRITICALITY ignore EXTENSION Single-Stream-MIMO- + Capability PRESENCE optional }| + { ID id-Dual-Band-Capability-Info CRITICALITY ignore EXTENSION Dual-Band-Capability- + Info PRESENCE optional }| + { ID id-CellPortion-CapabilityLCR CRITICALITY ignore EXTENSION CellPortion- + CapabilityLCR PRESENCE optional }| + { ID id-Cell-Capability-Container CRITICALITY ignore EXTENSION Cell-Capability- + Container PRESENCE optional }| + { ID id-TS0-CapabilityLCR CRITICALITY ignore EXTENSION TS0-CapabilityLCR + PRESENCE optional }| + { ID id-PrecodingWeightSetRestriction CRITICALITY ignore EXTENSION + PrecodingWeightSetRestriction PRESENCE optional }| + { ID id-Cell-Capability-Container-TDD-LCR CRITICALITY ignore EXTENSION Cell-Capability- + Container-TDD-LCR PRESENCE optional }| + { ID id-MU-MIMO-Capability-ContainerLCR CRITICALITY ignore EXTENSION MU-MIMO-Capability- + ContainerLCR PRESENCE optional }| + { ID id-Adaptive-Special-Burst-Power-CapabilityLCR CRITICALITY ignore EXTENSION Adaptive- + Special-Burst-Power-CapabilityLCR PRESENCE optional }, + ... + } + + Local-Cell-Group-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF + ProtocolIE-Single-Container { Local-Cell-Group-InformationItemIE-AuditRsp } + + Local-Cell-Group-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-Group-InformationItem-AuditRsp CRITICALITY ignore TYPE Local-Cell-Group- + InformationItem-AuditRsp PRESENCE mandatory} + } + + Local-Cell-Group-InformationItem-AuditRsp ::= SEQUENCE { + local-Cell-Group-ID Local-Cell-ID, + dl-or-global-capacityCredit DL-or-Global-CapacityCredit, + ul-capacityCredit UL-CapacityCredit OPTIONAL, + commonChannelsCapacityConsumptionLaw CommonChannelsCapacityConsumptionLaw, + dedicatedChannelsCapacityConsumptionLaw DedicatedChannelsCapacityConsumptionLaw, + iE-Extensions ProtocolExtensionContainer { Local-Cell-Group- + InformationItem-AuditRsp-ExtIEs} OPTIONAL, + ... + } + +``` + +``` + +Local-Cell-Group-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- +DCHCapacityConsumptionLaw PRESENCE optional } | + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- +CapacityConsumptionLaw PRESENCE optional }, + ... +} + +Power-Local-Cell-Group-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF +ProtocolIE-Single-Container {{ Power-Local-Cell-Group-InformationItemIE-AuditRsp }} + +Power-Local-Cell-Group-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-InformationItem-AuditRsp CRITICALITY ignore + TYPE Power-Local-Cell-Group-InformationItem-AuditRsp PRESENCE mandatory} +} + +Power-Local-Cell-Group-InformationItem-AuditRsp ::= SEQUENCE { + power-Local-Cell-Group-ID Local-Cell-ID, + maximumDL-PowerCapability MaximumDL-PowerCapability, + iE-Extensions ProtocolExtensionContainer {{ Power-Local-Cell- +Group-InformationItem-AuditRsp-ExtIEs}} OPTIONAL, + ... +} + +Power-Local-Cell-Group-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- AUDIT FAILURE +-- +-- ***** + +AuditFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AuditFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{AuditFailure-Extensions}} + OPTIONAL, + ... +} + +AuditFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +AuditFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON MEASUREMENT INITIATION REQUEST +-- +-- ***** + +CommonMeasurementInitiationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonMeasurementInitiationRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonMeasurementInitiationRequest- +Extensions}} OPTIONAL, + ... +} + +CommonMeasurementInitiationRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY reject TYPE MeasurementID + PRESENCE mandatory } | + { ID id-CommonMeasurementObjectType-CM-Rqst CRITICALITY reject TYPE +CommonMeasurementObjectType-CM-Rqst PRESENCE mandatory } | + { ID id-CommonMeasurementType CRITICALITY reject TYPE CommonMeasurementType + PRESENCE mandatory } | + { ID id-MeasurementFilterCoefficient CRITICALITY reject TYPE +MeasurementFilterCoefficient PRESENCE optional } | + { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics + PRESENCE mandatory } | +} + +``` + +``` + + { ID id-SFNReportingIndicator CRITICALITY reject TYPE FNReportingIndicator + PRESENCE mandatory }| + { ID id-SFN CRITICALITY reject TYPE SFN + PRESENCE optional }, + ... +} + +CommonMeasurementInitiationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-CommonMeasurementAccuracy CRITICALITY reject EXTENSION + CommonMeasurementAccuracy PRESENCE optional}| + { ID id-MeasurementRecoveryBehavior CRITICALITY ignore EXTENSION + MeasurementRecoveryBehavior PRESENCE optional }| + { ID id-RTWP-ReportingIndicator CRITICALITY reject EXTENSION RTWP- + ReportingIndicator PRESENCE optional}| + { ID id-RTWP-CellPortion-ReportingIndicator CRITICALITY reject EXTENSION RTWP- + CellPortion-ReportingIndicator PRESENCE optional}| + { ID id-Reference-ReceivedTotalWideBandPowerReporting CRITICALITY ignore EXTENSION Reference- + ReceivedTotalWideBandPowerReporting PRESENCE optional}| + { ID id-GANSS-Time-ID CRITICALITY ignore EXTENSION GANSS- + Time-ID PRESENCE optional}, + ... +} + +CommonMeasurementObjectType-CM-Rqst ::= CHOICE { + cell Cell-CM-Rqst, + rACH RACH-CM-Rqst, + notUsed-cPCH NULL, + ... + extension-CommonMeasurementObjectType-CM-Rqst Extension-CommonMeasurementObjectType-CM- +Rqst +} + +Extension-CommonMeasurementObjectType-CM-Rqst ::= ProtocolIE-Single-Container { { Extension- +CommonMeasurementObjectType-CM-RqstIE } } + +Extension-CommonMeasurementObjectType-CM-RqstIE NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-choice-CM-Rqst CRITICALITY reject TYPE PowerLocalCellGroup-CM- +Rqst PRESENCE mandatory }| + { ID id-ERACH-CM-Rqst CRITICALITY reject TYPE ERACH-CM-Rqst + PRESENCE mandatory} + -- FDD only +} + +ERACH-CM-Rqst ::= SEQUENCE { + c-ID C-ID, + iE-Extensions ProtocolExtensionContainer { { ERACHItem-CM-Rqst-ExtIEs} } + OPTIONAL, + ... +} + +ERACHItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-CM-Rqst ::= SEQUENCE { + c-ID C-ID, + timeSlot TimeSlot OPTIONAL, -- Applicable to 3.84Mcps TDD and +7.68Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { CellItem-CM-Rqst-ExtIEs} } + OPTIONAL, + ... +} + +CellItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TimeSlotLCR-CM-Rqst CRITICALITY reject EXTENSION TimeSlotLCR + PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + {ID id-NeighbouringCellMeasurementInformation CRITICALITY ignore EXTENSION + NeighbouringCellMeasurementInformation PRESENCE optional }| + {ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN + PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD when using multiple frequencies and the requested common + measurementtype is the one except for "HS-DSCH Required Power" or "HS-DSCH Provided Bit Rate" + {ID id-UPPCHPositionLCR CRITICALITY reject EXTENSION UPPCHPositionLCR + PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only +} + +``` + +``` + + { ID id-AdditionalTimeSlotListLCR CRITICALITY ignore EXTENSION +AdditionalTimeSlotListLCR PRESENCE optional }, + -- Applicable to 1.28Mcps TDD only + ... +} + +RACH-CM-Rqst ::= SEQUENCE { + c-ID C-ID, + commonTransportChannelID CommonTransportChannelID, + iE-Extensions ProtocolExtensionContainer { { RACHItem-CM-Rqst-ExtIEs } } +OPTIONAL, + ... +} + +RACHItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PowerLocalCellGroup-CM-Rqst ::= SEQUENCE { + powerLocalCellGroupID Local-Cell-ID, + iE-Extensions ProtocolExtensionContainer { { PowerLocalCellGroup-CM-Rqst-ExtIEs } } +OPTIONAL, + ... +} + +PowerLocalCellGroup-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- **************************************************************************** +-- +-- COMMON MEASUREMENT INITIATION RESPONSE +-- +-- **************************************************************************** + +CommonMeasurementInitiationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { CommonMeasurementInitiationResponse-IEs } }, + protocolExtensions ProtocolExtensionContainer { { CommonMeasurementInitiationResponse-Extensions } } +OPTIONAL, + ... +} + +CommonMeasurementInitiationResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID + PRESENCE mandatory } | + { ID id-CommonMeasurementObjectType-CM-Rsp CRITICALITY ignore TYPE CommonMeasurementObjectType-CM-Rsp + PRESENCE optional } | + { ID id-SFN CRITICALITY ignore TYPE SFN + PRESENCE optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +CommonMeasurementInitiationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-CommonMeasurementAccuracy CRITICALITY ignore EXTENSION CommonMeasurementAccuracy + PRESENCE optional } | + { ID id-MeasurementRecoverySupportIndicator CRITICALITY ignore EXTENSION MeasurementRecoverySupportIndicator + PRESENCE optional } | + { ID id-Reference-ReceivedTotalWideBandPowerSupportIndicator CRITICALITY ignore + EXTENSION Reference-ReceivedTotalWideBandPowerSupportIndicator + PRESENCE optional } | + { ID id-Reference-ReceivedTotalWideBandPower CRITICALITY ignore + EXTENSION Reference-ReceivedTotalWideBandPower PRESENCE optional }, + ... +} + +CommonMeasurementObjectType-CM-Rsp ::= CHOICE { + cell Cell-CM-Rsp, + rACH RACH-CM-Rsp, + notUsed-cPCH NULL, + ..., + extension-CommonMeasurementObjectType-CM-Rsp Extension-CommonMeasurementObjectType-CM-Rsp +} + +Extension-CommonMeasurementObjectType-CM-Rsp ::= ProtocolIE-Single-Container { { Extension-CommonMeasurementObjectType-CM-RspIE } } +``` + +``` + +Extension-CommonMeasurementObjectType-CM-RspIE NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-choice-CM-Rsp CRITICALITY ignore TYPE +PowerLocalCellGroup-CM-Rsp PRESENCE mandatory }| + { ID id-ERACH-CM-Rsp CRITICALITY ignore TYPE ERACH-CM-Rsp +PRESENCE mandatory } + -- FDD only +} + +ERACH-CM-Rsp ::= SEQUENCE { + commonMeasurementValue CommonMeasurementValue, + iE-Extensions ProtocolExtensionContainer { { ERACHItem-CM-Rsp-ExtIEs} } +OPTIONAL, + ... +} + +ERACHItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-CM-Rsp ::= SEQUENCE { + commonMeasurementValue CommonMeasurementValue, + iE-Extensions ProtocolExtensionContainer { { CellItem-CM-Rsp-ExtIEs} } +OPTIONAL, + ... +} + +CellItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + {ID id-AdditionalMeasurementValueList CRITICALITY ignore EXTENSION +AdditionalMeasurementValueList PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + {ID id-TimeSlotMeasurementValueListLCR CRITICALITY ignore EXTENSION +TimeSlotMeasurementValueListLCR PRESENCE optional }, + -- Applicable to 1.28Mcps TDD, this IE is for the measurement value from the Primary frequency + ... +} + +RACH-CM-Rsp ::= SEQUENCE { + commonMeasurementValue CommonMeasurementValue, + iE-Extensions ProtocolExtensionContainer { { RACHItem-CM-Rsp-ExtIEs} } +OPTIONAL, + ... +} + +RACHItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PowerLocalCellGroup-CM-Rsp ::= SEQUENCE { + commonMeasurementValue CommonMeasurementValue, + iE-Extensions ProtocolExtensionContainer { { PowerLocalCellGroup-CM-Rsp- +ExtIEs} } OPTIONAL, + ... +} + +PowerLocalCellGroup-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON MEASUREMENT INITIATION FAILURE +-- +-- ***** + +CommonMeasurementInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {CommonMeasurementInitiationFailure-IEs} }, + protocolExtensions ProtocolExtensionContainer { {CommonMeasurementInitiationFailure- +Extensions} } OPTIONAL, + ... +} + +CommonMeasurementInitiationFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID +PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause +PRESENCE mandatory }| +} + +``` + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +CommonMeasurementInitiationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON MEASUREMENT REPORT +-- +-- ***** + +CommonMeasurementReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonMeasurementReport-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonMeasurementReport-Extensions}} + OPTIONAL, + ... +} + +CommonMeasurementReport-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID + PRESENCE mandatory }| + { ID id-CommonMeasurementObjectType-CM-Rprt CRITICALITY ignore TYPE + CommonMeasurementObjectType-CM-Rprt PRESENCE mandatory }| + { ID id-SFN CRITICALITY ignore TYPE SFN + PRESENCE optional }, + ... +} + +CommonMeasurementReport-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MeasurementRecoveryReportingIndicator CRITICALITY ignore EXTENSION + MeasurementRecoveryReportingIndicator PRESENCE optional }| + { ID id-Reference-ReceivedTotalWideBandPower CRITICALITY ignore EXTENSION Reference- + ReceivedTotalWideBandPower PRESENCE optional }, + ... +} + +CommonMeasurementObjectType-CM-Rprt ::= CHOICE { + cell Cell-CM-Rprt, + rACH RACH-CM-Rprt, + notUsed-cPCH NULL, + ..., + extension-CommonMeasurementObjectType-CM-Rprt Extension-CommonMeasurementObjectType-CM- +Rprt +} + +Extension-CommonMeasurementObjectType-CM-Rprt ::= ProtocolIE-Single-Container {{ Extension- +CommonMeasurementObjectType-CM-RprtIE }} + +Extension-CommonMeasurementObjectType-CM-RprtIE NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-choice-CM-Rprt CRITICALITY ignore TYPE + PowerLocalCellGroup-CM-Rprt PRESENCE mandatory }| + { ID id-ERACH-CM-Rprt CRITICALITY ignore TYPE ERACH-CM-Rprt + PRESENCE mandatory }, + ... +} + +ERACH-CM-Rprt ::= SEQUENCE { + commonMeasurementValueInformation CommonMeasurementValueInformation, + iE-Extensions ProtocolExtensionContainer {{ ERACHItem-CM-Rprt-ExtIEs }} + OPTIONAL, + ... +} + +ERACHItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-CM-Rprt ::= SEQUENCE { + commonMeasurementValueInformation CommonMeasurementValueInformation, + iE-Extensions ProtocolExtensionContainer {{ CellItem-CM-Rprt-ExtIEs }} + OPTIONAL, + ... +} + +``` + +``` + +CellItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + {ID id-C-ID CRITICALITY ignore EXTENSION C-ID + PRESENCE optional}| + {ID id-AdditionalMeasurementValueList CRITICALITY ignore EXTENSION + AdditionalMeasurementValueList PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + {ID id-TimeSlotMeasurementValueListLCR CRITICALITY ignore EXTENSION + TimeSlotMeasurementValueListLCR PRESENCE optional }, + -- Applicable to 1.28Mcps TDD, this IE is for the measurement value from the Primary frequency + ... +} + +RACH-CM-Rprt ::= SEQUENCE { + commonMeasurementValueInformation CommonMeasurementValueInformation, + iE-Extensions ProtocolExtensionContainer {{ RACHItem-CM-Rprt-ExtIEs }} + OPTIONAL, + ... +} + +RACHItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + {ID id-C-ID CRITICALITY ignore EXTENSION C-ID PRESENCE optional}, + ... +} + +PowerLocalCellGroup-CM-Rprt ::= SEQUENCE { + commonMeasurementValueInformation CommonMeasurementValueInformation, + iE-Extensions ProtocolExtensionContainer {{ PowerLocalCellGroup-CM-Rprt- + ExtIEs}} OPTIONAL, + ... +} + +PowerLocalCellGroup-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON MEASUREMENT TERMINATION REQUEST +-- +-- ***** + +CommonMeasurementTerminationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonMeasurementTerminationRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonMeasurementTerminationRequest- + Extensions}} OPTIONAL, + ... +} + +CommonMeasurementTerminationRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID + PRESENCE mandatory }, + ... +} + +CommonMeasurementTerminationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- COMMON MEASUREMENT FAILURE INDICATION +-- +-- ***** + +CommonMeasurementFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CommonMeasurementFailureIndication- + IEs}}, + protocolExtensions ProtocolExtensionContainer {{CommonMeasurementFailureIndication- + Extensions}} OPTIONAL, + ... +} + +CommonMeasurementFailureIndication-IEs NBAP-PROTOCOL-IES ::= { + { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID PRESENCE + mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE + mandatory }, +} + +``` + +``` + + ... +} + +CommonMeasurementFailureIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- **************************************************************************** +-- +-- CELL SETUP REQUEST FDD +-- +-- **************************************************************************** + +CellSetupRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellSetupRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellSetupRequestFDD-Extensions}} + OPTIONAL, + ... +} + +CellSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-ID CRITICALITY reject TYPE Local-Cell-ID + PRESENCE mandatory }| + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE ConfigurationGenerationID + PRESENCE mandatory }| + { ID id-T-Cell CRITICALITY reject TYPE T-Cell + PRESENCE mandatory }| + { ID id-UARFCNforNu CRITICALITY reject TYPE UARFCN + PRESENCE mandatory }| + { ID id-UARFCNforNd CRITICALITY reject TYPE UARFCN + PRESENCE mandatory }| + { ID id-MaximumTransmissionPower CRITICALITY reject TYPE MaximumTransmissionPower + PRESENCE mandatory }| + { ID id-Closed-Loop-Timing-Adjustment-Mode CRITICALITY reject TYPE Closedlooptimingadjustmentmode + PRESENCE optional }| + { ID id-PrimaryScramblingCode CRITICALITY reject TYPE PrimaryScramblingCode + PRESENCE mandatory }| + { ID id-Synchronisation-Configuration-Cell-SetupRqst CRITICALITY reject TYPE Synchronisation-Configuration-Cell-SetupRqst + PRESENCE mandatory }| + { ID id-DL-TPC-Pattern01Count CRITICALITY reject TYPE DL-TPC-Pattern01Count + PRESENCE mandatory }| + { ID id-PrimarySCH-Information-Cell-SetupRqstFDD CRITICALITY reject TYPE PrimarySCH-Information-Cell-SetupRqstFDD + PRESENCE mandatory }| + { ID id-SecondarySCH-Information-Cell-SetupRqstFDD CRITICALITY reject TYPE SecondarySCH-Information-Cell-SetupRqstFDD + PRESENCE mandatory }| + { ID id-PrimaryCPICH-Information-Cell-SetupRqstFDD CRITICALITY reject TYPE PrimaryCPICH-Information-Cell-SetupRqstFDD + PRESENCE mandatory }| + { ID id-SecondaryCPICH-InformationList-Cell-SetupRqstFDD CRITICALITY reject TYPE SecondaryCPICH-InformationList-Cell-SetupRqstFDD + PRESENCE optional }| + { ID id-PrimaryCCPCH-Information-Cell-SetupRqstFDD CRITICALITY reject TYPE PrimaryCCPCH-Information-Cell-SetupRqstFDD + PRESENCE mandatory }| + { ID id-Limited-power-increase-information-Cell-SetupRqstFDD CRITICALITY reject TYPE Limited-power-increase-information-Cell-SetupRqstFDD + PRESENCE mandatory }, + ... +} + +CellSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-IPDLParameter-Information-Cell-SetupRqstFDD CRITICALITY reject EXTENSION IPDLParameter-Information-Cell-SetupRqstFDD + PRESENCE optional }| + { ID id-CellPortion-InformationList-Cell-SetupRqstFDD CRITICALITY reject EXTENSION CellPortion-InformationList-Cell-SetupRqstFDD + PRESENCE optional }| + { ID id-MIMO-PilotConfiguration CRITICALITY reject EXTENSION MIMO-PilotConfiguration + PRESENCE optional }| + { ID id-MIMO-PilotConfigurationExtension CRITICALITY reject EXTENSION MIMO-PilotConfigurationExtension + PRESENCE optional }| + { ID id-MIMO-withfourtransmitantennas-PilotConfiguration CRITICALITY reject EXTENSION MIMO-withfourtransmitantennas-PilotConfiguration + PRESENCE optional }, + ... +} + +Synchronisation-Configuration-Cell-SetupRqst ::= SEQUENCE { + n-INSYNC-IND N-INSYNC-IND, + n-OUTSYNC-IND N-OUTSYNC-IND, + t-RLFFAILURE T-RLFFAILURE, + iE-Extensions ProtocolExtensionContainer { { Synchronisation-Configuration-Cell-SetupRqst-ExtIEs} } + OPTIONAL, +} + +``` + +``` + + ... + } + + Synchronisation-Configuration-Cell-SetupRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PrimarySCH-Information-Cell-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + primarySCH-Power DL-Power, + tSTD-Indicator TSTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { PrimarySCH-Information- + Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PrimarySCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SecondarySCH-Information-Cell-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + secondarySCH-Power DL-Power, + tSTD-Indicator TSTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { SecondarySCH-Information- + Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + SecondarySCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PrimaryCPICH-Information-Cell-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + primaryCPICH-Power PrimaryCPICH-Power, + transmitDiversityIndicator TransmitDiversityIndicator, + iE-Extensions ProtocolExtensionContainer { { PrimaryCPICH-Information- + Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PrimaryCPICH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SecondaryCPICH-InformationList-Cell-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF + ProtocolIE-Single-Container{{ SecondaryCPICH-InformationItemIE-Cell-SetupRqstFDD }} + + SecondaryCPICH-InformationItemIE-Cell-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-SecondaryCPICH-InformationItem-Cell-SetupRqstFDD CRITICALITY reject TYPE + SecondaryCPICH-InformationItem-Cell-SetupRqstFDD PRESENCE mandatory} + } + + SecondaryCPICH-InformationItem-Cell-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + dl-ScramblingCode DL-ScramblingCode, + fdd-DL-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, + secondaryCPICH-Power DL-Power, + transmitDiversityIndicator TransmitDiversityIndicator, + iE-Extensions ProtocolExtensionContainer { { SecondaryCPICH- + InformationItem-Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + SecondaryCPICH-InformationItem-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PrimaryCCPCH-Information-Cell-SetupRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + bCH-information BCH-Information-Cell-SetupRqstFDD, + sTTD-Indicator STTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { PrimaryCCPCH-Information- + Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +PrimaryCCPCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +BCH-Information-Cell-SetupRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + bCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { BCH-Information-Cell- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +BCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Limited-power-increase-information-Cell-SetupRqstFDD ::= SEQUENCE { + powerRaiseLimit PowerRaiseLimit, + dLPowerAveragingWindowSize DLPowerAveragingWindowSize, + iE-Extensions ProtocolExtensionContainer { { Limited-power-increase- +information-Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +Limited-power-increase-information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +IPDLParameter-Information-Cell-SetupRqstFDD ::= SEQUENCE { + iPDL-FDD-Parameters IPDL-FDD-Parameters, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- +Information-Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +IPDLParameter-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellPortion-InformationList-Cell-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF +ProtocolIE-Single-Container{{ CellPortion-InformationItemIE-Cell-SetupRqstFDD }} + +CellPortion-InformationItemIE-Cell-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-CellPortion-InformationItem-Cell-SetupRqstFDD CRITICALITY reject TYPE CellPortion- +InformationItem-Cell-SetupRqstFDD PRESENCE mandatory } +} + +CellPortion-InformationItem-Cell-SetupRqstFDD ::= SEQUENCE { + cellPortionID CellPortionID, + associatedSecondaryCPICH CommonPhysicalChannelID, + maximumTransmissionPowerforCellPortion MaximumTransmissionPower, + iE-Extensions ProtocolExtensionContainer { { CellPortion- +InformationItem-Cell-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +CellPortion-InformationItem-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- **************************************************************************** +-- +-- CELL SETUP REQUEST TDD +-- +-- **************************************************************************** + +CellSetupRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellSetupRequestTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellSetupRequestTDD-Extensions}} + OPTIONAL, + ... +} + +CellSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-ID CRITICALITY reject TYPE Local-Cell-ID + PRESENCE mandatory } | +} + +``` + +``` + + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE +ConfigurationGenerationID PRESENCE mandatory }| + { ID id-UARFCNforNt CRITICALITY reject TYPE UARFCN + PRESENCE mandatory }| -- For 1.28Mcps TDD, if multiple frequencies exist within +the cell indicated by C-ID, this IE indicates the frequency of Primary frequency + { ID id-CellParameterID CRITICALITY reject TYPE CellParameterID + PRESENCE mandatory }| + -- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE indicate the Preamble +code used in the Speial Time Slot (TS 25.221 [19]) + { ID id-MaximumTransmissionPower CRITICALITY reject TYPE +MaximumTransmissionPower PRESENCE mandatory }| + { ID id-TransmissionDiversityApplied CRITICALITY reject TYPE +TransmissionDiversityApplied PRESENCE mandatory }| + { ID id-SyncCase CRITICALITY reject TYPE SyncCase + PRESENCE mandatory }| + { ID id-Synchronisation-Configuration-Cell-SetupRqst CRITICALITY reject TYPE +Synchronisation-Configuration-Cell-SetupRqst PRESENCE mandatory }| + { ID id-DPCHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE mandatory }| -- This IE shall be ignored by the Node B. + { ID id-PUSCHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE mandatory }| -- This IE shall be ignored by the Node B. + { ID id-PRACHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE mandatory }| -- This IE shall be ignored by the Node B. + { ID id-TimingAdvanceApplied CRITICALITY reject TYPE +TimingAdvanceApplied PRESENCE mandatory }| + { ID id-SCH-Information-Cell-SetupRqstTDD CRITICALITY reject TYPE SCH- +Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for 3.84Mcps TDD +and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD + { ID id-PCCPCH-Information-Cell-SetupRqstTDD CRITICALITY reject TYPE PCCPCH- +Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for 3.84Mcps TDD, Not +Applicable to 1.28Mcps TDD or 7.68Mcps TDD + { ID id-TimeSlotConfigurationList-Cell-SetupRqstTDD CRITICALITY reject TYPE +TimeSlotConfigurationList-Cell-SetupRqstTDD PRESENCE optional }, -- Mandatory for 3.84Mcps TDD +and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD + ... +} + +``` + +``` + +CellSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD CRITICALITY reject EXTENSION +TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for +1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. If multiple frequencies exist within +the cell indicated by C-ID, this IE indicates the Time Slot configuration of Primary frequency. + { ID id-PCCPCH-LCR-Information-Cell-SetupRqstTDD CRITICALITY reject EXTENSION +PCCPCH-LCR-Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for +1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD, For 1.28 Mcps TDD, if the cell is +operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]). + { ID id-DwPCH-LCR-Information-Cell-SetupRqstTDD CRITICALITY reject EXTENSION DwPCH- +LCR-Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for 1.28Mcps +TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-ReferenceSFNOffset CRITICALITY ignore EXTENSION +ReferenceSFNOffset PRESENCE optional }| + { ID id-IPDLParameter-Information-Cell-SetupRqstTDD CRITICALITY reject EXTENSION +IPDLParameter-Information-Cell-SetupRqstTDD PRESENCE optional }| -- Applicable to +3.84Mcps TDD and 7.68Mcps TDD only + { ID id-IPDLParameter-Information-LCR-Cell-SetupRqstTDD CRITICALITY reject EXTENSION +IPDLParameter-Information-LCR-Cell-SetupRqstTDD PRESENCE optional }| -- Applicable to 1.28Mcps +TDD only + { ID id-PCCPCH-768-Information-Cell-SetupRqstTDD CRITICALITY reject EXTENSION +PCCPCH-768-Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for +7.68Mcps TDD, Not Applicable to 3.84Mcps TDD or 1.28Mcps TDD + { ID id-SCH-768-Information-Cell-SetupRqstTDD CRITICALITY reject EXTENSION SCH- +768-Information-Cell-SetupRqstTDD PRESENCE optional }| -- Mandatory for 7.68Mcps +TDD, Not Applicable to 3.84Mcps TDD or 1.28Mcps TDD + { ID id-MBSFN-Only-Mode-Indicator-Cell-SetupRqstTDD-LCR CRITICALITY reject EXTENSION MBSFN- +Only-Mode-Indicator PRESENCE optional }| + { ID id-Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD CRITICALITY reject EXTENSION Cell- +Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD PRESENCE optional }, -- Mandatory for 1.28Mcps +TDD when using multiple frequencies + ... +} + +``` + +``` + +SCH-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + syncCaseIndicator SyncCaseIndicator-Cell-SetupRqstTDD-PSCH, + sCH-Power DL-Power, + tSTD-Indicator TSTD-Indicator, +} + +``` + +``` + + iE-Extensions + SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + SCH-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SyncCaseIndicator-Cell-SetupRqstTDD-PSCH ::= ProtocolIE-Single-Container { { SyncCaseIndicatorIE- + Cell-SetupRqstTDD-PSCH } } + + SyncCaseIndicatorIE-Cell-SetupRqstTDD-PSCH NBAP-PROTOCOL-IES ::= { + { ID id-SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH CRITICALITY reject TYPE + SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH PRESENCE mandatory } + } + + SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH ::= CHOICE { + case1 + case2 + ... + } + + Case1-Cell-SetupRqstTDD ::= SEQUENCE { + timeSlot + iE-Extensions + ExtIEs } } OPTIONAL, + ... + } + + Case1Item-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Case2-Cell-SetupRqstTDD ::= SEQUENCE { + sCH-TimeSlot + iE-Extensions + ExtIEs } } OPTIONAL, + ... + } + + Case2Item-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PCCPCH-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID + tdd-PhysicalChannelOffset + repetitionPeriod + repetitionLength + pCCPCH-Power + SCTD-Indicator + iE-Extensions + SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + PCCPCH-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + TimeSlotConfigurationList-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..15)) OF + TimeSlotConfigurationItem-Cell-SetupRqstTDD + + TimeSlotConfigurationItem-Cell-SetupRqstTDD ::= SEQUENCE { + timeSlot + timeSlotStatus + timeSlotDirection + iE-Extensions + TimeSlotConfigurationItem-Cell-SetupRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + TimeSlotConfigurationItem-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MBSFN-Cell-ParameterID-Cell-SetupRqstTDD CRITICALITY reject EXTENSION + CellParameterID PRESENCE optional },-- Applicable only to for MBSFN only mode + ... + } + +``` + +``` + +TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..7)) OF +TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD + +TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD ::= SEQUENCE { + timeSlotLCR TimeSlotLCR, + timeSlotStatus TimeSlotStatus, + timeSlotDirection TimeSlotDirection, + iE-Extensions ProtocolExtensionContainer { +TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Time-Slot-Parameter-ID CRITICALITY reject EXTENSION +CellParameterID PRESENCE optional }, + ... +} + +PCCPCH-LCR-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + pCCPCH-Power PCCPCH-Power, + sCTD-Indicator SCTD-Indicator, + tSTD-Indicator TSTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { PCCPCH-LCR-Information- +Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +PCCPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DwPCH-LCR-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelId CommonPhysicalChannelID, + tSTD-Indicator TSTD-Indicator, + dwPCH-Power DwPCH-Power, + iE-Extensions ProtocolExtensionContainer { { DwPCH-LCR-Information-Cell- +SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +DwPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +IPDLParameter-Information-Cell-SetupRqstTDD ::= SEQUENCE { + iPDL-TDD-Parameters IPDL-TDD-Parameters, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- +Information-Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +IPDLParameter-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +IPDLParameter-Information-LCR-Cell-SetupRqstTDD ::= SEQUENCE { + iPDL-TDD-Parameters-LCR IPDL-TDD-Parameters-LCR, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- +Information-LCR-Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +IPDLParameter-Information-LCR-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PCCPCH-768-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + tdd-PhysicalChannelOffset TDD-PhysicalChannelOffset, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, +} + +``` + +``` + + pCCPCH-Power pCCPCH-Power, + sCTD-Indicator sCTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { pCCPCH-768-Information- +Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + PCCPCH-768-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SCH-768-Information-Cell-SetupRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + syncCaseIndicator SyncCaseIndicator-Cell-SetupRqstTDD-PSCH, + sCH-Power DL-Power, + tSTD-Indicator TSTD-Indicator, + iE-Extensions ProtocolExtensionContainer { { SCH-768-Information-Cell- +SetupRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + SCH-768-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF + Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD + + Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD ::= SEQUENCE { + uARFCN UARFCN, + -- This IE indicates the frequency of Secondary frequency + timeSlotConfigurationList-LCR-Cell-SetupRqstTDD TimeSlotConfigurationList-LCR-Cell- +SetupRqstTDD, + -- This IE indicates the Time Slot configuration of Secondary frequency + iE-Extensions ProtocolExtensionContainer { { Cell-Frequency-Item-LCR- +MulFreq-Cell-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... + } + + Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- CELL SETUP RESPONSE + -- + -- ***** + + CellSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellSetupResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellSetupResponse-Extensions}} + OPTIONAL, + ... + } + + CellSetupResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + CellSetupResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- CELL SETUP FAILURE + -- + -- ***** + + CellSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellSetupFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellSetupFailure-Extensions}} + OPTIONAL, + ... + } + +``` + +``` + +CellSetupFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +CellSetupFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- CELL RECONFIGURATION REQUEST FDD +-- +-- ***** + +CellReconfigurationRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellReconfigurationRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellReconfigurationRequestFDD-Extensions}} + OPTIONAL, + ... +} + +CellReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE + ConfigurationGenerationID PRESENCE mandatory }| + { ID id-MaximumTransmissionPower CRITICALITY reject TYPE + MaximumTransmissionPower PRESENCE optional }| + { ID id-Synchronisation-Configuration-Cell-ReconfRqst CRITICALITY reject TYPE + Synchronisation-Configuration-Cell-ReconfRqst PRESENCE optional }| + { ID id-PrimarySCH-Information-Cell-ReconfRqstFDD CRITICALITY reject TYPE + PrimarySCH-Information-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-SecondarySCH-Information-Cell-ReconfRqstFDD CRITICALITY reject TYPE + SecondarySCH-Information-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-PrimaryCPICH-Information-Cell-ReconfRqstFDD CRITICALITY reject TYPE + PrimaryCPICH-Information-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-SecondaryCPICH-InformationList-Cell-ReconfRqstFDD CRITICALITY reject TYPE + SecondaryCPICH-InformationList-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-PrimaryCCPCH-Information-Cell-ReconfRqstFDD CRITICALITY reject TYPE + PrimaryCCPCH-Information-Cell-ReconfRqstFDD PRESENCE optional }, + ... +} + +CellReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-IPDLParameter-Information-Cell-ReconfRqstFDD CRITICALITY reject EXTENSION + IPDLParameter-Information-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-CellPortion-InformationList-Cell-ReconfRqstFDD CRITICALITY reject EXTENSION + CellPortion-InformationList-Cell-ReconfRqstFDD PRESENCE optional }| + { ID id-MIMO-PilotConfiguration CRITICALITY reject EXTENSION MIMO- + PilotConfiguration PRESENCE optional }| + { ID id-MIMO-PilotConfigurationExtension CRITICALITY reject EXTENSION MIMO- + PilotConfigurationExtension PRESENCE optional }| + { ID id-DormantModeIndicator CRITICALITY reject EXTENSION + DormantModeIndicator PRESENCE optional }| + { ID id-MIMO-withfourtransmitantennas-PilotConfiguration CRITICALITY reject EXTENSION MIMO- + withfourtransmitantennas-PilotConfiguration PRESENCE optional }, + ... +} + +Synchronisation-Configuration-Cell-ReconfRqst ::= SEQUENCE { + n-INSYNC-IND N-INSYNC-IND, + n-OUTSYNC-IND N-OUTSYNC-IND, + t-RLFFAILURE, + iE-Extensions ProtocolExtensionContainer { { Synchronisation-Configuration-Cell- + ReconfRqst-ExtIEs} } OPTIONAL, + ... +} + +Synchronisation-Configuration-Cell-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PrimarySCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE { + +``` + +``` + + commonPhysicalChannelID CommonPhysicalChannelID, + primarySCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { PrimarySCH-Information- +Cell-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PrimarySCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SecondarySCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + secondarySCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { SecondarySCH-Information- +Cell-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + SecondarySCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PrimaryCPICH-Information-Cell-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + primaryCPICH-Power PrimaryCPICH-Power, + iE-Extensions ProtocolExtensionContainer { { PrimaryCPICH-Information- +Cell-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PrimaryCPICH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SecondaryCPICH-InformationList-Cell-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF + ProtocolIE-Single-Container{{ SecondaryCPICH-InformationItemIE-Cell-ReconfRqstFDD }} + + SecondaryCPICH-InformationItemIE-Cell-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD CRITICALITY reject TYPE + SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD PRESENCE mandatory } + } + + SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + secondaryCPICH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { SecondaryCPICH- +InformationItem-Cell-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PrimaryCCPCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE { + bCH-information BCH-information-Cell-ReconfRqstFDD, + iE-Extensions ProtocolExtensionContainer { { PrimaryCCPCH-Information- +Cell-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PrimaryCCPCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + BCH-information-Cell-ReconfRqstFDD ::= SEQUENCE { + commonTransportChannelID CommonTransportChannelID, + bCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { BCH-information-Cell- +ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + BCH-information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +IPDLParameter-Information-Cell-ReconfRqstFDD ::= SEQUENCE { + iPDL-FDD-Parameters IPDL-FDD-Parameters OPTIONAL, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- +Information-Cell-ReconfRqstFDD-ExtIEs } } OPTIONAL, + ... +} + +IPDLParameter-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellPortion-InformationList-Cell-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) +OF ProtocolIE-Single-Container{{ CellPortion-InformationItemIE-Cell-ReconfRqstFDD }} + +CellPortion-InformationItemIE-Cell-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-CellPortion-InformationItem-Cell-ReconfRqstFDD CRITICALITY reject TYPE CellPortion- +InformationItem-Cell-ReconfRqstFDD PRESENCE mandatory} +} + +CellPortion-InformationItem-Cell-ReconfRqstFDD ::= SEQUENCE { + cellPortionID CellPortionID, + maximumTransmissionPowerforCellPortion MaximumTransmissionPower, + iE-Extensions ProtocolExtensionContainer { { CellPortion- +InformationItem-Cell-ReconfRqstFDD-ExtIEs } } OPTIONAL, + ... +} + +CellPortion-InformationItem-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- CELL RECONFIGURATION REQUEST TDD +-- +-- ***** + +CellReconfigurationRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellReconfigurationRequestTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellReconfigurationRequestTDD-Extensions}} + OPTIONAL, + ... +} + +CellReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-ConfigurationGenerationID CRITICALITY reject TYPE +ConfigurationGenerationID PRESENCE mandatory }| + { ID id-Synchronisation-Configuration-Cell-ReconfRqst CRITICALITY reject TYPE +Synchronisation-Configuration-Cell-ReconfRqst PRESENCE optional }| + { ID id-TimingAdvanceApplied CRITICALITY reject TYPE +TimingAdvanceApplied PRESENCE optional }| + { ID id-SCH-Information-Cell-ReconfRqstTDD CRITICALITY reject TYPE SCH- +Information-Cell-ReconfRqstTDD PRESENCE optional }| + -- Applicable to 3.84Mcps TDD only + { ID id-PCCPCH-Information-Cell-ReconfRqstTDD CRITICALITY reject TYPE PCCPCH- +Information-Cell-ReconfRqstTDD PRESENCE optional }| + -- Not applicable to 7.68Mcps TDD only. For 1.28 Mcps TDD, if the cell is operating in MBSFN +only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]). + { ID id-MaximumTransmissionPower CRITICALITY reject TYPE +MaximumTransmissionPower PRESENCE optional }| + { ID id-DPCHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE optional }| + -- This IE shall be ignored by the Node B. + { ID id-PUSCHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE optional }| + -- This IE shall be ignored by the Node B. + { ID id-PRACHConstant CRITICALITY reject TYPE ConstantValue + PRESENCE optional }| + -- This IE shall be ignored by the Node B. + { ID id-TimeSlotConfigurationList-Cell-ReconfRqstTDD CRITICALITY reject TYPE +TimeSlotConfigurationList-Cell-ReconfRqstTDD PRESENCE optional }| + -- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD only. Not Applicable to 1.28Mcps TDD. + ... +} + +``` + +``` + +CellReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION + TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only, If multiple frequencies exist within the cell indicated by C-ID, this IE + indicates the Time Slot reconfiguration of Primary frequency + { ID id-DwPCH-LCR-Information-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION DwPCH- + LCR-Information-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to 1.28Mcps TDD + only + { ID id-IPDLParameter-Information-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION + IPDLParameter-Information-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to + 3.84Mcps TDD and 7.68Mcps TDD only + { ID id-IPDLParameter-Information-LCR-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION + IPDLParameter-Information-LCR-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only + { ID id-SCH-768-Information-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION SCH- + 768-Information-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to 7.68Mcps + TDD only + { ID id-PCCPCH-768-Information-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION + PCCPCH-768-Information-Cell-ReconfRqstTDD PRESENCE optional }| -- Applicable to + 7.68Mcps TDD only + { ID id-UARFCN-Adjustment CRITICALITY reject EXTENSION + UARFCN-Adjustment PRESENCE optional }| -- Applicable to 1.28Mcps TDD when using multiple + frequencies + { ID id-DormantModeIndicator CRITICALITY reject EXTENSION + DormantModeIndicator PRESENCE optional }, + ... +} + +SCH-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + sCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { PSCH-Information-Cell- + ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +PSCH-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PCCPCH-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID CommonPhysicalChannelID, + pCCPCH-Power PCCPCH-Power, + iE-Extensions ProtocolExtensionContainer { { PCCPCH-Information-Cell- + ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +PCCPCH-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimeSlotConfigurationList-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..15)) OF +TimeSlotConfigurationItem-Cell-ReconfRqstTDD + +TimeSlotConfigurationItem-Cell-ReconfRqstTDD ::= SEQUENCE { + timeSlot TimeSlot, + timeSlotStatus TimeSlotStatus, + timeSlotDirection TimeSlotDirection, + iE-Extensions ProtocolExtensionContainer { { + TimeSlotConfigurationItem-Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +TimeSlotConfigurationItem-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MBSFN-Cell-ParameterID-Cell-ReconfRqstTDD CRITICALITY reject EXTENSION + CellParameterID PRESENCE optional }, + ... +} + +TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..7)) OF +TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD + +TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD ::= SEQUENCE { + timeSlotLCR TimeSlotLCR, + timeSlotStatus TimeSlotStatus, + timeSlotDirection TimeSlotDirection, + +``` + +``` + + iE-Extensions + TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD-ExtIEs } OPTIONAL, + ... + } + + TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + DwPCH-LCR-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelId CommonPhysicalChannelID, + dwPCH-Power DwPCH-Power, + iE-Extensions ProtocolExtensionContainer { { DwPCH-LCR-Information- + Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + DwPCH-LCR-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + IPDLParameter-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + iPDL-TDD-Parameters IPDL-TDD-Parameters OPTIONAL, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- + Information-Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + IPDLParameter-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + IPDLParameter-Information-LCR-Cell-ReconfRqstTDD ::= SEQUENCE { + iPDL-TDD-Parameters-LCR IPDL-TDD-Parameters-LCR OPTIONAL, + iPDL-Indicator IPDL-Indicator, + iE-Extensions ProtocolExtensionContainer { { IPDLParameter- + Information-LCR-Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + IPDLParameter-Information-LCR-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + SCH-768-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + SCH-Power DL-Power, + iE-Extensions ProtocolExtensionContainer { { PSCH-768-Information- + Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + PSCH-768-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PCCPCH-768-Information-Cell-ReconfRqstTDD ::= SEQUENCE { + commonPhysicalChannelID768 CommonPhysicalChannelID768, + pCCPCH-Power PCCPCH-Power, + iE-Extensions ProtocolExtensionContainer { { PCCPCH-768-Information- + Cell-ReconfRqstTDD-ExtIEs } } OPTIONAL, + ... + } + + PCCPCH-768-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + UARFCN-Adjustment ::= CHOICE { + cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD Cell-Frequency-Add-LCR-MulFreq- + Cell-ReconfRqstTDD, + cell-Frequency-ModifyList-LCR-MulFreq-Cell-ReconfRqstTDD Cell-Frequency-ModifyList-LCR- + MulFreq-Cell-ReconfRqstTDD, + cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD Cell-Frequency-Delete-LCR- + MulFreq-Cell-ReconfRqstTDD, + ... + } + +``` + +``` + +Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE { + uARFCN UARFCN, + -- This IE indicates the frequency of Secondary frequency to add + timeSlotConfigurationList-LCR-Cell-ReconfRqstTDD TimeSlotConfigurationList-LCR-Cell- +ReconfRqstTDD, + -- This IE indicates the Time Slot configuration of Secondary frequency to add + iE-Extensions ProtocolExtensionContainer { { Cell-Frequency-Add-LCR- +MulFreq-Cell-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-Frequency-ModifyList-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxFrequencyinCell- +1)) OF Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD + +Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE { + uARFCN UARFCN, + -- This IE indicates the frequency of Secondary frequency to modify + timeSlotConfigurationList-LCR-Cell-ReconfRqstTDD TimeSlotConfigurationList-LCR-Cell- +ReconfRqstTDD, + -- This IE indicates the Time Slot reconfiguration of Secondary frequency + iE-Extensions ProtocolExtensionContainer { { Cell-Frequency- +ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE { + uARFCN UARFCN, + -- This IE indicates the frequency of Secondary Frequency to delete + iE-Extensions ProtocolExtensionContainer { { Cell-Frequency-Delete- +LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- CELL RECONFIGURATION RESPONSE +-- +-- ***** + +CellReconfigurationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellReconfigurationResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellReconfigurationResponse- +Extensions}} OPTIONAL, + ... +} + +CellReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +CellReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- CELL RECONFIGURATION FAILURE +-- +-- ***** + +CellReconfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellReconfigurationFailure-IEs}}, + +``` + +``` + + protocolExtensions ProtocolExtensionContainer {{CellReconfigurationFailure-Extensions}} + OPTIONAL, + ... + } + + CellReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + CellReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- CELL DELETION REQUEST + -- + -- ***** + + CellDeletionRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellDeletionRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellDeletionRequest-Extensions}} + OPTIONAL, + ... + } + + CellDeletionRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID PRESENCE mandatory }, + ... + } + + CellDeletionRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- CELL DELETION RESPONSE + -- + -- ***** + + CellDeletionResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{CellDeletionResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{CellDeletionResponse-Extensions}} + OPTIONAL, + ... + } + + CellDeletionResponse-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + CellDeletionResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- RESOURCE STATUS INDICATION + -- + -- ***** + + ResourceStatusIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ResourceStatusIndication-IEs}}, + protocolExtensions ProtocolExtensionContainer {{ResourceStatusIndication-Extensions}} + OPTIONAL, + ... + } + + ResourceStatusIndication-IEs NBAP-PROTOCOL-IES ::= { + { ID id-IndicationType-ResourceStatusInd CRITICALITY ignore TYPE IndicationType- + ResourceStatusInd PRESENCE mandatory }| + +``` + +``` + + { ID id-Cause + PRESENCE optional }, + ... + } + +ResourceStatusIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +IndicationType-ResourceStatusInd ::= CHOICE { + no-Failure + serviceImpacting + ... +} + +No-Failure-ResourceStatusInd ::= SEQUENCE { + local-Cell-InformationList + local-Cell-Group-InformationList + OPTIONAL, + iE-Extensions + ResourceStatusInd-ExtIEs } OPTIONAL, + ... +} + +No-FailureItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Power-Local-Cell-Group-InformationList-ResourceStatusInd + CRITICALITY ignore + EXTENSION Power-Local-Cell-Group-InformationList-ResourceStatusInd + PRESENCE optional }, + ... +} + +Local-Cell-InformationList-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellInNodeB)) OF + ProtocolIE-Single-Container { { Local-Cell-InformationItemIE-ResourceStatusInd } } + +Local-Cell-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-InformationItem-ResourceStatusInd + CRITICALITY ignore + TYPE Local-Cell-InformationItem-ResourceStatusInd + PRESENCE mandatory } +} + +Local-Cell-InformationItem-ResourceStatusInd ::= SEQUENCE { + local-CellID + addorDeleteIndicator + dl-or-global-capacityCredit + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + ul-capacityCredit + OPTIONAL, + commonChannelsCapacityConsumptionLaw + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + dedicatedChannelsCapacityConsumptionLaw + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + maximumDL-PowerCapability + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + minSpreadingFactor + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + minimumDL-PowerCapability + OPTIONAL, + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" + local-Cell-Group-ID + OPTIONAL, + iE-Extensions + InformationItem-ResourceStatusInd-ExtIEs } OPTIONAL, + ... +} + +Local-Cell-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-ReferenceClockAvailability + CRITICALITY ignore + EXTENSION ReferenceClockAvailability + PRESENCE optional } | + -- This IE shall be present if AddorDeleteIndicator IE is set to "add" and the Local Cell is + related to a TDD cell + { ID id-Power-Local-Cell-Group-ID + CRITICALITY ignore + EXTENSION Local-Cell-ID + PRESENCE optional } | + { ID id-HSDPA-Capability + CRITICALITY ignore + EXTENSION HSDPA-Capability + PRESENCE optional } | +} + +``` + +``` + + { ID id-E-DCH-Capability CRITICALITY ignore EXTENSION E-DCH-Capability + PRESENCE optional }| + { ID id-E-DCH-TTI2ms-Capability CRITICALITY ignore EXTENSION E-DCH-TTI2ms- + Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-SF-Capability CRITICALITY ignore EXTENSION E-DCH-SF-Capability + PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-HARQ-Combining-Capability CRITICALITY ignore EXTENSION E-DCH-HARQ-Combining- + Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- + DCHCapacityConsumptionLaw PRESENCE optional }| + { ID id-F-DPCH-Capability CRITICALITY ignore EXTENSION F-DPCH-Capability + PRESENCE optional }| + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- + CapacityConsumptionLaw PRESENCE optional }| + { ID id-ContinuousPacketConnectivityDTX-DRX-Capability CRITICALITY ignore EXTENSION + ContinuousPacketConnectivityDTX-DRX-Capability PRESENCE optional }| + { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle + PRESENCE conditional }| + -- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present + and set to "Continuous Packet Connectivity DTX-DRX Capable". + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability CRITICALITY ignore EXTENSION + ContinuousPacketConnectivityHS-SCCH-less-Capability PRESENCE optional }| + { ID id-MIMO-Capability CRITICALITY ignore EXTENSION MIMO-Capability + PRESENCE optional }| + { ID id-SixtyfourQAM-DL-Capability CRITICALITY ignore EXTENSION SixtyfourQAM-DL- + Capability PRESENCE optional }| + { ID id-MBMS-Capability CRITICALITY ignore EXTENSION MBMS-Capability + PRESENCE optional }| + { ID id-Enhanced-FACH-Capability CRITICALITY ignore EXTENSION Enhanced-FACH- + Capability PRESENCE optional }| + { ID id-Enhanced-PCH-Capability CRITICALITY ignore EXTENSION Enhanced-PCH- + Capability PRESENCE conditional }| + -- The IE shall be present if Enhanced FACH Capability IE is set to "Enhanced FACH Capable". + { ID id-SixteenQAM-UL-Capability CRITICALITY ignore EXTENSION SixteenQAM-UL- + Capability PRESENCE optional }| + { ID id-HSDSCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION HSDSCH-MACdPDU- + SizeCapability PRESENCE optional }| + { ID id-MBSFN-Only-Mode-Capability CRITICALITY ignore EXTENSION MBSFN-Only-Mode- + Capability PRESENCE optional }| + { ID id-F-DPCH-SlotFormatCapability CRITICALITY ignore EXTENSION F-DPCH- + SlotFormatCapability PRESENCE optional }| + { ID id-E-DCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION E-DCH-MACdPDU- + SizeCapability PRESENCE optional }| + { ID id-Common-EDCH-Capability CRITICALITY ignore EXTENSION Common-EDCH-Capability + PRESENCE optional }| + { ID id-E-AI-Capability CRITICALITY ignore EXTENSION E-AI-Capability + PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH + Capable". + { ID id-Enhanced-UE-DRX-Capability CRITICALITY ignore EXTENSION Enhanced-UE-DRX- + Capability PRESENCE optional }| + { ID id-Enhanced-UE-DRX-CapabilityLCR CRITICALITY ignore EXTENSION Enhanced-UE-DRX- + Capability PRESENCE optional }| + { ID id-E-DPCCH-Power-Boosting-Capability CRITICALITY ignore EXTENSION E-DPCCH-Power- + Boosting-Capability PRESENCE optional }| + { ID id-SixtyfourQAM-DL-MIMO-Combined-Capability CRITICALITY ignore EXTENSION SixtyfourQAM- + DL-MIMO-Combined-Capability PRESENCE optional }| + { ID id-Multi-Cell-Capability-Info CRITICALITY ignore EXTENSION Multi-Cell-Capability- + Info PRESENCE optional }| + { ID id-Semi-PersistentScheduling-CapabilityLCR CRITICALITY ignore EXTENSION Semi- + PersistentScheduling-CapabilityLCR PRESENCE optional }| + { ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR CRITICALITY ignore EXTENSION + ContinuousPacketConnectivity-DRX-CapabilityLCR PRESENCE optional }| + { ID id-Common-E-DCH-HSDPCCCH-Capability CRITICALITY ignore EXTENSION Common-E-DCH-HSDPCCCH- + Capability PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH + Capable". + { ID id-MIMO-Power-Offset-For-S-CPICH-Capability CRITICALITY ignore EXTENSION MIMO- + PowerOffsetForS-CPICHCapability PRESENCE optional }| + { ID id-TxDiversityOnDLControlChannelsByMIMOUECapability CRITICALITY ignore EXTENSION + TxDiversityOnDLControlChannelsByMIMOUECapability PRESENCE optional }| + { ID id-Single-Stream-MIMO-Capability CRITICALITY ignore EXTENSION Single-Stream-MIMO- + Capability PRESENCE optional }| + { ID id-Dual-Band-Capability-Info CRITICALITY ignore EXTENSION Dual-Band-Capability- + Info PRESENCE optional }| + +``` + +``` + + { ID id-CellPortion-CapabilityLCR CRITICALITY ignore EXTENSION CellPortion- + CapabilityLCR PRESENCE optional }| + { ID id-Cell-Capability-Container CRITICALITY ignore EXTENSION Cell-Capability- + Container PRESENCE optional }| + { ID id-TS0-CapabilityLCR CRITICALITY ignore EXTENSION TS0-CapabilityLCR + PRESENCE optional }| + { ID id-PrecodingWeightSetRestriction CRITICALITY ignore EXTENSION + PrecodingWeightSetRestriction PRESENCE optional }| + { ID id-Cell-Capability-Container-TDD-LCR CRITICALITY ignore EXTENSION Cell-Capability- + Container-TDD-LCR PRESENCE optional }| + { ID id-MU-MIMO-Capability-ContainerLCR CRITICALITY ignore EXTENSION MU-MIMO-Capability- + ContainerLCR PRESENCE optional }| + { ID id-Adaptive-Special-Burst-Power-CapabilityLCR CRITICALITY ignore EXTENSION Adaptive- + Special-Burst-Power-CapabilityLCR PRESENCE optional }, + ... +} + +Local-Cell-Group-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF +ProtocolIE-Single-Container { { Local-Cell-Group-InformationItemIE-ResourceStatusInd } } + +Local-Cell-Group-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-Group-InformationItem-ResourceStatusInd CRITICALITY ignore TYPE Local-Cell- + Group-InformationItem-ResourceStatusInd PRESENCE mandatory } +} + +Local-Cell-Group-InformationItem-ResourceStatusInd ::= SEQUENCE { + local-Cell-Group-ID Local-Cell-ID, + dl-or-global-capacityCredit DL-or-Global-CapacityCredit, + ul-capacityCredit UL-CapacityCredit OPTIONAL, + commonChannelsCapacityConsumptionLaw CommonChannelsCapacityConsumptionLaw, + dedicatedChannelsCapacityConsumptionLaw DedicatedChannelsCapacityConsumptionLaw, + iE-Extensions ProtocolExtensionContainer { { Local-Cell-Group- + InformationItem-ResourceStatusInd-ExtIEs } } OPTIONAL, + ... +} + +Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- + DCHCapacityConsumptionLaw PRESENCE optional }| + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- + CapacityConsumptionLaw PRESENCE optional }, + ... +} + +Power-Local-Cell-Group-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) +OF ProtocolIE-Single-Container { { Power-Local-Cell-Group-InformationItemIE-ResourceStatusInd } } + +Power-Local-Cell-Group-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-InformationItem-ResourceStatusInd CRITICALITY ignore TYPE + Power-Local-Cell-Group-InformationItem-ResourceStatusInd PRESENCE mandatory } +} + +Power-Local-Cell-Group-InformationItem-ResourceStatusInd ::= SEQUENCE { + power-Local-Cell-Group-ID Local-Cell-ID, + maximumDL-PowerCapability MaximumDL-PowerCapability, + iE-Extensions ProtocolExtensionContainer { { Power-Local-Cell- + Group-InformationItem-ResourceStatusInd-ExtIEs } } OPTIONAL, + ... +} + +Power-Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +ServiceImpacting-ResourceStatusInd ::= SEQUENCE { + local-Cell-InformationList Local-Cell-InformationList2-ResourceStatusInd + OPTIONAL, + local-Cell-Group-InformationList Local-Cell-Group-InformationList2-ResourceStatusInd + OPTIONAL, + CCP-InformationList CCP-InformationList-ResourceStatusInd + OPTIONAL, + cell-InformationList Cell-InformationList-ResourceStatusInd + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ServiceImpactingItem- + ResourceStatusInd-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +ServiceImpactingItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Power-Local-Cell-Group-InformationList2-ResourceStatusInd CRITICALITY ignore + EXTENSION Power-Local-Cell-Group-InformationList2-ResourceStatusInd PRESENCE optional }, + ... +} + +Local-Cell-InformationList2-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF + ProtocolIE-Single-Container { { Local-Cell-InformationItem2-ResourceStatusInd } } + +Local-Cell-InformationItem2-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-InformationItem2-ResourceStatusInd CRITICALITY ignore TYPE Local-Cell- + InformationItem2-ResourceStatusInd PRESENCE mandatory } +} + +Local-Cell-InformationItem2-ResourceStatusInd ::= SEQUENCE { + local-Cell-ID Local-Cell-ID, + dl-or-global-capacityCredit DL-or-Global-CapacityCredit OPTIONAL, + ul-capacityCredit UL-CapacityCredit OPTIONAL, + commonChannelsCapacityConsumptionLaw CommonChannelsCapacityConsumptionLaw OPTIONAL, + dedicatedChannelsCapacityConsumptionLaw DedicatedChannelsCapacityConsumptionLaw OPTIONAL, + maximum-DL-PowerCapability MaximumDL-PowerCapability OPTIONAL, + minSpreadingFactor MinSpreadingFactor OPTIONAL, + minimumDL-PowerCapability MinimumDL-PowerCapability OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Local-Cell- + InformationItem2-ResourceStatusInd-ExtIEs } } OPTIONAL, + ... +} + +Local-Cell-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-ReferenceClockAvailability CRITICALITY ignore EXTENSION + ReferenceClockAvailability PRESENCE optional }| + { ID id-HSDPA-Capability CRITICALITY ignore EXTENSION HSDPA-Capability + PRESENCE optional }| + { ID id-E-DCH-Capability CRITICALITY ignore EXTENSION E-DCH-Capability + PRESENCE optional }| + { ID id-E-DCH-TTI2ms-Capability CRITICALITY ignore EXTENSION E-DCH-TTI2ms- + Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-SF-Capability CRITICALITY ignore EXTENSION E-DCH-SF-Capability + PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-HARQ-Combining-Capability CRITICALITY ignore EXTENSION E-DCH-HARQ-Combining- + Capability PRESENCE conditional }| + -- The IE shall be present if E-DCH Capability IE is set to "E-DCH Capable". + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- + DCHCapacityConsumptionLaw PRESENCE optional }| + { ID id-F-DPCH-Capability CRITICALITY ignore EXTENSION F-DPCH-Capability + PRESENCE optional }| + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- + CapacityConsumptionLaw PRESENCE optional }| + { ID id-ContinuousPacketConnectivityDTX-DRX-Capability CRITICALITY ignore EXTENSION + ContinuousPacketConnectivityDTX-DRX-Capability PRESENCE optional }| + { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle + PRESENCE conditional }| + -- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present + and set to "Continuous Packet Connectivity DTX-DRX Capable". + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability CRITICALITY ignore EXTENSION + ContinuousPacketConnectivityHS-SCCH-less-Capability PRESENCE optional }| + { ID id-MIMO-Capability CRITICALITY ignore EXTENSION MIMO-Capability + PRESENCE optional }| + { ID id-SixtyfourQAM-DL-Capability CRITICALITY ignore EXTENSION SixtyfourQAM-DL- + Capability PRESENCE optional }| + { ID id-MBMS-Capability CRITICALITY ignore EXTENSION MBMS-Capability + PRESENCE optional }| + { ID id-Enhanced-FACH-Capability CRITICALITY ignore EXTENSION Enhanced-FACH- + Capability PRESENCE optional }| + { ID id-Enhanced-PCH-Capability CRITICALITY ignore EXTENSION Enhanced-PCH- + Capability PRESENCE conditional }| + -- The IE shall be present if Enhanced FACH Capability IE is set to "Enhanced FACH Capable". + { ID id-SixteenQAM-UL-Capability CRITICALITY ignore EXTENSION SixteenQAM-UL- + Capability PRESENCE optional }| + { ID id-HSDSCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION HSDSCH-MACdPDU- + SizeCapability PRESENCE optional }| + { ID id-MBSFN-Only-Mode-Capability CRITICALITY ignore EXTENSION MBSFN-Only-Mode- + Capability PRESENCE optional }| + { ID id-F-DPCH-SlotFormatCapability CRITICALITY ignore EXTENSION F-DPCH- + SlotFormatCapability PRESENCE optional }| +} + +``` + +``` + + { ID id-E-DCH-MACdPDU-SizeCapability CRITICALITY ignore EXTENSION E-DCH-MACdPDU- +SizeCapability PRESENCE optional }| + { ID id-Common-EDCH-Capability CRITICALITY ignore EXTENSION Common-EDCH-Capability + PRESENCE optional }| + { ID id-E-AI-Capability CRITICALITY ignore EXTENSION E-AI-Capability + PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH +Capable". + { ID id-Enhanced-UE-DRX-Capability CRITICALITY ignore EXTENSION Enhanced-UE-DRX- +Capability PRESENCE optional }| + { ID id-Enhanced-UE-DRX-CapabilityLCR CRITICALITY ignore EXTENSION Enhanced-UE-DRX- +Capability PRESENCE optional }| + { ID id-E-DPCCH-Power-Boosting-Capability CRITICALITY ignore EXTENSION E-DPCCH-Power- +Boosting-Capability PRESENCE optional }| + { ID id-SixtyfourQAM-DL-MIMO-Combined-Capability CRITICALITY ignore EXTENSION SixtyfourQAM- +DL-MIMO-Combined-Capability PRESENCE optional }| + { ID id-Multi-Cell-Capability-Info CRITICALITY ignore EXTENSION Multi-Cell-Capability- +Info PRESENCE optional }| + { ID id-Semi-PersistentScheduling-CapabilityLCR CRITICALITY ignore EXTENSION Semi- +PersistentScheduling-CapabilityLCR PRESENCE optional }| + { ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR CRITICALITY ignore EXTENSION +ContinuousPacketConnectivity-DRX-CapabilityLCR PRESENCE optional }| + { ID id-Common-E-DCH-HSDPCCH-Capability CRITICALITY ignore EXTENSION Common-E-DCH-HSDPCCH- +Capability PRESENCE optional }| + -- The IE shall be present if Common E-DCH Capability IE is present and set to "Common E-DCH +Capable". + { ID id-MIMO-Power-Offset-For-S-CPICH-Capability CRITICALITY ignore EXTENSION MIMO- +PowerOffsetForS-CPICHCapability PRESENCE optional }| + { ID id-TxDiversityOnDLControlChannelsByMIMOUECapability CRITICALITY ignore EXTENSION +TxDiversityOnDLControlChannelsByMIMOUECapability PRESENCE optional }| + { ID id-Single-Stream-MIMO-Capability CRITICALITY ignore EXTENSION Single-Stream-MIMO- +Capability PRESENCE optional }| + { ID id-Dual-Band-Capability-Info CRITICALITY ignore EXTENSION Dual-Band-Capability- +Info PRESENCE optional }| + { ID id-CellPortion-CapabilityLCR CRITICALITY ignore EXTENSION CellPortion- +CapabilityLCR PRESENCE optional }| + { ID id-Cell-Capability-Container CRITICALITY ignore EXTENSION Cell-Capability- +Container PRESENCE optional }| + { ID id-TS0-CapabilityLCR CRITICALITY ignore EXTENSION TS0-CapabilityLCR + PRESENCE optional }| + { ID id-PrecodingWeightSetRestriction CRITICALITY ignore EXTENSION +PrecodingWeightSetRestriction PRESENCE optional }| + { ID id-Cell-Capability-Container-TDD-LCR CRITICALITY ignore EXTENSION Cell-Capability- +Container-TDD-LCR PRESENCE optional }| + { ID id-MU-MIMO-Capability-ContainerLCR CRITICALITY ignore EXTENSION MU-MIMO-Capability- +ContainerLCR PRESENCE optional }| + { ID id-Adaptive-Special-Burst-Power-CapabilityLCR CRITICALITY ignore EXTENSION Adaptive- +Special-Burst-Power-CapabilityLCR PRESENCE optional }, + ... + } + + Local-Cell-Group-InformationList2-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxLocalCellInNodeB)) OF + ProtocolIE-Single-Container { Local-Cell-Group-InformationItemIE2-ResourceStatusInd } + + Local-Cell-Group-InformationItemIE2-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Local-Cell-Group-InformationItem2-ResourceStatusInd CRITICALITY ignore TYPE Local- +Cell-Group-InformationItem2-ResourceStatusInd PRESENCE mandatory } + } + + Local-Cell-Group-InformationItem2-ResourceStatusInd ::= SEQUENCE { + local-Cell-Group-ID Local-Cell-ID, + dl-or-global-capacityCredit DL-or-Global-CapacityCredit + OPTIONAL, + ul-capacityCredit UL-CapacityCredit + OPTIONAL, + commonChannelsCapacityConsumptionLaw CommonChannelsCapacityConsumptionLaw + OPTIONAL, + dedicatedChannelsCapacityConsumptionLaw DedicatedChannelsCapacityConsumptionLaw + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { Local-Cell-Group- +InformationItem2-ResourceStatusInd-ExtIEs } OPTIONAL, + ... + } + + Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E- +DCHCapacityConsumptionLaw PRESENCE optional }| + } + +``` + +``` + + { ID id-E-DCH-TDD-CapacityConsumptionLaw CRITICALITY ignore EXTENSION E-DCH-TDD- +CapacityConsumptionLaw PRESENCE optional }, + ... +} + +CCP-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxCCPinNodeB)) OF ProtocolIE-Single- +Container {{ CCP-InformationItemIE-ResourceStatusInd }} + +CCP-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-CCP-InformationItem-ResourceStatusInd CRITICALITY ignore TYPE CCP-InformationItem- +ResourceStatusInd PRESENCE mandatory } +} + +CCP-InformationItem-ResourceStatusInd ::= SEQUENCE { + communicationControlPortID CommunicationControlPortID, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer { { CCP-InformationItem- +ResourceStatusInd-ExtIEs} } OPTIONAL, + ... +} + +CCP-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cell-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxCellInNodeB)) OF ProtocolIE-Single- +Container {{ Cell-InformationItemIE-ResourceStatusInd }} + +Cell-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Cell-InformationItem-ResourceStatusInd CRITICALITY ignore TYPE Cell-InformationItem- +ResourceStatusInd PRESENCE mandatory } +} + +Cell-InformationItem-ResourceStatusInd ::= SEQUENCE { + c-ID C-ID, + resourceOperationalState ResourceOperationalState + OPTIONAL, + availabilityStatus AvailabilityStatus + OPTIONAL, + primary-SCH-Information P-SCH-Information-ResourceStatusInd + OPTIONAL, -- FDD only + secondary-SCH-Information S-SCH-Information-ResourceStatusInd + OPTIONAL, -- FDD only + primary-CPICH-Information P-CPICH-Information-ResourceStatusInd + OPTIONAL, -- FDD only + secondary-CPICH-Information S-CPICH-InformationList-ResourceStatusInd + OPTIONAL, -- FDD only + primary-CCPCH-Information P-CCPCH-Information-ResourceStatusInd + OPTIONAL, + bCH-Information BCH-Information-ResourceStatusInd + OPTIONAL, + secondary-CCPCH-InformationList S-CCPCH-InformationList-ResourceStatusInd + OPTIONAL, + pCH-Information PCH-Information-ResourceStatusInd + OPTIONAL, + pICH-Information PICH-Information-ResourceStatusInd + OPTIONAL, + fACH-InformationList FACH-InformationList-ResourceStatusInd + OPTIONAL, + pRACH-InformationList PRACH-InformationList-ResourceStatusInd + OPTIONAL, + rACH-InformationList RACH-InformationList-ResourceStatusInd + OPTIONAL, + aICH-InformationList AICH-InformationList-ResourceStatusInd + OPTIONAL, -- FDD only + notUsed-1-pCPCH-InformationList NULL + OPTIONAL, + notUsed-2-cPCH-InformationList NULL + OPTIONAL, + notUsed-3-aP-AICH-InformationList NULL + OPTIONAL, + notUsed-4-cDCA-ICH-InformationList NULL + OPTIONAL, + SCH-Information SCH-Information-ResourceStatusInd + OPTIONAL, -- Applicable to 3.84Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { Cell-InformationItem- +ResourceStatusInd-ExtIEs} } OPTIONAL, +} + +``` + +``` + + ... + } + + Cell-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-FPACH-LCR-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION FPACH- + LCR-InformationList-ResourceStatusInd PRESENCE optional }| -- Applicable to 1.28Mcps + TDD only + { ID id-DwPCH-LCR-Information-ResourceStatusInd CRITICALITY ignore EXTENSION DwPCH- + LCR-Information-ResourceStatusInd PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only + { ID id-HSDSCH-Resources-Information-ResourceStatusInd CRITICALITY ignore EXTENSION HS- + DSCH-Resources-Information-ResourceStatusInd PRESENCE optional }| -- For 1.28Mcps TDD, + this HS-DSCH Resource Information is for the first Frequency repetition, HS-DSCH Resource + Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HS-DSCH-Resources- + InformationList-ResourceStatusInd. + { ID id-MICH-Information-ResourceStatusInd CRITICALITY ignore EXTENSION + Common-PhysicalChannel-Status-Information PRESENCE optional }| + { ID id-S-CCPCH-InformationListExt-ResourceStatusInd CRITICALITY ignore EXTENSION S- + CCPCH-InformationListExt-ResourceStatusInd PRESENCE optional }| + -- Applicable to 3.84Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the + message. + { ID id-S-CCPCH-LCR-InformationListExt-ResourceStatusInd CRITICALITY ignore EXTENSION S- + CCPCH-LCR-InformationListExt-ResourceStatusInd PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the + message. + { ID id-E-DCH-Resources-Information-ResourceStatusInd CRITICALITY ignore EXTENSION E-DCH- + Resources-Information-ResourceStatusInd PRESENCE optional }| + -- For 1.28Mcps TDD, this E-DCH Resource Information is for the first Frequency repetition, E- + DCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-E- + DCH-Resources-InformationList-ResourceStatusInd. + { ID id-PLCCH-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION PLCCH- + InformationList-ResourceStatusInd + PRESENCE optional }| + { ID id-P-CCPCH-768-Information-ResourceStatusInd CRITICALITY ignore EXTENSION + Common-PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-S-CCPCH-768-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION S- + CCPCH-768-InformationList-ResourceStatusInd PRESENCE optional }| + { ID id-PICH-768-Information-ResourceStatusInd CRITICALITY ignore EXTENSION + Common-PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-PRACH-768-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION PRACH- + 768-InformationList-ResourceStatusInd PRESENCE optional }| + { ID id-SCH-768-Information-ResourceStatusInd CRITICALITY ignore EXTENSION + Common-PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-MICH-768-Information-ResourceStatusInd CRITICALITY ignore EXTENSION + Common-PhysicalChannel-Status-Information768 PRESENCE optional }| + { ID id-E-RUCCH-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION E- + RUCCH-InformationList-ResourceStatusInd PRESENCE optional }| + { ID id-E-RUCCH-768-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION E- + RUCCH-768-InformationList-ResourceStatusInd PRESENCE optional }| + { ID id-Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd CRITICALITY ignore + EXTENSION Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd PRESENCE + optional }| -- Applicable to 1.28Mcps TDD when using multiple frequencies + { ID id-UPPCH-LCR-InformationList-ResourceStatusInd CRITICALITY ignore EXTENSION UPPCH- + LCR-InformationList-ResourceStatusInd PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only + { ID id-multipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd CRITICALITY ignore + EXTENSION MultipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd PRESENCE optional }| + -- Applicable to 1.28Mcps TDD when using multiple frequencies, This HS-DSCH Resource Information + is for the 2nd and beyond frequencies. + { ID id-MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd CRITICALITY ignore + EXTENSION MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd PRESENCE optional }|, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. This E-DCH Resource Information + is for the 2nd and beyond frequencies. + ... + } + + P-SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-SCH-InformationIE- + ResourceStatusInd }} + + P-SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-P-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } + } + + S-SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ S-SCH-InformationIE- + ResourceStatusInd }} + + S-SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + +``` + +``` +{ ID id-S-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +P-CPICH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-CPICH-InformationIE- +ResourceStatusInd }} + +P-CPICH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-P-CPICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +S-CPICH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE- +Single-Container {{ S-CPICH-InformationItemIE-ResourceStatusInd }} + +S-CPICH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-S-CPICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +P-CCPCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-CCPCH-InformationIE- +ResourceStatusInd }} + +P-CCPCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-P-CCPCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +BCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ BCH-InformationIE- +ResourceStatusInd }} + +BCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-BCH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +S-CCPCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCell)) OF ProtocolIE- +Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }} + +S-CCPCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-S-CCPCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +PCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ PCH-InformationIE- +ResourceStatusInd }} + +PCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-PCH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +PICH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ PICH-InformationIE- +ResourceStatusInd }} + +PICH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-PICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +FACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFACHCell)) OF ProtocolIE-Single- +Container {{ FACH-InformationItemIE-ResourceStatusInd }} + +FACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-FACH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +PRACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single- +Container {{ PRACH-InformationItemIE-ResourceStatusInd }} + +PRACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +RACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single- +Container {{ RACH-InformationItemIE-ResourceStatusInd }} +``` + +``` + +RACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-RACH-Information CRITICALITY ignore TYPE Common-TransportChannel-Status-Information + PRESENCE mandatory } +} + +AICH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single- +Container {{ AICH-InformationItemIE-ResourceStatusInd }} + +AICH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-AICH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ SCH-InformationIE- +ResourceStatusInd }} + +SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-SCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status-Information + PRESENCE mandatory } +} + +FPACH-LCR-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFPACHCell)) OF ProtocolIE- +Single-Container {{ FPACH-LCR-InformationItemIE-ResourceStatusInd }} + +FPACH-LCR-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-FPACH-LCR-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +DwPCH-LCR-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ DwPCH-LCR-InformationIE- +ResourceStatusInd }} + +DwPCH-LCR-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-DwPCH-LCR-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- + Information PRESENCE mandatory } +} + +HS-DSCH-Resources-Information-ResourceStatusInd ::= SEQUENCE { + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ HS-DSCH-Resources- + Information-ResourceStatusInd-ExtIEs }} OPTIONAL, + ... +} + +HS-DSCH-Resources-Information-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN PRESENCE optional}, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. + ... +} + +S-CCPCH-InformationListExt-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExt)) OF +ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }} + +S-CCPCH-LCR-InformationListExt-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExtLCR)) OF +ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }} + +E-DCH-Resources-Information-ResourceStatusInd ::= SEQUENCE { + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ E-DCH-Resources-Information- + ResourceStatusInd-ExtIEs }} OPTIONAL, + ... +} + +E-DCH-Resources-Information-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN PRESENCE optional}, + -- Applicable to 1.28Mcps TDD when using multiple frequencies. + ... +} + +PLCCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPLCCHCell)) OF ProtocolIE-Single- +Container {{ PLCCH-InformationItemIE-ResourceStatusInd }} + +PLCCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-PLCCH-Information-ResourceStatusInd CRITICALITY ignore TYPE Common-PhysicalChannel- + Status-Information PRESENCE mandatory } +} + +``` + +``` + +} + +S-CCPCH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCell768)) OF +ProtocolIE-Single-Container {{ S-CCPCH-768-InformationItemIE-ResourceStatusInd }} + +S-CCPCH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-S-CCPCH-768-Information-ResourceStatusInd CRITICALITY ignore TYPE Common- +PhysicalChannel-Status-Information768 PRESENCE mandatory } +} + +PRACH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE- +Single-Container {{ PRACH-768-InformationItemIE-ResourceStatusInd }} + +PRACH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-PRACH-768-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information768 PRESENCE mandatory } +} + +E-RUCCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE- +Single-Container {{ E-RUCCH-InformationItemIE-ResourceStatusInd }} + +E-RUCCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-E-RUCCH-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information PRESENCE mandatory } +} + +E-RUCCH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE- +Single-Container {{ E-RUCCH-768-InformationItemIE-ResourceStatusInd }} + +E-RUCCH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-E-RUCCH-768-Information CRITICALITY ignore TYPE Common-PhysicalChannel-Status- +Information768 PRESENCE mandatory } +} + +Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd ::= SEQUENCE (SIZE +(1..maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ Cell-Frequency-List-InformationIE-LCR- +MulFreq-ResourceStatusInd }} + +Cell-Frequency-List-InformationIE-LCR-MulFreq-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd CRITICALITY ignore +TYPE Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd PRESENCE mandatory } +} + +Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd ::= SEQUENCE { + uARFCN UARFCN, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ Cell-Frequency-List- +InformationItem-LCR-MulFreq-ResourceStatusInd-ExtIEs }} OPTIONAL, + ... +} + +Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UPPCH-LCR-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF +ProtocolIE-Single-Container {{ UPPCH-LCR-InformationIE-ResourceStatusInd }} + +UPPCH-LCR-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-UPPCH-LCR-InformationItem-ResourceStatusInd CRITICALITY ignore TYPE UPPCH-LCR- +InformationItem-ResourceStatusInd PRESENCE mandatory } +} + +UPPCH-LCR-InformationItem-ResourceStatusInd ::= SEQUENCE { + uARFCN UARFCN OPTIONAL, + uPPCHPositionLCR UPPCHPositionLCR, + resourceOperationalState ResourceOperationalState, + availabilityStatus AvailabilityStatus, + iE-Extensions ProtocolExtensionContainer {{ UPPCH-LCR-InformationItem- +ResourceStatusInd-ExtIEs }} OPTIONAL, + ... +} + +UPPCH-LCR-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +} + +MultipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE +(1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ MultipleFreq-HS-DSCH-Resources- +InformationItem-ResourceStatusInd }} +--Includes the 2nd through the max number of frequencies information repetitions. + +MultipleFreq-HS-DSCH-Resources-InformationItem-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-HSDSCH-Resources-Information-ResourceStatusInd CRITICALITY ignore TYPE HS-DSCH- +Resources-Information-ResourceStatusInd PRESENCE mandatory } +} + +Power-Local-Cell-Group-InformationList2-ResourceStatusInd ::= SEQUENCE (SIZE +(1..maxLocalCellInNodeB)) OF ProtocolIE-Single-Container {{ Power-Local-Cell-Group- +InformationItemE2-ResourceStatusInd }} + +Power-Local-Cell-Group-InformationItemE2-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-Power-Local-Cell-Group-InformationItem2-ResourceStatusInd CRITICALITY ignore TYPE +Power-Local-Cell-Group-InformationItem2-ResourceStatusInd PRESENCE mandatory } +} + +Power-Local-Cell-Group-InformationItem2-ResourceStatusInd ::= SEQUENCE { + power-Local-Cell-Group-ID Local-Cell-ID, + maximumDL-PowerCapability MaximumDL-PowerCapability, + iE-Extensions ProtocolExtensionContainer { { Power-Local-Cell-Group- +InformationItem2-ResourceStatusInd-ExtIEs} } OPTIONAL, + ... +} + +Power-Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE +(1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ MultipleFreq-E-DCH-Resources- +InformationItem-ResourceStatusInd }} +--Includes the 2nd through the max number of frequencies information repetitions. + +MultipleFreq-E-DCH-Resources-InformationItem-ResourceStatusInd NBAP-PROTOCOL-IES ::= { + { ID id-E-DCH-Resources-Information-ResourceStatusInd CRITICALITY ignore TYPE E-DCH- +Resources-Information-ResourceStatusInd PRESENCE mandatory } +} + +-- **************************************************************************** +-- +-- SYSTEM INFORMATION UPDATE REQUEST +-- +-- **************************************************************************** + +SystemInformationUpdateRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{SystemInformationUpdateRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{SystemInformationUpdateRequest- +Extensions}} OPTIONAL, + ... +} + +SystemInformationUpdateRequest-IEs NBAP-PROTOCOL-IES ::= { + { ID id-C-ID CRITICALITY reject TYPE C-ID + PRESENCE mandatory }| + { ID id-BCCH-ModificationTime CRITICALITY reject TYPE BCCH- +ModificationTime PRESENCE optional }| + { ID id-MIB-SB-SIB-InformationList-SystemInfoUpdateRqst CRITICALITY reject TYPE MIB-SB-SIB- +InformationList-SystemInfoUpdateRqst PRESENCE mandatory }, + ... +} + +SystemInformationUpdateRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-BCH-mappedOnSCCPCH-Indication CRITICALITY reject EXTENSION BCH-mappedOnSCCPCH- +Indication PRESENCE optional}, + ... +} + +MIB-SB-SIB-InformationList-SystemInfoUpdateRqst ::= SEQUENCE (SIZE (1..maxIB)) OF MIB-SB-SIB- +InformationItem-SystemInfoUpdateRqst + +MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst ::= SEQUENCE { + iB-Type IB-Type, + iB-OC-ID IB-OC-ID, + +``` + +``` + + deletionIndicator DeletionIndicator-SystemInfoUpdate, + iE-Extensions ProtocolExtensionContainer { { MIB-SB-SIB-InformationItem- +SystemInfoUpdateRqst-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +BCH-mappedOnSCCPCH-Indication ::= ENUMERATED { + inUse, + ... +} + +``` + +``` + +DeletionIndicator-SystemInfoUpdate ::= CHOICE { + no-Deletion No-Deletion-SystemInfoUpdate, + yes-Deletion NULL +} + +``` + +``` + +No-Deletion-SystemInfoUpdate ::= SEQUENCE { + sIB-Originator SIB-Originator OPTIONAL, + -- This IE shall be present if the IB-Type IE is set to "SIB" + iB-SG-REP iB-SG-REP OPTIONAL, + segmentInformationList SegmentInformationList-SystemInfoUpdate, + iE-Extensions ProtocolExtensionContainer { { No-DeletionItem- +SystemInfoUpdate-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +No-DeletionItem-SystemInfoUpdate-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +SegmentInformationList-SystemInfoUpdate ::= ProtocolIE-Single-Container {{ +SegmentInformationListIEs-SystemInfoUpdate }} + +``` + +``` + +SegmentInformationListIEs-SystemInfoUpdate NBAP-PROTOCOL-IES ::= { + { ID id-SegmentInformationListIE-SystemInfoUpdate CRITICALITY reject TYPE +SegmentInformationListIE-SystemInfoUpdate PRESENCE mandatory } +} + +``` + +``` + +SegmentInformationListIE-SystemInfoUpdate ::= SEQUENCE (SIZE (1..maxIBSEG)) OF +SegmentInformationItem-SystemInfoUpdate + +``` + +``` + +SegmentInformationItem-SystemInfoUpdate ::= SEQUENCE { + iB-SG-POS iB-SG-POS OPTIONAL, + segment-Type Segment-Type OPTIONAL, + -- This IE shall be present if the SIB Originator IE is set to "CRNC" or the IB-Type IE is set +to "MIB", "SB1" or "SB2" + iB-SG-DATA iB-SG-DATA OPTIONAL, + -- This IE shall be present if the SIB Originator IE is set to "CRNC" or the IB-Type IE is set +to "MIB", "SB1" or "SB2" + iE-Extensions ProtocolExtensionContainer { { SegmentInformationItem- +SystemInfoUpdate-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +SegmentInformationItem-SystemInfoUpdate-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- SYSTEM INFORMATION UPDATE RESPONSE +-- +-- ***** + +``` + +``` + +SystemInformationUpdateResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{SystemInformationUpdateResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{SystemInformationUpdateResponse- +Extensions}} OPTIONAL, + ... +} + +``` + +``` + +SystemInformationUpdateResponse-IEs NBAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +SystemInformationUpdateResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- SYSTEM INFORMATION UPDATE FAILURE +-- +-- ***** + +SystemInformationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{SystemInformationUpdateFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{SystemInformationUpdateFailure- + Extensions}} OPTIONAL, + ... +} + +SystemInformationUpdateFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +SystemInformationUpdateFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- RADIO LINK SETUP REQUEST FDD +-- +-- ***** + +RadioLinkSetupRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkSetupRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupRequestFDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY reject TYPE CRNC- + CommunicationContextID PRESENCE mandatory }| + { ID id-UL-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject TYPE UL-DPCH- + Information-RL-SetupRqstFDD PRESENCE mandatory }| + { ID id-DL-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject TYPE DL-DPCH- + Information-RL-SetupRqstFDD PRESENCE optional }| + { ID id-DCH-FDD-Information CRITICALITY reject TYPE DCH-FDD- + Information PRESENCE mandatory }| + { ID id-RL-InformationList-RL-SetupRqstFDD CRITICALITY notify TYPE RL- + InformationList-RL-SetupRqstFDD PRESENCE mandatory }| + { ID id-Transmission-Gap-Pattern-Sequence-Information CRITICALITY reject TYPE Transmission- + Gap-Pattern-Sequence-Information PRESENCE optional }| + { ID id-Active-Pattern-Sequence-Information CRITICALITY reject TYPE Active-Pattern- + Sequence-Information PRESENCE optional }, + ... +} + +RadioLinkSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-Information CRITICALITY ignore EXTENSION DL- + PowerBalancing-Information PRESENCE optional }| + { ID id-HSDSCH-FDD-Information CRITICALITY reject EXTENSION HSDSCH-FDD- + Information PRESENCE optional }| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional }| + -- The IE shall be present if HS-DSCH Information IE is present + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE conditional }| + -- The IE shall be present if HS-DSCH Information IE is present + { ID id-E-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject EXTENSION E-DPCH- + Information-RL-SetupRqstFDD PRESENCE optional }| +} + +``` + +``` + + { ID id-E-DCH-FDD-Information CRITICALITY reject EXTENSION E-DCH-FDD- +Information PRESENCE conditional}| + -- The IE shall be present if E-DPCH Information IE is present + { ID id-Serving-E-DCH-RL-ID CRITICALITY reject EXTENSION Serving-E-DCH- +RL-ID PRESENCE optional}| + { ID id-F-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject EXTENSION F-DPCH- +Information-RL-SetupRqstFDD PRESENCE optional}| + { ID id-Initial-DL-DPCH-TimingAdjustment-Allowed CRITICALITY ignore EXTENSION Initial-DL- +DPCH-TimingAdjustment-Allowed PRESENCE optional}| + { ID id-DCH-Indicator-For-E-DCH-HSDPA-Operation CRITICALITY reject EXTENSION DCH-Indicator- +For-E-DCH-HSDPA-Operation PRESENCE optional}| + { ID id-Serving-Cell-Change-CFN CRITICALITY reject EXTENSION CFN + PRESENCE optional}| + { ID id-ContinuousPacketConnectivityDTX-DRX-Information CRITICALITY reject EXTENSION +ContinuousPacketConnectivityDTX-DRX-Information PRESENCE optional}| + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Information CRITICALITY reject EXTENSION +ContinuousPacketConnectivityHS-SCCH-less-Information PRESENCE optional}| + { ID id-Additional-HS-Cell-Information-RL-Setup CRITICALITY reject EXTENSION Additional-HS- +Cell-Information-RL-Setup-List PRESENCE optional}| + { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE- +AggregateMaximumBitRate PRESENCE optional}| + { ID id-Additional-EDCH-Cell-Information-RL-Setup-Req CRITICALITY reject EXTENSION +Additional-EDCH-Setup-Info PRESENCE optional}| + { ID id-Usefulness-Of-Battery-Optimization CRITICALITY ignore EXTENSION Usefulness-Of- +Battery-Optimization PRESENCE optional}| + { ID id-UL-CLTD-Information CRITICALITY reject EXTENSION UL-CLTD- +Information PRESENCE optional}| + { ID id-E-DCH-Decoupling-Indication CRITICALITY reject EXTENSION E-DCH- +Decoupling-Indication PRESENCE optional}| + { ID id-DCH-ENH-Information CRITICALITY reject EXTENSION DCH-ENH- +Information PRESENCE optional}| + { ID id-Radio-Links-without-DPCH-FDPCH-Indication CRITICALITY reject EXTENSION Radio-Links- +without-DPCH-FDPCH-Indication PRESENCE optional}| + { ID id-UL-DPCCH2-Information CRITICALITY reject EXTENSION UL-DPCCH2- +Information PRESENCE optional}| + { ID id-Downlink-TPC-enhancements-Information CRITICALITY reject EXTENSION Downlink-TPC- +enhancements-Information PRESENCE optional}, + ... +} + +Additional-HS-Cell-Information-RL-Setup-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF +Additional-HS-Cell-Information-RL-Setup-ItemIEs + +Additional-HS-Cell-Information-RL-Setup-ItemIEs ::=SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + c-ID C-ID, + hs-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information, + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information- +RL-Setup-ItemIEs-ExtIEs} } OPTIONAL, + ... +} + +Additional-HS-Cell-Information-RL-Setup-ItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { + ul-ScramblingCode UL-ScramblingCode, + minUL-ChannelisationCodeLength MinUL-ChannelisationCodeLength, + maxNrOfUL-DPDCHs MaxNrOfUL-DPDCHs OPTIONAL, + -- This IE shall be present if Min UL Channelisation Code length IE is set to 4 -- + ul-PunctureLimit PunctureLimit, + tFCS TFCS, + ul-DPCCH-SlotFormat UL-DPCCH-SlotFormat, + ul-SIR-Target UL-SIR, + diversityMode DiversityMode, + not-Used-sSDT-CellID-Length NULL OPTIONAL, + not-Used-s-FieldLength NULL OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-Information-RL- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DPC-Mode CRITICALITY reject EXTENSION DPC-Mode + PRESENCE optional }| + { ID id-UL-DPDCH-Indicator-For-E-DCH-Operation CRITICALITY reject EXTENSION UL-DPDCH- +Indicator-For-E-DCH-Operation PRESENCE optional }, +} + +``` + +``` + + ... + } + + DL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { + tFCS TFCS, + dl-DPCH-SlotFormat DL-DPCH-SlotFormat, + tFCI-SignallingMode TFCI-SignallingMode, + tFCI-Presence TFCI-Presence OPTIONAL, + -- this IE shall be present if the DL DPCH slot format IE is set to any of the values from 12 to + 16 -- + multiplexingPosition MultiplexingPosition, + not-Used-pDSCH-RL-ID NULL OPTIONAL, + not-Used-pDSCH-CodeMapping NULL OPTIONAL, + powerOffsetInformation PowerOffsetInformation-RL-SetupRqstFDD, + fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, + limitedPowerIncrease LimitedPowerIncrease, + innerLoopDLPCStatus InnerLoopDLPCStatus, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-Information-RL- + SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + DL-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + PowerOffsetInformation-RL-SetupRqstFDD ::= SEQUENCE { + pO1-ForTFCI-Bits PowerOffset, + pO2-ForTPC-Bits PowerOffset, + pO3-ForPilotBits PowerOffset, + iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation- + RL-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + PowerOffsetInformation-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + RL-InformationList-RL-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF + ProtocolIE-Single-Container{{ RL-InformationItemIE-RL-SetupRqstFDD }} + + RL-InformationItemIE-RL-SetupRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationItem-RL-SetupRqstFDD CRITICALITY notify TYPE RL- + InformationItem-RL-SetupRqstFDD PRESENCE mandatory } + } + + RL-InformationItem-RL-SetupRqstFDD ::= SEQUENCE { + rL-ID RL-ID, + c-ID C-ID, + firstRLS-indicator FirstRLS-Indicator, + frameOffset FrameOffset, + chipOffset ChipOffset, + propagationDelay PropagationDelay OPTIONAL, + diversityControlField DiversityControlField OPTIONAL, + -- This IE shall be present if the RL is not the first one in the RL Information IE + dl-CodeInformation FDD-DL-CodeInformation, + initialDL-transmissionPower DL-Power, + maximumDL-power DL-Power, + minimumDL-power DL-Power, + not-Used-sSDT-Cell-Identity NULL OPTIONAL, + transmitDiversityIndicator TransmitDiversityIndicator OPTIONAL, + -- This IE shall be present if Diversity Mode IE in UL DPCH Information group is not set to + "none" + iE-Extensions ProtocolExtensionContainer { { RL-InformationItem-RL- + SetupRqstFDD-ExtIEs} } OPTIONAL, + ... + } + + RL-InformationItem-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific- + DCH-Info PRESENCE optional}| + { ID id-DelayedActivation CRITICALITY reject EXTENSION + DelayedActivation PRESENCE optional}| + { ID id-Primary-CPICH-Usage-for-Channel-Estimation CRITICALITY ignore EXTENSION Primary-CPICH- + Usage-for-Channel-Estimation PRESENCE optional}| + { ID id-Secondary-CPICH-Information CRITICALITY ignore EXTENSION + CommonPhysicalChannelID PRESENCE optional}| + } + +``` + +``` + + { ID id-E-DCH-RL-Indication + Indication PRESENCE optional}| + { ID id-RL-Specific-E-DCH-Info + DCH-Info PRESENCE optional}| + { ID id-SynchronisationIndicator + SynchronisationIndicator PRESENCE optional}| + { ID id-ExtendedPropagationDelay + ExtendedPropagationDelay PRESENCE optional}| + { ID id-F-DPCH-SlotFormat + SlotFormat PRESENCE optional}| + { ID id-HSDSCH-PreconfigurationSetup + PreconfigurationSetup PRESENCE optional}| + { ID id-E-RNTI + PRESENCE optional}| + { ID id-Non-Serving-RL-Preconfig-Setup + RL-Preconfig-Setup PRESENCE optional}| + { ID id-FTPICH-Information + Information PRESENCE optional}| + { ID id-TPC-slot-position + position PRESENCE optional}, + ... + } + } + } + } + } +} + +``` + +``` + +E-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { + maxSet-E-DPDCHs Max-Set-E-DPDCHs, + ul-PunctureLimit PunctureLimit, + e-TFCS-Information E-TFCS-Information, + e-TTI E-TTI, + e-DPCCH-PO E-DPCCH-PO, + e-RGCH-2-IndexStepThreshold E-RGCH-2-IndexStepThreshold, + e-RGCH-3-IndexStepThreshold E-RGCH-3-IndexStepThreshold, + hARQ-Info-for-E-DCH HARQ-Info-for-E-DCH, + hSDSCH-Configured-Indicator HSDSCH-Configured-Indicator, + iE-Extensions ProtocolExtensionContainer { { E-DPCH-Information- +RL-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +E-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-RNTI CRITICALITY reject EXTENSION E-RNTI + PRESENCE optional }| + { ID id-MinimumReducedE-DPCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE- +DPDCH-GainFactor PRESENCE optional }, + ... +} + +``` + +``` + +F-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { + powerOffsetInformation PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD, + fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, + limitedPowerIncrease LimitedPowerIncrease, + innerLoopDLPCStatus InnerLoopDLPCStatus, + iE-Extensions ProtocolExtensionContainer { { F-DPCH-Information-RL- +SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +F-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD ::= SEQUENCE { + pO2-ForTPC-Bits PowerOffset, + --This IE shall be ignored by Node B + iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation-F- +DPCH-RL-SetupRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- RADIO LINK SETUP REQUEST TDD +-- +-- ***** + +``` + +``` + +RadioLinkSetupRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkSetupRequestTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupRequestTDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY reject TYPE CRNC- + CommunicationContextID PRESENCE mandatory }| + { ID id-UL-CCTrCH-InformationList-RL-SetupRqstTDD CRITICALITY notify TYPE UL-CCTrCH- + InformationList-RL-SetupRqstTDD PRESENCE optional }| + { ID id-DL-CCTrCH-InformationList-RL-SetupRqstTDD CRITICALITY notify TYPE DL-CCTrCH- + InformationList-RL-SetupRqstTDD PRESENCE optional }| + { ID id-DCH-TDD-Information CRITICALITY reject TYPE DCH-TDD- + Information PRESENCE optional }| + { ID id-DSCH-TDD-Information CRITICALITY reject TYPE DSCH-TDD- + Information PRESENCE optional }| + { ID id-USCH-Information CRITICALITY reject TYPE USCH- + Information PRESENCE optional }| + { ID id-RL-Information-RL-SetupRqstTDD CRITICALITY reject TYPE RL-Information- + RL-SetupRqstTDD PRESENCE mandatory }, + ... +} + +RadioLinkSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HSDSCH-TDD-Information CRITICALITY reject EXTENSION HSDSCH-TDD-Information + PRESENCE optional }| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional }| + -- The IE shall be present if HS-DSCH Information IE is present + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE conditional }| + -- The IE shall be present if HS-DSCH Information IE is present + { ID id-PDSCH-RL-ID CRITICALITY ignore EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DCH-Information CRITICALITY reject EXTENSION E-DCH-Information + PRESENCE optional }| + { ID id-E-DCH-Serving-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DCH-768-Information CRITICALITY reject EXTENSION E-DCH-768-Information + PRESENCE optional }| + { ID id-E-DCH-LCR-Information CRITICALITY reject EXTENSION E-DCH-LCR-Information + PRESENCE optional }| + { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP + PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-ContinuousPacketConnectivity-DRX-InformationLCR CRITICALITY reject EXTENSION + ContinuousPacketConnectivity-DRX-InformationLCR PRESENCE optional }| + { ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION HS- + DSCH-Semi-PersistentScheduling-Information-LCR PRESENCE optional }| + { ID id-E-DCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION E-DCH- + Semi-PersistentScheduling-Information-LCR PRESENCE optional }| + { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION IdleIntervalInformation + PRESENCE optional }| + { ID id-UE-Selected-MBMS-Service-Information CRITICALITY ignore EXTENSION UE-Selected-MBMS- + Service-Information PRESENCE optional }| + { ID id-HSSCCH-TPC-StepSize CRITICALITY ignore EXTENSION TDD-TPC-DownlinkStepSize + PRESENCE optional }| + { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH- + MeasurementOccasion-Information PRESENCE optional }| + { ID id-HSDSCH-RNTI-For-FACH CRITICALITY ignore EXTENSION HSDSCH-RNTI + PRESENCE optional }| + { ID id-Multi-Carrier-EDCH-Setup CRITICALITY reject EXTENSION Multi-Carrier-EDCH-Info + PRESENCE optional }| + { ID id-MU-MIMO-InformationLCR CRITICALITY ignore EXTENSION MU-MIMO-InformationLCR + PRESENCE optional }| + { ID id-UE-Support-of-non-rectangular-resource-allocation CRITICALITY ignore EXTENSION UE- + Support-of-non-rectangular-resource-allocation PRESENCE optional }, + ... +} + +UL-CCTrCH-InformationList-RL-SetupRqstTDD ::= SEQUENCE (SIZE(1..maxNrOfCCTrCHs)) OF + ProtocolIE-Single-Container{{ UL-CCTrCH-InformationItemIE-RL-SetupRqstTDD }} + +UL-CCTrCH-InformationItemIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD CRITICALITY notify TYPE UL-CCTrCH- + InformationItem-RL-SetupRqstTDD PRESENCE mandatory } +} + +``` + +``` + +} + +UL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { + CCTrCH-ID CCTrCH-ID, + tFCS tFCS, + tFCI-Coding tFCI-Coding, + punctureLimit PunctureLimit, + uL-DPCH-Information uL-DPCH-Information-RL-SetupRqstTDD OPTIONAL, -- + Applicable to 3.84Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { UL-CCTrCH- + InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-LCR-Information-RL-SetupRqstTDD CRITICALITY notify EXTENSION UL-DPCH-LCR- + Information-RL-SetupRqstTDD PRESENCE optional }| -- Applicable to 1.28Mcps TDD only + { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR + PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + { ID id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD CRITICALITY reject EXTENSION TDD-TPC- + UplinkStepSize-LCR PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + { ID id-UL-DPCH-768-Information-RL-SetupRqstTDD CRITICALITY notify EXTENSION UL-DPCH-768- + Information-RL-SetupRqstTDD PRESENCE optional }, -- Applicable to 7.68Mcps TDD only + ... +} + +UL-DPCH-Information-RL-SetupRqstTDD ::= ProtocolIE-Single-Container{{ UL-DPCH-InformationIE-RL- +SetupRqstTDD }} + +UL-DPCH-InformationIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationList-RL-SetupRqstTDD CRITICALITY notify TYPE UL-DPCH- + InformationItem-RL-SetupRqstTDD PRESENCE mandatory } +} + +UL-DPCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information uL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-InformationItem- + RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-LCR-Information-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-TimeslotLCR-Information uL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-LCR- + InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-768-Information-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot768-Information uL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-768- + InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` +DL-CCTrCH-InformationList-RL-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE- +Single-Container{{ DL-CCTrCH-InformationItemIE-RL-SetupRqstTDD }} +``` + +``` +DL-CCTrCH-InformationItemIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD CRITICALITY notify TYPE DL-CCTrCH- +InformationItem-RL-SetupRqstTDD PRESENCE mandatory} +} +``` + +``` +DL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { + cCTrCH-ID cCTrCH-ID, + tFCS TFCS, + tFCI-Coding TFCI-Coding, + punctureLimit PunctureLimit, + tdd-TPC-DownlinkStepSize TDD-TPC-DownlinkStepSize, + cCTrCH-TPCList cCTrCH-TPCList-RL-SetupRqstTDD OPTIONAL, + dL-DPCH-Information dL-DPCH-Information-RL-SetupRqstTDD OPTIONAL, -- +Applicable to 3.84Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH- +InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +DL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-LCR-Information-RL-SetupRqstTDD CRITICALITY notify EXTENSION DL-DPCH- +LCR-Information-RL-SetupRqstTDD PRESENCE optional }| -- Applicable to 1.28Mcps TDD only + { ID id-CCTrCH-Initial-DL-Power-RL-SetupRqstTDD CRITICALITY ignore EXTENSION DL-Power +PRESENCE optional }| + { ID id-CCTrCH-Maximum-DL-Power-RL-SetupRqstTDD CRITICALITY ignore EXTENSION DL-Power +PRESENCE optional }| + { ID id-CCTrCH-Minimum-DL-Power-RL-SetupRqstTDD CRITICALITY ignore EXTENSION DL-Power +PRESENCE optional }| + { ID id-DL-DPCH-768-Information-RL-SetupRqstTDD CRITICALITY notify EXTENSION DL-DPCH- +768-Information-RL-SetupRqstTDD PRESENCE optional }, -- Applicable to 7.68Mcps TDD only + ... +} +``` + +``` +CCTrCH-TPCList-RL-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCItem-RL- +SetupRqstTDD +``` + +``` +CCTrCH-TPCItem-RL-SetupRqstTDD ::= SEQUENCE { + cCTrCH-ID cCTrCH-ID, + iE-Extensions ProtocolExtensionContainer { { CCTrCH-TPCItem-RL- +SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CCTrCH-TPCItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DL-DPCH-Information-RL-SetupRqstTDD ::= ProtocolIE-Single-Container{{ DL-DPCH-InformationIE-RL- +SetupRqstTDD }} +``` + +``` +DL-DPCH-InformationIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationList-RL-SetupRqstTDD CRITICALITY notify TYPE DL-DPCH- +InformationItem-RL-SetupRqstTDD PRESENCE mandatory } +} +``` + +``` +DL-DPCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information DL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-InformationItem- +RL-SetupRqstTDD-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +DL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DL-DPCH-LCR-Information-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-TimeslotLCR-Information DL-TimeslotLCR-Information, + tstdIndicator TSTD-Indicator, +} +``` + +``` + + iE-Extensions + InformationItem-RL-SetupRqstTDD-ExtIEs } } + ... + } + + DL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + DL-DPCH-768-Information-RL-SetupRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot768-Information + iE-Extensions ProtocolExtensionContainer { DL-DPCH-768- + InformationItem-RL-SetupRqstTDD-ExtIEs } } + ... + } + + DL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + RL-Information-RL-SetupRqstTDD ::= SEQUENCE { + rL-ID rL-ID, + c-ID c-ID, + frameOffset FrameOffset, + specialBurstScheduling SpecialBurstScheduling, + initialDL-transmissionPower + maximumDL-power DL-Power, + minimumDL-power DL-Power, + dL-TimeSlotISCPInfo DL-Power, + 3.84Mcps TDD and 7.68Mcps TDD only + iE-Extensions ProtocolExtensionContainer { RL-Information-RL- + SetupRqstTDD-ExtIEs } } + ... + } + + RL-Information-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TimeslotISCP-LCR-InfoList-RL-SetupRqstTDD CRITICALITY reject EXTENSION DL- + TimeslotISCPInfoLCR PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL- + Specific-DCH-Info PRESENCE optional }| + { ID id-DelayedActivation CRITICALITY reject EXTENSION + DelayedActivation PRESENCE optional }| + { ID id-UL-Synchronisation-Parameters-LCR CRITICALITY reject EXTENSION UL- + Synchronisation-Parameters-LCR PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN + PRESENCE optional }, + -- Mandatory for 1.28Mcps TDD when using multiple frequencies + ... + } + + -- ***** + -- + -- RADIO LINK SETUP RESPONSE FDD + -- + -- ***** + + RadioLinkSetupResponseFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkSetupResponseFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupResponseFDD-Extensions}} + OPTIONAL, + ... + } + + RadioLinkSetupResponseFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- + CommunicationContextID PRESENCE mandatory }| + { ID id-NodeB-CommunicationContextID CRITICALITY ignore TYPE NodeB- + CommunicationContextID PRESENCE mandatory }| + { ID id-CommunicationControlPortID CRITICALITY ignore TYPE + CommunicationControlPortID PRESENCE mandatory }| + { ID id-RL-InformationResponseList-RL-SetupRspFDD CRITICALITY ignore TYPE RL- + InformationResponseList-RL-SetupRspFDD PRESENCE mandatory }| + } + +``` + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE +CriticalityDiagnostics PRESENCE optional }, + ... +} + +RadioLinkSetupResponseFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD- +Information-Response PRESENCE optional }| + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response CRITICALITY ignore +EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response PRESENCE +optional }| + { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional- +HS-Cell-Information-Response-List PRESENCE optional }| + { ID id-Additional-EDCH-Cell-Information-Response CRITICALITY ignore EXTENSION +Additional-EDCH-Cell-Information-Response-List PRESENCE optional }, + ... +} +Additional-HS-Cell-Information-Response-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF +Additional-HS-Cell-Information-Response-ItemIEs + +Additional-HS-Cell-Information-Response-ItemIEs ::= SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + hs-DSCH-FDD-Secondary-Serving-Information-Response HS-DSCH-FDD-Secondary-Serving-Information- +Response, + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information- +Response-ItemIEs-ExtIEs } } OPTIONAL, + ... +} + +Additional-HS-Cell-Information-Response-ItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RL-InformationResponseList-RL-SetupRspFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single- +Container{ { RL-InformationResponseItemIE-RL-SetupRspFDD } } + +RL-InformationResponseItemIE-RL-SetupRspFDD NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationResponseItem-RL-SetupRspFDD CRITICALITY ignore TYPE RL- +InformationResponseItem-RL-SetupRspFDD PRESENCE mandatory } +} + +RL-InformationResponseItem-RL-SetupRspFDD ::= SEQUENCE { + rL-ID RL-ID, + rL-Set-ID RL-Set-ID, + received-total-wide-band-power Received-total-wide-band-power-Value, + diversityIndication DiversityIndication-RL-SetupRspFDD, + not-Used-dSCH-InformationResponseList NULL OPTIONAL, + sSDT-SupportIndicator SSDT-SupportIndicator, + iE-Extensions ProtocolExtensionContainer { { RL- +InformationResponseItem-RL-SetupRspFDD-ExtIEs } } OPTIONAL, + ... +} + +RL-InformationResponseItem-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL- +PowerBalancing-ActivationIndicator PRESENCE optional }| + { ID id-E-DCH-RL-Set-ID CRITICALITY ignore EXTENSION RL-Set-ID + PRESENCE optional }| + { ID id-E-DCH-FDD-DL-Control-Channel-Information CRITICALITY ignore EXTENSION E-DCH-FDD-DL- +Control-Channel-Information PRESENCE optional }| + { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH- +TimingAdjustment PRESENCE optional }| + { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationInfo PRESENCE optional }| + { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving- +RL-Preconfig-Info PRESENCE optional }, + ... +} + +DiversityIndication-RL-SetupRspFDD ::= CHOICE { + combining Combining-RL-SetupRspFDD, + nonCombiningOrFirstRL NonCombiningOrFirstRL-RL-SetupRspFDD +} + +Combining-RL-SetupRspFDD ::= SEQUENCE { + rL-ID RL-ID, + iE-Extensions ProtocolExtensionContainer { { Combining-RL- +SetupRspFDD-ExtIEs } } OPTIONAL, +} + +``` + +``` + + ... + } + + Combining-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + NonCombiningOrFirstRL-RL-SetupRspFDD ::= SEQUENCE { + dCH-InformationResponse DCH-InformationResponse, + iE-Extensions ProtocolExtensionContainer { { + NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs } } OPTIONAL, + ... + } + + NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD-Information- + Response PRESENCE optional }, + ... + } + + -- ***** + -- + -- RADIO LINK SETUP RESPONSE TDD + -- + -- ***** + + RadioLinkSetupResponseTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkSetupResponseTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupResponseTDD-Extensions}} + OPTIONAL, + ... + } + + RadioLinkSetupResponseTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- + CommunicationContextID PRESENCE mandatory } | + { ID id-NodeB-CommunicationContextID CRITICALITY ignore TYPE NodeB- + CommunicationContextID PRESENCE mandatory } | + { ID id-CommunicationControlPortID CRITICALITY ignore TYPE + CommunicationControlPortID PRESENCE mandatory } | + { ID id-RL-InformationResponse-RL-SetupRspTDD CRITICALITY ignore TYPE RL-InformationResponse- + RL-SetupRspTDD PRESENCE optional } | + -- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + RadioLinkSetupResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-RL-InformationResponse-LCR-RL-SetupRspTDD CRITICALITY ignore EXTENSION RL- + InformationResponse-LCR-RL-SetupRspTDD PRESENCE optional } | -- Mandatory for 1.28Mcps TDD, Not + Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD- + Information-Response PRESENCE optional } | + { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH- + Information-Response PRESENCE optional } | + { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore + EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR PRESENCE optional } | + { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore + EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional } | + { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore + EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional } | + { ID id-E-RNTI-For-FACH CRITICALITY ignore EXTENSION E-RNTI + PRESENCE optional } | + { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier- + EDCH-Information-Response PRESENCE optional } | + { ID id-MU-MIMO-Information-Response CRITICALITY reject EXTENSION MU-MIMO- + Information-Response PRESENCE optional } | + { ID id-Non-rectangular-resource-allocation-indicator CRITICALITY reject EXTENSION Non- + rectangular-resource-allocation-indicator PRESENCE optional } | + { ID id-Non-rectangular-resource-timeslot-set CRITICALITY reject EXTENSION Non- + rectangular-resource-timeslot-set PRESENCE optional }, + ... + } + + RL-InformationResponse-RL-SetupRspTDD ::= SEQUENCE { + rL-ID RL-ID, + uL-TimeSlot-ISCP-Info UL-TimeSlot-ISCP-Info, + } + +``` + +``` + + ul-PhysCH-SF-Variation + dCH-InformationResponseList + OPTIONAL, + dSCH-InformationResponseList + OPTIONAL, + uSCH-InformationResponseList + OPTIONAL, + iE-Extensions + InformationResponseList-RL-SetupRspTDD-ExtIEs} } + ... + } + + RL-InformationResponseList-RL-SetupRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + DCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container{{ DCH- + InformationResponseListIEs-RL-SetupRspTDD }} + + DCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= { + { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse + PRESENCE mandatory} + } + + DSCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{ DSCH- + InformationResponseListIEs-RL-SetupRspTDD }} + + DSCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= { + { ID id-DSCH-InformationResponse CRITICALITY ignore TYPE DSCH-InformationResponse + PRESENCE mandatory } + } + + USCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{ USCH- + InformationResponseListIEs-RL-SetupRspTDD }} + + USCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= { + { ID id-USCH-InformationResponse CRITICALITY ignore TYPE USCH-InformationResponse + PRESENCE mandatory } + } + + RL-InformationResponse-LCR-RL-SetupRspTDD ::= SEQUENCE { + RL-ID + uL-TimeSlot-ISCPLCR-Info + ul-PhysCH-SF-Variation + dCH-InformationResponseList + OPTIONAL, + dSCH-InformationResponseList + OPTIONAL, + uSCH-InformationResponseList + OPTIONAL, + iE-Extensions + InformationResponseList-LCR-RL-SetupRspTDD-ExtIEs} } + ... + } + + RL-InformationResponseList-LCR-RL-SetupRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + +-- ***** +-- +-- RADIO LINK SETUP FAILURE FDD +-- +-- ***** + +RadioLinkSetupFailureFDD ::= SEQUENCE { + protocolIEs + protocolExtensions + OPTIONAL, + ... +} + +RadioLinkSetupFailureFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC-CommunicationContextID + PRESENCE mandatory } | + { ID id-NodeB-CommunicationContextID CRITICALITY ignore TYPE NodeB- + CommunicationContextID PRESENCE conditional } | + -- This IE shall be present if at least one of the radio links has been successfully set up +} + +``` + +``` + + { ID id-CommunicationControlPortID CRITICALITY ignore TYPE CommunicationControlPortID + PRESENCE optional }| + { ID id-CauseLevel-RL-SetupFailureFDD CRITICALITY ignore TYPE CauseLevel-RL- +SetupFailureFDD PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + +RadioLinkSetupFailureFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CauseLevel-RL-SetupFailureFDD ::= CHOICE { + generalCause GeneralCauseList-RL-SetupFailureFDD, + rLSpecificCause RLSpecificCauseList-RL-SetupFailureFDD, + ... +} + +GeneralCauseList-RL-SetupFailureFDD ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL- +SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +GeneralCauseItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLSpecificCauseList-RL-SetupFailureFDD ::= SEQUENCE { + unsuccessful-RL-InformationRespList-RL-SetupFailureFDD Unsuccessful-RL-InformationRespList- +RL-SetupFailureFDD, + successful-RL-InformationRespList-RL-SetupFailureFDD Successful-RL-InformationRespList- +RL-SetupFailureFDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RLSpecificCauseItem- +RL-SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +RLSpecificCauseItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD- +Information-Response PRESENCE optional }| + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response CRITICALITY ignore + EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response PRESENCE +optional }| + { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional- +HS-Cell-Information-Response-List PRESENCE optional }| + { ID id-Additional-EDCH-Cell-Information-Response CRITICALITY ignore EXTENSION + Additional-EDCH-Cell-Information-Response-List PRESENCE optional }, + ... +} + +Unsuccessful-RL-InformationRespList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF +ProtocolIE-Single-Container { { Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureFDD } } + +Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureFDD NBAP-PROTOCOL-IES ::= { + { ID id-Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD CRITICALITY ignore TYPE +Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD PRESENCE mandatory } +} + +Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD ::= SEQUENCE { + rL-ID RL-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { Unsuccessful-RL- +InformationRespItem-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Successful-RL-InformationRespList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (1.. maxNrOfRLs)) OF +ProtocolIE-Single-Container { { Successful-RL-InformationRespItemIE-RL-SetupFailureFDD } } + +Successful-RL-InformationRespItemIE-RL-SetupFailureFDD NBAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-Successful-RL-InformationRespItem-RL-SetupFailureFDD CRITICALITY ignore TYPE +Successful-RL-InformationRespItem-RL-SetupFailureFDD PRESENCE mandatory } +} + +Successful-RL-InformationRespItem-RL-SetupFailureFDD ::= SEQUENCE { + rL-ID RL-ID, + rL-Set-ID RL-Set-ID, + received-total-wide-band-power Received-total-wide-band-power-Value, + diversityIndication DiversityIndication-RL-SetupFailureFDD, + not-Used-dSCH-InformationResponseList NULL OPTIONAL, + not-Used-tFCI2-BearerInformationResponse NULL OPTIONAL, + sSDT-SupportIndicator SSDT-SupportIndicator, + iE-Extensions ProtocolExtensionContainer { { Successful-RL- +InformationRespItem-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +Successful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL- +PowerBalancing-ActivationIndicator PRESENCE optional }| + { ID id-E-DCH-RL-Set-ID CRITICALITY ignore EXTENSION RL-Set-ID + PRESENCE optional }| + { ID id-E-DCH-FDD-DL-Control-Channel-Information CRITICALITY ignore EXTENSION E-DCH-FDD-DL- +Control-Channel-Information PRESENCE optional }| + { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH- +TimingAdjustment PRESENCE optional }| + { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationInfo PRESENCE optional }| + { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving- +RL-Preconfig-Info PRESENCE optional }, + ... +} + +DiversityIndication-RL-SetupFailureFDD ::= CHOICE { + combining Combining-RL-SetupFailureFDD, + nonCombiningOrFirstRL NonCombiningOrFirstRL-RL-SetupFailureFDD +} + +Combining-RL-SetupFailureFDD ::= SEQUENCE { + rL-ID RL-ID, + iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL- +SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +CombiningItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +NonCombiningOrFirstRL-RL-SetupFailureFDD ::= SEQUENCE { + dCH-InformationResponse DCH-InformationResponse, + iE-Extensions ProtocolExtensionContainer { { +NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD-Information- +Response PRESENCE optional }, + ... +} + +-- **************************************************************************** +-- +-- RADIO LINK SETUP FAILURE TDD +-- +-- **************************************************************************** + +RadioLinkSetupFailureTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkSetupFailureTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupFailureTDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkSetupFailureTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- +CommunicationContextID PRESENCE mandatory }| + +``` + +``` + + { ID id-CauseLevel-RL-SetupFailureTDD CRITICALITY ignore TYPE CauseLevel-RL- +SetupFailureTDD PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + RadioLinkSetupFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + CauseLevel-RL-SetupFailureTDD ::= CHOICE { + generalCause GeneralCauseList-RL-SetupFailureTDD, + rlSpecificCause RLSpecificCauseList-RL-SetupFailureTDD, + ... + } + + GeneralCauseList-RL-SetupFailureTDD ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-SetupFailureTDD- +ExtIEs} } OPTIONAL, + ... + } + + GeneralCauseItem-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + RLSpecificCauseList-RL-SetupFailureTDD ::= SEQUENCE { + unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD Unsuccessful-RL-InformationRespItem-RL- +SetupFailureTDD, + iE-Extensions ProtocolExtensionContainer { { +RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs} } OPTIONAL, + ... + } + + RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD ::= ProtocolIE-Single-Container { +{Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD} } + + Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD NBAP-PROTOCOL-IES ::= { + { ID id-Unsuccessful-RL-InformationResp-RL-SetupFailureTDD CRITICALITY ignore TYPE +Unsuccessful-RL-InformationResp-RL-SetupFailureTDD PRESENCE mandatory } + } + + Unsuccessful-RL-InformationResp-RL-SetupFailureTDD ::= SEQUENCE { + rl-ID RL-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { Unsuccessful-RL- +InformationResp-RL-SetupFailureTDD-ExtIEs} } OPTIONAL, + ... + } + + Unsuccessful-RL-InformationResp-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- RADIO LINK ADDITION REQUEST FDD + -- + -- ***** + + RadioLinkAdditionRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkAdditionRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionRequestFDD-Extensions}} + OPTIONAL, + ... + } + + RadioLinkAdditionRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY reject TYPE NodeB- +CommunicationContextID PRESENCE mandatory }| + { ID id-Compressed-Mode-Deactivation-Flag CRITICALITY reject TYPE Compressed-Mode- +Deactivation-Flag PRESENCE optional }| + } + +``` + +``` + + { ID id-RL-InformationList-RL-AdditionRqstFDD CRITICALITY notify TYPE RL-InformationList-RL- +AdditionRqstFDD PRESENCE mandatory }, + ... +} + +RadioLinkAdditionRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Initial-DL-DPCH-TimingAdjustment-Allowed CRITICALITY ignore EXTENSION Initial-DL- +DPCH-TimingAdjustment-Allowed PRESENCE optional}| + { ID id-Serving-E-DCH-RL-ID CRITICALITY reject EXTENSION Serving-E-DCH- +RL-ID PRESENCE optional}| + { ID id-Serving-Cell-Change-CFN CRITICALITY reject EXTENSION CFN + PRESENCE optional}| + { ID id-HS-DSCH-Serving-Cell-Change-Info CRITICALITY reject EXTENSION HS-DSCH- +Serving-Cell-Change-Info PRESENCE optional}| + { ID id-E-DPCH-Information-RL-AdditionReqFDD CRITICALITY reject EXTENSION E-DPCH- +Information-RL-AdditionReqFDD PRESENCE optional}| + { ID id-E-DCH-FDD-Information CRITICALITY reject EXTENSION E-DCH-FDD- +Information PRESENCE conditional}| + -- This IE shall be present if E-DPCH Information is present + { ID id-Additional-HS-Cell-Information-RL-Addition CRITICALITY reject EXTENSION Additional-HS- +Cell-Information-RL-Addition-List PRESENCE optional}| + { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE- +AggregateMaximumBitRate PRESENCE optional}| + { ID id-Additional-EDCH-Cell-Information-RL-Add-Req CRITICALITY reject EXTENSION Additional- +EDCH-Cell-Information-RL-Add-Req PRESENCE optional}| + { ID id-Active-Pattern-Sequence-Information CRITICALITY reject EXTENSION Active- +Pattern-Sequence-Information PRESENCE optional}| + { ID id-UL-CLTD-Information CRITICALITY reject EXTENSION UL-CLTD- +Information PRESENCE optional}| + { ID id-E-DCH-Decoupling-Indication CRITICALITY reject EXTENSION E-DCH- +Decoupling-Indication PRESENCE optional}| + { ID id-Radio-Links-without-DPCH-FDPCH-Indication CRITICALITY reject EXTENSION Radio-Links- +without-DPCH-FDPCH-Indication PRESENCE optional}| + { ID id-UL-DPCCH2-Information CRITICALITY reject EXTENSION UL-DPCCH2- +Information PRESENCE optional}| + { ID id-Downlink-TPC-enhancements-Information CRITICALITY reject EXTENSION Downlink-TPC- +enhancements-Information PRESENCE optional}, + ... +} + +Additional-HS-Cell-Information-RL-Addition-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF +Additional-HS-Cell-Information-RL-Addition-ItemIEs + +Additional-EDCH-Cell-Information-RL-Add-Req ::=SEQUENCE{ + setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency Setup-Or-Addition- +Of-EDCH-On-secondary-UL-Frequency, + iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information- +RL-Add-Req-ExtIEs} } OPTIONAL, + ... +} + +Additional-EDCH-Cell-Information-RL-Add-Req-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency ::= CHOICE { + setup Additional-EDCH-Setup-Info, + addition Additional-EDCH-Cell-Information-To-Add-List, + ... +} + +Additional-HS-Cell-Information-RL-Addition-ItemIEs ::=SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + c-ID C-ID, + hs-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information, + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information- +RL-Addition-ItemIEs-ExtIEs} } OPTIONAL, + ... +} + +Additional-HS-Cell-Information-RL-Addition-ItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RL-InformationList-RL-AdditionRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single- +Container {{ RL-InformationItemIE-RL-AdditionRqstFDD}} + +RL-InformationItemIE-RL-AdditionRqstFDD NBAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-RL-InformationItem-RL-AdditionRqstFDD CRITICALITY notify TYPE RL-InformationItem-RL- +AdditionRqstFDD PRESENCE mandatory} +} + +RL-InformationItem-RL-AdditionRqstFDD ::= SEQUENCE { + rL-ID RL-ID, + c-ID C-ID, + frameOffset FrameOffset, + chipOffset ChipOffset, + diversityControlField DiversityControlField, + dl-CodeInformation FDD-DL-CodeInformation, + initialDL-TransmissionPower DL-Power OPTIONAL, + maximumDL-Power DL-Power OPTIONAL, + minimumDL-Power DL-Power OPTIONAL, + not-Used-sSDT-CellIdentity NULL OPTIONAL, + transmitDiversityIndicator TransmitDiversityIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RL-InformationItem- +RL-AdditionRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +RL-InformationItem-RL-AdditionRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DLReferencePower CRITICALITY ignore EXTENSION DL-Power + PRESENCE optional} | + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info + PRESENCE optional} | + { ID id-DelayedActivation CRITICALITY reject EXTENSION DelayedActivation + PRESENCE optional} | + { ID id-E-DCH-RL-Indication CRITICALITY reject EXTENSION E-DCH-RL-Indication + PRESENCE optional} | + { ID id-RL-Specific-E-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-E-DCH-Info + PRESENCE optional} | + { ID id-SynchronisationIndicator CRITICALITY ignore EXTENSION +SynchronisationIndicator PRESENCE optional} | + { ID id-F-DPCH-SlotFormat CRITICALITY reject EXTENSION F-DPCH-SlotFormat + PRESENCE optional} | + { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationSetup PRESENCE optional} | + { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore EXTENSION Non-Serving-RL- +Preconfig-Setup PRESENCE optional} | + { ID id-FTPICH-Information CRITICALITY ignore EXTENSION FTPICH-Information + PRESENCE optional} | + { ID id-TPC-slot-position CRITICALITY ignore EXTENSION TPC-slot-position + PRESENCE optional}, + ... +} + +E-DPCH-Information-RL-AdditionReqFDD ::= SEQUENCE { + maxSet-E-DPDCHs Max-Set-E-DPDCHs, + ul-PunctureLimit PunctureLimit, + e-TFCS-Information E-TFCS-Information, + e-TTI E-TTI, + e-DPCCH-PO E-DPCCH-PO, + e-RGCH-2-IndexStepThreshold E-RGCH-2-IndexStepThreshold, + e-RGCH-3-IndexStepThreshold E-RGCH-3-IndexStepThreshold, + hARQ-Info-for-E-DCH HARQ-Info-for-E-DCH, + iE-Extensions ProtocolExtensionContainer { { E-DPCH-Information- +RL-AdditionReqFDD-ExtIEs} } OPTIONAL, + ... +} + +E-DPCH-Information-RL-AdditionReqFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HSDSCH-Configured-Indicator CRITICALITY reject EXTENSION HSDSCH-Configured- +Indicator PRESENCE mandatory } | + -- This shall be present for EDPCH configuration with HSDCH + { ID id-MinimumReducedE-DPCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE- +DPCH-GainFactor PRESENCE optional }, + ... +} + +-- **************************************************************************** +-- +-- RADIO LINK ADDITION REQUEST TDD +-- +-- **************************************************************************** + +RadioLinkAdditionRequestTDD ::= SEQUENCE { + +``` + +``` + + protocolIEs ProtocolIE-Container {{RadioLinkAdditionRequestTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionRequestTDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkAdditionRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY reject TYPE NodeB- + CommunicationContextID PRESENCE mandatory }| + { ID id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD CRITICALITY reject TYPE UL-CCTrCH- + InformationList-RL-AdditionRqstTDD PRESENCE optional }| + { ID id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD CRITICALITY reject TYPE DL-CCTrCH- + InformationList-RL-AdditionRqstTDD PRESENCE optional }| + { ID id-RL-Information-RL-AdditionRqstTDD CRITICALITY reject TYPE RL-Information- + RL-AdditionRqstTDD PRESENCE mandatory }, + ... +} + +RadioLinkAdditionRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HSDSCH-TDD-Information CRITICALITY reject EXTENSION HSDSCH-TDD-Information + PRESENCE optional }| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional }| + -- The IE shall be present if HS-PDSCH RL ID IE is present. + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DCH-Information CRITICALITY reject EXTENSION E-DCH-Information + PRESENCE optional }| + { ID id-E-DCH-Serving-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DCH-768-Information CRITICALITY reject EXTENSION E-DCH-768-Information + PRESENCE optional }| + { ID id-E-DCH-LCR-Information CRITICALITY reject EXTENSION E-DCH-LCR-Information + PRESENCE optional }| + { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP + PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-ContinuousPacketConnectivity-DRX-InformationLCR CRITICALITY reject EXTENSION + ContinuousPacketConnectivity-DRX-InformationLCR PRESENCE optional }| + { ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION HS- + DSCH-Semi-PersistentScheduling-Information-LCR PRESENCE optional }| + { ID id-E-DCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION E-DCH- + Semi-PersistentScheduling-Information-LCR PRESENCE optional }| + { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION IdleIntervalInformation + PRESENCE optional }| + { ID id-UE-Selected-MBMS-Service-Information CRITICALITY ignore EXTENSION UE-Selected-MBMS- + Service-Information PRESENCE optional }| + { ID id-HSSCH-TPC-StepSize CRITICALITY ignore EXTENSION TDD-TPC-DownlinkStepSize + PRESENCE optional }| + { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH- + MeasurementOccasion-Information PRESENCE optional }| + { ID id-Multi-Carrier-EDCH-Setup CRITICALITY reject EXTENSION Multi-Carrier-EDCH-Info + PRESENCE optional }| + { ID id-MU-MIMO-InformationLCR CRITICALITY ignore EXTENSION MU-MIMO-InformationLCR + PRESENCE optional }| + { ID id-UE-Support-of-non-rectangular-resource-allocation CRITICALITY ignore EXTENSION UE- + Support-of-non-rectangular-resource-allocation PRESENCE optional }, + ... +} + +UL-CCTrCH-InformationList-RL-AdditionRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH- +InformationItem-RL-AdditionRqstTDD + +UL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + UL-DPCH-Information UL-DPCH-InformationList-RL-AdditionRqstTDD + OPTIONAL, -- Applicable to 3.84cps TDD only + iE-Extensions ProtocolExtensionContainer { { UL-CCTrCH- + InformationItem-RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD CRITICALITY notify EXTENSION UL-DPCH- + InformationItem-LCR-RL-AdditionRqstTDD PRESENCE optional }| -- Applicable to 1.28cps TDD + only + { ID id-TDD-TPC-UplinkStepSize-LCR-RL-AdditionRqstTDD CRITICALITY reject EXTENSION TDD-TPC- + UplinkStepSize-LCR PRESENCE optional }|-- Applicable to 1.28cps TDD only +} + +``` + +``` + + { ID id-UL-DPCH-InformationItem-768-RL-AdditionRqstTDD CRITICALITY notify EXTENSION UL-DPCH- +InformationItem-768-RL-AdditionRqstTDD PRESENCE optional }, -- Applicable to 7.68Mcps +TDD only + ... +} + +UL-DPCH-InformationList-RL-AdditionRqstTDD ::= ProtocolIE-Single-Container { { UL-DPCH- +InformationItemIE-RL-AdditionRqstTDD } } + +UL-DPCH-InformationItemIE-RL-AdditionRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationItem-RL-AdditionRqstTDD CRITICALITY notify TYPE UL-DPCH- +InformationItem-RL-AdditionRqstTDD PRESENCE optional } + -- For 3.84Mcps TDD only +} + +UL-DPCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information UL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-InformationItem- +RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-TimeslotLCR-Information UL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-InformationItem- +LCR-RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-InformationItem-768-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot768-Information UL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-InformationItem- +768-RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-CCTrCH-InformationList-RL-AdditionRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH- +InformationItem-RL-AdditionRqstTDD + +DL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + dL-DPCH-Information DL-DPCH-InformationList-RL-AdditionRqstTDD OPTIONAL, -- +Applicable to 3.84Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH-InformationItem-RL- +AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD CRITICALITY notify EXTENSION +DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD PRESENCE optional } | -- Applicable to +1.28Mcps TDD only + { ID id-CCTrCH-Initial-DL-Power-RL-AdditionRqstTDD CRITICALITY ignore EXTENSION +DL-Power PRESENCE optional } | + { ID id-TDD-TPC-DownlinkStepSize-RL-AdditionRqstTDD CRITICALITY reject EXTENSION +TDD-TPC-DownlinkStepSize PRESENCE optional } | +} + +``` + +``` + + { ID id-CCTrCH-Maximum-DL-Power-RL-AdditionRqstTDD CRITICALITY ignore EXTENSION +DL-Power PRESENCE optional }| + { ID id-CCTrCH-Minimum-DL-Power-RL-AdditionRqstTDD CRITICALITY ignore EXTENSION +DL-Power PRESENCE optional }| + { ID id-DL-DPCH-InformationItem-768-RL-AdditionRqstTDD CRITICALITY notify EXTENSION +DL-DPCH-InformationItem-768-RL-AdditionRqstTDD PRESENCE optional }, -- Applicable to +7.68Mcps TDD only + ... +} + +DL-DPCH-InformationList-RL-AdditionRqstTDD ::= ProtocolIE-Single-Container { DL-DPCH- +InformationItemIE-RL-AdditionRqstTDD } + +DL-DPCH-InformationItemIE-RL-AdditionRqstTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationItem-RL-AdditionRqstTDD CRITICALITY notify TYPE DL-DPCH- +InformationItem-RL-AdditionRqstTDD PRESENCE mandatory } +} + +DL-DPCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information DL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-InformationItem- +RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-TimeslotLCR-Information DL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-InformationItem- +LCR-RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-InformationItem-768-RL-AdditionRqstTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot768-Information DL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-InformationItem- +768-RL-AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RL-Information-RL-AdditionRqstTDD ::= SEQUENCE { + rL-ID RL-ID, + c-ID C-ID, + frameOffset FrameOffset, + diversityControlField DiversityControlField, + initial-DL-Transmission-Power DL-Power OPTIONAL, + maximumDL-Power DL-Power OPTIONAL, + minimumDL-Power DL-Power OPTIONAL, + dL-TimeSlotISCPInfo DL-TimeslotISCPInfo OPTIONAL, -- Applicable to +3.84Mcps TDD and 7.68Mcps TDD only + iE-Extensions ProtocolExtensionContainer { { RL-information-RL- +AdditionRqstTDD-ExtIEs } } OPTIONAL, + ... +} + +RL-information-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TimeslotISCP-InformationList-LCR-RL-AdditionRqstTDD CRITICALITY reject EXTENSION DL- +TimeslotISCPInfoLCR PRESENCE optional }| +} + +``` + +``` + + -- Applicable to 1.28Mcps TDD only + { ID id-RL-Specific-DCH-Info + Specific-DCH-Info PRESENCE optional }| + { ID id-DelayedActivation + DelayedActivation PRESENCE optional }| + { ID id-UL-Synchronisation-Parameters-LCR + Synchronisation-Parameters-LCR PRESENCE optional }| -- Mandatory for 1.28Mcps TDD, Not + Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-UARFCNforNt + PRESENCE optional }, + -- Mandatory for 1.28Mcps TDD when using multiple frequencies + ... + } + + -- ***** + -- + -- RADIO LINK ADDITION RESPONSE FDD + -- + -- ***** + + RadioLinkAdditionResponseFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkAdditionResponseFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionResponseFDD-Extensions}} + OPTIONAL, + ... + } + + RadioLinkAdditionResponseFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- + CommunicationContextID PRESENCE mandatory }| + { ID id-RL-InformationResponseList-RL-AdditionRspFDD CRITICALITY ignore TYPE RL- + InformationResponseList-RL-AdditionRspFDD PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE + CriticalityDiagnostics PRESENCE optional }, + ... + } + + RadioLinkAdditionResponseFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HS-DSCH-Serving-Cell-Change-Info-Response CRITICALITY ignore EXTENSION HS-DSCH- + Serving-Cell-Change-Info-Response PRESENCE optional }| + { ID id-E-DCH-Serving-Cell-Change-Info-Response CRITICALITY ignore EXTENSION E-DCH-Serving- + Cell-Change-Info-Response PRESENCE optional }| + { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs- + ResetIndicator PRESENCE optional }| + { ID id-Additional-HS-Cell-Change-Information-Response CRITICALITY ignore EXTENSION Additional-HS- + Cell-Change-Information-Response-List PRESENCE optional }| + { ID id-Additional-EDCH-Cell-Information-Response-RL-Add CRITICALITY ignore EXTENSION + Additional-EDCH-Cell-Information-Response-RL-Add-List PRESENCE optional }, + ... + } + + Additional-HS-Cell-Change-Information-Response-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF + Additional-HS-Cell-Change-Information-Response-ItemIEs + + Additional-HS-Cell-Change-Information-Response-ItemIEs ::=SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + hS-DSCH-Secondary-Serving-Cell-Change-Information-Response HS-DSCH-Secondary-Serving-Cell- + Change-Information-Response, + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Change- + Information-Response-ItemIEs-ExtIEs} } OPTIONAL, + ... + } + + Additional-HS-Cell-Change-Information-Response-ItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + RL-InformationResponseList-RL-AdditionRspFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE- + Single-Container {{ RL-InformationResponseItemIE-RL-AdditionRspFDD }} + + RL-InformationResponseItemIE-RL-AdditionRspFDD NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationResponseItem-RL-AdditionRspFDD CRITICALITY ignore TYPE RL- + InformationResponseItem-RL-AdditionRspFDD PRESENCE mandatory } + } + + RL-InformationResponseItem-RL-AdditionRspFDD ::= SEQUENCE { + rL-ID RL-ID, + rL-Set-ID RL-Set-ID, + } + +``` + +``` + + received-total-wide-band-power Received-total-wide-band-power-Value, + diversityIndication DiversityIndication-RL-AdditionRspFDD, + sSDT-SupportIndicator SSDT-SupportIndicator, + iE-Extensions ProtocolExtensionContainer { { RL-InformationResponseItem- +RL-AdditionRspFDD-ExtIEs} } OPTIONAL, + ... +} + +RL-InformationResponseItem-RL-AdditionRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL- +PowerBalancing-ActivationIndicator PRESENCE optional }| + { ID id-E-DCH-RL-Set-ID CRITICALITY ignore EXTENSION RL-Set-ID + PRESENCE optional }| + { ID id-E-DCH-FDD-DL-Control-Channel-Information CRITICALITY ignore EXTENSION E-DCH-FDD-DL- +Control-Channel-Information PRESENCE optional }| + { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH- +TimingAdjustment PRESENCE optional }| + { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationInfo PRESENCE optional }| + { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving- +RL-Preconfig-Info PRESENCE optional }, + ... +} + +DiversityIndication-RL-AdditionRspFDD ::= CHOICE { + combining Combining-RL-AdditionRspFDD, + non-combining Non-Combining-RL-AdditionRspFDD +} + +Combining-RL-AdditionRspFDD ::= SEQUENCE { + rL-ID RL-ID, + iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL- +AdditionRspFDD-ExtIEs} } OPTIONAL, + ... +} + +CombiningItem-RL-AdditionRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD- +Information-Response PRESENCE optional }, + ... +} + +Non-Combining-RL-AdditionRspFDD ::= SEQUENCE { + dCH-InformationResponse DCH-InformationResponse, + iE-Extensions ProtocolExtensionContainer { { Non-CombiningItem-RL- +AdditionRspFDD-ExtIEs} } OPTIONAL, + ... +} + +Non-CombiningItem-RL-AdditionRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD- +Information-Response PRESENCE optional }, + ... +} + +-- **************************************************************************** +-- +-- RADIO LINK ADDITION RESPONSE TDD +-- +-- **************************************************************************** + +RadioLinkAdditionResponseTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkAdditionResponseTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionResponseTDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkAdditionResponseTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- +CommunicationContextID PRESENCE mandatory }| + { ID id-RL-InformationResponse-RL-AdditionRspTDD CRITICALITY ignore TYPE RL- +InformationResponse-RL-AdditionRspTDD PRESENCE optional }| -- Mandatory for 3.84Mcps +TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE +CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +RadioLinkAdditionResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-RL-InformationResponse-LCR-RL-AdditionRspTDD CRITICALITY ignore EXTENSION RL- +InformationResponse-LCR-RL-AdditionRspTDD PRESENCE optional}| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH- +TDD-Information-Response PRESENCE optional}| + { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH- +Information-Response PRESENCE optional}| + { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore +EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR PRESENCE optional}| + { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore +EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional}| + { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore +EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional}| + { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier- +EDCH-Information-Response PRESENCE optional}| + { ID id-MU-MIMO-Information-Response CRITICALITY reject EXTENSION MU-MIMO- +Information-Response PRESENCE optional}| + { ID id-Non-rectangular-resource-allocation-indicator CRITICALITY reject EXTENSION Non- +rectangular-resource-allocation-indicator PRESENCE optional}| + { ID id-Non-rectangular-resource-timeslot-set CRITICALITY reject EXTENSION Non- +rectangular-resource-timeslot-set PRESENCE optional}, + ... +} + +RL-InformationResponse-RL-AdditionRspTDD ::= SEQUENCE { + rL-ID RL-ID, + uL-TimeSlot-ISCPI-Info UL-TimeSlot-ISCPI-Info, + uL-PhysCH-SF-Variation UL-PhysCH-SF-Variation, + dCH-Information DCH-Information-RL-AdditionRspTDD + OPTIONAL, + dSCH-InformationResponseList DSCH-InformationResponseList-RL-AdditionRspTDD + OPTIONAL, + uSCH-InformationResponseList USCH-InformationResponseList-RL-AdditionRspTDD + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RL- +InformationResponse-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, + ... +} + +RL-InformationResponse-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DCH-Information-RL-AdditionRspTDD ::= SEQUENCE { + diversityIndication DiversityIndication-RL-AdditionRspTDD, + iE-Extensions ProtocolExtensionContainer { { DCH-Information-RL- +AdditionRspTDD-ExtIEs} } OPTIONAL, + ... +} + +DCH-Information-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DiversityIndication-RL-AdditionRspTDD ::= CHOICE { + combining Combining-RL-AdditionRspTDD, -- Indicates whether +the old Transport Bearer shall be reused or not + non-Combining Non-Combining-RL-AdditionRspTDD +} + +Combining-RL-AdditionRspTDD ::= SEQUENCE { + rL-ID RL-ID, -- Reference RL + iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL- +AdditionRspTDD-ExtIEs} } OPTIONAL, + ... +} + +CombiningItem-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Non-Combining-RL-AdditionRspTDD ::= SEQUENCE { + dCH-InformationResponse DCH-InformationResponse, + iE-Extensions ProtocolExtensionContainer { { Non-CombiningItem-RL- +AdditionRspTDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +} + +Non-CombiningItem-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DSCH-InformationResponseList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{ DSCH- +InformationResponseListIEs-RL-AdditionRspTDD }} + +DSCH-InformationResponseListIEs-RL-AdditionRspTDD NBAP-PROTOCOL-IES ::= { + { ID id-DSCH-InformationResponse CRITICALITY ignore TYPE DSCH-InformationResponse + PRESENCE mandatory } +} + +USCH-InformationResponseList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{ USCH- +InformationResponseListIEs-RL-AdditionRspTDD }} + +USCH-InformationResponseListIEs-RL-AdditionRspTDD NBAP-PROTOCOL-IES ::= { + { ID id-USCH-InformationResponse CRITICALITY ignore TYPE USCH-InformationResponse + PRESENCE mandatory } +} + +RL-InformationResponse-LCR-RL-AdditionRspTDD ::= SEQUENCE { + rL-ID RL-ID, + uL-TimeSlot-ISCP-InfoLCR UL-TimeSlot-ISCP-LCR-Info, + uL-PhysCH-SF-Variation UL-PhysCH-SF-Variation, + dCH-Information DCH-Information-RL-AdditionRspTDD OPTIONAL, + dSCH-InformationResponseList + DSCH-InformationResponseList-RL-AdditionRspTDD + OPTIONAL, + uSCH-InformationResponseList + USCH-InformationResponseList-RL-AdditionRspTDD + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RL- +InformationResponse-LCR-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, + ... +} + +RL-InformationResponse-LCR-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- RADIO LINK ADDITION FAILURE FDD +-- +-- ***** + +RadioLinkAdditionFailureFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkAdditionFailureFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionFailureFDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkAdditionFailureFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- +CommunicationContextID PRESENCE mandatory } | + { ID id-CauseLevel-RL-AdditionFailureFDD CRITICALITY ignore TYPE CauseLevel-RL- +AdditionFailureFDD PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE +CriticalityDiagnostics PRESENCE optional }, + ... +} + +RadioLinkAdditionFailureFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-HS-DSCH-Serving-Cell-Change-Info-Response CRITICALITY ignore EXTENSION HS-DSCH- +Serving-Cell-Change-Info-Response PRESENCE optional } | + { ID id-E-DCH-Serving-Cell-Change-Info-Response CRITICALITY ignore EXTENSION E-DCH-Serving- +Cell-Change-Info-Response PRESENCE optional } | + { ID id-Additional-HS-Cell-Change-Information-Response CRITICALITY ignore EXTENSION Additional-HS- +Cell-Change-Information-Response-List PRESENCE optional } | + { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs- +ResetIndicator PRESENCE optional } | + { ID id-Additional-EDCH-Cell-Information-Response-RL-Add CRITICALITY ignore EXTENSION +Additional-EDCH-Cell-Information-Response-RL-Add-List PRESENCE optional }, + ... +} + +CauseLevel-RL-AdditionFailureFDD ::= CHOICE { + +``` + +``` + + generalCause GeneralCauseList-RL-AdditionFailureFDD, + rLSpecificCause RLSpecificCauseList-RL-AdditionFailureFDD, + ... + } + + GeneralCauseList-RL-AdditionFailureFDD ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL- + AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... + } + + GeneralCauseItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + RLSpecificCauseList-RL-AdditionFailureFDD ::= SEQUENCE { + unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD Unsuccessful-RL- + InformationRespList-RL-AdditionFailureFDD, + successful-RL-InformationRespList-RL-AdditionFailureFDD Successful-RL- + InformationRespList-RL-AdditionFailureFDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RLSpecificCauseItem- + RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... + } + + RLSpecificCauseItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF + ProtocolIE-Single-Container { { Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureFDD } } + + Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureFDD NBAP-PROTOCOL-IES ::= { + { ID id-Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD CRITICALITY ignore TYPE + Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD PRESENCE mandatory } + } + + Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD ::= SEQUENCE { + rL-ID rL-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { Unsuccessful-RL-InformationRespItem- + RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... + } + + Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Successful-RL-InformationRespList-RL-AdditionFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-2)) OF + ProtocolIE-Single-Container { { Successful-RL-InformationRespItemIE-RL-AdditionFailureFDD } } + + Successful-RL-InformationRespItemIE-RL-AdditionFailureFDD NBAP-PROTOCOL-IES ::= { + { ID id-Successful-RL-InformationRespItem-RL-AdditionFailureFDD CRITICALITY ignore TYPE + Successful-RL-InformationRespItem-RL-AdditionFailureFDD PRESENCE mandatory } + } + + Successful-RL-InformationRespItem-RL-AdditionFailureFDD ::= SEQUENCE { + rL-ID rL-ID, + rL-Set-ID rL-Set-ID, + received-total-wide-band-power Received-total-wide-band-power-Value, + diversityIndication DiversityIndication-RL-AdditionFailureFDD, + sSDT-SupportIndicator SSDT-SupportIndicator, + iE-Extensions ProtocolExtensionContainer { { Successful-RL- + InformationRespItem-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... + } + + Successful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL- + PowerBalancing-ActivationIndicator PRESENCE optional } | + { ID id-E-DCH-RL-Set-ID CRITICALITY ignore EXTENSION rL-Set-ID + PRESENCE optional } | + { ID id-E-DCH-FDD-DL-Control-Channel-Information CRITICALITY ignore EXTENSION E-DCH-FDD-DL- + Control-Channel-Information PRESENCE optional } | + { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH- + TimingAdjustment PRESENCE optional } | + } + +``` + +``` + + { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationInfo PRESENCE optional }| + { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving- +RL-Preconfig-Info PRESENCE optional }, + ... +} + +DiversityIndication-RL-AdditionFailureFDD ::= CHOICE { + combining Combining-RL-AdditionFailureFDD, + non-Combining Non-Combining-RL-AdditionFailureFDD +} + +Combining-RL-AdditionFailureFDD ::= SEQUENCE { + rL-ID RL-ID, + iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL- +AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +CombiningItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD- +Information-Response PRESENCE optional }, + ... +} + +Non-Combining-RL-AdditionFailureFDD ::= SEQUENCE { + dCH-InformationResponse DCH-InformationResponse, + iE-Extensions ProtocolExtensionContainer { { Non-CombiningItem-RL- +AdditionFailureFDD-ExtIEs} } OPTIONAL, + ... +} + +Non-CombiningItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD- +Information-Response PRESENCE optional }, + ... +} + +-- ***** +-- +-- RADIO LINK ADDITION FAILURE TDD +-- +-- ***** + +RadioLinkAdditionFailureTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkAdditionFailureTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionFailureTDD-Extensions}} + OPTIONAL, + ... +} + +RadioLinkAdditionFailureTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- +CommunicationContextID PRESENCE mandatory }| + { ID id-CauseLevel-RL-AdditionFailureTDD CRITICALITY ignore TYPE CauseLevel-RL- +AdditionFailureTDD PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE +CriticalityDiagnostics PRESENCE optional }, + ... +} + +RadioLinkAdditionFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CauseLevel-RL-AdditionFailureTDD ::= CHOICE { + generalCause GeneralCauseList-RL-AdditionFailureTDD, + rLSpecificCause RLSpecificCauseList-RL-AdditionFailureTDD, + ... +} + +GeneralCauseList-RL-AdditionFailureTDD ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL- +AdditionFailureTDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +GeneralCauseItem-RL-AdditionFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLSpecificCauseList-RL-AdditionFailureTDD ::= SEQUENCE { + unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD Unsuccessful-RL-InformationRespItem- + RL-AdditionFailureTDD, + iE-Extensions ProtocolExtensionContainer { { + RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs} } OPTIONAL, + ... +} + +RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD ::= ProtocolIE-Single-Container { + {Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureTDD} } + +Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureTDD NBAP-PROTOCOL-IES ::= { + { ID id-Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD CRITICALITY ignore TYPE + Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD PRESENCE mandatory } +} + +Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD ::= SEQUENCE { + rL-ID rL-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { Unsuccessful-RL-InformationResp- + RL-AdditionFailureTDD-ExtIEs} } OPTIONAL, + ... +} + +Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION PREPARE FDD +-- +-- ***** + +RadioLinkReconfigurationPrepareFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationPrepareFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationPrepareFDD- + Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationPrepareFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY reject TYPE NodeB- + CommunicationContextID PRESENCE mandatory }| + { ID id-UL-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject TYPE UL-DPCH- + Information-RL-ReconfPrepFDD PRESENCE optional }| + { ID id-DL-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject TYPE DL-DPCH- + Information-RL-ReconfPrepFDD PRESENCE optional }| + { ID id-FDD-DCHs-to-Modify CRITICALITY reject TYPE FDD-DCHs-to- + Modify PRESENCE optional }| + { ID id-DCHs-to-Add-FDD CRITICALITY reject TYPE DCH-FDD- + Information PRESENCE optional }| + { ID id-DCH-DeleteList-RL-ReconfPrepFDD CRITICALITY reject TYPE DCH-DeleteList- + RL-ReconfPrepFDD PRESENCE optional }| + { ID id-RL-InformationList-RL-ReconfPrepFDD CRITICALITY reject TYPE RL- + InformationList-RL-ReconfPrepFDD PRESENCE optional }| + { ID id-Transmission-Gap-Pattern-Sequence-Information CRITICALITY reject TYPE Transmission- + Gap-Pattern-Sequence-Information PRESENCE optional }, + ... +} + +RadioLinkReconfigurationPrepareFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-SignallingBearerRequestIndicator CRITICALITY reject EXTENSION + SignallingBearerRequestIndicator PRESENCE optional }| + { ID id-HSDSCH-FDD-Information CRITICALITY reject EXTENSION HSDSCH-FDD- + Information PRESENCE optional }| + { ID id-HSDSCH-Information-to-Modify CRITICALITY reject EXTENSION HSDSCH- + Information-to-Modify PRESENCE optional }| + { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject EXTENSION HSDSCH-MACdFlows- + Information PRESENCE optional }| +} + +``` + +``` + + { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION HSDSCH-MACdFlows- +to-Delete PRESENCE optional}| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional}| + -- The IE shall be present if HS-PDSCH RL ID IE is present. + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional}| + { ID id-E-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject EXTENSION E-DPCH- +Information-RL-ReconfPrepFDD PRESENCE optional}| + { ID id-E-DCH-FDD-Information CRITICALITY reject EXTENSION E-DCH-FDD- +Information PRESENCE optional}| + { ID id-E-DCH-FDD-Information-to-Modify CRITICALITY reject EXTENSION E-DCH-FDD- +Information-to-Modify PRESENCE optional}| + { ID id-E-DCH-MACdFlows-to-Add CRITICALITY reject EXTENSION E-DCH-MACdFlows- +Information PRESENCE optional}| + { ID id-E-DCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION E-DCH-MACdFlows- +to-Delete PRESENCE optional}| + { ID id-Serving-E-DCH-RL-ID CRITICALITY reject EXTENSION Serving-E-DCH-RL- +ID PRESENCE optional}| + { ID id-F-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject EXTENSION F-DPCH- +Information-RL-ReconfPrepFDD PRESENCE optional}| + { ID id-Fast-Reconfiguration-Mode CRITICALITY ignore EXTENSION Fast- +Reconfiguration-Mode PRESENCE optional}| + { ID id-CPC-Information CRITICALITY reject EXTENSION CPC-Information + PRESENCE optional}| + { ID id-Additional-HS-Cell-Information-RL-Reconf-Prep CRITICALITY reject EXTENSION +Additional-HS-Cell-Information-RL-Reconf-Prep PRESENCE optional}| + { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE- +AggregateMaximumBitRate PRESENCE optional}| + { ID id-Additional-EDCH-Cell-Information-RL-Reconf-Prep CRITICALITY reject EXTENSION +Additional-EDCH-Cell-Information-RL-Reconf-Prep PRESENCE optional}| + { ID id-UL-CLTD-Information-Reconf CRITICALITY reject EXTENSION UL-CLTD- +Information-Reconf PRESENCE optional}| + { ID id-E-DCH-Decoupling-Indication CRITICALITY reject EXTENSION E-DCH-Decoupling- +Indication PRESENCE optional}| + { ID id-DCH-ENH-Information-Reconf CRITICALITY reject EXTENSION DCH-ENH- +Information-Reconf PRESENCE optional}| + { ID id-Radio-Links-without-DPCH-FDPCH-Indication CRITICALITY reject EXTENSION Radio-Links- +without-DPCH-FDPCH-Indication PRESENCE optional}| + { ID id-UL-DPCCH2-Information-Reconf CRITICALITY reject EXTENSION UL-DPCCH2- +Information-Reconf PRESENCE optional}| + { ID id-Downlink-TPC-enhancements-Reconf CRITICALITY reject EXTENSION Downlink-TPC- +enhancements-Reconf PRESENCE optional}| + { ID id-Improved-Synchronized-Indicator CRITICALITY ignore EXTENSION Improved- +Synchronized-Indicator PRESENCE optional}, + ... + } + + Additional-HS-Cell-Information-RL-Reconf-Prep ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF + Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs + + Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs ::=SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + c-ID C-ID + OPTIONAL, + hS-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information + OPTIONAL, + hS-DSCH-Secondary-Serving-Information-To-Modify HS-DSCH-Secondary-Serving-Information-To-Modify + OPTIONAL, + hS-HS-DSCH-Secondary-Serving-Remove HS-DSCH-Secondary-Serving-Remove + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information- +RL-Reconf-Prep-ItemIEs-ExtIEs} } OPTIONAL, + ... + } + + Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + Additional-EDCH-Cell-Information-RL-Reconf-Prep ::=SEQUENCE{ + setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency + Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency, + iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information- +RL-Reconf-Prep-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +Additional-EDCH-Cell-Information-RL-Reconf-Prep-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { + ul-ScramblingCode UL-ScramblingCode OPTIONAL, + ul-SIR-Target UL-SIR OPTIONAL, + minUL-ChannelisationCodeLength MinUL-ChannelisationCodeLength OPTIONAL, + maxNrOfUL-DPDCHs MaxNrOfUL-DPDCHs OPTIONAL, + -- This IE shall be present if minUL-ChannelisationCodeLength IE is set to 4 + ul-PunctureLimit PunctureLimit OPTIONAL, + tFCS TFCS OPTIONAL, + ul-DPCH-SlotFormat UL-DPCH-SlotFormat OPTIONAL, + diversityMode DiversityMode OPTIONAL, + not-Used-sSDT-CellIDLength NULL OPTIONAL, + not-Used-s-FieldLength NULL OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH- + Information-RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +UL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPDCH-Indicator-For-E-DCH-Operation CRITICALITY reject EXTENSION UL-DPDCH- + Indicator-For-E-DCH-Operation PRESENCE optional }, + ... +} + +DL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { + tFCS TFCS OPTIONAL, + dl-DPCH-SlotFormat DL-DPCH-SlotFormat OPTIONAL, + tFCI-SignallingMode TFCI-SignallingMode OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + -- This IE shall be present if the DL DPCH Slot Format IE is set to any of the values from 12 to +16 + multiplexingPosition MultiplexingPosition OPTIONAL, + not-Used-pDSCH-CodeMapping NULL OPTIONAL, + not-Used-pDSCH-RL-ID NULL OPTIONAL, + limitedPowerIncrease LimitedPowerIncrease OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- + Information-RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-Power-Information-RL-ReconfPrepFDD CRITICALITY reject EXTENSION DL-DPCH-Power- + Information-RL-ReconfPrepFDD PRESENCE optional }, + ... +} + +DL-DPCH-Power-Information-RL-ReconfPrepFDD ::= SEQUENCE { + powerOffsetInformation PowerOffsetInformation-RL-ReconfPrepFDD, + fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, + innerLoopDLPCStatus InnerLoopDLPCStatus, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-Power- + Information-RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-Power-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PowerOffsetInformation-RL-ReconfPrepFDD ::= SEQUENCE { + pO1-ForTFCI-Bits PowerOffset, + pO2-ForTPC-Bits PowerOffset, + pO3-ForPilotBits PowerOffset, + iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation- + RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +PowerOffsetInformation-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` +DCH-DeleteList-RL-ReconfPrepFDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfPrepFDD +``` + +``` +DCH-DeleteItem-RL-ReconfPrepFDD ::= SEQUENCE { + dCH-ID DCH-ID, + iE-Extensions ProtocolExtensionContainer { { DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RL-InformationList-RL-ReconfPrepFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { { RL-InformationItemIE-RL-ReconfPrepFDD } } +``` + +``` +RL-InformationItemIE-RL-ReconfPrepFDD NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationItem-RL-ReconfPrepFDD CRITICALITY reject TYPE RL-InformationItem-RL-ReconfPrepFDD PRESENCE mandatory} +} +``` + +``` +RL-InformationItem-RL-ReconfPrepFDD ::= SEQUENCE { + rL-ID RL-ID, + dl-CodeInformation FDD-DL-CodeInformation + OPTIONAL, + maxDL-Power DL-Power + OPTIONAL, + minDL-Power DL-Power + OPTIONAL, + not-Used-sSDT-Indication NULL + OPTIONAL, + not-Used-sSDT-Cell-Identity NULL + OPTIONAL, + transmitDiversityIndicator TransmitDiversityIndicator + OPTIONAL, + -- This IE shall be present if Diversity Mode IE is present in UL DPCH Information IE and it is not set to "none" + iE-Extensions ProtocolExtensionContainer { { RL-InformationItem-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RL-InformationItem-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DLReferencePower CRITICALITY ignore EXTENSION DL-Power PRESENCE optional}| + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info PRESENCE optional}| + { ID id-DL-DPCH-TimingAdjustment CRITICALITY reject EXTENSION DL-DPCH-TimingAdjustment PRESENCE optional}| + { ID id-Primary-CPICH-Usage-for-Channel-Estimation CRITICALITY ignore EXTENSION Primary-CPICH-Usage-for-Channel-Estimation PRESENCE optional}| + { ID id-Secondary-CPICH-Information-Change CRITICALITY ignore EXTENSION Secondary-CPICH-Information-Change PRESENCE optional}| + { ID id-E-DCH-RL-Indication CRITICALITY reject EXTENSION E-DCH-RL-Indication PRESENCE optional}| + { ID id-RL-Specific-E-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-E-DCH-Info PRESENCE optional}| + { ID id-F-DPCH-SlotFormat CRITICALITY reject EXTENSION F-DPCH-SlotFormat PRESENCE optional}| + { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore EXTENSION HSDSCH-PreconfigurationSetup PRESENCE optional}| + { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Setup PRESENCE optional}| + { ID id-Non-Serving-RL-Preconfig-Removal CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Setup PRESENCE optional}| + { ID id-FTPICH-Information-Reconf CRITICALITY ignore EXTENSION FTPICH-Information-Reconf PRESENCE optional}| + { ID id-TPC-slot-position CRITICALITY ignore EXTENSION TPC-slot-position PRESENCE optional}, + ... +} +``` + +``` +E-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { + maxSet-E-DPDCHs Max-Set-E-DPDCHs + OPTIONAL, + ul-PunctureLimit PunctureLimit + OPTIONAL, +``` + +``` + + e-TFCS-Information + OPTIONAL, + e-TTI + OPTIONAL, + e-DPCCH-PO + OPTIONAL, + e-RGCH-2-IndexStepThreshold + OPTIONAL, + e-RGCH-3-IndexStepThreshold + OPTIONAL, + hARQ-Info-for-E-DCH + OPTIONAL, + hSDSCH-Configured-Indicator + OPTIONAL, + iE-Extensions + ProtocolExtensionContainer { { E-DPCH-Information- +RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +E-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MinimumReducedE-DPCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE- +DPDCH-GainFactor PRESENCE optional }, + ... +} + +F-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { + powerOffsetInformation PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD, + fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, + limitedPowerIncrease LimitedPowerIncrease, + innerLoopDLPCStatus InnerLoopDLPCStatus, + iE-Extensions ProtocolExtensionContainer { { F-DPCH-Information-RL- +ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +F-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD ::= SEQUENCE { + pO2-ForTPC-Bits PowerOffset, + -- This IE shall be ignored by Node B + iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation-F- +DPCH-RL-ReconfPrepFDD-ExtIEs } } OPTIONAL, + ... +} + +PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION PREPARE TDD +-- +-- ***** + +RadioLinkReconfigurationPrepareTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationPrepareTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationPrepareTDD- +Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationPrepareTDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY reject TYPE NodeB- +CommunicationContextID PRESENCE mandatory }| + { ID id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD CRITICALITY reject TYPE UL-CCTrCH- +InformationAddList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE UL-CCTrCH- +InformationModifyList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE UL-CCTrCH- +InformationDeleteList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD CRITICALITY reject TYPE DL-CCTrCH- +InformationAddList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE DL-CCTrCH- +InformationModifyList-RL-ReconfPrepTDD PRESENCE optional }| +} + +``` + +``` + + { ID id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE DL-CCTrCH- +InformationDeleteList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-TDD-DCHs-to-Modify CRITICALITY reject TYPE TDD-DCHs- +to-Modify PRESENCE optional }| + { ID id-DCHs-to-Add-TDD CRITICALITY reject TYPE DCH-TDD- +Information PRESENCE optional }| + { ID id-DCH-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE DCH- +DeleteList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-DSCH-Information-ModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE DSCH- +Information-ModifyList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-DSCHs-to-Add-TDD CRITICALITY reject TYPE DSCH-TDD- +Information PRESENCE optional }| + { ID id-DSCH-Information-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE DSCH- +Information-DeleteList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-USCH-Information-ModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE USCH- +Information-ModifyList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-USCH-Information-Add CRITICALITY reject TYPE USCH- +Information PRESENCE optional }| + { ID id-USCH-Information-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE USCH- +Information-DeleteList-RL-ReconfPrepTDD PRESENCE optional }| + { ID id-RL-Information-RL-ReconfPrepTDD CRITICALITY reject TYPE RL- +Information-RL-ReconfPrepTDD PRESENCE optional }, +-- This RL Information is the for the 1st RL IE repetition +... +} + +``` + +``` + +RadioLinkReconfigurationPrepareTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-SignallingBearerRequestIndicator CRITICALITY reject EXTENSION +SignallingBearerRequestIndicator PRESENCE optional }| + { ID id-HSDSCH-TDD-Information CRITICALITY reject EXTENSION HSDSCH-TDD- +Information PRESENCE optional }| + { ID id-HSDSCH-Information-to-Modify CRITICALITY reject EXTENSION HSDSCH- +Information-to-Modify PRESENCE optional }| + { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject EXTENSION HSDSCH-MACdFlows- +Information PRESENCE optional }| + { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION HSDSCH-MACdFlows- +to-Delete PRESENCE optional }| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional }| +-- The IE shall be present if HS-PDSCH RL ID IE is present. + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-PDSCH-RL-ID CRITICALITY ignore EXTENSION RL-ID + PRESENCE optional }| + { ID id-multiple-RL-Information-RL-ReconfPrepTDD CRITICALITY reject EXTENSION MultipleRL- +Information-RL-ReconfPrepTDD PRESENCE optional }| +-- This RL Information is the for the 2nd and beyond repetition of RL information, + { ID id-E-DCH-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-Information- +Reconfig PRESENCE optional }| + { ID id-E-DCH-Serving-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DCH-768-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-768- +Information-Reconfig PRESENCE optional }| + { ID id-E-DCH-LCR-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-LCR- +Information-Reconfig PRESENCE optional }| + { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP + PRESENCE optional }| +-- Applicable to 1.28Mcps TDD only + { ID id-CPC-InformationLCR CRITICALITY reject EXTENSION CPC-InformationLCR + PRESENCE optional }| + { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION +IdleIntervalInformation PRESENCE optional }| + { ID id-UE-Selected-MBMS-Service-Information CRITICALITY ignore EXTENSION UE-Selected-MBMS- +Service-Information PRESENCE optional }| + { ID id-HSSCH-TPC-StepSize CRITICALITY ignore EXTENSION TDD-TPC- +DownlinkStepSize PRESENCE optional }| + { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH- +MeasurementOccasion-Information PRESENCE optional }| + { ID id-HSDSCH-RNTI-For-FACH CRITICALITY ignore EXTENSION HSDSCH-RNTI + PRESENCE optional }| + { ID id-Multi-Carrier-EDCH-Reconfigure CRITICALITY reject EXTENSION Multi-Carrier- +EDCH-Reconfigure PRESENCE optional }| + { ID id-MU-MIMO-InformationLCR CRITICALITY ignore EXTENSION MU-MIMO- +InformationLCR PRESENCE optional }| + { ID id-MU-MIMO-Information-To-ReconfigureLCR CRITICALITY ignore EXTENSION MU-MIMO- +Information-To-ReconfigureLCR PRESENCE optional }| + { ID id-UE-Support-of-non-rectangular-resource-allocation CRITICALITY ignore EXTENSION UE- +Support-of-non-rectangular-resource-allocation PRESENCE optional }, + +``` + +``` + + ... + } + + UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH- + InformationAddItem-RL-ReconfPrepTDD + + UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + tFCS TFCS, + tFCI-Coding TFCI-Coding, + punctureLimit PunctureLimit, + ul-DPCH-InformationList UL-DPCH-InformationAddList-RL-ReconfPrepTDD + OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD + iE-Extensions ProtocolExtensionContainer { { UL-CCTrCH- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfPrepTDD CRITICALITY reject EXTENSION UL- + DPCH-LCR-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR + PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + -- This Information is the for the first RL repetition, SIR Target information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION TDD-TPC-UplinkStepSize-LCR PRESENCE optional }| + -- This Information is the for the first RL repetition, TPCinformation for RL repetitions 2 and on, + should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + { ID id-RL-ID CRITICALITY ignore EXTENSION RL-ID + PRESENCE optional }| + -- This is the RL ID for the first RL repetition + { ID id-multipleRL-ul-DPCH-InformationList CRITICALITY reject EXTENSION + MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }| + -- This Information is the for the 2nd and beyond RL repetition, + { ID id-UL-DPCH-768-InformationAddItemIE-RL-ReconfPrepTDD CRITICALITY reject EXTENSION UL- + DPCH-768-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }, -- Applicable to + 7.68Mcps TDD only, first radio link + ... + } + + UL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { UL-DPCH- + InformationAddListIEs-RL-ReconfPrepTDD } } + + UL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE UL-DPCH- + InformationAddItem-RL-ReconfPrepTDD PRESENCE mandatory } + } + + UL-DPCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information UL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + UL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + UL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-InformationLCR UL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-LCR- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +} + +UL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF +MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD +--Includes the 2nd through the max number of radio link repetitions. + +MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD ::= SEQUENCE { + ul-DPCH-InformationList UL-DPCH-InformationAddList-RL-ReconfPrepTDD + OPTIONAL, + ul-DPCH-InformationListLCR UL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD + OPTIONAL, + ul-sir-target UL-SIR + OPTIONAL, + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + tdd-TPC-UplinkStepSize-LCR TDD-TPC-UplinkStepSize-LCR + OPTIONAL, + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. + rL-ID RL-ID + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MultipleRL-UL-DPCH- +InformationAddListIE-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-768-InformationAddListIE-RL-ReconfPrepTDD CRITICALITY reject EXTENSION UL- +DPCH-768-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }, + ... +} + +UL-DPCH-768-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + ul-Timeslot-Information768 UL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-768- +InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL- +CCTrCH-InformationModifyItem-RL-ReconfPrepTDD + +UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + CCTrCH-ID CCTrCH-ID, + tFCS tFCS + OPTIONAL, + tFCI-Coding tFCI-Coding + OPTIONAL, + punctureLimit PunctureLimit + OPTIONAL, + ul-DPCH-InformationAddList UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD + OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + ul-DPCH-InformationModifyList UL-DPCH-InformationModify-ModifyList-RL- + ReconfPrepTDD OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + ul-DPCH-InformationDeleteList UL-DPCH-InformationModify-DeleteList-RL- + ReconfPrepTDD OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + iE-Extensions ProtocolExtensionContainer { { UL-CCTrCH- + InformationModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + { ID id-UL-DPCH-LCR-InformationModify-AddList CRITICALITY reject EXTENSION UL-DPCH- + LCR-InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }| -- Applicable to + 1.28Mcps TDD only + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR PRESENCE + optional }| + -- Applicable to 1.28Mcps TDD only. + -- This Information is the for the first RL repetition, SIR Target information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION TDD-TPC-UplinkStepSize-LCR PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + -- This Information is the for the first RL repetition, Step Size information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-RL-ID CRITICALITY ignore EXTENSION RL- + ID PRESENCE optional }| + -- This is the RL ID for the first RL repetition + { ID id-multipleRL-ul-DPCH-InformationModifyList CRITICALITY reject EXTENSION + MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD PRESENCE optional }| + -- This DPCH Information is the for the 2nd and beyond RL repetition, + { ID id-UL-DPCH-768-InformationModify-AddItem CRITICALITY reject EXTENSION UL-DPCH- + 768-InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }, -- Applicable to + 7.68Mcps TDD only + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD + ... + } + + UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { UL-DPCH- + InformationModify-AddListIEs-RL-ReconfPrepTDD } } + + UL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE UL- + DPCH-InformationModify-AddItem-RL-ReconfPrepTDD PRESENCE mandatory } + } + + UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information UL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH- + InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + UL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { UL-DPCH- + InformationModify-ModifyListIEs-RL-ReconfPrepTDD } } + + UL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE + UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD PRESENCE mandatory } + } + + UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod OPTIONAL, + repetitionLength RepetitionLength OPTIONAL, + tdd-DPCHOffset TDD-DPCHOffset OPTIONAL, + uL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD UL-Timeslot- + InformationModify-ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-TimeslotLCR-Information-RL-ReconfPrepTDD CRITICALITY reject EXTENSION UL- + TimeslotLCR-InformationModify-ModifyList-RL-ReconfPrepTDD PRESENCE optional }| -- + Applicable to 1.28Mcps TDD only + { ID id-UL-Timeslot768-Information-RL-ReconfPrepTDD CRITICALITY reject EXTENSION UL- + Timeslot768-InformationModify-ModifyList-RL-ReconfPrepTDD PRESENCE optional }, -- + Applicable to 7.68Mcps TDD only + ... + } + +``` + +``` + +} + +UL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF +UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD -- Applicable to 3.84Mcps TDD only + +UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD UL-Code-InformationModify- + ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Timeslot- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF UL- +Code-InformationModify-ModifyItem-RL-ReconfPrepTDD + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID DPCH-ID, + tdd-ChannelisationCode TDD-ChannelisationCode OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Code- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-TimeslotLCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE +(1..maxNrOfULTSLCRs)) OF UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD -- +Applicable to 1.28Mcps TDD only + +UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDDLCR UL-Code- + InformationModify-ModifyList-RL-ReconfPrepTDDLCR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Timeslot-LCR- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-PLCCH-Information-RL-ReconfPrepTDDLCR CRITICALITY reject EXTENSION + PLCCHinformation PRESENCE optional }, + ... +} + +UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDDLCR ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) OF +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR ::= SEQUENCE { + dPCH-ID DPCH-ID, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Code- + InformationModify-ModifyItem-RL-ReconfPrepTDDLCR-ExtIEs} } OPTIONAL, + ... +} + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD CRITICALITY reject EXTENSION TDD- + UL-DPCH-TimeSlotFormat-LCR PRESENCE optional }, + ... +} + +UL-Timeslot768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) +OF UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD -- Applicable to 7.68Mcps TDD +only + +``` + +``` + +UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlot TimeSlot, + midambleShiftAndBurstType768 MidambleShiftAndBurstType768 OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD768 UL-Code- + InformationModify-ModifyList-RL-ReconfPrepTDD768 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Timeslot-768- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD768 ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768 + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768 ::= SEQUENCE { + dPCH-ID DPCH-ID, + tdd-ChannelisationCode768 TDD-ChannelisationCode768 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-Code- + InformationModify-ModifyItem-RL-ReconfPrepTDD768-ExtIEs} } OPTIONAL, + ... +} + +UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ UL-DPCH- +InformationModify-DeleteListIEs-RL-ReconfPrepTDD }} + +UL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE + UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD PRESENCE mandatory } +} + +UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF UL- +DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD + +UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID DPCH-ID, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-InformationModify- + DeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-InformationLCR UL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-LCR- + InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF +MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD +--Includes the 2nd through the max number of radio link information repetitions. + +MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD ::= SEQUENCE { + ul-DPCH-InformationAddList UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD + OPTIONAL, + ul-DPCH-InformationModifyList UL-DPCH-InformationModify-ModifyList-RL- + ReconfPrepTDD OPTIONAL, + ul-DPCH-InformationDeleteList UL-DPCH-InformationModify-DeleteList-RL- + ReconfPrepTDD OPTIONAL, +} + +``` + +``` + + ul-DPCH-InformationAddListLCR UL-DPCH-LCR-InformationModify-AddList-RL- +ReconfPrepTDD OPTIONAL, + ul-sir-target UL-SIR + OPTIONAL, + tdd-TPC-UplinkStepSize-LCR TDD-TPC-UplinkStepSize-LCR + OPTIONAL, + rL-ID RL-ID + OPTIONAL, + -- This DPCH Information is the for the 2nd and beyond RL repetitions, + iE-Extensions ProtocolExtensionContainer { { MultipleRL-UL-DPCH- +InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-768-InformationModify-AddList CRITICALITY reject EXTENSION UL-DPCH-768- +InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }, -- Applicable to 7.68Mcps +TDD only + ... +} + +UL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information768 UL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH-768- +InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL- +CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD + +UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + iE-Extensions ProtocolExtensionContainer { { UL-CCTrCH- +InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH- +InformationAddItem-RL-ReconfPrepTDD + +DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE { + cCTrCH-ID CCTrCH-ID, + tFCS TFCS, + tFCI-Coding TFCI-Coding, + punctureLimit PunctureLimit, + cCTrCH-TPCList CCTrCH-TPCAddList-RL-ReconfPrepTDD + OPTIONAL, + dl-DPCH-InformationList DL-DPCH-InformationAddList-RL-ReconfPrepTDD + OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD + iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH- +InformationAddItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD CRITICALITY reject +EXTENSION DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }| -- +Applicable to 1.28Mcps TDD only + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-CCTrCH-Initial-DL-Power-RL-ReconfPrepTDD CRITICALITY ignore +EXTENSION DL-Power PRESENCE optional }| + -- This DL Power information is the for the first RL repetition, DL power information for RL + repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD +} +``` + +``` + + { ID id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION TDD-TPC-DownlinkStepSize PRESENCE optional } + -- This DL step size is the for the first RL repetition, DL step size information for RL repetitions + 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional } + -- This DL Power information is the for the first RL repetition, DL power information for RL + repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional } + -- This DL Power information is the for the first RL repetition, DL power information for RL + repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD + { ID id-RL-ID CRITICALITY ignore + EXTENSION RL-ID PRESENCE optional } + -- This is the RL ID for the first RL repetition + { ID id-multipleRL-dl-DPCH-InformationList CRITICALITY reject + EXTENSION MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD PRESENCE optional } + -- This DPCH Information is the for the 2nd and beyond RL repetition, + { ID id-DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }, -- + Applicable to 7.68Mcps TDD only + ... +} + +CCTrCH-TPCAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCAddItem-RL- +ReconfPrepTDD -- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only + +CCTrCH-TPCAddItem-RL-ReconfPrepTDD ::= SEQUENCE { + cCTrCH-ID cCTrCH-ID, + iE-Extensions ProtocolExtensionContainer { { CCTrCH-TPCAddItem-RL- + ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +CCTrCH-TPCAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { DL-DPCH- + InformationAddListIEs-RL-ReconfPrepTDD } } + +DL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE DL-DPCH- + InformationAddItem-RL-ReconfPrepTDD PRESENCE mandatory } +} + +DL-DPCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information DL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-InformationLCR DL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-LCR- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF +MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD +--Includes the 2nd through the max number of radio link information repetitions. + +``` + +``` + +MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD ::= SEQUENCE { + dl-DPCH-InformationList DL-DPCH-InformationAddList-RL- + ReconfPrepTDD OPTIONAL, + dl-DPCH-InformationListLCR DL-DPCH-LCR-InformationAddList-RL- + ReconfPrepTDD OPTIONAL, + CCTrCH-Initial-DL-Power DL-Power + OPTIONAL, + tDD-TPC-DownlinkStepSize TDD-TPC-DownlinkStepSize + OPTIONAL, + CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD DL-Power + OPTIONAL, + CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD DL-Power + OPTIONAL, + rL-ID RL-ID + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MultipleRL-DL-DPCH- + InformationAddListIE-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD CRITICALITY reject EXTENSION DL- + DPCH-768-InformationAddList-RL-ReconfPrepTDD PRESENCE optional }, -- Applicable to + 7.68Mcps TDD only + ... +} + +DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information768 DL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-768- + InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL- +CCTrCH-InformationModifyItem-RL-ReconfPrepTDD + +DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + CCTrCH-ID CCTrCH-ID, + tFCS TFCS + OPTIONAL, + tFCI-Coding TFCI-Coding + OPTIONAL, + punctureLimit PunctureLimit + OPTIONAL, + CCTrCH-TPCList CCTrCH-TPCModifyList-RL-ReconfPrepTDD + OPTIONAL, + dl-DPCH-InformationAddList DL-DPCH-InformationModify-AddList-RL- + ReconfPrepTDD OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + dl-DPCH-InformationModifyList DL-DPCH-InformationModify-ModifyList-RL- + ReconfPrepTDD OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + dl-DPCH-InformationDeleteList DL-DPCH-InformationModify-DeleteList-RL- + ReconfPrepTDD OPTIONAL, + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH- + InformationModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }| -- + Applicable to 1.28Mcps TDD only + -- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD +} + +``` + +``` + + { ID id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION TDD-TPC-DownlinkStepSize PRESENCE optional }| + -- This Step Size Information is the for the first RL repetition, step size information for RL + repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional }| + -- This power Information is the for the first RL repetition, power information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional }| + -- This power Information is the for the 2nd and beyond RL repetitions, power information for RL repetitions 2 + and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD + { ID id-RL-ID CRITICALITY ignore EXTENSION RL-ID PRESENCE optional }| + -- This is the RL ID for the first RL repetition + { ID id-multipleRL-dl-DPCH-InformationModifyList CRITICALITY reject EXTENSION + MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD PRESENCE optional }| + -- This DPCH Information is the for the 2nd and beyond RL repetitions, + { ID id-DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }, -- + Applicable to 7.68Mcps TDD only first radio link + ... + } + + CCTrCH-TPCModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH- + TPCModifyItem-RL-ReconfPrepTDD + + CCTrCH-TPCModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + cCTrCH-ID cCTrCH-ID, + iE-Extensions ProtocolExtensionContainer { { CCTrCH-TPCModifyItem-RL- + ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + CCTrCH-TPCModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + DL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { DL-DPCH- + InformationModify-AddListIEs-RL-ReconfPrepTDD } } + -- Applicable to 3.84Mcps TDD only + + DL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE DL- + DPCH-InformationModify-AddItem-RL-ReconfPrepTDD PRESENCE mandatory } + } + + DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information DL-Timeslot-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- + InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + DL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { DL-DPCH- + InformationModify-ModifyListIEs-RL-ReconfPrepTDD } } + + DL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE + DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD PRESENCE mandatory } + } + + DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod OPTIONAL, + repetitionLength RepetitionLength OPTIONAL, + tdd-DPCHOffset TDD-DPCHOffset OPTIONAL, + dL-Timeslot-InformationAddModify-ModifyList-RL-ReconfPrepTDD DL-Timeslot- + InformationModify-ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD PRESENCE + optional } | + { ID id-DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD PRESENCE + optional }, + ... +} + +DL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTSSs)) OF +DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + dl-Code-InformationModify-ModifyList-RL-ReconfPrepTDD DL-Code-InformationModify- + ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Timeslot- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (0..maxNrOfDPCHs)) OF DL- +Code-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID DPCH-ID, + tdd-ChannelisationCode TDD-ChannelisationCode OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Code- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE +(1..maxNrOfDLTSLCRs)) OF DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlotLCR TimeSlotLCR, + midambleShiftLCR MidambleShiftLCR OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + dl-Code-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD DL-Code-LCR- + InformationModify-ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Timeslot-LCR- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Maximum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional } | + -- Applicable to 1.28Mcps TDD only + { ID id-Minimum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD CRITICALITY ignore + EXTENSION DL-Power PRESENCE optional }, + -- Applicable to 1.28Mcps TDD only + ... +} + +DL-Code-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) +OF DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID DPCH-ID, + tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Code-LCR- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR PRESENCE optional}, + ... +} + +DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) +OF DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + timeSlot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, + tFCI-Presence TFCI-Presence OPTIONAL, + dL-Code-768-InformationModify-ModifyList-RL-ReconfPrepTDD DL-Code-768- + InformationModify-ModifyList-RL-ReconfPrepTDD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Timeslot-768- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-Code-768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs768)) +OF DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD + +DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID768 DPCH-ID768, + tdd-ChannelisationCode768 TDD-ChannelisationCode768 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-Code-768- + InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container { { DL-DPCH- +InformationModify-DeleteListIEs-RL-ReconfPrepTDD } } + +DL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= { + { ID id-DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD CRITICALITY reject TYPE + DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD PRESENCE mandatory } +} + +DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF DL- +DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD + +DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + dPCH-ID DPCH-ID, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- + InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-InformationLCR DL-TimeslotLCR-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-LCR- + InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... +} + +DL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF +MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD + +``` + +--Includes the 2nd through the max number of radio link information repetitions. + +``` + +MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD ::= SEQUENCE { + dl-DPCH-InformationAddList DL-DPCH-InformationModify- + AddList-RL-ReconfPrepTDD OPTIONAL, + dl-DPCH-InformationModifyList DL-DPCH-InformationModify- + ModifyList-RL-ReconfPrepTDD OPTIONAL, + dl-DPCH-InformationDeleteList DL-DPCH-InformationModify- + DeleteList-RL-ReconfPrepTDD OPTIONAL, + dl-DPCH-InformationAddListLCR DL-DPCH-LCR-InformationModify- + AddList-RL-ReconfPrepTDD OPTIONAL, + tDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD TDD-TPC-DownlinkStepSize + OPTIONAL, + CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD DL-Power + OPTIONAL, + CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD DL-Power + OPTIONAL, + rL-ID RL-ID + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { +MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD CRITICALITY reject + EXTENSION DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD PRESENCE optional }, -- +Applicable to 7.68Mcps TDD only + ... +} + +DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE { + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + dL-Timeslot-Information768 DL-Timeslot768-Information, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH-768- +InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL- +CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD + +DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + CCTrCH-ID CCTrCH-ID, + iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH- +InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DCH-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL- +ReconfPrepTDD + +DCH-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + dCH-ID DCH-ID, + iE-Extensions ProtocolExtensionContainer { { DCH-DeleteItem-RL- +ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... +} + +DCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DSCH-Information-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH- +Information-ModifyItem-RL-ReconfPrepTDD + +DSCH-Information-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + dSCH-ID DSCH-ID, +} + +``` + +``` + + cCTrCH-ID CCTrCH-ID OPTIONAL, + -- DL CCTrCH in which the DSCH is mapped + transportFormatSet TransportFormatSet OPTIONAL, + allocationRetentionPriority AllocationRetentionPriority OPTIONAL, + frameHandlingPriority FrameHandlingPriority OPTIONAL, + toAWS ToAWS OPTIONAL, + toAWE ToAWE OPTIONAL, + transportBearerRequestIndicator TransportBearerRequestIndicator, + iE-Extensions ProtocolExtensionContainer { { DSCH-Information- +ModifyItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... + } + + DSCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION TransportLayerAddress + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... + } + + DSCH-Information-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH- + Information-DeleteItem-RL-ReconfPrepTDD + + DSCH-Information-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + dSCH-ID DSCH-ID, + iE-Extensions ProtocolExtensionContainer { { DSCH-Information- + DeleteItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... + } + + DSCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + + USCH-Information-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH- + Information-ModifyItem-RL-ReconfPrepTDD + + USCH-Information-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { + uSCH-ID USCH-ID, + transportFormatSet TransportFormatSet OPTIONAL, + allocationRetentionPriority AllocationRetentionPriority OPTIONAL, + cCTrCH-ID CCTrCH-ID OPTIONAL, -- UL CCTrCH + in which the USCH is mapped + transportBearerRequestIndicator TransportBearerRequestIndicator, + iE-Extensions ProtocolExtensionContainer { { USCH-Information- + ModifyItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... + } + + USCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-bindingID CRITICALITY ignore EXTENSION BindingID + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-transportlayeraddress CRITICALITY ignore EXTENSION TransportLayerAddress + PRESENCE optional } | + -- Shall be ignored if bearer establishment with ALCAP. + { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos + PRESENCE optional }, + ... + } + + USCH-Information-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH- + Information-DeleteItem-RL-ReconfPrepTDD + + USCH-Information-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { + uSCH-ID USCH-ID, + iE-Extensions ProtocolExtensionContainer { { USCH-Information- + DeleteItem-RL-ReconfPrepTDD-ExtIEs } } OPTIONAL, + ... + } + + USCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + + ... + } + + MultipleRL-Information-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF RL-Information-RL- + ReconfPrepTDD + --Includes the 2nd through the max number of radio link information repetitions. + + RL-Information-RL-ReconfPrepTDD ::= SEQUENCE { + rL-ID RL-ID, + maxDL-Power DL-Power OPTIONAL, + minDL-Power DL-Power OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RL-Information-RL- + ReconfPrepTDD-ExtIEs} } OPTIONAL, + ... + } + + RL-Information-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-InitDL-Power CRITICALITY ignore EXTENSION DL-Power + PRESENCE optional }| + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific- + DCH-Info PRESENCE optional }| + { ID id-UL-Synchronisation-Parameters-LCR CRITICALITY ignore EXTENSION UL- + Synchronisation-Parameters-LCR PRESENCE optional }| + -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD + { ID id-TimeslotISCP-LCR-InfoList-RL-ReconfPrepTDD CRITICALITY ignore EXTENSION DL- + TimeslotISCPInfoLCR PRESENCE optional }| + -- Applicable to 1.28Mcps TDD only + { ID id-UARFCNforNt CRITICALITY reject EXTENSION UARFCN + PRESENCE optional }, + -- Applicable to 1.28Mcps TDD when using multiple frequencies + ... + } + + -- ***** + -- + -- RADIO LINK RECONFIGURATION READY + -- + -- ***** + + RadioLinkReconfigurationReady ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationReady-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationReady-Extensions}} + OPTIONAL, + ... + } + + RadioLinkReconfigurationReady-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC- + CommunicationContextID PRESENCE mandatory }| + { ID id-RL-InformationResponseList-RL-ReconfReady CRITICALITY ignore TYPE RL- + InformationResponseList-RL-ReconfReady PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE + CriticalityDiagnostics PRESENCE optional }, + ... + } + + RadioLinkReconfigurationReady-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-TargetCommunicationControlPortID CRITICALITY ignore EXTENSION + CommunicationControlPortID PRESENCE optional }| + { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD- + Information-Response PRESENCE optional }| + -- FDD only + { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD- + Information-Response PRESENCE optional }| + -- TDD only + { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH-Information- + Response PRESENCE optional }| + { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs- + ResetIndicator PRESENCE optional }| + { ID id-Fast-Reconfiguration-Permission CRITICALITY ignore EXTENSION Fast- + Reconfiguration-Permission PRESENCE optional }| + { ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response CRITICALITY ignore + EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response PRESENCE optional }| + { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-HS- + Cell-Information-Response-List PRESENCE optional }| + { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore + EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR PRESENCE optional }| + } + +``` + +``` + + { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore + EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional }| + { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore + EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR PRESENCE optional }| + { ID id-Additional-EDCH-Cell-Information-ResponseRLReconf CRITICALITY ignore EXTENSION + Additional-EDCH-Cell-Information-Response-RLReconf-list PRESENCE optional }| + { ID id-E-RNTI-For-FACH CRITICALITY ignore EXTENSION E-RNTI + PRESENCE optional }| + { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier- + EDCH-Information-Response PRESENCE optional }| + { ID id-MU-MIMO-Information-Response CRITICALITY reject EXTENSION MU-MIMO- + Information-Response PRESENCE optional }| + { ID id-Non-rectangular-resource-allocation-indicator CRITICALITY reject EXTENSION Non- + rectangular-resource-allocation-indicator PRESENCE optional }| + { ID id-Non-rectangular-resource-timeslot-set CRITICALITY reject EXTENSION Non-rectangular- + resource-timeslot-set PRESENCE optional }, + ... +} + +RL-InformationResponseList-RL-ReconfReady ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE- +Single-Container {{ RL-InformationResponseItemIE-RL-ReconfReady }} + +RL-InformationResponseItemIE-RL-ReconfReady NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationResponseItem-RL-ReconfReady CRITICALITY ignore TYPE RL- + InformationResponseItem-RL-ReconfReady PRESENCE mandatory } +} + +RL-InformationResponseItem-RL-ReconfReady ::= SEQUENCE { + rL-ID RL-ID, + dCH-InformationResponseList-RL-ReconfReady DCH-InformationResponseList-RL-ReconfReady + OPTIONAL, + dSCH-InformationResponseList-RL-ReconfReady DSCH-InformationResponseList-RL-ReconfReady + OPTIONAL, -- TDD only + uSCH-InformationResponseList-RL-ReconfReady USCH-InformationResponseList-RL-ReconfReady + OPTIONAL, -- TDD only + not-Used-tFCI2-BearerInformationResponse NULL + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RL- + InformationResponseItem-RL-ReconfReady-ExtIEs } } OPTIONAL, + ... +} + +RL-InformationResponseItem-RL-ReconfReady-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DL-PowerBalancing-UpdatedIndicator CRITICALITY ignore EXTENSION DL- + PowerBalancing-UpdatedIndicator PRESENCE optional }| + { ID id-E-DCH-RL-Set-ID CRITICALITY ignore EXTENSION RL-Set-ID + PRESENCE optional }| + { ID id-E-DCH-FDD-DL-Control-Channel-Information CRITICALITY ignore EXTENSION E-DCH-FDD-DL- + Control-Channel-Information PRESENCE optional }| + { ID id-E-DCH-FDD-Information-Response CRITICALITY ignore EXTENSION E-DCH-FDD- + Information-Response PRESENCE optional }| + { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH- + PreconfigurationInfo PRESENCE optional }| + { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving- + RL-Preconfig-Info PRESENCE optional }, + ... +} + +DCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ DCH- +InformationResponseListIEs-RL-ReconfReady }} + +DCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= { + { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse PRESENCE + mandatory } +} + +DSCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ DSCH- +InformationResponseListIEs-RL-ReconfReady }} + +DSCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= { + { ID id-DSCH-InformationResponse CRITICALITY ignore TYPE DSCH-InformationResponse PRESENCE + mandatory } +} + +USCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ USCH- +InformationResponseListIEs-RL-ReconfReady }} + +USCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-USCH-InformationResponse CRITICALITY ignore TYPE USCH-InformationResponse PRESENCE +mandatory } +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION FAILURE +-- +-- ***** + +RadioLinkReconfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationFailure- +Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= { + { ID id-CRNC-CommunicationContextID CRITICALITY ignore TYPE CRNC-CommunicationContextID + PRESENCE mandatory } | + { ID id-CauseLevel-RL-ReconfFailure CRITICALITY ignore TYPE CauseLevel-RL-ReconfFailure + PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... +} + +RadioLinkReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CauseLevel-RL-ReconfFailure ::= CHOICE { + generalCause GeneralCauseList-RL-ReconfFailure, + rLSpecificCause RLSpecificCauseList-RL-ReconfFailure, + ... +} + +GeneralCauseList-RL-ReconfFailure ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL- +ReconfFailure-ExtIEs} } OPTIONAL, + ... +} + +GeneralCauseItem-RL-ReconfFailure-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLSpecificCauseList-RL-ReconfFailure ::= SEQUENCE { + RL-ReconfigurationFailureList-RL-ReconfFailure RL-ReconfigurationFailureList-RL- +ReconfFailure OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { +RLSpecificCauseItem-RL-ReconfFailure-ExtIEs} } OPTIONAL, + ... +} + +RLSpecificCauseItem-RL-ReconfFailure-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RL-ReconfigurationFailureList-RL-ReconfFailure ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE- +Single-Container {{ RL-ReconfigurationFailureItemIE-RL-ReconfFailure}} + +RL-ReconfigurationFailureItemIE-RL-ReconfFailure NBAP-PROTOCOL-IES ::= { + { ID id-RL-ReconfigurationFailureItem-RL-ReconfFailure CRITICALITY ignore TYPE RL- +ReconfigurationFailureItem-RL-ReconfFailure PRESENCE mandatory} +} + +RL-ReconfigurationFailureItem-RL-ReconfFailure ::= SEQUENCE { + rL-ID RL-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { RL- +ReconfigurationFailureItem-RL-ReconfFailure-ExtIEs} } OPTIONAL, + ... +} + +RL-ReconfigurationFailureItem-RL-ReconfFailure-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION COMMIT +-- +-- ***** + +RadioLinkReconfigurationCommit ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationCommit-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationCommit- + Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationCommit-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY ignore TYPE NodeB- + CommunicationContextID PRESENCE mandatory } | + { ID id-CFN CRITICALITY ignore TYPE CFN + PRESENCE mandatory } | + { ID id-Active-Pattern-Sequence-Information CRITICALITY ignore TYPE Active-Pattern- + Sequence-Information PRESENCE optional }, + -- FDD only + ... +} + +RadioLinkReconfigurationCommit-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-Fast-Reconfiguration-Mode CRITICALITY reject EXTENSION Fast-Reconfiguration-Mode + PRESENCE optional }|--FDD only + { ID id-ActivationDelay CRITICALITY reject EXTENSION ActivationDelay + PRESENCE optional },--FDD only + ... +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION CANCEL +-- +-- ***** + +RadioLinkReconfigurationCancel ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationCancel-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationCancel- + Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationCancel-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY ignore TYPE NodeB- + CommunicationContextID PRESENCE mandatory }, + ... +} + +RadioLinkReconfigurationCancel-Extensions NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- RADIO LINK RECONFIGURATION REQUEST FDD +-- +-- ***** + +RadioLinkReconfigurationRequestFDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationRequestFDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationRequestFDD- + Extensions}} OPTIONAL, + ... +} + +RadioLinkReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= { + { ID id-NodeB-CommunicationContextID CRITICALITY reject TYPE NodeB- + CommunicationContextID PRESENCE mandatory } | + { ID id-UL-DPCH-Information-RL-ReconfRqstFDD CRITICALITY reject TYPE UL-DPCH- + Information-RL-ReconfRqstFDD PRESENCE optional } | + { ID id-DL-DPCH-Information-RL-ReconfRqstFDD CRITICALITY reject TYPE DL-DPCH- + Information-RL-ReconfRqstFDD PRESENCE optional } | +} + +``` + +``` + + { ID id-FDD-DCHs-to-Modify CRITICALITY reject TYPE FDD-DCHs-to- +Modify PRESENCE optional }| + { ID id-DCHs-to-Add-FDD CRITICALITY reject TYPE DCH-FDD- +Information PRESENCE optional }| + { ID id-DCH-DeleteList-RL-ReconfRqstFDD CRITICALITY reject TYPE DCH-DeleteList- +RL-ReconfRqstFDD PRESENCE optional }| + { ID id-RL-InformationList-RL-ReconfRqstFDD CRITICALITY reject TYPE RL- +InformationList-RL-ReconfRqstFDD PRESENCE optional }| + { ID id-Transmission-Gap-Pattern-Sequence-Information CRITICALITY reject TYPE Transmission- +Gap-Pattern-Sequence-Information PRESENCE optional }, + ... +} + +``` + +``` + +RadioLinkReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= { + { ID id-SignallingBearerRequestIndicator CRITICALITY reject EXTENSION +SignallingBearerRequestIndicator PRESENCE optional}| + { ID id-HSDSCH-FDD-Information CRITICALITY reject EXTENSION HSDSCH-FDD- +Information PRESENCE optional }| + { ID id-HSDSCH-Information-to-Modify-Unsynchronised CRITICALITY reject EXTENSION HSDSCH- +Information-to-Modify-Unsynchronised PRESENCE optional }| + { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject EXTENSION HSDSCH- +MACdFlows-Information PRESENCE optional }| + { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION HSDSCH- +MACdFlows-to-Delete PRESENCE optional }| + { ID id-HSDSCH-RNTI CRITICALITY reject EXTENSION HSDSCH-RNTI + PRESENCE conditional }| + -- The IE shall be present if HS-PDSCH RL ID IE is present. + { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID + PRESENCE optional }| + { ID id-E-DPCH-Information-RL-ReconfRqstFDD CRITICALITY reject EXTENSION E-DPCH- +Information-RL-ReconfRqstFDD PRESENCE optional }| + { ID id-E-DCH-FDD-Information CRITICALITY reject EXTENSION E-DCH-FDD- +Information PRESENCE optional }| + { ID id-E-DCH-FDD-Information-to-Modify CRITICALITY reject EXTENSION E-DCH-FDD- +Information-to-Modify PRESENCE optional }| + { ID id-E-DCH-MACdFlows-to-Add CRITICALITY reject EXTENSION E-DCH- +MACdFlows-Information PRESENCE optional }| + { ID id-E-DCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION E-DCH- +MACdFlows-to-Delete PRESENCE optional }| + { ID id-Serving-E-DCH-RL-ID CRITICALITY reject EXTENSION Serving-E-DCH- +RL-ID PRESENCE optional }| + { ID id-CPC-Information CRITICALITY reject EXTENSION CPC- +Information PRESENCE optional }| + { ID id-NoOfTargetCellHS-SCCH-Order CRITICALITY ignore EXTENSION +NoOfTargetCellHS-SCCH-Order PRESENCE optional }| + { ID id-Additional-HS-Cell-Information-RL-Reconf-Req CRITICALITY reject EXTENSION +Additional-HS-Cell-Information-RL-Reconf-Req PRESENCE optional }| + { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE- +AggregateMaximumBitRate PRESENCE optional }| + { ID id-Additional-EDCH-Cell-Information-RL-Reconf-Req CRITICALITY reject EXTENSION +Additional-EDCH-Cell-Information-RL-Reconf-Req PRESENCE optional }| + { ID id-UL-CLTD-Information-Reconf CRITICALITY reject EXTENSION UL-CLTD- +Information-Reconf PRESENCE optional }| + { ID id-E-DCH-Decoupling-Indication CRITICALITY reject EXTENSION E-DCH- +Decoupling-Indication PRESENCE optional }| + { ID id-Radio-Links-without-DPCH-FDPCH-Indication CRITICALITY reject EXTENSION Radio-Links- +without-DPCH-FDPCH-Indication PRESENCE optional }| + { ID id-UL-DPCCH2-Information-Reconf CRITICALITY reject EXTENSION UL-DPCCH2- +Information-Reconf PRESENCE optional }| + { ID id-Downlink-TPC-enhancements-Reconf CRITICALITY reject EXTENSION Downlink-TPC- +enhancements-Reconf PRESENCE optional }, + ... +} + +``` + +``` + +Additional-HS-Cell-Information-RL-Reconf-Req ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF +Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs + +``` + +``` + +Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs ::= SEQUENCE{ + hSPDSCH-RL-ID RL-ID, + c-ID C-ID + OPTIONAL, + hs-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information + OPTIONAL, + hs-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised HS-DSCH-FDD-Secondary- +Serving-Information-To-Modify-Unsynchronised OPTIONAL, + hs-DSCH-Secondary-Serving-Remove HS-DSCH-Secondary-Serving-Remove + OPTIONAL, +} + +``` + +``` + + iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information- +RL-Reconf-Req-ExtIEs} } OPTIONAL, + ... +} + +Additional-HS-Cell-Information-RL-Reconf-Req-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Additional-EDCH-Cell-Information-RL-Reconf-Req ::= SEQUENCE{ + setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency + Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency, + iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information- +RL-Reconf-Req-ExtIEs} } OPTIONAL, + ... +} + +Additional-EDCH-Cell-Information-RL-Reconf-Req-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE { + ul-TFCS TFCS OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UL-DPCH- +Information-RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +UL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-UL-DPCH-Indicator-For-E-DCH-Operation CRITICALITY reject EXTENSION UL-DPCH- +Indicator-For-E-DCH-Operation PRESENCE optional }, + ... +} + +DL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE { + dl-TFCS TFCS + OPTIONAL, + tFCI-SignallingMode TFCI-SignallingMode + OPTIONAL, + limitedPowerIncrease LimitedPowerIncrease + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DL-DPCH- +Information-RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +DL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +DCH-DeleteList-RL-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL- +ReconfRqstFDD + +DCH-DeleteItem-RL-ReconfRqstFDD ::= SEQUENCE { + dCH-ID DCH-ID, + iE-Extensions ProtocolExtensionContainer { { DCH-DeleteItem- +RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +DCH-DeleteItem-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RL-InformationList-RL-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single- +Container {{ RL-InformationItemIE-RL-ReconfRqstFDD }} + +RL-InformationItemIE-RL-ReconfRqstFDD NBAP-PROTOCOL-IES ::= { + { ID id-RL-InformationItem-RL-ReconfRqstFDD CRITICALITY reject TYPE RL- +InformationItem-RL-ReconfRqstFDD PRESENCE mandatory } +} + +RL-InformationItem-RL-ReconfRqstFDD ::= SEQUENCE { + rL-ID RL-ID, + maxDL-Power DL-Power OPTIONAL, + minDL-Power DL-Power OPTIONAL, + ... +} + +``` + +``` + + dl-CodeInformation FDD-DL-CodeInformation OPTIONAL, + -- The IE shall be present if the Transmission Gap Pattern Sequence Information IE is included +and the indicated Downlink Compressed Mode method for at least one of the included Transmission Gap +Pattern Sequence is set to "SF/2". + iE-Extensions ProtocolExtensionContainer { { RL-InformationItem- +RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +RL-InformationItem-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-DLReferencePower CRITICALITY ignore EXTENSION DL-Power + PRESENCE optional}| + { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info + PRESENCE optional}| + { ID id-E-DCH-RL-Indication CRITICALITY reject EXTENSION E-DCH-RL-Indication + PRESENCE optional}| + { ID id-RL-Specific-E-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-E-DCH-Info + PRESENCE optional}| + { ID id-F-DPCH-SlotFormat CRITICALITY reject EXTENSION F-DPCH-SlotFormat + PRESENCE optional}| + { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore EXTENSION HSDSCH- +PreconfigurationSetup PRESENCE optional}| + { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore EXTENSION Non-Serving-RL- +Preconfig-Setup PRESENCE optional}| + { ID id-Non-Serving-RL-Preconfig-Removal CRITICALITY ignore EXTENSION Non-Serving-RL- +Preconfig-Setup PRESENCE optional}| + { ID id-FTPICH-Information-Reconf CRITICALITY ignore EXTENSION FTPICH-Information- +Reconf PRESENCE optional}| + { ID id-TPC-slot-position CRITICALITY ignore EXTENSION TPC-slot-position + PRESENCE optional}, + ... +} + +``` + +``` + +E-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE { + maxSet-E-DPDCHs Max-Set-E-DPDCHs + OPTIONAL, + ul-PunctureLimit PunctureLimit + OPTIONAL, + e-TFCS-Information E-TFCS-Information + OPTIONAL, + e-TTI E-TTI + OPTIONAL, + e-DPCCH-PO E-DPCCH-PO + OPTIONAL, + e-RGCH-2-IndexStepThreshold E-RGCH-2-IndexStepThreshold + OPTIONAL, + e-RGCH-3-IndexStepThreshold E-RGCH-3-IndexStepThreshold + OPTIONAL, + hARQ-Info-for-E-DCH HARQ-Info-for-E-DCH + OPTIONAL, + hSDSCH-Configured-Indicator HSDSCH-Configured-Indicator + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { E-DPCH-Information-RL- +ReconfRqstFDD-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +E-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= { + { ID id-MinimumReducedE-DPDCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE- +DPDCH-GainFactor PRESENCE optional }, + ... +} + +``` + +``` + +-- **************************************************************************** +-- +-- RADIO LINK RECONFIGURATION REQUEST TDD +-- +-- **************************************************************************** + +``` + +``` + +RadioLinkReconfigurationRequestTDD ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationRequestTDD-IEs}}, + protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationRequestTDD- +Extensions}} OPTIONAL, + ... +} + +``` + +``` + +RadioLinkReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= { + +``` + +``` +{ ID id-NodeB-CommunicationContextID +CommunicationContextID PRESENCE mandatory }| +{ ID id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD +InformationModifyList-RL-ReconfRqstTDD PRESENCE optional } | +{ ID id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD +InformationDeleteList-RL-ReconfRqstTDD PRESENCE optional } | +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/marked/Rel-16/25_series/25434/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25434/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24c27596960e8b2c03803a2d07828ffcf7924f2e --- /dev/null +++ b/marked/Rel-16/25_series/25434/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e41e69278ade925bad30ba503a438ca775da90c326d42a3d7d3ae7b9b67175fd +size 27280 diff --git a/marked/Rel-16/25_series/25434/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/25_series/25434/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e72d7a3c295ceb4f22589a635dd06c3786c1ecd --- /dev/null +++ b/marked/Rel-16/25_series/25434/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5c1c7fabe90a99537afb8aee3f0b0e9308156d87fd05f423b8414a7b02c3bb2 +size 86273 diff --git a/marked/Rel-16/25_series/25434/raw.md b/marked/Rel-16/25_series/25434/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f67a084d4f9e1c0be8b464f17b467979a8c767a6 --- /dev/null +++ b/marked/Rel-16/25_series/25434/raw.md @@ -0,0 +1,338 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 Definitions, symbols and abbreviations..... 6 + +3.1 Definitions..... 6 + +3.2 Symbols..... 6 + +3.3 Abbreviations ..... 6 + +3.4 Specification Notations ..... 7 + +4 Data Link Layer ..... 8 + +4.1 ATM Transport Option ..... 8 + +4.1.1 Protection Switching at ATM Layer ..... 8 + +4.2 Data Link Layer for IP Transport Option..... 8 + +5 Iub Data Transport for Common Transport Channel Data Streams..... 8 + +5.1 Introduction ..... 8 + +5.2 ATM Transport Option ..... 9 + +5.3 IP Transport Option..... 9 + +6 Iub Transport Signalling Application for Common Transport Channel Data Streams ..... 10 + +6.1 Introduction ..... 10 + +6.2 Transport Signalling in case of ATM Transport Option ..... 10 + +6.3 Transport Signalling in case of IP Transport Option ..... 10 + +7 Signalling Bearer for ALCAP on Iub Interface..... 10 + +7.1 Introduction ..... 10 + +7.2 Signalling Bearer in ATM Transport Option ..... 11 + +7.3 Signalling Bearer in IP Transport Option ..... 11 + +8 Interworking between ATM and IP Transport Options ..... 11 + +Annex A (informative): Change history..... 12 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document shall provide a specification of the UTRAN RNC-Node B (Iub) interface Data Transport and Transport Signalling for Common Transport Channel data streams. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL". +- [2] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2". +- [3] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)". +- [4] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [5] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation Layer - Service Specific Coordination Function for Support of Signalling at the User Network Interface (SSCF at UNI)". +- [6] ITU-T Recommendation Q.2150.2 (1999-12): "Signalling transport converter on SSCOP and SSCOPMCE". +- [7] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [8] ITU-T Recommendation I.630 (1999-02): "ATM protection switching". +- [9] ITU-T Recommendation Q.2630.2 (2000-12): "AAL Type 2 signalling protocol (Capability Set 2)". +- [10] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing". +- [11] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Network Service Definition". +- [12] IETF RFC 768, (1980-08): "User Datagram Protocol". +- [13] IETF RFC 2460, (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [14] IETF RFC 791, (1981-09): "Internet Protocol". +- [15] IETF RFC 2474, (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [16] IETF RFC 1661, (1994-07): "The Point-to-Point Protocol (PPP)". +- [17] IETF RFC 1662, (1994-07): "PPP in HDLC-like Framing". +- [18] IETF RFC 2507, (1999-02): "IP header compression". + +- [19] IETF RFC 1990, (1996-08): "The PPP Multilink Protocol (MP)". +- [20] IETF RFC 2686, (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [21] Void +- [22] 3GPP TS 25.401, "UTRAN Overall Description" +- [23] 3GPP TS 25.426, "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams" +- [24] IETF RFC 3153, (2001-08): "PPP Multiplexing". +- [25] IETF RFC 2364, (1998-07): "PPP over AAL5". +- [26] IETF RFC 3031, (2001-01): "Multiprotocol Label Switching Architecture". +- [27] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan". +- [28] IETF RFC 3376 (2002-10), "Internet Group Management Protocol, Version 3". +- [29] IETF RFC 3810 (2004-06), "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". +- [30] IETF RFC 3544, (2003-07): "IP Header Compression over PPP". + +# 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the following abbreviations apply: + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**ALCAP:** "ALCAP" is a generic name for the transport signalling protocol used to setup and tear down transport bearers. + +**IP UTRAN node:** An UTRAN Node supporting the IP Transport Option + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +| | | +|---------|------------------------------------| +| AAL | ATM Adaption Layer | +| AAL2 | AAL Type 2 | +| ATM | Asynchronous Transfer Mode | +| CPCS | Common Part Convergence Sublayer | +| CPS | Common Part Sublayer | +| DSCH | Downlink Shared Channel | +| FACH | Forward Access Channel | +| FP | Frame Protocol | +| HDLC | High-level Data Link Control | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| LC | Link Characteristics | +| PPP | Point-to-Point Protocol | +| PT | Path Type | +| RACH | Random Access Channel | +| RNC | Radio Network Controller | +| SAAL | Signalling ATM Adaption Layer | +| SAR | Segmentation And Reassembly | + +| | | +|-------|-----------------------------------------------| +| SSCF | Service Specific Co-ordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| SSSAR | Service Specific Segmentation And Reassembly | +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UMTS | Universal Mobile Telecommunication Network | +| UNI | User-Network Interface | +| USCH | Uplink Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.4 Specification Notations + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. +- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. +- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. +- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. + +# --- 4 Data Link Layer + +## 4.1 ATM Transport Option + +ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T Recommendation I.361 [7]. + +### 4.1.1 Protection Switching at ATM Layer + +If redundancy of pathways at ATM layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Recommendation I.630 [8]. + +## 4.2 Data Link Layer for IP Transport Option + +An RNC or Node B supporting IP Transport Option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [16], IETF RFC 1662 [17]). + +NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [24], IETF RFC 2364 [25]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [26]), etc.) fulfilling the UTRAN requirements towards the upper layers. + +An RNC or Node B supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [18]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [19], IETF RFC 2686 [20]). In this case, negotiation of header compression (IETF RFC 2507 [18]) over PPP shall be performed via (IETF RFC 3544 [30]). + +# --- 5 Iub Data Transport for Common Transport Channel Data Streams + +## 5.1 Introduction + +This subclause specifies the transport layers that support Common Transport Channel (FACH, RACH, PCH, DSCH, HS-DSCH, USCH [TDD]) data streams. + +There are two options for protocol suites for transport of RACH, FACH, USCH [TDD], DSCH and HS-DSCH Iub data streams: + +- 1) ATM Transport Option +- 2) IP Transport Option + +The following figure 1 shows the protocol stacks of these two options: + +![Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates two protocol stacks for transporting data streams from the Radio Network Layer. Both stacks share a common Radio Network Layer at the top, which contains a box labeled "FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, USCH [TDD]". Below this layer, the two stacks diverge. + +**Left Stack (ATM Transport Option):** This stack consists of four layers. The top layer is the Transport Network Layer, which is divided into two sub-layers: "AAL2 SSSAR (I.366.1)" and "AAL2 CPS (I.363.2)". Below the Transport Network Layer is the ATM layer. The bottom layer is the PHY layer. The entire stack from the ATM layer down to the PHY layer is enclosed in a dashed box. + +**Right Stack (IP Transport Option):** This stack consists of four layers. The top layer is the Transport Network Layer, which is divided into two sub-layers: "UDP" and "IP". Below the Transport Network Layer is the Data Link Layer. The bottom layer is the Physical Layer. The entire stack from the Data Link Layer down to the Physical Layer is enclosed in a dashed box. + +Both stacks are connected to the common Radio Network Layer via a horizontal line with two ovals, representing the Iub interface. + +Below the left stack is the text "Protocol Stack for ATM Transport Option". Below the right stack is the text "Protocol Stack for IP Transport Option". + +Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option. + +**Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams** + +## 5.2 ATM Transport Option + +ATM and AAL2 (ITU-T Rec. I.363.2 [1] and ITU-T Rec. I.366.1 [2]) are used at the standard transport layer for Iub RACH, FACH, PCH, DSCH [TDD], USCH [TDD], HS-DSCH data streams. + +The Service Specific Segmentation and Reassembly (SSSAR) sublayer is used for the segmentation and reassembly of AAL2 SDUs (i.e. SSSAR is only considered from ITU-T Recommendation I.366.1 [2]). + +## 5.3 IP Transport Option + +UDP (IETF RFC 768 [12]) over IP shall be supported as the transport for RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH data streams on Iub Interface. The data link layer is as specified in chapter 4.2 + +An IP UTRAN node shall support IPv6 (IETF RFC 2460 [13]). The support of IPv4 (IETF RFC 791 [14]) is optional. + +NOTE: This does not preclude single implementation and use of IPv4. + +IP dual stack is recommended for the potential transition period from IPv4 to IPv6 in the transport network. + +The transport bearer is identified by the UDP port number and the IP address (source UDP port number, destination UDP port number, source IP address, destination IP address). + +The source IP address and destination IP address exchanged via Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [22]. + +IP Differentiated Services code point marking (IETF RFC 2474 [15]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters. + +IP multicast (IETF RFC 3376 [28], IETF RFC 3810 [29]) may be supported for FACH data streams on Iub Interface if the security of RAN will not be compromised. This can be guaranteed in a closed IP based RAN. + +# --- 6 Iub Transport Signalling Application for Common Transport Channel Data Streams + +## 6.1 Introduction + +This subclause specifies the transport signalling protocol(s) used to establish the user plane transport bearers. The protocol stack is shown in clause 7 (figure 2). + +## 6.2 Transport Signalling in case of ATM Transport Option + +Q.2630.2 as developed by ITU-T [9] is selected as the standard AAL2 signalling protocol for Iub. ITU-T Recommendation Q.2630.2 [9] adds new optional capabilities to ITU-T Recommendation Q.2630.1 [3]. + +Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 [9]. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. + +User Plane Transport bearers are established and in all normal cases released by the ALCAP in the Controlling RNC. The Node B shall initiate release of the user plane transport bearers for the removed common channels that were remaining within the cell when the cell is deleted. + +AAL2 transport layer addressing is based on embedded E.164 (ITU-T Rec. E.164 [27]) or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [10], ITU-T Rec. X.213 [11]). Native E.164 addressing (ITU-T Rec. E.164 [27]) shall not be used. + +If there is an AAL2 switching function in the transport network layer of the interface, the Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol. + +If there is an AAL2 switching function in the transport network layer of the interface, the Path Type parameter (PT) may be included in the Establish Request message of AAL2 signalling protocol for prioritisation at ATM level. + +If the value in either the Maximum CPS-SDU Bit Rate or the Average CPS-SDU Bit Rate of the Link Characteristics (LC) in AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [9] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher. + +**NOTE:** Separation of traffic (e.g. HSDPA) using this modified ITU-T Rec. Q.2630.2 [9] from other traffic is highly recommended. Otherwise the bursty nature of the HSDPA traffic in combination with the unknown traffic volume per connection for bit rates exceeding 2048 Kbit/s may decrease the QoS of all traffic within the same AAL type 2 path. + +## 6.3 Transport Signalling in case of IP Transport Option + +An ALCAP protocol is not required in case both UTRAN Nodes (RNC and Node B) are using the IP Transport Option. + +# --- 7 Signalling Bearer for ALCAP on Iub Interface + +## 7.1 Introduction + +This subclause specifies the signalling bearer protocol stack which supports the ALCAP. + +## 7.2 Signalling Bearer in ATM Transport Option + +SAAL-UNI is the standard signalling bearer for the AAL Type Signalling protocol (ITU-T Rec. Q.2630.2 [9]) on Iub (ITU-T Rec. Q.2110 [4], ITU-T Rec. Q.2130 [5]). The protocol stack is shown in figure 2. + +![Diagram of Transport Network Control plane protocol structure on Iub in case of ATM Transport Option](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the protocol stack for the Transport Network Control plane on the Iub interface when using the ATM Transport Option. At the top is a box labeled 'Q.2630.2'. Below it is a horizontal line with a circle in the center, representing a connection point. The main stack consists of five layers: 1. STC (Q.2150.2); 2. AAL5 SSCS, which includes SSCF-UNI and SSCOP; 3. AAL5 Common Part (CPCS / SAR); 4. ATM; and 5. PHY. The top and bottom layers are enclosed in dashed boxes, while the middle three layers are in a solid box. + +Diagram of Transport Network Control plane protocol structure on Iub in case of ATM Transport Option + +**Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option** + +The signalling transport converter (STC) relevant for Iub is ITU-T Recommendation Q.2150.2 [6]. The AAL5 Common Part contains CPCS and SAR. + +## 7.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case of both UTRAN Nodes (RNC and Node B) are using the IP Transport Option. + +# --- 8 Interworking between ATM and IP Transport Options + +An RNC or Node B supporting IP transport option shall provide interworking to an RNC or Node B supporting only ATM transport option. The interworking alternatives are defined in TS 25.426 [23]. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.2.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110684 | 0040 | | Correction of References in TS 25.434 | 10.1.0 | +| 52 | RP-110685 | 0041 | 1 | Update of References in TS 25.434 | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25435/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25435/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1941f48531346a4747b0e3460390d234012e8fd2 --- /dev/null +++ b/marked/Rel-16/25_series/25435/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:202dfb3bd397c75d994135d691e5a6d4c19773e669c3f5f24fbc8f47bbb39fe8 +size 21272 diff --git a/marked/Rel-16/25_series/25435/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-16/25_series/25435/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7853e53003c3f6c66d153f618164d3baa11c79ec --- /dev/null +++ b/marked/Rel-16/25_series/25435/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34104b28774a294fa334201e2bc972960b7731cd091e2ad307ba8e3a77b1924d +size 26458 diff --git a/marked/Rel-16/25_series/25435/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/25_series/25435/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c9db252bf09b7ea2cc9a77b80bab821d4d2fc9b --- /dev/null +++ b/marked/Rel-16/25_series/25435/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b914edc5f90a6cb18de08174021b80fbe78880f9edd9546c36cc1d7090225a9a +size 155766 diff --git a/marked/Rel-16/25_series/25435/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg b/marked/Rel-16/25_series/25435/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c8df3a4d32bd7fd93626b338e29e360b04ab030 --- /dev/null +++ b/marked/Rel-16/25_series/25435/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97b995fdfaeefe41169623d3bc4df983cf47e1e237f786bd3511b7500c223cd3 +size 26028 diff --git a/marked/Rel-16/25_series/25435/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/marked/Rel-16/25_series/25435/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4d484b89430ffaa8ff02b08395f73bd74b9b070 --- /dev/null +++ b/marked/Rel-16/25_series/25435/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2900fc24f606aef173e9524abb21abba86a955ca7b9fdec1e3746c0fa2398fcc +size 19835 diff --git a/marked/Rel-16/25_series/25435/147f857b06606c016ce376b7a89934d2_img.jpg b/marked/Rel-16/25_series/25435/147f857b06606c016ce376b7a89934d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f1fd1db2e58f613114c5a1ca13ec9d158428cc8 --- /dev/null +++ b/marked/Rel-16/25_series/25435/147f857b06606c016ce376b7a89934d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:814aaeff02468e89ebe17c1de8d62055d7b2f4c68805f32a38a17f6419eab686 +size 18930 diff --git a/marked/Rel-16/25_series/25435/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/25_series/25435/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e2b8769abe2cae1d0977e673e02edae3194d27a --- /dev/null +++ b/marked/Rel-16/25_series/25435/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5cc7501fac2f3c1b00f4126a0165629e815905d3daeece3bf27636f00bb75d +size 18005 diff --git a/marked/Rel-16/25_series/25435/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-16/25_series/25435/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70da71a6d9727764bd2e4c31efc6704d6889a047 --- /dev/null +++ b/marked/Rel-16/25_series/25435/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae9c1601cc567b033837f58bece8ec2659707c235a3e5ac03d93977e8b26b093 +size 9972 diff --git a/marked/Rel-16/25_series/25435/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/marked/Rel-16/25_series/25435/220869911a1ecfa1dd4aa6d750319aad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3db30f9380ad7c6442bf0d83854e077171a0738 --- /dev/null +++ b/marked/Rel-16/25_series/25435/220869911a1ecfa1dd4aa6d750319aad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56659acbbbdca11026baa03e4e5cc20070741e7e21f7861053928063d922f010 +size 14916 diff --git a/marked/Rel-16/25_series/25435/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/25_series/25435/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02692357002b1f3a565320a21fd9136d5accf537 --- /dev/null +++ b/marked/Rel-16/25_series/25435/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7ed3b020ee99faefa014fdc24b59c658ef08557e9e664fae670c028ea8813b7 +size 184070 diff --git a/marked/Rel-16/25_series/25435/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/25_series/25435/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9192002282c75d82aecd56a0804645d32c05d229 --- /dev/null +++ b/marked/Rel-16/25_series/25435/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b2ea2de322b14cd122b55ebef3e1b27feaf9db29d52e8e6280d50dfb8f7f650 +size 95858 diff --git a/marked/Rel-16/25_series/25435/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/25_series/25435/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78397eb0e7d7ac96b729a4c9810ef0c544243a29 --- /dev/null +++ b/marked/Rel-16/25_series/25435/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:442757d35aa0a570a01cc7f61488972ee7f8d79b729339f088608d98e272399f +size 84195 diff --git a/marked/Rel-16/25_series/25435/3a72363d45bf0a19e0b543424b732b2c_img.jpg b/marked/Rel-16/25_series/25435/3a72363d45bf0a19e0b543424b732b2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4916fa2224f1bd554225e8187204639fbf59e35 --- /dev/null +++ b/marked/Rel-16/25_series/25435/3a72363d45bf0a19e0b543424b732b2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:519a8c539fc993c77a92a5798e4379b98b38658cb0bb46ef2bfdf5952328a28e +size 44749 diff --git a/marked/Rel-16/25_series/25435/3bd9d303382ff0566369ed81a9226ade_img.jpg b/marked/Rel-16/25_series/25435/3bd9d303382ff0566369ed81a9226ade_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8be426b77e889f8d4272d4d1c5d8a83c23cb70cc --- /dev/null +++ b/marked/Rel-16/25_series/25435/3bd9d303382ff0566369ed81a9226ade_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:062d567c1a1f3b3de0798f04fc48f4f7775c60b470560ffe17482b46f4a2e9a2 +size 20037 diff --git a/marked/Rel-16/25_series/25435/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/25_series/25435/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a09eace91156cbb5b15d50c5ae50eceffb0b87f2 --- /dev/null +++ b/marked/Rel-16/25_series/25435/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4eeb9296645547fe5d01235e92e8bfa336abf7e970d16d44a9b421b21ad0ae00 +size 10031 diff --git a/marked/Rel-16/25_series/25435/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25435/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5683be57ffced04930483920de8aea3044af37a2 --- /dev/null +++ b/marked/Rel-16/25_series/25435/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287da3de8aeebc426d04890ef2de8390e65848c4e428991c18b6e45362a53dd9 +size 11259 diff --git a/marked/Rel-16/25_series/25435/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/25_series/25435/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a61400634a421a49cfd3230070b029e9682bc88 --- /dev/null +++ b/marked/Rel-16/25_series/25435/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8620c9f8b7287e41bec814a634b26b241737a51525daa07d261a3741ddc3fe43 +size 11373 diff --git a/marked/Rel-16/25_series/25435/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/25_series/25435/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d249fc099a2f0f755d71f691c611960fa43b61bb --- /dev/null +++ b/marked/Rel-16/25_series/25435/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375f4bdb9c99ba77154995f3f9071f0ff38eff5acb5743ad28fda328a00a8464 +size 56897 diff --git a/marked/Rel-16/25_series/25435/4b82c57bac9f5800baee15745b212963_img.jpg b/marked/Rel-16/25_series/25435/4b82c57bac9f5800baee15745b212963_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03acc6952a28fe0db1a2163d1a1f2bdf802a5652 --- /dev/null +++ b/marked/Rel-16/25_series/25435/4b82c57bac9f5800baee15745b212963_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9a9cc216921d32cac72a833a0e6b1ec80af2f9d797da97be6b96d01e3fbcf4f +size 30760 diff --git a/marked/Rel-16/25_series/25435/4b8c5ecb492fd759c766fe8950fafe67_img.jpg b/marked/Rel-16/25_series/25435/4b8c5ecb492fd759c766fe8950fafe67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b661601d60d6e32763de05636019d20b4cb77209 --- /dev/null +++ b/marked/Rel-16/25_series/25435/4b8c5ecb492fd759c766fe8950fafe67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd04f2aec2d3b4339d63d1941695ea0fb88b7420d21d4fab7e5c023aacb6f947 +size 22702 diff --git a/marked/Rel-16/25_series/25435/4bb3aa9902f241d0b9ea5f1151b287b5_img.jpg b/marked/Rel-16/25_series/25435/4bb3aa9902f241d0b9ea5f1151b287b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92d2375e289384c4d350523c7b65164749dfcf79 --- /dev/null +++ b/marked/Rel-16/25_series/25435/4bb3aa9902f241d0b9ea5f1151b287b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f45916cbd5081a6bded156fdc4708a02ceacd0f9480f64e81e6935e8acbf623e +size 40127 diff --git a/marked/Rel-16/25_series/25435/58bbc570572758132ea39938e4f03b5b_img.jpg b/marked/Rel-16/25_series/25435/58bbc570572758132ea39938e4f03b5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ac13c21d8ba266af987fdac6665522204109649 --- /dev/null +++ b/marked/Rel-16/25_series/25435/58bbc570572758132ea39938e4f03b5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19dec8d0a06bd21e6d2958496a846f92e07209acfcce1a62f49c51f0c56172da +size 22927 diff --git a/marked/Rel-16/25_series/25435/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/25_series/25435/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d25831a1cea1c27e7af7b753485ccf2f2b859ed0 --- /dev/null +++ b/marked/Rel-16/25_series/25435/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b92ba9c41209b3982637ab1716411c42b4bf5b18a626e4cc5f90b3a2b1d2c0bd +size 17647 diff --git a/marked/Rel-16/25_series/25435/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-16/25_series/25435/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcc91cb8518f706d5b2163799ebd84e4e56403af --- /dev/null +++ b/marked/Rel-16/25_series/25435/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2067ab8195d72f82c0de6229c829957fdd035e3f36122c7c4e2936ace9a64f1 +size 15501 diff --git a/marked/Rel-16/25_series/25435/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/25_series/25435/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..321f7905f374b753b47273d893da7ced00f581c8 --- /dev/null +++ b/marked/Rel-16/25_series/25435/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51e7c6bc10301442e59e55dde6454761d801d69eee782047d45419489ca6fc54 +size 11899 diff --git a/marked/Rel-16/25_series/25435/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/25_series/25435/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6777e9afab2a014c2eca88d1219f39ee84e407b3 --- /dev/null +++ b/marked/Rel-16/25_series/25435/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba400c69dea50681a576610a67e5e5725cfb43ee4e2c4e5b6f8d0448d3db48ca +size 11390 diff --git a/marked/Rel-16/25_series/25435/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25435/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5c90fcd9105e065843448f8328f6b3ceae6c9ba --- /dev/null +++ b/marked/Rel-16/25_series/25435/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c26be36399bc91c5d213a6b3526f13ff0b7b878a8e4f3a1efea1198310030f7 +size 11000 diff --git a/marked/Rel-16/25_series/25435/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/25_series/25435/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..753246c44240616891c2dc107633dd8357ec8c1d --- /dev/null +++ b/marked/Rel-16/25_series/25435/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa0dfb82a907917cc852a33a2ce3078b8c31d787f65042198c6e5043f535871b +size 30429 diff --git a/marked/Rel-16/25_series/25435/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25435/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..014e95464129ae62666edb254502dbee2cca7f5b --- /dev/null +++ b/marked/Rel-16/25_series/25435/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8516e130b1e6d037adfd3c4cf0136998388f76b5f16f28f26fc7d947697558bc +size 65367 diff --git a/marked/Rel-16/25_series/25435/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/25_series/25435/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d84dc232a2a367e0b8482180fdc752691d14b47d --- /dev/null +++ b/marked/Rel-16/25_series/25435/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc3011d8c1286c16799c6ec4123099d0ff0cf78ad0ecc2aec75bb8fe9216234 +size 19861 diff --git a/marked/Rel-16/25_series/25435/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-16/25_series/25435/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd7c097b9cf42eebe4d066a03bce1b150792ad99 --- /dev/null +++ b/marked/Rel-16/25_series/25435/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ab1e653737e5173743d7b2576031b7e72949a0e435d2c85373a961d11c9d9c7 +size 29287 diff --git a/marked/Rel-16/25_series/25435/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/25_series/25435/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6d5e662c425f54be74cd06522426b512b75d866 --- /dev/null +++ b/marked/Rel-16/25_series/25435/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85411dd64faaa444cb74ca5d4962986a435fd67a2b5d1d426a2411ffa49cda9a +size 18969 diff --git a/marked/Rel-16/25_series/25435/a7079ddb124df3f1ee13ae406c7c8982_img.jpg b/marked/Rel-16/25_series/25435/a7079ddb124df3f1ee13ae406c7c8982_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f8a2d3dcba724de8ce637d4a53074f8b0cb855d --- /dev/null +++ b/marked/Rel-16/25_series/25435/a7079ddb124df3f1ee13ae406c7c8982_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0ed641ac029da7708cdd4b87102293c66923cb940546afb429614db7c7a4b87 +size 11257 diff --git a/marked/Rel-16/25_series/25435/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Rel-16/25_series/25435/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd12522f80599f4d954a0b2c3051fc8fe5beea1c --- /dev/null +++ b/marked/Rel-16/25_series/25435/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b04ed802f361ed0d479c6d65d324ca9cb59034531fb9aa14716edc34456e527 +size 13492 diff --git a/marked/Rel-16/25_series/25435/b0e32f17c90ce1db73135488888ce558_img.jpg b/marked/Rel-16/25_series/25435/b0e32f17c90ce1db73135488888ce558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..657a74669feda89174b4a031a2953b17ec52480c --- /dev/null +++ b/marked/Rel-16/25_series/25435/b0e32f17c90ce1db73135488888ce558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9908a8dd6560cd8a228c7fbe97259cecf22f20ec679ff55c588ce7cb3cf607ba +size 23182 diff --git a/marked/Rel-16/25_series/25435/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/25_series/25435/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1647830015a92aaf178c5a455747e9bcca92ca3 --- /dev/null +++ b/marked/Rel-16/25_series/25435/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde34311706d38ea13cce90e9af27d9d91fe6099e78b2da50e3877cb0ce25c2f +size 10979 diff --git a/marked/Rel-16/25_series/25435/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/25_series/25435/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..178de799293f7b8510133bd6264d4fd70737013c --- /dev/null +++ b/marked/Rel-16/25_series/25435/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0e70c78cf3cc870149ec2eca62b653fafb50b6fd44bbca2656de1205a20eb73 +size 11799 diff --git a/marked/Rel-16/25_series/25435/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/25_series/25435/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e87bdb53cd9bf385e70acb81a3a8931e583c7867 --- /dev/null +++ b/marked/Rel-16/25_series/25435/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ceb306cface74865921edf42fd059301824ae2a0ec2d2e62d8f5549fd1ae203e +size 113406 diff --git a/marked/Rel-16/25_series/25435/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25435/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7779c8f531b382935bff4e1320fdca03698e53ee --- /dev/null +++ b/marked/Rel-16/25_series/25435/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3779e05a9731fc0d899efc672968438220653318edf8014ada3ca93ed0c52b6a +size 17211 diff --git a/marked/Rel-16/25_series/25435/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/marked/Rel-16/25_series/25435/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7d7dedbdc248d11e32c628baceb080dfbd4c979 --- /dev/null +++ b/marked/Rel-16/25_series/25435/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8233b129af4b11029652b6230cc61cda772a1f7edd6b08525cb2e317f32460d4 +size 10998 diff --git a/marked/Rel-16/25_series/25435/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-16/25_series/25435/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21078680c68fe180bddd8455718d8302a3700350 --- /dev/null +++ b/marked/Rel-16/25_series/25435/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ea1fc4163b370bb911d922e3c6584421f0cdd04772e198c5ddbe8adb0563518 +size 25279 diff --git a/marked/Rel-16/25_series/25435/raw.md b/marked/Rel-16/25_series/25435/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f3ee91305410eac7a8d5c4203517fda783df472e --- /dev/null +++ b/marked/Rel-16/25_series/25435/raw.md @@ -0,0 +1,2792 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 3.3 Specification Notations ..... | 9 | +| 4 General aspects ..... | 10 | +| 4.1 Common Transport Channel Data Stream User Plane Protocol Services..... | 10 | +| 4.2 Services expected from the Data Transport Network layer ..... | 10 | +| 4.3 Protocol Version..... | 11 | +| 5 Data Streams User Plane Procedures..... | 11 | +| 5.1 Data Transfer..... | 11 | +| 5.1.1 RACH Channels ..... | 11 | +| 5.1.2 CPCH Channels [FDD] ..... | 11 | +| 5.1.3 Secondary-CCPCH related transport Channels..... | 11 | +| 5.1.4 Downlink Shared Channels [TDD] ..... | 12 | +| 5.1.5 Uplink Shared Channels [TDD] ..... | 13 | +| 5.1.6 High Speed Downlink Shared Channels ..... | 13 | +| 5.1.7 E-DCH Channels for CELL_FACH and Idle[FDD and 1.28Mcps TDD]..... | 15 | +| 5.2 Node Synchronisation ..... | 15 | +| 5.3 DL Transport Channels Synchronisation..... | 16 | +| 5.4 DL Timing Adjustment ..... | 16 | +| 5.5 Dynamic PUSCH Assignment [TDD] ..... | 17 | +| 5.6 DSCH TFCI Signalling [FDD] ..... | 17 | +| 5.7 Timing Advance [3.84 Mcps and 7.68Mcps TDD] ..... | 18 | +| 5.7A Outer Loop PC Information Transfer [1.28 Mcps TDD]..... | 18 | +| 5.8 General ..... | 18 | +| 5.8.1 Association between transport bearer and data/control frames ..... | 18 | +| 5.8.2 DSCH / USCH transport bearer replacement [TDD] ..... | 19 | +| 5.8.3 HS-DSCH Transport Bearer Replacement..... | 20 | +| 5.9 HS-DSCH Capacity Request..... | 21 | +| 5.10 HS-DSCH Capacity Allocation..... | 21 | +| 5.11 Indication of UE State Transition [1.28Mcps TDD]..... | 22 | +| 5.12 HS-DSCH UL Synchronization Establishment Failure [1.28Mcps TDD] ..... | 22 | +| 5.13 HS-DSCH PDU DROP INDICATION..... | 22 | +| 6 Frame Structure and Coding ..... | 23 | +| 6.1 General ..... | 23 | +| 6.2 Data frame structure..... | 24 | +| 6.2.1 RACH Channels ..... | 24 | +| 6.2.2 CPCH Channels [FDD] ..... | 26 | +| 6.2.3 FACH Channels..... | 26 | +| 6.2.4 PCH Channels ..... | 27 | +| 6.2.5 Downlink Shared Channels [TDD] ..... | 28 | +| 6.2.6 Uplink Shared Channels [TDD] ..... | 28 | +| 6.2.6A HS-DSCH Channels ..... | 29 | +| 6.2.6B E-DCH Channels for CELL_FACH and Idle[FDD and 1.28Mcps TDD]..... | 35 | +| 6.2.7 Coding of information elements in data frames ..... | 37 | +| 6.2.7.1 Header CRC..... | 37 | +| 6.2.7.2 Frame Type..... | 37 | +| 6.2.7.3 Connection Frame Number (CFN) ..... | 37 | +| 6.2.7.4 Transport Format Indicator ..... | 38 | +| 6.2.7.5 Propagation Delay [FDD]..... | 38 | +| 6.2.7.5A Ext Propagation Delay [FDD] ..... | 38 | +| 6.2.7.6 Rx Timing Deviation [3.84Mcps TDD] ..... | 38 | + +| | | | +|----------|-------------------------------------------------------------|----| +| 6.2.7.6A | Received SYNC UL Timing Deviation [1.28Mcps TDD] ..... | 39 | +| 6.2.7.6B | Rx Timing Deviation [7.68Mcps TDD] ..... | 39 | +| 6.2.7.7 | Transport Block ..... | 39 | +| 6.2.7.8 | CRC Indicator ..... | 39 | +| 6.2.7.9 | Payload CRC ..... | 39 | +| 6.2.7.10 | Transmit Power Level ..... | 40 | +| 6.2.7.11 | Paging Indication (PI) ..... | 40 | +| 6.2.7.12 | Paging Indication bitmap (PI-bitmap) ..... | 40 | +| 6.2.7.13 | Rx Timing Deviation on RACH [3.84Mcps TDD] ..... | 40 | +| 6.2.7.14 | PDSCH Set Id [TDD] ..... | 40 | +| 6.2.7.15 | Code Number [FDD] ..... | 41 | +| 6.2.7.16 | Spreading Factor (SF) [FDD] ..... | 41 | +| 6.2.7.17 | Power Offset [FDD] ..... | 41 | +| 6.2.7.18 | MC Info [FDD] ..... | 41 | +| 6.2.7.19 | Spare Extension ..... | 41 | +| 6.2.7.20 | Quality Estimate (QE) [TDD] ..... | 41 | +| 6.2.7.21 | Common Transport Channel Priority Indicator (CmCH-PI) ..... | 41 | +| 6.2.7.22 | User Buffer Size ..... | 41 | +| 6.2.7.23 | MAC-d PDU Length ..... | 41 | +| 6.2.7.24 | NumOfPDU ..... | 42 | +| 6.2.7.25 | MAC-d PDU ..... | 42 | +| 6.2.7.26 | Cell Portion ID [FDD] ..... | 42 | +| 6.2.7.27 | New IE Flags ..... | 42 | +| 6.2.7.28 | Flush ..... | 42 | +| 6.2.7.29 | DRT (Delay Reference Time) ..... | 42 | +| 6.2.7.30 | Frame Sequence Number ..... | 43 | +| 6.2.7.31 | Logical Channel ID in block n ..... | 43 | +| 6.2.7.32 | Total Number of PDU blocks ..... | 43 | +| 6.2.7.33 | MAC-d/c PDU Length in block n ..... | 43 | +| 6.2.7.34 | Number of MAC-d/c PDUs in block n (#PDUs in block n) ..... | 43 | +| 6.2.7.35 | DRT Indicator ..... | 43 | +| 6.2.7.36 | FACH Indicator (FI) [FDD and 1.28Mcps TDD] ..... | 44 | +| 6.2.7.37 | H-RNTI [FDD and 1.28Mcps TDD] ..... | 44 | +| 6.2.7.38 | RACH Measurement Result [FDD and 1.28Mcps TDD] ..... | 44 | +| 6.2.7.39 | H-RNTI Indicator (HI) [FDD and 1.28Mcps TDD] ..... | 44 | +| 6.2.7.40 | FSN/DRT Reset ..... | 44 | +| 6.2.7.41 | MAC-d/c PDU ..... | 45 | +| 6.2.7.42 | AOA (Angle of Arrival) [1.28Mcps TDD] ..... | 45 | +| 6.2.7.43 | Ext Received SYNC UL Timing Deviation [1.28Mcps TDD] ..... | 45 | +| 6.2.7.44 | Number of Subframes [FDD and 1.28Mcps TDD] ..... | 45 | +| 6.2.7.45 | Number of MAC-is SDU in frame [FDD and 1.28Mcps TDD] ..... | 45 | +| 6.2.7.46 | Number of MAC-is PDUs [FDD and 1.28Mcps TDD] ..... | 45 | +| 6.2.7.47 | Subframe Number [FDD and 1.28Mcps TDD] ..... | 46 | +| 6.2.7.48 | E-DCH User Buffer Size [FDD and 1.28Mcps TDD] ..... | 46 | +| 6.2.7.49 | E-RNTI [FDD and 1.28Mcps TDD] ..... | 46 | +| 6.2.7.50 | MAC-is PDU descriptor [FDD and 1.28Mcps TDD] ..... | 46 | +| 6.2.7.51 | Dedicated H-RNTI [FDD and 1.28Mcps TDD] ..... | 46 | +| 6.2.7.52 | eDRX Indication [FDD] ..... | 46 | +| 6.2.7.53 | HS-DSCH physical layer category [FDD] ..... | 46 | +| 6.2.7.54 | Cell Portion LCR ID [1.28Mcps TDD] ..... | 47 | +| 6.2.7.55 | TS0 Indication [1.28Mcps TDD] ..... | 47 | +| 6.2.7.56 | Enhanced HS-SCCH support indicator (EI) [FDD] ..... | 47 | +| 6.2.7.57 | MU-MIMO Indication(MI) [1.28Mcps TDD] ..... | 47 | +| 6.2.7.58 | Propagation Delay Full Range [FDD] ..... | 47 | +| 6.2.7.59 | CPC Recovery (CPC Recov) [FDD] ..... | 47 | +| 6.2.7.60 | FeDRX Indication [FDD] ..... | 47 | +| 6.2.7.61 | NodeB Triggered HS-DPCCH Transmission(NTHT) [FDD] ..... | 48 | +| 6.2.7.62 | TTI length [FDD] ..... | 48 | +| 6.2.7.63 | SN, Frame Number ..... | 48 | +| 6.2.7.64 | S/D, Store/Discard indicator ..... | 48 | +| 6.2.7.65 | CR Ind (Cell Reselection Indication) ..... | 48 | +| 6.2.7.66 | CRR Rec (Cell Reselection Request Received) ..... | 48 | + +| | | | +|------------|---------------------------------------------------------------------------------|----| +| 6.2.7.67 | Multiple UEs Indicator (MUI) [FDD] ..... | 48 | +| 6.2.7.68 | Extended for UEn [FDD]..... | 49 | +| 6.2.7.69 | Operation Preference of Common E-DCH resource Indication (OPCE Ind) [FDD] ..... | 49 | +| 6.2.7.70 | HS-SCCH DRX Indication [FDD] ..... | 49 | +| 6.3 | Control frame structure ..... | 49 | +| 6.3.1 | Introduction ..... | 49 | +| 6.3.2 | Coding of information elements of the Control frame header..... | 49 | +| 6.3.2.1 | Frame CRC ..... | 49 | +| 6.3.2.2 | Frame Type (FT)..... | 50 | +| 6.3.2.3 | Control Frame Type..... | 50 | +| 6.3.3 | Payload structure and information elements ..... | 50 | +| 6.3.3.1 | TIMING ADJUSTMENT..... | 50 | +| 6.3.3.1.1 | Payload Structure ..... | 50 | +| 6.3.3.1.2 | CFN ..... | 51 | +| 6.3.3.1.3 | Time of arrival (ToA)..... | 51 | +| 6.3.3.1.4 | Spare Extension..... | 51 | +| 6.3.3.2 | DL SYNCHRONISATION ..... | 51 | +| 6.3.3.2.1 | Payload Structure ..... | 51 | +| 6.3.3.2.2 | CFN ..... | 52 | +| 6.3.3.2.3 | Spare Extension..... | 52 | +| 6.3.3.3 | UL SYNCHRONISATION ..... | 52 | +| 6.3.3.3.1 | Payload Structure ..... | 52 | +| 6.3.3.3.2 | CFN ..... | 52 | +| 6.3.3.3.3 | Time of Arrival (TOA)..... | 52 | +| 6.3.3.3.4 | Spare Extension..... | 52 | +| 6.3.3.4 | DL NODE SYNCHRONISATION ..... | 52 | +| 6.3.3.4.1 | Payload Structure ..... | 52 | +| 6.3.3.4.2 | T1 ..... | 53 | +| 6.3.3.4.3 | Spare Extension..... | 53 | +| 6.3.3.5 | UL NODE SYNCHRONISATION ..... | 53 | +| 6.3.3.5.1 | Payload Structure ..... | 53 | +| 6.3.3.5.2 | T1 ..... | 53 | +| 6.3.3.5.3 | T2 ..... | 53 | +| 6.3.3.5.4 | T3 ..... | 54 | +| 6.3.3.5.5 | Spare Extension..... | 54 | +| 6.3.3.6 | DYNAMIC PUSCH ASSIGNMENT [TDD]..... | 54 | +| 6.3.3.6.1 | Payload structure..... | 54 | +| 6.3.3.6.2 | PUSCH Set Id..... | 54 | +| 6.3.3.6.3 | Activation CFN ..... | 54 | +| 6.3.3.6.4 | Duration..... | 54 | +| 6.3.3.7 | DSCH TFCI SIGNALLING [FDD] ..... | 55 | +| 6.3.3.7.1 | Payload structure..... | 55 | +| 6.3.3.7.2 | TFCI (field 2) ..... | 55 | +| 6.3.3.7.3 | Spare Extension..... | 55 | +| 6.3.3.8 | TIMING ADVANCE [3.84Mcps and 7.68Mcps TDD]..... | 55 | +| 6.3.3.8.1 | Payload structure..... | 55 | +| 6.3.3.8.2 | CFN ..... | 55 | +| 6.3.3.8.3 | TA [3.84 Mcps]..... | 55 | +| 6.3.3.8.3A | TA [7.68 Mcps]..... | 55 | +| 6.3.3.8.4 | Spare Extension..... | 55 | +| 6.3.3.9 | OUTER LOOP POWER CONTROL [1.28 Mcps TDD]..... | 56 | +| 6.3.3.9.1 | Payload structure..... | 56 | +| 6.3.3.9.2 | SIR Target ..... | 56 | +| 6.3.3.9.3 | Spare Extension..... | 56 | +| 6.3.3.10 | HS-DSCH CAPACITY REQUEST ..... | 56 | +| 6.3.3.10.1 | Common Transport Channel Priority Indicator (CmCH-PI)..... | 56 | +| 6.3.3.10.2 | User Buffer Size ..... | 57 | +| 6.3.3.10.3 | Spare Extension..... | 57 | +| 6.3.3.11 | HS-DSCH CAPACITY ALLOCATION..... | 57 | +| 6.3.3.11.1 | Common Transport Channel Priority Indicator (CmCH-PI)..... | 58 | +| 6.3.3.11.2 | Maximum MAC-d PDU Length ..... | 58 | +| 6.3.3.11.3 | HS-DSCH Credits ..... | 58 | + +| | | | +|------------------------|------------------------------------------------------------------------|----| +| 6.3.3.11.4 | HS-DSCH Interval ..... | 58 | +| 6.3.3.11.5 | HS-DSCH Repetition Period..... | 58 | +| 6.3.3.11.6 | Spare Extension..... | 59 | +| 6.3.3.11.7 | Congestion Status..... | 59 | +| 6.3.3.11.8 | Maximum MAC-d/c PDU Length..... | 59 | +| 6.3.3.12 | HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE [1.28Mcps TDD] ..... | 59 | +| 6.3.3.12.1 | Payload structure ..... | 59 | +| 6.3.3.12.2 | H-RNTI ..... | 59 | +| 6.3.3.13 | HS-DSCH PDU DROP INDICATION ..... | 59 | +| 6.3.3.13.1 | Payload structure ..... | 59 | +| 6.3.3.13.2 | Drop Reason..... | 60 | +| 6.3.3.13.3 | PDU Index..... | 60 | +| 7 | Frame protocol error handling ..... | 60 | +| 7.1 | Error detection..... | 60 | +| 7.1.1 | CRC Calculation..... | 60 | +| 7.1.1.1 | Relation between input and output of the Cyclic Redundancy Check ..... | 61 | +| Annex A (informative): | Change History..... | 62 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides a description of the UTRAN RNC-Node B (Iub) interface user plane protocols for Common Transport Channel data streams as agreed within the TSG-RAN working group 3. + +NOTE: By Common Transport Channel one must understand RACH, FACH/PCH, DSCH, USCH [FDD – and 1.28Mcps TDD -, E-DCH for CELL\_FACH and Idle] and HS-DSCH. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2". +- [3] 3GPP TS 25.302: "Services provided by the Physical Layer". +- [4] 3GPP TS 25.221: "Physical channels and mapping of transport channels to physical channels (TDD)". +- [5] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [6] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". +- [7] Void +- [8] 3GPP TS 25.331: "Radio Ressource Control (RRC) protocol specification". +- [9] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". +- [10] 3GPP TS 25.214: " Physical layer procedures (FDD)". +- [11] 3GPP TS 25.401: "UTRAN overall description". +- [12] 3GPP TS 25.306: "UE Radio Access capabilities". +- [13] 3GPP TS 25.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams". +- [14] 3GPP TS 25.224: "Physical layer procedures (TDD)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions in TS 25.401 [11] and the following apply: + +**Transport Connection:** service provided by the transport layer and used by Frame Protocol for the delivery of FP PDU + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|--------------------------------------| +| CFN | Connection Frame Number | +| CRC | Cyclic Redundancy Checksum | +| CRCI | CRC Indicator | +| DCH | Dedicated Transport Channel | +| DL | Downlink | +| DRT | Delay Reference Time | +| DSCH | Downlink Shared Channel | +| E-DCH | Enhanced Dedicated Transport Channel | +| FP | Frame Protocol | +| FSN | Frame Sequence Number | +| FT | Frame Type | +| HSDPA | High Speed Downlink Packet Access | +| HS-DSCH | High Speed Downlink Shared Channel | +| MFN | Multicast Frame Number | +| PC | Power Control | +| PDSCH | Physical Downlink Shared Channel | +| PUSCH | Physical Uplink Shared Channel | +| QE | Quality Estimate | +| TB | Transport Block | +| TBS | Transport Block Set | +| TFI | Transport Format Indicator | +| TNL | Transport Network Layer | +| ToA | Time of Arrival | +| ToAWE | Time of Arrival Window Endpoint | +| ToAWS | Time of Arrival Window Startpoint | +| TTI | Transmission Time Interval | +| UL | Uplink | +| USCH | Uplink Shared Channel | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD] | This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. | +| [TDD] | This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. | +| [7.68Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. | +| [3.84Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. | +| [1.28Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. | + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD - ...] | This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. | +| [TDD - ...] | This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 7.68Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. | +| [7.68Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. | +| [3.84Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. | +| [1.28Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. | +| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Node Synchronisation procedure. | +| Frame | When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. TIMING ADJUSTMENT control frame. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Frame Type IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 6.2.7 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255". | + +# --- 4 General aspects + +## 4.1 Common Transport Channel Data Stream User Plane Protocol Services + +Common transport channel provides the following services: + +- Transport of TBS between the Node B and the CRNC for common transport channels. +- Support of transport channel synchronisation mechanism. +- Support of Node Synchronisation mechanism. + +## 4.2 Services expected from the Data Transport Network layer + +The following services are expected from the transport layer: + +- Delivery of Frame Protocol PDUs. + +In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and should be avoided. + +## 4.3 Protocol Version + +This revision of the specification specifies version 1 of the protocols. + +# 5 Data Streams User Plane Procedures + +## 5.1 Data Transfer + +### 5.1.1 RACH Channels + +Data Transfer procedure is used to transfer data received from Uu interface from Node B to CRNC. Data Transfer procedure consists of a transmission of Data Frame from Node B to CRNC. + +![Diagram of RACH Data Transfer procedure showing a RACH DATA FRAME being transmitted from Node B to CRNC.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` +graph LR; NodeB[Node B] -- "RACH DATA FRAME" --> CRNC[CRNC]; +``` + +The diagram illustrates the RACH Data Transfer procedure. It shows two entities, Node B and CRNC, represented by rectangular boxes. A horizontal arrow labeled "RACH DATA FRAME" points from Node B to CRNC. Below each entity box is a thick horizontal line representing a physical layer or interface. + +Diagram of RACH Data Transfer procedure showing a RACH DATA FRAME being transmitted from Node B to CRNC. + +Figure 1: RACH Data Transfer procedure + +### 5.1.2 CPCH Channels [FDD] + +Void. + +### 5.1.3 Secondary-CCPCH related transport Channels + +For the FACH transport channel, a Data Transfer procedure is used to transfer data from CRNC to Node B. Data Transfer procedure consists of a transmission of Data Frame from CRNC to Node B. + +![Diagram of FACH Data Transfer procedure showing a FACH DATA FRAME being transmitted from CRNC to Node B.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` +graph LR; CRNC[CRNC] -- "FACH DATA FRAME" --> NodeB[Node B]; +``` + +The diagram illustrates the FACH Data Transfer procedure. It shows two entities, Node B and CRNC, represented by rectangular boxes. A horizontal arrow labeled "FACH DATA FRAME" points from CRNC to Node B. Below each entity box is a thick horizontal line representing a physical layer or interface. + +Diagram of FACH Data Transfer procedure showing a FACH DATA FRAME being transmitted from CRNC to Node B. + +Figure 3: FACH Data Transfer procedure + +For the PCH transport channel, a Data Transfer procedure is used to transfer data from CRNC to Node B. Data Transfer procedure consists of a transmission of Data Frame from CRNC to Node B. + +![Diagram of PCH Data Transfer procedure showing a PCH DATA FRAME being transmitted from CRNC to Node B.](a7079ddb124df3f1ee13ae406c7c8982_img.jpg) + +``` +graph LR; CRNC[CRNC] -- "PCH DATA FRAME" --> NodeB[Node B]; +``` + +The diagram illustrates the PCH Data Transfer procedure. It shows two entities, Node B and CRNC, represented by rectangular boxes. A horizontal arrow labeled "PCH DATA FRAME" points from CRNC to Node B. Below each entity box is a thick horizontal line representing a physical layer or interface. + +Diagram of PCH Data Transfer procedure showing a PCH DATA FRAME being transmitted from CRNC to Node B. + +Figure 4: PCH Data Transfer procedure + +In this case the PCH DATA FRAME may also transport information related to the PICH channel. + +If the Node B does not receive a valid FP frame in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel. For the FACH and PCH transport channels, the TFS shall never define a Transport Block Size of zero bits. + +If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. When combining the TFI's of the different transport channels, a valid TFCI might result and in this case data shall be transmitted on the Uu. + +If the Node B is not aware of a TFI value corresponding to zero bits for this transport channel or if combining the TFI corresponding to zero bits with other TFI's results in an unknown TFI combination, the handling as described in the following paragraph shall be applied. + +At each frame, the Node B shall build the TFCI value of each secondary-CCPCH according to the TFIs of the transport channels multiplexed on this secondary-CCPCH and scheduled for that frame. [FDD - In case the Node B receives an unknown TFI combination, no pilot bits, TFCI bits or Data bits shall be transmitted.] [TDD - In case the Node B receives an unknown TFI combination, it shall apply DTX, i.e. suspend transmission on the corresponding S-CCPCH - except if this S-CCPCH provides the "beacon function", in which case the Node B shall maintain the physical layer transmission as specified in TS 25.221] [4]. + +If the Node B does not receive a valid FP frame in a TTI or a frame without paging indication information, it assumes that no UE's have to be paged on the Uu in this TTI. In this case the default PICH bit pattern of all zeros shall be transmitted. + +Data Frames sent on Iub for different transport channels multiplexed on one secondary-CCPCH might indicate different transmission power levels to be used in a certain Uu frame. Node-B shall determine the highest DL power level required for any of the transport channels multiplexed in a certain Uu frame and use this power level as the desired output level for the data. + +In the case there is no data (i.e. no TB in the FP frame or no FP frame) in any transport channel for a given TTI and a TFCI is defined for no transmission on all transport channels multiplexed on the S-CCPCH, the TFCI transmit power is unspecified. + +NOTE: It can be for example 0 or determined by the Node B relatively to $P_{\text{ref-nodata}} = \text{Min (PCH Power, Max FACH1 Power, Max FACH2 Power, ..., Max FACHn Power)}$ where PCH, FACH1, FACH2, ..., FACHn are the transport channels of the S-CCPCH [FDD, using the respective PO1 and PO3 offsets specified in TS 25.214 [10]]. + +### 5.1.4 Downlink Shared Channels [TDD] + +The Data Transfer procedure is used to transfer a DSCH DATA FRAME from the CRNC to a Node B. + +If the Node B does not receive a valid DSCH DATA FRAME for transmission in a given TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel. For the DSCH transport channel, the TFS shall never define a Transport Block Size of zero bits. + +The Node B shall use the header information in the DSCH DATA FRAME to determine which PDSCH Set [3.84Mcps and 7.68 Mcps TDD - and Transmit Power Level if no closed loop TPC power control is used] should be used in the PDSCH Uu frames associated to the specified CFN. The specified PDSCH Set [3.84Mcps and 7.68 Mcps TDD - and Transmit Power Level if no closed loop TPC power control is used] shall then be used for DSCH transmission for as long as there is data to transmit or until a new DSCH DATA FRAME arrives that specifies that a different PDSCH Set [3.84Mcps and 7.68 Mcps TDD - and/or Transmit Power Level if no closed loop TPC power control is used] should be used. This feature enables multiple DSCH's with different TTI to be supported. + +The Node B may receive a DSCH data frame which contains a TFI value corresponding to there being no data to transmit, such a DSCH DATA FRAME will have no transport blocks. On receiving such a DATA FRAME the Node B shall apply the specified PDSCH Set [3.84Mcps and 7.68 Mcps TDD - and Transmit Power Level if no closed loop TPC power control is used] as described above starting in the PDSCH Uu frame associated to the specified CFN. This feature enables multiple DSCH's with different TTI to be supported, the use of such a zero payload DSCH DATA FRAME solves the problem of how the Node B should determine what PDSCH Set [3.84Mcps and 7.68 Mcps TDD - and Transmit Power Level if no closed loop TPC power control is used] should be used in the event that transmission of a transport block set being transmitted with a short TTI comes to an end, whilst the transmission of a TBS with a long TTI continues. + +Data Frames sent on Iub for different DSCH transport channels multiplexed on one CCTrCH might indicate different transmission power levels to be used in a certain Uu frame. Node-B shall determine the highest DL power level required for any of the transport channels multiplexed in a certain Uu frame and use this power level as the desired output level. + +![Diagram of DSCH Data Transfer procedure showing a data frame being sent from CRNC to Node B.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram illustrates the DSCH Data Transfer procedure. It shows two entities, 'Node B' and 'CRNC', represented by rectangular boxes. Below each box is a horizontal line representing a ground or interface level. A horizontal arrow labeled 'DSCH DATA FRAME' points from the CRNC side to the Node B side, indicating the direction of data transfer. + +Diagram of DSCH Data Transfer procedure showing a data frame being sent from CRNC to Node B. + +Figure 5: DSCH Data Transfer procedure + +### 5.1.5 Uplink Shared Channels [TDD] + +Data Transfer procedure is used to transfer data received from Uu interface from Node B to CRNC. Data Transfer procedure consists of a transmission of Data Frame from Node B to CRNC. + +![Diagram of USCH Data Transfer procedure showing a data frame being sent from Node B to CRNC.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +The diagram illustrates the USCH Data Transfer procedure. It shows two entities, 'Node B' and 'CRNC', represented by rectangular boxes. Below each box is a horizontal line representing a ground or interface level. A horizontal arrow labeled 'USCH DATA FRAME' points from the Node B side to the CRNC side, indicating the direction of data transfer. + +Diagram of USCH Data Transfer procedure showing a data frame being sent from Node B to CRNC. + +Figure 6: USCH Data Transfer procedure + +Node B shall always send an USCH DATA FRAME to the CRNC provided the Transport Format addressed by the TFI indicates that the number of Transport Blocks is greater than 0. + +When UL synchronisation is lost or not yet achieved on the Uu, USCH DATA FRAMEs shall not be sent to the CRNC. + +When Node B receives an invalid TFCI in the PUSCH, USCH DATA FRAMEs shall not be sent to the CRNC. + +### 5.1.6 High Speed Downlink Shared Channels + +The Data Transfer procedure is used to transfer a HS-DSCH DATA FRAME (TYPE 1, TYPE 2 [FDD and 1.28Mcps TDD - or TYPE3]) from the CRNC to a Node B. HS-DSCH DATA FRAME TYPE 2 is selected if the IE *HS-DSCH MAC-d PDU Size Format* in NBAP (TS 25.433 [6]) is present and set to 'Flexible MAC-d PDU Size' [FDD and 1.28Mcps TDD - or if the IE *HS-DSCH Common System Information* is present and the UE is in Cell\_FACH state. HS-DSCH DATA FRAME TYPE 3 is selected if the IE *HS-DSCH Paging System Information* in NBAP (TS 25.433 [6]) is present and the UE is in Cell\_PCH state or URA\_PCH state]. HS-DSCH DATA FRAME TYPE 1 is selected in any other case. + +[FDD and 1.28Mcps TDD – Three types of HS-DSCH Frame Protocols exist for HS-DSCH data transfer procedure, i.e., HS-DSCH Frame Protocol TYPE 1 (including HS-DSCH DATA FRAME TYPE 1 and HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame), HS-DSCH Frame Protocol TYPE 2 (including HS-DSCH DATA FRAME TYPE 2 and HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame) and HS-DSCH Frame Protocol TYPE 3 (including HS-DSCH DATA FRAME TYPE 3).] + +[3.84Mcps TDD and 7.68 Mcps TDD – Two types of HS-DSCH Frame Protocols exist for HS-DSCH data transfer procedure, i.e., HS-DSCH Frame Protocol TYPE 1 (including HS-DSCH DATA FRAME TYPE 1 and HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame) and HS-DSCH Frame Protocol TYPE 2 (including HS-DSCH DATA FRAME TYPE 2 and HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame).] + +HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame shall be associated only with HS-DSCH DATA FRAME TYPE 1 while HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame shall be associated only with HS-DSCH DATA FRAME TYPE 2. HS-DSCH CAPACITY REQUEST Control Frame shall be used for both of HS- + +DSCH Frame Protocols. HS-DSCH Frame Protocol TYPE 2 is used for Flexible MAC-d PDU Size [FDD and 1.28Mcps TDD - and Enhanced Cell\_FACH Operation] as described in NBAP (TS 25.433 [6]). + +When the CRNC has been granted capacity by the Node B via the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame or via the HS-DSCH initial capacity allocation as described in TS 25.433 [6] and the CRNC has data waiting to be sent, then the HS-DSCH DATA FRAME (TYPE 1 or TYPE 2) is used to transfer the data. If the CRNC has been granted capacity by the Node B via the HS-DSCH initial capacity allocation as described in TS 25.433 [6], this capacity is valid for only the first HS-DSCH DATA FRAME (TYPE 1 or TYPE 2) transmission. If the HS-DSCH Frame Protocol TYPE 2 has been selected by the Node B, the granted capacity shall be interpreted as the total number of octets which is retrieved by multiplying the maximum MAC-d PDU [FDD and 1.28Mcps TDD - or MAC-c PDU] length (indicated by the *Maximum MAC-d/c PDU Length* IE) with the number of MAC-d PDUs [FDD and 1.28Mcps TDD - or MAC-c PDUs] (indicated by the *HS-DSCH Credits* IE). When data is waiting to be transferred, and a CAPACITY ALLOCATION (TYPE 1 or TYPE 2) is received, a DATA FRAME (TYPE 1 or TYPE 2) will be transmitted immediately according to allocation received. If the allocation received is >0 but less than the data waiting to be transferred, then the CRNC may send one HS-DSCH DATA FRAME TYPE 2 containing one MAC-d PDU [FDD - or MAC-c PDU] with a length up to the NBAP *Maximum MAC-d PDU Size Extended* [FDD and 1.28Mcps TDD - or *Maximum MAC-c PDU Size*] IE value. In such a case, the amount of data exceeding the allocated capacity for the first HS-DSCH Interval shall be credited from the following HS-DSCH Intervals, if available. + +In case of HS-DSCH Frame Protocol TYPE 1, multiple MAC-d PDUs of same length and same priority level (CmCH-PI) may be transmitted in one MAC-d flow in the same HS-DSCH DATA FRAME TYPE 1. + +In case of HS-DSCH Frame Protocol TYPE 2, MAC-d PDUs [FDD and 1.28Mcps TDD - or MAC-c PDUs] with the same logical channel ID shall be associated to one unique priority level (CmCH-PI). + +The HS-DSCH DATA FRAME (TYPE 1 and TYPE 2) includes a *User Buffer Size* IE to indicate the amount of data pending for the respective MAC-d flow for the indicated priority level. [FDD and 1.28Mcps TDD - The HS-DSCH DATA FRAME TYPE 2 includes PDUs for UE in Cell\_FACH includes a *User Buffer Size* IE to indicate the amount of data pending for the respective Common MAC flow for the indicated priority level.] Within one priority level (CmCH-PI) and size the MAC-d PDUs [FDD and 1.28Mcps TDD - or MAC-c PDUs] shall be transmitted by the Node B on the Uu interface in the same order as they were received from the CRNC. + +FDD - In case of HS-DSCH Frame Protocol TYPE 2 or TYPE 3 and when the UE is not in Cell\_DCH state, then (see TS 25.331 [8] and TS 25.321 [9]): + +- [FDD - When transmitting the MAC-ehs PDU on the Uu interface using the dedicated H-RNTI for DCCH/DTCH the Node B shall:] + - [FDD - if supported use the actual HS-DSCH physical layer category for MAC-ehs of the UE, or] + - [FDD - if the actual HS-DSCH physical layer category is not known to Node B or the usage of the actual UE category is not supported - use category 12 and limit the MAC-ehs PDU size to not more than 1572 bits, if supported] +- [FDD - When transmitting the MAC-ehs PDU on the Uu interface for other channels than BCCH and not using the dedicated H-RNTI the Node B shall if supported use the "Total number of soft channel bits" as defined for a UE of category 12 (see Table 5.1a in TS 25.306 [12])] +- [FDD - When transmitting the MAC-ehs PDU on the Uu interface for BCCH, the Node B shall, if supported, use category 12 and limit the MAC-ehs PDU size to 1572 bits.] + +If the *Flush* IE in the HS-DSCH DATA FRAME (TYPE 1 and TYPE 2) is set to "flush" the Node B should remove all MAC-d PDUs [FDD and 1.28Mcps TDD - or MAC-c PDUs] from the corresponding MAC-hs Priority Queue that have been received prior to this data frame on the same transport bearer. + +For the purpose of TNL Congestion Control on HSDPA, the *Frame Sequence Number* and the *DRT* IEs may be included by the CRNC. + +![Figure 6A: HS-DSCH Data Transfer procedure diagram](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +A sequence diagram showing the HS-DSCH Data Transfer procedure. It features two lifelines: Node B and CRNC. A message labeled 'HS-DSCH DATA FRAME' is sent from the CRNC to the Node B. Both lifelines have a solid vertical line extending downwards, representing the timeline of the entities. + +Figure 6A: HS-DSCH Data Transfer procedure diagram + +Figure 6A: HS-DSCH Data Transfer procedure + +### 5.1.7 E-DCH Channels for CELL\_FACH and Idle[FDD and 1.28Mcps TDD] + +The E-DCH Data Transfer procedure for CELL\_FACH and Idle is used to transfer an E-DCH DATA FRAME from the Node B to the CRNC. The E-DCH user-plane payload is transmitted using the E-DCH DATA FRAME only when some payload has been successfully received in same way as E-DCH Data Transfer procedure for Cell\_DCH defined in TS 25.427 [13], i.e., only silent mode defined in TS 25.427 [13] is used. + +![Figure 6B: E-DCH Enhanced Data Transfer procedure in CELL_FACH and Idle diagram](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +A sequence diagram showing the E-DCH Enhanced Data Transfer procedure in CELL\_FACH and Idle. It features two lifelines: Node B and CRNC. A message labeled 'E-DCH DATA FRAME' is sent from the Node B to the CRNC. Both lifelines have a solid vertical line extending downwards, representing the timeline of the entities. + +Figure 6B: E-DCH Enhanced Data Transfer procedure in CELL\_FACH and Idle diagram + +Figure 6B : E-DCH Enhanced Data Transfer procedure in CELL\_FACH and Idle + +## 5.2 Node Synchronisation + +In the Node Synchronisation procedure, the RNC sends a DL NODE SYNCHRONISATION control frame to Node B containing the parameter T1. Upon reception of a DL NODE SYNCHRONISATION control frame, the Node B shall respond with UL NODE SYNCHRONISATION control frame, indicating T2 and T3, as well as T1 which was indicated in the initiating DL NODE SYNCHRONISATION control frame. + +The T1, T2, T3 parameters are defined as: + +- T1: RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. +- T2: Node B specific frame number (BFN) that indicates the time when Node B receives the correspondent DL NODE SYNCHRONISATION control frame through the SAP from the transport layer. +- T3: Node B specific frame number (BFN) that indicates the time when Node B sends the frame through the SAP to the transport layer. + +The general overview on the Node Synchronisation procedure is reported in TS 25.402 [2]. + +The procedure shall not be applied on transport bearers with IP multicast option. + +![Figure 7: Node Synchronisation procedure diagram](220869911a1ecfa1dd4aa6d750319aad_img.jpg) + +A sequence diagram showing the Node Synchronisation procedure. It features two lifelines: Node B and CRNC. The first message is 'DL NODE SYNCHRONISATION' sent from the CRNC to the Node B. The second message is 'UL NODE SYNCHRONISATION' sent from the Node B to the CRNC. Both lifelines have a solid vertical line extending downwards, representing the timeline of the entities. + +Figure 7: Node Synchronisation procedure diagram + +Figure 7: Node Synchronisation procedure + +## 5.3 DL Transport Channels Synchronisation + +CRNC sends a DL SYNCHRONISATION control frame to Node B. This message indicates the target CFN. + +Upon reception of the DL SYNCHRONISATION control frame Node B shall immediately respond with UL SYNCHRONISATION control frame indicating the ToA for the DL SYNCHRONISATION control frame and the CFN indicated in the received message. + +The procedure shall not be applied on transport bearers transporting UL traffic channels RACH [FDD and 1.28Mcps TDD – , E-DCH for CELL\_FACH and Idle] or USCH. + +In case a CRNC sends DL SYNCHRONISATION control frame to Node B via IP multicast transport bearer, the target CFN indicates the target MFN. Upon reception of the DL SYNCHRONISATION control frame Node B shall immediately respond with UL SYNCHRONISATION control frame via one unicast transport bearer indicating the ToA for the DL SYNCHRONISATION control frame and the MFN indicated in the received message. + +In case a transport bearer without IP multicast option is used by several FACH channels, the procedure shall take place for all these FACH channels. + +![Diagram illustrating the Transport Channels Synchronisation procedure. It shows two entities, Node B and CRNC, represented by boxes. A horizontal arrow labeled 'DL SYNCHRONISATION' points from the CRNC box to the Node B box. Below this, a horizontal arrow labeled 'UL SYNCHRONISATION' points from the Node B box to the CRNC box. Both boxes have a thick black horizontal line at their base, representing the ground or a common reference line.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +Diagram illustrating the Transport Channels Synchronisation procedure. It shows two entities, Node B and CRNC, represented by boxes. A horizontal arrow labeled 'DL SYNCHRONISATION' points from the CRNC box to the Node B box. Below this, a horizontal arrow labeled 'UL SYNCHRONISATION' points from the Node B box to the CRNC box. Both boxes have a thick black horizontal line at their base, representing the ground or a common reference line. + +**Figure 8: Transport Channels Synchronisation procedure** + +## 5.4 DL Timing Adjustment + +Timing Adjustment procedure is used to indicate for the CRNC the incorrect arrival time of downlink data to Node B. + +Timing Adjustment procedure is initiated by the Node B if a DL frame arrives outside of the defined arrival window. + +If the DL frame has arrived before the ToAWS or after the ToAWE Node B includes the ToA and the target CFN as message parameters for TIMING ADJUSTMENT control frame. + +In case a transport bearer without IP multicast option is used by several FACH channels, the procedure shall take place for all these FACH channels. + +The arrival window and the time of arrival are defined as follows: + +- **Time of Arrival Window Endpoint (ToAWE):** ToAWE represents the time point by which the DL data shall arrive to the Node B from Iub. The ToAWE is defined as the amount of milliseconds before the last time point from which a timely DL transmission for the identified CFN would still be possible taking into account the Node B internal delays. ToAWE is set via control plane. If data does not arrive before ToAWE a TIMING ADJUSTMENT control frame shall be sent by Node B. +- **Time of Arrival Window Startpoint (ToAWS):** ToAWS represents the time after which the DL data shall arrive to the Node B from Iub. The ToAWS is defined as the amount of milliseconds from the ToAWE. ToAWS is set via control plane. If data arrives before ToAWS a TIMING ADJUSTMENT control frame shall be sent by Node B. +- **Time of Arrival (ToA):** ToA is the time difference between the end point of the DL arrival window (ToAWE) and the actual arrival time of DL frame for a specific CFN. A positive ToA means that the frame is received before the ToAWE, a negative ToA means that the frame is received after the ToAWE. + +The general overview on the timing adjustment procedure is reported in TS 25.402 [2]. + +![Figure 9: Timing Adjustment procedure diagram](8307f6b04df072c9332f9987e034272c_img.jpg) + +A sequence diagram showing the timing adjustment procedure. It features two vertical lifelines: 'Node B' on the left and 'CRNC' on the right. A horizontal arrow labeled 'TIMING ADJUSTMENT' points from the Node B lifeline to the CRNC lifeline. Both lifelines have a thick horizontal bar at the bottom, representing the physical layer. + +Figure 9: Timing Adjustment procedure diagram + +Figure 9: Timing Adjustment procedure + +## 5.5 Dynamic PUSCH Assignment [TDD] + +Procedure for dynamic allocation of physical resources to uplink shared channels (USCH) in the Node B. The control frame includes a parameter "PUSCH Set Id" which is a pointer to a pre-configured table of PUSCH Sets in the Node B. + +When this control frame is sent via a certain Iub USCH data port, then it applies to that USCH and in addition to any other USCH channel which is multiplexed into the same CCTrCH in the Node B. + +The time limitation of the PUSCH allocation is expressed with the parameters "Activation CFN" and "Duration". + +*Node B behaviour:* When the Node B receives the "DYNAMIC PUSCH ASSIGNMENT" from the CRNC in the USCH frame protocol over an Iub USCH data port within a Traffic Termination Point, it shall behave as follows: + +- 1) The Node B shall extract the PUSCH Set Id. +- 2) It shall extract the parameters "Activation CFN" and "Duration" which identify the allocation period of that physical channel. +- 3) It shall retrieve the PUSCH Set which is referred to by the PUSCH Set Id. +- 4) It shall identify the CCTrCH to which the USCH is multiplexed, and hence the TFCS which is applicable for the USCH. +- 5) Within the time interval indicated by Activation CFN and Duration, the Node B shall make the specified PUSCH Set available to the CCTrCH. + +![Figure 10: Dynamic PUSCH Assignment procedure diagram](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +A sequence diagram showing the dynamic PUSCH assignment procedure. It features two vertical lifelines: 'Node B' on the left and 'CRNC' on the right. A horizontal arrow labeled 'DYNAMIC PUSCH ASSIGNMENT' points from the CRNC lifeline to the Node B lifeline. Both lifelines have a thick horizontal bar at the bottom, representing the physical layer. + +Figure 10: Dynamic PUSCH Assignment procedure diagram + +Figure 10: Dynamic PUSCH Assignment procedure + +## 5.6 DSCH TFCI Signalling [FDD] + +Void. + +## 5.7 Timing Advance [3.84 Mcps and 7.68Mcps TDD] + +This procedure is used in order to signal to the Node B the adjustment to be performed by the UE in the uplink timing. + +The Node B shall use the CFN and timing adjustment values to adjust its layer 1 to allow for accurate impulse averaging. + +![Diagram of Timing Advance procedure](4356776ca004ecba5d599667a155d7d4_img.jpg) + +A sequence diagram showing the Timing Advance procedure. It features two vertical lifelines: 'Node B' on the left and 'CRNC' on the right. A horizontal arrow labeled 'TIMING ADVANCE' points from the CRNC lifeline to the Node B lifeline. Both lifelines have a thick horizontal bar at their base, representing the ground or a common time reference. + +Diagram of Timing Advance procedure + +Figure 12: Timing Advance procedure + +## 5.7A Outer Loop PC Information Transfer [1.28 Mcps TDD] + +Based, for example, on the CRCI values and on the quality estimate in the USCH data frames, CRNC modifies the SIR target of the associated CCTrCH by including the absolute value of the new SIR target in the OUTER LOOP PC control frame sent to the Node B. + +At the reception of the OUTER LOOP PC control frame from the CRNC via a Transport Bearer used for an USCH, the Node B shall immediately update the SIR target used for the inner loop power control for the respective CCTrCH with the specified value. + +The OUTER LOOP PC control frame can be sent via any of the transport bearers carrying USCHs which belong to the CCTrCH for which the UL SIR Target shall be adjusted. + +![Diagram of Outer Loop Power Control Information Transfer procedure](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +A sequence diagram showing the Outer Loop Power Control Information Transfer procedure. It features two vertical lifelines: 'NB' (Node B) on the left and 'CRNC' on the right. A horizontal arrow labeled 'OUTER LOOP PC' points from the CRNC lifeline to the NB lifeline. Both lifelines have a thick horizontal bar at their base, representing the ground or a common time reference. + +Diagram of Outer Loop Power Control Information Transfer procedure + +Figure 12A: Outer Loop Power Control Information Transfer procedure + +## 5.8 General + +### 5.8.1 Association between transport bearer and data/control frames + +Table 1 shows how the data and control frames are associated to the transport bearers. 'yes' indicates that the control frame is applicable to the transport bearer, 'no' indicates that the control frame is not applicable to the transport bearer. + +Table 1 + +| Transport bearer used for | Associated data frame | Associated control frames | | | | | | | | | +|------------------------------|---------------------------|---------------------------|---------------------------------------|----------------------|--------------------------|----------------|-----------------------------|--------------------------|------------------------------------|-----| +| | | Timing Adjustment | DL Transport Channels Synchronisation | Node Synchronisation | Dynamic PUSCH Assignment | Timing Advance | Outer Loop PC Info Transfer | HS-DSCH Capacity Request | HS-DSCH Capacity Allocation TYPE 1 | | +| RACH | RACH DATA FRAME | no | no | no | no | no | no | no | no | no | +| FACH | FACH DATA FRAME | yes | yes | yes 1 | no | no | no | no | no | no | +| PCH | PCH DATA FRAME | yes | yes | yes | no | no | no | no | no | no | +| DSCH | DSCH DATA FRAME | yes | yes | yes | no | no | no | no | no | no | +| USCH | USCH DATA FRAME | no | no | no | yes | yes | yes | no | no | no | +| HS-DSCH | HS-DSCH DATA FRAME TYPE 1 | no | no | yes | no | no | no | yes | yes | yes | +| HS-DSCH | HS-DSCH DATA FRAME TYPE 2 | no | no | yes | no | no | no | yes | no | no | +| HS-DSCH | HS-DSCH DATA FRAME TYPE 3 | yes | yes | yes | no | no | no | no | no | no | +| E-DCH for CELL FACH and Idle | E-DCH DATA FRAME | no | no | no | no | no | no | no | no | no | + +NOTE: 1: The associated control frame is not applicable to the transport bearer with IP multicast option. + +### 5.8.2 DSCH / USCH transport bearer replacement [TDD] + +As described in NBAP (TS 25.433 [6]), transport bearer replacement can be achieved for a DSCH or USCH by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure. The following steps can be discerned: + +- 1) The new transport bearer is established after which 2 transport bearers exist in parallel. +- 2) The transport channel(s) is/are switched to the new transport bearer. +- 3) The old transport bearer is released. + +#### DSCH transport bearer replacement, step 1: + +Communication on the old transport bearer continues as normal. In addition, the Node B shall support DSCH DATA FRAMES, the DL Transport Channel Synchronisation procedure (see sub-clause 5.3) and the DL Timing Adjustment procedure (see sub-clause 5.4) on the new bearer. This enables the CRNC to determine the timing on the new transport bearer. DSCH DATA FRAMES transported on the new transport bearer shall not be transmitted on the Uu Interface before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. + +#### USCH transport bearer replacement, step 1: + +Communication on the old transport bearer continues as normal. + +#### DSCH / USCH Transport Bearer Replacement step 2: + +Regarding step 2), the moment of switching is determined as follows: + +- The DSCH DATA FRAMEs or USCH DATA FRAMEs shall be transported on the new transport bearer from the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. + +Starting from this CFN the Node B shall support all applicable Common Transport Channels frame protocol procedures on the new transport bearer and no requirements exist regarding support of Common Transport Channels frame protocol procedures on the old transport bearer. + +#### **DSCH / USCH Transport Bearer Replacement step 3:** + +Finally in step 3), the old transport bearer is released. + +### **5.8.3 HS-DSCH Transport Bearer Replacement** + +As described in NBAP (TS 25.433 [6]), transport bearer replacement can be achieved for a HS-DSCH MAC-d Flow by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. In both cases the following steps can be discerned: + +- 1) The new transport bearer is established after which 2 transport bearers exist in parallel. +- 2) The HS-DSCH MAC-d Flow is switched to the new transport bearer. +- 3) The old transport bearer is released. + +#### **HS-DSCH Transport Bearer Replacement, step 1:** + +Communication on the old transport bearer continues as normal. In addition, the Node B shall support HS-DSCH DATA FRAMEs (TYPE 1 or TYPE 2), the HS-DSCH CAPACITY REQUEST Control Frame (see sub-clause 5.9) and may support the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame (see sub-clause 5.10) on the new transport bearer. HS-DSCH DATA FRAMEs (TYPE 1 or TYPE 2) transported on the new transport bearer shall be transmitted on the Uu Interface in the same way as those received on the old transport bearer (see sub-clause 5.1.6). + +The Node B may use the old or the new transport bearer for the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame. The HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame indicates the total amount of capacity granted for the MAC-d flow and the indicated priority level, irrespective of the transport bearer used. Any capacity previously granted is replaced. + +The RNC may use the old or the new transport bearer for the HS-DSCH CAPACITY REQUEST Control Frame. The rules for reissuing a HS-DSCH CAPACITY REQUEST Control Frame as outlined in sub-clause 5.9 still apply. + +#### **HS-DSCH Transport Bearer Replacement, step 2:** + +Regarding step 2), the moment of switching is determined as follows: + +Starting from the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message – or directly when using the unsynchronised Radio Link Reconfiguration procedure, the Node B shall support all applicable Common Transport Channels frame protocol procedures on the new transport bearer and no requirements exist regarding support of Common Transport Channels frame protocol procedures on the old transport bearer. + +#### **HS-DSCH Transport Bearer Replacement, step 3:** + +Finally in step 3), the old transport bearer is released. + +## 5.9 HS-DSCH Capacity Request + +![Diagram of HS-DSCH Capacity Request procedure. A CRNC box is on the right and a Node B box is on the left. A horizontal arrow labeled 'CAPACITY REQUEST' points from the CRNC to the Node B. Below each box is a solid black rectangle representing the physical layer or radio interface.](a3472689858b068ef469213682965325_img.jpg) + +Diagram of HS-DSCH Capacity Request procedure. A CRNC box is on the right and a Node B box is on the left. A horizontal arrow labeled 'CAPACITY REQUEST' points from the CRNC to the Node B. Below each box is a solid black rectangle representing the physical layer or radio interface. + +**Figure 12B: HS-DSCH Capacity Request procedure** + +The HS-DSCH Capacity Request procedure provides means for the CRNC to request HS-DSCH capacity by indicating the user buffer size in the CRNC for a given priority level. + +The CRNC is allowed to reissue the HS-DSCH Capacity Request if no CAPACITY ALLOCATION (TYPE 1 or TYPE 2) has been received within an appropriate time threshold. + +## 5.10 HS-DSCH Capacity Allocation + +![Diagram of HS-DSCH Capacity Allocation procedure. A Node B box is on the left and a CRNC box is on the right. A horizontal arrow labeled 'CAPACITY ALLOCATION' points from the Node B to the CRNC. Below each box is a solid black rectangle representing the physical layer or radio interface.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +Diagram of HS-DSCH Capacity Allocation procedure. A Node B box is on the left and a CRNC box is on the right. A horizontal arrow labeled 'CAPACITY ALLOCATION' points from the Node B to the CRNC. Below each box is a solid black rectangle representing the physical layer or radio interface. + +**Figure 12C: HS-DSCH Capacity Allocation procedure** + +HS-DSCH Capacity Allocation procedure is generated within the Node B. It may be generated either in response to a HS-DSCH Capacity Request or at any other time. + +The Node B may use this message to modify the capacity at any time, irrespective of the reported user buffer status. + +The HS-DSCH CAPACITY ALLOCATION (TYPE 1 and TYPE 2) Control Frame is used by the Node B to control the user data flow. In case of HS-DSCH Frame Protocol TYPE 1, the *HS-DSCH Credits* IE indicates the number of MAC-d PDUs that the CRNC is allowed to transmit for the MAC-d flow and the associated priority level indicated by the *Common Transport Channel Priority Indicator* IE. In case of HS-DSCH Frame Protocol TYPE 2, the *HS-DSCH Credits* IE multiplied by the *Maximum MAC-d/c PDU Length* IE indicates the number of MAC-d PDU [FDD and 1.28Mcps TDD – or MAC-c PDU] octets that the CRNC is allowed to transmit for the MAC-d flow [FDD and 1.28Mcps TDD - or Common MAC flow] and the associated priority level indicated by the *Common Transport Channel Priority Indicator* IE. + +The *Maximum MAC-d PDU Length* (in case of HS-DSCH Frame Protocol TYPE 1) or *Maximum MAC-d/c PDU Length* (in case of HS-DSCH Frame Protocol TYPE 2), *HS-DSCH Credits*, *HS-DSCH Interval* and *HS-DSCH Repetition Period* IEs indicates the total amount of capacity granted. Any capacity previously granted is replaced. + +If *HS-DSCH Credits* IE = 0 (e.g. due to congestion in the Node B), the CRNC shall immediately stop transmission of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs]. If *HS-DSCH Credits* IE = 2047 in case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame or 65535 in case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame, the CRNC can transmit MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] with unlimited capacity. + +The IEs used in the HS-DSCH CAPACITY ALLOCATION Control Frame (TYPE 1 and TYPE 2) are the *Common Transport Channel Priority Indicator*, *HS-DSCH Credits*, *Maximum MAC- d PDU Length* (in case of HS-DSCH Frame Protocol TYPE 1) or *Maximum MAC- d/c PDU Length* (in case of HS-DSCH Frame Protocol TYPE 2), *HS-DSCH Interval* and the *HS-DSCH Repetition Period*. + +If the *HS-DSCH Repetition Period* IE = "unlimited repetition period" it indicates that the CRNC may transmit the amount of granted capacity for an unlimited period according to the bounds of *Maximum MAC- d PDU Length* IE (TYPE 1) or *Maximum MAC- d/c PDU length* IE (TYPE 2), *HS-DSCH Credits* IE and *HS-DSCH Interval* IE. + +## 5.11 Indication of UE State Transition [1.28Mcps TDD] + +In 1.28Mcps TDD, for UE in CELL\_PCH state with dedicated H-RNTI, the network will inform the UE to establish the uplink synchronization via HS-SCCH before transmitting DCCH and DTCH to the UE. And when UE receives dedicated H-RNTI on HS-SCCH, the UE shall initiate the uplink synchronization procedure and transit to CELL\_FACH state. After the Node B received the confirmation from UE (upon detection of the UE's E-RUCCH), it shall send the UE State Transition Indication to RNC through E-DCH user data frame with dedicated E-RNTI to inform that the UE's state has been transited from CELL\_PCH to CELL\_FACH. + +The UE State Transition Indication is indicated in E-DCH user data frame with values set as follows: + +- The *CFN* and *Subframe Number* IE values shall reflect the time when the state transition was detected +- The *Number of MAC-is SDUs* IE shall be set to zero. As a consequence there are no *MAC-is PDU descriptor* IE and there are no *MAC-is PDUs* IEs in the payload part of the data frame related to UE state transition indication. + +## 5.12 HS-DSCH UL Synchronization Establishment Failure [1.28Mcps TDD] + +![Sequence diagram showing the HS-DSCH UL Synchronization Establishment Failure procedure. A Node B sends a message labeled 'HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE' to a CRNC. Both entities are represented by boxes with a black bar at the bottom.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +sequenceDiagram + participant Node B + participant CRNC + Note left of Node B: [Node B] + Note right of CRNC: [CRNC] + Node B->>CRNC: HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE + +``` + +Sequence diagram showing the HS-DSCH UL Synchronization Establishment Failure procedure. A Node B sends a message labeled 'HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE' to a CRNC. Both entities are represented by boxes with a black bar at the bottom. + +Figure 12D: HS-DSCH UL Synchronization Establishment Failure procedure + +In 1.28Mcps TDD, when the Node B needs to transmit HS-DSCH data to the UE in CELL\_FACH state, the Node B will inform the UE to establish the uplink synchronization via HS-SCCH before HS-DSCH data transmission (TS 25.224 [14]). During this uplink synchronization establishment procedure, if the uplink synchronization failure indication from lower layer is received (TS 25.224 [14]), the Node B could use the HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE control frame to notify the RNC to terminate the HS-DSCH data transmission. The *H-RNTI* IE contains the same value as the H-RNTI currently allocated to the UE. + +## 5.13 HS-DSCH PDU DROP INDICATION + +![Diagram of HS-DSCH PDU DROP INDICATION procedure. A box labeled 'Node B' is on the left, and a box labeled 'CRNC' is on the right. A horizontal arrow labeled 'DROP INDICATION' points from Node B to CRNC. Below each box is a solid black rectangle.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Diagram of HS-DSCH PDU DROP INDICATION procedure. A box labeled 'Node B' is on the left, and a box labeled 'CRNC' is on the right. A horizontal arrow labeled 'DROP INDICATION' points from Node B to CRNC. Below each box is a solid black rectangle. + +Figure 12E: HS-DSCH PDU DROP INDICATION procedure + +The HS-DSCH PDU DROP INDICATION Control Frame is used by the Node B to report to CRNC the PDU drop events. It is used when Node B drops the PDUs. The content of the dropped PDU or Data Frame is available in the Node B so in this case direct identification of the PDUs is possible. + +# 6 Frame Structure and Coding + +## 6.1 General + +The general structure of a Common Transport Channel frame consists of a header and a payload. This structure is depicted in figure 13. + +![](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +| | | +|---------------|---------------------------------------------| +| Header | Payload: Data or Control Information | +|---------------|---------------------------------------------| + +Figure 13: General Frame Structure + +The header shall contain the Frame Type field and information related to the frame type. + +There are two types of frames (indicated by the Frame Type field). + +- Data frame. +- Control frame. + +In the present document the structure of frames will be specified by using pictures similar to figure 14. + +![](b0e32f17c90ce1db73135488888ce558_img.jpg) + +| | | | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|----------|----------|-----------|----------------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Condition | Byte 1
Byte 2
Byte 3 | +| Field 1 | | | | | | Field 2 | | | | +| Field 3 | | | | | | | | | | +| Field 3 (cont) | | | | Field 4 | | | | | | +| Spare Extension | | | | | | | | | | + +Figure 14: Example frame structure + +Unless otherwise indicated, fields which consist of multiple bits within a byte will have the more significant bit located at the higher bit position (indicated above frame in figure 14). In addition, if a field spans several bytes, more significant bits will be located in lower numbered bytes (right of frame in figure 14). + +On the Iub interface, the frame will be transmitted starting from the lowest numbered byte. Within each byte, the bits are sent according decreasing bit position (bit position 7 first). + +The parameters are specified giving the value range and the step (if not 1). The coding is done as follows (unless otherwise specified): + +- Unsigned values are binary coded. + +- Signed values are 2's complement binary coded. + +The Spare Extension indicates the location where new IEs can in the future be added in a backward compatible way. The Spare Extension shall not be used by the transmitter and shall be ignored by the receiver. + +Bits labelled "Spare" shall be set to zero by the transmitter and shall be ignored by the receiver. + +## 6.2 Data frame structure + +### 6.2.1 RACH Channels + +The RACH DATA FRAME includes the CFN corresponding to the SFN of the frame in which the payload was received. If the payload was received in several frames, the CFN corresponding to the first Uu frame in which the information was received shall be indicated. + +![](26d664119ad25250780f554633444e54_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +|--------------------------------------------------------------|-------------|-----------------|---------------------------------------|-----------------|-------------|------------------------------------|-------------|--------------------------------------------------------------|---------| +| Header CRC | | | | | | | | FT | Header | +| CFN | | | | | | | | | | +| spare | | | TFI | | | | | | | +| Rx Timing Deviation | | | | | | | | Conditional FDD
Conditional 3.84 Mcps and
7.68Mcps TDD | | +| Received SYNC UL Timing Deviation | | | | | | | | Conditional
1.28Mcps TDD | | +| First TB | | | | | | | | | | +| First TB | | | | | | | | Pad | | +| Last TB | | | | | | | | | | +| Last TB | | | | | | | | Pad | | +| CRCI of first TB | | | | | | | | | | +| | | | | CRCI of last TB | Pad | | | | Payload | +| New IE FI 7(E) | New IE FI 6 | New IE FI 5 | New IE FI 4 | New IE FI 3 | New IE FI 2 | New IE FI 1 | New IE FI 0 | | | +| Spare 7-6 | | Cell Porting ID | | | | | | Conditional FDD | | +| Spare 7-1 bits for 3.84 Mcps
Spare 7-2 bits for 7.68 Mcps | | | | | | Rx Timing Deviation (continuation) | | Conditional
3.84Mcps or
7.68Mcps | | +| Spare 7-2 | | | | | | Ext Propagation Delay | | Conditional FDD | | +| Ext Propagation Delay | | | | | | | | Conditional FDD | | +| Spare 7-2 | | | | | | AOA | | Conditional
1.28Mcps | | +| AOA | | | | | | | | Conditional
1.28Mcps | | +| Spare 7-5 | | | Ext Received SYNC UL Timing Deviation | | | | | Conditional
1.28Mcps | | +| Ext Received SYNC UL Timing Deviation | | | | | | | | Conditional
1.28Mcps | | +| Cell Portion LCR ID | | | | | | | | Conditional
1.28Mcps | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | + +Figure 15: RACH DATA FRAME structure + +*Propagation Delay* is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a FDD Cell. + +*Rx Timing Deviation* is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a 3.84 Mcps or 7.68Mcps TDD Cell. + +*Received SYNC UL Timing Deviation* is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a 1.28Mcps TDD Cell. The RNC shall ignore this IE if the measured Received SYNC UL Timing Deviation is sent in Ext Received SYNC UL Timing Deviation IE + +With respect to new IEs, for which the presence is indicated by the *New IE Flags* IE, the Figure 15 is an example of how a frame is structured when all such new IEs are present. Note that non-presence of such a new IE changes the position of all subsequent IEs on octet level. + +[FDD- Bit 0 of New IE Flags in RACH DATA FRAME indicates if a Cell Portion ID is present (1) or not present (0) in the byte (bits 0-5) following the *New IE Flags* IE.] + +[FDD - Bit 1 of New IE Flags in RACH DATA FRAME indicates if *Ext Propagation Delay* IE is present (1) or not present (0)] + +[FDD - Bits 2 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0.] + +[FDD - Field length of *Spare Extension* IE in RACH DATA FRAME is 0-28 octets.] + +[3.84 Mcps and 7.68 Mcps TDD - Bit 0 of New IE Flags in RACH DATA FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0. Field length of *Spare Extension* IE in RACH DATA FRAME is 0-30 octets.] + +[1.28Mcps TDD - Bit 0 of New IE Flags in RACH DATA FRAME indicates if the *AOA* IE is present (1) or not present (0).] + +[1.28Mcps TDD - Bit 1 of New IE Flags in RACH DATA FRAME indicates if *Ext Received SYNC UL Timing Deviation* IE is present (1) or not present (0).] + +[1.28Mcps TDD - Bit 2 of New IE Flags in RACH DATA FRAME indicates if *Cell Portion LCR* IE is present (1) or not present (0).] + +[1.28Mcps TDD – Bits 3 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0.] + +[1.28Mcps TDD – Field length of *Spare Extension* IE in RACH DATA FRAME is 0-26 octets.] + +### 6.2.2 CPCH Channels [FDD] + +Void. + +### 6.2.3 FACH Channels + +FACH DATA FRAME includes the CFN corresponding to the Uu frame at which this data in which the payload (FACH TBS) has to be transmitted. If the payload is to be sent in several frames, the CFN corresponding to the first frame shall be indicated. In case a transport bearer is used by several FACH channels, the CFN and Transmit power level are valid for all these FACH channels. + +![](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +| | | | | | | | | | | +|----------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|--------|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| Header CRC | | | | | | | FT | Header | | +| CFN | | | | | | | | | Payload | +| Spare | | | TFI | | | | | | | +| Transmit power level | | | | | | | | | | +| First TB | | | | | | | | | | +| First TB | | | | | | | Pad | | | +| Last TB | | | | | | | | | | +| Last TB | | | | | | | Pad | | | +| New IE FI
7(E) | New IE FI
6 | New IE FI
5 | New IE FI
4 | New IE FI
3 | New IE FI
2 | New IE FI
1 | New IE FI
0 | | | +| Spare 7 -2 | | | | | | AOA | | | | +| AOA | | | | | | | | | | +| Cell Portion LCR ID | | | | | | | | | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC( cont) | | | | | | | | | | + +Conditional +1.28Mcps TDD + +**Figure 17: FACH DATA FRAME structure** + +[1.28Mcps TDD - Bit 0 of New IE Flags in FACH DATA FRAME indicates if the *AOA* IE is present (1) or not present (0).] + +[1.28Mcps TDD - Bit 1 of New IE Flags in FACH DATA FRAME indicates if Cell Portion LCR ID IE is present (1) or not present (0).] + +[1.28Mcps TDD – Field length of Spare Extension IE in FACH DATA FRAME is 0-29 octets.] + +### 6.2.4 PCH Channels + +The PCH DATA FRAME includes the paging indication information and paging messages [FDD - To page one User Equipment, two consecutive PCH DATA FRAMEs with consecutive CFN numbers are transmitted, the first frame contains the Paging Indication Information and the second contains the Paging Message.] [TDD – To page one User Equipment, one or more PCH DATA FRAMEs are transmitted.] + +[TDD - If two or more consecutive frames are used, the first frame contains the Paging Indication Information and the rest contain the Paging Messages. If PI-bitmap and PCH TBS are both transmitted within the PCH DATA FRAME, the CFN is related to the PCH TBS only. The PI bitmap is mapped to the PICH frames, transmitted at the beginning of the paging block.] + +The paging messages are transmitted in S-CCPCH frames. The CFN in the PCH DATA FRAME header corresponds to the Cell SFN of the frame in which the start of the S-CCPCH frame is located. [TDD - If the paging messages are to be sent in several frames, the CFN corresponding to the first frame shall be indicated.] + +[FDD - The timing of the PICH frame (containing the paging indication information) is $\tau_{PICH}$ prior to the S-CCPCH frame timing (TS 25.211 [5]).] + +In contrast to all other Common Transport Channel data frames, which use a CFN of length 8, the PCH DATA FRAME includes a CFN of length 12. + +The Node B has no responsibility to ensure the consistency between the paging indication information and the corresponding paging messages. E.g. if the paging indication information is lost over the Iub, the paging messages might be sent over the Uu while no UE is actually listening. + +![](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +| | | | | | | | | +|--------------------|---|---|----------|---|---|---|-----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Header CRC | | | | | | | FT | +| CFN | | | | | | | | +| CFN (cont) | | | Not Used | | | | PI | +| Spare | | | TFI | | | | | +| PI-bitmap | | | | | | | | +| PI-bitmap | | | | | | | Pad | +| First TB | | | | | | | | +| First TB | | | | | | | Pad | +| Last TB | | | | | | | | +| Last TB | | | | | | | Pad | +| Spare Extension | | | | | | | | +| Payload CRC | | | | | | | | +| Payload CRC( cont) | | | | | | | | + +Header + +Payload + +Figure 18: PCH DATA FRAME structure + +"Not Used" bits shall be set to 0 by the RNC and ignored by the Node B. + +### 6.2.5 Downlink Shared Channels [TDD] + +DSCH DATA FRAME includes a CFN indicating the SFN of the PDSCH in which the payload shall be sent. If the payload is to be sent over several frames, the CFN corresponding to the first frame shall be indicated. + +![](4af57aad638888edf2062306f8a54a6c_img.jpg) + +| | | | | | | | | +|----------------------|---|---|-----|---|---|---|-----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Header CRC | | | | | | | FT | +| CFN | | | | | | | | +| Spare | | | TFI | | | | | +| PDSCH Set Id | | | | | | | | +| Transmit power level | | | | | | | | +| First TB | | | | | | | | +| First TB | | | | | | | Pad | +| Last TB | | | | | | | | +| Last TB | | | | | | | Pad | +| Spare Extension | | | | | | | | +| Payload CRC | | | | | | | | +| Payload CRC( cont) | | | | | | | | + +Header + +Payload + +Figure 20: DSCH DATA FRAME structure + +### 6.2.6 Uplink Shared Channels [TDD] + +USCH DATA FRAME includes the CFN in which the payload was received. If the payload was received in several frames, the CFN corresponding to the first frame will be indicated. + +![](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +| | | | | | | | | | | +|------------------------------------------------------------|-------------|-------------|-------------|-----------------|-------------|------------------------------------|-------------|--------|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| Header CRC | | | | | | | FT | Header | | +| CFN | | | | | | | | | Payload | +| Spare | | | TFI | | | | | | | +| Rx Timing Deviation | | | | | | | | | | +| First TB | | | | | | | | | | +| First TB | | | | | | | Pad | | | +| Last TB | | | | | | | | | | +| Last TB | | | | | | | Pad | | | +| QE | | | | | | | | | | +| CRCI of first TB | | | | | | | | | | +| | | | | CRCI of last TB | Pad | | | | | +| New IE FI 7(E) | New IE FI 6 | New IE FI 5 | New IE FI 4 | New IE FI 3 | New IE FI 2 | New IE FI 1 | New IE FI 0 | | | +| Spare 7-1 bits for 3.84Mcps
Spare 7-2 bits for 7.68Mcps | | | | | | Rx Timing Deviation (continuation) | | | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC( cont) | | | | | | | | | | + +Figure 21: USCH DATA FRAME structure + +[3.84 Mcps and 7.68 Mcps TDD - Field length of *Spare Extension* IE in USCH DATA FRAME is 0-30 octets. + +Bit 0 of New IE Flags in USCH DATA FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in USCH DATA FRAME shall be set to 0.] + +### 6.2.6A HS-DSCH Channels + +[FDD and 1.28Mcps TDD - Three types of HS-DSCH DATA FRAME exist for the HS-DSCH data transfer, i.e. HS-DSCH DATA FRAME TYPE 1, HS-DSCH DATA FRAME TYPE 2 and HS-DSCH DATA FRAME TYPE 3.] + +[3.84Mcps and 7.68Mcps TDD - Two types of HS-DSCH DATA FRAME exist for the HS-DSCH data transfer, i.e. HS-DSCH DATA FRAME TYPE 1 and HS-DSCH DATA FRAME TYPE 2.] + +![](dd5771673aececa53d42ece89218299d_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | +|-----------------------------|-------------------|-------------------|-------------------|-------------------|-------------------|----------------------|-------------------|--------|---------|--| +| Header CRC | | | | | | | | FT | | | +| Frame Seq Nr | | | | CmCH-PI | | | | | | | +| MAC -d PDU Length | | | | | | | | | | | +| MAC -c/sh SDU Length (cont) | | | | | Flush | FSN/
DRT
Reset | CPC
Recov | Header | | | +| Num Of PDUs | | | | | | | | | | | +| User Buffer Size | | | | | | | | | | | +| User Buffer Size (cont) | | | | | | | | | | | +| Spare, bits 7-4 | | | | MAC-d PDU-1 | | | | | | | +| MAC -d PDU 1 (cont) | | | | | | | | | Pad | | +| | | | | | | | | | | | +| Spare, bits 7-4 | | | | MAC-d PDU-n | | | | | Payload | | +| MAC -d PDU n (cont) | | | | | | | | Pad | | | +| New
IE FI
7(E) | New
IE FI
6 | New
IE FI
5 | New
IE FI
4 | New
IE FI
3 | New
IE FI
2 | New
IE FI
1 | New
IE FI
0 | | | | +| DRT | | | | | | | | | | | +| DRT (cont) | | | | | | | | | | | +| SN | | | | | | | | | | | +| SN(cont) | | | | | | | | S/D | | | +| SN | | | | | | | | | | | +| SN(cont) | | | | | | | | S/D | | | +| Spare Extension | | | | | | | | | | | +| Payload CRC | | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | | + +**Figure 21A: HS-DSCH DATA FRAME TYPE 1 structure** + +Bit 0 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 indicates if a DRT is present (1) or not (0) in the 2 octets following the *New IE Flags* IE. Bit 1 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 indicates if SN is present (1) or not (0) in the third and the forth octets following the *New IE Flags* IE. Bit 0 in the forth octet is allocated for IE S/D. Bit 2 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 indicates if SN is present (1) or not (0) in the fifth and the sixth octets following the *New IE Flags* IE. Bit 0 in the sixth octet is allocated for IE S/D. Bits 3 through 6 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 shall be set to 0. + +Field length of *Spare Extension* IE in HS-DSCH DATA FRAME TYPE 1 is 0-25 octets. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | +|---------------------------------|-----------------------|----------------------|-------------------|------------------------------|----------------------|----------------------|-------------------|--|--|--|--|--|--| +| Header CRC | | | | | | | FT | | | | | | | +| Frame Seq Nr | | | | CmCH-PI | | | | | | | | | | +| Total Num of PDU blocks | | | | Flush | FSN/
DRT
Reset | DRT
Indica
tor | | | | | | | | +| FI | eDRX
Indica
tor | TSO
indica
tor | MI | CPC
Recov | Spare 2-0 | | | | | | | | | +| User Buffer Size | | | | | | | | | | | | | | +| User Buffer Size (cont) | | | | | | | | | | | | | | +| MAC-d PDU length in block 1 | | | | | | | | | | | | | | +| M len 1 (cont) | Spare | | #PDUs in block 1 | | | | | | | | | | | +| Logical CH ID block1 | | | | MAC-d PDU length in block 2 | | | | | | | | | | +| M len 2 (cont) | | | | | | | Spare | | | | | | | +| #PDUs in block2 | | | | Logical Ch ID in block2 | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC -d PDU length in block n | | | | | | | | | | | | | | +| M len n (cont) | Spare | | #PDUs in block n | | | | | | | | | | | +| Logical CH ID block n | | | | Padding if n is odd | | | | | | | | | | +| DRT | | | | | | | | | | | | | | +| DRT (cont) | | | | | | | | | | | | | | +| H-RNTI | | | | | | | | | | | | | | +| H-RNTI (cont) | | | | | | | | | | | | | | +| RACH Measurement Result | | | | | | | | | | | | | | +| MAC-d/c PDU 1 | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC-d/c PDU 1 (cont) | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC-d/c PDU m1 | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC-d/c PDU m1 (cont) | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC-d/c PDU 1 | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| MAC-d/c PDU mn (cont) | | | | | | | | | | | | | | +| New
IE FI
7(E) | New
IE FI
6 | New
IE FI
5 | New
IE FI
4 | New
IE FI
3 | New
IE FI
2 | New
IE FI
1 | New
IE FI
0 | | | | | | | +| New
IE FI
7(E) | New
IE FI
6 | New
IE FI
5 | New
IE FI
4 | New
IE FI
3 | New
IE FI
2 | New
IE FI
1 | New
IE FI
0 | | | | | | | +| Dedicated H-RNTI | | | | | | | | | | | | | | +| Dedicated H-RNTI (cont) | | | | | | | | | | | | | | +| E-RNTI | | | | | | | | | | | | | | +| E-RNTI (cont) | | | | | | | | | | | | | | +| HS-DSCH physical layer category | | | | | | EI | spare | | | | | | | +| SN | | | | | | | | | | | | | | +| SN (cont) | | | | | | | S/D | | | | | | | +| SN | | | | | | | | | | | | | | +| SN (cont) | | | | | | | S/D | | | | | | | +| Fed
RX
Indica
tor | NTHT | CR
Ind | OPCE
Ind | HS-SCCH
DRX
Indication | Spare 2-0 | | | | | | | | | +| CFN | | | | | | | | | | | | | | +| Spare Extension | | | | | | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | | | | | + +Header + +First block of PDUs +with the same size + +Payload + +nth block of PDUs +with the same size + +###### Figure 21B: HS-DSCH DATA FRAME TYPE 2 structure + +[FDD and 1.28Mcps TDD - Bit 0 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the *Dedicated H-RNTI* IE and the *E-RNTI* IE is present (1) or not (0) in the 4 octets following the *New IE Flags* IE. Bit 1 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the HS-DSCH physical layer category [FDD] is present (1) or not (0) in the 5th octet following the *New IE Flags* IE.] + +[FDD – Bit 2 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the EI is present (1) or not (0).] + +[FDD – Bit 3 of 1st New IE Flags in HS-DSCH DATA FRAME TYPE2 indicates if SN and S/D is present (1) or not (0).] + +[FDD – Bit 4 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE2 indicates if SN and S/D is present (1) or not (0).] + +[FDD – Bit 5 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the FeDRX Indication is present (1) or not (0).] + +[FDD – Bit 6 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the NodeB Triggered HS-DPCCH Transmission (NTHT) is present (1) or not (0).] + +[FDD – Bit 7 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 is present (1) or not (0), and if present, then:] + +[FDD – Bit 0 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the CFN is present (1) or not (0).] + +[FDD – Bit 1 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the Cell Reselection Indication (CR Ind) IE is present (1) or not (0).] + +[FDD – Bit 2 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the Operation Preference of Common E-DCH resource Indication (OPCE Ind) is present (1) or not (0).] + +[FDD - Bit 3 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the HS-SCCH DRX Indication is present (1) or not (0). Bits 4 through 6 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 shall be set to 0.] + +With respect to new IEs, for which the presence is indicated by the *New IE Flags* IE, the Figure 21B is an example of how a frame is structured when all such new IEs are present. Note that non-presence of such a new IE changes the position of all subsequent IEs on octet level. + +[FDD and 1.28Mcps TDD - Field length of *Spare Extension* IE in HS-DSCH DATA FRAME TYPE 2 is 0-20 octets.] + +[FDD – If the received *H-RNTI* IE sets to same value as the *BCCH Specific HS-DSCH RNTI* IE configured in NBAP (TS 25.433 [6]), the Node B shall ignore *RACH Measurement Result* IE in the frame.] + +[FDD – If the received *H-RNTI* IE sets to same value as the *BCCH Specific HS-DSCH RNTI Information* IE configured in NBAP (TS 25.433 [6]), the Node B should not calculate FACH measurement occasion for scheduling the data in the frame.] + +[FDD – If the received *H-RNTI* IE sets to same value as the *Common HS-DSCH RNTI Information* IE configured in NBAP (TS 25.433 [6]), the Node B should not calculate FACH measurement occasion for scheduling the data in the frame.] + +[FDD – The CFN corresponding to the SFN of the frame in which the payload was received on Uplink. If the payload was received in several frames, the CFN corresponding to the last Uu frame in which the information was received shall be indicated.] + +[1.28Mcps TDD - If the received *H-RNTI* IE sets to the same value as the *BCCH Specific HS-DSCH RNTI* IE configured in NBAP (TS 25.433 [6]), the Node B shall ignore *RACH Measurement Result* IE in the frame.] + +[FDD and 1.28Mcps TDD – when a UE using E-DCH for CELL\_FACH and Idle is provided with a new H-RNTI and/or a new E-RNTI signalled to the UE in the RRC message contained in this HS-DSCH data frame, the *Dedicated H-RNTI* IE and the *E-RNTI* IE contains the values to be used after successful execution of the RRC procedure (TS + +25.331 [8]). The *H-RNTI* IE either contains the same value as the *BCCH Specific HS-DSCH RNTI* IE configured in NBAP (TS 25.433 [6]) or the H-RNTI currently allocated to the UE.] + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | +|---------------------------------|-------------------|-------------------|-------------------------|-------------------|----------------------|----------------------|-------------------|-----|--|--|--|--|--|--|--| +| Header CRC | | | | | | | | FT | | | | | | | | +| CFN | | | | | | | | | | | | | | | | +| CFN (cont) | | | | Frame Seq Nr | | | | | | | | | | | | +| Total Num of PDU blocks | | | | HI | FSN/
DRT
Reset | DRT
Indica
tor | | | | | | | | | | +| MAC-d/c PDU length in block 1 | | | | | | | | | | | | | | | | +| M len 1 (cont) | | Spare | #PDUs in block 1 | | | | | | | | | | | | | +| Logical CH ID block1 | | | M len 2 | | | | | | | | | | | | | +| MAC-d PDU length in block 2 | | | | | | | Spare | | | | | | | | | +| #PDUs in block2 | | | Logical Ch ID in block2 | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC -d PDU length in block n | | | | | | | | | | | | | | | | +| M len n (cont) | | Spare | #PDUs in block n | | | | | | | | | | | | | +| Logical CH ID block n | | | Padding if n is odd | | | | | | | | | | | | | +| DRT | | | | | | | | | | | | | | | | +| DRT (cont) | | | | | | | | | | | | | | | | +| H-RNTI | | | | | | | | | | | | | | | | +| H-RNTI (cont) | | | | | | | | | | | | | | | | +| CmCH-PI | | | Not Used | | | PI | | | | | | | | | | +| PI-bitmap | | | | | | | | | | | | | | | | +| PI-bitmap | | | | | | | | Pad | | | | | | | | +| MAC-d/c PDU 1 | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC-d/c PDU 1 (cont) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC-d/c PDU m1 | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC-d/c PDU m1 (cont) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC-d/c PDU 1 | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | +| MAC-d/c PDU mn (cont) | | | | | | | | | | | | | | | | +| New
IE FI
7(E) | New
IE FI
6 | New
IE FI
5 | New
IE FI
4 | New
IE FI
3 | New
IE FI
2 | New
IE FI
1 | New
IE FI
0 | | | | | | | | | +| HS-DSCH physical layer category | | | | | EI | NTHT | | | | | | | | | | +| Spare 7-1 | | | | | | MUI | | | | | | | | | | +| Extended for UE2 | | | | | | | | | | | | | | | | +| Spare Extension | | | | | | | | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | | | | | | | + +Notes in this column apply only when MUI=1 + +all IEs are common for all UEs + +all IEs are dedicated for UE1 except FSN/DRT Reset and DRT Indicator + +all IEs are common for all UEs + +all IEs are dedicated for UE1 + +all IEs are common for all UEs + +all IEs are dedicated for UE1 + +Extension for UE2 + +all IEs are common for all UEs + +Header + +Payload + +First block of PDUs with the same size + +nth block of PDUs with the same size + +Figure 21C: HS-DSCH DATA FRAME TYPE 3 structure [FDD and 1.28Mcps TDD only] + +![](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +|---------------------------------|-------------|-------------|-------------|-------------------------|------------------|-------------|-------------|--------------------------------------------|--| +| Total Num of PDU blocks | | | | | HI | Spare | | Notes in this column apply only when MUI=1 | | +| MAC-d/c PDU length in block 1 | | | | | | | | | | +| M len 1 (cont) | | | Spare | | #PDUs in block 1 | | | | | +| Logical CH ID block1 | | | | M len 2 | | | | | | +| MAC-d PDU length in block 2 | | | | | | | Spare | | | +| #PDUs in block2 | | | | Logical Ch ID in block2 | | | | | | +| | | | | | | | | | | +| MAC -d PDU length in block n | | | | | | | | | | +| M len n (cont) | | | Spare | | #PDUs in block n | | | | | +| Logical CH ID block n | | | | Padding if n is odd | | | | | | +| H-RNTI | | | | | | | | | | +| H-RNTI (cont) | | | | | | | | | | +| CmCH-PI | | | | Spare | | | | | | +| MAC-d/c PDU 1 | | | | | | | | | | +| | | | | | | | | | | +| MAC-d/c PDU 1 (cont) | | | | | | | | | | +| | | | | | | | | | | +| MAC-d/c PDU m1 | | | | | | | | First block of PDUs with the same size | | +| | | | | | | | | | | +| MAC-d/c PDU m1 (cont) | | | | | | | | | | +| | | | | | | | | | | +| | | | | | | | | | | +| MAC-d/c PDU 1 | | | | | | | | nth block of PDUs with the same size | | +| | | | | | | | | | | +| MAC-d/c PDU mn (cont) | | | | | | | | | | +| New IE FI 7(E) | New IE FI 6 | New IE FI 5 | New IE FI 4 | New IE FI 3 | New IE FI 2 | New IE FI 1 | New IE FI 0 | | | +| HS-DSCH physical layer category | | | | | | EI | NTHT | | | +| Spare 7-1 | | | | | | | MUI | | | +| Extended for UE(n+1) | | | | | | | | Extension for UE(n+1) | | +| Spare Extension | | | | | | | | | | + +**Figure 21C-1: Extended for UEn in HS-DSCH DATA FRAME TYPE 3 structure [FDD only]** + +[FDD - The CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the HS-SCCH frame is located. The timing of the PICH frame (containing the paging indication information) is the same as the HS-SCCH frame timing (TS 25.211 [5]).] + +[1.28Mcps TDD - In case *Total Number of PDU blocks* IE is not set to 0, or *Total Number of PDU blocks* IE is set to 0 and *Paging Indication (PI)* IE is set to 0, i.e. PI-bitmap not present in payload, the CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the HS-SCCH frame is located. The timing of the PICH frame (containing the paging indication information) is $N_{GAP}$ prior to the HS-SCCH or the HS-PDSCH frame timing (TS 25.221 [4]).] + +[1.28Mcps TDD –In case *Total Number of PDU blocks* IE is set to 0 and *Paging Indication (PI)* IE is set to 1, i.e. PI-bitmap present in payload, the CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the PICH frame]. + +[1.28Mcps TDD - If PI-bitmap and MAC-c PDU are both transmitted within the HS-DSCH DATA FRAME TYPE 3, the CFN is related to the MAC-c PDU only. The PI bitmap is mapped to the PICH frames, transmitted at the beginning of the paging block.] + +[FDD and 1.28Mcps TDD - Note: The HS-SCCH frame is not sent if *HI* IE is set to 0, i.e. H-RNTI not present.] + +[FDD - Bit 0 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if the HS-DSCH physical layer category is present (1) or not (0) in the 1st octet following the *New IE Flags* IE. Bit 1 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if *EI* [FDD] is present (1) or not (0) in the 1st octet following the New IE Flags IE. Bit 2 of + +New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if NodeB Triggered HS-DPCCH Transmission (NTHT) [FDD] is present (1) or not (0) in the 1st octet following the *New IE Flags* IE. Bit 3 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if Multiple UEs Indicator (MUI) is present (1) or not (0) in the 2nd octet following the *New IE Flags* IE. Bits 4 through 6 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 shall be set to 0.] + +[FDD - Note: When MUI is used, data of number of UEs carried in one HS-DSCH DATA FRAME TYPE 3 should be considered, in order to avoid too many UEs being scheduled in one CFN in NodeB.] + +[FDD - Field length of *Spare Extension* IE in HS-DSCH DATA FRAME TYPE 3 is 0-30 octets.] + +### 6.2.6B E-DCH Channels for CELL\_FACH and Idle[FDD and 1.28Mcps TDD] + +The structure of the E-DCH DATA FRAME is shown in Figure 21D. This frame structure is used for carrying MAC-is PDUs in Cell\_FACH and Idle UE state (TS 25.321 [9]) for one UE. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | +|-----------------------------------------------------------|---------------------------------|-------------|---------------------------------------|----------------------------|-------------|----------------|-------------|--|--|--|--|--|--|--| +| Header CRC | | | | | | | FT | | | | | | | | +| Header CRC (cont) | | | | FSN | | | | | | | | | | | +| Spare | | | | Number of subframes | | | | | | | | | | | +| CFN | | | | | | | | | | | | | | | +| E-DCH User Buffer Size (eUB Size) | | | | | | | | | | | | | | | +| E-DCH User Buffer Size (eUB Size) | | | | | | | | | | | | | | | +| eUB Size | Spare | | | Nr. of MAC-is SDU in frame | | | | | | | | | | | +| Nr of MAC-is SDU in frame(cont) | | | | | | | | | | | | | | | +| E-RNTI | | | | | | | | | | | | | | | +| E-RNTI | | | | | | | | | | | | | | | +| Spare | 1 st Subframe number | | | N of MAC-is PDUs | | | | | | | | | | | +| Spare | 2 nd Subframe number | | | N of MAC-is PDUs | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| Spare | Last Subframe number | | | N of MAC-is PDUs | | | | | | | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of 1st subframe | | | | | | | | | | | | | | | +| MAC-is PDU descriptor of 2nd MAC-is PDU of 1st subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of 1st subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of last subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of last subframe | | | | | | | | | | | | | | | +| First MAC-is PDU of first subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| Last MAC-is PDU of first subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| First MAC-is PDU of last subframe | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | +| Last MAC-is PDU of last subframe | | | | | | | | | | | | | | | +| New IE FI 7(E) | New IE FI 6 | New IE FI 5 | New IE FI 4 | New IE FI 3 | New IE FI 2 | New IE FI 1 | New IE FI 0 | | | | | | | | +| Cell Portion LCR ID | | | | | | | | | | | | | | | +| Spare 7-2 | | | | | | AOA | | | | | | | | | +| AOA | | | | | | | | | | | | | | | +| Spare 7-5 | | | Ext Received SYNC UL Timing Deviation | | | | | | | | | | | | +| Ext received SYNC UL Timing Deviation | | | | | | | | | | | | | | | +| Spare 7-4 | | | | CRR Rec | TTI length | Prop. Delay FR | | | | | | | | | +| Propagation Delay Full Range | | | | | | | | | | | | | | | +| Spare Extension | | | | | | | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | | | | | | + +Frame Header + +Frame Payload + +Optional + +Conditional + +1.28Mcps TDD + +Conditional + +1.28Mcps TDD + +Conditional + +1.28Mcps TDD + +Conditional + +1.28Mcps TDD + +Conditional + +1.28Mcps TDD + +FDD + +FDD + +**Figure 21D: E-DCH DATA FRAME structure** + +For the description of the fields see subclause 6.2.7. + +The *Payload CRC* IE is optional in frames that contain a Payload, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The *Payload CRC* IE may only be present if the E-DCH DATA FRAME contains payload. + +[1.28Mcps TDD - Bit 0 of New IE Flags in E-DCH DATA FRAME indicates if the *Cell Portion LCR ID* IE is present (1) or not present (0).] + +[1.28Mcps TDD - Bit 1 of New IE Flags in E-DCH DATA FRAME indicates if *AOA* IE is present (1) or not present (0).] + +[1.28Mcps TDD - Bit 2 of New IE Flags in E-DCH DATA FRAME indicates if *Ext Received SYNC UL Timing Deviation* IE is present (1) or not present (0).] + +[1.28Mcps TDD – Bits 2 through 6 of New IE Flags in E-DCH DATA FRAME shall be set to 0.] + +[FDD - Bit 0 of *New IE Flags* IE in E-DCH DATA FRAME indicates if *Propagation Delay Full Range* IE is present (1) or not present (0).] + +[FDD - Bit 1 of *New IE Flags* IE in E-DCH DATA FRAME indicates if TTI length IE is present (1) or not present (0).] + +[FDD - Bit 2 of *New IE Flags* IE in E-DCH DATA FRAME indicates if *Cell Reselection Request Received (CRR Rec)* IE is present (1) or not present (0).] + +[FDD - Bits 3 through 6 of *New IE Flags* IE in E-DCH DATA FRAME shall be set to 0.] + +[FDD - Field length of *Spare Extension* IE in E-DCH DATA FRAME is 0-29 octets.] + +### 6.2.7 Coding of information elements in data frames + +#### 6.2.7.1 Header CRC + +**Description:** Cyclic Redundancy Checksum calculated on the header of a data frame with polynom: $X^7+X^6+X^2+1$ for the 7 bit header CRC [FDD and 1.28Mcps TDD - , $X^{11}+X^9+X^8+ X^2+X+1$ for the 11 bit header CRC]. + +The CRC calculation shall cover all bits in the header, starting from bit 0 in the first byte (FT field) up to the end of the header. See subclause 7.1. + +**Value range:** {0..127} [FDD and 1.28Mcps TDD – , {0..2047} for E-DCH DATA FRAME]. + +**Field length:** 7 bits [FDD and 1.28Mcps TDD - , 11 bits for E-DCH DATA FRAME]. + +#### 6.2.7.2 Frame Type + +**Description:** Describes if it is a control frame or a data frame. + +**Value range:** {0=data, 1=control}. + +**Field Length:** 1 bit. + +#### 6.2.7.3 Connection Frame Number (CFN) + +**Description:** Indicator as to which radio frame the first data was received on uplink or shall be transmitted on downlink. In case a transport bearer is used by several FACH channels with IP multicast option, the radio frame in which the first data shall be transmitted on a FACH mapping on the transport bearer shall be calculated according to: + +$$CFN = (MFN - CFN Offset) \bmod 256,$$ + +where: + +- MFN is the value of CFN field in the data frame; +- CFN Offset is a FACH parameter indicated by RNC (TS 25.433 [6]). + +The value range and field length depend on the transport channel for which the CFN is used. + +**Value range (PCH):** {0..4095}. + +**Value range (other):** {0..255}. + +**Field length (PCH):** 12 bits. + +**Field length (other):** 8 bits. + +#### 6.2.7.4 Transport Format Indicator + +**Description:** TFI is the local number of the transport format used for the transmission time interval. For information about what the transport format includes see TS 25.302 [3]. + +**Value range:** {0..31}. + +**Field length:** 5 bits. + +#### 6.2.7.5 Propagation Delay [FDD] + +**Description:** One-way radio interface delay as measured during RACH access. If the measured value exceeds the range of this information element, the information element shall be set to its maximum value, and the *Ext Propagation Delay* IE shall be used to represent the measured value, see subclause 6.2.7.5A. + +**Value range:** {0..765 chips}. + +**Granularity:** 3 chips. + +**Field length:** 8 bits. + +#### 6.2.7.5A Ext Propagation Delay [FDD] + +**Description:** One-way radio interface delay as measured during RACH access, extended value part. This IE shall be present only if the range of the *Propagation Delay* IE is insufficient to represent the measured value. + +**Value range:** {0 - 3069 chips}, values 0 -765 are not used. + +**Granularity:** 3 chips. + +**Field length:** 10 bits. + +#### 6.2.7.6 Rx Timing Deviation [3.84Mcps TDD] + +**Description:** Measured Rx Timing Deviation as a basis for timing advance. This value should consider measurements made in all frames and all timeslots that contain the transport blocks in the payload. In case the *Timing Advance Applied* IE indicates "No" (see TS 25.433 [6]) in a cell, the Rx Timing Deviation field shall be set to N = 0. + +**Value range:** {-1024 .. +1023 chips}. + +$\{N*4 - 256\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1)*4 - 256\} \text{ chips}.$ + +With N = 0, 1, ..., 127. + +$\{(N-128)*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N-127)*4 - 1024\} \text{ chips}$ + +With N = 128, 129, ..., 319 + +$\{N*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N+1)*4 - 1024\} \text{ chips}$ + +With N = 320, 321, ..., 511 + +**Granularity:** 4 chips. + +**Field length:** 9 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant bit is contained in the RX timing deviation (continuation) field. + +#### 6.2.7.6A Received SYNC UL Timing Deviation [1.28Mcps TDD] + +**Description:** Measured Received SYNC UL Timing Deviation as a basis for propagation delay. + +**Value range:** {0, ..., +255} chips + +**Granularity:** 1 chip. + +**Field length:** 8 bits. + +#### 6.2.7.6B Rx Timing Deviation [7.68Mcps TDD] + +**Description:** Measured Rx Timing Deviation as a basis for timing advance. This value should consider measurements made in all frames and all timeslots that contain the transport blocks in the payload. In case the *Timing Advance Applied* IE indicates "No" (see TS 25.433 [6]) in a cell, the Rx Timing Deviation field shall be set to N = 0. + +**Value range:** {-2056, ..., +2055} chips + +$$\{N*4 - 2056\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1)*4 - 2056\} \text{ chips}$$ + +With N = 0, 1, ..., 1027 + +**Granularity:** 4 chips. + +**Field length:** 10 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant 2 bits are contained in the RX timing deviation (continuation) field. + +#### 6.2.7.7 Transport Block + +**Description:** A block of data to be transmitted or have been received over the radio interface. The transport format indicated by the TFI describes the transport block length and transport block set size. See TS 25.302 [3]. + +#### 6.2.7.8 CRC Indicator + +**Description:** Shows if the transport block has a correct CRC. The UL Outer Loop Power Control may use the CRC indication. + +**Value range:** {0=Correct, 1=Not Correct}. + +**Field length:** 1 bit. + +#### 6.2.7.9 Payload CRC + +**Description:** Cyclic Redundancy Checksum calculated on the payload of a data frame with polynom $X^{16}+X^{15}+X^2+1$ . + +The CRC calculation shall cover all bits in the data frame payload, starting from bit 7 in the first byte up to bit 0 in the byte before the payload CRC. See subclause 7.1. + +In HS-DSCH DATA FRAME TYPE3, if MUI is set, the CRC calculation shall cover all bits in the data frame payload, starting from bit 7 in the first byte up to bit 0 in the byte before the payload CRC, and all the bits in the Extended for UEn in HS-DSCH DATA FRAME TYPE 3 structure. See subclause 7.1. + +**Field length:** 16 bits. + +#### 6.2.7.10 Transmit Power Level + +**Description:** Preferred transmission power level during this TTI for the corresponding transport channel. The indicated value is the negative offset relative to the maximum power configured for the physical channel(s) used for the respective transport channel. [1.28Mcps TDD - The Node B shall ignore the Transmit Power Level in the TDD DSCH DATA FRAME.] [3.84Mcps and 7.68Mcps TDD - The Node B shall ignore the Transmit Power Level in the TDD DSCH DATA FRAME if closed loop TPC power control is used.] + +**Value range:** {0 .. 25.5 dB}. + +**Granularity:** 0,1 dB. + +**Field length:** 8 bits. + +#### 6.2.7.11 Paging Indication (PI) + +**Description:** Describes if the PI Bitmap is present in the payload. + +**Value range:** {0=no PI-bitmap in payload, 1=PI-bitmap in payload}. + +**Field length:** 1 bit. + +#### 6.2.7.12 Paging Indication bitmap (PI-bitmap) + +**Description:** Bitmap of Paging Indications PI0..PIN-1. Bit 7 of the first byte contains PI0, Bit 6 of the first byte contains PI1, ..., Bit 7 of the second byte contains PI8 and so on. + +**Value range:** [FDD - {18, 36, 72 or 144 Paging Indications}.] + [3.84Mcps TDD – {30, 34, 60, 68, 120 and 136} Paging Indications for 2 PICH frames, {60, 68, 120, 136, 240 and 272} Paging Indications for 4 PICH frames]. + [1.28Mcps TDD – {44, 88 and 176} Paging Indications for 2 PICH frames, {88, 176 and 352} Paging Indications for 4 PICH frames]. + [7.68Mcps TDD – {30, 34, 60, 68, 120 and 136} Paging Indications for 2 PICH frames, {60, 68, 120, 136, 240 and 272} Paging Indications for 4 PICH frames, ..... {120, 136, 240, 272, 480 and 544} Paging Indications for 8 PICH frames]. + +**Field length:** [FDD - 3, 5, 9 or 18 bytes (the PI-bitmap field is padded at the end up to an octet boundary)]. + +[3.84Mcps TDD – 4, 5, 8, 9, 15, 17, 30 or 34 bytes (the PI-bitmap field is padded at the end up to an octet boundary)]. + +[1.28Mcps TDD – 6, 11, 22 or 44 bytes (the PI-bitmap field is padded at the end up to an octet boundary)]. + +[7.68Mcps TDD – 4, 5, 8, 9, 15, 17, 30, 34, 60 or 68 bytes (the PI-bitmap field is padded at the end up to an octet boundary)]. + +#### 6.2.7.13 Rx Timing Deviation on RACH [3.84Mcps TDD] + +Void. + +#### 6.2.7.14 PDSCH Set Id [TDD] + +**Description:** A pointer to the PDSCH Set which shall be used to transmit the DSCH DATA FRAME over the radio interface. + +**Value range:** {0..255}. + +**Field length:** 8 bits. + +#### 6.2.7.15 Code Number [FDD] + +Void. + +#### 6.2.7.16 Spreading Factor (SF) [FDD] + +Void. + +#### 6.2.7.17 Power Offset [FDD] + +Void. + +#### 6.2.7.18 MC Info [FDD] + +Void. + +#### 6.2.7.19 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.2.7.20 Quality Estimate (QE) [TDD] + +**Description:** The quality estimate is derived from the Transport channel BER. + +If the USCH FP frame includes TB's for the USCH then the QE is the Transport channel BER for the selected USCH. If no Transport channel BER is available the QE shall be set to 0. + +The quality estimate shall be set to the Transport channel BER and be measured in the units TrCH\_BER\_LOG respectively (see TS 25.433 [6]). The UL Outer Loop Power Control may use the quality estimate. + +**Value range:** {0..255}. + +**Granularity:** 1. + +**Field length:** 8 bits. + +#### 6.2.7.21 Common Transport Channel Priority Indicator (CmCH-PI) + +**Description:** CmCH-PI, configured via the Scheduling Priority Indicator in NBAP (TS 25.433 [6]), is the relative priority of the data frame and the SDUs included. + +**Value range:** {0-15, where 0=lowest priority, 15=highest priority}. + +**Field length:** 4 bits. + +#### 6.2.7.22 User Buffer Size + +**Description:** Indicates the users' buffer size (i.e. the amount of data in the buffer) in octets for a given Common Transport Channel Priority Indicator level. + +**Value range:** {0-65535}. + +**Field length:** 16 bits. + +#### 6.2.7.23 MAC-d PDU Length + +**Description:** The value of that field indicates the length of every MAC-d PDU in the payload of the HS-DSCH DATA FRAME in number of bits. + +**Value range:** {0-5000}. + +**Field Length:** 13 bits. + +#### 6.2.7.24 NumOfPDU + +**Description:** Indicates the number of MAC-d PDUs in the payload. + +**Value range:** {1-255}. + +**Field Length:** 8 bits. + +#### 6.2.7.25 MAC-d PDU + +**Description:** A MAC-d PDU contains the MAC-d PDU as defined in TS 25.321 [9]. + +**Field length:** See the value of the *MAC-d PDU Length* IE. + +#### 6.2.7.26 Cell Portion ID [FDD] + +**Description:** Cell Portion ID indicates the cell portion with highest SIR during RACH access. Cell Portion ID is configured by O&M. + +**Value range:** {0-63}. + +**Field Length:** 6 bits. + +#### 6.2.7.27 New IE Flags + +**Description:** The *New IE Flags* IE is only present if at least one new IE is present. The *New IE Flags* IE contains flags indicating which new IEs that are present following the *New IE Flags* IE. The last bit position of the *New IE Flags* IE is used as the Extension Flag to allow the extension of the *New IE Flags* IE in the future. Extension octets of the *New IE Flags* IE shall follow directly after the first octet of the *New IE Flags* IE. When an extension octet of the *New IE Flags* IE is present, then all previous extension octets of the *New IE Flags* IE and the *New IE Flags* IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs. + +**Value range:** + +Bit 0-6 of each octet: Indicates if a new IE is present (1) or not present (0) in the bytes following the *New IE Flags* IE. The meaning of each bit is explained in the corresponding DATA FRAME subclause; + +Bit 7 of each octet: Indicates if an extension octet of the *New IE Flags* IE follows (1) or not (0). + +**Field length:** 1 – 31 octets. + +#### 6.2.7.28 Flush + +**Description:** Indicates whether the DRNS should remove (1) or not (0) all the MAC-d PDUs from the corresponding MAC-hs Priority Queue that have been received prior to this data frame HS-DSCH DATA FRAME on the same transport bearer. + +**Value range:** {0 = no flush, 1 = flush}. + +**Field Length:** 1 bit. + +#### 6.2.7.29 DRT (Delay Reference Time) + +**Description:** *DRT* is a 16-bit *Delay Reference Time*. *DRT* can be used for dynamic delay measurements. The *DRT* counter bridges the same time span as RFN and BFN. *DRT* is locked to RFN in SRNC and is a 40960 counter with 1 ms resolution. + +**Value range:** {0..40959DEC ms (0..9FFFHEX ms)}. + +**Granularity:** 1 ms. + +**Field length:** 16 bits. + +#### 6.2.7.30 Frame Sequence Number + +**Description:** The 4-bit *Frame Sequence Number* (FSN) is incremented for each transmitted HS-DSCH data frame belonging to one MAC-d flow [FDD and 1.28Mcps TDD – , common MAC flow or E-DCH DATA FRAME belonging to one E-DCH data flow for CELL\_FACH and Idle]. At wraparound of the Frame Sequence Number, the value "0" shall not be used. Each flow generates its own Frame Sequence. + +**Value range:** + +- | | | +|--------|------------------------------------------------------------------------------------------------------| +| 0 | is a special value and indicates that the Frame Sequence Number IE shall be treated as spare. | +| 1 – 15 | indicates the Frame Sequence Number. | + +**Granularity:** 1. + +**Field length:** 4 bits. + +#### 6.2.7.31 Logical Channel ID in block n + +**Description:** This field provides identification of the logical channel instance associated with the PDUs of the n-th *block of PDUs with the same size* in the HS-DSCH DATA FRAME TYPE 2 [FDD and 1.28Mcps TDD – and TYPE 3]. Multiple logical channels may be carried on the same MAC-d flow [FDD and 1.28Mcps TDD – , Common MAC flow or Paging MAC flow]. + +**Value range:** {0-15}, where 0-14 identifies logical channels 1-15, 15 identifies BCCH or PCCH logical channel mapped on HS-DSCH. + +**Field length:** 4 bits. + +#### 6.2.7.32 Total Number of PDU blocks + +**Description:** The field indicates the number of blocks of *block of PDUs with the same size* in this HS-DSCH DATA FRAME. In HS-DSCH DATA FRAME TYPE3, the field indicates the number of blocks of *block of PDUs with the same size* per UE, if MUI is set. + +**Value range:** {0-31}, 0 only for 1.28Mcps TDD HS-DSCH DATA FRAME TYPE 3. + +**Field length:** 5 bits. + +#### 6.2.7.33 MAC-d/c PDU Length in block n + +**Description:** The value of this field indicates the length of every MAC-d PDU [FDD and 1.28Mcps TDD - or MAC-c PDU] in the n-th *block of PDUs with the same size* in number of octets. + +**Value range:** {0-1505}, 0 – not used. + +**Field length:** 11 bits. + +#### 6.2.7.34 Number of MAC-d/c PDUs in block n (#PDUs in block n) + +**Description:** Indicates the number of MAC-d PDUs [FDD and 1.28Mcps TDD - or MAC-c PDUs] in the n-th *block of PDUs with the same size*. + +**Value range:** {0-15}, 0 – not used. + +**Field length:** 4 bits. + +#### 6.2.7.35 DRT Indicator + +**Description:** Indicates whether a DRT is present. + +**Value range:** {0 = DRT not present, 1= DRT present}. + +**Field length:** 1 bit. + +#### 6.2.7.36 FACH Indicator (FI) [FDD and 1.28Mcps TDD] + +**Description:** Indicates whether an H-RNTI and a RACH Measurement Result are present (i.e. whether UE in CELL\_FACH). + +**Value range:** {0 = H-RNTI and RACH Measurement Result not present, 1= H-RNTI and RACH Measurement Result present}. + +**Field length:** 1 bit. + +#### 6.2.7.37 H-RNTI [FDD and 1.28Mcps TDD] + +**Description:** H-RNTI is defined in TS 25.401 [11]. The field identifies an UE having a HS-PDSCH assignment within a cell [FDD and 1.28Mcps TDD - or has the same value as the *BCCH Specific HS-DSCH RNTI* IE configured in TS 25.433 [6]]. + +**Value range:** {0-65535}, 0 – not used. + +**Field length:** 16 bits. + +#### 6.2.7.38 RACH Measurement Result [FDD and 1.28Mcps TDD] + +**Description:** [FDD - This field indicates the values received in RACH Measurement. The type of the measured value in the field is configured via NBAP (TS 25.433 [6]). [1.28Mcps TDD - This field indicates the pathloss value (in dB) calculated based on the *Primary CCPCH RSCP* IE in the measurement result on RACH according to the formula in TS 25.331 [8].] + +**Value range:** [FDD - {0-158, 255}] + +255 is a special value for FDD and indicates that the Node B may ignore the RACH Measurement Results IE.] + +[1.28Mcps TDD - {0-112}] + +Note: The value “0” of the IE corresponds to the pathloss value of “46”, the value “1” corresponds to the pathloss value of “47”,..., the value “112” corresponds to the pathloss value of “158”.] + +**Field length:** [FDD - 8 bits]. + +[1.28Mcps TDD - 7 bits (Bit 7 of the RACH Measurement Result field is not used)]. + +#### 6.2.7.39 H-RNTI Indicator (HI) [FDD and 1.28Mcps TDD] + +**Description:** Indicates whether an H-RNTI and a CmCH-PI are present. + +**Value range:** {0 = H-RNTI and CmCH-PI not present, 1= H-RNTI and CmCH-PI present}. + +**Field length:** 1 bit. + +#### 6.2.7.40 FSN/DRT Reset + +**Description:** When the Node B receives a HS-DSCH DATA FRAME where the 1-bit *FSN/DRT Reset* IE is set to 1, the Node B should reset any state of congestion estimation based on previously received FSN and DRT values. Node B may instead decide to start a new estimation of congestion detection initiated with the FSN and DRT values included in this HS-DSCH data frame. *FSN/DRT Reset* IE set to 1 may indicate a discontinuity in the sequence of the transmitted DRT and FSN values in the transmitted HS-DSCH data frames belonging to the associated MAC-d flow. + +If the 1-bit *FSN/DRT Reset* IE is set to 0, Node B may use the included DRT and FSN values for congestion detection. + +**Value range:** + +- 0 Node B may use the included DRT and FSN values for congestion detection. +- 1 Node B should not use previously received FSN and DRT values for congestion detection. + +**Field length:** 1 bit. + +#### 6.2.7.41 MAC-d/c PDU + +**Description:** A MAC-d/c PDU contains the MAC-ehs SDU as defined in TS 25.321 [9]. + +**Field length:** For length of MAC-d/c PDU of block n, see the value of the *MAC-d/c PDU length in block n* IE. + +#### 6.2.7.42 AOA (Angle of Arrival) [1.28Mcps TDD] + +**Description:** This field indicates the angle of arrival information of UE measured by Node B. + +**Value range:** {0-719} + +**Field length:** 10 bit. + +#### 6.2.7.43 Ext Received SYNC UL Timing Deviation [1.28Mcps TDD] + +**Description:** Measured Received SYNC UL Timing Deviation as a basis for propagation delay. + +**Value range:** {0, ..., +1023} chips + +**Granularity:** 1/8 chip. + +**Field length:** 13 bits. + +#### 6.2.7.44 Number of Subframes [FDD and 1.28Mcps TDD] + +**Description:** The *Number of Subframes* field indicates how many subframes that follows in the frame. [1.28Mcps TDD – This will always be set to "1".] + +NOTE: A subframe has both a header portion and a payload portion in the frame. + +**Value range:** {1-16} + +The binary coding is derived from the value minus 1. E.g. value 1 is coded as binary "0000" and value 16 is coded as binary "1111". + +Values {11, 12, 13, 14, 15, 16}: Reserved in this user plane revision. Shall be ignored by the receiver. + +**Field length:** 4 bits. + +#### 6.2.7.45 Number of MAC-is SDU in frame [FDD and 1.28Mcps TDD] + +**Description:** Total number of MAC-is SDUs in all MAC-is PDUs in the E-DCH DATA FRAME. + +**Value range:** {0-4095}. + +**Field length:** 12 bits. + +#### 6.2.7.46 Number of MAC-is PDUs [FDD and 1.28Mcps TDD] + +**Description:** Indicates the number of MAC-is PDUs in the user data frame in the payload part for the corresponding subframe number. + +**Value range:** {0-15} + +**Field length:** 4 bits. + +#### 6.2.7.47 Subframe Number [FDD and 1.28Mcps TDD] + +**Description:** Indicates the subframe number in which the payload was received. [1.28 Mcps TDD – This will be set to {0-1}.] + +**Value range:** {0-4} + +**Field length:** 3 bits. + +#### 6.2.7.48 E-DCH User Buffer Size [FDD and 1.28Mcps TDD] + +**Description:** Indicates the the total size of the E-DCH DATA FRAME in octets + +**Value range:** {0-262 140} + +**Field length:** 18 bits. + +#### 6.2.7.49 E-RNTI [FDD and 1.28Mcps TDD] + +**Description:** E-RNTI is defined in TS 25.401 [11]. + +In the E-DCH DATA FRAME: the field identifies a UE having an E-DCH assignment within a cell or the allocated E-RNTI to a UE requesting E-DCH resources for CELL\_FACH and Idle in a cell. + +In HS-DSCH DATA FRAME TYPE 2: E-RNTI identifies the UE using E-DCH in Cell\_FACH and Idle state. + +**Value range:** {0-65535}, 0 – not used. + +**Field length:** 16 bits. + +#### 6.2.7.50 MAC-is PDU descriptor [FDD and 1.28Mcps TDD] + +**Description:** The *MAC-is PDU descriptor* contains the Length (L), Logical channel identifier (LCH-ID) and Flag (F) fields mapped directly from the "MAC-i Header n" field (n>0) received over the Uu (TS 25.321 [9]). + +**Field length:** variable; length of *MAC-is PDU descriptor* in octets = 2 \* number of MAC-is SDU contained in the corresponding MAC-is PDU as described in TS 25.321 [9]. + +#### 6.2.7.51 Dedicated H-RNTI [FDD and 1.28Mcps TDD] + +**Description:** *Dedicated H-RNTI* identifies the H-RNTI for a UE using E-DCH in Cell\_FACH and Idle state. H-RNTI is defined in TS 25.401 [11]. + +**Value range:** {0-65535}, 0 – not used. + +Field length: 16 bits + +#### 6.2.7.52 eDRX Indication [FDD] + +**Description:** Indicates whether the UE in Cell\_FACH state supports Enhanced UE DRX or not. + +**Value range:** {0 = Enhanced UE DRX not supported, 1= Enhanced UE DRX supported}. + +Field length: 1 bit. + +#### 6.2.7.53 HS-DSCH physical layer category [FDD] + +**Description:** HS-DSCH physical layer category is defined in TS 25.306 [12]. The value of the field identifies the HS-DSCH physical layer category number of the UE, which is not applicable to the case that the *H-RNTI* IE sets to the same value as the *BCCH Specific HS-DSCH RNTI* IE. + +**Value range:** {1 - 63}, where the valid values are defined in TS 25.306 [12]. + +Field length: 6 bit. + +#### 6.2.7.54 Cell Portion LCR ID [1.28Mcps TDD] + +**Description:** Cell Portion LCR ID indicates the cell portion with best received quality during RACH access. Cell Portion LCR ID is configured by O&M. + +**Value range:** {0-255}. + +Field Length: 8 bits. + +#### 6.2.7.55 TS0 Indication [1.28Mcps TDD] + +**Description:** Indicates whether the UE supports TS0 enhancement or not. + +**Value range:** {0 = Enhanced TS0 not supported, 1= Enhanced TS0 supported}. + +Field length: 1 bit. + +#### 6.2.7.56 Enhanced HS-SCCH support indicator (EI) [FDD] + +**Description:** Indicates whether the UE in Cell\_FACH state supports enhanced different HS-SCCHs in consecutive TTIs support or not. + +**Value range:** {0 = Enhanced different HS-SCCHs in consecutive TTIs not supported, 1= Enhanced different HS-SCCHs in consecutive TTIs supported}. + +Field length: 1 bit. + +#### 6.2.7.57 MU-MIMO Indication(MI) [1.28Mcps TDD] + +**Description:** Indicates whether the UE in Cell\_FACH state supports MU-MIMO or not. + +**Value range:** {0 = MU-MIMO not supported, 1= MU-MIMO supported}. + +**Field length:** 1 bit. + +#### 6.2.7.58 Propagation Delay Full Range [FDD] + +**Description:** One-way radio interface delay as measured during random access on Common E-DCH. + +**Value range:** {0..3069 chips}. + +**Granularity:** 3 chips. + +**Field length:** 10 bits. + +#### 6.2.7.59 CPC Recovery (CPC Recov) [FDD] + +**Description:** Describes if UE is CPC non-uniform related to HS-SCCH order and CPC recovery is needed in the serving Node-B. It indicates that the dynamic DTX/DRX (de)activation using HS-SCCH order is needed. + +**Value range:** {0=no Recovery, 1=Recovery}. + +**Field Length:** 1 bit. + +Note: This is not applicable when HS-SCCH order is not used. + +#### 6.2.7.60 FeDRX Indication [FDD] + +**Description:** Indicates whether the UE in Cell\_FACH state supports Further Enhanced UE DRX or not. + +**Value range:** {0 = Further Enhanced UE DRX not supported, 1= Further Enhanced UE DRX supported}. + +**Field length:** 1 bit. + +#### 6.2.7.61 NodeB Triggered HS-DPCCH Transmission(NTHT) [FDD] + +**Description:** Indicates whether the UE in Cell\_FACH and CELL\_PCH state supports NodeB Triggered HS-DPCCH Transmission or not. + +**Value range:** {0 = NodeB Triggered HS-DPCCH Transmission not supported, 1= NodeB Triggered HS-DPCCH Transmission supported}. + +**Field length:** 1 bit. + +#### 6.2.7.62 TTI length [FDD] + +**Description:** Indicates which type of TTI length UE in Cell\_FACH and Idle state is in use for 2ms/10ms concurrent deployment. + +**Value range:** {0 = 2ms, 1= 10ms}. + +**Field length:** 1 bit. + +#### 6.2.7.63 SN, Frame Number + +**Description:** SN is a sequence number assigned to each HS-DSCH data frame by RNC and can be used by Node B to identify the set of MAC-d PDU's sent in the frame. This is also used by RNC to indicate the HS-DSCH data frame that the Node B can discard. + +**Value range:** {0.. 32767}. + +**Field length:** 15 bits. + +#### 6.2.7.64 S/D, Store/Discard indicator + +**Description:** The S/D indicator indicates if Node B can store or discard data associated with SN (See section 6.2.7.63). + +**Value range:** {0 = Discard data associated with SN, 1 = Store and associate MAC-d PDUs in frame with SN}. + +**Field length:** 1 bit. + +#### 6.2.7.65 CR Ind (Cell Reselection Indication) + +**Description:** Indicates that the Node B may release the common E-DCH resource due to a cell reselection indication. + +**Value range:** {0 = Release common E-DCH resource not permitted due to a cell reselection indication, 1 = Release common E-DCH resource permitted due to a cell reselection indication.} + +**Field length:** 1 bit. + +#### 6.2.7.66 CRR Rec (Cell Reselection Request Received) + +**Description:** Indicates that the Node B has received Cell Reselection Request from UE or not. + +**Value range:** {0 = Cell Reselection Request from UE not received, 1 = Cell Reselection Request from UE received}. + +**Field length:** 1 bit. + +#### 6.2.7.67 Multiple UEs Indicator (MUI) [FDD] + +**Description:** The MUI indicates there is another UE's MAC-d/c PDUs (Extended for UEn) followed in below octets. MUI=0, indicates no other UE's MAC-d/c PDUs is followed. MUI=1 in Extended for UE(n-1) indicates nth UE's MAC-d/c PDUs (Extended for UEn) is followed. + +**Value range:** {0 = No other UE's MAC-d/c PDUs followed, 1 = there is another UE's MAC-d/c PDUs followed}. + +**Field length:** 1 bit. + +#### 6.2.7.68 Extended for UEn [FDD] + +**Description:** The Extended for UEn is used to carry another UE's data in same HS-DSCH DATA FRAME TYPE3 in case of MUI=1 is indicated in previous UE's New IE flags. All IEs included in *Extended for UEn* are defined in subclause 6.2.6A Figure 21C-1. + +#### 6.2.7.69 Operation Preference of Common E-DCH resource Indication (OPCE Ind) [FDD] + +**Description:** The OPCE Ind indicates there is a preference for the Node B to trigger acquisition of the common E-DCH resource or to release the allocated common E-DCH resource for the particular UE. In case of NTHT is not set or set to zero, the OPCE Ind bit is not used. + +**Value range:** {0 = Preference to release the allocated common E-DCH resource, 1 = Preference to trigger acquisition of the common E-DCH resource}. + +**Field length:** 1 bit. + +#### 6.2.7.70 HS-SCCH DRX Indication [FDD] + +**Description:** Indicates whether the UE in Cell\_FACH state supports HS-SCCH DRX or not. + +**Value range:** {0 = HS-SCCH DRX not supported, 1= HS-SCCH DRX DRX supported}. + +Field length: 1 bit. + +## 6.3 Control frame structure + +### 6.3.1 Introduction + +The Common Control Channel control frames are used to transport control information between the CRNC and the Node B. Figure 22 defines the Control Frame structure for common transport channels. + +![](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +| | | | | | | | | +|----------------------------|---|---|---|---|---|---|----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Frame CRC | | | | | | | FT | +| Control Frame Type | | | | | | | | +| Control Information | | | | | | | | +| Control Information (cont) | | | | | | | | + +| | +|---------------------------| +| Header (2 bytes) | +| Payload (variable length) | + +Header (2 bytes) + +**Figure 22: Iub Common Transport Channel Control Frame Format** + +The structure of the header and the payload of the control frames is defined in the following subclauses. + +### 6.3.2 Coding of information elements of the Control frame header + +#### 6.3.2.1 Frame CRC + +**Description:** Cyclic Redundancy Checksum calculated on a control frame with polynom: $X^7+X^6+X^2+1$ . + +The CRC calculation shall cover all bits in the control frame, starting from bit 0 in the first byte (FT field) up to the end of the control frame. See subclause 7.1. + +**Value range:** {0..127}. + +**Field length:** 7 bits. + +#### 6.3.2.2 Frame Type (FT) + +Refer to subclause 6.2.7.2. + +#### 6.3.2.3 Control Frame Type + +**Description:** Indicates the type of the control information (information elements and length) contained in the payload. + +**Value:** Values of the Control Frame Type parameter are defined in table 2. + +**Table 2** + +| Type of control frame | Value | +|----------------------------------------------------------------------|-----------| +| OUTER LOOP POWER CONTROL | 0000 0001 | +| TIMING ADJUSTMENT | 0000 0010 | +| DL SYNCHRONISATION | 0000 0011 | +| UL SYNCHRONISATION | 0000 0100 | +| Reserved Value | 0000 0101 | +| DL NODE SYNCHRONISATION | 0000 0110 | +| UL NODE SYNCHRONISATION | 0000 0111 | +| DYNAMIC PUSCH ASSIGNMENT | 0000 1000 | +| TIMING ADVANCE | 0000 1001 | +| HS-DSCH Capacity Request | 0000 1010 | +| HS-DSCH Capacity Allocation TYPE 1 | 0000 1011 | +| HS-DSCH Capacity Allocation TYPE 2 | 0000 1100 | +| HS-DSCH UL Synchronization Establishment Failure (1.28Mcps TDD only) | 0000 1101 | +| HS-DSCH PDU Drop Indication | 0000 1110 | + +**Field Length:** 8 bits. + +The "Reserved Value" for the *Control Frame Type* IE shall not be used by the SRNC. A control frame whose *Control Frame Type* IE is set to the "Reserved Value" shall be ignored by the Node B. + +### 6.3.3 Payload structure and information elements + +#### 6.3.3.1 TIMING ADJUSTMENT + +##### 6.3.3.1.1 Payload Structure + +Figures 23 and 24 shows the structure of the payload when control frame is used for the timing adjustment. + +![](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| ToA | | | | | | | | 1 | | +| ToA (cont) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 23: TIMING ADJUSTMENT payload structure (non-PCH transport bearers) + +![](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|----------|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| CFN(cont) | | | | Not Used | | | | 1 | | +| ToA | | | | | | | | 1 | | +| ToA (cont) | | | | | | | | 1 | | +| ToA(cont) | | | | Not Used | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 24: TIMING ADJUSTMENT payload structure (PCH transport bearer) + +##### 6.3.3.1.2 CFN + +Refer to subclause 6.2.7.3. + +##### 6.3.3.1.3 Time of arrival (ToA) + +**Description:** Time difference between the arrival of the DL frame with respect to TOAWE (based on the CFN in the frame). The value range and field length depend on the transport channel for which the CFN is used. + +**Value range (PCH):** {-20480ms, +20479.875ms}. + +**Value range (other):** {-1280ms, +1279.875ms}. + +**Granularity:** 125 $\mu$ s. + +**Field length (PCH):** 20 bits. + +**Field length (other):** 16 bits. + +##### 6.3.3.1.4 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.3.3.2 DL SYNCHRONISATION + +##### 6.3.3.2.1 Payload Structure + +Figures 25 and 26 shows the structure of the payload when control frame is used for the user plane synchronisation. + +![](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 25: DL SYNCHRONISATION payload structure (non-PCH transport bearers) + +![](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|----------|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| CFN(cont) | | | | Not Used | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 26: DL SYNCHRONISATION payload structure (PCH transport bearers) + +##### 6.3.3.2.2 CFN + +Refer to subclause 6.2.7.3. + +##### 6.3.3.2.3 Spare Extension + +Refer to subclause 6.3.3.1.4. + +#### 6.3.3.3 UL SYNCHRONISATION + +##### 6.3.3.3.1 Payload Structure + +Figures 27 and 28 shows the structure of the payload when the control frame is used for the user plane synchronisation (UL). + +![](4b8c5ecb492fd759c766fe8950fafe67_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| ToA | | | | | | | | 1 | | +| ToA (cont) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 27: UL SYNCHRONISATION payload structure (non-PCH transport bearers) + +![](4b82c57bac9f5800baee15745b212963_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|----------|---|---|---|-----------------|---------| +| CFN | | | | | | | | 1 | Payload | +| CFN(cont) | | | | Not Used | | | | 1 | | +| ToA | | | | | | | | 1 | | +| ToA (cont) | | | | | | | | 1 | | +| ToA(cont) | | | | Not Used | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 28: UL SYNCHRONISATION payload structure (PCH transport bearers) + +##### 6.3.3.3.2 CFN + +Refer to subclause 6.2.7.3. + +##### 6.3.3.3.3 Time of Arrival (TOA) + +Refer to subclause 6.3.3.1.3. + +##### 6.3.3.3.4 Spare Extension + +Refer to subclause 6.3.3.1.4. + +#### 6.3.3.4 DL NODE SYNCHRONISATION + +##### 6.3.3.4.1 Payload Structure + +The payload of the DL Node synchronisation control frames is shown in figure 29. + +![](58bbc570572758132ea39938e4f03b5b_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| T1 | | | | | | | | 1 | Payload | +| T1 (cont) | | | | | | | | 1 | | +| T1 (cont) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +**Figure 29: DL NODE SYNCHRONISATION payload structure** + +##### 6.3.3.4.2 T1 + +**Description:** RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. + +**Value range:** {0 .. 40959.875 ms}. + +**Granularity:** 0.125ms. + +**Field length:** 24 bits. + +##### 6.3.3.4.3 Spare Extension + +Refer to subclause 6.3.3.1.4. + +#### 6.3.3.5 UL NODE SYNCHRONISATION + +##### 6.3.3.5.1 Payload Structure + +The payload of the UL Node synchronisation control frames is shown in figure 30. + +![](4bb3aa9902f241d0b9ea5f1151b287b5_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| T1 | | | | | | | | 1 | Payload | +| T1 (cont) | | | | | | | | 1 | | +| T1 (cont) | | | | | | | | 1 | | +| T2 | | | | | | | | 1 | | +| T2 (cont) | | | | | | | | 1 | | +| T2 (cont) | | | | | | | | 1 | | +| T3 | | | | | | | | 1 | | +| T3 (cont) | | | | | | | | 1 | | +| T3 (cont) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +**Figure 30: UL NODE SYNCHRONISATION payload structure** + +##### 6.3.3.5.2 T1 + +**Description:** T1 timer is extracted from the correspondent DL Node synchronisation control frame. + +**Value range:** {0 .. 40959.875 ms}. + +**Granularity:** 0.125ms. + +**Field length:** 24 bits. + +##### 6.3.3.5.3 T2 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B received the correspondent DL synchronisation frame through the SAP from the transport layer. + +**Value range:** {0 .. 40959.875 ms}. + +**Granularity:** 0.125ms. + +**Field length:** 24 bits. + +##### 6.3.3.5.4 T3 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B sends the frame through the SAP to the transport layer. + +**Value range:** {0 .. 40959.875 ms}. + +**Granularity:** 0.125ms. + +**Field length:** 24 bits. + +##### 6.3.3.5.5 Spare Extension + +Refer to subclause 6.3.3.1.4. + +#### 6.3.3.6 DYNAMIC PUSCH ASSIGNMENT [TDD] + +##### 6.3.3.6.1 Payload structure + +The payload of the Dynamic PUSCH Assignment control frames is shown in figure 31. + +![](147f857b06606c016ce376b7a89934d2_img.jpg) + +| | | | | | | | | +|----------------|----------|----------|----------|----------|----------|----------|----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| PUSCH Set Id | | | | | | | | +| Activation CFN | | | | | | | | +| Duration | | | | | | | | + +Payload (3 bytes) + +**Figure 31: DYNAMIC PUSCH ASSIGNMENT payload structure** + +#### 6.3.3.6.2 PUSCH Set Id + +**Description:** Identifies a PUSCH Set from the collection of PUSCH Sets which have been pre-configured in the Node B, for the respective cell in which the USCH exists. The PUSCH Set Id is unique within a cell. + +**Value range:** {0..255}. + +**Field length:** 8 bits. + +#### 6.3.3.6.3 Activation CFN + +**Description:** Activation CFN, specifies the Connection Frame Number where the allocation period of that PUSCH Set starts. + +**Value range:** Integer {0..255}. + +**Field length:** 8 bits. + +#### 6.3.3.6.4 Duration + +**Description:** Indicates the duration of the activation period of the PUSCH Set, in radio frames. + +**Value range:** 0..255 means: 0 to 255 radio frames, i.e. 0 to 2550 msec. + +**Field length:** 8 bits. + +### 6.3.3.7 DSCH TFCI SIGNALLING [FDD] + +#### 6.3.3.7.1 Payload structure + +Void. + +#### 6.3.3.7.2 TFCI (field 2) + +Void. + +#### 6.3.3.7.3 Spare Extension + +Void. + +### 6.3.3.8 TIMING ADVANCE [3.84Mcps and 7.68Mcps TDD] + +#### 6.3.3.8.1 Payload structure + +Figure 33 shows the structure of the payload when the control frame is used for timing advance. + +![](1230eaa9d75a09d7e7b8509931e9190e_img.jpg) + +| | | | | | | | | | | +|-----------------|----|---|---|---|---|---|---|------------------|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of Octets | | +| CFN | | | | | | | | 1 | Payload | +| Spare | TA | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +**Figure 33: TIMING ADVANCE payload structure** + +#### 6.3.3.8.2 CFN + +Refer to subclause 6.2.7.3. + +#### 6.3.3.8.3 TA [3.84 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0 .. 252 chips}. + +**Granularity:** 4 chips. + +**Field length:** 6 bits. + +#### 6.3.3.8.3A TA [7.68 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0 .. 508 chips}. + +**Granularity:** 4 chips. + +**Field length:** 7 bits. + +#### 6.3.3.8.4 Spare Extension + +Refer to subclause 6.3.3.1.4. + +### 6.3.3.9 OUTER LOOP POWER CONTROL [1.28 Mcps TDD] + +#### 6.3.3.9.1 Payload structure + +Figure 34 shows the structure of the payload when control frame is used for the UL outer loop power control. + +![](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +| | | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|------------------|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of Octets | | +| UL SIR TARGET | | | | | | | | 1 | Payload | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 34: Structure of the payload for OUTER LOOP PC control frame + +## 6.3.3.9.2 SIR Target + +**Description:** Value (in dB) of the SIR target to be used by the UL inner loop power control. + +SIR Target is given in the unit UL\_SIR\_TARGET where: + +| | | +|---------------------|----------------------| +| UL_SIR_TARGET = 000 | SIR Target = -8.2 dB | +| UL_SIR_TARGET = 001 | SIR Target = -8.1 dB | +| UL_SIR_TARGET = 002 | SIR Target = -8.0 dB | +| ... | | +| UL_SIR_TARGET = 254 | SIR Target = 17.2 dB | +| UL_SIR_TARGET = 255 | SIR Target = 17.3 dB | + +**Value range:** {-8.2 .. 17.3 dB}. + +**Granularity:** 0.1 dB. + +**Field length:** 8 bits. + +## 6.3.3.9.3 Spare Extension + +Refer to subclause 6.3.3.1.4. + +## 6.3.3.10 HS-DSCH CAPACITY REQUEST + +![](0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg) + +| | | | | | | | | | | +|-------------------------|---|---|---|---------|---|---|---|-----------------|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of Bytes | | +| Spare bits 7-4 | | | | CmCH-PI | | | | 1 | Payload | +| User Buffer Size | | | | | | | | 1 | | +| User Buffer Size (cont) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +Figure 35: CAPACITY REQUEST payload structure + +The HS-DSCH CAPACITY REQUEST control frame is sent for each priority group to indicate the user buffer size. The control frame is sent by the CRNC when the CRNC considers the user buffer status needs an increased buffer reporting frequency. This may be sent to signal an event, such as, data arrival or user-buffer discard. This control frame is used to improve user-buffer reporting above the level produced by the user-buffer reporting associated with the HS-DSCH DATA FRAMES. + +## 6.3.3.10.1 Common Transport Channel Priority Indicator (CmCH-PI) + +Refer to subclause 6.2.7.21. + +## 6.3.3.10.2 User Buffer Size + +Refer to subclause 6.2.7.22. + +## 6.3.3.10.3 Spare Extension + +Refer to subclause 6.3.3.1.4. + +### 6.3.3.11 HS-DSCH CAPACITY ALLOCATION + +Two types of HS-DSCH CAPACITY ALLOCATION exist for the HS-DSCH capacity allocation, i.e. HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame and HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | +|---------------------------------|---|-------------------|---|-----------------|---|---|---|--|--|--|--|--|--| +| Spare bits 7-6 | | Congestion Status | | CmCH-PI | | | | | | | | | | +| Maximum MAC-d PDU Length | | | | | | | | | | | | | | +| Maximum MAC-d PDU Length (cont) | | | | HS-DSCH Credits | | | | | | | | | | +| HS-DSCH Credits (cont) | | | | | | | | | | | | | | +| HS-DSCH Interval | | | | | | | | | | | | | | +| HS-DSCH Repetition Period | | | | | | | | | | | | | | +| Spare Extension | | | | | | | | | | | | | | + +Figure 36: CAPACITY ALLOCATION TYPE 1 payload structure + +The CAPACITY ALLOCATION TYPE 1 Control Frame describes an allocation that the CRNC may use. When the *HS-DSCH Credits* IE has a value of 0 it signifies that there is no resources allocated for transmission and to thus stop transmission. When the *HS-DSCH Credits* IE has a value of 2047, it signifies unlimited capacity for transmission of PDUs. When the *HS-DSCH Repetition Period* IE has a value of 0, it signifies that the allocation (*Maximum MAC-d PDU Length*, *HS-DSCH Credits* and *HS-DSCH Interval* IEs) can be repeated without limit. In addition to this the CAPACITY ALLOCATION TYPE 1 Control Frame informs the CRNC about the detection of congestion in the DL transport network layer with the *Congestion Status* Bits. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +|-----------------------------------|---|-------------------|---|---------|----------------------------|---|---|--|--|--|--|--| +| Spare bits 7-6 | | Congestion Status | | CmCH-PI | | | | | | | | | +| Spare bits 7 – 3 | | | | | Maximum MAC-d/c PDU Length | | | | | | | | +| Maximum MAC-d/c PDU Length (cont) | | | | | | | | | | | | | +| HS-DSCH Credits | | | | | | | | | | | | | +| HS-DSCH Credits (cont) | | | | | | | | | | | | | +| HS-DSCH Interval | | | | | | | | | | | | | +| HS-DSCH Repetition Period | | | | | | | | | | | | | +| Spare Extension | | | | | | | | | | | | | + +Figure 37: CAPACITY ALLOCATION TYPE 2 payload structure + +The CAPACITY ALLOCATION TYPE 2 Control Frame describes an allocation that the CRNC may use. When the *HS-DSCH Credits* IE has a value of 0 it signifies that there is no resources allocated for transmission and to thus stop transmission. When the *HS-DSCH Credits* IE has a value of 65535, it signifies unlimited capacity for transmission of PDUs. When the *HS-DSCH Repetition Period* IE has a value of 0, it signifies that the allocation (*Maximum MAC-d/c PDU Length*, *HS-DSCH Credits* and *HS-DSCH Interval* IEs) can be repeated without limit. In addition to this the CAPACITY ALLOCATION TYPE 2 Control Frame informs the CRNC about the detection of congestion in the DL transport network layer with the *Congestion Status* Bits. + +#### 6.3.3.11.1 Common Transport Channel Priority Indicator (CmCH-PI) + +Refer to subclause 6.2.7.21. + +#### 6.3.3.11.2 Maximum MAC-d PDU Length + +**Description:** The *Maximum MAC-d PDU Length* IE is used in HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame. The value indicates the maximum allowable PDU size among the MAC-d PDU sizes configured via NBAP (TS 25.433 [6]). + +**Value range:** Refer to subclause 6.2.7.23. + +**Field length:** Refer to subclause 6.2.7.23. + +#### 6.3.3.11.3 HS-DSCH Credits + +**Description:** The *HS-DSCH Credits* IE is used in HS-DSCH CAPACITY ALLOCATION (TYPE 1 and TYPE 2) Control Frame. It indicates the granted amount of MAC-d PDU data that CRNC may transmit during one HD-DSCH interval + +In case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, it indicates the number of MAC-d PDUs that a CRNC may transmit during one HS-DSCH Interval granted in the HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame. + +In case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame, the granted amount of MAC-d [FDD and 1.28Mcps TDD – or MAC-c] PDU data in octets is obtained by multiplying the MAC-d PDU length [FDD and 1.28Mcps TDD – or the MAC-c PDU length] (indicated by the *Maximum MAC- d/c PDU Length* IE) with the number of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] (indicated by the *HS-DSCH Credits* IE). + +**Value range:** {0-2047, where 0=stop transmission, 2047=unlimited} in case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, {0-65535, where 0=stop transmission, 65535=unlimited} in case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame. + +**Field length:** 11 bits in case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, 16 bits in case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame. + +#### 6.3.3.11.4 HS-DSCH Interval + +**Description:** The value of this field indicates the time interval during which the *HS-DSCH Credits* granted in the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame may be used. The first interval starts immediately after reception of the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame, subsequent intervals start immediately after the previous interval has elapsed. This value is only applied to the HS-DSCH transport channel. + +**Value range:** {0-2550 ms}. Value 0 shall be interpreted that none of the credits shall be used. + +**Granularity:** 10ms. + +**Field Length:** 8 bits. + +#### 6.3.3.11.5 HS-DSCH Repetition Period + +**Description:** The value of this field indicates the number of subsequent intervals that the *HS-DSCH Credits* IE granted in the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame may be used. These values represent an integer number of Intervals (see subclause 6.3.3.11.4). This field is only applied to the HS-DSCH transport channel. + +**Value range:** {0-255, where 0= unlimited repetition period}. + +**Field Length:** 8 bits. + +#### 6.3.3.11.6 Spare Extension + +Refer to subclause 6.3.3.1.4. + +#### 6.3.3.11.7 Congestion Status + +**Description:** The *Congestion Status* Bits are used by the Node B to indicate whether a congestion situation is detected in a DL transport network layer or not. The Node B provides the congestion status in every HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame, which the CRNC may use. + +**Value range:** + +- 0 No TNL Congestion +- 1 Reserved for future use +- 2 TNL Congestion – detected by delay build-up + +### 3 TNL Congestion – detected by frame loss + +**Field Length:** 2 bits. + +#### 6.3.3.11.8 Maximum MAC-d/c PDU Length + +**Description:** The *Maximum MAC-d/c PDU Length* IE is used in HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame. The value is a factor in the granted amount of MAC-d PDU data that a CRNC may transmit during one HS-DSCH Interval. The amount of MAC-d [FDD and 1.28Mcps TDD - or MAC-c ] PDU data in octets is obtained by multiplying the MAC-d [FDD and 1.28Mcps TDD – or MAC-c ] PDU length (indicated by the *Maximum MAC d/c PDU Length* IE) with the number of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] (indicated by the *HS-DSCH Credits* IE). + +**Value range:** {0-1505}, 0 – not used. + +**Field length:** 11 bits. + +#### 6.3.3.12 HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE [1.28Mcps TDD] + +##### 6.3.3.12.1 Payload structure + +The payload of the HS-DSCH UL Synchronization Establishment Failure control frames is shown in figure 38. + +![](3bd9d303382ff0566369ed81a9226ade_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|-----------------|---|---|---|---|---|---|---|-----------------|---------| +| H-RNTI | | | | | | | | 1 | Payload | +| H-RNTI (cont.) | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +**Figure 38: HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE payload structure** + +##### 6.3.3.12.2 H-RNTI + +Refer to subclause 6.2.7.37. + +#### 6.3.3.13 HS-DSCH PDU DROP INDICATION + +##### 6.3.3.13.1 Payload structure + +The payload of the HS-DSCH PDU Drop Indication control frame is shown in figure 39. + +![](3a72363d45bf0a19e0b543424b732b2c_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Number of bytes | | +|------------------------|---|---|---|---|-------------|---|-------|-----------------|---------| +| Spare bit 7 to 3 | | | | | Drop Reason | | | 1 | Payload | +| Number of PDUs Dropped | | | | | | | | 1 | | +| SN 1 | | | | | | | | 1 | | +| SN 1 (cont) | | | | | | | Spare | 1 | | +| PDU 1 Index | | | | | | | | 1 | | +| ... | | | | | | | | 1 | | +| SN N | | | | | | | | 1 | | +| SN N (cont) | | | | | | | Spare | 1 | | +| PDU N Index | | | | | | | | 1 | | +| Spare Extension | | | | | | | | 0-32 | | + +**Figure 39: HS-DSCH PDU DROP INDICATION payload structure** + +##### 6.3.3.13.2 Drop Reason + +**Description:** The *Drop Reason* IE is used in HS-DSCH PDU DROP INDICATION Control Frame. It indicates the reason of drop of HS-DSCH PDUs in Node B. + +**Value range:** + +- 0 too long delay in MAC-hs/ehs buffer +- 1 unsuccessful HARQ due to T1 timer expiry +- 2 TNL Congestion – detected by frame loss +- 3 to 7 are reserved + +**Field length:** 3 bits + +6.3.3.13.3 PDU Index + +**Description:** The *PDU Index* IE identifies the PDU index in the HS-DSCH DATA FRAME.**Value range:** {0-255}.**Field length:** 8 bits. + +## 7 Frame protocol error handling + +A received frame protocol frame with unknown Information element or with illegal Information element value shall be ignored. Frame protocol frames sent with a CFN in which the radio resources assigned to the associated Iub data port are not available, shall be ignored. + +### 7.1 Error detection + +Error detection is provided on frames through a Cyclic Redundancy Check. The CRC for the payload is 16 and for the data frame header is 7 [FDD - or 11] bits and for control frames is 7 bits. + +#### 7.1.1 CRC Calculation + +The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{CRC16}(D) = D^{16} + D^{15} + D^2 + 1.$$ + +$$[FDD - g_{CRC11}(D) = D^{11} + D^9 + D^8 + D^2 + D + 1.]$$ + +$$g_{CRC7}(D) = D^7 + D^6 + D^2 + 1.$$ + +Denote the bits in a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ , and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of a protected data and $L_i$ is 16 or 7 depending on the CRC length. + +The encoding is performed in a systematic form, which means that in GF (2), the polynomial for the payload. + +$$a_1 D^{A_i+15} + a_2 D^{A_i+14} + \dots + a_{A_i} D^{16} + p_1 D^{15} + p_2 D^{14} + \dots + p_{15} D^1 + p_{16}$$ + +yields a remainder equal to 0 when divided by $g_{CRC16}(D)$ , [FDD - the polynomial for the data frame header with 11 bit CRC + +$$a_1 D^{A_i+11} + a_2 D^{A_i+10} + \dots + a_{A_i} D^{11} + p_1 D^{10} + p_2 D^9 + \dots + p_{10} D^1 + p_{11}$$ + +yields a remainder equal to 0 when divided by $g_{CRC11}(D)$ , ] the polynomial for the data frame header and control frames with 7 bit CRC. + +$$a_1 D^{A_i+6} + a_2 D^{A_i+5} + \dots + a_{A_i} D^7 + p_1 D^6 + p_2 D^5 + \dots + p_6 D^1 + p_7$$ + +yields a remainder equal to 0 when divided by $g_{CRC7}(D)$ . + +#### 7.1.1.1 Relation between input and output of the Cyclic Redundancy Check + +The bits after CRC attachment are denoted by $b_1, b_2, b_3, \dots, b_{B_i}$ , where $B_i = A_i + L_i$ . + +The parity bits for the payload are attached at the end of the frame: + +$$\begin{aligned} b_k &= a_k & k &= 1, 2, 3, \dots, A_i \\ b_k &= p_{(k-A_i)} & k &= A_i + 1, A_i + 2, A_i + 3, \dots, A_i + L_i \end{aligned}$$ + +The parity bits for the frame header and the control frames are attached at the beginning of the frame: + +$$\begin{aligned} b_k &= p_k & k &= 1, 2, 3, \dots, L_i \\ b_k &= a_{(k-L_i)} & k &= L_i + 1, L_i + 2, L_i + 3, \dots, L_i + A_i \end{aligned}$$ + +## Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------|--------| +| 09/2008 | | | | Creation of Rel-8 version based on v7.9.0. | 8.0.0 | +| 41 | RP-080587 | 0186 | | Introduction of frame formats supporting E-DCH for CELL_FACH and Idle over Iub | 8.0.0 | +| 41 | RP-080588 | 0188 | | Introduction of Enhanced UE DRX | 8.0.0 | +| 42 | RP-080856 | 0190 | 1 | Improve the data rate for Enhanced Cell_FACH state in FDD | 8.1.0 | +| 42 | RP-080850 | 0191 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.1.0 | +| 42 | RP-080858 | 0192 | | Corrections to IE definitions for E-DCH DATA FRAME and Common MAC flow | 8.1.0 | +| 42 | RP-080839 | 0194 | | Correction of CR182, allow node sync also for enhanced L2 | 8.1.0 | +| 43 | RP-090073 | 0196 | 1 | Correction of handling of Capacity Allocation and HS-DSCH Credits | 8.2.0 | +| 43 | RP-090074 | 0198 | 1 | Correction of value range for Ext Propagation Delay | 8.2.0 | +| 43 | RP-090076 | 0199 | | Correction of length of spare extension field | 8.2.0 | +| 44 | RP-090638 | 0200 | 1 | Clarification of HS-DSCH FP frame structure for enhanced CELL_FACH for 1.28Mcps TDD | 8.3.0 | +| 44 | RP-090630 | 0204 | | Correction of the value range of MAC PDU Size Extended IE in CCH FP Iub | 8.3.0 | +| 46 | RP-091180 | 0206 | 4 | Correction to the NodeB procedure when receiving uplink synchronization failure from physical layer for 1.28Mcp TDD | 8.4.0 | +| 46 | RP-091179 | 0208 | | Correction on the description of HS-DSCH DATA FRAME TYPE2 | 8.4.0 | +| 46 | RP-091181 | 0211 | | Silent Mode for Common E-DCH | 8.4.0 | +| 46 | RP-091181 | 0212 | | Correction on value range for Number of MAC-is SDU in frame | 8.4.0 | +| 46 | RP-091180 | 0214 | 1 | Correction of the limitation to FACH indicator for 1.28Mcps TDD | 8.4.0 | +| 46 | RP-091180 | 0216 | 1 | Clarification for eDRX Indication | 8.4.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v 8.4.0 | 9.0.0 | +| 46 | RP-091188 | 0207 | | Introduction of Cell Portion for 1.28 Mcps TDD | 9.0.0 | +| 47 | RP-100217 | 0218 | 1 | Clarification DCCH/DTCH transmission mechanism in enhanced CELL_PCH state | 9.1.0 | +| 47 | RP-100217 | 0220 | | Correction of the value range for RACH Measurement Result IE for 1.28Mcps TDD | 9.1.0 | +| 47 | RP-100229 | 0225 | | Corrections to the TS0 enhancement for the UE in CELL_FACH state for 1.28Mcps TDD | 9.1.0 | +| 48 | RP-100599 | 0233 | | Correction of HS-DSCH DATA FRAME TYPE3 | 9.2.0 | +| 49 | RP-100904 | 0240 | 1 | Addition of enhanced HS-SCCH support indicator in CELL_FACH | 9.3.0 | +| 49 | RP-100905 | 0244 | | HS-DSCH data transmission in enhanced CELL_FACH state and the relation to HS-DSCH physical layer category | 9.3.0 | +| 12/2010 | | | | Creation of Rel-10 version based on v. 9.3.0 | 10.0.0 | +| 50 | RP-101277 | 0245 | | Introduction of MU-MIMO to CTCH of Iub user plane | 10.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.0 | +| 51 | RP-110225 | 0251 | | Correction of propagation delay handling for E-DCH Data Frame | 10.1.0 | +| 52 | RP-110689 | 0255 | | Introduction of NodeB Operation for Common HS-DSCH SRB1 Transmission | 10.2.0 | +| 52 | RP-110688 | 0256 | 2 | Correction to mapping of MAC-is SDU to MAC-d PDU | 10.2.0 | +| 52 | RP-110683 | 0259 | | Special value for HS-DSCH DATA FRAME TYPE 2 RACH Measurement Result | 10.2.0 | +| 52 | RP-110685 | 0260 | | Correction to the References in 25.435 | 10.2.0 | +| 52 | RP-110681 | 0263 | | Correction of Logical Channel ID range used in Enhanced Cell-FACH | 10.2.0 | +| 53 | RP-111196 | 0268 | 2 | Addition of Cell Portion ID in the FACH DATA FRAME for 1.28Mcps TDD | 10.3.0 | +| 54 | RP-111651 | 0272 | 1 | Clarification on the timing of PICH/HS-SCCH | 10.4.0 | +| 54 | RP-111645 | 0275 | 1 | Indicator for DTXDRX HS-SCCH order | 10.4.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 58 | RP-121725 | 0284 | 2 | Introduction of Further Enhancements to CELL_FACH feature | 11.1.0 | +| 58 | RP-121727 | 0289 | 2 | Supporting Multiflow Operation | 11.1.0 | +| 58 | RP-121725 | 0290 | 1 | 2nd DRX cycle and fallback to PRACH R99 | 11.1.0 | +| 58 | RP-121724 | 0292 | | Correction of missing EI in Figure 2B of HS-DSCH DATA FRAME TYPE 2 | 11.1.0 | +| 58 | RP-121727 | 0293 | | Merge of all changes from CRs to Figure 21B and corresponding descriptions | 11.1.0 | +| 59 | RP-130206 | 0295 | 1 | Clean-up for Multiflow | 11.2.0 | +| 06/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 64 | RP-140875 | 0306 | 3 | Introduction of Cell Reselection indications | 12.0.0 | +| 64 | RP-140905 | 0313 | 1 | Carrying multiple UEs' data in one HS-DSCH DATA FRAME TYPE3 | 12.0.0 | +| 65 | RP-141608 | 0314 | 1 | Rapporteur Review – change figures to table style | 12.1.0 | +| 70 | RP-152090 | 0315 | 2 | Introduction of IDLE to CONNECTED mode transition optimization | 13.0.0 | +| 74 | RP-162338 | 0317 | | Introduction of DRX enhancements | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25442/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-16/25_series/25442/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab883dbc1fe4681554d78ee040d52f1e8d8694f7 --- /dev/null +++ b/marked/Rel-16/25_series/25442/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:803b6d1b2f00231d001315b0ec3530de8b830c02c3a2c67e61f7e147930b3496 +size 21193 diff --git a/marked/Rel-16/25_series/25442/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/marked/Rel-16/25_series/25442/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae96bc67b65da0268d9f30f33abb485598257fe4 --- /dev/null +++ b/marked/Rel-16/25_series/25442/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aba42777372c62368380617784119e7ede8c3182b19ac8ec66738bafe89de517 +size 27778 diff --git a/marked/Rel-16/25_series/25442/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-16/25_series/25442/5d76c2e9976aaf97001ee189908830fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7a6b9e98a4d66994884d5b3206b00edc34ac442 --- /dev/null +++ b/marked/Rel-16/25_series/25442/5d76c2e9976aaf97001ee189908830fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e85ef88603fce02671d654a2fe1d4c04b2a89c68fd13dac95f1f63c99ed9fa9b +size 83150 diff --git a/marked/Rel-16/25_series/25442/raw.md b/marked/Rel-16/25_series/25442/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5bee993e25304d2005506f960c25852c75acca93 --- /dev/null +++ b/marked/Rel-16/25_series/25442/raw.md @@ -0,0 +1,165 @@ + + + + + + +# Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Definitions and abbreviations ..... 5 + - 3.1 Definitions..... 5 + - 3.2 Abbreviations ..... 5 +- 4 Implementation Specific O&M Transport ..... 6 + - 4.1 Requirements..... 6 + - 4.2 Routing ..... 6 + - 4.3 Transport Bearer..... 7 + - 4.3.1 ATM Transport Option..... 7 + - 4.3.2 IP Transport Option..... 7 +- Annex A (informative): Change history..... 9 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the transport of implementation specific O&M signalling between Node B and the Management Platform in case that the transport is routed via the RNC. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] Void +- [2] Void +- [3] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5 Specification". +- [4] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM". +- [5] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5". +- [6] IETF RFC 791 (1981-09): "Internet Protocol". +- [7] Void +- [8] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport&Transport Signalling for DCH". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Logical O&M:** Logical O&M is the signalling associated with the control of logical resources owned by the RNC but physically implemented in Node B. + +**Implementation Specific O&M:** Implementation Specific O&M functions depend on the implementation of the Node B, both for its hardware and software components. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|-----------------------------| +| AAL5 | ATM Adaptation Layer type 5 | +| ATM | Asynchronous Transfer Mode | +| ARP | Address Resolution Protocol | +| RFC | Request For Comment | +| IP | Internet Protocol | +| O&M | Operation and Maintenance | +| RNC | Radio Network Controller | +| TNL | Transport Network Layer | + +# 4 Implementation Specific O&M Transport + +## 4.1 Requirements + +While this specification only addresses the transport of Node B Implementation Specific O&M signalling, many of the following requirements are derived from generic requirements for O&M of UMTS network elements: + +- Common O&M infrastructure for all network elements. +- Independence from various data link protocols. +- Support of various higher layer protocols and applications. +- Secure transmission. +- No Impact of O&M transport on traffic transport and signalling. +- Re-use of existing transport facilities, i.e. co-existence of Iub and Implementation Specific O&M on the same bearer. + +## 4.2 Routing + +It is the responsibility of the RNC to route Implementation Specific O&M signalling traffic. The traffic exchanged over this signalling link is completely transparent to the RNC. Both RNC and Node B have to support the routing of Implementation specific O&M via the RNC. + +![Figure 1: Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The Management Platform(s) contains three models: Node B Management Model (blue), RNC Management Model (blue), and Node B Management Model (yellow). The RNC contains an RNC O&M section with a Node B Logical O&M model. Each Node B contains an Implementation Specific O&M section and a Logical O&M section. Blue lines represent Implementation Specific O&M Transport paths from the Management Platform(s) through the RNC to the Node Bs. Green lines represent Logical O&M paths between the Node Bs and the RNC. Dashed lines represent the Iub interface between the Node Bs and the RNC. Solid lines represent the Physical bearer between the Node Bs and the RNC.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +Figure 1: Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The Management Platform(s) contains three models: Node B Management Model (blue), RNC Management Model (blue), and Node B Management Model (yellow). The RNC contains an RNC O&M section with a Node B Logical O&M model. Each Node B contains an Implementation Specific O&M section and a Logical O&M section. Blue lines represent Implementation Specific O&M Transport paths from the Management Platform(s) through the RNC to the Node Bs. Green lines represent Logical O&M paths between the Node Bs and the RNC. Dashed lines represent the Iub interface between the Node Bs and the RNC. Solid lines represent the Physical bearer between the Node Bs and the RNC. + +Figure 1: Implementation Specific O&M Transport via RNC + +## 4.3 Transport Bearer + +An appropriate transport bearer for Implementation Specific O&M should consider the requirements listed in subclause 4.1. IP (IETF RFC 791 [6]) should be the transport mechanism in order to allow a data link independent support of a variety of O&M applications and protocols for the Implementation Specific O&M of the Node B. + +IP datagrams containing O&M signalling have to be carried over the same bearer as Iub. There are two options for the implementation specific O&M signalling bearer in Iub. + +- 1) ATM Transport option +- 2) IP Transport option + +### 4.3.1 ATM Transport Option + +The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of ATM transport option in Iub: + +![Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks connected by a horizontal line representing the Iub interface. The left stack is labeled 'RNC' and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is labeled 'Node B' and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. The PHY layers of both stacks are connected to each other.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks connected by a horizontal line representing the Iub interface. The left stack is labeled 'RNC' and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is labeled 'Node B' and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. The PHY layers of both stacks are connected to each other. + +**Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option)** + +AAL5 shall be used according to ITU-T Recommendation I.363.5 [3]. + +AAL5 virtual circuits are used to transport the IP packets containing Implementation Specific O&M signalling data between Node B and RNC. Multiple VCs can be used over the interface. An association shall be made between a VC and the IP addresses that are related to this VC in the peer node side. This association can be made using O&M or using ATM Inverse ARP according to Classical IP over ATM. + +Classical IP over ATM protocols are used to carry the IP packets over the ATM transport network. Classical IP over ATM is specified in IETF RFC 2225 [4]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 2684 [5]. + +### 4.3.2 IP Transport Option + +The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of IP transport option in Iub: + +![Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL). The diagram shows two protocol stacks connected by a horizontal line representing the Iub interface. The left stack is labeled 'RNC' and consists of three layers: IP at the top, Datalink layer in the middle (containing IP and Datalink sub-layers), and PHY at the bottom. The right stack is labeled 'Node B' and consists of four layers: Implementation Specific O&M at the top, followed by IP, IP (if tunnelled), Datalink layer, and PHY at the bottom. The PHY layers of both stacks are connected to each other.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg) + +Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL). The diagram shows two protocol stacks connected by a horizontal line representing the Iub interface. The left stack is labeled 'RNC' and consists of three layers: IP at the top, Datalink layer in the middle (containing IP and Datalink sub-layers), and PHY at the bottom. The right stack is labeled 'Node B' and consists of four layers: Implementation Specific O&M at the top, followed by IP, IP (if tunnelled), Datalink layer, and PHY at the bottom. The PHY layers of both stacks are connected to each other. + +**Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL)** + +Implementation specific O&M signalling is conveyed by IP between the Node B and the RNC. IP-in-IP tunneling may be applied when the Iub Transport Network Layer is used. + +IP based Transport Network Layer of Iub is further defined in TS 25.426 [8]. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110685 | 0005 | | Removal of unused references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25444/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-16/25_series/25444/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2133cd9bcde1a0923510b6ab2a78a199e7b8bfe5 --- /dev/null +++ b/marked/Rel-16/25_series/25444/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c6696c162d096352762dd862b94778867a3dd6d7d3d1d456d5b18158d4821b3 +size 76101 diff --git a/marked/Rel-16/25_series/25444/raw.md b/marked/Rel-16/25_series/25444/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..db31b6bcadb6e6f0b0cb5d4bf13d014ebf97c8f5 --- /dev/null +++ b/marked/Rel-16/25_series/25444/raw.md @@ -0,0 +1,214 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Data Link Layer ..... | 6 | +| 5 Circuit switched domain ..... | 6 | +| 5.1 Transport Network User Plane without bandwidth efficiency mechanisms..... | 6 | +| 5.3 Transport Network User Plane with bandwidth efficiency mechanisms ..... | 6 | +| 5.3.1 General ..... | 6 | +| 5.3.2 Transport format..... | 6 | +| 5.3.2.1 UDP ..... | 6 | +| 5.3.2.2 RTP..... | 6 | +| 5.3.2.2.1 Transport Format for multiplexing RTP packets ..... | 6 | +| 6 Packet switched domain..... | 8 | +| 6.1 Transport network user plane..... | 8 | +| Annex A (informative): Change history..... | 9 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards for user data transport protocols between the HNB and HNB-GW/CN. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] Void +- [3] Void +- [4] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling". +- [5] Void +- [6] Void +- [7] Void +- [8] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [9] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real-Time Applications". +- [10] Void +- [11] Void +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [12] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [12]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [12] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [12]. + +| | | +|--------|---------------------| +| CN | Core Network | +| CS | Circuit Switched | +| HNB | Home Node B | +| HNB-GW | Home Node B Gateway | +| IP | Internet Protocol | + +| | | +|-----|------------------------------| +| PS | Packet Switched | +| RFC | Request For Comment | +| RTP | Real-Time Transport Protocol | +| UDP | User Datagram Protocol | + +# --- 4 Data Link Layer + +Any data link protocol that fulfils the requirements toward the upper layer may be used. + +# --- 5 Circuit switched domain + +## 5.1 Transport Network User Plane without bandwidth efficiency mechanisms + +Defined in Reference TS 25.414 [4], subclause 5.1.3. + +NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 5.1.3, may be directly between HNB and the CN. + +## 5.3 Transport Network User Plane with bandwidth efficiency mechanisms + +### 5.3.1 General + +Bandwidth efficient transport of Uplink CS data payload PDUs may be supported over bearer transport mechanisms for the Iuh interface, using a bearer transport multiplexing scheme that allows transporting several RTP PDUs of different user plane connections within one packet. + +### 5.3.2 Transport format + +UDP/IP shall be applied on Iuh between HNB and HNB GW as described in TS 25.414 [4] for Iu between RNC and CN, subclause 5.1.3, except as stated below. + +#### 5.3.2.1 UDP + +The path protocol used shall be UDP (IETF RFC 768 [8]). If multiplexing is applied the source UDP port number shall indicate the local termination used to combine the multiplexed packet and the destination UDP port number shall indicate the remote port number where PDUs are demultiplexed. + +#### 5.3.2.2 RTP + +RTP (IETF RFC 1889[9]) shall be applied as described in TS 25.414 [4], subclause 5.1.3.3 and requirements below. + +##### 5.3.2.2.1 Transport Format for multiplexing RTP packets + +Use of multiplexing shall be negotiated between the HNB and HNB-GW. + +Before each multiplexed RTP/codec payload PDU inserted into the UDP/IP packet a Multiplex Header, which identifies the multiplexed packet, shall be inserted. + +| Bits | | | | | | | | Number
of Octets | | | | | | | | | +|----------------------------------------------------|--------------------------------------------------------|---|---|---|---|---|---|---------------------|---------------------|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | +| Source IP, Dest IP, ... | | | | | | | | 20/40 | IP | | | | | | | | +| Source Port, Dest Port=, Length, ... | | | | | | | | 8 | UDP | | | | | | | | +| T=0 | Mux ID = (Destination UDP Port of multiplexed PDU) / 2 | | | | | | | 2 | Multiplex
Header | | | | | | | | +| | Length Indicator (LI) = n | | | | | | | 1 | | | | | | | | | +| R | Source ID = (Source UDP Port of multiplexed PDU) / 2 | | | | | | | 2 | | | | | | | | | +| Full RTP packet | | | | | | | | n | RTP header | | | | | | | | +| | | | | | | | | | RTP Payload | | | | | | | | +| Multiplex Header | | | | | | | | 5 | Multiplex
Header | | | | | | | | +| Full RTP packet | | | | | | | | m | RTP header | | | | | | | | +| | | | | | | | | | RTP Payload | | | | | | | | +| ... | | | | | | | | | | | | | | | | | + +**Figure 1: UDP/IP Packet with multiplexed RTP payload PDUs** + +The Multiplex Header includes : + +- T bit. + +The field has two possible values. Value 0 shall be used for an uncompressed RTP header, as described in the present sub-clause. Value 1 is FFS. + +- Mux ID, 15 bits. + +For identification of different user plane connections. The value shall be the UDP destination port of the corresponding non-multiplexed RTP PDU packet divided by two (only even numbered ports are used for RTP sessions). + +- Length Indicator (LI), 8 bits, unsigned integer. + +Gives the length of the multiplexed RTP PDU packet (RTP header + RTP) in bytes (the last byte of the RTP PDU is padded to the next byte boundary if necessary). Maximum length is 255 bytes. This LI allows to calculate where the next Multiplex Header for the next multiplexed RTP PDU packet starts. + +- R bit. + +Reserved for future use. Shall be set to 0 by the sending entity and be ignored by the receiving entity. + +- Source ID, 15 bits. + +For identification of the different connections. The value shall be the source UDP port of the corresponding non-multiplexed RTP/codec PDU packet divided by two (only even numbered ports are used for RTP sessions). + +The multiplexed RTP PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The multiplexed RTP packet PDU shall follow the rules defined in IETF RFC 1889 [9] and consists of the full RTP header and the RTP payload. If the multiplexed RTP packet PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros. + +The multiplexing method does not limit the number of packets being multiplexed and it is thus the data link layer protocol that defines the maximum frame size. In order to avoid additional delay in the network the packets should not be delayed more than 1 ms to 2 ms, which also effectively limits the number of multiplexed packets and makes the multiplexing-jitter low. + +![Diagram illustrating the structure of multiplexed packets. It shows two original packets with IP, UDP, RTP, and IuUP headers being multiplexed into two MUX packets. The MUX packets include a common header (IP, UDP, MUX) followed by the RTP and IuUP frames. The diagram includes callouts for 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy', and a 'Negotiated UDP MUX port.' label. A 'max 255 bytes' dimension line is shown at the bottom.](731f533b0599c8e42a063f06e4332045_img.jpg) + +The diagram illustrates the process of multiplexing two RTP streams into a single transport packet. At the top, two separate packets are shown. The first packet has a header section containing IP (20/40 bytes), UDP (8), and RTP (12) fields, followed by an IuUP frame (9 ...). A callout box points to the UDP header with the text 'Dest. & Source UDP Port: xxxx'. The second packet has a similar header section, with a callout box pointing to its UDP header with the text 'Dest. & Source UDP Port: yyyy'. Below these, the multiplexed packets are shown. The first MUX packet has a 'Common header' consisting of IP (20/40 bytes), UDP (8), and MUX (5) fields. This is followed by the first RTP (12) and IuUP frame (9 ...). A callout box points to the UDP header of the MUX packet with the text 'Negotiated UDP MUX port.'. The second MUX packet has the same common header and is followed by the second RTP (12) and IuUP frame (9 ...). A callout box points to the UDP header of the second MUX packet with the text 'Dest. & Source UDP Port: yyyy'. A dimension line at the bottom indicates the total length of the MUX packet headers and the start of the first RTP frame is 'max 255 bytes'. + +Diagram illustrating the structure of multiplexed packets. It shows two original packets with IP, UDP, RTP, and IuUP headers being multiplexed into two MUX packets. The MUX packets include a common header (IP, UDP, MUX) followed by the RTP and IuUP frames. The diagram includes callouts for 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy', and a 'Negotiated UDP MUX port.' label. A 'max 255 bytes' dimension line is shown at the bottom. + +Figure 2: Example of multiplexed packet with two RTP frames + +# 6 Packet switched domain + +## 6.1 Transport network user plane + +Defined in Ref TS 25.414 [4] subclause 6.1.3. + +NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 6.1.3, may be directly between HNB and the CN. + +# Annex A (informative): Change history + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|------------------------------------------------------------|--------| +| | | | | Initial Skeleton | 0.1.0 | +| | | | | Addition of TP for signalling for bandwidth efficiency | 0.2.0 | +| | | | | Presented for approval at RAN#46 | 2.0.0 | +| 46 | RP-091104 | | | Approved at RAN#46 | 9.0.0 | +| | | | | Editorial clean up | 9.0.1 | +| | | | | Version number in the change history corrected | 9.0.2 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.3 | +| 03/2011 | | | | Created Rel-10 version based on v9.0.3 | 10.0.0 | +| 52 | RP-110684 | 0002 | | Correction of references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25450/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/25_series/25450/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc144d0f264364a2aaecff298a3f1e55802cbb55 --- /dev/null +++ b/marked/Rel-16/25_series/25450/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e4a94eb2b802888bb3940d39c193c87a9c4db6d957a2504c430a2662cfaa881 +size 54834 diff --git a/marked/Rel-16/25_series/25450/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25450/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d33bf392c944dfb9492124fc49b0a2eeffa385c6 --- /dev/null +++ b/marked/Rel-16/25_series/25450/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a984e084006b51c3a3c689dc4f3b9d244f4aa1359f17936d3eeec162021fbf +size 23725 diff --git a/marked/Rel-16/25_series/25450/raw.md b/marked/Rel-16/25_series/25450/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8853a4cc42aaa22ccda936812c9e1466fc383b9a --- /dev/null +++ b/marked/Rel-16/25_series/25450/raw.md @@ -0,0 +1,337 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 3.3 Specification Notations ..... | 6 | +| 4 General Aspects ..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 Iupc Interface General Principles ..... | 7 | +| 4.3 Iupc Interface Specification Objectives ..... | 8 | +| 4.4 Iupc Interface Capabilities ..... | 8 | +| 4.4.1 General ..... | 8 | +| 4.4.2 Position Calculation Services ..... | 8 | +| 4.4.3 Information Exchange Services..... | 8 | +| 4.4.4 SAS Centric Position Services ..... | 8 | +| 4.5 Iupc Interface Characteristics..... | 8 | +| 4.5.1 Uses of SCCP ..... | 8 | +| 4.5.1.1 General..... | 8 | +| 4.5.1.2 SCCP Addressing ..... | 8 | +| 4.5.1.3 SCCP connection establishment ..... | 9 | +| 4.5.1.4 SCCP connection release..... | 9 | +| 4.5.1.5 General SCCP Abnormal Conditions ..... | 10 | +| 5 Functions of the Iupc Interface Protocols ..... | 10 | +| 5.1 List of Functions..... | 10 | +| 5.2 Management of GPS Related Data..... | 10 | +| 5.3 Management of Position Calculation Functions ..... | 10 | +| 5.4 Management of SAS Centric Position Functions..... | 10 | +| 5.5 Management of GANSS Related Data..... | 11 | +| 6 Other Iupc Interface Specifications..... | 11 | +| 6.1 UTRAN Iupc Interface: Layer 1 (TSG RAN 25.451)..... | 11 | +| 6.2 UTRAN Iupc Interface: Signalling Transport (TSG RAN 25.452) ..... | 11 | +| 6.3 PCAP Specification (TSG RAN 25.453) ..... | 11 | +| 6.4 Summary of UTRAN Iupc Interface Technical Specifications ..... | 11 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the TSG RAN TS 25.45z series of UMTS Technical Specifications that define the Iupc Interface. The Iupc interface is a logical interface for the interconnection of Stand-Alone SMLC (SAS) and Radio Network Controller (RNC) components of the Universal Terrestrial Radio Access Network (UTRAN) for the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] 3GPP TS 25.451: "UTRAN Iupc Interface: Layer 1". +- [3] 3GPP TS 25.452: "UTRAN Iupc Interface: Signalling Transport". +- [4] 3GPP TS 25.453: "UTRAN Iupc Interface PCAP Signalling". +- [5] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [6] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [7] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [8] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [9] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [10] Void +- [11] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Stand-Alone SMLC (SAS):** As defined in TS 25.305 [11]. + +**RNC Centric:** In this mode of operation (defined in TS 25.305 [11]), the RNC is responsible for position method selection and initiation of the selected positioning method. Once a position method is selected, the RNC may interact with the SAS to exchange data as well as for execution of the selected positioning method. + +**SAS Centric:** In this mode of operation (defined in TS 25.305 [11]), the SAS is responsible for position method selection and initiation of the selected positioning method. Once a position method is selected, the SAS may interact with the RNC to exchange data to enable it to execute the selected positioning method. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------------------| +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| GT | Global Title | +| M3UA | SS7 MTP3 User Adaptation Layer | +| PCAP | Position Calculation Application Part | +| RNC | Radio Network Controller | +| SAS | Stand-Alone SMLC | +| SCCP | Signalling Connection Control Part | +| SMLC | Serving Mobile Location Centre | +| SPC | Signalling Point Code | +| SRNC | Serving Radio Network Controller | +| SS7 | Signalling System N° 7 | +| SSN | Sub-System Number | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunication System | +| UTRAN | Universal Terrestrial Radio Access Network | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcpss TDD and 1.28Mcpss TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68 Mcps TDD, 3.84Mcpss TDD and 1.28Mcpss TDD. +- [7.68Mcpss TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcpss TDD]" applies only to 7.68Mcpss TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcpss TDD]" and the section following the heading applies only to 7.68Mcpss TDD. +- [3.84Mcpss TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcpss TDD]" applies only to 3.84Mcpss TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcpss TDD]" and the section following the heading applies only to 3.84Mcpss TDD. +- [1.28Mcpss TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcpss TDD]" applies only to 1.28Mcpss TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcpss TDD]" and the section following the heading applies only to 1.28Mcpss TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 7.68 Mcps TDD, 3.84Mcpss TDD and 1.28Mcpss TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [7.68Mcpss TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcpss TDD - " applies only to 7.68Mcpss TDD. Multiple sequential paragraphs applying only to 7.68Mcpss TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcpss TDD specific paragraphs. + +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- Procedure When referring to a procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. RNSAP Basic Mobility Procedures. +- Message When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. +- Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH data frame. +- + +# 4 General Aspects + +## 4.1 Introduction + +The logical interface between a RNC and a SAS within the UTRAN is referred to the Iupc interface. + +## 4.2 Iupc Interface General Principles + +The general principles for the specification of the Iupc interface are as follows: + +- the Iupc interface should be open; +- complex functionality shall as far as possible be avoided over Iupc. Advanced optimisation solutions may be added in later versions of the standard; +- from a logical standpoint, the Iupc is a point-to-point signalling interface between an RNC and SAS within the UTRAN, even though there may not be a direct physical connection between these two nodes; +- one RNC may connect to one SAS. One SAS may provide services to one RNC; +- neither the physical structure nor any internal protocols of the RNC or SAS shall be visible over Iupc and are thus not limiting factors, e.g., when introducing future technology. + +## 4.3 Iupc Interface Specification Objectives + +The Iupc interface specifications shall facilitate the following: + +- inter-connection of RNCs and SASs from different manufacturers; +- separation of Iupc interface Application functionality and Transport Network functionality to facilitate introduction of future technology. + +## 4.4 Iupc Interface Capabilities + +### 4.4.1 General + +The Iupc interface connects a RNC and a SAS. + +### 4.4.2 Position Calculation Services + +The Iupc interface enables an SRNC and a SAS to exchange information that is related to the positioning of a single UE. These exchanges involve the transfer of UE Positioning measurement data or UE position estimate data. + +### 4.4.3 Information Exchange Services + +The Iupc interface enables an RNC to request specific GNSS (GPS or GANSS) related data from an SAS on demand, on modification, or at regular intervals. + +### 4.4.4 SAS Centric Position Services + +The Iupc interface enables an RNC and a SAS to exchange information that is related to the positioning of a single UE, using SAS Centric mode of operation. + +## 4.5 Iupc Interface Characteristics + +### 4.5.1 Uses of SCCP + +#### 4.5.1.1 General + +The SCCP, ITU-T Rec. Q.711 [5], ITU-T Rec. Q.712 [6], ITU-T Rec. Q.713 [7] and ITU-T Rec. Q.714 [8], is used to transport messages between the RNC and SAS. One user function of the SCCP, called Positioning Calculation Application Part (PCAP), is defined TS 25.453 [4]. + +Both connectionless and connection-oriented procedures are used to support PCAP. TS 25.453 [4] explain whether connection oriented or connectionless services should be used for a layer 3 procedure. + +#### 4.5.1.2 SCCP Addressing + +The inclusion of caller party address in SCCP message is mandatory. PCAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. When GT addressing is utilised, the following settings shall be used: + +- SSN Indicator = 1 (PCAP SSN as defined in TS 23.003 [9]). +- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator). +- Translation Type = 0000 0000 (not used). +- Numbering Plan = 0001 (E.163/4). +- Nature of Address Indicator = 000 0100 (International Significant Number). +- Encoding Scheme = 0001 or 0010 (BCD, odd or even). +- Routing indicator = 0 or 1 (route on GT or PC/SSN). + +When used, the GT shall be the E.164 address of the relevant node. + +#### 4.5.1.3 SCCP connection establishment + +##### Information Exchange services + +A new SCCP connection is established when the RNC initiates a class-1 elementary procedure for Information Exchange services and there is no signalling bearer existing for this purpose. + +An SCCP connection is always established by the RNC. + +##### SAS Centric Position services + +A new SCCP connection is established when the RNC initiates a class-1 elementary procedure, with respect to each new positioning request, for SAS Centric Position services. + +An SCCP connection is always established by the RNC. + +##### Initiation + +The RNC sends SCCP CONNECTION REQUEST message to the SAS. A PCAP message is included in the user data field of the SCCP CONNECTION REQUEST message. **Termination** + +- **successful outcome:** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a PCAP message in the user data field, is returned to the RNC. +- **unsuccessful outcome:** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the RNC. This message may contain a PCAP message. + +![](0b87abe67b21a93777287649c33e755d_img.jpg) + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
RNC SAS
CR {SSN=SAS, a1=x, PCAP message}
----->
CC {a1=y, a2=x, PCAP message or no user data}
<-----
or
CREF{a2=x, PCAP message or no user data}
<-----
a1 = source local reference,
a2 = destination local reference,
x = SCCP connection reference at the RNC,
y = SCCP connection reference at the SAS.
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Figure 1: Setting-up of RNC Initiated SCCP Signalling Connection with SAS** + +#### 4.5.1.4 SCCP connection release + +This procedure is always initiated by the RNC. An SCCP connection is released when the RNC realises that a given signalling connection is no longer required. This is accomplished by the RNC sending a SCCP RELEASED message. + +#### 4.5.1.5 General SCCP Abnormal Conditions + +If a user-out-of-service information or signalling-point-inaccessible information is received by the RNC, no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received. + +When a user-out-of-service information or signalling-point-inaccessible is received by the RNC, an optional timer may be started. When the timer expires, all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped. + +If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the SAS procedures are being performed or while a dedicated resource is still allocated, the procedures associated to that SCCP connection shall be terminated (at both the RNC side and the SAS side). + +# 5 Functions of the Iupc Interface Protocols + +## 5.1 List of Functions + +The list of functions on the Iupc interface is the following: + +1. Management of GPS Related Data; +2. Management of Position Calculation Functions; + +3. Management of SAS Centric Position Functions; +4. Management of GANSS Related Data, + +## 5.2 Management of GPS Related Data + +An RNC may request GPS related data from an SAS in order to provide GPS assistance data to a single UE. Alternatively, an RNC may request GPS related data from an SAS in order to support the broadcast of GPS assistance data to multiple UEs in a particular area via system information messages. Each type of GPS related data may be requested on demand, on modification, or at regular intervals. + +## 5.3 Management of Position Calculation Functions + +To support a *UE-assisted* positioning attempt involving a single UE, an RNC provides an SAS with one or more sets of + +- GPS or GANSS measurement data, +- ODTOA measurement data, +- Cell ID measurement data. + +Subsequently, the SAS calculates the position estimate of the specific UE and returns this result to the RNC. + +## 5.4 Management of SAS Centric Position Functions + +In the SAS Centric mode of operation, the RNC may initiate a positioning event, the SAS may activate a positioning method requesting the RNC for relevant data, and on completion of the position determination process the SAS may return the final response to the RNC. In addition, during an ongoing positioning event, the RNC may send the SAS a modified set of positioning parameters, or the RNC may even instruct the SAS to abort the positioning process itself. + +## 5.5 Management of GANSS Related Data + +This management of the GANSS Related Data is the same as the management of the GPS Related Data described in section 5.2, except that it is applicable to Galileo and Additional Navigation Satellite Systems instead of GPS. + +# --- 6 Other Iupc Interface Specifications + +## 6.1 UTRAN Iupc Interface: Layer 1 (TSG RAN 25.451) + +TS 25.451 [2] specifies the standards allowed for implementation of Layer 1 (physical layer) on the Iupc interface. + +## 6.2 UTRAN Iupc Interface: Signalling Transport (TSG RAN 25.452) + +TS 25.452 [3] specifies the signalling transport related to PCAP signalling to be used across the Iupc interface. + +## 6.3 PCAP Specification (TSG RAN 25.453) + +TS 25.453 [4] specifies the standards for PCAP specification to be used over the Iupc interface. + +## 6.4 Summary of UTRAN Iupc Interface Technical Specifications + +The relationship between the technical specifications that define the UTRAN Iupc interface is shown in figure 2. + +![Diagram of lopc Interface Technical Specifications showing three layers: Radio Network Layer (PCAP, TS 25.453), Transport Layer (PCAP, Transport, TS 25.452), and Physical Layer (TS 25.451).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the technical specifications for the lopc interface, organized into three layers: + +- Radio Network Layer:** This top layer is associated with the label "Radio Network Layer" on the left. It contains a box with "PCAP" and "TS 25.453". +- Transport Layer:** This middle layer is associated with the label "Transport Layer" on the left. It contains a box with "PCAP", "Transport", and "TS 25.452". +- Physical Layer:** This bottom layer is represented by a box containing "Physical Layer TS 25.451". + +Vertical dashed lines connect the top two layers, indicating a continuous interface structure. + +Diagram of lopc Interface Technical Specifications showing three layers: Radio Network Layer (PCAP, TS 25.453), Transport Layer (PCAP, Transport, TS 25.452), and Physical Layer (TS 25.451). + +**Figure 2: lopc Interface Technical Specifications.** + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.2.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110685 | 0010 | 1 | References cleanup (25,450) | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25451/raw.md b/marked/Rel-16/25_series/25451/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..884c725daa01ab33e5b89e0580e6aad3baefbd0f --- /dev/null +++ b/marked/Rel-16/25_series/25451/raw.md @@ -0,0 +1,77 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 4 Iupc Layer 1 ..... | 5 | +| Annex A (informative): Change History..... | 6 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the Iupc interface. + +The specification of transmission delay requirements and O&M requirements is 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 25.411: "UTRAN Iu interface Layer 1". + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply. + +# --- 4 Iupc Layer 1 + +The Iupc Layer 1 shall comply with the requirements of clause 4 in TS 25.411 [1]. + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|----------|----|-----|--------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| 03/2011 | - | - | - | Creation of Rel-10 version based on v9.0.0 | 10.0.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25460/raw.md b/marked/Rel-16/25_series/25460/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ce7427cecad563587e77e2cea6c158969188cc1e --- /dev/null +++ b/marked/Rel-16/25_series/25460/raw.md @@ -0,0 +1,84 @@ + + + + + + +# --- Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 to 6 Void..... 5 + +7 Iuant interface: General aspects and principles..... 5 + +**Annex A: Void..... 6** + +Annex B (informative): Change History..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +See TS 37.460 [8]. + +# --- 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]-[7] Void + +[8] 3GPP TS 37.460: "Iuant interface: General aspects and principles". + +# --- 3 to 6 Void + +# --- 7 Iuant interface: General aspects and principles + +See TS 37.460 [8]. + +# --- Annex A: Void + +# Annex B (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|------------------------------------------------------------|--------| +| 06/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 40 | RP-080309 | 0007 | | Correction of figure 6.4.1 | 8.0.0 | +| 43 | RP-090085 | 0008 | 1 | RET and TMA support in LTE | 8.1.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.1.0 | 9.0.0 | +| 01/2011 | - | - | - | Creation of Rel-10 version based on v9.0.0 | 10.0.0 | +| 03/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.1 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2019-04 | RAN#83 | RP-190557 | 0019 | - | F | Transfer of luant interface specification from 25-series to 37-series | 15.1.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25461/raw.md b/marked/Rel-16/25_series/25461/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..157111caadb0c11d453d40a6d676a1406a9aa3a5 --- /dev/null +++ b/marked/Rel-16/25_series/25461/raw.md @@ -0,0 +1,152 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 to 4 Void..... | 5 | +| 5 Iuant interface: Layer 1 ..... | 5 | +| Annex A: Void ..... | 6 | +| Annex B (informative): Change history..... | 7 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +See TS 37.461 [7]. + +# --- 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]-[6] Void. + +[7] 3GPP TS 37.461: "Iuant interface: Layer 1". + +# --- 3 to 4 Void + +# --- 5 Iuant interface: Layer 1 + +See TS 37.461 [7]. + +# --- Annex A: Void + +# Annex B (informative): Change history + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|-----|-----|------------------------------------------------------------------------------------------|--------| +| TSG-RAN#25 | RP-040344 | - | - | presentation to TSG-RAN for information | 1.0.0 | +| TSG-RAN#25 | RP-040344 | - | - | approved at TSG-RAN#25 and placed under change control | 6.0.0 | +| 26 | RP-040444 | 1 | | DC power supply distribution | 6.1.0 | +| 26 | RP-040444 | 2 | 1 | Improved demodulator characteristics specification | 6.1.0 | +| 26 | RP-040444 | 3 | - | Requirements missing for when the RS485 bus shall not be driven by the secondary device | 6.1.0 | +| 26 | RP-040444 | 4 | 1 | RET DC power consumption modes | 6.1.0 | +| 26 | RP-040444 | 5 | - | Minor Corrections and editorial changes to 25.461 | 6.1.0 | +| 27 | RP-050061 | 7 | 1 | Minor Corrections and editorial changes to 25.461 | 6.2.0 | +| 27 | RP-050061 | 8 | 1 | Power consumption clarification of RET | 6.2.0 | +| 27 | RP-050061 | 9 | | Modem Operating Bands | 6.2.0 | +| 27 | RP-050061 | 10 | | Modem Return loss | 6.2.0 | +| 27 | RP-050061 | 11 | | Modem Time Delay and Accuracy | 6.2.0 | +| 27 | RP-050061 | 12 | | Modem Insertion Loss | 6.2.0 | +| 28 | RP-050237 | 13 | 1 | DC power on sequence | 6.3.0 | +| 28 | RP-050237 | 15 | - | BS Modem and RET Modem Filtering | 6.3.0 | +| 28 | RP-050237 | 16 | - | BS Modem and RET modem spectrum emission mode | 6.3.0 | +| 28 | RP-050237 | 17 | - | BS modem and RET modem return loss at modem frequency | 6.3.0 | +| 28 | RP-050237 | 18 | - | Time delay clarification | 6.3.0 | +| 28 | RP-050226 | 19 | - | Introduction of UMTS2600 requirements | 7.0.0 | +| 29 | RP-050438 | 21 | 1 | Power-Up period clarifications | 7.1.0 | +| 29 | RP-050438 | 23 | | Insertion loss for RET | 7.1.0 | +| 29 | RP-050438 | 25 | | Testing for RET | 7.1.0 | +| 29 | RP-050438 | 27 | | Time delay for RET | 7.1.0 | +| 29 | RP-050438 | 29 | | Intermodulation attenuation for RET | 7.1.0 | +| 29 | RP-050438 | 31 | | BS and RET modem isolation | 7.1.0 | +| 30 | RP-050704 | 32 | 1 | Introduction of UMTS 1700 requirements | 7.2.0 | +| 30 | RP-050703 | 33 | | Introduction of UMTS 900 | 7.2.0 | +| 30 | RP-050689 | 35 | | Test Procedures | 7.2.0 | +| 30 | RP-050689 | 37 | | Correction to modem isolation and emission | 7.2.0 | +| 30 | RP-050689 | 39 | | correction of referencing | 7.2.0 | +| 30 | RP-050689 | 41 | 1 | RET Control Unit spurious emission simplified version | 7.2.0 | +| 34 | RP-060704 | 42 | | Introduction of Band X (Extended UMTS 1.7/2.1 GHz) | 7.3.0 | +| 35 | RP-070058 | 44 | 1 | Update of DC Power Supply Requirements | 7.4.0 | +| 35 | RP-070058 | 45 | | Tower Mounted Amplifier amendment | 7.4.0 | +| 36 | RP-070323 | 47 | | Word alignment of station-device | 7.5.0 | +| 37 | RP-070576 | 48 | | Introduction of UMTS1500 requirement | 8.0.0 | +| 39 | RP-080082 | 49 | 1 | Introduction of UMTS 700 MHz (Bands XII -XIV) | 8.1.0 | +| 45 | RP-090822 | 51 | | Introduction of E-UTRA operating bands | | +| | RP-090826 | 53 | 1 | Introduction of the extended UMTS/LTE 800 MHz bands | 9.0.0 | +| 46 | RP-091185 | 54 | 1 | Introduction of Extended UMTS/LTE1500 requirements for TS25.461 | 9.1.0 | +| 47 | RP-100223 | 58 | | Introduction of UMTS/LTE in 800 MHz for Europe requirements in TS 25.461 | 9.2.0 | +| 49 | RP-100912 | 59 | - | Spectrum band definition additions for TDD 2600 MHz | 10.0.0 | +| 50 | RP-101361 | 59a | 1 | Introduction of L-band in TS 25.461 | 10.1.0 | +| 50 | RP-101278 | 61 | 2 | CR UMTS/LTE-3500 spectrum band definition additions for TDD luant interface to TS 25.461 | 10.1.0 | +| 50 | RP-101334 | 66 | | Band XII channel arrangement correction on 25.461 | 10.1.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.1 | +| 52 | RP-110699 | 70 | | Add 2 GHz band LTE for ATC of MSS in North America to TS25.461 (Rel-10) | 10.2.0 | +| 52 | RP-110696 | 71 | | Add Expanded 1900 MHz Band for UTRA and LTE to TS25.461 (Rel-10) | 10.2.0 | +| 52 | RP-110685 | 73 | | Removal of unused references | 10.2.0 | +| 54 | RP-111733 | 76 | | Removal of references to operating bands i) and h) | 10.3.0 | +| 03.2012 | | | | Creation of Rel-11 version based on v. 10.3.0 | 11.0.0 | +| 55 | RP-120235 | 78 | | Addition of new Band 26 for E850 | 11.0.0 | +| 56 | RP-120749 | 79 | 1 | Introduction of E850_LB (Band 27) to TS 25.461 | 11.1.0 | +| 56 | RP-120750 | 80 | - | Introduction of Band 28 | 11.1.0 | +| 56 | RP-120750 | 81 | - | Introduction of Band 44 | 11.1.0 | +| 58 | RP-121736 | 82 | - | Introduction of band 22 in TS 25.461 | 11.2.0 | +| 58 | RP-121735 | 83 | 1 | Introduction of Band 29 into TS 25.461 | 11.2.0 | +| 62 | RP-131903 | 84 | 1 | Introduction of LTE 450 MHZ | 12.0.0 | +| 62 | RP-131904 | 85 | 1 | Introduction of Band 30 | 12.0.0 | +| 64 | RP-140900 | 87 | - | Introduction of Band 32, XXXII | 12.1.0 | +| 70 | RP-152105 | 91 | - | Introduction of band 65 | 13.0.0 | +| 70 | RP-152106 | 92 | - | Introduction of band 66 | 13.0.0 | +| 70 | RP-152104 | 93 | - | Introduction of band 67 | 13.0.0 | + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|-----|-----|-----------------------------------------------|--------| +| 70 | RP-152107 | 94 | 1 | Introduction of band 45 in 25.461 | 13.0.0 | +| 71 | RP-160446 | 95 | - | Introduction of Band 68 into 25.461 | 13.1.0 | +| 71 | RP-160450 | 96 | 1 | Introduction of Band 46 in TS 25.461 | 13.1.0 | +| 06/2016 | | | | Creation of Rel-14 version based on v. 13.1.0 | 14.0.0 | +| 72 | RP-161040 | 97 | 1 | Introduction of band 70 | 14.0.0 | +| 72 | RP-161041 | 98 | - | Introduction of 2.6GHz SDL band | 14.0.0 | +| 74 | RP-162335 | 100 | - | Introduction of band 48 | 14.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | New version | +| 09/2017 | RP-77 | RP-171976 | 0102 | 1 | B | Introduction of Band 72 | 15.0.0 | +| 09/2017 | RP-77 | RP-171977 | 0104 | - | B | Introduction of the FDD L-band (Band 74) into TS 25.461 | 15.0.0 | +| 09/2017 | RP-77 | RP-171978 | 0105 | 1 | B | Introduction of the TDD L-band(Band 50 and Band 51) | 15.0.0 | +| 09/2017 | RP-77 | RP-171980 | 0106 | - | B | CR to 25.461: Introduction of Band 71 (600MHz FDD band for US) | 15.0.0 | +| 09/2017 | RP-77 | RP-171979 | 0107 | - | B | CR to 25.461: Introduction of B75 and B76 | 15.0.0 | +| 12/2017 | RP-78 | RP-172675 | 0101 | 3 | B | CR to 25.461: Introduction of Band 49 (3.5 GHz LAA in US) | 15.1.0 | +| 12/2017 | RP-78 | RP-172711 | 0108 | - | B | Introduction of Band 73 | 15.1.0 | +| 03/2018 | RP-79 | RP-180471 | 0109 | - | B | Introduction of band 85 | 15.2.0 | +| 03/2018 | RP-79 | RP-180470 | 0110 | - | B | Introduction of the TDD 3.3-3.4GHz band (Band 52) | 15.2.0 | +| 12/2018 | RP-82 | RP-182450 | 0112 | 1 | F | Replace Band table with reference to RAN4 specifications | 15.3.0 | +| 2019-04 | RAN#83 | RP-190557 | 0120 | - | F | Transfer of Iuant interface specification from 25-series to 37-series | 15.4.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25466/raw.md b/marked/Rel-16/25_series/25466/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..49a8a96f46b37fcb8708964639ceb33dc219fffe --- /dev/null +++ b/marked/Rel-16/25_series/25466/raw.md @@ -0,0 +1,121 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 to 7 Void..... | 5 | +| 8 Iuant interface: Application part ..... | 5 | +| Annex A to F: Void..... | 6 | +| Annex G (informative): Change History..... | 7 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +See TS 37.466 [5]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1]-[4] Void. + +[5] 3GPP TS 37.466: "Iuant interface: Application part". + +# --- 3 to 7 Void + +# --- 8 Iuant interface: Application part + +See TS 37.466 [5]. + +# --- Annex A to F: Void + +# Annex G (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|------------------------------------------------------------------------------------------|--------| +| 09/2007 | - | - | - | Creation of Rel-8 version based on v7.2.0 | 8.0.0 | +| 37 | RP-070576 | 0013 | | Introduction of UMTS1500 requirement | 8.0.0 | +| 38 | RP-070838 | 0015 | | Missing Parameter for "TMA Get Supported Non-Linear Gain Values" | 8.1.0 | +| 39 | RP-080082 | 0016 | | Introduction of UMTS 700 MHz (Bands XII XIV) in 25.466 | 8.2.0 | +| 43 | RP-090085 | 0017 | 1 | RET and TMA support in LTE | 8.3.0 | +| 09/2009 | - | - | - | Creation of Rel-9 version based on v8.3.0 | | +| 45 | RP-090782 | 0022 | | Introduction of new antenna operating bands in IuantAP | 9.0.0 | +| 46 | RP-091185 | 0023 | 1 | Introduction of Extended UMTS/LTE1500 requirements for TS25.466 | 9.1.0 | +| 47 | RP-100223 | 0024 | 1 | Introduction of UMTS/LTE in 800 MHz for Europe requirements in TS 25.466 | 9.2.0 | +| 09/2010 | - | - | - | Creation of Rel-10 version based on v9.2.0 | 10.0.0 | +| 49 | RP-100912 | 0025 | | Spectrum band definition additions for TDD 2600 MHz | 10.0.0 | +| 50 | RP-101184 | 0026 | 1 | Introduction of L-band in TS 25.466 | 10.1.0 | +| 50 | RP-101278 | 0028 | 1 | CR UMTS/LTE-3500 spectrum band definition additions for TDD Iuant interface to TS 25.466 | 10.1.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.1 | +| 52 | RP-110699 | 0036 | | Add 2 GHz band LTE for ATC of MSS in North America to TS25.466 (Rel-10) | 10.2.0 | +| 52 | RP-110696 | 0037 | | Add Expanded 1900 MHz Band for UTRA and LTE to TS25.466 (Rel-10) | 10.2.0 | +| 52 | RP-110685 | 0039 | | Removal of unused references | 10.2.0 | +| 54 | RP-111733 | 0042 | | Removal of references to operating bands i) and h) | 10.3.0 | +| 03/2012 | | | | Creation of Rel-11 version based on v10.3.0 | | +| 55 | RP-120266 | 0044 | 2 | Addition of new Band 26 for E850 | 11.0.0 | +| 56 | RP-120749 | 0045 | 1 | Introduction of E850 LB Band 27 to TS 25.466 | 11.1.0 | +| 56 | RP-120750 | 0046 | - | Introduction of LTE band for 700 MHz digital dividend | 11.1.0 | +| 56 | RP-120750 | 0047 | - | Introduction of TDD band for 700 MHz digital dividend | 11.1.0 | +| 57 | RP-121140 | 0048 | 1 | Operating bands Numbering for UTRA and EUTRA | 11.2.0 | +| 58 | RP-121736 | 0049 | - | Introduction of band 22 in TS 25.466 | 11.3.0 | +| 58 | RP-121735 | 0050 | 1 | Introduction of Band 29 into TS 25.466 | 11.3.0 | +| 62 | RP-131903 | 0051 | 1 | Introduction of LTE 450 MHZ | 12.0.0 | +| 62 | RP-131904 | 0052 | 1 | Introduction of Band 30 | 12.0.0 | +| 64 | RP-140900 | 0054 | 2 | Introduction of L-band for Supplemental Downlink in E-UTRA and UTRA | 12.1.0 | +| 67 | RP-150356 | 0055 | 1 | Correction of the reference | 12.2.0 | +| 70 | RP-152107 | 0056 | 2 | Introduction of band 45 in 25.466 | 13.0.0 | +| 70 | RP-152108 | 0057 | - | Extension of operating bands field | 13.0.0 | +| 70 | RP-152105 | 0058 | - | Introduction of band 65 | 13.0.0 | +| 70 | RP-152106 | 0059 | - | Introduction of band 66 | 13.0.0 | +| 70 | RP-152104 | 0060 | - | Introduction of band 67 | 13.0.0 | +| 71 | RP-160446 | 0061 | - | Introduction of Band 68 into 25.466 | 13.1.0 | +| 71 | RP-160450 | 0062 | 1 | Introduction of Band 46 in TS 25.466 | 13.1.0 | +| 06/2016 | | | | Creation of Rel-14 version based on v13.1.0 | 14.0.0 | +| 72 | RP-161040 | 0063 | 1 | Introduction of band 70 | 14.0.0 | +| 72 | RP-161041 | 0064 | 1 | Introduction of 2.6GHz SDL band | 14.0.0 | +| 74 | RP-162335 | 0066 | - | Introduction of band 48 | 14.1.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|-----------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 09/2017 | RP-77 | RP-171982 | 0072 | - | A | Correction to make band extensions applicable also for TMAAP | 14.2.0 | +| 09/2017 | RP-77 | RP-171976 | 0068 | 1 | B | Introduction of Band 72 | 15.0.0 | +| 09/2017 | RP-77 | RP-171978 | 0070 | 1 | B | Introduction of the TDD L-band(Band 50 and Band 51) | 15.0.0 | +| 09/2017 | RP-77 | RP-171980 | 0074 | | B | Introduction of Band 71 | 15.0.0 | +| 09/2017 | RP-77 | RP-171977 | 0076 | 1 | B | Introduction of Band 74 | 15.0.0 | +| 09/2017 | RP-77 | RP-171979 | 0077 | 1 | B | Introduction of Band 75 and 76 | 15.0.0 | +| 12/2017 | RP-78 | RP-172675 | 0067 | 2 | B | CR to 25.466: Introduction of Band 49 (3.5 GHz LAA in US ) | 15.1.0 | +| 12/2017 | RP-78 | RP-172711 | 0078 | - | B | Introduction of Band 73 | 15.1.0 | +| 03/2018 | RP-79 | RP-180471 | 0079 | 1 | B | Introduction of band 85 | 15.2.0 | +| 03/2018 | RP-79 | RP-180470 | 0080 | 1 | B | Introduction of the TDD 3.3-3.4GHz band (Band 52) | 15.2.0 | +| 12/2018 | RP-82 | RP-182447 | 0081 | 1 | F | Antenna Interface Function support | 15.3.0 | +| 2019-04 | RAN#83 | RP-190557 | 0089 | - | F | Transfer of luant interface specification from 25-series to 37-series | 15.4.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25467/06291c5328a7a4335d41a48850a3a207_img.jpg b/marked/Rel-16/25_series/25467/06291c5328a7a4335d41a48850a3a207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2282f67fdc30da6b1f3a35cf2fc1854c6c7f71f8 --- /dev/null +++ b/marked/Rel-16/25_series/25467/06291c5328a7a4335d41a48850a3a207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f681328640d35a36d1bedf38b2bf4caf4166eca32b7033fac2d385baf610001 +size 45440 diff --git a/marked/Rel-16/25_series/25467/0804537310c1bb3f615cb001e33efd1a_img.jpg b/marked/Rel-16/25_series/25467/0804537310c1bb3f615cb001e33efd1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f467f8df50803f1fc34be2f271367e6c08ca1689 --- /dev/null +++ b/marked/Rel-16/25_series/25467/0804537310c1bb3f615cb001e33efd1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6af782131cc3d3f089ec1a99c6af6839591f8c480bd6af11835562f007b26b96 +size 13766 diff --git a/marked/Rel-16/25_series/25467/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/25_series/25467/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51fb2c851bc23181d04ba5d0b553a24d659ac0ff --- /dev/null +++ b/marked/Rel-16/25_series/25467/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9adaa2fbe7921c2ea6f10fbe95d9a39d4423c794e2b4be5528c7b4dee01b4db1 +size 127051 diff --git a/marked/Rel-16/25_series/25467/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/Rel-16/25_series/25467/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c16d37467c7cead3605ca28520c817528c3ee5e8 --- /dev/null +++ b/marked/Rel-16/25_series/25467/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b82d7cc4c58be271ce07be22473f3d5e0cc98d69bfbc0404b4bb466749ae94 +size 14524 diff --git a/marked/Rel-16/25_series/25467/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-16/25_series/25467/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3995860dba60313525961b3696b1461c60149f4b --- /dev/null +++ b/marked/Rel-16/25_series/25467/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7726a1563d79bdb55c09be116ab5d5a0e6091e43a763f2818d1710848157b6ab +size 101577 diff --git a/marked/Rel-16/25_series/25467/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-16/25_series/25467/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f299b71f06fc094b2b097049c3d46c94d4de8fc9 --- /dev/null +++ b/marked/Rel-16/25_series/25467/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c92885f34a012d63bf6093ea3bf470954ff500a3c508dcb8a05355825c99e920 +size 64076 diff --git a/marked/Rel-16/25_series/25467/1ad662a678c4f002de911d403f00de8e_img.jpg b/marked/Rel-16/25_series/25467/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28843ee3b10b833b2f0038137ddec055a8d1b895 --- /dev/null +++ b/marked/Rel-16/25_series/25467/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1abc3487336d25aae4cb347f01accd2185af90139c8ca7c49e4fc525eff30475 +size 86089 diff --git a/marked/Rel-16/25_series/25467/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/25_series/25467/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f360773e5c723c9f2517891db975f8e69bad26c2 --- /dev/null +++ b/marked/Rel-16/25_series/25467/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3c96fee661125c84ddf719643b564497c093d5ac25380567342a7fd814afaae +size 34294 diff --git a/marked/Rel-16/25_series/25467/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/25_series/25467/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5510134d0a837daea3654e1b86694a4f2fac872 --- /dev/null +++ b/marked/Rel-16/25_series/25467/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c444d589bc2fa29285167d92aa0ce85c74b7cec521d95aaca0fffb6ca18f907 +size 78042 diff --git a/marked/Rel-16/25_series/25467/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/25_series/25467/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8888774e374bb2561f8b68c53f90dd6df57ab713 --- /dev/null +++ b/marked/Rel-16/25_series/25467/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3b9815a7089a2b80700ff689959cf6810a2c69e81e0d3aab410b072ebd98ff0 +size 96356 diff --git a/marked/Rel-16/25_series/25467/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/25_series/25467/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34f6939c5e5aa7f71929b2d9cd4a1bfbffa84518 --- /dev/null +++ b/marked/Rel-16/25_series/25467/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad059194cce1a7596c117d29edd7475d9b00c9e5c242190e4345c5d905488492 +size 75609 diff --git a/marked/Rel-16/25_series/25467/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/25_series/25467/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b18021206f912d139bb3d909d8216a81b1e58cd --- /dev/null +++ b/marked/Rel-16/25_series/25467/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7569e2c053deb6e4b3b4aea597ad8207e60650b432538b8956f464c3bc283d05 +size 89842 diff --git a/marked/Rel-16/25_series/25467/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/25_series/25467/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..738755065cbd3d89523efcde1ac47082fa8e08dd --- /dev/null +++ b/marked/Rel-16/25_series/25467/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b517fb5cbd9af640d85f42726e7e559f5088266f3c064559c5f106533e270bf +size 92556 diff --git a/marked/Rel-16/25_series/25467/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/25_series/25467/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..997dabcc66de747977f453f81f58797b564b19f6 --- /dev/null +++ b/marked/Rel-16/25_series/25467/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:426b1f4e66129b316a2442f46182ae11b82a6f4dd8f9b7ff53251540942e8f3a +size 152729 diff --git a/marked/Rel-16/25_series/25467/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25467/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a2f19ad942c808b0bac2911f2a8a2241e1ea381 --- /dev/null +++ b/marked/Rel-16/25_series/25467/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1a67bbb6ef5c3c8f32735be0ed40c2c2b40fd99b615461e4bf210ce261645ec +size 69512 diff --git a/marked/Rel-16/25_series/25467/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/marked/Rel-16/25_series/25467/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fbbdb3afa613f9f932c9e3115924003ac4d6671 --- /dev/null +++ b/marked/Rel-16/25_series/25467/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f73d83a50008831ac9637038d2781cc197e4e396fb043405dfca39bb7def49d +size 35394 diff --git a/marked/Rel-16/25_series/25467/3bd9d303382ff0566369ed81a9226ade_img.jpg b/marked/Rel-16/25_series/25467/3bd9d303382ff0566369ed81a9226ade_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0422b2bd9aa464f1b98830f2e2b45ef46d1f34a --- /dev/null +++ b/marked/Rel-16/25_series/25467/3bd9d303382ff0566369ed81a9226ade_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11229732925fbbc2f5062da092075250484e538cce1e312d0b5a9b0f847e3a3e +size 69076 diff --git a/marked/Rel-16/25_series/25467/443ee770f0d3d98d7411497a3191e2e0_img.jpg b/marked/Rel-16/25_series/25467/443ee770f0d3d98d7411497a3191e2e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5887423bc8966d7d03175211064b69db9704c0bc --- /dev/null +++ b/marked/Rel-16/25_series/25467/443ee770f0d3d98d7411497a3191e2e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb7b0e0e8792f6ae7edc9d7dceb1fd6fd47f8b792f928d3667542602ef580719 +size 37923 diff --git a/marked/Rel-16/25_series/25467/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/Rel-16/25_series/25467/4537891530c9f6f139a2e1ebf544edc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79f58316d1b78d0b677b2881a77099f468c91aa5 --- /dev/null +++ b/marked/Rel-16/25_series/25467/4537891530c9f6f139a2e1ebf544edc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:905a57b796c25f836c3d1d729f28cf65ad39619753341d6c2b374a7713384a2c +size 24439 diff --git a/marked/Rel-16/25_series/25467/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/25_series/25467/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ad3b9681dd3814f9037cab129134e49436969d9 --- /dev/null +++ b/marked/Rel-16/25_series/25467/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e23b6f9c15f9013eb91f6af02b1637922b8b62487e23ac9641bce74bec6b03 +size 95542 diff --git a/marked/Rel-16/25_series/25467/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-16/25_series/25467/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5be67c87faaf6b9aacb709e818f4fd6c83b658 --- /dev/null +++ b/marked/Rel-16/25_series/25467/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37061585691def58967b479fa0e18bb0413c29dece2b2b7026b320509bb61c3a +size 40888 diff --git a/marked/Rel-16/25_series/25467/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-16/25_series/25467/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0a50d2758ac986ac21cac4fbd7b40ff422e429e --- /dev/null +++ b/marked/Rel-16/25_series/25467/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2370fb22f7e45c9edc8f2c7d26313ded62fbf2ad66751bd9c75c1cbbe944a3cb +size 36459 diff --git a/marked/Rel-16/25_series/25467/50f72073c616cb3d3ca3af04a0c3a221_img.jpg b/marked/Rel-16/25_series/25467/50f72073c616cb3d3ca3af04a0c3a221_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b59b0ffa4ba1d75258e8ee468f12f09fe95ef02 --- /dev/null +++ b/marked/Rel-16/25_series/25467/50f72073c616cb3d3ca3af04a0c3a221_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e36d685848b5411daa7c951943a051bc54f3474938d0633cc6d6bf7cccc72031 +size 92875 diff --git a/marked/Rel-16/25_series/25467/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/25_series/25467/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20142b4fe35df49c6bdb68b8074a6f49280ac27d --- /dev/null +++ b/marked/Rel-16/25_series/25467/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03cacc7398d01450e87cfcf5b3bd3795a26bf1e9da1b968590bf702015b64591 +size 75291 diff --git a/marked/Rel-16/25_series/25467/53001b5ae3f65139f78db410bb41ae30_img.jpg b/marked/Rel-16/25_series/25467/53001b5ae3f65139f78db410bb41ae30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b42221b516128f7625b0fe50bb575c40cb9c768b --- /dev/null +++ b/marked/Rel-16/25_series/25467/53001b5ae3f65139f78db410bb41ae30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20707dc3dd1b4c706188c544bd73d5405e3f4a34ea3b4c6505a9a9b9859847c0 +size 54870 diff --git a/marked/Rel-16/25_series/25467/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-16/25_series/25467/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e67fb55d98132949a0b74a4589517808f8d81fdc --- /dev/null +++ b/marked/Rel-16/25_series/25467/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2821a165ac5d58621c166df6373bdb502a14846a4c24cc01f275e39b40c57bc0 +size 56169 diff --git a/marked/Rel-16/25_series/25467/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/25_series/25467/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa36d7edf4563f0170cdab0af6cf5e4815014f36 --- /dev/null +++ b/marked/Rel-16/25_series/25467/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8812edf374a0ebef3e18b4abfa1ba624cd287e01f1482ffbf1dcc2106ab1af5b +size 43464 diff --git a/marked/Rel-16/25_series/25467/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg b/marked/Rel-16/25_series/25467/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eea3b7b4cadd1a2451884984ff6a33f811763b71 --- /dev/null +++ b/marked/Rel-16/25_series/25467/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b84de2b7984667407944f900a833d0d99c07bf6cc2d2275a9572e50bc817a866 +size 17493 diff --git a/marked/Rel-16/25_series/25467/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/25_series/25467/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d6bf79ad272cde9b23f5495a63370f7c78e80de --- /dev/null +++ b/marked/Rel-16/25_series/25467/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:927325e7d0315644d3d971ca62c42bb58694382ab50316ee27b6c85cc615211e +size 65362 diff --git a/marked/Rel-16/25_series/25467/67c232883c119b120d2fb337bf588e05_img.jpg b/marked/Rel-16/25_series/25467/67c232883c119b120d2fb337bf588e05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dfc8ad7240f57f12ac1cf8a049068c763a9b34c --- /dev/null +++ b/marked/Rel-16/25_series/25467/67c232883c119b120d2fb337bf588e05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bd084227113e4608acf6e6af249732aab44a06edb1ba2651a80730be4d062e2 +size 26220 diff --git a/marked/Rel-16/25_series/25467/6e0ac4070edc6a056713e6f0a3222db5_img.jpg b/marked/Rel-16/25_series/25467/6e0ac4070edc6a056713e6f0a3222db5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..691892d85fd01097770bec4899c4ab2377c3ec2b --- /dev/null +++ b/marked/Rel-16/25_series/25467/6e0ac4070edc6a056713e6f0a3222db5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12d77aa5b0cb7e1c425d357181a92a512cc9d0f247b8f76c2852c91a60299a8f +size 45381 diff --git a/marked/Rel-16/25_series/25467/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/25_series/25467/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1d37e6455ad94d748be6eff8c71ca09d112894a --- /dev/null +++ b/marked/Rel-16/25_series/25467/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cc39b2379c9d1ad380db6e88e7f594c346690feed4cd13c455863081fa332dc +size 71909 diff --git a/marked/Rel-16/25_series/25467/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-16/25_series/25467/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b1a3986fa192c96f499a4875d93ec0da36d865 --- /dev/null +++ b/marked/Rel-16/25_series/25467/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f42ef9e4d50edef6cc8c7f0b82d0fb0961247e02f8eb183296472f013bdebde +size 14797 diff --git a/marked/Rel-16/25_series/25467/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-16/25_series/25467/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23c559d9ebd71bccc5fe43eae55fef1302440940 --- /dev/null +++ b/marked/Rel-16/25_series/25467/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e2ba100fd495231d8ffd6e5fb545c02c5abe2e1afa3a9c1b9b2a691b6651f0a +size 88364 diff --git a/marked/Rel-16/25_series/25467/7e74ac663f3e644b589ed28f5fd29398_img.jpg b/marked/Rel-16/25_series/25467/7e74ac663f3e644b589ed28f5fd29398_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31536186bedac5aad838cdeae89af1c9be95e7a2 --- /dev/null +++ b/marked/Rel-16/25_series/25467/7e74ac663f3e644b589ed28f5fd29398_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2723647b0dc885440ddfd48ce8f52050bf6aa5c6391dcb0976b6d03a5fce445 +size 46894 diff --git a/marked/Rel-16/25_series/25467/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/25_series/25467/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6aa5aee1f84dd0f376b79fd83f11b89f33d81ceb --- /dev/null +++ b/marked/Rel-16/25_series/25467/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130289f042080545bb579b639ef3d421b5b9a30e587e17c39e3b94baa1ce0d2b +size 105381 diff --git a/marked/Rel-16/25_series/25467/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/25_series/25467/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b63f29f8561ebea109a086dc3efde547f4d98e --- /dev/null +++ b/marked/Rel-16/25_series/25467/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeb042a272d552e13857c5068d9a02a7577a1ebf26e768563a0fc7baa2ed9194 +size 30368 diff --git a/marked/Rel-16/25_series/25467/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/25_series/25467/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b15bdf71c7984b057f83a703c10bd050760d676 --- /dev/null +++ b/marked/Rel-16/25_series/25467/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00880ab3d63fcad75d9ec7584576354c5aca049e4f6f8b85992b7d48f7eaf009 +size 35548 diff --git a/marked/Rel-16/25_series/25467/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/25_series/25467/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95ce931a8bd3adedb3e300f584243dcfb9f75f49 --- /dev/null +++ b/marked/Rel-16/25_series/25467/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a454871064fed8d20361bf0b1a72dc13c7470812046eb5d04f07e73628a5003 +size 93833 diff --git a/marked/Rel-16/25_series/25467/87b70d2e8951032d28b4412d82cf1413_img.jpg b/marked/Rel-16/25_series/25467/87b70d2e8951032d28b4412d82cf1413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad56419a8d5c55fca8d07667e3760adfb3510747 --- /dev/null +++ b/marked/Rel-16/25_series/25467/87b70d2e8951032d28b4412d82cf1413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5aad81994beecc8843b970ef90a87fcb7f9351d0b0abf870ff3ffa61f71a5cb +size 30302 diff --git a/marked/Rel-16/25_series/25467/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Rel-16/25_series/25467/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d45bc7e974cd3a759f09517519a82cbf6ff39d69 --- /dev/null +++ b/marked/Rel-16/25_series/25467/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd8f6cbe8588499662378aed7f7baf0a9b0767517399d40554238a4c002fcb11 +size 32589 diff --git a/marked/Rel-16/25_series/25467/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/25_series/25467/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf86f079a643a3bf97410e57fd754c9fd01c6062 --- /dev/null +++ b/marked/Rel-16/25_series/25467/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82d8fbd062501e0c789731e8ed9271653d07582b9c0408e0f4a442c0c7249a1c +size 73579 diff --git a/marked/Rel-16/25_series/25467/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/25_series/25467/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f108ad1813153e562b298ad22353dcd80ff56c50 --- /dev/null +++ b/marked/Rel-16/25_series/25467/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e14d3eabd4b8c44038891b35f998d6f5c2a5e21e427a93385bcfc50aebe7590 +size 65824 diff --git a/marked/Rel-16/25_series/25467/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25467/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ef6d94cb55ada81bbf778b9f8d0226fca6f51b0 --- /dev/null +++ b/marked/Rel-16/25_series/25467/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e01f25bc7394dd41aca4fd5063142fe4e2a74041665f1c140b3699da2a5e68f0 +size 27268 diff --git a/marked/Rel-16/25_series/25467/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/marked/Rel-16/25_series/25467/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fea2a181bd5499edabb7392d7cd2a591faa060d9 --- /dev/null +++ b/marked/Rel-16/25_series/25467/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1084214a40b280e4453067005cf3df17e527d728a1a10aa661bce6d83ee4cc28 +size 57077 diff --git a/marked/Rel-16/25_series/25467/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/25_series/25467/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..330158917001b23456e4129f38a98484731dc30e --- /dev/null +++ b/marked/Rel-16/25_series/25467/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af63caee98e5501cffecf3b660e6f42dee7841bcd89ba03a803a20c320c5e289 +size 184855 diff --git a/marked/Rel-16/25_series/25467/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/25_series/25467/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92fac436b28eead6d6c905faf0f3cbf9f353122c --- /dev/null +++ b/marked/Rel-16/25_series/25467/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fd93e9708c6a25bf02db3bd6f947c6fce6ee4050c282c1e62f59ecf8301f5ab +size 44057 diff --git a/marked/Rel-16/25_series/25467/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25467/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59991d970098cd55245091f633361c3e05ab2c36 --- /dev/null +++ b/marked/Rel-16/25_series/25467/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4907fdf827960080f49383f312ae09d350e556ab0c4e96322489a81804c452b +size 53288 diff --git a/marked/Rel-16/25_series/25467/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/25_series/25467/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1428103cf250724bb691ba250e3b6db9eb18299 --- /dev/null +++ b/marked/Rel-16/25_series/25467/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e08d8bf28d81fba6167e6f82befd6e56c22b272dbcbe4154fd13cb4b65d8f6bc +size 51612 diff --git a/marked/Rel-16/25_series/25467/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/25_series/25467/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..987feec0621ef8d9db09ec305ab7482655408519 --- /dev/null +++ b/marked/Rel-16/25_series/25467/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d352e4dc97846364e4ccdfb206e0f8e175c7ed18a11f656d91b03ef5e3fdf8e +size 134682 diff --git a/marked/Rel-16/25_series/25467/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/25_series/25467/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..252cf31cb5b5e9e798d3ee0b60bc97873b4ae182 --- /dev/null +++ b/marked/Rel-16/25_series/25467/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe573cb214dffccba2ac31ddb033d02257ef78339df4504877a11606aa4c720c +size 99339 diff --git a/marked/Rel-16/25_series/25467/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/Rel-16/25_series/25467/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b60d57b1b986d5fcd710be426e38ee4d7d5564a --- /dev/null +++ b/marked/Rel-16/25_series/25467/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f666f382b89a8ca105dfa1e9d1df3f4be0cb2d7c2657858aaf90320135ab18fc +size 90475 diff --git a/marked/Rel-16/25_series/25467/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/25_series/25467/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad093ac4c88c6d8e627a88dac30e8be583a517f --- /dev/null +++ b/marked/Rel-16/25_series/25467/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34d8168178919a1d1b02350ecfbec0a570e7991f9c4b657227c8b74891124682 +size 59062 diff --git a/marked/Rel-16/25_series/25467/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/Rel-16/25_series/25467/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..781b0831eee4bd17f430bac2f93dfffb30d41c5e --- /dev/null +++ b/marked/Rel-16/25_series/25467/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66c899c77c5eed127799a6fe68316a25a1dcb60af953c1399680c40960d33d80 +size 39455 diff --git a/marked/Rel-16/25_series/25467/b71ad9fc874230de9ba4480e12a216f7_img.jpg b/marked/Rel-16/25_series/25467/b71ad9fc874230de9ba4480e12a216f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51024b91590fc9fd3a016f87ab024604f74127bc --- /dev/null +++ b/marked/Rel-16/25_series/25467/b71ad9fc874230de9ba4480e12a216f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93d27b8fd695fc4834974d48493de3ec79243fa6ab6139928702b847b8acb268 +size 18713 diff --git a/marked/Rel-16/25_series/25467/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-16/25_series/25467/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c90f4ad0deb604f656bc77ce1667f77975b9436c --- /dev/null +++ b/marked/Rel-16/25_series/25467/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f539b02c1a484a0e85507c5190ca152465bd734085c2e175d2937ffedbb48825 +size 46876 diff --git a/marked/Rel-16/25_series/25467/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-16/25_series/25467/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f84e350b86fcc19841bf64529fbd689dda18344d --- /dev/null +++ b/marked/Rel-16/25_series/25467/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ec787d7679eb49bdf9e6cbb6060cfda4e1715cae120a7080f2fae61594378c +size 39621 diff --git a/marked/Rel-16/25_series/25467/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/25_series/25467/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b26c01acc3223d9a10be91cdfd8222eaeb0653a2 --- /dev/null +++ b/marked/Rel-16/25_series/25467/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b2118e328b575f8dc34384468076f007574338082c5ece34b796a76b6da2d63 +size 27030 diff --git a/marked/Rel-16/25_series/25467/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Rel-16/25_series/25467/dd6c544ab685b25dd17f59456efcfbfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dc5750ba2166dd1636d12b460124b7530adbac4 --- /dev/null +++ b/marked/Rel-16/25_series/25467/dd6c544ab685b25dd17f59456efcfbfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bafd9870cfd34285c9df741d0d1f1dd518a20cfdf86a4c2f435a1c7be2a5d8d +size 15354 diff --git a/marked/Rel-16/25_series/25467/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/Rel-16/25_series/25467/dfafe39c233a62ec8ebd71e42992c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbb75d0bc64eb3047604d62f06a32f1b8317be1d --- /dev/null +++ b/marked/Rel-16/25_series/25467/dfafe39c233a62ec8ebd71e42992c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdf047b7c8a771b3948a3e619788ccca463976122490ba1ea5fc68b3335edaef +size 32588 diff --git a/marked/Rel-16/25_series/25467/e42cc691d9c7c4d23e66b04472bb494e_img.jpg b/marked/Rel-16/25_series/25467/e42cc691d9c7c4d23e66b04472bb494e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f615fa0b456dc94ec3be7c43145e7c0c02090e5d --- /dev/null +++ b/marked/Rel-16/25_series/25467/e42cc691d9c7c4d23e66b04472bb494e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade8367544625e111d4decdf6e98e035b365a3700e321aefc4746ce4c69cd6f3 +size 33507 diff --git a/marked/Rel-16/25_series/25467/ef8f4838401ece0abd51d63b897fa388_img.jpg b/marked/Rel-16/25_series/25467/ef8f4838401ece0abd51d63b897fa388_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96f91015f064ba1ba6071e32adbff0eabe18fae8 --- /dev/null +++ b/marked/Rel-16/25_series/25467/ef8f4838401ece0abd51d63b897fa388_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e96b855b365bdc878b14c7d47e3fbae90220bc2f77c3a6b04f3c610ce1071ca +size 36835 diff --git a/marked/Rel-16/25_series/25467/f14f0843f9944e61124817d06809d7ad_img.jpg b/marked/Rel-16/25_series/25467/f14f0843f9944e61124817d06809d7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0c476f605884eae7d00372db78b4a1bae905cc7 --- /dev/null +++ b/marked/Rel-16/25_series/25467/f14f0843f9944e61124817d06809d7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ff1719d630c0958dac42dfb0d766d1c732969d379425fef0de2a52700d287f3 +size 29843 diff --git a/marked/Rel-16/25_series/25467/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-16/25_series/25467/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2080e7fa382c91c88c21c50bb845b179e077afdd --- /dev/null +++ b/marked/Rel-16/25_series/25467/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528861366a123b1cd05b127ecb77d8164aa48107114bb1dfff3394f93feabe2f +size 28721 diff --git a/marked/Rel-16/25_series/25467/f56ab8d50c10444a7043b7e30880cd0a_img.jpg b/marked/Rel-16/25_series/25467/f56ab8d50c10444a7043b7e30880cd0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e4f3a6abc4d571d85aaf1be1ff17d9e340da201 --- /dev/null +++ b/marked/Rel-16/25_series/25467/f56ab8d50c10444a7043b7e30880cd0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:833f55d18cef938a3b5799c1b18b2fc8389d0c2c58c810ad3967add0e3ff53de +size 36280 diff --git a/marked/Rel-16/25_series/25467/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/25_series/25467/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a491348b6eac75861d4a8862ecd65319581b1ec1 --- /dev/null +++ b/marked/Rel-16/25_series/25467/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c384f4df2669500696254ce447f40a5bc3b15c406b2c7e4a5e8ddfe97b930095 +size 114831 diff --git a/marked/Rel-16/25_series/25467/raw.md b/marked/Rel-16/25_series/25467/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e91ce6dab431136c78c5cc8ac9e770aac2f5d892 --- /dev/null +++ b/marked/Rel-16/25_series/25467/raw.md @@ -0,0 +1,3241 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 10 | +| 4 Overall architecture..... | 11 | +| 4.1 General ..... | 11 | +| 4.1.1 HNB Management System (HMS)..... | 12 | +| 4.1.2 Security Gateway (SeGW) ..... | 12 | +| 4.1.3 HNB Gateway (HNB-GW) ..... | 12 | +| 4.1.4 HNB..... | 13 | +| 4.1.5 L-GW..... | 13 | +| 4.2 Functional split..... | 13 | +| 5 UTRAN functions for HNB access..... | 15 | +| 5.1 UE Registration..... | 15 | +| 5.1.1 General ..... | 15 | +| 5.1.2 UE Registration: case of non CSG UEs or non CSG HNBs ..... | 16 | +| 5.1.3 UE Registration: case of CSG UEs and CSG or Hybrid HNBs ..... | 17 | +| 5.1.4 HNB-GW triggered UE Registration ..... | 18 | +| 5.1.5 UE Registration: case of Open Access HNBs..... | 20 | +| 5.2 HNB Registration..... | 21 | +| 5.2.1 General ..... | 21 | +| 5.2.2 HNB Registration procedure ..... | 21 | +| 5.3 HNB-GW Discovery Function..... | 22 | +| 5.3.1 General ..... | 22 | +| 5.4 HNB de-registration Function..... | 23 | +| 5.4.1 General ..... | 23 | +| 5.5 Iuh Disconnect..... | 23 | +| 5.5.1 General ..... | 23 | +| 5.5.2 Iuh Disconnect procedure..... | 24 | +| 5.6 Paging Optimization Function ..... | 25 | +| 5.6.1 General ..... | 25 | +| 5.7 HNB to HNB Mobility..... | 25 | +| 5.7.1 General ..... | 25 | +| 5.7.2 Connected mode mobility from one HNB to another HNB (Intra PLMN, Intra HNB-GW, Intra CSG)..... | 25 | +| 5.7.2.1 C-Plane Handling..... | 25 | +| 5.7.2.2 User Plane Handling ..... | 27 | +| 5.7.3 Soft Handover Initiation..... | 28 | +| 5.7.4 Mobility Access Control..... | 29 | +| 5.7.4.1 Limitations ..... | 29 | +| 5.7.5 CELL_FACH, CELL_PCH and URA_PCH Iuh based mobility (Intra-GW) ..... | 29 | +| 5.8 HNB Configuration Transfer ..... | 30 | +| 5.9 Iurh Setup..... | 31 | +| 5.9.1 General ..... | 31 | +| 5.9.2 Iurh Setup for direct Iurh connectivity between HNBs..... | 32 | +| 5.9.3 Iurh Setup for Iurh connectivity between HNBs via the HNB-GW..... | 32 | +| 5.9.4 Iurh Setup between the HNB and the HNB-GW for HNB-RNC connectivity ..... | 33 | +| 5.10 Handling of Source information transfer to Target..... | 33 | +| 5.10.1 RAB Related Parameters..... | 34 | +| 5.10.1.1 User Plane ..... | 34 | +| 5.10.1.2 Other parameters..... | 34 | +| 5.10.2 Non-RAB Related Parameters..... | 34 | +| 5.8a CS user plane multiplexing ..... | 34 | +| 5.9a Inbound Mobility to HNB ..... | 34 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------|----| +| 5.9.1a | General ..... | 34 | +| 5.9.2a | Connected Mode Inbound Mobility for CSG UEs to CSG HNBs or to Hybrid Cells ..... | 35 | +| 5.9.3a | Connected Mode Inbound Mobility for non-CSG UEs to CSG HNBs or to Hybrid Cells ..... | 37 | +| 5.9.4a | Connected Mode Inbound Mobility to open access HNBs ..... | 39 | +| 5.10a | CSG Subscription Expiry ..... | 40 | +| 5.11 | Connectivity between HNB and RNC via HNB-GW for RNSAP signalling..... | 40 | +| 5.11.1 | General ..... | 40 | +| 5.11.2 | Enhanced Relocation between HNB and RNC via HNB-GW ..... | 40 | +| 5.11.2.1 | Enhanced Relocation from Open Access and Hybrid HNBs to RNC ..... | 40 | +| 5.11.2.2 | Enhanced Relocation from RNC to Open Access HNBs for CSG UEs ..... | 41 | +| 5.11.2.3 | Enhanced Relocation from RNC to Hybrid HNB for CSG UEs ..... | 43 | +| 5.11.3 | Soft Handover between HNB and RNC via HNB-GW ..... | 45 | +| 5.11.3.1 | Soft Handover from HNB to RNC ..... | 45 | +| 5.11.3.2 | Soft Handover from RNC to Open or Hybrid Access HNB..... | 46 | +| 5.11.4 | HNB to RNC CELL_FACH, CELL_PCH and URA_PCH mobility ..... | 47 | +| 5.11.5 | RNC to HNB CELL_FACH, CELL_PCH and URA_PCH mobility ..... | 48 | +| 5.12 | Fixed Broadband Access network Interworking ..... | 49 | +| 6 | Requirements for O&M ..... | 50 | +| 6.1 | O&M for HNB ..... | 50 | +| 6.1.1 | Provisioning Procedure for HNB ..... | 50 | +| 6.1.2 | Location Verification..... | 50 | +| 6.1.2.1 | General ..... | 50 | +| 6.1.2.2 | Macro-cell Information ..... | 50 | +| 6.1.2.2.1 | General ..... | 50 | +| 6.1.2.2.2 | UTRAN Cell Information ..... | 51 | +| 6.1.2.2.3 | GSM Cell Information ..... | 51 | +| 6.1.2.3 | GNSS Location Information ..... | 52 | +| 6.1.2.4 | Broadband Connection Information ..... | 52 | +| 6.1.3 | HNB-GW Discovery ..... | 52 | +| 6.1.4 | HNB Provisioning ..... | 52 | +| 6.1.4.1 | General ..... | 52 | +| 6.1.4.2 | CN Level Parameters ..... | 53 | +| 6.1.4.3 | RAN Level Parameters ..... | 54 | +| 6.1.4.4 | RF Level Parameters..... | 56 | +| 6.2 | O&M for HNB-GW ..... | 56 | +| 7 | Iuh interface protocol structure ..... | 57 | +| 7.1 | General ..... | 57 | +| 7.2 | Iuh..... | 57 | +| 7.2.1 | Iupc-Iuh Interface Control Plane Protocol Stack..... | 58 | +| 7.2.2 | Interworking between the PCAP User Adaptation Layer (PUA) and the Signalling Connection Control Part (SCCP) ..... | 59 | +| 7.2.2.1 | General ..... | 59 | +| 7.2.2.2 | Establishment of signalling connection over Iuh and Iupc connections between HNB and SAS via HNB-GW ..... | 60 | +| 7.2.2.3 | Establishment of signalling connection over Iuh – Refusal from SAS ..... | 61 | +| 7.2.2.4 | Transport of PCAP signalling messages via signalling connection established over Iupc and Iuh connections ..... | 61 | +| 7.2.2.4.1 | HNB initiated ..... | 61 | +| 7.2.2.4.2 | SAS initiated ..... | 62 | +| 7.2.2.5 | Release of signalling connection over Iupc and Iuh Connections ..... | 62 | +| 7.2.2.6 | Transport of PCAP signalling messages via the connectionless data transfer service ..... | 63 | +| 7.2.2.6.1 | HNB initiated ..... | 63 | +| 7.2.2.6.2 | SAS initiated ..... | 63 | +| 7.3 | Iurh ..... | 63 | +| 7.3.1 | Iurh-Interface Control Plane Protocol Stack ..... | 64 | +| 7.3.2 | Usage of the services provided by RNSAP User Adaptation Layer (RNA) ..... | 65 | +| 7.3.2.1 | General ..... | 65 | +| 7.3.2.2 | Iurh Signalling Connection Establishment ..... | 66 | +| 7.3.2.2.1 | Direct Iurh connectivity ..... | 66 | +| 7.3.2.2.2 | Iurh signalling connection establishment via the HNB-GW ..... | 66 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------| +| 7.3.2.3 | Transport of RNSAP signalling messages via an established Iurh signalling connection ..... | 67 | +| 7.3.2.3.1 | Direct Iurh connectivity ..... | 67 | +| 7.3.2.3.2 | Iurh connectivity via the HNB-GW ..... | 67 | +| 7.3.2.4 | Release of a Signalling Connection ..... | 67 | +| 7.3.2.4.1 | Direct Iurh connectivity ..... | 67 | +| 7.3.2.4.2 | Iurh connectivity via the HNB-GW ..... | 68 | +| 7.3.2.5 | Transport of RNSAP signalling messages via the connectionless data transfer service ..... | 68 | +| 7.3.2.5.1 | Direct Iurh connectivity ..... | 68 | +| 7.3.2.5.2 | Iurh connectivity via the HNB-GW ..... | 68 | +| 7.3.3 | Interworking between the RNSAP User Adaptation Layer (RNA) and the Signalling Connection Control Part (SCCP) ..... | 69 | +| 7.3.3.1 | General ..... | 69 | +| 7.3.3.2 | Establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW ..... | 70 | +| 7.3.3.2.1 | HNB initiated ..... | 70 | +| 7.3.3.2.2 | HNB initiated – Refusal from RNC ..... | 71 | +| 7.3.3.2.3 | RNC initiated ..... | 72 | +| 7.3.3.3 | Transport of RNSAP signalling messages via signalling connection established over Iurh and Iur connections ..... | 73 | +| 7.3.3.3.1 | HNB initiated ..... | 73 | +| 7.3.3.3.2 | RNC initiated ..... | 73 | +| 7.3.3.4 | Release of signalling connection over Iurh and Iur Connections ..... | 74 | +| 7.3.3.4.1 | HNB initiated ..... | 74 | +| 7.3.3.4.2 | RNC initiated ..... | 74 | +| 7.3.3.5 | Transport of RNSAP signalling messages via the connectionless data transfer service ..... | 75 | +| 7.3.3.5.1 | HNB initiated ..... | 75 | +| 7.3.3.5.2 | RNC initiated ..... | 75 | +| 8 | Enhanced Interference Management ..... | 76 | +| 8.1 | General ..... | 76 | +| 8.2 | Mitigation of interference from HNB to Macro ..... | 76 | +| 8.2.1 | Interference from HNB UE (UL) to Macro NB ..... | 76 | +| 8.2.2 | Interference from HNB (DL) to Macro UE ..... | 76 | +| Annex A (informative): | Implementation of CN functions within the HNB-GW for support of inter-HNB intra-HNB-GW SRNS Relocation ..... | 77 | +| A.1 | Scope ..... | 77 | +| A.2 | General ..... | 77 | +| A.3 | Mobility procedure ..... | 77 | +| A.4 | Iurh Control Plane Aspects ..... | 79 | +| A.5 | Iurh user plane aspects ..... | 79 | +| A.6 | RAB management Functions ..... | 79 | +| A.7 | Data Volume Reporting ..... | 79 | +| A.8 | UE Tracing ..... | 79 | +| A.9 | Location reporting function ..... | 80 | +| A.10 | Security Functions ..... | 80 | +| A.11 | Iurh Framing Protocol Interworking Function (IurhUPIF) ..... | 80 | +| A.11.1 | Introduction ..... | 80 | +| A.11.2 | CS User Plane handling during the Initial CS RAB setup ..... | 81 | +| A.11.3 | CS User Plane handling after the finalisation of SRNS Relocation ..... | 82 | +| A.11.4 | FQC ..... | 82 | +| A.11.5 | Frame number ..... | 82 | +| A.11.6 | Time alignment Procedure: ..... | 83 | +| A.11.7 | Rate Control Procedure ..... | 83 | +| A.11.8 | Payload ..... | 83 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------|-----------| +| A.11.9 | Iu UP Re-Initialisation ..... | 83 | +| Annex B (informative): | Deployment Architecture ..... | 84 | +| B.1 | Direct Iurh connectivity between HNBs..... | 84 | +| Annex C (informative): | Implementation of PSC Disambiguation for Support of Legacy UE Mobility from RNC to HNB ..... | 86 | +| C.1 | Scope..... | 86 | +| C.2 | Disambiguation at the RNC ..... | 86 | +| C.2.1 | Step 1: Construction of HNB database in the RNC ..... | 86 | +| C.2.2 | Step 2: PSC disambiguation executed by the RNC during RNC to HNB hand-in ..... | 87 | +| C.3 | Disambiguation at the HNB-GW ..... | 87 | +| C.3.1 | Construction and Update of $\Delta$ OTD Database at the HNB-GW ..... | 88 | +| C.3.2 | Target Cell Disambiguation for Handover to the HNB ..... | 88 | +| C.4 | Notes ..... | 88 | +| Annex D (informative): | Change History..... | 90 | + +# --- 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 UTRAN architecture for 3G Home Node B (HNB). + +It covers specification of the functions for UEs not supporting Closed Subscriber Groups (CSG) and UEs supporting CSGs. It also covers HNB specific requirements for O&M. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.468: "UTRAN Iuh Interface RUA signalling". +- [3] 3GPP TS 25.469: "UTRAN Iuh Interface HNBAP signalling ". +- [4] 3GPP TS 25.401: "UTRAN overall description". +- [5] 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles". +- [6] IETF RFC 4960 (September 2007): "Stream Control Transmission Protocol". +- [7] Broadband Forum TR-069 Amendment 2, *CPE WAN Management Protocol*, Broadband Forum Technical Report, 2007. +- [8] 3GPP TS 25.444: "Iuh data transport and transport signalling". +- [9] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [10] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [11] 3GPP TS 22.220: "Service requirements for Home Node Bs and Home eNode Bs". +- [12] 3GPP TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP". +- [13] Void +- [14] Void +- [15] Void +- [16] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)". +- [17] 3GPP TS 25.415: "UTRAN Iu Interface user plane protocols". +- [18] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) Signalling". +- [19] 3GPP TS 25.471: "UTRAN Iurh Interface RNSAP User Adaption (RNA) signalling". +- [20] Void +- [21] 3GPP TS 25.425: "UTRAN Iur interface user plane protocols for Common Transport Channel data streams". + +- [22] 3GPP TS 25.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams". +- [23] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". +- [24] 3GPP TS 32.642: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)". +- [25] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification". +- [26] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [27] 3GPP TS 32.652: "Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)". +- [28] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [29] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode". +- [30] Void +- [31] 3GPP TS 25.420: "UTRAN Iur interface general aspects and principles". +- [32] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [33] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [34] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [35] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [36] 3GPP TS 23.139: "3GPP system – fixed broadband access network interworking". +- [37] 3GPP TS 25.450: "UTRAN Iupc interface general aspects and principles". +- [38] 3GPP TS 25.453: "UTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling". +- [39] 3GPP TS 25.470: "UTRAN Iuh Interface PCAP User Adaption (PUA) signalling". + +# --- 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]. + +**HNB, Home Node B, 3G Home Node B:** as defined in TS 22.220 [11]. These terms, their derivations and abbreviations are used synonymously throughout this document. + +**CSG HNB:** A HNB that serves a CSG Cell, broadcasting a CSG Indicator and a specific CSG identity. + +**Non CSG HNB:** A HNB that serves a cell which neither broadcasts a CSG Indicator nor a CSG Identity. + +**Hybrid HNB:** A HNB that serves a hybrid cell not broadcasting a CSG Indicator but broadcasting a CSG identity. + +**Membership Verification:** The process that checks whether a UE is a member or non-member of a hybrid cell. + +**Access Control:** The process that checks whether a UE is allowed to access and to be granted services in a closed cell. + +**CSG ID Validation:** The process that checks whether the CSG ID sent via relocation messages is the same as the one supported by the target RAN. + +**RNSAP Relocation:** denotes enhanced mobility for inter-HNB Relocation via RNSAP. In this version of the specification, RNSAP Relocation is only defined for intra-PLMN intra-HNB-GW intra-CSG scenarios. + +**PLMN ID Check:** The process that checks whether a PLMN ID is the RPLMN identity or an EPLMN identity of the 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]. + +| | | +|----------|--------------------------------------------------| +| CS | Circuit Switched | +| CSG | Closed Subscriber Group | +| DSL | Digital Subscriber Line | +| DSL-GW | DSL GateWay | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| HMS | Home Node B Management System | +| HNB | 3G Home Node B | +| HNB-GW | 3G HNB Gateway | +| HW | Hard Ware | +| IP | Internet Protocol | +| L-GW | Local GateWay | +| LAC | Local Area Code | +| LIPA | Local IP Access | +| PCRF | Policy and Charging Rules Function | +| RAC | Routing Area Code | +| RGW | Residential GateWay | +| SAC | Service Area Code | +| SCCP | Signalling Connection Control Part | +| SeGW | Security GateWay | +| SGW | Serving GateWay | +| SIPTO | Selected IP Traffic Offload | +| SIPTO@LN | Selected IP Traffic Offload at the Local Network | +| SW | SoftWare | + +# 4 Overall architecture + +## 4.1 General + +The overall UMTS architecture and UTRAN architectures are described in TS 25.401 [4] and TS 25.410 [5]. For clarity and ease of understanding, at appropriate places references to TR-069 [7] and associated methods are described briefly although they are beyond the scope of this specification. + +The reference model shown in Figure 4.1-1 below contains the network elements that make up the HNB access network. There is a one-to-many relationship between a HNB-GW and the HNB(s) it serves. + +![Sequence diagram of HNB access network reference model showing interactions between UE, SHNB, and DHNB.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SHNB + participant DHNB + Note right of SHNB: Decision to setup new RL + UE->>SHNB: 1. RRC Measurement Report + SHNB->>DHNB: 2. RNA CONNECT (UE context id, RNSAP Radio Link Setup Request) + Note right of DHNB: Start Rx + DHNB->>SHNB: 3. RNA Direct Transfer (UE context id, RNSAP Radio Link Setup Response) + DHNB->>SHNB: 4. RNA Direct Transfer (UE context id, RNSAP Radio Link Restore Indication) + Note right of SHNB: Start Tx + SHNB->>UE: 5. RRC Active Set Update + UE->>SHNB: 6. RRC Active Set Update Complete + +``` + +The diagram illustrates the sequence of messages for setting up a new radio link. It starts with the UE sending an RRC Measurement Report to the SHNB. The SHNB makes a decision to setup a new radio link and sends an RNA CONNECT message (containing UE context id and RNSAP Radio Link Setup Request) to the DHNB. The DHNB starts receiving (Start Rx) and responds with an RNA Direct Transfer message (containing UE context id and RNSAP Radio Link Setup Response). The SHNB then starts transmitting (Start Tx) and sends an RRC Active Set Update to the UE. Finally, the UE responds with an RRC Active Set Update Complete message to the SHNB. + +Sequence diagram of HNB access network reference model showing interactions between UE, SHNB, and DHNB. + +Figure 4.1-1: HNB access network reference model. + +The HNB-GW appears to the CN as an RNC and serves as a concentrator of HNB connections. The Iu interface between the CN and the HNB-GW serves the same purpose as the interface between the CN and a RNC. The HNB GW is uniquely identified towards the CN on a particular Iu interface by the RNC ID. One HNB serves only one cell. + +The HNB-GW appears to other RNCs as an RNC and serves as a concentrator of HNB connections. The HNB GW is uniquely identified towards the RNC on a particular Iur interface by the RNC ID. + +The Local Gateway (L-GW) may be present only when the HNB operates in LIPA mode or when the HNB operates in SIPTO@LN mode. When present, it is co-located with the HNB, in which case the HNB has a Gn/S5 interface towards the SGSN/SGW which does not use the HNB-GW, and a Gi interface towards the residential/IP network. + +If the L-GW is present within the HNB, the HNB shall use for Gn/S5 connectivity the same secure interface established by the HNB for Iuh signalling as specified in TS 33.320 [16]. + +If the HNB-GW is supporting Fixed Broadband Access network interworking function, the HNB-GW uses a S15 interface towards PCRF for CS sessions as specified in TS 23.139 [36]. + +The HNB may be assigned the same inner IP address for the Gn/S5 interfaces as for the Iuh interface, or a different IP address. + +NOTE: If the HNB uses the same IP address for Gn/S5 and the Iuh interface, they should be assigned distinct ranges of TEIDs in order to be able to discriminate downlink GTP-U packets. + +NOTE: The Security gateway is a logically separated entity and may be implemented either as a separate physical element or integrated into, for example, a HNB-GW. + +The HNB access network includes the functional entities as shown in Figure 4.1-1 and detailed below. + +The HNB access network supports Iurh connectivity between HNBs and connectivity between HNBs and RNCs via the HNB-GW. + +This version of specification supports three different Iurh connectivity options: + +- Option 1: Direct Iurh interface connectivity between the two involved HNBs. +In this case the HNB-GW is not involved at all in Iurh RNL signalling. +- Option 2: Iurh interface connectivity between HNBs with the HNB-GW serving as an Iurh proxy. +In this case the HNB-GW, acting as an Iurh-proxy, appears to a HNB as the peer HNB. +For this connectivity option the role of the HNB-GW is transparent with regard to RNSAP signalling. Conveying respective signalling messages via the HNB-GW is performed by routing based on information provided by the RNSAP User Adaptation (RNA) layer, see TS 25.471 [19]. +- Option 3: Iurh interface connectivity between HNBs and the HNB-GW utilised for transporting RNL signalling between those HNBs and RNCs via the HNB-GW. + +NOTE: If Option 2 and Option 3 coexist, they share the same SCTP association. + +Iurh connectivity between one pair of HNBs shall either support direct Iurh connectivity or Iurh connectivity via the HNB-GW, not both at the same time. + +With respect to HNB-HNB mobility, there is no requirement for a HNB to support direct Iurh connectivity and Iurh connectivity via the HNB-GW at the same time in the current release of the specification. + +### 4.1.1 HNB Management System (HMS) + +The HMS: + +- is based on the TR-069 family of standards [7]. +- facilitates HNB-GW discovery. +- provides configuration data to the HNB. +- performs location verification of HNB and assigns appropriate serving elements (HMS, Security Gateway and HNB-GW). + +### 4.1.2 Security Gateway (SeGW) + +The SeGW: + +- terminates secure tunnelling for TR-069 [7] as well as Iuh. +- terminates secure tunnelling for Iurh and Gn/S5 for certain deployment options. +- authenticates HNBs. +- provides the HNB with access to the HMS and HNB-GW. + +### 4.1.3 HNB Gateway (HNB-GW) + +The HNB Gateway: + +- terminates Iuh from HNB and appears as an RNC to the Core network. +- supports HNB registration and UE registration over Iuh. +- may terminate TNL for the Iurh interface, in case Iurh connectivity via the HNB-GW is deployed for at least one HNB or connectivity to an RNC via the HNB-GW. + +- may support Fixed Broadband Access network interworking via S15 interface towards PCRF for CS sessions as specified in TS23.139 [36]. + +### 4.1.4 HNB + +The HNB: + +- offers the Uu Interface to the UE. +- provides RAN connectivity using the Iuh and Iurh interfaces. +- acts as RNS (details are captured in Table 4.2-1). +- supports HNB registration and UE registration over Iuh. +- In case of LIPA support or SIPTO at the Local Network with collocated L-GW support, it supports the following additional functions: + - transfer of the Gn/S5 IP address of the HNB over Iuh. + - support of basic GGSN/P-GW functions in the collocated L-GW function by support of the Gi/SGi interface corresponding to LIPA or SIPTO@LN. + - Support of use of the Correlation ID or SIPTO Correlation ID, respectively, for correlation purposes between the collocated L-GW function and the HNB. +- In case of Fixed Broadband Access network interworking support, it supports transferring of Tunnel Information over Iu/Iuh as specified in TS 23.139 [36]. + +### 4.1.5 L-GW + +The L-GW function within the HNB provides: + +- in Idle mode, support for sending the first packet to the SGSN/SGW and, buffering of subsequent downlink packets. +- support of internal direct user plane path towards the corresponding HNB user plane functions. +- deactivation of the Gn/S5 interface connection. + +The mobility of the LIPA PDN connection is not supported in this Release of the specification. The LIPA connection is always released with handover as described in TS 23.060 [10]. + +The mobility of the SIPTO@LN PDN connection is not supported in this Release of the specification. The SIPTO@LN PDN connection is always released after a handover is performed, as described in TS 23.060 [10]. + +## 4.2 Functional split + +The UTRAN functions in the HNB are supported by RANAP, whereas the HNB specific functions are supported by the Home Node B Application Protocol (HNBAP) between the HNB and the HNB-GW. The HNB-GW provides a concentration function for the control plane and may provide a concentration function for the user plane. + +This sub-clause defines the functional split between the core network and the UMTS radio access network. The functional split is shown in Table 4.2-1 and 4.2-2. + +**Table 4.2-1. Functional split for UTRAN function in the HNB access.** + +| Function | HNB | HNB-GW | CN | +|-----------------------------------------------------------------|-----|---------------------|----| +| RAB management functions: | | | | +| RAB establishment, modification and release | X | X Note 1 | X | +| RAB characteristics mapping I u transmission bearers | X | X | | +| RAB characteristics mapping U u bearers | X | | | +| RAB queuing, pre-emption and priority | X | | X | +| Radio Resource Management functions: | | | | +| Radio Resource admission control | X | | | +| Broadcast Information | X | X Note 2 | X | +| Iu link Management functions: | | | | +| Iu signalling link management | X | X | X | +| ATM VC management | | X | X | +| AAL2 establish and release | | X | X | +| AAL5 management | | X | X | +| GTP-U Tunnels management | X | X | X | +| TCP Management | | X | X | +| Buffer Management | X | X | | +| Iu U-plane (RNL) Management: | | | | +| Iu U-plane frame protocol management | | | X | +| Iu U-plane frame protocol initialization | X | | | +| Mobility management functions: | | | | +| Location information reporting | X | | X | +| Handover and Relocation | | | | +| Inter RNC hard HO, Iur not used or not available | X | X | X | +| Serving RNS Relocation (intra/inter MSC) | X | X | X | +| Inter system hard HO (UMTS-GSM) | X | X | X | +| Inter system Change (UMTS-GSM) | X | | X | +| Paging Triggering | X | | X | +| Paging Optimization | | X | | +| GERAN System Information Retrieval | X | | X | +| Security Functions: | | | | +| Data confidentiality | | | | +| Radio interface ciphering | X | | | +| Ciphering key management | | | X | +| User identity confidentiality | X | | X | +| Data integrity | | | | +| Integrity checking | X | | | +| Integrity key management | | | X | +| Service and Network Access functions: | | | | +| CN Signalling data | X | | X | +| Data Volume Reporting | X | | | +| UE Tracing | X | | X | +| Location reporting | X | | X | +| Positioning | X | X | | +| Iu Co-ordination functions: | | | | +| Paging co-ordination | X | | X | +| NAS Node Selection Function | | X | | +| MOCN Rerouting Function | | X | X | +| SIPTO at the Local Network with Standalone GW | X | | X | + +Note 1: This function could be needed for TNL address translation in the HNB-GW when there is no user plane direct transport connection between HNB and CN + +Note 2: HNB-GW is able to perform the filtering of SABP messages i.e. determines from the SAI list to which HNB the SABP message needs to be sent and then distributes the SABP messages to the appropriate HNBs. This is an optional function in HNB-GW. + +**Table 4.2-2. Functional split for HNB function in the HNB access.** + +| Function | HNB | HNB-GW | CN | +|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------|-----------| +| HNB Registration Note 1 | | | | +| HNB Registration Function | X | X | | +| HNB-GW Discovery Function | X | | | +| HNB de-registration Function | X | X | | +| UE Registration for HNB Note 1 | | | | +| UE Registration Function for HNB | X | X | | +| UE de-registration Function for HNB | X | X | | +| Iuh user-plane Management functions | | | | +| Iuh User plane transport bearer handling | X | X | | +| Functions for multiplexing CS user plane on the Uplink | X | X | | +| Traffic Offload Functions | | | | +| LIPA | X | | X | +| SIPTO at the Local Network with Collocated L-GW | X | | X | +| Enhanced Interference Management | | | | +| Mitigation of Interference from HNB to Macro | X | | | +| UE Access Control / Membership Verification | | | | +| IDLE mode | X Note2 | X | X | +| Connected mode (inbound relocation to HNB cells) | | X | X | +| CSG ID validation | X | X | | +| CSG Subscription Expiry | X | X | X | +| Iurh Connectivity Functions | | | | +| Iurh Establishment | X | X Note 3 | | +| Exchange of Iurh Connectivity data for neighbour HNBs | X | X | | +| Fixed Broadband Access network Interworking | | | | +| CS sessions | X | X | X | +| PS sessions | X | | X | +| Note 1: Protocol support for this group of functions is provided by the HNB Application Protocol. | | | | +| Note 2: Access control or membership verification at the HNB are optional. | | | | +| Note 3: If the HNB-GW is involved in Iurh Establishment for Iurh connectivity option 2, it acts only as pure relay for this signalling. | | | | + +# 5 UTRAN functions for HNB access + +## 5.1 UE Registration + +### 5.1.1 General + +The UE Registration Function for HNB provides means for the HNB to convey UE identification data to the HNB-GW in order to perform access control or membership verification for the UE in the HNB-GW. The UE Registration also informs the HNB-GW of the specific HNB where the UE is located. + +The following sections illustrate the case when the HNB registers a specific UE with the HNB-GW. The registration is triggered when the UE attempts to access the HNB via an initial NAS message (e.g., Location Updating Request) and there is no context in the HNB allocated for that UE. + +### 5.1.2 UE Registration: case of non CSG UEs or non CSG HNBs + +![Sequence diagram of UE Registration for non CSG UEs or non CSG HNBs. Lifelines: UE, Source HNB, HNB-GW, Target HNB. The process involves RRC Connection Setup, RRC Cell/URA Update, determination of source HNB, optional HNBAP queries, RNA CONNECT, Context transfer, and RRC Cell/URA Update Confirm.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source HNB + participant HNB-GW + participant Target HNB + + Note right of Target HNB: 3. Based on the S-RNTI prefix part of the received U-RNTI, determines the source HNB + + UE->>Source HNB: 1. RRC: Connection Setup. HNB assigns U-RNTI = GW-RNC-ID + HNB S-RNTI-prefix + locally generated bits to UE + Source HNB->>Target HNB: 2. RRC: Cell/URA Update (U-RNTI) + Note right of Source HNB: 3a. If target cannot determine the source, it may optionally query HNB-GW and, if both HNBs support mobility, establish Iurh interface + Target HNB->>HNB-GW: 3a. HNBAP: U-RNTI Query + HNB-GW-->>Target HNB: 3a. RNA: Iurh Setup + Note right of Target HNB: 3b. If target cannot determine the source, it may optionally terminate mobility and re-establish RRC connection + Target HNB->>Source HNB: 4. RNA CONNECT (RNSAP: Uplink Signalling Transfer Indication) + Target HNB->>Source HNB: 5. Context transfer + Source HNB->>UE: 6. RRC: Cell/URA Update Confirm (New U-RNTI: GW-RNC-ID + S-RNTI-prefix (Target HNB) + Locally generate bits) + +``` + +Sequence diagram of UE Registration for non CSG UEs or non CSG HNBs. Lifelines: UE, Source HNB, HNB-GW, Target HNB. The process involves RRC Connection Setup, RRC Cell/URA Update, determination of source HNB, optional HNBAP queries, RNA CONNECT, Context transfer, and RRC Cell/URA Update Confirm. + +**Figure 5.1.2-1: UE Registration for non CSG UEs or non CSG HNBs.** + +- Upon camping on the HNB, the UE initiates an initial NAS procedure (e.g. LU Procedure) by establishing an RRC connection with the HNB. UE identity, UE capabilities and Establishment Cause, are reported to the HNB as part of the RRC Connection establishment procedure. +- The UE then transmits a RRC Initial Direct Transfer message carrying the initial NAS message (e.g. Location Updating Request message) with some form of UE identity. +- The HNB checks the UE capabilities provided in step 1, and if these indicate that CSG is not supported, or the HNB itself does not support CSG, and if the identity of the UE (provided during RRC Connection Establishment) is unknown at the HNB being accessed, i.e. no Context id exists for the UE, the HNB initiates UE registration towards the HNB-GW (step 5-7). Before starting the UE Registration procedure, the HNB triggers the Identity request procedure (step 3) asking the UE for its IMSI, unless that identity has been provided during the RRC Connection Establishment or optionally if it is an emergency call. If the HNB has a context id for the UE, the UE registration procedure is not performed nor is the Identification procedure. +- The HNB may optionally perform access control or membership verification based on the provided IMSI and the provided Allowed IMSI list. If the UE requests emergency services it shall always be admitted to the cell. +- The HNB attempts to register the UE on the HNB-GW by transmitting the UE REGISTER REQUEST. The message contains at a minimum: + - **UE Identity:** a unique identity for the UE provided in step 1 or 3. + - **UE Capabilities:** derived from that provided in step 1. + - **Registration Cause:** the indication about a UE registration for an emergency call. + +NOTE: The UE Identity provided in the HNBAP UE REGISTER REQUEST message is unauthenticated. + +6. The HNB-GW checks the UE capabilities and the Registration Cause. If the UE capabilities indicate that CSG is not supported or if the HNB does not support CSG, the HNB-GW shall perform access control or membership verification for the particular UE attempting to utilize the specific HNB. If the UE requests emergency services it shall always be admitted to the cell. +7. If the HNB-GW accepts the UE registration attempt it shall allocate a context-id for the UE and respond with an HNBAP UE REGISTER ACCEPT message, including the context-id, to the HNB. For non-CSG UEs, the HNB-GW may also include the CSG Membership Status in the HNBAP UE REGISTER ACCEPT message. If the HNB-GW chooses not to accept the incoming UE registration request then the HNB-GW shall respond with an HNBAP UE REGISTER REJECT message. +8. The HNB then sends an RUA CONNECT message containing the RANAP Initial UE message. If a L-GW function is deployed within the HNB the RANAP Initial UE message includes the corresponding IP address for Gn/S5 signalling and user data transport on the Gi interface. +9. The reception of the RUA CONNECT message at the HNB-GW triggers the setup of an SCCP connection by the HNB-GW towards the CN. The HNB-GW then forwards the RANAP Initial UE Message to the CN. +10. The CN responds with an SCCP Connection Confirm message. +- 10a. The HNB-GW shall additionally utilize a CN assisted method if available (e.g. using IMSI provided in the COMMON ID message), to alleviate the security risks associated with spoofing of IMSI and can subsequently trigger a UE deregistration upon detection of such an event. +11. The UE continues with the NAS procedure (e.g. Location Updating procedure) towards the CN, via the HNB and the HNB-GW. + +### 5.1.3 UE Registration: case of CSG UEs and CSG or Hybrid HNBs + +This call flow assumes that the Core Network is able to perform access control on the basis of Closed Subscriber Groups. + +![Sequence diagram of UE Registration for CSG UEs and CSG or Hybrid HNBs. The diagram shows the interaction between UE, HNB, HNB GW, and CN. The process starts with RRC Connection Establishment from UE to HNB, followed by RRC Initial Direct Transfer (e.g., LU Request) from UE to HNB. The HNB performs a 'Check Release, UE Capabilities' step. Then, the HNB sends a UE Registration message (TMSI or IMSI, Rel, UE Cap,...) to the HNB GW. The HNB GW sends a UE Registration message to the CN. The CN responds with a UE Registration Accept (Context-id,...) to the HNB GW. The HNB GW then sends a Connect (Initial UE Message,...) to the HNB. The HNB sends an SCCP CR (Initial UE Message,...) to the CN. The CN responds with an SCCP CC to the HNB GW. The HNB GW then sends an Optional MM message to the UE. The CN performs an Access Control or Membership Verification. Finally, the UE continues with the NAS procedure.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant HNB_GW as HNB GW + participant CN + + Note left of UE: 1. RRC Connection Est. (TMSI or IMSI, UE Rel, UE Cap, ..) + UE->>HNB: 2. RRC Initial Direct Transfer (e.g. LU Request,...) + Note right of HNB: 3. Check Release, UE Capabilities + HNB->>HNB_GW: 4. UE Registration (TMSI or IMSI, Rel, UE Cap,...) + Note right of HNB_GW: 5. UE Registration + HNB_GW->>CN: 6. UE Registration Accept (Context-id,...) + CN->>HNB_GW: 7. Connect (Initial UE Message,...) + HNB_GW->>HNB: 8. SCCP CR (Initial UE Message,...) + HNB->>CN: 9. SCCP CC + Note right of CN: 10. Optional MM + CN->>UE: 10. Optional MM + Note right of CN: 11. Access Control or Membership Verification + Note left of UE: 12. Continue with NAS procedure + +``` + +Sequence diagram of UE Registration for CSG UEs and CSG or Hybrid HNBs. The diagram shows the interaction between UE, HNB, HNB GW, and CN. The process starts with RRC Connection Establishment from UE to HNB, followed by RRC Initial Direct Transfer (e.g., LU Request) from UE to HNB. The HNB performs a 'Check Release, UE Capabilities' step. Then, the HNB sends a UE Registration message (TMSI or IMSI, Rel, UE Cap,...) to the HNB GW. The HNB GW sends a UE Registration message to the CN. The CN responds with a UE Registration Accept (Context-id,...) to the HNB GW. The HNB GW then sends a Connect (Initial UE Message,...) to the HNB. The HNB sends an SCCP CR (Initial UE Message,...) to the CN. The CN responds with an SCCP CC to the HNB GW. The HNB GW then sends an Optional MM message to the UE. The CN performs an Access Control or Membership Verification. Finally, the UE continues with the NAS procedure. + +Figure 5.1.3-1: UE Registration for CSG UEs and CSG or Hybrid HNBs. + +1. Upon camping on the HNB, the UE initiates an initial NAS procedure (e.g. LU Procedure) by establishing an RRC connection with the HNB. UE identity and UE capabilities are reported to the HNB as part of the RRC Connection establishment procedure. +2. The UE then transmits a RRC Initial Direct Transfer message carrying the initial NAS message (e.g. Location Updating Request message) with some form of identity (e.g. IMSI or TMSI...). +3. The HNB checks the UE capabilities provided in step 1, and if these indicate that CSG is supported and if the identity of the UE (provided during RRC Connection Establishment) is unknown at the HNB being accessed, i.e. no Context id exist for the UE, the HNB initiates UE registration towards the HNB-GW (steps 4-6). If the HNB has a context id for the UE, UE registration procedure is not performed. No Identification procedure is triggered, independent of the identity reported by the UE during the RRC Connection Establishment. +4. The HNB attempts to register the UE on the HNB-GW by transmitting the UE REGISTER REQUEST. The message contains: + - **UE Identity:** a unique identifier for the UE and provided in step 1. + - **UE capabilities:** derived from that provided in step 1. + - **Registration Cause:** the indication about a UE registration for an emergency call. + +NOTE: The UE Identity provided in the UE REGISTER message is unauthenticated. + +5. The HNB-GW checks UE capabilities and if these indicate that CSG is supported and if the HNB supports CSG, the HNB-GW may accept the UE registration and allocate a context-id for the UE. +6. The HNB-GW responds with a UE REGISTER ACCEPT message back to the HNB including a context-id allocated to the UE +7. The HNB then sends a RUA CONNECT message containing the RANAP Initial UE message. The RANAP Initial UE message may contain the Cell Access Mode. If a L-GW function is deployed within the HNB, the RANAP Initial UE message includes the corresponding IP address for Gn/S5 interface signalling and user data transport on the Gi interface. +8. The HNB-GW shall verify, for CSG HNBs, that the validity of the indicated cell access mode and the CSG ID in the Initial UE message as specified in TS 33.320 [16]. The reception of the RUA CONNECT message at the HNB-GW triggers the setup of an SCCP connection by the HNB-GW towards the CN. The HNB-GW then forwards the Initial UE Message including the CSG id of the HNB. +9. The CN responds with an SCCP Connection Confirm message. +10. The CN may optionally perform Mobility Management procedures, e.g. Authentication procedure. +11. The CN performs access control (in case of CSG cells) or membership verification (in case of Hybrid cells) of the UE. +12. After being granted access the UE then continues with the NAS procedure (e.g. Location Updating procedure) towards the CN, via the HNB and the HNB-GW. During such procedures the CN may send to the HNB the UE membership status for the accessed cell in the COMMON ID message. + +### 5.1.4 HNB-GW triggered UE Registration + +The following section describes the mechanism, which is used to manage UE registration and associated context IDs for the scenarios based on HNB-GW triggered setup of UE-associated Signalling Connection. + +In this mechanism, the RUA Connect message is used for transporting the first RANAP message resulting in network triggered setup of UE-associated Signalling Connection (e.g. RANAP Relocation Request). + +![Sequence diagram for HNB-GW Triggered UE Registration. Lifelines: HNB1, HNB2, HNB-GW. The sequence starts with a message '1. Establish reliable transport session (SCTP)' between HNB1 and HNB2. Then, HNB1 sends '2. RNA Iurh Setup Request' to HNB2. HNB2 sends '3a. HNBAP Configuration Transfer Request' to HNB-GW. HNB-GW sends '3b. HNBAP Configuration Transfer Response' back to HNB2. Finally, HNB2 sends '4. RNA Iurh Setup Response' to HNB1.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` +sequenceDiagram + participant HNB1 + participant HNB2 + participant HNB-GW + Note over HNB1, HNB2: 1. Establish reliable transport session (SCTP) + HNB1->>HNB2: 2. RNA Iurh Setup Request + HNB2->>HNB-GW: 3a. HNBAP Configuration Transfer Request + HNB-GW-->>HNB2: 3b. HNBAP Configuration Transfer Response + HNB2->>HNB1: 4. RNA Iurh Setup Response +``` + +Sequence diagram for HNB-GW Triggered UE Registration. Lifelines: HNB1, HNB2, HNB-GW. The sequence starts with a message '1. Establish reliable transport session (SCTP)' between HNB1 and HNB2. Then, HNB1 sends '2. RNA Iurh Setup Request' to HNB2. HNB2 sends '3a. HNBAP Configuration Transfer Request' to HNB-GW. HNB-GW sends '3b. HNBAP Configuration Transfer Response' back to HNB2. Finally, HNB2 sends '4. RNA Iurh Setup Response' to HNB1. + +**Figure 5.1.4-1: HNB-GW Triggered UE Registration.** + +The above call flow assumes that the HNB-GW receives a trigger for inbound relocation for a UE (e.g. RANAP Relocation Request message from the CN) as shown in step 0. + +1. The HNB-GW receives a RANAP message and determines the target HNB. +2. The HNB-GW sends the RANAP message encapsulated in the RUA Connect message to the target HNB. The RUA Connect Message may contain the *CSG Membership Status* IE. +3. The HNB-GW and the target HNB perform an implicit registration (HNB-GW establishes a UE specific Context Identifier to be used between the HNB and the HNB-GW, i.e., either re-use the existing Context Identifier if already present for the UE or otherwise allocate a new one) for the incoming UE session. The HNB also allocates the appropriate resource for handling the request in the RANAP message. +4. The RANAP reply message from the HNB to the HNB-GW is encapsulated in the RUA *Direct Transfer* message. + +In the case that the target HNB rejects the inbound relocation, the rejection message (e.g., RANAP Relocation Failure) is carried by a RUA Disconnect message, an implicit UE Deregistration takes place, and the resources allocated for handling the request are released. + +### 5.1.5 UE Registration: case of Open Access HNBs + +![Sequence diagram of UE Registration to open access HNBs. The diagram shows the interaction between UE, HNB, HNB GW, and CN. The steps are: 1. RRC Connection Est. (TMSI or IMSI, UE Rel, UE Cap, ..) from UE to HNB; 2. RRC Initial Direct Transfer (e.g. LU Request,...) from UE to HNB; 3. Check UE Identity (internal HNB step); 4. UE Registration (TMSI or IMSI, Rel, UE Cap,..) from HNB to HNB GW; 5. UE Registration (internal HNB GW step); 6. UE Registration Accept (Context-id,..) from HNB GW to HNB; 7. Connect (Initial UE Message,..) from HNB to HNB GW; 8. SCCP CR (Initial UE Message,..) from HNB GW to CN; 9. SCCP CC from CN to HNB GW; 10. Optional MM from CN to UE (dashed line); 11. Continue with NAS procedure (horizontal bar at the bottom).](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant HNB_GW as HNB GW + participant CN + Note left of UE: 1. RRC Connection Est. (TMSI or IMSI, UE Rel, UE Cap, ..) + UE->>HNB: 2. RRC Initial Direct Transfer (e.g. LU Request,...) + Note right of HNB: 3. Check UE Identity + HNB->>HNB_GW: 4. UE Registration (TMSI or IMSI, Rel, UE Cap,..) + Note right of HNB_GW: 5. UE Registration + HNB_GW->>HNB: 6. UE Registration Accept (Context-id,..) + HNB->>HNB_GW: 7. Connect (Initial UE Message,..) + HNB_GW->>CN: 8. SCCP CR (Initial UE Message,..) + CN->>HNB_GW: 9. SCCP CC + Note right of CN: 10. Optional MM + CN-->>UE: 10. Optional MM + Note bottom: 11. Continue with NAS procedure + +``` + +Sequence diagram of UE Registration to open access HNBs. The diagram shows the interaction between UE, HNB, HNB GW, and CN. The steps are: 1. RRC Connection Est. (TMSI or IMSI, UE Rel, UE Cap, ..) from UE to HNB; 2. RRC Initial Direct Transfer (e.g. LU Request,...) from UE to HNB; 3. Check UE Identity (internal HNB step); 4. UE Registration (TMSI or IMSI, Rel, UE Cap,..) from HNB to HNB GW; 5. UE Registration (internal HNB GW step); 6. UE Registration Accept (Context-id,..) from HNB GW to HNB; 7. Connect (Initial UE Message,..) from HNB to HNB GW; 8. SCCP CR (Initial UE Message,..) from HNB GW to CN; 9. SCCP CC from CN to HNB GW; 10. Optional MM from CN to UE (dashed line); 11. Continue with NAS procedure (horizontal bar at the bottom). + +**Figure 5.1.5-1: UE Registration to open access HNBs.** + +- Upon camping on the HNB, the UE initiates an initial NAS procedure (e.g. LU Procedure) by establishing an RRC connection with the HNB. UE identity and UE capabilities are reported to the HNB as part of the RRC Connection establishment procedure. + - The UE then transmits a RRC Initial Direct Transfer message carrying the initial NAS message (e.g. Location Updating Request message) with some form of identity (e.g. IMSI or TMSI). + - If the identity of the UE (provided during RRC Connection Establishment) is unknown at the HNB being accessed, i.e. no Context id exist for the UE, the HNB initiates UE registration towards the HNB-GW (steps 4-6). If the HNB has a context id for the UE, UE registration procedure is not performed. No Identification procedure is triggered, independent of the identity reported by the UE during the RRC Connection Establishment. + - The HNB attempts to register the UE on the HNB-GW by transmitting the UE REGISTER REQUEST. The message contains: + - **UE Identity**: a unique identifier for the UE and provided in step 1. + - **UE capabilities**: derived from that provided in step 1. + - **Registration Cause**: the indication about a UE registration for an emergency call. +- NOTE: The UE Identity provided in the UE REGISTER message is unauthenticated. +- The HNB-GW may accept the UE registration and allocate a context-id for the UE. + - The HNB-GW responds with a UE REGISTER ACCEPT message back to the HNB including a context-id allocated to the UE. + - The HNB then sends a RUA CONNECT message containing the RANAP Initial UE message. + +8. The reception of the RUA CONNECT message at the HNB-GW triggers the setup of an SCCP connection by the HNB-GW towards the CN. The HNB-GW then forwards the Initial UE Message to the Core Network. +9. The CN responds with an SCCP Connection Confirm message. +10. The CN may optionally perform Mobility Management procedures, e.g. Authentication procedure. +11. After being granted access the UE then continues with the NAS procedure (e.g. Location Updating procedure) towards the CN, via the HNB and the HNB-GW. + +## 5.2 HNB Registration + +### 5.2.1 General + +The following section illustrates the case when the HNB registers with the HNB-GW. The HNB registration procedure serves the following purposes: + +- It informs the HNB-GW that a HNB is now available at a particular IP address. + +### 5.2.2 HNB Registration procedure + +![Sequence diagram of the HNB Registration procedure. The diagram shows three participants: HNB, SeGW, and HNB-GW. The sequence of messages is: 1. HNB Initialization (internal to HNB); 2. Establish secure tunnel (HNB to SeGW); 3. Establish Reliable Transport Session for Iuh signalling (HNB to HNB-GW); 4. HNB REGISTER REQUEST (Location Information, HNB Identity, HNB Operating Parameters) (HNB to HNB-GW); 5a. HNB REGISTER ACCEPT (...) (HNB-GW to HNB); 5b. HNB REGISTER REJECT (Reject Cause) (HNB-GW to HNB, dashed line); 6. Establish Reliable Transport Session for Iurh signalling (HNB to HNB-GW).](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant SeGW + participant HNB-GW + Note left of HNB: 1. HNB Initialization + HNB->>SeGW: 2. Establish secure tunnel + HNB->>HNB-GW: 3. Establish Reliable Transport Session for Iuh signalling + HNB->>HNB-GW: 4. HNB REGISTER REQUEST (Location Information, HNB Identity, HNB Operating Parameters) + HNB-GW-->>HNB: 5a. HNB REGISTER ACCEPT (...) + HNB-GW-->>HNB: 5b. HNB REGISTER REJECT (Reject Cause) + HNB->>HNB-GW: 6. Establish Reliable Transport Session for Iurh signalling + +``` + +Sequence diagram of the HNB Registration procedure. The diagram shows three participants: HNB, SeGW, and HNB-GW. The sequence of messages is: 1. HNB Initialization (internal to HNB); 2. Establish secure tunnel (HNB to SeGW); 3. Establish Reliable Transport Session for Iuh signalling (HNB to HNB-GW); 4. HNB REGISTER REQUEST (Location Information, HNB Identity, HNB Operating Parameters) (HNB to HNB-GW); 5a. HNB REGISTER ACCEPT (...) (HNB-GW to HNB); 5b. HNB REGISTER REJECT (Reject Cause) (HNB-GW to HNB, dashed line); 6. Establish Reliable Transport Session for Iurh signalling (HNB to HNB-GW). + +**Figure 5.2.2-1: HNB Registration procedure.** + +1. HNB initialization is performed to obtain HNB configuration from the HNB Management System (HMS). Similarly, HNB-GW discovery is performed to obtain the initial serving HNB-GW information. +2. The HNB establishes a secure tunnel to the SeGW of the serving HNB-GW. + +NOTE: This step may be omitted if the secure tunnel happens to be the same tunnel that is already established to contact the HMS. + +3. The HNB sets up an SCTP transport session to the registered port on the serving HNB-GW for Iuh. +4. The HNB then attempts to register with the serving HNB-GW using an HNB REGISTER REQUEST message. The message contains: + - a. **HNB Location Information:** The HNB provides location information via use of one or more of the following mechanisms: + - i. Detected macro-cell coverage information (e.g. GERAN or UTRAN cell information). + - ii. Geographical co-ordinates (e.g. via use of GPS, etc). + +- iii. Internet connectivity information (e.g. IP address), provided, the resulting location information is at least as accurate as location determination based on macro-cell coverage information, whether or not there is macro cell-coverage available at the location of the HNB (e.g. as determined by point i above). + - b. **HNB Identity:** the HNB has a globally unique and permanent identity. + - c. **HNB Operating Parameters:** Such as the selected LAC, RAC, SAC, PLMN Id, Cell Id, etc. + - d. **HNB operating mode** (optional): HNB CSG-Id or access mode (open, closed or hybrid). + - e. **HNB's own IP address** for direct Iurh connectivity (if Iurh connectivity is supported by the HNB). + - f. **CELL\_FACH mobility support**, if the HNB supports mobility for CELL\_FACH, CELL\_PCH and URA\_PCH. + - g. **Additional Neighbour Information:** The HNB may indicate additional neighbour information necessary for CELL\_FACH mobility. This additional information may be used by HNB-GW to manage the assignment of S-RNTI prefixes. +- 5a. The HNB-GW may use the information from the HNB REGISTER REQUEST message to check whether the HNB registration can be accepted (e.g. to check whether a particular HNB is allowed to operate in a given location, etc). The HNB-GW shall verify the HNB identity, the validity of the indicated cell access mode and, for CSG cells, the CSG ID as specified in TS 33.320 [16]. If the HNB-GW accepts the registration attempt it shall respond with a HNB REGISTER ACCEPT message. If the HNB-GW has capability to de-multiplex, the HNB-GW may include a mux port in the HNB REGISTER ACCEPT message. The HNB shall include the RNC-ID provided by the HNB-GW within relevant RANAP messages in order to identify the HNB-GW during mobility procedures and within RRC messages, where the RNC-ID has to be contained within the most significant bits of the Cell Identification and be part of the U-RNTI. + +In order to support CELL\_FACH/CELL\_PCH/URA\_PCH mobility, the S-RNTI Prefix value is sent to the HNB. The HNB that supports S-RNTI prefix assignment shall include the S-RNTI prefix in the most significant bits of S-RNTI part following the RNC ID bits in the U-RNTI. + +The HNB-GW may provide its IP address in order to allow the HNB to either establish Iurh-connectivity via the HNB-GW or to establish connectivity to an RNC via the HNB-GW. + +The HNB-GW ensures that the S-RNTI prefixes assigned to HNBs are unique within the URA Area/overlapping URA Areas. If supported, the HNB-GW may reuse the S-RNTI prefix across non overlapping areas. + +- 5b. Alternatively, the HNB-GW may reject the registration request (e.g. due to network congestion, blacklisted HNB, unauthorized HNB location, etc). In this case, the HNB-GW shall respond with an HNB REGISTER REJECT indicating the reject cause. +- 6. If the HNB-GW had provided in the HNB REGISTER ACCEPT message the HNB-GW's own IP address for Iurh connectivity via/to the HNB-GW, the HNB shall, if supported, set up an SCTP transport session to the port registered for Iurh. + +NOTE: The HNB shall start broadcasting only after successful registration with the HNB-GW. + +## 5.3 HNB-GW Discovery Function + +### 5.3.1 General + +The HNB-GW Discovery Function provides the means to determine the address of the Serving HNB-GW for a particular HNB. The HNB uses the Serving HNB-GW address to register with the Serving HNB-GW. + +## 5.4 HNB de-registration Function + +### 5.4.1 General + +The HNB de-registration Function provides the means to terminate the HNB operation. The HNB de-registration can be initiated by either the HNB or the HNB-GW. + +## 5.5 Iuh Disconnect + +### 5.5.1 General + +The following section illustrates the scenario where an UE-associated signalling connection is released across the Iuh. In this scenario the HNB is responsible for initiating the release of the UE-associated signalling connection via the RUA disconnect message. The HNB-GW is then responsible for co-ordinating the release of the UE-associated Iuh signalling connection with the corresponding Iu connection, which is triggered by the CN. + +### 5.5.2 Iuh Disconnect procedure + +![Sequence diagram of the Iuh Disconnect procedure showing interactions between UE, HNB, HNB-GW, and CN.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` +sequenceDiagram + participant UE + participant HNB + participant HNB-GW + participant CN + + Note over UE, HNB, HNB-GW, CN: 1. Establish Connection between UE and Network + Note over UE, HNB, HNB-GW, CN: + CN->>HNB-GW: 2. SCCP:DT1 (RANAP Iu Release Command) + HNB-GW->>HNB: 3. RUA Direct Transfer (Context-Id, CN Domain Id , RANAP Iu Release Command ) + Note over HNB: 4. Release RRC Connection + HNB->>HNB-GW: 5. RUA Disconnect (Context-ID, CN Domain ID , RANAP Iu Release Complete) + HNB-GW->>CN: 6. SCCP:DT1 (RANAP Iu Release Complete) + CN->>HNB-GW: 7. SCCP: RLSD + HNB-GW->>CN: 8. SCCP: RLC + HNB->>HNB-GW: 9. (opt) HNBAP UE De-register (Context-ID) +``` + +The sequence diagram illustrates the Iuh Disconnect procedure. It begins with a shared activation bar labeled '1. Establish Connection between UE and Network'. The procedure then proceeds as follows: 1. The CN sends an SCCP:DT1 (RANAP Iu Release Command) message to the HNB-GW. 2. The HNB-GW forwards this via a RUA Direct Transfer (Context-Id, CN Domain Id , RANAP Iu Release Command ) message to the HNB. 3. The HNB triggers the 'Release RRC Connection' with the UE. 4. The HNB sends a RUA Disconnect (Context-ID, CN Domain ID , RANAP Iu Release Complete) message to the HNB-GW. 5. The HNB-GW responds with an SCCP:DT1 (RANAP Iu Release Complete) message to the CN. 6. The CN replies with SCCP: RLSD. 7. The HNB-GW then sends an SCCP: RLC message to the CN. 8. Finally, an optional HNBAP UE De-register (Context-ID) message is sent from the HNB to the HNB-GW. + +Sequence diagram of the Iuh Disconnect procedure showing interactions between UE, HNB, HNB-GW, and CN. + +Figure 5.5.2-1: Iuh Disconnect procedure. + +1. Establish connection between UE and network. The related procedure is described in subclause 5.1. +2. CN sends a RANAP Release Iu connection command message to the HNB-GW. +3. HNB-GW forwards this message to the relevant HNB. +4. HNB triggers the release of the RRC connection to the UE. In this case a single Iu connection had been established for the UE. + +5. HNB sends a Disconnect message to the HNB-GW to indicate that this is the end of this particular UE-associated signalling connection and includes the RANAP Release Iu Connection Complete message. +6. HNB-GW forwards the RANAP message onto the CN. +7. CN triggers the release of the associated SCCP connection. +8. HNB-GW confirms that the SCCP connection is released. +9. Optionally the HNB can de-register the UE context from the HNB-GW. + +## 5.6 Paging Optimization Function + +### 5.6.1 General + +The paging optimization function provides the means to decrease the impact of a paging load over Iuh (for example, via the use of knowledge about the UE Registration or its CSG Id List in the PAGING message). + +## 5.7 HNB to HNB Mobility + +### 5.7.1 General + +The following sub-sections describe the mechanism for handling the intra HNB-GW mobility signalling via Iurh. + +### 5.7.2 Connected mode mobility from one HNB to another HNB (Intra PLMN, Intra HNB-GW, Intra CSG) + +#### 5.7.2.1 C-Plane Handling + +RNSAP Relocation utilises existing protocol functions specified for Enhanced Relocation between non-CSG cells within TS 25.413 [9] and TS 25.423 [18]. + +Additional information from the Source HNB to the Target HNB is provided within the RANAP Enhanced Relocation Information and the RANAP Relocation Information procedures as specified in subclause 5.10. + +Figure 5.7.2.1-1 below depicts the case where the UE is involved in the RNSAP Relocation and the HNBs are directly Iurh-connected. In case of UE not being involved, an Iurh signalling connection (i.e. RNA signalling resources) already exists between the involved HNBs which can be utilised for RNSAP signalling. In case of Iurh-connectivity via the HNB-GW, RNA signalling terminates at the HNB-GW, whereas RNSAP signalling is still performed peer-to-peer. + +![Sequence diagram of HNB to HNB Handover via Iurh interface with UE involved. Lifelines: UE, Source HNB, Target HNB, HNB-GW, CN. The process involves 10 steps: 1. RNA Connect: RNSAP Enhanced Relocation Request from Source HNB to Target HNB; 2a. HNBAP TNL Update Request from Target HNB to HNB-GW; 2b. HNBAP TNL Update Response from HNB-GW to Target HNB; 3. RNA Direct Transfer: RNSAP Enhanced Relocation Response from Target HNB to Source HNB; 4. RNA Direct Transfer: RNSAP Relocation Commit from Source HNB to Target HNB; 5. RRC RB Reconfiguration from Source HNB to UE; 6. RRC RB Reconfiguration Complete from UE to Target HNB (with 'Detect UE sync' label); 7. HNBAP Relocation Complete from Target HNB to HNB-GW; 8a. RAB Release Request (Unaccepted RABs) from Target HNB to CN; 8b. RAB Assignment Procedure to release unaccepted RABs (between CN and HNB-GW); 9. HNBAP UE De-Registration from HNB-GW to Source HNB; 10. RNA Disconnect: RNSAP Enhanced Relocation Signalling Transfer (L3 information) from Source HNB to Target HNB.](26d664119ad25250780f554633444e54_img.jpg) + +Sequence diagram of HNB to HNB Handover via Iurh interface with UE involved. Lifelines: UE, Source HNB, Target HNB, HNB-GW, CN. The process involves 10 steps: 1. RNA Connect: RNSAP Enhanced Relocation Request from Source HNB to Target HNB; 2a. HNBAP TNL Update Request from Target HNB to HNB-GW; 2b. HNBAP TNL Update Response from HNB-GW to Target HNB; 3. RNA Direct Transfer: RNSAP Enhanced Relocation Response from Target HNB to Source HNB; 4. RNA Direct Transfer: RNSAP Relocation Commit from Source HNB to Target HNB; 5. RRC RB Reconfiguration from Source HNB to UE; 6. RRC RB Reconfiguration Complete from UE to Target HNB (with 'Detect UE sync' label); 7. HNBAP Relocation Complete from Target HNB to HNB-GW; 8a. RAB Release Request (Unaccepted RABs) from Target HNB to CN; 8b. RAB Assignment Procedure to release unaccepted RABs (between CN and HNB-GW); 9. HNBAP UE De-Registration from HNB-GW to Source HNB; 10. RNA Disconnect: RNSAP Enhanced Relocation Signalling Transfer (L3 information) from Source HNB to Target HNB. + +**Figure 5.7.2.1-1: HNB to HNB Handover via Iurh interface – UE involved.** + +1. The Source HNB evaluates the UE's access rights against the available neighbour information. If the UE has access rights for the Target HNB the Source HNB may decide to send an RNA:CONNECT message (or an RNA:DIRECT TRANSFER message if already in SHO) containing an RNSAP:ENHANCED RELOCATION REQUEST message to the Target HNB to prepare the Target HNB for relocation. +2. The Target HNB updates the transport network layer information for any RABs that are to be relocated to it by sending an HNBAP:TNL UPDATE REQUEST message to the HNB-GW, the HNB-GW responds with an HNBAP:TNL UPDATE RESPONSE. +3. The Target HNB sends an RNA:DIRECT TRANSFER message containing an RNSAP:ENHANCED RELOCATION RESPONSE message back to the Source HNB to indicate that it has successfully prepared the relocation. +4. The Source HNB sends an RNA:DIRECT TRANSFER message containing an RNSAP:RELOCATION COMMIT message, to commit the relocation preparation on the Target HNB. This message includes information to aid the relocation procedure, these are described in subclause 5.10. +5. The Source HNB reconfigures the UE to commence the relocation procedure. +6. At some point later Layer 1 synchronisation is achieved between the UE and the Target HNB. The UE then completes the RRC Reconfiguration procedure by sending an RRC:RADIO BEARER RECONFIGURATION COMPLETE message to the Target HNB. +7. The Target HNB indicates to the HNB-GW that the UE has successfully relocated via the HNBAP:UE RELOCATION COMPLETE message. The HNB-GW also switches the U-plane to the Target HNB. +8. The Target HNB initiates the RAB Release Request Procedure to the CN to release unaccepted RABs, if any, with an appropriate cause value. +9. The HNB-GW sends the HNBAP:UE-DEREGISTER to the Source HNB indicating Successful RNSAP Relocation with an appropriate cause value. +10. RNA Disconnect: RNSAP Enhanced Relocation Signalling Transfer (L3 information) from Source HNB to Target HNB. + +10. The Source HNB sends an RNA:DISCONNECT message containing an RNSAP:ENHANCED RELOCATION SIGNALLING TRANSFER message to the Target HNB to transfer any L3 information that the Source HNB may have received during the relocation procedure and locally releases any resources it has for the UE. + +NOTE: If the involved HNBs are Iurh connected via the HNB-GW, the RNA messages are routed via the HNB-GW. + +#### 5.7.2.2 User Plane Handling + +In order to keep the CN unaware of any Intra-GW mobility for RABs operating in support mode (see TS 25.415 [17]), which would normally need an Iu-UP initialization procedure during relocation, the respective user plane configuration (RFCIs, etc.) has to be transferred to the Target HNB without actually carrying out the Iu-UP Initialisation procedure towards its peer node. Special handling of related control and user data frame sequence numbers has to be applied. + +In order to avoid problems with Iu-UP version interworking, the Target HNB shall support at least the same versions of Iu UP and rate parameters used by the Source HNB. + +In order to allow seamless Iu-UP operation from a CN perspective, + +- the Source HNB: + - shall provide the Target HNB within RANAP ENHANCED RELOCATION INFORMATION REQUEST message with + - CS IuUP control information needed to allocate IuUP instances for those RABs operated in support mode. + - the latest CS Iu-UP user-data frame-numbers for UL and DL for all CS RABs operated in support mode for which user data frame numbering is based on time together with the time-difference between UL and DL packets as received/sent on the source side. + - shall provide the Target HNB within RANAP RELOCATION INFORMATION message (encapsulated within the RNSAP message RELOCATION COMMIT) with + - CS IuUP control information needed to allocate IuUP instances for those RABs operated in support mode, if the IuUP configuration of the RABs has changed. + - the latest CS Iu-UP control-data frame-numbers for UL and DL for all CS RABs operated in support mode. + - the latest CS Iu-UP user-data frame-numbers for UL and DL for all CS RABs operated in support mode for which user data frame numbering is based on time together with the time-difference between UL and DL packets as received/sent on the source side. + - the last sent DL and last received and forwarded UL user-data frame number for those CS RABs for which user-data frame-numbering is based on sent Iu UP PDU. + - the latest PS Iu-UP user-data frame-numbers for UL and DL for all applicable PS RABs. + - may start to forward user plane packets towards the Target-HNB for those RABs for which it has decided to perform data forwarding, when triggering the execution of the RNSAP Relocation (exact sequence of actions is implementation specific). + - not initiate any Iu-UP procedure and ignore incoming Iu-UP control frames, after having sent the RNSAP message RELOCATION COMMIT. +- the Target-HNB shall + - after having received the RANAP ENHANCED RELOCATION INFORMATION REQUEST message + - use the information provided by the Source HNB to establish Iu-UP instances for receiving user Iu-UP frames from the Source HNB and may use the information of the last CS Iu-UP UL/DL user-data frame number as received from the source together with received DL user-data frames to re-install the timing and frame-numbering for UL/DL user-data frames once the first DL user data packet is received from the Source HNB. + +- use the information provided by the Source HNB to establish Iu-UP instances. + - for each CS RAB operated in support mode, use the information of the last CS Iu-UP UL/DL user-data frame number as received from the source together with received DL user-data frames to re-install the timing and frame-numbering for UL/DL user-data frames once the first DL user data packet is received + - not initiate any Iu-UP procedure and ignore incoming Iu-UP control frames. +- after having received the HNBAP: TNL UPDATE RESPONSE message from the HNB-GW + - use the information provided by the Source HNB to establish Iu-UP instances for receiving user Iu-UP frames from the HNB-GW and use the information of the last CS Iu-UP UL/DL user-data frame number as received from the source together with received DL user-data frames to re-install the timing and frame-numbering for UL/DL user-data frames once the first DL user data packet is received from the HNB-GW. + - not initiate any Iu-UP procedure and ignore incoming Iu-UP control frames. +- after having received the RNSAP message RELOCATION COMMIT + - use the information of the last CS Iu-UP UL control-data frame number as received from the Source HNB for the next to be sent UL control-data frame. + - ignore any loss of DL control frames and start respective error handling after the first received DL control frame. + - use the information of the last CS Iu-UP UL/DL user-data frame number as received from the source together with received DL user-data frames to re-adjust the timing and frame-numbering for UL/DL user-data frames, if necessary. + - start Iu-UP procedures as necessary (e.g. downlink rate control (due to e.g. local congestion), Iu Time Alignment). +- the HNB-GW shall + - after receipt of the HNBAP:RELOCATION COMPLETE message + - switch the TNL part of the UP completely towards the Target HNB. + +### 5.7.3 Soft Handover Initiation + +Figure 5.7.3-1 below depicts Soft Handover Initiation in case HNBs are directly Iurh-connected. In case of Iurh-connectivity via the HNB-GW, RNA signalling terminates at the HNB-GW, whereas RNSAP signalling is still performed on a HNB-to-HNB basis. + +![Sequence diagram illustrating Soft Handover Initiation HNB to HNB. The diagram shows the interaction between a UE, SHNB, and DHNB. The process starts with the UE sending an RRC Measurement Report to the SHNB. The SHNB makes a decision to setup a new radio link (RL) and sends an RNA CONNECT message (containing UE context id and RNSAP Radio Link Setup Request) to the DHNB. The DHNB starts receiving (Start Rx) and sends an RNA Direct Transfer message (containing UE context id and RNSAP Radio Link Setup Response) back to the SHNB. The SHNB then starts transmitting (Start Tx) and sends an RRC Active Set Update to the UE. The UE responds with an RRC Active Set Update Complete message to the SHNB.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SHNB + participant DHNB + Note right of SHNB: Decision to setup new RL + UE->>SHNB: 1. RRC Measurement Report + SHNB->>DHNB: 2. RNA CONNECT (UE context id, RNSAP Radio Link Setup Request) + Note right of DHNB: Start Rx + DHNB->>SHNB: 3. RNA Direct Transfer (UE context id, RNSAP Radio Link Setup Response) + DHNB->>SHNB: 4. RNA Direct Transfer (UE context id, RNSAP Radio Link Restore Indication) + Note right of SHNB: Start Tx + SHNB->>UE: 5. RRC Active Set Update + UE->>SHNB: 6. RRC Active Set Update Complete + +``` + +Sequence diagram illustrating Soft Handover Initiation HNB to HNB. The diagram shows the interaction between a UE, SHNB, and DHNB. The process starts with the UE sending an RRC Measurement Report to the SHNB. The SHNB makes a decision to setup a new radio link (RL) and sends an RNA CONNECT message (containing UE context id and RNSAP Radio Link Setup Request) to the DHNB. The DHNB starts receiving (Start Rx) and sends an RNA Direct Transfer message (containing UE context id and RNSAP Radio Link Setup Response) back to the SHNB. The SHNB then starts transmitting (Start Tx) and sends an RRC Active Set Update to the UE. The UE responds with an RRC Active Set Update Complete message to the SHNB. + +**Figure 5.7.3-1: Soft Handover Initiation HNB to HNB.** + +1. The Serving HNB (SHNB) receives an RRC measurement report indicating that Soft handover is possible and the SHNB decides to setup a RL to the Drift HNB (DHNB). +2. The SHNB evaluates the UE's access rights against neighbour information available from the HNB Configuration Transfer function. If the UE has access rights for the DHNB, the SHNB may decide to setup a new RL and send an RNA:CONNECT message containing an RNSAP:RADIO LINK SETUP REQUEST message to the DHNB to set up a radio link at the DHNB. +3. The DHNB starts receiving from the UE and sends an RNSAP: RADIO LINK SETUP RESPONSE message. +4. When the radio link is established on the DHNB, the DHNB sends an RNSAP: RADIO LINK RESTORE INDICATION message. +5. The SHNB sends an RRC Active Set Update to the UE +6. The SHNB receives an RRC Active Set Update Complete from the UE. + +### 5.7.4 Mobility Access Control + +#### 5.7.4.1 Limitations + +The current version of the specification allows RNSAP relocation and SHO via Iurh only for the following scenarios: + +- Intra-PLMN Intra-CSG Closed access cell to Closed access cell mobility +- Intra-PLMN Intra-CSG Hybrid access cell to Hybrid access cell mobility +- Open access cell to Open access cell mobility. + +### 5.7.5 CELL\_FACH, CELL\_PCH and URA\_PCH Iurh based mobility (Intra-GW) + +Figure 5.7.5-1 below reports the message flow in case of CELL\_FACH/CELL\_PCH/URA\_PCH mobility across HNBs. + +![Sequence diagram for HNB to HNB CELL_FACH/CELL_PCH/URA_PCH mobility. The diagram shows the interaction between UE, Source HNB, HNB-GW, and Target HNB. The process starts with RRC Connection Setup (1) where Source HNB assigns a U-RNTI. Then RRC Cell/URA Update (2) is sent from UE to Source HNB. Source HNB forwards this to Target HNB. Target HNB determines the source HNB (3). If it cannot determine the source, it may query HNB-GW (3a) or terminate mobility (3b). HNB-GW responds with U-RNTI Query (3a). Source HNB establishes Iurh interface (3a). Target HNB sends RNA CONNECT (4) to Source HNB. Source HNB performs context transfer (5). Finally, Target HNB sends RRC Cell/URA Update Confirm (6) to UE with a new U-RNTI.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source HNB + participant HNB-GW + participant Target HNB + + Note left of UE: 1. RRC: Connection Setup. HNB assigns U-RNTI = GW-RNC-ID + HNB S-RNTI-prefix + locally generated bits to UE + UE->>Source HNB: 1. RRC: Connection Setup + Source HNB->>UE: 1. RRC: Connection Setup + Note right of Source HNB: 2. RRC: Cell/URA Update (U-RNTI) + Source HNB->>Target HNB: 2. RRC: Cell/URA Update (U-RNTI) + Note right of Target HNB: 3. Based on the S-RNTI prefix part of the received U-RNTI, determines the source HNB + alt 3a: If target cannot determine the source, it may optionally query HNB-GW and, if both HNBs support mobility, establish Iurh interface + Target HNB->>HNB-GW: 3a. HNBAP: U-RNTI Query + HNB-GW->>Target HNB: 3a. HNBAP: U-RNTI Query + Target HNB->>Source HNB: 3a. RNA: Iurh Setup + Source HNB->>Target HNB: 3a. RNA: Iurh Setup + alt 3b: If target cannot determine the source, it may optionally terminate mobility and re-establish RRC connection + Target HNB->>UE: 3b. RRC: Connection Setup + UE->>Target HNB: 3b. RRC: Connection Setup + Note right of Target HNB: 4. RNA CONNECT (RNSAP: Uplink Signalling Transfer Indication) + Target HNB->>Source HNB: 4. RNA CONNECT + Note right of Source HNB: 5. Context transfer + Source HNB->>Target HNB: 5. Context transfer + Note right of Target HNB: 6. RRC: Cell/URA Update Confirm + Target HNB->>UE: 6. RRC: Cell/URA Update Confirm + Note left of UE: (New U-RNTI: GW-RNC-ID + S-RNTI-prefix (Target HNB) + Locally generate bits) + +``` + +Sequence diagram for HNB to HNB CELL\_FACH/CELL\_PCH/URA\_PCH mobility. The diagram shows the interaction between UE, Source HNB, HNB-GW, and Target HNB. The process starts with RRC Connection Setup (1) where Source HNB assigns a U-RNTI. Then RRC Cell/URA Update (2) is sent from UE to Source HNB. Source HNB forwards this to Target HNB. Target HNB determines the source HNB (3). If it cannot determine the source, it may query HNB-GW (3a) or terminate mobility (3b). HNB-GW responds with U-RNTI Query (3a). Source HNB establishes Iurh interface (3a). Target HNB sends RNA CONNECT (4) to Source HNB. Source HNB performs context transfer (5). Finally, Target HNB sends RRC Cell/URA Update Confirm (6) to UE with a new U-RNTI. + +**Figure 5.7.5-1: HNB to HNB CELL\_FACH/CELL\_PCH/URA\_PCH mobility** + +- At initial RRC Connection Setup, the Source HNB assigns to the UE a U-RNTI value based on the S-RNTI-prefix previously assigned to the HNB by the HNB-GW. +- Subsequently, when the UE performs Cell or URA Reselection to the target HNB, it sends an RRC: Cell Update message (in case of CELL\_FACH or CELL\_PCH) or an RRC: URA Update message (in case of URA\_PCH) containing the U-RNTI value previously assigned by the Source HNB. +- Based on the received U-RNTI, the Target HNB detects the UE is reselecting from one of its neighbour HNBs. +If, based on the received U-RNTI, the Target HNB cannot detect from which HNB the UE is reselecting from, + - it may trigger a query towards the HNB-GW for the U-RNTI and subsequently, if both HNBs support CELL\_FACH mobility, establish an Iurh interface with the source HNB; + - alternatively, it may terminate the mobility procedure, re-establish the RRC connection for the UE and skip the subsequent steps. +- The target HNB forwards the received RRC Cell/URA update message via a RNSAP Uplink Signalling Transfer Indication message encapsulated in a RNA CONNECT message to the source HNB. +- The source HNB may now execute the SRNS Relocation/Enhanced SRNS Relocation procedure towards the target HNB to transfer the UE context or initialise the UE context in the target HNB via RNSAP Common Transport Channel Resources Initialisation procedure. +- The Target HNB sends to the UE an RRC: Cell Update Confirm message (in case of CELL\_FACH or CELL\_PCH) or an RRC: URA Update Confirm message (in case of URA\_PCH) to terminate the mobility procedure. Such message includes a new U-RNTI value, this time assigned by the Target HNB. If the SRNS relocation procedure is not used, the RRC: Cell Update Confirm message (in case of CELL\_FACH or CELL\_PCH) or the RRC: URA Update Confirm message (in case of URA\_PCH) is sent by the serving HNB. + +## 5.8 HNB Configuration Transfer + +The HNB Configuration Transfer function provides the means to inform the HNB-GW to provide HNBs with address information of neighbour HNBs in order to enable the establishment of Iurh connection. The neighbour list is maintained in the HNB via interaction with the HMS. The HNB uses the IP addresses received from the HNB-GW to connect to neighbour HNBs over Iurh. If the requested HNB supports S-RNTI prefix assignment, the HNB-GW shall, if supported, also inform the HNB of the S-RNTI prefix values of the neighbour HNBs supporting CELL\_FACH mobility along with their IP address information. If URAs are indicated at registration by the HNB, the HNB-GW may respond with the list of HNBs belonging to those URAs along with their S-RNTI prefixes and IP address information. + +The procedure for HNB Configuration Transfer is shown in Figure 5.8-1. + +![Sequence diagram for HNB Configuration Transfer showing interactions between HNB1, HNB-GW, and HNB2.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant HNB1 + participant HNB-GW + participant HNB2 + + Note right of HNB1: 0. HNB1 already operating and registered at the HNB-GW + Note right of HNB2: 1. HNB2 switches to operational mode, scans its environment. + Note right of HNB-GW: 2. HNB Registration Procedure + Note left of HNB1: 3. HNB1 Identifies HNB2 as a neighbor + Note right of HNB1: 4. HNB Configuration Transfer Request (request HNB2's Iurh signalling TNL Address) + Note left of HNB1: 5. HNB Configuration Transfer Response (reply HNB2's Iurh signalling TNL Address) + Note right of HNB1: 6. The HNB1 sets up an Iurh connection dependent on the Iurh connectivity option configured. + +``` + +The diagram illustrates the HNB Configuration Transfer procedure. It involves three main entities: HNB1, HNB-GW, and HNB2. The sequence of events is as follows: + + +- HNB1 is already operating and registered at the HNB-GW. +- HNB2 switches to operational mode and scans its environment. +- HNB2 registers at the HNB-GW (HNB Registration Procedure). +- HNB1 identifies HNB2 as a neighbor. +- HNB1 sends an HNB Configuration Transfer Request to the HNB-GW, requesting HNB2's Iurh signalling TNL Address. +- The HNB-GW responds with an HNB Configuration Transfer Response, providing HNB2's Iurh signalling TNL Address. +- HNB1 sets up an Iurh connection dependent on the Iurh connectivity option configured. + +Sequence diagram for HNB Configuration Transfer showing interactions between HNB1, HNB-GW, and HNB2. + +**Figure 5.8-1: HNB Configuration Transfer.** + +- HNB1 has already switched to operational mode, has registered at the HNB-GW and is connected to HNBs within its reach. +- HNB2 switches to operational mode. +- HNB2 registers at the HNB-GW successfully and provides its IP address for direct Iurh connectivity. +- HNB1 identifies a change in its neighbour list, from e.g. detecting HNB2 or via HMS. +- HNB1 requests the IP addresses of the Target HNB(s) by sending HNBAP HNB Configuration Transfer Request to the HNB-GW. +- The HNB-GW responds with a HNB Configuration Transfer Response message to the source HNB providing for each neighbour HNB requested + - either Iurh signalling TNL IP address information indicating the IP address to which the HNB shall setup an Iurh signalling connection and other information + - or a reason why respective information cannot be provided. +- The HNB1 sets up an Iurh connection towards HNB2. If direct Iurh connectivity is applied, HNB1 has to establish a reliable transport session before issuing the RNA:Iurh Setup procedure. + +If the HNB-GW includes a list of Iurh signalling TNL addresses in the HNBAP HNB: CONFIGURATION TRANSFER RESPONSE message, the HNB establishes Iurh connection using the addresses provided in an ordered manner starting with the first entry of the list. + +## 5.9 Iurh Setup + +### 5.9.1 General + +The purpose of this procedure is to setup an Iurh connection between two HNBs or between a HNB and a HNB-GW for HNB-RNC connectivity, and ensure that they have the necessary information for operation. + +### 5.9.2 Iurh Setup for direct Iurh connectivity between HNBs + +![Sequence diagram for direct Iurh connectivity between HNB1 and HNB2 via HNB-GW.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant HNB1 + participant HNB2 + participant HNB-GW + Note over HNB1, HNB2: 1. Establish reliable transport session (SCTP) + HNB1->>HNB2: 2. RNA Iurh Setup Request + HNB2->>HNB-GW: 3a. HNBAP Configuration Transfer Request + HNB-GW-->>HNB2: 3b. HNBAP Configuration Transfer Response + HNB2->>HNB1: 4. RNA Iurh Setup Response + +``` + +Sequence diagram for direct Iurh connectivity between HNB1 and HNB2 via HNB-GW. + +**Figure 5.9.2-1: Procedure for Iurh Setup - direct Iurh connectivity.** + +The purpose of this procedure is to establish Iurh connectivity between two HNBs and ensure that the application level information is available to the two HNBs to interoperate correctly. + +1. The HNB sets up an SCTP transport session, if required. +2. HNB1 sends an RNA:IURH SETUP REQUEST to HNB2. +- 3 If HNB2 does not have configuration information on HNB1, it triggers a request for the configuration information on HNB1 from the HNB-GW. +4. HNB2 responds to HNB1. + +### 5.9.3 Iurh Setup for Iurh connectivity between HNBs via the HNB-GW + +![Sequence diagram for Iurh connectivity between HNB1 and HNB2 via the HNB-GW.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +``` + +sequenceDiagram + participant HNB1 + participant HNB-GW + participant HNB2 + Note over HNB1, HNB-GW: 1. Established transport session ( SCTP) + Note over HNB-GW, HNB2: 1. Established transport session ( SCTP) + HNB1->>HNB-GW: 2. RNA:IURH SETUP REQUEST + HNB-GW->>HNB2: 2. RNA:IURH SETUP REQUEST + HNB2->>HNB-GW: 3a. HNBAP:CONFIGURATION TRANSFER REQUEST + HNB-GW-->>HNB2: 3b. HNBAP:CONFIGURATION TRANSFER RESPONSE + HNB2->>HNB-GW: 4. RNA:IURH SETUP RESPONSE + HNB-GW->>HNB1: 4. RNA:IURH SETUP RESPONSE + +``` + +Sequence diagram for Iurh connectivity between HNB1 and HNB2 via the HNB-GW. + +**Figure 5.9.3-1: Procedure for Iurh Setup-Iurh connectivity via the HNB-GW.** + +The purpose of this procedure is to establish Iurh connectivity between two HNBs via the HNB-GW and ensure that the application level information is available to the two HNBs to interoperate correctly. + +1. HNB1 and HNB2 have set up an SCTP transport session towards the HNB-GW at HNB Registration if they both support Iurh connectivity via the HNB-GW and where triggered by the HNB-GW to establish a transport session to it during HNB Registration. +2. HNB1 provides within the RNA:IURH SETUP REQUEST message information which enables the HNB-GW to route the message to the HNB2 and to enable the HNB2 to reply via the HNB-GW. +3. If HNB2 does not have configuration information on HNB1, it triggers a request for the configuration information on HNB1 from the HNB-GW. +4. HNB2 responds with a RNA:IURH SETUP RESPONSE to HNB2 via the HNB-GW. + +### 5.9.4 Iurh Setup between the HNB and the HNB-GW for HNB-RNC connectivity + +![Sequence diagram illustrating the Iurh Setup procedure between HNB, HNB-GW, and RNC. The diagram shows three lifelines: HNB, HNB-GW, and RNC. Step 0 shows the Iur interface established between HNB-GW and RNC. Step 1 shows HNB establishing an SCTP transport session with HNB-GW. Step 2 shows HNB sending an RNA:IURH SETUP REQUEST to HNB-GW. Step 3 shows HNB-GW sending an RNA:IURH SETUP RESPONSE to HNB.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + participant RNC + Note right of HNB-GW: 0. Iur interface established between HNB-GW and RNC + Note left of HNB: 1. At HNB Registration, the HNB establishes a transport session (SCTP) + HNB->>HNB-GW: 2. RNA:IURH SETUP REQUEST + HNB-GW-->>HNB: 3. RNA:IURH SETUP RESPONSE + +``` + +Sequence diagram illustrating the Iurh Setup procedure between HNB, HNB-GW, and RNC. The diagram shows three lifelines: HNB, HNB-GW, and RNC. Step 0 shows the Iur interface established between HNB-GW and RNC. Step 1 shows HNB establishing an SCTP transport session with HNB-GW. Step 2 shows HNB sending an RNA:IURH SETUP REQUEST to HNB-GW. Step 3 shows HNB-GW sending an RNA:IURH SETUP RESPONSE to HNB. + +**Figure 5.9.4-1: Procedure for Iurh Setup - Iurh connectivity between the HNB and the HNB-GW for HNB-RNC connectivity.** + +The purpose of this procedure is to establish Iurh connectivity between the HNB and the HNB-GW for connectivity between the HNB and the RNC and ensure that the peer RNC is available through the Iurh interface between the HNB and the HNB-GW. + +0. An Iur interface instance is established between the RNC and the HNB-GW. +1. At HNB Registration the HNB has set up an SCTP transport session towards the HNB-GW. +2. HNB sends an RNA:IURH SETUP REQUEST to the HNB-GW to establish the connectivity towards the RNC via the HNB-GW. The RNC ID included in the RNA message identifies the peer RNC. +3. HNB-GW responds with an RNA:IURH SETUP RESPONSE to HNB if the Iur interface between the HNB-GW and the peer RNC is available. + +## 5.10 Handling of Source information transfer to Target + +In order to maintain the continuity of UE support during RNSAP Relocation, information must be transferred from the Source HNB to the Target HNB. RAB related information to ensure that continuity of User Plane and RAB establishment and other non-RAB related information is transferred in the RELOCATION COMMIT message. + +### 5.10.1 RAB Related Parameters + +#### 5.10.1.1 User Plane + +During RNSAP Relocation preparation phase, information is provided to the Target HNB in order to allow forwarding of user data. For each CS RAB operated in support mode (see TS 25.415 [17] for the definition of “support mode”) IuUP protocol data is provided to establish a respective IuUP instance at the Target HNB in a way that the CN is unaware of the RNSAP Relocation. + +During the RNSAP Relocation execution phase, for each CS RAB operated in support mode, final counters of IuUP user data and control data frames are provided. + +The behaviour of all involved nodes (Source HNB, Target HNB, HNB-GW) is fully specified in subclause 5.7.2.2. + +#### 5.10.1.2 Other parameters + +During Relocation Commit the following information is transferred from the Source HNB to the Target HNB to maintain valid data volume reports. + +RAB Data Volume Information, The unsuccessful data report transferred to the target to be accumulated at the target for the final Data Volume report on RAB release. + +### 5.10.2 Non-RAB Related Parameters + +During Relocation Commit the following information is transferred from the Source HNB to the Target HNB to continue non-RAB related functionality triggered at the Source HNB: + +- Location Reporting parameters are transferred to the Target HNB to ensure continuity of Location Reporting. +- Trace Information parameters are transferred to the Target HNB to ensure continuity of Trace operations. +- The Service Area ID of the source cell is transferred to the target to enable the Target HNB to detect a change of service area and report this in the Location Reporting procedures. + +## 5.8a CS user plane multiplexing + +If the HNB-GW had signalled on the HNB REGISTER ACCEPT a mux port and if the HNB has capability to support CS user plane multiplexing, the HNB may send the multiplexed packets to the mux port at the HNB-GW. + +The HNB, for the same UE, shall not send multiplexed packets over multiple ports. i.e., once the HNB chooses to multiplex CS user plane packets for a given UE on the uplink, it shall send those multiplexed packets only to the assigned mux port on the HNB-GW. For those UEs whose CS user plane packets are not being multiplexed, the HNB shall send packets only to the port number assigned via RAB assignment request. + +When the HNB-GW receives multiplexed packet, it shall de-multiplex before sending them to the CN. + +## 5.9a Inbound Mobility to HNB + +### 5.9.1a General + +The following sub-sections describe the mechanism for handling the inbound mobility to HNB via the Iu and Iuh interfaces. This mechanism is also applicable to the handover between HNBs under the same HNB-GW. + +### 5.9.2a Connected Mode Inbound Mobility for CSG UEs to CSG HNBs or to Hybrid Cells + +The following figure and accompanying steps describe the inbound mobility procedure for CSG UEs from Rel-9 onwards when the Source RAN supplies to the Core Network a CSG id associated with the target HNB. The following is assumed: + +- UE is CSG capable from Rel-9 onwards and SIB-reading capable. +- UE is able to provide in the RRC measurement report the cell identity and the CSG-Id (if requested) of the target HNB. +- The Source RAN is able to determine the Cell Access Mode of the target HNB. + +NOTE: It is assumed that the network knows whether the target cell is a hybrid cell, e.g. by PSC range for hybrid cells. + +- The Source RAN is able to determine the necessary information of the target HNB for which mobility is possible. + +NOTE: It is assumed that the network knows the PLMN ID, LAC, RAC and RNC ID of such possible target cell, e.g. a possible implementation may be based on PSC ranges or based on location information of the macro-cell. + +- The Core network is CSG capable from Rel-9 onwards and is able to perform access control or membership verification for relocated CSG UE. +- The HNB-GW is able to route the incoming relocation to the appropriate target HNB using the target cell identity provided in RANAP RELOCATION REQUEST (i.e. Target Cell Id is unique for a HNB in a given HNB-GW). + +![Sequence diagram illustrating Connected Mode inbound mobility for CSG UEs to CSG HNB or Hybrid Cell. The diagram shows the interaction between UE, HNB, HNB GW, CN, and Source RAN.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant HNB_GW as HNB GW + participant CN + participant Source_RAN as Source RAN + + Note right of Source_RAN: 2. Source RAN decides to initiate relocation to target cell + UE->>Source_RAN: 1. RRC Measurement Report message + Source_RAN->>CN: 3. RANAP Relocation Required ( ... CSG id, Access Mode) + Note right of CN: 4. Access Control/ Membership Verification + CN->>HNB_GW: 5. RANAP Relocation Request (IMSI, ... CSG id, CSG Membership Status) + Note right of HNB_GW: 6. HNB-GW Triggered UE Registration. HNB-GW/HNB validates CSG id + Note bottom: 7. Continue with Relocation Procedures + +``` + +Sequence diagram illustrating Connected Mode inbound mobility for CSG UEs to CSG HNB or Hybrid Cell. The diagram shows the interaction between UE, HNB, HNB GW, CN, and Source RAN. + +Figure 5.9.2a-1: Connected Mode inbound mobility for CSG UEs to CSG HNB or Hybrid Cell. + +1. The UE is triggered to send an RRC Measurement Report by the rules set by the UTRAN. The Measurement Report includes the Cell Identity, CSG id (if requested) of the target HNB as in TS 25.331 [25]. If the target cell is a shared CSG/hybrid cell, the measurement report also includes the subset of the broadcast PLMN identities that pass PLMN ID check and for which the CSG whitelist of the UE includes an entry comprising the cell's CSG ID and the respective PLMN identity. +2. The Source RAN node makes a decision to relocate the UE session. +3. The source RAN triggers relocation of the UE session by sending the RANAP RELOCATION REQUIRED message to the Core Network. The target RNC-Id, CSG id, Target Cell Id and – for relocation to a hybrid cell – Cell Access Mode information along with relocation information are included by the source RAN in the RANAP RELOCATION REQUIRED message. + +4. If the target cell is a CSG HNB, the Core Network performs access control on the basis of the CSG ID associated with the target cell and the selected PLMN ID, as reported to the Core Network (TS 25.413 [9]). Otherwise (if the target is a Hybrid Cell), the Core Network performs membership verification and fills the *CSG Membership Status* IE in step 5 to reflect the UE's membership to the target cell. If the Core Network determines that this relocation is for an emergency call then it will allow inbound mobility to CSG cells even if the access control fails and, in case of access control failure, the Core Network sets the *CSG Membership Status* IE to the value "non-member" in step 5. +5. The HNB-GW receives a RANAP RELOCATION REQUEST message from the Core Network, including the CSG id, Target Cell Id and – for relocation to a hybrid cell – CSG Membership Status. For cases where the access control failed for relocation of one or more RABs with a particular ARP value (see TS 23.060 [10]) to a hybrid or to a CSG cell the *CSG Membership Status* IE shall be included and set to "non-member". +6. The steps for HNB-GW Triggered UE Registration are executed between the HNB-GW and the HNB. The HNB-GW/HNB validates the CSG id received in the RANAP RELOCATION REQUEST message. If the CSG HNB determines that this relocation is for one or more RABs with a particular ARP value (see TS 23.060 [10]) and CSG ID validation fails and/or UE is non member then it will accept only those RABs with a particular ARP value (see TS 23.060 [10]) and fail the others. +7. The remainder of the relocation procedure continues normally as documented in TS 25.413 [9], TS 23.060 [10] + +NOTE: Steps 2 to 7, as appropriate, are repeated for the second CN domain when present with the following exceptions. The relocation of the 2nd domain shall not trigger an additional registration. The 2nd RANAP Relocation Request shall be carried as RUA Direct Transfer. There is only one Context Id assigned to the UE regardless of the number of domains relocated from the source RAN. + +### 5.9.3a Connected Mode Inbound Mobility for non-CSG UEs to CSG HNBs or to Hybrid Cells + +The following figure and accompanying steps describe the inbound mobility procedure for non-CSG UEs, when the Source RAN is able to identify the target HNB. The following is assumed: + +- UE is non-CSG capable not able to read SIBs for CSG inbound mobility purposes. +- The HNB-GW is able to perform access control or membership verification for the UE +- The HNB-GW is able to route the incoming relocation to the appropriate target HNB. + +![Sequence diagram for Connected Mode inbound mobility for non-CSG UEs to CSG HNB or Hybrid Cell. The diagram shows interactions between UE, HNB, HNB GW, CN, and Source RAN. The steps are: 1. UE sends RRC Measurement Report to Source RAN; 2. Source RAN decides to initiate relocation; 3. Source RAN sends RANAP Relocation Required to CN; 4. CN sends RANAP Relocation Request (IMSI, ...) to HNB GW; 5. HNB GW performs Access Control/ Membership Verification; 6. HNB GW triggers UE Registration with HNB; 7. All entities continue with Relocation Procedures.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant HNB_GW as HNB GW + participant CN + participant Source_RAN as Source RAN + + Note left of UE: 1. RRC Measurement Report message + UE->>Source_RAN: RRC Measurement Report + Note right of Source_RAN: 2. Source RAN decides to initiate relocation to target cell + Source_RAN->>CN: 3. RANAP Relocation Required + CN->>HNB_GW: 4. RANAP Relocation Request (IMSI, ...) + Note right of HNB_GW: 5. Access Control/ Membership Verification + HNB_GW->>HNB: 6. HNB-GW Triggered UE Registration. + Note bottom: 7. Continue with Relocation Procedures + +``` + +Sequence diagram for Connected Mode inbound mobility for non-CSG UEs to CSG HNB or Hybrid Cell. The diagram shows interactions between UE, HNB, HNB GW, CN, and Source RAN. The steps are: 1. UE sends RRC Measurement Report to Source RAN; 2. Source RAN decides to initiate relocation; 3. Source RAN sends RANAP Relocation Required to CN; 4. CN sends RANAP Relocation Request (IMSI, ...) to HNB GW; 5. HNB GW performs Access Control/ Membership Verification; 6. HNB GW triggers UE Registration with HNB; 7. All entities continue with Relocation Procedures. + +**Figure 5.9.3a-1: Connected Mode inbound mobility for non-CSG UEs to CSG HNB or Hybrid Cell.** + +1. The UE is triggered to send an RRC Measurement Report by the rules set by the UTRAN as in TS 25.331[25]. +2. The Source RAN node makes a decision to relocate the UE session. +3. The source RAN triggers relocation of the UE session by sending the RANAP RELOCATION REQUIRED message to the Core Network. The target RNC-Id and Target Cell Id are included by the source RAN in the RANAP RELOCATION REQUIRED message. The source RAN shall not include target CSG ID and the Cell Access Mode in the RELOCATION REQUIRED message. +4. The Core Network shall not perform any access control or membership verification for the UE and it shall not include target CSG ID and CSG Membership Status in the RELOCATION REQUEST message. +5. The HNB-GW receives a RANAP RELOCATION REQUEST message not including the target CSG ID and the CSG Membership Status. The HNB-GW shall perform access control (in case of CSG cells) or membership verification (in case of Hybrid cells) for the UE. If the relocation is towards a hybrid cell the HNB-GW may include the CSG Membership Status in the RUA Connect message. If the HNB-GW determines that this relocation is for one or more RABs with a particular ARP value (see TS 23.060 [10]) then it will allow inbound mobility to CSG cells even if the access control fails and, in case of access control failure, the HNB-GW sets the *CSG Membership Status* IE to the value “non-member” in the RUA Connect message. +6. The steps for HNB-GW Triggered UE Registration are executed between the HNB-GW and the HNB. If the CSG HNB determines that this relocation is for one or more RABs with a particular ARP value (see TS 23.060 [10]) and the UE is non member then it will accept only those RABs with a particular ARP value (see TS 23.060 [10]) and ensure that the others are not continued in the target cell. + +7. The remainder of the relocation procedure continues normally as documented in TS 25.413 [9], TS 23.060 [10]. + +**NOTE:** Steps 2 to 7, as appropriate, are repeated for the second CN domain when present with the following exceptions. The relocation of the 2nd domain shall not trigger an additional registration. The 2nd RANAP Relocation Request shall be carried as RUA Direct Transfer. There is only one Context Id assigned to the UE regardless of the number of domains relocated from the source RAN. + +### 5.9.4a Connected Mode Inbound Mobility to open access HNBs + +The following figure and accompanying steps describe the inbound mobility procedure when the Source RAN is able to identify the target HNB. The following is assumed: + +- The HNB-GW is able to route the incoming relocation to the appropriate target HNB. + +![Sequence diagram showing Connected Mode inbound mobility to open access HNBs. The diagram includes lifelines for UE, HNB, HNB GW, CN, and Source RAN. Step 1: UE sends RRC Measurement Report to Source RAN. Step 2: Source RAN decides to initiate relocation. Step 3: Source RAN sends RANAP Relocation Required to CN. Step 4: CN sends RANAP Relocation Request (IMSI, ...) to HNB GW. Step 6: HNB-GW triggers UE Registration. Step 7: Relocation procedures continue across all entities.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant HNB_GW as HNB GW + participant CN + participant Source_RAN as Source RAN + + UE->>Source_RAN: 1. RRC Measurement Report message + Note right of Source_RAN: 2. Source RAN decides to +initiate relocation to target cell + Source_RAN->>CN: 3. RANAP Relocation Required + CN->>HNB_GW: 4. RANAP Relocation Request (IMSI, ...) + Note over HNB, HNB_GW: 6. HNB-GW Triggered UE Registration. + Note over UE, Source_RAN: 7. Continue with Relocation Procedures + +``` + +Sequence diagram showing Connected Mode inbound mobility to open access HNBs. The diagram includes lifelines for UE, HNB, HNB GW, CN, and Source RAN. Step 1: UE sends RRC Measurement Report to Source RAN. Step 2: Source RAN decides to initiate relocation. Step 3: Source RAN sends RANAP Relocation Required to CN. Step 4: CN sends RANAP Relocation Request (IMSI, ...) to HNB GW. Step 6: HNB-GW triggers UE Registration. Step 7: Relocation procedures continue across all entities. + +**Figure 5.9.4a-1: Connected Mode inbound mobility to open access HNBs.** + +1. The UE is triggered to send an RRC Measurement Report by the rules set by the UTRAN as in TS 25.331[25]. +2. The Source RAN node makes a decision to relocate the UE session. +3. The source RAN triggers relocation of the UE session by sending the RANAP RELOCATION REQUIRED message to the Core Network. The target RNC-Id and Target Cell Id are included by the source RAN in the RANAP RELOCATION REQUIRED message. The source RAN shall not include target CSG ID and the Cell Access Mode in the RELOCATION REQUIRED message. +4. The Core Network shall not perform any access control or membership verification for the UE and it shall not include target CSG ID and CSG Membership Status in the RELOCATION REQUEST message. + +5. The HNB-GW receives a RANAP RELOCATION REQUEST message not including the target CSG ID and the CSG Membership Status. +6. The steps for HNB-GW Triggered UE Registration are executed between the HNB-GW and the HNB. +7. The remainder of the relocation procedure continues normally as documented in TS 25.413 [9], TS 23.060 [10] + +NOTE: Steps 2 to 7, as appropriate, are repeated for the second CN domain when present with the following exceptions. The relocation of the 2nd domain shall not trigger an additional registration. The 2nd RANAP Relocation Request shall be carried as RUA Direct Transfer. There is only one Context Id assigned to the UE regardless of the number of domains relocated from the source RAN. + +## 5.10a CSG Subscription Expiry + +Case of CSG UEs: + +If the CN has signalled CSG membership update to the HNB: + +- If the UE is served by a CSG cell, and is no longer a member of the CSG cell, the HNB may initiate a handover to another cell. If the UE is not handed over, or handover is not initiated, the HNB should request the release of Iu connection (s) with an appropriate cause. The CN initiates Iu release after a configurable time, if the UE is not handed over or released by the CSG cell (TS 23.060 [10]). +- If the UE is served by a Hybrid cell, the HNB may use the new membership information to perform differentiated treatment for member and non-member UEs. + +Case of non-CSG UEs: + +If the HNB-GW has signalled CSG membership update to the HNB: + +- If the UE is served by a CSG cell, and is no longer a member of the CSG cell, the HNB may initiate a handover to another cell. If the UE is not handed over, or handover is not initiated, the HNB should request the release of Iu connection (s) with an appropriate cause. The HNB-GW shall initiate UE De-Registration after a configurable time, if the UE is not handed over or released by the serving HNB. +- If the UE is served by a Hybrid cell, the HNB may use the new membership information to perform differentiated treatment for member and non-member UEs. + +## 5.11 Connectivity between HNB and RNC via HNB-GW for RNSAP signalling + +### 5.11.1 General + +The following sub-sections describe the mechanism for handling Enhanced Relocation and Soft Handover between RNC and HNB via the HNB-GW. + +### 5.11.2 Enhanced Relocation between HNB and RNC via HNB-GW + +#### 5.11.2.1 Enhanced Relocation from Open Access and Hybrid HNBs to RNC + +The mobility procedure described in Figure 5.11.2.1-1 requires the HNB-GW to route the incoming Enhanced Relocation signalling from the Source HNB to the appropriate Target RNC indicated by an RNC-ID provided within the RNA:CONNECT message. + +![Sequence diagram for Enhanced Relocation from Open Access and Hybrid HNBs to RNC. The diagram shows interactions between UE, Source HNB, HNB-GW, CN, and Target RNC. Steps include RRC Measurement Report, RNSAP Enhanced Relocation Request, RNSAP Enhanced Relocation Response, RNSAP Enhanced Relocation Commit, RRC Connection Reconfiguration, RANAP Enhanced Relocation Complete Request, RANAP Enhanced Relocation Complete Response, RANAP Enhanced Relocation Complete Confirm (CS only), RANAP Iu Release Command, and RANAP Iu Release Complete.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source HNB + participant HNB-GW + participant CN + participant Target RNC + + Note left of UE: 0. Ongoing CS/PS session + UE->>Source HNB: 1. RRC Measurement Report message + Note right of Source HNB: 2. Source HNB decides to initiate relocation to target cell + Source HNB->>HNB-GW: 3. RNA Connect [RNSAP Enhanced Relocation Request] + HNB-GW->>Target RNC: 4. RNSAP Enhanced Relocation Request + Target RNC->>HNB-GW: 5. RNSAP Enhanced Relocation Response + HNB-GW->>Source HNB: 6. RNA Direct Transfer [RNSAP Enhanced Relocation Response] + Source HNB->>HNB-GW: 7. RNA Direct Transfer [RNSAP Enhanced Relocation Commit] + HNB-GW->>Target RNC: 8. RNSAP Enhanced Relocation Commit + Source HNB->>UE: 9. RRC Connection Reconfiguration Request + UE->>Source HNB: 10. RRC Connection Reconfiguration Complete + Target RNC->>CN: 11. RANAP Enhanced Relocation Complete Request + CN->>Target RNC: 12. RANAP Enhanced Relocation Complete Resp. + Target RNC->>CN: 13. RANAP Enhanced Relocation Complete Confirm (CS only) + CN->>HNB-GW: 14. RANAP Iu Release Command + HNB-GW->>Source HNB: 15. RUA Direct Transfer [RANAP Iu Release Command] + Source HNB->>HNB-GW: 16. RUA Disconnect [RANAP Iu Release Complete] + HNB-GW->>CN: 17. RANAP Iu Release Complete + +``` + +Sequence diagram for Enhanced Relocation from Open Access and Hybrid HNBs to RNC. The diagram shows interactions between UE, Source HNB, HNB-GW, CN, and Target RNC. Steps include RRC Measurement Report, RNSAP Enhanced Relocation Request, RNSAP Enhanced Relocation Response, RNSAP Enhanced Relocation Commit, RRC Connection Reconfiguration, RANAP Enhanced Relocation Complete Request, RANAP Enhanced Relocation Complete Response, RANAP Enhanced Relocation Complete Confirm (CS only), RANAP Iu Release Command, and RANAP Iu Release Complete. + +**Figure 5.11.2.1-1: Enhanced Relocation from Open Access and Hybrid HNBs to RNC.** + +0-9. The RNSAP signalling for preparing and executing the relocation between the HNB and the RNC follows the standardised Enhanced SRNS Relocation procedure as defined between two RNCs (see TS 23.060 [10]). + +10-13. After the UE has completed RRC signalling for the relocation, the RANAP: ENHANCED RELOCATION COMPLETE REQUEST message is sent from the Target RNC to the MSC/SGSN. The MSC/SGSN replies with a RANAP: ENHANCED RELOCATION COMPLETE RESPONSE message. In case of CS domain, the target RNC sends RANAP Enhanced Relocation Complete Confirm message to the MSC after completion of UP initialization. + +14-17. Subsequently the CN initiates Iu Release procedure to release the source-side Iu(h) resources. + +#### 5.11.2.2 Enhanced Relocation from RNC to Open Access HNBs for CSG UEs + +The mobility procedure described in Figure 5.11.2.2-1 requires the following: + +- The Source RNC is able to determine the target HNB and its Cell Access Mode based on UE measurements. + +NOTE: It is assumed that the source RNC has a priori knowledge whether the target cell is an open mode cell or not, e.g., via the PSC range configured for open cells in this part of the network + +- The HNB-GW is able to route the incoming Enhanced Relocation signalling from the Source RNC to the appropriate target HNB using the target cell identity provided in RNSAP: ENHANCED RELOCATION REQUEST. + +![Sequence diagram for Enhanced Relocation from RNC to Open Access HNB for CSG UEs. The diagram shows interactions between UE, Target HNB, HNB-GW, CN, and Source RNC. The process starts with an ongoing CS/PS session (0). The Source RNC sends an RRC Measurement Report message (PSC) to the UE (1). The Source RNC then decides to initiate relocation to the target cell (2). The Source RNC sends an RNSAP Enhanced Relocation Request to the CN (3). The CN sends an RNA Connect [RNSAP Enhanced Relocation Request] to the Target HNB (4). The Target HNB sends an RNA Direct Transfer [RNSAP Enhanced Relocation Response] to the CN (5). The CN sends an RNSAP Enhanced Relocation Response to the Source RNC (6). The CN sends an RNSAP Enhanced Relocation Commit to the Target HNB (7). The Target HNB sends an RNA Direct Transfer [RNSAP Enhanced Relocation Commit] to the CN (8). The Target HNB sends an RRC Connection Reconfiguration Request to the UE (9). The UE sends an RRC Connection Reconfiguration Complete to the Target HNB (10). The Target HNB sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Request] to the HNB-GW (11). The HNB-GW sends a RANAP Enhanced Relocation Complete Request to the CN (12). The CN sends a RANAP Enhanced Relocation Complete Resp. to the HNB-GW (13). The HNB-GW sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Resp.] to the Target HNB (14). The Target HNB sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Confirm] (for CS only) to the HNB-GW (15). The HNB-GW sends a RANAP Enhanced Relocation Complete Confirm (for CS only) to the CN (16). The CN sends a RANAP Iu Release Command to the Source RNC (17). The Source RNC sends a RANAP Iu Release Complete to the CN (18).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target HNB + participant HNB-GW + participant CN + participant Source RNC + + Note left of UE: 0. Ongoing CS/PS session + Note right of Source RNC: 2. Source RNC decides to initiate relocation to target cell + + Source RNC->>UE: 1. RRC Measurement Report message (PSC) + Source RNC->>CN: 3. RNSAP Enhanced Relocation Request + CN->>Target HNB: 4. RNA Connect [RNSAP Enhanced Relocation Request] + Target HNB->>CN: 5. RNA Direct Transfer [RNSAP Enhanced Relocation Response] + CN->>Source RNC: 6. RNSAP Enhanced Relocation Response + CN->>Target HNB: 7. RNSAP Enhanced Relocation Commit + Target HNB->>CN: 8. RNA Direct Transfer [RNSAP Enhanced Relocation Commit] + Target HNB->>UE: 9. RRC Connection Reconfiguration Request + UE->>Target HNB: 10. RRC Connection Reconfiguration Complete + Target HNB->>HNB-GW: 11. RUA Direct Transfer [RANAP Enhanced Relocation Complete Request] + HNB-GW->>CN: 12. RANAP Enhanced Relocation Complete Request + CN->>HNB-GW: 13. RANAP Enhanced Relocation Complete Resp. + HNB-GW->>Target HNB: 14. RUA Direct Transfer [RANAP Enhanced Relocation Complete Resp.] + Target HNB->>HNB-GW: 15. RUA Direct Transfer [RANAP Enhanced Relocation Complete Confirm] (for CS only) + HNB-GW->>CN: 16. RANAP Enhanced Relocation Complete Confirm (for CS only) + CN->>Source RNC: 17. RANAP Iu Release Command + Source RNC->>CN: 18. RANAP Iu Release Complete + +``` + +Sequence diagram for Enhanced Relocation from RNC to Open Access HNB for CSG UEs. The diagram shows interactions between UE, Target HNB, HNB-GW, CN, and Source RNC. The process starts with an ongoing CS/PS session (0). The Source RNC sends an RRC Measurement Report message (PSC) to the UE (1). The Source RNC then decides to initiate relocation to the target cell (2). The Source RNC sends an RNSAP Enhanced Relocation Request to the CN (3). The CN sends an RNA Connect [RNSAP Enhanced Relocation Request] to the Target HNB (4). The Target HNB sends an RNA Direct Transfer [RNSAP Enhanced Relocation Response] to the CN (5). The CN sends an RNSAP Enhanced Relocation Response to the Source RNC (6). The CN sends an RNSAP Enhanced Relocation Commit to the Target HNB (7). The Target HNB sends an RNA Direct Transfer [RNSAP Enhanced Relocation Commit] to the CN (8). The Target HNB sends an RRC Connection Reconfiguration Request to the UE (9). The UE sends an RRC Connection Reconfiguration Complete to the Target HNB (10). The Target HNB sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Request] to the HNB-GW (11). The HNB-GW sends a RANAP Enhanced Relocation Complete Request to the CN (12). The CN sends a RANAP Enhanced Relocation Complete Resp. to the HNB-GW (13). The HNB-GW sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Resp.] to the Target HNB (14). The Target HNB sends an RUA Direct Transfer [RANAP Enhanced Relocation Complete Confirm] (for CS only) to the HNB-GW (15). The HNB-GW sends a RANAP Enhanced Relocation Complete Confirm (for CS only) to the CN (16). The CN sends a RANAP Iu Release Command to the Source RNC (17). The Source RNC sends a RANAP Iu Release Complete to the CN (18). + +**Figure 5.11.2.2-1: Enhanced Relocation from RNC to Open Access HNB for CSG UEs.** + +0-9. The RNSAP signalling for preparing and executing the relocation between the RNC and the HNB follows the standardised Enhanced SRNS Relocation procedure as defined between two RNCs (see TS 23.060 [10]). + +10-12. After the UE has completed RRC signalling for the relocation, the RANAP: ENHANCED RELOCATION COMPLETE REQUEST message is sent from target HNB to HNB GW (via Iuh) and forwarded from HNB GW to MSC/SGSN (via Iu). + +13-14. After the reception of RANAP: ENHANCED RELOCATION COMPLETE REQUEST the MSC/SGSN replies with RANAP: ENHANCED RELOCATION COMPLETE RESPONSE. The HNB-GW forwards this message to the target HNB (via Iuh). + +15-16. In case of CS domain, the target HNB sends RANAP Enhanced Relocation Complete Confirm message to the MSC after completion of UP initialization. + +17-18. The MSC/SGSN mandates the RNC to release the former Iu resources. + +#### 5.11.2.3 Enhanced Relocation from RNC to Hybrid HNB for CSG UEs + +The mobility procedure described in Figure 5.11.2.3-1 requires the following: + +- The UE is CSG capable from Rel-9 onwards and SIB-reading capable. +- The Source RNC is able to determine the Cell Access Mode of the target HNB. + +NOTE: It is assumed that the source RNC is able to initiate and interpret respective UE measurements and may in addition have an a priori knowledge whether the target cell is a hybrid cell, e.g., via the PSC range configured for hybrid cells in this part of the network. + +- The HNB-GW is able to route the incoming Enhanced Relocation signalling from the Source RNC to the appropriate target HNB using the target cell identity provided in RNSAP: ENHANCED RELOCATION REQUEST. + +![Sequence diagram for Enhanced Relocation from RNC to Hybrid HNB for CSG UEs. Lifelines: UE, Target HNB, HNB-GW, CN, Source RNC. The diagram shows 20 steps of signaling between these entities to complete the relocation process.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target HNB + participant HNB-GW + participant CN + participant Source RNC + + Note left of UE: 0. Ongoing CS/PS session + UE->>Source RNC: 1. RRC Measurement Report message (CSG ID, CSG Membership Status, PSC) + Note right of Source RNC: 2. Source RNC decides to initiate relocation to target cell + Source RNC->>CN: 3. RNSAP Enhanced Relocation Request (CSG ID, CSG Membership Status) + CN->>HNB-GW: 4. RNA Connect [RNSAP Enhanced Relocation Request (CSG ID, CSG Membership Status)] + HNB-GW->>Target HNB: 5. RNA Direct Transfer [RNSAP Enhanced Relocation Response] + Target HNB->>Source RNC: 6. RNSAP Enhanced Relocation Response + Source RNC->>CN: 7. RNSAP Enhanced Relocation Commit + CN->>HNB-GW: 8. RNA Direct Transfer [RNSAP Enhanced Relocation Commit] + HNB-GW->>Target HNB: 9. RRC Connection Reconfiguration Request + Target HNB->>UE: 10. RRC Connection Reconfiguration Complete + Note left of Target HNB: 11. HNB temporarily accepts the UE based on the provided CSG Membership Status + Target HNB->>HNB-GW: 12. RUA Direct Transfer [RANAP Enhanced Relocation Complete Request (CSG ID, Cell Access Mode)] + HNB-GW->>CN: 13. RANAP Enhanced Relocation Complete Request (CSG ID, Cell Access Mode) + Note right of CN: 14. CN performs MV + CN->>HNB-GW: 15. RANAP Enhanced Relocation Complete Resp. (CSG Membership Status) + HNB-GW->>Target HNB: 16. RUA Direct Transfer [RANAP Enhanced Relocation Complete Resp. (CSG Membership Status)] + Target HNB->>HNB-GW: 17. RUA Direct Transfer [RANAP Enhanced Relocation Complete Confirm] (for CS only) + HNB-GW->>CN: 18. RANAP Enhanced Relocation Complete Confirm (for CS only) + CN->>Source RNC: 19. RANAP Iu Release Command + Source RNC->>CN: 20. RANAP Iu Release Complete + +``` + +Sequence diagram for Enhanced Relocation from RNC to Hybrid HNB for CSG UEs. Lifelines: UE, Target HNB, HNB-GW, CN, Source RNC. The diagram shows 20 steps of signaling between these entities to complete the relocation process. + +**Figure 5.11.2.3-1: Enhanced Relocation from RNC to Hybrid HNB for CSG UEs.** + +0-9. RNSAP Signalling for preparing and executing the relocation between the RNC and the HNB follows the currently standardised Enhanced SRNS Relocation procedure as defined between two RNCs (See TS 23.060 [10]). + +10-11. Upon successful relocation preparation and RRC signalling completion, the UE is temporarily admitted in the target hybrid cell according to the access status declared by the UE and provided by the Source RNC to the Target HNB within the *CSG Membership Status* IE included in the RNSAP: ENHANCED RELOCATION REQUEST message. The UE may be admitted as its reported CSG membership status until the outcomes of membership verification are received from CN. + +- 12-13. The RANAP: ENHANCED RELOCATION COMPLETE REQUEST message is sent from target HNB to HNB GW (via Iuh) and forwarded from HNB GW to MSC/SGSN (via Iu). The RANAP: ENHANCED RELOCATION COMPLETE REQUEST includes *CSG ID IE* and *Cell Access Mode IE* of the target cell. +- 14-16. After reception of RANAP: ENHANCED RELOCATION COMPLETE REQUEST the MSC/SGSN performs membership verification of the relocated UE according to *CSG ID IE* and *Cell Access Mode IE* received. The MSC/SGSN replies to the HNB GW with RANAP: ENHANCED RELOCATION COMPLETE RESPONSE containing the *CSG Membership Status IE*. The RANAP: ENHANCED RELOCATION COMPLETE RESPONSE message is forwarded from HNB GW to target HNB (via Iuh). The target HNB may apply the appropriate level of prioritisation to the UE according to the *CSG Membership Status IE* received. +- 17-18. In case of CS domain, the target HNB sends RANAP Enhanced Relocation Complete Confirm message to the MSC after completion of UP initialization. +- 19-20. The MSC/SGSN requests the RNC to release the source-side Iu resources. + +### 5.11.3 Soft Handover between HNB and RNC via HNB-GW + +#### 5.11.3.1 Soft Handover from HNB to RNC + +Mobility from HNB cells (hybrid or open access) to macro RNC using Soft Handover (SHO) follows the same principles as mobility between macro cells and uses an Iur interface established between HNB and macro RNC via the HNB-GW to support RNSAP signalling. + +The HNB-GW acts as a single RNC towards the macro RNC (as it does towards the CN) and therefore acts as a concentrator for HNB-RNC connectivity via the HNB-GW. + +For this case there is no involvement of the CN in the SHO operations, as there is no access control/membership verification needed for SHO to a macro RNC. + +The HNB acts as a SRNC and requests resources from the macro RNC, however this may happen only in case of HNBs deployed in a secure and operator controlled way (coordinated deployment) and, in this case, it is managed by the CAC of the DRNC. + +Figure 5.11.3.1-1 shows the sequence of messages involved. + +![Sequence diagram for Soft Handover HNB to RNC via HNB-GW](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + participant RNC + Note left of HNB: 1. Decision to setup new Radio Link + HNB->>HNB-GW: 2. RNA Connect [RNSAP Radio Link Setup Request] + HNB-GW->>RNC: 3. RNSAP Radio Link Setup Request + RNC-->>HNB-GW: 4. RNSAP Radio Link Setup Response + HNB-GW-->>HNB: 5. RNA Direct Transfer [RNSAP Radio Link Setup Response] + RNC-->>HNB-GW: 6. RNSAP Radio Link Restore Indication + HNB-GW-->>HNB: 7. RNA Direct Transfer [RNSAP Radio Link Restore Indication] +``` + +The diagram illustrates the sequence of messages for a soft handover from an HNB to an RNC via an HNB-GW. It starts with the HNB making a decision to set up a new radio link. The HNB then sends an RNA Connect message (RNSAP Radio Link Setup Request) to the HNB-GW. The HNB-GW forwards this as an RNSAP Radio Link Setup Request to the RNC. The RNC responds with an RNSAP Radio Link Setup Response, which is then transferred back to the HNB via the HNB-GW using an RNA Direct Transfer message. Finally, the RNC sends an RNSAP Radio Link Restore Indication to the HNB-GW, which is transferred back to the HNB via another RNA Direct Transfer message. + +Sequence diagram for Soft Handover HNB to RNC via HNB-GW + +**Figure 5.11.3.1-1: Soft Handover HNB to RNC via HNB-GW.** + +1. HNB determines that a RL can be established to a macro RNC cell. +- 2-7. Normal RL setup procedure between HNB and RNC via the HNB-GW. + +#### 5.11.3.2 Soft Handover from RNC to Open or Hybrid Access HNB + +Mobility from macro cells to Open or Hybrid Access HNB cells using Soft Handover follows the same principles as mobility between macro cells and uses an Iur interface established between the HNB and the macro RNC via the HNB-GW to support RNSAP signalling. + +The HNB-GW acts as a single RNC towards the macro RNC (as it does towards the CN) and therefore acts as a concentrator for HNB-RNC connectivity via the HNB-GW. + +For this case of open or hybrid access HNB, there is no involvement of the CN in the SHO operations. For the case of SHO to hybrid access HNB, if supported, the Radio Link is established assuming the UE is non-member. + +The macro RNC acting as SRNC requests resources from the HNB, it is managed by the CAC of the HNB. + +Figure 5.11.3.2-1 shows the sequence of messages involved. + +![Sequence diagram for Soft Handover from RNC to Open or Hybrid Access HNB via HNB-GW. Lifelines: HNB, HNB-GW, RNC. The process starts with a decision to setup a new radio link in the RNC. The RNC sends an RNSAP Radio Link Setup Request to the HNB-GW, which then sends an RNA Connect [RNSAP Radio Link Setup Request] to the HNB. The HNB responds with an RNA Direct Transfer [RNSAP Radio Link Setup Response] to the HNB-GW, which sends an RNSAP Radio Link Setup Response to the RNC. Finally, the HNB sends an RNA Direct Transfer [RNSAP Radio Link Setup Restore Indication] to the HNB-GW, which sends an RNSAP Radio Link Setup Restore Indication to the RNC.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + participant RNC + Note right of RNC: 1. Decision to setup new Radio Link + RNC->>HNB-GW: 2. RNSAP Radio Link Setup Request + HNB-GW->>HNB: 3. RNA Connect [RNSAP Radio Link Setup Request] + HNB->>HNB-GW: 4. RNA Direct Transfer [RNSAP Radio Link Setup Response] + HNB-GW->>RNC: 5. RNSAP Radio Link Setup Response + HNB->>HNB-GW: 6. RNA Direct Transfer [RNSAP Radio Link Setup Restore Indication] + HNB-GW->>RNC: 7. RNSAP Radio Link Setup Restore Indication + +``` + +Sequence diagram for Soft Handover from RNC to Open or Hybrid Access HNB via HNB-GW. Lifelines: HNB, HNB-GW, RNC. The process starts with a decision to setup a new radio link in the RNC. The RNC sends an RNSAP Radio Link Setup Request to the HNB-GW, which then sends an RNA Connect [RNSAP Radio Link Setup Request] to the HNB. The HNB responds with an RNA Direct Transfer [RNSAP Radio Link Setup Response] to the HNB-GW, which sends an RNSAP Radio Link Setup Response to the RNC. Finally, the HNB sends an RNA Direct Transfer [RNSAP Radio Link Setup Restore Indication] to the HNB-GW, which sends an RNSAP Radio Link Setup Restore Indication to the RNC. + +**Figure 5.11.3.2-1: Soft Handover from RNC to Open or Hybrid Access HNB via HNB-GW.** + +1. RNC determines that a RL can be established to a HNB cell. +- 2-7. Normal RL setup procedure between RNC and HNB via the HNB-GW. For Hybrid cells, if supported, the Radio Link is established assuming the UE is a non-member. + +### 5.11.4 HNB to RNC CELL\_FACH, CELL\_PCH and URA\_PCH mobility + +The CELL\_FACH, CELL\_PCH and URA\_PCH mobility message flow is described in Figure 5.11.4-1 below. + +![Sequence diagram for HNB to RNC CELL_FACH/CELL_PCH and URA_PCH mobility. Lifelines: UE, Source HNB, HNB-GW, Target RNC. The process starts with an RRC Connection Setup from the Source HNB to the UE, assigning a U-RNTI. The Source HNB then sends an RRC: Cell/URA Update (U-RNTI) to the Target RNC. The Target RNC detects the source HNB-GW by the RNC-ID in the U-RNTI. The Target RNC sends an RNSAP: UPLINK SIGNALLING TRANSFER INDICATION to the HNB-GW. The HNB-GW finds the source HNB Cell and sets up Iurh if needed. The HNB-GW then sends an RNA CONNECT(RNSAP UL Signalling Transfer Indication) to the Source HNB. The Source HNB sends a Context Transfer to the Target RNC. Finally, the Source HNB sends an RRC: Cell/URA Update Confirm to the UE.](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source HNB + participant HNB-GW + participant Target RNC + Note right of Source HNB: 1. RRC: Connection Setup. HNB assigns +U-RNTI = GW-RNC-ID + HNB S-RNTI- +prefix + locally generated bits to UE + Source HNB->>UE: 1. RRC: Connection Setup... + Source HNB->>Target RNC: 2. RRC: Cell/URA Update (U-RNTI) + Note right of Target RNC: 3. RNC detects the source HNB- +GW by the RNC-ID in the U- +RNTI + Target RNC->>HNB-GW: 4. RNSAP: UPLINK SIGNALLING +TRANSFER INDICATION + Note right of HNB-GW: 5. HNB-GW finds the source +HNB Cell and sets up Iurh if +needed + HNB-GW->>Source HNB: 6. RNA CONNECT(RNSAP UL Signalling +Transfer Indication) + Source HNB->>Target RNC: 7. Context Transfer + Source HNB->>UE: 8. RRC: Cell/URA Update Confirm + +``` + +Sequence diagram for HNB to RNC CELL\_FACH/CELL\_PCH and URA\_PCH mobility. Lifelines: UE, Source HNB, HNB-GW, Target RNC. The process starts with an RRC Connection Setup from the Source HNB to the UE, assigning a U-RNTI. The Source HNB then sends an RRC: Cell/URA Update (U-RNTI) to the Target RNC. The Target RNC detects the source HNB-GW by the RNC-ID in the U-RNTI. The Target RNC sends an RNSAP: UPLINK SIGNALLING TRANSFER INDICATION to the HNB-GW. The HNB-GW finds the source HNB Cell and sets up Iurh if needed. The HNB-GW then sends an RNA CONNECT(RNSAP UL Signalling Transfer Indication) to the Source HNB. The Source HNB sends a Context Transfer to the Target RNC. Finally, the Source HNB sends an RRC: Cell/URA Update Confirm to the UE. + +**Figure 5.11.4-1: HNB to RNC CELL\_FACH/CELL\_PCH and URA\_PCH mobility** + +1. At initial RRC Connection Setup, the HNB assigns to the UE a U-RNTI value based on the S-RNTI-prefix previously assigned to the HNB by the HNB-GW. + +2. Subsequently, when the UE performs Cell or URA Reselection to the target RNC, it sends an RRC: Cell Update message (in case of CELL\_FACH or CELL\_PCH) or an RRC: URA Update message (in case of URA\_PCH) containing the U-RNTI value previously assigned by the HNB. +3. Based on the RNC-ID part of such U-RNTI, the RNC detects that the UE is reselecting from one of its neighbour HNB-GWs. + +NOTE: The RNC may determine whether or not the source HNB supports CELL\_FACH/CELL\_PCH/URA\_PCH mobility. If the source HNB does not support CELL\_FACH/CELL\_PCH/URA\_PCH mobility, the RNC may release the RRC connection. + +4. The RNC forwards the received RRC Cell/URA update message via a RNSAP Uplink Signalling Transfer Indication message to the selected HNB-GW. +5. The HNB-GW, based on the S-RNTI-prefix included in the received U-RNTI and, if applicable, on the macro cell ID received from the RNC, selects the Source HNB. +6. The HNB-GW forwards the Uplink Signalling Transfer Indication RNSAP message to the source HNB. +7. The source HNB now executes the SRNS Relocation/enhanced SRNS Relocation towards the target RNC to transfer the UE context. +8. The RNC sends to the UE an RRC: Cell Update Confirm message (in case of CELL\_FACH or CELL\_PCH) or an RRC: URA Update Confirm message (in case of URA\_PCH) to terminate the mobility procedure. If the SRNS relocation procedure is not used, the RRC: Cell Update Confirm message (in case of CELL\_FACH or CELL\_PCH) or the RRC: URA Update Confirm message (in case of URA\_PCH) is sent by the serving HNB. + +### 5.11.5 RNC to HNB CELL\_FACH, CELL\_PCH and URA\_PCH mobility + +The CELL\_FACH, CELL\_PCH and URA\_PCH mobility message flow is described in Figure 5.11.5-1 below. + +![Sequence diagram for RNC to HNB CELL_FACH/CELL_PCH and URA_PCH mobility. The diagram shows the interaction between UE, Source RNC, HNB-GW, and Target HNB. The process starts with RRC Connection Setup, followed by RRC Cell/URA Update, then a series of checks and queries between Target HNB and Source RNC/HNB-GW, and finally Context Transfer and RRC Update Confirm.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source RNC + participant HNB-GW + participant Target HNB + + Note left of UE: 1. RRC: Connection Setup. RNC assigns U-RNTI = RNC-ID + locally generated bits + UE->>Source RNC: + Source RNC->>Target HNB: 2. RRC: Cell/URA Update (U-RNTI) + Note right of Target HNB: 3. Based on U-RNTI, HNB detects the source is a neighbour RNC + Note right of Source RNC: 3a. If target cannot determine the source, it may optionally query HNB-GW and establish Iurh interface + Target HNB->>HNB-GW: 3a. HNBAP: U-RNTI Query + HNB-GW->>Source RNC: 3a. RNA: Iurh Setup + Note right of Target HNB: 3b. If target cannot determine the source, it may optionally terminate mobility and re-establish RRC connection + Source RNC->>HNB-GW: 4. RNSAP: UPLINK SIGNALLING TRANSFER INDICATION + Note right of HNB-GW: 5. HNB-GW finds the proper source RNC based on the RNC-ID included RNA Connect message + HNB-GW->>Source RNC: 6. RNSAP: UPLINK SIGNALLING TRANSFER INDICATION + Source RNC->>Target HNB: 7. Context Transfer + Source RNC->>UE: 8. RRC: Cell/URA Update Confirm + +``` + +Sequence diagram for RNC to HNB CELL\_FACH/CELL\_PCH and URA\_PCH mobility. The diagram shows the interaction between UE, Source RNC, HNB-GW, and Target HNB. The process starts with RRC Connection Setup, followed by RRC Cell/URA Update, then a series of checks and queries between Target HNB and Source RNC/HNB-GW, and finally Context Transfer and RRC Update Confirm. + +Figure 5.11.5-1: RNC to HNB CELL\_FACH/CELL\_PCH and URA\_PCH mobility + +1. At initial RRC Connection Setup, the source HNB assigns to the UE a U-RNTI based on its RNC-ID and a set of locally defined bits. + +2. Subsequently, the UE performs Cell or URA Reselection to a HNB supporting CELL\_FACH/CELL\_PCH/URA\_PCH. +3. Based on the received U-RNTI, the target HNB detects the UE is reselecting from a neighbour RNC. + - If, based on the received U-RNTI, the Target HNB cannot detect from which node the UE is coming from, + - 3a. it may establish an Iurh interface with the source RNC; + - 3b.alternatively, it may terminate the mobility procedure, re-establish the RRC connection for the UE and skip the subsequent steps. +4. The HNB forwards the received message Cell/URA update via Uplink Signalling Transfer Indication RNSAP message to the selected HNB-GW. +5. The HNB-GW finds the proper source RNC based on the RNC-ID. +6. The HNB-GW forwards the RNSAP Uplink Signalling Transfer Indication message to the source RNC. +7. The source RNC may now execute the SRNS Relocation/Enhanced SRNS Relocation towards the target HNB to transfer the UE context or initialise the UE context in the target HNB via RNSAP Common Transport Channel Resources Initialisation procedure. +8. The HNB sends to the UE an RRC: Cell Update Confirm message (in case of CELL\_FACH or CELL\_PCH) or an RRC: URA Update Confirm message (in case of URA\_PCH) to terminate the mobility procedure. If the SRNS relocation procedure is not used, the RRC: Cell Update Confirm (in case of CELL\_FACH or CELL\_PCH) or the RRC: URA Update Confirm message (in case of URA\_PCH) is sent by the serving HNB. + +## 5.12 Fixed Broadband Access network Interworking + +Case of CS sessions: + +The HNB signals the Tunnel Information to the HNB GW via the HNB Registration procedure. The Tunnel Information includes HNB IP address and the UDP port number if NAT/NAPT is detected. The HNB-GW establishes and manages the S15 session by the tunnel information and RAB information as specified in TS 23.139 [36]. + +Case of PS sessions: + +The HNB signals the Tunnel Information to the SGSN via INITIAL UE MESSAGE message, RELOCATION COMPLETE message, and ENHANCED RELOCATION COMPLETE REQUEST message. The Tunnel Information includes HNB IP address and the UDP port number if NAT/NAPT is detected. + +# 6 Requirements for O&M + +## 6.1 O&M for HNB + +### 6.1.1 Provisioning Procedure for HNB + +![Sequence diagram illustrating the Provisioning procedure for HNB. The diagram shows four steps: 1. Establish Secure tunnel (between HNB and Security Gateway), 2. Location verification, HNB GW discovery, HNB Provisioning using TR-069 (between HNB and HMS), 3. Reliable Transport setup (SCTP) (between HNB and HNB GW), and 4. HNB Registration procedure commences (between HNB and HNB GW).](f56ab8d50c10444a7043b7e30880cd0a_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant Security Gateway + participant HMS + participant HNB GW + Note left of Security Gateway: 1. Establish Secure tunnel + Note left of HMS: 2. Location verification, HNB GW discovery, HNB Provisioning using TR-069 + Note left of HNB GW: 3. Reliable Transport setup (SCTP) + Note left of HNB GW: 4. HNB Registration procedure commences + +``` + +Sequence diagram illustrating the Provisioning procedure for HNB. The diagram shows four steps: 1. Establish Secure tunnel (between HNB and Security Gateway), 2. Location verification, HNB GW discovery, HNB Provisioning using TR-069 (between HNB and HMS), 3. Reliable Transport setup (SCTP) (between HNB and HNB GW), and 4. HNB Registration procedure commences (between HNB and HNB GW). + +**Figure 6.1.1-1: Provisioning procedure for HNB.** + +1. A secure tunnel is established from the HNB to the Security gateway. + +2. Location verification shall be performed by the HMS based on information sent by the HNB (e.g. macro neighbour cell scans, global navigational satellite system type of information etc.). HMS determines the serving elements and provides the HNB-GW, HMS and Security Gateway to the HNB. The HMS also provisions configuration parameters to the HNB only after successful location verification in the HMS. + +NOTE: Steps 3 & 4 are shown only for completeness. Security Gateway and HMS are shown to highlight the general architecture. + +NOTE: In the event information required for verifying location are not available (for example, no macro neighbour cells, no GNSS, no DSL line ID etc. available), HNB-GW discovery may be based on specific operator and/or regulatory policies. + +### 6.1.2 Location Verification + +#### 6.1.2.1 General + +During location verification, the HNB reports its location information to the HMS. The HMS in turn examines the provided information and verifies the HNB's location. There are 3 possible types of information for this purpose: + +1. Macro-cell Information +2. GNSS location information +3. Broadband connection information, provided that the resulting location information is at least as accurate as location determination based on macro-cell coverage information, whether or not there is macro-cell coverage available at the location of the HNB (e.g. as determined by point 1. above). + +NOTE: Not all of this information is mandatory. In fact, the type of reported information is based on factors such as the physical environment in which the HNB is installed and/or possible variations in the HNB's HW and SW implementation. + +#### 6.1.2.2 Macro-cell Information + +##### 6.1.2.2.1 General + +The HNB is expected to have a radio environment measurement capability. This includes capturing the following type of information from the surrounding environment. + +- a) UTRAN cell information + - RF level information + - Broadcast information +- b) GSM cell information + - RF level information + - Broadcast information + +##### 6.1.2.2.2 UTRAN Cell Information + +The information in the following table is reported by the HNB to the HMS for each UTRAN cell detected. + +**Table 6.1.2.2.2-1. UTRAN Cell Information.** + +| Information | | Description / Note | Presence | 3GPP Reference | +|-----------------------|---------------|-----------------------------|-----------------|--------------------------------------------------------------------------------------------------------| +| RF information | UARFCNDL | UARFCN (DL) | M | TS 25.104 [23]
sec.5.4,
TS 32.642 [24] sec.
6.3.11 | +| | CPICHRSCP | RSCP of CPICH | M | | +| | PSC | Primary Scrambling Code | M | TS 32.642 [24] sec.
6.3.11 | +| Broadcast information | PLMN Type | « GSM-MAP » or « ANSI-41 » | M | TS 25.331 [25]
sec.10.3.1.12 | +| | MCC | Mobile Country Code | M | TS 24.008 [26],
TS 32.642 [24] sec.
6.3.10 | +| | MNC | Mobile Network Code | M | TS 24.008 [26],
TS 32.642 [24] sec.
6.3.10 | +| | LAC | Location Area Code | M | TS 24.008 [26]
sec.10.5.1.3,
TS 32.642 [24] sec.
6.3.10 | +| | RAC | Routing Area Code | M | TS 24.008 [26],
sec.10.5.1.12.3,
TS 25.413 [9],
sec.9.2.3.7,
TS 32.642 [24] sec.
6.3.10 | +| | CellID | Cell ID | M | TS 25.331 [25]
sec.10.3.2.2 | +| | CSG Cell Info | | O | Applicable to Rel.8
compliant cell only. | + +##### 6.1.2.2.3 GSM Cell Information + +The information in the following table is reported by the HNB to the HMS for each GSM cell detected. + +**Table 6.1.2.2.3-1. GSM Cell Information.** + +| Information | | Description / Note | Presence | 3GPP Reference | +|-----------------------|----------|---------------------------|-----------------|------------------------------| +| RF information | ARFCN | Channel number | M | TS 32.652 [27]
sec. 6.3.5 | +| | BCCHRSSI | RSSI of the BCCH carrier. | M | TS 32.652 [27]
sec. 6.3.5 | +| | BSIC | Base Station ID Code | M | TS 32.652 [27]
sec. 6.3.5 | +| Broadcast Information | MCC | Mobile Country Code | M | TS 32.652 [27]
sec. 6.3.5 | +| | MNC | Mobile Network Code | M | TS 32.652 [27]
sec. 6.3.5 | +| | LAC | Location Area Code | M | TS 32.652 [27]
sec. 6.3.5 | +| | RAC | Routing Area Code | M | TS 32.652 [27]
sec. 6.3.5 | +| | CellID | Cell ID | M | TS 32.652 [27]
sec. 6.3.5 | + +#### 6.1.2.3 GNSS Location Information + +This information consists of, at minimum, latitude and longitude detected by the GNSS receiver (e.g. GPS receiver), if the HNB implementation includes this functionality. + +#### 6.1.2.4 Broadband Connection Information + +This information consists of the information associated with the broadband connection (e.g. DSL) the HNB is connected with: 1) public IP address assigned to the RGW (e.g. DSL-GW/router), and 2) line identifier to which the RGW is connected with (e.g. DSL line ID) as seen on the broadband service provider. These are applicable only when this information is available to the HNB, and only when the resulting location information is at least as accurate as location determination based on macro-cell coverage information, whether or not there is macro-cell coverage available at the location of the HNB (e.g. as determined by clause 6.1.2.2 above). + +### 6.1.3 HNB-GW Discovery + +During the HNB-GW Discovery procedure, the HMS provides the HNB with 3 identities as shown in the following table. The information may be either IP address or FQDN to be resolved by DNS. + +**Table 6.1.3-1. HNB-GW Discovery Information.** + +| Parameter | Description / Note | Presence | 3GPP Reference | +|-------------------|---------------------------------|----------|----------------| +| Serving HMS ID | One or more IDs may be provided | M | | +| Serving SeGW ID | One or more IDs may be provided | M | | +| Serving HNB-GW ID | One or more IDs may be provided | M | | + +### 6.1.4 HNB Provisioning + +#### 6.1.4.1 General + +During the HNB Provisioning procedure, the HMS transfers the HNB configuration information to the HNB. This includes 3 types of parameters: + +1. CN level parameters +2. RAN level parameters +3. RF level parameters + +NOTE: The HNB may have auto-configuration capabilities, such that the HMS sends a list/range of values to the HNB, which selects (and returns to HMS) a single value, also based on the information collected measuring the radio environment. The HMS may also provide control parameters of the auto-configuration process. + +#### 6.1.4.2 CN Level Parameters + +Table 6.1.4.2-1. CN Level Parameters. + +| Parameter | Description / Note | Presence | 3GPP Reference | +|--------------------------|------------------------------------------------------------------------------------------------------------|---------------|----------------------------------------------------------------------------------------------| +| PLMN Type | "GSM-MAP" or "ANSI-41" | M | TS 25.331 [25] sec. 10.3.1.12 | +| MCC | Mobile Country Code | M | TS 24.008 [26],
TS 32.642 [24] sec. 6.3.8 | +| MNC | Mobile Network Code | M | TS 24.008 [26],
TS 32.642 [24] sec. 6.3.8 | +| LAC | Location Area Code (one or more LACs may be provided) | M
(Note 1) | TS 24.008 [26] sec. 10.5.1.3,
TS 32.642 [24] sec. 6.3.9 | +| SAC | Service Area Code | M | TS 25.413 [9] sec. 9.2.3.9,
TS 32.642 [24] sec. 6.3.9 | +| T3212 | Periodic LAU timer (CS domain) | M | TS 24.008 [26] sec. 10.5.1.12.2 | +| ATT | Attach-detach allowed (CS domain) | M | TS 24.008 [26] sec. 10.5.1.12.2 | +| RAC | Routing area code (PS domain) (one or more RACs may be provided) | M
(Note 1) | TS 24.008 [26] sec. 10.5.1.12.3,
TS 25.413 [9] sec. 9.2.3.7,
TS 32.642 [24] sec. 6.3.9 | +| NMO | Network Mode of Operation (Gs i/f) | M | TS 24.008 [26] sec. 10.5.1.12.3 | +| Equivalent PLMN ID | List of one or more equivalent PLMN ID (MCC + MNC) | O
(Note 2) | TS 24.008 [26] sec. 10.5.1.13 | +| Allowed IMSI list | For access control or membership verification purposes. | O
(Note 3) | TS 24.008 [26] sec. 10.5.1.4 | +| CSG Cell Info | CSG Capability Indication, CSG Id, in case the Cell is CSG capable | M | Applicable to Rel.8 compliant cell only. | +| HNB Location Information | Location information (Geographical coordinates, Uncertainty code) | O | TS 25.413 [9] sec. 9.2.3.11 | +| SAI for broadcast | Service Area for broadcast | M | TS 25.419 [12] sec. 9.2.11 | + +Note 1: May be a list/range of values in case the HNB has auto-configuration capabilities. + +Note 2: This information is operator-dependent based on its circumstance. + +Note 3: ACL is an optional function at HNB. This information is provided if this function is enabled in the HNB. + +#### 6.1.4.3 RAN Level Parameters + +**Table 6.1.4.3-1. RAN Level Parameters.** + +| Parameter | | Description | Presence | 3GPP Reference | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------| +| RNCID for HNB | | RNC ID used by HNB | M | TS 32.642 [24]
sec. 6.3.8 | +| Cell ID | | 28-bit "Cell ID" in SIB3 | M | TS 25.331 [25]
sec. 10.3.2.2 | +| HSPA related | HSflag | Whether HSDPA/HSUPA is used or not | O | TS 32.642 [24]
sec. 6.3.9 | +| HCS related | UseOfHCS
HCSPrio
QHCS | | M | TS 25.331 [25]
sec. 10.3.7.47 and 10.3.7.12,
TS 32.642 [24]
sec. 6.3.9 | +| Cell selection / reselection related | Quality measure
QqualMin
QqualMin-offset
QrxlevMin
QrxlevMin-offset
Sintrasearch
Sintersearch
SsearchRAT
SsearchHCS
Treselections
UETxPwrMaxRACH
QHyst1 | CPICH Ec/N0 or RSCP
if Ec/N0 is used

if RSCP is used | O (Note 1) | TS 25.331 [25]
sec. 10.3.2.3 and 10.3.2.4,
TS 32.642 [24]
sec. 6.3.9,
TS 25.304 [29] | +| Intra Freq Measurement Related | Filter coefficient
Measurement quantity for freq quality estimate
Hysteresis for event 1x
Threshold for event 1x
TimetoTrigger for event 1x
Weighting factor for event 1x
Reporting Range
Triggering Condition | Filter coefficient
CPICH Ec/No, CPICH RSCP, or pathloss
"x" in 1x includes applicable events from 1A to 1J | O (Note 1) | TS 25.331 [25]
sec. 10.3.7.38 and 10.3.7.39 | +| Inter-Freq Measurement Related | Filter coefficient
Measurement quantity for freq quality estimate
Hysteresis for event 2x
Threshold for event 2x
TimetoTrigger for event 2x
Weighting factor for event 2x | Filter coefficient
CPICH Ec/No, CPICH RSCP
"x" in 2x includes applicable events from 2A to 2F | O (Note 1) | TS 25.331 [25]
sec. 10.3.7.18 and 10.3.7.19 | +| Inter-RAT Measurement Related | Filter coefficient
BSIC verification required
Hysteresis for event 3x
Threshold for event 3x
TimetoTrigger for event 3x
Weighting factor for event 3x | Filter coefficient
"required" / "not required"
"x" in 3x includes applicable events from 3A to 3D | O (Note 1) | TS 25.331 [25]
sec. 10.3.7.29 and 10.3.7.30 | +| RRC related | N30x, N31x
T30x, T31x, T320 | RRC constants
RRC timers | O (Note 1) | TS 25.331 [25]
sec. 10.3.3.43 and 10.3.3.44 | +| Neighbour list (UTRA Intra-Freq cell info list) | RNCID
C-Id
LAC
RAC
PSC | Defined for each intra-freq cells
C-Id is either 12 or 16 bits depending on RNCID length. | O (Note 2) | TS 32.642 [24]
sec. 6.3.10,
TS 25.401 [4] sec. 6.1,
TS 25.413 [9] sec. 9.2.1.28 | +| Neighbour list (UTRA Inter-Freq cell info list) | RNCID
C-Id
LAC
RAC
UARFCN (DL)
PSC | Defined for each inter-freq cells
C-Id is either 12 or 16 bits depending on RNCID length | O (Note 2) | TS 32.642 [24]
sec. 6.3.10,
TS 25.401 [4] sec. 6.1,
TS 25.413 [9] sec. 9.2.1.28 | +| Neighbour list (GERAN cell info list) | CellID
BSIC
BandIndicator
BCCHARFCN | Defined for each inter-RAT cells (assume GSM cell only). | O (Note 2) | TS 32.652 [27]
sec. 6.3.5 | + +| | | | | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---|----------------| +| HNB Positioning related | PCAP supported
SAS indication | Indicates if PCAP is supported.
Defined if HNB positioning is supported for multiple SASs. | O | TS 25.470 [39] | +| Note 1:
Note 2: |

Marked as optional based on the operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. In case this IE is absent, default value is assumed (additional implication is that HNB has a set of default parameter values).

Marked as optional due to several implications: 1) there may be no suitable neighbour cell available based on the RF scanning procedure described earlier, 2) based on operator deployment policy (e.g. dedicated RF channel for HNB layer vs. macro layer), and 3) operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. Regarding 3) above, this may include capabilities such as the HMS to add or remove neighbour cells initially detected by the HNB during the radio environment scanning process, and the HNB to extend the received Neighbour list based on auto-configuration capabilities.

| | | | + +#### 6.1.4.4 RF Level Parameters + +**Table 6.1.4.4-1. RF Level Parameters.** + +| Parameter | Description / Note | Presence | 3GPP Reference | +|--------------|------------------------------------------------------------------------------------------------------------------------|---------------|------------------------------------------------------------------------------------| +| UARFCN (DL) | Frequency channel number (one or more UARFCNs may be provided) | O
(Note 1) | TS 25.101 [28] sec. 5.4,
TS 25.104 [23] sec. 5.4,
TS 32.642 [24] sec. 6.3.11 | +| PSC | Primary scrambling code (one or more PSCs may be provided) | O
(Note 1) | TS 32.642 [24] sec. 6.3.11 | +| MaxHNBTPower | Maximum allowed Tx power of the HNB. | O
(Note 1) | TS 25.104 [23] sec. 6.2,
TS 32.642 [24] sec. 6.3.9 | +| MaxULTxPower | The parameter defines the maximum transmission power level a UE can use on PRACH. | O
(Note 1) | TS 25.101 [28] sec. 6.2,
TS 32.642 [24] sec. 6.3.9 | +| P-CPICHPower | Transmission power of Primary CPICH (DL config). This may be either a specific value or a range (min / max) of values. | O
(Note 1) | TS 32.642 [24] sec. 6.3.11 | +| P-SCHPower | Primary SCH power offset (DL config) | O
(Note 1) | TS 32.642 [24] sec. 6.3.11 | +| S-SCHPower | Secondary SCH power offset (DL config) | O
(Note 1) | TS 32.642 [24] sec. 6.3.11 | +| BCHPower | BCH power offset (DL config) | O
(Note 1) | TS 32.642 [24] sec. 6.3.11 | +| AICHPower | AICH power offset (DL config, BCCH info) | O
(Note 1) | TS 25.331 [25] sec. 10.3.6.3,
TS 32.642 [24] sec. 6.3.11 | +| PICHPower | PICH power offset (DL config, BCCH info) | O
(Note 1) | TS 25.331 [25] sec. 10.3.6.50,
TS 32.642 [24] sec. 6.3.9 | +| PCHPower | PCH power offset (DL config, BCCH info) | O
(Note 1) | TS 32.642 [24] sec. 6.3.9 | +| FACHPower | FACH power offset (DL config, BCCH info) | O
(Note 1) | TS 32.642 [24] sec. 6.3.9 | + +Note 1: Marked as optional based on the operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. In case this IE is absent, it is assumed that the HNB will derive the suitable value based on its auto-configuration capability. In case this IE is a list/range of values, the HNB will choose a single value based on its auto-configuration capability. UARFCN UL may be automatically determined by the HNB upon UARFCN DL (basing on standard duplex configuration and country-specific spectrum allocation). + +## 6.2 O&M for HNB-GW + +No requirements have been identified. + +# --- 7 Iuh interface protocol structure + +## 7.1 General + +Figure 7.2-1 shows the Control Plane and the User Plane protocol structures over the Iuh interface. For the control plane, the HNBAP protocol provides the signalling service between the HNB and the HNB-GW required to fulfil the functions described in TS 25.469 [3]. + +RUA provides the signalling service between the HNB and the HNB-GW that is required to fulfil the functions described in TS 25.468 [2]. + +PUA provides the signalling service between the HNB and HNB-GW that is required to fulfil the functions described in TS 25.470 [39]. + +The payload protocol identifier (PPI) field in SCTP (IETF RFC 4960 [6]) is set to the value 19 assigned by IANA for use with the RUA protocol. In addition, the value 20 is assigned for the PPI for HNBAP. The value 31 is assigned for the PPI for SABP. The value 55 is assigned for the PPI for PUA. The multiplexing protocol as specified in TS 25.444 [8] provides the means to multiplex CS user plane on the uplink. + +The destination port number field in SCTP (IETF RFC 4960 [6]) is set to the value 29169 assigned by IANA for setup of the common SCTP association in HNBAP, RUA, PUA and SABP. + +For Iurh there shall be an SCTP association for each direct Iurh interface between HNBs. For operation via the HNB-GW there shall be a single SCTP association common to all Iurh interface instances. This association shall be separate from the Iuh SCTP association established between the HNB and the HNB-GW. + +The payload protocol identifier (PPI) field in IETF RFC 4960 [6] is set to the value 42 registered by IANA for the use with the RNA protocol. + +The destination port number field in IETF RFC 4960 [6] is set to the value 25471 assigned by IANA for setup of the SCTP association in RNA. + +## 7.2 Iuh + +Figure 7.2-1 shows the protocol structure for Iuh, following the structure described in TS 25.401 [4]. + +![Figure 7.2-1: Iuh-Interface Protocol Stack. This diagram shows the protocol stack for the Iuh interface, divided into Control Plane and User Plane. The Control Plane includes the Radio Network Layer (RANAP, HNBAP, SABP, PCAP) and Transport Network Layer (SCTP, IP, Data Link). The User Plane includes the Iu UP Protocol Layer and Transport Network Layer (CS: RTP/RTCP, CS: MUX, PS: GTP-U, UDP/IP, Data Link). Both planes share a common Physical Layer.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The diagram illustrates the Iuh-Interface Protocol Stack, organized into two main vertical sections: Control Plane and User Plane. + +- Control Plane:** + - Radio Network Layer:** Contains RANAP, HNBAP, SABP, and PCAP. Below this is a sub-layer containing RUA and PUA. + - Transport Network Layer:** Labeled as "Transport User Network Plane". It consists of SCTP, IP, and Data Link layers. +- User Plane:** + - Iu UP Protocol Layer2):** The top layer of the User Plane. + - Transport Network Layer:** Labeled as "Transport User Network Plane". It consists of three parallel paths: CS: RTP/RTCP1), CS: MUX, and PS: GTP-U, which then converge into UDP/IP and Data Link layers. +- Common Physical Layer:** At the bottom, both planes share a single Physical Layer. + +Figure 7.2-1: Iuh-Interface Protocol Stack. This diagram shows the protocol stack for the Iuh interface, divided into Control Plane and User Plane. The Control Plane includes the Radio Network Layer (RANAP, HNBAP, SABP, PCAP) and Transport Network Layer (SCTP, IP, Data Link). The User Plane includes the Iu UP Protocol Layer and Transport Network Layer (CS: RTP/RTCP, CS: MUX, PS: GTP-U, UDP/IP, Data Link). Both planes share a common Physical Layer. + +Note 1) RTCP is optional. + +Note 2) Iu UP is terminated in CN and HNB only (i.e. not in the HNB GW) + +Figure 7.2-1: Iuh-Interface Protocol Stack. + +### 7.2.1 Iupc-luh Interface Control Plane Protocol Stack + +Figure 7.2.1-1 shows the control plane protocol stack for connectivity between a HNB and a SAS via the HNB-GW. + +![Figure 7.2.1-1: Iupc-luh Interfaces Protocol Stack for connectivity between a HNB and a SAS via the HNB-GW. This diagram shows three entities: HNB, HNB-GW, and SAS. The HNB and SAS have similar protocol stacks (PCAP, PUA, SCTP, IP, Data Link, PHY). The HNB-GW acts as an intermediary, containing an 'Interworking function' and a 'Layer 2' component that connects the HNB and SAS stacks.](7e74ac663f3e644b589ed28f5fd29398_img.jpg) + +The diagram shows the control plane protocol stack for connectivity between a HNB and a SAS via the HNB-GW. It consists of three main entities: HNB, HNB-GW, and SAS. + +- HNB (Left):** Protocol stack from top to bottom: PCAP, PUA, SCTP, IP, Data Link, PHY. +- HNB-GW (Middle):** + - At the top is an "Interworking function as described in §7.Y.2". + - Below this, the stack is split into two parallel paths: one containing PUA, SCTP, IP, Data Link, PHY; the other containing SCCP, Layer 2, PHY. +- SAS (Right):** Protocol stack from top to bottom: PCAP, SCCP, Layer 2, PHY. + +Horizontal arrows indicate the flow of data between the HNB and HNB-GW, and between the HNB-GW and SAS, showing the termination and relaying of various protocol layers. + +Figure 7.2.1-1: Iupc-luh Interfaces Protocol Stack for connectivity between a HNB and a SAS via the HNB-GW. This diagram shows three entities: HNB, HNB-GW, and SAS. The HNB and SAS have similar protocol stacks (PCAP, PUA, SCTP, IP, Data Link, PHY). The HNB-GW acts as an intermediary, containing an 'Interworking function' and a 'Layer 2' component that connects the HNB and SAS stacks. + +Figure 7.2.1-1: Iupc-luh Interfaces Protocol Stack for connectivity between a HNB and a SAS via the HNB-GW. + +### 7.2.2 Interworking between the PCAP User Adaptation Layer (PUA) and the Signalling Connection Control Part (SCCP) + +#### 7.2.2.1 General + +This section describes the usage of PUA and SCCP for connectivity between a HNB and a SAS via HNB-GW. + +RNL signalling between a SAS and a HNB-GW utilises services provided by the SCCP (ITU-T Rec. Q.711 [32] / ITU-T Rec. Q.712 [33] / ITU-T Rec. Q.713 [34] / ITU-T Rec. Q.714 [35]) as defined for IuPC interface signalling transport between an RNC and a SAS (see 3GPP TS 25.450 [37]), since the HNB-GW is seen as an RNC for connection via IuPC interface to the SAS. + +The Interworking functions at the HNB-GW deal with: + +- extracting or inserting the PCAP transaction ID information on the Iuh connection or on the IuPC connection of the SAS-HNB signalling connectivity, +- IuPC mapping of PCAP transaction IDs to provide the SAS with a consistent view aligned with the HNB-GW acting as one RNC, +- Iuh mapping of PCAP transaction ID on messages from the SAS to a local PCAP transaction ID for the HNB and mapping of local PCAP transaction ID on messages from the HNB to the corresponding PCAP transaction ID for the SAS. +- Iuh mapping of PCAP transaction ID received from the SAS to direct connectionless messages to the correct HNB. +- for connection oriented signalling, performing appropriate mapping between PUA level and SCCP level using the PUA context id and the SCCP connection information. +- For connectionless signalling, ensuring uniqueness of the PCAP Transaction ID for connectionless PCAP messages mapped to the same SCCP connection. +- respective routing of PCAP messages (see 3GPP TS 25.453[38]) based on available address information. + +In general, (i) IuPC connectivity between the HNB-GW and the SAS is established by configuration, while (ii) the Iuh connectivity for support of PCAP between the HNB and the HNB-GW is performed via the HNB registration procedure. + +The following subclauses describe the interworking between PUA and SCCP at the HNB-GW. + +#### 7.2.2.2 Establishment of signalling connection over Iuh and IuPC connections between HNB and SAS via HNB-GW + +![Sequence diagram showing the establishment of signalling connection over IuPC and Iuh connections between HNB and SAS via HNB-GW. The diagram involves three entities: Source HNB, HNB-GW, and SAS. The process starts with the Source HNB sending a PUA:CONNECT message to the HNB-GW. The HNB-GW then routes the PCAP-PDU1 to the Target SAS (IuPC already configured) and maintains a mapping between the SCCP based signalling connection and the PUA based signalling connection. The SAS then performs SCCP connection establishment and replies with a PCAP PDU2. Finally, the HNB-GW sends a PUA:DIRECT TRANSFER message to the Source HNB, and a dotted line indicates that the HNB and SAS are IuPC connected for the specific signalling connection.](3bd9d303382ff0566369ed81a9226ade_img.jpg) + +``` + +sequenceDiagram + participant Source HNB + participant HNB-GW + participant SAS + + Note right of HNB-GW: 2. The HNB-GW: +(a) routes the PCAP-PDU1 to Target SAS(IuPC already configured) +(b) maintains a mapping between the SCCP based signalling connection and the PUA based signalling connection + + Note right of SAS: 3. SCCP connection establishment as described in TS 25.450[x] +subclause 4.5.1.3. The SAS processes the received PCAP PDU and replies at application level with a PCAP PDU2. + + Source HNB->>HNB-GW: 1. PUA:CONNECT (PCAP Context Id, PCAP PDU, SAS Indicator) + HNB-GW->>SAS: 2. The HNB-GW: (a) routes the PCAP-PDU1 to Target SAS(IuPC already configured) (b) maintains a mapping between the SCCP based signalling connection and the PUA based signalling connection + SAS->>HNB-GW: 3. SCCP connection establishment as described in TS 25.450[x] subclause 4.5.1.3. The SAS processes the received PCAP PDU and replies at application level with a PCAP PDU2. + HNB-GW->>Source HNB: 4. PUA:DIRECT TRANSFER (PCAP Context Id, PCAP PDU) + Note right of Source HNB: HNB and SAS IuPC connected for the specific signalling connection + +``` + +Sequence diagram showing the establishment of signalling connection over IuPC and Iuh connections between HNB and SAS via HNB-GW. The diagram involves three entities: Source HNB, HNB-GW, and SAS. The process starts with the Source HNB sending a PUA:CONNECT message to the HNB-GW. The HNB-GW then routes the PCAP-PDU1 to the Target SAS (IuPC already configured) and maintains a mapping between the SCCP based signalling connection and the PUA based signalling connection. The SAS then performs SCCP connection establishment and replies with a PCAP PDU2. Finally, the HNB-GW sends a PUA:DIRECT TRANSFER message to the Source HNB, and a dotted line indicates that the HNB and SAS are IuPC connected for the specific signalling connection. + +Figure 7.2.2.2-1: Establishment of signalling connection over IuPC and Iuh connections between HNB and SAS via HNB-GW – HNB Initiated. + +1. If the Source HNB is configured for Iupc-connectivity via the HNB-GW, and wants to send a PCAP message to the SAS for which a signalling connection over the Iuh and Iupc connections has to be established, it issues a PUA:CONNECT message containing the PUA Context Id and the PCAP PDU1. +2. The HNB-GW identifies the signalling interface to which the PCAP message shall be routed to and maintains a mapping between the PUA-based signalling connection and the SCCP-based signalling connection for the HNB-SAS end-to-end. If the SAS indicator is included in the PUA: Connect message the HNB-GW may use this to route the PCAP message to the selected SAS. +3. The HNB-GW sends PCAP PDU1 to the SAS and the SAS sends back PCAP PDU2 (see TS 25.450 [37]). +4. The HNB-GW routes the PCAP PDU2 towards the Source HNB. +5. The HNB-GW sends a PUA:Direct Transfer message, including PCAP PDU2 if any, received from the SAS to the source HNB. + +#### 7.2.2.3 Establishment of signalling connection over Iuh – Refusal from SAS + +![Sequence diagram showing the establishment of a signalling connection over Iuh between Source HNB and SAS via HNB-GW, resulting in a refusal from the SAS.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +``` + +sequenceDiagram + participant Source HNB + participant HNB-GW + participant SAS + + Note left of Source HNB: 1. PUA:CONNECT (PCAP Context Id, PCAP PDU, SAS Indicator) + Source HNB->>HNB-GW: 1. PUA:CONNECT (PCAP Context Id, PCAP PDU, SAS Indicator) + Note right of HNB-GW: 2. The HNB-GW: +(a) routes the PCAP-PDU1 to Target SAS(Iupc already configured) +(b) maintains a mapping between the SCCP based signalling connection and the PUA based signalling connection + HNB-GW->>SAS: 3. SCCP connection establishment as described in TS 25.450[xx] subclause 4.5.1.3. The SAS refuses the connection due to e.g. Limited resources. A PCAP PDU2 may be included in the SCCP-CREF message. + Note right of SAS: 3. SCCP connection establishment as described in TS 25.450[xx] subclause 4.5.1.3. The SAS refuses the connection due to e.g. Limited resources. A PCAP PDU2 may be included in the SCCP-CREF message. + Note right of HNB-GW: 4. HNB-GW maps the SCCP-CREF into a PUA:DISCONNECT based on the mapping between SCCP based signaling connection and the PUA-based signalling connection. + HNB-GW->>Source HNB: 4. PUA:DISCONNECT (PCAP Context Id, Cause, PCAP PDU) + +``` + +Sequence diagram showing the establishment of a signalling connection over Iuh between Source HNB and SAS via HNB-GW, resulting in a refusal from the SAS. + +**Figure 7.2.2.3-1: Establishment of signalling connection over Iuh and Iupc connections between HNB and SAS via HNB-GW – HNB Initiated with refusal from SAS.** + +1. If the Source HNB is configured for Iupc-connectivity via the HNB-GW, and wants to send a PCAP message to the SAS for which a signalling connection over the Iuh and Iupc connections has to be established, it issues a PUA:CONNECT message containing the PUA Context Id and the PCAP PDU1. +2. The HNB-GW identifies the signalling interface to which the PCAP message shall be routed to and maintains a mapping between the PUA-based signalling connection and the SCCP-based signalling connection for the HNB-SAS end-to-end. If the SAS indicator is included in the PUA: Connect message the HNB-GW may use this to route the PCAP message to the selected SAS. +3. The HNB-GW sends PCAP PDU1 to the SAS as received from the HNB via SCCP Connection Request and the SAS refuses the connection request (see TS 25.450 [37]). +4. The HNB-GW maps the SCCP:CREF message into a PUA:DISCONNECT. +5. The HNB-GW sends a PUA:DISCONNECT message to the source HNB, including the optional PCAP PDU2 if received from the SAS. + +#### 7.2.2.4 Transport of PCAP signalling messages via signalling connection established over lupc and luh connections + +##### 7.2.2.4.1 HNB initiated + +![Sequence diagram for HNB initiated PCAP transport](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +``` +sequenceDiagram + participant Source HNB + participant HNB-GW + participant SAS + Note right of HNB-GW: 2. HNB-GW routes the PCAP PDU to the SAS + Source HNB->>HNB-GW: 1. PUA:DIRECT TRANSFER (PCAP Context Id, PCAP PDU) + HNB-GW->>SAS: 3. SCCP encapsulated PCAP PDU +``` + +The diagram illustrates the sequence of messages for HNB initiated transport. It features three lifelines: Source HNB, HNB-GW, and SAS. The process begins with the Source HNB sending a '1. PUA:DIRECT TRANSFER (PCAP Context Id, PCAP PDU)' message to the HNB-GW. The HNB-GW then performs an internal routing step, '2. HNB-GW routes the PCAP PDU to the SAS', indicated by a note. Finally, the HNB-GW sends a '3. SCCP encapsulated PCAP PDU' message to the SAS. + +Sequence diagram for HNB initiated PCAP transport + +**Figure 7.2.2.4.1-1: Transport of PCAP messages via signalling connection over luh and lupc connections – HNB initiated.** + +If the Source HNB wants to send a PCAP message to the SAS for which a connection oriented data transfer service is already established for a location session, it issues a PUA:DIRECT TRANSFER message towards the HNB-GW which contains the PUA Context Id and the PCAP PDU. + +The HNB-GW will forward the PCAP PDU to the SAS within an SCCP message. + +##### 7.2.2.4.2 SAS initiated + +![Sequence diagram for SAS initiated PCAP transport](87b70d2e8951032d28b4412d82cf1413_img.jpg) + +``` +sequenceDiagram + participant Receiving HNB + participant HNB-GW + participant SAS + Note right of HNB-GW: 2. HNB-GW routes the PCAP PDU to the appropriate HNB. + SAS->>HNB-GW: 1. SCCP encapsulated PCAP PDU + HNB-GW->>Receiving HNB: 2. PUA:DIRECT TRANSFER (PCAP Context Id, PCAP PDU) +``` + +The diagram illustrates the sequence of messages for SAS initiated transport. It features three lifelines: Receiving HNB, HNB-GW, and SAS. The process begins with the SAS sending a '1. SCCP encapsulated PCAP PDU' message to the HNB-GW. The HNB-GW then performs an internal routing step, '2. HNB-GW routes the PCAP PDU to the appropriate HNB.', indicated by a note. Finally, the HNB-GW sends a '2. PUA:DIRECT TRANSFER (PCAP Context Id, PCAP PDU)' message to the Receiving HNB. + +Sequence diagram for SAS initiated PCAP transport + +**Figure 7.2.2.4.2-1: Transport of PCAP messages via signalling connection over lupc and luh connections – SAS initiated.** + +If the SAS wants to send a PCAP message to the Receiving HNB for which a connection oriented data transfer service is already established for a location session, it will send to the HNB-GW the PCAP PDU within an SCCP message. + +The HNB-GW will then generate a PUA:DIRECT TRANSFER message and will route the PCAP PDU to the correct HNB. + +#### 7.2.2.5 Release of signalling connection over lupc and luh Connections + +![Sequence diagram showing the release of a signalling connection over lupc and luh connections initiated by HNB.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + participant SAS + Note right of HNB-GW: 2. HNB-GW Maps the DISCONNECT to a SCCP: RLSD and passes a PCAP PDU if contained in the PDU:DISCONNECT + Note right of SAS: 3.SCCP Release as described in TS 25.450[xx] + HNB->>HNB-GW: 1. PUA:DISCONNECT (PCAP Context Id, PCAP PDU) + HNB-GW->>SAS: 2. HNB-GW Maps the DISCONNECT to a SCCP: RLSD and passes a PCAP PDU if contained in the PDU:DISCONNECT + HNB-GW->>SAS: 3.SCCP Release as described in TS 25.450[xx] +``` + +The diagram illustrates the release of a signalling connection over lupc and luh connections initiated by HNB. It shows three steps: 1. HNB sends a PUA:DISCONNECT message (PCAP Context Id, PCAP PDU) to HNB-GW. 2. HNB-GW maps the DISCONNECT to a SCCP: RLSD and passes a PCAP PDU if contained in the PDU:DISCONNECT. 3. HNB-GW sends an SCCP Release message as described in TS 25.450[xx] to SAS. + +Sequence diagram showing the release of a signalling connection over lupc and luh connections initiated by HNB. + +**Figure 7.2.2.5-1: Release of established signalling connection over lupc and luh connections – HNB initiated.** + +If an HNB wants to release a signalling connection previously established over lupc and luh connections towards a SAS, it sends a PUA:DISCONNECT message, which includes the PUA Context Id and may include a PCAP PDU. The HNB-GW maps the PUA:DISCONNECT message to an SCCP:Release message and triggers the SCCP connection release procedure defined in TS 25.450 [37] for the corresponding SCCP connection. + +#### 7.2.2.6 Transport of PCAP signalling messages via the connectionless data transfer service + +##### 7.2.2.6.1 HNB initiated + +![Sequence diagram showing connectionless data transfer over luh and lupc connections initiated by HNB.](8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + participant SAS + Note right of HNB-GW: 2. HNB-GW routes PCAP PDU directly to the selected SAS based on the SAS indicator if present. + HNB->>HNB-GW: 1. PUA:CONNECTIONLESS TRANSFER (PCAP PDU, SAS indicator) + HNB-GW->>SAS: 2. HNB-GW routes PCAP PDU directly to the selected SAS based on the SAS indicator if present. + HNB-GW->>SAS: 3. SCCP encapsulated PCAP PDU +``` + +The diagram illustrates the connectionless data transfer over luh and lupc connections initiated by HNB. It shows three steps: 1. HNB sends a PUA:CONNECTIONLESS TRANSFER message (PCAP PDU, SAS indicator) to HNB-GW. 2. HNB-GW routes the PCAP PDU directly to the selected SAS based on the SAS indicator if present. 3. HNB-GW sends an SCCP encapsulated PCAP PDU to SAS. + +Sequence diagram showing connectionless data transfer over luh and lupc connections initiated by HNB. + +**Figure 7.2.2.6.1-1: Connectionless data transfer over luh and lupc connections – HNB initiated.** + +If the HNB wants to send in a connectionless manner a PCAP PDU to the HNB-GW for the SAS, it issues a PUA:CONNECTIONLESS TRANSFER message containing the PCAP PDU. The HNB-GW then generates and routes the PCAP PDU within a connectionless SCCP message towards the SAS. If the SAS indicator is included in the PUA: Connectionless Transfer message the HNB-GW may use this to route the PCAP message to the selected SAS. + +##### 7.2.2.6.2 SAS initiated + +![Sequence diagram showing connectionless data transfer over lupc and luh connections initiated by SAS.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + participant SAS + Note right of HNB-GW: 2. HNB-GW routes the PCAP PDU based on Transaction ID within the PCAP PDU. + SAS->>HNB-GW: 1. SCCP encapsulated PCAP PDU + HNB-GW->>HNB: 2. PUA:CONNECTIONLESS TRANSFER (PCAP PDU) +``` + +The diagram illustrates a sequence of interactions between three entities: HNB, HNB-GW, and SAS. The sequence begins with the SAS sending a message labeled '1. SCCP encapsulated PCAP PDU' to the HNB-GW. The HNB-GW then performs an internal routing step, indicated by a note: '2. HNB-GW routes the PCAP PDU based on Transaction ID within the PCAP PDU.' Finally, the HNB-GW sends a message labeled '2. PUA:CONNECTIONLESS TRANSFER (PCAP PDU)' to the HNB. + +Sequence diagram showing connectionless data transfer over lupc and luh connections initiated by SAS. + +**Figure 7.2.2.6.2-1: Connectionless data transfer over lupc and luh connections – SAS initiated.** + +If the SAS sends a PCAP PDU to the HNB-GW for the Receiving HNB, the HNB-GW has to be able to route the message to the correct HNB. The HNB-GW uses the PCAP transaction ID to determine the correct destination HNB. Then the HNB-GW issues a PUA:CONNECTIONLESS TRANSFER message containing the PCAP PDU. + +## 7.3 Iurh + +Figure 7.3-1 shows the protocol structure for Iurh, following the structure described in TS 25.401 [4]. + +![Figure 7.3-1: Iurh-Interface Protocol Stack. The diagram shows the protocol stack for the Iurh interface, divided into Control Plane and User Plane. The Control Plane stack consists of RNSAP and RNA in the Radio Network Layer, SCTP and IP in the Transport Network Layer, and Data Link in the Transport Network Layer. The User Plane stack consists of Iu-cs/Iu-ps user data forwarded via Iurh and Iur user data sent via Iurh in the Radio Network Layer, CS: RTP/RTCP and PS: GTP-U in the Transport Network Layer, UDP/IP in the Transport Network Layer, and Data Link in the Transport Network Layer. The Physical Layer is at the bottom.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram illustrates the Iurh-Interface Protocol Stack, organized into two main vertical sections: Control Plane and User Plane, both situated within the Radio Network Layer. + +- Control Plane:** + - Radio Network Layer:** Contains RNSAP and RNA. + - Transport Network Layer:** Contains SCTP and IP. + - Transport Network Layer:** Contains Data Link. +- User Plane:** + - Radio Network Layer:** Contains two boxes: "Iu-cs/Iu-ps user data forwarded via Iurh 3)" and "Iur user data sent via Iurh 2)". + - Transport Network Layer:** Contains two boxes: "CS: RTP/RTCP1)" and "PS: GTP-U". + - Transport Network Layer:** Contains UDP/IP. + - Transport Network Layer:** Contains Data Link. + +Both planes share a common **Physical Layer** at the base. The Transport Network Layer is labeled as "(void)" in the center section. + +Figure 7.3-1: Iurh-Interface Protocol Stack. The diagram shows the protocol stack for the Iurh interface, divided into Control Plane and User Plane. The Control Plane stack consists of RNSAP and RNA in the Radio Network Layer, SCTP and IP in the Transport Network Layer, and Data Link in the Transport Network Layer. The User Plane stack consists of Iu-cs/Iu-ps user data forwarded via Iurh and Iur user data sent via Iurh in the Radio Network Layer, CS: RTP/RTCP and PS: GTP-U in the Transport Network Layer, UDP/IP in the Transport Network Layer, and Data Link in the Transport Network Layer. The Physical Layer is at the bottom. + +**Figure 7.3-1: Iurh-Interface Protocol Stack.** + +NOTE 1: RTCP is optional + +NOTE 2: as specified in TS 25.425 [21] and TS 25.427 [22] + +NOTE 3: as specified in TS 25.415 [17] + +### 7.3.1 Iurh-Interface Control Plane Protocol Stack + +The figures below show the control plane protocol stack for Iurh both for direct connectivity between HNBs and for connectivity between a HNB and a macro RNC via the HNB-GW. + +Figure 7.3.1-1 shows the control plane protocol stack for the direct Iurh-connectivity option between HNBs. + +NOTE: The option that Iurh signalling traffic may be routed on IP level via the HNB-GW is depicted by the optional protocol entity boxes within the routing function. + +![Figure 7.3.1-1: Iurh-Interface Protocol Stack for direct Iurh-connectivity between HNBs. The diagram shows two HNBs (HNB1 and HNB2) connected via an IP routing function. The protocol stack for each HNB consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP, RNA, SCTP, and IP layers are connected to the IP routing function. The Data Link and PHY layers are connected to each other and to the IP routing function.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Figure 7.3.1-1: Iurh-Interface Protocol Stack for direct Iurh-connectivity between HNBs. The diagram shows two HNBs (HNB1 and HNB2) connected via an IP routing function. The protocol stack for each HNB consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP, RNA, SCTP, and IP layers are connected to the IP routing function. The Data Link and PHY layers are connected to each other and to the IP routing function. + +**Figure 7.3.1-1: Iurh-Interface Protocol Stack for direct Iurh-connectivity between HNBs.** + +Figure 7.3.1-2 shows the control plane protocol stack for the Iurh connectivity between HNBs via the HNB-GW. + +![Figure 7.3.1-2: Iurh-Interface Protocol Stack for Iurh-connectivity between HNBs via the HNB-GW. The diagram shows two HNBs (HNB1 and HNB2) connected via an HNB-GW. The protocol stack for each HNB consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP layer is connected to the HNB-GW. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The HNB-GW contains two sets of protocol stacks: one for the HNB1 side and one for the HNB2 side. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The RNSAP layer is connected to the HNB-GW.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +Figure 7.3.1-2: Iurh-Interface Protocol Stack for Iurh-connectivity between HNBs via the HNB-GW. The diagram shows two HNBs (HNB1 and HNB2) connected via an HNB-GW. The protocol stack for each HNB consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP layer is connected to the HNB-GW. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The HNB-GW contains two sets of protocol stacks: one for the HNB1 side and one for the HNB2 side. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The RNSAP layer is connected to the HNB-GW. + +**Figure 7.3.1-2: Iurh-Interface Protocol Stack for Iurh-connectivity between HNBs via the HNB-GW.** + +Figure 7.3.1-3 shows the control plane protocol stack for connectivity between a HNB and a macro RNC via the HNB-GW. + +![Figure 7.3.1-3: Iurh-Iur Interfaces Protocol Stack for connectivity between a HNB and a macro RNC via the HNB-GW. The diagram shows a HNB connected to an HNB-GW, which is connected to an RNC. The HNB protocol stack consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP layer is connected to the HNB-GW. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The HNB-GW contains an interworking function and two sets of protocol stacks. The first set (HNB side) includes RNA, SCTP, IP, Data Link, and PHY layers. The second set (RNC side) includes SCCP, Layer 2, and PHY layers. The RNC protocol stack consists of RNSAP, SCCP, Layer 2, and PHY layers. The RNSAP layer is connected to the HNB-GW. The SCCP, Layer 2, and PHY layers are connected to the HNB-GW.](06291c5328a7a4335d41a48850a3a207_img.jpg) + +Figure 7.3.1-3: Iurh-Iur Interfaces Protocol Stack for connectivity between a HNB and a macro RNC via the HNB-GW. The diagram shows a HNB connected to an HNB-GW, which is connected to an RNC. The HNB protocol stack consists of RNSAP, RNA, SCTP, IP, Data Link, and PHY layers. The RNSAP layer is connected to the HNB-GW. The RNA, SCTP, IP, Data Link, and PHY layers are connected to the HNB-GW. The HNB-GW contains an interworking function and two sets of protocol stacks. The first set (HNB side) includes RNA, SCTP, IP, Data Link, and PHY layers. The second set (RNC side) includes SCCP, Layer 2, and PHY layers. The RNC protocol stack consists of RNSAP, SCCP, Layer 2, and PHY layers. The RNSAP layer is connected to the HNB-GW. The SCCP, Layer 2, and PHY layers are connected to the HNB-GW. + +**Figure 7.3.1-3: Iurh-Iur Interfaces Protocol Stack for connectivity between a HNB and a macro RNC via the HNB-GW.** + +### 7.3.2 Usage of the services provided by RNSAP User Adaptation Layer (RNA) + +#### 7.3.2.1 General + +This section describes usage of RNA for Iurh connectivity between HNBs. + +RNA supports the transport of any RNSAP signalling messages between HNBs. + +RNA provides a connection-oriented data transfer service and a connectionless data transfer service. + +A signalling connection established by means of RNA is denoted by a single Context Id, which is unique within both involved nodes (see TS 25.471 [19] for further details). + +RNA supports direct Iurh-connectivity and Iurh-connectivity via the HNB-GW. + +#### 7.3.2.2 Iurh Signalling Connection Establishment + +##### 7.3.2.2.1 Direct Iurh connectivity + +![Sequence diagram for Direct Iurh connectivity signalling connection establishment.](dd6c544ab685b25dd17f59456efcfbfc_img.jpg) + +``` +sequenceDiagram + participant Sending HNB + participant Receiving HNB + Note left of Sending HNB: RNA: CONNECT (Iurh Context Id, RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id) + Sending HNB->>Receiving HNB: RNA: CONNECT + Note right of Receiving HNB: +``` + +The diagram shows a 'Sending HNB' box on the left and a 'Receiving HNB' box on the right. A horizontal arrow points from the Sending HNB to the Receiving HNB. Above the arrow is a text box containing: 'RNA: CONNECT (Iurh Context Id, RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id)'. Both boxes have a short vertical line extending downwards to a thick horizontal bar, representing lifelines. + +Sequence diagram for Direct Iurh connectivity signalling connection establishment. + +**Figure 7.3.2.2.1-1: Signalling Connection Establishment – Direct Iurh-connectivity.** + +If the Sending HNB wants to send an RNSAP message to the Receiving HNB for which a dedicated Iurh signalling connection has to be established, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity. The Reception of the RNA:CONNECT message at the Receiving HNB completes the signalling connection establishment. + +##### 7.3.2.2.2 Iurh signalling connection establishment via the HNB-GW + +![Sequence diagram for Iurh signalling connection establishment via the HNB-GW.](6e0ac4070edc6a056713e6f0a3222db5_img.jpg) + +``` +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving HNB + Note left of Sending HNB: 1. RNA:CONNECT (Iurh Context Id, RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id) + Sending HNB->>HNB-GW: 1. RNA:CONNECT + Note right of HNB-GW: 2. HNB-GW routes the RNA:CONNECT towards the HNB indicated in the Receivers HNB RNL Id + HNB-GW->>Receiving HNB: 3. RNA: CONNECT (Iurh Context Id, RNSAP PDU, Sender's HNB RNL Id, Receivers HNB RNL Id) + Note right of Receiving HNB: 4. dedicated Iurh signalling connection established +``` + +The diagram shows three boxes: 'Sending HNB' on the left, 'HNB-GW' in the center, and 'Receiving HNB' on the right. Step 1: An arrow points from 'Sending HNB' to 'HNB-GW' with the label '1. RNA:CONNECT (Iurh Context Id, RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id)'. Step 2: A box below the 'HNB-GW' contains the text '2. HNB-GW routes the RNA:CONNECT towards the HNB indicated in the Receivers HNB RNL Id'. Step 3: An arrow points from the 'HNB-GW' to the 'Receiving HNB' with the label '3. RNA: CONNECT (Iurh Context Id, RNSAP PDU, Sender's HNB RNL Id, Receivers HNB RNL Id)'. Step 4: A box below the 'Receiving HNB' contains the text '4. dedicated Iurh signalling connection established'. All boxes have lifelines extending downwards to thick horizontal bars. + +Sequence diagram for Iurh signalling connection establishment via the HNB-GW. + +**Figure 7.3.2.2.2-1: Signalling Connection Establishment – Iurh connection via HNB-GW.** + +1. If the Sending HNB is configured for Iurh-connectivity via the HNB-GW, and wants to send an RNSAP message to the Receiving HNB for which a signalling connection has to be established, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity. +2. The HNB-GW identifies the signalling interface to which the RNA message shall be routed by Receivers HNB RNL Identity as received from the Sending HNB. +3. The HNB-GW issues an RNA:CONNECT message with identical content as received from the Sending HNB to the Receiving HNB. +4. Reception of the RNA:CONNECT message by the Receiving HNB completes the signalling connection establishment for the Receiving HNB. + +#### 7.3.2.3 Transport of RNSAP signalling messages via an established Iurh signalling connection + +##### 7.3.2.3.1 Direct Iurh connectivity + +![Sequence diagram showing direct Iurh connectivity between a Sending HNB and a Receiving HNB. The Sending HNB sends an RNA: DIRECT TRANSFER message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the Receiving HNB.](74d23510f27b21403a7be84820821863_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant Receiving HNB + Note left of Sending HNB: RNA: DIRECT TRANSFER (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + Sending HNB->>Receiving HNB: RNA: DIRECT TRANSFER + +``` + +Sequence diagram showing direct Iurh connectivity between a Sending HNB and a Receiving HNB. The Sending HNB sends an RNA: DIRECT TRANSFER message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the Receiving HNB. + +**Figure 7.3.2.3.1-1: Transport of RNSAP messages via an established Iurh signalling connection – Direct Iurh connectivity.** + +If Sending HNB, directly Iurh connected to the Receiving HNB, wants to send an RNSAP message to Receiving HNB for which a connection oriented data transfer service is already established, it issues an RNA:DIRECT TRANSFER message to the Receiving HNB which contains the Iurh Context Id, the RNSAP PDU and the Receivers HNB RNL Identity. + +##### 7.3.2.3.2 Iurh connectivity via the HNB-GW + +![Sequence diagram showing Iurh connectivity via the HNB-GW. The Sending HNB sends an RNA: DIRECT TRANSFER message to the HNB-GW. The HNB-GW routes the message based on the Receivers HNB RNL Id. Finally, the HNB-GW sends an RNA: DIRECT TRANSFER message to the Receiving HNB.](e42cc691d9c7c4d23e66b04472bb494e_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving HNB + Note left of Sending HNB: 1. RNA: DIRECT TRANSFER (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + Sending HNB->>HNB-GW: 1. RNA: DIRECT TRANSFER + Note right of HNB-GW: 2. GW routes DIRECT TRANSFER based on Receivers HNB RNL Id + Note right of HNB-GW: 3. RNA: DIRECT TRANSFER (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + HNB-GW->>Receiving HNB: 3. RNA: DIRECT TRANSFER + +``` + +Sequence diagram showing Iurh connectivity via the HNB-GW. The Sending HNB sends an RNA: DIRECT TRANSFER message to the HNB-GW. The HNB-GW routes the message based on the Receivers HNB RNL Id. Finally, the HNB-GW sends an RNA: DIRECT TRANSFER message to the Receiving HNB. + +**Figure 7.3.2.3.2-1: Transport of RNSAP messages via an established Iurh signalling connection – Iurh connectivity via the HNB-GW.** + +If the Sending HNB, Iurh connected to the Receiving HNB via the HNB-GW, wants to send an RNSAP messages via the established signalling connection, it issues an RNA:DIRECT TRANSFER message to the HNB-GW, providing the Receivers HNB RNL Identity which enables the HNB-GW to route the RNSAP message to the Receiving HNB. + +#### 7.3.2.4 Release of a Signalling Connection + +##### 7.3.2.4.1 Direct Iurh connectivity + +![Sequence diagram showing the release of a direct Iurh signalling connection. The Sending HNB sends an RNA: DISCONNECT message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the Receiving HNB.](0804537310c1bb3f615cb001e33efd1a_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant Receiving HNB + Note left of Sending HNB: RNA: DISCONNECT (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + Sending HNB->>Receiving HNB: RNA: DISCONNECT + +``` + +Sequence diagram showing the release of a direct Iurh signalling connection. The Sending HNB sends an RNA: DISCONNECT message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the Receiving HNB. + +**Figure 7.3.2.4.1-1: Release of an Iurh signalling connection – Direct Iurh connectivity.** + +If the Sending HNB, directly Iurh-connected to the Receiving HNB, wants to release an established signalling connection towards the Receiving HNB, it sends an RNA:DISCONNECT message, which includes the Iurh Context Id and the Receivers HNB RNL Identity and may include an RNSAP PDU. Reception of the DISCONNECT message by the Receiving HNB completes the release of the Iurh signalling connection. + +##### 7.3.2.4.2 Iurh connectivity via the HNB-GW + +![Sequence diagram showing the release of an Iurh signalling connection via the HNB-GW. A Sending HNB sends an RNA:DISCONNECT message to the HNB-GW, which then routes it to the Receiving HNB.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving HNB + Note left of HNB-GW: GW routes the DISCONNECT message based on the Receivers HNB RNL Id + Sending HNB->>HNB-GW: RNA:DISCONNECT (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + HNB-GW->>Receiving HNB: RNA: DISCONNECT (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + +``` + +Sequence diagram showing the release of an Iurh signalling connection via the HNB-GW. A Sending HNB sends an RNA:DISCONNECT message to the HNB-GW, which then routes it to the Receiving HNB. + +**Figure 7.3.2.4.2-1: Release of an Iurh signalling connection – Iurh connectivity via the HNB-GW.** + +If the Sending HNB, Iurh connected to the Receiving HNB via the HNB-GW, wants to release the signalling connection towards Receiving HNB, it sends an RNA:DISCONNECT message, which includes the Iurh Context Id and the Receivers HNB RNL Identity and may include an RNSAP PDU. The HNB-GW routes the DISCONNECT message based on the Receivers HNB RNL Identity. Reception of the DISCONNECT message by Receiving HNB completes the release of the signalling connection. + +#### 7.3.2.5 Transport of RNSAP signalling messages via the connectionless data transfer service + +##### 7.3.2.5.1 Direct Iurh connectivity + +![Sequence diagram showing direct Iurh connectivity for connectionless data transfer. A Sending HNB sends an RNA: CONNECTIONLESS TRANSFER message directly to the Receiving HNB.](0ea87c5f55e5857d0969bc5ca36dccba_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant Receiving HNB + Sending HNB->>Receiving HNB: RNA: CONNECTIONLESS TRANSFER (RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id) + +``` + +Sequence diagram showing direct Iurh connectivity for connectionless data transfer. A Sending HNB sends an RNA: CONNECTIONLESS TRANSFER message directly to the Receiving HNB. + +**Figure 7.3.2.5.1-1: Connectionless data transfer – Direct Iurh-connectivity.** + +If the Sending HNB wants to send an RNSAP PDU to the Receiving HNB, for which no Iurh signalling connection is necessary, it issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity. + +##### 7.3.2.5.2 Iurh connectivity via the HNB-GW + +![Sequence diagram showing connectionless data transfer via the HNB-GW. A Sending HNB sends an RNA: CONNECTIONLESS TRANSFER message to the HNB-GW, which then routes it to the Receiving HNB.](ef8f4838401ece0abd51d63b897fa388_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving HNB + Note left of HNB-GW: GW routes the CONNECTIONLESS TRANSFER message based on the Receivers HNB RNL Id + Sending HNB->>HNB-GW: RNA:CONNECTIONLESS TRANSFER (RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id) + HNB-GW->>Receiving HNB: RNA: CONNECTIONLESS TRANSFER (RNSAP PDU, Senders HNB RNL Id, Receivers HNB RNL Id) + +``` + +Sequence diagram showing connectionless data transfer via the HNB-GW. A Sending HNB sends an RNA: CONNECTIONLESS TRANSFER message to the HNB-GW, which then routes it to the Receiving HNB. + +**Figure 7.3.2.5.2-1: Connectionless data transfer – Iurh connectivity via the HNB-GW.** + +If the Sending HNB wants to send an RNSAP PDU to the Receiving HNB, for which an Iurh signalling connection is not necessary, it issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders and the Receivers HNB RNL Identities to the HNB-GW, which routes the RNA message based on the Receivers HNB RNL Identity. The Receiving HNB is able to identify the sending HNB by the Senders HNB RNL Identity. + +### 7.3.3 Interworking between the RNSAP User Adaptation Layer (RNA) and the Signalling Connection Control Part (SCCP) + +#### 7.3.3.1 General + +This section describes usage of RNA and SCCP for connectivity between a HNB and a macro RNC via HNB-GW. + +RNL signalling between an RNC and a HNB-GW utilises services provided by the SCCP (ITU-T Rec. Q.711 [32] / ITU-T Rec. Q.712 [33] / ITU-T Rec. Q.713 [34] / ITU-T Rec. Q.714 [35]) as defined for Iur interface signalling transport between two RNCs (see 3GPP TS 25.420 [31]), since the HNB-GW is seen as an RNC from RNCs being connected via the Iur interface to it. + +The Interworking functions at the HNB-GW deal with: + +- extracting or inserting respective RNL related addressing information on the Iurh connection or on the Iur connection of the RNC-HNB signalling connectivity, +- on Iurh, RNL related addressing information carried on RNA within the *Receivers HNB RNL Identity* IE and the *Senders HNB RNL Identity* IE, +- on Iur, RNL related addressing information is carried within RNSAP; +- for connection oriented signalling, performing appropriate mapping between RNA level and SCCP level; +- respective routing of RNSAP messages based on available address information. + +In general, (i) Iur connectivity between the HNB-GW and the RNC is established by configuration, while (ii) the Iurh connectivity between the HNB and the HNB-GW is performed via the Iurh setup procedure. + +The following subclauses describe the interworking between RNA and SCCP at the HNB-GW. + +#### 7.3.3.2 Establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW + +##### 7.3.3.2.1 HNB initiated + +![Sequence diagram showing the establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW, initiated by the HNB.](50f72073c616cb3d3ca3af04a0c3a221_img.jpg) + +``` + +sequenceDiagram + participant Source HNB + participant HNB-GW + participant Target RNC + + Note left of Source HNB: 1. RNA:CONNECT (Iurh Context Id, RNSAP PDU1, Senders HNB RNL Id = HNB's Global Cell Id, Receivers HNB RNL Id = Global RNC Id of Target RNC) + Source HNB->>HNB-GW: 1. RNA:CONNECT + Note right of HNB-GW: 2. The HNB-GW: (a) routes RNSAP PDU1 to Target RNC (Iur already configured). (b) maintains a mapping between the SCCP-based signalling connection and the RNA-based signalling connection + HNB-GW->>Target RNC: 2. RNSAP PDU1 + Note right of Target RNC: 3. SCCP connection establishment as described in TS 25.420 [31] subclause 4.5.1.3. The RNC processes the received RNSAP PDU1, and replies at application level with RNSAP PDU2. + Target RNC->>HNB-GW: 3. RNSAP PDU2 + Note right of HNB-GW: 4. HNB-GW routes RNSAP PDU2 to the appropriate HNB based on the mapping between the SCCP-based signalling connection and the RNA-based signalling connection. + HNB-GW->>Source HNB: 5. RNA:Direct Transfer (Iurh Context Id, RNSAP PDU2, Senders HNB RNL Id = Global RNC Id of Target RNC, Receivers HNB RNL Id = Source HNB's Global Cell Id) + Note left of Source HNB: 5. RNA:Direct Transfer + Source HNB-->>Target RNC: HNB and RNC Iurh/Iur connected for the specific signalling connection. + +``` + +Sequence diagram showing the establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW, initiated by the HNB. + +Figure 7.3.3.2.1-1: Establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW – HNB Initiated. + +1. If the Source HNB is configured for Iurh-connectivity via the HNB-GW, and wants to send an RNSAP message to the Target RNC for which signalling connection over Iurh and Iur connections has to be established, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU1, the Source HNB RNL Identity and the Target RNC RNL Identity. +2. The HNB-GW identifies the signalling interface to which the RNA message shall be routed by the Target RNC's RNL Identity as received from the Source HNB and maintains a mapping between the RNA-based signalling connection and the SCCP-based signalling connection for the HNB-RNC end-to-end. +3. The HNB-GW sends RNSAP PDU1 to the Target RNC and the Target RNC sends back RNSAP PDU2 (see TS 25.420 [31] subclause 4.5.1.3). +4. The HNB-GW routes the RNSAP PDU2 towards the Source HNB. +5. The HNB-GW sends an RNA:Direct Transfer message, including RNSAP PDU2 received from the Target RNC. + +##### 7.3.3.2.2 HNB initiated – Refusal from RNC + +![Sequence diagram showing the establishment of a signalling connection over Iurh and Iur connections between Source HNB and Target RNC via HNB-GW, initiated by the Source HNB and refused by the Target RNC.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +``` + +sequenceDiagram + participant Source HNB + participant HNB-GW + participant Target RNC + + Note over Source HNB, HNB-GW: 1. RNA:CONNECT (Iurh Context Id, RNSAP PDU1, +Senders HNB RNL Id = HNB's Global Cell Id, +Receivers HNB RNL Id = Global RNC Id of Target RNC) + Source HNB->>HNB-GW: + + Note over HNB-GW: 2. The HNB-GW: +(a) routes RNSAP PDU1 to Target RNC (Iur already configured). +(b) maintains a mapping between the SCCP-based signalling +connection and the RNA-based signalling connection + HNB-GW->>Target RNC: + + Note over Target RNC, HNB-GW: 3. SCCP connection establishment as described in TS 25.420 [31] subclause +4.5.1.3. The RNC refuses the connection due to, e.g., limited resources. A +RNSAP PDU2 may be included in the in the SCCP:CREF message + Target RNC-->>HNB-GW: + + Note over HNB-GW: 4. HNB-GW maps the SCCP:CREF into a RNA:DISCONNECT +based on the mapping between the SCCP-based signalling +connection and the RNA-based signalling connection + + Note over HNB-GW, Source HNB: 5. RNA:DISCONNECT (Iurh Context Id, Receivers HNB +RNL Id=Source HNB's Global Cell Id, RNSAP PDU2) + HNB-GW-->>Source HNB: + +``` + +Sequence diagram showing the establishment of a signalling connection over Iurh and Iur connections between Source HNB and Target RNC via HNB-GW, initiated by the Source HNB and refused by the Target RNC. + +**Figure 7.3.3.2.2-1: Establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW – HNB Initiated with refusal from RNC.** + +1. If the Source HNB is configured for Iurh-connectivity via the HNB-GW, and wants to send an RNSAP message to the Target RNC, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU1, the Source HNB RNL Identity and the Target RNC RNL Identity. +2. The HNB-GW identifies the signalling interface to which the RNA message shall be routed by the Target RNC's RNL Identity as received from the Source HNB and maintains a mapping between the RNA-based signalling connection and the SCCP-based signalling connection for the HNB-RNC end-to-end communication. +3. The HNB-GW sends RNSAP PDU1 to the Target RNC as received from the HNB via SCCP:Connection Request and the Target RNC refuses the connection request (see TS 25.420 [31] subclause 4.5.1.3). +4. The HNB-GW maps the SCCP:CREF message into an RNA:DISCONNECT. +5. The HNB-GW sends an RNA:DISCONNECT message, including the optional RNSAP PDU2 if received from the Target RNC. + +##### 7.3.3.2.3 RNC initiated + +![Sequence diagram showing the establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW – RNC Initiated. The diagram involves three main entities: Target HNB, HNB-GW, and Source RNC. The process starts with the Source RNC sending an SCCP:CR message to the HNB-GW. The HNB-GW then routes the RNSAP PDU to the Target HNB. The Target HNB responds with an RNA:CONNECT message. The HNB-GW then routes the response back to the Source RNC via an RNA:Direct Transfer message. Finally, the Source RNC sends an SCCP:CC message to the HNB-GW. A dashed line at the bottom indicates the HNB and RNC Iurh/Iur connection for the specific signalling connection.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` + +sequenceDiagram + participant Source RNC + participant HNB-GW + participant Target HNB + + Note right of Source RNC: Note: RNC routes the RNSAP PDU to the HNB-GW based on the RNC-id portion of the target cell + + Source RNC->>HNB-GW: 1. SCCP:CR (Data=RNSAP PDU1) + Note over HNB-GW: 2. The HNB-GW routes RNSAP PDU to a HNB based on the contained cell identification + HNB-GW->>Target HNB: 3. RNA:CONNECT (Iurh Context Id, RNSAP PDU1, +Sends HNB RNL Id = Global-RNC Id of Source RNC, +Receivers HNB RNL Id = Target HNB's Global Cell Id) + Note over Target HNB: 4. HNB processes RNSAP PDU1, and answers on application level (RNSAP PDU2) and signalling TNL level (RNA Direct Transfer) + Target HNB->>HNB-GW: 5. RNA:Direct Transfer (Iurh Context Id, RNSAP PDU2, +Sends HNB RNL Id=Target HNB's Global Cell Id, +Receivers HNB RNL Id = Global RNC-Id of Source RNC) + Note over HNB-GW: 6. HNB-GW routes RNSAP PDU2 to the proper RNC + HNB-GW->>Source RNC: 7. SCCP:CC (Data=RNSAP PDU2) + + Note right of Target HNB: ----- HNB and RNC Iurh/Iur connected for the specific signalling connection ----- + +``` + +Sequence diagram showing the establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW – RNC Initiated. The diagram involves three main entities: Target HNB, HNB-GW, and Source RNC. The process starts with the Source RNC sending an SCCP:CR message to the HNB-GW. The HNB-GW then routes the RNSAP PDU to the Target HNB. The Target HNB responds with an RNA:CONNECT message. The HNB-GW then routes the response back to the Source RNC via an RNA:Direct Transfer message. Finally, the Source RNC sends an SCCP:CC message to the HNB-GW. A dashed line at the bottom indicates the HNB and RNC Iurh/Iur connection for the specific signalling connection. + +**Figure 7.3.3.2.3-1: Establishment of signalling connection over Iurh and Iur connections between HNB and RNC via HNB-GW – RNC Initiated.** + +1. The HNB-GW is seen by Source RNC as a (configured) neighbour RNC. Any signalling towards a target cell with a respective RNC-Id-prefix is sent to the HNB-GW. In this case the RNC triggers the SCCP connection establishment as described in TS 25.420 [31] subclause 4.5.1.3. +2. The HNB-GW has to be able (i) to extract the Target HNB RNL Id from the (Global) Cell-Id indicated in the initiating RNSAP PDU and (ii) to maintain a mapping between the SCCP-based signalling connection and the RNA-based signalling connection for the HNB-RNC end-to-end communication. +3. The HNB-GW sends an RNA:CONNECT message towards the appropriate HNB including the Iurh Context Id generated at Step 2, RNSAP PDU1 received from the RNC and the Global Ids of RNC and HNB. +- 4-7. At the reception of the RNA:CONNECT message, the Target HNB processes RNSAP PDU1, generates the response RNSAP PDU2. The HNB replies then with an RNA:Direct Transfer message including the new RNSAP PDU2 and the RNC and HNB Ids. The HNB-GW will forward such pieces of information to the RNC (TS 25.420 [31] subclause 4.5.1.3). + +#### 7.3.3.3 Transport of RNSAP signalling messages via signalling connection established over Iurh and Iur connections + +##### 7.3.3.3.1 HNB initiated + +![Sequence diagram for HNB initiated RNSAP message transport](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +``` +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving RNC + Note right of HNB-GW: 2. HNB-GW routes RNSAP PDU to the proper RNC + Sending HNB->>HNB-GW: 1. RNA:DIRECT TRANSFER (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) + HNB-GW->>Receiving RNC: 3. SCCP encapsulated RNSAP PDU +``` + +The diagram illustrates the sequence of operations for HNB-initiated RNSAP message transport. It involves three entities: Sending HNB, HNB-GW, and Receiving RNC. The process starts with the Sending HNB sending an RNA:DIRECT TRANSFER message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the HNB-GW. The HNB-GW then routes the RNSAP PDU to the proper RNC. Finally, the HNB-GW sends an SCCP encapsulated RNSAP PDU to the Receiving RNC. + +Sequence diagram for HNB initiated RNSAP message transport + +**Figure 7.3.3.3.1-1: Transport of RNSAP messages via signalling connection over Iurh and Iur connections – HNB initiated.** + +If the Sending HNB wants to send an RNSAP message to the Receiving RNC for which a connection oriented data transfer service is already established, it issues an RNA:DIRECT TRANSFER message towards the HNB-GW which contains the Iurh Context Id, the RNSAP PDU and the Receivers HNB RNL Identity. + +The HNB-GW will forward the RNSAP PDU to the Receiving RNC within an SCCP message. + +##### 7.3.3.3.2 RNC initiated + +![Sequence diagram for RNC initiated RNSAP message transport](f14f0843f9944e61124817d06809d7ad_img.jpg) + +``` +sequenceDiagram + participant Receiving HNB + participant HNB-GW + participant Sending RNC + Note right of HNB-GW: 2. HNB-GW routes RNSAP PDU to the appropriate HNB + Sending RNC->>HNB-GW: 1. SCCP encapsulated RNSAP PDU + HNB-GW->>Receiving HNB: 3. RNA:DIRECT TRANSFER (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id) +``` + +The diagram illustrates the sequence of operations for RNC-initiated RNSAP message transport. It involves three entities: Receiving HNB, HNB-GW, and Sending RNC. The process starts with the Sending RNC sending an SCCP encapsulated RNSAP PDU to the HNB-GW. The HNB-GW then routes the RNSAP PDU to the appropriate HNB. Finally, the HNB-GW sends an RNA:DIRECT TRANSFER message (containing Iurh Context Id, RNSAP PDU, and Receivers HNB RNL Id) to the Receiving HNB. + +Sequence diagram for RNC initiated RNSAP message transport + +**Figure 7.3.3.3.1-1: Transport of RNSAP messages via signalling connection over Iurh and Iur connections – RNC initiated.** + +If the Sending RNC wants to send an RNSAP message to the Receiving RNC for which a connection oriented data transfer service is already established, it will send to the HNB-GW the RNSAP PDU within an SCCP message. + +The HNB-GW will then generate an RNA:DIRECT TRANSFER message and will route the RNSAP PDU to the correct HNB. + +#### 7.3.3.4 Release of signalling connection over Iurh and Iur Connections + +##### 7.3.3.4.1 HNB initiated + +![Sequence diagram for HNB initiated release of signalling connection. The diagram shows three steps: 1. HNB sends an RNA:DISCONNECT message to HNB-GW; 2. HNB-GW maps the message to an SCCP:RLSD and passes an RNSAP PDU; 3. SCCP connection release is performed as described in TS 25.420 [31].](38a51baf4d5b8857d162e5d9a0645269_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + participant RNC + Note right of HNB-GW: 2. HNB-GW maps the DISCONNECT message to an SCCP:RLSD and passes an RNSAP PDU if contained in the RNA:DISCONNECT + HNB->>HNB-GW: 1. RNA:DISCONNECT (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id = Global RNC-Id) + HNB-GW->>RNC: 3. SCCP connection release, as described in TS 25.420 [31] + +``` + +Sequence diagram for HNB initiated release of signalling connection. The diagram shows three steps: 1. HNB sends an RNA:DISCONNECT message to HNB-GW; 2. HNB-GW maps the message to an SCCP:RLSD and passes an RNSAP PDU; 3. SCCP connection release is performed as described in TS 25.420 [31]. + +**Figure 7.3.3.4.1-1: Release of established signalling connection over Iurh and Iur connections – HNB initiated.** + +If an HNB wants to release a signalling connection previously established over Iurh and Iur connections previously established towards an RNC, it sends an RNA:DISCONNECT message, which includes the Iurh Context Id and the Receivers HNB RNL Identity (i.e., the Global RNC Id) and may include an RNSAP PDU. The HNB-GW maps the RNA:DISCONNECT message to an SCCP:Released message and triggers the SCCP connection release procedure defined in TS 25.420 [31] subclause 4.5.1.4. + +##### 7.3.3.4.2 RNC initiated + +![Sequence diagram for RNC initiated release of signalling connection. The diagram shows three steps: 1. RNC sends an SCCP connection release message to HNB-GW; 2. HNB-GW maps the message to an RNA:DISCONNECT including the RNSAP PDU; 3. HNB-GW sends the RNA:DISCONNECT message to HNB.](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + participant RNC + Note right of HNB-GW: 2. HNB-GW maps the SCCP:RLSD message to an RNA:DISCONNECT Including the RNSAP PDU if received from the RNC + RNC->>HNB-GW: 1. SCCP connection release, as described in TS 25.420 [31] + HNB-GW->>HNB: 3. RNA:DISCONNECT (Iurh Context Id, RNSAP PDU, Receivers HNB RNL Id=HNB's Global Cell Id) + +``` + +Sequence diagram for RNC initiated release of signalling connection. The diagram shows three steps: 1. RNC sends an SCCP connection release message to HNB-GW; 2. HNB-GW maps the message to an RNA:DISCONNECT including the RNSAP PDU; 3. HNB-GW sends the RNA:DISCONNECT message to HNB. + +**Figure 7.3.3.4.2-1: Release of established signalling connection over Iurh and Iur connections – RNC initiated.** + +If an RNC wants to release a signalling connection previously established over Iurh and Iur signalling connections previously established towards an HNB, it behaves as described in TS 25.420 [31] subclause 4.5.1.4. + +The HNB-GW maps the SCCP:RLSD to an RNA:DISCONNECT message and forwards it to the HNB. This last message includes the proper Iurh Context Id, the Receivers HNB RNL Identity (i.e., the HNB Global Id) and an RNSAP PDU, if previously received from the RNC. + +#### 7.3.3.5 Transport of RNSAP signalling messages via the connectionless data transfer service + +##### 7.3.3.5.1 HNB initiated + +![Sequence diagram for HNB initiated connectionless data transfer. It shows three participants: Sending HNB, HNB-GW, and Receiving RNC. Step 1: Sending HNB sends an RNA:CONNECTIONLESS TRANSFER (RNSAP PDU) to HNB-GW. Step 2: HNB-GW routes the message based on RNC-Id. Step 3: HNB-GW sends an SCCP encapsulated RNSAP PDU to Receiving RNC.](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +``` + +sequenceDiagram + participant Sending HNB + participant HNB-GW + participant Receiving RNC + Note right of Sending HNB: 1. RNA:CONNECTIONLESS TRANSFER (RNSAP PDU), +Senders HNB RNL Id = HNB's Global Cell Id, +Receivers HNB RNL Id = Global RNC-Id) + Sending HNB->>HNB-GW: 1. RNA:CONNECTIONLESS TRANSFER (RNSAP PDU) + Note right of HNB-GW: 2. HNB-GW routes the CONNECTIONLESS TRANSFER message based on the +RNC-Id. SCCP may, according to TS 25.420 [31] use SSN/SPC/GT addressing. + HNB-GW->>Receiving RNC: 3. SCCP encapsulated RNSAP PDU + +``` + +Sequence diagram for HNB initiated connectionless data transfer. It shows three participants: Sending HNB, HNB-GW, and Receiving RNC. Step 1: Sending HNB sends an RNA:CONNECTIONLESS TRANSFER (RNSAP PDU) to HNB-GW. Step 2: HNB-GW routes the message based on RNC-Id. Step 3: HNB-GW sends an SCCP encapsulated RNSAP PDU to Receiving RNC. + +**Figure 7.3.3.5.1-1: Connectionless data transfer over Iurh and Iur connections – HNB initiated.** + +If the Sending HNB wants to send in a connectionless manner an RNSAP PDU to the HNB-GW for the Receiving RNC, it issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders and the Receivers HNB RNL Identities. + +The HNB-GW then generates and routes the RNSAP PDU within an SCCP message towards the Receiving RNC. + +##### 7.3.3.5.2 RNC initiated + +![Sequence diagram for RNC initiated connectionless data transfer. It shows three participants: Receiving HNB, HNB-GW, and Sending RNC. Step 1: Sending RNC sends an SCCP encapsulated RNSAP PDU to HNB-GW. Step 2: HNB-GW routes the message based on an identification within the RNSAP PDU. Step 3: HNB-GW sends an RNA:CONNECTIONLESS TRANSFER (RNSAP PDU) to Receiving HNB.](443ee770f0d3d98d7411497a3191e2e0_img.jpg) + +``` + +sequenceDiagram + participant Receiving HNB + participant HNB-GW + participant Sending RNC + Note right of Sending RNC: 1. SCCP encapsulated RNSAP PDU + Sending RNC->>HNB-GW: 1. SCCP encapsulated RNSAP PDU + Note right of HNB-GW: 2. HNB-GW routes the CONNECTIONLESS TRANSFER message based on an +identification within the RNSAP PDU + HNB-GW->>Receiving HNB: 3. RNA:CONNECTIONLESS TRANSFER (RNSAP PDU), +Senders HNB RNL Id = Global RNC-Id, +Receivers HNB RNL Id = HNB Global Cell Id) + +``` + +Sequence diagram for RNC initiated connectionless data transfer. It shows three participants: Receiving HNB, HNB-GW, and Sending RNC. Step 1: Sending RNC sends an SCCP encapsulated RNSAP PDU to HNB-GW. Step 2: HNB-GW routes the message based on an identification within the RNSAP PDU. Step 3: HNB-GW sends an RNA:CONNECTIONLESS TRANSFER (RNSAP PDU) to Receiving HNB. + +**Figure 7.3.3.5.2-1: Connectionless data transfer over Iurh and Iur connections – RNC initiated.** + +If the Sending RNC sends an RNSAP PDU to the HNB-GW for the Receiving HNB, the HNB-GW has to be able to extract the receiving HNB's RNL address from received RNSAP PDU. Then the HNB-GW issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders and the Receivers HNB RNL Identities to the receiving HNB. The Receiving HNB is able to identify the sending RNC by the Senders HNB RNL Identity. + +# 8 Enhanced Interference Management + +## 8.1 General + +There is a type of interference which may be considered: 1) Interference from HNB to Macro. + +Scenarios are listed in Table 8.1-1. + +**Table 8.1-1. Interference scenarios.** + +| Scenario | Aggressor | Victim | Type of interference | +|----------|-------------|----------|-----------------------------------------------| +| 1 | HNB UE (UL) | Macro NB | Interference from HNB to Macro | +| 2 | HNB (DL) | Macro UE | *applicable to co-channel deployment scenario | + +## 8.2 Mitigation of interference from HNB to Macro + +### 8.2.1 Interference from HNB UE (UL) to Macro NB + +The scenario involves:- + +1. Adaptively limiting the HNB UE's maximum UL Tx Power in connected mode possibly using HNB UE measurement and calculating the path loss between HNB UE and Macro NB. + +### 8.2.2 Interference from HNB (DL) to Macro UE + +The scenario involves:- + +1. Redirecting unauthorized UE to another carrier possibly based on uplink access attempts by unauthorised UE. +2. Adjusting HNB's DL CPICH Tx Power adaptively either temporarily or over long term possibly based on uplink access attempts by unauthorised UE. + +# --- Annex A (informative): Implementation of CN functions within the HNB-GW for support of inter-HNB intra-HNB-GW SRNS Relocation + +## A.1 Scope + +The implementation option described in this Annex will not be evolved or maintained/corrected by 3GPP in the current Release or future Releases of the 3GPP specifications. The mechanism in subclause 5.7 is the mechanism that shall be maintained, and for which evolution within 3GPP is applicable. + +## --- A.2 General + +This Section describes an implementation variant where CN functions of SRNS Relocation are implemented within the HNB-GW in order to hide intra-HNB-GW inter-HNB active mode mobility from the CN. + +From a HNB perspective the HNB-GW appears as a CN node (one node per CN domain) providing all necessary protocol functions for SRNS Relocation (Hard Handover), from a CN node perspective, the HNB-GW appears as an RNC serving the inter-HNB relocations as intra-RNC mobility. + +The following sub-sections describe the respective mechanisms. The RANAP messages are exchanged over the Iuh interface from the Source-HNB to the HNB-GW and from the HNB-GW to the Target-HNB using appropriate RUA encapsulation. + +In this implementation the Iu UP protocol is still terminated in the CN and HNB (Figure 7.2-1), but there is an Iu UP Interworking function (A.10) residing in the HNB-GW. This implementation variant supports SRNS Relocation between HNBs supporting the same RFC combinations if the HNB supports only Iu UP v1 and SRNS Relocation between all HNBs supporting Iu UP v2. + +## --- A.3 Mobility procedure + +![Sequence diagram for Inter-HNB Inter-HNB-GW SRNS Relocation. Lifelines: UE, Source HNB, HNB GW, CN, Target HNB. The process involves 14 steps: 1. Ongoing CS PS session; 2. Decision to relocate UE to target HNB; 3. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Required) from Source HNB to HNB GW; 4. Prepare RANAP message; 5. HNB GW triggered UE Registration; 6. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Command) from HNB GW to Source HNB; 7. Physical Channel Reconfiguration from Source HNB to UE; 8. UL Synchronization from UE to Target HNB; 9. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Detect) from Target HNB to HNB GW; 10. Physical Channel Reconfiguration Complete from Target HNB to Source HNB; 11. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Complete) from Target HNB to HNB GW; 12. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Iu Release Command) from HNB GW to Source HNB; 13. RUA DISCONNECT (UE Context ID, CN Domain, RANAP Iu Release Complete) from Source HNB to HNB GW; 14. HNBAP UE DEREGISTER (UE Context ID) from HNB GW to Source HNB.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source HNB + participant HNB GW + participant CN + participant Target HNB + + Note right of Source HNB: 2 Decision to relocate UE to target HNB + Source HNB->>HNB GW: 3. RUA DIRECT TRANSFER ( UE Context ID +CN Domain RANAP Relocation Required ) + Note right of HNB GW: 4. Prepare RANAP message + Note right of HNB GW: 5. HNB GW triggered UE Registration + HNB GW->>Source HNB: 6. RUA DIRECT TRANSFER( UE Context ID +CN Domain RANAP Relocation Command ) + Source HNB->>UE: 7. Physical Channel +Reconfiguration + UE->>Target HNB: 8. UL Synchronization + Target HNB->>HNB GW: 9. RUA DIRECT TRANSFER ( UE Context ID +CN Domain RANAP Relocation Detect ) + Target HNB->>Source HNB: 10. Physical Channel Reconfiguration Complete + Target HNB->>HNB GW: 11. RUA DIRECT TRANSFER ( UE Context ID +CN Domain RANAP Relocation Complete ) + HNB GW->>Source HNB: 12. RUA DIRECT TRANSFER( UE Context ID +CN Domain RANAP Iu Release Command ) + Source HNB->>HNB GW: 13. RUA DISCONNECT ( UE Context ID, CN +Domain, RANAP Iu Release Complete ) + HNB GW->>Source HNB: 14. HNBAP UE DEREGISTER ( UE Context ID ) + +``` + +Sequence diagram for Inter-HNB Inter-HNB-GW SRNS Relocation. Lifelines: UE, Source HNB, HNB GW, CN, Target HNB. The process involves 14 steps: 1. Ongoing CS PS session; 2. Decision to relocate UE to target HNB; 3. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Required) from Source HNB to HNB GW; 4. Prepare RANAP message; 5. HNB GW triggered UE Registration; 6. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Command) from HNB GW to Source HNB; 7. Physical Channel Reconfiguration from Source HNB to UE; 8. UL Synchronization from UE to Target HNB; 9. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Detect) from Target HNB to HNB GW; 10. Physical Channel Reconfiguration Complete from Target HNB to Source HNB; 11. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Relocation Complete) from Target HNB to HNB GW; 12. RUA DIRECT TRANSFER (UE Context ID, CN Domain, RANAP Iu Release Command) from HNB GW to Source HNB; 13. RUA DISCONNECT (UE Context ID, CN Domain, RANAP Iu Release Complete) from Source HNB to HNB GW; 14. HNBAP UE DEREGISTER (UE Context ID) from HNB GW to Source HNB. + +**Figure A.3-1: Inter-HNB Inter-HNB-GW SRNS Relocation – Implementation of CN functions for SRNS Relocation within the HNB-GW.** + +1. The UE has established an active CS/PS session to the CN via the source HNB and HNB-GW. +2. At some point, the source HNB makes a decision to relocate the UE session. +3. The source HNB triggers relocation of the UE session by sending the RANAP *Relocation Required* message encapsulated in the RUA *Direct Transfer* message to the HNB-GW. The target RNC-Id and target Cell-Identity information along with relocation information are included by the source HNB in the RANAP *Relocation Required* message. +4. The HNB-GW constructs the RANAP RELOCATION REQUEST using the stored RAB Parameters and parameters received from source HNB. The RANAP message also includes the HNB-GW UL TNL information for each RAB to be setup at the target HNB. +5. Steps for HNB-GW Triggered UE Registration are executed between the HNB-GW and the HNB. The IuhUPIF function handles the CS user plane establishment in the HNB-GW. The RANAP message from the target HNB includes the target HNB DL TNL information for each RAB to be setup. In case the target HNB decides to use the alternative RAB parameters and indicates the same in the RANAP RELOCATION ACKNOWLEDGE message, the HNB-GW rejects the relocation towards the target HNB and redirects original relocation request + +towards the CN node as in subclause 5.9. + +In this phase, HNB-GW may begin bi-casting DL traffic to the source and target HNB. + +6. The HNB-GW constructs the appropriate RANAP *Relocation Command* message and routes the RANAP message encapsulated in the RUA *Direct Transfer* message to the source HNB. + - 7-11. The rest of the relocation procedure continues as shown in the corresponding steps in the above figure. When the relocation is detected in HNB-GW, the HNB-GW switches the user plane from the source HNB to the target HNB. + 12. The HNB-GW upon getting an indication that the UE has been successfully relocated to the target HNB triggers the Iu release procedure towards the source HNB by sending a RUA encapsulated RANAP *Iu Release Command* message. + 13. The source HNB acknowledges the Iu release procedure to the HNB-GW by sending a RUA encapsulated RANAP *Iu Release Complete* message. +- NOTE: Steps 2 to 13, as appropriate, are repeated for the second CN domain when present with the following exception. There is only one Context Id allocated to the UE regardless of the number of signalling domains relocated. +14. The HNB-GW deregisters the UE from the source HNB. The source HNB releases the resources assigned to the UE and deletes all stored context information associated with the UE. + +## --- A.4 Iuh Control Plane Aspects + +The HNB-GW processes and forwards some of the connection-oriented RANAP messages, related to RAB Management, Data Volume Reporting, UE Tracing, Location Reporting, Security and Iu UP Initialisation. + +## --- A.5 Iuh user plane aspects + +The HNB-GW processes and forwards all the user plane packets between the HNB and the CN and performs the switching of the user plane between the source and the target HNB. + +## --- A.6 RAB management Functions + +The establishment, modification or release of a RAB is performed between the HNB and the CN as specified in TS 25.413 [9]. However, the HNB-GW stores the RAB parameters of each established RAB as signalled via respective on the RANAP messages during RAB establishment, modification and SRNS Relocation. + +## --- A.7 Data Volume Reporting + +The data volume reporting function is used to report the volume of unsuccessfully transmitted DL data of PS RABs to the CN. If the CN has initiated the data volume report then in order to continue data volume reporting after the finalisation of the SRNS Relocation, the HNB-GW includes the Data Volume Reporting Indication in the RANAP RELOCATION REQUEST message towards the target HNB. The HNB-GW accumulates data volume reports from the different HNBs involved in subsequent inter-HNB intra-HNB-GW SRNS Relocations and reports the final value to the SGSN at RAB release. + +## --- A.8 UE Tracing + +This feature allows tracing of various events related to the UE and its activities. The HNB-GW stores the Trace related RANAP parameters exchanged in the RANAP signalling messages. In order to continue UE tracing in the target HNB during and after SRNS Relocation, the HNB-GW sends the stored RANAP CN INVOKE TRACE encapsulated in the RUA DIRECT TRANSFER message towards the target HNB after step 5 (see subclause 5.11.2). + +## A.9 Location reporting function + +The positioning function performs the determination of the geographical position for an UE. The location reporting function transfers the positioning information between the UTRAN and the CN triggered by the RANAP Location Reporting Control from the CN. If the RANAP Location Reporting Control procedure is initiated with “*Request Type*” indicated as “to report upon change of Service area”, the HNB-GW sends the Location Report if there is a change in SA due to SRNS Relocation. Also, the HNB GW sends the stored RANAP LOCATION REPORTING CONTROL encapsulated in the RUA DIRECT TRANSFER message towards the target HNB after step 5 (see subclause 5.11.2) if Location Reporting Control procedure continues after relocation. + +## A.10 Security Functions + +The radio interface is ciphered/integrity protected upon request of the Core Network. The ciphering/ integrity protection is done within UTRAN at the HNB. However, the HNB-GW stores the ciphering and integrity protection related RANAP parameters exchanged in the UE dedicated RANAP signalling messages. The HNB-GW includes the stored ciphering/integrity protection information in the Relocation Request message to the target HNB. + +## A.11 Iuh Framing Protocol Interworking Function (IuhUPIF) + +### A.11.1 Introduction + +The CS user plane traffic on the Iuh interface (between HNB and HNB-GW) carried using the Iu UP framing protocol as defined in the TS 25.415 [17] UTRAN Iu interface user plane protocols. The HNB Iu UP entity follows the procedures and principles defined in the Iu UP framing protocol specification (TS25.415 [17] UTRAN Iu interface user plane protocols). Most of the Iu UP PDUs will be transferred by the HNB-GW without any processing. However, the HNB-GW will perform certain functionalities that could be implemented by an IuhUPIF (Iuh user plane interworking function) in the HNB-GW as described below. + +The IuhUPIF is the functional entity responsible for aligning or mapping control procedures (including RFCIs, frame numbers etc) on the separate UP interfaces. The IuhUPIF determines if the two UP configurations (at the HNB and CN) are identical and thus the UP PDUs may be passed transparently. If the IuhUPIF determines that the two UP configurations are not identical it applies the necessary mapping. + +![Diagram of the Iuh Framing Protocol Interworking Function (IuhUPIF) architecture. The diagram shows the flow of Iu UP framing protocol frames between an HNB (left) and an HNB-GW (right). At the HNB, the Iuh Interface connects to the IuhUPIF. The IuhUPIF connects to the RNL/CNL-SAP, which in turn connects to the Iu Support Mode Functions. Below the Iu Support Mode Functions, the transfer of Iu FP protocol frames is shown. The HNB-GW contains its own Iu Support Mode Functions and RNL/CNL-SAP. The IuhUPIF in the HNB-GW connects to the Iu/Interface. The transfer of Iu FP protocol frames is also shown between the HNB-GW and the Iu/Interface. The HNB-GW is connected to the TNL-SAP.](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +Diagram of the Iuh Framing Protocol Interworking Function (IuhUPIF) architecture. The diagram shows the flow of Iu UP framing protocol frames between an HNB (left) and an HNB-GW (right). At the HNB, the Iuh Interface connects to the IuhUPIF. The IuhUPIF connects to the RNL/CNL-SAP, which in turn connects to the Iu Support Mode Functions. Below the Iu Support Mode Functions, the transfer of Iu FP protocol frames is shown. The HNB-GW contains its own Iu Support Mode Functions and RNL/CNL-SAP. The IuhUPIF in the HNB-GW connects to the Iu/Interface. The transfer of Iu FP protocol frames is also shown between the HNB-GW and the Iu/Interface. The HNB-GW is connected to the TNL-SAP. + +Figure A.11.1-1: The Iuh Framing Protocol Interworking Function. + +### A.11.2 CS User Plane handling during the Initial CS RAB setup + +During the CS RAB setup, the HNB allocates the RAB Subflows combination indicator for the SDU formats (SDU formats are sent to the HNB in the RANAP RAB ASSIGNMENT message). The allocation is then sent in the Iu Framing Initialisation PDU by the HNB in the user plane. For further details see TS 25.413 [9] and TS 25.415 [17]. + +Upon reception of the RFCI values in the Iu UP Initialisation Frame (Iu UP PDU type 14 from the HNB) during the call establishment, the HNB-GW stores “UL RFCI vector”. The first subflow of the initialisation corresponds to the Initial Rate control i.e. indicate the highest rate for the first speech mode to be used in the direction of the Initialisation acknowledgement frame. The HNB-GW forwards the Iu UP Initialisation frame towards the CN according to TS 25.415 [17] without any change to the received Iu UP PDU from the HNB. Upon reception of the Iu UP ACK/NACK PDU, the HNB-GW forwards it towards the HNB. + +![Sequence diagram showing IU UP Handling during the Initial call setup. The diagram involves three main entities: HNB, HNB GW, and MSC/MGW. The HNB sends an Iu UP INIT message to the HNB GW. The HNB GW stores RFCIs, acknowledges the Iu framing protocol Init, and terminates the Iu framing protocol. The HNB GW then forwards the Iu UP INIT message to the MSC/MGW. The MSC/MGW stores RFCIs and forwards control PDUs to the network side of the MGW. The MSC/MGW sends an Iu UP INIT ACK/NACK message back to the HNB GW. The HNB GW then forwards the Iu UP INIT ACK/NACK message back to the HNB.](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB_GW as HNB GW + participant MSC_MGW as MSC/MGW + + Note left of HNB: STORE RFCIs, Acknowledge Iu framing protocol Init, terminate the Iu framing protocol. + HNB->>HNB_GW: Iu UP INIT + Note right of HNB_GW: STORE RFCIs, forward control PDUs to network side of MGW + HNB_GW->>MSC_MGW: Iu UP INIT + MSC_MGW-->>HNB_GW: Iu UP INIT ACK/NACK + HNB_GW-->>HNB: Iu UP INIT ACK/NACK + +``` + +Sequence diagram showing IU UP Handling during the Initial call setup. The diagram involves three main entities: HNB, HNB GW, and MSC/MGW. The HNB sends an Iu UP INIT message to the HNB GW. The HNB GW stores RFCIs, acknowledges the Iu framing protocol Init, and terminates the Iu framing protocol. The HNB GW then forwards the Iu UP INIT message to the MSC/MGW. The MSC/MGW stores RFCIs and forwards control PDUs to the network side of the MGW. The MSC/MGW sends an Iu UP INIT ACK/NACK message back to the HNB GW. The HNB GW then forwards the Iu UP INIT ACK/NACK message back to the HNB. + +Figure A.11.2-1: IU UP Handling during the Initial call setup. + +### A.11.3 CS User Plane handling after the finalisation of SRNS Relocation + +During the SRNS Relocation, as part of the RANAP Relocation Resource Allocation procedure, the target HNB performs the user plane initialisation. The (Target) HNB allocates the RAB Subflows combination indicator(s) for the each SDU formats (SDU formats are sent to the HNB in the RANAP RELOCATION REQUEST message). The allocation is then sent in the Iu Framing Initialisation PDU by the HNB in the user plane. For further details see TS 25.413 [9] and TS 25.415 [17]. + +![Sequence diagram illustrating IU UP Handling after SRNS Relocation. The diagram shows three entities: HNB, HNB GW, and MSC/MGW. The HNB sends an IU UP INIT message to the HNB GW. The HNB GW responds with an IU UP INIT ACK. The HNB GW then sends an IU UP RATE CONTROL message to the MSC/MGW. The HNB GW also performs a 'Map RFCI if necessary' function. The HNB GW stores RFCIs, acknowledges the IU framing protocol Init, and terminates the IU framing protocol. The HNB GW also stores RFCIs, acknowledges the IU framing protocol Init. The HNB GW then forwards IU UP Packets to the MSC/MGW.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB_GW as HNB GW + participant MSC_MGW as MSC/MGW + + Note left of HNB: STORE RFCIs, Acknowledge Iu framing protocol Init, terminate the Iu framing protocol. + Note right of HNB_GW: STORE RFCIs, Acknowledge Iu framing protocol Init. + + HNB->>HNB_GW: Iu UP INIT + HNB_GW-->>HNB: Iu UP INIT ACK + HNB_GW->>MSC_MGW: Iu UP RATE CONTROL + Note right of HNB_GW: Map RFCI if necessary + Note right of HNB_GW: Iu UP Packets + +``` + +Sequence diagram illustrating IU UP Handling after SRNS Relocation. The diagram shows three entities: HNB, HNB GW, and MSC/MGW. The HNB sends an IU UP INIT message to the HNB GW. The HNB GW responds with an IU UP INIT ACK. The HNB GW then sends an IU UP RATE CONTROL message to the MSC/MGW. The HNB GW also performs a 'Map RFCI if necessary' function. The HNB GW stores RFCIs, acknowledges the IU framing protocol Init, and terminates the IU framing protocol. The HNB GW also stores RFCIs, acknowledges the IU framing protocol Init. The HNB GW then forwards IU UP Packets to the MSC/MGW. + +**Figure A.11.3-1. IU UP Handling after SRNS Relocation.** + +At reception of an IU UP Initialisation Frame (Iu UP PDU type 14) from the Target HNB, the HNB-GW stores received RFCI indexes (per data rate) in the form of ordered sequence (received in the initialisation PDU) as “UL RFCI Vector” and send the Initialisation acknowledgment to the target HNB. The HNB-GW does not perform the forwarding of the IuUP initialisation on the Iu interface. The HNB-GW checks whether the received RFCI allocations match the stored RFCI allocation for the same bearer established with the source HNB. The HNB-GW performs the following functions: + +- RFCI Mapping function: If the allocated RFCI index (s) does not match with the existing RFCI index(s) for the corresponding data rates, then the HNB-GW performs the RFCI Mapping function. That is, for every subsequent Iu UP frame upon the relocation, the HNB-GW maps the RFCI indices of the incoming side (from the HNB) to the corresponding RFCI indicates to the outgoing side (towards the MSC that is already stored in the HNB-GW) and vice versa. +- In case Iu UP version 1, if the maximum rate indicated by the target HNB in the Iu UP INIT is different from the current used maximum rate then the HNB-GW initiates a Rate Control PDU indicating the new maximum rate to the MSC. + +### A.11.4 FQC + +The HNB-GW (IuhUP IF) does not handle the FQC included in the UP frames. The value included in the Iu UP frame is passed to the peer not without any modification. + +### A.11.5 Frame number + +The frame number indicated by the peer node (i.e. Iu or Iuh) on the receiving side is forwarded unmodified to lower layer on the sending side. + +### A.11.6 Time alignment Procedure: + +When a HNB-GW (IuhUP IF) entity receives a time Alignment Command over the Iu or Iuh interface, it is relayed unmodified to the other peer node. + +### A.11.7 Rate Control Procedure + +When an HNB-GW (IuhUP IF) entity receives a Rate Control over the Iu or Iuh interface, it forwards to the other peer node) with ‘RFCI Mapping’ where appropriate. + +### A.11.8 Payload + +When a HNB-GW (IuhUP IF) entity receives the payload SDUs, the received SDUs is forwarded unmodified to the either side (HNB or HNB-GW) with 'RFCI Mapping' where appropriate. + +### A.11.9 Iu UP Re-Initialisation + +When an HNB-GW (IuhUP IF) entity receives a Iu UP Initialisation from the CN, it stores the "DL RFCI Vector" and then forward it to the HNB without any modification in the RFCIs. Upon reception of the Iu UP ACK/NACK PDU, the HNB-GW forwards it towards the CN. + +![Sequence diagram for Iu UP Re-Initialisation showing interactions between HNB, HNB GW, and MSC/MGW.](53001b5ae3f65139f78db410bb41ae30_img.jpg) + +The diagram illustrates the Iu UP Re-Initialisation process. It features three main entities: HNB, HNB GW, and MSC/MGW. The HNB GW is shown as a double rectangle, indicating it acts as a relay. The sequence of messages is as follows: 1. The HNB GW sends an 'Iu UP INIT' message to the HNB. 2. The HNB responds with an 'Iu UP INIT ACK/NACK' message to the HNB GW. 3. Simultaneously, the HNB GW sends an 'Iu UP INIT' message to the MSC/MGW. 4. The MSC/MGW responds with an 'Iu UP INIT ACK/NACK' message to the HNB GW. Above the HNB, there is a text box: 'STORE RFCIs, Acknowledge Iu framing protocol Init, terminate the Iu framing protocol.' Above the HNB GW, there is a text box: 'STORE RFCIs and forward control PDUs to the HNB'. + +Sequence diagram for Iu UP Re-Initialisation showing interactions between HNB, HNB GW, and MSC/MGW. + +Figure A.11.9-1: IU UP Re- Initialisation. + +# Annex B (informative): Deployment Architecture + +## B.1 Direct Iurh connectivity between HNBs + +The reference model shown in Figure B.1-1 below illustrates an HNB access network with direct Iurh connectivity. + +![Figure B.1-1: HNB access network deploying direct Iurh connectivity. The diagram shows two HNBs connected to an HNB GW via direct Iurh interfaces. Each HNB is also connected to a User Equipment (Uu) and has a vertical Iurh interface between them. An HMS is shown below the HNBs.](4537891530c9f6f139a2e1ebf544edc4_img.jpg) + +The diagram illustrates an HNB access network with direct Iurh connectivity. Two HNBs are shown, each connected to a User Equipment (Uu) via a Uu interface. Both HNBs have a direct Iurh interface connecting them to an HNB GW. The HNB GW is connected to an external network via an Iu interface. A Security Gateway is shown between the HNBs and the HNB GW, but the Iurh interfaces bypass it. An HMS (Home Management System) is shown below the HNBs, connected to them via a vertical Iurh interface. + +Figure B.1-1: HNB access network deploying direct Iurh connectivity. The diagram shows two HNBs connected to an HNB GW via direct Iurh interfaces. Each HNB is also connected to a User Equipment (Uu) and has a vertical Iurh interface between them. An HMS is shown below the HNBs. + +**Figure B.1-1: HNB access network deploying direct Iurh connectivity.** + +An alternative HNB access network configuration deploying the Iurh interface transported via the Security Gateway is shown in Figure B.1-2. + +NOTE: If the Security Gateway and the HNB-GW are co-located then the co-located node should support IP routing. + +![Figure B.1-2: HNB access network deploying Iurh connectivity via a Security Gateway. The diagram shows two HNBs connected to an HNB GW via a Security Gateway. Each HNB is also connected to a User Equipment (Uu) and has a vertical Iurh interface between them. An HMS is shown below the HNBs.](67c232883c119b120d2fb337bf588e05_img.jpg) + +The diagram illustrates an HNB access network configuration where the Iurh interface is transported via a Security Gateway. Two HNBs are shown, each connected to a User Equipment (Uu) via a Uu interface. Both HNBs have an Iurh interface connecting them to a Security Gateway, which in turn connects to an HNB GW. The HNB GW is connected to an external network via an Iu interface. An HMS (Home Management System) is shown below the HNBs, connected to them via a vertical Iurh interface. + +Figure B.1-2: HNB access network deploying Iurh connectivity via a Security Gateway. The diagram shows two HNBs connected to an HNB GW via a Security Gateway. Each HNB is also connected to a User Equipment (Uu) and has a vertical Iurh interface between them. An HMS is shown below the HNBs. + +**Figure B.1-2: HNB access network deploying Iurh connectivity via a Security Gateway.** + +An alternative arrangement with the Iurhr interface transported via the Security Gateway and the HNB-GW is shown in Figure B.1-3. The HNB-GW provides transport routing functionality. + +![Diagram of HNB access network architecture showing HNBs connected to an HNB GW via Iuh and Iurh interfaces, with a Security Gateway and HMS components.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +The diagram illustrates an HNB access network architecture. On the left, two HNB (Home NodeB) units are shown, each with a $U_u$ interface pointing left. Each HNB has a bidirectional connection to a central HNB GW (Home NodeB Gateway) on the right, labeled $Iuh$ . A dashed box labeled 'Security Gateway' is positioned between the HNBs and the HNB GW. The top HNB has a bidirectional connection to the Security Gateway labeled $Iurh$ . The Security Gateway has a bidirectional connection to the HNB GW. The HNB GW has an $I_u$ interface pointing right. Below the HNBs, a dashed box labeled 'HMS' (Home Management System) is shown. + +Diagram of HNB access network architecture showing HNBs connected to an HNB GW via Iuh and Iurh interfaces, with a Security Gateway and HMS components. + +Figure B.1-3: HNB access network deploying Iurh connectivity via the HNB-GW. + +# Annex C (informative): Implementation of PSC Disambiguation for Support of Legacy UE Mobility from RNC to HNB + +## C.1 Scope + +In some HNB deployments the limited number of PSCs available to be allocated to HNBs may cause PSC ambiguity. This may result in the inability of identifying, at the source macro RNC, a unique target HNB corresponding to a PSC reported by a Legacy UE (i.e., UEs not capable of SI acquisition). + +In this informative annex two solutions for PSC disambiguation are described. + +The implementation options described in this Annex are not intended to be evolved in the 3GPP specifications. + +## C.2 Disambiguation at the RNC + +This implementation option can be split in two different steps: + +Step 1: At first, during previous HNB to RNC mobility, the RNC builds a local database of necessary information concerning neighbouring cells with PSC confusion (e.g., neighbouring cells PSCs, Cell IDs, Observed Time Difference (OTD)). This local database is built/maintained via handover preparation signalling. The HNB shall include the full Measurement Report and the source cell ID in the handover preparation signalling, and the target RNC collects incoming data and adds/updates OTD information to its database. + +Step 2: In a second phase, during RNC to HNB mobility (hand-in), the RNC uses the information previously gathered in order to disambiguate the target HNB in case of a certain PSC is reused in a given (target) area. + +### C.2.1 Step 1: Construction of HNB database in the RNC + +Figure C.2.1-1 depicts the first step of this implementation option. It consists in the RNC building the database of HNBs during HNB to RNC mobility. Such database includes PSCs, Cell IDs and Assistance data (e.g., OTD). + +![Diagram illustrating Step 1 of RNC constructing database of HNBs during HNB to RNC mobility. A UE (User Equipment) is shown at the bottom left, connected to an HNB-GW & HNB. The HNB-GW & HNB is connected to a CN (Core Network) via a B interface. The CN is connected to an RNC via a B interface. The RNC is connected to a DB (Database) via a C interface. An arrow labeled A points from the UE to the HNB-GW & HNB. Arrows labeled B point from the HNB-GW & HNB to the CN and from the CN to the RNC. An arrow labeled C points from the RNC to the DB.](5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg) + +``` +graph TD; UE[UE] -- A --> HNBGW[HNB-GW & HNB]; HNBGW -- B --> CN[CN]; CN -- B --> RNC[RNC]; RNC -- C --> DB[(DB)]; +``` + +Diagram illustrating Step 1 of RNC constructing database of HNBs during HNB to RNC mobility. A UE (User Equipment) is shown at the bottom left, connected to an HNB-GW & HNB. The HNB-GW & HNB is connected to a CN (Core Network) via a B interface. The CN is connected to an RNC via a B interface. The RNC is connected to a DB (Database) via a C interface. An arrow labeled A points from the UE to the HNB-GW & HNB. Arrows labeled B point from the HNB-GW & HNB to the CN and from the CN to the RNC. An arrow labeled C points from the RNC to the DB. + +**Figure C.2.1-1: Step 1 – Example of RNC constructing database of HNBs during HNB to RNC mobility.** + +This first step can be split in the following sub-steps: + +- The UE under control of the HNB is configured to provide measurement reports, including OTD data. + +Such measurement report, e.g., can be carried within an RRC:Measurement Report to the HNB and, subsequently, to the target RNC via handover preparation procedures. + +- B. The HNB initiates relocation towards macro cells, by including the source cell identity and full Measurement Report in the *Source RNC to Target RNC Transparent Container*; +- C. The Macro RNC collects incoming data and adds/updates OTD information to its database. + +At this stage, the Macro RNC has built a database with all necessary information for future RNC to HNB relocation (hand-in). + +### C.2.2 Step 2: PSC disambiguation executed by the RNC during RNC to HNB hand-in + +Figure C.2.2-1 depicts the second step of implementation option. The RNC, during RNC to HNB mobility (hand-in), can disambiguate the target HNB on the basis of the information collected in the target cells database. + +![Diagram illustrating Step 2 of PSC disambiguation at the RNC during RNC to HNB relocation. The diagram shows three main components: CN (Core Network), HNB-GW & HNB (Home NodeB Gateway and Home NodeB), and RNC (Radio Network Controller). The RNC is connected to a DB (Database). Arrows indicate the flow of information: A (from UE to RNC), B (from RNC to DB), C (from RNC to CN), C (from CN to HNB-GW & HNB), and C (from RNC to HNB-GW & HNB).](b71ad9fc874230de9ba4480e12a216f7_img.jpg) + +``` + +graph TD + UE[UE] -- A --> RNC[RNC] + RNC -- B --> DB[(DB)] + RNC -- C --> CN[CN] + CN -- C --> HNBGW[HNB-GW & HNB] + RNC -- C --> HNBGW + +``` + +Diagram illustrating Step 2 of PSC disambiguation at the RNC during RNC to HNB relocation. The diagram shows three main components: CN (Core Network), HNB-GW & HNB (Home NodeB Gateway and Home NodeB), and RNC (Radio Network Controller). The RNC is connected to a DB (Database). Arrows indicate the flow of information: A (from UE to RNC), B (from RNC to DB), C (from RNC to CN), C (from CN to HNB-GW & HNB), and C (from RNC to HNB-GW & HNB). + +**Figure C.2.2-1: Step 2 – Example of PSC disambiguation at RNC during RNC to HNB relocation.** + +As shown in the figure above, the second step of this implementation option consists of the following sub-steps: + +- A. The RNC enables the normal measurement reporting to a “shared” PSC in the area; +- B. In case of shared target PSC and if the UE is not SI reading capable, the RNC checks the cells reported in the measurement report, calculates the $\Delta$ OTD information based on the measurement report and finds the best match in the database created in Step 1; +- C. The RNC initiates relocation towards the selected target HNB as per normal mobility procedures. + +## C.3 Disambiguation at the HNB-GW + +This solution allows the HNB-GW to identify the target HNB based on the source Cell ID and the measurements including OTD which are reported by the UE during the handover as shown in Figure C.3-1. The procedure includes two parts: + +- Construction and Update of HNB Timing Information ( $\Delta$ OTD) Database at the HNB-GW. +- Target Cell Disambiguation at the HNB-GW during handover to a HNB connected to this HNB-GW. + +![Figure C.3-1: ΔOTD based disambiguation at the HNB-GW. The diagram shows a sequence of four steps: 1. A UE sends an MRM (PSC, timing difference) to an S-RNC. 2. The S-RNC sends a RANAP Relocation Required message (Source Cell Id, HNB-GW id, OTD_HNB, OTD_MNB from Step 1) to the Core Network. 3. The Core Network sends a RANAP Relocation Request (Source Cell Id, OTD_HNB, OTD_MNB) to the HNB-GW. 4. The HNB-GW performs disambiguation using ΔOTD + Source Cell to identify the correct HNB (HNB1) among multiple candidates (HNB1, HNB2) that share the same PSC (In PSC Confusion).](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Figure C.3-1: ΔOTD based disambiguation at the HNB-GW. The diagram shows a sequence of four steps: 1. A UE sends an MRM (PSC, timing difference) to an S-RNC. 2. The S-RNC sends a RANAP Relocation Required message (Source Cell Id, HNB-GW id, OTD\_HNB, OTD\_MNB from Step 1) to the Core Network. 3. The Core Network sends a RANAP Relocation Request (Source Cell Id, OTD\_HNB, OTD\_MNB) to the HNB-GW. 4. The HNB-GW performs disambiguation using ΔOTD + Source Cell to identify the correct HNB (HNB1) among multiple candidates (HNB1, HNB2) that share the same PSC (In PSC Confusion). + +Figure C.3-1: $\Delta$ OTD based disambiguation at the HNB-GW. + +### C.3.1 Construction and Update of $\Delta$ OTD Database at the HNB-GW + +$\Delta$ OTD = (OTDHNB - OTDMNB) represents a HNB's timing with respect to a macro cell (MNB) as measured by the UE where $\Delta$ OTDCell is the timing of a UE with respect to a given cell [25]. The HNB-GW keeps a database of the $\Delta$ OTD values for HNBs under its control and their neighbour MNB cells. The HNB-GW also keeps the mapping of a MNB's Cell ID and its PSC. + +The HNB-GW updates the $\Delta$ OTD database by using the information provided by the UEs during handovers to MNB cells. During these hand-outs, a HNB includes the MEASUREMENT REPORT message (MRM) in the RRC transparent container which is sent in the RANAP *Relocation Required* message and set the *Target Cell Id* IE to the ID of the macro cell with respect to which the OTD is computed. + +### C.3.2 Target Cell Disambiguation for Handover to the HNB + +The procedure can be implemented as follows: + +1. UE is triggered to send an RRC Measurement Report (including OTD for both source and target cells) to the SRNC by the rules set by the UTRAN. +2. The source RAN triggers relocation of the UE session by sending the RANAP RELOCATION REQUIRED message to the Core Network: + - The time difference information of the target HNB cell and the source Macro cell is contained in the *RRC Container* IE as defined in TS 25.331 [25]. + - Source Cell ID is transmitted in the *Source RNC to Target RNC Transparent Container*. + - *Target Cell ID* IE may be set to a special value since the actual Cell ID is not known. +3. HNB-GW determines that PSC disambiguation is needed when target cell ID does not identify a HNB under its control. The HNB GW selects the target HNB using the received information (including the source Cell ID and MRM) and the $\Delta$ OTD database. +4. The remainder of the relocation procedure continues normally as documented in 3GPP TS 25.413 [9] and 3GPP TS 23.060 [10]. + +Additionally, after the successful inbound handover, the HNB GW can update the $\Delta$ OTD information between the target HNB cell and the source MNB cell using the received information. + +## C.4 Notes + +For both solutions described above, the following notes apply: + +NOTE 1: It is assumed that the HNB GW/RNC has the mapping of neighbouring cells PSCs and Cell IDs. + +NOTE 2: If OTD signatures are not maintained up to date, handover failures may occur. + +NOTE 3: The range of $\Delta$ OTDs will be different for intra and inter-frequency cell measurements (e.g., when the HNB cell is measured on another frequency than the source cell). Consequently the disambiguation performance in the two scenarios may differ. + +# --- Annex D (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 09/2009 | | | | Rel-9 version is created based on v.8.3.0 | 9.0.0 | +| 45 | RP-090999 | 0044 | 3 | Support for paging optimization with CSG membership changes | 9.0.0 | +| 45 | RP-090999 | 0048 | 1 | Enhancements to handle HNB to HNB mobility | 9.0.0 | +| 45 | RP-090999 | 0049 | 1 | Access Mode and Membership notification for UEs accessing CSG-Hybrid cells | 9.0.0 | +| 10/2009 | | | | Editorial changes: 5.x.2 -> 5.7.2 and adding numbering to Figure 5.7.2-1 | 9.0.1 | +| 46 | RP-091191 | 0039 | 4 | CS Mux on Uplink | 9.1.0 | +| 46 | RP-091195 | 0053 | 2 | Enhanced Interference Management Mechanisms for HNB | 9.1.0 | +| 46 | RP-091191 | 0057 | | Introducing changes for supporting ETWS in Home Node B (Rel9) | 9.1.0 | +| 46 | RP-091184 | 0059 | 1 | Add assigned SCTP Port Number for RUA and HNBAP | | +| 46 | RP-091191 | 0061 | | Addition of use of COMMON ID message to convey Hybrid cell membership information. | 9.1.0 | +| 46 | RP-091184 | 0067 | | Clean up of 25.467 | 9.1.0 | +| 46 | RP-091191 | 0070 | 1 | Mitigating IMSI spoofing in non-CSG UE registration | 9.1.0 | +| 46 | RP-091191 | 0071 | 1 | UE registration in case of HNB-GW access control | 9.1.0 | +| 46 | RP-091191 | 0072 | 1 | Inbound Mobility to CSG and Hybrid Cells | 9.1.0 | +| 47 | RP-100219 | 0073 | | Clarification of HNB Definition | 9.2.0 | +| 47 | RP-100219 | 0075 | | Corrections on the non-CSG UEs registration and Iuh Disconnect Procedure | 9.2.0 | +| 47 | RP-100365 | 0076 | 3 | Removal of incomplete material for intra-GW Handover | 9.2.0 | +| 47 | RP-100222 | 0083 | 2 | Removal of FFS in Rel-9 stage 2 specification | 9.2.0 | +| 47 | RP-100222 | 0085 | 7 | CSG expiry Handling | 9.2.0 | +| 47 | RP-100222 | 0086 | 2 | PSC Split Clarification | 9.2.0 | +| 47 | RP-100222 | 0087 | 3 | Clarifications on UE registration and mobility procedures | 9.2.0 | +| 48 | RP-100595 | 0092 | 2 | Support of HNB GW functionalities | 9.3.0 | +| 48 | RP-100595 | 0094 | | Location information correction for Stage 2 | 9.3.0 | +| 50 | RP-101271 | 0111 | | PPI value for SABP in Iuh | 9.4.0 | +| 50 | RP-101271 | 0113 | | Clarification on Inbound Mobility to HNB | 9.4.0 | +| 12/2010 | | | | Rel-10 version is created based on version 9.4.0 | 10.0.0 | +| 50 | RP-101407 | 0101 | 5 | Introduction of the Implementation Variant where CN functions for the enhancement of inter-HNB intra-HNB-GW SRNS Relocation are implemented within the HNB-GW. | 10.0.0 | +| 50 | RP-101272 | 0112 | 2 | Clarification of use of RNC-Id | 10.0.0 | +| 50 | RP-101188 | 0114 | 4 | Introduction of HNB to HNB mobility procedure using direct interface | 10.0.0 | +| 50 | RP-101389 | 0117 | 2 | Introduction of LIPA Functions for UMTS | 10.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.0 | +| 51 | RP-110231 | 0125 | | Correction on UE De-Registration for Enhanced H2H Mobility | 10.1.0 | +| 51 | RP-110227 | 0126 | | Completion of LIPA feature | 10.1.0 | +| 51 | RP-110231 | 0131 | 2 | Correction to definition of HNB enhanced mobility | 10.1.0 | +| 52 | RP-110689 | 0135 | | Removal of double-numbering from 3 sub-clauses | 10.2.0 | +| 52 | RP-110691 | 0136 | 2 | Removal of Access Query Procedure for Intra-CSG Handover | 10.2.0 | +| 52 | RP-110686 | 0140 | 4 | Cleanup and small corrections of 25.467 before Rel-10 closure | 10.2.0 | +| 52 | RP-110691 | 0142 | 2 | Final specification of the provision of Iuh-connectivity related TNL addresses | 10.2.0 | +| 53 | RP-111194 | 0144 | 1 | Corrections on Partial Failure During Enhanced H2H Mobility | 10.3.0 | +| 53 | RP-111196 | 0148 | 1 | Access Control for Soft Handover between HNBs | 10.3.0 | +| 53 | RP-111194 | 0150 | 2 | Stage 2 clean-up for HNB mobility | 10.3.0 | +| 53 | RP-111192 | 0153 | 1 | Remaining UE Context Issue during Mobility | 10.3.0 | +| 53 | RP-111196 | 0155 | 1 | Correction to protocol stack | 10.3.0 | +| 53 | RP-111194 | 0157 | 1 | SHO for different Iuh Connectivity | 10.3.0 | +| 53 | RP-111194 | 0158 | 1 | Security Mechanism for H(e)NB "no-IPsec" usage option | 10.3.0 | +| 54 | RP-111651 | 0159 | 1 | Rapporteur update on specification references | 10.4.0 | +| 54 | RP-111648 | 0160 | 1 | Access Control in RNSAP Relocation between HNBs | 10.4.0 | +| 54 | RP-111650 | 0161 | | Measurement configuration for Inbound Mobility | 10.4.0 | +| 54 | RP-111651 | 0162 | 2 | Corrections on UE Registration Procedure | 10.4.0 | +| 54 | RP-111646 | 0164 | | Correction of Emergency Call | 10.4.0 | +| 56 | RP-120744 | 0173 | 3 | Correction of emergency call handling during Inbound mobility | 10.5.0 | +| 57 | RP-121131 | 0177 | | Corrections on Iuh Setup | 10.6.0 | +| 09/2012 | | | | Rel-11 version is created based on version 10.6.0 | | +| 57 | RP-121136 | 0178 | 2 | Introduction of connectivity between HNBs and RNCs via the HNB-GW for RNSAP signalling | 11.0.0 | +| 57 | RP-121140 | 0179 | 2 | Verification of HNB Identity | 11.0.0 | +| 58 | RP-121736 | 0184 | | Clarification of target HNB behaviour in case of Relocation Failure | 11.1.0 | + +| | | | | | | +|---------|-----------|------|---|--------------------------------------------------------------------------------------------------------------------------|--------| +| 58 | RP-121732 | 0185 | 2 | Introduction of connectivity between HNB and RNC via HNB-GW for RNSAP signalling: soft handover between HNB and RNC | 11.1.0 | +| 58 | RP-121732 | 0188 | 2 | Introduction of connectivity between HNB and RNC via HNB-GW for RNSAP signaling: Enhanced Relocation between HNB and RNC | 11.1.0 | +| 58 | RP-121733 | 0189 | 1 | Support or Legacy UEs hand-in | 11.1.0 | +| 58 | RP-121739 | 0190 | 2 | New Information for BBF access | 11.1.0 | +| 58 | RP-121733 | 0193 | | Support of the Target HNB Cell Disambiguation at the HNB-GW | 11.1.0 | +| 59 | RP-130211 | 0195 | 2 | Clarification on inter-PLMN HO to CSG cell | 11.2.0 | +| 59 | RP-130212 | 0197 | 1 | Rapporteur editorial corrections | 11.2.0 | +| 60 | RP-130643 | 0199 | | Correction of the reference architecture figure | 11.3.0 | +| 61 | RP-131183 | 0204 | | Correction of HNB Verification | 11.4.0 | +| 61 | RP-131183 | 0205 | | Correction for the reference model | 11.4.0 | +| 62 | RP-131902 | 0211 | | Correction of Fixed Broadband Access | 11.5.0 | +| 62 | RP-131909 | 0206 | 4 | Introduction of Collocated L-GW for SIPTO@LN | 12.0.0 | +| 62 | RP-131908 | 0207 | 2 | Introduction of CELL_FACH, CELL_PCH and URA_PCH mobility support for HNBs | 12.0.0 | +| 62 | RP-131908 | 0208 | 2 | Support for connected mode inbound mobility to shared CSG/hybrid cell | 12.0.0 | +| 62 | RP-131907 | 0209 | 3 | Stage 2 changes for PCAP over luh | 12.0.0 | +| 62 | RP-131909 | 0210 | 1 | Introduction of Standalone GW for SIPTO@LN | 12.0.0 | +| 62 | RP-131913 | 0216 | 1 | Correction of inbound mobility for CSG UE | 12.0.0 | +| 63 | RP-140297 | 0217 | 2 | Clarification on Inbound mobility to an UTRAN CSG cell | 12.1.0 | +| 64 | RP-140907 | 0219 | - | Introduction of PPI for PUA | 12.2.0 | +| 66 | RP-142093 | 0221 | - | Rapporteur Review | 12.3.0 | +| 12/2015 | | | | Rel-13 version is created based on version 12.3.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25468/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/25_series/25468/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fbdc285bc9f939896db1e6b04c7d8cb41a70cd0 --- /dev/null +++ b/marked/Rel-16/25_series/25468/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:609fe600ac10b334505507f62e6e0223d96b0be469334808214e377f8cd6a050 +size 11739 diff --git a/marked/Rel-16/25_series/25468/536951b2bbd94325ae266d8d1363df8f_img.jpg b/marked/Rel-16/25_series/25468/536951b2bbd94325ae266d8d1363df8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d6d63504d355e47e770a0332a977b639225ef54 --- /dev/null +++ b/marked/Rel-16/25_series/25468/536951b2bbd94325ae266d8d1363df8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67bbbdb1d39317d6dbfb938cd0e8fb7d541f0ded656ca4f13ee2e11f11630878 +size 14357 diff --git a/marked/Rel-16/25_series/25468/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/25_series/25468/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09680899d68cd1608f5fab6e5715bb3d9cab95d9 --- /dev/null +++ b/marked/Rel-16/25_series/25468/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a3dec7f62fbc8ff2aa1bb8b082b1c16a8f5e59094ac6bf4f253123ed7855033 +size 14533 diff --git a/marked/Rel-16/25_series/25468/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/25_series/25468/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422bef41605fc41042d8d55abd96b68615c8bcde --- /dev/null +++ b/marked/Rel-16/25_series/25468/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baa60ba25124a098b53f379af9bbf0d17bd2c76e54795a79ac0bd802945a5376 +size 12311 diff --git a/marked/Rel-16/25_series/25468/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-16/25_series/25468/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a80093319de51a0a68af0803a676badc6b5ec1 --- /dev/null +++ b/marked/Rel-16/25_series/25468/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b36e49fa1779589f826b394482c95dc50481230346fe7d90e069097f1a3bbf5 +size 10782 diff --git a/marked/Rel-16/25_series/25468/a7079ddb124df3f1ee13ae406c7c8982_img.jpg b/marked/Rel-16/25_series/25468/a7079ddb124df3f1ee13ae406c7c8982_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc2ed14741df11d23c97dad0c4fda95f47221214 --- /dev/null +++ b/marked/Rel-16/25_series/25468/a7079ddb124df3f1ee13ae406c7c8982_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d928c2051ac726d0b56299d4ab3a1e1ce3f0a74442280a13e440dcdd0f1339d +size 14849 diff --git a/marked/Rel-16/25_series/25468/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/25_series/25468/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c13d7e762db3085254eab491053b59bc24b1b773 --- /dev/null +++ b/marked/Rel-16/25_series/25468/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a8af8b59f9eb3cdd58cdd4a86f21ba7999c293efb983488e79c7c97b600a1f +size 11553 diff --git a/marked/Rel-16/25_series/25468/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-16/25_series/25468/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e1fe5d6c471aedbbbc724420c94c231d52d6b9b --- /dev/null +++ b/marked/Rel-16/25_series/25468/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:863d1e3090337f59ed6862117aa8d8fbbd2963457ae404b31a718eb5a4c1a003 +size 21247 diff --git a/marked/Rel-16/25_series/25468/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/25_series/25468/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b99f589f313a7b54ccdb92e13952e0a0380ed81a --- /dev/null +++ b/marked/Rel-16/25_series/25468/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6a058a0b0754ebfebb06f91ccc6a37d10c8e918681a70f92d6292b34903a5a9 +size 12438 diff --git a/marked/Rel-16/25_series/25468/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-16/25_series/25468/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c1d39cae0496c2845c766ac3af9db70bbc3c8af --- /dev/null +++ b/marked/Rel-16/25_series/25468/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5889db81455a72d06566c547cf200f661ec1e1bbde2bbf9b1869fddbfffa3346 +size 13971 diff --git a/marked/Rel-16/25_series/25468/fe61ee8618403cf584b2e28c4bada03a_img.jpg b/marked/Rel-16/25_series/25468/fe61ee8618403cf584b2e28c4bada03a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8b007129008a99fceb11c3cdc2a19242493bc77 --- /dev/null +++ b/marked/Rel-16/25_series/25468/fe61ee8618403cf584b2e28c4bada03a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3185e6f29b0b3db4a047c749ce0add5c030fa3bc5ad270c1cf30f0a4f8b9289b +size 11991 diff --git a/marked/Rel-16/25_series/25468/raw.md b/marked/Rel-16/25_series/25468/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0015c09df4c9397ba4e121483334c9b0d9f3108b --- /dev/null +++ b/marked/Rel-16/25_series/25468/raw.md @@ -0,0 +1,1912 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 7 | +| 4.1 Procedure specification principles ..... | 7 | +| 4.2 Forwards and backwards compatibility..... | 7 | +| 4.3 Specification notations ..... | 7 | +| 5 RUA services ..... | 8 | +| 6 Services expected from the transport layer..... | 8 | +| 7 Functions of RUA ..... | 8 | +| 8 RUA procedures..... | 8 | +| 8.1 Elementary Procedures..... | 8 | +| 8.2 Connect..... | 8 | +| 8.2.1 General ..... | 8 | +| 8.2.2 Successful Operation..... | 9 | +| 8.2.2.1 HNB Originated..... | 9 | +| 8.2.2.2 HNB-GW Originated..... | 9 | +| 8.3 Direct Transfer ..... | 10 | +| 8.3.1 General ..... | 10 | +| 8.3.2 Successful Operation (HNB-GW Originated)..... | 10 | +| 8.3.3 Successful Operation (HNB Originated)..... | 10 | +| 8.3.4 Abnormal Conditions ..... | 10 | +| 8.4 Disconnect..... | 10 | +| 8.4.1 General ..... | 10 | +| 8.4.2 Successful Operation (HNB Originated)..... | 11 | +| 8.4.3 Successful Operation (HNB-GW Originated)..... | 11 | +| 8.4.4 Abnormal Conditions ..... | 11 | +| 8.5 Connectionless Transfer..... | 11 | +| 8.5.1 General ..... | 11 | +| 8.5.2 Successful Operation (HNB-GW Originated)..... | 11 | +| 8.5.3 Successful Operation (HNB Originated)..... | 12 | +| 8.5.4 Abnormal Conditions ..... | 12 | +| 8.6 Error Indication ..... | 12 | +| 8.6.1 General ..... | 12 | +| 8.6.2 Successful Operation..... | 12 | +| 9 Elements for RUA communication..... | 13 | +| 9.1 Message functional definition and content..... | 13 | +| 9.1.1 General ..... | 13 | +| 9.1.2 Message contents..... | 13 | +| 9.1.2.1 Presence ..... | 13 | +| 9.1.2.2 Criticality ..... | 13 | +| 9.1.2.3 Range ..... | 13 | +| 9.1.2.4 Assigned Criticality ..... | 13 | +| 9.1.3 CONNECT ..... | 14 | +| 9.1.4 DIRECT TRANSFER ..... | 14 | +| 9.1.5 DISCONNECT..... | 14 | +| 9.1.6 CONNECTIONLESS TRANSFER ..... | 14 | +| 9.1.7 ERROR INDICATION ..... | 15 | +| 9.2 Information Element Definitions ..... | 15 | +| 9.2.0 General ..... | 15 | + +- 9.2.1 Message Type.....15 +- 9.2.2 Context ID .....15 +- 9.2.3 Establishment Cause.....16 +- 9.2.4 Intra Domain NAS Node Selector.....16 +- 9.2.5 RANAP Message.....18 +- 9.2.6 CN Domain Indicator .....18 +- 9.2.7 Cause .....18 +- 9.2.8 Criticality Diagnostics .....20 +- 9.2.9 CSG Membership Status .....21 +- 9.3 Message and Information Element Abstract Syntax (with ASN.1) .....22 + - 9.3.0 General .....22 + - 9.3.1 Usage of private message mechanism for non-standard use .....22 + - 9.3.2 Elementary Procedure Definitions.....22 + - 9.3.3 PDU definitions .....25 + - 9.3.4 Information Element definitions.....29 + - 9.3.5 Common definitions .....33 + - 9.3.6 Constant definitions.....34 + - 9.3.7 Container definitions .....35 +- 9.4 Message transfer syntax .....38 +- 10 Handling of unknown, unforeseen, and erroneous protocol data .....39 + - 10.1 General .....39 + - 10.2 Transfer Syntax Error.....39 + - 10.3 Abstract Syntax Error.....39 + - 10.3.1 General .....39 + - 10.3.2 Criticality Information .....40 + - 10.3.3 Presence Information.....40 + - 10.3.4 Not comprehended IE/IE group.....41 + - 10.3.4.1 Procedure Code.....41 + - 10.3.4.1A Type of Message.....41 + - 10.3.4.2 IEs other than the Procedure Code and Type of Message .....41 + - 10.3.5 Missing IE or IE group .....42 + - 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present .....43 + - 10.4 Logical Error .....44 + - 10.5 Exceptions .....44 +- Annex A (informative): Change History.....45 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the *RANAP User Adaption* (RUA) between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils the HNB- HNB-GW communication requirements specified in TS 25.467 [3] and is defined over the Iuh – reference point. It provides transparent transport for RANAP messages. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [3] 3GPP TS 25.467: "UTRAN architecture for 3G Home NodeB; Stage 2". +- [4] 3GPP TR 25.921 (version.7.0.0): "Guidelines and principles for protocol description and error handling". +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [6] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [7] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [8] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [9] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905 [5]. + +**UE-associated Signalling Connection:** UE-associated Signalling Connection is a logical connection between HNB and HNB-GW associated to an Iu signalling connection for a particular UE over the single signalling connection between the HNB and HNB-GW, identified by the identities *Context ID* and *CN Domain ID*. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|----------------------| +| CN | Core Network | +| EP | Elementary Procedure | +| HNB | Home Node B | + +| | | +|--------|--------------------------------------| +| HNB-GW | Home Node B Gateway | +| PDU | Protocol Data Unit | +| RUA | RANAP User Adaption | +| SCTP | Stream Control Transmission Protocol | + +# --- 4 General + +The protocol described in the present document is the protocol between HNB-GW and HNB. + +## 4.1 Procedure specification principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the HNB & HNB-GW exactly and completely.. + +The following specification principles have been applied for the procedure text in clause 8: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + - 2) Functionality which "shall, if supported" be executed: + - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. + +## 4.2 Forwards and backwards compatibility + +The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification notations + +For the purposes of the present document, the following notations apply: + +- | | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. HNB Registration 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. CONNECT 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. HNB Identity IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 RUA services + +RUA provides the signalling service between the HNB and the HNB-GW that is required to fulfil the RUA functions described in Clause 7. + +# --- 6 Services expected from the transport layer + +Following service is expected from the transport layer: + +- reliable and in sequence delivery of Signalling data using SCTP (IETF RFC 4960 [9]) + +# --- 7 Functions of RUA + +The RUA has the following functions: + +- Transparent transfer of RANAP messages +- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined. + +These functions are implemented by one or several RUA elementary procedures described in the following clauses. + +# --- 8 RUA procedures + +## 8.1 Elementary Procedures + +Table 1 summarizes the EPs. + +**Table 1; Elementary procedures** + +| Elementary Procedure | Message | +|-------------------------|-------------------------| +| Connect | CONNECT | +| Direct Transfer | DIRECT TRANSFER | +| Disconnect | DISCONNECT | +| Connectionless Transfer | CONNECTIONLESS TRANSFER | +| Error Indication | ERROR INDICATION | + +## 8.2 Connect + +### 8.2.1 General + +The HNB or HNB-GW can initiate this procedure to establish an UE-associated Signalling Connection and carry a RANAP message. + +### 8.2.2 Successful Operation + +#### 8.2.2.1 HNB Originated + +![Diagram of Figure 1: Connect to HNB-GW procedure. It shows two rectangular boxes labeled 'HNB' and 'HNB-GW'. Below each box is a thick horizontal line representing a ground or base. A horizontal arrow labeled 'CONNECT' points from the HNB box to the HNB-GW box. Vertical lines connect each box to its respective ground line.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram of Figure 1: Connect to HNB-GW procedure. It shows two rectangular boxes labeled 'HNB' and 'HNB-GW'. Below each box is a thick horizontal line representing a ground or base. A horizontal arrow labeled 'CONNECT' points from the HNB box to the HNB-GW box. Vertical lines connect each box to its respective ground line. + +**Figure 1: Connect to HNB-GW procedure** + +This procedure is used to carry the first RANAP message from the HNB to the HNB-GW. + +Additional information is provided to enable the HNB-GW to handle the RANAP message without it being necessary to inspect the contents and trigger the establishment of a new UE-associated Signalling Connection between HNB and HNB-GW, which is directly mapped to the Iu Signalling Connection the RANAP message refers to. + +If HNB receives the *Intra Domain NAS Node Selector* IE in the RRC message, the HNB shall, if supported, include the *Intra Domain NAS Node Selector* IE in the CONNECT message. + +NOTE: The Context ID is used as the Iu Signalling Connection identifier in the corresponding RANAP messages. + +#### 8.2.2.2 HNB-GW Originated + +![Diagram of Figure 1A: Connect to HNB procedure. It shows two rectangular boxes labeled 'HNB' and 'HNB-GW'. Below each box is a thick horizontal line representing a ground or base. A horizontal arrow labeled 'CONNECT' points from the HNB-GW box to the HNB box. Vertical lines connect each box to its respective ground line.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +Diagram of Figure 1A: Connect to HNB procedure. It shows two rectangular boxes labeled 'HNB' and 'HNB-GW'. Below each box is a thick horizontal line representing a ground or base. A horizontal arrow labeled 'CONNECT' points from the HNB-GW box to the HNB box. Vertical lines connect each box to its respective ground line. + +**Figure 1A: Connect to HNB procedure** + +This procedure is used to carry the first RANAP message from the HNB-GW to an HNB for a particular UE, e.g. RANAP RELOCATION REQUEST. This shall trigger the establishment of a new UE-associated Signalling Connection between HNB-GW and HNB, which is directly mapped to the Iu Signalling Connection the RANAP message refers to. + +The HNB-GW allocates the context id. + +If the first RANAP message received by the HNB GW is a RELOCATION REQUEST message and the RELOCATION REQUEST does not contain the CSG ID of the target cell the RUA CONNECT message may contain the *CSG Membership Status* IE. + +Additional information is provided by the HNB-GW to the HNB to assist the HNB in handling the RANAP message. + +## 8.3 Direct Transfer + +### 8.3.1 General + +This procedure is initiated by either the HNB or HNB-GW to transport a RANAP message between the two nodes. The HNB-GW can initiate this procedure to establish an UE-associated Signalling Connection when carrying the second RANAP RELOCATION REQUEST message. + +### 8.3.2 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing Direct Transfer from HNB-GW to HNB.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +A sequence diagram showing two nodes, HNB and HNB-GW, represented by boxes at the top. Below each box is a vertical line representing a lifeline, ending in a thick horizontal bar. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. + +Sequence diagram showing Direct Transfer from HNB-GW to HNB. + +Figure 2: Direct Transfer to HNB + +This procedure is used to carry any DL connection-oriented RANAP message defined in TS 25.413 [2] from the HNB-GW to the HNB. + +This procedure can be used to carry the second RANAP RELOCATION REQUEST message from the HNB-GW to an HNB for a particular UE. This shall trigger the establishment of a second UE-associated Signalling Connection between HNB-GW and HNB, which is directly mapped to the Iu Signalling Connection the RANAP message refers to. + +### 8.3.3 Successful Operation (HNB Originated) + +![Sequence diagram showing Direct Transfer from HNB to HNB-GW.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +A sequence diagram showing two nodes, HNB and HNB-GW, represented by boxes at the top. Below each box is a vertical line representing a lifeline, ending in a thick horizontal bar. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. + +Sequence diagram showing Direct Transfer from HNB to HNB-GW. + +Figure 3: Direct Transfer to HNB-GW + +This procedure is used to carry any UL connection-oriented RANAP message defined in TS 25.413 [2], except those carried in CONNECT or DISCONNECT messages, from the HNB to the HNB-GW. + +### 8.3.4 Abnormal Conditions + +- + +## 8.4 Disconnect + +### 8.4.1 General + +This procedure is initiated by either the HNB or the HNB-GW to terminate an UE-associated Signalling Connection between these nodes. + +### 8.4.2 Successful Operation (HNB Originated) + +![Sequence diagram showing DISCONNECT from HNB to HNB-GW.](fe61ee8618403cf584b2e28c4bada03a_img.jpg) + +A sequence diagram showing two nodes, HNB and HNB-GW, represented by boxes at the top. Below each box is a vertical line representing a lifeline, ending in a thick horizontal bar. A horizontal arrow labeled 'DISCONNECT' points from the HNB lifeline to the HNB-GW lifeline. + +Sequence diagram showing DISCONNECT from HNB to HNB-GW. + +Figure 4: Disconnect to HNB-GW + +This procedure is used to carry the last RANAP (TS 25.413 [2]) UL connection-oriented message of a given Iu Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate error conditions at the HNB. + +### 8.4.3 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing a DISCONNECT message from HNB-GW to HNB.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +A sequence diagram illustrating the 'Disconnect to HNB' procedure. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A horizontal arrow labeled 'DISCONNECT' points from the 'HNB-GW' lifeline to the 'HNB' lifeline. + +Sequence diagram showing a DISCONNECT message from HNB-GW to HNB. + +Figure 5: Disconnect to HNB + +This procedure is initiated by the HNB-GW to close a given Iu Signalling Connection either in case of error or in case of normal operation when an Iu Signalling Connection request towards the CN is refused. + +### 8.4.4 Abnormal Conditions + +- + +## 8.5 Connectionless Transfer + +### 8.5.1 General + +This procedure is initiated by either the HNB or the HNB-GW to transfer connectionless RANAP messages between the HNB and HNB-GW. + +### 8.5.2 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing a CONNECTIONLESS TRANSFER message from HNB-GW to HNB.](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +A sequence diagram illustrating the 'Connectionless Transfer to HNB' procedure. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the 'HNB-GW' lifeline to the 'HNB' lifeline. + +Sequence diagram showing a CONNECTIONLESS TRANSFER message from HNB-GW to HNB. + +Figure 6: Connectionless Transfer to HNB + +This procedure is used to carry any DL connectionless RANAP message defined in TS 25.413 [2] from the HNB-GW to the HNB. + +### 8.5.3 Successful Operation (HNB Originated) + +![Sequence diagram showing a CONNECTIONLESS TRANSFER message from HNB to HNB-GW.](a7079ddb124df3f1ee13ae406c7c8982_img.jpg) + +A sequence diagram illustrating the 'Connectionless Transfer to HNB-GW' procedure. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the 'HNB' lifeline to the 'HNB-GW' lifeline. + +Sequence diagram showing a CONNECTIONLESS TRANSFER message from HNB to HNB-GW. + +Figure 7: Connectionless Transfer to HNB-GW + +This procedure is used to carry any UL connectionless RANAP message defined in TS 25.413 [2] from the HNB to the HNB-GW. + +### 8.5.4 Abnormal Conditions + +- + +## 8.6 Error Indication + +### 8.6.1 General + +The Error Indication procedure is initiated by either HNB or HNB-GW to report detected errors in one incoming message. + +### 8.6.2 Successful Operation + +![Sequence diagram showing Error Indication from HNB to HNB-GW.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +A sequence diagram illustrating the 'Error Indication' procedure when originated by the HNB. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a solid black rectangular bar at its base. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB lifeline to the HNB-GW lifeline. + +Sequence diagram showing Error Indication from HNB to HNB-GW. + +Figure 8 Error Indication HNB Originated, Successful Operation + +![Sequence diagram showing Error Indication from HNB-GW to HNB.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +A sequence diagram illustrating the 'Error Indication' procedure when originated by the HNB-GW. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a solid black rectangular bar at its base. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB-GW lifeline to the HNB lifeline. + +Sequence diagram showing Error Indication from HNB-GW to HNB. + +Figure 9 Error Indication HNB-GW Originated, Successful Operation + +# --- 9 Elements for RUA communication + +## 9.1 Message functional definition and content + +### 9.1.1 General + +Section 9.1 presents the contents of RUA messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [4]. + +For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message. + +### 9.1.2 Message contents + +#### 9.1.2.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 3 + +**Table 2: Meaning of abbreviations used in RUA messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| M | IE's marked as Mandatory (M) will always be included in the message. | +| O | IE's marked as Optional (O) may or may not be included in the message. | +| C | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible. + +**Table 3: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +### 9.1.3 CONNECT + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to establish a signalling connection and carry a RANAP message. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| CN Domain Indicator | M | | 9.2.6 | | YES | reject | +| Context ID | M | | 9.2.2 | | YES | reject | +| Intra Domain NAS Node Selector | O | | 9.2.4 | | YES | ignore | +| Establishment Cause | M | | 9.2.3 | | YES | reject | +| RANAP Message | M | | 9.2.5 | | YES | reject | +| CSG Membership Status | O | | 9.2.9 | | YES | ignore | + +### 9.1.4 DIRECT TRANSFER + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connection-oriented RANAP message between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| CN Domain Indicator | M | | 9.2.6 | | YES | reject | +| Context ID | M | | 9.2.2 | | YES | reject | +| RANAP Message | M | | 9.2.5 | | YES | reject | + +### 9.1.5 DISCONNECT + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to close the signaling connection between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------|--------------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| CN Domain Indicator | M | | 9.2.6 | | YES | reject | +| Context ID | M | | 9.2.2 | | YES | reject | +| Cause | M | | 9.2.7 | | YES | reject | +| RANAP Message | C - IfNormal | | 9.2.5 | | YES | reject | + +| Condition | Explanation | +|-----------|--------------------------------------------------------------| +| IfNormal | This IE shall be present if the Cause IE is set to "Normal". | + +### 9.1.6 CONNECTIONLESS TRANSFER + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connectionless RANAP message between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| RANAP Message | M | | 9.2.5 | | YES | reject | + +### 9.1.7 ERROR INDICATION + +This message is sent by either the HNB to HNB-GW or the HNB-GW to the HNB and is used to indicate that some errors have been detected. + +Direction: HNB → HNB-GW, HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Cause | M | | 9.2.7 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.8 | | YES | ignore | + +## 9.2 Information Element Definitions + +### 9.2.0 General + +Section 9.2 presents the RUA IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); +- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information; + +### 9.2.1 Message Type + +*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------| +| Message Type | | | | | +| >Procedure Code | M | | INTEGER(0..255) | | +| >Type of Message | M | | ENUMERATED
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
Outcome) | | + +### 9.2.2 Context ID + +*Context ID* IE uniquely identifies a particular UE in the HNB and HNB-GW. This unique Context ID is used for both CS and PS domain. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|----------------|-----------------------| +| Context ID | | | BIT STRING(24) | | + +### 9.2.3 Establishment Cause + +*Establishment Cause* IE identifies a the priority of call establishment + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|-------------------------------------------------------|-----------------------| +| Establishment Cause | | | ENUMERATED
(emergency call,
Normal,
...
) | | + +### 9.2.4 Intra Domain NAS Node Selector + +This IE carries information to be used to route the establishment of a signalling connection to a CN node within a CN domain. + +| IE/GROUP NAME | Presence | RANGE | IE Type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| CHOICE version | M | | | | + +| IE/GROUP NAME | Presence | RANGE | IE Type and reference | Semantics description | +|---------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >R99 | | | | This choice shall also be used by mobiles that are compliant to this version of the protocol | +| >>CHOICE CN type | M | | | | +| >>>GSM-MAP | | | | | +| >>>>CHOICE Routing basis | M | | | | +| >>>>>local (P)TMSI | | | | TMSI allocated in the current LA or PTMSI allocated in the current RA | +| >>>>>>Routing parameter | M | | Bit string (10) |

The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant

The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bit b23 of the TMSI/PTMSI.

| +| >>>>>(P)TMSI of same PLMN, different (RA)LA | | | | TMSI allocated in another LA of this PLMN or PTMSI allocated in another RA this PLMN | +| >>>>>>Routing parameter | M | | Bit string (10) |

The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant

The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bits b23 of the TMSI/ PTMSI.

| +| >>>>>(P)TMSI of different PLMN | | | | TMSI or a PTMSI allocated in another PLMN | + +| IE/GROUP NAME | Presence | RANGE | IE Type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>>>>>>Routing parameter | M | | Bit string (10) |

The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant.

The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI.

| +| >>>>>IMSI(response to IMSI paging) | | | | NAS identity is IMSI | +| >>>>>>>Routing parameter | M | | Bit string (10) |

The "Routing parameter" bit string consists of \text{DecimalToBinary}[(\text{IMSI div } 10) \bmod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result.

| +| >>>>>IMSI(cause UE initiated event) | | | | NAS identity is IMSI | +| >>>>>>>Routing parameter | M | | Bit string (10) |

The "Routing parameter" bit string consists of \text{DecimalToBinary}[(\text{IMSI div } 10) \bmod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result.

| +| >>>>>IMEI | | | | NAS parameter is IMEI | +| >>>>>>>Routing parameter | M | | Bit string (10) |

The "Routing parameter" bit string consists of \text{DecimalToBinary}[(\text{IMEI div } 10) \bmod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result.

| +| >>>>>Spare 1 | | | Bit string (10) | This choice shall not be used in this version | +| >>>>>Spare 2 | | | Bit string (10) | This choice shall not be used in this version | +| >>>ANSI-41 | | | Bit string (14) | All bits shall be set to 0 | +| >Later | | | Bit string(15) | This bit string shall not be sent by mobiles that are compliant to this version of the protocol. | + +### 9.2.5 RANAP Message + +*RANAP Message* IE contains the transferred RANAP message. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| RANAP Message | | | OCTET STRING | | + +### 9.2.6 CN Domain Indicator + +Indicates the CN domain from which the message originates or to which the message is sent. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------|-----------------------| +| CN Domain Indicator | M | | ENUMERATED (CS domain, PS domain) | | + +### 9.2.7 Cause + +*Cause* IE indicates the reason for a particular error event for the RUA protocol. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED
(
Normal,
Connect failed,
Network release,
Unspecified,
...,
) | | +| > Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED
(Transport Resource Unavailable,
Unspecified,
...) | | +| > Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely Constructed Message),
...) | | +| > Misc | | | | | +| >>Misc Cause | M | | ENUMERATED
(Processing Overload,
Hardware Failure,
O&M Intervention,
Unspecified,
...) | | + +The meaning of the different cause values is described in the following table. Cause values for information 'not valid' indicates that the information is not valid in the context that it was received. + +| Radio Network Layer cause | Meaning | +|----------------------------------|------------------------------------------------------------------------------------------------------| +| Normal | No error has occurred | +| Connect failed | Connect attempt failed | +| Network release | Connection released by network | +| Unspecified | Sent when none of the above cause values applies but still the cause is Radio Network layer related. | + +| Transport Network 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. | + +| Protocol cause | Meaning | +|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerned criticality indicated "reject". | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify" . | +| Abstract syntax error (falsely constructed message) | The received message contained IEs in wrong order or with too many occurrences. | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state. | +| Semantic Error | The received message included a semantic error. | +| Transfer Syntax Error | The received message included a transfer syntax error. | +| Unspecified | Sent when none of the above cause values applies but still the cause is protocol related. | + +| Miscellaneous cause | Meaning | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Processing Overload | Control processing overload. | +| Hardware Failure | HNB hardware failure. | +| O&M Intervention | Operation and Maintenance intervention related to HNB. | +| Unspecified | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. | + +### 9.2.8 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the RNC or the CN when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|-----------------|--------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | | | +| >Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| >Triggering Message | O | | ENUMERATED (initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|----------------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | | | +| >Procedure Criticality | O | | ENUMERATED(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0 to | | | +| >IE Criticality | M | | ENUMERATED(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | +| >IE ID | M | | INTEGER (0..65535) | The IE Id of the not understood or missing IE | +| >Type of Error | M | | ENUMERATED(not understood, missing, ...) | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------------------------| +| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxNrOfErrors is 256. | + +### 9.2.9 CSG Membership Status + +This element indicates the Membership status of the UE to a particular CSG. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------------|-----------------------| +| CSG Membership Status | M | | ENUMERATED (member, non-member,...) | | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +RUA ASN.1 definition conforms with ITU-T Rec. X.680 [7] and ITU-T Rec. X.681 [8]. + +The ASN.1 definition specifies the structure and content of RUA messages. RUA messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a RUA message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a RUA message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 10.3.6. + +### 9.3.1 Usage of private message mechanism for non-standard use + +The private message mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability; +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +RUA-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) rua(5) version1 (1) rUA-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` + +``` + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM RUA-CommonDataTypes + Connect, + DirectTransfer, + Disconnect, + ConnectionlessTransfer, + ErrorIndication, + PrivateMessage + +FROM RUA-PDU-Contents + id-Connect, + id-DirectTransfer, + id-Disconnect, + id-ConnectionlessTransfer, + id-ErrorIndication, + id-privateMessage +FROM RUA-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +RUA-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 definitions +-- +-- ***** + +``` + +``` + +RUA-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode RUA-ELEMENTARY-PROCEDURE.&procedureCode ({RUA-ELEMENTARY-PROCEDURES}), + criticality RUA-ELEMENTARY-PROCEDURE.&criticality ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value RUA-ELEMENTARY-PROCEDURE.&InitiatingMessage ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode RUA-ELEMENTARY-PROCEDURE.&procedureCode ({RUA-ELEMENTARY-PROCEDURES}), + criticality RUA-ELEMENTARY-PROCEDURE.&criticality ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value RUA-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode RUA-ELEMENTARY-PROCEDURE.&procedureCode ({RUA-ELEMENTARY-PROCEDURES}), + criticality RUA-ELEMENTARY-PROCEDURE.&criticality ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value RUA-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({RUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +RUA-ELEMENTARY-PROCEDURES RUA-ELEMENTARY-PROCEDURE ::= { + RUA-ELEMENTARY-PROCEDURES-CLASS-1 | + RUA-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +RUA-ELEMENTARY-PROCEDURES-CLASS-1 RUA-ELEMENTARY-PROCEDURE ::= { + ... +} + +RUA-ELEMENTARY-PROCEDURES-CLASS-2 RUA-ELEMENTARY-PROCEDURE ::= { + connectionRequest | + directTransfer | + disconnectRequest | + connectionlessTransfer | + errorIndication | + privateMessage, + ... +} + +-- ***** + +``` + +``` + +-- +-- Interface Elementary Procedures +-- +-- ***** + +connectionRequest RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connect + PROCEDURE CODE id-Connect + CRITICALITY ignore +} + +directTransfer RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DirectTransfer + PROCEDURE CODE id-DirectTransfer + CRITICALITY ignore +} + +disconnectRequest RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Disconnect + PROCEDURE CODE id-Disconnect + CRITICALITY ignore +} + +connectionlessTransfer RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ConnectionlessTransfer + PROCEDURE CODE id-ConnectionlessTransfer + CRITICALITY ignore +} + +errorIndication RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +privateMessage RUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +END + +``` + +### 9.3.3 PDU definitions + +``` + +-- ***** +-- +-- PDU definitions for RUA. +-- +-- ***** + +RUA-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +``` + +umts-Access (20) modules (3) rua(5) version1 (1) rUA-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- \*\*\*\*\* +-- +-- IE parameter types from other modules. +-- +-- \*\*\*\*\* + +IMPORTS + +Cause, +CriticalityDiagnostics, +Context-ID, +CN-DomainIndicator, +CSGMembershipStatus, +IntraDomainNasNodeSelector, +RANAP-Message, +Establishment-Cause + +FROM RUA-IEs + +ProtocolExtensionContainer{}, +ProtocolIE-ContainerList{}, +ProtocolIE-Container{}, +ProtocolIE-Single-Container{}, +PrivateIE-Container{}, +RUA-PRIVATE-IEs, +RUA-PROTOCOL-EXTENSION, +RUA-PROTOCOL-IEs + +FROM RUA-Containers + +id-Cause, +id-CriticalityDiagnostics, +id-Context-ID, +id-CN-DomainIndicator, +id-CSGMembershipStatus, +id-RANAP-Message, +id-IntraDomainNasNodeSelector, +id-Establishment-Cause + +FROM RUA-Constants; + +-- \*\*\*\*\* +-- +-- Connect +-- +-- \*\*\*\*\* + +Connect ::= SEQUENCE { +    protocolIEs           ProtocolIE-Container           { {ConnectIEs} }, + +``` + + protocolExtensions ProtocolExtensionContainer { {ConnectExtensions} } OPTIONAL, + ... +} + +ConnectIEs RUA-PROTOCOL-IES ::= { + { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator PRESENCE mandatory } | + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-IntraDomainNasNodeSelector CRITICALITY ignore TYPE IntraDomainNasNodeSelector PRESENCE optional } | + { ID id-Establishment-Cause CRITICALITY reject TYPE Establishment-Cause PRESENCE mandatory } | + { ID id-RANAP-Message CRITICALITY reject TYPE RANAP-Message PRESENCE mandatory }, + ... +} + +ConnectExtensions RUA-PROTOCOL-EXTENSION ::= { + { ID id-CSGMembershipStatus CRITICALITY ignore EXTENSION CSGMembershipStatus PRESENCE optional }, + ... +} + +``` + +``` + +-- ************************************************************** +-- +-- Direct Transfer +-- +-- ************************************************************** + +``` + +``` + +DirectTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DirectTransferIEs} }, + protocolExtensions ProtocolExtensionContainer { {DirectTransferExtensions} } OPTIONAL, + ... +} + +``` + +``` + +DirectTransferIEs RUA-PROTOCOL-IES ::= { + { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator PRESENCE mandatory } | + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-RANAP-Message CRITICALITY reject TYPE RANAP-Message PRESENCE mandatory }, + ... +} + +``` + +``` + +DirectTransferExtensions RUA-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ************************************************************** +-- +-- Disconnect +-- +-- ************************************************************** + +``` + +``` + +Disconnect ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DisconnectIEs} }, + protocolExtensions ProtocolExtensionContainer { {DisconnectExtensions} } OPTIONAL, + ... +} + +``` + +``` + +} + +DisconnectIEs RUA-PROTOCOL-IES ::= { + { ID id-CN-DomainIndicator CRITICALITY reject TYPE CN-DomainIndicator PRESENCE mandatory } | + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory } | + { ID id-RANAP-Message CRITICALITY reject TYPE RANAP-Message PRESENCE conditional }, + -- RANAP message shall be included if Cause value is "normal" + ... +} + +DisconnectExtensions RUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Connectionless Transfer +-- +-- ***** + +ConnectionlessTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ConnectionlessTransferIEs} }, + protocolExtensions ProtocolExtensionContainer { {ConnectionlessTransferExtensions} } OPTIONAL, + ... +} + +ConnectionlessTransferIEs RUA-PROTOCOL-IES ::= { + { ID id-RANAP-Message CRITICALITY reject TYPE RANAP-Message PRESENCE mandatory }, + ... +} + +ConnectionlessTransferExtensions RUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- ERROR INDICATION +-- +-- ***** + +ErrorIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ErrorIndicationIEs} }, + protocolExtensions ProtocolExtensionContainer { {ErrorIndicationExtensions} } OPTIONAL, + ... +} + +ErrorIndicationIEs RUA-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- A - 5 +} + +ErrorIndicationExtensions RUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- PRIVATE MESSAGE +-- +-- ***** + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container {{PrivateMessage-IEs}}, + ... +} + +PrivateMessage-IEs RUA-PRIVATE-IES ::= { + ... +} + +END + +``` + +### 9.3.4 Information Element definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +RUA-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) rua(5) version1 (1) rUA-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors +FROM RUA-Constants + + Criticality, + ProcedureCode, + ProtocolIE-ID, + TriggeringMessage +FROM RUA-CommonDataTypes + + ProtocolExtensionContainer{}, + RUA-PROTOCOL-EXTENSION + +``` + +----- + +FROM RUA-Containers; + +CN-DomainIndicator ::= ENUMERATED { + +    cs-domain, +     ps-domain + +} + +CSGMembershipStatus ::= ENUMERATED { + +    member, +     non-member, +     ... + +} + +Establishment-Cause ::= ENUMERATED { +     emergency-call, +     normal-call, +     ... + } + +Context-ID ::= BIT STRING (SIZE(24)) + +IntraDomainNasNodeSelector ::= +     version +         release99 +             cn-Type +                 gsm-Map-IDNNS +                 ansi-41-IDNNS +             } +         }, +         later +             futurecoding +         } +     } + } + +SEQUENCE { +     CHOICE { +         SEQUENCE { +             CHOICE { +                 Gsm-map-IDNNS, +                 Ansi-41-IDNNS +             } +         } +         SEQUENCE { +             BIT STRING (SIZE (15)) +         } +     } + } + +Gsm-map-IDNNS ::= +     routingbasis +         localPTMSI +             routingparameter +         }, +         tMSIoOfsamePLMN +             routingparameter +         }, +         tMSIoOfdifferentPLMN +             routingparameter +         }, +         iMSIresponsetopaging +             routingparameter +         }, +         iMSIcauseUEinitiatedEvent + +SEQUENCE { +     CHOICE { +         SEQUENCE { +             RoutingParameter +         } +         SEQUENCE { +             RoutingParameter +         } +         SEQUENCE { +             RoutingParameter +         } +         SEQUENCE { +             RoutingParameter +         } +         SEQUENCE { + +``` + +-- A-5 + routingparameter RoutingParameter + }, + iMEI SEQUENCE { + routingparameter RoutingParameter + }, + spare2 SEQUENCE { + routingparameter RoutingParameter + }, + spare1 SEQUENCE { + routingparameter RoutingParameter + } +}, +-- dummy is not used in this version of the specification and +-- it should be ignored by the receiver. +dummy BOOLEAN +} + +``` + +``` +Ansi-41-IDNNS ::= BIT STRING (SIZE (14)) +``` + +``` +RANAP-Message ::= OCTET STRING +``` + +``` +RoutingParameter ::= BIT STRING (SIZE (10)) +``` + +``` + +-- ***** +-- +-- Cause IE +-- +-- ***** + +``` + +``` + +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + ... +} + +``` + +``` + +CauseRadioNetwork ::= ENUMERATED { + normal, + connect-failed, + network-release, + unspecified, + ... +} + +``` + +``` + +CauseTransport ::= ENUMERATED { + transport-resource-unavailable, + unspecified, + ... +} + +``` + +``` + +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, + abstract-syntax-error-ignore-and-notify, + +``` + +``` + +... if +message-not-compatible-with-receiver-state, +semantic-error, +unspecified, +abstract-syntax-error-falsely-constructed-message, +... +} + +CauseMisc ::= ENUMERATED { +processing-overload, +hardware-failure, +o-and-m-intervention, +unspecified, +... +} + +-- ***** +-- +-- CriticalityDiagnostics +-- +-- ***** + +CriticalityDiagnostics ::= SEQUENCE { +procedureCode ProcedureCode OPTIONAL, +triggeringMessage TriggeringMessage OPTIONAL, +procedureCriticality Criticality OPTIONAL, +iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, +iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, +... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF +SEQUENCE { +iECriticality Criticality, +iE-ID ProtocolIE-ID, +typeOfError TypeOfError, +iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, +... +} + +CriticalityDiagnostics-IE-List-ExtIEs RUA-PROTOCOL-EXTENSION ::= { +... +} + +CriticalityDiagnostics-ExtIEs RUA-PROTOCOL-EXTENSION ::= { +... +} + +TypeOfError ::= ENUMERATED { +not-understood, +missing, +... +} + +END + +``` + +### 9.3.5 Common definitions + +``` + +-- ***** +-- +-- Common definitions +-- +-- ***** + +RUA-CommonDataTypes { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) rua(5) version1 (1) rUA-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- Extension constants +-- +-- ***** + +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ***** +-- +-- Common Data Types +-- +-- ***** +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +PrivateIE-ID ::= CHOICE { + local INTEGER (0..65535), + global OBJECT IDENTIFIER +} + +ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs) + +TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome } + +END + +``` + +### 9.3.6 Constant definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +RUA-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) rua(5) version1 (1) rUA-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + + IMPORTS + ProcedureCode, + ProtocolIE-ID + FROM RUA-CommonDataTypes; + +-- ***** +-- +-- Elementary Procedures +-- + id-Connect ProcedureCode ::= 1 + id-DirectTransfer ProcedureCode ::= 2 + id-Disconnect ProcedureCode ::= 3 + id-ConnectionlessTransfer ProcedureCode ::= 4 + id-ErrorIndication ProcedureCode ::= 5 + id-privateMessage ProcedureCode ::= 6 + +-- ***** +-- +-- Lists +-- +-- ***** + maxNrOfErrors INTEGER ::= 256 + +-- ***** +-- +-- IEs +-- +-- ***** + + id-Cause ProtocolIE-ID ::= 1 + id-CriticalityDiagnostics ProtocolIE-ID ::= 2 + id-Context-ID ProtocolIE-ID ::= 3 + id-RANAP-Message ProtocolIE-ID ::= 4 + id-IntraDomainNasNodeSelector ProtocolIE-ID ::= 5 + id-Establishment-Cause ProtocolIE-ID ::= 6 + id-CN-DomainIndicator ProtocolIE-ID ::= 7 + +``` + +id-CSGMembershipStatus                                ProtocolIE-ID ::= 9 + +END + +### 9.3.7 Container definitions + +``` + +-- ************************************************************** +-- +-- Container definitions +-- +-- ************************************************************** + +RUA-Containers { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) rua(5) version1 (1) rUA-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- IE parameter types from other modules. +-- +-- ************************************************************** + +IMPORTS + Criticality, + Presence, + PrivateIE-ID, + ProtocolIE-ID, + maxPrivateIEs, + maxProtocolExtensions, + maxProtocolIEs +FROM RUA-CommonDataTypes; + +-- ************************************************************** +-- +-- Class Definition for Private IEs +-- +-- ************************************************************** + +RUA-PRIVATE-IES ::= CLASS { + &id PrivateIE-ID, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality +} + +``` + +``` + + TYPE &Value + PRESENCE &presence +} + +-- ************************************************************** +-- +-- Class Definition for Protocol IEs +-- +-- ************************************************************** + +RUA-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ************************************************************** +-- +-- Class Definition for Protocol Extensions +-- +-- ************************************************************** + +RUA-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ************************************************************** +-- +-- Container for Protocol IEs +-- +-- ************************************************************** + +ProtocolIE-Container {RUA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Single-Container {RUA-PROTOCOL-IES : IEsSetParam} ::= + +``` + +``` + +ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {RUA-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id RUA-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality RUA-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value RUA-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, RUA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {RUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {RUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id RUA-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}}, + criticality RUA-PROTOCOL-EXTENSION.&criticality {{ExtensionSetParam}{@id}}, + extensionValue RUA-PROTOCOL-EXTENSION.&Extension {{ExtensionSetParam}{@id}} +} + +-- ***** +-- +-- Container for Private IEs +-- +-- ***** + +PrivateIE-Container {RUA-PRIVATE-IES : IEsSetParam } ::= + SEQUENCE (SIZE (1.. maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field {RUA-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id RUA-PRIVATE-IES.&id {{IEsSetParam}}, + criticality RUA-PRIVATE-IES.&criticality {{IEsSetParam}{@id}}, + value RUA-PRIVATE-IES.&Value {{IEsSetParam}{@id}} +} + +``` + +END + +## 9.4 Message transfer syntax + +RUA shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [6]. + +# 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 RUA. It shows two boxes: 'RUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large upward-pointing arrow is on the far right.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +``` + +graph TD + subgraph RUA_errors [ ] + LE[Logical Errors] + ASE[Abstract Syntax Errors] + end + subgraph ASN1_errors [ ] + TSE[Transfer Syntax Errors] + end + RUA[RUA functional entity] --- LE + RUA --- ASE + ASN1[ASN.1 Decoding] --- TSE + ASN1 <--> RUA + style RUA_errors fill:none,stroke:none + style ASN1_errors fill:none,stroke:none + +``` + +Diagram illustrating protocol errors in RUA. It shows two boxes: 'RUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large upward-pointing arrow is on the far right. + +**Figure 10: Protocol errors in RUA** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional RUA entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE id); +2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the RUA messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE; +- Ignore IE and Notify Sender; +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, RUA 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 RUA-PROTOCOL-IES, RUA-PROTOCOL-IES-PAIR, RUA-PROTOCOL-EXTENSION or RUA-PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following: + +Reject IE: + +- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +Ignore IE and Notify Sender: + +- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +Ignore IE: + +- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +#### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +#### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +Reject IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +##### Ignore IE and Notify Sender: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +##### Ignore IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +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 the present document used by the receiver: + +#### Reject IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +#### Ignore IE and Notify Sender: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +#### Ignore IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +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 IE's/IE groups containing the erroneous values. + +### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error; +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|-----------------------------------------------------------------|--------| +| 2008-12 | RP-080833 | | | Approved at TSG-RAN#42 and placed under change control | 8.0.0 | +| 2009-01 | | | | Editorial corrections, including spec number shown on cover | 8.0.1 | +| 43 | RP-090244 | 0001 | | Add Object Identifier for RUA ASN.1 | 8.1.0 | +| 43 | RP-090081 | 0004 | 1 | Clarification on Uniqueness of Context ID | 8.1.0 | +| 43 | RP-090082 | 0007 | 2 | Adding the definition of Iuh Signalling Connection | 8.1.0 | +| 43 | RP-090244 | 0008 | | Correction of IE presence in ASN.1 | 8.1.0 | +| 43 | RP-090244 | 0009 | | Clarification of operation of RUA disconnect | 8.1.0 | +| 46 | | | | Raised to version 9.0.0 | 9.0.0 | +| 46 | RP-091191 | 0020 | 1 | RUA enhancement to handle inbound Mobility | 9.0.0 | +| 46 | RP-091191 | 0021 | 2 | CSG Membership signalling during UE implicit registration | 9.0.0 | +| 47 | RP-100230 | 0023 | 1 | Minor corrections for RUA | 9.1.0 | +| 48 | RP-100595 | 0029 | 1 | Some Clarifications on RUA Direct Transfer | 9.2.0 | +| 49 | RP-100909 | 0030 | 1 | Add missing cause value descriptions | 9.3.0 | +| 03/2011 | | | | Raised to version 10.0.0 | 10.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.0 | +| 51 | RP-110231 | 0033 | 1 | RUA Connect Message for Enhanced H2H Mobility | 10.0.0 | +| 52 | RP-110684 | 0034 | 1 | Correction of References | 10.1.0 | +| 52 | RP-110689 | 0035 | 1 | IDNNS usage in the CONNECT message | 10.1.0 | +| 52 | RP-110689 | 0036 | 2 | Clarification of usage of RUA DISCONNECT | 10.1.0 | +| 53 | RP-111192 | 0040 | 1 | Remaining UE Context Issue during Mobility | 10.2.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 58 | RP-121737 | 0041 | | Editorial and minor corrections | 11.1.0 | +| 59 | RP-130211 | 0042 | | Corrections from ASN.1 Review | 11.2.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 66 | RP-142093 | 0047 | | Update of reference | 12.1.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | +| 71 | RP-160419 | 0049 | | Correction of tabular for Procedure Code in the Message Type IE | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25469/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Rel-16/25_series/25469/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10ed9c0ef1f91a0ba8d69aa0c6edd79ded266ed5 --- /dev/null +++ b/marked/Rel-16/25_series/25469/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1175abaa055321a293f5c1fe622da12303b1a17481c25bb78a0b3204b2cffc59 +size 15496 diff --git a/marked/Rel-16/25_series/25469/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25469/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62355cce999c254fc05fe5f86e859132d037f8b0 --- /dev/null +++ b/marked/Rel-16/25_series/25469/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fed14bc553fb0c83b2c093079a6f52c3f68bb7c214ae6516a83c1e3cdfc65f2 +size 14676 diff --git a/marked/Rel-16/25_series/25469/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-16/25_series/25469/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f7283e70dd9fa07f561093b122762018a14756 --- /dev/null +++ b/marked/Rel-16/25_series/25469/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23b69b16bed2a56dd294153e95291f0e3f6e0f04102b224e2ab72a758b393714 +size 19780 diff --git a/marked/Rel-16/25_series/25469/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/Rel-16/25_series/25469/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54cc6489af5cfa1c568fa578718591253a695e06 --- /dev/null +++ b/marked/Rel-16/25_series/25469/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e0821d3c0ba7546581eb8f4dd91222ec65676164132c78fb96725a1765a2db +size 19034 diff --git a/marked/Rel-16/25_series/25469/3597664ae86918629ceabb89ae71669d_img.jpg b/marked/Rel-16/25_series/25469/3597664ae86918629ceabb89ae71669d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45db68ad2e9bb0b6f043bd8e5aaa9c7ba227a4c7 --- /dev/null +++ b/marked/Rel-16/25_series/25469/3597664ae86918629ceabb89ae71669d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99643eae9b740770e9c8dbf4ec6ca300fc281bdf79b3e6a16038fb2ff6623c3b +size 18647 diff --git a/marked/Rel-16/25_series/25469/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/25_series/25469/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98f6026d9384a106558736e896aedb2f4bc1bd1f --- /dev/null +++ b/marked/Rel-16/25_series/25469/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53717ea56baa026f778775806ebfbfd077bb653ae25ebc44029b58b668a782d5 +size 22604 diff --git a/marked/Rel-16/25_series/25469/453a1dc18dd2dd3334d19f453b04d11b_img.jpg b/marked/Rel-16/25_series/25469/453a1dc18dd2dd3334d19f453b04d11b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86f6651e78880594f9185df01bfe61133c2a426d --- /dev/null +++ b/marked/Rel-16/25_series/25469/453a1dc18dd2dd3334d19f453b04d11b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:087e5ac5ae280344c2d996da252b24516f1cbedee33099a1bc692c5822416bc7 +size 22654 diff --git a/marked/Rel-16/25_series/25469/57f8e374b0e99c488f68c46b713ffc64_img.jpg b/marked/Rel-16/25_series/25469/57f8e374b0e99c488f68c46b713ffc64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..166bcdc6e001fd5465f446ae0def03c76d55125b --- /dev/null +++ b/marked/Rel-16/25_series/25469/57f8e374b0e99c488f68c46b713ffc64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2484d0e0e0ddb45b5fc7104e34756de8040b9723a7d9257b1254ebb2f46885a +size 14478 diff --git a/marked/Rel-16/25_series/25469/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/25_series/25469/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36fffd6592e28864c95dc8458575937fbe6f99f4 --- /dev/null +++ b/marked/Rel-16/25_series/25469/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d13861e140dfba3c05da1f882f9d04394bb93ceacd1dce3705d0737126931245 +size 14949 diff --git a/marked/Rel-16/25_series/25469/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/25_series/25469/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67bfaad79e09fc4d42c5bd3ba7490dd3cc82b0b6 --- /dev/null +++ b/marked/Rel-16/25_series/25469/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be4192985f21ae3bdac7b3513bf5a51565285a805dba696984e1c8795aa2b96b +size 14506 diff --git a/marked/Rel-16/25_series/25469/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-16/25_series/25469/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63690a255acbba623d357e06485389f5fb16a5e --- /dev/null +++ b/marked/Rel-16/25_series/25469/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4abd71b663ec5406c96562cf2ea039b75ab1390841328137c299a847726d4dd4 +size 14539 diff --git a/marked/Rel-16/25_series/25469/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/marked/Rel-16/25_series/25469/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a47a66988b13516ec9578d88456cb681ef8a96f6 --- /dev/null +++ b/marked/Rel-16/25_series/25469/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba733115de2b422dfddbde19695e6ca183f31c36c549d5125fe7858d6cf21390 +size 14446 diff --git a/marked/Rel-16/25_series/25469/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-16/25_series/25469/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8300573ac84ab0e483ff15e607e2bdfbe183645c --- /dev/null +++ b/marked/Rel-16/25_series/25469/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb4c2395b6e064666e1fdcf7ecae44ecd648d7df139b34e1b1228360a5211fa8 +size 18847 diff --git a/marked/Rel-16/25_series/25469/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Rel-16/25_series/25469/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5758b745fd681b30bce7a90c4d3296d31b1a1366 --- /dev/null +++ b/marked/Rel-16/25_series/25469/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee4f4725e64af4f7e10b348374c2291b388a5b83d2f0f3335ed845ff22cecdb5 +size 18971 diff --git a/marked/Rel-16/25_series/25469/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/25_series/25469/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6326f6af50f95db43ca80c524a08e93d52a6414 --- /dev/null +++ b/marked/Rel-16/25_series/25469/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5015fdd9191205f64ba54d31623d1cb76caad1b5d3e76229cf8c8b789ad47e9 +size 20820 diff --git a/marked/Rel-16/25_series/25469/e190b6ddb7c2e64b940749a1c5612256_img.jpg b/marked/Rel-16/25_series/25469/e190b6ddb7c2e64b940749a1c5612256_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55d2b475b62810730a5a8f72ccce4fee47bb7eb6 --- /dev/null +++ b/marked/Rel-16/25_series/25469/e190b6ddb7c2e64b940749a1c5612256_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9352196d814a02892f7651cf7a818ae17fcebd3772fd3fd8e78b0f0d69e7921f +size 14195 diff --git a/marked/Rel-16/25_series/25469/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-16/25_series/25469/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d9541038527935a6b0c48e8c1fa3fade23d29c5 --- /dev/null +++ b/marked/Rel-16/25_series/25469/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dbdc5d73a0410b356bb4922aa774cde3173ee5c66e0f31f2c9f1c5c267a0f14 +size 20071 diff --git a/marked/Rel-16/25_series/25469/raw.md b/marked/Rel-16/25_series/25469/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b25150f2ea40bde111864937b377f9b74609a3d6 --- /dev/null +++ b/marked/Rel-16/25_series/25469/raw.md @@ -0,0 +1,3798 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 4.1 Procedure Specification Principles..... | 8 | +| 4.2 Forwards and Backwards Compatibility..... | 9 | +| 4.3 Specification Notations ..... | 9 | +| 5 HNBAP Services..... | 9 | +| 6 Services expected from the Transport layer..... | 9 | +| 7 Functions of HNBAP ..... | 10 | +| 8 HNBAP Procedures ..... | 10 | +| 8.1 Elementary Procedures..... | 10 | +| 8.2 HNB Registration Procedure..... | 10 | +| 8.2.1 General ..... | 10 | +| 8.2.2 Successful Operation..... | 11 | +| 8.2.3 Unsuccessful Operation..... | 12 | +| 8.2.4 Abnormal Conditions ..... | 12 | +| 8.3 HNB De-registration Procedure..... | 12 | +| 8.3.1 Successful Operation (HNB Originated)..... | 12 | +| 8.3.2 Successful Operation (HNB-GW Originated)..... | 13 | +| 8.3.3 Abnormal Conditions ..... | 13 | +| 8.4 UE Registration..... | 13 | +| 8.4.1 General ..... | 13 | +| 8.4.2 Successful Operation..... | 14 | +| 8.4.3 Unsuccessful Operation..... | 14 | +| 8.4.4 Abnormal Conditions ..... | 15 | +| 8.5 UE De-Registration..... | 15 | +| 8.5.1 General ..... | 15 | +| 8.5.2 Successful Operation (HNB Originated)..... | 15 | +| 8.5.3 Successful Operation (HNB-GW Originated)..... | 15 | +| 8.5.4 Abnormal Conditions ..... | 16 | +| 8.6 Error Indication ..... | 16 | +| 8.6.1 General ..... | 16 | +| 8.6.2 Successful Operation..... | 16 | +| 8.7 CSG Membership Update Procedure ..... | 17 | +| 8.7.1 Successful Operation..... | 17 | +| 8.7.2 Abnormal Conditions ..... | 17 | +| 8.8 Void..... | 17 | +| 8.8.1 Void..... | 17 | +| 8.8.2 Void..... | 17 | +| 8.8.3 Void..... | 17 | +| 8.9 TNL Update..... | 17 | +| 8.9.1 General ..... | 17 | +| 8.9.2 Successful Operation..... | 18 | +| 8.9.3 Unsuccessful Operation..... | 18 | +| 8.9.4 Abnormal Conditions ..... | 18 | +| 8.10 HNB Configuration Transfer Procedure ..... | 18 | +| 8.10.1 General ..... | 18 | +| 8.10.2 Successful Operation..... | 18 | +| 8.10.3 Void..... | 19 | +| 8.10.4 Abnormal Conditions ..... | 19 | + +| | | | +|---------|-----------------------------------------------|----| +| 8.11 | Relocation Complete..... | 19 | +| 8.11.1 | General ..... | 19 | +| 8.11.2 | Successful Operation..... | 20 | +| 8.12 | U-RNTI Query ..... | 20 | +| 8.12.1 | General ..... | 20 | +| 8.12.2 | Successful Operation..... | 20 | +| 9 | Elements for HNBAP Communication..... | 20 | +| 9.1 | Message Functional Definiton and Content..... | 20 | +| 9.1.1 | General ..... | 20 | +| 9.1.2 | Message Contents..... | 21 | +| 9.1.2.1 | Presence ..... | 21 | +| 9.1.2.2 | Criticality ..... | 21 | +| 9.1.2.3 | Range ..... | 21 | +| 9.1.2.4 | Assigned Criticality ..... | 21 | +| 9.1.3 | HNB REGISTER REQUEST..... | 21 | +| 9.1.4 | HNB REGISTER ACCEPT ..... | 22 | +| 9.1.5 | HNB REGISTER REJECT ..... | 23 | +| 9.1.6 | UE REGISTER REQUEST..... | 23 | +| 9.1.7 | UE REGISTER ACCEPT ..... | 23 | +| 9.1.8 | UE REGISTER REJECT ..... | 23 | +| 9.1.9 | HNB DE-REGISTER..... | 24 | +| 9.1.10 | UE DE-REGISTER..... | 24 | +| 9.1.11 | ERROR INDICATION ..... | 24 | +| 9.1.12 | CSG MEMBERSHIP UPDATE..... | 24 | +| 9.1.13 | Void..... | 25 | +| 9.1.14 | Void..... | 25 | +| 9.1.15 | TNL UPDATE REQUEST..... | 25 | +| 9.1.16 | TNL UPDATE RESPONSE..... | 25 | +| 9.1.17 | TNL UPDATE FAILURE..... | 25 | +| 9.1.18 | HNB CONFIGURATION TRANSFER REQUEST ..... | 25 | +| 9.1.19 | HNB CONFIGURATION TRANSFER RESPONSE ..... | 26 | +| 9.1.20 | Void..... | 26 | +| 9.1.21 | RELOCATION COMPLETE ..... | 26 | +| 9.1.22 | U-RNTI QUERY REQUEST..... | 27 | +| 9.1.23 | U-RNTI QUERY RESPONSE..... | 27 | +| 9.2 | Information Element Definitions ..... | 27 | +| 9.2.0 | General ..... | 27 | +| 9.2.1 | Message Type..... | 28 | +| 9.2.2 | HNB Identity ..... | 28 | +| 9.2.3 | HNB Location Information ..... | 28 | +| 9.2.4 | Geographical Location ..... | 28 | +| 9.2.5 | Geographical Coordinates ..... | 29 | +| 9.2.6 | Altitude and Direction ..... | 29 | +| 9.2.7 | Macro Coverage Information ..... | 29 | +| 9.2.8 | IP Address ..... | 30 | +| 9.2.9 | Context-ID..... | 30 | +| 9.2.10 | IMSI..... | 30 | +| 9.2.11 | LAC ..... | 31 | +| 9.2.12 | RAC..... | 31 | +| 9.2.13 | SAC ..... | 31 | +| 9.2.14 | PLMN-ID ..... | 31 | +| 9.2.15 | Cause ..... | 32 | +| 9.2.16 | Criticality Diagnostics..... | 34 | +| 9.2.17 | UE Identity ..... | 35 | +| 9.2.18 | IMEI ..... | 36 | +| 9.2.19 | TMSI (GSM-MAP) ..... | 36 | +| 9.2.20 | LAI ..... | 36 | +| 9.2.21 | Registration Cause..... | 37 | +| 9.2.22 | P-TMSI (GSM-MAP)..... | 37 | +| 9.2.23 | Routing Area Identification..... | 37 | +| 9.2.24 | UE Capabilities..... | 37 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------|-----------| +| 9.2.25 | Cell-ID ..... | 37 | +| 9.2.26 | RNC-ID ..... | 38 | +| 9.2.27 | CSG-ID ..... | 38 | +| 9.2.28 | Backoff Timer ..... | 38 | +| 9.2.29 | Mux Port Number ..... | 38 | +| 9.2.30 | CSG Membership Status ..... | 38 | +| 9.2.31 | HNB Cell Access Mode ..... | 38 | +| 9.2.32 | RAB List ..... | 39 | +| 9.2.33 | Transport Info ..... | 39 | +| 9.2.34 | Transport Layer Address ..... | 39 | +| 9.2.35 | Transport Association ..... | 39 | +| 9.2.36 | HNB RNL Identity ..... | 40 | +| 9.2.37 | CN Domain Indicator ..... | 40 | +| 9.2.38 | Void ..... | 40 | +| 9.2.39 | Update Cause ..... | 40 | +| 9.2.40 | HNB Configuration Information ..... | 40 | +| 9.2.41 | PSC ..... | 41 | +| 9.2.42 | HNB Cell Identifier ..... | 41 | +| 9.2.43 | RAB ID ..... | 41 | +| 9.2.44 | Tunnel Information ..... | 42 | +| 9.2.45 | CELL_FACH Mobility Support ..... | 42 | +| 9.2.46 | S-RNTI Prefix ..... | 42 | +| 9.2.47 | URA Identity ..... | 42 | +| 9.2.48 | U-RNTI ..... | 42 | +| 9.2.49 | Unknown U-RNTI Indication ..... | 42 | +| 9.2.50 | HNB Capacity ..... | 43 | +| 9.2.51 | Neighbour Identity ..... | 43 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1) ..... | 43 | +| 9.3.0 | General ..... | 43 | +| 9.3.1 | Usage of private message mechanism for non-standard use ..... | 43 | +| 9.3.2 | Elementary Procedure Definitions ..... | 45 | +| 9.3.3 | PDU Definitions ..... | 49 | +| 9.3.4 | Information Element Definitions ..... | 60 | +| 9.3.5 | Common Definitions ..... | 71 | +| 9.3.6 | Constant Definitions ..... | 72 | +| 9.3.7 | Container Definitions ..... | 74 | +| 9.4 | Message Transfer Syntax ..... | 78 | +| 10 | Handling of unknown, unforeseen, and erroneous protocol data ..... | 78 | +| 10.1 | General ..... | 78 | +| 10.2 | Transfer Syntax Error ..... | 78 | +| 10.3 | Abstract Syntax Error ..... | 78 | +| 10.3.1 | General ..... | 78 | +| 10.3.2 | Criticality Information ..... | 79 | +| 10.3.3 | Presence Information ..... | 79 | +| 10.3.4 | Not comprehended IE/IE group ..... | 80 | +| 10.3.4.1 | Procedure Code ..... | 80 | +| 10.3.4.1A | Type of Message ..... | 80 | +| 10.3.4.2 | IEs other than the Procedure Code and Type of Message ..... | 80 | +| 10.3.5 | Missing IE or IE group ..... | 81 | +| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 82 | +| 10.4 | Logical Error ..... | 83 | +| 10.5 | Exceptions ..... | 83 | +| Annex A (informative): | Change History ..... | 84 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the *Home Node B Application Part (HNBAP)* between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils the HNB- HNB-GW communication requirements specified in TS 25.467 [3] and is defined over the Iuh – reference point. It provides control and management procedures between HNB and HNB-GW. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] Void +- [3] 3GPP TS 25.467: “UTRAN architecture for 3G Home Node B” +- [4] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [5] 3GPP TR 25.921 (Version 7.0.0): "Guidelines and Principles for Protocol Description and Error Handling". +- [6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [7] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [8] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [10] 3GPP TS 25.331: “Radio Resource Control (RRC) Protocol Specification” +- [11] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". +- [12] 3GPP TS 23.003: "Numbering, addressing and identification". +- [13] IETF RFC 4282 (2005-12): "The Network Access Identifier". +- [14] Broadband Forum TR-069 Amendment 2, *CPE WAN Management Protocol*, Broadband Forum Technical Report, 2007. +- [15] 3GPP TS 22.220: "Service requirements for Home Node Bs and Home eNode Bs". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [6] and the following terms and definitions apply: + +**Elementary Procedure:** HNBAP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the HNB and HNB-GW. These EPs are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand-alone procedures, which can be active in parallel. + +An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure). +- **Class 2:** Elementary Procedures without response. + +For Class 1 EPs, the types of responses can be as follows: + +### Successful + +- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. + +### Unsuccessful + +- A signalling message explicitly indicates that the EP failed. +- On time supervision expiry (i.e. absence of expected response). + +Class 2 EPs are considered always successful. + +**RNSAP Relocation:** see definition in TS 25.467 [3]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [6] and the following abbreviations apply: + +| | | +|--------|--------------------------| +| EP | Elementary Procedure | +| ESN | Electronic Serial Number | +| HNB | Home Node B | +| HNB-GW | Home Node B Gateway | +| HNBAP | HNB Application Part | +| PDU | Protocol Data Unit | +| PER | Packed Encoding Rules | +| SAC | Service Area Code | + +# --- 4 General + +The protocol described in the present document is the protocol between HNB-GW and HNB. + +## 4.1 Procedure Specification Principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the HNB & HNB-GW exactly and completely. + +The following specification principles have been applied for the procedure text in clause 8: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + +2) Functionality which "shall, if supported" be executed: + +- The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. + +## 4.2 Forwards and Backwards Compatibility + +The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. HNB Registration 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. HNB REGISTRATION REQUEST message. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. HNB Identity IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g., "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 HNBAP Services + +HNBAP provides the signalling service between the HNB and the HNB-GW that is required to fulfil the HNBAP functions in Clause 7. + +# --- 6 Services expected from the Transport layer + +Following service is expected from the transport layer: + +- reliable and in sequence delivery of HNBAP messages. HNBAP shall be notified if the signalling connection breaks. + +# --- 7 Functions of HNBAP + +The HNBAP has the following functions: + +- HNB Registration +- UE Registration +- Support RNSAP relocation (TS 25.467 [3]) +- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined. + +These functions are implemented by one or several HNBAP elementary procedures described in the following clauses. + +# 8 HNBAP Procedures + +## 8.1 Elementary Procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 Procedures. + +**Table 1: Class 1** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|----------------------------|------------------------------------|-------------------------------------|----------------------| +| | | Response message | Response message | +| HNB Registration | HNB REGISTER REQUEST | HNB REGISTER ACCEPT | HNB REGISTER REJECT | +| UE Registration | UE REGISTER REQUEST | UE REGISTER ACCEPT | UE REGISTER REJECT | +| TNL Update | TNL UPDATE REQUEST | TNL UPDATE RESPONSE | TNL UPDATE FAILURE | +| HNB Configuration Transfer | HNB CONFIGURATION TRANSFER REQUEST | HNB CONFIGURATION TRANSFER RESPONSE | | + +**Table 2: Class 2** + +| Elementary Procedure | Message | +|-----------------------|-----------------------| +| HNB De-Registration | HNB DE-REGISTER | +| UE De-Registration | UE DE-REGISTER | +| Error Indication | ERROR INDICATION | +| CSG Membership Update | CSG MEMBERSHIP UPDATE | +| Relocation Complete | RELOCATION COMPLETE | + +## 8.2 HNB Registration Procedure + +### 8.2.1 General + +The purpose of the HNB Registration Procedure is to register the HNB with the HNB-GW to enable the HNB-GW to provide service and core network connectivity for the HNB and if supported and configured, to enable Iuh connectivity via/to the HNB-GW. This procedure shall be the first HNBAP procedure triggered after the Iuh signalling transport has been successfully established. + +### 8.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the HNB Register Procedure. The HNB sends an HNB REGISTER REQUEST message to the HNB-GW, and the HNB-GW responds with an HNB REGISTER ACCEPT message.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: HNB REGISTER REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: HNB REGISTER ACCEPT + Note left of HNB: + +``` + +Sequence diagram showing the successful operation of the HNB Register Procedure. The HNB sends an HNB REGISTER REQUEST message to the HNB-GW, and the HNB-GW responds with an HNB REGISTER ACCEPT message. + +**Figure 8.2.2-1: HNB Register Procedure: Successful Operation** + +The HNB shall initiate this procedure by sending a HNB REGISTER REQUEST message whenever it needs to commence operations and requiring service from the HNB-GW. + +If the HNB is CSG capable and operates in a Closed access mode as defined in TS 22.220 [15], then it shall provide the *CSG-ID IE* and may provide the *HNB Cell Access Mode IE* within the HNB REGISTER REQUEST message. + +If the HNB is supporting PWS it shall provide the *Service Area For Broadcast IE* within the HNB REGISTER REQUEST message. + +If the HNB operates in a Hybrid access mode as defined in TS 22.220 [15], then it shall provide the *CSG-ID* IE and *HNB Cell Access Mode* IE within the HNB REGISTER REQUEST message. + +If the HNB operates in an Open access mode as defined in TS 22.220 [15], then it shall provide the *HNB Cell Access Mode* IE within the HNB REGISTER REQUEST message. + +If the HNB supports direct Iurh connectivity it shall provide the *Iurh signalling TNL Address* IE to the HNB-GW within the HNB REGISTER REQUEST message. + +If supported, the HNB shall include the *PSC* IE in the HNB REGISTER REQUEST message. + +If the registration is successful, the HNB-GW will respond with a HNB REGISTER ACCEPT message indicating acceptance and registration. If the *Iurh signalling TNL Address* IE is included in the HNB REGISTER ACCEPT message, the HNB shall, if supported, establish a transport layer session to the indicated address to support Iurh connectivity via/to the HNB-GW. + +If the HNB-GW is capable of de-multiplexing, then the *Mux Port Number* IE may be included in the HNB REGISTER ACCEPT message. + +If supported, the HNB may include the *Tunnel Information* IE in the HNB REGISTER REQUEST message. + +If the *CELL\_FACH Mobility Support* IE is included in the HNB REGISTER REQUEST message, the HNB-GW shall, if supported, include the *S-RNTI Prefix* IE and in the HNB REGISTER ACCEPT message. + +If included in the HNB REGISTER REQUEST message, the HNB-GW may use the *Neighbour Cell Identity List* IE, the *URA Identity List* IE or the *HNB Capacity* IE when assigning the *S-RNTI Prefix* IE to the HNB. + +### 8.2.3 Unsuccessful Operation + +![Sequence diagram showing the HNB Register Procedure: Un-Successful Operation. The HNB sends an HNB REGISTER REQUEST to the HNB-GW, and the HNB-GW responds with an HNB REGISTER REJECT.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: HNB REGISTER REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: HNB REGISTER REJECT + Note left of HNB: +``` + +Sequence diagram showing the HNB Register Procedure: Un-Successful Operation. The HNB sends an HNB REGISTER REQUEST to the HNB-GW, and the HNB-GW responds with an HNB REGISTER REJECT. + +**Figure 8.2.3-1: HNB Register Procedure: Un-Successful Operation** + +If the HNB-GW cannot register the HNB, the HNB-GW will respond with a HNB REGISTER REJECT message. + +Typical cause values are: + +#### **Radio Network Layer Cause:** + +- Unauthorised Location +- Unauthorised HNB +- Overload +- HNB Parameter Mismatch +- Unspecified + +If the *Cause* IE in the HNB REGISTER REJECT message is set to "overload", the HNB shall not retry registration to the same HNB-GW for at least the duration indicated in the *Backoff Timer* IE. + +### 8.2.4 Abnormal Conditions + +If the HNB-GW receives a duplicate HNB REGISTER REQUEST (i.e. for an already registered HNB identified by the same unique HNB identity), then the new HNB REGISTER REQUEST shall override the existing registration and the handling of the new HNB REGISTER REQUEST shall be performed according to subclause 8.2. + +## 8.3 HNB De-registration Procedure + +### 8.3.1 Successful Operation (HNB Originated) + +![Sequence diagram for HNB De-register Procedure: Successful Operation (HNB Originated). The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'HNB DE-REGISTER' is sent from the HNB lifeline to the HNB-GW lifeline. Both lifelines have a solid black bar at the bottom.](853f59c89931a666c07903b31d098277_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: HNB DE-REGISTER + Note right of HNB-GW: +``` + +Sequence diagram for HNB De-register Procedure: Successful Operation (HNB Originated). The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'HNB DE-REGISTER' is sent from the HNB lifeline to the HNB-GW lifeline. Both lifelines have a solid black bar at the bottom. + +Figure 8.3.1-1: HNB De-register Procedure: Successful Operation + +The HNB will initiate this procedure whenever it needs to terminate operations. + +The HNB-GW shall clear all related resources associated with the HNB. + +Typical cause values are: + +#### **Radio Network Layer Cause:** + +- Normal +- Unspecified + +### 8.3.2 Successful Operation (HNB-GW Originated) + +![Sequence diagram for HNB De-register Procedure: Successful Operation (HNB-GW Originated). The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'HNB DE-REGISTER' is sent from the HNB-GW lifeline to the HNB lifeline. Both lifelines have a solid black bar at the bottom.](cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB-GW->>HNB: HNB DE-REGISTER + Note right of HNB-GW: +``` + +Sequence diagram for HNB De-register Procedure: Successful Operation (HNB-GW Originated). The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'HNB DE-REGISTER' is sent from the HNB-GW lifeline to the HNB lifeline. Both lifelines have a solid black bar at the bottom. + +Figure 8.3.2-1: HNB De-register Procedure: Successful Operation + +The HNB-GW will initiate this procedure whenever it needs to terminate operations with a HNB. + +The HNB-GW shall clear all related resources associated with the HNB. + +Typical cause values are: + +#### **Radio Network Layer Cause:** + +- Overload +- Unspecified + +If the *Cause* IE in the HNB DE-REGISTER message is set to "overload", the HNB shall not retry registration to the same HNB-GW for at least the duration indicated in the *Backoff Timer* IE. + +### 8.3.3 Abnormal Conditions + +- + +## 8.4 UE Registration + +### 8.4.1 General + +The UE Registration procedure provides means for the HNB to convey UE identification data to the HNB-GW in order to perform access control for the UE in the HNB-GW. The UE Registration also establishes a UE specific context identifier to be used between HNB and HNB-GW. The procedure is triggered when the UE attempts to access the HNB via an initial NAS message and there is no context in the HNB allocated for that UE. + +### 8.4.2 Successful Operation + +![Sequence diagram for Successful Operation of UE Register Procedure](2e399449b7f62d40167a65ca88888917_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: UE REGISTER REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: UE REGISTER ACCEPT + Note left of HNB: + Note right of HNB-GW: +``` + +The diagram illustrates the successful operation of the UE Register Procedure. It shows two vertical lifelines: HNB on the left and HNB-GW on the right. The HNB sends a 'UE REGISTER REQUEST' message to the HNB-GW. The HNB-GW responds with a 'UE REGISTER ACCEPT' message. Both lifelines have a thick black horizontal bar at the bottom, indicating the start and end of the procedure. + +Sequence diagram for Successful Operation of UE Register Procedure + +Figure 8.4.2-1: UE Register Procedure: Successful Operation + +The HNB shall initiate the procedure by sending a UE REGISTER REQUEST message to the HNB-GW including UE specific data. The HNB shall always include within the *UE Identity* IE the UE permanent identity (i.e. IMSI) if it does not serve a CSG cell or for registration of UEs without CSG capability except if the *Registration Cause* IE indicates "emergency call". + +The HNB-GW shall perform access control or membership verification in case of non-CSG UEs or non-CSG HNBs. If the HNB does not operate in closed access mode or access control is successful, the HNB-GW shall respond with a UE REGISTER ACCEPT message including the *Context-ID* IE. + +The UE REGISTER ACCEPT message may include the *CSG Membership Status* IE for the UE registering to the cell. + +The HNB-GW shall not perform access control if the *Registration Cause* IE indicates "emergency call". + +### 8.4.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of UE Register Procedure](3597664ae86918629ceabb89ae71669d_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: UE REGISTER REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: UE REGISTER REJECT + Note left of HNB: + Note right of HNB-GW: +``` + +The diagram illustrates the unsuccessful operation of the UE Register Procedure. It shows two vertical lifelines: HNB on the left and HNB-GW on the right. The HNB sends a 'UE REGISTER REQUEST' message to the HNB-GW. The HNB-GW responds with a 'UE REGISTER REJECT' message. Both lifelines have a thick black horizontal bar at the bottom, indicating the start and end of the procedure. + +Sequence diagram for Unsuccessful Operation of UE Register Procedure + +Figure 8.4.3-1: UE Register Procedure: Unsuccessful Operation + +If the HNB-GW is unable to accept the UE registration it shall reject the procedure with a UE REGISTER REJECT message. + +Typical Cause values: + +#### **Radio Network Layer Cause:** + +- Invalid UE identity +- UE not allowed on this HNB +- HNB not registered +- Unspecified + +### 8.4.4 Abnormal Conditions + +- + +## 8.5 UE De-Registration + +### 8.5.1 General + +The purpose of the UE De-Registration Procedure is to request the release of a UE context in the HNB-GW or the HNB. + +### 8.5.2 Successful Operation (HNB Originated) + +![Sequence diagram showing the UE De-Register Procedure: HNB Originated Successful Operation. The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'UE DE-REGISTER' is sent from the HNB to the HNB-GW.](e190b6ddb7c2e64b940749a1c5612256_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: UE DE-REGISTER + Note right of HNB-GW: +``` + +Sequence diagram showing the UE De-Register Procedure: HNB Originated Successful Operation. The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'UE DE-REGISTER' is sent from the HNB to the HNB-GW. + +**Figure 8.5.2-1: UE De-Register Procedure: HNB Originated Successful Operation** + +The HNB shall initiate the procedure by sending a UE DE-REGISTER message. When receiving the UE DE-REGISTER message the HNB-GW shall release the resources associated with that UE including the Context-ID. + +Typical Cause values: + +#### **Radio Network Layer Cause:** + +- Connection with UE lost +- UE RRC Release +- Unspecified +- UE relocated + +### 8.5.3 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing UE DE-REGISTER message from HNB-GW to HNB.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +A sequence diagram illustrating the UE De-Register Procedure. It features two vertical lifelines: HNB on the left and HNB-GW on the right. Each lifeline starts with a rectangular box containing the entity name and ends with a thick horizontal bar. A horizontal arrow labeled 'UE DE-REGISTER' points from the HNB-GW lifeline to the HNB lifeline. + +Sequence diagram showing UE DE-REGISTER message from HNB-GW to HNB. + +**Figure 8.5.3-1: UE De-Register Procedure: HNB-GW Originated Successful Operation** + +The HNB-GW shall initiate the procedure by sending a UE DE-REGISTER message. When receiving the UE DE-REGISTER message the HNB shall release the resources associated with the provided Context-ID. + +Typical Cause values: + +#### **Radio Network Layer Cause:** + +- UE Registered in another HNB +- Unspecified +- UE not allowed on this HNB + +### 8.5.4 Abnormal Conditions + +-- + +## 8.6 Error Indication + +### 8.6.1 General + +The Error Indication procedure is initiated by either the HNB or the HNB-GW to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +### 8.6.2 Successful Operation + +![Sequence diagram showing ERROR INDICATION message from HNB to HNB-GW.](57f8e374b0e99c488f68c46b713ffc64_img.jpg) + +A sequence diagram illustrating the Error Indication procedure. It features two vertical lifelines: HNB on the left and HNB-GW on the right. Each lifeline starts with a rectangular box containing the entity name and ends with a thick horizontal bar. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB lifeline to the HNB-GW lifeline. + +Sequence diagram showing ERROR INDICATION message from HNB to HNB-GW. + +**Figure 8.6.2-1 Error Indication HNB Originated, Successful Operation** + +![Sequence diagram showing an ERROR INDICATION message from HNB-GW to HNB.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +A sequence diagram showing two lifelines: HNB and HNB-GW. A message labeled "ERROR INDICATION" is sent from the HNB-GW lifeline to the HNB lifeline. Both lifelines have a solid black bar at the bottom, indicating active periods. + +Sequence diagram showing an ERROR INDICATION message from HNB-GW to HNB. + +**Figure 8.6.2-2: Error Indication HNB-GW Originated, Successful Operation** + +When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the node receiving an erroneous HNBAP message. + +## 8.7 CSG Membership Update Procedure + +### 8.7.1 Successful Operation + +![Sequence diagram showing a CSG Membership Update message from HNB-GW to HNB.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +A sequence diagram showing two lifelines: HNB and HNB-GW. A message labeled "CSG Membership Update" is sent from the HNB-GW lifeline to the HNB lifeline. Both lifelines have a solid black bar at the bottom, indicating active periods. + +Sequence diagram showing a CSG Membership Update message from HNB-GW to HNB. + +**Figure 8.7.1-1: CSG Membership Update: Successful Operation** + +The HNB-GW shall initiate this procedure whenever it needs to indicate a change of a UE's CSG membership status to the HNB. + +### 8.7.2 Abnormal Conditions + +- + +## 8.8 Void + +### 8.8.1 Void + +### 8.8.2 Void + +### 8.8.3 Void + +## 8.9 TNL Update + +### 8.9.1 General + +The purpose of the TNL Update procedure is to provide the HNB-GW with updated TNL information for the indicated RABs. + +### 8.9.2 Successful Operation + +![Sequence diagram for Successful TNL Update operation](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: TNL UPDATE REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: TNL UPDATE RESPONSE + Note left of HNB: + Note right of HNB-GW: +``` + +A sequence diagram showing the interaction between an HNB and an HNB-GW for a successful TNL update. The HNB sends a 'TNL UPDATE REQUEST' message to the HNB-GW. The HNB-GW responds with a 'TNL UPDATE RESPONSE' message. Both entities have activation bars at the bottom of their lifelines. + +Sequence diagram for Successful TNL Update operation + +**Figure 8.9.2-1: TNL Update procedure: Successful operation.** + +The HNB initiates the procedure by sending the TNL UPDATE REQUEST message to the HNB-GW. + +Upon reception of the TNL UPDATE REQUEST message, the HNB-GW may start sending user data on the user plane to the target HNB. The HNB-GW shall respond with a TNL UPDATE RESPONSE message if the HNB-GW succeeds to establish TNL resources for the RABs indicated within the TNL UPDATE REQUEST message. + +### 8.9.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful TNL Update operation](29f586959675cafdf81cf934954908eb_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: TNL UPDATE REQUEST + Note right of HNB-GW: + HNB-GW-->>HNB: TNL UPDATE FAILURE + Note left of HNB: + Note right of HNB-GW: +``` + +A sequence diagram showing the interaction between an HNB and an HNB-GW for an unsuccessful TNL update. The HNB sends a 'TNL UPDATE REQUEST' message to the HNB-GW. The HNB-GW responds with a 'TNL UPDATE FAILURE' message. Both entities have activation bars at the bottom of their lifelines. + +Sequence diagram for Unsuccessful TNL Update operation + +**Figure 8.9.3-1: TNL Update: Unsuccessful operation.** + +If the HNB-GW fails to establish TNL resources for the RABs indicated within the TNL UPDATE REQUEST message the HNB-GW shall send the TNL UPDATE FAILURE message to the HNB with an appropriate cause value. + +### 8.9.4 Abnormal Conditions + +- + +## 8.10 HNB Configuration Transfer Procedure + +### 8.10.1 General + +The purpose of the HNB Configuration Transfer procedure is to obtain IP address information and other necessary information for establishing Iurh connections between HNBs. + +### 8.10.2 Successful Operation + +![Sequence diagram of HNB Configuration Transfer Procedure: Successful Operation](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: HNB Configuration Transfer Request + Note right of HNB-GW: + HNB-GW-->>HNB: HNB Configuration Transfer Response + Note left of HNB: +``` + +The diagram illustrates a successful HNB Configuration Transfer procedure. It features two lifelines: HNB (Home NodeB) on the left and HNB-GW (HNB Gateway) on the right. The HNB sends a 'HNB Configuration Transfer Request' message to the HNB-GW. The HNB-GW responds with a 'HNB Configuration Transfer Response' message. Both lifelines have a solid black bar at the bottom, indicating the end of the sequence. + +Sequence diagram of HNB Configuration Transfer Procedure: Successful Operation + +**Figure 8.10.2-1: HNB Configuration Transfer Procedure: Successful Operation** + +The HNB initiates this procedure by sending an HNB CONFIGURATION TRANSFER REQUEST message to the HNB-GW in order to retrieve the IP address and other necessary information for each neighbour HNB indicated in the *Neighbour Information Request List* IE. The HNB shall only request configuration information for those neighbour HNBs for which information has not already been received. + +The HNB CONFIGURATION TRANSFER REQUEST shall contain information for all requested neighbour HNBs in the *Neighbour Information Request List* IE. Available neighbour information shall be indicated in the *HNB Configuration Information Provided* IE, if no neighbour information is available this shall be indicated in the *HNB Configuration Information Missing* IE with the *Cause* IE set to an appropriate value. + +If the HNB indicated the support for CELL\_FACH/CELL\_PCH/URA\_PCH mobility at registration, the HNB-GW shall include the S-RNTI prefixes of the neighbour HNBs in the *Neighbour Information List* IE of the HNB CONFIGURATION TRANSFER RESPONSE message. If the HNB is also configured with a URA, the HNB-GW may include in the *Neighbour Information List* IE of the HNB CONFIGURATION TRANSFER RESPONSE message the *URA Identity List* IE of the neighbour HNBs. + +For each available neighbour information within the *Neighbour Information List* IE in the HNB CONFIGURATION TRANSFER RESPONSE message the HNB attempts establishing a transport layer session using the addresses provided in an ordered manner starting with the first entry of the list, if none is established yet, and an Iurh connection towards the related neighbour HNB. + +### 8.10.3 Void + +### 8.10.4 Abnormal Conditions + +- + +## 8.11 Relocation Complete + +### 8.11.1 General + +The purpose of the Relocation Complete procedure is to inform the HNB-GW that RNSAP Relocation at the Target-HNB has completed. The message indicates the RABs successfully established at the Target-HNB. + +### 8.11.2 Successful Operation + +![Sequence diagram for Figure 8.11.2-1: Relocation Complete procedure. Successful operation. The diagram shows two lifelines: HNB-GW and T-HNB. A message labeled 'RELOCATION COMPLETE' is sent from the T-HNB lifeline to the HNB-GW lifeline.](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` +sequenceDiagram + participant HNB-GW + participant T-HNB + Note left of HNB-GW: + T-HNB->>HNB-GW: RELOCATION COMPLETE + Note right of T-HNB: +``` + +Sequence diagram for Figure 8.11.2-1: Relocation Complete procedure. Successful operation. The diagram shows two lifelines: HNB-GW and T-HNB. A message labeled 'RELOCATION COMPLETE' is sent from the T-HNB lifeline to the HNB-GW lifeline. + +Figure 8.11.2-1: Relocation Complete procedure. Successful operation. + +The Target-HNB initiates the procedure by sending the RELOCATION COMPLETE message to the HNB-GW. + +## 8.12 U-RNTI Query + +### 8.12.1 General + +The purpose of the U-RNTI Query procedure is to allow the target HNB to query the HNB-GW about the source HNB of a UE in CELL\_FACH, CELL\_PCH or URA\_PCH state with unknown U-RNTI. + +### 8.12.2 Successful Operation + +![Sequence diagram for Figure 8.12.2-1: U-RNTI Query procedure: Successful Operation. The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'U-RNTI Query Request' is sent from the HNB lifeline to the HNB-GW lifeline. A message labeled 'U-RNTI Query Response' is sent from the HNB-GW lifeline to the HNB lifeline.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +``` +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: + HNB->>HNB-GW: U-RNTI Query Request + HNB-GW-->>HNB: U-RNTI Query Response + Note right of HNB-GW: +``` + +Sequence diagram for Figure 8.12.2-1: U-RNTI Query procedure: Successful Operation. The diagram shows two lifelines: HNB and HNB-GW. A message labeled 'U-RNTI Query Request' is sent from the HNB lifeline to the HNB-GW lifeline. A message labeled 'U-RNTI Query Response' is sent from the HNB-GW lifeline to the HNB lifeline. + +Figure 8.12.2-1: U-RNTI Query procedure: Successful Operation + +The target HNB initiates this procedure by sending a U-RNTI QUERY REQUEST message to the HNB-GW in order to request configuration information for a specific U-RNTI from the HNB-GW. + +# 9 Elements for HNBAP Communication + +## 9.1 Message Functional Definition and Content + +### 9.1.1 General + +Subclause 9.1 presents the contents of HNBAP messages in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [5]. + +For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message. + +### 9.1.2 Message Contents + +#### 9.1.2.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 3 + +**Table 3: Meaning of abbreviations used in HNBAP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| M | IE's marked as Mandatory (M) will always be included in the message. | +| O | IE's marked as Optional (O) may or may not be included in the message. | +| C | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have criticality information applied to it. Following cases are possible. + +**Table 4: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +### 9.1.3 HNB REGISTER REQUEST + +This message is sent by the HNB to the HNB-GW to register the HNB at the HNB-GW. + +Direction: HNB → HNB-GW + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------|----------|---------------------------------------|-----------------------|--------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| HNB Identity | M | | 9.2.2 | | YES | reject | +| HNB Location Information | M | | 9.2.3 | | YES | reject | +| PLMN-ID | M | | 9.2.14 | | YES | reject | +| Cell-ID | M | | 9.2.25 | | YES | reject | +| LAC | M | | 9.2.11 | | YES | reject | +| RAC | M | | 9.2.12 | | YES | reject | +| SAC | M | | 9.2.13 | | YES | reject | +| CSG-ID | O | | 9.2.27 | | YES | reject | +| Service Area For Broadcast | O | | SAC
9.2.13 | | YES | ignore | +| HNB Cell Access Mode | O | | 9.2.31 | | YES | reject | +| PSC | O | | 9.2.41 | | YES | ignore | +| Iurh signalling TNL Address | O | | IP Address
9.2.8 | HNB IP address used for direct Iurh connectivity | YES | ignore | +| Tunnel Information | O | | 9.2.44 | | YES | ignore | +| CELL_FACH Mobility Support | O | | 9.2.45 | | YES | ignore | +| Neighbour Cell Identity List | | 0 to
| | | GLOBAL | ignore | +| >Neighbour Identity | | | 9.2.51 | | | | +| URA Identity List | | 0 to
| | | GLOBAL | ignore | +| >URA Identity | | | 9.2.47 | | | | +| HNB Capacity | O | | 9.2.50 | | YES | ignore | + +| Range bound | Explanation | +|------------------------------------|---------------------------------------------------------------------------------------| +| maxnoofAdditionalNeighbours | Maximum number of additional neighbour cells associated to a given HNB. Value is 128. | +| maxnoofURAidentities | Maximum number of URA Identities assigned to a HNB. Value is 8. | + +### 9.1.4 HNB REGISTER ACCEPT + +This message is sent by the HNB-GW to the HNB as a successful response to a HNB REGISTER REQUEST message. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| RNC-ID | M | | 9.2.26 | | YES | reject | +| Mux Port Number | O | | 9.2.29 | The mux port number at which HNB-GW expects to receive multiplexed packets. | YES | ignore | +| Iurh signalling TNL Address | O | | IP Address
9.2.8 | HNB-GW IP address used for Iurh connectivity via/to the HNB-GW | YES | ignore | +| S-RNTI Prefix | O | | 9.2.46 | To be used together with the HNB-GW RNC-ID when assigning U-RNTI to UE. | YES | ignore | + +### 9.1.5 HNB REGISTER REJECT + +This message is sent by the HNB-GW to the HNB as unsuccessful response to a HNB REGISTER REQUEST message. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|------------------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Cause | M | | 9.2.15 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.16 | | YES | ignore | +| Backoff Timer | C-
ifOverload | | 9.2.28 | | YES | reject | + +| Condition | Explanation | +|-------------------|----------------------------------------------------------------| +| IfOverload | This IE shall be present if the Cause IE is set to "Overload". | + +### 9.1.6 UE REGISTER REQUEST + +This message is sent by the HNB to the HNB-GW to register a UE at HNB-GW for service. + +Direction: HNB → HNB-GW + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| UE Identity | M | | 9.2.17 | | YES | reject | +| Registration Cause | M | | 9.2.21 | | YES | ignore | +| UE Capabilities | M | | 9.2.24 | | YES | reject | + +### 9.1.7 UE REGISTER ACCEPT + +This message is sent by the HNB-GW to the HNB as a successful response to a UE REGISTER REQUEST message. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| UE Identity | M | | 9.2.17 | | YES | reject | +| Context-ID | M | | 9.2.9 | | YES | reject | +| CSG Membership Status | O | | 9.2.30 | | YES | reject | + +### 9.1.8 UE REGISTER REJECT + +This message is sent by the HNB-GW to the HNB as unsuccessful response to a UE REGISTER REQUEST message. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| UE Identity | M | | 9.2.17 | | YES | reject | +| Cause | M | | 9.2.15 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.16 | | YES | ignore | + +### 9.1.9 HNB DE-REGISTER + +This message is sent by the HNB to the HNB-GW or HNB-GW to HNB to deregister the HNB, + +Direction: HNB → HNB-GW or HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|------------------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Cause | M | | 9.2.15 | | YES | ignore | +| Backoff Timer | C-
ifOverload | | 9.2.28 | | YES | reject | + +| Condition | Explanation | +|------------|----------------------------------------------------------------| +| IfOverload | This IE shall be present if the Cause IE is set to "Overload". | + +### 9.1.10 UE DE-REGISTER + +This message is sent by the HNB to the HNB-GW or HNB-GW to HNB to de-register a UE. + +Direction: HNB → HNB-GW, HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Context-ID | M | | 9.2.9 | | YES | reject | +| Cause | M | | 9.2.15 | | YES | ignore | + +### 9.1.11 ERROR INDICATION + +This message is sent by the HNB to HNB-GW or HNB-GW to HNB and is used to indicate that some errors have been detected. + +Direction: HNB → HNB-GW, HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Cause | M | | 9.2.15 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.16 | | YES | ignore | + +### 9.1.12 CSG MEMBERSHIP UPDATE + +This message is sent by the HNB-GW to HNB to indicate CSG Membership changes to the HNB. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Context-ID | M | | 9.2.9 | | YES | reject | +| CSG Membership Status | M | | 9.2.30 | | YES | reject | + +### 9.1.13 Void + +### 9.1.14 Void + +### 9.1.15 TNL UPDATE REQUEST + +This message is sent by the HNB to the HNB-GW to inform the GW of new TNL information for the referenced RABs. + +Direction: HNB → HNB-GW + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Context-ID | M | | 9.2.9 | | YES | reject | +| RAB List | M | | 9.2.32 | | YES | reject | +| Update Cause | M | | 9.2.39 | | YES | reject | + +### 9.1.16 TNL UPDATE RESPONSE + +This message is sent by the HNB-GW to inform the HNB that a TNL update switch has been successfully completed in the HNB-GW. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Context-ID | M | | 9.2.9 | | YES | reject | + +### 9.1.17 TNL UPDATE FAILURE + +This message is sent by the HNB-GW to inform the HNB that a failure has occurred during the TNL update procedure. + +Direction: HNB-GW → HNB + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Context-ID | M | | 9.2.9 | | YES | reject | +| Cause | M | | 9.2.15 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.16 | | YES | ignore | + +### 9.1.18 HNB CONFIGURATION TRANSFER REQUEST + +This message is sent by the HNB to the HNB-GW to request configuration information for neighbouring HNBs. + +Direction: HNB → HNB-GW + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|--------------------------|-------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Neighbour Information Request List | M | | | | YES | reject | +| >Neighbour Information Request | | 1 to | HNB RNL Identity 9.2.36 | | - | | + +| Range bound | Explanation | +|--------------------------|---------------------------------------------------------------------------| +| maxnoofNeighbours | Maximum number of neighbour cells associated to a given HNB. Value is 32. | + +### 9.1.19 HNB CONFIGURATION TRANSFER RESPONSE + +This message is sent by the HNB-GW to the HNB as a response to a HNB CONFIGURATION TRANSFER REQUEST message. + +Direction: HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------------------------------------|--------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| Neighbour Information List | M | | | | YES | reject | +| >Neighbour Information | | 1 to | HNB Configuration Information 9.2.40 | | - | | +| Additional Neighbour Information List | O | | | | YES | ignore | +| >Neighbour Information | | 1 to | HNB Configuration Information 9.2.40 | | - | | + +| Range bound | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------| +| maxnoofNeighbours | Maximum number of neighbour cells associated to a given HNB. Value is 32. | +| maxnoofAdditionalNeighbours | Maximum number of additional neighbour cells associated to a given HNB. Value is 128. | + +### 9.1.20 Void + +### 9.1.21 RELOCATION COMPLETE + +This message is sent by the HNB to inform the HNB-GW that a relocation is completed. + +Direction: HNB → HNB GW + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Context-ID | M | | 9.2.9 | | YES | ignore | + +### 9.1.22 U-RNTI QUERY REQUEST + +This message is sent by the HNB to request configuration information for a specific U-RNTI from the HNB-GW. + +Direction: HNB → HNB GW + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| U-RNTI | M | | 9.2.48 | | YES | reject | + +### 9.1.23 U-RNTI QUERY RESPONSE + +This message is sent by the HNB-GW to provide the requested information for a specific U-RNTI. + +Direction: HNB-GW → HNB + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | reject | +| CHOICE HNB-GW response | M | | | | YES | reject | +| >HNB | | | | | | | +| >>HNB Configuration Information | M | | 9.2.40 | | - | | +| >Macro RNC | | | | | | | +| >>RNC-ID | M | | 9.2.26 | | - | | +| >Unknown U-RNTI Indication | | | | | | | +| >>Unknown U-RNTI Indication | M | | 9.2.49 | | - | | + +## 9.2 Information Element Definitions + +### 9.2.0 General + +Subclause 9.2 presents the HNBAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); +- When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information; + +### 9.2.1 Message Type + +*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------| +| Message Type | | | | | +| >Procedure Code | M | | INTEGER(0..255) | | +| >Type of Message | M | | ENUMERATED
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
Outcome) | | + +### 9.2.2 HNB Identity + +*HNB Identity* IE is sent from the HNB to the HNB-GW and identifies the HNB. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------|-----------------------| +| HNB Identity | | | OCTET STRING
(SIZE(1..255)) | See note below. | + +Note: + +The octet string shall take form of a Network Access Identifier (NAI) as defined in IETF RFC 4282 [13]. The format of the HNB-Identity will be: + +0@ + +Or + +1-@ + +Where is a 16 digit number coded as specified in TS 23.003 [12]; + +and and are coded as specified in TR-069 [14]. + +### 9.2.3 HNB Location Information + +The *HNB Location Information* IE is sent from the HNB to HNB-GW to provide information on the location of the HNB. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| HNB Location Information | | 1 | | | - | - | +| >Macro Coverage Information | O | | 9.2.7 | | - | - | +| >Geographic Location | O | | 9.2.4 | | - | - | +| >HNB Internet Information | O | | IP Address
9.2.8 | | YES | reject | + +### 9.2.4 Geographical Location + +This IE identifies the Ellipsoid point with altitude as in ref TS 23.032 [4]. + +| IE/GROUP NAME | PRESENCE | RANGE | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|-----------------------| +| Geographical Coordinates | M | | 9.2.5 | | +| Altitude and Direction | M | | 9.2.6 | | + +### 9.2.5 Geographical Coordinates + +This IE contains the geographical coordinates of an ellipsoid point. + +| IE/GROUP NAME | PRESENCE | RANGE | IE type and reference | Semantics description | +|----------------------|----------|-------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED
(North, South) | | +| Degrees Of Latitude | M | | INTEGER (
$0..2^{23}-1$ ) | The IE value (N) is derived by this formula:
$N \leq 2^{23} \times X / 90 < N+1$
X being the latitude in degree ( $0^\circ..90^\circ$ ) | +| Degrees Of Longitude | M | | INTEGER (
$-2^{23}..2^{23}-1$ ) | The IE value (N) is derived by this formula:
$N \leq 2^{24} \times X / 360 < N+1$
X being the longitude in degree ( $-180^\circ..+180^\circ$ ) | + +### 9.2.6 Altitude and Direction + +This IE contains the altitude and direction of an ellipsoid point. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Altitude and direction | | 1 | | | +| >Direction of Altitude | M | | ENUMERATED
(Height, Depth) | | +| >Altitude | M | | INTEGER (
0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \le a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all grater values of (a). | + +### 9.2.7 Macro Coverage Information + +The *Macro Coverage Information* IE identifies the macro cell used by the HNB for location. This may be e.g. a GERAN Cell ID or a UTRAN Cell ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|------------------------|----------------------------| +| CHOICE Cell Identifier | | | | | +| >UTRAN Cell ID Information | | | | | +| >>LAC | M | | 9.2.11 | | +| >>RAC | M | | 9.2.12 | | +| >>PLMN-ID | M | | 9.2.14 | | +| >>Cell-ID | M | | 9.2.25 | | +| >GERAN Cell ID Information | | | | | +| >>PLMN-ID | M | | 9.2.14 | | +| >>LAC | M | | 9.2.11 | 0000 and FFFE not allowed. | +| >>CI | M | | OCTET STRING (SIZE(2)) | | + +### 9.2.8 IP Address + +This IE defines an IP address. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|------------------------|-----------------------| +| CHOICE IP Address | | | | | +| >IPv4 | | | | | +| >>Internet Address ipv4 | M | | OCTET STRING(SIZE(4)) | | +| >IPv6 | | | | | +| >>Internet Address ipv6 | M | | OCTET STRING(SIZE(16)) | | + +### 9.2.9 Context-ID + +The *Context-ID* IE uniquely identifies a particular UE in the HNB and HNB-GW. This unique Context-ID is used for PS and CS domain. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Context-ID | | | BIT STRING(SIZE(24)) | | + +### 9.2.10 IMSI + +The IMSI is used to uniquely identify a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | | | OCTET STRING (SIZE (3..8)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit,
  • two digits per octet,
  • - bit 4 to 1 of octet n encoding digit 2n-1
  • - bit 8 to 5 of octet n encoding digit 2n

-Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity.
When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.

| + +### 9.2.11 LAC + +This element is used to identify a Location Area. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| LAC | | | OCTET STRING(SIZE(2)) | | + +### 9.2.12 RAC + +This element is used to identify a Routing Area within a Location Area. It is used for PS services. + +| IE/GROUP NAME | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| RAC | | | OCTET STRING(SIZE(1)) | | + +### 9.2.13 SAC + +The SAC identifies the Service Area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------| +| SAC | | | OCTET STRING (SIZE(2)) | | + +### 9.2.14 PLMN-ID + +The PLMN-ID identifies a Public Land Mobile Network. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN-ID | | | OCTET STRING (SIZE (3)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit, two digits per octet,
  • - bits 4 to 1 of octet n encoding digit 2n-1- bits 8 to 5 of octet n encoding digit 2n

-The PLMN identity consists of 3 digits from MCC followed by either

  • - a filler digit plus 2 digits from MNC (in case of 2 digit MNC)

or

  • - 3 digits from MNC (in case of a 3 digit MNC).
| + +### 9.2.15 Cause + +The *Cause* IE indicates the reason for a particular error event for the HNBAP protocol. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED
(
overload,
unauthorised-Location,
unauthorised-HNB,
HNB Parameter mismatch,
Invalid UE identity,
UE not allowed on this HNB,
UE unauthorised,
Connection with UE lost,
UE RRC Release,
HNB not registered,
unspecified,
Normal,
UE relocated,
UE Registered in another HNB,
...
No Neighbour Information available,
Iurh connection to that Neighbour not Allowed
) | | +| > Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED
(Transport Resource Unavailable,
Unspecified,
...) | | +| > Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely Constructed Message),
...) | | +| > Misc | | | | | +| >>Misc Cause | M | | ENUMERATED
(Processing Overload,
Hardware Failure,
O&M Intervention,
Unspecified,
...) | | + +The meaning of the different cause values is described in the following table. Cause values for information 'not valid' indicates that the information is not valid in the context that it was received. + +| Radio Network Layer cause | Meaning | +|-----------------------------------------------|------------------------------------------------------------------------------------------------------| +| Connection with UE lost | The connection to a Registered UE has been lost | +| HNB not registered | The HNB is not registered on this gateway | +| HNB Parameter Mismatch | The HNB-GW cannot register the HNB because of mismatch in parameters between HNB and HNB-GW | +| Invalid UE identity | The UE ID supplied for UE registration is not valid | +| Iurh connection to that Neighbour not Allowed | Any Iurh connection to the indicated neighbour is not allowed. | +| No Neighbour Information available | The requested neighbour information is not available. | +| Normal | No error has occurred | +| Overload | The HNB-GW cannot handle the HNB due to overload. | +| UE not allowed on this HNB | The UE is identified as not being allowed to use services on this HNB. (temporary rejection) | +| UE not authorised | The UE is identified as not being allowed to use services on a HNB (permanent rejection). | +| UE Registered in another HNB | The UE has already registered in another HNB on same HNB-GW. | +| UE relocated | The UE has been relocated to a neighbouring cell | +| UE RRC release | The Registered UE's RRC is released (e.g. due to IMSI detach NAS procedure) | +| Unauthorised-HNB | The HNB-GW cannot register the HNB because its supplied information is not considered valid | +| Unauthorised-Location | The HNB-GW cannot register the HNB because the location information provided is not valid. | +| Unspecified | Sent when none of the above cause values applies but still the cause is Radio Network layer related. | + +| Transport Network 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. | + +| Protocol cause | Meaning | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerned criticality indicated "reject". | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify". | +| Abstract syntax error (falsely constructed message) | The received message contained IEs in wrong order or with too many occurrences. | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state. | +| Semantic Error | The received message included a semantic error. | +| Transfer Syntax Error | The received message included a transfer syntax error. | +| Unspecified | Sent when none of the above cause values applies but still the cause is protocol related. | + +| Miscellaneous cause | Meaning | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Hardware Failure | HNB hardware failure. | +| O&M Intervention | Operation and Maintenance intervention related to HNB. | +| Processing Overload | Control processing overload. | +| Unspecified | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. | + +### 9.2.16 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the HNB or the HNB-GW 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. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|----------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | 1 | | | +| >Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| >Triggering Message | O | | ENUMERATED (initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | +| >Procedure Criticality | O | | ENUMERATED(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0 to | | | +| >IE Criticality | M | | ENUMERATED(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | +| >IE ID | M | | INTEGER (0..65535) | The IE Id of the not understood or missing IE | +| >Type of Error | M | | ENUMERATED(not understood, missing, ...) | | + +| Range bound | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------| +| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxNrOfErrors is 256. | + +### 9.2.17 UE Identity + +This is a unique identifier for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------------|-----------------------| +| CHOICE UE Identity | | | | | +| >IMSI | | | | | +| >>IMSI | | | 9.2.10 | | +| >TMSI and LAI (GSM-MAP) | | | | | +| >>TMSI (GSM-MAP) | M | | 9.2.19 | | +| >>LAI | M | | 9.2.20 | | +| >P-TMSI and RAI (GSM-MAP) | | | | | +| >>P-TMSI (GSM-MAP) | M | | 9.2.22 | | +| >>RAI (GSM-MAP) | M | | 9.2.23 | | +| >IMEI | | | | | +| >>IMEI | | | 9.2.18 | | +| >ESN (DS-41) | | | | | +| >>ESN (DS-41) | | | BIT STRING (SIZE (32)) | | +| >IMSI(DS-41) | | | | | +| >>IMSI (DS-41) | | | OCTET STRING (SIZE (5..7)) | | +| >IMSI and ESN (DS-41) | | | | | +| >>ESN (DS-41) | M | | BIT STRING(SIZE (32)) | | +| >>IMSI (DS-41) | M | | OCTET STRING (SIZE (5..7)) | | +| >TMSI(DS-41) | | | | | +| >>TMSI (DS-41) | | | OCTET STRING (SIZE (2..17)) | | + +### 9.2.18 IMEI + +This IE contains an International Mobile Equipment Identity. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| IMEI | | | BIT STRING(SIZE(60)) | | + +### 9.2.19 TMSI (GSM-MAP) + +This IE contains a Temporary Mobile Subscriber Identity, used towards a GSM-MAP type of PLMN. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------| +| TMSI (GSM-MAP) | | | BIT STRING (SIZE(32)) | The first/leftmost bit of the bit string contains the most significant bit of the TMSI. | + +### 9.2.20 LAI + +Location Area Identification identifies uniquely a location area for a GSM-MAP type of PLMN. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------|-----------------------| +| PLMN-ID | M | | 9.2.14 | | +| LAC | M | | 9.2.11 | | + +### 9.2.21 Registration Cause + +This IE indicates if a UE registration is for an emergency call. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------------------------------------------------------|-----------------------| +| Registration cause | | | Enumerated
( emergency
call,
normal, ...,
ue-relocation) | | + +### 9.2.22 P-TMSI (GSM-MAP) + +This IE contains a Packet Temporary Mobile Subscriber Identity (P-TMSI), used towards a GSM-MAP type of PLMN. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------------|-------------------------------------------------------------------------------------------| +| P-TMSI | | | BIT STRING
(SIZE(32)) | The first/leftmost bit of the bit string contains the most significant bit of the P-TMSI. | + +### 9.2.23 Routing Area Identification + +This IE identifies uniquely a routing area for a GSM-MAP type of PLMN. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------|-----------------------| +| LAI | M | | 9.2.20 | | +| RAC | M | | 9.2.12 | | + +### 9.2.24 UE Capabilities + +This IE identifies UE capabilities and release. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|-----------------------------------|----------|-------|----------------------------------------------------------------------------------------|-------------------------------------| +| UE Capabilities | | 1 | | | +| >Access Stratum Release Indicator | M | | Enumerated
{ R99, Rel-4,
Rel-5, Rel-6,
Rel-7, Rel-8-
and-
beyond, ... } | Values as defined in TS 25.331 [10] | +| >CSG Capability | M | | Enumerated
{CSG
capable,
Not CSG
capable,
... } | Indicates a CSG capable UE. | + +### 9.2.25 Cell-ID + +This IE identifies uniquely a cell within a PLMN, as defined in TS 25.331 [10]. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|---------------------------|--------------------------------------------------------------------| +| Cell-ID | | | BIT STRING
(SIZE (28)) | This information element identifies a cell uniquely within a PLMN. | + +### 9.2.26 RNC-ID + +The HNB uses the RNC-ID as specified in TS 25.467 [3]. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------|--------------------------------------------------------| +| RNC-ID | | | INTEGER (0..65535) | Values greater than 4095 are extended (16bit) RNC Ids. | + +### 9.2.27 CSG-ID + +This IE indicates the CSG-ID of a particular HNB, as defined in TS 23.003 [12] + +| Information Element/Group name | Need | Multi | Type and reference | Semantics description | +|--------------------------------|------|-------|-----------------------|-----------------------| +| CSG-ID | | | BIT STRING (SIZE(27)) | | + +### 9.2.28 Backoff Timer + +The *Backoff Timer* IE indicates in seconds the minimum duration for which the HNB registration shall not be retried. + +| Information Element/Group name | Need | Multi | Type and reference | Semantics description | +|--------------------------------|------|-------|--------------------|----------------------------------------| +| Backoff Timer | | | INTEGER (0..3600) | Value '0' indicates no specified time. | + +### 9.2.29 Mux Port Number + +This IE identifies the mux port number on which the HNB-GW expects the multiplexed packets from the HNB + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| Mux port number | | | INTEGER (1024..65535) | | + +### 9.2.30 CSG Membership Status + +This element indicates the Membership status of the UE to a particular CSG. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------------|-----------------------| +| CSG Membership Status | M | | ENUMERATED (member, non-member,...) | | + +### 9.2.31 HNB Cell Access Mode + +This information element indicates whether the cell of the HNB operates in a Closed, Hybrid, or Open Access mode as defined in TS 22.220 [15]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|----------------------------------------|-----------------------| +| HNB Cell Access Mode | M | | ENUMERATED (closed, hybrid, open, ...) | | + +### 9.2.32 RAB List + +The *RAB List* IE indicates a list of old and new RAB transport information. + +| IE/Group name | Presence | Range | IE Type and reference | Semantics description | +|----------------------|----------|---------------------------|-----------------------------|-----------------------------------------| +| RAB List | | 1 to
RABs> | | | +| >RAB ID | M | | 9.2.43 | | +| >Old Transport Info | M | | Transport
Info
9.2.33 | This IE shall be ignored by the HNB-GW. | +| >New Transport Info | M | | Transport
Info
9.2.33 | | +| >CN Domain Indicator | M | | 9.2.37 | | + +| Range bound | Explanation | +|-------------|-----------------------------------------------| +| maxnoofRABs | Maximum no. of RABs for one UE. Value is 256. | + +### 9.2.33 Transport Info + +The *Transport Info* IE indicates transport network layer related information. + +| IE/Group name | Presence | Range | IE Type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Transport Layer Address | M | | 9.2.34 | | +| Transport Association | M | | 9.2.35 | | + +### 9.2.34 Transport Layer Address + +This information element is an IP address to be used for the user plane transport. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|--------------------------------------|-----------------------| +| Transport Layer Address | M | | BIT STRING
(SIZE(1..160,
...)) | | + +### 9.2.35 Transport Association + +This element is used to associate the RAB and the corresponding transport bearer. For the CS domain this information element is the UDP port. In PS domain this information element is the GTP Tunnel Endpoint Identifier. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Transport Association | | | | | +| >GTP TEID | | | OCTET
STRING
(SIZE(4)) | | +| >Binding ID | | | OCTET
STRING
(SIZE(1..4,
...)) | The UDP port is included in octet 1 and 2. The first octet of the UDP port field shall be included in the first octet of the Binding ID. | + +### 9.2.36 HNB RNL Identity + +The *HNB RNL Identity* IE globally identifies an HNB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE HNB RNL Identity | | | | | - | - | +| > HNB Cell Identifier | | | | | | | +| >> HNB Cell Identifier | M | | 9.2.42 | | YES | reject | + +### 9.2.37 CN Domain Indicator + +The *CN Domain Indicator* IE globally identifies a CN domain. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------|-----------------------| +| CN Domain Indicator | M | | ENUMERATED (CS domain, PS domain) | | + +### 9.2.38 Void + +### 9.2.39 Update Cause + +This IE indicates the reason for TNL update request. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|-------------------------------------------|-----------------------| +| Update cause | | | ENUMERATED ( Relocation preparation, ...) | | + +### 9.2.40 HNB Configuration Information + +This IE contains configuration information of a HNB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|------------------------------|-----------------------|-----------------------|-------------|----------------------| +| HNB RNL Identity | M | | 9.2.36 | | - | - | +| CHOICE Configuration Information | M | | | | - | - | +| > HNB Configuration Information Provided | | | | | - | - | +| >>PSC | O | | 9.2.41 | | - | - | +| >>CSG-ID | O | | 9.2.27 | | - | - | +| >>HNB Cell Access Mode | M | | 9.2.31 | | - | - | +| >>> Iurh signalling TNL Address List | | 1 to | | | - | - | +| >>>Iurh signalling TNL address | M | | IP address 9.2.8 | | - | - | +| >>S-RNTI Prefix | O | | 9.2.46 | | YES | ignore | +| >> URA Identity List | | 0 to | | | GLOBAL | ignore | +| >>>URA Identity | | | 9.2.47 | | - | - | +| > HNB Configuration Information Missing | | | | | - | - | +| >>Cause | M | | 9.2.15 | | - | - | + +| Range bound | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------| +| maxnoofIurhAddresses | Maximum no. of Iurh signalling TNL addresses provided. The value for MaxnoofIurhAddresses is 3. | +| maxnoofURAIdentities | Maximum number of URA Identities assigned to a HNB. Value is 8. | + +### 9.2.41 PSC + +This IE contains the Primary Scrambling Code of the cell served by the HNB. + +| Information Element/Group name | Presence | Range | Type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------|-----------------------| +| PSC | | | BIT STRING (SIZE(9)) | | + +### 9.2.42 HNB Cell Identifier + +This IE contains the information which identifies a HNB for which configuration information is requested. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| PLMN-ID | M | | 9.2.14 | | +| Cell-ID | M | | 9.2.25 | | + +### 9.2.43 RAB ID + +This IE shall be used and encoded as defined in TS 25.413 [2]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| RAB ID | M | | BIT STRING (SIZE(8)) | | + +### 9.2.44 Tunnel Information + +This information element contains the IP address and UDP port information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|------------------------|--------------------------------------------------------------------| +| IP Address | M | | 9.2.8 | HNB's local IP Address assigned by the broadband access provider. | +| UDP Port Number | O | | OCTET STRING (SIZE(2)) | UDP Port Number if NAT/NAPT is deployed in the BBF access network. | + +### 9.2.45 CELL\_FACH Mobility Support + +This information element contains the indication of whether a HNB supports or not CELL\_FACH/CELL\_PCH/URA\_PCH mobility. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------------|-----------------------| +| CELL_FACH Mobility Support | M | | ENUMERATED (Supported, ...) | | + +### 9.2.46 S-RNTI Prefix + +This information element contains the S-RNTI prefix assigned by the HNB-GW to the HNB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------------------|-----------------------| +| S-RNTI Prefix | M | | BIT STRING
(SIZE
(1..16, ...)) | | + +### 9.2.47 URA Identity + +This information element contains the indication of the identity of a URA an HNB belongs to. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| URA Identity | M | | INTEGER
(0..65535) | | + +### 9.2.48 U-RNTI + +This information element contains the U-RNTI. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-----------------------| +| U-RNTI | M | | BIT STRING
(SIZE (32)) | | + +### 9.2.49 Unknown U-RNTI Indication + +This information element contains the indication from the HNB-GW of whether a certain U-RNTI is unknown or not. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|------------------------------|-----------------------| +| Unknown U-RNTI Indication | M | | ENUMERATED
(Unknown, ...) | | + +### 9.2.50 HNB Capacity + +This information element contains the indication of the HNB capacity for S-RNTI prefix assignment. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|---------------------------------------------------------------| +| HNB Capacity | M | | INTEGER
(0...1000) | HNB capacity in terms of supported concurrent RRC connections | + +### 9.2.51 Neighbour Identity + +This information element contains the HNB RNL Identity or the macro Cell-ID the HNB indicates to the HNB-GW in order to obtain the S-RNTI Prefix. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Neighbour Identity | M | | | | +| >HNB | | | | | +| >>HNB RNL Identity | M | | 9.2.36 | | +| >Macro RNC | | | | | +| >>Cell-ID | M | | 9.2.25 | | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +HNBAP ASN.1 definition conforms with ITU-T Rec. X.680 [8] and ITU-T Rec. X.681 [9]. + +The ASN.1 definition specifies the structure and content of HNBAP messages. HNBAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a HNBAP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a HNBAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 10.3.6. + +### 9.3.1 Usage of private message mechanism for non-standard use + +The private message mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability; +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** +HNBAP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) hnbap(6) version1 (1) hnbap-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM HNBAP-CommonDataTypes + + HNBRegisterRequest, + HNBRegisterAccept, + HNBRegisterReject, + HNBDe-Register, + UERegisterRequest, + UERegisterAccept, + UERegisterReject, + UEDe-Register, + ErrorIndication, + PrivateMessage, + CSGMembershipUpdate, + TNLUpdateRequest, + TNLUpdateResponse, + TNLUpdateFailure, + HNBConfigTransferRequest, + HNBConfigTransferResponse, + RelocationComplete, + U-RNTIQueryRequest, + U-RNTIQueryResponse + +FROM HNBAP-PDU-Contents + id-HNBRegister, + id-UERegister, + id-UEDe-Register, +``` + +``` + +id-HNBDe-Register, +id-ErrorIndication, +id-privateMessage, +id-CSGMembershipUpdate, +id-TNLUpdate, +id-HNBConfigTransfer, +id-RelocationComplete, +id-U-RNTIQuery + +FROM HNBAP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +HNBAP-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 definitions +-- +-- ***** + +HNBAP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode HNBAP-ELEMENTARY-PROCEDURE.&procedureCode ({HNBAP-ELEMENTARY-PROCEDURES}), + criticality HNBAP-ELEMENTARY-PROCEDURE.&criticality ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value HNBAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +SuccessfulOutcome ::= SEQUENCE { + procedureCode HNBAP-ELEMENTARY-PROCEDURE.&procedureCode ({HNBAP-ELEMENTARY-PROCEDURES}), + criticality HNBAP-ELEMENTARY-PROCEDURE.&criticality ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value HNBAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode HNBAP-ELEMENTARY-PROCEDURE.&procedureCode ({HNBAP-ELEMENTARY-PROCEDURES}), + criticality HNBAP-ELEMENTARY-PROCEDURE.&criticality ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value HNBAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({HNBAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +HNBAP-ELEMENTARY-PROCEDURES HNBAP-ELEMENTARY-PROCEDURE ::= { + HNBAP-ELEMENTARY-PROCEDURES-CLASS-1 | + HNBAP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +HNBAP-ELEMENTARY-PROCEDURES-CLASS-1 HNBAP-ELEMENTARY-PROCEDURE ::= { + hNBRegister| + uERegister, + ..., + tnlUpdate| + hNBConfigTransfer| + u-RNTIQuery +} + +HNBAP-ELEMENTARY-PROCEDURES-CLASS-2 HNBAP-ELEMENTARY-PROCEDURE ::= { + uEDe-Register | + hNBDe-Register | + errorIndication | + privateMessage, + ..., + csg-membership-update| + relocationComplete +} + +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +``` + +``` +hNBRegister HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE HNBRegisterRequest + SUCCESSFUL OUTCOME HNBRegisterAccept + UNSUCCESSFUL OUTCOME HNBRegisterReject + PROCEDURE CODE id-HNBRegister + CRITICALITY reject +} + +uERegister HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UERegisterRequest + SUCCESSFUL OUTCOME UERegisterAccept + UNSUCCESSFUL OUTCOME UERegisterReject + PROCEDURE CODE id-UERegister + CRITICALITY reject +} + +uEDe-Register HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEDe-Register + PROCEDURE CODE id-UEDe-Register + CRITICALITY ignore +} + +hNBDe-Register HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE HNBDe-Register + PROCEDURE CODE id-HNBDe-Register + CRITICALITY ignore +} + +errorIndication HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +csg-membership-update HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CSGMembershipUpdate + PROCEDURE CODE id-CSGMembershipUpdate + CRITICALITY ignore +} + +tnlUpdate HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TNLUpdateRequest + SUCCESSFUL OUTCOME TNLUpdateResponse + UNSUCCESSFUL OUTCOME TNLUpdateFailure + PROCEDURE CODE id-TNLUpdate + CRITICALITY reject +} + +hNBConfigTransfer HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE HNBConfigTransferRequest + SUCCESSFUL OUTCOME HNBConfigTransferResponse + PROCEDURE CODE id-HNBConfigTransfer +``` + +``` + + CRITICALITY reject + } + + relocationComplete HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RelocationComplete + PROCEDURE CODE id-RelocationComplete + CRITICALITY ignore + } + + u-RNTIQuery HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE U-RNTIQueryRequest + SUCCESSFUL OUTCOME U-RNTIQueryResponse + PROCEDURE CODE id-U-RNTIQuery + CRITICALITY reject + } + + privateMessage HNBAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore + } + +END + +``` + +### 9.3.3 PDU Definitions + +``` + +-- ***** +-- +-- PDU definitions for HNBAP. +-- +-- ***** + +HNBAP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) hnbap(6) version1 (1) hnbap-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Cause, + CriticalityDiagnostics, + CSGMembershipStatus, + HNB-Location-Information, + +``` + +HNB-Identity, +Context-ID, +UE-Identity, +LAC, +RAC, +SAC, +CN-DomainIndicator, +IP-Address, +Registration-Cause, +UE-Capabilities, +PLMNIdentity, +CellIdentity, +RNC-ID, +CSG-ID, +HNB-Cell-Access-Mode, +BackoffTimer, +MuxPortNumber, +RABList, +HNBConfigInfo, +AccessResult, +Update-cause, +NeighbourInfoList, +NeighbourInfoRequestList, +PSC, +Tunnel-Information, +CELL-FACHMobilitySupport, +S-RNTIPrefix, +NeighbourIdentity, +NeighbourCellIdentityList, +URAIdentity, +URAIdentityList, +HNBCapacity, +AdditionalNeighbourInfoList, +U-RNTI, +UnknownU-RNTIIndication, +HNB-GWResponse + +FROM HNBAP-IEs + +ProtocolExtensionContainer{}, +ProtocolIE-ContainerList{}, +ProtocolIE-Container{}, +ProtocolIE-Single-Container{}, +PrivateIE-Container{}, +HNBAP-PRIVATE-IES, +HNBAP-PROTOCOL-EXTENSION, +HNBAP-PROTOCOL-IES + +FROM HNBAP-Containers + +``` + +id-Cause, +id-CriticalityDiagnostics, +id-CSGMembershipStatus, +id-HNB-Location-Information, +id-HNB-Identity, +id-Context-ID, +id-PLMNIdentity, +id-UE-Identity, +id-LAC, +id-RAC, +id-SAC, +id-UE-Capabilities, +id-Registration-Cause, +id-CellIdentity, +id-RNC-ID, +id-CSG-ID, +id-HNB-Cell-Access-Mode, +id-BackoffTimer, +id-Service-Area-For-Broadcast, +id-MuxPortNumber, +id-RABList, +id-HNBConfigInfo, +id-AccessResult, +id-Update-cause, +id-NeighbourInfoList, +id-NeighbourInfoRequestList, +id-Iurh-Signalling-TNL-Address, +id-PSC, +id-Tunnel-Information, +id-CELL-FACHMobilitySupport, +id-S-RNTIPrefix, +id-URAIdentity, +id-URAIdentityList, +id-NeighbourIdentity, +id-NeighbourCellIdentityList, +id-HNBCapacity, +id-AdditionalNeighbourInfoList, +id-U-RNTI, +id-UnknownU-RNTIIndication, +id-HNB-GWResponse + +FROM HNBAP-Constants; + +-- ***** +-- +-- HNB Register REQUEST +-- +-- ***** + +HNBRegisterRequest ::= SEQUENCE { + +``` + +``` + + protocolIEs ProtocolIE-Container { {HNBRegisterRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {HNBRegisterRequestExtensions} } OPTIONAL, + ... +} + +HNBRegisterRequestIEs HNBAP-PROTOCOL-IES ::= { + { ID id-HNB-Identity CRITICALITY reject TYPE HNB-Identity PRESENCE mandatory } | + { ID id-HNB-Location-Information CRITICALITY reject TYPE HNB-Location-Information PRESENCE mandatory } | + { ID id-PLMNIdentity CRITICALITY reject TYPE PLMNIdentity PRESENCE mandatory } | + { ID id-CellIdentity CRITICALITY reject TYPE CellIdentity PRESENCE mandatory } | + { ID id-LAC CRITICALITY reject TYPE LAC PRESENCE mandatory } | + { ID id-RAC CRITICALITY reject TYPE RAC PRESENCE mandatory } | + { ID id-SAC CRITICALITY reject TYPE SAC PRESENCE mandatory } | + { ID id-CSG-ID CRITICALITY reject TYPE CSG-ID PRESENCE optional } , + ... +} + +HNBRegisterRequestExtensions HNBAP-PROTOCOL-EXTENSION ::= { + { ID id-Service-Area-For-Broadcast CRITICALITY ignore EXTENSION SAC PRESENCE optional } | + { ID id-HNB-Cell-Access-Mode CRITICALITY reject EXTENSION HNB-Cell-Access-Mode PRESENCE optional } | + { ID id-PSC CRITICALITY ignore EXTENSION PSC PRESENCE optional } | + { ID id-Iurh-Signalling-TNL-Address CRITICALITY ignore EXTENSION IP-Address PRESENCE optional } | + { ID id-Tunnel-Information CRITICALITY ignore EXTENSION Tunnel-Information PRESENCE optional } | + { ID id-CELL-FACHMobilitySupport CRITICALITY ignore EXTENSION CELL-FACHMobilitySupport PRESENCE optional } | + { ID id-NeighbourCellIdentityList CRITICALITY ignore EXTENSION NeighbourCellIdentityList PRESENCE optional } | + { ID id-URAIdentityList CRITICALITY ignore EXTENSION URAIdentityList PRESENCE optional } | + { ID id-HNBCapacity CRITICALITY ignore EXTENSION HNBCapacity PRESENCE optional } , + ... +} + +-- ***** +-- +-- HNB Register Accept +-- +-- ***** + +HNBRegisterAccept ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HNBRegisterResponseIEs} }, + protocolExtensions ProtocolExtensionContainer { {HNBRegisterResponseExtensions} } OPTIONAL, + ... +} + +HNBRegisterResponseIEs HNBAP-PROTOCOL-IES ::= { + { ID id-RNC-ID CRITICALITY reject TYPE RNC-ID PRESENCE mandatory }, + ... +} + +HNBRegisterResponseExtensions HNBAP-PROTOCOL-EXTENSION ::= { + -- Extension for Release 9 to support CS Multiplexing -- + { ID id-MuxPortNumber CRITICALITY ignore EXTENSION MuxPortNumber PRESENCE optional } | + { ID id-Iurh-Signalling-TNL-Address CRITICALITY ignore EXTENSION IP-Address PRESENCE optional } | + { ID id-S-RNTIPrefix CRITICALITY ignore EXTENSION S-RNTIPrefix PRESENCE optional }, + +``` + +``` + + ... + } + + -- ***** + -- + -- HNB Register REJECT + -- + -- ***** + + HNBRegisterReject ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HNBRegisterRejectIEs} }, + protocolExtensions ProtocolExtensionContainer { {HNBRegisterRejectExtensions} } OPTIONAL, + ... + } + + HNBRegisterRejectIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-BackoffTimer CRITICALITY reject TYPE BackoffTimer PRESENCE conditional }, + -- This IE shall be present if the Cause IE is set to "Overload". + ... + } + + HNBRegisterRejectExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- HNB De- Register + -- + -- ***** + + HNBDe-Register ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HNBDe-RegisterIEs} }, + protocolExtensions ProtocolExtensionContainer { {HNBDe-RegisterExtensions} } OPTIONAL, + ... + } + + HNBDe-RegisterIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-BackoffTimer CRITICALITY reject TYPE BackoffTimer PRESENCE conditional }, + -- This IE shall be present if the Cause IE is set to "Overload". + ... + } + + HNBDe-RegisterExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +-- ***** +-- +-- UE Register REQUEST +-- +-- ***** + +UERegisterRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UERegisterRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {UERegisterRequestExtensions} } OPTIONAL, + ... +} + +UERegisterRequestIEs HNBAP-PROTOCOL-IES ::= { + { ID id-UE-Identity CRITICALITY reject TYPE UE-Identity PRESENCE mandatory } | + { ID id-Registration-Cause CRITICALITY ignore TYPE Registration-Cause PRESENCE mandatory } | + { ID id-UE-Capabilities CRITICALITY reject TYPE UE-Capabilities PRESENCE mandatory }, + ... +} + +UERegisterRequestExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- UE Register ACCEPT +-- +-- ***** + +UERegisterAccept ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UERegisterAcceptIEs} }, + protocolExtensions ProtocolExtensionContainer { {UERegisterAcceptExtensions} } OPTIONAL, + ... +} + +UERegisterAcceptIEs HNBAP-PROTOCOL-IES ::= { + { ID id-UE-Identity CRITICALITY reject TYPE UE-Identity PRESENCE mandatory } | + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory }, + ... +} + +UERegisterAcceptExtensions HNBAP-PROTOCOL-EXTENSION ::= { + { ID id-CSGMembershipStatus CRITICALITY reject EXTENSION CSGMembershipStatus PRESENCE optional }, + ... +} + +-- ***** +-- +-- UE Register REJECT +-- +-- ***** + +``` + +``` + +-- ***** +UEReject := SEQUENCE { + protocolIEs ProtocolIE-Container { {UERejectIEs} }, + protocolExtensions ProtocolExtensionContainer { {UERejectExtensions} } OPTIONAL, + ... +} + +UERejectIEs HNBAP-PROTOCOL-IES := { + { ID id-UE-Identity CRITICALITY reject TYPE UE-Identity PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +UERejectExtensions HNBAP-PROTOCOL-EXTENSION := { + ... +} + +-- ***** +-- +-- UE De-Register +-- +-- ***** + +UEDeRegister := SEQUENCE { + protocolIEs ProtocolIE-Container { {UEDeRegisterIEs} }, + protocolExtensions ProtocolExtensionContainer { {UEDeRegisterExtensions} } OPTIONAL, + ... +} + +UEDeRegisterIEs HNBAP-PROTOCOL-IES := { + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +UEDeRegisterExtensions HNBAP-PROTOCOL-EXTENSION := { + ... +} + +-- ***** +-- +-- CSG Membership Update +-- +-- ***** + +CSGMembershipUpdate := SEQUENCE { + protocolIEs ProtocolIE-Container { {CSGMembershipUpdateIEs} }, + protocolExtensions ProtocolExtensionContainer { {CSGMembershipUpdateExtensions} } OPTIONAL, + ... +} + +``` + +``` + +} + +CSGMembershipUpdateIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-CSGMembershipStatus CRITICALITY reject TYPE CSGMembershipStatus PRESENCE mandatory }, + ... +} + +CSGMembershipUpdateExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- TNL Update Request +-- +-- ***** + +TNLUpdateRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TNLUpdateRequestIEs } }, + protocolExtensions ProtocolExtensionContainer { { TNLUpdateExtensions } } OPTIONAL, + ... +} + +TNLUpdateRequestIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-RABList CRITICALITY reject TYPE RABList PRESENCE mandatory } | + { ID id-Update-cause CRITICALITY reject TYPE Update-cause PRESENCE mandatory } , + ... +} + +TNLUpdateExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- TNL UPDATE RESPONSE +-- +-- ***** + +TNLUpdateResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TNLUpdateResponseIEs } }, + protocolExtensions ProtocolExtensionContainer { { TNLUpdateResponseExtensions } } OPTIONAL, + ... +} + +TNLUpdateResponseIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } , + ... +} + +``` + +``` + +TNLUpdateResponseExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- TNL UPDATE FAILURE +-- +-- ***** + +TNLUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TNLUpdateFailureIEs} }, + protocolExtensions ProtocolExtensionContainer { {TNLUpdateFailureExtensions} } OPTIONAL, + ... +} + +TNLUpdateFailureIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Context-ID CRITICALITY reject TYPE Context-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } , + ... +} + +TNLUpdateFailureExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- HNB Configuration Transfer Request +-- +-- ***** + +HNBConfigTransferRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HNBConfigTransferRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {HNBConfigTransferRequestExtensions} } OPTIONAL, + ... +} + +HNBConfigTransferRequestIEs HNBAP-PROTOCOL-IES ::= { + { ID id-NeighbourInfoRequestList CRITICALITY reject TYPE NeighbourInfoRequestList PRESENCE mandatory } , + ... +} + +HNBConfigTransferRequestExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- HNB Configuration Transfer Response +-- +-- ***** + +``` + +``` + +-- ***** +HNBConfigTransferResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { HNBConfigTransferResponseIEs } }, + protocolExtensions ProtocolExtensionContainer { { HNBConfigTransferResponseExtensions } } OPTIONAL, + ... +} + +HNBConfigTransferResponseIEs HNBAP-PROTOCOL-IES ::= { + { ID id-NeighbourInfoList CRITICALITY reject TYPE NeighbourInfoList PRESENCE mandatory } , + ... +} + +HNBConfigTransferResponseExtensions HNBAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalNeighbourInfoList CRITICALITY ignore EXTENSION AdditionalNeighbourInfoList PRESENCE optional }, + ... +} + +-- ***** +-- +-- RELOCATION COMPLETE +-- +-- ***** + +RelocationComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { RelocationCompleteIEs } }, + protocolExtensions ProtocolExtensionContainer { { RelocationCompleteExtensions } } OPTIONAL, + ... +} + +RelocationCompleteIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Context-ID CRITICALITY ignore TYPE Context-ID PRESENCE mandatory } , + ... +} + +RelocationCompleteExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- ERROR INDICATION +-- +-- ***** + +ErrorIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ErrorIndicationIEs } }, + protocolExtensions ProtocolExtensionContainer { { ErrorIndicationExtensions } } OPTIONAL, + ... +} + +``` + +``` + +ErrorIndicationIEs HNBAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +ErrorIndicationExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- PRIVATE MESSAGE +-- +-- ***** + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container { {PrivateMessage-IEs} }, + ... +} + +PrivateMessage-IEs HNBAP-PRIVATE-IES ::= { + ... +} + +-- ***** +-- +-- U-RNTI Query Request +-- +-- ***** + +U-RNTIQueryRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {U-RNTIQueryRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {U-RNTIQueryRequestExtensions} } OPTIONAL, + ... +} + +U-RNTIQueryRequestIEs HNBAP-PROTOCOL-IES ::= { + { ID id-U-RNTI CRITICALITY reject TYPE U-RNTI PRESENCE mandatory } , + ... +} + +U-RNTIQueryRequestExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- U-RNTI Query Response +-- +-- ***** + +``` + +``` + +U-RNTIQueryResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { U-RNTIQueryResponseIEs} }, + protocolExtensions ProtocolExtensionContainer { { U-RNTIQueryResponseExtensions} } OPTIONAL, + ... +} + +U-RNTIQueryResponseIEs HNBAP-PROTOCOL-IES ::= { + { ID id-HNB-GWResponse CRITICALITY reject TYPE HNB-GWResponse PRESENCE mandatory } , + ... +} + +U-RNTIQueryResponseExtensions HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +### 9.3.4 Information Element Definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +HNBAP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) hnbap(6) version1 (1) hnbap-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors, + maxnoofRABs, + maxnoofNeighbours, + maxnoofIurhAddresses, + maxnoofAdditionalNeighbours, + maxnoofURAIdentities, + id-HNB-Internet-Information, + id-HNB-Cell-Identifier, + id-S-RNTIPrefix, + id-URAIdentityList + +FROM HNBAP-Constants + + Criticality, + ProcedureCode, + ProtocolIE-ID, + +``` + +``` + TriggeringMessage +FROM HNBAP-CommonDataTypes + + ProtocolExtensionContainer{}, + HNBAP-PROTOCOL-EXTENSION +FROM HNBAP-Containers; + +--A +Access-stratum-release-indicator ::= ENUMERATED {r99, + rel-4, rel-5, rel-6, rel-7, rel-8-and-beyond, + ...} + +AccessResult ::= ENUMERATED {allowed, notAllowed, ...} + +AltitudeAndDirection ::= SEQUENCE { + directionOfAltitude ENUMERATED {height, depth}, + altitude INTEGER (0..32767), + ... +} + +--B +BackoffTimer ::= INTEGER(0..3600) + +BindingID ::= OCTET STRING(SIZE(1..4,...)) + +--C +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + ... +} + +CauseRadioNetwork ::= ENUMERATED { + overload, + unauthorised-Location, + unauthorised-HNB, + hNB-parameter-mismatch, + invalid-UE-identity, + uE-not-allowed-on-this-HNB, + uE-unauthorised, + connection-with-UE-lost, + ue-RRC-release, + hNB-not-registered, + unspecified, + normal, + uE-relocated, + ue-registered-in-another-HNB, + ..., + no-neighbour-information-available, + iurh-connection-to-that-neighbour-not-Allowed +} +``` + +``` + +} + +CauseTransport ::= ENUMERATED { + transport-resource-unavailable, + unspecified, + ... +} + +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, + abstract-syntax-error-ignore-and-notify, + message-not-compatible-with-receiver-state, + semantic-error, + unspecified, + abstract-syntax-error-falsely-constructed-message, + ... +} + +CauseMisc ::= ENUMERATED { + processing-overload, + hardware-failure, + o-and-m-intervention, + unspecified, + ... +} + +CellIdentity ::= BIT STRING (SIZE (28)) + +CELL-FACHMobilitySupport ::= ENUMERATED { + supported, + ... +} + +Context-ID ::= BIT STRING (SIZE(24)) + +CriticalityDiagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + ... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + } + +CriticalityDiagnostics-IE-List-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnostics-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CSG-ID ::= BIT STRING (SIZE (27)) + +CSG-Capability ::= ENUMERATED { + csg-capable, + not-csg-capable, + ... + } + +CSGMembershipStatus ::= ENUMERATED { + member, + non-member, + ... + } + +CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + LAC LAC, + CI CI, + iE-Extensions ProtocolExtensionContainer { { CGI-ExtIEs } } OPTIONAL +} + +CGI-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +CI ::= OCTET STRING (SIZE (2)) + +CN-DomainIndicator ::= ENUMERATED { + cs-domain, + ps-domain + } + +--D +--E +ESN ::= BIT STRING (SIZE(32)) +--F +--G +GeographicalLocation ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + altitudeAndDirection AltitudeAndDirection, + iE-Extensions ProtocolExtensionContainer { { GeographicLocation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` + } + + GeographicLocation-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... + } + + GeographicalCoordinates ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + latitude INTEGER (0..8388607), + longitude INTEGER (-8388608..8388607), + iE-Extensions ProtocolExtensionContainer { {GeographicalCoordinates-ExtIEs} } OPTIONAL, + ... + } + + GeographicalCoordinates-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... + } + + GTP-TEI ::= OCTET STRING (SIZE (4)) + + --H + + HNBCapacity ::= INTEGER(0..1000) + + HNB-Cell-Access-Mode ::= ENUMERATED { + closed, + hybrid, + open, + ... + } + + HNB-Cell-Identifier ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + cellIdentity CellIdentity, + iE-Extensions ProtocolExtensionContainer { { HNB-Cell-Identifier-ExtIEs } } OPTIONAL, + ... + } + + HNB-Cell-Identifier-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... + } + + HNB-GWResponse ::= CHOICE { + hNB HNBConfigInfo, + macroRNC RNC-ID, + unknownU-RNTIIndication UnknownU-RNTIIndication, + ... + } + + HNB-RNL-Identity ::= CHOICE { + hNB-Identity-as-Cell-Identifier HNB-Cell-Identifier, + ... + } +``` + +``` + +} + +HNBConfigInfo := SEQUENCE { + hnb-RNL-Identity HNB-RNL-Identity, + configurationInformation ConfigurationInformation, + iE-Extensions ProtocolExtensionContainer { { HNBConfigInfo-ExtIEs } } OPTIONAL, + ... +} + +HNBConfigInfo-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +ConfigurationInformation ::= CHOICE { + provided HNBConfigurationInformationProvided, + missing HNBConfigurationInformationMissing, + ... +} + +HNBConfigurationInformationProvided ::= SEQUENCE { + psc PSC OPTIONAL, + cSG-ID CSG-ID OPTIONAL, + hNB-Cell-Access-Mode HNB-Cell-Access-Mode, + iurh-Signalling-TNL-AddressList Iurh-Signalling-TNL-AddressList, + iE-Extensions ProtocolExtensionContainer { { HNBConfigurationInformationProvided-ExtIEs } } OPTIONAL, + ... +} + +HNBConfigurationInformationProvided-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + { ID id-S-RNTIPrefix CRITICALITY ignore EXTENSION S-RNTIPrefix PRESENCE optional }| + { ID id-URAIdentityList CRITICALITY ignore EXTENSION URAIdentityList PRESENCE optional }, + ... +} + +HNBConfigurationInformationMissing ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { { HNBConfigurationInformationMissing-ExtIEs } } OPTIONAL, + ... +} + +HNBConfigurationInformationMissing-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +HNB-Location-Information ::= SEQUENCE { + macroCoverageInfo MacroCoverageInformation OPTIONAL, + geographicalCoordinates GeographicalLocation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { HNB-Location-Information-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` +HNB-Location-Information-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + -- Extension for release-8 to support IP address for location verification -- + {ID id-HNB-Internet-Information CRITICALITY reject EXTENSION IP-Address PRESENCE optional }, + ... +} + +HNB-Identity ::= SEQUENCE { + hNB-Identity-Info HNB-Identity-Info, + iE-Extensions ProtocolExtensionContainer { { HNB-Identity-ExtIEs } } OPTIONAL, + ... +} + +HNB-Identity-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +HNB-Identity-Info ::= OCTET STRING (SIZE (1..255)) + +--I + +IMEI ::= BIT STRING (SIZE(60)) + +IMSI ::= OCTET STRING (SIZE (3..8)) +-- Reference: 23.003 +IMSIDS41 ::= OCTET STRING (SIZE (5..7)) + +IMSIESN ::= SEQUENCE { + iMSIDS41 IMSIDS41, + eSN ESN +} + +IP-Address ::= SEQUENCE { + ipaddress CHOICE { + ipv4info Ipv4Address, + ipv6info Ipv6Address, + ... + }, + iE-Extensions ProtocolExtensionContainer { { IP-Address-ExtIEs } } OPTIONAL, + ... +} + +IP-Address-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +Ipv4Address ::= OCTET STRING (SIZE (4)) + +Ipv6Address ::= OCTET STRING (SIZE (16)) +``` + +``` +Iurh-Signalling-TNL-AddressList ::= SEQUENCE (SIZE(1..maxnoofIurhAddresses)) OF IP-Address + +--J +--K +--L +LAC ::= OCTET STRING(SIZE(2)) + +LAI ::= SEQUENCE { + pLMNID PLMNIdentity, + LAC LAC, + ... +} + +-- M + +MacroCoverageInformation ::= SEQUENCE { + cellIdentity MacroCellID, + iE-Extensions ProtocolExtensionContainer { { MacroCoverageInformation-ExtIEs } } OPTIONAL, + ... +} + +MacroCoverageInformation-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +MacroCellID ::= CHOICE { + uTRANCellID UTRANCellID, + gERANCellID CGI, + ... +} + +MuxPortNumber ::= INTEGER (1024..65535) + +--N + +NeighbourCellIdentityList ::= SEQUENCE (SIZE(0..maxnoofAdditionalNeighbours)) OF NeighbourIdentity + +NeighbourIdentity ::= CHOICE { + hNB-RNL-Identity HNB-RNL-Identity, + cell-ID CellIdentity, + ... +} + +NeighbourInfoList ::= SEQUENCE (SIZE(1..maxnoofNeighbours)) OF HNBConfigInfo + +AdditionalNeighbourInfoList ::= SEQUENCE (SIZE(1..maxnoofAdditionalNeighbours)) OF HNBConfigInfo + +NeighbourInfoRequestList ::= SEQUENCE (SIZE(1..maxnoofNeighbours)) OF NeighbourInfoRequestItem + +NeighbourInfoRequestItem ::= SEQUENCE { +``` + +``` + + hnb-RNL-Identity HNB-RNL-Identity, + iE-Extensions ProtocolExtensionContainer { { NeighbourInfoRequestItem-ExtIEs } } OPTIONAL, + ... +} + +NeighbourInfoRequestItem-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +--O +--P +PLMNIdentity ::= OCTET STRING (SIZE (3)) + +PSC ::= BIT STRING (SIZE(9)) + +PTMSI ::= BIT STRING (SIZE(32)) + +PTMSIRAI ::= SEQUENCE { + pTMSI PTMSI, + rAI RAI, + ... +} + +--Q +--R + +RAB-ID ::= BIT STRING (SIZE (8)) + +RABList ::= SEQUENCE (SIZE(1..maxnoofRABs)) OF RABListItem + +RABListItem ::= SEQUENCE { + rAB-ID RAB-ID, + old-transport-Info TransportInfo, + new-transport-Info TransportInfo, + cn-domain-indicator CN-DomainIndicator, + iE-Extensions ProtocolExtensionContainer { { RABListItem-ExtIEs } } OPTIONAL, + ... +} + +RABListItem-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +RAC ::= OCTET STRING(SIZE(1)) + +RAI ::= SEQUENCE { + LAI LAI, + rAC RAC, + ... +} + +``` + +``` +Registration-Cause ::= ENUMERATED { + emergency-call, + normal, + ..., + ue-relocation +} + +RNC-ID ::= INTEGER(0..65535) + +--S + +SAC ::= OCTET STRING(SIZE(2)) + +S-RNTIPrefix ::= BIT STRING(SIZE(1..16, ...)) + +--T +TMSILAI ::= SEQUENCE { + tMSI BIT STRING(SIZE (32)), + LAI LAI +} + +TMSIDS41 ::= OCTET STRING (SIZE (2..17)) + +TransportInfo ::= SEQUENCE { + transportLayerAddress TransportLayerAddress, + transportAssociation CHOICE { + gtp-TEI GTP-TEI, + bindingID BindingID, + ... + }, + iE-Extensions ProtocolExtensionContainer { { TransportInfo-ExtIEs } } OPTIONAL, + ... +} + +TransportInfo-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +TransportLayerAddress ::= BIT STRING(SIZE(1..160,...)) + +Tunnel-Information ::= SEQUENCE { + iP-Address IP-Address, + uDP-Port-Number UDP-Port-Number OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Tunnel-Information-ExtIEs } } OPTIONAL, + ... +} + +Tunnel-Information-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} +--U + +UDP-Port-Number ::= OCTET STRING(SIZE(2)) + +UE-Capabilities ::= SEQUENCE { + access-stratum-release-indicator Access-stratum-release-indicator, + csg-capability CSG-Capability, + iE-Extensions ProtocolExtensionContainer { { UE-Capabilities-ExtIEs } } OPTIONAL, + ... +} + +UE-Capabilities-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UTRANCellID ::= SEQUENCE { + lAC LAC, + rAC RAC, + pLMNIdentity PLMNIdentity, + uTRANCellID CellIdentity, + iE-Extensions ProtocolExtensionContainer { { UTRANCellID-ExtIEs } } OPTIONAL +} + +UTRANCellID-ExtIEs HNBAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-Identity ::= CHOICE { + iMSI IMSI, + tMSILAI TMSILAI, + pTMSIRAI PTMSIRAI, + iMEI IMEI, + eSN ESN, + iMSIDS41 IMSIDS41, + iMSIESN IMSIESN, + tMSIDS41 TMSIDS41, + ... +} + +Update-cause ::= ENUMERATED { + relocation-preparation, + ... +} + +URAIdentityList ::= SEQUENCE (SIZE (0..maxnoofURAIdentities)) OF URAIdentity + +``` + +``` + +URAIdentity ::= INTEGER(0..65535) + +U-RNTI ::= BIT STRING (SIZE (32)) + +UnknownU-RNTIIndication ::= ENUMERATED { + unknown, + ... +} + +--V +--W +--X +--Y +--Z + +END + +``` + +### 9.3.5 Common Definitions + +``` + +-- ************************************************************** +-- +-- Common definitions +-- +-- ************************************************************** + +HNBAP-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) hnbap (6) version1 (1) hnbap-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- Extension constants +-- +-- ************************************************************** + +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ************************************************************** +-- +-- Common Data Types +-- +-- ************************************************************** + +``` + +``` + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +PrivateIE-ID ::= CHOICE { + local INTEGER (0..65535), + global OBJECT IDENTIFIER +} + +ProcedureCode ::= INTEGER (0..255) + +ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs) + +TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome } + +END + +``` + +### 9.3.6 Constant Definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +HNBAP-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) hnbap(6) version1 (1) hnbap-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + ProcedureCode, + ProtocolIE-ID +FROM HNBAP-CommonDataTypes; + +-- ***** +-- +-- Elementary Procedures +-- +id-HNBRegister ProcedureCode ::= 1 +id-HNBDe-Register ProcedureCode ::= 2 +id-UERegister ProcedureCode ::= 3 +id-UEDe-Register ProcedureCode ::= 4 +id-ErrorIndication ProcedureCode ::= 5 + +``` + +``` + +id-privateMessage ProcedureCode ::= 6 +id-CSGMembershipUpdate ProcedureCode ::= 7 +id-TNLUpdate ProcedureCode ::= 9 +id-HNBConfigTransfer ProcedureCode ::= 10 +id-RelocationComplete ProcedureCode ::= 11 +id-U-RNTIQuery ProcedureCode ::= 14 + +-- ***** +-- +-- Lists +-- +-- ***** +maxNrOfErrors INTEGER ::= 256 +maxnoofRABs INTEGER ::= 256 +maxnoofAdditionalNeighbours INTEGER ::= 128 +maxnoofURAIdentities INTEGER ::= 8 +maxnoofNeighbours INTEGER ::= 32 +maxnoofIurhAddresses INTEGER ::= 3 + +-- ***** +-- +-- IEs +-- +-- ***** + +id-Cause ProtocolIE-ID ::= 1 +id-CriticalityDiagnostics ProtocolIE-ID ::= 2 +id-HNB-Identity ProtocolIE-ID ::= 3 +id-Context-ID ProtocolIE-ID ::= 4 +id-UE-Identity ProtocolIE-ID ::= 5 +id-LAC ProtocolIE-ID ::= 6 +id-RAC ProtocolIE-ID ::= 7 +id-HNB-Location-Information ProtocolIE-ID ::= 8 +id-PLMNIdentity ProtocolIE-ID ::= 9 +id-SAC ProtocolIE-ID ::= 10 +id-CellIdentity ProtocolIE-ID ::= 11 +id-Registration-Cause ProtocolIE-ID ::= 12 +id-UE-Capabilities ProtocolIE-ID ::= 13 +id-RNC-ID ProtocolIE-ID ::= 14 +id-CSG-ID ProtocolIE-ID ::= 15 +id-BackoffTimer ProtocolIE-ID ::= 16 +id-HNB-Internet-Information ProtocolIE-ID ::= 17 +id-HNB-Cell-Access-Mode ProtocolIE-ID ::= 18 +id-MuxPortNumber ProtocolIE-ID ::= 19 +id-Service-Area-For-Broadcast ProtocolIE-ID ::= 20 +id-CSGMembershipStatus ProtocolIE-ID ::= 21 +id-RABList ProtocolIE-ID ::= 22 +id-HNBConfigInfo ProtocolIE-ID ::= 23 +id-AccessResult ProtocolIE-ID ::= 25 +id-Update-cause ProtocolIE-ID ::= 26 +id-NeighbourInfoList ProtocolIE-ID ::= 27 +id-NeighbourInfoRequestList ProtocolIE-ID ::= 28 + +``` + +``` + +id-Iurh-Signalling-TNL-Address ProtocolIE-ID ::= 29 +id-PSC ProtocolIE-ID ::= 30 +id-HNB-Cell-Identifier ProtocolIE-ID ::= 31 +id-Tunnel-Information ProtocolIE-ID ::= 41 +id-CELL-FACHMobilitySupport ProtocolIE-ID ::= 42 +id-S-RNTIPrefix ProtocolIE-ID ::= 43 +id-URAIdentity ProtocolIE-ID ::= 44 +id-NeighbourIdentity ProtocolIE-ID ::= 45 +id-HNBCapacity ProtocolIE-ID ::= 46 +id-NeighbourCellIdentityList ProtocolIE-ID ::= 47 +id-AdditionalNeighbourInfoList ProtocolIE-ID ::= 48 +id-U-RNTI ProtocolIE-ID ::= 49 +id-UnknownU-RNTIIndication ProtocolIE-ID ::= 50 +id-HNB-GWResponse ProtocolIE-ID ::= 51 +id-URAIdentityList ProtocolIE-ID ::= 52 + +``` + +END + +### 9.3.7 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +HNBAP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) hnbap(6) version1 (1) hnbap-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + Presence, + PrivateIE-ID, + ProtocolIE-ID, + maxPrivateIEs, + maxProtocolExtensions, + maxProtocolIEs +FROM HNBAP-CommonDataTypes; + +``` + +``` +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +HNBAP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +HNBAP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Private IEs +-- +-- ***** + +HNBAP-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 {HNBAP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + + ProtocolIE-Single-Container {HNBAP-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + + ProtocolIE-Field {HNBAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id HNBAP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality HNBAP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value HNBAP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) + } + + -- ***** + -- + -- Container Lists for Protocol IE Containers + -- + -- ***** + + ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, HNBAP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + + -- ***** + -- + -- Container for Protocol Extensions + -- + -- ***** + + ProtocolExtensionContainer {HNBAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + + ProtocolExtensionField {HNBAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id HNBAP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality HNBAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue HNBAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) + } + + -- ***** + -- + +``` + +``` +-- Container for Private IEs +-- +-- ***** + +PrivateIE-Container {HNBAP-PRIVATE-IES : IEsSetParam} ::= + SEQUENCE (SIZE (1.. maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field {HNBAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id HNBAP-PRIVATE-IES.&id {{IEsSetParam}}, + criticality HNBAP-PRIVATE-IES.&criticality {{IEsSetParam}{@id}}, + value HNBAP-PRIVATE-IES.&Value {{IEsSetParam}{@id}} +} + +END +``` + +## 9.4 Message Transfer Syntax + +HNBAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [7]. + +# 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 HNBAP. It shows two boxes: 'HNBAP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right side of the boxes group error types: 'Logical Errors' and 'Abstract Syntax Errors' are associated with the HNBAP functional entity, while 'Transfer Syntax Errors' are associated with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting from the decoding stage to the functional entity.](453a1dc18dd2dd3334d19f453b04d11b_img.jpg) + +Diagram illustrating Protocol Errors in HNBAP. It shows two boxes: 'HNBAP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right side of the boxes group error types: 'Logical Errors' and 'Abstract Syntax Errors' are associated with the HNBAP functional entity, while 'Transfer Syntax Errors' are associated with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting from the decoding stage to the functional entity. + +**Figure 10.1-1: Protocol Errors in HNBAP** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional HNBAP entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE id); +2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; + +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the HNBAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE; +- Ignore IE and Notify Sender; +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, HNBAP 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 HNBAP-PROTOCOL-IES, HNBAP-PROTOCOL-IES-PAIR, HNBAP-PROTOCOL-EXTENSION or HNBAP-PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following: + +##### Reject IE: + +- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +##### Ignore IE and Notify Sender: + +- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +##### Ignore IE: + +- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +#### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +#### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +##### Reject IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +##### **Ignore IE and Notify Sender:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +##### **Ignore IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +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 the present document used by the receiver: + +#### **Reject IE:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +#### **Ignore IE and Notify Sender:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +#### **Ignore IE:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +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 IE's/IE groups containing the erroneous values. + +### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error; +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality “ignore and notify” have earlier occurred within the same procedure. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|---------------------------------------------------------------------------------------|--------| +| 42 | RP-080834 | | | Approved at TSG-RAN42 and placed under change control | 8.0.0 | +| 43 | RP-090244 | 0001 | | Add Object Identifier for HNBAP ASN.1 | 8.1.0 | +| 43 | RP-090081 | 0005 | 1 | Clarification on Uniqueness of Context ID | 8.1.0 | +| 43 | RP-090244 | 0007 | 1 | Update to HNB deregistration cause codes and descriptions | 8.1.0 | +| 43 | RP-090081 | 0008 | 1 | Update to HNB initiated UE deregistration cause code and description | 8.1.0 | +| 43 | RP-090082 | 0009 | 2 | Abnormal condition handling associated with HNB registration | 8.1.0 | +| 43 | RP-090082 | 0012 | 2 | Clarification on access control and inclusion of IMSI for UE registration. | 8.1.0 | +| 43 | RP-090244 | 0013 | 1 | Adding Cause Values for UE Deregistration | 8.1.0 | +| 43 | RP-090244 | 0014 | 1 | Updating of CSG Identity Length | 8.1.0 | +| 43 | RP-090082 | 0016 | 1 | Clarification on the HNB Identity | 8.1.0 | +| 43 | RP-090244 | 0018 | | Correction of wrong reference in TMSI-IE description | 8.1.0 | +| 43 | RP-090082 | 0019 | 2 | CSG-ID optional in HNB register request | 8.1.0 | +| 43 | RP-090082 | 0020 | 1 | Backoff timer for HNB registration | 8.1.0 | +| 44 | RP-090626 | 0022 | 2 | Correction to HNB Identity definition | 8.2.0 | +| 45 | RP-090769 | 0031 | 2 | ASN.1 correction for HNB Location Information IE | 8.3.0 | +| 46 | RP-091184 | 0033 | | Correction to ASN.1 references | 8.4.0 | +| 46 | RP-091184 | 0034 | 1 | Addition of cause value for Invalid UE identity | 8.4.0 | +| 12/2009 | - | - | - | Creation of version 9.0.0 based on version 8.4.0 | 9.0.0 | +| 46 | RP-091191 | 0027 | 4 | CS Mux port exchange | 9.0.0 | +| 46 | RP-091191 | 0030 | 4 | Support for multiple access mode HNBs | 9.0.0 | +| 46 | RP-091191 | 0037 | 1 | Introducing changes for supporting ETWS in Home Node B in 25.469 | 9.0.0 | +| 46 | RP-091191 | 0039 | 1 | Hybrid access signalling during UE and HNB registration | 9.0.0 | +| 47 | RP-100229 | 0041 | | Minor corrections for HNBAP | 9.1.0 | +| 47 | RP-100222 | 0042 | 2 | Extend ASRI for Release 9 | 9.1.0 | +| 47 | RP-100222 | 0045 | 1 | Introduction of Support for CSG membership notification | 9.1.0 | +| 48 | RP-100595 | 0049 | 2 | UE Registration for Open and Hybrid cells | 9.2.0 | +| 49 | RP-100909 | 0051 | 1 | Add missing cause value descriptions | 9.3.0 | +| 03/2011 | - | - | - | Creation of version 10.0.0 based on version 9.3.0 | 10.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.0 | +| 51 | RP-110226 | 0059 | | Correct definition of Cell-ID | 10.0.0 | +| 51 | RP-110231 | 0062 | 2 | Additional messages to support direct HNB-HNB HO in HNBAP | 10.0.0 | +| 51 | RP-110226 | 0063 | 2 | Identifying the Cell Identity | 10.0.0 | +| 52 | RP-110691 | 0065 | 1 | Removal of Access Query Procedure for Intra-CSG Handover | 10.1.0 | +| 52 | RP-110684 | 0067 | 1 | Correction of References | 10.1.0 | +| 52 | RP-110691 | 0068 | 1 | ASN.1 Corrections and Tabular alignment | 10.1.0 | +| 52 | RP-110691 | 0069 | 2 | Review Changes | 10.1.0 | +| 52 | RP-110691 | 0072 | 3 | Final specification of the provision of Iurh-connectivity related TNL addresses | 10.1.0 | +| 57 | RP-121131 | 0083 | | Corrections on the provision of TNL address for direct Iurh-connectivity | 10.2.0 | +| 09/2012 | - | - | - | Creation of version 11.0.0 based on version 10.2.0 | 11.0.0 | +| 57 | RP-121136 | 0084 | 1 | Introduction of connectivity between HNBs and RNCs via the HNB-GW for RNSAP signaling | 11.0.0 | +| 58 | RP-121724 | 0090 | | Add missing cause values for Iurh support | 11.1.0 | +| 58 | RP-121737 | 0091 | | Editorial and minor corrections | 11.1.0 | +| 58 | RP-121739 | 0093 | 2 | New Information for BBF access | 11.1.0 | +| 59 | RP-130212 | 0096 | 2 | Corrections from ASN.1 Review | 11.2.0 | +| 59 | RP-130213 | 0098 | 1 | PWS in HNB | 11.2.0 | +| 62 | RP-131908 | 0100 | 2 | Introduction of CELL_FACH, CELL_PCH and URA_PCH mobility support for HNBs | 12.0.0 | +| 64 | RP-140896 | 0103 | - | Transport Info in Iurh Relocation | 12.1.0 | +| 65 | RP-141608 | 0104 | 1 | Rapporteur's corrections | 12.2.0 | +| 66 | RP-142093 | 0105 | - | Rapporteur Review | 12.3.0 | +| 67 | RP-150356 | 0106 | 2 | Rapporteur Review-ASN.1 consistency check | 12.4.0 | +| 12/2015 | - | - | - | Creation of version 13.0.0 based on version 12.2.0 | 13.0.0 | +| 01/2016 | - | - | - | Typo in the change history table corrected | 13.0.1 | +| 71 | RP-160449 | 0108 | 1 | Rapporteur Review of TS 25.469 | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25903/03b9c04a0552e519e849210b8e2bf596_img.jpg b/marked/Rel-16/25_series/25903/03b9c04a0552e519e849210b8e2bf596_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c8bd097a9dac323c5f3632bbe2ea40034b8cfb0 --- /dev/null +++ b/marked/Rel-16/25_series/25903/03b9c04a0552e519e849210b8e2bf596_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:341bcd059783ddc3be699b2917f1fc0dd87e5991864337173b597ddbad18a19c +size 79198 diff --git a/marked/Rel-16/25_series/25903/056f93110af61f80a3f9526f06423d44_img.jpg b/marked/Rel-16/25_series/25903/056f93110af61f80a3f9526f06423d44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c10cf9c45b72c653de9881d0cbf705b8cd94e50b --- /dev/null +++ b/marked/Rel-16/25_series/25903/056f93110af61f80a3f9526f06423d44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c5999581b465ef72038638c9a597d6dee6b32da08aa305be333eb4d1a284ade +size 30133 diff --git a/marked/Rel-16/25_series/25903/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg b/marked/Rel-16/25_series/25903/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7569c8e8c8a68695afdf913eb05ea6cda961d3c --- /dev/null +++ b/marked/Rel-16/25_series/25903/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f2d2f3ef89139dd2535cceaca3d411f24fa210aed1eb290526d2e8e8e12a47e +size 120764 diff --git a/marked/Rel-16/25_series/25903/0867e5b136ab5cc8674c490d96f196e2_img.jpg b/marked/Rel-16/25_series/25903/0867e5b136ab5cc8674c490d96f196e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58bb934e41e600ba46395b37d48e155610b29482 --- /dev/null +++ b/marked/Rel-16/25_series/25903/0867e5b136ab5cc8674c490d96f196e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7baf3dc76ca422da1ca922270a87065e57087a0a57c4a7901b6462f0f6bf96ae +size 72713 diff --git a/marked/Rel-16/25_series/25903/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-16/25_series/25903/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..436c42266ba9c6a850d671ed5f244c362a01245a --- /dev/null +++ b/marked/Rel-16/25_series/25903/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23f0d89895f8c4330325b36da08e0d8e4e2ab609176bbf7e3de8f4f856f4f2db +size 73048 diff --git a/marked/Rel-16/25_series/25903/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/Rel-16/25_series/25903/0a8d173734e4e46c344178e8d21bcbc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51a04f540dca5e0b443c6f4ce00638df60dcabf5 --- /dev/null +++ b/marked/Rel-16/25_series/25903/0a8d173734e4e46c344178e8d21bcbc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee6b59420413627e40c56e846550ad390a46e8c0763bfdeefd82dc21b15ca8de +size 129658 diff --git a/marked/Rel-16/25_series/25903/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/25_series/25903/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce4e42b8bbb30a1cb31233aff639c47072078e65 --- /dev/null +++ b/marked/Rel-16/25_series/25903/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0e4ae31c8faf4b8e9badaa5460727c1a3d80402fb4241b0a5c3e1810924dac3 +size 129190 diff --git a/marked/Rel-16/25_series/25903/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg b/marked/Rel-16/25_series/25903/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f874b9110f9a2e734c5b02495215d048d05abfc2 --- /dev/null +++ b/marked/Rel-16/25_series/25903/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c685b314731efd418489f1b40f91a21d79b92e45a9b93bddeeb1e6ed71ffc9 +size 98235 diff --git a/marked/Rel-16/25_series/25903/0eb57eefa7cd45d30e68829ca8a03843_img.jpg b/marked/Rel-16/25_series/25903/0eb57eefa7cd45d30e68829ca8a03843_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9956f7b6d876e41b9fab735a3d0c1acb8beddad7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/0eb57eefa7cd45d30e68829ca8a03843_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d510b8980c493e7a2d007d8f1456b21c2933e78071175249657e1c77534ea484 +size 33951 diff --git a/marked/Rel-16/25_series/25903/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg b/marked/Rel-16/25_series/25903/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82974209e74583ebf51cd05ab941aecb259d1ea --- /dev/null +++ b/marked/Rel-16/25_series/25903/0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc242739de89561444dd1cdc89281295ddff91f8f2762192428c468769ebd29f +size 33916 diff --git a/marked/Rel-16/25_series/25903/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg b/marked/Rel-16/25_series/25903/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fa79576dcd49895a3dd99211927d7ea733facd1 --- /dev/null +++ b/marked/Rel-16/25_series/25903/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:017c84ca74e1f594d0170f3b20bbadce43d2fc65c0cbf3942e8d812dddb8fde3 +size 119912 diff --git a/marked/Rel-16/25_series/25903/174f912c9b31990c1b57e64f629e75ac_img.jpg b/marked/Rel-16/25_series/25903/174f912c9b31990c1b57e64f629e75ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2e70fdd375bc8cd38002020905da19f3ed5a8b3 --- /dev/null +++ b/marked/Rel-16/25_series/25903/174f912c9b31990c1b57e64f629e75ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb29d5607bc41ee644edf6b6c4123cc2c950585c9088f5c8cc8af7fec265027 +size 70823 diff --git a/marked/Rel-16/25_series/25903/18fcacec609d0fd4816b30201438a00a_img.jpg b/marked/Rel-16/25_series/25903/18fcacec609d0fd4816b30201438a00a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8af8b48145dd1e751d5f613850ab6a8efe913466 --- /dev/null +++ b/marked/Rel-16/25_series/25903/18fcacec609d0fd4816b30201438a00a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b3ba3d3a3343a7d87320e037aa067fddc3aa32ea9e867b72a9238306aaf6c38 +size 37500 diff --git a/marked/Rel-16/25_series/25903/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-16/25_series/25903/198d076da025c516aec8122a6ab7db20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..362e116ed15477c42464e9dfd292492a8f847ce8 --- /dev/null +++ b/marked/Rel-16/25_series/25903/198d076da025c516aec8122a6ab7db20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25992e64d176b5f096cedef27e63b01e9d631a11512d60b16ea3633cca539c43 +size 87001 diff --git a/marked/Rel-16/25_series/25903/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-16/25_series/25903/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d4896601e1ef2cf2772fad6995d89163118572b --- /dev/null +++ b/marked/Rel-16/25_series/25903/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a0be757a8a78d25c1fa34b34572f6de021c90d583a9b042b78cf559e4d8fa3b +size 150004 diff --git a/marked/Rel-16/25_series/25903/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-16/25_series/25903/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..106f2a688c906ef81574e35786d3e93a81302bd7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4cb7f99ae6021612afa3c9782201241f40772b4e851a7b7b4484db268641ee1 +size 165182 diff --git a/marked/Rel-16/25_series/25903/1bd6a020aa71784ed74367899560cbb9_img.jpg b/marked/Rel-16/25_series/25903/1bd6a020aa71784ed74367899560cbb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a84f2acac48d5f1da0b074d39eff93915e5663d --- /dev/null +++ b/marked/Rel-16/25_series/25903/1bd6a020aa71784ed74367899560cbb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc8a5981f2ccf06b825e55b01ef98ad0207369884c5ba56435e16df43cd4266a +size 14776 diff --git a/marked/Rel-16/25_series/25903/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-16/25_series/25903/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd3209082036e4d2f757aaa6c46acf4acb2d9367 --- /dev/null +++ b/marked/Rel-16/25_series/25903/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5aa68b72b72a166f7c8c6f247994ece584931c14f2c49867e14ab226d2f4a563 +size 122996 diff --git a/marked/Rel-16/25_series/25903/1d62d44c82c21f9056394d2fa042b8e9_img.jpg b/marked/Rel-16/25_series/25903/1d62d44c82c21f9056394d2fa042b8e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59f3c8af29b2f1b513ad73ceb2e1235f253f6fe5 --- /dev/null +++ b/marked/Rel-16/25_series/25903/1d62d44c82c21f9056394d2fa042b8e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04008719973b013f941f2d540d7344daf096946d036e5fc7c26e911475e2605e +size 42790 diff --git a/marked/Rel-16/25_series/25903/1f39c3dd17bd94ca9aa24f5d13a5605f_img.jpg b/marked/Rel-16/25_series/25903/1f39c3dd17bd94ca9aa24f5d13a5605f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b675d7627ab2d3c5466bdb4db682f59979864a29 --- /dev/null +++ b/marked/Rel-16/25_series/25903/1f39c3dd17bd94ca9aa24f5d13a5605f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fdd0b2319990cd7f31813ae1ef608f5845a1b9675836449de00c73f73a034b +size 34875 diff --git a/marked/Rel-16/25_series/25903/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-16/25_series/25903/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37848284a9232aa818fe62a88c57beacec16333d --- /dev/null +++ b/marked/Rel-16/25_series/25903/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0372a2bd75af7ca39ec40709939e7c60209915ebdb82b5b30ca2bd71b865b40 +size 63430 diff --git a/marked/Rel-16/25_series/25903/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-16/25_series/25903/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3b3d71713fda12428301c0cf3d597dbddd595e9 --- /dev/null +++ b/marked/Rel-16/25_series/25903/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea2cfdc6e18e0a44b242063226a76d8aba48908c45cad066fee3f1cdd61d4fd5 +size 154984 diff --git a/marked/Rel-16/25_series/25903/215e8d5e5ba38df215b55049d255b2ed_img.jpg b/marked/Rel-16/25_series/25903/215e8d5e5ba38df215b55049d255b2ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2b6bc6c9a86b5b780229b09db066e3973a9ac3b --- /dev/null +++ b/marked/Rel-16/25_series/25903/215e8d5e5ba38df215b55049d255b2ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42078025699ed876cd1cbdeba81b8a5442c43c0c7bed31083a70aa2754507356 +size 42752 diff --git a/marked/Rel-16/25_series/25903/21998d5161d55a19df06b0ea8d3b4e59_img.jpg b/marked/Rel-16/25_series/25903/21998d5161d55a19df06b0ea8d3b4e59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..398dfe908a81eb122e265530bd1a4190288251fd --- /dev/null +++ b/marked/Rel-16/25_series/25903/21998d5161d55a19df06b0ea8d3b4e59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15f693a3786fa15926be47fceef6e7f65d5d3effd74ada4ad29af621a08c3d7d +size 53580 diff --git a/marked/Rel-16/25_series/25903/2333c01db80c100fb3f8467a0717d99d_img.jpg b/marked/Rel-16/25_series/25903/2333c01db80c100fb3f8467a0717d99d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78d1390450f6fc0fda4b5692ca6d7fb96688b272 --- /dev/null +++ b/marked/Rel-16/25_series/25903/2333c01db80c100fb3f8467a0717d99d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16b21ce0bd05110d004eeefe48472840f015235e4e0095914df339fed1a1cb1b +size 70507 diff --git a/marked/Rel-16/25_series/25903/293fb0a508d182b518ea429927dfd343_img.jpg b/marked/Rel-16/25_series/25903/293fb0a508d182b518ea429927dfd343_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0723b523c474644c010971e4b2d6da91be5d551f --- /dev/null +++ b/marked/Rel-16/25_series/25903/293fb0a508d182b518ea429927dfd343_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7b8ceea6117eb98ac9b84dd9eedd9f9a0492087cb6aca8ef88cf6b801061e05 +size 40912 diff --git a/marked/Rel-16/25_series/25903/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg b/marked/Rel-16/25_series/25903/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4569b02b204561ea185d6ce77a29c985915a16fd --- /dev/null +++ b/marked/Rel-16/25_series/25903/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9da044ecedd76edbcaebd12c31684534120e4330c34db1a7d34916d8429ff8fe +size 41834 diff --git a/marked/Rel-16/25_series/25903/318f02285df33c4d38cdad30845972d4_img.jpg b/marked/Rel-16/25_series/25903/318f02285df33c4d38cdad30845972d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d04103b06e654af10c6dd80bedf03d5a42a29e4b --- /dev/null +++ b/marked/Rel-16/25_series/25903/318f02285df33c4d38cdad30845972d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29fe99a08c9d10f1bd7dbf4501a0461e2fa434694d0d9bef3d2237ec1562afe9 +size 131075 diff --git a/marked/Rel-16/25_series/25903/31c1877b2b8a3479b473e01d9856b689_img.jpg b/marked/Rel-16/25_series/25903/31c1877b2b8a3479b473e01d9856b689_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16799d38f2d3fe44f2e04448ee9f11c8abc19612 --- /dev/null +++ b/marked/Rel-16/25_series/25903/31c1877b2b8a3479b473e01d9856b689_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4f6f226d86d5d545936c9f0ab3a786f4b47a9d42f0cd05bc2eafb639f12e1c3 +size 93229 diff --git a/marked/Rel-16/25_series/25903/36f66d23ff319c73247feee55fd2dfb1_img.jpg b/marked/Rel-16/25_series/25903/36f66d23ff319c73247feee55fd2dfb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..854718289ff1bc5a7ee9ff4174b3145a09f4dea1 --- /dev/null +++ b/marked/Rel-16/25_series/25903/36f66d23ff319c73247feee55fd2dfb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34fb8a4a0b8c9fdda3975bb9c4bf641ee510a61107347295ee11121735c05fca +size 52123 diff --git a/marked/Rel-16/25_series/25903/3881b390d52f27a35faedfc170916c86_img.jpg b/marked/Rel-16/25_series/25903/3881b390d52f27a35faedfc170916c86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bd4f711536c8882c7657e4ef069a6530da09c85 --- /dev/null +++ b/marked/Rel-16/25_series/25903/3881b390d52f27a35faedfc170916c86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:750948ab31fe2bfe2f6039cd98b2ec89de16e171708d9697ae7a5a8bacc4fc6e +size 38993 diff --git a/marked/Rel-16/25_series/25903/3d6f4088e319484d4e81fb68cd8520a3_img.jpg b/marked/Rel-16/25_series/25903/3d6f4088e319484d4e81fb68cd8520a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcabefc1bbfb63bc85c87df73115e8c2fbe31ff --- /dev/null +++ b/marked/Rel-16/25_series/25903/3d6f4088e319484d4e81fb68cd8520a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f49d67704fa6a947545d1c77b4359e9678b5b957d0525d75772d8482e224c6d +size 55212 diff --git a/marked/Rel-16/25_series/25903/3d9c6095cbd57a6fd5fe677f428d4a07_img.jpg b/marked/Rel-16/25_series/25903/3d9c6095cbd57a6fd5fe677f428d4a07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8074c65681b27e5f935b93f08aaee4e002e0ea1 --- /dev/null +++ b/marked/Rel-16/25_series/25903/3d9c6095cbd57a6fd5fe677f428d4a07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b9538189cf33773995959ddbacabc9a08d559e09994539cf6b84da51608641d +size 45871 diff --git a/marked/Rel-16/25_series/25903/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/Rel-16/25_series/25903/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ed23f8001e04b6ef733360c1bb502170ce6a2e6 --- /dev/null +++ b/marked/Rel-16/25_series/25903/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea1c1660fb66f8a5175f1d2ca413294f6d9ee9952e5c9fe5a22f8e93b212e5eb +size 120818 diff --git a/marked/Rel-16/25_series/25903/46b141b0e4f1e0bf48a036fc6dfc7d33_img.jpg b/marked/Rel-16/25_series/25903/46b141b0e4f1e0bf48a036fc6dfc7d33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d13e3e56332f867531b1695158d29dde59b33e --- /dev/null +++ b/marked/Rel-16/25_series/25903/46b141b0e4f1e0bf48a036fc6dfc7d33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000a726e6bb7359afc0abb1d4110523c2a20bab541f13b96444fcfacf57fa7bc +size 74835 diff --git a/marked/Rel-16/25_series/25903/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/25_series/25903/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2b9a851a3675d9d579dc7bbcc5b7c68937fe5fa --- /dev/null +++ b/marked/Rel-16/25_series/25903/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:154650195e573a8b5b412ee20866fc3b87a8e9651459d2514b9e4ef448375f53 +size 26964 diff --git a/marked/Rel-16/25_series/25903/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-16/25_series/25903/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca8e583fb497b9f594aa29dd685875d8c14c8c1 --- /dev/null +++ b/marked/Rel-16/25_series/25903/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dc3b07645a4d68030465f5cd56598c57e45a00eac78332cc0bc1e7d37d45553 +size 67917 diff --git a/marked/Rel-16/25_series/25903/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-16/25_series/25903/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c07fbbc855ae414bb56aabcac5e958c88cd097b --- /dev/null +++ b/marked/Rel-16/25_series/25903/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11f57c5903880cbe7a78450bfc08c29099cad0d28cd9ec49b3383f634213789f +size 71156 diff --git a/marked/Rel-16/25_series/25903/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-16/25_series/25903/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2cca60c2f949c85f445bbf0866e93a931e0b3e --- /dev/null +++ b/marked/Rel-16/25_series/25903/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cef949d00e8bc893fddeaf2c1f2261989d01127c38f096267a9c4c597463f4e0 +size 64931 diff --git a/marked/Rel-16/25_series/25903/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg b/marked/Rel-16/25_series/25903/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9847ef6a9afd5180367a93c7c44f58062eb166b9 --- /dev/null +++ b/marked/Rel-16/25_series/25903/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196a12090c5b38a910e35854022eb8c5790171e754d7db435cc3e5ec1d5ac89c +size 7215 diff --git a/marked/Rel-16/25_series/25903/57261b803cf2db0e8feca169cb2c416b_img.jpg b/marked/Rel-16/25_series/25903/57261b803cf2db0e8feca169cb2c416b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0de87e43003f06c563c7f4a81f44e29b7d77e7b7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/57261b803cf2db0e8feca169cb2c416b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71bbcbb9cc845c1eae83fdbc060b992ff391ec05ad8eac2df0e0287b70c75977 +size 116279 diff --git a/marked/Rel-16/25_series/25903/578d2763eaf3edf3f1bd6657455ad54a_img.jpg b/marked/Rel-16/25_series/25903/578d2763eaf3edf3f1bd6657455ad54a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0924fb40ea3764c4faa47eb3e168b623daff3559 --- /dev/null +++ b/marked/Rel-16/25_series/25903/578d2763eaf3edf3f1bd6657455ad54a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf1659094c7a2d8baf6da2b8eb8b947a180a00c9d707554d7330930022d395d1 +size 83458 diff --git a/marked/Rel-16/25_series/25903/5ae0af74768ab8a326191d61781d98e6_img.jpg b/marked/Rel-16/25_series/25903/5ae0af74768ab8a326191d61781d98e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d4abaf2781e340cb934cba2d012cc2c7ef90c0f --- /dev/null +++ b/marked/Rel-16/25_series/25903/5ae0af74768ab8a326191d61781d98e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dc485ff9bc2bff511fe83ed8d486892cbbb730d3a5531240afc18d8bbe6f7cc +size 88311 diff --git a/marked/Rel-16/25_series/25903/5b29df6b4f2a461b8c039fe47053fa65_img.jpg b/marked/Rel-16/25_series/25903/5b29df6b4f2a461b8c039fe47053fa65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2b66eae1638f5feb3948f2fb661db007082d795 --- /dev/null +++ b/marked/Rel-16/25_series/25903/5b29df6b4f2a461b8c039fe47053fa65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8009d4581e28205f1f8a3cc8a575302d07823081b8c67e91f3636d3dd9f29de1 +size 36538 diff --git a/marked/Rel-16/25_series/25903/6334c962f5e106e3331e59946e4d166e_img.jpg b/marked/Rel-16/25_series/25903/6334c962f5e106e3331e59946e4d166e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb99a1b2607320a5d046e963e95c3e33f771925e --- /dev/null +++ b/marked/Rel-16/25_series/25903/6334c962f5e106e3331e59946e4d166e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a32ffa54e6f712d769b24003a83769087a89cdfb5745c2c1c9d5d5703198e87 +size 50702 diff --git a/marked/Rel-16/25_series/25903/67a77127096ea6c8cb868e800021d803_img.jpg b/marked/Rel-16/25_series/25903/67a77127096ea6c8cb868e800021d803_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05ec168daf801c3ec566b07fe0f116e6ab4ec699 --- /dev/null +++ b/marked/Rel-16/25_series/25903/67a77127096ea6c8cb868e800021d803_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8bf1cd73244f67ba4f2ffe0d955fc9f114f2126024db3a0bd31efb3a1deb092 +size 47580 diff --git a/marked/Rel-16/25_series/25903/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg b/marked/Rel-16/25_series/25903/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be890a333ae0a0dc56a890ccac8aec5ac59ddbf5 --- /dev/null +++ b/marked/Rel-16/25_series/25903/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ba47c84cc71c39b68beac688f9ce792c7aeb6a8c6c2d174558f20429ab7cf7b +size 34211 diff --git a/marked/Rel-16/25_series/25903/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-16/25_series/25903/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8aeecade24377fbd979d36d322410adcfad2f48 --- /dev/null +++ b/marked/Rel-16/25_series/25903/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec168080d640bce8adfbef548aa4b239b863ef30d5e9e198189979d2216cd746 +size 120629 diff --git a/marked/Rel-16/25_series/25903/70546cb98239089866510133c7fbc169_img.jpg b/marked/Rel-16/25_series/25903/70546cb98239089866510133c7fbc169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a87d85d2469570102d123da8ba117ce70a96eb0 --- /dev/null +++ b/marked/Rel-16/25_series/25903/70546cb98239089866510133c7fbc169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29fa77fd0bb511dcf1cd3786e66e2ee4f1c3a641efb668d8c1067cd18235cfc0 +size 66066 diff --git a/marked/Rel-16/25_series/25903/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-16/25_series/25903/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..055dc4a0f293bc2a0f552b7c101071c61b9ac9e3 --- /dev/null +++ b/marked/Rel-16/25_series/25903/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:350b707836182b43d36a9ba6ef4f8f25ddb11d34160015d07d3c5000cb04bece +size 32646 diff --git a/marked/Rel-16/25_series/25903/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg b/marked/Rel-16/25_series/25903/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..306584bf9a449b1783660b07409249703bbe9298 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2015ed9c0f7a612f0c8febdca629f309cbfae6d8c4b4beaed69f8ee3bc37779e +size 113141 diff --git a/marked/Rel-16/25_series/25903/73c3a69fa000ad227906a39c79b86dbc_img.jpg b/marked/Rel-16/25_series/25903/73c3a69fa000ad227906a39c79b86dbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edfa0d28d9d1050765f115ce27b12d67c40a1080 --- /dev/null +++ b/marked/Rel-16/25_series/25903/73c3a69fa000ad227906a39c79b86dbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c305601bd9c9cc0bf852926796cdc8f0cd4723d8de4909c106c359aada885183 +size 117084 diff --git a/marked/Rel-16/25_series/25903/73e5c1369b67ddccf657e54d0434cc2b_img.jpg b/marked/Rel-16/25_series/25903/73e5c1369b67ddccf657e54d0434cc2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d42eeb57219f803d85821f2c61d83bcf1f70732 --- /dev/null +++ b/marked/Rel-16/25_series/25903/73e5c1369b67ddccf657e54d0434cc2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc88d0338aa26a77ec2f26b30746f6a58709dcff819d7e77c5747bbfae6bea2 +size 75464 diff --git a/marked/Rel-16/25_series/25903/74448f9178da618d823e5a5dadc56fb5_img.jpg b/marked/Rel-16/25_series/25903/74448f9178da618d823e5a5dadc56fb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e6cb911553059407850d2cec03b0a52cf3c0a99 --- /dev/null +++ b/marked/Rel-16/25_series/25903/74448f9178da618d823e5a5dadc56fb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0178665af54ceaaa24c6e393744feb9d2856f088269f630a241c088c0413bfb4 +size 70728 diff --git a/marked/Rel-16/25_series/25903/7498bf530d9e13633524982a399d4439_img.jpg b/marked/Rel-16/25_series/25903/7498bf530d9e13633524982a399d4439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f4c98689f08237cafb9fd2e8aa3fead9db53948 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7498bf530d9e13633524982a399d4439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd8efe112265142481962557b2eed4c2d663415816a53ddedfff5ee4f55eb9cd +size 37198 diff --git a/marked/Rel-16/25_series/25903/7a0281fac8690d8894ef1cb92d1a7704_img.jpg b/marked/Rel-16/25_series/25903/7a0281fac8690d8894ef1cb92d1a7704_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..156049cc8ecf206ae00d3480db42fec2a048de00 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7a0281fac8690d8894ef1cb92d1a7704_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f660d0bd915137123a870d70633aebb0ebf5f371fdf782cc859a2ffb92e6b48 +size 80128 diff --git a/marked/Rel-16/25_series/25903/7b24462ab2c9a9e6ed5937f2c1195f75_img.jpg b/marked/Rel-16/25_series/25903/7b24462ab2c9a9e6ed5937f2c1195f75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..843e8760bb5c2b1869ba632428a7b3c2e6ffd1e7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7b24462ab2c9a9e6ed5937f2c1195f75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1dc7fb64b9fbfe04bba11c43976767568fd360c7a7ac00d0ebc82eddcd25d82 +size 31072 diff --git a/marked/Rel-16/25_series/25903/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/25_series/25903/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f61aa3f3e0592c33c6f404ea028772d1436f84b5 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96a23839a82de2f1702f2a420fd1eb389629b9aee95d385069ad5d25efa4c917 +size 35441 diff --git a/marked/Rel-16/25_series/25903/7f687094e6abe34a9cf491942b296d9a_img.jpg b/marked/Rel-16/25_series/25903/7f687094e6abe34a9cf491942b296d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24bcb897d47ea48c08355f6113df3a40c02f2741 --- /dev/null +++ b/marked/Rel-16/25_series/25903/7f687094e6abe34a9cf491942b296d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b559f6a770bf512781a21dee6d5a8c162791c48dac17b090a20b9fdb8bc4e9 +size 120428 diff --git a/marked/Rel-16/25_series/25903/808fbf3058e19e39757a0a84c7796059_img.jpg b/marked/Rel-16/25_series/25903/808fbf3058e19e39757a0a84c7796059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b8a7718dd531e2a0a3562042ed6ade4a9cce580 --- /dev/null +++ b/marked/Rel-16/25_series/25903/808fbf3058e19e39757a0a84c7796059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da4479edd388d0f37c6db00286e229ae7fd6f2983659bc7ff38f99a102d694ea +size 72168 diff --git a/marked/Rel-16/25_series/25903/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Rel-16/25_series/25903/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8faa0c11ffcfb8db682e7be8fb7086382340c77 --- /dev/null +++ b/marked/Rel-16/25_series/25903/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eee678ab28a94a42b5f2a8c497ba30daadf9935360e5bdea6ff134bfec00bc0f +size 67311 diff --git a/marked/Rel-16/25_series/25903/85b10db535b22e64c7d37f362705ddbf_img.jpg b/marked/Rel-16/25_series/25903/85b10db535b22e64c7d37f362705ddbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..243bfc7a62b5ac49abcec42d5cf3bf1ad1bf340d --- /dev/null +++ b/marked/Rel-16/25_series/25903/85b10db535b22e64c7d37f362705ddbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93748a73648bf5bf1ab5870b9fe78d1dc185f4a51223cb50f952936f53f4f342 +size 94902 diff --git a/marked/Rel-16/25_series/25903/86e1f8551d4922ea8fa197f96fe4098b_img.jpg b/marked/Rel-16/25_series/25903/86e1f8551d4922ea8fa197f96fe4098b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..096841e2ee3f0890bc1b28cebbb3b39d65144a44 --- /dev/null +++ b/marked/Rel-16/25_series/25903/86e1f8551d4922ea8fa197f96fe4098b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e780d9ec26c8c73001f383049821bc4890664caf46f8fdcd9910664fd0aa5ad4 +size 32117 diff --git a/marked/Rel-16/25_series/25903/8e21461e0c9384ec60322bedb1b1ab17_img.jpg b/marked/Rel-16/25_series/25903/8e21461e0c9384ec60322bedb1b1ab17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6004605dd46e03be733f3f95d4e019046139673 --- /dev/null +++ b/marked/Rel-16/25_series/25903/8e21461e0c9384ec60322bedb1b1ab17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32fd576255dce16d6b576a8651651db4b52a79fbe80824b3c994ae33387d7cda +size 73249 diff --git a/marked/Rel-16/25_series/25903/8e395c7d3a0249c410ef3c5a4f666170_img.jpg b/marked/Rel-16/25_series/25903/8e395c7d3a0249c410ef3c5a4f666170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7c9348187b462dc4bfc8fa46b46616b9d79b509 --- /dev/null +++ b/marked/Rel-16/25_series/25903/8e395c7d3a0249c410ef3c5a4f666170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2aa524b6bd174491c86c9eb1f123c79649b3b354877ecf986d4d85cfb9241759 +size 67302 diff --git a/marked/Rel-16/25_series/25903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-16/25_series/25903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe6912d3cb46ded8c51d4781b3159bffdd17934b --- /dev/null +++ b/marked/Rel-16/25_series/25903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b286cf1d8cd4127ee1948482ff2cefce1c1d136db06f4847dcf05fd370a47725 +size 124101 diff --git a/marked/Rel-16/25_series/25903/9600eb9b09749d5b8a30898a75407ac8_img.jpg b/marked/Rel-16/25_series/25903/9600eb9b09749d5b8a30898a75407ac8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc19dfb8f3fa0c286aa78ad152530804db6b1cb6 --- /dev/null +++ b/marked/Rel-16/25_series/25903/9600eb9b09749d5b8a30898a75407ac8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1425cdc4c5f762e09ab107f873fee7a1dc9d0e7b52d136087d97900137b89870 +size 51922 diff --git a/marked/Rel-16/25_series/25903/96b654cdbd1138c5463c69c8f35cd3ed_img.jpg b/marked/Rel-16/25_series/25903/96b654cdbd1138c5463c69c8f35cd3ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6776d7aca21ed9648c49707d4a76db6a36405825 --- /dev/null +++ b/marked/Rel-16/25_series/25903/96b654cdbd1138c5463c69c8f35cd3ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cb4c441b63c4c4d3b012e68102036ac6b7a126989ddea5c542c6d521a23bfa0 +size 50709 diff --git a/marked/Rel-16/25_series/25903/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg b/marked/Rel-16/25_series/25903/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13ee6a46e01c61199e1219b4b841b02bbb97b891 --- /dev/null +++ b/marked/Rel-16/25_series/25903/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:941e74bc77410295e6d7825cfa573cdee461b1349bc8a07edb833a031960ca63 +size 50710 diff --git a/marked/Rel-16/25_series/25903/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-16/25_series/25903/9f92854fe6ecaf47760515c891a4fccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bf99048630802f0c9c6039387209e9e27409e72 --- /dev/null +++ b/marked/Rel-16/25_series/25903/9f92854fe6ecaf47760515c891a4fccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34d6d8afee28ff0e6e97ade409a64207fc078534dc14bc1983f76f2cd80f2736 +size 80939 diff --git a/marked/Rel-16/25_series/25903/9fb243582ed94533ea157cb66a878190_img.jpg b/marked/Rel-16/25_series/25903/9fb243582ed94533ea157cb66a878190_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c87f32868938c7a16d7ae6b2ab6375513af3a01b --- /dev/null +++ b/marked/Rel-16/25_series/25903/9fb243582ed94533ea157cb66a878190_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76c6c1ee2439440aa8198ba7714c1c3c59534ed3abf802ef386499dba9d56915 +size 147396 diff --git a/marked/Rel-16/25_series/25903/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/marked/Rel-16/25_series/25903/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea0e672c9386879d8f12c9dcee6ffabbb46f848f --- /dev/null +++ b/marked/Rel-16/25_series/25903/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:854eeabdf92e67c725190d1514c28056a6db20c322c4c720616ded2f2fd70409 +size 35675 diff --git a/marked/Rel-16/25_series/25903/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/25_series/25903/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c46bdaa7d57c28f692a2ab07a6feda2b7e0f64 --- /dev/null +++ b/marked/Rel-16/25_series/25903/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfc61d6bc5f0fdfd96e68a118cff63afd103d5499254167953f0febdec0a097b +size 18751 diff --git a/marked/Rel-16/25_series/25903/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-16/25_series/25903/a289b64f80c6df506c0c55d553fc4496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9bdbe7c6f81d6b4b4b22baf42b574014917173d --- /dev/null +++ b/marked/Rel-16/25_series/25903/a289b64f80c6df506c0c55d553fc4496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbdf81af28ca95d7ef6ec1a22789f4486427df22b06300553fce84e1749c9eca +size 123070 diff --git a/marked/Rel-16/25_series/25903/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg b/marked/Rel-16/25_series/25903/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c527d0397e3e7f520a1b12b610e9fddfce638f98 --- /dev/null +++ b/marked/Rel-16/25_series/25903/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d0e66c2713d429825d9bdc4e32daeec521df3546ec2f41cdf22124ecb0a928f +size 47690 diff --git a/marked/Rel-16/25_series/25903/a72d02d4e6305689a79b46d36739cd51_img.jpg b/marked/Rel-16/25_series/25903/a72d02d4e6305689a79b46d36739cd51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fac4a379b9f96bf3502a2330ebcdc22e5d656107 --- /dev/null +++ b/marked/Rel-16/25_series/25903/a72d02d4e6305689a79b46d36739cd51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11343cce6bf1ca6732ac548d7a60aa922aa2d734afcb5b10dedb84b650965521 +size 74571 diff --git a/marked/Rel-16/25_series/25903/a8b7b9a2533d0d71d6f7a922c5456ff4_img.jpg b/marked/Rel-16/25_series/25903/a8b7b9a2533d0d71d6f7a922c5456ff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf8d6b140c5eeac8d99d37ca51f1fe805650ff2a --- /dev/null +++ b/marked/Rel-16/25_series/25903/a8b7b9a2533d0d71d6f7a922c5456ff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04f4516ebbae585ece0487c438a54fa6da702e664f0811781bc5be8ca43a9c06 +size 46670 diff --git a/marked/Rel-16/25_series/25903/b18c42a97abc39df27fd810bc267f2fc_img.jpg b/marked/Rel-16/25_series/25903/b18c42a97abc39df27fd810bc267f2fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a29565945e3d99a03bf745c287c4a630db66f20e --- /dev/null +++ b/marked/Rel-16/25_series/25903/b18c42a97abc39df27fd810bc267f2fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f7902a50d2b69085bfc60b64dd70e2e04a8969df2d1bcfdb5c66d74f682c95b +size 34880 diff --git a/marked/Rel-16/25_series/25903/b3447f89ba9220b2e6aa861f6ed322cb_img.jpg b/marked/Rel-16/25_series/25903/b3447f89ba9220b2e6aa861f6ed322cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..870e528c34bba82f9f4a2aedd81f6c0b3c0ee631 --- /dev/null +++ b/marked/Rel-16/25_series/25903/b3447f89ba9220b2e6aa861f6ed322cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45abf34c5859d6e72fc02aa02daf421d82de62c540080581f6e7dc2b8ef974db +size 41663 diff --git a/marked/Rel-16/25_series/25903/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/25_series/25903/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57a32a9fab73ecdbf4c081e29e0caf35a0b33551 --- /dev/null +++ b/marked/Rel-16/25_series/25903/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8447723b7560abcfd08822e38934ad6a9a3a8aec782098eb2f8ecb4e1f2ab325 +size 69020 diff --git a/marked/Rel-16/25_series/25903/b53cd45f703a6a98fa703b754a69589a_img.jpg b/marked/Rel-16/25_series/25903/b53cd45f703a6a98fa703b754a69589a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fdf5603cb765f989266d7e12a5bb85c7b755199 --- /dev/null +++ b/marked/Rel-16/25_series/25903/b53cd45f703a6a98fa703b754a69589a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a61aca3d5681e3d0717d936ec0672ac4289328b8bfd216fd7479ae7f3c30379b +size 39767 diff --git a/marked/Rel-16/25_series/25903/b8261918596971c3801af23435c5ea50_img.jpg b/marked/Rel-16/25_series/25903/b8261918596971c3801af23435c5ea50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..711ed1193c4465dc9186dea294801c557c06eb3c --- /dev/null +++ b/marked/Rel-16/25_series/25903/b8261918596971c3801af23435c5ea50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87c2432274c17a6f962edff4bd7bd83c14826999334926a88c5ac41b23a474d1 +size 128422 diff --git a/marked/Rel-16/25_series/25903/baa4bab83368a423293c97f9e4ae8932_img.jpg b/marked/Rel-16/25_series/25903/baa4bab83368a423293c97f9e4ae8932_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e4419e68313a3c88239eebe400c62084aa5c369 --- /dev/null +++ b/marked/Rel-16/25_series/25903/baa4bab83368a423293c97f9e4ae8932_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a716877d2bd9e8462fb93267bfa8a08f1fa01391bed6984767d443251dcc64c +size 84444 diff --git a/marked/Rel-16/25_series/25903/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-16/25_series/25903/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8d9a02dba9f2478f741504de50ea2a0694d6894 --- /dev/null +++ b/marked/Rel-16/25_series/25903/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:550877372c04ab82ca4acaa3c7cd779c1b235c8de4e9619405dce622769d4e47 +size 102818 diff --git a/marked/Rel-16/25_series/25903/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg b/marked/Rel-16/25_series/25903/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97467a98fd5c269b991ab1bec33e03f36fb50513 --- /dev/null +++ b/marked/Rel-16/25_series/25903/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:632952eee92a847574ae9cbc630efa1753c92a75d3905cb8882487a7c7874ce6 +size 41154 diff --git a/marked/Rel-16/25_series/25903/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-16/25_series/25903/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55f55ec98c23293d873f4a3ee8bd544a9e3c0f06 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be53898b6bc4b457c2d3f85603ca5c791610c5aa186f9a01cc4bc0aadc22ad01 +size 25173 diff --git a/marked/Rel-16/25_series/25903/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-16/25_series/25903/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b8fa621fba49ca72c5972de97a4ff9c18a7176d --- /dev/null +++ b/marked/Rel-16/25_series/25903/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d26ff4f8037bb43f17bb8be625a75b14c957006fecf66acace51ae369f89389d +size 124573 diff --git a/marked/Rel-16/25_series/25903/c21fe89d8034ec5b80bd47c1cd710202_img.jpg b/marked/Rel-16/25_series/25903/c21fe89d8034ec5b80bd47c1cd710202_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..254977fe5482ec241cb648dc3fd774cabc4ccb91 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c21fe89d8034ec5b80bd47c1cd710202_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f10503f9b0592bcaaf8f3aec9030ce764655a28a4f354b51a9eda4e0c85f5e +size 64786 diff --git a/marked/Rel-16/25_series/25903/c301bbb71a13e5fb2800c48e300bafb1_img.jpg b/marked/Rel-16/25_series/25903/c301bbb71a13e5fb2800c48e300bafb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a411d17d7ccf5c1ef1ec7714d895bdb2d02f8dd3 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c301bbb71a13e5fb2800c48e300bafb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bcd4e6f16b47ad83bbc52c01fbc530ba4ab7d1d5adde68d6b233b674efd8876 +size 73919 diff --git a/marked/Rel-16/25_series/25903/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-16/25_series/25903/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81699aa0eb6c242b295b253a3f0352bc2cdedb9b --- /dev/null +++ b/marked/Rel-16/25_series/25903/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7589e70a4043c6c6695a9ffbf48a92051ed52f54188dd94f648be6dbf27b7c30 +size 87483 diff --git a/marked/Rel-16/25_series/25903/c742b64169a38a7f3f990172019878c8_img.jpg b/marked/Rel-16/25_series/25903/c742b64169a38a7f3f990172019878c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9867151d348b08a1eaa3c7568ab9da958588140 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c742b64169a38a7f3f990172019878c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6a4d14c8d7631fca69c35c8e7011168f0c48d97aae7a33adc45ce7038037b8 +size 70457 diff --git a/marked/Rel-16/25_series/25903/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/25_series/25903/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cb6e0668da3b79f6aefcc37b0ac5bed19fa5921 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed5d4953c8594a2c692a3684ca6f59c12636a38db0f397d2c8cbbe1e543298a3 +size 34887 diff --git a/marked/Rel-16/25_series/25903/c9829c80e5f6e9384df5f75e24da4c25_img.jpg b/marked/Rel-16/25_series/25903/c9829c80e5f6e9384df5f75e24da4c25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9c7a6927286a42b0b20ee5a43ede4b8db877e28 --- /dev/null +++ b/marked/Rel-16/25_series/25903/c9829c80e5f6e9384df5f75e24da4c25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe35f3764f963b0ddedf1115d604205922f208b28674c6b1c0e70c8c53e0d10c +size 50637 diff --git a/marked/Rel-16/25_series/25903/cf2d4d253cf03d94d0fd5544f4e3ca24_img.jpg b/marked/Rel-16/25_series/25903/cf2d4d253cf03d94d0fd5544f4e3ca24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2db3c6f23253b8a513dbefad87bf19494c26b87a --- /dev/null +++ b/marked/Rel-16/25_series/25903/cf2d4d253cf03d94d0fd5544f4e3ca24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05d91203e4fc8cf96862074d3f8261c36b44c76e1fb4333090b7b8770ba53bf6 +size 50191 diff --git a/marked/Rel-16/25_series/25903/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/25_series/25903/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f30e6d3e4c0979428eaa262ff0907f2ffc2f0617 --- /dev/null +++ b/marked/Rel-16/25_series/25903/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85edb80503fce2aa88422a5a5c5f9ab6dbb519bc28687aadb1f3f966db4859cf +size 41210 diff --git a/marked/Rel-16/25_series/25903/d3e2268ff05b24c2d8bbef7f56aba6c7_img.jpg b/marked/Rel-16/25_series/25903/d3e2268ff05b24c2d8bbef7f56aba6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b4ba672d4183ac7e82129665e36d8b9865ee18e --- /dev/null +++ b/marked/Rel-16/25_series/25903/d3e2268ff05b24c2d8bbef7f56aba6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0123ad36b50f034727bfe4110530bca72da2ec6f4ffb2f1eb39e44b4002f49eb +size 59405 diff --git a/marked/Rel-16/25_series/25903/d49bc18ad8867b97bbb9aa580449a641_img.jpg b/marked/Rel-16/25_series/25903/d49bc18ad8867b97bbb9aa580449a641_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61412487a2dd245de5c73566d9d4d937268d60e7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/d49bc18ad8867b97bbb9aa580449a641_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e541e07c0f072a725bf0628386e85ee4e882af69f4df397fa5c626cf83f0ed68 +size 72841 diff --git a/marked/Rel-16/25_series/25903/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/marked/Rel-16/25_series/25903/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8476089f22a5228476e540a94d404a8d94e7132f --- /dev/null +++ b/marked/Rel-16/25_series/25903/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e685fca157a7a85038706420edf08f126c511ab0e9294059279fb7706a23276 +size 6811 diff --git a/marked/Rel-16/25_series/25903/d6a5f8423065d7cef55e11a0007014d9_img.jpg b/marked/Rel-16/25_series/25903/d6a5f8423065d7cef55e11a0007014d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebc92b819c3f11a4fb92dd6a7a41c443ab3d1622 --- /dev/null +++ b/marked/Rel-16/25_series/25903/d6a5f8423065d7cef55e11a0007014d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33e70f407d1f055f81a47838a6d41a4930c7b3c72d31d760df5ae7e4cfd17a8f +size 62862 diff --git a/marked/Rel-16/25_series/25903/d8d893dd559845f86c5dd46147ef98b6_img.jpg b/marked/Rel-16/25_series/25903/d8d893dd559845f86c5dd46147ef98b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea58e23705311e262bc1bf7417db2a181d5913e8 --- /dev/null +++ b/marked/Rel-16/25_series/25903/d8d893dd559845f86c5dd46147ef98b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f29bcc7abfe6a27d52fd27da41f1e2a58d37186c981a7be03fe97fd80f078a71 +size 122400 diff --git a/marked/Rel-16/25_series/25903/d989d8766a23d5e409031f1ceae6572b_img.jpg b/marked/Rel-16/25_series/25903/d989d8766a23d5e409031f1ceae6572b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e2b5318733a4d3efc803f9e3e0e2c413a50e58d --- /dev/null +++ b/marked/Rel-16/25_series/25903/d989d8766a23d5e409031f1ceae6572b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85298e6957fe931e064bff53728260c54c55b2cfa9596f74aeb8e4a6a1d3d834 +size 52705 diff --git a/marked/Rel-16/25_series/25903/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-16/25_series/25903/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99fb3fb8830a3035912fa14508a91865fc97dc70 --- /dev/null +++ b/marked/Rel-16/25_series/25903/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5f83792b7afb2afb918d5f883ba0b4a3fdab432637b94c09b5a154e1461b67c +size 71407 diff --git a/marked/Rel-16/25_series/25903/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-16/25_series/25903/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..713d8ea33d0de255c41da21ea896f30e4371ecf4 --- /dev/null +++ b/marked/Rel-16/25_series/25903/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9969e44239ec3d20bbd39255697ff3bc6120f812642479bfa8ae0e0feaae969 +size 18676 diff --git a/marked/Rel-16/25_series/25903/df942da5e715e03b194b733d9f5998ad_img.jpg b/marked/Rel-16/25_series/25903/df942da5e715e03b194b733d9f5998ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63f733fe3cd4371936366c8c73da01dc14b35e0 --- /dev/null +++ b/marked/Rel-16/25_series/25903/df942da5e715e03b194b733d9f5998ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4396598dd385c6f7ca2863f7a21c87f9f631611eff8bedfdc3085f334af22e45 +size 50265 diff --git a/marked/Rel-16/25_series/25903/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-16/25_series/25903/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1fff3ed811cae0f1f5cba76efd23a65dc0a6e4f --- /dev/null +++ b/marked/Rel-16/25_series/25903/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64b2af7afd5de664c8b9766f4b599a7996420ab80a04ffee26918335b829a435 +size 39945 diff --git a/marked/Rel-16/25_series/25903/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-16/25_series/25903/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f035b6dd1a80377790f94f979a16400fa70db331 --- /dev/null +++ b/marked/Rel-16/25_series/25903/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecee7a9220bc39fbc12223643979bef550406715d1d688afaaaf4a42e42510ac +size 71115 diff --git a/marked/Rel-16/25_series/25903/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/25_series/25903/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1212ec27bd74d3e55284b76876e6f03a3ed60ae9 --- /dev/null +++ b/marked/Rel-16/25_series/25903/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0253f973316e2f91753f0acc65bef5686976c84606f0fa8252b1590d8a5a2ed +size 76060 diff --git a/marked/Rel-16/25_series/25903/e07207e429a7d92d9a8e3dd5030b6fda_img.jpg b/marked/Rel-16/25_series/25903/e07207e429a7d92d9a8e3dd5030b6fda_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..393870fbe05f72506419d5b1b2ca202a72a19690 --- /dev/null +++ b/marked/Rel-16/25_series/25903/e07207e429a7d92d9a8e3dd5030b6fda_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05d3c0e8c13291f1e6fd893bfa398626e5b067ef51cf04f3ced3d91d1432417d +size 32020 diff --git a/marked/Rel-16/25_series/25903/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg b/marked/Rel-16/25_series/25903/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a2a02dc798539b014a4f29b1eb5d259006a4a10 --- /dev/null +++ b/marked/Rel-16/25_series/25903/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c5a435f0c40e1c4bc0bb9c3e90aa60da8a93ad76375613f7e90a7f38e231c48 +size 15270 diff --git a/marked/Rel-16/25_series/25903/e466e4c4fb08567a109bb959a765225c_img.jpg b/marked/Rel-16/25_series/25903/e466e4c4fb08567a109bb959a765225c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2b7c4168d4e3a776d60c8b34aa7421cb9e53f3b --- /dev/null +++ b/marked/Rel-16/25_series/25903/e466e4c4fb08567a109bb959a765225c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:035355b7c1986a9c4bdcc097b450a64baf6ea3c4fb9016b004d7ed21a0c2d860 +size 53999 diff --git a/marked/Rel-16/25_series/25903/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg b/marked/Rel-16/25_series/25903/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d71c93c1727804d84f79f8527706a1ef890e3858 --- /dev/null +++ b/marked/Rel-16/25_series/25903/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89a5d025ea6735d76033c3badf36e6ff9f0c2f7a14d28b187461b55a2b25340f +size 73256 diff --git a/marked/Rel-16/25_series/25903/ead8d1841c351608343c98f30e5f3f07_img.jpg b/marked/Rel-16/25_series/25903/ead8d1841c351608343c98f30e5f3f07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..388b253180bf034e8161cfb2aff2cc0e86fba19a --- /dev/null +++ b/marked/Rel-16/25_series/25903/ead8d1841c351608343c98f30e5f3f07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7180a638dc6c560b3bbe615fd9ac8d95da7f2ad126de71b8413a13a6ae7330f +size 40600 diff --git a/marked/Rel-16/25_series/25903/ebbc36b94b206c93f73a15481c321fd6_img.jpg b/marked/Rel-16/25_series/25903/ebbc36b94b206c93f73a15481c321fd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d945f7f6feea58cd47d31738cade55cc0db661c0 --- /dev/null +++ b/marked/Rel-16/25_series/25903/ebbc36b94b206c93f73a15481c321fd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbb1e6f24f8eef3a357f2164baf09151677198e8118cdd7bcb9fdf82ca883ce7 +size 43433 diff --git a/marked/Rel-16/25_series/25903/ebce355620876e10f907f8b71926c112_img.jpg b/marked/Rel-16/25_series/25903/ebce355620876e10f907f8b71926c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49c696f335a534dd4567c85a8e2287657e8e1a37 --- /dev/null +++ b/marked/Rel-16/25_series/25903/ebce355620876e10f907f8b71926c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f16ee324dbbbc64515527c46c1cfbfaf57e26e055467435947776aafcc58ec9a +size 123544 diff --git a/marked/Rel-16/25_series/25903/efbdff107f5a5aade487cf4ea0eae150_img.jpg b/marked/Rel-16/25_series/25903/efbdff107f5a5aade487cf4ea0eae150_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e5fafb726a271dee5217677032222f89c0dd3ae --- /dev/null +++ b/marked/Rel-16/25_series/25903/efbdff107f5a5aade487cf4ea0eae150_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17efdff4d784ec03cd2e1d1df786d4c980a39675c003d19122681cc5daa4db33 +size 76624 diff --git a/marked/Rel-16/25_series/25903/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-16/25_series/25903/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a89fed040f021dfd23a8ec8967f144480010f03 --- /dev/null +++ b/marked/Rel-16/25_series/25903/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9897f881870c4ba269296b49c8bbf8417fe899471b88f09694671fb16fc8c545 +size 34875 diff --git a/marked/Rel-16/25_series/25903/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-16/25_series/25903/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cba87dfb1dbef16be9fd2f3674577e2c2e7d6bb5 --- /dev/null +++ b/marked/Rel-16/25_series/25903/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3683a7ea330ebdb205fc4a53c3afe50d12c9d0f6340d4e6fd9709665c271a23b +size 121226 diff --git a/marked/Rel-16/25_series/25903/f9625fa3465b009051f85d91cfa1da7e_img.jpg b/marked/Rel-16/25_series/25903/f9625fa3465b009051f85d91cfa1da7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e430b47f735bcf7504b48b5948cf318c48adeb2 --- /dev/null +++ b/marked/Rel-16/25_series/25903/f9625fa3465b009051f85d91cfa1da7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c45f4fe004a818cd1fc6eeb9682385afd27a8a52696004e234238ca351069087 +size 38039 diff --git a/marked/Rel-16/25_series/25903/f9d11004ac6966f27936c8d01e579313_img.jpg b/marked/Rel-16/25_series/25903/f9d11004ac6966f27936c8d01e579313_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6debcc12a2f876fd269c0e4a88f82bb962e5fd7 --- /dev/null +++ b/marked/Rel-16/25_series/25903/f9d11004ac6966f27936c8d01e579313_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a37b3109d0fb906a89ead93e81a8c2b421d7ead9f64036797deaee94d9532aa8 +size 32497 diff --git a/marked/Rel-16/25_series/25903/fd38170a3981416226ab91f7437ba821_img.jpg b/marked/Rel-16/25_series/25903/fd38170a3981416226ab91f7437ba821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dc154f439d72e67e004c59c079f9d960a11c21e --- /dev/null +++ b/marked/Rel-16/25_series/25903/fd38170a3981416226ab91f7437ba821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f63eb9aa35641535e0512a32f35755836d777a10a0ab8873f9b51bfea4aa774 +size 61947 diff --git a/marked/Rel-16/25_series/25903/fe8672dfa08ec40ce3d9eb6277780260_img.jpg b/marked/Rel-16/25_series/25903/fe8672dfa08ec40ce3d9eb6277780260_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b7da73b40d2525bf7b4629cb2da7b9f16eda82 --- /dev/null +++ b/marked/Rel-16/25_series/25903/fe8672dfa08ec40ce3d9eb6277780260_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04f57c0638468703540fe43cc272ba60ba9ca308c3132de34162793f3200f50e +size 41272 diff --git a/marked/Rel-16/25_series/25903/fed39b841ae2dce01088b84bfc1e2789_img.jpg b/marked/Rel-16/25_series/25903/fed39b841ae2dce01088b84bfc1e2789_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19864e4503ad572890c0f7ddcef786837b5f7c4a --- /dev/null +++ b/marked/Rel-16/25_series/25903/fed39b841ae2dce01088b84bfc1e2789_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f7a63d2b9bc94716b6c14554b3f81550d84daa53154d5dd493e84b11c9e88ff +size 149174 diff --git a/marked/Rel-16/25_series/25903/raw.md b/marked/Rel-16/25_series/25903/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..30936b109a50ce64d18dc3646f45abd046b0a739 --- /dev/null +++ b/marked/Rel-16/25_series/25903/raw.md @@ -0,0 +1,4340 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 6 | +| Introduction..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations..... | 8 | +| 4 Technical concepts..... | 9 | +| 4.1 New DPCCH slot format..... | 10 | +| 4.1.1 Description of the concept..... | 10 | +| 4.1.1.1 General description..... | 10 | +| 4.1.1.2 Detailed proposals..... | 12 | +| 4.1.1.2.1 SIR target adjustment..... | 13 | +| 4.1.1.2.2 CPC initiation and termination..... | 13 | +| 4.1.2 Analysis of the concept..... | 14 | +| 4.1.2.1 Simulation results on UL TPC error rate..... | 14 | +| 4.1.2.2 Simulation results on other UL channels..... | 17 | +| 4.1.2.2.1 CQI transmission..... | 19 | +| 4.1.2.2.2 HARQ-ACK transmission..... | 26 | +| 4.1.2.2.3 Observations from simulations of HS-DPCCH performance in sub-clauses 4.1.2.2.1 and 4.1.2.2.2..... | 31 | +| 4.1.2.3 Conclusions from TPC performance (sub-clause 4.1.2.1) and HS-DPCCH performance (sub-clause 4.1.2.2)..... | 32 | +| 4.1.2.4 Power control delay..... | 32 | +| 4.1.3 Benefits of the concept..... | 33 | +| 4.1.4 Open issues of the concept..... | 33 | +| 4.2 Uplink DPCCH gating..... | 33 | +| 4.2.1 Description of the concept..... | 33 | +| 4.2.1.1 General principle..... | 34 | +| 4.2.1.2 Basic packet traffic example..... | 34 | +| 4.2.1.3 VoIP traffic example..... | 34 | +| 4.2.1.4 Operation of the uplink DPCCH gating..... | 35 | +| 4.2.2 Analysis of the concept..... | 37 | +| 4.2.2.1 Power control stability..... | 37 | +| 4.2.2.2 F-DPCH performance..... | 40 | +| 4.2.2.3 Uplink link performance..... | 44 | +| 4.2.2.3.1 Additional link level results..... | 46 | +| 4.2.2.3.2 Link level results for CQI decoding and for large TB sizes..... | 54 | +| 4.2.2.3.3 Preamble detection link level result for uplink DPCCH gating with long gating gap..... | 60 | +| 4.2.2.4 System performance..... | 62 | +| 4.2.2.4.1 Simulation assumptions..... | 62 | +| 4.2.2.4.2 VoIP results with and without gating – 2 ms TTI..... | 62 | +| 4.2.2.4.3 VoIP results with and without gating – 10 ms TTI and packet bundling..... | 64 | +| 4.2.2.4.4 VoIP results - Summary..... | 66 | +| 4.2.2.4.5 Impact of inactive users to cell throughput..... | 66 | +| 4.2.2.4.6 System-level performance with high-velocity UEs..... | 68 | +| 4.2.2.5 UE battery saving calculations..... | 70 | +| 4.2.3 Benefits of the concept..... | 73 | +| 4.2.4 Open issues of the concept..... | 73 | +| 4.3 SIR target reduction..... | 73 | +| 4.3.1 Description of the concept..... | 73 | +| 4.3.1.1 L1 signalling approach..... | 73 | +| 4.3.1.1.1 Interworking aspects..... | 75 | +| 4.3.1.1.2 Handling of VoIP traffic..... | 75 | + +| | | | +|------------|----------------------------------------------------------------------------|-----| +| 4.3.1.2 | L2 signalling approach..... | 76 | +| 4.3.1.2.1 | New parameters for L2 signalling approach..... | 77 | +| 4.3.1.3 | Approach with predefined/configured rules..... | 77 | +| 4.3.2 | Analysis of the concept..... | 78 | +| 4.3.2.1 | Simulation of the concept..... | 78 | +| 4.3.2.1.1 | Simulation assumptions..... | 78 | +| 4.3.2.1.2 | Simulation results..... | 79 | +| 4.3.2.2 | Noise rise caused by UL DPCCH..... | 81 | +| 4.3.2.3 | Potential gain in terms of number of additional users & UL noise rise..... | 82 | +| 4.3.2.4 | Reactivation delay..... | 83 | +| 4.3.2.5 | Signalling load..... | 83 | +| 4.3.2.6 | CQI Performance for boosting HS-DPCCH power offset to DPCCH..... | 83 | +| 4.3.2.6.1 | Simulations assumptions..... | 83 | +| 4.3.2.6.2 | Simulations results..... | 84 | +| 4.3.3 | Benefits of the concept..... | 85 | +| 4.3.4 | Open issues of the concept..... | 86 | +| 4.4 | CQI reporting reduction..... | 86 | +| 4.4.1 | Description of the concept..... | 86 | +| 4.4.1.1 | L1 signalling approach for CQI off..... | 86 | +| 4.4.1.1.1 | Interworking aspects..... | 87 | +| 4.4.1.2 | L2 signalling approach for CQI off..... | 87 | +| 4.4.1.2.1 | New parameters for L2 signalling approach for CQI off..... | 88 | +| 4.4.1.3 | Predefined/configured rules for CQI reporting reduction..... | 88 | +| 4.4.2 | Analysis of the concept..... | 89 | +| 4.4.2.1 | Gain in terms of number of additional users & UL noise rise..... | 89 | +| 4.4.2.2 | Signalling load..... | 89 | +| 4.4.3 | Benefits of the concept..... | 89 | +| 4.4.4 | Open issues of the concept..... | 90 | +| 4.5 | DRX at the UE..... | 90 | +| 4.5.1 | Description of the concept..... | 90 | +| 4.5.2 | Analysis of the concept..... | 90 | +| 4.5.2.1 | Timing, with 2 ms E-DCH TTI..... | 90 | +| 4.5.2.1.1 | Background..... | 90 | +| 4.5.2.1.2 | DRX mode 2/8..... | 91 | +| 4.5.2.1.3 | DRX mode 1/8..... | 92 | +| 4.5.2.1.4 | DRX mode 1/16 and beyond..... | 93 | +| 4.5.2.1.5 | DRX mode 2/8, in a 2 way soft handover..... | 93 | +| 4.5.2.1.6 | DRX mode 1/8, in a 2 way soft handover..... | 94 | +| 4.5.2.1.7 | DRX mode 1/16, in a 2 way soft handover..... | 94 | +| 4.5.2.2 | Downlink scheduler performance..... | 95 | +| 4.5.2.2A | Timing, with 10 ms E-DCH TTI..... | 96 | +| 4.5.2.2A.1 | Background..... | 96 | +| 4.5.2.2A.2 | DRX mode 1/2..... | 97 | +| 4.5.2.2A.3 | DRX mode 1/3..... | 97 | +| 4.5.2.2A.4 | DRX mode 1/4..... | 97 | +| 4.5.2.2A.5 | DRX mode ¼, in a 2 way soft handover..... | 98 | +| 4.5.2.3 | Impact of DRX in demodulation performance..... | 99 | +| 4.5.2.3.1 | Simulation assumptions..... | 99 | +| 4.5.2.3.2 | Simulation results..... | 101 | +| 4.5.3 | Benefits of the concept..... | 102 | +| 4.5.4 | Open issues of the concept..... | 102 | +| 4.6 | Restricted HS-SCCH..... | 102 | +| 4.6.1 | Description of the concept..... | 102 | +| 4.6.1.1 | HARQ Operation and Signalling..... | 103 | +| 4.6.1.2 | Signalling of transport format..... | 103 | +| 4.6.1.3 | Coding for HS-SCCH..... | 104 | +| 4.6.1.4 | HS-SCCH physical channel structure..... | 105 | +| 4.6.1.5 | UE reception of the restricted HS-SCCH..... | 106 | +| 4.6.2 | Analysis of the concept..... | 106 | +| 4.6.3 | Benefits of the concept..... | 107 | +| 4.6.4 | Open issues of the concept..... | 107 | + +| | | | +|------------------------|-------------------------------------------------------------------------------------|-----| +| 4.6.4.1 | Unexpected and Erroneous Events..... | 107 | +| 4.6.4.1.1 | ACK/NACK not received in response to a new transmission..... | 107 | +| 4.6.4.1.2 | Buffer corruption..... | 107 | +| 4.6.4.1.3 | HS-SCCH misdetection followed by ACK false alarm..... | 108 | +| 4.6.4.1.4 | HS-SCCH misdetection followed by NACK false alarm..... | 108 | +| 4.7 | HS-SCCH-less operation..... | 108 | +| 4.7.1 | Description of the Concept..... | 108 | +| 4.7.2 | Analysis of the concept..... | 109 | +| 4.7.2.1 | Transmission waveform and timing..... | 109 | +| 4.7.2.2 | UE complexity discussion..... | 110 | +| 4.7.2.3 | CRC discussion..... | 111 | +| 4.7.2.4 | VoIP and best effort capacity simulations..... | 112 | +| 4.7.2.4.1 | Simulation assumptions..... | 112 | +| 4.7.2.4.2 | Simulation results..... | 113 | +| 4.7.3 | Benefits of the concept..... | 115 | +| 4.7.4 | Open issues of the concept..... | 115 | +| 4.8 | Reduced complexity HS-SCCH-less operation..... | 115 | +| 4.8.1 | Description of the concept..... | 115 | +| 4.8.1.1 | HS-SCCH for retransmissions with the reduced complexity HS-SCCH-less operation..... | 116 | +| 4.8.2 | Analysis of the concept..... | 117 | +| 4.8.2.1 | Timing and operation..... | 117 | +| 4.8.2.2 | UE Complexity discussion..... | 117 | +| 4.8.2.3 | Simulation Results..... | 117 | +| 4.8.2.3.1 | Simulation assumptions..... | 121 | +| 4.8.3 | Benefits of the concept..... | 122 | +| 4.8.4 | Open Issues of the concept..... | 122 | +| 4.A | Summary of technical concepts and possible combinations..... | 123 | +| 4.A.1 | Overview of the technical concepts..... | 123 | +| 4.A.2 | Overview of possible combinations of technical concepts..... | 128 | +| 5 | Technical solution..... | 130 | +| 5.1 | Overview of the selected solution..... | 130 | +| 5.1.1 | New UL DPCCH slot format..... | 131 | +| 5.1.2 | Discontinuous transmission and reception in CELL_DCH..... | 131 | +| 5.1.3 | HS-SCCH less operation..... | 133 | +| 5.2 | Impact on RAN1 specifications..... | 134 | +| 5.3 | Impact on RAN2 specifications..... | 135 | +| 5.4 | Impact on RAN3 specifications..... | 136 | +| 5.5 | Impact on RAN4 specifications..... | 138 | +| 5.6 | Change requests related to CPC..... | 138 | +| Annex A (informative): | Change history..... | 140 | + +# --- 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. + +# --- Introduction + +Packet-oriented features like HSDPA and E-DCH in WCDMA/UMTS systems will promote the subscribers' desire for continuous connectivity, where the user stays connected over a long time span with only occasional active periods of data transmission, and avoiding frequent connection termination and re-establishment with its inherent overhead and delay. + +This is the perceived mode a subscriber is used to in fixed broadband networks (e.g. DSL) and a precondition to attract users from fixed broadband networks. + +To support a high number of HSDPA users in the code limited downlink the feature F-DPCH was introduced in REL-6. + +In the uplink, the limiting factor for supporting a similarly high number of E-DCH users is the noise rise. + +For such a high number of users in the cell it can be assumed that many users are not transmitting any user data for some time (e.g. for reading during web browsing or in between packets for periodic packet transmission such as VoIP). The corresponding overhead in the noise rise caused by maintained control channels will significantly limit the number of users that can be efficiently supported. + +As completely releasing dedicated channels during periods of traffic inactivity would cause considerable delays for reestablishing data transmission and a corresponding bad user perception, this WI is intended to reduce the impact of control channels on uplink noise rise while maintaining the connections and allowing a much faster reactivation for temporarily inactive users. + +# 1 Scope + +The present document summarizes the work done under the WI "Continuous Connectivity for Packet Data Users" defined in [1] by listing technical concepts addressing the objectives of the work item (see below), analysing these technical concepts and selecting the best solution (which might be a combination of technical concepts). + +"The objective of this work item is to reduce the uplink noise rise from physical control channels of packet data users, e.g. for users which have temporarily no data transmission. + +This is intended to significantly increase the number of packet data users (i.e. HS-DSCH/E-DCH users without UL DPDCH) in the UMTS FDD system that can stay in CELL\_DCH state over a long time period, without degrading cell throughput, and that can restart transmission after a period of inactivity with a much shorter delay (<50ms) than would be necessary for reestablishment of a new connection + +The objective covers also schemes which could allow improving the achievable UL capacity for VoIP users with its inherent periodic transmission through reducing the overhead of the control channels. + +Mobility and downlink transmission should not be impacted for these users." + +The present document provides the base for the following preparation of change requests to the corresponding RAN specifications. + +# 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 Tdoc RP-050429: "Proposal for a WI description for 'Continuous connectivity for packet data users'", TSG RAN #29, Aug./Sep. 2005, Tallinn, Estonia. +- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [4] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [5] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [6] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [7] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [8] 3GPP TS 25.306: "UE Radio Access Capabilities". +- [9] 3GPP TS 25.308: "UTRA High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2". +- [10] 3GPP TS 25.309: "FDD Enhanced Uplink; Overall description; Stage 2". (for REL-7 see [23]) +- [11] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". +- [12] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification". +- [13] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling". + +- [14] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)". +- [15] 3GPP Tdoc RP-050427: "Status report of SI 'Continuous connectivity for packet data users' to TSG RAN #29", TSG RAN #29, Aug./Sep. 2005, Tallinn, Estonia. +- [16] 3GPP Tdoc RP-050670: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #30", TSG RAN #30, Nov./Dec. 2005, Saint Julian, Malta. +- [17] 3GPP Tdoc RP-050870: " Update of WI description for 'Continuous connectivity for packet data users'", TSG RAN #30, Nov./Dec. 2005, Saint Julian, Malta. +- [18] 3GPP Tdoc RP-060019: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #31", TSG RAN #31, March 2006, Sanya/Hainan, China. +- [19] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [20] 3GPP Tdoc RP-060241: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #32", TSG RAN #32, May/June 2006, Warsaw, Poland. +- [21] 3GPP Tdoc RP-060454: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #33", TSG RAN #33, Sep. 2006, Palm Springs, USA. +- [22] 3GPP Tdoc RP-060454: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #34", TSG RAN #34, Nov./Dec. 2006, Budapest, Hungary. +- [23] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2 (Release 7)". +- [24] 3GPP Tdoc RP-070033: "Status report of WI 'Continuous connectivity for packet data users' to TSG RAN #35", TSG RAN #35, March 2007, Lemesos, Cyprus. + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply. + +**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 following abbreviations apply: + +| | | +|---------|-----------------------------------------------------------------| +| ACK | Acknowledgement | +| CQI | Channel Quality Indicator | +| CPC | Continuously Packet Connected or Continuous Packet Connectivity | +| CRC | Cyclic Redundancy Check | +| DCH | Dedicated Channel | +| DL | Downlink | +| DPCCH | Dedicated Physical Control Channel | +| DPCH | Dedicated Physical Channel | +| DPDCH | Dedicated Physical Data Channel | +| DTX | Discontinuous Transmission | +| E-DCH | Enhanced Dedicated Channel | +| E-DPCCH | E-DCH Dedicated Physical Control Channel | +| E-DPDCH | E-DCH Dedicated Physical Data Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-HICH | E-DCH HARQ Acknowledgement Indicator Channel | + +| | | +|----------|-----------------------------------------------------| +| E-RGCH | E-DCH Relative Grant Channel | +| F-DPCH | Fractional Dedicated Physical Channel | +| HSDPA | High Speed Downlink Packet Access | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | High Speed Physical Downlink Shared Control Channel | +| NACK | Negative Acknowledgement | +| P-CCPCH | Primary Common Control Physical Channel | +| RL | Radio Link | +| S-CCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronisation Channel | +| SIR | Signal-to-Interference Ratio | +| TFC | Transport Format Combination | +| TPC | Transmit Power Control | +| TPC CER | TPC Command Error Rate | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# 4 Technical concepts + +This section describes and analyses the suggested technical concepts addressing the problem described by the work item “Continuous Connectivity for Packet Data Users” defined in [1]. This section 4 includes feasible concepts to address the WI without claiming that the concepts are complete or restricting the addition of alternatives. + +The following **common base for all concepts** can be assumed: + +- Packet data users in CELL\_DCH state using HSDPA and E-DCH as described in REL-6 are addressed. +- The UE is and will remain in the CELL\_DCH RRC state whatever continuous connectivity concept will be applied. +- The signalling radio bearers (SRBs) are assumed to be mapped on HS-DSCH in downlink (as is necessary for F-DPCH, anyway) and on E-DCH in uplink. +- UL channels present in this case: UL DPCCH, HS-DPCCH, E-DPCCH, E-DPDCH (E-DPCCH, E-DPDCH are DTXed when no data (or rate requests) needs to be transmitted on E-DPDCH). +- DL channels present in this case: F-DPCH, HS-SCCH, HS-PDSCH, E-AGCH, E-RGCH, E-HICH. To avoid DL channelization code limitations F-DPCH instead of DL DPCCH is considered. + +Different **phases during the stay in the CELL\_DCH state** can be distinguished by the activity of the data channels: + +- Packet on HS-PDSCH is transmitted to the UE in the TTI. +- inactive DL: No packet is transmitted on HS-PDSCH to the UE in the TTI. +- Packet on E-DPDCH is transmitted to the Node B in the TTI. +- inactive UL: No packet is transmitted on E-DPDCH to the Node B in the TTI. + +It is the aim that the application of a continuous connectivity concept will not affect the performance of a transmission in an active TTI. + +The description of the active and inactive phases does not preclude the way and whether or not CELL\_DCH substates should be introduced. + +The continuous connectivity concepts are addressing the control channels (i.e. one or more) during inactive phases in UL and/or DL. + +The triggers for initiating and terminating the use of a continuous connectivity concept relative to the start and end of active and inactive phases depend on the considered concept. For example: + +- whether the concept is triggered when there is inactivity in just one direction (i.e. only DL, only UL) or in both directions (UL & DL); +- whether a transition from activity to inactivity will directly trigger the application of the concept or whether there is a short period of inactive phase without applying the concept (e.g. if a timer is used to trigger the concept); +- whether very short periods of DL and/or UL inactivity (e.g. during transmission of VoIP packets or where a UE is not scheduled but data is waiting in the scheduler queue) could also be addressed by a continuous connectivity concept. +- whether during an inactive phase the concept is used during transmission of physical layer signalling (e.g. on HS-DPCCH or HS-SCCH). + +The period during which a continuous connectivity concept is applied is called "Continuously Packet Connected mode" or shorter "CPC mode". + +### Transitions between the different phases: + +The following transitions are called "CPC initiation": + +- active phase to CPC mode +- inactive phase where REL-6 is applied as usual to CPC mode + +while the transition back is called "CPC termination": + +- CPC mode to active phase. +- CPC mode to inactive phase where REL-6 is applied as usual + +Triggers for the transitions and a description of the signalling (e.g. L1 or L2 signalling) or the implicit rules/blind detection (if no signalling is required) for the transitions has to be described in the different continuous connectivity concepts. + +Nevertheless, three general transition control approaches (i.e. who will have the final decision about the transition) could be distinguished: + +- transition is controlled by the UE +- transition is controlled by the Node B +- transition is controlled by predefined rules applied by both UE and Node B + +This includes also the possibility to have a combination for different links (i.e. UL/DL) or transitions (i.e. CPC initiation/termination). + +Another aspect to be described for each concept is the question of how reliable is the control of the CPC initiation and termination. + +## 4.1 New DPCCH slot format + +### 4.1.1 Description of the concept + +#### 4.1.1.1 General description + +The primary purpose of the continuous DPCCH when data is not being transmitted is to maintain synchronisation and power control ready for a rapid resumption of data transmission when needed. + +This is different from the case when data is being transmitted, when the DPCCH also has to act as the phase reference for the data, and possibly also carry TFCI and/or FBI. + +The DPCCH slot formats which are available up to Release 6 are primarily adapted to the case when data is being transmitted, but are not necessarily suitable for minimising the overhead when the DPCCH is the only uplink channel. In particular, none of the existing DPCCH slot formats have more than 2 TPC bits, while the pilot field occupies between 5 and 8 bits, reflecting the need for sufficient pilot energy to give a reliable channel estimate for decoding data. + +One way to reduce the DPCCH overhead could therefore be to introduce a new DPCCH slot format which is better suited to the case when effectively the only data bits are the TPC bits. Typically this would involve reducing the pilot energy per slot. + +Some possible new slot formats are shown in Figure 4.1.1.1-1 to Figure 4.1.1.1-3. + +![Figure 4.1.1.1-1: One possible new DPCCH slot format (Format a). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N_pilot = 5 bits and a 'TPC' field of N_TPC = 5 bits. Below this, a double-headed arrow indicates the total slot duration T_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T_f = 10 ms.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 4.1.1.1-1: One possible new DPCCH slot format (Format a). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N\_pilot = 5 bits and a 'TPC' field of N\_TPC = 5 bits. Below this, a double-headed arrow indicates the total slot duration T\_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T\_f = 10 ms. + +**Figure 4.1.1.1-1: One possible new DPCCH slot format (Format a)** + +The slot format shown in figure 4.1.1.1-1 has an equal number of pilot and TPC bits. Typically this optimises the pilot-to-TPC ratio if the channel phase estimation is being carried out over a single slot. + +![Figure 4.1.1.1-2: A second possible new slot format (Format b). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N_pilot = 2 bits and a 'TPC' field of N_TPC = 8 bits. Below this, a double-headed arrow indicates the total slot duration T_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T_f = 10 ms.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +Figure 4.1.1.1-2: A second possible new slot format (Format b). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N\_pilot = 2 bits and a 'TPC' field of N\_TPC = 8 bits. Below this, a double-headed arrow indicates the total slot duration T\_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T\_f = 10 ms. + +**Figure 4.1.1.1-2: A second possible new slot format (Format b)** + +Figure 4.1.1.1-2 shows an example which may be better suited to a slowly-changing channel when the channel phase estimation may be averaged over a number of consecutive slots. Here the TPC field is increased in size even more than in figure 4.1.1.1-1, thus enabling a larger reduction in DPCCH transmit power. + +A reduction in SIR target would be applied at the Node B when a slot format like those in figure 4.1.1.1-1 or figure 4.1.1.1-2 was being used. A power step on the DPCCH could also be applied in order for the power control loop to converge quickly. + +Reducing the DPCCH power in this way enables the uplink control channel overhead to be reduced, and hence more inactive users to be supported in CELL\_DCH state. + +![Figure 4.1.1.1-3: A third possible new slot format (Format c). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N_pilot = 2 bits and a 'TPC' field of N_TPC = 2 bits. Below this, a double-headed arrow indicates the total slot duration T_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T_f = 10 ms.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +Figure 4.1.1.1-3: A third possible new slot format (Format c). The diagram shows a DPCCH slot structure. The top part is a single slot with a 'Pilot' field of N\_pilot = 2 bits and a 'TPC' field of N\_TPC = 2 bits. Below this, a double-headed arrow indicates the total slot duration T\_slot = 2560 chips, 10 bits. The bottom part shows a sequence of slots labeled Slot #0, Slot #1, Slot #i, and Slot #14, with a double-headed arrow indicating the duration of 1 radio frame: T\_f = 10 ms. + +**Figure 4.1.1.1-3: A third possible new slot format (Format c)** + +Figure 4.1.1.1-3 shows a slot format where the number of pilot bits is reduced to a suitable number for the current size of the TPC field. DTX would be used between the pilot and TPC fields. This type of slot format would give a reduction in the average overhead, with the noise rise from an individual user being discontinuous. + +Other possibilities, for example with 4 or 6 pilot bits, could also be considered, but the number of new slot formats should be minimised, preferably to a single new slot format. + +#### 4.1.1.2 Detailed proposals + +In this section specific proposals are described in more detail. + +As an example, a new slot format may be introduced into 25.211 as shown in Table 4.1.1.2-1, where the new format 1\* is associated with the existing slot format 1. When slot format 1\* is configured by the RNC, the slot format could switch to slot format 1 during certain periods when more pilot energy is required. The switching between slot formats 1 and 1\* could be according to predefined rules. This is discussed further in sub-clause 4.1.2.3. Configuring the new slot format under the control of the RNC in this way also allows compatibility with Node B's that do not support the new slot format. + +**Table 4.1.1.2-1: New slot format: Proposal A** + +| Slot Form at #I | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ Frame | Bits/ Slot | N pilot | N TPC | N TFCI | N FBI | Transmitted slots per radio frame | +|-----------------|-------------------------|----------------------------|-----|-------------|------------|--------------------|------------------|-------------------|------------------|-----------------------------------| +| 0 | 15 | 15 | 256 | 150 | 10 | 6 | 2 | 2 | 0 | 15 | +| 0A | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 3 | 0 | 10-14 | +| 0B | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 4 | 0 | 8-9 | +| 1 | 15 | 15 | 256 | 150 | 10 | 8 | 2 | 0 | 0 | 8-15 | +| 1* | 15 | 15 | 256 | 150 | 10 | 5 | 5 | 0 | 0 | 8-15 | +| 2 | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 2 | 1 | 15 | +| 2A | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 3 | 1 | 10-14 | +| 2B | 15 | 15 | 256 | 150 | 10 | 3 | 2 | 4 | 1 | 8-9 | +| 3 | 15 | 15 | 256 | 150 | 10 | 7 | 2 | 0 | 1 | 8-15 | + +As a further example, a new slot format may be introduced as shown in Table 4.1.1.2-2, where the use of the new format 4 can only be configured by the RNC in the normal way (i.e. its use does not depend on transmission activity on other channels). + +**Table 4.1.1.2-2: New slot format: Proposal B** + +| Slot Form at #I | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/ Frame | Bits/ Slot | N pilot | N TPC | N TFCI | N FBI | Transmitted slots per radio frame | +|-----------------|-------------------------|----------------------------|-----|-------------|------------|--------------------|------------------|-------------------|------------------|-----------------------------------| +| 0 | 15 | 15 | 256 | 150 | 10 | 6 | 2 | 2 | 0 | 15 | +| 0A | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 3 | 0 | 10-14 | +| 0B | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 4 | 0 | 8-9 | +| 1 | 15 | 15 | 256 | 150 | 10 | 8 | 2 | 0 | 0 | 8-15 | +| 2 | 15 | 15 | 256 | 150 | 10 | 5 | 2 | 2 | 1 | 15 | +| 2A | 15 | 15 | 256 | 150 | 10 | 4 | 2 | 3 | 1 | 10-14 | +| 2B | 15 | 15 | 256 | 150 | 10 | 3 | 2 | 4 | 1 | 8-9 | +| 3 | 15 | 15 | 256 | 150 | 10 | 7 | 2 | 0 | 1 | 8-15 | +| 4 | 15 | 15 | 256 | 150 | 10 | 6 | 4 | 0 | 0 | 8-15 | + +##### 4.1.1.2.1 SIR target adjustment + +In order to gain maximum benefit from a new slot format used during periods of with no uplink data transmission, at least the serving Node B should reduce its SIR target by a specified amount during the period with no uplink data, and the following behaviour should also occur: + +- At the start of usage of the new slot format, the UE should reduce its DPCCH transmit power by a specified amount. +- At the end of usage of the new slot format, the UE should increase its DPCCH transmit power by a specified amount. + +As an example, the methods described for SIR target reduction in section 4.3 could be used. + +##### 4.1.1.2.2 CPC initiation and termination + +The initiation and termination of CPC operation would be different for the two proposals given in sub-clause 4.1.1.2. + +For **Proposal A** (Table 4.1.1.2-1), CPC initiation would comprise configuring the use of slot format #1\* by RRC signalling in the usual way. Predefined rules for switching between slot format #1\* and slot format #1 could then be used, for example comprising using slot format #1 in all DPCCH slots which start at the beginning of or during either HS-DPCCH transmission, DPDCH transmission or E-DPCCH transmission, and using slot format #1\* in all other DPCCH slots. + +The HS-DSCH Serving Node B can predict exactly when HS-DPCCH transmissions will occur, and can therefore predict whether slot format #1 or slot format #1\* is being used. The serving Node B can therefore derive the channel estimate and decode the DPCCH correctly in this case. Other Node Bs do not have to decode the HS-DPCCH transmissions, but could nonetheless use detected HS-DPCCH energy to help determine which of slot formats 1 and 1\* was being used. + +For E-DPCCH/E-DPDCH transmission, the change of slot format could be detected on the basis of detected E-DPCCH/E-DPDCH energy (similar to blind transport format detection using received power ratio). The E-DCH Serving RLS also has knowledge of the Serving Grant and UE buffer status, and can therefore make a more reliable estimate of when E-DPCCH is transmitted. + +These possibilities are discussed further in sub-clause 4.1.2.3, where conclusions are also drawn in the light of the simulation results. + +Depending on the choice of pilot pattern, Node Bs could also use differences in bit pattern to detect a change of DPCCH slot format. However, in order to avoid blind slot-format detection in non-serving Node Bs in soft handover, it seems preferable to set the pilot pattern for the new slot format 1\* to be the same as the first bits of the pilot pattern for the associated slot format 1. This is illustrated in Table Y for a new slot format 1\* with 5 pilot bits and 5 TPC bits. The existing Rel-99 pilot pattern for slot format 1 (8 pilot bits) is also shown for comparison. + +| Bit # | N pilot = 5 (slot format 1*) | | | | | N pilot = 8 (slot format 1) | | | | | | | | +|--------|-----------------------------------------|---|---|---|---|----------------------------------------|---|---|---|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| Slot#0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | +| 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| 2 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | +| 3 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | +| 4 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | +| 5 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | +| 6 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | +| 7 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | +| 8 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | +| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 10 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | +| 11 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | +| 12 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | +| 13 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | +| 14 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | + +This enables the non-serving Node Bs always to decode two TPC bits at the end of each slot using a channel estimate derived from the first 5 pilot bits, without needing to do any blind detection of the change of slot format. + +For **Proposal B** (Table 4.1.1.2-2), Slot Format #4 would be configured by the RNC in the normal way, so fast switching would not occur. + +A combination of Proposals A and B could also be considered, by adding both slot format #1\* and slot format #4 to the slot formats table for UL DPCCH. In this case, it would be possible for the RNC to configure the new slot format either to be used in all slots (by configuring slot format #4), or only in inactive slots (by configuring slot format #1 and enabling the use of slot format #1\*). + +### 4.1.2 Analysis of the concept + +#### 4.1.2.1 Simulation results on UL TPC error rate + +The performance results here show the UL DPCCH $E_b/N_0$ required to achieve a given UL TPC error rate for some different DPCCH slot formats. These would be applicable for the case where only the UL DPCCH is present. + +The simulation assumptions are as follows: + +- 2GHz carrier frequency +- DPCCH SF = 256 +- Non-SHO +- UL power control using PCA1 and a 1dB step size, with a 4% error rate on DL TPC commands +- DL power control using DPC\_MODE= 0 is assumed +- Dual-antenna receive-diversity at Node B +- Uplink channel phase estimation averaged over either 1 or 3 slots +- UL channel model: PA, PB or VA +- UE speed 3 or 120km/h + +![Figure 4.1.2.1-1: UL TPC error rate for PB3 with 3-slot channel estimate. The graph shows Error rate (log scale, 10^-5 to 10^0) versus Eb/N0 / dB (linear scale, -3 to 7). Five curves are plotted for different pilot/TPC slot configurations: 8 pilot, 2 TPC (black); 6 pilot, 4 TPC (blue); 5 pilot, 5 TPC (magenta); 4 pilot, 6 TPC (green); and 2 pilot, 8 TPC (cyan). The 4 pilot, 6 TPC configuration shows the lowest error rate for a given Eb/N0, while the 8 pilot, 2 TPC configuration shows the highest error rate.](b8261918596971c3801af23435c5ea50_img.jpg) + +The figure is a line graph titled "PB3conslots3". The y-axis is labeled "Error rate" and uses a logarithmic scale from $10^{-5}$ to $10^0$ . The x-axis is labeled " $E_b/N_0$ / dB" and uses a linear scale from -3 to 7. There are five data series represented by different colored lines: a black line for "8 pilot, 2 TPC", a blue line for "6 pilot, 4 TPC", a magenta line for "5 pilot, 5 TPC", a green line for "4 pilot, 6 TPC", and a cyan line for "2 pilot, 8 TPC". All curves show a downward trend, indicating that the error rate decreases as the $E_b/N_0$ increases. The green curve (4 pilot, 6 TPC) is the lowest, followed by the cyan (2 pilot, 8 TPC), magenta (5 pilot, 5 TPC), blue (6 pilot, 4 TPC), and finally the black curve (8 pilot, 2 TPC) which is the highest. + +Figure 4.1.2.1-1: UL TPC error rate for PB3 with 3-slot channel estimate. The graph shows Error rate (log scale, 10^-5 to 10^0) versus Eb/N0 / dB (linear scale, -3 to 7). Five curves are plotted for different pilot/TPC slot configurations: 8 pilot, 2 TPC (black); 6 pilot, 4 TPC (blue); 5 pilot, 5 TPC (magenta); 4 pilot, 6 TPC (green); and 2 pilot, 8 TPC (cyan). The 4 pilot, 6 TPC configuration shows the lowest error rate for a given Eb/N0, while the 8 pilot, 2 TPC configuration shows the highest error rate. + +Figure 4.1.2.1-1: UL TPC error rate for PB3 with 3-slot channel estimate + +![Line graph titled 'PA3conslots3' showing Error rate vs Eb/N0 / dB for various pilot and TPC configurations.](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +This line graph, titled 'PA3conslots3', plots the Error rate (y-axis, logarithmic scale from 10-5 to 100) against the Eb/N0 / dB (x-axis, linear scale from -3 to 7). Five curves are shown, representing different pilot and TPC configurations: 8 pilot, 2 TPC (black line); 6 pilot, 4 TPC (blue line); 5 pilot, 5 TPC (magenta line); 4 pilot, 6 TPC (green line); and 2 pilot, 8 TPC (cyan line). The curves show that as the number of pilot bits increases and the number of TPC bits decreases, the error rate performance improves. The 4 pilot, 6 TPC configuration shows the best performance, reaching an error rate of 10-4 at approximately 4 dB Eb/N0. The 8 pilot, 2 TPC configuration shows the worst performance, reaching an error rate of 10-4 at approximately 6.5 dB Eb/N0. + +Line graph titled 'PA3conslots3' showing Error rate vs Eb/N0 / dB for various pilot and TPC configurations. + +Figure 4.1.2.1-2: UL TPC error rate for PA3 with 3-slot channel estimate + +![Line graph titled 'VA120conslots1' showing Error rate vs Eb/N0 / dB for various pilot and TPC configurations.](1145fc59efdc7dacc8d3c715d7ff3248_img.jpg) + +This line graph, titled 'VA120conslots1', plots the Error rate (y-axis, logarithmic scale from 10-4 to 100) against the Eb/N0 / dB (x-axis, linear scale from 0 to 10). Five curves are shown, representing the same pilot and TPC configurations as the previous graph: 8 pilot, 2 TPC (black line); 6 pilot, 4 TPC (blue line); 5 pilot, 5 TPC (magenta line); 4 pilot, 6 TPC (green line); and 2 pilot, 8 TPC (cyan line). The curves show that as the number of pilot bits increases and the number of TPC bits decreases, the error rate performance improves. The 4 pilot, 6 TPC configuration shows the best performance, reaching an error rate of 10-4 at approximately 9.5 dB Eb/N0. The 2 pilot, 8 TPC configuration shows the worst performance, reaching an error rate of 10-4 at approximately 10 dB Eb/N0. + +Line graph titled 'VA120conslots1' showing Error rate vs Eb/N0 / dB for various pilot and TPC configurations. + +Figure 4.1.2.1-3: UL TPC error rate for VA120 with 1-slot channel estimate + +The simulation results presented above for PA, PB and VA channels at UE speeds from 3km/h to 120km/h show that the $E_b/N_0$ required for the UL DPCCH can be reduced for a given TPC error rate by changing the ratio of pilot to TPC bits per slot. The gains are typically in the region 2-3dB. + +Considering the simulations above showing the TPC error rate, a slot format with 4 pilot bits and 6 TPC bits seems to give robust performance regardless of the averaging period of the channel estimate. + +Another set of simulations was run with different algorithms. The simulation parameters are listed in Table 4.1.2.1-1 and the results are shown in Figure 4.1.2.1-4. + +**Table 4.1.2.1-1: Simulation parameters for simulations with realistic algorithms** + +| Parameter | Value | Comment | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Simulation time | 5000 frames (25000 TTIs) | | +| E-DCH data rate | 160 kbps (2ms TTI, 320 bits TB size) | Full buffer | +| E-DPDCH/DPCCH | 8 dB | | +| E-DPCCH/DPCCH | 0 dB | | +| HS-DPCCH/DPCCH | 0 dB | | +| DPDCH | OFF | | +| DPCCH slot formats | 8 pilots + 2 TPC (slot format 1)
6 pilots + 4 TPC (new slot format)
5 pilots + 5 TPC (new slot format)
4 pilots + 6 TPC (new slot format) | | +| Channel models | AWGN
Pedestrian A, 3 km/h
Vehicular A, 30 km/h
Vehicular A, 120 km/h | | +| UL power control | ON | 0% error rate, 1-dB step size, 2-slot delay | +| Node B Rx antennas | 2 | | +| Channel estimation | Realistic | TPC-aided 2-slot sliding average | +| SIR estimation | Realistic | | +| Path delay search | Realistic | | +| Frequency estimation | Ideal | | +| HARQ | ON | Max 4 transmissions | + +![Figure 4.1.2.1-4: DL TPC BER for different UL DPCCH slot formats and various channel models. The figure contains four subplots: AWGN, PA3, VA30, and VA120. Each plot shows DL TPC BER on a log scale (10^-5 to 10^0) versus Eb/N0 (per antenna) [dB]. Four curves are shown in each plot: 8 pilots, 2 TPC (black); 6 pilots, 4 TPC (blue); 5 pilots, 5 TPC (red); and 4 pilots, 6 TPC (green). In the AWGN, PA3, and VA30 models, the 4 pilots, 6 TPC curve shows the best performance (lowest BER). In the VA120 model, the 8 pilots, 2 TPC curve shows the best performance.](fed39b841ae2dce01088b84bfc1e2789_img.jpg) + +Figure 4.1.2.1-4: DL TPC BER for different UL DPCCH slot formats and various channel models. The figure contains four subplots: AWGN, PA3, VA30, and VA120. Each plot shows DL TPC BER on a log scale (10^-5 to 10^0) versus Eb/N0 (per antenna) [dB]. Four curves are shown in each plot: 8 pilots, 2 TPC (black); 6 pilots, 4 TPC (blue); 5 pilots, 5 TPC (red); and 4 pilots, 6 TPC (green). In the AWGN, PA3, and VA30 models, the 4 pilots, 6 TPC curve shows the best performance (lowest BER). In the VA120 model, the 8 pilots, 2 TPC curve shows the best performance. + +Figure 4.1.2.1-4: DL TPC BER for different UL DPCCH slot formats and various channel models + +#### 4.1.2.2 Simulation results on other UL channels + +The basic simulation assumptions here are as follows: + +- 2GHz carrier frequency +- DPCCH SF = 256 +- Non-SHO +- UL power control using PCA1 and a 1dB step size, with a 4% error rate on DL TPC commands +- Dual-antenna receive-diversity at Node B +- Uplink channel phase estimation averaged over 1 to 3 slots, TPC-aided where shown +- UL channel model: PA, PB or VA +- UE speed 3, 30 or 120km/h + +The case of HS-DPCCH being transmitted in parallel with the DPCCH is considered, to examine the effect of changing the DPCCH slot format on the decoding of the HS-DPCCH. For the HS-DPCCH, the following assumptions are used: + +- $\beta_{hs} = \beta_c$ ( $\Delta_{ACK} = \Delta_{NACK} = \Delta_{CQI}$ ) +- $N\_cqi\_transmit = 1$ (i.e. no repetition) +- $N\_acknack\_transmit = 1$ (i.e. no repetition) +- Node B detection threshold for ACK configured to give $P(ACK|DTX) = 0.1$ (assuming the probability of missed detection for HS-SCCH at the UE is $10e-2$ ). + +Under these conditions, the CQI and ACK error rates are measured, using two different types of channel estimation: + +- Channel estimation using DPCCH pilot bits only +- TPC-aided channel estimation (using both pilot bits and TPC bits) + +MLSE decoding is used for CQI. + +The following DPCCH slot formats are evaluated: + +| Slot Form at #I | Channel Bit Rate (kbps) | Channel Symbol Rate (ksps) | SF | Bits/Frame | Bits/Slot | N pilot | N TPC | N TFCI | N FBI | +|-----------------|-------------------------|----------------------------|-----|------------|-----------|--------------------|------------------|-------------------|------------------| +| 1 | 15 | 15 | 256 | 150 | 10 | 8 | 2 | 0 | 0 | +| New 1 | 15 | 15 | 256 | 150 | 10 | 5 | 5 | 0 | 0 | +| New 2 | 15 | 15 | 256 | 150 | 10 | 4 | 6 | 0 | 0 | + +##### 4.1.2.2.1 CQI transmission + +![Two line graphs showing CQI performance in PA3, 1 slot channel estimation. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both plots show Error rate (log scale) vs Eb/N0 / dB (linear scale) for three CQI configurations: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed). In both cases, the 8pi, 2TPC configuration shows the lowest error rate, followed by 5pi, 5TPC, and then 4pi, 6TPC. The TPC-aided estimation shows improved performance across all configurations compared to the standard estimation.](07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg) + +Two line graphs showing CQI performance in PA3, 1 slot channel estimation. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both plots show Error rate (log scale) vs Eb/N0 / dB (linear scale) for three CQI configurations: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed). In both cases, the 8pi, 2TPC configuration shows the lowest error rate, followed by 5pi, 5TPC, and then 4pi, 6TPC. The TPC-aided estimation shows improved performance across all configurations compared to the standard estimation. + +Figure 4.1.2.2.1-1: CQI performance in PA3, 1 slot channel estimation, with and without TPC-assistance + +![Two line graphs showing CQI performance in PA3, 3 slot channel estimation. The top graph is for standard estimation, and the bottom graph is for TPC-aided estimation. Both plots show Error rate vs Eb/N0 / dB for three CQI configurations: 8pi, 2TPC; 5pi, 5TPC; and 4pi, 6TPC.](1c427123350e0e73e2a109b79069314b_img.jpg) + +The figure consists of two vertically stacked line graphs. Both graphs have a logarithmic y-axis labeled 'Error rate' ranging from $10^{-3}$ to $10^0$ , and an x-axis labeled 'Eb/No / dB' ranging from -6 to 5. The top graph is titled 'PA3, 3 slots channel estimate' and the bottom graph is titled 'PA3, 3 slots channel estimate (TPC-aided)'. Each graph contains three data series: a black dashed line for 'CQI: 8pi, 2TPC', a magenta dashed line for 'CQI: 5pi, 5TPC', and a green dashed line for 'CQI: 4pi, 6TPC'. In both plots, the error rate decreases as the Eb/N0 increases. The TPC-aided estimation (bottom graph) shows a lower error rate for all configurations compared to the standard estimation (top graph). The 8pi, 2TPC configuration consistently achieves the lowest error rate across the range of Eb/N0 values. + +Two line graphs showing CQI performance in PA3, 3 slot channel estimation. The top graph is for standard estimation, and the bottom graph is for TPC-aided estimation. Both plots show Error rate vs Eb/N0 / dB for three CQI configurations: 8pi, 2TPC; 5pi, 5TPC; and 4pi, 6TPC. + +**Figure 4.1.2.2.1-2: CQI performance in PA3, 3 slot channel estimation, with and without TPC-assistance** + +![Two line graphs showing Error rate vs Eb/No / dB for PB3, 1 slots channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs compare CQI 8pi, 2TPC (black dashed line), CQI 5pi, 5TPC (magenta dashed line), and CQI 4pi, 6TPC (green dashed line).](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +The figure consists of two vertically stacked line graphs. Both plots have 'Error rate' on the y-axis (logarithmic scale from $10^{-3}$ to $10^0$ ) and ' $E_b/N_0$ / dB' on the x-axis (linear scale from -6 to 5). The top plot is titled 'PB3, 1 slots channel estimate' and the bottom plot is titled 'PB3, 1 slots channel estimate (TPC-aided)'. Each plot contains three data series: 'CQI: 8pi, 2TPC' (black dashed line), 'CQI: 5pi, 5TPC' (magenta dashed line), and 'CQI: 4pi, 6TPC' (green dashed line). In the top plot, the black line reaches an error rate of $10^{-3}$ at approximately 0 dB, while the green line reaches it at approximately 2 dB. In the bottom plot, the black line reaches an error rate of $10^{-3}$ at approximately 0.5 dB, and the green line reaches it at approximately 4.5 dB. + +Two line graphs showing Error rate vs Eb/No / dB for PB3, 1 slots channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs compare CQI 8pi, 2TPC (black dashed line), CQI 5pi, 5TPC (magenta dashed line), and CQI 4pi, 6TPC (green dashed line). + +**Figure 4.1.2.2.1-3: CQI performance in PB3, 1 slot channel estimation, with and without TPC-assistance** + +![Two line graphs showing Error rate vs Eb/N0 / dB for PB3, 3 slots channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs show three curves for CQI: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed).](ebce355620876e10f907f8b71926c112_img.jpg) + +The figure consists of two vertically stacked line graphs. Both plots have 'Error rate' on the y-axis (logarithmic scale from $10^{-3}$ to $10^0$ ) and $E_b/N_0 / \text{dB}$ on the x-axis (linear scale from -6 to 5). Each plot contains three dashed lines representing different CQI configurations: 8pi with 2TPC (black), 5pi with 5TPC (magenta), and 4pi with 6TPC (green). + +**Top Plot: PB3, 3 slots channel estimate** + +| $E_b/N_0 / \text{dB}$ | CQI: 8pi, 2TPC (Error Rate) | CQI: 5pi, 5TPC (Error Rate) | CQI: 4pi, 6TPC (Error Rate) | +|-----------------------|-----------------------------|-----------------------------|-----------------------------| +| -6 | ~0.3 | ~0.5 | ~0.6 | +| -5 | ~0.2 | ~0.4 | ~0.5 | +| -4 | ~0.1 | ~0.3 | ~0.4 | +| -3 | ~0.04 | ~0.15 | ~0.25 | +| -2 | ~0.005 | ~0.05 | ~0.1 | +| -1 | < $10^{-3}$ | ~0.01 | ~0.03 | +| 0 | - | ~0.001 | ~0.005 | + +**Bottom Plot: PB3, 3 slots channel estimate (TPC-aided)** + +| $E_b/N_0 / \text{dB}$ | CQI: 8pi, 2TPC (Error Rate) | CQI: 5pi, 5TPC (Error Rate) | CQI: 4pi, 6TPC (Error Rate) | +|-----------------------|-----------------------------|-----------------------------|-----------------------------| +| -6 | ~0.25 | ~0.45 | ~0.55 | +| -5 | ~0.15 | ~0.35 | ~0.45 | +| -4 | ~0.08 | ~0.25 | ~0.35 | +| -3 | ~0.03 | ~0.12 | ~0.2 | +| -2 | ~0.004 | ~0.04 | ~0.08 | +| -1 | < $10^{-3}$ | ~0.008 | ~0.02 | +| 0 | - | ~0.0008 | ~0.004 | + +Two line graphs showing Error rate vs Eb/N0 / dB for PB3, 3 slots channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs show three curves for CQI: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed). + +Figure 4.1.2.2.1-4: CQI performance in PB3, 3 slot channel estimation, with and without TPC-assistance + +![Two line graphs showing Error rate vs Eb/N0 for VA30, 1 slot channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs compare CQI 8pi, 2TPC (black dashed line), CQI 5pi, 5TPC (magenta dashed line), and CQI 4pi, 6TPC (green dashed line).](7f687094e6abe34a9cf491942b296d9a_img.jpg) + +The figure consists of two vertically stacked line graphs. Both graphs plot 'Error rate' on a logarithmic y-axis (from $10^0$ down to $10^{-3}$ ) against $E_b/N_0$ / dB on a linear x-axis (from -6 to 5). + +The top graph is titled "VA30, 1 slots channel estimate". It shows three curves: + + +- CQI: 8pi, 2TPC (black dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 1.5 dB. +- CQI: 5pi, 5TPC (magenta dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 3 dB. +- CQI: 4pi, 6TPC (green dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 3.8 dB. + +The bottom graph is titled "VA30, 1 slots channel estimate (TPC-aided)". It shows three curves: + + +- CQI: 8pi, 2TPC (black dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 1.5 dB. +- CQI: 5pi, 5TPC (magenta dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 4.2 dB. +- CQI: 4pi, 6TPC (green dashed line): Starts at $10^0$ at -6 dB and drops to $10^{-3}$ at approx 4.8 dB. + +Two line graphs showing Error rate vs Eb/N0 for VA30, 1 slot channel estimate. The top graph is for standard channel estimation, and the bottom graph is for TPC-aided channel estimation. Both graphs compare CQI 8pi, 2TPC (black dashed line), CQI 5pi, 5TPC (magenta dashed line), and CQI 4pi, 6TPC (green dashed line). + +**Figure 4.1.2.2.1-5: CQI performance in VA30, 1 slot channel estimation, with and without TPC-assistance** + +![Two line graphs showing Error rate vs Eb/N0 / dB for VA30, 2 slots channel estimate. The top graph is for the standard case, and the bottom graph is for the TPC-aided case. Both graphs show three curves for CQI: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed). The TPC-aided case shows improved performance (lower error rate) across the Eb/N0 range from -6 to 5 dB.](a289b64f80c6df506c0c55d553fc4496_img.jpg) + +The figure consists of two vertically stacked line graphs. Both plots have 'Error rate' on the y-axis (logarithmic scale from 10-3 to 100) and 'Eb/N0 / dB' on the x-axis (linear scale from -6 to 5). The top plot is titled 'VA30, 2 slots channel estimate' and the bottom plot is titled 'VA30, 2 slots channel estimate (TPC-aided)'. Each plot contains three curves: a black dashed line for 'CQI: 8pi, 2TPC', a magenta dashed line for 'CQI: 5pi, 5TPC', and a green dashed line for 'CQI: 4pi, 6TPC'. In the top plot, the curves show a sharp drop in error rate starting around Eb/N0 = -4 dB. In the bottom plot, the curves show a similar drop but are shifted to the right, indicating better performance (lower error rate for the same Eb/N0). The TPC-aided case consistently achieves a lower error rate than the standard case across the entire Eb/N0 range. + +Two line graphs showing Error rate vs Eb/N0 / dB for VA30, 2 slots channel estimate. The top graph is for the standard case, and the bottom graph is for the TPC-aided case. Both graphs show three curves for CQI: 8pi, 2TPC (black dashed); 5pi, 5TPC (magenta dashed); and 4pi, 6TPC (green dashed). The TPC-aided case shows improved performance (lower error rate) across the Eb/N0 range from -6 to 5 dB. + +Figure 4.1.2.2.1-6: CQI performance in VA30, 2 slot channel estimation, with and without TPC-assistance + +![Two line graphs showing Error rate vs Eb/N0 / dB for CQI performance in VA120, 1 slot channel estimate. The top graph is for 'VA120, 1 slots channel estimate' and the bottom graph is for 'VA120, 1 slots channel estimate (TPC-aided)'. Both graphs show three curves: CQI: 8pi, 2TPC (black dashed), CQI: 5pi, 5TPC (magenta dashed), and CQI: 4pi, 6TPC (green dashed). The TPC-aided graph shows improved performance (lower error rate) for all configurations.](45329c7d9aa2bd1290af5b2027f08d7e_img.jpg) + +The figure consists of two vertically stacked line graphs. Both plots have 'Error rate' on the y-axis (logarithmic scale from 10-3 to 100) and 'Eb/N0 / dB' on the x-axis (linear scale from -6 to 5). The top plot is titled 'VA120, 1 slots channel estimate' and the bottom plot is titled 'VA120, 1 slots channel estimate (TPC-aided)'. Each plot contains three data series: 'CQI: 8pi, 2TPC' (black dashed line), 'CQI: 5pi, 5TPC' (magenta dashed line), and 'CQI: 4pi, 6TPC' (green dashed line). In the top plot, the error rate decreases as Eb/N0 increases, with the 8pi, 2TPC configuration showing the lowest error rate. In the bottom plot, the error rate is generally lower across the Eb/N0 range compared to the top plot, indicating improved performance with TPC assistance. The 8pi, 2TPC configuration again shows the lowest error rate in the TPC-aided scenario. + +Two line graphs showing Error rate vs Eb/N0 / dB for CQI performance in VA120, 1 slot channel estimate. The top graph is for 'VA120, 1 slots channel estimate' and the bottom graph is for 'VA120, 1 slots channel estimate (TPC-aided)'. Both graphs show three curves: CQI: 8pi, 2TPC (black dashed), CQI: 5pi, 5TPC (magenta dashed), and CQI: 4pi, 6TPC (green dashed). The TPC-aided graph shows improved performance (lower error rate) for all configurations. + +Figure 4.1.2.2.1-7: CQI performance in VA120, 1 slot channel estimation, with and without TPC-assistance + +##### 4.1.2.2.2 + +##### HARQ-ACK transmission + +![Two line graphs showing Error rate vs Eb/N0 for HARQ-ACK transmission with different channel estimates (peda,1 and peda,2) and TPC settings (8pi, 5pi, 4pi).](d8d893dd559845f86c5dd46147ef98b6_img.jpg) + +The figure contains two line graphs, one for 'peda,1 slots channel estimate' and another for 'peda,2 slots channel estimate'. Both graphs plot 'Error rate' on a logarithmic y-axis (from 10-3 to 100) against 'Eb/N0 / dB' on a linear x-axis (from -6 to 5). Three data series are shown in each graph: 'ACK: 8pi, 2TPC' (black dashed line), 'ACK: 5pi, 5TPC' (magenta dashed line), and 'ACK: 4pi, 6TPC' (green dashed line). In both cases, the error rate decreases as Eb/N0 increases. The 8pi, 2TPC configuration generally achieves a lower error rate than the others, while the 4pi, 6TPC configuration shows the highest error rate across the range. + +| Eb/N0 / dB | ACK: 8pi, 2TPC | ACK: 5pi, 5TPC | ACK: 4pi, 6TPC | +|------------|--------------------|----------------|----------------| +| -6 | ~0.4 | ~0.4 | ~0.4 | +| -4 | ~0.2 | ~0.25 | ~0.3 | +| -2 | ~0.08 | ~0.1 | ~0.12 | +| 0 | ~0.01 | ~0.02 | ~0.03 | +| 2 | < 10 -3 | ~0.005 | ~0.01 | + +| Eb/N0 / dB | ACK: 8pi, 2TPC | ACK: 5pi, 5TPC | ACK: 4pi, 6TPC | +|------------|--------------------|--------------------|--------------------| +| -6 | ~0.4 | ~0.4 | ~0.4 | +| -4 | ~0.2 | ~0.2 | ~0.2 | +| -2 | ~0.08 | ~0.08 | ~0.08 | +| 0 | ~0.01 | ~0.01 | ~0.01 | +| 2 | < 10 -3 | < 10 -3 | < 10 -3 | + +Two line graphs showing Error rate vs Eb/N0 for HARQ-ACK transmission with different channel estimates (peda,1 and peda,2) and TPC settings (8pi, 5pi, 4pi). + +Figure 4.1.2.2.2-1: ACK performance in PA3, 1 and 2 slot channel estimation, with TPC-assistance + +![Two line graphs showing ACK performance (Error rate vs Eb/N0) for 1 and 2 slot channel estimates. The top graph is for 'pedb,1 slots channel estimate' and the bottom for 'pedb,2 slots channel estimate'. Both show three curves: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). In both cases, the 8pi, 2TPC configuration achieves the lowest error rate, followed by 5pi, 5TPC, and then 4pi, 6TPC.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +The figure contains two subplots. The top subplot is titled 'pedb,1 slots channel estimate' and the bottom subplot is titled 'pedb,2 slots channel estimate'. Both plots have 'Error rate' on the y-axis (logarithmic scale from 10-3 to 100) and 'Eb/N0 / dB' on the x-axis (linear scale from -6 to 5). Each plot contains three data series: a black dashed line for 'ACK: 8pi, 2TPC', a magenta dashed line for 'ACK: 5pi, 5TPC', and a green dashed line for 'ACK: 4pi, 6TPC'. In both subplots, the black dashed line shows the best performance (lowest error rate), followed by the magenta dashed line, and then the green dashed line. The performance improves as the number of slots increases from 1 to 2. + +Two line graphs showing ACK performance (Error rate vs Eb/N0) for 1 and 2 slot channel estimates. The top graph is for 'pedb,1 slots channel estimate' and the bottom for 'pedb,2 slots channel estimate'. Both show three curves: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). In both cases, the 8pi, 2TPC configuration achieves the lowest error rate, followed by 5pi, 5TPC, and then 4pi, 6TPC. + +Figure 4.1.2.2.2-2: ACK performance in PB3, 1 and 2 slot channel estimation, both with TPC-assistance + +![Two line graphs showing ACK performance in VA30 channel estimation. The top graph is for 'veha, 1 slots channel estimate' and the bottom graph is for 'veha, 2 slots channel estimate'. Both plots show Error rate (log scale, 10^-3 to 10^0) vs Eb/N0 / dB (-6 to 5). Three curves are shown: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). In both cases, the 1-slot estimation shows better performance (lower error rate) than the 2-slot estimation.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +Two line graphs showing ACK performance in VA30 channel estimation. The top graph is for 'veha, 1 slots channel estimate' and the bottom graph is for 'veha, 2 slots channel estimate'. Both plots show Error rate (log scale, 10^-3 to 10^0) vs Eb/N0 / dB (-6 to 5). Three curves are shown: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). In both cases, the 1-slot estimation shows better performance (lower error rate) than the 2-slot estimation. + +Figure 4.1.2.2.2-3: ACK performance in VA30, 1 and 2 slot channel estimation, both with TPC-assistance + +![A line graph showing ACK performance in VA120 channel estimation with TPC-assistance. The plot is titled 'veha, 1 slots channel estimate' and shows Error rate (log scale, 10^-3 to 10^0) vs Eb/N0 / dB (-6 to 5). Three curves are shown: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). The performance is generally worse than in the VA30 scenario.](d6a5f8423065d7cef55e11a0007014d9_img.jpg) + +A line graph showing ACK performance in VA120 channel estimation with TPC-assistance. The plot is titled 'veha, 1 slots channel estimate' and shows Error rate (log scale, 10^-3 to 10^0) vs Eb/N0 / dB (-6 to 5). Three curves are shown: ACK: 8pi, 2TPC (black dashed), ACK: 5pi, 5TPC (magenta dashed), and ACK: 4pi, 6TPC (green dashed). The performance is generally worse than in the VA30 scenario. + +Figure 4.1.2.2.2-4: ACK performance in VA120, 1 slot channel estimation, with TPC-assistance + +The E-DCH and HS-DPCCH performance was also simulated with the simulation parameters listed in Table 4.1.2.1-1. The results are shown in Figures 4.1.2.2.2-5, 4.1.2.2.2-6 and 4.1.2.2.2-7. + +Error: + +28 + +Error: Reference source not + +![Four line graphs showing Throughput (bps) vs Eb/N0 (per antenna) [dB] for AWGN, PA3, VA30, and VA120 channel models. Each graph compares four slot formats: 8 pilots, 2 TPC; 6 pilots, 4 TPC; 5 pilots, 5 TPC; and 4 pilots, 6 TPC. The y-axis is scaled by 10^4. The x-axis ranges from -10 to 10 dB for AWGN, PA3, and VA30, and from -10 to 15 dB for VA120. In all cases, throughput increases with Eb/N0 and plateaus around 15-16 x 10^4 bps. The VA120 model shows a more pronounced difference between the slot formats, with the 8 pilots, 2 TPC format achieving the highest throughput at lower Eb/N0 values.](85b10db535b22e64c7d37f362705ddbf_img.jpg) + +The figure consists of four subplots arranged in a 2x2 grid, each showing the throughput (bps) versus the $E_b/N_0$ (per antenna) [dB] for different channel models: AWGN, PA3, VA30, and VA120. The y-axis for all plots is labeled "Throughput [bps]" and is scaled by $10^4$ . The x-axis is labeled "Eb/N0 (per antenna) [dB]". For AWGN, PA3, and VA30, the x-axis ranges from -10 to 10 dB, while for VA120 it ranges from -10 to 15 dB. Each plot compares four different UL DPCCH slot formats: 8 pilots, 2 TPC (blue line); 6 pilots, 4 TPC (red line); 5 pilots, 5 TPC (green line); and 4 pilots, 6 TPC (cyan line). In all channel models, the throughput increases as $E_b/N_0$ increases and eventually reaches a plateau at approximately $15 \times 10^4$ bps. The VA120 channel model shows a more significant performance difference between the slot formats compared to the others, with the 8 pilots, 2 TPC format performing best at lower $E_b/N_0$ values. + +Four line graphs showing Throughput (bps) vs Eb/N0 (per antenna) [dB] for AWGN, PA3, VA30, and VA120 channel models. Each graph compares four slot formats: 8 pilots, 2 TPC; 6 pilots, 4 TPC; 5 pilots, 5 TPC; and 4 pilots, 6 TPC. The y-axis is scaled by 10^4. The x-axis ranges from -10 to 10 dB for AWGN, PA3, and VA30, and from -10 to 15 dB for VA120. In all cases, throughput increases with Eb/N0 and plateaus around 15-16 x 10^4 bps. The VA120 model shows a more pronounced difference between the slot formats, with the 8 pilots, 2 TPC format achieving the highest throughput at lower Eb/N0 values. + +Figure 4.1.2.2.2-5: Throughput for different UL DPCCH slot formats and various channel models + +Error: + +29 + +Error: Reference source not + +![Four line graphs showing P(missed ACK) vs Eb/N0 for AWGN, PA3, VA30, and VA120 channel models. Each graph compares 8, 6, 5, and 4 pilot configurations with 2, 4, 5, and 6 TPC respectively.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +The figure consists of four subplots, each representing a different channel model: AWGN, PA3, VA30, and VA120. Each subplot shows the 'P(missed ACK)' on a logarithmic y-axis (ranging from 10-5 to 100) against the 'Eb/N0 (per antenna) [dB]' on the x-axis. The x-axis scale varies by model: AWGN (-10 to 4), PA3 (-10 to 4), VA30 (-10 to 8), and VA120 (-10 to 15). Each plot contains four curves representing different pilot and TPC configurations: 8 pilots, 2 TPC (black line); 6 pilots, 4 TPC (blue line); 5 pilots, 5 TPC (red line); and 4 pilots, 6 TPC (green line). In the AWGN, PA3, and VA30 models, all curves follow a similar downward trend, indicating good performance. However, in the VA120 model, the 4 pilots, 6 TPC configuration (green line) shows a significant performance degradation, reaching an error floor around 10-2 after Eb/N0 = 5 dB, while the other configurations continue to decrease. + +Four line graphs showing P(missed ACK) vs Eb/N0 for AWGN, PA3, VA30, and VA120 channel models. Each graph compares 8, 6, 5, and 4 pilot configurations with 2, 4, 5, and 6 TPC respectively. + +Figure 4.1.2.2.2-6: Probability of missed ACK for different UL DPCCH slot formats and various channel models + +![Figure 4.1.2.2.2-7: CQI decoding error rate for different UL DPCCH slot formats and various channel models. The figure consists of four subplots: AWGN, PA3, VA30, and VA120. Each subplot shows the CQI decoding error rate (log scale, 10^-5 to 10^0) versus Eb/N0 (per antenna) [dB]. Four curves are shown in each plot: 8 pilots, 2 TPC (black); 6 pilots, 4 TPC (blue); 5 pilots, 5 TPC (red); and 4 pilots, 6 TPC (green). In the AWGN, PA3, and VA30 models, all curves show a steep decrease in error rate as Eb/N0 increases. In the VA120 model, the curves for 4 and 5 pilot bits (green and red) show an error floor around 10^-2 and 10^-3 respectively, while the 6 and 8 pilot bit curves continue to decrease towards 10^-4 and 10^-5.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Figure 4.1.2.2.2-7: CQI decoding error rate for different UL DPCCH slot formats and various channel models. The figure consists of four subplots: AWGN, PA3, VA30, and VA120. Each subplot shows the CQI decoding error rate (log scale, 10^-5 to 10^0) versus Eb/N0 (per antenna) [dB]. Four curves are shown in each plot: 8 pilots, 2 TPC (black); 6 pilots, 4 TPC (blue); 5 pilots, 5 TPC (red); and 4 pilots, 6 TPC (green). In the AWGN, PA3, and VA30 models, all curves show a steep decrease in error rate as Eb/N0 increases. In the VA120 model, the curves for 4 and 5 pilot bits (green and red) show an error floor around 10^-2 and 10^-3 respectively, while the 6 and 8 pilot bit curves continue to decrease towards 10^-4 and 10^-5. + +**Figure 4.1.2.2.2-7: CQI decoding error rate for different UL DPCCH slot formats and various channel models** + +##### 4.1.2.2.3 Observations from simulations of HS-DPCCH performance in sub-clauses 4.1.2.2.1 and 4.1.2.2.2 + +From the simulation results presented above, it is observed that: + +1. If a new DPCCH slot format with fewer pilot bits is used during HS-DPCCH transmissions, there is degradation in HS-DPCCH performance for CQI (typically around 2dB). +2. The degradation in HS-DPCCH performance can be reduced slightly by using TPC-aided channel estimation, but only if the channel is sufficiently static for the channel estimate to be averaged over a few slots. When the coherence time of the channel is shorter, so that the channel estimate has to be derived from only 1 slot, use of TPC-aiding for the channel estimation further degrades the HS-DPCCH performance. +3. When using TPC-aided channel estimation, the ACK error rate degradation from DPCCH slot formats with more TPC bits is smaller than for CQI. +4. The degradation in ACK error rate is larger for a new slot format with 4 pilot bits than for a new slot format with 5 pilot bits. +5. In terms of throughput, a new slot format with fewer pilot bits but more TPC bits gives similar performance as slot format 1. However, for VA120, slot format 1 performs better, but a slot format with 6 pilot bits and 4 TPC bits performs decently also for VA120. + +#### 4.1.2.3 Conclusions from TPC performance (sub-clause 4.1.2.1) and HS-DPCCH performance (sub-clause 4.1.2.2) + +In the light of the observed performance of TPC and HS-DPCCH, the following behaviour could be useful: + +- A new slot format is configured by RRC signalling in the same way as Rel-99 slot formats; +- The new slot format uses 5 pilot bits and 5 TPC bits; +- In DPCCH slots that overlap a CQI transmission, the slot format switches dynamically to format 1 (8 pilots + 2 TPC) in order to avoid degrading the HS-DSCH performance. + - Note that the Serving Node B knows exactly when to expect transmissions on the HS-DPCCH, so with this proposal there is no need for the Serving Node B to blind-detect the change of DPCCH slot format. +- In other DPCCH slots, including those where E-DCH is transmitted (unless HS-DPCCH is also transmitted), the new slot format continues to be used. (As the Node B does not have full knowledge of when E-DCH will be transmitted, keeping the slot format the same avoids any need for blind detection of the DPCCH slot format at the Node B). +- In slots where E-DCH is transmitted, the UE can apply a DPCCH power offset if more pilot energy is needed. As the E-DPDCH transmission power will typically be considerably greater than the HS-DPCCH transmission power, the relative impact on total power of increasing the DPCCH power would be smaller in this case. +- Alternatively, if it were to be decided that the new slot format should be semi-static (“Proposal B” in sub-clause 4.1.1.2), the new slot format would need more than 5 pilot bits in order to reduce the degradation to CQI transmission. + +#### 4.1.2.4 Power control delay + +Assuming that the downlink uses F-DPCH, the minimum loop delay for the uplink power control is 1 slot, while the minimum loop delay for the downlink power control is 2 slots. This is shown in Figure 4.1.2.4-1. + +![Figure 4.1.2.4-1: Power control loop delays with normal F-DPCH operation. The diagram illustrates the timing relationships between Downlink F-DPCH (DL F-DPCH) and Uplink DPCCH (UL DPCCH) signals. The top signal, DL F-DPCH at UTRAN, shows a slot of 2560 chips with TPC bits. The second signal, DL F-DPCH at UE, shows the same slot with a propagation delay \tau_p and a DL-UL timing offset of 1024 chips. A DL SIR measurement is taken at the UE. The third signal, UL DPCCH at UE, shows a slot of 2560 chips with PILOT, TFCI, and TPC fields. A UL SIR measurement is taken at the UE. The bottom signal, UL DPCCH at UTRAN, shows the same slot with a propagation delay. Arrows indicate the flow of information: 'Response To TPC' from the UE's UL DPCCH to the UTRAN's DL F-DPCH, and 'Response to TPC' from the UTRAN's UL DPCCH to the UE's DL F-DPCH.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +Figure 4.1.2.4-1: Power control loop delays with normal F-DPCH operation. The diagram illustrates the timing relationships between Downlink F-DPCH (DL F-DPCH) and Uplink DPCCH (UL DPCCH) signals. The top signal, DL F-DPCH at UTRAN, shows a slot of 2560 chips with TPC bits. The second signal, DL F-DPCH at UE, shows the same slot with a propagation delay $\tau_p$ and a DL-UL timing offset of 1024 chips. A DL SIR measurement is taken at the UE. The third signal, UL DPCCH at UE, shows a slot of 2560 chips with PILOT, TFCI, and TPC fields. A UL SIR measurement is taken at the UE. The bottom signal, UL DPCCH at UTRAN, shows the same slot with a propagation delay. Arrows indicate the flow of information: 'Response To TPC' from the UE's UL DPCCH to the UTRAN's DL F-DPCH, and 'Response to TPC' from the UTRAN's UL DPCCH to the UE's DL F-DPCH. + +Figure 4.1.2.4-1: Power control loop delays with normal F-DPCH operation + +The power control loop delays with any of the new UL DPCCH slot formats proposed above are the same as with normal F-DPCH operation. Figure 4.1.2.4-2 shows an example for a slot format with 4 pilot bits and 6 TPC bits. + +**Error:** + +32 + +**Error: Reference source not** + +![Timing diagram illustrating power control loop delays between UTRAN and UE for DL F-DPCH and UL DPCCH.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The diagram illustrates the timing relationship between Downlink (DL) and Uplink (UL) channels for power control. It shows four timelines: + +- DL F-DPCH at UTRAN:** Shows slots of 2560 chips with TPC fields. A reference time $\tau_0$ marks the start of a slot. +- DL F-DPCH at UE:** Delayed by propagation delay $\tau_p$ . Shows a DL-UL timing offset of 1024 chips. A DL SIR measurement is taken 512 chips into the slot. +- UL DPCCH at UE:** Consists of PILOT and TPC fields. A slot is 2560 chips. There is a propagation delay indicated. +- UL DPCCH at UTRAN:** Received version of the UL DPCCH. Shows UL SIR measurement occurring during the PILOT/TPC transition. + +Arrows indicate 'Response to TPC' feedback loops between the UE and UTRAN timelines. + +Timing diagram illustrating power control loop delays between UTRAN and UE for DL F-DPCH and UL DPCCH. + +**Figure 4.1.2.4-2: Example of power control loop delays with new UL DPCCH slot format** + +### 4.1.3 Benefits of the concept + +The concept “New UL DPCCH slot format” could be combined with the concept “SIR\_target lowering & CQI off” as well as with the concept of “UL DPCCH gating”. + +- For a given TPC reliability the required DPCCH power would be reduced by around 2-4dB compared to existing UL DPCCH slot formats, thus reducing UL DPCCH noise contribution and also increasing UE battery life time compared to REL-6. +- Compared to REL-6: Increased number of temporarily inactive users that can stay in CELL\_DCH and that can therefore get active in a very short time avoiding frequent transitions to CELL\_FACH. +- There is no impact on TPC loop delay. + +### 4.1.4 Open issues of the concept + +- Suitable mechanisms (e.g. triggers and/or signalling) for changing the slot format? (considering how frequently it may be beneficial to change the slot format.) +- The use of the new slot format in soft handover needs to be investigated. + +## 4.2 Uplink DPCCH gating + +### 4.2.1 Description of the concept + +The Uplink DPCCH Gating concept applies to a HSDPA/HSUPA scenario only, with no DCHs configured in either direction. The uplink TPC commands sent in the downlink are assumed to be carried over F-DPCH, but one could use associated DPCCH as well. + +#### 4.2.1.1 General principle + +The optimal solution for reducing DPCCH overhead of packet data users is turning off the DPCCH transmission when no data or HS-DPCCH is being transmitted. With such an ideal solution the idle packet data users would not consume any uplink air interface resources and the network resource allocation would set the limit on how many idle users could + +be kept in the CELL\_DCH state. Due to practical reasons there may be a limit on the length of the DPCCH gating period as during long inactivity the Node B could not any more know whether the uplink synchronisation is lost or if there just is a very long inactivity period. + +In order to support longer uplink DPCCH gating gaps, the transmission after a gap is proposed to be preceded by a DPCCH preamble of sufficient length in order to facilitate the detection of the signal. Also, in order to save Node B receiver resources, DRX in the uplink is proposed to be allowed during the uplink DPCCH gating gaps. + +The basic principle in short is that if there is neither E-DCH nor HS-DPCCH transmission, the UE automatically stops the continuous DPCCH transmission and applies a known DPCCH activity (DPCCH on/off) pattern. When an E-DCH or HS-DPCCH transmission takes place also the DPCCH is transmitted regardless of the activity pattern. + +I.e. during the E-DCH and HS-DPCCH inactivity the UE would activate a known DPCCH transmission pattern that would be e.g. a few DPCCH slots transmitted every few radio frames and no DPCCH transmission during other times. If E-DCH or HS-DPCCH is transmitted the DPCCH would be transmitted normally regardless of the pattern. Depending on the length of the DPCCH transmission gap, a DPCCH power control preamble of few slots may be needed before E-DCH/HS-DPCCH transmission may start. Reception of the downlink HS-SCCH/HS-PDSCH would be active and possible at all times. During the periods when UL DPCCH is not transmitted, Node B will not be able to perform UL SIR estimation and has no information on which to base the UL TPC commands sent on F-DPCH. Therefore the F-DPCH should also be gated during the periods of UL DPCCH gating. + +#### 4.2.1.2 Basic packet traffic example + +Figure 4.2.1.2-1 depicts the basic idea, where during data traffic activity (e.g. web page is being transmitted in the downlink and TCP acknowledgements as well as HSDPA acknowledgements are transmitted in the uplink) everything operates as with Release 6 specifications. When the data traffic stops the continuous DPCCH transmission in the uplink is shut down too. Occasionally during the data inactivity the DPCCH is transmitted in a predetermined pattern so that the Node B always knows to expect some slots of DPCCH transmission and can still follow the uplink presence and quality. + +![Figure 4.2.1.2-1: Uplink DPCCH transmission with gating. The diagram shows a timeline of radio frames divided into two phases: 'Uplink activity (e.g. TCP ACKs for DL traffic)' and 'Uplink inactivity (e.g. web page reading time)'. During the activity phase, all frames are green, indicating continuous transmission. During the inactivity phase, frames are white (no transmission) or red (some slots transmitting DPCCH due to DPCCH activity pattern). A legend below the timeline defines the frame colors: white for 'Frame with no transmission of any uplink code channel due to no data to transmit', green for 'Frame with continuous transmission', and red for 'Frame with some slots transmitting DPCCH due to DPCCH activity pattern'.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +Figure 4.2.1.2-1: Uplink DPCCH transmission with gating. The diagram shows a timeline of radio frames divided into two phases: 'Uplink activity (e.g. TCP ACKs for DL traffic)' and 'Uplink inactivity (e.g. web page reading time)'. During the activity phase, all frames are green, indicating continuous transmission. During the inactivity phase, frames are white (no transmission) or red (some slots transmitting DPCCH due to DPCCH activity pattern). A legend below the timeline defines the frame colors: white for 'Frame with no transmission of any uplink code channel due to no data to transmit', green for 'Frame with continuous transmission', and red for 'Frame with some slots transmitting DPCCH due to DPCCH activity pattern'. + +Figure 4.2.1.2-1: Uplink DPCCH transmission with gating + +Whenever the uplink has anything to transmit on E-DCH or HS-DPCCH the DPCCH transmission will be automatically reinitiated. + +More generally, during any packet session with any packet activity/inactivity ratio, when the user is transmitting data in the uplink, the DPCCH is continuously active as long as the data or HS-DPCCH transmission is taking place and during the 'reading time', when the uplink is inactive, the DPCCH gating pattern would be applied reducing the consumed uplink capacity to a fraction compared to continuous DPCCH. In addition to reduced uplink capacity consumption the UE talk times would be increased due to lowered battery consumption. + +The actual savings would be heavily depending on the activity factor of the uplink transmission as well as the time before dropping inactive users from CELL\_DCH. + +#### 4.2.1.3 VoIP traffic example + +With VoIP it would be possible also to benefit from the fact that the data transmission timing even during the active phase of VoIP would be known and could be matched with DPCCH gating period. During the active speech phase the UE would transmit the VoIP packet transmissions and retransmissions with DPCCH and between the packets DPCCH would not be transmitted either. + +##### **Example: Gated DPCCH** **3 slots on, 45 off** **Transmitted always** + +![Figure 4.2.1.3-1: DPCCH transmission with gating & 2 ms E-DCH TTI. The diagram shows a timeline of sub-frames (10 ms each) and HARQ processes (1 and 2). A legend indicates white boxes are sub-frames with no transmission and green boxes are sub-frames with transmission. The 'E-DCH VoIP activity example' shows a 2 ms burst every 32 ms. The 'DPCCH transmission during voice inactivity' shows a 2 ms burst every 32 ms. The 'DPCCH transmission during voice activity' shows a 2 ms burst every 32 ms.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +2 ms subframe and HARQ process number + +10 ms + +□ Sub-frame with no transmission + ■ Sub-frame with transmission + +E-DCH VoIP activity example + +DPCCH transmission during voice inactivity + +DPCCH transmission during voice activity + +Figure 4.2.1.3-1: DPCCH transmission with gating & 2 ms E-DCH TTI. The diagram shows a timeline of sub-frames (10 ms each) and HARQ processes (1 and 2). A legend indicates white boxes are sub-frames with no transmission and green boxes are sub-frames with transmission. The 'E-DCH VoIP activity example' shows a 2 ms burst every 32 ms. The 'DPCCH transmission during voice inactivity' shows a 2 ms burst every 32 ms. The 'DPCCH transmission during voice activity' shows a 2 ms burst every 32 ms. + +**Figure 4.2.1.3-1: DPCCH transmission with gating & 2 ms E-DCH TTI. HS-DPCCH impact not shown** + +In Figure 4.2.1.3-1 an example DPCCH gating with 2 ms E-DCH TTI and VoIP traffic (with average transmission rate of 2.5 transmission per packet) mapped to HARQ processes 1 and 2 is shown with DPCCH activity pattern during E-DCH inactivity as 2 ms burst every 32 ms. Note that this is a simplified example; the transmissions and retransmissions do not need to follow this regular pattern in order to get the desired benefits from the DPCCH gating. With such parametrisation the DPCCH overhead would be reduced to ~6% during voice inactivity and to ~25% during voice activity. Assuming 50% voice activity the DPCCH overhead would be reduced to ~16% of the overhead from continuous DPCCH. HS-DPCCH activity and possible power control preambles would reduce the actual gains, but with good parametrisation and possible improvements to CQI reporting, the impact of HS-DPCCH is not dominant. + +##### **Example: Gated DPCCH** **3 slots on, 27 off** **Transmitted always** + +![Figure 4.2.1.3-2: DPCCH transmission with gating & 10 ms E-DCH TTI. The diagram shows a timeline of sub-frames (10 ms each) and HARQ processes (1, 2, and 3). A legend indicates white boxes are sub-frames with no transmission and green boxes are sub-frames with transmission. The 'E-DCH VoIP activity example' shows a 2 ms burst every 20 ms. The 'DPCCH transmission during voice inactivity' shows a 2 ms burst every 20 ms. The 'DPCCH transmission during voice activity' shows a 2 ms burst every 20 ms.](836b0790cef5469a167fa8931df4e408_img.jpg) + +2 ms subframe and HARQ process number + +10 ms + +□ Sub-frame with no transmission + ■ Sub-frame with transmission + +E-DCH VoIP activity example + +DPCCH transmission during voice inactivity + +DPCCH transmission during voice activity + +Figure 4.2.1.3-2: DPCCH transmission with gating & 10 ms E-DCH TTI. The diagram shows a timeline of sub-frames (10 ms each) and HARQ processes (1, 2, and 3). A legend indicates white boxes are sub-frames with no transmission and green boxes are sub-frames with transmission. The 'E-DCH VoIP activity example' shows a 2 ms burst every 20 ms. The 'DPCCH transmission during voice inactivity' shows a 2 ms burst every 20 ms. The 'DPCCH transmission during voice activity' shows a 2 ms burst every 20 ms. + +**Figure 4.2.1.3-2: DPCCH transmission with gating & 10 ms E-DCH TTI. HS-DPCCH impact not shown** + +In Figure 4.2.1.3-2 an example DPCCH gating with 10 ms E-DCH TTI and VoIP traffic (no retransmissions shown, low retransmission rate) mapped to HARQ processes 1 and 3 is shown with DPCCH activity pattern during E-DCH inactivity as 2 ms burst every 20 ms. With such parametrisation the DPCCH overhead would be reduced to 10% during voice inactivity and to ~50% during voice activity. Assuming 50% voice activity the DPCCH overhead would be reduced to ~30% of the overhead from continuous DPCCH. HS-DPCCH activity and potential power control preambles would reduce the actual gains. + +#### 4.2.1.4 Operation of the uplink DPCCH gating + +##### The role of the RNC + +The RNC would control the activation and deactivation of the Uplink DPCCH Gating feature the same way the RNC controls the Preamble/Postamble transmission for HSDPA ACK/NACK transmission. This is essential to guarantee the functionality in the SHO; gating can be used only if all Node B's in the active set support it. RNC should also decide what kind of gating parameters would be used, and signal the information to the Node B(s) and UE. If a Node B in the UE's active set does not support gating the RNC must disable the Uplink DPCCH Gating. + +When the Uplink DPCCH Gating feature is enabled by the RNC the UE would transmit the DPCCH continuously when E-DCH or HS-DPCCH is transmitted and transmit the DPCCH discontinuously during the inactivity of E-DCH and HS-DPCCH according to parameters provided by the RNC. + +##### Criteria for transmitting the uplink DPCCH + +The uplink DPCCH transmission would be resumed if at least one of the following criteria is fulfilled. + +1. The DPCCH transmission pattern defines the time to transmit the DPCCH for synchronisation and power control purposes. +2. A HS-DPCCH transmission is triggered in the UE. + - a. As in Release 5 the HS-SCCH triggers the need for HARQ ACK/NACK feedback on HS-DPCCH. + - b. As in Release 5 the CQI reporting criteria triggers sending a CQI report on HS-DPCCH. +3. An E-DCH transmission is triggered in the UE as in Release 6. + +It could be possible to align some or all the cases of 1,2,3 e.g. allow the E-DCH transmission to start only when the DPCCH transmission pattern would anyway activate the DPCCH transmission, or align the DPCCH transmission pattern's active phase and the CQI reporting. + +##### Criteria for stopping the uplink DPCCH transmission + +The uplink DPCCH transmission would be turned off if all the following criteria are fulfilled. + +1. The DPCCH transmission pattern defines when not to transmit the DPCCH if no other reason requires the DPCCH transmission. +2. The HS-SCCH has not triggered the need for HARQ ACK/NACK feedback on HS-DPCCH. +3. There is no immediate CQI report to be sent on HS-DPCCH. +4. There is no immediate E-DPCCH/E-DPDCH transmission taking place +5. There hasn't been any HS-DPCCH or E-DPCCH/E-DPDCH transmission in the last N slots. (N could be 0) + +I.e. the uplink DPCCH is not transmitted if the DPCCH transmission pattern is not in the active phase and there is no need for HS-DPCCH and/or E-DPCCH/E-DPDCH transmission. + +##### Signalling between the UE and the Node B + +The Node B to UE signalling is not necessarily required, but e.g. for purposes of controlling the CQI reporting or the timing when the UE may initiate the uplink E-DCH transmission, the Node B could use e.g. techniques described in chapters 4.3.1 and 4.4.1. As in Release 6, The E-AGCH and E-RGCH signalling can be used to control the UE's ability to transmit E-DCH. + +The UE to Node B signalling is not necessarily required, but e.g. if the UE is allowed to send E-DCH TTIs whenever it likes, the presence of a DPCCH or a DPCCH preamble can be seen as an implicit signal indicating that an E-DCH transmission is taking place. + +### 4.2.2 Analysis of the concept + +#### 4.2.2.1 Power control stability + +**Table 4.2.2.1-1: Simulation parameters** + +| Parameter | Value | Comment | +|--------------------|-----------------------------------------------------|-------------------------------------------------------------------------------| +| Channel model | Pedestrian A, 3 km/h
Vehicular A, 30 km/h | | +| Data rates | 160 kbps (2ms TTI, SF8)
320 kbps (2 ms TTI, SF4) | 1 VoIP packet every 20ms
2 VoIP packets every 40 ms | +| E-DPDCH/DPCCH | 8 dB | $A_{ed} = 38/15$ | +| E-DPCCH/DPCCH | 0dB | $A_{ec} = 15/15$ | +| Power Control | ON (error: 4%) | 1 dB step size | +| Channel Estimation | Ideal / realistic | Ideal channel estimation used in order to isolate the impact to power control | +| Rx Antennas | 2 | | +| Eb/N0 dB | E-DPxCH+DPCCH | Average over all antennas | +| HARQ | Off / on | When HARQ on, average number of transmissions $\sim 2.2$ | +| Traffic model | VoIP with 100% voice activity | 320 bits every 20 ms | + +##### HARQ off, Ideal channel estimation + +![Figure 4.2.2.1-1: BLER vs. Ec/No for different preamble lengths. Vehicular A, 30 km/h. The figure contains two line graphs. The left graph is for '2ms TTI every 20ms, 160kbps service' and the right graph is for '2ms every 40ms, 320kbps service'. Both graphs plot E-DPDCH BLER (log scale, 10^-4 to 10^0) against Ec/No per antenna, E-DPCCH + E-DPDCH + DPCCH (linear scale, -30 to -16 dB). Seven curves are shown: Continuous DPCCH (black), Preamble 0 slots (green), Preamble 1 slot (yellow), Preamble 2 slots (cyan), Preamble 3 slots (magenta), Preamble 4 slots (red), and Preamble 5 slots (blue). In both cases, the BLER decreases as Ec/No increases. The 'Continuous DPCCH' curve shows the highest BLER, while the 'Preamble 4 slots' and 'Preamble 5 slots' curves show the lowest BLER, indicating better performance with longer preambles.](7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg) + +Figure 4.2.2.1-1: BLER vs. Ec/No for different preamble lengths. Vehicular A, 30 km/h. The figure contains two line graphs. The left graph is for '2ms TTI every 20ms, 160kbps service' and the right graph is for '2ms every 40ms, 320kbps service'. Both graphs plot E-DPDCH BLER (log scale, 10^-4 to 10^0) against Ec/No per antenna, E-DPCCH + E-DPDCH + DPCCH (linear scale, -30 to -16 dB). Seven curves are shown: Continuous DPCCH (black), Preamble 0 slots (green), Preamble 1 slot (yellow), Preamble 2 slots (cyan), Preamble 3 slots (magenta), Preamble 4 slots (red), and Preamble 5 slots (blue). In both cases, the BLER decreases as Ec/No increases. The 'Continuous DPCCH' curve shows the highest BLER, while the 'Preamble 4 slots' and 'Preamble 5 slots' curves show the lowest BLER, indicating better performance with longer preambles. + +**Figure 4.2.2.1-1: BLER vs. Ec/No for different preamble lengths. Vehicular A, 30 km/h** + +Error: + +37 + +Error: Reference source not + +![Figure 4.2.2.1-2: BLER vs. Ec/No for different preamble lengths. Pedestrian A, 3 km/h. Two line graphs showing BLER performance for continuous DPCCH and various preamble lengths (0, 1, 2, 3, 4 slots) under two service conditions: 2ms every 20ms, 160kbit/s service, PA3 (left) and 2ms every 40ms, 320kbit/s service, PA3 (right).](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +The figure contains two line graphs. The left graph is for '2ms every 20ms, 160kbit/s service, PA3' and the right graph is for '2ms every 40ms, 320kbit/s service, PA3'. Both plots show E-DPCH BLER on a logarithmic y-axis (from 10-3 to 100) against Ec/No per antenna on the x-axis. The x-axis for the left plot ranges from -28 to -14, and for the right plot from -30 to -12. Each plot contains seven curves: Continuous DPCCH (black line with circles), Preamble 0 slots (green line with circles), Preamble 1 slot (yellow line with circles), Preamble 2 slots (cyan line with circles), Preamble 3 slots (magenta line with circles), and Preamble 4 slots (red line with circles). In both cases, the BLER decreases as Ec/No increases. The continuous DPCCH curve shows the best performance (lowest BLER), while the preamble curves show progressively worse performance as the preamble length increases. + +Figure 4.2.2.1-2: BLER vs. Ec/No for different preamble lengths. Pedestrian A, 3 km/h. Two line graphs showing BLER performance for continuous DPCCH and various preamble lengths (0, 1, 2, 3, 4 slots) under two service conditions: 2ms every 20ms, 160kbit/s service, PA3 (left) and 2ms every 40ms, 320kbit/s service, PA3 (right). + +Figure 4.2.2.1-2: BLER vs. Ec/No for different preamble lengths. Pedestrian A, 3 km/h + +![Figure 4.2.2.1-3: Average SIR error for different preamble lengths and for continuous DPCCH for one E-DCH transmitted every 20 and every 40 ms. A bar chart showing SIR error [dB] for preamble lengths 0, 1, 2, 3, 4, and Continuous DPCCH across four scenarios: PedA3 2ms/20ms, PedA3 2ms/40ms, VehA30 2ms/20ms, and VehA30 2ms/40ms.](fd38170a3981416226ab91f7437ba821_img.jpg) + +The figure is a bar chart showing the average SIR error [dB] for different preamble lengths (0, 1, 2, 3, 4, and Continuous DPCCH). The y-axis represents the SIR error [dB] from 0 to 1.6. The x-axis represents the preamble length [slots]. For each preamble length, there are four bars representing different scenarios: PedA3 2ms/20ms (blue), PedA3 2ms/40ms (dark red), VehA30 2ms/20ms (yellow), and VehA30 2ms/40ms (light blue). The SIR error generally decreases as the preamble length increases from 0 to 4 slots, and is lowest for the continuous DPCCH case. The PedA3 2ms/40ms scenario consistently shows the highest SIR error across all preamble lengths. + +| Preamble length [slots] | PedA3 2ms/20ms [dB] | PedA3 2ms/40ms [dB] | VehA30 2ms/20ms [dB] | VehA30 2ms/40ms [dB] | +|-------------------------|---------------------|---------------------|----------------------|----------------------| +| 0 | 0.9 | 1.45 | 1.0 | 0.98 | +| 1 | 0.68 | 1.1 | 0.82 | 0.8 | +| 2 | 0.58 | 0.88 | 0.72 | 0.7 | +| 3 | 0.52 | 0.72 | 0.68 | 0.68 | +| 4 | 0.5 | 0.62 | 0.65 | 0.62 | +| Cont. | 0.48 | 0.48 | 0.62 | 0.62 | + +Figure 4.2.2.1-3: Average SIR error for different preamble lengths and for continuous DPCCH for one E-DCH transmitted every 20 and every 40 ms. A bar chart showing SIR error [dB] for preamble lengths 0, 1, 2, 3, 4, and Continuous DPCCH across four scenarios: PedA3 2ms/20ms, PedA3 2ms/40ms, VehA30 2ms/20ms, and VehA30 2ms/40ms. + +Figure 4.2.2.1-3: Average SIR error for different preamble lengths and for continuous DPCCH for one E-DCH transmitted every 20 and every 40 ms. + +The SIR error in figure 4.2.2.1-3 was defined as $SIR_{error} = |SIR_{target} - SIR_{received}|$ and calculated over those slots where E-DPCH/E-DPDCH were transmitted. + +##### **HARQ off, Realistic channel estimation** + +![Two line graphs showing the CDF of SIR error for the 1st E-DCH slot. The left graph is for PedA3 channel and the right is for VehA30 channel. Both plots compare Continuous DPCCH, 0-slot preamble, 2-slot preamble, and 4-slot preamble. The x-axis is SIR error (dB) and the y-axis is CDF(SIR error).](efbdff107f5a5aade487cf4ea0eae150_img.jpg) + +Figure 4.2.2.1-4 displays two plots showing the Cumulative Distribution Function (CDF) of the SIR error for the 1st E-DCH slot after the gap. The plots are for a 2msTTI every 20 ms, 160kbps service, FIR CHE, PedA3 (left) and VehA30 (right) channel models. The x-axis represents the SIR error (dB) and the y-axis represents the CDF(SIR error). The legend indicates four cases: Continuous DPCCH (black line), 0-slot preamble (red line), 2-slot preamble (green line), and 4-slot preamble (blue line). In both plots, the CDF curves for the different preamble lengths are very close to each other, showing similar performance for the 1st slot. + +Two line graphs showing the CDF of SIR error for the 1st E-DCH slot. The left graph is for PedA3 channel and the right is for VehA30 channel. Both plots compare Continuous DPCCH, 0-slot preamble, 2-slot preamble, and 4-slot preamble. The x-axis is SIR error (dB) and the y-axis is CDF(SIR error). + +**Figure 4.2.2.1-4: SIR error of the 1st E-DCH slot after the gap for different preamble lengths and for continuous DPCCH for one E-DCH TTI transmitted every 20 ms.** + +![Two line graphs showing the CDF of SIR error over all E-DCH slots. The left graph is for PedA3 channel and the right is for VehA30 channel. Both plots compare Continuous DPCCH, 0-slot preamble, 2-slot preamble, and 4-slot preamble. The x-axis is SIR error (dB) and the y-axis is CDF(SIR error).](46b141b0e4f1e0bf48a036fc6dfc7d33_img.jpg) + +Figure 4.2.2.1-5 displays two plots showing the Cumulative Distribution Function (CDF) of the SIR error over all E-DCH slots. The plots are for a 2msTTI every 20 ms, 160kbps service, FIR CHE, PedA3 (left) and VehA30 (right) channel models. The x-axis represents the SIR error (dB) and the y-axis represents the CDF(SIR error). The legend indicates four cases: Continuous DPCCH (black line), 0-slot preamble (red line), 2-slot preamble (green line), and 4-slot preamble (blue line). In both plots, the CDF curves for the different preamble lengths are very close to each other, showing similar performance across all slots. + +Two line graphs showing the CDF of SIR error over all E-DCH slots. The left graph is for PedA3 channel and the right is for VehA30 channel. Both plots compare Continuous DPCCH, 0-slot preamble, 2-slot preamble, and 4-slot preamble. The x-axis is SIR error (dB) and the y-axis is CDF(SIR error). + +**Figure 4.2.2.1-5: SIR error over all E-DCH slots for different preamble lengths and for continuous DPCCH for one E-DCH TTI transmitted every 20 ms.** + +##### HARQ on, Realistic channel estimation + +![Figure 4.2.2.1-6: Two line graphs showing the CDF of SIR error (dB) for the 1st E-DCH slot after the gap. The left graph is for PedA3 channel and the right graph is for VehA30 channel. Both graphs compare Continuous DPCCH (black line) with 0-slot (red), 2-slot (green), and 4-slot (blue) preambles. The x-axis ranges from -8 to 8 dB, and the y-axis ranges from 0 to 1. The curves are very close to each other, indicating similar performance for all preamble lengths in this scenario.](a72d02d4e6305689a79b46d36739cd51_img.jpg) + +Figure 4.2.2.1-6: Two line graphs showing the CDF of SIR error (dB) for the 1st E-DCH slot after the gap. The left graph is for PedA3 channel and the right graph is for VehA30 channel. Both graphs compare Continuous DPCCH (black line) with 0-slot (red), 2-slot (green), and 4-slot (blue) preambles. The x-axis ranges from -8 to 8 dB, and the y-axis ranges from 0 to 1. The curves are very close to each other, indicating similar performance for all preamble lengths in this scenario. + +**Figure 4.2.2.1-6: SIR error of the 1st E-DCH slot after the gap for different preamble lengths and for continuous DPCCH for one E-DCH TTI transmitted every 20 ms with retransmissions** + +![Figure 4.2.2.1-7: Two line graphs showing the CDF of SIR error (dB) over all E-DCH slots. The left graph is for PedA3 channel and the right graph is for VehA30 channel. Both graphs compare Continuous DPCCH (black line) with 0-slot (red), 2-slot (green), and 4-slot (blue) preambles. The x-axis ranges from -8 to 8 dB, and the y-axis ranges from 0 to 1. In the VehA30 graph, the 4-slot preamble (blue) shows significantly lower SIR error (better performance) compared to the other cases across most of the CDF range.](e51925aa86bb1cd1ea891dbb493caa4f_img.jpg) + +Figure 4.2.2.1-7: Two line graphs showing the CDF of SIR error (dB) over all E-DCH slots. The left graph is for PedA3 channel and the right graph is for VehA30 channel. Both graphs compare Continuous DPCCH (black line) with 0-slot (red), 2-slot (green), and 4-slot (blue) preambles. The x-axis ranges from -8 to 8 dB, and the y-axis ranges from 0 to 1. In the VehA30 graph, the 4-slot preamble (blue) shows significantly lower SIR error (better performance) compared to the other cases across most of the CDF range. + +**Figure 4.2.2.1-7: SIR error over all E-DCH slots for different preamble lengths and for continuous DPCCH for one E-DCH TTI transmitted every 20 ms with retransmissions** + +#### 4.2.2.2 F-DPCH performance + +Table 4.2.2.2-1 shows the assumptions used for F-DPCH simulations. In case of discontinuous uplink DPCCH transmission (UL DPCCH gating), the TPC commands are not transmitted in all UL slots. Thus, the closed loop power control operation is slower than in case of continuous UL DPCCH. In the simulations, the F-DPCH power has been kept unchanged during UL DPCCH transmission gaps (F-DPCH closed loop PC OFF periods) and updated normally during UL DPCCH transmission activity. The outer loop power control in UE is not run, i.e., SIR target is not updated, during the F-DPCH closed loop PC OFF periods. + +**Table 4.2.2.2-1 Simulation assumptions** + +| Parameter | Explanation/Assumption | +|---------------------------------------------|----------------------------------------------------------| +| Simulation length | 100 000 frames | +| Closed loop Power Control | ON (when ON, also DL Outer Loop PC ON) | +| Uplink TPC error rate | 0% | +| PC step size | 1.0dB | +| PC additional upper limit | max -3.0 dB of total BS power (as specified in TS25.101) | +| Downlink Physical Channels and Power Levels | As specified in TS25.101 | +| Other L1 parameters | As Specified in latest L1 specifications. | +| Channel estimation | Non perfect | + +The results for continuous UL DPCCH with power control, for both DPC\_MODE = 0 and DPC\_MODE = 1, and for UL DPCCH transmission pattern 3 slots UL DPCCH transmission (F-DPCH closed loop PC ON both DPC\_MODE = 0 and DPC\_MODE = 1), 27 slots UL DPCCH DTX (F-DPCH closed loop PC OFF) are shown in Figure 4.2.2.2-1 for pedestrian A 3km/h (G=3dB) and in Figure 4.2.2.2-2 for vehicular A 30km/h (G=3dB). The performance is the worst with fast (slot rate) power control: the slower the closed loop PC, the better the performance. + +![Figure 4.2.2.2-2: F-DPCH performance with different PC modes and discontinuous PC, pedestrian A 3km/h, G=3dB. The graph plots TPC CER (log scale, 1.00E-03 to 1.00E+00) against Average Ec/Ior, dB (-38.00 to -24.00). Four curves are shown: 3 slots PC ON DPC_Mode=0, 27 slots PC OFF (blue diamonds); 3 slots PC ON DPC_Mode=1, 27 slots PC OFF (purple crosses); PC ON, DPC_Mode=0 (yellow triangles); and PC ON, DPC_Mode=1 (pink squares). All curves show a downward trend as Average Ec/Ior increases. The 3 slots PC ON DPC_Mode=0 curve is the lowest, indicating the best performance.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +**Pedestrian A 3km/h, G=3dB** + +Legend: + +- 3 slots PC ON DPC\_Mode=0, 27 slots PC OFF +- 3 slots PC ON DPC\_Mode=1, 27 slots PC OFF +- PC ON, DPC\_Mode=0 +- PC ON, DPC\_Mode=1 + +Y-axis: TPC CER (log scale from 1.00E-03 to 1.00E+00) + +X-axis: Average Ec/Ior, dB (from -38.00 to -24.00) + +Figure 4.2.2.2-2: F-DPCH performance with different PC modes and discontinuous PC, pedestrian A 3km/h, G=3dB. The graph plots TPC CER (log scale, 1.00E-03 to 1.00E+00) against Average Ec/Ior, dB (-38.00 to -24.00). Four curves are shown: 3 slots PC ON DPC\_Mode=0, 27 slots PC OFF (blue diamonds); 3 slots PC ON DPC\_Mode=1, 27 slots PC OFF (purple crosses); PC ON, DPC\_Mode=0 (yellow triangles); and PC ON, DPC\_Mode=1 (pink squares). All curves show a downward trend as Average Ec/Ior increases. The 3 slots PC ON DPC\_Mode=0 curve is the lowest, indicating the best performance. + +**Figure 4.2.2.2-2 F-DPCH performance with different PC modes and discontinuous PC, pedestrian A 3km/h, G=3dB.** + +![Figure 4.2.2.2-3: F-DPCH performance with different PC modes and discontinuous PC, vehicular A 30km/h, G=3dB. The graph plots TPC CER (log scale, 1.00E-03 to 1.00E+00) against Average Ec/Ior, dB (-38.00 to -24.00). Four curves are shown: 3 slots PC ON DPC_Mode=0, 27 slots PC OFF (blue diamonds); 3 slots PC ON DPC_Mode=1, 27 slots PC OFF (purple crosses); PC ON, DPC_Mode=0 (yellow triangles); and PC ON, DPC_Mode=1 (pink squares). All curves show a downward trend as Average Ec/Ior increases. The 3 slots PC ON DPC_Mode=0 curve is the lowest, indicating the best performance.](74448f9178da618d823e5a5dadc56fb5_img.jpg) + +**Vehicular A 30km/h, G=3dB** + +Legend: + +- 3 slots PC ON DPC\_Mode=0, 27 slots PC OFF +- 3 slots PC ON DPC\_Mode=1, 27 slots PC OFF +- PC ON, DPC\_Mode=0 +- PC ON, DPC\_Mode=1 + +Y-axis: TPC CER (log scale from 1.00E-03 to 1.00E+00) + +X-axis: Average Ec/Ior, dB (from -38.00 to -24.00) + +Figure 4.2.2.2-3: F-DPCH performance with different PC modes and discontinuous PC, vehicular A 30km/h, G=3dB. The graph plots TPC CER (log scale, 1.00E-03 to 1.00E+00) against Average Ec/Ior, dB (-38.00 to -24.00). Four curves are shown: 3 slots PC ON DPC\_Mode=0, 27 slots PC OFF (blue diamonds); 3 slots PC ON DPC\_Mode=1, 27 slots PC OFF (purple crosses); PC ON, DPC\_Mode=0 (yellow triangles); and PC ON, DPC\_Mode=1 (pink squares). All curves show a downward trend as Average Ec/Ior increases. The 3 slots PC ON DPC\_Mode=0 curve is the lowest, indicating the best performance. + +**Figure 4.2.2.2-3 F-DPCH performance with different PC modes and discontinuous PC, vehicular A 30km/h, G=3dB.** + +The results with different UL DPCCH transmission patterns (3 slots UL DPCCH transmission & 27 slots UL DPCCH DTX, 3 slots UL DPCCH transmission & 57 slots UL DPCCH DTX, 6 slots UL DPCCH transmission & 24 slots UL DPCCH DTX, 6 slots UL DPCCH transmission & 54 slots UL DPCCH DTX) are shown in Figure 4.2.2.2-3 for pedestrian A 3km/h (G=3dB) and in Figure 4.2.2.2-4 for vehicular A 30km/h (G=3dB), DPC\_MODE=0. There are no significant differences in the F-DPCH performance with the different patterns. The performance with slowest power control (3 slots PC ON & 57 slots PC OFF pattern) is slightly better than with the other patterns and the performance with more power control (6 slots PC ON & 24 slots PC OFF pattern) is slightly worse than with the other patterns. Thus, the performance seems to be the better the slower the power control is (i.e., the lower the number of the power controlled slots compared to the number of not power controlled slots is). + +![Figure 4.2.2.2-4: F-DPCH performance with different discontinuous PC patterns, pedestrian A 3km/h, G=3dB. The graph shows TPC CER on a log scale (1.00E-03 to 1.00E+00) versus Average Ec/Ior, dB (-38.00 to -24.00). Four curves are plotted: 3 slots PC ON, 27 slots PC OFF (blue diamonds); 6 slots PC ON, 24 slots PC OFF (red squares); 3 slots PC ON, 57 slots PC OFF (green plus signs); and 6 slots PC ON, 54 slots PC OFF (blue circles). All curves show a downward trend as Average Ec/Ior increases, with the 3 slots PC ON, 57 slots PC OFF pattern showing the lowest TPC CER at higher Average Ec/Ior values.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +**Pedestrian A 3km/h, G=3dB** + +Legend: + +- 3 slots PC ON, 27 slots PC OFF (blue diamonds) +- 6 slots PC ON, 24 slots PC OFF (red squares) +- 3 slots PC ON, 57 slots PC OFF (green plus signs) +- 6 slots PC ON, 54 slots PC OFF (blue circles) + +Y-axis: TPC CER (log scale, 1.00E-03 to 1.00E+00) + +X-axis: Average Ec/Ior, dB (-38.00 to -24.00) + +Figure 4.2.2.2-4: F-DPCH performance with different discontinuous PC patterns, pedestrian A 3km/h, G=3dB. The graph shows TPC CER on a log scale (1.00E-03 to 1.00E+00) versus Average Ec/Ior, dB (-38.00 to -24.00). Four curves are plotted: 3 slots PC ON, 27 slots PC OFF (blue diamonds); 6 slots PC ON, 24 slots PC OFF (red squares); 3 slots PC ON, 57 slots PC OFF (green plus signs); and 6 slots PC ON, 54 slots PC OFF (blue circles). All curves show a downward trend as Average Ec/Ior increases, with the 3 slots PC ON, 57 slots PC OFF pattern showing the lowest TPC CER at higher Average Ec/Ior values. + +Figure 4.2.2.2-4 F-DPCH performance with different discontinuous PC patterns, pedestrian A 3km/h, G=3dB. + +![Figure 4.2.2.2-5: F-DPCH performance with different discontinuous PC patterns, vehicular A 30km/h, G=3dB. The graph shows TPC CER on a log scale (1.00E-03 to 1.00E+00) versus Average Ec/Ior, dB (-38.00 to -24.00). Four curves are plotted: 3 slots PC ON, 27 slots PC OFF (blue diamonds); 6 slots PC ON, 24 slots PC OFF (red squares); 3 slots PC ON, 57 slots PC OFF (green plus signs); and 6 slots PC ON, 54 slots PC OFF (blue circles). All curves show a downward trend as Average Ec/Ior increases, with the 3 slots PC ON, 57 slots PC OFF pattern showing the lowest TPC CER at higher Average Ec/Ior values.](d49bc18ad8867b97bbb9aa580449a641_img.jpg) + +**Vehicular A 30km/h, G=3dB** + +Legend: + +- 3 slots PC ON, 27 slots PC OFF (blue diamonds) +- 6 slots PC ON, 24 slots PC OFF (red squares) +- 3 slots PC ON, 57 slots PC OFF (green plus signs) +- 6 slots PC ON, 54 slots PC OFF (blue circles) + +Y-axis: TPC CER (log scale, 1.00E-03 to 1.00E+00) + +X-axis: Average Ec/Ior, dB (-38.00 to -24.00) + +Figure 4.2.2.2-5: F-DPCH performance with different discontinuous PC patterns, vehicular A 30km/h, G=3dB. The graph shows TPC CER on a log scale (1.00E-03 to 1.00E+00) versus Average Ec/Ior, dB (-38.00 to -24.00). Four curves are plotted: 3 slots PC ON, 27 slots PC OFF (blue diamonds); 6 slots PC ON, 24 slots PC OFF (red squares); 3 slots PC ON, 57 slots PC OFF (green plus signs); and 6 slots PC ON, 54 slots PC OFF (blue circles). All curves show a downward trend as Average Ec/Ior increases, with the 3 slots PC ON, 57 slots PC OFF pattern showing the lowest TPC CER at higher Average Ec/Ior values. + +Figure 4.2.2.2-5 F-DPCH performance with different discontinuous PC patterns, vehicular A 30km/h, G=3dB. + +It can be concluded from the results, that the F-DPCH performance would not be degraded due to the UL DPCCH gating (relatively low transmit power required for reasonable TPC CERs) and that with discontinuous UL DPCCH transmission (i.e., discontinuous F-DPCH power control) the UL DPCCH transmission (F-DPCH power control ON/OFF) pattern has only minor impact on the performance (the performance seems to be slightly better for patterns with shorter PC ON periods). + +#### 4.2.2.3 Uplink link performance + +**Table 4.2.2.3-1: Simulation parameters** + +| Parameter | Value | Comment | +|--------------------|------------------------------------------------------|---------------------------------------------------------| +| Channel model | Pedestrian A, 3 km/h
Vehicular A, 30 km/h | | +| Data rates | 160 kbps (2ms TTI, SF8)
64 kbps (10 ms TTI, SF16) | 1 VoIP packet every 20 ms
2 VoIP packets every 40 ms | +| E-DPDCH/DPCCH | 8 dB | | +| E-DPCCH/DPCCH | 0dB | | +| Power Control | ON (error: 4%) | 1 dB step size | +| Channel Estimation | Realistic | | +| Rx Antennas | 2 | | +| Eb/N0 dB | E-DPxCH+DPCCH | Average over both antennas | +| HARQ | On | | +| Traffic model | VoIP with 100% voice activity | 320 bits every 20 ms / 640 bits every 40 ms | + +The results below simulate gated DPCCH with 0,1,2,3 and 4 slot preamble and with a continuous (R'6) DPCCH as a reference scenario. + +Simulation results for 10 ms TTI and 64 kbps instantaneous data rate (two new VoIP packets transmitted every 40 ms). + +Simulation results for 2 ms TTI and 160 kbps instantaneous data rate (a new VoIP packets transmitted every 20 ms). + +Y-axis of the figures 4.2.2.3-1 and 4.2.2.3-3 correspond to the HARQ operating point indicating the throughput of an individual packet. Instantaneous data rate / throughput = average # of transmissions per packet. + +![Figure 4.2.2.3-1: E-DCH performance with Gating, 10 ms TTI, 64 kbps instantaneous, 16 kbps average data rate. The figure contains two line graphs. The left graph is for Pedestrian A, 3 km/h channel model, and the right graph is for Vehicular A, 30 km/h channel model. Both graphs plot throughput (kbps) on the Y-axis (0 to 60) against E-DCH Ec/N0 (dB) on the X-axis (-26 to -18). Six curves are shown: Continuous DPCCH (black line with circles), 0-slot preamble (green line with circles), 1-slot preamble (yellow line with circles), 2-slot preamble (cyan line with circles), 3-slot preamble (magenta line with circles), and 4-slot preamble (red line with circles). In both graphs, the 4-slot preamble curve shows the highest throughput, followed by the 3-slot, 2-slot, 1-slot, and 0-slot preambles. The Continuous DPCCH curve shows the lowest throughput. The performance is better in the Pedestrian A channel model than in the Vehicular A channel model.](c301bbb71a13e5fb2800c48e300bafb1_img.jpg) + +Figure 4.2.2.3-1: E-DCH performance with Gating, 10 ms TTI, 64 kbps instantaneous, 16 kbps average data rate. The figure contains two line graphs. The left graph is for Pedestrian A, 3 km/h channel model, and the right graph is for Vehicular A, 30 km/h channel model. Both graphs plot throughput (kbps) on the Y-axis (0 to 60) against E-DCH Ec/N0 (dB) on the X-axis (-26 to -18). Six curves are shown: Continuous DPCCH (black line with circles), 0-slot preamble (green line with circles), 1-slot preamble (yellow line with circles), 2-slot preamble (cyan line with circles), 3-slot preamble (magenta line with circles), and 4-slot preamble (red line with circles). In both graphs, the 4-slot preamble curve shows the highest throughput, followed by the 3-slot, 2-slot, 1-slot, and 0-slot preambles. The Continuous DPCCH curve shows the lowest throughput. The performance is better in the Pedestrian A channel model than in the Vehicular A channel model. + +**Figure 4.2.2.3-1: E-DCH performance with Gating, 10 ms TTI, 64 kbps instantaneous, 16 kbps average data rate** + +Y-axis of the figures above correspond to the HARQ operating point indicating the throughput of an individual packet. Instantaneous data rate / throughput = average # of transmissions per packet. + +![Figure 4.2.2.3-2: E-DPCCH performance with gating, 10 ms TTI transmitted every 40 ms, HARQ on. The graph shows E-DPCCH BLER vs E-DCH Ec/No for various preamble configurations.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +10ms TTI every 40ms, 1 EDPCCCH, FIR CHE, VA30 + +The graph plots E-DPCCH BLER on a logarithmic Y-axis from $10^{-5}$ to $10^0$ against E-DCH Ec/No on a linear X-axis from -26 to -14. Six data series are shown: Continuous DPCCH (black circles), 0-slot preamble (green circles), 1-slot preamble (yellow circles), 2-slot preamble (cyan circles), 3-slot preamble (magenta circles), and 4-slot preamble (red circles). The Continuous DPCCH curve is shifted to the right, indicating higher BLER for the same Ec/No compared to gated configurations. + +Figure 4.2.2.3-2: E-DPCCH performance with gating, 10 ms TTI transmitted every 40 ms, HARQ on. The graph shows E-DPCCH BLER vs E-DCH Ec/No for various preamble configurations. + +**Figure 4.2.2.3-2: E-DPCCH performance with gating, 10 ms TTI transmitted every 40 ms, HARQ on.** + +![Figure 4.2.2.3-3: E-DCH performance with Gating, 2 ms TTI, 160 kbps instantaneous, 16 kbps average data rate. Two graphs are shown: one for PA3 and one for VA30.](198d076da025c516aec8122a6ab7db20_img.jpg) + +Left graph: 2ms TTI every 20ms, 160kbit/s service, FIR CHE, PA3. Right graph: 2ms TTI every 20ms, 160kbit/s service, FIR CHE, VA30. + +Both graphs plot throughput (kbps) on a linear Y-axis from 0 to 160 against total EDCH Ec/No per antenna (dB) on a linear X-axis from -27 to -18. The legends match Figure 4.2.2.3-2. In both channel models (PA3 and VA30), the gated preamble configurations reach maximum throughput at lower Ec/No values than the Continuous DPCCH configuration. + +Figure 4.2.2.3-3: E-DCH performance with Gating, 2 ms TTI, 160 kbps instantaneous, 16 kbps average data rate. Two graphs are shown: one for PA3 and one for VA30. + +**Figure 4.2.2.3-3: E-DCH performance with Gating, 2 ms TTI, 160 kbps instantaneous, 16 kbps average data rate** + +Y-axis of the figures above correspond to the HARQ operating point indicating the throughput of an individual packet. Instantaneous data rate / throughput = average # of transmissions per packet. + +![Figure 4.2.2.3-4: E-DPCCH performance with gating, 2 ms TTI transmitted every 20 ms, HARQ on. The graph shows E-DPCCH BLER (Y-axis, log scale from 10^-4 to 10^0) versus E-DCH Ec/No (X-axis, linear scale from -23 to -14). The legend indicates: Continuous DPCCH (black line with circles), 0-slot preamble (green line with circles), 1-slot preamble (yellow line with circles), 2-slot preamble (cyan line with circles), 3-slot preamble (magenta line with circles), and 4-slot preamble (red line with circles). The Continuous DPCCH curve is the highest, followed by 0-slot, 1-slot, 2-slot, 3-slot, and 4-slot preamble, which is the lowest. The title of the graph is '2ms every 20ms, E-DPCCH, FIR CHE, VA30'.](0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg) + +Figure 4.2.2.3-4: E-DPCCH performance with gating, 2 ms TTI transmitted every 20 ms, HARQ on. The graph shows E-DPCCH BLER (Y-axis, log scale from 10^-4 to 10^0) versus E-DCH Ec/No (X-axis, linear scale from -23 to -14). The legend indicates: Continuous DPCCH (black line with circles), 0-slot preamble (green line with circles), 1-slot preamble (yellow line with circles), 2-slot preamble (cyan line with circles), 3-slot preamble (magenta line with circles), and 4-slot preamble (red line with circles). The Continuous DPCCH curve is the highest, followed by 0-slot, 1-slot, 2-slot, 3-slot, and 4-slot preamble, which is the lowest. The title of the graph is '2ms every 20ms, E-DPCCH, FIR CHE, VA30'. + +Figure 4.2.2.3-4: E-DPCCH performance with gating, 2 ms TTI transmitted every 20 ms, HARQ on. + +##### 4.2.2.3.1 Additional link level results + +This section goes over the link level impact of gating the DPCCH in the UL of UTRA over active and inactive data transfers. Results in this section further elaborate on the characterization of link level impact of DPCCH gating by assessing the demodulation performance with HARQ enabled, realistic channel estimation and with time-tracking (TTL) as well as frequency-tracking loops (FTL). + +Incorporating the TTL and FTL into the simulations gives a clearer indication on whether or not synchronization issues may appear from the gating of the UL DPCCH. + +###### 4.2.2.3.1.1 Simulation assumptions + +- **Channel estimation:** Realistic. Non-causal FIR filter over 4 slots: same channel estimation used for non-gated DPCCH simulations as well as DPCCH gated simulations. +- **Time Tracking:** 1st order loop. Same loop gain for DPCCH non-gated simulations as well as DPCCH gated simulations. The time tracking loop in the simulations for inactive data periods takes into consideration the code Doppler to assess any synchronization issue for long gating periods. +- **Frequency Tracking:** 1st order loop. Same loop gain for DPCCH non-gated simulations as well as DPCCH gated simulations. The initial frequency error is set to 200 Hz. +- **UL Power Control:** UE transmit power adjusted just over the non-gated periods, over the gated periods the transmit power is on hold. + - Outer loop: + - Enabled with 1% residual BLER target for simulations over active data periods. + - Enabled and based on a target Pilot symbol error rate over inactive data periods. +- **Channel models:** AWGN (for simulation cross-check), PA3, VA120. +- **Transmission block size (data rate):** 296 bits block size i.e., 148 kbps over single transmission (49.33 kbps after 3 transmissions). +- **E-DCH Beta factors:** from 0 to 20 dB + +- **Data activity:** 100% over one HARQ process (when a packet is positively acknowledged, a new packet is transmitted). +- **DPCCH slot format:** 0, (6 pilot symbols out of 10 symbols) +- **Gating patterns:** + - 0% gating: continuous DPCCH transmission as illustrated by Figure 1. + - 50% gating: DPCCH transmitted over 2 HARQ processes every 8. Transmitted with 2-slot preamble and 1-slot postamble as illustrated by Figure 2. + - 75% gating: DPCCH transmitted over 1 HARQ process every 8. Transmitted with 2-slot preamble and 1-slot postamble as illustrated by Figure 3. + - 87.5% gating: DPCCH transmitted over 1 HARQ process every 16. Transmitted with 2-slot preamble and 1-slot postamble. + +![Figure 4.2.2.3.1.1-1: Baseline reference with continuous DPCCH transmission. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent DPCCH slots, which are continuous throughout the sequence.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +2 ms subframe E-DPDCH +One HARQ process + +One DPCCH slot + +7 (2 ms) subframes = 21 slots + +Figure 4.2.2.3.1.1-1: Baseline reference with continuous DPCCH transmission. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent DPCCH slots, which are continuous throughout the sequence. + +Figure 4.2.2.3.1.1-1: Baseline reference with continuous DPCCH transmission. + +![Figure 4.2.2.3.1.1-2: 50% gated DPCCH. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent transmitted DPCCH slots, and white blocks represent gated DPCCH slots. The pattern shows 2 subframes of continuous transmission followed by 2 subframes of gating.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +2 ms subframe E-DPDCH +One HARQ process + +One transmitted DPCCH slot + +One gated DPCCH slot + +7 (2 ms) subframes = 21 slots + +2 subframes + +Figure 4.2.2.3.1.1-2: 50% gated DPCCH. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent transmitted DPCCH slots, and white blocks represent gated DPCCH slots. The pattern shows 2 subframes of continuous transmission followed by 2 subframes of gating. + +Figure 4.2.2.3.1.1-2: 50% gated DPCCH. + +![Figure 4.2.2.3.1.1-3: 75% gated DPCCH. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent transmitted DPCCH slots, and white blocks represent gated DPCCH slots. The pattern shows 6 subframes of continuous transmission followed by 1 subframe of gating.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +2 ms subframe E-DPDCH +One HARQ process + +One transmitted DPCCH slot + +One gated DPCCH slot + +7 (2 ms) subframes = 21 slots + +6 subframes + +Figure 4.2.2.3.1.1-3: 75% gated DPCCH. The diagram shows a sequence of 21 slots (7 subframes of 3 slots each). A red block representing a 2 ms subframe E-DPDCH (One HARQ process) is shown at the beginning and end of the sequence. Green blocks represent transmitted DPCCH slots, and white blocks represent gated DPCCH slots. The pattern shows 6 subframes of continuous transmission followed by 1 subframe of gating. + +Figure 4.2.2.3.1.1-3: 75% gated DPCCH. + +- Rx antennas: 2. +- Max number of transmissions: 3. + +###### 4.2.2.3.1.2 Simulation results + +###### 4.2.2.3.1.2.1 Simulations results over data active periods + +Figures 4.2.2.3.1.2.1-1 to 4.2.2.3.1.2.1-6 present results for the scenarios considered. The figures show: + +- Combined Eb/Nt (per antenna) - figures at the left. DPCCH overhead taken into account just when E-DCH is active. +- Effective combined Eb/Nt (per antenna) - figures at the right. DPCCH overhead taken into account regardless E-DCH is active or not. + +To isolate the power control impact, results without TTL and FTL are shown for all channels. + +![Figure 4.2.2.3.1.2.1-1: Two line graphs for an AWGN channel with a target rate of 49.33 kbps. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' vs 'E-DPDCH/DPCCH (dB)'. The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' vs 'Effective E-DPDCH/DPCCH (dB)'. Both graphs compare three gating patterns: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with 'x' markers). In both cases, the curves show a U-shape, indicating an optimal power level. The 'Effective' graph on the right shows higher Eb/Nt values than the 'Combined' graph on the left.](0867e5b136ab5cc8674c490d96f196e2_img.jpg) + +Figure 4.2.2.3.1.2.1-1: Two line graphs for an AWGN channel with a target rate of 49.33 kbps. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' vs 'E-DPDCH/DPCCH (dB)'. The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' vs 'Effective E-DPDCH/DPCCH (dB)'. Both graphs compare three gating patterns: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with 'x' markers). In both cases, the curves show a U-shape, indicating an optimal power level. The 'Effective' graph on the right shows higher Eb/Nt values than the 'Combined' graph on the left. + +**Figure 4.2.2.3.1.2.1-1: AWGN channel, different gating patterns, combined Eb/Nt per antenna with TTL and FTL, target rate 49.3kbps.** + +![Figure 4.2.2.3.1.2.1-2: Two line graphs for an AWGN channel with a target rate of 49.33 kbps, without TTL and FTL. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' vs 'E-DPDCH/DPCCH (dB)'. The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' vs 'Effective E-DPDCH/DPCCH (dB)'. Both graphs compare the same three gating patterns: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with 'x' markers). The curves show a U-shape. The 'Effective' graph on the right shows higher Eb/Nt values than the 'Combined' graph on the left.](174f912c9b31990c1b57e64f629e75ac_img.jpg) + +Figure 4.2.2.3.1.2.1-2: Two line graphs for an AWGN channel with a target rate of 49.33 kbps, without TTL and FTL. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' vs 'E-DPDCH/DPCCH (dB)'. The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' vs 'Effective E-DPDCH/DPCCH (dB)'. Both graphs compare the same three gating patterns: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with 'x' markers). The curves show a U-shape. The 'Effective' graph on the right shows higher Eb/Nt values than the 'Combined' graph on the left. + +**Figure 4.2.2.3.1.2.1-2: AWGN channel, different gating patterns, combined Eb/Nt per antenna without TTL and FTL, target rate 49.3kbps.** + +Error: + +48 + +Error: Reference source not + +![Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Combined Eb/Nt(dB) (per antenna) vs E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB E-DPDCH/DPCCH. The Baseline curve is the lowest, followed by Gate 50%, and then Gate 75%.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +Target Rate=49.33 kbps - Channel Model - PA3 + +Combined Eb/Nt(dB) (per antenna) + +E-DPDCH/DPCCH (dB) + +Legend: Gate 75%, Baseline, Gate 50% + +Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Combined Eb/Nt(dB) (per antenna) vs E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB E-DPDCH/DPCCH. The Baseline curve is the lowest, followed by Gate 50%, and then Gate 75%. + +![Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Effective Combined Eb/Nt(dB) (per antenna) vs Effective E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Effective Eb/Nt occurring around 10 dB Effective E-DPDCH/DPCCH. The Gate 50% curve is the lowest, followed by Baseline, and then Gate 75%.](5b29df6b4f2a461b8c039fe47053fa65_img.jpg) + +Target Rate=49.33 kbps - Channel Model - PA3 + +Effective Combined Eb/Nt(dB) (per antenna) + +Effective E-DPDCH/DPCCH (dB) + +Legend: Gate 75%, Baseline, Gate 50% + +Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Effective Combined Eb/Nt(dB) (per antenna) vs Effective E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Effective Eb/Nt occurring around 10 dB Effective E-DPDCH/DPCCH. The Gate 50% curve is the lowest, followed by Baseline, and then Gate 75%. + +Figure 4.2.2.3.1.2.1-3: PA3 channel, different gating patterns, combined Eb/Nt per antenna with TTL and FTL, target rate 49.3kbps. + +![Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Combined Eb/Nt(dB) (per antenna) vs E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB E-DPDCH/DPCCH. The Baseline curve is the lowest, followed by Gate 50%, and then Gate 75%.](6a842e59ecf31b0d6f6721ac4e76f160_img.jpg) + +Target Rate=49.33 kbps - Channel Model - PA3 + +Combined Eb/Nt(dB) (per antenna) + +E-DPDCH/DPCCH (dB) + +Legend: Gate 75%, Baseline, Gate 50% + +Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Combined Eb/Nt(dB) (per antenna) vs E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB E-DPDCH/DPCCH. The Baseline curve is the lowest, followed by Gate 50%, and then Gate 75%. + +![Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Effective Combined Eb/Nt(dB) (per antenna) vs Effective E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Effective Eb/Nt occurring around 10 dB Effective E-DPDCH/DPCCH. The Gate 50% curve is the lowest, followed by Baseline, and then Gate 75%.](f9625fa3465b009051f85d91cfa1da7e_img.jpg) + +Target Rate=49.33 kbps - Channel Model - PA3 + +Effective Combined Eb/Nt(dB) (per antenna) + +Effective E-DPDCH/DPCCH (dB) + +Legend: Gate 75%, Baseline, Gate 50% + +Line graph titled 'Target Rate=49.33 kbps - Channel Model - PA3' showing Effective Combined Eb/Nt(dB) (per antenna) vs Effective E-DPDCH/DPCCH (dB). Three curves are shown: Gate 75% (red line with '+' markers), Baseline (blue line with 'o' markers), and Gate 50% (green line with triangle markers). The curves show a U-shaped trend, with the minimum Effective Eb/Nt occurring around 10 dB Effective E-DPDCH/DPCCH. The Gate 50% curve is the lowest, followed by Baseline, and then Gate 75%. + +Figure 4.2.2.3.1.2.1-4: PA3 channel, different gating patterns, combined Eb/Nt per antenna without TTL and FTL, target rate 49.3kbps. + +![Figure 4.2.2.3.1.2.1-5: VA120 channel, different gating patterns, combined Eb/Nt per antenna with TTL and FTL, target rate 49.3kbps. The figure contains two line graphs. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 2.5 to 7.5) against 'E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 3 to 11) against 'Effective E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). Both graphs compare three gating patterns: Gate 75% (red line with stars), Baseline (blue line with circles), and Gate 50% (green line with triangles). In both cases, the curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB. The Gate 50% pattern consistently achieves the lowest Eb/Nt across the range, followed by Gate 75%, and then the Baseline pattern.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +Figure 4.2.2.3.1.2.1-5: VA120 channel, different gating patterns, combined Eb/Nt per antenna with TTL and FTL, target rate 49.3kbps. The figure contains two line graphs. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 2.5 to 7.5) against 'E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 3 to 11) against 'Effective E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). Both graphs compare three gating patterns: Gate 75% (red line with stars), Baseline (blue line with circles), and Gate 50% (green line with triangles). In both cases, the curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB. The Gate 50% pattern consistently achieves the lowest Eb/Nt across the range, followed by Gate 75%, and then the Baseline pattern. + +Figure 4.2.2.3.1.2.1-5: VA120 channel, different gating patterns, combined Eb/Nt per antenna with TTL and FTL, target rate 49.3kbps. + +![Figure 4.2.2.3.1.2.1-6: VA120 channel, different gating patterns, combined Eb/Nt per antenna without TTL and FTL, target rate 49.3kbps. The figure contains two line graphs. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 2.5 to 7) against 'E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 3 to 11) against 'Effective E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). Both graphs compare three gating patterns: Gate 75% (red line with stars), Baseline (blue line with circles), and Gate 50% (green line with triangles). In both cases, the curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB. The Gate 50% pattern consistently achieves the lowest Eb/Nt across the range, followed by Gate 75%, and then the Baseline pattern.](73e5c1369b67ddccf657e54d0434cc2b_img.jpg) + +Figure 4.2.2.3.1.2.1-6: VA120 channel, different gating patterns, combined Eb/Nt per antenna without TTL and FTL, target rate 49.3kbps. The figure contains two line graphs. The left graph shows 'Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 2.5 to 7) against 'E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). The right graph shows 'Effective Combined Eb/Nt(dB) (per antenna)' on the y-axis (ranging from 3 to 11) against 'Effective E-DPDCH/DPCCH (dB)' on the x-axis (ranging from 0 to 20). Both graphs compare three gating patterns: Gate 75% (red line with stars), Baseline (blue line with circles), and Gate 50% (green line with triangles). In both cases, the curves show a U-shaped trend, with the minimum Eb/Nt occurring around 10 dB. The Gate 50% pattern consistently achieves the lowest Eb/Nt across the range, followed by Gate 75%, and then the Baseline pattern. + +Figure 4.2.2.3.1.2.1-6: VA120 channel, different gating patterns, combined Eb/Nt per antenna without TTL and FTL, target rate 49.3kbps. + +Tables 4.2.2.3.1.2.1-1 to 4.2.2.3.1.2.1-3 summarize the results with FTL and TTL enabled. + +Table 4.2.2.3.1.2.1-1: AWGN with TTL FTL target rate 49.3kbps + +| | No Gating | Gating 50% | Gating 75% | +|------------------------------------------------------|------------------|------------------|------------------| +| MinEbnT @ opt T/P /
Effective MinEbnT @ opt T/P | 0.26
1.65 | 0.47
1.27 | 1.04
1.36 | +| MinEcpnT @ opt T/P /
Effective MinEcpnT @ opt T/P | -24.73
-27.31 | -24.49
-25.73 | -22.85
-24.12 | +| Optimal T/P /
Effective Optimal T/P | 10
14 | 10
12 | 9
11 | +| Effective Ec/Nt | -12 | -12.79 | -12.54 | + +**Table 4.2.2.3.1.2.1-2: PA3 with FTL TTL target rate 49.3kbps** + +| | No Gating | Gating 50% | Gating 75% | +|--------------------------------------------------------------------|------------------|---------------|---------------| +| MinEbnT @ opt T/P /
Effective MinEbnT @ opt T/P | 0.33
1.73 | 0.64
1.50 | 1.80
2.42 | +| MinEcpnT @ opt T/P /
Effective MinEcpnT @ opt T/P | -23.92
-27.02 | -23.83
-25 | -21
-21.66 | +| Optimal T/P /
Effective Optimal T/P | 9
14 | 10
12 | 9
10 | +| Effective Ec/Nt | -11.68 | -12.13 | -10.69 | + +**Table 4.2.2.3.1.2.1-3: VA120 with TTL FTL target rate 49.3kbps** + +| | No Gating | Gating 50% | Gating 75% | +|-------------------------------------------------------------------|------------------|------------------|------------------| +| MinEbnT @ opt T/P /
Effective MinEbnT @opt T/P | 2.73
4.80 | 3.05
4.20 | 3.18
3.64 | +| MinEcpnT @ opt T/P /
Effective MinEcpnT @opt T/P | -19.89
-22.30 | -18.79
-21.35 | -19.36
-20.18 | +| Optimal T/P /
Effective Optimal T/P | 8
12 | 7
11 | 8
9 | +| Effective Ec/Nt | -8.10 | -8.88 | -9.78 | + +Table 4.2.2.3.1.2.1-4 presents the gains of the two considered gating schemes (50% and 75%) with respect to no-gating. For the transport block size of the evaluation i.e., 296 bits, the 50% gating provides gains between 0.45dB and 0.79dB. The gains range much more for the 75% gating where we go from a 1.68dB gain for the VA120 case to an actual loss of 0.99dB for the PA3 case. + +**Table 4.2.2.3.1.2.1-4: Summary of Results for target rate 16kbps** + +| | 50% gating gain over
0% gating | 75% gating gain over
0% gating | +|-------|-----------------------------------|-----------------------------------| +| AWGN | 0.79 | 0.54 | +| PA3 | 0.45 | -0.99 | +| VA120 | 0.78 | 1.68 | + +In general, the gains provided by the 50% gating are higher than 75% for AWGN and PA3 channel models. + +These gains at the link level directly yield a reduction in the contribution to the interference rise and therefore help into the overall system capacity improvement. + +###### 4.2.2.3.1.2.2 Simulations results over data inactive periods + +For the simulations over inactive data periods and due to lack of data blocks, a power control loop based on Pilot symbol error rate is used. Tables 4.2.2.3.1.2.2-1 to 4.2.2.3.1.2.2- 4 show the results of calibrating this outer loop power control method with the regular outer loop power control method based on E-DPDCH BLER. The verification is performed for a number of channel models and T/P operating points. + +**Table 4.2.2.3.1.2.2-1: PedA3 channel model without TTL FTL, Max 3ReTX target rate 49.3 kbps, T/P=9** + +| | Eb/Nt | Pilot Ec/Nt | E-DPDCH BLER | Pilot SER | +|----------------------------|-------|-------------|--------------|-----------| +| BLER based outer loop | 0.28 | -23.86 | 0.0104 | 0.0588 | +| Pilot SER based outer loop | 0.22 | -24.08 | 0.0113 | 0.0613 | + +**Table 4.2.2.3.1.2.2-2: PedA3 channel model without TTL FTL, Max 4ReTX target rate 16 kbps, T/P=7** + +| | Eb/Nt | Pilot Ec/Nt | E-DPDCH BLER | Pilot SER | +|----------------------------|-------|-------------|--------------|-----------| +| BLER based outer loop | 1.18 | -25.91 | 0.01030 | 0.090754 | +| Pilot SER based outer loop | 1.16 | -25.98 | 0.01080 | 0.092509 | + +**Table 4.2.2.3.1.2.2-3: Va120 channel model without TTL FTL, Max 4ReTX target rate 16 kbps, T/P=7** + +| | Eb/Nt | Pilot Ec/Nt | E-DPDCH BLER | Pilot SER | +|----------------------------|-------|-------------|--------------|-----------| +| BLER based outer loop | 3.82 | -22.48 | 0.01040 | 0.01275 | +| Pilot SER based outer loop | 3.83 | -22.52 | 0.00801 | 0.01277 | + +**Table 4.2.2.3.1.2.2-4: Va120 channel model without TTL FTL, Max 3ReTX target rate 49.3 kbps, T/P=9** + +| | Eb/Nt | Pilot Ec/Nt | E-DPDCH BLER | Pilot SER | +|----------------------------|-------|-------------|--------------|-----------| +| BLER based outer loop | 2.73 | -20.59 | 0.0104 | 0.00735 | +| Pilot SER based outer loop | 2.71 | -20.58 | 0.0073 | 0.00712 | + +From the results above, we can see that the outer-loop power control method based on Pilot SER yields practically the same result as the traditional outer-loop power control method based on E-DPDCH BLER. Therefore, given that over inactive periods there will not be sufficient packets to base the outer-loop power control on the E-DPDCH BLER, the Pilot SER method appears to be a viable alternative. + +Tables present results for the scenarios considered. The Tables show: + +- Pilot Ec/Nt (Ecp/Nt). +- Effective Pilot Ec/Nt (Eff. Ecp/Nt): normalized to the effective transmission ratio of DPCCH. + +###### **Results with no Code Doppler** + +The results in this subsection assume the paths of the traffic models under investigation to remain at a fixed time offset for the entire simulation length. Note that this is an unrealistic assumption as the UE speed will create Code Doppler that will skew in time the receive chips. Performance with Code Doppler is investigated in the next subsection. + +Tables 4.2.2.3.1.2.2-5 and 4.2.2.3.1.2.2-6 present the performance of DPCCH demodulation for continuous reception (no gating) and three DPCCH gating levels. + +**Table 4.2.2.3.1.2.2-5: PedA3 channel model with TTL FTL, no code Doppler** + +| Results in dB | No gating | Gating 50% | Gating 75% | Gating 87.5% | +|---------------|-----------|------------|------------|--------------| +| Ecp/Nt | -24.83 | -24.72 | -24.29 | -23.50 | +| Eff. Ecp/Nt | -24.83 | -27.72 | -30.29 | -32.50 | + +**Table 4.2.2.3.1.2.2-6: VA120 channel model with TTL FTL, no code Doppler** + +| Results in dB | No gating | Gating 50% | Gating 75% | Gating 87.5% | +|---------------|-----------|------------|------------|--------------| +| Ecp/Nt | -21.27 | -21.18 | -21.11 | -21.03 | +| Eff. Ecp/Nt | -21.27 | -24.18 | -27.11 | -30.03 | + +Table 4.2.2.3.1.2.2-7 summarizes the performance gain of DPCCH gating for the three different DPCCH gatings. + +**Table 4.2.2.3.1.2.2-7: DPCCH gating gain with TTL FTL, no code Doppler** + +| Results in dB | Gain gating 50% over 0% gating | Gain gating 75% over 0% gating | Gain gating 87.5% over 0% gating | +|---------------|--------------------------------|--------------------------------|----------------------------------| +| PA3 | 2.89 | 5.46 | 7.67 | +| VA120 | 2.91 | 5.84 | 8.76 | + +From the results in Table 4.2.2.3.1.2.2-7, the gains of DPCCH gating over inactive periods grow for larger gating periods. As we can see the gains for VA120 are very close to the ideal gains of 3dB, 6dB and 9dB for 50%, 75% and 87.5 gating respectively. + +###### **Results with Code Doppler** + +The results in this subsection assume take into account Code Doppler and therefore the DPCCH chips will skew over time. + +Tables 4.2.2.3.1.2.2-8 and 4.2.2.3.1.2.2-9 present the performance of DPCCH demodulation for continuous reception (no gating) and three DPCCH gating levels. + +**Table 4.2.2.3.1.2.2-8: PedA3 channel model with TTL FTL, code Doppler** + +| Results in dB | No gating | Gating 50% | Gating 75% | Gating 87.5% | +|---------------|-----------|------------|------------|--------------| +| Ecp/Nt | -24.83 | -24.69 | -23.87 | -23.39 | +| Eff. Ecp/Nt | -24.83 | -27.69 | -29.87 | -32.39 | + +**Table 4.2.2.3.1.2.2-9: VA120 channel model with TTL FTL, code Doppler** + +| Results in dB | No gating | Gating 50% | Gating 75% | Gating 87.5% | +|---------------|-----------|------------|------------|--------------| +| Ecp/Nt | -20.92 | -20.29 | -20.06 | -19.17 | +| Eff. Ecp/Nt | -20.92 | -23.29 | -26.06 | -28.17 | + +Table 4.2.2.3.1.2.2-10 summarizes the performance gain of DPCCH gating for the three different DPCCH gatings. + +**Table 4.2.2.3.1.2.2-10: DPCCH gating gain with TTL FTL, code Doppler** + +| Results in dB | Gain gating 50% over 0% gating | Gain gating 75% over 0% gating | Gain gating 87.5% over 0% gating | +|---------------|--------------------------------|--------------------------------|----------------------------------| +| PA3 | 2.86 | 5.03 | 7.56 | +| VA120 | 2.37 | 5.14 | 7.25 | + +From the results in Table 4.2.2.3.1.2.2-10, the gains of DPCCH gating over inactive periods grow for larger gating periods. As we can see, now the gains are further away from the ideal gains of 3dB, 6dB and 9dB for 50%, 75% and 87.5 gating respectively. + +##### 4.2.2.3.2 Link level results for CQI decoding and for large TB sizes + +###### 4.2.2.3.2.1 Simulation assumptions + +Common parameters for an ideal simulation setting and a more realistic simulation setting are found in Table 4.2.2.3.2.1-1 below. Parameters specific for the two cases are found in Table 4.2.2.3.2.1-2. Note that all simulations have been run without retransmissions. + +**Table 4.2.2.3.2.1-1: Simulation parameters common for the two simulated cases** + +| Parameter | Value | Comment | +|--------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| Gating pattern | See Figure 4.2.2.3.2.1-1 | Basic pattern is 1 sub-frame E-DCH transmission followed by 9 sub-frames E-DCH "silent". | +| DPDCH | OFF | | +| DPCCH slot format | 8 pilots + 2 TPC | | +| Channel models | AWGN
Pedestrian A, 3 km/h
Vehicular A, 30 km/h
Vehicular A, 120 km/h | | +| UL power control | ON | 0% error rate, 1-dB step size | +| Node B Rx antennas | 2 | | +| HARQ | OFF | One transmission | + +**Table 4.2.2.3.2.1-2: Parameters specific for the two simulated cases** + +| Parameter | Value, ideal | Value, realistic | +|----------------------|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| TTI | 2 ms | 2 ms | +| E-DCH data rate | 160 kbps (2 ms TTI, 320 bits TB size)
1.0 Mbps (2 ms TTI, 2000 bits TB size) | 160 kbps (2ms TTI, 320 bits TB size)
1.0 Mbps (2 ms TTI, 2000 bits TB size) | +| E-DPDCH/DPCCH | 8 dB (2 ms TTI, 320 bits TB)
11.5 dB (2 ms TTI, 2000 bits TB) | 8 dB (2 ms TTI, 320 bits TB)
13 dB (2 ms TTI, 2000 bits TB) | +| E-DPCCH/DPCCH | 0 dB | 0 dB | +| HS-DPCCH/DPCCH | HS-DPCCH off | 0 dB (2 ms TTI, 320 and 2000 bits TB) | +| Simulation time | 10 000 frames (320 bits TB)
5 000 frames (2000 bits TB) | 5 000 frames | +| Channel estimation | Ideal | TPC-aided 3-slot sliding average | +| SIR estimation | Realistic | Realistic | +| Path delay search | Ideal | Realistic | +| Frequency estimation | Ideal | Ideal | +| TPC loop delay | 1 slot | 2 slots | +| Physical channels | DPCCH + E-DPCCH + E-DPDCH | DPCCH + E-DPCCH + E-DPDCH + HS-DPCCH | + +The simulated transmission patterns are continuous DPCCH transmission, gating, gating with a 3-slot preamble, and gating with a 6-slot preamble (although the 6-slot preamble has only been simulated with the ideal parameter setting). The repetition period of the transmission pattern is 2 frames (30 slots). The simulated transmission pattern can be found in Figure 4.2.2.3.2.1-1. The transmission patterns for the realistic simulation setting are the same as for the ideal simulation setting, except that the HS-DPCCH is also transmitted whenever the E-DCH is active. Consequently, the HS-DPCCH is active in one sub-frame out of ten sub-frames. + +![Figure 4.2.2.3.2.1-1: Simulated transmission patterns for the 2 ms TTI. The figure shows four rows of transmission patterns over a 2 ms TTI, divided into 16 slots by vertical red dashed lines. Each row has an orange block representing the E-DCH in the first slot. The first row, 'Continuous DPCCH transmission:', shows a continuous green block for DPCCH across all slots. The second row, 'Gating:', shows a green block for DPCCH only in the first slot. The third row, 'Gating with a 3-slot preamble:', shows a green block for DPCCH in the first slot and the last three slots (14, 15, 16). The fourth row, 'Gating with a 6-slot preamble:', shows a green block for DPCCH in the first slot and the last six slots (11, 12, 13, 14, 15, 16).](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +Figure 4.2.2.3.2.1-1: Simulated transmission patterns for the 2 ms TTI. The figure shows four rows of transmission patterns over a 2 ms TTI, divided into 16 slots by vertical red dashed lines. Each row has an orange block representing the E-DCH in the first slot. The first row, 'Continuous DPCCH transmission:', shows a continuous green block for DPCCH across all slots. The second row, 'Gating:', shows a green block for DPCCH only in the first slot. The third row, 'Gating with a 3-slot preamble:', shows a green block for DPCCH in the first slot and the last three slots (14, 15, 16). The fourth row, 'Gating with a 6-slot preamble:', shows a green block for DPCCH in the first slot and the last six slots (11, 12, 13, 14, 15, 16). + +Figure 4.2.2.3.2.1-1. Simulated transmission patterns for the 2 ms TTI + +###### 4.2.2.3.2.2 + +###### CQI decoding simulation results + +Results for CQI decoding performance are shown only for the realistic simulation setting. + +![Four line graphs showing CQI performance (CQI P(NGdec) vs Received Ec/N0) for AWGN, ped A 3 kmph, veh A 30 kmph, and veh A 120 kmph channels. Each graph compares Continuous DPCCH transmission (blue solid line with circles), Gating (red dashed line with squares), and Gating with a 3-slot preamble (green dashed line with diamonds). In all cases, the gating methods show lower CQI values than continuous transmission, with the 3-slot preamble method generally performing better than the basic gating method.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Four line graphs showing CQI performance (CQI P(NGdec) vs Received Ec/N0) for AWGN, ped A 3 kmph, veh A 30 kmph, and veh A 120 kmph channels. Each graph compares Continuous DPCCH transmission (blue solid line with circles), Gating (red dashed line with squares), and Gating with a 3-slot preamble (green dashed line with diamonds). In all cases, the gating methods show lower CQI values than continuous transmission, with the 3-slot preamble method generally performing better than the basic gating method. + +**Table 4.2.2.3.2.2-1: CQI performance results. Gain in dB compared to the continuously transmitted DPCCH, 2ms TTI, 320 bit TB.** + +| Channel | Realistic | | +|----------------------------|-------------|-----------------| +| | No preamble | 3-slot preamble | +| AWGN
- 1 % P(NGdec) | 3.0 | 2.5 | +| PedA 3
- 1 % P(NGdec) | 1.4 | 2.2 | +| VehA 30
- 1 % P(NGdec) | 2.9 | 2.6 | +| VehA 120
- 1 % P(NGdec) | 2.8 | 3.0 | + +No unexpected results are found, but rather the findings are in line with the E-DCH results. However, the gains from gating are less pronounced for the CQI than for E-DCH, and it is likely that $\beta_{hs}$ needs to be increased slightly resulting in a minor degradation of the overall gating gain. + +###### 4.2.2.3.2.3 + +###### Simulation results with 2000-bit TB size + +The figures below provide simulation results for the ideal and the realistic simulations. Four channels have been simulated: AWGN, Pedestrian A 3 km/h, Vehicular A 30 km/h, and Vehicular A 120 km/h. Two figures are shown for each simulation, BLER vs. received $E_b/N_0$ (per antenna), and throughput vs. received $E_c/N_0$ (per antenna). + +###### Simulation results for the ideal parameter setting: + +![BLER vs. Received Eb/N0 (per antenna) [dB] for AWGN channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). All curves show a sharp decrease in BLER as Eb/N0 increases, with the gating schemes performing slightly better than continuous transmission at low Eb/N0.](bf5971de45ccc2d1a9e437d0f486ee08_img.jpg) + +AWGN + +BLER + +Received $E_b/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +BLER vs. Received Eb/N0 (per antenna) [dB] for AWGN channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). All curves show a sharp decrease in BLER as Eb/N0 increases, with the gating schemes performing slightly better than continuous transmission at low Eb/N0. + +![Throughput vs. Received Ec/N0 (per antenna) [dB] for AWGN channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). All curves show an increase in throughput as Ec/N0 increases, reaching a plateau around 1000 Kbps. The gating schemes reach the plateau at lower Ec/N0 values than continuous transmission.](0ff74f5b84bfe2303c9204d4feb60d5f_img.jpg) + +AWGN + +Throughput [Kbps] + +Received $E_c/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +Throughput vs. Received Ec/N0 (per antenna) [dB] for AWGN channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). All curves show an increase in throughput as Ec/N0 increases, reaching a plateau around 1000 Kbps. The gating schemes reach the plateau at lower Ec/N0 values than continuous transmission. + +![BLER vs. Received Eb/N0 (per antenna) [dB] for Pedestrian A 3 km/h channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes show better performance (lower BLER) than continuous transmission across the range of Eb/N0.](1d62d44c82c21f9056394d2fa042b8e9_img.jpg) + +ped A 3 kmh + +BLER + +Received $E_b/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +BLER vs. Received Eb/N0 (per antenna) [dB] for Pedestrian A 3 km/h channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes show better performance (lower BLER) than continuous transmission across the range of Eb/N0. + +![Throughput vs. Received Ec/N0 (per antenna) [dB] for Pedestrian A 3 km/h channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes achieve higher throughput at lower Ec/N0 values compared to continuous transmission.](1f39c3dd17bd94ca9aa24f5d13a5605f_img.jpg) + +ped A 3 kmh + +Throughput [Kbps] + +Received $E_c/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +Throughput vs. Received Ec/N0 (per antenna) [dB] for Pedestrian A 3 km/h channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes achieve higher throughput at lower Ec/N0 values compared to continuous transmission. + +![BLER vs. Received Eb/N0 (per antenna) [dB] for Vehicular A 30 km/h channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes show improved performance over continuous transmission in this channel.](ebbc36b94b206c93f73a15481c321fd6_img.jpg) + +veh A 30 kmh + +BLER + +Received $E_b/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +BLER vs. Received Eb/N0 (per antenna) [dB] for Vehicular A 30 km/h channel. The y-axis is BLER on a log scale from 10^-3 to 10^0. The x-axis is Received Eb/N0 (per antenna) [dB] from -4 to 6. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes show improved performance over continuous transmission in this channel. + +![Throughput vs. Received Ec/N0 (per antenna) [dB] for Vehicular A 30 km/h channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes reach the maximum throughput at lower Ec/N0 values than continuous transmission.](b18c42a97abc39df27fd810bc267f2fc_img.jpg) + +veh A 30 kmh + +Throughput [Kbps] + +Received $E_c/N_0$ (per antenna) [dB] + +Continuous DPCCH transmission +Gating +Gating with a 3-slot preamble +Gating with a 6-slot preamble + +Throughput vs. Received Ec/N0 (per antenna) [dB] for Vehicular A 30 km/h channel. The y-axis is Throughput [Kbps] from 300 to 1100. The x-axis is Received Ec/N0 (per antenna) [dB] from -20 to -10. Four curves are shown: Continuous DPCCH transmission (blue circles), Gating (red squares), Gating with a 3-slot preamble (green diamonds), and Gating with a 6-slot preamble (magenta triangles). The gating schemes reach the maximum throughput at lower Ec/N0 values than continuous transmission. + +Simulation results for the realistic parameter setting: + +Error: + +58 + +Error: Reference source not + +![AWGN BLER plot](3881b390d52f27a35faedfc170916c86_img.jpg) + +AWGN + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: Received $E_b/N_0$ (per antenna) [dB] (-4 to 10) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the Bit Error Rate (BLER) for three transmission methods in an AWGN environment. The 'Gating with a 3-slot preamble' method (green dashed line) shows the best performance, reaching a BLER of 10-3 at approximately 2.5 dB. The 'Continuous DPCCH transmission' (blue solid line) follows, reaching 10-3 at about 3.5 dB. The 'Gating' method (red dashed line) has the worst performance, reaching 10-3 at approximately 4.5 dB. + +AWGN BLER plot + +![AWGN Throughput plot](056f93110af61f80a3f9526f06423d44_img.jpg) + +AWGN + +Y-axis: Throughput [kbps] (300 to 1100) + +X-axis: Received $E_c/N_0$ (per antenna) [dB] (-18 to -6) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the throughput for three transmission methods in an AWGN environment. All three methods achieve a peak throughput of 1000 kbps. The 'Gating' (red dashed) and 'Gating with a 3-slot preamble' (green dashed) methods reach this peak at lower $E_c/N_0$ values (around -14 dB and -15 dB respectively) compared to the 'Continuous DPCCH transmission' (blue solid line), which reaches the peak at approximately -12 dB. + +AWGN Throughput plot + +![ped A 3 kmph BLER plot](2c5884241ad393e03dd8e4ea25ff74a2_img.jpg) + +ped A 3 kmph + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: Received $E_b/N_0$ (per antenna) [dB] (-2 to 10) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the BLER for three transmission methods in a pedestrian environment at 3 kmph. The 'Gating with a 3-slot preamble' (green dashed line) and 'Continuous DPCCH transmission' (blue solid line) both reach a BLER of 10-3 at approximately 4.5 dB. The 'Gating' method (red dashed line) performs significantly worse, reaching a BLER of 10-3 at about 10 dB. + +ped A 3 kmph BLER plot + +![ped A 3 kmph Throughput plot](7b24462ab2c9a9e6ed5937f2c1195f75_img.jpg) + +ped A 3 kmph + +Y-axis: Throughput [kbps] (300 to 1100) + +X-axis: Received $E_c/N_0$ (per antenna) [dB] (-18 to -6) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the throughput for three transmission methods in a pedestrian environment at 3 kmph. All three methods achieve a peak throughput of 1000 kbps. The 'Gating with a 3-slot preamble' (green dashed line) reaches the peak at approximately -13 dB, while the 'Continuous DPCCH transmission' (blue solid line) and 'Gating' (red dashed line) reach it at approximately -12 dB. + +ped A 3 kmph Throughput plot + +![veh A 30 kmph BLER plot](ead8d1841c351608343c98f30e5f3f07_img.jpg) + +veh A 30 kmph + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: Received $E_b/N_0$ (per antenna) [dB] (-2 to 10) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the BLER for three transmission methods in a vehicle environment at 30 kmph. The 'Gating with a 3-slot preamble' (green dashed line) reaches a BLER of 10-3 at approximately 5.5 dB. The 'Continuous DPCCH transmission' (blue solid line) and 'Gating' (red dashed line) both reach a BLER of 10-3 at approximately 8.5 dB. + +veh A 30 kmph BLER plot + +![veh A 30 kmph Throughput plot](f9d11004ac6966f27936c8d01e579313_img.jpg) + +veh A 30 kmph + +Y-axis: Throughput [kbps] (300 to 1200) + +X-axis: Received $E_c/N_0$ (per antenna) [dB] (-18 to -6) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the throughput for three transmission methods in a vehicle environment at 30 kmph. The 'Gating with a 3-slot preamble' (green dashed line) achieves a higher peak throughput of approximately 1000 kbps at around -11 dB. The 'Continuous DPCCH transmission' (blue solid line) and 'Gating' (red dashed line) achieve a peak throughput of approximately 1000 kbps at around -10 dB. + +veh A 30 kmph Throughput plot + +![veh A 120 kmph BLER plot](fe8672dfa08ec40ce3d9eb6277780260_img.jpg) + +veh A 120 kmph + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: Received $E_b/N_0$ (per antenna) [dB] (-2 to 10) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the BLER for three transmission methods in a vehicle environment at 120 kmph. The 'Gating' (red dashed line) and 'Gating with a 3-slot preamble' (green dashed line) both reach a BLER of 10-3 at approximately 9.5 dB. The 'Continuous DPCCH transmission' (blue solid line) reaches a BLER of 10-3 at approximately 10 dB. + +veh A 120 kmph BLER plot + +![veh A 120 kmph Throughput plot](e07207e429a7d92d9a8e3dd5030b6fda_img.jpg) + +veh A 120 kmph + +Y-axis: Throughput [kbps] (300 to 1100) + +X-axis: Received $E_c/N_0$ (per antenna) [dB] (-18 to -6) + +Legend: + +- Continuous DPCCH transmission (blue solid line with circles) +- Gating (red dashed line with crosses) +- Gating with a 3-slot preamble (green dashed line with diamonds) + +Detailed description: This plot shows the throughput for three transmission methods in a vehicle environment at 120 kmph. All three methods achieve a peak throughput of 1000 kbps. The 'Gating' (red dashed line) and 'Gating with a 3-slot preamble' (green dashed line) reach this peak at approximately -10 dB, while the 'Continuous DPCCH transmission' (blue solid line) reaches it at approximately -9 dB. + +veh A 120 kmph Throughput plot + +**Table 4.2.2.3.2.3-1: Gain dB compared to the continuously transmitted DPCCH, 2ms TTI, 2000 bit TB** + +| Channel | Ideal | | | Realistic | | | +|------------|-------------|-----------------|-----------------|-------------|-----------------|-----------------| +| | No preamble | 3-slot preamble | 6-slot preamble | No preamble | 3-slot preamble | 6-slot preamble | +| AWGN | | | | | | | +| - 50% BLER | 1.1 | 1.0 | 0.9 | 1.3 | 1.2 | - | +| - 5% BLER | 1.2 | 1.0 | 1.0 | 1.6 | 1.4 | - | +| PedA 3 | | | | | | | +| - 50% BLER | 0.8 | 0.9 | 1.0 | 1.1 | 1.3 | - | +| - 5% BLER | -1.2 | 0.5 | 0.7 | -0.5 | 0.8 | - | +| VehA 30 | | | | | | | +| - 50% BLER | 1.0 | 1.0 | 0.9 | 1.0 | 1.3 | - | +| - 5% BLER | 0.0 | 1.2 | 1.0 | 0.7 | 1.2 | - | +| VehA 120 | | | | | | | +| - 50% BLER | - | - | - | 1.6 | 1.3 | - | +| - 5% BLER | - | - | - | 1.6 | 0.9 | - | + +From the figures and the table above it is clear that the gains from gating are less for higher data rates compared to small and moderate data rates. This is expected since the power ratio between E-DPDCH and DPCCH increases as a function of the data rate. However, the trends are the same here as for lower data rates, but the preamble seems to be more important in this case. + +This case (2000 bits transmitted every 20 ms) might be somewhat artificial, but it indicates that the E-DCH performance can be robust after a gating gap also for traffic with higher data rates than VoIP. + +##### 4.2.2.3.3 Preamble detection link level result for uplink DPCCH gating with long gating gap + +This section presents preamble detection performance simulation results on uplink DPCCH gating with long gating gap. + +###### 4.2.2.3.3.1 Simulation assumptions + +**Table 4.2.2.3.3.1-1: Simulation parameters** + +| Parameter | Value | Comment | +|-------------------|----------------------------|-----------------------------------| +| Channel model | PA3, PB3, VA30, VA120 | | +| Rx Antennas | 2 | | +| Path Search | Real | | +| Ec/N0 dB | DPCCH | | +| DPCCH slot format | 1 | 8 pilot symbols out of 10 symbols | +| DPCCH gap length | 1 sec | | +| Preamble length | 9, 12, 15, 18 and 21 slots | | +| Inner loop PC | Off | | +| Outer loop PC | Off | | +| False Alarm | 0.1% | | +| Statistics number | 5000 for each case | | + +###### 4.2.2.3.3.2 + +###### Simulation results + +![Four empty plot frames for Preamble Detection Probability. The top-left frame is labeled 'preaml' and has a y-axis labeled 'detection probability' with a '1' at the top. The top-right frame has a y-axis labeled 'detection probability' with a '1' at the top. The bottom-left frame is labeled 'preaml' and has a y-axis labeled 'detection probability' with a '1' at the top. The bottom-right frame is labeled 'prear' and has a y-axis labeled 'detection probability' with a '1' at the top. All frames have dashed horizontal grid lines.](293fb0a508d182b518ea429927dfd343_img.jpg) + +Four empty plot frames for Preamble Detection Probability. The top-left frame is labeled 'preaml' and has a y-axis labeled 'detection probability' with a '1' at the top. The top-right frame has a y-axis labeled 'detection probability' with a '1' at the top. The bottom-left frame is labeled 'preaml' and has a y-axis labeled 'detection probability' with a '1' at the top. The bottom-right frame is labeled 'prear' and has a y-axis labeled 'detection probability' with a '1' at the top. All frames have dashed horizontal grid lines. + +Fig 4.2.2.3.3.2-1. Preamble Detection Probability for different preamble length and various channel models + +#### 4.2.2.4 System performance + +##### 4.2.2.4.1 Simulation assumptions + +**Table 4.2.2.4.1-1: Simulation parameters** + +| Parameter | Value | comments | +|-------------------------------------|----------------------|----------------------------------------------------------------------------------| +| Frame Size | 2ms TTI / 10 ms TTI | | +| Inter site distance | 2.8 km | | +| Cell configuration | ITU Veh-A, Macrocell | | +| Voice call mean length | 60 seconds | | +| Voice on/off mean length | 3 seconds | | +| Header compressed VoIP packet size | 31+7= 38 bytes | | +| UE speed | 3 kmph | | +| VoIP packet arrival interval | 20 ms | With 10 ms TTI 2 VoIP packets transmitted every 40 ms. | +| Outage observation window length | 10 seconds | | +| Cell outage threshold | 5% FER | | +| Soft handover Window_Add | 1 dB / 4 dB | | +| Number of HARQ channels | 8 / 4 | 2 ms TTI / 10 ms TTI respectively | +| Max number of L1 transmissions | 4 / 2 | 2 ms TTI / 10 ms TTI respectively | +| E-DPCCH | Error free | | +| HS-DPCCH | | CQI sent every 10 ms
ACK/NACK sent every 40 ms | +| E-DCH Bitrate | 160 kbps / 64 kbps | 2 ms TTI / 10 ms TTI respectively | +| Beta_ed | 8 dB | | +| Beta_ec | 3 dB / -6 dB | 2 ms TTI / 10 ms TTI respectively | +| Beta_hs | 0 dB | | +| Voice activity | 0.5 | DPCCH transmitted in every 10 th sub-frame during voice inactivity | +| Mean transmissions | 3 | Only used for semi-analytical study, and collected from system level simulations | +| Other cell to own cell interference | 0.65 | Only used for semi-analytical study | + +##### 4.2.2.4.2 VoIP results with and without gating – 2 ms TTI + +33% throughput in the figures refer to HARQ operating point of 3 transmissions per packet, or more generally: + $1/\text{throughput-\%} = \text{average number of transmissions per transmitted packet.}$ + +In Figure 4.2.2.4.2-1 the cell noise rise is shown as a function of the number of voice users. The two solid lines are from semi-analytical calculations with continuous (blue) and gated (red) DPCCH representing the theoretical upper bound of the system capacity with the given assumptions. The four simulated curves (sims) represents continuous and gated DPCCH with HS-DPCCH transmitted simultaneously with E-DCH (OFF=0) and HS-DPCCH not transmitted simultaneously with E-DCH (OFF=3). + +![Line graph titled '160kbps, 2ms TTI, 33%throughput, VA3 with E-DPCCH&HS-DPCCH' showing Noise rise (dB) vs. Num of VoIP users. The graph compares six scenarios: 'with ACK/CQI' (solid blue line), 'Gating with ACK/CQI' (solid red line), 'Sims with ACK/CQI OFF=0' (dashed blue line with 'x' markers), 'Sims with ACK/CQI OFF=3' (dashed blue line with circle markers), 'Sims Gating with ACK/CQI OFF=0' (dashed red line with '+' markers), and 'Sims Gating with ACK/CQI OFF=3' (dashed green line with square markers). Noise rise increases with the number of users, with the 'Sims with ACK/CQI OFF=3' scenario showing the steepest increase, reaching over 14 dB at 90 users. The 'Gating with ACK/CQI' scenario shows the lowest noise rise, reaching about 11 dB at 160 users.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +| Num of VoIP users | with ACK/CQI | Gating with ACK/CQI | Sims with ACK/CQI OFF=0 | Sims with ACK/CQI OFF=3 | Sims Gating with ACK/CQI OFF=0 | Sims Gating with ACK/CQI OFF=3 | +|-------------------|--------------|---------------------|-------------------------|-------------------------|--------------------------------|--------------------------------| +| 20 | 1.5 | 1.0 | 1.5 | 1.5 | 1.5 | 1.5 | +| 40 | 2.5 | 1.5 | 2.5 | 2.5 | 2.5 | 2.5 | +| 60 | 3.5 | 2.0 | 3.5 | 3.5 | 3.5 | 3.5 | +| 80 | 5.0 | 2.5 | 5.0 | 7.5 | 5.0 | 5.0 | +| 100 | 7.0 | 3.5 | 7.0 | - | 7.0 | 7.0 | +| 120 | 10.0 | 5.0 | 10.0 | - | 10.0 | 10.0 | +| 140 | - | 7.0 | - | - | - | - | +| 160 | - | 11.0 | - | - | - | - | + +Line graph titled '160kbps, 2ms TTI, 33%throughput, VA3 with E-DPCCH&HS-DPCCH' showing Noise rise (dB) vs. Num of VoIP users. The graph compares six scenarios: 'with ACK/CQI' (solid blue line), 'Gating with ACK/CQI' (solid red line), 'Sims with ACK/CQI OFF=0' (dashed blue line with 'x' markers), 'Sims with ACK/CQI OFF=3' (dashed blue line with circle markers), 'Sims Gating with ACK/CQI OFF=0' (dashed red line with '+' markers), and 'Sims Gating with ACK/CQI OFF=3' (dashed green line with square markers). Noise rise increases with the number of users, with the 'Sims with ACK/CQI OFF=3' scenario showing the steepest increase, reaching over 14 dB at 90 users. The 'Gating with ACK/CQI' scenario shows the lowest noise rise, reaching about 11 dB at 160 users. + +Figure 4.2.2.4.2-1: Noise rise as a function of # of VoIP users, calculated and simulated + +In Figure 4.2.2.4.2-2 the same four simulation cases as in Figure 4.2.2.4.2-1 are presented showing this time the cell outage as a function of a number of VoIP users. + +![Line graph titled 'Cell Outage of 160kbps, 2ms TTI, 33%throughput, VA3 with E-DPCCH&HS-DPCCH' showing Outage (%) vs. Num of VoIP users. The graph compares four simulation cases: 'Sims with ACK/CQI OFF=0' (dashed blue line with 'x' markers), 'Sims with ACK/CQI OFF=3' (dashed blue line with circle markers), 'Sims Gating with ACK/CQI OFF=0' (dashed red line with '+' markers), and 'Sims Gating with ACK/CQI OFF=3' (dashed green line with square markers). Cell outage is low (below 2%) for up to about 80 users, after which it increases sharply. The 'Sims with ACK/CQI OFF=3' case shows the highest outage, reaching over 12% at 90 users. The 'Sims Gating with ACK/CQI OFF=3' case shows the lowest outage, reaching about 8.5% at 130 users.](03b9c04a0552e519e849210b8e2bf596_img.jpg) + +| Num of VoIP users | Sims with ACK/CQI OFF=0 | Sims with ACK/CQI OFF=3 | Sims Gating with ACK/CQI OFF=0 | Sims Gating with ACK/CQI OFF=3 | +|-------------------|-------------------------|-------------------------|--------------------------------|--------------------------------| +| 20 | 1.0 | 1.0 | 1.0 | 1.0 | +| 40 | 1.0 | 1.0 | 1.0 | 1.0 | +| 60 | 1.0 | 1.0 | 1.0 | 1.0 | +| 80 | 2.0 | 2.0 | 1.0 | 1.0 | +| 100 | 1.5 | - | 1.5 | 1.5 | +| 120 | 3.5 | - | 3.5 | 3.5 | +| 140 | - | - | - | - | + +Line graph titled 'Cell Outage of 160kbps, 2ms TTI, 33%throughput, VA3 with E-DPCCH&HS-DPCCH' showing Outage (%) vs. Num of VoIP users. The graph compares four simulation cases: 'Sims with ACK/CQI OFF=0' (dashed blue line with 'x' markers), 'Sims with ACK/CQI OFF=3' (dashed blue line with circle markers), 'Sims Gating with ACK/CQI OFF=0' (dashed red line with '+' markers), and 'Sims Gating with ACK/CQI OFF=3' (dashed green line with square markers). Cell outage is low (below 2%) for up to about 80 users, after which it increases sharply. The 'Sims with ACK/CQI OFF=3' case shows the highest outage, reaching over 12% at 90 users. The 'Sims Gating with ACK/CQI OFF=3' case shows the lowest outage, reaching about 8.5% at 130 users. + +Figure 4.2.2.4.2-2: Cell outage % as a function of # of VoIP users, simulated + +Figure 4.2.2.4.2-3 shows the VoIP packet delay distribution with the gated DPCCH. The steps in the curves represent different number of retransmissions required. + +With the assumptions used in the simulations the UE transmitter could be off 73% of the time when gating is applied. + +![Figure 4.2.2.4.2-3: Packet delay distribution of the simulations. The graph shows the Cumulative Distribution Function (CDF) of packet delay in seconds for six different numbers of User Equipment (UEs): 30, 50, 70, 90, 110, and 130. The x-axis ranges from 0 to 0.09 seconds, and the y-axis ranges from 0 to 1. The curves show that as the number of UEs increases, the packet delay distribution shifts to the right, indicating higher delays. The 130UEs curve reaches a CDF of 1 at approximately 0.05 seconds, while the 30UEs curve reaches it at approximately 0.04 seconds.](8e395c7d3a0249c410ef3c5a4f666170_img.jpg) + +Gating DPCCH with E-DPCCH&HS-DPCCH + +CDF + +Delay(s) + +30UEs +50UEs +70UEs +90UEs +110UEs +130UEs + +Figure 4.2.2.4.2-3: Packet delay distribution of the simulations. The graph shows the Cumulative Distribution Function (CDF) of packet delay in seconds for six different numbers of User Equipment (UEs): 30, 50, 70, 90, 110, and 130. The x-axis ranges from 0 to 0.09 seconds, and the y-axis ranges from 0 to 1. The curves show that as the number of UEs increases, the packet delay distribution shifts to the right, indicating higher delays. The 130UEs curve reaches a CDF of 1 at approximately 0.05 seconds, while the 30UEs curve reaches it at approximately 0.04 seconds. + +Figure 4.2.2.4.2-3: Packet delay distribution of the simulations + +##### 4.2.2.4.3 VoIP results with and without gating – 10 ms TTI and packet bundling + +The results in figures 4.2.2.4.3-4...-6 are simulated with outer loop power control operating after the first transmission. The HARQ operating points of 25% and 67% initial transmission BLER have been investigated with and without uplink DPCCH gating. The used traffic model is VoIP with bundling of two packets, i.e. in all the cases 2 VoIP packets have been bundled to a single TTI and new initial transmission occurs every 40 ms when the user is in the active speech cycle. + +- Figure 4.2.2.4.3-4 shows the RoT curves for the simulated cases, +- Figure 4.2.2.4.3-5 shows the cell outage curves for the simulated cases, +- Figure 4.2.2.4.3-6 shows the residual FER curves for the simulated cases. + +![Line graph titled 'Cell RoT Compare OLPC' showing Noise rise (dB) vs. Num of VoIP users for four configurations: Cont. OLPC 1tx FER 67%, Gating OLPC 1tx FER 67%, Cont. OLPC 1tx FER 25%, and Gating OLPC 1tx FER 25%.](c742b64169a38a7f3f990172019878c8_img.jpg) + +The graph shows the relationship between the number of VoIP users and the noise rise in dB for four different OLPC configurations. The x-axis represents the number of VoIP users from 40 to 160, and the y-axis represents the noise rise in dB from 0 to 8. The four configurations are: Continuous OLPC with 1tx FER 67% (solid blue line), Gating OLPC with 1tx FER 67% (dashed blue line), Continuous OLPC with 1tx FER 25% (solid red line), and Gating OLPC with 1tx FER 25% (dashed red line). The Continuous OLPC configurations show a steeper increase in noise rise compared to the Gating configurations. The Continuous OLPC 1tx FER 25% configuration reaches a noise rise of 8 dB at approximately 60 users, while the Continuous OLPC 1tx FER 67% configuration reaches 8 dB at approximately 80 users. The Gating OLPC 1tx FER 25% configuration reaches 8 dB at approximately 105 users, and the Gating OLPC 1tx FER 67% configuration reaches 8 dB at approximately 115 users. + +| Num of VoIP users | Cont. OLPC 1tx FER 67% (dB) | Gating OLPC 1tx FER 67% (dB) | Cont. OLPC 1tx FER 25% (dB) | Gating OLPC 1tx FER 25% (dB) | +|-------------------|-----------------------------|------------------------------|-----------------------------|------------------------------| +| 40 | 2.5 | 2.0 | 3.0 | 2.5 | +| 60 | 4.0 | 3.0 | 5.5 | 4.0 | +| 80 | 6.0 | 4.5 | 8.0 | 5.5 | +| 100 | 8.0 | 6.0 | - | 7.5 | +| 120 | - | 8.0 | - | - | + +Line graph titled 'Cell RoT Compare OLPC' showing Noise rise (dB) vs. Num of VoIP users for four configurations: Cont. OLPC 1tx FER 67%, Gating OLPC 1tx FER 67%, Cont. OLPC 1tx FER 25%, and Gating OLPC 1tx FER 25%. + +Figure 4.2.2.4.3-4: Noise rise as a function of # of VoIP users + +![Line graph titled 'Cell Outage Comparison' showing Outage (%) vs. Num of VoIP users for four configurations: PC1tx Gating FER 67%, PC1tx Cont. FER 67%, PC1tx Gating FER 25%, and PC1tx Cont. FER 25%.](808fbf3058e19e39757a0a84c7796059_img.jpg) + +The graph shows the relationship between the number of VoIP users and the cell outage percentage for four different PC1tx configurations. The x-axis represents the number of VoIP users from 30 to 130, and the y-axis represents the outage percentage from 0 to 25. The four configurations are: PC1tx Gating FER 67% (dashed blue line with 'x' markers), PC1tx Continuous FER 67% (solid blue line with square markers), PC1tx Gating FER 25% (dashed red line with 'x' markers), and PC1tx Continuous FER 25% (solid red line with square markers). The Continuous FER 25% configuration shows a sharp increase in outage percentage starting around 60 users, reaching approximately 13% at 70 users. The Continuous FER 67% configuration shows a sharp increase in outage percentage starting around 80 users, reaching approximately 23% at 90 users. The Gating configurations show much lower outage percentages, remaining below 5% even at 130 users. The PC1tx Gating FER 25% configuration reaches approximately 10% outage at 130 users, while the PC1tx Gating FER 67% configuration reaches approximately 5% outage at 130 users. + +| Num of VoIP users | PC1tx Gating FER 67% (%) | PC1tx Cont. FER 67% (%) | PC1tx Gating FER 25% (%) | PC1tx Cont. FER 25% (%) | +|-------------------|--------------------------|-------------------------|--------------------------|-------------------------| +| 30 | 2.5 | 1.0 | 0.5 | 0.5 | +| 40 | 2.5 | 1.0 | 0.5 | 0.5 | +| 50 | 2.5 | 1.5 | 0.5 | 0.5 | +| 60 | 2.5 | 1.0 | 0.5 | 1.0 | +| 70 | 2.5 | 1.5 | 0.5 | 13.0 | +| 80 | 2.5 | 3.0 | 0.5 | - | +| 90 | 2.5 | 23.0 | 0.5 | - | +| 100 | 2.5 | - | 1.0 | - | +| 110 | 2.5 | - | 3.0 | - | +| 120 | 2.5 | - | 6.0 | - | +| 130 | 2.5 | - | 10.5 | - | + +Line graph titled 'Cell Outage Comparison' showing Outage (%) vs. Num of VoIP users for four configurations: PC1tx Gating FER 67%, PC1tx Cont. FER 67%, PC1tx Gating FER 25%, and PC1tx Cont. FER 25%. + +Figure 4.2.2.4.3-5: Cell outage % as a function of # of VoIP users + +![Figure 4.2.2.4.3-6: Residual FER as a function of # of VoIP users. The graph shows Avg Residual FER on the y-axis (0 to 0.07) versus UEs/Cell on the x-axis (20 to 140). Four curves are plotted: Cont. FER 67% (solid blue line), Gating FER 67% (dashed blue line with circles), Cont. FER 25% (solid red line), and Gating FER 25% (dashed red line with circles). The Cont. FER 67% curve rises sharply after 80 UEs/Cell, while the Gating FER 67% curve remains relatively flat. The Cont. FER 25% curve rises sharply after 60 UEs/Cell, and the Gating FER 25% curve remains relatively flat until about 100 UEs/Cell, then rises slightly.](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +| UEs/Cell | Cont. FER 67% | Gating FER 67% | Cont. FER 25% | Gating FER 25% | +|----------|---------------|----------------|---------------|----------------| +| 30 | 0.003 | 0.005 | 0.001 | 0.001 | +| 40 | 0.003 | 0.005 | 0.001 | 0.001 | +| 50 | 0.004 | 0.005 | 0.001 | 0.001 | +| 60 | 0.004 | 0.005 | 0.001 | 0.001 | +| 70 | 0.005 | 0.006 | 0.058 | 0.001 | +| 80 | 0.007 | 0.007 | - | 0.001 | +| 90 | 0.070 | 0.008 | - | 0.002 | +| 100 | - | 0.009 | - | 0.003 | +| 110 | - | 0.010 | - | 0.005 | +| 120 | - | 0.012 | - | 0.010 | +| 130 | - | - | - | 0.025 | + +Figure 4.2.2.4.3-6: Residual FER as a function of # of VoIP users. The graph shows Avg Residual FER on the y-axis (0 to 0.07) versus UEs/Cell on the x-axis (20 to 140). Four curves are plotted: Cont. FER 67% (solid blue line), Gating FER 67% (dashed blue line with circles), Cont. FER 25% (solid red line), and Gating FER 25% (dashed red line with circles). The Cont. FER 67% curve rises sharply after 80 UEs/Cell, while the Gating FER 67% curve remains relatively flat. The Cont. FER 25% curve rises sharply after 60 UEs/Cell, and the Gating FER 25% curve remains relatively flat until about 100 UEs/Cell, then rises slightly. + +Figure 4.2.2.4.3-6: Residual FER as a function of # of VoIP users + +With the assumptions used in the simulations the UE transmitter could be off 72% or 67% of the time with outer loop power control targeting for 25% or 67% BLER after the first transmission respectively. + +##### 4.2.2.4.4 VoIP results - Summary + +Table 4.2.2.4.4-1: Summary of the VoIP capacity results with uplink DPCCH gating + +| TTI | Average number of transmissions | Capacity criteria: 5% FER over 10 s | | | Capacity criteria: Noise rise 6 dB | | | +|--------|---------------------------------|-------------------------------------|-------------|-------------|------------------------------------|-------------|-------------| +| | | Continuous DPCCH | Gated DPCCH | Gating Gain | Continuous DPCCH | Gated DPCCH | Gating Gain | +| 2 ms | ~3 | 82 users | 123 users | 50% | 75 users | 106 users | 41% | +| 10 ms* | 1.25 | 65 users | 115 users | 77% | 61 users | 93 users | 52% | +| | 1.67 | 80 users | 120 users | 50% | 73 users | 103 users | 41% | + +\* 10 ms TTI results using bundling of 2 VoIP frames in a single TTI + +For 2 ms TTI case the transmitter was off 73% of the time when gating was applied + +For 10 ms TTI cases the transmitter was off 72% and 67% of the time for 1.25 and for 1.67 average transmissions per packet respectively. + +##### 4.2.2.4.5 Impact of inactive users to cell throughput + +Table 4.2.2.4.5-1: Further simulation parameters used in figures 4.2.2.4.5-1...3 + +| Parameter | Value | comments | +|--------------------|------------------|----------| +| Cell configuration | ITU Ped-A, Veh-A | | + +| Parameter | Value | comments | +|----------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------| +| UE speed | Ped-A 3 kmph, Veh-A 30 kmph | | +| Traffic model | Full buffer, no data | 6 full buffer users, rest with no data | +| E-DCH Bitrate | {64, 128, 256, 384, 512, 1024} kbps | | +| DPCCH CIR target | -18.1 dB | | +| Load target | 6 dB | | +| DPCCH gating pattern for no-data users | {12, 9, 0} slots gated in every radio frame. | 0 gated slots equals to no gating.
Full buffer users transmit continuously | +| Other parameters | As in table 4.2.2.4-1 | | + +In figures 4.2.2.4.5-1 and 4.2.2.4.5-2 the impact of large number of inactive users in CELL\_DCH on the cell throughput has been shown. An ideal reference curve for gating patterns has been calculated simply by scaling the continuous DPCCH curve with the gating-%. + +Figure 4.2.2.4.5-3 shows the RoT overshoot probability for the same cases. + +![Figure 4.2.2.4.5-1: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, PA3. The graph shows Cell Throughput (kbps) on the Y-axis (0 to 1300) versus Number of no-data UEs in CELL_DCH on the X-axis (0 to 55). Five curves are plotted: PedA_not gated (magenta squares), PedA_9/15 (dark blue diamonds), PedA_12/15 (yellow triangles), PedA_9/15 ideal (cyan crosses), and PedA_12/15 ideal (purple asterisks). The 'not gated' case shows a sharp drop in throughput as the number of no-data UEs increases. The 'ideal' cases show a more gradual decline, maintaining higher throughput than the non-ideal gating patterns.](70546cb98239089866510133c7fbc169_img.jpg) + +| Number of no-data UEs | PedA_not gated (kbps) | PedA_9/15 (kbps) | PedA_12/15 (kbps) | PedA_9/15 ideal (kbps) | PedA_12/15 ideal (kbps) | +|-----------------------|-----------------------|------------------|-------------------|------------------------|-------------------------| +| 0 | 1300 | 1300 | 1300 | 1300 | 1300 | +| 10 | 900 | 1100 | 1150 | 1100 | 1200 | +| 15 | 650 | 1000 | 1050 | 1000 | 1150 | +| 20 | 500 | 950 | 1000 | 950 | 1100 | +| 25 | 300 | 850 | 950 | 900 | 1050 | +| 30 | 150 | 750 | 900 | 850 | 1000 | +| 35 | - | 650 | 850 | 800 | 950 | +| 40 | - | 550 | 800 | 750 | 900 | +| 45 | - | 350 | 550 | 650 | 850 | +| 50 | - | 150 | 250 | 550 | 800 | + +Figure 4.2.2.4.5-1: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, PA3. The graph shows Cell Throughput (kbps) on the Y-axis (0 to 1300) versus Number of no-data UEs in CELL\_DCH on the X-axis (0 to 55). Five curves are plotted: PedA\_not gated (magenta squares), PedA\_9/15 (dark blue diamonds), PedA\_12/15 (yellow triangles), PedA\_9/15 ideal (cyan crosses), and PedA\_12/15 ideal (purple asterisks). The 'not gated' case shows a sharp drop in throughput as the number of no-data UEs increases. The 'ideal' cases show a more gradual decline, maintaining higher throughput than the non-ideal gating patterns. + +Figure 4.2.2.4.5-1: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, PA3 + +![Figure 4.2.2.4.5-2: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, VA30. The graph shows Cell Throughput (kbps) on the y-axis (0 to 1300) versus Number of no-data UEs in CELL_DCH on the x-axis (0 to 55). Five data series are plotted: VehA_not gated (cyan line with 'x' markers), VehA_9/15 (purple line with 'x' markers), VehA_12/15 (brown line with circle markers), Veh_9/15 ideal (blue line with diamond markers), and VehA_12/15 ideal (magenta line with square markers). The ideal gating patterns maintain higher throughput as the number of no-data users increases compared to the non-gated and gated patterns.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +Figure 4.2.2.4.5-2: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, VA30. The graph shows Cell Throughput (kbps) on the y-axis (0 to 1300) versus Number of no-data UEs in CELL\_DCH on the x-axis (0 to 55). Five data series are plotted: VehA\_not gated (cyan line with 'x' markers), VehA\_9/15 (purple line with 'x' markers), VehA\_12/15 (brown line with circle markers), Veh\_9/15 ideal (blue line with diamond markers), and VehA\_12/15 ideal (magenta line with square markers). The ideal gating patterns maintain higher throughput as the number of no-data users increases compared to the non-gated and gated patterns. + +Figure 4.2.2.4.5-2: Cell throughput as a function of no-data users, different gating patterns vs. ideal gating, VA30 + +![Figure 4.2.2.4.5-3: RoT Overshoot as a function of no-data users, different gating patterns and channel models. The figure contains two side-by-side line graphs. The left graph shows Overshoot (RoT>7dB) for channel model PA3, with the y-axis ranging from 0% to 50% and the x-axis from 0 to 55. The right graph shows the same for channel model VA30, with the y-axis ranging from 0% to 24% and the x-axis from 0 to 55. Both graphs compare PedA_not gated (magenta line with square markers), PedA_9/15 (blue line with diamond markers), PedA_12/15 (yellow line with triangle markers), VehA_not gated (cyan line with 'x' markers), VehA_9/15 (purple line with 'x' markers), and VehA_12/15 (brown line with circle markers). In both models, the 'not gated' scenario results in a significantly higher RoT overshoot as the number of no-data users increases.](5ae0af74768ab8a326191d61781d98e6_img.jpg) + +Figure 4.2.2.4.5-3: RoT Overshoot as a function of no-data users, different gating patterns and channel models. The figure contains two side-by-side line graphs. The left graph shows Overshoot (RoT>7dB) for channel model PA3, with the y-axis ranging from 0% to 50% and the x-axis from 0 to 55. The right graph shows the same for channel model VA30, with the y-axis ranging from 0% to 24% and the x-axis from 0 to 55. Both graphs compare PedA\_not gated (magenta line with square markers), PedA\_9/15 (blue line with diamond markers), PedA\_12/15 (yellow line with triangle markers), VehA\_not gated (cyan line with 'x' markers), VehA\_9/15 (purple line with 'x' markers), and VehA\_12/15 (brown line with circle markers). In both models, the 'not gated' scenario results in a significantly higher RoT overshoot as the number of no-data users increases. + +Figure 4.2.2.4.5-3: RoT Overshoot as a function of no-data users, different gating patterns and channel models + +##### 4.2.2.4.6 System-level performance with high-velocity UEs + +The simulated radio network consists of 12 three-sector sites (36 cells) with 1.5 km site-to-site distance deployed in an ordinary hexagonal layout. Wrap-around is used to prevent border effects. Standard models for distance attenuation ( $29+35\cdot\log(d)$ where $d$ is distance [m]), shadow fading (lognormal with standard deviation of 8 dB) and, multi-path fading (3GPP Typical Urban) are used. + +A comprehensive WCDMA system model is used. The physical layer models, comprising quality models, measurement models and power control models, have slot-level time resolution. Hybrid ARQ with 8 parallel processes and Chase combining are included. An RLC protocol configured in unacknowledged mode is modeled in detail. + +The speech codec is AMR12.2 and the speech activity is 50%, with on and off periods distributed exponentially. + +Headers are compressed using RoHC (for VoIP) and we assume a constant state where the remaining header size is 3 bytes throughout the simulation. The scheduler is QoS-aware and determines priority based on delay (after a packet has arrived at the buffer). The total time for scheduling and HARQ retransmissions is maximum 100ms. + +Some simulation parameters are given in Table 4.2.2.4.6-1. + +**Table 4.2.2.4.6-1: Simulation parameters used in Figure 4.2.2.4.6-1** + +| Parameter | Value | comments | +|-----------------------------------|-------------------------------------------------|--------------------------------------------------------------------------| +| Path loss Model: COST 231 | $-29.03 - 35.22 \cdot \log_{10}(d)$ | | +| Shadowing standard deviation [dB] | 8 | | +| Propagation Channel | 3GPP Typical Urban | | +| Number of cells | 36 | | +| Cell layout | 3-Cell Clover Leaf | | +| Inter-site Distance [m] | 1500 | | +| Frequency | 2 GHz | | +| EUL TTI length | 2 ms | | +| Receiver Type | RAKE | | +| Max UL HARQ attempts | 5 | | +| Max UL delay threshold | 75 ms | | +| E-DPCCH | Fixed | | +| UL DPCCH CIR target | -22 dB | | +| E-DPCCH power offset | 0 dB | | +| E-DPDCH power offset | 10 dB | | +| HS-DPCCH power offset | 0 dB* | *Sends every 5 th TTI for 3 km/h
Not modelled for 100 km/h | +| EUL Outer Loop | Not modelled | | +| Voice call mean length | 30 seconds | | +| Voice on/off mean length | 2 seconds | | +| RLC SDU size | 280 bits | AMR12.2 + ROHC 3 bytes | +| UE velocity | 3 km/h (for all UEs)
100 km/h (for all UEs)* | *HS-DPCCH not modelled for 100 km/h case | +| VoIP packet arrival interval | 20 ms | | +| Voice activity | 50% | | +| Satisfied user single link | Max 1% PLR @ 95% | | + +Figure 4.2.2.4.6-1 depicts the capacity gain with gating mechanism at the velocities 3 km/h and 100 km/h. The DPCCH update interval is set to every 8th TTI. A 3-slot DPCCH preamble is used before actual data is transmitted. Note that HS-DPCCH is not modeled here. **The relative capacity gain with gating is in the order of 80% for 3 km/h and in the order of 70% for 100 km/h.** + +![Figure 4.2.2.4.6-1: Capacity gain with gating. HS-DPCCH not modeled. A line graph showing 'Satisfied VOIP users, max 1% packet loss at max 75ms delay' on the y-axis (0.75 to 1.0) versus 'Offered Number Of users/cell' on the x-axis (50 to 150). Five curves are shown: Gating ON 1/8, 2ms TTI (solid blue line with circles); Gating ON 1/8, Halted PC, 2ms TTI (dashed red line with triangles); Gating ON 1/8, Halted PC, 2ms TTI, 100km/h (dash-dot magenta line with squares); Gating OFF, 2ms (solid green line with inverted triangles); and Gating OFF, 2ms, 100km/h (dashed cyan line with stars). The Gating OFF, 2ms, 100km/h curve drops sharply after 70 users. The Gating OFF, 2ms curve drops after 70 users. The Gating ON 1/8, Halted PC, 2ms TTI, 100km/h curve drops after 110 users. The Gating ON 1/8, Halted PC, 2ms TTI curve drops after 120 users. The Gating ON 1/8, 2ms TTI curve drops after 140 users. A date '06-Apr-2006' is noted at the bottom left of the graph area.](f455955c4bc84005728b4138f19098dc_img.jpg) + +Figure 4.2.2.4.6-1: Capacity gain with gating. HS-DPCCH not modeled. A line graph showing 'Satisfied VOIP users, max 1% packet loss at max 75ms delay' on the y-axis (0.75 to 1.0) versus 'Offered Number Of users/cell' on the x-axis (50 to 150). Five curves are shown: Gating ON 1/8, 2ms TTI (solid blue line with circles); Gating ON 1/8, Halted PC, 2ms TTI (dashed red line with triangles); Gating ON 1/8, Halted PC, 2ms TTI, 100km/h (dash-dot magenta line with squares); Gating OFF, 2ms (solid green line with inverted triangles); and Gating OFF, 2ms, 100km/h (dashed cyan line with stars). The Gating OFF, 2ms, 100km/h curve drops sharply after 70 users. The Gating OFF, 2ms curve drops after 70 users. The Gating ON 1/8, Halted PC, 2ms TTI, 100km/h curve drops after 110 users. The Gating ON 1/8, Halted PC, 2ms TTI curve drops after 120 users. The Gating ON 1/8, 2ms TTI curve drops after 140 users. A date '06-Apr-2006' is noted at the bottom left of the graph area. + +**Figure 4.2.2.4.6-1: Capacity gain with gating. HS-DPCCH not modeled.** + +(The solid blue curve represents the capacity obtained with UL DPCCH gating if the UL TPC loop could be fully functional also during the gaps.) + +#### 4.2.2.5 UE battery saving calculations + +Following assumptions are used in the simplified UE power saving calculations. + +- 1) The percentage of power saving of tx side and rx side, respectively, for certain tx power level, txpwr, when gating is not used: + - tx side consumes N1 mA @ txpwr + - rx side consumes N2 mA + +No specific data rates were assumed here either in uplink or downlink, for simplification. + +- 2) The tx side power consumption, if tx gating is used: + - tx side consumes N1\_gating mA, during gating @ txpwr +- 3) The rx side power consumption, if discontinuous reception possibility is utilised: + - rx side consumes N2\_gating mA, during gating +- 4) The savings for tx and rx parts power consumption: + +where: + +$$N1\_total\_new = (1 - \text{DPCCH\_gating\_}\%) * N1 + \text{DPCCH\_gating\_}\% * N1\_gating$$ + +$$N2\_total\_new = (1-DRX\_\%)*N2 + DRX\_\%*N2\_gating$$ + +Tables 4.2.2.5-1, 4.2.2.5-2 and 4.2.2.5-3 show the UE tx and rx parts power saving for VoIP and inactive user (in CELL\_DCH) case, for assumptions N1 = 30%, 50% and 70% of the (N1+N2), respectively. Inactive user meaning user that is in CELL\_DCH state, but neither transmitting nor receiving any data. Thus the only difference in calculating the UE tx and rx parts power saving for VoIP with different TTI lengths and inactive user case, is the value used for DPCCH\_gating\_% value. + +0% would mean no saving (same power consumption as with continuous transmission and reception) and 100% would mean that all power is saved and no power consumed. + +**Table 4.2.2.5-1 UE tx and rx parts power saving due to UL DPCCH gating and discontinuous reception in the UE, with assumption of N1=30%\*(N1+N2).** + +| | DPCCH_gating_%
(E-DCH inactivity) | DPCCH activity
during E-DCH
inactivity | DRX_% | UE tx and rx parts
power saving | +|----------------------------------------|--------------------------------------|----------------------------------------------|-------|------------------------------------| +| VoIP 2ms TTI | 85 % | 0% | 0% | 25% | +| | | | 20% | 39% | +| | | | 60% | 68% | +| | | | 80% | 82% | +| | | 10% | 0% | 22% | +| | | | 20% | 36% | +| | | | 60% | 65% | +| | | | 80% | 78% | +| VoIP 10ms TTI | 80% | 0% | 0% | 24% | +| | | | 20% | 38% | +| | | | 50% | 59% | +| | | | 80% | 80% | +| | | 10% | 0% | 21% | +| | | | 20% | 35% | +| | | | 50% | 56% | +| | | | 80% | 77% | +| Inactive user
(in CELL_DCH) | 100 % | 10% | 0% | 27% | +| | | | 50% | 62% | +| | | | 60% | 69% | +| | | | 80% | 83% | +| | | 20% | 0% | 24% | +| | | | 50% | 59% | +| | | | 60% | 66% | +| | | | 80% | 80% | + +**Table 4.2.2.5-2 UE tx and rx parts power saving due to UL DPCCH gating and discontinuous reception in the UE, with assumption of $N1=50\%*(N1+N2)$ .** + +| | DPCCH_gating_%
(E-DCH inactivity) | DPCCH activity
during E-DCH
inactivity | DRX_% | UE tx and rx parts
power saving | +|----------------------------------------|--------------------------------------|----------------------------------------------|-------|------------------------------------| +| VoIP 2ms TTI | 85 % | 0% | 0% | 43% | +| | | | 20% | 53% | +| | | | 60% | 73% | +| | | | 80% | 82% | +| | | 10% | 0% | 38% | +| | | | 20% | 47% | +| | | | 60% | 68% | +| | | | 80% | 77% | +| VoIP 10ms TTI | 80% | 0% | 0% | 40% | +| | | | 20% | 50% | +| | | | 50% | 65% | +| | | | 80% | 80% | +| | | 10% | 0% | 35% | +| | | | 20% | 45% | +| | | | 50% | 60% | +| | | | 80% | 75% | +| Inactive user
(in CELL_DCH) | 100 % | 10% | 0% | 45% | +| | | | 50% | 70% | +| | | | 60% | 75% | +| | | | 80% | 85% | +| | | 20% | 0% | 40% | +| | | | 50% | 65% | +| | | | 60% | 70% | +| | | | 80% | 80% | + +**Table 4.2.2.5-3 UE tx and rx parts power saving to UL DPCCH gating and discontinuous reception in the UE, with assumption of $N1=70\%*(N1+N2)$ .** + +| | DPCCH_gating_%
(E-DCH inactivity) | DPCCH activity
during E-DCH
inactivity | DRX_% | UE tx and rx parts
power saving | +|----------------------------------------|--------------------------------------|----------------------------------------------|-------|------------------------------------| +| VoIP 2ms TTI | 85 % | 0% | 0% | 60% | +| | | | 20% | 66% | +| | | | 60% | 77% | +| | | | 80% | 83% | +| | | 10% | 0% | 53% | +| | | | 20% | 59% | +| | | | 60% | 71% | +| | | | 80% | 77% | +| VoIP 10ms TTI | 80% | 0% | 0% | 56% | +| | | | 20% | 62% | +| | | | 50% | 71% | +| | | | 80% | 80% | +| | | 10% | 0% | 49% | +| | | | 20% | 55% | +| | | | 50% | 64% | +| | | | 80% | 73% | +| Inactive user
(in CELL_DCH) | 100 % | 10% | 0% | 63% | +| | | | 50% | 78% | +| | | | 60% | 81% | +| | | | 80% | 87% | +| | | 20% | 0% | 56% | +| | | | 50% | 71% | +| | | | 60% | 74% | +| | | | 80% | 80% | + +### 4.2.3 Benefits of the concept + +- Less air interface capacity consumption per UE due to reduced UL DPCCH and F-DPCH noise contribution and therefore also increased UE battery life time compared to REL-6.\* +- Compared to REL-6: Increased number of temporarily inactive users that can stay in CELL\_DCH and that can therefore get active in a very short time avoiding frequent transitions to CELL\_FACH.\* +- Concept is intended to address also VoIP users between packet transmissions. + +\*: Better than for “SIR\_target reduction” the more UL DPCCH is gated. + +### 4.2.4 Open issues of the concept + +- Impact on inner loop power control in UL & DL. +- How often/when will UL DPCCH and F-DPCH be sent for inactive users (how are the activity patterns designed?) in order to maintain power control stability and synchronisation status. +- How is reactivation started and the UL DPCCH power set after each UL DPCCH and F-DPCH gating gap? Longer power ramping needed? +- Modifying the CQI reporting for HSDPA from Release 6 could enable higher gains for Uplink DPCCH Gating. +- DL & UL have to be inactive at the same time during UL DPCCH gating. +- Impact on power balancing mechanism. (Note: This is not an issue if TPC based power control is not applied to F-DPCH/DPCCH.) + +## 4.3 SIR\_target reduction + +### 4.3.1 Description of the concept + +The proposed concept has the goal of substantially reducing the Tx power of the UL DPCCH (and thus, the generated noise rise) by reducing SIR\_target during idle traffic periods, i.e. when nothing needs to be transmitted in UL on the E-DPDCH. + +It is an important characteristic of the concept that these changes do not involve the RNC, so that the long delays of RRC or NBAP procedures (>> 100ms) are avoided and the user is staying in CELL\_DCH state. + +The "SIR\_target reduction" could be carried out by e.g.: + +- L1 signalling: Serving Node B controls when a UE is going into an inactive phase with a lower SIR\_target and corresponding L1 signalling is used to trigger deactivation & reactivation. +- L2 signalling: The UE controls by L2 MAC-e signalling when the SIR\_target in the NodeBs of the active RLS is reduced, i.e. deactivation & reactivation. +- Predefined/configured rules: Serving NodeB detects inactivity and activity based on pre-defined or configured rules and reduces the SIR target by a pre-defined or configured offset during periods of inactivity. + +#### 4.3.1.1 L1 signalling approach + +##### Traffic inactivity detection: + +The absence of data to be transmitted on E-DCH in the UL can be detected by observing the current occupation of the MAC-e buffer which is known by the MAC-e scheduler in the Node B through scheduling information received from the UE. A deactivation start timer/timeout (starting when a buffer runs empty) can be used to avoid unnecessary switching between active and inactive mode during very short traffic intermissions. + +##### SIR\_target reduction: + +When detecting the inactivity condition in the UL, the serving Node B reduces the target SIR for the UL power control from the last RNC-configured value to a pre-determined target value (for reliable TPC detection). The inner loop power control for the uplink will automatically reduce the Tx power of the UE on the UL DPCCH (by a sequence of 'power down' steps) to adjust to the new target. This autonomous reduction of the SIR target is not in conflict with the outer loop power control of the SRNC, as the transmitted power will not be permitted to become higher than the RNC-configured value. In the following text such a phase of reduced Tx power on UL DPCCH during the inactive traffic phase is also called 'reduced power mode'. + +The serving Node B informs the UE about the change by physical layer signalling. This can be implemented as a new signalling message on the HS-SCCH, using one of the 8 unused bit combinations within the 7 bits assigned to the channelization code set. + +The SIR\_target reduction with L1 signalling is considered applicable even when a transmission on HSDPA is still active (and therefore the transmission of the HS-DPCCH takes place). To assure the reliable operation of HSDPA after the SIR\_target reduction, a mechanism to compensate the UL DPCCH TX power lowering should be introduced. The application of a power offset on HS-DPCCH is analyzed for non-SHO and for CQI reports in section 4.3.2.6.x. An application of a power offset on UL DPCCH is ffs. + +One of the methods to inform UE about HS-DPCCH power offset to DPCCH value change is to utilize HS-SCCH signalling. In this approach the Node B has the possibility to send the new and exact value of the power offset to the UE. This procedure will assure a reliable transmission on the HS-DPCCH while applying the SIR\_target reduction concept to DPCCH. + +##### Triggering reactivation: + +When a UE is in a 'reduced power mode' a reactivation is triggered by the arrival of new data in the MAC queue. New data for UL in the MAC-e buffer will first be detected in the UE and must be brought to the attention of the serving Node B. 2 alternatives are (preference for the second): + +1. HARQ with possible UL power offset: + +The UE immediately transmits a MAC-e PDU as it would do in the normal E-DCH configuration. Note that the + +E-DPCCH and E-DPDCH are transmitted with a given power offset from the DPCCH power, and will therefore be power-reduced, when the DPCCH is power-reduced. As a mere trigger for reactivation it is, however, not necessary that the initial transmission can be correctly detected in the receiving Node B. It is sufficient that signal presence is recognized by the Node B at all, since this would trigger the Node B to restore the usual UL power control and the corresponding HARQ would avoid any loss of data. + +For even better robustness of this reactivation trigger a power offset could be applied for the first transmission on E-DPCCH and E-DPDCH at the end of the 'reduced power mode'. This would give the first MAC-e PDU a fair chance to be correctly decoded, in which case no reactivation delay would occur at all. + +##### 2. Reactivation signal on E-DPCCH: + +Another option is that the UEs are not allowed to transmit E-DPDCH and E-DPCCH in 'reduced power mode' at all, except for a reactivation signal on the E-DPCCH. For instance, the UE just sets the 'Happy Bit', or it transmits a predefined 10-bit sequence on the entire E-DPCCH. The Node B restores the SIR target and initiates the reactivation via HS-SCCH signalling. Such a trigger via E-DPCCH would be very easy and reliable to detect (if required, a power offset as aforementioned could also be applied). As soon as the UE receives the HS-SCCH confirmation from the Node B (will take less than 10ms) the UE returns back to normal operation. + +##### Restoring normal power control for data transmission: + +When the serving Node B recognizes a new transmission on E-DPCCH and/or E-DPDCH from the UE in 'reduced power mode', it starts the reactivation by resetting the target SIR for the UL power control to the last RNC-configured value. The inner loop PC will automatically re-adjust the Tx power on the UL DPCCH to the new target within a few time slots. + +Depending on the considered reactivation improvements (see Triggering reactivation above), the Node B will also send a reactivation message to the UE (via HS-SCCH), and the UE will restart regular transmissions. + +Retransmission(s) of the first packet, and possible transmissions of subsequent (non-scheduled) MAC-e PDUs will be automatically executed by the normal HARQ and E-DCH protocols in the UE and serving Node B. Depending on the TTI length, it may take one (for 10ms TTI) or a few TTIs (for 2ms TTI) before the power control has settled on the normal level (if no power offset is applied). In such a case the Node B may delay large rate grants to the UE, until the received signal power has reached the target SIR, in order to avoid early erroneous transmission of large scheduled PDUs. + +##### 4.3.1.1.1 Interworking aspects + +###### Cell changes and Soft Handover: + +Measurement reports from the UE and RNC-triggered signalling of changes in the active set and changes of the serving Node B will be transmitted on SRB over E-DCH and HS-DSCH, and thereby trigger reactivation. Therefore the highest gain of this concept is achieved when the reporting interval of such mobility measurements is well above the timeout parameter that triggers the deactivation. + +SHO may be applied on UL DPCCH. Nevertheless, either the serving cell will dominate the UL power control due to the SIR target reduction or a change of the serving cell will be initiated by the RNC in the normal way (i.e. as in the current specifications) and trigger a reactivation of the UE. + +In case of SHO, the radio links of non-serving NodeBs would not reduce their SIR target (as done in the serving NodeB) and these radio links might cause a RL FAILURE. As a RL\_FAILURE report will not occur before T\_RLFAILURE timer has elapsed (ranged from around 10ms to 28 sec), this problem occurs only for longer inactivity periods than T\_RLFAILURE setting, which is configured by RNC. For such cases the following options are considered to address the problem: + +- (A) The SIR target during the reduced power mode is periodically boosted in the serving Node B to a pre-determined value (less than or equal to a 'normal' SIR target) in order to achieve sufficient in-sync indications of radio links from non-serving NodeBs and to avoid RL FAILURE indications. The length of these temporary boosting periods (e.g. a few radio frames) and the periodicity (e.g. similar value to "T\_RLFAILURE" setting) of the temporary boosting periods is indicated by RNC. The ranges of those parameters as well as the definition of the boosted SIR target are FFS. +- (B) RNC is allowed to set a limit of the lowered SIR target (minimum SIR target) and NodeB can decide about the value of the lowered SIR target in the range between the minimum SIR target and the 'normal' SIR target. With the setting of a minimum SIR target, the RL\_FAILURE probability from non-serving NodeB can be reduced. As a special setting for SHO, the minimum SIR target could be set to the normal target SIR, which means that + +RNC could restrict the applicability of the SIR target reduction for SHO. The definition of a limit set by RNC is FFS. + +- (C) RNC could ignore RL\_FAILURE from non-serving NodeB(s) when the RL\_FAILURE is assumed to be triggered due to the SIR target reduction by serving NodeB. The RNC could decide this based on the information available at the RNC such as Node B and UE ability to apply CPC mode, whether the considered UE is in SHO or not, whether the link(s) of the serving Node B have no RL\_FAILURE and UL/DL traffic activity of the UE. Note that although the radio link(s) for non-serving NodeB can be maintained by ignoring RL\_FAILURE, the radio link may be kept in out-of-sync state at non-serving NodeB. + +###### Reporting power gains to RNC: + +As it is the goal of the proposed concept to allow more users to get and remain connected (without the need for intermediate RRC state switching), it is necessary that the RNC is made aware of the savings in the received noise rise, so that these can be taken into account in decisions e.g. for call admission and RRC state switching. These gains will, however, automatically be reflected in the measurements of "total received wideband power", which are periodically reported from Node B to CRNC, anyway. Thus, no changes to the standard measurement reporting are required for this purpose. + +##### 4.3.1.1.2 Handling of VoIP traffic + +VoIP traffic in UL is assumed to follow a predictable pattern of voice packets and silence descriptors (SID) and also the timing of HARQ retransmissions is under control of the Node B. + +By setting a standard rule that the UL DPCCH SIR\_target reduction is applied in the Node B between voice packets, between SIDs, as well as between voice packets and SIDs, the same SIR\_target reduction scheme as in section 4.3.1.1 can be applied for VoIP services but with a reduced L1 signalling. + +Note: For HARQ retransmissions the SIR\_target would also be set back to normal as for voice packets and SIDs. + +Only for restarting VoIP transmissions at the UE after longer speech pauses L1 signalling in form of an E-DPCCH sequence would be used which would be confirmed by HS-SCCH signalling from the Node B. + +For the case that DL is active and UL is temporarily inactive a power offset on HS-DPCCH and/or DPCCH might be applied to compensate for SIR\_target reduction. The details of this power offset application are ffs." + +Parallel smaller unscheduled transmissions like SRBs should be started directly before or after a voice packet or a SID where SIR\_target is almost unchanged. + +For other packet traffic in addition to VoIP the SIR\_target reduction as described above would only be applied by the Node B if this other packet traffic is inactive, i.e. if no packets for the other packet traffic are transmitted. + +![Figure 4.3.1.1.2-1: Illustration of an ideal SIR_target reduction profile for VoIP packets every 20ms. The graph shows SIR (R) on the y-axis and time (TTI) on the x-axis. The y-axis has labels for 'SIR target (for VoIP)', 'Reduced', and 'SIR target'. The x-axis has labels for '1', '2', and '4' TTI. A red line represents the 'actual SIR', which drops from the target to the reduced level during inactive phases and returns to the target during active phases. A blue dashed line represents the 'Node B' target, which follows the actual SIR. Three VoIP packets are shown as green rectangles at the top, corresponding to active periods.](c21fe89d8034ec5b80bd47c1cd710202_img.jpg) + +Figure 4.3.1.1.2-1: Illustration of an ideal SIR\_target reduction profile for VoIP packets every 20ms. The graph shows SIR (R) on the y-axis and time (TTI) on the x-axis. The y-axis has labels for 'SIR target (for VoIP)', 'Reduced', and 'SIR target'. The x-axis has labels for '1', '2', and '4' TTI. A red line represents the 'actual SIR', which drops from the target to the reduced level during inactive phases and returns to the target during active phases. A blue dashed line represents the 'Node B' target, which follows the actual SIR. Three VoIP packets are shown as green rectangles at the top, corresponding to active periods. + +Figure 4.3.1.1.2-1 Illustration of an ideal SIR\_target reduction profile for VoIP packets every 20ms (HARQ retransmission and inactive phases with SIDs are not shown in this example) + +#### 4.3.1.2 L2 signalling approach + +##### Traffic inactivity detection: + +The UE detects autonomously the conditions for a transition into the idle traffic mode, i.e. inactivity in the UL. The conditions for a transition into the idle traffic mode could involve no activity for a certain minimum period of time in UL (and DL). + +When the UE has detected a transition from active mode into “idle traffic mode” or vice versa, it can instantaneously apply the corresponding power control parameters with respect to DPC\_MODE and power control stepsize (see below). The NodeBs in the active RLS need to be notified by the UE of the idle traffic mode so that the NodeBs can operate with the changed parameter settings in this mode, i.e. changed inner loop power control parameters with respect to SIR target and DPC\_MODE and power control stepsize. + +The UE will inform the NodeBs about a change from active mode into idle traffic mode and vice versa by means of a short MAC-e PDU consisting of scheduling information (SI). For the change from active mode into idle traffic mode, a specific SI reserved for that purpose is transmitted and repeated through HARQ retransmissions until all NodeBs in serving and non-serving RLS have acknowledged receipt of the transition or the maximum number of transmissions is reached. + +##### SIR\_target reduction: + +Upon transition of the UE into the idle traffic mode, the target SIR in the Node Bs of the active RLS for the UL power control is reduced from the last RNC-configured value to a pre-determined target value (for reliable TPC detection). The inner loop power control for the uplink will automatically reduce the Tx power of the UE on the UL DPCCH (by a sequence of 'power down' steps) to adjust to the new target SIR. + +The robustness of the connection with a particular UE in idle traffic mode can be improved as follows: + +- The UE modifies its UL power control by applying a higher step size when receiving a 'power up' TPC command on the DL DPCCH. This will keep the power control more stable when the error rate on the UL DPCCH increases. +- The UE uses DPC\_MODE=1, i.e. the TPC commands on the UL DPCCH (for the downlink) are repeated in 3 successive timeslots. This achieves higher detection reliability in the Node B at the expense of a slower power adjustment to match changing channel conditions, which is assumed to be acceptable during idle traffic periods. The resulting reduction in the rate for forward link power control of the F-DPCH (from 1500 Hz down to 500 Hz) is not considered to be crucial. + +When the NodeB has detected a transition from active mode into “idle traffic mode” or vice versa, it can instantaneously apply the corresponding power control parameters with respect to SIR target and DPC\_MODE and continue. + +##### Triggering reactivation: + +When the UE is in idle traffic mode, it is required that the NodeB watches for a reactivation of the UE, i.e. a transition from idle traffic mode into the active mode. + +The UE can trigger autonomously the reactivation when data is to be transmitted in the uplink. For the change from idle traffic mode into active mode, the actual SI is transmitted and repeated through HARQ retransmissions until all NodeBs in serving and non-serving RLS have acknowledged receipt of the transition. + +For a reliable transmission of the SI while the UE is still in the idle traffic mode, the UE could temporarily increase the DPCCH power (and, hence, also the E-DCH power) in an open loop power adjustment for the time of the SI transmission. + +##### Specific L2 signalling aspects: + +The reserved MAC-e SI for indicating a transition can have its own HARQ profile with an additional power offset to ensure reliable detection by all NodeBs in the active set with reasonable latency. The SI word specific for the transition from active mode into idle traffic mode conveys UE buffer occupancy of 0 (9 bits), maximum possible power ratio versus DPCCH (5 bits) and a pre-defined logical channel ID (4 bits). While a pre-defined logical channel ID is given in the SI word specific for the transition from active mode into idle traffic mode, it may be noted that the transition is valid for all logical channel IDs. + +##### 4.3.1.2.1 New parameters for L2 signalling approach + +| Parameter | Description | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Inactivity time | minimum time of inactivity on UL and DL before the UE can trigger a transition into the idle traffic mode | +| Power offset | 1) difference in Target SIR between active and idle traffic mode
2) UE open loop power adjustment for the transmission of the SI for triggering a transition from idle traffic mode to active mode | +| SI for transition into idle traffic mode | Dedicated and reserved SI that is only used to signal the transition into the idle traffic mode | + +#### 4.3.1.3 Approach with predefined/configured rules + +Instead of relying on signalling, predefined (and standardized) rules can be used to control the UE and Node B behaviour, i.e., the UE and Node B could by applying these rules have a consistent view of whether 'normal' or 'reduced' activity transmission should be used. + +In uplink, the (serving) Node B will notice whether the UE is transmitting any data in the uplink or not. When the UE has not transmitted any data within a predefined time interval $\Delta T$ , the (serving) Node B can estimate that the UE has no data in the buffer and lower the SIR target by $z$ dB in the power control loop to reduce the interference from that UE. In order to reach the lower, more efficient SIR level faster, the UE could simultaneously apply a negative power offset $w_1$ (possibly but not necessarily equal to $-z$ dB) to its transmission. + +Note: In the special case that the transmission follows an entirely predictable pattern, which might be the case for VoIP traffic (this is FFS), $\Delta T$ could be set to zero, resulting in an immediate SIR target reduction after each VoIP packet. + +If data enters the UE buffer when the SIR target is lowered, the UE will according to the current specification transmit scheduling information in the uplink. A power offset $w_2$ can be used for the transmission of uplink scheduling information to compensate for the lowered SIR target. This is possible already in Rel6 using the HARQ profiles. + +Note: The need for Node B receiver resources could be reduced. Methods are FFS; see e.g. Tdoc R1-051448, 'Opportunities for resource saving in the Node B receiver'. + +The Node B will detect the presence of scheduling information after one or a few HARQ retransmissions (if the power offset $w_2$ is appropriately set, the first attempt is likely to succeed). Once the Node B detects the presence of the + +scheduling information, the SIR target is restored to its normal level and the inner power control loop will ensure that the UE after a couple of slots has adjusted its transmission power to meet the target. + +Note: In the special case that the transmission follows an entirely predictable pattern, which might be the case for VoIP traffic (this is FFS), the Node B knows when to restore the SIR target without detecting the presence of scheduling information. + +The SIR\_target reduction is considered applicable even when a transmission on HSDPA is still active (and therefore the transmission of the HS-DPCCH takes place). To assure the reliable operation of HSDPA after the SIR\_target reduction, a mechanism to compensate the UL DPCCH TX power lowering should be introduced. The introduction of a new power offset for DPCCH and/or HS-DPCCH is FFS. + +For example, the SIR level could be temporarily restored during the transmission of a CQI report (possibly also during a few slots before the CQI report for e.g. improved channel estimation). Thus, when the CQI reporting pattern dictates that the UE should transmit a CQI and that Node B should receive a CQI, the UE could apply a positive power offset to its transmission and Node B could apply the same offset to its SIR target. + +The ways of handling cell changes and soft handover described for the L1 signalling approach in sub-clause 4.3.1.1.1 are equally applicable for the approach with predefined/configured rules. + +To implement the above mechanisms, higher layer signalling between the RNC and the UE is required to configure the time interval $\Delta T$ and the power offsets $w_1$ and $w_2$ . This signalling typically only takes place once at call setup and thus does not lead to a significant increase in interference. Signalling is also required between the RNC and Node B to configure the SIR target reduction $z$ . + +### 4.3.2 Analysis of the concept + +#### 4.3.2.1 Simulation of the concept + +The aim of this analysis is to show to which value the SIR target of the UL DPCCH can be reduced during the inactivity phase without losing the stability of the inner loop power control (IL PC). + +Reducing the SIR target for the UL in the Node B could make the reception of the power control commands (TPC) on the UL DPCCH more erroneous, which in turn could make the DL power control less reliable. Therefore the reception of the TPC on the F-DPCH may be more erroneous, requiring extra downlink power. Thus, the criterion to identify the maximum UL SIR target reduction is given by the increase of DL power per F-DPCH, required to maintain a desired F-DPCH TPC error rate (4% is usually considered). + +Furthermore the simulation results show the expected time required to ramp up the UL DPCCH power to the initial SIR target when detecting the user activity. + +##### 4.3.2.1.1 Simulation assumptions + +The assumed channels are: AWGN, Vehicular A at 3km/h, 30km/h and 120km/h and a Rayleigh channel with one path at 3km/h. All the considered channels are at the carrier frequency of 2GHz and channel estimation is applied in the receiver. + +The power control timing follows the 25.214 v6.7.0 Annex B, operation with F-DPCH. It is assumed that the UE is able to react to a TPC command with a power adjustment in the immediate next slot and the Node B reacts with an extra slot delay (it is assumed here that the F-DPCH is used in the DL). It is also assumed that the UE and Node B are capable of generating a TPC command in the immediate next slot (in UL/DL) according to the SIR measurements of the previous slot in the DL or UL, respectively. + +The simulation assumption for UL and DL are listed in Table 4.3.2.1.1.-1 and 4.3.2.1.1.-2 respectively. + +**Table 4.3.2.1.1-1 Uplink simulation assumptions** + +| Parameter | Value | +|--------------------------------------------------------------------------|--------------------------------------------------| +| DPCCH_E c _MAX – maximum transmitted DPCCH energy per PN chip | Not limited | +| DPCCH_E c _MIN – minimum transmitted DPCCH energy per PN chip | Not limited | +| Slot format | 2 TPC bits, 8 Pilot bits-(slot format 1), SF 256 | +| Inner loop PC | On, minimum delay 1 slot (PC algorithm 1) | +| Inner loop PC range | Not limited | +| Inner loop PC step size | 1dB | +| Outer loop PC | Off | +| RX diversity | Reception with two antennas | +| Channel estimation | From dedicated pilots | + +**Table 4.3.2.1.1-2 Downlink simulation assumptions** + +| Parameter | Value | +|--------------------------------------------------------------------------|----------------------------------------| +| geometry | 3dB | +| I OR – cell total transmit power | 43dBm | +| DPCH_E c _MAX - maximum transmitted F-DPCH energy per PN chip | 30dBm | +| DPCH_E c _MIN - minimum transmitted F-DPCH energy per PN chip | 5dBm | +| Slot format | F-DPCH - 2 TPC bits, SF 256 | +| Inner loop PC | On, minimum delay 2 slots (DPC_MODE 0) | +| Inner loop PC range | 25dB | +| Inner loop PC step size | 1dB | +| TPC error rate target | 4% | +| Outer loop PC | On (based on DL TPC errors) | +| Outer loop PC step size | 0.3dB | +| Outer loop PC frequency | 100Hz | +| Channel estimation | From CPICH | + +##### 4.3.2.1.2 Simulation results + +From Figure 4.3.2.1.2-1 which shows F-DPCH\_Ec/Ior vs. the UL DPCCH SIR target it can be seen that when lowering the UL DPCCH SIR target down to -5dB, the transmitted F-DPCH energy per PN chip required to maintain the DL TPC error rate at 4% increases by a very small amount (<0.6dB) in presence of different propagation conditions and channel estimation. This means that despite of UL TPC errors of about 15% (for flat fading, AWGN – Figure 4.3.2.1.2-2) and 20% (for Veh A3, Veh A30 – Figure 4.3.2.1.2-2) the DL inner loop power control is kept stable although the SIR target for the UL DPCCH is reduced. The SIR\_target before applying a reduction depends on the considered type of service. The higher the data rate of the service the higher the SIR\_target and the larger can be the SIR\_target reduction. So for higher data rates (SIR\_target >0dB) SIR\_target reductions of even more than 6dB are possible. + +![Figure 4.3.2.1.2-1: DL F-DPCH Ec/Ior vs. UL DPCCH SIR target. This line graph plots DPCH_Ec/Ior [dB] on the y-axis (ranging from -26 to -16) against UL SIR target [dB] on the x-axis (ranging from -13 to 13). Five scenarios are plotted: AWGN (solid black line, lowest at ~-25dB), Flat Fading; 3[kmh] (solid red line), VehA3 (dashed blue line), VehA30 (dash-dot green line), and VehA120 (dashed magenta line, highest starting point). All fading curves show a downward trend as SIR target increases from -13 to -5 dB, then stabilize between -19 and -21 dB.](8e21461e0c9384ec60322bedb1b1ab17_img.jpg) + +Figure 4.3.2.1.2-1: DL F-DPCH Ec/Ior vs. UL DPCCH SIR target. This line graph plots DPCH\_Ec/Ior [dB] on the y-axis (ranging from -26 to -16) against UL SIR target [dB] on the x-axis (ranging from -13 to 13). Five scenarios are plotted: AWGN (solid black line, lowest at ~-25dB), Flat Fading; 3[kmh] (solid red line), VehA3 (dashed blue line), VehA30 (dash-dot green line), and VehA120 (dashed magenta line, highest starting point). All fading curves show a downward trend as SIR target increases from -13 to -5 dB, then stabilize between -19 and -21 dB. + +Figure 4.3.2.1.2-1 DL F-DPCH $E_c/I_{or}$ vs. UL DPCCH SIR target + +![Figure 4.3.2.1.2-2: UL TPC error rate vs. UL DPCCH SIR target. This line graph plots UL TPC error rate on a logarithmic y-axis (from 10^0 down to 10^-6) against UL SIR target [dB] on the x-axis (from -13 to 13). The same five scenarios are plotted: AWGN, Flat Fading 3kmh, VehA3, VehA30, and VehA120. All curves start near 10^-1 at -13dB and decrease as the SIR target increases. AWGN (black) decreases fastest, reaching 10^-5 around 5dB. VehA120 (magenta) decreases slowest, reaching 10^-5 around 13dB.](318f02285df33c4d38cdad30845972d4_img.jpg) + +Figure 4.3.2.1.2-2: UL TPC error rate vs. UL DPCCH SIR target. This line graph plots UL TPC error rate on a logarithmic y-axis (from 10^0 down to 10^-6) against UL SIR target [dB] on the x-axis (from -13 to 13). The same five scenarios are plotted: AWGN, Flat Fading 3kmh, VehA3, VehA30, and VehA120. All curves start near 10^-1 at -13dB and decrease as the SIR target increases. AWGN (black) decreases fastest, reaching 10^-5 around 5dB. VehA120 (magenta) decreases slowest, reaching 10^-5 around 13dB. + +Figure 4.3.2.1.2-2 UL TPC error rate vs. UL DPCCH SIR target + +The simulation result depicted in Figure 4.3.2.1.2-3 shows that the UL DPCCH ramp up time, when restoring the UL SIR target lowered to -3dB, is on average well below 12ms (depending on the initial UL SIR target). For realistic UL SIR target reductions (e.g. about 6dB) it can be assumed that this ramp up is finalized well before the first HARQ retransmission. This means that the considered requirement for the reactivation delay (lower than 50ms) can be fulfilled. + +![Line graph showing Reactivation time [ms] vs. initial UL DPCCH SIR target [dB]. The graph title is 'flat fading; velocity = 30 [km/h]; geometry = -3 [dB]'. The x-axis ranges from -3 to 13 dB, and the y-axis ranges from 6 to 24 ms. The curve shows a general upward trend, starting at approximately 8 ms at -3 dB and reaching about 19 ms at 12 dB, with a slight dip around 6 dB.](e466e4c4fb08567a109bb959a765225c_img.jpg) + +| UL SIR target [dB] | time [ms] | +|--------------------|-----------| +| -3 | 8.0 | +| -2 | 9.5 | +| -1 | 9.8 | +| 0 | 10.5 | +| 1 | 11.2 | +| 2 | 11.8 | +| 3 | 12.5 | +| 4 | 13.8 | +| 5 | 14.5 | +| 6 | 14.2 | +| 7 | 15.2 | +| 8 | 15.8 | +| 9 | 16.8 | +| 10 | 17.0 | +| 11 | 17.5 | +| 12 | 19.5 | +| 13 | 19.2 | + +Line graph showing Reactivation time [ms] vs. initial UL DPCCH SIR target [dB]. The graph title is 'flat fading; velocity = 30 [km/h]; geometry = -3 [dB]'. The x-axis ranges from -3 to 13 dB, and the y-axis ranges from 6 to 24 ms. The curve shows a general upward trend, starting at approximately 8 ms at -3 dB and reaching about 19 ms at 12 dB, with a slight dip around 6 dB. + +Figure 4.3.2.1.2-3 Reactivation time vs. initial UL DPCCH SIR target + +#### 4.3.2.2 Noise rise caused by UL DPCCH + +The goal of this section is to assess the portion of the UL noise rise due to the UL DPCCH in typical E-DCH configurations. + +The analysis is based on the recent E-DPDCH demodulation performance tests, introduced in RAN4 (see e.g. R4-050547). The results include the total receiver $E_c/N_0$ (including DPCCH, E-DPDCH and E-DPCCH), required to achieve 70% of the maximum bit rate for a number of fixed reference channels (FRCs). This corresponds to BLER of 30%. + +Table 4.3.2.2-1 shows SIR target for UL DPCCH for each FRC and the value $p$ which is the percentage of own cell noise rise which is caused by one user's UL DPCCH. $p$ is calculated for two usually considered RoT budgets: 3dB and 6dB, what corresponds to the 50% and 75% of the pole capacity. + +The following can be observed: + +- The tendency is for $p$ to increase as throughput increases. +- The DPCCH uses between about 0.8% and 4.6% of the UL resources, depending on FRC and RoT budget. + +**Table 4.3.2.2-1 Numerical results for $p$ (=UL noise rise percentage per UL DPCCH) and SIR target for different fixed reference channels (FRC), which are to be defined in TS 25.104.** + +| FRC# | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +|---------------------------------------------|--------|--------|--------|-------|-------|--------|-------| +| max. bit rate [kbps] | 1353.0 | 2706.0 | 4059.0 | 507.6 | 979.8 | 1959.6 | 69.0 | +| results for 70% of max. bit rate (30% BLER) | | | | | | | | +| total Ec/N0 [dB] | -4.7 | -1.5 | -0.2 | -9.7 | -7.3 | -4.4 | -18.1 | +| SIR_DPCCH [dB] | 9.7 | 11.9 | 12.8 | 7.6 | 7.4 | 9.4 | 1.2 | +| $p$ [%] for 3dB noise rise | 3.72 | 4.44 | 4.62 | 2.97 | 2.56 | 3.38 | 0.78 | +| $p$ [%] for 6dB noise rise | 2.48 | 2.96 | 3.08 | 1.98 | 1.70 | 2.26 | 0.52 | + +#### 4.3.2.3 Potential gain in terms of number of additional users & UL noise rise + +The potential gain that can be achieved by a power reduction of the uplink control channels for inactive users can best be measured by the number of inactive user connections that can be maintained within a fixed fraction of the allowed noise rise. This fraction must be small, as it limits the resources available for user data transmission, but it also must be large enough to accommodate a sufficient number of temporarily inactive users that can be quickly scheduled when resources become free. + +Example scenario: 5 active users and a control channel configuration with 1% of the max. allowed noise rise per UL DPCCH, plus 0.67% per HS-DPCCH at full CQI rate. These 5 active users will occupy 8.35% (= 5 x 1.67%) of the noise rise budget with their uplink control channels and thus, would have a maximum of 91.65% available for data traffic – if no inactive users were allowed. + +![Diagram comparing current UL noise situation (now) with a proposed scheme. The diagram shows two vertical rectangles representing the total UL noise budget. The 'now' rectangle is divided into a top 'Traffic channels' section and a bottom 'UL Ctrl channels of N active and M inactive users' section. The 'proposal' rectangle is also divided into a top 'Traffic channels' section and a bottom section for control channels. The bottom section is further divided into 'UL Ctrl channels of X inactive users' and 'UL Ctrl channels of N active users'. Brackets on the right indicate that the top section represents 80% of the total noise and the bottom section represents 20%. An arrow on the left points upwards, labeled 'UL noise'. Below the diagram, text states: 'Same number of active users N but extended number of inactive users: X >> M'.](6334c962f5e106e3331e59946e4d166e_img.jpg) + +Same number of active users N but extended number of inactive users: **X >> M** + +Diagram comparing current UL noise situation (now) with a proposed scheme. The diagram shows two vertical rectangles representing the total UL noise budget. The 'now' rectangle is divided into a top 'Traffic channels' section and a bottom 'UL Ctrl channels of N active and M inactive users' section. The 'proposal' rectangle is also divided into a top 'Traffic channels' section and a bottom section for control channels. The bottom section is further divided into 'UL Ctrl channels of X inactive users' and 'UL Ctrl channels of N active users'. Brackets on the right indicate that the top section represents 80% of the total noise and the bottom section represents 20%. An arrow on the left points upwards, labeled 'UL noise'. Below the diagram, text states: 'Same number of active users N but extended number of inactive users: X >> M'. + +**Figure 4.3.2.3-1 UL noise situation with the current standard (now) and with the proposed scheme assuming a limited UL noise for control (Ctrl) channels** + +In the reference scenario (see Figure 4.3.2.3-1) it is assumed, that 20% of these traffic resources (i.e. $20\% \times 91.65\% = 18.33\%$ of the max. allowed noise rise) are reserved for uplink control channels of additional inactive users. This would allow for a maximum of 11 ( $18.33\% / 1.67\%$ ) inactive users with CQI reporting per 2ms TTI. + +By reducing the control channel power for these inactive users, a substantially larger number of inactive users can be supported with the same amount of resources, i.e. without degrading the maximum total throughput of the 5 active users. + +In case of an SIR target reduction by 6dB, the number of inactive users that can be supported within the given noise rise budget increases from 11 to 44, i.e. by a factor of 4. In a more conservative scenario – SIR target reduction by 4.5dB and a CQI reporting cycle of 4 TTIs – the number of inactive users can still be increased from 16 to 44, i.e. a gain factor of 2.75. + +#### 4.3.2.4 Reactivation delay + +Although the first transmission after reactivation is much faster with this concept than it would be considering an RRC state change, it includes a small reactivation delay compared to an always active user (note: Due to the UL noise rise limitation the number of the active users is limited.) + +A simple analysis shows that this additional delay (before normal scheduling and transmission behavior of E-DCH or HS-DSCH applies) is well below 50 ms even in the worst case, when the extra retransmission is needed. + +The time for uplink reactivation comprises the transmission of the initial MAC-e PDU or E-DPCCH trigger signal, the transmission of the reactivation message on HS-SCCH, the power ramping to the original target SIR at the Node B, and the time for the first transmission (or retransmission) at the full power level. + +In the worst case (10 ms EDCH TTI), the total delay is dominated by the HARQ cycle, which allows a retransmission only after 40 ms. The HS-SCCH signalling message and the subsequent power ramping takes only a few power control slots and will therefore be finished well before the retransmission time. + +With the 2 ms EDCH TTI, the HARQ retransmission cycle is only 16 ms, thus the reactivation can be achieved much faster. + +#### 4.3.2.5 Signalling load + +Considering the L1 signalling approach: + +- the HS-SCCH capacity of 500 messages per sec (1 every 2ms), +- the fact that a UE has to be able to read 4 HS-SCCHs in parallel, +- the case that one HS-SCCH message would be used for deactivation and a second HS-SCCH message would be used for reactivation, +- an average inactivity period of 5sec, + +even a high number of inactive users (e.g. 80) would have only a smaller impact on the HS-SCCH signalling load ( $(80 \times (2 \text{ msg}/5\text{sec})) / (2000 \text{ msg/sec}) = 1,6\%$ ). + +#### 4.3.2.6 CQI Performance for boosting HS-DPCCH power offset to DPCCH + +This section presents some CQI over the HS-DPCCH link level results in non-SHO, and further discusses the feasibility of beta boosting and the possibility to keep the HSDPA downlink active during SIR target reduction. + +##### 4.3.2.6.1 Simulations assumptions + +Table 4.3.2.6.1-1 lists the most important simulations conditions of the evaluation. In the simulation the SIR target is swept and, the CQI error rate is examined for various HS-DPCCH power offsets to the DPCCH. The SIR target is the operation point of uplink inner loop power control [6], inner loop power control uses SIR measurements as per [7]. + +Table 4.3.2.6.1-1 Simulation assumption + +| Parameter | Value | +|--------------------------------------|-------------------------------------------------------------------------------------| +| SIR target | Variable | +| $A_{hs} = \beta_{hs} / \beta_{c\_c}$ | 15/15, 24/15, 30/15 – this gives HS-DPCCH power offset to DPCCH of 0 dB, 4 dB, 6 dB | +| N_cqi_transmit | 1 (i.e. no repetition) | +| CQI reporting interval | 2 ms | +| Slot format | 2 TPC bits, 8 Pilot bits, SF 256 | +| Channel estimation | Real, TPC-aided | +| Inner loop PC | On, minimum delay 1 slot (PC algorithm 1) | +| Inner loop PC step size | 1dB | +| Outer loop PC | Off | +| RX diversity | Reception with two antennas | +| Channel Model | Vehicular A | +| UE velocity | 3 km/h, 30 km/h | + +##### 4.3.2.6.2 Simulations results + +Figure 4.3.2.6.2-1 and Figure 4.3.2.6.2-2 present CQI link performance for the Vehicular A channel at the UE velocity of 3 km/h and 30 km/h respectively. + +![Figure 4.3.2.6.2-1: CQI error rate vs. SIR target for VehA3. The graph shows the CQI error rate (P_blk) on a logarithmic y-axis (10^-3 to 10^0) against the SIR target on a linear x-axis (-1 to 4). Three curves are plotted for different Ahs values: Ahs = 15/15 (blue line with 'x' markers), Ahs = 24/15 (red line with '+' markers), and Ahs = 30/15 (green line with square markers). All curves show a decreasing trend as the SIR target increases. The Ahs = 30/15 curve is the lowest, followed by Ahs = 24/15, and then Ahs = 15/15.](73c3a69fa000ad227906a39c79b86dbc_img.jpg) + +CQI error rate for VA3 using ILPC + +| SIR target | P_blk (Ahs = 15/15) | P_blk (Ahs = 24/15) | P_blk (Ahs = 30/15) | +|------------|---------------------|---------------------|---------------------| +| -1 | ~1.5e-1 | ~4e-2 | ~2e-2 | +| 0 | ~8e-2 | ~2e-2 | ~1e-2 | +| 1 | ~4e-2 | ~1e-2 | ~5e-3 | +| 2 | ~1e-2 | ~5e-3 | ~2e-3 | +| 3 | ~2e-3 | ~1e-3 | ~5e-4 | + +Figure 4.3.2.6.2-1: CQI error rate vs. SIR target for VehA3. The graph shows the CQI error rate (P\_blk) on a logarithmic y-axis (10^-3 to 10^0) against the SIR target on a linear x-axis (-1 to 4). Three curves are plotted for different Ahs values: Ahs = 15/15 (blue line with 'x' markers), Ahs = 24/15 (red line with '+' markers), and Ahs = 30/15 (green line with square markers). All curves show a decreasing trend as the SIR target increases. The Ahs = 30/15 curve is the lowest, followed by Ahs = 24/15, and then Ahs = 15/15. + +Figure 4.3.2.6.2-1 CQI error rate vs. SIR target for VehA3 + +![Figure 4.3.2.6.2-2: CQI error rate vs. SIR target for VehA30. The graph shows the CQI error rate (P_blk) on a logarithmic y-axis (10^-3 to 10^0) against the SIR target (SIR_target) on a linear x-axis (-1 to 4). Three curves are plotted for different Ahs values: Ahs = 15/15 (blue line with 'x' markers), Ahs = 24/15 (red line with '+' markers), and Ahs = 30/15 (green line with square markers). All curves show a decreasing trend as the SIR target increases. The Ahs = 30/15 curve shows the lowest error rate, while the Ahs = 15/15 curve shows the highest error rate.](57261b803cf2db0e8feca169cb2c416b_img.jpg) + +Figure 4.3.2.6.2-2: CQI error rate vs. SIR target for VehA30. The graph shows the CQI error rate (P\_blk) on a logarithmic y-axis (10^-3 to 10^0) against the SIR target (SIR\_target) on a linear x-axis (-1 to 4). Three curves are plotted for different Ahs values: Ahs = 15/15 (blue line with 'x' markers), Ahs = 24/15 (red line with '+' markers), and Ahs = 30/15 (green line with square markers). All curves show a decreasing trend as the SIR target increases. The Ahs = 30/15 curve shows the lowest error rate, while the Ahs = 15/15 curve shows the highest error rate. + +**Figure 4.3.2.6.2-2 CQI error rate vs. SIR target for VehA30** + +Table 4.3.2.6.2-1 captures the results of CQI error rates at the SIR target of 0 dB. + +**Table 4.3.2.6.2-1 CQI error rate results at SIR target 0 dB** + +| HS-DPCCH to DPCCH power offset | CQI error rate @ 0 dB SIR target and Veh A3 | CQI error rate @ 0 dB SIR target and Veh A30 | +|--------------------------------|---------------------------------------------|----------------------------------------------| +| 0 dB | 6.5 % | 10.1 % | +| 4 dB | 1.5 % | 5% | +| 6 dB | 0.8 % | 3 % | + +Based on the above results and taking as an example an operating point of 4% for the CQI error rate it is observed that: + +- If the HS-DPCCH power offset to the DPCCH is configured relatively high (e.g. 6 dB) then reliable detection of CQI with a reduced SIR target is possible in non-SHO even without increasing the HS-DPCCH power offset to the DPCCH. +- If the HS-DPCCH power offset to the DPCCH is configured relatively low (e.g. 0 dB), then high SIR target reduction (e.g. to 0 dB) may deteriorate CQI performance. The presented simulation results prove that beta boosting, i.e. increasing the HS-DPCCH power offset to the DPCCH, would then improve the CQI error rate. + +The UE can be DL active (receive HSDPA channels) and reliably transmit CQI on the HS-DPCCH when it is in CPC mode, and the SIR target is reduced. Depending on the configuration of the HS-DPCCH power offset to the DPCCH, beta boosting may be useful to keep the desired CQI error rate. + +### 4.3.3 Benefits of the concept + +- Less air interface capacity consumption per UE due to reduced UL DPCCH noise contribution and therefore also increased UE battery life time compared to REL-6. +- Compared to REL-6: Increased number of temporarily inactive users that can stay in CELL\_DCH and that can therefore get active in a very short time avoiding frequent transitions to CELL\_FACH. + +- Power control loop is maintained for UL and DL. +- For L1 signalling approach: no extra UL E-DPDCH transmission needed, fast signalling and low processing effort. +- For L2 signalling approach: reliable due to CRC for the MAC-e PDU and HARQ retransmission mechanism, applicable in SHO. +- For predefined/configured rules: further signalling reduction (especially for CPC initiation). + +### 4.3.4 Open issues of the concept + +- Need for modification of HS-SCCH signalling (spare values exist). +- Details of power offset on HS-DPCCH and/or UL DPCCH to compensate SIR\_target reduction in case of DL active and UL inactive. +- Automatic DPCCH power offset or reduction by the UE might be considered for reactivation or deactivation respectively to reduce convergence time of the power control. +- Handling of VoIP and non-VoIP together. +- Decision on how to address/avoid possible RL\_FAILURE messages of non-serving Node Bs in case of soft handover. + +## 4.4 CQI reporting reduction + +### 4.4.1 Description of the concept + +The proposed concept has the goal to reduce the Tx power of the UE by reducing the CQI reporting (thus eliminating the interference from HS-DPCCH in UL) when no data is transmitted on HS-PDSCH in downlink. This could be achieved by switching the CQI reporting off ("CQI off") or by just a reduction of CQI reporting ("Reduced CQI") which does not switch off the CQI reporting completely. + +It is an important characteristic of the concept that these changes do not involve the RNC, so that the long delays of RRC or NBAP procedures (>> 100ms) are avoided and the user is staying in CELL\_DCH state. + +The "CQI off" and "CQI reporting reduction" could be carried out by e.g.: + +- L1 signalling: Serving Node B controls when a UE is going into an inactive phase with CQI off and corresponding L1 signalling is used to trigger deactivation & reactivation. +- L2 signalling: The UE controls CQI off by L2 MAC-e signalling to the NodeBs of the active RLS, i.e. deactivation & reactivation. +- Predefined/configured rules: Both UE and NodeB detect inactivity and activity based on either pre-defined or configured rules and reduce the CQI reporting interval to a pre-defined or configured CQI reporting interval during periods of inactivity. + +#### 4.4.1.1 L1 signalling approach for CQI off + +##### Traffic inactivity detection: + +The absence of data to be transmitted on HS-DSCH in the DL can be detected by observing the current occupation of the MAC-hs buffer located in the serving Node B. A deactivation start timer/timeout (starting when a buffer runs empty) can be used to avoid unnecessary switching between active and inactive mode during very short traffic intermissions. + +##### Switching CQI off: + +Depending on the traffic inactivity on DL, a switching off of periodic CQI reporting (as configured by RNC) is triggered by the serving Node B. + +The serving Node B informs the UE about the change by physical layer signalling. This can be implemented as a new signalling message on the HS-SCCH, using one of the 8 unused bit combinations within the 7 bits assigned to the channelization code set. + +On receiving this message, the UE will immediately stop the transmission of CQI reports on HS-DPCCH, but save the RNC-configured reporting cycle to be restored at reactivation time. The reduction in UL interference achieved will depend upon the CQI reporting interval configured by the UTRAN for each UE. + +##### **Triggering reactivation:** + +When the serving Node B detects the reactivation condition (new data for DL in the MAC-hs buffer can be immediately detected in the serving Node B), it sends a signalling message to the UE (via HS-SCCH) to trigger the restart of CQI reporting. On receiving this message, the UE reacts by immediately restarting CQI reports with the last RNC-configured reporting cycle. + +The Node B avoids scheduling of large PDUs to the UE, until the first CQI report has been received. Delay-critical data (e.g. SRB messages) can immediately be scheduled when restricted to a small PDU (corresponding to low CQI values). + +##### **4.4.1.1.1 Interworking aspects** + +###### **Cell changes and Soft Handover:** + +Measurement reports from the UE and RNC-triggered signalling of changes in the active set and changes of the serving Node B will be transmitted on SRB over E-DCH and HS-DSCH, and thereby trigger reactivation. Therefore the highest gain of this concept is achieved when the reporting interval of such mobility measurements is well above the timeout parameter that triggers the deactivation. + +The on- and off-switching of the CQI reports is not affected by soft handover (SHO), as SHO is not applied on HS-DPCCH. + +###### **Reporting power gains to RNC:** + +As it is the goal of the proposed concept to allow more users to get and remain connected (without the need for intermediate RRC state switching), it is necessary that the RNC is made aware of the savings in the received noise rise, so that these can be taken into account in decisions e.g. for call admission and RRC state switching. These gains will, however, automatically be reflected in the measurements of “total received wideband power”, which are periodically reported from Node B to CRNC, anyway. Thus, no changes to the standard measurement reporting are required for this purpose. + +#### **4.4.1.2 L2 signalling approach for CQI off** + +##### **Traffic inactivity detection:** + +The UE detects autonomously the conditions for a transition into the idle traffic mode, i.e. inactivity in the DL. The conditions for a transition into the idle traffic mode could involve no activity for a certain minimum period of time in DL (and UL). + +When the UE has detected a transition from active mode into “idle traffic mode” or vice versa, it can instantaneously stop or resume CQI reporting. When the NodeB has detected a transition from active mode into “idle traffic mode” or vice versa, it can instantaneously continue or stop decoding the CQI information. + +The UE will inform the NodeBs about a change from active mode into idle traffic mode and vice versa by means of a short MAC-e PDU consisting of scheduling information (SI). For the change from active mode into idle traffic mode, a specific SI reserved for that purpose is transmitted and repeated through HARQ retransmissions until all NodeBs in serving and non-serving RLS have acknowledged receipt of the transition or the maximum number of transmissions is reached. + +##### **Switching CQI off:** + +Periodic CQI reporting (as configured by RNC) can be switched off when data inactivity on the downlink has been detected by the UE. In particular, the UE immediately stops the transmission of CQI reports on HS-DPCCH upon transition into the idle traffic mode. Since no HS-PDSCH data is transmitted in an idle traffic period, ACK/NACK signalling is not required and HS-DPCCH is completely switched off, thus also reducing the UL interference. The RNC-configured CQI reporting cycle is saved and can be restored instantaneously at reactivation time. + +##### Triggering reactivation: + +A NodeB can trigger reactivation by sending a short MAC-hs PDU in the downlink, which is then followed by the reactivation through transmitting SI by the UE in the uplink. + +For the change from idle traffic mode into active mode, the actual SI is transmitted and repeated through HARQ retransmissions until receipt of the transition is acknowledged. + +##### Specific L2 signalling aspects: + +The reserved MAC-e SI for indicating a transition can have its own HARQ profile with an additional power offset to ensure reliable detection by all NodeBs in the active set with reasonable latency. The SI word specific for the transition from active mode into idle traffic mode conveys UE buffer occupancy of 0 (9 bits), maximum possible power ratio versus DPCCH (5 bits) and a pre-defined logical channel ID (4 bits). While a pre-defined logical channel ID is given in the SI word specific for the transition from active mode into idle traffic mode, it may be noted that the transition is valid for all logical channel IDs. + +##### 4.4.1.2.1 New parameters for L2 signalling approach for CQI off + +| Parameter | Description | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| Inactivity time | minimum time of inactivity on UL and DL before the UE can trigger a transition into the idle traffic mode | +| SI for transition into idle traffic mode | Dedicated and reserved SI that is only used to signal the transition into the idle traffic mode | + +#### 4.4.1.3 Predefined/configured rules for CQI reporting reduction + +Instead of relying on signalling, predefined (and standardized) rules can be used to control the UE and Node B behaviour, i.e., the UE and Node B could by applying these rules have a consistent view of whether 'normal' or 'reduced' activity transmission should be used. + +In the downlink direction, the Node B is clearly aware of whether there is data awaiting transmission. The UE will notice whether it has been recently scheduled or not, which provides an indication about the downlink activity and correspondingly whether the UE shall use 'normal' or 'reduced' activity transmission for the uplink CQI reporting. + +Currently, a single CQI reporting pattern is defined for HSDPA, where a regular reporting interval can be configured. By defining an additional CQI reporting pattern (which can have a configurable reporting interval different from the first pattern) to be used in 'reduced' activity transmission, a solution not requiring signalling can be achieved. Normally, the UE reports CQI using the frequent reporting pattern, i.e., transmits a CQI report once every $x_1$ ms. If the UE has not been scheduled for a certain (configurable) time period, the UE switches to a second, 'reduced activity' CQI reporting pattern, i.e., reports CQI every $x_2$ ms, where $x_2 > x_1$ . + +Note that the CQI reporting patterns as a special case may include switching off the reporting completely (basically setting $x_i$ to infinity). One possibility to implement this is to (re)start a timer in the UE every time it is scheduled. Once the timer reaches zero, the UE switches from pattern 1 to pattern 2. The Node B can use a corresponding timer mechanism (one per UE) to determine whether to expect pattern 1 or pattern 2. + +Furthermore, it may be beneficial, although not absolutely necessary, to select the patterns such that $x_1$ is a factor in $x_2$ . If, e.g., due to the UE missing the HS-SCCH and the Node B not detecting the absence of an ACK/NAK on the HS-DPCCH, the UE and Node B happens to use different patterns there are at least some reporting events that coincide with this choice of patterns. Alternatively, Node B could detect the presence of CQI every $x_1$ ms regardless of whether CQI reporting is reduced or not. + +To implement the above mechanisms, higher layer signalling between the RNC and the UE is required to configure the CQI reporting intervals $x_i$ . This signalling typically only takes place once at call setup and thus does not lead to a significant increase in interference. Signalling is also required between the RNC and Node B to configure the CQI reporting patterns $x_i$ . + +### 4.4.2 Analysis of the concept + +#### 4.4.2.1 Gain in terms of number of additional users & UL noise rise + +The gain that can be achieved by switching CQI reporting off, in terms of reducing the noise rise consumed by HS-DPCCH, depends on several factors: + +- Interval of CQI reporting (this can be configured between once per 2ms HSDPA TTI and once per 160ms). The more often the CQI is reported the higher is the gain of switching CQI reporting off. +- The power of the HS-DPCCH. The higher the HS-DPCCH power the higher the gain of switching CQI reporting off. + +During DL inactivity the ACK/NACK field (first of the 3 slots) of HS-DPCCH is automatically DTXed. + +The HS-DPCCH power is defined relative to the UL DPCCH power via the signalled value $\Delta_{CQI}$ which translates into an amplitude ratio $\beta_{hs} / \beta_c = 1/3 \dots 2$ (i.e. -9.5dB .. 6dB), see 25.213 [5] and 25.214 [6]. + +Due to same SF, similar channel coding if TFCI carried by UL DPCCH and similar required reliability it could be assumed that HS-DPCCH and UL DPCCH are transmitted with similar power (i.e. power ratio of 0dB). + +Assuming one CQI reporting per 2ms HSDPA TTI (which is the highest reporting cycle), a power ratio of HS-DPCCH/DPCCH of 0dB and that the UL DPCCH SIR target is configured so that it consumes 1% of the maximum allowed noise rise then switching CQI reporting off will reduce the noise rise produced by one user from 1.67% to 1%. This gain translates into the increase of the number of inactive users by the gain factor of 1.67. + +#### 4.4.2.2 Signalling load + +Considering the L1 signalling approach: + +- the HS-SCCH capacity of 500 messages per sec (1 every 2ms), +- the fact that a UE has to be able to read 4 HS-SCCHs in parallel, +- the case that one HS-SCCH message would be used for deactivation and a second HS-SCCH message would be used for reactivation, +- an average inactivity period of 5sec, + +even a high number of inactive users (e.g. 80) would have only a smaller impact on the HS-SCCH signalling load ( $(80 \times (2 \text{ msg}/5\text{sec})) / (2000 \text{ msg}/\text{sec}) = 1,6\%$ ). + +### 4.4.3 Benefits of the concept + +- Less air interface capacity consumption per UE due to reduced UL DPCCH noise contribution and therefore also increased UE battery life time compared to REL-6. +- Compared to REL-6: Increased number of temporarily inactive users that can stay in CELL\_DCH and that can therefore get active in a very short time avoiding frequent transitions to CELL\_FACH. +- Possibility to address UL noise rise reduction in case of DL inactivity. +- for L1 signalling approach for CQI off: no extra UL E-DPDCH transmission needed, fast signalling and low processing effort. +- for L2 signalling approach for CQI off: reliable due to CRC for the MAC-e PDU and HARQ retransmission mechanism. +- for predefined/configured rules: further signalling reduction (especially for CPC initiation) + +### 4.4.4 Open issues of the concept + +- Need for modification of HS-SCCH signalling (spare values exist). +- Applicability for VoIP? +- Need for sending CQIs from time to time? Or is CQI off sufficient? + +## 4.5 DRX at the UE + +### 4.5.1 Description of the concept + +- In case of discontinuous transmissions or sustained DL and UL inactivity, the UE and UTRAN may limit the number of subframes where the UE needs to monitor the HS-SCCH so that: + - DL scheduling is still possible + - UE is able to shut-off the receiver circuitry over some periods of time to yield a non 100% receiver duty cycle. +- Minimum monitoring of CPICH for the UE to keep up with changes in its Active Set due to mobility. +- The UE monitors a limited subset of HS-SCCHs in the time domain e.g., one subframe every two, or every four subframes – this DRX operation is controlled by the “HS-SCCH transmission cycle”. + +Note: This concept alone does not solve the problems of limitations in number of users per cell or limitations in UL noise rise or reduction in latency for temporarily inactive users addressed by the WI. Therefore it will only be considered if it can be applied as add-on to the concepts addressing the objectives of the WI. + +### 4.5.2 Analysis of the concept + +The DRX concept is complementary to the DPCCH gating (DTX) concept introduced in section 4.2. Indeed, the DPCCH gating concept will effectively open transmission gaps during which no PHY channels are transmitted from the UE. It would be, therefore, desirable to open reception gaps aligned as much as possible with those transmission gaps so that the UE could effectively go to sleep and hence extend its battery life (talk-time). + +In order to analyze the concept we look into the following aspects: + +- How the DTX and DRX cycles can be maximally aligned. +- What is the performance impact at the DL scheduler. + +#### 4.5.2.1 Timing, with 2 ms E-DCH TTI + +##### 4.5.2.1.1 Background + +Figure 4.5.2.1.1-1 details the relative HARQ timings for HSDPA and HSUPA. + +![Timing diagram for HSDPA/HSUPA relative HARQ. It shows two radio frames (SFN mod 2 = 0 and 1) and the timing relationships between various channels: P-CCPCH, E-DL RX, E-HICH, H-SUP, E-DPDCH, E-U UL x, D-PCH, HS-PDSCH, and HS-DPCCH. Key timing parameters include T_E-HICH,n, T_DPCH,n, T_HS-PDSCH, and formulas for calculating offsets and retransmission intervals. A legend defines 1 slot = 2560 chips, 1 TTI = 3 slots, and 1 subframe = 1 TTI.](31c1877b2b8a3479b473e01d9856b689_img.jpg) + +Timing parameters and formulas shown in the diagram: + +- $\tau_{E-HICH,n}$ +- [9,7:12,6] slots +- $\tau_{DPCH,n}$ +- 1024 chips +- $\tau_{HS-PDSCH} = 2 \times 2560$ +- $\tau_{DPCH,n} = 256 \cdot n, n \in [0;149]$ +- $\tau_{E-HICH,n} = 5120 + 7680 \left( \frac{50 + \tau_{DPCH,n} / 256}{30} \right)$ +- $m = \frac{T_{TxDiff}}{256} + 101$ +- 7.5 slots +- $m \cdot 256$ +- [10;13] slots + +Legend: + +- 1 slot = 2560 chips +- 1 TTI = 3 slots +- 1 subframe = 1 TTI + +Timing diagram for HSDPA/HSUPA relative HARQ. It shows two radio frames (SFN mod 2 = 0 and 1) and the timing relationships between various channels: P-CCPCH, E-DL RX, E-HICH, H-SUP, E-DPDCH, E-U UL x, D-PCH, HS-PDSCH, and HS-DPCCH. Key timing parameters include T\_E-HICH,n, T\_DPCH,n, T\_HS-PDSCH, and formulas for calculating offsets and retransmission intervals. A legend defines 1 slot = 2560 chips, 1 TTI = 3 slots, and 1 subframe = 1 TTI. + +Figure 4.5.2.1.1-1: HSDPA/HSUPA relative HARQ timing + +It is worth to note that for HSDPA: + +- The data acknowledgment is sent 7.5 slots after the end of the transmission of a HS-PDSCH subframe over the HS-DPCCH. +- A data retransmission can occur between 5 and 7 TTIs later + +While for HSUPA: + +- The data acknowledgment is sent 9.7~12.6 slots after the end of the transmission of the corresponding E-DPDCH subframe over the E-HICH. +- A data retransmission can only be sent 7 TTIs later + +In the following discussion, we synchronize these events so that they coincide as much as possible. Since it is not desirable to change the above timing, we can only choose which subframes the UE is monitoring or is allowed to use for transmission. These restrictions have to be well shared and synchronized with the Node B as the latter has to take them into account when scheduling the HSDPA packets. + +The parameter “n” of , which defines the offset for the UE (see Figure 4.5.2.1.1-1), creates a variability in the relative position of the HSDPA and HSUPA channels. With different values of n, the success of channel synchronization will vary. + +##### 4.5.2.1.2 DRX mode 2/8 + +In this mode, the UE can be scheduled and is allowed to transmit every 4th subframe as depicted in Figure 4.5.2.1.2-1 and Figure 4.5.2.1.2-2. A DTX cycle of 4 TTIs, defines the E-DPDCH and E-HICH timelines. If we want to keep that DTX cycle almost unchanged, the UE transmission on the UL HS-DPCCH has to coincide with the DTX awake periods. This falls nicely as the UE reception would also fall in the same periods. By preserving the DTX cycle, we create an overlapping DRX cycle. This allows the UE to go to sleep when it is neither receiving or transmitting. + +Sleeping is optional for the UE. The time to switch between the awake and sleep states is implementation dependent. The subsequent figures show skirts around the combined channel activity time to illustrate this concept. However, this is for illustration purposes only. + +With arbitrarily chosen wakeup and sleep delays and averaging over n, which defines the offset for the UE (see Figure 4.5.2.1.1-1), a UEs can achieve 31% of DTX/DRX time. + +![Timing diagram for DRX mode 2/8, n=5. The x-axis represents time in slots from 0 to 34. The diagram shows five signal lines: HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and Wake Up (grey). The Wake Up signal is a periodic square wave. The other signals show periodic activity aligned with the Wake Up signal. HS-PDSCH is active in slots 2-4, 14-16, and 26-28. HS-DPCCH is active in slots 12-16 and 24-28. E-DPDCH is active in slots 2-4, 12-16, 24-28, and 30-32. E-HICH is active in slots 14-16 and 26-28.](9d18af84f9d0bd3cb990f22f91fcf938_img.jpg) + +Timing diagram for DRX mode 2/8, n=5. The x-axis represents time in slots from 0 to 34. The diagram shows five signal lines: HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and Wake Up (grey). The Wake Up signal is a periodic square wave. The other signals show periodic activity aligned with the Wake Up signal. HS-PDSCH is active in slots 2-4, 14-16, and 26-28. HS-DPCCH is active in slots 12-16 and 24-28. E-DPDCH is active in slots 2-4, 12-16, 24-28, and 30-32. E-HICH is active in slots 14-16 and 26-28. + +Figure 4.5.2.1.2-1: DRX mode 2/8, n=5 + +![Timing diagram for DRX mode 2/8, n=14. The x-axis represents time in slots from 0 to 34. The diagram shows five signal lines: HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX signal is a periodic square wave. The other signals show periodic activity aligned with the DTX/DRX signal. HS-PDSCH is active in slots 4-8, 16-20, and 28-32. HS-DPCCH is active in slots 16-20 and 28-32. E-DPDCH is active in slots 2-4, 14-16, 26-28, and 30-32. E-HICH is active in slots 16-20 and 28-32.](36f66d23ff319c73247feee55fd2dfb1_img.jpg) + +Timing diagram for DRX mode 2/8, n=14. The x-axis represents time in slots from 0 to 34. The diagram shows five signal lines: HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX signal is a periodic square wave. The other signals show periodic activity aligned with the DTX/DRX signal. HS-PDSCH is active in slots 4-8, 16-20, and 28-32. HS-DPCCH is active in slots 16-20 and 28-32. E-DPDCH is active in slots 2-4, 14-16, 26-28, and 30-32. E-HICH is active in slots 16-20 and 28-32. + +Figure 4.5.2.1.2-1: DRX mode 2/8, n=14 + +##### 4.5.2.1.3 DRX mode 1/8 + +In this mode, the UE is scheduled and is allowed to transmit every 8th subframe. The transmission and reception cycles are offset by 4 frames to separate transmission and reception operations. This allows DTX and DRX periods of 75%, however, the combined DTX/DRX average period is 42% at the UE. + +![Figure 4.5.2.1.3-1: DRX mode 1/8, n=0. This timing diagram shows five channels over 34 slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX channel is a grey background with a black line indicating active periods. The E-HICH channel has a pulse from slot 26 to 28. The E-DPDCH channel has a pulse from slot 12 to 16. The HS-DPCCH channel has a pulse from slot 12 to 16. The HS-PDSCH channel has pulses from slot 2 to 4 and slot 26 to 28.](df942da5e715e03b194b733d9f5998ad_img.jpg) + +Figure 4.5.2.1.3-1: DRX mode 1/8, n=0. This timing diagram shows five channels over 34 slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX channel is a grey background with a black line indicating active periods. The E-HICH channel has a pulse from slot 26 to 28. The E-DPDCH channel has a pulse from slot 12 to 16. The HS-DPCCH channel has a pulse from slot 12 to 16. The HS-PDSCH channel has pulses from slot 2 to 4 and slot 26 to 28. + +Figure 4.5.2.1.3-1: DRX mode 1/8, n=0 + +##### 4.5.2.1.4 DRX mode 1/16 and beyond + +In this mode, the UE is scheduled and is allowed to transmit every 16th subframe. The transmission and reception cycles are offset by 4 frames to combine the transmission operations. In this mode, the UE can achieve DTx/DRX periods of 60%. Note that if the UE chooses to transmit and that transmission is NACK-ed, the UE will have to wake up at the appropriate time (7 subframes later) to re-transmit. This case is not depicted below. + +![Figure 4.5.2.1.4-1: DRX mode 1/16, n=0. This timing diagram shows five channels over 88 slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX channel is a grey background with a black line indicating active periods. The E-HICH channel has pulses at slots 28-30 and 74-76. The E-DPDCH channel has pulses at slots 12-14 and 60-62. The HS-DPCCH channel has pulses at slots 12-14 and 60-62. The HS-PDSCH channel has pulses at slots 4-6 and 52-54.](3d6f4088e319484d4e81fb68cd8520a3_img.jpg) + +Figure 4.5.2.1.4-1: DRX mode 1/16, n=0. This timing diagram shows five channels over 88 slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), and DTX/DRX (grey). The DTX/DRX channel is a grey background with a black line indicating active periods. The E-HICH channel has pulses at slots 28-30 and 74-76. The E-DPDCH channel has pulses at slots 12-14 and 60-62. The HS-DPCCH channel has pulses at slots 12-14 and 60-62. The HS-PDSCH channel has pulses at slots 4-6 and 52-54. + +Figure 4.5.2.1.4-1: DRX mode 1/16, n=0 + +If longer DTx cycles are allowed, DRX cycles can be tailored that are similar to this 1/16 mode. + +##### 4.5.2.1.5 DRX mode 2/8, in a 2 way soft handover + +In the following, we assume the UE is in a 2 way soft handover between two Node B's and that the UE is assigned **n1** and **n2** as offsets from the Node B's. + +Per 25.214, "UTRAN starts the transmission of the downlink DPCCH/DPDCH or F- PCH for each new radio link at a frame timing such that the frame timing received at the UE will be within $T_0 \pm 148$ chips prior to the frame timing of the uplink DPCCH/DPDCH at the UE". We can assume that all Node Bs have adjusted their transmission times so that hypothetical DPCH channels would arrive at the same time. Since that arrival time dictates the E-DPCH offset, we can + +pick as a reference an enabled TTI subframe. The E-HICH subframes will be [9.7 to 12.6] slots after this enabled E-DPCH depending on the Node B. By design, they will fall within a subframe of each other. + +The choice of the HS-PDSCH subframe (and consequently the associated HS-DPCCH) is based on the closest E-DPCH subframe that optimizes the DTX/DRX cycle. + +However, the E-RGCH from the non-serving cell is 10 ms long, preventing any DRX during this mode of operation. + +If we ignore the E-RGCH from the non-serving cell, averaging over n1 and n2, the UE can sleep 26% of the time. + +##### 4.5.2.1.6 DRX mode 1/8, in a 2 way soft handover + +The 10ms E-RGCH impacts the possible DRX cycle, however, we can still achieve on average **24%** of sleep time. In the worse case scenario, the sleep time drops to **15%**. In the best cases, the UE can sleep up to **27%** of the time. + +If we ignore the E-RGCH from the non-serving cell, averaging over n1 and n2, the UE can sleep 36% of the time. At a worse case scenario, the sleep time drops to 22%. In the best cases, the UE can sleep up to 46% of the time. + +Figure 4.5.2.1.6-1 shows an example of handover between two Node Bs with sleep times of 27%. + +![Figure 4.5.2.1.6-1: UE in handover region, DRX mode 1/8, in soft handover, 27% sleep time. This timing diagram shows various signal states over 44 slots. The legend includes: HS-PDSCH (solid blue), HS-DPCCH (solid green), E-DPDCH (solid light blue), E-AGCH (dashed light blue), E-HICH #1 (solid magenta), E-HICH #2 (dashed magenta), E-RGCH #1 (dashed yellow), E-RGCH #2 (solid cyan), DTX/DRX #1 (dashed black), DTX/DRX #2 (solid black), and DTX/DRX Both (solid red). The diagram shows periodic activity for HS-PDSCH and HS-DPCCH, with E-RGCH #1 and #2 being active for 10ms (10 slots) each. The DTX/DRX signals show periods of inactivity (sleep) corresponding to the active periods of the data channels.](baa4bab83368a423293c97f9e4ae8932_img.jpg) + +Figure 4.5.2.1.6-1: UE in handover region, DRX mode 1/8, in soft handover, 27% sleep time. This timing diagram shows various signal states over 44 slots. The legend includes: HS-PDSCH (solid blue), HS-DPCCH (solid green), E-DPDCH (solid light blue), E-AGCH (dashed light blue), E-HICH #1 (solid magenta), E-HICH #2 (dashed magenta), E-RGCH #1 (dashed yellow), E-RGCH #2 (solid cyan), DTX/DRX #1 (dashed black), DTX/DRX #2 (solid black), and DTX/DRX Both (solid red). The diagram shows periodic activity for HS-PDSCH and HS-DPCCH, with E-RGCH #1 and #2 being active for 10ms (10 slots) each. The DTX/DRX signals show periods of inactivity (sleep) corresponding to the active periods of the data channels. + +Figure 4.5.2.1.6-1: UE in handover region, DRX mode 1/8, in soft handover, 27% sleep time + +##### 4.5.2.1.7 DRX mode 1/16, in a 2 way soft handover + +In this mode, we can achieve on average **39%** of sleep time. The sleep time varies between **33%** and **44%**. Figure 4.5.2.1.7-1 shows an example of handover between two Node Bs with sleep times of 39%. + +![Figure 4.5.2.1.7-1: A timing diagram showing various channel states over 80 slots. The x-axis is labeled 'time (slots)' with values 0, 8, 16, 24, 32, 40, 48, 56, 64, 72, 80. The legend includes: HS-PDSCH (blue solid), HS-DPCCH (green solid), E-DPDCH (light blue solid), E-AGCH (light blue dashed), E-HICH #1 (magenta solid), E-HICH #2 (magenta dashed), E-RGCH #1 (yellow dashed), E-RGCH #2 (cyan solid), DTX/DRX #1 (black dashed), DTX/DRX #2 (grey solid), and DTX/DRX Both (red solid). The diagram shows periodic activity for DTX/DRX and other channels.](578d2763eaf3edf3f1bd6657455ad54a_img.jpg) + +Figure 4.5.2.1.7-1: A timing diagram showing various channel states over 80 slots. The x-axis is labeled 'time (slots)' with values 0, 8, 16, 24, 32, 40, 48, 56, 64, 72, 80. The legend includes: HS-PDSCH (blue solid), HS-DPCCH (green solid), E-DPDCH (light blue solid), E-AGCH (light blue dashed), E-HICH #1 (magenta solid), E-HICH #2 (magenta dashed), E-RGCH #1 (yellow dashed), E-RGCH #2 (cyan solid), DTX/DRX #1 (black dashed), DTX/DRX #2 (grey solid), and DTX/DRX Both (red solid). The diagram shows periodic activity for DTX/DRX and other channels. + +Figure 4.5.2.1.7-1: UE in handover region, DRX mode 1/16, in soft handover, 39% sleep time + +#### 4.5.2.2 Downlink scheduler performance + +When a UE is in a DRX mode, the scheduler is restricted with regard to the times it can choose to schedule this UE on the DL. This could result in a degradation of the performance of the scheduler measured with the Average Outage Probability. Figures 4.5.2.2-1 and 4.5.2.2-2 show that the Average Outage Probability degradation is acceptable (less than 5%) for all channel models considered when we are well below the system capacity. + +While the DRX mode allows the UE to extend its battery life, it is under UTRAN's control, and thus can be deactivated if the DL scheduler is running short. At high system loads, the UTRAN can disable this function to optimize its resource allocation. + +![Figure 4.5.2.2-1: A line graph showing Average Outage Probability vs. Normalized Load for PB3 channel model. The y-axis is 'Average Outage Probability' from 0% to 50%. The x-axis is 'Normalized Load' from 25% to 125%. Four curves are shown: PB3 - 1 (blue), PB3 - 2/8 (magenta), PB3 - 1/8 (yellow), and PB3 - 1/16 (cyan). All curves show low outage probability until around 80% load, after which they rise sharply, with PB3 - 1/16 reaching nearly 50% at 125% load.](d3e2268ff05b24c2d8bbef7f56aba6c7_img.jpg) + +Figure 4.5.2.2-1: A line graph showing Average Outage Probability vs. Normalized Load for PB3 channel model. The y-axis is 'Average Outage Probability' from 0% to 50%. The x-axis is 'Normalized Load' from 25% to 125%. Four curves are shown: PB3 - 1 (blue), PB3 - 2/8 (magenta), PB3 - 1/8 (yellow), and PB3 - 1/16 (cyan). All curves show low outage probability until around 80% load, after which they rise sharply, with PB3 - 1/16 reaching nearly 50% at 125% load. + +Figure 4.5.2.2-1: Impact on DL scheduler for a PB3 channel model + +![Line graph showing Average Outage Probability vs Normalized Load for VA30 channel model with different scheduler configurations.](d989d8766a23d5e409031f1ceae6572b_img.jpg) + +The graph illustrates the Average Outage Probability (Y-axis, 0% to 50%) versus Normalized Load (X-axis, 60% to 120%) for a VA30 channel model. Four curves are shown, representing different scheduler configurations: VA30 - 1 (blue), VA30 - 2/8 (magenta), VA30 - 1/8 (yellow), and VA30 - 1/16 (cyan). The outage probability increases sharply as the normalized load increases, particularly above 80%. + +| Normalized Load | VA30 - 1 | VA30 - 2/8 | VA30 - 1/8 | VA30 - 1/16 | +|-----------------|----------|------------|------------|-------------| +| 60% | 0% | 0% | 2% | 5% | +| 80% | 0% | 1% | 2% | 7% | +| 100% | 9% | 16% | 42% | 48% | +| 110% | 35% | 45% | 50% | 50% | +| 115% | 50% | 50% | 50% | 50% | + +Line graph showing Average Outage Probability vs Normalized Load for VA30 channel model with different scheduler configurations. + +Figure 4.5.2.2-2: Impact on DL scheduler for a VA30 channel model + +#### 4.5.2.2A Timing, with 10 ms E-DCH TTI + +##### 4.5.2.2A.1 Background + +The same basic time relationships remain between the HSDPA/HSUPA channels, with some modifications as shown in Figure 4.5.2.2A.1-1. + +![Figure 4.5.2.2A.1-1: HSDPA/HSUPA relative HARQ timing for 10 ms E-DCH. The diagram illustrates the timing relationships between various channels (P-CCPCH, E-AGCH, E-RGCH, E-HICH, E-DPDCH, DPCH, HS-PDSCH, HS-SCCH, HS-DPCCH) across multiple radio frames. It shows subframe allocations and timing offsets for HSUPA and HSDPA. Key timing parameters like tau_E-AGCH, tau_E-RGCH,n, tau_E-HICH,n, tau_E-DPDCH, tau_DPCH,n, tau_HS-PDSCH, tau_HS-SCCH, and tau_HS-DPCCH are indicated. Formulas for calculating these timings are provided on the right side of the diagram.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +1 slot = 2560 chips +1 TTI = 3 slots +1 subframe = 1 TTI + +Formulas: + +$$\tau_{HS-PDSCH} = 2 \times 2560$$ +$$\tau_{DPCH,n} = 256 \cdot m, n \in [0, 149]$$ +$$\tau_{E-HICH,n} = 5120 + 7680 \times \left\lceil \frac{(\tau_{DPCH,n}/256) - 70}{30} \right\rceil$$ +$$m = \frac{T_{TxDiff}}{256} + 101$$ +$$\tau_{E-RGCH,n} = 5120 + 7680 \times \left\lceil \frac{(\tau_{DPCH,n}/256) - 70}{30} \right\rceil$$ + +Figure 4.5.2.2A.1-1: HSDPA/HSUPA relative HARQ timing for 10 ms E-DCH. The diagram illustrates the timing relationships between various channels (P-CCPCH, E-AGCH, E-RGCH, E-HICH, E-DPDCH, DPCH, HS-PDSCH, HS-SCCH, HS-DPCCH) across multiple radio frames. It shows subframe allocations and timing offsets for HSUPA and HSDPA. Key timing parameters like tau\_E-AGCH, tau\_E-RGCH,n, tau\_E-HICH,n, tau\_E-DPDCH, tau\_DPCH,n, tau\_HS-PDSCH, tau\_HS-SCCH, and tau\_HS-DPCCH are indicated. Formulas for calculating these timings are provided on the right side of the diagram. + +Figure 4.5.2.2A.1-1: HSDPA/HSUPA relative HARQ timing for 10 ms E-DCH + +##### 4.5.2.2A.2 DRX mode 1/2 + +As can be noted from Figure 4.5.2.2A.1-1, the need to receive E-HICH, E-RGCH and E-AGCH result in no sleep time. + +##### 4.5.2.2A.3 DRX mode 1/3 + +It is possible to operate in this mode, however, the UE DRX sleep mode is upper bounded by about 6 slots which is around 13%. + +##### 4.5.2.2A.4 DRX mode 1/4 + +We can achieve on average **24.6%** of sleep time. In the worse case scenario, the sleep time drops to **20.5%**. In the best cases, the UE can sleep up to **29.3%** of the time. + +Figure 4.5.2.2A.4-1 shows an example of handover between two Node Bs with sleep times of 25%. + +![Timing diagram showing signal activity for various channels over 100 time slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), E-AGCH (brown), E-RGCH (cyan), and DTX/DRX (grey). The x-axis represents time in slots from -50 to 100. The DTX/DRX signal shows a periodic sleep pattern. The E-RGCH signal is active for 10ms (10 slots) every 40ms (40 slots). The E-AGCH signal is active for 10ms every 40ms. The E-HICH signal is active for 10ms every 40ms. The E-DPDCH signal is active for 10ms every 40ms. The HS-DPCCH signal is active for 10ms every 40ms. The HS-PDSCH signal is active for 10ms every 40ms.](2333c01db80c100fb3f8467a0717d99d_img.jpg) + +Figure 4.5.2.2A.4-1: 10ms E-DCH, DRX mode 1/4, 25% sleep time + +Timing diagram showing signal activity for various channels over 100 time slots. The channels are HS-PDSCH (blue), HS-DPCCH (green), E-DPDCH (red), E-HICH (magenta), E-AGCH (brown), E-RGCH (cyan), and DTX/DRX (grey). The x-axis represents time in slots from -50 to 100. The DTX/DRX signal shows a periodic sleep pattern. The E-RGCH signal is active for 10ms (10 slots) every 40ms (40 slots). The E-AGCH signal is active for 10ms every 40ms. The E-HICH signal is active for 10ms every 40ms. The E-DPDCH signal is active for 10ms every 40ms. The HS-DPCCH signal is active for 10ms every 40ms. The HS-PDSCH signal is active for 10ms every 40ms. + +Figure 4.5.2.2A.4-1: 10ms E-DCH, DRX mode 1/4, 25% sleep time + +##### 4.5.2.2A.5 DRX mode 1/4, in a 2 way soft handover + +The 10ms E-RGCH still impacts the possible DRX cycle, we can achieve on average **18.2%** of sleep time. In the worse case scenario, the sleep time drops to **3.3%**. In the best cases, the UE can sleep up to **27.6%** of the time. + +If we ignore the E-RGCH from the non-serving cell, averaging over n1 and n2, the UE can sleep 24.6% of the time. At a worse case scenario, the sleep time drops to 20.5%. In the best cases, the UE can sleep up to 29.3% of the time. These results are as similar to the case where we are not in soft handover. + +Figure 4.5.2.2A.5-1 shows an example of handover between two Node Bs with sleep times of 23%. + +![Figure 4.5.2.2A.5-1: UE in handover region, 10ms E-DCH, DRX mode 1/4, in soft handover, 23% sleep time. The figure shows a timeline of various channels over 100 slots. The channels include HS-PDSCH (blue solid), E-HICH n1 (magenta solid), E-RGCH n1 (cyan solid), HS-DPCCH (green solid), E-HICH n2 (magenta dashed), E-RGCH n2 (cyan dashed), E-DPDCH (red solid), E-AGCH (brown solid), and DTX/DRX (grey background). The DTX/DRX signal shows periodic sleep periods. The HS-PDSCH transmissions occur during active periods, while the other channels show more continuous activity.](7a0281fac8690d8894ef1cb92d1a7704_img.jpg) + +Figure 4.5.2.2A.5-1: UE in handover region, 10ms E-DCH, DRX mode 1/4, in soft handover, 23% sleep time. The figure shows a timeline of various channels over 100 slots. The channels include HS-PDSCH (blue solid), E-HICH n1 (magenta solid), E-RGCH n1 (cyan solid), HS-DPCCH (green solid), E-HICH n2 (magenta dashed), E-RGCH n2 (cyan dashed), E-DPDCH (red solid), E-AGCH (brown solid), and DTX/DRX (grey background). The DTX/DRX signal shows periodic sleep periods. The HS-PDSCH transmissions occur during active periods, while the other channels show more continuous activity. + +**Figure 4.5.2.2A.5-1: UE in handover region, 10ms E-DCH, DRX mode 1/4, in soft handover, 23% sleep time** + +The HS-PDSCH transmissions have to occur when the UE wakes up so that the ACKs can be sent before it goes to sleep. More transmissions can occur than shown while the UE is awake, even if that means that the UE would have to stay longer awake to send the ACKs. + +#### 4.5.2.3 Impact of DRX in demodulation performance + +##### 4.5.2.3.1 Simulation assumptions + +This section goes over the assumptions for the link-level simulations. + +- **Channel estimation:** Non-causal FIR filter over 2 slots: same channel estimation used for DRX and non-DRX simulations. +- **Time tracking:** 1st order loop. Same loop gain for DRX and non-DRX simulations. +- **Frequency tracking:** 1st order loop. Same loop gain for DRX and non-DRX simulations. +- **Channel models:** + +| Propagation Conditions | Geometry (dB) | +|------------------------|---------------| +| PedA, 3km/h | 5 | +| VehA, 120km/h | 0 | + +- Physical channel parameters: + +| Physical channel | Parameter | Value | Note | +|------------------|----------------|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| P-CPICH | P-CPICH Ec/Ior | -10dB | | +| P-CCPCH | P-CCPCH Ec/Ior | -12dB | Mean power level is shared with SCH. | +| SCH | SCH Ec/Ior | -12dB | Mean power level is shared with P-CCPCH. SCH includes P- and S-SCH with power split between both. | +| PICH | PICH Ec/Ior | -15dB | | +| HS-SCCH | HS-SCCH Ec/Ior | Test-specific | | +| OCNS | OCNS Ec/Ior | Necessary power so that total transmit PSD of Node B adds to one | OCNS interference is specified in table C.13 of [19]. | + +- Rx antennas: 1 +- DRX cycles (inter-TTI interval): 4, 8, and 16. HS-SCCH is received every 4, 8, and 16 subframes. +- DRX patterns: + - CRX (continuous reception): Non-DRX with inter-TTI interval of 8 is illustrated in Figure 1 (baseline reference). The pilot processing is always on. + - DRX (discontinuous reception) with inter-TTI interval of 8 is illustrated in Figure 2. The UE wakes up 1 slot before the HS-SCCH subframe begins and goes to sleep 1 slot after the last HS-SCCH subframe ends because of non-causal channel estimation. + - The DRX duration of the inter-TTI interval of 8 is 19 slots (6.33 subframes). + - Similarly, the DRX duration of inter-TTI interval of 4 and 16 are 7 slots (2.33 subframes) and 43 slots (14.33 subframes), respectively. + +![Figure 4.5.2.3.1-1: Baseline reference without DRX when inter-TTI interval is 8. The diagram shows a sequence of subframes. A red block represents a 2 ms subframe containing HS-SCCH. A green block represents one slot of Rx processing. A blue double-headed arrow indicates a period of 7 (2 ms) subframes (21 slots) between the start of one HS-SCCH subframe and the start of the next. The UE is shown processing every slot throughout the sequence.](e1ce114c43dcefce51eadcd12f2da6d2_img.jpg) + +Figure 4.5.2.3.1-1: Baseline reference without DRX when inter-TTI interval is 8. The diagram shows a sequence of subframes. A red block represents a 2 ms subframe containing HS-SCCH. A green block represents one slot of Rx processing. A blue double-headed arrow indicates a period of 7 (2 ms) subframes (21 slots) between the start of one HS-SCCH subframe and the start of the next. The UE is shown processing every slot throughout the sequence. + +Figure 4.5.2.3.1-1: Baseline reference without DRX when inter-TTI interval is 8. + +![Figure 4.5.2.3.1-2: HS-SCCH demodulation with DRX when inter-TTI interval is 8. This diagram is similar to Figure 4.5.2.3.1-1 but shows discontinuous reception (DRX). The UE wakes up one slot before the start of each 2 ms HS-SCCH subframe and goes to sleep one slot after it ends. A blue double-headed arrow indicates a DRX duration of 6.33 subframes (19 slots) centered on each HS-SCCH subframe. The UE is shown processing only during these active periods.](df935fc9efbd024af4ba77e46bb0bb19_img.jpg) + +Figure 4.5.2.3.1-2: HS-SCCH demodulation with DRX when inter-TTI interval is 8. This diagram is similar to Figure 4.5.2.3.1-1 but shows discontinuous reception (DRX). The UE wakes up one slot before the start of each 2 ms HS-SCCH subframe and goes to sleep one slot after it ends. A blue double-headed arrow indicates a DRX duration of 6.33 subframes (19 slots) centered on each HS-SCCH subframe. The UE is shown processing only during these active periods. + +Figure 4.5.2.3.1-2: HS-SCCH demodulation with DRX when inter-TTI interval is 8. + +##### 4.5.2.3.2 Simulation results + +The following figures show the block error rates (BLER) of HS-SCCH for different inter-TTI intervals. In all figures, the TTL and FTL are enabled. + +Error: + +101 + +Error: Reference source not + +![Figure 4.5.2.3.2-1 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 4. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1.5 to 10^-2.5.](7498bf530d9e13633524982a399d4439_img.jpg) + +Channel model - PedA3, Inter-TTI interval = 4 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-1 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 4. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1.5 to 10^-2.5. + +![Figure 4.5.2.3.2-1 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 4. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2.](215e8d5e5ba38df215b55049d255b2ed_img.jpg) + +Channel model - VehA120, Inter-TTI interval = 4 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-1 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 4. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2. + +Figure 4.5.2.3.2-1: BLER of CRX and DRX cases with TTL, FTL and Inter-TTI interval = 4. + +![Figure 4.5.2.3.2-2 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 8. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1 to 10^-2.](18fcacec609d0fd4816b30201438a00a_img.jpg) + +Channel model - PedA3, Inter-TTI interval = 8 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-2 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 8. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1 to 10^-2. + +![Figure 4.5.2.3.2-2 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 8. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2.](3d9c6095cbd57a6fd5fe677f428d4a07_img.jpg) + +Channel model - VehA120, Inter-TTI interval = 8 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-2 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 8. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2. + +Figure 4.5.2.3.2-2: BLER of CRX and DRX cases with TTL, FTL and Inter-TTI interval = 8. + +![Figure 4.5.2.3.2-3 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 16. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1 to 10^-2.](b53cd45f703a6a98fa703b754a69589a_img.jpg) + +Channel model - PedA3, Inter-TTI interval = 16 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-3 (Left): BLER vs HS-SCCH Ec/lor for PedA3 channel model with Inter-TTI interval = 16. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -16 dB to -8 dB. The BLER values range from approximately 10^-1 to 10^-2. + +![Figure 4.5.2.3.2-3 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 16. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2.](67a77127096ea6c8cb868e800021d803_img.jpg) + +Channel model - VehA120, Inter-TTI interval = 16 + +BLER + +HS-SCCH Ec/lor [dB] + +w/o DRX + +w/ DRX + +Figure 4.5.2.3.2-3 (Right): BLER vs HS-SCCH Ec/lor for VehA120 channel model with Inter-TTI interval = 16. The plot shows two curves: 'w/o DRX' (blue line with triangle markers) and 'w/ DRX' (red line with square markers). Both curves show a downward trend as the signal-to-noise ratio increases from -17 dB to -14 dB. The BLER values range from approximately 10^-1 to 10^-2. + +Figure 4.5.2.3.2-3: BLER of CRX and DRX cases with TTL, FTL and Inter-TTI interval = 16. + +### 4.5.3 Benefits of the concept + +Figure 4.5.3-1 shows the impact in power control rates as well as the possible DRX and DTX ratios that are achieved when the UE skips a number of subframes. The modes detailed earlier correspond to values on the x axis of 3, 7 and 15. It is apparent that the benefits are achieved pretty quickly, i.e. without having to skip a great number of subframes. + +![Figure 4.5.3-1: Benefits vs DTX/DRX rate. A dual-axis line graph showing the impact of skipping subframes on power control rates and DRX/DTX ratios. The x-axis represents the number of subframes skipped (0 to 20), with specific points at 3, 7, and 15 highlighted. The left y-axis shows PC rate (Hz) from 0.00 to 1600.00. The right y-axis shows OFF/ON ratio from 0.00% to 100.00%. Four data series are plotted: UL PC rate (blue diamonds), DL PC rate (magenta squares), DRX/ON ratio (yellow triangles), and DTX/On ratio (cyan circles). UL and DL PC rates decrease as subframes are skipped, while DRX/ON and DTX/On ratios increase and then plateau.](9fb243582ed94533ea157cb66a878190_img.jpg) + +| Number of subframes DRX'd or DTX'd | UL PC rate (Hz) | DL PC rate (Hz) | DRX/ON ratio (%) | DTX/On ratio (%) | +|------------------------------------|-----------------|-----------------|------------------|------------------| +| 0 | 1500 | 1500 | 0 | 0 | +| 1 | 750 | 1250 | 50 | 15 | +| 2 | 500 | 850 | 65 | 45 | +| 3 | 380 | 620 | 75 | 58 | +| 4 | 300 | 500 | 80 | 65 | +| 5 | 250 | 420 | 83 | 70 | +| 6 | 210 | 370 | 85 | 74 | +| 7 | 180 | 320 | 86 | 77 | +| 8 | 160 | 280 | 87 | 79 | +| 9 | 140 | 250 | 88 | 81 | +| 10 | 130 | 220 | 89 | 83 | +| 11 | 120 | 200 | 90 | 84 | +| 12 | 110 | 180 | 91 | 85 | +| 13 | 100 | 170 | 91 | 86 | +| 14 | 90 | 160 | 92 | 87 | +| 15 | 80 | 150 | 92 | 88 | +| 16 | 70 | 140 | 93 | 89 | +| 17 | 60 | 130 | 93 | 90 | +| 18 | 50 | 120 | 94 | 91 | +| 19 | 40 | 110 | 94 | 92 | + +Figure 4.5.3-1: Benefits vs DTX/DRX rate. A dual-axis line graph showing the impact of skipping subframes on power control rates and DRX/DTX ratios. The x-axis represents the number of subframes skipped (0 to 20), with specific points at 3, 7, and 15 highlighted. The left y-axis shows PC rate (Hz) from 0.00 to 1600.00. The right y-axis shows OFF/ON ratio from 0.00% to 100.00%. Four data series are plotted: UL PC rate (blue diamonds), DL PC rate (magenta squares), DRX/ON ratio (yellow triangles), and DTX/On ratio (cyan circles). UL and DL PC rates decrease as subframes are skipped, while DRX/ON and DTX/On ratios increase and then plateau. + +Figure 4.5.3-1: Benefits vs DTX/DRX rate + +### 4.5.4 Open issues of the concept + +## 4.6 Restricted HS-SCCH + +### 4.6.1 Description of the concept + +The objective of the restricted HS-SCCH is to reduce HS-SCCH power requirements compared to the existing Rel-6 HS-SCCH (henceforth called legacy HS-SCCH) by + +- eliminating HS-SCCH transmissions during HARQ retransmissions, +- reducing the payload carried over the HS-SCCH during new transmissions, and +- jointly encoding the entire HS-SCCH payload and transmitting the codeword over all three slots of HS-SCCH transmission, in contrast to the existing scheme where part 1 and part 2 HS-SCCH information are encoded and transmitted independently. We discuss in Section 4.6.1.5 how this affects the ability of the UE to detect the HS-SCCH in time to start buffering HS-PDSCH signals. + +Under the proposed scheme, higher layers configure each HSDPA flow to use either the legacy HS-SCCH or the restricted HS-SCCH that is proposed in this contribution, depending on the type of traffic carried on the flow (e.g., + +VoIP or best effort) and on whether or not the UE is capable of receiving the restricted HS-SCCH. Once a flow is thus configured, the Node-B transmits the specified type of HS-SCCH to the UE whenever that flow is scheduled. + +The physical channel slot structure of the restricted HS-SCCH is the same as that of the legacy HS-SCCH. As in the current specification, the network configures each cell with a set of HS-SCCH channelization codes at SF128, and configures each HSDPA UE to monitor at most four of these codes. Any of the HS-SCCH channelization codes in the cell may be used in any TTI to carry either a legacy HS-SCCH or an restricted HS-SCCH. In other words, both the legacy HS-SCCH and the restricted HS-SCCH share the same set of channelization codes, and there is no need to reserve certain HS-SCCH codes for the enhanced mode of operation. + +It is possible for a user to use both the legacy HS-SCCH and the restricted HS-SCCH if the user is configured with both a VoIP flow and a non-VoIP flow simultaneously. In this case, any one of the HS-SCCH codes monitored by the UE may be used in a given TTI to carry a legacy HS-SCCH or the restricted HS-SCCH in a TTI, depending on which of the user's flows is scheduled. + +#### 4.6.1.1 HARQ Operation and Signalling + +The following changes to HARQ operation are made for an HSDPA flow that is configured to use the restricted HS-SCCH. + +- Synchronous HARQ retransmissions are used for the flow. In other words, the $n$ th HARQ transmission for a packet is implicitly scheduled at a fixed time following the $(n-1)$ th failed transmission, provided that HARQ is not terminated. This allows the UE to determine the time of a retransmission without relying on HS-SCCH signalling. The scheduler may still terminate HARQ for any packet arbitrarily at any time. New transmissions can be scheduled at any time, just like in the current operation. +- The restricted HS-SCCH is transmitted along with a new HARQ transmission for this flow. No HS-SCCH is transmitted for a retransmission. The possible issue of buffer corruption due to this is addressed in Section 4.6.4.1.2. +- A maximum limit is imposed on the number of HARQ transmissions for this flow. The maximum number of HARQ transmissions for the flow is configured by higher layers. Since there is no HS-SCCH transmission during retransmissions, there is a need to bound the number of retransmissions that the UE will consider after the initial transmission. In the absence of such a restriction, one can think of scenarios when the UE will be unable to determine exactly when the Node-B has terminated HARQ for a packet, thereby leading to unnecessary NACK transmissions on the HS-DPCCH. +- The restricted HS-SCCH does not carry any HARQ information. The HARQ process number is not required because of synchronous retransmissions: there is no ambiguity at the UE in associating a retransmission with the corresponding first transmission. When the restricted HS-SCCH is used, the redundancy version (RV) parameter is implicitly determined by the HARQ transmission number. The design of the sequence of RV parameters as a function of the HARQ transmission number is FFS. The new data indicator is not required since the restricted HS-SCCH is transmitted only for new transmissions. + +#### 4.6.1.2 Signalling of transport format + +The following modifications apply to HSDPA flows that are associated with the restricted HS-SCCH. + +- Only QPSK modulation is allowed. +- Only one OVSF code is allowed per HS-DSCH transmission, whereby the code for any transmission is chosen from a set of up to four codes that is configured by higher layers for that flow. Higher layers also signal a fixed mapping between the set of HS-SCCH codes that are monitored by the UE and a corresponding set of HS-PDSCH channelization codes, such that the HS-PDSCH channelization code used in a new HS-DSCH transmission is uniquely determined by the HS-SCCH code on which this transmission is signalled, without explicitly transmitting any channelization code information on the HS-SCCH. It is important to note that this scheme does not impose any additional restriction on the ability of the MAC-hs scheduler to schedule a particular set of code multiplexed VoIP users, compared to a scheme where one code from a pre-defined set of four channelization codes is explicitly signalled on the HS-SCCH using 2 bits. An example of how the network can allocate codes using this scheme is the following. If there are $M$ HS-SCCH channels configured in a cell, no more than $M$ HS-PDSCH codes may be used in one TTI for transmission of VoIP flows, due to the restriction that each VoIP flow may use no more than one code. Therefore, the network may impose a one-to-one mapping between the set of $M$ HS-SCCH channels and a set of $M$ HS-PDSCH codes, and use any remaining HS-PDSCH codes only for non-VoIP flows. An example of this scheme is shown in Figure 4.6.1.2-1, where $M=6$ HS-SCCH + +channels are available, and 10 OVSF codes, numbered 7 through 16, are available for HS-PDSCH. The network may establish a mapping between HS-SCCH and HS-PDSCH codes as shown in the figure. The network would then signal portions of this mapping to each UE based on the set of HS-SCCH channels that are monitored by that UE. The channelization code mapping is used only for transmissions that use the restricted HS-SCCH. Legacy HS-SCCH will continue to operate as specified in the Release-6 specification, whereby any HS-SCCH channel that is monitored by the UE may be used in conjunction with any set of HS-PDSCH channelization codes. + +![Diagram showing the mapping between HS-SCCH channels and HS-PDSCH codes. HS-SCCH Channel # 1 maps to HS-PDSCH Code # 7, Channel # 2 to Code # 8, Channel # 3 to Code # 9, Channel # 4 to Code # 10, Channel # 5 to Code # 11, and Channel # 6 to Code # 12. Code # 6 is marked as 'Unavailable for HS-PDSCH', while codes 7 through 13 are marked as 'Available for HS-PDSCH'.](a0eb8d30ac11ba97b2733c187b89ff22_img.jpg) + +| | | | | | | | | | +|-------------------|-----------------|---|---------------|---|----|----|----|----| +| HS-SCCH Channel # | | 1 | 2 | 3 | 4 | 5 | 6 | | +| | ↓ | ↓ | ↓ | ↓ | ↓ | ↓ | ↓ | | +| HS-PDSCH Code # | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | +| | Unavailable for | | Available for | | | | | | +| | HS-PDSCH | | HS-PDSCH | | | | | | + +Diagram showing the mapping between HS-SCCH channels and HS-PDSCH codes. HS-SCCH Channel # 1 maps to HS-PDSCH Code # 7, Channel # 2 to Code # 8, Channel # 3 to Code # 9, Channel # 4 to Code # 10, Channel # 5 to Code # 11, and Channel # 6 to Code # 12. Code # 6 is marked as 'Unavailable for HS-PDSCH', while codes 7 through 13 are marked as 'Available for HS-PDSCH'. + +**Figure 4.6.1.2-1: Mapping between HS-SCCH channels and HS-PDSCH codes that enables the UE to determine the transmitted HS-PDSCH code without explicit signaling on HS-SCCH.** + +- The channelization code used for a retransmission must be the same as the one used in the original transmission of that MAC-hs PDU. +- Choice of transport block size is limited to one of at most four different pre-configured transport block sizes. The set of up to four allowed block sizes is configured by higher layers. The restricted HS-SCCH signals an index into this set of block sizes. + +The selection of the above restrictions is based on the characteristics of VoIP transmissions. Simulation studies have shown that there is no significant degradation in VoIP performance or capacity by eliminating the use of 16-QAM modulation and by limiting the number of HS-PDSCH codes per transmission to one. Simulations have also shown that no more than three block sizes are used most of the time for VoIP transmissions. Multiple block sizes are required to support silence (SID) frames and voice frame aggregation in the MAC-hs layer, whereby the MAC-hs scheduler concatenates one or more MAC-d PDUs in one MAC-hs PDU. + +The size of the pre-configured set of channelization codes for a flow is selected to balance a trade-off between HS-SCCH signalling requirements and the flexibility that is provided to the scheduler in code multiplexing different VoIP users in one TTI. If the size of the set is larger than four, we will require at least one bit of additional HS-SCCH signalling for channelization code information, and thereby increase its transmit power requirements. If the size of the pre-configured set of codes is smaller than four, the scheduler may find it difficult to multiplex certain sets of users together in a TTI. If the scheduler selects a set of K users to be code multiplexed in a TTI, then for successful allocation of unique codes to each of them, the restricted channelization sets for the K users must satisfy the following criterion: there exists a code $c(k)$ in the $k$ th user's restricted code set such that $c(k1) \neq c(k2)$ whenever $k1 \neq k2$ . This becomes less likely as the size of the restricted code set is reduced. + +#### 4.6.1.3 Coding for HS-SCCH + +A block diagram of the restricted HS-SCCH coding chain is shown in Figure 4.6.1.3-1. The coding chain is described below. + +![Flowchart of the coding process for restricted HS-SCCH. The process starts with TBS (2 bits) entering a CRC Computation block. The output of CRC Computation (16 bit CRC) enters a UE ID Masking block, which also receives UE ID (16 bits). The output of UE ID Masking enters a UE-Specific CRC Addition block along with the TBS (2 bits). The output of UE-Specific CRC Addition (18 bits) enters a Convolutional Code block (r=1/3, K=9). The output of Convolutional Code (78 bits) enters a Rate Matching block. The output of Rate Matching (120 bits) enters an Interleaver block. The output of Interleaver (120 bits) is the final HS-SCCH.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +graph TD + TBS[TBS +2 bits] --> CRC_Comp[CRC Computation] + CRC_Comp -- "16 bit CRC" --> UE_ID_Mask[UE ID Masking] + UE_ID[UE ID +16 bits] --> UE_ID_Mask + UE_ID_Mask --> UE_Spec_CRC[UE-Specific CRC Addition] + TBS -- "2 bits" --> UE_Spec_CRC + UE_Spec_CRC -- "18 bits" --> Conv_Code["Convolutional Code +r=1/3, K=9"] + Conv_Code -- "78 bits" --> Rate_Match[Rate Matching] + Rate_Match -- "120 bits" --> Interleave[Interleaver] + Interleave -- "120 bits" --> HS_SCCH[HS-SCCH] + +``` + +Flowchart of the coding process for restricted HS-SCCH. The process starts with TBS (2 bits) entering a CRC Computation block. The output of CRC Computation (16 bit CRC) enters a UE ID Masking block, which also receives UE ID (16 bits). The output of UE ID Masking enters a UE-Specific CRC Addition block along with the TBS (2 bits). The output of UE-Specific CRC Addition (18 bits) enters a Convolutional Code block (r=1/3, K=9). The output of Convolutional Code (78 bits) enters a Rate Matching block. The output of Rate Matching (120 bits) enters an Interleaver block. The output of Interleaver (120 bits) is the final HS-SCCH. + +**Figure 4.6.1.3-1: Coding for restricted HS-SCCH** + +- **CRC addition.** A 16-bit UE-specific CRC is added to the 2-bit TBS information. To do this, a 16-bit CRC is first computed corresponding to the 2 TBS bits, according to the specification in Section 4.2.1 in [4]. The CRC remainder is then masked with the 16-bit UE ID as specified in Section 4.6.4 in [4]. The block obtained after CRC addition is 18 bits long. +- **Channel coding.** The 18-bit block is encoded using the rate 1/3, constraint length 9 convolutional code that is used in the current HS-SCCH specification. The output of the encoder has 78 coded bits, including tail bits. +- **Rate matching.** Repetition is performed according to the specification in Section 4.2.7 in [4] to match the 78 coded bits to 120 physical channel bits. +- **Interleaving.** A channel interleaver is used on the coded bits after rate matching according to the specification of the “2nd interleaver” in Section 4.2.11 in [4]. +- **Physical channel mapping.** The 120 bits from the output of the channel interleaver are mapped in sequence to the 120 physical channel bits available in the HS-SCCH subframe. + +#### 4.6.1.4 HS-SCCH physical channel structure + +The physical channel structure of the restricted HS-SCCH is identical to that of the legacy HS-SCCH: it has a fixed rate of 60kbps, operates at SF=128 and is transmitted over an HS-SCCH subframe that is 3 slots long. Timing of the HS-SCCH relative to HS-PDSCH also remains unchanged. + +#### 4.6.1.5 UE reception of the restricted HS-SCCH + +One of the consequences of encoding HS-SCCH information jointly across the whole 2ms TTI is that the UE will need to wait till the end of the HS-SCCH TTI in order to decode it. However, it may be desirable for the UE to detect the information it requires to start buffering and processing HS-PDSCH signals *before* the beginning of the corresponding HS-PDSCH transmission. A simple method is suggested in this section that can be used by the UE to detect the HS-SCCH after receiving only the first slot of HS-SCCH transmission. + +The method exploits the fact that there are only four possible HS-SCCH codewords—corresponding to the four choices for transport block size—that could possibly be intended for a particular UE. The total number of codewords that may be transmitted on the restricted HS-SCCH is corresponding to the different values taken by the 16-bit UE ID and the 2-bit TBS. Since the UE ID is fixed for any particular UE, it is only required to detect the presence of any of the four codewords that correspond to the UE. The UE may pre-compute the list of four HS-SCCH codewords that are consistent with its UE ID, and store only the portions of these codewords that are transmitted in the first slot. Upon receiving the first slot of HS-SCCH signal, the UE would compute a confidence metric by comparing the partial received signal with the stored set of four partial codewords, and use the maximum of the four metrics as a measure of confidence that the corresponding HS-SCCH transmission was intended for it. The confidence metric may be computed based on the distance metric between the received signal and the stored partial codewords, or, equivalently, as the correlation of the received signal with the partial codewords. A decision to start buffering the corresponding HS-PDSCH code can be made by performing a threshold test on this confidence measure. Choice of the threshold can be made to ensure a desired low probability of mis-detection. + +Once the UE detects that a particular restricted HS-SCCH transmission is intended for it, no other information is required from the HS-SCCH for the UE to start buffering the HS-PDSCH signal, since the channelization code is known from the HS-SCCH channel number, and modulation is always QPSK. + +### 4.6.2 Analysis of the concept + +The HS-SCCH fields carried on the restricted HS-SCCH for new HARQ transmissions are described below. Table 4.6.2-1 provides a comparative summary of the HS-SCCH payload for the legacy design and the proposed restricted HS-SCCH. + +**Table 4.6.2-1: Comparison of payload between the restricted HS-SCCH and legacy HS-SCCH.** + +| | Number of bits for the existing HS-SCCH | Number of bits for the new HS-SCCH mode | +|--------------------------------------|-----------------------------------------|-----------------------------------------| +| New data indicator | 1 | 0 | +| Redundancy and constellation version | 3 | 0 | +| HARQ process | 3 | 0 | +| Transport block size | 6 | 2 | +| Modulation scheme | 1 | 0 | +| Channelization code set | 7 | 0 | +| UE ID | 16 | 16 | +| Total number of bits | 37 | 18 | + +- **Channelization-code-set (CCS) information (0 bits).** As described in Section 4.6.1.2, the restricted HS-SCCH does not require explicit signalling of channelization code information. +- **Modulation scheme information (0 bits).** Signalling of modulation is not required since 16-QAM is not allowed. +- **Transport block size (TBS) information (2 bits).** As described in Section 4.6.1.2, the HS-SCCH needs to identify one of four pre-defined block sizes for a VoIP flow, which requires 2 bits. The HS-SCCH transmits a 2-bit index into the pre-configured set of at most four transport block sizes that is configured by higher layers. +- **HARQ process information (0 bits).** Signalling of HARQ process information is not required because of synchronous HARQ. +- **Redundancy and constellation version (0 bits).** The RV parameters are derived from the HARQ transmission number, and are therefore not required to be signalled. + +- **New data indicator (0 bits).** Since the restricted HS-SCCH is transmitted only for new transmissions, the new data indicator is not required. +- **UE identity (16 bits).** In order to signal the identity of the intended recipient UE, the restricted HS-SCCH will continue to use the 16-bit H-RNTI as the UE identity. + +Based on the reduction in payload alone, and assuming that coding gain remains unchanged, the relative gain in HS-SCCH performance can be calculated as dB. The restricted HS-SCCH also benefits from an additional coding gain, since it operates at a lower code rate than the existing HS-SCCH, which uses puncturing. Furthermore, in addition to the gains due to payload reduction and more coding, the restricted HS-SCCH yields a gain in fade margins because of joint encoding of the entire payload and transmission over three slots using an interleaver. + +### 4.6.3 Benefits of the concept + +- The new HS-SCCH specification requires only few changes with respect to the current standards specification. +- The required power for transmitting HS-SCCH is significantly reduced. +- Blind detection techniques for the UE are avoided. +- Soft buffer corruption in the UE is avoided as the presence of HS-SCCH is identical with the new data indication. + +### 4.6.4 Open issues of the concept + +#### 4.6.4.1 Unexpected and Erroneous Events + +In this section, we discuss some unexpected error events that may occur when the restricted HS-SCCH is used. It is shown that some of the error events can be mitigated by following some simple rules at the transmitter, that the error events that cannot be eliminated in this manner have a very small probability of occurrence, and that each error event leads to a possible loss of no more than one MAC-hs PDU. + +##### 4.6.4.1.1 ACK/NACK not received in response to a new transmission + +Suppose that in a TTI in which a UE is not expecting a HARQ retransmission, the Node-B transmits a new HARQ transmission to the UE along with the corresponding restricted HS-SCCH, but the UE misses detection of the HS-SCCH. Without further corrective action the packet will be lost in this case, since HS-SCCH is not transmitted with the retransmissions, and therefore the UE will never be able to receive any of the HARQ transmissions for this packet. + +This error event can be resolved by requiring that whenever the Node-B does not detect an ACK/NACK corresponding to a new transmission, it will transmit the new transmission again, along with the HS-SCCH. + +##### 4.6.4.1.2 Buffer corruption + +Consider the case when the UE is expecting a retransmission of a packet in a specific TTI, but the Node-B decides to transmit a fresh transmission of a new packet to the UE in that TTI. This may happen if the Node-B decides to pre-empt the retransmission with a fresh transmission, or if the Node-B had incorrectly detected an ACK when a NACK was transmitted. Suppose further that the UE misses HS-SCCH detection for this new transmission. In this case the UE will assume that it has received a retransmission of the old packet, and will HARQ-combine the received signal with the contents of the IR buffer for the old packet. This will lead to buffer corruption for the new packet, with the likely result that the new packet is lost. The effect of the error event is restricted to just one packet, however, since the UE will be able to receive the next new transmission by decoding the corresponding HS-SCCH. + +Probability of the above error event is reduced by the use of a limit on the maximum number of HARQ transmissions, since it reduces the probability of the Node-B terminating HARQ of a packet without the UE's knowledge. In fact, if the MAC-hs scheduler ensures that a retransmission is never pre-empted before exhausting the maximum number of transmissions, then the only way in which buffer corruption could occur is due to a NACK -> ACK detection error followed by mis-detection of the HS-SCCH for the new transmission. Assuming independent errors on the HS-DPCCH and HS-SCCH, the probability of this event is $P[\text{NACK} \rightarrow \text{ACK}] \cdot P[\text{HS-SCCH misdetection}]$ , which is smaller than 0.01%. Since this probability is much smaller than the target error rate for VoIP kind of applications, we can conclude that buffer corruption due to the restricted HS-SCCH is not a significant problem. + +##### 4.6.4.1.3 HS-SCCH misdetection followed by ACK false alarm + +This is a scenario in which the restricted HS-SCCH would perform better than the legacy HS-SCCH. Consider the case when HS-SCCH detection fails for a transmission, and the UE therefore does not send ACK/NACK in response, but the Node-B incorrectly detects an ACK (ACK false alarm). This causes the loss of one packet. The probability of this error event in the case of new transmissions is exactly the same for both legacy and restricted HS-SCCHs. The restricted HS-SCCH has the added advantage over the legacy channel in that, since the restricted HS-SCCH is not transmitted during retransmissions, this error event can never occur during retransmissions. The probability of this error event during a retransmission is the same as in the case of a new transmission when the legacy HS-SCCH is used. The probability that a packet is lost due to this error event can be computed as $P[\text{HS-SCCH misdetection}] * P[\text{DTX} \rightarrow \text{ACK}]$ , which is in the order of 0.01%. The effect of such an error is localized to only one packet, since the next fresh transmission will be received once the corresponding HS-SCCH is correctly decoded. + +##### 4.6.4.1.4 HS-SCCH misdetection followed by NACK false alarm + +This is the same scenario as in Section 4.6.4.1.3 except that DTX is interpreted as NACK on the HS-DPCCH. This will likely not lead to a packet loss in the case of the legacy HS-SCCH since it would just lead to another retransmission which will be received by the UE. However, with the restricted HS-SCCH, this packet will be lost since the UE will not receive any retransmissions of this packet. This is also a rare event, with a probability $P[\text{HS-SCCH misdetection}] * P[\text{DTX} \rightarrow \text{NACK}] \approx 0.01\%$ that a packet is lost in this manner. The effect of this error event is also localized to just one packet. + +## 4.7 HS-SCCH-less operation + +### 4.7.1 Description of the Concept + +HS-SCCH adds a significant overhead to each HS-DSCH transmission. Although this overhead is relatively small for transmission of large packets of data, such as in the presence of full-buffer type of traffic, it is considerable for IMS real-time services such as VoIP. + +This concept alleviates this overhead by allowing for each UE 2 HS-DSCH subframe formats to be transmitted without HS-SCCH. The new subframe format is the same as the current HS-DSCH subframe format, except that: + +- The HS-SCCH is not transmitted. +- Only pre-defined 2 TB sizes are allowed. (semi-static, configurable per UE) +- Only QPSK is allowed. +- Only one pre-defined HS-PDSCH code can be used per UE. (semi-static, configured per UE) + - Each UE is told via signalling to only listen to one particular OVSF code for transmissions using the new subframe formats. The UE must therefore monitor that code for a transmission in addition to monitoring the HS-SCCH as in Release 5/6. +- HARQ is limited to: + - 2 retransmissions. + - Synchronous IR. + - The redundancy version is pre-defined. (static, non configurable) +- The HS-PDSCH CRC is 24-bits long and is UE specific. + - Its generation follows the same procedure as the CRC currently on the HS-SCCH and therefore is covered by the 16-bit UE MAC ID. +- The UE does not transmit negative acknowledgements (NAK) +- The UE attempts reception of the regular HS-SCCH in parallel to the blind detection over the HS-PDSCH to detect scheduling with the old and with the new slot format. + +### 4.7.2 Analysis of the concept + +#### 4.7.2.1 Transmission waveform and timing + +Figure 4.7.2.1-1 depicts transmissions only using the existing subframe format. In contrast, Figure 4.7.2.1-2 depicts a transmission with a new subframe format. The new format disables transmission of the HS-SCCH, as well as negative acknowledgements. + +![Figure 4.7.2.1-1: Transmission waveform and timing using the existing HS-DSCH subframe format. The diagram shows a sequence of 15 subframes. The 15th subframe is highlighted with a bracket and contains three colored blocks: yellow, green, and red. Below the subframes, a red arrow points to a specific subframe, which is shown in a detailed view below. This detailed view shows two rows of data blocks, with the top row containing 7 blocks and the bottom row containing 6 blocks, separated by a vertical dotted line.](0eb57eefa7cd45d30e68829ca8a03843_img.jpg) + +Figure 4.7.2.1-1: Transmission waveform and timing using the existing HS-DSCH subframe format. The diagram shows a sequence of 15 subframes. The 15th subframe is highlighted with a bracket and contains three colored blocks: yellow, green, and red. Below the subframes, a red arrow points to a specific subframe, which is shown in a detailed view below. This detailed view shows two rows of data blocks, with the top row containing 7 blocks and the bottom row containing 6 blocks, separated by a vertical dotted line. + +Figure 4.7.2.1-1: Transmission waveform and timing using the existing HS-DSCH subframe format + +![Figure 4.7.2.1-2: Transmission waveform and timing using the proposed HS-DSCH subframe format. The diagram shows a sequence of 15 subframes. The 15th subframe is highlighted with a bracket and contains three colored blocks: yellow, green, and red. Below the subframes, a red arrow points to a specific subframe, which is shown in a detailed view below. This detailed view shows two rows of data blocks, with the top row containing 7 blocks and the bottom row containing 6 blocks, separated by a vertical dotted line. The difference from Figure 4.7.2.1-1 is that the first subframe in the sequence is missing, indicating a different subframe format.](86e1f8551d4922ea8fa197f96fe4098b_img.jpg) + +Figure 4.7.2.1-2: Transmission waveform and timing using the proposed HS-DSCH subframe format. The diagram shows a sequence of 15 subframes. The 15th subframe is highlighted with a bracket and contains three colored blocks: yellow, green, and red. Below the subframes, a red arrow points to a specific subframe, which is shown in a detailed view below. This detailed view shows two rows of data blocks, with the top row containing 7 blocks and the bottom row containing 6 blocks, separated by a vertical dotted line. The difference from Figure 4.7.2.1-1 is that the first subframe in the sequence is missing, indicating a different subframe format. + +Figure 4.7.2.1-2: Transmission waveform and timing using the proposed HS-DSCH subframe format + +Note how new and old subframe formats can be intermixed. Note also that in this depiction of the timing the ACK processing time is unchanged for the new formats. + +To implicitly convey the control information in the HS-SCCH, the following list goes over the HS-SCCH fields and their mapping to the HS-SCCH less operation: + +- Modulation used (1 bit): + - Always QPSK. +- OVSF codes used (7 bits): + - One pre-defined (semi-static) code. (P=1) + +- Transport Format Resource Indicator (6 bits): + - Only 2 possible values. Blindly determined by the UE. +- HARQ process number (3 bits): + - Not needed because synchronous IR is used. +- Redundancy version (3 bits): + - Pre-defined (static) redundancy versions for each transmission. +- New data indicator (1 bit): + - Not needed because synchronous IR with pre-defined redundancy versions is used. +- CRC / User identity (16 bits): + - Not needed because carried over HS-PDSCH transmission. + +#### 4.7.2.2 UE complexity discussion + +When an HS-SCCH-less transmission occurs the UE does not know the payload size, or the HARQ information for combining. The UE must therefore blindly decode for both of the possible payload sizes. Furthermore, since synchronous IR with 3 transmissions is used, the UE must decode for all 3 possibilities: current TTI is a 1st transmission, current TTI is a 2nd transmission and current TTI is a 3rd transmission. The UE must therefore perform a total of $2 \cdot 3 = 6$ blind decodes. + +The first 3 blind decodes are based on the assumption that a somewhat small payload was transmitted, of at most N1 bits. This would correspond, for example, to an AMR-NB full-rate frame. The next 3 blind decodes are based on the assumption that a very small payload was transmitted, of at most N2 bits. Both N1 and N2 are semi-static values. + +In order to minimize complexity we set + +- N1 = 353 bits; this is sufficient to carry a 12.2 kbit/s AMR-NB or 12.6 kbit/s AMR-WB speech frame. +- N2 = 161 bits; this is sufficient to carry an AMR-NB or AMR-WB SID frame. + +To control complexity of the de-interleaving and rate-matching process we restrict the redundancy versions of successive transmissions to be $X_{rv} = (0, 0, 0)$ . In other words energy combining (“Chase” combining) is used. There is virtually no performance loss in fixing the redundancy versions in such a manner, since the code-rate of these small payloads is already close or at the lowest code-rate achievable by our code ( $R=1/3$ ). + +With these assumptions in hand, the main complexity resides in the ability to performing the 6 decodes. The first 3 decodes are for a payload of at most N1 = 353 bits. The 3 next decodes are for a payload of at most N2 = 161. The total number of bits that need to be decoded is therefore at most $3 \cdot 353 + 3 \cdot 161 = 1.542$ bits. + +Consider that the lowest capability UE (Categories 11 and 12) must be able to Turbo decode 3.630 bits in that same amount of time (and process up to 14.000 soft channel bits). Furthermore the UEs typically deployed nowadays can decode 7.298 bits. + +Noting that there is no other Turbo decoding on the HS-DSCH required when HS-SCCH-less operation occurs, we conclude that the proposed HS-SCCH-less operation can be accommodated within the existing Release 5 UE complexity. + +Note that parallel decoding of the HS-SCCH within a subframe happens in the same way as in regular Rel-5 operation. + +#### 4.7.2.3 CRC discussion + +If a 16-bit CRC was to be used for HS-PDSCH transmissions for the HS-SCCH-less formats, instead of the traditional 24-bit CRC, the false alarm rate would be $2^{-16}$ . + +At each TTI the UE decodes 6 possible ways; if any of these decodes incorrectly triggers the CRC to check, a packet will be incorrectly forwarded to the upper-layers. + +With 6 decodes per TTI and a false alarm rate of $2^{-16}$ , we get that the mean time between false alarms will be: + +With a 24-bit CRC we get a false alarm rate of + +From the above false alarm computations for both CRC lengths, retaining the 24-bit CRC for HS-PDSCH is, therefore, recommended. Since the UE MAC ID is 16 bits, just part of the HS-PDSCH CRC will be covered by the UE MAC ID. + +#### 4.7.2.4 VoIP and best effort capacity simulations + +##### 4.7.2.4.1 Simulation assumptions + +| Multipath channel models | AWGN, PB3, and VA30
Fader type: JTC. | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----|----|-------|-----|---|---------|-----|---|---------|-----|---|--------|-----|---|------|-----|---|------|-----|---| +| Cell layout and link budget | According to TR 25.848:
Site-to-site distance: 2.8 km.
3-cells per site.
Node B Tx power: 44 dBm.
Log-normal shadowing: 8 dB.
Shadow-correlation between co-located cells: 1.0.
Shadow-correlation between non co-located cells: 0.5.
Carrier frequency: 2 GHz.
Bandwidth: 5 MHz.
Number of UE antennas: 1. | | | | | | | | | | | | | | | | | | | | | | +| Node B resources | Power reserved for common channels and DPCH for all users: 7.5 Watt (30%)
3 Watt for common channels + 1 Watt / ~100 users for DPCH.
Remaining power for all HS-SCCH and HS-PDSCH: 17.5 Watt
OVSF codes reserved for common channels:
Channel SF Nb
CPICH 256 1
P-CCPCH 256 1
S-CCPCH 256 1
E-AGCH 256 1
AICH 256 1
PICH 256 1
OVSF code usage modeled for dedicated channels:
F-DPCH
Soft-handover overhead: 1.8
Up to 8 simultaneous HS-SCCH transmissions allowed.
HS-SCCH code collisions were not modelled. | Channel | SF | Nb | CPICH | 256 | 1 | P-CCPCH | 256 | 1 | S-CCPCH | 256 | 1 | E-AGCH | 256 | 1 | AICH | 256 | 1 | PICH | 256 | 1 | +| Channel | SF | Nb | | | | | | | | | | | | | | | | | | | | | +| CPICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| P-CCPCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| S-CCPCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| E-AGCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| AICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| PICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| IMS VoIP packet format and overheads | VoIP packet with payload according to RFC3267.
24-bit ROHC overhead.
16-bit RLC overhead.
No voice packet bundling. | | | | | | | | | | | | | | | | | | | | | | +| VoIP traffic details | AMR 12.2 kbps.
SID transmitted every 160 ms of silence.
Voice activity model:
50% voice activity.
ON and OFF periods of duration exponentially distributed, of average 3 seconds.
100 ms maximum delay bound with SDU discarding at the MAC-hs. | | | | | | | | | | | | | | | | | | | | | | +| Best-effort (BE) traffic | Full-buffer traffic.
5 users per cell at fixed geometries {0, 1.5, 2.5, 3, 5dB}. 1
SDU size: 320 bit | | | | | | | | | | | | | | | | | | | | | | +| Signalling traffic | SRB, RTCP, and SIP not modeled. | | | | | | | | | | | | | | | | | | | | | | +| Parameters of New HS-DSCH Format | Synchronous IR.
TB sizes: 137 bits, and 317 bits with 24 Bit CRC.
No DRX or DTX.
Each user is assigned one of the available HS-PDSCH codes at call setup.
OVSF code collision and fragmentation is explicitly modelled. | | | | | | | | | | | | | | | | | | | | | | +| Scheduler | Voice traffic scheduled first, then best-effort (BE) traffic scheduled next.
Voice traffic scheduler:
Exponential scheduling rule with .
BE traffic scheduler:
Proportional Fair. | | | | | | | | | | | | | | | | | | | | | | +| Feedback delays | CQI delay: 8 slots from time of measure to start of HS-PDSCH transmission.
HARQ delay: minimum 15 slots from end of a transmission to start of a re-transmission. | | | | | | | | | | | | | | | | | | | | | | +| Error modelling | HS-PDSCH:
Threshold-based decoder.
Energy combining assumed.
HS-SCCH: Threshold-based decoder.
CQI: perfect estimation with quantization errors.
HS-DPCCH: HARQ feedback errors modelled with ACK false alarm probability of $10^{-3}$ and ACK mis-detection probability of $10^{-2}$ .
No channel estimation modelled. | | | | | | | | | | | | | | | | | | | | | | + +1 The geometries were fixed in order to accelerate simulation run-time. These geometries were randomly selected to represent typical values in a system. + +##### 4.7.2.4.2 Simulation results + +The system integrates modeling of simultaneously using new formats with synchronous IR and 3 transmissions as well as old formats with asynchronous IR and 4 transmissions. The simulations also explicitly track OVSF code usage for the HS-PDSCH, model code collision and OVSF space segmentation. + +The results highlight the relationship between real-time services load and best-effort (BE) throughput by characterizing the increase in BE throughput due to the introduction of the new subframe format for the real-time services. + +The real-time service modeled in these simulations is VoIP IMS using the AMR 12.2 kbit/s vocoder. The simulations consider 5 BE users per cell with the following assigned geometries {0, 1.5, 2.5, 3, 5dB}. Detailed simulation assumptions are explained in section 4.7.2.4.1. + +Figure 4.7.2.4.2-1, Figure 4.7.2.4.2-2 and Figure 4.7.2.4.2-3 plot the variation of total best-effort throughput with increasing number of VoIP users for systems without and with the introduction of the new subframe format. Results exhibit a significant increase in BE throughput for the range of 50-100 VoIP users. As observed, the relative performance gains in terms of BE throughput increases as the number of VoIP users (allowed to use to the new subframe format) in the system increase. As the system approaches the VoIP user capacity, the BE throughput goes to 0. This is because the BE users utilize only the residual throughput and are scheduled after the VoIP users. + +![Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Legacy and New subframe format systems in an AWGN channel. The graph shows that the new subframe format maintains higher BE throughput as VoIP users increase compared to the legacy system.](cf2d4d253cf03d94d0fd5544f4e3ca24_img.jpg) + +AWGN: Best Effort Throughput for 5 fixed Geometry Users + +| VoIP Users | Legacy (Kbps) | With new subframe format (Kbps) | +|------------|---------------|---------------------------------| +| 0 | 3150 | 3150 | +| 50 | 1900 | 2250 | +| 100 | 550 | 1300 | +| 150 | 50 | 400 | +| 160 | 10 | 100 | +| 170 | 0 | 50 | +| 180 | 0 | 50 | +| 190 | 0 | 50 | +| 200 | 0 | 50 | + +Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Legacy and New subframe format systems in an AWGN channel. The graph shows that the new subframe format maintains higher BE throughput as VoIP users increase compared to the legacy system. + +**Figure 4.7.2.4.2-1: Performance Results – AWGN channel** + +![Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Ped B-3kmh channel. The graph compares 'Legacy' (blue line with diamonds) and 'With new subframe format' (magenta line with squares). Throughput decreases as users increase, but is significantly higher for the new format.](c9829c80e5f6e9384df5f75e24da4c25_img.jpg) + +Ped B-3kmh: Best Effort Throughput for 5 fixed Geometry Users + +| VoIP Users | Legacy (Kbps) | With new subframe format (Kbps) | +|------------|---------------|---------------------------------| +| 0 | 1550 | 1550 | +| 10 | 1180 | 1350 | +| 25 | 820 | 1000 | +| 50 | 250 | 480 | +| 60 | 80 | 280 | +| 70 | 40 | 100 | +| 75 | 20 | 80 | +| 80 | 10 | 60 | +| 90 | 5 | 30 | +| 100 | 0 | 10 | + +Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Ped B-3kmh channel. The graph compares 'Legacy' (blue line with diamonds) and 'With new subframe format' (magenta line with squares). Throughput decreases as users increase, but is significantly higher for the new format. + +Figure 4.7.2.4.2-2: Performance Results – Ped B, 3 km/h channel + +![Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Veh A- 30kmh channel. The graph compares 'Legacy' (blue line with diamonds) and 'With new subframe format' (magenta line with squares). Throughput decreases as users increase, but is significantly higher for the new format.](a4a24ac70004b2e8087923d3f0f6d01d_img.jpg) + +Veh A- 30kmh: Best Effort Throughput for 5 fixed Geometry Users, + +| VoIP Users | Legacy (Kbps) | With new subframe format (Kbps) | +|------------|---------------|---------------------------------| +| 0 | 1280 | 1280 | +| 10 | 1150 | 1220 | +| 25 | 800 | 1000 | +| 50 | 350 | 620 | +| 75 | 40 | 350 | +| 80 | 20 | 250 | +| 90 | 5 | 150 | +| 100 | 0 | 40 | + +Line graph showing Best Effort Throughput (Kbps) vs. VoIP Users for Veh A- 30kmh channel. The graph compares 'Legacy' (blue line with diamonds) and 'With new subframe format' (magenta line with squares). Throughput decreases as users increase, but is significantly higher for the new format. + +Figure 4.7.2.4.2-3: Performance Results – Veh A, 30 km/h channel + +As an example, assume the system of Figure 4.7.2.4.2-2 with a load of 50 VoIP users (or an equivalent of some other multimedia users such as gaming or video-telephony). The introduction of the HS-SCCH-less operation offers the following possible benefits: + +- Increase the number of VoIP users from 50 to 70 users, without impacting the best-effort throughput. +- Maintain 50 VoIP users, and the best-effort throughput will be increased 2.7 times. +- Flexibly to operate between the previous two points of operation. + +### 4.7.3 Benefits of the concept + +The new subframe format propose is backward compatible, does not introduce any significant waveform changes, and provides the following capacity benefits: + +- Significant increase in DL capacity for real-time services. +- Significant increase in available best-effort throughput on the DL for a given load of real-time services. + +Although simulations presented were limited to IMS VoIP with AMR 12.2 kbit/s, it is expected that the benefit extends to other types of real-time services such as gaming and video-over-IP. + +### 4.7.4 Open issues of the concept + +## 4.8 Reduced complexity HS-SCCH-less operation + +### 4.8.1 Description of the concept + +The relative overhead consumed by HS-SCCH becomes significant when it is used to transport small packets, such as those generated in the transport of low-latency low data-rate traffic like VoIP and gaming over HSDPA. + +The full HS-SCCH-less operation, as described in TR 25.903 Section 4.7, reduces this overhead by removing the HS-SCCH completely for two of the HS-DSCH subframe formats (i.e. TB size and MCS). It relies on synchronous IR and blind combining & decoding to eliminate the need for the HS-SCCH. + +This concept, the reduced complexity HS-SCCH-less operation, lessens the HS-SCCH overhead by allowing 4 of the HS-DSCH subframe formats to be transmitted without HS-SCCH with the first HARQ transmission. On the other hand, HARQ retransmissions are accompanied by the HS-SCCH. + +More specifically, when the UE is set up in reduced complexity HS-SCCH-less operation, the traffic is delivered to the UE as follows. + +- The HS-SCCH is not transmitted with first HARQ transmissions. +- The modulation used is restricted to QPSK. +- Only 4 pre-defined TB formats for MAC-hs PDUs are allowed. + - These 4 formats are chosen semi-statically, and maybe independently configured per UE. +- The HS-PDSCH CRC is 24-bits long and is UE specific. + - Its generation follows the same procedure as the CRC currently on the HS-SCCH, and therefore is covered by the 16-bit UE MAC ID. +- At most two contiguous pre-defined HS-PDSCH OVSF codes are assigned per UE. (semi-static, configured per UE, multiple UEs can share the codes) + - Each UE is told via RRC signalling to listen to one particular HS-PDSCH OVSF code for transmissions of the chosen 4 TB formats. The UE therefore monitors that code and the neighboring code for a transmission by blind decoding of the 4 chosen formats. +- The UE does not transmit negative acknowledgements (NACK) in the first transmission when decoding the chosen formats. It transmits ACK or NACKs for the retransmissions. +- HARQ is limited to: + - 2 retransmissions. + - The redundancy version is pre-defined. (static, non configurable) + +- The HARQ retransmissions are accompanied by an HS-SCCH, which is sent with the same channel coding and decoding as the Release 5/6 HS-SCCH. Some of the bits of the HS-SCCH are reinterpreted in order to signal the UE the following information. + - That the HS-SCCH is for the Reduced Complexity HS-SCCH operation + - Whether the retransmission is the first retransmission or the second retransmission + - The channelization code and the transport block size used by the HARQ process + - The HARQ combining information – in the form of an offset from the current TTI indicating where the previous transmission was sent +- The detailed fields in the interpretation of the HS-SCCH are described in Section 4.X.2 +- In addition, just as in Release 5/6 operation, the UE continues to attempt reception of the regular HS-SCCH and corresponding HS-PDSCH codes if any and carries out HARQ the regular way. + +#### 4.8.1.1 HS-SCCH for retransmissions with the reduced complexity HS-SCCH-less operation + +As described in Section 4.8.1, the HS-SCCH is not included with the first HARQ transmission, but is included with the HARQ retransmissions. The coding of the HS-SCCH is unchanged – only the meaning of the bits is modified under this operation. + +![](d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg) + +| | | +|--|--| +| | | +|--|--| + +| | | | | | | +|--|--|--|--|--|--| +| | | | | | | +|--|--|--|--|--|--| + +**Figure 4.8.1.1-1: Structure of the HS-SCCH for legacy transmissions** + +Figure 4.8.1.1-1 depicts the existing HS-SCCH format. Part 2 contains the information necessary for HARQ combining. + +![](56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg) + +| | | +|--|--| +| | | +|--|--| + +| | | | | | | +|--|--|--|--|--|--| +| | | | | | | +|--|--|--|--|--|--| + +**Figure 4.8.1.1-2: Structure of the HS-SCCH for retransmissions using the reduced complexity HS-SCCH-less operation** + +Figure 4.8.1.1-2 depicts the structure of the HS-SCCH used for retransmissions in the reduced complexity HS-SCCH-less operation. The Format ID '111111' corresponds to a TB size that was never used in practice for legacy transmissions because it has a code-rate of $R=0.99$ . The combination of Format ID = '111111' and CCS with $P=1$ or $P=2$ is used to indicate to the UE that this is a reduced complexity HS-SCCH-less retransmission. + +Referring again to Figure 4.8.1.1-2, the interpretation of CCS and Modulation index of Part 1 is the same as for the legacy HS-SCCH, except that the P value signalled through the CCS must be consistent with the HS-SCCH-less TB format that was pre-configured through RRC signalling (see Section 4.X.1). Furthermore, since only QPSK is allowed for HS-SCCH-less operation the Modulation bit will always be set to '0'. + +The content of Part 2 is re-defined as follows: + +- Format ID: 6 bits indicate in combination with CCS ( $P=1$ or $2$ ) that this is an HS-SCCH-less retransmission. +- TB Format: 2 bits indicate which pre-configured TB size is being transmitted. +- reTx ID: 1 bit indicates whether this a 2nd transmission ('0') or a 3rd transmission ('1'). + +- Previous Transmission Pointer: 3 bits indicates the offset from the current TTI, in number of TTIs the time of the previous transmission: {6 TTIs, 7 TTIs, 8 TTIs, ...} +- UE-Specific CRC: unchanged. + +The redundancy version is pre-defined to follow the following sequence for the 3 HARQ transmissions: {s=1 r=0, s=0 r=1, s=1 r=2}. The reTx ID field therefore indicates which redundancy version is being transmitted. + +The NDI bit is not needed since HARQ transmissions are limited to 3 and the reTx ID avoids the ambiguity that existed in legacy transmissions. + +### 4.8.2 Analysis of the concept + +#### 4.8.2.1 Timing and operation + +The timing of the reduced complexity HS-SCCH-less operation is similar to the timing in Release 5/6 HSDPA operation. It is depicted in Figure 4.8.2.1-1. + +![Figure 4.8.2.1-1: Illustration of the reduced complexity HS-SCCH-less operation. The diagram shows a timeline with three transmission intervals. Each interval contains a white rectangular block (HS-SCCH) followed by a red rectangular block (HS-PDSCH). Arrows indicate the timing relationship between the blocks and the timeline. The first transmission starts at the beginning of the timeline. The second and third transmissions are shown as retransmissions, with their start times indicated by arrows pointing to the corresponding white blocks.](1bd6a020aa71784ed74367899560cbb9_img.jpg) + +Figure 4.8.2.1-1: Illustration of the reduced complexity HS-SCCH-less operation. The diagram shows a timeline with three transmission intervals. Each interval contains a white rectangular block (HS-SCCH) followed by a red rectangular block (HS-PDSCH). Arrows indicate the timing relationship between the blocks and the timeline. The first transmission starts at the beginning of the timeline. The second and third transmissions are shown as retransmissions, with their start times indicated by arrows pointing to the corresponding white blocks. + +**Figure 4.8.2.1-1: Illustration of the reduced complexity HS-SCCH-less operation** + +The first and second retransmissions can be asynchronous with respect to the first transmission, and with respect to each other. The accompanying HS-SCCH follows the same timing relationship with the HS-PDSCH transmission as legacy transmissions do; namely the HS-SCCH starts and ends one slot before the HS-PDSCH transmission boundaries. + +If the UE is able to decode the first transmission successfully, it sends an ACK to the Node B over the HS-DPCCH. If it is not able to decode the first transmission, it buffers the data sent on the TTI. The retransmissions do not require any blind combining or decoding operation as the HS-SCCH accompanying the retransmissions carry the information needed. The inclusion of systematic bits in the HS-SCCH of third retransmission provides robustness against HS-SCCH losses. + +#### 4.8.2.2 UE Complexity discussion + +The operation requires the UE to perform blind decoding every TTI of the transport format from 4 possibilities, but requires no blind combining. These 4 transport formats will typically carry small payloads (less than 1,000 bits). + +#### 4.8.2.3 Simulation Results + +Figure 4.8.2.3-1 and Figure 4.8.2.3-2 depict the VoIP capacity for channel models PB3 and VA30. The performance of the legacy operation (Release 6) is compared to that of + +- The original HS-SCCH-less proposal from TR 25.903, Section 4.7-- "Original HS-SCCH-less: 2 TB sizes" +- The original HS-SCCH-less proposal augmented with 4 TB size -- "Original HS-SCCH-less: 4 TB sizes" +- The proposed reduced complexity HS-SCCH-less proposal – "Reduced complexity HS-SCCH-less: 4 TB sizes" + +Figure 4.8.2.3-3 and Figure 4.8.2.3-4 depict the Best Effort throughput of 5 fixed Best Effort users when the number of VoIP users is kept at medium load. It shows that a significant advantage in Best Effort throughput can be obtained because of the overhead reduction and freeing up of HS-SCCH codes for Best Effort traffic. + +These results demonstrate that the reduced complexity HS-SCCH-less proposal captures the gains of the original HS-SCCH-less proposal, while maintaining a significantly lower complexity both at the UE as well as the Node B through increased flexibility. + +The reduced complexity HS-SCCH-less operation achieves a significant reduction in the HS-SCCH overhead because the HS-SCCH overhead is only incurred during retransmissions. In these two scenarios the fraction of transmissions that were retransmissions was 15%. + +![Line graph titled 'PB3 VoIP CAPACITY' showing Outage Probability vs VoIP Users for Ped B 3 km/h channel model.](a8b7b9a2533d0d71d6f7a922c5456ff4_img.jpg) + +This line graph, titled "PB3 VoIP CAPACITY", plots Outage Probability (Y-axis, 0.00 to 0.30) against VoIP Users (X-axis, 40 to 100) for the Ped B 3 km/h channel model. Four data series are shown: Original HS-SCCH-less with 2 TB sizes (yellow diamonds), Original HS-SCCH-less with 4 TB sizes (cyan squares), Reduced complexity HS-SCCH-less with 4 TB sizes (blue plus signs), and Rel 5 HSDPA: Legacy (magenta triangles). The Legacy series shows a sharp increase in outage probability starting around 70 users, reaching 0.30 at approximately 85 users. The Original HS-SCCH-less series show a more gradual increase, with the 2 TB sizes reaching an outage probability of about 0.25 at 90 users, and the 4 TB sizes reaching about 0.06 at 90 users. The Reduced complexity HS-SCCH-less series shows the lowest outage probability, reaching about 0.12 at 90 users. + +| VoIP Users | Original HS-SCCH-less: 2 TB sizes | Original HS-SCCH-less: 4 TB sizes | Reduced complexity HS-SCCH-less: 4 TB sizes | Rel 5 HSDPA: Legacy | +|------------|-----------------------------------|-----------------------------------|---------------------------------------------|---------------------| +| 40 | 0.00 | 0.00 | 0.00 | 0.00 | +| 60 | 0.00 | 0.00 | 0.00 | 0.01 | +| 70 | 0.00 | 0.00 | 0.00 | 0.03 | +| 80 | 0.01 | 0.01 | 0.01 | 0.20 | +| 90 | 0.25 | 0.06 | 0.12 | >0.30 | + +Line graph titled 'PB3 VoIP CAPACITY' showing Outage Probability vs VoIP Users for Ped B 3 km/h channel model. + +Figure 4.8.2.3-1: Comparison of VoIP capacity for the Ped B 3 km/h channel model + +![Line graph titled 'VA30 VoIP CAPACITY' showing Outage Probability vs VoIP Users for Veh A 30 km/h channel model.](b3447f89ba9220b2e6aa861f6ed322cb_img.jpg) + +This line graph, titled "VA30 VoIP CAPACITY", plots Outage Probability (Y-axis, 0.00 to 0.15) against VoIP Users (X-axis, 40 to 110) for the Veh A 30 km/h channel model. The same four data series as the previous graph are shown. The Legacy series (magenta triangles) shows a sharp increase in outage probability starting around 70 users, reaching 0.12 at approximately 85 users. The Original HS-SCCH-less series show a more gradual increase, with the 2 TB sizes reaching an outage probability of about 0.15 at 95 users, and the 4 TB sizes reaching about 0.11 at 100 users. The Reduced complexity HS-SCCH-less series shows the lowest outage probability, reaching about 0.04 at 90 users and about 0.15 at 100 users. + +| VoIP Users | Original HS-SCCH-less: 2 TB sizes | Original HS-SCCH-less: 4 TB sizes | Reduced complexity HS-SCCH-less: 4 TB sizes | Rel 5 HSDPA: Legacy | +|------------|-----------------------------------|-----------------------------------|---------------------------------------------|---------------------| +| 40 | 0.00 | 0.00 | 0.00 | 0.00 | +| 60 | 0.00 | 0.00 | 0.00 | 0.00 | +| 70 | 0.00 | 0.00 | 0.00 | 0.01 | +| 80 | 0.00 | 0.00 | 0.00 | 0.05 | +| 90 | 0.06 | 0.03 | 0.04 | 0.12 | +| 100 | >0.15 | 0.11 | 0.15 | >0.15 | + +Line graph titled 'VA30 VoIP CAPACITY' showing Outage Probability vs VoIP Users for Veh A 30 km/h channel model. + +Figure 4.8.2.3-2: Comparison of VoIP capacity for the Veh A 30 km/h channel model + +![Line graph titled 'PB3 BE Throughput of 5 BE users' showing throughput vs VoIP users for various configurations.](21998d5161d55a19df06b0ea8d3b4e59_img.jpg) + +This line graph shows the Best Effort (BE) throughput for 5 fixed geometry users as a function of VoIP load for the Ped B 3km/h channel model. The Y-axis represents throughput in KBPS, ranging from 0 to 1600. The X-axis represents the number of VoIP users, ranging from 0 to 60. Four data series are plotted: Original HS-SCCH-less with 2 TB sizes (yellow diamonds), Original HS-SCCH-less with 4 TB sizes (cyan squares), Reduced complexity HS-SCCH-less with 4 TB sizes (blue plus signs), and Rel 5 HSDPA Legacy (magenta stars). All series show a linear decrease in throughput as the number of VoIP users increases. The Original HS-SCCH-less configurations maintain the highest throughput, while the Rel 5 HSDPA Legacy configuration shows the lowest throughput. + +| VoIP USERS | Original HS-SCCH-less: 2 TB sizes | Original HS-SCCH-less: 4 TB sizes | Reduced complexity HS-SCCH-less: 4 TB sizes | Rel 5 HSDPA: Legacy | +|------------|-----------------------------------|-----------------------------------|---------------------------------------------|---------------------| +| 0 | 1450 | 1450 | 1450 | 1450 | +| 20 | 1000 | 1000 | 1000 | 850 | +| 30 | 800 | 800 | 750 | 600 | +| 40 | 600 | 600 | 550 | 350 | +| 50 | 450 | 450 | 400 | 150 | +| 60 | 300 | 300 | 250 | 50 | + +Line graph titled 'PB3 BE Throughput of 5 BE users' showing throughput vs VoIP users for various configurations. + +Figure 4.8.2.3-3: Best Effort throughput of 5 fixed geometry users as a function of VoIP load for the Ped B 3km/h channel model + +![Line graph titled 'VA30 BE Throughput of 5 BE users' showing throughput vs VoIP users for various configurations.](96b654cdbd1138c5463c69c8f35cd3ed_img.jpg) + +This line graph shows the Best Effort (BE) throughput for 5 fixed geometry users as a function of VoIP load for the Veh A 30 km/h channel model. The Y-axis represents throughput in KBPS, ranging from 0 to 1400. The X-axis represents the number of VoIP users, ranging from 0 to 60. Four data series are plotted: Original HS-SCCH-less with 2 TB sizes (yellow diamonds), Original HS-SCCH-less with 4 TB sizes (cyan squares), Reduced complexity HS-SCCH-less with 4 TB sizes (blue plus signs), and Rel 5 HSDPA Legacy (magenta stars). All series show a linear decrease in throughput as the number of VoIP users increases. The Original HS-SCCH-less configurations maintain the highest throughput, while the Rel 5 HSDPA Legacy configuration shows the lowest throughput. + +| VoIP USERS | Original HS-SCCH-less: 2 TB sizes | Original HS-SCCH-less: 4 TB sizes | Reduced complexity HS-SCCH-less: 4 TB sizes | Rel 5 HSDPA: Legacy | +|------------|-----------------------------------|-----------------------------------|---------------------------------------------|---------------------| +| 0 | 1200 | 1200 | 1200 | 1200 | +| 20 | 900 | 900 | 900 | 800 | +| 30 | 750 | 750 | 750 | 600 | +| 40 | 650 | 650 | 600 | 450 | +| 50 | 500 | 500 | 450 | 250 | +| 60 | 400 | 400 | 350 | 150 | + +Line graph titled 'VA30 BE Throughput of 5 BE users' showing throughput vs VoIP users for various configurations. + +Figure 4.8.2.3-4: Best Effort throughput of 5 fixed geometry users as a function of VoIP load for the Veh A 30 km/h channel model + +![Bar chart titled 'COMPARISON OF NUMBER OF CDM USERS FOR 60 VOIP AND 5 BE USERS: Ped B 3 kmh'. The chart compares 'Rel 5 HSDPA: Legacy' (blue bars) and 'Reduced complexity HS-SCCH-less: 4 TB sizes' (maroon bars) across 1 to 12 CDM users. The y-axis is 'Fraction' from 0.00 to 0.35. The x-axis is 'Number of CDM Users in a TTI'.](9600eb9b09749d5b8a30898a75407ac8_img.jpg) + +| Number of CDM Users in a TTI | Rel 5 HSDPA: Legacy (Fraction) | Reduced complexity HS-SCCH-less: 4 TB sizes (Fraction) | +|------------------------------|--------------------------------|--------------------------------------------------------| +| 1 | 0.03 | 0.01 | +| 2 | 0.20 | 0.05 | +| 3 | 0.30 | 0.17 | +| 4 | 0.26 | 0.29 | +| 5 | 0.15 | 0.28 | +| 6 | 0.05 | 0.15 | +| 7 | 0.01 | 0.04 | +| 8 | 0.00 | 0.01 | +| 9 | 0.00 | 0.00 | +| 10 | 0.00 | 0.00 | +| 11 | 0.00 | 0.00 | +| 12 | 0.00 | 0.00 | + +Bar chart titled 'COMPARISON OF NUMBER OF CDM USERS FOR 60 VOIP AND 5 BE USERS: Ped B 3 kmh'. The chart compares 'Rel 5 HSDPA: Legacy' (blue bars) and 'Reduced complexity HS-SCCH-less: 4 TB sizes' (maroon bars) across 1 to 12 CDM users. The y-axis is 'Fraction' from 0.00 to 0.35. The x-axis is 'Number of CDM Users in a TTI'. + +**Figure 4.8.2.3-5: Statistics of the number of simultaneously scheduled users (CDM) for legacy and new operation, in the presence of 60 VoIP and 5 Best Effort users for the Ped B 3 km/h channel. (Maximum number of simultaneous HS-SCCH transmissions fixed to 8)** + +##### 4.8.2.3.1 Simulation assumptions + +| Multi-path channel models | VA 30 km/h and PB 3 km/h
Fader type: JTC. | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----|----|-------|-----|---|---------|-----|---|---------|-----|---|--------|-----|---|------|-----|---|------|-----|---| +| Cell layout and link budget | According to TR 25.848 (section A.3):
Site-to-site distance: 2.8 km.
3-cells per site.
Node B Tx power: 44 dBm.
Log-normal shadowing: 8 dB.
Shadow-correlation between co-located cells: 1.0.
Shadow-correlation between non co-located cells: 0.5.
Carrier frequency: 2 GHz.
Bandwidth: 5 MHz.
Number of UE antennas: 1. | | | | | | | | | | | | | | | | | | | | | | +| Node B resources | Power reserved for common channels and DPCH for all users: 7.5 Watt (30%)
3 Watt for common channels + 1 Watt / ~100 users for DPCH
Remaining power for all HS-SCCH and HS-PDSCH: 17.6 Watt
OVSF codes reserved for common channels:
Channel SF Nb
CPICH 256 1
P-CCPCH 256 1
S-CCPCH 256 1
E-AGCH 256 1
AICH 256 1
PICH 256 1
OVSF code usage modelled for dedicated channels:
F-DPCH (SF – 256)
Soft-handover overhead: 1.8
Up to 8 simultaneous HS-SCCH transmissions allowed.
HS-SCCH code collisions are not modelled.
HS-PDSCH OVSF code usage and collisions are explicitly modelled. | Channel | SF | Nb | CPICH | 256 | 1 | P-CCPCH | 256 | 1 | S-CCPCH | 256 | 1 | E-AGCH | 256 | 1 | AICH | 256 | 1 | PICH | 256 | 1 | +| Channel | SF | Nb | | | | | | | | | | | | | | | | | | | | | +| CPICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| P-CCPCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| S-CCPCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| E-AGCH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| AICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| PICH | 256 | 1 | | | | | | | | | | | | | | | | | | | | | +| IMS VoIP packet format and overheads | VoIP packet with payload according to RFC3267
24-bit ROHC overhead.
8-bit RLC overhead.
No forced voice packet bundling. | | | | | | | | | | | | | | | | | | | | | | +| VoIP traffic details | AMR 12.2 kbps.
SID transmitted every 160 ms of silence.
Voice activity model:
50% voice activity.
ON and OFF periods of duration exponentially distributed, of average 3 seconds.
100 ms maximum delay bound with 100 ms SDU discarding at the MAC-hs.
Call length: 30 seconds.
Call Outage: VoIP calls with FER over call length greater than 3% are considered in outage. | | | | | | | | | | | | | | | | | | | | | | +| Best-effort (BE) traffic (if modeled) | Full-buffer traffic if specified.
5 users per cell at fixed geometries {0, 1.5, 2.5, 3, 5dB}.
SDU size: 320 bit | | | | | | | | | | | | | | | | | | | | | | +| Signalling traffic | SRB, RTCP, and SIP not modeled. | | | | | | | | | | | | | | | | | | | | | | +| Parameters of HS-SCCH-less operation | TB sizes:
2 TB sizes: 137 bits, 317 bits
4 TB sizes: 137 bits, 317 bits, 584 bits, and 320 bits
24-bit CRC overhead.
No DRX or DTX.
Each user is assigned two of the available HS-PDSCH OVSF codes at call setup.
OVSF code collision and fragmentation is explicitly modelled. | | | | | | | | | | | | | | | | | | | | | | +| Scheduler | Voice traffic scheduled first, then best-effort (BE) traffic scheduled next (if applicable).
Voice traffic scheduler:
HARQ retransmissions have highest priority
Oldest transmissions are re-transmitted first
Format is selected such as to minimize power usage
New transmissions are scheduled when there are no more HARQ retransmissions to schedule:
Users are prioritized according to the exponential scheduling rule modified as follows:
$P_i = a \cdot \exp \left( \frac{a \cdot D_i[n] - \overline{aD}[n]}{1 + (\overline{aD}[n])^{1/2}} \right) \frac{SNR_i[n]}{\overline{SNR}[n]}$ | | | | | | | | | | | | | | | | | | | | | | + +| | | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

with 1,

with and averaged using a 1-tap IIR low-pass filter of time-constant 3.3 seconds.

Format is selected such as to send the most of that user's voice packets as possible. ("Greedy" resource allocation.)

If there are several options, the format requiring the least power is selected.

BE traffic scheduler:

Proportional Fair priority function.

Format is selected such as to send the most of the user's data packets as possible. ("Greedy" resource allocation.)

If there are several options, the format requiring the least power is selected.

| +| Feedback delays |

CQI delay: 8 slots from time of measure to start of HS-PDSCH transmission.

HARQ delay: minimum 15 slots from end of a transmission to start of a retransmission.

| +| Error modelling |

HS-PDSCH:

Threshold-based decoder.

Energy combining assumed.

HS-SCCH: Threshold-based decoder.

CQI: perfect estimation with quantization errors.

HS-DPCCH: HARQ feedback errors modelled with ACK false alarm probability of 10^{-3} and ACK misdetection probability of 10^{-2}.

No channel estimation modelled.

| + +### 4.8.3 Benefits of the concept + +The performance benefits of the reduced complexity HS-SCCH-less operation are evident from the simulations results. + +- Significant increase in the VoIP capacity compared to the Release 5/6 HSDPA operation obtained due to reduced overhead. +- HS-SCCH channels are freed up to be used for other services. +- At medium VoIP user loads, the first two benefits translate into a large gain in the throughput available to co-existing Best Effort user's traffic. +- Delay sensitive traffic is better supported as more users can be code multiplexed in a single TTI without the costly overhead of the HS-SCCH. Figure 4.8.2.3-5 shows that typically more users are multiplexed per TTI in the new operation. + +#### Backward Compatibility and flexibility benefits: + +- Is backward compatible and integrated with the existing HS-DSCH operation. + - The scheduler may dynamically choose at each TTI whether to schedule a HS-SCCH-less or a legacy transmission. +- Does not impose synchronous operation on retransmissions. +- Does not change the coding and transmission of the HS-SCCH. +- Does not require blind combining by the UE. + +### 4.8.4 Open Issues of the concept + +## 4.A Summary of technical concepts and possible combinations + +### 4.A.1 Overview of the technical concepts + +| section | technical concept | alternatives (if any) | CPC initiation | | | | CPC termination | | | | comments | +|---------|-----------------------|-----------------------|-----------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------|-----------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | trigger | signalling | UE action | Node B action | trigger | signalling | UE action | Node B action | | +| 4.1 | new DPCCH slot format | - | New DPCCH slot format with fewer pilot bits can be configured in same way as existing slot formats. | - | Switch to Rel-99 slot format with more pilot bits during CQI transmission (FFS). | If switching to Rel-99 slot format occurs during CQI transmission:

Serving Node B: Switch to Rel-99 slot format with more pilot bits during CQI transmission (based on the configured CQI reporting occasions).

Non-serving Node B: Modify DPCCH detection appropriately (e.g. using a reduced number of DPCCH bits and/or blind slot | Rel-99 slot format with more pilots can be configured in the usual way. | - | - | - | A new DPCCH slot format with 5 pilot bits and 5 TPC bits would enable a larger reduction in DPCCH overhead than a new slot format with 6 pilot bits and 4 TPC bits.

The exact new slot format is FFS. The 5 pilots / 5 TPC format could be selected if the slot format changes during CQI transmissions; otherwise the 6 pilots / 4 TPC could be selected. | + +| section | technical concept | alternatives (if any) | CPC initiation | | | | CPC termination | | | | comments | +|---------|----------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| | | | trigger | signalling | UE action | Node B action | trigger | signalling | UE action | Node B action | | +| | | | | | | format detection) | | | | | | +| 4.2 | UL DPCCH gating | - | UL inactivity and no HS-DPCCH transmission (nothing else than DPCCH to transmit in the slot) | - | Transmit DPCCH only in predefined slots | - | E-DCH or HS-DPCCH transmission | - | -
(Start transmitting as in rel'6) | -
(Start receiving as in rel'6) | DPCCH DTX detection in the beginning of each TTI in slots where no predefined DPCCH transmission | +| 4.3.1.1 | SIR target reduction | L1 signalling | expiry of a timer which is started after MAC-e scheduler in Node B has noticed via scheduling information that MAC-e buffer in the UE is empty | HS-SCCH signalling to UE (to inform UE about CPC initiation and to trigger corresponding UE behaviour); signalling only in non-VoIP case) | autonomous UL DPCCH power reduction; application of a power offset on HS-DPCCH and/or UL DPCCH in case of DL activity while UL is inactive is ffs | UL DPCCH SIR_target reduction in serving Node B | new data arriving in UE's MAC-e buffer | specific E-DPCCH sequence from UE which is then confirmed by HS-SCCH from Node B (for VoIP signalling only needed after longer inactivity) | autonomous UL DPCCH power increase back to normal; then no further beta_hs boost required; start of E-DPDCH transmission | setting back of UL DPCCH SIR_target to normal in serving Node B | | +| 4.3.1.2 | SIR target reduction | L2 signalling | UE has no data to transmit in uplink for a | sending a MAC-e PDU reserved for | UL DPCCH power reduction, apply power | UL DPCCH SIR_target reduction, power control | New data arriving in UE's MAC-e | sending a MAC-e PDU with SI until all | UL DPCCH power restoration, restore | UL DPCCH SIR_target restoration, restore regular | | + +| section | technical concept | alternatives (if any) | CPC initiation | | | | CPC termination | | | | comments | +|---------|----------------------|-----------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| | | | trigger | signalling | UE action | Node B action | trigger | signalling | UE action | Node B action | | +| | | | certain minimum amount of time | this purpose until all NodeBs in serving and non-serving RLS have acknowledged receipt of the state transition | control loop with DPC_MOD E=1 | reception with DPC_MODE=1 | buffer | NodeBs in serving and non-serving RLS have acknowledged receipt of the state transition | regular power control loop | power control loop | | +| 4.3.1.3 | SIR target reduction | rules | Node B and UE detect a predefined time interval of E-DCH inactivity | - | UL DPCCH power reduction | UL DPCCH SIR_target reduction in serving Node B | E-DCH transmission

HS-DPCCH transmission | Node B detects the E-DCH transmission

- | UL DPCCH power restoration

temporary UL DPCCH power restoration during the HS-DPCCH transmission | UL DPCCH SIR_target restoration in serving Node B

temporary UL DPCCH SIR_target restoration in serving Node B during the HS-DPCCH transmission | note 2 | +| 4.4.1.1 | CQI off | L1 signalling | empty MAC-hs buffer in Node B for some time | request from Node B to UE via HS-SCCH | switching off CQI reporting (but storing reporting cycle) | trigger UE to switch off CQI | new data arriving in Node B's MAC-hs buffer | request from Node B to UE via HS-SCCH | restart CQI reporting with last reporting cycle | trigger UE to switch on CQI (first DL transmission may use former CQI or small CQI) | | +| 4.4.1.2 | CQI off | L2 | UE receives | sending a | switching | NodeB receives | new data | sending a | sending a | NodeB receives | | + +| section | technical concept | alternatives (if any) | CPC initiation | | | | CPC termination | | | | comments | +|---------|-------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------| +| | | | trigger | signalling | UE action | Node B action | trigger | signalling | UE action | Node B action | | +| | | signalling | no data in downlink for a certain minimum amount of time | MAC-e PDU reserved for this purpose until the serving NodeB has acknowledged receipt of the state transition | off CQI reporting (but storing reporting cycle) | MAC-e PDU and acknowledges receipt with ACK and stops CQI evaluation | arriving in Node B's MAC-hs buffer | short MAC-hs PDU in the downlink | MAC-e PDU reserved for this purpose until the serving NodeB has acknowledged receipt of the state transition | MAC-e PDU and acknowledges receipt with ACK and resumes CQI evaluation | | +| 4.4.1.3 | CQI reduction | rules | Node B and UE detect a predefined time interval of HS-DSCH inactivity | - | apply reduced CQI reporting pattern | apply reduced CQI reporting pattern | new data arriving in Node B's MAC-hs buffer | UE receives scheduling information on HS-SCCH | apply normal CQI reporting pattern | apply normal CQI reporting pattern | | +| 4.5 | DRX at UE | - | | | | | | | | | | +| 4.6 | Restricted HS-SCCH | | | | | | | | | | | +| 4.7 | HS-SCCH-less operation | | | | | | | | | | | +| note 1: | void. | | | | | | | | | | | +| note 2: | The introduction of a next-slot E-DCH transmission indication on DPCCH or E-DPCCH is FFS. | | | | | | | | | | | + +### 4.A.2 Overview of possible combinations of technical concepts + +| concepts ->
vs.
combinations | new DPCCH slot format (4.1) | UL DPCCH gating (4.2) | SIR target reduction with L1 signalling (4.3.1.1) | SIR target reduction with L2 signalling (4.3.1.2) | SIR target reduction with rules (4.3.1.3) | CQI off with L1 signalling (4.4.1.1) | CQI off with L2 signalling (4.4.1.2) | CQI reduction with rules (4.4.1.3) | DRX at UE (4.5) | Restricted HS-SCCH (4.6) | HS-SCCH-less operation (4.7) | comments | +|------------------------------------|-----------------------------|-----------------------|---------------------------------------------------|---------------------------------------------------|-------------------------------------------|--------------------------------------|--------------------------------------|------------------------------------|-----------------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1. | | | X | | | X | | | | | | consistent signalling approach | +| 2. | (X)
Note 1 | X | | | | | | (X)
Note 2 | (X)
Note 3 | | | One combination could contain all, any or none of the concepts marked with (X). | +| 3. | (X)
Note 1 | X | | | | (X)
Note 2 | | | (X)
Note 3 | | | One combination could contain all, any or none of the concepts marked with (X). | +| 4. | X
Note 4 | | | | X | | | X | | | | consistent signalling approach | +| 5. | X | | (X1) | (X1) | (X1) | (X2) | (X2) | (X2) | (X3) | | | One combination could contain one of the concepts marked (X1), and may contain one of the concepts marked (X2) and/or the concept marked (X3).

SIR target reduction can be greater with new DPCCH slot format than without. | + +| | | | | | | | | | | | | | +|---------|------------------------------------------------------------------------------------------------------------------------|---------------|------|------|------|------|------|------|------|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6. | X | X | (X1) | (X1) | (X1) | (X2) | (X2) | (X2) | (X3) | | |

One combination could contain one of the concepts marked (X1), and may contain one of the concepts marked (X2) and/or the concept marked (X3).

SIR target reduction can be greater with new DPCCH slot format than without.

New slot format enables DPCCH “on” slots in gated mode to be at lower power.

| +| 7. | (X) | (X)
Note 5 | | X | | | (X) | | (X) | | |

One combination could contain all, any or none of the concepts marked with (X).

| +| 8. | | | | | | | | | | | | | +| Note: | The numbering of the combinations in the table does not include any priority information. | | | | | | | | | | | | +| Note 1: | New DPCCH slot format could be used with DPCCH gating. It could e.g. contain a next slot E-DCH transmission indication | | | | | | | | | | | | +| Note 2: | CQI reporting frequency would enable larger gains for DPCCH gating | | | | | | | | | | | | +| Note 3: | DRX at UE allowed by DL transmission restrictions, but not required: no new/changes requirements for UE | | | | | | | | | | | | +| Note 4: | New DPCCH slot format proposal B is considered for this concept combination. | | | | | | | | | | | | +| Note 5: | Power control adjustments may be different from the ones described in L2 signalling. | | | | | | | | | | | | + +# 5 Technical solution + +This section describes which technical concepts of section 4 are selected to solve the problems in the 3GPP standard described by the work item "Continuous Connectivity for Packet Data Users" defined in [1]. + +## 5.1 Overview of the selected solution + +"Continuous connectivity for packet data users" as building block under the REL-7 feature "RAN improvements" was decided by RAN1 #46 to consist of the following UL & DL improvements: + +- A **new UL DPCCH slot format** configurable by L3 in a semi-static way (based on section 4.1). +- **UL DPCCH gating/discontinuous transmission (DTX)** in 2 cycles (based on section 4.2) connected with a **F-DPCH gating in DL** and an implicit **CQI reporting reduction** in UL (see section 4.4) +- In DL: **Discontinuous reception (DRX)** at the UE (based on section 4.5). +- In DL: A so called **HS-SCCH-less operation** which includes an HS-SCCH less initial transmission and modified HS-SCCH for retransmission(s) (based on section 4.8). + +Note 1: The referenced subsections of section 4 indicate the ideas that were taken into account but they do not necessarily describe the concepts exactly as they were introduced in the final solution as described in section 5. + +Note 2: The building block "Continuous connectivity for packet data users" under the REL-7 feature "RAN improvements" is in the following abbreviated as "CPC solution" (CPC: continuously packet connected or continuous packet connectivity). + +The following summary provides an overview about the CPC solution as introduced in the REL-7 specifications (for more detailed description please refer to the corresponding CRs). + +The CPC solution: + +- is mandatory to be implemented in all FDD UEs of REL-7 and above supporting HSDPA/E-DCH (even though the actual shutting off of the UE receiver remains an UE implementation issue); +- is configurable on a per UE basis by the SRNC i.e. the SRNC can enable the CPC solution or parts of it for each UE individually provided the corresponding Node B supports it; +- can only be applied to FDD UEs in CELL\_DCH state provided that F-DPCH but no DCH in UL and DL is configured for this UE (i.e. SRBs have to be mapped to HS-DSCH) +- is divided into three parts: + - 1) new UL DPCCH slot format + - 2) DTX/DRX at UE (linked with DTX of F-DPCH at Node B) + - 3) HS-SCCH less-operation +- These 3 parts could in theory be configured by the RNC independently from each other as well as in combination. In the specifications one limitation was introduced: 1. can only be applied in connection with 2. +- allows to reduce UL (esp. UL DPCCH, CQI) and DL (esp. HS-SCCH, F-DPCH) control signalling for temporarily inactive packet data users that can get active again in a short time period (<50ms). This helps to increase the number of packet data users in CELL\_DCH as well as to increase the time that these users can stay in CELL\_DCH state (due to increased battery life time as well as lower control signalling overhead on the air interface). + +### 5.1.1 New UL DPCCH slot format + +This part of the CPC solution introduces a new uplink DPCCH slot format which increases the number of TPC bits for power control from 2 to 4 allowing for a trade off between increased power control reliability and reduced UL DPCCH transmit power. As there is no UL DCH and no FBI field is used, the number of pilot bits is then 6 (instead of 8). + +This new UL DPCCH slot format can be configured and reconfigured per UE by the SRNC. + +### 5.1.2 Discontinuous transmission and reception in CELL\_DCH + +This part of the CPC solution can be divided into 2 subparts: + +- Discontinuous uplink DPCCH transmission (in the following abbreviated **UL\_DTX**/DTX at UE) +- Discontinuous downlink reception (in the following abbreviated **DL\_DRX**/DRX at UE). + +UL\_DTX can be applied independently from DL\_DRX but DL\_DRX is only applied if also UL\_DTX is applied. + +As soon as the feature UL\_DTX and/or DL\_DRX is enabled by the SRNC and a time **CPC\_enabling\_delay** (given by higher layers in 10ms radio frames; this period allows synchronisation and power control stabilisation; note: In the specifications this parameter is just called "Enabling\_Delay".) has passed the UE and Node B(s) apply UL\_DTX and/or DL\_DRX based on standardized rules. + +For UL\_DTX and DL\_DRX corresponding parameters for these rules are configured by the SRNC: via RNSAP/NBAP in the Node B and via RRC in the UE. + +**UL\_DTX** allows an autonomous reduction of UL DPCCH transmissions in the UE depending on how often EDCH and HS-DPCCH transmissions in UL occur. This mechanism is under control of the network by standardized rules whose parameters are configured in the RNC. + +Two different cycles of discontinuous UL DPCCH transmission have to be distinguished for a UE applying UL\_DTX: + +- **UE\_DTX\_cycle\_2** (time period in subframes) which is $\geq$ UE\_DTX\_cycle\_1 + - applied if no E-DCH transmissions in UL occurred within the last **Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2** (time period in E-DCH TTIs); + - creates UL DPCCH transmission pattern 2: UL DPCCH transmitted for **UE\_DPCCH\_burst\_2** subframes and no UL DPCCH for the rest of the period **UE\_DTX\_cycle\_2** +- **UE\_DTX\_cycle\_1** (time period in subframes) + - applied if **UE\_DTX\_cycle\_2** is not applied; + - creates UL DPCCH transmission pattern 1: UL DPCCH transmitted for **UE\_DPCCH\_burst\_1** subframes and no UL DPCCH for the rest of the period **UE\_DTX\_cycle\_1**. + +The UL DPCCH transmission patterns defined by the two cycles start at the same time and cycle 2 is configured to be a multiple of cycle 1. A UE specific offset **UE\_DTX\_DRX\_Offset** (in subframes) can be configured to distribute discontinuous transmissions of different users in the time domain. + +With these 2 UL DPCCH patterns the overhead of UL DPCCH can be controlled by a rule (known by UE and Node B): + +UL DPCCH is only transmitted if at least one of the following has to be transmitted: + +- HS-DPCCH (ACK/NACK/CQI) or +- EDCH or +- an UL DPCCH burst of a **UE\_DTX\_cycle\_1** or an UL DPCCH burst **UE\_DTX\_cycle\_2** or +- an UL DPCCH **preamble** or UL DPCCH **postamble** (1 slot). + +The 2 slots UL DPCCH preamble is used directly before an HS-DPCCH or EDCH or UL DPCCH bursts of UL DPCCH transmission pattern if not overlapping with an HS-DPCCH or EDCH transmission. The preamble helps for UL DPCCH power setting as UL DPCCH power is kept on hold during transmission gaps. In addition a one slot + +postamble of UL DPCCH is following after HS-DPCCH or EDCH transmissions or UL DPCCH bursts of UL DPCCH transmission pattern which are followed by a period of no UL DPCCH transmissions. + +When returning from UE\_DTX\_cycle\_2 to UE\_DTX\_cycle\_1 because of new EDCH data to be transmitted after some period of no EDCH transmission (>Inactivity\_Threshold\_for\_UE\_DTX\_cycle\_2 TTIs) it is also possible to use a long preamble (configurable by the parameter UE\_DTX\_long\_preamble\_length to 2 or 4 or 15 slots). + +As UL DTX reduces UL DPCCH transmissions which are also used for determining power control commands on F-DPCH in DL, the Node B is not required to transmit F-DPCH in those gaps of UL DPCCH transmission ("DL F-DPCH gating"). So the UE only receives the TPC commands on F-DPCH corresponding to actually transmitted UL DPCCH slots. + +The UL compressed mode (used for measurements since R99) and the UL DPCCH transmission patterns are applied as follows: + +- As long as UL DTX is not applied or if UL DTX is used but E-DCH data transmission is ongoing compressed mode is applied as in REL-6 and takes priority over UL DPCCH pattern settings. +- In case UL DTX is applied and no ED-DCH data needs to be send 2 cases can be distinguished: + - If a (preamble + UL DPCCH burst + postamble) of the UL DPCCH transmission pattern overlaps partly or fully with a compressed mode gap then the UL DPCCH in this radio frame will be transmitted as in a REL-6 compressed mode frame, i.e. in the whole frame except the compressed mode gap. + - If a (preamble + UL DPCCH burst + postamble) of the UL DPCCH transmission pattern does not overlap with the compressed mode gap in a compressed radio frame then the UL DPCCH transmission related to compressed mode will not be carried out in this radio frame. So in this radio frame the UL DPCCH will follow the UL DPCCH transmission pattern. + +When the discontinuous uplink DPCCH transmission is enabled a count down timer (going from a configurable value CQI\_DTX\_TIMER down to 0 in subframes) controls when **CQI reports** on HS-DPCCH are sent: + +- either CQI reports shall be sent on HS-DPCCH according to REL-6 CQI feedback cycle (this case is called "CQI\_DTX\_Priority=1" and applies before timer expires at 0), +- or CQI reports on HS-DPCCH have to fall into UL DPCCH bursts of the currently active discontinuous uplink DPCCH transmission pattern in order to get transmitted (this case is called "CQI\_DTX\_Priority=0" and applies after the timer has expired at 0). + +The timer is reset to CQI\_DTX\_TIMER every time an HS-SCCH indicating a HS-DSCH transmission (no HS-SCCH order) was received with consistent control information or HS-PDSCH was received correctly. + +Note: When UL DTX is enabled by higher layers for a specific UE then also its CQI feedback pattern is offset by UE\_DTX\_DRX\_Offset (in subframes) in the same way as the UL DPCCH transmission patterns. The CQI feedback cycle remains unchanged compared to the case where no UL DTX is applied. + +In addition to UL DTX there is an option **UL DRX/DRX** at the Node B which allows the Node B to save resources (e.g. for processing) by restricting on MAC level the starting points of new UL data transmissions (after inactivity) of a UE: If no E-DCH transmission has been performed for the time MAC\_Inactivity\_Threshold (in TTIs) the E-TFC selection in the UE will be restricted to cycles given by MAC\_DTX\_Cycle. This restriction of starting points of UL EDCH transmissions is time offset by the same UE\_DTX\_DRX\_Offset (in subframes) as already known from UL DTX in order to allow that the UL EDCH transmissions fall together with UL DPCCH bursts. + +**DL DRX** allows the UE to predict when it has to listen to DL transmissions from the Node B in order to save UE power and increase its battery life time. This mechanism is also based on standardized rules and uses parameters configured by the RNC. Note: Even when configured the UE is not forced to receive discontinuously. + +For Inactivity\_Threshold\_for\_UE\_DRX\_cycle subframes after an HS-SCCH reception or after the first slot of an HS-PDSCH reception the UE has to monitor HS-SCCH of its HS-SCCH set and HS-PDSCH (if HS-SCCH less mode is applied in parallel) continuously. + +In addition the parameter **UE\_DRX\_cycle** (in subframes) determines an "HS-SCCH reception pattern": The UE must listen to one HS-SCCH sub-frame (and the corresponding HS-PDSCH if HS-SCCH received successfully or if HS- + +SCCH less mode is applied in parallel) every UE\_DRX\_cycle sub-frames. The HS-SCCH reception pattern can be offset for different UEs by a UE dependent UE\_DTX\_DRX\_Offset (same parameter as for UL DTX). + Note: The Node B scheduler has to take into account the times at which a UE can receive HS-SCCH/HS-PDSCH. + +In addition the UE has to listen to + +- F-DPCH in slots corresponding to transmitted UL DPCCH slots; +- DL E-HICH corresponding to an UL E-DCH; +- if **UE\_DRX\_Grant\_Monitoring** = TRUE: + E-AGCH from serving cell and E-RGCH transmissions from cells in the serving E-DCH radio link set when they overlap with the start of an HS-SCCH reception pattern; +- DL E-AGCH from serving cell and DL E-RGCH(s) from all the cells in the E-DCH active set + - if overlapping with E-HICH (corresponding to a scheduled E-DCH transmission); + - if sent within Inactivity\_Threshold\_for\_UE\_Grant\_Monitoring subframes after an E-DCH scheduled transmission; + - if at least one MAC-d flow is configured with a scheduled transmission and TEBS > 0 (TEBS: Total E-DCH Buffer Status). + +The Node B has a fast L1 mechanism to force the UE back to continuous UL DPCCH transmissions and continuous DL receptions as in REL-6: **HS-SCCH orders**. + +- Node B can deactivate (or reactivate) UL DTX or DL DRX operation for a specific UE by a L1 command sent on an HS-SCCH of type 2 without an associated HS-PDSCH. +- HS-SCCH orders ('111101') can be distinguished from HS-SCCH less operation ('111110') by its special information type bit combination in HS-SCCH part 2. Note: HS-SCCH orders use already a specific (in REL-5/REL-6 not used) channelization code set bit sequence "1110000" on HS-SCCH part 1. +- These HS-SCCH orders are used in exceptional cases (e.g. danger of losing a connection to a UE). + Normally the UE will stay in the configured UL DTX/DL DRX mode until it is reconfigured and this allows the benefits of continuous operation as in REL-6 as well as discontinuous operation by autonomously applied standardized rules, i.e. without further signalling. + E.g. transmission gaps between packets of a VoIP call as well as speech pauses in between can all be handled as well as a continuous file transfer without a reconfiguration. +- HS-SCCH orders are carried out by the UE a specific time intervall after receiving an HS-SCCH order: + - for UL DTX: at earliest E-DCH TTI boundary coinciding with or following the beginning of the HS-DPCCH subframe containing the HARQ-ACK corresponding to the order, + - for DL DRX: 12 slots after the ending of the HS-SCCH subframe delivering the order. +- If received correctly by the UE an ACK is sent in the corresponding HS-DPCCH ACK field. + +### 5.1.3 HS-SCCH less operation + +This part of the CPC solution is introducing a new HS-SCCH type 2 format (compared to the HS-SCCH type 1 as in REL-6) as well as a new CRC attachment method 2 for HS-PDSCH and it is reducing the DL HS-SCCH overhead for lower data rate services that can be operated with just 4 predefined transport block formats for MAC-hs PDUs (special focus: VoIP users). + +If HS-SCCH less operation is combined with + +- either UL\_DTX +- or UL\_DTX & DL\_DRX + +further restrictions regarding the timing of DL HS-SCCH & HS-PDSCH & F-DPCH as well as UL DPCCH, HS-DPCCH have to be taken into account by the scheduler in the Node B as well as by the UE. + +The main characteristics of HS-SCCH less operation are: + +- 'HS-SCCH less mode' is configured per UE (not per HS-SCCH) by the SRNC by prescribing 1 or 2 HS-PDSCH channelization codes and corresponding up to 4 MAC-hs transport block sizes that have to be used if HS-SCCH type 2 is used. +These settings are semi-static, i.e. they can be reconfigured. +Note: 'HS-SCCH less mode' configured for a UE allows the usage of HS-SCCH less operation, i.e. HS-SCCH type 2/CRC attachment method 2 for this UE. It does not mandate it. This means the UE also continues to attempt reception of the legacy HS-SCCH type 1. +- As in REL-6 the UE has to monitor up to 4 HS-SCCHs but whether HS-SCCHs of type 1 (as in REL-6) or type 2 (as for HS-SCCH less operation) are used is up to the Node B and is autonomously detected by the UE. The only limitation is that if the first transmission of a transport block is using a HS-SCCH type x (x: either 1 or 2) also all retransmissions of this transport block have to use the same HS-SCCH type x. +- Operating with HS-SCCH type 2 is characterized by + - An initial HS-PDSCH transmission has no associated HS-SCCH. The UE: + - knows the channelization code of the HS-PDSCH via RRC from the SRNC (modulation of HS-PDSCH is fixed to QPSK), + - has to blindly decode on the up to 2 HS-PDSCH codes with 4 possible transport formats (configured by the SRNC), + - detects whether HS-PDSCH is dedicated to this UE (UE-Id) from an introduced new 24bit CRC of HS-PDSCH (CRC attachment method 2). + - successful detection is answered by an ACK from the UE (in unsuccessful case no NACK is sent). + - The retransmission (max. 2 are possible) has an associated HS-SCCH of type 2 which informs the UE about: + - HS-PDSCH channelization code (up to max. 2) and modulation (QPSK) + - whether associated HS-PDSCH is dedicated to this UE (UE identity) + - transport block size (1 out of the configured 4) so no blind decoding + - whether this is the first or second retransmission + - a pointer to the previous HS-PDSCH transmission of the same transport block (pointing 6..13 subframes before the start of this HS-PDSCH transmission); +the UE uses a so called 13 TTI long "cyclic soft buffer" to store and combine up to 3 HS-PDSCH transmissions + - The UE answers on HS-DPCCH with ACK or NACK in the same way as for HS-SCCH type 1. + - Apart from the information above same timing of HS-SCCH, HS-PDSCH, HS-DPCCH as in REL-6. + +## 5.2 Impact on RAN1 specifications + +TS 25.201 REL-7: + +- Update of the list of physical layer procedures to add HS-SCCH less operation and to add procedures related to discontinuous transmission and reception. + +TS 25.211 REL-7: + +- Introduction of the new slot format with 4 TPC bits, mapping of 4 TPC bits to power control commands and terminology of subframes. + +TS 25.212 REL-7: + +- Addition of new CRC attachment method 2 for HS-DSCH to be used in connection with HS-SCCH type 2. +- Addition of new HS-SCCH type 2 format to be used for: + - HS-SCCH format type 2 for retransmissions. + +- HS-SCCH orders: L1 commands to activate/deactivate DTX and/or DRX at the UE. + +TS 25.214 REL-7: + +- Synchronisation and power control aspects of discontinuous uplink DPCCH transmission. +- Operation of discontinuous transmission (DTX) and reception (DRX) procedures for CELL\_DCH. +- Details of HS-SCCH less operation and Node B procedure for transmitting HS-DSCH. + +## 5.3 Impact on RAN2 specifications + +TS 25.308 REL-7: Note: All changes apply to FDD only. + +- Summary of + - discontinuous UL transmission (with the option of UL DRX at the Node B) and discontinuous DL reception + - HS-SCCH-less HS-DSCH transmission + - usage of new UL DPCH slot format + +TS 25.319 REL-7: + +- Although E-DCH is impacted by the CPC solution RAN2 decided to only cover CPC changes in TS 25.308. + +TS 25.321 REL-7: Note: All changes apply to FDD only. + +- New parameters for primitives between MAC and RRC +- HARQ procedure for HS-SCCH less operation +- Impact on E-TFCI selection on MAC at UE for UL DRX at Node B +- Conditions under which UE is required to monitor E-AGCH and E-RGCH + +TS 25.331 REL-7: Note: All changes apply to FDD only. + +- DTX\_DRX\_STATUS variable and corresponding actions +- HS\_SCCH\_LESS\_STATUS variable and corresponding actions +- Parameters for UL DTX and DL DRX operation (DTX-DRX information, new variable DTX\_DRX\_PARAMS) +- Parameters for HS-SCCH less operation (HS-SCCH less information, new variable HS\_SCCH\_LESS\_PARAMS) +- CPC parameters (DTX-DRX timing information, DTX-DRX information, HS-SCCH less information) added to the following messages: + - 1) ACTIVE SET UPDATE + - 2) CELL UPDATE CONFIRM + - 3) PHYSICAL CHANNEL RECONFIGURATION + - 4) RADIO BEARER RECONFIGURATION + - 5) RADIO BEARER RELEASE + - 6) RADIO BEARER SETUP + - 7) RRC CONNECTION SETUP + - 8) TRANSPORT CHANNEL RECONFIGURATION +- Extension of CQI feedback cycle including now also 16ms, 32ms, 64ms +- UL DPCH: slot format #4 not applicable if CPC\_DTX\_DRX\_STATUS is FALSE +- DTX-DRX timing information added (Enabling\_Delay, UE\_DTX\_DRX\_Offset) +- constant maxHS-SCCHLessTrBlk = 4 to limit transport block sizes for HS-SCCH less operation + +- ASN.1 text + +## 5.4 Impact on RAN3 specifications + +TS 25.423 REL-7: Note: All changes apply to FDD only. + +- Procedure text added to + - Radio Link Setup + - Radio Link Addition + - Synchronised Radio Link Reconfiguration Preparation + - Unsynchronised Radio Link Reconfiguration +- CPC parameters (see ( ) ) added to the following messages: + - RADIO LINK SETUP REQUEST (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK SETUP RESPONSE (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK SETUP FAILURE (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK RECONFIGURATION PREPARE (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity DTX-DRX Information To Modify, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK RECONFIGURATION READY (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK RECONFIGURATION REQUEST (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity DTX-DRX Information To Modify, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK RECONFIGURATION RESPONSE (Continuous Packet Connectivity HS-SCCH less Information Response) +- Radio Network Layer causes added (Continuous Packet Connectivity DTX-DRX operation not supported, Continuous Packet Connectivity HS-SCCH less operation not supported) +- Continuous Packet Connectivity DTX-DRX Support Indicator and Continuous Packet Connectivity HS-SCCH less Support Indicator added to Cell Capability Container FDD +- Information Elements updated for CPC HS-SCCH less operation in: + - HS-DSCH Serving Cell Change Information + - HS-DSCH Serving Cell Change Information Response +- New Information Elements introduced for CPC: + - Continuous Packet Connectivity DTX-DRX Information + - Continuous Packet Connectivity DTX-DRX Information To Modify + - Continuous Packet Connectivity HS-SCCH less Information + - Continuous Packet Connectivity HS-SCCH less Information Response +- for HS-SCCH less operation: option of HS-PDSCH code change introduced in “Radio Link Parameter Update” procedure in RNSAP so that DRNS can indicate the need for HS-PDSCH code update to SRNC +- ASN.1 text + +TS 25.433 REL-7: Note: All changes apply to FDD only. + +- Procedure text added for + +- Audit +- Resource Status Indication +- Radio Link Setup +- Radio Link Addition +- Synchronised Radio Link Reconfiguration Preparation +- Unsynchronised Radio Link Reconfiguration +- CPC parameters added to the following messages: + - AUDIT RESPONSE (Continuous Packet Connectivity DTX-DRX Capability, Continuous Packet Connectivity HS-SCCH less Capability) + - RESOURCE STATUS INDICATION (Continuous Packet Connectivity DTX-DRX Capability, Continuous Packet Connectivity HS-SCCH less Capability) + - RADIO LINK SETUP REQUEST (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK SETUP RESPONSE (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK SETUP FAILURE (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK RECONFIGURATION PREPARE (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity DTX-DRX Information To Modify, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK RECONFIGURATION READY (Continuous Packet Connectivity HS-SCCH less Information Response) + - RADIO LINK RECONFIGURATION REQUEST (Continuous Packet Connectivity DTX-DRX Information, Continuous Packet Connectivity DTX-DRX Information To Modify, Continuous Packet Connectivity HS-SCCH less Information) + - RADIO LINK RECONFIGURATION RESPONSE (Continuous Packet Connectivity HS-SCCH less Information Response) +- Information Elements updated for CPC: + - HS-DSCH Serving Cell Change Information (Continuous Packet Connectivity HS-SCCH less Information) + - HS-DSCH Serving Cell Change Information Response (Continuous Packet Connectivity HS-SCCH less Information Response) 9.2.2.21B of R3-070349 +- Extension of CQI feedback cycle including now also 16ms, 32ms, 64ms + - New Information Elements introduced for CPC: + - Continuous Packet Connectivity DTX-DRX Capability + - Continuous Packet Connectivity HS-SCCH less Capability + - Continuous Packet Connectivity DTX-DRX Information + - Continuous Packet Connectivity DTX-DRX Information To Modify + - Continuous Packet Connectivity HS-SCCH less Information + - Continuous Packet Connectivity HS-SCCH less Information Response +- for HS-SCCH less operation: option of signalling the need of an HS-PDSCH code change in the “Radio Link Parameter Update” procedure of NBAP from the Node B to the CRNC +- ASN.1 text + +## 5.5 Impact on RAN4 specifications + + + +TS 25.101 REL-7: + +- out of synchronisation handling has to take into account discontinuous UL DPCCH transmission in that sense that not just F-DPCH of 160ms period is considered but 240 slots in which F-DPCH is known to be present during UL DTX operation +- areas to be further checked: impact of discontinuous UL DPCCH transmission on UL power control, need for additional DL power control requirement, transmit off power, transmit on/off time mask, blind demodulation requirement for HS-DSCH in case of HS-SCCH less operation, additional demodulation of new HS-SCCH format type 2, need for receiver performance requirements in case of DL DRX, need for testing of DTX/DRX cycles and timers. + +TS 25.133 REL-7: + +- normalised remaining power margin available for E-TFC selection (section 6.4) has to take into account discontinuous UL DPCCH transmission +- UE transmit power measurement (section 9.1.6) has to take into account discontinuous UL DPCCH transmission. +- UE transmission power headroom measurement (section 9.1.13) has to take into account discontinuous UL DPCCH transmission. +- ffs: extension of 200ms CPICH measurement period and intra-frequency CPICH measurement requirement at the UE in case of DL DRX. + +## 5.6 Change requests related to CPC + +The following CRs introduced CPC in REL-7 RAN specifications: + +| TS | vers. | CR | rev | Tdoc | Title | RAN | +|--------|-------|------|-----|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 25.201 | 7.10 | 0031 | - | R1-071214 | Introduction of CPC related functionality | #35 | +| 25.211 | 7.0.0 | 0230 | 2 | R1-071097 | Support of CPC feature | #35 | +| 25.211 | 7.0.0 | 0231 | - | R1-063151 | Support of CPC feature: addition of subframe numbering | #35 | +| 25.212 | 7.3.0 | 0238 | 5 | R1-071173 | Support of CPC feature | #35 | +| 25.214 | 7.3.0 | 0421 | 13 | R1-071257 | Support of CPC feature | #35 | +| 25.308 | 7.0.0 | 0013 | 3 | RP-060725 | Introduction of CPC | #34 | +| 25.321 | 7.3.0 | 0315 | - | R2-071072 | Introduction of DTX-DRX and HS-SCCH less in MAC | #35 | +| 25.331 | 7.3.0 | 2990 | - | R2-071071 | Introduction of DTX-DRX and HS-SCCH less in RRC | #35 | +| 25.423 | 7.3.0 | 1258 | 2 | R3-070350 | Introduction of Continuous Packet Connectivity in RNSAP | #35 | +| 25.423 | 7.3.0 | 1260 | 1 | R3-070360 | HS-PDSCH code change for CPC mode | #35 | +| 25.433 | 7.3.0 | 1330 | 2 | R3-070349 | Introduction of Continuous Packet Connectivity in NBAP | #35 | +| 25.433 | 7.3.0 | 1334 | 1 | R3-070361 | HS-PDSCH code change for CPC mode | #35 | +| 25.101 | 7.6.0 | 0506 | - | R4-070119 | Introduction of continuous packet connectivity (CPC) to "Out-of-synchronization handling of output power" | #35 | +| 25.133 | 7.6.0 | 0899 | - | R4-070120 | Introduction of continuous packet connectivity (CPC) to ETFC restriction, UE transmitted power and UE transmission power headroom measurement requirements | #35 | + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | Meeting | Doc. | CR | Rev | Subject/Comment | Old | New | +| 2005-10 | RAN1 #42bis | R1-051127 | - | - | Skeleton TR | - | 0.0.1 | +| 2005-10 | RAN1 #42bis | R1-051278 | - | - | Skeleton TR (editorial modifications) | 0.0.1 | 0.0.2 | +| 2005-10 | RAN1 #42bis | R1-051292 | - | - | TR 25.903 including text proposals agreed at RAN1 #42bis (i.e. parts of R1-051205 and R1-051215) and agreements of the email discussion after RAN1 #42bis (related to R1-051128 and R1-051277). | 0.0.2 | 0.0.3 | +| 2005-10 | RAN1 #42bis | R1-051293 | - | - | RAN1 agreed version of the TR 25.903 (after email discussion) | 0.0.3 | 0.1.0 | +| 2005-11 | RAN1 #43 | R1-051602 | - | - | TR 25.903 including text proposals agreed at RAN1 #43: R1-051320, R1-051322, R1-051461, R1-051462, R1-051565, R1-051566, R1-051603 (only "common base for all concepts"), R1-051606, R1-051609, R1-051611, R1-051612 | 0.1.0 | 0.1.1 | +| 2005-11 | RAN1 #43 | R1-051617 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email) | 0.1.1 | 0.2.0 | +| 2006-02 | RAN1 #44 | R1-060748 | - | - | TR 25.903 including text proposals agreed at RAN1 #44: R1-060357*, R1-060408*, R1-060452*, R1-060570*, R1-060592, R1-060595, R1-060598*, R1-060691, R1-060692, R1-060693, R1-060694, R1-060695, R1-060696 (*: agreed with modifications) | 0.2.0 | 0.2.1 | +| 2006-02 | RAN1 #44 | R1-060754 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email) | 0.2.1 | 0.3.0 | +| 2006-04 | RAN1 #44bis | R1-061098 | - | - | TR 25.903 including text proposals agreed at RAN1 #44bis: R1-060943, R1-061010, R1-061021, R1-061022 ('SIR' will be replaced by 'CIR'), R1-061030, R1-061039, R1-061075, R1-061076, R1-061077, R1-061078 | 0.3.0 | 0.3.1 | +| 2006-04 | RAN1 #44bis | R1-061101 | - | - | Adding a dash to the table in section 4.A.1 in row "SIR target reduction, rules" in the column "CPC initiation, signalling" according to a review comment to v0.3.1. | 0.3.1 | 0.3.2 | +| 2006-04 | RAN1 #44bis | R1-061102 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email) | 0.3.2 | 0.4.0 | +| 2006-05 | RAN1 #45 | R1-061638 | - | - | TR 25.903 including text proposals agreed at RAN1 #45: R1-061351, R1-061353, R1-061476, R1-061495, R1-061571, R1-061573, R1-061574, R1-061575, R1-061576 | 0.4.0 | 0.4.1 | +| 2006-05 | RAN1 #45 | R1-061643 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email) | 0.4.1 | 0.5.0 | +| 2006-05 | RAN #32 | RP-060318 | - | - | submitted to RAN #32 for information | 0.5.0 | 1.0.0 | +| 2006-09 | RAN1 #46 | R1-062444 | - | - | TR 25.903 including text proposals agreed at RAN1 #46: R1-062260, R1-062261, R1-062320 (adding "DPCCH gap length = 1sec" to simulation assumptions table), R1-062382, R1-062421, R1-062423 | 1.0.0 | 1.0.1 | +| 2006-09 | RAN1 #46 | R1-062451 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email), compared to v1.0.1 also corrections of some references were included (see cover page of R1-062451) in the email agreement | 1.0.1 | 1.1.0 | +| 2006-11 | RAN1 #47 | R1-063620 | - | - | TR 25.903 including in section 5 text proposal R1-063157 together with corresponding comments of the email discussion after RAN1 #47. | 1.1.0 | 1.1.1 | +| 2006-11 | RAN1 #47 | R1-063621 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email), compared to v1.1.1 only the revision marks were accepted and the yellow marks were removed. (note: This v1.2.0 was also submitted for information to RAN #34 in Dec. 2006 as RP-060794). | 1.1.1 | 1.2.0 | +| 2007-02 | RAN1 #48 | R1-070969 | - | - | Editor's proposal to update TR 25.903 according to decisions about latest REL-7 CRs | 1.2.0 | 1.2.1 | +| 2007-02 | RAN1 #48 | R1-071255 | - | - | RAN1 agreed version of the TR 25.903 (agreed by email). | 1.2.1 | 1.3.0 | +| 2007-03 | RAN_35 | RP-070077 | - | - | TR 25.903 version provided to RAN #35 for approval. | 1.3.0 | 2.0.0 | +| 15/03/07 | RAN_35 | RP-070077 | - | - | Doc in REL-7 under change control further to approval decision | 2.0.0 | 7.0.0 | +| 2008-12 | RAN_42 | - | - | - | Doc in REL-8 under change control | 7.0.0 | 8.0.0 | +| 2009-12 | SP_46 | - | - | - | Doc in REL-9 under change control | 8.0.0 | 9.0.0 | +| 2011-03 | SP_51 | - | - | - | Doc in REL-10 under change control | 9.0.0 | 10.0.0 | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP_65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | SP_70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25951/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-16/25_series/25951/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..057c4c27714332d139a7c8a5a7a9d22a79f74ce7 --- /dev/null +++ b/marked/Rel-16/25_series/25951/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fff4bba46588d2a6bd7650ec6307201e5712870bbdf4c0ae4a2da03230e11a53 +size 91236 diff --git a/marked/Rel-16/25_series/25951/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg b/marked/Rel-16/25_series/25951/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..028c40525181773c3b9dfff597511b1c9cf39338 --- /dev/null +++ b/marked/Rel-16/25_series/25951/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66e37fc44242f2f31524eba66ea646ef1c3fb4decfcac9ec77f55da8b8d440b2 +size 79325 diff --git a/marked/Rel-16/25_series/25951/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-16/25_series/25951/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b1a08edb6ba1e5db7792dfd2e774a2e3b2ce925 --- /dev/null +++ b/marked/Rel-16/25_series/25951/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5e1e135d6976b4fd5f627f7bd0308d8fad4d45ed0747a7f9f2e85d09d6cca2a +size 73400 diff --git a/marked/Rel-16/25_series/25951/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg b/marked/Rel-16/25_series/25951/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51bfd175c192e3273421ccae55a79540a9c616ad --- /dev/null +++ b/marked/Rel-16/25_series/25951/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:521858039ea59b2324726d89d10b193b3c24a5be2afa25cca1f4a6d7fcd68aab +size 12254 diff --git a/marked/Rel-16/25_series/25951/2c4f0f278bff4a04fd08f62808ae2a82_img.jpg b/marked/Rel-16/25_series/25951/2c4f0f278bff4a04fd08f62808ae2a82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ba6ade8bd66a4f68e58181c490ae58d945aad9a --- /dev/null +++ b/marked/Rel-16/25_series/25951/2c4f0f278bff4a04fd08f62808ae2a82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3995b46fc6d9d6b1296448d2ab01f0c7f435fe4a783eadedb1d8cde2f898bdb8 +size 46213 diff --git a/marked/Rel-16/25_series/25951/47b554ac4587106dd53a7ba24cbadd40_img.jpg b/marked/Rel-16/25_series/25951/47b554ac4587106dd53a7ba24cbadd40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..681f2d36f4a97afe989c32b2ca3f541f9cadb3b2 --- /dev/null +++ b/marked/Rel-16/25_series/25951/47b554ac4587106dd53a7ba24cbadd40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0546f96361f1784444b3556bdfaf180c06315a64673a2c7f2a51006b5d707357 +size 49242 diff --git a/marked/Rel-16/25_series/25951/484cfbdc05aee471306eeb11c0ee2543_img.jpg b/marked/Rel-16/25_series/25951/484cfbdc05aee471306eeb11c0ee2543_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..796d6140bf38acde416c5322014bd03a336e1bcd --- /dev/null +++ b/marked/Rel-16/25_series/25951/484cfbdc05aee471306eeb11c0ee2543_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196abdea1c73003cada3d006c6f4a71292f62e7bffe3ce30d763ff1fe9a07c20 +size 54720 diff --git a/marked/Rel-16/25_series/25951/4936add03827ef5a51439c28ec878506_img.jpg b/marked/Rel-16/25_series/25951/4936add03827ef5a51439c28ec878506_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6252d533064b178cee6886d72294bfe40fd6558 --- /dev/null +++ b/marked/Rel-16/25_series/25951/4936add03827ef5a51439c28ec878506_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3250694f80bc5b918a5b6f335b850803ebaa7e91a6e7ce4172f597cb17065152 +size 100371 diff --git a/marked/Rel-16/25_series/25951/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-16/25_series/25951/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8076bd8ef7d4819bfbcb08468b222aff725f2465 --- /dev/null +++ b/marked/Rel-16/25_series/25951/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5669faf56d5a6e99abaccaf38ddd31c7f1155331801b12607169b85c433320c7 +size 111482 diff --git a/marked/Rel-16/25_series/25951/5dc5581cd2aad0e683c73b959f637b31_img.jpg b/marked/Rel-16/25_series/25951/5dc5581cd2aad0e683c73b959f637b31_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35c2a34676f6547f4d42cf0e97ded5a81ca01ad0 --- /dev/null +++ b/marked/Rel-16/25_series/25951/5dc5581cd2aad0e683c73b959f637b31_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4157ceb218cccf70f0885177aa9ee35d29223e37b1e89623bab88d760ac8d2c3 +size 82000 diff --git a/marked/Rel-16/25_series/25951/62a4c9055642dbb00663e633332f04d3_img.jpg b/marked/Rel-16/25_series/25951/62a4c9055642dbb00663e633332f04d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1053467f952cca994bd98096f82270e4e5562c89 --- /dev/null +++ b/marked/Rel-16/25_series/25951/62a4c9055642dbb00663e633332f04d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeb231ac7f74912cb2eedc5aaf20e99ff9bc291dad45ef3bdbcc2e4c9bd8740f +size 72733 diff --git a/marked/Rel-16/25_series/25951/64f0cbd62402f4f1a601aad887f85b95_img.jpg b/marked/Rel-16/25_series/25951/64f0cbd62402f4f1a601aad887f85b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..442b9b2452de9e5804379a7a51c842ad5d793257 --- /dev/null +++ b/marked/Rel-16/25_series/25951/64f0cbd62402f4f1a601aad887f85b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99331d2d2d3b5733b4e3649e2e53909384281509ed04d2b1df28a97d9f23ed2a +size 79840 diff --git a/marked/Rel-16/25_series/25951/6752cee124f693bc4cebc66180f4f91f_img.jpg b/marked/Rel-16/25_series/25951/6752cee124f693bc4cebc66180f4f91f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c8a0777b6d361adabe358159ea6621071cdce90 --- /dev/null +++ b/marked/Rel-16/25_series/25951/6752cee124f693bc4cebc66180f4f91f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b64b624389800bd88ab09c1a3217dce8ab6bac0088a4e3027cecfca438ed7ab +size 43113 diff --git a/marked/Rel-16/25_series/25951/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-16/25_series/25951/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..369d3decad2ab2b4aad26f8646eafbc0e8481430 --- /dev/null +++ b/marked/Rel-16/25_series/25951/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e70669b81c92c520385e60460f64300089b9ecc343f6c84c9902d61195fb91ac +size 83956 diff --git a/marked/Rel-16/25_series/25951/76fd4ccd10dcf423d796c0a1e66a899f_img.jpg b/marked/Rel-16/25_series/25951/76fd4ccd10dcf423d796c0a1e66a899f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..667837980a9518dc84c4ba7227523c16cef4ddcc --- /dev/null +++ b/marked/Rel-16/25_series/25951/76fd4ccd10dcf423d796c0a1e66a899f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ff22b9d97afddf4c903e8c9d7bcaa37c19cc08d4ef37ad43a627ffbb2e368ba +size 46643 diff --git a/marked/Rel-16/25_series/25951/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/25_series/25951/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90951f91c1c62e5b8473f681547744eedce71d5e --- /dev/null +++ b/marked/Rel-16/25_series/25951/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b6dfc274599b414ef11631ef5f2dc6d283466b415d160fdb79120291fd362e8 +size 103932 diff --git a/marked/Rel-16/25_series/25951/97d95cd0cbe6c0c801edb6a4aaa5fc1c_img.jpg b/marked/Rel-16/25_series/25951/97d95cd0cbe6c0c801edb6a4aaa5fc1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d9447aa67711cf0c73440373b8aaede567909e4 --- /dev/null +++ b/marked/Rel-16/25_series/25951/97d95cd0cbe6c0c801edb6a4aaa5fc1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67052fc0474eb61a7cff91ef64330cf0447d56353ddbc7f69ef8b89fe7cf6bee +size 109561 diff --git a/marked/Rel-16/25_series/25951/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/Rel-16/25_series/25951/9c8070d46f1d2480a875239e792f1ef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8274acef07095c972182059cba658ff68d41526f --- /dev/null +++ b/marked/Rel-16/25_series/25951/9c8070d46f1d2480a875239e792f1ef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b937985c9a31cf434ddd09c0ecafff63e733b316f9e075e622c3357102f34e7 +size 48809 diff --git a/marked/Rel-16/25_series/25951/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg b/marked/Rel-16/25_series/25951/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ea9bdb416b30192fdd4412585b43d60bc972568 --- /dev/null +++ b/marked/Rel-16/25_series/25951/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6991ca912ef1355e7d2f13dc015df308e892e0837f0b2cb98d3363c1f2d3fc61 +size 78589 diff --git a/marked/Rel-16/25_series/25951/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-16/25_series/25951/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74f5a211fa5821fb284fb36fa9094e2e2d2f46aa --- /dev/null +++ b/marked/Rel-16/25_series/25951/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9d2ea604ed5031ea33b57d5b80f0323e294eb9eda15da5790975c7fc6d027af +size 73199 diff --git a/marked/Rel-16/25_series/25951/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/25_series/25951/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d058ea3a920f671e1df354024fed660fffbd5d7 --- /dev/null +++ b/marked/Rel-16/25_series/25951/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:072deaa9cb0d6cc46a32e25ee78315c8f9a105e5783580a52f8273e2a451c833 +size 48915 diff --git a/marked/Rel-16/25_series/25951/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-16/25_series/25951/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db49895d83a224f583fc0e0e876f0fdcb048bb41 --- /dev/null +++ b/marked/Rel-16/25_series/25951/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfba31099f911d588a7408eb11418d0da4509cc562a5f69f0f33dc73473bcc0d +size 31300 diff --git a/marked/Rel-16/25_series/25951/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-16/25_series/25951/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..503d981a792985653b78506473dc1ba6cfef205d --- /dev/null +++ b/marked/Rel-16/25_series/25951/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f46b01f6fb938d1e8f89a5d3ef62cce777a1376d338941efee2d4a2e1fa85417 +size 73879 diff --git a/marked/Rel-16/25_series/25951/d0e5691e25988dbacc6a4568af87574b_img.jpg b/marked/Rel-16/25_series/25951/d0e5691e25988dbacc6a4568af87574b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d07a97f63f6b27dafa4776e7c1c13a7d7ceccfb --- /dev/null +++ b/marked/Rel-16/25_series/25951/d0e5691e25988dbacc6a4568af87574b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c8160e6ed7692871de601381970a63821fc6940dd3678440b4762c4ef1a2b69 +size 65777 diff --git a/marked/Rel-16/25_series/25951/d1c99a42332e5ee19f3b840281c26681_img.jpg b/marked/Rel-16/25_series/25951/d1c99a42332e5ee19f3b840281c26681_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..863dfc907cd901d23053a6f3f9aac7643d4e490f --- /dev/null +++ b/marked/Rel-16/25_series/25951/d1c99a42332e5ee19f3b840281c26681_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b094cd3a45f8880a71dbefeb796540d770b65c2d2603a0bb5dade2ee8f87f906 +size 80461 diff --git a/marked/Rel-16/25_series/25951/dfb7b1135e92a91d2c81546f16a50947_img.jpg b/marked/Rel-16/25_series/25951/dfb7b1135e92a91d2c81546f16a50947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bee338065135998b84b31a50151a5878c29f034 --- /dev/null +++ b/marked/Rel-16/25_series/25951/dfb7b1135e92a91d2c81546f16a50947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aea4009c4c65023c15e9cca09f9e0f7e14c19eff5c19f3f25ba6c4247614585 +size 43122 diff --git a/marked/Rel-16/25_series/25951/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-16/25_series/25951/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9242df41eebb10347bd4e0bd1d0699f47dd7d4c --- /dev/null +++ b/marked/Rel-16/25_series/25951/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9a7e9c6ae54960ee93e9c483b89458273c4171022664b5914d3b404f0f3832a +size 47788 diff --git a/marked/Rel-16/25_series/25951/raw.md b/marked/Rel-16/25_series/25951/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc8d0a8f1b7c46d33fdf6ddfe7fd38336bb1b21e --- /dev/null +++ b/marked/Rel-16/25_series/25951/raw.md @@ -0,0 +1,2080 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 4 General..... | 7 | +| 5 System scenarios..... | 7 | +| 5.1 Indoor Environment ..... | 7 | +| 5.1.1 Path Loss Model..... | 7 | +| 5.2 Mixed Indoor – Outdoor Environment..... | 8 | +| 5.2.1 Propagation Model ..... | 8 | +| 5.3 Minimum coupling loss (MCL)..... | 9 | +| 5.3.1 MCL for Local Area scenario..... | 9 | +| 5.4 FDD Base Station Classification for Medium range BS class..... | 10 | +| 5.4.1 Proposal for Medium range (micro) BS class output power ..... | 10 | +| 5.4.1.1 Discussion..... | 10 | +| 5.4.1.2 Proposal ..... | 10 | +| 5.5 FDD Base Station Classification for Local area BS class..... | 10 | +| 5.5.1 Proposal for Local area (pico) BS class output power ..... | 10 | +| 5.5.1.1 Discussion..... | 10 | +| 5.5.1.2 Proposal ..... | 11 | +| 6 Base station classes..... | 11 | +| Base station class criteria ..... | 11 | +| Text proposal for 4.2 Base station classes..... | 11 | +| 7 Changes for the Release 6 in addition to Release 5 ..... | 12 | +| 7.1 Changes in 25.104..... | 12 | +| 7.1.1 Frequency error ..... | 12 | +| 7.1.1.1 New requirement..... | 12 | +| 7.1.1.2 Text proposal for 6.3.1 Minimum requirement ..... | 13 | +| Adjacent Channel Leakage power Ratio (ACLR)..... | 13 | +| 7.1.3 Reference sensitivity level..... | 14 | +| 7.1.4 Spectrum emission mask..... | 14 | +| 7.1.5 Adjacent Channel Selectivity (ACS)..... | 14 | +| 7.1.7 Intermodulation characteristics..... | 17 | +| 7.1.8 Demodulation in static propagation conditions..... | 18 | +| 7.1.9 Demodulation of DCH in multipath fading conditions ..... | 19 | +| 7.1.10 Demodulation of DCH in moving propagation conditions ..... | 19 | +| 7.1.11 Demodulation of DCH in birth/death propagation conditions ..... | 19 | +| 7.1.12 Output power dynamics..... | 19 | +| 7.1.13 Spurious emissions ..... | 19 | +| 7.1.14 Transmit intermodulation ..... | 22 | +| 7.1.15 Transmit modulation ..... | 22 | +| 7.1.16 Receiver dynamic range ..... | 22 | +| 7.1.17 Receiver spurious emissions..... | 23 | +| 7.1.18 Base station maximum output power ..... | 23 | +| 7.2 Changes in 25.133 ..... | 23 | +| 7.2.1 Received total wideband power..... | 23 | +| Changes in 25.141 ..... | 24 | + +| | | | +|-------------------------------|--------------------------------------------------------|-----------| +| 8 | Impacts to other WGs ..... | 25 | +| 9 | Backward Compatibility ..... | 25 | +| Annex A (informative): | Simulation results..... | 26 | +| A.1 | Micro base stations in FDD mode..... | 26 | +| A.1.1 | Receiver sensitivity ..... | 26 | +| A.1.1.1 | Macro to micro multi-operator case ..... | 26 | +| A.1.1.2 | Simulation results ..... | 27 | +| A.1.1.3 | Simulation parameters ..... | 28 | +| A.1.1.4 | Macro-Micro on adjacent frequencies..... | 29 | +| A.1.1.4.1 | Speech 8 kbps ..... | 29 | +| A.1.1.4.2 | Data 144 kbps ..... | 29 | +| A.1.1.5 | Micro-Micro scenario on adjacent frequencies ..... | 30 | +| A.1.2 | Blocking, ACS, and Intermodulation..... | 30 | +| A.1.2.1 | Macro to micro multi-operator case ..... | 30 | +| A.1.2.2 | Simulation results ..... | 32 | +| A.1.2.2.1 | Blocking performance..... | 34 | +| A.1.2.2.2 | Adjacent Channel Selectivity..... | 34 | +| A.1.2.2.3 | Intermodulation Characteristics ..... | 35 | +| A.1.2.3 | Simulation parameters ..... | 36 | +| A.2 | Pico base stations in FDD mode ..... | 36 | +| A.2.1 | Mixed microcell-picocell scenario ..... | 36 | +| A.2.2 | Receiver sensitivity ..... | 37 | +| A.2.2.1 | Simulation parameters ..... | 37 | +| A.2.2.2 | Simulation results ..... | 39 | +| A.2.2.3 | Noise rise for UL in Picocell environment..... | 40 | +| A.2.2.4 | UL noise rise calculation for the picocell BS ..... | 40 | +| A.2.2.5 | Reference sensitivity level..... | 42 | +| A.2.3 | Dynamic range, ACS, Blocking and Intermodulation ..... | 43 | +| A.2.3.1 | Simulation parameters ..... | 43 | +| A.2.3.2 | Dynamic range..... | 43 | +| A.2.3.3 | ACS ..... | 44 | +| A.2.3.4 | Blocking characteristics..... | 44 | +| A.2.3.5 | Intermodulation characteristics..... | 48 | +| A.3 | Maximum output power for Medium range BS class ..... | 49 | +| A.3.1 | Simulation results #1 ..... | 49 | +| A.3.1.1 | Simulation scenario ..... | 49 | +| A.3.1.2 | Simulation results ..... | 49 | +| A.3.1.3 | Proposal ..... | 50 | +| A.3.2 | Simulation results #2..... | 51 | +| A.3.2.1 | Simulation scenario ..... | 51 | +| A.3.2.2 | Simulation results ..... | 51 | +| A.3.2.3 | Proposal ..... | 52 | +| A.4 | Maximum output power for Local area BS class..... | 53 | +| A.4.1 | Simulation results #1 ..... | 53 | +| A.4.1.1 | Simulation scenario ..... | 53 | +| A.4.1.2 | Simulation results ..... | 53 | +| A.4.1.3 | Proposal ..... | 55 | +| A.4.2 | Simulation results #2..... | 55 | +| A.4.2.1 | Simulation scenario ..... | 55 | +| A.4.2.2 | Simulation results ..... | 56 | +| A.4.2.3 | Proposal ..... | 57 | +| Annex B (informative): | Radio Network Planning Considerations..... | 58 | +| B.1 | Adjacent frequency Interference ..... | 58 | +| B.1.1 | General ..... | 58 | +| B.1.2 | Example analysis for localized interference..... | 58 | + +B.1.3    Deployment guidelines to reduce interference.....59 + +B.2    Intra-frequency interference.....60 + +B.2.1    General .....60 + +B.2.2    Example analysis for localized interference.....60 + +B.2.2.1    UL issue.....60 + +B.2.2.2    DL issue.....61 + +B.2.3    Deployment guidelines to reduce interference.....62 + +Annex C (informative):    Change History.....63 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This document is a Technical Report on Release 6 work item “FDD Base Station Classification”. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. +- [1] 3GPP TS 25.104 “BS Radio transmission and Reception (FDD)” +- [2] 3GPP TS 25.133 “Requirements for Support of Radio Resource Management (FDD)” +- [3] 3GPP TS 25.141 “Base Station (BS) conformance testing (FDD)” +- [4] 3GPP TR 25.942 “RF System Scenarios” +- [5] UMTS 30.03 +- [6] 3GPP TR 25.905 “Vocabulary for 3GPP Specifications” + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the definitions, symbols and abbreviations given in TR 21.905 [6] apply. + +# --- 4 General + +Current TSG RAN WG4 specifications have been done according to the requirements for the general purpose base stations (NodeBs) applications. For the UTRA evolution requirement specifications for other types of base stations are needed as well to take into account different use scenarios and radio environments. In this technical report, base station classification is described and requirements for each base station class are derived. + +# --- 5 System scenarios + +This section describes the system scenarios for UTRA operation that are considered when defining base station classes. It also includes typical radio parameters that are used to derive requirements. + +## 5.1 Indoor Environment + +### 5.1.1 Path Loss Model + +The indoor path loss model expressed in dB is in the following form, which is derived from the COST 231 indoor model: + +$$L = 37 + 20 \text{ Log}_{10} I + \sum k_{wi} L_{wi} + 18.3 n^{((n+2)/(n+1)-0.46)}$$ + +where: + +R transmitter-receiver separation given in metres + +| | | +|----------|--------------------------------------| +| $k_{wi}$ | number of penetrated walls of type i | +| $L_{wi}$ | loss of wall type i | +| $n$ | number of penetrated floors | + +Two types of internal walls are considered. Light internal walls with a loss factor of 3.4 dB and regular internal walls with a loss factor of 6.9 dB. + +If internal walls are not modelled individually, the indoor path loss model is represented by the following formula: + +$$L = 37 + 30 \text{ Log}10I + 18.3 n ((n+2)/(n+1)-0.46)$$ + +where: + +| | | +|-----|--------------------------------------------------| +| $R$ | transmitter-receiver separation given in metres; | +| $n$ | number of penetrated floors | + +Slow fading deviation in pico environment is assumed to be 6 dB. + +## 5.2 Mixed Indoor – Outdoor Environment + +### 5.2.1 Propagation Model + +Distance attenuation inside a building is a pico cell model as defined in Chapter 5.1.1. In outdoors UMTS30.03 model is used [5]. + +Attenuation from outdoors to indoors is sketched in Figure 5.1 below. In figure star denotes receiving object and circle transmitting object. Receivers are projected to virtual positions. Attenuation is calculated using micro propagation model between transmitter and each virtual position. Indoor attenuation is calculated between virtual transmitters and the receiver. Finally, lowest pathloss is selected for further calculations. Only one floor is considered. + +The total pathloss between outdoor transmitter and indoor receiver is calculated as + +$$L = L_{\text{micro}} + L_{\text{OW}} + \sum k_{wi} L_{wi} + a * R ,$$ + +where: + +| | | +|--------------------|----------------------------------------------------------------------------------------------------------| +| $L_{\text{micro}}$ | Micro cell pathloss according UMTS30.03 Outdoor to Indoor and Pedestrian Test Environment pathloss model | +| $L_{\text{OW}}$ | outdoor wall penetration loss [dB] | +| $R$ | virtual transmitter-receiver separation given in metres; | +| $k_{wi}$ | number of penetrated walls of type I; | +| $L_{wi}$ | loss of wall type I; | +| $a = 0.8$ | attenuation [dB/m] | + +Slow fading deviation in mixed pico-micro environment shall be 6 dB. + +Propagation from indoors to outdoors would be symmetrical with above models. + +![Figure 5.1: Simulation scenario and propagation model. The diagram shows a grid of yellow rectangular buildings. A central building is divided into rooms and corridors, with a black star labeled 'MS' (Mobile Station) inside. A black circle labeled 'BS' (Base Station) is located on the top edge of the central building. Red arrows indicate signal paths: one from the BS, through the top wall, then horizontally across the top of the central building, and finally down into the MS; another from the BS, through the right wall, then horizontally across the right side of the central building, and finally down into the MS. A callout box labeled 'Virtual positions' has arrows pointing to the MS and the BS.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Figure 5.1: Simulation scenario and propagation model. The diagram shows a grid of yellow rectangular buildings. A central building is divided into rooms and corridors, with a black star labeled 'MS' (Mobile Station) inside. A black circle labeled 'BS' (Base Station) is located on the top edge of the central building. Red arrows indicate signal paths: one from the BS, through the top wall, then horizontally across the top of the central building, and finally down into the MS; another from the BS, through the right wall, then horizontally across the right side of the central building, and finally down into the MS. A callout box labeled 'Virtual positions' has arrows pointing to the MS and the BS. + +Figure 5.1: Simulation scenario and propagation model. + +Parameters related to propagation models are summarised in Table 5.1. + +Table 5.1: Parameters related to mixed indoor – outdoor propagation model + +| Parameter | value | +|-----------------------------------|-------------------| +| Inside wall loss | 6.9 dB | +| Outside wall loss | 10 dB | +| Slow fading deviation in indoors | 6 dB | +| Slow fading deviation in outdoors | 6 dB | +| Building size | 110 x 110 meters | +| Street size | 110 x 15 meters | +| Room size | 22 x 25 meters | +| Number of rooms | 5 rooms in 4 rows | +| Corridor size | 110 x 5 meters | +| Number of corridors | 2 | +| Size of entrance point | 5 meters | +| Number of base stations | 4 .. 6 | +| BS coordinates | tba | + +## 5.3 Minimum coupling loss (MCL) + +Minimum Coupling Loss (MCL) is defined as the minimum distance loss including antenna gain measured between antenna connectors. + +### 5.3.1 MCL for Local Area scenario + +The minimum coupling loss between UEs is independent of the scenario, therefore the same minimum coupling loss is assumed for all environments. + +Local area BSs are usually mounted under the ceiling, on wall or some other exposed position. In [4] chapter 4.1.1.2 a minimal separation of 2 metres between UE and indoor BS is assumed. Free space path loss is defined in [4] as: + +$$\text{Path loss [dB]} = 38.25 + 20 \log_{10}(d \text{ [m]})$$ + +Taking into account 0 dBi antenna gain for Local area BS and UE and a body loss of 1 dB at the terminal, a MCL of 45.27 dB is obtained. The additional 2 dB cable loss at the BS as proposed in TR 25.942 is not considered. + +The assumed MCL values are summarised in table 5.2. + +**Table 5.2: Minimum Coupling Losses** + +| | MCL | +|-----------------------------------------------|------------| +| MS $\leftrightarrow$ MS | 40 dB | +| Local area BS $\leftrightarrow$ MS | 45 dB | +| Local area BS $\leftrightarrow$ Local area BS | 45 dB | + +## 5.4 FDD Base Station Classification for Medium range BS class + +### 5.4.1 Proposal for Medium range (micro) BS class output power + +#### 5.4.1.1 Discussion + +2 contributions were presented during the TSG-RAN WG4 meeting #26 proposing a maximum output power requirement for the Medium range BS class. + +Contributions were proposing a value of 37 dBm and 39 dBm for the maximum output power requirement for the Medium range BS class. It was concluded that results from both simulations were in good agreement with each other. It could be concluded that the capacity loss for the macro layer will be at most 5.8 % for a 37 dBm MR network layer and an upper bound of 6.3 % for a 39 dBm MR network layer was established. + +Taking into account that capacity losses of approximately the same order may also occur for uncoordinated macro-macro networks and furthermore, that the TX powers of the studied MR BSs were in excess of the required TX power for coverage, it was concluded that also a 38 dBm micro layer should lead to acceptable capacity losses. + +As both proposals differed by only 2 dB the value of 38 dBm was suggested and approved as a consensus requirement + +The detailed simulation assumptions and results can be found in the informative Annex A.3. + +#### 5.4.1.2 Proposal + +Based on the above investigation, the proposed maximum output power, which is recommended for the Medium range BS, is +38 dBm as shown in the table below: + +**Table 5.3: Base Station maximum output power** + +| BS Class | Maximum output power | +|-----------------|-----------------------------| +| Medium range BS | $\leq +38$ dBm | + +## 5.5 FDD Base Station Classification for Local area BS class + +### 5.5.1 Proposal for Local area (pico) BS class output power + +#### 5.5.1.1 Discussion + +2 contributions were presented during the TSG-RAN WG4 meeting #26 proposing a maximum output power requirement for the Local area BS class. It was concluded that the output power of Local area BS should be less than +20dBm in order to maintain the capacity deterioration less than 5% when 10% of micro network UEs are in the building. Another conclusion was that even for a 30 dBm LA network layer, interference caused capacity losses in the micro layer could only occur for loads which are unrealistic from the code capacity limit point of view. + +During the discussions the following 2 aspects were identified: + +- 1) propagation losses in the the agreed micro-pico scenario are relatively low compared to those occurring frequently in practice. +- 2) indoor scenarios tend to be more case specific and some variation of the interference impact across real life deployment scenarios should therefore be taken into account. + +Aspect 1) leads to an overestimation of the interference impact, as the LA BSs use more TX power than would have been necessary from the coverage point of view. Hence, it was felt, that also larger than 20 dBm LA BS TX powers will lead to acceptable outage in the micro-layer in practice, due to the more favourable statistics of the pathloss differences. + +Aspect 2) leads to the recommendation to use some extra protection for the micro layer and hence an additional 6 dB safety margin relative to the 30 dBm value is proposed. + +The value 24 dBm was agreed and approved by RAN WG4 as a consensus requirement. + +In order to capture the reasoning behind this requirement, the related simulation results will be added into an informative Annex A.4. + +#### 5.5.1.2 Proposal + +Based on the above investigation, the proposed maximum output power, which is allowed for the Local area BS, is +24 dBm as shown in the table below. + +**Table 5.4: Base Station maximum output power** + +| BS Class | Maximum output power | +|---------------|----------------------| +| Local area BS | +24 dBm | + +# --- 6 Base station classes + +This section describes how the base station classes are defined. + +## Base station class criteria + +Different sets of requirements are derived from calculations based on Minimum Coupling Loss between BS and UE. Each set of requirements corresponds to a base station class is used as criteria for classification. Three classes are defined: Wide Area BS class, Medium Range BS class and Local Area BS class. + +Wide Area BS class assumes relatively high MCL, as is typically found in outdoor macro environments, where the BS antennas are located in masts, roof tops or high above street level. Existing requirements are used, as they are in [1], for the base station intended for general-purpose applications. + +Medium Range BS class assumes medium MCL, as typically found in outdoor micro environments, where the BS antennas are located below roof tops. + +Local Area BS class assumes relatively low MCL, as is typically found indoors (offices, subway stations etc) where antennas are located on the ceilings or walls or possibly built-in in the BS on the wall. Low-CL can also be found outdoors on hot spot areas like market place, high street or railway station. New requirements, as defined in this TR, are set for the Local Area BS class. + +## Text proposal for 4.2 Base station classes + +The requirements in this specification apply to both Wide Area Base Stations and Local Area Base Stations, unless otherwise stated. + +Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum coupling losses equal to 70 dB. The Wide Area Base Station class has the same requirements as the base station for General Purpose application in Release 99, Rel-4 and Rel-5. + +Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equal to 53dB.. + +Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling losses equal to 45dB. + +# 7 Changes for the Release 6 in addition to Release 5 + +## 7.1 Changes in 25.104 + +This section describes the considered changes to requirements on BS minimum RF characteristics, with respect to Release 5 requirements in TS25.104. + +### 7.1.1 Frequency error + +#### 7.1.1.1 New requirement + +In the present system the mobile has to be designed to work with a Doppler shift caused by speeds up to 250 km/h at 2100 MHz. This corresponds to a frequency offset of + +$$\begin{aligned} [\text{Doppler shift, Hz}] &= [\text{UE velocity, m/s}] * [\text{Carrier frequency, Hz}] / [\text{speed of light, m/s}] \\ &= (250 * 1000/3600) * 2.1 * 10^9 / (3 * 10^8) \text{ Hz} \\ &\approx 486 \text{ Hz} \end{aligned}$$ + +At present, the BS requirement is 0.05 ppm, corresponding to 105 Hz at 2100 MHz. + +In this case, the mobile must be able to successfully decode signals with offset of + +$$\begin{aligned} [\text{present UE decode offset, Hz}] &= [\text{frequency error, Hz}] + [\text{max. Doppler shift, Hz}] \\ &= 486 \text{ Hz} + 105 \text{ Hz} \\ &= 591 \text{ Hz} \end{aligned}$$ + +The frequency error requirement for local area BS class is proposed to be relaxed to 0.1ppm. + +$$[\text{frequency error, ppm}] = 0.1 \text{ ppm}$$ + +This corresponds to a maximum UE speed of 196km/h. + +$$\begin{aligned} [\text{max. new Doppler shift}] &= [\text{present UE decode offset}] - [\text{frequency error, Hz}] \\ &= 591 \text{ Hz} - 210 \text{ Hz} \\ &= 381 \text{ Hz} \end{aligned}$$ + +$$\begin{aligned} [\text{UE velocity, km/h}] &= [\text{speed of light, km/h}] * [\text{Doppler shift, Hz}] / [\text{Carrier frequency, Hz}] \\ &= (3 * 10^8 * 381 * 3600) / (2.1 * 10^9 * 1000) \\ &= 196 \text{ km/h} \end{aligned}$$ + +#### 7.1.1.2 Text proposal for 6.3.1 Minimum requirement + +### 6.3.1 *Minimum Requirement* + +The modulated carrier frequency of the Wide area BS shall be accurate to within $\pm 0.05$ ppm observed over a period of one power control group (timeslot). + +The modulated carrier frequency of the Medium range BS shall be accurate to within $\pm 0.1$ ppm observed over a period of one power control group (timeslot). + +The modulated carrier frequency of the Local Area BS shall be accurate to within $\pm 0.1$ ppm observed over a period of one power control group (timeslot). + +**Table 6.0: 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 | + +#### Adjacent Channel Leakage power Ratio (ACLR) + +No changes based on the new Medium Range and Local area BS classes. + +The capacity losses due to ACLR localized around the Local Area BS should be studied further and minuted in this section. + +For Japan, specific considerations of Out-of-band emission requirements for WA, MR and LA-BS were made. The change of the ACLR requirement is limited to Japan and does not apply to other regions. The background is that only Category A spurious emissions requirements apply in Japan. In other regions, the tighter BS spectrum mask and Category B spurious emissions requirements are also applied, which gives a very different situation. In this case the BS spectrum mask overrides the spurious emission limit for lower power BS and there will be no “unbalanced situation” for most power levels. The change is based on the considerable relaxation of the ACLR requirement for low power base stations being agreed in Japan as explained in Tdoc. R4-060414 and it will also become a part of the regulatory requirements of Japan. Based on this, it was agreed in RAN4 to introduce a new note for a certain region as seen below. It is also agreed that the note is only applicable in Japan which is captured in section 4.3 in [1] as a regional requirement. + +In the note introduced for BS ACLR, the minimum requirement of -8.0 dBm/3.84 MHz (for Band I and Band IX) and +2.0 dBm/3.84 MHz (for Band VI) are derived from -13dBm/1MHz and -13dBm/100kHz respectively with test tolerance of 0.8dB taking into account. The values -13dBm/1MHz and -13dBm/100kHz corresponds to Category A spurious emission requirement specified in Table 6.8 in [1]. + +The additional changes on a regional note for ACLR requirement in TS25.104 [1] can be found in documents R4-060684(for Release 6) and R4-060683(for Release 7). + +*Text proposal for 6.6.2.2.1 Minimum requirement* + +The ACLR shall be higher than the value specified in Table 6.7. + +**Table 6.7: BS ACLR** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| 5 MHz | 45 dB | +| 10 MHz | 50 dB | +| NOTE: In certain regions, the adjacent channel power (the RRC filtered mean power centered on an adjacent channel frequency) shall be less than or equal to -8.0 dBm/3.84 MHz (for Band I, Band IX) or +2.0 dBm/3.84 MHz (for Band VI) or as specified by the ACLR limit, whichever is the higher. The ACLR shall be higher than the value specified in this table, if the adjacent channel power is greater than the spurious emissions specified in Table 6.8. | | + +### 7.1.3 Reference sensitivity level + +The chapter 7.2.1 in TS 25.104 REL-6 should be changed as following: + +#### *Reference sensitivity level* + +The reference sensitivity level is the minimum mean power received at the antenna connector at which the Bit Error Ratio (BER) shall not exceed the specific value indicated in section 7.2.1. + +#### *Minimum requirement* + +Using the reference measurement channel specification in Annex A, the reference sensitivity level and performance of the BS shall be as specified in Table 7.1. + +**Table 7.1: BS reference sensitivity levels** + +| BS Class | Reference measurement channel data rate | BS reference sensitivity level (dBm) | BER | +|-----------------|-----------------------------------------|--------------------------------------|----------------------------| +| Wide Area BS | 12.2 kbps | -121 | BER shall not exceed 0.001 | +| Medium Range BS | 12.2 kbps | -111 | BER shall not exceed 0.001 | +| Local area BS | 12.2 kbps | -107 | BER shall not exceed 0.001 | + +### 7.1.4 Spectrum emission mask + +No changes based on the new Medium Range and Local area BS classes. + +### 7.1.5 Adjacent Channel Selectivity (ACS) + +The chapter 7.4.1 TS 25.104 REL-6 should be changed as following: + +#### *Adjacent Channel Selectivity (ACS)* + +Adjacent channel selectivity (ACS) is a measure of the receiver ability to receive a wanted signal at is assigned channel frequency in the presence of a single code W-CDMA modulated adjacent channel signal at a given frequency offset from the center frequency of the assigned channel. ACS is the ratio of the receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s). + +#### *Minimum requirement* + +The BER shall not exceed 0.001 for the parameters specified in Table 7.3. + +**Table 7.3: Adjacent channel selectivity** + +| Parameter | Level | Level | Level | Unit | +|-------------------------------|--------------|-----------------|---------------|------| +| | Wide Area BS | Medium Range BS | Local area BS | | +| Data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -115 | -105 | -101 | dBm | +| Interfering signal mean power | -52 | -42 | -38 | dBm | +| Fuw offset (Modulated) | 5 | 5 | 5 | MHz | + +#### Blocking characteristics + +The chapter 7.5.1 in TS 25.104 REL-6 should be changed as following: + +#### *Minimum requirement* + +The static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters. + +**Table 7.4: Blocking performance requirement for Wide Area BS** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 – 1980 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1900 – 1920 MHz
1980 – 2000 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz -1900 MHz
2000 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| II | 1850 – 1910 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1830 – 1850 MHz
1910 – 1930 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1830 MHz
1930 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| III | 1710 – 1785 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1690 – 1710 MHz
1785 – 1805 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1690 MHz
1805 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | + +**Table 7.4A: Blocking performance requirement for Medium Range BS** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 – 1980 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1900 – 1920 MHz
1980 – 2000 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz -1900 MHz
2000 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| II | 1850 – 1910 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1830 – 1850 MHz
1910 – 1930 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1830 MHz
1930 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| III | 1710 – 1785 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1690 – 1710 MHz
1785 – 1805 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1690 MHz
1805 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | + +**Table 7.4B: Blocking performance requirement for Local Area BS class** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 – 1980 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1900 – 1920 MHz
1980 – 2000 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz -1900 MHz
2000 MHz – 12750 MHz | -15 dBm | -101 dBm | — | CW carrier | +| II | 1850 – 1910 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1830 – 1850 MHz
1910 – 1930 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1830 MHz
1930 MHz – 12750 MHz | -15 dBm | -101 dBm | — | CW carrier | +| III | 1710 – 1785 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1690 – 1710 MHz
1785 – 1805 MHz | -30 dBm | -101 dBm | 10 MHz | WCDMA signal with one code | +| | 1 MHz – 1690 MHz
1805 MHz – 12750 MHz | -15 dBm | -101 dBm | — | CW carrier | + +**Table 7.5: Blocking performance requirement (narrowband) for Wide Area BS** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 – 1910 MHz | - 47 dBm | -115 dBm | 2.7 MHz | GMSK modulated* | +| III | 1710 – 1785 MHz | - 47 dBm | -115 dBm | 2.8 MHz | GMSK modulated* | + +\* GMSK modulation as defined in TS 45.004 [5]. + +**Table 7.5A: Blocking performance requirement (narrowband) for Medium Range BS** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 – 1910 MHz | - 42 dBm | -105 dBm | 2.7 MHz | GMSK modulated* | +| III | 1710 – 1785 MHz | - 42 dBm | -105 dBm | 2.8 MHz | GMSK modulated* | + +\* GMSK modulation as defined in TS 45.004 [5]. + +**Table 7.5B: Blocking performance requirement (narrowband) for Local Area BS class** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 – 1910 MHz | - 37 dBm | -101 dBm | 2.7 MHz | GMSK modulated* | +| III | 1710 – 1785 MHz | - 37 dBm | -101 dBm | 2.8 MHz | GMSK modulated* | + +\* GMSK modulation as defined in TS 45.004 [5]. + +### 7.1.7 Intermodulation characteristics + +The chapter 7.6.1 TS 25.104 REL-6 should be changed as following: + +#### 7.6.1 Minimum requirement + +The static reference performance as specified in clause 7.2.1 should be met in case of a Wide Area BS when the following signals are coupled to BS antenna input: + +- A wanted signal at the assigned channel frequency with a mean power of -115 dBm. +- Two interfering signals with the following parameters. + +**Table 7.6A1: Intermodulation performance requirement for Wide Area BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|-------------------------------|--------|----------------------------| +| I, II, III | - 48 dBm | 10 MHz | CW signal | +| | - 48 dBm | 20 MHz | WCDMA signal with one code | + +**Table 7.6A2: Narrowband intermodulation performance requirement for Wide Area BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|-------------------------------|---------|----------------------------| +| II, III | - 47 dBm | 3.5 MHz | CW signal | +| | - 47 dBm | 5.9 MHz | GMSK modulated* | + +\* GMSK as defined in TS45.004 + +The static reference performance as specified in clause 7.2.1 should be met in case of a Medium Range BS when the following signals are coupled to BS antenna input: + +- A wanted signal at the assigned channel frequency with a mean power of -105 dBm. +- Two interfering signals with the following parameters. + +**Table 7.6B1: Intermodulation performance requirement for Medium Range BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|-------------------------------|--------|----------------------------| +| I, II, III | - 44 dBm | 10 MHz | CW signal | +| | - 44 dBm | 20 MHz | WCDMA signal with one code | + +**Table 7.6B2: Narrowband intermodulation performance requirement for Medium Range BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|-------------------------------|---------|----------------------------| +| II, III | - 43 dBm | 3.5 MHz | CW signal | +| | - 43 dBm | 5.9 MHz | GMSK modulated* | + +\* GMSK as defined in TS45.004 + +The static reference performance as specified in clause 7.2.1 should be met in case of a Local area BS when the following signals are coupled to BS antenna input: + +- A wanted signal at the assigned channel frequency with a mean power of -101 dBm. +- Two interfering signals with the following parameters. + +**Table 7.6C1: Intermodulation performance requirement for Local area BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|-------------------------------|--------|----------------------------| +| I, II, III | - 38 dBm | 10 MHz | CW signal | +| | - 38 dBm | 20 MHz | WCDMA signal with one code | + +**Table 7.6C2: Narrowband intermodulation performance requirement for Local area BS** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|-------------------------------|-------------------------------|---------|----------------------------| +| II, III | - 37 dBm | 3.5 MHz | CW signal | +| | - 37 dBm | 5.9 MHz | GMSK modulated* | +| * GMSK as defined in TS45.004 | | | | + +### 7.1.8 Demodulation in static propagation conditions + +No changes based on the new Medium Range BS class. + +### 7.1.9 Demodulation of DCH in multipath fading conditions + +The chapter 8.3.4 TS 25.104 REL-6 should be changed as following: + +#### *Multipath fading Case 4* + +The performance requirement of DCH in multipath fading Case 4 in case of a Wide Area BS is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $E_b/N_0$ limit. The BLER is calculated for each of the measurement channels supported by the base station. + +#### *Minimum requirement* + +The BLER should not exceed the limit for the $E_b/N_0$ specified in Table 8.5A. + +**Table 8.5A: Performance requirements in multipath Case 4 channel for Wide Area BS** + +| Measurement channel | Received $E_b/N_0$ | Required BLER | +|---------------------|--------------------|---------------| +| 12.2 kbps | n.a. | $< 10^{-1}$ | +| | 10.2 dB | $< 10^{-2}$ | +| | 11.0 dB | $< 10^{-3}$ | +| 64 kbps | 6.4 dB | $< 10^{-1}$ | +| | 6.8 dB | $< 10^{-2}$ | +| | 7.1 dB | $< 10^{-3}$ | +| 144 kbps | 5.8 dB | $< 10^{-1}$ | +| | 6.2 dB | $< 10^{-2}$ | +| | 6.6 dB | $< 10^{-3}$ | +| 384 kbps | 6.2 dB | $< 10^{-1}$ | +| | 6.6 dB | $< 10^{-2}$ | +| | 7.2 dB | $< 10^{-3}$ | + +### 7.1.10 Demodulation of DCH in moving propagation conditions + +No changes based on the new Medium Range BS class. + +### 7.1.11 Demodulation of DCH in birth/death propagation conditions + +No changes based on the new Medium Range BS class. + +### 7.1.12 Output power dynamics + +No changes based on the new Medium Range and Local area BS classes. + +### 7.1.13 Spurious emissions + +No changes for spurious emission Mandatory Requirements and for Operation in the same geographic area based on the new Medium Range and Local area BS classes. However new optional requirements on spurious emission for Co-located base stations are recommended as following: + +#### 6.6.3.3 Co-existence with GSM 900 + +##### 6.6.3.3.1 Operation in the same geographic area + +This requirement may be applied for the protection of GSM 900 MS in geographic areas in which both GSM 900 and UTRA are deployed. + +###### *Minimum Requirement* + +The power of any spurious emission shall not exceed: + +**Table 6.11: BS Spurious emissions limits for BS in geographic coverage area of GSM 900 MS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 921 – 960 MHz | -57 dBm | 100 kHz | | + +###### *Co-located base stations* + +This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. + +###### *Minimum Requirement* + +The power of any spurious emission shall not exceed: + +**Table 6.12: BS Spurious emissions limits for protection of the GSM 900 BTS receiver** + +| BS class | Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|-------------|---------------|-----------------------|------| +| Wide Area BS | 876-915 MHz | -98 dBm | 100 kHz | | +| Medium Range BS | 876-915 MHz | -91 dBm | 100 kHz | | +| Local Area BS | 876-915 MHz | -70 dBm | 100 kHz | | + +These values assume a 30 dB coupling loss between transmitter and receiver. If BSs of different classes are co-sited, the coupling loss must be increased by the difference between the corresponding values from the table above. + +#### 6.6.3.4 Co-existence with DCS 1800 + +##### 6.6.3.4.1 Operation in the same geographic area + +This requirement may be applied for the protection of DCS 1800 MS in geographic areas in which both DCS 1800 and UTRA are deployed. + +###### *Minimum Requirement* + +The power of any spurious emission shall not exceed: + +**Table 6.13: BS Spurious emissions limits for BS in geographic coverage area of DCS 1800 MS receiver** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|-----------------|---------------|-----------------------|------| +| I | 1805 – 1880 MHz | -47 dBm | 100 kHz | | + +###### *Co-located base stations* + +This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. + +###### *Minimum Requirement* + +The power of any spurious emission shall not exceed: + +**Table 6.14: BS Spurious emissions limits for BS co-located with DCS 1800 BTS** + +| BS class | Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|----------------|-----------------|---------------|-----------------------|------| +| Wide Area BS | I | 1710 – 1785 MHz | -98 dBm | 100 kHz | | +| Medium Range BS | I | 1710 – 1785 MHz | -96 dBm | 100 kHz | | +| Local Area BS | I | 1710 – 1785 MHz | -80 dBm | 100 kHz | | +| Wide Area BS | III | 1710 – 1785 MHz | -98 dBm | 100 kHz | | +| Medium Range BS | III | 1710 – 1785 MHz | -96 dBm | 100 kHz | | +| Local Area BS | III | 1710 – 1785 MHz | -80 dBm | 100 kHz | | + +These values assume a 30 dB coupling loss between transmitter and receiver. If BSs of different classes are co-sited, the coupling loss must be increased by the difference between the corresponding values from the table above. + +#### 6.6.3.7 Co-existence with UTRA-TDD + +##### 6.6.3.7.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. + +###### Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 6.17: BS Spurious emissions limits for BS in geographic coverage area of UTRA-TDD** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1900 – 1920 MHz | -52 dBm | 1 MHz | | +| 2010 – 2025 MHz | -52 dBm | 1 MHz | | + +###### Co-located base stations + +This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. + +###### Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 6.18: BS Spurious emissions limits for BS co-located with UTRA-TDD** + +| BS class | Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|-----------------|---------------|-----------------------|------| +| Wide Area BS | 1900 – 1920 MHz | -86 dBm | 1 MHz | | +| Local Area BS | 1900 – 1920 MHz | -55 dBm | 1 MHz | | +| Wide Area BS | 2010 – 2025 MHz | -86 dBm | 1 MHz | | +| Local Area BS | 2010 – 2025 MHz | -55 dBm | 1 MHz | | + +These values assume a 30 dB coupling loss between transmitter and receiver. If BSs of different classes are co-sited, the coupling loss must be increased by the difference between the corresponding values from the table above. + +#### 6.6.3.10 Co-existence with PCS1900 + +##### 6.6.3.10.1 Co-located base stations + +This requirement may be applied for the protection of PCS1900 BS receivers when UTRA BS operating in frequency band II and PCS1900 BS are co-located. + +###### Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 6.23: BS Spurious emissions limits for BS co-located with PCS1900 BS** + +| BS class | Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|----------------|-----------------|---------------|-----------------------|------| +| Wide Area BS | II | 1850 – 1910 MHz | -98 dBm | 100 kHz | | +| Medium Range BS | II | 1850 – 1910 MHz | -96 dBm | 100 kHz | | +| Local Area BS | II | 1850 – 1910 MHz | -80 dBm | 100 kHz | | + +These values assume a 30 dB coupling loss between transmitter and receiver. If BSs of different classes are co-sited, the coupling loss must be increased by the difference between the corresponding values from the table above. + +#### 6.6.3.11 Co-existence with GSM850 + +##### 6.6.3.11.1 Co-located base stations + +This requirement may be applied for the protection of GSM850 BS receivers when UTRA BS operating in frequency band II and GSM850 BS are co-located. + +##### *Minimum Requirement* + +The power of any spurious emission shall not exceed: + +**Table 6.24: BS Spurious emissions limits for BS co-located with GSM850 BS** + +| BS class | Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|----------------|---------------|---------------|-----------------------|------| +| Wide Area BS | II | 824 – 849 MHz | -98 dBm | 100 kHz | | +| Medium Range BS | II | 824 – 849 MHz | -91 dBm | 100 kHz | | +| Local Area BS | II | 824 – 849 MHz | -70 dBm | 100 kHz | | + +These values assume a 30 dB coupling loss between transmitter and receiver. If BSs of different classes are co-sited, the coupling loss must be increased by the difference between the corresponding values from the table above. + +### 7.1.14 Transmit intermodulation + +No changes based on the new Medium Range and Local area BS classes. + +### 7.1.15 Transmit modulation + +No changes based on the new Medium Range and Local area BS classes. + +### 7.1.16 Receiver dynamic range + +The chapter 7.3.1 in TS 25.104 REL-6 should be changed as following: + +#### *Dynamic range* + +Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel. + +#### *Minimum requirement* + +The BER shall not exceed 0.001 for the parameters specified in Table 7.2. + +**Table 7.2: Dynamic range** + +| Parameter | Level Wide Area BS | Level Medium Range BS | Level Local area BS | Unit | +|-----------------------------------------|--------------------|-----------------------|---------------------|--------------| +| Reference measurement channel data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -91 | -81 | -77 | dBm | +| Interfering AWGN signal | -73 | -63 | -59 | dBm/3.84 MHz | + +### 7.1.17 Receiver spurious emissions + +No changes based on the new Medium range and Local area BS classes. + +### 7.1.18 Base station maximum output power + +The chapter 6.2.1 in TS 25.104 REL-6 should be changed as following: + +#### *Base station maximum output power* + +Maximum output power, Pmax, of the base station is the mean power level per carrier measured at the antenna connector in specified reference condition. + +#### *Minimum requirement* + +The rated output power, PRAT, of the BS shall be as specified in Table 6.0A. + +**Table 6.0A: Base Station rated output power** + +| BS class | PRAT | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Wide Area BS | (note) | +| Medium Range BS | $\leq +38\text{dBm}$ | +| Local Area BS | $\leq +24\text{dBm}$ | +| NOTE: There is no upper limit required for the rated output power of the Wide Area Base Station like for the base station for General Purpose application in Release 99, 4, and 5. | | + +In normal conditions, the Base station maximum output power shall remain within +2 dB and -2dB of the manufacturer's rated output power. + +In extreme conditions, the Base station maximum output power shall remain within +2.5 dB and -2.5 dB of the manufacturer's rated output power. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +## 7.2 Changes in 25.133 + +This section describes the considered changes to requirements on UTRAN measurements, with respect to Release 5 requirements in TS25.133. + +### 7.2.1 Received total wideband power + +### 9.2.1 Received total wideband power + +The measurement period shall be 100 ms. + +#### *Absolute accuracy requirement* + +**Table 9.35** + +| Parameter | Unit | Accuracy [dB] | Conditions | BS Class | +|----------------------------------|--------------|---------------|-------------------|-----------------| +| | | | Io [dBm/3.84 MHz] | | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 4 | -103... -74 | Wide Area BS | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 4 | -93... -64 | Medium Range BS | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 4 | -89... -60 | Local area BS | + +#### Relative accuracy requirement + +The relative accuracy is defined as the Received total wideband power measured at one frequency compared to the Received total wideband power measured from the same frequency at a different time. + +**Table 9.36** + +| Parameter | Unit | Accuracy [dB] | Conditions | BS Class | +|----------------------------------|--------------|---------------|--------------------------------------------------------|-----------------| +| | | | Io [dBm/3.84 MHz] | | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 0.5 | -103... -74
AND for changes $\leq \pm 5.0\text{dB}$ | Wide Area BS | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 0.5 | -93... -64
AND for changes $\leq \pm 5.0\text{dB}$ | Medium Range BS | +| Received Total Wideband Power Io | dBm/3.84 MHz | ± 0.5 | -89... -60
AND for changes $\leq \pm 5.0\text{dB}$ | Local area BS | + +#### Received total wideband power measurement report mapping + +The reporting range for *Received total wideband power (RTWP)* is from -112 ... -50 dBm. + +In table 9.37 the mapping of measured quantity is defined. The range in the signalling may be larger than the guaranteed accuracy range. + +**Table 9.37** + +| Reported value | Measured quantity value | Unit | +|----------------|------------------------------------|------| +| RTWP_LEV_000 | RTWP < -112.0 | dBm | +| RTWP_LEV_001 | $-112.0 \leq \text{RTWP} < -111.9$ | dBm | +| RTWP_LEV_002 | $-111.9 \leq \text{RTWP} < -111.8$ | dBm | +| ... | ... | ... | +| RTWP_LEV_619 | $-50.2 \leq \text{RTWP} < -50.1$ | dBm | +| RTWP_LEV_620 | $-50.1 \leq \text{RTWP} < -50.0$ | dBm | +| RTWP_LEV_621 | $-50.0 \leq \text{RTWP}$ | dBm | + +#### Changes in 25.141 + +This section describes the considered changes to base station conformance testing, with respect to Release 5 requirements in TS25.141. + +Approved changes for 25.141 can be found from documents R4-021695 and R4-030350. Changes are not repeated here. + +Additional changes on ALCR were made as a regional requirement in Japan, which capturing the changes in the core requirement in section 7.1.2 in this TR. The change is to introduce a new note for a certain region as seen below. It is also agreed that the note is only applicable in Japan which is captured in section 4.7 in [3] as a regional requirement. + +In the note introduced for BS ACLR, the test requirement of $-7.2\text{ dBm}/3.84\text{ MHz}$ (for Band I and Band IX) and $+2.8\text{ dBm}/3.84\text{ MHz}$ (for Band VI) are derived from $-13\text{ dBm}/1\text{ MHz}$ and $-13\text{ dBm}/100\text{ kHz}$ respectively. The values $-13\text{ dBm}/1\text{ MHz}$ and $-13\text{ dBm}/100\text{ kHz}$ corresponds to Category A spurious emission requirement specified in Table 6.8 in [1]. + +The additional changes on a regional note for ACLR requirement in TS25.141 [4] can be found in documents R4-060685(for Release 6) and R4-060686(for Release 7). + +*Text proposal for 6.6.2.2.5 Test Requirement* + +The measurement result in step 1 of 6.5.2.2.4.2 shall not be less than the ACLR limit specified in tables 6.23 + +Table 6.23: BS ACLR + +| BS channel offset below the first or above the last carrier frequency used | ACLR limit | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 5 MHz | 44.2 dB | +| 10 MHz | 49.2 dB | +| Note: In certain regions, the adjacent channel power (the RRC filtered mean power centered on an adjacent channel frequency) shall be less than or equal to -7.2 dBm/3.84 MHz (for Band I, Band IX) or +2.8dBm/3.84MHz (for Band VI) or as specified by the ACLR limit, whichever is the higher. | | + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 4.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex F. + +# --- 8 Impacts to other WGs + +void + +# --- 9 Backward Compatibility + +void + +# Annex A (informative): Simulation results + +## A.1 Micro base stations in FDD mode + +### A.1.1 Receiver sensitivity + +#### A.1.1.1 Macro to micro multi-operator case + +A multi-operator Macro-Micro scenario (as in TR 25.942 chapter 5.1.3.2) was investigated whereas the UL capacity of the system is calculated as a function of the Micro BS noise floor. The outcome is a relative UL capacity (either for the Micro or Macro system) as a function of the Micro noise floor. + +The Macro-Micro cell layout consists of a finite micro cell layer (Manhattan cell grid environment) under a much larger finite macro network. The area close to the Micro network and the simulation input parameters are specified in TR 25.942 chapter 5.1.3.2. The used Macro-Micro cell deployment is as following: + +![Figure A.1: Macro-Micro network deployment (units are in meter). The plot shows a 2D coordinate system with x-axis from -1200 to 600 and y-axis from -1000 to 800. A dense grid of green squares (Micro BS) is centered around the origin, roughly between x = -800 to 200 and y = -600 to 400. Blue crosses (Macro BS) are scattered throughout the area, with a higher concentration within the green grid area. The grid is composed of small squares, and the Macro BS are positioned at various points, some within the grid and some outside.](64f0cbd62402f4f1a601aad887f85b95_img.jpg) + +Figure A.1: Macro-Micro network deployment (units are in meter). The plot shows a 2D coordinate system with x-axis from -1200 to 600 and y-axis from -1000 to 800. A dense grid of green squares (Micro BS) is centered around the origin, roughly between x = -800 to 200 and y = -600 to 400. Blue crosses (Macro BS) are scattered throughout the area, with a higher concentration within the green grid area. The grid is composed of small squares, and the Macro BS are positioned at various points, some within the grid and some outside. + +**Figure A.1: Macro-Micro network deployment (units are in meter).** + +The number of BS in this scenario is 72 Micro BS and 36 Macro BS. The chosen number of Macro BS ensures that the Micro cell grid experience infinite Macro cell grid (not all macro BS:s are shown in Figure A.1 which is a zoomed picture showing the area close to the Micro cell grid). + +A number of Monte Carlo simulations were done to determine the impact of different Micro reference sensitivity levels versus UL capacity loss in both Micro and Macro cells where Micro and Macro cells are deployed at adjacent frequencies. The results are applicable both for a multi-operator or a single operator case. More details about simulations parameters and assumptions can be found in chapter A.1.1.3. + +#### A.1.1.2 Simulation results + +The Macro and the Micro networks are loaded to 75 % of pole capacity in a single layer system. This corresponds to 6 dB average noise rise in the Macro network. Simulations are done for a Micro noise floor ranges of –103 to –80 dBm. + +The relative UL capacity of the Macro and Micro system as function of the Micro BS noise floor is shown in Figure A.2 (see also chapter A.1.1.4): + +![Figure A.2: Relative UL capacity versus Micro BS noise floor. The graph shows two curves: a blue dashed line for the Micro network and a red solid line for the Macro network. The x-axis is Micro BS noise floor (dBm) from -103 to -81. The y-axis is Relative Capacity (%) from 85 to 101. The Micro network curve is flat at 100%. The Macro network curve starts at 99% at -103 dBm, remains relatively flat until about -95 dBm, then decreases to 97% at -87 dBm, 94% at -85 dBm, 90% at -83 dBm, and finally drops to 85% at -81 dBm.](62a4c9055642dbb00663e633332f04d3_img.jpg) + +| Micro BS noise floor (dBm) | Micro network Relative Capacity (%) | Macro network Relative Capacity (%) | +|----------------------------|-------------------------------------|-------------------------------------| +| -103 | 100 | 99 | +| -101 | 100 | 99 | +| -99 | 100 | 99 | +| -97 | 100 | 99 | +| -95 | 100 | 98.5 | +| -93 | 100 | 98 | +| -91 | 100 | 97.5 | +| -89 | 100 | 97 | +| -87 | 100 | 97 | +| -85 | 100 | 94 | +| -83 | 100 | 90 | +| -81 | 100 | 85 | + +Figure A.2: Relative UL capacity versus Micro BS noise floor. The graph shows two curves: a blue dashed line for the Micro network and a red solid line for the Macro network. The x-axis is Micro BS noise floor (dBm) from -103 to -81. The y-axis is Relative Capacity (%) from 85 to 101. The Micro network curve is flat at 100%. The Macro network curve starts at 99% at -103 dBm, remains relatively flat until about -95 dBm, then decreases to 97% at -87 dBm, 94% at -85 dBm, 90% at -83 dBm, and finally drops to 85% at -81 dBm. + +**Figure A.2: Relative UL capacity versus Micro BS noise floor.** + +The blue curve in Figure A.2 shows the relative Micro UL capacity under influence of interference from the Macro network. The UL Micro capacity is not affected by the Macro layer. The red curve in Figure A.2 shows the relative Macro UL capacity when the Micro BS noise floor is increased. The Macro UL capacity is affected when the Micro noise floor is increased. + +The Micro capacity in presence of another adjacent Micro system was also investigated and no significant impact (smaller than 0.5%) was seen. The scenario is described in chapter A.1.1.5. + +In a multi-operator environment, it is important to minimise the impact from a Micro cell grid on the Macro cells. Utilizing the already existing Macro-Macro multi-operator results stated in TR 25.942 chapter 5.1.3.1 allowing maximum of 3% Macro UL capacity loss, it would be possible to desensitise the Micro BS relative to Macro BS reference sensitivity by 16 dB resulting in a BS noise floor of –87dBm. + +On the other hand these results are based on an antenna gain of 11dBi. Assuming a lower antenna gain of e.g. 5dBi the impact to the Macro network will increase significant due to the shape of the curve. It is proposed to maintain a low impact from Micro to Macro layer also for smaller antenna gains and recommend only 10 dB Micro desensitisation (stay in the flat part of the curve) that results in 1.5% Macro UL capacity loss for 11dBi antennas and 3% for 5dBi antennas. + +The resulting 1.5% Macro capacity loss is valid for this scenario and is believed to be smaller in a real network since the scenario in TR 25.942 chapter 5.1.3.2 is a worst-case one. + +#### A.1.1.3 Simulation parameters + +**Table A.1: Simulation parameters** + +| Simulation parameter
Uplink | | +|------------------------------------------------|------------------------------------------------| +| MCL macro / micro | 70 / 53 dB | +| Antenna gain (including losses) | | +| Base station | 11 dBi | +| Mobile | 0 dBi | +| Log-normal shadow fading
standard deviation | 10 dB | +| Noise floor RBS receiver | -103 / -103 .. -73 dBm | +| Macro / micro | | +| Maximum TX power speech | 21 dBm | +| Maximum TX power data | 21 dBm | +| Minimum TX power speech | -50 dBm | +| ACIR | 33 dB | +| Power control | Perfect PC | +| Power control error | 0.01 dB | +| Outage condition | C/I target not reached due to lack of TX power | +| Admission control | Not included | +| Macro User distribution in macro network | Random and uniform over the network | +| Micro User distribution in micro network | Random and uniform over the streets | +| Macro User distribution in micro network | Random and uniform over the streets | +| Bit rate speech | 8 kbps | +| Activity factor speech | 100 % | +| Eb/No target speech | 6.1 / 3.3 dB | +| macro / micro | | +| Bit rate data | 144 kbps | +| Activity factor data | 100 % | +| Eb/No target data | 3.1 / 2.4 dB | +| macro / micro | | +| Micro deployment | Manhattan scenario | +| Block size | 75 m | +| Road width | 15 m | +| Intersite distance between line-of-sight | 180 | +| Number of micro cells | 72 | +| Number of macro cells | 3 affected macros
36 in total | +| Macro Site-to-Site distance | 1 km | + +#### A.1.1.4 Macro-Micro on adjacent frequencies + +##### A.1.1.4.1 Speech 8 kbps + +![Line graph titled 'Relative capacity versus micro BS noisefloor (Speech)' showing the relative capacity (%) of micro and macro networks as a function of micro BS noisefloor (dBm) for speech at 8 kbps. The micro network (dashed blue line) remains constant at 100% capacity. The macro network (solid red line) starts at 100% capacity and begins to drop around -90 dBm, reaching approximately 5% at -73 dBm.](484cfbdc05aee471306eeb11c0ee2543_img.jpg) + +| Micro BS noisefloor (dBm) | Micro network (%) | Macro network (%) | +|---------------------------|-------------------|-------------------| +| -105 | 100 | 100 | +| -100 | 100 | 100 | +| -95 | 100 | 100 | +| -90 | 100 | 100 | +| -85 | 100 | 95 | +| -80 | 100 | 85 | +| -75 | 100 | 30 | +| -73 | 100 | 5 | + +Line graph titled 'Relative capacity versus micro BS noisefloor (Speech)' showing the relative capacity (%) of micro and macro networks as a function of micro BS noisefloor (dBm) for speech at 8 kbps. The micro network (dashed blue line) remains constant at 100% capacity. The macro network (solid red line) starts at 100% capacity and begins to drop around -90 dBm, reaching approximately 5% at -73 dBm. + +Figure A.3: Relative capacity of macro and micro system versus micro BS noise floor (speech 8 kbps). + +##### A.1.1.4.2 Data 144 kbps + +![Line graph titled 'Relative capacity versus micro BS noisefloor (Data144)' showing the relative capacity (%) of micro and macro networks as a function of micro BS noisefloor (dBm) for data at 144 kbps. The micro network (dashed blue line) remains constant at 100% capacity. The macro network (solid red line) starts at 100% capacity and begins to drop around -85 dBm, reaching approximately 72% at -73 dBm.](9c8070d46f1d2480a875239e792f1ef6_img.jpg) + +| Micro BS noisefloor (dBm) | Micro network (%) | Macro network (%) | +|---------------------------|-------------------|-------------------| +| -105 | 100 | 100 | +| -100 | 100 | 100 | +| -95 | 100 | 100 | +| -90 | 100 | 100 | +| -85 | 100 | 100 | +| -82 | 100 | 96 | +| -80 | 100 | 96 | +| -75 | 100 | 88 | +| -73 | 100 | 72 | + +Line graph titled 'Relative capacity versus micro BS noisefloor (Data144)' showing the relative capacity (%) of micro and macro networks as a function of micro BS noisefloor (dBm) for data at 144 kbps. The micro network (dashed blue line) remains constant at 100% capacity. The macro network (solid red line) starts at 100% capacity and begins to drop around -85 dBm, reaching approximately 72% at -73 dBm. + +Figure A.4: Relative capacity of macro and micro system versus micro BS noise floor (data 144 kbps). + +#### A.1.1.5 Micro-Micro scenario on adjacent frequencies + +Used layout of single micro layer as described in TR 25.942 chapter 5.3.1.2. Another micro layer is added by placing base stations in the middle of the other bases. + +![Figure A.5: Micro-Micro layout [units in meter]. The figure shows a 2D coordinate system with x-axis from -900 to 200 and y-axis from -1000 to 600. A green grid represents the street layout. Red circles represent base stations for micro network 1, and blue asterisks represent base stations for micro network 2. The base stations are arranged in a regular grid pattern, with network 1 stations at the intersections and network 2 stations at the midpoints of the grid lines.](97d95cd0cbe6c0c801edb6a4aaa5fc1c_img.jpg) + +Figure A.5: Micro-Micro layout [units in meter]. The figure shows a 2D coordinate system with x-axis from -900 to 200 and y-axis from -1000 to 600. A green grid represents the street layout. Red circles represent base stations for micro network 1, and blue asterisks represent base stations for micro network 2. The base stations are arranged in a regular grid pattern, with network 1 stations at the intersections and network 2 stations at the midpoints of the grid lines. + +Figure A.5: Micro-Micro layout [units in meter]. + +##### Speech + +Capacity loss in micro networks < 0.5 % for noise floor range –103 dBm to –73 dBm. + +##### Data 144 kbps + +Capacity loss in micro networks < 0.3 % for noise floor range –103 dBm to –73 dBm. + +### A.1.2 Blocking, ACS, and Intermodulation + +#### A.1.2.1 Macro to micro multi-operator case + +A multi-operator Macro-Micro scenario (as in TR 25.942 chapter 5.3.2) was investigated whereas the power level at the Micro BS receivers, based on the signals transmitted from the Ues connected to a FDD Wide Area (Macro) base station (BS), was calculated. The outcomes are overall CDF (Cumulative Probability Density Function) curves dependent on the used Macro cell size, the simulated service (speech and data 144kbps) and the maximum output power of the Ues. + +The Macro-Micro cell layout consists of a finite Micro cell layer (Manhattan grid) under a much larger finite macro network. The area close to the Micro network and the simulation input parameters are specified in TR 25.942 chapter 5.1.3.2. The used Macro-Micro cell deployment is shown in Figure A.6. + +The number of BS in this scenario is 72 Micro BS and 36 Macro BS. Macro cells scenarios with cell radii of 1km, 2km and 5km were used for the simulations. The scenario of an interfering 5 km macro cell across microcells is unrealistic and the results shown for this case are mainly for additional information. The chosen number of Macro BS ensures that the Micro cell grid experience infinite Macro cell grid (not all macro BS's are shown in Figure A.6 which is a zoomed picture showing the area close to the Micro cell grid). + +Additional to the scenarios stated in TR 25.942 chapter 5.1.3.2 a comparable multi-operator Micro-Micro scenario was investigated whereas the power level at the Micro BS receivers of network 1, based on the signals transmitted from the Ues connected to a Micro BS of network 2, was calculated. The outcomes are overall CDF curves dependent on the simulated service (speech and data 144kbps). The layout for a single Micro network is described in TR 25.942 chapter + +5.3.1.2., the description of the interfering micro-micro network topology and simulation parameters can be found in 5.2.4 in 25.942. + +For all scenarios described above a number of Monte Carlo simulations were done to determine the Interfering Signal mean power level for a victim Micro class BS in FDD mode. More details about simulations parameters and assumptions can be found in chapter A.1.2.3. + +![Figure A.6: Macro-Micro network deployment topology. The plot shows a 2D coordinate system with X-axis from -1200 to 600 and Y-axis from -1000 to 800. A green rectangular area from X=-800 to 200 and Y=-600 to 400 contains a grid of blue '+' markers representing micro base stations. A single black 'x' marker is located at approximately (-300, -600) within this grid, representing a victim micro base station. The background features a faint hexagonal grid pattern.](d1c99a42332e5ee19f3b840281c26681_img.jpg) + +Figure A.6: Macro-Micro network deployment topology. The plot shows a 2D coordinate system with X-axis from -1200 to 600 and Y-axis from -1000 to 800. A green rectangular area from X=-800 to 200 and Y=-600 to 400 contains a grid of blue '+' markers representing micro base stations. A single black 'x' marker is located at approximately (-300, -600) within this grid, representing a victim micro base station. The background features a faint hexagonal grid pattern. + +**Figure A.6: Macro-Micro network deployment topology, used with 1, 2, 5km macro cell size (zoomed example here for 1 km case).** + +![Micro-Micro layout diagram showing a grid of streets and base stations for two micro networks.](4dfe30ac5a87d018364a0ac42ea533fe_img.jpg) + +The diagram shows a rectangular area representing a street layout. The x-axis ranges from -900 to 200 meters, and the y-axis ranges from -1000 to 600 meters. A grid of green lines represents the streets. Red circles with black outlines represent base stations for 'micro network 1', spaced at regular intervals. Blue asterisks represent base stations for 'micro network 2', also spaced at regular intervals. The legend indicates: Street (green line), Base station micro network 1 (red circle), and Base station micro network 2 (blue asterisk). + +Micro-Micro layout diagram showing a grid of streets and base stations for two micro networks. + +Figure A.7: Micro-Micro layout [units in meter]. + +#### A.1.2.2 Simulation results + +![CDF curves for received interference power at the BS input for various macro-micro and micro-micro scenarios.](4936add03827ef5a51439c28ec878506_img.jpg) + +The graph plots the Cumulative Probability Density Function (y-axis, 0 to 1) against Received interference power (dBm) (x-axis, -130 to -20). Six curves are shown: 1. Macro-micro, 5 km, data UE 33 dBm (solid magenta line); 2. Macro-micro, 1 km, data, UE 21 dBm (dashed green line); 3. Macro-micro, 5 km, speech UE 33 dBm (dotted red line); 4. Macro-micro, 1 km, speech, UE 21 dBm (dash-dot blue line); 5. Micro-micro, data, UE 21 dBm (solid orange line); 6. Micro-micro, Speech, UE 21 dBm (dashed black line). The curves show that the cumulative probability increases as the received interference power increases. The 'Micro-micro, Speech' scenario reaches a CDF of 1 at approximately -65 dBm, while the 'Macro-micro, 5 km, data' scenario reaches it at approximately -45 dBm. + +CDF curves for received interference power at the BS input for various macro-micro and micro-micro scenarios. + +Figure A.8: CDF curves for the received interferer power at the BS input. + +![Figure A.9: Zoomed CDF curves for the received interferer power at the BS input. The plot shows Cumulative Probability Density Function (Y-axis, 0.9 to 1.0) versus Received interference power (dBm) (X-axis, -100 to -30). Six curves are plotted: Macro-micro, 5 km, data UE 33 dBm (magenta solid); Macro-micro, 1 km, data, UE 21 dBm (green dashed); Macro-micro, 5 km, speech UE 33 dBm (red dotted); Macro-micro, 1 km, speech, UE 21 dBm (blue dash-dot); Micro-micro, data, UE 21 dBm (orange solid); and Micro-micro, Speech, UE 21 dBm (black dashed).](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +Figure A.9: Zoomed CDF curves for the received interferer power at the BS input. The plot shows Cumulative Probability Density Function (Y-axis, 0.9 to 1.0) versus Received interference power (dBm) (X-axis, -100 to -30). Six curves are plotted: Macro-micro, 5 km, data UE 33 dBm (magenta solid); Macro-micro, 1 km, data, UE 21 dBm (green dashed); Macro-micro, 5 km, speech UE 33 dBm (red dotted); Macro-micro, 1 km, speech, UE 21 dBm (blue dash-dot); Micro-micro, data, UE 21 dBm (orange solid); and Micro-micro, Speech, UE 21 dBm (black dashed). + +**Figure A.9: Zoomed CDF curves for the received interferer power at the BS input.** + +Figures A.8 and A.9 show, as overview, the overall CDF of the input signals to the receiver for different scenarios. It can be seen that the maximum power levels based on the UEs connected to a second Micro cell is lower than the maximum power level created by the UEs connected to a Macro BS. Due to this fact the resulting blocking requirements must base on UEs connected to a Macro BS. The following figures contain zoomed plots for CDF values dependent on different scenarios. + +![Figure A.10: Zoom: Macro – Micro Blocking (Average) Speech in one plot UE 21 dBm 1,2 and 5km. The plot shows Cumulative Probability Density Function (Y-axis, 0.999 to 1.0) versus Received interference power (dBm) (X-axis, -60 to -20). Three curves are plotted: Cell radius 1 km (blue solid); Cell radius 2 km (red dashed); and Cell radius 5 km (green dotted). The title is 'Macro - Micro scenario, Speech, Max pwr UE 21 dBm,'.](a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg) + +Figure A.10: Zoom: Macro – Micro Blocking (Average) Speech in one plot UE 21 dBm 1,2 and 5km. The plot shows Cumulative Probability Density Function (Y-axis, 0.999 to 1.0) versus Received interference power (dBm) (X-axis, -60 to -20). Three curves are plotted: Cell radius 1 km (blue solid); Cell radius 2 km (red dashed); and Cell radius 5 km (green dotted). The title is 'Macro - Micro scenario, Speech, Max pwr UE 21 dBm,'. + +**Figure A.10: Zoom: Macro – Micro Blocking (Average) Speech in one plot UE 21 dBm 1,2 and 5km** + +Figure A.10 shows a typical scenario for speech UEs (21dBm) in a Macro cell network dependent on the used cell radii of 1, 2 or 5 km. + +![Figure A.11: Zoom: Macro – Micro Blocking data in one plot UE 33 dBm 1,2 and 5km. The plot shows the Cumulative Probability Density Function (Y-axis, 0.999 to 1) versus Received interference power (dBm) (X-axis, -60 to -20). Three curves are shown: Cell radius 1 km (solid blue line), Cell radius 2 km (dashed red line), and Cell radius 5 km (dotted green line). The curves show that as the cell radius increases, the cumulative probability of receiving interference power above a certain level decreases.](5dc5581cd2aad0e683c73b959f637b31_img.jpg) + +Macro - Micro scenario, Data 144 kbps, Max pwr UE 33 dBm, + +Cumulative Probability Density Function + +Received interference power (dBm) + +Cell radius 1 km + +Cell radius 2 km + +Cell radius 5 km + +Figure A.11: Zoom: Macro – Micro Blocking data in one plot UE 33 dBm 1,2 and 5km. The plot shows the Cumulative Probability Density Function (Y-axis, 0.999 to 1) versus Received interference power (dBm) (X-axis, -60 to -20). Three curves are shown: Cell radius 1 km (solid blue line), Cell radius 2 km (dashed red line), and Cell radius 5 km (dotted green line). The curves show that as the cell radius increases, the cumulative probability of receiving interference power above a certain level decreases. + +**Figure A.11: Zoom: Macro – Micro Blocking data in one plot UE 33 dBm 1,2 and 5km.** + +Figure A.11 shows a typical scenario for pure data UEs (33dBm) in a Macro cell network with cell radii of 1, 2 or 5 km. + +##### A.1.2.2.1 Blocking performance + +According to TR25.942, Sect 8.4.2.2 the target blocking probability for a macro-macro scenario was assumed to be $1e-4$ for the victim BS. Considering that a micro BS will typically deploy only 1 carrier and also that additional coverage may be available from an overlaid macro network (ie single operator HCS scenario), the event of blocking a micro BS may be considered as less severe than the blocking of a multi-carrier macro BS. Hence, a slightly higher blocking probability of $2e-4$ is assumed for the micro BS to reflect this difference and to avoid overly conservative blocking criteria. + +It has been shown e.g. in Figure A.10 and A.11 that the Blocking performance requirement for a general purpose BS of $-40\text{dBm}$ interfering Signal mean power, as it is specified in TS 25.104 (Rel.99, Rel. 4 and Rel. 5), is not sufficient for a FDD Medium Range (Micro) base station (BS). + +It has been shown in Figure A.11 (which represents the worst case) that for a high power UE (33dBm, data 144kbps) only in 0.02% of the cases the received power is larger or equal to $-35\text{dBm}$ and it is recommended to use this value as new blocking requirement. + +##### A.1.2.2.2 Adjacent Channel Selectivity + +The ACIR (Adjacent Channel Interference Power Ratio) is in the up-link dominated by the ACLR performance of the terminals. Therefore it is not needed to change the minimum selectivity for the medium range BS from the selectivity used for a general purpose BS, as specified in TS 25.104 (Rel.99, Rel. 4 and Rel. 5). + +Additional it is expected that the ACS should be tested with a wanted signal 6 dB above sensitivity as for a general purpose BS. + +Based on the assumptions described before it is recommended to change the interferer signal mean power level linear with the wanted signal mean power. Based on a 10dB relaxed sensitivity for a Micro BS, as it was recommended in chapter A.1.1.2, the following values are proposed: + +Wanted signal mean power: -105dBm (-115dBm general purpose BS) + +Interfering signal mean power: -42dBm (-52dBm general purpose BS) + +##### A.1.2.2.3 Intermodulation Characteristics + +Receiver intermodulation can occur when two interfering signals with a particular relationship are applied to a BS receiver. The probability of two signals interfering the same BS simultaneously should be in the same order than probability for blocking interferer level. We assume a reasonable value of 0.01% . Assuming two independent networks the probability is the multiplication of the probability of an interferer power level based on network 1 and the corresponding probability based on network 2. + +Starting with the likely scenario with two networks, one Macro and one Micro, serving Ues which interferes a victim Micro BS. In this case the interferer levels are normally not equal resulting in one Interferer with higher power ( $Int_{high}$ ) and one Interferer with low power ( $Int_{low}$ ). On the other hand it is beneficial to recalculate a requirement based on equal interferers. This approach allows one requirement covering different scenarios. Based on a simple IM3 scenario the following formula can be used: + +$$\text{Equivalent Interfering Signal mean power [dBm]} = (2 * Int_{high} \text{ [dBm]} + Int_{low} \text{ [dBm]}) / 3$$ + +The CDF curve of a Micro – Micro scenario is very sharp (see Figure X10). The probability of an interference signal of > -66dBm is smaller than 1% but the probability of an interference signal of > -68dBm is in the order of 10%. Keeping the overall required probability of 0.01% and using a 10% probability for the interference of the Micro network a target value of 0.999 for the CDF of a Macro network is remaining. This results in an interferer level of –33dBm for the $Int_{high}$ . (Figure X11a) The calculated interferer levels are: + +$$\text{Interferer Requirement [dBm]} = (2 * (-33) \text{ [dBm]} + (-68) \text{ [dBm]}) / 3 = -44.7\text{dBm}$$ + +Based on the calculation above an interfering signal mean power level of –44dBm is proposed. This value is 9dB smaller than the proposed interferer level of –35dBm for blocking. This difference is in the same order of magnitude like the difference between the interferers for blocking and intermodulation in case of a wide area BS. + +Assuming now two equal but independent Macro or Micro networks serving Ues which interferes a victim Micro BS. In this case the probability for one interfering signal increasing the required power level at the Micro BS receiver should be smaller than 1.41 %. It is shown in Figure A.9 that the proposed requirement of –44dBm interferer level for a medium range BS is sufficient also for these scenarios. + +#### A.1.2.3 Simulation parameters + +**Table A.2: Simulation Parameters** + +| Simulation parameter
Uplink | | +|------------------------------------------------|---------------------------------------------------| +| MCL macro / micro | 70 / 53 dB | +| Antenna gain (including losses) | | +| Base station | 11 dBi | +| Mobile | 0 dBi | +| Log-normal shadow fading
standard deviation | 10 dB | +| Noise floor RBS receiver | | +| Macro / micro | -103 / -93 dBm | +| Maximum TX power speech | 21, 24, 27, 33 dBm | +| Maximum TX power data | 21, 33 dBm | +| Minimum TX power speech | -50 dBm | +| ACIR | 33 dB | +| Power control | Perfect PC | +| Power control error | 0.01 dB | +| Outage condition | C/I target not reached due to lack of TX power | +| Admission control | Not included | +| Macro User distribution in macro network | Random and uniform over the network | +| Micro User distribution in micro network | Random and uniform over the streets | +| Macro User distribution in micro network | Random and uniform over the streets | +| Bit rate speech | 8 kbps | +| Activity factor speech | 100 % | +| Eb/No target speech | | +| macro / micro | 6.1 / 3.3 dB | +| Bit rate data | 144 kbps | +| Activity factor data | 100 % | +| Eb/No target data | | +| macro / micro | 3.1 / 2.4 dB | +| Micro deployment | Manhattan scenario | +| Block size | 75 m | +| Road width | 15 m | +| Intersite distance between line-of-sight | 180 | +| Number of micro cells | 72 | +| Number of macro cells | 3 affected macros
36 in total | +| Macro cell radius | 1 km / 2km / 5km (5 km case for information only) | + +## A.2 Pico base stations in FDD mode + +### A.2.1 Mixed microcell-picocell scenario + +Studies and simulations have been performed in order to define requirements for the Local area BS class. The simulations were done using a mixed microcell-picocell environment, where the pico environment is embedded in the micro environment. The size of the pico environment is one building with 20 rooms, and the micro environment consists of 9 buildings in a 3x3 array. Figure A.12 shows a diagram of the environment. + +![Figure A.12: Mixed micro-pico environment with 12 micro and 10 pico base stations. The diagram shows a grid of buildings (black rectangles) and streets (light blue). Micro base stations are marked with blue asterisks (*) and pico base stations are marked with red plus signs (+). The grid is approximately 350x350 units, with buildings of varying sizes and street widths. The central area contains a cluster of pico base stations.](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +Figure A.12: Mixed micro-pico environment with 12 micro and 10 pico base stations. The diagram shows a grid of buildings (black rectangles) and streets (light blue). Micro base stations are marked with blue asterisks (\*) and pico base stations are marked with red plus signs (+). The grid is approximately 350x350 units, with buildings of varying sizes and street widths. The central area contains a cluster of pico base stations. + +**Figure A.12: Mixed micro-pico environment with 12 micro and 10 pico base stations** + +Appropriate requirements for LA BS blocking are derived from the results of these additional simulations. + +Proposals for this and other relevant receiver requirements for the Local area BS class will be presented in following sections. + +### A.2.2 Receiver sensitivity + +A number of simulations were performed to study the impact of the noise rise in both micro- and picocell scenarios. The results are applicable for both multi-operator or a single operator case. + +#### A.2.2.1 Simulation parameters + +Used simulation parameters can be found in Table A.3. + +**Table A.3: Simulation parameters** + +| Parameter | Value | Comments | +|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Active set size | 1 or 3 | 1 is HHO, 3 is SHO | +| Number of BSs | 12 Micro BSs,
10 Pico BSs | | +| ACS/ACLR/ACIR | UE: 33/33, BS:45/45
UL: 32.73, DL: 32.73
or
UE: 43/43 , BS: 45/45,
UL: 40.88, DL: 40.88
or
UE: 33/33, BS: 50/50
UL: 32.91, DL: 32.91 | | +| Base station transmission powers:
Min/Max/MinPerUser/MaxPerUser | Micro:
Min: 23 dBm,
Max 33 dBm,
Min per User: 5 dBm
Max per User: 30 dBm

Pico:
Min: 14 dBm,
Max 24 dBm,
Min per User: 21 dBm
Max per User: -4 dBm | The minimum BS tx powers are derived from pilot powers: Pilot power = BS max power – 10 dB. | +| Simulated services | 12 kbps speech (Processing gain=315) ,
142 kbps data (processing gain = 27) | One simulation is always either purely data or purely speech, there are no mixed data-speech cases. | +| Speech EbNo-targets | Micro:
UL 3.3 dB, DL 7.9 dB
Pico:
UL 3.3 dB, DL 6.1 dB | | +| Data EbNo-targets | Micro:
UL 2.4 dB, DL 1.9 dB
Pico:
UL 2.4 dB, DL 1.9 dB | | +| DL Outage target | 5 % | Same for both pico and micro.
NOTE: This was basically irrelevant since it was not reached in any of the simulations. | +| UL Noise rise target | 6 dB | Same for both pico and micro | +| Minimum Coupling loss | Micro : 53 dB
Pico : 45 dB | | +| Propagation Model | According to 25.951 | | +| UE Tx power limits | Min: -50 dBm
Max: 21 dBm | | +| Slow fading deviation (Mean: 0 dB) | Micro: 6 dB
Pico: 6 dB | | +| DL System noise | -99 dBm (both micro and pico) | | +| UL system noise | -103 dBm (both micro and pico) | | +| Number of Pico cell users | Speech, AS1: 60
Speech, AS3: 62
Data, AS1: 35
Data, AS3: 40 | The numbers of users were selected such that 6 dB noise rise was reached in reference cases | +| Number of Micro cell users | Speech, AS1: 185(0% indoors) or 200(10% indoors)
Speech, AS3: 185 (0% indoors) or 205 (10% indoors)
Data, AS1: 65 (0% indoors) or 67 (10% indoors)
Data,AS3: 75 (0% indoors) or 77 (10% indoors) | The numbers of users were selected such that 6 dB noise rise was reached in reference cases | + +#### A.2.2.2 Simulation results + +Additional noise rise was studied for the both micro- and picocell BSs. In cases where all micro users are outdoors different operators doesn't disturb each others. There is no influence in UL. + +Figure A.13 covers the situation where all micro users are located outdoors and are using speech service. Also situation when 10 % of microcell users are inside is presented in Figure A.13. UL noise rise in pico is growing and this represent the worst case. + +Figure A.14 covers the situation when 10 % of microcell users are indoors. UL noise rise is presented as a function of ACIR value. + +Results with data service are almost identical to speech service. Because user bit rates are bigger, disturbance from single user is bigger and random factors may affect the results. Micro suffers relatively less than pico. + +The worst case noise rise for picocell BSs is 15.8 dB which means 9.8 dB noise rise compared to macro. A macro value comparable to high load with 75% pole capacity is 6 dB. + +![Figure A.13: UL noise rise versus ACIR value. A line graph titled 'Noise rise, AS1' showing noise rise in dB for four cases: Ref, Mixed, ACIR1, Mixed, ACIR2, and Mixed, ACIR3. The y-axis ranges from 0 to 18 dB. The x-axis shows the cases. Four data series are plotted: Micro, 0% micro users indoors (blue diamonds), Pico, 0% micro users indoors (magenta squares), Micro, 10% micro users indoors (yellow triangles), and Pico, 10% micro users indoors (cyan crosses). The Pico, 10% micro users indoors series shows a significant increase in noise rise, peaking at approximately 16 dB for Mixed, ACIR1 and Mixed, ACIR3 cases, while the other three series remain relatively flat around 6 dB.](2c4f0f278bff4a04fd08f62808ae2a82_img.jpg) + +| Cases | Micro, 0% micro users indoors [dB] | Pico, 0% micro users indoors [dB] | Micro, 10% micro users indoors [dB] | Pico, 10% micro users indoors [dB] | +|--------------|------------------------------------|-----------------------------------|-------------------------------------|------------------------------------| +| Ref | 6 | 6 | 6 | 6 | +| Mixed, ACIR1 | 6 | 6 | 6 | 16 | +| Mixed, ACIR2 | 6 | 6 | 6 | 11 | +| Mixed, ACIR3 | 6 | 6 | 6 | 16 | + +Figure A.13: UL noise rise versus ACIR value. A line graph titled 'Noise rise, AS1' showing noise rise in dB for four cases: Ref, Mixed, ACIR1, Mixed, ACIR2, and Mixed, ACIR3. The y-axis ranges from 0 to 18 dB. The x-axis shows the cases. Four data series are plotted: Micro, 0% micro users indoors (blue diamonds), Pico, 0% micro users indoors (magenta squares), Micro, 10% micro users indoors (yellow triangles), and Pico, 10% micro users indoors (cyan crosses). The Pico, 10% micro users indoors series shows a significant increase in noise rise, peaking at approximately 16 dB for Mixed, ACIR1 and Mixed, ACIR3 cases, while the other three series remain relatively flat around 6 dB. + +Figure A.13: UL noise rise versus ACIR value + +![Figure A.14: UL noise rise versus ACIR value with AS1 and AS3. A line graph titled 'Pico, Noise rise, 10% Micro users indoors' showing noise rise in dB for four cases: Ref, Mixed, ACIR1, Mixed, ACIR2, and Mixed, ACIR3. The y-axis ranges from 0 to 18 dB. The x-axis shows the cases. Two data series are plotted: AS1 (blue diamonds) and AS3 (magenta squares). Both series show a significant increase in noise rise, peaking at approximately 16 dB for Mixed, ACIR1 and Mixed, ACIR3 cases, with AS1 consistently showing slightly higher noise rise than AS3.](76fd4ccd10dcf423d796c0a1e66a899f_img.jpg) + +| Cases | AS1 [dB] | AS3 [dB] | +|--------------|----------|----------| +| Ref | 6 | 6 | +| Mixed, ACIR1 | 16 | 15.8 | +| Mixed, ACIR2 | 11 | 10.8 | +| Mixed, ACIR3 | 16 | 15.8 | + +Figure A.14: UL noise rise versus ACIR value with AS1 and AS3. A line graph titled 'Pico, Noise rise, 10% Micro users indoors' showing noise rise in dB for four cases: Ref, Mixed, ACIR1, Mixed, ACIR2, and Mixed, ACIR3. The y-axis ranges from 0 to 18 dB. The x-axis shows the cases. Two data series are plotted: AS1 (blue diamonds) and AS3 (magenta squares). Both series show a significant increase in noise rise, peaking at approximately 16 dB for Mixed, ACIR1 and Mixed, ACIR3 cases, with AS1 consistently showing slightly higher noise rise than AS3. + +Figure A.14: UL noise rise versus ACIR value with AS1 and AS3 + +As a conclusion the simulations results show that there is no noise rise if all micro users are located outdoors. If some users are located indoors noise rise will rise in pico UL. + +#### A.2.2.3 Noise rise for UL in Picocell environment + +In this chapter we analyse more detail the noise rise for UL in Picocell environment. The most important and a typical scenario for adjacent channel interference could be a UE at the edge of a microcell transmitting high power in UL close to a picocell BS. However, at the same time, the UE is receiving interference from the picocell BS on the adjacent carrier in DL. This can lead to DL blocking of an interfering UE thus reducing the overall level of adjacent channel interference to picocell BS. A detailed analysis is presented in section A.2.2.4. As a result a noise rise is 4 dB...11.7 dB depending on the bit rate in the UL (12.2 kbps...144 kbps). + +The analytical study indicates that the additional noise rise in picocell due to other operator microcell is in the range of 4 dB...11.7 dB above the microcell interference levels. Microcell noise rise compared to macrocell was <2 dB as presented in [5]. Additional picocell noise rise compared to current specification will be though 13.7 dB in the worst case. + +#### A.2.2.4 UL noise rise calculation for the picocell BS + +The additional UL noise rise in WCDMA FDD picocell BS due the adjacent channel operation has been computed here. The basic scenario has been shown in Figure A.15. + +![Diagram illustrating micro- and picocell operation at adjacent frequency bands. A microcell user (Pm) is shown outside a picocell base station (Pp). The pathloss from the microcell antenna to the mobile is Lm. The pathloss from the pico base station to the mobile is Lp. The mobile is receiving interference from the pico base station (Pp) and transmitting to the microcell user (Pm). The picocell base station (Pp) is also receiving interference from the mobile (PUE).](24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg) + +Diagram illustrating micro- and picocell operation at adjacent frequency bands. A microcell user (Pm) is shown outside a picocell base station (Pp). The pathloss from the microcell antenna to the mobile is Lm. The pathloss from the pico base station to the mobile is Lp. The mobile is receiving interference from the pico base station (Pp) and transmitting to the microcell user (Pm). The picocell base station (Pp) is also receiving interference from the mobile (PUE). + +**Figure A.15. Micro- and picocell operation at adjacent frequency bands.** + +The required power for the microcell user can be computed by the equation: + +$$\frac{\frac{W p_m}{R L_m}}{\frac{P_p}{L_p \cdot ACIR_{DL}} + I_{own}(1-\alpha) + I_{oth} + N} \geq \rho,$$ + +where $P_m$ is the power allocated to the microcell user, $L_m$ is the pathloss from the microcell antenna to the mobile, $P_p$ is the power of the pico BS, $L_p$ is the pathloss from pico base station to the mobile and $ACIR\_DL$ is the adjacent channel interference in the downlink. Assuming that most of the interference comes from an other operator's pico cell the minimum required pathloss: + +$$L_p \geq \frac{\rho \cdot R \cdot L_m}{W \cdot ACIR_{DL}} \frac{P_p}{P_m}$$ + +The uplink interference at the pico BS can therefore computed as: + +$$I = \frac{P_m}{P_p} \cdot \frac{P_{UE} \cdot W \cdot ACIR_{DL}}{ACIR_{UL} \cdot \rho \cdot R \cdot L_m}$$ + +$$\frac{W}{R_{UL} L_m I_{UL}} = \rho_{UL} \Rightarrow P_{UE} = \frac{\rho_{UL} L_m I_{UL} R_{UL}}{W}$$ + +$$I = \frac{P_m}{P_p} \cdot \frac{W \cdot ACIR_{DL}}{ACIR_{UL} \cdot \rho \cdot R \cdot L_m} \cdot \frac{\rho_{UL} L_m I_{UL} R_{UL}}{W}$$ + +$$I = \frac{P_m}{P_p} \cdot \frac{\rho_{UL} I_{UL} R_{UL} \cdot ACIR_{DL}}{ACIR_{UL} \cdot \rho \cdot R}$$ + +The DL dedicated channel power in micro can be written as: + +$$p_m = \frac{P_{\text{pilot}} R \rho}{\chi \cdot R_{\text{ref}} \rho_{\text{ref}}},$$ + +where $\chi$ is the power adjustment factor; when $\chi=1$ (0 dB), the reference service is given the same power as for the pilot channel, when $\chi=2$ (3 dB), for instance, the reference service is given 3 dB less power than for the pilot. + +The interference can be then written as: + +$$I = \frac{P_{\text{pilot}} R \rho}{\chi \cdot R_{\text{ref}} \rho_{\text{ref}}} \frac{1}{P_p} \cdot \frac{\rho_{\text{UL}} I_{\text{UL}} R_{\text{UL}} \cdot \text{ACIR}_{\text{DL}}}{\text{ACIR}_{\text{UL}} \cdot \rho \cdot R} = \frac{P_{\text{pilot}}}{\chi \cdot R_{\text{ref}} \rho_{\text{ref}}} \frac{1}{P_p} \cdot \frac{\rho_{\text{UL}} I_{\text{UL}} R_{\text{UL}} \cdot \text{ACIR}_{\text{DL}}}{\text{ACIR}_{\text{UL}}}$$ + +RUL, $\rho_{\text{UL}}$ are UL parameters for the microcell RAB + +Rref, pref are DL parameters of the microcell ref RAB + +So what we can notice is that the interference in UL in pico is independent on the pathloss between micro and pico. + +Then, if + +$P_{\text{pilot}}=30$ dBm + +$\chi=1$ + +$R_{\text{ref}}=12.2$ kbps + +$\rho_{\text{UL}}=5$ dB + +$\rho_{\text{ref}}=8$ dB + +$R_{\text{UL}}=12.2$ kbps + +$\text{ACIR\_DL/ACIR\_UL}=-3$ dB ; + +$P_p=20$ dBm + +$$I = \frac{P_{\text{pilot}}}{\chi \cdot R_{\text{ref}} \rho_{\text{ref}}} \frac{1}{P_p} \cdot \frac{\rho_{\text{UL}} I_{\text{UL}} R_{\text{UL}} \cdot \text{ACIR}_{\text{DL}}}{\text{ACIR}_{\text{UL}}} \\ \frac{1000}{1} \frac{1}{100} \cdot \frac{I_{\text{UL}}}{2 \cdot 2} = 2.5 \cdot I_{\text{UL}} = 4 + I_{\text{UL}}(\text{dB})$$ + +So it is 4 dB above the micro interference levels + +Then, if + +$R_{\text{UL}}=144$ kbps + +$\rho_{\text{UL}}=2$ dB + +$\text{ACIR\_DL/ACIR\_UL}=-3$ dB ; + +$$I = \frac{P_{\text{pilot}}}{\chi \cdot R_{\text{ref}} \rho_{\text{ref}}} \frac{1}{P_p} \cdot \frac{\rho_{\text{UL}} I_{\text{UL}} R_{\text{UL}} \cdot \text{ACIR}_{\text{DL}}}{\text{ACIR}_{\text{UL}}} \\ \frac{1000}{1} \frac{1}{100} \cdot \frac{I_{\text{UL}}}{2 \cdot 4} \cdot \frac{144}{12.2} = 14 \cdot I_{\text{UL}} = 11.7 + I_{\text{UL}}(\text{dB})$$ + +So it is 11.7 dB above the micro interference levels. + +#### A.2.2.5 Reference sensitivity level + +The analytical study in section A.2.2.4 showed that additional noise rise in pico cells due to another operator's interfering micro cells is in the range of 4 dB...13.7 dB. Noise rise is depending on the bit rate in the UL (12.2 kbps...144 kbps). For the worst case, the picocell noise rise was 13.7 dB compared to a macro cell. Based on that 14 dB sensitivity degradation is proposed for the Local area BS class. + +### A.2.3 Dynamic range, ACS, Blocking and Intermodulation + +#### A.2.3.1 Simulation parameters + +**Table A.4: Simulation Parameters** + +| Parameter | Value | Comments | +|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Active set size | 3 | For SHO | +| Number of BSs | 12 Micro BSs,
10 Pico BSs | | +| ACS/ACLR/ACIR | Not used here for blocking simulations | | +| Base station transmission powers:
Min/Max/MinPerUser/MaxPerUser | Micro:
Min: 23 dBm,
Max 33 dBm,
Min per User: 5 dBm
Max per User: 30 dBm

Pico:
Min: 14 dBm,
Max 24 dBm,
Min per User: 21 dBm
Max per User: -4 dBm | The minimum BS tx powers are derived from pilot powers: Pilot power = BS max power – 10 dB. | +| Simulated services | 144 kbps data | | +| Speech EbNo-targets | - | | +| Data EbNo-targets | Micro:
UL 2.4 dB, DL 1.9 dB
Pico:
UL 2.4 dB, DL 1.9 dB | | +| DL Outage target | 5 % | Same for both pico and micro.
NOTE: This was basically irrelevant since it was not reached in any of the simulations. | +| UL Noise rise target | 6 dB | Same for both pico and micro | +| Minimum Coupling loss | Micro : 53 dB
Pico : 45 dB | | +| Propagation Model | According to 25.951 | | +| UE Tx power limits | Min: -50 dBm
Max: 21 dBm | | +| Slow fading deviation (Mean: 0 dB) | Micro: 6 dB
Pico: 6 dB | | +| DL System noise | -99 dBm (both micro and pico) | | +| UL system noise | -103 dBm (both micro and pico) | | +| Number of Pico cell users | Data, AS3: 40 | The numbers of users were selected such that 6 dB noise rise was reached in reference cases | +| Number of Micro cell users | 77 (10% indoors) | The numbers of users were selected such that 6 dB noise rise was reached in reference cases | + +#### A.2.3.2 Dynamic range + +It is proposed not to tighten the requirement for the Receiver dynamic range for the LA BS class. It should be tested with a wanted signal 30 dB above sensitivity. Correspondingly, the difference between wanted and interfering signals remains the same as for Wide area BS. + +Following signals are proposed for Dynamic range: + +- wanted signal: –77dBm +- interfering AWGN signal: –59 dBm. + +#### A.2.3.3 ACS + +The ACIR (Adjacent Channel Interference Power Ratio) is in the up-link dominated by the ACLR performance of the terminals. Therefore it is not needed to change the minimum selectivity for the LA BS from the selectivity used for a general purpose BS, as specified in TS 25.104. + +Based on these assumptions, it is recommended to change the interferer signal mean power level linear with the wanted signal mean power. Additionally, it is expected that the ACS should be tested with a wanted signal 6 dB above sensitivity as for a general purpose BS. + +Following signals are proposed for ACS: + +- wanted signal -101 dBm +- interfering signal -38 dBm. + +#### A.2.3.4 Blocking characteristics + +In order to derive a blocking requirement, we may want to relate it to the ACS requirement. For a single carrier LA BS, the impact of adjacent channel interference reaching a given interference level (ie -38 dBm as proposed in the previous section) is essentially the same as if a blocking level would be reached; in either case the LA BS receiver will be desensitized by 6 dB effecting the same amount of connections (due to the single carrier assumption). + +Hence, given identical consequences of these 2 events, we may then require the same (low) probability of occurrence for them. + +There are at most 2 adjacent carriers where adjacent channel interference can occur for a given LA BS RX carrier. However, within the Band I allocation of 12 carriers, there may be at most $12 - 2 - 1 = 9$ carriers where blocking (but not adjacent channel interference) may originate from; thus having an approximately 4.5 times larger chance of occurring (assuming the same event probabilities for ACS, respectively blocking). The exact combinatorics should also take carriers at the band edge into account + +Hence, one may now wish to ensure that blocking does occur at least 4.5 times less than adjacent channel interference. In order to do this, we will consider the resulting UL interference at the LA BS due to the micro cell UE's for the following two cases: + +- blocking of micro cell UE's due to the LA BS is not considered +- blocking of micro cell UE's due to the LA BS is considered with a blocking threshold of -39 dBm, ie 5 dB higher than the corresponding value from TS 25.101 (= -44 dBm). + +Figure A.16 shows a simulation results for 144 kbps data service with 10 % of the micro Ues indoors (worst case) for case a) with no UE blocking considered. As can be seen in zoomed version in Figure A.17, the proposed interfering signal of -38 dBm for ACS corresponds to value where 97.325% of 43 occurrences of the input signals to the receivers are less this level. Hence, probability to get blocked by ACS will be $1 - 0.97325 = 0.02675$ . + +![CDF plot titled 'UL Adjacent operator interference in Pico, CDF' showing interference power levels from -120 to -20 dBm.](a85105fd544c64ef624aa45c72378647_img.jpg) + +The figure is a Cumulative Distribution Function (CDF) plot titled "UL Adjacent operator interference in Pico, CDF". The x-axis represents the received interference power in dBm, ranging from -120 to -20 with major ticks every 10 dBm. The y-axis represents the cumulative probability, ranging from 0 to 1 with major ticks every 0.1. A blue curve starts at approximately (-110, 0) and rises to 1 at approximately -30 dBm. The curve passes through the point (-60, 0.5), indicating that the median interference power is -60 dBm. The plot includes a dotted grid for both axes. + +| Interference Power (dBm) | Cumulative Probability | +|--------------------------|------------------------| +| -120 | 0.00 | +| -110 | 0.00 | +| -100 | 0.01 | +| -90 | 0.05 | +| -80 | 0.12 | +| -70 | 0.25 | +| -60 | 0.50 | +| -50 | 0.75 | +| -40 | 0.90 | +| -30 | 0.98 | +| -20 | 1.00 | + +CDF plot titled 'UL Adjacent operator interference in Pico, CDF' showing interference power levels from -120 to -20 dBm. + +Figure A.16: Received UL interference at LA BS, no UE blocking + +![Figure A.17: UL Adjacent operator interference in Pico, CDF. The graph shows the Cumulative Distribution Function (CDF) of received UL interference at a LA BS, with no UE blocking. The x-axis represents the interference power in dBm, ranging from -40 to -30. The y-axis represents the CDF value, ranging from 0.965 to 0.995. The curve starts at approximately (-40, 0.963) and rises to approximately (-30, 0.995).](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +| Interference Power (dBm) | CDF | +|--------------------------|-------| +| -40 | 0.963 | +| -39 | 0.968 | +| -38 | 0.973 | +| -37 | 0.977 | +| -36 | 0.982 | +| -35 | 0.985 | +| -34 | 0.989 | +| -33 | 0.992 | +| -32 | 0.993 | +| -31 | 0.994 | +| -30 | 0.995 | + +Figure A.17: UL Adjacent operator interference in Pico, CDF. The graph shows the Cumulative Distribution Function (CDF) of received UL interference at a LA BS, with no UE blocking. The x-axis represents the interference power in dBm, ranging from -40 to -30. The y-axis represents the CDF value, ranging from 0.965 to 0.995. The curve starts at approximately (-40, 0.963) and rises to approximately (-30, 0.995). + +**Figure A.17: Received UL interference at LA BS, no UE blocking** + +According to above methodology, one may now wish to ensure that blocking does occur at least 4.5 times less than adjacent channel interference. Hence, we obtain for the probability for blocking $0.02675 / 4.5 = 0.00594$ . We will have CDF value $1 - 0.00594 = 0.9945$ . From the Figure A.17, we derive the required value for interfering (blocking) signal to be around $-30$ dBm. + +In reality, micro cell UE's will become blocked due to the strong signal from the LA BS, before they can cause significant interference (blocking) to the LA BS on UL. Thus the received UL interference CDFs in Figures A.16 and A.17 are very pessimistic and do not reflect the real situation adequately. + +Figures A.18 and A.19 show CDFs with DL UE blocking included. UEs receiving higher interfering signal than a blocking threshold of $-39$ dBm will be removed from the UL interference statistics. As can be seen, UL interference levels at LA BS are significantly reduced. + +The event probabilities for “ACS blocking” are now 0.00525. Probabilities for “blocking” are respectively 0 (i.e. LA BS blocking did not occur at all). + +Two remarks are appropriate: + +- blocker level of $-44$ dBm in TS 25.101 is only a minimum performance requirement and may be exceeded by actual UE implementation. Here it is assumed that for a 5 dB higher level ( $-39$ dBm) blocking has indeed occurred. +- Micro cell UE's may also lose connection due to ACLR/spurious emissions from LA BS under low CL conditions. This effect is, however, not included in the CDFs and the shown results including UE blocking are thus conservative + +![CDF of UL interference at the Pico Node Bs (DL blocked UEs filtered out). The graph shows a blue curve representing the cumulative distribution function of UL interference in dBm, with a legend indicating a DL Blocking Threshold of -39 dBm.](0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg) + +The figure is a Cumulative Distribution Function (CDF) plot titled "CDF of UL interference at the Pico Node Bs (DL blocked UEs filtered out)". The y-axis is labeled "CDF of UL interference" and ranges from 0 to 1. The x-axis is labeled "dBm" and ranges from -120 to -30. A blue curve represents the CDF, starting near 0 at -120 dBm and reaching 1 at approximately -35 dBm. A legend box in the lower right of the plot area contains the text "DL Blocking Threshold = -39 dBm". + +| dBm | CDF of UL interference | +|------|------------------------| +| -120 | 0.00 | +| -110 | 0.01 | +| -100 | 0.03 | +| -90 | 0.08 | +| -80 | 0.25 | +| -70 | 0.45 | +| -60 | 0.70 | +| -50 | 0.90 | +| -40 | 0.98 | +| -35 | 1.00 | + +CDF of UL interference at the Pico Node Bs (DL blocked UEs filtered out). The graph shows a blue curve representing the cumulative distribution function of UL interference in dBm, with a legend indicating a DL Blocking Threshold of -39 dBm. + +Figure A.18: Received UL interference at LA BS, with UE blocking at -39 dBm + +![Figure A.19: CDF of UL interference at the Pico Node Bs (DL blocked UEs filtered out). The graph shows the Cumulative Distribution Function (CDF) of UL interference in dBm. The x-axis ranges from -40 dBm to -30 dBm, and the y-axis ranges from 0.99 to 1. A blue line represents the CDF, with a legend indicating 'DL Blocking Threshold = -39 dBm'. The curve starts at approximately (-40, 0.99) and rises to (1, -33).](068b3a3247570c4b78342a943f15de9e_img.jpg) + +| dBm | CDF of UL interference | +|-----|------------------------| +| -40 | 0.990 | +| -39 | 0.992 | +| -38 | 0.994 | +| -37 | 0.996 | +| -36 | 0.997 | +| -35 | 0.998 | +| -34 | 0.999 | +| -33 | 1.000 | + +Figure A.19: CDF of UL interference at the Pico Node Bs (DL blocked UEs filtered out). The graph shows the Cumulative Distribution Function (CDF) of UL interference in dBm. The x-axis ranges from -40 dBm to -30 dBm, and the y-axis ranges from 0.99 to 1. A blue line represents the CDF, with a legend indicating 'DL Blocking Threshold = -39 dBm'. The curve starts at approximately (-40, 0.99) and rises to (1, -33). + +**Figure A.19: Received UL interference at LA BS, with UE blocking at $-39$ dBm** + +Based on these findings it is proposed that a blocker level of $-30$ dBm is sufficient for a LA BS. + +Blocking characteristics of the Local area BS can be tested with the wanted signal level 6 dB above Reference sensitivity level as for Wide area BS. For Local area BS that means the level $-121$ dBm + 14 dB + 6 dB = $-101$ dBm. + +Based on this following signals are proposed for In band blocking: + +- wanted signal $-101$ dBm +- interfering signal $-30$ dBm. + +Out of band blocking requirements can be kept unchanged except the wanted signal which will be 6 dB above reference sensitivity level. + +#### A.2.3.5 Intermodulation characteristics + +Receiver intermodulation can occur when two interfering signals with a particular relationship are applied to a BS receiver. Two large interfering signals at the same time occurs less frequently than a single interfering signal. Due to lower probability of two large interfering signals, the power level of the interfering signals for the Intermodulation requirement should be lower compared to Blocking requirement. For the Wide area BS, the level of interfering signals are 8 dB lower compared to Blocking requirement. It is proposed same relative values also for the Local area BS. + +Following signals for Intermodulation is proposed: + +- wanted signal –101 dBm +- interfering signals –38 dBm. + +## --- A.3 Maximum output power for Medium range BS class + +### A.3.1 Simulation results #1 + +#### A.3.1.1 Simulation scenario + +Earlier simulations were performed based on an statistical approach where the criteria for micro BS output power is defined as the outage probability for uncoordinated macro network UE:s. + +In order to compare the outage due to micro layer with reference cases, simulations for single macro layer and macro-macro cell layout with maximum offset between the two uncoordinated macro layers (worst case) were also performed. The maximum output power of the interfering Wide area BSs in the macro-macro cell layout was limited to the typical value of 43dBm. + +The approach is conservative because the comparison with the macro-macro cell layout is based on interfering Wide area BS with a maximum output power of 43dBm. In real life this value could be much higher as up to 50dBm. + +#### A.3.1.2 Simulation results + +The new simulations were again based on the macro-micro cell layout in where the micro cell layer were assumed to be fully loaded for different values for micro output power. In order to compare the outage due to micro layer with reference cases, simulations for single macro layer and macro-macro cell layout with maximum offset between the two uncoordinated macro layers (worst case) were performed. + +The maximum output power for the interfering Wide area BSs was set to 47dBm (50W). The value of 47dBm is assumed as a realistic worst-case scenario for the given cell layout. The maximum output power of the Wide Area BSs of the disturbed macro layer network was kept to 43dBm and the maximum code power was limited to 30dBm. + +The outage probability on macro layer for site-to-site distances of 1 km (cell radius of 577m) in the presence of a micro cell grid for a fixed micro output power of 27, 30, 33, 34, 35, 36, and 37dBm for each BS are as following: + +![Figure A.20: Outage probability for the users connected to the macro cells for macro site-to-site distance of 1 km and a fixed maximum output power of up to 37dBm per Medium Range BS. The graph plots Outage Probability (cell) [%] on the y-axis (0 to 10) against the Average number of users per cell on the x-axis (48 to 62). Six curves are shown: Single Macro (blue solid), Macro-Macro (43dBm) (red dashed), Macro-Macro (47dBm) (red solid), Micro-Macro (37 dBm) (green dashed), Micro-Macro (33 dBm) (green solid), and a black dashed line. The Single Macro curve rises sharply after 60 users. The other curves show lower outage probabilities, indicating improved capacity due to the presence of micro cells.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +Figure A.20: Outage probability for the users connected to the macro cells for macro site-to-site distance of 1 km and a fixed maximum output power of up to 37dBm per Medium Range BS. The graph plots Outage Probability (cell) [%] on the y-axis (0 to 10) against the Average number of users per cell on the x-axis (48 to 62). Six curves are shown: Single Macro (blue solid), Macro-Macro (43dBm) (red dashed), Macro-Macro (47dBm) (red solid), Micro-Macro (37 dBm) (green dashed), Micro-Macro (33 dBm) (green solid), and a black dashed line. The Single Macro curve rises sharply after 60 users. The other curves show lower outage probabilities, indicating improved capacity due to the presence of micro cells. + +**Figure A.20: Outage probability for the users connected to the macro cells for macro site-to-site distance of 1 km and a fixed maximum output power of up to 37dBm per Medium Range BS** + +The simulations show that the capacity of a macro layer is reduced, due to the presence of an uncoordinated micro or macro layer. Based on the outage target of 5%, the capacity is nearly identical in the presence of a macro layer where the macro BSs transmits with a constant power of 47dBm or where all the micro BS:s transmits at a constant power level of 37 dBm (see table A.5) + +**Table A.5: Worst case capacity of the macro cell layer for macro site-to-site distance of 1 km and a fixed maximum output power of 33 and 37dBm per Medium Range BS** + +| Scenario | Average number of users per cell | Worst case capacity [%] with 5% outage target | +|-------------------------------|----------------------------------|-----------------------------------------------| +| Single Macro layer | 60.6 | 100 | +| Macro – Macro (43dBm – 43dBm) | 58.4 | 96.4 | +| Macro – Micro (43dBm – 33dBm) | 58.4 | 96.4 | +| Macro – Macro (43dBm – 47dBm) | 56.8 | 93.7 | +| Macro – Micro (43dBm – 37dBm) | 57.1 | 94.2 | + +#### A.3.1.3 Proposal + +The statistical approach based on agreed scenarios for defining the micro BS class output power shows that the outage for macro layer UE:s will not significantly increase, in comparison to a realistic macro-macro cell layout, due to the presence of a micro layer transmitting up to 37 dBm. Based on the micro-macro layer scenario a capacity larger than 94.2% of the capacity of a single macro layer could be expected. This indicates that when defining the maximum output power for micro BS class, levels up to 37 dBm of micro output power is acceptable. + +Based on the above investigation, the proposed maximum output power, which is recommended for the Medium range BS, is +37dBm. + +### A.3.2 Simulation results #2 + +#### A.3.2.1 Simulation scenario + +This contribution provides simulation results based on the agreed scenario in TR25.942 in order to define a suitable maximum output power for the MR BS class. + +The criteria for MR BS output power is defined so as not to cause undue outage for an uncoordinated macro network UE:s. + +#### A.3.2.2 Simulation results + +In here the philosophy for establishing a maximum output power requirement for the MR BS class is to set this value as high as possible in order to maximise the coverage per MR BS site (economic reasons), but yet low enough, as not to cause noticeable outage on the DL of any surrounding uncoordinated macro network. + +Before studying the DL interference impact from the MR network onto the macro network, it is appropriate to investigate the DL operating point of the MR layer. This includes the following items: + +- DL capacity as function of MR Tx power +- relationship between UL and DL outage +- issue of possible code-blocking + +Figure A21 shows the 12.2 kbps speech service outage on UL and DL for a MR layer with 33 dBm TX power. It can be clearly seen that 33 dBm TX power is in this scenario excessive in order to match the UL capacity of approximately 95 users @ 5 % outage. This is primarily due to the assumed high orthogonality of 94 % which effectively reduces interference on the DL. + +![Figure A.21: Micro layer UL and DL outage. A line graph showing Outage % (Y-axis, 0 to 60) versus Number of UEs / site (X-axis, 97 to 167). The UL Outage % (magenta line with squares) increases sharply from approximately 7% at 97 UEs to 50% at 167 UEs. The DL Outage % (blue line with diamonds) increases much more slowly, reaching approximately 11% at 167 UEs.](47b554ac4587106dd53a7ba24cbadd40_img.jpg) + +| Number of UEs / site | DL Outage % | UL Outage % | +|----------------------|-------------|-------------| +| 97 | 0 | 7 | +| 111 | 1 | 20 | +| 125 | 2 | 31 | +| 139 | 4 | 39 | +| 153 | 8 | 45 | +| 167 | 11 | 50 | + +Figure A.21: Micro layer UL and DL outage. A line graph showing Outage % (Y-axis, 0 to 60) versus Number of UEs / site (X-axis, 97 to 167). The UL Outage % (magenta line with squares) increases sharply from approximately 7% at 97 UEs to 50% at 167 UEs. The DL Outage % (blue line with diamonds) increases much more slowly, reaching approximately 11% at 167 UEs. + +Figure A.21 Outage for MR layer with 33 dBm TX power + +It should be also noted that the theoretical capacity of approximately 140 speech users (Assuming VA factor = 1 according to TR 25.942) @ 5 % DL outage cannot be realized as this is in excess of the code capacity limit, in particular, when considering realistic voice activity factors. A similar investigation for the 144 kbps data service exhibits an even larger (primarily because of the DL Eb/No assumptions in TR 25.942 of voice vs data) DL/UL capacity asymmetry with DL throughput of approximately 4.4 Mbps / site and leads hence to the same conclusion. Therefore a naïve application of the DL load criteria (Specified for macro/macro multi-operator DL simulations. Both networks should be loaded up to 5 % outage ) according to TR25.942 leads obviously to a nonsensical scenario and hence, we assume the DL load is matched to the carried UL traffic. + +From Figure A21 we can now estimate that $33 \text{ dBm} - 10 \cdot \text{LOG}(140/95) = 31.3 \text{ dBm} \approx 31 \text{ dBm}$ TX power would have been already sufficient for 95 % DL coverage for the MR layer. + +An important conclusion from these considerations is that this scenario will allow us only to derive *an upper bound* of the DL capacity loss for the macro network for a MR network *with TX powers > 31 dBm*. + +In other words, the considered micro cell propagation environment is too “small” (in the PL sense) to justify MR BS with $> 31 \text{ dBm}$ Tx power. The primary reason for this is that in an obvious deviation from the real-life situation, the in-building penetration losses are not considered, neither are users distributed into the building blocks. + +Due to this bias towards too low PLs inherent, care needs now to be exercised when deriving requirements for the maximum TX powers of the MR layer from this scenario. + +Now we study the DL interference impact from the MR network onto the macro network. Parameters are as in TR25.942 with exception of the DL dedicated channel powers which are according to the limits of 25.104. + +In line with the considerations of the previous Section, Figure A22 shows the upper bound of macro layer DL outage due to MR layer with 33, 36 and 39 dBm TX power respectively. When compared to the required DL power for coverage, there is an excess of MR BS Tx power of 2, 5 and 8 dB respectively which will correspondingly overestimate the interference impact from the MR layer towards the macro layer. + +![Figure A.22: Upper bound for macro DL Outage. A line graph showing the upper bound for DL Outage (%) versus the Number of Macro UEs / site. The x-axis ranges from 33 to 67 Macro UEs / site. The y-axis ranges from 0 to 8% DL Outage. Four data series are plotted: Reference case (blue diamonds), 33 dBm Micro (magenta squares), 36 dBm Micro (yellow triangles), and 39 dBm Micro (cyan crosses). All series show a sharp increase in DL Outage as the number of Macro UEs increases, with the 39 dBm Micro series reaching the highest outage of approximately 7.3% at 67 Macro UEs / site.](d0e5691e25988dbacc6a4568af87574b_img.jpg) + +| Number of Macro UEs / site | Reference case (%) | 33 dBm Micro (%) | 36 dBm Micro (%) | 39 dBm Micro (%) | +|----------------------------|--------------------|------------------|------------------|------------------| +| 33 | 0.1 | 0.1 | 0.1 | 0.1 | +| 42 | 0.1 | 0.1 | 0.1 | 0.1 | +| 50 | 0.1 | 0.1 | 0.1 | 0.1 | +| 58 | 0.4 | 1.2 | 1.6 | 2.4 | +| 67 | 5.0 | 6.0 | 6.3 | 7.3 | + +Figure A.22: Upper bound for macro DL Outage. A line graph showing the upper bound for DL Outage (%) versus the Number of Macro UEs / site. The x-axis ranges from 33 to 67 Macro UEs / site. The y-axis ranges from 0 to 8% DL Outage. Four data series are plotted: Reference case (blue diamonds), 33 dBm Micro (magenta squares), 36 dBm Micro (yellow triangles), and 39 dBm Micro (cyan crosses). All series show a sharp increase in DL Outage as the number of Macro UEs increases, with the 39 dBm Micro series reaching the highest outage of approximately 7.3% at 67 Macro UEs / site. + +Figure A.22 Upper bound of macro layer DL Outage due to MR layer with 33, 36, 39 dBm TX power + +It can be seen from Figure A22 that the capacity loss for the macro layer will be *upper bounded* by 6.3 % for a 39 dBm MR network layer. With a propagation environment better matched to the 39 dBm TX power, i.e. micro-cells exhibiting a higher PL, the impact would have been certainly less due to the more favourable near-far PL distribution of the macro users. Without modifying this scenario in a substantial way to match the 39 dBm Tx power (e.g. by introducing in-building penetration losses), it cannot be asserted whether the capacity losses actually will be of that size or smaller. + +#### A.3.2.3 Proposal + +Based on the current micro-macro scenario of TR25.942 it can be concluded that the capacity loss for the macro layer will be at most 6.3 % for a 39 dBm MR network layer, however, that assumes that the MR layer has been operated with 8 dB more TX power than required, i.e. overestimating the interference impact. + +With these considerations in mind, the proposed maximum output power, which is recommended for the Medium range BS, is +39 dBm. + +## --- A.4 Maximum output power for Local area BS class + +### A.4.1 Simulation results #1 + +#### A.4.1.1 Simulation scenario + +This contribution provides simulation results based on the agreed baseline scenario in TR 25.951 in order to define a suitable maximum output power for the LA BS class. Necessary simulation parameters not already specified in TR 25.951 or TR 25.942 have been defined and are listed in Annex X. + +The criteria for LA BS output power is defined so as not to cause undue outage for an uncoordinated micro network UE:s. + +#### A.4.1.2 Simulation results + +In here the philosophy for establishing a maximum output power requirement for the LA BS class is to set this value as high as possible in order to maximise the coverage per LA BS site (economic reasons), but yet low enough not to cause noticeable outage on the DL of any surrounding uncoordinated micro network. + +All following simulation results are based on the agreed baseline scenario of TR 25.951 see Figure A12. + +The simulations were performed with all micro users located outdoors and 10 % of the micro users located indoors. + +As the BS coordinates for the locations of the LA BSs have not been fully specified in TR 25.951, these have been taken from earlier simulations instead and are marked by the '+' in Figure A12. + +There certainly exists a strong relationship between the number of LA BSs required for providing indoor coverage and their respective TX powers, hence this trade-off is investigated first. + +The indoor propagation loss (PL) according to $L = 37 + 20 \text{ Log}10I + \sum k_{wi} L_{wi}$ as defined in TR 25.951 will lead to values $< 100$ dB. This is relatively low PL when comparing to e.g. propagation in multi-floor buildings. It will make e.g. no sense at all for the LA operator to deploy 10 LA BSs à 20 dBm as can be seen immediately from the resulting excessively high DL signal levels within the building. + +Figure A23 shows the 12.2 kbps speech service outage on UL and DL for one LA BS situated at one of the center '+' in Figure A12 with 20 dBm TX power. It can be clearly be seen that even for a single LA BS, 20 dBm is in this scenario an excessive Tx power to match the UL capacity of approximately 110 users @ 5 % outage. This is primarily due to the assumed orthogonality of 94 % (according to TR 25.942). + +![Line graph titled 'Outage for LA BS' showing UL and DL outage percentages versus the number of speech users. The x-axis ranges from 50 to 700 speech users, and the y-axis ranges from 0% to 100% outage. The UL outage (blue line with diamonds) increases sharply from 0% at 100 users to approximately 85% at 700 users. The DL outage (pink line with squares) remains near 0% until about 400 users, then increases to approximately 20% at 700 users.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +| speech users | UL outage (%) | DL outage (%) | +|--------------|---------------|---------------| +| 50 | 0 | 0 | +| 100 | 0 | 0 | +| 200 | 35 | 0 | +| 300 | 60 | 0 | +| 400 | 70 | 2 | +| 500 | 78 | 5 | +| 700 | 85 | 20 | + +Line graph titled 'Outage for LA BS' showing UL and DL outage percentages versus the number of speech users. The x-axis ranges from 50 to 700 speech users, and the y-axis ranges from 0% to 100% outage. The UL outage (blue line with diamonds) increases sharply from 0% at 100 users to approximately 85% at 700 users. The DL outage (pink line with squares) remains near 0% until about 400 users, then increases to approximately 20% at 700 users. + +**Figure A.23 Outage for 1 LA BS with 20 dBm TX power** + +It should be also noted that the theoretical capacity of approximately 500 speech users @ 5 % DL outage cannot be realized as this is far in excess of the code capacity limit. A similar investigation for the 144 kbps data service leads to the very same conclusion. Therefore a naïve application of the DL load criteria according to TR 25.942 (Specified for macro/micro multi-operator DL simulations. Both networks should be loaded up to 5 % outage) leads obviously to a nonsensical scenario and hence in here, we assume the DL load is matched to the carried UL traffic. + +From Figure A23 we can now estimate that $20 \text{ dBm} - 10 \cdot \text{LOG}(500/110) = 13.4 \text{ dBm} \approx 14 \text{ dBm}$ TX power would have been already sufficient for 95 % DL coverage by a single BS. Using more than 1 LA BS will lead to even lower required TX powers and is therefore not considered further in the following results. + +An important conclusion from these considerations is that this scenario will allow us only to derive an upper bound of the DL capacity loss for the micro network for LA BS with TX powers > 14 dBm. + +In line with the considerations of the previous section, Figure A24 shows the upper bound of micro layer DL outage due to 1 LA BS with 20, 24 and 30 dBm TX power respectively. Hence, when compared to the required DL power for coverage, there is an excess of LA BS Tx power of 6, 10 and 16 dB respectively, which correspondingly overestimates the interference impact from the LA layer towards the micro layer. + +![Figure A.24: A line graph titled '1 Pico BS, Micro DL Outages (upper bound)'. The y-axis is 'upper bound of DL Outage %' ranging from 0 to 25. The x-axis is 'Number of speech Micro UEs' ranging from 2100 down to 1100. Four curves are shown: 20 dBm Pico (blue diamonds), 24 dBm Pico (magenta squares), 30 dBm Pico (yellow triangles), and Reference (No Pico) (cyan crosses). The 30 dBm Pico curve shows the highest outage percentage, starting at ~20% at 2100 UEs and dropping to ~4% at 1100 UEs. The 24 dBm Pico curve starts at ~11% and drops to ~1%. The 20 dBm Pico curve starts at ~8% and drops to ~0.5%. The Reference curve starts at ~6% and drops to ~0.5%.](6752cee124f693bc4cebc66180f4f91f_img.jpg) + +| Number of speech Micro UEs | 20 dBm Pico (%) | 24 dBm Pico (%) | 30 dBm Pico (%) | Reference (No Pico) (%) | +|----------------------------|-----------------|-----------------|-----------------|-------------------------| +| 2100 | 8 | 11 | 20 | 6 | +| 1900 | 5 | 8 | 16 | 4 | +| 1700 | 3 | 5 | 12 | 2 | +| 1500 | 2 | 3 | 9 | 1 | +| 1300 | 1 | 1 | 6 | 0.5 | +| 1100 | 0.5 | 0.5 | 4 | 0.5 | + +Figure A.24: A line graph titled '1 Pico BS, Micro DL Outages (upper bound)'. The y-axis is 'upper bound of DL Outage %' ranging from 0 to 25. The x-axis is 'Number of speech Micro UEs' ranging from 2100 down to 1100. Four curves are shown: 20 dBm Pico (blue diamonds), 24 dBm Pico (magenta squares), 30 dBm Pico (yellow triangles), and Reference (No Pico) (cyan crosses). The 30 dBm Pico curve shows the highest outage percentage, starting at ~20% at 2100 UEs and dropping to ~4% at 1100 UEs. The 24 dBm Pico curve starts at ~11% and drops to ~1%. The 20 dBm Pico curve starts at ~8% and drops to ~0.5%. The Reference curve starts at ~6% and drops to ~0.5%. + +**Figure A.24** Upper bound of micro layer DL Outage due to 1 LA BS with 20, 24, 30 dBm TX power + +Figure A.24 would at a first glance suggest that there would be a significant ( $> 5\%$ ) impact from a LA network layer with $> 20$ dBm Tx power onto the surrounding micro network. However, also for the micro network we have to consider a reasonable DL operating point. E.g., the $5\%$ DL outage point for the “30 dBm pico” curve at 1300 users total or, equivalently, 108 speech users (with VA = 1) /site cannot be realized for realistic VA factors as this is far in excess of the code capacity limit. The same conclusion holds for data services, here the code capacity limit will be exceeded even sooner due to the much lower Eb/No requirement according to TR 25.942. + +#### A.4.1.3 Proposal + +The conclusion is that even for a 30 dBm LA network layer, interference caused capacity losses in the micro layer could only occur for loads which are unrealisable from the code capacity limit point of view. + +In other words, for the given scenario here, the interference impact is purely hypothetical if realistic DL operating points are considered. + +On the other hand, as these results have been established for a specific scenario only, some extra protection for the micro layer is desirable; we propose an additional 3 dB safety margin. Hence, the proposed maximum output power, which is recommended for the Local area BS, is +27 dBm. + +A value of +27 dBm appears also appropriate from the perspective of balancing the UL with the DL: relative to a general purpose BS, the LA BS will be desensitised by 14 dB. On the other hand, 27 dBm Tx power is 16 dB below the typical value of 43 dBm for a WA BS, hence UL and DL will remain balanced. + +### A.4.2 Simulation results #2 + +#### A.4.2.1 Simulation scenario + +In this section, a statistical approach on the maximum output power is shown, which is based on TR 25.942 and TR 25.951, and the maximum output power for the Local area BS is proposed. In the simulation, the deployment of Micro BS and Pico BS shown in Figure A.12 is used. Parameters related to propagation models are summarized in Table A.6. The criteria for Local area BS output power is defined as the capacity deterioration for an uncoordinated Micro network UEs. + +**Table A.6: Parameters related to propagation models** + +| Parameter | Local area BS | Medium range BS | | +|-------------------------|---------------------------|----------------------------------------|--------------------------------------| +| | | Indoor | Outdoor | +| Propagation Model | Indoor model of UMTS30.03 | Indoor model of UMTS30.03 | Microcell propagation model [25.942] | +| Outside wall loss | 10dB | 10 dB | N/A | +| Slow fading deviation | 6dB [25.942] | | | +| MCL | 45 dB [25.951] | 53 dB [25.951] | | +| ACS | 33 dB | | | +| ACLR | 45 dB (5MHz offset) | | | +| Output power | 0 ... 31dBm | 33 dBm | | +| Deployment of BS | Max.10 / floor | 12 BS (wrap around)
Manhattan model | | +| Building size | 110 x 110 meters | | | +| Number of floors | 1 / building | | | +| Number of rooms | 20 / floor | | | +| In building users ratio | 0.02 ... 0.1 | | | + +The number of Local area BSs can be decreased as the maximum output power of Local area BSs increases. The minimum number of the Local area BSs that supports the received power at UE higher than -90dBm in more than 95% area out of the entire floor is shown in Table A.7. + +**Table A.7: Number of Local area BS** + +| Maximum output power of Local area BS | 0 dBm | 5 dBm | 10 dBm | 20 dBm | 31 dBm | +|---------------------------------------|-------|-------|--------|--------|--------| +| Number of Local area BS | 10 | 4 | 3 | 2 | 2 | + +#### A.4.2.2 Simulation results + +The simulation results on capacity deterioration for uncoordinated Micro and Pico networks are shown in Figure A25. + +In the simulations, the number of Local area BSs shown in Table A.7 was used. As the reference, capacity deterioration in the case of Macro-Macro and Micro-Macro, calculated for Medium range BS class are also shown in Figure A25. + +From Figure A25, the capacity deterioration for the Micro area network increases as Local area BS output power increases. As is shown in the figure, the output power of Local area BS should be less than +20dBm in order to maintain the capacity deterioration less than 5% when 10% of micro network UEs are in the building. + +![Line graph titled 'CAPACITY DETERIORATION' showing capacity deterioration vs maximum output power of Local Area BS [dBm] for various network configurations.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +The graph shows the relationship between the maximum output power of a Local Area BS (in dBm) and the resulting capacity deterioration. The x-axis ranges from 0 to 35 dBm, and the y-axis ranges from 0 to 0.1. Six data series are plotted: Macro-Macro [6] (dashed line), Micro-Macro [6] (solid line with triangle markers), Pico-Micro In\_building users ratio= 0.02 (dash-dot line), Pico-Micro In\_building users ratio= 0.05 (dash-dot-dot line), Pico-Micro In\_building users ratio= 0.10 (solid line), and Pico-Micro In\_building users ratio= 0.15 (dotted line). The capacity deterioration generally increases with the maximum output power of the Local Area BS. The Pico-Micro In\_building users ratio= 0.15 series shows the highest capacity deterioration, reaching approximately 0.09 at 30 dBm. The Pico-Micro In\_building users ratio= 0.02 series shows the lowest capacity deterioration, remaining relatively flat around 0.01. The Micro-Macro [6] series shows a sharp increase in capacity deterioration starting around 25 dBm, reaching approximately 0.04 at 30 dBm. + +| Maximum output power of Local Area BS [dBm] | Macro-Macro [6] | Micro-Macro [6] | Pico-Micro In_building users ratio= 0.02 | Pico-Micro In_building users ratio= 0.05 | Pico-Micro In_building users ratio= 0.10 | Pico-Micro In_building users ratio= 0.15 | +|---------------------------------------------|-----------------|-----------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------| +| 0 | 0.04 | 0.04 | 0.01 | 0.02 | 0.04 | 0.06 | +| 5 | 0.04 | 0.04 | 0.01 | 0.02 | 0.04 | 0.06 | +| 10 | 0.04 | 0.04 | 0.01 | 0.02 | 0.04 | 0.06 | +| 15 | 0.04 | 0.04 | 0.01 | 0.02 | 0.04 | 0.07 | +| 20 | 0.04 | 0.04 | 0.01 | 0.02 | 0.05 | 0.08 | +| 25 | 0.04 | 0.04 | 0.01 | 0.02 | 0.05 | 0.08 | +| 30 | 0.04 | 0.04 | 0.01 | 0.02 | 0.06 | 0.09 | +| 35 | 0.04 | 0.04 | 0.01 | 0.02 | 0.06 | 0.09 | + +Line graph titled 'CAPACITY DETERIORATION' showing capacity deterioration vs maximum output power of Local Area BS [dBm] for various network configurations. + +Figure A.25: Capacity deterioration + +#### A.4.2.3 Proposal + +Based on the above simulations, the proposed maximum output power for Local area BSs is +20dBm. The proposed value is identical to the earlier results presented in document R4-021635 where the interference between macro and pico cells were considered. + +# Annex B (informative): Radio Network Planning Considerations + +## B.1 Adjacent frequency Interference + +### B.1.1 General + +The RF specification for Base Stations is to a large extent based on statistical averaging of interference effects. This should normally be sufficient to eliminate significant interference effects on adjacent frequency networks, if some simple rules (e.g. 30 dB MCL between Wide Area BS) are followed. + +Especially in the case of Local Area and Medium Range BS, also considering some of their likely deployment environments (indoor, street canyons) there is however a higher probability that the interference on adjacent frequencies is localised. In these cases some co-ordination between operators may be required. + +This informative Annex considers Radio Network Planning (RNP) measures, which can be applied in case there is significant interference between adjacent radio networks of different hierarchy level, e.g. between a MR and a WA network. In the following mainly aspects related to DL adjacent channel interference will be considered. + +### B.1.2 Example analysis for localized interference + +Based on a number of assumptions on deployment of networks, the relevant parameter for the impact of DL adjacent channel interference caused by a MR or LA Node B is the maximum output power. From the Monte-Carlo simulation results contained in Annex A it can be seen that the DL capacity loss for an adjacent macro layer is upper-bounded by approximately no more than 6 % for a 38 dBm MR network layer. Similarly, it was shown that the DL capacity impact from a 24 dBm LA network on an adjacent MR network is of similar order. + +While the average impact is thus small, there is nevertheless a chance that a macro layer UE gets localised interference by a MR or LA Node B under low coupling loss (CL) and weak serving signal conditions. This will be illustrated by the following example analysis for the case of a LA (indoor) cell interfering to an adjacent macro cell. + +The following parameters will be assumed: + +**Table B.1: Assumed parameters for the localized interference analysis** + +| Parameter | Value | Unit | Notes | +|------------------------------------|-------|------|--------------| +| UE ACS | 33 | dB | from 25.101 | +| interfering LA BS maximum Tx power | 24 | dBm | from this TR | +| interfering LA BS antenna gain | 0 | dBi | from this TR | +| serving cell received DTCH level | -90 | dBm | | +| bit rate | 12.2 | kbps | | +| Eb/Io | 7 | dB | | + +With these service parameters we obtain for the required Ec/Io: + +$$\text{Required Ec/Io} = -25 \text{ dB [processing gain]} + 7 \text{ dB [Eb/Io]} = -18 \text{ dB}$$ + +The area of the localized interference around the LA BS can be estimated as follows (In this calculation the own system (cell) interference is not taken into account, i.e. it is assumed that ACI dominates): + +- 1) Maximum tolerated interference level on the own channel: $-90 \text{ dBm} + 18 \text{ dB [Required Ec/Io]} = -72 \text{ dBm}$ +- 2) Maximum tolerated interference level on the adjacent channel: $-72 \text{ dBm} + 33 \text{ dB [UE ACS]} = -39 \text{ dBm}$ +- 3) Required coupling loss CL towards interfering LA BS: $+24 \text{ dBm} - (-39 \text{ dBm}) = 63 \text{ dB}$ +- 4) Assuming the indoor path loss model from this TR for the case that internal walls are not modelled individually and a single floor, the indoor path loss model is represented by the following formula: + +$$\text{PL} = 37 + 30 \text{ Log10I},$$ + +with $R$ the UE – LA BS separation given in metres. From this, the required minimum distance towards the interfering LA BS is given by: + +$$R = 10^{\wedge}((63 \text{ dB [CL]} + 0 \text{ dBi [LA BS antenna gain]} - 37) / 30) = 7.36 \text{ m}$$ + +As can be seen, the required minimum distance towards the interfering LA BS depends not only on the parameters of the interfering system (i.e. TX power, antenna gain), but also on the available DTCH signal level of the serving macro cell. + +The following figure shows the size of the localized interference around the LA BS for serving cell received DTCH levels in the range of $-70 \dots -110 \text{ dBm}$ : + +![Figure B.1: A line graph showing the required minimum distance R (in meters) towards an interfering LA BS as a function of the serving cell received DTCH level (in dBm). The x-axis represents the serving cell received DTCH level from -70 to -110 dBm in 5 dBm increments. The y-axis represents the required minimum distance R in meters, ranging from 0,00 to 40,00 m in 5,00 m increments. The data points, marked with blue diamonds, show an exponential-like increase in distance as the signal level decreases. The legend indicates the line represents the 'required minimum distance R towards interfering LA BS'.](dfb7b1135e92a91d2c81546f16a50947_img.jpg) + +| Serving cell received DTCH level [dBm] | required minimum distance R towards interfering LA BS [m] | +|----------------------------------------|-----------------------------------------------------------| +| -70 | ~1,5 | +| -75 | ~2,5 | +| -80 | ~4,0 | +| -85 | ~6,5 | +| -90 | ~10,5 | +| -95 | ~17,0 | +| -100 | ~27,5 | +| -105 | ~44,5 | +| -110 | ~72,0 | + +Figure B.1: A line graph showing the required minimum distance R (in meters) towards an interfering LA BS as a function of the serving cell received DTCH level (in dBm). The x-axis represents the serving cell received DTCH level from -70 to -110 dBm in 5 dBm increments. The y-axis represents the required minimum distance R in meters, ranging from 0,00 to 40,00 m in 5,00 m increments. The data points, marked with blue diamonds, show an exponential-like increase in distance as the signal level decreases. The legend indicates the line represents the 'required minimum distance R towards interfering LA BS'. + +**Figure B.1: Localized interference around the LA BS as function of serving cell received DTCH levels** + +In order to further reduce the likelihood of such localized interference events, the measures presented in the following clause may be applied. + +### B.1.3 Deployment guidelines to reduce interference + +The following measures are applicable by the operator of the interfering radio network (i.e. LA or MR network) in order to reduce the likelihood of interference towards an adjacent band operator: + +- Avoid allocating LA, MR Node B carriers at the assigned band edge(s) to another operator whenever possible. This may be possible e.g. at an early UMTS deployment phase, where only part of the assigned band may be required. +- During a later UMTS deployment phase, for the case that an operator wishes to deploy 2 WA carriers and one MR or LA carrier, the latter carrier could be “sandwiched” by the WA carriers. +- Ensure sufficiently large MCL conditions across the planned micro cell (or in-building) coverage area. This can be facilitated by choosing suitable antenna types, heights and locations. Note that obtaining a sufficiently high MCL (including antenna gains) is also desirable for the MR or LA network operator due to the $-25 \text{ dBm}/3.84 \text{ MHz}$ maximum input level requirement of the UE [25.101]; hence, the MCL will also depend on the intended maximum Node B TX power setting. +- Match the setting of the maximum Node B TX power for MR or LA operation to the requirements (i.e. CL) of propagation environment at hand, i.e. avoid using substantially more TX power than is required for the micro cell or in-building coverage. DL power planning can be facilitated by adjusting the CPICH TX power in such a way that the received CPICH RSCP (or $E_c/I_o$ ) across the desired coverage area meets the outage target, but on the other hand, is not unnecessarily high. Scaling the windows of the DTCH DL power allocations accordingly, will then also lead to appropriate DTCH power levels. + +- Co-ordination between adjacent frequency operators of output powers, antenna sites, heights, gains and patterns, or even co-location of interfering sites. This would reduce worst case situations where a strong interfering signal is received by an adjacent frequency UE connected to a BS at large coupling loss, and thus under relatively poor radio conditions. + +For temporary effects, and remaining problems a number of additional system functionalities can be used: + +- In case that multiple WA carriers may have become available, the use of IFHO for DL interference avoidance may be used. Hence, the UE may be handed over to the 2nd or 3rd adjacent channel, which will reduce or eliminate the interference. +- In case that adjacent channel interference is encountered within a WA cell, proper setting of the DTCH TX power window can provide the UE with additional power to combat interference. Hence, there is possibility for trading off some capacity / throughput for reducing possible DL coverage holes. +- In case that adjacent channel interference is encountered within a WA cell, reduction of the allocated peak data rate (or AMR codec rate) can provide the UE with additional power to combat interference. Hence, there is possibility for trading off peak data rates for reducing possible DL coverage holes. +- For areas where the received Node B DL signals (or representatively the CPICH RSCP's) from the own and adjacent interfering system differ by much more than 40 dB, own system signal strength may be increased by RNP methods. This can be done by means of directing / tilting antennas beams towards the building in question (e.g. in case of interfering LA network) or by building additional sites. + +## B.2 Intra-frequency interference + +### B.2.1 General + +The RF specification for Base Stations is to a large extent based on statistical averaging of interference effects and on specific MCL requirement. This should normally be sufficient to eliminate significant interference. + +In the case of Local Area and Medium Range BS, also considering some of their likely deployment environments (indoor, street canyons) there is however a high probability that the current UE and BS specifications lead to localised significant intra-frequency interference and then to localised coverage and capacity holes. + +This informative Annex highlights through an example the impacts of UE performance requirements on the range of coupling loss that can be operated without degraded the network performance. + +### B.2.2 Example analysis for localized interference + +In this paragraph, the impact of the MCL requirement on UE and BS (either LA or MR) sensitivity is analysed. + +#### B.2.2.1 UL issue + +Regarding the UL, a LA or MR BS can be desensitised and suffer from UL capacity/coverage loss if the CL at which the power control causes the UE output power to reduce to the minimum output power is significantly higher than the MCL. In such conditions, if the UE were to move closer to the serving BS, the power control would be unable to reduce the UE output power further, and desensitization would occur. + +Then assuming the following parameters (Table B.2) the MCL requirement is compared to the CL value from where a UE reaches its minimum output power. + +**Table B.2: Assumed parameters for the UL analysis** + +| Parameter | UE Value | LA BS Value | MR BS value | Unit | Notes | +|------------------------------------------------------|----------|-------------|-------------|------|--------------| +| UE minimum output power | -50 | | | dBm | from 25.101 | +| BS reference sensitivity level (12.2kbps, BER<0.001) | | -107 | -111 | dBm | from this TR | +| MCL | | 45 | 53 | dB | from this TR | + +The parameters listed in Table B.2 shows that a UE using speech service and served by a LA BS reaches its minimum output power when the coupling loss is such as: + +$$-50 \text{ [UE min output power]} - \text{CL [coupling loss between UE and serving BS]} =$$ + +$$-107 \text{ [LA BS reference sensitivity level]} + \text{NR [noise rise of the cell corresponding to its load]}$$ + +That is to say: CL=57dB for an unloaded cell and 51dB for a 75% loaded cell (NR=6dB) while the minimum coupling loss of a LA BS is 45dB. + +The parameters listed in Table B.2 shows that a UE using speech service and served by a MR BS reaches its minimum output power when the coupling loss is such as: + +$$-50 \text{ [UE min output power]} - \text{CL [coupling loss between UE and serving BS]} =$$ + +$$-111 \text{ [LA BS reference sensitivity level]} + \text{NR [noise rise of the cell corresponding to its load]}$$ + +That is to say: CL=61dB for an unloaded cell and 55dB for a 75% loaded cell (NR=6dB) while the minimum coupling loss of a MR BS is 53dB. + +All these evaluated coupling losses are significantly higher than the MCL requirement of the corresponding BS classes. As a result a severe BS desensitisation is expected if a UE is very close to its serving BS. + +#### B.2.2.2 DL issue + +Regarding the DL, a LA or MR BS may degrade its own UE's performances and face then DL capacity/coverage loss if the UE received input power level is higher than the maximum requirement. + +Then assuming the following parameters (Table B.3) the MCL requirement is compared to the CL value from where a UE received its maximum input power. + +**Table B.3: Assumed parameters for the DL analysis** + +| Parameter | UE Value | LA BS Value | MR BS value | Unit | Notes | +|-------------------------|----------|-------------|-------------|------|--------------| +| UE maximum input level | -25 | | | dBm | from 25.101 | +| BS maximum output power | | 24 | 38 | dBm | from this TR | +| MCL | | 45 | 53 | dB | from this TR | + +The parameters listed in Table B.3 show that the maximum received input level of a UE is reached by a serving LA BS transmitting its maximum output power when the coupling loss is such as: + +$$24 \text{ [BS maximum output power]} - \text{CL [coupling loss between UE and serving BS]} = -25 \text{ [UE maximum input level]}$$ + +That is to say: CL=49dB while the minimum coupling loss is 45dB. + +The parameters listed in Table B.3 show that the maximum received input level of a UE is reached by a serving MR BS transmitting its maximum output power when the coupling loss is such as: + +$$38 \text{ [BS maximum output power]} - \text{CL [coupling loss between UE and serving BS]} = -25 \text{ [UE maximum input level]}$$ + +That is to say: CL=63dB while the minimum coupling loss is 53dB. + +Both these evaluated coupling losses are significantly higher than the MCL requirement of the corresponding BS classes. As a result a UE performances may be degraded by its serving BS. + +### B.2.3 Deployment guidelines to reduce interference + +The following measures may be applied by an operator deploying a LA or a MR network in order to reduce the likelihood of localized interference inside its own network: + +- Ensure sufficiently large MCL conditions across the planned micro cell or in-building coverage area. This can be facilitated by choosing suitable antenna types, heights and locations. + +- Match the setting of the maximum Node B TX power for MR or LA operation to the requirements (i.e. CL) of propagation environment at hand, i.e. avoid using substantially more TX power than is required for the micro cell or in-building coverage. DL power planning can be facilitated by adjusting the CPICH TX power in such a way that the received CPICH RSCP (or Ec/Io) across the desired coverage area meets the outage target, but on the other hand, is not unnecessarily high. Scaling the windows of the DTCH DL power allocations accordingly, will then also lead to appropriate DTCH power levels. +- Implement efficient handover algorithms to escape low coupling loss situation. + +# Annex C (informative): Change History + +**Table C.1: Change History** + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|------------|------------|-----------|----------|--------------------------------|------------|-------------|------------|------------------| +| RP-36 | | | | Rel-6 version created. | | 6.3.0 | 7.0.0 | | +| SP-42 | | | | Upgraded unchanged from Rel-7 | | | 8.0.0 | | +| SP-46 | | | | Upgraded unchanged from Rel-8 | | | 9.0.0 | | +| SP-51 | | | | Upgraded unchanged from Rel-9 | | 9.0.0 | 10.0.0 | | +| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.0.0 | 11.0.0 | - | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.0.0 | 12.0.0 | | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.0.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | - | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------|--|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-09 | RAN#81 | | | | | Update to Rel-15 version (MCC) | | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25956/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-16/25_series/25956/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18637ef9b3c0bfeae0a689c3cf33b9267ca10223 --- /dev/null +++ b/marked/Rel-16/25_series/25956/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f65d5116560bc9c4491d186039b4b93455934210e260c99df6980a04fa739e88 +size 16017 diff --git a/marked/Rel-16/25_series/25956/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-16/25_series/25956/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c55693a114573a672ad98b9fc0c25d8e8eb141 --- /dev/null +++ b/marked/Rel-16/25_series/25956/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10e28a21ae7ffaaec53426bd5cfeb157f61857f9826f88183e538d14b699b601 +size 69583 diff --git a/marked/Rel-16/25_series/25956/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-16/25_series/25956/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48affd9e67c7c13084f1f47f131271c412447263 --- /dev/null +++ b/marked/Rel-16/25_series/25956/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2043c48536239b29a2e4cd9a9907609809abc066ac956a66c975ef965bc4aa9a +size 52673 diff --git a/marked/Rel-16/25_series/25956/0aa15f5c9c3edae230985491199cfe8b_img.jpg b/marked/Rel-16/25_series/25956/0aa15f5c9c3edae230985491199cfe8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e27887b8271c9e4e57540d8fcfb2c83671b72b3 --- /dev/null +++ b/marked/Rel-16/25_series/25956/0aa15f5c9c3edae230985491199cfe8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2de6903001db1f5738f4a423c5c5e12fa5202f9bfe342af3e3cf6e2f4d11fdc9 +size 50504 diff --git a/marked/Rel-16/25_series/25956/0d5fdb87a392819c7d2e3b6230912a0b_img.jpg b/marked/Rel-16/25_series/25956/0d5fdb87a392819c7d2e3b6230912a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..097661f1f41ad508d1de6ea0a45acb5e21ff925b --- /dev/null +++ b/marked/Rel-16/25_series/25956/0d5fdb87a392819c7d2e3b6230912a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53b2099746b4da13156fde7326234b9d21e3262e1a278d9195a86e1a59a017c4 +size 33201 diff --git a/marked/Rel-16/25_series/25956/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-16/25_series/25956/198d076da025c516aec8122a6ab7db20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d02813d8214b076acd309e21508a582d1ca8e7d3 --- /dev/null +++ b/marked/Rel-16/25_series/25956/198d076da025c516aec8122a6ab7db20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c605b20f845d3573c0982d2e64e7c739e7e4523aac0ba0c402e2add49354f8b7 +size 50555 diff --git a/marked/Rel-16/25_series/25956/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-16/25_series/25956/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f63b824c9645318bc827022767bbc93cc4d7e93 --- /dev/null +++ b/marked/Rel-16/25_series/25956/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623a3d1258ce4f28f886e2f821acf6ce720eedfb92eb00cbe0586386136836e1 +size 51493 diff --git a/marked/Rel-16/25_series/25956/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-16/25_series/25956/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0812b829ce37ad9019d4ea32d6d7cd366bf2f1c --- /dev/null +++ b/marked/Rel-16/25_series/25956/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98aeb87668738a9456be9d030f0d192728d305ee7cc3b957f1e6f5031b3815b4 +size 51296 diff --git a/marked/Rel-16/25_series/25956/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-16/25_series/25956/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4a8bb50818613c72ea991bd936386dd0de87879 --- /dev/null +++ b/marked/Rel-16/25_series/25956/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c8aff2ee440d8cd56a589ba946cea4ae67ebe313be6f6ebb54d4f8c096659c8 +size 51451 diff --git a/marked/Rel-16/25_series/25956/34f735bc749df18394ac93f5b84857b7_img.jpg b/marked/Rel-16/25_series/25956/34f735bc749df18394ac93f5b84857b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cda3d5bc12faf9724d794ec8c12b2b5d7911af8 --- /dev/null +++ b/marked/Rel-16/25_series/25956/34f735bc749df18394ac93f5b84857b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:858dfa59c7b847fa7a087818689e1656147911cc22b5e9b1666bd1467c380d23 +size 49153 diff --git a/marked/Rel-16/25_series/25956/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg b/marked/Rel-16/25_series/25956/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d1484e607d25453cefd8a98675377b5d181404e --- /dev/null +++ b/marked/Rel-16/25_series/25956/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2282aba468ff6ced4de6a40a1306ef360dc5c3a6505153e2397158fa457e91f +size 50158 diff --git a/marked/Rel-16/25_series/25956/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg b/marked/Rel-16/25_series/25956/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1a87b33623948fef0f32da91d30d724dc3060ac --- /dev/null +++ b/marked/Rel-16/25_series/25956/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1181ff72fe128ffddbd5c8df2cf9bb524f8a4e862bf19f63ba4fc1c5c3aeac9f +size 51327 diff --git a/marked/Rel-16/25_series/25956/449d2799e97657d8fa5897b2e74a88bd_img.jpg b/marked/Rel-16/25_series/25956/449d2799e97657d8fa5897b2e74a88bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b827e21a4f0465a6066890bbc0ea00c27d3d36 --- /dev/null +++ b/marked/Rel-16/25_series/25956/449d2799e97657d8fa5897b2e74a88bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19af7d663a5f6c9fdc7d853a6d1a37c5d50a9305541e410398ea4e0d9b633997 +size 50326 diff --git a/marked/Rel-16/25_series/25956/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/Rel-16/25_series/25956/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e3004bdfbe3d682cdd3ee1b67daba0b6b6ad427 --- /dev/null +++ b/marked/Rel-16/25_series/25956/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0e3278dc757d159f186ecd7290b53f3818832c69a20fafd4d1da734e06910b +size 179349 diff --git a/marked/Rel-16/25_series/25956/455c842681aadb4969bd61d71f556744_img.jpg b/marked/Rel-16/25_series/25956/455c842681aadb4969bd61d71f556744_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32be63b3d6316518e59535f04c3bc1d13207d983 --- /dev/null +++ b/marked/Rel-16/25_series/25956/455c842681aadb4969bd61d71f556744_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa11cfdd21213c2d965a0fc40e9893b9ac30d2068e4acdf92d2d1558d7ffdb13 +size 50520 diff --git a/marked/Rel-16/25_series/25956/48fc91e19c1a9b6674b120fbdd89b203_img.jpg b/marked/Rel-16/25_series/25956/48fc91e19c1a9b6674b120fbdd89b203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1311404ae83e4e2b0ef3302fba7208a9ab2474e3 --- /dev/null +++ b/marked/Rel-16/25_series/25956/48fc91e19c1a9b6674b120fbdd89b203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b743ec06f529233e0c117493f48449c8f5f0c26e63b873b40bfab9771457edf1 +size 84266 diff --git a/marked/Rel-16/25_series/25956/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-16/25_series/25956/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..868b76ab11bacf140b88c9238036eb2d95d5ed97 --- /dev/null +++ b/marked/Rel-16/25_series/25956/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbf8e26e1fc2d63851ac906230459cf8b6c34d0fa035273fa6d7e9e4001f3755 +size 30500 diff --git a/marked/Rel-16/25_series/25956/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-16/25_series/25956/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0748641c38d8465629979e7b99788c51d0fd8eea --- /dev/null +++ b/marked/Rel-16/25_series/25956/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:627e2301e610f34df2f9ea017aa44d9c521e73b5de93222d6af2de2de6f41ef4 +size 53774 diff --git a/marked/Rel-16/25_series/25956/52f284e10be4323639b32fdd60e463db_img.jpg b/marked/Rel-16/25_series/25956/52f284e10be4323639b32fdd60e463db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..049fb28b5a1a5b410321239f9c50ba2e2c4e79e8 --- /dev/null +++ b/marked/Rel-16/25_series/25956/52f284e10be4323639b32fdd60e463db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df1851bc3cb1d2c94d49b25fc367dcbfd92a45dfbb706b192d196cff10120ed3 +size 68628 diff --git a/marked/Rel-16/25_series/25956/58f42a91047786934d8a7e258d581ca2_img.jpg b/marked/Rel-16/25_series/25956/58f42a91047786934d8a7e258d581ca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19c87c2a1fa7c561106cd45c9a935d65d058d0a6 --- /dev/null +++ b/marked/Rel-16/25_series/25956/58f42a91047786934d8a7e258d581ca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08969897a79c8a07d0002bbdd89883846327f0e9b9e0a55dfcc001a6ba68b368 +size 28066 diff --git a/marked/Rel-16/25_series/25956/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25956/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa81f0639276beec444a201e6d16d3f3a54872a9 --- /dev/null +++ b/marked/Rel-16/25_series/25956/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:895ba1081c0eb043fb5e4768d2cb43909d62d08d5c348dff562fd5dd86722496 +size 41052 diff --git a/marked/Rel-16/25_series/25956/5dc5581cd2aad0e683c73b959f637b31_img.jpg b/marked/Rel-16/25_series/25956/5dc5581cd2aad0e683c73b959f637b31_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06c363051fa1f3cec8d7b80ebb39d96272fafc9a --- /dev/null +++ b/marked/Rel-16/25_series/25956/5dc5581cd2aad0e683c73b959f637b31_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1cd80e65e6744855d49b8aa4f1b836ee0b5794a25e1f23b6ecc734d29df6d76 +size 65816 diff --git a/marked/Rel-16/25_series/25956/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-16/25_series/25956/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af53633b84604c4af1ce2b1201ec1996735c2e1 --- /dev/null +++ b/marked/Rel-16/25_series/25956/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bdd63e34cd7505275258fcd272959612e2fce97c18c871b377183d8c8094e50 +size 76539 diff --git a/marked/Rel-16/25_series/25956/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg b/marked/Rel-16/25_series/25956/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bee76dd888bc5e474eefb09f1c41ccd9bd9f713 --- /dev/null +++ b/marked/Rel-16/25_series/25956/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c466fac8246cd7c0fe6bcfea9b2a727278b9f9b42d565d1f75b9f10805847c0 +size 50636 diff --git a/marked/Rel-16/25_series/25956/6752cee124f693bc4cebc66180f4f91f_img.jpg b/marked/Rel-16/25_series/25956/6752cee124f693bc4cebc66180f4f91f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d48652bae6a1237f06eac3c3a94099953b724244 --- /dev/null +++ b/marked/Rel-16/25_series/25956/6752cee124f693bc4cebc66180f4f91f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5214f186f24ec109dbe9bfde494f9d04a323608d8d66f4ccc7144c25175ba6c8 +size 167569 diff --git a/marked/Rel-16/25_series/25956/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-16/25_series/25956/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a0ecc66564b6c106390a73ab76cf52bd618c3d0 --- /dev/null +++ b/marked/Rel-16/25_series/25956/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b836cfcd90d64b0852c9e81964ac16cc0212c6d31c00a2473ff0d86de0efbde +size 44138 diff --git a/marked/Rel-16/25_series/25956/6fe536731996880570f251da168376cf_img.jpg b/marked/Rel-16/25_series/25956/6fe536731996880570f251da168376cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11dd2dc6ff01886e6499483b070d7d3307888cbe --- /dev/null +++ b/marked/Rel-16/25_series/25956/6fe536731996880570f251da168376cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c2cd1cda6ddb5b87b42c741dfc60a60e9f9f2ae2c8b179374207ea0c0d63ac9 +size 63478 diff --git a/marked/Rel-16/25_series/25956/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-16/25_series/25956/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31c7782e135a161e24f91f80b291ab184bffb5bc --- /dev/null +++ b/marked/Rel-16/25_series/25956/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:592f65b3e220b154269ec8b0d4eb00d480f11019b0aee3fd01a3863a5d767558 +size 167153 diff --git a/marked/Rel-16/25_series/25956/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-16/25_series/25956/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81ac66ce135eac2d18f1e15e8824d40e51e6fca5 --- /dev/null +++ b/marked/Rel-16/25_series/25956/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837b6055717af4e4249b521f28595b535e313e1c8ac9be7491392528ca626738 +size 22545 diff --git a/marked/Rel-16/25_series/25956/73e5c1369b67ddccf657e54d0434cc2b_img.jpg b/marked/Rel-16/25_series/25956/73e5c1369b67ddccf657e54d0434cc2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29fbba45631663825bb6bf56b83409981863e1a6 --- /dev/null +++ b/marked/Rel-16/25_series/25956/73e5c1369b67ddccf657e54d0434cc2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8040d09497c2dca7b7899f632c1e5e1596a22583b9098990ea6dad62e6c7a193 +size 53215 diff --git a/marked/Rel-16/25_series/25956/74448f9178da618d823e5a5dadc56fb5_img.jpg b/marked/Rel-16/25_series/25956/74448f9178da618d823e5a5dadc56fb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cc8330c7e165d62b802492c1b45a8cf8a75973b --- /dev/null +++ b/marked/Rel-16/25_series/25956/74448f9178da618d823e5a5dadc56fb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19274f2262425f5d6182086ffba73a6002f58c4aa3d49ed714a30d26b137a5d3 +size 53295 diff --git a/marked/Rel-16/25_series/25956/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-16/25_series/25956/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7e980aa01de1498b3537bee372ffc4810393f79 --- /dev/null +++ b/marked/Rel-16/25_series/25956/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0405f47e8d1bd19047dedebb4d5c014bbc7ab7d9a4382585b0db8db9d713401 +size 53086 diff --git a/marked/Rel-16/25_series/25956/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/25_series/25956/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23089e69d907ce040c9949505eac0fbbf5c3c346 --- /dev/null +++ b/marked/Rel-16/25_series/25956/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4cf94f18b5ffabee6811cb2b2bfb555ad8a63afc21fc31c3d1a472f66f60df1 +size 14718 diff --git a/marked/Rel-16/25_series/25956/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-16/25_series/25956/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35f61251935beb832a84a3c216d5b558c3180a8f --- /dev/null +++ b/marked/Rel-16/25_series/25956/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e10728bd24d4ed50b320bb26d14c25e98c5d7484997ae8877ccc560a319faa7e +size 50690 diff --git a/marked/Rel-16/25_series/25956/809eec371620084c4b949c66d5d7bae0_img.jpg b/marked/Rel-16/25_series/25956/809eec371620084c4b949c66d5d7bae0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cee3bef2c13199d2a36bd090ac630ef1635d96d6 --- /dev/null +++ b/marked/Rel-16/25_series/25956/809eec371620084c4b949c66d5d7bae0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3655b907de32d92feadf642d53872cc0f4c84756f2b1cdbf8039e8e6edb8184e +size 50888 diff --git a/marked/Rel-16/25_series/25956/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/25_series/25956/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc677b03a26771a29c145017d61cff3a43602d73 --- /dev/null +++ b/marked/Rel-16/25_series/25956/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:483ddf37e85bdbb70b121608f7b503e69bd6795073c1122cf5888e04217d60a8 +size 69750 diff --git a/marked/Rel-16/25_series/25956/8a4275b35551f2ec9825a1aa442c0db1_img.jpg b/marked/Rel-16/25_series/25956/8a4275b35551f2ec9825a1aa442c0db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65d01807fb1712707bf6d42c9fe3813fb03f77fa --- /dev/null +++ b/marked/Rel-16/25_series/25956/8a4275b35551f2ec9825a1aa442c0db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:939a3d0f447c56f29c2207e0929bb1c6112d1cdbba7947592e02d3f424aef065 +size 51349 diff --git a/marked/Rel-16/25_series/25956/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg b/marked/Rel-16/25_series/25956/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0d85c8b2837df872ed53c4b4457bbb160eb05da --- /dev/null +++ b/marked/Rel-16/25_series/25956/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:890bb11dce925c983fbdf64046967017cfde65c5937de9c04b097e1f81cb5e53 +size 50166 diff --git a/marked/Rel-16/25_series/25956/8f38356601e137ac471fc4771b9c5a5c_img.jpg b/marked/Rel-16/25_series/25956/8f38356601e137ac471fc4771b9c5a5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b1a68cd73322ab4b842089459d04bfbb7859091 --- /dev/null +++ b/marked/Rel-16/25_series/25956/8f38356601e137ac471fc4771b9c5a5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18dbc98127d53dc1b5ba3850c69df12e31e1e1f77cb9f796d8e2dff2aaf48286 +size 167476 diff --git a/marked/Rel-16/25_series/25956/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg b/marked/Rel-16/25_series/25956/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82eac0a98fdff219e9e04d50e75c68c30b677b3 --- /dev/null +++ b/marked/Rel-16/25_series/25956/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b371d13fcb11c3fbc59a97b744ec94203e4265a29754575fe1146122341d9b0 +size 68645 diff --git a/marked/Rel-16/25_series/25956/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-16/25_series/25956/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7625689b25b36f1f869d14c1faf74238bb9e348 --- /dev/null +++ b/marked/Rel-16/25_series/25956/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c131abb40eb514942de719d223f406350d63e0f919315d48c7104ec8417fb477 +size 30246 diff --git a/marked/Rel-16/25_series/25956/930335a43c8196e391f87e6860db4d45_img.jpg b/marked/Rel-16/25_series/25956/930335a43c8196e391f87e6860db4d45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af5340e58030bf975d0bc715ea251369d3ec0250 --- /dev/null +++ b/marked/Rel-16/25_series/25956/930335a43c8196e391f87e6860db4d45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be10cc4cc83babd9e4fc468f3f641d3c2f3840cce6c3dfd52b21677ccb89653e +size 69631 diff --git a/marked/Rel-16/25_series/25956/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-16/25_series/25956/9f92854fe6ecaf47760515c891a4fccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ab692db7eb9b673441831501c09339c5b184d95 --- /dev/null +++ b/marked/Rel-16/25_series/25956/9f92854fe6ecaf47760515c891a4fccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd16f7bbf5e2bc43ce4899166133afa4f8b8a57ef4453120452164c005aca166 +size 53674 diff --git a/marked/Rel-16/25_series/25956/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg b/marked/Rel-16/25_series/25956/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7af4b93b5c9ac9079f9fc980e5ba3eb5cc8a962 --- /dev/null +++ b/marked/Rel-16/25_series/25956/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af1338a8f45764313be809c54fababff4bbd1deb4d9de90bf23a85e779b0a4b4 +size 65681 diff --git a/marked/Rel-16/25_series/25956/a1a474be12b8992842992294b1d18592_img.jpg b/marked/Rel-16/25_series/25956/a1a474be12b8992842992294b1d18592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28d6f53f9dc71bebfd83e3a9bc245055990ddbfe --- /dev/null +++ b/marked/Rel-16/25_series/25956/a1a474be12b8992842992294b1d18592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d79d8213c643c5fb13d7ee38412b29d9ef719cf597c91947a60e77569ee388b4 +size 167286 diff --git a/marked/Rel-16/25_series/25956/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-16/25_series/25956/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ae4df527f7ee683218523bf5c4bae5793ddd28 --- /dev/null +++ b/marked/Rel-16/25_series/25956/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91d3bac783763e8f715c5dd47306d783ea1bc5a928278f25a6ab333f775c321d +size 50697 diff --git a/marked/Rel-16/25_series/25956/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg b/marked/Rel-16/25_series/25956/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fcffe99bc5202c0e19bfdd10317e9fcaa3e0fa0 --- /dev/null +++ b/marked/Rel-16/25_series/25956/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab5a54f9062eaa6b1020f06a424499c00fa24f28d154334c3c95d73694b1e1e +size 51493 diff --git a/marked/Rel-16/25_series/25956/a96c7e19f53f2350db97a90738a6fb51_img.jpg b/marked/Rel-16/25_series/25956/a96c7e19f53f2350db97a90738a6fb51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8670fb65c9e96bd20981180ddde40048c1be0e37 --- /dev/null +++ b/marked/Rel-16/25_series/25956/a96c7e19f53f2350db97a90738a6fb51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4753fa428f2788842852125fca6b062d5d272605c886822079094b77a19ec48d +size 49199 diff --git a/marked/Rel-16/25_series/25956/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg b/marked/Rel-16/25_series/25956/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d02813d8214b076acd309e21508a582d1ca8e7d3 --- /dev/null +++ b/marked/Rel-16/25_series/25956/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c605b20f845d3573c0982d2e64e7c739e7e4523aac0ba0c402e2add49354f8b7 +size 50555 diff --git a/marked/Rel-16/25_series/25956/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-16/25_series/25956/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dffacc12a92b8447278a5b4516df5b287f823bd --- /dev/null +++ b/marked/Rel-16/25_series/25956/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7be5baf76b527fa9e758a58574bf4e0183fd9d0ac3b8eb933e7e7940e4b83ab +size 50402 diff --git a/marked/Rel-16/25_series/25956/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/Rel-16/25_series/25956/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9baed4bad134c3406b2e7b0c934a3098090a7901 --- /dev/null +++ b/marked/Rel-16/25_series/25956/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b2dc60e2fc35fe3709184d8389180b3653b0befece5cc2e1372c4af46f4d5df +size 79545 diff --git a/marked/Rel-16/25_series/25956/b9f1f5c5167e357277b530940312d9ed_img.jpg b/marked/Rel-16/25_series/25956/b9f1f5c5167e357277b530940312d9ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4b50895411cf11155a0a9e80c6c17a439a44018 --- /dev/null +++ b/marked/Rel-16/25_series/25956/b9f1f5c5167e357277b530940312d9ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49fc65625d8154b695e810089f6cb054da971dfcf045a31afac8313afb158649 +size 51321 diff --git a/marked/Rel-16/25_series/25956/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-16/25_series/25956/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b95dba3423401dccab45d796325c6190ef18695 --- /dev/null +++ b/marked/Rel-16/25_series/25956/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3edf61cf15fe9b129d05382dc86a07283c8f787cdec5932746b41911581c1106 +size 50651 diff --git a/marked/Rel-16/25_series/25956/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-16/25_series/25956/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1452ab55c82cb5b4818f22ebf82e2535181865bf --- /dev/null +++ b/marked/Rel-16/25_series/25956/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f0bc6da2501c117a2554b4c3e703615da8d151cd93628200d5cd98b27ea8d41 +size 58149 diff --git a/marked/Rel-16/25_series/25956/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-16/25_series/25956/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eedede57dbf3847587a1cf6dcc3124437859b48 --- /dev/null +++ b/marked/Rel-16/25_series/25956/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfd44fb1cea5311e4908beaf73c17a8095872407666b24665e662bf5a79a8c35 +size 52942 diff --git a/marked/Rel-16/25_series/25956/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-16/25_series/25956/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8245d83e7df5d7f63c609a26c4892112546cd06 --- /dev/null +++ b/marked/Rel-16/25_series/25956/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd70d340c0522fec805b626e150321115ce13e8dc5024c52b23e960694e13ef6 +size 50654 diff --git a/marked/Rel-16/25_series/25956/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/Rel-16/25_series/25956/cfc852835f2d91bea8dc074568937e22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b72a9a4b07683d6897c1483bc1997b68e63cb88d --- /dev/null +++ b/marked/Rel-16/25_series/25956/cfc852835f2d91bea8dc074568937e22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad74110000a389fe5c9d9291f556434fc5623680b035a40f066b00d982410dce +size 167522 diff --git a/marked/Rel-16/25_series/25956/d49bc18ad8867b97bbb9aa580449a641_img.jpg b/marked/Rel-16/25_series/25956/d49bc18ad8867b97bbb9aa580449a641_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bcdbdab550bc48e1890d351c23233da479892cf --- /dev/null +++ b/marked/Rel-16/25_series/25956/d49bc18ad8867b97bbb9aa580449a641_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b058477c85b3fb2a0a5129e86fa6c78e6ceeb58733d6afbe627c23173f7e5f4 +size 50772 diff --git a/marked/Rel-16/25_series/25956/d6d2d323ed8fdca4c18f226f9ba3f480_img.jpg b/marked/Rel-16/25_series/25956/d6d2d323ed8fdca4c18f226f9ba3f480_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9e211c3036e53183b1259564a182e51f41549ed --- /dev/null +++ b/marked/Rel-16/25_series/25956/d6d2d323ed8fdca4c18f226f9ba3f480_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9f1e1bf335654e968235e1c210dce5097b8181dd4a49f4aff1b6385945c449e +size 78603 diff --git a/marked/Rel-16/25_series/25956/d94a0100320109c1b9cd75c1054c7b95_img.jpg b/marked/Rel-16/25_series/25956/d94a0100320109c1b9cd75c1054c7b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..236f7eac723d894a0ec6c0191d97fbb93c32e962 --- /dev/null +++ b/marked/Rel-16/25_series/25956/d94a0100320109c1b9cd75c1054c7b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d06c41ed5da75983e52968d1139655728a1341db39644bdccde99ed9ee340191 +size 75030 diff --git a/marked/Rel-16/25_series/25956/e01e66047c133f38249229dc639c9430_img.jpg b/marked/Rel-16/25_series/25956/e01e66047c133f38249229dc639c9430_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cda3d5bc12faf9724d794ec8c12b2b5d7911af8 --- /dev/null +++ b/marked/Rel-16/25_series/25956/e01e66047c133f38249229dc639c9430_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:858dfa59c7b847fa7a087818689e1656147911cc22b5e9b1666bd1467c380d23 +size 49153 diff --git a/marked/Rel-16/25_series/25956/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg b/marked/Rel-16/25_series/25956/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cca8dc5063b898cf5c97c4ea2394bc78db425ff5 --- /dev/null +++ b/marked/Rel-16/25_series/25956/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57a2e363f6503fb74790daeafcdf33415122298e6f25220dd5aacda53e67b448 +size 51317 diff --git a/marked/Rel-16/25_series/25956/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/Rel-16/25_series/25956/e046996962d6740cf050a5640e0c6b40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ba1211f135d4a5f993a09906eda4e4cf5b8d09f --- /dev/null +++ b/marked/Rel-16/25_series/25956/e046996962d6740cf050a5640e0c6b40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11d399b8564153f5c4ff5bed4d00545a75ea143a7c3243c7b30a2deb54dba2f4 +size 69532 diff --git a/marked/Rel-16/25_series/25956/e23c9577e177bf077bac8951a775dd90_img.jpg b/marked/Rel-16/25_series/25956/e23c9577e177bf077bac8951a775dd90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..263d48269cc790f358b7c91b036e26fd0eac224e --- /dev/null +++ b/marked/Rel-16/25_series/25956/e23c9577e177bf077bac8951a775dd90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acd304fa43f68a4537b2a8459e8360370ab5f3a636e4159eeac7cd6e11e293a8 +size 21648 diff --git a/marked/Rel-16/25_series/25956/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/25_series/25956/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15b871574969ce7bf54689111e7b137ee457994f --- /dev/null +++ b/marked/Rel-16/25_series/25956/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:289ce465fcd1e12f1c267719e6ab9dea4c2996c1a41ef7713ce4106360a663e0 +size 32457 diff --git a/marked/Rel-16/25_series/25956/e91633da5160c8af51a4ace6d3347f53_img.jpg b/marked/Rel-16/25_series/25956/e91633da5160c8af51a4ace6d3347f53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dffacc12a92b8447278a5b4516df5b287f823bd --- /dev/null +++ b/marked/Rel-16/25_series/25956/e91633da5160c8af51a4ace6d3347f53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7be5baf76b527fa9e758a58574bf4e0183fd9d0ac3b8eb933e7e7940e4b83ab +size 50402 diff --git a/marked/Rel-16/25_series/25956/ebce355620876e10f907f8b71926c112_img.jpg b/marked/Rel-16/25_series/25956/ebce355620876e10f907f8b71926c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af6ad9d6b6ffcf887497a773fb6bea0321f76b44 --- /dev/null +++ b/marked/Rel-16/25_series/25956/ebce355620876e10f907f8b71926c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4575004048530cdaff216738d553fbc517282666d5b40a64c48de3c0d5b0526 +size 31799 diff --git a/marked/Rel-16/25_series/25956/fd38170a3981416226ab91f7437ba821_img.jpg b/marked/Rel-16/25_series/25956/fd38170a3981416226ab91f7437ba821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cae8882ff498f7f48ed57c23a777cbb6f3c69265 --- /dev/null +++ b/marked/Rel-16/25_series/25956/fd38170a3981416226ab91f7437ba821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:517153be262d991b0881e015e53a2a6a1516ee06c522f45843144637bb76e9bc +size 49947 diff --git a/marked/Rel-16/25_series/25956/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-16/25_series/25956/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94c2f7da58cf22545e7250f99cb0b3207fc8bf54 --- /dev/null +++ b/marked/Rel-16/25_series/25956/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c829aa30cc8401a5d8c7d28cb1d563aee639ed6f398f1edace06422311f1a6 +size 50386 diff --git a/marked/Rel-16/25_series/25956/raw.md b/marked/Rel-16/25_series/25956/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a395ed7f2e38ef97ee33c177232b23abb8a85677 --- /dev/null +++ b/marked/Rel-16/25_series/25956/raw.md @@ -0,0 +1,2025 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 System Impacts of Repeaters ..... | 7 | +| 4.1 Error Vector Magnitude (EVM)..... | 7 | +| 4.2 Peak Code Domain Error (PCDE) ..... | 8 | +| 4.3 Frequency error ..... | 8 | +| 4.4 Adjacent Channel Leakage Ratio (ACLR)..... | 8 | +| 4.5 Time Delay..... | 9 | +| 4.6 Location Services (LCS) ..... | 10 | +| 4.6.1 OTDOA ..... | 10 | +| 4.6.2 Cell coverage based positioning method..... | 11 | +| 4.6.3 Network assisted GPS methods..... | 11 | +| 4.7 Automatic Gain Control (AGC)..... | 11 | +| 4.8 Adjacent Channel Rejection Ratio (ACRR)..... | 12 | +| 5 Planning with Repeaters..... | 12 | +| 5.1 Sole System ..... | 12 | +| 5.1.1 Antenna Isolation..... | 12 | +| 5.1.2 Coupling loss measurements ..... | 13 | +| 5.1.3 Gain Settings ..... | 13 | +| 5.1.4 Delay..... | 14 | +| 5.2 Co-existence with UTRA FDD..... | 14 | +| 5.2.1 Out of band gain ..... | 14 | +| 5.2.2 Isolation ..... | 14 | +| 5.2.2.1 Example on application of equations..... | 15 | +| 5.3 Co-existence with UTRA TDD..... | 16 | +| 5.3.1 Isolation ..... | 16 | +| 5.4 Co-existence with GSM 900 and/or DCS 1800 ..... | 16 | +| 5.4.1 Isolation ..... | 16 | +| 5.5 Environments with low minimum coupling loss (MCL) ..... | 16 | +| 5.5.1 Normal repeater parameters..... | 16 | +| 5.5.2 Repeater parameters adjusted to low MCL ..... | 17 | +| 5.6 Analysis of out of band gain in the 3 rd adjacent channel..... | 18 | +| 5.6.1 MCL=70 dB..... | 18 | +| 5.6.2 MCL=40 dB..... | 18 | +| 6 System Simulations and Analysis ..... | 19 | +| 6.1 Down-link co-existence simulations ..... | 19 | +| 6.2 Outdoor coverage (High CL Rep-UE )..... | 21 | +| 6.3 Indoor coverage (Low CL Rep-UE )..... | 22 | +| 6.4 Repeater up-link co-existence simulations..... | 23 | +| 6.4.1 General ..... | 23 | +| 6.4.2 Simulation Assumptions..... | 25 | +| 6.4.3 Results ..... | 25 | +| 6.4.4 Conclusion..... | 26 | +| 6.5 Repeater ACRR system impact simulations ..... | 26 | +| 6.5.1 General ..... | 26 | +| 6.5.2 Simulation Description..... | 27 | +| 6.5.2.1 Infrastructure ..... | 27 | +| 6.5.2.2 Preparation..... | 27 | +| 6.5.2.3 Connection..... | 28 | +| 6.5.2.4 Iterations ..... | 28 | + +6.5.2.5 Parameters used through out the simulations ..... 29 +6.5.3 Results ..... 31 +6.5.3.1 288 m between repeater A and BSB..... 31 +6.5.3.2 164 m minimum distance between repeater A and BSB ..... 45 +6.5.4 Conclusions ..... 58 +6.5.5 Comments..... 58 +Annex A: Change History ..... 59 + +# --- 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 purpose of the following document is to describe planning guidelines and system scenarios for UTRA repeaters. In addition it also contains simulations and analysis of the usage of repeaters in UMTS networks. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 25.942 + +[2] R4-030365 + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply, unless otherwise stated: + +![Figure 3.1: Diagram illustrating the system architecture for a repeater. A Base Station (BS A) is connected to a Repeater (Rep A) via a dashed line labeled EDOCL_BSA-RepA. The BS A is also connected to a User Equipment (UE A) via a dashed line labeled CL_BSA-UEA. The Rep A is connected to the UE A via a dashed line labeled CL_RepA-UEA. The diagram shows the flow of signals from the BS A through the Rep A to the UE A, with coupling losses indicated between each component.](e23c9577e177bf077bac8951a775dd90_img.jpg) + +Figure 3.1: Diagram illustrating the system architecture for a repeater. A Base Station (BS A) is connected to a Repeater (Rep A) via a dashed line labeled EDOCL\_BSA-RepA. The BS A is also connected to a User Equipment (UE A) via a dashed line labeled CL\_BSA-UEA. The Rep A is connected to the UE A via a dashed line labeled CL\_RepA-UEA. The diagram shows the flow of signals from the BS A through the Rep A to the UE A, with coupling losses indicated between each component. + +Figure 3.1 + +| | | +|---------------------------|------------------------------------------------------------------------------------| +| ACRR RepA | Adjacent Channel Rejection Ratio for repeater A. | +| ACG RepA | Adjacent Channel Gain for repeater A. | +| CL BSA-UEA | Coupling Loss between Base Station A and the User Equipment A. | +| CL RepA-UEA | Coupling Loss between Repeater A and User Equipment A. | +| d RepA | Group delay of repeater A. | +| EDoCL BSA-RepA | Effective Donor Coupling Loss between the donor Base Station A and the Repeater A. | +| G RepA | Set gain of Repeater A. | +| Gmax RepA | The maximum Gain possible to set of Repeater A. | +| M RepA | Noise Margin for repeater A. | +| NF RepA | Noise Figure of repeater A. | + +| | | +|----------------------|----------------------------------------| +| $P_{\text{repA}}$ | Output power of repeater A. | +| $P_{\text{maxRepA}}$ | Maximum output power of repeater A. | +| $P_{\text{maxBSA}}$ | Maximum output power of base station A | + +![Figure 3.2: Network diagram showing signal paths and coupling losses between BS A, BS B, Rep A, UE A, and UE B. BS A and BS B are on the left, Rep A is in the center, and UE A and UE B are on the right. Dashed lines represent coupling losses: EDoCL_BSA-RepA from BS A to Rep A; CL_BSB-RepA from BS B to Rep A; CL_BSB-UEB from BS B to UE B; CL_BSB-UEA from BS B to UE A; and CL_RepA-UEB from Rep A to UE B.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +Figure 3.2: Network diagram showing signal paths and coupling losses between BS A, BS B, Rep A, UE A, and UE B. BS A and BS B are on the left, Rep A is in the center, and UE A and UE B are on the right. Dashed lines represent coupling losses: EDoCL\_BSA-RepA from BS A to Rep A; CL\_BSB-RepA from BS B to Rep A; CL\_BSB-UEB from BS B to UE B; CL\_BSB-UEA from BS B to UE A; and CL\_RepA-UEB from Rep A to UE B. + +Figure 3.2 + +| | | +|------------------------|----------------------------------------------------------------| +| $CL_{\text{BSB-UEA}}$ | Coupling Loss between Base station B and the User equipment A. | +| $CL_{\text{RepA-UEB}}$ | Coupling Loss between Repeater A and User equipment B. | +| $CL_{\text{BSB-RepA}}$ | Coupling Loss between Bas station B and Repeater A. | +| $CL_{\text{BSB-UEB}}$ | Coupling Loss between base station B and User equipment B. | +| $SsIR$ | Signal to self Interference Ratio. (Described below) | + +## 3.2 Symbols + +(void) + +## 3.3 Abbreviations + +(void) + +# 4 System Impacts of Repeaters + +## 4.1 Error Vector Magnitude (EVM) + +The introduction of a repeater has an impact in the EVM of the system. The basic effect is reflected in a system noise rise, which can be calculated from the EVM value the received signal exhibits. The formula is + +$$\text{Noise rise} = 10 \log(1 + \text{EVM}^2)$$ + +In the scenario of a Repeater amplifying the signal the EVM of the signal is calculated according to the following formula for uncorrelated processes: + +$$(\text{EVM\_total})^2 = (\text{EVM\_NodeB})^2 + (\text{EVM\_Repeater})^2$$ + +Taking the specified value of 17,5 % for both the Node B (as well as for the UE) and the Repeater result in a total EVM of 24,7 %. Calculating the noise rise for the Repeater scenario gives a value of 0,26 dB in the area of the repeater's coverage. This compares to a noise rise in a scenario without Repeater of 0,13 dB. The difference between the two numbers is the worst-case closed loop power rise in an otherwise perfect system that would occur with a Repeater being used. + +## 4.2 Peak Code Domain Error (PCDE) + +In the specification of the Peak Code Domain Error value of the Repeater -35 dB is used. The number for the Node B is -33dB. If we assume the processes in the Repeater that lead to the PCDE being independent of the equivalent process in the Node B we can assume that they can be treated as noise. In this case the resulting value for PCDE is calculated from the linear addition of the two signals that will lead to -31 dB. This is a 2 dB degradation to the value of the Node B. For the repeated cell the degradation might be negligible. In case of a neighbour cell the might be affected to some extend. Presumably the soft handover gain will be reduced by the tenth of a dB. + +## 4.3 Frequency error + +The effect of the additional frequency error will be a reduction of the maximum speed. In the repeater core specification the minimum requirement on frequency stability is 0,01 ppm. Hence, with the 0,05 ppm minimum requirement for the base station frequency stability the resulting "worst case" for a signal that have been amplified by the repeater is 0,06 ppm. + +## 4.4 Adjacent Channel Leakage Ratio (ACLR) + +With regard to the mentioned ACLR we have to investigate the behaviour of the Repeater. For this reason we use the model shown in the following Figure 4.1: + +![Figure 4.1: Simplified Repeater model. The diagram shows a bi-directional signal path. On the left, two input signals enter the system through duplexer-like components. The top path consists of an amplifier, a mixer, a filter, another mixer, and a second amplifier. The bottom path consists of an amplifier, a mixer, a filter, another mixer, and a second amplifier. Both paths then exit through another set of duplexer-like components on the right.](731f533b0599c8e42a063f06e4332045_img.jpg) + +Figure 4.1: Simplified Repeater model. The diagram shows a bi-directional signal path. On the left, two input signals enter the system through duplexer-like components. The top path consists of an amplifier, a mixer, a filter, another mixer, and a second amplifier. The bottom path consists of an amplifier, a mixer, a filter, another mixer, and a second amplifier. Both paths then exit through another set of duplexer-like components on the right. + +Figure 4.1: Simplified Repeater model. + +The Repeater in its basic function is bi-directional amplifier of RF signals from Base Stations in the downlink path and from Universal Equipments (UE) as mobile stations in the uplink path. The operating bands in which the Repeater amplifies is determined by the IF filter in its bandwidth and by the duplexer filter in its frequency range for operational configuration. In our discussion we will use the parameters defined in Table 4.1. + +Table 4.1: Parameters of the Repeater model. + +| Parameter | Description | Unit | Assumed value | Comment | +|------------------|----------------------------------------------------------------------------------------------------|--------------|------------------|--------------------------------------------------------------------| +| G | Repeater gain | dB | 90 dB | UL and DL gain should be the same for a balanced link. | +| Pout_DL_max | maximum Repeater average output power measured with WCDMA signal according to model 1 of TS25.141. | dBm | 30 dBm | DL value | +| Pout_UL_max | maximum Repeater average output power measured with WCDMA signal according to model 1 of TS25.141. | dBm | 12 dBm | UL value | +| NF | Repeater Noise Figure | dB | 5 dB | valid for UL and DL | +| N_therm (30 kHz) | Thermal Noise Power density in a Bandwidth of 30 kHz | dBm / 30 kHz | -129 dBm / 30kHz | -174 dBm/Hz (at 25 °C) + 45 dB | +| S (30 kHz) | WCDMA Signal Power Density | dBm / 30 kHz | Pout - 21 dB | the factor of 21 dB is the relation of channel bandwidth to 30 kHz | + +The Repeater output noise density can be calculated according to the formula: + +$$N\_Rep (30\text{kHz}) = N\_therm (30\text{kHz}) + NF + G = -34 \text{ dBm}/30 \text{ kHz} .$$ + +Considering the output of the Repeater in the Downlink path we will find an average power 30 dBm in the WCDMA channel. This is resulting in a signal density of + +$$S\_Downlink = +9 \text{ dBm}/30 \text{ kHz}.$$ + +This leads to a signal-to-noise ratio of the Downlink of: + +$$S / N\_Downlink = 43 \text{ dB}.$$ + +The Adjacent Channel Leakage Ratio (ACLR) as defined for BS is stating -45 dB for the first adjacent channel and -50 dB for the second adjacent channel. This situation is illustrated in Figure 4.2. + +In the Repeater case the resulting output frequency spectrum is shown below. + +![Figure 4.2: Repeater output frequency spectrum. The graph shows Power Density in dBm/Hz on the y-axis and Frequency in MHz on the x-axis. A cyan rectangular block represents the 'WCDMA Signal with ACLR according BS Spec.'. A yellow rectangular block represents the 'thermal Output Noise'. The signal is shown above the noise floor. A vertical double-headed arrow labeled 'S/N' indicates the signal-to-noise ratio between the signal peak and the noise floor.](0d5fdb87a392819c7d2e3b6230912a0b_img.jpg) + +Figure 4.2: Repeater output frequency spectrum. The graph shows Power Density in dBm/Hz on the y-axis and Frequency in MHz on the x-axis. A cyan rectangular block represents the 'WCDMA Signal with ACLR according BS Spec.'. A yellow rectangular block represents the 'thermal Output Noise'. The signal is shown above the noise floor. A vertical double-headed arrow labeled 'S/N' indicates the signal-to-noise ratio between the signal peak and the noise floor. + +**Fig. 4.2: Repeater output frequency spectrum.** + +It is obvious that the ACLR cannot be measured in the Repeater case due to the fact that the this signal is below the amplifier thermal noise of the Repeater amplifier chain. + +This even get worse when the Uplink is considered. As in this path the maximum average value of the output power is reduced to 12 dBm resulting in a signal power density of $S = -9 \text{ dBm} / 30 \text{ kHz}$ , the signal-to-noise ratio will be even smaller: + +$$S / N\_Uplink = -9 \text{ dBm} / 30 \text{ kHz} - (-43 \text{ dBm} / 30 \text{ kHz}) = 34 \text{ dB}.$$ + +This collision is the reason why the ACLR requirement as it is written for the BS equipment cannot be met with a Repeater. The ACLR measurement will be limited by the thermal noise of the Repeater amplifier chain. + +Spectral components (noise, ACP, intermodulation products, spurious signals, ...) falling outside the operating band are fully addressed in the TS 25.106 subclause 9. + +## 4.5 Time Delay + +Using common narrow band filter technologies (SAW) the IF-filtering process introduces a time delay of about 5-6 $\mu\text{s}$ to the signal. This puts a requirement on the length of the receiver's search window. It is, however, believed that the channel models now specified in TS 25.104 are sufficient for guaranteeing the receiver's performance in an area covered by both a repeater and a base station. + +Figure 4.3 illustrates a case where the UE receives multipath signals, both from the repeater and from the BS. Here, the repeater will introduce artificial multipaths. This could possibly reduce the effects from fading, but also increase the number of paths that are needed to capture a certain percentage of the energy is increased and it is therefore important to have a sufficient amount of RAKE fingers in the receiver. + +However, traditionally the repeater is deployed to cover a smaller area compared to the BS and the number of resolvable multipaths could therefore be believed to lower compare to that of macrocellular deployment. + +![Diagram illustrating excess multipaths introduced by a repeater. A User Equipment (UE) is shown receiving signals from a Base Station (BS) and a Repeater. The BS is connected to a building. The Repeater is connected to another building. Arrows indicate signal paths from the BS and the Repeater to the UE.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram shows a User Equipment (UE) represented by a mobile phone icon. Above it is a Base Station (BS) represented by a lattice tower icon. Below the BS is a Repeater represented by a small circle on a pole. To the left of the BS is a building with five windows. To the left of the Repeater is another building with five windows. Arrows indicate signal paths: from the BS to the UE, from the Repeater to the UE, and from the BS to the Repeater. There are also arrows from the buildings to the UE, representing other multipath components. + +Diagram illustrating excess multipaths introduced by a repeater. A User Equipment (UE) is shown receiving signals from a Base Station (BS) and a Repeater. The BS is connected to a building. The Repeater is connected to another building. Arrows indicate signal paths from the BS and the Repeater to the UE. + +**Fig. 4.3: Illustration of the excess multipaths that are introduced by the repeater in a scenario where the UE is receiving the signal, from both the BS and the repeater.** + +## 4.6 Location Services (LCS) + +The co-existence between repeaters and location services (LCS) is studied in this clause. Three methods for location services are currently specified in TS 25.305: OTDOA, Cell coverage based positioning and Network assisted GPS. + +### 4.6.1 OTDOA + +The OTDOA method is based on measurements of the UTRA pilot signal (CPICH) made by the UE and the Location Measurement Unit (LMU). The position of the UE is estimated by using the observed time difference of arrival (OTDOA) from three, or more, base stations. + +Figure 4.4 is an illustration of a network using repeaters. In this case the signal path from BS4 to the UE can be either the direct path, with a time delay of $\tau_4$ , or the path through the repeater, with a time delay of $\tau_{RB} + \tau_d + \tau_R$ , where $\tau_d$ is introduced by the repeater. This extra time delay introduces an ambiguity when performing the location estimation. + +![Diagram illustrating the effect of a repeater installation in a network using OTDOA based LCS. A User Equipment (UE) is shown receiving signals from four base stations (BS 1, BS 2, BS 3, and BS 4). BS 1, BS 2, and BS 3 are direct signals with time delays τ1, τ2, and τ3 respectively. BS 4's signal is received via a repeater, with a time delay τ4 from BS 4 to the repeater, τRB from the repeater to the UE, and τd representing the delay at the repeater. The repeater is labeled 'Repeater for BS 4'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Diagram illustrating the effect of a repeater installation in a network using OTDOA based LCS. A User Equipment (UE) is shown receiving signals from four base stations (BS 1, BS 2, BS 3, and BS 4). BS 1, BS 2, and BS 3 are direct signals with time delays τ1, τ2, and τ3 respectively. BS 4's signal is received via a repeater, with a time delay τ4 from BS 4 to the repeater, τRB from the repeater to the UE, and τd representing the delay at the repeater. The repeater is labeled 'Repeater for BS 4'. + +**Fig. 4.4: Illustration of the effect of a repeater installation in a network using OTDOA based LCS.** + +To avoid this ambiguity different mechanisms can be implemented: + +1. For small cells one can exclude one of the signals if it has too long path delay (i.e. passed through a repeater). Hence, for cells smaller than 1500 m (corresponding to 5 $\mu\text{s}$ ) it is detectable, whether or not, a repeater has transmitted the signal. +2. If the UE detects more than three sites, as the case is in Figure 4.4, the measurement of the time delay from BS 3 can be excluded, based on a too large relative difference to the time delays from BS 1-3. The probability of detecting three sites is much lower compared to that of detecting four or five sites. This result holds true for both the urban and the suburban environment, when the UE uses 16 ideal periods. + +### 4.6.2 Cell coverage based positioning method + +The only impact is that the cells become larger using repeaters and that this method thereby has less accuracy compared to a smaller cell. Other than that the repeater does not affect this LCS method. + +### 4.6.3 Network assisted GPS methods + +The UTRA network can assist the UE GPS receiver in several ways. E.g. by providing a frequency reference, since UTRAN has a better frequency stability compared to GPS (0,05 ppm frequency error compared to 20 ppm). UTRAN can also provide the UE with a timing reference to reduce the UE GPS search time and improve the accuracy. + +If a repeater is deployed in the network this will lead to about 5 $\mu\text{s}$ extra delay. This extra delay is not of the extent that it will affect the performance of GPS assisted method. It is however important that the frequency stability of UTRAN is maintained in the repeater. + +## 4.7 Automatic Gain Control (AGC) + +Repeaters use a function called Automatic Gain Control (AGC) to adjust the gain so that self-oscillation is avoided. The gain of the repeater shall be adjusted so that there is a margin to the port isolation between the up- and down-link directions as described in the sub-clause Gain Settings. + +As a consequence the AGC is not intended to constantly adjust the gain during the normal mode of operation. It shall be seen as a fail back to prevent self-oscillation if, for some reason, the isolation between the ports is reduced compared to the isolation measured during the deployment or an increase in input power to a level larger than the input level creating the maximum output power. + +The AGC is also slow in comparison to the fast power control (the range of several microseconds) in order not to interfere with the system performance. The AGC should further adjust the gain in both the up and downlink in order to make the repeater a transparent system element. + +## 4.8 Adjacent Channel Rejection Ratio (ACRR) + +The secondary impact on the adjacent channel operator as described in section 5.2.2 gives rise to a requirement of an explicit requirement on ACRR in the requirement specification. After simulations described in section 6.5 the requirements are introduced in the repeater specifications. + +# --- 5 Planning with Repeaters + +## 5.1 Sole System + +### 5.1.1 Antenna Isolation + +Antenna isolation is an essential issue for the performance of a repeater. + +As a repeater only amplifies a received signal, it can act as an oscillator under certain circumstances. The feedback path in this amplifier system are the two antennas: coverage antenna and donor antenna. + +In order to prevent oscillation of the system, the feedback must be lower than the amplifier gain. This loss in the feedback path is called the *Antenna Isolation*. It must be 15 dB higher than the repeater gain to guarantee an adequate protection against self-oscillation of the repeater. + +Several factors have influence on the antenna isolation: + +#### 1. Antenna pattern (Horizontal and vertical) + +The optimum is a combination of donor and coverage antennas that are mounted the way that there is a null in the antenna pattern in the direction pointing towards the other antenna. A null means minimum antenna gain in the specified direction. + +As both antennas are usually mounted in opposite directions, it is useful to chose both donor and coverage antenna types that have a high front-to-back ratio. + +#### 2. Vertical separation + +Typical antennas that are used for repeater sites have a narrower aperture in the vertical antenna pattern, the vertical distance of the antenna influences the isolation of the antenna system. In a typical configuration, when both antennas are mounted on a pole, there is a null in the antenna pattern pointing vertically up and down from the antenna's feeding point. If there is a horizontal separation between the antennas, additional lobes in the vertical antenna pattern have to be taken into account. + +#### 3. Environment of both antennas + +The environment of the antennas is a very important factor. The reflection and attenuation properties of all materials near the antenna can influence the antenna isolation drastically. + +- The waves transmitted by antennas are reflected by surfaces, depending on the materials. If there is a reflection from a building towards the pole with the mounted antennas, this can decrease the antenna isolation by more than 10 dB. +- The material of the tower itself has also an effect on the isolation: If both antennas are mounted on a tower made of concrete, this improves the antenna isolation, as signals are attenuated and reflected by the material of the tower. A steel grid tower however might not increase antenna isolation particularly, as the distances between the single elements might be bigger than half a wavelength, which means that radiated power can pass the tower almost unattenuated. In this case, antenna isolation is more dependent on the antenna patterns. + +- Shielding grids mounted near the antennas have also an effect on the isolation. Generally, isolation can be improved using a shielding grid by approximately 5 dB. This depends on the shape of the shielding grid. Grids that are shaped according to the antenna outlook are better than simple ones. + +### 5.1.2 Coupling loss measurements + +The links of most the interest are the coupling loss between the Node B (Base Station = BS) and the repeater and at the repeater between the donor- and the coverage antenna. + +#### 1. Coupling loss between the Node B and the repeater. + +- 1) Connect a Measurement User Equipment to the donor antenna and measure the incoming pilot signal. +- 2) The coupling loss between Node B and the repeater is then calculated as + +$$CL = \text{BS Pilot Level output power [dBm]} - \text{Measured input power at the Measurement User Equipment [dBm]}.$$ + +#### 2. Coupling loss at the repeater between the donor- and the coverage antenna. + +- 1) Connect the input of a spectrum analyser to the donor antenna cable +- 2) Set up the instrument for the desired UMTS band. +- 3) Connect a signal generator to the coverage antenna cable of the repeater. +- 4) Set up the analyser for the highest possible sensitivity (more than -100dBm) for 0 dBm source-power. +- 5) Set the analyser to "max-hold" if you do not use a tracking generator. +- 6) Set the output-power of the generator to 0 dBm. +- 7) Start sweeping +- 8) The minimum isolation is the highest value of the curve (except carriers transmitted by surrounding BS). (Note the highest value for further use.) +- 9) Change measurement-ports to check for the opposite direction by repeating the measurement procedure. (Note the worst value of isolation for further use.) + +### 5.1.3 Gain Settings + +Considering the repeater application in an isolated UMTS system, the basic rule as described above applies for both up-link and down-link: + +$$G_{\text{RepA}} \leq \text{Repeater port isolation} - 15 \text{ dB}$$ + +For the down-link the following rule of thumb ensures that the repeater AGC (Automatic Gain Control) is not activated during normal traffic conditions. + +$$G \leq P_{\text{maxRepA}} + EDoCL_{\text{BSA-RepA}} - P_{\text{maxBSA}}$$ + +In cell planning, the repeater can be modelled as a base station with transmit power + +$$P_{\text{RepA}} = P_{\text{BSA}} - EDoCL_{\text{BSA-RepA}} + G_{\text{RepA}} \text{ (dBm)}$$ + +For the up-link, the repeater has a transferred sensitivity; + +$$\text{Sensitivity}_{\text{RepA}} = \text{Sensitivity}_{\text{BSA}} - (EDoCL_{\text{BSA-RepA}} - G_{\text{RepA}}) \text{ (dBm)}$$ + +The transferred sensitivity is controlled by the setting the repeater gain in relation to the effective donor coupling loss. It is recommended that the transferred sensitivity is approximately $(5 \text{ to } 10) + N_{f\text{repA}}$ dB less than the donor base station sensitivity, in order not to desensitise the base station. This rule can be adjusted in the case where the repeater coverage area is also the main coverage area of the base station. The term "noise margin", M, is introduced to describe the difference between the base station sensitivity and the transferred repeater sensitivity in the installation. + +$$M_{\text{RepA}} = EDoCL_{\text{BSA-RepA}} - G_{\text{RepA}} \text{ (dB)}$$ + +The gain should be set so that the link balance through the repeater path is the same as the link balance in the donor base station. The loss of diversity gain may here be considered. + +### 5.1.4 Delay + +The UTRA BS and UEs can handle a 20 $\mu\text{s}$ time delay between two paths (c.f. TS 25.101 and TS 25.104). The repeater introduces a time delay of 5-6 $\mu\text{s}$ . The signal paths introduced through the repeater will be longer than the direct path, both due to the extra travelling distance required for the signal (approximately 5 $\mu\text{s}$ per 1.5 km) and due to the group delay in the repeater itself. + +For outdoor repeater coverage, where the areas can be substantial, it is a rule of thumb that the repeater site should be placed between the repeater service area and the donor base station. + +For applications with donor signal provided via optical fibre, it should be noted that the speed of light in fibres is approximately 2/3 of that in vacuum, or 5 $\mu\text{s}$ per km. This may introduce extra delay to be considered when designing both indoor and outdoor repeater applications. + +## 5.2 Co-existence with UTRA FDD + +### 5.2.1 Out of band gain + +In the UTRA repeater core specification TS 25.106 the out of band requirement have been derived assuming an in-band gain of 90 dB. The rationale for this value was the common understanding that it represents a maximum gain value for UTRA repeaters and that UTRA repeaters with higher value are very unlikely. In most application the repeater gain may be adjusted to lower values. + +With a reduction of the in-band gain value, compared to the assumed 90 dB, the out of band gain values, which decides the adjacent channel gain (ACG) will also be reduced compared to the values occurring in the specification TS 25.106. + +### 5.2.2 Isolation + +Taking other operator systems into concern, it is the responsibility of the repeater operator to make sure that the repeater installation does not significantly alter the cellular design of the uncoordinated operator. + +In the case where a repeater is installed in the vicinity of a base station operating on the adjacent channel the required isolation between base station B and the repeater's donor port will depend on the up-link gain. It can be seen that the signal from UEB to BSB can take the two paths "directly" or "via repeater A", both of which comprise multi-paths. It is here assumed that the path through the repeater will be badly distorted, since the delay spread in the adjacent carrier frequencies are bound to be substantial. As a consequence, the signal travelled through the repeater is considered to be interference only. However, this interference will have a fixed relation to the signal power from UEB arriving in BSB since it follows the power control applied from BSB on UEB. + +The term "self-interference", is here introduced to describe this phenomenon. SsIR (Signal to self Interference Ratio) is the relation between the power level of the distorted UEB signal from the repeater A path and the undistorted signal arriving direct from the UE, taken on the BSB receiver terminal. The effect of putting the SsIR to 0 dB is that a UEB with this SsIR occupies twice the air interface capacity from BSB as required from a UE with infinite SsIR utilising the same service. + +Now, in order to ensure the stability of system B a proper SsIR must be set, resulting in a minimum requirement for the isolation between the repeater A donor port and the base station B receive port: + +$$CL_{\text{BSB-RepA}} \geq \text{SsIR} + ACG_{\text{RepA}} - CL_{\text{minRepA-UEA}} + CL_{\text{BSB-UEB}} \text{ (dB)}$$ + +It is here assumed that the UE of system A and the UE of system B can enter the same areas and hence + +$$CL_{\text{RepA-UEA}} = CL_{\text{RepA-UEB}}.$$ + +The $CL_{\text{minRepA-UEA}}$ is the minimum Coupling loss that can be experienced between the repeater and the UE. It is assumed that the coupling loss between the repeater and an UE in the repeater service area will vary more than the coupling loss between BSB and the same UE. $CL_{\text{BSB-UEB}}$ is taken where $CL_{\text{minRepA-UEA}}$ occurs. + +The $ACG_{\text{RepA}}$ can be calculated as the gain set in repeater A minus the repeater's Adjacent Channel Rejection Ratio (ACRR). The ACRR of the repeater can be estimated as the maximum gain that can be set in the repeater minus the + +adjacent channel maximum gain as stated in TS 25.106, section 8.1, unless otherwise stated by the repeater manufacturer. E.g. the gain of 90 dB assumed as $G_{max,repA}$ renders the $ACRR_{repA}$ of 37 dB according to TS 25.106. + +The above described formulae for $CL_{BSB-RepA}$ do not take into account the absolute power and spurious emission requirements put forward in TS 25.106, section 9.1. The required coupling losses between the repeater's donor port and base station B are derived using the unwanted emission requirements in the first adjacent channel (TS 25.106 section 9.1.1): + +For $P_{max,RepA} \geq +39$ dBm; + +$$CL_{BSB-RepA} \geq 105 \text{ dB}$$ + +For $+31 \text{ dBm} \leq P_{max,RepA} < +39 \text{ dBm}$ ; + +$$CL_{BSB-RepA} \text{ (dB)} \geq P_{max,RepA} \text{ (dBm)} + 66 \text{ dB}$$ + +For $P_{max,RepA} < +31 \text{ dBm}$ ; + +$$CL_{BSB-RepA} \geq 97 \text{ dB}$$ + +The required coupling losses are calculated according to the requirement that the spurious emission level does not exceed -126 dBm/100 kHz at base station B's receive port (corresponding to spurious emission requirement for co-located BS, c.f. TS 25.104 and a 30 dB MCL, c.f. TR 25.942). Normal up-link powers are in the range of 0 dBm - 20 dBm. + +In the downlink direction the UTRA repeater specification TS 25.106 includes additional requirement on spurious emission for the protection of co-located UTRA FDD BS receivers. If these additional requirements are applied, the isolation between the coverage antenna and the base station antennas should be more than 30 dB. + +Given the above recommendations, the coverage antenna should be put closer to the BS antennas than the donor antenna should where repeaters are co-sitting with UMTS FDD base stations. The isolation required between the donor antenna and the service antenna will generate the isolation required between the donor antenna and the co-sited base station antenna. It is also recommended to use a high gain donor antenna with narrow horizontal beam width so that the UL power is directed exclusively towards the donor BS. + +#### 5.2.2.1 Example on application of equations + +Assume an area where two UMTS operators, A and B, are using adjacent RF-channels. + +Operator A wants to put a repeater in a position in the area. The coupling loss between the repeater donor port and the donor BS is measured to be 100 dB (using a UE from operator A connected to the antenna feeder to be connected to the repeater donor port.) Applying a noise margin of 10 dB, the repeater gain is set to 90 dB. The service antenna is mounted so that the repeater antenna isolation requirements are fulfilled. + +The minimum coupling loss between a UE A and the repeater service port is measured to be 70 dB (total coupling loss through the repeater is measured to be 80 dB, and hence the coupling loss between the repeater and the UE is less by the set noise margin). A UE from operator B is used to measure the coupling loss between the UEB and the BSB in this point. The result is 100 dB coupling loss. The Adjacent channel rejection ratio is estimated to be 37 dB as described above. The $SsIR$ at this point is set to 0 dB (implying that it will be lower every where else), and hence the minimum required coupling loss between the repeater donor port and the BS B is calculated to be 83 dB. The coupling loss between the BS B and the repeater donor port can be verified by connecting the UE B to the donor antenna feeder at the repeater site and measuring it. + +## 5.3 Co-existence with UTRA TDD + +### 5.3.1 Isolation + +In the downlink direction the UTRA FDD repeater specification TS 25.106 includes additional requirement on spurious emission for the protection of co-existence with UTRA TDD. If these additional requirements are applied, the isolation between the coverage antenna and the base station antennas should be more than 30 dB. + +For the donor antenna, the repeater should have the same coupling loss values to the BS as described in the section above. + +## 5.4 Co-existence with GSM 900 and/or DCS 1800 + +### 5.4.1 Isolation + +Co-existence and co-siting with GSM 900 and/or DCS 1800 is addressed in the UTRA repeater performance specification where additional requirements exist for these scenarios. + +If these additional requirements are applied, the isolation between the coverage antenna or donor and the base station antennas should be more than 30 dB. + +## 5.5 Environments with low minimum coupling loss (MCL) + +This section addresses the use of and planning with repeaters in environments with a Minimum Coupling Loss (MCL) of 40 dB. The cases are studied, one where the repeater's parameters are intended for general applications and one where they have been changed to align with the MCL value investigated. In the examples below "A" indicate the channel being amplified by the repeater and "B" the service at the adjacent channel. + +### 5.5.1 Normal repeater parameters + +The following parameters are seen to represent a repeater intended for normal applications; + +$P\_max\_DL$ (maximum power down-link) = 30 dBm + +$P\_max\_UL$ (maximum power up-link) = 12 dBm (the value can be reduced with respect to the Downlink due to the uplink power control mechanism) + +$G$ (gain, common for both directions) = 90 dB + +$NF$ (noise figure) = 5 dB + +The coupling loss between the repeater and the base station is 100 dB and the output power of 30 dBm is thus the result of a 40 dBm BS output power. + +If we now investigate the maximum received power for UEA we find that: + +$$P\_received\_max\_UEA = 30 \text{ dBm } (P\_max\_DL) - 40 \text{ dB } (MCL) = -10 \text{ dBm.}$$ + +This value is 15 dB greater than the minimum requirements on the maximum UE received power of -25 dBm (TS 25.101) and hence quality degradation or dropped calls can be expected. + +Further, the down-link interference at UEB due to the UE's Adjacent Channel Selectivity (ACS) can be calculated by using the 33 dB ACS value given in TS 25.101: + +$$I\_UEB = 30 \text{ dBm } (P\_max\_DL) - 40 \text{ dB } (MCL) - 33 \text{ dB } (ACS) = -43 \text{ dBm.}$$ + +This interference level is clearly too great in comparison to the signal levels that can be expected on down-link of service B. As a consequence quality degradation or dropped calls can be expected. + +In conclusion it can be stated that the usage of a repeater with normal parameters setting (given above) will result in dropped calls on the down-link, both the operator installing the repeater as well as operators at adjacent channels, when used in an environment with a 40 dB MCL. This should hence be avoided. + +### 5.5.2 Repeater parameters adjusted to low MCL + +To function in an environment with a 40 dB MCL the maximum output power in the down-link of the repeater have to be adjusted so that the maximum UE received power does not exceed -25 dBm. This lead to the following set of parameters: + +$P\_max\_DL$ (maximum power down-link) = 15 dBm + +$P\_max\_UL$ (maximum power up-link) = -3 dBm (the difference between UL and DL is kept as in section 5.5.1) + +$G$ (repeater gain, common for both directions) = 72 dB (the gain is given considering the coupling loss to the BSA) + +$NF$ (noise figure) = 5 dB + +With a 15 dBm maximum down-link output power, the down-link interference for UEB due to the UE's Adjacent Channel Selectivity (ACS) can be calculated by using the 33 dB ACS value given in TS 25.101: + +$$I\_UEB = 15 \text{ dBm } (P\_max\_DL) - 40 \text{ dB } (MCL) - 33 \text{ dB } (ACS) = -58 \text{ dBm.}$$ + +This interference level is fairly large and might cause quality degradation or dropped calls, but is a value in the range that can be expected if a UE is in the vicinity of other operators base stations or repeaters. To study the up-link interference generated by the repeaters out of band gain the minimum and maximum UE output is used. Further, the out of band values specified in the repeater core specification TS 25.106 are based on a 90 maximum gain value. By back calculation the Adjacent Channel Rejection Ratio (ACRR) of the filters in the repeater can be calculated to be 37 dB. Hence, if the in-band gain of the repeater is lower compared to the assumed 90 dB the out of band gain will be reduced accordingly. + +If UEB is transmitting at minimum output power the up-link interference at BSB can be calculated as: + +$$I\_BSB = -50 \text{ dBm (P\_min\_UE)} - 40 \text{ dB (MCL)} + 72 \text{ dB (G)} - 37 \text{ dB (ACRR)} - 100 \text{ dB (CL\_BSB-Rep)} = -155 \text{ dBm.}$$ + +This value is very low compared to the thermal noise of the BS and can hence have no impact on the sensitivity. + +To study the case when the UEB is transmitting at maximum output power we first study the power received in the repeaters operating band. This is calculated using the UE ACLR of 33 dB (according to TS 25.101 V3.4.0). In the repeater specification TS 25.106 there are requirements on the Automatic Gain Control (AGC), this functionality ensure that the amplifiers of the repeater is not driven into saturation by lowering the gain if a high input signal is applies. + +Now, with the maximum output power in the repeaters up-link of -3 dBm the reduction of the gain in the operating band can be calculated as: + +$$G = -3 \text{ dBm (P\_max\_UL)} - 21 \text{ dBm (P\_max\_UE)} + 40 \text{ (MCL)} + 33 \text{ (UE ACLR)} = 49 \text{ dB.}$$ + +With this new value of the repeaters gain the up-link interference given as: + +$$I\_BSB = 21 \text{ dBm (P\_max\_UE)} - 40 \text{ dB (MCL)} + 49 \text{ dB (G)} - 37 \text{ dB (ACRR)} - 100 \text{ dB (CL\_BSB-Rep)} = -107 \text{ dBm}$$ + +a value which is 5 dB below the thermal noise floor of the BS resulting in sensitivity degradation of about 1 dB. + +The maximum power from UEA at BSA has been reduced due to impact of UEBs ACLR on the repeater's gain. The resulting value would be: + +$$P\_max\_received\_BSA = 21 \text{ dBm (P\_max\_UE)} - 40 \text{ dB (MCL)} + 49 \text{ dB (G)} - 100 \text{ dB (CL\_BSB-Rep)} = -70 \text{ dBm.}$$ + +However, this value is still far greater than the maximum uplink power can deliver but also a much greater level than what is needed at the BS. Also, with BS reference sensitivity of -121 dBm the resulting transferred sensitivity and the repeater is calculated as: + +$$\text{Sensitivity}_{\text{RepA}} = -121 \text{ dBm (BS sensitivity)} + 100 \text{ dB (CL\_BSB-Rep)} - 49 \text{ dB (G)} = -70 \text{ dBm.}$$ + +The conclusion is that by an adjustment of the repeater parameters to a MCL of 40 dB the co-existence problems are mitigated. However, due to the UE ACLR impact on the repeater gain it is recommended that care be taken so that the installation results in a MCL greater than 40 dB. With a high MCL value the operator can ensure that repeaters coverage area is maintained when UEs from adjacent channels are in the close proximity. + +## 5.6 Analysis of out of band gain in the 3rd adjacent channel + +### 5.6.1 MCL=70 dB + +In this case following parameters are seen to represent a repeater intended for normal applications and typical coupling loss values; + +$$P_{\text{max\_DLrep}} \text{ (maximum power down-link)} = 30 \text{ dBm.}$$ + +$$P_{\text{max\_ULrep}} \text{ (maximum power up-link)} = 12 \text{ dBm (the value can be reduced 18 dB with respect to the Downlink due to the uplink power control mechanism).}$$ + +$$G\_max_{\text{rep}} \text{ (maximum repeater Gain, common for both directions)} = 90 \text{ dB.}$$ + +$$\text{CLBSB-Rep (Coupling loss between repeater and base station B)} = 100 \text{ dB.}$$ + +$$\text{MCLUEB-rep (Mutual Coupling Loss between the repeater and the UEB)} = 70 \text{ dB.}$$ + +$$\text{ACG3rep (Adjacent Channel Gain in the 3rd adjacent channel)} = 35 \text{ dB.}$$ + +ACCR3rep (Adjacent Channel Rejection Ratio in the 3rd adjacent channel) = $G\_maxrepeater - ACG3rep = 55$ dB. + +In addition the following parameters are used in the analysis: + +$P\_maxUEB$ (UEB maximum UL power, operating at a frequency corresponding to the repeaters 3rd adjacent channel) = 21 dBm. + +ACS3UEB (the UE's selectivity in the 3rd adjacent channel) = 52 dB + +$P\_maxBSB$ (BS B maximum DDL power) = 40 dBm. + +#### Up-link interference: + +Under the assumption that the signal amplified by the repeater outside of the operating band is interference, the resulting level at the base station can be calculated as + +$$I\_ULBSB = 21 \text{ dBm } (P\_maxUEB) - 70 \text{ dB } (MCLUEB\text{-rep}) + 90 \text{ dB } (G\_maxrep) - 55 \text{ dB } (ACR3rep) - 100 \text{ dB } (CLBSB\text{-Rep}) = -114 \text{ dBm}.$$ + +#### Down-link interference: + +In the analysis of down-link interference, we compare the interference generated by the repeater's out of band gain (referred to ACG) to that caused by the UE's blocking sensitivity (ACS), where the values have been obtained with back calculations from TS 25.101: + +$$I\_DLUEB (ACG) = 40 \text{ dBm } (P\_maxBSB) - 100 \text{ dB } (CLBSB\text{-Rep}) + 35 \text{ dB } (ACG3rep) - 100 \text{ dB } (CLBSB\text{-Rep}) = -95 \text{ dBm}.$$ + +$$I\_DLUEB (ACS) = 30 \text{ dBm } (Pmax\_DLrep) - 70 \text{ dB } (MCL) - 52 \text{ dB } (ACS3UEB) = -92 \text{ dBm}.$$ + +$$I\_DLUEB (ACG+ACS) = -90,2 \text{ dBm}$$ + +i.e. the additional interference generated by the repeater's out of band gain is 1,8 dB. + +### 5.6.2 MCL=40 dB + +In this case the repeater's output power and gain is adjusted to a 40 dB MCL leading to the following; + +$$Pmax\_DLrep \text{ (maximum power down-link)} = 15 \text{ dBm}.$$ + +$$Pmax\_ULrep \text{ (maximum power up-link)} = -3 \text{ dBm}.$$ + +$$Grep \text{ (Gain, common for both directions)} = 75 \text{ dB}.$$ + +$$CLBSB\text{-Rep} = 100 \text{ dB}.$$ + +$$MCLrep\text{-UEB} = 40 \text{ dB}.$$ + +$$ACG3rep = 75 \text{ dB } (Grep) - 55 \text{ dB } (ACRR3rep) = 20 \text{ dB}.$$ + +In addition the following parameters are used in the analysis: + +$$PmaxUEB \text{ (operating at a frequency corresponding to the repeaters 3rd adjacent channel)} = 21 \text{ dBm}.$$ + +$$ACS3UEB \text{ (the UEs selectivity in the 3rd adjacent channel)} = 52 \text{ dB}$$ + +$$P\_maxBSB = 40 \text{ dBm}.$$ + +#### Up-link interference: + +With a 40 dB MCLrep-UEB the repeater's gain is reduced by the repeater AGC due to the UEB's unwanted emission. The new inband gain level can be calculated as + +$$G\_newrep = -3 \text{ dBm } (Pmax\_ULrep) - -23 \text{ dBm } (Pspur.maxUEB) + 40 \text{ dB } (MCLrep\text{-UEB}) = 60 \text{ dB},$$ + +i.e. a reduction with 15 dB compared to the original settings. + +Using this new inband gain level we calculate the up-link interference as: + +$$I\_ULBSB = 21 \text{ dBm (PmaxUEB)} - 40 \text{ dB (MCLrep-UEB)} + 60 \text{ (G\_newrep)} \\ - 55 \text{ dB (ACCR3rep)} - 100 \text{ dB (CLBSB-Rep)} = -113 \text{ dBm.}$$ + +#### **Down-link interference:** + +$$I\_DLUEB \text{ (ACG)} = 40 \text{ dBm (PmaxBSB)} - 100 \text{ dB (CLBSB-Rep)} + 60 \text{ dB (G\_newrep)} \\ - 55 \text{ dB (ACCR3rep)} - 40 \text{ dB (MCLrep-UEB)} = -95 \text{ dBm.}$$ + +$$I\_DLUEB \text{ (ACS)} = 15 \text{ dBm (Pmax\_DL rep)} - 40 \text{ dB (MCLrep-UEB)} - 52 \text{ dB (ACS3UEB)} \\ = -77 \text{ dBm.}$$ + +$$I\_DLUEB \text{ (ACG+ACS)} = -77 \text{ dBm.}$$ + +As seen the interference caused by the repeater's out of band gain can be neglected compared to that caused by the UE's selectivity. + +# 6 System Simulations and Analysis + +## 6.1 Down-link co-existence simulations + +This section is intended to analyse a co-existence scenario between a UTRA repeaters and UTRA services at adjacent channels. + +Consider two operators (Operator A and B) that have base stations operating at adjacent frequencies located in the vicinity of each other and with equal EIRP. Further, consider also a down link macro scenario where the signal level is insufficient near the border of the cell, and one of the operators (Operator A) places a repeater there to strengthen the signal. + +When there are no ideal filters or amplifiers available, the signal in the repeater will leak into the adjacent channel and causing an area around the repeater site with increased interference in the adjacent frequency. + +The interference on frequency B at the repeater in this scenario consists of four components: + +1. The out of band emission from operator A' base station that is also amplified by the repeaters adjacent channel gain (ACG). +2. The signals from operator B' base station that is amplified by the repeaters ACG. In the analysis this signal is treated as interference. +3. The out of band emission produced by the repeater. +4. The interference caused by the adjacent channel selectivity (ACS) in the receiving mobile. + +Hence, the effect of the three first (1-3) interference components are caused by the repeater' ACG and out of band emission, and the last one by the filter in the mobile station. + +The simulations is based on a macro path loss model describe in TS 25.942 "RF Scenarios". Though this model has its limitations in the vicinity of the transmitter, it indicates how large the outage zone will be. The simulation assumptions are described in the Appendix. The repeater is placed at a distance of 1.5 km with a donor antenna that has LOS conditions to the base station. The coupling loss to the repeater is 100 dB and with 90 dB gain the output power is 33 dBm. + +In the results below the outage zone is defined as the area, where $SIR < -8 \text{ dB}$ . + +![Figure 6.1: A line graph showing Received power (dBm) on the y-axis (from -110 to -40) versus Distance (m) on the x-axis (from 0 to 3000). Three curves are plotted: a dashed black line for P_r,freq A(r), a solid black line for P_r,freq B(r), and a solid red line for I_freq B(r). The dashed line starts at -40 dBm at 0m, dips to a minimum of about -85 dBm at 1200m, and then rises back to -40 dBm at 1500m. The solid black line starts at -40 dBm at 0m and decreases steadily to about -90 dBm at 3000m. The red line starts at -40 dBm at 0m, dips to a minimum of about -105 dBm at 1200m, and then rises back to -40 dBm at 1500m.](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +Figure 6.1: A line graph showing Received power (dBm) on the y-axis (from -110 to -40) versus Distance (m) on the x-axis (from 0 to 3000). Three curves are plotted: a dashed black line for P\_r,freq A(r), a solid black line for P\_r,freq B(r), and a solid red line for I\_freq B(r). The dashed line starts at -40 dBm at 0m, dips to a minimum of about -85 dBm at 1200m, and then rises back to -40 dBm at 1500m. The solid black line starts at -40 dBm at 0m and decreases steadily to about -90 dBm at 3000m. The red line starts at -40 dBm at 0m, dips to a minimum of about -105 dBm at 1200m, and then rises back to -40 dBm at 1500m. + +**Figure 6.1: Simulation on the received average power from a base station on two 5 MHz channels, frequency A and B.** + +In Figure 6.1, the output power is the same for both base stations. $P_{r,freqB}$ represents a signal on frequency B and $P_{r,freqA}$ on frequency A where a repeater is used. $I_{freqB}$ indicates the interference on frequency B that the base station and repeater on frequency A have produced. + +In Figure 6.1 the received signal from the two base stations are shown and also the interference level on operator B' band. The signal-to-interference ratio (SIR) around the repeater site is illustrated in Figure 6.2. The outage zone is defined as the area where the mobile is unable to hold a channel with SIR requirement of -8 dB. The channel gain (CG) in the repeater is 90 dB and ACG is 50 dB. + +The outage zone is 62 m if only interference components 1-2 are considered. If also 3 is applied the outage zone is 67 m. If the effect of the receiver selectivity, ACS, in the mobile is also taken in account the outage zone becomes 103 m. If ACG in the repeater is set to zero the outage zone will get 99 m. + +![Figure 6.2: A line graph showing SIR (dB) on the y-axis (from -20 to 30) versus Distance (m) on the x-axis (from 1300 to 1800). Three lines are plotted: a solid black line for SIR(r), a horizontal red line for SIR required (-8 dB), and a horizontal blue line for Outage zone (103 m). The black line starts at 28 dB at 1300m, decreases to a minimum of -20 dB at 1500m, and then increases to 11 dB at 1800m. The red line is at -8 dB. The blue line is at -10 dB and spans from 1497 m to 1600 m, labeled 'Outage zone'.](58f42a91047786934d8a7e258d581ca2_img.jpg) + +Figure 6.2: A line graph showing SIR (dB) on the y-axis (from -20 to 30) versus Distance (m) on the x-axis (from 1300 to 1800). Three lines are plotted: a solid black line for SIR(r), a horizontal red line for SIR required (-8 dB), and a horizontal blue line for Outage zone (103 m). The black line starts at 28 dB at 1300m, decreases to a minimum of -20 dB at 1500m, and then increases to 11 dB at 1800m. The red line is at -8 dB. The blue line is at -10 dB and spans from 1497 m to 1600 m, labeled 'Outage zone'. + +**Figure 6.2: The figure shows the signal-to-interference (SIR) ratio and the threshold of -8 dB. The outage zone where the SIR drops below this threshold is around 103 m.** + +The outage zone as a function of ACG is shown in Figure 6.2. The results shown in the Figure 6.3 indicate that the impact of ACG on the outage zone is very small up to an ACG of about 55 dB. + +![Figure 6.3: A line graph showing Outage zone (m) on the y-axis (0 to 400) versus Adjacent channel gain (dB) on the x-axis (0 to 90). Three curves are plotted: 'Repeater and mobile impact' (black line), 'Repeater impact' (blue line), and 'ACG=0 dB' (red horizontal line). The black and blue lines start at 100m and 50m respectively at 0 dB ACG and increase sharply after 40 dB ACG. The red line remains constant at 100m.](ebce355620876e10f907f8b71926c112_img.jpg) + +Figure 6.3: A line graph showing Outage zone (m) on the y-axis (0 to 400) versus Adjacent channel gain (dB) on the x-axis (0 to 90). Three curves are plotted: 'Repeater and mobile impact' (black line), 'Repeater impact' (blue line), and 'ACG=0 dB' (red horizontal line). The black and blue lines start at 100m and 50m respectively at 0 dB ACG and increase sharply after 40 dB ACG. The red line remains constant at 100m. + +**Fig. 6. 3: Two cases are studied; one where only the interference impact is generated by the repeater and the other where also the selectivity limit is taken into account in the mobile. The red line shows the outage area with an ACG equal to zero.** + +It is shown with simulations that most interference comes from the selectivity in the receiving mobile, if the repeater in this scenario has a adjacent channel gain that is less than 55 dB. + +## 6.2 Outdoor coverage (High CLRep-UE) + +The repeater is located close to an area with poor signal strength. The link between repeater and Base Station (BS) is assumed to have a minimum Coupling Loss (CL) of 100 dB (Taken from TS 45.050). The minimum coupling loss between the Mobile Station (MS) and the repeater is assumed to be 70 dB (Taken from TS 25.201). The gain in the repeater of 90 dB is assumed to be a really high value, in practice a more realistic value would be less than that. The noise figure (F) of 5 dB in the repeater is the same as for base stations. + +![Figure 6.4: Schematic illustration of the radio link between BS and MS via a Repeater. It shows a Base Station (BS) connected to a Repeater via a coupling loss CL1, and the Repeater connected to a Mobile Station (MS) via a coupling loss CL2. Antennas are shown at each component.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +Figure 6.4: Schematic illustration of the radio link between BS and MS via a Repeater. It shows a Base Station (BS) connected to a Repeater via a coupling loss CL1, and the Repeater connected to a Mobile Station (MS) via a coupling loss CL2. Antennas are shown at each component. + +**Fig. 6.4: Schematic illustration of the radio link between BS and MS via a Repeater.** + +**Table 6.1: Assumed values for the outdoor scenario** + +| Parameter | Value | +|---------------------------------|--------| +| BS output power | 43 dBm | +| Coupling loss BS-Repeater (CL1) | 100 dB | +| Repeater gain | 90 dB | +| Repeater noise figure | 5 dB | +| Coupling loss Repeater-MS (CL2) | 70 | + +**Table 6.2: Analysis of the down-link for the outdoor scenario** + +| Downlink | | TX power | | | | RX power | Comment | +|----------|--|----------|--------|----------------------|--------|----------|-----------------------| +| Max P BS | | +43dBm | -57dBm | +90dB | +33dBm | -37dBm | Max received P=-25dBm | +| Noise | | | | -102dBm 1 | -12dBm | -82dBm | | + +**Table 6.3: Analysis of the up-link for the outdoor scenario** + +| Uplink: | Comment | RX power | | | | TX power | Comment | +|----------|-------------------------|----------|--------|------------------------------------------|---------|----------|---------| +| Min P MS | Below sensitivity level | -130dBm | -30dBm | +90dB | -120dBm | -50dBm | | +| Noise | -101.6dBm 2 | -112dBm | -12dBm | -102dBmError: Reference source not found | | | | + +The received signal strength at the MS after the repeater is below the maximum receiving power. Also the BS can with power control set the MS so the received power at BS is below the sensitivity level. + +## 6.3 Indoor coverage (Low CLRep-UE) + +The repeater is located so it takes the outside received signal and transmits it inside a building, and vice versa. Inside the building it is assumed to have about 40 dB as minimum coupling loss. The 40 dB coupling loss comes from TS 45.050. + +![Schematic illustration of the radio link between BS and MS via a Repeater. The diagram shows a Base Station (BS) on the left with an antenna, connected via a path labeled CL1 to a Repeater in the center. The Repeater has two antennas and is connected via a path labeled CL2 to a Mobile Station (MS) on the right, which also has an antenna. Arrows indicate bidirectional signal flow between the components.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +graph LR + BS[BS] -- CL1 --- Repeater[Repeater] + Repeater -- CL2 --- MS[MS] + +``` + +Schematic illustration of the radio link between BS and MS via a Repeater. The diagram shows a Base Station (BS) on the left with an antenna, connected via a path labeled CL1 to a Repeater in the center. The Repeater has two antennas and is connected via a path labeled CL2 to a Mobile Station (MS) on the right, which also has an antenna. Arrows indicate bidirectional signal flow between the components. + +**Fig. 6.5: Schematic illustration of the radio link between BS and MS via a Repeater.****Table 6.4: Assumed values for the outdoor scenario** + +| Parameter | Value | +|---------------------------------|--------| +| BS output power | 43 dBm | +| Coupling loss BS-Repeater (CL1) | 100 dB | +| Repeater gain | 70 dB | +| Repeater noise figure | 5 dB | +| Coupling loss Repeater-MS (CL2) | 40 dB | + +**Table 6.5: Analysis of the down-link for the outdoor scenario** + +| Downlink | | TX power | | | | RX power | Comment | +|----------|--|----------|--------|----------------------|--------|----------|-----------------------| +| Max P BS | | +43dBm | -57dBm | +70dB | +13dBm | -27dBm | Max received P=-25dBm | +| Noise | | | | -102dBm 3 | -12dBm | -82dBm | | + +1 Generated noise: $10\log(kN_{0B}/1\text{mW})+F=10\log(1.38\text{e-}23*290*5\text{e}6/1\text{e-}3)+5=-102\text{dBm}$ + +2 Total noise: $N_{\text{bs}}+N_{\text{repeater}}=(-102\text{Error: Reference source not found})_{\text{lin}}+(-112)_{\text{lin}}=-101.6\text{dBm}$ + +3 Generated noise: $10\log(kN_{0B}/1\text{mW})+F=10\log(1.38\text{e-}23*290*5\text{e}6/1\text{e-}3)+5=-102\text{dBm}$ + +**Table 6.6: Analysis of the up-link for the indoor scenario** + +| Uplink: | Comment | RX power | | | | TX power | Comment | +|----------------|----------------------|-----------------|--------|------------------------------------------------------------------|--------|-----------------|----------------| +| Min P MS | | -120dBm | -20dBm | +70dB | -90dBm | -50dBm | | +| Noise | -102dBm 4 | -132dBm | -32dBm | - 102dBmErr
or:
Reference
source not
found | | | | + +## 6.4 Repeater up-link co-existence simulations + +### 6.4.1 General + +This section analyses an up-link co-existence scenario between a UTRA repeaters and UTRA services at adjacent channels. Simulations are performed to analyse the effect of the interference generated by the repeater's out of band gain on services at adjacent channel. + +Two scenarios are studied, one where the operator with the repeater deployed (operator A) and the operator at the adjacent carrier (operator B) have co-ordinated base station deployment (using the same sites) and one where the two networks are uncoordinated (using different sites). Both operators have a 3-sector cell planning with 65° antennas. The co-ordinated and uncoordinated scenarios are illustrated in Fig. 6.6 and 6.7, respectively. The out of band gain value used in the simulations corresponds to the value in TS 25.106 for the first adjacent channel gain. + +Since the interference generated by the repeater's out of band gain is relative to the power received in the adjacent channel the interference level will vary with the load in operator B's network. Hence, if operator B has an unloaded network no interference will be generated. Due to this property a scenario is chosen where operator B has a load of 50 simultaneous user per sector using 12.2 kbps services. As a consequence the BS receiver sensitivity will be slightly lowered, compared to the referenced sensitivity, due to inter- and intracell interference. + +To include these effects a 5 dB noise increase have been assumed for all the base stations in operator B's network, thus resulting in a BS sensitivity of about -98 dBm5. Further, all the UE's in the network are connected with 12.2 kbps up-link, and a required $E_b/N_0 = 6,7$ dB. + +Perfect Power Control has been assumed and the up-link interference has been simulated using a Monte-Carlo approach with 1000 snapshots. + +4 Total noise: $N_{\text{bs}} + N_{\text{repeater}} = (-102 \text{ Error: Reference source not found})_{\text{lin}} + (-132)_{\text{lin}} = -102 \text{ dBm}$ + +5 A 5 dB thermal noise figure has been used for the base station. + +![Figure 6.6: A heatmap showing signal strength (dBm) across a 10000m by 9000m area. The x-axis and y-axis are both labeled 'Distance (m)'. A color bar on the right indicates signal strength from -120 dBm (blue) to -30 dBm (red). The map shows a grid of hexagonal cells with various signal levels. Several antenna icons are placed at different locations, and a red '+' symbol labeled 'Rept' is located at approximately (3800, 3500).](45329c7d9aa2bd1290af5b2027f08d7e_img.jpg) + +Figure 6.6: A heatmap showing signal strength (dBm) across a 10000m by 9000m area. The x-axis and y-axis are both labeled 'Distance (m)'. A color bar on the right indicates signal strength from -120 dBm (blue) to -30 dBm (red). The map shows a grid of hexagonal cells with various signal levels. Several antenna icons are placed at different locations, and a red '+' symbol labeled 'Rept' is located at approximately (3800, 3500). + +**Figure 6.6: An illustration of the co-ordinated scenario where the two operators use the same sites and cell planning.** + +In figure 6.6, the repeater is indicated with a red + (positioned @ 3800; 3500 m) and has its service sector directed towards the sector border. The figure also shows the total uplink power in operator B's network. + +![Figure 6.7: A heatmap similar to Figure 6.6, showing signal strength (dBm) across a 10000m by 9000m area. The axes and color bar are identical. This map represents an uncoordinated scenario, showing a different distribution of signal strengths and antenna placements compared to the coordinated scenario in Figure 6.6. A red '+' symbol labeled 'Rept' is also present at approximately (3800, 3500).](a1a474be12b8992842992294b1d18592_img.jpg) + +Figure 6.7: A heatmap similar to Figure 6.6, showing signal strength (dBm) across a 10000m by 9000m area. The axes and color bar are identical. This map represents an uncoordinated scenario, showing a different distribution of signal strengths and antenna placements compared to the coordinated scenario in Figure 6.6. A red '+' symbol labeled 'Rept' is also present at approximately (3800, 3500). + +**Figure 6.7: An illustration of the uncoordinated scenario.** + +In figure 6.7, the repeater's position is indicated with a red + (positioned @ 3800; 3500 m). The figure also shows the total uplink power in operator B's network. + +### 6.4.2 Simulation Assumptions + +The simulation assumptions used in this contribution are presented below in Table 6.7. + +It is important to highlight that Operator A has an unloaded network and hence the additional interference caused by the UEs ACIR on Operator B's up-link is not included in the simulations. + +Furthermore, the downlink is not considered and hence the possibility that UE's are dropped on the downlink due to ACIR from the repeater has not been considered.. + +**Table 6.7: Simulation assumptions** + +| | | +|-------------------------------------------|--------------------------------------| +| Coupling loss, BS-Repeater | 100 dB | +| Minimum Coupling loss UE-Repeater | 70 dB | +| NLOS path loss model for the mobile [2] | $128.1 + 37.6 \cdot \log_{10}(r)$ dB | +| Log-Normal fading; standard deviation | 6 dB | +| Repeater adjacent channel gain | 48 dB | +| Repeater output power | 33 dBm | +| UE antenna gain | 0 dBi | +| UE power range | -50 -- 24 dBm | +| Cell radius | 1 000 m | +| Power Control | Perfect | +| Simulation type | 36 cells; Monte-Carlo; Wrap-around | +| Base station and repeater serving antenna | 65° HBW; 15 dBi | +| Sectors/BS | 3 | + +### 6.4.3 Results + +The results from the simulations are shown in Fig. 6.8 as cumulative distribution functions of the power received at Operator B's base station. + +We find that there are some differences between the co-ordinated and uncoordinated scenarios. The simulations indicate the co-ordinated scenario gives a received power, which on average is about 5 dB greater than the uncoordinated. + +From Fig. 6.8 we find that the received power is less than -110 dBm at the 99% level for the uncoordinated scenario. The corresponding value for the co-ordinated scenario is -107 dBm. + +![Figure 6.8: Cumulative distribution function of the received signal strength at operator Bs base station due to the repeaters out of band gain. The graph plots P(Received signal < Abscissa) on the y-axis (0 to 1) against Received signal strength at BS (dBm) on the x-axis (-150 to -90). Two curves are shown: a dashed line for the 'Coordinated scenario' and a solid blue line for the 'Uncoordinated scenario'. The uncoordinated scenario curve is shifted to the left, indicating better performance (lower signal strength required for the same probability).](c17eaf807acd5faec68da19dd16929be_img.jpg) + +| Scenario | 99% Level (dBm) | +|------------------------|-----------------| +| Uncoordinated scenario | -110 | +| Coordinated scenario | -107 | + +Figure 6.8: Cumulative distribution function of the received signal strength at operator Bs base station due to the repeaters out of band gain. The graph plots P(Received signal < Abscissa) on the y-axis (0 to 1) against Received signal strength at BS (dBm) on the x-axis (-150 to -90). Two curves are shown: a dashed line for the 'Coordinated scenario' and a solid blue line for the 'Uncoordinated scenario'. The uncoordinated scenario curve is shifted to the left, indicating better performance (lower signal strength required for the same probability). + +**Figure 6.8: Cumulative distribution function of the received signal strength at operator Bs base station due to the repeaters out of band gain.** + +Figure 6.8 shows results for both uncoordinated and co-ordinated scenario. The 99% level is -110 dBm and -107 dBm for the uncoordinated and co-ordinated scenario, respectively. + +### 6.4.4 Conclusion + +In the simulations a noise increase of 5 dB due to load was assumed. With the resulting noise level at the base station receiver the additional interference caused by the repeaters out of band gain is 0,3 dB in the uncoordinated scenario and 0,5 dB in the co-ordinated scenario (at the 99% level). + +The simulations further indicate that the repeaters out of band gain have a negligible impact on the receiver sensitivity at a 95 % level, this holds true in both investigated scenarios. + +## 6.5 Repeater ACRR system impact simulations + +### 6.5.1 General + +This section analyses an up-link and down-link co-existence scenario between a UTRA repeaters and UTRA services at adjacent channels. Simulations are performed to analyse the effect of the interference generated by the repeater's adjacent channel rejection ratio on services at adjacent channel. + +Operator A has repeaters deployed (1 per cell) and operator B is using the adjacent channel to operator A . Two scenarios are studied, One where the closest distance between operator B's BS and operator A's repeaters is 288 m, and one where it is 164 m. Both operators have a 3-sector cell planning with 65° antennas. + +### 6.5.2 Simulation Description + +#### 6.5.2.1 Infrastructure + +Two operators have each 24 cells serviced from 8 sites situated as depicted in figure 6.9. + +![Figure 6.9: Infrastructure scenario plot showing Operator A (blue) and Operator B (red) base stations and repeaters. The plot has an x-axis from 0 to 6 and a y-axis from 0 to 3.5. Operator A (blue) uses repeaters, indicated by '+' symbols. Operator B (red) does not use repeaters. Black arrows show repeater antenna directions. Yellow shaded areas indicate service antenna coverage. The base stations are arranged in a grid-like pattern, with Operator A's repeaters positioned between their base stations and Operator B's base stations.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +Figure 6.9: Infrastructure scenario plot showing Operator A (blue) and Operator B (red) base stations and repeaters. The plot has an x-axis from 0 to 6 and a y-axis from 0 to 3.5. Operator A (blue) uses repeaters, indicated by '+' symbols. Operator B (red) does not use repeaters. Black arrows show repeater antenna directions. Yellow shaded areas indicate service antenna coverage. The base stations are arranged in a grid-like pattern, with Operator A's repeaters positioned between their base stations and Operator B's base stations. + +**Figure 6.9: Infrastructure scenario. Operator A (blue) uses repeaters (+ positions). Operator B (red) does not use repeaters. Black arrows show repeater antenna directions. Yellow shade indicate service antenna.** + +The distance closest between operator A base stations and operator B base stations is 288 m. Cell centre distances is 1 km for each operator. + +Operator A uses one repeater per cell. Operator B uses no repeater. The repeaters are placed in the cell centre positions 577 m away from the donor base stations. The distance between the repeaters and operator B base stations is 288 m and 764m respectively. The interference between operators is investigated with different repeater settings with respect to adjacent channel rejection ratio.. + +#### 6.5.2.2 Preparation + +For each snapshot, 960 subscribers per operator (average 40 per cell) are randomly placed with even distribution in the infrastructure. + +The coupling loss (CL) between all subscribers and all infrastructure elements is calculated. The CL model for this is the Macro cell propagation model as described in [1] MCL of 70 dB is applied. During the CL calculation, the subscribers are mirrored on all fringe areas and the minimum CL to each element is considered the actual, creating 100% wrap around. + +The coupling loss between all repeaters and all base stations is calculated using the free space model. + +The antenna models used are measured azimuth patterns for a 65 degree antenna (base station antenna and repeater service antenna) and for a 33 degree antenna (repeater donor antenna). The antenna gain is 16.6 dBi and 20 dBi respectively. + +The repeater gain is set using a noise margin (i.e related to the CL between donor BS and repeater donor port). Adjacent channel gain is calculated for the simulated ACRR. + +The coupling loss from each UE via each repeater to each BS is calculated. (for both systems) + +#### 6.5.2.3 Connection + +The lowest CL from each UE to any BS is considered the path of connection to the network. If there is a path to another BS with a CL within the soft handover margin, it is also added as a connection path. + +The power control is regulated to overcome the coupling loss in the connected path and to meet the SIR target taking the local interference at each element position into concern. + +The coupling loss for paths not representing connection is used to calculate interference. + +#### 6.5.2.4 Iterations + +Interference is calculated separately for the following interference mechanisms: + +Operator A UL: + +- Noise rise (due to traffic in each cell) +- Own subscribers in other cells +- ACLR from B subscribers reaching the BS directly and via repeaters +- Signals from the B subscribers affecting the BS through the ACS (directly and via the repeater adjacent channel gain) +- The noise generated by the repeater (NF). + +Operator A DL: + +- Own cell interference (using orthogonality factor) +- Own interference from other cells +- Signals from B BS affecting the UE ACS (direct path and via repeaters adjacent channel gain) +- ACLR from B BS reaching the UE (direct path and via repeaters) +- BS B adjacent channel noise reaching the UE (direct path and via repeaters) +- Noise generated by the repeaters (NF) + +Operator B UL: + +- Noise rise (due to traffic in each cell) +- Own subscribers in other cells +- ACLR from A subscribers reaching the BS (directly and via repeaters adjacent channel gain) +- Signals from the A subscribers affecting the BS through the ACS (directly and via the repeaters) +- The noise generated by the repeaters (NF). +- The own UE signals amplified (and distorted) by the repeater adjacent channel gain + +Operator B DL: + +- Own cell interference (using orthogonality factor) +- Own interference from other cells +- Signals from A BS affecting the UE ACS (direct path and via repeaters) + +- ACLR from A BS reaching the UE (direct path and via repeater adjacent channel gain) +- BS A adjacent channel noise reaching the UE (direct path and via repeater adjacent channel gain) +- Noise generated by the repeaters (NF) +- The own BS signals amplified (and distorted) by the rpeater adjacent channel gain) + +(descriptions of the interference mechanisms are detailed in [2].) + +The all interference mechanisms for each link are added to form the total interference used in the power control. + +The output power and interference for each element is updated iteratively until the difference in all interference mechanisms for each element is less than the balance criterion between two consecutive iterations. During the iterations the following may happen: + +- If a UE output power exceeds Pmax\_UE , it is disconnected and the call dropped. +- If a UE connection requires more BS power than max\_DL\_power\_per\_sub the UE is disconnected and the call dropped. +- If a BS power exceeds Pmax\_BS, the UE requiring most power from that BS will be disconnected. If this UE is not in SHO the call will be dropped, otherwise the UE will be connected only to the other BS. +- If the repeater power exceeds Pmax\_RepA in either UL or DL, the gain is reduced so that the repeater is not saturated. New coupling loss through the repeater is calculated and new connections are made to be used for the following iterations. The repeater gain is the same for UL and DL in each repeater. A saturated repeater increases its gain when possible due to the input power. (I.e. disconnection of UE may reduce the power allowing more gain.) + +For each snapshot, up to nine repeater settings are run with the same UE distribution in order to compare direct performance differences. + +The number of dropped calls in UL and DL, UE power, BS power UL interference , DL interference and number of UE in SHO for each repeater setting are saved after each snapshot. + +After the number of snapshots is completed, the median values are taken for all snapshots of respective parameter. + +The ACRR definition used in these simulations is the integrated power amplification over the adjacent channel. This definition differs from the out of band gain requirement, currently used where a more narrow bandwidth is used, and peak gain is limited by a mask. Sample measurements made by Allgon indicate that there is a difference of approximately 10 dB between the peak gain due to side band ripple and the integrated power amplification. + +#### 6.5.2.5 Parameters used through out the simulations + +Number of snapshots = 30 + +ballance\_criterion =0.1 dB criterion for completed power setting loop to determine interference levels. + +lognormal\_fading = 10 dB + +UE\_ACLR = 33 dB + +BSA\_ACS = 45 dB + +BSB\_ACS = 45 dB + +BSA\_ACLR = 45 dB + +BSB\_ACLR = 45 dB + +UE\_ACS = 33 dB + +noiseBW = 4096 kHz, Thermal noise = -174 dBm/Hz + +NF\_BSA = 5 dB + +NF\_BSB = 5 dB + +NF\_UL\_RepA = 5 dB + +NF\_DL\_RepA = 5 dB + +NF\_UE = 9 dB + +Pmax\_UE = 21 dBm + +Pmax\_BSA = 43 dBm + +Pmax\_BSB = 43 dBm + +UEA\_ant\_gain = 0 dBi + +UEB\_ant\_gain = 0 dBi + +UL\_Pmax\_RepA = 20 dBm + +DL\_Pmax\_RepA = 33 dBm + +BSA\_adjacent\_noise = -10 dBm (Spurious emissions integrated over one channel BW) + +BSB\_adjacent\_noise = -10 dBm + +SNIR\_A\_traffic = 6.1 dB Signal to noise and interference ratio required for traffic in system A in the UL, after processing gain. + +PG\_A = 25 dB Processing gain for traffic in system A. + +Activity\_factor\_A\_traffic = 0.66 Activity factor for traffic in system A + +A\_Number\_of\_users\_per\_cell = 40 + +SHOM\_A = 3 dB Soft Hand Over Margin for network A. + +Noise\_margin\_A = 10 dB + +A\_max\_DL\_power\_per\_sub = 33 dBm the maximum allocated power from a BS per connection. + +Pilot\_A = 33 dBm CPICH power for all BS in network A + +adminpower\_A = 30 dBm Other administrative power in the BS + +A\_orthogonality\_factor = 0.4 + +DL\_SNIR\_A\_traffic = 7.9 dB Signal to noise and interference ratio required for traffic in system A in the DL. + +SNIR\_B\_traffic = 6.1 dB Signal to noise and interference ratio required for traffic in system B. + +PG\_B = 25 dB Processing gain for traffic in system B. + +Activity\_factor\_B\_traffic = 0.66 Activity factor for traffic in system A + +B\_Number\_of\_users\_per\_cell = 40 + +SHOM\_B = 3 dB Soft HandOver Margin for network B. + +B\_max\_DL\_power\_per\_sub = 33 dBm the maximum allocated power from a BS per connection. + +Pilot\_B = 33 dBm CPICH power for all BS in network B + +adminpower\_B = 30 dBm + +B\_orthogonality\_factor = 0.4 + +DL\_SNIR\_B\_traffic = 7.9 dB Signal to noise and interference ratio required for traffic in system B in the DL. + +Useful\_fraction\_of\_ACG = 0.0 the fraction of signal, amplified through the repeater ACG, that can help interpretation. + +It is thus assumed that all adjacent channel energy is interference. + +### 6.5.3 Results + +#### 6.5.3.1 288 m between repeater A and BSB + +In the Simulations for repeater A to BS B minimum distance of 288 m, made here, 9 cases per 30 snapshots was made. ACRR for each case is shown in table 6.8 below. + +**Table 6.8: ACRR cases for Repeater A to BS B distance of 288 m.** + +| Case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | +|------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| ACRR | 0 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 0 | 4 | 6 | 8 | 22 | 25 | 27 | 37 | 50 | + +The repeater donor coupling loss was 63.1 dB and the repeater gain was set to 53.1 dB. + +![Two scatter plots showing median BS output power (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares).](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +**Operator A, median BS power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | 39,65 | 39,95 | +| 5 | 39,90 | 39,95 | +| 10 | 39,85 | 39,80 | +| 20 | 39,78 | 39,82 | +| 25 | 39,77 | 39,78 | +| 30 | 39,78 | 39,78 | +| 35 | 39,78 | 39,75 | +| 40 | 39,78 | 39,78 | +| 45 | 39,78 | 39,78 | +| 50 | 39,78 | 39,75 | + +**Operator B, median BS power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | 39,70 | 39,70 | +| 5 | 41,45 | 41,75 | +| 10 | 40,70 | 41,70 | +| 20 | 40,20 | 40,20 | +| 25 | 40,00 | 40,00 | +| 30 | 39,90 | 39,90 | +| 35 | 39,85 | 39,85 | +| 40 | 39,85 | 39,85 | +| 45 | 39,85 | 39,85 | +| 50 | 39,85 | 39,85 | + +Two scatter plots showing median BS output power (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares). + +Figure 6.10: Median BS output power, operator A and operator B. + +![Two scatter plots showing median DL interference (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares).](8fd97886a32c3ac7abb08aba9f7f231b_img.jpg) + +**Operator A, median DL interference** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -75,0 | -73,8 | +| 5 | -73,8 | -73,8 | +| 10 | -73,9 | -73,8 | +| 20 | -74,0 | -74,0 | +| 25 | -74,0 | -74,0 | +| 30 | -74,0 | -74,0 | +| 35 | -74,0 | -74,0 | +| 40 | -74,0 | -74,0 | +| 45 | -74,0 | -74,0 | +| 50 | -74,0 | -74,0 | + +**Operator B, median DL interference** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -75,0 | -75,0 | +| 5 | -73,0 | -72,8 | +| 10 | -73,7 | -72,8 | +| 20 | -74,3 | -74,3 | +| 25 | -74,6 | -74,6 | +| 30 | -74,7 | -74,7 | +| 35 | -74,8 | -74,8 | +| 40 | -74,8 | -74,8 | +| 45 | -74,8 | -74,8 | +| 50 | -74,8 | -74,8 | + +Two scatter plots showing median DL interference (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares). + +Figure 6.11: Median DL interference, operator A and operator B. + +![Two scatter plots showing median UL interference (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares).](5e16d3613b74558acc74ff6d7fd75fa9_img.jpg) + +**Operator A, median UL interference** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -99,0 | -98,5 | +| 5 | -98,5 | -98,5 | +| 10 | -98,5 | -98,5 | +| 20 | -98,5 | -98,5 | +| 25 | -98,5 | -98,5 | +| 30 | -98,5 | -98,5 | +| 35 | -98,5 | -98,5 | +| 40 | -98,5 | -98,5 | +| 45 | -98,5 | -98,5 | +| 50 | -98,5 | -98,5 | + +**Operator B, median UL interference** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -99,0 | -99,0 | +| 5 | -98,4 | -98,2 | +| 10 | -98,7 | -98,4 | +| 20 | -98,8 | -98,8 | +| 25 | -98,9 | -98,9 | +| 30 | -99,0 | -99,0 | +| 35 | -99,0 | -99,0 | +| 40 | -99,0 | -99,0 | +| 45 | -99,0 | -99,0 | +| 50 | -99,0 | -99,0 | + +Two scatter plots showing median UL interference (dBm) vs ACRR (dB) for Operator A and Operator B. The plots compare case 1-9 (blue diamonds) and case 10-18 (pink squares). + +Figure 6.12: Median UL interference, operator A and operator B. + +![Two scatter plots showing median UE output power (dBm) vs ACRR (dB) for Operator A and Operator B. The y-axis ranges from -7 to 0 dBm, and the x-axis ranges from 0 to 60 dB. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). For Operator A, most points are around -6 dBm, with case 10-18 starting at -4 dBm at 0 dB ACRR. For Operator B, points are around -4 dBm, with case 10-18 starting at -4.2 dBm at 0 dB ACRR.](5dc5581cd2aad0e683c73b959f637b31_img.jpg) + +**Operator A, median UE power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -6.0 | -4.2 | +| 5 | -6.0 | -6.0 | +| 10 | -6.0 | -6.0 | +| 15 | -6.0 | -6.0 | +| 20 | -6.0 | -6.0 | +| 25 | -6.0 | -6.0 | +| 30 | -6.0 | -6.0 | +| 35 | -6.0 | -6.0 | +| 40 | -6.0 | -6.0 | +| 45 | -6.0 | -6.0 | +| 50 | -6.0 | -6.0 | + +**Operator B, median UE power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -4.2 | -4.2 | +| 5 | -3.8 | -3.8 | +| 10 | -3.8 | -3.8 | +| 15 | -4.0 | -4.0 | +| 20 | -4.0 | -4.0 | +| 25 | -4.2 | -4.2 | +| 30 | -4.2 | -4.2 | +| 35 | -4.2 | -4.2 | +| 40 | -4.2 | -4.2 | +| 45 | -4.2 | -4.2 | +| 50 | -4.2 | -4.2 | + +Two scatter plots showing median UE output power (dBm) vs ACRR (dB) for Operator A and Operator B. The y-axis ranges from -7 to 0 dBm, and the x-axis ranges from 0 to 60 dB. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). For Operator A, most points are around -6 dBm, with case 10-18 starting at -4 dBm at 0 dB ACRR. For Operator B, points are around -4 dBm, with case 10-18 starting at -4.2 dBm at 0 dB ACRR. + +Figure 6.13: Median UE output power, operator A and operator B. + +![Two scatter plots showing the number of soft hand-overs (SHO) vs ACRR (dB) for Operator A and Operator B. The y-axis ranges from 260 to 290, and the x-axis ranges from 0 to 60 dB. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). For Operator A, the number of SHO is relatively constant around 262-266. For Operator B, the number of SHO is higher, around 282-286, with case 10-18 showing more variation.](6fe536731996880570f251da168376cf_img.jpg) + +**Operator A, number of SHO** + +| ACRR (dB) | case 1 - 9 | case 10 - 18 | +|-----------|------------|--------------| +| 0 | 283 | 288 | +| 5 | 262 | 266 | +| 10 | 262 | 266 | +| 15 | 262 | 266 | +| 20 | 262 | 266 | +| 25 | 262 | 266 | +| 30 | 262 | 266 | +| 35 | 262 | 266 | +| 40 | 262 | 266 | +| 45 | 262 | 266 | +| 50 | 262 | 266 | + +**Operator B, number of SHO** + +| ACRR (dB) | case 1 - 9 | case 10 - 18 | +|-----------|------------|--------------| +| 0 | 286 | 282 | +| 5 | 277 | 264 | +| 10 | 277 | 268 | +| 15 | 282 | 272 | +| 20 | 284 | 282 | +| 25 | 285 | 282 | +| 30 | 285 | 282 | +| 35 | 285 | 282 | +| 40 | 285 | 282 | +| 45 | 285 | 282 | +| 50 | 285 | 282 | + +Two scatter plots showing the number of soft hand-overs (SHO) vs ACRR (dB) for Operator A and Operator B. The y-axis ranges from 260 to 290, and the x-axis ranges from 0 to 60 dB. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). For Operator A, the number of SHO is relatively constant around 262-266. For Operator B, the number of SHO is higher, around 282-286, with case 10-18 showing more variation. + +Figure 6.14: Number of soft hand-overs, operator A and operator B. + +![Figure 6.15: Two scatter plots showing network performance metrics against ACRR (dB). The left plot for Operator A shows the number of saturated repeaters, and the right plot for Operator B shows the number of dropped calls due to UL causes. Both plots compare median and max values for cases 1-9 and 10-18.](b9d879f357d5f15fac9ea8585b87d0a2_img.jpg) + +**Operator A, number of saturated repeaters** + +| ACRR (dB) | case 1 - 9, median | case 1 - 9, max | case 10 - 18, median | case 10 - 18, max | +|-----------|--------------------|-----------------|----------------------|-------------------| +| 0 | 0 | 0 | 0 | 0 | +| 5 | 0 | 0 | 0 | 0 | +| 10 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 0 | 0 | +| 20 | 0 | 0 | 0 | 0 | +| 25 | 0 | 0 | 0 | 0 | +| 30 | 0 | 0 | 0 | 0 | +| 35 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 45 | 0 | 0 | 0 | 0 | +| 50 | 0 | 0 | 0 | 0 | + +**Operator B, UL, number of dropped calls** + +| ACRR (dB) | case 1 - 9, median | case 1 - 9, max | case 10 - 18, median | case 10 - 18, max | +|-----------|--------------------|-----------------|----------------------|-------------------| +| 0 | 0 | 0 | 0 | 0 | +| 5 | 0 | 0 | 0 | 0 | +| 10 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 0 | 0 | +| 20 | 0 | 0 | 0 | 0 | +| 25 | 0 | 0 | 0 | 0 | +| 30 | 0 | 0 | 0 | 0 | +| 35 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 45 | 0 | 0 | 0 | 0 | +| 50 | 0 | 0 | 0 | 0 | + +Figure 6.15: Two scatter plots showing network performance metrics against ACRR (dB). The left plot for Operator A shows the number of saturated repeaters, and the right plot for Operator B shows the number of dropped calls due to UL causes. Both plots compare median and max values for cases 1-9 and 10-18. + +**Figure 6.15: Operator A number of saturated repeaters and operator B number of dropped calls due to UL causes. Note that no calls were dropped due to UL causes for operator A.** + +![Figure 6.16: Two scatter plots showing the number of dropped calls due to DL causes for Operator A and Operator B against ACRR (dB). Both plots compare median and max values for cases 1-9 and 10-18.](d94a0100320109c1b9cd75c1054c7b95_img.jpg) + +**Operator A, DL, number of dropped calls** + +| ACRR (dB) | case 1 - 9, median | case 1 - 9, max | case 10 - 18, median | case 10 - 18, max | +|-----------|--------------------|-----------------|----------------------|-------------------| +| 0 | 1 | 3 | 0 | 0 | +| 5 | 1 | 4 | 0 | 0 | +| 10 | 1 | 4 | 0 | 0 | +| 15 | 1 | 4 | 0 | 0 | +| 20 | 0 | 2 | 0 | 0 | +| 25 | 0 | 2 | 0 | 0 | +| 30 | 0 | 2 | 0 | 0 | +| 35 | 0 | 2 | 0 | 0 | +| 40 | 0 | 2 | 0 | 0 | +| 45 | 0 | 2 | 0 | 0 | +| 50 | 0 | 2 | 0 | 0 | + +**Operator B, DL, number of dropped calls** + +| ACRR (dB) | case 1 - 9, median | case 1 - 9, max | case 10 - 18, median | case 10 - 18, max | +|-----------|--------------------|-----------------|----------------------|-------------------| +| 0 | 0 | 0 | 0 | 0 | +| 5 | 0 | 0 | 0 | 0 | +| 10 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 0 | 0 | +| 20 | 0 | 0 | 0 | 0 | +| 25 | 0 | 0 | 0 | 0 | +| 30 | 0 | 0 | 0 | 0 | +| 35 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 45 | 0 | 0 | 0 | 0 | +| 50 | 0 | 0 | 0 | 0 | + +Figure 6.16: Two scatter plots showing the number of dropped calls due to DL causes for Operator A and Operator B against ACRR (dB). Both plots compare median and max values for cases 1-9 and 10-18. + +**Figure 6.16: Number of dropped calls due to DL causes, operator A and operator B.** + +The following figures show the positions of the dropped calls subscribers in the last snapshot of a simulation. Note that the subscriber distribution in case 1 to 9 is not the same as in case 10 to 18. However repeaters are off in both case 1, in case 10 for comparison. + +Operator A subscribers are shown as blue dots. + +Operator B subscribers are shown as red dots. + +Dropped calls are shown as follows: + +Red – operator B, DL related dropped call + +Magenta – operator B, UL related dropped call + +Blue – operator A, DL related dropped call + +Cyan – operator A, UL related dropped call + +![Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 2D area. The x-axis ranges from 0 to 6, and the y-axis ranges from 0 to 3.5. The dots are densely packed and appear to be randomly distributed throughout the area.](8f38356601e137ac471fc4771b9c5a5c_img.jpg) + +Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 2D area. The x-axis ranges from 0 to 6, and the y-axis ranges from 0 to 3.5. The dots are densely packed and appear to be randomly distributed throughout the area. + +Figure 6.17: Subscriber distribution for operator A and operator B in the last snapshot, case 1 to 9. + +![Scatter plot titled 'Dropped calls' showing the locations of dropped calls for operator A (red) and operator B (blue) in case 1. The x-axis and y-axis both represent distance in km, ranging from 0 to 6. The plot shows several clusters of dropped calls, with vertical lines indicating the distance between the last successful call and the dropped call for each operator. A legend at the bottom identifies the symbols: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg) + +Dropped calls + +ADL - b, AUL - c, BDL - r, BUL - m + +Scatter plot titled 'Dropped calls' showing the locations of dropped calls for operator A (red) and operator B (blue) in case 1. The x-axis and y-axis both represent distance in km, ranging from 0 to 6. The plot shows several clusters of dropped calls, with vertical lines indicating the distance between the last successful call and the dropped call for each operator. A legend at the bottom identifies the symbols: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.18: dropped calls for operator A and operator B in case 1. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (green).](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)" and range from 0 to 6. The plot contains numerous data points and vector arrows representing signal directions. The points are color-coded and grouped into four categories: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , and $B_U L - m$ . The points are distributed across a hexagonal cell layout. The legend is located at the bottom of the plot area. + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (green). + +**Figure 6.19: dropped calls for operator A and operator B in case 2.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (green).](4349d5e2b079af7d2e45e10a3b8235e9_img.jpg) + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.19. The x-axis and y-axis both represent "distance (km)" from 0 to 6. The data points are categorized into four groups: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , and $B_U L - m$ . The distribution of points is similar to Figure 6.19, but with variations in the specific locations of dropped calls (red dots). The legend is positioned at the bottom of the plot. + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (green). + +**Figure 6.20: dropped calls for operator A and operator B in case 3.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (black).](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)" and range from 0 to 6. The plot contains numerous data points, each consisting of a central marker surrounded by four smaller markers, with lines connecting them. The data is categorized into four series: $A_D L - b$ (red), $A_U L - c$ (blue), $B_D L - r$ (yellow), and $B_U L - m$ (black). The points are distributed across the plot, with a higher density of red and blue points at distances of approximately 1, 2.5, 4, and 5.5 km on the x-axis. + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (black). + +Figure 6.21: dropped calls for operator A and operator B in case 4. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (black).](fd38170a3981416226ab91f7437ba821_img.jpg) + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.21. It shows "distance (km)" on both axes from 0 to 6. The data points are categorized into four series: $A_D L - b$ (red), $A_U L - c$ (blue), $B_D L - r$ (yellow), and $B_U L - m$ (black). The distribution of points is similar to Figure 6.21, with clusters of red and blue points at similar x-axis distances (1, 2.5, 4, 5.5 km). + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (black). + +Figure 6.22: dropped calls for operator A and operator B in case 5. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (black).](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (black). + +**Figure 6.23: dropped calls for operator A and operator B in case 6.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (blue), B_D L - r (yellow), and B_U L - m (black).](0aa15f5c9c3edae230985491199cfe8b_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (blue), B\_D L - r (yellow), and B\_U L - m (black). + +**Figure 6.24: dropped calls for operator A and operator B in case 7.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg) + +Dropped calls + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)" and range from 0 to 6. The plot contains four data series represented by colored arrows and markers at regular grid intervals: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , and $B_U L - m$ . The legend at the bottom of the plot lists the four series: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +**Figure 6.25: dropped calls for operator A and operator B in case 8.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](455c842681aadb4969bd61d71f556744_img.jpg) + +Dropped calls + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.25. It plots "distance (km)" on both axes from 0 to 6. The data series are $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , and $B_U L - m$ . The distribution of points and vectors is similar to the previous figure, showing a repeating pattern of clusters at specific distance intervals representing a cellular network layout. + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +**Figure 6.26: dropped calls for operator A and operator B in case 9.** + +![Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 2D area. The x-axis ranges from 0 to 6, and the y-axis ranges from 0 to 3.5. The points are densely packed and appear to be randomly distributed.](cfc852835f2d91bea8dc074568937e22_img.jpg) + +Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 2D area. The x-axis ranges from 0 to 6, and the y-axis ranges from 0 to 3.5. The points are densely packed and appear to be randomly distributed. + +Figure 6.27: Subscriber distribution for operator A and operator B in snapshot 30 case 10 to 18. + +![Scatter plot titled 'Dropped calls' showing call drops for operator A (red) and operator B (blue) in case 10. The x-axis and y-axis both represent distance in km, ranging from 0 to 6. Data points are marked with error bars and arrows indicating direction. A legend at the bottom identifies the series: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](809eec371620084c4b949c66d5d7bae0_img.jpg) + +Scatter plot titled 'Dropped calls' showing call drops for operator A (red) and operator B (blue) in case 10. The x-axis and y-axis both represent distance in km, ranging from 0 to 6. Data points are marked with error bars and arrows indicating direction. A legend at the bottom identifies the series: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.28: dropped calls for operator A and operator B in case 10. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)". The x-axis ranges from 0 to 6, and the y-axis ranges from 0 to 3. The plot shows a regular hexagonal pattern of base station sites. At each site, there are directional arrows (blue, red, yellow) pointing outwards. Small colored dots (red, magenta) are scattered throughout the area, representing dropped call locations. Below the plot, a legend identifies the categories: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +Figure 6.29: dropped calls for operator A and operator B in case 11. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](74448f9178da618d823e5a5dadc56fb5_img.jpg) + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.29. It features the same axes (distance in km) and the same hexagonal grid layout. The distribution of dropped call dots (red and magenta) varies slightly from Figure 6.29, representing data for case 12. The legend below the plot remains the same: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +Figure 6.30: dropped calls for operator A and operator B in case 12. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (yellow), B_D L - r (blue), and B_U L - m (green).](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)" and range from 0 to 6. The plot contains numerous data points, each represented by a small colored dot with a crosshair. The colors correspond to different call types: red for $A_D L - b$ , yellow for $A_U L - c$ , blue for $B_D L - r$ , and green for $B_U L - m$ . The points are distributed across the plot, with a higher density of points at distances of approximately 1, 2, 3, 4, and 5 km on the x-axis. The legend at the bottom of the plot reads: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (yellow), B\_D L - r (blue), and B\_U L - m (green). + +Figure 6.31: dropped calls for operator A and operator B in case 13. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A_D L - b (red), A_U L - c (yellow), B_D L - r (blue), and B_U L - m (green).](d49bc18ad8867b97bbb9aa580449a641_img.jpg) + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.31. The x-axis and y-axis both represent "distance (km)" from 0 to 6. The data points are categorized by operator and call type: $A_D L - b$ (red), $A_U L - c$ (yellow), $B_D L - r$ (blue), and $B_U L - m$ (green). The distribution of points is similar to Figure 6.31, with clusters of points at x-axis distances of 1, 2, 3, 4, and 5 km. The legend at the bottom reads: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. Data points are categorized by operator and call type: A\_D L - b (red), A\_U L - c (yellow), B\_D L - r (blue), and B\_U L - m (green). + +Figure 6.32: dropped calls for operator A and operator B in case 14. + +![Scatter plot titled 'Dropped calls' for case 15, showing distance (km) on both axes from 0 to 6. Data points are represented by colored symbols: red arrows pointing down, blue stars, yellow arrows pointing up, and black arrows pointing diagonally. A legend at the bottom identifies the series as A_D L - b, A_U L - c, B_D L - r, B_U L - m.](a85105fd544c64ef624aa45c72378647_img.jpg) + +The figure is a scatter plot titled "Dropped calls". Both the x-axis and y-axis are labeled "distance (km)" and range from 0 to 6. The plot displays data points for four categories: $A_D L - b$ (red), $A_U L - c$ (blue), $B_D L - r$ (yellow), and $B_U L - m$ (black). The points are arranged in a hexagonal grid pattern across the plot area. The legend $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ is located at the bottom of the plot area. + +Scatter plot titled 'Dropped calls' for case 15, showing distance (km) on both axes from 0 to 6. Data points are represented by colored symbols: red arrows pointing down, blue stars, yellow arrows pointing up, and black arrows pointing diagonally. A legend at the bottom identifies the series as A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.33: dropped calls for operator A and operator B in case 15. + +![Scatter plot titled 'Dropped calls' for case 16, showing distance (km) on both axes from 0 to 6. The plot structure and data point symbols are identical to Figure 6.33, showing a hexagonal distribution of red, blue, yellow, and black symbols.](b30a71a63c0093c8f54a2a57b1f601bb_img.jpg) + +This figure is a scatter plot titled "Dropped calls", identical in structure to Figure 6.33. It shows distance (km) on both axes (0 to 6) with data points for $A_D L - b$ (red), $A_U L - c$ (blue), $B_D L - r$ (yellow), and $B_U L - m$ (black). The distribution of points follows the same hexagonal grid pattern as in case 15. The legend $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ is at the bottom. + +Scatter plot titled 'Dropped calls' for case 16, showing distance (km) on both axes from 0 to 6. The plot structure and data point symbols are identical to Figure 6.33, showing a hexagonal distribution of red, blue, yellow, and black symbols. + +Figure 6.34: dropped calls for operator A and operator B in case 16. + +![Figure 6.35: dropped calls for operator A and operator B in case 17. The plot shows a grid of cell sites with arrows indicating dropped call directions. Axes are distance (km) from 0 to 6.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +Dropped calls + +Legend: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Figure 6.35: dropped calls for operator A and operator B in case 17. The plot shows a grid of cell sites with arrows indicating dropped call directions. Axes are distance (km) from 0 to 6. + +**Figure 6.35: dropped calls for operator A and operator B in case 17.** + +![Figure 6.36: dropped calls for operator A and operator B in case 18. The plot shows a grid of cell sites with arrows indicating dropped call directions. Axes are distance (km) from 0 to 6.](198d076da025c516aec8122a6ab7db20_img.jpg) + +Dropped calls + +Legend: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Figure 6.36: dropped calls for operator A and operator B in case 18. The plot shows a grid of cell sites with arrows indicating dropped call directions. Axes are distance (km) from 0 to 6. + +**Figure 6.36: dropped calls for operator A and operator B in case 18.** + +#### 6.5.3.2 164 m minimum distance between repeater A and BSB + +In the Simulations for repeater A to BS B minimum distance of 164 m, made here, 9 cases per 30 snapshots was made. ACRR for each case is shown in table 6.9 below. + +**Table 6.9: ACRR cases for Repeater A to BS B distance of 164 m.** + +| | | | | | | | | | | | | | | | | | | | +|------|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | +| ACRR | 0 | 4 | 6 | 8 | 22 | 25 | 27 | 37 | 50 | 0 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | + +The repeater donor coupling loss was 61 dB and the repeater gain was set to 51 dB. + +![Figure 6.37: Median BS output power for operator A and operator B. Two scatter plots showing median BS output power (dBm) vs ACRR (dB). Operator A's power is relatively stable around 39.7 dBm, while Operator B's power decreases as ACRR increases.](e046996962d6740cf050a5640e0c6b40_img.jpg) + +**Operator A, median BS power** + +| ACRR (dB) | Case | median BS output power (dBm) | +|-----------|------|------------------------------| +| 0 | 1 | 39.70 | +| 4 | 2 | 39.85 | +| 6 | 3 | 39.83 | +| 8 | 4 | 39.81 | +| 22 | 5 | 39.73 | +| 25 | 6 | 39.75 | +| 27 | 7 | 39.70 | +| 37 | 8 | 39.70 | +| 50 | 9 | 39.70 | +| 0 | 10 | 39.58 | +| 10 | 11 | 39.73 | +| 15 | 12 | 39.69 | +| 20 | 13 | 39.62 | +| 25 | 14 | 39.61 | +| 30 | 15 | 39.60 | +| 35 | 16 | 39.60 | +| 40 | 17 | 39.60 | +| 45 | 18 | 39.60 | + +**Operator B, median BS power** + +| ACRR (dB) | Case | median BS output power (dBm) | +|-----------|------|------------------------------| +| 0 | 1 | 39.70 | +| 4 | 2 | 41.10 | +| 6 | 3 | 41.30 | +| 8 | 4 | 41.50 | +| 22 | 5 | 40.20 | +| 25 | 6 | 40.10 | +| 27 | 7 | 40.00 | +| 37 | 8 | 39.90 | +| 50 | 9 | 39.85 | +| 0 | 10 | 39.70 | +| 10 | 11 | 40.70 | +| 15 | 12 | 40.20 | +| 20 | 13 | 40.00 | +| 25 | 14 | 39.90 | +| 30 | 15 | 39.85 | +| 35 | 16 | 39.85 | +| 40 | 17 | 39.85 | +| 45 | 18 | 39.85 | + +Figure 6.37: Median BS output power for operator A and operator B. Two scatter plots showing median BS output power (dBm) vs ACRR (dB). Operator A's power is relatively stable around 39.7 dBm, while Operator B's power decreases as ACRR increases. + +**Figure 6.37: Median BS output power for operator A and operator B.** + +![Figure 6.38: Median DL interference for operator A and operator B. Two scatter plots showing median DL interference (dBm) vs ACRR (dB). Operator A's interference is relatively stable around -74.8 dBm, while Operator B's interference decreases as ACRR increases.](52f284e10be4323639b32fdd60e463db_img.jpg) + +**Operator A, median DL interference** + +| ACRR (dB) | Case | median DL interference (dBm) | +|-----------|------|------------------------------| +| 0 | 1 | -74.80 | +| 4 | 2 | -73.80 | +| 6 | 3 | -73.70 | +| 8 | 4 | -73.60 | +| 22 | 5 | -74.00 | +| 25 | 6 | -74.00 | +| 27 | 7 | -74.10 | +| 37 | 8 | -74.10 | +| 50 | 9 | -74.10 | +| 0 | 10 | -74.80 | +| 10 | 11 | -74.00 | +| 15 | 12 | -74.10 | +| 20 | 13 | -74.10 | +| 25 | 14 | -74.10 | +| 30 | 15 | -74.10 | +| 35 | 16 | -74.10 | +| 40 | 17 | -74.10 | +| 45 | 18 | -74.10 | + +**Operator B, median DL interference** + +| ACRR (dB) | Case | median DL interference (dBm) | +|-----------|------|------------------------------| +| 0 | 1 | -74.80 | +| 4 | 2 | -73.20 | +| 6 | 3 | -73.00 | +| 8 | 4 | -72.80 | +| 22 | 5 | -74.20 | +| 25 | 6 | -74.30 | +| 27 | 7 | -74.40 | +| 37 | 8 | -74.60 | +| 50 | 9 | -74.70 | +| 0 | 10 | -74.80 | +| 10 | 11 | -73.80 | +| 15 | 12 | -73.60 | +| 20 | 13 | -74.30 | +| 25 | 14 | -74.50 | +| 30 | 15 | -74.60 | +| 35 | 16 | -74.60 | +| 40 | 17 | -74.60 | +| 45 | 18 | -74.60 | + +Figure 6.38: Median DL interference for operator A and operator B. Two scatter plots showing median DL interference (dBm) vs ACRR (dB). Operator A's interference is relatively stable around -74.8 dBm, while Operator B's interference decreases as ACRR increases. + +**Figure 6.38: Median DL interference for operator A and operator B.** + +![Two scatter plots showing median UL interference for Operator A and Operator B across different ACRR values. The y-axis represents UL interference in dBm, ranging from -99.1 to -98.4. The x-axis represents ACRR in dBm, with 0 representing 'off'. Data points are shown for Case 1-9 (blue diamonds) and Case 10-18 (pink squares).](068b3a3247570c4b78342a943f15de9e_img.jpg) + +**Operator A, median UL interference** + +| ACRR (dBm) | Case 1 - 9 (dBm) | Case 10 - 18 (dBm) | +|------------|------------------|--------------------| +| 0 | -98.5 | -99.0 | +| 5 | -98.5 | -98.5 | +| 10 | -98.5 | -98.5 | +| 15 | -98.5 | -98.5 | +| 20 | -98.5 | -98.5 | +| 25 | -98.5 | -98.5 | +| 30 | -98.5 | -98.5 | +| 35 | -98.5 | -98.5 | +| 40 | -98.5 | -98.5 | +| 45 | -98.5 | -98.5 | +| 50 | -98.5 | -98.5 | +| 55 | -98.5 | -98.5 | +| 60 | -98.5 | -98.5 | + +**Operator B, median UL interference** + +| ACRR (dBm) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|------------|------------------|--------------------| +| 0 | -99.0 | -99.0 | +| 5 | -98.4 | -98.5 | +| 10 | -98.4 | -98.5 | +| 15 | -98.4 | -98.7 | +| 20 | -98.5 | -98.7 | +| 25 | -98.8 | -98.8 | +| 30 | -98.9 | -98.9 | +| 35 | -98.9 | -99.0 | +| 40 | -99.0 | -99.0 | +| 45 | -99.0 | -99.0 | +| 50 | -99.0 | -99.0 | +| 55 | -99.0 | -99.0 | +| 60 | -99.0 | -99.0 | + +Two scatter plots showing median UL interference for Operator A and Operator B across different ACRR values. The y-axis represents UL interference in dBm, ranging from -99.1 to -98.4. The x-axis represents ACRR in dBm, with 0 representing 'off'. Data points are shown for Case 1-9 (blue diamonds) and Case 10-18 (pink squares). + +Figure 6.39: Median UL interference for operator A and operator B. + +![Two scatter plots showing median UE output power for Operator A and Operator B across different ACRR values. The y-axis represents median UE output power in dBm, ranging from -7 to 0. The x-axis represents ACRR in dB, with 0 representing 'off'. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares).](a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg) + +**Operator A, median UE power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -4.5 | -4.5 | +| 5 | -5.5 | -5.5 | +| 10 | -5.5 | -5.5 | +| 15 | -5.5 | -5.5 | +| 20 | -5.5 | -5.5 | +| 25 | -5.5 | -5.5 | +| 30 | -5.5 | -5.5 | +| 35 | -5.5 | -5.5 | +| 40 | -5.5 | -5.5 | +| 45 | -5.5 | -5.5 | +| 50 | -5.5 | -5.5 | +| 55 | -5.5 | -5.5 | +| 60 | -5.5 | -5.5 | + +**Operator B, median UE power** + +| ACRR (dB) | case 1 - 9 (dBm) | case 10 - 18 (dBm) | +|-----------|------------------|--------------------| +| 0 | -4.5 | -4.5 | +| 5 | -4.0 | -4.0 | +| 10 | -4.0 | -4.0 | +| 15 | -4.0 | -4.0 | +| 20 | -4.0 | -4.0 | +| 25 | -4.0 | -4.0 | +| 30 | -4.0 | -4.0 | +| 35 | -4.0 | -4.0 | +| 40 | -4.0 | -4.0 | +| 45 | -4.0 | -4.0 | +| 50 | -4.0 | -4.0 | +| 55 | -4.0 | -4.0 | +| 60 | -4.0 | -4.0 | + +Two scatter plots showing median UE output power for Operator A and Operator B across different ACRR values. The y-axis represents median UE output power in dBm, ranging from -7 to 0. The x-axis represents ACRR in dB, with 0 representing 'off'. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). + +Figure 6.40: Median UE output power for operator A and operator B. + +![Two scatter plots showing the median number of SHO for Operator A and Operator B across different ACRR values. The y-axis represents the median number of SHO, ranging from 260 to 290. The x-axis represents ACRR in dB, with 0 representing 'off'. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares).](930335a43c8196e391f87e6860db4d45_img.jpg) + +**Operator A, median number of SHO** + +| ACRR (dB) | case 1 - 9 | case 10 - 18 | +|-----------|------------|--------------| +| 0 | 288 | 282 | +| 5 | 266 | 266 | +| 10 | 266 | 266 | +| 15 | 266 | 266 | +| 20 | 266 | 266 | +| 25 | 266 | 266 | +| 30 | 266 | 266 | +| 35 | 266 | 266 | +| 40 | 266 | 266 | +| 45 | 266 | 266 | +| 50 | 266 | 266 | +| 55 | 266 | 266 | +| 60 | 266 | 266 | + +**Operator B, median number of SHO** + +| ACRR (dB) | case 1 - 9 | case 10 - 18 | +|-----------|------------|--------------| +| 0 | 282 | 285 | +| 5 | 268 | 268 | +| 10 | 273 | 277 | +| 15 | 270 | 281 | +| 20 | 282 | 283 | +| 25 | 282 | 284 | +| 30 | 282 | 284 | +| 35 | 282 | 284 | +| 40 | 282 | 285 | +| 45 | 282 | 285 | +| 50 | 282 | 285 | +| 55 | 282 | 285 | +| 60 | 282 | 285 | + +Two scatter plots showing the median number of SHO for Operator A and Operator B across different ACRR values. The y-axis represents the median number of SHO, ranging from 260 to 290. The x-axis represents ACRR in dB, with 0 representing 'off'. Data points are shown for case 1-9 (blue diamonds) and case 10-18 (pink squares). + +**Figure 6.41: Median number of soft hand-overs for operator A and operator B.** + +![Figure 6.41: Two line graphs showing the median number of saturated repeaters and dropped calls for Operator B against ACRR (dB).](d6d2d323ed8fdca4c18f226f9ba3f480_img.jpg) + +The figure consists of two line graphs. The left graph, titled "number of saturated repeaters", shows the number of saturated repeaters (y-axis, 0 to 10) against ACRR (dB) (x-axis, 0 to 60). The right graph, titled "Operator B, UL, number of dropped calls", shows the number of dropped calls (y-axis, 0 to 6) against ACRR (dB) (x-axis, 0 to 60). Both graphs include data for case 1-9 (median and max) and case 10-18 (median and max). In the left graph, case 1-9 max is around 8, case 10-18 max is around 8, case 1-9 median is around 4, and case 10-18 median is around 0. In the right graph, case 1-9 max is around 5, case 10-18 max is around 1, case 1-9 median is around 0, and case 10-18 median is around 0. + +Figure 6.41: Two line graphs showing the median number of saturated repeaters and dropped calls for Operator B against ACRR (dB). + +**Figure 6.42: Number of saturated repeaters for operator A and number of dropped calls due to UL causes for operator B. Note that no calls were dropped due to UL causes for operator A.** + +![Figure 6.42: Two line graphs showing the number of dropped calls due to DL causes for Operator A and Operator B against ACRR (dB).](48fc91e19c1a9b6674b120fbdd89b203_img.jpg) + +The figure consists of two line graphs. The left graph, titled "Operator A, DL, number of dropped calls", shows the number of dropped calls (y-axis, 0 to 2.5) against ACRR (dB) (x-axis, 0 to 60). The right graph, titled "Operator B, DL, number of dropped calls", shows the number of dropped calls (y-axis, 0 to 60) against ACRR (dB) (x-axis, 0 to 60). Both graphs include data for case 1-9 (median and max) and case 10-18 (median and max). In the left graph, case 1-9 max is around 2, case 10-18 max is around 2, case 1-9 median is around 0.5, and case 10-18 median is around 0. In the right graph, case 1-9 max is around 55, case 10-18 max is around 15, case 1-9 median is around 40, and case 10-18 median is around 5. + +Figure 6.42: Two line graphs showing the number of dropped calls due to DL causes for Operator A and Operator B against ACRR (dB). + +**Figure 6.43: Number of dropped calls due to DL causes for operator A and operator B.** + +The following figures show the positions of the dropped calls subscribers in the last snapshot of a simulation. Note that the subscriber distribution in case 1 to 9 is not the same as in case 10 to 18. However repeaters are off in both case 1, in case 10 for comparison. + +Operator A subscribers are shown as blue dots. + +Operator B subscribers are shown as red dots. + +Dropped calls are shown as follows: + +Red – operator B, DL related dropped call + +Magenta – operator B, UL related dropped call + +Blue – operator A, DL related dropped call + +Cyan – operator A, UL related dropped call + +![Scatter plot showing subscriber distribution for operator A and operator B. The x-axis represents distance in km from 0 to 6, and the y-axis represents distance in km from 0 to 3.5. The plot is filled with numerous red and blue dots representing individual subscribers.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +Scatter plot showing subscriber distribution for operator A and operator B. The x-axis represents distance in km from 0 to 6, and the y-axis represents distance in km from 0 to 3.5. The plot is filled with numerous red and blue dots representing individual subscribers. + +Figure 6.44: Subscriber distribution of the last snapshot for operator A and operator B in case 1 to 9. + +![Scatter plot titled 'Dropped calls' showing call drops for operator A and operator B. The x-axis and y-axis both represent distance in km, ranging from 0 to 6 and 0 to 3.5 respectively. Data points are marked with yellow, red, and blue crosses, each accompanied by error bars. The legend at the bottom indicates: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](e01f9228a215e26c8b62ad471c9d7a7f_img.jpg) + +Dropped calls + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing call drops for operator A and operator B. The x-axis and y-axis both represent distance in km, ranging from 0 to 6 and 0 to 3.5 respectively. Data points are marked with yellow, red, and blue crosses, each accompanied by error bars. The legend at the bottom indicates: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.45: Dropped calls for operator A and operator B in case 1 – repeater is off. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 2 with ACRR = 4 dB. The plot shows various data points with error bars and arrows indicating movement or direction.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot contains several data points, each with error bars and arrows pointing in various directions. The data points are categorized by operator and case, as indicated by the legend: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ . The legend is located at the bottom of the plot area. + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 2 with ACRR = 4 dB. The plot shows various data points with error bars and arrows indicating movement or direction. + +Figure 6.46: Dropped calls for operator A and operator B in case 2 – ACRR = 4 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 3 with ACRR = 6 dB. The plot shows various data points with error bars and arrows indicating movement or direction.](73e5c1369b67ddccf657e54d0434cc2b_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot contains several data points, each with error bars and arrows pointing in various directions. The data points are categorized by operator and case, as indicated by the legend: $A_D L - b$ , $A_U L - c$ , $B_D L - r$ , $B_U L - m$ . The legend is located at the bottom of the plot area. + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 3 with ACRR = 6 dB. The plot shows various data points with error bars and arrows indicating movement or direction. + +Figure 6.47: Dropped calls for operator A and operator B in case 3 – ACRR = 6 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 4 with ACRR = 8 dB. The plot shows several clusters of data points with error bars, representing dropped calls for different operators and cases.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 4 with ACRR = 8 dB. The plot shows several clusters of data points with error bars, representing dropped calls for different operators and cases. + +Figure 6.48: Dropped calls for operator A and operator B in case 4 – ACRR = 8 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 5 with ACRR = 22 dB. The plot shows several clusters of data points with error bars, representing dropped calls for different operators and cases.](8a4275b35551f2ec9825a1aa442c0db1_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 5 with ACRR = 22 dB. The plot shows several clusters of data points with error bars, representing dropped calls for different operators and cases. + +Figure 6.49: Dropped calls for operator A and operator B in case 5 – ACRR = 22 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered at various locations, marked with red, blue, and yellow symbols. A legend below the plot identifies the symbols: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered at various locations, marked with red, blue, and yellow symbols. A legend below the plot identifies the symbols: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.50: Dropped calls for operator A and operator B in case 6 – ACRR = 25 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered at various locations, marked with red, blue, and yellow symbols. A legend below the plot identifies the symbols: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered at various locations, marked with red, blue, and yellow symbols. A legend below the plot identifies the symbols: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.51: Dropped calls for operator A and operator B in case 7 – ACRR = 27 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 8 with ACRR = 37 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operators and cases.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot contains several clusters of data points, each with vertical error bars. The clusters are located at approximately (0.8, 0.8), (0.8, 1.1), (0.8, 2.5), (2.3, 0.2), (2.3, 1.7), (2.3, 3.3), (3.8, 0.8), (3.8, 1.1), (3.8, 2.5), (5.3, 0.2), (5.3, 1.7), (5.3, 2.0), and (5.3, 3.3). Below the x-axis, there is a legend: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 8 with ACRR = 37 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operators and cases. + +Figure 6.52: Dropped calls for operator A and operator B in case 8 – ACRR = 37 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 9 with ACRR = 50 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operators and cases.](a96c7e19f53f2350db97a90738a6fb51_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot contains several clusters of data points, each with vertical error bars. The clusters are located at approximately (0.8, 0.8), (0.8, 1.1), (0.8, 2.5), (2.3, 0.2), (2.3, 1.7), (2.3, 3.3), (3.8, 0.8), (3.8, 1.1), (3.8, 2.5), (5.3, 0.2), (5.3, 1.7), (5.3, 2.0), and (5.3, 3.3). Below the x-axis, there is a legend: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 9 with ACRR = 50 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operators and cases. + +Figure 6.53: Dropped calls for operator A and operator B in case 9 – ACRR = 50 dB. + +![Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 6x3.5 km area.](6752cee124f693bc4cebc66180f4f91f_img.jpg) + +A scatter plot showing the distribution of subscribers for two operators, A and B, in a 2D plane. The x-axis represents distance in km, ranging from 0 to 6. The y-axis represents distance in km, ranging from 0 to 3.5. Red dots represent subscribers for operator A, and blue dots represent subscribers for operator B. The dots are scattered across the entire area, with a higher density in some regions, particularly around the center and towards the right side of the plot. + +Scatter plot showing subscriber distribution for operator A (red dots) and operator B (blue dots) across a 6x3.5 km area. + +Figure 6.54: Subscriber distribution in snapshot number 30 for operator A and operator B in case 10 to 18 + +![Scatter plot titled 'Dropped calls' showing call drops for operators A and B. The plot includes a legend: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg) + +A scatter plot titled "Dropped calls" showing the locations of dropped calls for two operators, A and B. The x-axis and y-axis both represent distance in km, ranging from 0 to 6 and 0 to 3.5 respectively. The plot features several clusters of points, each consisting of a central blue dot surrounded by red, yellow, and green dots. Arrows point from these peripheral dots towards the central blue dot. A legend at the bottom identifies the symbols: $A_D L - b$ (red dot), $A_U L - c$ (yellow dot), $B_D L - r$ (blue dot), and $B_U L - m$ (green dot). The clusters are distributed across the plot, with some located near the top and others towards the bottom. + +Scatter plot titled 'Dropped calls' showing call drops for operators A and B. The plot includes a legend: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +Figure 6.55: Dropped calls for operator A and operator B in case 10 – their repeater is off. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operator A and operator B in case 11 with ACRR = 10 dB. The plot shows several clusters of points with error bars, labeled with A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot displays several clusters of data points, each with vertical error bars. The clusters are labeled with the following text at the bottom: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . The data points are colored blue, red, and yellow, and some have small arrows pointing to them. + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operator A and operator B in case 11 with ACRR = 10 dB. The plot shows several clusters of points with error bars, labeled with A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +Figure 6.56: Dropped calls for operator A and operator B in case 11 – ACRR = 10 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operator A and operator B in case 12 with ACRR = 15 dB. The plot shows several clusters of points with error bars, labeled with A_D L - b, A_U L - c, B_D L - r, and B_U L - m.](449d2799e97657d8fa5897b2e74a88bd_img.jpg) + +The figure is a scatter plot titled "Dropped calls". The x-axis is labeled "distance (km)" and ranges from 0 to 6. The y-axis is labeled "distance (km)" and ranges from 0 to 3. The plot displays several clusters of data points, each with vertical error bars. The clusters are labeled with the following text at the bottom: $A_D L - b, A_U L - c, B_D L - r, B_U L - m$ . The data points are colored blue, red, and yellow, and some have small arrows pointing to them. + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operator A and operator B in case 12 with ACRR = 15 dB. The plot shows several clusters of points with error bars, labeled with A\_D L - b, A\_U L - c, B\_D L - r, and B\_U L - m. + +Figure 6.57: Dropped calls for operator A and operator B in case 12 – ACRR = 15 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 13 with ACRR = 20 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operator and location combinations.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 13 with ACRR = 20 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operator and location combinations. + +Figure 6.58: Dropped calls for operator A and operator B in case 13 – ACRR = 20 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 14 with ACRR = 25 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operator and location combinations.](b9f1f5c5167e357277b530940312d9ed_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) vs distance (km) for operators A and B in case 14 with ACRR = 25 dB. The plot shows several clusters of points with error bars, representing dropped calls for different operator and location combinations. + +Figure 6.59: Dropped calls for operator A and operator B in case 14 – ACRR = 25 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. It displays a hexagonal layout of cell sites with directional arrows and markers representing dropped calls for Operator A and Operator B. Legend: A_D L - b, A_U L - c, B_D L - r, B_U L - m.](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. It displays a hexagonal layout of cell sites with directional arrows and markers representing dropped calls for Operator A and Operator B. Legend: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. + +**Figure 6.60: Dropped calls for operator A and operator B in case 15 – ACRR = 30 dB.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on both axes. It displays a hexagonal layout of cell sites with directional arrows and markers representing dropped calls for Operator A and Operator B. Legend: A_D L - b, A_U L - c, B_D L - r, B_U L - m. This plot is for Case 16 with ACRR = 35 dB.](e01e66047c133f38249229dc639c9430_img.jpg) + +Dropped calls + +distance (km) + +distance (km) + +$A_D L - b, A_U L - c, B_D L - r, B_U L - m$ + +Scatter plot titled 'Dropped calls' showing distance (km) on both axes. It displays a hexagonal layout of cell sites with directional arrows and markers representing dropped calls for Operator A and Operator B. Legend: A\_D L - b, A\_U L - c, B\_D L - r, B\_U L - m. This plot is for Case 16 with ACRR = 35 dB. + +**Figure 6.61: Dropped calls for operator A and operator B in case 16 – ACRR = 35 dB.** + +![Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered around x-values of 1, 2.5, 4, and 5.5 km, with y-values ranging from 0 to 3.5 km. The legend indicates four series: A_D L - b (blue), A_U L - c (red), B_D L - r (yellow), and B_U L - m (green).](e91633da5160c8af51a4ace6d3347f53_img.jpg) + +Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered around x-values of 1, 2.5, 4, and 5.5 km, with y-values ranging from 0 to 3.5 km. The legend indicates four series: A\_D L - b (blue), A\_U L - c (red), B\_D L - r (yellow), and B\_U L - m (green). + +Figure 6.62: Dropped calls for operator A and operator B in case 17 – ACRR = 40 dB. + +![Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered around x-values of 1, 2.5, 4, and 5.5 km, with y-values ranging from 0 to 3.5 km. The legend indicates four series: A_D L - b (blue), A_U L - c (red), B_D L - r (yellow), and B_U L - m (green).](34f735bc749df18394ac93f5b84857b7_img.jpg) + +Scatter plot titled 'Dropped calls' showing distance (km) on the y-axis (0 to 3.5) versus distance (km) on the x-axis (0 to 6). Data points are clustered around x-values of 1, 2.5, 4, and 5.5 km, with y-values ranging from 0 to 3.5 km. The legend indicates four series: A\_D L - b (blue), A\_U L - c (red), B\_D L - r (yellow), and B\_U L - m (green). + +Figure 6.63: Dropped calls for operator A and operator B in case 18 – ACRR = 45 dB. + +### 6.5.4 Conclusions + +The results show an increasingly negative impact on the network performance in the adjacent channel when the ACRR is lower than 20 dB. Operator B experiences negligible impact for ACRR = 30 dB or more. + +The impact seems to be local around RF sources (Repeaters and Base Stations), mainly in the down link. The results are very similar for the two repeater positions. + +### 6.5.5 Comments + +Since filters are linear devices, the capability of modern 3G receivers to interpret the signal may not be hampered as much as previously assumed by the filter flanks. + +# Annex A: Change History + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|-------|-----------|------|---|-----------------------------------|-----|--------|--------|-----------| +| RP-36 | | | | Rel-7 version created from v6.0.0 | | | 7.0.0 | | +| RP-36 | RP-070373 | 0001 | 1 | ACRR description | F | 6.0.0 | 7.0.0 | TEI7 | +| RP-39 | RP-080122 | 0004 | | ACRR description | F | 7.0.0 | 7.1.0 | TEI7 | +| SP-42 | | | | Upgraded unchanged from Rel-7 | | | 8.0.0 | | +| SP-46 | | | | Upgraded unchanged from Rel-8 | | | 9.0.0 | | +| SP-51 | | | | Upgraded unchanged from Rel-9 | | 9.0.0 | 10.0.0 | | +| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.0.0 | 11.0.0 | - | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.0.0 | 12.0.0 | | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.0.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | - | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|--|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25967/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25967/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fe48c77e816e0998617292050153f6699e14e47 --- /dev/null +++ b/marked/Rel-16/25_series/25967/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:782f166b65201dffd17a01ea92c94298a0ceff23aada1100cfe247f78d2d16be +size 32605 diff --git a/marked/Rel-16/25_series/25967/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Rel-16/25_series/25967/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc1577607e28dc0bad355c389e0eb741e64fbf31 --- /dev/null +++ b/marked/Rel-16/25_series/25967/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfd0c4c4d007759293e5ec5b7bcc1f96498c30107039603fe53811c803bb2805 +size 19060 diff --git a/marked/Rel-16/25_series/25967/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-16/25_series/25967/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c1ef86bf6e14fe0a6a9c8edf4bc270f8cc23e93 --- /dev/null +++ b/marked/Rel-16/25_series/25967/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c16671425ad40afde542fbeb33e9077cac30a528bdf0f71a72c1ab18e03544 +size 96181 diff --git a/marked/Rel-16/25_series/25967/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-16/25_series/25967/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bd9ecf3248ef84e6a34a4a4744d06b11a1abfe8 --- /dev/null +++ b/marked/Rel-16/25_series/25967/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f7e833e93de558ac9717e4c9fd69829704819757be1b371c99fd4f27b7d5229 +size 22794 diff --git a/marked/Rel-16/25_series/25967/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-16/25_series/25967/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..797d21517f43b3713b74aa94ded8e3ec712a1139 --- /dev/null +++ b/marked/Rel-16/25_series/25967/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed2a0711133b4c19a448657a90a6460649bedfb9b718170dcb6c5f3cb444fd47 +size 75487 diff --git a/marked/Rel-16/25_series/25967/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Rel-16/25_series/25967/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f1b516a2829ac3395f4c1ecb19aed6839038067 --- /dev/null +++ b/marked/Rel-16/25_series/25967/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31713f87b9eed7fd8c7ab093187edb3af9d3fa798032a3c77cebadbfcb6689e2 +size 15419 diff --git a/marked/Rel-16/25_series/25967/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg b/marked/Rel-16/25_series/25967/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d2e985e4c5161d659cf146922ed59202b224be --- /dev/null +++ b/marked/Rel-16/25_series/25967/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4af7617e2fde2ca7a8506e6c9d4eb52eb7d16dc6918255dd4e772ee3719a30c8 +size 77379 diff --git a/marked/Rel-16/25_series/25967/6fc99b56d4021cf515d190c3a0da183f_img.jpg b/marked/Rel-16/25_series/25967/6fc99b56d4021cf515d190c3a0da183f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b1e8ae3f25b34d625e8fed2c68199037d6c583b --- /dev/null +++ b/marked/Rel-16/25_series/25967/6fc99b56d4021cf515d190c3a0da183f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb155147e416193d6385b502f355312e353c70657f20f9bbdb332beb1f5e28af +size 96057 diff --git a/marked/Rel-16/25_series/25967/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/25_series/25967/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e16e943a39060d66439cdf42e62a19a0be9cc5f --- /dev/null +++ b/marked/Rel-16/25_series/25967/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06d06295409c4acef4f6445190aa6557d7cff6f686d89ae75b25bf7d91a45cc2 +size 15272 diff --git a/marked/Rel-16/25_series/25967/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg b/marked/Rel-16/25_series/25967/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a35e20dab66d230771fbc217b2ee48766cde75 --- /dev/null +++ b/marked/Rel-16/25_series/25967/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96568127232ccd6519b65c2fa3ca2d84472649dc8c7435272360d8909c703eb4 +size 63831 diff --git a/marked/Rel-16/25_series/25967/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/25_series/25967/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bb9e5ccb0d4e42baa3ba8ac43d7201c1e7c4b9e --- /dev/null +++ b/marked/Rel-16/25_series/25967/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a9d5ba1bbaac1452395474f5d91ead49a1eb12e611c6157008664abf7b980d2 +size 28400 diff --git a/marked/Rel-16/25_series/25967/8f38356601e137ac471fc4771b9c5a5c_img.jpg b/marked/Rel-16/25_series/25967/8f38356601e137ac471fc4771b9c5a5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9afac07cffe8d63d75ee89dac7d99283602a257 --- /dev/null +++ b/marked/Rel-16/25_series/25967/8f38356601e137ac471fc4771b9c5a5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b36115b9949eb09b406d7bec3aa9b4c2933b2176591456b7b9fb55fefed1e7c +size 56644 diff --git a/marked/Rel-16/25_series/25967/9288d35265c4f3578be38d28ac588f18_img.jpg b/marked/Rel-16/25_series/25967/9288d35265c4f3578be38d28ac588f18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..144aa40a45e3221334554a66f4cd1621ded49488 --- /dev/null +++ b/marked/Rel-16/25_series/25967/9288d35265c4f3578be38d28ac588f18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c43f163ca3250c2e1fb9ed119a9431e69134898b5acd28669725516432242ec +size 75423 diff --git a/marked/Rel-16/25_series/25967/b86f4fd2c05bc69b4e99efd5f15b743d_img.jpg b/marked/Rel-16/25_series/25967/b86f4fd2c05bc69b4e99efd5f15b743d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b89a009e19474cb94006477245b2cdd27b4c7417 --- /dev/null +++ b/marked/Rel-16/25_series/25967/b86f4fd2c05bc69b4e99efd5f15b743d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9bb403ed3ff3b2d73f2daa2a54fd01ead8086203b256ad55e6b65f587c12ad1 +size 89434 diff --git a/marked/Rel-16/25_series/25967/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/25_series/25967/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebd1c15a39d01bd50a282f93ca551fb17b275fc5 --- /dev/null +++ b/marked/Rel-16/25_series/25967/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5dc8b18a0157e39b207d5432f5442d46c00975ccbb40a35a6590f5e707e05d3 +size 15504 diff --git a/marked/Rel-16/25_series/25967/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/25_series/25967/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e2211ffd503e80e9173c4218d7fda1ef619675 --- /dev/null +++ b/marked/Rel-16/25_series/25967/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ef6086cd7133f690cf62ca114746963eac1d4f74b02ce1e9280f577f53adbb4 +size 14537 diff --git a/marked/Rel-16/25_series/25967/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/marked/Rel-16/25_series/25967/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aa484e41fac70c18274f5c18525cbfc5328697e --- /dev/null +++ b/marked/Rel-16/25_series/25967/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1240dd3cc226fd4385581913a451525d72c3c4b14e3744df801d6b3396495d3f +size 12425 diff --git a/marked/Rel-16/25_series/25967/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-16/25_series/25967/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea6c4b43dac91afd5c58c07dabcd488fe61ffbf --- /dev/null +++ b/marked/Rel-16/25_series/25967/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaf3020de064d37b09d5da0cea1574562cd9a668b35660bafeca7ef187715182 +size 20038 diff --git a/marked/Rel-16/25_series/25967/ec42effecdc5bce7bb2bf7a96c954845_img.jpg b/marked/Rel-16/25_series/25967/ec42effecdc5bce7bb2bf7a96c954845_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76d7e308ac6191c6e399b6076eabbbd4ec0431a4 --- /dev/null +++ b/marked/Rel-16/25_series/25967/ec42effecdc5bce7bb2bf7a96c954845_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ec26dda99bd03daaba34514fad35472b9b2f6e2c592a7922037c727b354edc7 +size 53755 diff --git a/marked/Rel-16/25_series/25967/efbdff107f5a5aade487cf4ea0eae150_img.jpg b/marked/Rel-16/25_series/25967/efbdff107f5a5aade487cf4ea0eae150_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f08447ec2c126be201d8938eecd0e8e59e0f5ab6 --- /dev/null +++ b/marked/Rel-16/25_series/25967/efbdff107f5a5aade487cf4ea0eae150_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bbac993da6ec87c2cf3e9c5f8b6d43acbbab065587bb6824729f81a68394da3 +size 69708 diff --git a/marked/Rel-16/25_series/25967/raw.md b/marked/Rel-16/25_series/25967/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ead7746d177c4c4933ffef06641cd8b71108845a --- /dev/null +++ b/marked/Rel-16/25_series/25967/raw.md @@ -0,0 +1,1755 @@ + + + + +document. + +**2** Error! No text of +specified style in + +Error! No text of specified style in + +document. + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 General..... | 9 | +| 4.1 Task description ..... | 10 | +| 4.1.1 HNB class definition ..... | 10 | +| 4.1.2 HNB measurements and adaptation ..... | 10 | +| 5 Radio scenarios ..... | 11 | +| 5.1 Deployment configurations ..... | 11 | +| 5.1.1 Configuration A. CSG, dedicated channel, fixed power..... | 11 | +| 5.1.2 Configuration B. CSG, dedicated channel, adaptive power..... | 12 | +| 5.1.3 Configuration C. CSG co-channel, adaptive power ..... | 12 | +| 5.1.4 Configuration D. Partial co-channel..... | 12 | +| 5.1.5 Configuration E. Open Access, dedicated or co-channel..... | 13 | +| 5.2 Interference scenarios..... | 13 | +| 5.2.1 Coexistence simulation parameters ..... | 14 | +| 5.2.2 Interference scenario 1 UL HNB UE → Macro ..... | 14 | +| 5.2.3 Interference scenario 2 DL HNB → Macro UE ..... | 15 | +| 5.2.4 Interference scenario 3 UL Macro UE → HNB..... | 17 | +| 5.2.5 Interference scenario 4 DL Macro → HNB UE..... | 17 | +| 5.2.6 Interference scenario 5 HNB ↔ HNB (UL)..... | 17 | +| 5.2.7 Interference scenario 6 HNB ↔ HNB (DL)..... | 18 | +| 5.2.8 Interference scenarios 7,8 HNB ↔ Other systems..... | 18 | +| 5.2.9 HNB mobile operating very close to serving HNB..... | 19 | +| 6 HNB class definition..... | 19 | +| 6.1 Changes in 3GPP TS 25.104..... | 19 | +| 6.1.1 Changes on receiver characteristics..... | 19 | +| 6.1.1.1 Receiver dynamic range..... | 20 | +| 6.1.1.2 Adjacent channel selectivity (ACS)..... | 20 | +| 6.1.2 Changes on transmitter characteristics ..... | 20 | +| 6.1.2.1 Base station maximum output power..... | 20 | +| 6.1.2.2 Frequency error..... | 21 | +| 6.1.2.3 Spectrum emission mask ..... | 21 | +| 6.1.2.4 Adjacent channel leakage power ratio (ACLR)..... | 22 | +| 6.2 Changes in 3GPP TS 25.141 ..... | 22 | +| 7 Guidance on how to control HNB interference ..... | 24 | +| 7.1 HNB measurements..... | 24 | +| 7.1.1 Measurements from all cells..... | 24 | +| 7.1.2 Measurements to identify macro cells..... | 24 | +| 7.1.3 Measurements from macro cell layer ..... | 25 | +| 7.1.4 Measurements of other HNB cells ..... | 25 | +| 7.2 Control of HNB downlink interference..... | 26 | +| 7.2.1 Control of HNB power ..... | 26 | +| 7.2.1.1 Control of HNB power with respect to macro layer..... | 26 | +| 7.2.1.1.1 Co-channel deployment..... | 26 | +| 7.2.1.1.2 Adjacent channel deployment..... | 29 | +| 7.2.1.2 Centralized HNB power control ..... | 31 | +| 7.2.1.3 Control of HNB power with respect to other HNB ..... | 31 | +| 7.2.1.4 Control of HNB power or macro UE based on network control..... | 32 | + +document. + +| | | | +|-----------|------------------------------------------------------|----| +| 7.2.1.5 | Enhancements for Control of HNB Tx Power..... | 32 | +| 7.2.1.5.1 | UE-Assisted Power Calibration ..... | 32 | +| 7.2.1.5.2 | Minimum HNB Tx power..... | 32 | +| 7.3 | Control of HNB uplink interference..... | 33 | +| 7.3.1 | Control of HUE allowable transmit power..... | 33 | +| 7.3.2 | Control of HNB noise rise threshold..... | 35 | +| 7.3.3 | Control of HNB receiver gain ..... | 36 | +| 7.3.3.1 | Performance analysis ..... | 36 | +| 7.3.3.1.1 | Cell edge scenarios..... | 37 | +| 7.3.3.1.2 | Cell site scenarios..... | 39 | +| 7.4 | HNB self-configuration..... | 41 | +| 7.4.1 | Scrambling code selection..... | 42 | +| 7.4.2 | Carrier or UARFCN selection..... | 43 | +| 7.4.3 | Neighbour cell list configuration and handover ..... | 44 | +| 7.4.4 | HNB DL power setting..... | 44 | +| 7.4.5 | HUE UL power setting..... | 45 | +| 7.4.6 | LAC/RAC selection..... | 45 | +| 7.4.7 | Extreme/Abnormal operating conditions ..... | 45 | +| 7.5 | Control of HNB coverage ..... | 46 | +| 7.5.1 | CSG ..... | 46 | +| 7.5.2 | Open access ..... | 46 | +| 8 | Interference tests ..... | 46 | +| 8.1 | Downlink..... | 46 | +| 8.1.1 | Co-channel tests..... | 46 | +| 8.1.1.1 | DL test for HNB with 70dB coverage radius ..... | 47 | +| 8.1.1.2 | DL test for HNB with 80dB coverage radius ..... | 48 | +| 8.1.1.3 | DL test for HNB with 90dB coverage radius ..... | 48 | +| 8.1.2 | Adjacent channel tests ..... | 48 | +| 8.2 | Uplink..... | 48 | +| 8.2.1 | Basic tests ..... | 48 | +| 8.2.1.1 | Test setup ..... | 49 | +| 8.2.1.2 | Test parameters ..... | 50 | +| 8.2.2 | HSUPA tests ..... | 50 | +| 8.2.2.1 | HNB-Macro tests ..... | 50 | +| 8.2.2.1.1 | Uplink test for HNB with 70dB coverage radius ..... | 51 | +| 8.2.2.1.2 | Uplink test for HNB with 80dB coverage radius ..... | 52 | +| 8.2.2.1.3 | Uplink test for HNB with 90dB coverage radius ..... | 52 | +| 8.2.2.2 | Inter-HNB uplink test ..... | 53 | +| 9 | Summary ..... | 53 | +| 10 | Conclusions..... | 54 | +| Annex A: | Change history..... | 55 | + +document. + +# --- 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. + +document. + +# 1 Scope + +This document is a technical report which was requested in the Objective 2 of the RAN4 work item description “FDD Home NodeB RF requirements” [5]. The goal of this technical report is to describe the agreed approach towards the RF related issues raised in [5]: + +- A) The existing UTRA BS classes did not fully address the RF requirements of the HNB application. Proposals for changes to radio performance requirement specifications TS 25.104 are therefore provided in this report, together with the proposals for the test specification TS 25.141. Most of the HNB-specific additions to TS 25.104 / 25.141 were accommodated in a manner similar to the other BS classes. + +Editors note: + +- Where square bracketed values are suggested in 3GPP TR 25.820, to conduct further work as required to agree appropriate values. + - Where it is suggested that performance values in 3GPP TS 25.104 may be subject to change to conduct further work as required to see if this is necessary. +- B) The report intends to ensure that operators are provided with sufficient information to fully understand the issues concerning the deployment of HNBs: + - Deployment scenarios and their potential bottlenecks. + - Guidance on how to control the interference to surrounding macro networks and provide good coverage for the HNB + - Testing of the HNB. + +# 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] R4-083117, “Feedback on output power requirement for TS 25.104, Picochip”, 3GPP RAN WG4, 49th meeting, Prague, 2008 +- [2] R4-083355, “CR on TS25.104 HNB adjacent channel protection requirements”, 3GPP RAN WG4, 49th meeting, Prague, 2008 +- [3] R4-083249, “Meeting minutes of the ad-hoc meeting”, 3GPP RAN WG4, 49th meeting, Prague, 2008 +- [4] R4-083087, “Meeting minutes of the phone meeting”, 3GPP RAN WG4, 49th meeting, Prague, 2008 +- [5] RP-080234, “RAN4 work item description “FDD Home NodeB RF Requirements,” +- [6] R4-071211, “Recommendations on transmit power of Home NodeB”, Alcatel-Lucent +R4-071231, “Open and Closed Access for Home NodeBs”, Nortel, Vodafone +- [7] R4-071241, “Regulatory aspects on Home Node B in the network architecture impacting RAN4 work”, BMWi + +document. + +- [8] R4-080409, "Home NodeB Interference Analysis", QUALCOMM Europe +- [9] R4-071540, "LTE Home Node B downlink simulation results with flexible Home Node B power", Nokia Siemens Networks +- [10] R4-071578, "Simulation results of macro-cell and co-channel Home NodeB with power configuration and open access", Alcatel-Lucent +- [11] R4-071617, "HNB and HNB-Macro Propagation Models", Qualcomm Europe +- [12] R4-071660, "Impact of HNB with fixed output power on macro HSDPA capacity" ,Ericsson +- [13] R4-072004, "Performance Evaluation about HNB coexistence with Macro networks", Huawei +- [14] R4-071661, "Impact of HNB with controlled output power on macro HSDPA capacity", Ericsson +- [15] R4-080149, "Simulation assumptions for the block of flats scenario", Ericsson +- [16] R4-070970, "Initial simulation results for Home Node B receiver sensitivity", Ericsson +- [17] R4-070971, "Initial simulation results for Home Node B receiver blocking", Ericsson +- [18] R4-071231, "Open and Closed Access for Home NodeBs", "Nortel, Vodafone" +- [19] R4-071619, "Analysis of Uplink Performance under Co-channel Home NodeB-Macro Deployment", Qualcomm Europe +- [20] R4-080409, "Home NodeB Interference Analysis", QUALCOMM Europe +- [21] R4-071185, "The analysis for Home NodeB receiver blocking requirements", Huawei +- [22] R4-071263, "System simulation results for Home NodeB interference scenario #2", Ericsson +- [23] R4-070902, "Initial home NodeB coexistence simulation results", Nokia Siemens Networks +- [24] R4-080151, "Simulation results for Home NodeB to macro UE downlink co-existence within the block of flats scenario", Ericsson +- [25] R4-071211, "Recommendations on transmit power of Home NodeB", Alcatel-Lucent +- [26] R4-071554, "The analysis for low limit for Home NodeB transmit power requirement", Huawei +- [27] R4-072025, "Proposed HNB Output Power Range", QUALCOMM Europe +- [28] R4-071150, "Home BTS output power", Orange +- [29] R4-071253, "Minutes of Home NodeB/ ENodeB Telephone Conference #3. Aug 7, 2007", Motorola +- [30] R4-070825, "Home BTS consideration and deployment scenarios for UMTS", Orange +- [31] R4-080097, "Minutes of Home NodeB/ ENodeB Telephone Conference #7, Jan 31, 2008" +- [32] R4-071618, "Home Node B HSDPA Performance Analysis", Qualcomm Europe +- [33] R4-080152, "Simulation results for Home NodeB uplink performance in case of adjacent channel deployment within the block of flats scenario", Ericsson +- [34] R4-080155, "Home NodeB maximum output power from the maximum UE input level point of view", Ericsson +- [35] R4-082153, "Transmitter characteristics of 3G Home NodeB" CR by Alcatel-Lucent, Ericsson, Vodafone, Orange, Huawei +- [36] R4-083255, "HNB adjacent channel protection requirements", CR by Nokia Siemens Networks, Vodafone Group, Ericsson, Huawei, Motorola, Alcatel-Lucent + +document. + +- [37] R4-081938 TP for 25.9xx: Section 6.1.2 Frequency error, Ericsson +- [38] R4-081939 TP for 25.9xx: Section 6.1.3 Spectrum emission mask +- [39] R4-082146 TP for 25.9xx: Section 6.1.4 Adjacent Channel Leakage power Ratio (ACLR), Ericsson +- [40] R4-082664 Transmitter characteristics Tests for 3G Home NodeB, CR by Huawei. +- [41] R4-082665 Receiver characteristics Tests for 3G Home NodeB, CR by Huawei +- [42] R4-082666 Demodulation Requirements Tests for 3G Home NodeB, CR by Huawei +- [43] R4-083193 Modified Test Models for 3G Home NodeB, CR by Alcatel-Lucent, Huawei, Qualcomm Europe, Vodafone. +- [44] R4-083149 Comparison on proposals on Modified Test Models for 3G Home NodeB, Alcatel-Lucent +- [45] R4-072006, "Clarification of Home eNB scenarios and issues for RAN2/3/4", NTT DoCoMo, T-mobile +- [46] R4-082994, "HNB Output power for adjacent channel protection", Ericsson, RAN4 #49 Prague +- [47] R4-082114, "Receiver Characteristics of 3G Home NodeB", Alcatel-Lucent, Nokia Siemens Networks, Ericsson, Vodafone, Orange, RAN4 #48 Jeju, Korea +- [48] R4-081886, "Home NodeB Co-existence Analysis with Adjacent-Channel Operator", Qualcomm Europe, RAN4 #48 Jeju, Korea +- [49] R4-081884, "Requirement for Co-existence of HNB with Adjacent Channel Operator", Qualcomm Europe, Vodafone Group, ip.access, Airvana, RAN4 #48 Jeju, Korea +- [50] R4-082613, "Requirement for Co-existence of HNB with Adjacent Channel Operator", Qualcomm Europe, Airvana, AT&T, ip.access, Vodafone Group RAN4 #48bis Edinburgh, Scotland +- [51] R4-081597, "Impact of uplink co-channel interference from an un-coordinated UE on the Home Node B", Airvana, Vodafone, ip.access, RAN4 #47, Munich, Germany +- [52] R4-081598, "Requirement Impact of uplink adjacent channel interference from an un-coordinated UE on the Home Node B", ip.access, Vodafone, Airvana, RAN4 #47, Munich, Germany +- [53] 3GPP TR 21.905: Vocabulary for 3GPP Specifications +- [54] Broadband Forum TR-069 Amendment 2, CPE WAN Management Protocol, Broadband Forum Technical Report, 2007. +- [56] R4-090172, "Home Node B control and monitoring", BMWi, RAN4#49bis, Ljubljana, Slovenia. +- [57] 3GPP TS 25.331 v8.3.0, "Radio Resource Control (RRC); Protocol specification". + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the terms and definitions given in TR 21.905 [54] 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 [54]. + +## 3.1 Definitions + +Void. + +document. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{of_i}$ | Interference on frequency $f_i$ | +| $G_{ant}$ | Gain of antenna | +| $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 white noise source (simulating interference from cells, which are not defined in a test procedure) as measured at the UE antenna connector. For DC-HSDPA $I_{oc}$ is defined for each of the cells individually and is assumed to be equal for both cells unless explicitly stated per cell. | +| $V_{UE\ max}$ | Maximum speed of UE | +| $V_{UE\ HNB}$ | UE speed | + +## 3.3 Abbreviations + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACIR | Adjacent Channel Interference Rejection, can be translated to receiver selectivity when the emission mask of the interfering signal is accounted for. | +| BW | Band Width | +| CSG | Closed Subscriber Group | +| DL | Downlink, the RF path from BS to UE | +| E-DPDCH | Enhanced Dedicated Physical Data CHannel | +| E-DPCCH | Enhanced Dedicated Physical Control CHannel | +| FRC | Fixed Reference Channel | +| GSM | Mobile cellular system (throughout this document, this acronym is generally to also means the services GPRS and EDGE, both enhancements to GSM, unless not applicable to the discussion.) | +| HENB | Home Enhanced Node B | +| HNB | Home NodeB | +| HNBAP | HNB Application Protocol | +| HNB-GW | HNB GateWay | +| HSPA | High Speed Packet Access | +| HS-DPCCH | High Speed Dedicated Physical Control CHannel | +| HUE | UE camping on HNB cell | +| IE | Information Element | +| IRAT | Inter-RAT | +| LAC | Location Area Code | +| LAU | Location Area Update | +| MBSFN | Multicast/Broadcast over a Single Frequency Network | +| MNB | Macro NodeB | +| MUE | UE camping on Macro cell | +| NB | NodeB | +| NLM | Network Listen Mode | +| NR | Noise Rise | +| PL | Path Loss | +| REM | Radio Environment Measurement | +| RRC | Radio Resource Control | +| RTWP | Receive Total Wideband Power | +| RX, Rx | Receive, Receiver | +| SIB | System Information Block | +| TX, Tx | Transmit, Transmitter | +| UE | User Equipment, also cellular terminal | +| UL | Uplink, the RF path from UE to BS | + +# --- 4 General + +As agreed in the work item proposal [1]: + +document. + +Within the course of increasing UMTS terminal penetration and fixed-mobile convergence, an upcoming demand for 3G Home NodeBs is observed to provide attractive services and data rates in *home environments*. + +UTRAN is not optimally suited for this application as UTRAN was developed and defined under the assumption of coordinated network deployment, whereas Home NodeBs are typically associated with uncoordinated and large scale deployment. + +Aim of this work item is to amend the UTRAN NodeB related RF specifications to support the Home NodeBs application. No changes to the UE RF specifications are foreseen. + +The scope of this work item is limited to the UTRA FDD mode. + +## 4.1 Task description + +### 4.1.1 HNB class definition + +The purpose of this work is to update the radio performance requirement specification TS 25.104, further work required to agree on *new parameter values will be documented in the TR and the updates required in test specification TS 25.141 will be documented*. + +### 4.1.2 HNB measurements and adaptation + +The purpose of this work item is to ensure that operators have necessary information about how to adjust the output transmission power of HNB as a function of the signal strength from the macro cell layer, and/or from other HNBs, in order to enhance overall system performance. + +In order to achieve this, (at least) the following areas should be addressed: + +- 1) Guidance on how to control HNB power + - a. The intention is to provide guidance to operators on possible strategies and expected performance in typical exemplary deployment scenarios. + - b. Is it possible to have the same mechanism to control HNB output power with respect to the macro cell layer, other surrounding HNBs, and in the case of HNB coverage control for open access HNB. + - c. It is not the intention to mandate HNB behaviour. +- 2) Measurements of surrounding environment (i.e. macro and other HNBs signal strength) + - a. Issues to address include factors that govern accuracy and timeliness of the suggested measurements, and the ability to identify the macro neighbour cell list. + - b. It is not the intention to restrict the vendor's scope about how to perform measurements. + - c. It is envisaged that measurements will be performed directly by the HNB or by employing the UEs attached to the HNB, using existing UE defined measurements. +- 3) Mechanism to set maximum power + - a. Issues to address include accuracy and timeliness of HNB maximum power setting. + - b. It is not the intention to restrict the vendor's scope about how to process measurements. + - c. It is not the intention to restrict the vendor's scope about which network element the measurements may be processed in. + - d. It is not the intention to restrict to which network entities measurements are reported. However, it is not envisaged that new signalling will be standardised to support this. +- 4) Mechanism to adjust HNB uplink. + - a. Issues to address include possibility to adjust uplink noise rise target. + - b. It is not the intention to restrict the vendor's scope about what actions may be taken regarding HNB uplink. + +document. + +# --- 5 Radio scenarios + +## 5.1 Deployment configurations + +A number of different deployment configurations have been considered for Home (e)NodeB. The aspects which define these are as follows: + +- Open access or CSG (Closed Subscriber Group) + - Open access HNBs can serve any UE in the same way as a normal NodeB + - CSG HNBs only serve UEs which are a member of a particular Closed Subscriber Group +- Dedicated channel or co-channel + - Whether HNBs operate in their own separate channel, or whether they share a channel with an existing (e)UTRAN network +- Fixed or adaptive (DL) maximum transmit power + - Fixed: HNBs have a set fixed maximum transmit power + - Adaptive: HNB's sense interference to existing networks, and adjust maximum transmit power accordingly + +The following configurations are considered and are described in more detail in the following sections. + +- A. CSG, Dedicated channel, Fixed Power +- B. CSG, Dedicated channel, Adaptive Power +- C. CSG, Co-channel, Adaptive Power +- D. Partial Co-Channel +- E. Open Access, dedicated or co-channel + +### 5.1.1 Configuration A. CSG, dedicated channel, fixed power + +HNB is configured as a Closed Subscriber Group. Access to HNB is controlled through an arrangement between the HNB owner and by the network operator. Access is restricted to a very limited number of UE; the majority of UE do not have access to the HNB. Therefore, a CSG covers the partially open system, as discussed in [46]. + +The HNB is deployed on a dedicated channel; i.e. a channel that is not used within the macro layer. The worst case dedicated channel deployment is the adjacent channel. The worst case adjacent channel deployment is when the adjacent channel is owned by a different operator. + +Although the HNB is deployed on the dedicated frequency with respect to the macro network, a co-channel interference scenario remains between HNB's. HNB's must share the same frequency, hence co-channel coexistence must be analysed within a dense population of HNB. + +In this configuration, the Home NodeB's maximum transmit power could potentially be fixed by the operator to be lower than the Maximum Transmit power capability. As analysed in detail in [13], the reduced power limit ensures the dominance of the HNB with respect to a macro cell is appropriately bounded. Therefore, the HNB cell size is limited with respect to a weak macro signal. Consequently, the HNB can operate with a fixed maximum power level even at the edge of a macro cell. + +### 5.1.2 Configuration B. CSG, dedicated channel, adaptive power + +HNB is configured as a Closed Subscriber Group. + +document. + +The HNB is deployed on a dedicated channel. + +Maximum transmit power may be set as high as the maximum capability of the HNB class of base stations. However, higher maximum power level than the acceptable “fixed” maximum power for dedicated channel deployment, Section 5.1.1 shall only be used when appropriate for the deployed environment, and when the resulting interference is acceptable. + +### 5.1.3 Configuration C. CSG co-channel, adaptive power + +HNB is configured as a Closed Subscriber Group. + +The HNB is deployed on the same channel as the macro network. This is considered the worst case interference scenario; consequently this is the highest risk deployment. Power levels used by the Home Node B and all attached UE’s must be set as appropriate for the deployed environment. + +The fixed maximum transmit power limit is not considered feasible for co-channel deployment and has been removed from further analysis. + +### 5.1.4 Configuration D. Partial co-channel + +Partial co-channel is proposed for CSG operation for HNBs. This works by limiting frequencies which are shared by the “macro layer” and the HNB, as shown in Figure 5.1.4-1. The macro layer uses the all available frequencies, whereas the home NodeB only uses a subset – the shared part. Macro UEs can operate on any frequency. Macro UEs in the shared part experiencing “pathological” interference from home NodeBs can move to the clear part. + +Whilst this configuration is intended as a solution for CSG operation, it may also be applicable to Open Access in order to limit the influence of the HNB in the overall network and allow more control over mobility. + +![Figure 5.1.4-1: Spectrum arrangement for macro and home node Bs. The diagram shows a horizontal axis labeled 'frequency'. Above the axis, there are two brackets: 'shared part' on the left and 'clear part' on the right. Below the 'shared part' bracket, there is a grey rectangle labeled 'Home Node B'. Below the 'clear part' bracket, there is a grey rectangle labeled 'Macro'.](5a95b187de0044da69b7322e04761b86_img.jpg) + +The diagram illustrates the spectrum arrangement for macro and home node Bs. A horizontal axis represents frequency. Above the axis, two brackets divide the spectrum into a 'shared part' on the left and a 'clear part' on the right. Below the 'shared part' bracket, a grey rectangle is labeled 'Home Node B'. Below the 'clear part' bracket, a grey rectangle is labeled 'Macro'. + +Figure 5.1.4-1: Spectrum arrangement for macro and home node Bs. The diagram shows a horizontal axis labeled 'frequency'. Above the axis, there are two brackets: 'shared part' on the left and 'clear part' on the right. Below the 'shared part' bracket, there is a grey rectangle labeled 'Home Node B'. Below the 'clear part' bracket, there is a grey rectangle labeled 'Macro'. + +**Figure 5.1.4-1 Spectrum arrangement for macro and home node Bs** + +Figure 5.1.4-2 shows how this could be implemented in UTRAN. Two channels are needed, one for Macro+HNB, the other for Macro only. Macro-only UEs experiencing HNB interference in channel 1 would handover to channel 2. + +![Figure 5.1.4-2: Spectrum arrangement for UTRAN. The diagram shows a horizontal axis representing frequency, divided by a vertical dashed line into two channels. Channel 1 (left) contains icons for 'NB' (NodeB) and 'HNB' (Home NodeB). Channel 2 (right) contains icons for 'NB' (NodeB) and 'UE' (User Equipment). Below the axis, the channels are labeled 'channel 1' and 'channel 2'.](cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg) + +The diagram illustrates the spectrum arrangement for UTRAN. A horizontal axis represents frequency, divided by a vertical dashed line into two channels. Channel 1 (left) contains icons for 'NB' (NodeB) and 'HNB' (Home NodeB). Channel 2 (right) contains icons for 'NB' (NodeB) and 'UE' (User Equipment). Below the axis, the channels are labeled 'channel 1' and 'channel 2'. + +Figure 5.1.4-2: Spectrum arrangement for UTRAN. The diagram shows a horizontal axis representing frequency, divided by a vertical dashed line into two channels. Channel 1 (left) contains icons for 'NB' (NodeB) and 'HNB' (Home NodeB). Channel 2 (right) contains icons for 'NB' (NodeB) and 'UE' (User Equipment). Below the axis, the channels are labeled 'channel 1' and 'channel 2'. + +**Figure 5.1.4-2 Spectrum arrangement for UTRAN** + +document. + +Figure 5.1.4-3 shows how this could be implemented for EUTRAN. Since it has scalable bandwidth, it does not necessarily require two channels as with UTRAN. Provided the HENB sub-band does not overlap the central 6 RBs of the macro's channel, then it will not prevent UEs receiving the BCH and SCH and connecting to the macro layer. Frequency hopping and Frequency dependent scheduling will ensure UEs experiencing HNB interference on part of the band will still be able to function. + +![Figure 5.1.4-3 Spectrum arrangement for EUTRAN. The diagram shows two horizontal frequency bands. The top band represents the macro layer, with a central portion highlighted in grey, representing the central 6 RBs. The bottom band represents the HENB sub-band, which is wider and also has a grey highlighted portion. Vertical dashed lines indicate the boundaries of these sub-bands. Arrows point to the left and right ends of the bands, and there are small icons of antennas at the bottom center.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 5.1.4-3 Spectrum arrangement for EUTRAN. The diagram shows two horizontal frequency bands. The top band represents the macro layer, with a central portion highlighted in grey, representing the central 6 RBs. The bottom band represents the HENB sub-band, which is wider and also has a grey highlighted portion. Vertical dashed lines indicate the boundaries of these sub-bands. Arrows point to the left and right ends of the bands, and there are small icons of antennas at the bottom center. + +**Figure 5.1.4-3 Spectrum arrangement for EUTRAN** + +Providing UEs hand over to the clear channel when experiencing HNB interference, the performance of this configuration should be similar to that of configuration A (dedicated channel, fixed power) + +### 5.1.5 Configuration E. Open Access, dedicated or co-channel + +Open access Home NodeBs serve all UEs, in the same way as other NodeBs do [6-8]. The results referenced in Section 5.2 explain the level of openness supported by a HNB deployment when explaining the model and assumptions used. A completely open system is already covered by the existing classes of Node B. + +## 5.2 Interference scenarios + +Home Node B's are intended to enhance the coverage of a UMTS Radio Access Network in the *home environment*. However, it is not feasible to completely control the deployment of the HNB layer within the UMTS RAN. Therefore, interference due to the HNB is a concern and interference mitigation techniques are required. Interference mitigation techniques will impact the HNB performance, which will present the HNB with challenges in managing its radio resources and maintaining Quality of Service to its attached users. In the following sections the interference scenarios that exist between a HNB and the macro layer, and among HNBs, are discussed in more detail. + +Priority of the interference scenario investigations has been established as shown in Table 5.1.5-1. + +document. + +**Table 5.2-1 Interference scenarios** + +| Number | Aggressor | Victim | Priority | +|---------------|-----------------------------------------------|-----------------------------------------------|-----------------| +| 1 | UE attached to Home Node B | Macro Node B Uplink | yes | +| 2 | Home Node B | Macro Node B Downlink | yes | +| 3 | UE attached to Macro Node B | Home Node B Uplink | yes | +| 4 | Macro Node B | Home Node B Downlink | | +| 5 | UE attached to Home Node B | Home Node B Uplink | yes | +| 6 | Home Node B | Home Node B Downlink | yes | +| 7 | UE attached to Home Node B and/or Home Node B | Other System | | +| 8 | Other System | UE attached to Home Node B and/or Home Node B | | + +In addition to the above scenarios, we also addressed the scenario of a HNB mobile operating very close to its serving HNB, simulation results are referred to in Section 5.2.9. + +Additionally, possible methods for assessing HNB performance in the different interference scenarios were proposed in [9]. + +### 5.2.1 Coexistence simulation parameters + +Simulation results assuming a wide range of parameters were performed to ensure a robust and diverse analysis of the problem. The results in this section were generated over a range of simulation assumptions. Simulation models are described for different HNB deployment scenarios in [10-14]. Models for the dense urban apartment building, HNB-Macro are provided in [12,16]. + +### 5.2.2 Interference scenario 1 UL HNB UE → Macro + +Noise rise on the macro layer will significantly reduce macro performance; consequently, the transmit power of the UE should be controlled. The following mechanisms are investigated to limit the interference cause by an HNB attached UE: + +- HNB receiver performance will have an impact on UE transmit power; therefore any relaxation of the BS receiver required must be carefully investigated. +- UE power limitations such as maximum transmit power limits, and strict scheduling limits and noise rise limitation for HSUPA +- Open access; UEs are permitted to move easily between the macro and HNB layers, thereby ensuring each uplink connection requires the least amount of UE transmit power and generates the least amount of interference [11]. + +document. + +**Table 5.2-2. Directory of results for interference scenario 1 UL HNB UE → Macro** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|------------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| High Level Requirement | | | | +| System Performance | [14,17,18] | CSG Performance analysis | | +| | [11,19] | Performance analysis of open system | | +| | [20,21] | Need to address trade-off between macro and HNB performance. Adaptive uplink attenuation can improve performance. | | +| Base station Requirements | | | | +| Receiver Sensitivity (for CSG HNB) | [17,21] | As per Local Area BS class spec. Acknowledgement that desensitisation of the CSG HNB receiver will potentially increase HNB UE interference on Macro | RAN4 | +| Receiver Performance (for HNB) | [17] | As per Local Area BS class spec. Acknowledgement that poor performance of the HNB receiver will potentially increase HNB UE interference on Macro. However, testing for high speed mobile may no longer be required, if lower maximum UE speed is adopted | RAN4 | +| In band blocking tests | [18,22] | As per Local Area BS class spec, (but may change if a different Minimum Coupling Loss is chosen) | RAN4 | +| HNB system Requirements | | | | +| UE power limits | [11] | No protocol changes required. A limit is required to protect macro performance. Note: this is operator implementation specific; no need to standardise. | | +| | | Deployment Scenario B will see highest UE power levels; hence most likely to require a limit. | | + +### 5.2.3 Interference scenario 2 DL HNB → Macro UE + +In a CSG, downlink interference from an HNB will result in coverage holes in the macro network. In co-channel deployment the coverage holes are considerably more significant than when the HNB is deployed on a separate carrier. Several mechanisms are considered to reduce the impact on the macro coverage: + +- fixed HNB transmit power. (this is only applicable to dedicated channel deployment) +- control of HNB behaviour with respect to setting its maximum transmit power +- moving macro UE to another carrier. (this is only applicable to the areas deploying overlay carriers) +- open access systems. + +Deployment scenario C reduces the impact on the macro layer by automatically adjusting the HNB transmit power. The algorithm used to control the HNB transmission power will be left as an implementation detail; consequently a variety of models are explored when setting the HNB transmission power. Some options are as follows: + +- In [13], the maximum output power for each HNB is set based on a fixed limit in the “dead zone” (out-of-coverage area) that would be caused by any adjacent channel macro UE. +- In [10], the transmit power for each HNB is set based on the inverted power control scheme used for macro/macro coexistence simulation (power control set 1, power control set 2) +- In [11], the average transmit power for both the HNB and the macro are balanced at the HNB cell edge. + +Deployment scenario B, where the HNB output power is controlled and the HNB's are deployed on an adjacent carrier to the macro layer, is shown to be of limited use [15], since the reduced power limit of Deployment Scenario A is adequate for coverage of the majority of homes. An increase in power may be desirable when a large coverage area is desired, or when coverage within the home is difficult. However, when the density of HNB is very high, inter-HNB interference dominates, and an increase in HNB power beyond Deployment scenario A does not result in performance gains. + +document. + +Open access provides an alternative solution, as illustrated in [11] and [19]. + +When specifying HNB behaviour, it is the goal of this study item to avoid any RAN1 impact if possible. If possible, RAN4 will determine the framework to allow a range of implementation to set the maximum transmit power. For example, a framework may consist of requirements and tests for a suitable target power level, but will not specify the algorithm. + +It is acknowledge that no single mechanism alone provides a definitive solution. Any solution will likely involve a combination of methods, and will certainly have to reach a suitable compromise between macro layer and HNB layer performance. + +**Table 5.2-3. Directory of results for interference scenario 2 DL HNB → Macro UE** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|----------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| High Level Requirement | | | | +| System Performance | [13,14,23] | CSG Performance analysis, Deployment Configuration A | | +| | [10,14,15,21,23] | CSG Performance analysis, Deployment Configuration B,C | | +| | [11,19] | Performance analysis of open system, Deployment Configuration E | | +| | [13,21,23,24] | CSG deployment of HNB's using fixed HNB transmit power results in unacceptable performance for co-channel deployments | | +| | [21] | CSG deployment of HNB's using fixed HNB transmit power results in unacceptable performance both for co-channel and dedicated channel deployments | | +| Base station Requirements | | | | +| Maximum transmit power | [21,25] | Deployment Configuration A:
agreement that Adjacent Channel interference still exists without some control or reduction of power. | RAN4,
RAN2 | +| Maximum transmit power dynamic range | [23,26,27,28] | General agreement that CSG HNB performance may benefit from the ability to set the maximum transmit power to lower values. This will require a change to Primary CPICH Tx Power in TS 25.331, Section 10.3.6.61 and is currently under discussion with RAN2 via LS, [77]. | RAN4,
RAN2, | +| Electromagnetic Field protection. Need for Radiated Power Tests | [29] | Raised in [30], no recorded objections | | +| HNB system Requirements | | | | +| Need for BS to set transmit power appropriate for macro environment. | [21,25] | Deployment Configuration B,C:
Acknowledged that interference in closed system is too high, interference management mechanism required. | RAN4,
RAN2, | +| Definition of transmit power level | [30] | Deployment Configuration B,C:
Multiple possibilities exist to define HNB power level:
- Relative to macro CPICH RSCP
- Relative to macro CPICH Ec/lo
- Relative to total RSSI
Could be defined as:
- HNB dominance level
- Size of dead zone caused. | RAN4,
RAN2, | +| Hand In requirement for Interference mitigation | [30] | Deployment Configuration A,B,C:
General consensus that aspects of open system help in managing HNB interference scenarios. interference mitigation is required in a closed system; hand in should be permitted as an option. | RAN2,
RAN4 | + +document. + +### 5.2.4 Interference scenario 3 UL Macro UE → HNB + +As described in interference scenario 1, the HNB attached UE is constrained in its transmit power. Consequently, the HNB attached UE is especially susceptible to interference from the macro UE. The HNB receiver must reach a compromise between protecting itself against uncoordinated interference from the macro UEs, while controlling the interference caused by its own UE's towards the macro layer. + +**Table 5.2-4. Directory of results for interference scenario 3 UL Macro UE → HNB** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|-------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| High Level Requirement | | | | +| System Performance | [20,21] | Need to address trade-off between macro and CSG HNB performance. Adaptive uplink attenuation can improve performance. | RAN2,
RAN4 | +| | [14] | CSG performance analysis | | +| Base station Requirements | | | | +| Receiver Sensitivity | [17] | In general can be the same as local area BS | RAN4 | +| | [17,31] | Deployment Scenario B,C:
In a CSG, co-channel deployment, HNB must manage noise rise of other UE's. It is noted that HNB desensitisation has an impact of system performance, eg. a reduction on UE battery life. | RAN4 | +| Receiver Dynamic Range | | In general can be the same as local area BS | RAN4 | +| | [31] | Deployment Scenario B,C:
In a CSG, co-channel deployment, HNB must manage noise rise of other UE's. Local Area BS class spec is sufficient. | RAN4 | +| Adjacent Channel Selectivity | | As per Local Area BS class spec. | RAN4 | +| Receiver Performance (fading) | [32] | general consensus on max user speed < 30 km/h; | RAN4 | +| Receiver Performance (delay spread) | | 50 m cell radius | RAN4 | +| In band blocking tests | | As per Local Area BS class spec (dependent on MCL). | RAN4 | + +### 5.2.5 Interference scenario 4 DL Macro → HNB UE + +A trade off exists between the HNB coverage and the impact on the macro network coverage (discussed in Section 5.2.3). The HNB downlink transmit power can be adjusted to maintain coverage if the dynamic range of the HNB power is large enough [16]. Additional performance analysis in a closed system is provided in [14]. + +No changes to UE. This is expected to hold for LTE as well. The Wide Area Base Station defines the UE RF performance. The UE will then be expected to work with all other classes of eNodeB. + +### 5.2.6 Interference scenario 5 HNB ↔ HNB (UL) + +With respect to other HNB, co-channel interference must be considered. This is especially important to deployment option A, where a strong macro presence is not available on the same frequency to act as a reference level to determine UE power limits. + +It is difficult to avoid co-channel interference between CSG HNB's, which limits the interference reductions achieved by deploying a CSG HNB on an separate carrier from the macro network, as shown in [15,18,33]. Interference management techniques are required to manage HNB to HNB interference. + +document. + +**Table 5.2-5. Directory of results for interference scenario 5 HNB ↔ HNB (UL)** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|----------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| High Level Requirement | | | | +| System Performance | [21,33] | The performance of CSG HNBs is degraded unless interference mitigation techniques are used. | RAN4 | +| | [34] | Without interference mitigation techniques, there is a clear impact on CSG HNB performance. However, the significant of the impact must be judged by the operator in the context of the desired system performance. | | +| Base station Requirements | | | | +| Receiver Sensitivity | [21,33] | Acknowledgement that a large number of HNB could be located very close together | RAN4 | +| Receiver Dynamic Range | [21,33] | Acknowledgement that a large number of HNB could be located very close together | RAN4 | +| Adjacent Channel Selectivity | | Acknowledgement that a large number of HNB could be located very close together | RAN4 | +| In band blocking tests | | Acknowledgement that a large number of HNB could be located very close together | RAN4 | +| HNB system Requirements | | | | +| UE power limits | | No protocol changes required | RAN4 | + +### 5.2.7 Interference scenario 6 HNB ↔ HNB (DL) + +With respect to other HNB, co-channel interference must be considered. This is especially important to deployment option A where a strong macro presence is not available on the same frequency to act as a reference to determine HNB transmit power settings. + +**Table 5.2-6. Directory of results for interference scenario 6 HNB ↔ HNB (DL)** + +| Requirements Affected | Ref-erences | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|---------------------------------------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| High Level Requirement | | | | +| System Performance | [21,33] | The performance of CSG HNBs is significantly degraded unless interference mitigation techniques are used. | | +| | [16,25] | CSG DL performance analysis including apartment blocks and macro layer. | | +| HNB system Requirements | | | | +| Need for HNB to set transmit power based on neighbouring HNB power. | | Deployment Scenario B,C:
Acknowledged that interference in closed system is too high, interference management mechanism required. | RAN4,
RAN2, | + +### 5.2.8 Interference scenarios 7,8 HNB ↔ Other systems + +document. + +**Table 5.2-7. Directory of results for interference scenarios 7 and 8** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|----------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Base station Requirements | | | | +| | | Need for new out of band blocking requirements due to different transceivers on top of each other in the home. [30][31] recommends a 15 dB MCL, 20 cm minimum spacing should be considered for investigations in RAN4 | | +| Out of band blocking | [31] | Status: An LS reply [73] was sent to ETSI TC DECT, stating that inter-operation studies are best done in ECC PT1 | RAN4 | +| Spurious Emissions | [31] | As above. | | + +### 5.2.9 HNB mobile operating very close to serving HNB + +**Table 5.2-8. Directory of results for HNB mobile operating very close to serving HNB** + +| Requirements Affected | References | Summary of analysis provided;
Recommendation endorsed by cited reference | WG affected | +|----------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Base station Requirements | | | | +| Maximum output power | [35] | Possible impact on a HNB mobile operating very close to its serving HNB is addressed. Indicates that power levels lower than 20dBm may be recommended to ensure correct mobile operation. | RAN4 | + +# --- 6 HNB class definition + +## 6.1 Changes in 3GPP TS 25.104 + +This section describes the changes to BS RF requirements specifications TS 25.104 + +### 6.1.1 Changes on receiver characteristics + +The changes on receiver characteristics are summarized in Table 6.1-1 and were approved in [48]. + +document. + +**Table 6.1-1 Summary of changes on receiver characteristics in TS 25.104** + +| Section | Requirement | Discussion / Required Changes | +|---------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| 7.2.1 | Reference Sensitivity Level | Same requirements as for Local Area BS | +| 7.3.1 | Dynamic Range | Introduced new requirements for Home BS | +| 7.4.1 | ACS | Introduced new requirements for Home BS | +| 7.5 | Blocking Characteristics | Same requirements as for Local Area BS. The minimum requirements for Home BS when co-located with DECT and WiFi/WLAN are FFS. | +| 7.6.1 | Intermodulation characteristics | Same requirements as for Local Area BS. | +| 8.1. | General | Only Static and Multipath Case 1 for Home BS | +| 8.4 | Demodulation of DCH... | This requirement shall not be applied to Home BS. | +| 8.5 | Demodulation of DCH... | This requirement shall not be applied to Home BS. | +| 8.7 | Perf. Req for RACH | Requirements in Tables 8.10, 8.10A, 8.12, 8.12A shall not be applied for Home BS. | +| 8.10 | Perf. Of ACK/NACK | Not applicable for Home BS | +| 8.12 | Performance of signaling detection for E-DPCCH in multipath fading condition | Requirements in Tables 8.21 and 8.22 are not applicable for Home BS. | + +#### 6.1.1.1 Receiver dynamic range + +The impact of co-channel uplink interference on the Home NodeB has been investigated in [51] for a scenario where the receiver can be exposed to strong blocking signals from un-coordinated UEs. It was shown that the HNB dynamic range requirement needs to be extended by 20dB to protect the HNB from the strong blocking signal of an un-coordinated UE. + +#### 6.1.1.2 Adjacent channel selectivity (ACS) + +The impact of adjacent channel uplink interference on the Home NodeB has been investigated in [52] for a scenario where the receiver can be exposed to strong blocking signals from un-coordinated UEs. It was shown that the HNB ACS requirement needs to be extended by 10dB to protect the HNB from the strong blocking signal of an un-coordinated UE. + +### 6.1.2 Changes on transmitter characteristics + +The main changes on transmitter characteristics were agreed and approved in [36] and [37]. + +#### 6.1.2.1 Base station maximum output power + +Maximum output power, Pmax, of the base station is the mean power level per carrier measured at the antenna connector in specified reference condition. The rated output power, PRAT, of the BS shall be as specified in Table 6.0A in the TS 25.104. In summary: + +- the output power of the HNB is limited to 20 dBm (17 dBm for MIMO) +- a power level of 8 dBm is always accepted +- an upper limit on the output power of HNB is introduced to protect an adjacent-channel operator [37] + +A minimum requirements was also introduced: In normal conditions, the Base station maximum output power shall remain within +2 dB of the manufacturer's rated output power. In extreme conditions, the Base station maximum output power shall remain within +2.5 dB of the manufacturer's rated output power. In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +#### 6.1.2.2 Frequency error + +During the Home NodeB study item a consensus was reached that the Home NodeB is expected to support UE speeds up to 30 kmph, see the RAN4 conclusions in TR 25.820. Since the UEs are anyhow required to operate with speeds up + +document. + +to 250 kmph within a macro cell, the approach here is to keep the same total frequency error tolerance but allow a larger BS frequency error as a result of the smaller Doppler. + +Considering the maximum UE speed of 30 kmph (8.3 m/s), and following the same approach as in TR 25.951 and R4-070687, the corresponding frequency reference error can be calculated as + +$$\Delta_{freq,ppm} = \frac{10^6}{f_c} \cdot \left( \frac{v_{UE,max} \cdot f_c}{c} + \frac{0.05 \cdot f_c}{10^6} - \frac{v_{UE,HNB} \cdot f_c}{c} \right) = \frac{v_{UE,max}}{300} + 0.05 - \frac{v_{UE,HNB}}{300}$$ + +Assuming $v_{UE,max} = 69.4$ m/s (250 kmph), $\Delta_{freq,ppm}$ becomes equal to 0.254 ppm. It is therefore proposed to relax the frequency error requirement for Home BS class to 0.25 ppm. + +The corresponding text proposal [38] was approved in [36] during RAN 4 #48. + +#### 6.1.2.3 Spectrum emission mask + +The BS spectrum emission mask specifies the maximum allowed BS emission level in the frequency range from $\Delta f = 2.5$ MHz to $\Delta f_{max}$ from the carrier frequency. In between 2.5 MHz and 12.5 MHz frequency offsets the BS emissions are also limited by the ACLR requirements. However, for scenarios where the frequency offset to the UMTS Tx band edge is larger than 12.5 MHz, the emissions beyond 12.5 MHz offset, e.g. “ACLR3”, are limited only by the spectrum emission mask. + +![Figure 6.1: Base station spectrum emission mask. The graph plots Power density in 1 MHz [dBm] on the y-axis (from -60 to 0) against Frequency separation from the carrier [MHz] on the x-axis (from 0 to 16). Three curves are shown: 1) SEM (blue line) starts at -10 dBm at 2.5 MHz, drops to -20 dBm at 4 MHz, then to -25 dBm at 8 MHz, and remains at -25 dBm for higher offsets. A label '25.104 SEM P < 31 dBm' is present. 2) Relative ACLR (black line) is constant at -30 dBm from 2.5 MHz to 7.5 MHz, then drops to -35 dBm until 12.5 MHz. A label 'Relative ACLR P = 20 dBm' is present. 3) Absolute ACLR Home BS (red line) is constant at -45 dBm from 2.5 MHz to 7.5 MHz, then drops to -50 dBm until 12.5 MHz. A label 'Absolute ACLR Home BS' is present.](ec42effecdc5bce7bb2bf7a96c954845_img.jpg) + +Figure 6.1: Base station spectrum emission mask. The graph plots Power density in 1 MHz [dBm] on the y-axis (from -60 to 0) against Frequency separation from the carrier [MHz] on the x-axis (from 0 to 16). Three curves are shown: 1) SEM (blue line) starts at -10 dBm at 2.5 MHz, drops to -20 dBm at 4 MHz, then to -25 dBm at 8 MHz, and remains at -25 dBm for higher offsets. A label '25.104 SEM P < 31 dBm' is present. 2) Relative ACLR (black line) is constant at -30 dBm from 2.5 MHz to 7.5 MHz, then drops to -35 dBm until 12.5 MHz. A label 'Relative ACLR P = 20 dBm' is present. 3) Absolute ACLR Home BS (red line) is constant at -45 dBm from 2.5 MHz to 7.5 MHz, then drops to -50 dBm until 12.5 MHz. A label 'Absolute ACLR Home BS' is present. + +Figure 6.1. Base station spectrum emission limits within the UMTS tx band. + +Considering now the current requirements for the Home BS, it is quite straightforward to notice that the ACLR results in considerably stringent emission requirements compared to the spectrum emission mask currently applicable for HNB ( $P < 31$ dBm), see Figure 6.1. Hence, as a result the required ACLR3 becomes considerably smaller than the required ACLR2 as highlighted also in Tdoc R4-080942. + +As a solution to avoid this kind of “jumping” ACLR, it is proposed to introduce an additional requirement, valid only for the Home BS and for frequency offset $12.5$ MHz $< \Delta f < \Delta f_{max}$ . Based on the results in Tdoc R4-080942, and assuming that the maximum output power of the Home BS is less than 20 dBm, it is proposed that the emissions within $12.5$ MHz $< \Delta f < \Delta f_{max}$ shall not exceed: + +$$P - 56 \text{ dBm/MHz, for } 6 \text{ dBm} \leq P < 20 \text{ dBm}$$ + +and + +document. + +-50 dBm/MHz for $P < 6$ dBm. + +The corresponding text proposal [39] was included and approved in [36] + +#### 6.1.2.4 Adjacent channel leakage power ratio (ACLR) + +Based on the findings in Tdoc R4-080939 and R4-080941 the current (relative) ACLR requirements of 45 dBc (5 MHz offset) and 50 dBc (10 MHz offset) are sufficient also for Home BS. However, as proposed by the results in Tdoc R4-081378 and R4-081379, an absolute emission requirement can be introduced for Home BS in addition to the existing relative requirement. System simulation results for this were presented in [49]. The value for the absolute requirement is proposed to be equal to -50 dBm/MHz for both 5 MHz and 10 MHz frequency offsets. The minimum requirement is calculated from the relative requirement or the absolute requirement, whichever is less stringent. + +The corresponding text proposal [40] was included and approved in [36]. + +## 6.2 Changes in 3GPP TS 25.141 + +This section describes the considered changes to base station conformance testing. + +The changes in TS 25.141 are summarised in the following tables.. Requirements which are not shown are applicable to Home BS without any modifications from the existing specifications. + +The necessary modifications to TS 25.141 were approved in [41-43]. The modifications for test models were approved in [44], based on the comparison of different proposals described in [45]. + +**Table 6.2-1 Changes on transmitter characteristics to TS 25.141** + +| Section | Requirement | Discussion / Required Changes | +|---------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.3A | Base station classes | Added a new BS class - Home Base Station. Home Base Stations are characterized by requirements derived from Femto Cell scenarios. | +| 6.2.1 | Base station maximum output power | Added rated output power requirement for Home BS. It was agreed on 20 dBm (without MIMO) or 17 dBm (with MIMO). | +| 6.3 | Frequency error | Added frequency error requirement for Home BS. It was agreed on a minimum frequency error of -0.25ppm-12Hz and maximum frequency error of +0.25ppm+12 Hz. | +| 6.5.2.1 | Spectrum emission mask | Added additional requirements for Home BS. Introduction of table 6.21D and 6.21E. See [41]. | +| 6.5.2.2 | ACLR | Added additional ACLR absolute limit requirement for Home BS. It was agreed that for Home BS, the adjacent channel power (the RRC filtered mean power centered on an adjacent channel frequency) shall be less than or equal to -49.2 dBm/MHz or as specified by the ACLR limit, whichever is the higher. | +| 6.5.3 | TX Spurious emissions | Added Home BS spurious emissions limits for protection of the BS receiver and coexistence with Home BS operating in other bands. Added Tables 6.37C and 6.47. See [41]. | + +**Table 6.2-2 Changes on receiver characteristics to TS 25.141** + +| Section | Requirement | Discussion / Required Changes | +|---------|---------------------------------|------------------------------------------------------------------| +| 7.2 | Reference sensitivity level | Added requirement for Home BS. See [42]. | +| 7.3 | Dynamic range | Added general and additional requirement for Home BS. See [42]. | +| 7.4 | ACS | Added general and additional requirement for Home BS. See [42]. | +| 7.5 | Blocking characteristics | Added minimum and narrowband requirements for Home BS. See [42]. | +| 7.6 | Intermodulation characteristics | Added minimum and narrowband requirements for Home BS. See [42]. | + +document. + +**Table 6.2-3 Changes on demodulation requirements to TS 25.141** + +| Section | Requirement | Discussion / Required Changes | +|---------|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| 8.2 | Demodulation of DCH in static propagation conditions | The requirement is applied to Home BS. See [43]. | +| 8.3.1 | Demodulation of multipath fading case 1 | The requirement is applied to Home BS. See [43]. | +| 8.3.2 | Demodulation of multipath fading case 2 | The requirements shall not be applied to Home BS. See [43]. | +| 8.3.3 | Demodulation of multipath fading case 3 | | +| 8.4 | Demodulation of DCH in moving propagation conditions | | +| 8.5 | Demodulation of DCH in birth/death propagation conditions | | +| 8.5A | Demodulation of DCH in high speed train conditions | | +| 8.8 | RACH performance | Only requirements in static propagation conditions or multipath fading case 1 are applied to Home BS. See [43]. | +| 8.11 | Performance of signaling detection for HS-DPCCH | Only requirements in static propagation conditions or multipath fading case 1 are applied to Home BS. See [43]. | +| 8.12 | Demodulation of E-DPDCH in multipath fading conditions | Only requirements in Pedestrian A are applied to Home BS. See [43]. | +| 8.13.1 | E-DPCCH false alarm in multipath fading conditions | Only requirements in Pedestrian A are applied to Home BS. See [43]. | +| 8.13.2 | E-DPCCH missed detection in multipath fading conditions | | + +**Table 6.2-4 Modifications of the transmitter test models in TS 25.141** + +| Section | Requirement | Discussion / Required Changes | +|----------|--------------|--------------------------------------------------------------------------------------------------------------------| +| 6.1.1.1 | Test Model 1 | For Home base station, additional options of this test model containing 8 and 4 DPCH are also specified. See [44]. | +| 6.1.1.3 | Test Model 3 | For Home base station, additional options of this test model containing 8 and 4 DPCH are also specified. | +| 6.1.1.4A | Test Model 5 | For Home base station, an additional option of this test model containing 4 HS-PDSCH + 4 DPCH is also specified. | +| 6.1.1.4B | Test Model 6 | For Home base station, an additional option of this test model containing 4 HS-PDSCH + 4 DPCH is also specified. | + +# 7 Guidance on how to control HNB interference + +## 7.1 HNB measurements + +Several types of measurements that HNB can perform are listed in the following subsections. The objectives of the HNB measurements are + +- to provide sufficient information to the HNB for the purpose of interference mitigation + +document. + +- to provide sufficient information to the HNB such that the HNB coverage can be maintained. + +According to the measurement type, some of these measurements can be collected through Connected Mode UEs attached to the HNB or via a DL Receiver function within the HNB itself. Such DL receiver function is also called Network Listen Mode (NLM), Radio Environment Measurement (REM) or “HNB Sniffer”. + +These measurements can also be used during the HNB self-configuration process. + +### 7.1.1 Measurements from all cells + +This section identifies the potential measurements performed by HNB during self-configuration and normal operation. Based on the measurements in Table 7.1.1-1, the HNB can obtain useful information from its surrounding cells for purposes such as interference management. + +**Table 7.1.1-1: HNB measurements from surrounding cells** + +| Measurement Type | Purpose | Measurement Source(s) | +|-------------------------------|--------------------------------------------------------------------------------------|-----------------------| +| Co-channel carrier RSSI | Calculation of co-channel DL interference towards HUEs from neighbouring cells | HNB DL Receiver HUE | +| Adjacent channel carrier RSSI | Calculation of adjacent channel DL interference towards HUEs from neighbouring cells | HNB DL Receiver HUE | +| CPICH Ec/No | Calculation of DL interference towards HNB | HNB DL Receiver HUE | +| RTWP | Calculation of UL interference towards HNB | HNB Physical Layer | + +The CPICH Ec/No measurement could be used in the scenario where the HNB is installed near a macro NodeB such that the HNB coverage is sufficient to meet the user requirements. + +The HNB downlink interference level depends on the HNB location and coverage area. It can be indicated whether the interference at the coverage edge is larger than the interference at the location of HNB by a pre-defined value. Therefore, HNB’s coverage performance can be improved by changing the location of HNB if needed. The downlink interference at the coverage edge can be obtained by UE measurement reports. + +The interference level can be indicated to the HNB’s owner. With this indication, the owner can make a decision as to where the proper place is to install HNB. + +HNB could use the RTWP measurement to monitor the uplink interference. For example, a RTWP measurement value larger than a pre-defined threshold (where an interfering MUE is close to HNB) would mean that the MUE’s Tx power would cause significant interference towards the HNB. + +### 7.1.2 Measurements to identify macro cells + +This section identifies the potential measurements performed by HNB during self-configuration and normal operation. Based on the measurements in Table 7.1.2-1, the HNB can obtain useful information to identify its surrounding macrocells and indirectly identifies other HNBs nearby for purposes such as mobility handling. + +document. + +**Table 7.1.2-1: HNB measurements to identify macro cells** + +| Measurement Type | Purpose | Measurement Source(s) | +|-------------------------|---------------------------------------------------------------------|------------------------------| +| PLMN ID | Identification of operator
Distinction between macrocell and HNB | HNB DL Receiver | +| Cell ID | Identification of surrounding macrocells | HNB DL Receiver | +| LAC | Distinction between macrocell and HNB | HNB DL Receiver | +| RAC | Distinction between macrocell and HNB | HNB DL Receiver | + +Note: These measurements are all made as decoded System Information IEs. + +### 7.1.3 Measurements from macro cell layer + +This section identifies the potential measurements performed by HNB during self-configuration and normal operation. Based on the measurements in Table 7.1.2-1, the HNB can obtain useful information from its surrounding macrocells for purposes such as interference management. + +**Table 7.1.3-1: HNB measurements from surrounding macro cells** + +| Measurement Type | Purpose | Measurement Source(s) | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| Co-channel CPICH RSCP | Calculation of co-channel DL interference towards macro UEs (from HNB)
Calculation of co-channel UL interference towards macro layer (from HUEs) | HNB DL Receiver
HUE | +| Adjacent channel CPICH RSCP | Calculation of adjacent channel DL interference towards macro UEs (from HNB)
Calculation of adjacent channel UL interference towards macro layer (from HUEs) | HNB DL Receiver
HUE | +| P-CPICH Tx Power 1 | Calculation of pathloss to MNB | HNB DL Receiver | + +Note 1: “P-CPICH Tx Power” is a decoded System Information IE, rather than a direct physical layer measurement + +### 7.1.4 Measurements of other HNB cells + +This section identifies the potential measurements performed by HNB during self-configuration and normal operation. Based on the measurements in Table 7.1.4-1, the HNB can obtain useful information from its adjacent HNBs for purposes such as interference management. + +**Table 7.1.4-1: HNB measurements from adjacent HNBs** + +| Measurement Type | Purpose | Measurement Source(s) | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| Co-channel CPICH RSCP | Calculation of co-channel DL interference towards neighbour HUEs (from HNB)
Calculation of co-channel UL interference towards neighbour HNBs (from HUEs) | HNB DL Receiver
HUE | +| Adjacent channel CPICH RSCP | Calculation of adjacent channel DL interference towards neighbour HUEs (from HNB)
Calculation of adjacent channel UL interference towards neighbour HNBs (from HUEs) | HNB DL Receiver
HUE | + +document. + +## 7.2 Control of HNB downlink interference + +### 7.2.1 Control of HNB power + +The following subsections provide some guidance on the control of HNB power relative to its surrounding macro cells and/or other HNBs, as part of interference mitigation techniques used by the HNB. The control mechanisms can be either used during HNB normal operation or during self-configuration process. + +#### 7.2.1.1 Control of HNB power with respect to macro layer + +This section provides guidelines on setting the HNB total DL transmit power (data and control channel power) based on the following deployment scenarios: + +- HNB and MNB operate in either co-channel or adjacent channel +- HNB situated far away from the MNB (i.e. cell edge scenario) +- HNB situated close to the MNB (i.e. cell site scenario) + +Based on these deployment scenarios, it is therefore expected that there will be trade-off between the HUE performance and MUE performance when the HNB transmit power is varied. + +First the co-channel deployment of HNB and MNB is analyzed for both cell site and cell edge cases. The analysis setup assumes a MNB and a HNB. A MUE is connected to the MNB and a HUE is connected to the HNB as shown in Figure 7.2.1.1-1. + +![Figure 7.2.1.1-1: DL Interference Setup. The diagram shows a Macro NodeB (MNB) at the top, a Home NodeB (HNB) at the bottom right, a Mobile User Equipment (MUE) at the top right, and a Home User Equipment (HUE) at the bottom left. The HNB, HUE, and MUE are enclosed in a rectangular box. Dashed arrows represent signal paths: from MNB to HUE (labeled X), from MNB to HNB (labeled X), from MNB to MUE (labeled X), from HUE to HNB (labeled Y), and from HNB to MUE (labeled Z).](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +Figure 7.2.1.1-1: DL Interference Setup. The diagram shows a Macro NodeB (MNB) at the top, a Home NodeB (HNB) at the bottom right, a Mobile User Equipment (MUE) at the top right, and a Home User Equipment (HUE) at the bottom left. The HNB, HUE, and MUE are enclosed in a rectangular box. Dashed arrows represent signal paths: from MNB to HUE (labeled X), from MNB to HNB (labeled X), from MNB to MUE (labeled X), from HUE to HNB (labeled Y), and from HNB to MUE (labeled Z). + +Figure 7.2.1.1-1: DL Interference Setup + +##### 7.2.1.1.1 Co-channel deployment + +In this section, the performance of HNB when deployed co-channel with MNB is analysed, for both cell site and cell edge cases. For the analysis, some simplified assumptions have been made in an effort to show the basic bottlenecks that arise from such deployment scenarios. + +The system model is also simplified (compared to a real situation) as shown in Figure 7.2.1.1-1, which consists of one MNB and one HNB. Only one MUE is connected to the MNB and only one HUE is connected to the HNB. We assume the pathloss from the MUE, HUE, HNB to the MNB are all equal to $PL\_MNB$ , i.e., $X=PL\_MNB$ . The parameters for the setup are given in Table 7.2.1.1.1-1. The total received signal level (i.e., RSSI) in the table includes the signals received from all NBs (MNBs and HNBs) other than the HNB under consideration. The RSSI is assumed to + +document. + +be the same at the HNB, HUE and MUE. Both the MUE and the HUE are placed at PL\_HNB from the HNB, i.e., $Y=Z=PL\_HNB$ . + +**Table 7.2.1.1.1-1: Parameters for co-channel deployment: cell edge versus cell site** + +| Parameters | Cell Edge | Cell Site | +|----------------------------|-----------|-----------| +| PL to MNB [dB] | 140 | 100 | +| RSSI [dBm] | -95 | -60 | +| MNB RSCP [dBm] | -107 | -67 | +| MNB maximum Tx Power [dBm] | 43 | 43 | +| MNB Tx CPICH Ec [dBm] | 33 | 33 | +| HNB CPICH Ec/Ior [dB] | -10 | -10 | +| MNB load factor [%] | 50 | 50 | +| HNB load factor [%] | 100 | 100 | + +In the analysis, the HNB Tx power is varied and the corresponding CPICH Ec/No of both the MUE and the HUE are calculated for different values of PL\_HNB. + +For the Cell Edge case the trade-off results are shown in Figure 7.2.1.1.1-2. + +![Figure 7.2.1.1.1-2: Trade-off between HUE and MUE performance as a function of HNB tx power at cell edge. The graph shows CPICH Ec/No (dB) on the y-axis (from -25 to -5) versus HNB Tx Power (dBm) on the x-axis (from -10 to 20). There are two sets of curves: red for MUE and green for HUE. Each set has four lines for PL-HNB values of 60dB, 70dB, 80dB, and 90dB. For the Cell Edge case, the HUE curves (green) generally show higher CPICH Ec/No values than the MUE curves (red) for the same PL-HNB value. As HNB Tx Power increases, the CPICH Ec/No for both MUE and HUE decreases. The HUE curves are relatively flat around -10 dB, while the MUE curves show a more significant drop, especially for lower PL-HNB values.](b86f4fd2c05bc69b4e99efd5f15b743d_img.jpg) + +Figure 7.2.1.1.1-2: Trade-off between HUE and MUE performance as a function of HNB tx power at cell edge. The graph shows CPICH Ec/No (dB) on the y-axis (from -25 to -5) versus HNB Tx Power (dBm) on the x-axis (from -10 to 20). There are two sets of curves: red for MUE and green for HUE. Each set has four lines for PL-HNB values of 60dB, 70dB, 80dB, and 90dB. For the Cell Edge case, the HUE curves (green) generally show higher CPICH Ec/No values than the MUE curves (red) for the same PL-HNB value. As HNB Tx Power increases, the CPICH Ec/No for both MUE and HUE decreases. The HUE curves are relatively flat around -10 dB, while the MUE curves show a more significant drop, especially for lower PL-HNB values. + +**Figure 7.2.1.1.1-2: Trade-off between HUE and MUE performance as a function of HNB tx power at cell edge** + +It is observed that at the cell edge, the HNB needs to transmit at low power to maintain the required coverage for the MUE. Also, as the desired coverage radius reduces, the HNB power has to be lower to maintain the MUE performance. + +For the Cell Site case the tradeoff results are shown in Figure 7.2.1.1.1-3. At the cell site the HNB has to increase its power to maintain good coverage for the HUE while not creating “much” interference for the MUE. More power is + +document. + +required to maintain the same coverage for the HUE compared to the cell-edge case, due to larger interference from the MNB. + +![Line graph titled 'Cell Site' showing CPICH Ec/No (dB) vs HNB Tx Power (dBm). The y-axis ranges from -25 to -5, and the x-axis ranges from -10 to 20. There are two sets of data series: MUE (red lines with various markers) and HUE (green lines with various markers) for different PL_HNB values (60dB, 70dB, 80dB, 90dB, 100dB). MUE performance generally decreases as HNB Tx Power increases, while HUE performance increases. Specific markers include asterisks, circles, squares, and triangles corresponding to the different PL_HNB values in the legend.](6fc99b56d4021cf515d190c3a0da183f_img.jpg) + +Line graph titled 'Cell Site' showing CPICH Ec/No (dB) vs HNB Tx Power (dBm). The y-axis ranges from -25 to -5, and the x-axis ranges from -10 to 20. There are two sets of data series: MUE (red lines with various markers) and HUE (green lines with various markers) for different PL\_HNB values (60dB, 70dB, 80dB, 90dB, 100dB). MUE performance generally decreases as HNB Tx Power increases, while HUE performance increases. Specific markers include asterisks, circles, squares, and triangles corresponding to the different PL\_HNB values in the legend. + +**Figure 7.2.1.1.1-3: Trade-off between HUE and MUE performance as a function of HNB tx power at cell site** + +In these figures, different PL\_HNB values correspond to different HNB deployment scenarios. Depending on the particular deployment scenario (e.g., suburban, urban, dense-urban), the HNB can have different coverage radius (i.e., link budget). For example, in a suburban scenario, the HNB coverage can be 100dB whereas a lower HNB coverage radius (e.g., 70dB) may be more suitable for dense-urban deployments. It is seen that in the cell edge scenario, using high HNB Tx power results in poor CPICH Ec/No for the MUE. On the other hand, when HNB is close to the macrocell site, a low HNB Tx power results in poor CPICH Ec/No for the HUE. As the HNB Tx power increases, the MUE CPICH Ec/No degrades. Therefore, the HNB transmit power needs to be adjusted properly to maintain an acceptable performance for both the HNB and the MNB. + +In order to exemplify how to adjust the HNB DL transmit power, we employ the following algorithm, where the transmit power of HNB is determined based on the results of a few measurements. Each HNB measures the total signal strength ( $N_0$ ) from all the other NodeBs (including MNBs and HNBs). It also measures the pilot strength from the best co-channel and adjacent-channel MNBs. Based on these measurements, the HNB can calculate its transmit power: + +1. To maintain an CPICH Ec/No of -18dB for a MUE located $X_1$ dB away from the HNB on the same channel (i.e., protect the co-channel macro user) +2. To maintain an CPICH Ec/No of -18dB for a MUE located $X_2$ dB away from the HNB on the adjacent channel (i.e., protect the adjacent channel macro user) +3. To make sure that HNB is not causing unnecessary interference to others by enforcing a cap on CPICH Ec/No of the HUE of -15 dB at $X_3$ dB away from the HNB. + +Using the algorithm above with $X_1=X_3=PL\_HNB$ , the calibrated HNB transmit powers for the co-channel case for different PL\_HNB values are shown in the following table. + +document. + +**Table 7.2.1.1.1-2: Calibrated HNB transmit power for cell-edge and cell-site scenarios** + +| PL_HNB (dB) | 60 | 70 | 80 | 90 | 100 | +|---------------------------------------------|-----------|-----------|-----------|-----------|------------| +| Cell Edge: HNB Transmit Power in dBm | -10 | -10 | -10 | -7.9 | 2.1 | +| Cell Site: HNB Transmit Power in dBm | -3.2 | 6.8 | 16.8 | 20 | 20 | + +The performance of the HUE and the MUE at the specified coverage radius and specified HNB output power is given in Table 7.2.1.1.1-3 and 7.2.1.1.1-4 for cell edge and cell site cases, respectively. + +**Table 7.2.1.1.1-3: Performance for cell-edge scenario based on the HNB tx powers in Table 7.2.1.1.1-2** + +| PL_HNB (dB) | 60 | 70 | 80 | 90 | 100 | +|-----------------------------|-----------|-----------|-----------|-----------|------------| +| MUE CPICH Ec/No (dB) | -37 | -27 | -18 | -14 | -14 | +| HUE CPICH Ec/No (dB) | -10 | -10 | -11.3 | -15 | -15 | + +**Table 7.2.1.1.1-4: Performance for cell-site scenario based on the HNB tx powers in Table 7.2.1.1.1-2** + +| PL_HNB (dB) | 60 | 70 | 80 | 90 | 100 | +|-----------------------------|-----------|-----------|-----------|-----------|------------| +| MUE CPICH Ec/No (dB) | -8.8 | -8.8 | -8.8 | -7.5 | -7 | +| HUE CPICH Ec/No (dB) | -15 | -15 | -15 | -20.5 | -30 | + +In general, we observe that at the cell edge deployment, the HNB should transmit at lower power compared to the cell site deployment. This is to maintain the minimum level of performance requirements for the MUE at the coverage radius. In some cases, the HNB will end up hitting the minimum transmit power level (e.g., -10dBm) in an attempt to satisfy the requirement for the MUE. For the cell-site, in some cases the HNB will end up hitting the maximum transmit power level (e.g., +20dBm) in an attempt to provide coverage for the HUE at the HNB coverage radius. + +##### 7.2.1.1.2 Adjacent channel deployment + +For the adjacent channel scenario, we consider the case when the two operators have macrocell Node Bs that are *not collocated*. The simulation parameters for the adjacent operator deployment are shown in Table 7.2.1.1.2-1. + +**Table 7.2.1.1.2-1: Parameters for adjacent channel non-collocated operator deployment.** + +| Parameters | Operator 1 | Adjacent Operator | +|-------------------|-------------------|--------------------------| +| PL to MNB | 100 dB | 120 dB | +| RSSI | -60 dBm | -80 dBm | +| MNB RSCP | -67 dBm | -87 dBm | + +The other simulation parameters are the same as for the co-channel deployment. A NodeB ACLR of 45dB and UE ACS of 33 dB are assumed, which result in an ACIR of 33 dB. The MUE and the HUE will have the same pathloss to the HNB (after taking the ACIR into account), as this is the worst case envisioned in this study. + +The trade-off between the performance of the MUE and the HUE as a result of varying the HNB transmit power is shown in Figure 7.2.1.1.2-1. + +document. + +![Figure 7.2.1.1.2-1: Trade-off between HUE and MUE (on adjacent channel) performance as a function of HNB tx power for non-collocated operators. The graph plots CPICH Ec/No (dB) on the y-axis (from -25 to -5) against HNB Tx Power (dBm) on the x-axis (from -10 to 20). It shows eight curves: four for MUE (red lines with markers) and four for HUE (green lines with markers) at different PL_HNB values (37, 47, 57, 67, 70, 80, 90, 100 dB). MUE performance generally decreases as HNB power increases, while HUE performance increases.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Figure 7.2.1.1.2-1: Trade-off between HUE and MUE (on adjacent channel) performance as a function of HNB tx power for non-collocated operators. The graph plots CPICH Ec/No (dB) on the y-axis (from -25 to -5) against HNB Tx Power (dBm) on the x-axis (from -10 to 20). It shows eight curves: four for MUE (red lines with markers) and four for HUE (green lines with markers) at different PL\_HNB values (37, 47, 57, 67, 70, 80, 90, 100 dB). MUE performance generally decreases as HNB power increases, while HUE performance increases. + +**Figure 7.2.1.1.2-1: Trade-off between HUE and MUE (on adjacent channel) performance as a function of HNB tx power for non-collocated operators** + +The calculated HNB transmit powers as obtained from the example algorithm described above with $X1=X3=PL\_HNB$ and $X2=47\text{dB}$ are in the following table. + +**Table 7.2.1.1.2-2: Calibrated HNB transmit power for adjacent channel non-collocated operator deployment.** + +| PL_HNB (dB) | 70 | 80 | 90 | 100 | +|---------------------------|-----|------|------|------| +| HNB Transmit Power in dBm | 6.8 | 10.6 | 10.6 | 10.6 | + +The CPICH Ec/No performance of the HUE and the MUE at the specified coverage radius and specified HNB output power is given in Table 7.2.1.1.2-3. + +**Table 7.2.1.1.2-3: Performance for adjacent-channel scenario based on the HNB tx powers in Table 8.6** + +| PL_HNB (dB) | 70 | 80 | 90 | 100 | +|----------------------|-------|-----|-------|-------| +| MUE CPICH Ec/No (dB) | -14.7 | -18 | -18 | -18 | +| HUE CPICH Ec/No (dB) | -15 | -20 | -29.6 | -39.5 | + +It is observed that the although the HNB is close to the adjacent-channel cell site, the calibrated powers for the HNB are lower than those in Table 7.2.1.1.1.2-2 for the co-channel cell site case. This is because the HNB has to lower its power to maintain the coverage for the adjacent operator's MUE. The case is of interest when the MNBs of the two operators are not collocated. + +document. + +#### 7.2.1.2 Centralized HNB power control + +From the previous studies we noticed that when HNB tries to self calibrate the transmission power it sometime faces an important bottleneck: the power necessary for guaranteed coverage is higher than a level which would also insure the co- and adjacent channels protection. In the scenarios we assumed, there are cases when either one of them has to be compromised in the favour of the other. One of the problems is that HNB measurements on the surrounding environment are not precise enough (i.e. we refer at the tolerance of the measurements, how often the HNB can perform these measurement, etc.), to allow the presented algorithm to calculate the ideal transmission power for the respective moment in time. + +In this section, we explore an alternative approach, when the HNB power control algorithm is implemented in a “*centralized*” manner. The HNBs may be initially configured with default thresholds for one or more parameters: HNB data rate, macro cell dead-zone, CIR of HUEs, detection of a nearby macro UE etc. The individual HNB then locally calibrates the transmission power to meet these thresholds by monitoring the relevant parameters using the algorithm above. As traffic conditions vary, the HNB gateway, which is an element owned by the operator deploying HNBs,, may compute the desired thresholds for these parameters and communicate to the HNBs at a slower or faster time-scale. This network command is not time-critical and does not rely on all HNBs being able to “hear” the network. It is meant to simply optimize system performance. + +Three options for enhancing the power adjustment of HNBs are proposed below. Note that these techniques are not mutually exclusive, and may co-exist with each other. + +- **Usage of macro network specific information.** The desired thresholds for the relevant system parameters (data rate, macro cell dead-zone coverage etc) are computed by the network for all HNBs. To do this, the network may take into account macro NodeB load, number of active HNBs, distance of the HNB to the macro cell, fading environment, time-of-day etc. The network command with threshold is communicated to the HNB either through the Broadcast Control Channel (BCCH) or the backhaul such as DSL or cable connection. By sharing information between HNB and macro NodeBs using the backhaul, it is possible for HNB to get more information than otherwise could obtain by listening the broadcast channels. For example, the close-by macro UE’s target signal to noise ratio (SNR), measured SNR, and received power are information that can be utilized for HNB power adjustment in a more proper way with respect to the interference caused to the surrounding macro networks However, it is required to modify the signalling at the macro layer to support this functionality and carefully design the backhaul information exchange by controlling the overhead. +- **Pseudo-static power assignment for HNB.** In addition to dynamic power calibration, it may be desirable to have a pseudo-static power assignment to the HNB. The transmit power of the HNB is a simple function of the HNB’s geographical location. The default value for transmit power and a geographical zone can be pre-configured at the time of buying a HNB or when there is a change in the location of the HNB. Any changes to the zone-wise power setting of HNB can be communicated at a slower time-scale over BCCH or the backhaul such as DSL or cable connection. However, it is again required to modify the signalling at the macro layer to support this functionality. +- **Control channel – data channel power ratio.** The proposal is to manipulate the ratio between HNB control channels power and HNB data channels power. For example, depending on the expected throughput, we can fix the control channel power, while reducing the maximum data channel power. This will ensure that the coverage area (for the assumed expected throughput) for HUE does not diminish, but the allowed total transmit power of HNBs reduces. This will result in improved macro cell coverage and reduced HNB maximum power requirement, at the same time. Note that the HNBs can support relatively high data rates even at low data channel power settings. + +#### 7.2.1.3 Control of HNB power with respect to other HNB + +Similar principles as in Section 7.2.1.1 and Section 7.2.1.2 can be applied to set the Tx power of the HNB in a dedicated deployment. One difference is that the co-channel macro condition does not apply in this case. For example, the transmit power of HNB may be determined as follows. + +Each HNB measures the total signal strength ( $N_0$ ) from all the other NodeBs (including MNBs and HNBs). It also measures the pilot strength from the best MNB on the adjacent channel. Based on these measurements, the HNB determines its transmit power: + +- i. To maintain an $CPICH E_c/N_0$ of -18dB for a MUE located X2 dB away from the HNB on the adjacent channel (i.e., protect the adjacent channel macro user) + +document. + +- ii. To make sure that HNB is not causing unnecessary interference to others by enforcing a cap on CPICH Ec/No of the HUE of -15 dB at X3 dB away from the HNB. + +#### 7.2.1.4 Control of HNB power or macro UE based on network control + +When the HNBs are deployed on the same channel as the macro network, macro UEs can experience interference from HNB DL when the macro UE is nearby a HNB or gets close to the HNB. One potential solution for mitigating this interference is to control HNB DL or macro UE adaptively through enhanced interference coordination. + +Potential methods for controlling HNB transmission power adaptively according to the macro UE behavior are as follows; + +- i. To reduce the interference to macro UE from HNB, it is useful to reduce the HNB CPICH power temporarily (this is only applicable when no HUEs exist on the HNB) +- ii. To avoid the interference to macro UE from HNB, it is useful to halt the HNB CPICH power temporarily (this is only applicable when no HUEs exist on the HNB) + +A potential method for controlling macro UE adaptively according to the macro UE behavior is as follows; + +- i. To avoid the interference to macro UE from HNB, the macro UE is driven out to another carrier by the network. (this is only applicable to the areas deploying overlay carriers) + +These solutions may need trigger from macro UEs. AS and NAS procedures may be utilized for this purpose. + +#### 7.2.1.5 Enhancements for Control of HNB Tx Power + +##### 7.2.1.5.1 UE-Assisted Power Calibration + +To deal with scenarios where there is a significant mismatch between the RF conditions measured by the HNB and those experienced by the MUEs and HUEs, it is useful to use UE measurements (or measurement statistics) to optimize the calibrated HNB Tx power. This is particularly useful in co-channel deployments and can provide better protection for MUEs while maintaining good HNB coverage for the HUEs. + +For example, if the HNB is placed near a window, HNB may see a stronger signal from MNB than the indoor HUE. In this case, HNB power calibration algorithm responding to the higher level of signal from the MNB, may set the transmit power of the HNB to a higher value than needed for the coverage of the home. This higher power may create a coverage hole for the MUEs that may be walking on the street close to the HNB premise. Therefore, if both the measurements from MUEs and HUEs (e.g. path loss to HNB), are made available to the HNB, then HNB can fine-tune its HNB Tx power. + +##### 7.2.1.5.2 Minimum HNB Tx power + +According to [57], the RRC signalling limits the lowest value for Primary CPICH Tx Power to -10 dBm. For CPICH Ec/Ior of -10 dB, this limits the lowest power transmit by a HNB to 0 dBm. However, in certain cases such as when the HNB is located at macro cell edge, the effectiveness of HNB power calibration algorithms is reduced because of 0 dBm limit imposed by the CPICH signalling. Since the HNB Tx power calibration algorithm may indicate a value less than 0 dBm as the desired value, it is useful to reduce the lower limit that can be signalled for CPICH Tx Power. This should be done in a manner that ensures backward compatibility with legacy UEs. + +document. + +## 7.3 Control of HNB uplink interference + +The guidance in this section addresses issues related to UL interference. The specific cases considered are: + +- a) how to minimise UL interference from HUEs towards the macro layer and other neighbour HNBs +- b) how to accommodate UL interference from uncontrolled (e.g. macro) UEs towards the HNB + +### 7.3.1 Control of HUE allowable transmit power + +This is to address UL interference from HUEs towards the macro layer and other neighbour HNBs. This is especially significant when a HUE is at the edge of its coverage, for example outside the property, but has good visibility of a neighbouring cell. Under such extreme conditions the UL power transmitted by the HUE could cause a considerable noise rise at the macro NodeB impacting its UL capacity. + +Such conditions are extreme and potentially unlikely in practice; HUE transmit levels will not typically cause a significant noise rise at neighbour cells. However to cover these extreme cases a maximum limit for the allowed transmit power of HUEs can be defined. + +In order to evaluate the potential level of UL interference that can be caused by a HUE, it is necessary to estimate the pathloss from the vicinity of the HNB to the neighbouring NodeBs. The pathloss from the vicinity of the HNB to the neighbouring NodeBs can be derived from measurements of CPICH RSCP of the neighbouring cells – potentially made by UEs attached to the HNB or by the HNB itself using a Downlink Receive mode of operation. Details of these measurements can be found in Section 7.1. + +Based on the pathloss and other related parameters, the HNB can then determine a maximum allowed HUE transmit power, such that the noise rise experienced at the neighbour cells is constrained to be within an acceptable limit. This maximum power level would be signalled to the HUE as part of its normal RRC connection setup procedure. Further, periodic and/or event-triggered pathloss measurements made by the UEs can be used by the HNB to update the maximum allowable UE transmit power or a correction factor that used to offset the initial maximum allowable UE transmit power determined during the HNB self-configuration. The updated value can be signalled to the UE using e.g., Radio Bearer Reconfiguration message. + +Alternatively, a fixed “cap” on the HUE transmit power could be defined irrespective of the proximity of the macro NodeB. Such approach offers simpler HNB implementation. However, due to no adaptation in the HUE transmit power level, if the cap is set too high, then this will create high UL interference. On the other hand, if the cap is set too low, then the UL interference is reduced at the expense of a potential reduction in the HUE UL throughput. Therefore, this limit would need to be selected such that the noise rise generated at the macro layer was acceptable in the worst case co-channel deployment scenario. A suggested value for this limit is 21dBm. + +The pros and cons of these mitigation techniques can be summarised in Table 7.3.1-1. + +**Table 7.3.1-1: HUE Allowable transmit power control techniques - pros and cons** + +| HUE Allowable Transmit Power Control techniques | Pros | Cons | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Fixed “cap” | simple HNB implementation
no additional signalling requirements | potential high UL interference created by HUE(s) if cap is not set optimally
high UL interference created by HUE(s) transmitting at consistently high Tx power (e.g. cell edge scenarios) | +| Dynamic | reduced UL interference created by HUE(s) transmitting at high Tx power
improved HNB performance | additional signalling required to adjust the allowable HUE Tx power
additional HNB RRM implementation | + +The noise rise at the MNB due to the HUE UL transmission can be determined from the estimated pathloss, as shown in the following link budget example. Table 7.3.1-2 shows the parameters used on the link budget analysis. + +document. + +Note that “estimated pathloss” is the difference between the MNB “CPICH Tx Power” as indicated in its System Information and the CPICH RSCP as received at the HNB. Therefore “estimated pathloss” is equivalent to actual pathloss minus the MNB and HNB antenna gains. + +**Table 7.3.1-2: Link Budget example parameters** + +| Parameter | Value | Formula | +|--------------------------|-----------------------|--------------------------------------------------| +| Thermal noise density | -174 dBm/Hz | ND_t | +| Bandwidth | 3.84 MHz | BW | +| Thermal noise power | -108.16 dBm | $N\_t = ND\_t + 10\log(BW \cdot 10^6)$ | +| MNB Noise Figure | 5 dB | NF | +| MNB receiver noise floor | -103.16 dBm | $N\_rx = N\_t + NF$ | +| MNB antenna gain | 14 dBi | Gant_m | +| HNB antenna gain | 0 dBi | Gant_h | +| Actual Pathloss | 100 dB (for example) | PL | +| Pathloss estimate | 86 dB | $PL\_Est = PL - Gant\_m - Gant\_h$ | +| HUE tx power | -30 dBm (for example) | H_tx | +| HUE antenna gain | 0 dBi | Gant_ue | +| ACLR | 0 dB (co-channel) | ACLR | +| HUE rx power at MNB | -116 dBm | $H\_rx = H\_tx + Gant\_ue - PL - ACLR + Gant\_m$ | +| Noise rise due to HUE | 0.22 dB | $NR = 10\log( 1 + \log2lin(H\_rx - N\_rx) )$ | + +Figure 7.3.1-1 and Figure 7.3.2-2 show the noise rise at the MNB vs HUE transmit power, for a range of pathloss values. + +![Line graph titled 'Noise Rise due to HUE UL Transmission: co-channel'. The Y-axis is 'Noise Rise at MNB (dB)' ranging from 0 to 40. The X-axis is 'HUE Tx Power (dBm)' ranging from -20 to 20. Three curves are shown for different pathloss (PL) values: PL = 100 dB (blue), PL = 120 dB (red), and PL = 140 dB (magenta). The blue curve shows a linear increase in noise rise with transmit power. The red and magenta curves show a more gradual increase, with the red curve being higher than the magenta curve.](7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg) + +| HUE Tx Power (dBm) | Noise Rise at MNB (dB) for PL = 100 dB | Noise Rise at MNB (dB) for PL = 120 dB | Noise Rise at MNB (dB) for PL = 140 dB | +|--------------------|----------------------------------------|----------------------------------------|----------------------------------------| +| -20 | 2 | 0 | 0 | +| -10 | 8 | 0 | 0 | +| 0 | 14 | 2 | 0 | +| 10 | 20 | 8 | 1 | +| 20 | 26 | 14 | 2 | + +Line graph titled 'Noise Rise due to HUE UL Transmission: co-channel'. The Y-axis is 'Noise Rise at MNB (dB)' ranging from 0 to 40. The X-axis is 'HUE Tx Power (dBm)' ranging from -20 to 20. Three curves are shown for different pathloss (PL) values: PL = 100 dB (blue), PL = 120 dB (red), and PL = 140 dB (magenta). The blue curve shows a linear increase in noise rise with transmit power. The red and magenta curves show a more gradual increase, with the red curve being higher than the magenta curve. + +**Figure 7.3.1-1: Noise rise at co-channel MNB** + +document. + +![Figure 7.3.2-2: Noise rise at adjacent channel MNB. A line graph showing Noise Rise at MNB (dB) on the y-axis (0 to 7) versus HUE Tx Power (dBm) on the x-axis (-20 to 20). Three curves are shown for different pathloss (PL) values: PL = 100 dB (blue), PL = 120 dB (red), and PL = 140 dB (magenta). The blue curve shows a significant increase in noise rise as transmit power increases, reaching approximately 6.5 dB at 20 dBm. The red and magenta curves remain near 0 dB across the entire power range.](8f38356601e137ac471fc4771b9c5a5c_img.jpg) + +| HUE Tx Power (dBm) | PL = 100 dB (dB) | PL = 120 dB (dB) | PL = 140 dB (dB) | +|--------------------|------------------|------------------|------------------| +| -20 | 0.0 | 0.0 | 0.0 | +| -15 | 0.0 | 0.0 | 0.0 | +| -10 | 0.0 | 0.0 | 0.0 | +| -5 | 0.0 | 0.0 | 0.0 | +| 0 | 0.1 | 0.0 | 0.0 | +| 5 | 0.4 | 0.0 | 0.0 | +| 10 | 1.0 | 0.0 | 0.0 | +| 15 | 2.5 | 0.0 | 0.0 | +| 20 | 6.5 | 0.1 | 0.0 | + +Figure 7.3.2-2: Noise rise at adjacent channel MNB. A line graph showing Noise Rise at MNB (dB) on the y-axis (0 to 7) versus HUE Tx Power (dBm) on the x-axis (-20 to 20). Three curves are shown for different pathloss (PL) values: PL = 100 dB (blue), PL = 120 dB (red), and PL = 140 dB (magenta). The blue curve shows a significant increase in noise rise as transmit power increases, reaching approximately 6.5 dB at 20 dBm. The red and magenta curves remain near 0 dB across the entire power range. + +**Figure 7.3.2-2: Noise rise at adjacent channel MNB** + +From these characterisations, the HNB can select a maximum allowable HUE transmit power based on the estimated pathloss, the desired limit to the noise rise at the MNB and the RSCP and/or RSSI levels of other neighbour NodeBs. + +### 7.3.2 Control of HNB noise rise threshold + +This is a mitigation technique to address UL interference from uncontrolled macro or other HNB UEs towards the HNB. This is especially significant for CSG deployments, as illustrated by the following scenarios: + +1. Uncontrolled UEs may be located within the premises where the HNB is installed while still being attached to an external macro network. In such cases the macro UE's transmit power will be high while the pathloss to the HNB will be small. +2. A HUE can generate a large UL noise rise at the HNB if the pathloss is very small and the HUE cannot be powered down due to limited dynamic range. + +This mitigation approach also applies to the use of HSUPA and is associated with the UL scheduler. Specifically the scheduler in the HNB is configured to dynamically allow a greater UL noise rise (rise over thermal) than would normally be the case for a macro NodeB. This ensures that the HNB scheduler will be able to continue to grant significant capacity on the UL, so that HUE traffic throughput can be maintained, in the presence of an interfering macro UE or when a HUE cannot be powered down. + +Adjustment of the UL noise rise threshold can be made by the HNB, driven by measurements of receive total wideband power (i.e. RTWP) or other similar measurement entities on the UL (as outlined in Section 7.1). Blocking levels of UL noise rise due to out of cell interference can be detected and the noise rise threshold adjusted accordingly. This adjustment would only need to be made temporarily while the UL interference was strong and as the noise rise was seen to fall the noise rise threshold could be returned to its normal operating value. However, in the presence of such greater UL noise rise, the HNB receiver should be designed so as to ensure proper system stability for HUEs (e.g., in the presence of bursty interference from MUE or power race among multiple HUEs) and adequate demodulation performance. + +Modifying the HNB scheduler in this way will increase HUE throughput but as a result will also increase the UL interference caused by the HUEs at the macro layer. As a consequence the UL throughput of macro UEs can become degraded. The application of an upper limit on the HUE transmit power, as discussed in Section 7.4.1, will ensure that this effect is constrained to an acceptable level. + +document. + +Table 7.3.2-1 summarises the control of HNB noise rise threshold. + +**Table 7.3.2-1: Control of HNB noise rise threshold based on different deployment scenarios** + +| Deployment Scenario | Interference source(s) | HNB noise rise threshold setting | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------------------------| +| HNB installed inside a building far from macrocell site | Macro UEs attached to macrocell and located close to HNB | High | +| HNB installed inside a building close to macrocell site | Macro UEs attached to macrocell and located close to HNB | Low | +| HNB installed inside a building far from other HNBs | HUE(s) served by other HNBs and located close to HNB | High | +| HNB installed inside a building close to other HNB(s) | HUE(s) served by other HNBs and located close to the HNB | Low | +| HNB installed inside a building | Own HUE(s) located very close to the HNB that cannot be powered down due to limited dynamic range | High | + +### 7.3.3 Control of HNB receiver gain + +This is an alternative mitigation technique to address UL interference from uncontrolled UEs towards the HNB and increase in noise rise from a HUE that cannot be powered down due to limited dynamic range. Again it is especially significant for CSG deployments where uncontrolled UEs may be located within the HNB premises while still being attached to an external macro network. In such cases, + +- the macro UE's transmit power could be high while the pathloss to the HNB could be small, or +- the uncontrolled UE (i.e. a HUE) associated with a neighbour HNB could be transmitting at high power, or +- own HUE located very close to the HNB could be transmitting at high power as it cannot be powered down due to limited dynamic range + +This mitigation approach is based on *dynamic control of the receiver gain* or UL attenuation, also known as *adaptive noise figure adjustment*. This has the effect of moving the dynamic range of the HNB receiver such that the interfering UE is no longer blocking the UL. As a consequence the HNB receiver is temporarily desensitised during periods of reduced gain or attenuation. + +Adjustment of the receiver gain or UL attenuation can be made by the HNB, driven by measurements of receive total wideband power (i.e. RTWP) or other similar measurement entities on the UL. Blocking levels of UL noise rise due to out of cell interference can be detected and the receiver gain reduced accordingly. This adjustment would only need to be made temporarily while the UL interference was strong and as soon as the noise rise was seen to fall the receiver gain could be returned to its normal operating value. + +This adjustment would also need to react fast when the UL interference is strong or noise rise from a HUE is high and slowly decay with time, e.g., to accommodate variations in interference due to bursty traffic. The effect of such desensitisation would be to temporarily cause HUEs to increase their own UL transmit power and thereby increase interference to the macro layer. Therefore, it is crucial to determine the correct amount of attenuation that will improve the HUE's performance without degrading the MUEs. The application of an upper limit on the HUE transmit power, as discussed in Section 7.4.1, will ensure that a runaway positive feedback condition is avoided. + +#### 7.3.3.1 Performance analysis + +The performance of using dynamic control of the receiver gain or UL attenuation can be obtained using the following analysis setup. The general set up for the uplink analysis is given in Figure 7.3.3.1-1. The cell edge case is considered first, where a HNB is deployed at the edge of a macro cell and it has an active HUE associated with it. There is also a MUE which is located close to the HNB. The HNB, HUE and the MUE are assumed to have 140dB PL with the MNB ( $X=140\text{dB}$ ). The HUE and the MUE are assumed to be separated from the HNB by Y and Z dB PL, respectively. + +document. + +![Diagram of UL Interference Analysis Setup showing a Macro NodeB (MNB) at the top, a Home User Equipment (HUE) and Home NodeB (HNB) at the bottom left, and a Mobile User Equipment (MUE) at the bottom right. The HUE, HNB, and MUE are enclosed in a rectangular box representing the cell coverage area. Dashed lines with arrows indicate signal paths: from MNB to HUE (labeled X), from MNB to HNB (labeled X), from MNB to MUE (labeled X), from HUE to HNB (labeled Y), and from MUE to HNB (labeled Z).](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Diagram of UL Interference Analysis Setup showing a Macro NodeB (MNB) at the top, a Home User Equipment (HUE) and Home NodeB (HNB) at the bottom left, and a Mobile User Equipment (MUE) at the bottom right. The HUE, HNB, and MUE are enclosed in a rectangular box representing the cell coverage area. Dashed lines with arrows indicate signal paths: from MNB to HUE (labeled X), from MNB to HNB (labeled X), from MNB to MUE (labeled X), from HUE to HNB (labeled Y), and from MUE to HNB (labeled Z). + +Figure 7.3.3.1-1: UL Interference Analysis Setup + +The PL values of interest (i.e., Y and Z) depend on the HNB coverage determined by the tx power chosen. Three deployment scenarios are considered: a) HNB with 70dB coverage radius, b) HNB with 80dB coverage radius, and c) HNB with 90dB coverage radius. Both cell edge and cell site scenarios are analyzed. The performance analysis for the cell edge and cell site scenarios demonstrate the need for an adaptive algorithm that adjusts the UL attenuation / padding based on the out-of-cell interference experienced at the HNB. + +##### 7.3.3.1.1 Cell edge scenarios + +For cell edge scenario, the following PL pairs are investigated in more detail (Table 7.3.3.1-1). When the HNB coverage of 70dB is targeted, the HNB tx power cannot go as low as required (min HNB total tx power limitation of -10dBm is assumed). Therefore, a MUE located at the edge of the targeted coverage region will be in outage. Hence, the MUE is placed 80dB away from the HNB in this case. + +Table 7.3.3.1-1: Cell edge parameters + +| Parameters | Values | | | +|--------------------------------|----------|-------|-------| +| HUE UL Ec/No at HNB | -2.4 dB | | | +| HNB default Noise Figure | 19 dB | | | +| Maximum HUE/MUE Tx Power | 21 dBm | | | +| MNB Noise Figure | 5 dB | | | +| Additional interference at MNB | -101 dBm | | | +| Y: PL (HUE to HNB) | 70 dB | 80 dB | 90 dB | +| Z: PL (MUE to HNB) | 80 dB | 80 dB | 90 dB | + +Being at the cell edge, the MUE is assumed to be transmitting at 21dBm (e.g., the maximum UE total tx power). The MUE transmitting at high power close to the HNB can significantly increases the noise rise at the HNB. This noise rise contribution is denoted by Ec/No', where Ec is received signal strength of the MUE at the HNB and No' corresponds to the received signal strength in the absence of HUE or MUE. The goal of the UL interference management is to keep the MUE contribution on the HNB noise rise below the noise rise threshold by adding attenuation or increasing the noise figure, such that the HUEs can get scheduled. + +document. + +In Figure 7.3.3.1-2, the solid curves correspond to the noise rise contribution of the MUEs at the HNB as a function of the additional padding / UL attenuation applied at the HNB. The HUE transmit power is determined based on a -2.4dB Ec/No requirement. The dashed curves correspond to the noise rise contribution of HUE at the MNB. Although the transmit power of the HUE is increased with the additional attenuation applied at the HNB, the HUE is still located very close to the HNB while being on the edge of the MNB coverage. Therefore, the HUE's contribution to the MNB noise rise is minimal. + +![Figure 7.3.3.1-2: UL cell edge scenario: noise rise contribution of non-associated UEs. The graph shows UE Noise Rise Contribution at Non-serving NB [dB] on the Y-axis (from -30 to 30) versus Additional Noise Figure/UL Attenuation [dB] on the X-axis (from 0 to 40). Six curves are plotted: three solid lines for MUE Ec/No' at HNB (Y=70dB, 80dB, 90dB) and three dashed lines for HUE Ec/No' at MNB (Y=70dB, 80dB, 90dB). The solid lines decrease linearly from 30 dB at 0 dB attenuation to -10 dB at 40 dB attenuation. The dashed lines remain relatively flat, starting around -20 dB and slightly increasing to -18 dB at 40 dB attenuation. A 'Cell Edge' label is present above the plot area.](efbdff107f5a5aade487cf4ea0eae150_img.jpg) + +| Additional Noise Figure/UL Attenuation [dB] | MUE Ec/No' at HNB - Y=70dB, Z=80dB [dB] | MUE Ec/No' at HNB - Y=80dB, Z=80dB [dB] | MUE Ec/No' at HNB - Y=90dB, Z=90dB [dB] | HUE Ec/No' at MNB - Y=70dB, Z=80dB [dB] | HUE Ec/No' at MNB - Y=80dB, Z=80dB [dB] | HUE Ec/No' at MNB - Y=90dB, Z=90dB [dB] | +|---------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| 0 | 30 | 20 | 10 | -28 | -20 | -20 | +| 5 | 25 | 15 | 5 | -28 | -20 | -20 | +| 10 | 20 | 10 | 0 | -28 | -20 | -20 | +| 15 | 15 | 5 | -5 | -28 | -20 | -20 | +| 20 | 10 | 0 | -10 | -28 | -20 | -20 | +| 25 | 5 | -5 | -15 | -27 | -19 | -19 | +| 30 | 0 | -10 | -20 | -26 | -18 | -18 | +| 35 | -5 | -15 | -25 | -24 | -17 | -17 | +| 40 | -10 | -20 | -30 | -22 | -16 | -16 | + +Figure 7.3.3.1-2: UL cell edge scenario: noise rise contribution of non-associated UEs. The graph shows UE Noise Rise Contribution at Non-serving NB [dB] on the Y-axis (from -30 to 30) versus Additional Noise Figure/UL Attenuation [dB] on the X-axis (from 0 to 40). Six curves are plotted: three solid lines for MUE Ec/No' at HNB (Y=70dB, 80dB, 90dB) and three dashed lines for HUE Ec/No' at MNB (Y=70dB, 80dB, 90dB). The solid lines decrease linearly from 30 dB at 0 dB attenuation to -10 dB at 40 dB attenuation. The dashed lines remain relatively flat, starting around -20 dB and slightly increasing to -18 dB at 40 dB attenuation. A 'Cell Edge' label is present above the plot area. + +Figure 7.3.3.1-2: UL cell edge scenario: noise rise contribution of non-associated UEs + +The HUE and MUE Ec/No values at their corresponding serving NBs are provided in Figure 7.3.3.1-3. Although the effect of HUE on the macro network is minimal, using more than the required amount of attenuation is not desired. For the cases where HUE to HNB PL is 80dB and 90dB, it is observed that beyond 10dB and 20dB additional noise figure respectively, the HUE starts running out of headroom and is unable to maintain the Ec/No requirement. + +document. + +![Line graph showing UE Ec/No at Serving NB [dB] vs Additional Noise Figure/UL Attenuation [dB]. The graph includes six data series for MUE and HUE with different path loss (Y) and interference (Z) values. A 'Cell Edge' marker is at 20 dB. Most series drop off after 20 dB, except for the HUE Y=90dB Z=90dB series which stays flat at -20 dB.](673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg) + +| Additional Noise Figure/UL Attenuation [dB] | MUE Ec/No - Y=70dB, Z=80dB | MUE Ec/No - Y=80dB, Z=80dB | MUE Ec/No - Y=90dB, Z=90dB | HUE Ec/No - Y=70dB, Z=80dB | HUE Ec/No - Y=80dB, Z=80dB | HUE Ec/No - Y=90dB, Z=90dB | +|---------------------------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------| +| 0 | -2 | -2 | -2 | -2 | -2 | -20 | +| 5 | -2 | -2 | -2 | -2 | -2 | -20 | +| 10 | -2 | -2 | -2 | -2 | -2 | -20 | +| 15 | -2 | -2 | -2 | -2 | -2 | -20 | +| 20 | -2 | -2 | -2 | -2 | -2 | -20 | +| 25 | -2 | -2 | -6 | -2 | -2 | -20 | +| 30 | -2 | -3 | -10 | -2 | -2 | -20 | +| 35 | -2 | -6 | -14 | -2 | -2 | -20 | +| 40 | -2 | -10 | -20 | -2 | -2 | -20 | + +Line graph showing UE Ec/No at Serving NB [dB] vs Additional Noise Figure/UL Attenuation [dB]. The graph includes six data series for MUE and HUE with different path loss (Y) and interference (Z) values. A 'Cell Edge' marker is at 20 dB. Most series drop off after 20 dB, except for the HUE Y=90dB Z=90dB series which stays flat at -20 dB. + +Figure 7.3.3.1-3: UL cell edge scenario: Ec/No at serving NB + +A reference algorithm trying to maintain the out-of-cell contribution to the HNB noise rise at 3dB would choose the following UL attenuation values (Table 7.3.3.1-2): + +Table 7.3.3.1-2: Cell edge analysis: suggested UL attenuation at HNB + +| Y: PL (HUE to HNB) | 70 dB | 80 dB | 90 dB | +|------------------------------------------|-------|-------|-------| +| Z: PL (MUE to HNB) | 80 dB | 80 dB | 90 dB | +| UL Attenuation (Additional Noise Figure) | 27dB | 27dB | 17dB | + +##### 7.3.3.1.2 Cell site scenarios + +For cell site scenarios, the HNB is deployed close to the macro cell site. In this case the HNB, HUE and the MUE are assumed to have 100dB PL to the MNB (X=100dB). The PL values of interest (i.e., Y and Z) again depend on the HNB coverage determined by the tx power chosen. For the cell site case, the following PL pairs are investigated in more detail (Table 7.3.3.1-3). When a HNB coverage of 90 or 100dB is targeted, the HNB tx power becomes insufficient due to the max HNB total tx power limitation of 20dBm. Therefore, a HUE located at the edge of targeted coverage region is unable to maintain -20dB CPICH Ec/No with the HNB. + +document. + +**Table 7.3.3.1-3: Cell site parameters** + +| Parameters | Values | | | +|--------------------------------|----------|-------|-------| +| HUE UL Ec/No at HNB | -2.4 dB | | | +| HNB default Noise Figure | 19 dB | | | +| HUE maximum Tx Power | 21 dBm | | | +| MUE Tx Power | -15 dBm | | | +| HNB maximum Tx Power | 20 dBm | | | +| MNB Noise Figure | 5 dB | | | +| Additional interference at MNB | -101 dBm | | | +| Y: PL (HUE to HNB) | 70 dB | 80 dB | 80 dB | +| Z: PL (MUE to HNB) | 70 dB | 80 dB | 90 dB | + +Being at the cell site, the MUE is assumed to be transmitting at -15dBm. In Figure 7.3.3.1-4, the noise rise contributions of the MUE and HUE at the HNB and MNB, respectively are presented. Here again, the HUE transmit power is determined based on a -2.4 dB Ec/No requirement. + +As seen in Figure 7.3.3.1-4, unlike the cell edge case, there is no need for large additional UL attenuation values to control the noise rise at the HNB. In fact, if unnecessary attenuation is applied, then the HUE tx power increases considerably, creating significant noise rise at the MNB. + +In Figure 7.3.3.1-5, the UE Ec/No values at their serving NB are presented. It is clearly seen that the MNB Ec/No goes down if more than necessary UL attenuation is used. For certain cases, the HUE could also run out of headroom and not be able to maintain the required Ec/No. + +![Figure 7.3.3.1-4: UL cell site scenario: noise rise contribution of non-associated UEs. The graph plots 'UE Noise Rise Contribution at Non-serving NB [dB]' on the y-axis (from -30 to 30) against 'Additional Noise Figure/UL Attenuation [dB]' on the x-axis (from 0 to 40). Six data series are shown: 1) MUE Ec/No' at HNB - Y=70dB, Z=70dB (blue solid line with circles) decreases from ~5 dB to -30 dB. 2) MUE Ec/No' at HNB - Y=80dB, Z=80dB (red solid line with circles) decreases from ~-5 dB to -30 dB. 3) MUE Ec/No' at HNB - Y=80dB, Z=90dB (green solid line with squares) decreases from ~-10 dB to -30 dB. 4) HUE Ec/No' at MNB - Y=70dB, Z=70dB (blue dashed line with circles) increases from ~-12 dB to ~22 dB. 5) HUE Ec/No' at MNB - Y=80dB, Z=80dB (red dashed line with circles) increases from ~-10 dB to ~22 dB. 6) HUE Ec/No' at MNB - Y=80dB, Z=90dB (green dashed line with squares) increases from ~-8 dB to ~22 dB.](9288d35265c4f3578be38d28ac588f18_img.jpg) + +Figure 7.3.3.1-4: UL cell site scenario: noise rise contribution of non-associated UEs. The graph plots 'UE Noise Rise Contribution at Non-serving NB [dB]' on the y-axis (from -30 to 30) against 'Additional Noise Figure/UL Attenuation [dB]' on the x-axis (from 0 to 40). Six data series are shown: 1) MUE Ec/No' at HNB - Y=70dB, Z=70dB (blue solid line with circles) decreases from ~5 dB to -30 dB. 2) MUE Ec/No' at HNB - Y=80dB, Z=80dB (red solid line with circles) decreases from ~-5 dB to -30 dB. 3) MUE Ec/No' at HNB - Y=80dB, Z=90dB (green solid line with squares) decreases from ~-10 dB to -30 dB. 4) HUE Ec/No' at MNB - Y=70dB, Z=70dB (blue dashed line with circles) increases from ~-12 dB to ~22 dB. 5) HUE Ec/No' at MNB - Y=80dB, Z=80dB (red dashed line with circles) increases from ~-10 dB to ~22 dB. 6) HUE Ec/No' at MNB - Y=80dB, Z=90dB (green dashed line with squares) increases from ~-8 dB to ~22 dB. + +**Figure 7.3.3.1-4: UL cell site scenario: noise rise contribution of non-associated UEs** + +document. + +![Line graph titled 'Cell Site' showing UE Ec/No at Serving NB [dB] vs Additional Noise Figure/UL Attenuation [dB]. The graph compares MUE and HUE performance for various Y and Z parameters. HUE performance remains relatively flat around -2 dB, while MUE performance decreases as noise figure increases.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +| Additional Noise Figure/UL Attenuation [dB] | MUE Ec/No - Y=70dB, Z=70dB | MUE Ec/No - Y=80dB, Z=80dB | MUE Ec/No - Y=80dB, Z=90dB | HUE Ec/No - Y=70dB, Z=70dB | HUE Ec/No - Y=80dB, Z=80dB | HUE Ec/No - Y=80dB, Z=90dB | +|---------------------------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------| +| 0 | -16 | -16 | -16 | -2 | -2 | -2 | +| 5 | -16 | -16 | -17 | -2 | -2 | -2 | +| 10 | -16 | -16 | -18 | -2 | -2 | -2 | +| 15 | -16 | -16 | -20 | -2 | -2 | -2 | +| 20 | -18 | -18 | -24 | -2 | -2 | -2 | +| 25 | -20 | -20 | -29 | -2 | -2 | -2 | +| 30 | -24 | -24 | -34 | -2 | -2 | -2 | +| 35 | -29 | -29 | -36 | -2 | -2 | -5 | +| 40 | -34 | -34 | -36 | -2 | -2 | -10 | + +Line graph titled 'Cell Site' showing UE Ec/No at Serving NB [dB] vs Additional Noise Figure/UL Attenuation [dB]. The graph compares MUE and HUE performance for various Y and Z parameters. HUE performance remains relatively flat around -2 dB, while MUE performance decreases as noise figure increases. + +Figure 7.3.3.1-5: UL cell site scenario: Ec/No at serving NB + +A reference algorithm trying to maintain the out-of-cell contribution to the HNB noise rise at 3dB would choose the following UL attenuation values (Table 7.3.3.1-4): + +Table 7.3.3.1-4: Cell site analysis: suggested UL attenuation at HNB + +| | | | | +|------------------------------------------|-------|-------|-------| +| Y: PL (HUE to HNB) | 70 dB | 80 dB | 80 dB | +| Z: PL (HUE to HNB) | 70 dB | 80 dB | 90 dB | +| UL Attenuation (Additional Noise Figure) | 1dB | 0dB | 0dB | + +## 7.4 HNB self-configuration + +HNB should perform self-configuration at power up and on a regular basis during normal operation. Depending on the implementation, the HNB should be able to relay its measurements to, and receive its RF configuration from, an external configuration element such as network planning server, O&M server and HNB-GW. Such configuration elements can also optimize the RF parameters of a set of HNBs in a joint manner. However, this section does not describe the operation of these configuration elements and is limited to the self-configuration of a HNB based on the self-obtained information.. + +The HNB self-configuration can also be activated on a regular basis provided that no UE is RRC connected to the HNB or all UEs attached to the HNB are in idle mode. The self-configuration capability of HNB should not impact the existing UE behaviour. If any UE served by the HNB has on-going voice/data transmission, the HNB should wait until the corresponding UE to complete its voice/data transmission, release the RRC connection and then activate the self-configuration mode. + +The self-configuration activation period can be set to long, medium or short (exact value FFS). For example, activation period can be set to 24 hours in order to activate HNB self-configuration mode once a day. Performing self-configuration on a regular basis (self-configuration interval FFS) or event triggered self-configuration will help to reduce excessive interference generated by the HNB to the surrounding macrocells and HNBs. + +document. + +Self-configuration of HNB consists of setting a number of RF parameters to a value which is optimized for achieving the proposed objectives. The most important parameters are: + +- Choosing the right carrier frequency, +- Selecting the optimum DL scrambling code +- Selecting suitable LAC and/or RAC. +- Setting the optimum maximum allowable Tx power level in downlink and uplink, +- Building a set of cell lists, and, +- Processing the UE measurement reports (if available) + +The HNB self-configuration requirements are listed in Table 7.4-1. Detailed fulfilment of HNB self-configuration requirements is vendor specific (i.e. dependent on self-configuration modes). Generally, the HNB self-configuration can be broadly divided into passive and active mode. The passive mode HNB self-configuration satisfies only the basic requirements, while the active mode HNB self-configuration is capable of handling more complex tasks such as detecting of abnormal operating conditions, decoding UE measurement reports, neighbour cell list construction, etc. + +**Table 7.4-1: HNB self-configuration modes and requirements** + +| Requirement
No | Requirements | | +|-------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| | Passive | Active | +| 1 | Conduct measurements in section 7.1.1, 7.1.2, 7.1.3, 7.1.4 | Conduct measurements in section 7.1.1, 7.1.2, 7.1.3 and 7.1.4 | +| 2 | Select DL scrambling code or UARFCN | Select DL scrambling code or UARFCN | +| 3 | Select DL Tx Power level of the HNB and max UL Tx power level of the HUE | Select DL Tx Power level of the HNB and max UL Tx power level of the HUE | +| 4 | Decode broadcast channel (e.g. BCH) | Decode broadcast channel (e.g. BCH) | +| 5 | N/A | Use UE measurement reports as input to self-configuration algorithm | +| 6 | N/A | Perform additional RRM (e.g. handover handling, coverage control) based on a set of measurement inputs | +| 7 | N/A | Detection of abnormal operating conditions | +| 8 | Construct a set of neighbour cell lists | Construct a set of neighbour cell lists | +| 9 | Synchronise local clock/RF oscillator with e.g., macrocells, IP network | Synchronise local data clock/RF oscillator with e.g., macrocells, IP network | +| 10 | Select suitable LAC, RAC | Select suitable LAC, RAC | + +### 7.4.1 Scrambling code selection + +In general, HNB should have abilities to detect interference and scrambling code. Using the information detected, HNB selects a spare scrambling code which is not used by neighboring HNBs. For example, HNB can monitor the radio signal in its downlink bands before setting up its own cell. Then, the HNB selects a scrambling code as its operating scrambling code which is not used by the neighboring HNBs or macro cells. + +Therefore, each HNB would require to be configured for a particular scrambling code on the downlink. If neighbouring HNBs use the same scrambling code, significant problems can arise since HUEs may not be able to associate with the correct HNB. In macrocell networks, scrambling codes for base stations are carefully managed so that base stations in a certain region use different scrambling codes. This, however, is not very practical for HNBs and a more autonomous method to select the scrambling codes would be useful for HNBs. The goal of such a mechanism is to minimize the number of scrambling code collisions for a given number of total scrambling codes. + +For instance, depending on the HNB deployment strategy, a certain set of scrambling codes can be reserved for HNBs, denoted as $S_{HNB} = \{S_1, S_2, \dots, S_{N_{sc}}\}$ . If the HNBs operate on a dedicated carrier, the HNB can scan all the available + +document. + +scrambling codes (i.e., $N_{sc}=512$ ) and the total number of scrambling codes that can be reserved for HNBs is configurable. If HNBs operate on a shared carrier (co-channel) with macrocell, a certain subset of available scrambling codes should be reserved for HNBs and these codes should not be used by any macrocell base station. + +During HNB self-configuration, HNB scans for all scrambling codes and construct a set of scrambling codes which have pilot energy above detection threshold: $S_{DETECTED}=\{S_i, S_j, \dots, S_k\}$ . Note that some of the scrambling codes in the set $S_{DETECTED}$ can be part of the set $S_{HNB}$ (i.e., PSCs used by neighbouring HNBs) and rest of the set can be part of “macrocell only” scrambling codes. Then, HNB can select the “best” scrambling code based on certain criteria, for example: + +- If all HNB-reserved scrambling codes are being used by neighbour HNBs + - HNB picks a scrambling code in $S_{HNB}$ with smallest amount of detected energy (i.e., smallest CPICH Ec/No and CPICH RSCP) +- Else + - HNB picks a scrambling code randomly from set of scrambling codes that are member of $S_{HNB}$ but not member of $S_{DETECTED}$ + +Upon failure to pick the “best” scrambling code, an alarm or some form of error indication shall be sent to the network controller (e.g. Core Network, HNB-GW, O&M server). The details of alarm triggering threshold is FFS. + +### 7.4.2 Carrier or UARFCN selection + +In general, HNB should have abilities to select a carrier frequency using information such as interference level. For example, HNB can monitor the radio signal in its downlink bands before setting up its own cell. Once the HNB gets the interference level (RSSI) on each of its available frequencies, it selects a carrier frequency as its operating frequency which has the smallest interference. + +Therefore, each HNB needs to be configured for a certain carrier frequency (channel or UARFCN) to operate on. Such a mechanism depends on the particular deployment configuration listed in section 5.1. If there is only one available carrier for all HNBs, there could be certain amount of inter-HNB interference. One solution for addressing this issue would be to use multiple carriers for HNBs. For example, HNBs in neighboring apartments can be assigned to different frequency carriers to mitigate the potential interference problems. + +If macrocells operate on the same carrier as HNBs, then HNB-macrocell interference can result in a certain amount of outage and performance degradation both for HUEs and MUEs. One solution for mitigating the HNB-macro interference would be to make sure the carriers used by HNBs are not used by macrocells. Although this method reduces HNB-macro interference noticeably, it is not efficient in terms of spectrum utilization especially if HNB deployment density is not high. Also, the total number of available carriers for an operator needs to be considered in this decision. For most operators with limited carriers (e.g., two or three carriers), sharing the carriers between HNBs and macrocells could be preferable. In this case, if a MUE goes into coverage hole of a HNB, it could perform inter-frequency handoff to another carrier frequency1. In order to minimize the number of inter-frequency hand-off events for MUEs, HNBs may prefer a certain frequency and use other frequencies only in the homes where there is noticeable interference from neighboring HNBs. + +In general if an operator has $N$ carrier frequencies: $F=\{f_1, f_2, \dots, f_N\}$ , then HNBs are allowed to use a certain subset ( $F_{HNB}$ ) of these frequencies while macrocells can use a certain subset ( $F_{macro}$ ). Without loss of generality, in the following, we will assume $F_{HNB}=\{f_1, f_2, \dots, f_K\}$ and $F_{macro}=\{f_M, f_{M+1}, \dots, f_N\}$ where $1 \leq K \leq N$ and $1 \leq M \leq N$ . + +As a possible method for carrier selection, during self configuration, the HNB will measure the RSS values for all $K$ carrier frequencies and find the carriers with least interference, denoted as $No_{min}$ . The accuracy of RSS measurement is [FFS]. In order to find the carrier suitable for operation, the HNB can scan all the available UARFCN or carrier frequencies and, starting from $f_1$ , choose $f_i$ if $No_{f_i} \leq No_{min} + HNB\_Frequency\_RSS\_margin$ . The usage of the parameter $HNB\_Frequency\_RSS\_margin$ is to adjust the tradeoff between selecting least interference carrier and concentrating the HNBs on certain carriers such that coverage hole created by macrocell is minimized. + +1 Note that macrocell legacy UEs are designed to choose the best macrocell frequency to operate given that system parameters are chosen appropriately. + +document. + +### 7.4.3 Neighbour cell list configuration and handover + +During the HNB self-configuration mode, HNB should be able to use the macrocells information detected on a set of UARFCNs to build the following cell lists: + +- Intra-frequency cell list +- Inter-frequency cell list +- Inter-RAT list + +In addition to the standard cell lists above, the HNB may also construct the following cell lists: + +- Preferred cell camping list. This list can be a subset of the normal cell camping list and can be operator configurable (via O&M server). The purpose of the preferred cell camping list is to prioritise certain cells for HUE to camp on for load balancing, traffic and QoS control. +- Preferred RAT handover list. This is can be a subset of the normal IRAT list and can be operator configurable (via O&M server). The purpose of the preferred RAT handover list is to prioritise the handover preference of certain RAT cells (e.g. prefer handover to EDGE over GSM/GPRS). + +Upon constructed the cell lists, the HNB can broadcast some of the cell list information (in e.g. SIB11) to the UEs served by the HNB. + +When an HUE leaves the coverage area of HNB it can be handed over to macro network. In order to support the handover from HNB to macro network, HNBs should detect macro neighboring cells and add them to their neighbour cell list automatically. + +In addition, when a number of HNBs may be required to be deployed as a small network, the HNB neighbour cell list can be configured automatically by the HNB or a HNB controller (e.g. HNB-GW) in order to facilitate the handover between HNBs. + +To enable MNBs and network aware of the cell list information, the cell lists constructed by the HNB during self-configuration mode and/or subsequent cell list updates can be fed back to the network controller (i.e. Core Network, HNB-GW) via either HNBAP or TR-069 [55] signalling. + +### 7.4.4 HNB DL power setting + +HNBs with large transmit power may cause significant interference to macro network and neighboring HNBs, leading for example to dropped calls for the connected UEs on same and adjacent channels. Therefore the transmit power of HNBs should be controlled. Coverage range and interference level in different HNB deployment environments are different and varied. For this reason the HNBs should have the ability to adjust its power autonomously and/or based on the report from UEs about interference and signal quality detected by the UEs. + +HNB DL power setting is a function of HNB cell coverage, macrocell interference and other-HNB interference. Given a suitable DL operating power range, the HNB should be able to set its output Tx power by taking into account a number of criterions such as: + +- The CPICH Ec/No at the expected edge of coverage of the HNB is of sufficient quality to provide adequate coverage/performance for the HNB +- The macro layer CPICH Ec/No at the expected edge of coverage of the HNB is not severely degraded +- The adjacent-channel macro layer CPICH Ec/No at certain distance/pathloss from the HNB is not severely degraded + +Out of all these three objectives, the last one is of special importance when the adjacent channel belongs to another operator, as it refers to the impact of HNB activity on the surrounding networks on adjacent channels. + +document. + +### 7.4.5 HUE UL power setting + +During HNB self-configuration, the HNB should set a maximum allowed transmit power for its UEs based on the pathloss to the neighbour NodeBs and the expected received power at neighbour NodeBs such that if its UEs were transmitting at this maximum power level they will not cause a significant UL noise rise to the neighbour NodeBs, and thus compromise the coverage or capacity significantly. The pathloss to the neighbour NodeBs can be estimated via measurements outlined in subclause 7.1. The received power at the neighbour NodeBs can be obtained either from measurements outlined in subclause 7.1 or from network (e.g. Core Network, HNB-GW). + +Note that the process to set HUE maximum allowed transmit power should not alter the existing UE behaviour. Also, the HUE transmit power will mainly affect the macro NodeBs operating on the same frequency channels as the Home NodeB. + +As the HUE transmit power does not significantly affect the surrounding macro NodeBs operating on adjacent channels (i.e. other operator's network), the HUE power adjustment remains an operator choice. + +### 7.4.6 LAC/RAC selection + +In a CSG deployment, in order to perform user authentication for the UEs, one technique is to utilize Location Area Update/Routing Area Update procedure. This technique assumes that each HNB is configured with a LAC that is different from the surrounding macro cells and nearby HNBs, so that a UE always performs location area update when it tries to camp on the HNB. Therefore, during the HNB self-configuration mode, the HNB should be capable of selecting a suitable LAC (or RAC) from a list of available LACs/RACs. + +However, the drawback of user authentication via LAU/RAU procedure is that there may be potentially a large number of LAU/RAU update reject messages generated when a HUE is not allowed to camp on to a consecutive number of HNBs under certain mobility scenarios, particularly for CSG type deployment. + +The solution to avoid generating a large number of LAU/RAU update reject messages is [FFS]. + +### 7.4.7 Extreme/Abnormal operating conditions + +There are certain conditions whereby the HNB might not be able to provide optimal RF performance to its HUEs, such as not having an accurate picture of the surrounding RF environment or the RF self-configuration algorithms not being able to select parameters within supplied bounds. In the event of detecting an error condition the HNB may use a set of RF parameters defined by the operator which will provide restricted HNB coverage or could disable radio transmission [56] until the situation has been rectified. + +Table 7.4.7-1 provides a list of such conditions, their implications on HNB operation and suggested actions to take on detecting such conditions. + +**Table 7.4.7-1: Extreme/Abnormal operating conditions** + +| | Condition | Implication | Possible consequent Actions | +|---|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Lack of suitable DL scrambling Code | HNB could degrade performance of other HNBs | -Select alternative UARFCN if available.
-HNB could be relocated within building | +| 2 | Failure to detect BCH on downlink UARFCN | HNB power setting & DL primary scrambling code might not be optimal
Neighbour cell list will not be generated | -Alert operator
-HNB could be relocated within building
-Other possible actions [FFS] | +| 3 | No suitable LAC/RAC available | If a HNB reuses a LAC within the same geographical area it is possible that a UE can camp on to neighbour's HNB without being on its access control list. Under this scenario the UE will not be able to receive paging messages. | - Alert operator
- HNB could transmit with low power to eliminate the overlap in coverage areas between HNBs that have the same LAC. | + +document. + +| | | | | +|---|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 | Location Change e.g. as indicated by different macro cell IDs on UARFCN or PLMN | HNB is potentially in a location outside the one it was provisioned for. HNB can potentially transmit on a UARFCN that is not allocated to the operator. | - Alert operator
- HNB could disable radio transmission until new location has been verified 1
- Other possible actions [FFS] | +| 5 | Failure to detect a suitable frequency reference | The RF oscillator of the HNB could potentially be out-of-synch. | - Alert operator
- HNB could disable radio transmission 1 | + +Note 1: For regulatory reasons (e.g., intended by Japan and Germany), HNB should be able to stop radio transmission [56]. + +## 7.5 Control of HNB coverage + +In principle, the HNB transmit power could be used to ensure HNB coverage. This is because the HNB coverage range and interference level in different HNB deployment environment are different and variable. With HNB adjusting its Tx power either autonomously and/or based on interference and signal quality detected and reported by surrounding UEs, the HNB coverage can be controlled. + +The HNB coverage is determined by HNB output power, the data rate provided to the HUEs, and the external interference that HNB system received from macrocells and surrounding HNBs. There is no simple formula to define the HNB coverage as a function of all the parameters involved. However, the HNB coverage can be used as a trade-off in order to reduce the interference caused to the macrocells or other surrounding HNBs. Some interference control mechanisms in Section 7.2 and Section 7.3 can also be used to control the HNB coverage. + +The HNB can be uplink and downlink coverage limited depending on the link budgets. The coverage of the HNB can also be controlled via dynamic switching of service-level data rates. + +### 7.5.1 CSG + +[Editor notes: detail of HNB coverage control for CSG type deployment] + +### 7.5.2 Open access + +[Editor notes: detail of HNB coverage control for open access HNB deployment] + +# --- 8 Interference tests + +//Editors note: this section is to test the ability of HNB maximum allowable transmit power dependant of co-channel interference conditions. + +The following subsections describe example test procedure and parameters which can be used to evaluate HNB self-configuration and performance in both uplink and downlink scenarios. + +## 8.1 Downlink + +### 8.1.1 Co-channel tests + +In order to ensure reasonable behaviour of HNB on the DL, two scenarios are considered for HNB deployments: a) cell edge and b) cell site. The DL scenario under consideration is shown in Figure 8.1-1. Cell edge refers to the case where the HNB and UEs are at the macro cell edge and cell site refers to the case where the HNB and UEs are close to the macro cell edge. + +document. + +![Diagram of a DL interference scenario. A Macro NodeB (MNB) is at the top, with three dashed arrows labeled 'X' pointing to a User Equipment (UE) labeled 'MUE', a Home UE (HUE), and a Home NodeB (HNB). The HUE and HNB are inside a rectangular box representing the HNB coverage area. A dashed arrow labeled 'Y' points from the HNB to the HUE, and a dashed arrow labeled 'Z' points from the HNB to the MUE.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Diagram of a DL interference scenario. A Macro NodeB (MNB) is at the top, with three dashed arrows labeled 'X' pointing to a User Equipment (UE) labeled 'MUE', a Home UE (HUE), and a Home NodeB (HNB). The HUE and HNB are inside a rectangular box representing the HNB coverage area. A dashed arrow labeled 'Y' points from the HNB to the HUE, and a dashed arrow labeled 'Z' points from the HNB to the MUE. + +**Figure 8.1-1: DL interference scenario** + +Since a HNB can have different coverage radius (i.e., link budget) depending on the particular deployment scenario (e.g., suburban, urban, dense-urban), three categories of HNBs are considered: a) HNB with 70dB coverage radius, b) HNB with 80dB coverage radius, and c) HNB with 90dB coverage radius. A HNB with a particular coverage radius shall adjust its transmit power within the minimum and maximum power limits such that the MUE at the coverage radius can maintain a minimum quality of the CPICH Ec/No and the HUE can maintain an acceptable quality of CPICH Ec/No at the coverage radius. HNB DL tests are given below for the three HNB categories. The purpose of these tests is to ensure the HNB Tx power is adjusted properly to provide good HNB coverage and limit the coverage hole on macro. + +#### **Test Set-up:** + +The test set-up is as follows. The HNB under test is on frequency F1. A noise generator on F1 generates Ioc as specified in Table 8.1.1-1. A NB on frequency F1 is set up such that the RSSI (including Ioc) and the RSCP at the HNB are as specified in Table 8.1.1-1. + +**Table 8.1.1-1: Parameters for HNB DL co-channel tests** + +| Test Parameters | Cell Edge | Cell Site | +|-----------------|-----------|-----------| +| PL to MNB | 140 dB | 100 dB | +| RSSI at HNB | -95 dBm | -60 dBm | +| MNB RSCP | -107 dBm | -67 dBm | +| Ioc at HNB | -96dBm | -75dBm | + +In the following tests, the requirements are in terms of lower and upper limits for HNB Tx power. The lower limits are specified such that a HUE at the HNB coverage radius is able to maintain -18dB CPICH Ec/No. For the upper limits, a margin of a few dBs (~3dB) is included to allow for variations in the algorithm used for HNB Tx powers. CPICH Ec/Ior of -10dB for HNB and MNB are assumed. The tests assume +20dBm as the maximum power for the HNB. + +#### **8.1.1.1 DL test for HNB with 70dB coverage radius** + +For the test scenario described in Table 8.1.1-1, the total output power of the HNB with a designed coverage radius of 70dB shall be as specified in Table 8.1.1-2. + +document. + +**Table 8.1.1-2: HNB total output power** + +| Reference Condition | MNB RSCP at HNB | RSSI at HNB | loc at HNB | HNB Transmit Power Range | +|----------------------------|------------------------|--------------------|-------------------|-----------------------------------------------------------------------| +| A | - 107 dBm | - 95 dBm | - 96 dBm | $-34 \text{ dBm} \leq \text{HNB Total Tx Power} \leq -10 \text{ dBm}$ | +| B | - 67 dBm | - 60 dBm | - 75 dBm | $2 \text{ dBm} \leq \text{HNB Total Tx Power} \leq 10 \text{ dBm}$ | + +#### 8.1.1.2 DL test for HNB with 80dB coverage radius + +For the test scenario described in Table 8.1.1-1, the total output power of the HNB with a designed coverage radius of 80dB shall be as specified in Table 8.1.1-3. + +**Table 8.1-3: HNB total output power** + +| Reference Condition | MNB RSCP at HNB | RSSI at HNB | loc at HNB | HNB Transmit Power Range | +|----------------------------|------------------------|--------------------|-------------------|-----------------------------------------------------------------------| +| A | - 107 dBm | - 95 dBm | - 96 dBm | $-24 \text{ dBm} \leq \text{HNB Total Tx Power} \leq -10 \text{ dBm}$ | +| B | - 67 dBm | - 60 dBm | - 75 dBm | $12 \text{ dBm} \leq \text{HNB Total Tx Power} \leq 20 \text{ dBm}$ | + +#### 8.1.1.3 DL test for HNB with 90dB coverage radius + +For the test scenario described in Table 8.1.1-1, the total output power of the HNB with a designed coverage radius of 90dB shall be as specified in Table 8.1.1-4. + +**Table 8.1-4: HNB total output power** + +| Reference Condition | MNB RSCP at HNB | RSSI at HNB | loc at HNB | HNB Transmit Power Range | +|----------------------------|------------------------|--------------------|-------------------|----------------------------------------------------------------------| +| A | - 107 dBm | - 95 dBm | - 96 dBm | $-14 \text{ dBm} \leq \text{HNB Total Tx Power} \leq -5 \text{ dBm}$ | + +### 8.1.2 Adjacent channel tests + +The purpose of the test is to ensure that a HNB does not cause unacceptable interference to the adjacent channel operator. The HNB can use measurements such as RSSI and RSCP to adjust its transmit power such that it does not cause interference for the adjacent channel operator. The test set-up and requirements are specified in [25.104/25.141]. + +## 8.2 Uplink + +### 8.2.1 Basic tests + +Uplink interference between HNBs and the macro layer comprises three components, identified in the figure below as (a) (b) and (c): + +document. + +![Diagram of UL interference paths showing a macro base station (MNB) at the top, a Home User Equipment (HUE) and a Mobile User Equipment (MUE) in the middle, and a Home Base Station (HNB) at the bottom. Path (a) shows interference from HUE to MNB. Path (b) shows interference from MUE to HNB. Path (c) shows interference from a neighbour HUE to HNB. Dashed arrows indicate 'wanted' UL signals from HUE and MUE towards the MNB.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Diagram of UL interference paths showing a macro base station (MNB) at the top, a Home User Equipment (HUE) and a Mobile User Equipment (MUE) in the middle, and a Home Base Station (HNB) at the bottom. Path (a) shows interference from HUE to MNB. Path (b) shows interference from MUE to HNB. Path (c) shows interference from a neighbour HUE to HNB. Dashed arrows indicate 'wanted' UL signals from HUE and MUE towards the MNB. + +- (a) UL interference from HUE towards the macro layer +- (b) UL interference from MUE towards the HNB +- (c) UL interference from a neighbour HUE towards the HNB + +**Figure 8.2-1: UL interference paths** + +The interference mitigation approaches presented in Section 7.4 above have addressed all of these interference components, but the key requirement being tested here is that the UL interference from the HUE towards the macro layer (component (a) in the figure above) is controlled to be within an acceptable limit. + +The additional Dynamic Range and ACS tests for the Home BS class in 25.104, as specified in [3], have ensured that the HNB receiver can accommodate increased levels of interference (b) and (c) from nearby uncontrolled UEs. Guidance on how to make this accommodation has been provided in Sections 7.4.2 and 7.4.3 above. It has further been noted that as a result of this mitigation the transmit power of the HUE will increase, potentially causing additional noise rise at the macro layer – so interference paths (b), (c) and (a) are inextricably linked. The way in which this positive feedback cycle is broken is through the application of a limit on the HUE allowable transmit power as discussed in Section 7.4.1 above. + +Therefore, given that mitigation techniques to accommodate UL interference (b) and (c) towards the HNB have already been tested by the new Dynamic Range and ACS requirements in 25.104, it is sufficient from a “closed loop” system perspective to ensure that the maximum UL interference (a) towards the macro layer is controlled. This can be tested as follows. + +#### 8.2.1.1 Test setup + +![Diagram of the UL interference test setup. It shows an MNB emulator at the top receiving signals from a Home User Equipment (HUE) and a Home Base Station (HNB). The HUE is connected to an RL Setup signal. The HNB is connected to a P-CPICH & signal. A dashed double-headed arrow indicates the distance between the HUE and the HNB.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +Diagram of the UL interference test setup. It shows an MNB emulator at the top receiving signals from a Home User Equipment (HUE) and a Home Base Station (HNB). The HUE is connected to an RL Setup signal. The HNB is connected to a P-CPICH & signal. A dashed double-headed arrow indicates the distance between the HUE and the HNB. + +**Figure 8.2-2: UL interference test setup** + +document. + +The MNB emulator is configured to transmit a P-CPICH and a P-CCPCH. The latter physical channel carries the BCH on which SIB5 is transmitted, providing an indication of the P-CPICH Tx Power. Note that the actual transmit power of the P-CPICH does not need to align with this signalled value. Sufficient other SIBs must also be present to allow for identification of the NodeB as part of the macro layer, rather than another HNB. The cabled connection to the HNB receiver passes through a variable attenuator (not shown in the figure above) such that the pilot power (RSCP) arriving at the HNB can be controlled. + +The HNB makes measurements, as defined in Section 7.1 above, of the macro P-CPICH RSCP and the decoded P-CPICH Tx Power IE in order to estimate the pathloss to the MNB. From this estimate it can derive a value for the maximum HUE allowable transmit power such that the noise rise at the macro layer is constrained. This value will be signalled to the HUE as part of a subsequent RL Setup procedure for AMR 12.2 kbps service and can be logged at the HUE for verification. + +#### 8.2.1.2 Test parameters + +Based on the analysis in subclause 7.4.1 above, the following test parameters are specified for the co-channel and adjacent channel cases. The maximum allowable HUE transmit power is defined such that it causes no more than [1dB] noise rise at the MNB: + +**Table 8.2-1: Co-channel UL test parameters** + +| Signalled P-CPICH Tx Power (on MNB BCH) | Pathloss 1 | P-CPICH RSCP at HNB | Maximum allowable HUE Tx power 2 | +|-----------------------------------------|-----------------------|---------------------|---------------------------------------------| +| 33 dBm | 100 dB | -67 dB | ≤ [-9 dBm] | +| 33 dBm | 140 dB | -107 dB | ≤ [21 dBm] | + +**Table 8.2-2: Adjacent channel UL test parameters** + +| Signalled P-CPICH Tx Power (on MNB BCH) | Pathloss 1 | P-CPICH RSCP at HNB | Maximum allowable HUE Tx power 2 | +|-----------------------------------------|-----------------------|---------------------|---------------------------------------------| +| 33 dBm | 100 dB | -67 dB | ≤ [21 dBm] | +| 33 dBm | 140 dB | -107 dB | ≤ [21 dBm] | + +Notes: + +1. The Pathloss of 100dB and 140dB represent typical “cell-site” and “cell-edge” scenarios respectively. +2. The maximum allowable HUE Tx power is capped at a maximum level of [21 dBm] as per Section 7.4.1 above. + +### 8.2.2 HSUPA tests + +#### 8.2.2.1 HNB-Macro tests + +For the uplink tests, we again consider three deployment scenarios: a) HNB with 70dB coverage radius, b) HNB with 80dB coverage radius, and c) HNB with 90dB coverage radius. Separate cell edge and cell site tests are specified. The uplink tests are to be carried out in a cabled-up lab setup. The HNB and MNB in these tests are on the same carrier frequency (i.e., co-channel). All the path loss values specified here include antenna gains. + +For the cell edge tests, the test setup is as displayed in Figure 8.2.2.1-1(i). The HUE, HNB and MUE path loss to the MNB is assumed to be 140dB. The MNB is assumed to experience interference at -101dBm from users other than the HUE, which is modelled through an AWGN noise source (not shown in the picture). Two BS testers are used as the HUE and the MUE, which are connected to the HNB and the MNB through channel emulators. AWGN channel is assumed and path loss values of the links are set as specified in the test description. The MUE is set to transmit at 21dBm max Tx power, with power control disabled. The HNB is run with the regular UL scheduler and power control enabled with full queue traffic. The UL throughput and the transmit power at the BS tester (HUE) is measured. The MNB does not play any role in the test requirements. + +For the cell site tests, a HNB, a MNB and a single BS tester (HUE) are used (Figure 8.2.2.1-1(ii) ). The HUE and HNB path loss to the MNB is assumed to be 100dB. A channel emulator is used to adjust the path loss between the HUE and + +document. + +the HNB. The HNB is operated with the regular UL scheduler with full queue traffic. The UL throughput and the transmit power at the BS tester (HUE) is measured. It should be noted that since there is no MUE present in this test, the only purpose of having a MNB is for path loss estimation in case it is used by the HNB. + +The E-DPDCH demodulation tests for FRC1 and FRC2 for Ped A channel with no Rx diversity have been used as reference to show that the transmit power and throughput requirements for the cell-edge and cell-site tests are indeed achievable. However, since the power control is enabled for these tests, AWGN channel is used instead of PedA to minimize the fluctuations in HUE tx power and throughput (due to fading). + +![Figure 8.2.2.1-1: UL test setup. The diagram consists of two parts, (i) and (ii). Part (i) shows a Mobile Node (MNB) at the top left, a Home User Equipment (HUE) at the bottom left, and a Home NodeB (HNB) at the bottom right, all within a rectangular boundary. Dashed arrows labeled 'X' point from the MNB to both the HUE and the HNB. A dashed arrow labeled 'Y' points from the HUE to the HNB. Part (ii) shows the same setup but adds a Mobile User Equipment (MUE) at the top right. Dashed arrows labeled 'X' point from the MNB to the HUE, HNB, and MUE. A dashed arrow labeled 'Y' points from the HUE to the HNB, and a dashed arrow labeled 'Z' points from the HNB to the MUE.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Figure 8.2.2.1-1: UL test setup. The diagram consists of two parts, (i) and (ii). Part (i) shows a Mobile Node (MNB) at the top left, a Home User Equipment (HUE) at the bottom left, and a Home NodeB (HNB) at the bottom right, all within a rectangular boundary. Dashed arrows labeled 'X' point from the MNB to both the HUE and the HNB. A dashed arrow labeled 'Y' points from the HUE to the HNB. Part (ii) shows the same setup but adds a Mobile User Equipment (MUE) at the top right. Dashed arrows labeled 'X' point from the MNB to the HUE, HNB, and MUE. A dashed arrow labeled 'Y' points from the HUE to the HNB, and a dashed arrow labeled 'Z' points from the HNB to the MUE. + +**Figure 8.2.2.1-1: UL test setup** + +The test requirements for the different HNB coverage scenarios are given below. + +##### 8.2.2.1.1 Uplink test for HNB with 70dB coverage radius + +The purpose of the test is for the HUE to achieve a minimum UL throughput while its average total transmit power does not exceed the requirement given in Table 8.2.2.1.1-1. + +For the cell edge test, the HUE transmit power can go as high as the maximum limit of 21 dBm. The test requirement is in terms of an upper limit for the HUE average transmit power while the HUE average throughput is above a certain value. The throughput and transmit power requirements are chosen based on an Ec/No target of 0.8 dB (corresponding to the FRC2 E-DPDCH demodulation test). + +For the cell site test, the maximum Tx power is specified such that the HUE interference at the MNB which is 100dB away is limited to 5dB below the noise floor of the MNB which is -103dBm. Here again, an Ec/No target of 0.8 dB is used. + +document. + +**Table 8.2.2.1.1-1: UL test specifications - 70dB HNB coverage** + +| Parameter | Cell Edge | Cell Site | +|------------------|-----------------------|-----------------------| +| PL to MNB | 140dB | 100dB | +| PL MUE to HNB | 80dB | - | +| HUE Throughput | $\geq 811\text{kbps}$ | $\geq 811\text{kbps}$ | +| HUE Tx Power | $\leq 21\text{dBm}$ | $\leq -8\text{dBm}$ | + +##### 8.2.2.1.2 Uplink test for HNB with 80dB coverage radius + +The purpose of the test is for the HUE to achieve a minimum uplink throughput at the HNB for cell site case while its average total transmit power does not exceed the requirement given in Table 8.2.2.1.1-2. + +For the cell edge test, the HUE transmit power can go as high as the maximum limit of 21 dBm. The test requirement is specified in terms of an upper limit for the HUE average transmit power while the HUE average throughput is above a certain value. The throughput and transmit power requirements are chosen based on an Ec/No target of -2.4 dB (corresponding to the FRC1 E-DPDCH demodulation test). + +For the cell site test, the maximum tx power is specified such that the HUE interference at the MNB which is 100dB away is limited to 5dB below the noise floor of the MNB which is -103dBm. Here, an Ec/No target of 0.8 dB is used (corresponding to the FRC2 E-DPDCH demodulation test). + +**Table 8.2.2.1.1-2: UL test specifications - 80dB HNB coverage** + +| Parameter | Cell Edge | Cell Site | +|------------------|-----------------------|-----------------------| +| PL to MNB | 140dB | 100dB | +| PL MUE to HNB | 80dB | - | +| HUE Throughput | $\geq 405\text{kbps}$ | $\geq 811\text{kbps}$ | +| HUE Tx Power | $\leq 21\text{dBm}$ | $\leq -8\text{dBm}$ | + +##### 8.2.2.1.3 Uplink test for HNB with 90dB coverage radius + +The purpose of the test is for the HUE to achieve a minimum uplink throughput at the HNB for the cell edge case while its average total transmit power does not exceed the requirement given in Table 8.2.2.1.1-3. A cell site test is not specified for this particular HNB coverage case due to the fact that the max Tx power limit of 20dBm on the HNB does not allow the coverage to be 90dB. + +For the cell edge test, the HUE transmit power can go as high as the maximum limit of 21 dBm. The test requirement is specified in terms of an upper limit for the HUE average transmit power while the HUE average throughput is above a certain value. The throughput and transmit power requirements are chosen based on an Ec/No target of -2.4 dB (corresponding to the FRC1 E-DPDCH demodulation test). + +document. + +**Table 8.2.2.1.1-3: UL test specifications - 90dB HNB coverage** + +| Parameter | Cell Edge | +|----------------|-----------------| +| PL to MNB | 140dB | +| PL MUE to HNB | 90dB | +| HUE Throughput | $\geq 405$ kbps | +| HUE Tx Power | $\leq 21$ dBm | + +#### 8.2.2.2 Inter-HNB uplink test + +The inter-HNB test corresponds to two neighbouring HNBs on the same carrier as shown in Figure 8.2.2.2-1. + +![Diagram of Inter-HNB uplink test set-up showing two apartments (Apartment 1 and Apartment 2) separated by a wall. Apartment 1 contains HUE1 and HNB1. Apartment 2 contains HUE2 and HNB2. Arrows indicate path loss (PL) values: PL12=87dB from HUE1 to HNB2, PL11=60dB from HUE1 to HNB1, PL21=60dB from HUE2 to HNB1, and PL22=75dB from HUE2 to HNB2. The distance between the apartments is 10 m by 10 m.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +Diagram of Inter-HNB uplink test set-up showing two apartments (Apartment 1 and Apartment 2) separated by a wall. Apartment 1 contains HUE1 and HNB1. Apartment 2 contains HUE2 and HNB2. Arrows indicate path loss (PL) values: PL12=87dB from HUE1 to HNB2, PL11=60dB from HUE1 to HNB1, PL21=60dB from HUE2 to HNB1, and PL22=75dB from HUE2 to HNB2. The distance between the apartments is 10 m by 10 m. + +**Figure 8.2.2.2-1: Inter-HNB uplink test set-up** + +The purpose of the test is for the HUEs to maintain a minimum uplink throughput at their own HNBs while their total transmit powers do not exceed the requirements given in Table 8.2.2.2-1. + +The test requirement is specified in terms of an upper limit for the HUE average transmit power while the HUE average throughput is above a certain value. The throughput and transmit power requirements are chosen based on an Ec/No target of 0.8 dB (corresponding to the FRC2 E-DPDCH demodulation test). + +**Table 8.2.2.2-1: Specifications for UL inter-HNB test** + +| Parameter | HUE1 | HUE2 | +|----------------|-----------------|-----------------| +| HUE Throughput | $\geq 811$ kbps | $\geq 811$ kbps | +| HUE Tx Power | $\leq -11$ dBm | $\leq -12$ dBm | + +# 9 Summary + +# --- 10 Conclusions + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2008-06 | RAN4#47 bis | | | | TR created based on content in R4-081548 | | 0.2.0 | +| 2008-08 | RAN4#48 | R4-082045 | | | Agreed TPs in RAN4#47bis:
R4-081380, "TP for 25.9xx: Structure of chapter 6, HNB Class definition" | 0.2.0 | 0.3.0 | +| 2008-11 | RAN4#49 | R4-083250 | | | Agreed TPs in RAN4#48bis:
R4-082623, "Merged Text Proposal for HNB TR25.9xx – Home NodeB RF"
R4-082624, "Merged Text Proposal for HNB TR25.9xx: DL Interference Mitigation for Home NodeB RF"
R4-082316, "Text Proposal for HNB TR25.9xx: Guidance on UL interference mitigation" | 0.3.0 | 0.4.0 | +| 2008-12 | RAN#42 | RP-080972 | | | Approved TR in RAN#42:
RP-080972 "TR 25.9xx v 1.0.0, FDD Home NodeB RF Requirements Work Item Technical Report" | 0.4.0 | 1.0.0 | +| 2009-01 | RAN4#49 bis | R4-090394 | | | Approved TPs in RAN4#49bis:
R4-090349, " Text Proposals for TR 25.967 – Home NodeB RF, chapter 7"
R4-090383, " Text Proposals for TR 25.967 – Home NodeB RF, chapters 1 to 6" | 1.0.0 | 1.1.0 | +| 2009-02 | RAN4#50 | R4-091032 | | | Approved TPs in RAN4#50:
R4-091026, " Text Proposal for TR25.967 regarding switch off upon RF-Tx-failure in Chapters 2 and 7.4"
R4-091027, " Text Proposal for TR25.967 for improvement of reading in Chapters 3 and 7.3.1" | 1.1.0 | 2.0.0 | +| 2009-03 | RAN#43 | RP-090284 | | | Technical Report Approved. | 2.0.0 | 8.0.1 | +| 2009-05 | RAN#44 | RP-090561 | 2 | | Enhanced interference management methods for controlling HNB transmit power | 8.0.1 | 9.0.0 | +| 2009-05 | RAN#44 | RP-090561 | 3 | | Enhanced HNB interference coordination based on network control | 8.0.1 | 9.0.0 | +| | SA-51 | | | | Upgraded unchanged from Rel-9 | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25968/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/25_series/25968/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7f1ced6a78078dad959b0115ac46a846eec50f7 --- /dev/null +++ b/marked/Rel-16/25_series/25968/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb96555aca7b28e8a9e0fe80d8940c0012ae01dbde518ecc2ff5655eb6be1b20 +size 31572 diff --git a/marked/Rel-16/25_series/25968/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Rel-16/25_series/25968/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40a7699ad5ba108706113d4bf24127f04e93f4d --- /dev/null +++ b/marked/Rel-16/25_series/25968/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55aa25fca6e8997ce287e945f53af1fc9e931bd7a2ae0b33c27b1fc853e14901 +size 84674 diff --git a/marked/Rel-16/25_series/25968/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/25_series/25968/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc59312b97de7ea1eca157bcbb5253997e18dd0a --- /dev/null +++ b/marked/Rel-16/25_series/25968/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a86222278fa5b8d9d12861420fa5600c89aac0a0cebea00405f5e6e73d66d636 +size 28574 diff --git a/marked/Rel-16/25_series/25968/raw.md b/marked/Rel-16/25_series/25968/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..75611cb30e929137fa04eae568bba6d5cf46446a --- /dev/null +++ b/marked/Rel-16/25_series/25968/raw.md @@ -0,0 +1,550 @@ + + + + +document. + +**2** Error! No text of +specified style in + +Error! No text of specified style in + +document. + +# Contents + +| | | +|---------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 General..... | 5 | +| 4.1 Task description ..... | 6 | +| 5 Radio scenarios ..... | 6 | +| 5.1 Deployment configurations ..... | 6 | +| 5.2 Interference scenarios..... | 6 | +| 6 HNB class definition..... | 6 | +| 6.1 Changes in 3GPP TS 25.105..... | 6 | +| 6.1.1 Changes on transmitter characteristics ..... | 6 | +| 6.1.1.1 Maximum Home NodeB output power ..... | 6 | +| 6.1.1.2 Frequency Accuracy ..... | 7 | +| 6.1.1.3 summary of transmitter change..... | 7 | +| 6.1.2 Changes on receiver characteristics..... | 7 | +| 6.1.2.1 Sensitivity ..... | 7 | +| 6.1.2.2 Dynamic range..... | 7 | +| 6.1.2.3 Adjacent channel selectivity (ACS)..... | 8 | +| 6.1.2.4 Blocking characteristics..... | 8 | +| 6.1.2.5 Intermodulation characteristics..... | 8 | +| 6.1.2.6 summary of receiver change..... | 8 | +| 6.1.3 Changes on demodulation characteristics..... | 8 | +| 6.2 Changes in 3GPP TS 25.142..... | 9 | +| 6.2.1 Changes on transmitter characteristics ..... | 9 | +| 6.2.2 Changes on receiver characteristics..... | 9 | +| 6.2.3 Changes on demodulation characteristics..... | 9 | +| 7 Guidance on how to control HNB interference ..... | 10 | +| 7.1 HNB measurements..... | 10 | +| 7.2 Control of output power of Home NodeB..... | 11 | +| 7.3 AGC of Home NodeB ..... | 12 | +| 7.4 HNB Self Configuration..... | 13 | +| 7.4.1 Carrier selection or reselection:..... | 13 | +| 7.4.2 Automatic neighbouring cells configuration: ..... | 14 | +| 7.5 Synchronization..... | 14 | +| 7.5.1 Initial synchronization ..... | 14 | +| 7.5.2 Periodic synchronization ..... | 15 | +| 8 Interference tests ..... | 16 | +| 8.1 Adjacent channel deployment..... | 16 | +| 8.2 Co-channel deployment..... | 16 | +| Annex A: Change history ..... | 17 | + +document. + +# --- 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. + +document. + +# --- 1 Scope + +This document is a technical report which was requested in the Objective of the RAN4 work item description “1.28Mcps TDD Home NodeB RF requirements” [1]. The goal of this technical report is to describe the agreed approach towards the RF related issues raised in [1]: + +- A) The existing 1.28Mcps BS classes did not fully address the RF requirements of the Home NodeB application. Proposals for changes to radio performance requirement specifications TS 25.105 are therefore provided in this report, together with the proposals for the test specification TS 25.142. +- B) The report intends to provide guidance to mitigate interference and clarify some interference cases + +# --- 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] R4-091435, “WI on 1.28Mcps TDD Home NodeB RF Requirements”, 3GPP RAN WG#46 Sanya China Dec.2009 TD Tech, CMCC, CATT, Picochip Designs, ZTE +- [2] R4-091232, “25.866 TR on 1.28Mcps TDD Home NodeB ”, 3GPP RAN WG#46 Sanya China Dec.2009 TD Tech + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the terms and definitions given in TR 21.905 [54] 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 [54]. + +## 3.1 Definitions + +## 3.2 Symbols + +## 3.3 Abbreviations + +- DL Downlink, the RF path from BS to UE +- UL Uplink, the RF path from UE to BS + +# --- 4 General + +As agreed in the work item proposal [1]: + +An increasing need for 1.28Mcps TDD Home NodeBs is observed to provide attractive services and data rates in home environments in China as a consequence of a large number of TD-SCDMA subscribers within recent years. + +document. + +Whereas UTRAN is not optimally suited for this application, as it was developed and defined under the assumption of coordinated network deployment. Actually home NodeBs are typically associated with uncoordinated and large scale deployment. + +Aim of this work item is to amend the 1.28Mcps TDD Home NodeB related RF specifications as suggested in the RAN4 specific part of TR 25.866 to support the Home NodeBs application. No changes to the UE RF specifications are foreseen. + +## 4.1 Task description + +TR 25.866 suggests that the existing 1.28Mcps TDD Base Station classes do not fully address the RF requirements of the Home NodeB application. TR 25.866 summarises the areas where changes to TS 25.105 are expected to transmitter characteristics, receiver characteristics and performance respectively. And guidance to mitigate interference and interference test are needed to be investigated. Correspondingly, there are 2 objects in this WI, + +- To update the RF requirement specification TS 25.105 as suggested by TR 25.866. +- Guidance to mitigate interference and interference test are need clarification. + +# 5 Radio scenarios + +## 5.1 Deployment configurations + +## 5.2 Interference scenarios + +# 6 HNB class definition + +## 6.1 Changes in 3GPP TS 25.105 + +This section describes the changes to BS RF requirements specifications TS 25.105 + +### 6.1.1 Changes on transmitter characteristics + +#### 6.1.1.1 Maximum Home NodeB output power + +**Maximum output power**, Pmax, of the base station is the mean power level per carrier of the base station measured at the antenna connector in a specified reference condition. The period of measurement shall be a transmit timeslot excluding the guard period. Considering interference of Home NodeB, it is suggested that Home NodeB output power should be controlled. According to TR25.866, Considering two common Home NodeB scenarios(Home and small-scale corporation), the following two Max. output power level are recommended in Table 6.1.1.1-1. + +**Table 6.1.1.1-1: Recommended power of Home NodeB** + +| Power class | Max. output Power | Scenario | +|-------------|-------------------|-------------------------| +| 1 | 20 mW (13dBm) | Home | +| 2 | 100 mW(20dBm) | Small-scale Corporation | + +Correspondingly, the rated output power, PRAT, of the Home NodeB is suggested to be specified in the TS 25.105. + +In summary, two types of Home NodeB should be defined in specifications, that is, + +- type 1: the output power of the Home NodeB is limited to 20 dBm +- type 2: the output power of the Home NodeB is limited to 13 dBm + +document. + +A minimum requirements was also introduced: In normal conditions, the Base station maximum output power shall remain within +2 dB and -2dB of the manufacturer's rated output power. In extreme conditions, the Base station maximum output power shall remain within +2.5 dB and -2.5dB of the manufacturer's rated output power. In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +#### 6.1.1.2 Frequency Accuracy + +Considering Home NodeBs are usually deployed at home and office, it is most likely that the serving UEs are in slow mobility profile and a consensus was reached that the Home NodeB is expected to support UE speeds up to 30km/h speed during the 1.28Mcps TDD Home NodeB SI. + +According to 25.866 simulation results, the Home NodeB modulated carrier frequency can be relaxed to 0.25 PPM. + +#### 6.1.1.3 summary of transmitter change + +The changes on transmitter characteristics in TS 25.105 are summarised in the following table. + +**Table 6.1.1.3-1: Changes on transmitter characteristics to TS 25.105** + +| Section | Requirement | Discussion / Required Changes | +|---------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.2 | Base station classes | Add a new BS class – Home NodeB. Home NodeBs are characterized by requirements derived from Femto Cell scenarios. | +| 6.2.1 | Base station maximum output power | Two types of Home NodeB should be defined in specifications, that is,
type 1: the output power of the HNB is limited to 20 dBm
type 2: the output power of the HNB is limited to 13 dBm | +| 6.3 | Frequency error | Added frequency error requirement for Home BS
It was agreed on a minimum frequency error of 0.25ppm | + +### 6.1.2 Changes on receiver characteristics + +#### 6.1.2.1 Sensitivity + +According to 3GPP TR25.866, using the reference measurement channel specified in 25.105 Annex A, the reference sensitivity level and performance of the BS shall be as specified in Table 6.1.2.1-1. + +**Table 6.1.2.1-1: 1.28Mcps TDD Home NodeB reference sensitivity level** + +| BS Class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|-------------------------|-----------------------------------------|--------------------------------|----------------------------| +| 1.28Mcps TDD Home NodeB | 12.2 kbps | -101 dBm | BER shall not exceed 0.001 | + +#### 6.1.2.2 Dynamic range + +Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel. + +Considering impact of co-channel uplink interference on the Home NodeB, it is possible that Home NodeB receiver will be exposed to strong interference signals from un-coordinated UEs. It was shown that the FDD Home NodeB dynamic range requirement needs to be extended by 20dB to protect the HNB from the strong interference signal of an un-coordinated UE. This conclusion can be reused in 1.28Mcps TDD Home NodeB. + +The BER shall not exceed 0.001 for the parameters specified in Table 6.1.2.2-1. + +document. + +**Table 6.1.2.2-1: Dynamic Range of 1.28Mcps TDD Home NodeB Receiver** + +| Parameter | Level | Unit | +|-----------------------------------------|-------|--------------| +| Reference measurement channel data rate | 12.2 | kbps | +| Wanted signal mean power | -51 | dBm | +| Interfering AWGN signal | -47 | dBm/1.28 MHz | + +#### 6.1.2.3 Adjacent channel selectivity (ACS) + +Adjacent channel selectivity (ACS) is defined as a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of a single code CDMA modulated adjacent channel signal at a given frequency offset from the center frequency of the assigned channel. ACS is the ratio of the receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s). + +The BER shall not exceed 0.001 for the parameters specified in Table 6.1.2.3-1. + +**Table 6.1.2.3-1: Adjacent channel selectivity of 1.28Mcps TDD Home NodeB Receiver** + +| Parameter | Level | Unit | +|-----------------------------------------|-------|------| +| Reference measurement channel data rate | 12.2 | kbps | +| Wanted signal mean power | -77 | dBm | +| Interfering AWGN signal | -28 | dBm | + +#### 6.1.2.4 Blocking characteristics + +Blocking requirement of Home NodeB is same as Local Area BS. + +#### 6.1.2.5 Intermodulation characteristics + +Intermodulation requirement of Home NodeB is same as Local Area BS. + +#### 6.1.2.6 summary of receiver change + +The changes on receiver characteristics in TS 25.105 are summarised in the following table. + +**Table 6.1.2.6-1: Changes on receiver characteristics in TS 25.105** + +| Section | Requirement | Discussion / Required Changes | +|---------|---------------------------------|--------------------------------------------| +| 7.2 | Reference sensitivity level | Added requirement for Home NodeB. | +| 7.3 | Dynamic range | Added minimum requirement for Home NodeB. | +| 7.4 | ACS | Added minimum requirement for Home NodeB. | +| 7.5 | Blocking characteristics | Added minimum requirements for Home NodeB. | +| 7.6 | Intermodulation characteristics | Added minimum requirements for Home NodeB. | + +### 6.1.3 Changes on demodulation characteristics + +To Multi-path Fading environment shown in Table B.2 of 25.105, case 1 is recommended for 1.28Mcps TDD Home NodeB demodulation. + +To Propagation Conditions for Multipath Fading Environments for E-DCH Performance Requirements for 1,28 Mcps TDD shown in Table B.2A of 25.105 , ITU Pedestrian A speed 3km/h (PA3), ITU Pedestrian B speed 3km/h (PB3) and ITU vehicular A speed 30km/h (VA30) are suitable to 1.28Mcps TDD Home NodeB. + +To Parameters in static propagation conditions and multipath Case 1 channel, Ioc will be changed according to sensitivity of Home NodeB. + +document. + +## 6.2 Changes in 3GPP TS 25.142 + +This section describes the considered changes to base station conformance testing. + +### 6.2.1 Changes on transmitter characteristics + +The changes on transmitter characteristics in TS 25.142 are summarised in the following tables. Requirements which are not shown are applicable to Home NodeB without any modifications from the existing specifications. + +**Table 6.2.1-1: Changes on transmitter characteristics to TS 25.142** + +| Section | Requirement | Discussion / Required Changes | +|---------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 | Base station maximum output power | Two types of Home NodeB should be defined in specifications, that is,
type 1: the output power of the HNB is limited to 20 dBm
type 2: the output power of the HNB is limited to 13 dBm | +| 6.3 | Frequency stability | Added frequency stability requirement for Home NodeB
It was agreed on a minimum frequency error of 0.25ppm | + +### 6.2.2 Changes on receiver characteristics + +The changes on receiver characteristics in TS 25.142 are summarised in the following table. + +**Table 6.2.2-1: Changes on receiver characteristics in TS 25.142** + +| Section | Requirement | Discussion / Required Changes | +|---------|---------------------------------|--------------------------------------------| +| 7.2 | Reference sensitivity level | Added requirement for Home NodeB. | +| 7.3 | Dynamic range | Added minimum requirement for Home NodeB. | +| 7.4 | ACS | Added minimum requirement for Home NodeB. | +| 7.5 | Blocking characteristics | Added minimum requirements for Home NodeB. | +| 7.6 | Intermodulation characteristics | Added minimum requirements for Home NodeB. | + +### 6.2.3 Changes on demodulation characteristics + +To Multi-path Fading environment shown in Table B.2 of 25.142, case 1 is recommended for 1.28Mcps TDD Home NodeB demodulation. + +To Propagation Conditions for Multipath Fading Environments for E-DCH Performance Requirements for 1,28 Mcps TDD shown in Table B.2A of 25.142 , ITU Pedestrian A speed 3km/h (PA3), ITU Pedestrian B speed 3km/h (PB3) and ITU vehicular A speed 30km/h (VA30) are suitable to 1.28Mcps TDD Home NodeB. + +To Parameters in static propagation conditions and multipath Case 1 channel, Ioc will be changed according to sensitivity of Home NodeB. + +# 7 Guidance on how to control HNB interference + +## 7.1 HNB measurements + +The HNB and its HUE can perform some measurements from the surrounding HNB, Macro UE, HUE and Macro NodeB (MNB) such that HNB can apply some algorithms to perform interference mitigation and maintain the HNB coverage. The potential measurements collected by HNB can be through the Connected Mode UEs attached to the HNB during normal operation mode or via a DL Receiver function within the HNB itself in self-configuration mode. Such DL receiver function is also called Network Listen Mode (NLM) or “HNB Sniffer”. The following measurements can be performed by the HNB and its attached HUE and utilized for interference mitigation. + +- 1) P-CCPCH RSCP: + +document. + +- HNB can inform its DL Receiver HUE perform the PCCPCH RSCP measurement of the neighbouring cells including the Macro NodeB and HNB and report it to the HNB. Based on the measurement, the HNB can estimate the DL interference from neighbouring cell to the HUE, further HNB can control the transmit power of HUE such that the HUE's UL interference to other cells (HNB and Macros) at a reasonable level. +- In "Sniffer mode", HNB itself can also perform the P-CCPCH RSCP of the neighbouring cells including the Macro NodeB and HNB and can estimate the DL interference towards the HUE. Base on the measurement, HNB can control the HUE transmit power such that the HUE UL interference to other cells (HNB and Macros) at a reasonable level. +- As the 1.28Mcps TDD system usually operate in multiple carrier, the measurements of the PCCPCH RSCP and UTRA RSSI can help the HNB choose the proper carrier with less interference to reside on or estimate the potential interference from the neighboring cell to the HUE, such that it can perform the power control or shift to another carrier to avoid the interference. + +### 2) ISCP: + +- HNB can perform the ISCP measurement in a specified time slot in uplink and thus it can estimate the interference from neighbouring cell in both UL and DL. If the ISCP measurement value is larger than a pre-defined threshold (where an interfering MUE is close to HNB), which would mean the MUE's Tx power cause significant interference towards the HNB, HNB can choose to shift to work in another carrier to avoid the strong UL interference or communicate with the interfering cell to coordinate the interference. +- HNB can inform the HUE perform the ISCP and report the ISCP measurement in DL. Judging from the report, HNB can estimate the interference level such that it can perform transmit power control or coordinate the HUE to another timeslot or carrier to avoid the interference. + +### 3) Midamble Strength of Neighbouring Cells: + +- By self-configuration, HNB can have the neighbouring cell list and the midamble sequences used by the neighbouring cells. When HNB experiences the strong interference in UL, it can find the potential interfering cell by estimating the Midamble strength of the potential cells for the neighbouring list such that HNB can avoid the strong interference by shifting to another carrier or scheduling HUE to another UL time slot. +- As 1.28Mcps TDD system operate in multiple carriers, usually only the primary carrier have the P-CCPCH, when HUE experience some strong interference from the secondary carrier of some neighbouring cells in DL, HUE can estimate the interference strength by estimating the midamble strength of the potential neighbouring cells and report to the HNB. Base on the report, some interference management can be performed by the HNB. + +### 4) Macro/HNB Cell to HNB Pathloss: + +- In self-configuration mode, HNB can read the BCH of macro cell and neighbouring HNB and know the transmit power of the P-CCPCH. Knowing the P-CCPCH transmit power and the received power of the P-CCPCH, HNB can deduce the pathloss from Macro cell or neighbouring HNB to HNB. By knowing the Pathloss from Macro Cell/Neighbouring to HNB, HNB can adjust it's transmit power or control the transmit power of the HUE such that it have less interference to the neighbouring or it can control the DL and UL performance at a reasonable level. + +### 5) Cell ID, LAC and RAC Measurements: + +- The HNB can have the Cell ID or LAC or RAC information in self-configuration and normal configuration by performing the physical layer measurement and reading BCH of macro cell and neighbouring HNB. Based on the measurements, HNB can identify its surrounding macrocells and other HNBs nearby, and broadcast the information to the HUE to have HUE distinguish the HNB cell and Macro Cell for purposes such as mobility handling and cell reselection etc. + +## 7.2 Control of output power of Home NodeB + +Considering interferences between Home NodeB and Macro BS and among Home NodeBs, interference scenarios are listed in Table 1 and shown in Figure 1 and Figure 2. To scenario 2, Home NodeB Downlink will interfere with Macro UE. The worst case is that the Macro UE is close to Home NodeB and Macro UE located at the cell edge of Macro BS. + +document. + +Of course, the output power of Home NodeB is big factor to this scenario. To scenario 6, Home NodeB Downlink will interfere with HUE which belongs to other Home NodeB. + +**Table 7.2-1: Interference Scenarios** + +| Number | Aggressor | Victim | +|--------|--------------------------------------|---------------------------------| +| 1 | UE attached to Home Node B (Uplink) | Macro Node B Uplink | +| 2 | Home Node B (Downlink) | Macro Node B Downlink (UE) | +| 3 | UE attached to Macro Node B (Uplink) | Home Node B Uplink | +| 4 | Macro Node B (Downlink) | Home Node B Downlink | +| 5 | UE attached to Home Node B (Uplink) | Home Node B Uplink (Home NodeB) | +| 6 | Home Node B (Downlink) | Other Home Node B Downlink (UE) | + +3GPP 25.866 gives the simulation result of scenario 2. It is shown results in high outage probability and throughput loss are indicated at locations where the macro P-CCPCH and HSDPA are fairly weak for the co-channel deployment. In this case the interference can be reduced for example by lowering the Home NodeB maximum output power. According to the simulation results, there is a need to set the maximum Home NodeB output power to lower than 0dBm, or in some cases even below that, in order to obtain an acceptable “coverage vs. interference” trade-off. + +The adjacent channel deployment is found to work much better. The Home NodeB maximum output power could be much higher than the co-channel deployment scenario. However, assuming some form of downlink interference control also for the adjacent channel scenario could further improve the HNB performance. + +In this scenario, Home NodeB should have capability to know the interference strength between Macro UE and Home NodeB. e.g. Home NodeB measure uplink interference result from Macro UE. If uplink interference is beyond the limitation which is set by Home NodeB itself, Home NodeB can suppose that Macro UE is approaching Home NodeB, and Home NodeB will decrease the output power of Home NodeB. If uplink interference is below the limitation which is set by Home NodeB itself, Home NodeB will ignore interference from Macro UE, common power control algorithm are applied to power control of Home NodeB. + +It is also a solution that Maximum output power of Home NodeB will be set according to P-CCPCH RSCP of Macro BS for mitigating Macro UE interference result from Home NodeB, especially when Macro UE is at the edge of the cell with bad reception quality. In detail, When Home NodeB is close to Macro BS, Home NodeB can be set high output power because Macro UE have good reception quality in this area. When Home NodeB is the edge of cell, Home NodeB can be set low output power because Macro UE have bad reception quality in this area. Additionally, if P-CCPCH RSCP of Macro BS is so low that no Macro BS can have in the vicinity of Home NodeB. In this case, Home NodeB can transmit with maximum output power. + +3GPP 25.866 gives the simulation result of scenario 6. It is shown that frequency reuse 3 can increase the throughput of Home NodeB. In order to enhance the throughput of HNB, more frequency band should be reserved for Home NodeB. In this scenario, the distance between Home NodeBs is key point to mitigate interference. However, it is managed by operators. So it is suggested that Home NodeB should have capability to know the uplink interference strength. + +document. + +12Error! No text of specified style in + +Error! No text of specified style in + +![Diagram of interference scenarios 1, 2, 3, and 4. A Macro BS is on the left. A circular cell on the right contains a Home NodeB and a Macro UE. Scenario 1 shows a signal from the Macro BS to an HNB UE. Scenario 2 shows a signal from the Macro BS to the Home NodeB. Scenario 3 shows a signal from the Macro UE to the Home NodeB. Scenario 4 shows a signal from the Macro BS to the Macro UE.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram of interference scenarios 1, 2, 3, and 4. A Macro BS is on the left. A circular cell on the right contains a Home NodeB and a Macro UE. Scenario 1 shows a signal from the Macro BS to an HNB UE. Scenario 2 shows a signal from the Macro BS to the Home NodeB. Scenario 3 shows a signal from the Macro UE to the Home NodeB. Scenario 4 shows a signal from the Macro BS to the Macro UE. + +**Figure 7.2-1: Interference Scenarios 1, 2, 3 and Scenarios 4** + +![Diagram of interference scenarios 5 and 6. Two adjacent circular cells are shown. The left cell contains Home NodeB 1 and HNB1 UE. The right cell contains Home NodeB and HNB2 UE. Scenario 5 shows a signal from HNB1 UE to Home NodeB. Scenario 6 shows a signal from HNB2 UE to Home NodeB 1.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Diagram of interference scenarios 5 and 6. Two adjacent circular cells are shown. The left cell contains Home NodeB 1 and HNB1 UE. The right cell contains Home NodeB and HNB2 UE. Scenario 5 shows a signal from HNB1 UE to Home NodeB. Scenario 6 shows a signal from HNB2 UE to Home NodeB 1. + +**Figure 7.2-2: Interference Scenarios 5 and Scenarios 6** + +It is suggested that control of output power can be one of efficient interference mitigation method. It is also suggested that Home NodeB should have capability to know the uplink interference strength. And Maximum output power of Home NodeB will be set according to P-CCPCH RSCP of Macro BS for mitigating Macro UE interference result from Home NodeB, especially when Macro UE is at the edge of the cell with bad reception quality. + +## 7.3 AGC of Home NodeB + +AGC(Automatic Gain Control) is an alternative mitigation technique to address UL interference from uncontrolled UEs towards the HNB and increase in noise rise from a HUE that cannot be powered down due to limited dynamic range. + +25.866 gives that 1.28Mcps TDD Home NodeB dynamic range requirement needs to be extended by 20dB to protect the HNB from the strong interference signal of an un-coordinated UE. Dynamic range of 1.28Mcps TDD Home NodeB is also asked that the BER shall not exceed 0.001 for the parameters specified in shown in Table 7.3-1. + +**Table 7.3-1: Dynamic Range of 1.28Mcps TDD Home NodeB Receiver** + +| Parameter | Level | Unit | +|-----------------------------------------|-------|--------------| +| Reference measurement channel data rate | 12.2 | Kbps | +| Wanted signal mean power | -51 | dBm | +| Interfering AWGN signal | -47 | dBm/1.28 MHz | + +document. + +Adjacent channel selectivity (ACS) requirement is also tighten. The BER shall not exceed 0.001 for the parameters specified in Table 7.3-2. The interfering AWGN signal is increased to -28dBm. + +**Table 7.3 -2: Adjacent channel selectivity of 1.28Mcps TDD Home NodeB Receiver** + +| Parameter | Level | Unit | +|-----------------------------------------|-------|------| +| Reference measurement channel data rate | 12.2 | kbps | +| Wanted signal mean power | -77 | dBm | +| Interfering AWGN signal | -28 | dBm | + +This mitigation approach is based on dynamic control of the receiver gain or UL attenuation, also known as AGC(Automatic Gain Control). Because receiver performance is increased, Home NodeB Uplink is no longer blocking by interfering UE. + +Home NodeB can adjust the receiver gain or UL attenuation, driven by UL measurements. Blocking levels of UL noise rise due to interference can be detected and the receiver gain reduced accordingly. This adjustment would only need to be made temporarily while the UL interference was strong and as soon as the noise rise was seen to fall the receiver gain could be returned to its normal operating value. + +Home NodeB would response this adjustment quickly when the UL interference is strong or noise rise from a HUE is high and slowly decay with time, e.g., to accommodate variations in interference due to bursty traffic. Therefore, it is crucial to determine the correct amount of attenuation that will improve the HUE's performance without degrading the MUEs. + +It is suggested that AGC can be one of efficient interference mitigation method to Home NodeB. + +## 7.4 HNB Self Configuration + +Self configuration can be applied in HNB to mitigate the interference between HNB and neighbour Macro NodeB/neighbour HNB. The trigger of HNB self configuration could be power up, event triggered or periodical measurement report. The following self configuration can be performed by the HNB to mitigate the interference between HNB and Macro NodeB. + +### 7.4.1 Carrier selection or reselection: + +In general, HNB should have abilities to select a carrier frequency using the information of DL and UL interference measurement. For example, HNB or HNB controlled HUE can measure the P-CCPCH RSCP or DL/UL Timeslot ISCP of neighbour Macro NodeB or HNB. When HNB is power on or self configuration is triggered by interference measurement, HNB should select a carrier frequency with smallest interference as its operating frequency. + +As the 1.28Mcps TDD system usually operate in multiple carriers, HNB need to detect the carrier occupation status of neighbour cell's primary frequency and secondary frequency. + +- If DwPTS or P-CCPCH is detected on one candidate carrier, this carrier can be affirmed to be occupied by one neighbour cell's primary frequency. Furthermore, HNB can decode the BCH channel to differentiate the neighbour Macro NodeB and HNB. +- If no DwPTS or P-CCPCH is detected on one carrier, HNB or HNB controlled HUE can measure the RTWP or UL/DL ISCP of the candidate carrier. If the RTWP or ISCP is higher, this carrier may be occupied by neighbour Macro NodeB or HNB's secondary frequency. HNB should select another carrier with smaller RTPW or ISCP as its working frequency. +- The HNB carrier selection priority should be: HNB secondary frequency > HNB primary frequency > Macro NodeB's secondary frequency > Macro NodeB's primary frequency. + +If the frequency of Macro NodeB and HNB is pre-configured with different carrier, HNB needn't to mitigate the HNB-macro interference. HNB only need to detect the carrier occupation status of neighbour HNB's primary and secondary frequency, and select carriers with smaller interference. + +If the frequency of Macro NodeB and HNB is mixed, HNB could detect and distinguish the primary frequency of neighbour Macro NodeB and HNB by BCH information, If HNB carrier selection procedure is limited to the HNB self- + +document. + +obtained information, HNB can't distinguish the secondary frequency of neighbour Macro NodeB and HNB. While the HNB can report neighbour cell's ID to the network controller (i.e. Core Network, HNB-GW), the network controller can feedback the secondary frequency of the corresponding neighbour cell. + +Based on the neighbour cell primary and secondary frequency measurement, HNB can mitigate the HNB-macro and HNB-HNB interference. + +### 7.4.2 Automatic neighbouring cells configuration: + +During the HNB self-configuration mode, HNB should be able to decode the neighbour cells broadcast information and build the following cell lists for inter-cell interference mitigation: + +- Neighbour cell list including Macro NodeBs: The purpose of the neighbour list is to mitigate the UL interference of serving HNB to neighbour Macro NodeBs. +- Neighbour cell list including HNBs. The purpose of the neighbour list is to mitigate the UL interference of serving HNB to neighbour HNBs. + +HNB and HUE can use the following neighbour cell organisation and SNPL reporting mechanism to control the UL interference of serving HNB to neighbour Macro NodeB and HNB. + +- By searching the DwPTS of neighbour Macro NodeB and HNB, and decoding the BCH channel, HNB can get the information of neighbour Macro NodeB and HNB. If each HNB is configured with a LAC that is different from the surrounding macro cells and nearby HNBs, HNB can differentiate the neighbour Macro NodeB and HNB. +- If the neighbour cell list contains all Macro NodeB, HUE can calculate its pathloss to all intra-frequency neighbour Macro cell. In turn, HUE can estimate the mean pathloss to the serving cell (Lserv) and to each of the N neighbour cells, and report the SNPL (Serving and Neighbour cell Pathloss) to serving HNB. Based on the SNPL reporting, serving HNB can control the HUE's interference to neighbour Macro NodeBs under the predefined interference target. +- If the neighbour cell list contains neighbour HNB, HUE can calculate and report the SNPL of neighbour HNB to serving HNB. In turn, serving HNB can control the HUE's interference to neighbour HNBs under the predefined interference target. + +Based on the neighbour cell self configuration in HNB, Some ISCP control method could be introduced in Home NodeB environment. E.g. the same ISCP control method as Macro NodeB or the maximum UL output power of Home UE should be limited by the self optimization process of Control HNB according to the neighbour Home Node B number and distance. + +## 7.5 Synchronization + +### 7.5.1 Initial synchronization + +Home Node B should detect Macro Node B's DwPCH, and define its timing benchmark according to Macro Node B's DwPCH. Considering the complex deployment scenario of Home Node B networks, we advise Macro Node BS and Home Node B be deployed on different frequency band. + +If Home Node B can detect multi Macro Node Bs' signal, it should select the best suitable macro cell from all candidate Macro Node Bs. + +![Figure 7.5.1-1: 1.28Mcps TDD Home NodeB Timing according to Macro Node B's DwPCH. The diagram shows five horizontal timelines representing frames, each with DwPTS (cyan), GP (hatched), and UpPTS (yellow) segments. The top timeline is 'Macro Node B'. Below it is a frame with 'Timing detection' labels, showing a timing advance \tau_{adv} and a macro timing advance \tau_{macBS}. The third frame is 'Timing Ref 1', where the start of DwPTS is \tau_{adv} before the macro's DwPTS start. The fourth frame is 'Timing Ref 2', where the start of DwPTS is aligned with the macro's DwPTS start. The fifth frame is 'Timing Ref 3', where the start of DwPTS is \tau_{macBS} after the macro's DwPTS start. A horizontal axis at the bottom is labeled t.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +15Error! No text of specified style in document. Error! No text of specified style in document. + +Figure 7.5.1-1: 1.28Mcps TDD Home NodeB Timing according to Macro Node B's DwPCH. The diagram shows five horizontal timelines representing frames, each with DwPTS (cyan), GP (hatched), and UpPTS (yellow) segments. The top timeline is 'Macro Node B'. Below it is a frame with 'Timing detection' labels, showing a timing advance $\tau_{adv}$ and a macro timing advance $\tau_{macBS}$ . The third frame is 'Timing Ref 1', where the start of DwPTS is $\tau_{adv}$ before the macro's DwPTS start. The fourth frame is 'Timing Ref 2', where the start of DwPTS is aligned with the macro's DwPTS start. The fifth frame is 'Timing Ref 3', where the start of DwPTS is $\tau_{macBS}$ after the macro's DwPTS start. A horizontal axis at the bottom is labeled $t$ . + +**Figure 7.5.1-1: 1.28Mcps TDD Home NodeB Timing according to Macro Node B's DwPCH** + +Figure 7.5.1-1 gives three candidate 1.28Mcps TDD Home Node B air interface timing adjust methods: + +- Reference 1: The frame boundary of Home Node B precedes anchored macro one with one $\tau_{adv}$ , which is given by macro Node B via a uplink synchronisation procedure; +- Reference 2: The frame boundary of Home Node B is exactly aligned with anchored macro one via uplink synchronisation procedure; +- Reference 3: Home Node B sets its frame boundary at the time point when it detects a downlink synchronisation peak, which in principle lag $\tau_{adv}$ behind anchored macro one. + +If reference 1 or 2 is selected, Home Node B shall behave as a regular 1.28Mcps TDD UE and perform a 'fake' random access in its synchronization. + +If Home Node B can not detect Macro Node Bs' DwPCH, according to its SON characters, Home Node B should select one empty frequency that not occupied by its neighbour Home Node Bs. + +- When Home Node B is power on, it should search the best suitable Home Node B from Home Node B available frequency list, and get its timing advance. +- Apply any type of Home Node B timing reference as shown in figure 1. + +### 7.5.2 Periodic synchronization + +Due to cost concern, Home NodeBs' oscillators with loose timing accuracy and stability requirement were preferred. Therefore 1.28Mcps TDD Home Node B needs to periodically perform a synchronisation corroboration to amend low stability problem to enable working frequency and timing accuracy. + +On top of those detection rules elaborated above, Home NodeB will establish synchronization with the macro station at regular intervals. In the technical specification of 25.866, the description of frequency accuracy for Home NodeB is as follows: + +Taking the conformance of frequency accuracy in the radio interface with the maximum mobility into account, the Home NodeB modulated carrier frequency can be relaxed to 0.25 PPM. + +document. + +So the interval of periodical synchronization will become shorter. If the Home NodeB synchronizes with macro station so frequently, the Home NodeB needs to read the downlink signal often from macro station, it will affect the communication between the Home NodeB and UE in the coverage. So we propose the UE which works in the Home NodeB cell to measure the SFN-SFN observed time difference, and UE will report the measure result to Home NodeB, if the value of SFN-SFN observed time difference is bigger than predefined threshold, the Home NodeB will change the timing using this value. + +SFN-SFN observed time difference is one of UE measurement abilities. It is the time difference of the reception times of frames from two cells (serving and target) measured in the UE and expressed in chips. It is distinguished by two types. Type 2 applies if the serving and the target cell have the same frame timing. + +If there is any UE in the coverage of Home NodeB, a measure of SFN-SFN observed time difference will be configured by Home NodeB for this UE. UE performs the measurement periodically, and report it by event triggered or periodically. If the reporting is event triggered, the condition of reporting is the measurement value expires the predefined threshold. If the Home NodeB receives this measure report, the Home NodeB will change the timing of itself by this value. If the UE reports the measurement periodically, the Home NodeB will compare the measurement value to one predefined threshold, if the value is bigger than threshold, the Home NodeB will align it's timing using this reference. + +If there is no UE in the Home NodeB cell, the Home NodeB will use the method depicted in section 2.1 to synchronize with macro station periodically. + +# --- 8 Interference tests + +## 8.1 Adjacent channel deployment + +In TR 25.866[3], the adjacent channel deployment is found to work much better. At the early stage of Home NodeB deployment, the adjacent channel deployment is suggested for use. The purpose of the test is to ensure that a Home NodeB does not cause unacceptable interference to the adjacent channel operator. The Home NodeB can use measurements such as P-CCPCH RSCP and ISCP to adjust its transmit power such that it does not cause interference for the adjacent channel operator. The core requirements are specified in 25.105[4], corresponding test requirements is also specified in 25.142 R10. + +## 8.2 Co-channel deployment + +In order to ensure reasonable behaviour of Home NodeB and Macro NodeB, two scenarios are considered for Home NodeB deployments: a) cell edge and b) cell centre. + +When Home NodeB is deployed at the cell edge, Macro UE transmits with maximum output power and it's reception power is lowest because of far distance. In this deployment, scenario 2(downlink) and scenario 3(uplink) are concerned interference scenarios. + +When Home NodeB is deployed in the centre of cell, scenario 1(uplink) and scenario 4(downlink) are concerned interference scenarios. + +To interference among Home NodeBs, it is suggested to consider 2 Home NodeBs and each Home NodeB only has one UE. + +Detailed test cases are FFS. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|--------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-02 | RAN4#54 | | | | TR created | | 0.1.0 | +| 2010-05 | RAN4#54 | R4-100490 | | | Text Proposal on changes of transmitter of 1.28Mcps TDD Home NodeB in 25.105 | 0.1.0 | 0.2.0 | +| | | R4-100491 | | | Text Proposal on Receiver of 1.28Mcps TDD Home NodeB in 25.105 | | | +| | | R4-100492 | | | Text Proposal on changes of performance of 1.28Mcps TDD Home NodeB in 25.105 | | | +| | | R4-100493 | | | Text Proposal on changes of transmitter of 1.28Mcps TDD Home NodeB in 25.142 | | | +| | | R4-100494 | | | Text Proposal on Receiver of 1.28Mcps TDD Home NodeB in 25.142 | | | +| | | R4-100495 | | | Text Proposal on changes of performance of 1.28Mcps TDD Home NodeB in 25.142 | | | +| 2010-08 | RAN4#55 | R4-103079 | | | 3GPP TR 25.869 on 1.28Mcps TDD Home NodeB | 0.2.0 | 0.3.0 | +| 2010-08 | RAN4#55 | R4-103080 | | | TP on Interference mitigation method of 1.28Mcps TDD Home NodeB- Measurement test | 0.3.0 | 0.4.0 | +| | | R4-103081 | | | TP on Interference mitigation method of 1.28Mcps TDD Home NodeB- Control of output power of Home NodeB | | | +| | | R4-103082 | | | TP on Interference mitigation method of 1.28Mcps TDD Home NodeB- AGC of Home NodeB | | | +| | | R4-103083 | | | TP on Interference mitigation method of 1.28Mcps TDD Home NodeB- Self Configuration of Home NodeB | | | +| | | R4-103084 | | | TP on Interference mitigation method of 1.28Mcps TDD Home NodeB- Synchronization | | | +| 2010-10 | RAN4#57 | R4-104021 | | | TP on consideration of interference test of 1.28Mcps TDD Home NodeB | 0.4.0 | 0.5.0 | +| 2010-12 | RAN#50 | RP-101166 | | | Presented to RAN for Approval | 0.5.0 | 1.0.0 | +| 2010-12 | RAN#50 | RP-101166 | | | Approved by TSG RAN | 1.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25992/raw.md b/marked/Rel-16/25_series/25992/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0fbd9cc3199295633088f7b55870b103226a7e1a --- /dev/null +++ b/marked/Rel-16/25_series/25992/raw.md @@ -0,0 +1,271 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------------------------------------------------|----| +| Contents..... | 3 | +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References ..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions ..... | 5 | +| 3.2 Symbols..... | 6 | +| 3.1 Abbreviations ..... | 6 | +| 4 Background and introduction..... | 6 | +| 5 RAN MBMS requirements ..... | 6 | +| 5.1 MBMS Notification Requirements ..... | 7 | +| 6 RAN MBMS functions ..... | 8 | +| 6.1 Functions list ..... | 8 | +| 6.2 Function descriptions ..... | 8 | +| 6.2.1 Admission control ..... | 8 | +| 6.2.2 Identification of the number of UEs with activated MBMS service(s) in a cell ..... | 8 | +| 6.2.3 Selection, assignment and establishment and release of radio bearers ..... | 9 | +| 6.2.4 Identification of MBMS parameters to UEs..... | 9 | +| 6.2.5 Alerting UEs that MBMS data is to be transmitted..... | 9 | +| 6.2.6 Power control..... | 9 | +| 6.2.7 Support of cell change and minimization of data loss..... | 9 | +| 6.2.8 Maintenance of MBMS context ..... | 9 | +| 6.2.9 Replication of MBMS data streams ..... | 9 | +| 6.2.10 Transfer of MBMS data..... | 9 | +| 6.3 Functional separation ..... | 10 | +| Annex A: Change History ..... | 11 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This document is part of the RAN WI "**Introduction of the Multimedia Broadcast Multicast Service (MBMS) in RAN**" and it is linked to 3GPP TS 22.146 "Multimedia Broadcast Multicast Service; Stage-1" [2] and the SA2 WI "Multimedia Broadcast/Multicast Service Architecture", the work of which is reflected in 3GPP TS 23.246 [3]. + +The purpose of the present document is to address the UTRAN and GERAN MBMS requirements in order to help the TSG RAN and TSG GERAN working groups address the changes needed to existing specifications and also identify new specifications, that are required for the introduction of the WI "**Introduction of the Multimedia Broadcast Multicast Service (MBMS) in RAN**". + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications ". +- [2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage-1". +- [3] 3GPP TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions given in [1] and the following apply.. + +**Broadcast mode:** The part of MBMS that supports broadcast services. + +**Counting:** This is the function that UTRAN performs when it wishes to identify the number of multicast subscribers (all joined subscribers, or just above a "threshold") in a particular cell, that wish to receive a multicast session for a particular service. + +**MBMS (Broadcast/Multicast) Session:** A continuous and time-bounded reception of a broadcast/multicast service by the UE. A single broadcast/multicast service can only have one broadcast/multicast session at any time. A broadcast/multicast service may consist of multiple successive broadcast/multicast sessions. + +**Multicast mode:** The part of MBMS that supports multicast services. + +**MBMS broadcast activation:** The process which enables the data reception from a specific broadcast mode MBMS on a UE. Thereby the user enables the reception locally on the UE. + +**MBMS multicast activation (Joining):** The explicit point-to-point UE to network signalling, which enables a UE to become a member of a multicast group and thus start receiving data from a specific MBMS multicast service (when data become available). + +**MBMS Notification:** The mechanism, which informs the UEs about the availability or coming availability of a specific MBMS RAB data in one given cell. + +**Service Announcements/Discovery:** The mechanisms should allow users to request or be informed about the range of MBMS services available Operators/service providers may consider several service discovery mechanisms. This could include standard mechanisms such as SMS, or depending on the capability of the terminal, applications that encourage user interrogation. Users who have not already subscribed to a MBMS service should also be able to discover MBMS services. + +NOTE: Some of the above definitions have been taken from TS 22.146 [2]. + +**Tracking:** This is a function that allows UTRAN to follow the mobility of multicast subscribers. Inherently it can be used as a means of counting multicast subscribers. + +**UE:** Unless otherwise stated, 'UE' is used to refer to both the UE and the MS. + +## 3.2 Symbols + +(void) + +## 3.1 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [1] and the following apply: + +| | | +|-------|----------------------------------------| +| MBMS | Multimedia Broadcast Multicast Service | +| p-t-p | Point-to-point | +| p-t-m | Point-to-multipoint | + +# --- 4 Background and introduction + +Following TSG RAN/SA#15, it was concluded that the service requirements [2] of MBMS are considered stable enough and the work on the architectural aspects have progressed to the extent that the work in the RAN groups could be initiated. + +# --- 5 RAN MBMS requirements + +Following the clarifications provided during the 3GPP MBMS workshop on stage 1 [2] and stage 2 [3], the following RAN requirements have been identified and are currently agreed within RAN WG2: + +1. MBMS data transfer shall be downlink only. +2. QoS attributes shall be the same for MBMS Multicast and Broadcast modes. +3. During MBMS data transmission it shall be possible to receive paging messages, which also should contain some additional information, such as CLI. +4. Simultaneous reception of MBMS and non-MBMS services shall depend upon UE capabilities. +5. Simultaneous reception of more than one MBMS services shall depend upon UE capabilities. +6. A notification procedure shall be used to indicate the start of MBMS data transmission. This procedure shall contain MBMS RB information. The MBMS notification requirements are listed in subclause 5.1. +7. A mechanism to enable the Network to move MBMS subscribers between cells is required. +8. MBMS UE multicast activation (Joining) shall be transparent to UTRAN. +9. A mechanism is required that enables the non-transmission of MBMS multicast mode in a cell which does not contain any MBMS UEs joined to the multicast group. +10. Reception of MBMS shall not be guaranteed at RAN level. MBMS does not support individual retransmissions at the radio link layer, nor does it support retransmissions based on feedback from individual subscribers at the + +radio level. This does not preclude the periodic repetitions of the MBMS content based on operator or content provider scheduling or retransmissions based on feedback at the application level. + +11. MBMS shall not prevent the capability for SRNS/SBSS relocation. + 12. A mechanism to provide UTRAN the received QoS per UE is not required as part of MBMS. + 13. UE controlled "service based" cell selection/reselection shall not be permitted. + 14. Handover and SGSN relocation shall not be affected by an active MBMS session. + 15. In the case of UTRAN only, guaranteed 'QoS' linked to a certain initial downlink power setting is not required; however, the purpose and possibility of some reporting mechanism could be identified to measure the delivered QoS. +- NOTE: The above requirement is not applicable in GERAN, as a p-t-m type connection will use a similar power control mechanism to a broadcast channel. +- 16 MBMS Multicast mode transmissions should use dedicated resources (p-t-p) or common resources (p-t-m). The selection of the connection type (p-t-p or p-t-m) is operator dependent, typically based on downlink radio resource environment such as radio resource efficiency. A "threshold" related to the number of users may be utilised, resulting in the need for a mechanism to identify the number of subscribers in a given "area". + - 17 MBMS solutions to be adopted should minimise the impact on the RAN physical layer and maximise reuse of existing physical layer and other RAN functionality. + - 18 MBMS charging should be transparent to the RAN. + - 19 MBMS should allow for low UE power consumption. + - 20 Header compression should be used. + - 21 MBMS should not prevent support for SGSN in pool. + - 22 Data loss during cell change should be minimal. + +## 5.1 MBMS Notification Requirements + +The following requirements for MBMS notification mechanism(s) have been identified and currently agreed: + +- 1 MBMS notification shall be transmitted within the MBMS service area. + +NOTE: If MBMS notification is transmitted in all cells of a corresponding MBMS service area or only in those cells where MBMS subscribers are actually located, is FFS. + +- 2 MBMS notification shall be sent so it could be received by all UEs with an activated MBMS service, regardless of their RRC state or the lack of an RRC connection. +- 3 MBMS notification should maximise the reuse of existing channels. +- 4 MBMS notification should allow terminals to minimise their power consumption, meaning that UEs with an activated MBMS service should not listen permanently, but at regular intervals to MBMS notification. +- 5 Reception of MBMS notification cannot be guaranteed. +- 6 UEs may receive MBMS notification and simultaneously monitor other occasions, e.g. UE dedicated paging and CBS messages. The avoidance of collisions cannot be guaranteed. If collisions occur, the UE dedicated Paging has higher priority (UE requirement). + +# 6 RAN MBMS functions + +## 6.1 Functions list + +The RAN functions identified for MBMS are: + +- 1 Functions relating to service establishment and radio resource management and control for MBMS services: + - 1.1 Admission control for MBMS services (see subclause 6.2.1). + - 1.2 Identification of the number of UEs (counting) with activated MBMS service(s) within a cell (see subclause 6.2.2). + - 1.3 Selection between the use of p-t-p and p-t-m radio bearers (see subclause 6.2.3). + - 1.4 Assignment of resources and the selection of parameters for MBMS radio bearers (see subclause 6.2.3). + - 1.5 Establishment and release of radio bearers for MBMS services (see subclause 6.2.3). + - 1.6 Identifying to UEs the physical, transport and logical channel parameters with which particular MBMS services are transmitted in each cell (see subclause 6.2.4). + - 1.7 Alerting UEs that MBMS data is to be transmitted (see subclause 6.2.5). + - 1.8 Power Control (see subclause 6.2.6). +- 2 Functions relating to mobility: + - 2.1 Support of cell change and minimisation of data loss (see subclause 6.2.7). + - 2.2 Maintenance of the MBMS context (see subclause 6.2.8). +- 3 Functions relating to transmission of MBMS data: + - 3.1 Replication of MBMS data streams to the cells of a multicast or broadcast area (see subclause 6.2.9). + - 3.2 Transfer of MBMS data (see subclause 6.2.10). + +## 6.2 Function descriptions + +This subclause contains a brief description of the RAN MBMS function identified in subclause 6.1. + +### 6.2.1 Admission control + +The RAN shall contain functionality that enables it to determine how to respond to requests to provide radio bearers for individual MBMS services (data streams) made by the SGSN. This admission procedure may take into account the capacity required, quality of service and priority of the requested service and the resources that are available for MBMS services within the cell. + +### 6.2.2 Identification of the number of UEs with activated MBMS service(s) in a cell + +Some architectural solutions for MBMS require that the RAN can identify the number of UEs (or at least whether a minimum number of UEs) that have activated particular MBMS services are present in a cell. This function may be used, in conjunction with discontinuous MBMS services, to identify whether the service should be established in the cell and whether p-t-p or p-t-m radio access bearers should be used. + +### 6.2.3 Selection, assignment and establishment and release of radio bearers + +The RAN shall assign radio resources to bearers for MBMS services within the cells of broadcast and multicast areas. RAN decides on the radio bearer configuration, it may be p-t-p or p-t-m. + +### 6.2.4 Identification of MBMS parameters to UEs + +The RAN shall provide mechanisms whereby the RAN indicates to the UE the physical, transport and logical channel parameters that are associated with radio bearers that carry specific MBMS data streams within specific cells. + +### 6.2.5 Alerting UEs that MBMS data is to be transmitted + +For discontinuous MBMS services radio bearers may be established only during those periods when there is data to be transferred. The RAN shall be required to alert the UE that the service is about to be re-established. + +### 6.2.6 Power control + +The power level shall be set for p-t-p and p-t-m bearers. + +**Editor's note:** It is an open issue whether feedback control for p-t-m radio bearers is practical. + +### 6.2.7 Support of cell change and minimization of data loss + +Whilst it is accepted that MBMS data loss may occur following cell reselection or handover, procedures shall be introduced to support resynchronisation after cell change and to reduce the potential for loss in these circumstances. + +### 6.2.8 Maintenance of MBMS context + +The RAN shall maintain internal records of the MBMS services that are active in each cell. These contexts shall be dependent upon the mobility of the UEs. + +### 6.2.9 Replication of MBMS data streams + +The content of an MBMS data stream may be transmitted in several cells by RAN. The RAN replicates the data to these cells. + +**Editor's note:** This is a working assumption and this is to be decided by TSG SA WG2. + +### 6.2.10 Transfer of MBMS data + +The RAN shall provide the layer 1 and layer 2 processes necessary for the preparation and transfer of MBMS data on the Uu and Um interfaces. This encompasses the functions of + +- header compression; +- segmentation/concatenation; +- multiplexing; and +- coding. + +Depending on the service characteristics and the reception capability of the UE, it has to be evaluated how several data streams are multiplexed. + +## 6.3 Functional separation + +**Editor's note:** This clause will introduce the functional separation between the different protocol layers. + + + +# Annex A: Change History + +| Date | Version | Comment | +|------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 19 Sept. 2002 | 1.0.0 | Changes are captured in attached document | +| 6 Nov. 2002 | 1.1.0 | Changes captures in the attached "cover" document. | +| 17 January 2003 | 1.2.0 | Changes are done based on discussions during the RAN2 RAN3 MBMS AdHoc (15-16 January 2003). | +| 20 January 2003 | 1.3.0 | RAN requirement #7 was re-worded based on comments on the RAN2 reflector. | +| 16 June 2003 | 2.0.1 | The version 2.0.0 identical to version 1.3.0 was presented in TSG RAN plenary meeting for approval. The TR was not approved so drafting work will continue in 3GPP WG2/3 based on version 2.0.0. The changes in version 2.0.1 compared to 2.0.0 are in History part where rapporteur information is changed. | +| 2 September 2003 | 2.0.2 | Agreed editorial changes (proposed in R2-031714) from RAN WG2 #37 included. Provide to TSG-RAN #21 for approval. | + +| Change history | | | | | | | | +|----------------|--------|-----------|----|-----|-----------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 09/2003 | RP-21 | RP-030426 | - | - | Created following RAN#21. Put under change control. | 2.0.2 | 6.0.0 | +| 06/2007 | RP-36 | - | - | - | Upgrade to the Release 7 - no technical change | 6.0.0 | 7.0.0 | +| 12/2008 | RP-42 | - | - | - | Upgrade to the Release 8 - no technical change | 7.0.0 | 8.0.0 | +| 12/2009 | RP-46 | - | - | - | Upgrade to the Release 9 - no technical change | 8.0.0 | 9.0.0 | +| 03/2011 | RP-51 | - | - | - | Upgrade to the Release 10 - no technical change | 9.0.0 | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | Upgrade to the Release 11 - no technical change | 10.0.0 | 11.0.0 | +| 09/2014 | RP-65 | - | - | - | Upgrade to the Release 12 - no technical change | 11.0.0 | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | Upgrade to the Release 13 - no technical change | 12.0.0 | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | Upgrade to the Release 14 - no technical change | 13.0.0 | 14.0.0 | +| 06/2018 | RP-80 | - | - | - | Upgrade to the Release 15 - no technical change | 14.0.0 | 15.0.0 | +| 07/2020 | RP-88e | - | - | - | Upgrade to the Release 16 - no technical change | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25993/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/25_series/25993/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62a4eb6e3525f18248a3726dcfcaeb8074f7393 --- /dev/null +++ b/marked/Rel-16/25_series/25993/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1045ba6bc9b2f925e7fb21a21e6cac5ab26a90fbb570e23c7c44e186870e4aca +size 80692 diff --git a/marked/Rel-16/25_series/25993/cf734b5645d3e02a8df25f67904cd2d3_img.jpg b/marked/Rel-16/25_series/25993/cf734b5645d3e02a8df25f67904cd2d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e340b7e20eb1933fbcf47047a31fd8ab9c05685 --- /dev/null +++ b/marked/Rel-16/25_series/25993/cf734b5645d3e02a8df25f67904cd2d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5d0a45acea211e3e0fc61f5ad2e736b9083f9c0562020908b416a1679323de1 +size 22756 diff --git a/marked/Rel-16/25_series/25993/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg b/marked/Rel-16/25_series/25993/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fba299a3004206cb77ad735dfe99170d957cf4b5 --- /dev/null +++ b/marked/Rel-16/25_series/25993/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d0f02a7daf1985694e24b6c69590b52c4ca245991cba7840e6702d3a66da7a4 +size 72104 diff --git a/marked/Rel-16/25_series/25993/raw.md b/marked/Rel-16/25_series/25993/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ada03309d9688b6a4e0d5b824893d0943c751519 --- /dev/null +++ b/marked/Rel-16/25_series/25993/raw.md @@ -0,0 +1,18721 @@ +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 25 | +| 1 Scope..... | 26 | +| 2 References..... | 26 | +| 3 Abbreviations and Terms..... | 27 | +| 3.1 Abbreviations..... | 27 | +| 3.2 Terms..... | 27 | +| 4 QoS Architecture and RAB attributes..... | 27 | +| 5 List of RABs and SRBs..... | 29 | +| 5.1 Interactive or background class Radio Access Bearers (PS domain)..... | 29 | +| 5.2 Streaming class Radio Access Bearers..... | 30 | +| 5.2.1 CS domain..... | 30 | +| 5.2.2 PS domain..... | 30 | +| 5.3 Conversational class Radio Access Bearers..... | 31 | +| 5.3.1 CS domain..... | 31 | +| 5.3.2 PS domain..... | 32 | +| 5.4 Signalling Radio Bearers (Control Plane)..... | 32 | +| 6 Combinations of RABs..... | 33 | +| 7 Examples of Radio Bearers and Signalling Radio Bearers for FDD..... | 33 | +| 7.1 Combinations on DPCH..... | 33 | +| 7.1.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH..... | 33 | +| 7.1.2 Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 33 | +| 7.1.2a Stand-alone UL:6.8 DL:6.8 kbps SRBs for DCCH..... | 34 | +| 7.1.3 Stand-alone UL:13.6 DL:13.6 kbps SRBs for DCCH..... | 35 | +| 7.1.3a Stand-alone UL:27.2 DL:27.2 kbps SRBs for DCCH..... | 35 | +| 7.1.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 37 | +| 7.1.5 Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 37 | +| 7.1.5a Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 37 | +| 7.1.6 Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 38 | +| 7.1.7 Conversational / speech / UL:(10.2, 6.7, 5.9, 4.75) DL:(10.2, 6.7, 5.9, 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 38 | +| 7.1.8 Conversational / speech / UL:7.95 DL:7.95 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 38 | +| 7.1.9 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 38 | +| 7.1.10 Conversational / speech / UL:(7.4, 6.7, 5.9, 4.75) DL:(7.4, 6.7, 5.9, 4.75) kbps / CS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 38 | +| 7.1.11 Conversational / speech / UL:6.7 DL:6.7 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 39 | +| 7.1.12 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 39 | +| 7.1.12a Conversational / speech / UL:(5.9, 4.75) DL:(5.9, 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 39 | +| 7.1.12b Conversational / speech / UL:5.9 DL:5.9 (SF=128) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 41 | +| 7.1.13 Conversational / speech / UL:5.15 DL:5.15 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH..... | 41 | +| 7.1.14 Conversational / speech / UL:4.75 DL:4.75 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH..... | 41 | +| 7.1.15 Conversational / unknown / UL:28.8/DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 41 | +| 7.1.16 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 41 | +| 7.1.16a Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 42 | +| 7.1.16b Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH+ DL:0.15 kbps SRB#5 for DCCH..... | 43 | +| 7.1.17 Conversational / unknown / UL:32 DL:32 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 44 | +| 7.1.18 Streaming / unknown / UL:14.4 DL:14.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 45 | +| 7.1.19 Streaming / unknown / UL:28.8 DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 45 | +| 7.1.20 Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 45 | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.1.21 | Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................45 | +| 7.1.22 | Streaming / unknown / UL:64 DL:0 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................46 | +| 7.1.23 | Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................48 | +| 7.1.24 | Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH....................48 | +| 7.1.25 | Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................49 | +| 7.1.26 | Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................49 | +| 7.1.27 | Interactive or background / UL:32 DL:32 kbps / PS RAB (20 ms TTI)+ UL:3.4 DL:3.4 kbps SRBs for DCCH..................................................................................................................................................................50 | +| 7.1.28 | Interactive or background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................51 | +| 7.1.29 | Interactive or background / UL:32 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..............52 | +| 7.1.30 | Interactive or background / UL:64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..............53 | +| 7.1.31 | Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH............53 | +| 7.1.32 | Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..........53 | +| 7.1.33 | Interactive or background / UL:64 DL:144 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH............54 | +| 7.1.34 | Interactive or background / UL:144 DL:144 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH..........54 | +| 7.1.35 | Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH............54 | +| 7.1.36 | Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH............56 | +| 7.1.37 | Interactive or background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..........57 | +| 7.1.38 | Interactive or background / UL:384 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..........57 | +| 7.1.39 | Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..........57 | +| 7.1.40 | Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................................................................................................................................................................58 | +| 7.1.41 | Interactive or background / UL:384 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................................................................................................................................................................58 | +| 7.1.42 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................................................................59 | +| 7.1.43 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................................................................59 | +| 7.1.44 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................................................................59 | +| 7.1.45 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.....................................................................60 | +| 7.1.45a | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB (20ms TTI)+ UL:3.4 DL:3.4 kbps SRBs for DCCH...................................................60 | +| 7.1.46 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.......................................................................................................................................62 | +| 7.1.47 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................62 | +| 7.1.47a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................62 | +| 7.1.48 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................63 | +| 7.1.48a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..................64 | +| 7.1.49 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) kbps DL: (12.2 7.95 5.9 4.75) / CS RAB + Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................65 | +| 7.1.49a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps DL: (12.2 7.4 5.9 4.75) / CS RAB + Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................65 | +| 7.1.50 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................66 | +| 7.1.50a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................67 | +| 7.1.51 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................68 | +| 7.1.51a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................68 | +| 7.1.52 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH............69 | +| 7.1.52a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH............70 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.1.53 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH..... | 70 | +| 7.1.54 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH..... | 71 | +| 7.1.55 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 71 | +| 7.1.56 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 72 | +| 7.1.57 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 73 | +| 7.1.58 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 74 | +| 7.1.59 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 74 | +| 7.1.60 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 74 | +| 7.1.61 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 75 | +| 7.1.62 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 76 | +| 7.1.63 | Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 76 | +| 7.1.63a | Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 76 | +| 7.1.64 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 77 | +| 7.1.65 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 77 | +| 7.1.66 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 78 | +| 7.1.67 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 78 | +| 7.1.68 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 78 | +| 7.1.69 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 79 | +| 7.1.70 | Interactive or background / UL:64 DL:128 kbps / PS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 79 | +| 7.1.71 | Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 80 | +| 7.1.72 | Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 81 | +| 7.1.73 | Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 81 | +| 7.1.73a | Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative..... | 82 | +| 7.1.74 | Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 83 | +| 7.1.75 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 83 | +| 7.1.76 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 85 | +| 7.1.77 | Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 87 | +| 7.1.78 | Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 89 | +| 7.1.79 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 92 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.1.79a | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (L1 multiplexing) (FDD)..... | 93 | +| 7.1.80 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 95 | +| 7.1.81 | Streaming / unknown / UL:8 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 96 | +| 7.1.82 | Streaming / unknown / UL:8 DL:32 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 98 | +| 7.1.83 | Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 100 | +| 7.1.84 | Interactive or background / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 102 | +| 7.1.85 | Interactive or background / UL:64 DL:8 kbps / PS RAB + Interactive or Background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 103 | +| 7.1.86 | Interactive or Background / UL:64 DL:128 kbps / PS RAB + Interactive or Background / UL:64 DL:128 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 104 | +| 7.1.87 | Interactive or Background / UL:64 DL:384 kbps / PS RAB + Interactive or Background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 105 | +| 7.1.88 | Interactive or background / UL:128 DL:128 kbps / PS RAB + Interactive or Background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 106 | +| 7.1.89 | Interactive or background / UL:128 DL:32 kbps / PS RAB + Interactive or Background / UL:128 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 108 | +| 7.1.90 | Streaming / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 109 | +| 7.1.91 | Streaming / unknown / UL:16 DL:32 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 109 | +| 7.1.92 | Interactive or background / UL:16 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 109 | +| 7.1.93 | Interactive or background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 110 | +| 7.1.94 | Interactive or background / UL:16 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 110 | +| 7.1.95 | Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 110 | +| 7.1.96 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 112 | +| 7.1.97 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 114 | +| 7.1.98 | Interactive or background / UL:32 DL:64 kbps / PS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (L1 multiplexing) (FDD)..... | 114 | +| 7.1.99 | Interactive or background / UL:128 DL: 64k / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH..... | 115 | +| 7.1.100 | Interactive or background / UL:384 DL: 64k / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH..... | 116 | +| 7.1.101 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 117 | +| 7.1.102 | Interactive or background / UL:384 DL: 128kbps / PS RAB + UL:3.4 DL:3.4 kb/s Signalling Radio Bearers for DCCH..... | 118 | +| 7.1.103 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 64kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH..... | 119 | +| 7.1.104 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 128kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH..... | 120 | +| 7.1.105 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 384kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH..... | 121 | +| 7.1.106 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 122 | +| 7.1.107 | Conversational / speech / UL:(15.85 12.65 8.85 6.6) DL:(15.85 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 123 | +| 7.1.108 | Conversational / speech / UL:(23.85 12.65 8.85 6.6) DL:(23.85 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 126 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.1.109 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 128 | +| 7.1.110 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 130 | +| 7.1.111 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 132 | +| 7.1.112 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 135 | +| 7.1.113 | Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 137 | +| 7.1.113a | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:64 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 138 | +| 7.1.114 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 139 | +| 7.1.115 | Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH..... | 141 | +| 7.1.116 | Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 143 | +| 7.1.117 | Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 144 | +| 7.1.118 | Conversational / speech / UL:38.8 DL:38.8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-6 onwards]..... | 144 | +| 7.1.119 | Conversational / speech / UL:16.8 DL:16.8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-6 onwards]..... | 148 | +| 7.1.120 | Conversational / speech / UL: 40 DL: 40 kbps / PS RAB + Interactive or Background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH [Rel-5 only]..... | 153 | +| 7.1.121 | Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:27.2 DL:27.2 kbps SRBs for DCCH... | 156 | +| 7.1.122 | Conversational / speech / UL:39.6 DL:39.6 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-5]..... | 157 | +| 7.1.123 | Conversational / speech / UL:17.6 DL:17.6 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-5]..... | 160 | +| 7.1.124 | Conversational / speech / UL: 39.2 DL: 39.2 kbps / PS RAB + Interactive or Background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 165 | +| 7.1.125 | Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 168 | +| 7.1.126 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative..... | 170 | +| 7.1.127 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 171 | +| 7.1.128 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 173 | +| 7.1.129 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 176 | + +| | | | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.1.130 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 179 | +| 7.1.131 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH..... | 181 | +| 7.1.132 | Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH..... | 183 | +| 7.1.132a | Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH..... | 184 | +| 7.1.133 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:13.6 DL:13.6 kbps SRBs for DCCH. .... | 185 | +| 7.1.134 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH..... | 186 | +| 7.1.135 | Void..... | 187 | +| 7.1.136 | Void..... | 187 | +| 7.1.137 | Interactive or Background / UL:32 DL:64 kbps / PS RAB + Interactive or Background / UL:32 DL:64 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 187 | +| 7.1.138 | Interactive or background / UL:128 DL:384 kbps / PS RAB + Interactive or Background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 188 | +| 7.1.139 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 189 | +| 7.1.140 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 190 | +| 7.1.141 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 193 | +| 7.1.142 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB (20ms TTI) + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 196 | +| 7.1.143 | Conversational / speech / UL:6.6 DL:6.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 198 | +| 7.1.144 | Interactive or background / UL:64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 200 | +| 7.1.145 | Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL:( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 203 | +| 7.1.145.1 | Uplink..... | 203 | +| 7.1.145.1.1 | Transport channel parameters..... | 203 | +| 7.1.145.1.1.2 | Transport channel parameters for UL:3.4 kbps SRBs for DCCH..... | 203 | +| 7.1.145.1.2 | Physical channel parameters..... | 204 | +| 7.1.145.2 | Downlink..... | 204 | +| 7.1.145.2.1 | Transport channel parameters..... | 204 | +| 7.1.145.2.2 | Physical channel parameters..... | 205 | +| 7.1.146 | Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 206 | +| 7.1.146.1 | Uplink..... | 206 | +| 7.1.146.1.1 | Transport channel parameters..... | 206 | +| 7.1.146.1.2 | Physical channel parameters..... | 207 | +| 7.1.146.2 | Downlink..... | 207 | +| 7.1.146.2.1 | Transport channel parameters..... | 207 | +| 7.1.146.2.2 | Physical channel parameters..... | 208 | +| 7.1.147 | Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 209 | +| 7.1.147.1 | Uplink..... | 209 | +| 7.1.147.1.1 | Transport channel parameters..... | 209 | +| 7.1.147.1.2 | Physical channel parameters..... | 210 | +| 7.1.147.2 | Downlink..... | 210 | +| 7.1.147.2.1 | Transport channel parameters..... | 210 | +| 7.1.147.2.2 | Physical channel parameters..... | 211 | +| 7.1.148 | Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 212 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.1.148.1 | Uplink..... | 212 | +| 7.1.148.1.1 | Transport channel parameters..... | 212 | +| 7.1.148.1.2 | Physical channel parameters..... | 213 | +| 7.1.148.2 | Downlink..... | 214 | +| 7.1.148.2.1 | Transport channel parameters..... | 214 | +| 7.1.149 | Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL:( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 215 | +| 7.1.149.1 | Uplink..... | 215 | +| 7.1.149.1.1 | Transport channel parameters..... | 215 | +| 7.1.149.2 | Downlink..... | 215 | +| 7.1.149.2.1 | Transport channel parameters..... | 215 | +| 7.1.149.2.2 | Physical channel parameters..... | 216 | +| 7.1.150 | Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 217 | +| 7.1.150.1 | Uplink..... | 217 | +| 7.1.150.1.1 | Transport channel parameters..... | 217 | +| 7.1.150.1.2 | Physical channel parameters..... | 217 | +| 7.1.150.2 | Downlink..... | 217 | +| 7.1.150.2.1 | Transport channel parameters..... | 217 | +| 7.1.150.2.2 | Physical channel parameters..... | 218 | +| 7.1.151 | Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 218 | +| 7.1.151.1 | Uplink..... | 218 | +| 7.1.151.1.1 | Transport channel parameters..... | 218 | +| 7.1.151.1.2 | Physical channel parameters..... | 218 | +| 7.1.151.2 | Downlink..... | 219 | +| 7.1.151.2.1 | Transport channel parameters..... | 219 | +| 7.1.151.2.2 | Physical channel parameters..... | 219 | +| 7.1.152 | Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 220 | +| 7.1.152.1 | Uplink..... | 220 | +| 7.1.152.1.1 | Transport channel parameters..... | 220 | +| 7.1.152.1.2 | Physical channel parameters..... | 220 | +| 7.1.152.2 | Downlink..... | 220 | +| 7.1.152.2.1 | Transport channel parameters..... | 220 | +| 7.1.152.2.2 | Physical channel parameters..... | 221 | +| 7.1.153 | Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL:( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 221 | +| 7.1.153.1 | Uplink..... | 221 | +| 7.1.153.1.1 | Transport channel parameters..... | 221 | +| 7.1.153.1.2 | Physical channel parameters..... | 222 | +| 7.1.153.2 | Downlink..... | 222 | +| 7.1.153.2.1 | Transport channel parameters..... | 222 | +| 7.1.153.2.2 | Physical channel parameters..... | 222 | +| 7.1.154 | Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 223 | +| 7.1.154.1 | Uplink..... | 223 | +| 7.1.154.1.1 | Transport channel parameters..... | 223 | +| 7.1.154.1.2 | Physical channel parameters..... | 223 | +| 7.1.154.2 | Downlink..... | 223 | +| 7.1.154.2.1 | Transport channel parameters..... | 223 | +| 7.1.154.2.2 | Physical channel parameters..... | 224 | +| 7.1.155 | Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 224 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.1.155.1 | Uplink..... | 224 | +| 7.1.155.1.1 | Transport channel parameters..... | 224 | +| 7.1.155.1.2 | Physical channel parameters..... | 225 | +| 7.1.155.2 | Downlink..... | 225 | +| 7.1.155.2.1 | Transport channel parameters..... | 225 | +| 7.1.155.2.2 | Physical channel parameters..... | 226 | +| 7.1.156 | Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:
( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or
background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 227 | +| 7.1.156.1 | Uplink..... | 227 | +| 7.1.156.1.1 | Transport channel parameters..... | 227 | +| 7.1.156.1.2 | Physical channel parameters..... | 227 | +| 7.1.156.2 | Downlink..... | 227 | +| 7.1.156.2.1 | Transport channel parameters..... | 227 | +| 7.1.156.2.2 | Physical channel parameters..... | 228 | +| 7.2 | Combinations on S-CCPCH..... | 228 | +| 7.2.1 | Stand-alone signalling RB for PCCH..... | 228 | +| 7.2.2 | Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 228 | +| 7.2.3 | Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for
CCCH + SRB for DCCH + SRB for BCCH..... | 228 | +| 7.2.4 | Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB
for BCCH..... | 229 | +| 7.2.5 | 16 kbps RB for CTCH + SRB for CCCH + SRB for BCCH..... | 229 | +| 7.2.6 | RB for CTCH + Interactive/Background 32 kbps PS RAB + SRB for PCCH + SRB for CCCH +
SRB for DCCH + SRB for BCCH..... | 229 | +| 7.2.7 | Interactive/Background 16 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 231 | +| 7.2.8 | 8 kbps RB for CTCH + SRB for CCCH + SRB for BCCH..... | 232 | +| 7.2.9 | Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB
for BCCH..... | 233 | +| 7.2.10 | 258.4 kbps RB for MTCH with 40 ms TTI..... | 235 | +| 7.2.11 | 129.2 kbps RB for MTCH with 40 ms TTI..... | 237 | +| 7.2.12 | 129.2 kbps RB for MTCH with 80 ms TTI..... | 238 | +| 7.2.13 | 64.6 kbps RB for MTCH with 80 ms TTI..... | 240 | +| 7.2.14 | 64.8kbps RB for MTCH with 80 ms TTI (alternative config)..... | 241 | +| 7.2.15 | 129.6 kbps RB for MTCH with 80 ms TTI (alternative config)..... | 241 | +| 7.2.16 | 259.2 kbps RB for MTCH with 40 ms TTI (alternative config)..... | 241 | +| 7.2.17 | 7.6 kbps signalling RB for MCCH..... | 241 | +| 7.2.18 | 6.4 kbps SRB for MCCH..... | 242 | +| 7.3 | Combinations on PRACH..... | 242 | +| 7.3.1 | Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH..... | 242 | +| 7.3.2 | Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRB for
CCCH + SRB for DCCH..... | 242 | +| 7.3.3 | Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH..... | 243 | +| 7.3.4 | Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRB for
CCCH + SRB for DCCH..... | 243 | +| 7.4 | Radio Bearer and Radio Bearer Combinations on DPCH and HS-PDSCH..... | 243 | +| 7.4.1 | RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB
maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 243 | +| 7.4.1b | Void..... | 244 | +| 7.4.2 | RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB
maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 244 | +| 7.4.3 | RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background /
UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH..... | 244 | +| 7.4.3a | RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background /
UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH..... | 245 | +| 7.4.4 | RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background /
UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH..... | 246 | + +| | | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.4.4a | RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 247 | +| 7.4.5 | RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 247 | +| 7.4.5a | RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 248 | +| 7.4.6 | Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 249 | +| 7.4.7 | RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 249 | +| 7.4.7a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 250 | +| 7.4.8 | RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 251 | +| 7.4.8a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 252 | +| 7.4.9 | Void..... | 253 | +| 7.4.10 | RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 253 | +| 7.4.11 | Void..... | 254 | +| 7.4.12 | RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 254 | +| 7.4.14 | RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 256 | +| 7.4.15 | RB for Streaming / unknown / UL:64 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 258 | +| 7.4.16 | RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 260 | +| 7.4.16a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 262 | +| 7.4.17 | RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:128 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 263 | +| 7.4.17a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:128 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 266 | +| 7.4.18 | RB for Streaming / unknown / UL:64 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 266 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.4.19 | RB for Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 268 | +| 7.4.20 | RB for Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 269 | +| 7.4.21 | RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 270 | +| 7.4.22 | Conversational / unknown / UL:38.8 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 271 | +| 7.4.23 | Conversational / unknown / UL:16.8 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 273 | +| 7.4.24 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or Background / UL:384 DL:[Bit rate depending on the UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 275 | +| 7.4.25 | RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or Background / UL:64 DL:[Bit rate depending on the UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 275 | +| 7.4.26 | RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:6.8 DL:6.8 kbps SRBs for DCCH..... | 276 | +| 7.4.27 | RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:6.8 DL:6.8 kbps SRBs for DCCH..... | 277 | +| 7.4.28 | RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or Background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + RB for Interactive or Background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH..... | 278 | +| 7.4.29 | RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 280 | +| 7.4.30 | RB for Interactive or background / UL:16 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 281 | +| 7.4.31 | RB for Streaming MBMS PTP / unknown / UL:16 DL:[max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 281 | +| 7.4.32 | RB for Streaming MBMS PTP / unknown / UL:16 DL:[max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on UE category & RAB maximum bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on UE category & RAB maximum bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 282 | +| 7.4.33 | RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 283 | +| 7.4.33.1 | Uplink..... | 283 | +| 7.4.33.2 | Downlink..... | 283 | +| 7.4.33.2.1 | Transport channel parameters..... | 283 | +| 7.4.33.2.2 | Physical channel parameters..... | 283 | +| 7.4.34 | RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 284 | +| 7.4.34.1 | Uplink..... | 284 | +| 7.4.34.2 | Downlink..... | 284 | +| 7.4.34.2.1 | Transport channel parameters..... | 284 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.4.34.2.2 | Physical channel parameters..... | 284 | +| 7.4.35 | RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 284 | +| 7.4.35.1 | Uplink..... | 284 | +| 7.4.35.1.1 | Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB..... | 284 | +| 7.4.35.1.2 | Transport channel parameters for UL:3.4 kbps SRBs for DCCH..... | 284 | +| 7.4.35.1.3 | TFCS..... | 285 | +| 7.4.35.1.4 | Physical channel parameters..... | 285 | +| 7.4.35.2 | Downlink..... | 285 | +| 7.4.35.2.1 | Transport channel parameters..... | 285 | +| 7.4.35.2.2 | Physical channel parameters..... | 285 | +| 7.4.36 | RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 286 | +| 7.4.36.1 | Uplink..... | 286 | +| 7.4.36.2 | Downlink..... | 286 | +| 7.4.36.2.1 | Transport channel parameters..... | 286 | +| 7.4.36.2.2 | Physical channel parameters..... | 286 | +| 7.4.37 | RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 286 | +| 7.4.37.1 | Uplink..... | 286 | +| 7.4.37.1.1 | Transport channel parameters..... | 286 | +| 7.4.37.1.1.4 | TFCS..... | 287 | +| 7.4.37.1.2 | Physical channel parameters..... | 287 | +| 7.4.37.2 | Downlink..... | 287 | +| 7.4.37.2.1 | Transport channel parameters..... | 287 | +| 7.4.37.2.2 | Physical channel parameters..... | 287 | +| 7.4.38 | RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 288 | +| 7.4.38.1 | Uplink..... | 288 | +| 7.4.38.1.1 | Transport channel parameters..... | 288 | +| 7.4.38.1.2 | Physical channel parameters..... | 288 | +| 7.4.38.2 | Downlink..... | 288 | +| 7.4.38.2.1 | Transport channel parameters..... | 288 | +| 7.4.38.2.2 | Physical channel parameters..... | 289 | +| 7.4.39 | RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 289 | +| 7.4.39.1 | Uplink..... | 289 | +| 7.4.39.1.1 | Transport channel parameters..... | 289 | +| 7.4.39.1.2 | Physical channel parameters..... | 290 | +| 7.4.39.2 | Downlink..... | 290 | +| 7.4.39.2.1 | Transport channel parameters..... | 290 | +| 7.4.39.2.2 | Physical channel parameters..... | 290 | +| 7.4.39.2.2.1 | Physical channel parameters on DPCH..... | 290 | +| 7.4.40 | RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 290 | +| 7.4.40.1 | Uplink..... | 290 | +| 7.4.40.1.1 | Transport channel parameters..... | 290 | +| 7.4.40.1.2 | Physical channel parameters..... | 291 | +| 7.4.40.2 | Downlink..... | 291 | +| 7.4.40.2.1 | Transport channel parameters..... | 291 | +| 7.4.40.2.2 | Physical channel parameters..... | 291 | + +| | | | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.5 | Radio Bearer and Radio Bearer Combinations on E-DPDCH and HS-PDSCH..... | 292 | +| 7.5.1 | RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 292 | +| 7.5.2 | RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL on DCH..... | 292 | +| 7.5.3 | RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 293 | +| 7.5.4 | RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 294 | +| 7.5.5 | Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH..... | 295 | +| 7.5.6 | Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 295 | +| 7.5.7 | Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + DL:0.15 kbps SRB#5 for DCCH..... | 296 | +| 7.5.8 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 297 | +| 7.5.9 | Conversational / speech / UL:(5.9, 4.75) DL:( 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 298 | +| 7.5.10 | UL: [max bit rate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH..... | 299 | +| 7.5.11 | RB for interactive or background / UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL: [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH..... | 300 | +| 7.5.12 | RB for Conversational / unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH..... | 301 | +| 7.5.13 | RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH..... | 302 | +| 7.5.14 | RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 303 | +| 7.5.14a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 304 | + +7.5.15 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + DL:0.15 kbps SRB#5 for DCCH...........................305 + +7.5.16 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..................................................................................306 + +7.5.17 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................................................................................................306 + +7.5.17a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH................................................................................................307 + +7.5.18 RB for Conversational / Speech UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH SRBs for DCCH.......................................................................308 + +7.5.19 RB for Conversational / Speech UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH...........................309 + +7.5.20 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..................................................................................................................310 + +7.5.21 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH.........................................311 + +7.5.22 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH...........312 + +7.5.23 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH...........313 + +| | | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.5.23a | RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 314 | +| 7.5.24 | RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 315 | +| 7.5.25 | RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 316 | +| 7.5.26 | UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + DCH 3.4kbps..... | 316 | +| 7.5.27 | Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:13.6 DL:13.6kbps SRBs for DCCH on DCH..... | 318 | +| 7.5.28 | Conversational / speech / UL: 12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 319 | +| 7.5.29 | Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 321 | +| 7.5.30 | Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 323 | +| 7.5.30a | Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 324 | +| 7.5.31 | Conversational / speech / UL:(12.65, 8.85, 6.6) kbps DL: (12.65, 8.85, 6.6) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 326 | +| 7.5.32 | Conversational / speech / UL:(23.85 12.65 8.85 6.6) DL:(23.85 12.65 8.85 6.6) kbps / CS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 327 | +| 7.5.33 | Conversational / speech / UL:12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 329 | +| 7.5.34 | Conversational / speech / UL:12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 330 | +| 7.5.35 | Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 331 | +| 7.5.35a | Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 332 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.5.36 | Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 333 | +| 7.5.36a | Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 334 | +| 7.5.37 | Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 335 | +| 7.5.38 | Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 336 | +| 7.5.39 | Conversational / speech / UL:( 12.65 8.85 6.6) kbps DL: (12.65 8.85 6.6) kbps / CS RAB on E-DCH and HS-DSCH + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 338 | +| 7.5.40 | Conversational / speech / UL:( 12.65 8.85 6.6) kbps DL: (12.65 8.85 6.6) kbps / CS RAB on E-DCH and HS-DSCH + Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH..... | 339 | +| 7.5.41 | RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 340 | +| 7.5.41.1 | Uplink..... | 340 | +| 7.5.41.1.1 | Transport channel parameters..... | 340 | +| 7.5.41.1.2 | Physical channel parameters..... | 340 | +| 7.5.41.2 | Downlink..... | 340 | +| 7.5.42 | RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 341 | +| 7.5.42.1 | Uplink..... | 341 | +| 7.5.42.1.1 | Transport channel parameters..... | 341 | +| 7.5.42.1.2 | Physical channel parameters..... | 341 | +| 7.5.42.2 | Downlink..... | 341 | +| 7.5.43 | RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 341 | +| 7.5.43.1 | Uplink..... | 341 | +| 7.5.43.1.1 | Transport channel parameters..... | 341 | +| 7.5.43.1.2 | Physical channel parameters..... | 342 | +| 7.5.43.2 | Downlink..... | 342 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.5.44 | RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH..... | 342 | +| 7.5.44.1 | Uplink..... | 342 | +| 7.5.44.1.1 | Transport channel parameters..... | 342 | +| 7.5.44.1.2 | Physical channel parameters..... | 342 | +| 7.5.44.2 | Downlink..... | 342 | +| 7.6 | Void..... | 343 | +| 8 | Examples of Radio Bearers and Signalling Radio Bearers for 3.84 Mcps TDD..... | 343 | +| 8.1 | Combinations on DPCH..... | 343 | +| 8.1.1 | Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH..... | 343 | +| 8.1.2 | Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 343 | +| 8.1.3 | Stand-aloneUL:13.6 DL:13.6 kbps SRBs for DCCH..... | 343 | +| 8.1.4 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH... | 343 | +| 8.1.5 | Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB + UL:3.4 kbps SRBs for DCCH..... | 343 | +| 8.1.6 | Conversational / speech / UL:7.95 DL:7.95 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 343 | +| 8.1.7 | Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 344 | +| 8.1.8 | Conversational / speech / UL:6.7 DL: 6.7 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 344 | +| 8.1.9 | Conversational / speech / UL:5.9 DL:5.9 kbps / CS rab + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 344 | +| 8.1.10 | Conversational / speech / UL:5.15 DL:5.15 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH.... | 344 | +| 8.1.11 | Conversational / speech / UL:4.75 DL:4.75 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH.... | 344 | +| 8.1.12 | Conversational / unknown / UL:28.8 DL:28.8kbps / CS RAB + UL:3.4 DL:3.4kbps SRBs for DCCH. | 344 | +| 8.1.13 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 344 | +| 8.1.14 | Conversational / unknown / UL:32 DL: 32 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.15 | Streaming / unknown / UL:14.4 DL:14.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.16 | Streaming / unknown / UL:28.8 DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.17 | Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.18 | Streaming / unknown / UL:0 DL: 64 kbps / CS or PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH.... | 345 | +| 8.1.19 | Streaming / unknown / UL: 64 DL:0 kbps / CS or PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.20 | Interactive or background / UL: 32 DL:8 kbps / PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH..... | 345 | +| 8.1.21 | Interactive or background / UL: 64 DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 346 | +| 8.1.22 | Interactive or background / UL: 32 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 346 | +| 8.1.23 | Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH.... | 346 | +| 8.1.24 | Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 346 | +| 8.1.25 | Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.. | 346 | +| 8.1.26 | Interactive or background / UL:64 DL:144 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 346 | +| 8.1.27 | Interactive or background / UL: 144 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 346 | +| 8.1.28 | Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 347 | +| 8.1.29 | Interactive or background / UL: 64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 347 | +| 8.1.30 | Interactive or background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.. | 347 | +| 8.1.31 | Interactive or background / UL:384 DL:384 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH.... | 347 | +| 8.1.32 | Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.. | 347 | +| 8.1.33 | Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 347 | +| 8.1.34 | Interactive or background / UL: 384 DL:2048 kbps / PS RAB+UL:3.4 DL:3.4 kbps SRBs for DCCH. | 348 | +| 8.1.35 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 348 | +| 8.1.36 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 348 | +| 8.1.37 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 348 | +| 8.1.38 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 348 | +| 8.1.39 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 348 | +| 8.1.40 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | +| 8.1.41 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | + +| | | | +|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.1.42 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | +| 8.1.43 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS or PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | +| 8.1.44 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | +| 8.1.45 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 349 | +| 8.1.46 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 350 | +| 8.1.47 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 350 | +| 8.1.48 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 350 | +| 8.1.49 | Interactive or background / UL:64 DL:128 kbps / PS RAB + streaming / unknown / UL:0 DL:64 kbps / CS or PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 350 | +| 8.1.50 | Conversational / Speech UL:(12.2-7.95-5.9-4.75) & DL:(12.2-7.95-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH..... | 350 | +| 8.1.51 | Conversational / Speech UL:(10.2-6.7-5.9-4.75) & DL:(10.2-7.95-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH..... | 350 | +| 8.1.52 | Conversational / Speech UL:(7.4-6.7-5.9-4.75) & DL:(7.4-6.7-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH..... | 351 | +| 8.1.53 | Interactive or Background UL:8 & DL:8kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH..... | 351 | +| 8.1.54 | Interactive or Background UL:16 & DL:16kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH..... | 351 | +| 8.1.55 | Interactive or Background UL:32 & DL:32kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH..... | 351 | +| 8.1.56 | Interactive or Background UL:32 & DL:32kbps PS RAB (20msTTI) + UL:3.4 & DL:3.4 SRBs for DCCH..... | 351 | +| 8.1.57 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 351 | +| 8.1.58 | Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:8 & DL:8kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH..... | 352 | +| 8.1.59 | Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:32 & DL:32kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH..... | 352 | +| 8.1.60 | Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH..... | 352 | +| 8.1.61 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:0 & DL:0kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH..... | 352 | +| 8.1.62 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:8 & DL:8kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH..... | 352 | +| 8.1.63 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:16 & DL:16kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH.... | 352 | +| 8.1.64 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:32 & DL:32kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH.... | 353 | +| 8.1.65 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH.... | 353 | +| 8.1.66 | Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:64 & DL:128kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH. . | 353 | +| 8.1.67 | Conversational / speech / UL:(12.2 7.95 5.9 4.75) kbps DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 353 | +| 8.1.68 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 353 | +| 8.1.69 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 354 | +| 8.1.70 | Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 354 | +| 8.1.71 | Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 354 | +| 8.1.72 | Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 354 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.1.72a | Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative..... | 354 | +| 8.1.73 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 355 | +| 8.1.74 | Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH (Multiframe)..... | 356 | +| 8.1.75 | Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 356 | +| 8.1.76 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 357 | +| 8.1.77 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 359 | +| 8.1.78 | Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 361 | +| 8.1.79 | Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 363 | +| 8.1.80 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 365 | +| 8.1.81 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 367 | +| 8.1.82 | Streaming / unknown / UL:8 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 368 | +| 8.1.83 | Streaming / unknown / UL:8 DL:32 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 370 | +| 8.1.84 | Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 372 | +| 8.1.85 | Interactive or background / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 374 | +| 8.1.86 | Interactive or background / UL:64 DL:8 kbps / PS RAB + Interactive or Background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 376 | +| 8.1.87 | Interactive or Background / UL:64 DL:128 kbps / PS RAB + Interactive or Background / UL:64 DL:128 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 376 | +| 8.1.88 | Interactive or Background / UL:64 DL:384 kbps / PS RAB + Interactive or Background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 377 | +| 8.1.89 | Interactive or background / UL:128 DL:128 kbps / PS RAB + Interactive or Background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 378 | +| 8.1.90 | Interactive or background / UL:128 DL:32 kbps / PS RAB + Interactive or Background / UL:128 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 380 | +| 8.1.91 | Streaming / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 381 | +| 8.1.92 | Streaming / unknown / UL:16 DL:32 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 381 | +| 8.1.93 | Interactive or background / UL:16 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 381 | +| 8.1.94 | Interactive or background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 382 | +| 8.1.95 | Interactive or background / UL:16 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 382 | +| 8.1.96 | Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 382 | +| 8.1.97 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 384 | +| 8.2 | Combinations on PDSCH, SCCH, PUSCH and PRACH..... | 387 | +| 8.2.1 | Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH..... | 387 | +| 8.2.2 | Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH..... | 387 | +| 8.2.3 | Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH..... | 387 | +| 8.2.4 | Interactive or background / UL: 384 DL: 2048 kbps / PS RAB + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH..... | 388 | + +| | | | +|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.3 | Combinations on PDSCH, SCCPCH, DPCH, PUSCH and PRACH..... | 388 | +| 8.3.1 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
+ interactive or background / UL:64 DL:256 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and
SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 388 | +| 8.3.2 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
+ Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and
SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 388 | +| 8.3.3 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
+ Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and
SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 388 | +| 8.4 | Combinations on SCCPCH..... | 389 | +| 8.4.1 | Stand – alone signalling RB for PCCH..... | 389 | +| 8.4.2 | Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 389 | +| 8.4.3 | Interactive / Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH +
SRB for BCCH..... | 389 | +| 8.4.4 | Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for
CCCH + SRB for DCCH + SRB for BCCH..... | 389 | +| 8.4.5 | SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 389 | +| 8.4.6 | SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH..... | 389 | +| 8.4.7 | RB for CTCH + SRB for CCCH + SRB for BCCH..... | 389 | +| 8.5 | Combinations on PRACH..... | 390 | +| 8.5.1 | SRB for CCCH + SRB for DCCH..... | 390 | +| 8.5.2 | Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH..... | 390 | +| 8.5.3 | Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH..... | 390 | +| 9 | Examples of Radio Bearers and Signalling Radio Bearers for 1.28 Mcps TDD..... | 390 | +| 9.1 | Combinations on DPCH..... | 390 | +| 9.1.1 | Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH..... | 390 | +| 9.1.1a | Stand-alone UL: 1.7 DL: 1.7 kbps SRBs for DCCH (multiframe)..... | 390 | +| 9.1.2 | Stand-alone UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 390 | +| 9.1.3 | Stand-aloneUL: 13.6 DL: 13.6 kbps SRBs for DCCH..... | 390 | +| 9.1.4 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 391 | +| 9.1.4a | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2 kbps, 7.95, 5.9, 4.75) / CS RAB +
UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 391 | +| 9.1.5 | Conversational / speech / UL: 10.2 DL: 10.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 391 | +| 9.1.5a | Conversational / speech / UL: (10.2, 6.7, 5.9, 4.75) DL: (10.2, 6.7, 5.9, 4.75) kbps / CS RAB + UL:
3.4 DL: 3.4 kbps SRBs for DCCH..... | 391 | +| 9.1.6 | Conversational / speech / UL: 7.95 DL: 7.95 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 391 | +| 9.1.7 | Conversational / speech / UL: 7.4 DL: 7.4 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH.... | 391 | +| 9.1.7a | Conversational / speech / UL: (7.4, 6.7, 5.9, 4.75) DL: (7.4, 6.7, 5.9, 4.75) kbps / CS RAB + UL: 3.4
DL: 3.4 kbps SRBs for DCCH..... | 391 | +| 9.1.8 | Conversational / speech / UL: 6.7 DL: 6.7 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH.... | 392 | +| 9.1.9 | Conversational / speech / UL: 5.9 DL: 5.9 kbps / CS rab + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 392 | +| 9.1.10 | Conversational / speech / UL: 5.15 DL: 5.15 kbps / CS RAB + UL: 1.7 DL: 1.7 kbps SRBs for
DCCH..... | 392 | +| 9.1.11 | Conversational / speech / UL: 4.75 DL: 4.75 kbps / CS RAB + UL: 1.7 DL: 1.7 kbps SRBs for
DCCH..... | 392 | +| 9.1.12 | Conversational / unknown / UL: 28.8 DL: 28.8 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 392 | +| 9.1.13 | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH. . | 392 | +| 9.1.14 | Conversational / unknown / UL: 32 DL: 32 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH. . | 392 | +| 9.1.15 | Streaming / unknown / UL: 14.4 DL: 14.4 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH.... | 393 | +| 9.1.16 | Streaming / unknown / UL: 28.8 DL: 28.8 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH.... | 393 | +| 9.1.17 | Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH.... | 393 | +| 9.1.18 | Void..... | 393 | +| 9.1.19 | Void..... | 393 | +| 9.1.20 | Void..... | 393 | +| 9.1.21 | Void..... | 393 | +| 9.1.22 | Void..... | 393 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 9.1.23 | Interactive or background / UL: 32 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 393 | +| 9.1.23a | Interactive or background / UL: 8DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 393 | +| 9.1.23b | Interactive or background / UL: 16 DL: 16 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 394 | +| 9.1.23c | Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 394 | +| 9.1.23d | Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH
(20 ms TTI)..... | 394 | +| 9.1.24 | Void..... | 394 | +| 9.1.25 | Interactive or background / UL: 32 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 394 | +| 9.1.26 | Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 394 | +| 9.1.27 | Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 394 | +| 9.1.28 | Interactive or background / UL: 128 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.29 | Interactive or background / UL: 64 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.30 | Interactive or background / UL: 144 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.31 | Interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.32 | Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.33 | Interactive or background / UL: 128 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.34 | Interactive or background / UL: 384 DL: 384 kbps / PS RAB +UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 395 | +| 9.1.35 | Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 396 | +| 9.1.36 | Void..... | 396 | +| 9.1.37 | Void..... | 396 | +| 9.1.38 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32
DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 396 | +| 9.1.38a | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 0
DL: 0 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 396 | +| 9.1.38b | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 8
DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 396 | +| 9.1.38c | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32
DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 396 | +| 9.1.38d | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64
DL: 64 kbps / PS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL:
3.4 kbps SRBs for DCCH..... | 397 | +| 9.1.38e | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 0 DL: 0 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 397 | +| 9.1.38f | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 397 | +| 9.1.38g | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 16 DL: 16 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 397 | +| 9.1.38h | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 397 | +| 9.1.38i | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH... | 397 | +| 9.1.38j | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB +
Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for
DCCH..... | 398 | +| 9.1.39 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32
DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 398 | +| 9.1.40 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64
DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 398 | +| 9.1.41 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64
DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 398 | +| 9.1.42 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64
DL: 256 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 398 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 9.1.43 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 398 | +| 9.1.44 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 128 DL: 2048 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 399 | +| 9.1.45 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 399 | +| 9.1.46 | Void..... | 399 | +| 9.1.47 | Void..... | 399 | +| 9.1.48 | Void..... | 399 | +| 9.1.49 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 399 | +| 9.1.49a | Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH. .... | 399 | +| 9.1.50 | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 399 | +| 9.1.51 | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 400 | +| 9.1.51a | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 400 | +| 9.1.51b | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 16 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 400 | +| 9.1.52 | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 400 | +| 9.1.53 | Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 128 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH..... | 400 | +| 9.1.54 | Void..... | 400 | +| 9.1.55 | Void..... | 401 | +| 9.1.56 | Interactive or background / UL: 8 DL: 8 kbps / PS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 401 | +| 9.1.57 | Interactive or background / UL: 64 DL: 64 kbps / PS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 401 | +| 9.1.58 | Streaming / Unknown / UL: 16 DL: 64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 401 | +| 9.1.59 | Reserved for future use..... | 401 | +| 9.1.60 | Reserved for future use..... | 401 | +| 9.1.61 | Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH..... | 401 | +| 9.2 | Combinations on PDSCH, SCCH, PUSCH and PRACH..... | 401 | +| 9.2.1 | Interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH..... | 401 | +| 9.2.2 | Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH..... | 402 | +| 9.2.3 | Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH..... | 402 | +| 9.3 | Combinations on PDSCH, SCCPCH, DPCH, PUSCH and PRACH..... | 402 | +| 9.3.1 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 402 | +| 9.3.2 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 402 | +| 9.3.3 | Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH..... | 402 | +| 9.4 | Combinations on SCCPCH..... | 403 | +| 9.4.1 | Stand – alone signalling RB for PCCH..... | 403 | +| 9.4.2 | Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 403 | + +| | | | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 9.4.2a | Interactive / Background 32 kbps PS RAB + Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 403 | +| 9.4.2b | SRBs for CCCH + SRB for DCCH + SRB for BCCH..... | 403 | +| 9.4.3 | Interactive / Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH..... | 403 | +| 9.4.3a | SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH..... | 403 | +| 9.4.4 | RB for CTCH + SRB for CCCH + SRB for BCCH..... | 403 | +| 9.5 | Combinations on PRACH..... | 404 | +| 9.5.1 | SRB for CCCH + SRB for DCCH..... | 404 | +| 9.5.2 | Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRBs for DCCH..... | 404 | +| 9.5.3 | Interactive/Background 12.8 kbps PS RAB + Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRBs for DCCH..... | 404 | +| 9.6 | Radio Bearer and Radio Bearer Combinations on DPCH and HS-PDSCH..... | 404 | +| 9.6.1 | Interactive or background / UL:8 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5)..... | 404 | +| 9.6.1a | Interactive or background / UL:8 (multiframe) DL: [max bit rate depending on UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH (multiframe) (REL-5)..... | 405 | +| 9.6.2 | Interactive or background / UL:16 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5)..... | 405 | +| 9.6.2a | Interactive or background / UL:16(multiframe) DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH(multiframe) (REL-5)..... | 406 | +| 9.6.3 | Interactive or background / UL:32 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5)..... | 407 | +| 9.6.3a | Interactive or background / UL:32(multiframe) DL: [max bit rate depending on UE category] / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH(multiframe) (REL-5)..... | 407 | +| 9.6.4 | Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5)..... | 408 | +| 9.6.5 | Interactive or background / UL:128 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5)..... | 408 | +| 9.6.6 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL: [Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5).... | 409 | +| 9.6.7 | Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL: [Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5).... | 410 | +| 9.6.8 | Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL: [Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5).... | 410 | +| A.1 | Common characteristics of scenarios..... | 413 | +| A.1.1 | RTP and RTCP streams..... | 413 | +| A.1.2 | Signalling stream..... | 414 | +| A.1.3 | Data stream..... | 414 | +| A.2 | Scenarios..... | 414 | +| A.2.1 | Speech..... | 414 | +| A.2.2 | Audio..... | 415 | +| A.2.3 | Video..... | 415 | +| A.2.4 | Text..... | 415 | +| A.2.5 | Speech and video..... | 415 | +| A.2.6 | Audio and video..... | 415 | +| A.2.7 | Video, audio, or speech with text..... | 415 | +| Annex B: | Mapping of service scenarios to Radio Access Bearers..... | 416 | +| B.1 | Common requirements..... | 416 | +| B.2 | Bearer characteristics..... | 416 | +| B.3 | RAB Scenarios..... | 417 | +| Annex C: | Change history..... | 418 | + +--- + +## Foreword + +This Technical Report (TR) 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 a list of examples of RABs and RAB combinations which are supported by UTRA with examples of radio interface mapping for these RABs onto Radio Bearers and Signalling Radio Bearers. + +This list of examples describes typical parameters, and should only be understood as possible configurations i.e. any other configuration supported by the Core Specifications and consistent with a given UE capability shall also be supported by this UE. + +The present document addresses the FDD mode as well as the TDD mode. + +This report is a release independent report. This means that the latest release applicable to 3GPP is the reference that this TR is defined upon, and contains information on all previous releases. Actual release where a given example applies is indicated in the relevant section. + +# 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 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing" +- [2] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [4] 3GPP TS 25.322: "RLC Protocol Specification". +- [5] 3GPP TS 25.323: "PDCP Protocol Specification". +- [6] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [7] IETF RFC 2507: "IP Header Compression". +- [8] 3GPP TS 25.306: "UE Radio Access Capabilities" +- [9] IETF RFC 3095: "ROBust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". +- [10] 3GPP TS 26.236: "Packet switched conversational multimedia applications; Transport protocols" +- [11] 3GPP TS 26.234: "Transparent end-to-end packet switched streaming service (PSS); Protocols and codecs" +- [12] IETF RFC1889: "RTP: A Transport Protocol for Real-Time Applications" +- [13] IETF RFC3267: "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs" +- [14] 3GPP TR 26.937: "Transparent end-to-end packet switched streaming service (PSS); RTP usage model" +- [15] 3GPP TS 26.235: "Packet switched conversational multimedia applications; Default codecs" + +[16] IETF RFC2793: "RTP Payload for Text Conversation" + +## 3 Abbreviations and Terms + +### 3.1 Abbreviations + +For the purposes of the present document, the abbreviations contained in TR 21.905 apply, as well as the following: + +| | | +|------|--------------------------------------| +| DL | Downlink | +| EVS | Enhanced Voice Services | +| HC | Header Compression | +| IETF | Internet Engineering Task Force | +| I/B | Interactive / Background | +| IP | Internet Protocol | +| kbps | kilo-bits per second | +| RAB | Radio Access Bearer | +| RB | Radio Bearer | +| RNC | Radio Network Controller | +| ROHC | Robust Header Compression | +| RT | Real-time | +| RTP | Real-time Transport Protocol | +| RTCP | Real-time Transport Control Protocol | +| RTSP | Real-time Streaming Protocol | +| SIP | Session Initiation Protocol | +| SRB | Signalling Radio Bearer | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| UL | Uplink | + +### 3.2 Terms + +| | | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearer | Common term used to refer to RAB, RB, and/or SRB, when there is no need to distinguish between these terms. | +| Radio Access Bearer | Bearer between UE and CN. | +| Radio Bearer | User plane bearer on RAN level between RNC/NodeB and UE. | +| Signalling Radio Bearer | RAN level bearer for RRC and NAS signalling between RNC and UE. User plane signalling bearer (e.g., the bearer for SIP signalling) is not SRB, but RB. | + +NOTE: In [1] also the RAN level bearers are called as RABs. In order to maintain consistency with [1], the term RAB is partly used instead of RB also in this document in similar contexts as in [1]. + +For the Radio Access Bearers mapped on HS-PDSCH in the downlink, or E-PDCH in the uplink, the terminology was enhanced so that the above mentioned terms are used correctly in the document except for subclauses 7.1, 7.2, 7.3 and the complete clauses 8 and 9. + +## 4 QoS Architecture and RAB attributes + +From a user point-of-view services are considered end-to-end, this means from a Terminal Equipment (TE) to another TE. An End-to-End Service may have a certain Quality of Service (QoS) which is provided for the user through the different networks. In UMTS, it is the UMTS Bearer Service that provides the requested QoS through the use of different QoS classes as defined in [2]. + +The UMTS Bearer Service consists of two parts, the Radio Access Bearer (RAB) Service and the Core Network Bearer Service. The Radio Access Bearer Service is realised by a Radio Bearer (RB) Service and an Iu-Bearer Service. The relationship between the services is illustrated in figure 4.1. + +![Figure 4.1: UMTS QoS Architecture diagram showing the hierarchy of services from End-to-End Service down to Physical Bearer Service across TE, MT, UTRAN, CN Iu EDGE NODE, CN Gateway, and TE components.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates the UMTS QoS Architecture. At the top, a bracket labeled 'UMTS' spans across six vertical columns representing network elements: TE, MT, UTRAN, CN Iu EDGE NODE, CN Gateway, and TE. Below this, the architecture is shown in layers: + +- End-to-End Service:** A single wide grey box spanning all six columns. +- Bearer Services:** Below the End-to-End Service, three grey boxes are shown: + - TE/MT Local Bearer Service:** Located under the first two columns (TE and MT). + - UMTS Bearer Service:** A wide grey box spanning the next four columns (MT, UTRAN, CN Iu EDGE NODE, and CN Gateway). + - External Bearer Service:** Located under the last column (TE). +- Radio Access Bearer Service:** A grey box under the UMTS Bearer Service, spanning the MT and UTRAN columns. +- CN Bearer Service:** A grey box under the UMTS Bearer Service, spanning the CN Iu EDGE NODE and CN Gateway columns. +- Radio Bearer Service:** A grey box under the Radio Access Bearer Service, located under the MT column. +- Iu Bearer Service:** A grey box under the UMTS Bearer Service, located under the UTRAN column. +- Backbone Bearer Service:** A grey box under the CN Bearer Service, spanning the CN Iu EDGE NODE and CN Gateway columns. +- UTRA FDD/TDD Service:** A grey box under the Radio Bearer Service, located under the MT column. +- Physical Bearer Service:** A grey box under the Iu Bearer Service, located under the UTRAN column. + +Vertical lines connect the boxes within each column to show the flow of services through the network elements. + +Figure 4.1: UMTS QoS Architecture diagram showing the hierarchy of services from End-to-End Service down to Physical Bearer Service across TE, MT, UTRAN, CN Iu EDGE NODE, CN Gateway, and TE components. + +**Figure 4.1: UMTS QoS Architecture** + +The Radio Access Bearer (RAB) Service is characterised by a number of attributes such as Traffic class, Maximum bit rate, Guaranteed bit rate, SDU error ratio, Residual BER, Transfer Delay etc. As a first approach the four following attributes have been considered to come up with the parameter settings in clause 7 for FDD mode and 8 for TDD mode: + +- Traffic class; +- SSD; +- Maximum bit rate; +- Residual BER. + +The Traffic classes are explained in table 4-1. The Maximum bit rate has been considered at RLC layer and Physical Layer for the acknowledged and unacknowledged modes respectively. The Residual BER is understood as BER at RLC layer and Transport BLER for the acknowledged and unacknowledged modes respectively. + +**Table 4-1: Traffic classes** + +| Traffic class | Conversational class
conversational RT | Streaming class
streaming RT | Interactive class
Interactive best effort | Background
Background best effort | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------| +| Fundamental characteristics | - Preserve time relation (variation) between information entities of the stream

Conversational pattern (stringent and low delay) | - Preserve time relation (variation) between information entities of the stream (i.e. some but constant delay) | Request response pattern

Preserve payload content | Destination is not expecting the data within a certain time

Preserve payload content | +| Example of the application | - speech, video, ... | - facsimile (NT)

- streaming audio and video | - Web browsing | - background download of emails | + +## 5 List of RABs and SRBs + +The following tables provide examples of Radio Access Bearers (RABs) which can be realised by various Radio Bearers (RBs) as defined in clauses 7 and 8. The data rate given for each RAB is the maximum data rate that can be supported by that RAB in case of non real-time RABs. For real-time RABs the given datarate are the guaranteed and maximum bit rates. + +The mapping between Radio Access Bearer and Radio Bearer is internal to UTRAN Radio Resource Management and not standardised. Based on certain Radio Access Bearer attributes, resource utilisation or radio conditions, different Radio Bearers can fulfill the Radio Access Bearer requirements. + +Table 5.1: Void + +### 5.1 Interactive or background class Radio Access Bearers (PS domain) + +The following table lists typical maximum RAB data rates independently for uplink and downlink. These maximum bit rates are part of the "RAB parameters" received by the RNC in the RANAP: RAB ASSIGNMENT messages and must be mandatorily provided from the CN (SGSN) to the UTRAN (RNC). Any combination of the listed example data rates is possible. + +**Table 5.1-1: Interactive or Background / UL: [m] kbps DL: [m] kbps / PS RAB** + +| Max UL bitrate [m] kbps | Max DL bitrate [m] kbps | +|--------------------------------|--------------------------------| +| 0 | 0 | +| 8 | 8 | +| 16 | 16 | +| 24 | 24 | +| 32 | 32 | +| 64 | 64 | +| 128 | 128 | +| 144 | 144 | +| 256 | 256 | +| 384 | 384 | +| 512 | 512 | +| 1024 | 1024 | +| 2048 | 2048 | +| 3072 | 3072 | +| 4096 | 4096 | +| | 6144 | +| | 7168 | +| | 8192 | +| | 10240 | +| | 12288 | +| | 14336 | + +## 5.2 Streaming class Radio Access Bearers + +### 5.2.1 CS domain + +The following table lists typical guaranteed and maximum RAB data rates independently for uplink and downlink which can be used by CS streaming applications for example. These guaranteed and maximum bitrates are part of the "RAB parameters" received by the RNC in the RANAP: RAB ASSIGNMENT messages and must be mandatorily provided from the CN (SGSN) to the UTRAN (RNC) for the streaming traffic class. Any combination of the listed example datarates is possible. It should be noted that the requested maximum bit rate should always be equal to the requested guaranteed bit rate for a given connection. + +**Table 5.2.1-1: Streaming / unknown / UL: [g] [m] kbps DL: [g] [m] kbps / CS RAB** + +| Guaranteed UL bitrate [g] kbps for streaming | Max UL bitrate [m] kbps for streaming | Guaranteed DL bitrate [g] kbps for streaming | Max DL bitrate [m] kbps for streaming | +|----------------------------------------------|---------------------------------------|----------------------------------------------|---------------------------------------| +| 0 | 0 | 0 | 0 | +| 14.4 | 14.4 | 14.4 | 14.4 | +| 28.8 | 28.8 | 28.8 | 28.8 | +| 57.6 | 57.6 | 57.6 | 57.6 | +| 64 | 64 | 64 | 64 | + +NOTE: The requested max. bit rate shall always be equal to the requested guaranteed bit rate. + +### 5.2.2 PS domain + +The following table lists typical guaranteed and maximum RAB data rates independently for uplink and downlink which can be used by PS streaming applications for example. These guaranteed and maximum bit rates are part of the "RAB parameters" received by the RNC in the RANAP: RAB ASSIGNMENT messages and must be mandatorily provided from the CN (SGSN) to the UTRAN (RNC) for the streaming traffic class. Any combination of the listed example data rates is possible. It should be noted that the requested maximum bit rate should always be equal or higher than the requested guaranteed bit rate for a given connection. + +**Table 5.2.2-1: Streaming / unknown / UL: [g] [m] kbps DL: [g] [m] kbps / PS RAB** + +| Guaranteed UL bitrate [g] kbps for streaming | Max UL bitrate [m] kbps for streaming | Guaranteed DL bitrate [g] kbps for streaming | Max DL bitrate [m] kbps for streaming | +|----------------------------------------------|---------------------------------------|----------------------------------------------|---------------------------------------| +| 0 | 0 | 0 | 0 | +| 8 | 8 | 8 | 8 | +| 16 | 16 | 16 | 16 | +| 32 | 32 | 32 | 32 | +| 64 | 64 | 64 | 64 | +| 128 | 128 | 128 | 128 | +| 256 | 256 | 256 | 256 | +| 384 | 384 | 384 | 384 | +| | | 512 | 512 | +| | | 1024 | 1024 | +| | | | 2048 | +| | | | 3072 | +| | | | 4096 | +| | | | 6144 | +| | | | 7168 | +| | | | 8192 | +| | | | 10240 | +| | | | 12288 | +| | | | 14336 | + +NOTE: The requested maximum bit rate shall always be equal or higher than the requested guaranteed bit rate. + +## 5.3 Conversational class Radio Access Bearers + +### 5.3.1 CS domain + +**Table 5.3.1-1: Conversational / speech / UL: [Y] kbps DL: [Y] kbps / CS RAB** + +| UL [Y] kbps for CS voice | DL [Y] kbps for CS voice | +|--------------------------|--------------------------| +| 4.75 | 4.75 | +| 5.15 | 5.15 | +| 5.9 | 5.9 | +| 6.7 | 6.7 | +| 7.4 | 7.4 | +| 7.95 | 7.95 | +| 10.2 | 10.2 | +| 12.2 | 12.2 | + +NOTE: It is understood that for speech service the AMR mode may be operated asymmetrically for the uplink and downlink. Multirate AMR can apply a set of UL and DL datarate out of the entire set of NB-AMR rates, where the set is the same for UL and DL, while the RAB configuration is always set up symmetrically (e.g. same rates in the UL and DL). + +**Table 5.3.1-2: Conversational / speech / UL: [Y] kbps DL: [Y] kbps / CS RAB** + +| UL [Y] kbps for CS voice (WB-AMR) | DL [Y] kbps for CS voice (WB-AMR) | +|-----------------------------------|-----------------------------------| +| 6.60 | 6.60 | +| 8.85 | 8.85 | +| 12.65 | 12.65 | +| 14.25 | 14.25 | +| 15.85 | 15.85 | +| 18.25 | 18.25 | +| 19.25 | 19.25 | +| 23.05 | 23.05 | +| 23.85 | 23.85 | + +NOTE: It is understood that for speech service the AMR mode may be operated asymmetrically for the uplink and downlink. Multirate AMR can apply a set of UL and DL datarate out of the entire set of WB-AMR rates, where the set is the same for UL and DL, while the RAB configuration is always set up symmetrically (e.g. same rates in the UL and DL). + +**Table 5.3.1-3: Conversational / unknown / UL: [Y] kbps DL: [Y] kbps / CS RAB** + +| UL [Y] kbps for CS video or data | DL [Y] kbps for CS video or data | +|----------------------------------|----------------------------------| +| 28.8 | 28.8 | +| 32 | 32 | +| 64 | 64 | + +NOTE: The data rates selected must be symmetrically for the uplink and downlink. + +**Table 5.3.1-4: Conversational / speech / UL: [Y] kbps DL: [Y] kbps / CS RAB** + +| UL [Y] kbps for CS voice (EVS) | DL [Y] kbps for CS voice (EVS) | +|--------------------------------|--------------------------------| +| 5.9 | 5.9 | +| 6.60 | 6.60 | +| 7.2 | 7.2 | +| 8 | 8 | +| 8.85 | 8.85 | +| 9.6 | 9.6 | +| 12.65 | 12.65 | +| 13.2 | 13.2 | +| 16.4 | 16.4 | +| 24.4 | 24.4 | + +NOTE: It is understood that for speech service the EVS mode may be operated asymmetrically for the uplink and downlink. EVS can apply a set of UL and DL datarate out of the entire set of EVS rates, where the set is the same for UL and DL, while the RAB configuration is always set up symmetrically (e.g. same rates in the UL and DL). + +### 5.3.2 PS domain + +**Table 5.3.2-1: Conversational / speech / UL: [Y] kbps DL: [Y] kbps / PS RAB** + +| UL [Y] kbps for PS voice | DL [Y] kbps for PS voice | +|--------------------------|--------------------------| +| 16.8 | 16.8 | +| 17.6 | 17.6 | +| 27.6 | 27.6 | +| 38.8 | 38.8 | +| 39.2 | 39.2 | +| 39.6 | 39.6 | +| 40 | 40 | +| 42.8 | 42.8 | + +**Table 5.3.2-2: Conversational / unknown / UL: [Y] kbps DL: [Y] kbps / PS RAB** + +| UL [Y] kbps for PS voice | DL [Y] kbps for PS voice | +|--------------------------|--------------------------| +| 8 | 8 | +| 16 | 16 | + +## 5.4 Signalling Radio Bearers (Control Plane) + +Table 5.4-1 provides examples of Signalling Radio Bearers (SRBs) which can use configurations as defined in clauses 7, 8 and 9. + +**Table 5.4-1: Signalling Radio Bearers (SRBs)** + +| # | Maximum rate, kbps | Logical channel | PhyCh onto which SRBs are mapped | +|----|---------------------|-----------------|----------------------------------| +| 1 | UL:1.7 DL:1.7 | DCCH | DPCH | +| 2 | UL:3.4 DL:3.4 | DCCH | DPCH | +| 3 | UL:13.6 DL:13.6 | DCCH | DPCH | +| 4 | DL:27.2 (alt. 40.8) | DCCH | SCCPCH | +| 5 | UL:16.6 | CCCH | PRACH | +| 6 | DL:30.4 (alt. 45.6) | CCCH | SCCPCH | +| 7 | DL:33.2 (alt. 49.8) | BCCH | SCCPCH | +| 8 | DL:24 (alt. 6.4) | PCCH | SCCPCH | +| 9 | UL:16.8 (TDD) | SHCCH | PRACH | +| 10 | UL:16.8 (TDD) | SHCCH | PRACH or PUSCH | +| 11 | DL:16 (TDD) | SHCCH | SCCPCH | +| 12 | DL:16 (TDD) | SHCCH | SCCPCH or PUSCH | +| 13 | DL: 0.15 | DCCH | DPCH | +| 14 | UL:27.2 DL:27.2 | DCCH | DPCH | +| 15 | UL:6.8 DL:6.8 | DCCH | DPCH | + +## 6 Combinations of RABs + +Any combination of the listed RABs in clause 5 is possible. Based on the selected RAB or RAB combination, the Radio Resource Management (RRM) inside the RNC selects appropriate Radio Bearers (RB) from clauses 7, 8 or 9. + +For a valid configuration the Signalling Radio Bearer listed in subclause 5.4. is existing alone or it is combined with one or multiple RABs of subclause 5.1, 5.2, 5.3. Configuration limitations are defined in clause 5. + +## 7 Examples of Radio Bearers and Signalling Radio Bearers for FDD + +### 7.1 Combinations on DPCH + +#### 7.1.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.1 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps with support of DL SF = 512. + +This is supported in Release '99. + +#### 7.1.2 Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### 7.1.2a Stand-alone UL:6.8 DL:6.8 kbps SRBs for DCCH + +##### 7.1.2a.1 Uplink + +###### 7.1.2a.1.1 Transport channel parameters + +###### 7.1.2a.1.1.1 Transport channel parameters for UL:6.8 kbps SRBs for DCCH + +| Higher layer | RAB/signalling RB | | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +|--------------|-------------------------------------------------------------|-----------|--------------------------------|-------|---------------------|--------------------| +| | User of Radio Bearer | | RRc | RRc | NAS_DT
High prio | NAS_DT
Low prio | +| RLC | Logical channel type | | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | | UM | AM | AM | AM | +| | Payload sizes, bit | | 136 | 128 | 128 | 128 | +| | Max data rate, bps | | 6800 | 6400 | 6400 | 6400 | +| | AMD/UMD PDU header, bit | | 8 | 16 | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | 4 | 4 | +| | MAC multiplexing | | 4 logical channel multiplexing | | | | +| Layer 1 | TrCH type | | DCH | | | | +| | TB sizes, bit | | 148 (alt 0, 148) | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) | | | | +| | | TF1, bits | 1x148 | | | | +| | TTI, ms | | 20 | | | | +| | Coding type | | CC 1/3 | | | | +| | CRC, bit | | 16 | | | | +| | Max number of bits/TTI before rate matching | | 516 | | | | +| | Uplink: Max number of bits/radio frame before rate matching | | 258 | | | | + +###### 7.1.2a.1.1.2 TFCS + +| | | +|-----------|--------------------------| +| TFCS size | 2 | +| TFCS | SRBs for DCCH = TF0, TF1 | + +### 7.1.2a.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-----| +| DPCH Uplink | Min spreading factor | 128 | +| | Max number of DPDCH data bits/radio frame | 300 | +| | Puncturing Limit | 1 | + +### 7.1.2a.2 Downlink + +#### 7.1.2a.2.1 Transport channel parameters + +##### 7.1.2a.2.1.1 Transport channel parameters for DL:6.8 kbps SRBs for DCCH + +| | | | | | | | | | +|-----------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------|------------------------|------------------------------|-----------------------------|--|--|--| +| Higher layer | RAB/signalling RB
User of Radio Bearer | SRB#1
RRC | SRB#2
RRC | SRB#3
NAS_DT
High prio | SRB#4
NAS_DT
Low prio | | | | +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | | | | +| | RLC mode | UM | AM | AM | AM | | | | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | | | | +| | Max data rate, bps | 6 800 | 6 400 | 6 400 | 6 400 | | | | +| | AMD/UMD PDU header, bit | 8 | 16 | 16 | 16 | | | | +| MAC | MAC header, bit | 4 | 4 | 4 | 4 | | | | +| | MAC multiplexing | 4 logical channel multiplexing | | | | | | | +| Layer 1 | TrCH type | DCH | | | | | | | +| | TB sizes, bit | 148 (alt 0, 148) (note) | | | | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) (note) | | | | | | +| | | TF1, bits | 1x148 | | | | | | +| | TTI, ms | 20 | | | | | | | +| | Coding type | CC 1/3 | | | | | | | +| | CRC, bit | 16 | | | | | | | +| | Max number of bits/TTI before rate matching | 516 | | | | | | | +| | RM attribute | 155 to 230 | | | | | | | +| NOTE: Alternative parameters enable the measurement "transport channel BLER" in the UE. | | | | | | | | | + +##### 7.1.2a.2.1.2 TFCS + +| | | +|-----------|--------------------------| +| TFCS size | 2 | +| TFCS | SRBs for DCCH = TF0, TF1 | + +### 7.1.2a.2.2 Physical channel parameters + +| | | | +|---------------|---------------------------|---------------------------| +| DPCH Downlink | DTX position | Fixed | +| | Spreading factor | 256 | +| | DPCCH | Number of TFCI bits/slot | +| | | 0 | +| | | Number of TPC bits/slot | +| | | 2 | +| | | Number of Pilot bits/slot | +| | | 4 | +| | DPDCH | Number of data bits/slot | +| | | 14 | +| | Number of data bits/frame | 210 | + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.3 Stand-alone UL:13.6 DL:13.6 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.3 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.3a Stand-alone UL:27.2 DL:27.2 kbps SRBs for DCCH + +### 7.1.3a.1 Uplink + +#### 7.1.3a.1.1 Transport channel parameters + +##### 7.1.3a.1.1.1 Transport channel parameters for UL:27.2 kbps SRBs for DCCH + +| | | | | | | | | | +|--------------|-------------------------------------------------------------|--------------------------------|-----------------|---------------------|--------------------|--|--|--| +| Higher layer | RAB/signalling RB | SRB#1 | SRB#2 | SRB#3 | SRB#4 | | | | +| | User of Radio Bearer | RRC | RRC | NAS_DT
High prio | NAS_DT
Low prio | | | | +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | | | | +| | RLC mode | UM | AM | AM | AM | | | | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | | | | +| | Max data rate, bps | 13600 | 12800 | 12800 | 12800 | | | | +| | AMD/UMD PDU header, bit | 8 | 16 | 16 | 16 | | | | +| MAC | MAC header, bit | 4 | 4 | 4 | 4 | | | | +| | MAC multiplexing | 4 logical channel multiplexing | | | | | | | +| Layer 1 | TrCH type | DCH | | | | | | | +| | TB sizes, bit | 148 (alt 0, 148) | | | | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) | | | | | | +| | | TF1, bits | 1x148 | | | | | | +| | | TF2, bits | 2x148 | | | | | | +| | TTI, ms | 10 | | | | | | | +| | Coding type | CC 1/3 | | | | | | | +| | CRC, bit | 16 | | | | | | | +| | Max number of bits/TTI before rate matching | 1008 | | | | | | | +| | Uplink: Max number of bits/radio frame before rate matching | 1008 | | | | | | | +| | RM attribute | 155 to 185 | | | | | | | + +##### 7.1.3a.1.1.2 TFCS + +| | | +|-----------|-------------------------------| +| TFCS size | 3 | +| TFCS | SRBs for DCCH = TF0, TF1, TF2 | + +##### 7.1.3a.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +### 7.1.3a.2 Downlink + +#### 7.1.3a.2.1 Transport channel parameters + +##### 7.1.3a.2.1.1 Transport channel parameters for DL:27.2 kbps SRBs for DCCH + +| Higher layer | RAB/signalling RB | | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +|--------------|---------------------------------------------|-----------|--------------------------------|-------|---------------------|--------------------| +| | User of Radio Bearer | | RRc | RRc | NAS_DT
High prio | NAS_DT
Low prio | +| RLC | Logical channel type | | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | | UM | AM | AM | AM | +| | Payload sizes, bit | | 136 | 128 | 128 | 128 | +| | Max data rate, bps | | 13600 | 12800 | 12800 | 12800 | +| | AMD/UMD PDU header, bit | | 8 | 16 | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | 4 | 4 | +| | MAC multiplexing | | 4 logical channel multiplexing | | | | +| Layer 1 | TrCH type | | DCH | | | | +| | TB sizes, bit | | 148 (alt 0, 148) (note) | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) (note) | | | | +| | | TF1, bits | 1x148 | | | | +| | | TF2, bits | 2x148 | | | | +| | TTI, ms | | 10 | | | | +| | Coding type | | CC 1/3 | | | | +| | CRC, bit | | 16 | | | | +| | Max number of bits/TTI before rate matching | | 1008 | | | | +| | RM attribute | | 155 to 230 | | | | + +NOTE: alternative parameters enable the measurement "transport channel BLER" in the UE. + +##### 7.1.3a.2.1.2 TFCS + +| | | +|-----------|-------------------------------| +| TFCS size | 3 | +| TFCS | SRBs for DCCH = TF0, TF1, TF2 | + +#### 7.1.3a.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------| +| DPCH Downlink | DTX position | | Fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 12 kbps plus support for 'Maximum number of DPDCH bits transmitted per 10 ms' = 1200, DL: 12 kbps. + +This is supported in Release '99. + +### 7.1.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.4 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +### 7.1.5 Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.4a of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +### 7.1.5a Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### 7.1.5a.1 Uplink + +##### 7.1.5a.1.1 Transport channel parameters + +###### 7.1.5a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.1.1.1 of [1]. + +###### 7.1.5a.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.5a.1.1.3 TFCS + +See subclause 6.10.2.4.1.4a.1.1.3 of [1]. + +##### 7.1.5a.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.4a.1.2 of [1]. + +#### 7.1.5a.2 Downlink + +##### 7.1.5a.2.1 Transport channel parameters + +###### 7.1.5a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +###### 7.1.5a.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.1.5a.2.1.3 TFCS + +See subclause 6.10.2.4.1.4a.2.1.3 of [1]. + +##### 7.1.5a.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.4a.2.2 of [1]. + +### 7.1.6 Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.5 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.7 Conversational / speech / UL:(10.2, 6.7, 5.9, 4.75) DL:(10.2, 6.7, 5.9, 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.5a of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.8 Conversational / speech / UL:7.95 DL:7.95 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.6 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.9 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.7 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.10 Conversational / speech / UL:(7.4, 6.7, 5.9, 4.75) DL:(7.4, 6.7, 5.9, 4.75) kbps / CS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.7a of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.11 Conversational / speech / UL:6.7 DL:6.7 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.8 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.12 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.9 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +#### **7.1.12a Conversational / speech / UL:(5.9, 4.75) DL:(5.9, 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.12a.1 Uplink + +## 7.1.12a.1.1 Transport channel parameters + +## 7.1.12a.1.1.1 Transport channel parameters for Conversational / speech / UL:(5.9, 4.75) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3 | +|--------------|-------------------------------------------------------------|-----------|---------------------------------|----------------|----------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 39, 42, 55 (alt. 0, 39, 42, 55) | 53, 63 | 60 | +| | Max data rate, bps | | 5900 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 39, 42, 55 (alt. 0, 39, 42, 55) | 53, 63 | 60 | +| | TFS | TF0, bits | 0x55 (alt. 1x0) (note) | 0x63 | 0x60 | +| | | TF1, bits | 1x39 | 1x53 | N/A | +| | | TF2, bits | 1x42 | 1x63 | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 225 | 213 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 113 | 107 | 0 | +| | RM attribute | | 180-220 | 170-210 | 215-256 | + +NOTE: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +## 7.1.12a.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.12a.1.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF0, TF0), (TF3, TF2, TF0, TF0)
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF1, TF0, TF1), (TF3, TF2, TF0, TF1) | + +## 7.1.12a.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.9.1.2 of [1]. + +## 7.1.12a.2 Downlink + +## 7.1.12a.2.1 Transport channel parameters + +## 7.1.12a.2.1.1 Transport channel parameters for Conversational / speech / DL:(5.9, 4.75) kbps / CS RAB + +| Higher Layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3 | +|--------------|---------------------------------------------|-----------|----------------|----------------|----------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 39, 42, 55 | 53, 63 | 60 | +| | Max data rate, bps | | 5900 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 39, 42, 55 | 53, 63 | 60 | +| | TFS
(note 1) | TF0, bits | 1x0 (note 2) | 0x63 | 0x60 | +| | | TF1, bits | 1x39 | 1x53 | N/A | +| | | TF2, bits | 1x42 | 1x63 | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | 0 | +| | Max number of bits/TTI after channel coding | | 225 | 213 | 0 | +| | RM attribute | | 180-220 | 170-210 | 215-256 | + +NOTE 1: The TrCH corresponding to RAB subflow #1 should be used as the guiding TrCH, (see subclause 4.3 in TS 25.212). + +NOTE 2: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +## 7.1.12a.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.12a.2.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF0, TF0), (TF3, TF2, TF0, TF0)
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF1, TF0, TF1), (TF3, TF2, TF0, TF1) | + +## 7.1.12a.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.9.2.2 of [1]. + +## 7.1.12b Conversational / speech / UL:5.9 DL:5.9 (SF=128) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.12b.1 Uplink + +See subclause 6.10.2.4.1.9.1 of [1]. + +## 7.1.12b.2 Downlink + +### 7.1.12b.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.9.2.1 of [1]. + +### 7.1.12b.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Fixed | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | 0 | +| | | Number of TPC bits/slot | +| | DPDCH | 2 | +| | | Number of Pilot bits/slot | +| | | 4 | +| | | Number of data bits/slot | +| | | 34 | +| | | Number of data bits/frame | +| | | 510 | + +## 7.1.13 Conversational / speech / UL:5.15 DL:5.15 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.10 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.14 Conversational / speech / UL:4.75 DL:4.75 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.11 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.15 Conversational / unknown / UL:28.8/DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.12 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.16 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.13 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.16a Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 5. + +## 7.1.16a.1 Uplink + +## 7.1.16a.1.1 Transport channel parameters + +## 7.1.16a.1.1.1 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2
(note) | RAB subflow #3
(note) | +|--------------|-------------------------------------------------------------|-----------|-------------------|--------------------------|--------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 640 | 60 | 60 | +| | Max data rate, bps | | 64 000 | | | +| MAC | TrD PDU header, bit | | 0 | | | +| | MAC header, bit | | 0 | | | +| Layer 1 | MAC multiplexing | | N/A | | | +| | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 640 | 60 | 60 | +| | TFS | TF0, bits | 0x640 | 0x60 | 0x60 | +| | | TF1, bits | 2x640(alt. 4x640) | N/A | N/A | +| | TTI, ms | | 20(alt. 40) | 20(alt. 40) | 20(alt. 40) | +| | Coding type | | TC | TC | TC | +| | CRC, bit | | 16 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 3 948(alt. 7 884) | 0 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 1 974(alt. 1 971) | 0 | 0 | +| | RM attribute | | 150 to 195 | 256 | 256 | + +NOTE: RAB subflow #2 and RAB subflow #3 do not exist in Iu interface. UTRAN establishes this additional "dummy" subflows when the RAB is assigned. + +## 7.1.16a.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.16a.1.1.3 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 4 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow #3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1) | + +## 7.1.16a.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2 400 | +| | Puncturing Limit | 0.88 | + +## 7.1.16a.2 Downlink + +## 7.1.16a.2.1 Transport channel parameters + +## 7.1.16a.2.1.1 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2
(note) | RAB subflow #3
(note) | +|--------------|----------------------|--|----------------|--------------------------|--------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 640 | 60 | 60 | +| | Max data rate, bps | | 64 000 | | | +| MAC | TrD PDU header, bit | | 0 | | | +| | MAC header, bit | | 0 | | | +| Layer 1 | MAC multiplexing | | N/A | | | +| | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 640 | 60 | 60 | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-------------------|-------------|-------------| +| TFS | TF0, bits | 0x640 | 0x60 | 0x60 | +| | TF1, bits | 2x640(alt. 4x640) | N/A | N/A | +| | TTI, ms | 20(alt. 40) | 20(alt. 40) | 20(alt. 40) | +| | Coding type | TC | TC | TC | +| | CRC, bit | 16 | N/A | N/A | +| | Max number of bits/TTI after channel coding | 3 948(alt. 7 884) | 0 | 0 | +| | RM attribute | 150 to 195 | 256 | 256 | +| NOTE: RAB subflow #2 and RAB subflow #3 do not exist in Iu interface. UTRAN establishes this additional "dummy" subflows when the RAB is assigned. | | | | | + +#### 7.1.16a.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.1.16a.2.1.3 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 4 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow #3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1) | + +#### 7.1.16a.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | +| | | 8 | +| | | 4 | +| | | 8 | +| | | 140 | +| | | 2 100 | + +### 7.1.16b Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH+ DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 5. + +#### 7.1.16b.1 Uplink + +##### 7.1.16b.1.1 Transport channel parameters + +###### 7.1.16b.1.1.1 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +See subclause 7.1.16a.1.1.1 + +###### 7.1.16b.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.1.16b.1.1.3 TFCS + +See subclause 7.1.16a.1.1.1 + +##### 7.1.16b.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2 400 | +| | Puncturing Limit | 0.88 | + +7.1.16b.2 Downlink + +7.1.16b.2.1 Transport channel parameters + +7.1.16b.2.1.1 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See subclause 7.1.16a.2.1.1 + +7.1.16b.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.16b.2.1.3 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +7.1.16b.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 4 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow #3, DCCH, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0) | + +7.1.16b.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------| +| DPCH Downlink | DTX position | Flexible | | +| | Spreading factor | 32 | | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2 100 | + +## 7.1.17 Conversational / unknown / UL:32 DL:32 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.14 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.18 Streaming / unknown / UL:14.4 DL:14.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.15 of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps with support of turbo encoding and 'Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant' = 1280, DL: 32 kbps. + +This is supported in Release '99. + +## 7.1.19 Streaming / unknown / UL:28.8 DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.16 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.20 Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.17 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.21 Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.21.1 Uplink + +#### 7.1.21.1.1 Transport channel parameters + +##### 7.1.21.1.1.1 Transport channel parameters for Streaming / unknown / UL:0 kbps / CS RAB + +N/A + +##### 7.1.21.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 6.10.2.4.1.18.1.1.3 TFCS + +See subclause 6.10.2.4.1.2.1.1.2 of [1]. + +#### 7.1.21.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.2.1.2 of [1]. + +### 7.1.21.2 Downlink + +#### 7.1.21.2.1 Transport channel parameters + +##### 7.1.21.2.1.1 Transport channel parameters for Streaming / unknown / DL:64 kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|-------------------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | TM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 64000 | +| | TrD PDU header, bit | | 0 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 320 | +| | TFS | TF0, bits | 0x320 (alt. 1x0) (note) | +| | | TF1, bits | 1x320 | +| | | TF2, bits | 2x320 | +| | | TF3, bits | 4x320 | +| | | TF4, bits | 8x320 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | RM attribute | | 125-165 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. + +## 7.1.21.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.21.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +## 7.1.21.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|--------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of data bits/slot | +| | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 64 kbps plus support for 'Maximum total number of transport blocks received within TTIs that end at the same time' = 16. + +This is supported in Release '99. + +## 7.1.22 Streaming / unknown / UL:64 DL:0 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +## 7.1.22.1 Uplink + +## 7.1.22.1.1 Transport channel parameters + +## 7.1.22.1.1.1 Transport channel parameters for Streaming / unknown / UL:64 kbps / CS RAB + +| | | | | +|--------------|-------------------------------------------------------------|-----------|------------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | TM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 64000 | +| | TrD PDU header, bit | | 0 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 320 | +| | TFS | TF0, bits | 0x320 | +| | | TF1, bits | 1x320 | +| | | TF2, bits | 2x320 | +| | | TF3, bits | 4x320 | +| | | TF4, bits | 8x320 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 2019 | +| | RM attribute | | 125-165 | + +## 7.1.22.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.22.1.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +## 7.1.22.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +## 7.1.22.2 Downlink + +## 7.1.22.2.1 Transport channel parameters + +## 7.1.22.2.1.1 Transport channel parameters for Streaming / unknown / DL:0 kbps / CS RAB + +N/A. + +## 7.1.22.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.22.2.1.3 TFCS + +See subclause 6.10.2.4.1.2.2.1.2 of [1]. + +## 7.1.22.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.2.2.2 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.23 Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +## 7.1.23.1 Uplink + +See subclause 6.10.2.4.1.23.1 of [1]. + +## 7.1.23.2 Downlink + +## 7.1.23.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.23.2.1 of [1]. + +### 7.1.23.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. For the alternative UL configuration, the minimum UE class supporting this combination is UL: 32 kbps. + +This is supported in Release '99. + +## 7.1.24 Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.24.1 Uplink + +See subclause 6.10.2.4.1.23a.1 of [1]. + +### 7.1.24.2 Downlink + +#### 7.1.24.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.23a.2.1 of [1]. + +#### 7.1.24.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.25 Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.25.1 Uplink + +See subclause 6.10.2.4.1.23b.1 of [1] + +### 7.1.25.2 Downlink + +#### 7.1.25.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.23b.2.1 of [1]. + +### 7.1.25.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.26 Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.26.1 Uplink + +See subclause 6.10.2.4.1.23c.1 of [1]. + +#### 7.1.26.2 Downlink + +##### 7.1.26.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.23c.2.1 of [1]. + +##### 7.1.26.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.27 Interactive or background / UL:32 DL:32 kbps / PS RAB (20 ms TTI)+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.27.1 Uplink + +See subclause 6.10.2.4.1.23d.1 of [1]. + +## 7.1.27.2 Downlink + +## 7.1.27.2.1 Transport channel parameters + +## 7.1.27.2.1.1 Transport channel parameters for Interactive or background / DL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|------------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 alt.640 | +| | Max data rate, bps | | 32000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 alt. 656 | +| | TFS | TF0, bits | 0x336 alt. 0x656 | +| | | TF1, bits | 1x336 alt. 1x656 | +| | | TF2, bits | 2x336 alt. none | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2124 alt. 2028 | +| | RM attribute | | 135-175 alt. tbd | + +## 7.1.27.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.27.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 alt. 4 | +| TFCS | (32 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF0,TF1), (TF1,TF1), (TF2,TF1)
alt. (32 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF0,TF1), (TF1,TF1) | + +## 7.1.27.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99, the alt. is supported in Release 5. + +## 7.1.28 Interactive or background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.28.1 Uplink + +#### 7.1.28.1.1 Transport channel parameters + +##### 7.1.28.1.1.1 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 64000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | | TF2, bits | 2x336 | +| | | TF3, bits | 3x336 | +| | | TF4, bits | 4x336 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 4236 | +| | Uplink: Max number of bits/radio frame before rate matching | | 2118 | +| | RM attribute | | 130-170 | + +##### 7.1.28.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.28.1.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +#### 7.1.28.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +### 7.1.28.2 Downlink + +#### 7.1.28.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.23.2.1 of [1]. + +## 7.1.28.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 12 plus support for turbo decoding and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 640. The minimum UE class to support the alternative DL configuration is DL: 12kbps. + +This is supported in Release '99. + +## 7.1.29 Interactive or background / UL:32 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.29.1 Uplink + +See subclause 6.10.2.4.1.25.1 of [1]. + +### 7.1.29.2 Downlink + +#### 7.1.29.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.25.2.1 of [1]. + +#### 7.1.29.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. The minimum UE class to support the alternative UL configuration (10ms TTI) is UL: 32kbps. + +This is supported in Release '99. + +## 7.1.30 Interactive or background / UL:64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.30.1 Uplink + +See subclause 6.10.2.4.1.26.1 of [1]. + +### 7.1.30.2 Downlink + +See subclause 7.1.29.2. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### 7.1.31 Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.31.1 Uplink + +See subclause 6.10.2.4.1.27.1 of [1]. + +#### 7.1.31.2 Downlink + +##### 7.1.31.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.27.2.1 of [1]. + +##### 7.1.31.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.32 Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.32.1 Uplink + +See subclause 6.10.2.4.1.28.1 of [1]. + +#### 7.1.32.2 Downlink + +See subclause 7.1.31.2. + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.33 Interactive or background / UL:64 DL:144 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.33.1 Uplink + +See subclause 6.10.2.4.1.29.1 of [1]. + +#### 7.1.33.2 Downlink + +##### 7.1.33.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.29.2.1 of [1]. + +### 7.1.33.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.34 Interactive or background / UL:144 DL:144 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH + +#### 7.1.34.1 Uplink + +See subclause 6.10.2.4.1.30.1 of [1]. + +#### 7.1.34.2 Downlink + +See subclause 7.1.33.2. + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.35 Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH + +#### 7.1.35.1 On DPCH + +##### 7.1.35.1.1 Uplink + +See subclause 6.10.2.4.1.31.1 of [1]. + +##### 7.1.35.1.2 Downlink + +###### 7.1.35.1.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.31.2.1 of [1]. + +###### 7.1.35.1.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | Number of DPDCH | | 1 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps plus support for 'Maximum number of physical channel bits received in any 10ms interval' = 9600. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 384kbps. + +This is supported in Release '99. + +## 7.1.35.2 On PDSCH and DPCH + +### 7.1.35.2.1 Uplink + +See subclause 6.10.2.4.1.24.1 of [1]. + +### 7.1.35.2.2 Downlink + +#### 7.1.35.2.2.1 Transport channel parameters + +##### 7.1.35.2.2.1.1 Transport channel parameters for Interactive or background / DL:256 kbps / PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|--------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 384000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 18 | +| | MAC multiplexing | | Logical channel multiplexing on a frame by frame basis | +| Layer 1 | TrCH type | | DSCH | +| | TB sizes, bit | | 354 | +| | TFS | TF0, bits | 0x354 | +| | | TF1, bits | 1x354 | +| | | TF2, bits | 2x354 | +| | | TF3, bits | 4 x354 | +| | | TF4, bits | 8 x354 | +| | | TF5, bits | N/A (alt. 12x354) | +| | | TF6, bits | N/A (alt. 16x354) | +| | TTI, ms | | 10(alt. 20) | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8892(alt. 17784) | +| | RM attribute | | 135-175 | + +##### 7.1.35.2.2.1.2 Transport channel parameters for DL:3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.35.2.2.1.3 TFCS + +| | | | +|-------------------------------------|-----------|--------------------------------------------------------------------------------| +| PDSCH | TFCS size | 5 (alt.7) | +| | TFCS | 256 kbps RAB =TF0, TF1, TF2, TF3, TF4 (alt. TF0, TF1, TF2, TF3, TF4, TF5, TF6) | +| DPCH Downlink associated with PDSCH | TFCS size | 2 | +| | TFCS | SRBs for DCCH = TF0, TF1 | + +## 7.1.35.2.2.2 Physical channel parameters + +| | | | | +|-------------------------------------------------|--------------------------|---------------------------|-----------------------------------------------------| +| PDSCH | RAB or SRB, TrCh | | Interactive or background / 256 kbps / PS RAB, DSCH | +| | DTX position | | N/A (SingleTrCH) | +| | Minimum spreading factor | | 8 | +| DPCH
Downlink
associated
with
PDSCH | RAB or SRB, TrCh | | 3.4 kbps SRB for DCCH, DCH | +| | DTX position | | N/A (SingleTrCH) | +| | Spreading factor | | 256 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 12 | +| | | Number of data bits/frame | 180 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps plus support for PDSCH plus support for 'Maximum number of physical channel bits received in any 10ms interval' = 9600. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 384kbps plus support for PDSCH. + +This is supported in Release '99. + +## 7.1.36 Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH + +### 7.1.36.1 On DPCH + +#### 7.1.36.1.1 Uplink + +See subclause 6.10.2.4.1.32.1 of [1]. + +#### 7.1.36.1.2 Downlink + +##### 7.1.36.1.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.32.2.1 of [1]. + +##### 7.1.36.1.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | Number of DPDCH | | 1 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +### 7.1.36.2 On PDSCH and DPCH + +See subclause 6.10.2.4.2.2 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps plus support for PDSCH. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +## 7.1.37 Interactive or background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.37.1 Uplink + +See subclause 6.10.2.4.1.33.1 of [1]. + +### 7.1.37.2 Downlink + +See subclause 7.1.36.1.2. + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 384kbps. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +## 7.1.38 Interactive or background / UL:384 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.38.1 Uplink + +See subclause 6.10.2.4.1.34.1 of [1]. + +### 7.1.38.2 Downlink + +See subclause 7.1.36.1.2. + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 384kbps. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +## 7.1.39 Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.39.1 On DPCH + +#### 7.1.39.1.1 Uplink + +See subclause 6.10.2.4.1.35.1 of [1]. + +#### 7.1.39.1.2 Downlink + +##### 7.1.39.1.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.35.2.1 of [1]. + +##### 7.1.39.1.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 4 | +| | Number of DPCH | | 3 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 1248 | +| | | Number of data bits/frame | 18720 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 2048kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms) + +alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +### 7.1.39.2 On PDSCH and DPCH + +See subclause 6.10.2.4.2.3 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 2048kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +## 7.1.40 Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.40.1 Uplink + +See subclause 6.10.2.4.1.28.1 of [1]. + +### 7.1.40.2 Downlink + +See subclause 7.1.39.1.2. + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 2048 kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +## 7.1.41 Interactive or background / UL:384 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.41.1 Uplink + +See subclause 6.10.2.4.1.34.1 of [1]. + +### 7.1.41.2 Downlink + +See subclause 7.1.39.1.2. + +The minimum UE classes supporting this combination are UL: 384 kbps, DL: 2048 kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +## 7.1.42 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.42.1 Uplink + +See subclause 6.10.2.4.1.38.1 of [1]. + +## 7.1.42.2 Downlink + +### 7.1.42.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38.2.1 of [1]. + +### 7.1.42.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. + +This is supported in Release '99. + +## 7.1.43 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.38a of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 12 kbps plus support for 'Maximum number of simultaneous transport channels' = 5. + +This is supported in Release '99. + +## 7.1.44 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.44.1 Uplink + +See subclause 6.10.2.4.1.38b.1 of [1]. + +### 7.1.44.2 Downlink + +#### 7.1.44.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38b.2.1 of [1]. + +#### 7.1.44.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 32 kbps. + +This is supported in Release '99. + +## 7.1.45 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.45.1 Uplink + +See subclause 6.10.2.4.1.38c.1 of [1]. + +### 7.1.45.2 Downlink + +#### 7.1.45.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38c.2.1 of [1]. + +#### 7.1.45.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +## 7.1.45a Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB (20ms TTI)+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.45a.1 Uplink + +#### 7.1.45a.1.1 Transport channel parameters + +##### 7.1.45a.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1] + +##### 7.1.45a.1.1.2 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23d.1.1.1 of [1] + +##### 7.1.45a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.45a.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF1,TF2,TF1) | + +## 7.1.45a.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1.0 | + +## 7.1.45a.2 Downlink + +## 7.1.45a.2.1 Transport channel parameters + +## 7.1.45a.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1] + +## 7.1.45a.2.1.2 Transport channel parameters for Interactive or background / DL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23d.2.1.1 of [1] + +## 7.1.45a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.45a.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF1,TF2,TF1) | + +## 7.1.45a.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of Pilot bits/slot | +| | DPDCH | 140 | +| | | Number of data bits/frame | +| | | 2100 | + +7.1.46 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.46.1 Uplink + +See subclause 6.10.2.4.1.38d.1 of [1]. + +#### 7.1.46.2 Downlink + +##### 7.1.46.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38d.2.1 of [1]. + +##### 7.1.46.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +7.1.47 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.38e of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 12 kbps plus support for 'Maximum number of simultaneous transport channels' = 5. + +This is supported in Release '99. + +7.1.47a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 12 kbps plus support for 'Maximum number of simultaneous transport channels' = 5. + +This is supported in Release '99. + +#### 7.1.47a.1 Uplink + +##### 7.1.47a.1.1 Transport channel parameters + +###### 7.1.47a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +###### 7.1.47a.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See clause 6.10.2.4.1.38a.1.1.2 of [1]. + +7.1.47a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.47a.1.1.4 TFCS + +See clause 6.10.2.4.1.38e.1.1.4 of [1]. + +7.1.47a.1.2 Physical channel parameters + +See clause 6.10.2.4.1.38e.1.2 of [1]. + +7.1.47a.2 Downlink + +7.1.47a.2.1 Transport channel parameters + +7.1.47a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +7.1.47a.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See clause 6.10.2.4.1.38a.2.1.2 of [1]. + +7.1.47a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.47a.2.1.4 TFCS + +See clause 6.10.2.4.1.38e.2.1.4 of [1]. + +7.1.47a.2.2 Physical channel parameters + +See clause 6.10.2.4.1.38e.2.2 of [1]. + +**7.1.48 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +7.1.48.1 Uplink + +See subclause 6.10.2.4.1.38f.1 of [1]. + +7.1.48.2 Downlink + +7.1.48.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38f.2.1 of [1]. + +7.1.48.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 32 kbps. + +This is supported in Release '99. + +## 7.1.48a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 32 kbps. + +This is supported in Release '99. + +### 7.1.48a.1 Uplink + +#### 7.1.48a.1.1 Transport channel parameters + +##### 7.1.48a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +##### 7.1.48a.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See clause 6.10.2.4.1.38b.1.1.2 of [1]. + +##### 7.1.48a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.48a.1.1.4 TFCS + +See clause 6.10.2.4.1.38f.1.1.4 of [1]. + +#### 7.1.48a.1.2 Physical channel parameters + +See clause 6.10.2.4.1.38f.1.2 of [1]. + +### 7.1.48a.2 Downlink + +#### 7.1.48a.2.1 Transport channel parameters + +##### 7.1.48a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +##### 7.1.48a.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See clause 6.10.2.4.1.38b.2.1.2 of [1]. + +##### 7.1.48a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.48a.2.1.4 TFCS + +See clause 6.10.2.4.1.38f.2.1.4 of [1]. + +#### 7.1.48a.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +7.1.49 Conversational / speech / UL: (12.2 7.95 5.9 4.75) kbps DL: (12.2 7.95 5.9 4.75) / CS RAB + Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.49.1 Uplink + +See subclause 6.10.2.4.1.38g.1 of [1]. + +#### 7.1.49.2 Downlink + +##### 7.1.49.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38g.2.1 of [1]. + +##### 7.1.49.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +7.1.49a Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps DL: (12.2 7.4 5.9 4.75) / CS RAB + Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### 7.1.49a.1 Uplink + +##### 7.1.49a.1.1 Transport channel parameters + +###### 7.1.49a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +###### 7.1.49a.1.1.2 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See clause 6.10.2.4.1.23b.1.1.1 of [1]. + +###### 7.1.49a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.49a.1.1.4 TFCS + +See clause 6.10.2.4.1.38g.1.1.4 of [1]. + +##### 7.1.49a.1.2 Physical channel parameters + +See clause 6.10.2.4.1.38g.1.2 of [1]. + +## 7.1.49a.2 Downlink + +## 7.1.49a.2.1 Transport channel parameters + +## 7.1.49a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +## 7.1.49a.2.1.2 Transport channel parameters for Interactive or background / DL:16 kbps / PS RAB + +See clause 6.10.2.4.1.23b.2.1.1 of [1]. + +## 7.1.49a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.49a.2.1.4 TFCS + +See clause 6.10.2.4.1.38g.2.1.4 of [1]. + +## 7.1.49a.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +7.1.50 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +## 7.1.50.1 Uplink + +See subclause 6.10.2.4.1.38h.1 of [1]. + +## 7.1.50.2 Downlink + +## 7.1.50.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38h.2.1 of [1]. + +## 7.1.50.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 7.1.50a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### 7.1.50a.1 Uplink + +#### 7.1.50a.1.1 Transport channel parameters + +##### 7.1.50a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +##### 7.1.50a.1.1.2 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See clause 6.10.2.4.1.23c.1.1.1 of [1]. + +##### 7.1.50a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 7.1.50a.1.1.4 TFCS + +See clause 6.10.2.4.1.38h.1.1.4 of [1]. + +### 7.1.50a.1.2 Physical channel parameters + +See clause 6.10.2.4.1.38h.1.2 of [1]. + +### 7.1.50a.2 Downlink + +#### 7.1.50a.2.1 Transport channel parameters + +##### 7.1.50a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +##### 7.1.50a.2.1.2 Transport channel parameters for Interactive or background / DL:32 kbps / PS RAB + +See clause 6.10.2.4.1.23c.2.1.1 of [1]. + +##### 7.1.50a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.1.50a.2.1.4 TFCS + +See clause 6.10.2.4.1.38h.2.1.4 of [1]. + +### 7.1.50a.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +7.1.51 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.51.1 Uplink + +See subclause 6.10.2.4.1.38i.1 of [1]. + +#### 7.1.51.2 Downlink + +##### 7.1.51.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38i.2.1 of [1]. + +##### 7.1.51.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +7.1.51a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### 7.1.51a.1 Uplink + +##### 7.1.51a.1.1 Transport channel parameters + +###### 7.1.51a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +###### 7.1.51a.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +See clause 6.10.2.4.1.26.1.1.1 of [1]. + +###### 7.1.51a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.51a.1.1.4 TFCS + +See clause 6.10.2.4.1.38i.1.1.4 of [1]. + +##### 7.1.51a.1.2 Physical channel parameters + +See clause 6.10.2.4.1.38i.1.2 of [1]. + +## 7.1.51a.2 Downlink + +## 7.1.51a.2.1 Transport channel parameters + +## 7.1.51a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +## 7.1.51a.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See clause 6.10.2.4.1.25.2.1.1 of [1]. + +## 7.1.51a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.51a.2.1.4 TFCS + +See clause 6.10.2.4.1.38i.2.1.4 of [1]. + +## 7.1.51a.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +7.1.52 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +## 7.1.52.1 Uplink + +See subclause 6.10.2.4.1.38j.1 of [1]. + +## 7.1.52.2 Downlink + +## 7.1.52.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.38j.2.1 of [1]. + +## 7.1.52.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +The minimum UE classes supporting this combination are UL: 64kbp, DL: 128kbp. + +This is supported in Release '99. + +## 7.1.52a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbp, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.52a.1 Uplink + +See clause 7.1.51a.1. + +### 7.1.52a.2 Downlink + +#### 7.1.52a.2.1 Transport channel parameters + +##### 7.1.52a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +##### 7.1.52a.2.1.2 Transport channel parameters for Interactive or background / DL:128 kbps / PS RAB + +See clause 6.10.2.4.1.27.2.1.1 of [1]. + +##### 7.1.52a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.52a.2.1.4 TFCS + +See clause 6.10.2.4.1.38j.2.1.4 of [1]. + +#### 7.1.52a.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +## 7.1.53 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH + +### 7.1.53.1 Uplink + +See subclause 6.10.2.4.1.39.1 of [1]. + +### 7.1.53.2 Downlink + +#### 7.1.53.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.39.2.1 of [1]. + +### 7.1.53.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.54 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH + +#### 7.1.54.1 Uplink + +See subclause 6.10.2.4.1.40.1 of [1]. + +#### 7.1.54.2 Downlink + +See subclause 7.1.53.2. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.55 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.55.1 Uplink + +See subclause 6.10.2.4.1.41.1 of [1]. + +#### 7.1.55.2 Downlink + +##### 7.1.55.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.41.2.1 of [1]. + +##### 7.1.55.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +## 7.1.56 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.56.1 On DPCH + +#### 7.1.56.1.1 Uplink + +See subclause 6.10.2.4.1.42.1 of [1]. + +#### 7.1.56.1.2 Downlink + +##### 7.1.56.1.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.42.2.1 of [1]. + +##### 7.1.56.1.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | Number of DPDCH | | 1 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 384 kbps. + +This is supported in Release '99. + +### 7.1.56.2 On PDSCH and DPCH + +#### 7.1.56.2.1 Uplink + +See subclause 6.10.2.4.1.40.1 of [1]. + +#### 7.1.56.2.2 Downlink + +##### 7.1.56.2.2.1 Transport channel parameters + +###### 7.1.56.2.2.1.1 Transport channel parameters for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +###### 7.1.56.2.2.1.2 Transport channel parameters for Interactive or background / DL:256 kbps / PS RAB + +See subclause 6.10.2.4.2.1.2.1.1 of [1]. + +###### 7.1.56.2.2.1.3 Transport channel parameters for DL:3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1]. + +## 7.1.56.2.2.1.4 TFCS + +| | | | +|-------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDSCH | TFCS size | 5 (alt.7) | +| | TFCS | 256 kbps RAB = TF0, TF1, TF2, TF3, TF4
(alt. TF0, TF1, TF2, TF3, TF4, TF5, TF6) | +| DPCH Downlink associated with PDSCH | TFCS size | 6 | +| | TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH) =
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF1, TF0),
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF1, TF1, TF1) | + +## 7.1.56.2.2.2 Physical channel parameters + +| | | | | +|-------------------------------------|--------------------------|---------------------------|------------------------------------------------------------------------------------| +| PDSCH | RAB or SRB, TrCh | | Interactive or background / 256 kbps / PS RAB, DSCH | +| | DTX position | | N/A (SingleTrCH) | +| | Minimum spreading factor | | 4 | +| DPCH Downlink associated with PDSCH | RAB or SRB, TrCh | | Conversational / speech / 12.2 kbps / CS RAB, DCH
+ 3.4 kbps SRBs for DCCH. DCH | +| | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 384 kbps plus support of PDSCH. + +This is supported in Release '99. + +## 7.1.57 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.57.1 On DPCH + +#### 7.1.57.1.1 Uplink + +See subclause 6.10.2.4.1.43.1 of [1]. + +#### 7.1.57.1.2 Downlink + +##### 7.1.57.1.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.43.2.1 of [1]. + +##### 7.1.57.1.2.2 Physical channel parameters + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 384. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +### 7.1.57.2 On PDSCH and DPCH + +See subclause 6.10.2.4.2.5 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 384 kbps plus support for PDSCH. The minimum UE class to support the alternative DL configuration (20ms TTI) is DL: 768kbps. + +This is supported in Release '99. + +## 7.1.58 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.58.1 Uplink + +See subclause 6.10.2.4.2.6.1 of [1]. + +### 7.1.58.2 Downlink + +#### 7.1.58.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.44.2.1 of [1]. + +#### 7.1.58.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | Flexible or fixed | | +| | Spreading factor | 4 | | +| | Number of DPDCH | 3 | | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 1248 | +| | | Number of data bits/frame | 18720 | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 2048 kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +## 7.1.59 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.59.1 Uplink + +See subclause 6.10.2.4.1.44.1 of [1]. + +### 7.1.59.2 Downlink + +See subclause 7.1.58.2. + +The minimum UE classes supporting this combination are UL: 384 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 2048 kbps plus support for 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative) and 'Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant' = 40960 (81920 for the TTI=20ms alternative). + +This is supported in Release '99. + +## 7.1.60 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.60.1 Uplink + +See subclause 6.10.2.4.1.45.1 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 7.1.61 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.61.1 Uplink + +See subclause 6.10.2.4.1.4.1 of [1]. + +### 7.1.61.2 Downlink + +#### 7.1.61.2.1 Transport channel parameters + +##### 7.1.61.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +##### 7.1.61.2.1.2 Transport channel parameters for Streaming / unknown / DL:64 kbps / CS RAB + +See subclause 7.1.21.2.1.1. + +##### 7.1.61.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.61.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF1, TF0, TF0),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF1, TF1, TF0),
(TF0, TF0, TF0, TF2, TF0), (TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF1, TF2, TF0),
(TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF1, TF3, TF0),
(TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0), (TF2, TF1, TF1, TF4, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF1, TF0, TF1),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF1, TF1, TF1),
(TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1), (TF2, TF1, TF1, TF2, TF1),
(TF0, TF0, TF0, TF3, TF1), (TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF1, TF3, TF1),
(TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF1, TF4, TF1) | + +#### 7.1.61.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of Pilot bits/slot | +| | | 8 | +| | | Number of data bits/slot | +| | | 140 | +| | | Number of data bits/frame | +| | | 2100 | + +The minimum UE classes supporting this combination are UL: 12 kbps plus support for 'Maximum number of simultaneous transport channels' = 5, DL: 128kbps. + +This is supported in Release '99. + +### **7.1.62 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.49 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### **7.1.63 Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.49a of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### **7.1.63a Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### **7.1.63a.1 Uplink** + +##### **7.1.63a.1.1 Transport channel parameters** + +###### **7.1.63a.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.2 7.4 5.9 4.75) kbps / CS RAB** + +See clause 6.10.2.4.1.4b.1.1.1 of [1]. + +###### **7.1.63a.1.1.2 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB** + +See clause 6.10.2.4.1.13.1.1.1 of [1]. + +###### **7.1.63a.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH** + +See clause 6.10.2.4.1.2.1.1.1 of [1]. + +###### **7.1.63a.1.1.4 TFCS** + +See clause 6.10.2.4.1.49a.1.1.4 of [1]. + +##### **7.1.63a.1.2 Physical channel parameters** + +See clause 6.10.2.4.1.49a.1.2 of [1]. + +## 7.1.63a.2 Downlink + +### 7.1.63a.2.1 Transport channel parameters + +#### 7.1.63a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +#### 7.1.63a.2.1.2 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See clause 6.10.2.4.1.13.2.1.1 of [1]. + +#### 7.1.63a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.1.63a.2.1.4 TFCS + +See clause 6.10.2.4.1.49a.2.1.4 of [1]. + +### 7.1.63a.2.2 Physical channel parameters + +See clause 6.10.2.4.1.49a.2.2 of [1]. + +## 7.1.64 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.50 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 128kbps. The minimum UE class to support the alternative UL combination (40ms TTI) is UL: 384kbps. + +This is supported in Release '99. + +## 7.1.65 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.65.1 Uplink + +See subclause 6.10.2.4.1.51.1 of [1]. + +### 7.1.65.2 Downlink + +#### 7.1.65.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.51.2.1 of [1]. + +#### 7.1.65.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|------------------|---------------------------|-------------------| +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 128kbps. The minimum UE class to support the alternative UL combination (40ms TTI) is UL: 384kbps. + +This is supported in Release '99. + +## 7.1.66 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.66.1 Uplink + +See subclause 6.10.2.4.1.51a.1 of [1]. + +### 7.1.66.2 Downlink + +#### 7.1.66.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.51a.2.1 of [1]. + +#### 7.1.66.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 7.1.67 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.67.1 Uplink + +See subclause 6.10.2.4.1.51b.1 of [1]. + +### 7.1.67.2 Downlink + +See subclause 7.1.65.2. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +## 7.1.68 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.68.1 Uplink + +See subclause 6.10.2.4.1.52.1 of [1]. + +## 7.1.68.2 Downlink + +### 7.1.68.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.52.2.1 of [1]. + +### 7.1.68.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 384kbps. The minimum UE class to support the alternative UL combination (40ms TTI) is UL: 384kbps. + +This is supported in Release '99. + +## 7.1.69 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.69.1 Uplink + +See subclause 6.10.2.4.1.53.1 of [1]. + +### 7.1.69.2 Downlink + +See subclause 7.1.68.2. + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 384kbps. + +This is supported in Release '99. + +## 7.1.70 Interactive or background / UL:64 DL:128 kbps / PS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.70.1 Uplink + +See subclause 6.10.2.4.1.27.1 of [1]. + +### 7.1.70.2 Downlink + +#### 7.1.70.2.1 Transport channel parameters + +##### 7.1.70.2.1.1 Transport channel parameters for Interactive or background / DL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.27.2.1.1 of [1]. + +##### 7.1.70.2.1.2 Transport channel parameters for Streaming / unknown / DL:64 kbps / CS RAB + +See subclause 7.1.21.2.1.1. + +##### 7.1.70.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.70.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (I/B 128 kbps RAB, Str. 64 kbps RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF0, TF1, TF0), (TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0),
(TF0, TF2, TF0), (TF1, TF2, TF0), (TF2, TF2, TF0), (TF3, TF2, TF0), (TF4, TF2, TF0),
(TF0, TF3, TF0), (TF1, TF3, TF0), (TF2, TF3, TF0), (TF3, TF3, TF0), (TF4, TF3, TF0),
(TF0, TF4, TF0), (TF1, TF4, TF0), (TF2, TF4, TF0), (TF3, TF4, TF0), (TF4, TF4, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1),
(TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2, TF1), (TF3, TF2, TF1), (TF4, TF2, TF1),
(TF0, TF3, TF1), (TF1, TF3, TF1), (TF2, TF3, TF1), (TF3, TF3, TF1), (TF4, TF3, TF1),
(TF0, TF4, TF1), (TF1, TF4, TF1), (TF2, TF4, TF1), (TF3, TF4, TF1), (TF4, TF4, TF1) | + +## 7.1.70.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 8 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. + +This is supported in Release '99. + +## 7.1.71 Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +## 7.1.71.1 Uplink + +See subclause 6.10.2.4.1.56.1 of [1]. + +## 7.1.71.2 Downlink + +## 7.1.71.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.56.2.1 of [1]. + +## 7.1.71.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +The minimum UE classes supporting this combination are UL: 32kbps plus support for turbo encoding, DL: 32kbps plus support for 5 AM entities. + +This is supported in Release '99. + +## 7.1.72 Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.72.1 Uplink + +See subclause 6.10.2.4.1.57.1 of [1]. + +### 7.1.72.2 Downlink + +#### 7.1.72.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.57.2.1 of [1]. + +#### 7.1.72.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps plus support for 5 AM entities. + +This is supported in Release '99. + +## 7.1.73 Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +### 7.1.73.1 Uplink + +See subclause 6.10.2.4.1.58.1 of [1]. + +### 7.1.73.2 Downlink + +#### 7.1.73.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.58.2.1 of [1]. + +#### 7.1.73.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps plus support for 5 AM entities. + +This is supported in Release '99. + +## 7.1.73a Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative + +This configuration optimises the flexibility of the Transport Format Selection by adding an omitted Transport Format, to the transport channel parameters given in the reference subclause 6.10.2.4.1.58 of [1], for the downlink, transport channel Streaming / unknown / DL:64 kbps PS RAB. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps plus support for 5 AM entities. + +This is supported in Release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +### 7.1.73a.1 Uplink + +See subclause 6.10.2.4.1.58.1 of [1] + +### 7.1.73a.2 Downlink + +#### 7.1.73a.2.1 Transport channel parameters + +##### 7.1.73a.2.1.1 Transport channel parameters for Streaming / unknown / DL:64 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 64000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | RM attribute | | 125-165 | + +##### 7.1.73a.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +##### 7.1.73a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.73a.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (64 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1), | + +## 7.1.73a.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|---------------------------|--|-------------------| +| | Spreading factor | | 32 | +| DPCCH | Number of TFCI bits/slot | | 8 | +| | Number of TPC bits/slot | | 4 | +| | Number of Pilot bits/slot | | 8 | +| DPDCH | Number of data bits/slot | | 140 | +| | Number of data bits/frame | | 2100 | + +## 7.1.74 Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +## 7.1.74.1 Uplink + +See subclause 6.10.2.4.1.58a.1 of [1]. + +## 7.1.74.2 Downlink + +## 7.1.74.2.1 Transport channel parameters + +See subclause 6.10.2.4.1.58a.2.1 of [1]. + +## 7.1.74.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|---------------------------|--|-------------------| +| | Spreading factor | | 16 | +| DPCCH | Number of TFCI bits/slot | | 8 | +| | Number of TPC bits/slot | | 8 | +| | Number of Pilot bits/slot | | 16 | +| DPDCH | Number of data bits/slot | | 288 | +| | Number of data bits/frame | | 4320 | + +## 7.1.75 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:8 kbps / PS RAB – TF0 contains zero Transport Blocks . + +NOTE: Conversational / unknown / DL:8 kbps / PS RAB – TF0 contains zero Transport Blocks. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### 7.1.75.1 Uplink + +#### 7.1.75.1.1 Transport channel parameters + +##### 7.1.75.1.1.1 Transport channel parameters for Conversational / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Uplink: Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +##### 7.1.75.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +##### 7.1.75.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +##### 7.1.75.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +#### 7.1.75.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +## 7.1.75.2 Downlink + +## 7.1.75.2.1 Transport channel parameters + +## 7.1.75.2.1.1 Transport channel parameters for Conversational / unknown / DL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | RM attribute | | 135-175 | + +## 7.1.75.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +## 7.1.75.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.75.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +## 7.1.75.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.1.76 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:8 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +NOTE: Conversational / unknown / DL:8 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.76.1 Uplink + +#### 7.1.76.1.1 Transport channel parameters + +##### 7.1.76.1.1.1 Transport channel parameters for Conversational / unknown / UL:8 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Uplink: Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +##### 7.1.76.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +##### 7.1.76.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +##### 7.1.76.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +### 7.1.76.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +### 7.1.76.2 Downlink + +#### 7.1.76.2.1 Transport channel parameters + +##### 7.1.76.2.1.1 Transport channel parameters for Conversational / unknown / DL:8 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | RM attribute | | 135-175 | + +##### 7.1.76.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +##### 7.1.76.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +##### 7.1.76.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +## 7.1.76.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.1.77 Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:16 kbps / PS RAB – TF0 contains zero Transport Blocks. + +NOTE: Conversational / unknown / DL:16 kbps / PS RAB – TF0 contains zero Transport Blocks. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 7.1.77.1 Uplink + +## 7.1.77.1.1 Transport channel parameters + +## 7.1.77.1.1.1 Transport channel parameters for Conversational / unknown / UL:16 kbps / PS RAB + +| | | | | +|--------------|-------------------------------------------------------------|-----------|------------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +## 7.1.77.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +## 7.1.77.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.77.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +## 7.1.77.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +## 7.1.77.2 Downlink + +## 7.1.77.2.1 Transport channel parameters + +## 7.1.77.2.1.1 Transport channel parameters for Conversational / unknown / DL:16 kbps / PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | RM attribute | | 135-175 | + +## 7.1.77.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +#### 7.1.77.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +#### 7.1.77.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +#### 7.1.77.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | | 4 | +| | | Number of Pilot bits/slot | +| | | 8 | +| | DPDCH | Number of data bits/slot | +| | | 60 | +| | | Number of data bits/frame | +| | | 900 | + +### 7.1.78 Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:16 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +NOTE: Conversational / unknown / DL:16 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### 7.1.78.1 Uplink + +##### 7.1.78.1.1 Transport channel parameters + +###### 7.1.78.1.1.1 Transport channel parameters for Conversational / unknown / UL:16 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| | | | | +|--------------|-------------------------------------------------------------|-----------|------------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +#### 7.1.78.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +#### 7.1.78.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +#### 7.1.78.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +#### 7.1.78.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +#### 7.1.78.2 Downlink + +##### 7.1.78.2.1 Transport channel parameters + +###### 7.1.78.2.1.1 Transport channel parameters for Conversational / unknown / DL:16 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | RM attribute | | 135-175 | + +#### 7.1.78.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +#### 7.1.78.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +#### 7.1.78.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +#### 7.1.78.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +### 7.1.79 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +#### 7.1.79.1 Uplink + +##### 7.1.79.1.1 Transport channel parameters + +###### 7.1.79.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +###### 7.1.79.1.1.2 Transport channel parameters for Interactive or Background / UL:0 + UL:0 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-------------------------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 0 | 0 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 0 | | +| | Uplink: Max number of bits/radio frame before rate matching | | 0 | | +| | RM attribute | | 130-170 | | + +###### 7.1.79.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.79.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1) | + +##### 7.1.79.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +## 7.1.79.2 Downlink + +## 7.1.79.2.1 Transport channel parameters + +## 7.1.79.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +## 7.1.79.2.1.2 Transport channel parameters for Interactive or Background / DL:0 + DL:0 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 0 | 0 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 0 | | +| | RM attribute | | 130-170 | | + +## 7.1.79.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.79.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1) | + +## 7.1.79.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------| +| DPCH Downlink | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 34 | +| | | Number of data bits/frame | 510 | + +## 7.1.79a Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + ++ Interactive or background / UL:0 DL:0 kbps / PS RAB + ++ Interactive or background / UL:0 DL:0 kbps / PS RAB + ++ UL:3.4 DL:3.4 kbps SRBs for DCCH (L1 multiplexing) (FDD) + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +#### 7.1.79a.1 Uplink + +##### 7.1.79a.1.1 Transport channel parameters + +###### 7.1.79a.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +###### 7.1.79a.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +###### 7.1.79a.1.1.3 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +###### 7.1.79a.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.79a.1.1.5 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0 kbps RAB, 0 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0, TF0),
(TF2, TF1, TF1, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF0, TF1), (TF2, TF1, TF1, TF0, TF0, TF1) | + +##### 7.1.79a.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.38a.1.2 of [1]. + +#### 7.1.79a.2 Downlink + +##### 7.1.79a.2.1 Transport channel parameters + +###### 7.1.79a.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +###### 7.1.79a.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +###### 7.1.79a.2.1.3 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +###### 7.1.79a.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.1.79a.2.1.5 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0 kbps RAB, 0 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0, TF0),
(TF2, TF1, TF1, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF0, TF1), (TF2, TF1, TF1, TF0, TF0, TF1) | + +##### 7.1.79a.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.38a.2.2 of [1]. + +## 7.1.80 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.80.1 Uplink + +#### 7.1.80.1.1 Transport channel parameters + +##### 7.1.80.1.1.1 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.1.1.1 of [1]. + +##### 7.1.80.1.1.2 Transport channel parameters for Interactive or Background / UL:8 + UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.1.1.1 of [1] + +##### 7.1.80.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.80.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (64 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +#### 7.1.80.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.72 | + +### 7.1.80.2 Downlink + +#### 7.1.80.2.1 Transport channel parameters + +##### 7.1.80.2.1.1 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.2.1.1 of [1]. + +##### 7.1.80.2.1.2 Transport channel parameters for Interactive or Background / DL:8 + DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.2.1.1 of [1] + +##### 7.1.80.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.80.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (64 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 7.1.80.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of Pilot bits/slot | +| | | 8 | +| | | Number of data bits/slot | +| | | 140 | +| | | Number of data bits/frame | +| | | 2100 | + +## 7.1.81 Streaming / unknown / UL:8 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +## 7.1.81.1 Uplink + +## 7.1.81.1.1 Transport channel parameters + +## 7.1.81.1.1.1 Transport channel parameters for Streaming / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Uplink: Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 7.1.81.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +## 7.1.81.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.81.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 7.1.81.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +## 7.1.81.2 Downlink + +## 7.1.81.2.1 Transport channel parameters + +## 7.1.81.2.1.1 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2028 | +| | RM attribute | | 125-165 | + +## 7.1.81.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +## 7.1.81.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.81.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (16 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 7.1.81.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | | 4 | +| | | Number of Pilot bits/slot | +| | | 8 | +| | DPDCH | Number of data bits/slot | +| | | 60 | +| | Number of data bits/frame | 900 | + +## 7.1.82 Streaming / unknown / UL:8 DL:32 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +## 7.1.82.1 Uplink + +## 7.1.82.1.1 Transport channel parameters + +## 7.1.82.1.1.1 Transport channel parameters for Streaming / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Uplink: Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 7.1.82.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +## 7.1.82.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.82.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 7.1.82.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +## 7.1.82.2 Downlink + +## 7.1.82.2.1 Transport channel parameters + +## 7.1.82.2.1.1 Transport channel parameters for Streaming / unknown / DL:32 kbps / PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 32000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 4044 | +| | RM attribute | | 125-165 | + +## 7.1.82.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +## 7.1.82.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.82.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (32 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +## 7.1.82.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of data bits/slot | +| | | 140 | +| | | Number of data bits/frame | +| | | 2100 | + +## 7.1.83 Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. + +This is supported in Release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +## 7.1.83.1 Uplink + +## 7.1.83.1.1 Transport channel parameters + +## 7.1.83.1.1.1 Transport channel parameters for Streaming / unknown / UL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 32000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | | TF2, bits | 2x336 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2124 | +| | Uplink: Max number of bits/radio frame before rate matching | | 1062 | +| | RM attribute | | 135-175 | + +## 7.1.83.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1] + +## 7.1.83.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.83.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (32 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=

(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0),
(TF0, TF1, TF0), (TF1, TF1, TF0), (TF2, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1),
(TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1) | + +## 7.1.83.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1.0 | + +## 7.1.83.2 Downlink + +## 7.1.83.2.1 Transport channel parameters + +## 7.1.83.2.1.1 Transport channel parameters for Streaming / unknown / DL:256 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 256000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 10 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | RM attribute | | 125-165 | + +## 7.1.83.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +## 7.1.83.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.83.2.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (256 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=

(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1), | + +### 7.1.83.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +### 7.1.84 Interactive or background / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +#### 7.1.84.1 Uplink + +##### 7.1.84.1.1 Transport channel parameters + +###### 7.1.84.1.1.1 Transport channel parameters for Interactive or Background / UL:16 + UL:16 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-------------------------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 16000 | 16000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | TTI, ms | | 40 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 2148 | | +| | Uplink: Max number of bits/radio frame before rate matching | | 537 | | +| | RM attribute | | 135-175 | | + +###### 7.1.84.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.84.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (16 kbps RAB + 16 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1), (TF1, TF1), (TF2, TF1) | + +## 7.1.84.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1.0 | + +## 7.1.84.2 Downlink + +## 7.1.84.2.1 Transport channel parameters + +## 7.1.84.2.1.1 Transport channel parameters for Interactive or background / DL:16 + DL:16 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|-------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 16000 | 16000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | TTI, ms | | 40 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 2148 | | +| | RM attribute | | 135-175 | | + +## 7.1.84.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.84.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (16 kbps RAB + 16 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1), (TF1, TF1), (TF2, TF1) | + +### 7.1.84.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +### 7.1.85 Interactive or background / UL:64 DL:8 kbps / PS RAB + Interactive or Background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +#### 7.1.85.1 Uplink + +See subclause 6.10.2.4.1.57.1 of [1]. + +#### 7.1.85.2 Downlink + +See subclause 7.1.71.2. + +### 7.1.86 Interactive or Background / UL:64 DL:128 kbps / PS RAB + Interactive or Background / UL:64 DL:128 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 128kbps. + +This is supported in Release '99. + +#### 7.1.86.1 Uplink + +See subclause 6.10.2.4.1.57.1 of [1] + +## 7.1.86.2 Downlink + +## 7.1.86.2.1 Transport channel parameters + +## 7.1.86.2.1.1 Transport channel parameters for Interactive or background / DL:128 + DL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|--------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 128000 | 128000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 8556 | | +| | RM attribute | | 120-160 | | + +## 7.1.86.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.86.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF3,TF0), (TF4,TF0),
(TF0,TF1), (TF1,TF1), (TF2,TF1), (TF3,TF1), (TF4,TF1) | + +## 7.1.86.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | +| | | | | + +## 7.1.87 Interactive or Background / UL:64 DL:384 kbps / PS RAB + Interactive or Background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. + +This is supported in Release '99. + +### 7.1.87.1 Uplink + +See subclause 6.10.2.4.1.57.1 of [1]. + +### 7.1.87.2 Downlink + +#### 7.1.87.2.1 Transport channel parameters + +##### 7.1.87.2.1.1 Transport channel parameters for Interactive or background / DL:384 + DL:384 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|--------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 384000 | 384000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | | TF5, bits | 12x340 | | +| | TTI, ms | | 10 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 12828 | | +| | RM attribute | | 110-150 | | + +##### 7.1.87.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.87.2.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (384 kbps RAB + 384 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0), (TF5, TF0)
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1), (TF5, TF1) | + +#### 7.1.87.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +## 7.1.88 Interactive or background / UL:128 DL:128 kbps / PS RAB + Interactive or Background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 128kbps. + +This is supported in Release '99. + +### 7.1.88.1 Uplink + +#### 7.1.88.1.1 Transport channel parameters + +##### 7.1.88.1.1.1 Transport channel parameters for Interactive or Background / UL:128 + UL:128 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-------------------------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 128000 | 128000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 8556 | | +| | Uplink: Max number of bits/radio frame before rate matching | | 4278 | | +| | RM attribute | | 120-160 | | + +##### 7.1.88.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +##### 7.1.88.1.1.3 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +## 7.1.88.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.96 | + +## 7.1.88.2 Downlink + +## 7.1.88.2.1 Transport channel parameters + +## 7.1.88.2.1.1 Transport channel parameters for Interactive or background / DL:128 + DL:128 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 128000 | 128000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 8556 | | +| | RM attribute | | 120-160 | | + +## 7.1.88.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.88.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF3,TF0), (TF4,TF0),
(TF0,TF1), (TF1,TF1), (TF2,TF1), (TF3,TF1), (TF4,TF1) | + +## 7.1.88.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 16 | +| DPCCH | Number of TFCI bits/slot | 8 | +| | Number of TPC bits/slot | 8 | +| | Number of Pilot bits/slot | 16 | +| DPDCH | Number of data bits/slot | 288 | +| | Number of data bits/frame | 4320 | + +## 7.1.89 Interactive or background / UL:128 DL:32 kbps / PS RAB + Interactive or Background / UL:128 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 32kbps. + +This is supported in Release '99. + +### 7.1.89.1 Uplink + +See subclause 7.1.88.1 + +### 7.1.89.2 Downlink + +#### 7.1.89.2.1 Transport channel parameters + +##### 7.1.89.2.1.1 Transport channel parameters for Interactive or background / DL:32 + DL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 32000 | 32000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 3x340 | | +| | | TF4, bits | 4x340 | | +| | TTI, ms | | 40 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 4284 | | +| | RM attribute | | 135-175 | | + +##### 7.1.89.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +##### 7.1.89.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (32 kbps RAB + 32 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0)
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +### 7.1.89.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +### 7.1.90 Streaming / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +#### 7.1.90.1 Uplink + +See subclause 6.10.2.4.1.58.1 of [1]. + +#### 7.1.90.2 Downlink + +See subclause 7.1.81.2. + +### 7.1.91 Streaming / unknown / UL:16 DL:32 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +#### 7.1.91.1 Uplink + +See subclause 6.10.2.4.1.58.1 of [1]. + +#### 7.1.91.2 Downlink + +See subclause 7.1.82.2. + +### 7.1.92 Interactive or background / UL:16 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +#### 7.1.92.1 Uplink + +See subclause 6.10.2.4.1.23b.1 of [1]. + +#### 7.1.92.2 Downlink + +See subclause 7.1.26.2. + +## 7.1.93 Interactive or background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.93.1 Uplink + +See subclause 6.10.2.4.1.23b.1 of [1]. + +### 7.1.93.2 Downlink + +See subclause 7.1.29.2. + +## 7.1.94 Interactive or background / UL:16 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +### 7.1.94.1 Uplink + +See subclause 6.10.2.4.1.23b.1 of [1]. + +### 7.1.94.2 Downlink + +See subclause 7.1.31.2. + +## 7.1.95 Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +### 7.1.95.1 Uplink + +#### 7.1.95.1.1 Transport channel parameters + +##### 7.1.95.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +##### 7.1.95.1.1.2 Transport channel parameters for Streaming / unknown / UL:16 kbps + +See subclause 6.10.2.4.1.58.1.1.1 of [1]. + +##### 7.1.95.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +##### 7.1.95.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.95.1.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1) | + +## 7.1.95.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1.0 | + +## 7.1.95.2 Downlink + +## 7.1.95.2.1 Transport channel parameters + +## 7.1.95.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1] + +## 7.1.95.2.1.2 Transport channel parameters for Streaming / unknown / DL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.58a.2.1.1 of [1]. + +## 7.1.95.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +## 7.1.95.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.95.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 60 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF1,TF4,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF1,TF4,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF1,TF4,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF1,TF4,TF1,TF1) | + +## 7.1.95.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +## 7.1.96 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps, DL: 64 kbps. + +This is supported in release '99. + +## 7.1.96.1 Uplink + +## 7.1.96.1.1 Transport channel parameters + +## 7.1.96.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1] + +## 7.1.96.1.1.2 Transport channel parameters for Streaming / unknown / UL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 128000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 4x656 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 4038 | +| | RM attribute | | 125-165 | + +## 7.1.96.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +## 7.1.96.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.96.1.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1) | + +## 7.1.96.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.92 | + +## 7.1.96.2 Downlink + +## 7.1.96.2.1 Transport channel parameters + +## 7.1.96.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1] + +## 7.1.96.2.1.2 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +See subclause 7.1.81.2.1.1 + +## 7.1.96.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +## 7.1.96.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.96.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1) | + +## 7.1.96.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.1.97 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62 of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps plus support for 'Maximum number of TFC' = 32. + +This is supported in Release 5. + +## 7.1.98 Interactive or background / UL:32 DL:64 kbps / PS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH (L1 multiplexing) (FDD) + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +## 7.1.98.1 Uplink + +## 7.1.98.1.1 Transport channel parameters + +## 7.1.98.1.1.1 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23.1.1.1 of [1]. + +## 7.1.98.1.1.2 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23.1.1.1 of [1]. + +## 7.1.98.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.98.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 (alt. 8) | +| TFCS | (I/B 32 kbps RAB, I/B 32 kbps RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF0, TF2, TF0), (TF1, TF2, TF0), (TF2, TF2, TF0), (TF0, TF0, TF1),
(TF1, TF0, TF1), (TF2, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2, TF1)

(alt. (TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0), (TF0, TF0, TF1),
(TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1)) | + +### 7.1.98.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +### 7.1.98.2 Downlink + +#### 7.1.98.2.1 Transport channel parameters + +##### 7.1.98.2.1.1 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1]. + +##### 7.1.98.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1]. + +##### 7.1.98.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.98.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (I/B 64 kbps RAB, I/B 64 kbps RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF0, TF1, TF0), (TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0),
(TF0, TF2, TF0), (TF1, TF2, TF0), (TF2, TF2, TF0), (TF3, TF2, TF0), (TF4, TF2, TF0),
(TF0, TF3, TF0), (TF1, TF3, TF0), (TF2, TF3, TF0), (TF3, TF3, TF0), (TF4, TF3, TF0),
(TF0, TF4, TF0), (TF1, TF4, TF0), (TF2, TF4, TF0), (TF3, TF4, TF0), (TF4, TF4, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1),
(TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2, TF1), (TF3, TF2, TF1), (TF4, TF2, TF1),
(TF0, TF3, TF1), (TF1, TF3, TF1), (TF2, TF3, TF1), (TF3, TF3, TF1), (TF4, TF3, TF1),
(TF0, TF4, TF1), (TF1, TF4, TF1), (TF2, TF4, TF1), (TF3, TF4, TF1), (TF4, TF4, TF1) | + +#### 7.1.98.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 16 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of Pilot bits/slot | +| | | 16 | +| | DPDCH | Number of data bits/slot | +| | | 288 | +| | Number of data bits/frame | 4320 | + +### 7.1.99 Interactive or background / UL:128 DL: 64k / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 64kbps. + +#### 7.1.99.1 Uplink + +##### 7.1.99.1.1 Transport channel parameters + +##### 7.1.99.1.1.1 Transport channel parameters for Interactive or background / UL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.28.1.1.1 of [1] + +7.1.99.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1. of [1] + +7.1.99.1.1.3 TFCS + +See subclause 6.10.2.4.1.28.1.1.3 of [1] + +7.1.99.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.28.1.2 of [1] + +7.1.99.2 Downlink + +7.1.99.2.1 Transport channel parameters + +7.1.99.2.1.1 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1] + +7.1.99.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1] + +7.1.99.2.1.3 TFCS + +See subclause 6.10.2.4.1.25.2.1.3 of [1]. + +7.1.99.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +## 7.1.100 Interactive or background / UL:384 DL: 64k / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 64kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +7.1.100.1 Uplink + +7.1.100.1.1 Transport channel parameters + +7.1.100.1.1.1 Transport channel parameters for Interactive or background / UL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.34.1.1.1 of [1] + +7.1.100.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +7.1.100.1.1.3 TFCS + +See subclause 6.10.2.4.1.34.1.1.3 of [1] + +7.1.100.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.34.1.2 of [1] + +## 7.1.100.2 Downlink + +### 7.1.100.2.1 Transport channel parameters + +#### 7.1.100.2.1.1 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1] + +#### 7.1.100.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1] + +#### 7.1.100.2.1.3 TFCS + +See subclause 6.10.2.4.1.25.2.1.3 of [1]. + +### 7.1.100.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +## 7.1.101 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 64kbps. + +### 7.1.101.1 Uplink + +#### 7.1.101.1.1 Transport channel parameters + +##### 7.1.101.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +##### 7.1.101.1.1.2 Transport channel parameters for Interactive or background / UL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.28.1.1.1 of [1]. + +##### 7.1.101.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.101.1.1.4 TFCS + +See subclause 6.10.2.4.1.44.1.1.4 of [1] + +#### 7.1.101.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.44.1.2 of [1] + +### 7.1.101.2 Downlink + +#### 7.1.101.2.1 Transport channel parameters + +##### 7.1.101.2.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +7.1.101.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1] + +7.1.101.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +7.1.101.2.1.4 TFCS + +See subclause 6.10.2.4.1.39.2.1.4 of [1]. + +7.1.101.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|------| +| DPCH
Downlink | DTX position | Flexible or fixed | | +| | Spreading factor | 32 | | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +## 7.1.102 Interactive or background / UL:384 DL: 128kbps / PS RAB + UL:3.4 DL:3.4 kb/s Signalling Radio Bearers for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 128kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +7.1.102.1 Uplink + +7.1.102.1.1 Transport channel parameters + +7.1.102.1.1.1 Transport channel parameters for Interactive or background / UL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.34.1.1.1 of [1]. + +7.1.102.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.102.1.1.3 TFCS + +See subclause 6.10.2.4.1.34.1.1.3 of [1]. + +7.1.102.1.2 Physical channel parameters + +See subclause 6.10.2.4.1.34.1.2 of [1]. + +7.1.102.2 Downlink + +7.1.102.2.1 Transport channel parameters + +7.1.102.2.1.1 Transport channel parameters for Interactive or background / DL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.27.2.1.1 of [1]. + +7.1.102.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1]. + +7.1.102.2.1.3 TFCS + +See subclause 6.10.2.4.1.27.2.1.3 of [1]. + +### 7.1.102.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +### 7.1.103 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 64kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 64kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +#### 7.1.103.1 Uplink + +##### 7.1.103.1.1 Transport channel parameters + +###### 7.1.103.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1. of [1]. + +###### 7.1.103.1.1.2 Transport channel parameters for Interactive or background / UL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.34.1.1.1 of [1]. + +###### 7.1.103.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.103.1.1.4 TFCS + +See subclause 6.10.2.4.5.3.1.1.4 of [1]. + +##### 7.1.103.1.2 Physical channel parameters + +See subclause 6.10.2.4.5.3.1.2 of [1]. + +#### 7.1.103.2 Downlink + +##### 7.1.103.2.1 Transport channel parameters + +###### 7.1.103.2.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +###### 7.1.103.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1]. + +###### 7.1.103.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.1.103.2.1.3 TFCS + +See subclause 6.10.2.4.1.39.2.1.4 of [1]. + +### 7.1.103.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +### 7.1.104 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 128kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 128kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +#### 7.1.104.1 Uplink + +##### 7.1.104.1.1 Transport channel parameters + +###### 7.1.104.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +###### 7.1.104.1.1.1 Transport channel parameters for Interactive or background / UL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.34.1.1.1 of [1]. + +###### 7.1.104.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.104.1.1.3 TFCS + +See subclause 6.10.2.4.5.3.1.1.4 of [1]. + +##### 7.1.104.1.2 Physical channel parameters + +See subclause 6.10.2.4.5.3.1.2 of [1]. + +#### 7.1.104.2 Downlink + +##### 7.1.104.2.1 Transport channel parameters + +###### 7.1.104.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +###### 7.1.104.2.1.2 Transport channel parameters for Interactive or background / DL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.27.2.1.1 of [1]. + +###### 7.1.104.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1]. + +###### 7.1.104.2.1.4 TFCS + +See subclause 6.10.2.4.1.41.2.1.4 of [1]. + +### 7.1.104.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +### 7.1.105 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL: 384kbps / PS RAB + UL:3.4 DL:3.4 kbps Signalling Radio Bearers for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps, DL: 384kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +#### 7.1.105.1 Uplink + +##### 7.1.105.1.1 Transport channel parameters + +###### 7.1.105.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +###### 7.1.105.1.1.2 Transport channel parameters for Interactive or background / UL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.34.1.1.1 of [1]. + +###### 7.1.105.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.105.1.1.3 TFCS + +See subclause 6.10.2.4.5.3.1.1.4 of [1]. + +##### 7.1.105.1.2 Physical channel parameters + +See subclause 6.10.2.4.5.3.1.2 of [1]. + +#### 7.1.105.2 Downlink + +##### 7.1.105.2.1 Transport channel parameters + +###### 7.1.105.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +###### 7.1.105.2.1.2 Transport channel parameters for Interactive or background / DL:384 kbps / PS RAB + +See subclause 6.10.2.4.1.32.2.1.1 of [1]. + +###### 7.1.105.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1. of [1]. + +###### 7.1.105.2.1.4 TFCS + +See subclause 6.10.2.4.1.43.2.1.4. of [1]. + +### 7.1.105.2.2 Physical channel parameters + +| | | | +|---------------|---------------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 8 | +| | Number of DPDCH | 1 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of Pilot bits/slot | +| | | 16 | +| | DPDCH | Number of data bits/slot | +| | | 608 | +| | Number of data bits/frame | 9120 | + +### 7.1.106 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release 5. + +#### 7.1.106.1 Uplink + +##### 7.1.106.1.1 Transport channel parameters + +###### 7.1.106.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.106.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.106.1.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1) | + +##### 7.1.106.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +#### 7.1.106.2 Downlink + +##### 7.1.106.2.1 Transport channel parameters + +###### 7.1.106.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.106.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.106.2.1.3 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0),(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1) | + +## 7.1.106.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Fixed | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | 0 | +| | | Number of TPC bits/slot | +| | DPDCH | 2 | +| | | Number of Pilot bits/slot | +| | | 4 | +| | | Number of data bits/slot | +| | | 34 | +| | | Number of data bits/frame | +| | | 510 | + +## 7.1.107 Conversational / speech / UL:(15.85 12.65 8.85 6.6) DL:(15.85 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 32 kbps, DL: 32 kbps. + +This is supported in Release 5. + +## 7.1.107.1 Uplink + +## 7.1.107.1.1 Transport channel parameters + +## 7.1.107.1.1.1 Transport channel parameters for Conversational / speech / UL: (15.85 12.65 8.85 6.6) kbps / CS RAB + +| Higher Layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3
(note 2) | +|--------------|----------------------|-----------|--------------------------------------------|-------------------|----------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 40, 54, 64, 72
(alt. 0, 40, 54, 64, 72) | 78, 113, 181, 245 | 60 | +| | Max data rate, bps | | 15 850 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 40, 54, 64, 72
(alt. 0, 40, 54, 64, 72) | 78, 113, 181, 245 | 60 | +| | TFS | TF0, bits | 0x72(alt. 1x0) (note) | 0x245 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2 bits | 1x54 | 1x113 | N/A | +| | | TF3, bits | 1x64 | 1x181 | N/A | +| | | TF4, bits | 1x72 | 1x245 | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|---------|---------|-----| +| | Max number of bits/TTI after channel coding | 276 | 759 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | 138 | 380 | 0 | +| | RM attribute | 180-220 | 170-210 | 256 | +| NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). | | | | | +| NOTE 2: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned. | | | | | + +#### 7.1.107.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 7.1.107.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF4,TF4,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1),
(TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF4,TF4,TF0,TF1) | + +#### 7.1.107.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.76 | + +## 7.1.107.2 Downlink + +## 7.1.107.2.1 Transport channel parameters + +## 7.1.107.2.1.1 Transport channel parameters for Conversational / speech / DL: (15.85 12.65 8.85 6.6) kbps / CS RAB + +| Higher Layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3
(note 3) | +|--------------|---------------------------------------------|-----------|-------------------|-------------------|----------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 40, 54, 64, 72 | 78, 113, 181, 245 | 60 | +| | Max data rate, bps | | 15 850 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 40, 54, 64, 72 | 78, 113, 181, 245 | 60 | +| | TFS
(note 1) | TF0, bits | 1x0 (note 2) | 0x245 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2, bits | 1x54 | 1x113 | N/A | +| | | TF3, bits | 1x64 | 1x181 | N/A | +| | | TF4, bits | 1x72 | 1x245 | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 276 | 759 | 0 | +| | RM attribute | | 180-220 | 170-210 | 256 | + +NOTE 1: The TrCH corresponding to RAB subflow #1 should be used as the guiding TrCH, (see subclause 4.3 in TS 25.212). + +NOTE 2: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 3: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned. + +## 7.1.107.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.107.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF4,TF4,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1),
(TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF4,TF4,TF0,TF1) | + +### 7.1.107.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------| +| DPCH Downlink | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 34 | +| | | Number of data bits/frame | 510 | + +### 7.1.108 Conversational / speech / UL:(23.85 12.65 8.85 6.6) DL:(23.85 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 32 kbps, DL: 32 kbps. + +This is supported in Release 5. + +#### 7.1.108.1 Uplink + +##### 7.1.108.1.1 Transport channel parameters + +###### 7.1.108.1.1.1 Transport channel parameters for Conversational / speech / UL: (23.85 12.65 8.85 6.6) kbps / CS RAB + +| Higher Layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3 (note 2) | +|--------------|-------------------------------------------------------------|-----------|--------------------------------------------|-------------------|-------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 40, 54, 64, 72
(alt. 0, 40, 54, 64, 72) | 78, 113, 181, 405 | 60 | +| | Max data rate, bps | | 23 850 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 40, 54, 64, 72
(alt. 0, 40, 54, 64, 72) | 78, 113, 181, 405 | 60 | +| | TFS | TF0, bits | 0x72(alt. 1x0) (note) | 0x405 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2 bits | 1x54 | 1x113 | N/A | +| | | TF3, bits | 1x64 | 1x181 | N/A | +| | | TF4, bits | 1x72 | 1x405 | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 276 | 1239 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 138 | 620 | 0 | +| | RM attribute | | 180-220 | 170-210 | 256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). +NOTE 2: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned. + +###### 7.1.108.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.108.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF4,TF4,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1),
(TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF4,TF4,TF0,TF1) | + +## 7.1.108.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +## 7.1.108.2 Downlink + +## 7.1.108.2.1 Transport channel parameters + +## 7.1.108.2.1.1 Transport channel parameters for Conversational / speech / DL: (23.85 12.65 8.85 6.6) kbps / CS RAB + +| Higher Layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3
(note 3) | +|--------------|---------------------------------------------|-----------|-------------------|-------------------|----------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 40, 54, 64, 72 | 78, 113, 181, 405 | 60 | +| | Max data rate, bps | | 23 850 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 40, 54, 64, 72 | 78, 113, 181, 405 | 60 | +| | TFS
(note 1) | TF0, bits | 1x0 (note 2) | 0x405 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2, bits | 1x54 | 1x113 | N/A | +| | | TF3, bits | 1x64 | 1x181 | N/A | +| | | TF4, bits | 1x72 | 1x405 | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 276 | 1239 | 0 | +| | RM attribute | | 180-220 | 170-210 | 256 | + +NOTE 1: The TrCH corresponding to RAB subflow #1 should be used as the guiding TrCH, (see subclause 4.3 in TS 25.212). + +NOTE 2: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 3: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned. + +## 7.1.108.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.108.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF4,TF4,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1),
(TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF4,TF4,TF0,TF1) | + +## 7.1.108.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|--------------------------| +| DPCH
Downlink | DTX position | Fixed | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | 0 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of data bits/slot | +| | Number of data bits/frame | 900 | + +**7.1.109 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH** + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL: 64 kbps plus support for 'Maximum number of TFC' = 128. + +This is supported in Release 5. + +## 7.1.109.1 Uplink + +## 7.1.109.1.1 Transport channel parameters + +## 7.1.109.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +## 7.1.109.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.26.1.1.1 of [1]. + +## 7.1.109.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.109.1.1.4 + +TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1), (TF0, TF0, TF0, TF2, TF0),
(TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0), (TF3, TF2, TF0, TF2, TF0),
(TF4, TF3, TF0, TF2, TF0), (TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1),
(TF2, TF1, TF0, TF2, TF1), (TF3, TF2, TF0, TF2, TF1), (TF4, TF3, TF0, TF2, TF1),
(TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF0, TF3, TF0),
(TF3, TF2, TF0, TF3, TF0), (TF4, TF3, TF0, TF3, TF0), (TF0, TF0, TF0, TF3, TF1),
(TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF0, TF3, TF1), (TF3, TF2, TF0, TF3, TF1),
(TF4, TF3, TF0, TF3, TF1), (TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0),
(TF2, TF1, TF0, TF4, TF0), (TF3, TF2, TF0, TF4, TF0), (TF4, TF3, TF0, TF4, TF0),
(TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF0, TF4, TF1),
(TF3, TF2, TF0, TF4, TF1), (TF4, TF3, TF0, TF4, TF1) | + +### 7.1.109.1.1.5 + +## TFC subset list + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1)},

2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)} | + +| | | +|--|------------------------------------------------| +| | {(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1)} | +|--|------------------------------------------------| + +#### 7.1.109.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.76 | + +#### 7.1.109.2 Downlink + +##### 7.1.109.2.1 Transport channel parameters + +###### 7.1.109.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +###### 7.1.109.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1]. + +###### 7.1.109.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.1.109.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.109.2.1.5 + +## TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 | +| TFCS | ((RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH, DCCH 0.15)= (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0), (TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0), (TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0), (TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0), (TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0), (TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0), (TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0), (TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0), (TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1), (TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1), (TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1), (TF4,TF3,TF0,TF4,TF1,TF1) | + +## 7.1.109.2.2 + +## Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|----------| +| DPCH Downlink | DTX position | | Flexible | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +7.1.110 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL: 128 kbps plus support for 'Maximum number of TFC' = 128. + +This is supported in Release 5. + +### 7.1.110.1 Uplink + +#### 7.1.110.1.1 Transport channel parameters + +##### 7.1.110.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +##### 7.1.110.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.26.1.1.1 of [1]. + +##### 7.1.110.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.110.1.1.4 TFCS + +See subclause 7.1.109.1.1.4. + +##### 7.1.110.1.1.5 TFC subset list + +See subclause 7.1.109.1.1.5. + +#### 7.1.110.1.2 Physical channel parameters + +See subclause 7.1.109.1.2. + +### 7.1.110.2 Downlink + +#### 7.1.110.2.1 Transport channel parameters + +##### 7.1.110.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +##### 7.1.110.2.1.2 Transport channel parameters for Interactive or background / DL:128 kbps / PS RAB + +See subclause 6.10.2.4.1.27.2.1.1 of [1]. + +##### 7.1.110.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.110.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.110.2.1.5 + +## TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 | +| TFCS | ((RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, DCCH, DCCH 0.15)= (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0), (TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0), (TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0), (TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0), (TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0), (TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0), (TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0), (TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0), (TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1), (TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1), (TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1), (TF4,TF3,TF0,TF4,TF1,TF1) | + +## 7.1.110.2.2 + +## Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|----------| +| DPCH Downlink | DTX position | | Flexible | +| | Spreading factor | | 16 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 288 | +| | | Number of data bits/frame | 4320 | + +7.1.111 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL: 384 kbps. + +This is supported in Release 5. + +## 7.1.111.1 Uplink + +## 7.1.111.1.1 Transport channel parameters + +## 7.1.111.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +## 7.1.111.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.26.1.1.1 of [1]. + +## 7.1.111.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.111.1.1.4 TFCS + +See subclause 7.1.109.1.1.4. + +## 7.1.111.1.1.5 TFC subset list + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list |

0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF0,TF0,TF0,TF5,TF0), (TF1,TF0,TF0,TF5,TF0), (TF2,TF1,TF0,TF5,TF0),
(TF0,TF0,TF0,TF5,TF1), (TF1,TF0,TF0,TF5,TF1), (TF2,TF1,TF0,TF5,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF0,TF0,TF0,TF5,TF0), (TF1,TF0,TF0,TF5,TF0),
(TF2,TF1,TF0,TF5,TF0), (TF3,TF2,TF0,TF5,TF0), (TF0,TF0,TF0,TF5,TF1),
(TF1,TF0,TF0,TF5,TF1), (TF2,TF1,TF0,TF5,TF1), (TF3,TF2,TF0,TF5,TF1)},

2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),

| + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1), (TF0,TF0,TF0,TF5,TF0),
(TF1,TF0,TF0,TF5,TF0), (TF2,TF1,TF0,TF5,TF0), (TF3,TF2,TF0,TF5,TF0),
(TF4,TF3,TF0,TF5,TF0), (TF0,TF0,TF0,TF5,TF1), (TF1,TF0,TF0,TF5,TF1),
(TF2,TF1,TF0,TF5,TF1), (TF3,TF2,TF0,TF5,TF1), (TF4,TF3,TF0,TF5,TF1)} | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.111.1.2 Physical channel parameters + +See subclause 7.1.109.1.2. + +### 7.1.111.2 Downlink + +#### 7.1.111.2.1 Transport channel parameters + +##### 7.1.111.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +##### 7.1.111.2.1.2 Transport channel parameters for Interactive or background / DL:384 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 384 000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | | TF2, bits | 2x336 | +| | | TF3, bits | 4x336 | +| | | TF4, bits | 8x336 | +| | | TF5, bits | 12x336 | +| | TTI, ms | | 10 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 12684 | +| | RM attribute | | 110 to 150 | + +##### 7.1.111.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.111.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.111.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 120 | +| TFCS | ((RAB subflow#1, RAB subflow#2, RAB subflow#3, 384 kbps RAB, DCCH, DCCH 0.15)= (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0), (TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0), (TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0), (TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0), (TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0), (TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0), (TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0), (TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0), (TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF5,TF0,TF0), (TF1,TF0,TF0,TF5,TF0,TF0), (TF2,TF1,TF0,TF5,TF0,TF0), (TF3,TF2,TF0,TF5,TF0,TF0), (TF4,TF3,TF0,TF5,TF0,TF0), (TF0,TF0,TF0,TF5,TF1,TF0), (TF1,TF0,TF0,TF5,TF1,TF0), (TF2,TF1,TF0,TF5,TF1,TF0), (TF3,TF2,TF0,TF5,TF1,TF0), (TF4,TF3,TF0,TF5,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1), (TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1), (TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1), (TF4,TF3,TF0,TF4,TF1,TF1), (TF0,TF0,TF0,TF5,TF0,TF1), (TF1,TF0,TF0,TF5,TF0,TF1), (TF2,TF1,TF0,TF5,TF0,TF1), (TF3,TF2,TF0,TF5,TF0,TF1), (TF4,TF3,TF0,TF5,TF0,TF1), (TF0,TF0,TF0,TF5,TF1,TF1), (TF1,TF0,TF0,TF5,TF1,TF1), (TF2,TF1,TF0,TF5,TF1,TF1), (TF3,TF2,TF0,TF5,TF1,TF1), (TF4,TF3,TF0,TF5,TF1,TF1) | + +## 7.1.111.2.2 + +## Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|----------| +| DPCH Downlink | DTX position | | Flexible | +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +7.1.112 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. + +This is supported in Release 5. + +## 7.1.112.1 Uplink + +## 7.1.112.1.1 Transport channel parameters + +## 7.1.112.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +## 7.1.112.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +## 7.1.112.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.112.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1) | + +## 7.1.112.1.1.5 TFC subset list + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1)},
1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1)},
2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1)} | + +## 7.1.112.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.64 | + +## 7.1.112.2 Downlink + +## 7.1.112.2.1 Transport channel parameters + +## 7.1.112.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +7.1.112.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1 of [1]. + +7.1.112.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.112.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +7.1.112.2.1.5 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0 kbps RAB, DCCH 3.4, DCCH 0.15)=
(TF0, TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1, TF0),
(TF1, TF0, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF0, TF1, TF0), (TF3, TF2, TF0, TF0, TF1, TF0),
(TF4, TF3, TF0, TF0, TF1, TF0), (TF0, TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF0, TF1),
(TF2, TF1, TF0, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF0, TF1), (TF4, TF3, TF0, TF0, TF0, TF1),
(TF0, TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF0, TF1, TF1),
(TF3, TF2, TF0, TF0, TF1, TF1), (TF4, TF3, TF0, TF0, TF1, TF1) | + +7.1.112.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.62.2.2 of [1]. + +**7.1.113 Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +7.1.113.1 Uplink + +See subclause 7.1.95.1 + +7.1.113.2 Downlink + +7.1.113.2.1 Transport channel parameters + +7.1.113.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1] + +7.1.113.2.1.2 Transport channel parameters for Streaming / unknown / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.58.2.1.1 of [1]. + +7.1.113.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +7.1.113.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.113.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1) | + +## 7.1.113.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +### 7.1.113a Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:64 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 64, DL: 64 kbps. + +This is supported in release '99. + +## 7.1.113a.1 Uplink + +## 7.1.113a.1.1 Transport channel parameters + +## 7.1.113a.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1] + +## 7.1.113a.1.1.2 Transport channel parameters for Streaming / unknown / UL:64 kbps / PS RAB + +See subclause 7.4.15.1.1.1 + +## 7.1.113a.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +#### 7.1.113a.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 7.1.113a.1.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 60 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF1,TF4,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF1,TF4,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF1,TF4,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF1,TF4,TF1,TF1) | + +#### 7.1.113a.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.64 | + +#### 7.1.113a.2 Downlink + +See subclause 7.1.96.2. + +### 7.1.114 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Maximum number of TFC' = 48, DL: 128 kbps plus support for 'Maximum total number of transport blocks received within TTIs that end within the same 10 ms interval' = 16 and 'Maximum number of physical channel bits received in any 10 ms interval (DPCH, S-CCPCH)' = 9600. + +This is supported in release '99. + +NOTE: This RAB combination is also applicable for Streaming MBMS PTP. + +#### 7.1.114.1 Uplink + +##### 7.1.114.1.1 Transport channel parameters + +###### 7.1.114.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +7.1.114.1.1.2 Transport channel parameters for Streaming / unknown / UL:32 kbps / PS RAB + +See subclause 7.1.83.1.1.1 + +7.1.114.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +7.1.114.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.114.1.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1) | + +7.1.114.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +7.1.114.2 Downlink + +7.1.114.2.1 Transport channel parameters + +7.1.114.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1] + +7.1.114.2.1.2 Transport channel parameters for Streaming / unknown / DL:256 kbps / PS RAB + +See subclause 7.1.83.2.1.1 + +7.1.114.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1] + +7.1.114.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.114.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 60 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 256 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF1,TF4,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF1,TF4,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF1,TF4,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF1,TF4,TF1,TF1) | + +## 7.1.114.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|------------------|---------------------------|-------------------| +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 608 | +| | | Number of data bits/frame | 9120 | + +## 7.1.115 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release'99. + +### 7.1.115.1 Uplink + +#### 7.1.115.1.1 Transport channel parameters + +##### 7.1.115.1.1.1 Transport channel parameters for Conversational / speech / UL:5.9 kbps / CS RAB + +See subclause 6.10.2.4.1.9.1.1.1 of [1]. + +##### 7.1.115.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.26.1.1.1 of [1]. + +##### 7.1.115.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.115.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0),
(TF0, TF0, TF0, TF2, TF0), (TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0),
(TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF0, TF3, TF0),
(TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0), (TF2, TF1, TF0, TF4, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1), (TF2, TF1, TF0, TF2, TF1),
(TF0, TF0, TF0, TF3, TF1), (TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF0, TF3, TF1),
(TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF0, TF4, TF1) | + +## 7.1.115.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.84 | + +## 7.1.115.2 Downlink + +## 7.1.115.2.1 Transport channel parameters + +## 7.1.115.2.1.1 Transport channel parameters for Conversational / speech / DL: 5.9 kbps / CS RAB + +See subclause 6.10.2.4.1.9.2.1.1 of [1]. + +## 7.1.115.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.25.2.1.1 of [1]. + +## 7.1.115.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.115.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB , DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0),
(TF0, TF0, TF0, TF2, TF0), (TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0),
(TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF0, TF3, TF0),
(TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0), (TF2, TF1, TF0, TF4, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1), (TF2, TF1, TF0, TF2, TF1),
(TF0, TF0, TF0, TF3, TF1), (TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF0, TF3, TF1),
(TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF0, TF4, TF1) | + +## 7.1.115.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +### 7.1.116 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps plus support for 'Maximum number of AM entities' = 5, DL: 64kbps plus support for 'Maximum number of AM entities' = 5. + +This is supported in Release '99. + +#### 7.1.116.1 Uplink + +##### 7.1.116.1.1 Transport channel parameters + +###### 7.1.116.1.1.1 Transport channel parameters for Conversational / speech / UL:5.9 kbps / CS RAB + +See subclause 6.10.2.4.1.9.1.1.1 of [1]. + +###### 7.1.116.1.1.2 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.38d.1.1.2 of [1]. + +###### 7.1.116.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.116.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB + 64 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0),
(TF0, TF0, TF0, TF2, TF0), (TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0),
(TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF0, TF3, TF0),
(TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0), (TF2, TF1, TF0, TF4, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1), (TF2, TF1, TF0, TF2, TF1),
(TF0, TF0, TF0, TF3, TF1), (TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF0, TF3, TF1),
(TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF0, TF4, TF1) | + +##### 7.1.116.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.84 | + +## 7.1.116.2 Downlink + +### 7.1.116.2.1 Transport channel parameters + +#### 7.1.116.2.1.1 Transport channel parameters for Conversational / speech / DL: 5.9 kbps / CS RAB + +See subclause 6.10.2.4.1.9.2.1.1 of [1]. + +#### 7.1.116.2.1.2 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.38d.2.1.2 of [1]. + +#### 7.1.116.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.1.116.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB + 64 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1) | + +### 7.1.116.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|---------------------------|--|-------------------| +| | Spreading factor | | 32 | +| DPCH | Number of TFCI bits/slot | | 8 | +| | Number of TPC bits/slot | | 4 | +| | Number of Pilot bits/slot | | 8 | +| DPDCH | Number of data bits/slot | | 140 | +| | Number of data bits/frame | | 2100 | + +## 7.1.117 Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.4b of [1]. + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 32 kbps. + +This is supported in Release 4. + +## 7.1.118 Conversational / speech / UL:38.8 DL:38.8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-6 onwards] + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 6. + +NOTE: This RAB is used for the transient state, where couple of IR packets are transmitted to synchronize contexts. + +### 7.1.118.1 Uplink + +#### 7.1.118.1.1 Transport channel parameters + +##### 7.1.118.1.1.1 Transport channel parameters for conversational/speech/UL:38.8 kbps/ PS RAB + +| | | | | +|--------------|-------------------------------------------------------------|-----------|-------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 568, 624, 640, 656, 672, 704, 768, 776
(alt 0, 568, 624, 640, 656, 672, 704, 768, 776) | +| | Max data rate, bps | | 38800 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 576, 632, 648, 664, 680, 712, 776, 784
(alt 0, 576, 632, 648, 664, 680, 712, 776, 784) | +| | TFS | TF0, bits | 0x784 (alt 1x0) | +| | | TF1, bits | 1x576 | +| | | TF2, bits | 1x632 | +| | | TF3, bits | 1x648 | +| | | TF4, bits | 1x664 | +| | | TF5, bits | 1x680 | +| | | TF6, bits | 1x712 | +| | | TF7, bits | 1x776 | +| | | TF8, bits | 1x784 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2412 | +| | Uplink: Max number of bits/radio frame before rate matching | | 1206 | +| | RM attribute | | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. + +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB + +7.1.118.1.1.2 Transport channel parameters for interactive or background/UL:8 kbps/ PS RAB + UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.1.1.1 of [1] + +7.1.118.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +7.1.118.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (38.8 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0),
(TF6, TF1, TF0), (TF7, TF1, TF0), (TF8, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1),
(TF7, TF0, TF1), (TF8, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1),
(TF8, TF1, TF1) | + +7.1.118.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +## 7.1.118.2 Downlink + +## 7.1.118.2.1 Transport channel parameters + +## 7.1.118.2.1.1 Transport channel parameters for conversational/speech/DL:38.8 kbps/ PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|-------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 568, 624, 640, 656, 672, 704, 768, 776
(alt 0, 568, 624, 640, 656, 672, 704, 768, 776) | +| | Max data rate, bps | | 38800 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 576, 632, 648, 664, 680, 712, 776, 784
(alt 0, 576, 632, 648, 664, 680, 712, 776, 784) | +| | TFS | TF0, bits | 0x784 (alt 1x0) | +| | | TF1, bits | 1x576 | +| | | TF2, bits | 1x632 | +| | | TF3, bits | 1x648 | +| | | TF4, bits | 1x664 | +| | | TF5, bits | 1x680 | +| | | TF6, bits | 1x712 | +| | | TF7, bits | 1x776 | +| | | TF8, bits | 1x784 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2412 | +| | RM attribute | | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. + +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB + +## 7.1.118.2.1.2 Transport channel parameters for interactive or background/DL:8 kbps/ PS RAB + DL: 8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.2.1.1 of [1] + +## 7.1.118.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1] + +## 7.1.118.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (38.8 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0),
(TF6, TF1, TF0), (TF7, TF1, TF0), (TF8, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1),
(TF7, TF0, TF1), (TF8, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1),
(TF8, TF1, TF1) | + +## 7.1.118.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +### 7.1.119 Conversational / speech / UL:16.8 DL:16.8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH [Rel-6 onwards] + +The minimum UE classes supporting this combination are UL: 32 kbps, DL: 32 kbps plus support for 'Maximum number of TFC' = 96. + +This is supported in Release 6. + +NOTE: This RAB is used for the steady-state, where the contexts of the ROHC compressor and the ROHC decompressor are already synchronized so IR packets are not transmitted. + +## 7.1.119.1 Uplink + +## 7.1.119.1.1 Transport channel parameters + +## 7.1.119.1.1.1 Transport channel parameters for conversational/speech/UL:16.8 kbps/ PS RAB + +| | | | | +|--------------|-----------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 80, 96, 128, 136, 152, 168, 184, 200, 216, 232, 264, 280, 288, 296, 304, 328, 336 (alt 0, 80, 96, 128, 136, 152, 168, 184, 200, 216, 232, 264, 280, 288, 296, 304, 328, 336) | +| | Max data rate, bps | | 16800 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 88, 104, 136, 144, 160, 176, 192, 208, 224, 240, 272, 288, 296, 304, 312, 336, 344 (alt 0, 88, 104, 136, 144, 160, 176, 192, 208, 224, 240, 272, 288, 296, 304, 312, 336, 344) | +| | TFS | TF0, bits | 0x344 (alt 1x0) | +| | | TF1, bits | 1x88 | +| | | TF2, bits | 1x104 | +| | | TF3, bits | 1x136 | +| | | TF4, bits | 1x144 | +| | | TF5, bits | 1x160 | +| | | TF6, bits | 1x176 | +| | | TF7, bits | 1x192 | +| | | TF8, bits | 1x208 | +| | | TF9, bits | 1x224 | +| | | TF10, bits | 1x240 | +| | | TF11, bits | 1x272 | +| | | TF12, bits | 1x288 | +| | | TF13, bits | 1x296 | +| | | TF14, bits | 1x304 | +| | | TF15, bits | 1x312 | +| | | TF16, bits | 1x336 | +| | | TF17, bits | 1x344 | + +| Higher layer | RAB/Signalling RB | RAB | +|--------------|-------------------------------------------------------------|---------| +| PDCP | PDCP header size, bit | 0 | +| | TTI, ms | 20 | +| | Coding type | TC | +| | CRC, bit | 16 | +| | Max number of bits/TTI after channel coding | 1092 | +| | Uplink: Max number of bits/radio frame before rate matching | 546 | +| | RM attribute | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB + +7.1.119.1.1.2 Transport channel parameters for interactive or background/UL:8 kbps/ PS RAB + UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.1.1.1 of [1]. + +7.1.119.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.119.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 72 | +| TFCS | (16.8 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF9, TF0, TF0),
(TF10, TF0, TF0), (TF11, TF0, TF0), (TF12, TF0, TF0), (TF13, TF0, TF0), (TF14, TF0, TF0),
(TF15, TF0, TF0), (TF16, TF0, TF0), (TF17, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0), (TF6, TF1, TF0),
(TF7, TF1, TF0), (TF8, TF1, TF0), (TF9, TF1, TF0), (TF10, TF1, TF0), (TF11, TF1, TF0),
(TF12, TF1, TF0), (TF13, TF1, TF0), (TF14, TF1, TF0), (TF15, TF1, TF0), (TF16, TF1, TF0),
(TF17, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1),
(TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1), (TF7, TF0, TF1), (TF8, TF0, TF1),
(TF9, TF0, TF1), (TF10, TF0, TF1), (TF11, TF0, TF1), (TF12, TF0, TF1), (TF13, TF0, TF1),
(TF14, TF0, TF1), (TF15, TF0, TF1), (TF16, TF0, TF1), (TF17, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1),
(TF6, TF1, TF1), (TF7, TF1, TF1), (TF8, TF1, TF1), (TF9, TF1, TF1), (TF10, TF1, TF1),
(TF11, TF1, TF1), (TF12, TF1, TF1), (TF13, TF1, TF1), (TF14, TF1, TF1), (TF15, TF1, TF1),
(TF16, TF1, TF1), (TF17, TF1, TF1) | + +## 7.1.119.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 0.88 | + +## 7.1.119.2 Downlink + +## 7.1.119.2.1 Transport channel parameters + +## 7.1.119.2.1.1 Transport channel parameters for conversational/speech/DL:16.8 kbps/ PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 80, 96, 128, 136, 152, 168, 184, 200, 216, 232, 264, 280, 288, 296, 304, 328, 336 (alt 0, 80, 96, 128, 136, 152, 168, 184, 200, 216, 232, 264, 280, 288, 296, 304, 328, 336) | +| | Max data rate, bps | | 16800 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 88, 104, 136, 144, 160, 176, 192, 208, 224, 240, 272, 288, 296, 304, 312, 336, 344 (alt 0, 88, 104, 136, 144, 160, 176, 192, 208, 224, 240, 272, 288, 296, 304, 312, 336, 344) | +| | TFS | TF0, bits | 0x344 (alt 1x0) | +| | | TF1, bits | 1x88 | +| | | TF2, bits | 1x104 | +| | | TF3, bits | 1x136 | +| | | TF4, bits | 1x144 | +| | | TF5, bits | 1x160 | +| | | TF6, bits | 1x176 | +| | | TF7, bits | 1x192 | +| | | TF8, bits | 1x208 | +| | | TF9, bits | 1x224 | +| | | TF10, bits | 1x240 | +| | | TF11, bits | 1x272 | +| | | TF12, bits | 1x288 | +| | | TF13, bits | 1x296 | +| | | TF14, bits | 1x304 | +| | | TF15, bits | 1x312 | + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|------------|---------| +| PDCP | PDCP header size, bit | | 0 | +| | | TF16, bits | 1x336 | +| | | TF17, bits | 1x344 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1092 | +| | RM attribute | | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. + +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB + +7.1.119.2.1.2 Transport channel parameters for interactive or background/DL:8 kbps/ PS RAB + DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.2.1.1 of [1]. + +7.1.119.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.119.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 72 | +| TFCS | (16 8 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF9, TF0, TF0),
(TF10, TF0, TF0), (TF11, TF0, TF0), (TF12, TF0, TF0), (TF13, TF0, TF0), (TF14, TF0, TF0),
(TF15, TF0, TF0), (TF16, TF0, TF0), (TF17, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0), (TF6, TF1, TF0),
(TF7, TF1, TF0), (TF8, TF1, TF0), (TF9, TF1, TF0), (TF10, TF1, TF0), (TF11, TF1, TF0),
(TF12, TF1, TF0), (TF13, TF1, TF0), (TF14, TF1, TF0), (TF15, TF1, TF0), (TF16, TF1, TF0),
(TF17, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1),
(TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1), (TF7, TF0, TF1), (TF8, TF0, TF1),
(TF9, TF0, TF1), (TF10, TF0, TF1), (TF11, TF0, TF1), (TF12, TF0, TF1), (TF13, TF0, TF1),
(TF14, TF0, TF1), (TF15, TF0, TF1), (TF16, TF0, TF1), (TF17, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1),
(TF6, TF1, TF1), (TF7, TF1, TF1), (TF8, TF1, TF1), (TF9, TF1, TF1), (TF10, TF1, TF1),
(TF11, TF1, TF1), (TF12, TF1, TF1), (TF13, TF1, TF1), (TF14, TF1, TF1), (TF15, TF1, TF1),
(TF16, TF1, TF1), (TF17, TF1, TF1) | + +## 7.1.119.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +7.1.120 Conversational / speech / UL: 40 DL: 40 kbps / PS RAB + +Interactive or Background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 +kbps SRBs for DCCH [Rel-5 only] + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 5 only. This does not apply to Release 6 onwards. + +NOTE: The first RAB is used for multiplexed RTP and RTCP flows, the second RAB is used for SIP signaling and the third RAB is used for signaling radio bearers. + +## 7.1.120.1 Uplink + +## 7.1.120.1.1 Transport channel parameters + +## 7.1.120.1.1.1 Transport channel parameters for Conversational / speech / UL: 40 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 104, 320, 800 | +| | Max data rate, bps | | 40000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 112, 328, 808 | +| | TFS | TF0, bits | 0x808 | +| | | TF1, bits | 1x112 | +| | | TF2, bits | 1x328 | +| | | TF3, bits | 1x808 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2484 | +| | Uplink: Max number of bits/radio frame before rate matching | | 1242 | +| | RM attribute | | 180-220 | + +## 7.1.120.1.1.2 Transport channel parameters for Interactive or Background / UL: 8 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Uplink: Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 7.1.120.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.120.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (40 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), | + +## 7.1.120.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +## 7.1.120.2 Downlink + +### 7.1.120.2.1 Transport channel parameters + +#### 7.1.120.2.1.1 Transport channel parameters for Conversational / speech / DL: 40 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|---------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 104, 320, 800 | +| | Max data rate, bps | | 40000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 112, 328, 808 | +| | TFS | TF0, bits | 0x808 | +| | | TF1, bits | 1x112 | +| | | TF2, bits | 1x328 | +| | | TF3, bits | 1x808 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2484 | +| | RM attribute | | 180-220 | + +#### 7.1.120.2.1.2 Transport channel parameters for Interactive or Background / DL: 8 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | RM attribute | | 135-175 | + +#### 7.1.120.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.120.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (40 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1) | + +## 7.1.120.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Fixed | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +## 7.1.121 Interactive or background / UL:16 DL:16 kbps / PS RAB + UL:27.2 DL:27.2 kbps SRBs for DCCH + +## 7.1.121.1 Uplink + +## 7.1.121.1.1 Transport channel parameters + +## 7.1.121.1.1.1 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.1.1.1 of [1]. + +## 7.1.121.1.1.2 Transport channel parameters for UL:27.2 kbps SRBs for DCCH + +See subclause 7.1.3a.1.1.1. + +## 7.1.121.1.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (16 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF0,TF1), (TF1,TF1), (TF2,TF1), (TF0,TF2), (TF1,TF2) | + +## 7.1.121.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 0.72 | + +## 7.1.121.2 Downlink + +## 7.1.121.2.1 Transport channel parameters + +## 7.1.121.2.1.1 Transport channel parameters for Interactive or background / DL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.2.1.1 of [1]. + +## 7.1.121.2.1.2 Transport channel parameters for DL:27.2 kbps SRBs for DCCH + +See subclause 7.1.3a.2.1.1. + +## 7.1.121.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (16 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF0,TF1), (TF1,TF1), (TF2,TF1), (TF0,TF2), (TF1,TF2) | + +## 7.1.121.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | +| | | | + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. + +This is supported in Release '99. + +**7.1.122 Conversational / speech / UL:39.6 DL:39.6 kbps / PS RAB + +Interactive or background / UL:8 DL:8 kbps / PS RAB + +Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 +DL:3.4 kbps SRBs for DCCH [Rel-5]** + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 5. This is not applied to Release 6 onwards. + +NOTE: This RAB is used for the transient state, where couple of IR packets are transmitted to synchronize contexts. + +## 7.1.122.1 Uplink + +## 7.1.122.1.1 Transport channel parameters + +## 7.1.122.1.1.1 Transport channel parameters for conversational/speech/UL:39.6 kbps/ PS RAB + +| | | | | +|--------------|-----------------------|-----------|-------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 584, 640, 656, 672, 688, 720, 784, 792
(alt 0, 584, 640, 656, 672, 688, 720, 784, 792) | +| | Max data rate, bps | | 39600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 592, 648, 664, 680, 696, 728, 792, 800
(alt 0, 592, 648, 664, 680, 696, 728, 792, 800) | +| | TFS | TF0, bits | 0x800 (alt 1x0) | +| | | TF1, bits | 1x592 | + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------------|---------| +| PDCP | PDCP header size, bit | | 0 | +| | | TF2, bits | 1x648 | +| | | TF3, bits | 1x664 | +| | | TF4, bits | 1x680 | +| | | TF5, bits | 1x696 | +| | | TF6, bits | 1x728 | +| | | TF7, bits | 1x792 | +| | | TF8, bits | 1x800 | +| | | TTI, ms | 20 | +| | | Coding type | TC | +| | | CRC, bit | 16 | +| | | Max number of bits/TTI after channel coding | 2460 | +| | | Uplink: Max number of bits/radio frame before rate matching | 1230 | +| | | RM attribute | 180-220 | +| NOTE: Alternative 1x0 is used to have CRC present in all transport formats.
Header compressor should ensure that ROHC's small_CID is used and that CID 0 is allocated to this RAB | | | | + +7.1.122.1.1.2 Transport channel parameters for interactive or background/UL:8 kbps/ PS RAB + UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.1.1.1 of [1]. + +7.1.122.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.122.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (396 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0),
(TF6, TF1, TF0), (TF7, TF1, TF0), (TF8, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1),
(TF7, TF0, TF1), (TF8, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1),
(TF8, TF1, TF1) | + +## 7.1.122.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +## 7.1.122.2 Downlink + +## 7.1.122.2.1 Transport channel parameters + +## 7.1.122.2.1.1 Transport channel parameters for conversational/speech/DL:39.6 kbps/ PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|-------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 584, 640, 656, 672, 688, 720, 784, 792
(alt 0, 584, 640, 656, 672, 688, 720, 784, 792) | +| | Max data rate, bps | | 39600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 592, 648, 664, 680, 696, 728, 792, 800
(alt 0, 592, 648, 664, 680, 696, 728, 792, 800) | +| | TFS | TF0, bits | 0x800 (alt 1x0) | +| | | TF1, bits | 1x592 | +| | | TF2, bits | 1x648 | +| | | TF3, bits | 1x664 | +| | | TF4, bits | 1x680 | +| | | TF5, bits | 1x696 | +| | | TF6, bits | 1x728 | +| | | TF7, bits | 1x792 | +| | | TF8, bits | 1x800 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2460 | +| | RM attribute | | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB + +7.1.122.2.1.2 Transport channel parameters for interactive or background/DL:8 kbps/ PS RAB + DL: 8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.2.1.1 of [1]. + +7.1.122.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.122.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (39.6 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0),
(TF6, TF1, TF0), (TF7, TF1, TF0), (TF8, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1),
(TF7, TF0, TF1), (TF8, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1),
(TF8, TF1, TF1) | + +7.1.122.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +7.1.123 Conversational / speech / UL:17.6 DL:17.6 kbps / PS RAB + +Interactive or background / UL:8 DL:8 kbps / PS RAB + +Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 +DL:3.4 kbps SRBs for DCCH [Rel-5] + +The minimum UE classes supporting this combination are UL: 32 kbps, DL: 32 kbps plus support for 'Maximum number of TFC' = 96. + +This is supported in Release 5. This is not applied to Release 6 onwards. + +NOTE: This RAB is used for the steady-state, where the contexts of the ROHC compressor and the ROHC decompressor are already synchronized so IR packets are not transmitted. + +### 7.1.123.1 Uplink + +#### 7.1.123.1.1 Transport channel parameters + +##### 7.1.123.1.1.1 Transport channel parameters for conversational/speech/UL:17.6.8 kbps/ PS RAB + +| | | | | +|--------------|-----------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 96, 112, 144, 152, 168, 184, 200, 216, 232, 248, 280, 296, 304, 312, 320, 344, 352 (alt 0, 96, 112, 144, 152, 168, 184, 200, 216, 232, 248, 280, 296, 304, 312, 320, 344, 352) | +| | Max data rate, bps | | 17600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 104, 120, 152, 160, 176, 192, 208, 224, 240, 256, 288, 304, 312, 320, 328, 352, 360 (alt 0, 104, 120, 152, 160, 176, 192, 208, 224, 240, 256, 288, 304, 312, 320, 328, 352, 360) | +| | TFS | TF0, bits | 0x360 (alt 1x0) | +| | | TF1, bits | 1x104 | +| | | TF2, bits | 1x120 | +| | | TF3, bits | 1x152 | +| | | TF4, bits | 1x160 | +| | | TF5, bits | 1x176 | +| | | TF6, bits | 1x192 | +| | | TF7, bits | 1x208 | +| | | TF8, bits | 1x224 | +| | | TF9, bits | 1x240 | +| | | TF10, bits | 1x256 | +| | | TF11, bits | 1x288 | +| | | TF12, bits | 1x304 | +| | | TF13, bits | 1x312 | +| | | TF14, bits | 1x320 | +| | | TF15, bits | 1x328 | +| | | TF16, bits | 1x352 | +| | | TF17, bits | 1x360 | + +| Higher layer | RAB/Signalling RB | RAB | +|--------------|-------------------------------------------------------------|---------| +| PDCP | PDCP header size, bit | 0 | +| | TTI, ms | 20 | +| | Coding type | TC | +| | CRC, bit | 16 | +| | Max number of bits/TTI after channel coding | 1140 | +| | Uplink: Max number of bits/radio frame before rate matching | 570 | +| | RM attribute | 180-220 | + +NOTE: Alternative 1x0 is used to have CRC present in all transport formats. +Header compressor should ensure that small\_CID is used and that CID 0 is allocated to this RAB. + +7.1.123.1.1.2 Transport channel parameters for interactive or background/UL:8 kbps/ PS RAB + UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.56.1.1.1 of [1]. + +7.1.123.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.123.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 72 | +| TFCS | (17.6 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF9, TF0, TF0),
(TF10, TF0, TF0), (TF11, TF0, TF0), (TF12, TF0, TF0), (TF13, TF0, TF0), (TF14, TF0, TF0),
(TF15, TF0, TF0), (TF16, TF0, TF0), (TF17, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0), (TF6, TF1, TF0),
(TF7, TF1, TF0), (TF8, TF1, TF0), (TF9, TF1, TF0), (TF10, TF1, TF0), (TF11, TF1, TF0),
(TF12, TF1, TF0), (TF13, TF1, TF0), (TF14, TF1, TF0), (TF15, TF1, TF0), (TF16, TF1, TF0),
(TF17, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1),
(TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1), (TF7, TF0, TF1), (TF8, TF0, TF1),
(TF9, TF0, TF1), (TF10, TF0, TF1), (TF11, TF0, TF1), (TF12, TF0, TF1), (TF13, TF0, TF1),
(TF14, TF0, TF1), (TF15, TF0, TF1), (TF16, TF0, TF1), (TF17, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1),
(TF6, TF1, TF1), (TF7, TF1, TF1), (TF8, TF1, TF1), (TF9, TF1, TF1), (TF10, TF1, TF1),
(TF11, TF1, TF1), (TF12, TF1, TF1), (TF13, TF1, TF1), (TF14, TF1, TF1), (TF15, TF1, TF1),
(TF16, TF1, TF1), (TF17, TF1, TF1) | + +## 7.1.123.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 0.84 | + +## 7.1.123.2 Downlink + +## 7.1.123.2.1 Transport channel parameters + +## 7.1.123.2.1.1 Transport channel parameters for conversational/speech/DL:17.6 kbps/ PS RAB + +| | | | | +|--------------|-----------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | | RAB | +| PDCP | PDCP header size, bit | | 0 | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 96, 112, 144, 152, 168, 184, 200, 216, 232, 248, 280, 296, 304, 312, 320, 344, 352 (alt 0, 96, 112, 144, 152, 168, 184, 200, 216, 232, 248, 280, 296, 304, 312, 320, 344, 352) | +| | Max data rate, bps | | 17600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 104, 120, 152, 160, 176, 192, 208, 224, 240, 256, 288, 304, 312, 320, 328, 352, 360 (alt 0, 104, 120, 152, 160, 176, 192, 208, 224, 240, 256, 288, 304, 312, 320, 328, 352, 360) | +| | TFS | TF0, bits | 0x360 (alt 1x0) | +| | | TF1, bits | 1x104 | +| | | TF2, bits | 1x120 | +| | | TF3, bits | 1x152 | +| | | TF4, bits | 1x160 | +| | | TF5, bits | 1x176 | +| | | TF6, bits | 1x192 | +| | | TF7, bits | 1x208 | +| | | TF8, bits | 1x224 | +| | | TF9, bits | 1x240 | +| | | TF10, bits | 1x256 | +| | | TF11, bits | 1x288 | +| | | TF12, bits | 1x304 | +| | | TF13, bits | 1x312 | +| | | TF14, bits | 1x320 | + +| Higher layer | RAB/Signalling RB | | RAB | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------|---------| +| PDCP | PDCP header size, bit | | 0 | +| | | TF15, bits | 1x328 | +| | | TF16, bits | 1x352 | +| | | TF17, bits | 1x360 | +| | | TTI, ms | 20 | +| | | Coding type | TC | +| | | CRC, bit | 16 | +| | | Max number of bits/TTI after channel coding | 1140 | +| | | RM attribute | 180-220 | +| NOTE: Alternative 1x0 is used to have CRC present in all transport formats.
Header compressor should ensure that small_CID is used and that CID 0 is allocated to this RAB | | | | + +7.1.123.2.1.2 Transport channel parameters for interactive or background/DL:8 kbps/ PS RAB + DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.5.6.2.1.1 of [1]. + +7.1.123.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.123.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 72 | +| TFCS | (17 6. kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF9, TF0, TF0),
(TF10, TF0, TF0), (TF11, TF0, TF0), (TF12, TF0, TF0), (TF13, TF0, TF0), (TF14, TF0, TF0),
(TF15, TF0, TF0), (TF16, TF0, TF0), (TF17, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0), (TF6, TF1, TF0),
(TF7, TF1, TF0), (TF8, TF1, TF0), (TF9, TF1, TF0), (TF10, TF1, TF0), (TF11, TF1, TF0),
(TF12, TF1, TF0), (TF13, TF1, TF0), (TF14, TF1, TF0), (TF15, TF1, TF0), (TF16, TF1, TF0),
(TF17, TF1, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1),
(TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1), (TF7, TF0, TF1), (TF8, TF0, TF1),
(TF9, TF0, TF1), (TF10, TF0, TF1), (TF11, TF0, TF1), (TF12, TF0, TF1), (TF13, TF0, TF1),
(TF14, TF0, TF1), (TF15, TF0, TF1), (TF16, TF0, TF1), (TF17, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1),
(TF6, TF1, TF1), (TF7, TF1, TF1), (TF8, TF1, TF1), (TF9, TF1, TF1), (TF10, TF1, TF1),
(TF11, TF1, TF1), (TF12, TF1, TF1), (TF13, TF1, TF1), (TF14, TF1, TF1), (TF15, TF1, TF1),
(TF16, TF1, TF1), (TF17, TF1, TF1) | + +## 7.1.123.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +7.1.124 Conversational / speech / UL: 39.2 DL: 39.2 kbps / PS RAB + +Interactive or Background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 +kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 6. + +NOTE: The first RAB is used for multiplexed RTP and RTCP flows, the second RAB is used for SIP signaling and the third RAB is used for signaling radio bearers. + +## 7.1.124.1 Uplink + +## 7.1.124.1.1 Transport channel parameters + +## 7.1.124.1.1.1 Transport channel parameters for Conversational / speech / UL: 39.2 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|--------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 88, 304, 784 | +| | Max data rate, bps | | 39200 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 96, 312, 792 | +| | TFS | TF0, bits | 0x792 | +| | | TF1, bits | 1x96 | +| | | TF2, bits | 1x312 | +| | | TF3, bits | 1x792 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2436 | +| | Uplink: Max number of bits/radio frame before rate matching | | 1218 | +| | RM attribute | | 180-220 | + +NOTE: Header compressor should ensure that ROHC's small\_CID is used + +## 7.1.124.1.1.2 Transport channel parameters for Interactive or Background / UL: 8 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Uplink: Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 7.1.124.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.124.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (40 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), | + +## 7.1.124.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +## 7.1.124.2 Downlink + +## 7.1.124.2.1 Transport channel parameters + +## 7.1.124.2.1.1 Transport channel parameters for Conversational / speech / DL: 39.2 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|--------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 88, 304, 784 | +| | Max data rate, bps | | 39200 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 96, 312, 792 | +| | TFS | TF0, bits | 0x792 | +| | | TF1, bits | 1x96 | +| | | TF2, bits | 1x312 | +| | | TF3, bits | 1x792 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2436 | +| | RM attribute | | 180-220 | + +NOTE: Header compressor should ensure that ROHC's small\_CID is used + +## 7.1.124.2.1.2 Transport channel parameters for Interactive or Background / DL: 8 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|------------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | RM attribute | | 135-175 | + +## 7.1.124.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.124.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (40 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1) | + +## 7.1.124.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | | Fixed | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.1.125 Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps, DL: 64 kbps. This is supported in release 99. + +## 7.1.125.1 Uplink + +## 7.1.125.1.1 Transport channel parameters + +## 7.1.125.1.1.1 Transport channel parameters for Streaming / unknown / UL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 128000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 4038 | +| | RM attribute | | 125-165 | + +## 7.1.125.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +## 7.1.125.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.125.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF0), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF0), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1) | + +## 7.1.125.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.88 | + +## 7.1.125.2 Downlink + +## 7.1.125.2.1 Transport channel parameters + +## 7.1.125.2.1.1 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|---------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | RM attribute | | 135-175 | + +## 7.1.125.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +## 7.1.125.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.125.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF0,TF1,TF0), (TF1,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF0,TF1,TF1), (TF1,TF1,TF1) | + +## 7.1.125.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|----------| +| DPCH Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.1.126 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative + +This configuration is similar to configuration 7.1.96, but uses an RLC PDU size of 336 bits for the Streaming 16 kbps RB, and defines a full TFS for the Streaming 128 kbps RB. The TF 2x656 is left out of the TFCS to increase the probability that GBR can be met. + +The minimum UE classes supporting this combination are UL: 128 kbps, DL: 64 kbps. This is supported in release 99. + +## 7.1.126.1 Uplink + +## 7.1.126.1.1 Transport channel parameters + +## 7.1.126.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +## 7.1.126.1.1.2 Transport channel parameters for Streaming / unknown / UL:128 kbps / PS RAB + +See subclause 7.1.125.1.1.1. + +## 7.1.126.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.1.1.2 of [1]. + +## 7.1.126.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.126.1.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF1,TF4,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF1,TF4,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF1,TF4,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF1,TF4,TF1,TF1) | + +## 7.1.126.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.76 | + +## 7.1.126.2 Downlink + +## 7.1.126.2.1 Transport channel parameters + +## 7.1.126.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +## 7.1.126.2.1.2 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +See subclause 7.1.125.2.1.1. + +## 7.1.126.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.38b.2.1.2 of [1]. + +## 7.1.126.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.126.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1) | + +## 7.1.126.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of Pilot bits/slot | +| | DPDCH | 60 | +| | | Number of data bits/frame | +| | | 900 | + +**7.1.127 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH** + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum sum of number of bits of all convolutionally coded transport blocks being transmitted at an arbitrary time instant' = 1280, DL: 32 kbps plus support for 'Maximum number of TFC' = 48 and 'Maximum sum of number of bits of all convolutionally coded transport blocks being received at an arbitrary time instant' = 1280. The minimum UE class to support the alternative UL configuration is UL: 64kbps. The minimum UE class to support the alternative DL configuration is DL: 32 kbps plus support for 'Maximum number of TFC' = 48. + +This is supported in Release 5. + +### 7.1.127.1 Uplink + +#### 7.1.127.1.1 Transport channel parameters + +##### 7.1.127.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +##### 7.1.127.1.1.2 Transport channel parameters for Interactive or background / UL: 8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +##### 7.1.127.1.1.3 Transport channel parameters for UL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 7.1.127.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1) | + +#### 7.1.127.1.1.5 TFC subset list + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1)},

1 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1),
(TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0),
(TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1)},

2 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1)} | + +#### 7.1.127.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +## 7.1.127.2 Downlink + +## 7.1.127.2.1 Transport channel parameters + +## 7.1.127.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +## 7.1.127.2.1.2 Transport channel parameters for Interactive or background / DL: 8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.2.1.1 of [1]. + +## 7.1.127.2.1.3 Transport channel parameters for DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.127.2.1.4 Transport channel parameters for DL: 0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.127.2.1.5 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 40 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8 kbps RAB, DCCH, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0),
(TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1),
(TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1),
(TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1),
(TF4,TF3,TF0,TF1,TF1,TF1) | + +## 7.1.127.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +7.1.128 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL: 64 kbps plus support for 'Maximum number of TFC' = 128. + +This is supported in Release 5. + +## 7.1.128.1 Uplink + +## 7.1.128.1.1 Transport channel parameters + +## 7.1.128.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +## 7.1.128.1.1.2 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23c.1.1.1 of [1]. + +## 7.1.128.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.128.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1) | + +## 7.1.128.1.1.5 TFC subset list + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1)}, | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | $ \begin{aligned} 2 = \{ & (TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0), \\ & (TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1), \\ & (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1), \\ & (TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), \\ & (TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0), \\ & (TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1), \\ & (TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1), (TF0, TF0, TF0, TF2, TF0), \\ & (TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0), (TF3, TF2, TF0, TF2, TF0), \\ & (TF4, TF3, TF0, TF2, TF0), (TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1), \\ & (TF2, TF1, TF0, TF2, TF1), (TF3, TF2, TF0, TF2, TF1), (TF4, TF3, TF0, TF2, TF1), \\ & (TF0, TF0, TF0, TF3, TF0), (TF1, TF0, TF0, TF3, TF0), (TF2, TF1, TF0, TF3, TF0), \\ & (TF3, TF2, TF0, TF3, TF0), (TF4, TF3, TF0, TF3, TF0), (TF0, TF0, TF0, TF3, TF1), \\ & (TF1, TF0, TF0, TF3, TF1), (TF2, TF1, TF0, TF3, TF1), (TF3, TF2, TF0, TF3, TF1), \\ & (TF4, TF3, TF0, TF3, TF1), (TF0, TF0, TF0, TF4, TF0), (TF1, TF0, TF0, TF4, TF0), \\ & (TF2, TF1, TF0, TF4, TF0), (TF3, TF2, TF0, TF4, TF0), (TF4, TF3, TF0, TF4, TF0), \\ & (TF0, TF0, TF0, TF4, TF1), (TF1, TF0, TF0, TF4, TF1), (TF2, TF1, TF0, TF4, TF1), \\ & (TF3, TF2, TF0, TF4, TF1), (TF4, TF3, TF0, TF4, TF1) \} \end{aligned} $ | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.128.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +### 7.1.128.2 Downlink + +#### 7.1.128.2.1 Transport channel parameters + +##### 7.1.128.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +##### 7.1.128.2.1.2 Transport channel parameters for Interactive or background / DL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23c.2.1.1 of [1]. + +##### 7.1.128.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.128.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.128.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 | +| TFCS | ((RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH, DCCH 0.15)= (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0), (TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0), (TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0), (TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0), (TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0), (TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0), (TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0), (TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0), (TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0), (TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1), (TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1), (TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1), (TF4,TF3,TF0,TF4,TF1,TF1) | + +## 7.1.128.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +### 7.1.129 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL: 128 kbps plus support for 'Maximum number of TFC' = 128 and 'Maximum number of physical channel bits received in any 10 ms interval (DPCH, S-CCPCH)' = 14400. The minimum UE class to support the alternative DL configuration is DL: 384 kbps plus support for 'Maximum number of TFC' = 256. + +This is supported in Release 5. + +### 7.1.129.1 Uplink + +See subclause 7.1.109.1 + +**7.1.129.2 Downlink****7.1.129.2.1 Transport channel parameters****7.1.129.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB** + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +**7.1.129.2.1.2 Transport channel parameters for Interactive or background / DL:256 kbps / PS RAB** + +See subclause 6.10.2.4.1.31.2.1.1 of [1]. + +**7.1.129.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +**7.1.129.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH** + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +7.1.129.2.1.5 + +TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 (alt 140) | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 256 kbps RAB, DCCH, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0),
(TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0),
(TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0),
(TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0),
(TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0),
(TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0),
(TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0),
(TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0),
(TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0),
(TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1),
(TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1),
(TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1),
(TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1),
(TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1),
(TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1),
(TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1),
(TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1),
(TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1),
(TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1),
(TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1),
(TF4,TF3,TF0,TF4,TF1,TF1)
(alt. (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0),
(TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0),
(TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0),
(TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0),
(TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0),
(TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0),
(TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0),
(TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0),
(TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0),
(TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF5,TF0,TF0),
(TF1,TF0,TF0,TF5,TF0,TF0), (TF2,TF1,TF0,TF5,TF0,TF0), (TF3,TF2,TF0,TF5,TF0,TF0),
(TF4,TF3,TF0,TF5,TF0,TF0), (TF0,TF0,TF0,TF5,TF1,TF0), (TF1,TF0,TF0,TF5,TF1,TF0),
(TF2,TF1,TF0,TF5,TF1,TF0), (TF3,TF2,TF0,TF5,TF1,TF0), (TF4,TF3,TF0,TF5,TF1,TF0),
(TF0,TF0,TF0,TF6,TF0,TF0), (TF1,TF0,TF0,TF6,TF0,TF0), (TF2,TF1,TF0,TF6,TF0,TF0),
(TF3,TF2,TF0,TF6,TF0,TF0), (TF4,TF3,TF0,TF6,TF0,TF0), (TF0,TF0,TF0,TF6,TF1,TF0),
(TF1,TF0,TF0,TF6,TF1,TF0), (TF2,TF1,TF0,TF6,TF1,TF0), (TF3,TF2,TF0,TF6,TF1,TF0),
(TF4,TF3,TF0,TF6,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1),
(TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1),
(TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1),
(TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1),
(TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1) | + +| | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1),
(TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1),
(TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1),
(TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1),
(TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF0,TF3,TF1,TF1),
(TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1), (TF0,TF0,TF0,TF4,TF0,TF1),
(TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1), (TF3,TF2,TF0,TF4,TF0,TF1),
(TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1), (TF1,TF0,TF0,TF4,TF1,TF1),
(TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1), (TF4,TF3,TF0,TF4,TF1,TF1),
(TF0,TF0,TF0,TF5,TF0,TF1), (TF1,TF0,TF0,TF5,TF0,TF1), (TF2,TF1,TF0,TF5,TF0,TF1),
(TF3,TF2,TF0,TF5,TF0,TF1), (TF4,TF3,TF0,TF5,TF0,TF1), (TF0,TF0,TF0,TF5,TF1,TF1),
(TF1,TF0,TF0,TF5,TF1,TF1), (TF2,TF1,TF0,TF5,TF1,TF1), (TF3,TF2,TF0,TF5,TF1,TF1),
(TF4,TF3,TF0,TF5,TF1,TF1), (TF0,TF0,TF0,TF6,TF0,TF1), (TF1,TF0,TF0,TF6,TF0,TF1),
(TF2,TF1,TF0,TF6,TF0,TF1), (TF3,TF2,TF0,TF6,TF0,TF1), (TF4,TF3,TF0,TF6,TF0,TF1),
(TF0,TF0,TF0,TF6,TF1,TF1), (TF1,TF0,TF0,TF6,TF1,TF1), (TF2,TF1,TF0,TF6,TF1,TF1),
(TF3,TF2,TF0,TF6,TF1,TF1), (TF4,TF3,TF0,TF6,TF1,TF1)) | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.129.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|----------| +| DPCH Downlink | DTX position | | Flexible | +| | Spreading factor | | 8 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 8 | +| | | Number of Pilot bits/slot | 16 | +| | DPDCH | Number of data bits/slot | 640 | +| | | Number of data bits/frame | 9600 | +| | | | | + +### 7.1.130 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 5. + +#### 7.1.130.1 Uplink + +##### 7.1.130.1.1 Transport channel parameters + +###### 7.1.130.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.130.1.1.2 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.1.1.1 of [1]. + +###### 7.1.130.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.1.130.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH)=
(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1) | + +## 7.1.130.1.1.5 TFC subset list + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1),
(TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1)},

1 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1),
(TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0),
(TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1)},

2 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1)} | + +## 7.1.130.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.72 | + +## 7.1.130.2 Downlink + +## 7.1.130.2.1 Transport channel parameters + +## 7.1.130.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +## 7.1.130.2.1.2 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.2.1.1 of [1]. + +## 7.1.130.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.130.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.130.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 40 | +| TFCS | ((RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH, DCCH 0.15)= (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0), (TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0), (TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1) | + +## 7.1.130.2.2 Physical channel parameters + +| | | | +|---------------|---------------------------|--------------------------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | | 4 | +| DPDCH | Number of Pilot bits/slot | 8 | +| | Number of data bits/slot | 140 | +| | Number of data bits/frame | 2100 | + +## 7.1.131 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release '99. + +## 7.1.131.1 Uplink + +## 7.1.131.1.1 Transport channel parameters + +## 7.1.131.1.1.1 Transport channel parameters for Conversational / speech / UL: 12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.1.1.1 of [1]. + +## 7.1.131.1.1.2 Transport channel parameters for UL:13.6 kbps SRBs for DCCH + +| | | | | | | +|--------------|-------------------------------------------|--------------------------------|-----------------|------------------------------|-----------------------------| +| Higher layer | RAB/signalling RB
User of Radio Bearer | SRB#1
RRC | SRB#2
RRC | SRB#3
NAS_DT
High prio | SRB#4
NAS_DT
Low prio | +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | UM | AM | AM | AM | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | +| | Max data rate, bps | 13 600 | 12 800 | 12 800 | 12 800 | +| | AMD/UMD PDU header, bit | 8 | 16 | 16 | 16 | +| MAC | MAC header, bit | 4 | 4 | 4 | 4 | +| | MAC multiplexing | 4 logical channel multiplexing | | | | +| Layer 1 | TrCH type | DCH | | | | +| | TB sizes, bit | 148 (alt 0, 148) | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) | | | +| | | TF1, bits | 1x148 | | | +| | | TF2, bits | 2x148 | | | +| | | TF3, bits | 3x148 | | | +| | | TF4, bits | 4x148 | | | + +| | | +|-------------------------------------------------------------|------------| +| TTI, ms | 40 | +| Coding type | CC 1/3 | +| CRC, bit | 16 | +| Max number of bits/TTI before rate matching | 1992 | +| Uplink: Max number of bits/radio frame before rate matching | 498 | +| RM attribute | 155 to 185 | + +## 7.1.131.1.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 11 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF1, TF0), (TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF1), (TF2, TF1, TF1, TF1), (TF0, TF0, TF0, TF2), (TF1, TF0, TF0, TF2),
(TF0, TF0, TF0, TF3), (TF1, TF0, TF0, TF3), (TF0, TF0, TF0, TF4) | + +## 7.1.131.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +## 7.1.131.2 Downlink + +## 7.1.131.2.1 Transport channel parameters + +## 7.1.131.2.1.1 Transport channel parameters for Conversational / speech / DL: 12.2 kbps / CS RAB + +See subclause 6.10.2.4.1.4.2.1.1 of [1]. + +## 7.1.131.2.1.2 Transport channel parameters for DL:13.6 kbps SRBs for DCCH + +| | | | | | | | +|--------------|---------------------------------------------|-----------|--------------------------------|--------|---------------------|--------------------| +| Higher layer | RAB/signalling RB | | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +| | User of Radio Bearer | | RRC | RRC | NAS_DT
High prio | NAS_DT
Low prio | +| RLC | Logical channel type | | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | | UM | AM | AM | AM | +| | Payload sizes, bit | | 136 | 128 | 128 | 128 | +| | Max data rate, bps | | 13 600 | 12 800 | 12 800 | 12 800 | +| | AMD/UMD PDU header, bit | | 8 | 16 | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | 4 | 4 | +| | MAC multiplexing | | 4 logical channel multiplexing | | | | +| Layer 1 | TrCH type | | DCH | | | | +| | TB sizes, bit | | 148 (alt 0, 148) (note) | | | | +| | TFS | TF0, bits | 0x148 (alt 1x0) (note) | | | | +| | | TF1, bits | 1x148 | | | | +| | | TF2, bits | 2x148 | | | | +| | | TF3, bits | 3x148 | | | | +| | | TF4, bits | 4x148 | | | | +| | TTI, ms | | 40 | | | | +| | Coding type | | CC 1/3 | | | | +| | CRC, bit | | 16 | | | | +| | Max number of bits/TTI before rate matching | | 1992 | | | | +| | RM attribute | | 155 to 230 | | | | + +NOTE: Alternative parameters enable the measurement "transport channel BLER" in the UE. + +## 7.1.131.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 11 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF1, TF0), (TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF1), (TF2, TF1, TF1, TF1), (TF0, TF0, TF0, TF2), (TF1, TF0, TF0, TF2),
(TF0, TF0, TF0, TF3), (TF1, TF0, TF0, TF3), (TF0, TF0, TF0, TF4) | + +## 7.1.131.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +## 7.1.132 Conversational / speech / UL: (12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps with support of 'Maximum number of TFC = 32', DL: 12 kbps with support of 'Maximum number of TFC = 32'. + +This is supported in Release '99. + +## 7.1.132.1 Uplink + +## 7.1.132.1.1 Transport channel parameters + +## 7.1.132.1.1.1 Transport channel parameters for Conversational / speech / UL:(12.2 7.95 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4a.1.1.1 of [1]. + +## 7.1.132.1.1.2 Transport channel parameters for UL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.1.1.2. + +## 7.1.132.1.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 17 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF1, TF0, TF0), (TF3, TF2, TF0, TF0),
(TF4, TF3, TF0, TF0), (TF5, TF4, TF1, TF0), (TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1),
(TF2, TF1, TF0, TF1), (TF3, TF2, TF0, TF1), (TF4, TF3, TF0, TF1), (TF5, TF4, TF1, TF1),
(TF0, TF0, TF0, TF2), (TF1, TF0, TF0, TF2), (TF0, TF0, TF0, TF3), (TF1, TF0, TF0, TF3),
(TF0, TF0, TF0, TF4) | + +## 7.1.132.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +## 7.1.132.2 Downlink + +### 7.1.132.2.1 Transport channel parameters + +#### 7.1.132.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.95 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4a.2.1.1 of [1]. + +#### 7.1.132.2.1.2 Transport channel parameters for DL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.2.1.2. + +#### 7.1.132.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 17 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF5,TF4,TF1,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1),
(TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF5,TF4,TF1,TF1),
(TF0,TF0,TF0,TF2), (TF1,TF0,TF0,TF2), (TF0,TF0,TF0,TF3), (TF1,TF0,TF0,TF3),
(TF0, TF0, TF0, TF4) | + +### 7.1.132.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +## 7.1.132a Conversational / speech / UL: (12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps with support of 'Maximum number of TFC = 32', DL: 12 kbps with support of 'Maximum number of TFC = 32'. + +This is supported in Release '99. + +### 7.1.132a.1 Uplink + +#### 7.1.132a.1.1 Transport channel parameters + +##### 7.1.132a.1.1.1 Transport channel parameters for Conversational / speech / UL:(12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.1.1.1 of [1]. + +##### 7.1.132a.1.1.2 Transport channel parameters for UL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.1.1.2. + +##### 7.1.132a.1.1.3 TFCS + +See subclause 7.1.132.1.1.3. + +#### 7.1.132a.1.2 Physical channel parameters + +See subclause 7.1.132.1.2. + +## 7.1.132a.2 Downlink + +### 7.1.132a.2.1 Transport channel parameters + +#### 7.1.132a.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB + +See subclause 6.10.2.4.1.4b.2.1.1 of [1]. + +#### 7.1.132a.2.1.2 Transport channel parameters for DL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.2.1.2. + +#### 7.1.132a.2.1.3 TFCS + +See subclause 7.1.132.2.1.3. + +### 7.1.132a.2.2 Physical channel parameters + +See subclause 7.1.132.2.2. + +## 7.1.133 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:13.6 DL:13.6 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps with support of 'Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant' = 2560 and 'Maximum number of physical channel bits received in any 10 ms interval (DPCH, S-CCPCH)' = 2400. The minimum UE class to support the alternative DL configuration (40ms TTI) is DL: 64 kbps. + +This is supported in Release '99. + +### 7.1.133.1 Uplink + +#### 7.1.133.1.1 Transport channel parameters + +##### 7.1.133.1.1.1 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.1.1.1 of [1]. + +##### 7.1.133.1.1.2 Transport channel parameters for UL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.1.1.2 + +#### 7.1.133.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------| +| TFCS size | 7 | +| TFCS | (64 kbps RAB, DCCH)=(TF0, TF0), (TF1, TF0), (TF0, TF1), (TF1, TF1), (TF0, TF2), (TF0, TF3), (TF0, TF4) | + +#### 7.1.133.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.88 | + +### 7.1.133.2 Downlink + +#### 7.1.133.2.1 Transport channel parameters + +##### 7.1.133.2.1.1 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See subclause 6.10.2.4.1.13.2.1.1 of [1]. + +#### 7.1.133.2.1.2 Transport channel parameters for DL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.2.1.2 + +#### 7.1.133.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------| +| TFCS size | 7 | +| TFCS | (64 kbps RAB, DCCH)=(TF0, TF0), (TF1, TF0), (TF0, TF1), (TF1, TF1), (TF0, TF2), (TF0, TF3), (TF0, TF4) | + +#### 7.1.133.2.2 Physical channel parameters + +| | | | +|---------------|---------------------------|----------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| DPCCH | Number of TFCI bits/slot | 8 | +| | Number of TPC bits/slot | 4 | +| | Number of Pilot bits/slot | 8 | +| DPDCH | Number of data bits/slot | 140 | +| | Number of data bits/frame | 2 100 | + +### 7.1.134 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + UL: 13.6 DL: 13.6 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release 5. + +#### 7.1.134.1 Uplink + +##### 7.1.134.1.1 Transport channel parameters + +###### 7.1.134.1.1.1 Transport channel parameters for Conversational / speech / UL:(12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.134.1.1.2 Transport channel parameters for UL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.1.1.2. + +###### 7.1.134.1.1.3 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 15 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0), (TF4,TF3,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1), (TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF0,TF0,TF0,TF2), (TF1,TF0,TF0,TF2), (TF0,TF0,TF0,TF3), (TF1,TF0,TF0,TF3), (TF0,TF0,TF0,TF4) | + +##### 7.1.134.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +## 7.1.134.2 Downlink + +### 7.1.134.2.1 Transport channel parameters + +#### 7.1.134.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +#### 7.1.134.2.1.2 Transport channel parameters for DL:13.6 kbps SRBs for DCCH + +See subclause 7.1.131.2.1.2. + +#### 7.1.134.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 15 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0), (TF3,TF2,TF0,TF0),
(TF4,TF3,TF0,TF0), (TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1), (TF4,TF3,TF0,TF1), (TF0,TF0,TF0,TF2), (TF1,TF0,TF0,TF2),
(TF0,TF0,TF0,TF3), (TF1,TF0,TF0,TF3), (TF0,TF0,TF0,TF4) | + +### 7.1.134.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +## 7.1.135 Void + +## 7.1.136 Void + +## 7.1.137 Interactive or Background / UL:32 DL:64 kbps / PS RAB + Interactive or Background / UL:32 DL:64 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps plus support for 'Maximum number of AM entities' = 5, DL: 64kbps plus support for 'Maximum number of AM entities' = 5. The minimum UE class to support the alternative UL physical configuration is UL: 12kbps plus support for 'Maximum number of AM entities' = 5 and 'Maximum number of DPDCH bits transmitted per 10 ms' = 1200. + +This is supported in Release '99. + +## 7.1.137.1 Uplink + +## 7.1.137.1.1 Transport channel parameters + +## 7.1.137.1.1.1 Transport channel parameters for Interactive or Background / UL:32 + UL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-------------------------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 32000 | 32000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 (alt. N/A) | | +| | TTI, ms | | 20 (alt. 10) | | +| | Coding type | | TC (alt. CC 1/3) | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 2148 (1092) | | +| | Uplink: Max number of bits/radio frame before rate matching | | 1074 (1092) | | +| | RM attribute | | 135-175 | | + +## 7.1.137.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1] + +## 7.1.137.1.1.3 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 (alt. 4) | +| TFCS | (32 kbps RAB + 32 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1), (TF1, TF1), (TF2, TF1)
(alt. (TF0, TF0), (TF1, TF0), (TF0, TF1), (TF1, TF1)) | + +## 7.1.137.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 0.88 | + +## 7.1.137.2 Downlink + +See subclause 7.1.72.2. + +## 7.1.138 Interactive or background / UL:128 DL:384 kbps / PS RAB + Interactive or Background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL: 384kbps. + +This is supported in Release '99. + +### 7.1.138.1 Uplink + +See subclause 7.1.88.1 + +### 7.1.138.2 Downlink + +See subclause 7.1.87.2 + +### 7.1.139 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5, DL: 32 kbps plus support for 'Maximum number of AM entities' = 5. + +This is supported in Release 5. + +### 7.1.139.1 Uplink + +#### 7.1.139.1.1 Transport channel parameters + +##### 7.1.139.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +##### 7.1.139.1.1.2 Transport channel parameters for Interactive or background / UL:0 + UL:0 kbps / PS RAB + +See subclause 7.1.79.1.1.2 + +##### 7.1.139.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.139.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1) | + +##### 7.1.139.1.1.5 TFC subset list + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1)},
1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1)},
2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1)} | + +### 7.1.139.1.2 Physical channel parameters + +| | | | +|-------------|----------------------|----| +| DPCH Uplink | Min spreading factor | 64 | +|-------------|----------------------|----| + +| | | | +|--|-------------------------------------------|------| +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 0.84 | + +## 7.1.139.2 Downlink + +### 7.1.139.2.1 Transport channel parameters + +#### 7.1.139.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +#### 7.1.139.2.1.2 Transport channel parameters for Interactive or background / DL:0 + DL:0 kbps / PS RAB + +See subclause 7.1.79.2.1.2 + +#### 7.1.139.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.1.139.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +#### 7.1.139.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0 kbps RAB, DCCH 3.4, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1),
(TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1) | + +### 7.1.139.2.2 Physical channel parameters + +See subclause 6.10.2.4.1.62.2.2 of [1]. + +## 7.1.140 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Maximum number of TFC' = 64, DL: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Maximum number of TFC' = 128. + +This is supported in Release 5. + +### 7.1.140.1 Uplink + +#### 7.1.140.1.1 Transport channel parameters + +##### 7.1.140.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +7.1.140.1.1.2 Transport channel parameters for Interactive or background / UL:64 + UL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.38d.1.1.2 of [1]. + +7.1.140.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.140.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64+64 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1) | + +7.1.140.1.1.5 TFC subset list + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1)},

2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1)} | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.140.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.76 | + +### 7.1.140.2 Downlink + +#### 7.1.140.2.1 Transport channel parameters + +##### 7.1.140.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +##### 7.1.140.2.1.2 Transport channel parameters for Interactive or background / DL:64 + DL:64 kbps / PS RAB + +See subclause 6.10.2.4.1.38d.2.1.2 of [1]. + +##### 7.1.140.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.140.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +##### 7.1.140.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64+64 kbps RAB, DCCH 3.4, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0),
(TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0),
(TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0),
(TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0),
(TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0),
(TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF0,TF0,TF0,TF3,TF1,TF0),
(TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0), (TF3,TF2,TF0,TF3,TF1,TF0),
(TF4,TF3,TF0,TF3,TF1,TF0), (TF0,TF0,TF0,TF4,TF0,TF0), (TF1,TF0,TF0,TF4,TF0,TF0),
(TF2,TF1,TF0,TF4,TF0,TF0), (TF3,TF2,TF0,TF4,TF0,TF0), (TF4,TF3,TF0,TF4,TF0,TF0),
(TF0,TF0,TF0,TF4,TF1,TF0), (TF1,TF0,TF0,TF4,TF1,TF0), (TF2,TF1,TF0,TF4,TF1,TF0),
(TF3,TF2,TF0,TF4,TF1,TF0), (TF4,TF3,TF0,TF4,TF1,TF0), (TF0,TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1),
(TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1), | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF0,TF0,TF0,TF1,TF1,TF1),
(TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1), (TF3,TF2,TF0,TF1,TF1,TF1),
(TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1),
(TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF0,TF2,TF1,TF1),
(TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1), (TF0,TF0,TF0,TF3,TF0,TF1),
(TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1), (TF3,TF2,TF0,TF3,TF0,TF1),
(TF4,TF3,TF0,TF3,TF0,TF1), (TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1),
(TF2,TF1,TF0,TF3,TF1,TF1), (TF3,TF2,TF0,TF3,TF1,TF1), (TF4,TF3,TF0,TF3,TF1,TF1),
(TF0,TF0,TF0,TF4,TF0,TF1), (TF1,TF0,TF0,TF4,TF0,TF1), (TF2,TF1,TF0,TF4,TF0,TF1),
(TF3,TF2,TF0,TF4,TF0,TF1), (TF4,TF3,TF0,TF4,TF0,TF1), (TF0,TF0,TF0,TF4,TF1,TF1),
(TF1,TF0,TF0,TF4,TF1,TF1), (TF2,TF1,TF0,TF4,TF1,TF1), (TF3,TF2,TF0,TF4,TF1,TF1),
(TF4,TF3,TF0,TF4,TF1,TF1) | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.140.2.2 Physical channel parameters + +| DPCH Downlink | DTX position | | Flexible or fixed | +|---------------|---------------------------|--|-------------------| +| | Spreading factor | | | +| DPCCH | Number of TFCI bits/slot | | 8 | +| | Number of TPC bits/slot | | 4 | +| | Number of Pilot bits/slot | | 8 | +| DPDCH | Number of data bits/slot | | 140 | +| | Number of data bits/frame | | 2100 | + +### 7.1.141 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 64, DL: 128 kbps plus support for 'Maximum number of TFC' = 128. + +This is supported in Release 5. + +#### 7.1.141.1 Uplink + +##### 7.1.141.1.1 Transport channel parameters + +###### 7.1.141.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.141.1.1.2 Transport channel parameters for Interactive or background / UL:128 + UL:128kbps / PS RAB + +See subclause 7.1.88.1.1.1 + +###### 7.1.141.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.141.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128+128 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +7.1.141.1.1.5 + +## TFC subset list + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1)},

2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1)} | + +#### 7.1.141.1.2 + +### Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.88 | + +7.1.141.2 Downlink + +7.1.141.2.1 Transport channel parameters + +7.1.141.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +7.1.141.2.1.2 Transport channel parameters for Interactive or background / DL:128 + DL:128 kbps / PS RAB + +See subclause 7.1.88.2.1.1 + +7.1.141.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.141.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +7.1.141.2.1.5 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 100 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128+128 kbps RAB, DCCH 3.4, DCCH 0.15)=
(TF0, TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1, TF0),
(TF1, TF0, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF0, TF1, TF0), (TF3, TF2, TF0, TF0, TF1, TF0),
(TF4, TF3, TF0, TF0, TF1, TF0), (TF0, TF0, TF0, TF1, TF0, TF0), (TF1, TF0, TF0, TF1, TF0, TF0),
(TF2, TF1, TF0, TF1, TF0, TF0), (TF3, TF2, TF0, TF1, TF0, TF0), (TF4, TF3, TF0, TF1, TF0, TF0),
(TF0, TF0, TF0, TF1, TF1, TF0), (TF1, TF0, TF0, TF1, TF1, TF0), (TF2, TF1, TF0, TF1, TF1, TF0),
(TF3, TF2, TF0, TF1, TF1, TF0), (TF4, TF3, TF0, TF1, TF1, TF0), (TF0, TF0, TF0, TF2, TF0, TF0),
(TF1, TF0, TF0, TF2, TF0, TF0), (TF2, TF1, TF0, TF2, TF0, TF0), (TF3, TF2, TF0, TF2, TF0, TF0),
(TF4, TF3, TF0, TF2, TF0, TF0), (TF0, TF0, TF0, TF2, TF1, TF0), (TF1, TF0, TF0, TF2, TF1, TF0),
(TF2, TF1, TF0, TF2, TF1, TF0), (TF3, TF2, TF0, TF2, TF1, TF0), (TF4, TF3, TF0, TF2, TF1, TF0),
(TF0, TF0, TF0, TF3, TF0, TF0), (TF1, TF0, TF0, TF3, TF0, TF0), (TF2, TF1, TF0, TF3, TF0, TF0),
(TF3, TF2, TF0, TF3, TF0, TF0), (TF4, TF3, TF0, TF3, TF0, TF0), (TF0, TF0, TF0, TF3, TF1, TF0),
(TF1, TF0, TF0, TF3, TF1, TF0), (TF2, TF1, TF0, TF3, TF1, TF0), (TF3, TF2, TF0, TF3, TF1, TF0),
(TF4, TF3, TF0, TF3, TF1, TF0), (TF0, TF0, TF0, TF4, TF0, TF0), (TF1, TF0, TF0, TF4, TF0, TF0),
(TF2, TF1, TF0, TF4, TF0, TF0), (TF3, TF2, TF0, TF4, TF0, TF0), (TF4, TF3, TF0, TF4, TF0, TF0),
(TF0, TF0, TF0, TF4, TF1, TF0), (TF1, TF0, TF0, TF4, TF1, TF0), (TF2, TF1, TF0, TF4, TF1, TF0),
(TF3, TF2, TF0, TF4, TF1, TF0), (TF4, TF3, TF0, TF4, TF1, TF0), (TF0, TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF0, TF1), (TF0, TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF0, TF1, TF1),
(TF2, TF1, TF0, TF0, TF1, TF1), (TF3, TF2, TF0, TF0, TF1, TF1), (TF4, TF3, TF0, TF0, TF1, TF1),
(TF0, TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF0, TF1), (TF2, TF1, TF0, TF1, TF0, TF1),
(TF3, TF2, TF0, TF1, TF0, TF1), (TF4, TF3, TF0, TF1, TF0, TF1), (TF0, TF0, TF0, TF1, TF1, TF1),
(TF1, TF0, TF0, TF1, TF1, TF1), (TF2, TF1, TF0, TF1, TF1, TF1), (TF3, TF2, TF0, TF1, TF1, TF1),
(TF4, TF3, TF0, TF1, TF1, TF1), (TF0, TF0, TF0, TF2, TF0, TF1), (TF1, TF0, TF0, TF2, TF0, TF1),
(TF2, TF1, TF0, TF2, TF0, TF1), (TF3, TF2, TF0, TF2, TF0, TF1), (TF4, TF3, TF0, TF2, TF0, TF1),
(TF0, TF0, TF0, TF2, TF1, TF1), (TF1, TF0, TF0, TF2, TF1, TF1), (TF2, TF1, TF0, TF2, TF1, TF1),
(TF3, TF2, TF0, TF2, TF1, TF1), (TF4, TF3, TF0, TF2, TF1, TF1), (TF0, TF0, TF0, TF3, TF0, TF1),
(TF1, TF0, TF0, TF3, TF0, TF1), (TF2, TF1, TF0, TF3, TF0, TF1), (TF3, TF2, TF0, TF3, TF0, TF1),
(TF4, TF3, TF0, TF3, TF0, TF1), (TF0, TF0, TF0, TF3, TF1, TF1), (TF1, TF0, TF0, TF3, TF1, TF1),
(TF2, TF1, TF0, TF3, TF1, TF1), (TF3, TF2, TF0, TF3, TF1, TF1), (TF4, TF3, TF0, TF3, TF1, TF1),
(TF0, TF0, TF0, TF4, TF0, TF1), (TF1, TF0, TF0, TF4, TF0, TF1), (TF2, TF1, TF0, TF4, TF0, TF1),
(TF3, TF2, TF0, TF4, TF0, TF1), (TF4, TF3, TF0, TF4, TF0, TF1), (TF0, TF0, TF0, TF4, TF1, TF1),
(TF1, TF0, TF0, TF4, TF1, TF1), (TF2, TF1, TF0, TF4, TF1, TF1), (TF3, TF2, TF0, TF4, TF1, TF1),
(TF4, TF3, TF0, TF4, TF1, TF1) | + +### 7.1.141.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible or fixed | +| | Spreading factor | 16 | +| | DPCCH | Number of TFCI bits/slot | +| | | Number of TPC bits/slot | +| | | Number of Pilot bits/slot | +| | DPDCH | Number of data bits/slot | +| | | Number of data bits/frame | + +### 7.1.142 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:32 DL:32 kbps / PS RAB (20ms TTI) + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps plus support for 'Maximum number of TFC' = 64 and 'Maximum number of physical channel bits received in any 10 ms interval (DPCH, S-CCPCH)' = 2400. + +This is supported in Release 5. + +#### 7.1.142.1 Uplink + +##### 7.1.142.1.1 Transport channel parameters + +###### 7.1.142.1.1.1 Transport channel parameters for Conversational / speech / UL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.1.1.1 of [1]. + +###### 7.1.142.1.1.2 Transport channel parameters for Interactive or background / UL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23d.1.1.1 of [1]. + +###### 7.1.142.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.1.142.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1) | + +###### 7.1.142.1.1.5 TFC subset list + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list | 0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1)} | + +| | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

1 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF0, TF1),
(TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0),
(TF1, TF0, TF0, TF1, TF0), (TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF0, TF0, TF0, TF2, TF0), (TF1, TF0, TF0, TF2, TF0),
(TF2, TF1, TF0, TF2, TF0), (TF3, TF2, TF0, TF2, TF0), (TF0, TF0, TF0, TF2, TF1),
(TF1, TF0, TF0, TF2, TF1), (TF2, TF1, TF0, TF2, TF1), (TF3, TF2, TF0, TF2, TF1)}

2 = {(TF0, TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0, TF0), (TF2, TF1, TF0, TF0, TF0),
(TF3, TF2, TF0, TF0, TF0), (TF4, TF3, TF0, TF0, TF0), (TF0, TF0, TF0, TF0, TF1),
(TF1, TF0, TF0, TF0, TF1), (TF2, TF1, TF0, TF0, TF1), (TF3, TF2, TF0, TF0, TF1),
(TF4, TF3, TF0, TF0, TF1), (TF0, TF0, TF0, TF1, TF0), (TF1, TF0, TF0, TF1, TF0),
(TF2, TF1, TF0, TF1, TF0), (TF3, TF2, TF0, TF1, TF0), (TF4, TF3, TF0, TF1, TF0),
(TF0, TF0, TF0, TF1, TF1), (TF1, TF0, TF0, TF1, TF1), (TF2, TF1, TF0, TF1, TF1),
(TF3, TF2, TF0, TF1, TF1), (TF4, TF3, TF0, TF1, TF1), (TF0, TF0, TF0, TF2, TF0),
(TF1, TF0, TF0, TF2, TF0), (TF2, TF1, TF0, TF2, TF0), (TF3, TF2, TF0, TF2, TF0),
(TF4, TF3, TF0, TF2, TF0), (TF0, TF0, TF0, TF2, TF1), (TF1, TF0, TF0, TF2, TF1),
(TF2, TF1, TF0, TF2, TF1), (TF3, TF2, TF0, TF2, TF1), (TF4, TF3, TF0, TF2, TF1)}

| +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.1.142.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +### 7.1.142.2 Downlink + +#### 7.1.142.2.1 Transport channel parameters + +##### 7.1.142.2.1.1 Transport channel parameters for Conversational / speech / DL: (12.65 8.85 6.6) kbps / CS RAB + +See subclause 6.10.2.4.1.62.2.1.1 of [1]. + +##### 7.1.142.2.1.2 Transport channel parameters for Interactive or background / DL:32 kbps / PS RAB + +See subclause 6.10.2.4.1.23d.2.1.1 of [1]. + +##### 7.1.142.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.142.2.1.4 Transport channel parameters for DL:0.15 kbps SRB#5 for DCCH + +See subclause 6.10.2.4.1.62.2.1.3 of [1]. + +## 7.1.142.2.1.5 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 60 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 32 kbps RAB, DCCH, DCCH 0.15)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0), (TF3,TF2,TF0,TF0,TF1,TF0),
(TF4,TF3,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0),
(TF2,TF1,TF0,TF1,TF0,TF0), (TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF0,TF0,TF0,TF2,TF0,TF0),
(TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0), (TF3,TF2,TF0,TF2,TF0,TF0),
(TF4,TF3,TF0,TF2,TF0,TF0), (TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0),
(TF2,TF1,TF0,TF2,TF1,TF0), (TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1),
(TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF0,TF1,TF1),
(TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1), (TF3,TF2,TF0,TF0,TF1,TF1),
(TF4,TF3,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1),
(TF2,TF1,TF0,TF1,TF0,TF1), (TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF0,TF0,TF0,TF2,TF0,TF1),
(TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1), (TF3,TF2,TF0,TF2,TF0,TF1),
(TF4,TF3,TF0,TF2,TF0,TF1), (TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1),
(TF2,TF1,TF0,TF2,TF1,TF1), (TF3,TF2,TF0,TF2,TF1,TF1), (TF4,TF3,TF0,TF2,TF1,TF1) | + +## 7.1.142.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------------------| +| DPCH
Downlink | DTX position | | Flexible or fixed | +| | Spreading factor | | 32 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 140 | +| | | Number of data bits/frame | 2100 | + +## 7.1.143 Conversational / speech / UL:6.6 DL:6.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 12 kbps, DL: 12 kbps. + +This is supported in Release 5. + +## 7.1.143.1 Uplink + +## 7.1.143.1.1 Transport channel parameters + +## 7.1.143.1.1.1 Transport channel parameters for Conversational / speech / UL: 6.6 kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3 (note 2) | +|--------------|-------------------------------------------------------------|-----------|-----------------------------|----------------|-------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 40, 54
(alt. 0, 40, 54) | 78 | 60 | +| | Max data rate, bps | | 6600 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 40, 54
(alt. 0, 40, 54) | 78 | 60 | +| | TFS | TF0, bits | 0x54 (alt. 1x0)
(note 1) | 0x78 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2 bits | 1x54 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 222 | 258 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 111 | 129 | 0 | +| | RM attribute | | 180 to 220 | 170 to 210 | 256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 2: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned. + +#### 7.1.143.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +#### 7.1.143.1.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=

(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1) | + +#### 7.1.143.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +## 7.1.143.2 Downlink + +## 7.1.143.2.1 Transport channel parameters + +## 7.1.143.2.1.1 Transport channel parameters for Conversational / speech / DL: 6.6 kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 | RAB subflow #3 (note 2) | +|--------------|---------------------------------------------|-----------|----------------|----------------|-------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 40, 54 | 78 | 60 | +| | Max data rate, bps | | 6600 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 40, 54 | 78 | 60 | +| | TFS | TF0, bits | 1x0 (note 2) | 0x78 | 0x60 | +| | | TF1, bits | 1x40 | 1x78 | N/A | +| | | TF2 bits | 1x54 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/3 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 222 | 258 | 0 | +| | RM attribute | | 180 to 220 | 170 to 210 | 256 | + +NOTE 1: The TrCH corresponding to RAB subflow #1 should be used as the guiding TrCH, (see clause 4.3 in 3GPP TS 25.212 [14]). + +NOTE 2: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 3: RAB subflow #3 does not exist in Iu interface. UTRAN establishes this additional "dummy" subflow when the RAB for Wideband AMR is assigned + +## 7.1.143.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.1.143.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=

(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF1,TF0,TF1) | + +## 7.1.143.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------------------| +| DPCH Downlink | DTX position | | Fixed | +| | Spreading factor | | 256 (alt. 128)128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 2 (alt 4) | +| | DPDCH | Number of data bits/slot | 16 (alt. 34)34 | +| | | Number of data bits/frame | 240 (alt 510)510 | + +Note: The alternative DPDCH configuration is used with spreading factor of 128. + +## 7.1.144 Interactive or background / UL:64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +### 7.1.144.1 Uplink + +#### 7.1.144.1.1 Transport channel parameters + +##### 7.1.144.1.1.1 Transport channel parameters for Interactive or background / UL:64 kbps / PS RAB + +| | | | | +|--------------|-------------------------------------------------------------|-----------|------------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 64 000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | | TF3, bits | 3x328 | +| | | TF4, bits | 4x328 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 4 236 | +| | Uplink: Max number of bits/radio frame before rate matching | | 2 118 | +| | RM attribute | | 130 to 170 | + +##### 7.1.144.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1. + +##### 7.1.144.1.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +##### 7.1.144.1.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2 400 | +| | Puncturing Limit | 0.96 | + +### 7.1.144.2 Downlink + +#### 7.1.144.2.1 Transport channel parameters + +##### 7.1.144.2.1.1 Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB + +| | | | | +|--------------|----------------------|--|--------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 64 000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | + +| | | | +|---------|---------------------------------------------|------------| +| Layer 1 | TrCH type | DCH | +| | TB sizes, bit | 328 | +| | TFS | 0x328 | +| | | 1x328 | +| | | 2x328 | +| | | 3x328 | +| | | 4x328 | +| | TTI, ms | 20 | +| | Coding type | TC | +| | CRC, bit | 16 | +| | Max number of bits/TTI after channel coding | 4 236 | +| | RM attribute | 130 to 170 | + +#### 7.1.144.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See clause 6.10.2.4.1.2.2.1.1. + +#### 7.1.144.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +#### 7.1.144.2.2 Physical channel parameters + +| | | | +|---------------|------------------|---------------------------| +| DPCH Downlink | DTX position | Flexible | +| | Spreading factor | 32 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | | 4 | +| | | Number of Pilot bits/slot | +| | | 8 | +| | DPDCH | Number of data bits/slot | +| | | 140 | +| | | Number of data bits/frame | +| | | 2 100 | + +## 7.1.145 Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: ( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.145.1 Uplink + +#### 7.1.145.1.1 Transport channel parameters + +##### 7.1.145.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2
(note 2) | RAB subflow #3
(note 2) | +|--------------|-------------------------------------------------------------|-----------|--------------------------------------------------------------------|----------------------------|----------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 7, 47, 55, 63, 139, 151, 167 (alt 0, 7, 47, 55, 63, 139, 151, 167) | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 7, 47, 55, 63, 139, 151, 167 (alt 0, 7, 47, 55, 63, 139, 151, 167) | 103 | 60 | +| | TFS | TF0, bits | 0x167 (alt 1x0)
(note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x63 | N/A | N/A | +| | | TF5, bits | 1x139 | N/A | N/A | +| | | TF6, bits | 1x151 | N/A | N/A | +| | | TF7, bits | 1x167 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 561 | 0 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 281 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +##### 7.1.145.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.145.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF0, TF0, TF0), (TF3, TF0, TF0, TF0), (TF4, TF0, TF0, TF0),
(TF5, TF0, TF0, TF0), (TF6, TF0, TF0, TF0), (TF7, TF0, TF0, TF0)
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF0, TF0, TF1), (TF3, TF0, TF0, TF1), (TF4, TF0, TF0, TF1),
(TF5, TF0, TF0, TF1), (TF6, TF0, TF0, TF1), (TF7, TF0, TF0, TF1) | + +### 7.1.145.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +### 7.1.145.2 Downlink + +#### 7.1.145.2.1 Transport channel parameters + +##### 7.1.145.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | RAB subflow #1 | RAB subflow #2 (note 2) | RAB subflow #3 (note 2) | +|--------------|---------------------------------------------|---------------------------------|-------------------------|-------------------------| +| RLC | Logical channel type | DTCH | | | +| | RLC mode | TM | TM | TM | +| | Payload sizes, bit | 0, 7, 47, 55, 63, 139, 151, 167 | 103 | 60 | +| | Max data rate, bps | 13 200 | | | +| | TrD PDU header, bit | 0 | | | +| MAC | MAC header, bit | 0 | | | +| | MAC multiplexing | N/A | | | +| Layer 1 | TrCH type | DCH | DCH | DCH | +| | TB sizes, bit | 0, 7, 47, 55, 63, 139, 151, 167 | 103 | 60 | +| | TFS | 1x0 (note 1) | 0x103 | 0x60 | +| | | 1x7 | N/A | N/A | +| | | 1x47 | N/A | N/A | +| | | 1x55 | N/A | N/A | +| | | 1x63 | N/A | N/A | +| | | 1x139 | N/A | N/A | +| | | 1x151 | N/A | N/A | +| | | 1x167 | N/A | N/A | +| | TTI, ms | 20 | 20 | 20 | +| | Coding type | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | 561 | 0 | 0 | +| | RM attribute | 1-256 | 1-256 | 1-256 | + +NOTE 1: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +##### 7.1.145.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.145.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0), (TF4,TF0,TF0,TF0),
(TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1), (TF4,TF0,TF0,TF1),
(TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1) | + +## 7.1.145.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | | Fixed | +| | Spreading factor | | 256 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 2 | +| | DPDCH | Number of data bits/slot | 16 | +| | | Number of data bits/frame | 240 | + +7.1.146 Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +7.1.146.1 Uplink + +7.1.146.1.1 Transport channel parameters + +7.1.146.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 (note2) | RAB subflow #3 (note2) | +|--------------|-------------------------------------------------------------|-----------|--------------------------------------------------------------------------------|------------------------|------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 7, 47, 55, 139, 184, 199, 260, 271 (alt 0, 7, 47, 55, 139, 184, 199, 260, 271) | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 7, 47, 55, 139, 184, 199, 260, 271 (alt 0, 7, 47, 55, 139, 184, 199, 260, 271) | 103 | 60 | +| | TFS | TF0, bits | 0x271 (alt 1x0) (note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x139 | N/A | N/A | +| | | TF5, bits | 1x184 | N/A | N/A | +| | | TF6, bits | 1x199 | N/A | N/A | +| | | TF7, bits | 1x260 | N/A | N/A | +| | | TF8, bits | 1x271 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 873 | 0 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 437 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +7.1.146.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.1.146.1.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF0, TF0, TF0), (TF3, TF0, TF0, TF0), (TF4, TF0, TF0, TF0),
(TF5, TF0, TF0, TF0), (TF6, TF0, TF0, TF0), (TF7, TF0, TF0, TF0), (TF8, TF0, TF0, TF0)
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF0, TF0, TF1), (TF3, TF0, TF0, TF1), (TF4, TF0, TF0, TF1),
(TF5, TF0, TF0, TF1), (TF6, TF0, TF0, TF1), (TF7, TF0, TF0, TF1), (TF8, TF0, TF0, TF1) | + +## 7.1.146.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +#### 7.1.146.2 Downlink + +##### 7.1.146.2.1 Transport channel parameters + +##### 7.1.146.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 (note 2) | RAB subflow #3 (note 2) | +|--------------|---------------------------------------------|-----------|---------------------------------------|-------------------------|-------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 7, 47, 55, 139, 184, 199, 260, 271 | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 7, 47, 55, 139, 184, 199, 260, 271 | 103 | 60 | +| | TFS | TF0, bits | 1x0 (note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x139 | N/A | N/A | +| | | TF5, bits | 1x184 | N/A | N/A | +| | | TF6, bits | 1x199 | N/A | N/A | +| | | TF7, bits | 1x260 | N/A | N/A | +| | | TF8, bits | 1x271 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 873 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +###### 7.1.146.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.146.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0), (TF4,TF0,TF0,TF0),
(TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0), (TF8,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1), (TF4,TF0,TF0,TF1),
(TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1), (TF8,TF0,TF0,TF1) | + +##### 7.1.146.2.2 Physical channel parameters + +| | | | | +|---------------|------------------|---------------------------|-------| +| DPCH Downlink | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 34 | +| | | Number of data bits/frame | 510 | + +7.1.147 Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +7.1.147.1 Uplink + +7.1.147.1.1 Transport channel parameters + +7.1.147.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 (note2) | RAB subflow #3 (note2) | +|--------------|-------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271 (alt 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271) | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271 (alt 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271) | 103 | 60 | +| | TFS | TF0, bits | 0x271 (alt 1x0) (note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x63 | N/A | N/A | +| | | TF5, bits | 1x139 | N/A | N/A | +| | | TF6, bits | 1x151 | N/A | N/A | +| | | TF7, bits | 1x167 | N/A | N/A | +| | | TF8, bits | 1x184 | N/A | N/A | +| | | TF9, bits | 1x199 | N/A | N/A | +| | | TF10, bits | 1x260 | N/A | N/A | +| | | TF11, bits | 1x271 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 873 | 0 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 437 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +7.1.147.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.147.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF2, TF0, TF0, TF0), (TF3, TF0, TF0, TF0),
(TF4, TF0, TF0, TF0), (TF5, TF0, TF0, TF0), (TF6, TF0, TF0, TF0), (TF7, TF0, TF0, TF0),
(TF8, TF0, TF0, TF0), (TF9, TF0, TF0, TF0), (TF10, TF0, TF0, TF0), (TF11, TF0, TF0, TF0)
(TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF2, TF0, TF0, TF1), (TF3, TF0, TF0, TF1),
(TF4, TF0, TF0, TF1), (TF5, TF0, TF0, TF1), (TF6, TF0, TF0, TF1), (TF7, TF0, TF0, TF1),
(TF8, TF0, TF0, TF1), (TF9, TF0, TF0, TF1), (TF10, TF0, TF0, TF1), (TF11, TF0, TF0, TF1) | + +##### 7.1.147.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +#### 7.1.147.2 Downlink + +##### 7.1.147.2.1 Transport channel parameters + +##### 7.1.147.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2 (note 2) | RAB subflow #3 (note 2) | +|--------------|---------------------------------------------|------------|-----------------------------------------------------|-------------------------|-------------------------| +| RLC | Logical channel type | | DTCH | | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271 | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271 | 103 | 60 | +| | TFS | TF0, bits | 1x0 (note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x63 | N/A | N/A | +| | | TF5, bits | 1x139 | N/A | N/A | +| | | TF6, bits | 1x151 | N/A | N/A | +| | | TF7, bits | 1x167 | N/A | N/A | +| | | TF8, bits | 1x184 | N/A | N/A | +| | | TF9, bits | 1x199 | N/A | N/A | +| | | TF10, bits | 1x260 | N/A | N/A | +| | | TF11, bits | 1x271 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 873 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +##### 7.1.147.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.147.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0), (TF4,TF0,TF0,TF0),
(TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0), (TF8,TF0,TF0,TF0), (TF9,TF0,TF0,TF0),
(TF10,TF0,TF0,TF0), (TF11,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1), (TF4,TF0,TF0,TF1),
(TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1), (TF8,TF0,TF0,TF1), (TF9,TF0,TF0,TF1),
(TF10,TF0,TF0,TF1), (TF11,TF0,TF0,TF1) | + +##### 7.1.147.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 34 | +| | | Number of data bits/frame | 510 | + +7.1.148 Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.148.1 Uplink + +##### 7.1.148.1.1 Transport channel parameters + +7.1.148.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | | RAB subflow #1 | RAB subflow #2
(note 2) | RAB subflow #3
(note 2) | +|--------------|-------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------| +| RLC | Logical channel type | | | DTCH | | +| | RLC mode | | TM | TM | TM | +| | Payload sizes, bit | | 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495
(alt 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495) | 103 | 60 | +| | Max data rate, bps | | 13 200 | | | +| | TrD PDU header, bit | | 0 | | | +| MAC | MAC header, bit | | 0 | | | +| | MAC multiplexing | | N/A | | | +| Layer 1 | TrCH type | | DCH | DCH | DCH | +| | TB sizes, bit | | 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495
(alt 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495) | 103 | 60 | +| | TFS | TF0, bits | 0x495 (alt 1x0)
(note 1) | 0x103 | 0x60 | +| | | TF1, bits | 1x7 | N/A | N/A | +| | | TF2, bits | 1x47 | N/A | N/A | +| | | TF3, bits | 1x55 | N/A | N/A | +| | | TF4, bits | 1x63 | N/A | N/A | +| | | TF5, bits | 1x139 | N/A | N/A | +| | | TF6, bits | 1x151 | N/A | N/A | +| | | TF7, bits | 1x167 | N/A | N/A | +| | | TF8, bits | 1x184 | N/A | N/A | +| | | TF9, bits | 1x199 | N/A | N/A | +| | | TF10, bits | 1x260 | N/A | N/A | +| | | TF11, bits | 1x271 | N/A | N/A | +| | | TF12, bits | 1x335 | N/A | N/A | +| | | TF13, bits | 1x495 | N/A | N/A | +| | TTI, ms | | 20 | 20 | 20 | +| | Coding type | | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | | 1545 | 0 | 0 | +| | Uplink: Max number of bits/radio frame before rate matching | | 773 | 0 | 0 | +| | RM attribute | | 1-256 | 1-256 | 1-256 | + +NOTE 1: In case of using this alternative, CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see subclause 4.2.1.1 in TS 25.212). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +##### 7.1.148.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.148.1.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 28 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0), (TF4,TF0,TF0,TF0),
(TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0), (TF8,TF0,TF0,TF0), (TF9,TF0,TF0,TF0),
(TF10,TF0,TF0,TF0), (TF11,TF0,TF0,TF0), (TF12,TF0,TF0,TF0), (TF13,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1), (TF4,TF0,TF0,TF1),
(TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1), (TF8,TF0,TF0,TF1), (TF9,TF0,TF0,TF1),
(TF10,TF0,TF0,TF1), (TF11,TF0,TF0,TF1), (TF12,TF0,TF0,TF1), (TF13,TF0,TF0,TF1) | + +##### 7.1.148.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.1.148.2 Downlink + +##### 7.1.148.2.1 Transport channel parameters + +##### 7.1.148.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 24.4 16.2 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +| Higher layer | RAB/Signalling RB | RAB subflow #1 | RAB subflow #2 (note 2) | RAB subflow #3 (note 2) | +|--------------|---------------------------------------------|---------------------------------------------------------------|-------------------------|-------------------------| +| RLC | Logical channel type | DTCH | | | +| | RLC mode | TM | TM | TM | +| | Payload sizes, bit | 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495 | 103 | 60 | +| | Max data rate, bps | 13 200 | | | +| | TrD PDU header, bit | 0 | | | +| MAC | MAC header, bit | 0 | | | +| | MAC multiplexing | N/A | | | +| Layer 1 | TrCH type | DCH | DCH | DCH | +| | TB sizes, bit | 0, 7, 47, 55, 63, 139, 151, 167, 184, 199, 260, 271, 335, 495 | 103 | 60 | +| | TFS | 1x0 (note 1) | 0x103 | 0x60 | +| | TF0, bits | 1x0 (note 1) | 0x103 | 0x60 | +| | TF1, bits | 1x7 | N/A | N/A | +| | TF2, bits | 1x47 | N/A | N/A | +| | TF3, bits | 1x55 | N/A | N/A | +| | TF4, bits | 1x63 | N/A | N/A | +| | TF5, bits | 1x139 | N/A | N/A | +| | TF6, bits | 1x151 | N/A | N/A | +| | TF7, bits | 1x167 | N/A | N/A | +| | TF8, bits | 1x184 | N/A | N/A | +| | TF9, bits | 1x199 | N/A | N/A | +| | TF10, bits | 1x260 | N/A | N/A | +| | TF11, bits | 1x271 | N/A | N/A | +| | TF12, bits | 1x335 | N/A | N/A | +| | TF13, bits | 1x495 | N/A | N/A | +| | TTI, ms | 20 | 20 | 20 | +| | Coding type | CC 1/3 | CC 1/3 | CC 1/2 | +| | CRC, bit | 12 | N/A | N/A | +| | Max number of bits/TTI after channel coding | 1545 | 0 | 0 | +| | RM attribute | 1-256 | 1-256 | 1-256 | + +NOTE 1: CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]). + +NOTE 2: RAB subflows #2 and #3 do not exist in Iu interface. UTRAN establishes these additional "dummy" subflows when the RAB for EVS is assigned. + +##### 7.1.148.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.148.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 28 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0), (TF4,TF0,TF0,TF0),
(TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0), (TF8,TF0,TF0,TF0), (TF9,TF0,TF0,TF0),
(TF10,TF0,TF0,TF0), (TF11,TF0,TF0,TF0), (TF12,TF0,TF0,TF0), (TF13,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1), (TF4,TF0,TF0,TF1),
(TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1), (TF8,TF0,TF0,TF1), (TF9,TF0,TF0,TF1),
(TF10,TF0,TF0,TF1), (TF11,TF0,TF0,TF1), (TF12,TF0,TF0,TF1), (TF13,TF0,TF0,TF1) | + +##### 7.1.148.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +### 7.1.149 Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: ( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.149.1 Uplink + +##### 7.1.149.1.1 Transport channel parameters + +##### 7.1.149.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.1.1.1 + +##### 7.1.149.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +##### 7.1.149.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.149.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0), (TF2,TF0,TF0,TF0), (TF3,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0), (TF5,TF0,TF0,TF0), (TF6,TF0,TF0,TF0), (TF7,TF0,TF0,TF0)
(TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF1), (TF2,TF0,TF0,TF1), (TF3,TF0,TF0,TF1),
(TF4,TF0,TF0,TF1), (TF5,TF0,TF0,TF1), (TF6,TF0,TF0,TF1), (TF7,TF0,TF0,TF1) | + +##### 7.1.149.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +#### 7.1.149.2 Downlink + +##### 7.1.149.2.1 Transport channel parameters + +##### 7.1.149.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.2.1.1 + +##### 7.1.149.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +##### 7.1.149.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.149.2.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 16 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1) | + +##### 7.1.149.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | | Fixed | +| | Spreading factor | | 256 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 2 | +| | DPDCH | Number of data bits/slot | 16 | +| | | Number of data bits/frame | 240 | + +7.1.150 Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.150.1 Uplink + +##### 7.1.150.1.1 Transport channel parameters + +##### 7.1.150.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.1.1.1 + +###### 7.1.150.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +##### 7.1.150.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.150.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1) | + +##### 7.1.150.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-----| +| DPCH Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +#### 7.1.150.2 Downlink + +##### 7.1.150.2.1 Transport channel parameters + +##### 7.1.150.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.2.1.1 + +##### 7.1.150.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +##### 7.1.150.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.150.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1) | + +##### 7.1.150.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|--------------------------| +| DPCH
Downlink | DTX position | Fixed | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | 0 | +| | | Number of TPC bits/slot | +| | | 2 | +| DPDCH | Number of Pilot bits/slot | 4 | +| | Number of data bits/slot | 34 | +| | Number of data bits/frame | 510 | + +7.1.151 Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.151.1 Uplink + +##### 7.1.151.1.1 Transport channel parameters + +7.1.151.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.1.1.1 + +7.1.151.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +7.1.151.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.151.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1) | + +##### 7.1.151.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|-----| +| DPCH
Uplink | Min spreading factor | 64 | +| | Max number of DPDCH data bits/radio frame | 600 | +| | Puncturing Limit | 1 | + +#### 7.1.151.2 Downlink + +##### 7.1.151.2.1 Transport channel parameters + +7.1.151.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.2.1.1 + +7.1.151.2.1.2 Transport channel parameters for Interactive or background / DL: 0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +7.1.151.2.1.3 Transport channel parameters for DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.1.151.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1) | + +##### 7.1.151.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|-------| +| DPCH
Downlink | DTX position | | Fixed | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 0 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 34 | +| | | Number of data bits/frame | 510 | + +7.1.152 Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.152.1 Uplink + +##### 7.1.152.1.1 Transport channel parameters + +##### 7.1.152.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.1.1.1 + +##### 7.1.152.1.1.2 Transport channel parameters for Interactive or background / UL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.1.1.2 of [1]. + +##### 7.1.152.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.152.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 28 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF12,TF0,TF0,TF0,TF0), (TF13,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF12,TF0,TF0,TF0,TF1), (TF13,TF0,TF0,TF0,TF1) | + +##### 7.1.152.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.1.152.2 Downlink + +##### 7.1.152.2.1 Transport channel parameters + +##### 7.1.152.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 24.4 16.2 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.2.1.1 + +##### 7.1.152.2.1.2 Transport channel parameters for Interactive or background / DL:0 kbps / PS RAB + +See subclause 6.10.2.4.1.38a.2.1.2 of [1]. + +##### 7.1.152.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.152.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 28 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF12,TF0,TF0,TF0,TF0), (TF13,TF0,TF0,TF0,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF12,TF0,TF0,TF0,TF1), (TF13,TF0,TF0,TF0,TF1) | + +##### 7.1.152.2.2 Physical channel parameters + +| | | | +|------------------|------------------|---------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 64 | +| | DPCCH | Number of TFCI bits/slot | +| | | 8 | +| | | Number of TPC bits/slot | +| | DPDCH | 4 | +| | | Number of Pilot bits/slot | +| | DPDCH | 8 | +| | | Number of data bits/slot | +| | DPDCH | 60 | +| | | Number of data bits/frame | +| | | 900 | + +7.1.153 Conversational / speech / UL:(EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: +( EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or +background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for +DCCH + +### 7.1.153.1 Uplink + +##### 7.1.153.1.1 Transport channel parameters + +##### 7.1.153.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.1.1.1 + +##### 7.1.153.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +##### 7.1.153.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.153.1.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 32 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1) | + +##### 7.1.153.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.1.153.2 Downlink + +##### 7.1.153.2.1 Transport channel parameters + +##### 7.1.153.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.2.1.1 + +##### 7.1.153.2.1.2 Transport channel parameters for Interactive or background / DL: 8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.2.1.1 of [1]. + +##### 7.1.153.2.1.3 Transport channel parameters for DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.153.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 32 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1) | + +##### 7.1.153.2.2 Physical channel parameters + +| | | | +|------------------|---------------------------|--------------------------| +| DPCH
Downlink | DTX position | Flexible | +| | Spreading factor | 128 | +| | DPCCH | Number of TFCI bits/slot | +| | | 2 | +| | | Number of TPC bits/slot | +| | | 2 | +| DPDCH | Number of Pilot bits/slot | 4 | +| | Number of data bits/slot | 32 | +| | Number of data bits/frame | 480 | + +7.1.154 Conversational / speech / UL:(EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.154.1 Uplink + +##### 7.1.154.1.1 Transport channel parameters + +##### 7.1.154.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.1.1.1 + +##### 7.1.154.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +##### 7.1.154.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.154.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0),
(TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0),
(TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1),
(TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1),
(TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1) | + +##### 7.1.154.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.1.154.2 Downlink + +##### 7.1.154.2.1 Transport channel parameters + +##### 7.1.154.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.2.1.1 + +##### 7.1.154.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.2.1.1 of [1]. + +##### 7.1.154.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.154.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 36 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0),
(TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0),
(TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1),
(TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1),
(TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1) | + +##### 7.1.154.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +7.1.155 Conversational / speech / UL:(EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.1.155.1 Uplink + +##### 7.1.155.1.1 Transport channel parameters + +##### 7.1.155.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.1.1.1 + +##### 7.1.155.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +##### 7.1.155.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.155.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0), (TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1),
(TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1), (TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1) | + +##### 7.1.155.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.1.155.2 Downlink + +##### 7.1.155.2.1 Transport channel parameters + +##### 7.1.155.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.2.1.1 + +##### 7.1.155.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.2.1.1 of [1]. + +##### 7.1.155.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.155.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0), (TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1),
(TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1), (TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1) | + +##### 7.1.155.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 128 | +| | DPCCH | Number of TFCI bits/slot | 2 | +| | | Number of TPC bits/slot | 2 | +| | | Number of Pilot bits/slot | 4 | +| | DPDCH | Number of data bits/slot | 32 | +| | | Number of data bits/frame | 480 | + +7.1.156 Conversational / speech / UL:(EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL:( EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.1.156.1 Uplink + +##### 7.1.156.1.1 Transport channel parameters + +7.1.156.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.1.1.1 + +7.1.156.1.1.2 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +7.1.156.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.1.156.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 56 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF12,TF0,TF0,TF0,TF0), (TF13,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0),
(TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0),
(TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0), (TF12,TF0,TF0,TF1,TF0),
(TF13,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF12,TF0,TF0,TF0,TF1), (TF13,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1),
(TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1),
(TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1),
(TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1), (TF12,TF0,TF0,TF1,TF1),
(TF13,TF0,TF0,TF1,TF1) | + +##### 7.1.156.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +#### 7.1.156.2 Downlink + +##### 7.1.156.2.1 Transport channel parameters + +7.1.156.2.1.1 Transport channel parameters for Conversational / speech / DL: (EVS 24.4 16.2 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.2.1.1 + +7.1.156.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.2.1.1 of [1]. + +##### 7.1.156.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +##### 7.1.156.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 56 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF12,TF0,TF0,TF0,TF0), (TF13,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0),
(TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0),
(TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0), (TF12,TF0,TF0,TF1,TF0), (TF13,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF12,TF0,TF0,TF0,TF1), (TF13,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1),
(TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1),
(TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1),
(TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1), (TF12,TF0,TF0,TF1,TF1), (TF13,TF0,TF0,TF1,TF1) | + +##### 7.1.156.2.2 Physical channel parameters + +| | | | | +|------------------|------------------|---------------------------|----------| +| DPCH
Downlink | DTX position | | Flexible | +| | Spreading factor | | 64 | +| | DPCCH | Number of TFCI bits/slot | 8 | +| | | Number of TPC bits/slot | 4 | +| | | Number of Pilot bits/slot | 8 | +| | DPDCH | Number of data bits/slot | 60 | +| | | Number of data bits/frame | 900 | + +## 7.2 Combinations on S-CCPCH + +### 7.2.1 Stand-alone signalling RB for PCCH + +See subclause 6.10.2.4.3.1 of [1]. + +The minimum UE class supporting this combination is DL: 12 kbps. + +This is supported in Release '99. + +### 7.2.2 Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.2.4.3.2 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 7.2.3 Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.2.4.3.2a of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps plus support for 5 AM entities. + +This is supported in Release '99. + +### 7.2.4 Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.2.4.3.3 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 7.2.5 16 kbps RB for CTCH + SRB for CCCH + SRB for BCCH + +See subclause 6.10.2.4.3.4 of [1]. + +The minimum UE class supporting this combination is DL: 12 kbps. + +This is supported in Release '99. + +### 7.2.6 RB for CTCH + Interactive/Background 32 kbps PS RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +#### 7.2.6.1 Transport channel parameters + +##### 7.2.6.1.1 Transport channel parameters of RB for CTCH + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/signalling RB | | N/A | +| | User of Radio Bearer | | BMC | +| RLC | Logical channel type | | CTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 152 | +| | Max data rate, bps | | 15200 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 8 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 168 | +| | TFS | TF0, bits | 0x168 | +| | | TF1, bits | 1x168 | +| | TTI, ms | | 10 | +| | Coding type | | CC 1/2 | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 384 | +| | RM attribute | | 200-240 | + +##### 7.2.6.1.2 Transport channel parameters of SRB for Interactive/Background 32 kbps PS RAB + +See subclause 6.10.2.4.3.2.1.1 of [1]. + +##### 7.2.6.1.3 Transport channel parameter of SRB for PCCH + +See subclause 6.10.2.4.3.1.1.1 of [1]. + +##### 7.2.6.1.4 Transport channel parameters of SRBs for CCCH, SRB for DCCH, and SRB for BCCH + +See subclause 6.10.2.4.3.2.1.2 of [1]. + +##### 7.2.6.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 14 | +| TFCS | (SRB for PCCH, SRBs for CCCH/DCCH/BCCH, 32kbps RAB, RB for CTCH) =
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF0, TF1, TF0, TF0), (TF1, TF1, TF0, TF0), (TF0, TF2, TF0, TF0), (TF1, TF2, TF0, TF0), (TF0, TF0, TF1, TF0), (TF0, TF1, TF1, TF0), (TF0, TF0, TF0, TF1), (TF1, TF0, TF0, TF1), (TF0, TF1, TF0, TF1), (TF1, TF1, TF0, TF1), (TF0, TF2, TF0, TF1), (TF0, TF0, TF1, TF1) | + +#### 7.2.6.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 64 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 72 | +| | Number of data bits/frame | 1080 | + +### 7.2.7 Interactive/Background 16 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +#### 7.2.7.1 Transport channel parameters + +##### 7.2.7.1.1 Transport channel parameters for Interactive/Background 16 kbps PS RAB + +| Higher layer | RAB/signalling RB | | RAB | | +|--------------|---------------------------------------------|-----------|-----------------------------|--| +| | User of Radio Bearer | | Interactive/ Background RAB | | +| RLC | Logical channel type | | DTCH | | +| | RLC mode | | AM | | +| | Payload sizes, bit | | 320 | | +| | Max data rate, bps | | 16000 | | +| | AMD PDU header, bit | | 16 | | +| MAC | MAC header, bit | | 24 | | +| | MAC multiplexing | | N/A | | +| Layer 1 | TrCH type | | FACH | | +| | TB sizes, bit | | 360 | | +| | TFS | TF0, bits | 0x360 | | +| | | TF1, bits | 1x360 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI before rate matching | | 1140 | | +| | RM attribute | | 110-150 | | + +##### 7.2.7.1.2 Transport channel parameters of SRBs for CCCH, SRB for DCCH, and SRB for BCCH + +| Higher layer | RAB/signalling RB | | SRB#0 | SRB#1 | SRB#2 | SRB#3 | SRB#4 | SRB#5 | +|--------------|---------------------------------------------|-----------|--------------------------------|-------------------|-------|---------------------|--------------------|-------| +| | User of Radio Bearer | | RRc | RRc | RRc | NAS_DT
High prio | NAS_DT
Low prio | RRc | +| RLC | Logical channel type | | CCCH | DCCH | DCCH | DCCH | DCCH | BCCH | +| | RLC mode | | UM | UM | AM | AM | AM | TM | +| | Payload sizes, bit | | 152 | 136 or 120 (note) | 128 | 128 | 128 | 166 | +| | Max data rate, bps | | 15200 | 13600 or 12000 | 12800 | 12800 | 12800 | 16600 | +| | AMD/UMD/TrD PDU header, bit | | 8 | 8 | 16 | 16 | 16 | 0 | +| MAC | MAC header, bit | | 8 | 24 or 40 | 24 | 24 | 24 | 2 | +| | MAC multiplexing | | 6 logical channel multiplexing | | | | | | +| Layer 1 | TrCH type | | FACH | | | | | | +| | TB sizes, bit | | 168 | | | | | | +| | TFS | TF0, bits | 0x168 | | | | | | +| | | TF1, bits | 1x168 | | | | | | +| | | TF2, bits | 2x168 | | | | | | +| | TTI, ms | | 20 | | | | | | +| | Coding type | | CC 1/2 | | | | | | +| | CRC, bit | | 16 | | | | | | +| | Max number of bits/TTI before rate matching | | 752 | | | | | | +| | RM attribute | | 200-240 | | | | | | + +NOTE: MAC header size and PLC payload size depend on use of U-RNTI or C-RNTI. + +##### 7.2.7.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------| +| TFCS size | 4 | +| TFCS | (SRBs for CCCH/DCCH/BCCH, 16 kbps RAB) =
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1) | + +#### 7.2.7.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 128 | +| | Number of TFCI bits/slot | 2 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 38 | +| | Number of data bits/frame | 570 | + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 7.2.8 8 kbps RB for CTCH + SRB for CCCH + SRB for BCCH + +#### 7.2.8.1 Transport channel parameters + +##### 7.2.8.1.1 Transport channel parameters of 8 kbps RB for CTCH + +| | | | | +|--------------|---------------------------------------------|-----------|---------| +| Higher layer | RAB/signalling RB | | N/A | +| | User of Radio Bearer | | BMC | +| RLC | Logical channel type | | CTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 152 | +| | Max data rate, bps | | 7600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 8 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 168 | +| | TFS | TF0, bits | 0x168 | +| | | TF1, bits | 1x168 | +| | TTI, ms | | 20 | +| | Coding type | | CC 1/3 | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 576 | +| | RM attribute | | 200-240 | + +##### 7.2.8.1.2 Transport channel parameters of SRB for CCCH and SRB for BCCH + +| | | | | | +|--------------|---------------------------------------------|-----------|--------------------------------|-------| +| Higher layer | RAB/signalling RB | | SRB#0 | SRB#5 | +| | User of Radio Bearer | | RRC | RRC | +| RLC | Logical channel type | | CCCH | BCCH | +| | RLC mode | | UM | TM | +| | Payload sizes, bit | | 152 | 166 | +| | Max data rate, bps | | 7600 | 8300 | +| | AMD/UMD/TrD PDU header, bit | | 8 | 0 | +| MAC | MAC header, bit | | 8 | 2 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | FACH | | +| | TB sizes, bit | | 168 | | +| | TFS | TF0, bits | 0x168 | | +| | | TF1, bits | 1x168 | | +| | TTI, ms | | 20 | | +| | Coding type | | CC 1/3 | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI before rate matching | | 576 | | +| | RM attribute | | 200-240 | | + +##### 7.2.8.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------| +| TFCS size | 3 | +| TFCS | (SRBs for CCCH/ BCCH, RB for CTCH) =
(TF0, TF0), (TF1, TF0), (TF0, TF1) | + +#### 7.2.8.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 256 | +| | Number of TFCI bits/slot | 2 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 18 | +| | Number of data bits/frame | 270 | + +The minimum UE class supporting this combination is DL: 12 kbps. + +This is supported in Release '99. + +### 7.2.9 Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +#### 7.2.9.1 Transport channel parameters + +##### 7.2.9.1.1 Transport channel parameters for Interactive or background / 32 kbps / PS RAB + 32 kbps / PS RAB (RLC size 320) + +See subclause 6.10.2.4.3.2a.1.1 of [1] + +##### 7.2.9.1.2 Transport channel parameters for Interactive or background / 32 kbps / PS RAB + 32 kbps / PS RAB (RLC size 640) + +| Higher Layer | RAB/Signalling RB | | RAB | RAB | +|--------------|---------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 640 | 640 | +| | Max data rate, bps | | 32000 | 32000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 24 | 24 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | FACH | | +| | TB sizes, bit | | 680 | | +| | TFS | TF0, bits | 0x680 | | +| | | TF1, bits | 1x680 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 2100 | | +| | RM attribute | | 110- 150 | | + +##### 7.2.9.1.3 Transport channel parameters of SRB for PCCH + +See subclause 6.10.2.4.3.1.1 of [1] + +##### 7.2.9.1.4 Transport channel parameters of SRBs for CCCH, SRB for DCCH, and SRB for BCCH + +See subclause 6.10.2.4.3.2.1.2 of [1] + +##### 7.2.9.1.5 TFCS + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 7, 8, 9 or 10 for 240 bits PCH TrBlk size and TF3 not used
(alt 7, 8, 9 or 10, 11 or 12 for 80 bits PCH TrBlk size and TF3 not used)
(alt 7, 8, 9, 10 or 11 for 240 bits PCH TrBlk size and TF3 used)
(alt. 7, 8, 9, 10, 11, 12, 13 or 14 for 80 bits PCH TrBlk size and TF3 used) | +| TFCS | (SRB for PCCH, SRBs for CCCH/ DCCH/ BCCH, 32 kbps RAB (RLC size 320), 32 kbps RAB (RLC size 640)) =
(TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF0, TF1, TF0, TF0), (TF1, TF1, TF0, TF0), (TF0, TF2, TF0, TF0), [TF1, TF2, TF0, TF0] (see note), (TF0, TF0, TF1, TF0), [TF0, TF1, TF1, TF0] (see note), (TF0, TF0, TF0, TF1), [TF0, TF1, TF0, TF1] (see note) for 240 bits PCH TrBlk size and TF3 not used
(alt. (TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF0, TF1, TF0, TF0), (TF1, TF1, TF0, TF0), (TF0, TF2, TF0, TF0), [TF1, TF2, TF0, TF0] (see note), (TF0, TF0, TF1, TF0), [TF1, TF0, TF1, TF0] (see note), [TF0, TF1, TF1, TF0] (see note), (TF0, TF0, TF0, TF1), [TF1, TF0, TF0, TF1] (see note), [TF0, TF1, TF0, TF1] (see note) for 80 bits PCH TrBlk size and TF3 not used
(alt. (TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF0, TF1, TF0, TF0), (TF1, TF1, TF0, TF0), (TF0, TF2, TF0, TF0), [TF1, TF2, TF0, TF0] (see note), [TF0, TF3, TF0, TF0] (see note), (TF0, TF0, TF1, TF0), [TF0, TF1, TF1, TF0] (see note), (TF0, TF0, TF0, TF1), [TF0, TF0, TF0, TF1] (see note) for 240 bits PCH TrBlk size and TF3 used
(alt. (TF0, TF0, TF0, TF0), (TF1, TF0, TF0, TF0), (TF0, TF1, TF0, TF0), (TF1, TF1, TF0, TF0), (TF0, TF2, TF0, TF0), [TF1, TF2, TF0, TF0] (see note), [TF0, TF3, TF0, TF0] (see note), [TF1, TF3, TF0, TF0] (see note), (TF0, TF0, TF1, TF0), [TF1, TF0, TF1, TF0] (see note), [TF0, TF1, TF1, TF0] (see note), (TF0, TF0, TF0, TF1), [TF1, TF0, TF0, TF1] (see note), [TF0, TF1, TF0, TF1] (see note) for 80 bits PCH TrBlk size and TF3 used) | +| NOTE: These TFCS are available only if SCCPCH can be allocated bigger Tx power than required Tx power for TFC of (TF0, TF2, TF0). | | + +#### 7.2.9.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 64 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 72 | +| | Number of data bits/frame | 1080 | + +The minimum UE class supporting this combination is DL: 32 kbps plus support for 5 AM entities. + +### 7.2.10 258.4 kbps RB for MTCH with 40 ms TTI + +#### 7.2.10.1 Transport channel parameters + +##### 7.2.10.1.1 Transport channel parameters for 258.4 kbps PS RAB + +| | | | +|--------------|---------------------------------------------|-----------------------------------------| +| Higher layer | RAB/signalling RB | RAB | +| | User of Radio Bearer | MBMS | +| RLC | Logical channel type | MTCH | +| | RLC mode | UM | +| | Payload sizes, bit | 968, 1272, 2264, 2584, 3544, 3864, 4824 | +| | Max data rate, bps | 258 400 | +| | UMD PDU header, bit | 8 | +| MAC | MAC header, bit | 8 | +| | MAC multiplexing | N/A | +| Layer 1 | TrCH type | FACH | +| | TB sizes, bit | 984, 1288, 2280, 2600, 3560, 3880, 4840 | +| | TFS [1] | 0x984 | +| | | 1x984 | +| | | 1x1288 | +| | | 1x2280 | +| | | 1x2600 | +| | | 1x3560 | +| | | 1x3880 | +| | | 1x4840 | +| | | 2x2600 | +| | | 5x1288 | +| | | 3x2600 | +| | | 7x1288 | +| | | 4x2600 | +| | TTI, ms | 40 | +| | Coding type | TC | +| | CRC, bit | 16 | +| | Max number of bits/TTI before rate matching | 31 464 | +| | RM attribute | n/a | + +NOTE 1 (informative): The corresponding RTP payload sizes that fit most ideally into the transport formats are 936, 2232, 3528, 4792, 5136, 6328, 7720, 8872, and 10304 bits: + +| TF | RTP packet size and header status | +|--------|-------------------------------------------------------------------------------------------------------------------| +| 0x984 | No data | +| 1x984 | 936 (compressed header) | +| 1x1288 | 936 (uncompressed header) | +| 1x2280 | 2232 (compressed header) | +| 1x2600 | 2232(uncompressed header) | +| 1x3560 | 3512(compressed header) | +| 1x3880 | 3528(uncompressed header) | +| 1x4840 | 4792 (compressed header) | +| 2x2600 | 5136 (compressed header) | +| 5x1288 | 4792 (uncompressed header)
6328(compressed header) | +| 3x2600 | 6328(uncompressed header)
7720(compressed header) | +| 7x1288 | 7720(uncompressed header)
8872 (compressed header) | +| 4x2600 | 8872 (uncompressed header)
10304 (compressed header)
10304 (uncompressed header, with overflow to next TTI) | + +This table is not absolutely optimal; for instance, a 6328-bit RTP packet with an uncompressed header could be more closely accommodated with a TF of 3x2280, or exactly with a TF of 2x3344 (requiring a new TB size and matching PDU size). However, because uncompressed headers are infrequent, we have dimensioned the larger TB sizes only for the compressed-header case, accepting that the occasional uncompressed header on a large packet will involve a waste of bandwidth (small in proportion to the large packet size). + +##### 7.2.10.1.2 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------| +| TFCS size | 13 | +| TFCS | 258.4 kbps RAB =TF0, TF1, TF2, TF3, TF4, TF5, TF6, TF7, TF8, TF9, TF10, TF11, TF12 | + +#### 7.2.10.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 8 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 632 | +| | Number of data bits/frame | 9480 | + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +### 7.2.11 129.2 kbps RB for MTCH with 40 ms TTI + +#### 7.2.11.1 Transport channel parameters + +##### 7.2.11.1.1 Transport channel parameters for 129.2 kbps PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|-----------------------------------------| +| Higher layer | RAB/signalling RB | | RAB | +| | User of Radio Bearer | | MBMS | +| RLC | Logical channel type | | MTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 968, 1272, 2280, 2584, 3544, 3864, 4824 | +| | Max data rate, bps | | 129 200 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 8 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 984, 1288, 2280, 2600, 3560, 3880, 4840 | +| | TFS [1] | TF0, bits | 0x984 | +| | | TF1, bits | 1x984 | +| | | TF2, bits | 1x1288 | +| | | TF3, bits | 1x2280 | +| | | TF4, bits | 1x2600 | +| | | TF5, bits | 1x3560 | +| | | TF6, bits | 1x3880 | +| | | TF7, bits | 1x4840 | +| | | TF8, bits | 2x2600 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 15 732 | +| | RM attribute | | n/a | + +NOTE 1 (informative): The corresponding RTP payload sizes that fit most ideally into the transport formats are 936, 2232, 3528, 4792, and 5136 bits: + +| TF | RTP packet size and header status | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------| +| 0x984 | No data | +| 1x984 | 936 (compressed header) | +| 1x1288 | 936 (uncompressed header) | +| 1x2280 | 2232 (compressed header) | +| 1x2600 | 2232 (uncompressed header) | +| 1x3560 | 3512 (compressed header) | +| 1x3880 | 3528 (uncompressed header) | +| 1x4840 | 4792 (compressed header) | +| 2x2600 | 5136 (compressed header)
4792 (uncompressed header, with overflow to next TTI)
5056 (uncompressed header, with overflow to next TTI) | + +The overflow in the case of a 4792-bit RTP packet with uncompressed header could be avoided by reducing the packet size to 4776 (hence reducing the corresponding TB size to 4824 and the PDU size to 4808), at the cost of a small amount of application bandwidth. + +##### 7.2.11.1.2 TFCS + +| | | +|-----------|-------------------------------------------------------------| +| TFCS size | 9 | +| TFCS | 129.2kbps RAB = TF0, TF1, TF2, TF3, TF4, TF5, TF6, TF7, TF8 | + +#### 7.2.11.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 8 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 632 | +| | Number of data bits/frame | 9480 | + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +### 7.2.12 129.2 kbps RB for MTCH with 80 ms TTI + +#### 7.2.12.1 Transport channel parameters + +##### 7.2.12.1.1 Transport channel parameters for 129.2 kbps PS RAB + +| | | | | +|--------------|---------------------------------------------|------------|-----------------------------------------| +| Higher layer | RAB/signalling RB | | RAB | +| | User of Radio Bearer | | MBMS | +| RLC | Logical channel type | | MTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 968, 1272, 2280, 2584, 3544, 3864, 4824 | +| | Max data rate, bps | | 129 200 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 8 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 984, 1288, 2280, 2600, 3560, 3880, 4840 | +| | TFS [1] | TF0, bits | 0x984 | +| | | TF1, bits | 1x984 | +| | | TF2, bits | 1x1288 | +| | | TF3, bits | 1x2280 | +| | | TF4, bits | 1x2600 | +| | | TF5, bits | 1x3560 | +| | | TF6, bits | 1x3880 | +| | | TF7, bits | 1x4840 | +| | | TF8, bits | 2x2600 | +| | | TF9, bits | 5x1288 | +| | | TF10, bits | 3x2600 | +| | | TF11, bits | 7x1288 | +| | | TF12, bits | 4x2600 | +| | TTI, ms | | 80 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 31 464 | +| | RM attribute | | n/a | + +NOTE 1 (informative): The corresponding RTP payload sizes that fit most ideally into the transport formats are 936, 2232, 3528, 4792, 5136, 6328, 7720, 8872, and 10304 bits: + +| TF | RTP packet size and header status | +|--------|-------------------------------------------------------------------------------------------------------------------| +| 0x984 | No data | +| 1x984 | 936 (compressed header) | +| 1x1288 | 936 (uncompressed header) | +| 1x2280 | 2232 (compressed header) | +| 1x2600 | 2232 (uncompressed header) | +| 1x3560 | 3512 (compressed header) | +| 1x3880 | 3528 (uncompressed header) | +| 1x4840 | 4792 (compressed header) | +| 2x2600 | 5136 (compressed header) | +| 5x1288 | 4792 (uncompressed header)
6328 (compressed header) | +| 3x2600 | 6328 (uncompressed header)
7720 (compressed header) | +| 7x1288 | 7720 (uncompressed header)
8872 (compressed header) | +| 4x2600 | 8872 (uncompressed header)
10304 (compressed header)
10304 (uncompressed header, with overflow to next TTI) | + +This mapping is suboptimal in the same ways identified in subclause 7.2.10.1. + +##### 7.2.12.1.2 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------| +| TFCS size | 13 | +| TFCS | 129.2 kbps RAB =TF0, TF1, TF2, TF3, TF4, TF5, TF6, TF7, TF8, TF9, TF10, TF11, TF12 | + +#### 7.2.12.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 16 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 312 | +| | Number of data bits/frame | 4680 | + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +### 7.2.13 64.6 kbps RB for MTCH with 80 ms TTI + +#### 7.2.13.1 Transport channel parameters + +##### 7.2.13.1.1 Transport channel parameters for 64.6 kbps PS RAB + +| | | | | +|--------------|---------------------------------------------|-----------|-----------------------------------------| +| Higher layer | RAB/signalling RB | | RAB | +| | User of Radio Bearer | | MBMS | +| RLC | Logical channel type | | MTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 968, 1272, 2280, 2584, 3544, 3864, 4824 | +| | Max data rate, bps | | 64 600 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 8 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 984, 1288, 2280, 2600, 3560, 3880, 4840 | +| | TFS [1] | TF0, bits | 0x984 | +| | | TF1, bits | 1x984 | +| | | TF2, bits | 1x1288 | +| | | TF3, bits | 1x2280 | +| | | TF4, bits | 1x2600 | +| | | TF5, bits | 1x3560 | +| | | TF6, bits | 1x3880 | +| | | TF7, bits | 1x4840 | +| | | TF8, bits | 2x2600 | +| | TTI, ms | | 80 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 15 720 | +| | RM attribute | | n/a | + +NOTE 1 (informative): The corresponding RTP payload sizes that fit most ideally into the transport formats are 936, 2232, 3528, 4792, and 5136 bits: + +| TF | RTP packet size and header status | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------| +| 0x984 | No data | +| 1x984 | 936 (compressed header) | +| 1x1288 | 936 (uncompressed header) | +| 1x2280 | 2232 (compressed header) | +| 1x2600 | 2232 (uncompressed header) | +| 1x3560 | 3512 (compressed header) | +| 1x3880 | 3528 (uncompressed header) | +| 1x4840 | 4792 (compressed header) | +| 2x2600 | 5136 (compressed header)
4792 (uncompressed header, with overflow to next TTI)
5136 (uncompressed header, with overflow to next TTI) | + +As in subclause 7.2.11.1, the overflow in the case of a 4792-bit RTP packet with uncompressed header could be avoided by reducing the packet, TB, and PDU sizes slightly in this case. + +##### 7.2.13.1.2 TFCS + +| | | +|-----------|------------------------------------------------------------| +| TFCS size | 9 | +| TFCS | 64.6 kbps RAB =TF0, TF1, TF2, TF3, TF4, TF5, TF6, TF7, TF8 | + +#### 7.2.13.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 32 | +| | Number of TFCI bits/slot | 8 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 152 | +| | Number of data bits/frame | 2280 | + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +### 7.2.14 64.8kbps RB for MTCH with 80 ms TTI (alternative config) + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +See subclause 6.10.2.4.3.5 of [1]. + +7.2.14.1 Void + +7.2.14.2 Void + +### 7.2.15 129.6 kbps RB for MTCH with 80 ms TTI (alternative config) + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +See subclause 6.10.2.4.3.6 of [1]. + +7.2.15.1 Void + +7.2.15.2 Void + +### 7.2.16 259.2 kbps RB for MTCH with 40 ms TTI (alternative config) + +The minimum UE class supporting this combination is MBMS minimum capability. + +This is supported in Release 6. + +See subclause 6.10.2.4.3.7 of [1]. + +7.2.16.1 Void + +7.2.16.2 Void + +### 7.2.17 7.6 kbps signalling RB for MCCH + +This is supported in Release 6 by UEs with capability for MBMS. + +See subclause 6.10.2.4.3.8 of [1]. + +7.2.17.1 Void + +7.2.17.2 Void + +### 7.2.18 6.4 kbps SRB for MCCH + +7.2.18.1 Transport channel parameters + +7.2.18.1.1 Transport channel parameters for 6.4 kbps SRB for MCCH + +| | | | | +|--------------|---------------------------------------------|-----------|---------------------------------| +| Higher layer | RAB/signalling RB | | SRB | +| | User of Radio Bearer | | MBMS | +| RLC | Logical channel type | | MCCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 64 | +| | Max data rate, bps | | 6 400 | +| | UM PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | No logical channel multiplexing | +| Layer 1 | TrCH type | | FACH | +| | TB sizes, bit | | 72 | +| | TFS | TF0, bits | 0 x72 | +| | | TF1, bits | 1x72 | +| | TTI, ms | | 10 | +| | Coding type | | CC 1/3 | +| | CRC, bit | | 16 | +| | Max number of bits/TTI before rate matching | | 288 | +| | RM attribute | | n/a | + +7.2.18.1.2 TFCS + +| | | +|-----------|-------------------------| +| TFCS size | 2 | +| TFCS | 6.4 kbps SRB = TF0, TF1 | + +7.2.18.2 Physical channel parameters + +| | | | +|--------|---------------------------|----------| +| SCCPCH | DTX position | Flexible | +| | Spreading factor | 256 | +| | Number of TFCI bits/slot | 2 | +| | Number of Pilot bits/slot | 0 | +| | Number of data bits/slot | 18 | +| | Number of data bits/frame | 270 | + +## 7.3 Combinations on PRACH + +### 7.3.1 Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.2.4.4.1 of [1]. Using Release '99 configuration of SRB#0. + +The minimum UE class supporting this combination is UL: 12 kbps. + +This is supported in Release '99. + +### 7.3.2 Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.2.4.4.2 of [1]. Using Release '99 configuration of SRB#0. + +The minimum UE class supporting this combination is UL: 12 kbps plus support for 5 AM entities and in addition for the alternative configuration 'Maximum number of DPDCH bits transmitted per 10 ms' = 1200. + +This is supported in Release '99 + +### 7.3.3 Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.2.4.4.1 of [1]. Using Release 6 configuration of SRB#0. + +The minimum UE class supporting this combination is UL: 12 kbps. + +This is supported in Release 6. + +### 7.3.4 Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.2.4.4.2 of [1]. Using Release 6 configuration of SRB#0. + +The minimum UE class supporting this combination is UL: 12 kbps plus support for 5 AM entities and in addition for the alternative configuration 'Maximum number of DPDCH bits transmitted per 10 ms' = 1200. + +This is supported in Release 6. + +## 7.4 Radio Bearer and Radio Bearer Combinations on DPCH and HS-PDSCH + +In the following tables for the references to [1], the details of the configuration are defined there. + +### 7.4.1 RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.1.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.26.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 7.4.1.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +| | | | | | + +| | | | | | +|-------------------|---------------------------|-----------------------------|---------------------------|--| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +#### 7.4.1b Void + +### 7.4.2 RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.2.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.34.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.2.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|-----------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +### 7.4.3 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. The minimum UE class to support the alternative UL physical configuration + +2 is UL: 384kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +This is supported in Release 5. + +#### 7.4.3.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-----------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.5.3.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 7.4.3.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.5.3.2 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +### 7.4.3a RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.3a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.5.3a.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 7.4.3a.2 Downlink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.3a.2 of [1] | | | | +| Physical Channel | | | | | + +### 7.4.4 RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 64 kbps, DL on HS-PDSCH: category 11. The minimum UE class to support the alternative UL configuration is DL: 768 kbps plus support for 'Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant' = 20480 and 'Maximum sum of number of bits of all turbo coded transport blocks being transmitted at an arbitrary time instant' = 20480. + +This is supported in Release 5. + +#### 7.4.4.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|----------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.4.1of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.4.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.4.2 of [1] | | | | +| Physical Channel | | | | | + +### 7.4.4a RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps, DL on DPCH: 64 kbps, DL on HS-PDSCH: category 11. The minimum UE class to support the alternative UL combination (40ms TTI) is UL: 384kbps. + +This is supported in Release 5. + +#### 7.4.4a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.4a.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.4a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|------------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.4a.2 of [1] | | | | +| Physical Channel | | | | | + +### 7.4.5 RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH. + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.5.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | | | | | + +| | | +|------------------|-----------------------| +| Physical Channel | 6.10.2.4.5.5.1 of [1] | +|------------------|-----------------------| + +#### 7.4.5.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.5.2 of [1] | | | | +| Physical Channel | | | | | + +7.4.5a RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.5a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.5a.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.5a.2 Downlink + +See subclause 6.10.2.4.5.5a.2 of [1]. + +7.4.6 Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.6.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.28.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.6.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|-----------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +7.4.7 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.7.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|-------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.38i.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.7.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| + +| | | | | | +|-------------------|----------------------------|-----------------------------|---------------------------------------|--| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +7.4.7a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.7a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 7.1.51a.1 | | | | +| Physical Channel | | | | | + +#### 7.4.7a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|---------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +7.4.8 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 64, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.8.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------------------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.1.1.1 of [1]
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.8.1.1 | | | | +| Physical Channel | See 7.4.8.1.2 | | | | + +##### 7.4.8.1.1 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 60 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF5,TF4,TF1,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0), (TF5,TF4,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF3,TF2,TF0,TF2,TF0), (TF4,TF3,TF0,TF2,TF0), (TF5,TF4,TF1,TF2,TF0),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF5,TF4,TF1,TF3,TF0),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0), (TF5,TF4,TF1,TF4,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF3,TF2,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF1), (TF5,TF4,TF1,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF5,TF4,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1), (TF5,TF4,TF1,TF2,TF1),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF3,TF2,TF0,TF3,TF1), (TF4,TF3,TF0,TF3,TF1), (TF5,TF4,TF1,TF3,TF1),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1), (TF5,TF4,TF1,TF4,TF1) | + +##### 7.4.8.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.92 | + +#### 7.4.8.2 Downlink + +| | Radio Bearer | Radio Bearer | Signalling Radio | Signalling Radio | +|--|--------------|--------------|------------------|------------------| +|--|--------------|--------------|------------------|------------------| + +| | on DPCH | on HS-PDSCH | Bearer on DPCH | Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|----------------------------------------------|--------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.8a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 64, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.8a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|----------------------------------------------------------|---------------------------------------|---------------------------------|---------------------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1]
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.8.1.1 | | | | +| Physical Channel | See 7.4.8.1.2 | | | | + +#### 7.4.8a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +### 7.4.9 Void + +### 7.4.10 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL:128 DL: [Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.10.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.44.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.10.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|-----------------------------|---------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.4.11 Void + +### 7.4.12 RB for Conversational / unknown / UL:64 DL:64 kbps / CS RAB + RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH. + +The minimum UE classes supporting this combination are UL: 384kbps, DL on DPCH: 64 kbps, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.12.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|------------------------|---------------------------------------|---------------------------------|---------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.53.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.12.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|---------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.13.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.13.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.13.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.13.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +### 7.4.13 RB for Conversational / unknown / UL:42.8 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + RB for interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.13.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|--|----------------------|---------------------------------------|---------------------------------|---------------------------------------------------| +|--|----------------------|---------------------------------------|---------------------------------|---------------------------------------------------| + +| | | +|-------------------|------------------------| +| Transport Channel | 6.10.2.4.1.60.1 of [1] | +| TFCS | | +| Physical Channel | | + +#### 7.4.13.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|--------------------------|---------------------------------------|-------------------------------------| +| Transport Channel | | See 7.4.13.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | 6.10.2.4.1.2.2.2 of [1] | 6.10.2.4.5.2.2.2 in [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: already included in Physical Channel Definition of Radio Bearer on DPCH + +##### 7.4.13.2.1 Transport channel parameters + +##### 7.4.13.2.1.1 Transport channel parameters for HS-DSCH + +###### 7.4.13.2.1.1.1 MAC-d flow parameters for conversational / unknown DL:[max bit rate depending on UE category] / PS RAB + +| | | Alt 1 MAC-hs
(Rel-5 and later releases) | Alt 2 MAC-ehs
(Rel-7 and later releases) | +|--------------|-----------------------------------|--------------------------------------------|---------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 920, 304, 96 | Flexible up to 12000 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | | +| MAC | MAC-d header, bit | 0 | | +| | MAC multiplexing | N/A | | +| | MAC-d PDU size, bit | 928, 312, 104 | Flexible | +| | MAC-hs Type | MAC-hs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | +| Layer 1 | TrCH type | HS-DSCH | | +| | TTI | 2 ms | | +| | Coding type | TC | | +| | CRC, bit | 24 | | +| | Applicable modulation scheme | QPSK, 16QAM | QPSK, 16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | +| | | | | + +NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). + +7.4.13.2.1.1.2 MAC-d flow parameters for interactive or background DL:[max bit rate depending on UE category] / PS RAB + +See subclause 6.10.2.4.5.1.2.1.1.1 of [1]. + +### 7.4.14 RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps plus support for 'Maximum number of DPDCH bits transmitted per 10 ms' = 4800 and 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL on DPCH: 32 kbps plus support for HS-PDSCH and 'Maximum number of AM entities' = 5, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.14.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------------------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.1.58.1.1.1 of [1]
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.14.1.1 | | | | +| Physical Channel | See 7.4.14.1.2 | | | | + +7.4.14.1.1 Transport channel parameters + +7.4.14.1.1.1 Void + +7.4.14.1.1.2 Void + +7.4.14.1.1.3 Void + +7.4.14.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (16 kbps RAB, 128 kbps RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0), (TF0, TF2, TF0), (TF1, TF2, TF0), (TF0, TF3, TF0), (TF1, TF3, TF0), (TF0, TF4, TF0), (TF1, TF4, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF0, TF2, TF1), (TF1, TF2, TF1), (TF0, TF3, TF1), (TF1, TF3, TF1), (TF0, TF4, TF1), (TF1, TF4, TF1) | + +7.4.14.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.8 | + +#### 7.4.14.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------------|-------------------------------------| +| Transport Channel | | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | 6.10.2.4.1.2.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +##### 7.4.14.2.1 Transport channel parameters + +##### 7.4.14.2.1.1 Transport channel parameters for HS-DSCH + +###### 7.4.14.2.1.1.1 MAC-d flow parameters for Streaming / unknown / DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + +| | | Alt 1
Fixed RLC + MAC-hs
(Rel-5 and later releases) | Alt2
Fixed RLC + MAC-ehs
(Rel-7 and later releases) | Alt 3
Flexible RLC + MAC-ehs
(Rel-7 and later releases) | +|--------------|-----------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | RAB | | | +| RLC | Logical channel type | DTCH | | | +| | RLC mode | AM | | | +| | Payload sizes, bit | 320 (alt. 640) | 320 (alt. 640) | Flexible up to 12000 | +| | Max data rate, bps | depends on UE category
NOTE1 | | | +| | AMD PDU header, bit | 16 | | | +| MAC | MAC-d header, bit | 0 | | | +| | MAC multiplexing | N/A | | | +| | MAC-d PDU size, bit | 336 (alt. 656) | 336 (alt. 656) | Flexible | +| | MAC-hs Type | MAC-hs | MAC-ehs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | 24 | +| Layer 1 | TrCH type | HS-DSCH | | | +| | TTI | 2 ms | | | +| | Coding type | TC | | | +| | CRC, bit | 24 | | | +| | Applicable modulation scheme | QPSK, 16QAM | QPSK, 16QAM, 64QAM | QPSK, 16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | Yes | + +NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). + +###### 7.4.14.2.1.1.2 MAC-d flow parameters for Interactive or background / DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + +See subclause 6.10.2.4.5.1.2.1.1.1 of [1]. + +7.4.14.2.1.2 Void + +7.4.15 RB for Streaming / unknown / UL:64 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +Note that the streaming RAB is not supported by all number of processes for UE category 1 and 11. + +The minimum UE classes supporting this combination are UL: 384kbps, DL on DPCH: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Total RLC AM buffer size' = 50, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +7.4.15.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.15.1.1.4 | | | | +| Physical Channel | See 7.4.15.1.2 | | | | + +7.4.15.1.1 Transport channel parameters + +7.4.15.1.1.1 Transport channel parameters for Streaming / unknown / UL:64 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-------------------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 64000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Uplink: Max number of bits/radio frame before rate matching | | 2019 | +| | RM attribute | | 125-165 | + +7.4.15.1.1.2 Void + +7.4.15.1.1.3 Void + +7.4.15.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (64 kbps RAB, 128 kbps RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF0, TF1, TF0), (TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0),
(TF0, TF2, TF0), (TF1, TF2, TF0), (TF2, TF2, TF0), (TF3, TF2, TF0), (TF4, TF2, TF0),
(TF0, TF3, TF0), (TF1, TF3, TF0), (TF2, TF3, TF0), (TF3, TF3, TF0), (TF4, TF3, TF0),
(TF0, TF4, TF0), (TF1, TF4, TF0), (TF2, TF4, TF0), (TF3, TF4, TF0), (TF4, TF4, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1),
(TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2, TF1), (TF3, TF2, TF1), (TF4, TF2, TF1),
(TF0, TF3, TF1), (TF1, TF3, TF1), (TF2, TF3, TF1), (TF3, TF3, TF1), (TF4, TF3, TF1),
(TF0, TF4, TF1), (TF1, TF4, TF1), (TF2, TF4, TF1), (TF3, TF4, TF1), (TF4, TF4, TF1) | + +7.4.15.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 4 | +| | Max number of DPDCH data bits/radio frame | 9600 | +| | Puncturing Limit | 1 | + +7.4.15.2 Downlink + +| | Radio Bearer
on DPCH | Radio Bearer
on HS-PDSCH | Signalling Radio
Bearer
on DPCH | Signalling Radio
Bearer
on HS-PDSCH | +|----------------------|---------------------------|-----------------------------|---------------------------------------|-------------------------------------------| +| Transport
Channel | | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical
Channel | 6.10.2.4.1.2.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.16 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 128, DL on DPCH: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Total RLC AM buffer size' = 50, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.16.1 + +##### Uplink + +| | Radio Bearer
on DPCH | (reserved for Radio
Bearer
on E-DCH ) | Signalling Radio
Bearer
on DPCH | ( reserved for Signalling
Radio Bearer
on E-DCH ) | +|----------------------|----------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------------------| +| Transport
Channel | 6.10.2.4.1.4a.1.1.1 of [1]
6.10.2.4.1.58.1.1.1 of [1]
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.16.1.1.5 | | | | +| Physical
Channel | See 7.4.16.1.2 | | | | + +##### 7.4.16.1.1 Transport channel parameters + +7.4.16.1.1.1 Void + +7.4.16.1.1.2 Void + +7.4.16.1.1.3 Void + +7.4.16.1.1.4 Void + +7.4.16.1.1.5 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 120 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 128 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF5,TF4,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0),
(TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF5,TF4,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0),
(TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF5,TF4,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF5,TF4,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF0,TF2,TF0),
(TF3,TF2,TF0,TF0,TF2,TF0), (TF4,TF3,TF0,TF0,TF2,TF0), (TF5,TF4,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF1,TF2,TF0), (TF1,TF0,TF0,TF1,TF2,TF0), (TF2,TF1,TF0,TF1,TF2,TF0),
(TF3,TF2,TF0,TF1,TF2,TF0), (TF4,TF3,TF0,TF1,TF2,TF0), (TF5,TF4,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF0,TF3,TF0),
(TF3,TF2,TF0,TF0,TF3,TF0), (TF4,TF3,TF0,TF0,TF3,TF0), (TF5,TF4,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF1,TF3,TF0), (TF1,TF0,TF0,TF1,TF3,TF0), (TF2,TF1,TF0,TF1,TF3,TF0),
(TF3,TF2,TF0,TF1,TF3,TF0), (TF4,TF3,TF0,TF1,TF3,TF0), (TF5,TF4,TF1,TF1,TF3,TF0),
(TF0,TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF0,TF4,TF0),
(TF3,TF2,TF0,TF0,TF4,TF0), (TF4,TF3,TF0,TF0,TF4,TF0), (TF5,TF4,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF1,TF4,TF0), (TF1,TF0,TF0,TF1,TF4,TF0), (TF2,TF1,TF0,TF1,TF4,TF0),
(TF3,TF2,TF0,TF1,TF4,TF0), (TF4,TF3,TF0,TF1,TF4,TF0), (TF5,TF4,TF1,TF1,TF4,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1),
(TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF5,TF4,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF5,TF4,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF0,TF1,TF1),
(TF3,TF2,TF0,TF0,TF1,TF1), (TF4,TF3,TF0,TF0,TF1,TF1), (TF5,TF4,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF0,TF1,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1,TF1), (TF4,TF3,TF0,TF1,TF1,TF1), (TF5,TF4,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF0,TF2,TF1),
(TF3,TF2,TF0,TF0,TF2,TF1), (TF4,TF3,TF0,TF0,TF2,TF1), (TF5,TF4,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF1,TF2,TF1), (TF1,TF0,TF0,TF1,TF2,TF1), (TF2,TF1,TF0,TF1,TF2,TF1),
(TF3,TF2,TF0,TF1,TF2,TF1), (TF4,TF3,TF0,TF1,TF2,TF1), (TF5,TF4,TF1,TF1,TF2,TF1),
(TF0,TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF0,TF3,TF1),
(TF3,TF2,TF0,TF0,TF3,TF1), (TF4,TF3,TF0,TF0,TF3,TF1), (TF5,TF4,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF1,TF3,TF1), (TF1,TF0,TF0,TF1,TF3,TF1), (TF2,TF1,TF0,TF1,TF3,TF1),
(TF3,TF2,TF0,TF1,TF3,TF1), (TF4,TF3,TF0,TF1,TF3,TF1), (TF5,TF4,TF1,TF1,TF3,TF1),
(TF0,TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF0,TF4,TF1),
(TF3,TF2,TF0,TF0,TF4,TF1), (TF4,TF3,TF0,TF0,TF4,TF1), (TF5,TF4,TF1,TF0,TF4,TF1),
(TF0,TF0,TF0,TF1,TF4,TF1), (TF1,TF0,TF0,TF1,TF4,TF1), (TF2,TF1,TF0,TF1,TF4,TF1),
(TF3,TF2,TF0,TF1,TF4,TF1), (TF4,TF3,TF0,TF1,TF4,TF1), (TF5,TF4,TF1,TF1,TF4,TF1) | + +##### 7.4.16.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 8 | +| | Max number of DPDCH data bits/radio frame | 4800 | +| | Puncturing Limit | 0.72 | + +#### 7.4.16.2 Downlink + +| | Radio Bearer
on DPCH | Radio Bearer
on HS-DPCH | Signalling Radio
Bearer | Signalling Radio
Bearer | +|--|-------------------------|----------------------------|----------------------------|----------------------------| +|--|-------------------------|----------------------------|----------------------------|----------------------------| + +| | | | on DPCH | on HS-DPCH | +|-------------------|----------------------------|---------------------------|---------------------------------------|------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.16a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:16 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16 and 'Maximum number of TFC' = 128, DL on DPCH: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Total RLC AM buffer size' = 50, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.16a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------------------------------------------------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1]
6.10.2.4.1.58.1.1.1 of [1]
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.16.1.1.5 | | | | +| Physical Channel | See 7.4.16.1.2 | | | | + +#### 7.4.16a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-DPCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-DPCH | +|-------------------|----------------------------|-------------------------|---------------------------------|------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | + +| | | | | | +|------------------|--------------------------|---------------------------|---------------------------------------|--| +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | +|------------------|--------------------------|---------------------------|---------------------------------------|--| + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.17 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:128 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps plus support for 'Maximum number of TFC' = 256, DL on DPCH: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Total RLC AM buffer size' = 50, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +### 7.4.17.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|--------------------------------------------------------------------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.1.1.1 of [1]

See 7.1.96.1.1.2

6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.17.1.1.5 | | | | +| Physical Channel | See 7.4.17.1.2 | | | | + +##### 7.4.17.1.1 Transport channel parameters + +7.4.17.1.1.1 Void + +7.4.17.1.1.2 Void + +7.4.17.1.1.3 Void + +7.4.17.1.1.4 Void + +7.4.17.1.1.5 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 240 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 128 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0,TF0), (TF5,TF4,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF0,TF1,TF0,TF0),
(TF3,TF2,TF0,TF1,TF0,TF0), (TF4,TF3,TF0,TF1,TF0,TF0), (TF5,TF4,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF0,TF2,TF0,TF0),
(TF3,TF2,TF0,TF2,TF0,TF0), (TF4,TF3,TF0,TF2,TF0,TF0), (TF5,TF4,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF0,TF3,TF0,TF0),
(TF3,TF2,TF0,TF3,TF0,TF0), (TF4,TF3,TF0,TF3,TF0,TF0), (TF5,TF4,TF1,TF3,TF0,TF0),

(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF0,TF1,TF0),
(TF3,TF2,TF0,TF0,TF1,TF0), (TF4,TF3,TF0,TF0,TF1,TF0), (TF5,TF4,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF0,TF1,TF1,TF0),
(TF3,TF2,TF0,TF1,TF1,TF0), (TF4,TF3,TF0,TF1,TF1,TF0), (TF5,TF4,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF0,TF2,TF1,TF0),
(TF3,TF2,TF0,TF2,TF1,TF0), (TF4,TF3,TF0,TF2,TF1,TF0), (TF5,TF4,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF0,TF3,TF1,TF0),
(TF3,TF2,TF0,TF3,TF1,TF0), (TF4,TF3,TF0,TF3,TF1,TF0), (TF5,TF4,TF1,TF3,TF1,TF0),

(TF0,TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF0,TF2,TF0),
(TF3,TF2,TF0,TF0,TF2,TF0), (TF4,TF3,TF0,TF0,TF2,TF0), (TF5,TF4,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF1,TF2,TF0), (TF1,TF0,TF0,TF1,TF2,TF0), (TF2,TF1,TF0,TF1,TF2,TF0),
(TF3,TF2,TF0,TF1,TF2,TF0), (TF4,TF3,TF0,TF1,TF2,TF0), (TF5,TF4,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF2,TF2,TF0), (TF1,TF0,TF0,TF2,TF2,TF0), (TF2,TF1,TF0,TF2,TF2,TF0),
(TF3,TF2,TF0,TF2,TF2,TF0), (TF4,TF3,TF0,TF2,TF2,TF0), (TF5,TF4,TF1,TF2,TF2,TF0),
(TF0,TF0,TF0,TF3,TF2,TF0), (TF1,TF0,TF0,TF3,TF2,TF0), (TF2,TF1,TF0,TF3,TF2,TF0),
(TF3,TF2,TF0,TF3,TF2,TF0), (TF4,TF3,TF0,TF3,TF2,TF0), (TF5,TF4,TF1,TF3,TF2,TF0),

(TF0,TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF0,TF3,TF0),
(TF3,TF2,TF0,TF0,TF3,TF0), (TF4,TF3,TF0,TF0,TF3,TF0), (TF5,TF4,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF1,TF3,TF0), (TF1,TF0,TF0,TF1,TF3,TF0), (TF2,TF1,TF0,TF1,TF3,TF0),
(TF3,TF2,TF0,TF1,TF3,TF0), (TF4,TF3,TF0,TF1,TF3,TF0), (TF5,TF4,TF1,TF1,TF3,TF0),
(TF0,TF0,TF0,TF2,TF3,TF0), (TF1,TF0,TF0,TF2,TF3,TF0), (TF2,TF1,TF0,TF2,TF3,TF0),
(TF3,TF2,TF0,TF2,TF3,TF0), (TF4,TF3,TF0,TF2,TF3,TF0), (TF5,TF4,TF1,TF2,TF3,TF0),
(TF0,TF0,TF0,TF3,TF3,TF0), (TF1,TF0,TF0,TF3,TF3,TF0), (TF2,TF1,TF0,TF3,TF3,TF0),
(TF3,TF2,TF0,TF3,TF3,TF0), (TF4,TF3,TF0,TF3,TF3,TF0), (TF5,TF4,TF1,TF3,TF3,TF0),

(TF0,TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF0,TF4,TF0),
(TF3,TF2,TF0,TF0,TF4,TF0), (TF4,TF3,TF0,TF0,TF4,TF0), (TF5,TF4,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF1,TF4,TF0), (TF1,TF0,TF0,TF1,TF4,TF0), (TF2,TF1,TF0,TF1,TF4,TF0),
(TF3,TF2,TF0,TF1,TF4,TF0), (TF4,TF3,TF0,TF1,TF4,TF0), (TF5,TF4,TF1,TF1,TF4,TF0),
(TF0,TF0,TF0,TF2,TF4,TF0), (TF1,TF0,TF0,TF2,TF4,TF0), (TF2,TF1,TF0,TF2,TF4,TF0),
(TF3,TF2,TF0,TF2,TF4,TF0), (TF4,TF3,TF0,TF2,TF4,TF0), (TF5,TF4,TF1,TF2,TF4,TF0),
(TF0,TF0,TF0,TF3,TF4,TF0), (TF1,TF0,TF0,TF3,TF4,TF0), (TF2,TF1,TF0,TF3,TF4,TF0),
(TF3,TF2,TF0,TF3,TF4,TF0), (TF4,TF3,TF0,TF3,TF4,TF0), (TF5,TF4,TF1,TF3,TF4,TF0),

(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF0,TF1),
(TF3,TF2,TF0,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF0,TF1), (TF5,TF4,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF0,TF1,TF0,TF1),
(TF3,TF2,TF0,TF1,TF0,TF1), (TF4,TF3,TF0,TF1,TF0,TF1), (TF5,TF4,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF0,TF2,TF0,TF1),
(TF3,TF2,TF0,TF2,TF0,TF1), (TF4,TF3,TF0,TF2,TF0,TF1), (TF5,TF4,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF0,TF3,TF0,TF1),
(TF3,TF2,TF0,TF3,TF0,TF1), (TF4,TF3,TF0,TF3,TF0,TF1), (TF5,TF4,TF1,TF3,TF0,TF1) | + +##### 7.4.17.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 4 | +| | Max number of DPDCH data bits/radio frame | 9600 | +| | Puncturing Limit | 0.88 | + +#### 7.4.17.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------------------------|---------------------------|-----------------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] -> CS voice fehlt ! | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.17a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:128 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL: [max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384kbps plus support for 'Maximum number of TFC' = 256, DL on DPCH: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Total RLC AM buffer size' = 50, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.17a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------------------------------------------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1]
See 7.1.96.1.1.2
6.10.2.4.1.28.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.17.1.1.5 | | | | +| Physical Channel | See 7.4.17.1.2 | | | | + +#### 7.4.17a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.4.18 RB for Streaming / unknown / UL:64 DL: [max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL on DPCH: 32 kbps plus support for HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.18.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | See 7.4.14.1.1.1 | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.18.1.1 | | | | +| Physical Channel | See 7.4.18.1.2 | | | | + +##### 7.4.18.1.1 Transport channel parameters + +7.4.18.1.1.1 Void + +7.4.18.1.1.2 Void + +7.4.18.1.1.3 Void + +7.4.18.1.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +##### 7.4.18.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +#### 7.4.18.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|---------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | See 7.4.14.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | 6.10.2.4.1.2.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +### 7.4.19 RB for Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 64 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.19.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|---------------------------------------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.9.1.1.1 of [1]
6.10.2.4.1.26.1.1.1 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.19.1.1.1 | | | | +| Physical Channel | See 7.4.19.1.2 | | | | + +##### 7.4.19.1.1 Transport channel parameters + +##### 7.4.19.1.1.1 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1) | + +##### 7.4.19.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.84 | + +#### 7.4.19.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|-----------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.9.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.9.1.1.3 of [1] | | | | + +| | | | | | +|------------------|-------------------------|---------------------------|-------------------------|--| +| Physical Channel | 6.10.2.4.1.9.1.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | +|------------------|-------------------------|---------------------------|-------------------------|--| + +7.4.20 RB for Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5, DL on DPCH: 64kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11 + +This is supported in Release 5. + +#### 7.4.20.1 Uplink + +| | Radio Bearer on DPCH | ( reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|----------------------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------------------------------------| +| Transport Channel | 6.10.2.4.1.9.1.1.1 of [1]
6.10.2.4.1.38d.1.1.2 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.20.1.1.1 | | | | +| Physical Channel | See 7.4.20.1.2 | | | | + +##### 7.4.20.1.1 Transport channel parameters + +##### 7.4.20.1.1.1 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 30 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB + 64 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1) | + +##### 7.4.20.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.84 | + +#### 7.4.20.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| + +| | | | | | +|-------------------|---------------------------|---------------------------|---------------------------|--| +| Transport Channel | 6.10.2.4.1.9.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.9.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.9.1.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +7.4.21 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on the UE category & RAB max. bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5, DL on DPCH: 64 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.21.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|--------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.38d.1 of [1]. | | | | +| Physical Channel | | | | | + +#### 7.4.21.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +7.4.22 Conversational / unknown / UL:38.8 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support of 'Maximum number of TFC'=64, DL: 32 kbps, plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 6. + +#### 7.4.22.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-------------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 7.1.118.1.1.1
7.1.84.1.1.1 | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.22.1.1 | | | | +| Physical Channel | See 7.4.22.1.2 | | | | + +##### 7.4.22.1.1 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 54 | +| TFCS | (38.8 kbps Conversational RAB, 16+16 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0),
(TF6, TF1, TF0), (TF7, TF1, TF0), (TF8, TF1, TF0), (TF0, TF2, TF0),
(TF1, TF2, TF0), (TF2, TF2, TF0), (TF3, TF2, TF0), (TF4, TF2, TF0), (TF5, TF2, TF0),
(TF6, TF2, TF0), (TF7, TF2, TF0), (TF8, TF2, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1),
(TF7, TF0, TF1), (TF8, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1),
(TF3, TF1, TF1), (TF4, TF1, TF1), (TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1),
(TF8, TF1, TF1), (TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2, TF1),
(TF3, TF2, TF1), (TF4, TF2, TF1), (TF5, TF2, TF1), (TF6, TF2, TF1), (TF7, TF2, TF1),
(TF8, TF2, TF1) | + +##### 7.4.22.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.96 | + +#### 7.4.22.2 + +#### Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-DPCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-DPCH | +|-------------------|---------------------------|---------------------------|---------------------------------|------------------------------------| +| Transport Channel | | See 7.4.22.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +##### 7.4.22.2.1 Transport channel parameters + +###### 7.4.22.2.1.1 Transport channel parameters for HS-DSCH + +###### 7.4.22.2.1.1.1 MAC-d flow parameters for conversational / unknown DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + +| | | Alt 1 MAC-hs
(Rel-6 and later releases) | Alt 2 MAC-ehs
(Rel-7 and later releases) | +|--------------|-----------------------------------|-------------------------------------------------|---------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 104, 136, 152, 168, 184, 216, 288, 336(alt 328) | Flexible up to 12000 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | | +| MAC | MAC-d header, bit | 0 | | +| | MAC multiplexing | N/A | | +| | MAC-d PDU size, bit | 112, 144, 160, 176, 192, 224, 296, 344(alt 336) | Flexible | +| | MAC-hs Type | MAC-hs | | +| | MAC-hs/ehs header fixed part, bit | 21 | | +| Layer 1 | TrCH type | HS-DSCH | | +| | TTI | 2 ms | | +| | Coding type | TC | | +| | CRC, bit | 24 | | +| | Applicable modulation scheme | QPSK, 16QAM | QPSK, 16QAM, 64QAM | +| | Applicable with MIMO | No | | + +NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). + +###### 7.4.22.2.1.1.2 MAC-d flow parameters for interactive or background DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + +See subclause 6.10.2.4.5.1.2.1.1.1 of [1]. + +###### 7.4.22.2.1.1.3 MAC-d flow parameters for interactive or background DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + +See subclause 6.10.2.4.5.1.2.1.1.1 of [1]. + +7.4.23 Conversational / unknown / UL:16.8 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + interactive / background UL: 16 kbps DL:[max bit rate depending on UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support of 'Maximum number of TFC'=128, DL: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 6. + +NOTE: This RAB is used for the steady-state, where the contexts of the ROHC compressor and the ROHC decompressor are already synchronized so IR packets are not transmitted. + +#### 7.4.23.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|-------------------------------|---------------------------------------|---------------------------------|---------------------------------------------------| +| Transport Channel | 7.1.119.1.1.1
7.1.84.1.1.1 | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.23.1.1 | | | | +| Physical Channel | See 7.4.23.1.2 | | | | + +##### 7.4.23.1.1 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 108 | +| TFCS | (16.8 kbps Conversational RAB, 16+16 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0), (TF3, TF0, TF0), (TF4, TF0, TF0),
(TF5, TF0, TF0), (TF6, TF0, TF0), (TF7, TF0, TF0), (TF8, TF0, TF0), (TF9, TF0, TF0),
(TF10, TF0, TF0), (TF11, TF0, TF0), (TF12, TF0, TF0), (TF13, TF0, TF0), (TF14, TF0, TF0),
(TF15, TF0, TF0), (TF16, TF0, TF0), (TF17, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF2, TF1, TF0), (TF3, TF1, TF0), (TF4, TF1, TF0), (TF5, TF1, TF0), (TF6, TF1, TF0),
(TF7, TF1, TF0), (TF8, TF1, TF0), (TF9, TF1, TF0), (TF10, TF1, TF0), (TF11, TF1, TF0),
(TF12, TF1, TF0), (TF13, TF1, TF0), (TF14, TF1, TF0), (TF15, TF1, TF0), (TF16, TF1, TF0),
(TF17, TF1, TF0), (TF0, TF2, TF0), (TF1, TF2, TF0), (TF2, TF2, TF0), (TF3, TF2, TF0), (TF4,
TF2, TF0), (TF5, TF2, TF0), (TF6, TF2, TF0), (TF7, TF2, TF0), (TF8, TF2, TF0), (TF9, TF2,
TF0), (TF10, TF2, TF0), (TF11, TF2, TF0), (TF12, TF2, TF0), (TF13, TF2, TF0), (TF14, TF2,
TF0), (TF15, TF2, TF0), (TF16, TF2, TF0), (TF17, TF2, TF0), (TF0, TF0, TF1), (TF1, TF0, TF1),
(TF2, TF0, TF1), (TF3, TF0, TF1), (TF4, TF0, TF1), (TF5, TF0, TF1), (TF6, TF0, TF1), (TF7,
TF0, TF1), (TF8, TF0, TF1), (TF9, TF0, TF1), (TF10, TF0, TF1), (TF11, TF0, TF1), (TF12, TF0,
TF1), (TF13, TF0, TF1), (TF14, TF0, TF1), (TF15, TF0, TF1), (TF16, TF0, TF1), (TF17, TF0,
TF1), (TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1), (TF3, TF1, TF1), (TF4, TF1, TF1),
(TF5, TF1, TF1), (TF6, TF1, TF1), (TF7, TF1, TF1), (TF8, TF1, TF1), (TF9, TF1, TF1), (TF10,
TF1, TF1), (TF11, TF1, TF1), (TF12, TF1, TF1), (TF13, TF1, TF1), (TF14, TF1, TF1), (TF15,
TF1, TF1), (TF16, TF1, TF1), (TF17, TF1, TF1), (TF0, TF2, TF1), (TF1, TF2, TF1), (TF2, TF2,
TF1), (TF3, TF2, TF1), (TF4, TF2, TF1), (TF5, TF2, TF1), (TF6, TF2, TF1), (TF7, TF2, TF1),
(TF8, TF2, TF1), (TF9, TF2, TF1), (TF10, TF2, TF1), (TF11, TF2, TF1), (TF12, TF2, TF1),
(TF13, TF2, TF1), (TF14, TF2, TF1), (TF15, TF2, TF1), (TF16, TF2, TF1), (TF17, TF2, TF1) | + +##### 7.4.23.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 0.88 | + +#### 7.4.23.2 Downlink + +| | Radio Bearer
on DPCH | Radio Bearer
on HS-DPCH | Signalling Radio
Bearer
on DPCH | Signalling Radio
Bearer
on HS-DPCH | +|-------------------|---------------------------|----------------------------|---------------------------------------|------------------------------------------| +| Transport Channel | | See 7.4.22.2.1.1 | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +### **7.4.24 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or Background / UL:384 DL:[Bit rate depending on the UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH** + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### **7.4.24.1 Uplink** + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|-----------------------------|----------------------------------------------|----------------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.8.1 of [1] | | | | +| Physical Channel | | | | | + +#### **7.4.24.2 Downlink** + +| | Radio Bearer on DPCH | Radio Bearer on HS-DPCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-DPCH | +|-------------------|-----------------------------|--------------------------------|----------------------------------------|-------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.8.2 of [1] | | | | +| Physical Channel | | | | | + +### **7.4.25 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or Background / UL:64 DL:[Bit rate depending on the UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH** + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of TFC' = 64, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### **7.4.25.1 Uplink** + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|--|-----------------------------|----------------------------------------------|----------------------------------------|---------------------------------------------------------| +| | | | | | + +| | | +|-------------------|-------------------------| +| Transport Channel | See subclause 7.1.109.1 | +| TFCS | | +| Physical Channel | | + +#### 7.4.25.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|---------------------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.62.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1]
6.10.2.4.1.62.2.1.3 of [1] | | +| TFCS | 6.10.2.4.1.62.2.1.4 of [1] | | | | +| Physical Channel | 6.10.2.4.1.62.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.62.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.4.26 RB for Interactive or background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:6.8 DL:6.8 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.26.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------|--------------------------------------|---------------------------------|-------------------------------------------------| +| Transport Channel | 6.10.2.4.1.26.1.1.1 of [1] | | See 7.1.2a | | +| TFCS | See 7.4.26.1.1 | | | | +| Physical Channel | See 7.4.26.1.2 | | | | + +##### 7.4.26.1.1 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (64 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +##### 7.4.26.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-------| +| DPCH Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2 400 | + +| | | | | | +|--------------------------|-----------------------------|---------------------------------|----------------------------------------|--------------------------------------------| +| | Puncturing Limit | | 0.96 | | +| 7.4.26.2 Downlink | | | | | +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | See 7.1.2a | | +| TFCS | See 7.1.2a.2.1.2 | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | See 7.1.2a.2.2 | | + +### 7.4.27 RB for Interactive or background / UL:384 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:6.8 DL:6.8 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 384 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.27.1 Uplink + +| | | | | | +|-------------------|-----------------------------|---------------------------------------------|----------------------------------------|--------------------------------------------------------| +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +| Transport Channel | 6.10.2.4.1.34.1.1.1 of [1] | | See 7.1.2a | | +| TFCS | See 7.4.27.1.1 | | | | +| Physical Channel | See 7.4.27.1.2 | | | | + +##### 7.4.27.1.1 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 18 (alt.12) | +| TFCS | (384 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0), (TF5, TF0), (TF6, TF0), (TF7, TF0),
(TF8, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1), (TF5, TF1), (TF6, TF1), (TF7, TF1),
(TF8, TF1)
(alt. (TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0), (TF5, TF0)
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1), (TF5, TF1)) | + +##### 7.4.27.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|-------| +| DPCH Uplink | Min spreading factor | 4 | +| | Max number of DPDCH data bits/radio frame | 9 600 | +| | Number of DPDCH | 1 | +| | Puncturing Limit | 0.64 | + +#### 7.4.27.2 Downlink + +| | | | | | +|--|-----------------------------|---------------------------------|----------------------------------------|--------------------------------------------| +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|-----------------------------|---------------------------------|----------------------------------------|--------------------------------------------| + +| | | | | | +|-------------------|------------------|-----------------------------|----------------|--| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | See 7.1.2a | | +| TFCS | See 7.1.2a.2.1.2 | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | See 7.1.2a.2.2 | | + +7.4.28 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or Background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + RB for Interactive or Background / UL:64 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 'Maximum number of AM entities' = 5 and 'Maximum number of TFC' = 64, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.28.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-----------------------------------------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.1.62.1.1.1 of [1]
6.10.2.4.1.38d.1.1.2 of [1] | | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.4.28.1.1 and 7.4.28.1.2 | | | | +| Physical Channel | See 7.4.28.1.3 | | | | + +##### 7.4.28.1.1 + +##### TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 50 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 64 kbps RAB + 64 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF4,TF3,TF0,TF1,TF0), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF4,TF3,TF0,TF2,TF0),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF4,TF3,TF0,TF4,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF4,TF3,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF4,TF3,TF0,TF2,TF1), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF4,TF3,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1) | + +##### 7.4.28.1.2 TFC subset list + +| | | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFC subset list size | 3 | +| TFC subset list |

0 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1),
(TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1)},

1 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1),
(TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0),
(TF1,TF0,TF0,TF1,TF0), (TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1),
(TF1,TF0,TF0,TF2,TF1), (TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1), (TF1,TF0,TF0,TF3,TF1),
(TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0),
(TF1,TF0,TF0,TF4,TF0), (TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1)},

2 = {(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF0,TF0,TF0),
(TF3,TF2,TF0,TF0,TF0), (TF4,TF3,TF0,TF0,TF0), (TF0,TF0,TF0,TF0,TF1),
(TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF0,TF0,TF1), (TF3,TF2,TF0,TF0,TF1),
(TF4,TF3,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF1,TF0,TF1,TF0), (TF3,TF2,TF0,TF1,TF0), (TF4,TF3,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF1,TF0,TF1,TF1),
(TF3,TF2,TF0,TF1,TF1), (TF4,TF3,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF0),
(TF1,TF0,TF0,TF2,TF0), (TF2,TF1,TF0,TF2,TF0), (TF3,TF2,TF0,TF2,TF0),
(TF4,TF3,TF0,TF2,TF0), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF1,TF0,TF2,TF1), (TF3,TF2,TF0,TF2,TF1), (TF4,TF3,TF0,TF2,TF1),
(TF0,TF0,TF0,TF3,TF0), (TF1,TF0,TF0,TF3,TF0), (TF2,TF1,TF0,TF3,TF0),
(TF3,TF2,TF0,TF3,TF0), (TF4,TF3,TF0,TF3,TF0), (TF0,TF0,TF0,TF3,TF1),
(TF1,TF0,TF0,TF3,TF1), (TF2,TF1,TF0,TF3,TF1), (TF3,TF2,TF0,TF3,TF1),
(TF4,TF3,TF0,TF3,TF1), (TF0,TF0,TF0,TF4,TF0), (TF1,TF0,TF0,TF4,TF0),
(TF2,TF1,TF0,TF4,TF0), (TF3,TF2,TF0,TF4,TF0), (TF4,TF3,TF0,TF4,TF0),
(TF0,TF0,TF0,TF4,TF1), (TF1,TF0,TF0,TF4,TF1), (TF2,TF1,TF0,TF4,TF1),
(TF3,TF2,TF0,TF4,TF1), (TF4,TF3,TF0,TF4,TF1)}

| + +##### 7.4.28.1.3 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 0.76 | + +#### 7.4.28.2 Downlink + +| | Radio Bearer
on DPCH | Radio Bearer
on HS-PDSCH | Signalling Radio
Bearer
on DPCH | Signalling Radio
Bearer
on HS-PDSCH | +|----------------------|-----------------------------|-----------------------------|----------------------------------------------------------|-------------------------------------------| +| Transport
Channel | 6.10.2.4.1.6.2.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1]
6.10.2.4.1.6.2.2.1.3 of [1] | | + +| | | | | | +|------------------|----------------------------|---------------------------|---------------------------------------|--| +| TFCS | 6.10.2.4.1.62.2.1.4 of [1] | | | | +| Physical Channel | 6.10.2.4.1.62.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.62.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.4.29 RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + RB for Interactive or background / UL:128 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 16, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.29.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | ( reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|----------------------|---------------------------------------|---------------------------------|---------------------------------------------------| +| Transport Channel | See 7.1.88.1 | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 7.4.29.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +### 7.4.30 RB for Interactive or background / UL:16 DL:[Bit rate depending on the UE category & RAB maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11. + +This is supported in Release 5. + +#### 7.4.30.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|-------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.1.23b.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.30.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|-----------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +### 7.4.31 RB for Streaming MBMS PTP / unknown / UL:16 DL:[max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11, and MBMS minimum capability. + +This is supported in Release 6. + +#### 7.4.31.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|-----------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.5.9.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.4.31.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| + +| | | +|-------------------|-----------------------| +| Transport Channel | 6.10.2.4.5.9.2 of [1] | +| TFCS | | +| Physical Channel | | + +7.4.32 RB for Streaming MBMS PTP / unknown / UL:16 DL:[max bit rate depending on UE category & RAB guaranteed/maximum bit rate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on UE category & RAB maximum bitrate] / PS RAB + RB for Interactive or background / UL:64 DL:[max bit rate depending on UE category & RAB maximum bitrate] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH, DL on HS-PDSCH: category 11, and MBMS minimum capability. + +This is supported in Release 6. + +#### 7.4.32.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.10.2.4.5.10.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 7.4.32.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|------------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.5.10.2 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +7.4.33 RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.4.33.1 Uplink + +See subclause 7.1.153.1 + +#### 7.4.33.2 Downlink + +##### 7.4.33.2.1 Transport channel parameters + +###### 7.4.33.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +###### 7.4.33.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.2.1.1 + +###### 7.4.33.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.4.33.2.1.4 TFCS + +See subclause 7.1.145.2.1.3 + +##### 7.4.33.2.2 Physical channel parameters + +###### 7.4.33.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.145.2.2. + +###### 7.4.33.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +7.4.34 RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.4.34.1 Uplink + +See subclause 7.1.154.1 + +#### 7.4.34.2 Downlink + +##### 7.4.34.2.1 Transport channel parameters + +###### 7.4.34.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +###### 7.4.34.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.2.1.1 + +###### 7.4.34.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +###### 7.4.34.2.1.4 TFCS + +See subclause 7.1.146.2.1.3 + +##### 7.4.34.2.2 Physical channel parameters + +###### 7.4.34.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.146.2.2. + +###### 7.4.34.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +### 7.4.35 RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.4.35.1 Uplink + +See subclause 7.1.155.1 + +##### 7.4.35.1.1 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.2.4.1.23a.1.1.1 of [1]. + +##### 7.4.35.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.4.35.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 8kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0), (TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1),
(TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1), (TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1) | + +##### 7.4.35.1.4 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +###### 7.4.35.2 Downlink + +### 7.4.35.2.1 Transport channel parameters + +#### 7.4.35.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +#### 7.4.35.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.2.1.1 + +#### 7.4.35.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.4.35.2.1.4 TFCS + +See subclause 7.1.147.2.1.3 + +### 7.4.35.2.2 Physical channel parameters + +#### 7.4.35.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.147.2.2. + +#### 7.4.35.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.4.36 RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:8 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +### 7.4.36.1 Uplink + +See subclause 7.1.11.1 + +## 7.4.36.2 Downlink + +### 7.4.36.2.1 Transport channel parameters + +#### 7.4.36.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +#### 7.4.36.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 24.4 16.2 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.2.1.1 + +#### 7.4.36.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.4.36.2.1.4 TFCS + +See subclause 7.1.148.2.1.3 + +#### 7.4.36.2.2 Physical channel parameters + +##### 7.4.36.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.148.2.2. + +##### 7.4.36.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +#### 7.4.37 RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +##### 7.4.37.1 Uplink + +###### 7.4.37.1.1 Transport channel parameters + +###### 7.4.37.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.1.1.1 + +###### 7.4.37.1.1.2 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.1.1.1 of [1]. + +###### 7.4.37.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.4.37.1.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF0,TF0,TF2,TF0), (TF3,TF0,TF0,TF2,TF0),
(TF4,TF0,TF0,TF2,TF0), (TF5,TF0,TF0,TF2,TF0), (TF6,TF0,TF0,TF2,TF0), (TF7,TF0,TF0,TF2,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF0,TF0,TF2,TF1), (TF3,TF0,TF0,TF2,TF1),
(TF4,TF0,TF0,TF2,TF1), (TF5,TF0,TF0,TF2,TF1), (TF6,TF0,TF0,TF2,TF1), (TF7,TF0,TF0,TF2,TF1) | + +##### 7.4.37.1.2 Physical channel parameters + +| | | | +|-------------|-------------------------------------------|------| +| DPCH Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +## 7.4.37.2 Downlink + +### 7.4.37.2.1 Transport channel parameters + +#### 7.4.37.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +#### 7.4.37.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + +See subclause 7.1.145.2.1.1 + +#### 7.4.37.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +#### 7.4.37.2.1.4 TFCS + +See subclause 7.1.145.2.1.3 + +### 7.4.37.2.2 Physical channel parameters + +#### 7.4.37.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.145.2.2. + +#### 7.4.37.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +**7.4.38 RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +## 7.4.38.1 Uplink + +### 7.4.38.1.1 Transport channel parameters + +#### 7.4.38.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.1.1.1 + +#### 7.4.38.1.1.2 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.1.1.1 of [1]. + +#### 7.4.38.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.4.38.1.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 54 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0),
(TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0),
(TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0),
(TF2,TF0,TF0,TF2,TF0), (TF3,TF0,TF0,TF2,TF0), (TF4,TF0,TF0,TF2,TF0), (TF5,TF0,TF0,TF2,TF0),
(TF6,TF0,TF0,TF2,TF0), (TF7,TF0,TF0,TF2,TF0), (TF8,TF0,TF0,TF2,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1),
(TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1),
(TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1),
(TF2,TF0,TF0,TF2,TF1), (TF3,TF0,TF0,TF2,TF1), (TF4,TF0,TF0,TF2,TF1), (TF5,TF0,TF0,TF2,TF1),
(TF6,TF0,TF0,TF2,TF1), (TF7,TF0,TF0,TF2,TF1), (TF8,TF0,TF0,TF2,TF1) | + +## 7.4.38.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +## 7.4.38.2 Downlink + +## 7.4.38.2.1 Transport channel parameters + +## 7.4.38.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +## 7.4.38.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.2.1.1 + +## 7.4.38.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.4.38.2.1.4 TFCS + +See subclause 7.1.146.2.1.3 + +## 7.4.38.2.2 Physical channel parameters + +## 7.4.38.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.146.2.2. + +## 7.4.38.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +7.4.39 RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +#### 7.4.39.1 Uplink + +##### 7.4.39.1.1 Transport channel parameters + +7.4.39.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.1.1.1 + +7.4.39.1.1.2 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.1.1.1 of [1]. + +7.4.39.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.4.39.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 72 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0), (TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0),
(TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0), (TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0),
(TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0), (TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0),
(TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF0,TF0,TF2,TF0), (TF3,TF0,TF0,TF2,TF0),
(TF4,TF0,TF0,TF2,TF0), (TF5,TF0,TF0,TF2,TF0), (TF6,TF0,TF0,TF2,TF0), (TF7,TF0,TF0,TF2,TF0),
(TF8,TF0,TF0,TF2,TF0), (TF9,TF0,TF0,TF2,TF0), (TF10,TF0,TF0,TF2,TF0), (TF11,TF0,TF0,TF2,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1), (TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1),
(TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1), (TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1),
(TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1), (TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF0,TF0,TF2,TF1), (TF3,TF0,TF0,TF2,TF1),
(TF4,TF0,TF0,TF2,TF1), (TF5,TF0,TF0,TF2,TF1), (TF6,TF0,TF0,TF2,TF1), (TF7,TF0,TF0,TF2,TF1),
(TF8,TF0,TF0,TF2,TF1), (TF9,TF0,TF0,TF2,TF1), (TF10,TF0,TF0,TF2,TF1), (TF11,TF0,TF0,TF2,TF1) | + +##### 7.4.39.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 32 | +| | Max number of DPDCH data bits/radio frame | 1200 | +| | Puncturing Limit | 1 | + +#### 7.4.39.2 Downlink + +##### 7.4.39.2.1 Transport channel parameters + +7.4.39.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +7.4.39.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.2.1.1 + +7.4.39.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +7.4.39.2.1.4 TFCS + +See subclause 7.1.147.2.1.3 + +7.4.39.2.2 Physical channel parameters + +7.4.39.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.147.2.2. + +7.4.39.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +7.4.40 RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL:16 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +7.4.40.1 Uplink + +7.4.40.1.1 Transport channel parameters + +7.4.40.1.1.1 Transport channel parameters for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.1.1.1 + +7.4.40.1.1.2 Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB + +See subclause 6.10.2.4.1.23b.1.1.1 of [1]. + +7.4.40.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +## 7.4.40.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 84 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF0,TF0,TF0,TF0), (TF3,TF0,TF0,TF0,TF0),
(TF4,TF0,TF0,TF0,TF0), (TF5,TF0,TF0,TF0,TF0), (TF6,TF0,TF0,TF0,TF0), (TF7,TF0,TF0,TF0,TF0),
(TF8,TF0,TF0,TF0,TF0), (TF9,TF0,TF0,TF0,TF0), (TF10,TF0,TF0,TF0,TF0), (TF11,TF0,TF0,TF0,TF0),
(TF12,TF0,TF0,TF0,TF0), (TF13,TF0,TF0,TF0,TF0), (TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF1,TF0),
(TF2,TF0,TF0,TF1,TF0), (TF3,TF0,TF0,TF1,TF0), (TF4,TF0,TF0,TF1,TF0), (TF5,TF0,TF0,TF1,TF0),
(TF6,TF0,TF0,TF1,TF0), (TF7,TF0,TF0,TF1,TF0), (TF8,TF0,TF0,TF1,TF0), (TF9,TF0,TF0,TF1,TF0),
(TF10,TF0,TF0,TF1,TF0), (TF11,TF0,TF0,TF1,TF0), (TF12,TF0,TF0,TF1,TF0),
(TF13,TF0,TF0,TF1,TF0), (TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF2,TF0), (TF2,TF0,TF0,TF2,TF0),
(TF3,TF0,TF0,TF2,TF0), (TF4,TF0,TF0,TF2,TF0), (TF5,TF0,TF0,TF2,TF0), (TF6,TF0,TF0,TF2,TF0),
(TF7,TF0,TF0,TF2,TF0), (TF8,TF0,TF0,TF2,TF0), (TF9,TF0,TF0,TF2,TF0), (TF10,TF0,TF0,TF2,TF0),
(TF11,TF0,TF0,TF2,TF0), (TF12,TF0,TF0,TF2,TF0), (TF13,TF0,TF0,TF2,TF0)
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF0,TF0,TF0,TF1), (TF3,TF0,TF0,TF0,TF1),
(TF4,TF0,TF0,TF0,TF1), (TF5,TF0,TF0,TF0,TF1), (TF6,TF0,TF0,TF0,TF1), (TF7,TF0,TF0,TF0,TF1),
(TF8,TF0,TF0,TF0,TF1), (TF9,TF0,TF0,TF0,TF1), (TF10,TF0,TF0,TF0,TF1), (TF11,TF0,TF0,TF0,TF1),
(TF12,TF0,TF0,TF0,TF1), (TF13,TF0,TF0,TF0,TF1), (TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF1,TF1),
(TF2,TF0,TF0,TF1,TF1), (TF3,TF0,TF0,TF1,TF1), (TF4,TF0,TF0,TF1,TF1), (TF5,TF0,TF0,TF1,TF1),
(TF6,TF0,TF0,TF1,TF1), (TF7,TF0,TF0,TF1,TF1), (TF8,TF0,TF0,TF1,TF1), (TF9,TF0,TF0,TF1,TF1),
(TF10,TF0,TF0,TF1,TF1), (TF11,TF0,TF0,TF1,TF1), (TF12,TF0,TF0,TF1,TF1),
(TF13,TF0,TF0,TF1,TF1), (TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF2,TF1), (TF2,TF0,TF0,TF2,TF1),
(TF3,TF0,TF0,TF2,TF1), (TF4,TF0,TF0,TF2,TF1), (TF5,TF0,TF0,TF2,TF1), (TF6,TF0,TF0,TF2,TF1),
(TF7,TF0,TF0,TF2,TF1), (TF8,TF0,TF0,TF2,TF1), (TF9,TF0,TF0,TF2,TF1), (TF10,TF0,TF0,TF2,TF1),
(TF11,TF0,TF0,TF2,TF1), (TF12,TF0,TF0,TF2,TF1), (TF13,TF0,TF0,TF2,TF1) | + +## 7.4.40.1.2 Physical channel parameters + +| | | | +|----------------|-------------------------------------------|------| +| DPCH
Uplink | Min spreading factor | 16 | +| | Max number of DPDCH data bits/radio frame | 2400 | +| | Puncturing Limit | 1 | + +## 7.4.40.2 Downlink + +## 7.4.40.2.1 Transport channel parameters + +## 7.4.40.2.1.1 Transport channel parameters for HS-DSCH + +See subclause 6.10.2.4.5.1.2.1.1 of [1]. + +## 7.4.40.2.1.2 Transport channel parameters for Conversational / speech / DL: (EVS 24.4 16.2 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.2.1.1 + +## 7.4.40.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.2.1.1 of [1]. + +## 7.4.40.2.1.4 TFCS + +See subclause 7.1.148.2.1.3 + +## 7.4.40.2.2 Physical channel parameters + +## 7.4.40.2.2.1 Physical channel parameters on DPCH + +See subclause 7.1.148.2.2. + +## 7.4.40.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.5 Radio Bearer and Radio Bearer Combinations on E-DPDCH and HS-PDSCH + +In the following tables for the references to [1], the details of the configuration are defined there. + +### 7.5.1 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.1.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------|-----------------------|---------------------------------|----------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.1.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.5.1.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.1.2 of [1] | | | | +| Physical Channel | | | | | + +### 7.5.2 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.2.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer | Signalling Radio Bearer | +|--|----------------------|-----------------------|-------------------------|-------------------------| +|--|----------------------|-----------------------|-------------------------|-------------------------| + +| | | | on DPCH | on E-DCH | +|-------------------|-----------------------|--|---------|----------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.2.1 of [1] | | | | +| Physical Channel | | | | | + +### 7.5.2.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.2.2 of [1] | | | | +| Physical Channel | | | | | + +7.5.3 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.3.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------|-----------------------|---------------------------------|----------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.3.1 of [1] | | | | +| Physical Channel | | | | | + +### 7.5.3.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.6.3.2 of [1] | | | | + +| | | +|------------------|--| +| TFCS | | +| Physical Channel | | + +7.5.4 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.4.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------|-----------------------|---------------------------------|----------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.4.1 of [1] | | | | +| Physical Channel | | | | | + +#### 7.5.4.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.4.2 of [1] | | | | +| Physical Channel | | | | | + +7.5.5 Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.5.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------|-----------------------|---------------------------------|----------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.5.1 of [1] | | | | +| Physical Channel | | | | | + +### 7.5.5.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.5.2 of [1] | | | | +| Physical Channel | | | | | + +### 7.5.6 Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.6.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|---------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.5.1.1.1 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.1.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.6.5.1.2.1 of [1] | 6.10.2.4.1.2.1.2 of [1] | | + +### 7.5.6.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.10.2.4.6.5.2 of [1] | | | | +| Physical Channel | | | | | + +7.5.7 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.7.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|---------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.62.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.62.1.1.3 of [1] | | | | +| TFC subset list | 6.10.2.4.1.62.1.1.4 of [1] | | | | +| Physical Channel | 6.10.2.4.1.62.1.2 of [1] | 6.10.2.4.6.5.1.2.1 of [1] | 6.10.2.4.1.62.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.7.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|---------------------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.62.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1]
6.10.2.4.1.62.2.1.3 of [1] | | +| TFCS | 6.10.2.4.1.62.2.1.4 of [1] | | | | + +| | | | | | +|------------------|--------------------------|---------------------------|---------------------------------------------|--| +| Physical Channel | 6.10.2.4.1.62.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.62.2.2 of [1]
See NOTE | | +|------------------|--------------------------|---------------------------|---------------------------------------------|--| + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.8 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 64 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.8.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|---------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.13.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.13.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.13.1.2 of [1] | 6.10.2.4.6.5.1.2.1 of [1] | 6.10.2.4.1.13.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.8.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|-----------------------------|---------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.13.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.13.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.13.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.13.2.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.9 Conversational / speech / UL:(5.9, 4.75) DL:( 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.9.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-------------------------|---------------------------|--------------------------------------------|----------------------------------| +| Transport Channel | 7.1.12a.1.1 | 6.10.2.4.6.5.1.1.1 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 7.1.12a.1.1.3 | | | | +| Physical Channel | 6.10.2.4.1.9.1.2 of [1] | 6.10.2.4.6.5.1.2.1 of [1] | 6.10.2.4.1.9.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.9.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-------------------------|-----------------------------|--------------------------------------------|-------------------------------------| +| Transport Channel | 7.1.12a.2.1 | 6.10.2.4.5.1.2.1.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 7.1.12a.2.1.3 | | | | +| Physical Channel | 6.10.2.4.1.9.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.9.2.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.10 UL: [max bit rate depending on UE category and TTI] on E-DCH DL: [max bit rate depending on UE category] on HS-PDSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +#### 7.5.10.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer | Signalling Radio Bearer | +|--|----------------------|-----------------------|-------------------------|-------------------------| +|--|----------------------|-----------------------|-------------------------|-------------------------| + +| | | | on DPCH | on E-DCH | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------|--|---------|----------------| +| Transport Channel | | | | 7.5.10.1.1.1.1 | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.6.1.1.2.1 of [1]
E-TFCI table index = 0; E-DCH minimum set E-TFCI = 9 (10 ms TTI) or 10 (2 ms TTI) (TB size 166 bits) | | | | + +7.5.10.1.1 Transport channel parameters + +7.5.10.1.1.1 Transport channel parameters for E-DCH + +7.5.10.1.1.1.1 MAC-d flow#1 parameters for UL: [max bit rate depending on UE category and TTI] (non-scheduled) on E-DCH SRBs for DCCH + +| Higher layer | RAB/Signalling RB | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +|--------------|---------------------------------|--------------------------------|-------|-------|-------| +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | UM | AM | AM | AM | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | +| | Max data rate, bps | Depends on UE category and TTI | | | | +| | AMD/UMD PDU header, bit | 8 | 16 | 16 | 16 | +| MAC | MAC-e multiplexing | 4 logical channel multiplexing | | | | +| | MAC-d PDU size, bit | 144 | | | | +| | Max MAC-e PDU content size, bit | 162 (non-scheduled) (NOTE1) | | | | +| | MAC-e/es header fixed part, bit | 18 | | | | +| Layer 1 | TrCH type | E-DCH | | | | +| | TTI | 10ms (alt. 2ms) (NOTE2) | | | | +| | Coding type | TC | | | | +| | CRC, bit | 24 | | | | + +NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC +NOTE2: The support of 2ms TTI depends on the UE category. + +7.5.10.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +7.5.11 RB for interactive or background / UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + UL: [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +7.5.11.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.1.1.1.1.1 of [1] | | 7.5.10.1.1.1.1 | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.6.1.1.2.1 of [1]
E-TFCI table index = 0; E-DCH minimum set E-TFCI = 9 (10 ms TTI) or 10 (2 ms TTI) (TB size 166 bits) | | | | + +Note: MAC-e multiplexing of scheduled and non-scheduled MAC-d flows is allowed + +7.5.11.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|-----------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +7.5.12 RB for Conversational / unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + + RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + + UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +#### 7.5.12.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.6.3.1.1.1.1 for conversational RB,
6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | | 7.5.10.1.1.1.1 | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.6.1.1.2.1 of [1]
E-TFCI table index = 0; E-DCH minimum set E-TFCI = 29 (10 ms TTI, TB size 374 bits) or 32 (2 ms TTI, TB size 368 bits) | | | | + +NOTE: MAC-e multiplexing of scheduled and non-scheduled MAC-d flows is allowed. + +##### 7.5.12.1.1 Transport channel parameters + +###### 7.5.12.1.1.1 Transport channel parameters for E-DCH + +###### 7.5.12.1.1.1.1 MAC-d flow#1 parameters for conversational / Unknown UL: [max bit rate depending on UE category and TTI] on E-DCH / PS RAB + +| | | | +|--------------|-----------------------|------------------------------------------------------------------------| +| Higher layer | RAB/Signalling RB | RAB | +| PDCP | PDCP header size, bit | 0 | +| RLC | Logical channel type | DTCH | +| | RLC mode | UM | +| | Payload sizes, bit | 88, 104, 136, 152, 168, 184, 200, 216, 280, 288, 304, 336
(alt 328) | +| | Max data rate, bps | Depends on UE category and TTI | +| | UMD PDU header, bit | 8 | +| MAC | MAC-e multiplexing | N/A | + +| | | | +|---------------------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------| +| | MAC-d PDU size, bit | 96, 112, 144, 160, 176, 192, 208, 224, 288, 296, 312, 344
(alt 336) | +| | Max MAC-e PDU content size, bit | (non-scheduled) (NOTE1) | +| | MAC-e/es header fixed part, bit | 18 | +| Layer 1 | TrCH type | E-DCH | +| | TTI | 10ms (alt. 2ms) (NOTE2) | +| | Coding type | TC | +| | CRC, bit | 24 | +| NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC | | | +| NOTE2: The support of 2ms TTI depends on the UE category. | | | + +## 7.5.12.2 + +## Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.4.22.2.1.1.1 for Conversational RB

6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +## 7.5.13 + +RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB ++ RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB ++ UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +## 7.5.13.1 + +## Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|-------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.6.3.1.1.1.1 for Conversational RB | | 7.5.10.1.1.1.1 | + +| | | | | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|--|--| +| | | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background | | | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.6.1.1.2.1 of [1]
E-TFCI table index = 0; E-DCH minimum set E-TFCI = 29 (10 ms TTI, TB size 374 bits) or 32 (2 ms TTI, TB size 368 bits) | | | | + +NOTE: MAC-e multiplexing of scheduled and non-scheduled MAC-d flows is allowed. + +## 7.5.13.2 + +## Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.4.22.2.1.1.1 for Conversational RB
6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RB | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +7.5.14 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +## 7.5.14.1 + +## Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4a.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | + +| | | | | | +|------------------|--------------------------|---------------------------|---------------------------------------------|--| +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | +|------------------|--------------------------|---------------------------|---------------------------------------------|--| + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +## 7.5.14.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.14a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +## 7.5.14a.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|------------------------------------------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +## 7.5.14a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| + +| | | | | | +|-------------------|----------------------------|---------------------------|----------------------------------------------|--| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.15 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + DL:0.15 kbps SRB#5 for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.15.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|------------------------------------------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.62.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.62.1.1.3 of [1] | | | | +| TFC subset list | 6.10.2.4.1.62.1.1.4 of [1] | | | | +| Physical Channel | 6.10.2.4.1.62.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.62.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.15.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|---------------------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.62.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1]
6.10.2.4.1.62.2.1.3 of [1] | | +| TFCS | 6.10.2.4.1.62.2.1.4 of [1] | | | | + +| | | | | | +|------------------|--------------------------|---------------------------|---------------------------------------|--| +| Physical Channel | 6.10.2.4.1.62.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.62.2.2 of [1]
See NOTE. | | +|------------------|--------------------------|---------------------------|---------------------------------------|--| + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.16 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.16.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.1.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.2.1.2 of [1] | | + +#### 7.5.16.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +7.5.17 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.17.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|------------------------------------------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4a.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.17.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | 6.10.2.4.5.6.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.6.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.17a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.17a.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|--|----------------------|-----------------------|---------------------------------|----------------------------------| +| | | | | | + +| | | | | | +|-------------------|----------------------------|------------------------------------------------------------|---------------------------------------------|--| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1] | 6.10.2.4.6.5.1.1.1.1 of [1]
6.10.2.4.6.5.1.1.1.2 of [1] | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +## 7.5.17a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | 6.10.2.4.5.6.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.6.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.18 RB for Conversational / Speech UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +## 7.5.18.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.5.12.1.1.1.1 for Conversational RBs (MAC-e muxed)
6.10.2.4.6.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | | 7.5.10.1.1.1.1 | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.6.1.1.2.1 of [1]
E-TFCI table index = 0; E-DCH minimum set E-TFCI = 29 (10 ms TTI, TB size 374 bits) or 32 (2 ms TTI, TB size 368 bits) | | | | + +NOTE: MAC-e multiplexing of scheduled and non-scheduled MAC-d flows is allowed. + +## 7.5.18.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.4.22.2.1.1.1 for Conversational RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +7.5.19 RB for Conversational / Speech UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ RB for Conversational / Unknown UL: [max bitrate depending on UE category and TTI] on E-DCH DL: [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ RB for interactive or background / UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bitrate depending on UE category] on HS-DSCH / PS RAB + ++ UL : [max bitrate depending on UE category and TTI] on E-DCH DL : [max bit rate depending on UE category] on HS-DSCH SRBs for DCCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DPDCH, UL on E-DPDCH category 1. + +This is supported in Release 6. + +## 7.5.19.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.5.12.1.1.1.1 for Conversational RBs (MAC-e muxed)
6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RB | | 7.5.10.1.1.1.1 | +| TFCS | | | | | +| Physical Channel | E-TFCI table index = 0; E-DCH minimum set E-TFCI = 29 (10 ms TTI, TB size 374 bits) or 32 (2 ms TTI, TB size 368 bits) | | | | + +NOTE: MAC-e multiplexing of scheduled and non-scheduled MAC-d flows is allowed. + +## 7.5.19.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.4.22.2.1.1.1 for Conversational RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RB | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | 6.10.2.4.5.1.2.2.2 of [1]
The physical channel configuration shall use F-DPCH. | | | | + +7.5.20 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +## 7.5.20.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|--------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.1.1.3 of [1] | | | | + +| | | | | | +|------------------|-------------------------|---------------------------|--------------------------------------------|--| +| Physical Channel | 6.10.2.4.1.4.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4.1.2 of [1]
See NOTE | | +|------------------|-------------------------|---------------------------|--------------------------------------------|--| + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +## 7.5.20.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.21 RB for Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +## 7.5.21.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|--------------------------------------------------------------------------|--------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +## 7.5.21.2 Downlink + +| | Radio Bearer | Radio Bearer | Signalling Radio Bearer | Signalling Radio Bearer | +|--|--------------|--------------|-------------------------|-------------------------| +|--|--------------|--------------|-------------------------|-------------------------| + +| | on DPCH | on HS-PDSCH | on DPCH | on HS-PDSCH | +|-------------------|---------------------------|------------------------------------------------------------|---------------------------------------------|-------------| +| Transport Channel | 6.10.2.4.1.4.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.22 RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.22.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|--------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.1.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.2.1.2 of [1] | | + +#### 7.5.22.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.2.2.2 of [1] | | + +7.5.23 RB for Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +### 7.5.23.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|--------------------------------------------------------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4a.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +### 7.5.23.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|------------------------------------------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4a.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.23a RB for Conversational / speech / UL:(12.2 7.4 5.9 4.75) DL:(12.2 7.4 5.9 4.75) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.23a.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|--------------------------------------------------------------------------|---------------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.4b.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.1.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.1.2 of [1] | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.4a.1.2 of [1]
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.23a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|------------------------------------------------------------|----------------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4b.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4a.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4a.2.2 of [1] | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.4a.2.2 of [1]
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.24 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.24.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|--------------------------------------------------------------------------|------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.62.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.1.106.1.1.3 | | | | +| Physical Channel | See 7.1.106.1.2 | 6.10.2.4.6.1.1.2.1 of [1] | See 7.1.106.1.2
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.24.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|-------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.62.2.1.1 of [1] | 6.10.2.4.5.5.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | See 7.1.106.2.1.3 | | | | +| Physical Channel | See 7.1.106.2.2 | 6.10.2.4.5.1.2.2.2 of [1] | See 7.1.106.2.2
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.25 RB for Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + RB for Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +#### 7.5.25.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------------|--------------------------------------------------------------------------|------------------------------------|----------------------------------| +| Transport Channel | 6.10.2.4.1.62.1.1.1 of [1] | 6.10.2.4.6.1.1.1.1.1 of [1] for Interactive/Background RBs (MAC-e muxed) | 6.10.2.4.1.2.1.1.1 of [1] | | +| TFCS | See 7.1.106.1.1.3 | | | | +| Physical Channel | See 7.1.106.1.2 | 6.10.2.4.6.1.1.2.1 of [1] | See 7.1.106.1.2
See NOTE | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH. + +#### 7.5.25.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|------------------------------------------------------------|-------------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.62.2.1.1 of [1] | 6.10.2.4.5.1.2.1.1.1 of [1] for Interactive/Background RBs | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | See 7.1.106.2.1.3 | | | | +| Physical Channel | See 7.1.106.2.2 | 6.10.2.4.5.1.2.2.2 of [1] | See 7.1.106.2.2
See NOTE. | | + +NOTE: Already included in Physical Channel Definition of Radio Bearer on DPCH + +7.5.26 UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-PDSCH + DCH 3.4kbps + +The minimum UE classes supporting this combination are UL: 12 kbps, DL on DPCH: 12 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6 onwards. + +## 7.5.26.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|-----------------------|---------------------------------|----------------------------------| +| Transport Channel | | | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | | | 6.10.2.4.6.1.1.2.1 of [1] | + +## 7.5.26.2 Downlink + +### 7.5.26.2.1 Transport channel parameters for SRBs mapped on “DCH + HS-DSCH” + +There is only one configuration for RLC and Mac-d that is mapped to the transport channel type “DCH + HS-DSCH”. + +#### 7.5.26.2.1.1 RLC and Mac-d Parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + DCH 3.4kbps + +Alternative 1: Fixed RLC + MAC-hs (Rel-6 and later releases): + +| Higher layer | RAB/Signalling RB | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------|-------|-------|-------| +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | UM | AM | AM | AM | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | +| | Max data rate, bps | On HS-DSCH : Depends on UE category (NOTE 1)
On DCH : 3.4kbps | | | | +| | AMD PDU header, bit | 8 | 16 | 16 | 16 | +| MAC-d | MAC-d header, bit | 4 | 4 | 4 | 4 | +| | MAC multiplexing | 4 logical channel multiplexing | | | | +| | MAC-d PDU size, bit | 148 | | | | +| | MAC-hs Type | MAC-hs | | | | +| | MAC-hs/ehs header fixed part, bit | 21 | | | | +| NOTE 1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs PDU (see 3GPP TS 25.321 [38]). | | | | | | + +Alternative 2: Fixed RLC + MAC-ehs (Rel-7 and later releases): + +| Higher layer | RAB/Signalling RB | SRB#1 | SRB#2 | SRB#3 | SRB#4 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------|-------|-------|-------| +| RLC | Logical channel type | DCCH | DCCH | DCCH | DCCH | +| | RLC mode | UM | AM | AM | AM | +| | Payload sizes, bit | 136 | 128 | 128 | 128 | +| | Max data rate, bps | On HS-DSCH : Depends on UE category (NOTE 1)
On DCH : 3.4kbps | | | | +| | AMD PDU header, bit | 8 | 16 | 16 | 16 | +| MAC-d | MAC-d header, bit | 0 | 0 | 0 | 0 | +| | MAC multiplexing | 4 logical channel multiplexing | | | | +| | MAC-d PDU size, bit | 144 | | | | +| | MAC-hs Type | MAC-ehs | | | | +| | MAC-hs/ehs header fixed part, bit | 24 | | | | +| NOTE 1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-ehs PDU (see 3GPP TS 25.321 [38]). | | | | | | + +## 7.5.26.2.1.2 Layer 1 parameters for DL SRBs for DCH 3.4kbps + +| | | | +|---------|---------------------------------------------|---------------------------| +| Layer 1 | TrCH type | DCH | +| | TB sizes, bit | 148 (alt 0, 148) (note 2) | +| | TFS | 0x148 (alt 1x0) (note 2) | +| | | 1x148 | +| | TTI | 40 | +| | Coding type | CC 1/3 | +| | CRC, bit | 16 | +| | Max number of bits/TTI before rate matching | 516 | +| | RM attribute | 155 to 230 | + +NOTE 2: alternative parameters enable the measurement "transport channel BLER" in the UE. + +## 7.5.26.2.1.3 Mac-hs and layer 1 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +Alternative 1: Fixed RLC + MAC-hs (Rel-6 and later releases): + +| | | | +|---------|-------------------------------|-------------| +| MAC-hs | MAC-hs header fixed part, bit | 21 | +| Layer 1 | TrCH type | HS-DSCH | +| | TTI | 2 ms | +| | Coding type | TC | +| | CRC, bit | 24 | +| | Applicable modulation scheme | QPSK, 16QAM | +| | Applicable with MIMO | No | + +Alternative 2: Fixed RLC + MAC-ehs (Rel-7 and later releases): + +| | | | +|---------|--------------------------------|--------------------| +| MAC-ehs | MAC-ehs header fixed part, bit | 24 | +| Layer 1 | TrCH type | HS-DSCH | +| | TTI | 2 ms | +| | Coding type | TC | +| | CRC, bit | 24 | +| | Applicable modulation scheme | QPSK, 16QAM, 64QAM | +| | Applicable with MIMO | Yes | + +## 7.5.26.2.1.4 TFCS + +| | | +|-----------|--------------------------| +| TFCS size | 2 | +| TFCS | SRBs for DCCH = TF0, TF1 | + +## 7.5.26.2.2 Physical channel parameters + +## 7.5.26.2.2.1 Physical channel parameters on DPCH + +See subclause 6.10.2.4.1.2.2.2 of [1] + +## 7.5.26.2.2.2 Physical channel parameters on HS-PDSCH + +See subclause 6.10.2.4.5.1.2.2.2 of [1] + +## 7.5.27 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:13.6 DL:13.6kbps SRBs for DCCH on DCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL on DPCH: 32 kbps plus support of HS-PDSCH and support of E-DCH, HS-PDSCH: category 11, E-DCH: category 1. + +This is supported in Release 6. + +## 7.5.27.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|---------------------------|---------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.1.1.1.1 of [1] | 6.10.2.4.1.3.1.1.1 of [1] | | +| TFCS | 6.10.2.4.1.3.1.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | 6.10.2.4.1.3.1.2 of [1] | | + +## 7.5.27.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.5.1.2.1.1 of [1] | 6.10.2.4.1.3.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.3.2.1.2 of [1] | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | 6.10.2.4.1.3.2.2 of [1] | | + +## 7.5.28 Conversational / speech / UL: 12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.28.1 Uplink + +## 7.5.28.1.1 Transport channel parameters + +## 7.5.28.1.1.1 Transport channel parameters for E-DCH + +## 7.5.28.1.1.1.1 MAC-d flow#1 parameters for Conversational / speech / UL: 12.2 kbps / CS RAB (non-scheduled) + +| | | | +|---------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| Higher layer | RAB/Signalling RB | RAB | +| PDCP | Header size, bit | 8 | +| RLC | Logical channel type | DTCH | +| | RLC mode | UM | +| | Payload sizes, bit | 48, 256 | +| | Max data rate, bps | Depends on UE category and TTI | +| | UMD PDU header, bit | 8 | +| MAC | MAC multiplexing | N/A | +| | MAC-d PDU size, bit | 56, 264 (non-scheduled) NOTE1 | +| | MAC-e/es header fixed part, bit | 18 | +| Layer 1 | TrCH type | E-DCH | +| | TTI | 10ms (alt. 2ms) (NOTE2) | +| | Coding type | TC | +| | CRC, bit | 24 | +| NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC | | | +| NOTE2: The support of 2ms TTI depends on the UE category. | | | + +7.5.28.1.1.1.2 MAC-d flow #2 parameters for UL: [max bit rate depending on UE category and TTI] +sSRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +## 7.5.28.1.2 Physical channel parameters + +## 7.5.28.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +## 7.5.28.2 Downlink + +## 7.5.28.2.1 Transport channel parameters + +## 7.5.28.2.1.1 Transport channel parameters for HS-DSCH + +## 7.5.28.2.1.1.1 MAC-d flow#1 parameters for Conversational / speech / DL: 12.2 kbps / CS RAB + +| | | Alt 1
RLC + MAC-hs
(Rel-5 and later
releases) | Alt 2
RLC + MAC-ehs
(Rel-7 and later
releases) | +|--------------|-----------------------------------|--------------------------------------------------------|---------------------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| PDCP | Header size, bit | 8 | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 48, 256 | 48, 256 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | 8 | +| MAC | MAC-d header, bit | 0 | 0 | +| | MAC multiplexing | N/A | N/A | +| | MAC-d PDU size, bit | 56, 264 | 56, 264 | +| | MAC-hs Type | MAC-hs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | +| Layer 1 | TrCH type | HS-DSCH | HS-DSCH | +| | TTI | 2 ms | 2 ms | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|----------------|-----------------------| +| | Coding type | TC | TC | +| | CRC, bit | 24 | 24 | +| | Applicable modulation schemes | QPSK,
16QAM | QPSK,
16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | +| NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). | | | | + +7.5.28.2.1.1.2 MAC-d flow#2 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +7.5.28.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +7.5.28.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +7.5.29 Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +7.5.29.1 Uplink + +7.5.29.1.1 Transport channel parameters + +7.5.29.1.1.1 Transport channel parameters for E-DCH + +7.5.29.1.1.1.1 MAC-d flow#1 parameters for Conversational / speech / UL:( 5.9, 4.75) kbps / CS RAB (non-scheduled) + +| | | | +|---------------------------------------------------------------------------------|---------------------------------|------------------------------------| +| Higher layer | RAB/Signalling RB | RAB | +| PDCP | Header size, bit | 8 | +| RLC | Logical channel type | DTCH | +| | RLC mode | UM | +| | Payload sizes, bit | 48, 104, 128 | +| | Max data rate, bps | Depends on UE category and TTI | +| | UMD PDU header, bit | 8 | +| MAC | MAC multiplexing | N/A | +| | MAC-d PDU size, bit | 56, 112, 136 (non-scheduled) NOTE1 | +| | MAC-e/es header fixed part, bit | 18 | +| Layer 1 | TrCH type | E-DCH | +| | TTI | 10ms (alt. 2ms) (NOTE2) | +| | Coding type | TC | +| | CRC, bit | 24 | +| NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC | | | +| NOTE2: The support of 2ms TTI depends on the UE category. | | | + +7.5.29.1.1.1.2 MAC-d flow #2 parameters for UL: [max bit rate depending on UE category and TTI] +SRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +7.5.29.1.2 Physical channel parameters + +7.5.29.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +7.5.29.2 Downlink + +7.5.29.2.1 Transport channel parameters + +7.5.29.2.1.1 Transport channel parameters for HS-DSCH + +7.5.29.2.1.1.1 MAC-d flow #1 parameters for Conversational / speech / DL:( 5.9, 4.75) kbps / CS +RAB + +| | | Alt 1
RLC + MAC-hs
(Rel-5 and later
releases) | Alt 2
RLC + MAC-ehs
(Rel-7 and later
releases) | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--------------------------------------------------------|---------------------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| PDCP | Header size, bit | 8 | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 48, 104, 128 | 48, 104, 128 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | 8 | +| MAC | MAC-d header, bit | 0 | 0 | +| | MAC multiplexing | N/A | N/A | +| | MAC-d PDU size, bit | 56, 112, 136 | 56, 112, 136 | +| | MAC-hs Type | MAC-hs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | +| Layer 1 | TrCH type | HS-DSCH | HS-DSCH | +| | TTI | 2 ms | 2 ms | +| | Coding type | TC | TC | +| | CRC, bit | 24 | 24 | +| | Applicable modulation schemes | QPSK,
16QAM | QPSK,
16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | +| NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). | | | | + +7.5.29.2.1.1.2 MAC-d flow #2 parameters for DL: [max bit rate depending on UE category] SRBs for +HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +7.5.29.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +7.5.29.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.5.30 Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.30.1 Uplink + +#### 7.5.30.1.1 Transport channel parameters + +##### 7.5.30.1.1.1 Transport channel parameters for E-DCH + +###### 7.5.30.1.1.1.1 MAC-d flow #1 parameters for Conversational / speech / UL:(12.2, 7.75, 5.9, 4.75) kbps / CS RAB (non-scheduled) + +See clause 6.10.2.4.6.9.1.1.1.1 of [1]. + +###### 7.5.30.1.1.1.2 MAC-d flow #2 parameters for UL: [max bit rate depending on UE category and TTI] SRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +#### 7.5.30.1.2 Physical channel parameters + +##### 7.5.30.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +### 7.5.30.2 Downlink + +#### 7.5.30.2.1 Transport channel parameters + +##### 7.5.30.2.1.1 Transport channel parameters for HS-DSCH + +###### 7.5.30.2.1.1.1 MAC-d flow#1 parameters for Conversational / speech / DL:(12.2, 7.75, 5.9, 4.75) kbps / CS RAB + +See clause 6.10.2.4.6.9.2.1.1.1 of [1]. + +###### 7.5.30.2.1.1.2 MAC-d flow#2 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +#### 7.5.30.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +##### 7.5.30.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.5.30a Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.30a.1 Uplink + +#### 7.5.30a.1.1 Transport channel parameters + +##### 7.5.30a.1.1.1 Transport channel parameters for E-DCH + +###### 7.5.30a.1.1.1.1 MAC-d flow #1 parameters for Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps / CS RAB (non-scheduled) + +| | | Alt 1
Fixed RLC +
MAC-e/es (Rel-6 and
later)
NOTE 3 | Alt 2
Flexible RLC + MAC-
i/is (Rel-8 and later
releases)
NOTE 3 | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|--|--| +| Higher layer | RAB/Signalling RB | RAB | | | | +| PDCP | Header size, bit | 8 | | | | +| RLC | Logical channel type | DTCH | | | | +| | RLC mode | UM | | | | +| | Payload sizes, bit | 48, 104, 128, 160, 256 | Flexible from 48 up to
up to 12000
(NOTE 4) | | | +| | Max data rate, bps | Depends on UE category and TTI | | | | +| | UMD PDU header, bit | 8 | | | | +| MAC | MAC multiplexing | N/A | | | | +| | MAC-d PDU size, bit | 56, 112, 136, 168, 264
(non-scheduled)
NOTE1 | Flexible | | | +| | MAC type | MAC-e/es | MAC-i/is | | | +| | MAC-e/es / MAC-i/is header
fixed part, bit | 18 | 24 | | | +| Layer 1 | TrCH type | E-DCH | | | | +| | TTI | 10ms (alt. 2ms) (NOTE 2) | | | | +| | Coding type | TC | | | | +| | CRC, bit | 24 | | | | +| NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC | | | | | | +| NOTE 2: The support of 2ms TTI depends on the UE category | | | | | | +| NOTE 3: Alternative 1 with Fixed RLC + MAC-e/es is the default configuration. For test cases that use alternative 2 (Flexible RLC + MAC-i/is) then this shall be explicitly stated in the test case. | | | | | | +| NOTE 4: The Maximum RLC payload size for Flexible RLC is 12024 bits (1503 octets, ref: TS 25.322 clause 9.2.2.9). The maximum SDU size above PDCP layer is limited to 12000 bits (1500 octets limit in QoS parameter "Max SDU size", ref: TS 24.008 clause 10.5.6.5). As no PDCP header is used in this radio bearer configuration then the RLC payload size has been limited to 12000 bits. | | | | | | + +###### 7.5.30a.1.1.1.2 MAC-d flow #2 parameters for UL: [max bit rate depending on UE category and TTI] SRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +## 7.5.30a.1.2 Physical channel parameters + +## 7.5.30a.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +## 7.5.30a.2 Downlink + +## 7.5.30a.2.1 Transport channel parameters + +## 7.5.30a.2.1.1 Transport channel parameters for HS-DSCH + +## 7.5.30a.2.1.1.1 MAC-d flow#1 parameters for Conversational / speech / DL:(12.2, 7.4, 5.9, 4.75) kbps / CS RAB + +| | | Alt 1
RLC + MAC-hs
(Rel-5 and later
releases)
NOTE2 | Alt 2
RLC + MAC-ehs
(Rel-7 and later
releases)
NOTE2 | +|--------------|-----------------------------------|-----------------------------------------------------------------|------------------------------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| PDCP | Header size, bit | 8 | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 48, 104, 128, 160, 256 | 48, 104, 128, 160, 256 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | 8 | +| MAC | MAC-d header, bit | 0 | 0 | +| | MAC multiplexing | N/A | N/A | +| | MAC-d PDU size, bit | 56, 112, 136, 168, 264 | 56, 112, 136, 168, 264 | +| | MAC-hs Type | MAC-hs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | +| Layer 1 | TrCH type | HS-DSCH | HS-DSCH | +| | TTI | 2 ms | 2 ms | +| | Coding type | TC | TC | +| | CRC, bit | 24 | 24 | +| | Applicable modulation schemes | QPSK, 16QAM | QPSK, 16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | +| | Applicable with Dual-Cell HSDPA | No | Yes | + +NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). + +NOTE2: Alternative 1 with Fixed RLC + MAC-hs is the default configuration. For test cases that use alternative 2 (Fixed RLC + MAC-ehs) then this shall be explicitly stated in the test case. + +## 7.5.30a.2.1.1.2 MAC-d flow#2 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +## 7.5.30a.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +## 7.5.30a.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.5.31 Conversational / speech / UL:(12.65, 8.85, 6.6) kbps DL: (12.65, 8.85, 6.6) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.31.1 Uplink + +#### 7.5.31.1.1 Transport channel parameters + +##### 7.5.31.1.1.1 Transport channel parameters for E-DCH + +###### 7.5.31.1.1.1.1 MAC-d flow#1 parameters for Conversational / speech / UL:(12.65, 8.85, 6.6) kbps / CS RAB (non-scheduled) + +See clause 6.10.2.4.6.10.1.1.1.1 of [1]. + +###### 7.5.31.1.1.1.2 MAC-d flow#2 parameters for UL: [max bit rate depending on UE category and TTI] SRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +#### 7.5.31.1.2 Physical channel parameters + +##### 7.5.31.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +### 7.5.31.2 Downlink + +#### 7.5.31.2.1 Transport channel parameters + +##### 7.5.31.2.1.1 Transport channel parameters for HS-DSCH + +###### 7.5.31.2.1.1.1 MAC-d flow#1 parameters for Conversational / speech / DL:(12.65, 8.85, 6.6) kbps / CS RAB + +See clause 6.10.2.4.6.10.2.1.1.1 of [1]. + +###### 7.5.31.2.1.1.2 MAC-d flow#2 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +#### 7.5.31.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +##### 7.5.31.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +## 7.5.32 Conversational / speech / UL:(23.85 12.65 8.85 6.6) DL:(23.85 12.65 8.85 6.6) kbps / CS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.32.1 Uplink + +#### 7.5.32.1.1 Transport channel parameters + +##### 7.5.32.1.1.1 Transport channel parameters for E-DCH + +###### 7.5.32.1.1.1.1 MAC-d flow#1 parameters for Conversational / speech / UL:( 23.85 12.65 8.85 6.6) kbps / CS RAB (non-scheduled) + +| | | | +|--------------|---------------------------------|--------------------------------------------------| +| Higher layer | RAB/Signalling RB | RAB | +| PDCP | Header size, bit | 8 | +| RLC | Logical channel type | DTCH | +| | RLC mode | UM | +| | Payload sizes, bit | 48, 144, 192, 264, 488 | +| | Max data rate, bps | Depends on UE category and TTI | +| | UMD PDU header, bit | 8 | +| MAC | MAC multiplexing | N/A | +| | MAC-d PDU size, bit | 56, 152, 200, 272 , 496 (non-scheduled)
NOTE1 | +| | MAC-e/es header fixed part, bit | 18 | +| Layer 1 | TrCH type | E-DCH | +| | TTI | 10ms (alt. 2ms) (NOTE2) | +| | Coding type | TC | +| | CRC, bit | 24 | + +NOTE1: Max MAC-e PDU content sizes depends on non-scheduled grant given by SRNC +NOTE2: The support of 2ms TTI depends on the UE category. + +###### 7.5.32.1.1.1.2 MAC-d flow#2 parameters for UL: [max bit rate depending on UE category and TTI] SRBs for E-DCH + +See clause 6.10.2.4.6.2.1.1.1.2 of [1]. + +#### 7.5.32.1.2 Physical channel parameters + +##### 7.5.32.1.2.1 Physical channel parameters on E-DPDCH + +See clause 6.10.2.4.6.1.1.2.1 of [1]. + +## 7.5.32.2 Downlink + +## 7.5.32.2.1 Transport channel parameters + +## 7.5.32.2.1.1 Transport channel parameters for HS-DSCH + +## 7.5.32.2.1.1.1 MAC-d flow#1 parameters for Conversational / speech / DL:(23.85 12.65 8.85 6.6) kbps / CS RAB + +| | | Alt 1
RLC + MAC-hs
(Rel-5 and later
releases) | Alt 2
RLC + MAC-ehs
(Rel-7 and later
releases) | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--------------------------------------------------------|---------------------------------------------------------| +| Higher Layer | RAB/Signalling RB | RAB | | +| PDCP | Header size, bit | 8 | | +| RLC | Logical channel type | DTCH | | +| | RLC mode | UM | | +| | Payload sizes, bit | 48, 144, 192, 264, 488 | 48, 144, 192, 264, 488 | +| | Max data rate, bps | depends on UE category
NOTE1 | | +| | UMD PDU header, bit | 8 | 8 | +| MAC | MAC-d header, bit | 0 | 0 | +| | MAC multiplexing | N/A | N/A | +| | MAC-d PDU size, bit | 56, 152, 200, 272, 496 | 56, 152, 200, 272, 496 | +| | MAC-hs Type | MAC-hs | MAC-ehs | +| | MAC-hs/ehs header fixed part, bit | 21 | 24 | +| Layer 1 | TrCH type | HS-DSCH | HS-DSCH | +| | TTI | 2 ms | 2 ms | +| | Coding type | TC | TC | +| | CRC, bit | 24 | 24 | +| | Applicable modulation schemes | QPSK,
16QAM | QPSK,
16QAM, 64QAM | +| | Applicable with MIMO | No | Yes | +| NOTE1: The peak throughput may be limited by the maximum number of MAC-d PDUs that can be included in a single MAC-hs or MAC-ehs PDU (see [25.321]). | | | | + +## 7.5.32.2.1.1.2 MAC-d flow#2 parameters for DL: [max bit rate depending on UE category] SRBs for HS-DSCH + +See clause 6.10.2.4.6.3.2.1.1.2 of [1]. + +## 7.5.32.2.2 Physical channel parameters + +The physical channel configuration shall use F-DPCH. + +## 7.5.32.2.2.1 Physical channel parameters on HS-PDSCH + +See clause 6.10.2.4.5.1.2.2.2 of [1]. + +7.5.33 Conversational / speech / UL:12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + ++ (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +#### 7.5.33.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.5.28.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +#### 7.5.33.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.28.2.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.34 Conversational / speech / UL:12.2 kbps DL: 12.2 kbps / CS RAB on E-DCH and HS-DSCH + ++ Streaming / unknown / UL:[max bit rate depending on UE category and TTI] +DL: [max bit rate depending on UE category] kbps / PS RAB + ++ (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +#### 7.5.34.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.5.28.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for Streaming RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.34.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.28.2.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Streaming RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.35 Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH ++ (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.35.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.9.1.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.35.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.6.9.2.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.35a Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + + (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.35a.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|----------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 7.5.30a.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1] | + +## 7.5.35a.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.30a.2.1.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.36 Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH ++ Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB ++ (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.36.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.9.1.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for Streaming RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | + +| | | | | | +|------------------|--|---------------------------|--|----------------------------| +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | +|------------------|--|---------------------------|--|----------------------------| + +### 7.5.36.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.6.9.2.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Streaming RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.36a Conversational / speech / UL:(12.2, 7.4, 5.9, 4.75) kbps DL: (12.2, 7.4, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH ++ Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB ++ (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.36a.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|--|----------------------|-----------------------|---------------------------------|----------------------------------| +| | | | | | + +| | | | | | +|-------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-----------------------------| +| Transport Channel | | 7.5.30a.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for Streaming RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.36a.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.30a.2.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Streaming RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.37 Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + ++ (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.37.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer | Signalling Radio Bearer | +|--|----------------------|-----------------------|-------------------------|-------------------------| +|--|----------------------|-----------------------|-------------------------|-------------------------| + +| | | | on DPCH | on E-DCH | +|-------------------|--|---------------------------------------------------------------------------------------------------------------|---------|-----------------------------| +| Transport Channel | | 7.5.29.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.37.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.29.2.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.38 Conversational / speech / UL:(5.9, 4.75) kbps DL: (5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + ++ Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + ++ (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.38.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer | Signalling Radio Bearer | +|--|----------------------|-----------------------|-------------------------|-------------------------| +|--|----------------------|-----------------------|-------------------------|-------------------------| + +| | | | on DPCH | on E-DCH | +|-------------------|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------------------------| +| Transport Channel | | 7.5.29.1.1.1.1 for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for Streaming RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.38.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 7.5.29.2.1.1.1 for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Streaming RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.39 Conversational / speech / UL: ( 12.65 8.85 6.6) kbps DL: (12.65 8.85 6.6) kbps / CS RAB on E-DCH and HS-DSCH ++ (1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +## 7.5.39.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.10.1.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +## 7.5.39.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.6.10.2.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.40 Conversational / speech / UL:( 12.65 8.85 6.6) kbps DL: (12.65 8.85 6.6) kbps / CS RAB on E-DCH and HS-DSCH + ++ Streaming / unknown / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + ++ (0, 1, 2 or 3) Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RABs + ++ UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH + +The minimum UE classes supporting this combination are: support of HS-PDSCH, DL on HS-PDSCH: category 11 and support of E-DCH, UL on E-DCH category 1. + +Support depends on the UE capability: Support for CS voice over HSPA. + +This is supported in Release 8. + +### 7.5.40.1 Uplink + +| | Radio Bearer on DPCH | Radio Bearer on E-DCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on E-DCH | +|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------| +| Transport Channel | | 6.10.2.4.6.10.1.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.6.1.1.1.1.1 of [1] for Streaming RBs
6.10.2.4.6.1.1.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.2.1.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.6.1.1.2.1 of [1] | | 6.10.2.4.6.1.1.2.1 of [1]. | + +### 7.5.40.2 Downlink + +The physical channel configuration shall use F-DPCH. + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.10.2.4.6.10.2.1.1.1 of [1] for CS over HSPA RBs
6.10.2.4.5.1.2.1.1.1 of [1] for Streaming RBs
6.10.2.4.5.1.2.1.1.1 of [1] for (0, 1, 2 or 3) Interactive/Background RBs | | 6.10.2.4.6.3.2.1.1.2 of [1] | +| TFCS | | | | | +| Physical Channel | | 6.10.2.4.5.1.2.2.2 of [1] | | 6.10.2.4.5.1.2.2.2 of [1] | + +7.5.4.1 RB for Conversational / speech / UL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) DL: (EVS 8 7.2 5.9 – AMR-WB IO 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +#### 7.5.4.1.1 Uplink + +##### 7.5.4.1.1.1 Transport channel parameters + +###### 7.5.4.1.1.1.1 Transport channel parameters for E-DCH + +See subclause 6.10.2.4.6.4.1.1.1 of [1]. + +###### 7.5.4.1.1.1.2 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.145.1.1.1 + +###### 7.5.4.1.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +##### 7.5.4.1.1.4 TFCS + +See subclause 7.1.145.1.1.3. + +##### 7.5.4.1.1.2 Physical channel parameters + +###### 7.5.4.1.1.2.1 Physical channel parameters on E-DPDCH + +See subclause 6.10.2.4.6.1.1.2.1 of [1]. + +###### 7.5.4.1.1.2.2 Physical channel parameters on DCH + +See subclause 7.1.145.1.2 + +#### 7.5.4.1.2 Downlink + +See subclause 7.4.145.2. + +7.5.4.2 RB for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +#### 7.5.4.2.1 Uplink + +##### 7.5.4.2.1.1 Transport channel parameters + +###### 7.5.4.2.1.1.1 Transport channel parameters for E-DCH + +See subclause 6.10.2.4.6.4.1.1.1 of [1]. + +###### 7.5.4.2.1.1.2 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.146.1.1.1 + +7.5.42.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.5.42.1.1.4 TFCS + +See subclause 7.1.146.1.1.3. + +7.5.42.1.2 Physical channel parameters + +7.5.42.1.2.1 Physical channel parameters on E-DPDCH + +See subclause 6.10.2.4.6.1.1.2.1 of [1]. + +7.5.42.1.2.2 Physical channel parameters on DCH + +See subclause 7.1.146.1.2 + +7.5.42.2 Downlink + +See subclause 7.4.34.2. + +7.5.43 RB for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +7.5.43.1 Uplink + +7.5.43.1.1 Transport channel parameters + +7.5.43.1.1.1 Transport channel parameters for E-DCH + +See subclause 6.10.2.4.6.4.1.1.1 of [1]. + +7.5.43.1.1.2 Transport channel parameters for Conversational / speech / UL: (EVS 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.147.1.1.1 + +7.5.43.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +7.5.43.1.1.4 TFCS + +See subclause 7.1.147.1.1.3. + +7.5.43.1.2 Physical channel parameters + +7.5.43.1.2.1 Physical channel parameters on E-DPDCH + +See subclause 6.10.2.4.6.1.1.2.1 of [1]. + +7.5.43.1.2.2 Physical channel parameters on DCH + +See subclause 7.1.147.1.2 + +7.5.43.2 Downlink + +See subclause 7.4.35.2. + +7.5.44 RB for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) DL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH + +#### 7.5.44.1 Uplink + +##### 7.5.44.1.1 Transport channel parameters + +###### 7.5.44.1.1.1 Transport channel parameters for E-DCH + +See subclause 6.10.2.4.6.4.1.1.1 of [1]. + +###### 7.5.44.1.1.2 Transport channel parameters for Conversational / speech / UL: (EVS 24.4 16.4 13.2 9.6 8 7.2 5.9 – AMR-WB IO 12.65 8.85 6.6) kbps / CS RAB + +See subclause 7.1.148.1.1.1 + +###### 7.5.44.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.2.4.1.2.1.1.1 of [1]. + +###### 7.5.44.1.1.4 TFCS + +See subclause 7.1.148.1.1.3. + +##### 7.5.44.1.2 Physical channel parameters + +###### 7.5.44.1.2.1 Physical channel parameters on E-DPDCH + +See subclause 6.10.2.4.6.1.1.2.1 of [1]. + +###### 7.5.44.1.2.2 Physical channel parameters on DCH + +See subclause 7.1.148.1.2 + +#### 7.5.44.2 Downlink + +See subclause 7.4.36.2. + +### 7.6 Void + +## 8 Examples of Radio Bearers and Signalling Radio Bearers for 3.84 Mcps TDD + +NOTE: The physical channel parameters were chosen for each RAB because they are typical for the targeted UE class to support the particular RAB. However based on current radio conditions UEs shall expect to be configured to use any timeslot/code/spreading factors combinations that support the RAB and are supported by that UE's physical capabilities. + +### 8.1 Combinations on DPCH + +#### 8.1.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.1 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.2 Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.2 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.3 Stand-aloneUL:13.6 DL:13.6 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.3 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.4 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.5 Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB + UL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.5 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.6 Conversational / speech / UL:7.95 DL:7.95 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.6 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.7 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.7 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +### **8.1.8 Conversational / speech / UL:6.7 DL: 6.7 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.8 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.9 Conversational / speech / UL:5.9 DL:5.9 kbps / CS rab + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.9 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.10 Conversational / speech / UL:5.15 DL:5.15 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.10 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.11 Conversational / speech / UL:4.75 DL:4.75 kbps / CS RAB + UL:1.7 DL:1.7 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.11 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.12 Conversational / unknown / UL:28.8 DL:28.8kbps / CS RAB + UL:3.4 DL:3.4kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.12 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.13 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.13 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### **8.1.14 Conversational / unknown / UL:32 DL: 32 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.14 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.15 Streaming / unknown / UL:14.4 DL:14.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.15 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.16 Streaming / unknown / UL:28.8 DL:28.8 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.16 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.17 Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.17 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### **8.1.18 Streaming / unknown / UL:0 DL: 64 kbps / CS or PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH** + +Void. + +#### **8.1.19 Streaming / unknown / UL: 64 DL:0 kbps / CS or PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH** + +Void + +#### **8.1.20 Interactive or background / UL: 32 DL:8 kbps / PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.23 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps ; DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI + +This is supported in Release '99. + +#### **8.1.21 Interactive or background / UL: 64 DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +Void. + +#### **8.1.22 Interactive or background / UL: 32 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.25 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps ; DL: 64kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### **8.1.23 Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.26 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 64kbps . The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.24 Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.27 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 128kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.25 Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.28 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbps; DL: 128kbps. The minimum UE class to support the alternative UL configuration is UL: 128kbps plus support for 32 TB/TTI. + +This is supported in Release '99. + +#### **8.1.26 Interactive or background / UL:64 DL:144 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.29 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 128kbps. + +This is supported in Release '99. + +#### **8.1.27 Interactive or background / UL: 144 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.30 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbps plus support for maximum 16 TBs per TTI; DL: 128kbps. + +This is supported in Release '99. + +#### **8.1.28 Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.31 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.29 Interactive or background / UL: 64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.32 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL: 768kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +### **8.1.30 Interactive or background / UL:128 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.33 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbps; DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL: 768kbps. The minimum UE class to support the alternative UL configuration is UL: 128kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +### **8.1.31 Interactive or background / UL:384 DL:384 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.34 of [1]. + +The minimum UE classes supporting this combination are UL: 384kbps; DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL 768 kbps. The minimum UE class to support the alternative UL physical configuration 2 is UL 768 kbps. + +This is supported in Release '99. + +### **8.1.32 Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.35 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 2048kbps. The minimum UE class to support the alternative DL configuration is 2048kbps plus support for maximum TB bits 81920 and maximum TC TB bits 81920. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +### **8.1.33 Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +Void. + +### **8.1.34 Interactive or background / UL: 384 DL:2048 kbps / PS RAB+UL:3.4 DL:3.4 kbps SRBs for DCCH** + +Void. + +### **8.1.35 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.38 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.36 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.39 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.37 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.40 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps ; DL: 64kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.38 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.41 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 128 kbps. + +This is supported in Release '99. + +#### **8.1.39 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.42 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 384kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.40 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.43 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 384 kbps plus. The minimum UE class to support the alternative DL configuration is DL: 768kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.41 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:128 DL:2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.44 of [1]. + +The minimum UE classes supporting this combination are UL: 384kbps plus support for 2 physical channels per TS; DL: 2048 kbps plus support for maximum TB bits 40960, maximum TC TB bits 40960, or if an alternative RAB is used, plus support for maximum TB bits 81920 and maximum TB TC bits 81920. + +This is supported in Release '99. + +#### **8.1.42 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:57.6 DL:57.6 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.45 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps. + +This is supported in Release '99. + +#### **8.1.43 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:0 DL:64 kbps / CS or PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +Void. + +#### **8.1.44 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.49 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64kbps + +This is supported in Release '99. + +#### **8.1.45 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.50 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 128 kbps. + +This is supported in Release '99 + +#### **8.1.46 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.51 of [1]. + +The minimum UE classes for this combinations are UL: 64 kbps; DL: 128kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.47 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.52 of [1]. + +The minimum UE classes for this combination are UL: 64 kbps ; DL: 384kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB/TTI. + +This is supported in Release '99. + +#### **8.1.48 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.53 of [1]. + +The minimum UE classes for this combination are UL: 384kbps; DL: 384kbps. The minimum UE class to support the alternative UL configuration is UL: 384kbps plus support for 32 TB/TTI. + +This is supported in Release '99. + +#### **8.1.49 Interactive or background / UL:64 DL:128 kbps / PS RAB + streaming / unknown / UL:0 DL:64 kbps / CS or PS RAB + UL:3.4 DL:3.4kbps SRBs for DCCH** + +Void. + +#### **8.1.50 Conversational / Speech UL:(12.2-7.95-5.9-4.75) & DL:(12.2-7.95-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.4a of [1]. + +The minimum UE classes for this combination are UL: 32 kbps; DL: 32 kbps. + +This is supported in Release '99. + +#### **8.1.51 Conversational / Speech UL:(10.2-6.7-5.9-4.75) & DL:(10.2-7.95-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.5a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.52 Conversational / Speech UL:(7.4-6.7-5.9-4.75) & DL:(7.4-6.7-5.9-4.75) CS RAB + UL:3.4 & DL 3.4kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.7a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +#### **8.1.53 Interactive or Background UL:8 & DL:8kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH** + +See subclause 6.10.3.4.1.23a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### **8.1.54 Interactive or Background UL:16 & DL:16kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH** + +See subclause 6.10.3.4.1.23b of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### **8.1.55 Interactive or Background UL:32 & DL:32kbps PS RAB + UL:3.4 & DL:3.4 SRBs for DCCH** + +See subclause 6.10.3.4.1.23c of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +#### **8.1.56 Interactive or Background UL:32 & DL:32kbps PS RAB (20msTTI) + UL:3.4 & DL:3.4 SRBs for DCCH** + +See subclause 6.10.3.4.1.23d of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### **8.1.57 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH** + +See subclause 6.10.3.4.1.38a of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps. + +This is supported in Release '99. + +#### **8.1.58 Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:8 & DL:8kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38b of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. + +This is supported in Release '99. + +#### **8.1.59 Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:32 & DL:32kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38c of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +#### **8.1.60 Conversational / Speech UL:12.2 & DL:12.2kbps CS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38d of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM mode entities, DL: 64 kbps plus support for 5 AM mode entities. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB per TTI and support for 5 AM mode entities. + +This is supported in Release '99. + +#### **8.1.61 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:0 & DL:0kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38e of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps. + +This is supported in Release '99. + +#### **8.1.62 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:8 & DL:8kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38f of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps. + +This is supported in Release '99. + +#### **8.1.63 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:16 & DL:16kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38g of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +#### **8.1.64 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:32 & DL:32kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38h of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 32 kbps.. + +This is supported in Release '99. + +**8.1.65 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:64 & DL:64kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38i of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps + 48 Configured TFCs, DL: 64 kbps + 64 Configured TFCs. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB per TTI and 48 Configured TFCs. + +This is supported in Release '99. + +**8.1.66 Conversational / Speech UL:(12.2 7.95 5.9 4.75) & DL:(12.2 7.95 5.9 4.75)kbps CS RAB + Interactive or Background UL:64 & DL:128kbps PS RAB + UL3.4 & DL:3.4kbps SRB's for DCCH** + +See subclause 6.10.3.4.1.38j of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps + 48 Configured TFCs, DL: 128 kbps.. The minimum UE class to support the alternative UL configuration is UL: 64kbps plus support for 16 TB per TTI and 48 Configured TFCs. + +This is supported in Release '99. + +**8.1.67 Conversational / speech / UL:(12.2 7.95 5.9 4.75) kbps DL:(12.2 7.95 5.9 4.75) kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.49a of [1]. + +The minimum UE classes supporting this combination are UL:64 kbps; DL:64 kbps. + +This is supported in Release '99. + +**8.1.68 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.51a of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release '99. + +**8.1.69 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.51b of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. + +This is supported in Release '99. + +**8.1.70 Interactive or background / UL:8 DL:8 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.56 of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps plus support for 5 AM entities, DL: 32 kbps plus support for 5 AM entities. The minimum UE class to support the alternative UL configuration is UL: 32 kbps plus support for 5 AM mode entities and 8 TB per TTI. + +This is supported in Release '99. + +### **8.1.71 Interactive or background / UL:64 DL:64 kbps / PS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.57 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM mode entities; DL: 64 kbps plus support for 5 AM mode entities. The minimum UE class to support the alternative UL configuration is UL: 64 kbps plus support for 5 AM mode entities and 16 TB per TTI. + +This is supported in Release '99. + +### **8.1.72 Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH.** + +See subclause 6.10.3.4.1.58 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM mode entities; DL: 64 kbps plus support for 5 AM mode entities. + +This is supported in Release '99. + +### **8.1.72a Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH – Alternative** + +This configuration optimises the flexibility of the Transport Format Selection by adding an omitted Transport Format, to the transport channel parameters given in the reference subclause 6.10.3.4.1.58 of [1], for the downlink transport channel Streaming / unknown / DL:64 kbps PS RAB. + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM mode entities; DL: 64 kbps plus support for 5 AM mode entities. + +This is supported in Release '99. + +#### **8.1.72a.1 Uplink** + +See subclause 6.10.3.4.1.58.1 of [1] + +## 8.1.72a.2 Downlink + +## 8.1.72a.2.1 Transport channel parameters + +## 8.1.72a.2.1.1 Transport channel parameters for Streaming / unknown / DL:64 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 64000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Max number of bits/radio frame before rate matching | | 2019 | +| | RM attribute | | 125-165 | + +## 8.1.72a.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.2 of [1]. + +## 8.1.72a.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.72a.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (64 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1), | + +## 8.1.72a.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 6 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 1640 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.64 | + +## 8.1.73 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.61 of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32 kbps. + +This is supported in Release '99. + +## 8.1.74 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH (Multiframe) + +See subclause 6.10.3.4.1.1a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +## 8.1.75 Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM mode entities; DL: 128kbps. + +This is supported in Release '99. + +### 8.1.75.1 Uplink + +See subclause 6.10.3.4.1.58.1 of [1] + +### 8.1.75.2 Downlink + +#### 8.1.75.2.1 Transport channel parameters + +##### 8.1.75.2.1.1 Transport channel parameters for Streaming / unknown / DL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 128000 | +| | UM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Max number of bits/radio frame before rate matching | | 4038 | +| | RM attribute | | 125-165 | + +##### 8.1.75.2.1.2 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.1 of [1]. + +##### 8.1.75.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.75.2.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1), | + +## 8.1.75.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 5 codes x 2 time slot | +| | Max. Number of data bits/radio frame | 2744 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.60 | + +## 8.1.76 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:8 kbps / PS RAB – TF0 contains zero Transport Blocks. + +NOTE: Conversational / unknown / DL:8 kbps / PS RAB – TF0 contains zero Transport Blocks. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps. + +This is supported in Release '99. + +## 8.1.76.1 Uplink + +## 8.1.76.1.1 Transport channel parameters + +## 8.1.76.1.1.1 Transport channel parameters for Conversational / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +## 8.1.76.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1] + +## 8.1.76.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.76.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 (alt. 12) | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1)
(alt. (TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF0, TF2, TF0), (TF1, TF2, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF0, TF2, TF1), (TF1, TF2, TF1)) | + +## 8.1.76.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCl code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.68 (alt. 0.64) | + +## 8.1.76.2 Downlink + +## 8.1.76.2.1 Transport channel parameters + +## 8.1.76.2.1.1 Transport channel parameters for Conversational / unknown / DL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +## 8.1.76.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.2 of [1]. + +## 8.1.76.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.76.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +## 8.1.76.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 716 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.96 | + +## 8.1.77 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:8 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +NOTE: Conversational / unknown / DL:8 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps. + +This is supported in Release '99. + +## 8.1.77.1 Uplink + +## 8.1.77.1.1 Transport channel parameters + +## 8.1.77.1.1.1 Transport channel parameters for Conversational / unknown / UL:8 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +## 8.1.77.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.2 of [1] + +## 8.1.77.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.77.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 (alt. 12) | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1)
(alt. (TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0),
(TF1, TF1, TF0), (TF0, TF2, TF0), (TF1, TF2, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF1, TF1), (TF0, TF2, TF1), (TF1, TF2, TF1)) | + +## 8.1.77.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.68 (alt. 0.64) | + +## 8.1.77.2 Downlink + +## 8.1.77.2.1 Transport channel parameters + +## 8.1.77.2.1.1 Transport channel parameters for Conversational / unknown / DL:8 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1044 | +| | Max number of bits/radio frame before rate matching | | 261 | +| | RM attribute | | 135-175 | + +## 8.1.77.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.2 of [1]. + +## 8.1.77.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.77.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (8 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF0, TF1, TF0), (TF1, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF0, TF1, TF1), (TF1, TF1, TF1) | + +## 8.1.77.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 716 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.72 | + +## 8.1.78 Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:16 kbps / PS RAB – TF0 contains zero Transport Blocks. + +NOTE: Conversational / unknown / DL:16 kbps / PS RAB – TF0 contains zero Transport Blocks. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps. + +This is supported in Release '99. + +## 8.1.78.1 Uplink + +## 8.1.78.1.1 Transport channel parameters + +## 8.1.78.1.1.1 Transport channel parameters for Conversational / unknown / UL:16 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +## 8.1.78.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1] + +## 8.1.78.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.78.1.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 (alt 18) | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1)
(alt ((TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF1, TF2, TF1), (TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF2, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1), (TF2, TF2, TF1))) | + +## 8.1.78.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF4 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 904 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.96 (alt. 0.92) | + +## 8.1.78.2 Downlink + +## 8.1.78.2.1 Transport channel parameters + +## 8.1.78.2.1.1 Transport channel parameters for Conversational / unknown / DL:16 kbps / PS RAB + +| | | | | +|--------------|-----------------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 328 | +| | TFS | TF0, bits | 0x328 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +## 8.1.78.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1. 23.2.1.1 of [1] + +## 8.1.78.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.78.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +## 8.1.78.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 716 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.72 | + +## 8.1.79 Conversational / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +NOTE: Conversational / unknown / UL:16 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +NOTE: Conversational / unknown / DL:16 kbps / PS RAB – TF0 contains one Transport Block of zero size. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration is UL: 64kbps. + +This is supported in Release '99. + +## 8.1.79.1 Uplink + +## 8.1.79.1.1 Transport channel parameters + +## 8.1.79.1.1.1 Transport channel parameters for Conversational / unknown / UL:16 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | UMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +## 8.1.79.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1] + +## 8.1.79.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.79.1.1.4 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 (alt 18) | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1)
(alt. ((TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF1, TF1, TF1), (TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF2, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1), (TF2, TF1, TF1)) | + +## 8.1.79.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF4 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 904bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.96 (alt. 0.92) | + +## 8.1.79.2 Downlink + +## 8.1.79.2.1 Transport channel parameters + +## 8.1.79.2.1.1 Transport channel parameters for Conversational / unknown / DL:16 kbps / PS RAB + +NOTE: In case of using this alternative, CRC parity bits are to be attached every time since number of TrBlks are 1 even if there is no data on the RAB (see subclause 4.2.1.1 in [3]). + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | UM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 8 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 0, 328 | +| | TFS | TF0, bits | 1x0 | +| | | TF1, bits | 1x328 | +| | | TF2, bits | 2x328 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2076 | +| | Max number of bits/radio frame before rate matching | | 519 | +| | RM attribute | | 135-175 | + +## 8.1.79.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.1 of [1] + +## 8.1.79.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.79.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (16 kbps Conversational RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +## 8.1.79.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 716 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.72 | + +## 8.1.80 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + Interactive or Background / UL:0 DL:0 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 32kbps plus support for 5 AM mode entities, DL: 32kbps plus support for 5 AM mode entities. + +This is supported in Release '99. + +## 8.1.80.1 Uplink + +## 8.1.80.1.1 Transport channel parameters + +## 8.1.80.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.1.1.1 of [1]. + +## 8.1.80.1.1.2 Transport channel parameters for Interactive or Background / UL:0 + UL:0 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-----------------------------------------------------|-----------|--------------------------------|------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 0 | 0 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 0 | | +| | Max number of bits/radio frame before rate matching | | 0 | | +| | RM attribute | | 130-170 | | + +## 8.1.80.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1]. + +## 8.1.80.1.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1) | + +## 8.1.80.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bit | +| | Puncturing Limit | 0.68 | + +## 8.1.80.2 Downlink + +## 8.1.80.2.1 Transport channel parameters + +## 8.1.80.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.2.1.1 of [1]. + +## 8.1.80.2.1.2 Transport channel parameters for Interactive or Background / DL:0 + DL:0 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | RAB | RAB | +|--------------|-----------------------------------------------------|--------------------------------|------| +| RLC | Logical channel type | DTCH | DTCH | +| | RLC mode | AM | AM | +| | Payload sizes, bit | 320 | 320 | +| | Max data rate, bps | 0 | 0 | +| | AMD PDU header, bit | 16 | 16 | +| MAC | MAC header, bit | 4 | 4 | +| | MAC multiplexing | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | DCH | | +| | TB sizes, bit | 340 | | +| | TFS TF0, bits | 0x340 | | +| | TTI, ms | 20 | | +| | Coding type | TC | | +| | CRC, bit | 16 | | +| | Max number of bits/TTI after channel coding | 0 | | +| | Max number of bits/radio frame before rate matching | 0 | | +| | RM attribute | 130-170 | | + +## 8.1.80.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.80.2.1.4 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 0+0kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF1) | + +## 8.1.80.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 2 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 472 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bit | +| | Puncturing limit | 0.68 | + +## 8.1.81 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64 kbps. + +This is supported in Release '99. + +### 8.1.81.1 Uplink + +#### 8.1.81.1.1 Transport channel parameters + +##### 8.1.81.1.1.1 Transport channel parameters for Conversational / unknown / UL:64 kbps / CS RAB + +See subclause 6.10.3.4.1.13.1.1.1 of [1]. + +##### 8.1.81.1.1.2 Transport channel parameters for Interactive or Background / UL:8 + UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.56.1.1.1 of [1] + +##### 8.1.81.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1]. + +#### 8.1.81.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 (alt. 12) | +| TFCS | (64 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1)
(alt. (TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF1, TF2, TF1)) | + +#### 8.1.81.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------------------------------------| +| DPCH Uplink | Midamble | 256 chips | +| | Codes and time slots | SF4 x 1 code x 1 time slot
SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 1584 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.60(alt. 0.56) | + +### 8.1.81.2 Downlink + +#### 8.1.81.2.1 Transport channel parameters + +##### 8.1.81.2.1.1 Transport channel parameters for Conversational / unknown / DL:64 kbps / CS RAB + +See subclause 6.10.3.4.1.13.2.1.1 of [1]. + +##### 8.1.81.2.1.2 Transport channel parameters for Interactive or Background / DL:8 + DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.56.2.1.1 of [1] + +##### 8.1.81.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.81.2.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (64 kbps Conversational RAB, 8+8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 8.1.81.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 6 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 1640 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.60 | + +## 8.1.82 Streaming / unknown / UL:8 DL:16 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 8.1.82.1 Uplink + +## 8.1.82.1.1 Transport channel parameters + +## 8.1.82.1.1.1 Transport channel parameters for Streaming / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 8.1.82.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.2.23a.1.1.2 of [1] + +## 8.1.82.1.1.3 Transport channel parameters for UL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.2.2.1.1.1 of [1] + +## 8.1.82.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 (alt 12) | +| TFCS | (8 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1)
(alt. ((TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1), (TF1, TF2, TF1))) | + +## 8.1.82.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.64 | + +## 8.1.82.2 Downlink + +## 8.1.82.2.1 Transport channel parameters + +## 8.1.82.2.1.1 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +| | | | | +|--------------|-----------------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 16000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2028 | +| | Max number of bits/radio frame before rate matching | | 507 | +| | RM attribute | | 125-165 | + +## 8.1.82.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.2.23.2.1.2 of [1] + +## 8.1.82.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.2.2.2.1.1 of [1] + +## 8.1.82.2.1.4 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 | +| TFCS | (16 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1) | + +## 8.1.82.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 2 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 472 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.48 | + +## 8.1.83 Streaming / unknown / UL:8 DL:32 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release '99. + +## 8.1.83.1 Uplink + +## 8.1.83.1.1 Transport channel parameters + +## 8.1.83.1.1.1 Transport channel parameters for Streaming / unknown / UL:8 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 8000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 1068 | +| | Max number of bits/radio frame before rate matching | | 267 | +| | RM attribute | | 135-175 | + +## 8.1.83.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.2.23a.1.1.2 of [1] + +## 8.1.83.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.2.2.1.1.1 of [1] + +## 8.1.83.1.1.4 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 8 (alt. 12) | +| TFCS | (8 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1)
(alt (TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1), (TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1), (TF1, TF2, TF1)) | + +## 8.1.83.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.64 | + +## 8.1.83.2 Downlink + +## 8.1.83.2.1 Transport channel parameters + +## 8.1.83.2.1.1 Transport channel parameters for Streaming / unknown / DL: 32 kbps / PS RAB + +| | | | | +|--------------|-----------------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 32000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | TTI, ms | | 40 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 4044 | +| | Max number of bits/radio frame before rate matching | | 1011 | +| | RM attribute | | 125-165 | + +## 8.1.83.2.1.2 Transport channel parameters for Interactive or Background / DL: 8 kbps / PS RAB + +See subclause 6.10.3.4.2.23.2.1.2 of [1] + +## 8.1.83.2.1.3 Transport channel parameters for DL: 3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.2.2.2.1.1 of [1] + +## 8.1.83.2.1.4 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (32 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF0, TF1), (TF1, TF1, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1) | + +## 8.1.83.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 5 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 1204 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.80 | + +## 8.1.84 Streaming / unknown / UL:32 DL:256 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. + +This is supported in Release '99. + +## 8.1.84.1 Uplink + +## 8.1.84.1.1 Transport channel parameters + +## 8.1.84.1.1.1 Transport channel parameters for Streaming / unknown / UL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 320 | +| | Max data rate, bps | | 32000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 336 | +| | TFS | TF0, bits | 0x336 | +| | | TF1, bits | 1x336 | +| | | TF2, bits | 2x336 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 2124 | +| | Max number of bits/radio frame before rate matching | | 1062 | +| | RM attribute | | 135-175 | + +## 8.1.84.1.1.2 Transport channel parameters for Interactive or Background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1] + +## 8.1.84.1.1.3 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.84.1.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 (alt 18) | +| TFCS | (32 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0, TF0, TF0), (TF1, TF0, TF0), (TF2, TF0, TF0),
(TF0, TF1, TF0), (TF1, TF1, TF0), (TF2, TF1, TF0),
(TF0, TF0, TF1), (TF1, TF0, TF1), (TF2, TF0, TF1),
(TF0, TF1, TF1), (TF1, TF1, TF1), (TF2, TF1, TF1)
(alt. ((TF0, TF0, TF0), (TF0, TF1, TF0), (TF0, TF2, TF0) (TF0, TF0, TF1), (TF0, TF1, TF1),
(TF0, TF2, TF1), (TF1, TF0, TF0), (TF1, TF1, TF0), (TF1, TF2, TF0) (TF1, TF0, TF1), (TF1,
TF1, TF1), (TF1, TF2, TF1),
(TF2, TF0, TF0), (TF2, TF1, TF0), (TF2, TF2, TF0), (TF2, TF0, TF1), (TF2, TF1, TF1), (TF2,
TF2, TF1)) | + +## 8.1.84.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF4 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 904 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.60 | + +## 8.1.84.2 Downlink + +## 8.1.84.2.1 Transport channel parameters + +## 8.1.84.2.1.1 Transport channel parameters for Streaming / unknown / DL:256 kbps / PS RAB + +| | | | | +|--------------|-----------------------------------------------------|-----------|---------| +| Higher layer | RAB/Signalling RB | | RAB | +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 256000 | +| | AMD PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 3x656 | +| | | TF4, bits | 4x656 | +| | TTI, ms | | 10 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Max number of bits/radio frame before rate matching | | 8076 | +| | RM attribute | | 125-165 | + +## 8.1.84.2.1.2 Transport channel parameters for Interactive or Background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1. 23.2.1.2 of [1] + +## 8.1.84.2.1.3 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.84.2.1.4 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 20 | +| TFCS | (256 kbps Streaming RAB, 8 kbps I/B RAB, DCCH)=
(TF0,TF0,TF0), (TF1,TF0,TF0), (TF2,TF0,TF0), (TF3,TF0,TF0), (TF4,TF0,TF0),
(TF0,TF1,TF0), (TF1,TF1,TF0), (TF2,TF1,TF0), (TF3,TF1,TF0), (TF4,TF1,TF0),
(TF0,TF0,TF1), (TF1,TF0,TF1), (TF2,TF0,TF1), (TF3,TF0,TF1), (TF4,TF0,TF1),
(TF0,TF1,TF1), (TF1,TF1,TF1), (TF2,TF1,TF1), (TF3,TF1,TF1), (TF4,TF1,TF1), | + +## 8.1.84.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|-------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 5 codes x 4 time slots | +| | Max. Number of data bits/radio frame | 5504 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.64 | + +## 8.1.85 Interactive or background / UL:16 DL:16 kbps / PS RAB + Interactive or Background / UL:16 DL:16 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release '99. + +## 8.1.85.1 Uplink + +## 8.1.85.1.1 Transport channel parameters + +## 8.1.85.1.1.1 Transport channel parameters for Interactive or Background / UL:16 + UL:16 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | RAB | RAB | +|--------------|-----------------------------------------------------|--------------------------------|-------------------| +| RLC | Logical channel type | DTCH | DTCH | +| | RLC mode | AM | AM | +| | Payload sizes, bit | 320 (alt 128) | 320 (alt 128) | +| | Max data rate, bps | 16000 | 16000 | +| | AMD PDU header, bit | 16 | 16 | +| MAC | MAC header, bit | 4 | 4 | +| | MAC multiplexing | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | DCH | | +| | TB sizes, bit | 340 | | +| | TFS | TF0, bits | 0x340 (alt 0x148) | +| | | TF1, bits | 1x340 (alt 1x148) | +| | | TF2, bits | 2x340 (alt 5x148) | +| | TTI, ms | 40 | | +| | Coding type | TC | | +| | CRC, bit | 16 | | +| | Max number of bits/TTI after channel coding | 2148 (alt 2472) | | +| | Max number of bits/radio frame before rate matching | 537 (alt 618) | | +| | RM attribute | 135-175 | | + +## 8.1.85.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1] + +## 8.1.85.1.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (16 kbps RAB + 16 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1), (TF1, TF1), (TF2, TF1) | + +## 8.1.85.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|----------------------------| +| DPCH Uplink | Midamble | 512 chips | +| | Codes and time slots | SF8 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 452 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.64 (alt. 0.60) | + +## 8.1.85.2 Downlink + +## 8.1.85.2.1 Transport channel parameters + +## 8.1.85.2.1.1 Transport channel parameters for Interactive or background / DL:16 + DL:16 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | RAB | RAB | +|--------------|-----------------------------------------------------|--------------------------------|-------| +| RLC | Logical channel type | DTCH | DTCH | +| | RLC mode | AM | AM | +| | Payload sizes, bit | 320 | 320 | +| | Max data rate, bps | 16000 | 16000 | +| | AMD PDU header, bit | 16 | 16 | +| MAC | MAC header, bit | 4 | 4 | +| | MAC multiplexing | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | DCH | | +| | TB sizes, bit | 340 | | +| | TFS | TF0, bits | 0x340 | +| | | TF1, bits | 1x340 | +| | | TF2, bits | 2x340 | +| | TTI, ms | 40 | | +| | Coding type | TC | | +| | CRC, bit | 16 | | +| | Max number of bits/TTI after channel coding | 2148 | | +| | Max number of bits/radio frame before rate matching | 537 | | +| | RM attribute | 135-175 | | + +## 8.1.85.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1] + +## 8.1.85.2.1.3 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------| +| TFCS size | 6 | +| TFCS | (16 kbps RAB + 16 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF0, TF1), (TF1, TF1), (TF2, TF1) | + +## 8.1.85.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 512 chips | +| | Codes and time slots | SF16 x 2 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 472 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.68 | + +## 8.1.86 Interactive or background / UL:64 DL:8 kbps / PS RAB + Interactive or Background / UL:64 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM entities, DL: 32 kbps.plus support for 5 AM entities. + +This is supported in Release '99. + +### 8.1.86.1 Uplink + +See subclause 6.10.3.4.1.57.1 of [1] + +### 8.1.86.2 Downlink + +See subclause 6.10.3.4.1.56.2 of [1] + +## 8.1.87 Interactive or Background / UL:64 DL:128 kbps / PS RAB + Interactive or Background / UL:64 DL:128 kbps / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM entities, DL: 128kbps. + +This is supported in Release '99. + +### 8.1.87.1 Uplink + +See subclause 6.10.3.4.1.57.1 of [1]. + +### 8.1.87.2 Downlink + +#### 8.1.87.2.1 Transport channel parameters + +##### 8.1.87.2.1.1 Transport channel parameters for Interactive or background / DL:128 + DL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-----------------------------------------------------|-----------|--------------------------------|------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 128000 | 128000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 8556 | | +| | Max number of bits/radio frame before rate matching | | 4278 | | +| | RM attribute | | 120-160 | | + +## 8.1.87.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.87.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF3,TF0), (TF4,TF0),
(TF0,TF1), (TF1,TF1), (TF2,TF1), (TF3,TF1), (TF4,TF1) | + +## 8.1.87.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 9 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 2468 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.52 | + +## 8.1.88 Interactive or Background / UL:64 DL:384 kbps / PS RAB + Interactive or Background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. + +This is supported in Release '99. + +## 8.1.88.1 Uplink + +See subclause 6.10.3.4.1.57.1 of [1]. + +## 8.1.88.2 Downlink + +## 8.1.88.2.1 Transport channel parameters + +## 8.1.88.2.1.1 Transport channel parameters for Interactive or background / DL:384 + DL:384 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-----------------------------------------------------|-----------|--------------------------------|--------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 384000 | 384000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 4x340 | | +| | | TF4, bits | 8x340 | | +| | | TF5, bits | 12x340 | | +| | TTI, ms | | 10 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 12828 | | +| | Max number of bits/radio frame before rate matching | | 12828 | | +| | RM attribute | | 110-150 | | + +## 8.1.88.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.88.2.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 12 | +| TFCS | (384 kbps RAB + 384 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0), (TF5, TF0)
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1), (TF5, TF1) | + +## 8.1.88.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|-------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 9 codes x 3 time slots | +| | Max. Number of data bits/radio frame | 7436 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.56 | + +8.1.89 Interactive or background / UL:128 DL:128 kbps / PS RAB + +Interactive or Background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 +kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 128kbps. The minimum UE class to support the alternative UL configuration (128-bit payload size) is UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +This is supported in Release '99. + +## 8.1.89.1 Uplink + +## 8.1.89.1.1 Transport channel parameters + +## 8.1.89.1.1.1 Transport channel parameters for Interactive or Background / UL:128 + UL:128 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-----------------------------------------------------|-----------|--------------------------------|----------------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 (alt. 128) | 320 (alt. 128) | +| | Max data rate, bps | | 128000 | 128000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 (alt. 148) | | +| | TFS | TF0, bits | 0x340 (alt. 0x148) | | +| | | TF1, bits | 1x340 (alt. 1x148) | | +| | | TF2, bits | 2x340 (alt. 7x148) | | +| | | TF3, bits | 4x340 (alt. 14x148) | | +| | | TF4, bits | 8x340 (alt. 20x148) | | +| | TTI, ms | | 20 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 8556 (alt. 9852) | | +| | Max number of bits/radio frame before rate matching | | 4278 (alt. 4926) | | +| | RM attribute | | 120-160 | | + +## 8.1.89.1.1.2 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1]. + +## 8.1.89.1.1.3 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 9 (alt. 10) | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1)
(alt (TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0),
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1)) | + +## 8.1.89.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|--------------------------------------------------------| +| DPCH Uplink | Midamble | 256 chips | +| | Codes and time slots | SF2 x 1 code x 1 time slot+ SF4 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 3168 bits | +| | TFCI code word | 16 bits | +| | TPC | 2 bits | +| | Puncturing Limit | 0.68(alt. 0.60) | + +## 8.1.89.2 Downlink + +## 8.1.89.2.1 Transport channel parameters + +## 8.1.89.2.1.1 Transport channel parameters for Interactive or background / DL:128 + DL:128 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | RAB | RAB | +|--------------|-----------------------------------------------------|--------------------------------|--------| +| RLC | Logical channel type | DTCH | DTCH | +| | RLC mode | AM | AM | +| | Payload sizes, bit | 320 | 320 | +| | Max data rate, bps | 128000 | 128000 | +| | AMD PDU header, bit | 16 | 16 | +| MAC | MAC header, bit | 4 | 4 | +| | MAC multiplexing | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | DCH | | +| | TB sizes, bit | 340 | | +| | TFS | TF0, bits | 0x340 | +| | | TF1, bits | 1x340 | +| | | TF2, bits | 2x340 | +| | | TF3, bits | 4x340 | +| | | TF4, bits | 8x340 | +| | TTI, ms | 20 | | +| | Coding type | TC | | +| | CRC, bit | 16 | | +| | Max number of bits/TTI after channel coding | 8556 | | +| | Max number of bits/radio frame before rate matching | 4278 | | +| | RM attribute | 120-160 | | + +## 8.1.89.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.89.2.1.3 TFCS + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (128 kbps RAB + 128 kbps RAB, DCCH)=
(TF0,TF0), (TF1,TF0), (TF2,TF0), (TF3,TF0), (TF4,TF0),
(TF0,TF1), (TF1,TF1), (TF2,TF1), (TF3,TF1), (TF4,TF1) | + +## 8.1.89.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|-------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 5 codes x 2 time slots | +| | Max. Number of data bits/radio frame | 2744 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.60 | + +## 8.1.90 Interactive or background / UL:128 DL:32 kbps / PS RAB + Interactive or Background / UL:128 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128kbps, DL: 32kbps. The minimum UE class to support the alternative UL configuration (128-bit payload size) is UL: 128kbps plus support for 'Maximum total number of transport blocks transmitted within TTIs that start at the same time' = 32. + +This is supported in Release '99. + +## 8.1.90.1 Uplink + +See subclause 8.1.89.1 of [1]. + +## 8.1.90.2 Downlink + +## 8.1.90.2.1 Transport channel parameters + +## 8.1.90.2.1.1 Transport channel parameters for Interactive or background / DL:32 + DL:32 kbps / PS RAB + +| Higher layer | RAB/Signalling RB | | RAB | RAB | +|--------------|-----------------------------------------------------|-----------|--------------------------------|-------| +| RLC | Logical channel type | | DTCH | DTCH | +| | RLC mode | | AM | AM | +| | Payload sizes, bit | | 320 | 320 | +| | Max data rate, bps | | 32000 | 32000 | +| | AMD PDU header, bit | | 16 | 16 | +| MAC | MAC header, bit | | 4 | 4 | +| | MAC multiplexing | | 2 logical channel multiplexing | | +| Layer 1 | TrCH type | | DCH | | +| | TB sizes, bit | | 340 | | +| | TFS | TF0, bits | 0x340 | | +| | | TF1, bits | 1x340 | | +| | | TF2, bits | 2x340 | | +| | | TF3, bits | 3x340 | | +| | | TF4, bits | 4x340 | | +| | TTI, ms | | 40 | | +| | Coding type | | TC | | +| | CRC, bit | | 16 | | +| | Max number of bits/TTI after channel coding | | 4284 | | +| | Max number of bits/radio frame before rate matching | | 1071 | | +| | RM attribute | | 135-175 | | + +#### 8.1.90.2.1.2 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +#### 8.1.90.2.1.3 TFCS + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 10 | +| TFCS | (32 kbps RAB + 32 kbps RAB, DCCH)=
(TF0, TF0), (TF1, TF0), (TF2, TF0), (TF3, TF0), (TF4, TF0)
(TF0, TF1), (TF1, TF1), (TF2, TF1), (TF3, TF1), (TF4, TF1) | + +#### 8.1.90.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 812 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.64 | + +### 8.1.91 Streaming / unknown / UL:16 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM entities, DL: 64 kbps. + +This is supported in Release '99. + +#### 8.1.91.1 Uplink + +See subclause 6.10.3.4.1.58.1 of [1]. + +#### 8.1.91.2 Downlink + +See subclause 8.1.82.2 of [1]. + +### 8.1.92 Streaming / unknown / UL:16 DL:32 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 5 AM entities, DL: 64 kbps. + +This is supported in Release '99. + +#### 8.1.92.1 Uplink + +See subclause 6.10.3.4.1.58.1 of [1]. + +#### 8.1.92.2 Downlink + +See subclause 8.1.83.2 of [1]. + +### 8.1.93 Interactive or background / UL:16 DL:32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### 8.1.93.1 Uplink + +See subclause 6.10.3.4.1.23b.1 of [1]. + +### 8.1.93.2 Downlink + +See subclause 6.10.3.4.1.23c.2 of [1]. + +### 8.1.94 Interactive or background / UL:16 DL:64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 64 kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### 8.1.94.1 Uplink + +See subclause 6.10.3.4.1.23b.1 of [1]. + +#### 8.1.94.2 Downlink + +See subclause 6.10.3.4.1.25.2 of [1]. + +### 8.1.95 Interactive or background / UL:16 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps, DL: 128 kbps. The minimum UE class to support the alternative UL configuration is UL: 32kbps plus support for 8 TB/TTI. + +This is supported in Release '99. + +#### 8.1.95.1 Uplink + +See subclause 6.10.3.4.1.23b.1 of [1]. + +#### 8.1.95.2 Downlink + +See subclause 6.10.3.4.1.27.2 of [1]. + +### 8.1.96 Conversational / speech / UL:12.2 DL:12.2 kbps + Streaming / unknown / UL:16 DL:128 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 64 kbps plus support for 16 TB/TTI, DL: 128 kbps. + +This is supported in release '99. + +#### 8.1.96.1 Uplink + +##### 8.1.96.1.1 Transport channel parameters + +###### 8.1.96.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.1.1.1 of [1]. + +###### 8.1.96.1.1.2 Transport channel parameters for Streaming / unknown / UL:16 kbps + +See subclause 6.10.3.4.1.58.1.1.1 of [1]. + +###### 8.1.96.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1]. + +###### 8.1.96.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1]. + +## 8.1.96.1.1.5 TFCS + +| | | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 (alt. 36) | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1)
(alt (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF0,TF2,TF0), (TF2,TF1,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF1,TF2,TF0), (TF1,TF0,TF0,TF1,TF2,TF0), (TF2,TF1,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF0,TF2,TF1), (TF2,TF1,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF1,TF2,TF1), (TF1,TF0,TF0,TF1,TF2,TF1), (TF2,TF1,TF1,TF1,TF2,TF1)) | + +## 8.1.96.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|-------------------------------------------------------------| +| DPCH Uplink | Midamble | 256 chips | +| | Codes and time slots | SF4 x 1 code x 1 time slot +
SF16 x 1 code x 1 time slot | +| | Max. Number of data bits/radio frame | 1308 bits (alt. 1244 bits) | +| | TFCI code word | 16 bits (alt. 32 bits) | +| | TPC | 2 bits | +| | Puncturing Limit | 0.88 (alt. 0.84)) | + +## 8.1.96.2 Downlink + +## 8.1.96.2.1 Transport channel parameters + +## 8.1.96.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.2.1.1 of [1] + +## 8.1.96.2.1.2 Transport channel parameters for Streaming / unknown / DL:128 kbps / PS RAB + +See subclause 8.1.75.2.1.1 of [1]. + +## 8.1.96.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.1 of [1]. + +## 8.1.96.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +## 8.1.96.2.1.5 TFCS + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1) | + +## 8.1.96.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|-------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 6 codes x 2 time slots | +| | Max. Number of data bits/radio frame | 3280 bits | +| | TFCI code word | 32 bits | +| | Puncturing limit | 0,64 | + +## 8.1.97 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / unknown / UL:128 DL:16 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +The minimum UE classes supporting this combination are UL: 128 kbps plus support for 16 TB/TTI, DL: 64 kbps. + +This is supported in release '99. + +## 8.1.97.1 Uplink + +## 8.1.97.1.1 Transport channel parameters + +## 8.1.97.1.1.1 Transport channel parameters for Conversational / speech / UL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.1.1.1 of [1] + +## 8.1.97.1.1.2 Transport channel parameters for Streaming / unknown / UL:128 kbps / PS RAB + +| Higher Layer | RAB/Signalling RB | | RAB | +|--------------|-----------------------------------------------------|-----------|---------| +| RLC | Logical channel type | | DTCH | +| | RLC mode | | AM | +| | Payload sizes, bit | | 640 | +| | Max data rate, bps | | 128000 | +| | AM PDU header, bit | | 16 | +| MAC | MAC header, bit | | 0 | +| | MAC multiplexing | | N/A | +| Layer 1 | TrCH type | | DCH | +| | TB sizes, bit | | 656 | +| | TFS | TF0, bits | 0x656 | +| | | TF1, bits | 1x656 | +| | | TF2, bits | 2x656 | +| | | TF3, bits | 4x656 | +| | TTI, ms | | 20 | +| | Coding type | | TC | +| | CRC, bit | | 16 | +| | Max number of bits/TTI after channel coding | | 8076 | +| | Max number of bits/radio frame before rate matching | | 4038 | +| | RM attribute | | 125-165 | + +## 8.1.97.1.1.3 Transport channel parameters for Interactive or background / UL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23a.1.1.1 of [1]. + +## 8.1.97.1.1.4 Transport channel parameters for UL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.1.1.1 of [1]. + +## 8.1.97.1.1.5 TFCS + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 48 (alt. 72) | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 128 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(alt. (TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF2,TF0,TF0), (TF1,TF0,TF0,TF2,TF0,TF0), (TF2,TF1,TF1,TF2,TF0,TF0),
(TF0,TF0,TF0,TF3,TF0,TF0), (TF1,TF0,TF0,TF3,TF0,TF0), (TF2,TF1,TF1,TF3,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF2,TF1,TF0), (TF1,TF0,TF0,TF2,TF1,TF0), (TF2,TF1,TF1,TF2,TF1,TF0),
(TF0,TF0,TF0,TF3,TF1,TF0), (TF1,TF0,TF0,TF3,TF1,TF0), (TF2,TF1,TF1,TF3,TF1,TF0),
(TF0,TF0,TF0,TF0,TF2,TF0), (TF1,TF0,TF0,TF0,TF2,TF0), (TF2,TF1,TF1,TF0,TF2,TF0),
(TF0,TF0,TF0,TF1,TF2,TF0), (TF1,TF0,TF0,TF1,TF2,TF0), (TF2,TF1,TF1,TF1,TF2,TF0),
(TF0,TF0,TF0,TF2,TF2,TF0), (TF1,TF0,TF0,TF2,TF2,TF0), (TF2,TF1,TF1,TF2,TF2,TF0),
(TF0,TF0,TF0,TF3,TF2,TF0), (TF1,TF0,TF0,TF3,TF2,TF0), (TF2,TF1,TF1,TF3,TF2,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF2,TF0,TF1), (TF1,TF0,TF0,TF2,TF0,TF1), (TF2,TF1,TF1,TF2,TF0,TF1),
(TF0,TF0,TF0,TF3,TF0,TF1), (TF1,TF0,TF0,TF3,TF0,TF1), (TF2,TF1,TF1,TF3,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1),
(TF0,TF0,TF0,TF2,TF1,TF1), (TF1,TF0,TF0,TF2,TF1,TF1), (TF2,TF1,TF1,TF2,TF1,TF1),
(TF0,TF0,TF0,TF3,TF1,TF1), (TF1,TF0,TF0,TF3,TF1,TF1), (TF2,TF1,TF1,TF3,TF1,TF1),
(TF0,TF0,TF0,TF0,TF2,TF1), (TF1,TF0,TF0,TF0,TF2,TF1), (TF2,TF1,TF1,TF0,TF2,TF1),
(TF0,TF0,TF0,TF1,TF2,TF1), (TF1,TF0,TF0,TF1,TF2,TF1), (TF2,TF1,TF1,TF1,TF2,TF1),
(TF0,TF0,TF0,TF2,TF2,TF1), (TF1,TF0,TF0,TF2,TF2,TF1), (TF2,TF1,TF1,TF2,TF2,TF1),
(TF0,TF0,TF0,TF3,TF2,TF1), (TF1,TF0,TF0,TF3,TF2,TF1), (TF2,TF1,TF1,TF3,TF2,TF1)) | + +## 8.1.97.1.2 Physical channel parameters + +| | | | +|-------------|--------------------------------------|-----------------------------------------------------------| +| DPCH Uplink | Midamble | 256 chips | +| | Codes and time slots | {SF2 x 1 code x 1 timeslot} + {SF4 x 1 code x 1 timeslot} | +| | Max. Number of data bits/radio frame | 3040 bits | +| | TFCl code word | 32 bits | +| | TPC | 2 | +| | Puncturing limit | 0.60 | + +## 8.1.97.2 Downlink + +## 8.1.97.2.1 Transport channel parameters + +## 8.1.97.2.1.1 Transport channel parameters for Conversational / speech / DL:12.2 kbps / CS RAB + +See subclause 6.10.3.4.1.4.2.1.1 of [1]. + +## 8.1.97.2.1.2 Transport channel parameters for Streaming / unknown / DL:16 kbps / PS RAB + +See subclause 8.1.82.2.1.1 of [1]. + +#### 8.1.97.2.1.3 Transport channel parameters for Interactive or background / DL:8 kbps / PS RAB + +See subclause 6.10.3.4.1.23.2.1.1 of [1]. + +#### 8.1.97.2.1.4 Transport channel parameters for DL:3.4 kbps SRBs for DCCH + +See subclause 6.10.3.4.1.2.2.1.1 of [1]. + +#### 8.1.97.2.1.5 TFCS + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFCS size | 24 | +| TFCS | (RAB subflow#1, RAB subflow#2, RAB subflow#3, 16 kbps RAB, 8 kbps RAB, DCCH)=
(TF0,TF0,TF0,TF0,TF0,TF0), (TF1,TF0,TF0,TF0,TF0,TF0), (TF2,TF1,TF1,TF0,TF0,TF0),
(TF0,TF0,TF0,TF1,TF0,TF0), (TF1,TF0,TF0,TF1,TF0,TF0), (TF2,TF1,TF1,TF1,TF0,TF0),
(TF0,TF0,TF0,TF0,TF1,TF0), (TF1,TF0,TF0,TF0,TF1,TF0), (TF2,TF1,TF1,TF0,TF1,TF0),
(TF0,TF0,TF0,TF1,TF1,TF0), (TF1,TF0,TF0,TF1,TF1,TF0), (TF2,TF1,TF1,TF1,TF1,TF0),
(TF0,TF0,TF0,TF0,TF0,TF1), (TF1,TF0,TF0,TF0,TF0,TF1), (TF2,TF1,TF1,TF0,TF0,TF1),
(TF0,TF0,TF0,TF1,TF0,TF1), (TF1,TF0,TF0,TF1,TF0,TF1), (TF2,TF1,TF1,TF1,TF0,TF1),
(TF0,TF0,TF0,TF0,TF1,TF1), (TF1,TF0,TF0,TF0,TF1,TF1), (TF2,TF1,TF1,TF0,TF1,TF1),
(TF0,TF0,TF0,TF1,TF1,TF1), (TF1,TF0,TF0,TF1,TF1,TF1), (TF2,TF1,TF1,TF1,TF1,TF1) | + +#### 8.1.97.2.2 Physical channel parameters + +| | | | +|---------------|--------------------------------------|------------------------------| +| DPCH Downlink | Midamble | 256 chips | +| | Codes and time slots | SF16 x 3 codes x 1 time slot | +| | Max. Number of data bits/radio frame | 812 bits | +| | TFCI code word | 16 bits | +| | Puncturing limit | 0.52 | + +## 8.2 Combinations on PDSCH, SCCH, PUSCH and PRACH + +### 8.2.1 Interactive or background / UL:64 DL:256 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH + +See subclause 6.10.3.4.2.1 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps , DL: 384kbps. + +This is supported in Release '99. + +### 8.2.2 Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH + +See subclause 6.10.3.4.2.2 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL: 768kbps. + +This is supported in Release '99. + +### 8.2.3 Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:16.8 DL:33.6 kbps SRBs for DCCH, CCCH and BCCH + UL:16.8 DL:16 kbps SRBs for SHCCH + +See subclause 6.10.3.4.2.3 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 2048kbps The minimum UE class to support the alternative DL configuration is DL: 2048kbps plus support maximum TB bits 81920, and TB TC bits 81920. + +This is supported in Release '99. + +#### **8.2.4 Interactive or background / UL: 384 DL: 2048 kbps / PS RAB + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH** + +See subclause 6.10.3.4.2.4 of [1]. + +The minimum UE classes supporting this combination are UL: 384kbps plus support of SF1, DL: 2048kbps. The minimum UE class to support the alternative DL configuration is DL: 2048kbps plus support maximum TB bits 81920, and TB TC bits 81920. The minimum UE class to support the alternative UL configuration is UL: 384kbps plus support for 64 TB/TTI and support of SF1. + +This is supported in Release '99. + +### **8.3 Combinations on PDSCH, SCCPCH, DPCH, PUSCH and PRACH** + +#### **8.3.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + interactive or background / UL:64 DL:256 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH** + +See subclause 6.10.3.4.3.1 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL: 768kps. + +NOTE: It is assumed that the DPCH DL, PDSCH and SCCPCH use different TS. + +This is supported in Release '99. + +#### **8.3.2 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH** + +See subclause 6.10.3.4.3.2 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384kbps. The minimum UE class to support the alternative DL configuration is DL: 768kps. + +NOTE: It is assumed that the DPCH DL, PDSCH and SCCPCH use different TS. + +This is supported in Release '99. + +#### **8.3.3 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + Interactive or background / UL:64 DL:2048 kbps / PS RAB + UL:16.8 kbps SRBs for CCCH and SHCCH + DL:33.6 kbps SRBs for CCCH, SHCCH and BCCH** + +See subclause 6.10.3.4.3.3 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 2048kbps plus support for maximum TB bits 81920, maximum TC TB bits 81920. + +This is supported in Release '99. + +## 8.4 Combinations on SCCPCH + +### 8.4.1 Stand – alone signalling RB for PCCH + +See subclause 6.10.3.4.4.1 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. This is supported in Release '99 + +### 8.4.2 Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.3.4.4.2 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 8.4.3 Interactive / Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.3.4.4.3 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 8.4.4 Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.3.4.4.2a of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 8.4.5 SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.3.4.4.2b of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 8.4.6 SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.10.3.4.4.3a of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +### 8.4.7 RB for CTCH + SRB for CCCH + SRB for BCCH + +See subclause 6.10.3.4.4.4 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release '99. + +## 8.5 Combinations on PRACH + +### 8.5.1 SRB for CCCH + SRB for DCCH + +See subclause 6.10.3.4.5.1 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps. This is supported by Release '99. + +### 8.5.2 Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.3.4.5.2 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps. This is supported by Release '99. + +### 8.5.3 Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH + +See subclause 6.10.3.4.5.3 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps. This is supported by Release '99. + +--- + +## 9 Examples of Radio Bearers and Signalling Radio Bearers for 1.28 Mcps TDD + +### 9.1 Combinations on DPCH + +#### 9.1.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.1 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.1a Stand-alone UL: 1.7 DL: 1.7 kbps SRBs for DCCH (multiframe) + +See subclause 6.11.5.4.1.1a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.2 Stand-alone UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.2 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.3 Stand-aloneUL: 13.6 DL: 13.6 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.3 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.4 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.4 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.4a Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2 kbps, 7.95, 5.9, 4.75) / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.4a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.5 Conversational / speech / UL: 10.2 DL: 10.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.5 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.5a Conversational / speech / UL: (10.2, 6.7, 5.9, 4.75) DL: (10.2, 6.7, 5.9, 4.75) kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.5a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.6 Conversational / speech / UL: 7.95 DL: 7.95 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.6 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.7 Conversational / speech / UL: 7.4 DL: 7.4 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.7 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### 9.1.7a Conversational / speech / UL: (7.4, 6.7, 5.9, 4.75) DL: (7.4, 6.7, 5.9, 4.75) kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.7a of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.8 Conversational / speech / UL: 6.7 DL: 6.7 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.8 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.9 Conversational / speech / UL: 5.9 DL: 5.9 kbps / CS rab + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.9 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.10 Conversational / speech / UL: 5.15 DL: 5.15 kbps / CS RAB + UL: 1.7 DL: 1.7 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.10 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.11 Conversational / speech / UL: 4.75 DL: 4.75 kbps / CS RAB + UL: 1.7 DL: 1.7 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.11 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.12 Conversational / unknown / UL: 28.8 DL: 28.8 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.12 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +#### **9.1.13 Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.13 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps, DL: 64kbps. + +This is supported in Release 4. + +#### **9.1.14 Conversational / unknown / UL: 32 DL: 32 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.14 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +### **9.1.15 Streaming / unknown / UL: 14.4 DL: 14.4 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.15 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps, DL: 32kbps. + +This is supported in Release 4. + +### **9.1.16 Streaming / unknown / UL: 28.8 DL: 28.8 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.16 of [1]. + +The minimum UE classes supporting this combination are UL: 32kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.17 Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.17 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.18 Void** + +Void + +### **9.1.19 Void** + +Void + +### **9.1.20 Void** + +Void. + +### **9.1.21 Void** + +Void. + +### **9.1.22 Void** + +Void. + +### **9.1.23 Interactive or background / UL: 32 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.23 of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.23a Interactive or background / UL: 8DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.23a of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.23b Interactive or background / UL: 16 DL: 16 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.23b of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.23c Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.23c of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.23d Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH (20 ms TTI)** + +See subclause 6.11.5.4.1.23d of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.24 Void** + +Void. + +### **9.1.25 Interactive or background / UL: 32 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.25 of [1]. + +The minimum UE classes supporting this combination are UL: 32 kbps; DL: 64 kbps. + +This is supported in Release 4. + +### **9.1.26 Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.26 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 64 kbps. + +This is supported in Release 4. + +### **9.1.27 Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.27 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 128kbps. + +This is supported in Release 4. + +### **9.1.28 Interactive or background / UL: 128 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.28 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbps; DL: 128kbps. + +This is supported in Release 4. + +### **9.1.29 Interactive or background / UL: 64 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.29 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 128kbps. + +This is supported in Release 4. + +### **9.1.30 Interactive or background / UL: 144 DL: 144 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.30 of [1]. + +The minimum UE classes supporting this combination are UL: 128 kbps; DL: 128kbps. + +This is supported in Release 4. + +### **9.1.31 Interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.31 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384 kbps. + +This is supported in Release 4. + +### **9.1.32 Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.32 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 384 kbps. + +This is supported in Release 4. + +### **9.1.33 Interactive or background / UL: 128 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.33 of [1]. + +The minimum UE classes supporting this combination are UL: 128 kbps; DL: 384 kbps. + +This is supported in Release 4. + +### **9.1.34 Interactive or background / UL: 384 DL: 384 kbps / PS RAB +UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.34 of [1]. + +The minimum UE classes supporting this combination are UL: 384 kbps; DL: 384kbps. + +This is supported in Release 4. + +### **9.1.35 Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.35 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 2048kbps. + +This is supported in Release 4. + +### **9.1.36 Void** + +Void. + +### **9.1.37 Void** + +Void. + +### **9.1.38 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.38 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32kbps. + +This is supported in Release 4. + +### **9.1.38a Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 0 DL: 0 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.38a of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32kbps + +This is supported in Release 4. + +### **9.1.38b Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.38b of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps + +This is supported in Release 4. + +### **9.1.38c Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.38c of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps + +This is supported in Release 4. + +**9.1.38d** Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38d of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps + +This is supported in Release 4. + +**9.1.38e** Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 0 DL: 0 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38e of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps + +This is supported in Release 4. + +**9.1.38f** Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38f of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps + +This is supported in Release 4. + +**9.1.38g** Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 16 DL: 16 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38g of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps + +This is supported in Release 4. + +**9.1.38h** Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 32 DL: 32 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38h of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 32 kbps + +This is supported in Release 4. + +**9.1.38i** Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.38i of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps + +This is supported in Release 4. + +**9.1.38j Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.38j of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 128 kbps + +This is supported in Release 4. + +**9.1.39 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 32 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.39 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64kbps. + +This is supported in Release 4. + +**9.1.40 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.40 of [1]. + +The minimum UE classes supporting this combination are UL: 64kbps; DL: 64 kbps. + +This is supported in Release 4. + +**9.1.41 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.41 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 128 kbps. + +This is supported in Release 4. + +**9.1.42 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.42 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 384 kbps.. + +This is supported in Release 4. + +**9.1.43 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.43 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 384 kbps. + +This is supported in Release 4. + +#### **9.1.44 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Interactive or background / UL: 128 DL: 2048 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.44 of [1]. + +The minimum UE classes supporting this combination are UL: 384 kbps; DL: 2048 kbps. + +This is supported in Release 4. + +#### **9.1.45 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Streaming / unknown / UL: 57.6 DL: 57.6 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.45 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps. + +This is supported in Release 4. + +#### **9.1.46 Void** + +Void. + +#### **9.1.47 Void** + +Void. + +#### **9.1.48 Void** + +Void. + +#### **9.1.49 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.49 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 64 kbps. + +This is supported in Release 4. + +#### **9.1.49a Conversational / speech / UL: (12.2, 7.95, 5.9, 4.75) DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.49 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps ; DL: 64 kbps. + +This is supported in Release 4. + +#### **9.1.50 Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.50 of [1]. + +The minimum UE classes supporting this combination are UL: 64 kbps; DL: 128 kbps. + +This is supported in Release 4. + +#### **9.1.51 Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.51 of [1]. + +The minimum UE classes for this combinations are UL: 64 kbps; DL: 128 kbps. + +This is supported in Release 4. + +#### **9.1.51a Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.51a of [1]. + +The minimum UE classes for this combinations are UL: 64 kbps ; DL: 64 kbps. + +This is supported in Release 4. + +#### **9.1.51b Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 16 DL: 64 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.51b of [1]. + +The minimum UE classes for this combinations are UL: 64 kbps ; DL: 128 kbps. + +This is supported in Release 4. + +#### **9.1.52 Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 64 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.52 of [1]. + +The minimum UE classes for this combination are UL: 64 kbps; DL: 384 kbps. + +This is supported in Release 4. + +#### **9.1.53 Conversational / unknown / UL: 64 DL: 64 kbps / CS RAB + Interactive or background / UL: 128 DL: 128 kbps / PS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH** + +See subclause 6.11.5.4.1.53 of [1]. + +The minimum UE classes for this combination are UL: 384 kbps; DL: 384 kbps. + +This is supported in Release 4. + +#### **9.1.54 Void** + +Void. + +### 9.1.55 Void + +Void. + +### 9.1.56 Interactive or background / UL: 8 DL: 8 kbps / PS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.56 of [1]. + +The minimum UE classes for this combination are UL: 32 kbps, DL: 32 kbps. + +This is supported in Release 4. + +### 9.1.57 Interactive or background / UL: 64 DL: 64 kbps / PS RAB + Interactive or background / UL: 64 DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.57 of [1]. + +The minimum UE classes for this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 4. + +### 9.1.58 Streaming / Unknown / UL: 16 DL: 64 kbps / PS RAB + Interactive or background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.58 of [1]. + +The minimum UE classes for this combination are UL: 64 kbps, DL: 64 kbps. + +This is supported in Release 4. + +### 9.1.59 Reserved for future use + +### 9.1.60 Reserved for future use + +### 9.1.61 Conversational / unknown / UL:8 DL:8 kbps / PS RAB + Interactive or Background / UL:8 DL:8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + +See subclause 6.11.5.4.1.561 of [1]. + +The minimum UE classes for this combination are UL: 32 kbps, DL: 32 kbps. + +This is supported in Release 4. + +## 9.2 Combinations on PDSCH, SCCH, PUSCH and PRACH + +### 9.2.1 Interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH + +See subclause 6.11.5.4.2.1 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs; DL: 384kbs. + +This is supported in Release 4. + +9.2.2 Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH + +See subclause 6.11.5.4.2.2 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs, DL: 384kbs. + +This is supported in Release 4. + +9.2.3 Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + UL: 16.8 DL: 33.6 kbps SRBs for DCCH, CCCH and BCCH + UL: 16.8 DL: 16 kbps SRBs for SHCCH + +See subclause 6.11.5.4.2.3 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs, DL: 2Mbps. + +This is supported in Release 4. + +## 9.3 Combinations on PDSCH, SCCPCH, DPCH, PUSCH and PRACH + +9.3.1 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + interactive or background / UL: 64 DL: 256 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH + +See subclause 6.11.5.4.3.1 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs; DL: 384kbs. + +This is supported in Release 4. + +9.3.2 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + Interactive or background / UL: 64 DL: 384 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH + +See subclause 6.11.5.4.3.2 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs; DL: 384kbs. + +This is supported in Release 4. + +9.3.3 Conversational / speech / UL: 12.2 DL: 12.2 kbps / CS RAB + UL: 3.4 DL: 3.4 kbps SRBs for DCCH + Interactive or background / UL: 64 DL: 2048 kbps / PS RAB + UL: 16.8 kbps SRBs for CCCH and SHCCH + DL: 33.6 kbps SRBs for CCCH, SHCCH and BCCH + +See subclause 6.11.5.4.3.3 of [1]. + +The minimum UE classes supporting this combination are UL: 128kbs; DL: 2048kbs. + +This is supported in Release 4. + +## 9.4 Combinations on SCCPCH + +### 9.4.1 Stand – alone signalling RB for PCCH + +See subclause 6.11.5.4.4.1 of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release 4. + +### 9.4.2 Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.11.5.4.4.2 of [1]. + +The minimum UE class supporting this combination is DL: 64 kbps. + +This is supported in Release 4. + +### 9.4.2a Interactive / Background 32 kbps PS RAB + Interactive / Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.11.5.4.4.2a of [1]. + +The minimum UE class supporting this combination is DL: 64 kbps. + +This is supported in Release 4. + +### 9.4.2b SRBs for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.11.5.4.4.2b of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release 4. + +### 9.4.3 Interactive / Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.11.5.4.4.3 of [1]. + +The minimum UE class supporting this combination is DL: 64 kbps.. + +This is supported in Release 4. + +### 9.4.3a SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + +See subclause 6.11.5.4.4.3a of [1]. + +The minimum UE class supporting this combination is DL: 32 kbps. + +This is supported in Release 4. + +### 9.4.4 RB for CTCH + SRB for CCCH + SRB for BCCH + +See subclause 6.11.5.4.4.4 of [1]. + +The minimum UE class supporting this combination is DL: 64 kbps.. + +This is supported in Release 4. + +## 9.5 Combinations on PRACH + +### 9.5.1 SRB for CCCH + SRB for DCCH + +See subclause 6.11.5.4.5.1 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps. + +This is supported in Release 4. + +### 9.5.2 Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRBs for DCCH + +See subclause 6.11.5.4.5.2 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps.. + +This is supported in Release 4. + +### 9.5.3 Interactive/Background 12.8 kbps PS RAB + Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRBs for DCCH + +See subclause 6.11.5.4.5.3 of [1]. + +The minimum UE class supporting this combination is UL: 32 kbps. + +This is supported in Release 4. + +## 9.6 Radio Bearer and Radio Bearer Combinations on DPCH and HS-PDSCH + +In the following tables for the references to [1], the details of the configuration are defined there. + +### 9.6.1 Interactive or background / UL:8 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.1.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.11.5.4.1.23a.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +#### 9.6.1.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|--|----------------------|--------------------------|---------------------------------|-------------------------------------| +| | | | | | + +| | | | | | +|-------------------|---------------------------|---------------------------|---------------------------|--| +| Transport Channel | | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.11.5.4.6.1.2.2.2 of [1] | 6.11.5.4.1.2.2.2 of [1] | | + +9.6.1a Interactive or background / UL:8 (multiframe) DL: [max bit rate depending on UE category] / PS RAB+ UL:3.4 DL:3.4 kbps SRBs for DCCH (multiframe) (REL-5) + +#### 9.6.1a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-----------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.11.5.4.6.1a.1.1.1 of [1] | | 6.11.5.4.1.2a.1.1.1 of [1] | | +| TFCS | 6.10.3.4.1.23d.1.1.3 of [1] | | | | +| Physical Channel | 6.11.5.4.6.1a.1.2 of [1] | | 6.11.5.4.6.1a.1.2 of [1] | | + +#### 9.6.1a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.3.4.1.2a.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.11.5.4.6.1.2.2.2 of [1] | 6.11.5.4.1.2a.2.2 of [1] | | + +9.6.2 Interactive or background / UL:16 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.2.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.1.23b.1 of [1] | | | | +| Physical Channel | | | | | + +## 9.6.2.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.11.5.4.6.1.2.2.2 of [1] | 6.11.5.4.1.2.2.2 of [1] | | + +9.6.2a Interactive or background / UL:16(multiframe) DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH(multiframe) (REL-5) + +## 9.6.2a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.11.5.4.6.2a.1.1.1 of [1] | | 6.11.5.4.1.2a.1.1.1 of [1] | | +| TFCS | 6.10.3.4.1.26.1.1.3 of [1] | | | | +| Physical Channel | 6.11.5.4.6.2a.1.2 of [1] | | 6.11.5.4.6.2a.1.2 of [1] | | + +## 9.6.3a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|------------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.11.5.4.6.2a.2 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +9.6.3 Interactive or background / UL:32 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +## 9.6.3.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|--|----------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +|--|----------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| + +| | | +|-------------------|-------------------------| +| Transport Channel | 6.11.5.4.1.23d.1 of [1] | +| TFCS | | +| Physical Channel | | + +### 9.6.3.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.2.2.1.2 of [1] | | | | +| Physical Channel | | 6.11.5.4.6.1.2.2.2 of [1] | 6.11.5.4.1.2.2.2 of [1] | | + +9.6.3a Interactive or background / UL:32(multiframe) DL: [max bit rate depending on UE category] / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH(multiframe) (REL-5) + +### 9.6.3a.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|----------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.11.5.4.6.3a.1.1.1 of [1] | | 6.11.5.4.1.2a.1.1.1 of [1] | | +| TFCS | 6.10.3.4.1.28.1.1.3 of [1] | | | | +| Physical Channel | 6.11.5.4.6.3a.1.2 of [1] | | 6.11.5.4.6.3a.1.2 of [1] | | + +### 9.6.3a.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|------------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.11.5.4.6.2a.2 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +### 9.6.4 Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.4.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.1.26.1 of [1] | | | | +| Physical Channel | | | | | + +#### 9.6.4.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.6.2.2 of [1] | | | | +| Physical Channel | | | | | + +### 9.6.5 Interactive or background / UL:128 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.5.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH ) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH ) | +|-------------------|------------------------|----------------------------------------------|---------------------------------|---------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.1.28.1 of [1] | | | | +| Physical Channel | | | | | + +#### 9.6.5.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | | | | | + +| | | +|------------------|-----------------------| +| TFCS | 6.11.5.4.6.2.2 of [1] | +| Physical Channel | | + +9.6.6 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:32 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.6.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|-------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.1.38c.1 of [1] | | | | +| Physical Channel | | | | | + +#### 9.6.6.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|---------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.2.4.1.4.2.1.1 of [1] | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.2.4.1.4.2.1.3 of [1] | | | | +| Physical Channel | 6.10.2.4.1.4.2.2 of [1] | 6.11.5.4.6.1.2.2.2 of [1] | 6.10.2.4.1.4.2.2 of [1] | | + +9.6.7 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +#### 9.6.7.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | | | | | +| TFCS | 6.11.5.4.1.40.1 of [1] | | | | +| Physical Channel | | | | | + +## 9.6.7.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|-----------------------|--------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.11.5.4.6.5.2 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +9.6.8 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Interactive or background / UL:64 DL:[Bit rate depending on the UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (REL-5) + +## 9.6.8.1 Uplink + +| | Radio Bearer on DPCH | (reserved for Radio Bearer on E-DCH) | Signalling Radio Bearer on DPCH | (reserved for Signalling Radio Bearer on E-DCH) | +|-------------------|------------------------|---------------------------------------------|---------------------------------|--------------------------------------------------------| +| Transport Channel | 6.11.5.4.1.51.1 of [1] | | | | +| TFCS | | | | | +| Physical Channel | | | | | + +## 9.6.8.2 Downlink + +| | Radio Bearer on DPCH | Radio Bearer on HS-PDSCH | Signalling Radio Bearer on DPCH | Signalling Radio Bearer on HS-PDSCH | +|-------------------|----------------------------|---------------------------|---------------------------------|-------------------------------------| +| Transport Channel | 6.10.3.4.1.13.2.1.1 of [1] | 6.11.5.4.6.1.2.1.1 of [1] | 6.10.2.4.1.2.2.1.1 of [1] | | +| TFCS | 6.10.3.4.1.13.2.1.3 of [1] | | | | +| Physical Channel | 6.11.5.4.1.13.2.2 of [1] | 6.11.5.4.6.1.2.2.2 of [1] | 6.11.5.4.1.13.2.2 of [1] | | + +Annex A: +Service scenarios + +This chapter presents a selection of service scenarios, which are used as a basis for the RAB scenarios. Only the basic scenarios having impact on the lower layers are considered. Because the real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail in this document. Other scenarios can be derived as combinations of these basic scenarios. + +Even though these scenarios are for IMS, they are applicable also for non-IMS PS scenarios. The differences between IMS and non-IMS are small in RAN level: Usually, the difference is that in non-IMS cases the IMS signalling stream is left out or replaced by non-IMS signalling stream. Other differences are indicated later in the text, whenever necessary. + +**Table A-1: Service scenarios** + +| | | IMS Signalling | Speech (RTP) | Speech (RTCP) | Audio (RTP) | Audio (RTCP) | Video (RTP) | Video (RTCP) | Text (RTP) | Text (RTCP) | Data | Notes | +|----|---------------------|----------------|--------------|---------------|-------------|--------------|-------------|--------------|------------|-------------|------|-------| +| 1 | Speech | X | X | X | - | - | - | - | - | - | O | | +| 2 | Audio | X | - | - | X | X | - | - | - | - | O | | +| 3 | Video | X | - | - | - | - | X | X | - | - | O | | +| 4 | Text | X | - | - | - | - | - | - | X | X | O | | +| 5 | Speech, Video | X | X | X | - | - | X | X | - | - | O | | +| 6 | Audio, Video | X | - | - | - | - | X | X | X | X | O | | +| 7 | Speech, Text | X | - | - | X | X | X | X | - | - | O | | +| 8 | Video, Text | X | X | X | - | - | - | - | X | X | O | | +| 9 | Speech, Video, Text | X | X | X | - | - | X | X | X | X | O | | +| 10 | Audio, Text | X | - | - | X | X | - | - | X | X | O | | +| 11 | Audio, Video, Text | X | - | - | X | X | X | X | X | X | O | | + +X = stream included in scenario + +- = stream not included in scenario + +O = stream optionally included in scenario + +NOTE: In some 3GPP specifications (e.g., [10]) "audio" and "speech" are not separated, but handled under title "audio". + +In most of the scenarios, the services can be either streaming or conversational. For PS streaming, there is no full IMS support in Release 5. However, this does not have major impact on the items presented in this document. + +The protocol layers of the scenarios are presented in Figure A-1 for conversational and in Figure A-2 for streaming services ([10], [11]). + +![](cf734b5645d3e02a8df25f67904cd2d3_img.jpg) + +| | | | | +|---------------------------------------|-------|------|------| +| Conversational Multimedia Application | | | | +| Audio | Video | Text | RTCP | +| Payload formats | | | | +| RTP | | | | +| UDP | | | | +| IP | | | | + +**Figure A-1 – User plane protocol stack for conversational multimedia terminal** + +The protocol layers for IMS signalling stream, not presented in the figure, are (SDP/)SIP/UDP/IP. + +![](e211ff0e795ca1dbe9216da5d5a6d950_img.jpg) + +| | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Video
Audio
Speech | Capability exchange
Scene description
Presentation description
Still images
Bitmap graphics
Vector graphics
Text
Timed text
Synthetic audio | Capability exchange
Presentation description | +| Payload formats | HTTP | RTSP | +| RTP | | | +| UDP | TCP | UDP | +| IP | | | + +**Figure A-2: Protocol stack for PS streaming terminal** + +## A.1 Common characteristics of scenarios + +The characteristics of the streams in the next sub-chapters are common to all or most of the scenarios. + +In scenarios, where the IP protocol header size or contents are relevant, it is assumed that IPv6 header without extension headers is used, i.e., the IP header size is 40 bytes. The UDP header size is 8 bytes. + +### A.1.1 RTP and RTCP streams + +## A.1.2 Signalling stream + +## A.1.3 Data stream + +The data stream may be used to carry any background or interactive data. Examples on data are still images, graphics, and scene / presentation descriptions, shown in Figure A-2 and [11], as well as web browsing and/or file download. Low delay is not guaranteed, and the data rates may vary between 0 kbps and the maximum bit rate of the context. + +## A.2 Scenarios + +In each of the scenarios, there is also an additional PDP context for SIP or RTSP, and optionally one or more PDP contexts for data. Which PDP contexts are primary or secondary, is not relevant for RAB scenarios. + +### A.2.1 Speech + +For the IMS speech service, the parameters that the transmitter should use (and the receiver shall at least support) are defined more precisely than for any other service in [10]. + +NOTE: Speech is defined under the term "audio" in [10]. + +Both AMR and AMR-WB are included. The parameters for speech are presented below, derived from [10] and [13]: + +**Table A.2.1-1: Conversational IMS speech service parameters** + +| | | Selection or parameter value | | Notes | +|----------------------------------|-----------------------------------------|------------------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| | Nr of AMR / AMR-WB frames in RTP packet | One | | Min. 20 ms packet interval
RTP header adds 12 bytes | +| | AMR / AMR-WB payload mode | Bandwidth efficient | | | +| AMR , lowest and highest modes | | AMR / AMR-WB mode | Payload bytes per frame | Payload bits include AMR data, payload header, table of contents and padding.

Multi-channel session, interleaving or internal CRC not used. | +| | | 4.75 | 14 | | +| | | 12.2 | 32 | | +| AMR-WB, lowest and highest modes | | 6.6 | 18 | Size of SID frame is 7 bytes. | +| | | 23.85 | 61 | | + +For non-IMS services, the above-mentioned restrictions are not applicable. However, it can be assumed that the parameters for conversational VoIP services do not usually deviate significantly from those given above. + +For speech streaming, the codecs are the same as above (AMR and AMR-WB) [11]. In [14], examples on streaming services are presented. The most important difference to the conversational parameters is that the number of speech frames in one RTP packet may be much larger (e.g., 10). On the other hand, the payload mode can be different (octet aligned), CRCs included etc. (as in [14]), which gives larger payload presented in table A.2.1-1. + +## A.2.2 Audio + +"Audio" in this document refers to other than speech-based audio (music, combination of music and speech, etc...). + +In [10] there is no distinction between audio and speech for conversational traffic. The default audio codecs for IMS are AMR and AMR-WB, hence the numbers in chapter A.2.1 are applicable. + +According to [11], MPEG-4 AAC-LC codec should be supported for audio streaming, and in addition, also MPEG-4 AAC-LTP may be supported. As for the speech streaming, the RTP packets contain of several audio frames, as presented in [14]. + +## A.2.3 Video + +The video codecs have a wide range of possible bit rates and packet sizes. For streaming and conversational video, the codecs are H.263 and MPEG 4 (see [11] and [15]). RTP packet size is restricted in IMS conversational video to 512 bytes [10]. + +Examples on video streaming are presented in [14]. There is a wide range of RTP packet rates, depending on various factors, e.g., codec rate or packetization. + +## A.2.4 Text + +According to [16], the data rate of T.140 text telephony over RTP is low: "The rate of character entry is usually at a level of a few characters per second or less. Therefore, the expected number of characters to transmit is low. Only one or a few new characters are expected to be transmitted with each packet". Hence, large part of the traffic consists of the overhead, i.e., RTP/UDP/IP headers and RTCP/UDP/IP packets. The data rate is mostly less than 1 kbps. Whenever the delay has to be guaranteed, the context cannot be of interactive or background traffic class, but e.g., streaming class has to be used. + +It should be noted that text telephony does not include document viewing or other similar use, but only situations where the text is entered by human users in the both ends. For example, the "Text" service in Figure A-2 does not refer to text telephony. + +## A.2.5 Speech and video + +There are basically two different alternatives, depending on whether audio and video streams are on the same or different PDP contexts. The former case is basically similar to the scenario in the chapter A.2.3. The latter case has different implications on lower layers. For streaming case with speech and video over the same context, there is an example in [14]. + +## A.2.6 Audio and video + +The difference in this scenario to the previous one is that the audio/speech coded may be different. On lower layers, this can be handled as the previous scenario. + +## A.2.7 Video, audio, or speech with text + +The additional text telephony stream adds a low bit rate PDP context. Whenever there is a requirement to synchronize the text with the voice or video stream, the text telephony context delay parameters have to be aligned with those of the others (i.e., the delay requirement may be stricter than for stand-alone text telephony). + +## Annex B: Mapping of service scenarios to Radio Access Bearers + +### B.1 Common requirements + +The bearers in this document shall be based entirely on existing 25-series specifications. That is, no requirement on RABs that is not in line with existing RAN specifications, shall be presented. + +In this chapter, the main principles for selecting the parameters are presented. + +### B.2 Bearer characteristics + +The following table lists general characteristics of the bearers in the scenarios: + +| | Parameter | Typical selection or parameter value | Notes | +|------|--------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP | PDCP header, bits | 8 | 8 bit PDCP header is the default in the scenarios.

(For lossless SRNS relocation support, PDCP header can also contain sequence number of 16 bits.) | +| | Header compression | RFC 3095 (ROHC) | ROHC assumed to compress [RTP]/UDP/IP (and ESP/IP) traffic.

No ROHC context identifier needed: PID field (5 bits) of PDCP header is sufficient to indicate all ROHC contexts in the given scenarios.

The most common header (shortest 2 nd order header) is 3 bytes when UDP checksum is present (with IPv6); see RLC payload sizes.

ROHC feedback packets transmitted in opposite direction, interspersed with main flow packets.

Segmentation of ROHC not in use, because only non-transparent RLC modes in these scenarios. | +| | | RFC 2507 | For TCP/IP compression (even though any IP headers, also those in UDP/IP could be compressed by RFC 2507).

TCP/IP used in interactive and background, therefore no impact on RLC payload sizes | +| RLC | | | | +| | RLC mode | UM or AM | TM not possible because no a priori information on (compressed) IP packets, and no mechanism specified for negotiating ROHC packet sizes parameters.

UM used for conversational traffic class, AM for all other classes. | + +| | | | | +|--|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Payload sizes, bit | |

Number of different payload sizes to be limited so that max size of TFCS is reasonably low.

In some scenarios, one of payload sizes is IP payload with shortest ROHC header.

For AM, default payload size is 320 bits

| +| | Max data rate, kbps | |

The actual data rate on IP layer is somewhat different from this nominal figure, due to:

  • • PDCP header
  • • Length indicator part of RLC header
  • • Retransmissions (in AM)
  • • Header compression
| +| | UMD/AMD PDU header, bit | 8 / 16 | 8 for UM, 16 for AM | + +**Table B.2-1: Common characteristics of L2** + +In the scenarios, the RABs for data stream are not presented. Each of the scenarios may or may not have one or more RABs for data stream. The RABs can be selected from the interactive/background RABs. + +## B.3 RAB Scenarios + +NOTE: The following RAB combinations are only examples of possible implementations of the scenarios. + +Due to flexibility in RAN specifications (and in PDP context parameters) there is a large number of other possible RABs and their combinations that could implement the scenarios. There are also other RAB combinations applicable for other scenarios, not listed below. + +This chapter concentrates on the basic scenarios of chapter A.2.1, thus excluding most of the combinations of multiple sessions. + +## Annex C: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|----------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 09/2002 | RP-17 | RP-020663 | - | | | Creation. | - | +| 12/2002 | RP-18 | RP-020890 | - | | | Merge of RP-020877 with RP-020814. Clause numbering changed.
Approved at TSG RAN#18. | 6.0.0 | +| 03/2003 | RP-19 | RP-030109 | 001 | | | Streaming and interactive/background RAB combinations | 6.1.0 | +| | RP-19 | RP-030109 | 002 | | | QoS attributes for RABs in 25.993 | 6.1.0 | +| | RP-19 | RP-030109 | 003 | | | TDD RABs in 25.993 | 6.1.0 | +| 06/2003 | RP-20 | RP-030288 | 004 | | | Corrections to the UE capabilities and editorial changes | 6.2.0 | +| | RP-20 | RP-030288 | 005 | | | New configuration for CBS: CTCH, PCCH, 32kbps RAB and SRBs on 1 S-CCPCH | 6.2.0 | +| | RP-20 | RP-030288 | 006 | | | New SCCPCH Configurations | 6.2.0 | +| | RP-20 | RP-030288 | 008 | | | PS streaming and CS speech RAB combinations | 6.2.0 | +| | RP-20 | RP-030288 | 009 | | | RB configuration for the support of wideband AMR speech telephony services | 6.2.0 | +| | RP-20 | RP-030288 | 010 | | | Corrections on TDD RABs | 6.2.0 | +| 09/2003 | RP-21 | RP-030497 | 012 | | | IMS RAB scenarios | 6.3.0 | +| | RP-21 | RP-030489 | 013 | | | Addition of Streaming RABs | 6.3.0 | +| 12/2003 | RP-22 | RP-030609 | 014 | | | BTFD with Flexible TrCH position | 6.4.0 | +| | RP-22 | RP-030609 | 015 | | | Addition of Conversational – Interactive/Background RAB combination | 6.4.0 | +| 03/2004 | RP-23 | RP-040100 | 019 | | | Alignment with 34.108 for TDD | 6.5.0 | +| | RP-23 | RP-040100 | 024 | | | S-CCPCH combination for HS-DSCH channel type switching | 6.5.0 | +| | RP-23 | RP-040109 | 025 | | | DCH combination for HS-DSCH channel type switching | 6.5.0 | +| 06/2004 | RP-24 | RP-040205 | 026 | | | Corrections on required capabilities for 32kbps UE class and addition of the 12kbps class | 6.6.0 | +| | RP-24 | RP-040205 | 027 | | | Addition of RAB Parameters For RABs Removed From TS34.108 But Retained In TS25.993 | 6.6.0 | +| 09/2004 | RP-25 | RP-040325 | 028 | | | Physical layer multiplexing configuration in case of AMR and two PS RABs with zero bit rates | 6.7.0 | +| | RP-25 | RP-040325 | 029 | | | Physical layer multiplexing configuration in case of two PS RABs | 6.7.0 | +| | RP-25 | RP-040325 | 030 | | | Correction of RAB configuration in 1.28Mcps TDD | 6.7.0 | +| | RP-25 | RP-040325 | 032 | | | Conversational PS RAB for HS-DSCH | 6.7.0 | +| 12/2004 | RP-26 | RP-040483 | 031 | 3 | | Addition of HSDPA RABs | 6.8.0 | +| | RP-26 | RP-040475 | 033 | | | Addition RAB combinations for UL>DL PS rates | 6.8.0 | +| | RP-26 | RP-040475 | 034 | | | Radio bearer combination for PS streaming in section 7.1.74 | 6.8.0 | +| | RP-26 | RP-040475 | 035 | 1 | | Correct TFCS used in 128DL RAB | 6.8.0 | +| 03/2005 | RP-27 | RP-050064 | 036 | | | Addition of asymmetric RAB-combinations with voice | 6.9.0 | +| | RP-27 | RP-050071 | 037 | | | AMR-WB reference RAB configurations | 6.9.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|------------------------------------------------------------------------------------|--------| +| 06/2005 | RP-28 | RP-050325 | 0038 | | | Introduction of fixed DTX positions for I/B RAB combinations | 6.10.0 | +| | RP-28 | RP-050325 | 0039 | | | Inclusion of HSDPA RABs already defined in 34.108 | 6.10.0 | +| | RP-28 | RP-050321 | 0040 | | | CCCH message enhancements | 6.10.0 | +| | RP-28 | RP-050325 | 0041 | | | Introduction of Streaming RABs over HSDPA | 6.10.0 | +| 09/2005 | RP-29 | RP-050455 | 0042 | | | Redefiniton of Radio Access Bearer (RAB) combinations | 6.11.0 | +| | RP-29 | RP-050455 | 0043 | | | Proposed new notation for HSDPA Radio Bearers (RB) | 6.11.0 | +| | RP-29 | RP-050455 | 0044 | | | Combinations of radio bearers on DPCH with WB-AMR and I/B PS | 6.11.0 | +| | RP-29 | RP-050455 | 0045 | | | Inclusion of additional example RAB combinations | 6.11.0 | +| | RP-29 | RP-050455 | 0046 | | | Addition of RAB-combinations with AMR 5.9 voice and AMR 12.2 with two PDP contexts | 6.11.0 | +| | RP-29 | RP-050487 | 0047 | | | Maximum number of bits per TTI for extended CCCH | 6.11.0 | +| | RP-29 | RP-050586 | 0050 | 1 | | Reference RB configuration for AMR utilising 5.9, and 4.75 kbps with SF256 in DL | 6.11.0 | +| 12/2005 | RP-30 | RP-050799 | 0048 | 3 | | Addition of VoIP RAB combinations | 6.12.0 | +| | RP-30 | RP-050799 | 0049 | 3 | | Addition of VoIP RAB combination for multiplexed RTP and RTCP flows | 6.12.0 | +| | RP-30 | RP-050799 | 0051 | 1 | | Addition of multi-rate AMR-NB configuration with SRB#5 | 6.12.0 | +| | RP-30 | RP-050799 | 0052 | 1 | | Introduction of high bit rate SRB | 6.12.0 | +| | RP-30 | RP-050799 | 0053 | 3 | | Addition of multi-rate AMR configuration over HSDPA | 6.12.0 | +| | RP-30 | RP-050799 | 0054 | 1 | | Miscellaneous corrections | 6.12.0 | +| | RP-30 | RP-050799 | 0055 | | | Introduction of conversational mono rate AMR 5.9 kbps RAB with SF 128. | 6.12.0 | +| | RP-30 | RP-050799 | 0057 | | | PL for Conversational / speech (12.65, 8.85, 6.6) kbps + Interactive 0 kbps | 6.12.0 | +| | RP-30 | RP-050799 | 0060 | | | WB-AMR configurations | 6.12.0 | +| | RP-30 | RP-050799 | 0061 | 1 | | Addition of VoIP RAB combinations | 6.12.0 | +| | RP-30 | RP-050799 | 0062 | | | Addition of VoIP RAB combination for multiplexed RTP and RTCP flows | 6.12.0 | +| 03/2006 | RP-31 | RP-060088 | 0056 | 2 | | Reference RAB configurations for MBMS | 6.13.0 | +| | RP-31 | RP-060082 | 0063 | | | Corrections to TR 25.993 | 6.13.0 | +| | RP-31 | RP-060083 | 0064 | | | VT bearer configurations | 6.13.0 | +| | RP-31 | RP-060083 | 0065 | | | Introduction of additional WB-AMR RAB combinations | 6.13.0 | +| | RP-31 | RP-060087 | 0066 | | | Introduction of EUL RB configurations | 6.13.0 | +| | RP-31 | RP-060082 | 0067 | 1 | | Uplink Streaming 128 kbps combinations | 6.13.0 | +| | RP-31 | RP-060087 | 0068 | 1 | | VoIP reference configuration for E-DCH | 6.13.0 | +| | RP-31 | RP-060089 | 0069 | | | Alternative reference RB configurations for MBMS | 6.13.0 | +| 06/2006 | RP-32 | RP-060368 | 0070 | | | Correction of transport block sizes in MBMS reference bearer configurations | 6.14.0 | +| | RP-32 | RP-060367 | 0071 | | | Addition of the combinations on DPCH and HS-PDSCH for LCR TDD | 6.14.0 | +| | RP-32 | RP-060367 | 0073 | | | Correction of internal references | 6.14.0 | +| | RP-32 | RP-060367 | 0074 | | | Reference configuration of AMR (5.9 kbps, 4.75 kbps) and HSDPA and E-DCH | 6.14.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|--------------------------------------------------------------------------------------------------|--------| +| | RP-32 | RP-060367 | 0075 | | | Puncturing limit correction in 7.1.112 | 6.14.0 | +| | RP-32 | RP-060372 | 0076 | | | New configurations with 'flexible TFCS' | 6.14.0 | +| | RP-32 | RP-060371 | 0077 | 1 | | Introduction of high data rate SRB | 6.14.0 | +| 09/2006 | RP-33 | RP-060572 | 0078 | | | Correction to chapter numbering in E-DPDCH and HS-DPSCH RB combinations | 6.15.0 | +| | RP-33 | RP-060572 | 0084 | | | Correction on combinaisons with Streaming / unknown / UL:0 DL:64 kbps / CS RAB | 6.15.0 | +| | RP-33 | - | - | | | Upgrade to the Release 7 - No technical change | 7.0.0 | +| 12/2006 | RP-34 | RP-060721 | 0079 | 3 | | Addition of VoIP RAB combination for multiplexed RTP and RTCP flows when ROHC is in steady state | 7.1.0 | +| | RP-34 | RP-060721 | 0085 | | | Additional I/B RAB combinations | 7.1.0 | +| | RP-34 | RP-060721 | 0086 | | | 7.6 kbps signalling RB for MCCH | 7.1.0 | +| | RP-34 | RP-060721 | 0087 | | | Reference SRB configuration for MCCH | 7.1.0 | +| 03/2007 | RP-35 | RP-070152 | 0088 | 1 | | Correction on RAB combinations for VoIP for TR 25.993 | 7.2.0 | +| | RP-35 | RP-070152 | 0089 | | | Addition of IMS MM Telephony configurations over HSPA | 7.2.0 | +| | RP-35 | RP-070152 | 0090 | | | Correction to TF size in MBMS reference configuration | 7.2.0 | +| | RP-35 | RP-070152 | 0091 | | | UE capability requirement for 7.6 kbps signalling RB for MCCH | 7.2.0 | +| | RP-35 | RP-070152 | 0092 | | | Additional HSPA RAB Combinations | 7.2.0 | +| | RP-35 | RP-070152 | 0093 | | | Additional HSDPA RAB Combinations | 7.2.0 | +| 06/2007 | RP-36 | RP-070396 | 0094 | 1 | | Addition of RAB combinaison for SRB mapped on DL "HSDPA + DCH" | 7.3.0 | +| | RP-36 | RP-070396 | 0095 | | | Additional DCH RAB Combinations | 7.3.0 | +| | RP-36 | RP-070396 | 0096 | | | HSPA RAB Combinations | 7.3.0 | +| | RP-36 | RP-070396 | 0097 | | | Additional HSPA RAB Combinations | 7.3.0 | +| 09/2007 | RP-37 | | | | | | 7.4.0 | +| | | RP-070623 | 0098 | | | HSUPA and HSDPA with SRBs on 13.6 kbps DCH | 7.4.0 | +| | RP-37 | | | | | | 7.4.0 | +| | | RP-070625 | 0099 | | | References to radio bearer for MCCH and MTCH testing | 7.4.0 | +| | RP-37 | | | | | | 7.4.0 | +| | | RP-070624 | 0100 | | | Add references to additional combinations on PRACH adopted in 34.108 | 7.4.0 | +| | RP-37 | | | | | | 7.4.0 | +| | | RP-070624 | 0101 | | | Additional DCH RAB Combination | 7.4.0 | +| | RP-37 | | | | | | 7.4.0 | +| | | RP-070624 | 0102 | | | Very low bit rate WB-AMR configuration | 7.4.0 | +| | RP-37 | | | | | | 7.4.0 | +| | | RP-070624 | 0103 | | | Additional DCH RAB combination | 7.4.0 | +| 12/2007 | RP-38 | RP-070895 | | | | MBMS ptp RAB on HS | 7.5.0 | +| | | | 0104 | | | | | +| | RP-38 | RP-070892 | | | | Removal of incorrect configuration | 7.5.0 | +| | | | 0106 | | | | | +| 03/2008 | RP-39 | RP-080190 | 0107 | 1 | | RB combinations for flexible PDU sizes and MAC-ehs | 7.6.0 | +| | RP-39 | RP-080180 | 0108 | - | | RAB combinations MBMS PTP on DPCH | 7.6.0 | +| 05/2008 | RP-40 | RP-080405 | 0109 | - | | RAB combinations for CS voice over HSPA | 8.0.0 | +| 09/2008 | RP-41 | RP-080687 | 0111 | - | | RAB combinations for CS voice over HSPA | 8.1.0 | +| 12/2008 | RP-42 | RP-081012 | 0112 | 1 | | Update of references to TS 34.108 CS voice over HSPA RAB combinations | 8.2.0 | +| 09/2009 | RP-45 | RP-090916 | 0114 | - | | CS over HSPA RAB combinations adding | 8.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|--------------------------------------------------------|--------| +| 12/2009 | RP-46 | RP-091328 | 0115 | 1 | | Editorial modification to 25.993 | 8.4.0 | +| 12/2009 | RP-46 | - | - | - | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 03/2010 | RP-47 | RP-100294 | 0117 | - | | Rapporteur CR for corrections to 25.993 | 9.1.0 | +| 12/2010 | RP-50 | RP-101213 | 0118 | - | | Adding the 12.2/7.4/5.9/4.75 kbps speech without SRB#5 | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | +| 09/2014 | RP-65 | - | - | - | | Upgrade to the Release 12 - no technical change | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 12/2015 | RP-70 | RP-152059 | 0119 | 1 | | Introduction of EVS CS RABs | 13.0.1 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | | | | | Upgrade to Release 14 - no technical change | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|---------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Upgrade to Release 15 - no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/46_series/46010/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-16/46_series/46010/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09bff03db668c59382201c72ac31f792e397483a --- /dev/null +++ b/marked/Rel-16/46_series/46010/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db52d5b572fbdbd8de801007d4a928da5206f55bcfe9dad7500b687c89890f06 +size 21089 diff --git a/marked/Rel-16/46_series/46010/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/marked/Rel-16/46_series/46010/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4934623d07e0a8487656edabe4d3eacbc9765b8a --- /dev/null +++ b/marked/Rel-16/46_series/46010/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6861fff11a3256c67aba01ad27ce8d9b769e1a71790b28556e4f6c9a0bd1815 +size 33662 diff --git a/marked/Rel-16/46_series/46010/1381593e48739f603c81fa60e6b98a6c_img.jpg b/marked/Rel-16/46_series/46010/1381593e48739f603c81fa60e6b98a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f66005244b48223dfb63e8128fb778c284c59b2 --- /dev/null +++ b/marked/Rel-16/46_series/46010/1381593e48739f603c81fa60e6b98a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:769277d2a1434a8cc78792e028282224ce1410c50a1ab0cfbaae1ffdf0da19fe +size 33010 diff --git a/marked/Rel-16/46_series/46010/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/46_series/46010/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..240e3b13b857e7ac78135089542fcbb639505b5f --- /dev/null +++ b/marked/Rel-16/46_series/46010/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc33454940dcbfdf166fadda82ea3e80cfc3f030c4fdd9966e07605b971e8808 +size 47480 diff --git a/marked/Rel-16/46_series/46010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1ebabb40c336471925887cb63202d3d847cd1d0 --- /dev/null +++ b/marked/Rel-16/46_series/46010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1bf5415c544ade62d0415d00f98cdf921b4fd959401a6d9d82b38d2b7470c2f +size 100009 diff --git a/marked/Rel-16/46_series/46010/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/46_series/46010/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e2ca3c4f0c76d86a0eae14b4283fbcd02a55366 --- /dev/null +++ b/marked/Rel-16/46_series/46010/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29d104bb5906da12916a64584f0953f3dfd8cd18c0c49f220e2f03448205f775 +size 77476 diff --git a/marked/Rel-16/46_series/46010/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/46_series/46010/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4740c5b75dd874e008720c345ef2c7b20438a42c --- /dev/null +++ b/marked/Rel-16/46_series/46010/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f1a94569e2ace724a9d88b59d9fa192d9522c1ccc91626ca471fca8a7585c1 +size 60916 diff --git a/marked/Rel-16/46_series/46010/86692d82da6655813b5acf58a767a38c_img.jpg b/marked/Rel-16/46_series/46010/86692d82da6655813b5acf58a767a38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f38ae2c846331dde91b25ae77d193e6b7e4e5384 --- /dev/null +++ b/marked/Rel-16/46_series/46010/86692d82da6655813b5acf58a767a38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4fbb7f2d661090d3a0bafdfb5fcf7f587696c7c8f02daf1645e5390be0c5ff5 +size 15034 diff --git a/marked/Rel-16/46_series/46010/92271d74f67effbd92583eb3fba71514_img.jpg b/marked/Rel-16/46_series/46010/92271d74f67effbd92583eb3fba71514_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bace281bf52bb466afd3b6dc07c5affa9b91f7bc --- /dev/null +++ b/marked/Rel-16/46_series/46010/92271d74f67effbd92583eb3fba71514_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be65fea899131e979a47378f6cc6fe380e905830902d9fa840e486ff8c8ebebf +size 24234 diff --git a/marked/Rel-16/46_series/46010/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/46_series/46010/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b7291b1edc7bc750182e772033a3e8130db008e --- /dev/null +++ b/marked/Rel-16/46_series/46010/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d846225146f72b850460e34511b483ecccb19c22112c0569ca5abba77577698 +size 32286 diff --git a/marked/Rel-16/46_series/46010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/46_series/46010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9528e05cc977d5830713581f3f533930078bfb27 --- /dev/null +++ b/marked/Rel-16/46_series/46010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3472371dfa6e6e0c1a312b9aadd03dadd16975ee86362a3db7c08c1d09b2952 +size 46913 diff --git a/marked/Rel-16/46_series/46010/b9f1f5c5167e357277b530940312d9ed_img.jpg b/marked/Rel-16/46_series/46010/b9f1f5c5167e357277b530940312d9ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc134020598a97caea3eaf07a5ed5e356abfb183 --- /dev/null +++ b/marked/Rel-16/46_series/46010/b9f1f5c5167e357277b530940312d9ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de1f776f9ab5a280c7e89803832c1a777c218f663d01e34ded1fd320cabc68bd +size 78465 diff --git a/marked/Rel-16/46_series/46010/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/46_series/46010/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d70e3271728a97553707f9f711948a2748fa0f6 --- /dev/null +++ b/marked/Rel-16/46_series/46010/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa41525c6789dcea87f37cdcaafab2474b315ead1ced04d3c2f24fdd229ac113 +size 132861 diff --git a/marked/Rel-16/46_series/46010/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/46_series/46010/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1a0ad3691217992e55e1fdd6ad2ff3e4383e26b --- /dev/null +++ b/marked/Rel-16/46_series/46010/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc3798989233cbb4bd5f41d921a8cad126cfab6713bfed71cac9ac34c012062 +size 112808 diff --git a/marked/Rel-16/46_series/46010/raw.md b/marked/Rel-16/46_series/46010/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9b669ff567da603c8e01e7837c186dc74e5cbfee --- /dev/null +++ b/marked/Rel-16/46_series/46010/raw.md @@ -0,0 +1,2850 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1.1 References..... | 7 | +| 1.1.1 Abbreviations ..... | 8 | +| 1.2 Outline description..... | 8 | +| 1.3 Functional description of audio parts..... | 8 | +| 1.4 PCM Format conversion ..... | 9 | +| 1.5 Principles of the RPE-LTP encoder ..... | 9 | +| 1.6 Principles of the RPE-LTP decoder ..... | 10 | +| 1.7 Sequence and subjective importance of encoded parameters ..... | 10 | +| 2 Transmission characteristics ..... | 13 | +| 2.1 Performance characteristics of the analogue/digital interfaces ..... | 13 | +| 2.2 Transcoder delay ..... | 13 | +| 3 Functional description of the RPE-LTP codec ..... | 13 | +| 3.1 Functional description of the RPE-LTP encoder ..... | 13 | +| 3.1.1 Offset compensation..... | 14 | +| 3.1.2 Pre-emphasis..... | 14 | +| 3.1.3 Segmentation ..... | 14 | +| 3.1.4 Autocorrelation..... | 15 | +| 3.1.5 Schur Recursion..... | 15 | +| 3.1.6 Transformation of reflection coefficients to Log.-Area Ratios ..... | 15 | +| 3.1.7 Quantization and coding of Log.-Area Ratios..... | 15 | +| 3.1.8 Decoding of the quantized Log.-Area Ratios ..... | 16 | +| 3.1.9 Interpolation of Log.-Area Ratios ..... | 16 | +| 3.1.10 Transformation of Log.-Area Ratios into reflection coefficients ..... | 16 | +| 3.1.11 Short term analysis filtering ..... | 16 | +| 3.1.12 Sub-segmentation ..... | 17 | +| 3.1.13 Calculation of the LTP parameters..... | 17 | +| 3.1.14 Coding/Decoding of the LTP lags..... | 17 | +| 3.1.15 Coding/Decoding of the LTP gains..... | 18 | +| 3.1.16 Long term analysis filtering..... | 18 | +| 3.1.17 Long term synthesis filtering..... | 18 | +| 3.1.18 Weighting Filter..... | 19 | +| 3.1.19 Adaptive sample rate decimation by RPE grid selection ..... | 19 | +| 3.1.20 APCM quantization of the selected RPE sequence ..... | 19 | +| 3.1.21 APCM inverse quantization ..... | 20 | +| 3.1.22 RPE grid positioning ..... | 21 | +| 3.2 Decoder ..... | 21 | +| 3.2.1 RPE decoding clause ..... | 21 | +| 3.2.2 Long Term Prediction clause..... | 21 | +| 3.2.3 Short term synthesis filtering clause..... | 21 | +| 3.2.4 Post-processing..... | 21 | +| 4 Codec homing ..... | 25 | +| 4.1 Functional description ..... | 25 | +| 4.2 Definitions..... | 25 | +| 4.3 Encoder homing ..... | 26 | +| 4.4 Decoder homing ..... | 26 | +| 4.5 Encoder home state ..... | 27 | +| 4.6 Decoder home state ..... | 27 | +| 5 Computational details of the RPE-LTP codec ..... | 27 | +| 5.1 Data representation and arithmetic operations..... | 27 | +| 5.2 Fixed point implementation of the RPE-LTP coder..... | 29 | +| 5.2.0 Scaling of the input variable ..... | 30 | +| 5.2.1 Downscaling of the input signal..... | 30 | +| 5.2.2 Offset compensation..... | 30 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------|-----------| +| 5.2.3 | Pre-emphasis..... | 30 | +| 5.2.4 | Autocorrelation..... | 31 | +| 5.2.5 | Computation of the reflection coefficients ..... | 31 | +| 5.2.6 | Transformation of reflection coefficients to Log.-Area Ratios ..... | 32 | +| 5.2.7 | Quantization and coding of the Log.-Area Ratios..... | 33 | +| 5.2.8 | Decoding of the coded Log.-Area Ratios..... | 33 | +| 5.2.9 | Computation of the quantized reflection coefficients..... | 34 | +| 5.2.9.1 | Interpolation of the LARpp[1..8] to get the LARp[1..8] ..... | 34 | +| 5.2.9.2 | Computation of the rp[1..8] from the interpolated LARp[1..8] ..... | 34 | +| 5.2.10 | Short term analysis filtering ..... | 34 | +| 5.2.11 | Calculation of the LTP parameters..... | 35 | +| 5.2.12 | Long term analysis filtering..... | 36 | +| 5.2.13 | Weighting filter ..... | 36 | +| 5.2.14 | RPE grid selection ..... | 37 | +| 5.2.15 | APCM quantization of the selected RPE sequence ..... | 37 | +| 5.2.16 | APCM inverse quantization ..... | 38 | +| 5.2.17 | RPE grid positioning ..... | 39 | +| 5.2.18 | Update of the reconstructed short term residual signal dp[-120..-1] ..... | 39 | +| 5.3 | Fixed point implementation of the RPE-LTP decoder..... | 39 | +| 5.3.1 | RPE decoding clause ..... | 39 | +| 5.3.2 | Long term synthesis filtering..... | 40 | +| 5.3.3 | Computation of the decoded reflection coefficients..... | 40 | +| 5.3.4 | Short term synthesis filtering clause..... | 40 | +| 5.3.5 | De-emphasis filtering ..... | 41 | +| 5.3.6 | Upscaling of the output signal..... | 41 | +| 5.3.7 | Truncation of the output variable ..... | 41 | +| 5.4 | Tables used in the fixed point implementation of the RPE-LTP coder and decoder ..... | 42 | +| 6 | Digital test sequences..... | 43 | +| 6.1 | Input and output signals ..... | 44 | +| 6.2 | Configuration for the application of the test sequences ..... | 44 | +| 6.2.1 | Configuration 1 (encoder only) ..... | 44 | +| 6.2.2 | Configuration 2 (decoder only) ..... | 44 | +| 6.3 | Test sequences..... | 45 | +| 6.3.1 | Test sequences for configuration 1 ..... | 45 | +| 6.3.2 | Test sequences for configuration 2 ..... | 46 | +| 6.3.3 | Additional Test sequences for Codec Homing..... | 50 | +| 6.3.3.1 | Codec homing frames ..... | 50 | +| 6.3.3.2 | Sequence for an extensive test of the decoder homing..... | 50 | +| 6.3.3.3 | Sequences for finding the 20 ms framing of the GSM full rate speech encoder ..... | 50 | +| 6.3.3.4 | Formats and sizes of the synchronization sequences..... | 51 | +| Annex A (informative): | Codec performance ..... | 53 | +| A.1 | Performance of the RPE-LTP ..... | 53 | +| A.1.1 | Introduction ..... | 53 | +| A.1.2 | Speech performance ..... | 53 | +| A.1.2.1 | Single encoding ..... | 53 | +| A.1.2.2 | Speech performance when interconnected with coding systems on an analogue basis ..... | 54 | +| A.1.2.2.1 | Performance with 32 kbit/s ADPCM (G.721, superseded by G.726)..... | 54 | +| A.1.2.2.2 | Performance with another RPE-LTP codec..... | 54 | +| A.1.2.2.3 | Performance with encoding other than RPE-LTP and 32 kbit/s ADPCM (G.721, superseded by G.726) ..... | 54 | +| A.1.3 | Non-speech performance..... | 55 | +| A.1.3.1 | Performance with single sine waves..... | 55 | +| A.1.3.2 | Performance with DTMF tones ..... | 55 | +| A.1.3.3 | Performance with information tones ..... | 55 | +| A.1.3.4 | Performance with voice-band data ..... | 55 | +| A.1.4 | Delay ..... | 55 | +| A.1.5 | Bibliography..... | 57 | + +A.2 Subjective relevance of the speech coder output bits ..... 57 + +A.3 Format for test sequence distribution..... 59 + +A.3.1 Type of files provided ..... 59 + +A.3.2 File format description ..... 60 + +**Annex B (informative): Test sequence disks..... 62** + +Annex C (informative): Change history..... 63 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the full rate speech transcoding within the digital cellular telecommunications system. + +NOTE: The present document is a reproduction of recommendation T/L/03/11 "13 kbit/s Regular Pulse Excitation - Long Term Prediction - Linear Predictive Coder for use in the digital cellular telecommunications system". + +Archive en\_300961v080101p0.ZIP which accompanies the present document, contains test sequences, as described in clause 6 and annex A.3. + +The archive contains the following: + +- | | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Disk1.zip | Annex B: Test sequences for the GSM Full Rate speech codec; Test sequences SEQ01.xxx to SEQ05.xxx. (Disk1.zip contains LHA compressed files.) | +| Disk2.zip | Annex B: Test sequences for the GSM Full Rate speech codec with homing frames; Test sequences SEQ01H.* to SEQ02H.*. | +| Disk3.zip | Annex B: Test sequences for the GSM Full Rate speech codec with homing frames; Test sequences SEQ03H.* to SYNC159.COD. | +| Disk4.zip | Annex B: 8 bit A-law test sequences for the GSM Full Rate speech codec with and without homing frames (Disk4.zip contains self-extracting files). | +| Disk5.zip | Annex B: 8 bit μ-law test sequences for the GSM Full Rate speech codec with and without homing frames (Disk5.zip contains self-extracting files). | + +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 transcoding procedure specified in the present document is applicable for the full-rate Traffic Channel (TCH) in the digital cellular telecommunications system. The use of this transcoding scheme for other applications has not been considered. + +In GSM 06.01, a reference configuration for the speech transmission chain of the digital cellular telecommunications system is shown. According to this reference configuration, the speech encoder takes its input as a 13 bit uniform PCM signal either from the audio part of the mobile station or on the network side, from the PSTN via an 8 bit/A- or $\mu$ -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to a channel encoder unit which is specified in GSM 05.03. In the receive direction, the inverse operations take place. + +The present document describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format to encoded blocks of 260 bits and from encoded blocks of 260 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8000 sample/s leading to an average bit rate for the encoded bit stream of 13 kbit/s. The coding scheme is the so-called Regular Pulse Excitation - Long Term prediction - Linear Predictive Coder, here-after referred to as RPE-LTP. + +The present document also specifies the conversion between A- and $\mu$ -law (PCS 1900) PCM and 13 bit uniform PCM. Performance requirements for the audio input and output parts are included only to the extent that they affect the transcoder performance. The present document also describes the codec down to the bit level, thus enabling the verification of compliance to the present document to a high degree of confidence by use of a set of digital test sequences. These test sequences are described and are contained in archive en\_300961v080101p0.ZIP which accompanies the present document. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [3] GSM 06.01: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Processing functions". +- [4] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformity specification". +- [5] Void. +- [6] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". +- [7] ITU-T Recommendation G.712: "Transmission performance characteristics of pulse code modulation". +- [8] ITU-T Recommendation G.726: "40, 32, 24, 16 kbit/s adaptive differential pulse code modulation (ADPCM)". +- [9] ITU-T Recommendation Q.35: "Technical characteristics of tones for the telephone service". +- [10] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network". + +- [11] ITU-T Recommendation V.23: "600/1 200-band modem standardized for use in the general switched telephone network". +- [12] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD)". + +### 1.1.1 Abbreviations + +Abbreviations used in the present document are listed in GSM 01.04. + +## 1.2 Outline description + +The present document is structured as follows: + +Subclause 1.3 contains a functional description of the audio parts including the A/D and D/A functions. Subclause 1.4 describes the conversion between 13 bit uniform and 8 bit A-law samples. Subclauses 1.5 and 1.6 present a simplified description of the principles of the RPE-LTP encoding and decoding process respectively. In clause 1.7, the sequence and subjective importance of encoded parameters are given. + +Clause 2 deals with the transmission characteristics of the audio parts that are relevant for the performance of the RPE-LTP codec. + +Some transmission characteristics of the RPE-LTP codec are also specified in clause 2. Clause 3 presents the functional description of the RPE-LTP coding and decoding procedures, whereas clause 4 describes the computational details of the algorithm. Procedures for the verification of the correct functioning of the RPE-LTP are described in clause 5. + +Performance and network aspects of the RPE-LTP codec are contained in annex A. + +## 1.3 Functional description of audio parts + +The analogue-to-digital and digital-to-analogue conversion will in principle comprise the following elements: + +### 1) Analogue to uniform digital: + +- microphone; +- input level adjustment device; +- input anti-aliasing filter; +- sample-hold device sampling at 8 kHz; +- analogue-to-uniform digital conversion to 13 bits representation. + +The uniform format shall be represented in two's complement. + +### 2) Uniform digital to analogue: + +- conversion from 13 bit /8 kHz uniform PCM to analogue; +- a hold device; +- reconstruction filter including $x/\sin x$ correction; +- output level adjustment device; +- earphone or loudspeaker. + +In the terminal equipment, the A/D function may be achieved either: + +- by direct conversion to 13 bit uniform PCM format; +- or by conversion to 8 bit/A- or $\mu$ -law (PCS 1900) companded format, based on a standard A- or $\mu$ -law (PCS 1900) codec/filter according to ITU-T Recommendation G.711/714, followed by the 8-bit to 13-bit conversion according to the procedure specified in clause 1.4. + +For the D/A operation, the inverse operations take place. + +In the latter case it should be noted that the specifications in ITU-T recommendation G.714 (superseded by G.712) are concerned with PCM equipment located in the central parts of the network. When used in the terminal equipment, the present document does not on its own ensure sufficient out-of-band attenuation. + +The specification of out-of-band signals is defined in clause 2 between the acoustic signal and the digital interface to take into account that the filtering in the terminal can be achieved both by electronic and acoustical design. + +## 1.4 PCM Format conversion + +The conversion between 8 bit A- or $\mu$ -law (PCS 1900) companded format and the 13-bit uniform format shall be as defined in ITU-T Recommendation G.721 (superseded by G.726), clause 4.2.1, sub-block EXPAND and clause 4.2.7, sub-block COMPRESS. The parameter LAW = 1 should be used for A-law and LAW=0 should be used for $\mu$ -law (PCS 1900). + +## 1.5 Principles of the RPE-LTP encoder + +A simplified block diagram of the RPE-LTP encoder is shown in figure 1.1. In this diagram the coding and quantization functions are not shown explicitly. + +The input speech frame, consisting of 160 signal samples (uniform 13 bit PCM samples), is first pre-processed to produce an offset-free signal, which is then subjected to a first order pre-emphasis filter. The 160 samples obtained are then analysed to determine the coefficients for the short term analysis filter (LPC analysis). These parameters are then used for the filtering of the same 160 samples. The result is 160 samples of the short term residual signal. The filter parameters, termed reflection coefficients, are transformed to log.area ratios, LARs, before transmission. + +For the following operations, the speech frame is divided into 4 sub-frames with 40 samples of the short term residual signal in each. Each sub-frame is processed blockwise by the subsequent functional elements. + +Before the processing of each sub-block of 40 short term residual samples, the parameters of the long term analysis filter, the LTP lag and the LTP gain, are estimated and updated in the LTP analysis block, on the basis of the current sub-block of the present and a stored sequence of the 120 previous reconstructed short term residual samples. + +A block of 40 long term residual signal samples is obtained by subtracting 40 estimates of the short term residual signal from the short term residual signal itself. The resulting block of 40 long term residual samples is fed to the Regular Pulse Excitation analysis which performs the basic compression function of the algorithm. + +As a result of the RPE-analysis, the block of 40 input long term residual samples are represented by one of 4 candidate sub-sequences of 13 pulses each. The subsequence selected is identified by the RPE grid position (M). The 13 RPE pulses are encoded using Adaptive Pulse Code Modulation (APCM) with estimation of the sub-block amplitude which is transmitted to the decoder as side information. + +The RPE parameters are also fed to a local RPE decoding and reconstruction module which produces a block of 40 samples of the quantized version of the long term residual signal. + +By adding these 40 quantized samples of the long term residual to the previous block of short term residual signal estimates, a reconstructed version of the current short term residual signal is obtained. + +The block of reconstructed short term residual signal samples is then fed to the long term analysis filter which produces the new block of 40 short term residual signal estimates to be used for the next sub-block thereby completing the feedback loop. + +## 1.6 Principles of the RPE-LTP decoder + +The simplified block diagram of the RPE-LTP decoder is shown in fig 1.2. The decoder includes the same structure as the feed-back loop of the encoder. In error-free transmission, the output of this stage will be the reconstructed short term residual samples. These samples are then applied to the short term synthesis filter followed by the de-emphasis filter resulting in the reconstructed speech signal samples. + +## 1.7 Sequence and subjective importance of encoded parameters + +As indicated in fig 1.1 the three different groups of data are produced by the encoder are: + +- the short term filter parameters; +- the Long Term Prediction (LTP) parameters; +- the RPE parameters. + +The encoder will produce this information in a unique sequence and format, and the decoder shall receive the same information in the same way. In table 1.1, the sequence of output bits b1 to b260 and the bit allocation for each parameter is shown. + +The different parameters of the encoded speech and their individual bits have unequal importance with respect to subjective quality. Before being submitted to the channel encoding function the bits have to be rearranged in the sequence of importance as given in GSM 05.03. The ranking has been determined by subjective testing and the procedure used is described in annex A, clause A.2. + +**Table 1.1: Encoder output parameters in order of occurrence and bit allocation within the speech frame of 260 bits/20 ms** + +| Parameter | Parameter number | Parameter name | Var. name | Number of bits | Bit no. (LSB-MSB) | +|-------------------|------------------|------------------|-----------|----------------|-------------------| +| FILTER PARAMETERS | 1 | | LAR 1 | 6 | b1 - b6 | +| | 2 | | LAR 2 | 6 | b7 - b12 | +| | 3 | Log. Area ratios | LAR 3 | 5 | b13 - b17 | +| | 4 | | LAR 4 | 5 | b18 - b22 | +| | 5 | 1 - 8 | LAR 5 | 4 | b23 - b26 | +| | 6 | | LAR 6 | 4 | b27 - b30 | +| | 7 | | LAR 7 | 3 | b31 - b33 | +| | 8 | | LAR 8 | 3 | b34 - b36 | + +### Sub-frame no.1 + +| | | | | | | +|----------------|----|-------------------|--------|---|-----------| +| LTP PARAMETERS | 9 | LTP lag | N1 | 7 | b37 - b43 | +| | 10 | LTP gain | b1 | 2 | b44 - b45 | +| RPE PARAMETERS | 11 | RPE grid position | M1 | 2 | b46 - b47 | +| | 12 | Block amplitude | Xmax1 | 6 | b48 - b53 | +| | 13 | RPE-pulse no.1 | x1(0) | 3 | b54 - b56 | +| | 14 | RPE-pulse no.2 | x1(1) | 3 | b57 - b59 | +| | 25 | RPE-pulse no.13 | x1(12) | 3 | b90 - b92 | + +### Sub-frame no.2 + +| | | | | | | +|----------------|----|-------------------|--------|---|------------| +| LTP PARAMETERS | 26 | LTP lag | N2 | 7 | b93 - b99 | +| | 27 | LTP gain | b2 | 2 | b100- b101 | +| RPE PARAMETERS | 28 | RPE grid position | M2 | 2 | b102- b103 | +| | 29 | Block amplitude | Xmax2 | 6 | b104- b109 | +| | 30 | RPE-pulse no.1 | x2(0) | 3 | b110- b112 | +| | 31 | RPE-pulse no.2 | x2(1) | 3 | b113- b115 | +| | 42 | RPE-pulse no.13 | x2(12) | 3 | b146- b148 | + +**Table 1.1: Encoder output parameters in order of occurrence and bit allocation within the speech frame of 260 bits/20 ms** + +### Sub-frame no.3 + +| | | | | | | +|----------------|----|-------------------|----|---|------------| +| LTP PARAMETERS | 43 | LTP lag | N3 | 7 | b149- b155 | +| | 44 | LTP gain | b3 | 2 | b156- b157 | +| | 45 | RPE grid position | M3 | 2 | b158- b159 | + +| | | | | | | +|------------|----|-----------------|--------|---|------------| +| RPE | 46 | Block amplitude | Xmax3 | 6 | b160- b165 | +| PARAMETERS | 47 | RPE-pulse no.1 | x3(0) | 3 | b166- b168 | +| | 48 | RPE-pulse no.2 | x3(1) | 3 | b169- b171 | +| | .. | ... | | | ... | +| | 59 | RPE-pulse no.13 | x3(12) | 3 | b202- b204 | + +### Sub-frame no.4 + +| | | | | | | +|------------|----|-------------------|--------|---|------------| +| LTP | 60 | LTP lag | N4 | 7 | b205- b211 | +| PARAMETERS | 61 | LTP gain | b4 | 2 | b212- b213 | +| | 62 | RPE grid position | M4 | 2 | b214- b215 | +| RPE | 63 | Block amplitude | Xmax4 | 6 | b216- b221 | +| PARAMETERS | 64 | RPE-pulse no.1 | x4(0) | 3 | b222- b224 | +| | 65 | RPE-pulse no.2 | x4(1) | 3 | b225- b227 | +| | .. | ... | | | ... | +| | 76 | RPE-pulse no.13 | x4(12) | 3 | b258- b260 | + +![Simplified block diagram of the RPE - LTP encoder. The input signal is pre-processed and then split into a short term LPC analysis block and a short term analysis filter. The short term analysis filter output is labeled (1) Short term residual. This signal is added (+) to a feedback signal (3) Short term residual estimate (40 samples) to produce (2) Long term residual (40 samples). This residual is processed by an RPE grid selection and coding block, which outputs RPE parameters (47 bits/5 ms). The RPE parameters are also fed into an RPE grid decoding and positioning block, which outputs (5) Quantized long term residual (40 samples). This quantized residual is added (+) to the output of a long term analysis filter to produce (4) Reconstructed short term residual (40 samples). The reconstructed short term residual is fed into an LTP analysis block, which outputs LTP parameters (9 bits/5 ms). The short term LPC analysis block outputs reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms). All three parameter sets are sent to a radio subsystem.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms) + +Short term LPC analysis + +Input signal → Pre-processing → Short term analysis filter + +(1) Short term residual + +(2) Long term residual (40 samples) + +(3) Short term residual estimate (40 samples) + +(4) Reconstructed short term residual (40 samples) + +(5) Quantized long term residual (40 samples) + +RPE grid selection and coding + +RPE parameters (47 bits/5 ms) + +Long term analysis filter + +LTP analysis + +LTP parameters (9 bits/5 ms) + +RPE grid decoding and positioning + +To radio subsystem + +- (1) Short term residual +- (2) Long term residual (40 samples) +- (3) Short term residual estimate (40 samples) +- (4) Reconstructed short term residual (40 samples) +- (5) Quantized long term residual (40 samples) + +Simplified block diagram of the RPE - LTP encoder. The input signal is pre-processed and then split into a short term LPC analysis block and a short term analysis filter. The short term analysis filter output is labeled (1) Short term residual. This signal is added (+) to a feedback signal (3) Short term residual estimate (40 samples) to produce (2) Long term residual (40 samples). This residual is processed by an RPE grid selection and coding block, which outputs RPE parameters (47 bits/5 ms). The RPE parameters are also fed into an RPE grid decoding and positioning block, which outputs (5) Quantized long term residual (40 samples). This quantized residual is added (+) to the output of a long term analysis filter to produce (4) Reconstructed short term residual (40 samples). The reconstructed short term residual is fed into an LTP analysis block, which outputs LTP parameters (9 bits/5 ms). The short term LPC analysis block outputs reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms). All three parameter sets are sent to a radio subsystem. + +**Figure 1.1: Simplified block diagram of the RPE - LTP encoder**![Simplified block diagram of the RPE - LTP decoder. The decoder receives RPE parameters (47 bits/5 ms) and LTP parameters (9 bits/5 ms) from a radio subsystem. The RPE parameters are processed by an RPE grid decoding and positioning block. The output of this block is added (+) to the output of a long term synthesis filter. The sum is then processed by a short term synthesis filter. The output of the short term synthesis filter is post-processed to produce the final output signal. The short term synthesis filter also receives reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms).](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms) + +RPE parameters (47 bits/5 ms) + +RPE grid decoding and positioning + +Long term synthesis filter + +Short term synthesis filter + +Post-processing + +Output signal + +LTP parameters (9 bits/5 ms) + +From radio subsystem + +Simplified block diagram of the RPE - LTP decoder. The decoder receives RPE parameters (47 bits/5 ms) and LTP parameters (9 bits/5 ms) from a radio subsystem. The RPE parameters are processed by an RPE grid decoding and positioning block. The output of this block is added (+) to the output of a long term synthesis filter. The sum is then processed by a short term synthesis filter. The output of the short term synthesis filter is post-processed to produce the final output signal. The short term synthesis filter also receives reflection coefficients coded as Log. - Area Ratios (36 bits/20 ms). + +**Figure 1.2: Simplified block diagram of the RPE - LTP decoder** + +# --- 2 Transmission characteristics + +This clause specifies the necessary performance characteristics of the audio parts for proper functioning of the speech transcoder. Some transmission performance characteristics of the RPE-LTP transcoder are also given to assist the designer of the speech transcoder function. The information given here is redundant and the detailed specifications are contained in recommendation GSM 11.10. + +The performance characteristics are referred to the 13 bit uniform PCM interface. + +NOTE: To simplify the verification of the specifications, the performance limits may be referred to an A- or $\mu$ -law (PCS 1900) measurement interface according to ITU-T Recommendation G.711. In this way, standard measuring equipments for PCM systems can be utilized for measurements. The relationship between the 13 bit format and the A- or $\mu$ -law (PCS 1900) companded shall follow the procedures defined in clause 1.4. + +## 2.1 Performance characteristics of the analogue/digital interfaces + +Concerning 1) discrimination against out-of-band signals (sending) and 2) spurious out-of-band signals (receiving), the same requirements as defined in ETSI standard TE 04-15 (digital telephone, candidate NET33) apply. + +## 2.2 Transcoder delay + +Consider a back to back configuration where the parameters generated by the encoder are delivered to the speech decoder as soon as they are available. + +The transcoder delay is defined as the time interval between the instant a speech frame of 160 samples has been received at the encoder input and the instant the corresponding 160 reconstructed speech samples have been out-put by the speech decoder at an 8 kHz sample rate. + +The theoretical minimum delay which can be achieved is 20 ms. The requirement is that the transcoder delay should be less than 30 ms. + +# --- 3 Functional description of the RPE-LTP codec + +The block diagram of the RPE-LTP-coder is shown in figure 3.1. The individual blocks are described in the following clauses. + +## 3.1 Functional description of the RPE-LTP encoder + +The **Pre-processing clause** of the RPE-LTP encoder comprises the following two sub-blocks: + +- Offset compensation (3.1.1); +- Pre-emphasis (3.1.2). + +The **LPC analysis clause** of the RPE-LTP encoder comprises the following five sub-blocks: + +- Segmentation (3.1.3); +- Auto-Correlation (3.1.4); +- Schur Recursion (3.1.5); +- Transformation of reflection coefficients to Log.-Area Ratios (3.1.6); +- Quantization and coding of Log.-Area Ratios (3.1.7). + +The **Short term analysis filtering clause** of the RPE-LTP comprises the following four sub-blocks: + +- Decoding of the quantized Log.-Area Ratios (LARs) (3.1.8); +- Interpolation of Log.-Area Ratios (3.1.9); + +- Transformation of Log.-Area Ratios into reflection coefficients (3.1.10); +- Short term analysis filtering (3.1.11). + +The **Long Term Predictor (LTP) clause** comprises 4 sub-blocks working on subsegments (3.1.12) of the short term residual samples: + +- Calculation of LTP parameters (3.1.13); +- Coding of the LTP lags (3.1.14) and the LTP gains (3.1.15); +- Decoding of the LTP lags (3.1.14) and the LTP gains (3.1.15); +- Long term analysis filtering (3.1.16), and Long term synthesis filtering (3.1.17). + +The **RPE encoding clause** comprises five different sub-blocks: + +- Weighting filter (3.1.18); +- Adaptive sample rate decimation by RPE grid selection (3.1.19); +- APCM quantization of the selected RPE sequence (3.1.20); +- APCM inverse quantization (3.1.21); +- RPE grid positioning (3.1.22). + +### Pre-processing clause + +### 3.1.1 Offset compensation + +Prior to the speech encoder an offset compensation, by a notch filter is applied in order to remove the offset of the input signal $s_o$ to produce the offset-free signal $s_{of}$ + +$$s_{of}(k) = s_o(k) - s_o(k-1) + \alpha \cdot s_{of}(k-1) \quad (3.1.1)$$ + +$$\alpha = 32735 \cdot 2^{-15}$$ + +### 3.1.2 Pre-emphasis + +The signal $s_{of}$ is applied to a first order FIR pre-emphasis filter leading to the input signal $s$ of the analysis clause. + +$$s(k) = s_{of}(k) - \beta \cdot s_{of}(k-1) \quad (3.1.2)$$ + +$$\beta = 28180 \cdot 2^{-15}$$ + +### LPC analysis clause + +### 3.1.3 Segmentation + +The speech signal $s(k)$ is divided into non-overlapping frames having a length of $T_0 = 20$ ms (160 samples). A new LPC-analysis of order $p=8$ is performed for each frame. + +### 3.1.4 Autocorrelation + +The first $p+1 = 9$ values of the Auto-Correlation function are calculated by: + +$$ACF(k) = \sum_{i=k}^{159} s(i)s(i-k) \quad , k = 0, 1, \dots, 8 \quad (3.2)$$ + +### 3.1.5 Schur Recursion + +The reflection coefficients are calculated as shown in figure 3.2 using the Schur Recursion algorithm. The term "reflection coefficient" comes from the theory of linear prediction of speech (LPC), where a vocal tract representation consisting of series of uniform cylindrical clauses is assumed. Such a representation can be described by the reflection coefficients or the area ratios of connected clauses. + +### 3.1.6 Transformation of reflection coefficients to Log.-Area Ratios + +The reflection coefficients $r(i)$ , ( $i=1..8$ ), calculated by the Schur algorithm, are in the range: + +$$-1 \leq r(i) \leq +1$$ + +Due to the favourable quantization characteristics, the reflection coefficients are converted into Log.-Area Ratios which are strictly defined as follows: + +$$Logarea(i) = \log_{10} \left( \frac{1 + r(i)}{1 - r(i)} \right) \quad (3.3)$$ + +Since it is the companding characteristic of this transformation that is of importance, the following segmented approximation is used. + +$$LAR(i) = \begin{cases} r(i) & ; |r(i)| < 0.675 \\ \text{sign}[r(i)] * [2|r(i)| - 0.675] & ; 0.675 \leq |r(i)| < 0.950 \\ \text{sign}[r(i)] * [8|r(i)| - 6.375] & ; 0.950 \leq |r(i)| \leq 1.000 \end{cases} \quad (3.4)$$ + +with the result that instead of having to divide and obtain the logarithm of particular values, it is merely necessary to multiply, add and compare these values. + +The following equation (3.5) gives the inverse transformation. + +$$r'(i) = \begin{cases} \text{LAR}'(i) & ; |\text{LAR}'(i)| < 0.675 \\ \text{sign}[\text{LAR}'(i)] * [0.500 * |\text{LAR}'(i)| + 0.337500] & ; 0.675 \leq |\text{LAR}'(i)| < 1.225 \\ \text{sign}[\text{LAR}'(i)] * [0.125 * |\text{LAR}'(i)| + 0.796875] & ; 1.225 \leq |\text{LAR}'(i)| \leq 1.625 \end{cases} \quad (3.5)$$ + +### 3.1.7 Quantization and coding of Log.-Area Ratios + +The Log.-Area Ratios $LAR(i)$ have different dynamic ranges and different asymmetric distribution densities. For this reason, the transformed coefficients $LAR(i)$ are limited and quantized differently according to the following equation (3.6), with $LAR_c(i)$ denoting the quantized and integer coded version of $LAR(i)$ . + +$$LAR_c(i) = \text{Nint}\{A(i) * LAR(i) + B(i)\} \quad (3.6)$$ + +with + +$$\text{Nint}\{z\} = \text{int}\{z + \text{sign}\{z\} * 0.5\} \quad (3.6a)$$ + +Function Nint defines the rounding to the nearest integer value, with the coefficients $A(i)$ , $B(i)$ , and different extreme values of $LAR_c(i)$ for each coefficient $LAR(i)$ given in table 3.1. + +**Table 3.1: Quantization of the Log.-Area Ratios LAR(i)** + +| LAR No i | A(i) | B(i) | Minimum LAR c (i) | Maximum LAR c (i) | +|----------|--------|--------|------------------------------|------------------------------| +| 1 | 20.000 | 0.000 | -32 | +31 | +| 2 | 20.000 | 0.000 | -32 | +31 | +| 3 | 20.000 | 4.000 | -16 | +15 | +| 4 | 20.000 | -5.000 | -16 | +15 | +| 5 | 13.637 | 0.184 | - 8 | + 7 | +| 6 | 15.000 | -3.500 | - 8 | + 7 | +| 7 | 8.334 | -0.666 | - 4 | + 3 | +| 8 | 8.824 | -2.235 | - 4 | + 3 | + +### Short-term analysis filtering clause + +The current frame of the speech signal $s$ is retained in memory until calculation of the LPC parameters LAR(i) is completed. The frame is then read out and fed to the short term analysis filter of order $p=8$ . However, prior to the analysis filtering operation, the filter coefficients are decoded and pre-processed by interpolation. + +### 3.1.8 Decoding of the quantized Log.-Area Ratios + +In this block the quantized and coded Log.-Area Ratios (LARc(i)) are decoded according to equation (3.7). + +$$\text{LAR}'(i) = ( \text{LAR}_c(i) - B(i) ) / A(i) \quad (3.7)$$ + +### 3.1.9 Interpolation of Log.-Area Ratios + +To avoid spurious transients which may occur if the filter coefficients are changed abruptly, two subsequent sets of Log.-Area Ratios are interpolated linearly. Within each frame of 160 analysed speech samples the short term analysis filter and the short term synthesis filter operate with four different sets of coefficients derived according to table 3.2. + +**Table 3.2: Interpolation of LAR parameters (J=actual segment)** + +| k | LAR'(J)(i) = | +|---------|-----------------------------------------------------------------| +| 0...12 | $0.75 \cdot \text{LAR}'(J-1)(i) + 0.25 \cdot \text{LAR}'(J)(i)$ | +| 13...26 | $0.50 \cdot \text{LAR}'(J-1)(i) + 0.50 \cdot \text{LAR}'(J)(i)$ | +| 27...39 | $0.25 \cdot \text{LAR}'(J-1)(i) + 0.75 \cdot \text{LAR}'(J)(i)$ | +| 40..159 | $\text{LAR}'(J)(i)$ | + +### 3.1.10 Transformation of Log.-Area Ratios into reflection coefficients + +The reflection coefficients are finally determined using the inverse transformation according to equation (3.5). + +### 3.1.11 Short term analysis filtering + +The Short term analysis filter is implemented according to the lattice structure depicted in figure 3.3. + +$$d_0(k) = s(k) \quad (3.8a)$$ + +$$u_0(k) = s(k) \quad (3.8b)$$ + +$$d_i(k) = d_{i-1}(k) + r'_i \cdot u_{i-1}(k-1) \quad \text{with } i=1, \dots, 8 \quad (3.8c)$$ + +$$u_i(k) = u_{i-1}(k-1) + r'_i \cdot d_{i-1}(k) \quad \text{with } i=1, \dots, 8 \quad (3.8d)$$ + +$$d(k) = d_8(k) \quad (3.8e)$$ + +### Long-Term Predictor (LTP) clause + +### 3.1.12 Sub-segmentation + +Each input frame of the short term residual signal contains 160 samples, corresponding to 20 ms. The long term correlation is evaluated four times per frame, for each 5 ms subsegment. For convenience in the following, we note + +$j=0,\dots,3$ the sub-segment number, so that the samples pertaining to the $j$ -th sub-segment of the residual signal are now denoted by $d(k_j+k)$ with $j = 0,\dots,3$ ; $k_j = k_0 + j*40$ and $k = 0,\dots,39$ where $k_0$ corresponds to the first value of the current frame. + +### 3.1.13 Calculation of the LTP parameters + +For each of the four sub-segments a long term correlation lag $N_j$ , ( $j=0,\dots,3$ ), and an associated gain factor $b_j$ , ( $j=0,\dots,3$ ) are determined. For each sub-segment, the determination of these parameters is implemented in three steps. + +- 1) The first step is the evaluation of the cross-correlation $R_j(\lambda)$ of the current sub-segment of short term residual signal $d(k_j+i)$ , ( $i=0,\dots,39$ ) and the previous samples of the reconstructed short term residual signal $d'(k_j+i)$ , ( $i=-120,\dots,-1$ ): + +$$R_j(\lambda) = \sum_{i=0}^{39} d(k_j+i) * d'(k_j+i-\lambda); \quad \begin{aligned} j &= 0, \dots, 3 \\ k_j &= k_0 + j*40 \\ \lambda &= 40, \dots, 120 \end{aligned} \quad (3.9)$$ + +The cross-correlation is evaluated for lags $\lambda$ greater than or equal to 40 and less than or equal to 120, i.e. corresponding to samples outside the current sub-segment and not delayed by more than two sub-segments. + +- 2) The second step is to find the position $N_j$ of the peak of the cross-correlation function within this interval: + +$$\begin{aligned} R_j(N_j) &= \max \{ R_j(\lambda); \lambda = 40..120 \}; \\ j &= 0, \dots, 3 \end{aligned} \quad (3.10)$$ + +- 3) The third step is the evaluation of the gain factor $b_j$ according to: + +$$b_j = R_j(N_j) / S_j(N_j); \quad j = 0, \dots, 3 \quad (3.11)$$ + +with + +$$S_j(N_j) = \sum_{i=0}^{39} d'^2(k_j+i-N_j); \quad j = 0, \dots, 3 \quad (3.12)$$ + +It is clear that the last 120 samples of the reconstructed short term residual signal $d'(k_j+i)$ , ( $i=-120,\dots,-1$ ) shall be retained until the next sub-segment so as to allow the evaluation of the relations (3.9),..., (3.12). + +### 3.1.14 Coding/Decoding of the LTP lags + +The long term correlation lags $N_j$ , ( $j=0,\dots,3$ ) can have values in the range (40,...,120), and so shall be coded using 7 bits with: + +$$N_{cj} = N_j; \quad j = 0, \dots, 3 \quad (3.13)$$ + +At the receiving end, assuming an error free transmission, the decoding of these values will restore the actual lags: + +$$N_j' = N_{cj}; \quad j = 0, \dots, 3 \quad (3.14)$$ + +### 3.1.15 Coding/Decoding of the LTP gains + +The long term prediction gains $b_j$ , ( $j=0,\dots,3$ ) are encoded with 2 bits each, according to the following algorithm: + +``` + +if bj <= DLB(i) then bcj = 0; i=0 +if DLB(i-1) < bj <= DLB(i) then bcj = i; i=1,2 +if DLB(i-1) < bj then bcj = 3; i=3 + +``` + +(3.15) + +where DLB(i), (i=0,...,2) denotes the decision levels of the quantizer, and bcj represents the coded gain value. Decision levels and quantizing levels are given in table 3.3. + +**Table 3.3: Quantization table for the LTP gain** + +| i | Decision level | Quantizing level | +|---|----------------|------------------| +| | DLB(i) | QLB(i) | +| 0 | 0.2 | 0.10 | +| 1 | 0.5 | 0.35 | +| 2 | 0.8 | 0.65 | +| 3 | | 1.00 | + +The decoding rule is implemented according to: + +$$b_j' = QLB(b_{cj}) ; j = 0, \dots, 3 \quad (3.16)$$ + +where QLB(i), (i=0,...,3) denotes the quantizing levels, and bj' represents the decoded gain value (see table 3.3). + +### 3.1.16 Long term analysis filtering + +The short term residual signal d(k0+k), (k=0,...,159) is processed by sub-segments of 40 samples. From each of the four sub-segments (j=0,...,3) of short term residual samples, denoted here d(kj+k), (k=0,...,39), an estimate d''(kj+k), (k=0,...,39) of the signal is subtracted to give the long term residual signal e(kj+k), (k=0,...,39) (see figure 3.1): + +$$\begin{aligned} + e(k_j+k) &= d(k_j+k) - d''(k_j+k) & ; \quad j &= 0, \dots, 3 \\ + & & ; \quad k &= 0, \dots, 39 \\ + & & k_j &= k_0 + j*40 + \end{aligned} \quad (3.17)$$ + +Prior to this subtraction, the estimated samples d''(kj+k) are computed from the previously reconstructed short term residual samples d', adjusted to the current sub-segment LTP lag Nj' and weighted with the sub-segment LTP gain bj': + +$$\begin{aligned} + d''(k_j+k) &= b_j' * d'(k_j+k-N_j') & ; \quad j &= 0, \dots, 3 \\ + & & ; \quad k &= 0, \dots, 39 \\ + & & k_j &= k_0 + j*40 + \end{aligned} \quad (3.18)$$ + +### 3.1.17 Long term synthesis filtering + +The reconstructed long term residual signal e'(k0+k), (k=0,...,159) is processed by sub-segments of 40 samples. To each sub-segment, denoted here e'(kj+k), (k=0,...,39), the estimate d''(kj+k), (k=0,...,39) of the signal is added to give the reconstructed short term residual signal d'(kj+k), (k=0,...,39): + +$$\begin{aligned} + d'(k_j+k) &= e'(k_j+k) + d''(k_j+k) & ; \quad j &= 0, \dots, 3 \\ + & & ; \quad k &= 0, \dots, 39 \\ + & & k_j &= k_0 + j*40 + \end{aligned} \quad (3.19)$$ + +### RPE encoding clause + +### 3.1.18 Weighting Filter + +A FIR "block filter" algorithm is applied to each sub-segment by convolving 40 samples e(k) with the impulse response H(i) ; i=0,...,10 (see table 3.4). + +**Table 3.4: Impulse response of block filter (weighting filter)** + +| i | 5 | 4 (6) | 3 (7) | 2 (8) | 1 (9) | 0 (10) | +|---------------|----------|--------------|--------------|--------------|--------------|---------------| +| $H(i)*2^{13}$ | 8192 | 5741 | 2054 | 0 | -374 | -134 | + +$$|H(\Omega=0)| = 2.779;$$ + +The conventional convolution of a sequence having 40 samples with an 11-tap impulse response would produce $40+11-1=50$ samples. In contrast to this, the "block filter" algorithm produces the 40 central samples of the conventional convolution operation. For notational convenience the block filtered version of each sub-segment is denoted by $x(k)$ , $k=0,\dots,39$ . + +$$x(k) = \sum_{i=0}^{10} H(i) * e(k+5-i) \quad \text{with } k = 0, \dots, 39 \quad (3.20)$$ + +NOTE: $e(k+5-i) = 0$ for $k+5-i < 0$ and $k+5-i > 39$ . + +### 3.1.19 Adaptive sample rate decimation by RPE grid selection + +For the next step, the filtered signal $x$ is down-sampled by a ratio of 3 resulting in 3 interleaved sequences of lengths 14, 13 and 13, which are split up again into 4 sub-sequences $x_m$ of length 13: + +$$x_m(i) = x(k_j + m + 3*i) \quad ; \quad i = 0, \dots, 12 \quad (3.21)$$ + +$$m = 0, \dots, 3$$ + +with $m$ denoting the position of the decimation grid. According to the explicit solution of the RPE mean squared error criterion, the optimum candidate sub-sequence $x_M$ is selected which is the one with the maximum energy: + +$$E_M = \max_m \sum_{i=0}^{12} x_m^2(i) \quad ; \quad m = 0, \dots, 3 \quad (3.22)$$ + +The optimum grid position $M$ is coded as $M_c$ with 2 bits. + +### 3.1.20 APCM quantization of the selected RPE sequence + +The selected sub-sequence $x_M(i)$ (RPE sequence) is quantized, applying APCM (Adaptive Pulse Code Modulation). For each RPE sequence consisting of a set of 13 samples $x_M(i)$ , the maximum $x_{max}$ of the absolute values $|x_M(i)|$ is selected and quantized logarithmically with 6 bits as $x_{maxc}$ as given in table 3.5. + +**Table 3.5: Quantization of the block maximum $x_{\max}$** + +| xmax | x'max | xmaxc | xmax | x'max | xmaxc | +|--------------|--------------|--------------|----------------|--------------|--------------| +| 0 .. 31 | 31 | 0 | 2048 .. 2303 | 2303 | 32 | +| 32 .. 63 | 63 | 1 | 2304 .. 2559 | 2559 | 33 | +| 64 .. 95 | 95 | 2 | 2560 .. 2815 | 2815 | 34 | +| 96 .. 127 | 127 | 3 | 2816 .. 3071 | 3071 | 35 | +| 128 .. 159 | 159 | 4 | 3072 .. 3327 | 3327 | 36 | +| 160 .. 191 | 191 | 5 | 3328 .. 3583 | 3583 | 37 | +| 192 .. 223 | 223 | 6 | 3584 .. 3839 | 3839 | 38 | +| 224 .. 255 | 255 | 7 | 3840 .. 4095 | 4095 | 39 | +| 256 .. 287 | 287 | 8 | 4096 .. 4607 | 4607 | 40 | +| 288 .. 319 | 319 | 9 | 4608 .. 5119 | 5119 | 41 | +| 320 .. 351 | 351 | 10 | 5120 .. 5631 | 5631 | 42 | +| 352 .. 383 | 383 | 11 | 5632 .. 6143 | 6143 | 43 | +| 384 .. 415 | 415 | 12 | 6144 .. 6655 | 6655 | 44 | +| 416 .. 447 | 447 | 13 | 6656 .. 7167 | 7167 | 45 | +| 448 .. 479 | 479 | 14 | 7168 .. 7679 | 7679 | 46 | +| 480 .. 511 | 511 | 15 | 7680 .. 8191 | 8191 | 47 | +| 512 .. 575 | 575 | 16 | 8192 .. 9215 | 9215 | 48 | +| 576 .. 639 | 639 | 17 | 9216 .. 10239 | 10239 | 49 | +| 640 .. 703 | 703 | 18 | 10240 .. 11263 | 11263 | 50 | +| 704 .. 767 | 767 | 19 | 11264 .. 12287 | 12287 | 51 | +| 768 .. 831 | 831 | 20 | 12288 .. 13311 | 13311 | 52 | +| 832 .. 895 | 895 | 21 | 13312 .. 14335 | 14335 | 53 | +| 896 .. 959 | 959 | 22 | 14336 .. 15359 | 15359 | 54 | +| 960 .. 1023 | 1023 | 23 | 15360 .. 16383 | 16383 | 55 | +| 1024 .. 1151 | 1151 | 24 | 16384 .. 18431 | 18431 | 56 | +| 1152 .. 1279 | 1279 | 25 | 18432 .. 20479 | 20479 | 57 | +| 1280 .. 1407 | 1407 | 26 | 20480 .. 22527 | 22527 | 58 | +| 1408 .. 1535 | 1535 | 27 | 22528 .. 24575 | 24575 | 59 | +| 1536 .. 1663 | 1663 | 28 | 24576 .. 26623 | 26623 | 60 | +| 1664 .. 1791 | 1791 | 29 | 26624 .. 28671 | 28671 | 61 | +| 1792 .. 1919 | 1919 | 30 | 28672 .. 30719 | 30719 | 62 | +| 1920 .. 2047 | 2047 | 31 | 30720 .. 32767 | 32767 | 63 | + +For the normalization, the 13 samples are divided by the decoded version $x'_{\max}$ of the block maximum. Finally, the normalized samples: + +$$x'(i) = x_M(i)/x'_{\max} ; \quad i=0, \dots, 12 \quad (3.23)$$ + +are quantized uniformly with three bits to $x_{Mc}(i)$ as given in table 3.6. + +**Table 3.6: Quantization of the normalized RPE-samples** + +| x' \cdot 2^{15}
(Interval-limits) | \underline{x}_M \cdot 2^{15} | x_{Mc}
(Channel) | +|----------------------------------------------------------|--------------------------------------------------|-----------------------------------------| +| -32768 ... -24577 | -28672 | 0 = 000 | +| -24576 ... -16385 | -20480 | 1 = 001 | +| -16384 ... -8193 | -12288 | 2 = 010 | +| -8192 ... -1 | -4096 | 3 = 011 | +| 0 ... 8191 | 4096 | 4 = 100 | +| 8192 ... 16383 | 12288 | 5 = 101 | +| 16384 ... 24575 | 20480 | 6 = 110 | +| 24576 ... 32767 | 28672 | 7 = 111 | + +### 3.1.21 APCM inverse quantization + +The $x_{Mc}(i)$ are decoded to $\underline{x}_M(i)$ and denormalized using the decoded value $x'_{\max}$ leading to the decoded sub-sequence $x'_M(i)$ . + +### 3.1.22 RPE grid positioning + +The quantized sub-sequence is upsampled by a ratio of 3 by inserting zero values according to the grid position given with $M_c$ . + +## 3.2 Decoder + +The decoder comprises the following 4 clauses. Most of the sub-blocks are also needed in the encoder and have been described already. Only the short term synthesis filter and the de-emphasis filter are added in the decoder as new sub-blocks. + +- RPE decoding clause (3.2.1); +- Long Term Prediction clause (3.2.2); +- Short term synthesis filtering clause (3.2.3); +- Post-processing (3.2.4). + +The complete block diagram for the decoder is shown in figure 3.4. The variables and parameters of the decoder are marked by the index $r$ to distinguish the received values from the encoder values. + +### 3.2.1 RPE decoding clause + +The input signal of the long term synthesis filter (reconstruction of the long term residual signal) is formed by decoding and denormalizing the RPE-samples (APCM inverse quantization - 3.1.21) and by placing them in the correct time position (RPE grid positioning - 3.1.22). At this stage, the sampling frequency is increased by a factor of 3 by inserting the appropriate number of intermediate zero-valued samples. + +### 3.2.2 Long Term Prediction clause + +The reconstructed long term residual signal $e_r'$ is applied to the long term synthesis filter (see 3.1.16 and 3.1.17) which produces the reconstructed short term residual signal $d_r'$ for the short term synthesizer. + +### 3.2.3 Short term synthesis filtering clause + +The coefficients of the short term synthesis filter (see figure 3.5) are reconstructed applying the identical procedure to that in the encoder (3.1.8 - 3.1.10). The short term synthesis filter is implemented according to the lattice structure depicted in figure 3.5. + +$$s_{r(0)}(k) = d_r'(k) \quad (3.24a)$$ + +$$s_{r(i)}(k) = s_{r(i-1)}(k) - r_{r'(9-i)} * v_{8-i}(k-1); \quad i=1, \dots, 8 \quad (3.24b)$$ + +$$v_{9-i}(k) = v_{8-i}(k-1) + r_{r'(9-i)} * s_{r(i)}(k); \quad i=1, \dots, 8 \quad (3.24c)$$ + +$$s_{r'}(k) = s_{r(8)}(k) \quad (3.24d)$$ + +$$v_0(k) = s_{r(8)}(k) \quad (3.24e)$$ + +### 3.2.4 Post-processing + +The output of the synthesis filter $s_r(k)$ is fed into the IIR- de-emphasis filter leading to the output signal $s_{ro}$ . + +$$s_{ro}(k) = s_r(k) + \beta * s_{ro}(k-1); \quad \beta = 28180 * 2^{-15} \quad (3.25)$$ + +![Block diagram of the RPE - LTP encoder showing signal flow and parameter encoding paths.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the RPE - LTP encoder architecture, divided into four main processing stages: Preprocessing, LPC analysis, Short term analysis filtering, and Long term Prediction. A legend at the bottom right indicates that thin arrows represent signals and thick arrows represent parameters to the radio subsystem. + +- Preprocessing:** The input signal $s_0$ is processed by an **Offset compensation** block (producing $s_{0f}$ ) and a **Preemphasis** block (producing $s$ ). +- LPC analysis:** The signal $s$ is processed by **Segmentation**, **Auto-correlation** (producing **ACF**), **Schur recursion** (producing $r$ ), and **Log Area Ratios** (producing **LAR**). This **LAR** is then processed by a **Quantizer/coder** to produce **LARc**, which is sent to the radio subsystem. +- Short term analysis filtering:** The signal $s$ is processed by an **Inverse filter $A(z)$** to produce $r'$ . This is followed by **Reflection coefficients** (producing **LAR'**), **Interpolation** (producing **LAR''**), and a **LAR decoder** to produce **LARc**, which is sent to the radio subsystem. +- Long term Prediction:** The signal $s$ is processed by a **Weighting filter $H(z)$** to produce $x_m$ . This is processed by **RPE grid selection** to produce $M_c$ (sent to the radio subsystem) and $x_m$ . The signal $x_m$ is then processed by an **APCM quantizer** to produce $x_{mc}$ and $x_{maxc}$ (both sent to the radio subsystem). The signal $x_{mc}$ is processed by an **Inverse APCM** block to produce $x'_m$ . The signal $x'_m$ is processed by an **RPE grid position** block to produce $e'$ (sent to the radio subsystem). The signal $e'$ is then processed by a summation node (+) to produce the error signal $e$ . +- Feedback and LTP:** The error signal $e$ is processed by a summation node (+) to produce $d''$ . The signal $d''$ is processed by a summation node (+) to produce $d$ . The signal $d$ is processed by an **LTP parameter** block to produce $N$ and $b$ (both sent to the radio subsystem). The signal $b$ is processed by a **Quantizer/coder** to produce $b_c$ (sent to the radio subsystem). The signal $b_c$ is processed by an **LTP parameter decoder** to produce $N'$ and $b'$ (both sent to the radio subsystem). The signal $N'$ is processed by a delay block $z^{-N}$ to produce $d'$ . The signal $d'$ is processed by a summation node (+) to produce $d''$ . The signal $d''$ is processed by a summation node (+) to produce $e$ . + +Block diagram of the RPE - LTP encoder showing signal flow and parameter encoding paths. + +Figure 3.1: Block diagram of the RPE - LTP encoder + +![Flowchart of LPC analysis using Schur recursion. The process starts with n=1, checks if ACF=0, initializes K and P, then enters a loop for n from 1 to 8. Inside the loop, it checks if P(0) < |P(1)|, calculates r(n), checks if P(1) > 0, and if n=8. If not n=8, it updates P(0) and enters an inner loop for m from 1 to 8-n, updating P(m) and K(9-m). Finally, it performs a transformation r -> LAR and ends.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +graph TD + Start[n = 1] --> ACF0{ACF = 0 ?} + ACF0 -- yes --> rInit[r(i) = 0; i = n, ..., 8] + ACF0 -- no --> InitK[ $K(9 - i) = ACF(i); i=1, \dots, 7$ + $P(j) = ACF(j); j=0, \dots, 8$ ] + InitK --> P0P1{ $P(0) < |P(1)|$ ?} + P0P1 -- yes --> rInit + P0P1 -- no --> rN[r(n) = $|P(1)| / P(0)$ ] + rN --> P1Pos{ $P(1) > 0$ ?} + P1Pos -- yes --> rNneg[r(n) = $-r(n)$ ] + P1Pos -- no --> n8{n = 8 ?} + rNneg --> n8 + n8 -- yes --> Transform[/Transformation +r -> LAR/] + n8 -- no --> P0Update[P(0) = $P(0) + P(1) * r(n)$ ] + P0Update --> m1[m = 1] + m1 --> PMK[ $P(m) = P(1 + m) + r(n) * K(9 - m)$ + $K(9 - m) = K(9 - m) + r(n) * P(1 + m)$ ] + PMK --> m8n{ $m = 8 - n$ ?} + m8n -- yes --> nInc[n = n + 1] + m8n -- no --> mInc[m = m + 1] + mInc --> PMK + nInc --> P0Update + Transform --> END[END] + +``` + +Flowchart of LPC analysis using Schur recursion. The process starts with n=1, checks if ACF=0, initializes K and P, then enters a loop for n from 1 to 8. Inside the loop, it checks if P(0) < |P(1)|, calculates r(n), checks if P(1) > 0, and if n=8. If not n=8, it updates P(0) and enters an inner loop for m from 1 to 8-n, updating P(m) and K(9-m). Finally, it performs a transformation r -> LAR and ends. + +Figure 3.2: LPC analysis using Schur recursion + +![Block diagram of a short term analysis filter. The input s(k) is split into two paths. The top path consists of a series of adders (+) producing outputs d0, d1, d2, ..., d8, and finally d(k). The bottom path consists of delay blocks (T) and adders (+) producing intermediate signals u0, u1, u2, ..., u8. Reflection coefficients r1, r2, ..., r8 are used in both paths: in the top path, they are subtracted from the signal before the adder, and in the bottom path, they are subtracted from the delayed signal before the adder.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Block diagram of a short term analysis filter. The input s(k) is split into two paths. The top path consists of a series of adders (+) producing outputs d0, d1, d2, ..., d8, and finally d(k). The bottom path consists of delay blocks (T) and adders (+) producing intermediate signals u0, u1, u2, ..., u8. Reflection coefficients r1, r2, ..., r8 are used in both paths: in the top path, they are subtracted from the signal before the adder, and in the bottom path, they are subtracted from the delayed signal before the adder. + +Figure 3.3: Short term analysis filter + +![Block diagram of the RPE-LTP decoder. The diagram is divided into four sections: RPE decoding, Long term Prediction, Short term synthesis filtering, and Postprocessing. Inputs include Mcr, xmaxcr, xmcr, bcr, Ncr, and LARcr. The RPE decoding section uses Mcr and xmcr' to find an RPE grid position, which is then added to a prediction signal. The Long term Prediction section uses b'r' and N'r' from an LTP parameter decoder, along with a delay block (-N/z), to generate the prediction signal. The Short term synthesis filtering section uses reflection coefficients r'r' derived from LAR'r' and LARcr via a LAR decoder and interpolation. The final output s' is processed by a Deemphasis block to produce s'0. A legend indicates that thin arrows represent signals and thick arrows represent parameters from the radio subsystem.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +Block diagram of the RPE-LTP decoder. The diagram is divided into four sections: RPE decoding, Long term Prediction, Short term synthesis filtering, and Postprocessing. Inputs include Mcr, xmaxcr, xmcr, bcr, Ncr, and LARcr. The RPE decoding section uses Mcr and xmcr' to find an RPE grid position, which is then added to a prediction signal. The Long term Prediction section uses b'r' and N'r' from an LTP parameter decoder, along with a delay block (-N/z), to generate the prediction signal. The Short term synthesis filtering section uses reflection coefficients r'r' derived from LAR'r' and LARcr via a LAR decoder and interpolation. The final output s' is processed by a Deemphasis block to produce s'0. A legend indicates that thin arrows represent signals and thick arrows represent parameters from the radio subsystem. + +Figure 3.4: Block diagram of the RPE-LTP decoder + +![Figure 3.5: Short term synthesis filter diagram. The diagram shows a feedforward filter structure with three stages. The input d_r' enters from the right. The first stage has a summer with a positive input from d_r' and a negative feedback from a delay element. The output of this summer is s_r0. Below this, there is a delay element 'T' followed by a summer with a positive input from the delay and a negative feedback from a delay element 'r_8'. The output of this summer is v_8. The second stage is similar, with a summer producing s_r6 and a delay element 'T' followed by a summer producing v_2. The third stage produces s_r7 and v_1. The final output s_r(k) is produced by a summer with a positive input from s_r8 and a negative feedback from a delay element 'r_1'. The output s_r(k) is also fed back to the first stage through a delay element 'T'.](26d664119ad25250780f554633444e54_img.jpg) + +Figure 3.5: Short term synthesis filter diagram. The diagram shows a feedforward filter structure with three stages. The input d\_r' enters from the right. The first stage has a summer with a positive input from d\_r' and a negative feedback from a delay element. The output of this summer is s\_r0. Below this, there is a delay element 'T' followed by a summer with a positive input from the delay and a negative feedback from a delay element 'r\_8'. The output of this summer is v\_8. The second stage is similar, with a summer producing s\_r6 and a delay element 'T' followed by a summer producing v\_2. The third stage produces s\_r7 and v\_1. The final output s\_r(k) is produced by a summer with a positive input from s\_r8 and a negative feedback from a delay element 'r\_1'. The output s\_r(k) is also fed back to the first stage through a delay element 'T'. + +Figure 3.5: Short term synthesis filter + +# 4 Codec homing + +The below described codec homing procedure is introduced to the GSM Full Rate speech codec as an optional feature to simplify bit-exact codec tests. It is free to the manufacturers to implement this feature or not. + +## 4.1 Functional description + +The full rate speech codec is described in a bit-exact arithmetic to ease type approval as well as general testing purposes of the full rate speech codec. + +The response of the codec to a predefined input sequence can only be foreseen if the internal state variables of the codec are in a predefined state at the beginning of the experiment. Therefore, the codec has to be put into a so called home state before a bit-exact test can be performed. This is usually done by a reset (a procedure in which the internal state variables of the codec are set to their defined initial values). + +To allow a reset of the codec in remote locations, special homing frames have been defined for the encoder and the decoder, thus enabling a codec homing by inband signalling. + +The codec homing procedure is defined in such a way, that in either direction (encoder or decoder) the homing functions are called after processing the homing frame that is input. The output corresponding to the first homing frame is therefore dependent on the codec state when receiving that frame and hence usually not known. The response to any further homing frame in one direction is by definition a homing frame of the other direction. This procedure allows homing of both, the encoder and decoder from either side, if a loop back configuration is implemented, taking proper framing into account. + +## 4.2 Definitions + +**Encoder-homing-frame:** The encoder-homing-frame consists of 160 identical samples, each 13 bits long, with the least significant bit set to "one" and all other bits set to "zero". When written to 16-bit words with left justification, the samples have a value of 0008 hex. The speech decoder has to produce this frame as a response to the second and any further decoder-homing-frame if at least two decoder-homing-frames were input to the decoder consecutively. + +**Decoder-homing-frame:** The decoder-homing-frame has a fixed set of speech parameters as described in table 4.1 a/b. It is the natural response of the speech encoder to the second and any further encoder-homing-frame if at least two encoder-homing-frames were input to the encoder consecutively. + +**Table 4.1 a: LAR parameter values for the decoder-homing-frame** + +| LARc[1] | LARc[2] | LARc[3] | LARc[4] | LARc[5] | LARc[6] | LARc[7] | LARc[8] | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| 0x0009 | 0x0017 | 0x000F | 0x0008 | 0x0007 | 0x0003 | 0x0003 | 0x0002 | + +**Table 4.1 b: Sub-frame parameter values for the decoder-homing-frame** + +| Parameter | Sub-frame 1 | Sub-frame 2 | Sub-frame 3 | Sub-frame 4 | +|-------------------------------------|--------------------|--------------------|--------------------|--------------------| +| LTP lag Nc | 0x0028 | 0x0028 | 0x0028 | 0x0028 | +| LTP gain bc | 0x0000 | 0x0000 | 0x0000 | 0x0000 | +| RPE grid Mc | 0x0000 | 0x0000 | 0x0000 | 0x0000 | +| block amplitude xmaxc | 0x0000 | 0x0000 | 0x0000 | 0x0000 | +| RPE pulse 0 xMc[0] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 1 xMc[1] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 2 xMc[2] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 3 xMc[3] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 4 xMc[4] | 0x0004 | 0x0004 | 0x0004 | 0x0003 | +| RPE pulse 5 xMc[5] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 6 xMc[6] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 7 xMc[7] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 8 xMc[8] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 9 xMc[9] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 10 xMc[10] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 11 xMc[11] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | +| RPE pulse 12 xMc[12] | 0x0004 | 0x0004 | 0x0004 | 0x0004 | + +## 4.3 Encoder homing + +Whenever the full rate speech encoder receives at its input an encoder-homing-frame exactly aligned with its internal speech frame segmentation, the following events take place: + +- Step 1: The speech encoder performs its normal operation including VAD and DTX and produces a speech parameter frame at its output which is in general unknown. If the speech encoder is already in its home state at the beginning of that frame, then the resulting speech parameter frame is identical to the decoder-homing-frame. This is how the decoder-homing-frame was constructed. +- Step 2: After successful completion of that operation, the speech encoder provokes the homing functions for all sub-modules including VAD and DTX and sets all state variables into their home state. On the reception of the next input frame, the speech encoder will start from its home state. + +NOTE: Applying a sequence of N encoder-homing-frames will cause at least N-1 decoder-homing-frames at the output of the speech encoder. + +## 4.4 Decoder homing + +Whenever the speech decoder receives at its input a decoder-homing-frame (which is not marked as a bad frame), then the following events take place: + +- Step 1: The speech decoder performs its normal operation and produces a speech frame at its output which is in general unknown. If the speech decoder is already in its home state at the beginning of that frame, then the resulting speech frame is replaced by the encoder-homing-frame. This would not naturally be the case but is forced by this definition here. +- Step 2: After successful completion of that operation, the speech decoder provokes the homing functions for all sub-modules including the comfort noise generator and sets all state variables into their home state. On the reception of the next input frame, the speech decoder will start from its home state. + +NOTE 1: Applying a sequence of N decoder-homing-frames will cause at least N-1 encoder-homing-frames at the output of the speech decoder. + +NOTE 2: By definition, the first frame of each decoder test sequence must differ from the decoder-homing-frame at least in one bit position within the parameters for LARs and first subframe. Therefore, if the decoder is in its home state, it is sufficient to check only these parameters to detect a subsequent decoder-homing-frame. This definition is made to support a delay-optimized implementation in the TRAU uplink direction. + +## 4.5 Encoder home state + +In table 4.2, a listing of all the encoder state variables with their predefined values when in the home state is given. + +**Table 4.2: Initial values of the encoder state variables** + +| | Variable | Initial value | +|-----------------------------------|-------------------|---------------| +| Offset compensation filter memory | z1 | set to 0 | +| Offset compensation filter memory | L_z2 | set to 0 | +| Pre-emphasis filter memory | mp | set to 0 | +| LARs from previous frame | LARpp(j-1)[1...8] | all set to 0 | +| Short term analysis filter memory | u[0...7] | all set to 0 | +| LTP delay line | dp[-120...-1] | all set to 0 | + +Initial values for variables used by the VAD algorithm are listed in GSM 06.32 [12]. In addition, the state variables of the DTX system have to be brought into their home state. As the DTX system is not specified in a bit-exact way, no common reset table can be given here. + +## 4.6 Decoder home state + +In table 4.3, a listing of all the decoder state variables with their predefined values when in the home state is given. + +**Table 4.3: Initial values of the decoder state variables** + +| | Variable | Initial value | +|------------------------------------|-------------------|---------------| +| LTP lag from previous frame | nrp | set to 40 | +| LTP delay line | drp[-120...-1] | all set to 0 | +| LARs from previous frame | LARpp(j-1)[1...8] | all set to 0 | +| Short term synthesis filter memory | v[0...8] | all set to 0 | +| De-emphasis filter memory | msr | set to 0 | + +In addition, the state variables of the bad frame handling (error concealment) module and the comfort noise insertion module have to be brought into their home state. As these modules are not specified in a bit-exact way, no common reset table can be given here. + +# 5 Computational details of the RPE-LTP codec + +## 5.1 Data representation and arithmetic operations + +Only two types of variables are used along the implementation of the RPE-LTP algorithm in fixed point arithmetic. These two types are: + +Integer on 16 bits; + +Long integer on 32 bits. + +This assumption simplifies the detailed description and allows the maximum reach of precision. + +In different places of the recommendation, different scaling factors are used according to different operations. To help the reader in the comparison of corresponding floating point and fixed point values given in clause 3 and 4 comments of the format: + +``` +/* var = integer( real_var * scalefactor ) */ +``` + +are used at several points of clause 5. var is the rounded fixed point representation of the floating point representation of var (real\_var) using the given scaling factor. + +In the description, input signal samples, coded parameters and output signal samples are represented by 16 bit words. At the receiving part it shall therefore be ensured that only valid bits (13 bits for samples signal and two to seven bits for coded parameters) are used. In verification tests, the testing system may introduce random bit at non valid places inside these samples (3 LSBs) or parameters (MSBs) to test this function. In the digital test sequences all non valid bits are set to 0. + +The following part of this clause describes the required set of arithmetic operations to implement the RPE-LTP algorithm in fixed point. + +For arithmetics operations or variables with a long integer type (32 bit) a prefix L\_ is used in order to distinguish them from the 16 bit variables or arithmetic operations. + +All the names of the variables are identical to those of the functional description of the RPE-LTP Codec (clause 3) but variables like x', x'' are respectively called: + +``` +x' -----> xp +x'' -----> xpp +``` + +in order to avoid any confusing notation. + +NOTE: The x', x'' variables are examples but are not used within the following description. + +The following notations are used in the arithmetic operations: + +Square brackets ( [..] ) are used for arrays and when needed, the starting index and the ending index are put inside the bracket. For example x[0..159] means that x is an array of 160 words of 16 bits with beginning index 0 and ending index 159 and x[k] is an element of the array x[0..159]. + +All functions' names are underlined. For example add( x, y) means that we perform the addition of x and y. + +| | | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| << n: | denotes a n-bit arithmetic shift left operation (zero fill) on variables of type short or long; if n is less than 0, this operation becomes an arithmetic right shift of -n; | +| >> n: | denotes a n-bit arithmetic right shift operation (sign extension ) on variables of type short or long; if n is less than 0, this operation becomes an arithmetic left shift of -n (zero fill); | +| a > b: | denotes the "greater than" condition; | +| a >= b: | denotes the "greater than or equal" condition; | +| a < b: | denotes the "less than" condition; | +| a <= b: | denotes the "less than or equal" condition; | +| a == b: | denotes the "equal to" condition. | + +The basic structure of the FOR-NEXT loop is used in this description for loop computation; the declaration is: + +``` +|== FOR k= start to end: +| inner computation; +|== NEXT k: +``` + +Also the IF.. ELSE IF structure is used throughout this detailed description. The basic structure is: + +``` +IF (condition1) THEN statement1; +ELSE IF ( condition2) THEN statement2; +ELSE IF ( condition3) THEN statement3; +``` + +The word EXIT is used to exit immediately from a procedure. + +The following arithmetic operations are defined: + +add( var1, var2): performs the addition (var1+var2) with overflow control and saturation; the result is set at +32767 when overflow occurs or at -32768 when underflow occurs. + +sub( var1, var2): performs the subtraction (var1-var2) with overflow control and saturation; the result is set at +32767 when overflow occurs or at -32768 when underflow occurs. + +mult( var1, var2): performs the multiplication of var1 by var2 and gives a 16 bits result which is scaled i.e. + $\underline{\text{mult}}(\text{var1}, \text{var2}) = (\text{var1 times var2}) \gg 15$ and $\underline{\text{mult}}(-32768, -32768) = 32767$ + +mult\_r( var1, var2): same as mult but with rounding i.e. $\underline{\text{mult\_r}}(\text{var1}, \text{var2}) = ((\text{var1 times var2}) + 16384) \gg 15$ and $\underline{\text{mult\_r}}(-32768, -32768) = 32767$ + +abs( var1 ): absolute value of var1; $\underline{\text{abs}}(-32768) = 32767$ + +div( var1, var2): div produces a result which is the fractional integer division of var1 by var2; var1 and var2 shall be positive and var2 shall be greater or equal to var1; The result is positive (leading bit equal to 0) and truncated to 16 bits. if var1 == var2 then $\underline{\text{div}}(\text{var1}, \text{var2}) = 32767$ + +L\_mult(var1, var2): L\_mult is a 32 bit result for the multiplication of var1 times var2 with a one bit shift left. + $\underline{\text{L\_mult}}(\text{var1}, \text{var2}) = (\text{var1 times var2}) \ll 1$ . The condition L\_mult (-32768, -32768) does not occur in the algorithm. + +L\_add(L\_var1, L\_var2): 32 bits addition of two 32 bits variables (L\_var1 + L\_var2) with overflow control and saturation; the result is set at 2147483647 when overflow occurs and at -2147483648 when underflow occurs. + +L\_sub(L\_var1, L\_var2): 32 bits subtraction of two 32 bits variables (L\_var1 - L\_var2) with overflow control and saturation; the result is set at 2147483647 when overflow occurs and at -2147483648 when underflow occurs. + +norm( L\_var1 ): norm produces the number of left shifts needed to normalize the 32 bits variable L\_var1 for positive values on the interval with minimum of 1073741824 and maximum of 2147483647 and for negative values on the interval with minimum of -2147483648 and maximum of -1073741824; in order to normalize the result, the following operation shall be done: $\text{L\_norm\_var1} = \text{L\_var1} \ll \underline{\text{norm}}(\text{L\_var1})$ + +L\_var2 = var1: deposit the 16 bits of var1 in the LSB 16 bits of L\_var2 with sign extension. + +var2 = L\_var1: extract the 16 LSB bits of L\_var1 to put in var2. + +When a constant is used in an operation on 32 bits, it shall be first sign-extended on 32 bits. + +## 5.2 Fixed point implementation of the RPE-LTP coder + +The RPE-LTP coder works on a frame by frame basis. The length of the frame is equal to 160 samples. Some computations are done once per frame (analysis) and some others for each of the four sub-segments (40 samples). + +In the following detailed description, procedure 5.2.0 to 5.2.10 are done once per frame to produce at the output of the coder the LARc[1..8] parameters which are the coded LAR coefficients and also to realize the inverse filtering operation for the entire frame (160 samples of signal d[0..159]). These parts produce at the output of the coder: + +``` +| LARc[1..8] : Coded LAR coefficients +|--> These parameters are calculated and sent once per frame. +``` + +Procedure 5.2.11 to 5.2.18 are to be executed four times per frame. That means once for each sub-segment RPE-LTP analysis of 40 samples. These parts produce at the output of the coder: + +``` +| Nc : LTP lag; +| bc : Coded LTP gain; +| Mc : RPE grid selection; +| xmaxc : Coded maximum amplitude of the RPE sequence; +| xMc[0..12] : Codes of the normalized RPE samples; +|--> These parameters are calculated and sent four times per frame. +``` + +### Pre-processing clause + +### 5.2.0 Scaling of the input variable + +After A or $\mu$ -law (PCS 1900) to linear conversion (or directly from the A to D converter) the following scaling is assumed for input to the RPE-LTP algorithm: + +S.v.v.v.v.v.v.v.v.v.v.v.x.x.x ( 2's complement format). +Where S is the sign bit, v a valid bit, and x a "don't care" bit. +The original signal is called sop[..]; + +### 5.2.1 Downscaling of the input signal + +``` + +|== FOR k=0 to 159: +| so[k] = sop[k] >> 3; +| so[k] = so[k] << 2; +|== NEXT k: + +``` + +### 5.2.2 Offset compensation + +This part implements a high-pass filter and requires extended arithmetic precision for the recursive part of this filter. + +The input of this procedure is the array so[0..159] and the output the array sof[0..159]. + +``` + +|== FOR k = 0 to 159: +| +| Compute the non-recursive part. +| s1 = sub( so[k], z1 ); +| z1 = so[k]; +| +| Compute the recursive part. +| L_s2 = s1; +| L_s2 = L_s2 << 15; +| Execution of a 31 by 16 bits multiplication. +| msp = L_z2 >> 15; +| lsp = L_sub( L_z2, ( msp << 15 ) ); +| temp = mult_r( lsp, 32735 ); +| L_s2 = L_add( L_s2, temp ); +| L_z2 = L_add( L_mult( msp, 32735 ) >> 1, L_s2 ); +| +| Compute sof[k] with rounding. +| sof[k] = L_add( L_z2, 16384 ) >> 15; +|== NEXT k: + +``` + +Keep z1 and L\_z2 in memory for the next frame. + +Initial value: z1=0; L\_z2=0; + +### 5.2.3 Pre-emphasis + +``` + +|== FOR k=0 to 159: +| s[k] = add( sof[k], mult_r( mp, -28180 ) ); +| mp = sof[k]; +|== NEXT k: + +``` + +Keep mp in memory for the next frame. + +Initial value: mp=0; + +**LPC analysis clause** + +### 5.2.4 Autocorrelation + +The goal is to compute the array $L\_ACF[k]$ . The signal $s[i]$ shall be scaled in order to avoid an overflow situation. + +Dynamic scaling of the array s[0..159]. + +#### Search for the maximum. + +``` + +smax = 0; +|== FOR k = 0 to 159: +| temp = abs( s [k] ); +| IF ( temp > smax ) THEN smax = temp; +|== NEXT k; + +``` + +#### Computation of the scaling factor. + +``` + +IF ( smax == 0 ) THEN scalauto = 0; +ELSE scalauto = sub( 4, norm( smax << 16 ) ); + +``` + +#### Scaling of the array s[0..159]. + +``` + +IF ( scalauto > 0 ) THEN + | temp = 16384 >> sub( scalauto, 1 ); + |== FOR k = 0 to 159: + | s[k] = mult_r( s[k], temp ); + |== NEXT k: + +``` + +#### Compute the L\_ACF[.]. + +``` + +|== FOR k=0 to 8: +| L_ACF[k] = 0; +|==== FOR i=k to 159: +| L_temp = L_mult( s[i], s[i-k] ); +| L_ACF[k] = L_add( L_ACF[k], L_temp ); +|==== NEXT i: +|== NEXT k: + +``` + +#### Rescaling of the array s[0..159]. + +``` + +IF ( scalauto > 0 ) THEN + |== FOR k = 0 to 159: + | s[k] = s[k] << scalauto; + |== NEXT k: + +``` + +### 5.2.5 Computation of the reflection coefficients + +#### Schur recursion with 16 bits arithmetic. + +``` + +IF( L_ACF[0] == 0 ) THEN + |== FOR i = 1 to 8: + | r[i] = 0; + |== NEXT i: + | EXIT; /continue with clause 5.2.6/ +temp = norm( L_ACF[0] ); +|== FOR k=0 to 8: +| ACF[k] = ( L_ACF[k] << temp ) >> 16; +|== NEXT k: + +``` + +##### Initialize array Pf[.] and Kf[.] for the recursion. + +``` + +|== FOR i=1 to 7: +| K[9-i] = ACF[i]; +|== NEXT i: +|== FOR i=0 to 8: +| P[i] = ACF[i]; +|== NEXT i: + +``` + +##### Compute reflection coefficients. + +``` + +|== FOR n=1 to 8: + +``` + +``` + +| IF( P[0] < abs( P[1] ) ) THEN +| |== FOR i = n to 8: +| | r[i] = 0; +| |== NEXT i: +| | EXIT; /continue with +| | clause 5.2.6/ +| +| r[n] = div( abs( P[1] ), P[0] ); +| IF ( P[1] > 0 ) THEN r[n] = sub( 0, r[n] ); +| +| IF ( n == 8 ) THEN EXIT; /continue with +| clause 5.2-6/ + +``` + +#### Schur recursion. + +``` + +| P[0] = add( P[0], mult_r( P[1], r[n] ) ); +| |==== FOR m=1 to 8-n: +| | P[m] = add( P[m+1], mult_r( K[9-m], r[n] ) ); +| | K[9-m] = add( K[9-m], mult_r( P[m+1], r[n] ) ); +| |==== NEXT m: +| +| |== NEXT n: + +``` + +NOTE: The following lines gives one correct implementation of the div(num, denum) arithmetic operation. +Compute div which is the integer division of num by denum: with denum >= num > 0. + +``` + +L_num = num; +L_denum = denum; +div = 0; +|== FOR k = 0 to 14: +| div= div << 1; +| L_num = L_num << 1; +| IF ( L_num >= L_denom) THEN +| | L_num=L_sub(L_num, L_denom); +| | div = add( div , 1 ); +| |== NEXT k: + +``` + +### 5.2.6 Transformation of reflection coefficients to Log.-Area Ratios + +The following scaling for r[..] and LAR[..] has been used: + +``` + +/* r[..] = integer( real_r[..]*32768. ); -1. <= real_r <1. */ +/* */ +/* LAR[..] = integer( real_LAR[..]*16384. ); */ +/* */ +/* with -1.625 <= real_LAR <= 1.625 */ + +``` + +#### Computation of the LAR[1..8] from the r[1..8]. + +``` + +|== FOR i = 1 to 8: +| temp = abs( r[i] ); +| IF ( temp < 22118 ) THEN temp = temp >> 1; +| ELSE IF ( temp < 31130 ) THEN +| temp= sub(temp, 11059); +| ELSE temp = sub( temp, 26112 ) << 2; +| +| LAR[i] = temp; +| +| IF ( r[i] < 0 ) THEN LAR[i] = sub( 0, LAR[i] ); +| +| |== NEXT i: + +``` + +### 5.2.7 Quantization and coding of the Log.-Area Ratios + +This procedure needs four tables; the following equations give the optimum scaling for the constants: + +``` +/* A[1..8]= integer( real_A[1..8]*1024); 8 values (see table5.1)*/ +/* */ +/* B[1..8]= integer( real_B[1..8]*512); 8 values (see table5.1)*/ +/* */ +/* MAC[1..8]= maximum of the LARc[1..8]; 8 values (see table5.1)*/ +/* */ +/* MIC[1..8]= minimum of the LARc[1..8]; 8 values (see table5.1)*/ +``` + +#### Computation for quantizing and coding the LAR[1..8]. + +``` +|== FOR i =1 to 8: +| temp= mult( A[i], LAR[i] ); +| temp= add( temp, B[i] ); +| temp= add( temp, 256); for rounding +| LARc[i]= temp >> 9; +| +| Check IF LARc[i] lies between MIN and MAX +| +| IF ( LARc[i] > MAC[i] ) THEN LARc[i] = MAC[i]; +| IF ( LARc[i] < MIC[i] ) THEN LARc[i] = MIC[i]; +| LARc[i] = sub( LARc[i], MIC[i] ); /See note below/ +|== NEXT i: +``` + +NOTE: The equation is used to make all the LARc[i] positive. + +### Short term analysis filtering clause + +### 5.2.8 Decoding of the coded Log.-Area Ratios + +This procedure requires for efficient implementation two tables. + +``` +/* INVA[1..8]=integer((32768*8)/(real_A[1..8])); */ +/* 8 values (table 5.2 ) */ +/* MIC[1..8]=minimum value of the LARc[1..8]; */ +/* 8 values (table 5.1) */ +``` + +#### Compute the LARpp[1..8]. + +``` +|== FOR i=1 to 8: +| temp1 = add( LARc[i], MIC[i] ) << 10; /See note below/ +| temp2 = B[i] << 1; +| temp1 = sub( temp1, temp2); +| temp1 = mult_r( INVA[i], temp1); +| LARpp[i] = add( temp1, temp1); +|== NEXT i: +``` + +NOTE: The addition of MIC[i] is used to restore the sign of LARc[i]. + +### 5.2.9 Computation of the quantized reflection coefficients + +Within each frame of 160 analysed speech samples the short term analysis and synthesis filters operate with four different sets of coefficients, derived from the previous set of decoded LARs(LARpp(j-1)) and the actual set of decoded LARs (LARpp(j)). + +#### 5.2.9.1 Interpolation of the LARpp[1..8] to get the LARp[1..8] + +``` +For k_start = 0 to k_end = 12. +|=== FOR i= 1 to 8: +``` + +``` + +| LARp[i] = add((LARpp(j-1)[i] >> 2), (LARpp(j)[i] >> 2)); +| LARp[i] = add( LARp[i] , ( LARpp(j-1)[i] >> 1 ) ); +|==== NEXT i: + +For k_start = 13 to k_end = 26. +|==== FOR i= 1 to 8: +| LARp[i] = add((LARpp(j-1)[i] >> 1), (LARpp(j)[i] >> 1 )); +|==== NEXT i: + +For k_start = 27 to k_end = 39. +|==== FOR i= 1 to 8: +| LARp[i] = add((LARpp(j-1)[i] >> 2), (LARpp(j)[i] >> 2 )); +| LARp[i] = add( LARp[i] , ( LARpp(j)[i] >> 1 ) ); +|==== NEXT i: + +For k_start = 40 to k_end = 159. +|==== FOR i= 1 to 8: +| LARp[i] = LARpp(j)[i]; +|==== NEXT i: + +``` + +Initial value: LARpp(j-1)[1..8]=0; + +#### 5.2.9.2 Computation of the rp[1..8] from the interpolated LARp[1..8] + +The input of this procedure is the interpolated LARp[1..8] array. The reflection coefficients, rp[i], are used in the analysis filter and in the synthesis filter. + +``` + +|== FOR i=1 to 8: +| temp = abs( LARp[i] ); +| IF ( temp < 11059 ) THEN temp = temp << 1; +| ELSE IF (temp < 20070) THEN +| temp = add(temp, 11059); +| ELSE temp = add( (temp >> 2), 26112 ); +| rp[i] = temp; +| IF ( LARp[i] < 0 ) THEN rp[i] = sub( 0, rp[i] ); +|== NEXT i: + +``` + +### 5.2.10 Short term analysis filtering + +This procedure computes the short term residual signal d[..] to be fed to the RPE-LTP loop from the s[..] signal and from the local rp[..] array (quantized reflection coefficients). As the call of this procedure can be done in many ways (see the interpolation of the LAR coefficient), it is assumed that the computation begins with index k\_start (for arrays d[..] and s[..]) and stops with index k\_end (k\_start and k\_end are defined in 5.2.9.1). This procedure also needs to keep the array u[0..7] in memory for each call. + +``` + +|== FOR k = k_start to k_end: +| di = s[k] +| sav = di; +|==== FOR i = 1 to 8: +| temp = add( u[i-1], mult_r( rp[i], di ) ); +| di = add( di, mult_r( rp[i], u[i-1] ) ); +| u[i-1] = sav; +| sav = temp; +|==== NEXT i: +| d[k] = di; +|== NEXT k: + +``` + +Keep the array u[0..7] in memory. + +Initial value: u[0..7]=0; + +### Long Term Predictor (LTP) clause + +### 5.2.11 Calculation of the LTP parameters + +This procedure computes the LTP gain (bc) and the LTP lag (Nc) for the long term analysis filter. This is done by calculating a maximum of the cross-correlation function between the current sub-segment short term residual signal d[0..39] (output of the short term analysis filter; for simplification the index of this array begins at 0 and ends at 39 for each sub-segment of the RPE-LTP analysis) and the previous reconstructed short term residual signal dp[-120..-1]. A dynamic scaling shall be performed to avoid overflow. + +#### Search of the optimum scaling of d[0..39]. + +``` + +dmax = 0; +|== FOR k = 0 to 39: +| temp = abs( d[k] ); +| IF ( temp > dmax ) THEN dmax = temp; +|== NEXT k: + +temp = 0; +IF ( dmax == 0 ) THEN scal = 0; +ELSE temp = norm( dmax << 16 ); +IF ( temp > 6 ) THEN scal = 0; +ELSE scal = sub( 6, temp ); + +``` + +##### Initialization of a working array wt[0..39]. + +``` + +|== FOR k = 0 to 39: +| wt[k] = d[k] >> scal; +|== NEXT k: + +``` + +##### Search for the maximum cross-correlation and coding of the LTP lag. + +``` + +L_max = 0; +Nc = 40; (index for the maximum cross-correlation) +|== FOR lambda = 40 to 120: +| L_result = 0; +|=== FOR k = 0 to 39: +| L_temp = L_mult( wt[k], dp[k-lambda] ); +| L_result = L_add( L_temp, L_result ); +|=== NEXT k: +| IF ( L_result > L_max ) THEN +| | Nc = lambda; +| | L_max = L_result ; +|== NEXT lambda: + +``` + +#### Rescaling of L\_max. + +``` + +L_max = L_max >> ( sub( 6, scal ) ); + +``` + +##### Initialization of a working array wt[0..39]. + +``` + +|== FOR k = 0 to 39: +| wt[k] = dp[k-Nc] >> 3; +|== NEXT k: + +``` + +##### Compute the power of the reconstructed short term residual signal dp[..]. + +``` + +L_power = 0; +|== FOR k = 0 to 39: +| L_temp = L_mult( wt[k], wt[k] ); +| L_power = L_add( L_temp, L_power ); +|== NEXT k: + +``` + +##### Normalization of L\_max and L\_power. + +``` + +IF ( L_max <= 0 ) THEN + | bc = 0; + | EXIT; /cont. with 5.2.12/ +IF ( L_max >= L_power ) THEN + | bc = 3; + | EXIT; /cont. with 5.2.12/ +temp = norm( L_power ); +R = ( L_max << temp ) >> 16; +S = ( L_power << temp ) >> 16; + +``` + +#### Coding of the LTP gain. + +Table 5.3a shall be used to obtain the level DLB[i] for the quantization of the LTP gain b to get the coded version bc. + +``` + +|== FOR bc = 0 to 2: +| IF (R <= mult(S, DLB[bc])) THEN EXIT; /cont. with +| 5.2.12/ +|== NEXT bc; +bc = 3; + +``` + +Initial value: dp[-120..-1]=0; + +### 5.2.12 Long term analysis filtering + +In this part, we have to decode the bc parameter to compute the samples of the estimate dpp[0..39]. The decoding of bc needs the use of table 5.3b. The long term residual signal e[0..39] is then calculated to be fed to the RPE encoding clause. + +#### Decoding of the coded LTP gain. + +``` +bp = QLB[bc]; +``` + +#### Calculating the array e[0..39] and the array dpp[0..39]. + +``` + +|== FOR k = 0 to 39: +| dpp[k] = mult_r( bp, dp[k-Nc] ); +| e[k] = sub( d[k], dpp[k] ); +|== NEXT k: + +``` + +### **RPE encoding clause** + +### 5.2.13 Weighting filter + +The coefficients of the weighting filter are stored in a table (see table 5.4). The following scaling is used: + +``` +/* H[0..10] = integer( real_H[0..10]*8192 ); */ +``` + +#### Initialization of a temporary working array wt[0..49]. + +``` + +|== FOR k= 0 to 4: +| wt[k] = 0; +|== NEXT k: + +|== FOR k = 5 to 44: +| wt[k] = e[k-5]; +|== NEXT k: + +|== FOR k= 45 to 49: +| wt[k] = 0; +|== NEXT k: + +``` + +#### Compute the signal x[0..39]. + +``` + +|== FOR k= 0 to 39: +| L_result = 8192; /rounding of the output +| of the filter/ +|==== FOR i = 0 to 10: +| L_temp = L_mult( wt[k+i], H[i] ); +| L_result = L_add( L_result, L_temp ); +|==== NEXT i: +| L_result = L_add(L_result,L_result); /scaling (x2)/ +| L_result = L_add(L_result,L_result); /scaling (x4)/ +| x[k] = L_result >> 16; +|== NEXT k: + +``` + +### 5.2.14 RPE grid selection + +The signal x[0..39] is used to select the RPE grid which is represented by Mc. + +``` + +EM =0; +Mc = 0; + +|== FOR m = 0 to 3: +| L_result = 0; +|==== FOR i = 0 to 12: +| temp1 = x[m+(3*i)] >> 2; +| L_temp = L_mult( temp1, temp1 ); +| L_result = L_add( L_temp, L_result ); +|==== NEXT i: +| IF ( L_result > EM) THEN +| | Mc = m; +| | EM = L_result; +|== NEXT m: + +``` + +#### Down-sampling by a factor 3 to get the selected xM[0..12] RPE sequence. + +``` + +|== FOR i = 0 to 12: +| xM[i] = x[Mc +(3*i)]; +|== NEXT i: + +``` + +### 5.2.15 APCM quantization of the selected RPE sequence + +#### Find the maximum absolute value xmax of xM[0..12]. + +``` + +xmax = 0; +|== FOR i = 0 to 12: +| temp = abs( xM[i] ) ; +| IF ( temp > xmax ) THEN xmax = temp; +|== NEXT i: + +``` + +#### Quantizing and coding of xmax to get xmaxc. + +``` + +exp = 0; +temp = xmax >> 9; +itest = 0; +|== FOR i = 0 to 5: +| IF ( temp <= 0 ) THEN itest = 1; +| temp = temp >> 1; +| IF ( itest == 0 ) THEN exp = add( exp, 1 ) ; +|== NEXT i: + +``` + +``` +temp = add( exp, 5 ) ; +xmaxc = add( ( xmax >> temp ), ( exp << 3 ) ) ; +``` + +#### Quantizing and coding of the xM[0..12] RPE sequence to get the xMc[0..12]. + +This computation uses the fact that the decoded version of xmaxc can be calculated by using the exponent and the mantissa part of xmaxc (logarithmic table). + +So, this method avoids any division and uses only a scaling of the RPE samples by a function of the exponent. A direct multiplication by the inverse of the mantissa (NRFAC[0..7] found in table 5.5) gives the 3 bit coded version xMc[0..12] of the RPE samples. + +##### Compute exponent and mantissa of the decoded version of xmaxc. + +``` +exp = 0 ; +IF ( xmaxc > 15 ) THEN exp = sub( ( xmaxc >> 3 ), 1 ) ; +mant = sub( xmaxc , ( exp << 3 ) ) ; +``` + +##### Normalize mantissa 0 <= mant <= 7. + +``` +IF ( mant == 0 ) THEN | exp = -4; + | mant = 15; +ELSE | itest = 0; + |== FOR i = 0 to 2: + | IF ( mant > 7 ) THEN itest = 1; + | IF ( itest == 0 ) THEN mant = add( (mant << 1), 1 ); + | IF ( itest == 0 ) THEN exp = sub( exp, 1 ) ; + |== NEXT i: +mant = sub( mant, 8 ) ; +``` + +##### Direct computation of xMc[0..12] using table 5.5. + +``` +temp1= sub( 6, exp ) ; /normalization by the exponent/ +temp2 = NRFAC[mant]; /see table 5.5 (inverse mantissa)/ + +|== FOR i = 0 to 12: +| temp = xM[i] << temp1; +| temp = mult( temp , temp2 ) ; +| xMc[i] = add( ( temp >> 12 ), 4 ) ; /See note below/ +|== NEXT I: +``` + +NOTE: This equation is used to make all the xMc[i] positive. + +##### Keep in memory exp and mant for the following inverse APCM quantizer. + +### 5.2.16 APCM inverse quantization + +This part is for decoding the RPE sequence of coded xMc[0..12] samples to obtain the xMp[0..12] array. Table 5.6 is used to get the mantissa of xmaxc (FAC[0..7]). + +``` +temp1 = FAC[mant]; see 5.2.15 for mant +temp2= sub( 6, exp ) ; see 5.2.15 for exp +temp3= 1 << sub( temp2, 1 ) ; + +|== FOR i =0 to 12: +| temp = sub( ( xMc[i] << 1 ), 7 ) ; /See note below/ +| temp = temp << 12; +| temp = mult_r( temp1, temp ) ; +| temp = add( temp, temp3 ) ; +| xMp[i] = temp >> temp2; +|== NEXT i; +``` + +NOTE: This subtraction is used to restore the sign of $x_{Mc}[i]$ . + +### 5.2.17 RPE grid positioning + +This procedure computes the reconstructed long term residual signal $ep[0..39]$ for the LTP analysis filter. The inputs are the $Mc$ which is the grid position selection and the $x_{Mp}[0..12]$ decoded RPE samples which are upsampled by a factor of 3 by inserting zero values. + +``` + +|== FOR k = 0 to 39: +| ep[k] = 0; +|== NEXT k: + +|== FOR i = 0 to 12: +| ep[Mc + (3*i)] = xMp[i]; +|== NEXT i: + +``` + +### 5.2.18 Update of the reconstructed short term residual signal $dp[-120..-1]$ + +This procedure adds the reconstructed long term residual signal $ep[0..39]$ to the estimated signal $dpp[0..39]$ from the long term analysis filter to compute the reconstructed short term residual signal $dp[-40..-1]$ ; also the reconstructed short term residual array $dp[-120..-41]$ is updated. + +``` + +|== FOR k = 0 to 79: +| dp[-120+k] = dp[-80+k]; +|== NEXT k: + +|== FOR k = 0 to 39: +| dp[-40+k] = add( ep[k], dpp[k] ); +|== NEXT k: + +``` + +Keep the array $dp[-120..-1]$ in memory for the next sub-segment. + +Initial value: $dp[-120..-1]=0$ ; + +## 5.3 Fixed point implementation of the RPE-LTP decoder + +Only the synthesis filter and the de-emphasis procedure are different from the procedures found in the RPE-LTP coder. Procedures 5.3.1 and 5.3.2 are executed for each sub-segment (four times per frame). Procedures 5.3.3, 5.3.4 and 5.3.5 are executed once per frame. + +### 5.3.1 RPE decoding clause + +Procedures 5.2.15 (only the part to get $mant$ and $exp$ of $x_{maxc}$ ), 5.2.16 and 5.2.17 are used to obtain the reconstructed long term residual signal $erp[0..39]$ signal from the received parameters for each sub-segment (i.e. $M_{cr}$ , $x_{maxcr}$ , $x_{mer}[0..12]$ ). + +### 5.3.2 Long term synthesis filtering + +This procedure uses the $b_{cr}$ and $N_{cr}$ parameter to realize the long term synthesis filtering. The decoding of $b_{cr}$ needs the use of table 5.3b. + +- $N_r$ is the received and decoded LTP lag. +- An array $drp[-120..39]$ is used in this procedure. + +The elements for $-120$ to $-1$ of the array $drp$ are kept in memory for the long term synthesis filter. For each sub-segment (40 samples), this procedure computes the $drp[0..39]$ to be fed to the synthesis filter. + +Check the limits of $N_r$ . + +``` + + $N_r = N_{cr}$ ; +IF ( $N_{cr} < 40$ ) THEN $N_r = n_{rp}$ ; + +``` + +``` +IF ( Ncr > 120 ) THEN Nr = nrp; +nrp= Nr; +``` + +Keep the nrp value for the next sub-segment. + +Initial value: nrp=40; + +Decoding of the LTP gain bcr. + +``` +brp = QLB[bc] +``` + +Computation of the reconstructed short term residual signal drp[0..39]. + +``` +|== FOR k = 0 to 39: +| drpp = mult_r( brp, drp[k-Nr] ); +| drp[k] = add( erp[k], drpp ); +|== NEXT k: +``` + +Update of the reconstructed short term residual signal drp[-1..-120]. + +``` +|== FOR k = 0 to 119: +| drp[-120+k] = drp[-80+k]; +|== NEXT k: +``` + +Keep the array drp[-120..-1] for the next sub-segment. + +Initial value: drp[-120..-1]=0; + +### 5.3.3 Computation of the decoded reflection coefficients + +This procedure (which is executed once per frame) is the same as the one described in the CODER part. For decoding of the received LARcr[1..8], see procedure 5.2.8. For the interpolation of the decoded Log.-Area Ratios, see procedure 5.2.9.1 and for the computation of the reflection coefficients rrp[1..8], see procedure 5.2.9.2. + +### 5.3.4 Short term synthesis filtering clause + +This procedure uses the drp[0..39] signal and produces the sr[0..159] signal which is the output of the short term synthesis filter. For ease of explanation, a temporary array wt[0..159] is used. + +Initialization of the array wt[0..159]. + +For the first sub-segment in a frame: + +``` +|== FOR k = 0 to 39: +| wt[k] = drp[k]; +|== NEXT k: +``` + +For the second sub-segment in a frame: + +``` +|== FOR k = 0 to 39: +| wt[40+k] = drp[k]; +|== NEXT k: +``` + +For the third sub-segment in a frame: + +``` +|== FOR k = 0 to 39: +| wt[80+k] = drp[k]; +|== NEXT k: +``` + +For the fourth sub-segment in a frame: + +``` +|== FOR k = 0 to 39: +| wt[120+k] = drp[k]; +|== NEXT k: +``` + +As the call of the short term synthesis filter procedure can be done in many ways (see the interpolation of the LAR coefficient), it is assumed that the computation begins with index *k\_start* (for arrays *wt[..]* and *sr[..]*) and stops with index *k\_end* (*k\_start* and *k\_end* are defined in 5.2.9.1). The procedure also needs to keep the array *v[0..8]* in memory between calls. + +``` + +|== FOR k = k_start to k_end: +| sri = wt[k]; +|=== FOR i = 1 to 8: +| sri = sub( sri, mult_r( rrp[9-i], v[8-i] ) ); +| v[9-i] = add( v[8-i], mult_r( rrp[9-i], sri ) ); +|=== NEXT i: +| sr[k] = sri; +| v[0] = sri; +|== NEXT k: + +``` + +Keep the array v[0..8] in memory for the next call. + +Initial value: v[0..8]=0; + +### Post-processing + +### 5.3.5 De-emphasis filtering + +``` + +|== FOR k = 0 to 159: +| temp = add( sr[k], mult_r( msr, 28180 ) ); +| msr = temp; +| sro[k] = msr; +|== NEXT k: + +``` + +Keep msr in memory for the next frame. + +Initial value: msr=0; + +### 5.3.6 Upscaling of the output signal + +``` + +|== FOR k = 0 to 159: +| srop[k] = add( sro[k], sro[k] ); +|== NEXT k: + +``` + +### 5.3.7 Truncation of the output variable + +``` + +|== FOR k = 0 to 159: +| srop[k] = srop[k] >> 3; +| srop[k] = srop[k] << 3; +|== NEXT k: + +``` + +The output format is the following: + +S.v.v.v.v.v.v.v.v.v.v.v.v.0.0.0 (2's complement). + +Where S is the sign bit, v a valid bit. + +NOTE: When a linear to A-law compression is needed, then the sub-block COMPRESS of CCITT G721 recommendation shall be used with inputs: + +``` + +SR = srop[k] >> 3; +LAW = 1; + +``` + +When a linear to $\mu$ -law compression is needed, then the sub-block COMPRESS of CCITT G721 recommendation shall be used with inputs: + +``` + +SR = srop[k] >> 3; +LAW = 0; + +``` + +## 5.4 Tables used in the fixed point implementation of the RPE-LTP coder and decoder + +**Table 5.1: Quantization of the Log.-Area Ratios** + +| i | A[i] | B[i] | MIC[i] | MAC[i] | +|---|-------|-------|--------|--------| +| 1 | 20480 | 0 | -32 | 31 | +| 2 | 20480 | 0 | -32 | 31 | +| 3 | 20480 | 2048 | -16 | 15 | +| 4 | 20480 | -2560 | -16 | 15 | +| 5 | 13964 | 94 | -8 | 7 | +| 6 | 15360 | -1792 | -8 | 7 | +| 7 | 8534 | -341 | -4 | 3 | +| 8 | 9036 | -1144 | -4 | 3 | + +**Table 5.2: Tabulation of $1/A[1..8]$** + +| i | INVA[i] | +|---|---------| +| 1 | 13107 | +| 2 | 13107 | +| 3 | 13107 | +| 4 | 13107 | +| 5 | 19223 | +| 6 | 17476 | +| 7 | 31454 | +| 8 | 29708 | + +**Table 5.3a: Decision level of the LTP gain quantizer** + +| bc | DLB[bc] | +|----|---------| +| 0 | 6554 | +| 1 | 16384 | +| 2 | 26214 | +| 3 | 32767 | + +**Table 5.3b: Quantization levels of the LTP gain quantizer** + +| bc | QLB[bc] | +|----|---------| +| 0 | 3277 | +| 1 | 11469 | +| 2 | 21299 | +| 3 | 32767 | + +**Table 5.4: Coefficients of the weighting filter** + +| i | H[i] | +|----|------| +| 0 | -134 | +| 1 | -374 | +| 2 | 0 | +| 3 | 2054 | +| 4 | 5741 | +| 5 | 8192 | +| 6 | 5741 | +| 7 | 2054 | +| 8 | 0 | +| 9 | -374 | +| 10 | -134 | + +**Table 5.5: Normalized inverse mantissa used to compute xM/xmax** + +| i | NRFAC[i] | +|---|----------| +| 0 | 29128 | +| 1 | 26215 | +| 2 | 23832 | +| 3 | 21846 | +| 4 | 20165 | +| 5 | 18725 | +| 6 | 17476 | +| 7 | 16384 | + +**Table 5.6: Normalized direct mantissa used to compute xM/xmax** + +| i | FAC[i] | +|---|--------| +| 0 | 18431 | +| 1 | 20479 | +| 2 | 22527 | +| 3 | 24575 | +| 4 | 26623 | +| 5 | 28671 | +| 6 | 30719 | +| 7 | 32767 | + +# 6 Digital test sequences + +This clause provides information on the digital test sequences that have been designed to help in the verification of implementations of the RPE-LTP codec. Copies of these sequences are available (see annex A3). As the codec homing procedure (see clause 4) is an optional feature two sets of test vectors are provided, one set without codec homing frames and a second set with codec homing frames. In addition A-law and $\mu$ -law compressed testsequences are provided ffor each set as a further option for TRAU testing. + +## 6.1 Input and output signals + +Table 6.1 defines the input and output signals for the test sequences. The words defined in this table use 16 bits. The left or right justification is indicated in the table. The codewords described in the table correspond to one frame of coder input or decoder output signal; i.e. for 20 ms of input signal the 76 codewords are obtained at the output of the coder and 76 codewords provided at the input of the decoder will yield 20 ms of output signal in the decoder. Three types of files are provided: + +- speech encoder input samples, sop[..] \*.INP +- coded parameters (encoded speech data) \*.COD +- speech decoder output samples, srop[..] \*.OUT + +## 6.2 Configuration for the application of the test sequences + +Two configurations are appropriate in order to test an implementation of the RPE-LTP codec. The first is for testing the coder part of the RPE-LTP algorithm which means that a sop[..] signal (on files: \*.INP) is provided at the input of the encoder which responds with frames of coded parameters. The encoder output has to be checked against reference files (files: \*.COD). The other configuration is for testing the decoder part of the RPE-LTP algorithm. In this case, frames of coded parameters (see table 5.1, files: \*.COD) are sent to the RPE-LTP decoder which responds with the srop[..] signal. These samples have to be checked against reference files (files: \*.OUT). + +### 6.2.1 Configuration 1 (encoder only) + +A reset signal (RS) shall be applied to the RPE-LTP encoder under test to set all internal variables to the exact states specified in clause 5 of this recommendation prior to the start of an input test sequence in order to obtain the correct output values for this test. But please note, this reset signal is only required for a codec implementation without codec + +homing procedure. If codec homing is implemented the reset of the internal state variables is done by the means of software. This test shall be done in real-time with a sampling rate of 8 kHz at the input of the encoder under test (see figure 6.1). All the necessary hardware and software should be installed by the user in order to capture in real time the output coded parameters of the RPE-LTP encoder and to compare them to the dedicated reference file. + +Codec homing not implemented: + +In the case of a correct hardware implementation undergoing test, all speech encoder output frames must be identical to the corresponding frames in the \*.COD file. + +Codec homing implemented: + +Each \*H.INP file includes two homing frames at the start of the test sequence. The function of these is to reset the speech encoder state variables to their initial value. In the case of a correct hardware implementation undergoing test, the first speech encoder output frame is undefined and need not be identical to the first frame in the \*H.COD file. All subsequent speech encoder output frames must be identical to the corresponding frames in the \*H.COD file. + +![Figure 6.1: Configuration 1: RPE-LTP encoder under test. The diagram shows an 'RPE-LTP Encoder under test' block. Inputs include 'RS' (Reset Signal) and 'Input' (13 bits). A '8 kHz sampling rate' is indicated above the input. The output is 'Coded parameters' (2-7 bits), which are then compared.](09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg) + +``` + +graph LR + RS[RS] --> Encoder[RPE-LTP Encoder under test] + Input["Input: 13 bits"] --> Encoder + SamplingRate["8 kHz sampling rate"] --> Input + Encoder --> CodedParams["Coded parameters 2-7 bits"] + CodedParams --> Comparison[/comparison/] + +``` + +Figure 6.1: Configuration 1: RPE-LTP encoder under test. The diagram shows an 'RPE-LTP Encoder under test' block. Inputs include 'RS' (Reset Signal) and 'Input' (13 bits). A '8 kHz sampling rate' is indicated above the input. The output is 'Coded parameters' (2-7 bits), which are then compared. + +Figure 6.1: Configuration 1: RPE-LTP encoder under test + +### 6.2.2 Configuration 2 (decoder only) + +Figure 6.2 shows a RPE-LTP decoder under test. In the same way as described in the coder part, a reset signal (RS) shall be used before the processing of the first frame of coded parameters. But please note that also for the decoder this reset signal is only required if the codec homing procedure is not implemented. The decoder shall be tested for a continuous output with a sampling rate of 8 kHz. At the input of the decoder, the 76 parameters shall be sent in a time interval of 20 ms. + +Codec homing not implemented: + +In the case of a correct hardware implementation undergoing testing, all speech decoder output frames must be identical to the corresponding frames in the \*.OUT file. + +Codec homing implemented: + +Each \*H.COD file includes two homing frames at the start of the test sequence. The function of these is to reset the speech decoder state variables to their initial value. In the case of a correct hardware implementation undergoing testing, the first speech decoder output frame is undefined and need not be identical to first frame in the \*H.OUT file. All subsequent speech decoder output frames must be identical to the corresponding frames in the \*H.OUT file. + +![Figure 6.2: Configuration 2: RPE-LTP decoder under test. The diagram shows an 'RPE-LTP Decoder under test' block. Inputs include 'RS' (Reset Signal) and 'Input' (Coded parameters 2-7 bits). A '8 kHz sampling rate' is indicated above the input. The output is 'Output signal: srop [k]' (13 bits), which are then compared.](92271d74f67effbd92583eb3fba71514_img.jpg) + +``` + +graph LR + RS[RS] --> Decoder[RPE-LTP Decoder under test] + Input["Input: Coded parameters 2-7 bits"] --> Decoder + SamplingRate["8 kHz sampling rate"] --> Input + Decoder --> OutputSignal["Output signal: srop [k] 13 bits"] + OutputSignal --> Comparison[/comparison/] + +``` + +Figure 6.2: Configuration 2: RPE-LTP decoder under test. The diagram shows an 'RPE-LTP Decoder under test' block. Inputs include 'RS' (Reset Signal) and 'Input' (Coded parameters 2-7 bits). A '8 kHz sampling rate' is indicated above the input. The output is 'Output signal: srop [k]' (13 bits), which are then compared. + +Figure 6.2: Configuration 2: RPE-LTP decoder under test + +## 6.3 Test sequences + +The letter 'H' at the end of a file name denotes a test sequences with codec homing frames. + +### 6.3.1 Test sequences for configuration 1 + +For configuration 1, four different input test sequence are provided: + +SRQ01/SEQ01H Sequence for testing the overflow controls in the encoder; + +SEQ02/SEQ02H Sequence for testing the LPC part of the encoder; + +SEQ03/SEQ03H Sequence for testing the LTP part of the encoder; + +SEQ04/SEQ04H Sequence for testing various critical parts of the algorithm. + +Sequence SEQ01/SEQ01H uses a large number of saturated samples. The residual LPC signal reaches very high values, which has two effects on the processing: + +- occurrence of a large number of overflows in addition/subtraction operations. Table 6.2 describes each overflow point and the number of occurrences for each. +- the excitation RPE samples have a large dynamic range and the 64 codewords of the sub-block maximum are each obtained at least once on output. + +Sequence SEQ02/SEQ02H focuses successively on each reflection coefficient calculated in the Schur recursion. Table 6.3 shows which frames deal with which reflection coefficient and its dynamic range. The Log.-Area codewords output by the coder cover the full range of their possible values except the 2nd LARc that does not reach the value 0 and 63 (min and max). The maximum value (63) is however obtained in sequence 4. + +Sequence SEQ03/SEQ03H tests the long term predictor part of the algorithm. It has been generated by exciting a sharply resonant filter with a periodic train of impulses; this produces a pitched signal. Each part corresponding to a given pitch is 128 ms (4 blocks of 256 words) long. The pitch periods have been randomly drawn in the range [2,15] ms and the random order is shown in table 6.4. + +Sequence SEQ04/SEQ04H accounts for various remaining non tested points of the algorithm where implementing errors may be suspected. Tables 6.5 and 6.6 summarize the critical points that this sequence has been designed to check (i.e. where the three previous sequences were ineffective). Table 6.5 shows the list of tested points where errors can be detected. Each tested error is described and the frame number corresponding to the first occurrence of a divergence between the exact and the degraded algorithm is also indicated. + +Table 6.6 illustrates three paths of the algorithm that are never explored during the processing of the three previous sequences; the table shows which condition leads to each path and the number of associated occurrences in sequence SEQ04/SEQ04H. + +Notice finally one point where special care shall be taken: + +- A small degradation (i.e. +/- 1) of DLB[2] (the third decision level of the LTP gain quantizer (see table 5.3a) is unable to provide any noticeable effect on the output of the four sequences described above). + +### 6.3.2 Test sequences for configuration 2 + +Five different input test sequence are provided for this configuration. Four sequences obtained in configuration 1 at the output of the encoder (coded parameters) are used as input for the decoder under test in configuration 2. + +Table 6.7 gives the list of tested overflow points and their occurrence on sequence SEQ01/SEQ01H for this configuration. + +Sequence SEQ05/SEQ05H is provided to scan all possible codes for each parameter. This sequence is an artificial sequence and does not correspond to any encoder output. The codewords have been randomly generated and cover the entire range of codewords values. Moreover, the delay value Nr belonging to [40,120] in an error-free transmission condition, takes in this sequence its value in [0,127]. In this case the decoder behaviour on non-allowed values of Nr will be tested. + +**Table 6.1a: Signals used in digital test sequences (\*.INP)** + +| Name | Description | Justification | +|---------------|--------------------------------|---------------| +| ENCODER INPUT | | | +| sop[k] | 13 bits: encoder input signal. | left | + +**Table 6.1b: Signals used in digital test sequences (\*.COD)** + +| Name | Description | Justification | +|---------------------------------------|-----------------------------------|---------------| +| ENCODER OUTPUT / DECODER INPUT | | | +| LARc[1] | 6 bits : 1st Log.-Area Ratio | right | +| LARc[2] | 6 bits : 2nd Log.-Area Ratio | right | +| LARc[3] | 5 bits : 3rd Log.-Area Ratio | right | +| LARc[4] | 5 bits : 4th Log.-Area Ratio | right | +| LARc[5] | 4 bits : 5th Log.-Area Ratio | right | +| LARc[6] | 4 bits : 6th Log.-Area Ratio | right | +| LARc[7] | 3 bits : 7th Log.-Area Ratio | right | +| LARc[8] | 3 bits : 8th Log.-Area Ratio | right | +| Sub-frame no 1 | | | +| Nc | 7 bits : LTP lag | right | +| bc | 2 bits : LTP gain | right | +| Mc | 2 bits : RPE grid position | right | +| xmaxc | 6 bits : Block amplitude | right | +| xMc[0..12] | 3 bits : RPE pulses index 0 to 12 | right | +| Sub-frame no 2 | | | +| Nc | 7 bits : LTP lag | right | +| bc | 2 bits : LTP gain | right | +| Mc | 2 bits : RPE grid position | right | +| xmaxc | 6 bits : Block amplitude | right | +| xMc[0..12] | 3 bits : RPE pulses index 0 to 12 | right | +| Sub-frame no 3 | | | +| Nc | 7 bits : LTP lag | right | +| bc | 2 bits : LTP gain | right | +| Mc | 2 bits : RPE grid position | right | +| xmaxc | 6 bits : Block amplitude | right | +| xMc[0..12] | 3 bits : RPE pulses index 0 to 12 | right | +| Sub-frame no 4 | | | +| Nc | 7 bits : LTP lag | right | +| bc | 2 bits : LTP gain | right | +| Mc | 2 bits : RPE grid position | right | +| xmaxc | 6 bits : Block amplitude | right | +| xMc[0..12] | 3 bits : RPE pulses index 0 to 12 | right | + +**Table 6.1c: Signals used in digital test sequences (\*.OUT)** + +| Name | Description | Justification | +|-----------------------|---------------------------------------------------------------------------|---------------| +| DECODER OUTPUT | | | +| srop[k] | 13 bits: decoder output signal. The 3 LSB's of the 16 bits are equal to 0 | left | + +**Table 6.2: List of tested overflow points for sequence 1 (coder part)** + +| Overflow point | No of occurrences | +|--------------------------------------------------------------|--------------------------| +| Short term analysis filter (5.2.10) | | +| 1st add | 1059 | +| 2nd add | 134 | +| LTP parameters computation (5.2.11) | | +| $Abs( d[k] )$ | 5 | +| Long term analysis filter (5.2.12) | | +| sub | 11 | +| Weighting filter (5.2.13) | | +| scaling the result (both x2 and x4) | 302 | +| APCM quantizer (5.2.15) | | +| Find max abs of xm: Abs | 49 | +| Update of Array dp of the long term analysis filter (5.2.18) | | +| add | 126 | + +**Table 6.3** + +| Reflection Coeff. | Frames | Dynamic range | +|--------------------------|---------------|----------------------| +| 1 | 1-135 | -32564,32558 | +| 2 | 136-311 | -32356,32242 | +| 3 | 316-423 | -32157,32744 | +| 4 | 424-524 | -31594,31960 | +| 5 | 525-633 | -31697,31735 | +| 6 | 634-738 | -30055,31575 | +| 7 | 739-839 | -29090,31386 | +| 8 | 840-944 | -31052,31208 | + +Table 6.3 gives the position of the frames dedicated to the study of each reflection coefficient and dynamic range of the coefficient for sequence 2 in configuration 2. + +**Table 6.4: Pitch periods of sequence 3 (configuration 1)** + +| | | | | | | | | | | | | | | | | | +|-----|----|-----|-----|----|----|-----|-----|-----|-----|-----|----|----|-----|-----|-----|----| +| 86 | 56 | 68 | 120 | 52 | 93 | 20 | 66 | 82 | 115 | 114 | 60 | 42 | 45 | 17 | 64 | 16 | +| 88 | 83 | 63 | 90 | 73 | 23 | 77 | 100 | 33 | 29 | 106 | 35 | 67 | 57 | 103 | 116 | 30 | +| 71 | 69 | 81 | 47 | 32 | 97 | 65 | 62 | 111 | 49 | 109 | 25 | 96 | 50 | 54 | 91 | 85 | +| 99 | 70 | 76 | 46 | 26 | 34 | 104 | 108 | 107 | 22 | 119 | 48 | 58 | 37 | 72 | 110 | 27 | +| 24 | 36 | 87 | 51 | 59 | 38 | 21 | 44 | 113 | 39 | 61 | 53 | 18 | 40 | 94 | 105 | 55 | +| 112 | 75 | 98 | 118 | 41 | 80 | 31 | 74 | 28 | 84 | 89 | 79 | 43 | 101 | 95 | 19 | 78 | +| 117 | 92 | 102 | | | | | | | | | | | | | | | + +**Table 6.5: Errors specially detected by sequence 4/Config 1** + +| Test point | Error checked :
incorrect / correct
statement / statement | No of the
1st frame
with error | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| Autocorrelation function
(5.2.4) | k=0 to 158/k=0 to 159 | 27 | +| Computation of the reflect.
coefficients (5.2.5) | if( P[0] <= / if( P[0] <
abs(P[1]) ) / abs(P[1]) ) | 514 | +| Quantization and coding
of the LARs (5.2.7) | A[4] + 1 /A[4]
A[5] - 1 /A[5]
A[5] + 1 /A[5]
A[6] - 1 /A[6]
A[8] - 1 /A[8]
MAC[2] - 1 / MAC[2]
MAC[2] + 1 / MAC[2] | 21
35
430
427
8
24
516 | +| Comput. of the rp from the
interp. LARp (5.2.9) | 11058 / 11059
20069 / 20070 | 19
25 | +| Calc. of the LTP parameters
->Search of the opt scaling
(5.2.11) | k= 0 to 38 / k= 0 to 39 | 32 | +| ->Coding of the LTP gain
(5.2.11) | mult_r/ mult
DLB[0] + 1 / DLB[0]
DLB[1] + 1 / DLB[1] | 373
511
373 | +| ADPCM inverse quantizer
(5.2.16) | FAC[2] + 1 / FAC[2]
FAC[3] - 1 / FAC[3]
FAC[4] + 1 / FAC[4]
FAC[5] - 1 / FAC[5]
FAC[5] + 1 / FAC[5]
FAC[6] - 1 / FAC[6]
FAC[6] + 1 / FAC[6]
FAC[7] - 1 / FAC[7] | 422
179
74
439
74
479
330
139 | + +**Table 6.6: Paths specially explored by sequence 4/Config 1** + +| Test point | Number of
occurrences | +|------------------------------------------------------------------------------------|--------------------------| +| Autocorrelation function (5.2.4)
condition smax == 0 | 8 | +| Computation of the reflection coefficients :
-> condition L_ACF[0] == 0 (5.2.5) | 8 | +| -> condition P[0] < abs(P[1])(5.2.5) | 4 | + +**Table 6.7: List of tested overflows points for sequence 1 (decoder part)** + +| Overflow Point | Nb of occurrences | | | +|----------------------------------------------|-------------------|------------|------------| +| | Sequence 1 | Sequence 2 | Sequence 3 | +| Long term synthesis filter
(5.3.2) : add | 126 | 0 | 0 | +| Short term synthesis filter :
(5.3.4) | | | | +| 1st add: | 4499 | 0 | 0 | +| 2nd add: | 405 | 1 | 0 | +| De-emphasize filter
(5.3.5): add | 89 | 0 | 0 | +| Scaling of the output signal
(5.3.6): add | 16691 | 339 | 19 | + +### 6.3.3 Additional Test sequences for Codec Homing + +The test sequences described below are only required if the codec homing procedure is implemented. + +#### 6.3.3.1 Codec homing frames + +In addition to the test sequences described above, two homing sequences are provided to assist in codec testing. SEQ06H.INP contains one encoder-homing-frame. SEQ06H.COD contains one decoder-homing-frame. + +#### 6.3.3.2 Sequence for an extensive test of the decoder homing + +If the decoder receives a complete decoder-homing-frame (which is not marked as a bad frame), then it is sufficient that the following frame contains only the LARs and the first subframe data of the decoder-homing-frame to cause a decoder reset and the output of the encoder-homing-frame. To check this behaviour the test sequence HOMING01.COD/OUT was produced. As the test sequences SEQ01H...05H the sequence HOMING01 contains 2 complete decoder-homing-frames at the beginning and inside there is a mixture of complete and fractional (incomplete) decoder-homing-frames. + +#### 6.3.3.3 Sequences for finding the 20 ms framing of the GSM full rate speech encoder + +When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (MS test) or can be reached easily on the Abis-interface (test on network side). + +When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder. + +In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronization sequences. This procedure can be used for MS as well as for network side. + +Synchronization can be achieved in two steps. First, bit synchronization has to be found. In a second step, frame synchronization can be determined. This procedure takes advantage of the codec homing feature of the full rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined which can be used as a trigger reference. + +##### **- Bit synchronization** + +The input to the speech encoder is a series of 13 bit long words (104 kbits/s, 13 bit linear PCM). When starting to test the speech encoder, no knowledge is available of bit synchronization, i.e., where the encoder expects its least significant bits, and where it expects the most significant bits. + +The encoder-homing-frame consists of 160 samples, all set to zero with the exception of the least significant bit, which is set to one (0 0000 0000 0001 binary, or 0x0008 hex if written into 16 bit words left justified). If two such encoder-homing-frames are input to the encoder consecutively, the decoder-homing-frame is expected at the output as a reaction of the second encoder-homing-frame. + +Since there are only 13 possibilities for bit synchronization, after a maximum of 13 trials bit synchronization can be reached. In each trial three consecutive encoder-homing-frames are input to the encoder. If the decoder-homing-frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder-homing-frame is detected at the output, bit synchronization is found, and the first step can be terminated. + +The reason why three consecutive encoder-homing-frames are needed is that frame synchronization is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder-homing-frames. + +An example of the 13 different frame triplets is given in sequence BITSYNC.INP. + +##### **- Frame synchronization** + +Once bit synchronization is found, frame synchronization can be found by inputting one special frame that delivers 160 different output frames, depending on the 160 different positions that this frame can possibly have with respect to the encoder framing. + +This special synchronization frame was found by taking one input frame and shifting it through the positions 0 to 159. The corresponding 160 encoded speech frames were calculated and it was verified that all 160 output frames were different. When shifting the input synchronization frame, the samples at the beginning were set to 0x0008 hex, which corresponds to the samples of the encoder-homing-frame. + +Before inputting this special synchronization frame to the encoder, again the encoder has to be reset by one encoder-homing-frame. A second encoder-homing-frame is needed to provoke a decoder-homing-frame at the output that can be used as a trigger reference. Since the framing of the encoder is not known at that stage, three encoder-homing-frames have to precede the special synchronization frame to ensure that the encoder reads at least two homing frames, and at least one decoder-homing-frame is produced at the output, serving as a trigger for recording. + +The special synchronization frame preceded by the three encoder-homing-frames are given in SEQSYNC.INP. The corresponding 160 different output frames are given in SYNC000.COD through SYNC159.COD. The three digit number in the filename indicates the number of samples by which the input is retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing can be attained. + +#### **6.3.3.4 Formats and sizes of the synchronization sequences** + +##### **BIT SYNC.INP:** + +This sequence consists of 13 frame triplets. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (BITSYNC.INP)} = 13 * 3 * 160 * 2 \text{ bytes} = 12\,480 \text{ bytes}$$ + +##### **SEQSYNC.INP:** + +This sequence consists of 3 encoder reset frames and the special synchronization frame. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (SEQSYNC.INP)} = 4 * 160 * 2 \text{ bytes} = 1\,280 \text{ bytes}$$ + +##### **SYNCXXX.COD:** + +These sequences consist of 1 encoder output frame each. They have the format of the speech encoder output test sequences (16 bit words right justified). + +The size of them is therefore: + +$$\text{SIZE (SYNCXXX.COD)} = 76 * 2 \text{ bytes} = 152 \text{ bytes}$$ + +# Optional 8 bit Test Sequences + +In addition to the test sequences with and without homing as described above, two complete sets of test sequences with A-law and $\mu$ -law compressed are provided. These sequences allow the test of TRAU equipment by means of the A-Interface. On the A-Interface speech data is available as a 64 kbps PCM data stream of compressed samples with 8 bits each. + +The usage of these 8 bit test sequences is exactly the same as described above for the 13 bit linear test sequences except that the A-Interface is used instead of feeding/taking them directly into/from the speech codec. Therefore bit synchronization is not necessary, too. + +Provided are the encoder input sequences \_x.INP, the encoder output sequences \_x.COD and the decoder output sequences \_x.OUT. + +The \_x.INP sequences are used at the encoder input and result in the \_x.COD sequences at the encoder output. + +The linear decoder input sequences .COD (without -x in their names) have to be used to force the 8 bit compressed decoder output sequences -x.OUT. + +The format of the \_x.INP and \_x.OUT sequences is such that 160 samples of a speech frame are contained in one byte each. This results in a file size of half the size of the 13 bit linear test sequences. + +The format of the \*.cod files remains unchanged. + +# Annex A (informative): Codec performance + +## A.1 Performance of the RPE-LTP + +### A.1.1 Introduction + +The purpose of this annex is to give a broad outline of the performance of the RPE-LTP codec with other parts of the digital network. Some general guidance is also offered on non-voice services. + +### A.1.2 Speech performance + +Planning rules for digital processes are defined in terms of quantizing distortion units (qdu) which can be realized from the following formula (reference 1) using the assumption that the formula accuracy represents the determination of qdus from QN measurements: + +$$QN = 37 - 15 \log_{10}(n) \quad , \text{where } n \text{ is the qdu} \quad (A1.1)$$ + +By definition 1 qdu is the quantization distortion arising from one commercial PCM codec. + +NOTE: The subjective testing methodology to determine QN for the RPE-LTP codec was consistent with current ITU-T methods (reference 2). + +#### A.1.2.1 Single encoding + +Under error-free transmission conditions the perceived quality of the RPE-LTP codec (see figure A.1.1) is lower than both codecs conforming to recommendations ITU-T G.711 and ITU-T G.721 (superseded by G.726). Table A.1.1 indicates the relative performance of the codec and can be compared with codecs conforming to recommendations ITU-T G.711 and ITU-T G.721 (superseded by G.726). + +The performance of the RPE-LTP codec has been found to be substantially unaffected down to a carrier to interference (C/I) ratio of 10 dB, but may be considered to have acceptable performance down to 7 dB. Smaller C/I ratios produce unacceptable degradation of speech performance and should be avoided. + +NOTE 1: It should be noted that there are doubts as to whether the simulations which generated the error pattern properly represent real operating conditions. The C/I values quoted should therefore only be considered as parameters of this simulation. They may not correspond to real radio interference conditions. Results from early GSM validation hardware show that the C/I values which give the performance quoted may be several dBs higher. Some error statistics of the simulations are shown in table A.1.2. + +NOTE 2: The real condition C/I = 10 dB is believed to correspond to about 90 % coverage. + +**Table A.1.1: Relative levels of speech performance under error-free conditions** + +| Codec | QN (dB) | qdu | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------| +| G.711
(64 kbit/s, A- or $\mu$ -law (PCS 1900) PCM) | 37 | 1 | +| G.721 (superseded by G.726)
(32 kbit/s, ADPCM) | 29 | 3.5 (*) | +| RPE-LTP | 23-25 | 7-8 (*) | +| (*) Commercial A- or $\mu$ -law (PCS 1900) PCM input and output circuitry included. | | | +| NOTE: The qdu value for the RPE-LTP codec is a conservative estimate. At present there are no specific CCITT rules for determining qdus for encoding below 32 kbit/s. | | | + +**Table A1.2: Bit error statistics for C/I test conditions** + +| Simulated C/I ratio: | 10 dB | 7 dB | 4 dB | +|------------------------------------------------------------------------------|--------------|-------------|-------------| +| Total number of errors in class I (182 bits protected by a 1/2 rate code) | 0.016% | 0.61% | 4.1% | +| Total number of errors in class II (78 bits unprotected) | 4.5% | 8.3% | 13.0% | +| Number of "frame erasure" indications by CRC | 1 | 15 | 95 | +| Number of "frame erasures" not detected by CRC | 1 | 14 | 76 | +| NOTE: The total number of frames was 750. CRC means Cyclic Redundancy Check. | | | | + +#### A.1.2.2 Speech performance when interconnected with coding systems on an analogue basis + +##### A.1.2.2.1 Performance with 32 kbit/s ADPCM (G.721, superseded by G.726) + +The speech performance of the RPE-LTP codec when interconnected with encoding at 32 kbit/s (see figure A.1.3 and A.1.4) decreases in accordance with the formula in clause A.1.2, and appears to obey the law of additivity when qdus have been determined for the individual codecs. + +##### A.1.2.2.2 Performance with another RPE-LTP codec + +The speech performance of the RPE-LTP codec when interconnected with another codec of the same type (see figure A1.2) is lower than that of A1.2.2.1. It again appears to obey the law of additivity when qdus have been determined for the individual codecs. + +##### A.1.2.2.3 Performance with encoding other than RPE-LTP and 32 kbit/s ADPCM (G.721, superseded by G.726) + +No information is available on this point, so great care shall be exercised when interconnection is made to codecs with encoding different from that of A.1.2.2.1 and A.1.2.2.2. + +### A.1.3 Non-speech performance + +It should be noted that the RPE-LTP speech codec is an adaptive system which has been optimized for speech inputs. Great care shall be taken when making measurements with non-speech signals because the normal assumptions of time invariance and linearity cannot be made. + +#### A.1.3.1 Performance with single sine waves + +Detailed experiments have shown that the RPE-LTP codec will pass sine waves with segmental signal to noise ratios generally in excess of 20 dB in the frequency range of 100 - 2000 Hz. However, in some cases reproduction above 2000 Hz is not as good. + +It should be noted that sine waves above 1300 Hz may be reproduced with significant fluctuations in amplitude and frequency due to the adaptive sub-sampling technique employed. This results in irregularities in the measured frequency response. + +A typical frequency response measured with A-law PCM input circuitry is shown in figure A.1.5. If 13 bit linear PCM input circuitry is used, the irregularity is less. + +#### A.1.3.2 Performance with DTMF tones + +It has been shown that the RPE-LTP codec transfers DTMF signals of 80 ms duration. However, questions like minimum allowable signal duration, pause duration and the behaviour in the presence of transmission errors have not been investigated. + +#### A.1.3.3 Performance with information tones + +Experiments have shown that network originated signalling tones, conforming to recommendation ITU-T Q.35, are easily recognizable when passed through the RPE-LTP codec. + +#### A.1.3.4 Performance with voice-band data + +Tests have shown that voice-band data transmission does not work satisfactorily with 1200 bit/s modems according to recommendation ITU-T V.23. Voice-band data according to recommendation ITU-T V.21 (300 bit/s) will not be subject to any significant degradation. + +This behaviour has been tested for one RPE-LTP link (encoder-decoder). The effect of transmission errors has not been tested. + +### A.1.4 Delay + +The theoretical minimum delay of the RPE-LTP codec is 20 ms. However, practical realizations may have an additional processing time in the order of 3 - 8 ms. + +![Figure A.1.1: One - transcoding scheme (A-law). This block diagram shows a single-direction signal flow. It starts with an input arrow pointing to a box labeled 'A/D'. This is followed by a box labeled 'A-law encoder', then a box labeled 'Codec RPE-LTP', then a box labeled 'A-law decoder', and finally a box labeled 'D/A'. An output arrow points away from the 'D/A' box.](86692d82da6655813b5acf58a767a38c_img.jpg) + +Figure A.1.1: One - transcoding scheme (A-law). This block diagram shows a single-direction signal flow. It starts with an input arrow pointing to a box labeled 'A/D'. This is followed by a box labeled 'A-law encoder', then a box labeled 'Codec RPE-LTP', then a box labeled 'A-law decoder', and finally a box labeled 'D/A'. An output arrow points away from the 'D/A' box. + +**Figure A.1.1: One - transcoding scheme (A-law)** + +![Figure A.1.2: Two - transcodings scheme (A-law). This block diagram shows a bidirectional signal flow. The top path (left to right) consists of: input arrow, 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. The bottom path (right to left) consists of: 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. Vertical lines connect the 'D/A' box of the top path to the 'A/D' box of the bottom path, and the 'D/A' box of the bottom path to the 'A/D' box of the top path.](1230eaa9d75a09d7e7b8509931e9190e_img.jpg) + +Figure A.1.2: Two - transcodings scheme (A-law). This block diagram shows a bidirectional signal flow. The top path (left to right) consists of: input arrow, 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. The bottom path (right to left) consists of: 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. Vertical lines connect the 'D/A' box of the top path to the 'A/D' box of the bottom path, and the 'D/A' box of the bottom path to the 'A/D' box of the top path. + +**Figure A.1.2: Two - transcodings scheme (A-law)** + +![Figure A.1.3: Mixed transcodings - scheme 1 (A-law). This block diagram shows a bidirectional signal flow. The top path (left to right) consists of: input arrow, 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. The bottom path (right to left) consists of: 'A/D' box, 'A-law encoder' box, 'Codec G.721' box, 'A-law decoder' box, and 'D/A' box. Vertical lines connect the 'D/A' box of the top path to the 'A/D' box of the bottom path, and the 'D/A' box of the bottom path to the 'A/D' box of the top path.](1381593e48739f603c81fa60e6b98a6c_img.jpg) + +Figure A.1.3: Mixed transcodings - scheme 1 (A-law). This block diagram shows a bidirectional signal flow. The top path (left to right) consists of: input arrow, 'A/D' box, 'A-law encoder' box, 'Codec RPE-LTP' box, 'A-law decoder' box, and 'D/A' box. The bottom path (right to left) consists of: 'A/D' box, 'A-law encoder' box, 'Codec G.721' box, 'A-law decoder' box, and 'D/A' box. Vertical lines connect the 'D/A' box of the top path to the 'A/D' box of the bottom path, and the 'D/A' box of the bottom path to the 'A/D' box of the top path. + +**Figure A.1.3: Mixed transcodings - scheme 1 (A-law)** + +![Block diagram of mixed transcoding scheme 2 (A-law). The diagram shows two parallel processing paths. The top path consists of five blocks in series: an input arrow, an A/D converter, an A-law encoder, a Codec G.721, an A-law decoder, and a D/A converter. The bottom path also consists of five blocks in series, but in reverse order from right to left: an input arrow, an A/D converter, an A-law encoder, a Codec RPE-LTP, an A-law decoder, and a D/A converter. The D/A output of the top path is connected to the A/D input of the bottom path, forming a loop.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` +graph LR; Input1(( )) --> A/D1[A/D]; A/D1 --> A-law1[A-law encoder]; A-law1 --> Codec1[Codec G.721]; Codec1 --> A-law2[A-law decoder]; A-law2 --> D/A1[D/A]; D/A1 --> Input2(( )); Input2 --> A/D2[A/D]; A/D2 --> A-law3[A-law encoder]; A-law3 --> Codec2[Codec RPE-LTP]; Codec2 --> A-law4[A-law decoder]; A-law4 --> D/A2[D/A]; D/A2 --> Output1(( )); +``` + +Block diagram of mixed transcoding scheme 2 (A-law). The diagram shows two parallel processing paths. The top path consists of five blocks in series: an input arrow, an A/D converter, an A-law encoder, a Codec G.721, an A-law decoder, and a D/A converter. The bottom path also consists of five blocks in series, but in reverse order from right to left: an input arrow, an A/D converter, an A-law encoder, a Codec RPE-LTP, an A-law decoder, and a D/A converter. The D/A output of the top path is connected to the A/D input of the bottom path, forming a loop. + +Figure A 1.4: Mixed transcodings - scheme 2 (A-law) + +![Frequency response graph for RPE-LTP codec. The Y-axis is labeled 'Gain (dB)' and ranges from -50.0 to 0.0 in increments of 20.0. The X-axis is labeled 'Frequency (Hz)' and ranges from 20 to 4000 in increments of 1000. The graph shows a noisy signal that starts at 0 dB at 20 Hz, remains relatively flat until about 1000 Hz, then begins to fluctuate and generally decrease, ending at approximately -25 dB at 4000 Hz.](b9f1f5c5167e357277b530940312d9ed_img.jpg) + +| Frequency (Hz) | Gain (dB) | +|----------------|-----------| +| 20 | 0.0 | +| 1000 | 0.0 | +| 2000 | -5.0 | +| 3000 | -10.0 | +| 4000 | -25.0 | + +Frequency response graph for RPE-LTP codec. The Y-axis is labeled 'Gain (dB)' and ranges from -50.0 to 0.0 in increments of 20.0. The X-axis is labeled 'Frequency (Hz)' and ranges from 20 to 4000 in increments of 1000. The graph shows a noisy signal that starts at 0 dB at 20 Hz, remains relatively flat until about 1000 Hz, then begins to fluctuate and generally decrease, ending at approximately -25 dB at 4000 Hz. + +Figure A.1.5: Frequency response for RPE-LTP codec +(with commercial A-law PCM input and output circuitry) + +### A.1.5 Bibliography + +- 1) ITU-T: "Subjective performance assessment of digital processes using the Modulated Noise Reference Unit (MNRU)", annex C, Supplement no 14, Red book, volume V, 1985. +- 2) ITU-T: "Subjective performance assessment of digital processes using the Modulated Noise Reference Unit (MNRU)", annex A, Supplement no 14, Red book, volume V, 1985. +- 3) ITU-T: "Technical characteristics of tones for the telephone service", recommendation Q.35, Red book, volume VI.1, 1985. + +## A.2 Subjective relevance of the speech coder output bits + +Since no valid objective quality criterion for speech signals is available, the only way to build up such a relevance table is to perform listening tests. The procedure described below was used to obtain the relevance classification given in table A.2.1 of the recommendation. + +To classify a single bit, say bit *i* of parameter *k*, a short speech signal (2 sec) was encoded, then this bit was inverted in each frame (the other bits were left unchanged) and the resulting bit stream was fed into the speech decoder. The listeners had to compare the quality of the signal with the quality of six reference signals with different levels of distortion. Repeating this procedure for all bits would result in a subdivision of the 260 bits into six relevance classes. It can be observed that many of the bits have the same physical meaning and it can be expected that bits with the same meaning have the same relevance (e.g. the MSB's of the RPE samples). Relying on this assumption, only one of the equivalent parameters was considered. Since there are 13 parameters with different physical meaning with 56 bits in total, the number of tests is reduced from 260 to 56. + +The reference signals were the same speech signal distorted by inverting one of the six bits of LAR coefficient number one. This resulted in an adequate quantization of distortion levels ranging from "not intelligible" (MSB inverted) to "negligible distortion" (LSB inverted). + +The test was carried out using three listeners and one female speaker. Since the three listeners came to rather similar results, no more listeners were considered to be required. Averaging the three outcomes led to the relevance table given in table A.2.1, where the order of all bits between two successive bits of the first parameter (LAR 1) are arbitrarily chosen. + +**Table A.2.1a: Subjective importance of encoded bits +(the parameter and bit numbers refer to table 1.1)** + +| Importance class | Parameter name | Parameter number | Bit number | +|------------------|----------------------|------------------|--------------------| +| 1 | Log.area ratio 1 | 1 | b6 | +| | Block amplitude | 12,29,46,63 | b53,b109,b165,b221 | +| 2 | Log.area ratio 1 | 1 | b5 | +| | Log.area ratio 2 | 2 | b12 | +| | Log.area ratio 3 | 3 | b17 | +| 3 | Log.area ratio 1 | 1 | b4 | +| | Log.area ratio 2 | 2 | b11 | +| | Log.area ratio 3 | 3 | b16 | +| | Log.area ratio 4 | 4 | b22 | +| | LTP lag | 9,26,43,60 | b43,b99,b155,b211 | +| | Block amplitude | 12,29,46,63 | b52,b108,b164,b220 | +| | Log.area ratio 2,5,6 | 2,5,6 | b10,b26,b30 | +| | LTP lag | 9,26,43,60 | b42,b98,b154,b210 | +| | LTP lag | 9,26,43,60 | b41,b97,b153,b209 | +| | LTP lag | 9,26,43,60 | b40,b96,b152,b208 | +| | LTP lag | 9,26,43,60 | b39,b95,b151,b207 | +| 4 | Block amplitude | 12,29,46,63 | b51,b107,b163,b219 | +| | Log.area ratio 1 | 1 | b3 | +| | Log.area ratio 4 | 4 | b21 | +| | Log.area ratio 7 | 7 | b33 | +| | LTP lag | 9,26,43,60 | b38,b94,b150,b206 | +| | Log.area ratio 5,6 | 5,6 | b25,b29 | +| | LTP gain | 10,27,44,61 | b45,b101,b157,b213 | +| | LTP lag | 9,26,43,60 | b37,b93,b149,b205 | +| | Grid position | 11,28,45,62 | b47,b103,b159,b215 | + +**Table A.2.1b: Subjective importance of encoded bits +(the parameter and bit numbers refer to table 1.1)** + +| Importance | Parameter class | Parameter name | Bit number number | +|------------|------------------------|----------------|--------------------| +| 5 | Log.area ratio 1 | 1 | b2 | +| | Log.area ratio 2,3,8,4 | 2,3,8,4 | b9,b15,b36,b20 | +| | Log.area ratio 5,7 | 5,7 | b24,b32 | +| | LTP gain | 10..27,44,61 | b44,b100,b156,b212 | +| | Block amplitude | 12,29,46,63 | b50,b106,b162,b218 | +| | RPE pulses | 13..25 | b56,b59,...,b92 | +| | RPE pulses | 30..42 | b112,b115,...,b148 | +| | RPE pulses | 47..59 | b168,b171,...,b204 | +| | RPE pulses | 64..76 | b224,b227,...,b260 | +| | Grid position | 11,28,45,62 | b46,b102,b158,b214 | +| | Block amplitude | 12,29,46,63 | b49,b105,b161,b217 | +| | RPE pulses | 13..25 | b55,b58,...,b91 | +| | RPE pulses | 30..42 | b111,b114,...,b147 | +| | RPE pulses | 47..59 | b167,b170,...,b203 | +| | RPE pulses | 64..76 | b235,b238,...,b259 | +| 6 | Log.area ratio 1 | 1 | b1 | +| | Log.area ratio 2,3,6 | 2,3,6 | b8,b14,b28 | +| | Log.area ratio 7 | 7 | b31 | +| | Log.area ratio 8 | 8 | b35 | +| | Log.area ratio 8,3 | 8,3 | b34,b13 | +| | Log.area ratio 4 | 4 | b19 | +| | Log.area ratio 4,5 | 4,5 | b18,b23 | +| | Block amplitude | 12,29,46,63 | b48,b104,b160,b216 | +| | RPE pulses | 13..25 | b54,b57,...,b90 | +| | RPE pulses | 30..42 | b110,b113,...,b146 | +| | RPE pulses | 47..59 | b166,b169,...,b202 | +| | RPE pulses | 64..76 | b222,b225,...,b258 | +| | Log.area ratio 2,6 | 2,6 | b7,b27 | + +## A.3 Format for test sequence distribution + +### A.3.1 Type of files provided + +Three types of files are provided: + +- Files for input of the encoder: \*.INP; +- Files for input of decoder or comparison with encoder output: \*.COD; +- Files for comparison with the decoder output: \*.OUT; + +Five disks are provided containing all the digital test sequences. Disk1.zip contains all test sequences that are required for a codec implementation without codec homing while disk2.zip and disk3.zip contain the test sequences required for a codec implementation with codec homing. Disk4.zip and disk5.zip contain the 8 bit test sequences with A-law and $\mu$ -law compression, respectively. + +Disk1.zip contains the SEQ01.INP, SEQ01.COD, SEQ01.OUT, SEQ02.INP, SEQ02.COD, SEQ02.OUT, SEQ03.INP, SEQ03.COD, SEQ03.OUT, SEQ04.INP, SEQ04.COD, SEQ04.OUT, SEQ05.COD, SEQ05.OUT files. Disk2.zip contains the SEQ01H.INP, SEQ01H.COD, SEQ01H.OUT, SEQ02H.INP, SEQ02H.COD, SEQ02H.OUT files. + +Disk3.zip contains the SEQ03H.INP, SEQ03H.COD, SEQ03H.OUT, SEQ04H.INP, SEQ04H.COD, SEQ04H.OUT, SEQ05H.COD, SEQ05H.OUT, SEQ06H.INP, SEQ06H.COD, HOMING01.COD, HOMING01.OUT, BITSYNC.INP, SEQSYNC.INP and SYNC000...159.COD files. + +Disk4.zip contains the A-law compressed 8 bit test sequences with and without homing. All the files of disk1- 3.zip except for BITSYNC.INP, which is not necessary for TRAU testing, are on disk4.zip. The extension \_A is added to the + +filenames in order to indicate A-law. The files HOMING01, SEQSYC and SYNC000... are renamed to HOM01\_A, SEQSYN\_A and SYN000\_A, respectively. + +Disk5.zip contains the $\mu$ -law compressed 8 bit test sequences with and without homing similar to disk4.zip. The \_u in the filenames stands for $\mu$ -law. + +Table A.3.1a/b gives the contents of the five disks and also the size in bytes and the number of frames for each test sequence file. + +### A.3.2 File format description + +All the files with the linear 13 bit test sequences are written in binary using 16 bit words. This means that input samples (sop[k], on files: \*.INP), output samples (srop[k], on files: \*.OUT) and coded parameters (on files: \*.COD) use 2 bytes each. Hence the sizes of the files are directly related to the number of processed frames. + +For files with linear 13 bit sequences and .INP or .OUT extension type: + +$$\text{Size (in bytes)} = \text{No of frames} * 160 * 2;$$ + +All files \_x.INP and \_x.OUT with the compressed 8 bit test sequences are written in binary using 1 byte per sample. + +For files with compressed 8 bit sequences and \_x.INP or \_x.OUT type: + +$$\text{Size (in bytes)} = \text{No of frames} * 160 * ;$$ + +For all files with .COD extension type: + +$$\text{Size (in bytes)} = \text{No of frames} * 76 * 2;$$ + +Table A.3.1 shows the size of all the 13 bit linear files written in direct binary format. The size of the files containing the optional 8 bit test sequences with type \_x.INP and \_x.OUT is half the size shown in the table (disk4.zip and disk5.zip). + +**Table A.3.1a: Contents of disk1.zip (test sequences without codec homing frames and file sizes)** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. Of Frames | Size in Bytes | Justification | +|----------|-----------------------|------------------|---------------|---------------|---------------| +| 1/5 | Codec test sequence | SEQ01.INP | 584 | 186 880 | Left | +| 1/5 | Codec test sequence | SEQ01.COD | 584 | 88 768 | Right | +| 1/5 | Codec test sequence | SEQ01.OUT | 584 | 186 880 | Left | +| 1/5 | Codec test sequence | SEQ02.INP | 947 | 303 040 | Left | +| 1/5 | Codec test sequence | SEQ02.COD | 947 | 143 944 | Right | +| 1/5 | Codec test sequence | SEQ02.OUT | 947 | 303 040 | Left | +| 1/5 | Codec test sequence | SEQ03.INP | 673 | 215 360 | Left | +| 1/5 | Codec test sequence | SEQ03.COD | 673 | 102 296 | Right | +| 1/5 | Codec test sequence | SEQ03.OUT | 673 | 215 360 | Left | +| 1/5 | Codec test sequence | SEQ04.INP | 520 | 166 400 | Left | +| 1/5 | Codec test sequence | SEQ04.COD | 520 | 79 040 | Right | +| 1/5 | Codec test sequence | SEQ04.OUT | 520 | 166 400 | Left | +| 1/5 | Decoder test sequence | SEQ05.COD | 64 | 9 728 | Right | +| 1/5 | Decoder test sequence | SEQ05.OUT | 64 | 20 480 | Left | + +**Table A.3.1b: Contents of disk2.zip and disk3.zip (test sequences with codec homing frames and file sizes)** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. Of Frames | Size in Bytes | Justification | +|----------|--------------------------------|------------------|---------------|---------------|---------------| +| 2/5 | Codec test sequence | SEQ01H.INP | 586 | 187 520 | Left | +| 2/5 | Codec test sequence | SEQ01H.COD | 586 | 89 072 | Right | +| 2/5 | Codec test sequence | SEQ01H.OUT | 586 | 187 520 | Left | +| 2/5 | Codec test sequence | SEQ02H.INP | 949 | 303 680 | Left | +| 2/5 | Codec test sequence | SEQ02H.COD | 949 | 144 248 | Right | +| 2/5 | Codec test sequence | SEQ02H.OUT | 949 | 303 680 | Left | +| 3/5 | Codec test sequence | SEQ03H.INP | 675 | 216 000 | Left | +| 3/5 | Codec test sequence | SEQ03H.COD | 675 | 102 600 | Right | +| 3/5 | Codec test sequence | SEQ03H.OUT | 675 | 216 000 | Left | +| 3/5 | Codec test sequence | SEQ04H.INP | 522 | 167 040 | Left | +| 3/5 | Codec test sequence | SEQ04H.COD | 522 | 79 344 | Right | +| 3/5 | Codec test sequence | SEQ04H.OUT | 522 | 167 040 | Left | +| 3/5 | Decoder test sequence | SEQ05H.COD | 66 | 10 032 | Right | +| 3/5 | Decoder test sequence | SEQ05H.OUT | 66 | 21 120 | Left | +| 3/5 | Encoder-homing-frame | SEQ06H.INP | 1 | 320 | Left | +| 3/5 | Decoder-homing-frame | SEQ06H.COD | 1 | 152 | Right | +| 3/5 | Decoder homing test | HOMING01.COD | 100 | 15 200 | Right | +| 3/5 | Decoder homing test | HOMING01.OUT | 100 | 32 000 | Left | +| 3/5 | Bit Synchronization | BITSYNC.INP | 39 | 1 2480 | Left | +| 3/5 | Frame Synchronization (input) | SEQSYNC.INP | 4 | 1 280 | Left | +| 3/5 | Frame Synchronization (output) | SYNC000.COD | 1 | 152 | Right | +| 3/5 | | SYNC001.COD | 1 | 152 | Right | +| 3/5 | | SYNC002.COD | 1 | 152 | Right | +| " | | " | " | " | " | +| " | | " | " | " | " | +| " | | " | " | " | " | +| 3/5 | | SYNC159.COD | 1 | 152 | Right | + +# --- Annex B (informative): Test sequence disks + +Provided in archive en\_300961v080101p0.ZIP which accompanies the present document. + +# Annex C (informative): Change history + +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +|---------|-----------|---------|------------------|-------------|----------------------------------------------------------------------------------| +| SMG#07 | | | | 4.0.2 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#23 | 97-737 | A002 | | 5.1.1 | UAP61 comments | +| | 97-741 | A003 | | | Introduction of Homing and 8 bit Test Sequences for Full Rate Speech Transcoding | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | P-99-138 | A004 | whole document | 7.0.0 | Addition of mu-law (PCS 1900) | +| | | | | 7.0.1 | Update to Version 7.0.1 for OAP | +| | | | | 7.0.2 | Update to Version 7.0.2 for Publication | +| | | | | 7.0.3 | Inclusion of associated zip files | +| | | | | 7.0.4 | Inclusion of present text | +| | | | | 8.0.0 | Release 99 version | +| | | | | 8.0.1 | Inclusion of present text file | +| SMG#32 | P-00-272 | A009 | | 8.1.0 | Correction of figure 3.1 | +| | | | | 8.1.1 | Update to Version 8.1.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|--------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-03 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 2001-06 | 12 | SP-010303 | 001 | | Correction of figure 3.2 | 4.0.0 | 4.1.0 | +| 2002-06 | 16 | | | | Version for Release 5 | 4.1.0 | 5.0.0 | +| 2004-12 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 2007-06 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 2008-12 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 2012-09 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2013-12 | 62 | SP-130568 | 0002 | | Correction to references | 11.0.0 | 11.1.0 | +| 2014-09 | 65 | | | | Version for Release 12 | 11.1.0 | 12.0.0 | +| 2015-12 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | + diff --git a/marked/Rel-16/46_series/46021/raw.md b/marked/Rel-16/46_series/46021/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..671c739487467624617f33c1e820e87bbc464b8b --- /dev/null +++ b/marked/Rel-16/46_series/46021/raw.md @@ -0,0 +1,217 @@ + + + + + + +# --- Contents + +| | | +|---------------------------------------------------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 General..... | 6 | +| 5 Requirements ..... | 6 | +| 5.1 Error detection and concealment in case of unreliable speech or SID frames ..... | 6 | +| 5.1.1 Error detection ..... | 6 | +| 5.1.2 Output signal concealment ..... | 6 | +| 5.2 Frame substitution and muting in case of lost speech or SID frames ..... | 6 | +| 5.2.1 First and second lost speech frame..... | 6 | +| 5.2.2 Subsequent lost speech frames ..... | 7 | +| 5.2.3 First and second lost SID frame ..... | 7 | +| 5.2.4 Subsequent lost SID frames..... | 7 | +| 6 Example solutions ..... | 7 | +| 6.1 Example solution for error detection in case of unreliable frames ..... | 7 | +| 6.2 Example solution for output signal concealment in case of unreliable frames ..... | 7 | +| 6.3 Example solution for substitution and muting of lost speech frames ..... | 7 | +| 6.4 Example solution for substitution and muting of lost SID frames..... | 8 | +| Annex A (informative): Change history..... | 9 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler for the half rate speech traffic channels within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".** +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost or unreliable speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS). + +The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the half rate speech traffic channel. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [3] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [4] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +The definitions of terms used in the present document can be found in GSM 06.20 [3], GSM 06.41 [4], GSM 05.03 [2]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-----------------------------------------| +| BFI | Bad Frame Indication | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| GSM | Global System for Mobile communications | +| LPC | Linear Predictive Coding | +| MS | Mobile Station | +| RSS | Radio Sub System | +| RX | Receive | +| SID | SIlence Descriptor | +| UFI | Unreliable Frame Indication | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +The RSS indicates lost speech or SID frames by setting the Bad Frame Indication (BFI) flag and unreliable decoded speech or SID frames by setting the Unreliable Frame Indication (UFI) flag. + +If the BFI flag is set, the speech decoder performs frame substitution and muting of the speech output. The purpose of frame substitution is to conceal the effect of lost frames. The purpose of muting the speech output in case of several lost frames is to indicate the breakdown of the channel to the Mobile Station (MS) user in a way that avoids excessively unpleasant sounds. + +If the UFI flag is set, the speech decoder performs a plausibility analysis of the received frame parameters and of the output signal aiming at the detection and concealment of erroneous frames which are not marked with the BFI flag. + +# --- 5 Requirements + +## 5.1 Error detection and concealment in case of unreliable speech or SID frames + +A cleared BFI flag (BFI= "0") and a set UFI flag (UFI="1") indicate a probably erroneous speech or SID frame. To improve the subjective quality, the probability of decoding erroneous frames shall be decreased by additional error detection which is based on both the exploitation of the frame parameters' properties and the decoder output signal's properties. + +### 5.1.1 Error detection + +By investigating the frame parameter properties, it shall be decided whether the frame is to be considered as usable or unusable. In the latter case, the BFI flag is set and substitution and muting is performed (clause 5.2). Clause 6.1 gives an example solution for error detection in case of unreliable frames. + +### 5.1.2 Output signal concealment + +If the frame is considered as usable, properties of the decoder output signal shall be compared to the corresponding signal properties of the previous valid frames. In case of large differences, the output signal shall be modified such that these differences are limited. Clause 6.2 gives an example solution for output signal concealment in case of unreliable frames. + +## 5.2 Frame substitution and muting in case of lost speech or SID frames + +A set BFI flag (BFI="1") indicates a lost speech or SID frame. Normal decoding of these frames would result in a degradation of the subjective quality of the speech. To improve the subjective quality of the speech, the frame parameters shall be appropriately modified prior to the execution of the speech decoder functions. + +### 5.2.1 First and second lost speech frame + +The first and second lost speech frame shall be partly or completely substituted with the last valid speech frame. For the first and second lost speech frame, the output shall not be muted directly. + +### 5.2.2 Subsequent lost speech frames + +For subsequent lost speech frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 80 ms. For subsequent lost speech frames, the muting of the output shall be maintained. Clause 6.3 gives an example of such a method. + +### 5.2.3 First and second lost SID frame + +The first and second lost SID frame shall be substituted with the last good SID frame. For the first and second lost SID frame, the output shall not be muted directly. + +### 5.2.4 Subsequent lost SID frames + +For subsequent lost SID frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. For subsequent lost SID frames, the muting of the output shall be maintained. Clause 6.4 gives an example of such a method. + +# --- 6 Example solutions + +The C code of the following example solutions are given in GSM 06.06 [5]. + +## 6.1 Example solution for error detection in case of unreliable frames + +With the parameter R0, the average signal energy is transmitted. Except at the beginning or the end of a talk spurt, this parameter shows a smooth behaviour from frame to frame. For error detection purposes, the difference of the R0-value between the actual and the last good frame is computed. If this difference exceeds a level dependent threshold and the frame is marked as unreliable, it is declared unusable by setting the BFI flag equal to "1". + +## 6.2 Example solution for output signal concealment in case of unreliable frames + +In the speech decoder, the output signal is created by processing an excitation sequence through an LPC synthesis filter. The output signal energy of each subframe is calculated and compared to the output signal energy of the previous subframes. If the difference exceeds a level dependent threshold, the excitation sequence is attenuated such that the output signal energy corresponds to the output signal energy of the previous subframes. + +## 6.3 Example solution for substitution and muting of lost speech frames + +For the half rate speech decoder, a possible substitution and muting strategy is based on an 8-state machine. + +The state, with the exception of states 6 and 7, indicates how many consecutive frames were lost. For example, state 5 indicates that 5 consecutive frames (including the current frame) were lost. State 7 is the initial state of the system, so that if the first decoded frame is lost, the frame is muted. Usually, the system will operate in state 0. The state machine remains in this state unless a frame is lost. On each successive lost speech frame, the state machine moves to the next higher numbered state. As soon as a frame is not declared lost, the machine returns to state 0 (unless it is in state 6). The machine remains in state 6 in the case of additional lost speech frames. If the machine is in state 6, a single frame without detected errors moves the machine to state 7 (i.e., two successive frames with no detected errors are needed to return to state 0 from state 6). This provides additional protection during prolonged intervals of very poor channel conditions which might cause false indications of valid speech data. If the machine is in state 7 and a lost speech frame is received, the machine returns to state 6. + +In each state, the following occurs: + +- State 0: No error is detected. The received decoded speech data is output. The current frame parameters are stored. +- State 1: An error has been detected in the frame. If the last speech frame in state 0 is in the unvoiced mode, then the parameters R0, INT\_LPC and the LPC coefficients in the current frame are replaced with the corresponding values from the last good frame. All GSP0 parameters are replaced with the GSP0\_4 parameter from the last good frame. If the MODE bits for the current frame indicate unvoiced, the current frame of codevectors is used. If not, the codevectors from the last good frame are used. The frame's remaining decoded bits are passed to the speech decoder without modification. + +Alternatively, if the last speech frame in state 0 was in the voiced mode, the long term predictor lag from the last good frame is used for all subframes in the current frame. The parameters MODE, R0, INT\_LPC and the LPC coefficients are replaced with those from the last good frame. All GSP0 parameters are replaced with the GSP0\_4 parameter from the last good frame. If the MODE bits for the current frame indicate voiced (MODE = 1, 2 or 3), the current frame of codevectors is used. If not, the codevectors from the last good frame are used. The frame's remaining decoded bits are passed to the speech decoder without modification. + +- State 2: Same action as in state 1. +- State 3: As in state 1 and 2, a frame repetition is performed, but the frame energy $R_0$ (coded on the interval from 0 to 31) is decreased by a value of 2. +- State 4: Same action as in state 3. +- State 5: Same action as in state 3. +- State 6: Again a frame repetition is performed. The output speech signal is muted by setting $R_0$ to zero. +- State 7: The speech signal remains muted, $R_0$ remains zero. + +## 6.4 Example solution for substitution and muting of lost SID frames + +The first and second lost SID frame is replaced by the last good SID frame. + +For subsequent lost SID frames the last good SID frame is repeated, but the frame energy $R_0$ (coded on the interval from 0 to 31) is decreased with a constant value of 2 in each frame down to $R_0 = 0$ . This value is maintained if additional lost SID frames occur. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#15 | | | | 4.0.2 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/46_series/46042/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46042/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf94e4e1f16092ff8abfca5acb4c4f2ddb635f10 --- /dev/null +++ b/marked/Rel-16/46_series/46042/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a033a1fe8f284d0c782552e12ec51501e090917532f3cbacc827f859ce2fc3b +size 110814 diff --git a/marked/Rel-16/46_series/46042/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/46_series/46042/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c8545787850712654c9b072ef78c41d0016662f --- /dev/null +++ b/marked/Rel-16/46_series/46042/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67e66b760461368b3478f2947177f38777fefc0182a026a8cf56c4909fdd426d +size 60678 diff --git a/marked/Rel-16/46_series/46081/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/46_series/46081/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b73e284d96d0699cd53ebcaadbf7a80bf0829649 --- /dev/null +++ b/marked/Rel-16/46_series/46081/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33ebdd15006545969e6cf9717044c666d5d76878d5d38618896c6c9a8bdff394 +size 40800 diff --git a/marked/Rel-16/46_series/46081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..725d1658211c155ee739bb02ddd4e1ff6e91f221 --- /dev/null +++ b/marked/Rel-16/46_series/46081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:783dbbba87636e0c4be3c0c6fc630bfd3864e989e8867320b9e0a010bb1a1ef1 +size 82325 diff --git a/marked/Rel-16/46_series/46081/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/46_series/46081/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36dd2f0a3767115ea2d1391984dcea8032c32e2c --- /dev/null +++ b/marked/Rel-16/46_series/46081/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40f40219a917a763b973996a7967251c0db12a30199a7bb1a2f89a2ba769eba2 +size 37852 diff --git a/marked/Rel-16/46_series/46081/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/46_series/46081/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..222003f1ee9aa4b7125a829025298b0ebe1659a0 --- /dev/null +++ b/marked/Rel-16/46_series/46081/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5631d382e9ef3f729389d106d2941fe6f0d3a3f27088594e9ac2a342e93cdf6 +size 73108 diff --git a/marked/Rel-16/46_series/46081/raw.md b/marked/Rel-16/46_series/46081/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f0b0e1c1ae4598552a29aaf42e70bbd2de1678b3 --- /dev/null +++ b/marked/Rel-16/46_series/46081/raw.md @@ -0,0 +1,393 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 General organization ..... | 7 | +| 5 Transmit (TX) side..... | 8 | +| 5.1 General operation ..... | 8 | +| 5.1.1 Functions of the TX DTX handler..... | 8 | +| 5.1.2 Functions of the TX Radio Subsystem..... | 10 | +| 6 Receive (RX) side ..... | 11 | +| 6.1 General operation ..... | 11 | +| 6.1.1 Functions of the RX radio subsystem..... | 11 | +| 6.1.2 Functions of the RX DTX handler ..... | 12 | +| Annex A (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document describes the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations and Base Station Systems during Discontinuous Transmission (DTX) within the digital cellular telecommunications system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document gives a description of the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX). + +For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same. + +In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being part of the A-bis interface as described in GSM 08.60 [13]. + +The DTX functions described in the present document are mandatory for implementation in the GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. + +For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". +- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [4] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [5] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [6] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech processing functions; General description". +- [7] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [8] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec". +- [9] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [10] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels". + +- [11] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels". +- [12] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels". +- [13] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**accepted SID frame:** traffic frame which is flagged with SID="1" or SID="2" by the Radio Subsystem. + +**bad traffic frame:** traffic frame flagged BFI flag ="1" (Bad Frame Indication) by the Radio Subsystem. + +**frame:** time interval of 20 msec. corresponding to the time segmentation of the Enhanced Full Rate speech transcoder (GSM 06.60 [9]), also used as a short term for a traffic frame. + +**good speech frame:** good traffic frame which is not an accepted SID frame. + +**good traffic frame:** traffic frame flagged BFI flag ="0" by the Radio Subsystem. + +**hangover period:** period of 7 frames added at the end of a speech burst in which VAD flag ="0" and SP flag ="1". + +**invalid SID frame:** accepted SID frame which was not classified as valid SID frame. This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued. + +**lost SID frame:** unusable frame received when the RX DTX handler is generating comfort noise and a SID frame is expected (Time Alignment Flag, TAF="1"). + +**lost speech frame:** unusable frame received when the RX DTX handler is passing on traffic frames directly to the speech decoder. + +**SID code word:** fixed bit pattern defined in GSM 06.62 [11], for labelling a traffic frame as a SID frame. + +**SID field:** bit positions defined in GSM 06.62 [11], of the SID codeword within a SID frame. + +**SID frame:** frame characterized by the SID (Silence Descriptor) code word. It conveys information on the acoustic background noise. + +**SP flag:** boolean flag, generated by the TX DTX handler, indicating the presence of a speech frame ("1") or the presence of a SID frame ("0"). + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +**TAF flag:** Time Alignment Flag. Boolean flag, marks with TAF=1 those traffic frames that are aligned with the SACCH multiframe structure (see GSM 05.08 [5]). The next SID frame is expected at the decoder when TAF=1. + +**traffic frame:** block of 244 information bits transmitted on the Enhanced Full Rate speech traffic channel. + +**unusable frame:** bad traffic frame that is not an accepted SID frame. + +**VAD flag:** boolean flag, generated by the VAD algorithm defined in GSM 06.82 [12] indicating the presence ("1") or the absence ("0") of a speech frame. + +**valid SID frame:** good traffic frame flagged with SID="2" by the Radio Subsystem. This frame is valid for updating of comfort noise parameters at any time. + +## 3.2 Symbols + +For the purposes of the present document, the following symbol applies: + +| | | +|----------------------|------------------------------------------------------------| +| $N_{\text{elapsed}}$ | Number of elapsed frames since the last updated SID frame. | +|----------------------|------------------------------------------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|---------------------------------------------| +| BFI | Bad Frame Indicator | +| BSC | Base Station Controller | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| ETS | European Telecommunication Standard | +| FACCH | Fast Associated Control CHannel | +| GSM | Global System for Mobile Telecommunications | +| MS | Mobile Station | +| RSS | Radio Sub System | +| RX | Receive | +| SACCH | Slow Associated Control CHannel | +| SID | Silence Descriptor | +| TX | Transmit | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +Discontinuous Transmission (DTX) is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes: + +- to save power in the Mobile Station (MS); +- to reduce the overall interference level over the air interface; + +DTX shall be in operation in GSM MS if commanded so by the network, see GSM 04.08 [2]. + +## 4.1 General organization + +The overall DTX mechanism described in the present document requires the following functions: + +- a Voice Activity Detector (VAD) on the transmit (TX) side; +- evaluation of the background acoustic noise on the transmit (TX) side, in order to transmit characteristic parameters to the receive (RX) side; +- generation on the receive (RX) side of a similar noise, called comfort noise, during periods where the radio transmission is switched off. + +The Voice Activity Detector (VAD) is defined in GSM 06.82 [12] and the comfort noise functions in GSM 06.62 [11]. Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.60 [9]. + +In addition to these functions, if the parameters arriving at the RX side are detected to be seriously corrupted by errors, the speech or comfort noise must be generated from substituted data in order to avoid seriously annoying effects for the listener. This function is defined in GSM 06.61 [10]. + +An overall description of the speech processing parts can be found in GSM 06.51 [6]. + +# 5 Transmit (TX) side + +A block diagram of the transmit side DTX functions is shown in figure 1. + +![Block diagram of the transmit side DTX functions. The diagram shows two main components: 'TX DTX handler' and 'TX radio subsystem'. The 'TX DTX handler' contains three sub-blocks: 'Speech encoder', 'Voice Activity Detector', and 'Comfort Noise Computation'. The 'Speech encoder' outputs 'Information bits' (labeled '244') to the 'Channel Encoding' block in the 'TX radio subsystem'. The 'Voice Activity Detector' outputs an 'SP flag' (labeled '1') to the 'SP flag monitoring' block in the 'TX radio subsystem'. The 'Comfort Noise Computation' block is present but its output is not shown.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +graph LR + subgraph TX_DTX_handler [TX DTX handler] + SE[Speech encoder] + VAD[Voice Activity Detector] + CNC[Comfort Noise Computation] + end + subgraph TX_radio_subsystem [TX radio subsystem] + CE[Channel Encoding] + SFM[SP flag monitoring] + end + SE -- "Information bits (244)" --> CE + VAD -- "SP flag (1)" --> SFM + +``` + +Block diagram of the transmit side DTX functions. The diagram shows two main components: 'TX DTX handler' and 'TX radio subsystem'. The 'TX DTX handler' contains three sub-blocks: 'Speech encoder', 'Voice Activity Detector', and 'Comfort Noise Computation'. The 'Speech encoder' outputs 'Information bits' (labeled '244') to the 'Channel Encoding' block in the 'TX radio subsystem'. The 'Voice Activity Detector' outputs an 'SP flag' (labeled '1') to the 'SP flag monitoring' block in the 'TX radio subsystem'. The 'Comfort Noise Computation' block is present but its output is not shown. + +Figure 1: Block diagram of the transmit side DTX functions + +## 5.1 General operation + +The TX DTX handler continuously passes traffic frames, individually marked by a flag SP, to the Radio Subsystem (RSS). This binary flag is redundant to the SID code word labelling. SP flag = "1" indicates a speech frame, SP flag = "0" a SID frame. + +The scheduling of the frames for transmission on the air interface is controlled by the radio subsystem (RSS) alone, on the basis of the SP flag as described in clause 5.1.1. + +### 5.1.1 Functions of the TX DTX handler + +To allow an exact verification of the TX DTX handler functions, all frames before the reset of the system are treated as if there were speech frames of an infinitely long time. Therefore, the first 7 frames after the reset are always marked with SP flag = "1", even if VAD flag = "0" (hangover period, see figure 2). + +The Voice Activity Detector (VAD) shall operate all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD flag = "1" or VAD flag = "0", respectively) on a frame by frame basis (see GSM 06.82 [12]). + +The VAD flag controls indirectly, via the TX DTX handler operations described below, the overall DTX operation on the transmit side. + +Whenever VAD flag = "1", the speech encoder output frame shall be passed directly to the radio subsystem (RSS), marked with SP flag = "1". + +At the end of a speech burst (transition VAD flag = "1" to VAD flag = "0"), it takes 8 consecutive frames to make a new updated SID frame available (see GSM 06.62 [11]). Normally, the first 7 speech encoder output frames after the end of the speech burst shall therefore be passed directly to the radio subsystem, marked with SP flag = "1" ("hangover period"). The first new SID frame is then passed to the RSS as frame 8 after the end of the speech burst, marked with SP flag = "0" (see figure 2). + +![Figure 2: Normal hangover procedure (N_elapsed > 23).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the timing and flag states for speech processing. It consists of three main horizontal axes: + +- VAD flag:** Transitions from high to low. Annotations point to the 'last "speech" frame', 'end of speech burst', and 'first "pause" frame'. A 20 ms frame interval is indicated. +- SP flag:** Shows a 'hangover' period starting from the end of the speech burst. This is the averaging period to calculate $\hat{f}^{ref}$ and $\hat{g}_c^{ref}$ . +- Frame Sequence:** A table-like row showing *Nelapsed* values and frame types: + + +| | | | | | | | | | | | | | +|----------------------|--------|----|----|----|----|----|----|----|--------|---------|---------|---------| +| N elapsed | e.g. | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 0 | 0 | 0 | +| Type | Speech | | | | | | | | Speech | SID k+1 | SID k+2 | SID k+3 | +- Frames to RSS:** Arrows point from SID k+1, k+2, and k+3 downwards. +- SID averaging periods:** Brackets indicate the averaging periods for $f^{mean}$ and $g_c^{mean}$ , spanning from frame 35 to 42. + +Figure 2: Normal hangover procedure (N\_elapsed > 23). + +(Nelapsed: No. of elapsed frames since last update SID). + +**Figure 2: Normal hangover procedure (Nelapsed > 23)** + +If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (8 consecutive frames marked with VAD flag = "0"). This reduces the activity on the air in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see figure 3). + +NOTE: Figure 3 shows as example the longest possible speech burst without hangover. + +![Figure 3: Handling of short speech bursts (N_elapsed < 24) (Example).](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the timing and logic for handling short speech bursts in a DTX system. It consists of three main horizontal axes representing time, divided into 20 ms frames. + +- VAD flag:** Shows voice activity detection. It goes high at the start of a speech burst and low at the end. +- SP flag:** Shows the speech flag status. It follows the VAD flag but remains high for a hangover period after VAD goes low. +- Nelapsed:** A counter for frames. It shows values like ?, ?, ?, 0, 1, 2, 3, 4, 5, 6, 7, 8, ..., 22, ~~23~~ ~~24~~, ..., 29, 0. +- Frames to RSS:** Shows the type of frame passed to the Radio Subsystem. + - Initial frames are marked with '?' and 'SID k'. + - A 'Speech' burst occurs during frames 0-3. + - Following the speech burst, frames 4-7 are marked 'SID k' (repeat previous SID). + - Another 'Speech' burst occurs from frame 8 to 22. + - After frame 22, there is a gap (indicated by ~~23~~ ~~24~~). + - Frames 23-29 are marked 'SID k' (repeat previous SID). + - Frame 29 is followed by a 'new (updated) SID' marked 'SID k+1'. + +Annotations indicate 'SID averaging periods' before and after speech bursts, and 'end of speech burst' markers pointing to the falling edges of the VAD and SP flags. + +Figure 3: Handling of short speech bursts (N\_elapsed < 24) (Example). + +**Figure 3: Handling of short speech bursts ( $N_{elapsed} < 24$ ) (Example)** + +Once the first SID frame after the end of a speech burst has been computed and passed to the Radio Subsystem, the TX DTX handler shall continuously compute and pass updated SID frames to the Radio Subsystem (RSS), marked with SP flag = "0" as long as VAD flag = "0". + +Following a handover, the DTX hangover period shall be initiated in the MS speech encoder to synchronize the encoder and decoder DTX states. This will allow a decoder which is reset at handover to synthesize comfort noise with the correct noise level using the first received SID frame following the handover. + +The speech encoder is operated in full speech modality if SP flag = "1" and in a simplified mode if SP flag = "0", because not all encoder functions are required for the evaluation of comfort noise parameters. + +### 5.1.2 Functions of the TX Radio Subsystem + +The following traffic frames shall be scheduled for transmission: + +- all frames marked with SP flag = "1"; +- the first one with SP flag = "0" after one or more frames with SP flag = "1"; +- those marked with SP=0 and aligned with the SACCH multiframe structure as described in GSM 05.08 [5]. + +This has the overall function, that the radio transmission is cut after the transmission of a SID frame when the speaker stops talking. During speech pauses the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the RX side (and to improve the measurement of the link quality by the RSS). + +If a SID frame (SP flag = "0"), scheduled for transmission is stolen for Fast Associated Control Channel (FACCH) signalling purposes, then the subsequent frame shall be scheduled for transmission instead. + +# 6 Receive (RX) side + +A block diagram of the receive side DTX functions is shown in figure 4. + +![Block diagram of the receive side DTX functions showing the RX DTX handler and RX radio subsystem.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +graph LR + subgraph "RX radio subsystem" + ECD[Error Correction & Detection] + SFD[SID frame detection] + end + subgraph "RX DTX handler" + SD[Speech decoder] + CNG[Comfort Noise Generation] + EC[Error Concealment] + end + ECD -- "Information bits (244)" --> SD + ECD -- "BFI (1)" --> SD + SFD -- "SID (2)" --> CNG + SFD -- "TAF (1)" --> EC + +``` + +The diagram illustrates the flow of information from the RX radio subsystem to the RX DTX handler. The RX radio subsystem contains 'Error Correction & Detection' which outputs 244 information bits and a 1-bit BFI (Bad Frame Indicator) to the 'Speech decoder'. It also contains 'SID frame detection' which outputs a 2-bit SID (Silence Descriptor) flag to 'Comfort Noise Generation' and a 1-bit TAF (Time Alignment Flag) to 'Error Concealment'. + +Block diagram of the receive side DTX functions showing the RX DTX handler and RX radio subsystem. + +Figure 4: Block diagram of the receive side DTX functions + +## 6.1 General operation + +Whatever their context (speech, SID, FACCH or none), the RSS continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 3 flags. These are the Bad Frame Indicator (BFI) flag, the Silence Descriptor (SID) flag and the Time Alignment Flag (TAF) described in clause 6.1.1 and table 1, which serve to classify the traffic frame according to the list of terms defined in clause 3.1. This classification, summarized in table 1, allows the RX DTX handler to determine in a simple way how the received frame is to be handled. + +Table 1: Classification of traffic frames + +| BFI | SID | | | +|-----|-------------------|---|-------------------| +| | 2 | 1 | 0 | +| 0 | Valid SID frame | | Good speech frame | +| 1 | Invalid SID frame | | Unusable frame | + +### 6.1.1 Functions of the RX radio subsystem + +The binary BFI flag (see GSM 05.05 [4]) indicates whether the traffic frame is considered to contain meaningful information bits (BFI flag = "0") or not (BFI flag = "1"). In the context of the present document, a FACCH frame is considered not to contain meaningful bits and shall be marked with BFI flag = "1". The BFI flag must fulfil the performance requirements of GSM 05.05 [4]. + +The SID frame detector compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.62 [11] and gives back the ternary SID flag. The SID flag is coded as follows, where $n$ designates the number of bit deviations: + +SID = 2 when $n < 2$ + +SID = 1 when $2 \leq n < 16$ + +SID = 0 when $n \geq 16$ + +The binary TAF flag marks with TAF="1" those traffic frames that are aligned with the SACCH multiframe structure as described in GSM 05.08 [5]. + +### 6.1.2 Functions of the RX DTX handler + +The RX DTX handler is responsible for the overall DTX operation on the RX side. + +The DTX operation on the RX side shall be as follows: + +- whenever a good speech frame is detected, the DTX handler shall pass it directly on to the speech decoder; +- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.61 [10] shall be applied; +- valid SID frames shall result in comfort noise generation, as defined in GSM 06.62 [11], until the next SID frame is expected (TAF ="1") or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the RSS; +- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#22 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| SMG#30 | 631/99 | A004 | 5.1.1 | 7.1.0 | Fix of DTX Synchronization Problem at Handover | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file